Your message dated Sun, 11 Sep 2022 01:34:12 +0000
with message-id <e1oxbrq-002sgm...@fasolo.debian.org>
and subject line Bug#1019509: fixed in loggerhead 2.0.0-2
has caused the Debian Bug report #1019509,
regarding src:loggerhead: fails to migrate to testing for too long: autopkgtest 
regression
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.)


-- 
1019509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: loggerhead
Version: 1.19~bzr511-1
Severity: serious
Control: close -1 2.0.0-1
Tags: sid bookworm
User: release.debian....@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:loggerhead has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package has autopkgtests which regressed.

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 bookworm, so it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team.

Paul

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

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: loggerhead
Source-Version: 2.0.0-2
Done: Jelmer Vernooij <jel...@debian.org>

We believe that the bug you reported is fixed in the latest version of
loggerhead, 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 1019...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jelmer Vernooij <jel...@debian.org> (supplier of updated loggerhead 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: SHA512

Format: 1.8
Date: Sun, 11 Sep 2022 02:05:36 +0100
Source: loggerhead
Architecture: source
Version: 2.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Bazaar Maintainers <pkg-bazaar-ma...@lists.alioth.debian.org>
Changed-By: Jelmer Vernooij <jel...@debian.org>
Closes: 1019509
Changes:
 loggerhead (2.0.0-2) unstable; urgency=medium
 .
   * Run tests from source since they are no longer installed. Closes:
     #1019509
Checksums-Sha1:
 8161235432895cd4271a4d5f110cc8e9d7e239dd 2550 loggerhead_2.0.0-2.dsc
 75c294ab12eeadf25e66df4ab43471831e06c181 7460 loggerhead_2.0.0-2.debian.tar.xz
 96ec0e5fa3b019c41a0651d6e2e919dd74fe8aa9 8731 
loggerhead_2.0.0-2_amd64.buildinfo
Checksums-Sha256:
 cadf828a0c761d174355b906635b4bcbb3b2b8fefe3bfbdfd2cd42248ddf9def 2550 
loggerhead_2.0.0-2.dsc
 eba50e660497a710892ebe3b173ccf166ca53a21a6d7006eb342988d095abf7c 7460 
loggerhead_2.0.0-2.debian.tar.xz
 b4456c420c16b7a89c93e8ac3024d9551baa786c728df3b66d17556faea9e275 8731 
loggerhead_2.0.0-2_amd64.buildinfo
Files:
 8a1aabd3c014c328ca1b943071abbe37 2550 devel optional loggerhead_2.0.0-2.dsc
 47e124eb782b49f40c97f0ac75bf1024 7460 devel optional 
loggerhead_2.0.0-2.debian.tar.xz
 e6a341b4b18369d28b13b90dda7c62b4 8731 devel optional 
loggerhead_2.0.0-2_amd64.buildinfo

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

iQIzBAEBCgAdFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAmMdNKMACgkQV5wWDUye
I+igHBAAweoM7n0GeskyyrgqT03BW3xU6wCsF65B8tuQg2pIuc0Sz/sZQbWQoNZj
WMWUrZAAa246729aWmsmqzXeLYFaB1IWydMmk6t8HNM/rNn5qi+lMHvRXsTESeVI
u3vn2VE7P+HLQr+7oaCweVyQCK2wO3ZELYsNCQt7KMpSLrXabhVYAJvmfivQeyk6
vCAJLqeARrB+wPFYFjom7raqtaG9KXEkbSnJ9X+Nt4rGjfffIHwhNrhi1Z+XaYdM
wxP/1E9A/ARK+M24CvG0XZ28EarZB2wuBt1DxzHlY7twRwmXGdiEfgvnJzgpA1LK
sK60wRYA3rw5l7cNR9pLNh44xqW6w+IsK83gAYTcv0pQ0vlHHnX1ZD+gKiO3Z3Se
2sgIucxzDR5jj81KaIPZKz3n7s3qV5tu8IJVBvgU1TSID1pldrNakLrWu/CiqCIb
/qoavqgJtqzott/JSQLSrBD+2fQRPliHkXmlKlL9Q8g43k42FGpxac8y6J0e59VN
KaWn51GLbTlelH5HzIY2M6lph/X6J9Lf2XX1vlLqjfLYHLNvWO/1OsOCHPtSZZIo
doJ5oTZDEW2VAp95gbGRlkt8MowvuHYabsdcKA4yXWSPaxGR1VzlLZ3Ry4erx3AI
1zCmJxbi4FDARlAmxCL8KYSXkvdbiwqcdjLU/GJsJS0nTmF4erE=
=iiGp
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to