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
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,
> >
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
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
$
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
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
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:
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
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
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
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
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.
--
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
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
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
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
Processing changes file: linux_4.9.135-1_mipsel.changes
ACCEPT
17 matches
Mail list logo
