Bug#1021524: lomiri-system-settings is not installable
Hi Adrian, On Mo 10 Okt 2022 04:49:47 CEST, Adrian Bunk wrote: Package: lomiri-system-settings Version: 1.0~git20221004.572f3a9-1 Severity: serious The following packages have unmet dependencies: lomiri-system-settings : Depends: lomiri-keyboard-data but it is not installable Depends: ubports-wallpapers but it is not installable thanks for reporting this. lomiri-keyboard-data will come, but I could actually comment it out as we don't provide the language plugin in Debian, yet. Regarding ubports-wallpapers, we might have to rename stuff upstream (ubports-wallpapers -> lomiri-wallpapers). Will discuss it with the UBports team. Greets, Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpurAxojtEjW.pgp Description: Digitale PGP-Signatur
Bug#1016248: marked as done (content-hub: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Mon, 10 Oct 2022 05:33:59 + with message-id and subject line Bug#1016248: fixed in content-hub 1.0.0-5 has caused the Debian Bug report #1016248, regarding content-hub: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1016248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: content-hub Version: 1.0.0-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220728 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-gensymbols: error: some new symbols appeared in the symbols file: see > diff output below > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libcontent-hub1/DEBIAN/symbols doesn't match > completely debian/libcontent-hub1.symbols > --- debian/libcontent-hub1.symbols (libcontent-hub1_1.0.0-4_amd64) > +++ dpkg-gensymbolsupdZbz 2022-07-29 09:06:22.915431250 + > @@ -1,6 +1,6 @@ > libcontent-hub.so.1 libcontent-hub1 #MINVER# > * Build-Depends-Package: libcontent-hub-dev > - > (optional=templinst)_Z10qdbus_castIN3com6lomiri7content4PeerEET_RK8QVariantPS4_@Base > 1.0.0 > +#MISSING: 1.0.0-4# > (optional=templinst)_Z10qdbus_castIN3com6lomiri7content4PeerEET_RK8QVariantPS4_@Base > 1.0.0 > _Z13action_acceptP19_NotifyNotificationPcPv@Base 1.0.0 > _Z14action_dismissP19_NotifyNotificationPcPv@Base 1.0.0 > _Z15setLoggingLeveli@Base 1.0.0 > @@ -292,7 +292,7 @@ > > _ZN3com6lomiri7content5Paste7Private11qt_metacallEN11QMetaObject4CallEiPPv@Base > 1.0.0 > _ZN3com6lomiri7content5Paste7Private11qt_metacastEPKc@Base 1.0.0 > _ZN3com6lomiri7content5Paste7Private16staticMetaObjectE@Base 1.0.0 > - _ZN3com6lomiri7content5Paste7Private8mimeDataEv@Base 1.0.0 > +#MISSING: 1.0.0-4# _ZN3com6lomiri7content5Paste7Private8mimeDataEv@Base 1.0.0 > _ZN3com6lomiri7content5Paste7PrivateD0Ev@Base 1.0.0 > _ZN3com6lomiri7content5Paste7PrivateD1Ev@Base 1.0.0 > _ZN3com6lomiri7content5Paste7PrivateD2Ev@Base 1.0.0 > @@ -443,16 +443,16 @@ > _ZN3com6lomiri7content8Transfer5abortEv@Base 1.0.0 > _ZN3com6lomiri7content8Transfer5startEv@Base 1.0.0 > _ZN3com6lomiri7content8Transfer6chargeERK7QVectorINS1_4ItemEE@Base 1.0.0 > - _ZN3com6lomiri7content8Transfer7Private10downloadIdEv@Base 1.0.0 > +#MISSING: 1.0.0-4# > _ZN3com6lomiri7content8Transfer7Private10downloadIdEv@Base 1.0.0 > > _ZN3com6lomiri7content8Transfer7Private11qt_metacallEN11QMetaObject4CallEiPPv@Base > 1.0.0 > _ZN3com6lomiri7content8Transfer7Private11qt_metacastEPKc@Base 1.0.0 > > _ZN3com6lomiri7content8Transfer7Private13make_transferERK15QDBusObjectPathP7QObject@Base > 1.0.0 > - _ZN3com6lomiri7content8Transfer7Private14selection_typeEv@Base 1.0.0 > +#MISSING: 1.0.0-4# > _ZN3com6lomiri7content8Transfer7Private14selection_typeEv@Base 1.0.0 > _ZN3com6lomiri7content8Transfer7Private16staticMetaObjectE@Base 1.0.0 > - _ZN3com6lomiri7content8Transfer7Private5stateEv@Base 1.0.0 > +#MISSING: 1.0.0-4# _ZN3com6lomiri7content8Transfer7Private5stateEv@Base 1.0.0 > _ZN3com6lomiri7content8Transfer7Private6chargeERK7QVectorINS1_4ItemEE@Base > 1.0.0 > _ZN3com6lomiri7content8Transfer7Private7collectEv@Base 1.0.0 > - _ZN3com6lomiri7content8Transfer7Private9directionEv@Base 1.0.0 > +#MISSING: 1.0.0-4# _ZN3com6lomiri7content8Transfer7Private9directionEv@Base > 1.0.0 > _ZN3com6lomiri7content8Transfer7PrivateD0Ev@Base 1.0.0 > _ZN3com6lomiri7content8Transfer7PrivateD1Ev@Base 1.0.0 > _ZN3com6lomiri7content8Transfer7PrivateD2Ev@Base 1.0.0 > @@ -599,6 +599,7 @@ > _ZNSt14_Function_baseD2Ev@Base 1.0.0 > > (optional=templinst|arch=!amd64)_ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE10_M_releaseEv@Base > 1.0.0 > > (optional=templinst|arch=amd64)_ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE10_M_releaseEv@Base > 1.0.0 > + > _ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE24_M_release_last_use_coldEv@Base > 1.0.0-4 > > (optional=templinst)_ZNSt3mapISt4pairIN3com6lomiri7content5ScopeENS3_4TypeEEPNS3_5StoreESt4lessIS6_ESaIS0_IKS6_S8_EEED1Ev@Base > 1.0.0 > > (optional=templinst)_ZNSt3mapISt4pairIN3com6lomiri7content5ScopeENS3_4TypeEEPNS3_5StoreESt4lessIS6_ESaIS0_IKS6_S8_EEED2Ev@Base > 1.0.0 > >
Processed: Bug#1016248 marked as pending in content-hub
Processing control commands: > tag -1 pending Bug #1016248 [src:content-hub] content-hub: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below Added tag(s) pending. -- 1016248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016248: marked as pending in content-hub
Control: tag -1 pending Hello, Bug #1016248 in content-hub 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/ubports-team/content-hub/-/commit/b4fad56d8242ba8e350d9752eed192331f6844ac Update symbols due to gcc-12. (CloseS: #1016248) (this message was generated automatically) -- Greetings https://bugs.debian.org/1016248
Bug#1021524: lomiri-system-settings is not installable
Package: lomiri-system-settings Version: 1.0~git20221004.572f3a9-1 Severity: serious The following packages have unmet dependencies: lomiri-system-settings : Depends: lomiri-keyboard-data but it is not installable Depends: ubports-wallpapers but it is not installable
Processed: retitle 1020010 to cvc4 FTBFS with bash 5.2
Processing commands for cont...@bugs.debian.org:
> retitle 1020010 cvc4 FTBFS with bash 5.2
Bug #1020010 [src:cvc4] cvc4: FTBFS: expr_template.h:0: error: undefined
replacement ${getConst_instantiations}
Changed Bug title to 'cvc4 FTBFS with bash 5.2' from 'cvc4: FTBFS:
expr_template.h:0: error: undefined replacement ${getConst_instantiations}'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1020010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1013554: golang-github-valyala-tcplisten: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/valyala/tcplisten returned exit code 1
Processing control commands: > tags -1 + pending Bug #1013554 [src:golang-github-valyala-tcplisten] golang-github-valyala-tcplisten: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/valyala/tcplisten returned exit code 1 Added tag(s) pending. -- 1013554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013554 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013554: golang-github-valyala-tcplisten: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/valyala/tcplisten returned exit code 1
Control: tags -1 + pending Hi Marco, On Sat, 2022-10-08 at 04:53 +0200, Marco d'Itri wrote: > On Jul 30, Mathias Gibbens wrote: > > > Feel free to apply it directly yourself. :) If this does fix the > > issue, it would probably be good to contact Lucas and see if we can > > figure out what in the rebuild setup needs to be tweaked to ensure > > that "ip6-localhost" is properly resolvable. > This bug has been inactive for over two months: do you need any help? > It is keeping cfrpki out of testing. I had left it in Aloïs' hands, but I also know he's been pretty busy. I hadn't looked at the build-rdeps for this package, but see there are several. So, I've pushed my proposed patch to the salsa repo along with a few other small cleanups. It's ready for an upload to unstable after a `dch -r` and `git tag`. My gpg key should be included in the DD uploaders keyring after this month's update, at which point I will upload the package myself, or if either you or Aloïs want to you can upload it sooner. Mathias signature.asc Description: This is a digitally signed message part
Bug#1002083: marked as done (ruby-rufus-scheduler: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(job.last_work_time).to be < 0.0999)
Your message dated Mon, 10 Oct 2022 00:19:26 + with message-id and subject line Bug#1002083: fixed in ruby-rufus-scheduler 3.8.2-1 has caused the Debian Bug report #1002083, regarding ruby-rufus-scheduler: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(job.last_work_time).to be < 0.0999 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.) -- 1002083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-rufus-scheduler Version: 3.8.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Failure/Error: expect(job.last_work_time).to be < 0.0999 > >expected: < 0.0999 > got: 0.10008716583251953 > # ./spec/job_spec.rb:765:in `block (4 levels) in ' > > Finished in 7 minutes 14 seconds (files took 0.19873 seconds to load) > 308 examples, 1 failure, 2 pending > > Failed examples: > > rspec ./spec/job_spec.rb:753 # Rufus::Scheduler::Job work time > #mean_work_time gathers work times and computes the mean > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2021/12/20/ruby-rufus-scheduler_3.8.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: ruby-rufus-scheduler Source-Version: 3.8.2-1 Done: Cédric Boutillier We believe that the bug you reported is fixed in the latest version of ruby-rufus-scheduler, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1002...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cédric Boutillier (supplier of updated ruby-rufus-scheduler 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, 10 Oct 2022 01:23:11 +0200 Source: ruby-rufus-scheduler Architecture: source Version: 3.8.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Cédric Boutillier Closes: 1002083 Changes: ruby-rufus-scheduler (3.8.2-1) unstable; urgency=medium . * Team upload * New upstream version 3.8.2 + tests measuring average work time less strict (Closes: #1002083) * Bump Standards-Version to 4.6.1 (no changes needed) * Drop Modernize-spec-job_spec.rb.patch and Harden-tests.patch, applied upstream Checksums-Sha1: ae93c417187b2528323700ff9bdd6e7051ff7a6f 1561 ruby-rufus-scheduler_3.8.2-1.dsc 53c77bdd067faa7fd533a668ea86798b45203e92 65017 ruby-rufus-scheduler_3.8.2.orig.tar.gz 65b5def8301a26800749f872e9b84d1771c8cbfa 3632 ruby-rufus-scheduler_3.8.2-1.debian.tar.xz 76c7b167d4f95012c08b6e1f99fb1e2fed61bdc7 9427 ruby-rufus-scheduler_3.8.2-1_amd64.buildinfo Checksums-Sha256: 87d155af2fdb72bfb6aa6bc35100e5b1abe3f8203b5e08595772b1b0161f 1561 ruby-rufus-scheduler_3.8.2-1.dsc 65b46a7f3b34b11a9ef7e4868a32d3f4b8a256b8e9df193a5b6cc20240f29550 65017 ruby-rufus-scheduler_3.8.2.orig.tar.gz c4d2fac73d0ebbd62bbf3a75ff7109eaa7add3d8b94b49c8eb5b6740e3a3835a 3632 ruby-rufus-scheduler_3.8.2-1.debian.tar.xz 3083f4e5b72d065612a0b69f9b69086f813552f5405db4ad7b16a8cea218abbb 9427 ruby-rufus-scheduler_3.8.2-1_amd64.buildinfo Files: 413a2b05bf259fec05e1306352d27206 1561 ruby optional ruby-rufus-scheduler_3.8.2-1.dsc 636f0f736e7f49ddf5ac8054347069d1 65017 ruby
Bug#1021448: marked as done (apt-venv: autopkgtest regression: output on stderr)
Your message dated Mon, 10 Oct 2022 00:03:54 + with message-id and subject line Bug#1021441: fixed in apt-venv 1.0.0-5 has caused the Debian Bug report #1021441, regarding apt-venv: autopkgtest regression: output on stderr 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.) -- 1021441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apt-venv Version: 1.0.0-4 Severity: serious Dear maintainer, A recent upload of apt-venv introduced CI tests that fail over some architectures. See below an example for arm64. [...] Ign:37 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse arm64 Packages Err:19 http://archive.ubuntu.com/ubuntu jammy/main arm64 Packages 404 Not Found [IP: 185.125.190.36 80] Ign:21 http://archive.ubuntu.com/ubuntu jammy/universe arm64 Packages Ign:23 http://archive.ubuntu.com/ubuntu jammy/restricted arm64 Packages Ign:25 http://archive.ubuntu.com/ubuntu jammy/multiverse arm64 Packages Err:31 http://archive.ubuntu.com/ubuntu jammy-updates/main arm64 Packages 404 Not Found [IP: 185.125.190.36 80] Ign:33 http://archive.ubuntu.com/ubuntu jammy-updates/universe arm64 Packages Ign:35 http://archive.ubuntu.com/ubuntu jammy-updates/restricted arm64 Packages Ign:37 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse arm64 Packages Fetched 27.4 MB in 10s (2692 kB/s) Reading package lists... E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Some index files failed to download. They have been ignored, or old ones used instead. Welcome to apt virtual environment for jammy release. All the configuration is available in /home/debci/.config/apt-venv/jammy You may want run first "apt-get update" autopkgtest [11:14:36]: test apt-cache-update.sh: ---] autopkgtest [11:14:36]: test apt-cache-update.sh: - - - - - - - - - - results - - - - - - - - - - apt-cache-update.sh FAIL stderr: E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] autopkgtest [11:14:36]: test apt-cache-update.sh: - - - - - - - - - - stderr - - - - - - - - - - E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Some index files failed to download. They have been ignored, or old ones used instead. E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.38 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.38 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.38 80] E: Some index files failed to download. They have been ignored, or old ones used instead. E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/focal-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Some index files failed to download. They have been ignored, or old ones used instead. E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Some index files failed to download. They have been ignored, or old ones used instead. --- End Message ---
Bug#1021441: marked as done (apt-venv: autopkgtest regression: output on stderr)
Your message dated Mon, 10 Oct 2022 00:03:54 + with message-id and subject line Bug#1021441: fixed in apt-venv 1.0.0-5 has caused the Debian Bug report #1021441, regarding apt-venv: autopkgtest regression: output on stderr 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.) -- 1021441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apt-venv Version: 1.0.0-4 Severity: serious X-Debbugs-Cc: Braulio Henrique Marques Souto Dear maintainer, A recent upload of apt-venv introduced CI tests that fail over some architectures. See below an example for arm64. [...] Ign:37 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse arm64 Packages Err:19 http://archive.ubuntu.com/ubuntu jammy/main arm64 Packages 404 Not Found [IP: 185.125.190.36 80] Ign:21 http://archive.ubuntu.com/ubuntu jammy/universe arm64 Packages Ign:23 http://archive.ubuntu.com/ubuntu jammy/restricted arm64 Packages Ign:25 http://archive.ubuntu.com/ubuntu jammy/multiverse arm64 Packages Err:31 http://archive.ubuntu.com/ubuntu jammy-updates/main arm64 Packages 404 Not Found [IP: 185.125.190.36 80] Ign:33 http://archive.ubuntu.com/ubuntu jammy-updates/universe arm64 Packages Ign:35 http://archive.ubuntu.com/ubuntu jammy-updates/restricted arm64 Packages Ign:37 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse arm64 Packages Fetched 27.4 MB in 10s (2692 kB/s) Reading package lists... E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Some index files failed to download. They have been ignored, or old ones used instead. Welcome to apt virtual environment for jammy release. All the configuration is available in /home/debci/.config/apt-venv/jammy You may want run first "apt-get update" autopkgtest [11:14:36]: test apt-cache-update.sh: ---] autopkgtest [11:14:36]: test apt-cache-update.sh: - - - - - - - - - - results - - - - - - - - - - apt-cache-update.sh FAIL stderr: E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] autopkgtest [11:14:36]: test apt-cache-update.sh: - - - - - - - - - - stderr - - - - - - - - - - E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Some index files failed to download. They have been ignored, or old ones used instead. E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.38 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.38 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.38 80] E: Some index files failed to download. They have been ignored, or old ones used instead. E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/focal-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Some index files failed to download. They have been ignored, or old ones used instead. E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Some index files failed to download. They have been ignored,
Bug#1021445: marked as done (apt-venv: autopkgtest regression: output on stderr)
Your message dated Mon, 10 Oct 2022 00:03:54 + with message-id and subject line Bug#1021441: fixed in apt-venv 1.0.0-5 has caused the Debian Bug report #1021441, regarding apt-venv: autopkgtest regression: output on stderr 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.) -- 1021441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apt-venv Version: 1.0.0-4 Severity: serious X-Debbugs-Cc: Braulio Henrique Marques Souto Dear maintainer, A recent upload of apt-venv introduced CI tests that fail over some architectures. See below an example for arm64. [...] Ign:37 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse arm64 Packages Err:19 http://archive.ubuntu.com/ubuntu jammy/main arm64 Packages 404 Not Found [IP: 185.125.190.36 80] Ign:21 http://archive.ubuntu.com/ubuntu jammy/universe arm64 Packages Ign:23 http://archive.ubuntu.com/ubuntu jammy/restricted arm64 Packages Ign:25 http://archive.ubuntu.com/ubuntu jammy/multiverse arm64 Packages Err:31 http://archive.ubuntu.com/ubuntu jammy-updates/main arm64 Packages 404 Not Found [IP: 185.125.190.36 80] Ign:33 http://archive.ubuntu.com/ubuntu jammy-updates/universe arm64 Packages Ign:35 http://archive.ubuntu.com/ubuntu jammy-updates/restricted arm64 Packages Ign:37 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse arm64 Packages Fetched 27.4 MB in 10s (2692 kB/s) Reading package lists... E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Some index files failed to download. They have been ignored, or old ones used instead. Welcome to apt virtual environment for jammy release. All the configuration is available in /home/debci/.config/apt-venv/jammy You may want run first "apt-get update" autopkgtest [11:14:36]: test apt-cache-update.sh: ---] autopkgtest [11:14:36]: test apt-cache-update.sh: - - - - - - - - - - results - - - - - - - - - - apt-cache-update.sh FAIL stderr: E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] autopkgtest [11:14:36]: test apt-cache-update.sh: - - - - - - - - - - stderr - - - - - - - - - - E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Some index files failed to download. They have been ignored, or old ones used instead. E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.38 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.38 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.38 80] E: Some index files failed to download. They have been ignored, or old ones used instead. E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/focal-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.39 80] E: Some index files failed to download. They have been ignored, or old ones used instead. E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Some index files failed to download. They have been ignored,
Bug#975490: u-boot-sunxi: A64-Olinuxino-eMMC boot stuck at "Starting kernel ..."
Hi, I followed https://wiki.debian.org/InstallingDebianOn/Allwinner#Installing_from_an_SD_card_image using the daily build of the unstable netboot installer from https://d-i.debian.org/daily-images/arm64/20221009-02:38/netboot/SD-card-images/ and I was able to install successfully but the system does not boot - it tries to boot from eMMC actually: U-Boot SPL 2020.04+olimex-2-20210111.165338 (Jan 30 2020 - 11:10:18 +) DRAM: 2048 MiB Trying to boot from MMC2 NOTICE: BL31: v2.2(debug):v2.2-8-g51ce3c6-dirty NOTICE: BL31: Built : 19:42:23, Mar 20 2020 NOTICE: BL31: Detected Allwinner A64/H64/R18 SoC (1689) NOTICE: BL31: Found U-Boot DTB at 0x40ab7d8, model: Olimex A64-Olinuxino-eMMC INFO:ARM GICv2 driver initialized INFO:Configuring SPC Controller NOTICE: BL31: PMIC: Detected AXP803 on RSB. INFO:PMIC: AXP803: Enabling DRIVEVBUS INFO:PMIC: AXP803: dcdc1 voltage: 3.300V INFO:PMIC: AXP803: dcdc5 voltage: 1.360V INFO:PMIC: AXP803: dcdc6 voltage: 1.100V INFO:PMIC: AXP803: dldo1 voltage: 3.300V INFO:PMIC: AXP803: dldo4 voltage: 3.300V INFO:BL31: Platform setup done INFO:BL31: Initializing runtime services INFO:BL31: cortex_a53: CPU workaround for 843419 was applied INFO:BL31: cortex_a53: CPU workaround for 855873 was applied INFO:BL31: Preparing for EL3 exit to normal world INFO:Entry point address = 0x4a00 INFO:SPSR = 0x3c9 U-Boot 2020.04+olimex-2-20210111.165338 (Jan 30 2020 - 11:10:18 +) Allwinner Technology CPU: Allwinner A64 (SUN50I) Model: Olimex A64-Olinuxino-eMMC DRAM: 2 GiB MMC: mmc@1c0f000: 0, mmc@1c11000: 1 Loading Environment from EXT4... ** File not found /uboot.env ** ** Unable to read "/uboot.env" from mmc0:1 ** In:serial Out: serial Err: serial Allwinner mUSB OTG (Peripheral) Net: phy interface7 eth0: ethernet@1c3 Warning: usb_ether using MAC address from ROM , eth1: usb_ether starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1b400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1b000 for devices... 1 USB Device(s) found scanning bus usb@1c1b400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 2904 bytes read in 1 ms (2.8 MiB/s) ## Executing script at 4fc0 30797760 bytes read in 1340 ms (21.9 MiB/s) 29408 bytes read in 3 ms (9.3 MiB/s) 32463063 bytes read in 1412 ms (21.9 MiB/s) Booting Debian 5.19.0-2-arm64 from mmc 0:1... ## Flattened Device Tree blob at 4fa0 Booting using the fdt blob at 0x4fa0 Loading Ramdisk to 4810a000, end 49fff8d7 ... OK Loading Device Tree to 480ff000, end 481092df ... OK Starting kernel ... [I didn't use the exact same board as the reporter but the industrial variant of that board - I don't see any reason why they should behave differently in that regard.] When I tried to install u-boot again from an chroot, I got (/dev/sda is the SDCARD and I needed to install u-boot-sunxi): $ sudo systemd-nspawn -q -E DEBIAN_FRONTEND=noninteractive -E LANG=C -E LC_ALL=C -D /PATH/WHERE/I/MOUNTED/THE/SDCARD --bind=/dev/sda -E TARGET=/usr/lib/u-boot/a64-olinuxino-emmc/ u-boot-install-sunxi64 /dev/sda /usr/bin/u-boot-install-sunxi64: device/image (/dev/sda) uses GPT partition table, unusable on sunxi64 fdisk gives me: Disk /dev/sda: 14,72 GiB, 15804137472 bytes, 30867456 sectors Disk model: STORAGE DEVICE Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: SOME-UUID DeviceStart End Sectors Size Type /dev/sda1 2048 999423 997376 487M Linux filesystem /dev/sda2999424 28866559 27867136 13,3G Linux filesystem /dev/sda3 28866560 30865407 1998848 976M Linux swap To me it seems the debian-installer (or is it flash-kernel-installer?) is doing something wrong here ... Might be related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000313 I'm happy to debug further, but I'm lost. Best, Philip OpenPGP_signature Description: OpenPGP digital signature
Processed: affects 1021117
Processing commands for cont...@bugs.debian.org: > affects 1021117 src:opencl-clang-15 Bug #1021117 [llvm-15-dev] llvm-15-dev: cmake fails on missing /usr/lib/llvm-15/bin/mlir-tblgen Added indication that 1021117 affects src:opencl-clang-15 > thanks Stopping processing here. Please contact me if you need assistance. -- 1021117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1021506 is serious
Processing commands for cont...@bugs.debian.org: > severity 1021506 serious Bug #1021506 [binutils-common] binutils-common: not co-installable due to differing content of /usr/share/man/man1/ld.gold.1.gz Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1021506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021506 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999114: marked as done (xwrits: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Sun, 09 Oct 2022 21:19:45 + with message-id and subject line Bug#999114: fixed in xwrits 2.26-1 has caused the Debian Bug report #999114, regarding xwrits: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 999114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xwrits Version: 2.21-6.1 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: xwrits Source-Version: 2.26-1 Done: Barak A. Pearlmutter We believe that the bug you reported is fixed in the latest version of xwrits, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barak A. Pearlmutter (supplier of updated xwrits package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 09 Oct 2022 21:37:12 +0100 Source: xwrits Architecture: source Version: 2.26-1 Distribution: unstable Urgency: medium Maintainer: Barak A. Pearlmutter Changed-By: Barak A. Pearlmutter Closes: 503134 999114 1012001 Changes: xwrits (2.26-1) unstable; urgency=medium . * Use secure URI in debian/watch. * Use secure URI in Homepage field. * Bump debhelper from deprecated 7 to 13 and update scripts (closes: #999114) * Update watch file format version to 4. * New upstream version (closes: #503134) * Forward port, quiltify, and modularize patches * Bump policy * Rules do not require root * Adopt package (closes: #1012001) * Set up packaging repo on salsa Checksums-Sha1: dbb26938153b53a6ea5affe9638830f8a0394477 1912 xwrits_2.26-1.dsc b9d8fde90e6c96a80baea6c76de92da1473d1586 159360 xwrits_2.26.orig.tar.xz e8000770741c6695e3ac11ef780d57314189a92d 4596 xwrits_2.26-1.debian.tar.xz 6749487bbe6fcfaa305ccc1286e05ea1ba553175 7249 xwrits_2.26-1_source.buildinfo Checksums-Sha256: ac8ceaea57eb3dc8c30e492f43e20c434772c37569f8ea7a0c13b1c73a2b0680 1912 xwrits_2.26-1.dsc fc991d990a645166fff4cfaec83eee5046739a0d58fb7f6cc065390d3899a6a0 159360 xwrits_2.26.orig.tar.xz 0b5f9045a0fa6d7b4f56bbef1c7e8c01c7944d4d928ebe7b1a78cac4b36eb041 4596 xwrits_2.26-1.debian.tar.xz d55ee8168ca4a009567a681e6a9c04b8d0ce9af35a2d47001be44e2a84778e15 7249 xwrits_2.26-1_source.buildinfo Files: 737d5268faa79858974de079fffb9f00 1912 x11 optional xwrits_2.26-1.dsc b9b468f723ed1b3cd1b79d38463e70ca 159360 x11 optional xwrits_2.26.orig.tar.xz 9d025d1b215678bb1e90c4bbf33daf9e 4596 x11 optional xwrits_2.26-1.debian.tar.xz d6ec746976e08840ca22416c7079580a 7249 x11 optional xwrits_2.26-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEE+nZaz+JE7Dn2AefCmesepNIze4gFAmNDMtUPHGJhcEBkZWJp YW4ub3JnAAoJEJnrHqTSM3uIhHgQAMuvBJ+8QwyTAk1LEziGxSEGAzkXQvUZXVCN wB0iBBTwF96WB3clKQfp1q/TebfNW/txXGmbMM1Qq9L2YxsuLti2YTsQ07DTovDL Mur4u28Qv5qEwg/yS3QnDFi+F/mhPpzUiY8f0l+LfXAQyO07vsVxwwvaAGByojB1 d8xHCX/vJ4s1VtnM14FtVi1zEhwnpiuQCckSjJcewUPNOabeXVVQ2ZtYQHapXeRk fD+EVIA3OqR6ncqlCq93dAktH10sCkD8pHBBYxsPVBpH8cdU1OZIrPtUwSo5pfHY w4o+67l0t4OoiO+s7H4uw331FLADgK31YoMPcMuUsTplxilO3jYDwmB+R9FYWKBp IYYEgTSSLTg+dItah6mNCA1BiZQstouCiMsmLaBO1QfKQSm/YUucSWElRCptNbBB XPWQbWB8xu9Jdgc2QwoNgZ3/JFYH41sJQ1LQrcgwJ+Jod8Oa8VZP7cxm9Sa8kJQ7 G2NHZ5Kmwck0bChL1Xg0z/e/4lCT4DD3SNjWEiOnE88sTS2Fk6+CIWc0CW1CzZjm
Processed: tagging 1021117
Processing commands for cont...@bugs.debian.org: > tags 1021117 + ftbfs Bug #1021117 [llvm-15-dev] llvm-15-dev: cmake fails on missing /usr/lib/llvm-15/bin/mlir-tblgen Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1021117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1021117
Processing commands for cont...@bugs.debian.org: > affects 1021117 src:spirv-llvm-translator-15 Bug #1021117 [llvm-15-dev] llvm-15-dev: cmake fails on missing /usr/lib/llvm-15/bin/mlir-tblgen Added indication that 1021117 affects src:spirv-llvm-translator-15 > thanks Stopping processing here. Please contact me if you need assistance. -- 1021117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021435: marked as done (python3-matrix-common: matrix-synapse not starting due to ModuleNotFoundError: No module named 'matrix_common')
Your message dated Mon, 10 Oct 2022 01:37:10 +0530 with message-id <20221009200710.tpn32g2m5edz6...@nileshpatra.info> and subject line Re: python3-matrix-common: matrix-synapse not starting due to ModuleNotFoundError: No module named 'matrix_common' has caused the Debian Bug report #1021435, regarding python3-matrix-common: matrix-synapse not starting due to ModuleNotFoundError: No module named 'matrix_common' 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.) -- 1021435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-matrix-common Version: 1.3.0-2~bpo11+1 Severity: important X-Debbugs-Cc: sa...@sahilister.in Dear Maintainer, * What led up to the situation? Was updating matrix-synapse from 1.63.0-1~bpo11+1 to v1.66.0-1~bpo11+1 when python3-matrix-common was also updated to 1.3.0-2~bpo11+1. * What exactly did you do (or not do) that was effective (or ineffective)? From `journalctl -u matrix-synapse`, it shows ModuleNotFoundError: No module named 'matrix_common'. Full log can be found here https://paste.debian.net/1256360/ * What was the outcome of this action? matrix-synapse package is stuck in activating state. * What outcome did you expect instead? matrix-synapse package is not starting. -- System Information: Debian Release: 11.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/12 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 Versions of packages python3-matrix-common depends on: ii python3 3.9.2-3 ii python3-attr20.3.0-1 ii python3-importlib-metadata 1.6.0-2 python3-matrix-common recommends no packages. python3-matrix-common suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 1.3.0-2~bpo11+3 This should be fixed in a later upload of the package so I am marking it as closed. Although, that said I find the upload a little sub-optimal as the build-time tests are still disabled and copying is taken care at the dh_auto_install step, rather it'd be nicer to copy that to the build_dir before build itself and let pyproject plugin do its install job -- patch attached. But, no big of a deal in current status quo though which should work OK. diff --git a/debian/python3-matrix-common.install b/debian/python3-matrix-common.install deleted file mode 100644 index 3899dd6..000 --- a/debian/python3-matrix-common.install +++ /dev/null @@ -1 +0,0 @@ -src/matrix_common /usr/lib/python3/dist-packages/ diff --git a/debian/rules b/debian/rules index 9a85c76..e5e3dd1 100755 --- a/debian/rules +++ b/debian/rules @@ -3,8 +3,8 @@ %: dh $@ --buildsystem=pybuild -override_dh_auto_test: - -dh_auto_test +execute_after_dh_auto_configure: + cp -av src/matrix_common .pybuild/cpython3_*/build/ execute_after_dh_auto_install: -rm -rf debian/*/usr/lib/*/dist-packages/.pytest_cache signature.asc Description: PGP signature --- End Message ---
Bug#1021510: lxqt-qtplugin: hardcoded dependencies on libfm-qt8
Source: lxqt-qtplugin Version: 0.16.0-1 Severity: serious The libfm-qt started its transition from libfm-qt8 to libfm-qt11. Since lxqt-qtplugin hardcodes a dependency on libfm-qt8, this dependency needs to be fixed with a sourceful upload. Cheers -- Sebastian Ramacher
Bug#1020702: prusa-slicer: SEGV on start
Hello, it looks like following line should expect the Get() call returning a nullptr, which wxWidget documentation explicitly notes. 2079 wxTranslations::Get()->SetLanguage(wxLANGUAGE_DEFAULT); I have raised this question to upstream here: https://github.com/prusa3d/PrusaSlicer/issues/9024 Kind regards, Bernhard Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f2589f565f3 in std::__cxx11::basic_string, std::allocator >::_M_data (this=) at /build/gcc-12-GwPmq4/gcc-12-12.2.0/build/x86_64-linux-gnu/libstdc++-v3/include/bits/basic_string.h:234 234 /build/gcc-12-GwPmq4/gcc-12-12.2.0/build/x86_64-linux-gnu/libstdc++-v3/include/bits/basic_string.h: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 0x7f2589f565f3 in std::__cxx11::basic_string, std::allocator >::_M_data (this=) at /build/gcc-12-GwPmq4/gcc-12-12.2.0/build/x86_64-linux-gnu/libstdc++-v3/include/bits/basic_string.h:234 #1 std::__cxx11::basic_string, std::allocator >::_M_is_local (this=) at /build/gcc-12-GwPmq4/gcc-12-12.2.0/build/x86_64-linux-gnu/libstdc++-v3/include/bits/basic_string.h:274 #2 std::__cxx11::basic_string, std::allocator >::capacity (this=) at /build/gcc-12-GwPmq4/gcc-12-12.2.0/build/x86_64-linux-gnu/libstdc++-v3/include/bits/basic_string.h:1134 #3 std::__cxx11::basic_string, std::allocator >::_M_assign (this=this@entry=0x0, __str=L"") at /build/gcc-12-GwPmq4/gcc-12-12.2.0/build/x86_64-linux-gnu/libstdc++-v3/include/bits/basic_string.tcc:279 #4 0x7f258896e05a in std::__cxx11::basic_string, std::allocator >::assign (__str=L"", this=0x0) at /usr/include/c++/12/bits/basic_string.h:1540 #5 0x7f258896e0c6 in wxTranslations::SetLanguage (this=0x0, lang=lang@entry=wxLANGUAGE_DEFAULT) at ./src/common/translation.cpp:1384 #6 0x563e57fb8e26 in Slic3r::GUI::GUI_App::load_language (this=0x563e59d29200, language=..., initial=) at ./src/slic3r/GUI/GUI_App.cpp:2079 #7 0x563e57fbaaf5 in Slic3r::GUI::GUI_App::on_init_inner (this=0x563e59d29200) at ./src/slic3r/GUI/GUI_App.cpp:1093 #8 0x563e57fbd4c6 in Slic3r::GUI::GUI_App::OnInit (this=) at ./src/slic3r/GUI/GUI_App.cpp:1035 #9 0x7f258891feda in wxEntry (argc=, argv=) at ./src/common/init.cpp:487 #10 0x563e57f9f7b9 in Slic3r::GUI::GUI_Run (params=...) at ./src/slic3r/GUI/GUI_Init.cpp:54 #11 0x563e577605de in Slic3r::CLI::run (this=, argc=, argv=) at ./src/PrusaSlicer.cpp:618 #12 0x563e57735bf4 in main (argc=, argv=) at ./src/PrusaSlicer.cpp:844 https://docs.wxwidgets.org/3.0/classwx_translations.html#ab384ea68c44e74cfd2cd59e782529540
Processed: tagging 1020314
Processing commands for cont...@bugs.debian.org:
> tags 1020314 + ftbfs
Bug #1020314 {Done: Thorsten Alteholz } [src:osmo-bts]
osmo-bts: Stale build dependency on openbsc-dev
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1020314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1019865: Debian Bug report logs - #1019865
Package: evolution Version: 3.45.3-2 / 3.46.0-2 I have since apt upgraded to version 3.46.0-2. I confirm the workaround for this problem, with the suggested disabling of requesting read receipts: edit> preferences> composer preferences> UNTICK always request read receipt The compose window then starts as normal. It also now starts as normal from the command line.
Bug#1021504: cargo: BD-Uninstallable: libgit2-dev
Source: cargo Version: 0.57.0-7 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org report: - package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 status: broken reasons: - missing: pkg: package: sbuild-build-depends-main-dummy version: 0.invalid.0 architecture: amd64 unsat-dependency: libgit2-dev:amd64 (< 1.4~~) Cheers -- Sebastian Ramacher
Bug#1020747: AM_PATH_PYTHON
Hello Bastien, thanks for your reply. On Fri, 30 Sep 2022 14:31:47 + Bastien =?ISO-8859-1?Q?Roucari=E8s?= wrote: control: reassign -1 automake control: affects -1 autoconf-archive Hi, The macro AM_PATH_PYTHON dos not support 3 level python version... The `configure.ac' of graph-tool passes a 2 level python version to AM_PATH_PYTHON. The bug lie in automake not autoconf-archive Could be workarround by a little sed script in order remove micro version on graph tool side Can you please more specific here ? Are you referred to the PYTHON_FULL_VERSION set up in `configure.ac' ? If so, it was working well before ax_python_devel serial 32 went. Second, I am not sure that removing micro version for devel stuff is a good idea. Best wishes, Jerome Bastien -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.net AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B OpenPGP_signature Description: OpenPGP digital signature
Processed: affects 1020898
Processing commands for cont...@bugs.debian.org:
> affects 1020898 - perl6-readline
Bug #1020898 {Done: Dominique Dumont }
[perl6-readline,raku-file-which,raku-librarycheck,raku-readline] Uninstallable
due to file conflict A37F26876B58371B70EDD889AD69F064C90AC2C6
Removed indication that 1020898 affects
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1020898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: merging 1021441 1021445
Processing commands for cont...@bugs.debian.org: > merge 1021441 1021445 Bug #1021441 [apt-venv] apt-venv: autopkgtest regression: output on stderr Bug #1021445 [apt-venv] apt-venv: autopkgtest regression: output on stderr Bug #1021448 [apt-venv] apt-venv: autopkgtest regression: output on stderr Merged 1021441 1021445 1021448 > thanks Stopping processing here. Please contact me if you need assistance. -- 1021441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021441 1021445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021445 1021448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021448 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020677: httraqt: Segfault upon mirroring initiation
Dear Maintainer,
I tried to have a look and found unfortunately the dbgsym package
not containing useful files.
This seems related to CMAKE_CXX_FLAGS getting reset,
therefore loosing Qt related flags.
Before the application crashed already when trying to open
one leaf in the tree view, with the Qt flags this crash did not happen,
so this might be related.
The second patch just removes a leftover CMakeLists.txt.rej from a previous
patch.
Kind regards,
Bernhard
Before:
-- CMAKE_CXX_FLAGS -O3 -DNDEBUG -Wall
After:
-- CMAKE_CXX_FLAGS -g -O2
-ffile-prefix-map=/home/benutzer/source/httraqt/git/httraqt=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -Wall -DQT_NO_DEPRECATED_WARNINGSFrom 1349c117855ba576dd9eb7aea2612550c58a1727 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bernhard=20=C3=9Cbelacker?=
Date: Sun, 9 Oct 2022 16:29:40 +0200
Subject: Remove CMakeLists.txt.rej from 10_reproducible_build.patch.
---
debian/patches/10_reproducible_build.patch | 27 --
1 file changed, 27 deletions(-)
diff --git a/debian/patches/10_reproducible_build.patch b/debian/patches/10_reproducible_build.patch
index 22f5ebb..7a620e5 100644
--- a/debian/patches/10_reproducible_build.patch
+++ b/debian/patches/10_reproducible_build.patch
@@ -17,30 +17,3 @@ Last-Update: 2017-07-18
MESSAGE("-- Version build date: ${BUILD_DATE}")
configure_file (
/dev/null
-+++ httraqt-1.4.9/CMakeLists.txt.rej
-@@ -0,0 +1,24 @@
-+--- CMakeLists.txt
- CMakeLists.txt
-+@@ -6,7 +6,7 @@ CMAKE_POLICY(SET CMP0003 OLD)
-+ CMAKE_POLICY(SET CMP0015 OLD)
-+
-+ # if you use the version 5, please change it to 5
-+-SET(USE_QT_VERSION 4)
-++SET(USE_QT_VERSION 5)
-+
-+ MESSAGE("Qt version for compiling: " ${USE_QT_VERSION})
-+
-+@@ -62,12 +62,6 @@ set(APP_RESOURCES "${PROJECT_SOURCE_DIR
-+ MESSAGE("-- Version info: ${HTTRAQT_VERSION}")
-+ SET(VERSION ${HTTRAQT_VERSION})
-+
-+-EXECUTE_PROCESS (
-+- COMMAND date +"%d %b %Y"
-+- COMMAND sed -e "s/\"//g"
-+- OUTPUT_VARIABLE BUILD_DATE
-+- OUTPUT_STRIP_TRAILING_WHITESPACE)
-+-
-+ MESSAGE("-- Version build date: ${BUILD_DATE}")
-+
-+ configure_file (
--
2.35.1
From a678025eece455ffcc3916c65bfac194b5747b1a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bernhard=20=C3=9Cbelacker?=
Date: Sun, 9 Oct 2022 16:34:36 +0200
Subject: Do not override CMAKE_CXX_FLAGS.
Adds additionally QT_NO_DEPRECATED_WARNINGS as those warnings
might be mostly useful for upstream developers.
---
.../30_do_not_override_CMAKE_CXX_FLAGS.patch | 21 +++
debian/patches/series | 1 +
2 files changed, 22 insertions(+)
create mode 100644 debian/patches/30_do_not_override_CMAKE_CXX_FLAGS.patch
diff --git a/debian/patches/30_do_not_override_CMAKE_CXX_FLAGS.patch b/debian/patches/30_do_not_override_CMAKE_CXX_FLAGS.patch
new file mode 100644
index 000..b11608a
--- /dev/null
+++ b/debian/patches/30_do_not_override_CMAKE_CXX_FLAGS.patch
@@ -0,0 +1,21 @@
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index 1310490..a51d391 100644
+--- a/CMakeLists.txt
b/CMakeLists.txt
+@@ -26,11 +26,14 @@ OPTION (USE_PROFILER "Include in binary file profiling information" OFF)
+
+
+ IF(${USE_DEBUGGER})
+- SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS_DEBUG} -Wall")
++ SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${CMAKE_CXX_FLAGS_DEBUG} -Wall")
+ ELSE()
+- SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS_RELEASE} -Wall")
++ SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${CMAKE_CXX_FLAGS_RELEASE} -Wall")
+ ENDIF()
+
++SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -DQT_NO_DEPRECATED_WARNINGS")
++
++
+ MESSAGE(STATUS "CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS}")
+
+
diff --git a/debian/patches/series b/debian/patches/series
index 8d027f0..43c04ea 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
10_reproducible_build.patch
20_cross.patch
+30_do_not_override_CMAKE_CXX_FLAGS.patch
--
2.35.1
Bug#1021123: marked as done (libgdbm-compat-dev: missing dependency on libgdbm-dev)
Your message dated Sun, 09 Oct 2022 15:04:27 + with message-id and subject line Bug#1021123: fixed in gdbm 1.23-3 has caused the Debian Bug report #1021123, regarding libgdbm-compat-dev: missing dependency on libgdbm-dev 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.) -- 1021123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgdbm-compat-dev Version: 1.23-2 Severity: serious Justification: Policy 3.5 The header files in libgdbm-compat-dev (dbm.h, gdbm-ndbm.h, and ndbm.h) all have "#include ". libgdbm-compat-dev therefore needs to depend on libgdbm-dev so that this #include can be resolved. (Noticed while improving man-db's upstream CI jobs.) Thanks, -- Colin Watson (he/him) [cjwat...@debian.org] --- End Message --- --- Begin Message --- Source: gdbm Source-Version: 1.23-3 Done: Nicolas Mora We believe that the bug you reported is fixed in the latest version of gdbm, 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 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Mora (supplier of updated gdbm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 02 Oct 2022 20:24:12 -0400 Source: gdbm Architecture: source Version: 1.23-3 Distribution: unstable Urgency: medium Maintainer: Nicolas Mora Changed-By: Nicolas Mora Closes: 1021123 Changes: gdbm (1.23-3) unstable; urgency=medium . * libgdbm-compat-dev: Add dependency libgdbm-dev (Closes: #1021123) Checksums-Sha1: f8a317eaea64193428360faed01bbe7798b431bc 2583 gdbm_1.23-3.dsc 50ba1b1d45ce33fd44e4fdaaf3b55a9d8f3dc418 1115854 gdbm_1.23.orig.tar.gz 81599dbe10c7d0fb309ec1fa784860fd8a489f38 181 gdbm_1.23.orig.tar.gz.asc fb689329fef4fa50905303a96ca756e92aac0b19 18552 gdbm_1.23-3.debian.tar.xz 1bf5bd40fddb6ff4c13c247f2ed516a3cf2d138f 8934 gdbm_1.23-3_amd64.buildinfo Checksums-Sha256: 3e4a52655a1b65c51d33e032913edda3423dcae8cc282c16a455a0afd2d2738d 2583 gdbm_1.23-3.dsc 74b1081d21fff13ae4bd7c16e5d6e504a4c26f7cde1dca0d963a484174bbcacd 1115854 gdbm_1.23.orig.tar.gz 64ebb68cc68e8915d62cb20ea40323c00b56051f844589ee0a52169fff34cecb 181 gdbm_1.23.orig.tar.gz.asc a0ff17befcbd7c4b361cfe0d821a7a71334102a9c423537bd57f60f18f6802ea 18552 gdbm_1.23-3.debian.tar.xz f25b5ca24bd35b6b6e9fe9a3e3d9bde362834bb40cb352bd2b42d85cf6c8ab15 8934 gdbm_1.23-3_amd64.buildinfo Files: 6ec1c4eb47b5e04fd39ccfb706e32347 2583 libs optional gdbm_1.23-3.dsc 8551961e36bf8c70b7500d255d3658ec 1115854 libs optional gdbm_1.23.orig.tar.gz 1e65967aaf85d790831a51fbac1aebe2 181 libs optional gdbm_1.23.orig.tar.gz.asc c5a6ce3d9ff36734c927b6e546eea9bb 18552 libs optional gdbm_1.23-3.debian.tar.xz 4ba5e8557661bcdcde49c65f3fff086d 8934 libs optional gdbm_1.23-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEhAWwL8wo75dEyPJT/oITlEC9IrkFAmNC3uwACgkQ/oITlEC9 Irmy8A//cpIhOkAM7jZoZTdLDBVEPYAfQcimGDEW7B27SOQuSuFoTl7ja28rw37k 0SiEgSb7IOIC/48c6QWomNuRuot6rafXgOvr7BcQaljVz6PGoo4g7+UMFdktH1wP cn7VbvE2CdhBaLB0AK2brFUDW6OnraUrQZd6uPBVLFpYfSH/8lzFogU43Bg/Fh3F C5pYi/kRW5lvQs/ygUEuz32GmOczz9sfqjwWGjHXwz1o5SxXgWl+PdiVmNGuiFW5 LWtYp0Gci/hvrnqHz6fRdxuIgWguR2x3q5ZzbHGxRwUqEPqCF9jU7d4QvIlNot2T JkVqF5aLU2ZmO84nYkHPJO/qzXi0CtfQK2CtSuDa1ZDUuC/SBZy3AMTBEVC0/EWl vp/8/q/DxUYdbvPME1WYl6zC9EyoYDx8ikExbP1fhgCJ8XscRia1/2hAHCo9t/g6 jhMNoOsRz1J2GHr8XW3QsOQayzJv68T/2kH0HEOWaZnRlbUYdJHUl1bSGrRACRBv 0kswmFuTb5sr3ZPWRcAenV1TeKwXY87gkhmAPcymaHTRwlraOIi+bKMwseYYh2kB lUeQqeuQn0Rjt59ip4RR6rsuYOv5UK/vYtYHXY23nlk1NpVUlwGke+rEdfC8z+Jn 9tVtp+8QBk/lVrD+mcTCkRiC6zGx+iEMYBKAmop4fod4ZIcHDkI= =4ovs -END PGP SIGNATURE End Message ---
Bug#1018743: marked as done (squid: build failures because of -Wall -Werror)
Your message dated Sun, 9 Oct 2022 15:22:46 +0200 with message-id <20221009132246.t2sa54wpwzkx6...@zeha.at> and subject line Re: #1018743: squid: build failures because of -Wall -Werror has caused the Debian Bug report #1018743, regarding squid: build failures because of -Wall -Werror 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.) -- 1018743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: squid Version: 5.6-1 Severity: serious Tags: bookworm sid ftbfs X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update regression squid's autopkgtests are failing because it fails to build because it sets -Wall -Werror which means the build will fail for *any* build warning. Please override that. Thank you, Jeremy Bicha --- End Message --- --- Begin Message --- Version: 5.7-1 Looks like closing this bug was forgotten in the new upstream upload. Chris--- End Message ---
Processed: #1017104: dpkg fails when purging git-daemon-run (patch)
Processing control commands: > tags -1 + patch Bug #1017104 [src:git] during removal fails to remove /var/log/git-daemon Added tag(s) patch. -- 1017104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017104: #1017104: dpkg fails when purging git-daemon-run (patch)
Control: tags -1 + patch Jonathan, I'm attaching a patch for the git-daemon-run postrm script, please apply it when you can. Currently, the postrm fails, causing dpkg to fail. From what I can tell, the change is harmless (the old behavior was wrong IMO). Thanks, Chris >From 095ac91986212502a7fb35c1de9808cf304e1e78 Mon Sep 17 00:00:00 2001 From: Chris Hofstaedtler Date: Sun, 9 Oct 2022 11:47:33 + Subject: [PATCH] git-daemon-run.postrm: remove -f flag from deluser call Does not exist since #1002495 and was always wrong. Signed-off-by: Chris Hofstaedtler --- debian/git-daemon-run.postrm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/git-daemon-run.postrm b/debian/git-daemon-run.postrm index f6aa282d05..1c2ac6570a 100644 --- a/debian/git-daemon-run.postrm +++ b/debian/git-daemon-run.postrm @@ -18,5 +18,5 @@ done rmdir /var/log/git-daemon || : getent passwd gitlog >/dev/null || exit 0 -! deluser --version >/dev/null 2>&1 || exec deluser -f gitlog +! deluser --version >/dev/null 2>&1 || exec deluser gitlog echo 'deluser program not available, not removing system user "gitlog".' >&2 -- 2.37.2
Bug#995624: marked as done (pktstat FTBFS: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Sun, 09 Oct 2022 11:04:49 +
with message-id
and subject line Bug#995624: fixed in pktstat 1.8.5-8
has caused the Debian Bug report #995624,
regarding pktstat FTBFS: error: format not a string literal and no format
arguments [-Werror=format-security]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
995624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pktstat
Version: 1.8.5-7
Severity: serious
Tags: ftbfs
pktstat fails to build from source in unstable on amd64. A non-parallel
build ends as follows:
| gcc -DHAVE_CONFIG_H -I. -DPATH_PKTSTATRC=\"/etc/pktstatrc\" -Wdate-time
-D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic
-D_BSD_SOURCE -c -o display.o display.c
| In file included from
/usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
| from /usr/include/stdio.h:27,
| from display.c:17:
| /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and
_SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
| 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use
_DEFAULT_SOURCE"
| | ^~~
| display.c: In function ‘display_update’:
| display.c:499:33: warning: field width specifier ‘*’ expects argument of type
‘int’, but argument 2 has type ‘long unsigned int’ [-Wformat=]
| 499 | attron(A_UNDERLINE); printw("%-*s",
| | ~~^~
| | |
| | int
| display.c:552:13: warning: field precision specifier ‘.*’ expects argument of
type ‘int’, but argument 2 has type ‘long unsigned int’ [-Wformat=]
| 552 | printw("%.*s\n", MIN(maxx - LLEN, sizeof flows[i].tag - 1),
| | ~~^~
| | |
| | int
| display.c:566:15: warning: field precision specifier ‘.*’ expects argument of
type ‘int’, but argument 2 has type ‘long unsigned int’ [-Wformat=]
| 566 |printw(" %.*s\n", MIN(maxx - LLEN - 2,
| | ~~^~
| | |
| | int
| display.c:285:21: warning: variable ‘x’ set but not used
[-Wunused-but-set-variable]
| 285 | int maxx, maxy, y, x;
| | ^
| display.c: In function ‘printhelp’:
| display.c:672:3: error: format not a string literal and no format arguments
[-Werror=format-security]
| 672 | printw((char *)h->name + 1);
| | ^~
| cc1: some warnings being treated as errors
| make[2]: *** [Makefile:483: display.o] Error 1
| make[2]: Leaving directory '/<>'
| make[1]: *** [Makefile:339: all] Error 2
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j1 returned exit code 2
| make: *** [debian/rules:11: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
This is likely due to ncurses including format string annotations.
Helmut
--- End Message ---
--- Begin Message ---
Source: pktstat
Source-Version: 1.8.5-8
Done: Adam Borowski
We believe that the bug you reported is fixed in the latest version of
pktstat, 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 995...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adam Borowski (supplier of updated pktstat package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 09 Oct 2022 12:39:23 +0200
Source: pktstat
Architecture: source
Version: 1.8.5-8
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Adam Borowski
Closes: 995624
Changes:
pktstat (1.8.5-8) unstable; urgency=medium
.
* QA upload.
* Fix FTBFS due to format string (closes: #995624)
* dh 13.
* Change pointless R³:binary-targets to no.
Checksums-Sha1:
bbef2571978470a53817cc6ab9540060810772b0 1851 pktstat_1.8.5-8.dsc
cb5399a493b18730fe40607fc6fb96fd6c13d84f 4728 pktstat_1.8.5-8.debian.tar.xz
b3de2dbc440b1a3e98be028e5a2753ffe77f7754 5865 pktstat_1.8.5-8_source.buildinfo
Checksums-Sha256:
Bug#938792: marked as done (vmdebootstrap: Python2 removal in sid/bullseye)
Your message dated Sun, 9 Oct 2022 11:32:33 +0200 with message-id <20221009093233.rqdfn25roe4ko...@percival.namespace.at> and subject line vmdebootstrap has been removed has caused the Debian Bug report #938792, regarding vmdebootstrap: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:vmdebootstrap Version: 1.11-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:vmdebootstrap If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.11-2+rm1 Closing all src:vmdebootstrap bugs, per: https://tracker.debian.org/news/1185469/removed-111-2-from-unstable/ Subject: Bug#907751: Removed package(s) from unstable ROM; upstream discontinued, obsolete, better options exist--- End Message ---
Processed: Re: Processed: reopen #516394 djbdns [security]: Rapid DNS Poisoning in dnscache
Processing commands for cont...@bugs.debian.org: > close 516394 1:1.05-10 Bug #516394 [djbdns] [security]: Rapid DNS Poisoning in dnscache There is no source info for the package 'djbdns' at version '1:1.05-10' with architecture '' Unable to make a source version for version '1:1.05-10' Marked as fixed in versions 1:1.05-10. Bug #516394 [djbdns] [security]: Rapid DNS Poisoning in dnscache Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 516394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020820: marked as done (joblib: CVE-2022-21797)
Your message dated Sun, 09 Oct 2022 09:20:31 + with message-id and subject line Bug#1020820: fixed in joblib 1.2.0-1 has caused the Debian Bug report #1020820, regarding joblib: CVE-2022-21797 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.) -- 1020820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: joblib Version: 1.1.0-2 Severity: grave Tags: security Justification: user security hole Forwarded: https://github.com/joblib/joblib/issues/1128 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for joblib. CVE-2022-21797[0]: | The package joblib from 0 and before 1.2.0 are vulnerable to Arbitrary | Code Execution via the pre_dispatch flag in Parallel() class due to | the eval() statement. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-21797 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21797 [1] https://github.com/joblib/joblib/issues/1128 [2] https://github.com/joblib/joblib/commit/b90f10efeb670a2cc877fb88ebb3f2019189e059 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: joblib Source-Version: 1.2.0-1 Done: Chiara Marmo We believe that the bug you reported is fixed in the latest version of joblib, 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 1020...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chiara Marmo (supplier of updated joblib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 09 Oct 2022 14:09:39 +0530 Source: joblib Architecture: source Version: 1.2.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Chiara Marmo Closes: 1020820 Changes: joblib (1.2.0-1) unstable; urgency=medium . * Team upload. * Update upstream version (Closes: #1020820) * Refresh patches Checksums-Sha1: ef953f965382f8061afa8e804224658fdff5ca23 2269 joblib_1.2.0-1.dsc 26a23da574bf0cd83c5907e8d7ab7f0bdedd 345345 joblib_1.2.0.orig.tar.gz d45a8e4b405dcf38c4f245f63f0ece663a7671cb 7440 joblib_1.2.0-1.debian.tar.xz e79615f5d51b994b8b66e3f6e6de2b28e65803d8 6874 joblib_1.2.0-1_amd64.buildinfo Checksums-Sha256: c27bfeaf649cf63c04a8b761775ddf7e0efa02d3c9f11077414e25f7ca9e86a7 2269 joblib_1.2.0-1.dsc 574eca5aaeb0a06c4fe0a8e8e67b24715218fb0f9d0fdc9d4f30519100885e53 345345 joblib_1.2.0.orig.tar.gz f79ce95599689217175eb4cd3aeea1e47a67ab55fa93f86159068f5294502061 7440 joblib_1.2.0-1.debian.tar.xz d820b91ab39faabdad51ab81fce2b5444663d4027d4f799bf50bf814c48e48d2 6874 joblib_1.2.0-1_amd64.buildinfo Files: f6cecb252f7331bb737ae9a70053eed5 2269 python optional joblib_1.2.0-1.dsc d51f8e86fe75ed94b88be83604c3f43d 345345 python optional joblib_1.2.0.orig.tar.gz d459e8a4f6f652cf5c4348dec0ffb0bb 7440 python optional joblib_1.2.0-1.debian.tar.xz cc802c7f73b7dac56077f17022eb5e56 6874 python optional joblib_1.2.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmNCjfwSHG5pbGVzaEBk ZWJpYW4ub3JnAAoJEAC650s0M2nxJAsP+gJ+2BNp6busmFwlY0oW05UldkNWHDqH pJ2IxXfpI93qS6kg9rdUfHV9xwyaU1NtegBSlrD9uSv/n+xuheiyI15fJ76Kgb1y d5D5ylcF/4skOIMPwkVprJcJrt5VOBrojIHMcPFTcthXY/hTzLzqMeTBs65Ho1sQ UHttVzBIb88llZjf73PlX/lyTWC6Cg83J6E5XxB+B4Cl9+M2F21FWx+SMoeFUVwk o8qz4j1RchDOj4PWCijLrd4XsXR1cLPoe3YJSUCtXiy3Ct4Hpx+5jvTWbkxP0+8s yqoMLPvKPy+utKzLgYwiy1vd7EoofBh/GOxHYBXtTPXs2lz0csutFiURXJ7LQVVr jc65NjomNU7Le6w7UUrGmbuwiinOrp63/GzhtmEfLWrH6Uii0wBqrF37/8C5Ct9B ysaVn1GRJAesSAdgD4MLKhUxX5GPuoqqI7rfxOFXQ/yKLyLEzDpMQUaD7LL6lv4P kppgJgUy5XprTqgaGOAZeaZJK6dQRbtIV8GU3Soa1tcUPpK32Mdr+Y2j7D9WrMto 7c3uzckYgwpAw0lThTYpTHNwvye1GSLqt2AWQlTOBC8Syk3OR35Wv+uCOwY7bB8M Z22lmOgJLkgSbjeyLMyv+HTDdKJTamDnY9H0qPGZe4MLPTsOfoJoE4PBoHmlx5y9 ZWruQ7jDQVDZ =PSuH -END PGP SIGNATURE End Message ---
Processed: affects 1016218, affects 1016218, block 1016234 with 1016218, block 1016230 with 1016218
Processing commands for cont...@bugs.debian.org: > affects 1016218 src:feynmf Bug #1016218 [texlive-latex-base] doc.sty requires hypdoc.sty that is in texlive-latex-extra Bug #1016231 [texlive-latex-base] doc.sty requires hypdoc.sty that is in texlive-latex-extra Added indication that 1016218 affects src:feynmf Added indication that 1016231 affects src:feynmf > affects 1016218 src:auctex Bug #1016218 [texlive-latex-base] doc.sty requires hypdoc.sty that is in texlive-latex-extra Bug #1016231 [texlive-latex-base] doc.sty requires hypdoc.sty that is in texlive-latex-extra Added indication that 1016218 affects src:auctex Added indication that 1016231 affects src:auctex > block 1016234 with 1016218 Bug #1016234 [src:feynmf] feynmf: FTBFS: ! LaTeX Error: File `hypdoc.sty' not found. 1016234 was not blocked by any bugs. 1016234 was not blocking any bugs. Added blocking bug(s) of 1016234: 1016218 and 1016231 > block 1016230 with 1016218 Bug #1016230 [src:auctex] auctex: FTBFS: ! LaTeX Error: File `hypdoc.sty' not found. 1016230 was not blocked by any bugs. 1016230 was not blocking any bugs. Added blocking bug(s) of 1016230: 1016231 and 1016218 > thanks Stopping processing here. Please contact me if you need assistance. -- 1016218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016218 1016230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016230 1016231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016231 1016234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reopen #516394 djbdns [security]: Rapid DNS Poisoning in dnscache
Processing commands for cont...@bugs.debian.org:
> reopen 516394
Bug #516394 {Done: Modellbahnen Walter Licht GmbH }
[djbdns] [security]: Rapid DNS Poisoning in dnscache
'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 1:1.05-10.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
516394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#995595: #995595: current version builds fine
guile-3.0 3.0.8-2 builds fine (on the buildds and locally). Should this bug be closed? Chris
Bug#1013561: marked as done (spirv-tools: FTBFS: validate_builtins.cpp:4010:10: error: enumeration value ‘SpvBuiltInCullMaskKHR’ not handled in switch [-Werror=switch])
Your message dated Sun, 9 Oct 2022 11:13:19 +0200
with message-id <20221009091319.wthtaiu7w667q...@percival.namespace.at>
and subject line 1013561 fixed in new upstream release
has caused the Debian Bug report #1013561,
regarding spirv-tools: FTBFS: validate_builtins.cpp:4010:10: error: enumeration
value ‘SpvBuiltInCullMaskKHR’ not handled in switch [-Werror=switch]
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.)
--
1013561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spirv-tools
Version: 2022.1+1.3.204.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/source && /usr/bin/c++
> -DSPIRV_COLOR_TERMINAL -DSPIRV_LINUX -DSPIRV_TIMER_ENABLED -I/<>
> -I/<>/include -I/<>/obj-x86_64-linux-gnu -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC
> -Wall -Wextra -Wnon-virtual-dtor -Wno-missing-field-initializers -Werror
> -std=c++11 -fno-exceptions -Wno-long-long -Wshadow -Wundef -Wconversion
> -Wno-sign-conversion -std=gnu++11 -MD -MT
> source/CMakeFiles/SPIRV-Tools-static.dir/val/validate_conversion.cpp.o -MF
> CMakeFiles/SPIRV-Tools-static.dir/val/validate_conversion.cpp.o.d -o
> CMakeFiles/SPIRV-Tools-static.dir/val/validate_conversion.cpp.o -c
> /<>/source/val/validate_conversion.cpp
> /<>/source/val/validate_builtins.cpp: In member function
> ‘spv_result_t
> spvtools::val::{anonymous}::BuiltInsValidator::ValidateSingleBuiltInAtDefinition(const
> spvtools::val::Decoration&, const spvtools::val::Instruction&)’:
> /<>/source/val/validate_builtins.cpp:4010:10: error: enumeration
> value ‘SpvBuiltInCullMaskKHR’ not handled in switch [-Werror=switch]
> 4010 | switch (label) {
> | ^
> [ 23%] Building CXX object
> source/CMakeFiles/SPIRV-Tools-static.dir/val/validate_debug.cpp.o
> cd /<>/obj-x86_64-linux-gnu/source && /usr/bin/c++
> -DSPIRV_COLOR_TERMINAL -DSPIRV_LINUX -DSPIRV_TIMER_ENABLED -I/<>
> -I/<>/include -I/<>/obj-x86_64-linux-gnu -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC
> -Wall -Wextra -Wnon-virtual-dtor -Wno-missing-field-initializers -Werror
> -std=c++11 -fno-exceptions -Wno-long-long -Wshadow -Wundef -Wconversion
> -Wno-sign-conversion -std=gnu++11 -MD -MT
> source/CMakeFiles/SPIRV-Tools-static.dir/val/validate_debug.cpp.o -MF
> CMakeFiles/SPIRV-Tools-static.dir/val/validate_debug.cpp.o.d -o
> CMakeFiles/SPIRV-Tools-static.dir/val/validate_debug.cpp.o -c
> /<>/source/val/validate_debug.cpp
> [ 24%] Building CXX object
> source/CMakeFiles/SPIRV-Tools-static.dir/val/validate_decorations.cpp.o
> cd /<>/obj-x86_64-linux-gnu/source && /usr/bin/c++
> -DSPIRV_COLOR_TERMINAL -DSPIRV_LINUX -DSPIRV_TIMER_ENABLED -I/<>
> -I/<>/include -I/<>/obj-x86_64-linux-gnu -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC
> -Wall -Wextra -Wnon-virtual-dtor -Wno-missing-field-initializers -Werror
> -std=c++11 -fno-exceptions -Wno-long-long -Wshadow -Wundef -Wconversion
> -Wno-sign-conversion -std=gnu++11 -MD -MT
> source/CMakeFiles/SPIRV-Tools-static.dir/val/validate_decorations.cpp.o -MF
> CMakeFiles/SPIRV-Tools-static.dir/val/validate_decorations.cpp.o.d -o
> CMakeFiles/SPIRV-Tools-static.dir/val/validate_decorations.cpp.o -c
> /<>/source/val/validate_decorations.cpp
> [ 24%] Building CXX object
> source/CMakeFiles/SPIRV-Tools-static.dir/val/validate_derivatives.cpp.o
> cd /<>/obj-x86_64-linux-gnu/source && /usr/bin/c++
> -DSPIRV_COLOR_TERMINAL -DSPIRV_LINUX -DSPIRV_TIMER_ENABLED -I/<>
> -I/<>/include -I/<>/obj-x86_64-linux-gnu -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC
> -Wall -Wextra -Wnon-virtual-dtor -Wno-missing-field-initializers -Werror
> -std=c++11 -fno-exceptions -Wno-long-long -Wshadow -Wundef -Wconversion
> -Wno-sign-conversion -std=gnu++11 -MD -MT
> source/CMakeFiles/SPIRV-Tools-static.dir/val/validate_derivatives.cpp.o -MF
> CMakeFiles/SPIRV-Tools-static.dir/val/validate_derivatives.cpp.o.d -o
> CMakeFiles/SPIRV-Tools-static.dir/val/validate_derivatives.cpp.o
Processed: 996297: patched with workaround
Processing control commands: > severity -1 normal Bug #996297 [src:ruby-ice-nine] ruby-ice-nine: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: expect(subject.end).to be_frozen Severity set to 'normal' from 'serious' -- 996297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996297: 996297: patched with workaround
Control: severity -1 normal 0.11.2-2 added a workaround patch, so the FTBFS itself is gone.
Bug#1013550: marked as done (sddm: FTBFS: XorgDisplayServer.cpp:68:42: error: use of deleted function ‘QCharRef& QCharRef::operator=(char)’)
Your message dated Sun, 09 Oct 2022 08:49:16 +
with message-id
and subject line Bug#1013550: fixed in sddm 0.19.0-4
has caused the Debian Bug report #1013550,
regarding sddm: FTBFS: XorgDisplayServer.cpp:68:42: error: use of deleted
function ‘QCharRef& QCharRef::operator=(char)’
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.)
--
1013550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sddm
Version: 0.19.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/src/daemon && /usr/bin/c++
> -DHAVE_JOURNALD -DHAVE_SYSTEMD -DNDEBUG -DQT_CORE_LIB -DQT_DBUS_LIB
> -DQT_NETWORK_LIB -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_FROM_BYTEARRAY
> -DQT_NO_DEBUG -DQT_NO_FOREACH -DQT_QML_LIB -DUSE_PAM
> -I/<>/obj-x86_64-linux-gnu/src/daemon
> -I/<>/src/daemon
> -I/<>/obj-x86_64-linux-gnu/src/daemon/sddm_autogen/include
> -I/<>/src/common -I/<>/src/auth
> -I/<>/obj-x86_64-linux-gnu/src/common -isystem
> /usr/include/x86_64-linux-gnu/qt5 -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtQml -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -Wall
> -std=c++11 -fPIC -MD -MT src/daemon/CMakeFiles/sddm.dir/PowerManager.cpp.o
> -MF CMakeFiles/sddm.dir/PowerManager.cpp.o.d -o
> CMakeFiles/sddm.dir/PowerManager.cpp.o -c
> /<>/src/daemon/PowerManager.cpp
> /<>/src/daemon/XorgDisplayServer.cpp: In constructor
> ‘SDDM::XorgDisplayServer::XorgDisplayServer(SDDM::Display*)’:
> /<>/src/daemon/XorgDisplayServer.cpp:68:42: error: use of
> deleted function ‘QCharRef& QCharRef::operator=(char)’
>68 | m_cookie[i] = digits[dis(gen)];
> | ^
> In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:47,
> from /usr/include/x86_64-linux-gnu/qt5/QtCore/QObject:1,
> from /<>/src/daemon/DisplayServer.h:24,
> from /<>/src/daemon/XorgDisplayServer.h:24,
> from /<>/src/daemon/XorgDisplayServer.cpp:21:
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1236:15: note: declared
> here
> 1236 | QCharRef =(char c) = delete;
> | ^~~~
> /<>/src/daemon/XorgDisplayServer.cpp: In member function
> ‘virtual bool SDDM::XorgDisplayServer::start()’:
> /<>/src/daemon/XorgDisplayServer.cpp:174:74: warning:
> ‘QStringList QString::split(QChar, QString::SplitBehavior,
> Qt::CaseSensitivity) const’ is deprecated: Use split(QChar sep,
> Qt::SplitBehavior ...) variant instead [-Wdeprecated-declarations]
> 174 | QStringList args =
> mainConfig.X11.ServerArguments.get().split(QLatin1Char(' '),
> QString::SkipEmptyParts);
> |
> ~~^~~
> In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:47,
> from /usr/include/x86_64-linux-gnu/qt5/QtCore/QObject:1,
> from /<>/src/daemon/DisplayServer.h:24,
> from /<>/src/daemon/XorgDisplayServer.h:24,
> from /<>/src/daemon/XorgDisplayServer.cpp:21:
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:615:17: note: declared here
> 615 | QStringList split(QChar sep, SplitBehavior behavior,
> | ^
> /<>/src/daemon/XorgDisplayServer.cpp: In member function
> ‘virtual void SDDM::XorgDisplayServer::finished()’:
> /<>/src/daemon/XorgDisplayServer.cpp:288:33: warning: ‘void
> QProcess::start(const QString&, QIODevice::OpenMode)’ is deprecated: Use
> QProcess::start(const QString , const QStringList ,OpenMode
> mode = ReadWrite) instead [-Wdeprecated-declarations]
> 288 | displayStopScript->start(displayStopCommand);
> | ^~~~
> In file included from
> /usr/include/x86_64-linux-gnu/qt5/QtCore/QProcessEnvironment:1,
> from /<>/src/auth/Auth.h:28,
> from /<>/src/daemon/Display.h:28,
> from
Bug#1021478: mmdebstrap - Enables first boot experience via machine-id
Package: mmdebstrap Version: 1.2.1-2 Severity: serious mmdebstrap writed "uninitialized" to /etc/machine-id. This triggers first boot semantic[1], so makes the boot wait for input. Please write an empty file if you are not equipped to handle first boot questions. Bastian [1]: https://www.freedesktop.org/software/systemd/man/machine-id.html -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (700, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mmdebstrap depends on: ii apt 2.5.3 ii perl 5.34.0-5 ii python3 3.10.6-1 Versions of packages mmdebstrap recommends: pn arch-test pn fakechroot ii fakeroot 1.29-1 ii gpg 2.2.39-1 pn libdistro-info-perl ii libdpkg-perl 1.21.9 ii mount2.38.1-1 pn uidmap Versions of packages mmdebstrap suggests: ii apt [apt-transport-https] 2.5.3 pn apt-transport-tor ii apt-utils 2.5.3 pn binfmt-support ii ca-certificates20211016 pn debootstrap ii distro-info-data 0.54 ii dpkg-dev 1.21.9 pn genext2fs pn perl-doc pn proot pn qemu-user pn qemu-user-static pn squashfs-tools-ng
Processed: retitle 965026
Processing commands for cont...@bugs.debian.org: > # retitle as the critical problem is hanging the console. a11y issue > # could be tracked separately > retitle 965026 grub-emu hangs linux console when run as root Bug #965026 [grub-emu] grub-emu is unusable with orca nor BRLTTY Changed Bug title to 'grub-emu hangs linux console when run as root' from 'grub-emu is unusable with orca nor BRLTTY'. > thanks Stopping processing here. Please contact me if you need assistance. -- 965026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012998: marked as done (mir: ftbfs with GCC-12)
Your message dated Sun, 09 Oct 2022 06:04:14 + with message-id and subject line Bug#1012998: fixed in mir 1.8.2+dfsg-4 has caused the Debian Bug report #1012998, regarding mir: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1012998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012998 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mir Version: 1.8.2+dfsg-3 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/mir_1.8.2+dfsg-3_unstable_gcc12.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] cd /<>/build-amd64/src/server/compositor && /usr/bin/c++ -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LOG_COMPONENT_FALLBACK=\"mirserver\" -DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API -DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT -DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" -DMIR_SERVER_GRAPHICS_PLATFORM_VERSION=\"MIR_GRAPHICS_PLATFORM_0.32\" -DMIR_SERVER_INPUT_PLATFORM_VERSION=\"MIR_INPUT_PLATFORM_0.27\" -DMIR_SERVER_PLATFORM_PATH=\"/usr/lib/x86_64-linux-gnu/mir/server-platform\" -DMIR_VERSION=\"1.8.2\" -DMIR_VERSION_MAJOR=1 -DMIR_VERSION_MICRO=2 -DMIR_VERSION_MINOR=8 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -I/<>/include/core -I/<>/include/common -I/<>/include/cookie -I/<>/src/include/common -I/<>/build-amd64/src/capnproto -I/<>/build-amd64/src/protobuf -I/<>/include/ platform -I/<>/include/client -I/<>/include/server -I/<>/include/renderer -I/<>/include/renderers/gl -I/<>/include/renderers/sw -I/<>/src/include/platform -I/<>/src/include/client -I/<>/src/include/server -I/<>/src/include/cookie -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/<>/src/renderers -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -std=c++14 -Wall -fno-strict-aliasing -pedantic -Wnon-virtual-dtor -Wextra -fPIC -Wno-mismatched-tags -Wno-psabi -flto -ffat-lto-objects -std=c++14 -MD -MT src/server/compositor/CMakeFiles/mircompositor.dir/screencast_display_buffer.cpp.o -MF CMakeFiles/mircompositor.dir/screencast_display_buffer.cpp.o.d -o CMakeFiles/mircompos itor.dir/screencast_display_buffer.cpp.o -c /<>/src/server/compositor/screencast_display_buffer.cpp [ 14%] Building CXX object src/server/graphics/CMakeFiles/mirgraphics.dir/surfaceless_egl_context.cpp.o cd /<>/build-amd64/src/server/graphics && /usr/bin/c++ -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LOG_COMPONENT_FALLBACK=\"mirserver\" -DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API -DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT -DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" -DMIR_SERVER_GRAPHICS_PLATFORM_VERSION=\"MIR_GRAPHICS_PLATFORM_0.32\" -DMIR_SERVER_INPUT_PLATFORM_VERSION=\"MIR_INPUT_PLATFORM_0.27\" -DMIR_SERVER_PLATFORM_PATH=\"/usr/lib/x86_64-linux-gnu/mir/server-platform\" -DMIR_VERSION=\"1.8.2\" -DMIR_VERSION_MAJOR=1 -DMIR_VERSION_MICRO=2 -DMIR_VERSION_MINOR=8 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE
Bug#1015134: marked as done (mir: FTBFS: input_config_matchers.h:119:5: error: ISO C++ forbids declaration of ‘GTEST_DISALLOW_ASSIGN_’ with no type [-fpermissive])
Your message dated Sun, 09 Oct 2022 06:04:14 + with message-id and subject line Bug#1012998: fixed in mir 1.8.2+dfsg-4 has caused the Debian Bug report #1012998, regarding mir: FTBFS: input_config_matchers.h:119:5: error: ISO C++ forbids declaration of ‘GTEST_DISALLOW_ASSIGN_’ with no type [-fpermissive] 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.) -- 1012998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012998 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mir Version: 1.8.2+dfsg-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<>/build-amd64/tests/unit-tests/platforms/mesa/kms && > /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_DATE_TIME_DYN_LINK > -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK > -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DEGL_NO_X11 > -DGTEST_VERSION_MAJOR=1 -DGTEST_VERSION_MINOR=12 -DGTEST_VERSION_PATCH=1 > -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS > -DMIR_BUILD_PLATFORM_EGLSTREAM_KMS -DMIR_BUILD_PLATFORM_MESA_KMS > -DMIR_BUILD_PLATFORM_MESA_X11 > -DMIR_CLIENT_PLATFORM_VERSION=\"MIR_CLIENT_PLATFORM_5\" > -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LIBINPUT_HAS_ACCEL_PROFILE=1 > -DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API > -DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT > -DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" > -DMIR_SERVER_GRAPHICS_PLATFORM_ABI_STRING=\"16\" -DMIR_VERSION_MAJOR=1 > -DMIR_VERSION_MICRO=2 -DMIR_VERSION_MINOR=8 -D_FILE_OFFSET_BITS=64 > -D_GNU_SOURCE -I/<>/include/core > -I/<>/include/common -I/<>/include/cookie > -I/<>/build-amd64/src/capnproto > -I/<>/build-amd64/src/protobuf > -I/usr/src/googletest/googlemock/include -I/<>/include/platform > -I/<>/include/miral -I/<>/include/server > -I/usr/include/uuid -I/<>/include/client > -I/<>/include/test -I/<>/include/renderer > -I/<>/include/renderers/gl -I/<>/tests/include > -I/<> -I/usr/include/libdrm -I/usr/include/umockdev-1.0 > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/<>/include/renderers/sw -I/<>/src/include/cookie > -I/<>/src/include/platform -I/<>/src/include/server > -I/<>/src/include/client -I/<>/src/include/common > -I/<>/src/include/gl > -I/<>/src/platforms/common/client > -I/<>/src/platforms/common/server -I/usr/include/gio-unix-2.0 > -I/usr/include/libmount -I/usr/include/blkid > -I/<>/include/platforms/mesa > -I/<>/src/platforms/mesa/server > -I/<>/include/wayland -I/<>/src/wayland/generated > -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g > -std=c++14 -Wall -fno-strict-aliasing -pedantic -Wnon-virtual-dtor -Wextra > -fPIC -Wno-mismatched-tags -Wno-psabi -flto -ffat-lto-objects > -Wno-error=null-dereference -Wno-error=overloaded-virtual -Wno-sign-compare > -fno-lto -Dregister= -pthread -std=c++14 -Wno-variadic-macros -MD -MT > tests/unit-tests/platforms/mesa/kms/CMakeFiles/mir_unit_tests_mesa-kms.dir/test_display_buffer.cpp.o > -MF CMakeFiles/mir_unit_tests_mesa-kms.dir/test_display_buffer.cpp.o.d -o > CMakeFiles/mir_unit_tests_mesa-kms.dir/test_display_buffer.cpp.o -c > /<>/tests/unit-tests/platforms/mesa/kms/test_display_buffer.cpp > In file included from > /<>/tests/integration-tests/input/test_single_seat_setup.cpp:53: > /<>/tests/include/mir/test/input_config_matchers.h:119:5: error: > ISO C++ forbids declaration of ‘GTEST_DISALLOW_ASSIGN_’ with no type > [-fpermissive] > 119 | GTEST_DISALLOW_ASSIGN_(InputConfigElementsMatcher); > | ^~ > [ 78%] Building CXX object > tests/unit-tests/platforms/mesa/kms/CMakeFiles/mir_unit_tests_mesa-kms.dir/test_display_multi_monitor.cpp.o > cd /<>/build-amd64/tests/unit-tests/platforms/mesa/kms && > /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_DATE_TIME_DYN_LINK > -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK > -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DEGL_NO_X11 > -DGTEST_VERSION_MAJOR=1 -DGTEST_VERSION_MINOR=12 -DGTEST_VERSION_PATCH=1 > -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS > -DMIR_BUILD_PLATFORM_EGLSTREAM_KMS -DMIR_BUILD_PLATFORM_MESA_KMS > -DMIR_BUILD_PLATFORM_MESA_X11 > -DMIR_CLIENT_PLATFORM_VERSION=\"MIR_CLIENT_PLATFORM_5\" > -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LIBINPUT_HAS_ACCEL_PROFILE=1 >
Bug#1021021: Upload planned
Hi, I plan to upload version 5.5.1 in the near future. Kind regards Felix Lechner
