Your message dated Sat, 08 Aug 2020 19:34:11 +0000
with message-id <e1k4ubb-000d96...@fasolo.debian.org>
and subject line Bug#966210: fixed in django-ranged-response 0.2.0-4.1
has caused the Debian Bug report #966210,
regarding src:django-ranged-response: fails to migrate to testing for too long:
maintainer built arch:all binary
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.)
--
966210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-ranged-response
Version: 0.2.0-2
Severity: serious
Control: close -1 0.2.0-4
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:django-ranged-response 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=django-ranged-response
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: django-ranged-response
Source-Version: 0.2.0-4.1
Done: Paul Gevers <elb...@debian.org>
We believe that the bug you reported is fixed in the latest version of
django-ranged-response, 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 966...@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 django-ranged-response
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, 24 Jul 2020 20:41:06 +0200
Source: django-ranged-response
Architecture: source
Version: 0.2.0-4.1
Distribution: unstable
Urgency: medium
Maintainer: FreedomBox packaging team
<freedombox-pkg-t...@lists.alioth.debian.org>
Changed-By: Paul Gevers <elb...@debian.org>
Closes: 966210
Changes:
django-ranged-response (0.2.0-4.1) unstable; urgency=medium
.
* Non-maintainer upload.
* source only upload to enable migration (Closes: #966210)
Checksums-Sha1:
262e001fe5231ba357db1b1bfb0ce4bf5e17f5d0 2097
django-ranged-response_0.2.0-4.1.dsc
69f60c49383451f65f5b10118878a0bc266c5c2a 3456
django-ranged-response_0.2.0-4.1.debian.tar.xz
Checksums-Sha256:
9e89e3658509d9161e756c22a3be4aaec1d96b006cf59d5f7da3e3fdcdb36776 2097
django-ranged-response_0.2.0-4.1.dsc
2509a06280fe4b8ea82a71bc72ebc3d853b7134f76cead3afc0ef41b26d29b4e 3456
django-ranged-response_0.2.0-4.1.debian.tar.xz
Files:
472b02546b7ec27e119887dfaf297973 2097 python optional
django-ranged-response_0.2.0-4.1.dsc
20dc3755806d2d60e39edb1385d9e8e5 3456 python optional
django-ranged-response_0.2.0-4.1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl8bK2YACgkQnFyZ6wW9
dQpUdQf/RQ/sjiyv5V6Q78257G0ocTyp4XnqLrqRzTUFFC9tDYWfe+PKXgV7If7l
JcP0K9M1E+6ZLwCAKGZpVHKgeqTM56uoQ+upmxTreWrxwz/yoNSgPXhB7bAlYjm3
O09kibDPJTpMSuhOThpC4Z5JNGmyXy2VU1jxtbq/rPPtUua/Wkf81S24sMd+aRfl
r1heKULeRbjbR3wQQskKTh6pvALOAsiCsLQPHttcsTgJdwHkDlpX/jrgo6LZLfnY
Q+TzxQH4KfhHko3Ig9evu7e1zDqIdr+xvCMe1zjjLCCLuFkW6/+WvFxM4gbQ+Eyp
WRHpbLynY5KhLISwD/vG9Ym+5D0sqw==
=NWy/
-----END PGP SIGNATURE-----
--- End Message ---
