Your message dated Wed, 25 Dec 2019 14:03:32 +1100
with message-id <4146575.h7uxvT4bdz@deblab>
and subject line Done: golang-logrus: new upstream release 1.4.2
has caused the Debian Bug report #935524,
regarding golang-logrus: new upstream release 1.4.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 [email protected]
immediately.)
--
935524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935524
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: golang-logrus
Severity: wishlist
Dear Maintainer,
There's a new upstream release available - 1.4.2
I did a rebuild of the reverse dependencies that reverse-depends[0]
could identify and the following packages failed to build with a locally
updated golang-logrus:
cadvisor_0.27.1+dfsg2-4 [not-in-testing]
containerd_0.2.3+git20170126.85.aa8187d~ds1-2 [not-in-testing]
docker.io_18.09.1+dfsg1-7.1 ---> FTBFS on *all* archs in unstable buildd
docker-swarm_1.2.5+dfsg-2 [not-in-testing]
gobgp_1.33-1 [not-in-testing]
golang-github-prometheus-common_0+git20181119.b36ad28-1 [not-in-testing]
kubernetes_1.7.16+dfsg-1 [not-in-testing]
nomad_0.8.7+dfsg1-1 [not-in-testing]
notary_0.6.1~ds1-3 ---> known test failure: #917716
Ignoring the packages that aren't in testing (probably for a good
reason), the remaining ones seems to have known issues with existing
bug reports.
Thus unless I overlooked something there would be 0 new FTBFS introduced
by updating logrus to 1.4.2.
[0]: reverse-depends -l -b src:golang-logrus
Regards,
Andreas Henriksson
--- End Message ---
--- Begin Message ---
Package: src:golang-logrus
Version: 1.4.2-1
Uploaded, thanks.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
