Your message dated Sat, 26 Nov 2016 15:11:21 +0100
with message-id <20161126141121.u2qbvmrst7rea...@aurel32.net>
and subject line Re: Bug#845721: Cannot install libc6:i386 -- Breaks:
libc6:i386 (!= 2.24-7) but -7 does not exist
has caused the Debian Bug report #845721,
regarding Cannot install libc6:i386 -- Breaks: libc6:i386 (!= 2.24-7) but -7
does not exist
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
845721: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.24-7
Severity: normal
Tried to install libc6:i386 but cannot.
$ sudo apt-get install libc6:i386
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:
cli-common : Depends: perl but it is not going to be installed
libc6 : Breaks: libc6:i386 (!= 2.24-7) but 2.24-5 is to be installed
libc6:i386 : Breaks: libc6 (!= 2.24-5) but 2.24-7 is to be installed
[...]
I don't know how to make sense of these "breaks" versions. libc6
doesn't even have a revision -7. Should both of those be
"breaks ... != 2.24-6"?
-Steve
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libc6 depends on:
ii libgcc1 1:6.2.1-5
libc6 recommends no packages.
Versions of packages libc6 suggests:
ii cdebconf [debconf-2.0] 0.219
ii debconf [debconf-2.0] 1.5.59
ii glibc-doc 2.24-7
ii libc-l10n 2.24-7
ii locales 2.24-7
-- debconf information:
* glibc/disable-screensaver:
glibc/kernel-too-old:
* glibc/upgrade: true
* glibc/restart-services: spamassassin samba openbsd-inetd exim4 cron atd
apache2
glibc/kernel-not-supported:
glibc/restart-failed:
* libraries/restart-without-asking: true
--- End Message ---
--- Begin Message ---
On 2016-11-26 11:02, Adam D. Barratt wrote:
> On Sat, 2016-11-26 at 01:02 -0600, Steve M. Robbins wrote:
> > The following packages have unmet dependencies:
> > cli-common : Depends: perl but it is not going to be installed
> > libc6 : Breaks: libc6:i386 (!= 2.24-7) but 2.24-5 is to be installed
> > libc6:i386 : Breaks: libc6 (!= 2.24-5) but 2.24-7 is to be installed
> > [...]
>
> That normally means that apt is seeing libc6 2.24-7 as available on
> amd64 and 2.24-5 as available on i386 and is refusing to install the
> combination, as they're different versions and libc6 is marked
> Multi-Arch:same.
>
> > I don't know how to make sense of these "breaks" versions. libc6
> > doesn't even have a revision -7. Should both of those be
> > "breaks ... != 2.24-6"?
>
> -7 was uploaded a little over 10 hours ago. Looking at the dak log that
> would make sense in terms of what you're seeing - the amd64 build of -7
> made it into the 0152UTC dinstall by a few minutes, so would have been
> available on mirrors when you filed this report, with the i386 build
> being part of the subsequent 0752 dinstall.
glibc version 2.24-7 is now available on the mirrors for both amd64 and
i386. I am therefore closing the bug.
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
--- End Message ---
