Bug#794893: marked as done (nmu: cwidget_0.5.17-3.1 aptitude_0.7-1)
Your message dated Fri, 07 Aug 2015 19:46:20 +0100
with message-id <1438973180.24735.21.camel@adam-barratt.org.uk>
and subject line Re: Bug#794893: nmu: cwidget_0.5.17-3.1 aptitude_0.7-1
has caused the Debian Bug report #794893,
regarding nmu: cwidget_0.5.17-3.1 aptitude_0.7-1
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.)
--
794893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794893
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
I realise you don't want 3000 binNMU requests for the libstdc++ ABI
transitions; but this particular one breaks the amd64 experimental buildds,
which maintainers might be relying on for their ...v5 transitions,
so it seems worth speeding up. Please rebuild cwidget against
libsigc++-2.0-0v5, then rebuild aptitude against that:
nmu cwidget_0.5.17-3.1 . ALL . -m "rebuild against libsigc++-2.0-0v5"
nmu aptitude_0.7-1 . ALL . -m "rebuild against libsigc++-2.0-0v5"
dw aptitude_0.7-1 . ALL . -m "libcwidget3v5 (>= 0.5.17-3.1+b1)"
This is currently affecting all the amd64 experimental buildds, for instance
<https://buildd.debian.org/status/logs.php?pkg=dbus&ver=1.9.20-1&arch=amd64>
(which was successful on all other architectures). However, if there's
some subtle ABI issue, it seems safer to rebuild everywhere.
I can reproduce the sbuild failure locally when using
"--build-dep-resolver=aptitude", which I think is what the official
experimental buildds do. When I rebuild cwidget in an unstable sbuild,
rebuild aptitude with the new cwidget added via --extra-package, then
build dbus in an experimental sbuild with the updated cwidget and aptitude,
the dbus build succeeds. New cwidget + old aptitude is not sufficient
(aptitude becomes uninstallable).
Fixing this should hopefully mean people can use pbuilder again, too.
Regards,
S
--- End Message ---
--- Begin Message ---
On Fri, 2015-08-07 at 19:24 +0100, Simon McVittie wrote:
> I realise you don't want 3000 binNMU requests for the libstdc++ ABI
> transitions; but this particular one breaks the amd64 experimental buildds,
> which maintainers might be relying on for their ...v5 transitions,
> so it seems worth speeding up. Please rebuild cwidget against
> libsigc++-2.0-0v5, then rebuild aptitude against that:
>
> nmu cwidget_0.5.17-3.1 . ALL . -m "rebuild against libsigc++-2.0-0v5"
> nmu aptitude_0.7-1 . ALL . -m "rebuild against libsigc++-2.0-0v5"
> dw aptitude_0.7-1 . ALL . -m "libcwidget3v5 (>= 0.5.17-3.1+b1)"
Scheduled.
Regards,
Adam
--- End Message ---
Reply to: