Your message dated Mon, 02 Dec 2024 15:16:24 +0100
with message-id <173314898442.377837.11239806373773519649@localhost>
and subject line Re: aspcud: can't find a solution with a new glibc
has caused the Debian Bug report #818120,
regarding aspcud resolver cannot find a solution with new glibc in experimental
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.)
--
818120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sbuild
Version: 0.68.0-1
Severity: normal
There a bunch of packages where aspcud can't find a solution. This
seems to be related to the new glibc in unstable. Possibly the old
libc is installed in the chroot and aspcud doesn't consider upgrading
it, though that's just a guess.
See https://buildd.debian.org/status/logs.php?pkg=gcc-6&ver=6-20160313-1
Cheers,
Emilio
--- End Message ---
--- Begin Message ---
Hi Emilio,
On Sun, 13 Mar 2016 22:58:04 +0100 Emilio Pozuelo Monfort <po...@debian.org>
wrote:
> There a bunch of packages where aspcud can't find a solution. This
> seems to be related to the new glibc in unstable. Possibly the old
> libc is installed in the chroot and aspcud doesn't consider upgrading
> it, though that's just a guess.
>
> See https://buildd.debian.org/status/logs.php?pkg=gcc-6&ver=6-20160313-1
has the problem occurred again during the past eight years of silence (sorry!)
in this bug report? If yes, please re-open this bug and we investigate again. I
cannot reproduce the issue locally.
Thanks!
cheers, josch
signature.asc
Description: signature
--- End Message ---
