Bug#945929: marked as done (nmu: php7.3_7.3.11-1~deb10u1)
Your message dated Sun, 1 Dec 2019 17:59:24 +0100
with message-id <20191201165922.GA13315@debian.org>
and subject line Re: nmu: php7.3_7.3.11-1~deb10u1
has caused the Debian Bug report #945929,
regarding nmu: php7.3_7.3.11-1~deb10u1
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.)
--
945929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945929
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
nmu php7.3_7.3.11-1~deb10u1 . ANY . unstable . -m "Rebuild in sid."
I don't know what happened to 7.3.11-1 ... but currently we have a
version skew
php7.3 | 7.3.10-1 | testing | source, all
php7.3 | 7.3.11-1~deb10u1 | stable | source, all
php7.3 | 7.3.11-1~deb10u1 | unstable | source, all
and the 7.3.11-1~deb10u1 security cannot migrate to testing because of
* maintainer built binaries for the security upload
* snmp transition that was done in sid some time ago
A binNMU should get the package into testing.
Andreas
--- End Message ---
--- Begin Message ---
On Sun, Dec 01, 2019 at 12:13:57PM +0100, Ivo De Decker wrote:
> In this case, I'm reluctant to do this. What is really needed here is an
> upload of the newer version to unstable.
A new upload happened, so the binNMU request is no longer relevant.
Ivo
--- End Message ---
Reply to: