Your message dated Thu, 28 Jun 2007 18:32:40 -0700
with message-id <[EMAIL PROTECTED]>
and subject line now affects unstable too
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: libapt-pkg-perl
Version: 0.2.3-4
Severity: important
Tags: experimental
debian:/# apt-get install apt-file
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
apt-file: Depends: libapt-pkg-perl but it is not going to be installed
E: Broken packages
debian:/#
debian:/# apt-get install apt-file libapt-pkg-perl
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libapt-pkg-perl: Depends: libapt-pkg-libc6.3-6-3.11
E: Broken packages
debian:/#
debian:/# apt-get install apt-file libapt-pkg-perl libapt-pkg-libc6.3-6-3.11
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting apt instead of libapt-pkg-libc6.3-6-3.11
apt is already the newest version.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libapt-pkg-perl: Depends: libapt-pkg-libc6.3-6-3.11
E: Broken packages
debian:/#
debian:/# apt-get install libapt-pkg-perl libapt-pkg-libc6.3-6-3.11
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting apt instead of libapt-pkg-libc6.3-6-3.11
apt is already the newest version.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libapt-pkg-perl: Depends: libapt-pkg-libc6.3-6-3.11
E: Broken packages
debian:/#
-- System Information:
Debian Release: 4.0
APT prefers experimental
APT policy: (990, 'experimental'), (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-skas3-v9-pre9
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=locale: Cannot set LC_CTYPE to
default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
--- End Message ---
--- Begin Message ---
On Tue, Jun 12, 2007 at 01:59:02PM +0100, peter green wrote:
> retitle 414944 libapt-pkg-perl and hence apt-file are uninstallable on
> systems that preffer unstable
> severity 414944 grave
> CCing debian-release because a binnmu should be enough to fix this.
There has already been a maintainer upload of this package against the
unstable version of apt, so this looks to me like it's resolved.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
--- End Message ---
