Bug#1018924: libgc FTBFS: architecture-specific symbol handling removed
Hi Ivan, On Mon, Sep 05, 2022 at 12:17:10AM +0300, Ivan Maidanski wrote: > Let me go thru all items you warry about. Please be sure both Ian and I pay > attention to the quality of the prepared releases. Sometimes mistakes happen > — it is essential to promptly react and think of the proper fix or workaround > in such situations. Thank you. I concur. Please upload a fixed version quickly. This currently breaks half of the bootstrap ci jobs, which makes me blind to breakage in other packages. Urgency is needed here. > The builds fail because of a change in some mangled names — probably the > reason is changing of noexcept/throw() specification in operator delete > (libgc tries to follow C++ standard but if this breaks some ABI, it could be > configured at build time thru macros). I need more time to check the > situation deeper. That would sound reasonable if the upload had been done to experimental. The combination of urgency and "need more time" is unfortunate. I fear that doing it improperly would be making it worse as symbol issues can have a rippling effect. Admittedly all missing symbols on the most recent upload seem to be C++ symbols. That much is plausible at least. To make your (and my) life easier, I suggest that you use modern symbol features (man deb-src-symbols). In particular, you can restrict symbols to 32bit or 64bit using "(arch-bits=32)symbol..." and you can use C++ symbol mangling using "(c++)unmangled...". > > its symbol handling is essentially stripped of all the > >architecture-specific patterns that we have accumulated over the years > > These stripped symbols are actually «leaked» internal symbols of libgc, > additionally I am not aware of any libgc client S/W which relies on these > internal symbols. Let me know please if someone is using any of the stripped > symbols. There is no practical reason of keeping these symbols in libgc > except for a formal one. Please correct me if I am wrong. I happen to not understand which symbols are internal and which are not. I really cannot tell. I'm more than happy if those really are unused. > > * Lots of symbols were dropped from the symbols file without bumping > >soname. Possibly, this may lead to incorrect dependencies on libgc in > >downstream builds. > > Bumping soname indicates no backward compatibility. This has some negative > drawback (e.g. system should have 2 versions of libraries, client S/W does > not benefit from the new library version until client binary is rebuilt). I > avoid deletion or incompatible changes of API symbols between libgc releases. > (Unfortunately there’s an issues with a mangled name I wrote above.) I’ve > explained the situation about dropping of lots of symbols above. My opinion > this should not lead to incorrect dependencies on libgc but how could we > figure it out practically. If it would turn out later that some of dropped > symbols are nonetheless in use, then I think it would not be complicated to > fix it on the libgc side. If you look into the differences, it's not just C++ symbols that have been dropped. Here is a list of dropped symbols: < GC_FirstDLOpenedLinkMap@Base 1:7.2d < (arch=kfreebsd-amd64 kfreebsd-i386)GC_FreeBSDGetDataStart@Base 1:7.2d < (arch=sparc sparc64)GC_SysVGetDataStart@Base 1:7.2d < (arch=!nios2 !sh4)GC_acquire_mark_lock@Base 1:8.0 < (arch=!nios2 !sh4)GC_active_count@Base 1:8.0 < GC_add_ext_descriptor@Base 1:7.2d < GC_add_map_entry@Base 1:7.2d < GC_add_roots_inner@Base 1:7.2d < GC_add_smashed@Base 1:7.2d < GC_add_to_black_list_normal@Base 1:7.2d < GC_add_to_black_list_stack@Base 1:7.2d < GC_add_to_fl@Base 1:7.2d < GC_add_to_heap@Base 1:7.2d < GC_adj_bytes_allocd@Base 1:7.2d < GC_all_bottom_indices@Base 1:7.2d < GC_all_bottom_indices_end@Base 1:7.2d < GC_alloc_large@Base 1:7.2d < GC_alloc_large_and_clear@Base 1:7.2d < GC_alloc_reclaim_list@Base 1:7.2d < GC_allocate_ml@Base 1:8.0 < GC_allochblk@Base 1:7.2d < GC_allochblk_nth@Base 1:7.2d < GC_allocobj@Base 1:7.2d < GC_apply_to_all_blocks@Base 1:7.2d < GC_approx_sp@Base 1:7.2d < GC_array_kind@Base 1:7.2d < GC_array_mark_proc@Base 1:7.2d < GC_array_mark_proc_index@Base 1:7.2d < GC_avail_descr@Base 1:7.2d < GC_bl_init@Base 1:7.2d < GC_bl_init_no_interiors@Base 1:7.2d < GC_black_list_spacing@Base 1:7.2d < GC_block_empty@Base 1:7.2d < GC_block_nearly_full@Base 1:7.2d < GC_block_was_dirty@Base 1:7.2d < GC_bm_table@Base 1:7.2d < (arch=!kfreebsd-amd64 !kfreebsd-i386)GC_brief_async_signal_safe_sleep@Base 1:7.6.4 < GC_build_fl2@Base 1:7.2d < GC_build_fl4@Base 1:7.2d < GC_build_fl@Base 1:7.2d < GC_build_fl_clear2@Base 1:7.2d < GC_build_fl_clear4@Base 1:7.2d < (arch=!nios2 !sh4)GC_bytes_allocd_tmp@Base 1:8.0 < GC_bytes_found@Base 1:7.2d < GC_check_annotated_obj@Base 1:7.2d < GC_check_finalizer_nested@Base 1:7.2d < GC_check_heap@Base 1:7.2d < GC_check_heap_block@Base 1:7.2d < GC_check_heap_proc@Base 1:7.2d < GC_check_leaked@Base 1:7.2d < GC_clear_a_few_f
Bug#1017592: marked as done (mmdebstrap: autopkgtest fails because getpwnam is broken in fakechroot since glibc 2.34)
Your message dated Mon, 05 Sep 2022 06:03:42 + with message-id and subject line Bug#1017592: fixed in mmdebstrap 1.2.0-1 has caused the Debian Bug report #1017592, regarding mmdebstrap: autopkgtest fails because getpwnam is broken in fakechroot since glibc 2.34 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.) -- 1017592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017592 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mmdebstrap Version: 1.1.0-1 Severity: serious X-Debbugs-Cc: jo...@debian.org Control: block -1 by 1017590 Hi, since the upload of src:glibc 2.34, getpwnam are not wrapped anymore by fakechroot. This breaks the autopkgtest of mmdebstrap. See https://bugs.debian.org/1017590 for details. Thanks! cheers, josch --- End Message --- --- Begin Message --- Source: mmdebstrap Source-Version: 1.2.0-1 Done: Johannes Schauer Marin Rodrigues We believe that the bug you reported is fixed in the latest version of mmdebstrap, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Johannes Schauer Marin Rodrigues (supplier of updated mmdebstrap 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: Mon, 05 Sep 2022 07:48:37 +0200 Source: mmdebstrap Architecture: source Version: 1.2.0-1 Distribution: unstable Urgency: medium Maintainer: Johannes Schauer Marin Rodrigues Changed-By: Johannes Schauer Marin Rodrigues Closes: 1017592 1017795 1018957 Changes: mmdebstrap (1.2.0-1) unstable; urgency=medium . * new upstream release - fix mmdebstrap hanging if apt in download step failed (closes: #1017795) - remove proot mode (closes: #1018957) * fix autopkgtests (closes: #1017592) Checksums-Sha1: 2bb82dc234904026d28a878c517cbe5fe2b67387 2329 mmdebstrap_1.2.0-1.dsc f46cd3ccca3ebd01b0a12e3ee5b029268871c1d7 126066 mmdebstrap_1.2.0.orig.tar.gz 4100f34df86a9451f0a8662629527fb827c36d00 10936 mmdebstrap_1.2.0-1.debian.tar.xz Checksums-Sha256: 8cd25a0c58b40fcc38ebe49b0d5be41352dfa9ec3148e91f4de1637f7b8b3259 2329 mmdebstrap_1.2.0-1.dsc 71ce0d4d9fbe99b985be5d35ca5fb595ad52b5d0a8c46ded039c422b788e4f0b 126066 mmdebstrap_1.2.0.orig.tar.gz 8def63a6b3a33532cff9ed661df5bb8f16b52f838dc79f19705e79b945f8e649 10936 mmdebstrap_1.2.0-1.debian.tar.xz Files: a80268c54126acbe2e9fb6351c1c2355 2329 admin optional mmdebstrap_1.2.0-1.dsc c99f91dcfc285636d25cc0209d01afea 126066 admin optional mmdebstrap_1.2.0.orig.tar.gz d2982c64a2d3578900f893cce9aae727 10936 admin optional mmdebstrap_1.2.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmMVjd4ACgkQ8sulx4+9 g+FZ3Q/9GNPiBq38Ngnd6UoAfYGgssMTXP7aBfSNKprmnupxgudHPAyBa/5ssjXm laXULbGyElIVB/7Nm0Ppb0laBmdrG3vfkYmJRacKWfQ0f9D4sUKpzxrDW2e1hx3I 9zaYqWh5+gQ7yv85jqd/JJWyOoiPnAWW7D5B86eqzYqa+6Vn5CbRG+0c7K6qqfiU tC4QJERu5c2y24MFxyVPtduhhbdbU0cHWawReVaa2y3rgKT/DgnnXXXtcxUv/9uO ouYaG68l4uctGhbtKR+nw8f8hhcw/F5en2q5a49scNnFLu0t1/gXv232M4FeK6Q+ Qq8n3sZFidQW3103ygQ/MtFEoaxkBVFDd1c/+Fp4G634Q8AGzcJhAdQr1j5UyRyc +I6PwBrjXgME+sVOyo713yvZxwW6P7mBgG75xhtQi5JJJFc51xa6VkJ2pFcpqgE6 aOQ/WYrUcNalrZQlnnPnpieR9SajP9RBpIYg5ubeHrqayARjOBrZlB3k444WAY54 En9vfmlOjveJ3b1UkZWnIMefpw+7EhqVKiUE5X2t6y2X3/Rz+rBhOzwCHan1zzLs 2bGVO18pH2KOLN73BFspGEVlefxP3OGhs9QI7PDUY0tHZyTgJSyjBmLH6RVRWGAk WQU/qB256zZUJ0UlymuFqXT11OcTarxRJ0fBYBTtJIA+65Fdw08= =r3qz -END PGP SIGNATURE End Message ---
Bug#1019183: librust-uuid+rand-dev: impossible to install package
On Mon, 05 Sep 2022 06:52:57 +0200 Jonas Smedegaard wrote: librust-uuid+rand-dev is impossible to install: Depends on missing package librust-uuid-dev (= 0.8.1-5) Hi Jonas, librust-uuid-dev is now 1.1.2, which has no "rand" feature. You may want to use feature "v4" which is the randomly generated UUID v4, or "fast-rng" that references a "private_rand" feature, using the rand crate rather than getrandom. -- Regards, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1019183: librust-uuid+rand-dev: impossible to install package
Package: librust-uuid+rand-dev Version: 0.8.1-5 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 librust-uuid+rand-dev is impossible to install: Depends on missing package librust-uuid-dev (= 0.8.1-5) - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmMVgKYACgkQLHwxRsGg ASH7yA/+OM5w4lxNq/DXpvH1/deH2CUKQ7DD2A3ngwA6EsndGggWCAeyiKmatm78 pWeT0PP7FIVkFBi0ExGmK6/egxTUATC7W1CvWB8N0txrtNoBHtS2O2yeQbrqNV9r Tg9+iQwdbYVHKXuTwh+OEKmZsVufCqGnfvihaICl6mAp6IqAWdD6Y521DlgX8y8R ZadX8SZHKjc3uAhwlU4ENIzkFS+8d9livYBdmrM+m0UK+ITCq4i4+V6TsKOlj4am h9hWy6eagoUKgIPUI9A/j8DWp3IcdaLg2xT4J7MSoF8HcyAGjTDjpv+ZlZOISr3i lvLuUm9oJm7mI8icdxIIUD0pLY49iAn18XDwposAQ+qoRhRUb+o+MfkI2WtcCpi0 /7MTbWCITC+Y0NFq1M7SGHV5yOjEG2xl6I/pTvNOkK1noOtx4oCaHQB+ykm0vst4 7P/40CMs0XDhw+7TJyW2Gf0RtaKf4Qc4ES+T+/1GckGLa4LvnefVAYJkXGMxf/yf zMjeGPjPBvgFUBi4mMGIWWp4ctt5I9/oyjCXY4nOOkt0IfbYoV6d1FlMJnJhCES2 TKnkRad8QABmqEv30R3rXbL5QZp6osT+kuqOosyJ4XA7uPSKO1M3VdP9VCnRsAhL yGNjIczL6K7M8G5/OsFAhUNEQ5bxoIZmYohC02ocBPGxmujMCgE= =ks2S -END PGP SIGNATURE-
Bug#1015044: Not a setuptools-scm issue?
Le lundi 05 septembre 2022 à 08:28 +1000, Brian May a écrit : > On Wed, Aug 03, 2022 at 12:22:32PM +0200, > julien.pu...@gmail.com wrote: > > I'm sorry, but I don't see why you think this is a problem with > > setuptools-scm. > > > > sshuttle's debian/rules asks setuptools-scm to generate a version > > file > > in its clean target. So setuptools-scm does so, and it doesn't look > > invalid. > > > > But it doesn't not correspond to the version file as shipped, so > > dpkg > > protests that the source tree has been modified. > > Please make sure you CC responses to me. Otherwise I won't get them. > > At first glance I thought this was invalid Python code, but oh wait, > I > think this is valid. Problem when dealing with too many languages. > > __version__ = version = '1.1.0' > __version_tuple__ = version_tuple = (1, 1, 0) > > But what seems to be the problem here is that setuptools-scm has > silently changed how it generates this file. Which breaks Debian > packages. > > If you don't agree with me, then assign this bug back to sshuttle and > I > will deal with it. In fact latest upstream sshuttle removes > setuptools-scm support anyway. If I remember well, that generation is done in the clean target: if that's the case, then it's sshuttle's (package's) problem. I see two solutions: - add a patch so the file becomes re-generation invariant ; - add an empty override_dh_whatever_clean in d/rules so the re- generation isn't triggered. Cheers, J.Puydt
Bug#1017833: marked as done (elpa-elscreen: emacs 28.1 upgrade failure with byte compiling of elpa-elscreen)
Your message dated Mon, 05 Sep 2022 02:33:46 + with message-id and subject line Bug#1017833: fixed in elscreen 1.4.6-9 has caused the Debian Bug report #1017833, regarding elpa-elscreen: emacs 28.1 upgrade failure with byte compiling of elpa-elscreen 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.) -- 1017833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: elpa-elscreen Version: 1.4.6-8 Severity: normal Dear Maintainer, Upgrading to emacs-gtk 28.1 fail with byte compiling elpa-elscreen Paramétrage de emacs-gtk (1:28.1+1-2) ... Deep recursion on subroutine "main::generate_relevant_tsort_dependencies_internals" at /usr/lib/emacsen-common/lib.pl line 127. Install emacs-calfw for emacs Install emacs-window-layout for emacs Install emacsen-common for emacs emacsen-common: Handling install of emacsen flavor emacs Install emacspeak for emacs /usr/lib/emacsen-common/packages/install/emacspeak running in / Latest installed version: 53.0+dfsg-1 Latest compiled version: 53.0+dfsg-1 Install pylint for emacs ... a lot of successful byte compiling lines skipped Install elpa-elscreen for emacs install/elscreen-1.4.6: Handling install of emacsen flavor emacs install/elscreen-1.4.6: byte-compiling for emacs In toplevel form: elscreen-color-theme.el:25:1: Error: Wrong number of arguments: make-obsolete-variable, 2 In toplevel form: elscreen-dired.el:26:1: Error: Wrong number of arguments: make-obsolete-variable, 2 In toplevel form: elscreen-dnd.el:26:1: Error: Wrong number of arguments: make-obsolete-variable, 2 In toplevel form: elscreen-gf.el:28:1: Error: Wrong number of arguments: make-obsolete-variable, 2 In toplevel form: elscreen-goby.el:26:1: Error: Wrong number of arguments: make-obsolete-variable, 2 In toplevel form: elscreen-howm.el:26:1: Error: Wrong number of arguments: make-obsolete-variable, 2 In toplevel form: elscreen-server.el:27:1: Error: Wrong number of arguments: make-obsolete-variable, 2 In toplevel form: elscreen-speedbar.el:25:1: Error: Wrong number of arguments: make-obsolete-variable, 2 In toplevel form: elscreen-w3m.el:26:1: Error: Wrong number of arguments: make-obsolete-variable, 2 In toplevel form: elscreen.el:155:4: Warning: make-obsolete-variable called with 2 arguments, but requires 3-4 elscreen.el:201:13: Warning: custom-declare-variable `elscreen-tab-display-kill-screen' docstring wider than 80 characters In elscreen-get-alist-to-nickname: elscreen.el:630:8: Warning: ‘mapcar’ called for effect; use ‘mapc’ or ‘dolist’ instead In elscreen-get-screen-to-name-alist: elscreen.el:666:21: Warning: ‘mapcar’ called for effect; use ‘mapc’ or ‘dolist’ instead elscreen.el:666:21: Warning: ‘mapcar’ called for effect; use ‘mapc’ or ‘dolist’ instead In elscreen-find-screens: elscreen.el:769:11: Warning: ‘mapcar’ called for effect; use ‘mapc’ or ‘dolist’ instead In elscreen-find-screen-by-major-mode: elscreen.el:818:15: Warning: ‘mapcar’ called for effect; use ‘mapc’ or ‘dolist’ instead In elscreen-kill-others: elscreen.el:927:14: Warning: ‘interactive-p’ is an obsolete function (as of 23.2); use ‘called-interactively-p’ instead. elscreen.el:929:5: Warning: ‘interactive-p’ is an obsolete function (as of 23.2); use ‘called-interactively-p’ instead. elscreen.el:929:5: Warning: ‘interactive-p’ is an obsolete function (as of 23.2); use ‘called-interactively-p’ instead. elscreen.el:926:45: Warning: ‘interactive-p’ is an obsolete function (as of 23.2); use ‘called-interactively-p’ instead. In elscreen-select-and-goto: elscreen.el:1170:8: Warning: ‘mapcar’ called for effect; use ‘mapc’ or ‘dolist’ instead elscreen.el:1183:43: Warning: ‘mapcar’ called for effect; use ‘mapc’ or ‘dolist’ instead In elscreen-find-and-goto-by-buffer: elscreen.el:1193:30: Warning: ‘interactive-p’ is an obsolete function (as of 23.2); use ‘called-interactively-p’ instead. In elscreen-find-file-read-only: elscreen.el:1220:4: Warning: ‘toggle-read-only’ is an obsolete function (as of 24.3); use ‘read-only-mode’ instead. In elscreen-e21-tab-update: elscreen.el:1533:38: Warning: ‘mapcar’ called for effect; use ‘mapc’ or ‘dolist’ instead In elscreen-command-line-funcall: elscreen.el:1676:10: Warning: reference to free variable ‘file-count’ elscreen.el:1676:10: Warning: assignment to free variable ‘file-count’ In elscreen-command-line-find-file: elscreen.el:1693:20: Warning: ‘goto-line’ is for interactive use only; use ‘forward-line’ instead. elscreen.
Bug#1015027: marked as done (php-dragonmantank-cron-expression: FTBFS: make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1)
Your message dated Mon, 05 Sep 2022 00:07:04 + with message-id and subject line Bug#1015027: fixed in php-dragonmantank-cron-expression 3.3.1-2 has caused the Debian Bug report #1015027, regarding php-dragonmantank-cron-expression: FTBFS: make[1]: *** [debian/rules:14: override_dh_auto_test] Error 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.) -- 1015027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-dragonmantank-cron-expression Version: 3.3.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 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 '/<>' > phpunit -v --bootstrap src/Cron/autoload.php --include-path src > PHPUnit 9.5.21 [44;37m#StandWith[0m[43mUkraine[0m > > Runtime: PHP 8.1.7 > Configuration: /<>/phpunit.xml.dist > > ... 63 / 167 ( > 37%) > ... 126 / 167 ( > 75%) > ...FF..F.F... 167 / 167 > (100%) > > Time: 00:00.062, Memory: 8.00 MB > > There were 4 failures: > > 1) Cron\Tests\DaylightSavingsTest::testOffsetDecrementsNextRunDateAllowCurrent > Failed asserting that two DateTime objects are equal. > --- Expected > +++ Actual > @@ @@ > -2020-10-25T01:00:00.00+ > +2020-10-25T01:00:00.00+0100 > > /<>/tests/Cron/DaylightSavingsTest.php:125 > > 2) > Cron\Tests\DaylightSavingsTest::testOffsetDecrementsNextRunDateDisallowCurrent > Failed asserting that two DateTime objects are equal. > --- Expected > +++ Actual > @@ @@ > -2020-10-25T01:00:00.00+ > +2020-10-25T01:00:00.00+0100 > > /<>/tests/Cron/DaylightSavingsTest.php:159 > > 3) Cron\Tests\DaylightSavingsTest::testOffsetDecrementsMultipleRunDates > Failed asserting that an array contains DateTimeImmutable Object > &011e ( > 'date' => '2020-11-08 01:00:00.00' > 'timezone_type' => 3 > 'timezone' => 'Europe/London' > ). > > /<>/tests/Cron/DaylightSavingsTest.php:248 > > 4) Cron\Tests\DaylightSavingsTest::testOffsetDecrementsEveryOtherHour > Failed asserting that an array contains DateTimeImmutable Object > &011f ( > 'date' => '2020-10-25 07:00:00.00' > 'timezone_type' => 3 > 'timezone' => 'Europe/London' > ). > > /<>/tests/Cron/DaylightSavingsTest.php:367 > > FAILURES! > Tests: 167, Assertions: 775, Failures: 4. > make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/07/16/php-dragonmantank-cron-expression_3.3.1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220716&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results 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: php-dragonmantank-cron-expression Source-Version: 3.3.1-2 Done: Robin Gustafsson We believe that the bug you reported is fixed in the latest version of php-dragonmantank-cron-expression, 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 1015...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Robin Gustafsson (supplier of updated php-dragonmantank-cron-expression 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) -BEGI
Bug#1018713: marked as done (mailfilter: Filtering at pop.gmail.com doesn't work)
Your message dated Sun, 04 Sep 2022 23:34:34 + with message-id and subject line Bug#1018713: fixed in mailfilter 0.8.9-1 has caused the Debian Bug report #1018713, regarding mailfilter: Filtering at pop.gmail.com doesn't work 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.) -- 1018713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018713 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mailfilter Version: 0.8.8-1 Severity: grave Justification: renders package unusable I enabled pop on Port 995 at gmail. 2FA password is generated and works well fetching mails with getmail6. Running mailfilter -r -M mailfilterrc gives Aug 16 14:18:52 mailfilter: 0.8.8 querying m...@gmail.com@pop.gmail.com. Aug 16 14:18:53 mailfilter: Error: SSL connection could not be established: self-signed certificate Aug 16 14:18:53 mailfilter: Error: SSL connection could not be established. Aug 16 14:18:53 mailfilter: Error: Could not establish network connection. mailfilterrc: SERVER="pop.gmail.com" USER="m...@gmail.com" PASS="blafasel" PROTOCOL="pop3/ssl" PORT=995 -- System Information: Debian Release: bookworm/sid merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.15.59-baumbart-lxtec-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages mailfilter depends on: ii debconf [debconf-2.0] 1.5.79 ii libc6 2.34-7 ii libgcc-s1 12.2.0-1 ii libssl33.0.5-2 ii libstdc++6 12.2.0-1 mailfilter recommends no packages. mailfilter suggests no packages. -- debconf information excluded --- End Message --- --- Begin Message --- Source: mailfilter Source-Version: 0.8.9-1 Done: Elimar Riesebieter We believe that the bug you reported is fixed in the latest version of mailfilter, 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 1018...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Elimar Riesebieter (supplier of updated mailfilter 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: Sun, 04 Sep 2022 14:01:55 +0200 Source: mailfilter Architecture: source Version: 0.8.9-1 Distribution: unstable Urgency: medium Maintainer: Joerg Jaspert Changed-By: Elimar Riesebieter Closes: 1018713 Changes: mailfilter (0.8.9-1) unstable; urgency=medium . * Import new upstream version. Thanks upstream for cooperation. (Closes: 1018713) * Refresh patches as needed. Checksums-Sha1: a76d6c32ea9209c8844fcb85e39182a49361758b 1944 mailfilter_0.8.9-1.dsc cbabbac4d57f6dec763093fd9926bf085cc219d8 146416 mailfilter_0.8.9.orig.tar.gz 0579534ead33ecad711cec18a019d3b5d105b9b2 15192 mailfilter_0.8.9-1.debian.tar.xz bab5b34418f402115040e4d9a7f4b41955f57951 5699 mailfilter_0.8.9-1_source.buildinfo Checksums-Sha256: 9d986ed23789fb3976390c3a3b46ef88aefc4d38daf553e436c33c6536d84011 1944 mailfilter_0.8.9-1.dsc ad903ced13bce1538c459d1288de08adfef1da6e01a826fd58a17a936f7525fb 146416 mailfilter_0.8.9.orig.tar.gz 5f0f4e8a2abd66f4cb158c7f8fafaf94e563688813096d5fbd41c0ef4a8ea68a 15192 mailfilter_0.8.9-1.debian.tar.xz 0cd786306c720ac059f67e4241e9655f02373424c83a40656f421d3779697327 5699 mailfilter_0.8.9-1_source.buildinfo Files: a16ce4f22ddabf7980f1c83382adfe4f 1944 mail optional mailfilter_0.8.9-1.dsc 787ab69670fa7a95069d2cda3402e2f9 146416 mail optional mailfilter_0.8.9.orig.tar.gz 63939f36aaf935b7ff1aec3409c76000 15192 mail optional mailfilter_0.8.9-1.debian.tar.xz 079ed9365ed1a1be1b1be4ce6d356858 5699 mail optional mailfilter_0.8.9-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmMVMyEACgkQweDZLphv fH71mxAAnZ6h89wkDFjGD2IaljCnwYhyiLSSDqIiuwO0lVWiMg9gZzSBfkkdW8iE esbBPOZOj0x8BfkAIksf+CnOu9mTNQAaZYmDWkvLDjenBFp25VNGttBwS9Z6N/tx Nug2JSdbbm6yDzLLIiousuwhe0kNlSv5Przmb3x5zJ+18n4aEGOHKLqRHROtVTlO JZWIlcEL68oeTXhGLerLEXWKZmQIXKxydnz4ixeUAD9x+56VResJaeQLoTHxSCsX hBC3wyzJCEfZNp7525kNqXCSaX+U/MSFISP/vB+got
Bug#1019172: opengrm-ngram FTBFS against libfst 1.7.9
Source: opengrm-ngram
Version: 1.3.2-3
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic
Hi Giulio,
opengrm-ngram fails to build from source in Debian unstable:
[...]
In file included from ./../include/ngram/hist-mapper.h:22,
from ngram-count.cc:17:
./../include/ngram/hist-arc.h:47:16: error: ‘string’ does not name a type; did
you mean ‘stdin’?
47 | static const string &Type() { // Arc type name
|^~
|stdin
[...]
A build log showing this failure in Ubuntu is available at:
https://launchpad.net/ubuntu/+source/opengrm-ngram/1.3.2-3build2/+build/24299140
I attempted to patch the package to make it buildable, but in addition to
the obvious C++ standard fixes, there appear to also be api
incompatibilities with the new libfst which were not straightforwardly
fixable.
[...]
ngram-context.cc:78:8: error: ‘SplitToVector’ is not a member of ‘fst’
78 | fst::SplitToVector(contexts[0], " ", &labels1, true);
|^
[...]
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: PGP signature
Bug#984298: marked as done (psensor: ftbfs with GCC-11)
Your message dated Sun, 04 Sep 2022 23:05:38 + with message-id and subject line Bug#984298: fixed in psensor 1.1.5-1.4 has caused the Debian Bug report #984298, regarding psensor: 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.) -- 984298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984298 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:psensor Version: 1.1.5-1.3 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/psensor_1.1.5-1.3_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. [...] config.status: creating icons/hicolor/22x22/Makefile config.status: creating icons/hicolor/24x24/Makefile config.status: creating icons/hicolor/32x32/Makefile config.status: creating icons/hicolor/48x48/Makefile config.status: creating icons/hicolor/64x64/Makefile config.status: creating icons/ubuntu-mono-dark/status/22/Makefile config.status: creating icons/ubuntu-mono-light/status/22/Makefile config.status: creating icons/ubuntu-mono-dark/apps/22/Makefile config.status: creating www/Makefile config.status: creating po/Makefile.in config.status: creating tests/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing po-directories commands config.status: creating po/POTFILES config.status: creating po/Makefile dh_auto_build dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9 in use) make -j1 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in doc make[3]: Entering directory '/<>/doc' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/<>/doc' Making all in po make[3]: Entering directory '/<>/po' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/<>/po' Making all in src make[3]: Entering directory '/<>/src' Making all in lib make[4]: Entering directory '/<>/src/lib' gcc -DHAVE_CONFIG_H -I. -I../.. -Wall -Werror -I/usr/include/libgtop-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/json-c -pthread -I/usr/include/udisks2 -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 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o color.o color.c gcc -DHAVE_CONFIG_H -I. -I../.. -Wall -Werror -I/usr/include/libgtop-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/json-c -pthread -I/usr/include/udisks2 -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 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o hdd_hddtemp.o hdd_hddtemp.c gcc -DHAVE_CONFIG_H -I. -I../.. -Wall -Werror -I/usr/include/libgtop-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/json-c -pthread -I/usr/include/udisks2 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-
Bug#1015044: Reassign to sshuttle from setuptools-scm
On Sat, Aug 06, 2022 at 03:57:47PM +0200, julien.pu...@gmail.com wrote: > reassign 1015044 sshutle 1.0.1-1 errr, typo here in the package name. -- Brian May
Bug#1015044: Not a setuptools-scm issue?
On Wed, Aug 03, 2022 at 12:22:32PM +0200, julien.pu...@gmail.com wrote: > I'm sorry, but I don't see why you think this is a problem with > setuptools-scm. > > sshuttle's debian/rules asks setuptools-scm to generate a version file > in its clean target. So setuptools-scm does so, and it doesn't look > invalid. > > But it doesn't not correspond to the version file as shipped, so dpkg > protests that the source tree has been modified. Please make sure you CC responses to me. Otherwise I won't get them. At first glance I thought this was invalid Python code, but oh wait, I think this is valid. Problem when dealing with too many languages. __version__ = version = '1.1.0' __version_tuple__ = version_tuple = (1, 1, 0) But what seems to be the problem here is that setuptools-scm has silently changed how it generates this file. Which breaks Debian packages. If you don't agree with me, then assign this bug back to sshuttle and I will deal with it. In fact latest upstream sshuttle removes setuptools-scm support anyway. -- Brian May
Processed: forcibly merging 1015995 1016308
Processing commands for cont...@bugs.debian.org: > forcemerge 1015995 1016308 Bug #1015995 [src:gpgme1.0] gpgme1.0 FTBFS with 3.10 as only supported Python3 version Bug #1016308 [src:gpgme1.0] gpgme1.0: FTBFS: /bin/bash: line 1: ../../../../lang/python/tests/run-tests.py: Permission denied Added tag(s) patch. Bug #1015995 [src:gpgme1.0] gpgme1.0 FTBFS with 3.10 as only supported Python3 version Added tag(s) bookworm and sid. Merged 1015995 1016308 > thanks Stopping processing here. Please contact me if you need assistance. -- 1015995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015995 1016308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1018924: 1018924
> what happend to libgc? It ftbfs on all 32bit architectures and its > symbol handling is essentially stripped of all the architecture-specific > patterns that we have accumulated over the years. I will keep an eye on this with Ivan per his last mail. > * A possibly breaking change for a core package is often done to > experimental first to reduce disruption of development on unstable. > Doing so would have prevented major pain here. Well of course it wasn't supposed to be. I do apologise and there's always something to learn. > * The debian/changelog entry contains duplicates. Mea culpa as I learn gbp's automated changelog generation steps. > * Lots of symbols were dropped from the symbols file without bumping > soname. Possibly, this may lead to incorrect dependencies on libgc in > downstream builds. This was discussed. They were not supposed to be used [1]. We will need to discuss what is happening calmly. > * debian/changelog says that you removed libatomic_ops handling, but > for every new architecture libatomic_ops is still opted in leading to > unnecessary porting work even though built-in atomics generally work > well. This was done with [2]. I agree it's a bug to keep including it as a dependency, which we can handle as a bug [3] > I am also wondering whether this actually is a package hijack as there > is no visible acknowledgement from any existing maintainers to adding > Ian to uploaders. > I am quite disappointed by this upload and the downstream pain it causes > to QA. As if I would just hijack a package [4]. Please consider your tone so we can have a project where we work together instead of throw flames at each other. -i [1] https://salsa.debian.org/debian/libgc/-/merge_requests/3 [2] https://salsa.debian.org/debian/libgc/-/merge_requests/4 [3] https://salsa.debian.org/debian/libgc/-/merge_requests/8 [4] https://salsa.debian.org/debian/libgc/-/merge_requests/7
Bug#1019090: marked as done (librust-petgraph-dev: impossible to satisfy dependency)
Your message dated Sun, 04 Sep 2022 21:51:09 + with message-id and subject line Bug#1019090: fixed in rust-petgraph 0.6.2-1 has caused the Debian Bug report #1019090, regarding librust-petgraph-dev: impossible to satisfy dependency to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1019090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-petgraph-dev Version: 0.5.1-2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 nary package librust-petgraph-dev cannoy be installed, as it depends on missing package librust-fixedbitset-0.2-dev. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmMTdHYACgkQLHwxRsGg ASFgBhAAnr1YrSm7uazC0cXPfvvkUocVqWZxvJHuhSTUnoLNhkGKFEhc2xKwLeTy oVUUzKaNc44YGtUBXJHgU2gXJ7FdR///PG/oXwJoIEILtlsRwBXCdDTgWXmFHn/Z 2NG6J+deddRYKNG7+B4V360e00t946W9CnWluy/ugk0xVnlzL+v5T4skQeOvGcBr H6D6nNmAGqmre/IwB8q/PbSxEctKgqw4H5MiM0gVYwd7xCzpkqmsFwHOl2J3eMCJ mFJDqYaaVwx3v4VW+zk5GDJvXAf8wSrz9sOcySkERSwVTiTQYAYW/21nFDv6x551 VXUW786hhbp+FAK0lJLMkDnKcS+Tl/VfnxIiebo60TdSPlX3iJYcrzvYSenmK2jp S6obupY94cEYvaA+1Ae5wdc5rr0IylMwVPyII95fX5mp21gLvzzHHvF0Edi6AAhs oYFFYdWMaQxKmLd6sWOPhDHa5kjYtfstk1T3uINutQWVH+KWFSpogyx+XG9VVE+k mz6U6qKqhlhFd+bEBRJDdRa3k0JXROx7aYUOqzB963uH+49X4VD9z6Ng7j8PJIWk BIgxxmdJCChStJa3qHRJHfB0nILg5dDQOFYYvgzS3mooOLnya6NVJN3tzhwEpHAt HNO4VtaNBj6jcOSKaUgTzMKVsNoO2bXuD2Oa39a5Kky+EovXTe8= =3XsI -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: rust-petgraph Source-Version: 0.6.2-1 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-petgraph, 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 1019...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-petgraph 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: Sat, 03 Sep 2022 21:20:09 + Source: rust-petgraph Architecture: source Version: 0.6.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 1019090 Changes: rust-petgraph (0.6.2-1) unstable; urgency=medium . [ Blair Noctis ] * Team upload. * Package petgraph 0.6.2 from crates.io using debcargo 2.5.0 * Drop outdated patches * Collapse features . [ Peter Michael Green ] * Team upload. * Package petgraph 0.6.2 from crates.io using debcargo 2.5.0 (Closes: 1019090) * Update patches for new upstream. * Reorder/cleanup patches for easier testing. Checksums-Sha1: 6374b4c1b5aa2eada0ab54baf89cf8ef6383eee3 2365 rust-petgraph_0.6.2-1.dsc 013abe90e09c235d758534fdaa41392ba14e6f7f 182513 rust-petgraph_0.6.2.orig.tar.gz 320f4de6d1868678b35a2e81bf46d87bcccb58a5 6276 rust-petgraph_0.6.2-1.debian.tar.xz 010aeee4f82cdfbe50316fd9536d7a93a7c8f062 9545 rust-petgraph_0.6.2-1_source.buildinfo Checksums-Sha256: 2d5f24d15c8834ad0c522d4434b48ef44799ff39c1c0315bc82dbabbfeb0835f 2365 rust-petgraph_0.6.2-1.dsc e6d5014253a1331579ce62aa67443b4a658c5e7dd03d4bc6d302b94474888143 182513 rust-petgraph_0.6.2.orig.tar.gz 3add9875700554df02fc5399887056a2de219ae575f1912aee1e39243939c88d 6276 rust-petgraph_0.6.2-1.debian.tar.xz 8a2726b8e516e7c05e560a189cc68d48c549a5176a45cd5407172a0f74e86bc5 9545 rust-petgraph_0.6.2-1_source.buildinfo Files: 513c470b72fbc978fa0473d6d195408a 2365 rust optional rust-petgraph_0.6.2-1.dsc e940d7307f0c3c3273dbd91f92b50ce8 182513 rust optional rust-petgraph_0.6.2.orig.tar.gz 27861a05396879b901e36d3cae3c47af 6276 rust optional rust-petgraph_0.6.2-1.debian.tar.xz d1f463c88f190f0b5554acfc14541638 9545 rust optional rust-petgraph_0.6.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmMVGH8UHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XuXHBAAlBi2stvSd28snCwj4jhSliNrRTbr KnGWTDyt48YEYkMxhOuyyVJzs0/VZZnh40Xvvs9vZeSAomh4srjDEdmHwfKINVXU gH63NVqgTXX8OrMLfYhccV5jbjwcN/BtoVQQJPuBoypyfcOCeqm2pZ5dhjr60ssc yFJ77KWTroEBmEzguGiFeDOHL5z9T4H9ePdJqdlknq+i3R3RhoAzUaWVyrtWrqLQ B3BG
Processed: stressapptest: diff for NMU version 1.0.6-2.1
Processing control commands: > tags 1013043 + patch Bug #1013043 [src:stressapptest] stressapptest: ftbfs with GCC-12 Added tag(s) patch. > tags 1013043 + pending Bug #1013043 [src:stressapptest] stressapptest: ftbfs with GCC-12 Added tag(s) pending. -- 1013043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013043: stressapptest: diff for NMU version 1.0.6-2.1
Control: tags 1013043 + patch
Control: tags 1013043 + pending
Dear maintainer,
I've prepared an NMU for stressapptest (versioned as 1.0.6-2.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I should
cancel it.
cu
Adrian
diff -Nru stressapptest-1.0.6/debian/changelog stressapptest-1.0.6/debian/changelog
--- stressapptest-1.0.6/debian/changelog 2015-01-21 02:44:51.0 +0200
+++ stressapptest-1.0.6/debian/changelog 2022-09-05 00:42:31.0 +0300
@@ -1,3 +1,10 @@
+stressapptest (1.0.6-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Backport upstream fix for FTBFS with gcc 12. (Closes: #1013043)
+
+ -- Adrian Bunk Mon, 05 Sep 2022 00:42:31 +0300
+
stressapptest (1.0.6-2) unstable; urgency=medium
* Add i586 support patch. (Closes: #775642)
diff -Nru stressapptest-1.0.6/debian/patches/gcc-12 stressapptest-1.0.6/debian/patches/gcc-12
--- stressapptest-1.0.6/debian/patches/gcc-12 1970-01-01 02:00:00.0 +0200
+++ stressapptest-1.0.6/debian/patches/gcc-12 2022-09-05 00:42:31.0 +0300
@@ -0,0 +1,19 @@
+Description: Backport upstream fix for FTBFS with gcc 12
+Author: Adrian Bunk
+Bug-Debian: https://bugs.debian.org/1013043
+Forwarded: https://github.com/stressapptest/stressapptest/commit/2ea87b7996f4f433d5d946eaf8f0d2f6fd18c144
+
+--- stressapptest-1.0.6.orig/src/worker.cc
stressapptest-1.0.6/src/worker.cc
+@@ -2989,8 +2989,9 @@ bool DiskThread::AsyncDiskIO(IoOp op, in
+ errorcount_++;
+ os_->ErrorReport(device_name_.c_str(), operations[op].error_str, 1);
+
+-if (event.res < 0) {
+- switch (event.res) {
++int64 result = static_cast(event.res);
++if (result < 0) {
++ switch (result) {
+ case -EIO:
+ logprintf(0, "Hardware Error: Low-level I/O error while doing %s to "
+"sectors starting at %lld on disk %s (thread %d).\n",
diff -Nru stressapptest-1.0.6/debian/patches/series stressapptest-1.0.6/debian/patches/series
--- stressapptest-1.0.6/debian/patches/series 2015-01-21 02:44:51.0 +0200
+++ stressapptest-1.0.6/debian/patches/series 2022-09-05 00:42:31.0 +0300
@@ -1,3 +1,4 @@
armhf_support
support_i486_builds
support_i586_builds
+gcc-12
Bug#1019144: marked as done (librust-dialoguer-dev: impossible to install)
Your message dated Sun, 04 Sep 2022 21:21:21 + with message-id and subject line Bug#1019144: fixed in rust-dialoguer 0.10.2-1 has caused the Debian Bug report #1019144, regarding librust-dialoguer-dev: impossible to install 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.) -- 1019144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-dialoguer-dev Version: 0.10.1-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Binary package librust-dialoguer-dev is impossible to install, as it depends on unavailable package librust-fuzzy-matcher-0.3+default-dev - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmMUwWQACgkQLHwxRsGg ASFFig/+NpM/heUD2TaGbHpZhmAdIvpWf6iXZ4Q+g/YTUnVXc1YUy9GsG8RrqYn+ YIu3phL//Tj7FCveoxSfWqbk4gXU4oTP12KcIKNkGJFHijqRWn8R1/q16GmfvIxQ A1xIBpwFx8mGWjbpysLGR5lz50mf4A2RmefXy04tkt5+t3ghEXUssPEUWwmYMRKD XSAOhkC9h7U3kNWiJSi7lq9lsV/45gMtaYLSGFU/LEfNpUpMh53OIxb2fYCs4xw0 IsfqkEd+J78IuQ8rqOG3CipVvZfsQqn+MEUtDrPEBdwuSD9bOjUSUQqIvklLQECu 8fYgpTWRM/ICWFQqkr5YIwh9iHk/+Ppk0ssa4UF1pm2XLUXLZZCHvNkjukboQIhu 1DYz1jLgNhrKjpaIWqh+XBb0AvzWfjTWa2f8bbTATI4W1cREiGgA1CpoD7NPZblj FdBQn8p4i33Ls0d88BCXOjaHXe1rE79HAH4ByksXdzQ+J2NocWeYKqBR0xbq0fkE EeVCeMdUM82qBBfH+cR6IfBYQnp909dBQrSWezIq3sDBJHbdd6biJG0zsbOzYU4z A/z/bpz/9nKHHSTZi/v/dBvg8EcF+d1w8EOF1FOAfDpOj+qwZPMlJ2ntHzXIvssZ LzwKRZwNnaSTwWqg4pAULfvNbOaDbPBDNBXtJ8qzPPUCrY0XT5w= =9O94 -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: rust-dialoguer Source-Version: 0.10.2-1 Done: Philip Rinn We believe that the bug you reported is fixed in the latest version of rust-dialoguer, 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 1019...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Philip Rinn (supplier of updated rust-dialoguer 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: Sun, 04 Sep 2022 23:04:30 +0200 Source: rust-dialoguer Architecture: source Version: 0.10.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Philip Rinn Closes: 1019144 Changes: rust-dialoguer (0.10.2-1) unstable; urgency=medium . * Package dialoguer 0.10.2 from crates.io using debcargo 2.5.0 * Disable feature fuzzy-select (Closes: #1019144) Checksums-Sha1: d0c7b5a724e329b3ef108986521d4e06495e68b4 2321 rust-dialoguer_0.10.2-1.dsc 110ebb7c8ae80fb23bbe91519169083cfa5cfce7 25304 rust-dialoguer_0.10.2.orig.tar.gz aeeebf7ea4df043d3ef9168ed17f5ff717d18525 3496 rust-dialoguer_0.10.2-1.debian.tar.xz 1ed792deaddee6009d09230a6ae3afbd3b574644 8132 rust-dialoguer_0.10.2-1_source.buildinfo Checksums-Sha256: d1ad5730843ba291b33c97b825a4c1e60ab64dff1cb58547e1d5ad2a9fbbfbb4 2321 rust-dialoguer_0.10.2-1.dsc a92e7e37ecef6857fdc0c0c5d42fd5b0938e46590c2183cc92dd310a6d078eb1 25304 rust-dialoguer_0.10.2.orig.tar.gz 6135e155aab09fd4c538105eff4568595a6efe0826e928f88b3b4139e7fed971 3496 rust-dialoguer_0.10.2-1.debian.tar.xz d1f44f01553d57cceb2f39e0fa695b3656abd6bc47c677ba45ef0dbd38b50038 8132 rust-dialoguer_0.10.2-1_source.buildinfo Files: 64f6a9fbc3cccb657b9f42358d666289 2321 rust optional rust-dialoguer_0.10.2-1.dsc 05b3b5c8612bfda2018f4fa30600c2a0 25304 rust optional rust-dialoguer_0.10.2.orig.tar.gz 19f5afe38e208c13d9c9ad346748c594 3496 rust optional rust-dialoguer_0.10.2-1.debian.tar.xz 3551684d7c57f1b4a8a2f96897002e72 8132 rust optional rust-dialoguer_0.10.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEK9jU45eVX3dG2zuJrWkWlnOTmCsFAmMVEu8ACgkQrWkWlnOT mCtK3w//a3uoZJ9J5uqjWHUikFI8s2MyP4GWSXS4R8ToOLwhcWl0qNtTMPWAI597 TxCHTN1czb1Qt943KlgimRqrX91VXBhcvab85NmyOHoTIArz+XXWpVsyK2DqLfXf kawXzpXiIVYiOUbOwh+H4+peikhYmfiFK8wGKq8Lgeb/mPSz0Jc5ksBrw8L/gY+U TkmhEm6LmMlN4Nb423tmVSrUp5NoGT5EenNJYp0W/FeBlmC/LO9mtPHUUJKZQGIJ RmqSHUs7N7LLawEpBaPqoqT0uM3G9Yc/jLYoB4vkKdeOrK6ohcek+ZER1WpykqkV mJxL3ljICVtEdcCRLC7d/AlX5mHkj0bt705MG+WDgZLAhZdbkiIcb45OXoymuJXq idAL/1Ud/EmNfKTZQGo/sutduLTZFbsauEXqGvDebc1AWfMlvlyfDay8lyU8HJ6u WlkZcE0uJ2KCeb8+Rm4arbhVV43cHlr/
Bug#1017637: marked as done (havp: Not working anymore since linux-image-* v5.15.)
Your message dated Sun, 04 Sep 2022 21:19:37 + with message-id and subject line Bug#1018907: Removed package(s) from unstable has caused the Debian Bug report #1017637, regarding havp: Not working anymore since linux-image-* v5.15. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1017637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: havp Version: 0.93-2 Severity: grave While testing havp before uploading I noticed that starting havp ends quickly with: | Starting HAVP Version: 0.93 | Filesystem not supporting mandatory locks! | On Linux, you need to mount filesystem with "-o mand" The so called "mandatory locks" have been removed from the Linux kernel in v5.15 [0]. havp is compiled to use it and fails to continue if it is not working. We have to options now: - Remove havp from unstable. - Pass --disable-locking to configure and build it without it. This forces havp to download everything scan it first. I'm not a user of havp so I can't tell if disabling locking is an option. There is a script with loopback mount and everything just to use the locking without enabling it on the main partition. The first 5.15 kernel was uploaded by the end of 2021 and this went unnoticed until now. Probably even longer if it wasn't for #1016270. Given that and the dropping popcon numbers, I lean towards RM. Anyone? [0] https://git.kernel.org/torvalds/c/f7e33bdbd6d1bdf9c3df8bba5abcf3399f957ac3 Sebastian --- End Message --- --- Begin Message --- Version: 0.93-2+rm Dear submitter, as the package havp has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1018907 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---
Bug#1016270: marked as done (havp: FTBFS: logfile.cpp:111:22: error: ‘time’ was not declared in this scope)
Your message dated Sun, 04 Sep 2022 21:19:37 +
with message-id
and subject line Bug#1018907: Removed package(s) from unstable
has caused the Debian Bug report #1016270,
regarding havp: FTBFS: logfile.cpp:111:22: error: ‘time’ was not declared in
this scope
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.)
--
1016270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: havp
Version: 0.93-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2
> -I/usr/include -Wall -g -O2 -DHAVE_CONFIG_H -c -o sockethandler.o
> sockethandler.cpp
> sockethandler.cpp: In member function ‘int
> SocketHandler::CheckForSSLData(int, int)’:
> sockethandler.cpp:584:20: warning: operation on
> ‘((SocketHandler*)this)->SocketHandler::Timeout.timeval::tv_sec’ may be
> undefined [-Wsequence-point]
> 584 | Timeout.tv_sec = Timeout.tv_sec =
> Params::GetConfigInt("SSLTIMEOUT");
> |
> ~~~^
> logfile.cpp: In static member function ‘static void
> LogFile::AccessMessage(const char*, ...)’:
> logfile.cpp:111:22: error: ‘time’ was not declared in this scope
> 111 | time_t now = time(NULL);
> | ^~~~
> logfile.cpp:33:1: note: ‘time’ is defined in header ‘’; did you forget
> to ‘#include ’?
>32 | #include
> +++ |+#include
>33 |
> logfile.cpp:112:19: error: variable ‘tm TmDate’ has initializer but
> incomplete type
> 112 | struct tm TmDate = *localtime(&now);
> | ^~
> logfile.cpp:112:29: error: ‘localtime’ was not declared in this scope
> 112 | struct tm TmDate = *localtime(&now);
> | ^
> logfile.cpp:112:29: note: ‘localtime’ is defined in header ‘’; did you
> forget to ‘#include ’?
> logfile.cpp:113:9: error: ‘strftime’ was not declared in this scope
> 113 | strftime(tmpdate, 50, TimeFormat.c_str(), &TmDate);
> | ^~~~
> logfile.cpp:113:9: note: ‘strftime’ is defined in header ‘’; did you
> forget to ‘#include ’?
> logfile.cpp:115:32: warning: argument to ‘sizeof’ in ‘char* strncpy(char*,
> const char*, size_t)’ call is the same expression as the source; did you mean
> to use the size of the destination? [-Wsizeof-pointer-memaccess]
> 115 | strncpy(strt, tmpdate, sizeof(tmpdate));
> |^~~
> logfile.cpp: In static member function ‘static void
> LogFile::VirusMessage(const char*, ...)’:
> logfile.cpp:141:22: error: ‘time’ was not declared in this scope
> 141 | time_t now = time(NULL);
> | ^~~~
> logfile.cpp:141:22: note: ‘time’ is defined in header ‘’; did you
> forget to ‘#include ’?
> logfile.cpp:142:19: error: variable ‘tm TmDate’ has initializer but
> incomplete type
> 142 | struct tm TmDate = *localtime(&now);
> | ^~
> logfile.cpp:142:29: error: ‘localtime’ was not declared in this scope
> 142 | struct tm TmDate = *localtime(&now);
> | ^
> logfile.cpp:142:29: note: ‘localtime’ is defined in header ‘’; did you
> forget to ‘#include ’?
> logfile.cpp:143:9: error: ‘strftime’ was not declared in this scope
> 143 | strftime(tmpdate, 50, TimeFormat.c_str(), &TmDate);
> | ^~~~
> logfile.cpp:143:9: note: ‘strftime’ is defined in header ‘’; did you
> forget to ‘#include ’?
> logfile.cpp:145:32: warning: argument to ‘sizeof’ in ‘char* strncpy(char*,
> const char*, size_t)’ call is the same expression as the source; did you mean
> to use the size of the destination? [-Wsizeof-pointer-memaccess]
> 145 | strncpy(strt, tmpdate, sizeof(tmpdate));
> |^~~
> logfile.cpp: In static member function ‘static void
> LogFile::ErrorMessage(const char*, ...)’:
> logfile.cpp:171:22: error: ‘time’ was not declared in this scope
> 171 | time_t now = time(NULL);
> | ^~~~
> logfile.cpp:171:22: note: ‘time’ is defined in header ‘’; did you
> forget to ‘#include ’?
> logfile.cpp:172:19: error: variable ‘tm
Bug#966748: marked as done (grokmirror: Unversioned Python removal in sid/bullseye)
Your message dated Sun, 04 Sep 2022 21:14:47 + with message-id and subject line Bug#1015981: Removed package(s) from unstable has caused the Debian Bug report #936665, regarding grokmirror: Unversioned Python removal in sid/bullseye 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.) -- 936665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:grokmirror Version: 1.0.0-1.1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.0.0-1.1+rm Dear submitter, as the package grokmirror has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1015981 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---
Bug#936665: marked as done (grokmirror: Python2 removal in sid/bullseye)
Your message dated Sun, 04 Sep 2022 21:14:47 + with message-id and subject line Bug#1015981: Removed package(s) from unstable has caused the Debian Bug report #936665, regarding grokmirror: Python2 removal in sid/bullseye 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.) -- 936665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:grokmirror Version: 1.0.0-1.1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:grokmirror If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.0.0-1.1+rm Dear submitter, as the package grokmirror has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1015981 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---
Bug#967193: marked as done (pd-aubio: Unversioned Python removal in sid/bullseye)
Your message dated Sun, 04 Sep 2022 21:13:41 + with message-id and subject line Bug#1015980: Removed package(s) from unstable has caused the Debian Bug report #967193, regarding pd-aubio: Unversioned Python removal in sid/bullseye 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.) -- 967193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967193 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pd-aubio Version: 0.4-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.4-1+rm Dear submitter, as the package pd-aubio has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1015980 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---
Bug#1019158: graphicsmagick breaks gnudatalanguage autopkgtest: undefined symbol: _ZN6Magick5Image12colorMapSizeEv
On Sun, Sep 4, 2022 at 10:27 PM Paul Gevers wrote: > With a recent upload of graphicsmagick the autopkgtest of > gnudatalanguage fails in testing when that autopkgtest is run with the > binary packages of graphicsmagick from unstable. I will check this and see what may cause it. > I copied some of the output at the bottom of this report. It looks like > graphicsmagick dropped a symbol that was actually used. Was that a mistake? According to my double check, no symbol was removed. Quite the opposite, one (IsEventLogged@Base) was added. > Currently this regression is blocking the migration of graphicsmagick to > testing [1]. Can you please investigate the situation? Nope, at least the first reason it's not migrating its FTBFS on mips64el. Already contacted upstream and it's not yet known what causes it. Might be some floating point issue on that architecture. > gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: > undefined symbol: _ZN6Magick5Image12colorMapSizeEv Strange, I might think it's somehow related to GCC 12 changes. Regards, Laszlo/GCS
Bug#1019163: rust-smol - unsatisfiable build-dependency
Package: rust-smol Version: 1.2.5-2 Severity: serious rust-smol build-depends on librust-nix-0.24+default-dev but the nix crate in debian testing/unstable is now at 0.25
Bug#1001593: marked as done (php-easyrdf: flaky autopkgtest: Unable to connect to localhost:10101)
Your message dated Sun, 04 Sep 2022 20:36:56 + with message-id and subject line Bug#1001593: fixed in php-easyrdf 1.0.0-3 has caused the Debian Bug report #1001593, regarding php-easyrdf: flaky autopkgtest: Unable to connect to localhost:10101 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.) -- 1001593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001593 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-easyrdf Version: 1.0.0-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of you package on ppc64el because it was showing up as a regression for the upload of curl in stable. I noticed that the test regularly fails, not only on ppc64el. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. In this case, Release Team members had to investigate if curl was OK to go into the next Stable point release. Don't hesitate to reach out if you need help and some more information from our infrastructure. Paul https://ci.debian.net/packages/p/php-easyrdf/testing/ppc64el/ https://ci.debian.net/packages/p/php-easyrdf/stable/ppc64el/ OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: php-easyrdf Source-Version: 1.0.0-3 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of php-easyrdf, 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 1001...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated php-easyrdf 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: Sun, 04 Sep 2022 21:35:19 +0200 Source: php-easyrdf Architecture: source Version: 1.0.0-3 Distribution: unstable Urgency: medium Maintainer: Debian PHP PEAR Maintainers Changed-By: Paul Gevers Closes: 1001593 Changes: php-easyrdf (1.0.0-3) unstable; urgency=medium . * Team upload . [ Marco Villegas ] * Check server output on rapper smoke test. Closes: #1001593. Checksums-Sha1: b83ac0b13e7371175a135125d1149e21f2ff61ec 1823 php-easyrdf_1.0.0-3.dsc cd08af9a8630e2966d08196e5e17ed667bf9fe0a 5372 php-easyrdf_1.0.0-3.debian.tar.xz Checksums-Sha256: 90109d3a5e404c1cf38b57aee1310c386a8930118828ade13420b1b9443c88fa 1823 php-easyrdf_1.0.0-3.dsc 81f5c3437ae0d8d9181190e6ee9bcc146b451a1278a73514b7df7a86a1177fc8 5372 php-easyrdf_1.0.0-3.debian.tar.xz Files: 79d75c09173dc66a782a8d8d995ba743 1823 php optional php-easyrdf_1.0.0-3.dsc f727a01c8f5521337f6e748cdb79681b 5372 php optional php-easyrdf_1.0.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmMVANUACgkQnFyZ6wW9 dQp5kwf/djwtBpyXEGbAVG7jE9DjtZIWPcDn57BzBdQ3k494f+lg0+DRnS+zUzRa iaHTFiJ8qc9SN6dK2Q96tWhuz/huB7N/TTv7RfNm4EaK4Rhv9VEI8ck/vTSzUAeS EIir2ZpolWrfamuWmL8yxgWmvzVr5tndglDE0hIGKCR7vrYGRqX+zv+S9I0IkcEW KJr+i1JDhiDHdjrlOeb5ZObJeXySbs/FFsQDipF9bvqHdUTWmj9/hK7hT0uU26Ff QODyPYtKu5KzdT+1JJhcxO9SK3Lu3dZI/tEv+i9GEGBBUPmULnpptgMXmmILoV8t Qfc4jfxQuAyyq6wkdfEaKcf1dYJZ+g== =DxAq -END PGP SIGNATURE End Message ---
Processed: limit source to aspcud, tagging 1017131
Processing commands for cont...@bugs.debian.org: > limit source aspcud Limiting to bugs with field 'source' containing at least one of 'aspcud' Limit currently set to 'source':'aspcud' > tags 1017131 + pending Bug #1017131 [src:aspcud] aspcud: FTBFS: catch.hpp:10822:58: error: call to non-‘constexpr’ function ‘long int sysconf(int)’ Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1017131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019158: graphicsmagick breaks gnudatalanguage autopkgtest: undefined symbol: _ZN6Magick5Image12colorMapSizeEv
Source: graphicsmagick Control: found -1 graphicsmagick/1.4+really1.3.38+hg16728-1 Affects: -1 src:gnudatalanguage Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks Dear maintainer(s), With a recent upload of graphicsmagick the autopkgtest of gnudatalanguage fails in testing when that autopkgtest is run with the binary packages of graphicsmagick from unstable. It passes when run with only packages from testing. In tabular form: passfail graphicsmagick from testing1.4+really1.3.38+hg16728-1 gnudatalanguagefrom testing1.0.1-3 all others from testingfrom testing I copied some of the output at the bottom of this report. It looks like graphicsmagick dropped a symbol that was actually used. Was that a mistake? Currently this regression is blocking the migration of graphicsmagick to testing [1]. Can you please investigate the situation? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=graphicsmagick https://ci.debian.net/data/autopkgtest/testing/amd64/g/gnudatalanguage/25681414/log.gz gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Magick5Image12colorMapSizeEv gdl: symbol lookup error: /lib/x86_64-linux-gnu/libgnudatalanguage.so.0: undefined symbol: _ZN6Ma
Processed: graphicsmagick breaks gnudatalanguage autopkgtest: undefined symbol: _ZN6Magick5Image12colorMapSizeEv
Processing control commands: > found -1 graphicsmagick/1.4+really1.3.38+hg16728-1 Bug #1019158 [src:graphicsmagick] graphicsmagick breaks gnudatalanguage autopkgtest: undefined symbol: _ZN6Magick5Image12colorMapSizeEv Marked as found in versions graphicsmagick/1.4+really1.3.38+hg16728-1. -- 1019158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019156: nbconvert: autopkgtest regression: SyntaxError: invalid escape sequence
Source: nbconvert
Version: 6.5.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of nbconvert the autopkgtest of nbconvert fails in
testing when that autopkgtest is run with the binary packages of
nbconvert from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
nbconvert from testing6.5.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 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=nbconvert
https://ci.debian.net/data/autopkgtest/testing/amd64/n/nbconvert/25709432/log.gz
[1m= test session starts
==[0m
platform linux -- Python 3.10.6, pytest-7.1.2, pluggy-1.0.0+repack
rootdir: /tmp/autopkgtest-lxc.7b1y4lix/downtmp/build.PuB/src,
configfile: pyproject.toml, testpaths: nbconvert/
collected 0 items / 1 error
ERRORS
[31m[1m ERROR collecting test session
_[0m
[1m[31m/usr/lib/python3.10/importlib/__init__.py[0m:126: in import_module
[94mreturn[39;49;00m _bootstrap._gcd_import(name[level:],
package, level)
[1m[31m[0m:1050: in _gcd_import
[04m[91m?[39;49;00m[04m[91m?[39;49;00m[04m[91m?[39;49;00m
[1m[31m[0m:1027: in _find_and_load
[04m[91m?[39;49;00m[04m[91m?[39;49;00m[04m[91m?[39;49;00m
[1m[31m[0m:992: in _find_and_load_unlocked
[04m[91m?[39;49;00m[04m[91m?[39;49;00m[04m[91m?[39;49;00m
[1m[31m[0m:241: in _call_with_frames_removed
[04m[91m?[39;49;00m[04m[91m?[39;49;00m[04m[91m?[39;49;00m
[1m[31m[0m:1050: in _gcd_import
[04m[91m?[39;49;00m[04m[91m?[39;49;00m[04m[91m?[39;49;00m
[1m[31m[0m:1027: in _find_and_load
[04m[91m?[39;49;00m[04m[91m?[39;49;00m[04m[91m?[39;49;00m
[1m[31m[0m:1006: in _find_and_load_unlocked
[04m[91m?[39;49;00m[04m[91m?[39;49;00m[04m[91m?[39;49;00m
[1m[31m[0m:688: in _load_unlocked
[04m[91m?[39;49;00m[04m[91m?[39;49;00m[04m[91m?[39;49;00m
[1m[31m[0m:883: in exec_module
[04m[91m?[39;49;00m[04m[91m?[39;49;00m[04m[91m?[39;49;00m
[1m[31m[0m:241: in _call_with_frames_removed
[04m[91m?[39;49;00m[04m[91m?[39;49;00m[04m[91m?[39;49;00m
[1m[31mnbconvert/__init__.py[0m:3: in
[94mfrom[39;49;00m [04m[96m.[39;49;00m [94mimport[39;49;00m
filters, postprocessors, preprocessors, writers
[1m[31mnbconvert/filters/__init__.py[0m:8: in
[94mfrom[39;49;00m
[04m[96m.[39;49;00m[04m[96mmarkdown[39;49;00m [94mimport[39;49;00m *
[1m[31mnbconvert/filters/markdown.py[0m:13: in
[94mfrom[39;49;00m
[04m[96m.[39;49;00m[04m[96mmarkdown_mistune[39;49;00m
[94mimport[39;49;00m markdown2html_mistune
[1m[31mnbconvert/filters/markdown_mistune.py[0m:24: in
[94mimport[39;49;00m
[04m[96mnbconvert[39;49;00m[04m[96m.[39;49;00m[04m[96mfilters[39;49;00m[04m[96m.[39;49;00m[04m[96m_mistune[39;49;00m
[94mas[39;49;00m [04m[96mmistune[39;49;00m
[1m[31mE File
"/tmp/autopkgtest-lxc.7b1y4lix/downtmp/build.PuB/src/nbconvert/filters/_mistune.py",
line 435[0m
[1m[31mE cells[i][c] = re.sub('\|', '|', cell)[0m
[1m[31mE[0m
[1m[31mE SyntaxError: invalid escape sequence '\|'[0m
=== short test summary info
ERROR - File
"/tmp/autopkgtest-lxc.7b1y4lix/downtmp/build.PuB/src/nbconver...
Interrupted: 1 error during collection
[31m=== [31m[1m1 error[0m[31m in
0.22s[0m[31m ===[0m
autopkgtest [14:15:27]: test command1
OpenPGP_signature
Description: OpenPGP digital signature
Processed: nbconvert breaks nbclient autopkgtest: No module named 'testpath'
Processing control commands: > found -1 nbconvert/6.5.1-1 Bug #1019155 [src:nbconvert, src:nbclient] nbconvert breaks nbclient autopkgtest: No module named 'testpath' Marked as found in versions nbconvert/6.5.1-1. > found -1 nbclient/0.6.6-1 Bug #1019155 [src:nbconvert, src:nbclient] nbconvert breaks nbclient autopkgtest: No module named 'testpath' Marked as found in versions nbclient/0.6.6-1. -- 1019155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019155: nbconvert breaks nbclient autopkgtest: No module named 'testpath'
Source: nbconvert, nbclient Control: found -1 nbconvert/6.5.1-1 Control: found -1 nbclient/0.6.6-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of nbconvert the autopkgtest of nbclient fails in testing when that autopkgtest is run with the binary packages of nbconvert from unstable. It passes when run with only packages from testing. In tabular form: passfail nbconvert from testing6.5.1-1 nbclient from testing0.6.6-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 nbconvert 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=nbconvert https://ci.debian.net/data/autopkgtest/testing/amd64/n/nbclient/25713974/log.gz = test session starts == platform linux -- Python 3.10.6, pytest-7.1.2, pluggy-1.0.0+repack rootdir: /usr/lib/python3/dist-packages/nbclient collected 5 items / 1 error ERRORS ERROR collecting tests/test_client.py _ ImportError while importing test module '/usr/lib/python3/dist-packages/nbclient/tests/test_client.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.10/importlib/__init__.py:126: in import_module return _bootstrap._gcd_import(name[level:], package, level) /usr/lib/python3/dist-packages/nbclient/tests/test_client.py:22: in from testpath import modified_env E ModuleNotFoundError: No module named 'testpath' OpenPGP_signature Description: OpenPGP digital signature
Bug#997220: marked as done (eclipse-jdt-ui: FTBFS: [javac] /<>/org.eclipse.jdt.ui/target/sources/org/eclipse/jdt/internal/ui/fix/PatternMatchingForInstanceofCleanUp.java:144: error: c
Your message dated Sun, 4 Sep 2022 21:56:16 +0200 with message-id and subject line Closing: eclipse-jdt-ui: FTBFS: [javac] ... has caused the Debian Bug report #997220, regarding eclipse-jdt-ui: FTBFS: [javac] /<>/org.eclipse.jdt.ui/target/sources/org/eclipse/jdt/internal/ui/fix/PatternMatchingForInstanceofCleanUp.java:144: error: cannot find symbol 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.) -- 997220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: eclipse-jdt-ui Version: 4.18-1 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): > debian/rules build > dh build --buildsystem=eclipse_bundles >dh_update_autotools_config -O--buildsystem=eclipse_bundles >dh_autoreconf -O--buildsystem=eclipse_bundles >dh_auto_configure -O--buildsystem=eclipse_bundles >dh_auto_build -O--buildsystem=eclipse_bundles > ant -Dbasedir . -Dbundledir . -f debian/build.xml > org.eclipse.jdt.astview org.eclipse.jdt.core.manipulation > org.eclipse.jdt.junit.core org.eclipse.jdt.junit.runtime > org.eclipse.jdt.junit4.runtime org.eclipse.jdt.ui > org.eclipse.ltk.core.refactoring org.eclipse.ltk.ui.refactoring -Duser.name > debian > Buildfile: /<>/debian/build.xml > > org.eclipse.ltk.core.refactoring: > [echo] Building bundle 'Refactoring Core' > (org.eclipse.ltk.core.refactoring:3.11.200) > [mkdir] Created dir: > /<>/org.eclipse.ltk.core.refactoring/target/classes > [touch] Creating > /<>/org.eclipse.ltk.core.refactoring/target/dependencies > [mkdir] Created dir: > /<>/org.eclipse.ltk.core.refactoring/target/sources > [copy] Copying 144 files to > /<>/org.eclipse.ltk.core.refactoring/target/sources > [javac] Compiling 144 source files to > /<>/org.eclipse.ltk.core.refactoring/target/classes > [javac] Note: Some input files use or override a deprecated API. > [javac] Note: Recompile with -Xlint:deprecation for details. > [copy] Copying 6 files to > /<>/org.eclipse.ltk.core.refactoring/target/classes > [jar] Building jar: > /<>/org.eclipse.ltk.core.refactoring/target/org.eclipse.ltk.core.refactoring.jar > [copy] Copying 1 file to > /<>/org.eclipse.ltk.core.refactoring/target > > org.eclipse.jdt.core.manipulation: > [echo] Building bundle 'Java Code Manipulation Functionality' > (org.eclipse.jdt.core.manipulation:1.14.200) > [mkdir] Created dir: > /<>/org.eclipse.jdt.core.manipulation/target/classes > [touch] Creating > /<>/org.eclipse.jdt.core.manipulation/target/dependencies > [mkdir] Created dir: > /<>/org.eclipse.jdt.core.manipulation/target/sources > [copy] Copying 403 files to > /<>/org.eclipse.jdt.core.manipulation/target/sources > [javac] Compiling 403 source files to > /<>/org.eclipse.jdt.core.manipulation/target/classes > [javac] Note: Some input files use or override a deprecated API. > [javac] Note: Recompile with -Xlint:deprecation for details. > [javac] Note: Some input files use unchecked or unsafe operations. > [javac] Note: Recompile with -Xlint:unchecked for details. > [copy] Copying 19 files to > /<>/org.eclipse.jdt.core.manipulation/target/classes > [jar] Building jar: > /<>/org.eclipse.jdt.core.manipulation/target/org.eclipse.jdt.core.manipulation.jar > [copy] Copying 1 file to > /<>/org.eclipse.jdt.core.manipulation/target > > org.eclipse.ltk.ui.refactoring: > [echo] Building bundle 'Refactoring UI' > (org.eclipse.ltk.ui.refactoring:3.11.200) > [mkdir] Created dir: > /<>/org.eclipse.ltk.ui.refactoring/target/classes > [touch] Creating > /<>/org.eclipse.ltk.ui.refactoring/target/dependencies > [mkdir] Created dir: > /<>/org.eclipse.ltk.ui.refactoring/target/sources > [copy] Copying 126 files to > /<>/org.eclipse.ltk.ui.refactoring/target/sources > [javac] Compiling 126 source files to > /<>/org.eclipse.ltk.ui.refactoring/target/classes > [javac] Note: Some input files use or override a deprecated API. > [javac] Note: Recompile with -Xlint:deprecation for details. > [copy] Copying 49 files to > /<>/org.eclipse.ltk.ui.refactoring/target/classes > [jar] Building jar: > /<>/org.eclipse.ltk.ui.refactoring/target/org.eclipse.ltk.ui.refactoring.jar > [copy] Copying 1 file to > /<>/org.eclipse.ltk.ui.refactoring/target > > org.eclipse.jdt.ui: > [echo] Building bundle 'Java Development Tools UI'
Bug#1019154: golang-github-xi2-xz: autopkgtest fails: testdata/other/bad-0-backward_size.xz: no such file or directory
Source: golang-github-xi2-xz Version: 0.0~git20171230.48954b6-1 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), Your package has an autopkgtest, great. However, it fails. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/packages/g/golang-github-xi2-xz/ https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-xi2-xz/25124641/log.gz dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 in use) cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/xi2/xz === RUN TestBadFiles reader_test.go:445: open testdata/other/bad-0-backward_size.xz: no such file or directory --- FAIL: TestBadFiles (0.00s) === RUN TestGoodFiles reader_test.go:445: open testdata/other/good-0cat-empty.xz: no such file or directory --- FAIL: TestGoodFiles (0.00s) === RUN TestUnsupportedFiles reader_test.go:445: open testdata/other/unsupported-block_header.xz: no such file or directory --- FAIL: TestUnsupportedFiles (0.00s) === RUN TestOtherFiles reader_test.go:445: open testdata/other/good-1-x86-lzma2-offset-2048.xz: no such file or directory --- FAIL: TestOtherFiles (0.00s) === RUN TestMemlimit reader_test.go:528: open testdata/other/words.xz: no such file or directory --- FAIL: TestMemlimit (0.00s) === RUN TestPrematureError reader_test.go:545: open testdata/other/good-2-lzma2-corrupt.xz: no such file or directory --- FAIL: TestPrematureError (0.00s) === RUN TestMultipleBadReads reader_test.go:570: open testdata/other/good-2-lzma2-corrupt.xz: no such file or directory --- FAIL: TestMultipleBadReads (0.00s) === RUN TestByteReads reader_test.go:478: open testdata/other/bad-0-backward_size.xz: no such file or directory --- FAIL: TestByteReads (0.00s) === RUN TestMultistream reader_test.go:624: open testdata/other/good-1-x86-lzma2-offset-2048.xz: no such file or directory --- FAIL: TestMultistream (0.00s) === RUN TestReuseReader reader_test.go:445: open testdata/other/bad-0-backward_size.xz: no such file or directory --- FAIL: TestReuseReader (0.00s) === RUN TestReuseReaderPartialReads reader_test.go:678: open testdata/other/words.xz: no such file or directory --- FAIL: TestReuseReaderPartialReads (0.00s) === RUN ExampleNewReader 2022/08/23 15:26:15 open testdata/xz-utils/good-1-check-sha256.xz: no such file or directory FAILgithub.com/xi2/xz 0.002s FAIL dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/xi2/xz returned exit code 1 make: *** [debian/rules:9: build] Error 25 autopkgtest [15:26:15]: test dh-golang-autopkgtest: ---] OpenPGP_signature Description: OpenPGP digital signature
Bug#1019152: python-bonsai: flaky autopkgtest on armhf and armel: timeout too short?
Source: python-bonsai
Version: 1.3.0+ds-3
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of your package. I noticed
that it regularly fails on armel and armhf.
Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.
Don't hesitate to reach out if you need help and some more information
from our infrastructure.
Paul
https://ci.debian.net/data/autopkgtest/testing/armel/p/python-bonsai/24971339/log.gz
=== FAILURES
===
__ test_open
___
client =
def test_open(client):
""" Test opening the pool. """
pool = ConnectionPool(client, minconn=5)
> pool.open()
tests/test_pool.py:35:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
/usr/lib/python3/dist-packages/bonsai/pool.py:70: in open
self._idles.add(self._client.connect(self._kwargs))
/usr/lib/python3/dist-packages/bonsai/ldapclient.py:675: in connect
return LDAPConnection(self).open(timeout)
/usr/lib/python3/dist-packages/bonsai/ldapconnection.py:297: in open
return super().open(timeout)
/usr/lib/python3/dist-packages/bonsai/ldapconnection.py:53: in open
return self._evaluate(super().open(), timeout)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
self = ,
msg_id = -1
timeout = None
def _evaluate(self, msg_id: int, timeout: Optional[float] = None)
-> Any:
"""
It returns the result of the LDAP operation.
:param int msg_id: the ID of the LDAP operation.
:param float timeout: time limit in seconds for the operation.
:return: the result of the operation.
"""
> return self.get_result(msg_id, timeout)
E bonsai.errors.TimeoutError: Timed out. (0xFFFB [-5])
/usr/lib/python3/dist-packages/bonsai/ldapconnection.py:246: TimeoutError
___ test_get
___
self =
def get(self):
"""
Get a connection from the connection pool.
:raises EmptyPool: when the pool is empty.
:raises ClosedPool: when the method is called on a closed pool.
:return: an LDAP connection object.
"""
if self._closed:
raise ClosedPool("The pool is closed.")
try:
> conn = self._idles.pop()
E KeyError: 'pop from an empty set'
/usr/lib/python3/dist-packages/bonsai/pool.py:84: KeyError
During handling of the above exception, another exception occurred:
client =
def test_get(client):
""" Test getting a connection from the pool. """
pool = ConnectionPool(client, minconn=1, maxconn=2)
with pytest.raises(ClosedPool):
_ = pool.get()
pool.open()
assert pool.max_connection == 2
assert pool.idle_connection == 1
assert pool.shared_connection == 0
conn1 = pool.get()
assert conn1 is not None
assert conn1.closed == False
assert pool.idle_connection == 0
assert pool.shared_connection == 1
> conn2 = pool.get()
tests/test_pool.py:66:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
/usr/lib/python3/dist-packages/bonsai/pool.py:87: in get
conn = self._client.connect(self._kwargs)
/usr/lib/python3/dist-packages/bonsai/ldapclient.py:675: in connect
return LDAPConnection(self).open(timeout)
/usr/lib/python3/dist-packages/bonsai/ldapconnection.py:297: in open
return super().open(timeout)
/usr/lib/python3/dist-packages/bonsai/ldapconnection.py:53: in open
return self._evaluate(super().open(), timeout)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
self = ,
msg_id = -1
timeout = None
def _evaluate(self, msg_id: int, timeout: Optional[float] = None)
-> Any:
"""
It returns the result of the LDAP operation.
:param int msg_id: the ID of the LDAP operation.
:param float timeout: time limit in seconds for the operation.
:return: the result of the operation.
"""
> return self.get_result(msg_id, timeout)
E bonsai.errors.TimeoutError: Timed out. (0xFFFB [-5])
/usr/lib/python3/dist-packages/bonsai/ldapconnection.py:246: TimeoutError
___ test_threaded_pool_block
___
client =
def test_threaded_pool_block(client):
""" Test threaded pool blocks when it's empty. """
sleep = 5
pool = ThreadedConnectionPool(client, minconn=1, maxconn=1)
> pool.open()
tests/test_pool.py:123:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Bug#1019151: pydevd: flaky autopkgtest on armel: timeout too short?
Source: pydevd Version: 2.8.0+git20220602.1b1fb8b+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package. I noticed that it regularly fails on armel. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Don't hesitate to reach out if you need help and some more information from our infrastructure. Paul https://ci.debian.net/packages/p/pydevd/testing/armel/ https://ci.debian.net/data/autopkgtest/testing/armel/p/pydevd/25054651/log.gz OpenPGP_signature Description: OpenPGP digital signature
Bug#1014707: marked as done (pcc: provides c-compiler while not providing cc alternative)
Your message dated Sun, 04 Sep 2022 19:07:47 + with message-id and subject line Bug#1014707: fixed in pcc 1.2.0~DEVEL+20220331-1 has caused the Debian Bug report #1014707, regarding pcc: provides c-compiler while not providing cc alternative 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.) -- 1014707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014707 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ikiwiki-hosting-web Version: 0.20180719-2 Severity: important Depends: ..., gcc | c-compiler,... There is no defined semantics what "c-compiler" actually provides, e.g. 'cc' might or might not be provided. There are mysterious ppc64el debci failures that might be related to bcc being installed on ppc64el while tcc gets installed on other architectures. Please change this dependency to either only gcc, or a list of known-working C compiler alternatives. --- End Message --- --- Begin Message --- Source: pcc Source-Version: 1.2.0~DEVEL+20220331-1 Done: Yangfl We believe that the bug you reported is fixed in the latest version of pcc, 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 1014...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yangfl (supplier of updated pcc 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: Sat, 03 Sep 2022 23:52:56 +0800 Source: pcc Architecture: source Version: 1.2.0~DEVEL+20220331-1 Distribution: unstable Urgency: medium Maintainer: Yangfl Changed-By: Yangfl Closes: 1014707 Changes: pcc (1.2.0~DEVEL+20220331-1) unstable; urgency=medium . * New upstream release * Provide cc alternative (Closes: #1014707) * Bump Standards-Version to 4.6.1 Checksums-Sha1: 4f7aaf08266ed71dd71522a79db37745aee175ed 1894 pcc_1.2.0~DEVEL+20220331-1.dsc a10a95056024f0a00a9067b20ab0e94f03eb9242 978027 pcc_1.2.0~DEVEL+20220331.orig.tar.gz dbc35cb6bf937ef76d2d2cfc0eb87990a93ec80b 7436 pcc_1.2.0~DEVEL+20220331-1.debian.tar.xz a329d59e85bac8882fed3ecab794d5e22c3f39fe 6536 pcc_1.2.0~DEVEL+20220331-1_amd64.buildinfo Checksums-Sha256: a7ddf7721bf408ae79012b75bc5b07c53c39b832b16af9db82359b3565c7f4cd 1894 pcc_1.2.0~DEVEL+20220331-1.dsc 60bc1c7ac2e41807ef6f32c2b8237b0a69e2d0924c2be17c376846322755763f 978027 pcc_1.2.0~DEVEL+20220331.orig.tar.gz 3b80d7ffb43f4a193292d03298045da87a8e5353821570c3c13cf80c13b91a7b 7436 pcc_1.2.0~DEVEL+20220331-1.debian.tar.xz e3b3d0dd1a74f57695f40a84046848d8403bda58ffde65d03871edc0267749a1 6536 pcc_1.2.0~DEVEL+20220331-1_amd64.buildinfo Files: 64c79af578f1c4aefd0268bb0d0eb0f8 1894 devel optional pcc_1.2.0~DEVEL+20220331-1.dsc 8c31c9a49a7434265ea5efa52e07002a 978027 devel optional pcc_1.2.0~DEVEL+20220331.orig.tar.gz 3ff8cce892cfb95d9b391448b4bba56f 7436 devel optional pcc_1.2.0~DEVEL+20220331-1.debian.tar.xz 02573d0d14341a9cae8b1589feaede6b 6536 devel optional pcc_1.2.0~DEVEL+20220331-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmMU8foACgkQwpPntGGC Ws6nSBAAg8af80EIQv2nREsUV+/MAzUSp1wME0jkCivpYQZCI0SGsyXFy75DcAjX ZRW+uXqX4YqoT/rh60xD+tncYNMy01oJWD//WEIGJgZLJvZX8RwrJtoiAbHEM8nu snu2YVRr5mNCV0RaaiV0D6giEjkNq8XS9GcjLdVZDjf+ap3QljU9NbFMQlkyDNAI 5YdqM4yedcl8udW0WU3cUSqXMq/+KPIYwzl3nK8j/l76qKr2XUc+TPLdisL4q7/O JRHKZDOTilvg/F3YdnZHDfQt8QOOyTFu/d8Vu2QEpveJVMetkA1HW/ART47iUsPU 9p6gVVZ0to9tPkC+1955qmX2dnWl7lG1YDcCa5Qmbz7stmlEzn04wrwro9LyUGqZ ahchglrdlpl+xps3DP9Vy9HKRUFqPhJJlk4kizBI2Ke2BRpEu0rOAGZ0qu0dTJT3 2T3BmDTqVw29f/K6wfp394AqsJa9BeaAS2xQ98ZtZbqZuLYM5P8KHAby6BdEyDXe wcnJadlte4Rh8JYqIagZj2fpZYsTysxs4O28Y9AZExXC4N2H3xHKw1WDJpyksGp5 HMDWjSloMOCs87AX44TLffvlu+mQm+f8avEeEPGWXgcv20u6gPbXrGw/V/HlRUQp BdUwLMhwrD744r03nyafc8X1liujRLitPSI1qfpfZY4qVOe9ILU= =8bAG -END PGP SIGNATURE End Message ---
Processed: let's mark this bug as affecting a version in the changelog
Processing commands for cont...@bugs.debian.org: > # the bts doesn't recognize that the current version in this bug affects > # the package in unstable because it doesn't decent from it > found 938645 0.8.1-7 Bug #938645 [src:telepathy-salut] telepathy-salut: Python2 removal in sid/bullseye Marked as found in versions telepathy-salut/0.8.1-7. > thanks Stopping processing here. Please contact me if you need assistance. -- 938645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938645 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960679: fontconfig: strict dependency of arch:any libfontconfig1 on arch:all fontconfig-config going wrong
Hi,
On Fri, 15 May 2020 12:48:14 +0200 Julien Cristau wrote:
> libfontconfig1 Depends on fontconfig-config (>= ${source:Version})
>
> If the arch:amd64 buildd is faster than the arch:all one, as happened
> with 2.13.1-4.1, the new libfontconfig1 becomes uninstallable, and,
> because fontconfig indirectly build-depends on libfontconfig1, that
> situation can't fix itself.
>
> One way around that is to make fontconfig-config arch:any; there may be other
> solutions.
I uploaded an NMU with attached debdiff to DELAYED/10 to fix this bug.
Thanks!
cheers, joschdiff -Nru fontconfig-2.13.1/debian/changelog fontconfig-2.13.1/debian/changelog
--- fontconfig-2.13.1/debian/changelog 2022-01-29 17:05:46.0 +0100
+++ fontconfig-2.13.1/debian/changelog 2022-09-04 18:37:48.0 +0200
@@ -1,3 +1,14 @@
+fontconfig (2.13.1-4.5) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Make fontconfig-config arch:any. If one of the arch:any buildds is faster
+than the arch:all one, the new libfontconfig1 becomes uninstallable, and,
+because fontconfig indirectly build-depends on libfontconfig1, that
+situation can't fix itself. Turning fontconfig-config from arch:all to
+arch:any prevents this from happening. (closes: #960679)
+
+ -- Johannes Schauer Marin Rodrigues Sun, 04 Sep 2022 18:37:48 +0200
+
fontconfig (2.13.1-4.4) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru fontconfig-2.13.1/debian/control fontconfig-2.13.1/debian/control
--- fontconfig-2.13.1/debian/control 2020-05-15 12:55:02.0 +0200
+++ fontconfig-2.13.1/debian/control 2022-09-04 17:16:52.0 +0200
@@ -42,7 +42,7 @@
available to fontconfig applications.
Package: fontconfig-config
-Architecture: all
+Architecture: any
Depends: ${misc:Depends},
ucf (>= 0.29),
# Bitstream Vera and derivatives
diff -Nru fontconfig-2.13.1/debian/rules fontconfig-2.13.1/debian/rules
--- fontconfig-2.13.1/debian/rules 2022-01-12 07:49:42.0 +0100
+++ fontconfig-2.13.1/debian/rules 2022-09-04 17:17:10.0 +0200
@@ -23,8 +23,7 @@
chmod +w debian/po/*.po
debconf-updatepo
-override_dh_install-indep:
- dh_install -i
+execute_after_dh_install-arch:
cd debian/fontconfig-config/usr/share/fontconfig/conf.avail && \
mv 70-yes-bitmaps.conf 70-force-bitmaps.conf
cp debian/70-yes-bitmaps.conf debian/fontconfig-config/usr/share/fontconfig/conf.avail/
signature.asc
Description: signature
Bug#1018930: marked as done (pcs: CVE-2022-2735: Obtaining an authentication token for hacluster user leads to privilege escalation)
Your message dated Sun, 4 Sep 2022 20:57:14 +0200 with message-id and subject line Accepted pcs 0.11.3-2 (source) into unstable has caused the Debian Bug report #1018930, regarding pcs: CVE-2022-2735: Obtaining an authentication token for hacluster user leads to privilege escalation 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.) -- 1018930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pcs Version: 0.11.3-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 0.10.8-1 Hi, The following vulnerability was published for pcs. CVE-2022-2735[0]: | Obtaining an authentication token for hacluster user leads to | privilege escalation If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-2735 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2735 [1] https://www.openwall.com/lists/oss-security/2022/09/01/4 Regards, Salvatore --- End Message --- --- Begin Message --- Source: pcs Source-Version: 0.11.3-2 This issue was fixed with the update below, but did not contain the bug closer. Closing manually. - Forwarded message from Debian FTP Masters - -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 04 Sep 2022 19:08:15 +0200 Source: pcs Architecture: source Version: 0.11.3-2 Distribution: unstable Urgency: high Maintainer: Debian HA Maintainers Changed-By: Valentin Vidic Changes: pcs (0.11.3-2) unstable; urgency=high . * d/patches: add fix for CVE-2022-2735 Checksums-Sha1: 01f44f8743e86deb7a97f6473aa3f2dd9d79490d 2540 pcs_0.11.3-2.dsc 05204a6fafdedd3ee23f80a1139b5d1184b62af0 10048 pcs_0.11.3-2.debian.tar.xz c2060c7ff2c3778513f986e02180c834e39ac054 8671 pcs_0.11.3-2_source.buildinfo Checksums-Sha256: 6a5cf61328e07459c2e7d8647fca4dc5e820973971f631031418fd82195967f7 2540 pcs_0.11.3-2.dsc db3d0afaec3d272c0f7f7bbd019818a2a7b1eb32ee21eef47ce91571fe26e01b 10048 pcs_0.11.3-2.debian.tar.xz 602438d8e136221b100df9e94bf9851e766824a6b8f29143675ff2b87148 8671 pcs_0.11.3-2_source.buildinfo Files: e997638b7e5e3dff9bdb9e87e9c9a1ae 2540 admin optional pcs_0.11.3-2.dsc 253ae1337868c304df92305808c836b8 10048 admin optional pcs_0.11.3-2.debian.tar.xz ed5a82896e36c2ba069563475b8b45d0 8671 admin optional pcs_0.11.3-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEExaW53cM9k/u2PWfIMofYmpfNqHsFAmMU3+QSHHZ2aWRpY0Bk ZWJpYW4ub3JnAAoJEDKH2JqXzah7LUQP/jUBrwxZg1/bOZegWiPgj2ny2rylMTc8 qgnhcXJutD7KRAd+od+xI7ZZoHmTyrZMlGn2iUbTmSi1+rDq4cSU6o3KHYDU95bj PUn8mbL6FeSf1A1pypUG0p3V1S8p37/pN/t6Jluvk9As1cWs1AUuP1056hozwgmD tlQTTKC8gfwLP+l2vY70K0he23pxn9lbQcPfxghJtLvUJCdHdVb+6Y98pAnP724P jWUfQ3VArUJo2yJ/vqKkz5HX3j/A01lMkHlSnfJai37dYuXg7Q6a7tr73ChdRH6s XyLwH2EwH9TC/F0prd6kMu++QEYiROBmuqvXG03NPk0zfomLYTZYtjq/j7Yzx4YR 939IJxyWicBtnO+NMaS4DGNzj5A9L6JHt22+C2aw4ZFwOZVn649GJ+lNB30kr+Ay kbIS4pHQTpyroLn6lXWv4ArfaDZgSQ7MOffG5pIoTeWTI7h7PxqHXsZB137gnawy zoJ1Ad/tOB+Ro1p8GZQwzuCoT3A1i2gPsfSRpbZTSyEJUMLKAo4KfKDaJ00I6g5P qnq17ottzzSO302OCKUFe7EpbvdLuBq2qCQWDS/2kz0mdQe47P+J5cGrsYEMcWMU 2mJQlyoIRL9uS4htOwdl/sJ85D7nLhWw+ZP761g+eozOjAopOpu2V4Z0kZpR+/R8 cNAF1IaDHscb =D7dF -END PGP SIGNATURE- - End forwarded message End Message ---
Bug#1019128: marked as done (gnome-builder: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported.)
Your message dated Sun, 04 Sep 2022 16:48:59 + with message-id and subject line Bug#1019128: fixed in devhelp 43~rc-1 has caused the Debian Bug report #1019128, regarding gnome-builder: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported. 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.) -- 1019128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-builder Version: 42.1-1+b2 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: tylermageeshie...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? GNOME Builder no longer works so I can no longer create GNOME apps * What exactly did you do (or not do) that was effective (or ineffective)? Enable backports * What was the outcome of this action? GNOME Builder crashes instantly a split second after launch * What outcome did you expect instead? GNOME Builder displays UI Log: (process:46288): libsoup-ERROR **: 09:19:28.122: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported. Trace/breakpoint trap In the terminal I cannot use command line flags at all, it throws the same error. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-builder depends on: ii clang1:14.0-55.1 ii dconf-gsettings-backend [gsettings-backend] 0.40.0-3 ii exuberant-ctags 1:5.9~svn20110310-16 ii gir1.2-dazzle-1.03.44.0-1 ii gir1.2-ggit-1.0 1.1.0-1 ii gir1.2-glib-2.0 1.72.0-1+b1 ii gir1.2-gtk-3.0 3.24.34-3 ii gir1.2-gtksource-4 4.8.3-1 ii gir1.2-jsonrpc-1.0 3.42.0-1 ii gir1.2-peas-1.0 1.32.0-1+b1 ii gir1.2-template-1.0 3.35.0-1 ii gir1.2-vte-2.91 0.69.92-1 ii gir1.2-webkit2-4.0 2.36.7-1 ii libatk1.0-0 2.38.0-1 ii libc62.34-7 ii libcairo-gobject21.16.0-6 ii libcairo21.16.0-6 ii libclang1-14 1:14.0.6-2 ii libcmark0.30.2 0.30.2-5 ii libdazzle-1.0-0 3.44.0-1 ii libdevhelp-3-6 43~beta-2 ii libenchant-2-2 2.3.3-1 ii libflatpak0 1.14.0-1 ii libfontconfig1 2.13.1-4.4 ii libgirepository-1.0-11.72.0-1+b1 ii libgit2-1.3 1.3.0+dfsg.1-3 ii libgit2-glib-1.0-0 1.1.0-1 ii libgladeui-2-13 3.40.0-1 ii libglib2.0-0 2.72.3-1+b1 ii libgspell-1-21.11.1-1 ii libgtk-3-0 3.24.34-3 ii libgtksourceview-4-0 4.8.3-1 ii libhandy-1-0 1.7.90-1 ii libjson-glib-1.0-0 1.6.6-1 ii libjsonrpc-glib-1.0-13.42.0-1 ii libpango-1.0-0 1.50.9+ds-1 ii libpangocairo-1.0-0 1.50.9+ds-1 ii libpangoft2-1.0-01.50.9+ds-1 ii libpcre3 2:8.39-14 ii libpeas-1.0-01.32.0-1+b1 ii libportal-gtk3-1 0.6-2 ii libportal1 0.6-2 ii libsoup2.4-1 2.74.2-3 ii libsysprof-4 3.44.0-1 ii libsysprof-ui-4 3.44.0-1 ii libtemplate-glib-1.0-0 3.35.0-1 ii libvala-0.56-dev [libvala-dev] 0.56.2-1 ii libvte-2.91-0
Bug#1018797: marked as done (glib-d FTBFS: conflicting constructors)
Your message dated Sun, 04 Sep 2022 16:49:15 + with message-id and subject line Bug#1018797: fixed in glib-d 2.3.0-3 has caused the Debian Bug report #1018797, regarding glib-d FTBFS: conflicting constructors 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.) -- 1018797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018797 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glib-d Version: 2.3.0-2 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic Hi Matthias, After patching dh-dlang as in bug #1018795, and rebuilding gir-to-d against current ldc, I find that glib-d FTBFS because of invalid generated code: [...] FAILED: libglibd-2.0.so.2.2.0.p/obj-x86_64-linux-gnu_generated_gio_DtlsConnectionIF.d.o ldc2 -I=libglibd-2.0.so.2.2.0.p -I=. -I=.. -I=generated -I=../generated -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -enable-color -wi -O -g -release -wi -relocation-model=pic -makedeps=libglibd-2.0.so.2.2.0.p/obj-x86_64-linux-gnu_generated_gio_DtlsConnectionIF.d.o.deps -of=libglibd-2.0.so.2.2.0.p/obj-x86_64-linux-gnu_generated_gio_DtlsConnectionIF.d.o -c ../obj-x86_64-linux-gnu/generated/gio/DtlsConnectionIF.d generated/gio/TlsCertificate.d(194): Error: constructor `gio.TlsCertificate.TlsCertificate.this(string certFile, string keyFile)` conflicts with previous declaration at generated/gio/TlsCertificate.d(146) [...] Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: glib-d Source-Version: 2.3.0-3 Done: Matthias Klumpp We believe that the bug you reported is fixed in the latest version of glib-d, 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 1018...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klumpp (supplier of updated glib-d 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: Sun, 04 Sep 2022 18:16:46 +0200 Source: glib-d Architecture: source Version: 2.3.0-3 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Matthias Klumpp Closes: 1018797 Changes: glib-d (2.3.0-3) unstable; urgency=medium . * Add glib-2.72-support.patch: - Fixes build with GLib 2.72 (Closes: #1018797) * Mark d/rules as not requiring root Checksums-Sha1: 553617307486cd17f0cc8baa8216e7f1f0aa2a04 2136 glib-d_2.3.0-3.dsc 18a79505e36c667bb45b9de16daab4c6460bfdd2 35915 glib-d_2.3.0.orig.tar.gz e4dc83331161fac42dfe6b772115fbf8d46fc607 5348 glib-d_2.3.0-3.debian.tar.xz 3e52805912e51c7d3ac3500ebbc0a869a529e71e 9174 glib-d_2.3.0-3_source.buildinfo Checksums-Sha256: 75db94cab782807ec48b1bb2e33d0b8e552cd9a8e58c5bf25ee8b5fa7c615588 2136 glib-d_2.3.0-3.dsc 5f84268026e134b2bb7998b05a82869ecebbe303182c66983cd62c32dae8460d 35915 glib-d_2.3.0.orig.tar.gz 1114ffb0bd306c8dbfbd5d7c115fd7aec524ebbe1a50e14f06e48d32c5366965 5348 glib-d_2.3.0-3.debian.tar.xz 9fb15d98ed936c2f3c51a83cf7efc1ec836521d773d0476bbb26dddb5d8f1d08 9174 glib-d_2.3.0-3_source.buildinfo Files: 79acf05423b69447a277c359e793fb89 2136 libs optional glib-d_2.3.0-3.dsc 0ea6fa559a08778ae2f81248e6a2109d 35915 libs optional glib-d_2.3.0.orig.tar.gz 365efc669047a8ddb0cfb1b643f6c3b7 5348 libs optional glib-d_2.3.0-3.debian.tar.xz 9159eb4fb6b53d9923b901d0654fd158 9174 libs optional glib-d_2.3.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEE0zo/DKFrCsxRpgc4SUyKX79N7OsFAmMU0C4PHG1ha0BkZWJp YW4ub3JnAAoJEElMil+/TezrZxUP/1hzlQFoMNSupvpNfaqmeLU3Rz8GH76iTcPu 3tTl/OZnX8rZ2NVBhMCs5xLJxC8guJLMtRMNT4ITqkZP/TS2h/zWCKKVsmADsbJw +ilYNvD6rZMR/RI86SfviZylJUE5BiamjZtN0f4qyOqaRQpSaF1Y2TcaSC217+0+ BbWdk7qdYGoJAMyS2ymPFdstBAtVUGfcyPn77jrN2PGY3+SiFddeY0tZGsqAAUqY k1O0VAQWCq7L9xkgWCIfcm24JGhUnCnrTqDzCY2Z5qLA/gnfsWdl+GIbGF/rIctt VNsGH2PE
Processed: Bug#1019128 marked as pending in devhelp
Processing control commands: > tag -1 pending Bug #1019128 [src:devhelp] gnome-builder: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported. Added tag(s) pending. -- 1019128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019128: marked as pending in devhelp
Control: tag -1 pending Hello, Bug #1019128 in devhelp 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/gnome-team/devhelp/-/commit/c42d581e6802e6e1e84fe2bb3cb4276b61e5a711 releasing package devhelp version 43~beta-3 Closes: #1019128 (this message was generated automatically) -- Greetings https://bugs.debian.org/1019128
Processed: Re: Bug#1019128: gnome-builder: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported.
Processing control commands: > reassign -1 src:devhelp 43~beta-2 Bug #1019128 [gnome-builder] gnome-builder: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported. Bug reassigned from package 'gnome-builder' to 'src:devhelp'. No longer marked as found in versions gnome-builder/42.1-1. Ignoring request to alter fixed versions of bug #1019128 to the same values previously set Bug #1019128 [src:devhelp] gnome-builder: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported. Marked as found in versions devhelp/43~beta-2. > affects -1 src:gnome-builder Bug #1019128 [src:devhelp] gnome-builder: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported. Added indication that 1019128 affects src:gnome-builder -- 1019128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019128: gnome-builder: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported.
Control: reassign -1 src:devhelp 43~beta-2 Control: affects -1 src:gnome-builder On Sun, Sep 4, 2022 at 11:43 AM Tyler Magee Shields wrote: > (process:46288): libsoup-ERROR **: 09:19:28.122: libsoup2 symbols detected. > Using libsoup2 and libsoup3 in the same process is not supported. Thank you for reporting this bug. There are 2 ways forward: either pushing GNOME Builder 43 to Unstable or revert the devhelp change. GNOME Builder 43 requires glib 2.73 which is unable to migrate to Testing yet. So the only fix is to revert devhelp for now. Jeremy Bicha
Bug#1018796: marked as done (mir-core: FTBFS with gdc: unrecognized commandline option -preview=dip1008)
Your message dated Sun, 04 Sep 2022 15:49:29 + with message-id and subject line Bug#1018796: fixed in mir-core 1.1.111-2 has caused the Debian Bug report #1018796, regarding mir-core: FTBFS with gdc: unrecognized commandline option -preview=dip1008 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.) -- 1018796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mir-core Version: 1.1.111-1 Severity: serious Tags: patch Justification: ftbfs User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic ubuntu-patch Hi Matthias, The mir-core package is failing to build on all gdc archs in unstable because meson.build includes a compiler option, '-preview=dip1008', which is ldc-specific and not understood by gdc. Patching this option out lets the package build on all archs, including those using ldc, so it doesn't appear to be needed. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru mir-core-1.1.111/debian/patches/drop-non-portable-option.patch mir-core-1.1.111/debian/patches/drop-non-portable-option.patch --- mir-core-1.1.111/debian/patches/drop-non-portable-option.patch 1969-12-31 16:00:00.0 -0800 +++ mir-core-1.1.111/debian/patches/drop-non-portable-option.patch 2022-08-30 15:48:27.0 -0700 @@ -0,0 +1,17 @@ +Description: Don't pass -preview= to the compiler + This option is understood by ldc and not by gdc, and is not required in order + for the package to build. +Author: Steve Langasek +Last-Update: 2022-08-30 +Forwarded: no + +--- mir-core-1.1.111.orig/meson.build mir-core-1.1.111/meson.build +@@ -37,7 +37,6 @@ foreach s : sources_list + endforeach + + add_project_arguments([ +-'-preview=dip1008', + '-lowmem', + ], language: 'd') + diff -Nru mir-core-1.1.111/debian/patches/series mir-core-1.1.111/debian/patches/series --- mir-core-1.1.111/debian/patches/series 1969-12-31 16:00:00.0 -0800 +++ mir-core-1.1.111/debian/patches/series 2022-08-30 15:47:47.0 -0700 @@ -0,0 +1 @@ +drop-non-portable-option.patch --- End Message --- --- Begin Message --- Source: mir-core Source-Version: 1.1.111-2 Done: Matthias Klumpp We believe that the bug you reported is fixed in the latest version of mir-core, 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 1018...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klumpp (supplier of updated mir-core 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: Sun, 04 Sep 2022 17:25:46 +0200 Source: mir-core Architecture: source Version: 1.1.111-2 Distribution: unstable Urgency: medium Maintainer: Debian D Language Group Changed-By: Matthias Klumpp Closes: 1018796 Changes: mir-core (1.1.111-2) unstable; urgency=medium . * Add fix-gdc-build.patch: Fix build with GDC (Closes: #1018796) Checksums-Sha1: 1321a7bfe1dc9639e1af19ddcabbda4218d1148c 2043 mir-core_1.1.111-2.dsc f5394425f42881d0e0097e2881152abe3a5ff404 83463 mir-core_1.1.111.orig.tar.gz 63b0790209cc77437592c3d274c090970c59eeaf 3196 mir-core_1.1.111-2.debian.tar.xz 1e3ad151bf2e2b8a3cdc8411df16378a33de9f6d 8117 mir-core_1.1.111-2_source.buildinfo Checksums-Sha256: 4a047ddcaa7039b67bd7c0246970f1cfb91f116f06ec4aa1a24ee011a5ff2c19 2043 mir-core_1.1.111-2.dsc 11863a987872b1b1651ae09178d90cb91b1d705ebf06cf6b4eb340b9058148fd 83463 mir-core_1.1.111.orig.tar.gz 23bf57f9becf84cae8e7ac8f5515c21481bab288da338b89c231012400e1692e 3196 mir-core_1.1.111-2.debian.tar.xz cb25b3eb14c22bbcfef25819bdaadad3f6312248a82b7f4570997da4bf8926de 8117 mir-core_1.1.111-2_source.buildinfo Files: 6babb0a63c3565b869af43f7f5a1d72c 2043 libs optional mir-core_1.1.111-2.dsc 56daebb2b9b9715fa9b23f29909e56e1 83463 libs optional mir-core_1.1.111.orig.tar.gz 2df9b2827eb2ef85ab1b992fc4152102 3196 libs optional mir-core_1
Processed: block 996464 with 1019044 1019090 1019144
Processing commands for cont...@bugs.debian.org: > block 996464 with 1019044 1019090 1019144 Bug #996464 [wnpp] ITP: atomic-data-rust -- graph database server to share Atomic Data on the web 996464 was blocked by: 984622 1010256 1013099 1013109 1013104 1013098 1013108 1013100 1013107 1013106 969609 1013103 1010212 996464 was not blocking any bugs. Added blocking bug(s) of 996464: 1019044, 1019144, and 1019090 > thanks Stopping processing here. Please contact me if you need assistance. -- 996464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016936: dwz: fails while building assaultcube
Package: dwz Version: 0.14-1 Followup-For: Bug #1016936 It also fails for nodejs (gcc 11 on mips64el): https://buildd.debian.org/status/fetch.php?pkg=nodejs&arch=mips64el&ver=18.8.0%2Bdfsg-1&stamp=1662286086&raw=0 -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dwz depends on: ii libc62.34-7 ii libelf1 0.187-2 dwz recommends no packages. dwz suggests no packages. -- no debconf information
Bug#1019144: librust-dialoguer-dev: impossible to install
Package: librust-dialoguer-dev Version: 0.10.1-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Binary package librust-dialoguer-dev is impossible to install, as it depends on unavailable package librust-fuzzy-matcher-0.3+default-dev - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmMUwWQACgkQLHwxRsGg ASFFig/+NpM/heUD2TaGbHpZhmAdIvpWf6iXZ4Q+g/YTUnVXc1YUy9GsG8RrqYn+ YIu3phL//Tj7FCveoxSfWqbk4gXU4oTP12KcIKNkGJFHijqRWn8R1/q16GmfvIxQ A1xIBpwFx8mGWjbpysLGR5lz50mf4A2RmefXy04tkt5+t3ghEXUssPEUWwmYMRKD XSAOhkC9h7U3kNWiJSi7lq9lsV/45gMtaYLSGFU/LEfNpUpMh53OIxb2fYCs4xw0 IsfqkEd+J78IuQ8rqOG3CipVvZfsQqn+MEUtDrPEBdwuSD9bOjUSUQqIvklLQECu 8fYgpTWRM/ICWFQqkr5YIwh9iHk/+Ppk0ssa4UF1pm2XLUXLZZCHvNkjukboQIhu 1DYz1jLgNhrKjpaIWqh+XBb0AvzWfjTWa2f8bbTATI4W1cREiGgA1CpoD7NPZblj FdBQn8p4i33Ls0d88BCXOjaHXe1rE79HAH4ByksXdzQ+J2NocWeYKqBR0xbq0fkE EeVCeMdUM82qBBfH+cR6IfBYQnp909dBQrSWezIq3sDBJHbdd6biJG0zsbOzYU4z A/z/bpz/9nKHHSTZi/v/dBvg8EcF+d1w8EOF1FOAfDpOj+qwZPMlJ2ntHzXIvssZ LzwKRZwNnaSTwWqg4pAULfvNbOaDbPBDNBXtJ8qzPPUCrY0XT5w= =9O94 -END PGP SIGNATURE-
Bug#1019099: marked as done (rust-ahash - autopkgtest failure)
Your message dated Sun, 04 Sep 2022 14:36:41 +
with message-id
and subject line Bug#1019099: fixed in rust-ahash 0.7.6-5
has caused the Debian Bug report #1019099,
regarding rust-ahash - autopkgtest 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.)
--
1019099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rust-ahash
Version: 0.7.6-4
Severity: serious
The autopkgtest of rust-ahash is failing
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-ahash/25673987/log.gz
Testing aeshash/u8
thread 'main' panicked at 'aes must be enabled', tests/bench.rs:20:5
stack backtrace:
0: std::panicking::begin_panic
at /usr/src/rustc-1.59.0/library/std/src/panicking.rs:525:12
1: ahash::aeshash
at ./tests/bench.rs:20:5
2: ahash::bench_ahash::{{closure}}::{{closure}}
at ./tests/bench.rs:92:81
3: criterion::bencher::Bencher::iter
at
/tmp/tmp.wNUW0kfuKe/registry/criterion-0.3.5/src/bencher.rs:88:23
4: ahash::bench_ahash::{{closure}}
at ./tests/bench.rs:89:54
5: as
criterion::routine::Routine>::bench::{{closure}}
at
/tmp/tmp.wNUW0kfuKe/registry/criterion-0.3.5/src/routine.rs:209:17
6: core::iter::adapters::map::map_fold::{{closure}}
at
/usr/src/rustc-1.59.0/library/core/src/iter/adapters/map.rs:84:28
7: core::iter::traits::iterator::Iterator::fold
at
/usr/src/rustc-1.59.0/library/core/src/iter/traits/iterator.rs:2171:21
8: as
core::iter::traits::iterator::Iterator>::fold
at
/usr/src/rustc-1.59.0/library/core/src/iter/adapters/map.rs:124:9
9: core::iter::traits::iterator::Iterator::for_each
at
/usr/src/rustc-1.59.0/library/core/src/iter/traits/iterator.rs:736:9
10: as
alloc::vec::spec_extend::SpecExtend>::spec_extend
at
/usr/src/rustc-1.59.0/library/alloc/src/vec/spec_extend.rs:40:17
11: as
alloc::vec::spec_from_iter_nested::SpecFromIterNested>::from_iter
at
/usr/src/rustc-1.59.0/library/alloc/src/vec/spec_from_iter_nested.rs:56:9
12: as
alloc::vec::spec_from_iter::SpecFromIter>::from_iter
at
/usr/src/rustc-1.59.0/library/alloc/src/vec/spec_from_iter.rs:33:9
13: as
core::iter::traits::collect::FromIterator>::from_iter
at /usr/src/rustc-1.59.0/library/alloc/src/vec/mod.rs:2541:9
14: core::iter::traits::iterator::Iterator::collect
at
/usr/src/rustc-1.59.0/library/core/src/iter/traits/iterator.rs:1745:9
15: as
criterion::routine::Routine>::bench
at
/tmp/tmp.wNUW0kfuKe/registry/criterion-0.3.5/src/routine.rs:205:9
16: criterion::routine::Routine::test
at
/tmp/tmp.wNUW0kfuKe/registry/criterion-0.3.5/src/routine.rs:18:9
17: criterion::benchmark_group::BenchmarkGroup::run_bench
at
/tmp/tmp.wNUW0kfuKe/registry/criterion-0.3.5/src/benchmark_group.rs:339:21
18: criterion::benchmark_group::BenchmarkGroup::bench_with_input
at
/tmp/tmp.wNUW0kfuKe/registry/criterion-0.3.5/src/benchmark_group.rs:269:9
19: ahash::bench_ahash
at ./tests/bench.rs:87:5
20: ahash::benches
at
/tmp/tmp.wNUW0kfuKe/registry/criterion-0.3.5/src/macros.rs:71:17
21: ahash::main
at
/tmp/tmp.wNUW0kfuKe/registry/criterion-0.3.5/src/macros.rs:127:17
22: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.59.0/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose
backtrace.
error: test failed, to rerun pass '--bench ahash'
autopkgtest [16:38:41]: test
librust-ahash+compile-time-rng-dev:compile-time-rng: ---]
autopkgtest [16:38:41]: test
librust-ahash+compile-time-rng-dev:compile-time-rng: - - - - - - - - - -
results - - - - - - - - - -
librust-ahash+compile-time-rng-dev:compile-time-rng FAIL non-zero exit status
101
autopkgtest [16:38:41]: summary
rust-ahash:@ FAIL non-zero exit status 101
librust-ahash-dev:default FAIL non-zero exit status 101
librust-ahash-dev:std FAIL non-zero exit status 101
librust-ahash-dev: FAIL non-zero exit status 101
librust-ahash+compile-time-rng-dev:compile-time-rng FAIL non-zero exit status
101
Thanks to an annoyance with the way testing migration autopkgtests
interact with skip-not-installable this is blocking the migration of the
new version of rust-once-cell to testing. So we would appr
Bug#989409: marked as done (nss-pam-ldapd's autopkgtest fails with OpenLDAP 2.5)
Your message dated Sun, 04 Sep 2022 12:34:18 +
with message-id
and subject line Bug#989409: fixed in nss-pam-ldapd 0.9.12-3
has caused the Debian Bug report #989409,
regarding nss-pam-ldapd's autopkgtest fails with OpenLDAP 2.5
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.)
--
989409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nss-pam-ldapd
Version: 0.9.11-1
Severity: medium
Hi there!
We're currently working on getting OpenLDAP 2.5 into experimental, so
that we can start slowly working on its migration. As a side note,
Ubuntu is already planning to ship OpenLDAP 2.5 in the next release
(Impish, 21.10).
While running autopkgtests against openldap's rdeps, I noticed that
nss-pam-ldapd is failing with the following error:
Creating blank /tmp/slapd.g4Wq6n slapd environment... done.
Loading cn=config...
added: "cn=config" (0001)
lt_dlopenext failed: (back_bdb) file not found
slapadd: could not add entry dn="cn=module{0},cn=config" (line=10):
handler exited with 1
FAILED
testsuite: cleaning up...
Failed to stop pynslcd.service: Unit pynslcd.service not loaded.
Cleaning /tmp/slapd.g4Wq6n... done.
testsuite: restoring configuration...
autopkgtest [23:55:51]: test testsuite: ---]
autopkgtest [23:55:51]: test testsuite: - - - - - - - - - - results - - - -
- - - - - -
testsuiteFAIL non-zero exit status 1
You can find the full log here if you're interested:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4572/impish/amd64/n/nss-pam-ldapd/20210602_235938_b5f64@/log.gz
The reason this fails is because OpenLDAP 2.5 has dropped the BDB
backend. I believe that the test will need to be ported to LMDB.
Thank you,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: nss-pam-ldapd
Source-Version: 0.9.12-3
Done: Arthur de Jong
We believe that the bug you reported is fixed in the latest version of
nss-pam-ldapd, 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 989...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Arthur de Jong (supplier of updated nss-pam-ldapd 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: Sun, 04 Sep 2022 14:05:24 +0200
Source: nss-pam-ldapd
Architecture: source
Version: 0.9.12-3
Distribution: unstable
Urgency: medium
Maintainer: Arthur de Jong
Changed-By: Arthur de Jong
Closes: 989409
Changes:
nss-pam-ldapd (0.9.12-3) unstable; urgency=medium
.
* Don't force password change during tests (closes: #989409)
* Update lintian overrides
* Upgrade to standards-version 4.6.1 (no changes needed)
Checksums-Sha1:
77925cca868f30d2718c0828fad49ed95e09a0ed 2632 nss-pam-ldapd_0.9.12-3.dsc
dd62b3d226fc6685f82cfa0ec9e92aac0f7734d4 112784
nss-pam-ldapd_0.9.12-3.debian.tar.xz
21448be539d6402e422ed511dc700bf075dc732b 11154
nss-pam-ldapd_0.9.12-3_amd64.buildinfo
Checksums-Sha256:
45ebef31fa840f6282b6f719308eaa5f2a56c17f68219d02e725e429d318d845 2632
nss-pam-ldapd_0.9.12-3.dsc
d9b5252fc923b935b9d200604fd14374f1dd12d7a9b5d30193b10c7af0604d68 112784
nss-pam-ldapd_0.9.12-3.debian.tar.xz
79693de8ff8d4d6ec659ef50fac1332a6f62be5a99c7936195db9403761094c2 11154
nss-pam-ldapd_0.9.12-3_amd64.buildinfo
Files:
575afcd8758bdc8dc8b0f59a8d97ab7f 2632 admin optional nss-pam-ldapd_0.9.12-3.dsc
f4f492e1d678422432b6153514164a0a 112784 admin optional
nss-pam-ldapd_0.9.12-3.debian.tar.xz
573fff995ca0e005310025423b5f1ada 11154 admin optional
nss-pam-ldapd_0.9.12-3_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEERS7Cy2XPaMKhrb9fKot0aBDgr8EFAmMUlSsACgkQKot0aBDg
r8Ffwg/+ObKFwugwEJm9D6ZH6N0Uq7REIABg6sAqFWztaHG30RbPgDKdJfR9XNb3
F94/EaBI9dldBg3Hq+P+SxECl8rHlDxcuacHmkx1C3Nz0HSt5HdGPjuK1Tme9BcC
oodvKAK8PCYtRKbmS/L7dQqPxULsDG4JQNbkCVRha1vhzwkoPVQUpzivEbTnTWJT
IFaYrlrE6MpCIllwarV3aGWsNsVsS+nqS1GCjzQ73y58X7GeoBNTt4Jza2rUoh7l
5KSl4nfo1fW33iqT6rx4wKb0
Bug#1017776: marked as done (elpa-ledger: Breaks upgrade to Emacs 28.1)
Your message dated Sun, 04 Sep 2022 12:33:55 + with message-id and subject line Bug#1017776: fixed in ledger-mode 4.0.0-1 has caused the Debian Bug report #1017776, regarding elpa-ledger: Breaks upgrade to Emacs 28.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.) -- 1017776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: elpa-ledger Version: 3.1.2~pre3+g5067e408-2 Severity: serious Hi, When upgrading my sid system today, which included the upgrade to Emacs 28.1, byte-compilation of the ledger .el files failed, which broke the upgrade. See log below. I understand that's because define-obsolete-function-alias now needs 3 arguments. Indeed, applying this fix from upstream Git fixed the problem for me: https://github.com/ledger/ledger-mode/commit/bcd8cefb720702db88986a52bb66e08e2e451c05 Thanks for maintaining ledger-mode in Debian! :) Failure log: Install elpa-ledger for emacs install/ledger-3.1.2: Handling install of emacsen flavor emacs install/ledger-3.1.2: byte-compiling for emacs Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) Error loading autoloads: (wrong-number-of-arguments (3 . 4) 2) Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) In toplevel form: ledger-check.el:31:1: Error: Wrong number of arguments: (3 . 4), 2 In ledger-string-to-number: ledger-commodities.el:112:8: Warning: docstring wider than 80 characters In ledger-accounts-list-in-buffer: ledger-complete.el:93:8: Warning: docstring wider than 80 characters In ledger-single-line-config: ledger-context.el:55:11: Warning: docstring wider than 80 characters In toplevel form: ledger-exec.el:33:1: Warning: defvar `ledger-works' docstring wider than 80 characters In ledger-exec-success-p: ledger-exec.el:61:8: Warning: docstring wider than 80 characters In ledger-version-greater-p: ledger-exec.el:96:8: Warning: docstring wider than 80 characters ../../elpa-src/ledger-3.1.2/ledger-occur.el: Warning: Use keywords rather than deprecated positional arguments to `define-minor-mode' Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) In toplevel form: ledger-mode.el:48:1: Error: Wrong number of arguments: (3 . 4), 2 In ledger-navigate-skip-lines-backwards: ledger-navigate.el:100:8: Warning: docstring wider than 80 characters In toplevel form: ledger-occur.el:37:1: Warning: custom-declare-variable `ledger-occur-use-face-shown' docstring wider than 80 characters ledger-occur.el:58:39: Warning: Use keywords rather than deprecated positional arguments to `define-minor-mode' In ledger-occur-mode: ledger-occur.el:58:39: Warning: docstring wider than 80 characters In ledger-occur-find-matches: ledger-occur.el:137:8: Warning: docstring wider than 80 characters In ledger-post-align-postings: ledger-post.el:96:8: Warning: docstring wider than 80 characters In toplevel form: ledger-reconcile.el:56:1: Warning: custom-declare-variable `ledger-narrow-on-reconcile' docstring wider than 80 characters ledger-reconcile.el:61:1: Warning: custom-declare-variable `ledger-buffer-tracks-reconcile-buffer' docstring wider than 80 characters ledger-reconcile.el:67:1: Warning: custom-declare-variable `ledger-reconcile-force-window-bottom' docstring wider than 80 characters ledger-reconcile.el:119:1: Warning: custom-declare-variable `ledger-reconcile-sort-key' docstring wider than 80 characters ledger-reconcile.el:126:1: Warning: custom-declare-variable `ledger-reconcile-insert-effective-date' docstring wider than 80 characters In ledger-do-reconcile: ledger-reconcile.el:445:8: Warning: docstring wider than 80 characters In ledger-reconcile-ensure-xacts-visible: ledger-reconcile.el:477:8: Warning: docstring wider than 80 characters In ledger-reconcile-track-xact: ledger-reconcile.el:494:8: Warning: docstring wider than 80 characters In toplevel form: ledger-report.el:88:1: Warning: custom-declare-variable `ledger-report-auto-refresh-sticky-cursor' docstring wider than 80 characters ledger-report.el:592:1: Error: Wrong number of arguments: (3 . 4), 2 In ledger-schedule-constrain-every-count-day: ledger-schedule.el:128:8: Warning: doc
Bug#1016414: abinit: autopkgtest failure
Hi Bas On Sun, 4 Sept 2022 at 14:20, Sebastiaan Couwenberg wrote: > Since no one cares enough about netcdf-fortran, I'll go an have it > removed from the archive as I'm not willing to spend time on issues like > these. I'm sure you are aware, but we have a process [1] for passing packages on to other maintainers. I suggest speaking to Alastair (now added as a recipient). He maintains most of netcdf-fortran's reverse-dependencies. Regards Graham [1] https://wiki.debian.org/Orphaning
Bug#1019137: FTBFS: FAIL: TestNewCmdCompletion/zsh_completion
Source: gh Version: 2.14.4+dfsg1-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: z...@debian.org --- FAIL: TestNewCmdCompletion (0.00s) --- PASS: TestNewCmdCompletion/no_arguments (0.00s) --- FAIL: TestNewCmdCompletion/zsh_completion (0.00s) --- PASS: TestNewCmdCompletion/fish_completion (0.00s) --- PASS: TestNewCmdCompletion/PowerShell_completion (0.00s) --- PASS: TestNewCmdCompletion/unsupported_shell (0.00s) Caused by golang-github-spf13-cobra 1.5.0 https://salsa.debian.org/go-team/packages/golang-github-spf13-cobra/-/commit/37d481d4
Bug#1016414: abinit: autopkgtest failure
Control: tags -1 wontfix On 9/4/22 13:42, Graham Inggs wrote: You wrote: No other netcdf-fortran rdeps have shown issues which leads me to suspect it is an issue in abinit. Only abinit has a comprehensive autopkgtest. The other reverse dependencies, cdftools, etsf-io, ferret-vis, ncl and oasis3 have no autopkgtests, and pyferret only has a superficial 'import pyferret' test. You also wrote: Rebuilding with netcdf-fortan (4.6.0+ds-1) resolves the issue. If no change in abinit was needed, why do you suspect an issue in abinit? Because only that package has an issue. I don't know any fortran, so I cannot troubleshoot this issue. In your request for a binNMU in #1016496, you were asked if libnetcdff shouldn't have bumped its SONAME. Someone needs to talk to upstream to get this unblocked. I'm not going to be that person. I was hoping that the abinit maintainer would chime in, but they haven't responded to this issue for almost two months. Since no one cares enough about netcdf-fortran, I'll go an have it removed from the archive as I'm not willing to spend time on issues like these. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processed: Re: abinit: autopkgtest failure
Processing control commands: > tags -1 wontfix Bug #1016414 [src:netcdf-fortran] abinit: autopkgtest failure Added tag(s) wontfix. -- 1016414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: abinit: autopkgtest failure
Processing control commands: > reassign -1 src:netcdf-fortran 4.6.0+ds-1 Bug #1016414 [src:abinit] abinit: autopkgtest failure Bug reassigned from package 'src:abinit' to 'src:netcdf-fortran'. No longer marked as found in versions abinit/9.6.2-1. Ignoring request to alter fixed versions of bug #1016414 to the same values previously set Bug #1016414 [src:netcdf-fortran] abinit: autopkgtest failure Marked as found in versions netcdf-fortran/4.6.0+ds-1. > affects -1 src:abinit Bug #1016414 [src:netcdf-fortran] abinit: autopkgtest failure Added indication that 1016414 affects src:abinit -- 1016414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016414: abinit: autopkgtest failure
Control: reassign -1 src:netcdf-fortran 4.6.0+ds-1 Control: affects -1 src:abinit Hi Bas You wrote: > No other netcdf-fortran rdeps have shown issues which leads me to > suspect it is an issue in abinit. Only abinit has a comprehensive autopkgtest. The other reverse dependencies, cdftools, etsf-io, ferret-vis, ncl and oasis3 have no autopkgtests, and pyferret only has a superficial 'import pyferret' test. You also wrote: > Rebuilding with netcdf-fortan (4.6.0+ds-1) resolves the issue. If no change in abinit was needed, why do you suspect an issue in abinit? In your request for a binNMU in #1016496, you were asked if libnetcdff shouldn't have bumped its SONAME. Someone needs to talk to upstream to get this unblocked. Regards Graham
Processed (with 2 errors): Re: [gsfonts] Fonts include copyrighted adobe fragment all rights reserved
Processing commands for cont...@bugs.debian.org:
> unblock 694320 by 694308
Bug #694320 {Done: Fabian Greffrath } [gsfonts] [gsfonts]
Fonts include copyrighted adobe fragment all right reserved
Bug #694321 {Done: Fabian Greffrath } [gsfonts] [gsfonts]
Fonts include copyrighted adobe fragment all right reserved
694320 was blocked by: 694308
694320 was not blocking any bugs.
Removed blocking bug(s) of 694320: 694308
694321 was blocked by: 694308
694321 was not blocking any bugs.
Removed blocking bug(s) of 694321: 694308
> The fonts files in fonts-urw-core35 are not built by fontforge anymore.
Unknown command or malformed arguments to command.
> - Fabian
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
694320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694320
694321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#694320: [gsfonts] Fonts include copyrighted adobe fragment all rights reserved
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 unblock 694320 by 694308 The fonts files in fonts-urw-core35 are not built by fontforge anymore. - Fabian -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAmMUfacACgkQy+qOlwzN Wd9hghAA0ZNlg3JqcZYSOI6XRWCSz22Q8hYKpFdqzXNSkY0O/aA9fFIPN2OC/p2b FIBWEgjZZ0o7aa060fu0hfYTajjQly9vRxZdmynYdxcISjmJ85qyVrkmYY0sMrWT yMpakN52mXK/E5lbwFdI0LNk6OZ9VKcPY09lxfXKZMPKZtBDEtVdnCD+hHOJ6MQs iF7wLB+R9Nf/E7sARv97FqprqIIkCU1pCuqmgD5/YxdcNlqYz3lDCv2IKqk53UFk wAQjedXM+OHAvE0zeo7UmAZraufVxyOC++U6yU0zcSiJlbTEkbVZSn/WsyxXjnk1 bSLl8PBuVfpRFY+ZMNhF6M27PEMa94AiVFaT06ZIFJByoP5BHqho1tJAMIlQAkFk ksaW7dPJz2FYDlDsC6HVVkMYg8t+cqii0vuZK9IabdQ49tF2RxYBYVhTybW+GRw8 Wc6/uW80Z+lqnrQ8l8pViMghQg1CGjShCdDL6J2DMJY4BboGM0Qd+hHONRhRStmX SrCKgBWRZLxYds/Iw3T+2TW1pWf8EZ1ElTAXQRiIMgaeOqMvkzGidD8eKYES5/Qz uwPyXyIQnLPrp2gMc05BC7VF47PR7SpE1E6rldqSESNxjY/PcNeVFDq8YC3ZEdPV RYgQPBwWONma16YHy65UXycrCRIWmru3hs3v+OwnbwMHSrqhzmo= =uJpJ -END PGP SIGNATURE-
Bug#1019131: r-bioc-dada2: autopkgtest regression in testing
Source: r-bioc-dada2
Version: 1.24.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime between 2022-06-15 and 2022-06-22, r-bioc-dada2's regressed
in testing [1]. I've copied what I hope is the relevant part of the
log below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-bioc-dada2/testing/amd64/
> library('dada2')
Loading required package: Rcpp
Error: package or namespace load failed for ‘dada2’ in dyn.load(file,
DLLpath = DLLpath, ...):
unable to load shared object '/usr/lib/R/site-library/dada2/libs/dada2.so':
/usr/lib/R/site-library/dada2/libs/dada2.so: undefined symbol: _ZTIN3tbb4taskE
Execution halted
Bug#1012143: marked as done (r-cran-prophet: FTBFS with onetbb/2021.5.0-8 in experimental)
Your message dated Sun, 04 Sep 2022 09:05:48 + with message-id and subject line Bug#1012143: fixed in r-cran-prophet 1.0+dfsg-4 has caused the Debian Bug report #1012143, regarding r-cran-prophet: FTBFS with onetbb/2021.5.0-8 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.) -- 1012143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-prophet Version: 1.0+dfsg-3 Severity: normal Tags: ftbfs Hello, tbb/onetbb transition (#1007222) is currently in the planning. During test rebuild of libtbb-dev reverse dependencies with onetbb/2021.5.0-8 in experimental, current source failed to build with the following: ** using staged installation Error in dyn.load(file, DLLpath = DLLpath, ...) : unable to load shared object '/usr/lib/R/site-library/rstan/libs/rstan.so': /usr/lib/R/site-library/rstan/libs/rstan.so: undefined symbol: _ZN3tbb8internal26task_scheduler_observer_v37observeEb Calls: ... lapply -> FUN -> loadNamespace -> library.dynam -> dyn.load Execution halted Andrius --- End Message --- --- Begin Message --- Source: r-cran-prophet Source-Version: 1.0+dfsg-4 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of r-cran-prophet, 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 1012...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated r-cran-prophet 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: Sun, 04 Sep 2022 13:11:37 +0530 Source: r-cran-prophet Architecture: source Version: 1.0+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Nilesh Patra Closes: 1012143 Changes: r-cran-prophet (1.0+dfsg-4) unstable; urgency=medium . * Team Upload. * Rebuild against new rstan (Closes: #1012143) Checksums-Sha1: e78b87dc242871adc0c8f127c27f8204113cf179 2421 r-cran-prophet_1.0+dfsg-4.dsc 995b3fc5a7a48d41e36f0b6378a9875a0fcc5839 2864 r-cran-prophet_1.0+dfsg-4.debian.tar.xz 3e8ba1f77879674afd5994594eca232f8ed2f7d9 13413 r-cran-prophet_1.0+dfsg-4_amd64.buildinfo Checksums-Sha256: 52d90381fcc1dab5b21faa7d56876c4cbb4048dd9107970116db2e3445ecb383 2421 r-cran-prophet_1.0+dfsg-4.dsc f9d11c34a238fc0da603178f90a6c80e1f54c44fabed1cded70268e21791e4fa 2864 r-cran-prophet_1.0+dfsg-4.debian.tar.xz fd5fc9f713c599ff1f75c17dd340db54b41ec8cfc9599101fb16dc325f735430 13413 r-cran-prophet_1.0+dfsg-4_amd64.buildinfo Files: bea46878f55b61d58f9c2caa3649d318 2421 gnu-r optional r-cran-prophet_1.0+dfsg-4.dsc 170040a12667323cc556a65d54ec6f9a 2864 gnu-r optional r-cran-prophet_1.0+dfsg-4.debian.tar.xz 42b0616773a00951e5acdbd8fee70d3c 13413 gnu-r optional r-cran-prophet_1.0+dfsg-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmMUWZoSHG5pbGVzaEBk ZWJpYW4ub3JnAAoJEAC650s0M2nxN50P/i1MY/7ewXTf+ahc9qS2RoO70ONObrJG 7iFHuh4wSj5Brw3vILJ023iMnEq8Z4pNJnnlxawkjTr2uySkuIxPbpek7L53hLFn debSMhtAYA84tYsVY63sPNmELyoBiTCl4eB8ttIcEEr4HJJM0hoKVdZXI17nZpXC biNIUYQU2q4zaVtcDJ9v0gK8KifPaVNiYRtq/XNs/dbBfCVkF4h9VBkOhaxGIKax irYxQzMVzSUEKxiX5DOFeLOI2+Uxrl9UjJBkMiRV6i988bmHKy4xPWkaHUnDjiVf mcpz2lL6TmB8g+byuBMn55O3qfx64rbHdZrcByr3Js6h2zmDe7sypy6rJktiQo11 wLXNCCkD+luroufyFwJUzAfF2UXm75eeRtZefj6EA8IU5XC0nYYlQamHP1zhaY2+ og6oPDYlAwXWMQwj4bJvlWoMLHe/zBvK1PYVU1fjkoDs7ciQrFWMBzvQTxAW9dMx SWBnWrofh/BElTNu9zKeUuSwMETQ3xC++/cMQzo1TD34zk4EeDwaXxcxuprcyhLU j5PHunZIc2s6Pw0eDcjQCiKv6QKl3ltbYa5lcPUyAU8Ko57+ILfvHdAVSAPNpR6S DAIKyHMYzuoBX89lXr0IE1CkK8bi2EGed2LB5gUCjpijc3lS75DFKpycmPI7/ahG nunNDcNr4cuQ =PM1Q -END PGP SIGNATURE End Message ---
Bug#1011222: marked as done (r-cran-rstanarm: FTBFS with onetbb/2021.5.0-8 in experimental)
Your message dated Sun, 04 Sep 2022 09:05:59 +
with message-id
and subject line Bug#1011222: fixed in r-cran-rstanarm 2.21.3-2
has caused the Debian Bug report #1011222,
regarding r-cran-rstanarm: FTBFS with onetbb/2021.5.0-8 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.)
--
1011222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-rstanarm
Version: 2.21.1-1
Severity: normal
Tags: ftbfs
Hello,
tbb/onetbb transition (#1007222) is currently in the planning. During
test rebuild of libtbb-dev reverse dependencies with onetbb/2021.5.0-8
in experimental, current source failed to build with the following:
dh_auto_install --destdir=debian/r-cran-rstanarm/ -O--buildsystem=R
I: R packages needed for DEP8: testthat, stanheaders (>= 2.18.1-10-2),
bh, hsaur3, codetools, r-base-dev
I: R Package: rstanarm Version: 2.21.1
I: Building using R version 4.2.0-1
I: R API version: r-api-4.0
I: Using built-time from d/changelog: Mon, 08 Feb 2021 19:42:38 +
mkdir -p
/<>/debian/r-cran-rstanarm/usr/lib/R/site-library
R CMD INSTALL -l
/<>/debian/r-cran-rstanarm/usr/lib/R/site-library --clean .
"--built-timestamp='Mon, 08 Feb 2021 19:42:38 +'"
* installing *source* package ‘rstanarm’ ...
files ‘DESCRIPTION’, ‘src/Makevars’,
‘tests/testthat/test_stan_functions.R’ have the wrong MD5 checksums
** using staged installation
** libs
make[1]: Entering directory '/<>/src'
"/usr/lib/R/bin/Rscript" -e "source(file.path('..', 'tools',
'make_cc.R')); make_cc(commandArgs(TRUE))" stan_files/bernoulli.stan
Error in dyn.load(file, DLLpath = DLLpath, ...) :
unable to load shared object
'/usr/lib/R/site-library/rstan/libs/rstan.so':
/usr/lib/R/site-library/rstan/libs/rstan.so: undefined symbol:
_ZN3tbb8internal26task_scheduler_observer_v37observeEb
Calls: make_cc -> loadNamespace -> library.dynam -> dyn.load
Execution halted
Andrius
--- End Message ---
--- Begin Message ---
Source: r-cran-rstanarm
Source-Version: 2.21.3-2
Done: Nilesh Patra
We believe that the bug you reported is fixed in the latest version of
r-cran-rstanarm, 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 1011...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nilesh Patra (supplier of updated r-cran-rstanarm 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: Sun, 04 Sep 2022 13:44:51 +0530
Source: r-cran-rstanarm
Architecture: source
Version: 2.21.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Nilesh Patra
Closes: 1011222
Changes:
r-cran-rstanarm (2.21.3-2) unstable; urgency=medium
.
* Team Uploaded.
* Rebuild with updated rstan (Closes: #1011222)
Checksums-Sha1:
9b2b175c6aee8e4295f7458c25e8af6bba6fa740 2531 r-cran-rstanarm_2.21.3-2.dsc
bf63476d1fb9a83b1f7d089df456d906fa0f5b97 4392
r-cran-rstanarm_2.21.3-2.debian.tar.xz
89c0247654a2ab25ca8d3a2a6ed60741b8b8d7fc 15441
r-cran-rstanarm_2.21.3-2_source.buildinfo
Checksums-Sha256:
805187168bc493f289707748b8917097825e0d7e9fe4cbbdf4f90f52d1061742 2531
r-cran-rstanarm_2.21.3-2.dsc
71b11f5c1f8e90597467cd9e6f3ce89df0cde9c4c2a9a6639676d275d5226748 4392
r-cran-rstanarm_2.21.3-2.debian.tar.xz
7e0a27fe26325ef52184a0ad84c93d3e322d739d640f7dd5883740dde6969207 15441
r-cran-rstanarm_2.21.3-2_source.buildinfo
Files:
a44f881af2d83c1277f484cdd2b20e96 2531 gnu-r optional
r-cran-rstanarm_2.21.3-2.dsc
a37575456c64cc5af7233165acd2d84b 4392 gnu-r optional
r-cran-rstanarm_2.21.3-2.debian.tar.xz
4253f76655d66e8917a857785acee6b7 15441 gnu-r optional
r-cran-rstanarm_2.21.3-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmMUXyQSHG5pbGVzaEBk
ZWJpYW4ub3JnAAoJEAC650s0M2nxWigP/2/D5mBCY1mthPhfRrxbeQQIoSY77BKl
vrpb+jcNT2ZuDnp613fqyp5AgMHANhtxUljOtRvaFiIKXqmQmUpaviwzIztwwZAQ
ZvEoxHZxE/6s2xOaUw0KmkCWK69u2e5O4W/2RxRQ49Lb2cTFzUPy+lJAfrvGLEFt
0mP+ewalkkM29v7J+3nrjQm9E6o5mDEbHnEnzKT3Q7INFWyXDTOmsI8T4H3zoLMV
bay/93iOoXCvCMALbIOo47TRkFssH0AwRb8hLGVUo5HY5Gn1rs+JgQxu1SsShXEU
UZ7ajHYhuN9pftOcq+FAzszqcR+NYBR61iQv7C1u+WsR
Processed: lowering severity
Processing commands for cont...@bugs.debian.org: > severity 1017905 normal Bug #1017905 [src:rust-glib-sys] Ships autogenerated files that can't be renegerated with the code in Debian main Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1017905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017905: lowering severity
severity 1017905 normal thanks Lowering the severity until we hear back from ftpmasters.
Bug#1019128: gnome-builder: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported.
Package: gnome-builder Version: 42.1-1+b2 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: tylermageeshie...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? GNOME Builder no longer works so I can no longer create GNOME apps * What exactly did you do (or not do) that was effective (or ineffective)? Enable backports * What was the outcome of this action? GNOME Builder crashes instantly a split second after launch * What outcome did you expect instead? GNOME Builder displays UI Log: (process:46288): libsoup-ERROR **: 09:19:28.122: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported. Trace/breakpoint trap In the terminal I cannot use command line flags at all, it throws the same error. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-builder depends on: ii clang1:14.0-55.1 ii dconf-gsettings-backend [gsettings-backend] 0.40.0-3 ii exuberant-ctags 1:5.9~svn20110310-16 ii gir1.2-dazzle-1.03.44.0-1 ii gir1.2-ggit-1.0 1.1.0-1 ii gir1.2-glib-2.0 1.72.0-1+b1 ii gir1.2-gtk-3.0 3.24.34-3 ii gir1.2-gtksource-4 4.8.3-1 ii gir1.2-jsonrpc-1.0 3.42.0-1 ii gir1.2-peas-1.0 1.32.0-1+b1 ii gir1.2-template-1.0 3.35.0-1 ii gir1.2-vte-2.91 0.69.92-1 ii gir1.2-webkit2-4.0 2.36.7-1 ii libatk1.0-0 2.38.0-1 ii libc62.34-7 ii libcairo-gobject21.16.0-6 ii libcairo21.16.0-6 ii libclang1-14 1:14.0.6-2 ii libcmark0.30.2 0.30.2-5 ii libdazzle-1.0-0 3.44.0-1 ii libdevhelp-3-6 43~beta-2 ii libenchant-2-2 2.3.3-1 ii libflatpak0 1.14.0-1 ii libfontconfig1 2.13.1-4.4 ii libgirepository-1.0-11.72.0-1+b1 ii libgit2-1.3 1.3.0+dfsg.1-3 ii libgit2-glib-1.0-0 1.1.0-1 ii libgladeui-2-13 3.40.0-1 ii libglib2.0-0 2.72.3-1+b1 ii libgspell-1-21.11.1-1 ii libgtk-3-0 3.24.34-3 ii libgtksourceview-4-0 4.8.3-1 ii libhandy-1-0 1.7.90-1 ii libjson-glib-1.0-0 1.6.6-1 ii libjsonrpc-glib-1.0-13.42.0-1 ii libpango-1.0-0 1.50.9+ds-1 ii libpangocairo-1.0-0 1.50.9+ds-1 ii libpangoft2-1.0-01.50.9+ds-1 ii libpcre3 2:8.39-14 ii libpeas-1.0-01.32.0-1+b1 ii libportal-gtk3-1 0.6-2 ii libportal1 0.6-2 ii libsoup2.4-1 2.74.2-3 ii libsysprof-4 3.44.0-1 ii libsysprof-ui-4 3.44.0-1 ii libtemplate-glib-1.0-0 3.35.0-1 ii libvala-0.56-dev [libvala-dev] 0.56.2-1 ii libvte-2.91-00.69.92-1 ii libwebkit2gtk-4.0-37 2.36.7-1 ii libxml2 2.9.14+dfsg-1+b1 ii python3 3.10.6-1 ii python3-gi 3.42.2-2 Versions of packages gnome-builder recommends: ii build-essential12.9 pn flatpak-builder ii gettext0.21-8 ii meson 0.62.2-1 ii pkg-config 0.29.2-1 ii python3-lxml 4.9.1-1+b1 ii valgrind-if-available 3.18.1-1-1 Versions of packages gnome-builder suggests: pn rubocop Versions of packages flatpak depends on: ii adduser 3.128 ii bubblewrap 0.6.2-1 ii dbus [default-dbus-system-bus] 1.14.0-2 ii libappstream4 0.15.5-1 ii libarchive133.6.0-1 ii
Bug#1019127: recoll: FTBFS if systemd is in build environment
Source: recoll Version: 1.32.5-1 Severity: serious Tags: patch Hi Maintainer As can be seen on reproducible builds [1], if systemd is present in the build environment, the build fails with the following output: dh_missing: warning: lib/systemd/system/recollindex@.service exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/systemd/user/recollindex.service exists in debian/tmp but is not installed to anywhere dh_missing: error: missing files, aborting This can be avoided by configuring recoll with --without-systemd, as per the patch below. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/recoll.html --- a/debian/rules +++ b/debian/rules @@ -21,7 +21,7 @@ dh $@ --with python3 override_dh_auto_configure: - dh_auto_configure -- --enable-recollq --enable-xadump + dh_auto_configure -- --enable-recollq --enable-xadump --without-systemd override_dh_auto_install: dh_auto_install
Bug#1017053: fenics-dolfinx: FTBFS on mips64el
Source: fenics-dolfinx Followup-For: Bug #1017053 I see. I attributed the fault to the pmix problem too quickly. >From the error logs it seems to be coming from xtl. I've just uploaded dolfinx 0.5.0. It might help since it has removed explicit xtl use.
Bug#1017249: rheolef: FTBFS: ../../include/rheolef/communicator.h:112:25: error: expected initializer before ‘size’
Dear Lucas, Many thanks for reporting this bug. I've just tried to reproduce it with sid (g++ 12.2.0-1) and bookwork (g++ 12.1.0-3): the package built successfully in both cases. I used pbuilder together with all the up-to-date package versions. So, please could you try to rebuild the rheolef package in Debian (I am not DM) and let me known: probably this bug in rheolef was due to another package (g++?) and could now be closed ? Many thanks for your help, Pierre -- pierre.saram...@imag.fr Directeur de Recherche CNRS Laboratoire Jean Kuntzmann, Grenoble, France http://ljk.imag.fr/membres/Pierre.Saramito
Bug#1019101: resampy: autopkgtest regression on s390x
Dear Paul, On Sat, 3 Sep 2022 23:08:37 +0200 Paul Gevers wrote: Source: resampy Version: 0.4.0+ds-2 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of resampy the autopkgtest of resampy fails in testing when that autopkgtest is run with the binary packages of resampy from unstable on s390x (our only big endian release archive). It passes when run with only packages from testing. In tabular form: passfail resampyfrom testing0.4.0+ds-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration 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=resampy https://ci.debian.net/data/autopkgtest/testing/s390x/r/resampy/25657002/log.gz [...] I have this issue in my radar already. I'm waiting to get access to a s390x porterbox to be able to investigate. kind regards -- Antonio Valentino
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 1006818 Jan Wielemaker Bug #1006818 [swi-prolog-core] intermediary files embed arch-specific path Set Bug forwarded-to-address to 'Jan Wielemaker '. > thanks Stopping processing here. Please contact me if you need assistance. -- 1006818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
