Your message dated Sat, 31 Oct 2015 15:07:58 +0100 with message-id <5634CB3E.9060906@debian.org> and subject line Re: Bug#798198: nmu: psi4_4.0~beta5+dfsg-2 has caused the Debian Bug report #798198, regarding nmu: psi4_4.0~beta5+dfsg-2 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.) -- 798198: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798198 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: nmu: psi4_4.0~beta5+dfsg-2
- From: Peter Green <plugwash@debian.org>
- Date: Sun, 06 Sep 2015 18:32:39 +0100
- Message-id: <55EC78B7.2020105@debian.org>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: binnmu There were problems with using psi4 built with gcc-4.9 with a gcc-5libstdc++6. As a result a breaks was added to libstdc++6 and psi4 was binnmu'd.However the binnmus on arm64 and ppc64el were built with a +b1 suffix while those on other architectures were built with a +b2 suffix. Since the breaks is declared on psi4 (<= 4.0~beta5+dfsg-2+b1) this means that the package is uninstallable on arm64 and ppc64el.I think the neatest solution is to re-binnmu the package onarm64 and ppc64el and hence bring the binnmu suffix back into sync across all release architectures and make the package installable on arm64 and ppc64el.nmu innoextract_1.4-1 . arm64 ppc64el . -m "Rebuild for the gcc5 transition."-- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.14-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
- To: Peter Green <plugwash@debian.org>, 798198-done@bugs.debian.org
- Subject: Re: Bug#798198: nmu: psi4_4.0~beta5+dfsg-2
- From: Emilio Pozuelo Monfort <pochu@debian.org>
- Date: Sat, 31 Oct 2015 15:07:58 +0100
- Message-id: <5634CB3E.9060906@debian.org>
- In-reply-to: <55EC78B7.2020105@debian.org>
- References: <55EC78B7.2020105@debian.org>
On 06/09/15 19:32, Peter Green wrote: > Package: release.debian.org > Severity: normal > User: release.debian.org@packages.debian.org > Usertags: binnmu > > There were problems with using psi4 built with gcc-4.9 with a gcc-5 > libstdc++6. As a result a breaks was added to libstdc++6 and psi4 was binnmu'd. > > However the binnmus on arm64 and ppc64el were built with a +b1 suffix while > those on other architectures were built with a +b2 suffix. Since the breaks is > declared on psi4 (<= 4.0~beta5+dfsg-2+b1) this means that the package is > uninstallable on arm64 and ppc64el. > > I think the neatest solution is to re-binnmu the package on > arm64 and ppc64el and hence bring the binnmu suffix back into sync across all > release architectures and make the package installable on arm64 and ppc64el. > > nmu innoextract_1.4-1 . arm64 ppc64el . -m "Rebuild for the gcc5 transition." Sorry for the delay. There has been a maintainer upload in the meantime. Closing. Cheers, Emilio
--- End Message ---