[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#980084: marked as done (nmu: binNMUs for statically linked binaries built with glibc (<< 2.31))

Your message dated Mon, 18 Jan 2021 22:53:15 +0100
with message-id <YAYDS5/xVqesAI9O@aurel32.net>
and subject line Re: Bug#980084: nmu: binNMUs for statically linked binaries built with glibc (<< 2.31)
has caused the Debian Bug report #980084,
regarding nmu: binNMUs for statically linked binaries built with glibc (<< 2.31)
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.)


-- 
980084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980084
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu

Dear release team,

Now that (build-)essential is frozen, the glibc package will only see
minor changes up to the bullseye release. I therefore think it's the
good moment to binNMUs packages with binaries statically linked against
older versions of glibc. This will reduce the number of glibc versions
shipped in bullseye and gives time ahead of the release to find possible
issues that could be introduced by this rebuilds (the autopkgtests can't
detect issues due to the statically linkage).

Here is a first list of binNMUs for packages built using glibc (<< 2.31):

nmu aide_0.16.1-1 . ANY . -m "Rebuild against latest glibc" # currently 2.28-8
nmu cdebootstrap_0.7.7 . ANY . -m "Rebuild against latest glibc" # currently 2.28-10
nmu prelink_0.0.20131005-1.1 . ANY . -m "Rebuild against latest glibc" # currently 2.30-4
nmu sash_3.8-5 . ANY . -m "Rebuild against latest glibc" # currently 2.28-8
nmu tripwire_2.4.3.7-3 . ANY . -m "Rebuild against latest glibc" # currently 2.30-4
nmu zsh_5.8-5 . ANY . -m "Rebuild against latest glibc" # currently 2.30-8
nmu zutils_1.9-1 . ANY . -m "Rebuild against latest glibc" # currently 2.30-8

The are a few other packages not built with the latest glibc, but they
are at least built with glibc (>= 2.31-3). I think we can binNMU them
later in the release process, as there might be a new glibc upload or
they might also get uploaded in the meantime.

Regards,
Aurelien

--- End Message ---
--- Begin Message --- 
Hi Sebastian,

On 2021-01-17 11:38, Sebastian Ramacher wrote:
> On 2021-01-14 10:53:57 +0100, Aurelien Jarno wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian.org@packages.debian.org
> > Usertags: binnmu
> > 
> > Dear release team,
> > 
> > Now that (build-)essential is frozen, the glibc package will only see
> > minor changes up to the bullseye release. I therefore think it's the
> > good moment to binNMUs packages with binaries statically linked against
> > older versions of glibc. This will reduce the number of glibc versions
> > shipped in bullseye and gives time ahead of the release to find possible
> > issues that could be introduced by this rebuilds (the autopkgtests can't
> > detect issues due to the statically linkage).
> > 
> > Here is a first list of binNMUs for packages built using glibc (<< 2.31):
> > 
> > nmu aide_0.16.1-1 . ANY . -m "Rebuild against latest glibc" # currently 2.28-8
> > nmu cdebootstrap_0.7.7 . ANY . -m "Rebuild against latest glibc" # currently 2.28-10
> > nmu prelink_0.0.20131005-1.1 . ANY . -m "Rebuild against latest glibc" # currently 2.30-4
> > nmu sash_3.8-5 . ANY . -m "Rebuild against latest glibc" # currently 2.28-8
> > nmu tripwire_2.4.3.7-3 . ANY . -m "Rebuild against latest glibc" # currently 2.30-4
> > nmu zsh_5.8-5 . ANY . -m "Rebuild against latest glibc" # currently 2.30-8
> > nmu zutils_1.9-1 . ANY . -m "Rebuild against latest glibc" # currently 2.30-8
> 
> Thanks, scheduled

Thanks, they all built fine and migrated to testing. I am therefore
closing the bug.

Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: