Your message dated Sat, 26 Sep 2020 19:18:23 +0000
with message-id <e1kmfib-0004x7...@fasolo.debian.org>
and subject line Bug#970102: fixed in barman 2.11-1.1
has caused the Debian Bug report #970102,
regarding src:barman: fails to migrate to testing for too long: maintainer 
built arch:all binaries
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.)


-- 
970102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: barman
Version: 2.10-2
Severity: serious
Control: close -1 2.11-1
Tags: sid bullseye pending
User: release.debian....@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:barman in its
current version in unstable has been trying to migrate for 60 days [2].
Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

Your package is only blocked because the arch:all binary package(s)
aren't built on a buildd. Unfortunately the Debian infrastructure
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
shortly do a no-changes source-only upload to DELAYED/15, closing this
bug. Please let me know if I should delay or cancel that upload.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg00005.html
[2] https://qa.debian.org/excuses.php?package=barman


Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: barman
Source-Version: 2.11-1.1
Done: Paul Gevers <elb...@debian.org>

We believe that the bug you reported is fixed in the latest version of
barman, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 970...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Paul Gevers <elb...@debian.org> (supplier of updated barman package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 11 Sep 2020 20:21:45 +0200
Source: barman
Architecture: source
Version: 2.11-1.1
Distribution: unstable
Urgency: medium
Maintainer: Marco Nenciarini <mnen...@debian.org>
Changed-By: Paul Gevers <elb...@debian.org>
Closes: 970102
Changes:
 barman (2.11-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #970102)
Checksums-Sha1:
 e96b36fd68a72ba57ac47ca9680aac9d60e63ccb 2067 barman_2.11-1.1.dsc
 035278176fe8fc66de29c2a31ed3e578bed2fbe1 11036 barman_2.11-1.1.debian.tar.xz
Checksums-Sha256:
 c8282da414512ac0716db951bcd6b2dc665b7d82aca428ebbdcc04663d78eebb 2067 
barman_2.11-1.1.dsc
 8b04182fcd546db42707f8e4353043186c59d68dd3deee969673cd5400db8fa3 11036 
barman_2.11-1.1.debian.tar.xz
Files:
 6034dd7e492d658c17387872afc68b3b 2067 database optional barman_2.11-1.1.dsc
 e57e42f2fb5a52001e650c65c0a97691 11036 database optional 
barman_2.11-1.1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl9bwFQACgkQnFyZ6wW9
dQoE4ggAnFQieC/iP4RlS9/gd+jJeci8/q3cko9KKCTOCPUVZFOMjKdHOInmTSyE
TAwMuRiQ15ORtiAZiB8j7WtiJqNkDnDmG2jw/kcq6jHoOQtBLwpFlqaj6mGuW8Tp
0rrMcOYUUu0bX0r0NcfP7wGYxa/DzDhTrIS1Vs4gA6sp51Idx09CCkxCFcfs2Bls
1wGQ+Hvq73IJl3BZAwGCPxgwmtF/Dl46fa8dBoje3JKozdSndGjt5hYwTHezzUZA
fny2mwhQhcICdy+kr+8WOZfqGeE10TOiTEJQWs+eIXxdJwRc8uy+lQRHMAKZ7Fvf
ghcvkXY7mm6rxkGM2KS/mhHkLjmNAA==
=nXDX
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to