--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: transition: eglibc
- From: Aurelien Jarno <aurel32@debian.org>
- Date: Sat, 31 May 2014 21:09:12 +0200
- Message-id: <20140531190912.3404.24814.reportbug@volta.rr44.fr>
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
Dear release team,
We would like to get a transition slot for eglibc 2.19. It is currently
uploaded in experimental and has been built successfully on all
architectures except armel and armhf. We have done manual builds on
these architectures and they have been successful.
As the libc is using symbol versioning, there is no soname change. That
said a few packages are using libc internal symbols and have to be
rebuilt for this transition:
- dante
- libnih
- libnss-db
- unscd
In addition it should be noted that a few new symbols have been added
that might prevent a few other packages to transition to testing if they
pick up the new symbols. This time the amount of new symbols is quite
limited, so it should not concern a lot of packages:
- getrlimit64 and setrlimit64 on mips and mipsel
- longjmp, __longjmp_chk, siglongjmp, sigsetjmp, setjmp and getcontext
on s390x
Thanks,
Aurelien
Ben file:
title = "eglibc";
is_affected = .depends ~ "/libc[0-9.]* \(<</";
is_good = .depends ~ "/libc[0-9.]* \(<< 2.20\)/";
is_bad = .depends ~ "/libc[0-9.]* \(<< 2.19\)/";
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
On 04/06/14 22:13, Aurelien Jarno wrote:
> On Wed, Jun 04, 2014 at 01:17:06PM +0200, Emilio Pozuelo Monfort wrote:
>> Control: tags -1 confirmed
>>
>> On 31/05/14 21:09, Aurelien Jarno wrote:
>>> We would like to get a transition slot for eglibc 2.19. It is currently
>>> uploaded in experimental and has been built successfully on all
>>> architectures except armel and armhf. We have done manual builds on
>>> these architectures and they have been successful.
>>
>> Please go ahead.
>
> Thanks, I have just uploaded it.
And it's in! Closing.
Emilio
--- End Message ---