into /etc/apt/sources.list, run 'apt-get update' then 'apt-get install sourceforge', answer a few questions and you have a working Sourceforge. Now. It works. Really.
Well... Mostly. Here's an excerpt of the announcement I sent to the debian-devel mailing-list:
-----CUT-----
I think I have reached a milestone. I have a mostly stable package
that installs fine and works out of the box. I have got a report of a
Debconf problem, but it's probably a detail. Thanks to people who
tried and tested and crashed and reported bugs. So, what do we have?
What works: mostly the web-related stuff. User creation, personal
page, project creation and administration, bug tracking, support
requests, tasks, forums, software map, docs, monitoring, patch
tracker, surveys, news, personal skills, help needed stuff,
bookmarking. The cron jobs work, although some of them might not be
useful.
What doesn't work: mostly everything else, in fact. That includes
mail aliases, shell accounts, CVS integration, mailing-lists, DNS and
virtual hosting of project pages, FTP and file releases. Probably
foundries.
What sucks: most of the stuff is full of references to VA Linux,
OSDN, and more generally plenty of people related to the official
sourceforge.net. I'm not saying that they suck, it's just that seeing
how many mails Debian gets for just mentioning its name in the
template home page for Apache... I'd rather not be remembered as the
guy who caused sourceforge.net to be mailbombed or RBL'ed or spammed
with useless messages.
I know that a Sourceforge without CVS and FTP is far from complete,
but I have used an ancient version of my package here at work for
about six months, and bugs+support+forums+tasks is already rather
useful.
-----CUT-----
You people are encouraged to try the package and report any bugs and problems. I'm also scanning the audience for potential helpers relating to the missing points.
I'm probably going to try the sf-genericinst source and see how much of it I can take and incorporate in my package (due credit will of course be given :-). I haven't seen any references to the "other" services (like, FTP and CVS), but if they are here I'll grab them and if they aren't, well, it'll make it easier for me to get more up-to-date with upstream development (my package is based on the Sourceforge 2.5 release).
Please do not hesitate to contact me about the package, especially if you're having problems or willing to help :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi. thanks for the package...this is exactly what i've been looking for!
I'm currently using potato and having problem installing your package.
the package depends on postgresql-6.1 but I can't find postgresql-6.1 debian package
(lastest version i could find was postgresql 6.0)
and i think package 'perl' is gone as of potato and I can't downgrade perl5 module to old 'perl'
now what do i have to install the package on my potato debian?
thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
now what do i have to install the package on my potato debian?
had to be
==> now what do i have (to do) to install the package on my potato debian?
the meaning is so different:) sorry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
PostgreSQL 7.1 is now in the "experimental" distribution. The maintainer told me he will upload it to "unstable" ("sid") in a few days.
I didn't know the "perl" name was the old name for the package. It also happens to be the new one, that is available in "unstable".
If you don't want to switch to "unstable", I'd recommend using "testing". That distribution, which will become "woody" when it's released, is basically "unstable" with 10 days delay. Packages that stay 10 days in "unstable" with no grave bugs automatically enter "testing".
Thus, if you wait for PostgreSQL 7.1 to enter "testing", you'll be able to upgrade to "testing" and install my sourceforge package.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i got alien to convert the sourceforge.deb but it doesn't work.
So , if anyone have the sourceforge in .rpm format please send it to me at radu@ipdevel.ro
Thanks a lot!
Radu
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't know Red Hat based distributions enough to be reliable here (I used to use RH but I switched rather long ago). But in short: I don't do *.rpm and I don't support them.
My package might very well depend on Debian-specific features. I don't know how RPM works, or if it provides the same facilities (pre/post-inst/rm scripts come to mind, along with the conffiles system). I'm not sure RH-based systems have the same tools (cron.d dir for instance). I'm pretty sure RH doesn't provide tools like Debconf. And RH might just install Apache, PHP and other stuff in different directories than Debian does (although the FHS effort will probably help in that regard).
No flames please, I'm just a happy Debian user (and developer), I think the Debian packaging system is great, I believe it's better than RPM, so I do *.deb. I'd be glad to hear someone takes the *.deb and makes working *.rpm with them, of course :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To go further, I could include script for pre and post installation, but I have only my notes or the work I did. I am looking into the scripts from Franck, but I believe the script you did for a debian install might be closer to what I would like. I do not know if the source for that are available, or how to access then from the .deb without the tool installed on my Mandrake distro.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I could successfully install postgresql 7.1 and it works fine.
while installing sourceforge.deb, error returned
Setting up sourceforge (2.5-0+12) ...
dpkg: error processing sourceforge (--configure):
subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
sourceforge
install script configured apache but database was not configured.
DB user 'sourceforge' was created but could not connect to DB using sourceforge (invalid password?)
sourceforge database was created too but no tables.
am i missing something?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello people,
Having been busily working the last few weeks, I now have a working Debian package for Sourceforge. Which means: cut'n'paste
deb http://people.debian.org/~lolando/debian binary-i386/
deb-src http://people.debian.org/~lolando/debian source/
into /etc/apt/sources.list, run 'apt-get update' then 'apt-get install sourceforge', answer a few questions and you have a working Sourceforge. Now. It works. Really.
Well... Mostly. Here's an excerpt of the announcement I sent to the debian-devel mailing-list:
-----CUT-----
I think I have reached a milestone. I have a mostly stable package
that installs fine and works out of the box. I have got a report of a
Debconf problem, but it's probably a detail. Thanks to people who
tried and tested and crashed and reported bugs. So, what do we have?
What works: mostly the web-related stuff. User creation, personal
page, project creation and administration, bug tracking, support
requests, tasks, forums, software map, docs, monitoring, patch
tracker, surveys, news, personal skills, help needed stuff,
bookmarking. The cron jobs work, although some of them might not be
useful.
What doesn't work: mostly everything else, in fact. That includes
mail aliases, shell accounts, CVS integration, mailing-lists, DNS and
virtual hosting of project pages, FTP and file releases. Probably
foundries.
What sucks: most of the stuff is full of references to VA Linux,
OSDN, and more generally plenty of people related to the official
sourceforge.net. I'm not saying that they suck, it's just that seeing
how many mails Debian gets for just mentioning its name in the
template home page for Apache... I'd rather not be remembered as the
guy who caused sourceforge.net to be mailbombed or RBL'ed or spammed
with useless messages.
I know that a Sourceforge without CVS and FTP is far from complete,
but I have used an ancient version of my package here at work for
about six months, and bugs+support+forums+tasks is already rather
useful.
-----CUT-----
You people are encouraged to try the package and report any bugs and problems. I'm also scanning the audience for potential helpers relating to the missing points.
I'm probably going to try the sf-genericinst source and see how much of it I can take and incorporate in my package (due credit will of course be given :-). I haven't seen any references to the "other" services (like, FTP and CVS), but if they are here I'll grab them and if they aren't, well, it'll make it easier for me to get more up-to-date with upstream development (my package is based on the Sourceforge 2.5 release).
Please do not hesitate to contact me about the package, especially if you're having problems or willing to help :-)
Hi. thanks for the package...this is exactly what i've been looking for!
I'm currently using potato and having problem installing your package.
the package depends on postgresql-6.1 but I can't find postgresql-6.1 debian package
(lastest version i could find was postgresql 6.0)
and i think package 'perl' is gone as of potato and I can't downgrade perl5 module to old 'perl'
now what do i have to install the package on my potato debian?
thanks
now what do i have to install the package on my potato debian?
had to be
==> now what do i have (to do) to install the package on my potato debian?
the meaning is so different:) sorry
I'm afraid you'll have to upgrade your system.
PostgreSQL 7.1 is now in the "experimental" distribution. The maintainer told me he will upload it to "unstable" ("sid") in a few days.
I didn't know the "perl" name was the old name for the package. It also happens to be the new one, that is available in "unstable".
If you don't want to switch to "unstable", I'd recommend using "testing". That distribution, which will become "woody" when it's released, is basically "unstable" with 10 days delay. Packages that stay 10 days in "unstable" with no grave bugs automatically enter "testing".
Thus, if you wait for PostgreSQL 7.1 to enter "testing", you'll be able to upgrade to "testing" and install my sourceforge package.
i got alien to convert the sourceforge.deb but it doesn't work.
So , if anyone have the sourceforge in .rpm format please send it to me at radu@ipdevel.ro
Thanks a lot!
Radu
I don't know Red Hat based distributions enough to be reliable here (I used to use RH but I switched rather long ago). But in short: I don't do *.rpm and I don't support them.
My package might very well depend on Debian-specific features. I don't know how RPM works, or if it provides the same facilities (pre/post-inst/rm scripts come to mind, along with the conffiles system). I'm not sure RH-based systems have the same tools (cron.d dir for instance). I'm pretty sure RH doesn't provide tools like Debconf. And RH might just install Apache, PHP and other stuff in different directories than Debian does (although the FHS effort will probably help in that regard).
No flames please, I'm just a happy Debian user (and developer), I think the Debian packaging system is great, I believe it's better than RPM, so I do *.deb. I'd be glad to hear someone takes the *.deb and makes working *.rpm with them, of course :-)
Hello, lolando
I have started to built a RPM of my own codebase, and I have then also built a RPM of the SF2.5 tarball with all corrections that are generic. See
http://sourceforge.net/forum/message.php?msg_id=215899
To go further, I could include script for pre and post installation, but I have only my notes or the work I did. I am looking into the scripts from Franck, but I believe the script you did for a debian install might be closer to what I would like. I do not know if the source for that are available, or how to access then from the .deb without the tool installed on my Mandrake distro.
Well, paint me late.
Oliver Elphick uploaded PostgreSQL 7.1 packages to "unstable" Debian a few hours ago. No need to go "experimental" for Sourceforge.
I could successfully install postgresql 7.1 and it works fine.
while installing sourceforge.deb, error returned
Setting up sourceforge (2.5-0+12) ...
dpkg: error processing sourceforge (--configure):
subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
sourceforge
install script configured apache but database was not configured.
DB user 'sourceforge' was created but could not connect to DB using sourceforge (invalid password?)
sourceforge database was created too but no tables.
am i missing something?
The default configuration for PostgreSQL 7.1 is more paranoid than it used to be. I'm working on a clean fix for that problem.
Meanwhile, you can edit /etc/postgresql/pg_hba.conf and replace
host all 127.0.0.1 255.0.0.0 ident sameuser
by
host all 127.0.0.1 255.0.0.0 trust
It's not as secure as it should be, so it'll have to go away. I'm working on it.
Thanks roland...it works fine!
it's great:)
After installing postgresql 7.1
modified pg_hba.conf has you said,
configured ssl_module and it just works great
Pleased to hear it :-)
Don't forget to report any problems to me, either by mail (lo-lan-do@users.sourceforge.net) or by IRC (I'm on openprojects.net #Debian-SF).