Your message dated Mon, 18 May 2026 14:35:40 +0000
with message-id <[email protected]>
and subject line Bug#1136798: fixed in lua-sql 2.8.1-3
has caused the Debian Bug report #1136798,
regarding src:lua-sql: 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 [email protected]
immediately.)
--
1136798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1136798
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: lua-sql
Version: 2.7.0-2
Severity: serious
Control: close -1 2.8.1-2
Tags: sid forky
User: [email protected]
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:lua-sql 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. Blocked packages can have impact on other packages, which makes
preparing for the release more difficult. The situation that caused this bug
report might even be the result of such an issue. We expect maintainers to fix
issues that hamper the migration of their package in a timely manner. If your
package in this situation due to another package, consider helping out.
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 forky, 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. 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=lua-sql
Current text from [2]:
Migration status for lua-sql (2.7.0-2 to 2.8.1-2): BLOCKED: Rejected/violates
migration policy/introduces a regression
Issues preventing migration:
∙ ∙ lua-sql unsatisfiable Build-Depends(-Arch) on armhf: libduckdb-dev
∙ ∙ lua-sql unsatisfiable Build-Depends(-Arch) on i386: libduckdb-dev
∙ ∙ lua-sql unsatisfiable Build-Depends(-Arch) on s390x: libduckdb-dev
∙ ∙ Missing build on armhf
∙ ∙ Missing build on i386
∙ ∙ Missing build on s390x
∙ ∙ Autopkgtest deferred on i386: missing arch:i386 build
∙ ∙ Autopkgtest deferred on s390x: missing arch:s390x build
∙ ∙ Lintian check waiting for test results on i386, armhf, s390x - info
∙ ∙ Reproducibility check deferred on armhf: missing builds - info
∙ ∙ Reproducibility check deferred on i386: missing builds - info
Additional info (not blocking):
∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lua-sql.html
∙ ∙ Reproduced on amd64 - info
∙ ∙ Reproduced on arm64 - info
∙ ∙ 31 days old (needed 5 days)
--- End Message ---
--- Begin Message ---
Source: lua-sql
Source-Version: 2.8.1-3
Done: Victor Seva <[email protected]>
We believe that the bug you reported is fixed in the latest version of
lua-sql, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Victor Seva <[email protected]> (supplier of updated lua-sql 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 18 May 2026 15:36:18 +0200
Source: lua-sql
Architecture: source
Version: 2.8.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Lua Team <[email protected]>
Changed-By: Victor Seva <[email protected]>
Closes: 1136798
Changes:
lua-sql (2.8.1-3) unstable; urgency=medium
.
* Build the duckdb backend only where it is available
* Compile duckdb module conditionally (Closes: #1136798)
* d/watch: version 5
Checksums-Sha1:
11860e7c83ecf5aad2664e6f13f97620372fb84c 2197 lua-sql_2.8.1-3.dsc
5109582961444b8ead2bdb88c74fdd8ace18f73a 5720 lua-sql_2.8.1-3.debian.tar.xz
888af6d0a4bbb4f5fe2241f694f9fa236b870e51 11307 lua-sql_2.8.1-3_amd64.buildinfo
Checksums-Sha256:
8976cabd29aecd3417652980ca6826d9d6f78d61b54f91f54da5a70c46880e97 2197
lua-sql_2.8.1-3.dsc
fc842513c0207cf0c4ed68d0e1ea123280dd9312aa83653d4ff99d413b98d45c 5720
lua-sql_2.8.1-3.debian.tar.xz
a4eada490cb281b911a92dd060cb34d88cf4a49dd1b091ffc4e6d59c927f005a 11307
lua-sql_2.8.1-3_amd64.buildinfo
Files:
86ced3f35d5077df8344324d29db9c42 2197 interpreters optional lua-sql_2.8.1-3.dsc
758fb775b814ff6f6ef2488af4e83295 5720 interpreters optional
lua-sql_2.8.1-3.debian.tar.xz
77b94e7a3ce9357e55cd7011d46a1f17 11307 interpreters optional
lua-sql_2.8.1-3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iIcEARYKAC8WIQQq6AO8RS0zF4SC1vh9e2XEKg7IsgUCagscWBEcdnNldmFAZGVi
aWFuLm9yZwAKCRB9e2XEKg7IskpeAQCUWCgmxUU5PGy5MZQblOE0a9ygYbXkv0gN
BxCsFLn1eAEAiSKnFiCMSD/1IGIAINWrc5lOsP6FSqQszSBNTa/O4QM=
=zC1D
-----END PGP SIGNATURE-----
pgpbsaF2o_87o.pgp
Description: PGP signature
--- End Message ---
