Bug#1004119: fricas: libc6 2.33 bug causes assert; patch is upstream
Package: fricas Version: 1.3.7-3 Severity: grave Since recent update to libc6 2.33 in testing it broke fricas, please use the patch upstream in this bug: https://savannah.gnu.org/bugs/index.php?60161 https://git.savannah.gnu.org/cgit/gcl.git/commit/?id=26a7a50d3d2ac4bc27d082f7321d16dba2b920cf Maxima should be also affected. P.S. Looks like https://sources.debian.org/patches/gcl/2.6.12-117/ should be compiled into fricas? Please note that I was able to see assert on WSLv1 but somehow it just fails in real machine. Another bug in glibc? Thanks.
Bug#1004107: meson: flaky autopkgtest on armhf: dictionary changed size during iteration -> timeout
On Thu, 20 Jan 2022 at 23:33, Paul Gevers wrote: > I looked at the results of the autopkgtest of you package on armhf > because it was showing up as a regression for the upload of > python-defaults and setuptools. I noticed that the test regularly fails, > what's worse, it also seems to hang as the test is killed because it > hits an autopkgtest timeout. If we look at the backtrace: > Running tests with 160 workers > Exception in thread Thread-1: > Traceback (most recent call last): >File "/usr/lib/python3.9/threading.py", line 973, in _bootstrap_inner > self.run() >File "/usr/lib/python3.9/concurrent/futures/process.py", line 317, in run > result_item, is_broken, cause = self.wait_result_broken_or_wakeup() >File "/usr/lib/python3.9/concurrent/futures/process.py", line 376, in > wait_result_broken_or_wakeup > worker_sentinels = [p.sentinel for p in self.processes.values()] >File "/usr/lib/python3.9/concurrent/futures/process.py", line 376, in > > worker_sentinels = [p.sentinel for p in self.processes.values()] > RuntimeError: dictionary changed size during iteration This is all Python's internal code. Further, Meson does not do any fancy threading stuff itself, it uses Python's thread and process executors to queue up a bunch of work and then wait for it to be done. According to Python's documentation you don't need to do any locking or similar to submit new work, you can call the submit method directly. All of this would seem to indicate that the issue might lie somewhere in Python's multithreading code. At the very least I have no idea how I should go about debugging that issue.
Bug#965458: marked as done (chntpw: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Thu, 20 Jan 2022 23:03:40 + with message-id and subject line Bug#965458: fixed in chntpw 140201-1 has caused the Debian Bug report #965458, regarding chntpw: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965458 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: chntpw Version: 1.0-1.1 Severity: normal Usertags: compat-5-6-removal Hi, The package chntpw uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: chntpw Source-Version: 140201-1 Done: Javier Fernández-Sanguino Peña We believe that the bug you reported is fixed in the latest version of chntpw, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Javier Fernández-Sanguino Peña (supplier of updated chntpw 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, 20 Jan 2022 22:35:49 +0100 Source: chntpw Architecture: source Version: 140201-1 Distribution: unstable Urgency: medium Maintainer: Javier Fernández-Sanguino Peña Changed-By: Javier Fernández-Sanguino Peña Closes: 762508 803883 803884 803888 902549 965458 Changes: chntpw (140201-1) unstable; urgency=medium . [ Fabio Fantoni ] * switch package to use dh and bump compat to 13 (Closes: #965458) * add d/source/format quilt * include the Makefile changes that was out of d/patches in 01_port_to_gcrypt.patch . [ Helmut Grohne ] * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #902549) * Remove unused/wrong INSTALL_PROGRAM variable. . [ Javier Fernández-Sanguino ] * Add VCS fields in debian/control * Updated Standards-Version * debian/watch: updated to version 4 * Use the original version numbering to avoid confusing uscan * Add description to all patches (lintian fix) * Apply patch to fix descriptions in source code and typos (Closes: 803884, 803883) * Apply patch to enable sampasswd writing to the HIVE file (Closes: 803888) * Apply patch to make it possible to read files when the filesystem is read-only (Closes: 762508) * Add samunlock tool developed by Adrian Gibanel Lopez and published in https://github.com/rescatux/chntpw Checksums-Sha1: 60f95a646af8cf8b7df8aa1063d509355c880975 1901 chntpw_140201-1.dsc e5f9efd16bd78b8da8a6985c0617b555aa85c5e4 436864 chntpw_140201.orig.tar.xz fd2b645d57e724f2ee73d3b568905166263396b7 42276 chntpw_140201-1.debian.tar.xz 71bc8c1b038eb3bd918f9494e77b56c7036312c4 6988 chntpw_140201-1_i386.buildinfo Checksums-Sha256: 62129ebfed494d1bb5db6471d684d5c8521c0877d7ecffad4d737825214db03d 1901 chntpw_140201-1.dsc 56849d366043a6335449cd83c6cd3cb31c041300ae17d388728b4c2a16d1f4ed 436864 chntpw_140201.orig.tar.xz 6dd493d28eaac21b14b82240c0864270d25f98c84188c3f07ab9387d4ddd02e3 42276 chntpw_140201-1.debian.tar.xz 7e005210e301f810db369176e1166dd34f25de5fb98bd7f8279fc983092aafcd 6988 chntpw_140201-1_i386.buildinfo Files:
Bug#965458: chntpw: Removal of obsolete debhelper compat 5 and 6 in bookworm
Dear Fabio and Adrian, I have just uploaded version 140201-1 to the archive based on Fabio's work in Salsa. I have taken some time to fix some additional bugs as well as incorporate some patches / improvements published in Github by Adrian Gibanel Lopez (https://github.com/rescatux/chntpw/) some of which had been also submitted to Debian. Note that the changes are in this repository: https://salsa.debian.org/debian/chntpw (I restored there the old GIT repo from Alioth). Thank you both for your work Javier On Wed, 19 Jan 2022 at 15:27, Fabio Fantoni wrote: > Hi, in recent days I had prepared a git for chntpw, contacted the > maintainer, then prepared the patches to convert to dh and compat 13 and > also solve other few issues. > > the maintainer is still active and he told me he would revise my > changes, anyway thanks to Adrian Bunk for your pending patch/build that > delayed remove from testing (in case the maintainer does not have time > to review and do the new build) > >
Bug#1004111: unattended-upgrades: regression: packages with conffile prompts are no longer skipped, leading to upgrade failures
Package: unattended-upgrades Version: 2.8 Severity: serious Hi All, This bug has showing up on this end in unattended-upgrades 2.8 on my Raspberry Pi Model 3B+ running Raspberry Pi OS 11.2 since January 6, 2022. I'm emailing this list because the Raspberry Pi OS repos list Michael Vogt < m...@debian.org> as unattended-upgrade's maintainer for that distro: # apt show unattended-upgrades Package: unattended-upgrades Version: 2.8 Priority: optional Section: admin Maintainer: Michael Vogt Here is proof of the Raspberry Pi OS version: $ cat /etc/debian_version 11.2 & of the kernel version: $ uname -a Linux RaspberryPi3ModelBPlus 5.10.63-v7+ #1496 SMP Wed Dec 1 15:58:11 GMT 2021 armv7l GNU/Linux Here's the error email I received from root on January 6, 2022: Unattended upgrade result: All upgrades installed Packages that attempted to upgrade: chromium-browser chromium-browser-l10n chromium-codecs-ffmpeg-extra lxplug-updater Packages with upgradable origin but kept back: Raspberry Pi Foundation stable: chromium-codecs-ffmpeg-extra chromium-browser lxplug-updater chromium-browser-l10n Unattended-upgrades log: Enabled logging to syslog via daemon facility Starting unattended upgrades script Allowed origins are: origin=Debian,codename=bullseye,label=Debian, origin=Debian,codename=bullseye,label=Debian-Security, origin=Debian,codename=bullseye-security,label=Debian-Security, origin=* Initial blacklist: Initial whitelist (not strict): Packages that will be upgraded: chromium-browser chromium-browser-l10n chromium-codecs-ffmpeg-extra lxplug-updater Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades -dpkg.log Package chromium-browser is kept back because a related package is kept back or due to local apt_preferences(5). Package chromium-browser-l10n is kept back because a related package is kept back or due to local apt_preferences(5). Package chromium-codecs-ffmpeg-extra is kept back because a related package is kept back or due to local apt_preferences(5). Package lxplug-updater is kept back because a related package is kept back or due to local apt_preferences(5). & the error email I received today: Unattended upgrade result: All upgrades installed Packages that attempted to upgrade: chromium-browser chromium-browser-l10n chromium-codecs-ffmpeg-extra libraspberrypi-bin libraspberrypi-dev libraspberrypi-doc libraspberrypi0 linux-libc-dev lynis raspberrypi-bootloader raspberrypi-kernel vcdbg Packages with upgradable origin but kept back: Raspberry Pi Foundation stable: chromium-codecs-ffmpeg-extra raspberrypi-bootloader raspberrypi-kernel libraspberrypi-doc chromium-browser-l10n libraspberrypi0 chromium-browser libraspberrypi-dev vcdbg libraspberrypi-bin CISOfy stable: lynis Package installation log: Log started: 2022-01-20 06:45:51 apt-listchanges: Reading changelogs... apt-listchanges: Reading changelogs... Preparing to unpack .../linux-libc-dev_1%3a1.20220118-1_armhf.deb ... Unpacking linux-libc-dev:armhf (1:1.20220118-1) over (1:1.20211201~buster-1) ... Setting up linux-libc-dev:armhf (1:1.20220118-1) ... Log ended: 2022-01-20 06:46:11 Unattended-upgrades log: Enabled logging to syslog via daemon facility Starting unattended upgrades script Allowed origins are: origin=Debian,codename=bullseye,label=Debian, origin=Debian,codename=bullseye,label=Debian-Security, origin=Debian,codename=bullseye-security,label=Debian-Security, origin=* Initial blacklist: Initial whitelist (not strict): Packages that will be upgraded: chromium-browser chromium-browser-l10n chromium-codecs-ffmpeg-extra libraspberrypi-bin libraspberrypi-dev libraspberrypi-doc libraspberrypi0 linux-libc-dev lynis raspberrypi-bootloader raspberrypi-kernel vcdbg Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades -dpkg.log Package chromium-browser is kept back because a related package is kept back or due to local apt_preferences(5). Package chromium-browser-l10n is kept back because a related package is kept back or due to local apt_preferences(5). Package chromium-codecs-ffmpeg-extra is kept back because a related package is kept back or due to local apt_preferences(5). Package libraspberrypi-bin is kept back because a related package is kept back or due to local apt_preferences(5). Package libraspberrypi-dev is kept back because a related package is kept back or due to local apt_preferences(5). Package libraspberrypi-doc is kept back because a related package is kept back or due to local apt_preferences(5). Package libraspberrypi0 is kept back because a related package is kept back or due to local apt_preferences(5). Package lynis is kept back because a related package is kept back or due to local apt_preferences(5). Package raspberrypi-bootloader is kept back because a related package is kept back or due to local apt_preferences(5). Package raspberrypi-kernel is kept back because a related package is kept back or due to local apt_preferences(5). Package vcdbg is kept back
Bug#991449: marked as done (fix for CVE-2021-32749 breaks systems with mail from bsd-mailx)
Your message dated Thu, 20 Jan 2022 22:34:04 + with message-id and subject line Bug#991449: fixed in fail2ban 0.11.2-5 has caused the Debian Bug report #991449, regarding fix for CVE-2021-32749 breaks systems with mail from bsd-mailx 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.) -- 991449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fail2ban Version: 0.11.2-2 Severity: important According to upstreams security advisory [1] CVE-2021-32749 only affects systems where the mail utility from the mailutils package is installed. The recommended fix [2] is to add a new parameter "-E" to the invocation of mail. Unfortunately this fix breaks other implementations of mail, especially the version from package bsd-mailx. Thus upstream recommends in the Workaround section of the advisory to only manually patch the systems where the mailutils-mail is used. According to popcon the numbers of systems where mailutils-mail and bsd-mailx-mail are used is about even. So applying upstreams fix now breaks about half of the systems using fail2ban. The corresponding upstream bug #3069 [3] did not get any attention yet. Thorsten [1] https://github.com/fail2ban/fail2ban/security/advisories/GHSA-m985-3f3v-cwmm [2] https://github.com/fail2ban/fail2ban/commit/410a6ce5c80dd981c22752da034f2529b5eee844 [3] https://github.com/fail2ban/fail2ban/issues/3069 --- End Message --- --- Begin Message --- Source: fail2ban Source-Version: 0.11.2-5 Done: Sylvestre Ledru We believe that the bug you reported is fixed in the latest version of fail2ban, 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 991...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated fail2ban 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, 20 Jan 2022 23:21:44 +0100 Source: fail2ban Architecture: source Version: 0.11.2-5 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Sylvestre Ledru Closes: 991449 Changes: fail2ban (0.11.2-5) unstable; urgency=medium . * Revert the CVE-2021-32749 fix (Closes: #991449) Debian bookworm has the mailutils version with the proper fix Checksums-Sha1: e8621ee29543828d5aafc99a39ae1f1d96a95220 2045 fail2ban_0.11.2-5.dsc b70db24159edda4d9d0d4eaae8405fb80f8e6676 31272 fail2ban_0.11.2-5.debian.tar.xz 9fc79fc15a61b122c2418edf0114223d07b005c3 6740 fail2ban_0.11.2-5_amd64.buildinfo Checksums-Sha256: 07a49a571b3eb9c5f5973b7870c864f3972cca2302be0525f3eaba7f4254 2045 fail2ban_0.11.2-5.dsc 89871941c3d806981a9f9ad5cb31d0787751651c55feddf982854a963cf5bbf7 31272 fail2ban_0.11.2-5.debian.tar.xz f3bd4416a802b2d1c3093cf9b2fba6a5269ccae06c76517f2f063ca6991c0c2c 6740 fail2ban_0.11.2-5_amd64.buildinfo Files: fd46b16e284d4f78db5e49b95fc9949d 2045 net optional fail2ban_0.11.2-5.dsc 41b96eefbc2cb82b1c4119ae68afdfc8 31272 net optional fail2ban_0.11.2-5.debian.tar.xz ccf4bb39fdda162c227ffc27d2802abd 6740 net optional fail2ban_0.11.2-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmHp4Q8ACgkQfmUo2nUv G+GQCw//V4CH94zXa++zLpU0KPTQEy1Fvoz8Kont9tSnw31zq8oUqB0e95xDfhkF HEAt3AlkorGejm8kq+p9g/mkonTfUw+FWePKotWcmkgaunknsVFe3GG80v9sgrUs +7LSxmFQgTHSs0ek4OfyZWgMwPhXyUsHU75F7KsokwsVIkR6vuztgAcGDgFFo8TR u63UhnkLAmKxidBDXkGLm1xpFwYeTm72T8Jp9QUwo8A7B6hhFciWFKEsWZDjKMIw mt6g7Cp8XVcZ91piYPN3owVXnAx1amYKE/h9XVzVmvzcy0Q6roqnxdhDXQdzDEdo XamSp646hGqXcfNqVezx/Xrsrc8JUqoqRVMv0bv207mTo6knMRdcCMYwWXx0m+Lk NpiXbckkWb4JS3S+GfqqdDepbqlnxpucLswb/DcMA7EDmQiMH9smgQ6zZ7adT3rT UNj8GlupX2flYSkMYb3axQSYCvV+BU2WIjPwTGvdFXhqnYP7gWDOseTmBoUxmhbW aZR7q2OEkPeRA98dS7VXoBxEbRLxuWNkF9RW79Byc5hQgixA/PR9Ys2/agC4CIQi pigiDSb/N8KM77r4IVpmqXOMD6NhGjWuR6VVzrjpqbdG2oSUd2Q66pd5nk5x22EI RMmrqvmpLvoUhjgKj1MRs+ibrmxYP2w6SOjDoQ1LCSiBXYc7RYM= =C73b -END PGP SIGNATURE End Message ---
Processed: bug 1002343 is forwarded to https://github.com/aio-libs/aiosmtpd/issues/277
Processing commands for cont...@bugs.debian.org:
> forwarded 1002343 https://github.com/aio-libs/aiosmtpd/issues/277
Bug #1002343 [src:python-aiosmtpd] python-aiosmtpd: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit
code 13
Set Bug forwarded-to-address to
'https://github.com/aio-libs/aiosmtpd/issues/277'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1002343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: found 1001809 in 2.0.18+dfsg-3
Processing commands for cont...@bugs.debian.org:
> found 1001809 2.0.18+dfsg-3
Bug #1001809 {Done: Simon McVittie } [libsdl2] libsdl2/2.0.18
breaks osk-sdl autopkgtest: Testing osk toggle button and 'mouse' key input
There is no source info for the package 'libsdl2' at version '2.0.18+dfsg-3'
with architecture ''
Unable to make a source version for version '2.0.18+dfsg-3'
Marked as found in versions 2.0.18+dfsg-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1001809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1003964: pandoc doesn't start: error while loading shared libraries: libcmark-gfm.so.0.29.0.gfm.0
On 2022-01-20 11:51:48 -0800, Keith Packard wrote: > Jonas Smedegaard writes: > > > Looks good to me. But then again, I was the one with the wrong approach > > here, so not sure how much my input can be trusted ;-) > > And I'm the one who packaged this initially with *completely* bogus > names. > > I'm a bit uncertain about the Replaces and Breaks clauses in the control > file; we need to make sure to remove the current packages which are > installing the libraries with the same filename. I think I've got it > right, but another bit of review would be appreciated. > > I'll wait a week to see if Sebastian has time to respond, and if we're > still both reasonably happy with this approach, I'll go ahead and upload > it (alas, in binary form as is required for the New queue). Looks good to me. The Breaks+Replaces can be dropped after the next upstream release. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: Move where it was fixed
Processing commands for cont...@bugs.debian.org:
> reassign 1001809 libsdl2 2.0.18-3
Bug #1001809 {Done: Simon McVittie } [src:osk-sdl,
src:libsdl2] libsdl2/2.0.18 breaks osk-sdl autopkgtest: Testing osk toggle
button and 'mouse' key input
Bug reassigned from package 'src:osk-sdl, src:libsdl2' to 'libsdl2'.
No longer marked as found in versions osk-sdl/0.66-2 and libsdl2/2.0.18-3.
No longer marked as fixed in versions libsdl2/2.0.18+dfsg-4.
Bug #1001809 {Done: Simon McVittie } [libsdl2] libsdl2/2.0.18
breaks osk-sdl autopkgtest: Testing osk toggle button and 'mouse' key input
There is no source info for the package 'libsdl2' at version '2.0.18-3' with
architecture ''
Unable to make a source version for version '2.0.18-3'
Marked as found in versions 2.0.18-3.
> fixed 1001809 2.0.18+dfsg-4
Bug #1001809 {Done: Simon McVittie } [libsdl2] libsdl2/2.0.18
breaks osk-sdl autopkgtest: Testing osk toggle button and 'mouse' key input
There is no source info for the package 'libsdl2' at version '2.0.18+dfsg-4'
with architecture ''
Unable to make a source version for version '2.0.18+dfsg-4'
Marked as fixed in versions 2.0.18+dfsg-4.
> affects 1001809 src:osk-sdl
Bug #1001809 {Done: Simon McVittie } [libsdl2] libsdl2/2.0.18
breaks osk-sdl autopkgtest: Testing osk toggle button and 'mouse' key input
Added indication that 1001809 affects src:osk-sdl
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1001809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1002527: postinst ignores USER from /etc/default/milter-greylist when invoking chown ... /var/lib/milter-greylist
On Thu, Dec 23, 2021 at 02:12:04PM -0500, Marvin Renich wrote: >... > With an existing installation of milter-greylist set up to work with > chrooted postfix (i.e. USER="postfix" in /etc/default/milter-greylist), > every upgrade sets the owner of the directory /var/lib/milter-greylist > to "greylist" regardless of the setting of USER. This effectively > breaks postfix, as it will no longer deliver mail until the problem is > resolved. > > Note that the particular system hosting my mail server is still running > sysvinit, not systemd. I do not know how milter-greylist configures the > user under systemd, but the postinst has "greylist" hardcoded, so I > suspect that if the sysadmin has configured a different user, this will > break under systemd, as well. >... With systemd the problem likely doesn't exist since the user is hardcoded also in the service file: /lib/systemd/system/milter-greylist.service: ExecStart=/usr/sbin/milter-greylist -u greylist > ...Marvin >... cu Adrian
Bug#1004047: marked as done (python-django-dbconn-retry: autopkgtest failure: Authentication failure)
Your message dated Thu, 20 Jan 2022 21:36:50 + with message-id and subject line Bug#1004047: fixed in python-django-dbconn-retry 0.1.6-2 has caused the Debian Bug report #1004047, regarding python-django-dbconn-retry: autopkgtest failure: Authentication failure 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.) -- 1004047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-django-dbconn-retry Version: 0.1.6-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package python-django-dbconn-retry, great. However, it fails. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. 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=python-django-dbconn-retry https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-django-dbconn-retry/18488294/log.gz Password: su: Authentication failure autopkgtest [16:49:14]: test upstream OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-django-dbconn-retry Source-Version: 0.1.6-2 Done: Michael Fladischer We believe that the bug you reported is fixed in the latest version of python-django-dbconn-retry, 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 1004...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Fladischer (supplier of updated python-django-dbconn-retry 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: Thu, 20 Jan 2022 21:01:25 + Source: python-django-dbconn-retry Architecture: source Version: 0.1.6-2 Distribution: unstable Urgency: low Maintainer: Debian Python Team Changed-By: Michael Fladischer Closes: 1004047 Changes: python-django-dbconn-retry (0.1.6-2) unstable; urgency=low . * Set restrictions on autopkgtest and use runuser to switch users (Closes: #1004047). Checksums-Sha1: c3f767e325eddebd0ce365ddcbb13ff34d515b14 1965 python-django-dbconn-retry_0.1.6-2.dsc 4be639ec72a2adbafcc7456f4bb011491384bb4f 2964 python-django-dbconn-retry_0.1.6-2.debian.tar.xz afd5d70e0dbff241106b04df3d3477baba9255b0 6433 python-django-dbconn-retry_0.1.6-2_arm64.buildinfo Checksums-Sha256: 8f72505d0a7a5eb5699d947ffb618686449c9fa06ab869851fa7e302378a36d2 1965 python-django-dbconn-retry_0.1.6-2.dsc b7502752696b6d827303c55c8d88fdc8d1995ae3c4622c26f47c17a8890400e7 2964 python-django-dbconn-retry_0.1.6-2.debian.tar.xz ca5a306486d18884346ce068a33d29d19e6cea0b2a5895e4fbf07f4094040c00 6433 python-django-dbconn-retry_0.1.6-2_arm64.buildinfo Files: 2c9d1f9ff2ffe0692938a624ce62c5c3 1965 python optional python-django-dbconn-retry_0.1.6-2.dsc aa0becab0af6f7fe46e45410afbda100 2964 python optional python-django-dbconn-retry_0.1.6-2.debian.tar.xz aeff7e2c67a3dda34713618743772ecd 6433 python optional python-django-dbconn-retry_0.1.6-2_arm64.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAmHpzlAACgkQ/9PIi5l9 0WqPGgf9EYuHMQ1YnJHtfV8xK9Hmxk2epMGn755lHutXZtdG/Nka5E7HHllfPxUX OvG77AGcJupuUsoHVpDQR1zsfGJw2/zkoTKp/a1cJ+OgEPkl1skzmfFVVK1Hx0je KCycQVsgPAiqDdg3fZfTsd336i+FrNW4dTOpzjGKhC4bP4dU03hO4TcwV4w2nW5f LUaUrbWco0wg6Pn1v2hwxv0w/hncsPqfMBVgUILex6wwGuLmS7y5MfcYWyAPWkl+ w69ByiD9f9Zgbx19IdzYiCPDnaS33LQMnV0wp44vtkNtferCgU/Z/MH8LEZbv59K vLwn1L821D3e8l7wc8j23VURs25o9g== =4qub -END PGP SIGNATURE End Message ---
Bug#1004109: xdg-utils-cxx FTBFS on !amd64/arm64: symbol differences
Source: xdg-utils-cxx Version: 1.0.1-3 Severity: serious Tags: ftbfs Control: block 1002520 by -1 https://buildd.debian.org/status/package.php?p=xdg-utils-cxx
Processed: xdg-utils-cxx FTBFS on !amd64/arm64: symbol differences
Processing control commands:
> block 1002520 by -1
Bug #1002520 {Done: Paul Gevers } [src:xdg-utils-cxx]
src:xdg-utils-cxx: fails to migrate to testing for too long: FTBFS everywhere
except amd64, arm64 and kfreebsd-amd64
1002520 was not blocked by any bugs.
1002520 was not blocking any bugs.
Added blocking bug(s) of 1002520: 1004109
--
1002520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002520
1004109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#999768: lintian: false report: adopted-extended-field
On Sun, Nov 21, 2021 at 07:23:32PM +0100, Francesco Poli wrote: > On Wed, 17 Nov 2021 00:56:11 +0100 Guillem Jover wrote: > [...] > > The same with XS-Go-Import-Path, and I guess a bunch of other fields > > that are unknown to dpkg-dev. > > Same here with my package (apt-listbugs). Ditto for (X-)Python-Version (though X-Python3-Version is correctly not included in the list of adopted fields). Julian
Bug#1004107: meson: flaky autopkgtest on armhf: dictionary changed size during iteration -> timeout
Source: meson Version: 0.56.2-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky timeout Dear maintainer(s), I looked at the results of the autopkgtest of you package on armhf because it was showing up as a regression for the upload of python-defaults and setuptools. I noticed that the test regularly fails, what's worse, it also seems to hang as the test is killed because it hits an autopkgtest timeout. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. In this case, Release Team members had to investigate if curl was OK to go into the next Stable point release. Don't hesitate to reach out if you need help and some more information from our infrastructure. Please note that the host we run our armhf tests on is very powerful. It has 160 cores and 255 GB RAM. This is sometimes the root cause of test that fail. It seems that before we switch to this host, the test was more reliable. Paul https://ci.debian.net/packages/m/meson/testing/amd64/ E.g. https://ci.debian.net/data/autopkgtest/testing/armhf/m/meson/18519155/log.gz Ran 462 tests in 569.524s OK (skipped=66) Meson build system 0.61.0 Unit Tests pytest-xdist not found, using unittest instead Total time: 569.540 seconds Meson build system 0.61.0 Project Tests Using python 3.9.9 (main, Jan 12 2022, 16:10:51) host machine compilers c : [gcc] cc (gcc 11.2.0 "cc (Debian 11.2.0-13) 11.2.0") cpp: [gcc] c++ (gcc 11.2.0 "c++ (Debian 11.2.0-13) 11.2.0") cs : [mono] mcs (mono 6.8.0.105) cuda : [not found] cython : [not found] d : [llvm] ldc2 (llvm 1.28.0 "LDC - the LLVM D compiler (1.28.0):") fortran: [gcc] gfortran (gcc 11.2.0 "GNU Fortran (Debian 11.2.0-13) 11.2.0") java : [unknown] javac (unknown 11.0.13) objc : [gcc] cc (gcc 11.2.0) objcpp : [gcc] c++ (gcc 11.2.0) rust : [rustc]rustc -C linker=cc (rustc 1.56.0) swift : [not found] vala : [valac]valac (valac 0.54.6) tools ninja : /usr/bin/ninja (1.10.1) cmake : /usr/bin/cmake (3.22.1) hotdoc : not found Checking that configuring works... Checking that introspect works... Checking that building works... Checking that testing works... Checking that installing works... Running tests with 160 workers Exception in thread Thread-1: Traceback (most recent call last): File "/usr/lib/python3.9/threading.py", line 973, in _bootstrap_inner self.run() File "/usr/lib/python3.9/concurrent/futures/process.py", line 317, in run result_item, is_broken, cause = self.wait_result_broken_or_wakeup() File "/usr/lib/python3.9/concurrent/futures/process.py", line 376, in wait_result_broken_or_wakeup worker_sentinels = [p.sentinel for p in self.processes.values()] File "/usr/lib/python3.9/concurrent/futures/process.py", line 376, in worker_sentinels = [p.sentinel for p in self.processes.values()] RuntimeError: dictionary changed size during iteration Running cmake tests. autopkgtest [16:04:29]: ERROR: timed out on command "su -s /bin/bash debci -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true; . ~/.profile >/dev/null 2>&1 || true; buildtree="/tmp/autopkgtest-lxc.f3gr65px/downtmp/build.IRe/src"; mkdir -p -m 1777 -- "/tmp/autopkgtest-lxc.f3gr65px/downtmp/exhaustive-artifacts"; export AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.f3gr65px/downtmp/exhaustive-artifacts"; export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 "/tmp/autopkgtest-lxc.f3gr65px/downtmp/autopkgtest_tmp"; export AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.f3gr65px/downtmp/autopkgtest_tmp"; export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=160; 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"; chmod +x /tmp/autopkgtest-lxc.f3gr65px/downtmp/build.IRe/src/debian/tests/exhaustive; touch /tmp/autopkgtest-lxc.f3gr65px/downtmp/exhaustive-stdout /tmp/autopkgtest-lxc.f3gr65px/downtmp/exhaustive-stderr; /tmp/autopkgtest-lxc.f3gr65px/downtmp/build.IRe/src/debian/tests/exhaustive 2> >(tee -a /tmp/autopkgtest-lxc.f3gr65px/downtmp/exhaustive-stderr >&2) > >(tee -a /tmp/autopkgtest-lxc.f3gr65px/downtmp/exhaustive-stdout);" (kind: test) autopkgtest [16:04:30]: test exhaustive: ---] OpenPGP_signature Description: OpenPGP digital signature
Bug#1004103: calcurse FTBFS on big endian
Source: calcurse Version: 4.7.1-1 Severity: serious Tags: ftbfs Control: block 1002519 by -1 https://buildd.debian.org/status/logs.php?pkg=calcurse=4.7.1-1 ... FAIL: ical-003.sh = Running ./ical-003.sh... FAIL FAIL ical-003.sh (exit status: 1) Testsuite summary for calcurse 4.7.1 # TOTAL: 77 # PASS: 76 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See test/test-suite.log Please report to b...@calcurse.org make[6]: *** [Makefile:761: test-suite.log] Error 1 s390x porters Cc'ed to debug this issue.
Processed: calcurse FTBFS on big endian
Processing control commands:
> block 1002519 by -1
Bug #1002519 {Done: Paul Gevers } [src:calcurse]
src:calcurse: fails to migrate to testing for too long: FTBFS on s390x
1002519 was not blocked by any bugs.
1002519 was not blocking any bugs.
Added blocking bug(s) of 1002519: 1004103
--
1002519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002519
1004103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1004101: ignition-fuel-tools: autopkgtest needs update for new version of ignition-common: Package 'ignition-common3' not found
Source: ignition-fuel-tools Version: 4.1.0+dfsg-6 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:ignition-common [X-Debbugs-CC: debian...@lists.debian.org, ignition-com...@packages.debian.org] Dear maintainer(s), With a recent upload of ignition-common the autopkgtest of ignition-fuel-tools fails in testing when that autopkgtest is run with the binary packages of ignition-common from unstable, but also with ignition-fuel-tools from unstable. It passes when run with only packages from testing. In tabular form: passfail ignition-commonfrom testing4.4.0+ds-4 ignition-fuel-toolsfrom testing4.1.0+dfsg-6/7.0.0+ds-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of ignition-common to testing [1] and that of ignition-fuel-tools itself [2]. 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=ignition-common [2] https://qa.debian.org/excuses.php?package=ignition-fuel-tools https://ci.debian.net/data/autopkgtest/testing/amd64/i/ignition-fuel-tools/18486065/log.gz Package ignition-common3 was not found in the pkg-config search path. Perhaps you should add the directory containing `ignition-common3.pc' to the PKG_CONFIG_PATH environment variable Package 'ignition-common3', required by 'ignition-fuel_tools4', not found igntest.c:2:10: fatal error: ignition/fuel_tools/ClientConfig.hh: No such file or directory 2 | #include "ignition/fuel_tools/ClientConfig.hh" | ^ compilation terminated. autopkgtest [16:33:24]: test build OpenPGP_signature Description: OpenPGP digital signature
Processed: ignition-fuel-tools: autopkgtest needs update for new version of ignition-common: Package 'ignition-common3' not found
Processing control commands: > affects -1 src:ignition-common Bug #1004101 [src:ignition-fuel-tools] ignition-fuel-tools: autopkgtest needs update for new version of ignition-common: Package 'ignition-common3' not found Added indication that 1004101 affects src:ignition-common -- 1004101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004099: lua-system: autopkgtest regression: module 'mediator' not found
Source: lua-system Version: 0.2.1-5 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of lua-system the autopkgtest of lua-system fails in testing when that autopkgtest is run with the binary packages of lua-system from unstable. It passes when run with only packages from testing. In tabular form: passfail lua-system from testing0.2.1-5 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? 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=lua-system https://ci.debian.net/data/autopkgtest/testing/amd64/l/lua-system/18491945/log.gz dh autopkgtest --buildsystem=lua --with lua dh_auto_test -O--buildsystem=lua make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple autopkgtest Making target autopkgtest for debian/lua5.1.dh-lua.conf * lua dynamic custom (5.1, autopkgtest) ** +++ 3 successes / 0 failures / 0 errors / 0 pending : 0.501591 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.2.dh-lua.conf * lua dynamic custom (5.2, autopkgtest) ** +++ 3 successes / 0 failures / 0 errors / 0 pending : 0.502037 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.3.dh-lua.conf * lua dynamic custom (5.3, autopkgtest) ** +++ 3 successes / 0 failures / 0 errors / 0 pending : 0.50354 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.4.dh-lua.conf * lua dynamic custom (5.4, autopkgtest) ** lua5.4: /usr/share/lua/5.4/busted/core.lua:45: module 'mediator' not found: no field package.preload['mediator'] no file '/usr/local/share/lua/5.4/mediator.lua' no file '/usr/local/share/lua/5.4/mediator/init.lua' no file '/usr/local/lib/lua/5.4/mediator.lua' no file '/usr/local/lib/lua/5.4/mediator/init.lua' no file '/usr/share/lua/5.4/mediator.lua' no file '/usr/share/lua/5.4/mediator/init.lua' no file './mediator.lua' no file './mediator/init.lua' no file '/usr/local/lib/lua/5.4/mediator.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.4/mediator.so' no file '/usr/lib/lua/5.4/mediator.so' no file '/usr/local/lib/lua/5.4/loadall.so' no file './mediator.so' stack traceback: [C]: in function 'require' /usr/share/lua/5.4/busted/core.lua:45: in function 'busted.core' /usr/share/lua/5.4/busted/runner.lua:18: in function 'busted.runner' /usr/bin/busted:3: in main chunk [C]: in ? make[2]: *** [/usr/share/dh-lua/make/dh-lua.Makefile.single:326: test-lua-dynamic-apkgt-real-custom] Error 1 make[1]: *** [/usr/share/dh-lua/make/dh-lua.Makefile.multiple:12: autopkgtest] Error 1 dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple autopkgtest returned exit code 2 make: *** [debian/rules:6: autopkgtest] Error 25 autopkgtest [17:40:57]: test dh-lua-tests OpenPGP_signature Description: OpenPGP digital signature
Bug#1004098: lua-say: autopkgtest regression: module 'system' not found
Source: lua-say Version: 1.3-1-7 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of lua-say the autopkgtest of lua-say fails in testing when that autopkgtest is run with the binary packages of lua-say from unstable. It passes when run with only packages from testing. In tabular form: passfail lua-sayfrom testing1.3-1-7 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? 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=lua-say https://ci.debian.net/data/autopkgtest/testing/amd64/l/lua-say/18500281/log.gz dh autopkgtest --buildsystem=lua --with lua dh_auto_test -O--buildsystem=lua make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple autopkgtest Making target autopkgtest for debian/lua5.1.dh-lua.conf * lua dynamic custom (5.1, autopkgtest) ** + 5 successes / 0 failures / 0 errors / 0 pending : 0.002135 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.2.dh-lua.conf * lua dynamic custom (5.2, autopkgtest) ** + 5 successes / 0 failures / 0 errors / 0 pending : 0.003267 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.3.dh-lua.conf * lua dynamic custom (5.3, autopkgtest) ** + 5 successes / 0 failures / 0 errors / 0 pending : 0.007344 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.4.dh-lua.conf * lua dynamic custom (5.4, autopkgtest) ** lua5.4: /usr/share/lua/5.4/busted/core.lua:6: module 'system' not found: no field package.preload['system'] no file '/usr/local/share/lua/5.4/system.lua' no file '/usr/local/share/lua/5.4/system/init.lua' no file '/usr/local/lib/lua/5.4/system.lua' no file '/usr/local/lib/lua/5.4/system/init.lua' no file '/usr/share/lua/5.4/system.lua' no file '/usr/share/lua/5.4/system/init.lua' no file './system.lua' no file './system/init.lua' no file '/usr/local/lib/lua/5.4/system.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.4/system.so' no file '/usr/lib/lua/5.4/system.so' no file '/usr/local/lib/lua/5.4/loadall.so' no file './system.so' stack traceback: [C]: in function 'require' /usr/share/lua/5.4/busted/core.lua:6: in main chunk [C]: in function 'require' /usr/share/lua/5.4/busted/runner.lua:18: in function 'busted.runner' /usr/bin/busted:3: in main chunk [C]: in ? make[2]: *** [/usr/share/dh-lua/make/dh-lua.Makefile.single:326: test-lua-dynamic-apkgt-real-custom] Error 1 make[1]: *** [/usr/share/dh-lua/make/dh-lua.Makefile.multiple:12: autopkgtest] Error 1 dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple autopkgtest returned exit code 2 make: *** [debian/rules:4: autopkgtest] Error 25 autopkgtest [23:14:51]: test dh-lua-tests OpenPGP_signature Description: OpenPGP digital signature
Bug#1004097: lua-mediator: autopkgtest regression: module 'system' not found
Source: lua-mediator Version: 1.1.2-0-6 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of lua-mediator the autopkgtest of lua-mediator fails in testing when that autopkgtest is run with the binary packages of lua-mediator from unstable. It passes when run with only packages from testing. In tabular form: passfail lua-mediator from testing1.1.2-0-6 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? 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=lua-mediator https://ci.debian.net/data/autopkgtest/testing/amd64/l/lua-mediator/18493076/log.gz dh autopkgtest --buildsystem=lua --with lua dh_auto_test -O--buildsystem=lua make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple autopkgtest Making target autopkgtest for debian/lua5.1.dh-lua.conf * lua dynamic custom (5.1, autopkgtest) ** ++ 26 successes / 0 failures / 0 errors / 0 pending : 0.008956 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.2.dh-lua.conf * lua dynamic custom (5.2, autopkgtest) ** ++ 26 successes / 0 failures / 0 errors / 0 pending : 0.00897 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.3.dh-lua.conf * lua dynamic custom (5.3, autopkgtest) ** ++ 26 successes / 0 failures / 0 errors / 0 pending : 0.02869 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.4.dh-lua.conf * lua dynamic custom (5.4, autopkgtest) ** lua5.4: /usr/share/lua/5.4/busted/core.lua:6: module 'system' not found: no field package.preload['system'] no file '/usr/local/share/lua/5.4/system.lua' no file '/usr/local/share/lua/5.4/system/init.lua' no file '/usr/local/lib/lua/5.4/system.lua' no file '/usr/local/lib/lua/5.4/system/init.lua' no file '/usr/share/lua/5.4/system.lua' no file '/usr/share/lua/5.4/system/init.lua' no file './system.lua' no file './system/init.lua' no file '/usr/local/lib/lua/5.4/system.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.4/system.so' no file '/usr/lib/lua/5.4/system.so' no file '/usr/local/lib/lua/5.4/loadall.so' no file './system.so' stack traceback: [C]: in function 'require' /usr/share/lua/5.4/busted/core.lua:6: in main chunk [C]: in function 'require' /usr/share/lua/5.4/busted/runner.lua:18: in function 'busted.runner' /usr/bin/busted:3: in main chunk [C]: in ? make[2]: *** [/usr/share/dh-lua/make/dh-lua.Makefile.single:326: test-lua-dynamic-apkgt-real-custom] Error 1 make[1]: *** [/usr/share/dh-lua/make/dh-lua.Makefile.multiple:12: autopkgtest] Error 1 dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple autopkgtest returned exit code 2 make: *** [debian/rules:4: autopkgtest] Error 25 autopkgtest [17:41:48]: test dh-lua-tests OpenPGP_signature Description: OpenPGP digital signature
Bug#1004096: lua-cliargs: autopkgtest regression: module 'system' not found
Source: lua-cliargs Version: 3.0-2-4 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of lua-cliargs the autopkgtest of lua-cliargs fails in testing when that autopkgtest is run with the binary packages of lua-cliargs from unstable. It passes when run with only packages from testing. In tabular form: passfail lua-cliargsfrom testing3.0-2-4 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? 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=lua-cliargs https://ci.debian.net/data/autopkgtest/testing/amd64/l/lua-cliargs/18493075/log.gz dh autopkgtest --buildsystem=lua --with lua dh_auto_test -O--buildsystem=lua make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple autopkgtest Making target autopkgtest for debian/lua5.1.dh-lua.conf * lua dynamic custom (5.1, autopkgtest) ** +++ 175 successes / 0 failures / 0 errors / 0 pending : 0.099948 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.2.dh-lua.conf * lua dynamic custom (5.2, autopkgtest) ** +++ 175 successes / 0 failures / 0 errors / 0 pending : 0.101283 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.3.dh-lua.conf * lua dynamic custom (5.3, autopkgtest) ** +++ 175 successes / 0 failures / 0 errors / 0 pending : 0.323412 seconds * Target autopkgtest made Making target autopkgtest for debian/lua5.4.dh-lua.conf * lua dynamic custom (5.4, autopkgtest) ** lua5.4: /usr/share/lua/5.4/busted/core.lua:6: module 'system' not found: no field package.preload['system'] no file '/usr/local/share/lua/5.4/system.lua' no file '/usr/local/share/lua/5.4/system/init.lua' no file '/usr/local/lib/lua/5.4/system.lua' no file '/usr/local/lib/lua/5.4/system/init.lua' no file '/usr/share/lua/5.4/system.lua' no file '/usr/share/lua/5.4/system/init.lua' no file './system.lua' no file './system/init.lua' no file '/usr/local/lib/lua/5.4/system.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.4/system.so' no file '/usr/lib/lua/5.4/system.so' no file '/usr/local/lib/lua/5.4/loadall.so' no file './system.so' stack traceback: [C]: in function 'require' /usr/share/lua/5.4/busted/core.lua:6: in main chunk [C]: in function 'require' /usr/share/lua/5.4/busted/runner.lua:18: in function 'busted.runner' /usr/bin/busted:3: in main chunk [C]: in ? make[2]: *** [/usr/share/dh-lua/make/dh-lua.Makefile.single:326: test-lua-dynamic-apkgt-real-custom] Error 1 make[1]: *** [/usr/share/dh-lua/make/dh-lua.Makefile.multiple:12: autopkgtest] Error 1 dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple autopkgtest returned exit code 2 make: *** [debian/rules:4: autopkgtest] Error 25 autopkgtest [17:41:55]: test dh-lua-tests OpenPGP_signature Description: OpenPGP digital signature
Processed: pillow breaks python-imageio autopkgtest: assert (150, 200, 3) == (150, 200, 4)
Processing control commands: > found -1 pillow/9.0.0-1 Bug #1004094 [src:pillow, src:python-imageio] pillow breaks python-imageio autopkgtest: assert (150, 200, 3) == (150, 200, 4) Marked as found in versions pillow/9.0.0-1. > found -1 python-imageio/2.4.1-3 Bug #1004094 [src:pillow, src:python-imageio] pillow breaks python-imageio autopkgtest: assert (150, 200, 3) == (150, 200, 4) Marked as found in versions python-imageio/2.4.1-3. -- 1004094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004094: pillow breaks python-imageio autopkgtest: assert (150, 200, 3) == (150, 200, 4)
Source: pillow, python-imageio
Control: found -1 pillow/9.0.0-1
Control: found -1 python-imageio/2.4.1-3
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of pillow the autopkgtest of python-imageio fails
in testing when that autopkgtest is run with the binary packages of
pillow from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
pillow from testing9.0.0-1
python-imageio from testing2.4.1-3
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of pillow to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?
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=pillow
https://ci.debian.net/data/autopkgtest/testing/ppc64el/p/python-imageio/18424529/log.gz
=== FAILURES
===
__ test_animated_gif
___
def test_animated_gif():
# Read newton's cradle
ims = imageio.mimread("imageio:newtonscradle.gif")
assert len(ims) == 36
for im in ims:
assert im.shape == (150, 200, 4)
E assert (150, 200, 3) == (150, 200, 4)
E At index 2 diff: 3 != 4
E Full diff:
E - (150, 200, 4)
E ?^
E + (150, 200, 3)
E ?^
test_pillow.py:256: AssertionError
=== warnings summary
===
test_bsdf.py: 12 warnings
/usr/lib/python3/dist-packages/imageio/plugins/_bsdf.py:418:
DeprecationWarning: The 'warn' method is deprecated, use 'warning' instead
logger.warn("BSDF warning: no extension found for %r" % ext_id)
test_core.py: 4 warnings
test_dicom.py: 2 warnings
test_format.py: 4 warnings
test_grab.py: 2 warnings
/usr/lib/python3/dist-packages/imageio/core/util.py:562:
DeprecationWarning: Deprecated since Python 3.4. Use
importlib.util.find_spec() instead.
return importlib.find_loader(module_name) is not None
test_pillow.py::test_png
/usr/lib/python3/dist-packages/imageio/plugins/pillow.py:317:
UserWarning: PIL PNG writer cannot produce interlaced images.
warn("PIL PNG writer cannot produce interlaced images.")
-- Docs: https://docs.pytest.org/en/stable/warnings.html
=== short test summary info
FAILED test_pillow.py::test_animated_gif - assert (150, 200, 3) == (150,
200, 4)
== 1 failed, 53 passed, 67 skipped, 3 xfailed, 25 warnings in 24.04s
===
autopkgtest [08:06:23]: test command1
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1004013: marked as done (python3-typedload-doc: missing Breaks+Replaces: python3-typedload (<< 2.15))
Your message dated Thu, 20 Jan 2022 19:25:47 + with message-id and subject line Bug#1004013: fixed in typedload 2.15-3 has caused the Debian Bug report #1004013, regarding python3-typedload-doc: missing Breaks+Replaces: python3-typedload (<< 2.15) 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.) -- 1004013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004013 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-typedload-doc Version: 2.15-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-typedload-doc_2.15-2_all.deb ... Unpacking python3-typedload-doc (2.15-2) ... dpkg: error processing archive /var/cache/apt/archives/python3-typedload-doc_2.15-2_all.deb (--unpack): trying to overwrite '/usr/share/doc/python3-typedload/docs/CHANGELOG.md.gz', which is also in package python3-typedload 2.14-2 Errors were encountered while processing: /var/cache/apt/archives/python3-typedload-doc_2.15-2_all.deb The exisiting Breaks+Replaces: python3-typedload (<< 2.5) are insufficiently versioned. cheers, Andreas python3-typedload=2.14-2_python3-typedload-doc=2.15-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: typedload Source-Version: 2.15-3 Done: Salvo 'LtWorf' Tomaselli We believe that the bug you reported is fixed in the latest version of typedload, 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 1004...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvo 'LtWorf' Tomaselli (supplier of updated typedload 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, 20 Jan 2022 19:40:49 +0100 Source: typedload Architecture: source Version: 2.15-3 Distribution: unstable Urgency: medium Maintainer: Salvo 'LtWorf' Tomaselli Changed-By: Salvo 'LtWorf' Tomaselli Closes: 1004013 Changes: typedload (2.15-3) unstable; urgency=medium . * Fix Breaks and Replace version (Closes: #1004013) Checksums-Sha1: adf8ca7f733e9d9601cd40bb67c083cbf97c8ec7 2289 typedload_2.15-3.dsc 539ecfc79247cb1366f6e3973a40d634d1d5a0a6 14000 typedload_2.15-3.debian.tar.xz 834fe3b30d04eb352aae9da3dfac0febf4050069 8865 typedload_2.15-3_amd64.buildinfo Checksums-Sha256: b502d3bc001b9d04db820b5e75e594600e6e9fd076cbbc1ee7a369118335dbb3 2289 typedload_2.15-3.dsc 73d30dfd80a11acbcac610829779b3a1f1816384afd1a41d2ef0606ccde656fa 14000 typedload_2.15-3.debian.tar.xz 7decbefa25f8641d801505ed21999e763ffb88aae976fb6b6c5758679b5f6409 8865 typedload_2.15-3_amd64.buildinfo Files: 0b25cd9ee8d007b7b7b362c1dd903dc7 2289 python optional typedload_2.15-3.dsc a14879b006bfcf5c144c219ff558a5e8 14000 python optional typedload_2.15-3.debian.tar.xz 2a5f471df4ffe432c539994fa3e7fd59 8865 python optional typedload_2.15-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEQnSLnnbYmXmeH74Us6fPDIAYhs8FAmHprwcUHHRpcG9zY2hp QHRpc2NhbGkuaXQACgkQs6fPDIAYhs+lIA//UK2yLH/kXakh6gPBkGAnG+HM2+WC wkiPmrp71dB37u9pVLxRl1dCI6TDLU9YEZvQmaPMuPCJX9uXhgIS69V360h9apkJ EAAjZXaarthVNyGqBkRTIFvy9vyJmbHJjpQtUIuuK1FE4Ua8juiunNS6orTDVzmj jTOuY4KEItV3BeWlElOulJvyYMFehcE+UBbvFS42t+fjjwMD+fy9cvRU/Trbplxw NAwG7HC3r9F5EmF1++FVjyy0vp7Uvwb6AXoPvKDXPOP4TcUWVo+eNHX8paHKypwe ZLBVAkZDluNBdL8OXer6dWKe+DEUcFdx7bKJaAY6Q8UUlqlpyR4a//E+vMsXKMtE zBy/bCmSdoNxcsn/UZUBzqJf3uEv/afmvYBWjL9fIIE6Le7nrZUFzs81iOOgKyDK 13DXwD77YlGHpUEt+4Uf4bVPTCRhc7sydX4KZ6vtpqZpL4OK/+r6mF20ELhX3ER5 YyW+Ip5+LkN7h1vcvqNOGE36nIHWzSKmH6AO6AX5YK/DYB3xjvm0O4V0DyCDR5CR jAcX0GoyVEgaCD8CuzL/HCcTXr7DZUHNs93BlFUOTsGkBJWBt8O8Axxnx8kCv5kH zqgon3pIFupWSO7zyDPkaNQR5ux8kt6bzig2WzFGBOWB8x3Ng/npU9JZ/9+BWM2x K4b/ehjdi5lVZmk= =eUnU -END PGP SIGNATURE End
Bug#1003347: marked as done (src:android-platform-dalvik: fails to migrate to testing for too long: uploader built arch:all binaries)
Your message dated Thu, 20 Jan 2022 19:19:07 + with message-id and subject line Bug#1003347: fixed in android-platform-dalvik 10.0.0+r36-3 has caused the Debian Bug report #1003347, regarding src:android-platform-dalvik: fails to migrate to testing for too long: uploader built arch:all binaries 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.) -- 1003347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003347 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: android-platform-dalvik Version: 10.0.0+r36-1 Severity: serious Control: close -1 10.0.0+r36-2 Tags: sid bookworm pending 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:android-platform-dalvik has been trying to migrate for 63 days [2]. Hence, I am filing this bug. 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. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=android-platform-dalvik OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: android-platform-dalvik Source-Version: 10.0.0+r36-3 Done: Roger Shimizu We believe that the bug you reported is fixed in the latest version of android-platform-dalvik, 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 1003...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roger Shimizu (supplier of updated android-platform-dalvik 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: Fri, 21 Jan 2022 02:19:50 +0900 Source: android-platform-dalvik Architecture: source Version: 10.0.0+r36-3 Distribution: unstable Urgency: medium Maintainer: Android Tools Maintainers Changed-By: Roger Shimizu Closes: 1003347 Changes: android-platform-dalvik (10.0.0+r36-3) unstable; urgency=medium . * Team upload. * Source-upload to enable the testing migration (Closes: #1003347). Checksums-Sha1: c121fef9d7db2ace7e84868bee4cc884ed5c9a79 2387 android-platform-dalvik_10.0.0+r36-3.dsc 86375b2ed43a957f03d7b24262d3704eb7310ba7 6948 android-platform-dalvik_10.0.0+r36-3.debian.tar.xz 3c01ffd7adeaa00dcd23e6a8b109edde82b908c2 14171 android-platform-dalvik_10.0.0+r36-3_amd64.buildinfo Checksums-Sha256: c0822e9ae297347876fe3535066c8ecf03de84e1fc92edde84c092cd94b0c409 2387 android-platform-dalvik_10.0.0+r36-3.dsc b45150e32c5c67d5624a71586c4dce765169811961c3cb01844dd9ecefdbc8bd 6948 android-platform-dalvik_10.0.0+r36-3.debian.tar.xz 09656189c17acc5d66a7b128b9ed6b6cc37b1de4b6b6c34d4ce2395c731de8e8 14171 android-platform-dalvik_10.0.0+r36-3_amd64.buildinfo Files: d8add8f2a1be65de5f33b9a72e53990f 2387 devel optional android-platform-dalvik_10.0.0+r36-3.dsc ab85c225af57671d278a51cdb3c2072e 6948 devel optional
Bug#1004092: swayidle FTBFS on 32bit
Source: swayidle
Version: 1.7.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=swayidle=1.7.1-1
...
FAILED: swayidle.p/main.c.o
cc -Iswayidle.p -I. -I.. -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64
-Wall -Winvalid-pch -Wextra -Werror -std=c11 -Wno-unused-parameter
-Wno-unused-result -Wundef -Wvla '-DSYSCONFDIR="/etc"' -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ
swayidle.p/main.c.o -MF swayidle.p/main.c.o.d -o swayidle.p/main.c.o -c
../main.c
In file included from ../main.c:19:
../main.c: In function ‘load_config’:
../log.h:28:25: error: format ‘%lu’ expects argument of type ‘long unsigned
int’, but argument 5 has type ‘size_t’ {aka ‘unsigned int’} [-Werror=format=]
28 | _swayidle_log(verb, "[Line %d] " fmt, __LINE__, ##__VA_ARGS__)
| ^~~~
../main.c:1007:25: note: in expansion of macro ‘swayidle_log’
1007 | swayidle_log(LOG_ERROR, "Unexpected keyword
\"%s\" in line %lu", line, lineno);
| ^~~~
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
dh_auto_build: error: cd obj-i686-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v
returned exit code 1
make: *** [debian/rules:11: binary-arch] Error 25
Bug#1002532: pygments breaks ruby-pygments.rb autopkgtest: UTF-8 != ASCII-8BIT
Hi Alex, On Thu, Jan 06, 2022 at 11:19:00AM +0100, Alexandre Ghiti wrote: > As the current version we have is from 2017, I bumped the version of > this package to the latest available version: I updated the patches, > removed the ones that do not apply anymore, updated the build system > and dependencies. The result is available in my PPA [2] and fixes the > issue we encounter here. > > Can you consider pulling this? Thank you for this!! I had a look at your work, however I couldn't help but notice that: * the .orig you used looks odd, much larger than what I get from uscan (despite yours is also using a different compression, so repacked). * You did a ton of patch wrangling, including deletion, renaming, rebasing, etc. which is all fine, except that the way you did it obscures quite a bit what you did. Why did you drop the numbers from the patches? Do you have --no-patch-numbers as you gbp-pq default or something? * why requiring gem2deb >=1 ? that's already in bullseye as well in focal, so why did you feel the need to add the version? (that's also not in the changelog) As such, I went ahead and re-imported the repacked origin I got myself in git. Could I ask you to submit a MR on top of it, with at least commits separating the deletion, refresh and rebasing of patches (and eventual new ones, I can't tell at a glance if any new patch appeared…) also separated. https://salsa.debian.org/ruby-team/ruby-pygments.rb Thank you for your work!! :) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Processed: forcibly merging 1001766 1004089
Processing commands for cont...@bugs.debian.org: > forcemerge 1001766 1004089 Bug #1001766 [oomd] oomd: ships both ./lib/systemd/system/oomd.service & ./usr/lib/systemd/system/oomd.service Bug #1004089 [oomd] Error during install Severity set to 'grave' from 'normal' Marked as found in versions oomd/0.5.0-1. Merged 1001766 1004089 > thanks Stopping processing here. Please contact me if you need assistance. -- 1001766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001766 1004089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003563: marked as done (aide: autopkgtest regression: unexpected character: '@' in /etc/aide/aide.conf.d/31_aide_spamassassin)
Your message dated Thu, 20 Jan 2022 17:24:39 + with message-id and subject line Bug#1003563: fixed in aide 0.17.4-1 has caused the Debian Bug report #1003563, regarding aide: autopkgtest regression: unexpected character: '@' in /etc/aide/aide.conf.d/31_aide_spamassassin 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.) -- 1003563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003563 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: aide Version: 0.17.3-6 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of aide the autopkgtest of aide fails in testing when that autopkgtest is run with the binary packages of aide from unstable. It passes when run with only packages from testing. In tabular form: passfail aide from testing0.17.3-6 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? 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=aide https://ci.debian.net/data/autopkgtest/testing/amd64/a/aide/18222075/log.gz ERROR: /etc/aide/aide.conf.d/31_aide_spamassassin:3: unexpected character: '@' (line: '@endif') autopkgtest [19:10:30]: test 01-aide-config-check OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: aide Source-Version: 0.17.4-1 Done: Marc Haber We believe that the bug you reported is fixed in the latest version of aide, 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 1003...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marc Haber (supplier of updated aide 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, 30 Dec 2021 22:45:57 +0100 Source: aide Architecture: source Version: 0.17.4-1 Distribution: unstable Urgency: medium Maintainer: Aide Maintainers Changed-By: Marc Haber Closes: 1003563 Changes: aide (0.17.4-1) unstable; urgency=medium . * new upstream release * this fixes CVE-2021-45417 * fix stupid typo in 31_aide_spamassassin (Closes: #1003563) * more improvements for 31_aide_Spamassassin Checksums-Sha1: 318e51f6a688068f894f337faf9742d265a41bf4 2581 aide_0.17.4-1.dsc de8d03b2c5ceac7efd4527a5daa578258d201a57 331783 aide_0.17.4.orig.tar.gz 0084accd157fa3e39f71344212eff5bd06abf5b4 659 aide_0.17.4.orig.tar.gz.asc 70072b2022bfd3f2da45c7149e6b48ee13d9bf2d 97220 aide_0.17.4-1.debian.tar.xz f980c33d5cdf2b3fe8a450b4c6987587605f97f7 6446 aide_0.17.4-1_source.buildinfo Checksums-Sha256: 7fa897025f53fdfb337371eb0d75663d797b87a2d3a491c6ddc735eff8ad 2581 aide_0.17.4-1.dsc c81505246f3ffc2e76036d43a77212ae82895b5881d9b9e25c1361b1a9b7a846 331783 aide_0.17.4.orig.tar.gz 4c9d7d6c7737f79069a3a50136986eed23606bc1e7bb6315dc900b2c8e39443a 659 aide_0.17.4.orig.tar.gz.asc fd1c9a85352ba8763c74d1ab3d14243d776dc305e2663de8220ea634f7a27229 97220 aide_0.17.4-1.debian.tar.xz 56720628617fd320134a966b56fe82a28c3e0b064781f36fcbc692fa31ecae1f 6446 aide_0.17.4-1_source.buildinfo Files: 2b5fc1e7e713ec88675ac13a9571eb7b 2581 admin optional aide_0.17.4-1.dsc adac3bc719b923d49059edb992eb95c9 331783 admin optional aide_0.17.4.orig.tar.gz 948c3eb46c8994911f07390adcb9109b 659 admin optional aide_0.17.4.orig.tar.gz.asc 3e04ea3937add42a83dfcf10235fd0ea 97220 admin optional aide_0.17.4-1.debian.tar.xz f392f85b045b3114f17eadfe89279707 6446 admin optional aide_0.17.4-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE6QL5UJ/L0pcuNEbjj3cgEwEyBEIFAmHpko8ACgkQj3cgEwEy BEK8pg/6A+VyZ+G8ATyWpDadWELkxjsd2hIABhplIxOOo0LjNXUvEQ+O+ybkJ8t4 Fx3V9xeSkVtu8hyhQQ14QIXaXWtsbA+2UPkcH521Twm0CE0FIbDFmGMb9THoyaer Rsw2XXAK/qXoU9xHzq0OFSUmmGWpCFnEALn5OwV25z8P/Zx5U+9GGG758WNT8b6A
Processed: [bts-link] source package src:pillow
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:pillow > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1003661 (http://bugs.debian.org/1003661) > # Bug title: Pillow claims GIF frame to be mode RGB instead of P > # * https://github.com/python-pillow/Pillow/issues/5966 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1003661 + fixed-upstream Bug #1003661 [src:pillow] Pillow claims GIF frame to be mode RGB instead of P Added tag(s) fixed-upstream. > usertags 1003661 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1003661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003661 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:clementine
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:clementine > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #984014 (http://bugs.debian.org/984014) > # Bug title: clementine: ftbfs with GCC-11 > # * https://github.com/clementine-player/Clementine/issues/6865 > # * remote status changed: (?) -> closed > # * closed upstream > tags 984014 + fixed-upstream Bug #984014 [src:clementine] clementine: ftbfs with GCC-11 Added tag(s) fixed-upstream. > usertags 984014 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 984014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984014 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:isbnlib
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:isbnlib > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1002165 (http://bugs.debian.org/1002165) > # Bug title: isbnlib: FTBFS: ImportError: cannot import name 'MutableMapping' > from 'collections' (/usr/lib/python3.10/collections/__init__.py) > # * https://github.com/xlcnd/isbnlib/issues/61 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1002165 + fixed-upstream Bug #1002165 [src:isbnlib] isbnlib: FTBFS: ImportError: cannot import name 'MutableMapping' from 'collections' (/usr/lib/python3.10/collections/__init__.py) Added tag(s) fixed-upstream. > usertags 1002165 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1002165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001483: marked as done (scoop: (autopkgtest) needs update for python3.10: 'Iterable' from 'collections' is removed)
Your message dated Thu, 20 Jan 2022 16:50:05 + with message-id and subject line Bug#1003748: Removed package(s) from unstable has caused the Debian Bug report #1001483, regarding scoop: (autopkgtest) needs update for python3.10: 'Iterable' from 'collections' is removed 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.) -- 1001483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scoop Version: 0.7.1.1-7 Severity: serious X-Debbugs-CC: debian...@lists.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.10 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.10 to the supported Python versions [0]. With a recent upload of python3-defaults the autopkgtest of scoop fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.9.8-1 scoop from testing0.7.1.1-7 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists what's new in Python3.10, it may help to identify what needs to be updated. https://docs.python.org/3.9/library/collections.html says: """ Deprecated since version 3.3, will be removed in version 3.10: Moved Collections Abstract Base Classes to the collections.abc module. For backwards compatibility, they continue to be visible in this module through Python 3.9. """ Time to move on. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/996584 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/s/scoop/17446737/log.gz Traceback (most recent call last): File "/tmp/autopkgtest-lxc.iso4fc4h/downtmp/autopkgtest_tmp/test/tests.py", line 34, in from scoop import futures, _control, utils, shared File "/usr/lib/python3/dist-packages/scoop/futures.py", line 19, in from collections import namedtuple, Iterable ImportError: cannot import name 'Iterable' from 'collections' (/usr/lib/python3.10/collections/__init__.py) /usr/lib/python3/dist-packages/scoop/futures.py:19: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated since Python 3.3, and in 3.10 it will stop working from collections import namedtuple, Iterable /usr/lib/python3/dist-packages/scoop/futures.py:19: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated since Python 3.3, and in 3.10 it will stop working from collections import namedtuple, Iterable ./tmp/autopkgtest-lxc.iso4fc4h/downtmp/autopkgtest_tmp/test/tests.py:332: ResourceWarning: unclosed socket scoop._control.execQueue = FutureQueue() ResourceWarning: Enable tracemalloc to get the object allocation traceback ./tmp/autopkgtest-lxc.iso4fc4h/downtmp/autopkgtest_tmp/test/tests.py:332: ResourceWarning: unclosed socket scoop._control.execQueue = FutureQueue() ResourceWarning: Enable tracemalloc to get the object allocation traceback ./tmp/autopkgtest-lxc.iso4fc4h/downtmp/autopkgtest_tmp/test/tests.py:332: ResourceWarning: unclosed socket scoop._control.execQueue = FutureQueue() ResourceWarning: Enable tracemalloc to get the object allocation traceback ./tmp/autopkgtest-lxc.iso4fc4h/downtmp/autopkgtest_tmp/test/tests.py:332: ResourceWarning: unclosed socket scoop._control.execQueue = FutureQueue() ResourceWarning: Enable tracemalloc to get the object allocation traceback ./usr/lib/python3/dist-packages/scoop/futures.py:19: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated since Python 3.3, and in 3.10 it will stop working from collections import namedtuple, Iterable ./tmp/autopkgtest-lxc.iso4fc4h/downtmp/autopkgtest_tmp/test/tests.py:332: ResourceWarning: unclosed socket scoop._control.execQueue = FutureQueue() ResourceWarning: Enable tracemalloc to get the object allocation traceback
Bug#996074: marked as done (gnome-shell-extension-trash: does not declare compatibility with GNOME Shell 41)
Your message dated Thu, 20 Jan 2022 16:28:20 + with message-id and subject line Bug#1004078: Removed package(s) from unstable has caused the Debian Bug report #996074, regarding gnome-shell-extension-trash: does not declare compatibility with GNOME Shell 41 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.) -- 996074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996074 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-extension-trash Version: 0.2.0-git20200326.3425fcf1-1 Severity: normal Tags: bookworm sid User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gnome-shell-41 The metadata.json for this extension doesn't declare compatibility with GNOME 41. I don't know whether the actual code will need changes or not: the conservative assumption is that it probably will (so please test). gnome-shell 41 should be available in experimental soon. In versions of GNOME Shell up to 3.38, metadata.json didn't matter much, because validation of extensions' metadata against the installed Shell version was disabled by default; but since GNOME 40 the default has changed back to enabling the version check by default, in an effort to avoid issues caused by outdated extensions remaining enabled. As a result, GNOME Shell extensions in bookworm should probably have a dependency like: Depends: gnome-shell (>= x), gnome-shell (<< y~) where x and y are set according to metadata.json. gnome-shell-extension-caffeine is a good example of this technique. When we do the GNOME Shell 41 transition, hopefully soon, we will have to either update this extension or remove it from testing. It would be useful to get a fixed version into experimental. Thanks, smcv --- End Message --- --- Begin Message --- Version: 0.2.0-git20200326.3425fcf1-1+rm Dear submitter, as the package gnome-shell-extension-trash has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1004078 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#998913: marked as done (libbiod: FTBFS with ldc 1.28.0)
Your message dated Thu, 20 Jan 2022 16:21:18 + with message-id and subject line Bug#1000434: Removed package(s) from unstable has caused the Debian Bug report #998913, regarding libbiod: FTBFS with ldc 1.28.0 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.) -- 998913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbiod Version: 0.2.3+git20191120.b8eecef-2 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) libbiod fails to build: | ../bio/std/experimental/hts/bam/reader.d(237): Error: no property `cleanup` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(245): Error: no property `is_mapped` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(246): Error: no property `refid` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(250): Error: no property `refid` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(254): Error: no property `_flag_nc` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(258): Error: no property `_flag` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(267): Error: no property `is_mapped` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(268): Error: no property `pos` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(269): Error: no property `pos` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(273): Error: no property `pos` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(280): Error: incompatible types for `(this.start_pos()) + (this.consumed_reference_bases())`: `uint` and `Nullable!uint` | ../bio/std/experimental/hts/bam/reader.d(284): Error: incompatible types for `(this.raw_start_pos()) + (this.consumed_reference_bases())`: `uint` and `Nullable!uint` | ../bio/std/experimental/hts/bam/reader.d(296): Error: no property `is_mapped` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(297): Error: no property `mapping_quality` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(301): Error: no property `_tlen` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(306): Error: no property `sequence_length` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(307): Error: cannot implicitly convert expression `this.sequence_length2` of type `Nullable!int` to `uint` | ../bio/std/experimental/hts/bam/reader.d(314): Error: no property `is_mapped` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(316): Error: no property `raw_cigar` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(335): Error: no property `is_mapped` for type `std.typecons.Nullable!(ReadBlob)` See https://buildd.debian.org/status/fetch.php?pkg=libbiod=amd64=0.2.3%2Bgit20191120.b8eecef-2%2Bb4=1636458777=0 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Version: 0.2.3+git20191120.b8eecef-2+rm Dear submitter, as the package libbiod has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1000434 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#963303: marked as done (libnewlib-nano: FTBFS: ../../newlib/libc/include/ssp/ssp.h:47:52: error: expected declaration specifiers or '...' before numeric constant)
Your message dated Thu, 20 Jan 2022 16:21:45 + with message-id and subject line Bug#1004058: Removed package(s) from unstable has caused the Debian Bug report #960866, regarding libnewlib-nano: FTBFS: ../../newlib/libc/include/ssp/ssp.h:47:52: error: expected declaration specifiers or '...' before numeric constant 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.) -- 960866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960866 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libnewlib-nano Version: 2.11.2-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > cd debian/build-nano && ninja > [1/16620] Compiling C object > 'newlib/libc/machine/arm/50beb5a@@machine@sta/setjmp.S.o' > [2/16620] Compiling C object > 'newlib/libc/machine/arm/50beb5a@@machine@sta/strcpy.c.o' > FAILED: newlib/libc/machine/arm/50beb5a@@machine@sta/strcpy.c.o > arm-none-eabi-gcc -Inewlib/libc/machine/arm/50beb5a@@machine@sta > -Inewlib/libc/machine/arm -I../../newlib/libc/machine/arm -I. -I../.. > -Inewlib/libc/tinystdio -I../../newlib/libc/tinystdio -Inewlib/libc/include > -I../../newlib/libc/include -fdiagnostics-color=always -pipe > -D_FILE_OFFSET_BITS=64 -std=gnu99 -g -ffunction-sections -fdata-sections -Os > -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fno-builtin > -MD -MQ 'newlib/libc/machine/arm/50beb5a@@machine@sta/strcpy.c.o' -MF > 'newlib/libc/machine/arm/50beb5a@@machine@sta/strcpy.c.o.d' -o > 'newlib/libc/machine/arm/50beb5a@@machine@sta/strcpy.c.o' -c > ../../newlib/libc/machine/arm/strcpy.c > In file included from ../../newlib/libc/include/ssp/strings.h:34, > from ../../newlib/libc/include/strings.h:77, > from ../../newlib/libc/include/string.h:24, > from ../../newlib/libc/machine/arm/strcpy.c:31: > ../../newlib/libc/include/ssp/ssp.h:47:52: error: expected declaration > specifiers or '...' before numeric constant > #define __ssp_bos0(ptr) __builtin_object_size(ptr, 0) > ^ > ../../newlib/libc/include/ssp/string.h:57:7: note: in expansion of macro > '__ssp_bos0' > ((__ssp_bos0(dst) != (size_t)-1) ? \ >^~ > ../../newlib/libc/include/ssp/string.h:109:26: note: in expansion of macro > '__ssp_bos_check2' > #define strcpy(dst, src) __ssp_bos_check2(strcpy, dst, src) > ^~~~ > ../../newlib/libc/machine/arm/strcpy.c:42:1: note: in expansion of macro > 'strcpy' > strcpy (char* dst, const char* src) > ^~ > In file included from ../../newlib/libc/include/string.h:180, > from ../../newlib/libc/machine/arm/strcpy.c:31: > ../../newlib/libc/include/ssp/string.h:57:23: error: expected ')' before '!=' > token > ((__ssp_bos0(dst) != (size_t)-1) ? \ >^~ > ../../newlib/libc/include/ssp/string.h:109:26: note: in expansion of macro > '__ssp_bos_check2' > #define strcpy(dst, src) __ssp_bos_check2(strcpy, dst, src) > ^~~~ > ../../newlib/libc/machine/arm/strcpy.c:42:1: note: in expansion of macro > 'strcpy' > strcpy (char* dst, const char* src) > ^~ > ../../newlib/libc/include/ssp/string.h:57:38: error: expected ')' before '?' > token > ((__ssp_bos0(dst) != (size_t)-1) ? \ > ^ > ../../newlib/libc/include/ssp/string.h:109:26: note: in expansion of macro > '__ssp_bos_check2' > #define strcpy(dst, src) __ssp_bos_check2(strcpy, dst, src) > ^~~~ > ../../newlib/libc/machine/arm/strcpy.c:42:1: note: in expansion of macro > 'strcpy' > strcpy (char* dst, const char* src) > ^~ > [3/16620] Compiling C object > 'newlib/libc/machine/arm/50beb5a@@machine@sta/aeabi_memmove.c.o' > [4/16620] Compiling C object > 'newlib/libc/machine/arm/50beb5a@@machine@sta/strcmp.S.o' > [5/16620] Compiling C object > 'newlib/libc/machine/arm/50beb5a@@machine@sta/aeabi_memcpy.c.o' > [6/16620] Compiling C object > 'newlib/libc/machine/arm/50beb5a@@machine@sta/aeabi_memcpy-armv7a.S.o' > [7/16620] Compiling C object > 'newlib/libc/machine/arm/50beb5a@@machine@sta/aeabi_memmove-soft.S.o' > ninja: build stopped: subcommand failed. > make[1]: *** [debian/rules:48: override_dh_auto_build] Error 1
Bug#960866: marked as done (libnewlib-nano FTBFS with meson 0.54.2-1)
Your message dated Thu, 20 Jan 2022 16:21:45 + with message-id and subject line Bug#1004058: Removed package(s) from unstable has caused the Debian Bug report #960866, regarding libnewlib-nano FTBFS with meson 0.54.2-1 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.) -- 960866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960866 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libnewlib-nano Version: 2.11.2-1 Severity: serious Tags: ftbfs bullseye sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libnewlib-nano.html ... Configuring newlib.h using configuration Configuring _newlib_version.h using configuration meson.build:187: WARNING: Consider using the built-in debug option instead of using "-g". meson.build:187: WARNING: Consider using the built-in optimization level instead of using "-Os". WARNING: Target "arm_v5te_softfp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "arm_v5te_hard/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_nofp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7_nofp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7_fp_softfp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7_fp_hard/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v6_m_nofp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7_m_nofp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7e_m_nofp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7e_m_fp_softfp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7e_m_fp_hard/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7e_m_dp_softfp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7e_m_dp_hard/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v8_m_base_nofp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v8_m_main_nofp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v8_m_main_fp_softfp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v8_m_main_fp_hard/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v8_m_main_dp_softfp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v8_m_main_dp_hard/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "arm_v5te_softfp/libm" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "arm_v5te_hard/libm" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target
Processed: closing 1003984
Processing commands for cont...@bugs.debian.org: > close 1003984 0~20220102git3b7b199-3 Bug #1003984 [src:fpga-icestorm] fpga-icestorm: binary-all FTBFS Marked as fixed in versions fpga-icestorm/0~20220102git3b7b199-3. Bug #1003984 [src:fpga-icestorm] fpga-icestorm: binary-all FTBFS Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1003984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003984 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: pillow breaks img2pdf autopkgtest: TypeError: object is not an array
Processing control commands: > found -1 pillow/9.0.0-1 Bug #1004087 [src:pillow, src:img2pdf] pillow breaks img2pdf autopkgtest: TypeError: object is not an array Marked as found in versions pillow/9.0.0-1. > found -1 img2pdf/0.4.2-1 Bug #1004087 [src:pillow, src:img2pdf] pillow breaks img2pdf autopkgtest: TypeError: object is not an array Marked as found in versions img2pdf/0.4.2-1. -- 1004087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004087: pillow breaks img2pdf autopkgtest: TypeError: object is not an array
Source: pillow, img2pdf
Control: found -1 pillow/9.0.0-1
Control: found -1 img2pdf/0.4.2-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of pillow the autopkgtest of img2pdf fails in
testing when that autopkgtest is run with the binary packages of pillow
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
pillow from testing9.0.0-1
img2pdffrom testing0.4.2-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of pillow to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?
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=pillow
https://ci.debian.net/data/autopkgtest/testing/amd64/i/img2pdf/18501325/log.gz
= test session starts
==
platform linux -- Python 3.9.9, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
rootdir: /tmp/autopkgtest-lxc.e_87xohl/downtmp/build.JA2/src
collected 301 items
src/img2pdf_test.py
[ 17%]
EE..
[ 41%]
[ 65%]
[ 89%]
.FF..
[100%]
ERRORS
ERROR at setup of test_gif_animation[internal]
tmp_path_factory = TempPathFactory(_given_basetemp=None,
_trace=,
_basetemp=PosixPath('/tmp/pytest-of-debci/pytest-0'))
gif_animation_img =
PosixPath('/tmp/pytest-of-debci/pytest-0/gif_animation_img0/in.gif')
request = test_gif_animation[internal]>>
@pytest.fixture(scope="session", params=["internal", "pikepdf"])
def gif_animation_pdf(tmp_path_factory, gif_animation_img, request):
tmpdir = tmp_path_factory.mktemp("gif_animation_pdf")
out_pdf = tmpdir / "out.pdf"
subprocess.check_call(
[
img2pdfprog,
"--producer=",
"--nodate",
"--engine=" + request.param,
"--output=" + str(out_pdf),
str(gif_animation_img),
]
)
pdfinfo = subprocess.check_output(["pdfinfo", str(out_pdf)])
assert re.search(
"^Pages: +2$", pdfinfo.decode("utf8"), re.MULTILINE
), identify.decode("utf8")
subprocess.check_call(["pdfseparate", str(out_pdf), str(tmpdir
/ "page-%d.pdf")])
for page in [1, 2]:
gif_animation_pdf_nr = tmpdir / ("page-%d.pdf" % page)
with pikepdf.open(gif_animation_pdf_nr) as p:
assert (
p.pages[0].Contents.read_bytes()
== b"q\n45. 0 0 45. 0. 0. cm\n/Im0
Do\nQ"
)
assert
p.pages[0].Resources.XObject.Im0.BitsPerComponent == 8
assert p.pages[0].Resources.XObject.Im0.ColorSpace[0] ==
"/Indexed"
E TypeError: object is not an array
src/img2pdf_test.py:4697: TypeError
ERROR at setup of test_gif_animation[pikepdf]
_
tmp_path_factory = TempPathFactory(_given_basetemp=None,
_trace=,
_basetemp=PosixPath('/tmp/pytest-of-debci/pytest-0'))
gif_animation_img =
PosixPath('/tmp/pytest-of-debci/pytest-0/gif_animation_img0/in.gif')
request = test_gif_animation[pikepdf]>>
@pytest.fixture(scope="session", params=["internal", "pikepdf"])
def gif_animation_pdf(tmp_path_factory, gif_animation_img, request):
tmpdir = tmp_path_factory.mktemp("gif_animation_pdf")
out_pdf = tmpdir / "out.pdf"
subprocess.check_call(
[
img2pdfprog,
"--producer=",
"--nodate",
"--engine=" + request.param,
"--output=" + str(out_pdf),
str(gif_animation_img),
]
)
pdfinfo = subprocess.check_output(["pdfinfo", str(out_pdf)])
assert re.search(
"^Pages: +2$", pdfinfo.decode("utf8"), re.MULTILINE
), identify.decode("utf8")
subprocess.check_call(["pdfseparate", str(out_pdf), str(tmpdir
/ "page-%d.pdf")])
for page in [1, 2]:
gif_animation_pdf_nr = tmpdir / ("page-%d.pdf" % page)
with pikepdf.open(gif_animation_pdf_nr) as p:
Processed: Re: fwbuilder: ftbfs with GCC-11
Processing control commands: > tags -1 patch Bug #984144 [src:fwbuilder] fwbuilder: ftbfs with GCC-11 Added tag(s) patch. -- 984144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002103: marked as done (ruby-fast-gettext: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError: undefined method `update_attributes' for #)
Your message dated Thu, 20 Jan 2022 15:11:48 + with message-id and subject line Bug#1002103: fixed in ruby-fast-gettext 2.0.3-2 has caused the Debian Bug report #1002103, regarding ruby-fast-gettext: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError: undefined method `update_attributes' for # 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.) -- 1002103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002103 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-fast-gettext Version: 2.0.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > NoMethodError: >undefined method `update_attributes' for > # >Did you mean? update_attribute > # > /usr/share/rubygems-integration/all/gems/activemodel-6.1.4.1/lib/active_model/attribute_methods.rb:469:in > `method_missing' > # ./spec/fast_gettext/translation_repository/db_spec.rb:115:in `block (2 > levels) in ' > > Finished in 1.03 seconds (files took 0.37403 seconds to load) > 262 examples, 1 failure, 1 pending > > Failed examples: > > rspec ./spec/fast_gettext/translation_repository/db_spec.rb:112 # > FastGettext::TranslationRepository::Db expires the cache when updated > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > mv ./.gem2deb.Gemfile.lock Gemfile.lock > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2021/12/20/ruby-fast-gettext_2.0.3-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: ruby-fast-gettext Source-Version: 2.0.3-2 Done: Utkarsh Gupta We believe that the bug you reported is fixed in the latest version of ruby-fast-gettext, 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 1002...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Utkarsh Gupta (supplier of updated ruby-fast-gettext 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, 20 Jan 2022 19:59:29 +0530 Source: ruby-fast-gettext Architecture: source Version: 2.0.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Utkarsh Gupta Closes: 1002103 Changes: ruby-fast-gettext (2.0.3-2) unstable; urgency=medium . [ Debian Janitor ] * Remove constraints unnecessary since buster: + Build-Depends: Drop versioned constraint on ruby-rspec. . [ Utkarsh Gupta ] * Drop the patch related to tainting. * Add patch to fix FTBFS. (Closes: #1002103) * Add patch to use update over update_attributes. * Add myself as an uploader. Checksums-Sha1: bebf91d19c7d25495f8467f24c3582b41c0c0396 2197 ruby-fast-gettext_2.0.3-2.dsc 8c1161128c6aed69c9909c8b47e4aebd1c51a893 92262 ruby-fast-gettext_2.0.3.orig.tar.gz f697a2a84b4168a2e11935d831bfb788648bdea5 8340 ruby-fast-gettext_2.0.3-2.debian.tar.xz 10a29e53624b7b77b692966e704b89cc57394326 14510 ruby-fast-gettext_2.0.3-2_source.buildinfo Checksums-Sha256: a17f6def69e68255982c94c19d96cab25538ca0f198e96c479e6a84647b8b8a1 2197 ruby-fast-gettext_2.0.3-2.dsc 7a58cd52a57911987b50747e890d4f810f4b271173431646274e1cfe5f605c0a 92262 ruby-fast-gettext_2.0.3.orig.tar.gz 3a3637c00e180905ca157a1e0ce0981f27ff0b6a060b64ccc6841f57ce5da70a 8340 ruby-fast-gettext_2.0.3-2.debian.tar.xz
Processed: golang-github-go-redis-redis: autopkgtest regression
Processing control commands: > severity -1 serious Bug #985011 [src:golang-github-go-redis-redis] golang-github-go-redis-redis: autopkgtest regression Severity set to 'serious' from 'normal' -- 985011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: openems: diff for NMU version 0.0.35+git20190103.6a75e98+dfsg.1-3.1
Processing control commands: > tags 1002429 + patch Bug #1002429 [src:openems] openems: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: 'debian/control' Added tag(s) patch. > tags 1002429 + pending Bug #1002429 [src:openems] openems: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: 'debian/control' Added tag(s) pending. -- 1002429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002429: openems: diff for NMU version 0.0.35+git20190103.6a75e98+dfsg.1-3.1
Control: tags 1002429 + patch Control: tags 1002429 + pending Dear maintainer, I've prepared an NMU for openems (versioned as 0.0.35+git20190103.6a75e98+dfsg.1-3.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru openems-0.0.35+git20190103.6a75e98+dfsg.1/debian/changelog openems-0.0.35+git20190103.6a75e98+dfsg.1/debian/changelog --- openems-0.0.35+git20190103.6a75e98+dfsg.1/debian/changelog 2021-02-21 13:09:58.0 +0200 +++ openems-0.0.35+git20190103.6a75e98+dfsg.1/debian/changelog 2022-01-20 13:19:49.0 +0200 @@ -1,3 +1,11 @@ +openems (0.0.35+git20190103.6a75e98+dfsg.1-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: PYBUILD_SYSTEM = distutils to workaround FTBFS +with new dh-python. (Closes: #1002429) + + -- Adrian Bunk Thu, 20 Jan 2022 13:19:49 +0200 + openems (0.0.35+git20190103.6a75e98+dfsg.1-3) unstable; urgency=medium * Team upload. diff -Nru openems-0.0.35+git20190103.6a75e98+dfsg.1/debian/rules openems-0.0.35+git20190103.6a75e98+dfsg.1/debian/rules --- openems-0.0.35+git20190103.6a75e98+dfsg.1/debian/rules 2021-02-21 11:42:01.0 +0200 +++ openems-0.0.35+git20190103.6a75e98+dfsg.1/debian/rules 2022-01-20 13:19:43.0 +0200 @@ -19,6 +19,7 @@ OCTAVE_FULLBPATH = $(OCTAVE_BPATH)/openems-0.0.35/$(OCTAVE_HOSTTYPE)-$(OCTAVE_API_VERSION) PYTHON3VERSIONS := $(shell py3versions -s -v) +export PYBUILD_SYSTEM = distutils export CXXFLAGS := $(CXXFLAGS) -DSSE_CORRECT_DENORMALS=0
Processed: tinydb 4.6.1 builds (but needs changes at least to the build dependencies)
Processing commands for cont...@bugs.debian.org:
> tags 1002394 fixed-upstream
Bug #1002394 [src:tinydb] tinydb: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1002394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1002390: lttnganalyses: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13
Processing control commands:
> reassign -1 python3-babeltrace 1.5.8-1
Bug #1002390 [src:lttnganalyses] lttnganalyses: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13
Bug reassigned from package 'src:lttnganalyses' to 'python3-babeltrace'.
No longer marked as found in versions lttnganalyses/0.6.1-2.
Ignoring request to alter fixed versions of bug #1002390 to the same values
previously set
Bug #1002390 [python3-babeltrace] lttnganalyses: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13
Marked as found in versions babeltrace/1.5.8-1.
> retitle -1 python3-babeltrace does not work with Python 3.10
Bug #1002390 [python3-babeltrace] lttnganalyses: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13
Changed Bug title to 'python3-babeltrace does not work with Python 3.10' from
'lttnganalyses: FTBFS: dh_auto_test: error: pybuild --test -i python{version}
-p "3.10 3.9" returned exit code 13'.
> affects -1 src:lttnganalyses
Bug #1002390 [python3-babeltrace] python3-babeltrace does not work with Python
3.10
Added indication that 1002390 affects src:lttnganalyses
> forwarded -1
> http://git.efficios.com/?p=babeltrace.git;a=commit;h=64b7b73406242324460e4df149eff329b289192a
Bug #1002390 [python3-babeltrace] python3-babeltrace does not work with Python
3.10
Set Bug forwarded-to-address to
'http://git.efficios.com/?p=babeltrace.git;a=commit;h=64b7b73406242324460e4df149eff329b289192a'.
--
1002390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1002390: lttnganalyses: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13
Control: reassign -1 python3-babeltrace 1.5.8-1 Control: retitle -1 python3-babeltrace does not work with Python 3.10 Control: affects -1 src:lttnganalyses Control: forwarded -1 http://git.efficios.com/?p=babeltrace.git;a=commit;h=64b7b73406242324460e4df149eff329b289192a On Sat, Jan 01, 2022 at 09:08:59AM +0100, s3v wrote: > Dear Maintainer, > > This issue is being caused by babeltrace and affects your package [1]. > "Mapping" abstract class was moved from the collections module to the > collections.abc > module and > importing from the former leads to an error starting from Python 3.10. Thanks, reassigning and linking to the upstream fix. > Kind Regards and happy new year :) > > [1] > https://sources.debian.org/src/babeltrace/1.5.8-1/bindings/python/babeltrace/babeltrace.i.in/#L676 cu Adrian
Processed: google-guest-agent,python3-google-compute-engine: both ship /usr/bin/google_metadata_script_runner
Processing control commands: > found -1 2026.00-1 Bug #1004071 [google-guest-agent,python3-google-compute-engine] google-guest-agent,python3-google-compute-engine: both ship /usr/bin/google_metadata_script_runner There is no source info for the package 'python3-google-compute-engine' at version '2026.00-1' with architecture '' Marked as found in versions google-guest-agent/2026.00-1. > found -1 20190916-1 Bug #1004071 [google-guest-agent,python3-google-compute-engine] google-guest-agent,python3-google-compute-engine: both ship /usr/bin/google_metadata_script_runner There is no source info for the package 'google-guest-agent' at version '20190916-1' with architecture '' Marked as found in versions google-compute-image-packages/20190916-1. -- 1004071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004071 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004071: google-guest-agent,python3-google-compute-engine: both ship /usr/bin/google_metadata_script_runner
Package: google-guest-agent,python3-google-compute-engine Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 2026.00-1 Control: found -1 20190916-1 Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package python3-google-compute-engine. Preparing to unpack .../5-python3-google-compute-engine_20190916-1_all.deb ... Unpacking python3-google-compute-engine (20190916-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-8A9en2/5-python3-google-compute-engine_20190916-1_all.deb (--unpack): trying to overwrite '/usr/bin/google_metadata_script_runner', which is also in package google-guest-agent 2026.00-1 Errors were encountered while processing: /tmp/apt-dpkg-install-8A9en2/5-python3-google-compute-engine_20190916-1_all.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/bin/google_metadata_script_runner This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html google-guest-agent=2026.00-1_python3-google-compute-engine=20190916-1.log.gz Description: application/gzip
Bug#1004068: origami-pdf: FTBFS: TestSign#test_sign: ArgumentError: wrong number of arguments (given 1, expected 0; required keyword: year)
Source: origami-pdf Version: 2.1.0-1~exp1 Severity: serious Hi, origami-pdf/experimental recently started to FTBFS (origami-pdf/sid is not affected): [...] ┌──┐ │ Run tests for ruby3.0 from debian/ruby-tests.rake│ └──┘ RUBYLIB=/build/origami-pdf-2.1.0/debian/ruby-origami/usr/lib/ruby/vendor_ruby:. GEM_PATH=/build/origami-pdf-2.1.0/debian/ruby-origami/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 ruby3.0 -S rake -f debian/ruby-tests.rake /usr/bin/ruby3.0 -w -I"test" /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb "test/test_pdf.rb" -v Run options: -v --seed 1938 # Running: TestXrefs#test_xrefstream = 0.01 s = . TestXrefs#test_xreftable = 0.00 s = . TestPDFCreate#test_pdf_create = 0.00 s = . TestStreams#test_object_stream = 0.02 s = . TestStreams#test_predictors = 0.00 s = E TestStreams#test_filter_ascii85 = 0.03 s = . TestStreams#test_filter_asciihex = 0.00 s = . TestStreams#test_filter_rle = 0.00 s = . TestStreams#test_filter_ccittfax = 0.03 s = . TestStreams#test_filter_lzw = 0.01 s = . TestStreams#test_filter_flate = 0.00 s = . TestStreams#test_stream = 0.01 s = . TestEncryption#test_decrypt_aes_256b = 0.01 s = . TestEncryption#test_encrypt_rc4_128b = 0.00 s = . TestEncryption#test_decrypt_aes_128b = 0.00 s = . TestEncryption#test_decrypt_rc4_128b = 0.00 s = . TestEncryption#test_encrypt_aes_128b = 0.00 s = . TestEncryption#test_crypt_filter = 0.00 s = . TestEncryption#test_decrypt_rc4_40b = 0.00 s = . TestEncryption#test_encrypt_rc4_40b = 0.00 s = . TestForms#test_create_acroform = 0.00 s = . TestAnnotations#test_annotations = 0.00 s = . TestAnnotations#test_annotation_actions = 0.00 s = . TestPages#test_append_page = 0.00 s = . TestPages#test_example_write_page = 0.00 s = . TestSign#test_sign = 0.02 s = E TestActions#test_page_actions = 0.00 s = . TestActions#test_pdf_actions = 0.00 s = . TestPDFObjects#test_pdf_object_tree = 0.00 s = . TestAttachment#test_attach_file = 0.00 s = . TestPDFLazyParser#test_random_access = 0.00 s = . TestPDFLazyParser#test_save_pdf_lazy = 0.01 s = . TestPDFLazyParser#test_parse_pdf_lazy = 0.00 s = . TestPDFParser#test_parse_name = 0.00 s = . TestPDFParser#test_parse_reference = 0.00 s = . TestPDFParser#test_parse_dictionary = 0.00 s = . TestPDFParser#test_parse_int = 0.00 s = . TestPDFParser#test_parse_pdf = 0.00 s = . TestPDFParser#test_parse_real = 0.00 s = . TestPDFParser#test_parse_bool = 0.00 s = . TestPDFParser#test_parse_string = 0.00 s = . Finished in 0.189514s, 216.3427 runs/s, 1677.9750 assertions/s. 1) Error: TestStreams#test_predictors: ArgumentError: wrong number of arguments (given 2, expected 1) /build/origami-pdf-2.1.0/lib/origami/filters/predictors.rb:83:in `apply_pre_prediction' /build/origami-pdf-2.1.0/lib/origami/filters/predictors.rb:65:in `pre_prediction' /build/origami-pdf-2.1.0/lib/origami/filters/flate.rb:44:in `encode' /build/origami-pdf-2.1.0/lib/origami/filters.rb:351:in `encode' /build/origami-pdf-2.1.0/lib/origami/stream.rb:479:in `encode_data' /build/origami-pdf-2.1.0/lib/origami/stream.rb:377:in `block in encode!' /build/origami-pdf-2.1.0/lib/origami/stream.rb:365:in `downto' /build/origami-pdf-2.1.0/lib/origami/stream.rb:365:in `encode!' /build/origami-pdf-2.1.0/lib/origami/stream.rb:287:in `encoded_data' /build/origami-pdf-2.1.0/test/test_streams.rb:14:in `test_predictors' /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run' /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions' /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run' /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it' /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run' /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler' /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run' /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method' /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method' /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run' /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each' /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run' /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler' /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run' /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run' /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map'
Bug#1004067: imath: causes openexr to FTBFS
Source: imath Version: 3.1.3-9 Severity: serious Control: affects -1 + src:openexr Hi, openexr/experimental recently started to FTBFS, cmake aborts after an imath related error: CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Imath/ImathConfig.cmake:109 (message): The imported target "Imath::PyImath_Python3_9" references the file "/usr/lib/x86_64-linux-gnu/libPyImath_Python3_9-3_1.so.29.2.0" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/x86_64-linux-gnu/cmake/Imath/ImathConfig.cmake" but not all the files it references. Call Stack (most recent call first): cmake/OpenEXRSetup.cmake:259 (find_package) CMakeLists.txt:59 (include) -- Configuring incomplete, errors occurred! My previous and successful build attempt of openexr/experimental was on Dec 7. (openexr/sid is not affected) Andreas openexr_3.1.3-2.log.gz Description: application/gzip
Processed: imath: causes openexr to FTBFS
Processing control commands: > affects -1 + src:openexr Bug #1004067 [src:imath] imath: causes openexr to FTBFS Added indication that 1004067 affects src:openexr -- 1004067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004066: groestlcoin: FTBFS pubkey.cpp:181:96: error: invalid conversion from 'secp256k1_xonly_pubkey*' to 'size_t'
Source: groestlcoin
Version: 2.21.1~dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
groestlcoin recently started to FTBFS after some build-dependency or
toolchain package got updated:
g++ -std=c++11 -DHAVE_CONFIG_H -I. -I../src/config-I.
-DBOOST_SP_USE_STD_ATOMIC -DBOOST_AC_USE_STD_ATOMIC -pthread -I/usr/include
-Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_BUILD_INFO -D__STDC_FORMAT_MACROS
-fstack-reuse=none -g -O2 -ffile-prefix-m
ap=/build/groestlcoin-2.21.1~dfsg=. -fstack-protector-strong -Wformat
-Werror=format-security -fPIC -fno-extended-identifiers -c -o
libgroestlcoin_consensus_a-pubkey.o `test -f 'pubkey.cpp' || echo
'./'`pubkey.cpp
pubkey.cpp: In member function 'bool XOnlyPubKey::VerifySchnorr(const uint256&,
Span) const':
pubkey.cpp:181:96: error: invalid conversion from 'secp256k1_xonly_pubkey*' to
'size_t' {aka 'long unsigned int'} [-fpermissive]
181 | return secp256k1_schnorrsig_verify(secp256k1_context_verify,
sigbytes.data(), msg.begin(), );
|
^~~
|
|
|
secp256k1_xonly_pubkey*
pubkey.cpp:181:39: error: too few arguments to function 'int
secp256k1_schnorrsig_verify(const secp256k1_context*, const unsigned char*,
const unsigned char*, size_t, const secp256k1_xonly_pubkey*)'
181 | return secp256k1_schnorrsig_verify(secp256k1_context_verify,
sigbytes.data(), msg.begin(), );
|
~~~^
In file included from pubkey.cpp:10:
/usr/include/secp256k1_schnorrsig.h:158:48: note: declared here
158 | SECP256K1_API SECP256K1_WARN_UNUSED_RESULT int
secp256k1_schnorrsig_verify(
|
^~~
g++ -std=c++11 -DHAVE_CONFIG_H -I. -I../src/config-I.
-DBOOST_SP_USE_STD_ATOMIC -DBOOST_AC_USE_STD_ATOMIC -pthread -I/usr/include
-Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_BUILD_INFO -D__STDC_FORMAT_MACROS
-fstack-reuse=none -g -O2
-ffile-prefix-map=/build/groestlcoin-2.21.1~dfsg=. -fstack-protector-strong
-Wformat -Werror=format-security -fPIC -fno-extended-identifiers -c -o
script/libgroestlcoin_consensus_a-groestlcoinconsensus.o `test -f
'script/groestlcoinconsensus.cpp' || echo './'`script/groestlcoinconsensus.cpp
make[2]: *** [Makefile:11718: libgroestlcoin_consensus_a-pubkey.o] Error 1
Andreas
groestlcoin_2.21.1~dfsg-1.log.gz
Description: application/gzip
Bug#1002988: Waiting for b-deps
Hi, now camlp5 8.* is in unstable the problem occurs ; I'm just waiting for the other b-deps to be available, but I have a commit ready. Cheers, J.Puydt
Bug#1004060: systemd: breaks lightdm / lightdm-gtk-greeter
Control: tags -1 + unreproducible moreinfo Control: severity -1 important Am 20.01.22 um 05:08 schrieb Vincent Lefevre: Package: systemd Version: 250.3-1 Severity: critical Justification: breaks unrelated software The upgrade to systemd 250.3-1 breaks lightdm / lightdm-gtk-greeter: the menu bar and login dialog no longer appear. I quickly checked the changelog between 250.2 and 250.3 [1] but didn't find anything which might appear relevant (the closest maybe being 19fbd7764d) In a next step, I tried lightdm in VM and it came up just fine with 250.3-1 (see attached screenshot). It is thus likely that this issue is specific to your system. I'm thererfor marking the issue as unreproducible for now. I guess your best bet is to run git bisect to find the offending commit. Regards, [1] 1b003bbc80 (HEAD -> v250-stable, tag: v250.3, origin/v250-stable) pid1,cgroup-show: ignore -EOPNOTSUPP in cg_read_pid() 7fc41274e6 stdio-bridge: make the error more straightforward fdcb1bf673 kernel-install: also remove modules.builtin.alias.bin 8c4badc445 man: enhance the description of systemd-stdio-bridge 33aba4c50a systemd-stdio-bridge: add manpage 5cc70d1759 man: change 'allow[s] to' -> 'allow[s] one to' 44198d7ddb core: add missing dependency DBus properties 9f43dde134 core: update log message 0874eaefa3 network: wireguard: also accept negative boolean values to disable adding routes 417622f42b network: wireguard: do not add routes to AllowedIPs= by default 18aff8c857 sd-device: silence gcc warning with newest gcc 5b44d30087 journal: Fix entry array iteration corruption checks ef108015f3 journal: Remove unused arguments from journal_file_next_entry_for_data() 6a6182c3f4 man: Add more details about desktop file processing 7f3e962f08 boot: Don't try to free loaded_image 34e5084c14 boot: Fix invalid free d44050a015 test: add testcase for broken NTP server option 2a7279f226 test: voidify test functions ab73799568 sd-dhcp6-client: expose client_parse_message() bc56b640f6 sd-dhcp6-client: ignore broken non-critical options d72db2d7ca journal: Don't discard -b arg when followed by -e 556f46aa3b journal: Skip data objects with invalid offsets 19fbd7764d xdg-autostart-service: Ignore missing desktop-sepcific condition binary 704d859eeb man+docs: adjust links to the new page 944d8d9050 policy files: adjust landing page link e7ed0ba895 docs: use https:// for fd.o links 26271c128a README: link to the new page 2b075f74cb NEWS: adjust links to moved pages 32f33c9474 fix test-string-util failed when locale is not utf8 27d141acdf nss: only read logging config from environment variables 2176cec5ec nss: drop dummy setup_logging() helpers 96826c48ad bootctl: do not update sd-boot if it wasn't installed in the first place 527c9002b5 bootctl: split out the check whether sd-boot is installed 9a109a9a11 sd-bus/man: document EBUSY error in bus_message_read (#21954) e9a0404b76 boot: Fix readdir_harder() on VirtualBox OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: Bug#1004060: systemd: breaks lightdm / lightdm-gtk-greeter
Processing control commands: > tags -1 + unreproducible moreinfo Bug #1004060 [systemd] systemd: breaks lightdm / lightdm-gtk-greeter Added tag(s) unreproducible and moreinfo. > severity -1 important Bug #1004060 [systemd] systemd: breaks lightdm / lightdm-gtk-greeter Severity set to 'important' from 'critical' -- 1004060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004060 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002369: marked as done (piglit: FTBFS: AttributeError: module 'collections' has no attribute 'MutableMapping')
Your message dated Thu, 20 Jan 2022 08:49:25 + with message-id and subject line Bug#1002369: fixed in piglit 0~git20220119-124bca3c9-1 has caused the Debian Bug report #1002369, regarding piglit: FTBFS: AttributeError: module 'collections' has no attribute 'MutableMapping' 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.) -- 1002369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: piglit Version: 0~git20200212-f4710c51b-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > [ 0%] Generating builtin_cl_int_tests.list > cd "/<>/obj-x86_64-linux-gnu/generated_tests" && > /usr/bin/python3.10 "/<>/generated_tests/gen_cl_int_builtins.py" > > builtin_cl_int_tests.list > [ 0%] Generating ../../../tests/opengl.xml.gz > [ 0%] Generating builtin_packing_tests.list > cd "/<>/obj-x86_64-linux-gnu/target_api/no_api/tests" && > /usr/bin/cmake -E env > "PIGLIT_BUILD_TREE=/<>/obj-x86_64-linux-gnu" /usr/bin/python3.10 > "/<>/tests/serializer.py" opengl > "/<>/tests/opengl.py" > "/<>/obj-x86_64-linux-gnu/tests/opengl.xml.gz" > cd "/<>/obj-x86_64-linux-gnu/generated_tests" && > /usr/bin/python3.10 > "/<>/generated_tests/gen_builtin_packing_tests.py" > > builtin_packing_tests.list > Traceback (most recent call last): > File "/<>/tests/serializer.py", line 34, in > from framework.test.piglit_test import ( > File "/<>/tests/../framework/test/__init__.py", line 31, in > > from .base import * > File "/<>/tests/../framework/test/base.py", line 46, in > > from framework.results import TestResult > File "/<>/tests/../framework/results.py", line 42, in > class Subtests(collections.MutableMapping): > AttributeError: module 'collections' has no attribute 'MutableMapping' > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make[3]: *** > [target_api/no_api/tests/CMakeFiles/generate-opengl-xml.dir/build.make:77: > tests/opengl.xml.gz] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/12/20/piglit_0~git20200212-f4710c51b-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: piglit Source-Version: 0~git20220119-124bca3c9-1 Done: Jordan Justen We believe that the bug you reported is fixed in the latest version of piglit, 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 1002...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jordan Justen (supplier of updated piglit 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, 19 Jan 2022 23:32:20 -0800 Source: piglit Architecture: source Version: 0~git20220119-124bca3c9-1 Distribution: unstable Urgency: medium Maintainer: Jordan Justen Changed-By: Jordan Justen Closes: 1002369 Changes: piglit (0~git20220119-124bca3c9-1) unstable; urgency=medium . * Update piglit upstream version to 124bca3c9 (Closes: #1002369) * d/control: Add vulkan build dependencies * debian: Convert to cmake ninja build * d/control: Set Standards-Version to 4.6.0.1 * d/control: Set debhelper-compat to 13 * debian: Remove old lintian overrides * d/rules: Set DEB_BUILD_MAINT_OPTIONS = hardening=+all for lintian hardening-no-bindnow * d/piglit.lintian-overrides: Skip package-contains-documentation-outside-usr-share-doc for asmparsertest tests * d/piglit-dbgsym.lintian-overrides: Skip elf-error for debug symbol files * d/control: Update
Bug#1003964: pandoc doesn't start: error while loading shared libraries: libcmark-gfm.so.0.29.0.gfm.0
Quoting Keith Packard (2022-01-20 02:28:30) > Keith Packard writes: > > > Suggestions welcome, but it looks like Sebastian may be right and that I > > need to change the package name of the libraries at each release. Ick. > > I've put together a patch which does this, automatically generating new > package names for each upstream cmark-gfm release. > > https://salsa.debian.org/keithp/cmark-gfm/-/commits/lib-autogen > > This uses a gbp buildpackage hook to automatically generate > debian/control and the library debian/*.install files as those now > depend on the upstream package version in ways that dpkg-gencontrol > isn't sufficient to deal with. > > This does clear the lintian warning about so name not matching package > version at least, so maybe I should have been listening more closely to Looks good to me. But then again, I was the one with the wrong approach here, so not sure how much my input can be trusted ;-) - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1003490: u-boot: FTBFS on arch:all with qemu-ppce500 target
Hi Vagrant!
On 1/11/22 02:10, Vagrant Cascadian wrote:
> Something in the toolchain recently changed which causes u-boot arch:all
> build to FTBFS... I suspect binutils, as building in "bookworm" still
> works fine where binutils hasn't yet migrated.
>
> On arch:all builds the qemu-ppce500 target is cross-compiled.
>
> Full log:
>
>
> https://buildd.debian.org/status/fetch.php?pkg=u-boot=all=2022.01%2Bdfsg-1=1641860624=0
>
> The hopefully relevent lines from the build log:
> ...
> {standard input}: Assembler messages:
> {standard input}:127: Error: unrecognized opcode: `tlbre'
> {standard input}:418: Error: unrecognized opcode: `tlbre'
> {standard input}:821: Error: unrecognized opcode: `msync'
> {standard input}:821: Error: unrecognized opcode: `tlbwe'
> {standard input}:884: Error: unrecognized opcode: `tlbsx'
> make[4]: *** [/<>/scripts/Makefile.build:253:
> arch/powerpc/cpu/mpc85xx/tlb.o] Error 1
> make[3]: *** [/<>/Makefile:1810: arch/powerpc/cpu/mpc85xx] Error
> 2
> make[3]: *** Waiting for unfinished jobs
> powerpc-linux-gnu-gcc -Wp,-MD,arch/powerpc/lib/.traps.o.d -nost
>
>
> If anyone has thoughts what might be the issue, please chime in!
It's most likely this upstream change [1] in binutils that broke the build.
It also affects glibc [2] and the kernel [3][4], for example.
Adrian
> [1]
> https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=b25f942e18d6ecd7ec3e2d2e9930eb4f996c258a
> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003847
> [3]
> https://buildd.debian.org/status/fetch.php?pkg=linux=powerpc=5.15.15-1=1642579068=0
> [4]
> https://buildd.debian.org/status/fetch.php?pkg=linux=ppc64=5.15.15-1=1642578946=0
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Processed: src:raft: fails to migrate to testing for too long: FTBFS on i386 and mipsel
Processing control commands: > close -1 0.11.2+git211214-1 Bug #1004065 [src:raft] src:raft: fails to migrate to testing for too long: FTBFS on i386 and mipsel Marked as fixed in versions raft/0.11.2+git211214-1. Bug #1004065 [src:raft] src:raft: fails to migrate to testing for too long: FTBFS on i386 and mipsel Marked Bug as done -- 1004065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004065 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004065: src:raft: fails to migrate to testing for too long: FTBFS on i386 and mipsel
Source: raft Version: 0.9.25-1 Severity: serious Control: close -1 0.11.2+git211214-1 Tags: sid bookworm ftbfs 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:raft has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package failed to build from source on i386 and mipsel, while it built there in the past. 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/msg5.html [2] https://qa.debian.org/excuses.php?package=raft OpenPGP_signature Description: OpenPGP digital signature
