On Wed, Aug 10, 2011 at 02:58:07PM -0500, Jonathan Nieder wrote:
Niko Tyni wrote:
Looks like dpkg tries to sync /usr/bin/perl5.12.4.dpkg-new when a hard
link has already been renamed to /usr/bin/perl and presumably gotten
executed by someone else.
Does this help?
+ * Open extracted
Hi!
On Fri, 2011-08-12 at 13:33:22 +0300, Niko Tyni wrote:
On Wed, Aug 10, 2011 at 02:58:07PM -0500, Jonathan Nieder wrote:
Niko Tyni wrote:
Looks like dpkg tries to sync /usr/bin/perl5.12.4.dpkg-new when a hard
link has already been renamed to /usr/bin/perl and presumably gotten
On Fri, 12 Aug 2011, Niko Tyni wrote:
However, are sync_file_range() and fsync() effective with an O_RDONLY
file descriptor? From fsync(2):
EBADF fd is not a valid file descriptor open for writing.
but https://bugzilla.kernel.org/show_bug.cgi?id=29972 suggests this is
Niko Tyni wrote:
From fsync(2):
EBADF fd is not a valid file descriptor open for writing.
*digs* Looks like that description was added between man-pages-1.10
(16-Jan-1996) and man-pages-1.11 (15-Apr-1996). From a look at Linux
0.99.10, I think fsync has just looked at the dirent and
Guillem Jover wrote:
This is misleading on Linux, but it's not a safe portable assumption
to make on POSIX in general as that behaviour is not specified and as
such is implementation specific, some Unix systems do actually fail
on read-only file descriptors, for example:
On Fri, 12 Aug 2011, Guillem Jover wrote:
This is misleading on Linux, but it's not a safe portable assumption
to make on POSIX in general as that behaviour is not specified and as
such is implementation specific, some Unix systems do actually fail
on read-only file descriptors, for example:
On Fri, 2011-08-12 at 21:10:20 +0200, Raphael Hertzog wrote:
On Fri, 12 Aug 2011, Guillem Jover wrote:
This is misleading on Linux, but it's not a safe portable assumption
to make on POSIX in general as that behaviour is not specified and as
such is implementation specific, some Unix
On Wed, Aug 10, 2011 at 06:28:39PM +0200, Peter Gervai wrote:
So, I have sid not updated for a few weeks now. Needed to update perl
from 5.12.4-1 to 5.12.4-2, and got the following:
dpkg: error processing
/var/cache/apt/archives/perl-base_5.12.4-2_i386.deb (--install):
unable to open
Thanks Niko for commenting, I have met this report but since it was
kicked away with fixed in later I didn't dare to touch.
My dpkg is 1.16.0.3
peter
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hi,
Niko Tyni wrote:
Looks like dpkg tries to sync /usr/bin/perl5.12.4.dpkg-new when a hard
link has already been renamed to /usr/bin/perl and presumably gotten
executed by someone else.
Ah, fun. :)
Does this help?
---
debian/changelog |6 ++
src/archives.c |4 ++--
2 files
10 matches
Mail list logo
