Processed: Re: pandas: autopkgtest regression in testing: No tables found
Processing control commands: > tags -1 fixed-upstream pending Bug #979621 [src:pandas] pandas: autopkgtest regression in testing: No tables found Added tag(s) fixed-upstream and pending. -- 979621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979621 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 977258 is normal
Processing commands for cont...@bugs.debian.org: > severity 977258 normal Bug #977258 [libssreflect-coq] libssreflect-coq: ABI break by coq binNMU Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 977258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962203: NMU
Il 11/01/21 01:28, Paul Wise ha scritto: > A Mennucc1, would you be interested in having assistance with the > codebase and the service? that's OK for me What is the best debian-ish way to collaborate? There are some problems to address (a few urgent): how do we discuss? mailing list? does `salsa` have a way to open a chat/mailing list for us to use? a. signature.asc Description: OpenPGP digital signature
Bug#975789: marked as pending in golang-github-xenolf-lego
Control: tag -1 pending Hello, Bug #975789 in golang-github-xenolf-lego 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/go-team/packages/golang-github-xenolf-lego/-/commit/35f13f91f7295148a5509cc58107f92713f728f3 Fix FTBFS against nrdcg-goinwx-dev 0.8 (Closes: #975789) (this message was generated automatically) -- Greetings https://bugs.debian.org/975789
Processed: Bug#975789 marked as pending in golang-github-xenolf-lego
Processing control commands: > tag -1 pending Bug #975789 [src:golang-github-xenolf-lego] golang-github-xenolf-lego: FTBFS: src/github.com/go-acme/lego/providers/dns/inwx/inwx.go:85:6: assignment mismatch: 1 variable but d.client.Account.Login returns 2 values Added tag(s) pending. -- 975789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979758: xxhash: broken pkgconfig file
Source: xxhash
Version: 0.8.0-1
Severity: serious
tags: patch
Hello, after trying hard to see why python3-pkgconfig was not detecting xxhash
I discovered that the Version field was empty
https://github.com/Cyan4973/xxHash/commit/b4dbf5fefc37b8a5f80b3bbc6b8ff639cf5f0ec2
This trivial commit fixes it.
To reproduce:
python3
>>> import pkgconfig
>>> pkgconfig.installed('libxxhash', '>= 0.7.3')
True
This is what is expected
G.
Processed: affects 979590
Processing commands for cont...@bugs.debian.org: > affects 979590 chromium Bug #979590 [libx11] libx11 possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium Bug #979618 [libx11] libx11 possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium Added indication that 979590 affects chromium Added indication that 979618 affects chromium > thanks Stopping processing here. Please contact me if you need assistance. -- 979590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979590 979618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979590: libx11-xcb1: Updating to 1.7.0-1 from 1.6.12-1 breaks chromium and google chrome
Re: Faidon Liambotis > It turned out that for me, the cause was a disparity between libx11-xcb1 > and libx11-6 -- the former was at 2:1.7.0-1, while the latter was at > 2:1.6.12-1 (don't ask why...). I had the same here on testing+unstable (the latter on lower pin priority), and upgrading libx11-6 fixed the problem. chromium depends on libx11-6 (>= 2:1.4.99.1), libx11-xcb1 (>= 2:1.7.0) which explains why only libx11-xcb1 got pulled from unstable. Christoph
Bug#979760: vdjtools: autopkgtest failure: "java: not found"
Package: src:vdjtools Version: 1.2.1+git20190311-2 Severity: serious X-Debbugs-Cc: tmanc...@debian.org, debian-med-packag...@lists.alioth.debian.org Dear maintainer, testing migration excuses show that vdjtools' autopkgtests fail to run. https://qa.debian.org/excuses.php?package=vdjtools https://ci.debian.net/data/autopkgtest/testing/amd64/v/vdjtools/8647479/log.gz autopkgtest [05:08:10]: test run-unit-test: [--- /usr/bin/vdjtools: 10: java: not found autopkgtest [05:08:11]: test run-unit-test: ---] autopkgtest [05:08:11]: test run-unit-test: - - - - - - - - - - results - - - - - - - - - - run-unit-testFAIL non-zero exit status 127 autopkgtest [05:08:11]: summary run-unit-testFAIL non-zero exit status 127 -- Juhani
Bug#979666: marked as done (cross-toolchain-base_50_all-buildd.changes REJECTED)
Your message dated Mon, 11 Jan 2021 11:49:38 +0100 with message-id <84fdb3f3-acf8-5dca-c469-137407258...@debian.org> and subject line 51 successfully built has caused the Debian Bug report #979666, regarding cross-toolchain-base_50_all-buildd.changes REJECTED 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.) -- 979666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cross-toolchain-base Version: 50 Severity: serious - Forwarded message from Debian FTP Masters - From: Debian FTP Masters To: all / amd64 / i386 Build Daemon Date: Sat, 09 Jan 2021 21:18:45 + Subject: cross-toolchain-base_50_all-buildd.changes REJECTED Message-Id: Version check failed: Your upload included the binary package libc6-amd64-cross, version 2.31-9cross1, for all, however unstable already has version 2.31-9cross1. Uploads to unstable must have a higher version than present in unstable. Mapping sid to unstable. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. - End forwarded message - --- End Message --- --- Begin Message --- 51 successfully built.--- End Message ---
Bug#979727: racon: FTBFS: fatal error: bioparser/bioparser.hpp: No such file or directory
Control: tags -1 pending On Sun, 10 Jan 2021 21:13:32 +0100 Sebastian Ramacher wrote: > | /<>/src/polisher.cpp:20:10: fatal error: > bioparser/bioparser.hpp: No such file or directory > | 20 | #include "bioparser/bioparser.hpp" > | | ^ > | compilation terminated. > | make[3]: *** [CMakeFiles/racon.dir/build.make:111: > CMakeFiles/racon.dir/src/polisher.cpp.o] Error 1 > > See > https://buildd.debian.org/status/fetch.php?pkg=racon&arch=amd64&ver=1.4.13-2%2Bb1&stamp=1610291712&raw=0 Michael, I think you are already fixing this problem. I wanted to let you know that bug #979727 should probably be closed in the next upload's changelog. https://salsa.debian.org/med-team/racon/-/commit/9da51296c87af89a046e8c70cdfcb18adf3153ae Thanks, Juhani Numminen
Processed: Re: Bug#979727: racon: FTBFS: fatal error: bioparser/bioparser.hpp: No such file or directory
Processing control commands: > tags -1 pending Bug #979727 [src:racon] racon: FTBFS: fatal error: bioparser/bioparser.hpp: No such file or directory Added tag(s) pending. -- 979727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979664: marked as done (apache2: autopkgtest regression in testing: Failed test 2 in t/modules/data.t at line 21)
Your message dated Mon, 11 Jan 2021 11:18:32 + with message-id and subject line Bug#979664: fixed in apache2 2.4.46-4 has caused the Debian Bug report #979664, regarding apache2: autopkgtest regression in testing: Failed test 2 in t/modules/data.t at line 21 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.) -- 979664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979664 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apache2 Version: 2.4.46-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent change in testing the autopkgtest of your package started to fail. I copied some of the output at the bottom of this report. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul https://ci.debian.net/data/autopkgtest/testing/amd64/a/apache2/9549366/log.gz # Failed test 2 in t/modules/data.t at line 21 t/modules/data.t Failed 1/2 subtests [...] Test Summary Report --- t/modules/data.t (Wstat: 0 Tests: 2 Failed: 1) Failed test: 2 Files=134, Tests=10102, 318 wallclock secs ( 3.23 usr 0.30 sys + 201.11 cusr 50.96 csys = 255.60 CPU) Result: FAIL Failed 1/134 test programs. 1/10102 subtests failed. [warning] server localhost:8529 shutdown [ error] error running tests (please examine t/logs/error_log) OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: apache2 Source-Version: 2.4.46-4 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of apache2, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated apache2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 11 Jan 2021 11:58:23 +0100 Source: apache2 Architecture: source Version: 2.4.46-4 Distribution: unstable Urgency: medium Maintainer: Debian Apache Maintainers Changed-By: Xavier Guimard Closes: 979664 Changes: apache2 (2.4.46-4) unstable; urgency=medium . * Ignore other random another test failures (Closes: #979664) Checksums-Sha1: bda62f5b58a48e56bbfceb5f41b7bd968c7fc263 3501 apache2_2.4.46-4.dsc a7c3eb412e1624e3e967754e6e701a129c736eef 882336 apache2_2.4.46-4.debian.tar.xz Checksums-Sha256: 1ebe1ce5b99df7660c98eacad3acc104063afa955bdc37fc18c5bd4ef536538e 3501 apache2_2.4.46-4.dsc c3fb8c74db25010cf663582332eb38f1679a678d7ad40a4ffbd40fe74ce68759 882336 apache2_2.4.46-4.debian.tar.xz Files: 94f9e3e434a762e385b6270609427511 3501 httpd optional apache2_2.4.46-4.dsc b8a574a930140e42d502b9d7da58b04c 882336 httpd optional apache2_2.4.46-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl/8MKQACgkQ9tdMp8mZ 7umDfQ//b/jeUeSd7Q0P5qTyj/xAay8akQ6a0n7LAqAvqMaezikLymDPq8MECtza 8zZSo4WtpjIwlWUVxXYWkWNnosw4saloD/R1HFRLYFsRREwyGfBJPdThB4nAIeCp uqEL6Unh0eWGajTT+Gg9r/uEkB9dtNnA1e5zTLSmH9mtd3E29zfm1k/S+9qClKW4 I8fHvfepylrXcrHFwv6/WQ/bFEitP9d6QYKi6hxEZN2laC8OuVDOqt6JRVP1OSRW 7/3NMSz0PF208eSaM4re1d+hSWuAIWPOmWIHxsJnwoqWXwlO5DwAc4nZkAPAioCF +TgLIRZC2+Ut9ukrlDIJKBxHiVTSoKIH/MdmPn/egqMnhoW4ndbqDbreVGhXtWBE I3dulNZxVJH05BQf97qtIquhYrj8vGj43W8Lu2ctRcDbVrLjfbDyS/EWdSOJD2YE wjsGUEbbAjFZlVzUNc83EKocZyPKtK4f+JBEIJEFoCJ7Ovt+VhikZPND1GGbmgIZ plyPP98U2Ka17TEI9w5CM0uLTcj1K96KiEfKUcz+xzLMzx3pGTD6/WL67XnKeIE8 78qhQ7ybCdYgezALYfh2R2sf31B5s7I8nBXGOqGFkGxnkc4uVjNx0s+nXuhhh15j RKvZ6DyvsvW8i5UXgikEly+jNtoA1dflIaKD4SYhtTLceM2iBgU= =D/xG -END PGP SIGNATURE End Message ---
Bug#962203: NMU
On Mon, 2021-01-11 at 10:12 +0100, A Mennucc1 wrote: > Il 11/01/21 01:28, Paul Wise ha scritto: > > A Mennucc1, would you be interested in having assistance with the > > codebase and the service? > > that's OK for me Excellent! > What is the best debian-ish way to collaborate? I would suggest moving debdelta from your personal salsa account to the debian organisation, and then giving commit access to it for anyone who is not a Debian member and is interested in helping, you could also use salsa merge requests instead. > There are some problems to address (a few urgent): how do we discuss? > mailing list? does `salsa` have a way to open a chat/mailing list for > us to use? You could use debde...@packages.debian.org or a tracker.debian.org team for discussions or even the debian-devel mailing list. For chat I would suggest a new IRC channel on OFTC or using one of the existing ones like #debian-apt, #debian-dpkg or #debian-devel. https://wiki.debian.org/IRC#How_to_create_a_new_.23debian-.2A_channel -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed: pmix/openmpi serious
Processing commands for cont...@bugs.debian.org: > severity 979744 serious Bug #979744 [libpmix2] libpmix2: pmix_psquash_base_select failed during pmix_init Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 979744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971299: [Pkg-privacy-maintainers] Bug#971299: onionshare: Switch to python3-pycryptodome
Hi, On 10/01/2021 23:46, Sebastian Ramacher wrote: > On 2020-10-05 15:18:46 +0200, Clément Hermann wrote: >> >> Hi, >> >> Control: block 971299 with 886291 >> thanks >> >> On 28/09/2020 23:29, Sebastian Ramacher wrote: >>> Source: onionshare >>> Version: 2.2-2 >>> Severity: important >>> Tags: sid bullseye >>> Usertags: pycrypto >>> >>> Dear maintainer, >>> >>> onionshare currently Build-Depends or Depends on python3-crypto from >>> PyCrypto. This project is no longer maintained and PyCryptodome >>> (https://www.pycryptodome.org/en/latest/) provides a drop in >>> replacement. Please switch to python3-pycryptodome. I'd like to >>> remove python-crypto before the release of bullseye. >> >> >> As far as I understand it, pycryptodome *can* be a drop-in replacement >> usually, but not currently in Debian since it doesn't install in Crypto >> but Cryptodomex namespace (#886291). >> >> Are there any plan to change it when python3-crypto is removed or before ? >> >> Of course, we can patch onionshare to import cryptodomex, but that patch >> would be debian-only then… Upstream already expect pycryptodome as >> Crypto module. > > Sorry for the delay. I don't have any plans other than removing > python3-crypto. CCing the pycryptodome maintainer for more input. Thanks. Meanwhile, Ulrike added a patch to import cryptodome explicitly, and I just uploaded the version with it. It's a short-term fix IMO, until #886291 is clarified, but at least it removes the dep to pycrypto. Cheers, -- nodens
Bug#971299: marked as done (onionshare: Switch to python3-pycryptodome)
Your message dated Mon, 11 Jan 2021 11:54:39 + with message-id and subject line Bug#971299: fixed in onionshare 2.2-3 has caused the Debian Bug report #971299, regarding onionshare: Switch to python3-pycryptodome 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.) -- 971299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: onionshare Version: 2.2-2 Severity: important Tags: sid bullseye Usertags: pycrypto Dear maintainer, onionshare currently Build-Depends or Depends on python3-crypto from PyCrypto. This project is no longer maintained and PyCryptodome (https://www.pycryptodome.org/en/latest/) provides a drop in replacement. Please switch to python3-pycryptodome. I'd like to remove python-crypto before the release of bullseye. Cheers --- End Message --- --- Begin Message --- Source: onionshare Source-Version: 2.2-3 Done: Clément Hermann We believe that the bug you reported is fixed in the latest version of onionshare, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Clément Hermann (supplier of updated onionshare package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 11 Jan 2021 12:30:19 CET Source: onionshare Binary: Architecture: source Version: 2.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Privacy Tools Maintainers Changed-By: Clément Hermann Description: Closes: 965055 965152 971299 Changes: onionshare (2.2-3) unstable; urgency=medium . [ Ulrike Uhlig ] * Correct and update manpages. (Closes: #965055) * Document --website option in manpages. (Closes: #965152) * Replace python3-crypto by python3-pycryptodome (Closes: #971299) * Add debian/patches/cryptodome.diff to use the cryptodome namespace. Note that this does not fix the root cause in #886291. . [ Clément Hermann ] * manpage: fix groff warning (missing escape) * d/Copyright: Add missing license info for appstream metadata * d/missing-sources: refresh jquery to 3.4.0 * d/patches/cryptodome.diff: Add DEP-3 headers * d/control: - declare compliance with Debian Policy 4.5.1 (no change) - add myself to uploaders Checksums-Sha256: 5e49b4e44a07ecdbacf79301f503d6d1716bd3e8258bea38e6717bab7da564f6 2254 onionshare_2.2-3.dsc 3cfe3ae2fb64eaa58aee497ad1f32f4123b83da64b676d6ff8597d4ffa1aabf7 78340 onionshare_2.2-3.debian.tar.xz ec4fcd8ee00eb4c1d8855c3482b4afba5b9e3bde73f9b3e2fb86e80714848239 14130 onionshare_2.2-3_sourceonly.buildinfo Checksums-Sha1: b137668733981cbc6776234581c0322dfd133309 2254 onionshare_2.2-3.dsc a97f75dcdad575e50d62d9a0e96f7823d35a2821 78340 onionshare_2.2-3.debian.tar.xz 7860613bbde0c2918731d5f503c683acd26a6ae7 14130 onionshare_2.2-3_sourceonly.buildinfo Files: 58a4147235de4eb7f77a8f9a54f860a9 2254 net optional onionshare_2.2-3.dsc aa9794e0a48a24e6e4dfc85f4c98dc63 78340 net optional onionshare_2.2-3.debian.tar.xz 7b92df43b8e9eca22566c6c5ad89edac 14130 - - onionshare_2.2-3_sourceonly.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEboF7OBIOe73fYj9R2KOaUw8NzMsFAl/8NtkACgkQ2KOaUw8N zMsEHw//cSnbxu2DlLBOxG+SEKMphJt7nntpRi16DtkkIoX9h4z7lo1+ngKQi01+ AHkUaB7Nu6cLiU1oTE0OLU342RTGkAkx7NQNnTJskQXYjQDRWSUrn0kegE5ZF6w5 tBhpTo+5DqbDuKfqbbCtR1dTf2NblQN6iWBfH1qCdHcMl4NYls1IFcPbTXHepT/P gQ9SJ2y1oyqGyijS3GLPV1sRw/b0zXij8W7ChMWKpMOX2TvGAmL/0mAJfJwa9xpr 31J6rvKQMMlDk1DXw6a3N08kdyjUPnhG6Gd+dxpet/9+qF65LTnVj9AydqOZRRuO Nx+fmGBOA/58ODsexKMfI0Qfz1KkOwF+CF1E/o8kfXziWRniEIOTvbmDrtLFvBjD IYU6WPznGv7RLzOQ9r6Ci02JYwGZoTjFkeyf0Yw/VgG/0vskMnPMJjEucafr187y fSQh8kIKKfJBocV7eknbChfQfz9YZerh9yLx/yio6gX8pbysRtdKut83L3SVlHuG zg+5jBPyCNbynRAtuioIGju8YQH4k0EBRpqVL62P+py5C+IpQz1RLY08wZsHkqUB MW0cM7bce8xObKjmxjCeR0VnADqGgPqgYAAnDif0U4/+AvAi8hIRGdhq3ltbKahZ MtpCUNV/Tbm0SnPV2608znx83ZSUkeh14d4mvnHJAm/EVTC9TMg= =iZxs -END PGP SIGNATURE End Message ---
Bug#979590: marked as done (libx11 possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium)
Your message dated Mon, 11 Jan 2021 11:54:20 + with message-id and subject line Bug#979590: fixed in libx11 2:1.7.0-2 has caused the Debian Bug report #979590, regarding libx11 possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium 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.) -- 979590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libx11-xcb1 Version: 2:1.7.0-1 Severity: normal X-Debbugs-Cc: mic...@lebihan.pl Dear Maintainer, After updating libx11-xcb1 chromium and google chrome UI is not responding to any input and clicking anywhere on the app window causes the GNOME app is not responding dialog to appear. The app actually is not frozen because if you pass a URL with dynamic web content as a parameter, it will be constantly updated. I didn't notice any other affected app, but I didn't test much. Michel Le Bihan -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (700, 'testing'), (650, 'unstable'), (600, 'experimental'), (500, 'unstable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information --- End Message --- --- Begin Message --- Source: libx11 Source-Version: 2:1.7.0-2 Done: Julien Cristau We believe that the bug you reported is fixed in the latest version of libx11, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Cristau (supplier of updated libx11 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 11 Jan 2021 12:15:25 +0100 Source: libx11 Architecture: source Version: 2:1.7.0-2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Julien Cristau Closes: 979590 Changes: libx11 (2:1.7.0-2) unstable; urgency=medium . * Set a strict dependency of libx11-xcb1 on libx11-6, as internal ABI may change across releases - and indeed did change between 1.6.12 and 1.7.0 (closes: #979590) * Update upstream git URL in package descriptions. Checksums-Sha1: 9d7689b4f621e72e48cc225a5986b123b5102b98 2564 libx11_1.7.0-2.dsc f0294ed61e0ce05da05d1f7ea3682536e0f5ae96 73844 libx11_1.7.0-2.diff.gz Checksums-Sha256: 1540dcbbbdf7e08405d133127ca6f63fe191a3946ae9c5afc95293bc12f784a1 2564 libx11_1.7.0-2.dsc 910d4a1527458ff020f0bab9df55bab44d63db8247543d2b2256c7b258ce439c 73844 libx11_1.7.0-2.diff.gz Files: e8781a3e2d7accd1f2057d91a5940570 2564 x11 optional libx11_1.7.0-2.dsc f8911845bfd953f82a3ef1ac0697e022 73844 x11 optional libx11_1.7.0-2.diff.gz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAl/8NhYUHGpjcmlzdGF1 QGRlYmlhbi5vcmcACgkQnbAjVVb4z61cYg/5AeB5A0SF/qCS2fCCaADJOla4RJlH HZPna/MmPxIonahyZ3caCuhJ+7etZdq9vAyGLqoy4wLyYWp3Xbq4Htx0TFDxGBHD qA0OTW7QmhrlrIs3b+140UmXaehasc7PD8paAlLzaWkqC6A5de30VCoE/XDzufNo V5qeVh/ouXFGzBtbY0UaOA9nLM1IewzL2bqt48U++QbgYDcLu49rc5JEIdEAzcf2 twe+4BIk0tRTItfxswbu+wdUXam3uzYoUwcH92Q306IBoTT2Ls4cErPaiHmovfsP eWjKU7f8sKKBF7AdkVqd8roBtTEHsa23Je09vdB0JFF7+Dljuj/cmUoDg5JbracU aZIrHrVobVJqwGExof2lIXQe1uuBPcLGGuKXNQuUSXuN6Q/jX3mfxn9flCpiij+K +u1Iu5CFjuwo8dHluHk14ev5yZ/jSTx0WT6bvNQHnr6RYpAt4cat7ST6NJluS8U7 5OlL4AaoVw4nuxW8WzimWk/XtaDwI2/XIK4cdnb41l4MlT4Qt/iwtPyifZX9rvnZ WL3Y6T0ZqRi8o2qSPUVIpIrOcW+JBLL7maKCw1I/oonbs4leFRSV5KxZzWoV9ATy iUM0H0/OHAx/EanyrgGhLhu8bn+W9dXj6vmMXPOpujwxcfv1vQO7BOfLw4Mk78oe 8GNy4TAE57g/XCE= =jAIK -END PGP SIGNATURE End Message ---
Bug#979618: marked as done (libx11 possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium)
Your message dated Mon, 11 Jan 2021 11:54:20 + with message-id and subject line Bug#979590: fixed in libx11 2:1.7.0-2 has caused the Debian Bug report #979590, regarding libx11 possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium 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.) -- 979590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: chromium Version: 87.0.4280.88-0.4 Severity: grave X-Debbugs-Cc: deb...@rocketjump.eu Hi, starting chromium on bullseye will render a window (with various elements shifted down by half a screen), which is impossible to interact with, and causes gnome to offer a "force quit" prompt after a few seconds. Output from the CLI: ->8-->8-->8-->8-->8-->8-->8-->8-->8-->8-->8- $ chromium libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) [9413:9413:0109/060426.733876:ERROR:vaapi_wrapper.cc(541)] vaInitialize failed: unknown libva error [9413:9413:0109/060426.735693:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [9413:9413:0109/060426.855283:ERROR:shared_context_state.cc(74)] Skia shader compilation error Errors: [9413:9413:0109/060426.858413:ERROR:shared_context_state.cc(74)] Skia shader compilation error Errors: [9413:9413:0109/060426.860282:ERROR:shared_context_state.cc(74)] Skia shader compilation error Errors: [9413:9413:0109/060426.867099:ERROR:shared_context_state.cc(74)] Skia shader compilation error Errors: [9413:9413:0109/060426.869489:ERROR:shared_context_state.cc(74)] Skia shader compilation error Errors: [9415:9428:0109/060426.876651:ERROR:nss_util.cc(283)] After loading Root Certs, loaded==false: NSS error code: -8018 [9413:9413:0109/060426.993836:ERROR:shared_context_state.cc(74)] Skia shader compilation error Errors: [9413:9413:0109/060430.833703:ERROR:gl_surface_presentation_helper.cc(259)] GetVSyncParametersIfAvailable() failed for 1 times! [9413:9413:0109/060430.839756:ERROR:gl_surface_presentation_helper.cc(259)] GetVSyncParametersIfAvailable() failed for 2 times! Killed ->8-->8-->8-->8-->8-->8-->8-->8-->8-->8-->8- Various things I've tried: - reverting to chromium(,-common,-sandbox) to 87.0.4280.88-0.3 -> same problem - reverting to chromium(,-common,-sandbox) to 87.0.4280.88-0.3 -> same problem - starting chromium with a fresh profile -> same problem Installing debug symbols and starting `chromium -g` will result in the same errors, except for chromium complaining about being started in single-process mode. One user on #debian-next IRC reported no such errors on sid and KDE, so it might not effect all users. I *think* about a week ago chromium still ran fine (I only use it for debugging purposes). Checking /var/log/apt/history.log, I don't see any libva* packages being updated in that timeframe. Regards, Lee -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_USER, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chromium depends on: ii chromium-common 87.0.4280.88-0.4 ii libasound2 1.2.4-1.1 ii libatk-bridge2.0-0 2.38.0-1 ii libatk1.0-0 2.36.0-2 ii libatomic1 10.2.1-3 ii libatspi2.0-02.38.0-2 ii libavcodec58 7:4.3.1-5 ii libavformat587:4.3.1-5 ii libavutil56 7:4.3.1-5 ii libc62.31-6 ii libcairo21.16.0-5 ii libcups2 2.3.3op1-4 ii libdbus-1-3 1.12.20-1 ii libdrm2 2.4.103-2 ii libevent-2.1-7 2.1.12-stable-1 ii libexpat12.2.10-1 ii libflac8 1.3.3-2 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1 ii libgbm1 20.3.2-1 ii libgcc-s110.2.1-3 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.4-1 ii libgtk-3-0 3.24.24-1 ii
Bug#979621: pandas: autopkgtest regression in testing: No tables found
Control: tags -1 fixed-upstream pending The trigger was a change in the outside world, not Debian testing: the tests (of HTML table parsing) were trying to access a web page that no longer exists. Fixed in Salsa.
Processed: racon FTBFS WIP
Processing commands for cont...@bugs.debian.org: > forwarded 979727 https://github.com/lbcb-sci/racon/pull/48 Bug #979727 [src:racon] racon: FTBFS: fatal error: bioparser/bioparser.hpp: No such file or directory Set Bug forwarded-to-address to 'https://github.com/lbcb-sci/racon/pull/48'. > End of message, stopping processing here. Please contact me if you need assistance. -- 979727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: [pkg-php-pear] Bug#979156: Useless in Debian
Processing control commands: > severity -1 serious Bug #979156 [php-net-idna2] Useless in Debian Severity set to 'serious' from 'important' -- 979156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979338: marked as done (python3-scapy: hardcodes tcpdump location to /usr/sbin/tcpdump)
Your message dated Mon, 11 Jan 2021 13:13:43 +0100 with message-id and subject line Fixed in 2.4.4-4 has caused the Debian Bug report #979338, regarding python3-scapy: hardcodes tcpdump location to /usr/sbin/tcpdump 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.) -- 979338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-scapy Version: 2.4.4-3 Severity: normal In tcpdump 4.99.0-1, the location of the tcpdump binary was changed from /usr/sbin/tcpdump to /usr/bin/tcpdump. This causes autopkgtest to fail for scapy, as the path is hardcoded to the old location via this patch: https://salsa.debian.org/pkg-security-team/scapy/-/raw/debian/master/debian/patches/use-absolute-paths.patch Simply removing the patch will allow the test suite to pass again, however you may consider versioning the dependency on tcpdump in the autopkgtest control file to ensure that the location will match the tcpdump version. Note that the location change may also impact operation of Scapy itself, in which case the severity of this bug would likely be higher than 'normal'. I have not tested this. Thanks. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-scapy depends on: ii libjs-sphinxdoc 3.4.1-1 ii python3 3.9.1-1 ii sphinx-rtd-theme-common 0.5.0+dfsg-1 Versions of packages python3-scapy recommends: ii ipython3 7.19.0-3 pn python3-cryptography ii tcpdump 4.99.0-1 Versions of packages python3-scapy suggests: pn graphviz pn python3-matplotlib pn python3-pyx pn sox pn tcpreplay pn wireshark -- no debconf information --- End Message --- --- Begin Message --- Version: 2.4.4-4 This has been fixed in the last upload. Date: Mon, 11 Jan 2021 11:40:10 +0100 Source: scapy Architecture: source Version: 2.4.4-4 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Raphaël Hertzog Changes: scapy (2.4.4-4) unstable; urgency=medium . * Team upload. . [ Romain Francoise ] * Drop debian/patches/use-absolute-paths.patch (#979338) * debian/tests/control: version dependency on tcpdump * Cherry-pick upstream commit 42d58d8729 to fix pipetool test (and thus fix autopkgtest too) -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄ Debian Long Term Support: https://deb.li/LTS--- End Message ---
Bug#979618: Bug#979590: fixed in libx11 2:1.7.0-2
I can confirm that upgrading libx11-6 to match libx11-xcb1 fixed my issue with chromium. Thanks!
Bug#979758: marked as done (xxhash: broken pkgconfig file)
Your message dated Mon, 11 Jan 2021 13:26:31 +
with message-id
and subject line Bug#979758: fixed in xxhash 0.8.0-2
has caused the Debian Bug report #979758,
regarding xxhash: broken pkgconfig file
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.)
--
979758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979758
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xxhash
Version: 0.8.0-1
Severity: serious
tags: patch
Hello, after trying hard to see why python3-pkgconfig was not detecting xxhash
I discovered that the Version field was empty
https://github.com/Cyan4973/xxHash/commit/b4dbf5fefc37b8a5f80b3bbc6b8ff639cf5f0ec2
This trivial commit fixes it.
To reproduce:
python3
>>> import pkgconfig
>>> pkgconfig.installed('libxxhash', '>= 0.7.3')
True
This is what is expected
G.
--- End Message ---
--- Begin Message ---
Source: xxhash
Source-Version: 0.8.0-2
Done: Norbert Preining
We believe that the bug you reported is fixed in the latest version of
xxhash, 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 979...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Norbert Preining (supplier of updated xxhash package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 11 Jan 2021 21:57:57 +0900
Source: xxhash
Architecture: source
Version: 0.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Norbert Preining
Changed-By: Norbert Preining
Closes: 977345 979758
Changes:
xxhash (0.8.0-2) unstable; urgency=medium
.
* Use hardware-accelerated XXH3 computation on x86 architecture, and
install the hardware-accelerating header file.
Thanks to Julian Andres Klode. (Closes: #977345)
* Cherry-pick upstream: Fix empty version in .pc file (Closes: #979758)
Checksums-Sha1:
4f344cf5cdbee4879cdf575f15e03e09d4124503 1601 xxhash_0.8.0-2.dsc
ad48ecf4f560d2913e98dd7f799a820843d6882a 4160 xxhash_0.8.0-2.debian.tar.xz
f9a7fd3fcc10cedbad7703161107e95641ccd38e 6152 xxhash_0.8.0-2_source.buildinfo
Checksums-Sha256:
91c696b5371558ebb12c323b0bd4e15eece0a439ef49c6aa5a6d0c1cf6c7762a 1601
xxhash_0.8.0-2.dsc
5c427c2c08019a945412afac02326a24c72b65a83bff59447009db303233aecd 4160
xxhash_0.8.0-2.debian.tar.xz
575014ec3f2637463ecc71370bbd9261c7989bfa23ed20f0fbeef5089397a459 6152
xxhash_0.8.0-2_source.buildinfo
Files:
6f399f537b336850d0593ecbc8d040a3 1601 utils optional xxhash_0.8.0-2.dsc
1558d7b4f99c39a3e94e6a760dc4368a 4160 utils optional
xxhash_0.8.0-2.debian.tar.xz
4a618b27e449c58e301d4469d79f3d54 6152 utils optional
xxhash_0.8.0-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQEzBAEBCgAdFiEE68ws0vrA2voQX53I2A4JsIcUAGYFAl/8TCsACgkQ2A4JsIcU
AGbYNQf/Z/0F5l+vS6WoIPN92eBLECBcSf+U4N2qBqdpiRWkgaAbWMEgj3DfsJS0
/M1nBOUhl/OdvXjwFQ7bZkY9TL1MVzqzlZ0Dx201IpdkEWLpg6N++TgHx8UrgM+s
jgPlu//pUvQlBkgfeK1IAx2uYJn09yKX+FYeYseex5X1wcLbNJDvs6l1TKGBBXQq
5JomyX92B3CnkfKG8s8mt4kMuO0s3zQ2kHvXwSjX02f0+yylg35ZaBVCRa4KqchQ
XLSTXh6kRxTaIiHUpyrnLv6FcHxczacqZGDXfYkuGCCmWVgQRMSmRSHrWDdpF0TW
uQVrj8NjC99V8EMRuesAiYxk+fzOaQ==
=2FLG
-END PGP SIGNATURE End Message ---
Bug#979815: libmeep23: missing Conflicts: libmeep22
Package: libmeep23 Version: 1.17.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libmeep23_1.17.0-2_amd64.deb ... Unpacking libmeep23 (1.17.0-2) ... dpkg: error processing archive /var/cache/apt/archives/libmeep23_1.17.0-2_amd64.deb (--unpack): trying to overwrite '/usr/share/meep/casimir.scm', which is also in package libmeep22 1.16.1-2 Errors were encountered while processing: /var/cache/apt/archives/libmeep23_1.17.0-2_amd64.deb cheers, Andreas libmeep22=1.16.1-2_libmeep23=1.17.0-2.log.gz Description: application/gzip
Bug#957601: marked as done (netsniff-ng: ftbfs with GCC-10)
Your message dated Mon, 11 Jan 2021 13:49:22 + with message-id and subject line Bug#957601: fixed in netsniff-ng 0.6.8-1 has caused the Debian Bug report #957601, regarding netsniff-ng: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:netsniff-ng Version: 0.6.5-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/netsniff-ng_0.6.5-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] /usr/bin/ld: mausezahn/tools.o:(.bss+0x6e6c0): multiple definition of `simulate'; mausezahn/automops.o:(.bss+0x6e6c0): first defined here /usr/bin/ld: mausezahn/tools.o:(.bss+0x6e6c4): multiple definition of `verbose'; mausezahn/automops.o:(.bss+0x6e6c4): first defined here /usr/bin/ld: mausezahn/tools.o:(.bss+0x6e6c8): multiple definition of `quiet'; mausezahn/automops.o:(.bss+0x6e6c8): first defined here /usr/bin/ld: mausezahn/tools.o:(.bss+0x6e6cc): multiple definition of `ipv6_mode'; mausezahn/automops.o:(.bss+0x6e6cc): first defined here /usr/bin/ld: mausezahn/tools.o:(.bss+0x6e6d0): multiple definition of `mode'; mausezahn/automops.o:(.bss+0x6e6d0): first defined here /usr/bin/ld: mausezahn/tools.o:(.bss+0x6e6d4): multiple definition of `device_list_entries'; mausezahn/automops.o:(.bss+0x6e6d4): first defined here /usr/bin/ld: mausezahn/tools.o:(.bss+0x6e6e0): multiple definition of `device_list'; mausezahn/automops.o:(.bss+0x6e6e0): first defined here /usr/bin/ld: mausezahn/tools.o:(.bss+0x6ef20): multiple definition of `MZ_SIZE_LONG_INT'; mausezahn/automops.o:(.bss+0x6ef20): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x6e790): multiple definition of `mode'; mausezahn/automops.o:(.bss+0x6e6d0): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x60e0): multiple definition of `tx'; mausezahn/automops.o:(.bss+0x6020): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x6e788): multiple definition of `quiet'; mausezahn/automops.o:(.bss+0x6e6c8): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x6e538): multiple definition of `mz_stop'; mausezahn/automops.o:(.bss+0x6e478): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x6e540): multiple definition of `mz_start'; mausezahn/automops.o:(.bss+0x6e480): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x6e550): multiple definition of `total_d'; mausezahn/automops.o:(.bss+0x6e490): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x0): multiple definition of `cli_debug'; mausezahn/cdp.o:(.bss+0x0): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x4): multiple definition of `clidev'; mausezahn/cdp.o:(.bss+0x4): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x8): multiple definition of `clipkt'; mausezahn/cdp.o:(.bss+0x8): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x10): multiple definition of `mz_port'; mausezahn/cdp.o:(.bss+0x10): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x20): multiple definition of `mz_listen_addr'; mausezahn/cdp.o:(.bss+0x20): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x40): multiple definition of `mz_enable'; mausezahn/cdp.o:(.bss+0x40): first defined here /usr/bin/ld: mausezahn/tx_switch.o:(.bss+0x60): multiple definition of `mz_password'; mausezahn/cdp.o:(.bss+0x60): first defined here /usr/bin/ld: m
Bug#979817: lld: missing Breaks+Replaces: llvm (= 1:11.0-51+nmu1)
Package: lld Version: 1:11.0-51+nmu2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../lld_1%3a11.0-51+nmu2_amd64.deb ... Unpacking lld (1:11.0-51+nmu2) ... dpkg: error processing archive /var/cache/apt/archives/lld_1%3a11.0-51+nmu2_amd64.deb (--unpack): trying to overwrite '/usr/bin/wasm-ld', which is also in package llvm 1:11.0-51+nmu1 Errors were encountered while processing: /var/cache/apt/archives/lld_1%3a11.0-51+nmu2_amd64.deb The existing Replaces: llvm (= 0.51+nmu1) Breaks: llvm (= 0.51+nmu1) are versioned after the source version, not the binary version of the llvm binary package. cheers, Andreas llvm=1:11.0-51+nmu1_lld=1:11.0-51+nmu2.log.gz Description: application/gzip
Bug#969597: libzstd: Please correct version in symbol file
Hi Andreas, On 1/7/21 4:51 PM, Andreas Tille wrote: Hi Alex, did you possibly by chance forgot to close #969597 in your latest upload of libzstd 1.4.8+dfsg-1 ? Kind regards Andreas. No, I didn't correct this specific issue. Just added the new symbols from the new release. However a patch or a list of "all" symbols is very welcome. Best regards, Alex
Bug#979817: lld: missing Breaks+Replaces: llvm (= 1:11.0-51+nmu1)
+jonas Le 11/01/2021 à 14:52, Andreas Beckmann a écrit : Package: lld Version: 1:11.0-51+nmu2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces From the attached log (scroll to the bottom...): Preparing to unpack .../lld_1%3a11.0-51+nmu2_amd64.deb ... Unpacking lld (1:11.0-51+nmu2) ... dpkg: error processing archive /var/cache/apt/archives/lld_1%3a11.0-51+nmu2_amd64.deb (--unpack): trying to overwrite '/usr/bin/wasm-ld', which is also in package llvm 1:11.0-51+nmu1 Errors were encountered while processing: /var/cache/apt/archives/lld_1%3a11.0-51+nmu2_amd64.deb The existing Replaces: llvm (= 0.51+nmu1) Breaks: llvm (= 0.51+nmu1) are versioned after the source version, not the binary version of the llvm binary package.
Bug#979443: chromium: desktop GUI locks up as Xorg process goes to 100%
After three full days of use, the desktop has not frozen again, and the Xorg process has remained below 7% CPU use. Should I modify the menu to include the alternate launch command, or is there a beta version of chromium you would like me to try? Steve Steve A. wrote on 1/8/21 6:32 AM: Thanks, Jan. I killed chromium, upgraded to 87* again, and re-launched with the recommended command last night. The user is back on this morning and I'm monitoring from another machine. Steve Jan Luca Naumann wrote on 1/7/21 2:30 AM: Dear Steve, with the upgrade to 87.* we included the ANGLE library which manages the OpenGL access of chromium. Maybe this is the cause of your problem. Could you try to launch "$ chromium --use-gl=desktop"? This should disable the usage of ANGLE. Best, Jan
Bug#975789: marked as done (golang-github-xenolf-lego: FTBFS: src/github.com/go-acme/lego/providers/dns/inwx/inwx.go:85:6: assignment mismatch: 1 variable but d.client.Account.Login returns 2 values)
Your message dated Mon, 11 Jan 2021 14:36:35 +
with message-id
and subject line Bug#975789: fixed in golang-github-xenolf-lego 3.2.0-3
has caused the Debian Bug report #975789,
regarding golang-github-xenolf-lego: FTBFS:
src/github.com/go-acme/lego/providers/dns/inwx/inwx.go:85:6: assignment
mismatch: 1 variable but d.client.Account.Login returns 2 values
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.)
--
975789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-xenolf-lego
Version: 3.2.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201125 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure
> set -e -x ;\
> cd _build/src/github.com/go-acme/lego && \
> for P in acmedns alidns auroradns azure bindman cloudflare designate
> dnsimple dnspod exoscale fastdns iij linode linodev4 liquidweb namedotcom
> namesilo ns1 oraclecloud sakuracloud transip vegadns ; do \
> perl -ni -E "print unless m{\b$P\b}"
> providers/dns/dns_providers.go ;\
> rm -rf providers/dns/$P ;\
> done
> + cd _build/src/github.com/go-acme/lego
> + perl -ni -E print unless m{\bacmedns\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/acmedns
> + perl -ni -E print unless m{\balidns\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/alidns
> + perl -ni -E print unless m{\bauroradns\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/auroradns
> + perl -ni -E print unless m{\bazure\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/azure
> + perl -ni -E print unless m{\bbindman\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/bindman
> + perl -ni -E print unless m{\bcloudflare\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/cloudflare
> + perl -ni -E print unless m{\bdesignate\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/designate
> + perl -ni -E print unless m{\bdnsimple\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/dnsimple
> + perl -ni -E print unless m{\bdnspod\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/dnspod
> + perl -ni -E print unless m{\bexoscale\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/exoscale
> + perl -ni -E print unless m{\bfastdns\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/fastdns
> + perl -ni -E print unless m{\biij\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/iij
> + perl -ni -E print unless m{\blinode\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/linode
> + perl -ni -E print unless m{\blinodev4\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/linodev4
> + perl -ni -E print unless m{\bliquidweb\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/liquidweb
> + perl -ni -E print unless m{\bnamedotcom\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/namedotcom
> + perl -ni -E print unless m{\bnamesilo\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/namesilo
> + perl -ni -E print unless m{\bns1\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/ns1
> + perl -ni -E print unless m{\boraclecloud\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/oraclecloud
> + perl -ni -E print unless m{\bsakuracloud\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/sakuracloud
> + perl -ni -E print unless m{\btransip\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/transip
> + perl -ni -E print unless m{\bvegadns\b} providers/dns/dns_providers.go
> + rm -rf providers/dns/vegadns
> make[1]: Leaving directory '/<>'
>dh_auto_build -O--buildsystem=golang -O--builddirectory=_build
> cd _build && go generate -v github.com/go-acme/lego/acme
> github.com/go-acme/lego/acme/api
> github.com/go-acme/lego/acme/api/internal/nonces
> github.com/go-acme/lego/acme/api/internal/secure
> github.com/go-acme/lego/acme/api/internal/sender
> github.com/go-acme/lego/certcrypto github.com/go-acme/lego/certificate
> github.com/go-acme/lego/challenge github.com/go-acme/lego/challenge/dns01
> github.com/go-acme/lego/challenge/http01
> github.com/go-acme/lego/challenge/resolver
> github.com/go-acme/lego/challenge/tlsalpn01 github.com/go-acme/lego/cmd
> github.com/go-acme/lego/cmd/lego github.com/go-acme/lego/internal
> github.com/go-acme/lego/lego github.com/go-acme/lego/log
> github.com/go-acme/lego/platfor
Bug#979640: src:adv-17v35x: invalid maintainer address
On Sun, 10 Jan 2021 14:11:36 +0300 Alexander Gerasiov wrote: > Yep, Andrey has retired from the project where he worked with the > hardware. (So did I.) So he definitely is not interested in packaging > this driver anymore. > > > I thinks the package could be orphaned. Let's wait for Andrey's response. I did indeed retire from the project. Please mark the package as orphaned (unless, of course, there's an interested person willing to maintain it). -- Andrey Drobyshev
Bug#979817: llvm-defaults: diff for NMU version 0.51+nmu3
Control: tags 979817 + patch
Control: tags 979817 + pending
Dear maintainer,
I've prepared an NMU for llvm-defaults (versioned as 0.51+nmu3) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru llvm-defaults-0.51+nmu2/debian/changelog
llvm-defaults-0.51+nmu3/debian/changelog
--- llvm-defaults-0.51+nmu2/debian/changelog2021-01-09 18:25:49.0
+0100
+++ llvm-defaults-0.51+nmu3/debian/changelog2021-01-11 15:49:22.0
+0100
@@ -1,3 +1,13 @@
+llvm-defaults (0.51+nmu3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ * add note documenting need for Breaks+Replaces
+ * fix relax breaks+replaces;
+closes: bug#979817, thanks to Andreas Beckmann and Sylvestre Ledru
+
+ -- Jonas Smedegaard Mon, 11 Jan 2021 15:49:22 +0100
+
llvm-defaults (0.51+nmu2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru llvm-defaults-0.51+nmu2/debian/control
llvm-defaults-0.51+nmu3/debian/control
--- llvm-defaults-0.51+nmu2/debian/control 2021-01-09 18:22:52.0
+0100
+++ llvm-defaults-0.51+nmu3/debian/control 2021-01-11 15:48:18.0
+0100
@@ -212,8 +212,10 @@
Architecture: any
Depends: lld-${pv:llvm} ${reqv:llvm}, ${misc:Depends}
Pre-Depends: ${misc:Pre-Depends}
-Replaces: llvm (= 0.51+nmu1)
-Breaks: llvm (= 0.51+nmu1)
+# TODO: drop when 0.51+nmu1 with broken symlink is in no Debian suite
+# (see release 0.51+nmu2)
+Replaces: llvm (<< 0.51+nmu2)
+Breaks: llvm (<< 0.51+nmu2)
Description: LLVM-based linker
LLD is a new, high-performance linker. It is built as a set of reusable
components which highly leverage existing libraries in the larger LLVM
diff -Nru llvm-defaults-0.51+nmu2/debian/TODO
llvm-defaults-0.51+nmu3/debian/TODO
--- llvm-defaults-0.51+nmu2/debian/TODO 1970-01-01 01:00:00.0 +0100
+++ llvm-defaults-0.51+nmu3/debian/TODO 2021-01-09 19:13:35.0 +0100
@@ -0,0 +1,3 @@
+ * stop lld break+Replace llvm
+when 0.51+nmu1 with broken symlink has gone from all Debian suites
+(see release 0.51+nmu2)
Processed: llvm-defaults: diff for NMU version 0.51+nmu3
Processing control commands: > tags 979817 + patch Bug #979817 [lld] lld: missing Breaks+Replaces: llvm (= 1:11.0-51+nmu1) Added tag(s) patch. > tags 979817 + pending Bug #979817 [lld] lld: missing Breaks+Replaces: llvm (= 1:11.0-51+nmu1) Added tag(s) pending. -- 979817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: limit source to llvm-defaults, tagging 979817
Processing commands for cont...@bugs.debian.org: > limit source llvm-defaults Limiting to bugs with field 'source' containing at least one of 'llvm-defaults' Limit currently set to 'source':'llvm-defaults' > tags 979817 + pending Bug #979817 [lld] lld: missing Breaks+Replaces: llvm (= 1:11.0-51+nmu1) Ignoring request to alter tags of bug #979817 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 979817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > fixed 979443 87.0.4280.141-0.1 Bug #979443 [chromium] chromium: desktop GUI locks up as Xorg process goes to 100% Marked as fixed in versions chromium/87.0.4280.141-0.1. > End of message, stopping processing here. Please contact me if you need assistance. -- 979443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979818: python-dlt: FTBFS in sid
Source: python-dlt Version: 2.0-2 Severity: serious Hello, looks like python-dlt is compatible only with one single dlt-daemon release, and breaks also with minor updates, because it relies on c structures not being stable in dlt-daemon. I don't think this is currently suitable for stable, because it breaks too often, and its currently broken because I updated dlt-daemon yesterday. there is already an upstream issue asking to make it compatible. G.
Bug#979734: marked as done (calibre: remove python3-crypto from (Build-)Depends)
Your message dated Mon, 11 Jan 2021 15:48:30 + with message-id and subject line Bug#979734: fixed in calibre 5.9.0+dfsg-2 has caused the Debian Bug report #979734, regarding calibre: remove python3-crypto from (Build-)Depends 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.) -- 979734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: calibre Version: 5.8.1+dfsg+fontFix-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org Control: block 972184 by -1 Control: block 979318 by -1 We will remove python3-crypto from bullseye. It is unmaintained and a replacement is available via python3-pycryptodome. calibre only uses any module from python3-crypto in src/calibre/test_build.py to check if is installed. No other code in calibre uses python3-crypto. So I recommend to simply remove this check and drop the dependencies. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: calibre Source-Version: 5.9.0+dfsg-2 Done: YOKOTA Hiroshi We believe that the bug you reported is fixed in the latest version of calibre, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. YOKOTA Hiroshi (supplier of updated calibre package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Jan 2021 00:04:05 +0900 Source: calibre Architecture: source Version: 5.9.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Calibre maintainer team Changed-By: YOKOTA Hiroshi Closes: 979734 Changes: calibre (5.9.0+dfsg-2) unstable; urgency=medium . [ Norbert Preining ] * Remove dependency on python3-crypto (Closes: #979734) remove the one trivial crypto loading test from src/calibre/test_build.py . [ YOKOTA Hiroshi ] * Update patch queue Checksums-Sha1: 4faf39e9c794573a3ab5095a7b08509177bd94e9 3325 calibre_5.9.0+dfsg-2.dsc aeb9dfdb8c3876554c3b6a1c2eaa405a872e30c0 4411416 calibre_5.9.0+dfsg-2.debian.tar.xz 755da680b6a61672c4f73653564eefdcf1747733 19749 calibre_5.9.0+dfsg-2_source.buildinfo Checksums-Sha256: 0b347a72424472d722e2c714533e1bf6035450d7d53917a72cf927c331477617 3325 calibre_5.9.0+dfsg-2.dsc dbc1dae3ff3567656dd8a1ac50bb8b1536fbc8fd33bd7c6c1ac6dcac4e32ba82 4411416 calibre_5.9.0+dfsg-2.debian.tar.xz 0c556defeed7061518088ebeed1f1154d85b10e1fc3920ff37a31f20739713b3 19749 calibre_5.9.0+dfsg-2_source.buildinfo Files: 6ea681f8b594781bb5b28c1caa731165 3325 text optional calibre_5.9.0+dfsg-2.dsc 700f193f435f96bad07ca50e9e1a4921 4411416 text optional calibre_5.9.0+dfsg-2.debian.tar.xz a4fd1b29ae47e5bc8532efed5439bd7a 19749 text optional calibre_5.9.0+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEErjlfKHqxT11VFyPEqem2T5LebcoFAl/8cJ4WHHlva290YS5o Z21sQGdtYWlsLmNvbQAKCRCp6bZPkt5tyoPbEACvn0003KwlVZE/9uVXDN5T2IPi GgaIIES0nEUj1jvyrxaC6LJ8VuQkTTzJu9WmVFJNFLOX3EeVQ3MBT+RolLrzFX0S sT3VfS/ROmoYwdgA0iltOY+d1SbFgfXwfuZ9KigtCUAxhKgEKAaJQJLvmC8YbduD VMCnmiUy1UabSrYhtHtdTDn+VPN01sD69nIHEDvufjnODKgAo/0ZIlZ2FV37iguh ikrj7+v4hayEKf3RE41cQfVm0zYYtVUup3O/SaM4UT1PUYmseFFuptkNl+nB/32k /KKiLWrOjN55G17LmSAii5JZoSNMyams+XPHc2UdbZT/n+vjg8bfKw/OQ2JIAOCv bcSaOkqW4r8rsS90w86F+mr4e5G+P8eWhK6+bvM2KvuzKpmxUaMnG8E+pm9QfCPm sTNDo+5VKppYTa5wj14qcV/W8EGFWBIXulyNMqmSkbw7JoJPosPouFO/MBNXHTbf I7/R+eM7RbZfXPzcSgnSzpMCDj9u1LSsL+xIVj8LXuGZNFw9M10CYx2fGol2t2t+ Z5BJaM3JNVFTSkChfcM0Uqi4AFXejcMG2J/ygW7qGhNX05l3Q08gOEqntA765jLT /ULsttEKWo8uG7biUfT2wrNSSxViN6FtqJwDmyr+pG83R3nNAqHBZNUv7N9W4Spx 2Fcr2CJqx1wSgdUbnA== =70cm -END PGP SIGNATURE End Message ---
Bug#979563: gitlab: my instance work great after upgrade to 13.5.6.1!
On 2021, ജനുവരി 11 7:00:11 PM IST, Dragos Jarca wrote: >Package: gitlab >Followup-For: Bug #979563 > >Dear Maintainer, > >My instance work great after upgrade to 13.5.6.1! > >I can see the content of folder and files on UI. >I can fetch, push, etc. >I added versions off packages if I use, maby will help you. >If you want to give you more info, tell me. Thanks for the feedback. I can see gitaly is still 13.4.6 so the bug is in gitaly. - >Versions of packages gitlab recommends: >ii certbot 1.10.1-1 >ii gitaly 13.4.6+dfsg1-2 So I suggest you hold gitaly on this version. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#979765: linux-image-5.10.0-1-amd64: Kernel panic on boot on my Via VX900
Package: src:linux Version: 5.10.5-1 Severity: critical Justification: breaks the whole system Dear Maintainer, * What led up to the situation? Kernel update from buster's 4.19 to backports or using bullseye/sid 5.9 and 5.10 * What exactly did you do (or not do) that was effective (or ineffective)? The whole system is updated to bullseye, but I kept 4.19 kernel which works. Another solution was to use third-party kernel repository from liquorix.net - their kernels (5.9 and 5.10) work without problems. * What was the outcome of this action? System works on 5.10 liquorix kernel. * What outcome did you expect instead? I would like to stick to bullseye's linux-image-amd64 -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Hewlett-Packard product_name: HP t5550 Thin Client product_version: chassis_vendor: Hewlett-Packard chassis_version: bios_vendor: American Megatrends Inc. bios_version: 786R9 v1.05 board_vendor: Hewlett-Packard board_name: 158Ch board_version: ** PCI devices: 00:00.0 Host bridge [0600]: VIA Technologies, Inc. VX900 Host Bridge: Host Control [1106:0410] (rev 80) Subsystem: VIA Technologies, Inc. VX900 Host Bridge: Host Control [1106:0410] 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- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: viafb Kernel modules: viafb 00:01.1 Audio device [0403]: VIA Technologies, Inc. Device [1106:9170] Subsystem: VIA Technologies, Inc. Device [1106:9170] 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: snd_hda_intel Kernel modules: snd_hda_intel 00:03.0 PCI bridge [0604]: VIA Technologies, Inc. VX900 PCI Express Root Port 0 [1106:a410] (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- Capabilities: Kernel driver in use: pcieport 00:03.1 PCI bridge [0604]: VIA Technologies, Inc. VX900 PCI Express Root Port 1 [1106:b410] (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- Capabilities: Kernel driver in use: pcieport 00:03.2 PCI bridge [0604]: VIA Technologies, Inc. VX900 PCI Express Root Port 2 [1106:c410] (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- Capabilities: Kernel driver in use: pcieport 00:03.3 PCI bridge [0604]: VIA Technologies, Inc. VX900 PCI Express Root Port 3 [1106:d410] (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- Capabilities: Kernel driver in use: pcieport 00:03.4 Host bridge [0600]: VIA Technologies, Inc. VX900 PCI Express Physical Layer Electrical Sub-block [1106:e410] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Kernel driver in use: pata_via Kernel modules: pata_via, pata_acpi, ata_generic 00:10.0 USB controller [0c03]: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller [1106:3038] (rev a0) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller [1106:3038] 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: uhci_hcd Kernel modules: uhci_hcd 00:10.1 USB controller [0c03]: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller [1106:3038] (rev a0) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. VT82xx/62xx UHC
Bug#972306: marked as done (analitza: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath)
Your message dated Mon, 11 Jan 2021 16:03:21 + with message-id and subject line Bug#972306: fixed in analitza 4:20.12.0-2 has caused the Debian Bug report #972306, regarding analitza: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath 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.) -- 972306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972306 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: analitza Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: fixfilepath ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org When the reproducible=+fixfilepath feature is enabled (either through DEB_BUILD_OPTIONS, or using a dpkg that enables this by default), analitza fails to build from source: http://qa-logs.debian.net/2020/09/26.fixfilepath/analitza_20.08.0-1_unstable_fixfilepath.log While the "fixfilepath" feature is not currently enabled by dpkg-buildflags by default, it may become the default at some point in the future, and can by triggered manually by setting DEB_BUILD_OPTIONS=reproducible=+fixfilepath in the build environment. It is also used in the tests.reproducible-builds.org infrastructure when testing unstable and experimental. More information about this issue is available at: https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html I have not identified the exact cause of this issue, but a common trigger is test suites expecting __FILE__ to resolve to an absolute path. The attached patch works around this issue by disabling the fixfilepath feature in debian/rules using DEB_BUILD_MAINT_OPTIONS=-fixfilepath. Thanks for maintaining analitza! live well, vagrant From 42f35de749a9eaf462a85eff7d26aa2150054a49 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Fri, 16 Oct 2020 00:08:52 + Subject: [PATCH] debian/rules: Disable fixfilepath feature, as it triggers build failures when enabled. https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html --- debian/rules | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index 38d755d..377deae 100755 --- a/debian/rules +++ b/debian/rules @@ -3,7 +3,8 @@ #export DH_VERBOSE = 1 # see FEATURE AREAS in dpkg-buildflags(1) -export DEB_BUILD_MAINT_OPTIONS = hardening=+all +# Disable fixfilepath as it triggers build failures. +export DEB_BUILD_MAINT_OPTIONS = hardening=+all reproducible=-fixfilepath # see ENVIRONMENT in dpkg-buildflags(1) # package maintainers to append CFLAGS -- 2.28.0 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: analitza Source-Version: 4:20.12.0-2 Done: Aurélien COUDERC We believe that the bug you reported is fixed in the latest version of analitza, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurélien COUDERC (supplier of updated analitza package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 11 Jan 2021 16:43:53 +0100 Source: analitza Architecture: source Version: 4:20.12.0-2 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Aurélien COUDERC Closes: 972306 Changes: analitza (4:20.12.0-2) unstable; urgency=medium . [ Vagrant Cascadian ] * Disable fixfilepath reproducibility feature, as it triggers build failures when enabled. (Closes: #972306) Checksums-Sha1: 64873eb84cb9336377eec7ff43746a8d3adb3559 2968 analitza_20.12.0-2.dsc 9ba7a7d1b993ebfa521da34b17b02296776f3ec6 8968 analitza_20.12.0-2.debian.tar.xz 951477a6ace835cd25caf7cbacaaafec68acb582 16264 analitza_20.12.0-2_amd64.buildinfo Checksums-Sha256: 08a83ee8bc191c6178c93d4b5f30bba724446a7340d747079e8b000f2463c837 2968 analitza_20.12.0-2.dsc 8688c0bfd984c867b44a8e61bec8754d5b724b7f3bcb5742fb46e81b72874803 8968 analitza_20.12.0-2.debian.tar.xz d404c01f2c474313b65085f07ec17e2354e8cdb71631bd27acab44e3e39ae32a 16264 analitza_20.12.0-2_amd64.buildinfo Files: 26fb84f08d01ca5ce
Bug#972306: analitza: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath
Dear Vagrant, On Thu, 15 Oct 2020 17:10:39 -0700 Vagrant Cascadian wrote: > Package: analitza > Severity: normal > Tags: patch > User: reproducible-bui...@lists.alioth.debian.org > Usertags: fixfilepath ftbfs > X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org > > When the reproducible=+fixfilepath feature is enabled (either through > DEB_BUILD_OPTIONS, or using a dpkg that enables this by default), > analitza fails to build from source: […] > I have not identified the exact cause of this issue, but a common > trigger is test suites expecting __FILE__ to resolve to an absolute > path. The topic has now been discussed in more details on d-devel and elsewhere and is due to the fact that some build-time tests use the QTESTDATA Qt macro which relies on __FILE__ expanding to the full path of the source file where it’s used. > The attached patch works around this issue by disabling the fixfilepath > feature in debian/rules using DEB_BUILD_MAINT_OPTIONS=-fixfilepath. We (the maintainers)’d prefer that kind of change be discussed and resolved upstream instead of having to revert it in every package that fails, but, oh well… Thanks for the patch. Applied and uploaded. Happy hacking ! -- Aurélien
Bug#978390: marked as pending in node-rollup-plugin-typescript
Control: tag -1 pending Hello, Bug #978390 in node-rollup-plugin-typescript 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/js-team/node-rollup-plugin-typescript/-/commit/98cd5110adaa35bade37af0939c2db3977142bc8 Fix regression due to typescript ≥ 4.1 Closes: #978390 (this message was generated automatically) -- Greetings https://bugs.debian.org/978390
Processed: Bug#978390 marked as pending in node-rollup-plugin-typescript
Processing control commands: > tag -1 pending Bug #978390 [src:node-rollup-plugin-typescript] node-rollup-plugin-typescript: FTBFS: src/index.ts(69,54): error TS2345: Argument of type 'NormalizedOutputOptions' is not assignable to parameter of type 'OutputOptions'. Added tag(s) pending. -- 978390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972134: chromium: please, consider moving the package to team-maintenance to properly maintain it
Hello, Thank you for granting me access to the Salsa group. Can I push all my commits to the chromium repo? Will you review my commits and check if everything is OK and I didn't miss anything important or made any mayor mistakes? The window for getting in Bullseye will close soon and this issue is blocking. Will you be able to maintain Chromium in Bullseye? I can help with it if needed. Michel Le Bihan
Bug#979443: chromium: desktop GUI locks up as Xorg process goes to 100%
Michel and I just prepared an security update for unstable and buster-security which changes the default to "desktop". This should be soon in the archive. Best, Jan Am 11.01.21 um 15:14 schrieb Steve A.: > After three full days of use, the desktop has not frozen again, and the > Xorg process has remained below 7% CPU use. Should I modify the menu to > include the alternate launch command, or is there a beta version of > chromium you would like me to try? > > Steve > > > Steve A. wrote on 1/8/21 6:32 AM: >> Thanks, Jan. I killed chromium, upgraded to 87* again, and >> re-launched with the recommended command last night. The user is back >> on this morning and I'm monitoring from another machine. >> >> Steve >> >> >> Jan Luca Naumann wrote on 1/7/21 2:30 AM: >>> Dear Steve, >>> >>> with the upgrade to 87.* we included the ANGLE library which manages the >>> OpenGL access of chromium. Maybe this is the cause of your problem. >>> >>> Could you try to launch "$ chromium --use-gl=desktop"? This should >>> disable the usage of ANGLE. >>> >>> Best, >>> Jan >>> OpenPGP_signature Description: OpenPGP digital signature
Bug#972302: marked as done (grantlee5: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath)
Your message dated Mon, 11 Jan 2021 16:33:51 + with message-id and subject line Bug#972302: fixed in grantlee5 5.2.0-3 has caused the Debian Bug report #972302, regarding grantlee5: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath 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.) -- 972302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972302 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: grantlee5 Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: fixfilepath ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org When the reproducible=+fixfilepath feature is enabled (either through DEB_BUILD_OPTIONS, or using a dpkg that enables this by default), grantlee5 fails to build from source: http://qa-logs.debian.net/2020/09/26.fixfilepath/grantlee5_5.2.0-2_unstable_fixfilepath.log While the "fixfilepath" feature is not currently enabled by dpkg-buildflags by default, it may become the default at some point in the future, and can by triggered manually by setting DEB_BUILD_OPTIONS=reproducible=+fixfilepath in the build environment. It is also used in the tests.reproducible-builds.org infrastructure when testing unstable and experimental. More information about this issue is available at: https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html I have not identified the exact cause of this issue, but a common trigger is test suites expecting __FILE__ to resolve to an absolute path. The attached patch works around this issue by disabling the fixfilepath feature in debian/rules using DEB_BUILD_MAINT_OPTIONS=-fixfilepath. Thanks for maintaining grantlee5! live well, vagrant From e9685403f92d54948eaa427ba36ac1ad3fa2bb5d Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Thu, 15 Oct 2020 23:56:07 + Subject: [PATCH] debian/rules: Disable fixfilepath feature, as it triggers build failures when enabled. https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html --- debian/rules | 2 ++ 1 file changed, 2 insertions(+) diff --git a/debian/rules b/debian/rules index 1325d43..ee58c88 100755 --- a/debian/rules +++ b/debian/rules @@ -2,6 +2,8 @@ DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH) DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) +# Disable fixfilepath, as it triggers build failures. +export DEB_BUILD_MAINT_OPTIONS = reproducible=-fixfilepath testsuite_failing_archs := hppa ia64 sparc64 ifneq (,$(filter $(DEB_HOST_ARCH),$(testsuite_failing_archs))) -- 2.28.0 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: grantlee5 Source-Version: 5.2.0-3 Done: Aurélien COUDERC We believe that the bug you reported is fixed in the latest version of grantlee5, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurélien COUDERC (supplier of updated grantlee5 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 11 Jan 2021 17:19:37 +0100 Source: grantlee5 Architecture: source Version: 5.2.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Krap Maintainers Changed-By: Aurélien COUDERC Closes: 972302 Changes: grantlee5 (5.2.0-3) unstable; urgency=medium . * Team upload. . [ Vagrant Cascadian ] * Disable fixfilepath reproducibility feature, as it triggers build failures when enabled. (Closes: #972302) Checksums-Sha1: 33a5b2093557de811ad381f18a2b8e54ef1d59fb 2751 grantlee5_5.2.0-3.dsc 34dc7f3b1e1e733a1861b3052cd9464053ccf8f9 13220 grantlee5_5.2.0-3.debian.tar.xz d2aefacb27dc56060cd482499acf7724a6ec0873 13900 grantlee5_5.2.0-3_amd64.buildinfo Checksums-Sha256: 157ab3a804ed53bf2fd64f107d114b8fb2f12759773b65621879e8fc56b22887 2751 grantlee5_5.2.0-3.dsc 9faa2256acfe46e2f82a7d36b032cd1f7ac9d89de2f3b1861e86b8e95d6bf197 13220 grantlee5_5.2.0-3.debian.tar.xz 46083eea36edca8517408d621df94b912c8578be9c4585cc057cb29e0f4c68f6 13900 grantlee5_5.2.0-3_amd64.buildinfo Files: 16
Bug#978390: marked as done (node-rollup-plugin-typescript: FTBFS: src/index.ts(69,54): error TS2345: Argument of type 'NormalizedOutputOptions' is not assignable to parameter of type 'OutputOptions'.)
Your message dated Mon, 11 Jan 2021 16:34:08 +
with message-id
and subject line Bug#978390: fixed in node-rollup-plugin-typescript
6.0.0+~1.0.1-3
has caused the Debian Bug report #978390,
regarding node-rollup-plugin-typescript: FTBFS: src/index.ts(69,54): error
TS2345: Argument of type 'NormalizedOutputOptions' is not assignable to
parameter of type 'OutputOptions'.
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.)
--
978390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-rollup-plugin-typescript
Version: 6.0.0+~1.0.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build --buildsystem=nodejs
> Found debian/nodejs/legacy/build
> cd ./legacy && sh -ex ../debian/nodejs/legacy/build
> + rollup -c
>
> src/index.js → dist/rollup-plugin-typescript.cjs.js,
> dist/rollup-plugin-typescript.es.js...
> (!) Entry module "src/index.js" is implicitly using "default" export mode,
> which means for CommonJS output that its default export is assigned to
> "module.exports". For many tools, such CommonJS output will not be
> interchangeable with the original ES module. If this is intended, explicitly
> set "output.exports" to either "auto" or "default", otherwise you might want
> to consider changing the signature of "src/index.js" to use named exports
> only.
> https://rollupjs.org/guide/en/#outputexports
> src/index.js
> created dist/rollup-plugin-typescript.cjs.js,
> dist/rollup-plugin-typescript.es.js in 47ms
> # Step 1: build a temporary @rollup/plugin-typescript
> cd packages/typescript && \
> ln -s ../../../node_modules/@types/resolve node_modules/ && \
> mkdir dist && \
> NODE_PATH=node_modules tsc --module CommonJS --esModuleInterop
> src/index.ts
> src/index.ts(69,54): error TS2345: Argument of type 'NormalizedOutputOptions'
> is not assignable to parameter of type 'OutputOptions'.
> Types of property 'amd' are incompatible.
> Type 'NormalizedAmdOptions' is not assignable to type 'AmdOptions'.
> Type '{ autoId: false; id?: string; } & { define: string; }' is not
> assignable to type 'AmdOptions'.
> Type '{ autoId: false; id?: string; } & { define: string; }' is not
> assignable to type '{ autoId?: false; id: string; } & { define?: string; }'.
> Type '{ autoId: false; id?: string; } & { define: string; }' is not
> assignable to type '{ autoId?: false; id: string; }'.
> Property 'id' is optional in type '{ autoId: false; id?: string;
> } & { define: string; }' but required in type '{ autoId?: false; id: string;
> }'.
> src/index.ts(70,54): error TS2345: Argument of type 'NormalizedOutputOptions'
> is not assignable to parameter of type 'OutputOptions'.
> make[1]: *** [debian/rules:25: override_dh_auto_build] Error 2
The full build log is available from:
http://qa-logs.debian.net/2020/12/26/node-rollup-plugin-typescript_6.0.0+~1.0.1-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: node-rollup-plugin-typescript
Source-Version: 6.0.0+~1.0.1-3
Done: Xavier Guimard
We believe that the bug you reported is fixed in the latest version of
node-rollup-plugin-typescript, 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 978...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Xavier Guimard (supplier of updated
node-rollup-plugin-typescript package)
(This message was generated automatically
Bug#969597: libzstd: Please correct version in symbol file
Hi Alex, On Mon, Jan 11, 2021 at 02:48:50PM +0100, Alex Mestiashvili wrote: > > No, I didn't correct this specific issue. Just added the new symbols from > the new release. However a patch or a list of "all" symbols is very welcome. I'd like to repeat my suggestion to move that package to a team that is more focussed on this kind of basic software. I'm absolutely swamped with lots of other stuff which is more dedicated to the medical field and more in my focus. I have no time and energy to follow and test those symbols issues for really basic libraries on all kinds of architectures. Kind regards Andreas. -- http://fam-tille.de
Bug#972300: marked as done (keditbookmarks: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath)
Your message dated Mon, 11 Jan 2021 16:48:54 + with message-id and subject line Bug#972300: fixed in keditbookmarks 20.12.0-2 has caused the Debian Bug report #972300, regarding keditbookmarks: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath 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.) -- 972300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: keditbookmarks Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: fixfilepath ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org When the reproducible=+fixfilepath feature is enabled (either through DEB_BUILD_OPTIONS, or using a dpkg that enables this by default), keditbookmarks fails to build from source: http://qa-logs.debian.net/2020/09/26.fixfilepath/keditbookmarks_20.04.0-1_unstable_fixfilepath.log While the "fixfilepath" feature is not currently enabled by dpkg-buildflags by default, it may become the default at some point in the future, and can by triggered manually by setting DEB_BUILD_OPTIONS=reproducible=+fixfilepath in the build environment. It is also used in the tests.reproducible-builds.org infrastructure when testing unstable and experimental. More information about this issue is available at: https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html I have not identified the exact cause of this issue, but a common trigger is test suites expecting __FILE__ to resolve to an absolute path. The attached patch works around this issue by disabling the fixfilepath feature in debian/rules using DEB_BUILD_MAINT_OPTIONS=-fixfilepath. Thanks for maintaining keditbookmarks! live well, vagrant From 9b1cf46b595b17be5da9ec9fd5a7fa2b7c72d523 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Thu, 15 Oct 2020 23:45:04 + Subject: [PATCH] debian/rules: Disable fixfilepath feature, as it triggers build failures when enabled. https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html --- debian/rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index 4f64a3a..b240019 100755 --- a/debian/rules +++ b/debian/rules @@ -1,7 +1,7 @@ #!/usr/bin/make -f # see FEATURE AREAS in dpkg-buildflags(1) -export DEB_BUILD_MAINT_OPTIONS = hardening=+all +export DEB_BUILD_MAINT_OPTIONS = hardening=+all reproducible=-fixfilepath # see ENVIRONMENT in dpkg-buildflags(1) # package maintainers to append CFLAGS -- 2.28.0 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: keditbookmarks Source-Version: 20.12.0-2 Done: Aurélien COUDERC We believe that the bug you reported is fixed in the latest version of keditbookmarks, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurélien COUDERC (supplier of updated keditbookmarks package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 11 Jan 2021 17:26:33 +0100 Source: keditbookmarks Architecture: source Version: 20.12.0-2 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Aurélien COUDERC Closes: 972300 Changes: keditbookmarks (20.12.0-2) unstable; urgency=medium . [ Vagrant Cascadian ] * Disable fixfilepath reproducibility feature, as it triggers build failures when enabled. (Closes: #972300) Checksums-Sha1: d84b8ae588f116a0473f8d1e0b9c4f7e4fd3e5d1 2756 keditbookmarks_20.12.0-2.dsc 1341e4f52aa07cac8db97064b4595c7ba18742a7 8096 keditbookmarks_20.12.0-2.debian.tar.xz 9668e0fc982ba4c47dcbe5ae58b7f3e632fccc1f 21286 keditbookmarks_20.12.0-2_amd64.buildinfo Checksums-Sha256: 75e9e77e3c1818ed7cfda18ae0903b58da8ffacb18432487818c9a583e7974c2 2756 keditbookmarks_20.12.0-2.dsc 681b8f3a74aba697e10663fec1b80a9f069d5d249d72a1355337393c3c4de0c2 8096 keditbookmarks_20.12.0-2.debian.tar.xz 15d37c8a4dd2f0c8a083a2a24b06ffc48f6b6881f0c09435c6ac0935e35d6b64 21286 keditbookmarks_20.12.0-2_amd6
Processed: Readjust, I probably reported the bug against the wrong pkg
Processing commands for cont...@bugs.debian.org:
> reassign 979704 src:shasta 0.6.0-5
Bug #979704 {Done: Michael R. Crusoe } [libspoa-dev]
libspoa-dev: breaks reverse-depends: shasta
Bug reassigned from package 'libspoa-dev' to 'src:shasta'.
No longer marked as found in versions spoa/4.0.6+ds-1.
No longer marked as fixed in versions shasta/0.7.0-1.
Bug #979704 {Done: Michael R. Crusoe } [src:shasta]
libspoa-dev: breaks reverse-depends: shasta
Marked as found in versions shasta/0.6.0-5.
> fixed 979704 shasta/0.7.0-1
Bug #979704 {Done: Michael R. Crusoe } [src:shasta]
libspoa-dev: breaks reverse-depends: shasta
The source shasta and version 0.7.0-1 do not appear to match any binary packages
Marked as fixed in versions shasta/0.7.0-1.
> tags 979704 + ftbfs
Bug #979704 {Done: Michael R. Crusoe } [src:shasta]
libspoa-dev: breaks reverse-depends: shasta
Added tag(s) ftbfs.
> severity 979704 serious
Bug #979704 {Done: Michael R. Crusoe } [src:shasta]
libspoa-dev: breaks reverse-depends: shasta
Severity set to 'serious' from 'grave'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
979704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#975665: Raising the bug's severity
Control: tags -1 patch There is a patch available; with it applied it builds here locally (until it hits #975198) https://build.opensuse.org/package/view_file/science/PrusaSlicer/PrusaSlicer-pr4340-boost-1-73.patch?expand=0 -- tobi
Processed: Re: Raising the bug's severity
Processing control commands: > tags -1 patch Bug #975665 [slic3r-prusa] slic3r-prusa: FTBFS against boost_1.74 Added tag(s) patch. -- 975665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979563: gitlab: my instance work great after upgrade to 13.5.6.1!
Package: gitlab Followup-For: Bug #979563 Dear Maintainer, My instance work great after upgrade to 13.5.6.1! I can see the content of folder and files on UI. I can fetch, push, etc. I added versions off packages if I use, maby will help you. If you want to give you more info, tell me. Dragos -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'experimental'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gitlab depends on: ii asciidoctor 2.0.10-2 ii bc 1.07.1-2+b2 ii bundler 2.2.0~rc.2-6 ii bzip21.0.8-4 ii dbconfig-pgsql 2.0.17 ii debconf [debconf-2.0]1.5.74 ii fonts-font-awesome [node-font-awesome] 5.0.10+really4.7.0~dfsg-4 ii gitlab-common13.4.6+dfsg1-2 ii gitlab-workhorse 8.46.0+debian-1 ii libjs-bootstrap4 [node-bootstrap]4.5.2+dfsg1-4 ii libjs-codemirror [node-codemirror] 5.59.0+~cs0.23.105-1 ii libjs-pdf [node-pdfjs-dist] 2.6.347+dfsg-3 ii libjs-popper.js [node-popper.js] 1.16.1+ds-2 ii libruby2.7 [ruby-json] 2.7.2-3 ii lsb-base 11.1.0 ii nginx1.18.0-6 ii nginx-extras [nginx] 1.18.0-6+b1 ii node-autosize4.0.2~dfsg1-5 ii node-axios 0.21.1+dfsg-1 ii node-babel-loader8.2.2-3 ii node-babel7 7.12.11+~cs150.141.84-3 ii node-brace-expansion 2.0.0-1 ii node-cache-loader4.1.0+~cs2.0.0-1 ii node-chart.js2.9.4+dfsg+~cs2.10.1-3 pn node-clipboard ii node-compression-webpack-plugin 6.1.1-1 ii node-copy-webpack-plugin 5.1.2+~cs9.0.2-4 ii node-core-js 3.8.2-1 ii node-css-loader 5.0.1+~cs14.0.5-1 ii node-d3 5.16.0-4 ii node-d3-scale2.2.2-3 ii node-d3-selection1.4.0-6 pn node-dateformat pn node-deckar01-task-list ii node-exports-loader 1.1.1-2 ii node-file-loader 6.2.0-2 pn node-fuzzaldrin-plus ii node-glob7.1.6+~7.1.3-1 pn node-imports-loader ii node-jed 1.1.1-2 ii node-jquery 3.5.1+dfsg+~3.5.5-5 pn node-jquery-ujs pn node-js-cookie ii node-js-yaml 3.14.0+dfsg-3 ii node-jszip 3.5.0+dfsg-1 ii node-jszip-utils 0.0.2+dfsg-2 ii node-katex 0.8.3+dfsg-2 ii node-lodash 4.17.20+dfsg+~cs8.31.172-1 ii node-marked 0.8.0+ds+repack-2 ii node-mermaid 8.7.0+ds+~cs27.17.17-2 ii node-minimatch 3.0.4+~3.0.3-1 ii node-miragejs0.1.41+~cs5.6.6-4 ii node-mousetrap 1.6.5~ds-1 ii node-prismjs 1.11.0+dfsg-4 ii node-prosemirror-markdown1.4.4-2 pn node-prosemirror-model pn node-raven-js ii node-raw-loader 4.0.2-2 ii node-style-loader2.0.0-2 ii node-three-orbit-controls82.1.0-3 ii node-three-stl-loader1.0.6-3 ii node-timeago.js 4.0.2-3 pn node-underscore ii node-url-loader 4.1.1-3 ii node-uuid8.3.2+~8.3.0-3 ii node-vue
Bug#956423: Bullseye freeze is coming soon
Hi all, Bullseye freeze is coming and we still have problems with node-request removal. In particular, node-jsdom is not easy to patch. I tried a patch (not approved by upstream) but it needs a lot of unavailable Node.js modules. Looking at the following list, it seems that only node-jsdom is important to update, others have no important reverse dependencies AFAIK, haven't they? List of problems (from dak): # Broken Depends: node-jsdom: node-jsdom node-jsonld: node-jsonld node-matrix-js-sdk: node-matrix-js-sdk node-millstone: node-millstone node-yarnpkg: yarnpkg # Broken Build-Depends: node-client-sessions: node-request node-jsdom: node-request node-matrix-js-sdk: node-request node-opencv: node-request node-request-promise-core: node-request node-yarnpkg: node-request (>= 2.88.1-5~)
Processed: severity of 979823 is serious
Processing commands for cont...@bugs.debian.org: > severity 979823 serious Bug #979823 [src:catch2] catch2: Needs source-only upload Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 979823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979823: catch2: diff for NMU version 2.13.4-1.1
Control: tags 979823 + patch Control: tags 979823 + pending Dear maintainer, I've prepared an NMU for catch2 (versioned as 2.13.4-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. (It is a no-change source only upload) Regards. diff -Nru catch2-2.13.4/debian/changelog catch2-2.13.4/debian/changelog --- catch2-2.13.4/debian/changelog 2020-12-29 21:12:46.0 +0100 +++ catch2-2.13.4/debian/changelog 2021-01-11 19:24:37.0 +0100 @@ -1,3 +1,11 @@ +catch2 (2.13.4-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * No-Change-Source-Only upload to allow testing migration testing. +(Closes: #979823) + + -- Tobias Frost Mon, 11 Jan 2021 19:24:37 +0100 + catch2 (2.13.4-1) unstable; urgency=medium * New upstream release
Processed: catch2: diff for NMU version 2.13.4-1.1
Processing control commands: > tags 979823 + patch Bug #979823 [src:catch2] catch2: Needs source-only upload Added tag(s) patch. > tags 979823 + pending Bug #979823 [src:catch2] catch2: Needs source-only upload Added tag(s) pending. -- 979823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 979825 libx11 Bug #979825 [chromium] chromium: Chromium freezes on startup Bug reassigned from package 'chromium' to 'libx11'. No longer marked as found in versions chromium/87.0.4280.141-0.1. Ignoring request to alter fixed versions of bug #979825 to the same values previously set > End of message, stopping processing here. Please contact me if you need assistance. -- 979825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: openorienteering-mapper: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath
Processing commands for cont...@bugs.debian.org: > severity 972294 normal Bug #972294 [openorienteering-mapper] openorienteering-mapper: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath Severity set to 'normal' from 'serious' > tags 972294 - moreinfo Bug #972294 [openorienteering-mapper] openorienteering-mapper: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath Removed tag(s) moreinfo. > block 972294 by 876901 Bug #972294 [openorienteering-mapper] openorienteering-mapper: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath 972294 was not blocked by any bugs. 972294 was not blocking any bugs. Added blocking bug(s) of 972294: 876901, 876933, and 876917 > affects 876901 src:openorienteering-mapper Bug #876901 [qtbase5-dev] QFINDTESTDATA uses __FILE__ Bug #876917 [qtbase5-dev] QFINDTESTDATA uses __FILE__ Bug #876933 [qtbase5-dev] QFINDTESTDATA uses __FILE__ Added indication that 876901 affects src:openorienteering-mapper Added indication that 876917 affects src:openorienteering-mapper Added indication that 876933 affects src:openorienteering-mapper > thanks Stopping processing here. Please contact me if you need assistance. -- 876901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901 876917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876917 876933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876933 972294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972294 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979575: ispell 3.4.01 breaks affix files of igerman98 and hkgerman
reassign 979694 ispell 3.4.01-1 reassign 979746 ispell 3.4.01-1 forcemerge 979575 979694 979746 affects 979575 ispanish thanks El dom, 10 ene 2021 a las 23:02, Agustin Martin () escribió: > > El dom, 10 ene 2021 a las 22:39, Robert Luberda () > escribió: > > > > reassign 979549 ispell 3.4.01-1 > > reassign 979565 ispell 3.4.01-1 > > forcemerge 979575 979549 979565 > > affects 979575 ingerman iogerman ifrench iesperanto iswiss > > tags 979575 pending fixed-upstream > > thanks > > > > > > Roland Rosenfeld pisze: > > > > > > In the meantime upstream maintainer released a version 3.4.02 on > > > > Yes, I've noticed it this morning, and it looks like upgrading to that > > version fixes the issue. > > This may also be causing #979694. Confirmed, ispell 3.4.02 fixes this problem. Reassigning and forcemerging #979575 and #979746 with this bug report, so everything is marked as fixed. Regards, -- Agustin
Processed: Re: Bug#979575: ispell 3.4.01 breaks affix files of igerman98 and hkgerman
Processing commands for cont...@bugs.debian.org:
> reassign 979694 ispell 3.4.01-1
Bug #979694 [dictionaries-common] dictionaries-common: 'espa~nol' dict contains
illegal characters
Bug reassigned from package 'dictionaries-common' to 'ispell'.
No longer marked as found in versions dictionaries-common/1.28.3.
Ignoring request to alter fixed versions of bug #979694 to the same values
previously set
Bug #979694 [ispell] dictionaries-common: 'espa~nol' dict contains illegal
characters
Marked as found in versions ispell/3.4.01-1.
> reassign 979746 ispell 3.4.01-1
Bug #979746 [wspanish] wspanish: Word "xx" contains illegal characters, on
dictionaries-common trigger (ispell-autobuildhash)
Bug reassigned from package 'wspanish' to 'ispell'.
No longer marked as found in versions wspanish/1.0.29.
Ignoring request to alter fixed versions of bug #979746 to the same values
previously set
Bug #979746 [ispell] wspanish: Word "xx" contains illegal characters, on
dictionaries-common trigger (ispell-autobuildhash)
Marked as found in versions ispell/3.4.01-1.
> forcemerge 979575 979694 979746
Bug #979575 {Done: Robert Luberda } [ispell] ispell 3.4.01
breaks affix files of igerman98 and hkgerman
Bug #979549 {Done: Robert Luberda } [ispell] ingerman:
Problems during ispell-autobuild
Bug #979565 {Done: Robert Luberda } [ispell]
/usr/lib/ispell/ogerman.aff: multiple errors
Bug #979575 {Done: Robert Luberda } [ispell] ispell 3.4.01
breaks affix files of igerman98 and hkgerman
Added tag(s) l10n.
Added tag(s) l10n.
Added tag(s) l10n.
Bug #979746 [ispell] wspanish: Word "xx" contains illegal characters, on
dictionaries-common trigger (ispell-autobuildhash)
Severity set to 'serious' from 'normal'
Marked Bug as done
Added indication that 979746 affects ifrench,iswiss,iesperanto,ingerman,iogerman
Marked as fixed in versions ispell/3.4.02-1.
Added tag(s) fixed-upstream and upstream.
Bug #979694 [ispell] dictionaries-common: 'espa~nol' dict contains illegal
characters
Severity set to 'serious' from 'normal'
Marked Bug as done
Added indication that 979694 affects ifrench,iswiss,iesperanto,ingerman,iogerman
Marked as fixed in versions ispell/3.4.02-1.
Added tag(s) upstream, l10n, and fixed-upstream.
Bug #979565 {Done: Robert Luberda } [ispell]
/usr/lib/ispell/ogerman.aff: multiple errors
Removed indication that 979565 affects ingerman, iesperanto, ifrench, iswiss,
and iogerman
Added indication that 979565 affects ifrench,iswiss,iesperanto,ingerman,iogerman
Removed indication that 979549 affects iogerman, iswiss, ifrench, iesperanto,
and ingerman
Added indication that 979549 affects ifrench,iswiss,iesperanto,ingerman,iogerman
Removed indication that 979575 affects iesperanto, ingerman, iogerman, iswiss,
and ifrench
Added indication that 979575 affects ifrench,iswiss,iesperanto,ingerman,iogerman
Bug #979549 {Done: Robert Luberda } [ispell] ingerman:
Problems during ispell-autobuild
Merged 979549 979565 979575 979694 979746
> affects 979575 ispanish
Bug #979575 {Done: Robert Luberda } [ispell] ispell 3.4.01
breaks affix files of igerman98 and hkgerman
Bug #979549 {Done: Robert Luberda } [ispell] ingerman:
Problems during ispell-autobuild
Bug #979565 {Done: Robert Luberda } [ispell]
/usr/lib/ispell/ogerman.aff: multiple errors
Bug #979694 {Done: Robert Luberda } [ispell]
dictionaries-common: 'espa~nol' dict contains illegal characters
Bug #979746 {Done: Robert Luberda } [ispell] wspanish: Word
"xx" contains illegal characters, on dictionaries-common trigger
(ispell-autobuildhash)
Added indication that 979575 affects ispanish
Added indication that 979549 affects ispanish
Added indication that 979565 affects ispanish
Added indication that 979694 affects ispanish
Added indication that 979746 affects ispanish
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
979549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979549
979565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979565
979575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979575
979694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979694
979746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> forcemerge 979590 979825
Bug #979590 {Done: Julien Cristau } [libx11] libx11
possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium
Bug #979618 {Done: Julien Cristau } [libx11] libx11
possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium
Bug #979825 [libx11] chromium: Chromium freezes on startup
Marked Bug as done
Outlook recorded from message bug 979825 message
Added indication that 979825 affects chromium
Marked as fixed in versions libx11/2:1.7.0-2.
There is no source info for the package 'libx11' at version '2:1.7.0-1' with
architecture ''
Unable to make a source version for version '2:1.7.0-1'
Marked as found in versions 2:1.7.0-1.
Bug #979618 {Done: Julien Cristau } [libx11] libx11
possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium
Merged 979590 979618 979825
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
979590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979590
979618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979618
979825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979825
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979825: chromium: Chromium freezes on startup
Package: chromium
Version: 87.0.4280.141-0.1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Chromium freezes on start up, requiring it to be killed, and making it
completely unusable.
Exactly the same with clean temporary profile.
Console output:
$ chromium --temp-profile
Using temporary profile: /tmp/tmp.7HqrY9kdHm
[4080619:4080655:0111/130724.593825:ERROR:nss_util.cc(283)] After loading Root
Certs, loaded==false: NSS error code: -8018
libva error: vaGetDriverNameByIndex() failed with unknown libva error,
driver_name = (null)
[4080617:4080617:0111/130724.619909:ERROR:vaapi_wrapper.cc(541)] vaInitialize
failed: unknown libva error
[4080617:4080617:0111/130724.640757:ERROR:sandbox_linux.cc(374)]
InitializeSandbox() called with multiple threads in process gpu-process.
[4080588:4080588:0111/130725.142104:ERROR:CONSOLE(1)] "Refused to execute
inline event handler because it violates the following Content Security Policy
directive: "script-src 'strict-dynamic'
'sha256-1+GSDjMMklBjZY0QiWq+tGupCvajw4Xbn46ect2mZgM='
'sha256-2mX1M62Fd0u8q0dQY2mRsK5S1NS9jJuQAvyE8tD0dkQ='
'sha256-EtIKSV82ixJHE3AzqhoiVbUGKG+Kd8XS0fFToow29o0='
'sha256-QSyFltV9X3gkyBrg+SMfKvZNXmqPQc6K4B6OYhTuXmw='
'sha256-ANdtIo91Yk/zh1YKZ+IXKP1pb00awOjEFMAUld02F6A='
'sha256-CbH+xPsBKQxVw5d9blISLDeuMSe1M+dJ4xfArFynIfw='
'sha256-lA+EURA/fC0TZq1ATYZvxIQHBc9iTAaBcI+dFMmTn9I='
'sha256-ezOZE3GsFiiFM39LE8bQs5vdJyeJAqh3r+5jHc7863I='". Either the
'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is
required to enable inline execution.
", source: chrome-search://local-ntp/local-ntp.html (1)
[4080617:4080617:0111/130728.834685:ERROR:gl_surface_presentation_helper.cc(259)]
GetVSyncParametersIfAvailable() failed for 1 times!
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (800, 'testing'), (750, 'unstable'), (500, 'unstable-debug'),
(500, 'testing-debug'), (500, 'oldstable-updates'), (500, 'stable'), (500,
'oldstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 chromium depends on:
ii chromium-common87.0.4280.141-0.1
ii libasound2 1.2.4-1.1
ii libatk-bridge2.0-0 2.38.0-1
ii libatk1.0-02.36.0-2
ii libatomic1 10.2.1-3
ii libatspi2.0-0 2.38.0-2
ii libavcodec-extra58 [libavcodec58] 7:4.3.1-5
ii libavformat58 7:4.3.1-5
ii libavutil567:4.3.1-5
ii libc6 2.31-9
ii libcairo2 1.16.0-5
ii libcups2 2.3.3op1-5
ii libdbus-1-31.12.20-1
ii libdrm22.4.103-2
ii libevent-2.1-7 2.1.12-stable-1
ii libexpat1 2.2.10-1
ii libflac8 1.3.3-2
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.10.4+dfsg-1
ii libgbm120.3.2-1
ii libgcc-s1 10.2.1-3
ii libgdk-pixbuf-2.0-02.42.2+dfsg-1
ii libglib2.0-0 2.66.4-1
ii libgtk-3-0 3.24.24-1
ii libharfbuzz0b 2.6.7-1
ii libicu67 67.1-5
ii libjpeg62-turbo1:2.0.5-2
ii libjsoncpp24 1.9.4-4
ii liblcms2-2 2.9-4+b1
ii libminizip11.1-8+b1
ii libnspr4 2:4.29-1
ii libnss32:3.60-1
ii libopenjp2-7 2.3.1-1
ii libopus0 1.3.1-0.1
ii libpango-1.0-0 1.46.2-3
ii libpangocairo-1.0-01.46.2-3
ii libpng16-161.6.37-3
ii libpulse0 14.0-2
ii libre2-9 20201101+dfsg-2
ii libsnappy1v5 1.1.8-1
ii libstdc++6 10.2.1-3
ii libwebp6 0.6.1-2+b1
ii libwebpdemux2 0.6.1-2+b1
ii libwebpmux30.6.1-2+b1
ii libx11-6 2:1.6.12-1
ii libx11-xcb12:1.7.0-1
ii libxcb11.14-2.1
ii libxcomposite1 1:0.4.5-1
ii libxdamage11:1.1.5-2
ii libxext6 2:1.3.3-1.1
ii libxfixes3 1:5.0.3-2
ii libxml22.9.10+dfsg-6.3+b1
ii
Bug#979156: [pkg-php-pear] Bug#979156: Useless in Debian
On 11/01/21 4:37 am, Guilhem Moulin wrote:
> Control: severity -1 serious
>
> On Mon, 11 Jan 2021 at 00:58:01 +0100, Guilhem Moulin wrote:
>> On Sun, 03 Jan 2021 at 16:54:41 -0800, Sunil Mohan Adapa wrote:
>>> I will be filing an RM: bug on the package on Jan 10, 2021. I will
>>> wait to see if the other uploaders think it is still needed.
>>
>> Roundcube's test suite which I'm working on now has some tests making
>> use of Net_IDNA2
>
> On closer look Net_IDNA2 is only used as a fallback when idn_to_{ascii,utf8}()
> do not exist. Roundcube has a hard dependency on php-intl already, so
> as far as Debian is concerned the part using Net_IDNA2 is dead code. I
> therefore drop my interest in having php-net-idna2 in Bullseye and
> restore the RC severity :-)
>
> Appologies for the noise
>
I filed an RM bug (#979829) and CCed all uploaders and participants of
this bug.
--
Sunil
OpenPGP_signature
Description: OpenPGP digital signature
Bug#979831: src:colord: fails to migrate to testing for too long: unresolved RC bug
Source: colord Version: 1.4.4-2 Severity: serious Control: close -1 1.4.5-2 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 978167 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:colord in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, 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=colord OpenPGP_signature Description: OpenPGP digital signature
Processed: src:colord: fails to migrate to testing for too long: unresolved RC bug
Processing control commands:
> close -1 1.4.5-2
Bug #979831 [src:colord] src:colord: fails to migrate to testing for too long:
unresolved RC bug
Marked as fixed in versions colord/1.4.5-2.
Bug #979831 [src:colord] src:colord: fails to migrate to testing for too long:
unresolved RC bug
Marked Bug as done
> block -1 by 978167
Bug #979831 {Done: Paul Gevers } [src:colord] src:colord:
fails to migrate to testing for too long: unresolved RC bug
979831 was not blocked by any bugs.
979831 was not blocking any bugs.
Added blocking bug(s) of 979831: 978167
--
979831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979381: Useless in Debian
Hello, I have filed an RM bug (#979832) against the package and CCed David and all the uploaders. Thanks, -- Sunil
Bug#979834: chromiums shows … nothing but errors on the console
Package: chromium Version: 87.0.4280.141-0.1 Severity: serious Justification: unusable as shipped -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Starting today's chromium leads to - - nothing within the window (actually an image from the previous desktop) - - tons of errors like Xlib: sequence lost (0x1012c > 0x12e) in reply type 0x0! in the terminal. After looking through https://peter.sh/experiments/chromium-command-line-switches/ and trying some switches I found that --gpu-sandbox-start-early helps to get it back to working. Some observations: % chromium --use-gl=desktop Xlib: sequence lost (0x1010d > 0x10f) in reply type 0x0! Xlib: sequence lost (0x10114 > 0x116) in reply type 0x0! Xlib: sequence lost (0x1011b > 0x11d) in reply type 0x0! [11129:11129:0111/200209.168377:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. Xlib: sequence lost (0x1012c > 0x12e) in reply type 0x0! Xlib: sequence lost (0x10133 > 0x135) in reply type 0x0! Xlib: sequence lost (0x1013a > 0x13c) in reply type 0x0! Xlib: sequence lost (0x10145 > 0x147) in reply type 0x0! Xlib: sequence lost (0x1014c > 0x14e) in reply type 0x0! Xlib: sequence lost (0x10153 > 0x155) in reply type 0x0! % chromium --use-gl=desktop --gpu-sandbox-start-early [12840:12840:0111/200259.913622:ERROR:gl_implementation.cc(282)] Failed to load libGL.so.1: libGL.so.1: cannot open shared object file: Operation not permitted [12840:12840:0111/200259.923311:ERROR:viz_main_impl.cc(150)] Exiting GPU process due to errors during initialization % chromium --use-gl=egl --gpu-sandbox-start-early [25274:25274:0111/200829.114696:ERROR:gl_implementation.cc(282)] Failed to load libGLESv2.so.2: libGLESv2.so.2: cannot open shared object file: Operation not permitted [25274:25274:0111/200829.136862:ERROR:viz_main_impl.cc(150)] Exiting GPU process due to errors during initialization locate finds both /usr/lib/x86_64-linux-gnu/libGLESv2.so.2 and /usr/lib/x86_64-linux-gnu/libGL.so.1 This Xlib error reminds me of #979561 (without the segfault). Unlike in geeqie, downgrading libx11-6 from 2:1.7.0-1 to 2:1.6.12-1 doesn't help (chromium first starts (without any switches) but crashes soon). Cheers, gregor - -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'oldoldstable'), (500, 'experimental'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages chromium depends on: ii chromium-common 87.0.4280.141-0.1 ii libasound2 1.2.4-1.1 ii libatk-bridge2.0-0 2.38.0-1 ii libatk1.0-0 2.36.0-2 ii libatomic1 10.2.1-6 ii libatspi2.0-02.38.0-2 ii libavcodec58 7:4.3.1-5 ii libavformat587:4.3.1-5 ii libavutil56 7:4.3.1-5 ii libc62.31-9 ii libcairo21.16.0-5 ii libcups2 2.3.3op1-3 ii libdbus-1-3 1.12.20-1 ii libdrm2 2.4.103-2 ii libevent-2.1-7 2.1.12-stable-1 ii libexpat12.2.10-1 ii libflac8 1.3.3-2 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1 ii libgbm1 20.3.2-1 ii libgcc-s110.2.1-6 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.4-1 ii libgtk-3-0 3.24.24-1 ii libharfbuzz0b2.6.7-1 ii libicu67 67.1-5 ii libjpeg62-turbo 1:2.0.5-2 ii libjsoncpp24 1.9.4-4 ii liblcms2-2 2.9-4+b1 ii libminizip1 1.1-8+b1 ii libnspr4 2:4.29-1 ii libnss3 2:3.60-1 ii libopenjp2-7 2.3.1-1 ii libopus0 1.3.1-0.1 ii libpango-1.0-0 1.46.2-3 ii libpangocairo-1.0-0 1.46.2-3 ii libpng16-16 1.6.37-3 ii libpulse014.0-2 ii libre2-9 20201101+dfsg-2 ii libsnappy1v5 1.1.8-1 ii libstdc++6 10.2.1-6 ii libwebp6 0.6.1-2+b1 ii libwebpdemux20.6.1-2+b1 ii libwebpmux3 0.6.1-2+b1 ii libx11-6 2:1.7.0-1 ii libx11-xcb1 2:1.7.0-1 ii libxcb1 1.14-2.1 ii libxcomposite1 1:0.4.5-1 ii libxdamage1 1:1.1.5-2 ii libxext6 2:1.3.3-1.1 ii libxfixes3 1:5.0.3-2 ii libxml2 2.9.10+dfsg-6.3+b1 ii libxrandr2 2:1.5.1-1 ii libxslt1.1 1.1.34-4 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages chromium recommends: ii chromium-sandbox 87.0.4280.141-0.1 Versions of packages chromium suggests: pn chromium-driver pn chromium-l10n pn chromium-shell Versions of packa
Bug#979836: icu: autopkgtest failure (fixed in experimental)
Source: icu Version: 57.1-9 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Control: close -1 68.2-1 Dear maintainer(s), You package has an autopkgtest, graet. However, it always fails on the ci.debian.net infrastructure [1]. Can you please investigate the situation and fix it? I see you fixed it in experimental, could you carry the autopkgtest change to the version in unstable? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: icu: autopkgtest failure (fixed in experimental)
Processing control commands: > close -1 68.2-1 Bug #979836 [src:icu] icu: autopkgtest failure (fixed in experimental) Marked as fixed in versions icu/68.2-1. Bug #979836 [src:icu] icu: autopkgtest failure (fixed in experimental) Marked Bug as done -- 979836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979838: twisted: autopkgtest regression in testing: No such file or directory: 'ckeygen'
Source: twisted
Version: 18.9.0-3
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a not so recent change (March 2019) in testing the autopkgtest of
your package started to fail. I copied some of the output at the bottom
of this report. Can you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
https://ci.debian.net/data/autopkgtest/testing/amd64/t/twisted/9444048/log.gz
autopkgtest [09:30:22]: test unit-tests-3: [---
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/twisted/conch/test/test_ckeygen.py",
line 86, in test_keygeneration
self._testrun('ecdsa', '384')
File
"/usr/lib/python3/dist-packages/twisted/conch/test/test_ckeygen.py",
line 75, in _testrun
subprocess.call(args)
File "/usr/lib/python3.9/subprocess.py", line 349, in call
with Popen(*popenargs, **kwargs) as p:
File "/usr/lib/python3.9/subprocess.py", line 947, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.9/subprocess.py", line 1819, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
builtins.FileNotFoundError: [Errno 2] No such file or directory: 'ckeygen'
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/twisted/conch/test/test_ckeygen.py",
line 105, in test_runBadKeytype
subprocess.check_call(
File "/usr/lib/python3/dist-packages/twisted/trial/_synctest.py", line
352, in __exit__
self._testCase.fail(
twisted.trial.unittest.FailTest: builtins.FileNotFoundError raised
instead of CalledProcessError:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/twisted/trial/_asynctest.py",
line 111, in _run
d = defer.maybeDeferred(
File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line
151, in maybeDeferred
result = f(*args, **kw)
File "/usr/lib/python3/dist-packages/twisted/internet/utils.py", line
217, in runWithWarningsSuppressed
result = f(*a, **kw)
File
"/usr/lib/python3/dist-packages/twisted/conch/test/test_ckeygen.py",
line 105, in test_runBadKeytype
subprocess.check_call(
--- ---
File
"/usr/lib/python3/dist-packages/twisted/conch/test/test_ckeygen.py",
line 105, in test_runBadKeytype
subprocess.check_call(
File "/usr/lib/python3.9/subprocess.py", line 368, in check_call
retcode = call(*popenargs, **kwargs)
File "/usr/lib/python3.9/subprocess.py", line 349, in call
with Popen(*popenargs, **kwargs) as p:
File "/usr/lib/python3.9/subprocess.py", line 947, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.9/subprocess.py", line 1819, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
builtins.FileNotFoundError: [Errno 2] No such file or directory: 'ckeygen'
OpenPGP_signature
Description: OpenPGP digital signature
Bug#979840: dns-root-data: autopkgtest regression in testing: failed to query server 127.0.0.1@53
Source: dns-root-data Version: 2019052802 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a not so recent change (beginning 2020) somewhere outside your package the autopkgtest of your package started to fail. I copied some of the output at the bottom of this report. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul https://ci.debian.net/data/autopkgtest/testing/amd64/d/dns-root-data/9516338/log.gz autopkgtest [17:42:10]: test baseline: [--- ;; WARNING: response timeout for 127.0.0.1@53(UDP) ;; WARNING: response timeout for 127.0.0.1@53(UDP) ;; WARNING: response timeout for 127.0.0.1@53(UDP) ;; ERROR: failed to query server 127.0.0.1@53(UDP) autopkgtest [17:42:25]: test baseline: ---] OpenPGP_signature Description: OpenPGP digital signature
Bug#979841: rdflib: autopkgtest failure: cannot create directory ‘build/py3_testing’
Source: rdflib Version: 4.2.1-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You package has an autopkgtest, graet. However, it always fails on the ci.debian.net infrastructure [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul https://ci.debian.net/data/autopkgtest/testing/amd64/r/rdflib/9601096/log.gz autopkgtest [14:14:57]: test python3: [--- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.y62s4fn_/downtmp/build.9Un/src/setup.py", line 39, in from setuptools import setup, find_packages ModuleNotFoundError: No module named 'setuptools' mkdir: cannot create directory ‘build/py3_testing’: No such file or directory cp: cannot create directory 'build/py3_testing/': No such file or directory cp: target 'build/py3_testing/' is not a directory cp: cannot stat 'build/lib/rdflib': No such file or directory ./run_tests_py3.sh: 14: cd: can't cd to build/py3_testing ./run_tests_py3.sh: 16: 2to3: not found ./run_tests_py3.sh: 17: 2to3: not found File "/tmp/autopkgtest-lxc.y62s4fn_/downtmp/build.9Un/src/run_tests.py", line 92 print "Running nose with:", " ".join(finalArgs[1:]) ^ SyntaxError: invalid syntax OpenPGP_signature Description: OpenPGP digital signature
Bug#979843: python-django: autopkgtest regression in testing: 'image/vnd.mozilla.apng' != 'image/png'
Source: python-django Version: 2:2.2.17-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent in testing the autopkgtest of your package started to fail. I copied some of the output at the bottom of this report. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-django/9501583/log.gz == FAIL: test_attach_file (mail.tests.MailTests) Test attaching a file against different mimetypes and make sure that -- Traceback (most recent call last): File "/usr/lib/python3.9/unittest/case.py", line 59, in testPartExecutor yield File "/usr/lib/python3.9/unittest/case.py", line 593, in run self._callTestMethod(testMethod) File "/usr/lib/python3.9/unittest/case.py", line 550, in _callTestMethod method() File "/tmp/autopkgtest-lxc.pw5bm44p/downtmp/autopkgtest_tmp/tests/mail/tests.py", line 472, in test_attach_file self.assertEqual(mimetypes.guess_type(basename)[0], real_mimetype) File "/usr/lib/python3.9/unittest/case.py", line 831, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python3.9/unittest/case.py", line 1211, in assertMultiLineEqual self.fail(self._formatMessage(msg, standardMsg)) File "/usr/lib/python3.9/unittest/case.py", line 670, in fail raise self.failureException(msg) AssertionError: 'image/vnd.mozilla.apng' != 'image/png' - image/vnd.mozilla.apng + image/png OpenPGP_signature Description: OpenPGP digital signature
Bug#979563: gitlab: my instance work great after upgrade to 13.5.6.1!
Just to know, in previous version I have some trouble with licensee, and I do the following to solve the problem: gitaly(13.4.6+dfsg1-2) and gitlab(13.4.7-2) have in Gemfile: gem 'rugged', '~> 0.28' ... gem 'licensee', '~> 8.9' But rugged is 1.1.0+ds-1 in testing and unstable and licensee need rugged~>0.24. Solved putting in Gemfile: gem 'rugged', '>= 0.28' gem 'licensee', '~> 9.14', '>= 9.14.1' and manually install licensee 9.14.1 with: cd /usr/share/gitlab gem install licensee It could help. Cu respect, Dragos Jarca General manager Dynamic Puzzle S.R.L. www.dynamicpuzzle.ro On 11.01.2021 17:52, Pirate Praveen wrote: On 2021, ജനുവരി 11 7:00:11 PM IST, Dragos Jarca wrote: Package: gitlab Followup-For: Bug #979563 Dear Maintainer, My instance work great after upgrade to 13.5.6.1! I can see the content of folder and files on UI. I can fetch, push, etc. I added versions off packages if I use, maby will help you. If you want to give you more info, tell me. Thanks for the feedback. I can see gitaly is still 13.4.6 so the bug is in gitaly. - Versions of packages gitlab recommends: ii certbot 1.10.1-1 ii gitaly 13.4.6+dfsg1-2 So I suggest you hold gitaly on this version.
Processed: found 979765 in 5.9.15-1
Processing commands for cont...@bugs.debian.org: > # submitter mentions 5.9 as well > found 979765 5.9.15-1 Bug #979765 [src:linux] linux-image-5.10.0-1-amd64: Kernel panic on boot on my Via VX900 Marked as found in versions linux/5.9.15-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 979765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): your mail
Processing commands for cont...@bugs.debian.org:
> forcemerge 909651 956778
Bug #909651 {Done: Thomas Koch } [parcellite] Please enable
AppIndicator support and switch over to Ayatana AppIndicator
Unable to merge bugs because:
package of #956778 is 'src:parcellite' not 'parcellite'
Failed to forcibly merge 909651: Did not alter merged bugs.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
909651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909651
956778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#931003: [Pkg-rust-maintainers] Bug#931003: Removed package(s) from unstable
On Sun, 8 Sep 2019, Ximin Luo wrote: > Santiago Vila: > > reopen 931003 > > found 931003 0.2.4-1 > > fixed 931003 0.2.4-1+rm > > thanks > > > > Hi. > > > > This was automatically closed by ftpmaster because the package was > > removed from unstable, but this still does not fix the FTBFS problem > > in stable. > > > > Thanks. > > > > Please be aware that the Debian Rust team today *does not make any > effort* towards bugs affecting Debian Stable. [...] Not even FTBFS bugs, as it is the case here? There are already 74 packages which FTBFS in stable (by my count), it would be much better if every mantainer cared about their own packages. I'm curious: does this really sound unreasonable for you? Thanks.
Bug#979562: lightdm session termination does not stop xscreensaver
Hallo, * Michael Biebl [Sun, Jan 10 2021, 08:24:12PM]: > Am 10.01.21 um 20:02 schrieb Jamie Zawinski: > > > Why would a xscreensaver instance running for user A have any influence > > > on a xscreensaver instance running for user B? That seems absolutely > > > weird to me and something I don't understand. > > > > Yeah, that sounds impossible, assuming that the X server has restarted > > between user A and user B. > > > > If things have gone wrong in a weird way, the "xscreensaver-systemd" > > process of user A might linger, but it won't be able to communicate with > > user B's xscreensaver. > > Since Eduard has been claiming this originally: > > > - having this xscreensaver hanging around disturbs the startup of > >another xscreensaver process in the new user session > > I guess he needs to back this up somehow. > Unfortunately I haven't seen any log files or anything, which would give us > the opportunity to retrace what's happening. Not sure which kind of backup you expect. How can I generate more useful logfiles? IMHO I asked before for some kind of tracing functionality to become able to get that information, i.e. to see how systemd is ticking, to see what is happening or how the the delayed SIGTERM is triggered. Those are basically the symptoms I see: my .icewm/startup file at the moment contains: xscreensaver -nosplash -log wtf-xscreensaver.txt & When icewm starts, I see the splash screen for a brief moment (not joking, looks -nosplash has no effect there), but it does not happen every time. And in wtf-xscreensaver.txt I find: xscreensaver: 21:50:06: already running on display :0 (window 0x45) from process 9797 (lightdm@whitestar). Second attempt (and a different PID): When I run "xscreensaver-command -lock" (through ctrl-alt-del dialog of icewm) then the screen gets locked, and pushing a key shows me the credentials prompt for the user called "lightdm". Or, if run ps quick enough before it's killed, I see: user 3904 0.0 0.0 5712 1128 ?SN 21:13 0:00 xscreensaver-systemd -verbose lightdm11997 0.1 0.0 18948 5952 ?Ss 21:55 0:00 xscreensaver lightdm12068 0.0 0.0 5712 1128 ?SN 21:55 0:00 xscreensaver-systemd user 12416 0.0 0.0 3748 664 pts/0S+ 21:56 0:00 grep saver (one of those "xscreensaver-systemd" belongs to an earlier session, this is another complaint of mine in #978589 but it's claimed not to cause the main issue). Best regards, Eduard.
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> reassign 956778 parcellite
Bug #956778 [src:parcellite] parcellite: Depends on deprecated libappindicator
Bug reassigned from package 'src:parcellite' to 'parcellite'.
No longer marked as found in versions parcellite/1.2.1-3.
Ignoring request to alter fixed versions of bug #956778 to the same values
previously set
> forcemerge 909651 956778
Bug #909651 {Done: Thomas Koch } [parcellite] Please enable
AppIndicator support and switch over to Ayatana AppIndicator
Bug #956778 [parcellite] parcellite: Depends on deprecated libappindicator
Severity set to 'normal' from 'serious'
895037 was blocked by: 956765 956771 956777 974146 956778 956770 956761 956775
956767 956768 956782 956780 921339 956779 977156 956764 956766 956773 956772
956781 956769 956774 956776 906026 956762
895037 was blocking: 895038
Removed blocking bug(s) of 895037: 956778
Marked Bug as done
Marked as fixed in versions parcellite/1.2.1-4.
Bug #909651 {Done: Thomas Koch } [parcellite] Please enable
AppIndicator support and switch over to Ayatana AppIndicator
Added tag(s) sid, bullseye, and pending.
Merged 909651 956778
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
895037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895037
909651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909651
956778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979562: lightdm session termination does not stop xscreensaver
> my .icewm/startup file at the moment contains: > > xscreensaver -nosplash -log wtf-xscreensaver.txt & > > When icewm starts, I see the splash screen for a brief moment (not joking, > looks -nosplash has no effect there), but it does not happen every time. This kinda sounds like *something else* is launching xscreensaver at the same time, and whatever that is is doing it without -nosplash. The two of them racing would explain the "already running" error. > Or, if run ps quick enough before it's killed, I see: > > user 3904 0.0 0.0 5712 1128 ?SN 21:13 0:00 > xscreensaver-systemd -verbose > lightdm11997 0.1 0.0 18948 5952 ?Ss 21:55 0:00 > xscreensaver > lightdm12068 0.0 0.0 5712 1128 ?SN 21:55 0:00 > xscreensaver-systemd > user 12416 0.0 0.0 3748 664 pts/0S+ 21:56 0:00 grep saver Note that pid 11997 does not have -nosplash on its command line. -- Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
Bug#979562: lightdm session termination does not stop xscreensaver
Am 11.01.21 um 22:04 schrieb Eduard Bloch: Not sure which kind of backup you expect. Well, you filed a serious bug report against systemd, so I expect at least some kind of justification for that. OpenPGP_signature Description: OpenPGP digital signature
Bug#931003: [Pkg-rust-maintainers] Bug#931003: Removed package(s) from unstable
These packages are not installed by users, so leaving them as FTBFS is not a big deal. If you want to clean it up, please feel free. I can certainly understand if people (e.g. me) want to spend their time doing other things. X Santiago Vila: > On Sun, 8 Sep 2019, Ximin Luo wrote: > >> Santiago Vila: >>> reopen 931003 >>> found 931003 0.2.4-1 >>> fixed 931003 0.2.4-1+rm >>> thanks >>> >>> Hi. >>> >>> This was automatically closed by ftpmaster because the package was >>> removed from unstable, but this still does not fix the FTBFS problem >>> in stable. >>> >>> Thanks. >>> >> >> Please be aware that the Debian Rust team today *does not make any >> effort* towards bugs affecting Debian Stable. [...] > > Not even FTBFS bugs, as it is the case here? > > There are already 74 packages which FTBFS in stable (by my count), it > would be much better if every mantainer cared about their own packages. > I'm curious: does this really sound unreasonable for you? > > Thanks. > > ___ > Pkg-rust-maintainers mailing list > pkg-rust-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers > -- GPG: ed25519/56034877E1F87C35 https://github.com/infinity0/pubkeys.git
Bug#979850: fp-compiler-3.2.0: missing '\' at end of line 67 in postinst script
Package: fp-compiler-3.2.0 Version: 3.2.0+dfsg-9 Severity: grave Justification: renders package unusable Dear maintainer, At upgrade time: Setting up fp-compiler-5.2.0:amd64 (3.2.0+dfsg-9) ... Saved old "fpc-3.2.0.cfg" to "fpc-3.2.0.bak" /var/lib/dpkg/info/fp-compiler-3.2.0:amd64.postinst: 68: --slave: not found dpkg: error processing package fp-compiler-3.2.0:amd64 (--configure): This is because there is a missing '\' ant the end of line 67. Thanks, -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fp-compiler-3.2.0 depends on: ii binutils 2.35.1-7 ii debconf [debconf-2.0] 1.5.74 ii fp-units-rtl-3.2.0 3.2.0+dfsg-9 ii libc6 2.31-9 Versions of packages fp-compiler-3.2.0 recommends: pn fp-utils-3.2.0 Versions of packages fp-compiler-3.2.0 suggests: pn fp-docs-3.2.0 -- debconf information excluded
Bug#979853: fp-compiler-3.2.0: does not install: postinst: line 68: --slave: command not found
Package: fp-compiler-3.2.0 Version: 3.2.0+dfsg-9 Severity: grave Justification: renders package unusable Hi! During postinst the following happens: Setting up fp-compiler-3.2.0:amd64 (3.2.0+dfsg-9) ... Saved old "fpc-3.2.0.cfg" to "fpc-3.2.0.bak" /var/lib/dpkg/info/fp-compiler-3.2.0:amd64.postinst: line 68: --slave: command not found Reason: Line 67 misses the \ at the end for the continuation line to work. Grüße Sven. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (400, 'testing'), (100, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 5.10.0-1-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CPU_OUT_OF_SPEC, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages fp-compiler-3.2.0 depends on: ii binutils 2.35.1-7 ii debconf [debconf-2.0] 1.5.74 ii fp-units-rtl-3.2.0 3.2.0+dfsg-9 ii libc6 2.31-9 Versions of packages fp-compiler-3.2.0 recommends: ii fp-utils-3.2.0 3.2.0+dfsg-9 Versions of packages fp-compiler-3.2.0 suggests: pn fp-docs-3.2.0 -- debconf information excluded
Bug#979573: Acknowledgement (nvidia-driver: Screen freezes since upgrade to 455.45)
Addendum: The fix is to install nvidia-driver 460.27.04-1 No freezes happened since then: system boot 5.10.x Fri Jan 8 15:20 still running Cheers Seegras -- "Those who give up essential liberties for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin "It's also true that those who would give up privacy for security are likely to end up with neither." -- Bruce Schneier
Bug#972298: marked as done (okteta: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath)
Your message dated Mon, 11 Jan 2021 22:55:57 + with message-id and subject line Bug#972298: fixed in okteta 5:0.26.4-2 has caused the Debian Bug report #972298, regarding okteta: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath 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.) -- 972298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972298 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: okteta Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: fixfilepath ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org When the reproducible=+fixfilepath feature is enabled (either through DEB_BUILD_OPTIONS, or using a dpkg that enables this by default), okteta fails to build from source: http://qa-logs.debian.net/2020/09/26.fixfilepath/okteta_0.26.4-1_unstable_fixfilepath.log While the "fixfilepath" feature is not currently enabled by dpkg-buildflags by default, it may become the default at some point in the future, and can by triggered manually by setting DEB_BUILD_OPTIONS=reproducible=+fixfilepath in the build environment. It is also used in the tests.reproducible-builds.org infrastructure when testing unstable and experimental. More information about this issue is available at: https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html I have not identified the exact cause of this issue, but a common trigger is test suites expecting __FILE__ to resolve to an absolute path. The attached patch works around this issue by disabling the fixfilepath feature in debian/rules using DEB_BUILD_MAINT_OPTIONS=-fixfilepath. Thanks for maintaining okteta! live well, vagrant From f31c64a3960214e4b35f0d7b08bdcb53d81de2b3 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Thu, 15 Oct 2020 23:35:14 + Subject: [PATCH] debian/rules: Disable fixfilepath feature, as it triggers build failures when enabled. https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html --- debian/rules | 3 +++ 1 file changed, 3 insertions(+) diff --git a/debian/rules b/debian/rules index c948de6..a5d0afc 100755 --- a/debian/rules +++ b/debian/rules @@ -2,6 +2,9 @@ TESTS_HOME=$(CURDIR)/debian/tests.home +# Disable fixfilepath, as it causes build failures. +export DEB_BUILD_MAINT_OPTIONS = reproducible=-fixfilepath + l10npkgs_firstversion_ok := 4:16.04.3-7~ include /usr/share/pkg-kde-tools/qt-kde-team/2/l10n-packages.mk -- 2.28.0 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: okteta Source-Version: 5:0.26.4-2 Done: Aurélien COUDERC We believe that the bug you reported is fixed in the latest version of okteta, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurélien COUDERC (supplier of updated okteta package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 11 Jan 2021 23:28:57 +0100 Source: okteta Architecture: source Version: 5:0.26.4-2 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Aurélien COUDERC Closes: 972298 Changes: okteta (5:0.26.4-2) unstable; urgency=medium . [ Vagrant Cascadian ] * Disable fixfilepath reproducibility feature, as it triggers build failures when enabled. (Closes: #972298) . [ Aurélien COUDERC ] * Refresh copyright information. * Bump Standards-Version to 4.5.1, no change required. * Refresh upstream metadata. * Update project homepage. * Removed George Kiagiadakis, Maximiliano Curia, Modestas Vainius from the uploaders, thanks for your work on the package! * Added myself to the uploaders. * Build with hardening=+all build hardening flag. * Drop kde-l10n migration rules, not needed anymore after 2 stable releases. Checksums-Sha1: eac29a894b6445af5c534dc61e69f107643ea496 3700 okteta_0.26.4-2.dsc fb3b22b9456448dbb2c9f712da11c6340753c5c7 29968 okteta_0.26.4-2.debian.tar.xz 81b32202423b003c5e3a440394f5254703c2c739 28640 okteta_0.26.4-2_
Bug#979734: closed by Debian FTP Masters (reply to YOKOTA Hiroshi ) (Bug#979734: fixed in calibre 5.9.0+dfsg-2)
Control: reopen -1 Thank you for the very fast fix. python3-crypto is still listed in Depends, though. Cheers On 2021-01-11 15:51:03 +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the src:calibre package: > > #979734: calibre: remove python3-crypto from (Build-)Depends > > It has been closed by Debian FTP Masters > (reply to YOKOTA Hiroshi ). > > 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 YOKOTA Hiroshi > ) by > replying to this email. > > > -- > 979734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979734 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > Date: Mon, 11 Jan 2021 15:48:30 + > From: Debian FTP Masters > To: 979734-cl...@bugs.debian.org > Subject: Bug#979734: fixed in calibre 5.9.0+dfsg-2 > Reply-To: YOKOTA Hiroshi > Message-Id: > > Date: Sun, 10 Jan 2021 23:34:05 +0100 > From: Sebastian Ramacher > To: Debian Bug Tracking System > Subject: calibre: remove python3-crypto from (Build-)Depends > Message-ID: > > Source: calibre > Version: 5.8.1+dfsg+fontFix-1 > Severity: serious > X-Debbugs-Cc: sramac...@debian.org > Control: block 972184 by -1 > Control: block 979318 by -1 > > We will remove python3-crypto from bullseye. It is unmaintained and a > replacement is available via python3-pycryptodome. calibre only uses any > module from python3-crypto in src/calibre/test_build.py to check if is > installed. No other code in calibre uses python3-crypto. So I recommend > to simply remove this check and drop the dependencies. > > Cheers > -- > Sebastian Ramacher -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: Re: Bug#979734 closed by Debian FTP Masters (reply to YOKOTA Hiroshi ) (Bug#979734: fixed in calibre 5.9.0+dfsg-2)
Processing control commands:
> reopen -1
Bug #979734 {Done: YOKOTA Hiroshi } [src:calibre]
calibre: remove python3-crypto from (Build-)Depends
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions calibre/5.9.0+dfsg-2.
--
979734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979734
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979734: closed by Debian FTP Masters (reply to YOKOTA Hiroshi ) (Bug#979734: fixed in calibre 5.9.0+dfsg-2)
> Thank you for the very fast fix. python3-crypto is still listed in > Depends, though. Bummer ... thanks! Norbert -- PREINING Norbert https://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#971216: marked as done (imagemagick: FTBFS: dh_doxygen: error: Doxygen documentation not found)
Your message dated Mon, 11 Jan 2021 23:34:09 + with message-id and subject line Bug#971216: fixed in imagemagick 8:6.9.11.57+dfsg-1 has caused the Debian Bug report #971216, regarding imagemagick: FTBFS: dh_doxygen: error: Doxygen documentation not found 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.) -- 971216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: imagemagick Version: 8:6.9.11.24+dfsg-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # special source imagemagick-*-common > dh_install --package=imagemagick-6-common > install -d debian/imagemagick-6-common// > cp --reflink=auto -a ./debian/tmp-indep/etc/ > debian/imagemagick-6-common/// > install -d debian/imagemagick-6-common//usr/share/ > cp --reflink=auto -a ./debian/tmp-indep/usr/share/ImageMagick-6 > debian/imagemagick-6-common//usr/share// > install -d debian/imagemagick-6-common//usr/share/doc/ > cp --reflink=auto -a > ./debian/prebuilt/usr/share/doc/imagemagick-6-common > debian/imagemagick-6-common//usr/share/doc// > # remaining package > dh_install --indep --remaining-packages --sourcedir=debian/tmp-indep > --autodest > install -d > debian/imagemagick-6-doc//usr/share/doc/imagemagick-6-common/html > cp --reflink=auto -a > debian/tmp-indep/usr/share/doc/imagemagick-6-common/html/images > debian/tmp-indep/usr/share/doc/imagemagick-6-common/html/index.html > debian/tmp-indep/usr/share/doc/imagemagick-6-common/html/www > debian/imagemagick-6-doc//usr/share/doc/imagemagick-6-common/html/ > install -d debian/libmagickcore-6-headers//usr/include/ImageMagick-6 > cp --reflink=auto -a debian/tmp-indep/usr/include/ImageMagick-6/magick > debian/libmagickcore-6-headers//usr/include/ImageMagick-6/ > install -d debian/libmagickwand-6-headers//usr/include/ImageMagick-6 > cp --reflink=auto -a debian/tmp-indep/usr/include/ImageMagick-6/wand > debian/libmagickwand-6-headers//usr/include/ImageMagick-6/ > install -d debian/libmagick\+\+-6-headers//usr/include/ImageMagick-6 > cp --reflink=auto -a > debian/tmp-indep/usr/include/ImageMagick-6/Magick\+\+ > debian/tmp-indep/usr/include/ImageMagick-6/Magick\+\+.h > debian/libmagick\+\+-6-headers//usr/include/ImageMagick-6/ > cp --reflink=auto -a debian/tmp-indep/usr/share/perl5 > debian/libimage-magick-perl//usr/share/ > install -d debian/libimage-magick-perl//usr/share/man/man3 > cp --reflink=auto -a > debian/tmp-indep/usr/share/man/man3/Image::Magick.3pm > debian/libimage-magick-perl//usr/share/man/man3/ > # fix doxygen problem > ./debian/scripts/dh_doxygen --indep --package=imagemagick-6-doc > dh_doxygen: error: Doxygen documentation not found > make[1]: *** [debian/rules:722: override_dh_install-indep] Error 25 The full build log is available from: http://qa-logs.debian.net/2020/09/26/imagemagick_6.9.11.24+dfsg-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: imagemagick Source-Version: 8:6.9.11.57+dfsg-1 Done: Bastien Roucariès We believe that the bug you reported is fixed in the latest version of imagemagick, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastien Roucariès (supplier of updated imagemagick package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 11 Jan 2021 22:14:26 + Source: imagemagick Architecture: source Version: 8:6.9.11.57+dfsg-1 Distribution: unst
Bug#977205: marked as done (imagemagick: CVE-2020-29599)
Your message dated Mon, 11 Jan 2021 23:34:09 + with message-id and subject line Bug#977205: fixed in imagemagick 8:6.9.11.57+dfsg-1 has caused the Debian Bug report #977205, regarding imagemagick: CVE-2020-29599 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.) -- 977205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: imagemagick Version: 8:6.9.11.24+dfsg-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for imagemagick. A very extensive blogpost[1] explains the issue, and note that the provided POC though does only work so far in ImageMagick7 the issue is present as well in legacy ImageMagick 6, affected versions should be around 6.9.8-1 onwards. The required fixes for ImageMagick6 are referenced in the security-tracker. As a side node: For buster the issue is mitigated as the recent DSA included the 200-disable-ghostscript-formats.patch patch and disables ghostscript handled formats. As a hardening measure against those issue it might be ideal to ship the disabling as well in bullseye. CVE-2020-29599[0]: | ImageMagick before 6.9.11-40 and 7.x before 7.0.10-40 mishandles the | -authenticate option, which allows setting a password for password- | protected PDF files. The user-controlled password was not properly | escaped/sanitized and it was therefore possible to inject additional | shell commands via coders/pdf.c. 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-2020-29599 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29599 [1] https://insert-script.blogspot.com/2020/11/imagemagick-shell-injection-via-pdf.html Regards, Salvatore -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-rc6-amd64 (SMP w/8 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: imagemagick Source-Version: 8:6.9.11.57+dfsg-1 Done: Bastien Roucariès We believe that the bug you reported is fixed in the latest version of imagemagick, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastien Roucariès (supplier of updated imagemagick package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 11 Jan 2021 22:14:26 + Source: imagemagick Architecture: source Version: 8:6.9.11.57+dfsg-1 Distribution: unstable Urgency: medium Maintainer: ImageMagick Packaging Team Changed-By: Bastien Roucariès Closes: 971216 972797 977205 Changes: imagemagick (8:6.9.11.57+dfsg-1) unstable; urgency=medium . * New upstream version: - Bug fix: "CVE-2020-29599", imagemagick mishandles the -authenticate option, which allows setting a password for password-protected PDF files. The user-controlled password was not properly escaped/sanitized and it was therefore possible to inject additional shell commands via coders/pdf.c. Thanks to Salvatore Bonaccorso (Closes: #977205). - Bug fix: "CVE-2020-27560: Division by Zero in function OptimizeLayerFrames", thanks to Salvatore Bonaccorso (Closes: #972797). * Fix dh_doxygen FTBFS (Closes: #971216) Checksums-Sha1: 98043226f8d2a24a7f1057380adb9c6867cf54ed 5079 imagemagick_6.9.11.57+dfsg-1.dsc 8420160075e75cde28a09a0b9b7cff725cee9db9 9392580 imagemagick_6.9.11.57+dfsg.orig.tar.xz abbd21d51c0d56aceb902c602c0fc0cf477603e6 245888 imagemagick_6.9.11.57+dfsg-1.debian.tar.xz 944dad89fa48f440ea2391cfd5f9afc1b2b613c3 11973 imagemagick_6.9.11.57+dfsg-1_source.buildinfo Checksums-Sha256: df60159c4f67c2
Bug#978358: marked as done (transmission-remote-gtk: FTBFS: error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.19 but the autoconf macros are from gettext version 0.
Your message dated Mon, 11 Jan 2021 23:35:47 +
with message-id
and subject line Bug#978358: fixed in transmission-remote-gtk 1.4.1-5
has caused the Debian Bug report #978358,
regarding transmission-remote-gtk: FTBFS: error: gettext infrastructure
mismatch: using a Makefile.in.in from gettext version 0.19 but the autoconf
macros are from gettext version 0.20
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.)
--
978358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978358
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: transmission-remote-gtk
Version: 1.4.1-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/<>/po'
> sed -e '/^#/d' remove-potcdate.sin > t-remove-potcdate.sed
> mv t-remove-potcdate.sed remove-potcdate.sed
> package_gnu=""; \
> test -n "$package_gnu" || { \
> if { if (LC_ALL=C find --version) 2>/dev/null | grep GNU >/dev/null; then \
>LC_ALL=C find -L .. -maxdepth 1 -type f \
> -size -1000c -exec grep 'GNU
> transmission-remote-gtk' \
> /dev/null '{}' ';' 2>/dev/null; \
>else \
>LC_ALL=C grep 'GNU transmission-remote-gtk' ../* 2>/dev/null; \
>fi; \
> } | grep -v 'libtool:' >/dev/null; then \
> package_gnu=yes; \
>else \
> package_gnu=no; \
>fi; \
> }; \
> if test "$package_gnu" = "yes"; then \
> package_prefix='GNU '; \
> else \
> package_prefix=''; \
> fi; \
> if test -n '' || test
> 'https://github.com/transmission-remote-gtk/transmission-remote-gtk/issues' =
> '@'PACKAGE_BUGREPORT'@'; then \
> msgid_bugs_address=''; \
> else \
>
> msgid_bugs_address='https://github.com/transmission-remote-gtk/transmission-remote-gtk/issues';
> \
> fi; \
> case `/usr/bin/xgettext --version | sed 1q | sed -e 's,^[^0-9]*,,'` in \
> '' | 0.[0-9] | 0.[0-9].* | 0.1[0-5] | 0.1[0-5].* | 0.16 | 0.16.[0-1]*) \
> /usr/bin/xgettext --default-domain=transmission-remote-gtk --directory=..
> \
> --add-comments=TRANSLATORS: --from-code=UTF-8 --keyword=_ --keyword=N_
> --keyword=C_:1c,2 --keyword=NC_:1c,2 --keyword=g_dngettext:2,3 --add-comments
> \
> --files-from=./POTFILES.in \
> --copyright-holder='' \
> --msgid-bugs-address="$msgid_bugs_address" \
> ;; \
> *) \
> /usr/bin/xgettext --default-domain=transmission-remote-gtk --directory=..
> \
> --add-comments=TRANSLATORS: --from-code=UTF-8 --keyword=_ --keyword=N_
> --keyword=C_:1c,2 --keyword=NC_:1c,2 --keyword=g_dngettext:2,3 --add-comments
> \
> --files-from=./POTFILES.in \
> --copyright-holder='' \
> --package-name="${package_prefix}transmission-remote-gtk" \
> --package-version='1.4.1' \
> --msgid-bugs-address="$msgid_bugs_address" \
> ;; \
> esac
> /usr/bin/xgettext: warning: a fallback ITS rule file
> '/usr/share/gettext-0.21/its/metainfo.its' is used; it may not be in sync
> with the upstream
> test ! -f transmission-remote-gtk.po || { \
> if test -f ./transmission-remote-gtk.pot-header; then \
> sed -e '1,/^#$/d' < transmission-remote-gtk.po >
> transmission-remote-gtk.1po && \
> cat ./transmission-remote-gtk.pot-header transmission-remote-gtk.1po >
> transmission-remote-gtk.po; \
> rm -f transmission-remote-gtk.1po; \
> fi; \
> if test -f ./transmission-remote-gtk.pot; then \
> sed -f remove-potcdate.sed < ./transmission-remote-gtk.pot >
> transmission-remote-gtk.1po && \
> sed -f remove-potcdate.sed < transmission-remote-gtk.po >
> transmission-remote-gtk.2po && \
> if cmp transmission-remote-gtk.1po transmission-remote-gtk.2po >/dev/null
> 2>&1; then \
> rm -f transmission-remote-gtk.1po transmission-remote-gtk.2po
> transmission-remote-gtk.po; \
> else \
> rm -f transmission-remote-gtk.1po transmission-remote-gtk.2po
> ./transmission-remote-gtk.pot && \
> mv transmission-remote-gtk.po ./transmission-remote-gtk.pot; \
> fi; \
> else \
> mv transmission-remote-gtk.po ./transmission-remote-gtk.pot; \
> fi; \
> }
> make[4]: Leaving directory '/<>/po'
> *** error: gettext infrastructure mismatch: using a Makefile.in.in from
> gettext version 0.19 but the autoconf macros are from gettext version 0.20
> make[3]: *** [Makefile:265: stamp-po] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/12/26/transmission-remote-gtk_1.4.1
Bug#979063: php-font-lib: Useless in Debian
On Saturday, 2 January 2021 11:39:12 PM AEDT Markus Frosch wrote: > Similar to php-dompdf [1], this package is pretty useless for bullseye, > since it is only needed by php-dompdf, which is not depent on by any > package in testing. > > Only possible candidate would be civicrm [2], which seems not be able to > make it to bullseye. I took care of CiviCRM and I might adopt php-dompdf (and reluctantly php- font-lib) as I intend to continue to look after CiviCRM... -- Regards, Dmitry Smirnov GPG key : 4096R/52B6BBD953968D1B --- Censorship is always cause for celebration. It is always an opportunity because it reveals fear of reform. It means that the power position is so weak that you have got to care what people think. -- Julian Assange --- Covid: The Big Picture in 7 Charts https://swprs.org/covid-the-big-picture-in-7-charts/ signature.asc Description: This is a digitally signed message part.
Bug#975817: marked as pending in mom
Control: tag -1 pending Hello, Bug #975817 in mom 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/mom/-/commit/acf3d8596c145a3d3c9fc554df49fe27f82253b7 New patch for compatibility with Python-3.9 (Closes: #975817) Thanks, Adrian Bunk. (this message was generated automatically) -- Greetings https://bugs.debian.org/975817
Processed: Bug#975817 marked as pending in mom
Processing control commands: > tag -1 pending Bug #975817 [src:mom] mom: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 Added tag(s) pending. -- 975817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:wolfssl
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:wolfssl > # 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 #979534 (http://bugs.debian.org/979534) > # Bug title: wolfssl: CVE-2020-36177 > # * https://github.com/wolfSSL/wolfssl/pull/3426 > # * remote status changed: (?) -> closed > # * closed upstream > tags 979534 + fixed-upstream Bug #979534 [src:wolfssl] wolfssl: CVE-2020-36177 Added tag(s) fixed-upstream. > usertags 979534 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 979534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979823: catch2: diff for NMU version 2.13.4-1.1
On Mon, Jan 11, 2021 at 07:27:24PM +0100, Tobias Frost wrote: Dear maintainer, Hi Tobias, I've prepared an NMU for catch2 (versioned as 2.13.4-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Thanks for fixing this! However I noticed a bug in version 2.13.4-1 and I am preparing a new upload. We can keep the NMU, but the new upload will render it moot. Cheers, -- Mathieu Mirmont signature.asc Description: PGP signature
