Bug#1002900: marked as done (darktable: FTBFS on arm64)
Your message dated Wed, 12 Jan 2022 03:04:03 + with message-id and subject line Bug#1002900: fixed in darktable 3.8.0-2 has caused the Debian Bug report #1002900, regarding darktable: FTBFS on arm64 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.) -- 1002900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: darktable Version: 3.8.0-1 Severity: serious Tags: fixed-upstream Justification: FTBFS, previously did on this architecture -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 See [1] for the full log. __DT_CLONE_TARGETS__ is undefined on aarch64. Fixed upstream in the darktable-3.8.x branch. There are quite a few fixes in that branch, so it may be worth waiting for a point release (or packaging a snapshot) rather than cherry-picking a fix for this bug. [1]: https://buildd.debian.org/status/fetch.php?pkg=darktable=arm64=3.8.0-1=1640868741=0 - -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages darktable depends on: ii libc62.33-1 ii libcairo21.16.0-5 ii libcolord-gtk1 0.1.26-2+b1 ii libcolord2 1.4.5-3 ii libcups2 2.3.3op2-7 ii libcurl3-gnutls 7.79.1-2 ii libexiv2-27 0.27.3-3.1 ii libgcc-s111.2.0-13 ii libgdk-pixbuf-2.0-0 2.42.6+dfsg-2 ii libglib2.0-0 2.70.2-1 ii libgomp1 11.2.0-13 ii libgphoto2-6 2.5.27-1 ii libgphoto2-port122.5.27-1 ii libgraphicsmagick-q16-3 1.4+really1.3.37-1 ii libgtk-3-0 3.24.31-1 ii libicu67 67.1-7 ii libilmbase25 2.5.7-2 ii libjpeg62-turbo 1:2.1.2-1 ii libjson-glib-1.0-0 1.6.6-1 ii liblcms2-2 2.12~rc1-2 ii liblensfun1 0.3.2-6 ii libopenexr25 2.5.7-1 ii libopenjp2-7 2.4.0-3 ii libosmgpsmap-1.0-1 1.2.0-1 ii libpango-1.0-0 1.48.10+ds1-1 ii libpangocairo-1.0-0 1.48.10+ds1-1 ii libpng16-16 1.6.37-3 ii libpugixml1v51.11.4-1 ii librsvg2-2 2.50.7+dfsg-2 ii libsecret-1-00.20.4-2 ii libsoup2.4-1 2.74.2-3 ii libsqlite3-0 3.36.0-2 ii libstdc++6 11.2.0-13 ii libtiff5 4.3.0-2 ii libwebp6 0.6.1-2.1 ii libx11-6 2:1.7.2-2+b1 ii libxml2 2.9.12+dfsg-5+b1 ii libxrandr2 2:1.5.2-1 ii zlib1g 1:1.2.11.dfsg-2 darktable recommends no packages. darktable suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmHO7G8ACgkQA0U5G1Wq FSHz1g/+Ov/i1IEujrRSFfdblQ676PJEOaonHAkxOAV0Z4lMAYZXf01c8c0AkSC+ GxDagr0hcDfqEZaxavmaps+D30MUwptBAf/7/Cfj13AFNOZ13Xls2q9jpZfkjYRp WnIBL9Rapyws6BtphU8LGTNkioVGrMYEMOwYCpLao1uWs4TbHJzhyxZnbxFpHJc4 BTLfXf/ZNZVRX5zTuR37f3qFXO10JjapzMt/Po8gIbRH3bnmsz+JppbJtlzj1a/W keTibD5cxjllpynUhj8Rz5XDTl3a6GlJeOuhOpMm1pLmk+I4GfWueXrbf5loLj5q gmvz0RgvjnBZpzx5plR+NPnhL4ryhY8g613feU1MeJlMZmVZSRbFVhDmzCTuFiuo ZvCHZeMV9u3c6xLR9pKG/t02/MvfEF0LuE8RnD0+fbFm4+jAHwvxVvQLZPVkVL5X H8Z06GzBC3ehRqxZCAyu2alTX8mqHN3qeHaJ9nfa9M6QToeTXJhroGtVUd94PSxe kcCFMVUqkP4QRtcVX0w3968YW2GMqaGBAstrg95qSymdzJoatGzSqTo25/rq5fYC NFJBuJYC/LWCKcT+GY2d8+SN6708aKblC15v1MCRW6ZxjOdTC66rV/1ivaQ2Qbuk urGmmEJOlVVluAFvH3A+ct3LEkDcDzDCaCe6I6RD+UewW58SLMg= =W6FW -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: darktable Source-Version: 3.8.0-2 Done: David Bremner We believe that the bug you reported is fixed in the latest version of darktable, 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. David Bremner (supplier of updated darktable
Bug#1000716: marked as done (ponyorm: FTBFS on Python 3.10)
Your message dated Wed, 12 Jan 2022 02:38:52 + with message-id and subject line Bug#1000716: fixed in ponyorm 0.7.15~rc1+ds-1 has caused the Debian Bug report #1000716, regarding ponyorm: FTBFS on Python 3.10 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.) -- 1000716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000716 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pony Version: 0.7.14-1 Severity: serious User: debian-pyt...@lists.debian.org Usertags: python3.10 Hello, It seems the current version of ponyorm is broken on python3.10. If you look closely at the logs from the latest DebCI run [1], it outputs (without failing): > Sorry, but pony 0.7.14 requires Python of one of the following > versions: 2.7, 3.3-3.9. You have version 3.10.0+ Actually running pony on 3.10 outputs something like: == ERROR: tests (unittest.loader._FailedTest) -- ImportError: Failed to import test module: tests Traceback (most recent call last): File "/usr/lib/python3.10/unittest/loader.py", line 154, in loadTestsFromName module = __import__(module_name) File "/<>/tests/__init__.py", line 11, in from . import base File "/<>/tests/base/__init__.py", line 10, in from .test_cli import CLITestCase File "/<>/tests/base/test_cli.py", line 14, in from pony.orm import db_session File "/usr/lib/python3/dist-packages/pony/orm/__init__.py", line 3, in from pony.orm.core import * File "/usr/lib/python3/dist-packages/pony/orm/core.py", line 18, in from pony.thirdparty.compiler import ast, parse File "/usr/lib/python3/dist-packages/pony/thirdparty/compiler/__init__.py", line 24, in from .transformer import parse, parseFile File "/usr/lib/python3/dist-packages/pony/thirdparty/compiler/transformer.py", line 32, in import parser ModuleNotFoundError: No module named 'parser' This is because the parser module has been removed in Python 3.10 in favor of ast [2]. I'll suggest upstream to fail their testsuite when ran on Python 3.10. [1]: https://ci.debian.net/data/autopkgtest/unstable/amd64/p/ponyorm/17023056/log.gz [2]: https://docs.python.org/3/whatsnew/3.9.html#new-parser -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: ponyorm Source-Version: 0.7.15~rc1+ds-1 Done: Louis-Philippe Véronneau We believe that the bug you reported is fixed in the latest version of ponyorm, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Louis-Philippe Véronneau (supplier of updated ponyorm 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: Tue, 11 Jan 2022 21:12:48 -0500 Source: ponyorm Architecture: source Version: 0.7.15~rc1+ds-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Louis-Philippe Véronneau Closes: 1000716 Changes: ponyorm (0.7.15~rc1+ds-1) unstable; urgency=medium . * Team upload. . [ Louis-Philippe Véronneau ] * New upstream release. (Closes: #1000716) * d/tests: run the upstream testsuite with "set -efu" to catch error codes. * d/watch: use the github releases. * d/gbp.conf: add file. * d/copyright: repack to not include a thirdparty file we don't install anyway. * d/patches: refresh. * d/copyright: remove old files and update date. * d/control: Standards-Version update to 4.6.0. No changes. Checksums-Sha1: 8e022eb69c66f52b8af0305ffdde6abca04b8b86 1562 ponyorm_0.7.15~rc1+ds-1.dsc 24e1780ce5dae06cebb3e6e45979128a890ce8a2 203848 ponyorm_0.7.15~rc1+ds.orig.tar.xz 2b38b6613fe0ea40abc5fdef1a692749879a5dfd 3256 ponyorm_0.7.15~rc1+ds-1.debian.tar.xz 552b87a930587483744ec170887a22f8b366ea26 6921 ponyorm_0.7.15~rc1+ds-1_amd64.buildinfo Checksums-Sha256: 941093cf2b9577639cf1d1bcd569fc9141100c17d708564e89ddf5d7f2f130ef
Bug#999131: uqm-russian: provide fix by using dh sequencer
Package: uqm-russian Version: 1.0.2-5 Followup-For: Bug #999131 X-Debbugs-Cc: mnalis-debian...@voyager.hr Control: tags -1 patch Here is a MR to fix this, by using dh sequencer: https://salsa.debian.org/games-team/uqm-russian/-/merge_requests/1
Processed: uqm-russian: provide fix by using dh sequencer
Processing control commands: > tags -1 patch Bug #999131 [src:uqm-russian] uqm-russian: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. -- 999131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000571: marked as done (phpmyadmin: autopkgtest fails with PHP8.1 (in experimental))
Your message dated Wed, 12 Jan 2022 01:48:55 + with message-id and subject line Bug#1000571: fixed in phpmyadmin 4:5.1.1+dfsg1-5 has caused the Debian Bug report #1000571, regarding phpmyadmin: autopkgtest fails with PHP8.1 (in experimental) 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.) -- 1000571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phpmyadmin Version: 4:5.1.1+dfsg1-4 Severity: important Control: block 976811 by -1 Dear maintainer, We're in the process of transitioning to php8.1 (see bug #976811). As part of that, the default PHP in experimental has been switched to 8.1. The pseudo excuses [1] show that the autopkgtest of phpmyadmin fails with PHP8.1 with the error pasted below. Apart from the failure (which to my eye seems to only be a test failure, so thing might not be so bad) there are a lot of deprecation warnings. Please fix the autopkgtest to support PHP8.1. Paul [1] https://release.debian.org/britney/pseudo-excuses-experimental.html#php-defaults There was 1 error: 1) PhpMyAdmin\Tests\Dbal\DbiMysqliTest::testStoreResult PHPUnit\Framework\MockObject\IncompatibleReturnValueException: Method store_result may not return value of type boolean, its declared return type is "false|mysqli_result" /tmp/autopkgtest-lxc.8iuz2hkx/downtmp/build.Pi1/src/test/classes/Dbal/DbiMysqliTest.php:180 /usr/bin/phpunit:73 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: phpmyadmin Source-Version: 4:5.1.1+dfsg1-5 Done: William Desportes We believe that the bug you reported is fixed in the latest version of phpmyadmin, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. William Desportes (supplier of updated phpmyadmin 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: Wed, 12 Jan 2022 02:27:47 +0100 Source: phpmyadmin Built-For-Profiles: noudeb Architecture: source Version: 4:5.1.1+dfsg1-5 Distribution: unstable Urgency: medium Maintainer: phpMyAdmin Packaging Team Changed-By: William Desportes Closes: 1000571 Changes: phpmyadmin (4:5.1.1+dfsg1-5) unstable; urgency=medium . * Add a patch to fix PHP 8.1 test failure (Closes: #1000571) * Add a patch to remove PHP 8.1 deprecation issues (Closes: #1000571) * Update d/copyright Checksums-Sha1: 5b90308cb3e74c4e24878f7328bbce84e48f2e1d 2640 phpmyadmin_5.1.1+dfsg1-5.dsc 3e533715294813d1bf2d07750e53b80467fb99bf 10162288 phpmyadmin_5.1.1+dfsg1.orig.tar.xz b4cf67083a5cdcc678793664feb51d47bdf5d217 1731772 phpmyadmin_5.1.1+dfsg1-5.debian.tar.xz 8052393cff8ebbe1c22912bfa30d087274ec538f 23289 phpmyadmin_5.1.1+dfsg1-5_source.buildinfo Checksums-Sha256: 97db13f81a7adb057414fe98adfe2b97d9b8dc432699541facb1aa5e20a02880 2640 phpmyadmin_5.1.1+dfsg1-5.dsc 2ea0ba9c2ac3f6c625be60be1013752dff2e852cc40f85c4b0e94c782ae98d93 10162288 phpmyadmin_5.1.1+dfsg1.orig.tar.xz f637aca2ddd59ce564e0334169302ad67f8be4053ea7408e94a88b66c0a2f756 1731772 phpmyadmin_5.1.1+dfsg1-5.debian.tar.xz 16abf529ae26f78187fe66d6e744559f0f25c267d6fd410305c95f0719c0c9ed 23289 phpmyadmin_5.1.1+dfsg1-5_source.buildinfo Files: 92606d21bee41c8625bb91b90e010fb3 2640 web optional phpmyadmin_5.1.1+dfsg1-5.dsc 5e519e2087be1d81b4f8ae9a0657158a 10162288 web optional phpmyadmin_5.1.1+dfsg1.orig.tar.xz 60710e31c0d4905f8af319d2dccb37ed 1731772 web optional phpmyadmin_5.1.1+dfsg1-5.debian.tar.xz 1d6afc3e9333ff8e069fdd0f546f5de2 23289 web optional phpmyadmin_5.1.1+dfsg1-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEExNkf3872tKPGU/14kKDvG4JRqIkFAmHeLvsACgkQkKDvG4JR qIkZQQ//V2nzerOtwIB+fdHHdSKnknHor2wLmbhd+nxbPcsT/boXpy/9ScbAOl3k c12vIsKUAjE2YGSCbyU1oqQcBFmtx287uDn4FwMFaycyi4tcwJN5hQ6l3iFQHgCL LOYo1GV8/CunidnEQm26PInmhFgC5JfleBnBZH6g0d4djBVpieayVobm7fmgcGJc dC46MYvnS9Ns+kr46GxXDG+N1dxfF1IfhXL7guqgfOn+SwFBRExtHQ4N67rHIjx+ a+zFMIIbs+M+8JNLY07aTkmaCvyMZ07MoYCOqSsc/hbrHla1jN13CNbQTP2T9g0k mWweTR/bquh7fa8wsAJcixytKoFFWjuyct+XcRIdTvwrQzqYqyh6HnkSgHGe3umu
Bug#1003530: lintian: Hangs when checking some .dsc file
Control: notfound 1003530 2.114.0 Control: close 1003530 Hi Mattia, Thanks for the info. For the local test: I ran the test on my machine and it took slightly less than 1 hour to finish. I didn't know that recent lintian could take that much time for a full test. Looks like this is a duplicate of https://bugs.debian.org/993613 , so I am closing this bug report. Thanks, Boyuan Yang 在 2022-01-11星期二的 13:41 +0100，Mattia Rizzolo写道： > On Tue, Jan 11, 2022 at 07:29:32AM -0500, Boyuan Yang wrote: > > I just notice that lintian will never finish when checking some specific > > That's not correct. > > > https://mentors.debian.net/package/fcitx5-table-extra/ shows the lintian > > check > > result to be " lintian took too much time to run ". > > I actually never saw lintian *hang*. It just got quite slow. > > Specifically, on mentors.d.n we set a timeout for lintian of 30 minutes. > > We really don't want the whole site to spend hours processing an > incoming packages... > > > Notably, in mentors we don't use `-X cruft` to bypass the slowest > codepath in lintian, that can easily go over the 30 minutes time. > > > I am not 100% sure about the severity, but endless hang could be serious. > > Feel > > free to let me know if you have any questions. > > IMHO, this could just be merged with that other bug (that I'm not > looking up) about the cruft check being slow. > > > Did you try running lintian yourself to actually verify it hangs > somewhere? signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#1003530: lintian: Hangs when checking some .dsc file
Processing control commands: > notfound 1003530 2.114.0 Bug #1003530 [lintian] lintian: Hangs when checking some .dsc file No longer marked as found in versions lintian/2.114.0. > close 1003530 Bug #1003530 [lintian] lintian: Hangs when checking some .dsc file Marked Bug as done -- 1003530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003530 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993033: marked as done (libmcrypt FTBFS: autoreconf failure)
Your message dated Wed, 12 Jan 2022 00:49:06 + with message-id and subject line Bug#993033: fixed in libmcrypt 2.5.8-4 has caused the Debian Bug report #993033, regarding libmcrypt FTBFS: autoreconf 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.) -- 993033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libmcrypt Version: 2.5.8-3.4 Tags: ftbfs Severity: serious libmcrypt fails to build from source, because autoreconf fails. A build ends as follows: |dh_autoreconf | autoreconf: warning: autoconf input should be named 'configure.ac', not 'configure.in' | aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in' | aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in' | acinclude.m4:3740: warning: the serial number must appear before any macro definition | libtoolize: putting auxiliary files in '..'. | libtoolize: copying file '../compile' | libtoolize: copying file '../config.guess' | libtoolize: copying file '../config.sub' | libtoolize: copying file '../depcomp' | libtoolize: copying file '../install-sh' | libtoolize: copying file '../missing' | libtoolize: copying file '../ltmain.sh' | libtoolize: putting macros in 'libltdl/m4'. | libtoolize: copying file 'libltdl/m4/libtool.m4' | libtoolize: You should add the contents of 'libltdl/m4/libtool.m4' to 'aclocal.m4'. | libtoolize: copying file 'libltdl/m4/ltargz.m4' | libtoolize: You should add the contents of 'libltdl/m4/ltargz.m4' to 'aclocal.m4'. | libtoolize: copying file 'libltdl/m4/ltdl.m4' | libtoolize: You should add the contents of 'libltdl/m4/ltdl.m4' to 'aclocal.m4'. | libtoolize: copying file 'libltdl/m4/ltoptions.m4' | libtoolize: You should add the contents of 'libltdl/m4/ltoptions.m4' to 'aclocal.m4'. | libtoolize: copying file 'libltdl/m4/ltsugar.m4' | libtoolize: You should add the contents of 'libltdl/m4/ltsugar.m4' to 'aclocal.m4'. | libtoolize: copying file 'libltdl/m4/ltversion.m4' | libtoolize: You should add the contents of 'libltdl/m4/ltversion.m4' to 'aclocal.m4'. | libtoolize: copying file 'libltdl/m4/lt~obsolete.m4' | libtoolize: You should add the contents of 'libltdl/m4/lt~obsolete.m4' to 'aclocal.m4'. | libtoolize: putting libltdl files in 'libltdl'. | libtoolize: copying file 'libltdl/COPYING.LIB' | libtoolize: creating file 'libltdl/Makefile.am' | libtoolize: copying file 'libltdl/README' | libtoolize: creating file 'libltdl/configure.ac' | libtoolize: creating file 'libltdl/aclocal.m4' | libtoolize: creating file 'libltdl/Makefile.in' | libtoolize: copying file 'libltdl/config-h.in' | libtoolize: creating file 'libltdl/configure' | libtoolize: copying file 'libltdl/libltdl/lt__alloc.h' | libtoolize: copying file 'libltdl/libltdl/lt__argz_.h' | libtoolize: copying file 'libltdl/libltdl/lt__dirent.h' | libtoolize: copying file 'libltdl/libltdl/lt__glibc.h' | libtoolize: copying file 'libltdl/libltdl/lt__private.h' | libtoolize: copying file 'libltdl/libltdl/lt__strl.h' | libtoolize: copying file 'libltdl/libltdl/lt_dlloader.h' | libtoolize: copying file 'libltdl/libltdl/lt_error.h' | libtoolize: copying file 'libltdl/libltdl/lt_system.h' | libtoolize: copying file 'libltdl/libltdl/slist.h' | libtoolize: copying file 'libltdl/loaders/dld_link.c' | libtoolize: copying file 'libltdl/loaders/dlopen.c' | libtoolize: copying file 'libltdl/loaders/dyld.c' | libtoolize: copying file 'libltdl/loaders/load_add_on.c' | libtoolize: copying file 'libltdl/loaders/loadlibrary.c' | libtoolize: copying file 'libltdl/loaders/preopen.c' | libtoolize: copying file 'libltdl/loaders/shl_load.c' | libtoolize: copying file 'libltdl/lt__alloc.c' | libtoolize: copying file 'libltdl/lt__argz.c' | libtoolize: copying file 'libltdl/lt__dirent.c' | libtoolize: copying file 'libltdl/lt__strl.c' | libtoolize: copying file 'libltdl/lt_dlloader.c' | libtoolize: copying file 'libltdl/lt_error.c' | libtoolize: copying file 'libltdl/ltdl.c' | libtoolize: copying file 'libltdl/ltdl.h' | libtoolize: copying file 'libltdl/slist.c' | libtoolize: You should add the contents of the following files to 'aclocal.m4': | libtoolize: '/usr/share/aclocal/libtool.m4' | libtoolize: '/usr/share/aclocal/ltargz.m4' | libtoolize: '/usr/share/aclocal/ltdl.m4' | libtoolize: '/usr/share/aclocal/ltoptions.m4' | libtoolize: '/usr/share/aclocal/ltsugar.m4' | libtoolize: '/usr/share/aclocal/ltversion.m4' | libtoolize: '/usr/share/aclocal/lt~obsolete.m4' | libtoolize: Remember to add
Bug#1003490: u-boot: FTBFS on arch:all with qemu-ppce500 target
On 2022-01-11, Lennart Sorensen wrote:
> On Mon, Jan 10, 2022 at 05:10:04PM -0800, Vagrant Cascadian wrote:
>> Package: u-boot
>> Version: 2022.01+dfsg1-1
>> Severity: serious
>> X-Debbugs-Cc: debian-powe...@lists.debian.org, q...@packages.debian.org,
>> binut...@packages.debian.org
>>
>> 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:
>>
>> powerpc-linux-gnu-gcc -Wp,-MD,arch/powerpc/cpu/mpc85xx/.tlb.o.d -nostdinc
>> -isystem /usr/lib/gcc-cross/powerpc-linux-gnu/11/include -Iinclude
>> -I/<>/include -I/<>/arch/powerpc/include -include
>> /<>/include/linux/kconfig.h
>> -I/<>/arch/powerpc/cpu/mpc85xx -Iarch/powerpc/cpu/mpc85xx
>> -D__KERNEL__ -D__UBOOT__ -Wall -Wstrict-prototypes -Wno-format-security
>> -fno-builtin -ffreestanding -std=gnu11 -fshort-wchar -fno-strict-aliasing
>> -fno-PIE -Os -fno-stack-protector -fno-delete-null-pointer-checks
>> -Wno-pointer-sign -Wno-stringop-truncation -Wno-zero-length-bounds
>> -Wno-array-bounds -Wno-stringop-overflow -Wno-maybe-uninitialized
>> -fmacro-prefix-map=/<>/= -g -fstack-usage
>> -Wno-format-nonliteral -Wno-address-of-packed-member
>> -Wno-unused-but-set-variable -Werror=date-time -Wno-packed-not-aligned
>> -D__powerpc__ -ffixed-r2 -m32 -fno-ira-hoist-pressure -Wa,-me500
>> -msoft-float -mno-string -fpic -mrelocatable -ffunction-sections
>> -fdata-sections -mcall-linux -msingle-pic-base -fno-jump-tables -pipe
>> -DKBUILD_BASENAME='"tlb"' -DKBUILD_MODNAME='"tlb"' -c -o
>> arch/powerpc/cpu/mpc85xx/tlb.o
>> /<>/arch/powerpc/cpu/mpc85xx/tlb.c
>> ...
>> {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!
>>
>>
>> I could remove qemu-ppce500 from the build targets(all other targets
>> build fine); I am not sure if it is used by qemu or if qemu builds all
>> it's own firmwares.
>
> Which gcc version? I believe gcc 9 removed the code for powerpcspe
> which gcc 8 deprecated. So at this point I think only llvm/clang supports
> the powerpcspe targets.
gcc-11 11.2.0-13 in both the successfull (bookworm) and
failing case (sid).
Which is why I suspect binutils, which differs between bookworm and
sid...
> I don't recall if binutils also dropped support or have kept it around.
The binutils versions appear to be:
succeeding, bookworm 2.37-10.1
failing, sid 2.37.50.20220106-2
live well,
vagrant
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 1000571 > https://github.com/phpmyadmin/phpmyadmin/commit/451563c8234b89c4a4f733c977fba2482e295ecd Bug #1000571 [src:phpmyadmin] phpmyadmin: autopkgtest fails with PHP8.1 (in experimental) Set Bug forwarded-to-address to 'https://github.com/phpmyadmin/phpmyadmin/commit/451563c8234b89c4a4f733c977fba2482e295ecd'. > tags 1000571 + fixed pending patch Bug #1000571 [src:phpmyadmin] phpmyadmin: autopkgtest fails with PHP8.1 (in experimental) Added tag(s) fixed, pending, and patch. > stop Stopping processing here. Please contact me if you need assistance. -- 1000571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996263: ctop: Should this package be removed?
Hi, Since there seems to be no solution available, I will submit a RM bug to request package removal. Thanks, Boyuan Yang On Tue, 12 Oct 2021 13:34:13 -0400 Boyuan Yang wrote: > Package: ctop > Severity: serious > Version: 1.0.0-2.1 > X-Debbugs-CC: czc...@debian.org > > Dear Debian ctop package maintainer, > > As discussed in https://bugs.debian.org/922061 , the current ctop software in > Debian is unmaintained, incompatible with Debian 11 and later, and has a dead > upstream. I believe this package should be removed from Debian to avoid > confusion. > > I may submit a package removal request within 1 month if there's no other > opinions. Also please let me know if we should choose other solutions. signature.asc Description: This is a digitally signed message part
Bug#1003490: u-boot: FTBFS on arch:all with qemu-ppce500 target
On Mon, Jan 10, 2022 at 05:10:04PM -0800, Vagrant Cascadian wrote:
> Package: u-boot
> Version: 2022.01+dfsg1-1
> Severity: serious
> X-Debbugs-Cc: debian-powe...@lists.debian.org, q...@packages.debian.org,
> binut...@packages.debian.org
>
> 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:
>
> powerpc-linux-gnu-gcc -Wp,-MD,arch/powerpc/cpu/mpc85xx/.tlb.o.d -nostdinc
> -isystem /usr/lib/gcc-cross/powerpc-linux-gnu/11/include -Iinclude
> -I/<>/include -I/<>/arch/powerpc/include -include
> /<>/include/linux/kconfig.h
> -I/<>/arch/powerpc/cpu/mpc85xx -Iarch/powerpc/cpu/mpc85xx
> -D__KERNEL__ -D__UBOOT__ -Wall -Wstrict-prototypes -Wno-format-security
> -fno-builtin -ffreestanding -std=gnu11 -fshort-wchar -fno-strict-aliasing
> -fno-PIE -Os -fno-stack-protector -fno-delete-null-pointer-checks
> -Wno-pointer-sign -Wno-stringop-truncation -Wno-zero-length-bounds
> -Wno-array-bounds -Wno-stringop-overflow -Wno-maybe-uninitialized
> -fmacro-prefix-map=/<>/= -g -fstack-usage -Wno-format-nonliteral
> -Wno-address-of-packed-member -Wno-unused-but-set-variable -Werror=date-time
> -Wno-packed-not-aligned -D__powerpc__ -ffixed-r2 -m32 -fno-ira-hoist-pressure
> -Wa,-me500 -msoft-float -mno-string -fpic -mrelocatable -ffunction-sections
> -fdata-sections -mcall-linux -msingle-pic-base -fno-jump-tables -pipe
> -DKBUILD_BASENAME='"tlb"' -DKBUILD_MODNAME='"tlb"' -c -o
> arch/powerpc/cpu/mpc85xx/tlb.o /<>/arch/powerpc/cpu/mpc85xx/tlb.c
> ...
> {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!
>
>
> I could remove qemu-ppce500 from the build targets(all other targets
> build fine); I am not sure if it is used by qemu or if qemu builds all
> it's own firmwares.
Which gcc version? I believe gcc 9 removed the code for powerpcspe
which gcc 8 deprecated. So at this point I think only llvm/clang supports
the powerpcspe targets.
I don't recall if binutils also dropped support or have kept it around.
--
Len Sorensen
Bug#1003579: wsl: destroys files/directories named 'temp'
Package: wsl
Version: 0.2.1-2
Severity: grave
hi,
when sourcing /usr/share/wsl/wsl-functions, files or directories named
temp are overwritten or renamed to .wslrun, depending on if it is a file
or directory. Errors are not handled at all...
cat ${MYENV} | grep -v "^#" | sort | uniq >temp
echo "# history ends #" >>temp
/bin/mv temp ${MYENV}
Made my temp folder unhappy. Even if its a file named 'temp', this
should never happen, especially as the created file is sourced later.
. ${MYENV}
Cheers,
Bernd
--
Bernd ZeimetzDebian GNU/Linux Developer
http://bzed.dehttp://www.debian.org
GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
Bug#1002444: python-setuptools: FTBFS: ModuleNotFoundError: No module named 'distutils.command.bdist_wininst'
Control: forwarded -1 https://github.com/pypa/setuptools/pull/1986
Control: tag -1 + patch
Patch attached.
SR
--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272
From: "Jason R. Coombs"
Date: Tue, 11 Jan 2022 18:04:05 -0400
Subject: Fix install_scripts() if bdist_wininst is missing
Bug-Debian: https://bugs.debian.org/1002444
Origin: upstream, https://github.com/pypa/setuptools/pull/1986
---
setuptools/command/install_scripts.py | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/setuptools/command/install_scripts.py b/setuptools/command/install_scripts.py
index 1623427..8c9a15e 100644
--- a/setuptools/command/install_scripts.py
+++ b/setuptools/command/install_scripts.py
@@ -32,8 +32,11 @@ class install_scripts(orig.install_scripts):
)
bs_cmd = self.get_finalized_command('build_scripts')
exec_param = getattr(bs_cmd, 'executable', None)
-bw_cmd = self.get_finalized_command("bdist_wininst")
-is_wininst = getattr(bw_cmd, '_is_running', False)
+try:
+bw_cmd = self.get_finalized_command("bdist_wininst")
+is_wininst = getattr(bw_cmd, '_is_running', False)
+except ImportError:
+is_wininst = False
writer = ei.ScriptWriter
if is_wininst:
exec_param = "python.exe"
Processed: Re: Bug#1002444: python-setuptools: FTBFS: ModuleNotFoundError: No module named 'distutils.command.bdist_wininst'
Processing control commands: > forwarded -1 https://github.com/pypa/setuptools/pull/1986 Bug #1002444 [src:python-setuptools] python-setuptools: FTBFS: ModuleNotFoundError: No module named 'distutils.command.bdist_wininst' Set Bug forwarded-to-address to 'https://github.com/pypa/setuptools/pull/1986'. > tag -1 + patch Bug #1002444 [src:python-setuptools] python-setuptools: FTBFS: ModuleNotFoundError: No module named 'distutils.command.bdist_wininst' Added tag(s) patch. -- 1002444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002444 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003113: python-django: CVE-2021-45115, CVE-2021-45116 & CVE-2021-45452
Am Thu, Jan 06, 2022 at 12:44:03PM - schrieb Chris Lamb: > Hi Security Team, > > I was just looking at these CVEs for ELTS and LTS, but before I make > a move there, I was just wondering if you were planning on (or would > like) a DSA. Hi Chris, these both seem rather harmless to me, I'd say we postpone them until the next round of more serious Django issues? Cheers, Moritz
Bug#1003563: aide: autopkgtest regression: unexpected character: '@' in /etc/aide/aide.conf.d/31_aide_spamassassin
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
Bug#1003562: python-psutil breaks patroni autopkgtest: psutil.Error:
Source: python-psutil, patroni
Control: found -1 python-psutil/5.9.0-1
Control: found -1 patroni/2.1.2-2
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 python-psutil the autopkgtest of patroni fails
in testing when that autopkgtest is run with the binary packages of
python-psutil from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
python-psutil from testing5.9.0-1
patronifrom testing2.1.2-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 python-psutil 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=python-psutil
https://ci.debian.net/data/autopkgtest/testing/armhf/p/patroni/18228177/log.gz
=== FAILURES
===
TestCancellableSubprocess.test_cancel
_
self = 0xf4587850>
def _kill_process(self):
with self._lock:
if self._process is not None and self._process.is_running()
and not self._process_children:
try:
self._process.suspend() # Suspend the process before getting
list of children
patroni/postgresql/cancellable.py:39: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_mock_self = , args = (),
kwargs = {}
def __call__(_mock_self, *args, **kwargs):
# can't use self in-case a function / method we are mocking
uses self
# in the signature
_mock_self._mock_check_sig(*args, **kwargs)
_mock_self._increment_mock_call(*args, **kwargs)
return _mock_self._mock_call(*args, **kwargs)
/usr/lib/python3/dist-packages/mock/mock.py:1100: _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_mock_self = , args = (),
kwargs = {}
def _mock_call(_mock_self, *args, **kwargs):
return _mock_self._execute_mock_call(*args, **kwargs)
/usr/lib/python3/dist-packages/mock/mock.py:1104: _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_mock_self = , args = (),
kwargs = {}
self = , effect = psutil.Error()
def _execute_mock_call(_mock_self, *args, **kwargs):
self = _mock_self
# separate from _increment_mock_call so that awaited functions are
# executed separately from their call, also AsyncMock overrides
this method
effect = self.side_effect
if effect is not None:
if _is_exception(effect):
raise effect
E psutil.Error:
/usr/lib/python3/dist-packages/mock/mock.py:1161: Error
During handling of the above exception, another exception occurred:
self = testMethod=test_cancel>
@patch('patroni.postgresql.cancellable.polling_loop',
Mock(return_value=[0, 0]))
def test_cancel(self):
self.c._process = Mock()
self.c._process.is_running.return_value = True
self.c._process.children.side_effect = psutil.Error()
self.c._process.suspend.side_effect = psutil.Error()
self.c.cancel()
tests/test_cancellable.py:32: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
patroni/postgresql/cancellable.py:133: in cancel
self._kill_process()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
self = 0xf4587850>
def _kill_process(self):
with self._lock:
if self._process is not None and self._process.is_running()
and not self._process_children:
try:
self._process.suspend() # Suspend the process
before getting list of children
except psutil.Error as e:
logger.info('Failed to suspend the process: %s', e.msg)
E AttributeError: 'Error' object has no attribute 'msg'
patroni/postgresql/cancellable.py:41: AttributeError
TestPostmasterProcess.test_signal_kill
self = <[AttributeError("'PostmasterProcess' object has no attribute
'_pid'") raised in repr()] PostmasterProcess object at 0xef4bc598>
def signal_kill(self):
"""to suspend and kill postmaster and all children
:returns True if postmaster and children are killed, False
if error
"""
try:
self.suspend()
patroni/postgresql/postmaster.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _
Processed: python-psutil breaks patroni autopkgtest: psutil.Error:
Processing control commands: > found -1 python-psutil/5.9.0-1 Bug #1003562 [src:python-psutil, src:patroni] python-psutil breaks patroni autopkgtest: psutil.Error: Marked as found in versions python-psutil/5.9.0-1. > found -1 patroni/2.1.2-2 Bug #1003562 [src:python-psutil, src:patroni] python-psutil breaks patroni autopkgtest: psutil.Error: Marked as found in versions patroni/2.1.2-2. -- 1003562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003561: mypy breaks python-sop autopkgtest: Missing type parameters for generic type "_SubParsersAction"
Source: mypy, python-sop Control: found -1 mypy/0.931-1 Control: found -1 python-sop/0.2.0-1.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 mypy the autopkgtest of python-sop fails in testing when that autopkgtest is run with the binary packages of mypy from unstable. It passes when run with only packages from testing. In tabular form: passfail mypy from testing0.931-1 python-sop from testing0.2.0-1.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 mypy 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=mypy https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-sop/18224287/log.gz sop/__init__.py:224: error: Missing type parameters for generic type "_SubParsersAction" sop/__init__.py:387: error: Missing type parameters for generic type "_SubParsersAction" Found 2 errors in 1 file (checked 3 source files) autopkgtest [21:22:47]: test command2 OpenPGP_signature Description: OpenPGP digital signature
Processed: mypy breaks python-sop autopkgtest: Missing type parameters for generic type "_SubParsersAction"
Processing control commands: > found -1 mypy/0.931-1 Bug #1003561 [src:mypy, src:python-sop] mypy breaks python-sop autopkgtest: Missing type parameters for generic type "_SubParsersAction" Marked as found in versions mypy/0.931-1. > found -1 python-sop/0.2.0-1.1 Bug #1003561 [src:mypy, src:python-sop] mypy breaks python-sop autopkgtest: Missing type parameters for generic type "_SubParsersAction" Marked as found in versions python-sop/0.2.0-1.1. -- 1003561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001591: [Pkg-matrix-maintainers] Bug#1002380: drops attributes used by reverse dependencies
Pierre-Elliott Bécue wrote on 09/01/2022 at 13:11:41+0100: > [[PGP Signed Part:Good signature from 29BFA0D079290ACA Pierre-Elliott Bécue > (trust ultimate) created at 2022-01-09T13:14:08+0100 using > RSA]] > > Sandro Tosi wrote on 09/01/2022 at 03:38:18+0100: > >>> I am eager to revert mistune (and therefore django-hyperkitty) back to >>> previous versions, and to open bugs against reverse deps, with new >>> uploads in experimental for both mistune and django-hyperkitty. >> >> this would be great indeed, thanks! >> >>> I consider a delay between bug opening and making them RC on the >>> reverse-deps of a month, which, added to the removal delay, means around >>> mid-march I'll probably reupload mistune 2.0.0 and django-hyperkitty in >>> unstable. >> >> from what i have seen, many of the downstream projects developers were >> rather surprised by the sudden release of a mistune 2.0 version, and >> they were uncertain how to move forward in a proper way, given the >> vast number of differences and incompatible changes. > > Well, having participated to writing some documentation, I am not sure > that this number of differences is that vast. Mistune, on itself, was > not that big a project in terms of features, and getting a grip on the > new version should not take that much time. > >> There also seems to be a complete lack of guidance from mistune >> upstream on how to port projects from 0.8.x to 2.x: do you think any >> effort will be spent by mistune upstream to provide any such >> documentation? without it, i'm afraid 1 month is not enough >> (anecdotally, the 2.x upload in unstable was a little more than a >> month ago, and i dont think any upstream project mas ported to it, so >> that should provide some guidance on how long to wait to make it RC) > > Okay, lets go with 3 months from Jan the 15th so April the 15th. If > things seem to go faster than expected I will maybe contract that > schedule. (let's say if two thirds of the deps are up-to-date upstream > on March the 1st I'll come back to the initial schedule) > > Would that make sense for you? > >>> Last but not least, do you have appropriate tooling to file bugs against >>> mistune reverse deps a bit more efficiently than "mail by mail"? >> >> `mass-bug` from devscripts > > Ah right, I never used it, it's about time. :) > > Thanks! Done, I'll mass-bug this evening. I plan to reupload immediately 2.0.0 in experimental. This means no further upload of mistune 0.8.4 are possible in unstable. Is this okay with both of you? Cheers! -- PEB
Bug#1001591: [Pkg-matrix-maintainers] Bug#1002380: drops attributes used by reverse dependencies
> I plan to reupload immediately 2.0.0 in experimental. This means no > further upload of mistune 0.8.4 are possible in unstable. Is this okay > with both of you? you're the maintainer, bugs can happen, so it has to be fine for you on how to handle a situation where an upload of mistune 0.8.4 is absolutely needed and you have to take care of it. -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#999132: marked as done (uqm: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Tue, 11 Jan 2022 20:56:59 + with message-id and subject line Bug#999132: fixed in uqm 0.6.2.dfsg-9.6 has caused the Debian Bug report #999132, regarding uqm: missing required debian/rules targets build-arch and/or build-indep 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.) -- 999132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999132 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: uqm Version: 0.6.2.dfsg-9.5 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: uqm Source-Version: 0.6.2.dfsg-9.6 Done: Stephen Kitt We believe that the bug you reported is fixed in the latest version of uqm, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen Kitt (supplier of updated uqm 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: Tue, 11 Jan 2022 20:57:14 +0100 Source: uqm Architecture: source Version: 0.6.2.dfsg-9.6 Distribution: unstable Urgency: medium Maintainer: Dmitry E. Oboukhov Changed-By: Stephen Kitt Closes: 999132 Changes: uqm (0.6.2.dfsg-9.6) unstable; urgency=medium . [ Matija Nalis ] * Non-maintainer upload. * Update the VCS URIs to point to Salsa. * Update debian/watch to track the latest releases. * Switch to debhelper compatibility level 13, using dh. Closes: #999132. * Re-enable PIE, the workaround for #843979 is no longer needed. Checksums-Sha1: f97301077a482bd6eff0a83d69daaadda4d0c612 1929 uqm_0.6.2.dfsg-9.6.dsc b62cbae609d66db50462371e8109d5102d59951d 29508 uqm_0.6.2.dfsg-9.6.debian.tar.xz aab0b9742ca246aeaee87a2ad8a068629001e89e 10771 uqm_0.6.2.dfsg-9.6_source.buildinfo Checksums-Sha256: 1a37cdaba48d675d35ffd825ea25e15f6330462942e78ea0fd9455654afafdc8 1929 uqm_0.6.2.dfsg-9.6.dsc a0a4493255cfba8f2353c1da51625e3a9ed1241180d19c92d02203f5399bae12 29508 uqm_0.6.2.dfsg-9.6.debian.tar.xz 5c699d27502a9c05869f1e6bc0f9cf9a56527a9cd9bb3f1a07229c466bad5bcb 10771 uqm_0.6.2.dfsg-9.6_source.buildinfo Files: 321f1ba839d2c57cf86dd4621285f112 1929 contrib/games optional uqm_0.6.2.dfsg-9.6.dsc 026bd103409925c7b3aa73a81b9379c2 29508 contrib/games optional uqm_0.6.2.dfsg-9.6.debian.tar.xz f22bc1d339a9c45a6d990e8b54f7d9a0 10771 contrib/games optional uqm_0.6.2.dfsg-9.6_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmHd4a8ACgkQgNMC9Yht g5z9/Q/9Ew5clASPqE1HJHLaG74LpbTMS09r2FlZUGWhGnxGBGc5RKnR9dn5SQcM 6Ytemsh9KfNGb6rxfnFV+mLnbt+Wgr9yxN6j06fzsJ08yJ0ddOj1BZQQJDRA/7Q3 oJTN4nWsMjekJbseD0ez+fKgkNZAAWZ7TIcDHdLX094CuT5tHzsZJF2o2455tQZU ZtqP0Rdn1h44pmAHK5vZbOYyKzXx/Tvwg84g/rKhw9O10l6NZvNMoGktDXZG9+4E 5qTGB8knYirdRLc5b2ljWvp20cBSVvwlvRLYbhGP/ckP0rzUWSVdoA9pKAvh9bBW BGvOoGNEq9N6RZXuVljlJNqLEggEN/C3OIK3VF6DnmIpx8cJLfrjOcN5jA5cakpQ +QHxUXWu0WxRgTTJBDOYeB9rv+WyAR/XsXSEYJY7Bmlv6ksEPvTnCbfshIV7iotd U130f3NwxImv4HQbmUJdTCD1syLdYNUuB8OdsVvg3m3RymxN6FKEw92DJESeL3hp EBmqzwDaT/bcKLXFLKWNPoNBrjGxj2WV4cg/Vl0emZaW1M97NJ9P+ImAllx3RKHR N8AY47Veu/lS4/ridRz5HxmwYIIOicKMFULeZc1AMjTkEQkZJVMdFevJ8C17UePE 6xJFiEijgfI2ld5WQ7F/dHwxhcjGzwU1cgtbm+6kZoho/SrR+PU= =PDDc -END PGP SIGNATURE End Message ---
Bug#998485: marked as done (gjiten: FTBFS: configure.in:8: error: AM_INIT_AUTOMAKE expanded multiple times)
Your message dated Tue, 11 Jan 2022 20:48:51 + with message-id and subject line Bug#998485: fixed in gjiten 3.1-1 has caused the Debian Bug report #998485, regarding gjiten: FTBFS: configure.in:8: error: AM_INIT_AUTOMAKE expanded multiple times 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.) -- 998485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998485 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gjiten Version: 2.6-3.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build >dh_update_autotools_config >dh_autoreconf > autoreconf: warning: autoconf input should be named 'configure.ac', not > 'configure.in' > aclocal: warning: autoconf input should be named 'configure.ac', not > 'configure.in' > configure.in:8: error: AM_INIT_AUTOMAKE expanded multiple times > /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... > configure.in:7: the top level > /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... > configure.in:8: the top level > autom4te: error: /usr/bin/m4 failed with exit status: 1 > aclocal: error: /usr/bin/autom4te failed with exit status: 1 > autoreconf: error: aclocal failed with exit status: 1 > dh_autoreconf: error: autoreconf -f -i returned exit code 1 > make: *** [debian/rules:4: build] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/gjiten_2.6-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: gjiten Source-Version: 3.1-1 Done: Ludovic Drolez We believe that the bug you reported is fixed in the latest version of gjiten, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ludovic Drolez (supplier of updated gjiten package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 10 Jan 2022 19:38:40 +0100 Source: gjiten Architecture: source Version: 3.1-1 Distribution: unstable Urgency: medium Maintainer: Botond Botyanszki Changed-By: Ludovic Drolez Closes: 998485 Changes: gjiten (3.1-1) unstable; urgency=medium . * New upstream release. * Updated the watch file * Most patches dropped, will see if the new upstream maintainer will integrate them. * FTBFS fixed with new release. Closes: #998485 Checksums-Sha1: a63be9216dc24f3f3015984f5ed851e9fefb349c 1468 gjiten_3.1-1.dsc fc9e6eb656d33589a494c05252649acbeeb3522b 922726 gjiten_3.1.orig.tar.gz 06cf0f23b3e4e78da633b568217b033b48663750 25348 gjiten_3.1-1.debian.tar.xz 4fed100ae5704578350ee4f4a1b69d248ad7d907 16814 gjiten_3.1-1_amd64.buildinfo Checksums-Sha256: 0e6037a76828e7a47ae9a7cd410289976383cd63353de464d4afb301963d9545 1468 gjiten_3.1-1.dsc 3e2d2dff4a42e700086cec1ea6d295746df13d019fff02f12a5f1b6b9e6d1e98 922726 gjiten_3.1.orig.tar.gz a95d7363a5a3e48fce7c6cf4faeb683409e9adf791eacf6fe1c9aca0a2926c05 25348 gjiten_3.1-1.debian.tar.xz d6854221e0e5600ecb98c884a2d1fcaeb3e3940df657399a34b80f70f21a5203 16814 gjiten_3.1-1_amd64.buildinfo Files: 598c09f53b1cd33ee2b276d6b3ef6683 1468 gnome optional gjiten_3.1-1.dsc d2b6c1f805b4016f6b616c50a4b81db1 922726 gnome optional gjiten_3.1.orig.tar.gz 460433e0cc4d84fc4ad33d9bcba49362 25348 gnome optional gjiten_3.1-1.debian.tar.xz 019902d31bb6d5ffc27ae17eab82a3b7 16814 gnome optional gjiten_3.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQFHBAEBCAAxFiEEKrWNbKjxjlSqtxlZi3UoEkf5wXwFAmHd59kTHGxkcm9sZXpA
Processed: konwert: diff for NMU version 1.8-13.2
Processing control commands: > tags 965613 + patch Bug #965613 [src:konwert] konwert: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965613 + pending Bug #965613 [src:konwert] konwert: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending. -- 965613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965613: konwert: diff for NMU version 1.8-13.2
Control: tags 965613 + patch Control: tags 965613 + pending Dear maintainer, I've prepared an NMU for konwert (versioned as 1.8-13.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer or speed it up. Regards, dam diff -Nru konwert-1.8/debian/changelog konwert-1.8/debian/changelog --- konwert-1.8/debian/changelog 2020-12-27 17:28:47.0 +0200 +++ konwert-1.8/debian/changelog 2022-01-11 22:13:21.0 +0200 @@ -1,3 +1,11 @@ +konwert (1.8-13.2) unstable; urgency=medium + + * Non-maintainer upload. + * Bump debhelper compatibility level from 5 to 7 +Closes: 965613 - removal of compatibility levels 5 and 6 + + -- Damyan Ivanov Tue, 11 Jan 2022 20:13:21 + + konwert (1.8-13.1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. diff -Nru konwert-1.8/debian/compat konwert-1.8/debian/compat --- konwert-1.8/debian/compat 2014-06-23 00:00:29.0 +0300 +++ konwert-1.8/debian/compat 2022-01-11 22:10:09.0 +0200 @@ -1 +1 @@ -5 +7 diff -Nru konwert-1.8/debian/control konwert-1.8/debian/control --- konwert-1.8/debian/control 2016-08-15 12:03:45.0 +0300 +++ konwert-1.8/debian/control 2022-01-11 22:12:22.0 +0200 @@ -5,7 +5,7 @@ Standards-Version: 3.6.2 Vcs-Git: git://anonscm.debian.org/collab-maint/konwert.git Vcs-Browser: http://anonscm.debian.org/cgit/collab-maint/konwert.git -Build-Depends: debhelper (>> 5), dh-buildinfo, bash-completion +Build-Depends: debhelper (>= 7), dh-buildinfo, bash-completion Package: konwert Architecture: any
Processed: Bug#1003150 marked as pending in wheel
Processing control commands: > tag -1 pending Bug #1003150 [python3-wheel] python3-wheel: Missing depends on python3-distutils Added tag(s) pending. -- 1003150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003150 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003150: marked as pending in wheel
Control: tag -1 pending Hello, Bug #1003150 in wheel reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/wheel/-/commit/db75d127f6006dc64b6c3ef687fde7fe38c45913 Explicitly depend on python3-distutils (Closes: #1003150) (this message was generated automatically) -- Greetings https://bugs.debian.org/1003150
Bug#1002533: marked as pending in wheel
Control: tag -1 pending Hello, Bug #1002533 in wheel reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/wheel/-/commit/1e3a9e82b8cc311cf44b640703ed47a85262a244 Mark existing autopkgtests as allow-stderr, due to deprecation warning emitted by newer setuptools. (Closes: #1002533) (this message was generated automatically) -- Greetings https://bugs.debian.org/1002533
Processed: Bug#1002533 marked as pending in wheel
Processing control commands: > tag -1 pending Bug #1002533 [src:wheel] wheel: autopkgtest needs update for new version of setuptools: deprecation warning on stderr Added tag(s) pending. -- 1002533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984013: marked as done (chromium: ftbfs with GCC-11)
Your message dated Tue, 11 Jan 2022 14:26:18 -0500 with message-id <8e4bdc1e-84b9-c880-1c48-51a5ab30f...@queued.net> and subject line Re: chromium: ftbfs with GCC-11 has caused the Debian Bug report #984013, regarding chromium: ftbfs with GCC-11 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.) -- 984013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984013 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:chromium Version: 88.0.4324.182-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/chromium_88.0.4324.182-1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] [6063/44184] CXX obj/third_party/perfetto/src/trace_processor/containers/containers/nullable_vector.o [6064/44184] STAMP obj/third_party/devtools-frontend/src/front_end/ui/devtools_entrypoint-bundle-typescript.stamp [6065/44184] CXX obj/third_party/perfetto/src/trace_processor/importers/memory_tracker/graph_processor/raw_memory_graph_node.o [6066/44184] CXX obj/third_party/perfetto/src/protozero/protoc_plugin/cppgen_plugin/cppgen_plugin.o [6067/44184] CXX obj/third_party/perfetto/src/protozero/protoc_plugin/protozero_plugin/protozero_plugin.o [6068/44184] CXX obj/third_party/perfetto/src/trace_processor/importers/memory_tracker/graph_processor/graph_processor.o [6069/44184] ACTION //third_party/devtools-frontend/src/front_end/bindings:devtools_entrypoint-bundle-rollup(//build/toolchain/linux/unbundle:default) [6070/44184] STAMP obj/third_party/devtools-frontend/src/front_end/bindings/devtools_entrypoint-bundle-rollup.stamp [6071/44184] ACTION //third_party/devtools-frontend/src/front_end/ui:devtools_entrypoint-bundle(//build/toolchain/linux/unbundle:default) [6072/44184] ACTION //third_party/devtools-frontend/src/front_end/bindings:devtools_entrypoint-bundle-typescript(//build/toolchain/linux/unbundle:default) [6073/44184] STAMP obj/third_party/devtools-frontend/src/front_end/bindings/devtools_entrypoint-bundle-typescript.stamp [6074/44184] STAMP obj/third_party/devtools-frontend/src/front_end/ui/devtools_entrypoint-bundle.stamp [6075/44184] COPY gen/third_party/devtools-frontend/src/front_end/ui/ui.js resources/inspector/ui/ui.js [6076/44184] STAMP obj/third_party/devtools-frontend/src/front_end/ui/bundle-copy.stamp [6077/44184] STAMP obj/third_party/devtools-frontend/src/front_end/ui/bundle.stamp [6078/44184] CXX obj/third_party/perfetto/src/trace_processor/importers/memory_tracker/graph_processor/graph.o [6079/44184] CXX obj/third_party/perfetto/src/trace_processor/db/lib/table.o [6080/44184] CXX obj/third_party/perfetto/src/trace_processor/containers/containers/row_map.o [6081/44184] CXX obj/third_party/perfetto/src/trace_processor/importers/memory_tracker/graph_processor/memory_allocator_node_id.o [6082/44184] CXX obj/third_party/perfetto/src/trace_processor/containers/containers/string_pool.o FAILED: obj/third_party/perfetto/src/trace_processor/containers/containers/string_pool.o clang++ -MMD -MF obj/third_party/perfetto/src/trace_processor/containers/containers/string_pool.o.d -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1
Bug#1000593: marked as done (php-console-commandline: Failing testsuite with PHP 8.1)
Your message dated Tue, 11 Jan 2022 19:05:32 + with message-id and subject line Bug#1000593: fixed in php-console-commandline 1.2.4-1 has caused the Debian Bug report #1000593, regarding php-console-commandline: Failing testsuite with PHP 8.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.) -- 1000593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000593 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: php-console-commandline Version: 1.2.1-1 Severity: normal Control: block 976811 by -1 Hi, The testsuite is currently failing with PHP 8: FAIL [ 2/53] Test for Console_CommandLine::addArgument() method.[Console_CommandLine-1.2.1/tests/console_commandline_addargument.phpt] […] FAIL [ 6/53] Test for Console_CommandLine::addCommand() method.[Console_CommandLine-1.2.1/tests/console_commandline_addcommand_3.phpt] FAIL [ 7/53] Test for Console_CommandLine::addOption() method.[Console_CommandLine-1.2.1/tests/console_commandline_addoption.phpt] There is a new upstream version (1.2.4), but I quickly checked that two failures (first and last) still happen. (It’s also not a PEAR package anymore, so need some work to convert the packaging to its Composer source). signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: php-console-commandline Source-Version: 1.2.4-1 Done: Guilhem Moulin We believe that the bug you reported is fixed in the latest version of php-console-commandline, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guilhem Moulin (supplier of updated php-console-commandline 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: Tue, 11 Jan 2022 19:46:03 +0100 Source: php-console-commandline Architecture: source Version: 1.2.4-1 Distribution: unstable Urgency: medium Maintainer: Debian PHP PEAR Maintainers Changed-By: Guilhem Moulin Closes: 1000593 Changes: php-console-commandline (1.2.4-1) unstable; urgency=medium . * New upstream version 1.2.4. * Add self to Uploaders. * Trim trailing whitespace. * Use secure copyright file specification URI. * Update watch file format version to 4. * Use secure URI in Homepage field. * Bump debhelper from deprecated 9 to 13. * Set debhelper-compat version in Build-Depends. * Update Vcs-* headers to use salsa repository. * Set Rules-Requires-Root: no. * Use secure URI in d/copyright. * Remove check for DEB_BUILD_OPTIONS=nocheck in override_dh_auto_test. * Bump Standards-Version to 4.5.1 from ancient 3.9.7. * Add d/gbp.conf. * Point d/watch to GitHub. * Add d/salsa-ci.yml file for GitLab CI. * Adapt d/rules and d/control to use composer. * Override false positive lintian tag 'repeated-path-segment'. * Adjust d/copyright. * Fix FTBFS with PHP8.1. (Closes: #1000593) * Avoid deprecation messages under PHP8.1. * d/control: Skip Build-Depends: php-cgi under 'nocheck' profile. * d/control: Build-Depends on a recent enough PHP for the test suite. Checksums-Sha1: 699f3b5ed076b6879c91d886c89a4cfd2c39dc9b 2242 php-console-commandline_1.2.4-1.dsc 1249a0ee5b8b59d8abe39004294ce0b3f3012087 36195 php-console-commandline_1.2.4.orig.tar.gz c5f2a674a304dc463e09604878d8d48ad561f35e 4860 php-console-commandline_1.2.4-1.debian.tar.xz 276e47b00e373b4b313fcdb52f2117d9c02c9393 6507 php-console-commandline_1.2.4-1_amd64.buildinfo Checksums-Sha256: 69186ef2ff8678f79202336433fd011e3d805b029d62536be629e87c9c029817 2242 php-console-commandline_1.2.4-1.dsc 54afcb88f02d7184c10d7f318904eced00712f4d066f0981e6b0d13d96ae6d1e 36195 php-console-commandline_1.2.4.orig.tar.gz 6c03215d96f93bc8d96378a45f0036cdb75b7420455e681218dc1bc03ec6e18c 4860 php-console-commandline_1.2.4-1.debian.tar.xz 44c9fec59456538d62287156bcdf677ba87dfe887da3969c48b07ee4511d6ac6 6507 php-console-commandline_1.2.4-1_amd64.buildinfo Files: 9085ee41df35e97ab350b8747b55a295 2242 php optional php-console-commandline_1.2.4-1.dsc 51c37fe192638febf35c2f81548564dd 36195 php optional php-console-commandline_1.2.4.orig.tar.gz
Bug#997710: marked as done (erlang-erlware-commons: FTBFS: src/ec_cmd_log.erl:160:5: ambiguous call of overridden auto-imported BIF error/3)
Your message dated Tue, 11 Jan 2022 19:00:10 +
with message-id
and subject line Bug#997710: fixed in erlang-erlware-commons 1.6.0+dfsg-1
has caused the Debian Bug report #997710,
regarding erlang-erlware-commons: FTBFS: src/ec_cmd_log.erl:160:5: ambiguous
call of overridden auto-imported BIF error/3
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.)
--
997710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-erlware-commons
Version: 1.3.1+dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --buildsystem=rebar --with rebar
>dh_update_autotools_config -O--buildsystem=rebar
>dh_autoreconf -O--buildsystem=rebar
>dh_auto_configure -O--buildsystem=rebar
> make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile
> configure
> make[1]: Nothing to be done for 'configure'.
>dh_auto_build -O--buildsystem=rebar
> make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile
> build
> rebar_compile
> rebar compile skip_deps=true -vv
> DEBUG: Evaluating config script "/<>/rebar.config.script"
> DEBUG: Consult config file "/<>/rebar.config"
> DEBUG: Rebar location: "/usr/bin/rebar"
> DEBUG: Consult config file "/<>/src/erlware_commons.app.src"
> DEBUG: Available deps: []
> DEBUG: Missing deps : []
> DEBUG: Plugins requested while processing /<>: []
> DEBUG: Predirs: []
> ==> erlang-erlware-commons-1.3.1+dfsg (compile)
> DEBUG: Matched required ERTS version: 12.1.1 -> .*
> DEBUG: Matched required OTP release: 24 -> .*
> DEBUG: Min OTP version unconfigured
> DEBUG: erl_opts [debug_info,
> {d,namespaced_types},
> {d,have_callback_support},
> {d,rand_module},
> {d,unicode_str},
> debug_info,warnings_as_errors]
> DEBUG: Files to compile first: ["src/ec_vsn.erl","src/ec_dictionary.erl"]
> Compiled src/ec_vsn.erl
> Compiled src/ec_dictionary.erl
> DEBUG: Starting 3 compile worker(s)
> Compiled src/ec_dict.erl
> Compiled src/ec_orddict.erl
> Compiled src/ec_git_vsn.erl
> src/ec_cmd_log.erl:160:5: ambiguous call of overridden auto-imported BIF
> error/3
> - use erlang:error/3 or "-compile({no_auto_import,[error/3]})." to resolve
> name clash
> Compiling src/ec_cmd_log.erl failed:
> DEBUG: Worker compilation failed: {{error,
> {error,[],
> [["src/ec_cmd_log.erl:160:5: ambiguous
> call of overridden auto-imported BIF error/3\n - use erlang:error/3 or
> \"-compile({no_auto_import,[error/3]}).\" to resolve name clash\n"]]}},
>{source,"src/ec_cmd_log.erl"}}
> ERROR: compile failed while processing /<>: rebar_abort
> make[1]: *** [/usr/share/dh-rebar/make/dh-rebar.Makefile:126: rebar_compile]
> Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/erlang-erlware-commons_1.3.1+dfsg-2_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: erlang-erlware-commons
Source-Version: 1.6.0+dfsg-1
Done: Nobuhiro Iwamatsu
We believe that the bug you reported is fixed in the latest version of
erlang-erlware-commons, 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 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu (supplier of updated
erlang-erlware-commons 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:
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org: > reassign 1003547 src:libvigraimpex Bug #1003547 [hugin] hugin: Hugun begins to block for a great number of packages Bug reassigned from package 'hugin' to 'src:libvigraimpex'. No longer marked as found in versions hugin/2021.0~beta1+dfsg-1. Ignoring request to alter fixed versions of bug #1003547 to the same values previously set > forcemerge 984049 1003547 Bug #984049 [src:libvigraimpex] enblend-enfuse: ftbfs with GCC-11 Bug #984213 [src:libvigraimpex] libvigraimpex: ftbfs with GCC-11 Bug #1003549 [src:libvigraimpex] enblend blocks for a number of packages Bug #1003550 [src:libvigraimpex] enfuse blocks for a great number of packages Bug #1003547 [src:libvigraimpex] hugin: Hugun begins to block for a great number of packages Set Bug forwarded-to-address to 'https://github.com/ukoethe/vigra/issues/491'. Severity set to 'serious' from 'important' Added indication that 1003547 affects enfuse,enblend,src:enblend-enfuse Marked as found in versions libvigraimpex/1.11.1+dfsg-8. Added tag(s) bookworm, help, sid, and ftbfs. Bug #984213 [src:libvigraimpex] libvigraimpex: ftbfs with GCC-11 Removed indication that 984213 affects enblend, enfuse, and src:enblend-enfuse Added indication that 984213 affects enfuse,enblend,src:enblend-enfuse Removed indication that 984049 affects enblend, src:enblend-enfuse, and enfuse Added indication that 984049 affects enfuse,enblend,src:enblend-enfuse Removed indication that 1003549 affects enblend, src:enblend-enfuse, and enfuse Added indication that 1003549 affects enfuse,enblend,src:enblend-enfuse Removed indication that 1003550 affects enfuse, src:enblend-enfuse, and enblend Added indication that 1003550 affects enfuse,enblend,src:enblend-enfuse Bug #1003549 [src:libvigraimpex] enblend blocks for a number of packages Bug #1003550 [src:libvigraimpex] enfuse blocks for a great number of packages Merged 984049 984213 1003547 1003549 1003550 > affects 984049 hugin Bug #984049 [src:libvigraimpex] enblend-enfuse: ftbfs with GCC-11 Bug #984213 [src:libvigraimpex] libvigraimpex: ftbfs with GCC-11 Bug #1003547 [src:libvigraimpex] hugin: Hugun begins to block for a great number of packages Bug #1003549 [src:libvigraimpex] enblend blocks for a number of packages Bug #1003550 [src:libvigraimpex] enfuse blocks for a great number of packages Added indication that 984049 affects hugin Added indication that 984213 affects hugin Added indication that 1003547 affects hugin Added indication that 1003549 affects hugin Added indication that 1003550 affects hugin > thanks Stopping processing here. Please contact me if you need assistance. -- 1003547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003547 1003549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003549 1003550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003550 984049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984049 984213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org: > reassign 1003549 src:libvigraimpex Bug #1003549 [enblend] enblend blocks for a number of packages Bug reassigned from package 'enblend' to 'src:libvigraimpex'. No longer marked as found in versions enblend-enfuse/4.2-8. Ignoring request to alter fixed versions of bug #1003549 to the same values previously set > reassign 1003550 src:libvigraimpex Bug #1003550 [enfuse] enfuse blocks for a great number of packages Bug reassigned from package 'enfuse' to 'src:libvigraimpex'. No longer marked as found in versions enblend-enfuse/4.2-8. Ignoring request to alter fixed versions of bug #1003550 to the same values previously set > forcemerge 984049 1003549 1003550 Bug #984049 [src:libvigraimpex] enblend-enfuse: ftbfs with GCC-11 Bug #984213 [src:libvigraimpex] libvigraimpex: ftbfs with GCC-11 Bug #1003550 [src:libvigraimpex] enfuse blocks for a great number of packages Set Bug forwarded-to-address to 'https://github.com/ukoethe/vigra/issues/491'. Severity set to 'serious' from 'important' Added indication that 1003550 affects src:enblend-enfuse Marked as found in versions libvigraimpex/1.11.1+dfsg-8. Added tag(s) sid, bookworm, help, and ftbfs. Bug #1003549 [src:libvigraimpex] enblend blocks for a number of packages Set Bug forwarded-to-address to 'https://github.com/ukoethe/vigra/issues/491'. Severity set to 'serious' from 'important' Added indication that 1003549 affects src:enblend-enfuse Marked as found in versions libvigraimpex/1.11.1+dfsg-8. Added tag(s) help, bookworm, ftbfs, and sid. Bug #984213 [src:libvigraimpex] libvigraimpex: ftbfs with GCC-11 Merged 984049 984213 1003549 1003550 > affects 984049 enblend enfuse Bug #984049 [src:libvigraimpex] enblend-enfuse: ftbfs with GCC-11 Bug #984213 [src:libvigraimpex] libvigraimpex: ftbfs with GCC-11 Bug #1003549 [src:libvigraimpex] enblend blocks for a number of packages Bug #1003550 [src:libvigraimpex] enfuse blocks for a great number of packages Added indication that 984049 affects enblend and enfuse Added indication that 984213 affects enblend and enfuse Added indication that 1003549 affects enblend and enfuse Added indication that 1003550 affects enblend and enfuse > thanks Stopping processing here. Please contact me if you need assistance. -- 1003549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003549 1003550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003550 984049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984049 984213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996048: [Pkg-openssl-devel] Bug#996048: postfix-mta-sts-resolver: autopkgtest doesn't handle new version of ca-certificates nicely: rehash: warning: skipping ca-certificates.crt, it does not conta
Control: reassign -1 postfix-mta-sts-resolver On Mon, Nov 08, 2021 at 03:57:00PM +0200, Adrian Bunk wrote: > On Tue, Oct 19, 2021 at 09:13:56AM +0200, Julien Cristau wrote: > > On Mon, Oct 18, 2021 at 11:05:14PM +0200, Kurt Roeckx wrote: > > > On Mon, Oct 18, 2021 at 10:40:59PM +0200, Julien Cristau wrote: > > > > On Mon, Oct 18, 2021 at 02:50:50PM +0200, Benjamin Hof wrote: > > > > > Hi, > > > > > > > > > > I think the following change might be the relevant one: > > > > > > > > > > --- a/update-ca-certificates > > > > > +++ b/update-ca-certificates > > > > > @@ -164,8 +164,6 @@ > > > > >done > > > > > fi > > > > > > > > > > -rm -f "$CERTBUNDLE" > > > > > - > > > > > ADDED_CNT=$(wc -l < "$ADDED") > > > > > REMOVED_CNT=$(wc -l < "$REMOVED") > > > > > > > > > > It triggers this stderr output during openssl rehash (l. 184): > > > > > > > > > > rehash: warning: skipping ca-certificates.crt,it does not contain > > > > > exactly one certificate or CRL > > > > > > > > > Ah, that makes sense. Annoying... > > > > > > > > Kurt/Sebastian, do you think there's a chance openssl rehash could grow > > > > some sort of ignore option so update-ca-certificates could ask it to > > > > skip ca-certificates.crt, to avoid spitting out a warning for it? > > > > > > As in rehash all files in that directory, excluding a file? I > > > guess that's an option. I guess it's not an option to move the > > > file to a different location. > > > > > Exactly. /etc/ssl/certs/ca-certificates.crt is the package's main > > "interface" so I suspect it'd be quite painful to move. Likewise moving > > the certs and hash symlinks themselves would break packages/scripts > > looking them up that way. > > > > The other option for me would be to revert the fix for bug #920348. > > In any case, there is nothing happening here specific to > postfix-mta-sts-resolver, the same problem would happen with > any other package that does not permit stderr output in the > autopkgtest when upgrading ca-certificates is tested. > > The failing part of the autopkgtest is a testing->unstable upgrade of > ca-certificates. > > Any objections to reassigning this to ca-certificates? > After thinking about this a bit more I think ca-certificates is doing the right thing here, and permitting this stderr output is a reasonable workaround for affected packages until we can avoid the warning with an openssl change. Cheers, Julien
Processed: Re: Bug#996048: [Pkg-openssl-devel] Bug#996048: postfix-mta-sts-resolver: autopkgtest doesn't handle new version of ca-certificates nicely: rehash: warning: skipping ca-certificates.crt, it
Processing control commands: > reassign -1 postfix-mta-sts-resolver Bug #996048 [src:ca-certificates] postfix-mta-sts-resolver: autopkgtest doesn't handle new version of ca-certificates nicely: rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL Bug reassigned from package 'src:ca-certificates' to 'postfix-mta-sts-resolver'. No longer marked as found in versions ca-certificates/20211016. Ignoring request to alter fixed versions of bug #996048 to the same values previously set -- 996048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003543: shush: crontab path not defined
Package: shush Version: 1.2.3-5+b2 Severity: grave Justification: renders package unusable Dear Maintainer, shush is unable to find crontab path on Debian bullseye (similar to #758126): $ shush -i shush: execv(NOCRONTAB): No such file or directory shush: The impossible just happened: line 51 in file exec.c was reached! shush: Nothing to do. Re-building the package from source after having installed the cron package fix the issue. Thank for your work, Antoine -- System Information: Debian Release: 11.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.14.17-201.fc34.x86_64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages shush depends on: ii libc6 2.31-13+deb11u2 ii libpcre3 2:8.39-13 shush recommends no packages. shush suggests no packages. -- no debconf information
Bug#1003540: gsl-doc: please update to 2.7.1
On 11 January 2022 at 17:31, Andreas Beckmann wrote: | Package: gsl-doc | Version: 2.6-2 | Severity: serious Why would that be a serious bug rather normal or even minor? It's a bit of a manual process becuase of the dfsg dance and manual ops. And there generally is not that much that changes between versions -- GSL is fairly mature and stable at this point. Dirk | Hi, | | please update gsl-doc to 2.7.1 to match the gsl version in the archive: | | gsl| 2.7.1+dfsg-3 | unstable | source | gsl-doc| 2.6-2 | unstable/non-free| source | | Andreas -- https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1003542: scribus-doc: please update to 1.5.7
Package: scribus-doc Version: 1.5.6.1+dfsg-1 Severity: serious Tags: sid bookworm Hi, please update scribus-doc to 1.5.7 to match the scribus version in the archive: scribus | 1.5.7+dfsg-5 | unstable | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x scribus-doc | 1.5.6.1+dfsg-1 | unstable/non-free| source, all Andreas
Bug#1003541: org-mode-doc: please update to 9.5.2
Package: org-mode-doc Version: 9.4.0-2 Severity: serious Tags: sid bookworm Hi, please update org-mode-doc to 9.5.2 to match the org-mode version in the archive: org-mode | 9.5.2+dfsh-4 | unstable | source, all org-mode-doc | 9.4.0-2 | unstable/non-free| source, all Andreas
Bug#1003540: gsl-doc: please update to 2.7.1
Package: gsl-doc Version: 2.6-2 Severity: serious Hi, please update gsl-doc to 2.7.1 to match the gsl version in the archive: gsl| 2.7.1+dfsg-3 | unstable | source gsl-doc| 2.6-2 | unstable/non-free| source Andreas
Bug#1003539: coq-doc: several releases behind coq
Package: coq-doc Version: 8.6-1 Severity: serious Hi, coq-doc is several releases behind coq - how useful is this outdated documentation package? coq-doc | 8.4pl4-2 | stretch/non-free | source coq-doc | 8.6-1 | sid/non-free | source coq | 8.6-4 | stretch | source coq | 8.9.0-1| buster| source coq | 8.12.0-3 | bullseye | source coq | 8.14.1+dfsg-1 | bookworm | source coq | 8.14.1+dfsg-1 | sid | source Andreas
Bug#1001545: pyopencl, build-depends on package that is no longer in testing
Source: pyopencl Version: 2021.2.9-1 Followup-For: Bug #1001545 Reading the history further, mesa-opencl-icd was replaced by pocl-opencl-icd | opencl-icd for 2016.1+git20161003-2, commit 3b0d193c, "pocl-opencl-icd is the best default choice when there no other OpenCL ICD installed as it uses CPU and no specialized hardware" But that was only for the binary package Depends. The source package Build-Depends: pocl-opencl-icd was added much later for 2020.2.2-1, Commit f815 Would we more packaging stability that respects the intention to use pocl-opencl-icd where available if we switch to Build-Depends: mesa-opencl-icd | pocl-opencl-icd | opencl-icd with python3-pyopencl Depends: pocl-opencl-icd | mesa-opencl-icd | opencl-icd i.e. use mesa-opencl-icd to build the package, and prefer pocl-opencl-icd to use it.
Processed: found 1001841 in 3.20.0-1
Processing commands for cont...@bugs.debian.org: > found 1001841 3.20.0-1 Bug #1001841 [liblouis] liblouisutdml autopkgtest failing with the new liblouis Bug #1002097 [liblouis] liblouisutdml: FTBFS: tests fail There is no source info for the package 'liblouis' at version '3.20.0-1' with architecture '' Unable to make a source version for version '3.20.0-1' Marked as found in versions 3.20.0-1. Marked as found in versions 3.20.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1001841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001841 1002097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 1001841 in 3.19.0-2
Processing commands for cont...@bugs.debian.org: > notfound 1001841 3.19.0-2 Bug #1001841 [liblouis] liblouisutdml autopkgtest failing with the new liblouis Bug #1002097 [liblouis] liblouisutdml: FTBFS: tests fail There is no source info for the package 'liblouis' at version '3.19.0-2' with architecture '' Unable to make a source version for version '3.19.0-2' Ignoring request to alter found versions of bug #1001841 to the same values previously set Ignoring request to alter found versions of bug #1002097 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1001841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001841 1002097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1001841 to liblouis
Processing commands for cont...@bugs.debian.org: > reassign 1001841 liblouis Bug #1001841 [src:liblouisutdml] liblouisutdml autopkgtest failing with the new liblouis Bug #1002097 [src:liblouisutdml] liblouisutdml: FTBFS: tests fail Bug reassigned from package 'src:liblouisutdml' to 'liblouis'. Bug reassigned from package 'src:liblouisutdml' to 'liblouis'. No longer marked as found in versions liblouisutdml/2.10.0-3. No longer marked as found in versions liblouisutdml/2.10.0-3. Ignoring request to alter fixed versions of bug #1001841 to the same values previously set Ignoring request to alter fixed versions of bug #1002097 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1001841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001841 1002097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001545: pyopencl, build-depends on package that is no longer in testing
Source: pyopencl Followup-For: Bug #1001545 It should be possible to close this bug soon once pocl 1.8-3 migrates to testing. If pocl continues to make trouble, a workaround could be to replace Build-Depends: pocl-opencl-icd with Build-Depends: mesa-opencl-icd | pocl-opencl-icd | opencl-icd and package Depends: pocl-opencl-icd | opencl-icd with Depends: mesa-opencl-icd | pocl-opencl-icd | opencl-icd Actually I'd say it's best to do that anyway, since mesa-opencl-icd builds for all arches while pocl-opencl-icd has never built on ppc64el and other arches. Or even drop pocl-opencl-icd altogether and just use Depends: mesa-opencl-icd | opencl-icd
Bug#997601: marked as done (fail2ban: FTBFS: error in fail2ban setup command: use_2to3 is invalid.)
Your message dated Tue, 11 Jan 2022 15:34:25 +
with message-id
and subject line Bug#997601: fixed in fail2ban 0.11.2-4
has caused the Debian Bug report #997601,
regarding fail2ban: FTBFS: error in fail2ban setup command: use_2to3 is invalid.
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.)
--
997601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997601
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fail2ban
Version: 0.11.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem pybuild
>dh_auto_clean -O--buildsystem=pybuild
> pybuild --clean -i python{version} -p 3.9
> I: pybuild base:232: python3.9 setup.py clean
> error in fail2ban setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:15: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/fail2ban_0.11.2-2_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: fail2ban
Source-Version: 0.11.2-4
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 997...@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: Tue, 11 Jan 2022 09:12:57 +0100
Source: fail2ban
Architecture: source
Version: 0.11.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Sylvestre Ledru
Closes: 997601
Changes:
fail2ban (0.11.2-4) unstable; urgency=medium
.
* Cherry pick 5ac303df8a171f748330d4c645ccbf1c2c7f3497
to address the 2to3 issue.
Thanks to Paul Wise for digging
(Closes: #997601)
Checksums-Sha1:
2d0fa650ae6570f8b1c0a97852617eeecc694e69 2045 fail2ban_0.11.2-4.dsc
7bd49fcf22973eb66a71000363282d09b244 32204 fail2ban_0.11.2-4.debian.tar.xz
46dadfcce62367c84a25723a04de83fd17a49fa3 6482 fail2ban_0.11.2-4_amd64.buildinfo
Checksums-Sha256:
1d3898f52f9aa86ede6883bff4c7b9a40709131112fb53de41d0208cb3d66c56 2045
fail2ban_0.11.2-4.dsc
65618352f061923b4246907ee429dd0f218e51abbe3df416babca5308b9fdc42 32204
fail2ban_0.11.2-4.debian.tar.xz
61f8a8707967833c8f97a60b34d9babc262e7591d28ac0d0aeab64db36d9d75f 6482
fail2ban_0.11.2-4_amd64.buildinfo
Files:
47880164dc47908368f7aa3f42c824ec 2045 net optional fail2ban_0.11.2-4.dsc
7c6f78aba91d5fefe0ea838611b0c013 32204 net optional
fail2ban_0.11.2-4.debian.tar.xz
c61429a88d64a3487e7ec07d43ee156f 6482 net optional
fail2ban_0.11.2-4_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmHdnkgACgkQfmUo2nUv
G+EyBg//V9SJl1746w1sdinSDx/TCZPdRPQT11lNPmhQsPiZh9ZrC9xUZcyLFeAb
GjZeUtEj7v0tqjMgbxrwvB64GoFtdZWPtF3PXgeByxLbJ7viwVIjjSOJNpVm7XMA
dnQ305FRDbGrYxOv3/RfDLWSqqP4+fxSdGTyf5eE/ZwRVc7Z4hBx7TZjoYPx/WPl
1I7EDWErGGFVeKaYNNq2IBEus4Xo7LuVN79M6b0ciEiLFLBwA9FQ/zCt0FsMF/I2
YpvZ4yIOw9DIjthMVPcgPgqxLEF96YWe7+HZmAxaRzpdTlfCNq/9c5bnH7AqTgfS
mRWx8+GS8nrpcd2S9zn4XHl/RpcPGwNmt+J1dwYlOBtkDzOfI1PgVXVKCQ9BTUrL
jH4J74ozFOahefKMG3nNfy9j9hFY7JhYKlizkTuodS80YUK3Q0p7QRhOZfCq2g5v
SA+/OTn6h7ZVRrZmgqRPh7T5xtTbkCFDXru0NeAtCNHslXHAEajFrHKfCZw7HBLj
DWFcgzt83GuO0PjqFwGur+Lf66WO8RocrvI27OroCDoh/0V6UVYNVAlC/CpeTY++
Bug#1001766: oomd: ships both ./lib/systemd/system/oomd.service & ./usr/lib/systemd/system/oomd.service
Hi! Got a different error (with the same cause) when installing 0.5.0-1 using apt: Unpacking oomd (0.5.0-1+b1) ... dpkg: error processing archive /tmp/apt-dpkg-install-46e3FG/48-oomd_0.5.0-1+b1_amd64.deb (--unpack): unable to open '/usr/lib/systemd/system/oomd.service.dpkg-new': No such file or directory Looks like the package builds OK, but lintian fails: $ gbp clone https://salsa.debian.org/yangfl-guest/oomd.git $ cd oomd $ gbp buildpackage -uc -us ... Now running lintian oomd_0.5.0-1_amd64.changes ... E: oomd: file-in-root-and-usr lib/systemd/system/oomd.service usr/lib/systemd/system/oomd.service ... This is probably due to both oomd and the package shipping a (different!) service file: src/oomd/etc/oomd.service.in debian/oomd.service I've prepared a merge request to drop the upstream service (since the package's version is better) at: https://salsa.debian.org/yangfl-guest/oomd/-/merge_requests/3 Thank you! Christopher Obbard
Bug#997652: marked as done (sparql-wrapper-python: FTBFS: error in SPARQLWrapper setup command: use_2to3 is invalid.)
Your message dated Tue, 11 Jan 2022 14:48:55 +
with message-id
and subject line Bug#997652: fixed in sparql-wrapper-python 1.8.5-2
has caused the Debian Bug report #997652,
regarding sparql-wrapper-python: FTBFS: error in SPARQLWrapper setup command:
use_2to3 is invalid.
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.)
--
997652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sparql-wrapper-python
Version: 1.8.5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package sparql-wrapper-python
> dpkg-buildpackage: info: source version 1.8.5-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Sandro Tosi
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> /usr/lib/python3.9/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'use_2to3_fixers'
> warnings.warn(msg)
> error in SPARQLWrapper setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p 3.9
> returned exit code 13
> make: *** [debian/rules:15: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/sparql-wrapper-python_1.8.5-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: sparql-wrapper-python
Source-Version: 1.8.5-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
sparql-wrapper-python, 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 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated sparql-wrapper-python
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: Tue, 11 Jan 2022 15:23:08 +0100
Source: sparql-wrapper-python
Architecture: source
Version: 1.8.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Andreas Tille
Closes: 997652
Changes:
sparql-wrapper-python (1.8.5-2) unstable; urgency=medium
.
* Team upload.
.
[ Ondřej Nový ]
* d/control: Update Maintainer field with new Debian Python Team
contact address.
* d/control: Update Vcs-* fields with new Debian Python Team Salsa
layout.
.
[ Debian Janitor ]
* Use secure URI in Homepage field.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
* Bump debhelper from old 12 to 13.
.
[ Andreas Tille ]
* Standards-Version: 4.6.0 (routine-update)
* Add salsa-ci file (routine-update)
* No tab in license text (routine-update)
* watch file standard 4 (routine-update)
* Do not use use_2to3 since it is deprecated
Closes: #997652
* Fix autopkgtest-pkg-python
Checksums-Sha1:
03349c24cf965269ca200ffd1ef648d720eafd73 2205 sparql-wrapper-python_1.8.5-2.dsc
f14c269e347d6d83e3303ffbbbcf15ac3d757959 8552
sparql-wrapper-python_1.8.5-2.debian.tar.xz
26393896df54b8857bdd0932a9e3a9d63aa158a5 6825
sparql-wrapper-python_1.8.5-2_amd64.buildinfo
Checksums-Sha256:
Bug#1000593: Failing testsuite with PHP 8.1
Hi taffit, On Thu, 25 Nov 2021 at 11:50:24 -0400, David Prévot wrote: > There is a new upstream version (1.2.4), but I quickly checked that > two failures (first and last) still happen. (It’s also not a PEAR > package anymore, so need some work to convert the packaging to its > Composer source). I plan to work on this during the next few days if no one beats me to it. AFAICT php-console-commandline's only reverse depends is php-crypt- gpg which in turns is currently only used for Roundcube. (I currently co-maintain these packages already.) Cheers, -- Guilhem. signature.asc Description: PGP signature
Bug#1003218: marked as done (libhwy-dev: HWY_CMAKE_ARM7:BOOL=ON triggers illegal instructions on armhf)
Your message dated Tue, 11 Jan 2022 14:34:40 + with message-id and subject line Bug#1003218: fixed in highway 0.15.0-5 has caused the Debian Bug report #1003218, regarding libhwy-dev: HWY_CMAKE_ARM7:BOOL=ON triggers illegal instructions on armhf 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.) -- 1003218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libhwy-dev Version: 0.15.0-3 Severity: normal Dear Maintainer, highway fails to build on armhf as seen at: https://buildd.debian.org/status/fetch.php?pkg=highway=armhf=0.15.0-3=1641476548=0 Please disable HWY_CMAKE_ARM7 option for now. -- System Information: Debian Release: 11.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-0.bpo.2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information --- End Message --- --- Begin Message --- Source: highway Source-Version: 0.15.0-5 Done: Mathieu Malaterre We believe that the bug you reported is fixed in the latest version of highway, 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. Mathieu Malaterre (supplier of updated highway 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: Tue, 11 Jan 2022 14:52:28 +0100 Source: highway Architecture: source Version: 0.15.0-5 Distribution: unstable Urgency: medium Maintainer: Debian PhotoTools Maintainers Changed-By: Mathieu Malaterre Closes: 1003218 Changes: highway (0.15.0-5) unstable; urgency=medium . * d/rules: Clarify that we only ship static libs for now * d/control: Add missing Rules-Requires-Root: no * d/patches: Remove compilation error on GNU/Hurd * d/rules: Set HWY_CMAKE_ARM7 to OFF. Closes: #1003218 * d/patches: Fix compilation error on riscv64 Checksums-Sha1: a78d357e1c3b596655945b2bc262dcdc65534f5d 2071 highway_0.15.0-5.dsc 56c78c4c1fd2ffe7a5d6808bb79adfdb56ba56b3 4164 highway_0.15.0-5.debian.tar.xz a29881463a31d247401d600a70231c9897bffe3e 6936 highway_0.15.0-5_source.buildinfo Checksums-Sha256: 019a1dc99c558ac73a7632f5384e8a64467e9937903bdd2bad0939ba53160d03 2071 highway_0.15.0-5.dsc 364ea078cfcf1cbe459ec1b3b59326bafce7016ae1a31af122abfb310fb4149a 4164 highway_0.15.0-5.debian.tar.xz 061b6f9b7bc4f95bb7ba42fc01cde5c411a5160062688f1081d0a15e8d7d2611 6936 highway_0.15.0-5_source.buildinfo Files: 423999c4ea5f5c792b0463698b40969a 2071 libs optional highway_0.15.0-5.dsc d684000966c6533afd35927764d631a4 4164 libs optional highway_0.15.0-5.debian.tar.xz 57970ee2a84bcce66711639b12b3d932 6936 libs optional highway_0.15.0-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAmHdi9YRHG1hbGF0QGRl Ymlhbi5vcmcACgkQAXHhgorgk0WE7hAAjDZ9/TIz4gQBE3Db7dHVrCaVQJ7FOCPe LUnaRRWsypqMmjskoOrG37d/z5IdMgxsVSJDxyIV8eKBolIGm4ZxCeUC8PX6058P KO9A/OHFeCRqFIH1CdDMxFRDAkMlu2U19z+Q0bigXP52kYSmhdG5JFm6bS/FuHcX svYHFGv7F6pcs5GoBzR3FAdKKEu+HrsD329swowrA9c0SIB/vC9zIHcEZcrdUSpO Gq+Q+bXaWpVvGeBMIOzp6OKqzo6+tL+JDd7piPWiRqswFDHikbP1V2WEM2ZqABBf roBixd6ZzdMZIIXeh14odwXFgQ+mMKVv6zu/7jFEs7QerPY7KT24GYSY1NPQwiU8 KhesrEvwu749w1gL3i5M3b7ZwvORhZ7t8oDmnHvLoROfhy1dHTX0AcjZckcCfMQB 2B7BI8fHLTglusDEBtS6RY3rRUcizNNlggobeS4TGrLp0fCh6oIeSIn1eG/a8er9 XovpSzCDtMljM19B8b2zsnSoAdXeoZgFhWCHgjUSoEuvunMOgYKcWUhX9uUlbidw /swdKGzpgXVyMSM44mmyaxWxHng4Av1IsSQ+1BSumeOGBYFoUaeRNVdQGvKsqKJb UQxg6ZpXQdlb1eQ4/9+FDWBnsfOeFfRZqVFiLEK/QIYt5/BEFmdDngW+a8IJllvZ awujyoWzJTU= =mHrf -END PGP SIGNATURE End Message ---
Bug#1002722: marked as done (python-rdflib-tools must depend on python3-rdflib (= ${source:Version}))
Your message dated Tue, 11 Jan 2022 14:36:46 +
with message-id
and subject line Bug#1002722: fixed in rdflib 5.0.0-2
has caused the Debian Bug report #1002722,
regarding python-rdflib-tools must depend on python3-rdflib (=
${source:Version})
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.)
--
1002722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-rdflib-tools
Version: 4.2.2-2
Severity: serious
Installing python-rdflib-tools/buster and python3-rdflib/bullseye:
$ rdfs2dot < /dev/null
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 583, in
_build_master
ws.require(__requires__)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 900, in
require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 791, in
resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.VersionConflict: (rdflib 5.0.0 (/usr/lib/python3/dist-packages),
Requirement.parse('rdflib==4.2.2'))
...
This is a regression introduced by the fix for #921751.
--- End Message ---
--- Begin Message ---
Source: rdflib
Source-Version: 5.0.0-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
rdflib, 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.
Andreas Tille (supplier of updated rdflib 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: Tue, 11 Jan 2022 12:40:59 +0100
Source: rdflib
Architecture: source
Version: 5.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Andreas Tille
Closes: 1002722
Changes:
rdflib (5.0.0-2) unstable; urgency=medium
.
* Team upload.
* python-rdflib-tools: Depend: python3-rdflib (= ${source:Version})
Closes: #1002722
* Standards-Version: 4.6.0 (routine-update)
* debhelper-compat 13 (routine-update)
* Remove trailing whitespace in debian/copyright (routine-update)
* Add salsa-ci file (routine-update)
* Rules-Requires-Root: no (routine-update)
* No tab in license text (routine-update)
* Add missing build dependency on dh addon.
* Set upstream metadata fields: Bug-Database, Bug-Submit.
* Apply multi-arch hints.
+ python-rdflib-doc: Add Multi-Arch: foreign.
* watch file standard 4 (routine-update)
* Drop Build-Depends: dpkg-dev
* Cleanup d/copyright from Files that are not included in source any more
Checksums-Sha1:
7d405b4e437ad3d7b4feea9c7cceb5c8ffd0670a 2681 rdflib_5.0.0-2.dsc
66d9ebdb1c184567b971aabdab5389282908ce6c 29244 rdflib_5.0.0-2.debian.tar.xz
fc19efa02417462b398505ebacab81f9e48e1d9e 8462 rdflib_5.0.0-2_amd64.buildinfo
Checksums-Sha256:
5c4d2242ab1d382ebca4ad9cb9851abdbed454fb7858f2a1a2a62a2effe7459b 2681
rdflib_5.0.0-2.dsc
c34d5a3e2e07c47404f955a112f9a7502d6fb14b8638bca095278e6a280ccc78 29244
rdflib_5.0.0-2.debian.tar.xz
f39d573d9f48bfb66ecf02fa74167905f2883959aea60a4f97c33a230e66312f 8462
rdflib_5.0.0-2_amd64.buildinfo
Files:
083fe850571a22c3cc6bea3609ba20b5 2681 python optional rdflib_5.0.0-2.dsc
57af71803c8f3fd28d03941de6ed243c 29244 python optional
rdflib_5.0.0-2.debian.tar.xz
9e25c4751afa3642be2e24331744c818 8462 python optional
rdflib_5.0.0-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmHdjdcRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHEpw//RyLfDwKxopJbrbXq4r3Z6FWzW3Iad2YF
L8sADx5oMUluIgCFIIAjmi5BgjBORQ4xJ9jWP1eALV+vdApIl3bRxk/iYEQ9FIQy
F5jL6nbtBhardzMhs3m0kYkrA/eN8LH/ILZHg5uCxnJdJnAphYIdZ4RY8Xc0BzFk
FceTCtcYAvfBBzrZ/l2n9NnO4PODOAprVLZYXG8EQ5mzCWT8aRiHsZBTMqVgj5oD
iPvCF69W/M4QDKrA36ZHjrebITQBJUuztGOKbG2ULlkA4xBmwRwIuuvZmSMBpHAN
q5eHx2iXBGVndl6+vyi2DrSriNHuBkm+g+COzSqL+CAHfZmZgFd6mAqJU58/CZVP
T/5LGTcX0LWux5haAK9oDQjurtNsuTRrSWJt22nZ5so6m2nnlwG/qavaPl3xQVL0
Ky2Db1vusrk9p69PHup6glLYK8ifrwGFnheV7KZ5vq12O89drd/H/wP6Mg4EGkPf
Bug#1002216: marked as done (jpylyzer: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Tue, 11 Jan 2022 14:56:11 +0100
with message-id
and subject line jpylyzer: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
has caused the Debian Bug report #1002216,
regarding jpylyzer: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.9 returned exit code 13
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.)
--
1002216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jpylyzer
Version: 2.0.0-3
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[1]: Entering directory '/<>'
> dh_auto_build
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level
> 9 in use)
> I: pybuild base:237: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/jpylyzer
> copying jpylyzer/byteconv.py ->
> /<>/.pybuild/cpython3_3.9/build/jpylyzer
> copying jpylyzer/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/jpylyzer
> copying jpylyzer/__main__.py ->
> /<>/.pybuild/cpython3_3.9/build/jpylyzer
> copying jpylyzer/shared.py ->
> /<>/.pybuild/cpython3_3.9/build/jpylyzer
> copying jpylyzer/jpylyzer.py ->
> /<>/.pybuild/cpython3_3.9/build/jpylyzer
> copying jpylyzer/mix.py ->
> /<>/.pybuild/cpython3_3.9/build/jpylyzer
> copying jpylyzer/boxvalidator.py ->
> /<>/.pybuild/cpython3_3.9/build/jpylyzer
> copying jpylyzer/config.py ->
> /<>/.pybuild/cpython3_3.9/build/jpylyzer
> copying jpylyzer/etpatch.py ->
> /<>/.pybuild/cpython3_3.9/build/jpylyzer
> creating /<>/.pybuild/cpython3_3.9/build/tests
> copying tests/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/tests
> creating /<>/.pybuild/cpython3_3.9/build/tests/unit
> copying tests/unit/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/tests/unit
> copying tests/unit/test_jpylyzer.py ->
> /<>/.pybuild/cpython3_3.9/build/tests/unit
> (cd doc && pandoc -s --toc --toc-depth=2 -N --top-level-division=chapter
> --pdf-engine=xelatex -o jpylyzerUserManual.pdf jpylyzerUserManual.md)
> [WARNING] Note with key '2' defined at line 2280 column 1 but not used.
> [WARNING] Missing character: There is no ∑ (U+2211) (U+2211) in font
> [lmroman10-regular]:mapping=t
> [WARNING] Missing character: There is no ≤ (U+2264) (U+2264) in font
> [lmroman10-regular]:mapping=t
> [WARNING] Missing character: There is no ≥ (U+2265) (U+2265) in font
> [lmroman10-regular]:mapping=t
> [WARNING] Missing character: There is no ≥ (U+2265) (U+2265) in font
> [lmroman10-regular]:mapping=t
> [WARNING] Missing character: There is no ≤ (U+2264) (U+2264) in font
> [lmroman10-regular]:mapping=t
> [WARNING] Missing character: There is no ≥ (U+2265) (U+2265) in font
> [lmroman10-regular]:mapping=t
> [WARNING] Missing character: There is no ≥ (U+2265) (U+2265) in font
> [lmroman10-regular]:mapping=t
> (cd doc && pandoc -o jpylyzerUserManual.txt jpylyzerUserManual.md)
> [WARNING] Note with key '2' defined at line 2280 column 1 but not used.
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9
> in use)
> I: pybuild base:237: cd /<>/.pybuild/cpython3_3.9/build;
> python3.9 -m pytest tests
> = test session starts
> ==
> platform linux -- Python 3.9.9, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
> rootdir: /<>
> collected 0 items / 1 error
>
> ERRORS
>
> ___ ERROR collecting .pybuild/cpython3_3.9/build/tests/unit/test_jpylyzer.py
> ___
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.9/build/tests/unit/test_jpylyzer.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.9/importlib/__init__.py:127: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> tests/unit/test_jpylyzer.py:5: in
> from jpylyzer.jpylyzer import __version__, checkNullArgs, checkNoInput, \
> jpylyzer/jpylyzer.py:45: in
> from six import u
> E ModuleNotFoundError: No module named 'six'
> === short test summary info
>
> ERROR tests/unit/test_jpylyzer.py
> Interrupted: 1
Processed: jpylyzer: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Processing control commands:
> fixed -1 2.0.1-1
Bug #1002216 [src:jpylyzer] jpylyzer: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p 3.9 returned exit code 13
The source 'jpylyzer' and version '2.0.1-1' do not appear to match any binary
packages
Marked as fixed in versions jpylyzer/2.0.1-1.
--
1002216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1002216: jpylyzer: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Control: fixed -1 2.0.1-1
Bug#997194: marked as done (mtr: FTBFS: ../ui/curses.c:435:17: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Tue, 11 Jan 2022 13:05:03 + with message-id and subject line Bug#997194: fixed in mtr 0.95-1 has caused the Debian Bug report #997194, regarding mtr: FTBFS: ../ui/curses.c:435:17: error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 997194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mtr Version: 0.94-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread > -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include > -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu > -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi > -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/harfbuzz > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16-g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Wno-pointer-sign -c -o ui/mtr-curses.o `test > -f 'ui/curses.c' || echo '../'`ui/curses.c > ../ui/curses.c: In function ‘mtr_curses_hosts’: > ../ui/curses.c:435:17: error: format not a string literal and no format > arguments [-Werror=format-security] > 435 | printw(fmt_ipinfo(ctl, addr)); > | ^~ > ../ui/curses.c:488:21: error: format not a string literal and no format > arguments [-Werror=format-security] > 488 | printw(fmt_ipinfo(ctl, addrs)); > | ^~ > ../ui/curses.c: In function ‘mtr_curses_graph’: > ../ui/curses.c:653:17: error: format not a string literal and no format > arguments [-Werror=format-security] > 653 | printw(fmt_ipinfo(ctl, addr)); > | ^~ > ../ui/curses.c: In function ‘mtr_curses_redraw’: > ../ui/curses.c:703:5: error: format not a string literal and no format > arguments [-Werror=format-security] > 703 | mvprintw(1, maxx - 25, iso_time()); > | ^~~~ > ../ui/curses.c:763:42: error: format not a string literal and no format > arguments [-Werror=format-security] > 763 | mvprintw(rowstat - 1, startstat, msg); > | ^~~ > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread > -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include > -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu > -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi > -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/harfbuzz > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16-g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Wno-pointer-sign -c -o ui/mtr-gtk.o `test -f > 'ui/gtk.c' || echo '../'`ui/gtk.c > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Wno-pointer-sign -c -o packet/packet.o > ../packet/packet.c > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Wno-pointer-sign -c -o packet/cmdparse.o > ../packet/cmdparse.c > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Wno-pointer-sign -c -o packet/command.o > ../packet/command.c > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Wno-pointer-sign -c -o packet/probe.o > ../packet/probe.c > In file included from /usr/include/string.h:519, > from ../packet/probe.c:31: > In function ‘strncat’, >
Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)
On Mon, Jan 10, 2022 at 02:21:48PM -0500, Andres Salomon wrote: > On 1/10/22 05:01, Mattia Rizzolo wrote: > > On Sun, Jan 09, 2022 at 11:23:20PM -0500, Andres Salomon wrote: > > > Btw, https://salsa.debian.org/dilinger/chromium/-/tree/stable is my branch > > > with cleaned-up commits. That's what I'll use for the NMU, which I'm > > > preparing now. > > If you all agree, you could finalize the tree, then I'll build again, > > after which I could sponsor this after a couple days of testing. > > > > I see that you changed debian/copyright compared to the one I used in my > > build here, so I'll export the orig tarball again. (normally with > > Michel we'd share the sha256 of one's produced tarball to check we are > > building with the same thing, so please share yours?) > > > Thank you so much for testing! The sha256 that I have is > cca093107bf6991b4777889012646455f8e520b446c9f27250653f98ed4bb7e0 Cool, this matches with the new tarball I produced. Guess I'll restart a build with the stable branch now then. BTW, my current build (from the v97 branch), just crashed on me. Not sure where, and I couldn't quickly reproduce it either; I was just clicking ont he "extension bar", but I'm not even sure what I was doing.. just saying :) > I don't need a sponsor (I'm a developer), but thank you for the offer. Ah! Apologies! I didn't look your name up, and I just assumed so from the n...@debian.org address. Well, happy then, less "work" for me :D > Btw, hopefully Michael is just currently busy and is still interested in > working on chromium? I ralized that riku retaired formally last month (indeed, please drop him from Uploaders, I also opened a bug (as MIA team) against chromium last month). About Micheal, that's unclear to me: he stated less than one year ago that he would keep working on chromium, but he really is not answering to anybody... so well, even if he is still interested, in a case as big as chromium I think you really needs to show consideration and be at least reachable. Though it might just be my own opinion. -- 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
Bug#1002770: marked as done (lua-say: FTBFS: dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple test returned exit code 2)
Your message dated Tue, 11 Jan 2022 12:49:25 + with message-id and subject line Bug#1002770: fixed in lua-say 1.3-1-7 has caused the Debian Bug report #1002770, regarding lua-say: FTBFS: dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple test returned exit code 2 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.) -- 1002770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002770 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lua-say Version: 1.3-1-6 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211228 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem=lua --with lua >dh_update_autotools_config -O--buildsystem=lua >dh_autoreconf -O--buildsystem=lua >dh_auto_configure -O--buildsystem=lua > make --no-print-directory -f > /usr/share/dh-lua/make/dh-lua.Makefile.multiple configure > > Making target configure for debian/lua5.1.dh-lua.conf > # .install > Filling in debian/lua-say.install using > /usr/share/dh-lua/template/lib.install.in > Adding new line: > Adding new line: usr/share/lua/5.1/say/init.lua > Filling in debian/lua-say-dev.install using > /usr/share/dh-lua/template/dev.install.in > Adding new line: > # lua_versions > Filling in debian/lua_versions > Adding new line: 5.1 > Target configure made > > > Making target configure for debian/lua5.2.dh-lua.conf > # .install > Filling in debian/lua-say.install using > /usr/share/dh-lua/template/lib.install.in > Adding new line: usr/share/lua/5.2/say/init.lua > Filling in debian/lua-say-dev.install using > /usr/share/dh-lua/template/dev.install.in > # lua_versions > Filling in debian/lua_versions > Adding new line: 5.2 > Target configure made > > > Making target configure for debian/lua5.3.dh-lua.conf > # .install > Filling in debian/lua-say.install using > /usr/share/dh-lua/template/lib.install.in > Adding new line: usr/share/lua/5.3/say/init.lua > Filling in debian/lua-say-dev.install using > /usr/share/dh-lua/template/dev.install.in > # lua_versions > Filling in debian/lua_versions > Adding new line: 5.3 > Target configure made > > > Making target configure for debian/lua5.4.dh-lua.conf > # .install > Filling in debian/lua-say.install using > /usr/share/dh-lua/template/lib.install.in > Adding new line: usr/share/lua/5.4/say/init.lua > Filling in debian/lua-say-dev.install using > /usr/share/dh-lua/template/dev.install.in > # lua_versions > Filling in debian/lua_versions > Adding new line: 5.4 > Target configure made > >dh_auto_build -O--buildsystem=lua > make --no-print-directory -f > /usr/share/dh-lua/make/dh-lua.Makefile.multiple build > > Making target build for debian/lua5.1.dh-lua.conf > Target build made > > > Making target build for debian/lua5.2.dh-lua.conf > Target build made > > > Making target build for debian/lua5.3.dh-lua.conf > Target build made > > > Making target build for debian/lua5.4.dh-lua.conf > Target build made > >dh_auto_test -O--buildsystem=lua > make --no-print-directory -f > /usr/share/dh-lua/make/dh-lua.Makefile.multiple test > > Making target test for debian/lua5.1.dh-lua.conf > # tests > /usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > Copying src/init.lua in /<>/5.1-say for test > ** lua dynamic custom (5.1) ** > + > 5 successes / 0 failures / 0 errors / 0 pending : 0.000701 seconds > * > Target test made > > > Making target test for debian/lua5.2.dh-lua.conf > # tests > /usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > Copying src/init.lua in /<>/5.2-say for test > ** lua dynamic custom (5.2) ** > + > 5 successes / 0 failures / 0 errors / 0 pending : 0.001066 seconds > * > Target test made > > > Making target test for debian/lua5.3.dh-lua.conf > # tests > /usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > Copying src/init.lua in /<>/5.3-say for test > ** lua dynamic custom (5.3) ** > + > 5 successes / 0 failures / 0 errors / 0 pending : 0.002288 seconds > * > Target test made > > > Making target test for debian/lua5.4.dh-lua.conf > # tests >
Bug#1003530: lintian: Hangs when checking some .dsc file
On Tue, Jan 11, 2022 at 07:29:32AM -0500, Boyuan Yang wrote: > I just notice that lintian will never finish when checking some specific That's not correct. > https://mentors.debian.net/package/fcitx5-table-extra/ shows the lintian check > result to be " lintian took too much time to run ". I actually never saw lintian *hang*. It just got quite slow. Specifically, on mentors.d.n we set a timeout for lintian of 30 minutes. We really don't want the whole site to spend hours processing an incoming packages... Notably, in mentors we don't use `-X cruft` to bypass the slowest codepath in lintian, that can easily go over the 30 minutes time. > I am not 100% sure about the severity, but endless hang could be serious. Feel > free to let me know if you have any questions. IMHO, this could just be merged with that other bug (that I'm not looking up) about the cruft check being slow. Did you try running lintian yourself to actually verify it hangs somewhere? -- 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
Bug#1002216: jpylyzer: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
I just created a bugfix release that should fix this, details here: https://github.com/openpreserve/jpylyzer/issues/176#issuecomment-1009877080
Bug#1002774: marked as done (lua-cliargs: FTBFS: dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple test returned exit code 2)
Your message dated Tue, 11 Jan 2022 12:33:55 + with message-id and subject line Bug#1002774: fixed in lua-cliargs 3.0-2-3 has caused the Debian Bug report #1002774, regarding lua-cliargs: FTBFS: dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple test returned exit code 2 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.) -- 1002774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lua-cliargs Version: 3.0-2-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211228 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=lua --with lua >dh_update_autotools_config -O--buildsystem=lua >dh_autoreconf -O--buildsystem=lua >dh_auto_configure -O--buildsystem=lua > make --no-print-directory -f > /usr/share/dh-lua/make/dh-lua.Makefile.multiple configure > > Making target configure for debian/lua5.1.dh-lua.conf > # .install > Filling in debian/lua-cliargs.install using > /usr/share/dh-lua/template/lib.install.in > Adding new line: > Adding new line: usr/share/lua/5.1//cliargs.lua > Adding new line: usr/share/lua/5.1//cliargs/config_loader.lua > Adding new line: usr/share/lua/5.1//cliargs/constants.lua > Adding new line: usr/share/lua/5.1//cliargs/core.lua > Adding new line: usr/share/lua/5.1//cliargs/parser.lua > Adding new line: usr/share/lua/5.1//cliargs/printer.lua > Adding new line: usr/share/lua/5.1//cliargs/utils/disect.lua > Adding new line: usr/share/lua/5.1//cliargs/utils/disect_argument.lua > Adding new line: usr/share/lua/5.1//cliargs/utils/filter.lua > Adding new line: usr/share/lua/5.1//cliargs/utils/lookup.lua > Adding new line: usr/share/lua/5.1//cliargs/utils/shallow_copy.lua > Adding new line: usr/share/lua/5.1//cliargs/utils/split.lua > Adding new line: usr/share/lua/5.1//cliargs/utils/trim.lua > Adding new line: usr/share/lua/5.1//cliargs/utils/wordwrap.lua > Filling in debian/lua-cliargs-dev.install using > /usr/share/dh-lua/template/dev.install.in > Adding new line: > # lua_versions > Filling in debian/lua_versions > Adding new line: 5.1 > Target configure made > > > Making target configure for debian/lua5.2.dh-lua.conf > # .install > Filling in debian/lua-cliargs.install using > /usr/share/dh-lua/template/lib.install.in > Adding new line: usr/share/lua/5.2//cliargs.lua > Adding new line: usr/share/lua/5.2//cliargs/config_loader.lua > Adding new line: usr/share/lua/5.2//cliargs/constants.lua > Adding new line: usr/share/lua/5.2//cliargs/core.lua > Adding new line: usr/share/lua/5.2//cliargs/parser.lua > Adding new line: usr/share/lua/5.2//cliargs/printer.lua > Adding new line: usr/share/lua/5.2//cliargs/utils/disect.lua > Adding new line: usr/share/lua/5.2//cliargs/utils/disect_argument.lua > Adding new line: usr/share/lua/5.2//cliargs/utils/filter.lua > Adding new line: usr/share/lua/5.2//cliargs/utils/lookup.lua > Adding new line: usr/share/lua/5.2//cliargs/utils/shallow_copy.lua > Adding new line: usr/share/lua/5.2//cliargs/utils/split.lua > Adding new line: usr/share/lua/5.2//cliargs/utils/trim.lua > Adding new line: usr/share/lua/5.2//cliargs/utils/wordwrap.lua > Filling in debian/lua-cliargs-dev.install using > /usr/share/dh-lua/template/dev.install.in > # lua_versions > Filling in debian/lua_versions > Adding new line: 5.2 > Target configure made > > > Making target configure for debian/lua5.3.dh-lua.conf > # .install > Filling in debian/lua-cliargs.install using > /usr/share/dh-lua/template/lib.install.in > Adding new line: usr/share/lua/5.3//cliargs.lua > Adding new line: usr/share/lua/5.3//cliargs/config_loader.lua > Adding new line: usr/share/lua/5.3//cliargs/constants.lua > Adding new line: usr/share/lua/5.3//cliargs/core.lua > Adding new line: usr/share/lua/5.3//cliargs/parser.lua > Adding new line: usr/share/lua/5.3//cliargs/printer.lua > Adding new line: usr/share/lua/5.3//cliargs/utils/disect.lua > Adding new line: usr/share/lua/5.3//cliargs/utils/disect_argument.lua > Adding new line: usr/share/lua/5.3//cliargs/utils/filter.lua > Adding new line: usr/share/lua/5.3//cliargs/utils/lookup.lua > Adding new line: usr/share/lua/5.3//cliargs/utils/shallow_copy.lua > Adding new line: usr/share/lua/5.3//cliargs/utils/split.lua > Adding new line: usr/share/lua/5.3//cliargs/utils/trim.lua > Adding new line: usr/share/lua/5.3//cliargs/utils/wordwrap.lua >
Bug#1003530: lintian: Hangs when checking some .dsc file
Package: lintian Version: 2.114.0 Severity: grave X-Debbugs-CC: la...@debian.org Dear lintian maintainer, I just notice that lintian will never finish when checking some specific debian source package. As of 2022-01-11, https://mentors.debian.net/package/fcitx5-table-extra/ shows the lintian check result to be " lintian took too much time to run ". You may find an archived copy of dsc files at https://salsa.debian.org/byang/lintian-bugreport-20220111 . md5sum ./* d279730f7020a5509231d6e5571108aa ./fcitx5-table-extra_5.0.6-1.debian.tar.xz 12869f078c1b68ef385e5f4372797dcc ./fcitx5-table-extra_5.0.6-1.dsc fd7db60ae678b94607dae78a6a3e2752 ./fcitx5-table-extra_5.0.6.orig.tar.gz I am not 100% sure about the severity, but endless hang could be serious. Feel free to let me know if you have any questions. -- Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1002166: sdrangelove: FTBFS: gnuradiothread.cpp:139:23: error: no matching function for call to ‘gr::top_block::connect(osmosdr::source::sptr&, int, gr_adaptor_sptr&, int)’
Re: Lucas Nussbaum > Source: sdrangelove > Version: 0.0.1.20150707-5 > 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. sdrangelove hasn't really been touched upstream since 2015 (except 3 more or less boring git commits), so I propose we remove it. (... and I should finally get around to upload sdrangel.) Christoph
Processed: Bug#993699 marked as pending in libxtrx
Processing control commands: > tag -1 pending Bug #993699 [src:libxtrx] libxtrx: FTBFS with libsoapysdr 0.8 Added tag(s) pending. -- 993699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993699: marked as pending in libxtrx
Control: tag -1 pending Hello, Bug #993699 in libxtrx reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian-hamradio-team/libxtrx/-/commit/d7fecfef1db7054c56c2691bb750242d7e9caed2 Team upload. * Apply upstream patch for soapysdr 0.8 (Closes: #993699) * Bump soapysdr build-dependency to 0.8 * Change all references to soapysdr in debian packaging from 0.7 to 0.8 (this message was generated automatically) -- Greetings https://bugs.debian.org/993699
Bug#1003525: scalapack-doc: several releases behind scalapack
Package: scalapack-doc Version: 1.5-11 Severity: serious Tags: sid bookworm scalapack-doc is several releases behind scalapack: scalapack | 1.8.0-6 | squeeze | source scalapack | 1.8.0-9 | wheezy | source scalapack | 1.8.0-12 | jessie | source scalapack | 1.8.0-13 | stretch | source scalapack | 2.0.2-7 | buster | source scalapack | 2.1.0-4 | bullseye | source scalapack | 2.1.0-4 | bookworm | source scalapack | 2.1.0-4 | sid | source scalapack-doc | 1.5-10 | squeeze | source, all scalapack-doc | 1.5-10 | wheezy | source, all scalapack-doc | 1.5-10 | jessie | source, all scalapack-doc | 1.5-11 | stretch | source, all scalapack-doc | 1.5-11 | buster | source, all scalapack-doc | 1.5-11 | bullseye | source, all scalapack-doc | 1.5-11 | sid | source, all Actually, the scalapack history already begins with the scalapack (1.6-1) upload in 1999 ... which happened at the same time as the initial scalapack-doc upload (1.5-1). @scalapack maintainers: how useful is this outdated 1.5 -doc package for scalapack 2.1? Andreas
Bug#997271: marked as done (xnnpack: FTBFS: intrinsics-polyfill.h:27:6: error: conflicting types for ‘_mm_storeu_si32’; have ‘void(const void *, __m128i)’)
Your message dated Tue, 11 Jan 2022 10:21:39 +
with message-id
and subject line Bug#997271: fixed in xnnpack 0.0~git20201221.e1ffe15-2.1
has caused the Debian Bug report #997271,
regarding xnnpack: FTBFS: intrinsics-polyfill.h:27:6: error: conflicting types
for ‘_mm_storeu_si32’; have ‘void(const void *, __m128i)’
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.)
--
997271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xnnpack
Version: 0.0~git20201221.e1ffe15-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/cc -DXNNPACK_EXPORTS -DXNN_ENABLE_ASSEMBLY=1 -DXNN_ENABLE_MEMOPT=1
> -DXNN_ENABLE_SPARSE=1 -DXNN_LOG_LEVEL=0 -I"/<>/include"
> -I"/<>/src" -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -fPIC -Wno-psabi -std=gnu99 -msse -O2 -MD -MT
> CMakeFiles/XNNPACK.dir/src/f32-vbinary/gen/vadd-minmax-sse-x4.c.o -MF
> CMakeFiles/XNNPACK.dir/src/f32-vbinary/gen/vadd-minmax-sse-x4.c.o.d -o
> CMakeFiles/XNNPACK.dir/src/f32-vbinary/gen/vadd-minmax-sse-x4.c.o -c
> '/<>/src/f32-vbinary/gen/vadd-minmax-sse-x4.c'
> In file included from
> /<>/src/f32-vbinary/gen/vadd-minmax-sse-x4.c:15:
> /<>/src/xnnpack/intrinsics-polyfill.h:27:6: error: conflicting
> types for ‘_mm_storeu_si32’; have ‘void(const void *, __m128i)’
>27 | void _mm_storeu_si32(const void* address, __m128i v) {
> | ^~~
> In file included from
> /usr/lib/gcc/x86_64-linux-gnu/11/include/xmmintrin.h:1316,
> from
> /<>/src/f32-vbinary/gen/vadd-minmax-sse-x4.c:12:
> /usr/lib/gcc/x86_64-linux-gnu/11/include/emmintrin.h:756:1: note: previous
> definition of ‘_mm_storeu_si32’ with type ‘void(void *, __m128i)’
> 756 | _mm_storeu_si32 (void *__P, __m128i __B)
> | ^~~
> [622/1642] /usr/bin/cc -DXNNPACK_EXPORTS -DXNN_ENABLE_ASSEMBLY=1
> -DXNN_ENABLE_MEMOPT=1 -DXNN_ENABLE_SPARSE=1 -DXNN_LOG_LEVEL=0
> -I"/<>/include" -I"/<>/src" -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wno-psabi
> -std=gnu99 -msse -O2 -MD -MT
> CMakeFiles/XNNPACK.dir/src/f32-vbinary/gen/vadd-minmax-sse-x8.c.o -MF
> CMakeFiles/XNNPACK.dir/src/f32-vbinary/gen/vadd-minmax-sse-x8.c.o.d -o
> CMakeFiles/XNNPACK.dir/src/f32-vbinary/gen/vadd-minmax-sse-x8.c.o -c
> '/<>/src/f32-vbinary/gen/vadd-minmax-sse-x8.c'
> FAILED: CMakeFiles/XNNPACK.dir/src/f32-vbinary/gen/vadd-minmax-sse-x8.c.o
> /usr/bin/cc -DXNNPACK_EXPORTS -DXNN_ENABLE_ASSEMBLY=1 -DXNN_ENABLE_MEMOPT=1
> -DXNN_ENABLE_SPARSE=1 -DXNN_LOG_LEVEL=0 -I"/<>/include"
> -I"/<>/src" -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -fPIC -Wno-psabi -std=gnu99 -msse -O2 -MD -MT
> CMakeFiles/XNNPACK.dir/src/f32-vbinary/gen/vadd-minmax-sse-x8.c.o -MF
> CMakeFiles/XNNPACK.dir/src/f32-vbinary/gen/vadd-minmax-sse-x8.c.o.d -o
> CMakeFiles/XNNPACK.dir/src/f32-vbinary/gen/vadd-minmax-sse-x8.c.o -c
> '/<>/src/f32-vbinary/gen/vadd-minmax-sse-x8.c'
> In file included from
> /<>/src/f32-vbinary/gen/vadd-minmax-sse-x8.c:15:
> /<>/src/xnnpack/intrinsics-polyfill.h:27:6: error: conflicting
> types for ‘_mm_storeu_si32’; have ‘void(const void *, __m128i)’
>27 | void _mm_storeu_si32(const void* address, __m128i v) {
> | ^~~
> In file included from
> /usr/lib/gcc/x86_64-linux-gnu/11/include/xmmintrin.h:1316,
> from
> /<>/src/f32-vbinary/gen/vadd-minmax-sse-x8.c:12:
> /usr/lib/gcc/x86_64-linux-gnu/11/include/emmintrin.h:756:1: note: previous
> definition of ‘_mm_storeu_si32’ with type ‘void(void *, __m128i)’
> 756 | _mm_storeu_si32 (void *__P, __m128i __B)
> | ^~~
> [623/1642] /usr/bin/cc -DXNNPACK_EXPORTS -DXNN_ENABLE_ASSEMBLY=1
> -DXNN_ENABLE_MEMOPT=1 -DXNN_ENABLE_SPARSE=1 -DXNN_LOG_LEVEL=0
> -I"/<>/include" -I"/<>/src" -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wno-psabi
> -std=gnu99 -msse -O2 -MD -MT
> CMakeFiles/XNNPACK.dir/src/f32-spmm/gen/16x1-minmax-sse.c.o -MF
> CMakeFiles/XNNPACK.dir/src/f32-spmm/gen/16x1-minmax-sse.c.o.d -o
> CMakeFiles/XNNPACK.dir/src/f32-spmm/gen/16x1-minmax-sse.c.o -c
> '/<>/src/f32-spmm/gen/16x1-minmax-sse.c'
> [624/1642]
Bug#965886: marked as done (xbubble: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 11 Jan 2022 10:21:34 + with message-id and subject line Bug#965886: fixed in xbubble 0.5.11.2-3.5 has caused the Debian Bug report #965886, regarding xbubble: 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.) -- 965886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965886 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xbubble Version: 0.5.11.2-3.4 Severity: normal Usertags: compat-5-6-removal Hi, The package xbubble 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: xbubble Source-Version: 0.5.11.2-3.5 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of xbubble, 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. Adrian Bunk (supplier of updated xbubble 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: Tue, 04 Jan 2022 18:24:24 +0200 Source: xbubble Architecture: source Version: 0.5.11.2-3.5 Distribution: unstable Urgency: low Maintainer: Uwe Hermann Changed-By: Adrian Bunk Closes: 965886 Changes: xbubble (0.5.11.2-3.5) unstable; urgency=low . * Non-maintainer upload. * debian/compat: 5 -> 7. (Closes: #965886) Checksums-Sha1: 236a3a305009ccd51e2489ec579d42b73f6dfd5d 1849 xbubble_0.5.11.2-3.5.dsc 8cef7a055cdd2d5471e568832c7735f566f367f7 6356 xbubble_0.5.11.2-3.5.debian.tar.xz Checksums-Sha256: e74266d4bc5c94a7c73ed157889867760a17978f94045605d7e718297530f9fe 1849 xbubble_0.5.11.2-3.5.dsc 9909c69aac7a8dd28dc2f50349698156a702a5696dc4de625539b4e2a854abf6 6356 xbubble_0.5.11.2-3.5.debian.tar.xz Files: cbdedc97f5cdd3408684803b5a5f619a 1849 games optional xbubble_0.5.11.2-3.5.dsc 7d2e367e6cce8bd275c70f5811bcd851 6356 games optional xbubble_0.5.11.2-3.5.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHUdSEACgkQiNJCh6LY mLHUWRAArcv7Gimk5mzu6aiV6iXy3Vlc6VAwn1ip8LLiqgxyysfXv/ZTQnqLx1Ub UZ82CqeKgI23UrD+M7ULX1u0BqAexjZHUsZrlTBlsIbji3Ydk30Jx4u6Ojn+fOUn d7cntrn4r4ItrtxSju3oyu5+Im2KP1kHCfMiCTa4kNLaHO+oM6JaYpOu3A6mr0m+ B1mT1ncbC8KwevLeJb5QA7YEpjalygte4n+EqCJA1JcOZ0DcM0mpA6qQ4xxmDd5p PbK8WLYwgZNlS3w2XAKSVnuWbDJ96s0rj4NOcrPvQ0AX8z3N3k/KDieOAKykLTQL 1f2WQG3eu4HVbuqUCJ95Vw82DNuYBYXh2INEclAGYDAd8kuMSHU+EOepagbqnq+X jPHF9c0WWLNcsQ77WIp+1Tg1Q8evGkj/hAcsG6i969MmASJvvzZMGMS6LBuM6g9M 9Bf/M68+Ro8azbrFB/wHWADAM/UKRhAuPC1hvVEqxwvIY5kjbG8zKFrn3h+QHKtx JaKXfOkK7Bds4Me1Q1NSXrLLlJKWmk42WIdSlbi4H0AgwsrY08Wl3GNGrvNCrJU0 ghA5oDfHuo+bdgKIflSWeC4AyzeYHMoALue8V7p+GpZG8WKDN7IjDCbr6mjmXQL8 +w5F5Jk5+hrvlMyskjLaOdqX1z4gI6txjC2xsM7aqPKRTtKbhV4= =M2dH -END PGP SIGNATURE End Message ---
Bug#965778: marked as done (pixelize: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 11 Jan 2022 10:21:11 + with message-id and subject line Bug#965778: fixed in pixelize 1.0.0-1.1 has caused the Debian Bug report #965778, regarding pixelize: 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.) -- 965778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pixelize Version: 1.0.0-1 Severity: normal Usertags: compat-5-6-removal Hi, The package pixelize 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: pixelize Source-Version: 1.0.0-1.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of pixelize, 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. Adrian Bunk (supplier of updated pixelize 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: Tue, 04 Jan 2022 18:05:03 +0200 Source: pixelize Architecture: source Version: 1.0.0-1.1 Distribution: unstable Urgency: low Maintainer: Uwe Hermann Changed-By: Adrian Bunk Closes: 965778 Changes: pixelize (1.0.0-1.1) unstable; urgency=low . * Non-maintainer upload. * debian/compat: 5 -> 7. (Closes: #965778) Checksums-Sha1: 5acda5325d0aab23fb1c17c4eca667844872393f 1704 pixelize_1.0.0-1.1.dsc c98c7a81e8f35c77ba4e9416362fa180a86397e7 5244 pixelize_1.0.0-1.1.diff.gz Checksums-Sha256: 5d1daef0a5759573d9203c0e5e437bb9052835045183edffa2c5d70b1dd8e466 1704 pixelize_1.0.0-1.1.dsc 86d26640dd6091ab143591cce796c1f53f1a296043b56f25e2cea9197a08f779 5244 pixelize_1.0.0-1.1.diff.gz Files: 37e2dc92aac2be22886cc0f1fec4a3b6 1704 graphics optional pixelize_1.0.0-1.1.dsc 6d1e4bdd0ef5e5ffbce704fa3e2c3d09 5244 graphics optional pixelize_1.0.0-1.1.diff.gz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHUcHYACgkQiNJCh6LY mLGozA/+OD7sgvb7gCqWpfb+SIA8wCmCcb9tDmBjZB7HrjgxcmohGRGXiWmb7pTd AmDkzaWzoSDPxxh+LX5sODqNBqiIKHIyeAgNWWhonjiA6iBd/CCUHhEQj44RJITT cdABeuQxzGpve9XQ7MoLskdWe+XjOPxfcsXVdjTXjg9988PDv9v0j17qfsB/vsR6 jctwVioJBvCo/E5415BXq0UExkPxDemjf6NmFPf60Fl+wXCUdk+H8Q4GzhEkjZ+W iz23huogYbTMimB8lAJOJyvynU0LquuPuyqsXR+tx6ZRQP25y4lV4aahGGDTn5/8 INERh0lwiu705kNDKbM23lLNkpuEvmGhs4HVOIVjTEh1tNIK4XxvhmJvZW/Oxat4 wGYWIXVbcZdXrYwzlMOMRjLa3Jjz4+EzoLj9JVZ3osRBCne8C49++N/QAd9kIEyg MW0rnU7B+kE/6mwSBMdOIPFPcjaYbxioSV2uewKGtJgO/+HWQ7WA2W7RsyKGIQps ttO/GKVfI8hYZwt/+qlEzKPL80jvHhwzSeurBl6bro+COEly/AODmDwppImUjvwk /SiiK31T0o7h2TXg03uHyTjoR6CxYqPf43nrA9E40r7YYqrZLafCctThZp/KcVd7 xrItJ54da6ijU8ejDYN7+urYWHfZPJSYBHCwM9I6zlBybJYF7zY= =Yk4W -END PGP SIGNATURE End Message ---
Bug#965777: marked as done (pixbros: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 11 Jan 2022 10:21:06 + with message-id and subject line Bug#965777: fixed in pixbros 0.6.3+dfsg-0.2 has caused the Debian Bug report #965777, regarding pixbros: 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.) -- 965777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965777 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pixbros Version: 0.6.3+dfsg-0.1 Severity: normal Usertags: compat-5-6-removal Hi, The package pixbros 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: pixbros Source-Version: 0.6.3+dfsg-0.2 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of pixbros, 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. Adrian Bunk (supplier of updated pixbros 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: Tue, 04 Jan 2022 15:59:16 +0200 Source: pixbros Architecture: source Version: 0.6.3+dfsg-0.2 Distribution: unstable Urgency: low Maintainer: Debian Games Team Changed-By: Adrian Bunk Closes: 965777 Changes: pixbros (0.6.3+dfsg-0.2) unstable; urgency=low . * Non-maintainer upload. * debian/compat: 5 -> 7. (Closes: #965777) Checksums-Sha1: 19f3c9ae45eb142aafbcd6b0c4973d0be7ea8709 2159 pixbros_0.6.3+dfsg-0.2.dsc 1001a90b365208d460ee29fdca44bfaeb36f6246 7990 pixbros_0.6.3+dfsg-0.2.diff.gz Checksums-Sha256: f4fb677b95b521421a38f9ee4dda7c9441995bb6b5cf817a09a7ff2d93206e5f 2159 pixbros_0.6.3+dfsg-0.2.dsc 043c037ca9a841d5e5451c49b998bf82b832f2ac0fa6e330ed7b28f258bde658 7990 pixbros_0.6.3+dfsg-0.2.diff.gz Files: b98adf10f92886fbd07ba008b8c035ec 2159 games optional pixbros_0.6.3+dfsg-0.2.dsc 3688ba9fd700c17fd79f3642c3c6ae2a 7990 games optional pixbros_0.6.3+dfsg-0.2.diff.gz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHUU2QACgkQiNJCh6LY mLEx+hAAwuMfzkRjssIIr0ucJQmQIYkEFgTVpt+Qs9SDqJakj2vQWz+r5aVcxvXv drJGofNNOE7gLCYH7E+lIHMqDd7JFbaxvqkxgketFo5gqN7P2EsaZYomVz95hH+B 1cbAbTVAXqME0sLV2GjpNvvxdhC7u0fuPTDLaMs7nX8zi0joFTYsrBOjwyirZ8ym +pCkghUm5kvRrvKytMhHsb4MlrbDA8OpVUyj49hciTIsXLVGEqJsC/NfMh5Oocok SIYh/CfWQT6VI+yotwkwuhw7SEFzcIRLIBJqSi9aPc1MPGq80nc8jPQ6nP/3PItd pGlEwDvgiddNrI3L0fN5Li2su0u1MilplcorulMDURZoWOtj6FWeLMMr74JxAPfA qs2HgSZaTZKV+xwH3+6R9SdjBpzuT1Mkf8LXF+TQ8PCIJiumtJIbpgSI/LGaCgo6 0b3Ui5j3rkz1LNLKH0YaJKVCmTJymgWCCat9f3n3a9Y61iF8AXJCoEUd9zDQeQmu kgKla8y1b9ViN8VniSb/wCfDiqwWHT4n3sRl4d0CmRS+tVQqp4/TpU/+QNnE+jZZ XQwHp9jHCqOJr4bToSYYVePoWaaA/8L3DIauW6MJ861aeDXUjiaWPzf9L/xmZehR K+KcZqFLy7D6eDjw0KWiYmFZA2LJwiUUa6VMp1BRQ1s9MOuJEe8= =6vbs -END PGP SIGNATURE End Message ---
Bug#965775: marked as done (phnxdeco: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 11 Jan 2022 10:20:53 + with message-id and subject line Bug#965775: fixed in phnxdeco 0.33-3.1 has caused the Debian Bug report #965775, regarding phnxdeco: 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.) -- 965775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phnxdeco Version: 0.33-3 Severity: normal Usertags: compat-5-6-removal Hi, The package phnxdeco 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: phnxdeco Source-Version: 0.33-3.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of phnxdeco, 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. Adrian Bunk (supplier of updated phnxdeco 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: Tue, 04 Jan 2022 16:26:07 +0200 Source: phnxdeco Architecture: source Version: 0.33-3.1 Distribution: unstable Urgency: low Maintainer: Uwe Hermann Changed-By: Adrian Bunk Closes: 965775 Changes: phnxdeco (0.33-3.1) unstable; urgency=low . * Non-maintainer upload. * debian/compat: 5 -> 7. (Closes: #965775) Checksums-Sha1: 81b86dce0f5a4273000d9b21dcd1c7a6ffe3b9b7 1673 phnxdeco_0.33-3.1.dsc c1fda1892fa5637ebeab0c88fdb91fdeb46b147e 2647 phnxdeco_0.33-3.1.diff.gz Checksums-Sha256: 264e5bc50b37e5a3f51eb3ba2755669d3055611ef4da32736e98443b37b53824 1673 phnxdeco_0.33-3.1.dsc 287d28c236f34f64af50c81a86f6cd553c88ee965464c9658460f42e17683a11 2647 phnxdeco_0.33-3.1.diff.gz Files: 8477cb9687852ed1154155a985bb9cfe 1673 utils optional phnxdeco_0.33-3.1.dsc 679a2c969f8279f7996aa0b30d86e810 2647 utils optional phnxdeco_0.33-3.1.diff.gz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHUWUIACgkQiNJCh6LY mLEC+Q//VJ49v659eT8MNLEAwZzteeyqQUDR1RkIaAP6Z3VRkVKmqAMFPfMr9wcZ dJshCNoUSISdYpZH7+AIF8qmu/9QsmHcCtl3FaMAGUt3eaw/uf+m54LVjlYmqJCa lelXJrfTkVnWkMkvBUGLgBgrpJi1TZMx5pOBsCB5QQbiy8Y5ICpISgcSHJqBXl3t h6ZmBE9LQDGas8u40WQtmHb9QUynGCFGw8u++42kCMTF32jSYOk2HNbbJYWN1oFN 3Lj8YHfRDM6Bcp+aW0SAZn9M2Hy7aiZGOT99n+YxgIYLgCDD1h4bYuPn74mvf5kF UHJk5r/P4R+hhGRZYPS7x9Woqzut6/eUagdpk4WLckK3yQ3UyztBQhnTCtGmRz3T 8Hu18oaH4UxxhVoGBXwx6F79G1wu45kHtyTKohqtorBBP7T/cLbYTY05FSl2jz0X /+7Wf2dDRBCLFrsoV/bmSJbx/cihI2Ca89aWz8xGOOCv071xlhilGVIQriSmYrwB qZjM2BDtJYrDER4GQZ2X+KuUsWausUwAyIimhQD2eifNmcp/St6OrT7djjthh0Nd QeTVeM/YngKwtDOCHSG4EIBqZPOcwY1hLZ4TXiMmp77Z0QSSlXvi1p+eFdcRAgYl HfKVRIiLzoQDBQqAS0ngJJ092QRcKCNrS81vaqa0H7juBv0rWAE= =x6Yn -END PGP SIGNATURE End Message ---
Bug#965774: marked as done (pidgin-festival: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 11 Jan 2022 10:20:58 + with message-id and subject line Bug#965774: fixed in pidgin-festival 2.4-3.1 has caused the Debian Bug report #965774, regarding pidgin-festival: 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.) -- 965774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pidgin-festival Version: 2.4-3 Severity: normal Usertags: compat-5-6-removal Hi, The package pidgin-festival 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: pidgin-festival Source-Version: 2.4-3.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of pidgin-festival, 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. Adrian Bunk (supplier of updated pidgin-festival 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: Tue, 04 Jan 2022 16:33:01 +0200 Source: pidgin-festival Architecture: source Version: 2.4-3.1 Distribution: unstable Urgency: low Maintainer: Varun Hiremath Changed-By: Adrian Bunk Closes: 965774 Changes: pidgin-festival (2.4-3.1) unstable; urgency=low . * Non-maintainer upload. * debian/compat: 5 -> 7. (Closes: #965774) Checksums-Sha1: 4cf88e002f58cb802031faec8b9aecc7a684be54 1968 pidgin-festival_2.4-3.1.dsc 80271c19d3e5d2d0e6bfc53104f1b498b746753c 4492 pidgin-festival_2.4-3.1.debian.tar.xz Checksums-Sha256: db0b023f96fa8aa48c0570849cf1cf48f7ca5885adbd8712dea6272b51607444 1968 pidgin-festival_2.4-3.1.dsc bdc16989e162cd53c857469f463dba906394727d856f78f2d77f348a1091dc4e 4492 pidgin-festival_2.4-3.1.debian.tar.xz Files: 8a6b6d0f7a2392846638f2b7534a 1968 net optional pidgin-festival_2.4-3.1.dsc 473bfa72d72e2dc8aea4b11cf85f6593 4492 net optional pidgin-festival_2.4-3.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHUWucACgkQiNJCh6LY mLFkLQ/6A9D1GxN/iz3syOL7rlgnR7Hs+vm7AfoOt7boWXcD7VLzTR1G/r0Xj7p6 3t5neX5do5uS7MXuPZJmy/SuQ5kBMJb09Gllc5eOzuBVmO3my6ux6QdUXWPS5y83 C8aH6kYAk+EqIGHAkKRA+8ebAhMJz11lUOl+yXlsgbGo8Y25CMgmt5DQrpK6CTnC DOucZX/V1o2rjJPEI0HGEn5ynu9NzYq8b1qF65rDTk9FKYnkFChC1aT3hmWFN1z/ glRiBBkIhxzCrDweWmC9NaXjWM4S3/awRgm7IeZPEup281yEcT89sFAFVvbWv3SA +N8SE3LTsjyMkFD/DEKqlFCvO05ruhdc7I04XwPDr0RcWnyHSl/DukDK8Il76ulQ v9RSvX1e7/d48ThwqoXgPyb7LGHwt50UohBV5Q0102c1xejHv4rRAN7ZFcMywMBO x7U4P1ViBqc2nLwQu2fau1V0Df23p9lfcEvB7oahCk4m4r+F/h5UTsuCyRwqRtMh nRSrvvbVpZf0wIM27zGLR/k0xneOAilfS5sIcgmKplHZ/Cc2LHcJKDPpUielLUaJ 0GElUZ5OrOGLhizrQt6PANpYK6L2Rj+v4LrdOcGKzcF0FtBfvRFiRBKYLyuydoQg QYoQh4VJdjsaA8M4lsE0a4LE5Lbll+dsAYJp7+roVMOHR1Dacu0= =1BLk -END PGP SIGNATURE End Message ---
Bug#965764: marked as done (paje.app: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 11 Jan 2022 10:20:48 + with message-id and subject line Bug#965764: fixed in paje.app 1.98-1.1 has caused the Debian Bug report #965764, regarding paje.app: 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.) -- 965764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: paje.app Version: 1.98-1 Severity: normal Usertags: compat-5-6-removal Hi, The package paje.app 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: paje.app Source-Version: 1.98-1.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of paje.app, 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. Adrian Bunk (supplier of updated paje.app 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: Tue, 04 Jan 2022 18:27:54 +0200 Source: paje.app Architecture: source Version: 1.98-1.1 Distribution: unstable Urgency: low Maintainer: Vincent Danjean Changed-By: Adrian Bunk Closes: 965764 Changes: paje.app (1.98-1.1) unstable; urgency=low . * Non-maintainer upload. * debian/compat: 5 -> 7. (Closes: #965764) Checksums-Sha1: c58c5eb993905e56ccb2d95efda36dca991da9d6 1825 paje.app_1.98-1.1.dsc ea34a76ee971774749b5629ffbfce53d8750f28c 5760 paje.app_1.98-1.1.debian.tar.xz Checksums-Sha256: b25659ee92befab68346d58056e2e8b78d76407c49f712899e3b42056d95a112 1825 paje.app_1.98-1.1.dsc 6bd0b77fe12e6014c565ec00e377b63a5174baa2975fa2c368803aa42b84bd4d 5760 paje.app_1.98-1.1.debian.tar.xz Files: 5517423b8801dcda8e6e83bdae9edc60 1825 science optional paje.app_1.98-1.1.dsc 1345ccac49f506ef1c114eca94692383 5760 science optional paje.app_1.98-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHUdh8ACgkQiNJCh6LY mLHb5RAAs09uCurLdzthppsn7ude/Xg+4OW8YkNlGPGwkUrAaygwOgskaohRuV8j vYaH7oNsjb4hUDvGbqGIC+bfo5X+S8NtaieS7Wc/20d4CelFhnRJqi64IxVg7wbE WpMW4/rA7p8eb5NyjHK/TFZFVKQmuPYJktjqmVyLf861KILJKl9ex9fv/7HLd7Nf zTgkyAuMLWKmwYeyESFizyaPNFXEq0KBsNbxDUt8Ja9zSUYIFtFy2cJ+E9mtftIm gx4I7Vav5GMLX0ELO496olVjShZm+km1EJmaSZMCocGv71QgECK1CYP7+pfeOGWZ 6SwpKzo7VbExNYR2h0nPLiY5Y8TC/Sz1TBiTI0306lB7TH3bEeR7Xf7fb+zJiSBg +t5xlS7oxYeU8ZNGtdB1b3v4SFxslyKRzD9dfRiHJKJL5A97uI73dNEt6bEbTyft K2pWFG8aYnoFMH4PLCPnJly+S9Xc5KmktsHWHai5wj9Ss9LzTi/lLNHW24JkW0oD 4N+tjEt4KEDkRZeEMB+G+AyOyN4UYXivozIkODSsqpUxhJuk8TYe6gPKXgNGg2Uj jQ3nEbXwznawfwgiYmET8H8MnZsXT5GRXsGTjgFNzyXghhbPx6bWH3kz663ipSVs wH3RXq2ryoQIRRNAjiIciVZbwwQVa5HUXKF37ffemIMw5AHLfjE= =p/gC -END PGP SIGNATURE End Message ---
Bug#965708: marked as done (m16c-flash: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 11 Jan 2022 10:20:19 + with message-id and subject line Bug#965708: fixed in m16c-flash 0.1-1.2 has caused the Debian Bug report #965708, regarding m16c-flash: 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.) -- 965708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: m16c-flash Version: 0.1-1.1 Severity: normal Usertags: compat-5-6-removal Hi, The package m16c-flash 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: m16c-flash Source-Version: 0.1-1.2 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of m16c-flash, 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. Adrian Bunk (supplier of updated m16c-flash 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: Tue, 04 Jan 2022 16:08:08 +0200 Source: m16c-flash Architecture: source Version: 0.1-1.2 Distribution: unstable Urgency: medium Maintainer: Uwe Hermann Changed-By: Adrian Bunk Closes: 965708 Changes: m16c-flash (0.1-1.2) unstable; urgency=medium . * Non-maintainer upload. * debian/compat: 5 -> 7. (Closes: #965708) Checksums-Sha1: f40172f121988ed1e9ac637e55826bf4ad68d181 1652 m16c-flash_0.1-1.2.dsc c344a6bf20e6c342a79ecbb366ca788da627dcfa 1985 m16c-flash_0.1-1.2.diff.gz Checksums-Sha256: 5671d5572b56ffd3157cb93c3a916c83638251ad5029317346ad85753a5c0024 1652 m16c-flash_0.1-1.2.dsc 323fd74bcab278e57a7c23b893f7af9f41d2cecc00c29684ea96d7750a7867d8 1985 m16c-flash_0.1-1.2.diff.gz Files: 177504e62126d89600db3bd079739bad 1652 electronics optional m16c-flash_0.1-1.2.dsc a25526756ee660b55f3dfdb8816372d2 1985 electronics optional m16c-flash_0.1-1.2.diff.gz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHUVSkACgkQiNJCh6LY mLEkeQ/+LhlnINjv7VHprKqzU6YLMOQqwYf294BfcFrYjGx9K/Nmyg7267tzeMWp 5dEyni/WmRjVhbhCA+6SocPK4rc/1sbgRotrx02gNFZWBU1U3aOEsRb9kwdEH91b Lhw/cDzNkt5Rsab7fTBo9j3aAbqjBJ40o14jt9AjgMxWWPH7nNJ7tVZ8N60ZdX6W O8FaGIhFFoSjq2Uyb7XfwS+VOW/B4qqvWBHlDUP3eNZunn94zb4YgbAw+GIsdIEU WRdhmb9zbqXmJouuKeXQ+EshzkQQAgrOUDqQoAiXhqlvxcnLAtWKEOExz3307ihn k1g7qLWxVi4Ivv44Xhvj4jBAeNu2DljI1ATYfnVvOO6T/sw/3rXQrjz7PI9RET17 Hwqq4de4gmFdMzmzV1zKRwxnZ2jtDM+G3NrDQE5UOjQFp7jm++8kfKnUSj4KguO1 CiClKHGdCu3wBcVpKmTi7REDACC3EHy3nhC+tn/eIw711tDb+QubnWsAIavbT6Fw ZC6qewtRWkN1VP2IbhxpA3gPFpYllEr9AC/oZFFKG2JJ1UaBtSmUYlklGdRZvoH+ GcGSBXTRw1htY2/oc47lmbLiKUOLOh3NU5PxT0YKz+u0LdQ7pbx0whIO6LDPd50V a+lvR2AILsBoT8J8gzpzn1g3Pg8XnUIlg/RBCuStMGB3ygF47bU= =2KEo -END PGP SIGNATURE End Message ---
Bug#965437: marked as done (bfm: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 11 Jan 2022 10:19:05 + with message-id and subject line Bug#965437: fixed in bfm 0.6.4-6.1 has caused the Debian Bug report #965437, regarding bfm: 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.) -- 965437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965437 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bfm Version: 0.6.4-6 Severity: normal Usertags: compat-5-6-removal Hi, The package bfm 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: bfm Source-Version: 0.6.4-6.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of bfm, 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. Adrian Bunk (supplier of updated bfm 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: Tue, 04 Jan 2022 17:30:21 +0200 Source: bfm Architecture: source Version: 0.6.4-6.1 Distribution: unstable Urgency: low Maintainer: Mika Matsuzaki Changed-By: Adrian Bunk Closes: 965437 Changes: bfm (0.6.4-6.1) unstable; urgency=low . * Non-maintainer upload. * debian/compat: 5 -> 7. (Closes: #965437) Checksums-Sha1: c9abb2678049ecb19fd3b2fb31a2dc6092c3c39c 1802 bfm_0.6.4-6.1.dsc 02a7823f34a1c8a4a3282458278e00031664e05e 5684 bfm_0.6.4-6.1.debian.tar.xz Checksums-Sha256: f3e3854cec8daa0ce4c25374db87566d0b771479580b73e19a0b4f7b4633620c 1802 bfm_0.6.4-6.1.dsc 2bde3323f8c19d85d8310465392208244ff819b6458776caaa8d32bf93fb2a29 5684 bfm_0.6.4-6.1.debian.tar.xz Files: 96abeed4dbbd0237aff5c18382d1c9c0 1802 x11 optional bfm_0.6.4-6.1.dsc 9d76e63cc3bd193fbcea42cb7f0ff85a 5684 x11 optional bfm_0.6.4-6.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHUaHYACgkQiNJCh6LY mLF5FQ//WcwLrW9cP6rSQKrNAHr3mCNeDVa64r5MiX9ECjHcvARZy3f3CqBvr6EK QPl+2fvh15b7gvGpb7j2Y5tscOXZovhoxtpTf1C5fX5itDjdaCrhQOI88iuqd4k5 xpQcMyHVmC7fyoAEb+6caGJ2hHGy/Cs20BppgrycgO9NWhx17OTJn+1khnFwVyl0 tj4wFO59OlPopBSyhjsVaeW8Qz+QVovScd7d82a0deYlkF5bytHxoQOSkXwlnR00 ZA6xzy76d6MIYCs4z0nPKxp7KBTVIyjpuJXZJEdwltrGiAeEhFeuVA/XTSmMpXGD 6ibhyjUm4eD4CWC2MxHFZvAe/pb0bG9auevR6c/AK2ftJcZqvIEQfKeMPGDjJ3zu x4F/U2JpMiGD1Wn0SzDN++l0No+xtOKVPXM35IAizHn++J4aqByCf36Zknw75Qpx goH2hkCH7DwKQRhhW8vedKhK5AVLtXpdsv9sjWJr+IaqzRH7JbvTxoQtb8PKzE0A lWJZISOOVBpX8lv2F//evhgyvMJD9c2Mndu2b1iZI8RTZ/VX1dhZVoU7G8f+wENa B7INvQFrMoDw5LZOzuMk1XCbqXfVCT+qB+O9+gDZVIP4Zoc0gFIE4DwNCqn22Czg kYM29wOP50T683GholMKasKR8sTTIDf/J9MxJg5HRarI9iB74Ec= =17vI -END PGP SIGNATURE End Message ---
Bug#965427: marked as done (awardeco: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 11 Jan 2022 10:19:00 + with message-id and subject line Bug#965427: fixed in awardeco 0.2-3.2 has caused the Debian Bug report #965427, regarding awardeco: 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.) -- 965427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965427 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: awardeco Version: 0.2-3.1 Severity: normal Usertags: compat-5-6-removal Hi, The package awardeco 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: awardeco Source-Version: 0.2-3.2 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of awardeco, 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. Adrian Bunk (supplier of updated awardeco 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: Tue, 04 Jan 2022 17:25:14 +0200 Source: awardeco Architecture: source Version: 0.2-3.2 Distribution: unstable Urgency: low Maintainer: Uwe Hermann Changed-By: Adrian Bunk Closes: 965427 Changes: awardeco (0.2-3.2) unstable; urgency=low . * Non-maintainer upload. * debian/compat: 5 -> 7. (Closes: #965427) Checksums-Sha1: d95481927e3bef83c6c79ef94efcf1b8abdfc2b1 1666 awardeco_0.2-3.2.dsc cb52697cf239878b4ed365c76829eec03e84a70e 3443 awardeco_0.2-3.2.diff.gz Checksums-Sha256: 91977b46f8766d8d39884308a265ae382c92b3a2100a1cf0f64a8872cbaf 1666 awardeco_0.2-3.2.dsc b6f34ded62c7dfd09ca08f412e91df7375ff7e67f266c408e8ca69987583f17b 3443 awardeco_0.2-3.2.diff.gz Files: 0b9b0ba92cac09662aa0c81db4753612 1666 utils optional awardeco_0.2-3.2.dsc 07ada55faec6bbde6df1e93a28a908f3 3443 utils optional awardeco_0.2-3.2.diff.gz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHUZyIACgkQiNJCh6LY mLFUfg/+K+FTFfRO8TBof9QbS7wOT2S54tZgYH/yZn27BfBYJ4GZ0vv0byWmRkh0 7uT8on+nUWkzPXyMpqRfPLpf2UyZ85JnYKz0uqMzKMxGs+64q/XSh4lcBtPu8j5V w3BbI6+mNvOGvTmAEV0dPTsKALat9O1GsW+y1FNag6/vpH3Jn8BMlxXPyiDIaWE1 7yw3gZiTc4h5ivJzoZcHV6jWZJS8nAxJIMAepIKKpi+psHxJh8j4vTPloeh3Vgho 2Q+A73DztOo/yUO6ThmIHKiiCnCtZIJwcXstfdS3DF/wUw7z3TRtUkPFXjAnE0ia iNpPMxVp8KV3QyoQLxy6RGSCLfgwUHEE9VLXpOWDeGf7wPl0GBWCijOdpTHbKNTW fPoxQu4qoCUkZzJcx1KEWuL3O3NaDwhjqeE+Aqn7KKAPjxFUG9XWIoxQC4//H2cx 98s4wYj0+YD6OrUCrzlBgTq0TNUNrjpKpoREgpX61dYjMPpGgQFVtdrnBPEZIMQP hKu4DB5nOoNBEwSdNcqhZshKR5/HEMMqN81JzDLCvnG9v06suje87P3Ckq59Q1oY 2FxV3BwQLVPgVO8zzrUph4dNSnQpPMqUlVx3CQ5dtCX4XJGIikhBSBykh8X9rfA+ H8pFqnotpiSscnpsoQTrygnuxiz1E7gzPWaHVYJZ3LeUb2Q2LSE= =/jtI -END PGP SIGNATURE End Message ---
Bug#965412: marked as done (and: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 11 Jan 2022 10:18:46 + with message-id and subject line Bug#965412: fixed in and 1.2.2-4.2 has caused the Debian Bug report #965412, regarding and: 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.) -- 965412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965412 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: and Version: 1.2.2-4.1 Severity: normal Usertags: compat-5-6-removal Hi, The package and 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: and Source-Version: 1.2.2-4.2 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of and, 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. Adrian Bunk (supplier of updated and 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: Tue, 04 Jan 2022 16:11:47 +0200 Source: and Architecture: source Version: 1.2.2-4.2 Distribution: unstable Urgency: low Maintainer: Dario Minnucci Changed-By: Adrian Bunk Closes: 965412 Changes: and (1.2.2-4.2) unstable; urgency=low . * Non-maintainer upload. * debian/compat: 5 -> 7. (Closes: #965412) Checksums-Sha1: 2ea2038cc7495ec4989398b8d0d89c0987f9b482 1666 and_1.2.2-4.2.dsc d7c4dec281406787d7ce33254d2f353b8e02ce0d 11184 and_1.2.2-4.2.debian.tar.xz Checksums-Sha256: 975f5d893b8a8b464eecd2b3c33527baba0de89ef0a1a69c19e8149ff2806b25 1666 and_1.2.2-4.2.dsc cec4cc01e2e776ebfcc725638935dae9a2f583fbcfd3af2169d729629266a90c 11184 and_1.2.2-4.2.debian.tar.xz Files: 4128df812c39149ef49dd56995c17dd5 1666 misc extra and_1.2.2-4.2.dsc 39033ae5282057d0428c4d468029 11184 misc extra and_1.2.2-4.2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHUVeoACgkQiNJCh6LY mLEhHRAAwu1MlIJVbUUDboHD6ys9cNOeycc3wrOPPOe0AtcF9WnkHfykXNXsOXbu 6h7h7Er+IpcHZI1FwNn6VA3Q/jaCmITnThMnDDcovS4IcD6V+uN+VZU7G0mTHhCF ecm8Opy2PN5h2MeGDtW6fba7lU1dmL/DPKvWkglbA8xpkgJNlFrp8Ky9LZcHL9pu JhAYL0EyFfX7Qgdv/gv2TaYje3t3p5pIBqhznjcW+pbYRHksydTvf5thsIKebFIW ysWyJIk9cG5jXKblLHKSmCqQ55JHGyQK6dag7EYxIEdHibMTeRgObe/nd+F+8Q3J RWEkZyHWnmqZDFpJFdZ+ktrF6HPDpg9gpwZDJ8KjGSKAXWet/OEiKcXn9z3dHWtG hxUY1q9V3yv8scKAR09XRxvafbmJ9wt9o1vHp8LNy8RmHk64b5ftoXDhWZ86QF9+ Lc0PY9L4gyJoOdRX3Yq7aoiGrmS4/wdVdLbJcrRtgi2pd6W+kTyvtV5Y+R/QZoKp BhXO1Mzv1KeRGVhCS1l5IIP7hN3pL5DB8ZSQWKSDt50g3l6ubKw96RrqPW1f1yWc IkCfgtvEeqxirz0WitPlBq59U8kVt901qjTiZsN2+RBbqiI8T/Xm9izsMPuL/bB5 OF5wzY/txvPX06EBw3zZU8I99qRwwV6R47SEPSCpCVcLKOOQ2oA= =Bn/6 -END PGP SIGNATURE End Message ---
Bug#965426: marked as done (aview: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 11 Jan 2022 10:18:55 + with message-id and subject line Bug#965426: fixed in aview 1.3.0rc1-9.1 has caused the Debian Bug report #965426, regarding aview: 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.) -- 965426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: aview Version: 1.3.0rc1-9 Severity: normal Usertags: compat-5-6-removal Hi, The package aview 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: aview Source-Version: 1.3.0rc1-9.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of aview, 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. Adrian Bunk (supplier of updated aview 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: Tue, 04 Jan 2022 17:19:01 +0200 Source: aview Architecture: source Version: 1.3.0rc1-9.1 Distribution: unstable Urgency: low Maintainer: Uwe Hermann Changed-By: Adrian Bunk Closes: 965426 Changes: aview (1.3.0rc1-9.1) unstable; urgency=low . * Non-maintainer upload. * debian/compat: 5 -> 7. (Closes: #965426) Checksums-Sha1: c4724f98f1af2b7efc6b373e9bbda1a018a1a70f 1716 aview_1.3.0rc1-9.1.dsc f5746d445140490079e5a5bf7ae800697d2b86a1 8868 aview_1.3.0rc1-9.1.diff.gz Checksums-Sha256: 60e728140716a5e7822e805b5cade22e53bc26609c0c09895543551ae57a2f8a 1716 aview_1.3.0rc1-9.1.dsc 53c0d45f9e42bbf2019e6ae8adcff0e4666fe680e49ecf79d841ae665995ffdd 8868 aview_1.3.0rc1-9.1.diff.gz Files: a7204decc9a7cf15f13f00516e05c71b 1716 graphics optional aview_1.3.0rc1-9.1.dsc 89367c5acf07ba0114c85e7902506f32 8868 graphics optional aview_1.3.0rc1-9.1.diff.gz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHUZaQACgkQiNJCh6LY mLFHwRAAhEUz+TzXrDUWmQJpPnA63ezY7+7H9PWTXCsI6Ln9qeAMlDeznMLIizXL YDmuTi7SYSJOXWnoDByFfn0pOWThOj/fpmJsWt+TSzP3rbxMNfBXqhXa5KLCyhml fH2y1IgXUPTByDFqxOYa5npGN4MCCD2moGw+Z1VZ6/y74Ny+95KZ8DLd96rKt9VL yOmhgG8zgYY7OWv4AC8/4aN2P1VHVf2XueX2PSTec2EOnQarDPncCN3VVjbes8Ai CmlvGpbGVtQviUYfgE31kpeswFTyL8oRbQ61ZH5wuCi38QWXWe0B3rDp1h6DdpUz PECIsZ5tCZjRFcjcajlmgqu0VT0uhJ3QQfH7k+Uro6oOqq6hitNsyv/3UcGHtl47 YqIkNoFop+ZKBo+FUKsQv1keLFBJgkk1qUxNQgMZapp2PYcksStF1I8SRWAut7Yk 8LuOjsDf3LAslmLlQRx0FVZKxy8KIPN/bi5Q7s7Nw5TelCB+jgSZLGgK6w3OGCu3 gWjSW0auYm7aZFGCtSat8zkNO1igO7n7z0Zf41VzD0DjR/R07dS2NEyPUk8R+bgI hOka8ITGO/B5vh1QWothxzo3+UG5OTp96bpdislpWpuhiDlOoa4amUPJ0JMfNDA1 1M/MhUBsgRH61On63yd21cjRy8+IHxf8vRID8AwESynRxCP2f28= =aoRD -END PGP SIGNATURE End Message ---
Bug#965411: marked as done (asmix: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 11 Jan 2022 10:18:50 + with message-id and subject line Bug#965411: fixed in asmix 1.5-4.2 has caused the Debian Bug report #965411, regarding asmix: 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.) -- 965411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965411 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: asmix Version: 1.5-4.1 Severity: normal Usertags: compat-5-6-removal Hi, The package asmix 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: asmix Source-Version: 1.5-4.2 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of asmix, 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. Adrian Bunk (supplier of updated asmix 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: Tue, 04 Jan 2022 16:36:13 +0200 Source: asmix Architecture: source Version: 1.5-4.2 Distribution: unstable Urgency: low Maintainer: Varun Hiremath Changed-By: Adrian Bunk Closes: 965411 Changes: asmix (1.5-4.2) unstable; urgency=low . * Non-maintainer upload. * debian/compat: 6 -> 7. (Closes: #965411) Checksums-Sha1: 6f9a6f250b0aaa76de2329249db57b198425bbde 1894 asmix_1.5-4.2.dsc 23b9eba5206277d1e54ee4308434478534c4d504 4170 asmix_1.5-4.2.diff.gz Checksums-Sha256: a2bc0d3eb51729be9fce8dd02e6f0f0bb771edee6a6e31717427fe085628b1d9 1894 asmix_1.5-4.2.dsc 6660c981dd9ac19f74b2e323f285ca93b1aab6be0f15e3c52c72e95a7e86bd6d 4170 asmix_1.5-4.2.diff.gz Files: e246bfdb2e785f2d9863210233bbb652 1894 x11 optional asmix_1.5-4.2.dsc 76c48fd94460cb3bed48f9e6f2f18ba8 4170 x11 optional asmix_1.5-4.2.diff.gz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHUW6IACgkQiNJCh6LY mLEMNw//dUs//FFBjMokOaPO/5cNEpz9ypY47dh+vVAIzTJRPCrMX/2LS4Vw8yIO cWxB+iqNiDc775VH8mGytDeBE932D+MF2wXyxGNeqFRpZ9i836UY/F5dbapyyC2z mNPdCbY2vEsNGfok9Fena0/mYTFZJD7voEVjAyr9YtUABMq5lOPp1oxjYpUdJpTc NBLhcvogG+E7TOWff4W5f/v2nqsr1W6Ma3DtdahITfKy6SgR+faCw+6eZ4/Zdw6L 5QZOoZWpCCbgBRJy4N4bLUiNPgn8BTCRgVi2y9d2CAUmv/NieITRVTQrevbkXyoS 5Iw/UMVr+BxmXmSxkKgZWDXXoWpv1JTjDByeS7/EmrI070Xh7VDhjemk21Gke27r b3hc8OLJBVkfHxES65mzpOoj9zwAEiGQ6eajYmn27mamFYCcvPPXJE5m6VVqjKTo c1AEGmZ4IUklHl+6TPCqFVIZ/gIDAKI66aG+NrPQaM5PvglWHhC8FNBqoE6msfL+ FjIJqSgRfqVr5q46KAhWtc/u6+sl0AfKxSHGyL+zuxHc5coa8EKNBXbaaWMQCJni 5vZapgGPolCLOPjUONcVFS9rglY/fh65QL0SJDALlhhOyepiXV0soguk3VJDQWM2 TRIEzfXFuVbyhTcBlsUw+RwZ4muSELeByyvH98pjGtKLIcN53V0= =I8I9 -END PGP SIGNATURE End Message ---
Bug#965406: marked as done (afuse: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 11 Jan 2022 10:18:36 + with message-id and subject line Bug#965406: fixed in afuse 0.4.1-1.1 has caused the Debian Bug report #965406, regarding afuse: 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.) -- 965406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965406 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: afuse Version: 0.4.1-1 Severity: normal Usertags: compat-5-6-removal Hi, The package afuse 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: afuse Source-Version: 0.4.1-1.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of afuse, 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. Adrian Bunk (supplier of updated afuse 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: Tue, 04 Jan 2022 17:02:06 +0200 Source: afuse Architecture: source Version: 0.4.1-1.1 Distribution: unstable Urgency: low Maintainer: Varun Hiremath Changed-By: Adrian Bunk Closes: 965406 974614 Changes: afuse (0.4.1-1.1) unstable; urgency=low . * Non-maintainer upload. * debian/compat: 6 -> 7. (Closes: #965406) * debian/control: Update Homepage. (Closes: #974614) Checksums-Sha1: aff04ff433d911c5a38cc1a2c19acd4d076f1fd2 1821 afuse_0.4.1-1.1.dsc 550054d253f9fce2c3d4ae20e81fd4bca3373737 3388 afuse_0.4.1-1.1.debian.tar.xz Checksums-Sha256: 324d2e888d16bfa815a516670cfbfc83260c2df0fc1af7e8302eda2382a0fcfd 1821 afuse_0.4.1-1.1.dsc dc8653c1e1b30289808a33d3eebfaa83fd3a597e2f6c2c3275245bc8326efe22 3388 afuse_0.4.1-1.1.debian.tar.xz Files: fecf21055880f17d58ef4bdfd76b8327 1821 utils optional afuse_0.4.1-1.1.dsc eb7ae08bf9423a51d7209fc83fc18960 3388 utils optional afuse_0.4.1-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHUYgoACgkQiNJCh6LY mLH2aBAAtUEk9i2wDV3CR7x0V+qV8ivEVrqTMERt8Yhg1Ii0+WOha5ZwsXIMk/at c6smB5vxE8fHBHLz8Sv5/60bw/qHb4u64BjQjlSO1K1ileLHH/6UDs7rrxwixw2E IxjftT7M6IgznGmNF8gyugcUWdHqzk0HvQAV8MfYYB8uJhoaXDc1Eecf9PJqU6ba iRJ8ZZQ9tE+iPeqYJE60Gn5ncmi6IhRvf8uxvDxNHkG5Pk2YgP9MEQuquluFlPpn Z9xilo5n2EjM3yUz+NCOYOz6zEJ+SWPxU7ZbDidCGSDz1Yk1at3MmXNAj3rZuWjF L+eVDi0X+OSnxAOjiyGqhsniBuZpvM1zQXYqqJtNU0Oc9C9Gw6xNh6pK8MD7IC5Z 3yjcbOMQRuCLj3iolKMf2QIoN/pJkYALKmFdlc+qMD2gGOtAcYULq8gd7yYnoIiT MsaDieEobLpul9f27+lahOGDTwChzHvtWSaDmbcWRlzuK8Gcz2GIRjB4un2HJMjl gkRX9Jv8t6Stf21wh5w2pdV6WSOTxz5y1+s4Qm7jkJh3IM2xNjAwWZREDUjwhDgu qnG/SmR/U7NT5qzceeQzL0KNNwP6QNxEFDDhBIhRxD6Efc529hHMli9EoSVu2EUW 8/xIkwv/Ukc18rpYkFxjkFNB1S0PnGkIu1kTKWgZ9WIgwDbuNqs= =+5Nz -END PGP SIGNATURE End Message ---
Bug#965407: marked as done (amideco: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 11 Jan 2022 10:18:41 + with message-id and subject line Bug#965407: fixed in amideco 0.31e-3.2 has caused the Debian Bug report #965407, regarding amideco: 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.) -- 965407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965407 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: amideco Version: 0.31e-3.1 Severity: normal Usertags: compat-5-6-removal Hi, The package amideco 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: amideco Source-Version: 0.31e-3.2 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of amideco, 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. Adrian Bunk (supplier of updated amideco 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: Tue, 04 Jan 2022 16:18:44 +0200 Source: amideco Architecture: source Version: 0.31e-3.2 Distribution: unstable Urgency: low Maintainer: Uwe Hermann Changed-By: Adrian Bunk Closes: 965407 Changes: amideco (0.31e-3.2) unstable; urgency=low . * Non-maintainer upload. * debian/compat: 5 -> 7. (Closes: #965407) Checksums-Sha1: 5e759baf9ac867ba34a429cd4958fa9eba4711f4 1671 amideco_0.31e-3.2.dsc c17c890268ae9da0a4dc46b5f9fecbbb720c17d7 3521 amideco_0.31e-3.2.diff.gz Checksums-Sha256: b847cb0bb66476565fa4a984d4c5cf98a865e49b84d309497d2539c94592b932 1671 amideco_0.31e-3.2.dsc d6a8bee81cbf02da77d9e02e7f27a8022ab39e65d5fb75675166b65d0b2b7f98 3521 amideco_0.31e-3.2.diff.gz Files: 5aacf83b172d82a2f3ddcf12b137db71 1671 utils optional amideco_0.31e-3.2.dsc d90b156c75ae85e464ba18dc5410b91f 3521 utils optional amideco_0.31e-3.2.diff.gz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHUWK0ACgkQiNJCh6LY mLH0lQ/+MFT5YjqM4OPn8wR1UFH9m3WdvBXdUVUV2ZpfCBQel/+pZE1lEkQxioTf 9df2pxBNeQOSDg0w8wgivDtIvtGuk3IxYc/lqW+iD9VPAoaxxuPZpxiwAEzJ3bzv GCM2e5zGLHlnTZBLjhB7rNbZXZVAMFmMrSHj2j4B8Pnj3nbGtb2kFkiQpmLdRhu3 Xaoni5DOoAzil+SzO8jskYDTYs8gl9NaaQQ93r+YV0sFtdFtvXENsosvSfoL6kcl IPstpI2CmkWcjE2YhV7yjxGwiLy8vZiCLXwT2iSihqh3p3rFDpTTIJbXanyRhwOc JlKvQF16rQYWyCv4PBHFHiAmyGgMsCfRqSzg8EvdP5LSqxTr6iZZZOxvvc9aXDnK OAw80kCi7lpJeoNhBzwyXktHaAZh8VR7bnLnfn8uzdiHm9fRGMoe1BiL7c8iaz+q +4GpI1jk98MnHw1h7tGyS2/yOt73DUjzymkjasSIRydCAyJtSqLQq/LvdQ/5okAc mBVBG0M6K3Z74OlIcRF+S6uuIjcZ3bnu9q2FuNRRRPgonqrPtEJcOSZ980JGCZD0 e5xCIJ6NTh4cMj0jHIg6PdaqOQbzgVa8Ncjy7WmH5nPo1i0R2bFKm9b5TUockMAG u8rVUGP7PZbl+CyIFU83GymKdkGVtJeMVwHtLDdGMU4D8gtPsao= =hOzA -END PGP SIGNATURE End Message ---
Bug#965403: marked as done (aconnectgui: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 11 Jan 2022 10:18:32 + with message-id and subject line Bug#965403: fixed in aconnectgui 0.9.0rc2-1-10.1 has caused the Debian Bug report #965403, regarding aconnectgui: 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.) -- 965403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: aconnectgui Version: 0.9.0rc2-1-10 Severity: normal Usertags: compat-5-6-removal Hi, The package aconnectgui 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: aconnectgui Source-Version: 0.9.0rc2-1-10.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of aconnectgui, 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. Adrian Bunk (supplier of updated aconnectgui 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: Tue, 04 Jan 2022 17:53:11 +0200 Source: aconnectgui Architecture: source Version: 0.9.0rc2-1-10.1 Distribution: unstable Urgency: low Maintainer: Paul Brossier Changed-By: Adrian Bunk Closes: 608651 965403 Changes: aconnectgui (0.9.0rc2-1-10.1) unstable; urgency=low . * Non-maintainer upload. * debian/compat: 5 -> 7. (Closes: #965403) * debian/control: Remove Homepage. (Closes: #608651) * Stop using the obsolete dh-buildinfo. Checksums-Sha1: bf025c9e10c4f08c9b6cf67b1140dc0034306628 1865 aconnectgui_0.9.0rc2-1-10.1.dsc ea3ebe328df6db031ce9a817fc6acb91bf130076 48093 aconnectgui_0.9.0rc2-1-10.1.diff.gz Checksums-Sha256: 30ab49389ef31addc6a50eb42824b8c9e2cf92637f96a7ad64da60fa39556c49 1865 aconnectgui_0.9.0rc2-1-10.1.dsc cf01f60d4a99fd79630d5b5d20cbf354b8e6e18480336614484d9b1f41131f3b 48093 aconnectgui_0.9.0rc2-1-10.1.diff.gz Files: dfebcbb7b76386c68faedd97c3704341 1865 sound optional aconnectgui_0.9.0rc2-1-10.1.dsc 76f45dd11ee6675a4008284b500e331a 48093 sound optional aconnectgui_0.9.0rc2-1-10.1.diff.gz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHUbgEACgkQiNJCh6LY mLHgbA//VToLbNxFfpCp4Onn7l9nedoSZHgeDXDxLgALu4EiNmxXoakh+I1FTPZd IPWaK2K4Y5F5ffavpuV5FxXLMRB5+BApBjOYIfSE0PvaOFRJXQpP5VnjLCNCD+/B layQ166uhLKnGIPIprbqyWOEZkdYf01f2sbY80vMTkwZTXQuQR+RkTTX/l5+p1sW RSkIqNPFTpTCSr5loSc7rN+a+8IHWKfoPbauA9pS+O4IuSwrwmm2+x7+RsKerzW7 OE8LA+sym+ykZBHncfoZbT8P6Z8qGzeK7lFmqzKd5HSN3E60JSBTP3PWXCvjWzZ2 LAlFLGhmlfpqtwsBfnTi1QLODNjMv/Q3vHnshTLrAZe2Wo8mosYu/La+yuFEXaUX pncMBxzMzucSBBu4eClk46+EKR34SjLfPf8kRULuVZSPqqQIUplRLV0O1cBRPnuP CGm2Z/jvaFEiVzQw0QouWeZ8newg5CEwuAytxkWb6GRWn/rj7Wfb9QY4gESJ9ezI eCTKizePOq5xJGlCN/64wQVIkN4Z3/mwG718OKmmTkV3uFMvWVEayjoupiEmQVYG FgGiA03oviKlRyGkAqvPqSKGMhBWG3OeZo/9lOIkl+eARjGlR2Ox+Bl5PiMUhNqN ZAJNQ3tK7EHm+TH2xcsqHi3ZlEq2Y4ptkZkPmuCfMesWxT5utKU= =pCJg -END PGP SIGNATURE End Message ---
Bug#1002132: marked as done (lightdm: FTBFS: libsystem.c:333:1: error: no previous prototype for ‘__xstat’ [-Werror=missing-prototypes])
Your message dated Tue, 11 Jan 2022 10:20:07 + with message-id and subject line Bug#1002132: fixed in lightdm 1.26.0-8 has caused the Debian Bug report #1002132, regarding lightdm: FTBFS: libsystem.c:333:1: error: no previous prototype for ‘__xstat’ [-Werror=missing-prototypes] 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.) -- 1002132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002132 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lightdm Version: 1.26.0-7 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): > /bin/bash ../../libtool --tag=CC --mode=link gcc -Wall > -Wstrict-prototypes -Wnested-externs > -Werror=missing-prototypes > -Werror=implicit-function-declaration -Werror=pointer-arith > -Werror=init-self -Werror=format-security > -Werror=format=2 -Werror=missing-include-dirs > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread > -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,-O1 -o > initctl initctl-initctl.o initctl-status.o -lglib-2.0 -lgio-2.0 -lgobject-2.0 > -lglib-2.0 > libsystem.c:333:1: error: no previous prototype for ‘__xstat’ > [-Werror=missing-prototypes] > 333 | __xstat (int version, const char *path, struct stat *buf) > | ^~~ > libsystem.c:342:1: error: no previous prototype for ‘__xstat64’ > [-Werror=missing-prototypes] > 342 | __xstat64 (int version, const char *path, struct stat64 *buf) > | ^ > libsystem.c:351:1: error: no previous prototype for ‘__fxstatat’ > [-Werror=missing-prototypes] > 351 | __fxstatat(int ver, int dirfd, const char *pathname, struct stat > *buf, int flags) > | ^~ > libsystem.c:360:1: error: no previous prototype for ‘__fxstatat64’ > [-Werror=missing-prototypes] > 360 | __fxstatat64(int ver, int dirfd, const char *pathname, struct stat64 > *buf, int flags) > | ^~~~ > libtool: link: gcc -Wall -Wstrict-prototypes -Wnested-externs > -Werror=missing-prototypes -Werror=implicit-function-declaration > -Werror=pointer-arith -Werror=init-self -Werror=format-security > -Werror=format=2 -Werror=missing-include-dirs -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread > -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed > -Wl,-O1 -o initctl initctl-initctl.o initctl-status.o -lgio-2.0 > -lgobject-2.0 -lglib-2.0 -pthread > /bin/bash ../../libtool --tag=CC --mode=link gcc -Wall > -Wstrict-prototypes -Wnested-externs > -Werror=missing-prototypes > -Werror=implicit-function-declaration -Werror=pointer-arith > -Werror=init-self -Werror=format-security > -Werror=format=2 -Werror=missing-include-dirs > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread > -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,-O1 -o > plymouth plymouth-plymouth.o plymouth-status.o -lglib-2.0 -lgio-2.0 > -lgobject-2.0 -lglib-2.0 > libtool: link: gcc -Wall -Wstrict-prototypes -Wnested-externs > -Werror=missing-prototypes -Werror=implicit-function-declaration > -Werror=pointer-arith -Werror=init-self -Werror=format-security > -Werror=format=2 -Werror=missing-include-dirs -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread > -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g
Processed: reassign 1003507 to wnpp, tagging 1002758
Processing commands for cont...@bugs.debian.org:
> reassign 1003507 wnpp
Bug #1003507 [wordpress-plugin-http-authentication] weblog manager (HTTP
Authentication Plugin) - From short description on control
Warning: Unknown package 'wordpress-plugin-http-authentication'
Bug reassigned from package 'wordpress-plugin-http-authentication' to 'wnpp'.
Ignoring request to alter found versions of bug #1003507 to the same values
previously set
Ignoring request to alter fixed versions of bug #1003507 to the same values
previously set
> tags 1002758 - bookworm sid
Bug #1002758 {Done: Jonas Smedegaard } [src:emscripten]
emscripten: FTBFS: FAIL: test_pthread_abort (test_core.wasm3)
Removed tag(s) bookworm and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1002758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002758
1003507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1002767: marked as done (lua-system: FTBFS: dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple test returned exit code 2)
Your message dated Tue, 11 Jan 2022 09:49:32 + with message-id and subject line Bug#1002767: fixed in lua-system 0.2.1-4 has caused the Debian Bug report #1002767, regarding lua-system: FTBFS: dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple test returned exit code 2 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.) -- 1002767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lua-system Version: 0.2.1-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211228 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem=lua --with lua >dh_update_autotools_config -O--buildsystem=lua >dh_autoreconf -O--buildsystem=lua >dh_auto_configure -O--buildsystem=lua > make --no-print-directory -f > /usr/share/dh-lua/make/dh-lua.Makefile.multiple configure > > Making target configure for debian/lua5.1.dh-lua.conf > # .install > Filling in debian/lua-system.install using > /usr/share/dh-lua/template/lib.install.in > Adding new line: usr/lib/x86_64-linux-gnu/lua/5.1/system/core.so > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.1-system.so.* > Adding new line: usr/share/lua/5.1/system/init.lua > Filling in debian/lua-system-dev.install using > /usr/share/dh-lua/template/dev.install.in > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.1-system.so > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.1-system.a > Adding new line: usr/lib/x86_64-linux-gnu/pkgconfig/lua5.1-system.pc > Adding new line: usr/include/lua5.1/lua-system.h > # lua_versions > Filling in debian/lua_versions > Adding new line: 5.1 > Target configure made > > > Making target configure for debian/lua5.2.dh-lua.conf > # .install > Filling in debian/lua-system.install using > /usr/share/dh-lua/template/lib.install.in > Adding new line: usr/lib/x86_64-linux-gnu/lua/5.2/system/core.so > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.2-system.so.* > Adding new line: usr/share/lua/5.2/system/init.lua > Filling in debian/lua-system-dev.install using > /usr/share/dh-lua/template/dev.install.in > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.2-system.so > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.2-system.a > Adding new line: usr/lib/x86_64-linux-gnu/pkgconfig/lua5.2-system.pc > Adding new line: usr/include/lua5.2/lua-system.h > # lua_versions > Filling in debian/lua_versions > Adding new line: 5.2 > Target configure made > > > Making target configure for debian/lua5.3.dh-lua.conf > # .install > Filling in debian/lua-system.install using > /usr/share/dh-lua/template/lib.install.in > Adding new line: usr/lib/x86_64-linux-gnu/lua/5.3/system/core.so > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.3-system.so.* > Adding new line: usr/share/lua/5.3/system/init.lua > Filling in debian/lua-system-dev.install using > /usr/share/dh-lua/template/dev.install.in > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.3-system.so > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.3-system.a > Adding new line: usr/lib/x86_64-linux-gnu/pkgconfig/lua5.3-system.pc > Adding new line: usr/include/lua5.3/lua-system.h > # lua_versions > Filling in debian/lua_versions > Adding new line: 5.3 > Target configure made > > > Making target configure for debian/lua5.4.dh-lua.conf > # .install > Filling in debian/lua-system.install using > /usr/share/dh-lua/template/lib.install.in > Adding new line: usr/lib/x86_64-linux-gnu/lua/5.4/system/core.so > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.4-system.so.* > Adding new line: usr/share/lua/5.4/system/init.lua > Filling in debian/lua-system-dev.install using > /usr/share/dh-lua/template/dev.install.in > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.4-system.so > Adding new line: usr/lib/x86_64-linux-gnu/liblua5.4-system.a > Adding new line: usr/lib/x86_64-linux-gnu/pkgconfig/lua5.4-system.pc > Adding new line: usr/include/lua5.4/lua-system.h > # lua_versions > Filling in debian/lua_versions > Adding new line: 5.4 > Target configure made > >dh_auto_build -O--buildsystem=lua > make --no-print-directory -f > /usr/share/dh-lua/make/dh-lua.Makefile.multiple build > > Making target build for debian/lua5.1.dh-lua.conf > libtool --tag=CC --mode=compile cc -c -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time
Bug#1002763: marked as done (lua-mediator: FTBFS: dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple test returned exit code 2)
Your message dated Tue, 11 Jan 2022 09:49:22 + with message-id and subject line Bug#1002763: fixed in lua-mediator 1.1.2-0-5 has caused the Debian Bug report #1002763, regarding lua-mediator: FTBFS: dh_auto_test: error: make --no-print-directory -f /usr/share/dh-lua/make/dh-lua.Makefile.multiple test returned exit code 2 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.) -- 1002763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lua-mediator Version: 1.1.2-0-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211228 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem=lua --with lua >dh_update_autotools_config -O--buildsystem=lua >dh_autoreconf -O--buildsystem=lua >dh_auto_configure -O--buildsystem=lua > make --no-print-directory -f > /usr/share/dh-lua/make/dh-lua.Makefile.multiple configure > > Making target configure for debian/lua5.1.dh-lua.conf > # .install > Filling in debian/lua-mediator.install using > /usr/share/dh-lua/template/lib.install.in > Adding new line: > Adding new line: usr/share/lua/5.1/mediator.lua > Filling in debian/lua-mediator-dev.install using > /usr/share/dh-lua/template/dev.install.in > Adding new line: > # lua_versions > Filling in debian/lua_versions > Adding new line: 5.1 > Target configure made > > > Making target configure for debian/lua5.2.dh-lua.conf > # .install > Filling in debian/lua-mediator.install using > /usr/share/dh-lua/template/lib.install.in > Adding new line: usr/share/lua/5.2/mediator.lua > Filling in debian/lua-mediator-dev.install using > /usr/share/dh-lua/template/dev.install.in > # lua_versions > Filling in debian/lua_versions > Adding new line: 5.2 > Target configure made > > > Making target configure for debian/lua5.3.dh-lua.conf > # .install > Filling in debian/lua-mediator.install using > /usr/share/dh-lua/template/lib.install.in > Adding new line: usr/share/lua/5.3/mediator.lua > Filling in debian/lua-mediator-dev.install using > /usr/share/dh-lua/template/dev.install.in > # lua_versions > Filling in debian/lua_versions > Adding new line: 5.3 > Target configure made > > > Making target configure for debian/lua5.4.dh-lua.conf > # .install > Filling in debian/lua-mediator.install using > /usr/share/dh-lua/template/lib.install.in > Adding new line: usr/share/lua/5.4/mediator.lua > Filling in debian/lua-mediator-dev.install using > /usr/share/dh-lua/template/dev.install.in > # lua_versions > Filling in debian/lua_versions > Adding new line: 5.4 > Target configure made > >dh_auto_build -O--buildsystem=lua > make --no-print-directory -f > /usr/share/dh-lua/make/dh-lua.Makefile.multiple build > > Making target build for debian/lua5.1.dh-lua.conf > Target build made > > > Making target build for debian/lua5.2.dh-lua.conf > Target build made > > > Making target build for debian/lua5.3.dh-lua.conf > Target build made > > > Making target build for debian/lua5.4.dh-lua.conf > Target build made > >dh_auto_test -O--buildsystem=lua > make --no-print-directory -f > /usr/share/dh-lua/make/dh-lua.Makefile.multiple test > > Making target test for debian/lua5.1.dh-lua.conf > # tests > /usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > Copying src/mediator.lua in /<>/5.1-mediator for test > ** lua dynamic custom (5.1) ** > ++ > 26 successes / 0 failures / 0 errors / 0 pending : 0.003928 seconds > * > Target test made > > > Making target test for debian/lua5.2.dh-lua.conf > # tests > /usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > Copying src/mediator.lua in /<>/5.2-mediator for test > ** lua dynamic custom (5.2) ** > ++ > 26 successes / 0 failures / 0 errors / 0 pending : 0.003983 seconds > * > Target test made > > > Making target test for debian/lua5.3.dh-lua.conf > # tests > /usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > Copying src/mediator.lua in /<>/5.3-mediator for test > ** lua dynamic custom (5.3) ** > ++ > 26 successes / 0 failures / 0 errors / 0 pending :
Bug#1002677: marked as done (FTBFS in unstable)
Your message dated Tue, 11 Jan 2022 09:34:16 + with message-id and subject line Bug#1002677: fixed in liquidsoap 2.0.2-1 has caused the Debian Bug report #1002677, regarding FTBFS in unstable 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.) -- 1002677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002677 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: liquidsoap Version: 1.4.4-1 Severity: serious Tags: ftbfs Dear Maintainer, Your package FTBFS in unstable with the following error: > File "tools/ffmpeg_config.ml", line 38, characters 9-36: > 38 | FFmpeg.Avutil.Log.set_level verbosity; > ^^^ > Error: Unbound module FFmpeg Cheers, -- Stéphane -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: liquidsoap Source-Version: 2.0.2-1 Done: Kyle Robbertze We believe that the bug you reported is fixed in the latest version of liquidsoap, 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. Kyle Robbertze (supplier of updated liquidsoap 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: Tue, 11 Jan 2022 11:00:10 +0200 Source: liquidsoap Architecture: source Version: 2.0.2-1 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Kyle Robbertze Closes: 1002677 Changes: liquidsoap (2.0.2-1) unstable; urgency=medium . * New upstream version 2.0.2 (Closes: #1002677) * Refresh d/patches * Update d/control with new build-dep versions * Update d/liquidsoap.links for new version * Update autopkgtests for new language features Checksums-Sha1: 38c6380cb9d655489df65fb2d4ff837d31bdebdf 3522 liquidsoap_2.0.2-1.dsc 950ae4dd283a90b044ad65c9bc15165d9e2640eb 2968342 liquidsoap_2.0.2.orig.tar.bz2 1523bd2b5947b670448a767071e8c6a16571db6b 17776 liquidsoap_2.0.2-1.debian.tar.xz 9b92741b2284bf3adf7a74102a264271f826c882 24523 liquidsoap_2.0.2-1_amd64.buildinfo Checksums-Sha256: 44d86e34f320a9659c87e41ffab8bc695e8c653d9521ecaa4d77d7fa86e7 3522 liquidsoap_2.0.2-1.dsc 4e74e158a949430d3b46d160176bff9375b4f6a940cbdfd19e64fdafc72635a7 2968342 liquidsoap_2.0.2.orig.tar.bz2 e990b8af540b3225acf3115458d93b8379a318c9a56f9ae4ca46dc03eec5e476 17776 liquidsoap_2.0.2-1.debian.tar.xz 11205098ea3bbc245cdc889c5045e5ef9ee29651b523ddfd578f87fa45dbbf28 24523 liquidsoap_2.0.2-1_amd64.buildinfo Files: b6a0804c18c3f2154088286b98f8cefd 3522 sound optional liquidsoap_2.0.2-1.dsc 3ab39586ed5c35f415db4f347bfab2f6 2968342 sound optional liquidsoap_2.0.2.orig.tar.bz2 8c28d79f3e0b4b152626eea0e337167a 17776 sound optional liquidsoap_2.0.2-1.debian.tar.xz 5bc13284c8217ca6abeeddbfa8fe9878 24523 sound optional liquidsoap_2.0.2-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJMBAEBCgA2FiEElqWPGCu4+bgcXyczhU8Hvggt8U8FAmHdSZUYHHBhZGRhdHJh cHBlckBkZWJpYW4ub3JnAAoJEIVPB74ILfFPIjUQAKRGEmRcsJD7c4QwyltJ0pxZ n0WNusfuF+OBwSfRQUJ4rQBYzC+UKIyJsJAifdNfddPHRVxBD2h368szUdzpJPae N6dWvQMySQNr5qfhnCS3OJOA37EQb5XQYBbX2PimuKTEnQ79QEH+kzo9907PLX7s oAIuPGID0Kxhjie11TnkP10abq+nMB7EA2yOMELz/vD/VYG9IR6v/2+g2/Yy0oQJ ULfqZzddO6hkf6BM+8xIwM5GuxxDEKM6cCrRA0B2FKLGLFltHxuXg+Cl95VeRonO RelOWo1DLzhmlloaPj1OLpcSfZlLDhMnYlqGYcBPBCDa1sg49B92xp4dFIgwRIc8 jCT9th2X9gQEwGaKVw4v4yaXj8n6wECcwwmjQ+/bx9RAu37jApy941JBVnn6lwIl r1J2+xarWK2ThJif13EwjyRRtHsueQQK3OdhQvxZo++7YN7bt0RnOrFxzYI+gnXV oNE35qQEB8Kqa0BKrr26DeGg0F1VNJbyWPLWWkNjfMxHUd/txP5PF1Mqhlwg/SKf xcssLarcJ+lZx5YkJmiovTjCrmitr/Jb5mfCp5OIGgxZs7JyUDpUxMVx+rJWvZ/G vB+qnfT7Nvi1BlJyRONhAD1Quy1x7b0DH3f5O9w/4T1wvjoyQhI55mtwm/mU7GvK AFhYX3U7N0LUYwOZCZif =DhGK -END PGP SIGNATURE End Message ---
Processed: closing 997489
Processing commands for cont...@bugs.debian.org:
> close 997489
Bug #997489 [src:fonttools] fonttools: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p 3.9 returned exit code 13
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
997489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997489
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#978926: marked as done (xscreensaver: ftbfs with autoconf 2.70)
Your message dated Tue, 11 Jan 2022 08:33:50 + with message-id and subject line Bug#978926: fixed in xscreensaver 6.02+dfsg1-1 has caused the Debian Bug report #978926, regarding xscreensaver: ftbfs with autoconf 2.70 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.) -- 978926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978926 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:xscreensaver Version: 5.42+dfsg1-1 Severity: normal Tags: sid bookworm User: d...@debian.org Usertags: ftbfs-ac270 [This bug report is not targeted to the upcoming bullseye release] The package fails to build in a test rebuild on at least amd64 with autoconf 2.70, but succeeds to build with autoconf 2.69. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://qa-logs.debian.net/2020/09/26.ac270/xscreensaver_5.42+dfsg1-1_unstable_ac270.log The last lines of the build log are at the end of this report. To build with autoconf 2.70, please install the autoconf package from experimental: apt-get -t=experimental install autoconf [...] 206 | G_URI_HIDE_FRAGMENT= 1 << 4, | ^ /usr/include/glib-2.0/glib/guri.h:256:41: warning: comma at end of enumerator list [-Wpedantic] 256 | G_URI_PARAMS_PARSE_RELAXED= 1 << 2, | ^ /usr/include/glib-2.0/glib/guri.h:331:27: warning: comma at end of enumerator list [-Wpedantic] 331 | G_URI_ERROR_BAD_FRAGMENT, | ^ In file included from /usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9, from /usr/include/glib-2.0/glib/gtypes.h:32, from /usr/include/glib-2.0/glib/galloca.h:32, from /usr/include/glib-2.0/glib.h:30, from /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf.h:29, from /usr/include/gdk-pixbuf-2.0/gdk-pixbuf-xlib/gdk-pixbuf-xlib.h:22, from xscreensaver-getimage.c:56: /usr/include/glib-2.0/gobject/gobject.h: In function ‘g_assert_finalize_object’: /usr/include/glib-2.0/glib/gmacros.h:768:39: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic] 768 | #define G_STRFUNC ((const char*) (__FUNCTION__)) | ^~~~ /usr/include/glib-2.0/glib/gtestutils.h:140:103: note: in expansion of macro ‘G_STRFUNC’ 140 |g_assertion_message (G_LOG_DOMAIN, __FILE__, __LINE__, G_STRFUNC, \ | ^ /usr/include/glib-2.0/gobject/gobject.h:786:3: note: in expansion of macro ‘g_assert_true’ 786 | g_assert_true (G_IS_OBJECT (weak_pointer)); | ^ /usr/include/glib-2.0/glib/gmacros.h:768:39: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic] 768 | #define G_STRFUNC ((const char*) (__FUNCTION__)) | ^~~~ /usr/include/glib-2.0/glib/gtestutils.h:162:103: note: in expansion of macro ‘G_STRFUNC’ 162 |g_assertion_message (G_LOG_DOMAIN, __FILE__, __LINE__, G_STRFUNC, \ | ^ /usr/include/glib-2.0/gobject/gobject.h:789:3: note: in expansion of macro ‘g_assert_null’ 789 | g_assert_null (weak_pointer); | ^ In file included from /usr/include/glib-2.0/gio/giotypes.h:28, from /usr/include/glib-2.0/gio/gio.h:26, from /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:33, from /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf.h:34, from /usr/include/gdk-pixbuf-2.0/gdk-pixbuf-xlib/gdk-pixbuf-xlib.h:22, from xscreensaver-getimage.c:56: /usr/include/glib-2.0/gio/gioenums.h: At top level: /usr/include/glib-2.0/gio/gioenums.h:601:52: warning: comma at end of enumerator list [-Wpedantic] 601 | G_ASK_PASSWORD_TCRYPT = (1 << 5), |^ In file included from /usr/include/glib-2.0/gio/giotypes.h:28, from /usr/include/glib-2.0/gio/gio.h:26, from /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:33,
Processed: severity of 993882 is normal
Processing commands for cont...@bugs.debian.org: > severity 993882 normal Bug #993882 [virt-manager] power64le: virt-manager refuses to start fresh install of FreeBSD 13.0 due to qemu issue on power8 host (safe cache missing) Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 993882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
