Bug#806695: marked as done (libc6: Why still working on 2.21 in experimental instead of 2.22?)
Your message dated Mon, 30 Nov 2015 09:34:29 +0100
with message-id <20151130083429.GB3751@aurel32.net>
and subject line Re: Bug#806695: libc6: Why still working on 2.21 in experimental instead of 2.22?
has caused the Debian Bug report #806695,
regarding libc6: Why still working on 2.21 in experimental instead of 2.22?
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 owner@bugs.debian.org
immediately.)
--
806695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806695
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.21-0experimental4
Severity: wishlist
I do see activity in glibc on experimental but still on glibC 2.21.
Any reason to not jump at 2.22?
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.1.13 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
Versions of packages libc6 depends on:
ii libgcc1 1:5.2.1-26
libc6 recommends no packages.
Versions of packages libc6 suggests:
ii debconf [debconf-2.0] 1.5.58
ii glibc-doc 2.21-0experimental4
ii libc-l10n 2.21-0experimental4
ii locales 2.21-0experimental4
-- debconf information:
* glibc/disable-screensaver:
glibc/restart-failed:
* glibc/upgrade: true
* libraries/restart-without-asking: true
glibc/restart-services:
--- End Message ---
--- Begin Message ---
On 2015-11-30 08:51, Eric Valette wrote:
> Package: libc6
> Version: 2.21-0experimental4
> Severity: wishlist
>
> I do see activity in glibc on experimental but still on glibC 2.21.
> Any reason to not jump at 2.22?
Yes. For the toolchain it's easier to go incrementally than skip too
many versions. It helps in finding regression.
Aurelien
PS: You don't need to open a bug for such questions. Closing the bug.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
--- End Message ---
Reply to: