nicholas at periapt.co.uk
Fri Dec 24 13:15:56 EST 2010
It would *probably* take about twenty minutes of my time, to package it
for Debian though with the release freeze it could be weeks before it
actually gets into Debian. However there is a presentation on Debian
packaging for Perl here:
cgiapp-request at lists.erlbaum.net wrote:
> Send cgiapp mailing list submissions to
> cgiapp at lists.erlbaum.net
> To subscribe or unsubscribe via the World Wide Web, visit
> or, via email, send a message with subject or body 'help' to
> cgiapp-request at lists.erlbaum.net
> You can reach the person managing the list at
> cgiapp-owner at lists.erlbaum.net
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of cgiapp digest..."
> Today's Topics:
> 1. Re: Data::Session/CGI::Session (Ron Savage)
> Message: 1
> Date: Fri, 24 Dec 2010 16:37:46 +1100
> From: Ron Savage <ron at savage.net.au>
> Subject: Re: [cgiapp] Data::Session/CGI::Session
> To: CGI Application <cgiapp at lists.erlbaum.net>
> Message-ID: <1293169066.3514.29.camel at localhost.localdomain>
> Content-Type: text/plain
> Hi Nicholas
> On Sat, 2010-12-18 at 23:37 +0000, Nicholas Bamber wrote:
>> I notice that a 4.43 o CGI::Session has been released. That should get
>> into Debian in due course. Reviewing the Debian bug list I noticed this:
>> "Session file not being written for driver:File; serializer:Storable"
>> That appears to be related to #482355
>> "Storable.pm segfaults when called during global destruction"
>> And from my brief reading of the bug reports this seems to be related to
>> design/backwards compatibility issues
>> in both CGI::Session and Storable. Can I conclude from that, that the
>> best thing to do with #315669
>> would be to mark it "wontfix" and to suggest that people bother by the
>> bug try Data::Session (which would of course will need to be packaged)?
> This bug report for Storable
> indicates that the maintainers of Storable /may/ attempt to rectify the
> problem with Storable.
> As I see it, since the problem has been identified as being with
> Storable, it should not be up to other modules to add special code to
> compensate for this.
> I do realise various modules have had special code put in them to
> compensate for problems with other modules.
> My policy is that the module with the bug should be fixed, and that
> workarounds should not be used except, perhaps, in exceptional
> circumstances. This case is not exceptional, since users can simply
> switch away from Storable to something reliable.
> We could add a patch to CGI::Session, but I am not going to patch
> Data::Session in this manner.
> What I will do is patch the docs for Data::Session to warn users about
> the issue with Storable.
> I suggest the docs for CGI::Session should be likewise updated.
> Lastly, since I'm a Debian user myself, I could package Data::Session
> (i.e. in Debian format), given some help, since I only have limited
> experience with that. If there is someone available, they can email me
> Thanx for following this up.
More information about the cgiapp