Processed: reassign 1054581 to python3-asdf, tagging 1020507, tagging 1054596, tagging 1054609, tagging 1018126 ...
Processing commands for cont...@bugs.debian.org:
> reassign 1054581 python3-asdf 2.14.3-1
Bug #1054581 [asdf] asdf: Missing dependency on asdf-unit-schemas (breaks
pkg_resources)
Warning: Unknown package 'asdf'
Bug reassigned from package 'asdf' to 'python3-asdf'.
No longer marked as found in versions 2.14.3-1.
Ignoring request to alter fixed versions of bug #1054581 to the same values
previously set
Bug #1054581 [python3-asdf] asdf: Missing dependency on asdf-unit-schemas
(breaks pkg_resources)
Marked as found in versions python-asdf/2.14.3-1.
> tags 1020507 + experimental
Bug #1020507 {Done: Paul Gevers } [src:libcleri] libcleri
breaks siridb-server autopkgtest, siridb-server rebuild "fixes" the issue
Added tag(s) experimental.
> tags 1054596 + sid trixie
Bug #1054596 [src:haskell-binary-parsers] Removal notice: obsolete
Added tag(s) sid and trixie.
> tags 1054609 + experimental
Bug #1054609 {Done: Paul Gevers } [src:python-django]
src:python-django: fails to migrate to testing for too long: sort of transition
Added tag(s) experimental.
> tags 1018126 - bookworm + trixie
Bug #1018126 {Done: Boyuan Yang } [src:gthumb] gthumb:
depends on unmaintained clutter-1.0 and related libraries
Removed tag(s) bookworm.
Bug #1018126 {Done: Boyuan Yang } [src:gthumb] gthumb:
depends on unmaintained clutter-1.0 and related libraries
Added tag(s) trixie.
> tags 1012666 - bookworm
Bug #1012666 {Done: Noël Köthe } [src:wget2] ITS: wget2
Removed tag(s) bookworm.
> fixed 1034659 4.10.2-1
Bug #1034659 {Done: Timo Aaltonen } [freeipa-client]
freeipa-client: IPA client Kerberos configuration incompatible with java
Marked as fixed in versions freeipa/4.10.2-1.
> reassign 973861 nginx
Bug #973861 {Done: Jan Mojžíš } [apt] apt: http acquire
method still failing with "Undetermined error" or "Data left in the buffer"
Bug reassigned from package 'apt' to 'nginx'.
No longer marked as found in versions apt/2.1.11 and apt/2.1.18.
No longer marked as fixed in versions nginx/1.22.1-7.
> fixed 973861 1.22.1-7
Bug #973861 {Done: Jan Mojžíš } [nginx] apt: http acquire
method still failing with "Undetermined error" or "Data left in the buffer"
Marked as fixed in versions nginx/1.22.1-7.
> affects 973861 + src:apt
Bug #973861 {Done: Jan Mojžíš } [nginx] apt: http acquire
method still failing with "Undetermined error" or "Data left in the buffer"
Added indication that 973861 affects src:apt
> notfound 1031066 252.5-2
Bug #1031066 {Done: Michael Biebl } [systemd] systemd kills
all processes in user session/scope unit upon kernel OOM
No longer marked as found in versions systemd/252.5-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1012666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012666
1018126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018126
1020507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020507
1031066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031066
1034659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034659
1054581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054581
1054596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054596
1054609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054609
973861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1040901: Upcoming changes to Debian Linux kernel packages
OK, it seems my original email got lost somewhere in tech hickups, it's possible the kernel crashed before sending the email, AMD just crashes once or twice a day. So I'm writing this email a bit in a hurry, so it's not quite as thought out as the last one weeks ago, but yesterday's email was pretty concerning. We should not rush this. we need to be realistic that this will take a couple of months to sort out a new scheme, don't expect this to be done before the end of the year, and that seems to be very optimistic. On Sat, Oct 07, 2023 at 04:53:33PM +0200, Bastian Blank wrote: > Moin > > On Sun, Sep 24, 2023 at 03:01:51PM +0200, Bastian Blank wrote: > > ## Kernel modules will be signed with an ephemeral key > > This is now > https://salsa.debian.org/kernel-team/linux/-/merge_requests/607. > > > ## Image packages contains more version info > > > > Example: linux-image-6.5.3-cloud-arm64 > > > It will not longer be possible to reliably derive the package name from > > kernel release (see above), as both values are not really related > > anymore. This package name seems to be missing the Debian release, which is mandatory to ensure that you can install 6.5.3-2 and 6.5.3-1 in parallel, which again is mandatory. That's not something we can compromise on; it's absolutely vital that - you can revert to the kernel you last booted succesfully, i.e. 6.5.3-1 if 6.5.3-2 is broken (think toolchain broke or something on buildds) - the currently booted kernel is not impacted. This means it must be able to load additional modules. Some platforms even require additional modules to be loaded to reboot, I've seen this on laptops. It is fine to say "you must reboot", but it is not fine to just break the running system until you do. > > I missed that apt does something similar (maintainers cced). It wants > to see if a particular package matches the current kernel to make the > autoremove prevention work. That lookup is quite a hard problem. > > What should work: We define a new control field. It contains both the > kernel name and a version prefix. > > Example: > - Linux 6.6 (would match 6.6-1, 6.6.1-1) > - Linux 6.6.3 (would match 6.6.3-1, but not 6.6.3+2-1) > - Linux 6.6.3+2 > > The algorithm would be something like this: > - Check $(uname -s) against the first word. Otherwise completely > ignore. Needless to say I do not believe that uname -s is necessarily a single word. > - Check if $(uname -r) matches the version prefix in this field. Mark > as keep if it matches. > - Aggregate packages by version prefix. > - Sort as version, keep newest two(?). I don't really care about the ordering, I want to order by package version. I need to identify: * Which kernel image package is currently booted. Hence I need to go from the uname -r to exactly one installed kernel image package that acts as the key package to determine if a kernel version is installed. * What are other installed kernel image packages * Given a uname / kernel image package, which other kernel packages belong to it This allows me to keep the currently installed kernels around. The flip side of the coin is the code in APT that actually autoremoves kernels: It needs to identify, given a list of kernel images to keep which other kernel packages can be removed. Optimally it can still remove headers for 6.6 if you don't even have 6.6 images installed anymore and _somehow_ pulled them in. Essentially I want to order kernel image packages by version, and keep the currently booted and the latest one, and the 2nd latest if currently booted == latest one, and then remove any other versioned kernel package not related to them. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Bug#1054635: python3-certbot-dns-ovh: fails with Error adding TXT record: Expecting value: line 1 column 1 (char 0)
Package: python3-certbot-dns-ovh Version: 2.1.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, Certbot renewal fails: > systemctl status certbot × certbot.service - Let's Encrypt renewal Loaded: loaded (/etc/systemd/system/certbot.service; static) Active: failed (Result: exit-code) since Fri 2023-10-27 01:05:12 CEST; 7h ago TriggeredBy: ● certbot.timer Process: 31415 ExecStart=/usr/bin/certbot renew --quiet --agree-tos --post-hook systemctl reload dovecot.service; systemctl reload lighttpd.service (code=exited, status=1/FAILURE) Main PID: 31415 (code=exited, status=1/FAILURE) CPU: 24.663s okt 27 01:01:13 alarm systemd[1]: Starting certbot.service - Let's Encrypt renewal... okt 27 01:05:10 alarm certbot[31415]: Failed to renew certificate *** with error: Error adding TXT record: Expecting value: line 1 column 1 (char 0) okt 27 01:05:11 alarm certbot[31415]: All renewals failed. The following certificates could not be renewed: okt 27 01:05:11 alarm certbot[31415]: /etc/letsencrypt/live/***/fullchain.pem (failure) okt 27 01:05:11 alarm certbot[31415]: 1 renew failure(s), 0 parse failure(s) The bug was alreay reported & fixed upstream, can it please be backported?: https://github.com/certbot/certbot/issues/9799 -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable') Architecture: armel (armv5tel) Kernel: Linux 6.1.0-13-marvell (UP) Kernel taint flags: TAINT_WARN Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-certbot-dns-ovh depends on: ii certbot 2.1.0-4 ii python3 3.11.2-1+b1 ii python3-acme 2.1.0-1 ii python3-certbot [python3-certbot-abi-2] 2.1.0-4 ii python3-lexicon 3.11.7-1 ii python3-pkg-resources66.1.1-1 python3-certbot-dns-ovh recommends no packages. python3-certbot-dns-ovh suggests no packages. -- no debconf information
Bug#1040901: Upcoming changes to Debian Linux kernel packages
On Thu, Oct 26, 2023 at 01:36:50PM +0200, Bastian Blank wrote: > On Fri, Oct 20, 2023 at 05:54:23PM +0200, Bastian Blank wrote: > > Or would it be easier to re-use normal dependency resolving, like: > > Kernel-Provides: linux (>> 6.6.1~), linux (<< 6.6.1.) > > This would allow full flexibility and re-uses existing code to check > > such definitions. > > Okay, noone complained, so it looks like this should work. > No no it doesn't. Did nobody read my email? Did I even send my email? I don't know what the hell is going on here, but I spend an hour writing an email discussing the options outlined before this ridiculousness and the requirements, but I can't find it in my notmuch. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Bug#1054436: marked as done (wand: update required for imagemagick 6.9.12.98)
Your message dated Fri, 27 Oct 2023 05:50:04 + with message-id and subject line Bug#1054436: fixed in wand 0.6.11-3 has caused the Debian Bug report #1054436, regarding wand: update required for imagemagick 6.9.12.98 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.) -- 1054436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wand Version: 0.6.11-2 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: sramac...@debian.org imagemagick is currently performing a transition of its shared libraries. wand hard-codes these shared libraries and needs to be updated for the new SONAMEs. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: wand Source-Version: 0.6.11-3 Done: Håvard F. Aasen We believe that the bug you reported is fixed in the latest version of wand, 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 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Håvard F. Aasen (supplier of updated wand 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, 27 Oct 2023 07:08:11 +0200 Source: wand Architecture: source Version: 0.6.11-3 Distribution: unstable Urgency: medium Maintainer: Håvard F. Aasen Changed-By: Håvard F. Aasen Closes: 1054436 Changes: wand (0.6.11-3) unstable; urgency=medium . [ Stephan Lachnit ] * debian/control: recommend libmagickcore-extra package. . [ Håvard F. Aasen ] * Change BD to libmagickwand-dev. Closes: #1054436 * Update metadata for latest patch. * Update runtime dependencies to the latest imagemagick SONAME. Checksums-Sha1: 8419659596bab95b5df3147747c960ebeed24b54 1456 wand_0.6.11-3.dsc 737a4bddb5abc88302510df289a26105f7561710 9000 wand_0.6.11-3.debian.tar.xz 035249988a1573ee10cd658ca029b7b792e849e7 12477 wand_0.6.11-3_amd64.buildinfo Checksums-Sha256: 7cd491cc0d8323b890381aae30e8b6da40742506903c8190855db2a3ee79cbf8 1456 wand_0.6.11-3.dsc 9e5ed89be528b675b1be979f624fa46630ec60de659cc35da6bad53c8f9f5033 9000 wand_0.6.11-3.debian.tar.xz 04a385532ca96979051b3533b28b2c2e8d6ff76422c2378197d7b19406f78494 12477 wand_0.6.11-3_amd64.buildinfo Files: c5836b1fcfc470f6d9417a4556d15c52 1456 python optional wand_0.6.11-3.dsc d6706275a8b4ea4c90a39a6f72080632 9000 python optional wand_0.6.11-3.debian.tar.xz b8d62b26ef3685b81023fc8196c74b73 12477 python optional wand_0.6.11-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iI0EARYIADUWIQSD/42dLkLq3fzhpN2I4w6v/UfCtwUCZTtJ6RccaGF2YXJkLmYu YWFzZW5AcGZmdC5ubwAKCRCI4w6v/UfCt6EqAP9T0L0TIToh64H/UAxEpnDiNFT0 KypVTCXdV5eTSmEcdAD/X6LneYBfgPPPpPkXzKxddsmbkTnc0HUHLVdZOpTL4wk= =60DA -END PGP SIGNATURE End Message ---
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign #1054611 kwin 4:5.27.8-1 Bug #1054611 [kde-spectacle] kde-spectacle: Dropping a screencast frame because the compositor is slow Bug reassigned from package 'kde-spectacle' to 'kwin'. No longer marked as found in versions kde-spectacle/23.04.2-2. Ignoring request to alter fixed versions of bug #1054611 to the same values previously set Bug #1054611 [kwin] kde-spectacle: Dropping a screencast frame because the compositor is slow There is no source info for the package 'kwin' at version '4:5.27.8-1' with architecture '' Unable to make a source version for version '4:5.27.8-1' Marked as found in versions 4:5.27.8-1. > End of message, stopping processing here. Please contact me if you need assistance. -- 1054611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: causes RC bug in other package
Processing commands for cont...@bugs.debian.org: > severity 1053924 serious Bug #1053924 [src:timew] timew: autopkgtests fail with man-db 2.12.0 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1053924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:nvme-stas: fails to migrate to testing for too long: autopkgtest regression
Processing control commands:
> close -1 2.3-1
Bug #1054610 [src:nvme-stas] src:nvme-stas: fails to migrate to testing for too
long: autopkgtest regression
Marked as fixed in versions nvme-stas/2.3-1.
Bug #1054610 [src:nvme-stas] src:nvme-stas: fails to migrate to testing for too
long: autopkgtest regression
Marked Bug as done
> block -1 by 1054533
Bug #1054610 {Done: Paul Gevers } [src:nvme-stas]
src:nvme-stas: fails to migrate to testing for too long: autopkgtest regression
1054610 was not blocked by any bugs.
1054610 was not blocking any bugs.
Added blocking bug(s) of 1054610: 1054533
--
1054610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1054610: src:nvme-stas: fails to migrate to testing for too long: autopkgtest regression
Source: nvme-stas Version: 2.2.2-2 Severity: serious Control: close -1 2.3-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1054533 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:nvme-stas has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable fails its own autopkgtest as reported in bug 1054533. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=nvme-stas OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:python-django: fails to migrate to testing for too long: sort of transition
Processing control commands: > close -1 3:4.2.6-1 Bug #1054609 [src:python-django] src:python-django: fails to migrate to testing for too long: sort of transition Marked as fixed in versions python-django/3:4.2.6-1. Bug #1054609 [src:python-django] src:python-django: fails to migrate to testing for too long: sort of transition Marked Bug as done -- 1054609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054609: src:python-django: fails to migrate to testing for too long: sort of transition
Source: python-django Version: 3:3.2.21-1 Severity: serious Control: close -1 3:4.2.6-1 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:python-django has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable causes autopkgtest failes in quite some packages as well as making several packages non-installable as they have a versioned (build) dependency. For some of them, there's no bug report yet notifying the maintainers. 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/msg1.html [2] https://qa.debian.org/excuses.php?package=python-django OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1020507: marked as done (libcleri breaks siridb-server autopkgtest, siridb-server rebuild "fixes" the issue)
Your message dated Thu, 26 Oct 2023 18:03:52 +
with message-id
and subject line Bug#1020507: fixed in libcleri 1.0.1-1
has caused the Debian Bug report #1020507,
regarding libcleri breaks siridb-server autopkgtest, siridb-server rebuild
"fixes" the issue
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.)
--
1020507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcleri
Control: found -1 libcleri/1.0.0-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks
Dear maintainer(s),
With a recent upload of libcleri the autopkgtest of siridb-server fails
in testing when that autopkgtest is run with the binary packages of
libcleri from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
libcleri from testing1.0.0-1
siridb-server from testing2.0.48-1
all others from testingfrom testing
I copied some of the output at the bottom of this report. The test hangs
until the 2:47 hour timeout kills the test. I tried to run the
autopgktest with a rebuild of siridb-server, and that passes quickly.
So, this hints at an ABI breakage. The failures *looks* very much like
the libuv failure of some weeks ago.
Currently this regression is blocking the migration of libcleri to
testing [1]. Can you please investigate the situation?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=libcleri
https://ci.debian.net/data/autopkgtest/testing/amd64/s/siridb-server/26309651/log.gz
autopkgtest [19:27:49]: test http-api: [---
* fixing /etc/siridb/siridb.conf
* restarting siridb-server
* run queries
get-version
["2.0.48"]
new-database
"OK"
new-account
"OK"
change-password
"OK"
drop-account
"OK"
drop-database
"OK"
drop-database again
{"error_msg":"cannot find database 'sampledb'"}
get-accounts
["sa"]
new-database for queries
"OK"
get-databases
["sampledb"]
query data (nothing there)
autopkgtest [22:14:29]: ERROR: timed out on command "su -s /bin/bash
root -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 ||
true; . ~/.profile >/dev/null 2>&1 || true;
buildtree="/tmp/autopkgtest-lxc.9z7k06kk/downtmp/build.AuZ/src"; mkdir
-p -m 1777 --
"/tmp/autopkgtest-lxc.9z7k06kk/downtmp/http-api-artifacts"; export
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.9z7k06kk/downtmp/http-api-artifacts";
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755
"/tmp/autopkgtest-lxc.9z7k06kk/downtmp/autopkgtest_tmp"; export
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.9z7k06kk/downtmp/autopkgtest_tmp";
export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive;
export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=64; unset
LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY
LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo
$$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f
/tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; export
AUTOPKGTEST_NORMAL_USER=debci; export ADT_NORMAL_USER=debci; chmod +x
/tmp/autopkgtest-lxc.9z7k06kk/downtmp/build.AuZ/src/debian/tests/http-api;
touch /tmp/autopkgtest-lxc.9z7k06kk/downtmp/http-api-stdout
/tmp/autopkgtest-lxc.9z7k06kk/downtmp/http-api-stderr;
/tmp/autopkgtest-lxc.9z7k06kk/downtmp/build.AuZ/src/debian/tests/http-api
2> >(tee -a /tmp/autopkgtest-lxc.9z7k06kk/downtmp/http-api-stderr >&2) >
>(tee -a /tmp/autopkgtest-lxc.9z7k06kk/downtmp/http-api-stdout);"
(kind: test)
autopkgtest [22:14:29]: test http-api: ---]
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libcleri
Source-Version: 1.0.1-1
Done: Paul Gevers
We believe that the bug you reported is fixed in the latest version of
libcleri, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Paul Gevers (supplier of updated libcleri package)
(This message was
Bug#1050618: marked as done (rocrand: failing autopkgtests on gfx1030)
Your message dated Thu, 26 Oct 2023 19:33:29 +0200 with message-id <55d7b962-8ca4-44b7-818e-b813c0cb2...@debian.org> and subject line close has caused the Debian Bug report #1050618, regarding rocrand: failing autopkgtests on gfx1030 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.) -- 1050618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rocrand Version: 5.5.1-1 Severity: serious The tests from ci.rocm.debian.net failed on gfx1030 [1]. I'm filing this RC bug to prevent migration to testing. [1] https://ci.rocm.debian.net/data/autopkgtest/unstable/amd64+gfx1030/r/rocrand/83/log.gz --- End Message --- --- Begin Message --- X-CrossAssassin-Score: 45613--- End Message ---
Bug#1050618: Invalid bug
Version: 5.5.1-1 Closing this bug, as it is invalid. rocrand never failed, according to the CI logs (even the linked one).
Bug#1054596: Removal notice: obsolete
Source: haskell-binary-parsers Version: 0.2.4.0-4 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS * Seems unmaintained; Last upload more than 4 years ago * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias
Bug#1054568: marked as done (breezy - broken rust regex build-dependency)
Your message dated Thu, 26 Oct 2023 15:04:44 + with message-id and subject line Bug#1054568: fixed in breezy 3.3.4-1.1 has caused the Debian Bug report #1054568, regarding breezy - broken rust regex build-dependency 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.) -- 1054568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: breezy Version: 3.3.4-1 Severity: serious Tags: patch Breezy build-depends on librust-regex+aho-corasick-dev which is no longer provided (in either physical or virtual form) by rust-regex. Looking at the Cargo.toml files I belive the correct build-dependency is librust-regex-1+default-dev (>= 1.5.4), after changing the build-dependency I was able to get a succesful build. If there are no objections I will likely NMU this in the not too distant future.diff -Nru breezy-3.3.4/debian/changelog breezy-3.3.4/debian/changelog --- breezy-3.3.4/debian/changelog 2023-09-04 17:39:38.0 + +++ breezy-3.3.4/debian/changelog 2023-10-26 02:55:52.0 + @@ -1,3 +1,12 @@ +breezy (3.3.4-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Replace broken build-dependency on "librust-regex+aho-corasick-dev" +with build-dependency on "librust-regex-1+default-dev (>= 1.5.4)" +based on the contents of Cargo.toml. + + -- Peter Michael Green Thu, 26 Oct 2023 02:55:52 + + breezy (3.3.4-1) unstable; urgency=low * New upstream release. diff -Nru breezy-3.3.4/debian/control breezy-3.3.4/debian/control --- breezy-3.3.4/debian/control 2023-09-04 17:39:38.0 + +++ breezy-3.3.4/debian/control 2023-10-26 02:55:40.0 + @@ -31,7 +31,7 @@ debhelper-compat (= 13), librust-pkg-version-dev, librust-pyo3-dev, - librust-regex+aho-corasick-dev, + librust-regex-1+default-dev (>= 1.5.4), rustc Standards-Version: 4.6.2 Rules-Requires-Root: no --- End Message --- --- Begin Message --- Source: breezy Source-Version: 3.3.4-1.1 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of breezy, 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 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated breezy 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: Thu, 26 Oct 2023 02:55:52 + Source: breezy Architecture: source Version: 3.3.4-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Breezy Maintainers Changed-By: Peter Michael Green Closes: 1054568 Changes: breezy (3.3.4-1.1) unstable; urgency=medium . * Non-maintainer upload with maintainers approval. * Replace broken build-dependency on "librust-regex+aho-corasick-dev" with build-dependency on "librust-regex-1+default-dev (>= 1.5.4)" based on the contents of Cargo.toml (Closes: #1054568). Checksums-Sha1: 990a2c8f4be0568e381a45ee7cb64591367aac25 2935 breezy_3.3.4-1.1.dsc dfcfcb7471f1381b5a4bff66a58b26d81c531b15 74792 breezy_3.3.4-1.1.debian.tar.xz 9b9046d1e8550192fef0430f9a441271eaeb47f4 18252 breezy_3.3.4-1.1_source.buildinfo Checksums-Sha256: 7127eedcf314f72e71b9bc623992f59bda61c4c93de5d7bf3b25fa5c52d88911 2935 breezy_3.3.4-1.1.dsc 1f8fa7cc96de9312773a401dfcf3b06fe3348b82a4b487fe1514ce6d0084bf95 74792 breezy_3.3.4-1.1.debian.tar.xz 23b19de258161d4484cbba02aff05e437e8fe08ff9f3de114ecb55f66efc2e1c 18252 breezy_3.3.4-1.1_source.buildinfo Files: f185dfa279f9cd769c43ed10e14148e4 2935 vcs optional breezy_3.3.4-1.1.dsc c032e4bb457edb051a94f10ee305f460 74792 vcs optional breezy_3.3.4-1.1.debian.tar.xz 378c37544f29407aef086d15d03817c8 18252 vcs optional breezy_3.3.4-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmU6etYUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XtGmA//QRz73ZzBvr/s8SGw/wpDGMs1Vug2 mnwKFU15UEYcrcGoYrpCXb1qq08rBBfqoL2vGro32Hw/raG3TlQdFWnDT4cfU+kc pwkGtw5k2pLIxqctj1Fu6U0CmkSoqN0jVKrpEWB1eXZ3aMnewm5hDlTCTq0nniYk oSORruVFlu8XCdURnIEzVSZ4hdRs1ijbzM
Bug#1054591: python3-pyflow: ${VERSION} not expanded in package metadata, causing PEP-440 validation failures
Package: python3-pyflow
Version: 1.1.20-4
Severity: serious
Filing this as serious severity, because it has the risk of breaking
unrelated software.
The background here is that setuptools since 66 has required PEP-440
valid versions for all packages installed on a system. Pip makes a noise
about this since 23.3 in preparation for completely rejecting them in
pip 24.
https://github.com/pypa/setuptools/issues/3772#issuecomment-1384342813
https://github.com/pypa/pip/issues/12063
It looks like ${VERSION} is never expanded in setup.py. I suspect this
is because you are grabbing source from GitHub, and not using tarballs
from "scratch/make_release_tarball.bash"
Please provide a valid version in the package metadata.
$ python3 -c 'import pkg_resources; pkg_resources.require("pyFlow")'
This affects bookworm too, if a virtualenv has --system-site-packages
(less common) and upgraded setuptools (very common).
Stefano
Processed: Block by new required package
Processing commands for cont...@bugs.debian.org: > block 1042099 by 1054588 Bug #1042099 [src:liquidsoap] liquidsoap FTBFS: Error: This expression has type ... but an expression was expected of type 1042099 was not blocked by any bugs. 1042099 was not blocking any bugs. Added blocking bug(s) of 1042099: 1054588 > thanks Stopping processing here. Please contact me if you need assistance. -- 1042099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042099 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053756: marked as done (haskell-lambdahack FTBFS: test: Error when parsing configuration file. Please fix config.ui.ini or remove it altogether.)
Your message dated Thu, 26 Oct 2023 13:04:39 +
with message-id
and subject line Bug#1053756: fixed in haskell-lambdahack 0.11.0.0-4
has caused the Debian Bug report #1053756,
regarding haskell-lambdahack FTBFS: test: Error when parsing configuration
file. Please fix config.ui.ini or remove it altogether.
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.)
--
1053756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-lambdahack
Version: 0.11.0.0-3
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=haskell-lambdahack&ver=0.11.0.0-3
...
Running 1 test suites...
Test suite test: RUNNING...
test: Error when parsing configuration file. Please fix config.ui.ini or remove
it altogether. The details:
Internal failure occurred and the following is to blame:
config file access failed
( ""
, "maxFps"
, fromList
[ ( "additional_commands"
, fromList
[ ( "Cmd_2 "
, "(\"KP_Insert\", ([CmdAim], \"\", ByAimMode AimModeCmd
{exploration = Dashboard, aiming = Accept}))"
)
]
)
, ( "fonts"
, fromList
[ ( "16x16xwBitmap " , "FontMapBitmap \"16x16xw.bdf\" 0" )
, ( "16x16xwScalable "
, "FontMapScalable \"16x16xw.woff\" 16 HintingHeavy 0"
)
, ( "8x8xBitmap " , "FontMapBitmap \"8x8x.fnt\" 2" )
, ( "8x8xbBitmap " , "FontMapBitmap \"8x8xb.fnt\" 2" )
, ( "binaryBold "
, "FontProportional \"BinarySansProLH-Semibold.ttf.woff\" 16
HintingHeavy"
)
, ( "binaryMono "
, "FontMonospace \"BinaryCodeProLH-Bold.ttf.woff\" 14 HintingHeavy"
)
, ( "binaryRegular "
, "FontProportional \"BinarySansProLH-Regular.ttf.woff\" 16
HintingHeavy"
)
, ( "dejavuBold "
, "FontProportional \"DejaVuLGCSans-Bold.ttf.woff\" 13 HintingHeavy"
)
, ( "dejavuMono "
, "FontMonospace \"Hack-Bold.ttf.woff\" 13 HintingHeavy"
)
, ( "dejavuRegular "
, "FontProportional \"DejaVuLGCSans.ttf.woff\" 15 HintingHeavy"
)
]
)
, ( "fontsets"
, fromList
[ ( "16x16xw "
, "FontSet {fontMapScalable = \"16x16xwScalable\", fontMapBitmap =
\"16x16xwBitmap\", fontPropRegular = \"\", fontPropBold = \"\", fontMono =
\"\"}"
)
, ( "8x8x "
, "FontSet {fontMapScalable = \"\", fontMapBitmap = \"8x8xBitmap\",
fontPropRegular = \"\", fontPropBold = \"\", fontMono = \"\"}"
)
, ( "8x8xb "
, "FontSet {fontMapScalable = \"\", fontMapBitmap =
\"8x8xbBitmap\", fontPropRegular = \"\", fontPropBold = \"\", fontMono = \"\"}"
)
, ( "binary "
, "FontSet {fontMapScalable = \"16x16xwScalable\", fontMapBitmap =
\"16x16xwBitmap\", fontPropRegular = \"binaryRegular\", fontPropBold =
\"binaryBold\", fontMono = \"binaryMono\"}"
)
, ( "binaryBold "
, "FontSet {fontMapScalable = \"16x16xwScalable\", fontMapBitmap =
\"16x16xwBitmap\", fontPropRegular = \"binaryBold\", fontPropBold =
\"binaryBold\", fontMono = \"binaryMono\"}"
)
, ( "binaryMono "
, "FontSet {fontMapScalable = \"16x16xwScalable\", fontMapBitmap =
\"16x16xwBitmap\", fontPropRegular = \"binaryMono\", fontPropBold =
\"binaryMono\", fontMono = \"binaryMono\"}"
)
, ( "dejavu "
, "FontSet {fontMapScalable = \"16x16xwScalable\", fontMapBitmap =
\"16x16xwBitmap\", fontPropRegular = \"dejavuRegular\", fontPropBold =
\"dejavuBold\", fontMono = \"dejavuMono\"}"
)
, ( "dejavuBold "
, "FontSet {fontMapScalable = \"16x16xwScalable\", fontMapBitmap =
\"16x16xwScalable\", fontPropRegular = \"dejavuBold\", fontPropBold =
\"dejavuBold\", fontMono = \"dejavuMono\"}"
)
, ( "dejavuBold_original "
, "FontSet {fontMapScalable = \"16x16xwScalable\", fontMapBitmap =
\"16x16xwBitmap\", fontPropRegular = \"dejavuBold\", fontPropBold =
\"dejavuBold\", fontMono = \"dejavuMono\"}"
)
, ( "dejavuMono "
, "FontSet {fontMapScalable = \"16x16xwScalable\", fontMapBitmap =
\"16x16xwBitmap\", fontPropRegular = \"dejavuMono\", fontPropBold =
\"dejavuMono\", fontMono = \"dejavuMono\"}"
)
]
)
, ( "hero_names"
, fromList
[ ( "HeroNa
Processed: really downgrading to normal
Processing commands for cont...@bugs.debian.org: > severity 1054586 normal Bug #1054586 [cream] cream: depends on non-existent package Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1054586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054586: cream: depends on non-existent package
severity 105458 normal thanks El 26/10/23 a las 13:51, jaylaa.maldon...@allfreemail.net escribió: Package: cream Version: 0.43-3.1 Severity: serious Dear Maintainer, cream depends on non-existent package gvim, which is a policy violation. Please fix. Have you actually tried to install cream on bookworm? It works for me: # apt-get install cream Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: ca-certificates fontconfig-config fonts-dejavu-core libasound2 libasound2-data libbrotli1 libbsd0 libcanberra0 libedit2 libexpat1 libfontconfig1 libfreetype6 libgpm2 libice6 libjpeg62-turbo libltdl7 liblua5.2-0 libmotif-common libncurses6 libogg0 libpng16-16 libpython3.11 libpython3.11-minimal libpython3.11-stdlib libreadline8 libruby libruby3.1 libsm6 libsodium23 libsqlite3-0 libtcl8.6 libtdb1 libvorbis0a libvorbisfile3 libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxext6 libxft2 libxm4 libxmu6 libxrender1 libxt6 libyaml-0-2 media-types openssl rake readline-common ruby ruby-net-telnet ruby-rubygems ruby-sdbm ruby-webrick ruby-xmlrpc ruby3.1 rubygems-integration sound-theme-freedesktop tzdata ucf vim-common vim-gui-common vim-motif vim-runtime x11-common Suggested packages: libasound2-plugins alsa-utils libcanberra-gtk0 libcanberra-pulse gpm tcl8.6 readline-doc ri ruby-dev bundler cscope vim-doc Recommended packages: alsa-ucm-conf alsa-topology-conf zip fonts-lato libjs-jquery xxd The following NEW packages will be installed: ca-certificates cream fontconfig-config fonts-dejavu-core libasound2 libasound2-data libbrotli1 libbsd0 libcanberra0 libedit2 libexpat1 libfontconfig1 libfreetype6 libgpm2 libice6 libjpeg62-turbo libltdl7 liblua5.2-0 libmotif-common libncurses6 libogg0 libpng16-16 libpython3.11 libpython3.11-minimal libpython3.11-stdlib libreadline8 libruby libruby3.1 libsm6 libsodium23 libsqlite3-0 libtcl8.6 libtdb1 libvorbis0a libvorbisfile3 libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxext6 libxft2 libxm4 libxmu6 libxrender1 libxt6 libyaml-0-2 media-types openssl rake readline-common ruby ruby-net-telnet ruby-rubygems ruby-sdbm ruby-webrick ruby-xmlrpc ruby3.1 rubygems-integration sound-theme-freedesktop tzdata ucf vim-common vim-gui-common vim-motif vim-runtime x11-common 0 upgraded, 67 newly installed, 0 to remove and 0 not upgraded. Need to get 33.1 MB of archives. After this operation, 128 MB of additional disk space will be used. Do you want to continue? [Y/n] This is also from your own bug report: Versions of packages cream depends on: ii ucf 3.0043+nmu1 ii vim-motif [gvim] 2:9.0.1378-2 gvim is a "virtual package", which other real packages may "provide". If you try to install gvim, this is what happens: # apt-get install gvim Reading package lists... Done Building dependency tree... Done Reading state information... Done Package gvim is a virtual package provided by: vim-motif 2:9.0.1378-2 (= 2:9.0.1378-2) vim-gtk3 2:9.0.1378-2 (= 2:9.0.1378-2) You should explicitly select one to install. However, in your bug report it seems you already have vim-motif installed, so what's exactly the problem you had? (Note: I'm not the cream maintainer, I just noticed this bug and decided to reply just to help diagnosing the problem) Thanks.
Bug#1054586: cream: depends on non-existent package
Package: cream Version: 0.43-3.1 Severity: serious Dear Maintainer, cream depends on non-existent package gvim, which is a policy violation. Please fix. -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-11-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cream depends on: ii ucf 3.0043+nmu1 ii vim-motif [gvim] 2:9.0.1378-2 cream recommends no packages. cream suggests no packages. -- no debconf information
Bug#1040901: Upcoming changes to Debian Linux kernel packages
On Fri, Oct 20, 2023 at 05:54:23PM +0200, Bastian Blank wrote: > Or would it be easier to re-use normal dependency resolving, like: > Kernel-Provides: linux (>> 6.6.1~), linux (<< 6.6.1.) > This would allow full flexibility and re-uses existing code to check > such definitions. Okay, noone complained, so it looks like this should work. Regards, Bastian -- Too much of anything, even love, isn't necessarily a good thing. -- Kirk, "The Trouble with Tribbles", stardate 4525.6
Bug#1054323: fixed in r-cran-tmb 1.9.6-2
Hi Paul,
Am Wed, Oct 25, 2023 at 09:58:42PM +0200 schrieb Paul Gevers:
> > 48s > library('TMB')
> > 48s Error: package or namespace load failed for ‘TMB’ in loadNamespace(j
> > <- i[[1L]], c(lib.loc, .libPaths()), versionCheck = vI[[j]]):
> > 48s namespace ‘Matrix’ 1.6-1 is being loaded, but >= 1.6.1.1 is required
> >
> > which is to be expected if I understand things correctly.
>
> rmatrix is at 1.6-1.1-1, I think you have the version wrong because of the
> double hyphen.
>
> paul@mulciber ~ $ dpkg --compare-versions 1.6-1-1 ge 1.6-1.1 ; echo $?
> 0
Hopefully fixed now. If I would ever meet a three-wishes fairy
my wishes would be:
1. Peace on earth
2. Solve climate crisis
3. Let R people stop using different characters sorting equally
Kind regards
Andreas.
--
http://fam-tille.de
Bug#1051293: Acknowledgement (rocfft: soft lockup with gfx1034)
Control: severity -1 important I'm downgrading this bug, as the suite successfully completed on another Navi24 device [1]. No longer RC, this should allow migration to testing again. Best, Christian [1] https://lists.debian.org/debian-ai/2023/10/msg00044.html
Processed: Re: Bug#1051293: Acknowledgement (rocfft: soft lockup with gfx1034)
Processing control commands: > severity -1 important Bug #1051293 [src:rocfft] rocfft: soft lockup with gfx1034 Severity set to 'important' from 'grave' -- 1051293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024790: ortools: FTBFS everywhere
Hi, 2023-10-12 09:56 CEST, Nilesh Patra: > ortools have a bunch of bugs filed against it. Do you intend to take > care of them sometime soon? Not really. I packaged it because I needed the python package as a dependency, but I lost interest and did not make it to package the final software. The package maintainer is the Debian Science Team so that anyone can contribute to the packaging, no questions asked. If someone is willing to take the Uploader role, I can commit that into the repo. Bests, Agathe.
Bug#997299:
أود أن أناقش معك فرصة عمل أساسية وأحتاج أيضًا إلى مشاركتك فيها. أنا متأكد جدًا من أنها ستكون مفيدة لكلا الطرفين ، وعند الإقرار بردك الذي أنتظره بصبر ، سأقدم لك المزيد من التفاصيل. شكرًا لك أطيب التحيات نفيد علي
Bug#1054581: asdf: Missing dependency on asdf-unit-schemas (breaks pkg_resources)
Package: asdf
Version: 2.14.3-1
Severity: serious
asdf's upstream requirements declare a dependency on asdf-unit-schemas,
but this doesn't exist in Debian, and isn't a dependency.
The relevant upstream change is https://github.com/asdf-format/asdf/pull/1210
It seems this used to be part of asdf-standard, but got moved into its
own module.
I see the relevant schemas still exist in asdf-standard in Debian.
However, missing this dependency this breaks Python pkg_resources, that
attempts to validate Python requirements.
Filing this as serious, because it breaks unrelated software when asdf
is installed.
In bookworm:
$ python3 -c 'import pkg_resources; pkg_resources.require("asdf")'
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 956, in
require
needed = self.resolve(parse_requirements(requirements))
^^
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 815, in
resolve
dist = self._resolve_dist(
^^^
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 856, in
_resolve_dist
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'asdf-unit-schemas>=0.1.0' distribution
was not found and is required by asdf
The same thing happens in unstable.
If you are certain that you don't need a (non-optional) Python
dependency, the best thing to do is to patch it out of the requirements
in pyproject.toml.
Stefano
Bug#1031346:
أود أن أناقش معك فرصة عمل أساسية وأحتاج أيضًا إلى مشاركتك فيها. أنا متأكد جدًا من أنها ستكون مفيدة لكلا الطرفين ، وعند الإقرار بردك الذي أنتظره بصبر ، سأقدم لك المزيد من التفاصيل. شكرًا لك أطيب التحيات نفيد علي
Bug#1054568: breezy - broken rust regex build-dependency
Hi Peter, Please do go ahead and NMU this. Thanks! Cheers, Jelmer On Thu, Oct 26, 2023 at 04:19:28AM +0100, Peter Green wrote: > Package: breezy > Version: 3.3.4-1 > Severity: serious > Tags: patch > > Breezy build-depends on librust-regex+aho-corasick-dev which is no longer > provided (in either physical or virtual form) by rust-regex. > > Looking at the Cargo.toml files I belive the correct build-dependency is > librust-regex-1+default-dev (>= 1.5.4), after changing the build-dependency > I was able to get a succesful build. > > If there are no objections I will likely NMU this in the not too distant > future. > diff -Nru breezy-3.3.4/debian/changelog breezy-3.3.4/debian/changelog > --- breezy-3.3.4/debian/changelog 2023-09-04 17:39:38.0 + > +++ breezy-3.3.4/debian/changelog 2023-10-26 02:55:52.0 + > @@ -1,3 +1,12 @@ > +breezy (3.3.4-1.1) UNRELEASED; urgency=medium > + > + * Non-maintainer upload. > + * Replace broken build-dependency on "librust-regex+aho-corasick-dev" > +with build-dependency on "librust-regex-1+default-dev (>= 1.5.4)" > +based on the contents of Cargo.toml. > + > + -- Peter Michael Green Thu, 26 Oct 2023 02:55:52 > + > + > breezy (3.3.4-1) unstable; urgency=low > >* New upstream release. > diff -Nru breezy-3.3.4/debian/control breezy-3.3.4/debian/control > --- breezy-3.3.4/debian/control 2023-09-04 17:39:38.0 + > +++ breezy-3.3.4/debian/control 2023-10-26 02:55:40.0 + > @@ -31,7 +31,7 @@ > debhelper-compat (= 13), > librust-pkg-version-dev, > librust-pyo3-dev, > - librust-regex+aho-corasick-dev, > + librust-regex-1+default-dev (>= 1.5.4), > rustc > Standards-Version: 4.6.2 > Rules-Requires-Root: no
Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory
Hi,
On 04/10/23 at 21:25 +0100, Mark Hindley wrote:
> Control: tags -1 moreinfo
>
> Ian
>
> On Wed, Sep 27, 2023 at 10:33:32PM +0100, Ian Jackson wrote:
> > Mark Hindley writes ("Bug#1052942: insserv: FTBFS: insserv: Could not read
> > script nolsbheader: No such file or directory"):
> > > Thanks for this. However, I am currently unable to repoduce this
> > > failure in my customary pbuilder setup. And it doesn't appear at
> > > reproducible builds either[1]
> >
> > I just tried this myself with my usual sbuild setup and it succeeded
> > there too[1].
>
>
> Thanks for your confirmation.
>
> > Lucas, I think something from your rebuild environment
> > (a chroot of some kind I presume) must be triggering this failure. Is
> > there some way we can reproduce it more precisely (eg, a buildinfo
> > file?)
>
> Yes, I agree a buildinfo file might give a hint.
>
> > I looked at the build log
> > http://qa-logs.debian.net/2023/09/25/insserv_1.24.0-1_unstable.log
> > and compared it to the one from my sbuild, using diff. There are a
> > lot of changes to the "furniture" but also there are noise changes to
> > the output of the insserv test suite, including ordring changes of
> > passing tests. This seemed surprising to me.
> >
> > Mark, is the insserv test suite supposed to produce deterministic
> > output ?
>
> I have never had the need to look at the testsuite since I started looking
> after
> the package. A quick look now doesn't immediately reveal something that would
> obviously change the order of the tests.
>
> I tried again locally with make -j8 and still could not reproduce any failure.
It also fails with -j1: it does not look like a concurrency issue. See
attached log.
Lucas
sbuild (Debian sbuild) 0.85.0 (04 January 2023) on ip-10-84-234-181
+==+
| insserv 1.24.0-1 (amd64) Thu, 26 Oct 2023 07:58:20 + |
+==+
Package: insserv
Version: 1.24.0-1
Source Version: 1.24.0-1
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full
I: NOTICE: Log filtering will replace
'var/run/schroot/mount/sid-amd64-sbuild-9b6ecbbe-48ed-462f-8959-f9b693a34744'
with '<>'
I: NOTICE: Log filtering will replace 'build/insserv-MtNjSQ/resolver-hdop7y'
with '<>'
+--+
| Update chroot|
+--+
Hit:1 http://127.0.0.1:12990/debian sid InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+--+
| Fetch source files |
+--+
Check APT
-
Checking available source versions...
Download source files with APT
--
Reading package lists...
NOTICE: 'insserv' packaging is maintained in the 'Git' version control system
at:
https://salsa.debian.org/debian/insserv.git
Please use:
git clone https://salsa.debian.org/debian/insserv.git
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 114 kB of source archives.
Get:1 http://127.0.0.1:12990/debian sid/main insserv 1.24.0-1 (dsc) [1996 B]
Get:2 http://127.0.0.1:12990/debian sid/main insserv 1.24.0-1 (tar) [76.5 kB]
Get:3 http://127.0.0.1:12990/debian sid/main insserv 1.24.0-1 (diff) [35.8 kB]
Fetched 114 kB in 0s (1611 kB/s)
Download complete and in download only mode
I: NOTICE: Log filtering will replace 'build/insserv-MtNjSQ/insserv-1.24.0'
with '<>'
I: NOTICE: Log filtering will replace 'build/insserv-MtNjSQ' with '<>'
+--+
| Install package build dependencies |
+--+
Setup apt archive
-
Merged Build-Depends: bash-completion, debhelper-compat (= 12), po-debconf,
build-essential, fakeroot
Filtered Build-Depends: bash-completion, debhelper-compat (= 12), po-debconf,
build-essential, fakeroot
dpkg-deb: building package 'sbuild-build-depends-main-dummy' in
'/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
Ign:1 copy:/<>/apt_archive ./ InRelease
Get:2 copy:/<>/apt_archive ./ Release [609 B]
Ign:3 copy:/<>/apt_archive ./ Release.gpg
Get:4 copy:/<>/apt_archive ./ Sources [646 B]
Get:5 copy:/<>/apt_archive ./ Packages [678 B]
Fetched 1933 B in 0s (80.7 kB/s)
Reading package lists...
Reading package lists...
Install main build dependenc
