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

Bug#953735: marked as done (nmu: unscd_0.53-1+b2)

Your message dated Fri, 13 Mar 2020 11:09:15 +0100
with message-id <c182688b-a781-5aa3-121f-2b1868bcc062@debian.org>
and subject line Re: Bug#953735: nmu: unscd_0.53-1+b2
has caused the Debian Bug report #953735,
regarding nmu: unscd_0.53-1+b2
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.)


-- 
953735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953735
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

nmu unscd_0.53-1+b2 . ANY . unstable . -m "Rebuild against glibc 2.30"

As usual with new glibc major versions, please binNMU unscd quickly,
not having it prevents the installation of the new libc.

An extra versioned B-D, so that architectures where glibc 2.30 FTBFS
(ia64, kfreebsd-amd64, kfreebsd-i386, sparc64) wait with the binNMU
until it’s fixed, would be appreciated.

-- System Information:
Debian Release: bullseye/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-4-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

--- End Message ---
--- Begin Message --- 
On 12/03/2020 19:13, Thorsten Glaser wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: binnmu
> 
> nmu unscd_0.53-1+b2 . ANY . unstable . -m "Rebuild against glibc 2.30"
> 
> As usual with new glibc major versions, please binNMU unscd quickly,
> not having it prevents the installation of the new libc.

Done.

> An extra versioned B-D, so that architectures where glibc 2.30 FTBFS
> (ia64, kfreebsd-amd64, kfreebsd-i386, sparc64) wait with the binNMU
> until it’s fixed, would be appreciated.

Not just that. An extra-depends is also needed so that we get the new glibc in
the chroots. That extra-depends will cause the build-dep where it can't be
satisfied at the moment.

Cheers,
Emilio

--- End Message ---
Reply to: