Your message dated Tue, 4 Dec 2007 08:27:50 +0200
with message-id <[EMAIL PROTECTED]>
and subject line fixed in experimental
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libxml-sax-perl
Version: 0.12-5
Severity: normal
In the process of doing an apt-get upgrade, 5 pages won't install. I
believe libxml-sax-perl is probably the reason, but no good evidence of
it.
libxml-sax-perl
libxml-filter-buffertext-perl
libxml-sax-writer-perl
libxml-filter-xslt-perl
libxml-sax-expat-perl
Are the packages in question. There seems to be problems involving
/etc/perl/XML/SAX/ParserDetails.d/. Sometimes the problem looks like
the partial directory XML/SAX, sometimes it is the absence of the
directory, so that it (dpkg install process) can't write to some file in
that directory.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.27
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages libxml-sax-perl depends on:
ii libxml-namespacesupport-perl 1.08-3 Perl module for supporting simple
ii perl 5.8.4-3 Larry Wall's Practical Extraction
-- no debconf information
--- End Message ---
--- Begin Message ---
Package: libxml-sax-perl
Version: 0.16+dfsg-1
Hi,
although I can't recreate this exact way of failing on upgrades anymore
(my guess is a symlink somewhere in /etc/XML, /etc/perl/XML or so on),
it should be fixed in the current version in experimental, 0.16+dfsg-1.
The preinst maintainer script doesn't try to move the ParserDetails.d
directory around anymore, which was clearly the cause of the problem.
I'm closing the bug, feel free to reopen if there are still issues.
The fixed version should make it into unstable soon as well.
Cheers,
--
Niko Tyni [EMAIL PROTECTED]
--- End Message ---
