Bug#910977: transition: atlas-cpp
Followup-For: Bug #910977 nmu eris_1.3.23-7 . hurd-i386 kfreebsd-amd64 kfreebsd-i386 . unstable . -m "Rebuild against libatlas-cpp-0.6-3." The atlas-cpp builds were not yet available on these architectures at the time the other architectures were binNMUed. Andreas
Bug#913210: transition: libqalculate
On Wed, Nov 21, 2018 at 12:59:31PM +0100, Emilio Pozuelo Monfort wrote : > Control: tags -1 confirmed > > On 08/11/2018 07:12, Vincent Legout wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: transition > > > > Hello, > > > > I'd like to request a transition slot for libqalculate. > > > > The new version is in experimental. It has 4 reverse dependencies. > > qalculate-gtk has also been uploaded to experimental, and I plan to > > upload it to unstable just after libqalculate. The other 3 build fine > > with the new version. > > Go ahead. Thanks. libqalculate and qalculate-gtk have both been uploaded to unstable. Would it be possible to schedule rebuilds for the remaining reverse dependencies please? (cantor plasma-workspace step) Vincent
Bug#914662: transition: hypre
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition With the hdf5 transition completed, I'd like to proceed with the hypre transition from 2.14.0 to 2.15.1. I've updated hypre packaging to remove circular dependencies between libHYPRE sublibraries. petsc and sundials will build and pass tests with a trivial fix to handle the new hypre libraries. FYI: a transition of petsc/slepc from 3.9 to 3.10 will follow, subject to being able to fix the petsc FTBFS (memory exhausted) on mips. Ben file: title = "hypre"; is_affected = .depends ~ "libhypre-2.14.0" | .depends ~ "libhypre-2.15.1"; is_good = .depends ~ "libhypre-2.15.1"; is_bad = .depends ~ "libhypre-2.14.0"; -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#914631: nmu: mpb_1.5-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu mpb_1.5-3 . ANY . unstable . -m "Merged /usr considered harmful" $ mpb-split bash: /usr/bin/mpb-split: /usr/bin/bash: bad interpreter: No such file or directory $
Bug#914611: transition: yaml-cpp
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition After discussion in #debian-release last week, I NMUed yaml-cpp with an SONAME bump to fix bug #914190. We need to binNMU the reverse dependencies listed in the transition tracker for that: https://release.debian.org/transitions/html/auto-yaml-cpp.html Ben file: title = "yaml-cpp"; is_affected = .depends ~ /\b(libyaml\-cpp0\.5v5)\b/ | .depends ~ /\b(libyaml\-cpp0\.5d1)\b/; is_good = .depends ~ /\b(libyaml\-cpp0\.5d1)\b/; is_bad = .depends ~ /\b(libyaml\-cpp0\.5v5)\b/; -- System Information: Debian Release: buster/sid APT prefers disco APT policy: (500, 'disco'), (100, 'disco-proposed') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-11-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Bug#914603: marked as done (nmu: mpich_3.3-1)
Your message dated Sun, 25 Nov 2018 17:56:27 +0100 with message-id <20181125165626.yqqch6emzj67l...@debian.org> and subject line Re: nmu: mpich_3.3-1 has caused the Debian Bug report #914603, regarding nmu: mpich_3.3-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 ow...@bugs.debian.org immediately.) -- 914603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914603 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu mpich_3.3-1 . ANY . unstable . -m "Merged /usr considered harmful" $ mpicc.mpich bash: /usr/bin/mpicc.mpich: /usr/bin/bash: bad interpreter: No such file or directory $ Multi-Arch: same, so needs rebuild on all architectures. --- End Message --- --- Begin Message --- Hi, On Sun, Nov 25, 2018 at 05:43:27PM +0200, Adrian Bunk wrote: > nmu mpich_3.3-1 . ANY . unstable . -m "Merged /usr considered harmful" > > $ mpicc.mpich > bash: /usr/bin/mpicc.mpich: /usr/bin/bash: bad interpreter: No such file or > directory > $ > > Multi-Arch: same, so needs rebuild on all architectures. Scheduled. Ivo--- End Message ---
Bug#914603: nmu: mpich_3.3-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu mpich_3.3-1 . ANY . unstable . -m "Merged /usr considered harmful" $ mpicc.mpich bash: /usr/bin/mpicc.mpich: /usr/bin/bash: bad interpreter: No such file or directory $ Multi-Arch: same, so needs rebuild on all architectures.
Bug#914594: stretch-pu, jessie-pu: package ssh-agent-filter/0.4.2-1,0.4-2
Control: tags -1 - jessie Control: retitle -1 stretch-pu: package ssh-agent-filter/0.4.2-1 On Sun, 2018-11-25 at 14:26 +0100, Timo Weingärtner wrote: > Package: release.debian.org > User: release.debian@packages.debian.org > Usertags: pu > Tags: stretch jessie > Severity: normal > > bug with potential security implications, see > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914501 The Release Team hasn't handled updates to jessie for nearly 6 months now - see https://www.debian.org/News/2018/20180623 (and even when it did, updates to multiple suites have always required separate bugs). Regards, Adam
Processed: Re: Bug#914594: stretch-pu, jessie-pu: package ssh-agent-filter/0.4.2-1,0.4-2
Processing control commands: > tags -1 - jessie Bug #914594 [release.debian.org] stretch-pu, jessie-pu: package ssh-agent-filter/0.4.2-1,0.4-2 Removed tag(s) jessie. > retitle -1 stretch-pu: package ssh-agent-filter/0.4.2-1 Bug #914594 [release.debian.org] stretch-pu, jessie-pu: package ssh-agent-filter/0.4.2-1,0.4-2 Changed Bug title to 'stretch-pu: package ssh-agent-filter/0.4.2-1' from 'stretch-pu, jessie-pu: package ssh-agent-filter/0.4.2-1,0.4-2'. -- 914594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914594 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914594: stretch-pu, jessie-pu: package ssh-agent-filter/0.4.2-1,0.4-2
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: stretch jessie
Severity: normal
bug with potential security implications, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914501
diff -Nru ssh-agent-filter-0.4.2/debian/changelog ssh-agent-filter-0.4.2/debian/changelog
--- ssh-agent-filter-0.4.2/debian/changelog 2016-08-27 23:36:56.0 +0200
+++ ssh-agent-filter-0.4.2/debian/changelog 2018-11-24 01:46:12.0 +0100
@@ -1,3 +1,9 @@
+ssh-agent-filter (0.4.2-1+deb9u1) stretch; urgency=medium
+
+ * backport fix for two-byte out-of-bounds stack write (Closes: #914501)
+
+ -- Timo Weingärtner Sat, 24 Nov 2018 01:46:12 +0100
+
ssh-agent-filter (0.4.2-1) unstable; urgency=medium
* New upstream release:
diff -Nru ssh-agent-filter-0.4.2/debian/gbp.conf ssh-agent-filter-0.4.2/debian/gbp.conf
--- ssh-agent-filter-0.4.2/debian/gbp.conf 2016-08-27 23:36:56.0 +0200
+++ ssh-agent-filter-0.4.2/debian/gbp.conf 2018-11-24 01:46:12.0 +0100
@@ -1,5 +1,5 @@
[DEFAULT]
upstream-branch=master
upstream-tag=%(version)s
-debian-branch=debian
+debian-branch=debian-stretch
pristine-tar=true
diff -Nru ssh-agent-filter-0.4.2/debian/patches/914501_fix_two-byte_oob_stack_write ssh-agent-filter-0.4.2/debian/patches/914501_fix_two-byte_oob_stack_write
--- ssh-agent-filter-0.4.2/debian/patches/914501_fix_two-byte_oob_stack_write 1970-01-01 01:00:00.0 +0100
+++ ssh-agent-filter-0.4.2/debian/patches/914501_fix_two-byte_oob_stack_write 2018-11-24 01:46:12.0 +0100
@@ -0,0 +1,26 @@
+Description: fix two-byte out-of-bounds stack write
+ BASE64_ENCODE_LENGTH() calculates the encoded size without padding
+Author: Timo Weingärtner
+Origin: upstream, https://git.tiwe.de/ssh-agent-filter.git/commit/?id=87f2de93a6522bbcf17d1960e78641df8ecd85d3
+Bug-Debian: https://bugs.debian.org/914501
+Forwarded: not-needed
+Last-Update: 2018-11-24
+
+--- ssh-agent-filter-0.4.2.orig/ssh-agent-filter.C
ssh-agent-filter-0.4.2/ssh-agent-filter.C
+@@ -116,12 +116,9 @@ string md5_hex (string const & s) {
+ }
+
+ string base64_encode (string const & s) {
+- struct base64_encode_ctx ctx;
+- base64_encode_init();
+- uint8_t b64[BASE64_ENCODE_LENGTH(s.size())];
+- auto len = base64_encode_update(, b64, s.size(), reinterpret_cast(s.data()));
+- len += base64_encode_final(, b64 + len);
+- return {reinterpret_cast(b64), len};
++ uint8_t b64[BASE64_ENCODE_RAW_LENGTH(s.size())];
++ base64_encode_raw(b64, s.size(), reinterpret_cast(s.data()));
++ return {reinterpret_cast(b64), sizeof(b64)};
+ }
+
+ void cloexec (int fd) {
diff -Nru ssh-agent-filter-0.4.2/debian/patches/series ssh-agent-filter-0.4.2/debian/patches/series
--- ssh-agent-filter-0.4.2/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ ssh-agent-filter-0.4.2/debian/patches/series 2018-11-24 01:46:12.0 +0100
@@ -0,0 +1 @@
+914501_fix_two-byte_oob_stack_write
diff -Nru ssh-agent-filter-0.4/debian/changelog ssh-agent-filter-0.4/debian/changelog
--- ssh-agent-filter-0.4/debian/changelog 2014-10-21 17:40:14.0 +0200
+++ ssh-agent-filter-0.4/debian/changelog 2018-11-24 02:01:09.0 +0100
@@ -1,3 +1,9 @@
+ssh-agent-filter (0.4-2+deb8u1) jessie; urgency=medium
+
+ * backport fix for two-byte out-of-bounds stack write (Closes: #914501)
+
+ -- Timo Weingärtner Sat, 24 Nov 2018 02:01:09 +0100
+
ssh-agent-filter (0.4-2) unstable; urgency=medium
* add debian/patches/0001-workaround-FTBFS-caused-by-doko:
diff -Nru ssh-agent-filter-0.4/debian/gbp.conf ssh-agent-filter-0.4/debian/gbp.conf
--- ssh-agent-filter-0.4/debian/gbp.conf 2014-10-21 17:40:14.0 +0200
+++ ssh-agent-filter-0.4/debian/gbp.conf 2018-11-24 02:01:09.0 +0100
@@ -1,5 +1,5 @@
[DEFAULT]
upstream-branch=master
upstream-tag=%(version)s
-debian-branch=debian
+debian-branch=debian-jessie
pristine-tar=true
diff -Nru ssh-agent-filter-0.4/debian/patches/914501_fix_two-byte_oob_stack_write ssh-agent-filter-0.4/debian/patches/914501_fix_two-byte_oob_stack_write
--- ssh-agent-filter-0.4/debian/patches/914501_fix_two-byte_oob_stack_write 1970-01-01 01:00:00.0 +0100
+++ ssh-agent-filter-0.4/debian/patches/914501_fix_two-byte_oob_stack_write 2018-11-24 02:01:09.0 +0100
@@ -0,0 +1,26 @@
+Description: fix two-byte out-of-bounds stack write
+ BASE64_ENCODE_LENGTH() calculates the encoded size without padding
+Author: Timo Weingärtner
+Origin: upstream, https://git.tiwe.de/ssh-agent-filter.git/commit/?id=87f2de93a6522bbcf17d1960e78641df8ecd85d3
+Bug-Debian: https://bugs.debian.org/914501
+Forwarded: not-needed
+Last-Update: 2018-11-24
+
+--- ssh-agent-filter-0.4.2.orig/ssh-agent-filter.C
ssh-agent-filter-0.4.2/ssh-agent-filter.C
+@@ -116,12 +116,9 @@ string md5_hex (string const & s) {
+ }
+
+ string base64_encode (string const & s) {
+- struct base64_encode_ctx ctx;
+- base64_encode_init();
+- uint8_t b64[BASE64_ENCODE_LENGTH(s.size())];
+- auto len = base64_encode_update(, b64, s.size(),
Bug#914591: stretch-pu: package python-cryptography/1.7.1-3
On 2018-11-25 13:49:15 [+0100], To sub...@bugs.debian.org wrote: diff -Nru python-cryptography-1.7.1/debian/changelog python-cryptography-1.7.1/debian/changelog --- python-cryptography-1.7.1/debian/changelog 2017-05-28 04:20:33.0 +0200 +++ python-cryptography-1.7.1/debian/changelog 2018-09-02 15:17:35.0 +0200 @@ -1,3 +1,11 @@ +python-cryptography (1.7.1-3+deb9u1) unstable; urgency=medium Okay. This needs to be stretch and not unstable. Sebastian
Processed: Re: discipline the cowboy buildds
Processing commands for cont...@bugs.debian.org: > affects 914558 src:petsc Bug #914558 [release.debian.org] petsc: hardcodes path to sh depending on build host Added indication that 914558 affects src:petsc > thanks Stopping processing here. Please contact me if you need assistance. -- 914558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914558 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914591: stretch-pu: package python-cryptography/1.7.1-3
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: stretch
Severity: normal
With the intention of pushing OpenSSL 1.1.0j into Stretch here is the
proposed change for python-cryptography.
The package python-cryptography fails to build due to an API change of
BIO_callback_ctrl() in OpenSSL. While this is a no-no in a stable
release, it has been explained [0] that the function / callback was
always used with a different prototype. I fixed this by removing the
function / prototype from the python wrapper while upstream removed the
almost all BIO related wrappers [1].
I did a rebuild of python-cryptography's rdeps in Stretch against OpenSSL
1.1.0i and the proposed package with no fallout [2].
Any feedback from the python team is welcome.
[0] https://github.com/openssl/openssl/pull/4493#discussion_r143505277
[1] https://github.com/pyca/cryptography/pull/4220
[2]
https://breakpoint.cc/openssl-rebuild/2018-09-02-rebuild-stretch-python-cryptography/
Sebastian
diff -Nru python-cryptography-1.7.1/debian/changelog python-cryptography-1.7.1/debian/changelog
--- python-cryptography-1.7.1/debian/changelog 2017-05-28 04:20:33.0 +0200
+++ python-cryptography-1.7.1/debian/changelog 2018-09-02 15:17:35.0 +0200
@@ -1,3 +1,11 @@
+python-cryptography (1.7.1-3+deb9u1) unstable; urgency=medium
+
+ * Remove BIO_callback_ctrl: The prototype differs with the OpenSSL's
+definition of it after it was changed (fixed) within OpenSSL. It has no
+users.
+
+ -- Sebastian Andrzej Siewior Sun, 02 Sep 2018 15:17:35 +0200
+
python-cryptography (1.7.1-3) unstable; urgency=medium
* Apply patch 6e7ea2e7 from upstream to fix compilation against OpenSSL
diff -Nru python-cryptography-1.7.1/debian/patches/Remove-BIO_callback_ctrl.patch python-cryptography-1.7.1/debian/patches/Remove-BIO_callback_ctrl.patch
--- python-cryptography-1.7.1/debian/patches/Remove-BIO_callback_ctrl.patch 1970-01-01 01:00:00.0 +0100
+++ python-cryptography-1.7.1/debian/patches/Remove-BIO_callback_ctrl.patch 2018-09-02 15:17:35.0 +0200
@@ -0,0 +1,52 @@
+From: Sebastian Andrzej Siewior
+Date: Sun, 2 Sep 2018 15:00:43 +0200
+Subject: [PATCH] Remove BIO_callback_ctrl()
+
+This removes BIO_callback_ctrl(), bio_info_cb and its two users.
+This is the small version of #4220 ("Remove unused BIO bindings.").
+OpenSSL changed this type because it was wrong and the (now) different
+prototype fails to build.
+There should be users which rely on this function.
+
+Link: https://github.com/pyca/cryptography/pull/4220
+Signed-off-by: Sebastian Andrzej Siewior
+---
+ src/_cffi_src/openssl/bio.py | 8
+ 1 file changed, 8 deletions(-)
+
+diff --git a/src/_cffi_src/openssl/bio.py b/src/_cffi_src/openssl/bio.py
+index a134d9b605b0..c4aa88c5b075 100644
+--- a/src/_cffi_src/openssl/bio.py
b/src/_cffi_src/openssl/bio.py
+@@ -10,7 +10,6 @@ INCLUDES = """
+
+ TYPES = """
+ typedef struct bio_st BIO;
+-typedef void bio_info_cb(BIO *, int, const char *, int, long, long);
+ typedef ... bio_st;
+ typedef ... BIO_METHOD;
+ typedef ... BUF_MEM;
+@@ -69,11 +68,6 @@ BIO *BIO_new_fp(FILE *, int);
+ BIO *BIO_new_fd(int, int);
+ BIO *BIO_new_socket(int, int);
+ long BIO_ctrl(BIO *, int, long, void *);
+-long BIO_callback_ctrl(
+-BIO *,
+-int,
+-void (*)(struct bio_st *, int, const char *, int, long, long)
+-);
+ long BIO_int_ctrl(BIO *, int, long, int);
+ size_t BIO_ctrl_pending(BIO *);
+ size_t BIO_ctrl_wpending(BIO *);
+@@ -125,8 +119,6 @@ int BIO_set_close(BIO *,long);
+ int BIO_get_close(BIO *);
+ int BIO_pending(BIO *);
+ int BIO_wpending(BIO *);
+-int BIO_get_info_callback(BIO *, bio_info_cb **);
+-int BIO_set_info_callback(BIO *, bio_info_cb *);
+ long BIO_get_buffer_num_lines(BIO *);
+ long BIO_set_read_buffer_size(BIO *, long);
+ long BIO_set_write_buffer_size(BIO *, long);
+--
+2.11.0
+
diff -Nru python-cryptography-1.7.1/debian/patches/series python-cryptography-1.7.1/debian/patches/series
--- python-cryptography-1.7.1/debian/patches/series 2017-05-28 04:20:33.0 +0200
+++ python-cryptography-1.7.1/debian/patches/series 2018-09-02 15:17:12.0 +0200
@@ -1,2 +1,3 @@
0001-add-memory-limit-check-for-scrypt.patch
0002-fix-compilation-on-1.1.0f-3603.patch
+Remove-BIO_callback_ctrl.patch
Bug#914412: marked as done (nmu: morbig_0.9-1)
Your message dated Sun, 25 Nov 2018 13:35:03 +0100 with message-id <20181125123501.bzfbczvjn5igc...@debian.org> and subject line Re: nmu: morbig_0.9-1 has caused the Debian Bug report #914412, regarding nmu: morbig_0.9-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 ow...@bugs.debian.org immediately.) -- 914412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914412 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu morbig_0.9-1 . amd64 . unstable . -m "rebuild against menhir 20181113" needed to make libmorbig-ocaml-dev installable on amd64. Thanks -Ralf -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Hi, On Fri, Nov 23, 2018 at 09:05:02AM +0100, Ralf Treinen wrote: > nmu morbig_0.9-1 . amd64 . unstable . -m "rebuild against menhir 20181113" Scheduled. BTW is this only needed on amd64? > needed to make libmorbig-ocaml-dev installable on amd64. Thanks -Ralf Ivo--- End Message ---
Bug#914379: marked as done (nmu: mpich_3.3~rc1-2)
Your message dated Sun, 25 Nov 2018 13:30:40 +0100 with message-id <20181125123039.x3qibikbseowv...@debian.org> and subject line Re: nmu: mpich_3.3~rc1-2 has caused the Debian Bug report #914379, regarding nmu: mpich_3.3~rc1-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 ow...@bugs.debian.org immediately.) -- 914379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Subject: nmu: mpich_3.3~rc1-2 Package: release.debian.org User: release.debian@packages.debian.org Usertags: binnmu Severity: normal Hi, The recent upload of mpich during the window where the buildds on some architectures had a /usr-merged chroot, and the mpich build created scripts (e.g. /usr/bin/mpicc.mpich) with shebang lines pointing to "/usr/bin/bash". Naturally, this then fails to run on non-/usr-merged systems. Now that the buildds have that change reverted, a binNMU should fix it up. nmu mpich_3.3~rc1-2 . arm64 armel armhf i386 mips mips64el ppc64el s390x . unstable . -m 'Rebuild without usrmerge' I'm not the mpich maintainer, but I noticed this when it broke the build of my recent gromacs upload on those architectures - I think this is the right syntax to additionally request a dep-wait on the rebuilt mpich? dw gromacs . arm64 armel armhf i386 mips mips64el ppc64el s390x . unstable . -m 'mpich (>= 3.3~rc1-2+b1)' Thank you. -- Nicholas Breen nbr...@debian.org --- End Message --- --- Begin Message --- Hi, On Thu, Nov 22, 2018 at 10:53:44AM -0800, Nicholas Breen wrote: > The recent upload of mpich during the window where the buildds on some > architectures had a /usr-merged chroot, and the mpich build created > scripts (e.g. /usr/bin/mpicc.mpich) with shebang lines pointing to > "/usr/bin/bash". Naturally, this then fails to run on non-/usr-merged > systems. Now that the buildds have that change reverted, a binNMU > should fix it up. > > nmu mpich_3.3~rc1-2 . arm64 armel armhf i386 mips mips64el ppc64el s390x . > unstable . -m 'Rebuild without usrmerge' There was a maintainer upload, so this is no longer necessary. > > I'm not the mpich maintainer, but I noticed this when it broke the build > of my recent gromacs upload on those architectures - I think this is the > right syntax to additionally request a dep-wait on the rebuilt mpich? > > dw gromacs . arm64 armel armhf i386 mips mips64el ppc64el s390x . unstable . > -m 'mpich (>= 3.3~rc1-2+b1)' Done. Ivo--- End Message ---
Processed: discipline the cowboy buildds
Processing commands for cont...@bugs.debian.org: > reassign 914558 release.debian.org Bug #914558 [petsc] petsc: hardcodes path to sh depending on build host Bug reassigned from package 'petsc' to 'release.debian.org'. No longer marked as found in versions 3.9.4+dfsg1-2. Ignoring request to alter fixed versions of bug #914558 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 914558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914558 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
NEW changes in stable-new
Processing changes file: linux_4.9.135-1_mipsel.changes ACCEPT
