Bug#808444: marked as done (nmu: boost1.58_1.58.0+dfsg-4.1)
Your message dated Sun, 20 Dec 2015 14:00:30 +0100
with message-id <5676A66E.8090009@debian.org>
and subject line Re: Bug#808444: nmu: boost1.58_1.58.0+dfsg-4.1
has caused the Debian Bug report #808444,
regarding nmu: boost1.58_1.58.0+dfsg-4.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.)
--
808444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808444
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
Control: block 796345 with -1
libboost-mpi1.58.0 is currently uninstallable on s390x (and probably on a
few non-release archs like hppa and m68k too) because of changes in mpich:
mpich (3.2-1~exp1) experimental; urgency=medium
* Add libmpl1/libopa1 to Breaks/Replaces for libmpich12, since it replaces those
which entered sid recently.
The uninstallability is specific to architectures without openmpi
(#376833 et al.), and is preventing slic3r to be rebuilt for the Perl
5.22 transition.
I rebuilt boost1.58 on s390x manually and it looks like that fixes the issue,
so a binNMU should be enough.
nmu boost1.58_1.58.0+dfsg-4.1 . s390x . unstable . -m "rebuild for mpich changes"
However, I see this probably applies to other packages too. On zelenka.d.o sid chroot:
grep-dctrl -FDepends libmpich12 /var/lib/apt/lists/debian.netcologne.de_debian_dists_sid_main_binary-s390x_Packages|grep-dctrl -sSource:Package -FDepends -w libopa1|sort -u|wc -l
47
so perhaps it needs a proper transition tracker or something...
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Ccing Anton.
On 20/12/15 10:36, Niko Tyni wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: binnmu
> Control: block 796345 with -1
>
> libboost-mpi1.58.0 is currently uninstallable on s390x (and probably on a
> few non-release archs like hppa and m68k too) because of changes in mpich:
>
> mpich (3.2-1~exp1) experimental; urgency=medium
>
> * Add libmpl1/libopa1 to Breaks/Replaces for libmpich12, since it replaces those
>
> which entered sid recently.
>
> The uninstallability is specific to architectures without openmpi
> (#376833 et al.), and is preventing slic3r to be rebuilt for the Perl
> 5.22 transition.
>
> I rebuilt boost1.58 on s390x manually and it looks like that fixes the issue,
> so a binNMU should be enough.
>
> nmu boost1.58_1.58.0+dfsg-4.1 . s390x . unstable . -m "rebuild for mpich changes"
Scheduled.
> However, I see this probably applies to other packages too. On zelenka.d.o sid chroot:
>
> grep-dctrl -FDepends libmpich12 /var/lib/apt/lists/debian.netcologne.de_debian_dists_sid_main_binary-s390x_Packages|grep-dctrl -sSource:Package -FDepends -w libopa1|sort -u|wc -l
> 47
>
> so perhaps it needs a proper transition tracker or something...
Anton, what do you think about this?
Cheers,
Emilio
--- End Message ---
Reply to: