Your message dated Wed, 13 Nov 2024 08:40:46 +0000
with message-id <e1tb8ve-00akel...@fasolo.debian.org>
and subject line Bug#1086590: fixed in psycopg3 3.2.3-4
has caused the Debian Bug report #1086590,
regarding src:psycopg3: fails to migrate to testing for too long
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.)


-- 
1086590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086590
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: psycopg3
Version: 3.2.1-3
Severity: serious
Control: close -1 3.2.3-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:psycopg3 has been trying to migrate for 31 days [2], hence this bug report. The current output of the migration software for this package is copied to the bottom of this report and should list the reason why the package is blocked.

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.

This bug submission immediately closes the bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. This bug is also tagged 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.

This bug report has been automatically generated and has only been sent manually. If you have any comments with regards to the content or the process, please reach out to me.

Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=psycopg3

Current text from [2]:
Migration status for psycopg3 (3.2.1-3 to 3.2.3-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
Issues preventing migration:
∙ ∙ missing build on armel
∙ ∙ missing build on armhf
∙ ∙ missing build on i386
∙ ∙ arch:armel not built yet, autopkgtest delayed there
∙ ∙ arch:armhf not built yet, autopkgtest delayed there
∙ ∙ arch:i386 not built yet, autopkgtest delayed there
∙ ∙ autopkgtest for psycopg3/3.2.3-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
Additional info:
∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psycopg3.html ∙ ∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ 5 days old (needed 5 days)

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: psycopg3
Source-Version: 3.2.3-4
Done: Colin Watson <cjwat...@debian.org>

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

Debian distribution maintenance software
pp.
Colin Watson <cjwat...@debian.org> (supplier of updated psycopg3 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: Wed, 13 Nov 2024 08:18:21 +0000
Source: psycopg3
Architecture: source
Version: 3.2.3-4
Distribution: unstable
Urgency: medium
Maintainer: Tomasz Rybak <serp...@debian.org>
Changed-By: Colin Watson <cjwat...@debian.org>
Closes: 1086590
Changes:
 psycopg3 (3.2.3-4) unstable; urgency=medium
 .
   * Team upload.
   * test(numpy): fix integer type handling harder (closes: #1086590).
Checksums-Sha1:
 f51c7ef51932ab889eccfb34c986a82c967adad3 2735 psycopg3_3.2.3-4.dsc
 7135c11bd5e0e839b0ac30c34ad785b5c682c70d 11616 psycopg3_3.2.3-4.debian.tar.xz
 50f2fc0140dd5a9a5e334706eb209f3e778e333c 9617 psycopg3_3.2.3-4_source.buildinfo
Checksums-Sha256:
 e497383fec1fc6cb753fb8325536b4ee8359b5e34a8c3cf551724ccb740c4064 2735 
psycopg3_3.2.3-4.dsc
 d35080ce966b6349944d5faa9e3861f72ee495b44b298252a31be36e5c708809 11616 
psycopg3_3.2.3-4.debian.tar.xz
 9a92489f986bedc1ecd87da93da77e069af5771bf382c1121c1c6a40d9555a9a 9617 
psycopg3_3.2.3-4_source.buildinfo
Files:
 a635517bbc6d1a581038e7e149c35095 2735 python optional psycopg3_3.2.3-4.dsc
 b977edff790346db2787ebf3121fd509 11616 python optional 
psycopg3_3.2.3-4.debian.tar.xz
 281828ccdea1ff26a5ea9dcfb0df2e1f 9617 python optional 
psycopg3_3.2.3-4_source.buildinfo

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

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmc0YPwACgkQOTWH2X2G
UAsvRA//XuLxjWfITfa01XVwoYKon3sRQVTB0PMy8a4IuaRq0RgGSSq2TU8D6WoX
3H0v9D58kzf0ZYQOKFirD4nm5i3H3mPQ246HvXsqsrc9GEzanGX2oZVutBPsXTB1
/fUaWqf+wfcNeLkW2lNmjTu6jQnu0Zdzr3Je6t3dT8s2Er54baFEfNuEVdTtRlhA
0DlhsWuAXx0CFFjmHIlqeRvz8eo7B2+Adw9L6Ows9u9Wwrt7Iy36uwatW2aizTCG
KN0PM0v0ItbqS1liJleZTWgUM9caKRp4a7YQFk6r/tAlIbmvVxgdO8LiKrffyL37
/Qwa3tYdaW++muYbkK23S8VtDzEtVScAtPygzOc9wNwXpQ0mcI40gJlDCut3LzXi
tw/6MVoBfccjxui1Gu6Wc6KMDHSmh7nrB3qOOduHUjDBEnKWud5yWgwlz1pNeyhP
9FQR/kntx+RAtfAqHmueGokNgZBiF61IJ0K7BgCNQ9iip9Z8RrcfDnwms5qubFTw
GbOq4Orioa6vMHPgFYHBKWYQhYt0c5E6IZ4Y9e1qVE/4UrmZzbcBdmz366TV3kul
7qbFCK/4ocN6dkFc9PunPWh6laWaTRg93NuU5Fq2PhghV3AftpjUQsNTN1ee67ZF
xAx0ZMqVYv7CbLrPr1st/qij4gw5RKV3Px6IoJrWz6VHRcNbZS0=
=Tr3A
-----END PGP SIGNATURE-----

Attachment: pgpvRs3bLlK2A.pgp
Description: PGP signature


--- End Message ---

Reply via email to