Your message dated Mon, 13 May 2024 16:49:26 +0000
with message-id <e1s6yre-0052zf...@fasolo.debian.org>
and subject line Bug#1070982: fixed in click 0.5.2-3
has caused the Debian Bug report #1070982,
regarding src:click: fails to migrate to testing for too long: autopkgtest 
regression on !amd64
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.)


-- 
1070982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070982
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: click
Version: 0.5.0-10
Severity: serious
Control: close -1 0.5.2-2
Tags: sid trixie
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 30 days as having a Release Critical bug in testing [1]. Your package src:click has been trying to migrate for 60 days [2]. Hence, I am filing this bug. The autopkgtest of the version in unstable fails everywhere except on amd64.

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 trixie, 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/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=click

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: click
Source-Version: 0.5.2-3
Done: Mike Gabriel <sunwea...@debian.org>

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

Debian distribution maintenance software
pp.
Mike Gabriel <sunwea...@debian.org> (supplier of updated click 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: Mon, 13 May 2024 18:21:51 +0200
Source: click
Architecture: source
Version: 0.5.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian UBports Team <team+ubpo...@tracker.debian.org>
Changed-By: Mike Gabriel <sunwea...@debian.org>
Closes: 1067815 1070982
Changes:
 click (0.5.2-3) unstable; urgency=medium
 .
   * debian/watch:
     + Update file for recent GitLab changes of the tags overview page.
   * debian/patches:
     + Add 0006_fix-implicit-function-declaration.patch. Make -Werror=implicit-
       function-declaration unnecessary.
     + Add 0007_add-support-for-loongarch.patch. Thanks to Ruilong Wu for
       providing the patch. Resolve FTBFS on loongarch architecture. (Closes:
       #1067815).
   * debian/rules:
     + Drop DEB_CFLAGS_MAINT_STRIP = -Werror=implicit-function-declaration.
   * debian/{rules,click.install}:
     + Set systemdsystemunitdir to /usr/lib/systemd/system (not
       /lib/systemd/system/ anymore).
   * Revert "debian/control: Make bin:pkg python3-click-package arch:all."
     The python3-click-package module contains:
     preload_path = "/usr/lib/<multiarch>/click/libclickpreload.so"
     in paths.py and should thus always be arch:any. This should fix
     autopkgtest builds on non-amd64 architectures. (Closes: #1070982).
   * debian/control:
     + Bump Standards-Version to 4.7.0. No changes needed.
     + Drop B-D python3-six. Patched out in 1015_drop-using-six.patch.
Checksums-Sha1:
 b9d6cc85ed625961a1695b57e3c170762ffff5fc 2911 click_0.5.2-3.dsc
 bd8ee383db0fc8781fafd6436b78fdf4010812d6 37512 click_0.5.2-3.debian.tar.xz
 dc0b2fce83d7021d41ff69d80751c2782d082d95 10347 click_0.5.2-3_source.buildinfo
Checksums-Sha256:
 b5c9703bff25e72453a43d6f298537458a415840446e1a8bf439dbc80485deec 2911 
click_0.5.2-3.dsc
 136de4fff13dc062e77c364a690374b02277f68029a87e91b471d765f87ab98f 37512 
click_0.5.2-3.debian.tar.xz
 23d8f1455c25befb81aaf369e7733dece630ae6f20c58b150fde4a74cbb94bd2 10347 
click_0.5.2-3_source.buildinfo
Files:
 9454f6599064f90a01453ccfdcf21988 2911 admin optional click_0.5.2-3.dsc
 aacb29db6cff87a7b6fd7267541a2743 37512 admin optional 
click_0.5.2-3.debian.tar.xz
 18fb2f89ef8a3346301c8f627662c739 10347 admin optional 
click_0.5.2-3_source.buildinfo

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

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmZCPvQVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxrIAQAICd4Qp8X6c+2XKNqz3W+0siyYdS
6SEf3F9KkmOzm2cOH1q+CItjgyGcGpv0q8taJ6H59WNXuZVRZPieztRy5l/hpbBR
+PkouuFD9Akggnx3DSBq8ikFnwVyNDF8iDzopFqb7rt6y3Ov7rHLdxYeFzfi6H2S
skhBxm33boKLmaeUZM+bb6+JDZWg6ndJWsAGSLanzoCzCpRPIEYM2NGzdEEfZcdK
iczqR7JW565n4jgnJqjlc9qYfivckneNlGSC3tOQKfdJWMKIAKFNFESRWbFE2qP/
sHwOgetg9xJAHmpGg2pcPXYD30InOylO3BZrAFqVR0PVOBoywGcfJvqszvy+QSKS
cgv8vRNRcOQ0nvvKal7VtWLwgocgGHe46DKw1XKJfAPfZp4rqcOErzhuHs+EJrRi
ec5sSGdROyND1J0Z0D6AfjSXY4hDoIqhWQVgui+O1ExNQ5vIU1GaGht1T96k51z9
0hzrCV2GkDXZNh8R2Vi8R9+iWQ0LlLKYmEPD1cszoEqUQPnI//rKh72l+KDPnlGY
sqjJKaseGfX/AG4lTvauyW3WeWt4bH+JgcsQz133MDnIpxhf3xAQKS8UECfoJX0e
vI3LT7WiNyP2A/dRswU9SxUphByt7RmQqakuClrfRmVrJbeZfIP3STzRklks/+7E
YeTgmIYj6w1zX6Rw
=7Y9x
-----END PGP SIGNATURE-----

Attachment: pgpFFgRIh27_I.pgp
Description: PGP signature


--- End Message ---

Reply via email to