Bug#1018867: luajit2: stop building on ppc64el
Source: luajit2 Version: 2.1-20220411-5 Severity: serious Justification: broken Hi Mo, all, As a follow-up of our transition bug # 1012362, I just discussed with ftp-master on IRC to finally clean up the luajit* situation and I learned (I should have realized) that the first thing that needs to happen is that luajit2 doesn't build itself on ppc64el. If the binaries are still there, any reverse build dependency will just be rebuild if the those binaries are removed. If you can't (or don't want to) do this soon, I'll upload luajit2 with only ppc64el dropped from the Architectures field (well, convert `any` to the list where it builds). Please let me know if you want me to do that. Paul
Processed: fenics-dolfinx: FTBFS on mips64el
Processing commands for cont...@bugs.debian.org:
> reopen 1017053
Bug #1017053 {Done: Drew Parsons } [src:fenics-dolfinx]
fenics-dolfinx: FTBFS on mips64el
Bug reopened
Ignoring request to alter fixed versions of bug #1017053 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1017053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017053
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1018863: wordpress: 6.0.2 Security and Maintenance Release
On Thu, 1 Sept 2022 at 16:39, Salvatore Bonaccorso wrote: > Do the issues affect as well older series? > I suspect so because 2 days ago there was an update for the 5.7 branch upstream. https://github.com/WordPress/WordPress/commit/8b87e45e69889ec4a6a837c9d6971697da49e2c8 The commit message looks like security-type fixes: - Posts, Post Types: Escape output within `the_meta()`. - General: Ensure bookmark query limits are numeric. - Plugins: Escape output in error messages. - Build/Test Tools: Allow the PHPCS plugin in Composer configuration. - Craig
Bug#1018863: marked as pending in wordpress
Control: tag -1 pending Hello, Bug #1018863 in wordpress reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/wordpress/-/commit/c7b6b21a3fce6eee49536ffecd5e6858ae0b8ce3 New security release Closes: #1018863 Update to 6.0.2 (this message was generated automatically) -- Greetings https://bugs.debian.org/1018863
Processed: Bug#1018863 marked as pending in wordpress
Processing control commands: > tag -1 pending Bug #1018863 [src:wordpress] wordpress: 6.0.2 Security and Maintenance Release Added tag(s) pending. -- 1018863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1018863: marked as done (wordpress: 6.0.2 Security and Maintenance Release)
Your message dated Thu, 01 Sep 2022 09:27:03 + with message-id and subject line Bug#1018863: fixed in wordpress 6.0.2+dfsg1-1 has caused the Debian Bug report #1018863, regarding wordpress: 6.0.2 Security and Maintenance Release 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.) -- 1018863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wordpress Version: 6.0+dfsg1-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi From https://wordpress.org/news/2022/08/wordpress-6-0-2-security-and-maintenance-release/ there is a security and maintenance release for 6.0.x. Do the issues affect as well older series? Regards, Salvatore --- End Message --- --- Begin Message --- Source: wordpress Source-Version: 6.0.2+dfsg1-1 Done: Craig Small We believe that the bug you reported is fixed in the latest version of wordpress, 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. Craig Small (supplier of updated wordpress package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Sep 2022 18:41:07 +1000 Source: wordpress Architecture: source Version: 6.0.2+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Craig Small Changed-By: Craig Small Closes: 1018863 Changes: wordpress (6.0.2+dfsg1-1) unstable; urgency=medium . * New security release Closes: #1018863 - Possible link SQL injection within the Link API - XSS in Plugins screen - Output escaping issue within the_meta() Checksums-Sha1: 57c6689d353bae538f492d7dbccdfe8272006004 2394 wordpress_6.0.2+dfsg1-1.dsc 9f12ba7228fe2488c93656f270d149ba4f9e353c 15482564 wordpress_6.0.2+dfsg1.orig.tar.xz ac26d3955e8487563078a265de2525659c4c66f7 6825348 wordpress_6.0.2+dfsg1-1.debian.tar.xz 365bf98c486f9ffd12519dbcfc8551b15e561147 7661 wordpress_6.0.2+dfsg1-1_amd64.buildinfo Checksums-Sha256: 9160dbb638962f6f573e6c196dbe890be8f62e10ae0c2dcf04319acda27e326a 2394 wordpress_6.0.2+dfsg1-1.dsc 5dd5d7dc64194ce2e823a1a58512c3e69c7cd688b6f449686ca784db96b77444 15482564 wordpress_6.0.2+dfsg1.orig.tar.xz 6ef1d57317091b9f6f4e47996a2061d9376035d4a072c4c2e93ff729ecf44e98 6825348 wordpress_6.0.2+dfsg1-1.debian.tar.xz 469c6af62de2ad1c7688fcdc811ee039ea7a0becc128a6d17eb1cc2a0b468087 7661 wordpress_6.0.2+dfsg1-1_amd64.buildinfo Files: 224e25abe16a7b91699b00b6da30e8d2 2394 web optional wordpress_6.0.2+dfsg1-1.dsc c349a632725491e13fccb2733bbe3e0a 15482564 web optional wordpress_6.0.2+dfsg1.orig.tar.xz 19d465955c42a89df3fb7afc2cad92c6 6825348 web optional wordpress_6.0.2+dfsg1-1.debian.tar.xz 94ebcca5a416042fe803f522b33aba4a 7661 web optional wordpress_6.0.2+dfsg1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXT3w9TizJ8CqeneiAiFmwP88hOMFAmMQcIoACgkQAiFmwP88 hOOkwQ//ZFu1tAHdyl0ofjqWo6PLo+KBDsQQtwgIekaSBsNtN36wgvpTvw9SU3ij /uyq3TEfflrmKAnsYHjATxJsojFHjiYBE8dD+wDXMDzjpStV7rdSjZq4r/MeN4AU vAJJKlnAgd01u3qB3NHqplqsDbRWs93Jj9+bhmEvQP5LWGXAlet3s4p4L2GusR6Y r7zgsULOKNyl+dXn2ux/pu7feLBoXDvFaGcAPlhCbuUfkIVR2q84I8GoU0dqVYav LI86IfVckt4EtCE20tQYhg+hQ4UJCu2ST90tq2Neyi/UQR8xuy/5mL/UBOAOHZP5 DqZvq6OfRz4GB4Dep6dxyYijtxWPwMi0JawbJDON5xQbmrGXjF+gYlQW7VMk71+L qIoYpHNBpIda5X0WoWQqn07JBBYV8sfKJ/EelBlLwyzo7GFE5iNc1YZYp3R6qzWE mdGgbz3lpY6OIx8+QkMgKonhZXSOnRdXCymJsxgHvlmphFxCQmhlBWhCrKBJ1PyT pc1UsKlUQupZbppmXfwQ2HBXqxcxx/HvylU+cLZSa781nfqOmRzKOk8BtXimqDF1 yzMoAxYylgn3iIiiwv2sHlBlo5PATJjDEo7Xlk0+dD5G6FGPBn7LA4SM8GEH/nJW 71Sb4oh6jUSz+CEGVEIId3LnKA8KfPG57ngr1CzE7wfF/ljG+/U= =+PjZ -END PGP SIGNATURE End Message ---
Bug#1015733: ghc: ABI reproducibility broken in 9.0.2
On Thu, Sep 01, 2022 at 06:29AM, Paul Gevers wrote: > Ping. Can this please be looked at? This is affecting more and more packages > that can't migrate to testing (and I [Release Team hat on] don't want ghc in > testing with this bug). I will try to take a look, but I am not confident it will be something obvious I can fix. I read somewhere that disabling parallelism fixes this, but I have not tried it yet. Would this be acceptable? (not sure how much time GHC will take to build with -j1). -- Ilias
Bug#1015733: ghc: ABI reproducibility broken in 9.0.2
Hi Ilias, On 01-09-2022 13:26, Ilias Tsitsimpis wrote: I read somewhere that disabling parallelism fixes this, but I have not tried it yet. Would this be acceptable? I'd say yes. Long build times are not release critical issues, while this one is. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1018882: ruby-vcr: build times out after 150 minutes
Source: ruby-vcr Version: 6.0.0+really5.0.0-2 Severity: serious Tags: ftbfs Justification: ftbfs Dear maintainers, The last upload failed to build from source. https://buildd.debian.org/status/fetch.php?pkg=ruby-vcr&arch=all&ver=6.0.0%2Breally5.0.0-3&stamp=1661725468&raw=0 when VCR.real_http_connections_allowed? is returning false does not allow real HTTP requests or record them when ignore_hosts is configured to "127.0.0.1", "localhost" E: Build killed with signal TERM after 150 minutes of inactivity Paul
Bug#1017576: marked as done (nautilus-admin: Incompatible with Nautilus 43)
Your message dated Thu, 01 Sep 2022 12:19:16 + with message-id and subject line Bug#1017576: fixed in nautilus-admin 1.1.9-3.2 has caused the Debian Bug report #1017576, regarding nautilus-admin: Incompatible with Nautilus 43 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.) -- 1017576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nautilus-admin Severity: important Version: 1.1.9-3.1 Tags: patch sid bookworm Control: block 1016988 by -1 Nautilus 43 includes major API changes for Nautilus extensions. Code changes are needed to support this. Here is a merge request with the required changes https://salsa.debian.org/debian/nautilus-admin/-/merge_requests/1 Nautilus 43 and nautilus-python 4 are available in Debian Experimental. Thank you, Jesus Soto --- End Message --- --- Begin Message --- Source: nautilus-admin Source-Version: 1.1.9-3.2 Done: Jeremy Bicha We believe that the bug you reported is fixed in the latest version of nautilus-admin, 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. Jeremy Bicha (supplier of updated nautilus-admin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Sep 2022 07:56:08 -0400 Source: nautilus-admin Built-For-Profiles: noudeb Architecture: source Version: 1.1.9-3.2 Distribution: unstable Urgency: medium Maintainer: Carlos Maddela Changed-By: Jeremy Bicha Closes: 1017576 Changes: nautilus-admin (1.1.9-3.2) unstable; urgency=medium . * Non-maintainer upload . [ Jesús Soto ] * Add patch to add compatibility with nautilus 43 (Closes: #1017576) Checksums-Sha1: f77715603e60c552bf1f34f76f25e7155f97a510 2216 nautilus-admin_1.1.9-3.2.dsc 5451487f43526eeb5cd42bd37efe2365934c5ad4 9588 nautilus-admin_1.1.9-3.2.debian.tar.xz bc073671efd50613147fd05a47e7123e74418bf7 7339 nautilus-admin_1.1.9-3.2_source.buildinfo Checksums-Sha256: 18435ed631bee14c5e4b65ddaf94eeb5f622d11195d5f21382951f91610934e4 2216 nautilus-admin_1.1.9-3.2.dsc fae04231c52d98161696dc36cba48bab860925a6266a9b1eea839fd1dc246de0 9588 nautilus-admin_1.1.9-3.2.debian.tar.xz 7dd810ded5ae5d17e41e0365a2701303f79c4f9e84477bfbca6b5272c7d0eaa4 7339 nautilus-admin_1.1.9-3.2_source.buildinfo Files: fbb420993718a7e49fc2d0196865c7b8 2216 gnome optional nautilus-admin_1.1.9-3.2.dsc 9525c60ccb95705c485f5751f680bad1 9588 gnome optional nautilus-admin_1.1.9-3.2.debian.tar.xz f096c802434b795ae8c7f7e0a8ea466a 7339 gnome optional nautilus-admin_1.1.9-3.2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmMQnr8ACgkQ5mx3Wuv+ bH307A/8Dt/d8sM3vurnGfWgXUw0tvu3u55Nv9RGeyZ4Y8CxHiha34hPa9aHJB60 /mog0SOwJVsXLU9nZjliV3wBuFaYH0wf1fNTdptWMHmwG6UMW+wWEQn3gwH0xMfb RXATDqikzJKApoXzuJ3rsMFunNsb1/dyByPL0k8KmYhulbmlxZ8Hr7df92SCoyDK rJjbRtyipoUtjt3ri5sNxkJmJZJh+5bF4HkKJ5JVnsvtKslScdUnlYk+hXK51Ggc UQ2qOrJJ1jzoSMIG9XleG3VhhazDT/65SpG6camO/G3/DMQB33At/CaNI3osnrb2 wvjwEqgi30QQl9g4cjk5gR7ujSSvk/FTMpHeMaF0BAZsjbsyLsjjRCWiJLHEn5kg +i1VoGcYkelsfOox1LJ3n7mWyQeRc82WIjVXLTk7mC/KL1KCg1nqaCfZWM72QSSA tPyTXlibY+DHNhCTd1LDlkdIbgUNTjlBUJnJCE6sov8wtuhObmTISzWcVuUsusZ4 cfLvCSEyVdHy0NvhflIIdKyuPDTz/M9EhwvcWomPuShDKihOoVxzymePxDoC2tFN Awwmd0GQo5RoTOxsu4x6m1/9nteUrDXZ82hvV0WzBGt40ovS9Bho3nW6JFz0/4eB K+8/C4DK5bLdF+HwJK/1Hsb86ha4ZRjgnrE6kf50d+NBqR1oRBI= =4tAN -END PGP SIGNATURE End Message ---
Bug#1018090: marked as done (nautilus-hide: Patch for compatibility with older python3-nautilus)
Your message dated Thu, 01 Sep 2022 12:42:38 + with message-id and subject line Bug#1018090: fixed in nautilus-hide 0.2.3-8.1 has caused the Debian Bug report #1018090, regarding nautilus-hide: Patch for compatibility with older python3-nautilus 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.) -- 1018090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nautilus-hide Version: 0.2.3-9 Severity: important Tags: patch bookworm sid X-Debbugs-Cc: nathan.teodo...@canonical.com Hi there! The merge request[1]. [1]: https://salsa.debian.org/debian/nautilus-hide/-/merge_requests/1 -- System Information: Debian Release: bookworm/sid APT prefers kinetic APT policy: (500, 'kinetic'), (40, 'jammy') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-15-generic (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nautilus-hide depends on: ii nautilus 1:43~beta.1-2ubuntu2 ii python3-nautilus 1.2.3-3.1build1 nautilus-hide recommends no packages. nautilus-hide suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: nautilus-hide Source-Version: 0.2.3-8.1 Done: Jeremy Bicha We believe that the bug you reported is fixed in the latest version of nautilus-hide, 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. Jeremy Bicha (supplier of updated nautilus-hide package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 01 Sep 2022 08:21:02 -0400 Source: nautilus-hide Built-For-Profiles: noudeb Architecture: source Version: 0.2.3-8.1 Distribution: unstable Urgency: medium Maintainer: Carlos Maddela Changed-By: Jeremy Bicha Closes: 1018090 Changes: nautilus-hide (0.2.3-8.1) unstable; urgency=medium . * Non-maintainer upload . [ Nathan Pratta Teodosio ] * Patch for compatibility with nautilus 43 (Closes: #1018090) . [ Jeremy Bicha ] * Add patch to fix gettext import with newer Python3 versions Checksums-Sha1: fe75fc91bef3f42ef8fa196941b3cfe3ebcd83f3 1939 nautilus-hide_0.2.3-8.1.dsc aece70359cbb319aec4fe24bd7db7de772826c09 9004 nautilus-hide_0.2.3-8.1.debian.tar.xz 40c11a5894bf18df72a37001f2f4513198d63325 7335 nautilus-hide_0.2.3-8.1_source.buildinfo Checksums-Sha256: ee6bca75d96ba984ffef94fefeb5c2df175b8392c55581204ad56e7e48d10bc5 1939 nautilus-hide_0.2.3-8.1.dsc ea9b5cefd6c7a4bc8120e0de8bf163bcf041721a93b182a6aa1b2974290045f5 9004 nautilus-hide_0.2.3-8.1.debian.tar.xz eda2219682bd3070e5420d5ccf400be79897d56dedb1db2c51f3d6c9421c96c1 7335 nautilus-hide_0.2.3-8.1_source.buildinfo Files: 3e56c24b84ec3101285ee35154b05abc 1939 gnome optional nautilus-hide_0.2.3-8.1.dsc 142b54890099e28635e21bd0bc0a7f81 9004 gnome optional nautilus-hide_0.2.3-8.1.debian.tar.xz 89d9627628c61e05fa13af4ff284587b 7335 gnome optional nautilus-hide_0.2.3-8.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmMQo+8ACgkQ5mx3Wuv+ bH3+dhAArKFyDqUyfeslRvE3BWLE2ZsvybTFHoyAdrPvtCy1d95lWd5N38PpRF0R Ziba13j7TRyDHYL29HguU1DRci1ov94zLjUbBaPWgqA5/bmueN0BVpbxfkQHOtNO iKHMTVqkDCANBx4gAA0+nXM9AraMbXtW+2qRNb24xgt8Qao2Fkj4TsrLxagSoTSX 0/IAqKiBbDd+myBTHlEwoPwdQD66msxC5kocB7BQjpYwBwjWyeBrb2Qm361XhqgT 6NUI2KF18gEGS3a7p2QU0qHWiJr0H8O61vi0PJ9PJ1ZuwcLN0OUyKdAp6PI7WXEt jaIazXuJHAOy7V6SmjjBvchYR/cs1D8BB8R0SNI+tXZfx2wfr/lytxVexu4tNFU4 UIZv4mQnmHu95nO0oLPdGbEai+4b6hiLcvMp5zxcF+MQBw69QbciB9y83ckZD7rC lWVbAHnk6okqy+6PZne02VVYlUDPYGphKBXVU9oZTKgJSWGi0iRxx/8WxkGW3QDi 1FdWJI7aQ+32db9qB2yrp3lOuHZW4H+pUDogy9axDqyq//pbQcooj8pVrkkeENzj FaXAlZokFYe3QKPJTxFQ+WXCNqZOKGEhP7hmGz950fMoSN1dCkZtGxWbU/ohd4zC QhLLlGVxhPg8urQtWf0cF09DYFYJ09g9S13F166/ZeYZ++pVogY= =FMDL -END PGP SIGNATURE End Message ---
Bug#1017425: marked as done ([i386] Unconditional LFENCE instructions in FILL_RETURN_BUFFER)
Your message dated Thu, 01 Sep 2022 14:10:11 + with message-id and subject line Bug#1017425: fixed in linux 5.19.6-1 has caused the Debian Bug report #1017425, regarding [i386] Unconditional LFENCE instructions in FILL_RETURN_BUFFER 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.) -- 1017425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 5.10.136-1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 5.10.0-17-686-pae cannot boot on this Pentium III. The fan goes to full speed during initrd loading and the host reboots at that point. There is no screenshot to attach since there is no screen output after the "Loading initrd..." message from GRUB2. Reverting to 5.10.0-16-686-pae, the fan runs at low speed and the host boots normally. Martin-Éric - -- Package-specific info: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 8 model name : Pentium III (Coppermine) stepping: 6 microcode : 0x8 cpu MHz : 865.440 cache size : 256 KB physical id : 0 siblings: 1 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fdiv_bug: no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pse36 mmx fxsr sse cpuid pti bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit bogomips: 1730.88 clflush size: 32 cache_alignment : 32 address sizes : 36 bits physical, 32 bits virtual power management: ** Kernel log: boot messages should be attached ** Model information ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 82815 815 Chipset Host Bridge and Memory Controller Hub [8086:1130] (rev 02) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: agpgart-intel 00:01.0 PCI bridge [0604]: Intel Corporation 82815 815 Chipset AGP Bridge [8086:1131] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:1f.0 ISA bridge [0601]: Intel Corporation 82801BA ISA Bridge (LPC) [8086:2440] (rev 01) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: nouveau Kernel modules: nouveau 02:04.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller [10ec:8169] (rev 10) Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family PCI Gigabit Ethernet NIC [10ec:8169] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: r8169 Kernel modules: r8169 02:08.0 Ethernet controller [0200]: Intel Corporation 82801BA/BAM/CA/CAM Ethernet Controller [8086:2449] (rev 01) Subsystem: Compaq Computer Corporation EtherExpress PRO/100 VM [0e11:0012] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: e100 Kernel modules: e100 02:09.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller [10ec:8169] (rev 10) Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family PCI Gigabit Et
Bug#1018776: marked as done (linux-image-5.18.0-4-686-pae Kernel panic on Pentium 3 and Athlon XP)
Your message dated Thu, 01 Sep 2022 14:10:11 + with message-id and subject line Bug#1017425: fixed in linux 5.19.6-1 has caused the Debian Bug report #1017425, regarding linux-image-5.18.0-4-686-pae Kernel panic on Pentium 3 and Athlon XP 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.) -- 1017425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 5.18.16-1 Severity: important X-Debbugs-Cc: m...@posteo.de Dear Maintainer, * What led up to the situation? Booting Kernel linux-image-5.18.0-4-686-pae on a Pentium 3 600 (Coppermine) or an Athlon XP (I can find out the exact model number if you need). Older kernel versions work. The current kernel works on a Pentium 4 3 GHz (I can find out the exact model number if you need). Error message: https://picr.eu/images/2022/08/29/qUlKO.jpg German discussion in a newsgroup: https://de.comp.os.unix.linux.misc.narkive.com/JzfZxhgj/kernelpanic-5-18-0-4-686-pae-attempted-to-kill-the-idle-task * What exactly did you do (or not do) that was effective (or ineffective)? Booting this specific kernel, older kernels work. * What was the outcome of this action? Kernel panic, can't boot system. * What outcome did you expect instead? Booting the system the nromal way on the specified hardware. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge [8086:7190] (rev 03) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: agpgart-intel 00:01.0 PCI bridge [0604]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge [8086:7191] (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- Reset- FastB2B+ PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:10.0 Ethernet controller [0200]: 3Com Corporation 3c905C-TX/TX-M [Tornado] [10b7:9200] (rev 78) Subsystem: 3Com Corporation 3C905CX-TX/TX-M Fast Etherlink for PC Management NIC [10b7:1000] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: 3c59x Kernel modules: 3c59x 00:14.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 02) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: mgag200 Kernel modules: matroxfb_base, mgag200 ** USB devices: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 5.18.0-3-686-pae (SMP w/1 CPU thread; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-5.18.0-4-686-pae depends on: ii initramfs-tools [linux-initramfs-tool] 0.142 ii kmod30+20220630-3 ii linux-base 4.9 Versions of packages linux-image-5.18.0-4-686-pae recommends: pn apparmor ii firmware-linux-free 20200122-1 Versions of packages linux-image-5.18.0-4-686-pae suggests: pn debian-kernel-handbook ii grub-pc 2.06-3 pn linux-doc-5.18 Versions of packages linux-image-5.18.0-4-686-pae is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-no
Processed: severity of 1018191 is grave
Processing commands for cont...@bugs.debian.org: > severity 1018191 grave Bug #1018191 [src:libapreq2] libapreq2: CVE-2022-22728: multipart form parse memory corruption Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1018191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015027: php-dragonmantank-cron-expression: Fix FTBFS salsa MR
I have proposed a salsa MR to skip the offending tests at https://salsa.debian.org/php-team/pear/php-dragonmantank-cron-expression/-/merge_requests/1. I also forwarded the patch upstream with an explanation on why the tests should be skipped at the moment [1]. [1] https://github.com/dragonmantank/cron-expression/issues/133 -- Athos Ribeiro
Bug#1013062: marked as done (visualboyadvance: ftbfs with GCC-12)
Your message dated Thu, 01 Sep 2022 14:40:23 +
with message-id
and subject line Bug#1013062: fixed in visualboyadvance 1.8.0.dfsg-5.1
has caused the Debian Bug report #1013062,
regarding visualboyadvance: ftbfs with GCC-12
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.)
--
1013062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:visualboyadvance
Version: 1.8.0.dfsg-5
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12
[This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.
The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/visualboyadvance_1.8.0.dfsg-5_unstable_gcc12.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.
[...]
../thumb.h:26:47: warning: iteration 17 invokes undefined behavior
[-Waggressive-loop-optimizations]
26 |oldreg[xxx]=reg[xxx].I; \
|~~~^~~
../thumb.h:1945:18: note: in expansion of macro ‘UPDATE_OLD_REG’
1945 | UPDATE_OLD_REG
| ^~
../thumb.h:25:43: note: within this loop
25 |for (xxx=0; xxx<18; xxx++){ \
|~~~^~~
../thumb.h:1945:18: note: in expansion of macro ‘UPDATE_OLD_REG’
1945 | UPDATE_OLD_REG
| ^~
../thumb.h:26:47: warning: iteration 17 invokes undefined behavior
[-Waggressive-loop-optimizations]
26 |oldreg[xxx]=reg[xxx].I; \
|~~~^~~
../thumb.h:1426:18: note: in expansion of macro ‘UPDATE_OLD_REG’
1426 | UPDATE_OLD_REG
| ^~
../thumb.h:25:43: note: within this loop
25 |for (xxx=0; xxx<18; xxx++){ \
|~~~^~~
../thumb.h:1426:18: note: in expansion of macro ‘UPDATE_OLD_REG’
1426 | UPDATE_OLD_REG
| ^~
../thumb.h:26:47: warning: iteration 17 invokes undefined behavior
[-Waggressive-loop-optimizations]
26 |oldreg[xxx]=reg[xxx].I; \
|~~~^~~
../thumb.h:1402:18: note: in expansion of macro ‘UPDATE_OLD_REG’
1402 | UPDATE_OLD_REG
| ^~
../thumb.h:25:43: note: within this loop
25 |for (xxx=0; xxx<18; xxx++){ \
|~~~^~~
../thumb.h:1402:18: note: in expansion of macro ‘UPDATE_OLD_REG’
1402 | UPDATE_OLD_REG
| ^~
../thumb.h:26:47: warning: iteration 17 invokes undefined behavior
[-Waggressive-loop-optimizations]
26 |oldreg[xxx]=reg[xxx].I; \
|~~~^~~
../thumb.h:1380:14: note: in expansion of macro ‘UPDATE_OLD_REG’
1380 | UPDATE_OLD_REG
| ^~
../thumb.h:25:43: note: within this loop
25 |for (xxx=0; xxx<18; xxx++){ \
|~~~^~~
../thumb.h:1380:14: no
Bug#1017425: closed by Debian FTP Masters (reply to Salvatore Bonaccorso ) (Bug#1017425: fixed in linux 5.19.6-1)
This bug was reported against Stable. It cannot be considered as
closed for as long as a new 5.10 kernel including the fix hasn't been
published.
Martin-Éric
On Thu, Sep 1, 2022 at 5:15 PM Debian Bug Tracking System
wrote:
>
> This is an automatic notification regarding your Bug report
> which was filed against the src:linux package:
>
> #1017425: [i386] Unconditional LFENCE instructions in FILL_RETURN_BUFFER
>
> It has been closed by Debian FTP Masters
> (reply to Salvatore Bonaccorso ).
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP Masters
> (reply to Salvatore Bonaccorso
> ) by
> replying to this email.
>
>
> --
> 1017425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017425
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Debian FTP Masters
> To: 1017425-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Thu, 01 Sep 2022 14:10:11 +
> Subject: Bug#1017425: fixed in linux 5.19.6-1
> Source: linux
> Source-Version: 5.19.6-1
> Done: Salvatore Bonaccorso
>
> We believe that the bug you reported is fixed in the latest version of
> linux, 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.
> Salvatore Bonaccorso (supplier of updated linux package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Format: 1.8
> Date: Thu, 01 Sep 2022 09:04:35 +0200
> Source: linux
> Architecture: source
> Version: 5.19.6-1
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Kernel Team
> Changed-By: Salvatore Bonaccorso
> Closes: 1016807 1017425 1017894 1017972 1018752
> Changes:
> linux (5.19.6-1) unstable; urgency=medium
> .
>* New upstream stable update:
> https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.19.1
> https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.19.2
> - Revert "net: usb: ax88179_178a needs FLAG_SEND_ZLP" (Closes: #1017894)
> https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.19.3
> https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.19.4
> https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.19.5
> https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.19.6
> - mm/gup: fix FOLL_FORCE COW security issue and remove FOLL_COW
>(CVE-2022-2590)
> - af_key: Do not call xfrm_probe_algs in parallel (CVE-2022-3028)
> - [x86] nospec: Unwreck the RSB stuffing
> - [x86] nospec: Fix i386 RSB stuffing (Closes: #1017425)
> - bpf: Don't use tnum_range on array range checking for poke descriptors
>(CVE-2022-2905)
> .
>[ Ben Hutchings ]
>* d/tests/kbuild: Fix default-flavour lookup for arches with no featuresets
>* d/tests/kbuild: Make flavour lookup verbose
>* d/lib/python/debian_linux, d/templates: Use variable for binary package
> name
>* lintian: Update overrides in linux-image-*-dbg for lintian 2.115
>* d/{signing_templates/,}rules.real: Run dh_lintian for all packages
>* [hppa,mips,mipsel,powerpc] lintian: Override error for 64-bit kernels
>* [mips64el,mipsel,ppc64el] lintian: Override error for unstripped vmlinux
>* [arm64] lintian: Override errors for vdso32.so in linux-image-*-dbg
>* android: Remove CONFIG_ANDROID:
> - Drop "wireguard: Clear keys after suspend despite CONFIG_ANDROID=y"
> - pm/sleep: Add PM_USERSPACE_AUTOSLEEP Kconfig
> - remove CONFIG_ANDROID
> - Enable/disable ANDROID_BINDER_IPC to match previous configuration
> .
>[ Vincent Blut ]
>* [x86] drivers/hwmon: Enable SENSORS_ASUS_WMI and SENSORS_ASUS_EC as
> modules
>* [x86] drivers/platform/x86: Enable NVIDIA_WMI_EC_BACKLIGHT as module
> (Closes: #1017972)
>* [arm64] drivers/spi: Enable SPI_GPIO and SPI_SUN6I as modules
> (Closes: #1016807)
> .
>[ Diederik de Haas ]
>* [arm64] drivers/gpu/drm/rockchip: Explicitly enable ROCKCHIP_VOP
> .
>[ Helge Deller ]
>* [hppa] Drop CONFIG_PATA_LEGACY for hppa architecture
> .
>[ Salvatore Bonaccorso ]
>* [rt] Refresh "rcutorture: Also force sched priority to timersd on
> boosting
> test."
>* Drop setting of CRYPTO_BLAKE2S
> crypto: blake2s shash module was removed upstream.
>* [arm] arch/arm/crypto: Enable CRYPTO_BLAKE2S_ARM
>* certs: Rotate to use
Bug#1017147: marked as done (quvi: FTBFS: ../../src/pbar/lpbar.h:24:56: error: ‘write’ redeclared as different kind of symbol)
Your message dated Thu, 01 Sep 2022 15:35:41 +
with message-id
and subject line Bug#1017147: fixed in quvi 0.9.5-0.1
has caused the Debian Bug report #1017147,
regarding quvi: FTBFS: ../../src/pbar/lpbar.h:24:56: error: ‘write’ redeclared
as different kind of 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.)
--
1017147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: quvi
Version: 0.9.4-1.2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I../.. -DLOCALEDIR=\""/usr/share/locale"\" -I../../src/get/
> -I../../src/pbar/ -I../../src/util/ -I../../src/ -I/usr/include/quvi-0.9
> -I/usr/include/x86_64-linux-gnu -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 libget_la-http.lo `test -f 'http.c' ||
> echo './'`http.c
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../..
> -DLOCALEDIR=\"/usr/share/locale\" -I../../src/get/ -I../../src/pbar/
> -I../../src/util/ -I../../src/ -I/usr/include/quvi-0.9
> -I/usr/include/x86_64-linux-gnu -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 http.c -fPIC -DPIC -o .libs/libget_la-http.o
> In file included from http.c:29:
> ../../src/pbar/lpbar.h:24:56: error: ‘write’ redeclared as different kind of
> symbol
>24 | typedef enum { retrieved_already, forced_skip, resume, write }
> lpbar_mode;
> |^
> In file included from /usr/include/x86_64-linux-gnu/bits/sigstksz.h:24,
> from /usr/include/signal.h:328,
> from /usr/include/glib-2.0/glib/gbacktrace.h:36,
> from /usr/include/glib-2.0/glib.h:34,
> from /usr/include/glib-2.0/glib/gi18n.h:21,
> from http.c:24:
> /usr/include/unistd.h:378:16: note: previous declaration of ‘write’ with type
> ‘ssize_t(int, const void *, size_t)’ {aka ‘long int(int, const void *, long
> unsigned int)’}
> 378 | extern ssize_t write (int __fd, const void *__buf, size_t __n) __wur
> |^
> make[4]: *** [Makefile:460: libget_la-http.lo] Error 1
The full build log is available from:
http://qa-logs.debian.net/2022/08/13/quvi_0.9.4-1.2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220813&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: quvi
Source-Version: 0.9.5-0.1
Done: Boyuan Yang
We believe that the bug you reported is fixed in the latest version of
quvi, 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.
Boyuan Yang (supplier of updated quvi package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 25 Aug 2022 10:53:26 -0400
Source: quvi
Architecture: source
Version: 0.9.5-0.1
Distribution: unstable
Urgency: hig
Bug#1017425: closed by Debian FTP Masters (reply to Salvatore Bonaccorso ) (Bug#1017425: fixed in linux 5.19.6-1)
Hi, On Thu, Sep 01, 2022 at 06:03:41PM +0300, Martin-Éric Racine wrote: > This bug was reported against Stable. It cannot be considered as > closed for as long as a new 5.10 kernel including the fix hasn't been > published. it very well can. The BTS can close a bug in multiple versions which will be done here. A second time with the version for 5.10.y when it hits stable. Regards, Salvatore
Bug#1009915: sysvinit: Please align with manpages-l10n and afterwards activate man page translations
Hello Torsten et al, On Wed, Aug 31, 2022 at 11:04:25PM +0200, Thorsten Glaser wrote: > On Wed, 31 Aug 2022, Mark Hindley wrote: > > > > there seems to be one manpage (in bootlogd) missing conflict handling: > > > > > > /usr/share/man/fr/man8/bootlogd.8.gz > > > > Thanks. I was under the impression that manpages-i10n had changed to > > systemd versions (which doesn't have bootlogd.8) but apparently not. I > > think we should continue to use the manpages-i10n version and not have > > any more dpkg diversions than are absolutely necessary. No. This is not the intention, quite the contrary. This file probably escaped me, because I did not realize that the package bootlogd originates from sysvinit. I can do another upload removing this file as well. > > I am away for a week, but will resolve this once I am back. > > Perhaps in this time a french speaker can compare the two versions, > from sysvinit and manpages-l10n, and see which one is “better”, then > contribute that to sysvinit so manpages-l10n can remove theirs as > bootlogd isn’t provided with systemd? Yes, that would be the best option. A few days ago I informed all translation teams about the transfer of translations to sysvinit, so if the French team could integrate the translation of bootlogd there, that'll be great. I suggest we keep this source file in the manpage l10n upstream repository for a few more weeks and then I ask upstream (Mario Blättermann) to move it to the archive. (Best if the French team would indicate a good time). For Debian, as stated above, I can do another upload removing this file as well. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature
Bug#1016235: marked as done (passwordsafe: FTBFS: pws_time.cpp:30:10: error: ‘localtime_r’ was not declared in this scope; did you mean ‘localtime64_r’?)
Your message dated Thu, 01 Sep 2022 16:36:00 + with message-id and subject line Bug#1016235: fixed in passwordsafe 1.15.0+dfsg-1 has caused the Debian Bug report #1016235, regarding passwordsafe: FTBFS: pws_time.cpp:30:10: error: ‘localtime_r’ was not declared in this scope; did you mean ‘localtime64_r’? 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.) -- 1016235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016235 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: passwordsafe Version: 1.12.0+dfsg-1 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 -fPIC -Wall -I../../core -I../.. > `/usr/bin/wx-config --debug=no --unicode=yes --inplace --cxxflags` > -I/usr/include/ykpers-1 -pthread -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 > -std=c++11 -O -DUNICODE -DNDEBUG -c xsendstring.cpp -o > ../../../obj/unicoderelease/os/xsendstring.o > pws_time.cpp: In function ‘int localtime64_r(const __time64_t*, tm*)’: > pws_time.cpp:30:10: error: ‘localtime_r’ was not declared in this scope; did > you mean ‘localtime64_r’? >30 | return localtime_r(tp, result) != nullptr; > | ^~~ > | localtime64_r > pws_time.cpp: In function ‘int pws_os::asctime(TCHAR*, size_t, const tm*)’: > pws_time.cpp:36:3: error: ‘asctime_r’ was not declared in this scope >36 | asctime_r(t, cbuf); > | ^ > g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -fPIC -Wall -I../../core -I../.. > `/usr/bin/wx-config --debug=no --unicode=yes --inplace --cxxflags` > -I/usr/include/ykpers-1 -pthread -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 > -std=c++11 -O -DUNICODE -DNDEBUG -c keyname.cpp -o > ../../../obj/unicoderelease/os/keyname.o > make[4]: *** [Makefile:81: ../../../obj/unicoderelease/os/pws_time.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/07/28/passwordsafe_1.12.0+dfsg-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220728&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: passwordsafe Source-Version: 1.15.0+dfsg-1 Done: William Blough We believe that the bug you reported is fixed in the latest version of passwordsafe, 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 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. William Blough (supplier of updated passwordsafe package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Sep 2022 11:33:35 -0400 Source: passwordsafe Architecture: source Version: 1.15.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: William Blough Changed-By: William Blough Closes: 1016235 Changes: passwordsafe (1.15.0+dfsg-1) unstable; urgency=medium . * Update watch file to fix pgpsigurlmangle * Remove temp build files on repack * New upstream version 1.15.0+dfsg * Update watch file to fix pgpsigurlmangle * Remove temp build files on repack * New upstream version 1.15.0+dfsg * Refresh existing patches * Update packaging to handle upstream buildsystem change * Fix FTBFS with GCC12
Bug#1009915: sysvinit: Please align with manpages-l10n and afterwards activate man page translations
Hello Thorsten, On Thu, Sep 01, 2022 at 06:39:18PM +0200, Thorsten Glaser wrote: > […] > > Yes, that would be the best option. A few days ago I informed all > > translation teams about the transfer of translations to sysvinit, so > > if the French team could integrate the translation of bootlogd there, > > that'll be great. > > ok, great! > > > For Debian, as stated above, I can do another upload removing this > > file as well. > > Thanks. Feel free to reassign/close this bug at will then… or do we > need another sysvinit upload with updated Replaces/Breaks/… as well, > Andreas? I'll do the upload on the weekend. I guess the best is that you close it afterwards? Or reassign it to manpages-l10n? Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature
Bug#1009915: sysvinit: Please align with manpages-l10n and afterwards activate man page translations
Hi Helge, […] > Yes, that would be the best option. A few days ago I informed all > translation teams about the transfer of translations to sysvinit, so > if the French team could integrate the translation of bootlogd there, > that'll be great. ok, great! > For Debian, as stated above, I can do another upload removing this > file as well. Thanks. Feel free to reassign/close this bug at will then… or do we need another sysvinit upload with updated Replaces/Breaks/… as well, Andreas? bye, //mirabilos -- Infrastrukturexperte • tarent solutions GmbH Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/ Telephon +49 228 54881-393 • Fax: +49 228 54881-235 HRB AG Bonn 5168 • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg /⁀\ The UTF-8 Ribbon ╲ ╱ Campaign against Mit dem tarent-Newsletter nichts mehr verpassen: ╳ HTML eMail! Also, https://www.tarent.de/newsletter ╱ ╲ header encryption!
Bug#1018896: grcompiler: FTBFS on big endian
Source: grcompiler Version: 5.2.1-0.1 Severity: serious Tags: ftbfs Control: forwarded -1 grcompiler fails to build from scratch on big endian systems, including s390x, because of test fails: https://buildd.debian.org/status/fetch.php?pkg=grcompiler&arch=s390x&ver=5.2.1-0.1&stamp=1661942327 test 1 Start 1: compile_SchTest 1: Test command: /<>/obj-s390x-linux-gnu/compiler/grcompiler "-D" "-v4" "-e" "/<>/obj-s390x-linux-gnu/test/GrcRegressionTest/SchTest.gdlerr.txt" "/<>/test/GrcRegressionTest/fonts/SchMain.gdl" "/<>/test/GrcRegressionTest/fonts/SchInput.ttf" "SchTest.ttf" 1: Working Directory: /<>/obj-s390x-linux-gnu/test/GrcRegressionTest 1: Environment variables: 1: GDLPP=/<>/obj-s390x-linux-gnu/preprocessor/gdlpp 1: LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/include/../lib 1: Test timeout computed to be: 1500 test 4 Start 4: compile_CharisTest 4: Test command: /<>/obj-s390x-linux-gnu/compiler/grcompiler "-D" "-v2" "-e" "/<>/obj-s390x-linux-gnu/test/GrcRegressionTest/CharisTest.gdlerr.txt" "/<>/test/GrcRegressionTest/fonts/CharisMain.gdl" "/<>/test/GrcRegressionTest/fonts/CharisInput.ttf" "CharisTest.ttf" 4: Working Directory: /<>/obj-s390x-linux-gnu/test/GrcRegressionTest 4: Environment variables: 4: GDLPP=/<>/obj-s390x-linux-gnu/preprocessor/gdlpp 4: LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/include/../lib 4: Test timeout computed to be: 1500 1: Frexx C Preprocessor v1.5 Copyright (C) by FrexxWare 1993 - 1997. 1: Revised by SIL International for Graphite Description Language, Aug 23 2022 1: Graphite Compiler Version 5.2.1 [release build] 1: Copyright (c) 2002-2021, by SIL International. All rights reserved. 1: Reading input font... 1: 1: GDL file: /<>/test/GrcRegressionTest/fonts/SchMain.gdl 1: PreProcessor: /<>/obj-s390x-linux-gnu/preprocessor/gdlpp 1: Input TT file: /<>/test/GrcRegressionTest/fonts/SchInput.ttf 1: Output TT file: SchTest.ttf 1: Output font name: Scheherazade GrcRegTest (unchanged) 1: Silf table version requested: 4.0 1: 1: Parsing file /<>/test/GrcRegressionTest/fonts/SchMain.gdl... 1: Initial processing... 1: Checking for errors... 1: Compiling... 1: [Generating FSMs: table 0 pass 0 1 (mc 4 fsm 5 5) 2 (mc 4 fsm 45 19) 3 (mc 2 fsm 3 3) 4 (mc 13 fsm 120 57) 5 (mc 15 fsm 41 15) 6 (mc 8 fsm 46 36); table 1 pass 0 1 (mc 21 fsm 235 64) 2 (mc 9 fsm 52 16) 3 (mc 32 fsm 1623 368); ] 1: Debug files generated. 1: Debugger XML file generated. 1: Compilation successful! 1: 1 warning has been output to /<>/obj-s390x-linux-gnu/test/GrcRegressionTest/SchTest.gdlerr.txt (121 warnings ignored). 1/15 Test #1: compile_SchTest . Passed0.22 sec test 7 Start 7: compile_PigLatinTest_v2 7: Test command: /<>/obj-s390x-linux-gnu/compiler/grcompiler "-D" "-v2" "-p" "-e" "/<>/obj-s390x-linux-gnu/test/GrcRegressionTest/PigLatinTest_v2.gdlerr.txt" "/<>/test/GrcRegressionTest/fonts/PigLatinMain.gdl" "/<>/test/GrcRegressionTest/fonts/PigLatinInput.ttf" "PigLatinTest_v2.ttf" "PigLatin GrRegTest V2" 7: Working Directory: /<>/obj-s390x-linux-gnu/test/GrcRegressionTest 7: Environment variables: 7: GDLPP=/<>/obj-s390x-linux-gnu/preprocessor/gdlpp 7: LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/include/../lib 7: Test timeout computed to be: 1500 7: Frexx C Preprocessor v1.5 Copyright (C) by FrexxWare 1993 - 1997. 7: Revised by SIL International for Graphite Description Language, Aug 23 2022 4: Frexx C Preprocessor v1.5 Copyright (C) by FrexxWare 1993 - 1997. 4: Revised by SIL International for Graphite Description Language, Aug 23 2022 4: Graphite Compiler Version 5.2.1 [release build] 4: Copyright (c) 2002-2021, by SIL International. All rights reserved. 4: Reading input font... 4: 4: GDL file: /<>/test/GrcRegressionTest/fonts/CharisMain.gdl 4: PreProcessor: /<>/obj-s390x-linux-gnu/preprocessor/gdlpp 4: Input TT file: /<>/test/GrcRegressionTest/fonts/CharisInput.ttf 4: Output TT file: CharisTest.ttf 4: Output font name: Charis GrcRegTest (unchanged) 4: Silf table version requested: 2.0 4: 4: Parsing file /<>/test/GrcRegressionTest/fonts/CharisMain.gdl... 4: Initial processing... 4: Checking for errors... 4: Compiling... 4: [Generating FSMs: table 0 pass 0 1 (mc 138 fsm 3349 279) 2 (mc 39 fsm 363 92); table 1 pass 0 1 (mc 25 fsm 3493 474) 2 (mc 5 fsm 1080 493) 3 (mc 6 fsm 1927 733); ] 4: Debug files generated. 4: Debugger XML file generated. 4: Compilation successful! 4: 1 warning has been output to /<>/obj-s390x-linux-gnu/test/GrcRegressionTest/CharisTest.gdlerr.txt (128 warnings ignored). 2/15 Test #4: compile_CharisTest .. Passed2.33 sec test 10 Start 10: compile_PigLatinTest_v3 10: Test command: /<>/obj-s390x-linux-gnu/compiler/grcompiler "-D" "-v3" "-e" "/<>/obj-s390x-linux-gnu/test/GrcRegressionTest/PigLatinTest_v3.gdlerr.txt" "/<>/test/GrcRegressionTest/fonts/PigLatinMain.gdl" "/<>/test/GrcRegressionTest/fonts/PigLatinInput.ttf" "PigLatinTest_v3.ttf" 10: Working Directory: /<>/obj-s390x-linux-gnu/test/Gr
Processed: forward
Processing commands for cont...@bugs.debian.org: > forwarded 1018896 https://github.com/silnrsi/grcompiler/issues/45 Bug #1018896 [src:grcompiler] grcompiler: FTBFS on big endian Set Bug forwarded-to-address to 'https://github.com/silnrsi/grcompiler/issues/45'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1018896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:mkautodoc
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:mkautodoc
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was
debian-bts-l...@lists.debian.org).
> # remote status report for #1016299 (http://bugs.debian.org/1016299)
> # Bug title: mkautodoc: FTBFS: dh_auto_test: error: pybuild --test
> --test-pytest -i python{version} -p 3.10 returned exit code 13
> # * https://github.com/tomchristie/mkautodoc/pull/33
> # * remote status changed: (?) -> closed
> # * closed upstream
> tags 1016299 + fixed-upstream
Bug #1016299 [src:mkautodoc] mkautodoc: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p 3.10 returned exit code 13
Added tag(s) fixed-upstream.
> usertags 1016299 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1016299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:passwordsafe
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:passwordsafe
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was
debian-bts-l...@lists.debian.org).
> # remote status report for #1016235 (http://bugs.debian.org/1016235)
> # Bug title: passwordsafe: FTBFS: pws_time.cpp:30:10: error: localtime_r was
> not declared in this scope; did you mean localtime64_r?
> # * https://github.com/pwsafe/pwsafe/pull/865
> # * remote status changed: (?) -> closed
> # * closed upstream
> tags 1016235 + fixed-upstream
Bug #1016235 {Done: William Blough } [src:passwordsafe]
passwordsafe: FTBFS: pws_time.cpp:30:10: error: ‘localtime_r’ was not declared
in this scope; did you mean ‘localtime64_r’?
Added tag(s) fixed-upstream.
> usertags 1016235 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1016235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016235
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1018898: gconf-editor: Intent to request removal from Debian
Source: gconf-editor Version: 3.0.1-6 Severity: serious Tags: bookworm sid gconf-editor was removed from Testing two and a half years ago. Its only purpose is to enable editing gconf settings which are only used by a very small number of packages and are functionally obsolete. I remember that the last time I tried to remove this package years ago, the current maintainer had strong feelings against it so I figured it was best for me to file this bug first. Thank you, Jeremy Bicha
Bug#1011881: php-dapphp-radius: FTBFS: tests fail
This is now fixed in the salsa repository. Please, upload a new version. -- Athos Ribeiro
Bug#1007000: thin FTBFS on IPV6-only buildds
This is a consequence of this bug filed against ruby-eventmachine: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998097 -- Lucas Kanashiro
Processed: notfound 1017425 in 5.18.14-1
Processing commands for cont...@bugs.debian.org:
> # only introduced in 5.18.16-1 for unstable
> notfound 1017425 5.18.14-1
Bug #1017425 {Done: Salvatore Bonaccorso } [src:linux]
[i386] Unconditional LFENCE instructions in FILL_RETURN_BUFFER
Bug #1017494 {Done: Salvatore Bonaccorso } [src:linux]
[i386] Unconditional LFENCE instructions in FILL_RETURN_BUFFER
Bug #1018060 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-5.18.0-4-686-pae: crashes right away in switch_to_asm
Bug #1018776 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-5.18.0-4-686-pae Kernel panic on Pentium 3 and Athlon XP
No longer marked as found in versions linux/5.18.14-1.
No longer marked as found in versions linux/5.18.14-1.
No longer marked as found in versions linux/5.18.14-1.
No longer marked as found in versions linux/5.18.14-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1017425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017425
1017494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017494
1018060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018060
1018776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1017637: havp: Not working anymore since linux-image-* v5.15.
On 2022-08-18 19:36:28 [+], Scott Kitterman wrote: Hi Scott, > I agree. It's been dead upstream for a long time. I think this is a > logical point to put an end to trying to keep it alive in Debian. nice to hear from you! Sorry for not replying earlier but I'm kind of busy… Anyway, I managed to fill a RM bug for this. > Scott K Sebastian
Processed (with 1 error): let's close this....
Processing commands for cont...@bugs.debian.org: > retitle 1003045 libreoffice: Since testing update on Jan 2, 2022, Bug #1003045 [libreoffice] libreoffice: Since testing update on Jan 2, 2021, libreoffice doesn't start. Changed Bug title to 'libreoffice: Since testing update on Jan 2, 2022,' from 'libreoffice: Since testing update on Jan 2, 2021, libreoffice doesn't start.'. > libreoffice doesn't start. Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. -- 1003045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003045: marked as done (libreoffice: Since testing update on Jan 2, 2022,)
Your message dated Thu, 1 Sep 2022 22:27:14 +0200 with message-id <5da2324a-a096-4fb4-0b9d-90537fb83...@debian.org> and subject line let's close this has caused the Debian Bug report #1003045, regarding libreoffice: Since testing update on Jan 2, 2022, 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.) -- 1003045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libreoffice Version: 1:7.2.4-3 Severity: grave Justification: renders package unusable * What led up to the situation? A routine update of Debian testing (bookworm) on Jan 2, 2021 led to a situation where clicking on LibreOffice's or LibreOffice apps' icons is ineffective ; similarly, launching an application from a console's command line returns after a few seconds. * What exactly did you do (or not do) that was effective (or ineffective)? I tried to reinstall Libreoffice applications by : dpkg -l "*libre*office*" | grep -e "^ii" | sed -re "s/[ \t]+/ /g" | cut -d " " -f 2 | sudo xargs apt-get install --reinstall * What was the outcome of this action? Clicking on the gnome menu icons is ineffective (spinning cursor for a few seconds) ; starting an app from the command line initially started the document recovery dialog box ; after having cancelled that operation, starting a LibreOffice application returns after about one second. * What outcome did you expect instead? A normal function of libreoffice app. Possibly related : sudo apt dist-upgrade leaves libc++1 unupgraded, whereas sudo apt install -s wants to uninstall libc++1-11 and libc++abi1-11 and install libc++1-13 libc++abi1-13 libunwind-13. So far, I did **not** proceed. HTH ... -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (650, 'testing'), (60, 'unstable'), (50, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libreoffice depends on: ii libreoffice-base1:7.2.4-3 ii libreoffice-calc1:7.2.4-3 ii libreoffice-core1:7.2.4-3 ii libreoffice-draw1:7.2.4-3 ii libreoffice-impress 1:7.2.4-3 ii libreoffice-math1:7.2.4-3 ii libreoffice-report-builder-bin 1:7.2.4-3 ii libreoffice-writer 1:7.2.4-3 ii python3-uno 1:7.2.4-3 Versions of packages libreoffice recommends: ii fonts-crosextra-caladea 20130214-2.1 ii fonts-crosextra-carlito 20130920-1.1 ii fonts-dejavu2.37-2 ii fonts-liberation1:1.07.4-11 ii fonts-liberation2 2.1.5-1 ii fonts-linuxlibertine5.3.0-6 ii fonts-noto-core 20201225-1 ii fonts-noto-extra20201225-1 ii fonts-noto-mono 20201225-1 ii fonts-noto-ui-core 20201225-1 ii fonts-sil-gentium-basic 1.102-1.1 ii libreoffice-java-common 1:7.2.4-3 ii libreoffice-nlpsolver 0.9+LibO7.2.4-3 ii libreoffice-report-builder 1:7.2.4-3 ii libreoffice-script-provider-bsh 1:7.2.4-3 ii libreoffice-script-provider-js 1:7.2.4-3 ii libreoffice-script-provider-python 1:7.2.4-3 ii libreoffice-sdbc-mysql 1:7.2.4-3 ii libreoffice-sdbc-postgresql 1:7.2.4-3 ii libreoffice-wiki-publisher 1.2.0+LibO7.2.4-3 Versions of packages libreoffice suggests: ii cups-bsd 2.3.3op2-7 ii default-jre [java8-runtime] 2:1.11-72 ii firefox-esr 91.4.0esr-1 ii ghostscript 9.55.0~dfsg-3 ii gnupg2.2.27-2 ii gpa 0.10.0-3+b1 ii gstreamer1.0-libav 1.18.5-1 ii gstreamer1.0-plugins-bad 1.18.5-1+b4 ii gstreamer1.0-plugins-base1.18.5-1 ii gstreamer1.0-plugins-good1.18.5-1+b1 ii gstreamer1.0-plugins-ugly1.18.5-1 ii hunspell-en-us [hunspell-dictionary] 1:2020.12.07-1 ii hunspell-fr-classical [hunspell-dictionary] 1:7.0-1 ii hyphen-en-us [hyphen-h
Bug#1006994: marked as done (thin: FTBFS on s390x)
Your message dated Thu, 1 Sep 2022 17:30:12 -0300
with message-id <7e6a2eda-cf88-73b7-f189-974ed32be...@debian.org>
and subject line thin: FTBFS on s390x
has caused the Debian Bug report #1006994,
regarding thin: FTBFS on s390x
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.)
--
1006994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: thin
Version: 1.8.0-1
Severity: serious
Justification: FTBFS
Dear maintainer(s),
I binNMU'd your package for the ruby2.7 removal transition. Your package fails
to build from source on s390x.
Paul
https://buildd.debian.org/status/fetch.php?pkg=thin&arch=s390x&ver=1.8.0-1%2Bb2&stamp=1646899039&raw=0
Failures:
1) Daemonizing should kill process in pid file
Failure/Error: expect{sleep 0.1 until File.exist?(subject.pid_file)}.to
take_less_then(10)
should take less then 10 sec to run
# ./spec/daemonizing_spec.rb:186:in `wait_for_server_to_start'
# ./spec/daemonizing_spec.rb:89:in `block (2 levels) in '
--- End Message ---
--- Begin Message ---
I uploaded thin/1.8.0-2 to the archive and it built just fine on s390x:
https://buildd.debian.org/status/fetch.php?pkg=thin&arch=s390x&ver=1.8.0-2&stamp=1662059965&raw=0
--
Lucas Kanashiro--- End Message ---
Processed: retitle 1003045 to libreoffice: Since testing update on Jan 2, 2022, libreoffice doesn't start.
Processing commands for cont...@bugs.debian.org:
> retitle 1003045 libreoffice: Since testing update on Jan 2, 2022, libreoffice
> doesn't start.
Bug #1003045 {Done: Rene Engelhard } [libreoffice]
libreoffice: Since testing update on Jan 2, 2022,
Changed Bug title to 'libreoffice: Since testing update on Jan 2, 2022,
libreoffice doesn't start.' from 'libreoffice: Since testing update on Jan 2,
2022,'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1003045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003045
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1005483: marked as done (pangomm: FTBFS: ../untracked/pango/pangomm/attrlist.cc:38:20: error: ‘pango_parse_markup’ was not declared in this scope)
Your message dated Thu, 1 Sep 2022 16:42:11 -0400 with message-id and subject line Re: pangomm: FTBFS: ../untracked/pango/pangomm/attrlist.cc:38:20: error: ‘pango_parse_markup’ was not declared in this scope has caused the Debian Bug report #1005483, regarding pangomm: FTBFS: ../untracked/pango/pangomm/attrlist.cc:38:20: error: ‘pango_parse_markup’ 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.) -- 1005483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pangomm Version: 2.46.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > c++ -Ipango/pangomm/libpangomm-1.4.so.1.0.30.p -Ipango -I../pango > -I../untracked/pango -I/usr/include/glibmm-2.4 > -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sigc++-2.0 > -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/cairomm-1.0 > -I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/cairo > -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 > -I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi > -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch > -Wnon-virtual-dtor -std=c++11 -pedantic -Wall -Wextra -Wformat-security > -Wsuggest-override -Wshadow -Wno-long-long -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread > -DPANGOMM_BUILD=1 -MD -MQ > pango/pangomm/libpangomm-1.4.so.1.0.30.p/.._.._untracked_pango_pangomm_attrlist.cc.o > -MF > pango/pangomm/libpangomm-1.4.so.1.0.30.p/.._.._untracked_pango_pangomm_attrlist.cc.o.d > -o > pango/pangomm/libpangomm-1.4.so.1.0.30.p/.._.._untracked_pango_pangomm_attrlist.cc.o > -c ../untracked/pango/pangomm/attrlist.cc > ../untracked/pango/pangomm/attrlist.cc: In constructor > ‘Pango::AttrList::AttrList(const Glib::ustring&, gunichar)’: > ../untracked/pango/pangomm/attrlist.cc:38:20: error: ‘pango_parse_markup’ was > not declared in this scope >38 | gboolean bTest = pango_parse_markup(markup_text.c_str(), -1 /* > means null-terminated */, accel_marker, > |^~ > ../untracked/pango/pangomm/attrlist.cc: In constructor > ‘Pango::AttrList::AttrList(const Glib::ustring&, gunichar, Glib::ustring&, > gunichar&)’: > ../untracked/pango/pangomm/attrlist.cc:65:20: error: ‘pango_parse_markup’ was > not declared in this scope >65 | gboolean bTest = pango_parse_markup(markup_text.c_str(), -1 /* > means null-terminated */, accel_marker, > |^~ > [7/32] c++ -Ipango/pangomm/libpangomm-1.4.so.1.0.30.p -Ipango -I../pango > -I../untracked/pango -I/usr/include/glibmm-2.4 > -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sigc++-2.0 > -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/cairomm-1.0 > -I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/cairo > -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 > -I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi > -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch > -Wnon-virtual-dtor -std=c++11 -pedantic -Wall -Wextra -Wformat-security > -Wsuggest-override -Wshadow -Wno-long-long -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread > -DPANGOMM_BUILD=1 -MD -MQ > pango/pangomm/libpangomm-1.4.so.1.0.30.p/.._.._untracked_pango_pangomm_context.cc.o > -MF > pango/pangomm/libpangomm-1.4.so.1.0.30.p/.._.._untracked_pango_pangomm_context.cc.o.d > -o > pango/pangomm/libpangomm-1.4.so.1.0.30.p/.._.._untracked_pango_pangomm_context.cc.o > -c ../untracked/pango/pangomm/context.cc > [8/32] c++ -Ipango/pangomm/libpangomm-1.4.so.1.0.30.p -Ipango -I../pango > -I../untracked/pango -I/usr/include/glibmm-2.4 > -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sigc++-2.
Bug#1016600: siconos: vtk[6,7] removal
On Wed, Aug 03, 2022 at 10:42:08PM +0200, Sebastian Ramacher wrote: > Source: siconos > Version: 4.3.1+dfsg-2 > Severity: serious > X-Debbugs-Cc: sramac...@debian.org > Tags: sid bookworm > Control: block 1016597 by -1 > User: gl...@debian.org > Usertags: vtk6_vtk7_removal > > Based on #1013156 and similar bugs: > > Dear maintainer, > > Debian archive has now three major versions of the VTK (The > Visualization Toolkit) package: vtk6, vtk7 and vtk9. Old vesions > (vtk6 and vtk7) are not supported by upstream and the package itself > is not easy for the mainance. > > We aim to drop old and deprecated version vtk6 and vtk7 packages before > the freeze of the Debian 12 Bookworm. Your package depends on vtk6 or > vtk7. Thus we ask you to migrate it to the latest vtk9 package. Two observations regarding the usage of VTK in siconos: There is WITH_VTK in siconos that does not seem to build with VTK 9, but it's anyway not enabled. The only current usage of VTK is python3-vtk7 in siconos-mechanics-tools. This might need upstrream fixes like https://github.com/siconos/siconos/pull/437 > Cheers cu Adrian
Bug#984030: marked as done (d-itg: ftbfs with GCC-11)
Your message dated Thu, 01 Sep 2022 21:50:46 + with message-id and subject line Bug#984030: fixed in d-itg 2.8.1-r1023-5 has caused the Debian Bug report #984030, regarding d-itg: 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.) -- 984030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984030 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:d-itg Version: 2.8.1-r1023-4 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/d-itg_2.8.1-r1023-4_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. [...] |^~ newran2.cpp: In function ‘DividedRandom& operator/(Random&, Random&)’: newran2.cpp:1003:4: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 1003 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp:1003:28: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 1003 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp: In function ‘AddedSelectedRandom& operator+(SelectedRandom&, SelectedRandom&)’: newran2.cpp:1121:4: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 1121 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp:1121:28: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 1121 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp: In function ‘AddedSelectedRandom& operator+(AddedSelectedRandom&, SelectedRandom&)’: newran2.cpp:1128:4: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 1128 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp:1128:28: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 1128 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp: In function ‘AddedSelectedRandom& operator+(SelectedRandom&, AddedSelectedRandom&)’: newran2.cpp:1135:4: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 1135 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp:1135:28: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 1135 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp: In function ‘AddedSelectedRandom& operator+(AddedSelectedRandom&, AddedSelectedRandom&)’: newran2.cpp:1142:4: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 1142 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp:1142:28: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 1142 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp: In member function ‘SelectedRandom& Random::operator()(double)’: newran2.cpp:1148:4: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 1148 |if (!r) ErrorNoSpace(); return *r; |^~ newran2.cpp:1148:28: note: ...this statement, b
Bug#1016884: marked as done (heimdal: FTBFS with glibc >= 2.34)
Your message dated Thu, 01 Sep 2022 23:05:59 + with message-id and subject line Bug#1016884: fixed in heimdal 7.7.0+dfsg-5 has caused the Debian Bug report #1016884, regarding heimdal: FTBFS with 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.) -- 1016884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016884 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: heimdal Version: 1.6~rc2+dfsg-9+deb8u1 Severity: serious Justification: FTBFS Hello, Now that glibc provides a closefrom function, heimdal doesn't build its own rk_closefrom function any more, and thus the libroken18-heimdal.symbols check complains: - rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 +#MISSING: 7.7.0+dfsg-4+b1# rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 Samuel -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 5.19.0 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Samuel --- Pour une évaluation indépendante, transparente et rigoureuse ! Je soutiens la Commission d'Évaluation de l'Inria. --- End Message --- --- Begin Message --- Source: heimdal Source-Version: 7.7.0+dfsg-5 Done: Brian May We believe that the bug you reported is fixed in the latest version of heimdal, 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 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Brian May (supplier of updated heimdal package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 02 Sep 2022 07:59:59 +1000 Source: heimdal Architecture: source Version: 7.7.0+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Brian May Changed-By: Brian May Closes: 1016884 1017244 Changes: heimdal (7.7.0+dfsg-5) unstable; urgency=medium . * Fix missing closefrom symbol. Closes: #1016884, #1017244. * Fix spelling of dependency in changelog. * Fix override_dh_fixperms typo, use 700 for /var/lib/heimdal-kdc/ * Remove default --parallel from dh call. * Remove unused debian/upstream/signing-key.asc key. * Fix Multi-Arch headers. heimdal-multidev is not co-installable, so heimdal-dev cannot be co-installable either. Checksums-Sha1: edf59c1c1e099df299d6f318c69b93d7a77f 3479 heimdal_7.7.0+dfsg-5.dsc 2b71fff4c2e4a4c8b2c6ab3e4f5dc40b26b6388f 5945252 heimdal_7.7.0+dfsg.orig.tar.xz cd09b37e664d92d151bb563f924f9a0deb16c616 129192 heimdal_7.7.0+dfsg-5.debian.tar.xz ef2d4f37d90ccd9174e43ed5e4aec7448bc19046 7458 heimdal_7.7.0+dfsg-5_source.buildinfo Checksums-Sha256: 8c0ae8b16bfa218f6f1763dd85f83cff49ae2f482a1ac912e268d250921f23b1 3479 heimdal_7.7.0+dfsg-5.dsc 6822c9547188b753b6325047fda9255744e4ebbbe02bb0dade78c261061fefac 5945252 heimdal_7.7.0+dfsg.orig.tar.xz 573ba1426b523b93311df443984ecb0e5d9b1e3b176a7f876dc6c7e68319889f 129192 heimdal_7.7.0+dfsg-5.debian.tar.xz c06fa6a8e1ced175305f50e64d875ffe6343bdd73b5dc54c03aae64d6d7ab8df 7458 heimdal_7.7.0+dfsg-5_source.buildinfo Files: 97646bf1f72da8895cb1ea628572005b 3479 net optional heimdal_7.7.0+dfsg-5.dsc 4400de10f7a569fe14ecb2641aea341b 5945252 net optional heimdal_7.7.0+dfsg.orig.tar.xz 6750c51a85ea34dc276fe504ad15f9a4 129192 net optional heimdal_7.7.0+dfsg-5.debian.tar.xz e55286a785b685108098be3835bef991 7458 net optional heimdal_7.7.0+dfsg-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEKpwfR8DOwu5vyB4TKpJZkldkSvoFAmMRL0oACgkQKpJZkldk Sv
Bug#1017244: marked as done (heimdal: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Thu, 01 Sep 2022 23:05:59 + with message-id and subject line Bug#1017244: fixed in heimdal 7.7.0+dfsg-5 has caused the Debian Bug report #1017244, regarding heimdal: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below 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.) -- 1017244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017244 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: heimdal Version: 7.7.0+dfsg-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_makeshlibs -plibsl0-heimdal -- -c4 > dh_makeshlibs -plibkafs0-heimdal -- -c4 > dh_makeshlibs -plibgssapi3-heimdal -- -c4 > dh_makeshlibs -plibotp0-heimdal -- -c4 > dh_makeshlibs -plibkdc2-heimdal -V"libkdc2-heimdal (>= > 1.4.0~git20110226.dfsg.2-1)" -- -c4 > dh_makeshlibs -plibasn1-8-heimdal -V"libasn1-8-heimdal (>= > 1.4.0~git20110226.dfsg.2-1)" -- -c4 > dh_makeshlibs -plibheimbase1-heimdal -V"libheimbase1-heimdal (>= > 1.4.0~git20110226.dfsg.2-1)" -- -c4 > dh_makeshlibs -plibhcrypto4-heimdal -V"libhcrypto4-heimdal (>= > 1.4.0~git20110226.dfsg.2-1)" -- -c4 > dh_makeshlibs -plibhdb9-heimdal -V"libhdb9-heimdal (>= > 1.4.0~git20110226.dfsg.2-1)" -- -c4 > dh_makeshlibs -plibhx509-5-heimdal -V"libhx509-5-heimdal (>= > 1.4.0~git20110226.dfsg.2-1)" -- -c4 > dh_makeshlibs -plibkadm5srv8-heimdal -V"libkadm5srv8-heimdal (>= > 1.4.0~git20110226.dfsg.2-1)" -- -c4 > dh_makeshlibs -plibkadm5clnt7-heimdal -V"libkadm5clnt7-heimdal (>= > 1.6~rc2+dfsg)" -- -c4 > dh_makeshlibs -plibkrb5-26-heimdal -V"libkrb5-26-heimdal (>= > 1.4.0~git20110226.dfsg.2-1)" -- -c4 > dh_makeshlibs -plibheimntlm0-heimdal -V"libheimntlm0-heimdal (>= > 1.4.0~git20110226.dfsg.2-1)" -- -c4 > dh_makeshlibs -plibroken18-heimdal -V"libroken18-heimdal (>= > 1.4.0~git20110226.dfsg.2-1)" -- -c4 > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libroken18-heimdal/DEBIAN/symbols doesn't > match completely debian/libroken18-heimdal.symbols > --- debian/libroken18-heimdal.symbols (libroken18-heimdal_7.7.0+dfsg-4_amd64) > +++ dpkg-gensymbols8TrN02 2022-08-14 02:53:18.881781629 + > @@ -42,7 +42,7 @@ > rk_cloexec_dir@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 > rk_cloexec_file@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 > rk_cloexec_socket@HEIMDAL_ROKEN_1.0 1.6~git20131117 > - rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 > +#MISSING: 7.7.0+dfsg-4# rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 > rk_copyhostent@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 > rk_dns_free_data@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 > rk_dns_lookup@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 > dh_makeshlibs: error: failing due to earlier errors > make[1]: *** [debian/rules:30: override_dh_makeshlibs] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/08/13/heimdal_7.7.0+dfsg-4_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220813&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: heimdal Source-Version: 7.7.0+dfsg-5 Done: Brian May We believe that the bug you reported is fixed in the latest version of heimdal, 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. Brian May (supplier of updated heimdal
Bug#919697: arcanist: file conflict with arc
Hi! On Wed, 2022-08-10 at 01:29:27 +0200, Guillem Jover wrote: > [ The bug has been (correctly) bumped back to serious. Sorry that I > have not engaged about this bug in the past, but the reply to simply > ignore policy looked rather off-putting, I just noticed the reply > below, which seemed encouraging! :) ] > > On Sat, 2019-01-26 at 11:20:13 +0100, Sylvestre Ledru wrote: > > As we shipped the previous release with this bug, we are close to > > the freeze and there is not easy fix, > > I propose that we fix this issue for the next stable release. > > Could you please rename the archanist /usr/bin/arc into > /usr/bin/arcanist? Or if that's not feasible, then stop installing the > symlink in PATH, and document that users might want to add the /usr/share > /arcanist/bin/ into their own PATH? Or do both? > > Renaming the binary from the arc package, which matches the package > name itself, seems unfair, as it has existed upstream and has been in > the Debian archive for way way longer, and in addition the idea of > potentially having a binary package arc with a non-arc program, and > arcanist providing an arc program seems rather confusing and just > wrong. :) > > Otherwise, all these package will get removed in the coming days. So I'd > also appreciate if you could reassign these bugs to arcanist. So we have reached the point at which arc is getting autoremoved from testing as the RC is still filed against it too. :( Could some arcanist maintainer please check this, and ideally agree to reassign this bug to arcanist? If necessary I'm willing to prepare a patch for arcanist to stop installing as bin/arc, as described above, if this would expedite things. Thanks, Guillem
Bug#1018922: kbibtex crashes on startup
Package: kbibtex Version: 0.9.90-1+b1 Severity: grave Justification: renders package unusable Backtrace [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe5fff640 (LWP 150852)] [New Thread 0x7fffe563b640 (LWP 150853)] [New Thread 0x7fffdcdff640 (LWP 150855)] [New Thread 0x7fffd15ff640 (LWP 150856)] [New Thread 0x7fffd0dfe640 (LWP 150857)] [New Thread 0x7fffcbfff640 (LWP 150858)] [New Thread 0x7fffcb7fe640 (LWP 150859)] [New Thread 0x7fffb7473640 (LWP 150860)] [New Thread 0x7fffb6c72640 (LWP 150861)] [New Thread 0x7fffb6471640 (LWP 150862)] [New Thread 0x7fffb5c70640 (LWP 150863)] [New Thread 0x7fffb546f640 (LWP 150865)] Thread 1 "kbibtex" received signal SIGSEGV, Segmentation fault. 0x77bbfbac in FileModel::element (this=0x0, row=0) at ./src/data/models/filemodel.cpp:388 #0 0x77bbfbac in FileModel::element (this=0x0, row=0) at ./src/data/models/filemodel.cpp:388 #1 0x77f1dafd in SortFilterFileModel::filterAcceptsRow (this=0x573c4560, source_row=, source_parent=...) at ./src/gui/file/sortfilterfilemodel.cpp:147 #2 0x7607e6d6 in QSortFilterProxyModelPrivate::create_mapping (this=this@entry=0x573c58b0, source_parent=...) at itemmodels/qsortfilterproxymodel.cpp:504 #3 0x76088504 in QSortFilterProxyModel::setSourceModel (this=0x573c4560, sourceModel=) at itemmodels/qsortfilterproxymodel.cpp:2152 #4 0x77f1efe1 in SortFilterFileModel::setSourceModel (this=this@entry=0x573c4560, model=0x573c5620) at ./src/gui/file/sortfilterfilemodel.cpp:39 #5 0x7fffc802cc04 in KBibTeXPart::KBibTeXPartPrivate::openFile (this=this@entry=0x57339c70, url=..., localFilePath=...) at ./src/parts/part.cpp:385 #6 0x7fffc80247d0 in KBibTeXPart::openFile (this=0x572f0790) at ./src/parts/part.cpp:956 #7 0x77b23355 in KParts::ReadOnlyPartPrivate::openLocalFile (this=this@entry=0x5733f470) at ./src/readonlypart.cpp:180 #8 0x77b2441e in KParts::ReadOnlyPart::openUrl (this=0x572f0790, url=...) at ./src/readonlypart.cpp:141 #9 0x555ac42f in OpenFileInfo::OpenFileInfoPrivate::createPart (this=0x55a42550, newWidgetParent=0x558fe280, newServicePtr=...) at ./src/program/openfileinfo.cpp:138 #10 0x555aae64 in OpenFileInfo::part (this=this@entry=0x55d78d90, parent=parent@entry=0x558fe280, servicePtr=...) at ./src/program/openfileinfo.cpp:262 #11 0x555840ee in MDIWidget::setFile (this=0x558fe280, openFileInfo=0x55d78d90, servicePtr=...) at ./src/program/mdiwidget.cpp:255 #12 0x5557deab in QtPrivate::FunctorCall, QtPrivate::List >, void, void (MDIWidget::*)(OpenFileInfo*, QExplicitlySharedDataPointer)>::call (arg=, o=, f=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:152 #13 QtPrivate::FunctionPointer)>::call >, void> (arg=, o=, f=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:185 #14 QtPrivate::QSlotObject), QtPrivate::List >, void>::impl (which=, this_=, r=, a=, ret=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:418 #15 0x760e89af in QtPrivate::QSlotObjectBase::call (a=0x7fffd630, r=0x558fe280, this=0x572ce050) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #16 doActivate (sender=0x55d889e0, signal_index=3, argv=0x7fffd630) at kernel/qobject.cpp:3886 #17 0x760e1d6f in QMetaObject::activate (sender=sender@entry=0x55d889e0, m=m@entry=0x555c5fe0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffd630) at kernel/qobject.cpp:3946 #18 0x555772a4 in OpenFileInfoManager::currentChanged (this=this@entry=0x55d889e0, _t1=, _t1@entry=0x55d78d90, _t2=...) at ./obj-x86_64-linux-gnu/src/program/kbibtex_autogen/EWIEGA46WW/moc_openfileinfo.cpp:280 #19 0x555a904c in OpenFileInfoManager::setCurrentFile (this=0x55d889e0, openFileInfo=openFileInfo@entry=0x55d78d90, servicePtr=...) at ./src/program/openfileinfo.cpp:713 #20 0x555a929b in operator() (__closure=0x55d76be0) at ./src/program/openfileinfo.cpp:522 #21 QtPrivate::FunctorCall, QtPrivate::List<>, void, OpenFileInfoManager::OpenFileInfoManager(QObject*):: >::call (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146 #22 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256 #23 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x55d76bd0, r=, a=, ret=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:443 #24 0x760ec852 in QtPrivate::QSlotObjectBase::call (a=0x7fffd710, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #25 QSingleShotTimer::timerEvent (this=0x55a423d0) at ke
Bug#1018924: libgc FTBFS: architecture-specific symbol handling removed
Source: libgc Version: 1:8.2.2-1 Severity: serious Tags: ftbfs Hi, 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. The general quality of the upload seems questionable as well: * 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. * The debian/changelog entry contains duplicates. * Lots of symbols were dropped from the symbols file without bumping soname. Possibly, this may lead to incorrect dependencies on libgc in downstream builds. * 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. 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. Helmut
Processed: src:hslogger: fails to migrate to testing for too long: part of unfinshed ghc transition?
Processing control commands: > close -1 1.3.1.0+dfsg-1 Bug #1018925 [src:hslogger] src:hslogger: fails to migrate to testing for too long: part of unfinshed ghc transition? Marked as fixed in versions hslogger/1.3.1.0+dfsg-1. Bug #1018925 [src:hslogger] src:hslogger: fails to migrate to testing for too long: part of unfinshed ghc transition? Marked Bug as done -- 1018925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018925 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1018925: src:hslogger: fails to migrate to testing for too long: part of unfinshed ghc transition?
Source: hslogger Version: 1.3.1.0-1 Severity: serious Control: close -1 1.3.1.0+dfsg-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:hslogger has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package is part of the unfinished ghc transition. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=hslogger OpenPGP_signature Description: OpenPGP digital signature
Bug#1018926: src:meson: fails to migrate to testing for too long: unresolved RC bug
Source: meson Version: 0.62.2-1 Severity: serious Control: close -1 0.63.1-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1017087 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:meson has been trying to migrate for 61 days [2]. Hence, I am filing this bug. The version of your package in unstable has an unresolved RC bug: #1017087. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=meson OpenPGP_signature Description: OpenPGP digital signature
Processed: src:meson: fails to migrate to testing for too long: unresolved RC bug
Processing control commands:
> close -1 0.63.1-1
Bug #1018926 [src:meson] src:meson: fails to migrate to testing for too long:
unresolved RC bug
Marked as fixed in versions meson/0.63.1-1.
Bug #1018926 [src:meson] src:meson: fails to migrate to testing for too long:
unresolved RC bug
Marked Bug as done
> block -1 by 1017087
Bug #1018926 {Done: Paul Gevers } [src:meson] src:meson:
fails to migrate to testing for too long: unresolved RC bug
1018926 was not blocked by any bugs.
1018926 was not blocking any bugs.
Added blocking bug(s) of 1018926: 1017273, 1017237, 1017296, 1018732, 1017243,
1017303, and 1017087
--
1018926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#919697: arcanist: file conflict with arc
Le 02/09/2022 à 01:10, Guillem Jover a écrit : Hi! On Wed, 2022-08-10 at 01:29:27 +0200, Guillem Jover wrote: [ The bug has been (correctly) bumped back to serious. Sorry that I have not engaged about this bug in the past, but the reply to simply ignore policy looked rather off-putting, I just noticed the reply below, which seemed encouraging! :) ] On Sat, 2019-01-26 at 11:20:13 +0100, Sylvestre Ledru wrote: As we shipped the previous release with this bug, we are close to the freeze and there is not easy fix, I propose that we fix this issue for the next stable release. Could you please rename the archanist /usr/bin/arc into /usr/bin/arcanist? Or if that's not feasible, then stop installing the symlink in PATH, and document that users might want to add the /usr/share /arcanist/bin/ into their own PATH? Or do both? Renaming the binary from the arc package, which matches the package name itself, seems unfair, as it has existed upstream and has been in the Debian archive for way way longer, and in addition the idea of potentially having a binary package arc with a non-arc program, and arcanist providing an arc program seems rather confusing and just wrong. :) Otherwise, all these package will get removed in the coming days. So I'd also appreciate if you could reassign these bugs to arcanist. So we have reached the point at which arc is getting autoremoved from testing as the RC is still filed against it too. :( Could some arcanist maintainer please check this, and ideally agree to reassign this bug to arcanist? If necessary I'm willing to prepare a patch for arcanist to stop installing as bin/arc, as described above, if this would expedite things. I don't think renaming is the right approach against an MS-DOS software (and I still think that Debian's policy is too binary for this). However, as: * phabricator is dying * Richard, Christoph and myself didn't show a strong interest to keep it alive (it is currently broken in unstable). Please do what you want. ;) Cheers Sylvestre
Bug#1018930: pcs: CVE-2022-2735: Obtaining an authentication token for hacluster user leads to privilege escalation
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
Processed: pcs: CVE-2022-2735: Obtaining an authentication token for hacluster user leads to privilege escalation
Processing control commands: > found -1 0.10.8-1 Bug #1018930 [src:pcs] pcs: CVE-2022-2735: Obtaining an authentication token for hacluster user leads to privilege escalation Marked as found in versions pcs/0.10.8-1. -- 1018930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
