Control: block -1 by 827075
On Mon, Jun 06, 2016 at 11:54:01PM +0200, Guillem Jover wrote:
> I've been looking recently at creating a small helper to delegate the
> locking to, because the automatic dbgsym packages and dpkg coloring
> have exacerbated this annoyance when building packages :), but
Processing control commands:
> block -1 by 827075
Bug #677865 [libdpkg-perl] dpkg-gencontrol warns about 'File::FcntlLock not
available'
Bug #679777 [libdpkg-perl] libdpkg-perl: Please warn only once about
File::FcntLock being missing
677865 was not blocked by any bugs.
677865 was not blocking
Hi!
On Sun, 2015-05-24 at 20:11:42 +0300, Niko Tyni wrote:
> On Wed, May 28, 2014 at 08:10:50AM +0200, Guillem Jover wrote:
> > On Tue, 2014-05-27 at 23:56:03 +0300, Niko Tyni wrote:
>
> > > @debian-perl: To make this usable for the original problem (giving
> > > dpkg-dev a working
(dropped the debian-perl list, added the pkg-perl team)
On Wed, May 28, 2014 at 08:10:50AM +0200, Guillem Jover wrote:
On Tue, 2014-05-27 at 23:56:03 +0300, Niko Tyni wrote:
@debian-perl: To make this usable for the original problem (giving
dpkg-dev a working File::FcntlLock without a
Package: libdpkg-perl
Version: 1.17.23
Followup-For: Bug #677865
What's the current status of this bug? The most recent mail, in May
2014, mentions a possible improvement in dpkg 1.17.10. Has the
necessarily perl packaging change not yet taken place?
I still see this issue every time I build a
Hi!
On Tue, 2014-05-27 at 23:56:03 +0300, Niko Tyni wrote:
On Tue, May 27, 2014 at 04:49:35PM +0200, Jens Thoms Toerring wrote:
Let's hope the new 0.20 version on CPAN is the final one;-)
Thanks for your awesome work, Jens!
Absolutely, the same goes for the debian-perl team! :)
Hi,
I realized that I can install a 32-bit version of Debian
in a virtual box also on an 64-bit machine and that allowed
me to find the reason for the failing tests. As you already
may have suspected, it was a rather stupid mistake: I had
forgotten to pass the CFLAGS Perl was build with to the
Hi,
On Tue, May 27, 2014 at 03:01:18PM +0300, Damyan Ivanov wrote:
The hurd-i386 build fails with an undefined subroutine error:
Looks like I got this fixed also (a missing '$self-' and a
stray '=cut' - no idea why it wasn't also flagged on other
systems...). Let's hope the new 0.20 version on
On Tue, 27 May 2014 16:49:35 +0200, Jens Thoms Toerring wrote:
On Tue, May 27, 2014 at 03:01:18PM +0300, Damyan Ivanov wrote:
The hurd-i386 build fails with an undefined subroutine error:
Looks like I got this fixed also (a missing '$self-' and a
stray '=cut' - no idea why it wasn't also
On Tue, May 27, 2014 at 04:49:35PM +0200, Jens Thoms Toerring wrote:
Let's hope the new 0.20 version on CPAN is the final one;-)
Thanks for your awesome work, Jens!
@debian-perl: To make this usable for the original problem (giving
dpkg-dev a working File::FcntlLock without a transitive hard
-=| Jens Thoms Toerring, 25.05.2014 23:01:34 +0200 |=-
since I got no complaints about the new version of the
File::FcntlLock module I just uploaded it to CPAN. I hope
that it will help to avoid the problems you had with it.
Package libfile-fcntllock-perl upgraded to 0.16 and uploaded to
Hi,
On Mon, May 26, 2014 at 12:39:51PM +0300, Damyan Ivanov wrote:
Package libfile-fcntllock-perl upgraded to 0.16 and uploaded to Debian
unstable.
Thank you very much. Unfortunately, CPAN testing has shown
that there are some systems where there are problems building
the complete module.
On Mon, 26 May 2014 17:57:34 +0200, Jens Thoms Toerring wrote:
(trimming the CC list a bit)
On Mon, May 26, 2014 at 12:39:51PM +0300, Damyan Ivanov wrote:
Package libfile-fcntllock-perl upgraded to 0.16 and uploaded to Debian
unstable.
Thank you very much. Unfortunately, CPAN testing has
Hi,
On Mon, May 26, 2014 at 08:34:59PM +0200, gregor herrmann wrote:
On Mon, 26 May 2014 17:57:34 +0200, Jens Thoms Toerring wrote:
Thank you very much. Unfortunately, CPAN testing has shown
that there are some systems where there are problems building
the complete module.
The results
On Mon, 26 May 2014 22:41:13 +0200, Jens Thoms Toerring wrote:
Is there any chance of someone temporarily giving me an account
on a type of machine where the tests fail or
https://gcc.gnu.org/wiki/CompileFarm
https://dsa.debian.org/doc/guest-account/
might be possibilities.
at least of
On 26/05/14 22:11, gregor herrmann wrote:
On Mon, 26 May 2014 22:41:13 +0200, Jens Thoms Toerring wrote:
Is there any chance of someone temporarily giving me an account
on a type of machine where the tests fail or
https://gcc.gnu.org/wiki/CompileFarm
If it's of any use I do have an
Hi,
since I got no complaints about the new version of the
File::FcntlLock module I just uploaded it to CPAN. I hope
that it will help to avoid the problems you had with it.
Best regards, Jens
--
\ Jens Thoms Toerring j...@toerring.de
Hi,
thanks to your inputs I'm mostly through with a rework
of the File::FnctlLock module. It's now basically three
modules:
a) File::FcntlLock (or File::FcntlLock::XS as an alias) -
this is basically the old module, using XS,
b) File::FcntlLock::Pure - created during Perl Makefile.PL
On Sun, 2014-05-18 at 14:38:31 +0200, Jens Thoms Toerring wrote:
On Sun, May 18, 2014 at 06:04:45AM +0200, Guillem Jover wrote:
What about, preserving the XS module, and make the code try to load it
and if not available, fall back to the new pure perl code? I think that
would palliate such
Hi,
On Fri, May 16, 2014 at 11:06:17PM +0300, Niko Tyni wrote:
Would it be possible to probe for the contents of the flock struct with C
code at build time, and then use that information to write out a pure perl
module that regenerates the structs at run time (probably with pack())?
It
Hi!
On Sun, 2014-05-18 at 01:39:12 +0200, Jens Thoms Toerring wrote:
On Fri, May 16, 2014 at 11:06:17PM +0300, Niko Tyni wrote:
Would it be possible to probe for the contents of the flock struct with C
code at build time, and then use that information to write out a pure perl
module that
Hi!
On Fri, 2014-05-16 at 11:05:35 +0200, Jens Thoms Toerring wrote:
Long term what I think would be best would be to get File::FcntlLock
into the perl core distribution, preferably upstream, but I'm not sure
how such proposals are handled there and if something like that would
be
Hi,
On Fri, May 16, 2014 at 05:54:26PM +0200, Guillem Jover wrote:
... But they might argue that you already can get
fcntl(2) used for locking instead of flock(2) by building Perl with
-Ud_flock (don't ask me why that's not the default anyway;-)
Perhaps building the Perl version
On Fri, May 16, 2014 at 05:54:26PM +0200, Guillem Jover wrote:
On Fri, 2014-05-16 at 11:05:35 +0200, Jens Thoms Toerring wrote:
Long term what I think would be best would be to get File::FcntlLock
into the perl core distribution, preferably upstream, but I'm not sure
how such proposals
Hi,
On Fri, May 16, 2014 at 11:06:17PM +0300, Niko Tyni wrote:
Unfortunately, I also
don't see any way to do things without XS since the flock
structure that must be passed to fcntl(2) can be quite dif-
ferent on different systems, both concerning the number and
ordering of its
Hi,
On Tue, 13 May 2014, Gerfried Fuchs wrote:
This also affects a cowbuilder chroot and ends up in its build logs.
Either it is needed, then it should be a Depends, or not, then it
shouldn't blabber about it and end up in build logs.
Yes, installing something in a pbuilder/cowbuilder
[ CCed Jens and the Debian perl team for feedback on a proposal at
the bottom, leaving the rest for context. ]
Hi!
On Tue, 2014-05-13 at 17:08:24 +0200, Gerfried Fuchs wrote:
* Guillem Jover guil...@debian.org [2012-06-17 19:46:50 CEST]:
On Sun, 2012-06-17 at 13:02:31 +0200, Julien Cristau
On Wed, May 14, 2014 at 19:44:45 +0200, Guillem Jover wrote:
It is needed on NFS mounts, where the locks are going to be most needed,
as it's easier to get into a situation that several uncoordinate remote
systems are building the same thing in parallel, but those are also not
portably
* Guillem Jover guil...@debian.org [2012-06-17 19:46:50 CEST]:
On Sun, 2012-06-17 at 13:02:31 +0200, Julien Cristau wrote:
Package: dpkg-dev
Version: 1.16.4.2
Severity: normal
dpkg-gencontrol makes annoying noise like this:
dpkg-gencontrol: warning: File::FcntlLock not available;
Hi,
On Sun, 17 Jun 2012, Julien Cristau wrote:
On Sun, Jun 17, 2012 at 19:46:50 +0200, Guillem Jover wrote:
But you can silence it yourself, by installing libfile-fcntllock-perl,
or is that a problem?
I'm not installing anything I don't have to in any build chroot, no.
The only reason why
Package: dpkg-dev
Version: 1.16.4.2
Severity: normal
Hi,
dpkg-gencontrol makes annoying noise like this:
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is
not NFS-safe
Please silence it.
Cheers,
Julien
--
To UNSUBSCRIBE, email to
On Sun, 2012-06-17 at 13:02:31 +0200, Julien Cristau wrote:
Package: dpkg-dev
Version: 1.16.4.2
Severity: normal
dpkg-gencontrol makes annoying noise like this:
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is
not NFS-safe
Please silence it.
But you can
Guillem Jover wrote:
On Sun, 2012-06-17 at 13:02:31 +0200, Julien Cristau wrote:
dpkg-gencontrol makes annoying noise like this:
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which
is not NFS-safe
Please silence it.
But you can silence it yourself, by installing
33 matches
Mail list logo
