[Pkg-torrus-maintainers] Help with torrus 2.01?
Marc Haber
mh+pkg-torrus-maintainers at zugschlus.de
Fri Sep 16 07:09:08 UTC 2011
On Fri, Sep 16, 2011 at 01:27:15AM +0200, Bernhard Schmidt wrote:
> I have made the first attempts at updating the torrus package. It is
> mostly a packaging cleanup and the new upstream version so far, it
> is not polished.
>
> I have converted the svn repository to git for local use, since I'm
> much more familiar with that toolchain (and I cannot accidentally
> commit something back into the repository). That does not mean the
> Alioth project has to be converted as well, everything is a patch in
> debian/ anyway.
I would support migraton to git should nobody object.
> 1.) Upstream recommends using the FastCGI method for new
> installations, which has been causing a lot less problems than
> mod_perl in my experience. However, old installations will continue
> to use the old method. I don't see a way to migrate automatically.
> Should we
> - not do anything
> - add a note in NEWS.Debian and hope for people to see it
> - add a debconf note
> - ???
Can we have packages that
- use fastCGI on new installs
- continue using mod_perl on updates,
- make migration from mod_perl to fastCGI as easy as possible,
- document this in NEWS.Debian?
> 2.) Upstream strongly recommends rerunning devdiscover and recompile
> the database on upgrades. I don't want to open the can of worms
> associated with an automated devdiscover, but recompiling the
> database would be possible. However, it can take literally ages to
> complete, doing that in postinst would be highly annoying since a
> lot of other services might be down during that time when running a
> dist-upgrade. So what to do?
If torrus continues to run without a recompile in the majority of
cases, we should not do anything in the maintainer scripts. In my
experience, torrus updates were never a smooth thing due to Berkeley
DB breakage, so I reckon that user will be conditioned to read docs
and check torrus after upgrade anyway.
> 3.) torrus-fastcgi is currently an extremely small package with a
> dependency on a 200k perl module, shipping the 2k fcgi-handler
> script and recommending a few (but by far not all) FCGI-webserver
> implementations. IMO, this does not warrant an extra package. Should
> we fold it into torrus-common?
We should, IMO.
> The code is on https://github.com/bernhardschmidt/pkg-torrus/ , it
> has been build-tested on wheezy and is currently running on my
> private box running squeeze. It would probably even compile on
> lenny-backports. Note that this is by far not an extensive test, as
> it has been 1.0.9+gitsomething before. If anyone wants to test it,
> feel free, but don't blame me when it breaks :-)
I will try to, but fear that I won't find any time for it soon :-(
Thanks for helping with the package!
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190
More information about the Pkg-torrus-maintainers
mailing list