Le Monday 13 June 2011 08:47:27, Dominic Hargreaves a écrit :
> > * Digest::MD5 (or other modules within the Digest:: namespace).
>
> This would be implemented in the C part of pperl, so this one is out.
Not necessarily. The "interesting" part of Digest::MD5 is implemented in C
within Digest::M
* Dominic Hargreaves:
> I added the quotation marks because I'm starting to doubt that it is
> worth spending time on. I use pperl a bit, but probably wouldn't miss
> it hugely, and upstream appears to be dead.
I don't use it anymore, either.
You could probably get away without hashing, by using
On Sun, Jun 12, 2011 at 11:20:07PM -0400, Daniel Kahn Gillmor wrote:
> On 06/12/2011 05:36 PM, Dominic Hargreaves wrote:
> > On Fri, May 13, 2011 at 07:38:41PM +0200, Dominique Dumont wrote:
> >> Le vendredi 13 mai 2011 00:31:52, Dominic Hargreaves a écrit :
> >>> This bug is caused by the fact tha
On 06/12/2011 05:36 PM, Dominic Hargreaves wrote:
> On Fri, May 13, 2011 at 07:38:41PM +0200, Dominique Dumont wrote:
>> Le vendredi 13 mai 2011 00:31:52, Dominic Hargreaves a écrit :
>>> This bug is caused by the fact that pperl names its socket files based
>>> on the full path of the perl program
On Fri, May 13, 2011 at 07:38:41PM +0200, Dominique Dumont wrote:
> Le vendredi 13 mai 2011 00:31:52, Dominic Hargreaves a écrit :
> > This bug is caused by the fact that pperl names its socket files based
> > on the full path of the perl program being run under pperl, and there
> > is a fairly sho
Le vendredi 13 mai 2011 00:31:52, Dominic Hargreaves a écrit :
> This bug is caused by the fact that pperl names its socket files based
> on the full path of the perl program being run under pperl, and there
> is a fairly short limit on the full path of the socket (sun_path in
> struct sockaddr_un
[CCing debian-perl since pperl is in the process of being adopted]
On Mon, May 02, 2011 at 12:13:01PM +0100, Dominic Hargreaves wrote:
> severity 533934 serious
> block 619117 by 533934
> thanks
>
> On Tue, Jul 28, 2009 at 05:27:46PM +0200, Tim Retout wrote:
> > This is a copy of an earlier bug w
Processing commands for cont...@bugs.debian.org:
> severity 533934 serious
Bug #533934 [pperl] pperl: FTBFS: tests failed directory
Bug #539028 [pperl] pperl: FTBFS: pperl: perl script failed to start: No such
file or directory
Severity set to 'serious' from 'normal'
Severity set to 'serious' fr
forcemerge 539028 533934
thanks
This is a copy of an earlier bug which got assigned to sbuild. It
doesn't affect the buildds or many users, as I understand it... We
should fix it, but it's not RC.
--
Tim Retout
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subj
Package: pperl
Version: 0.25-5
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20090620 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> make[1]: Entering directory `/build/user-pperl
10 matches
Mail list logo
