Bug#1000336: numba: FTBFS with Python 3.10

2022-02-20 Thread Graham Inggs
Hi Diane On Mon, 21 Feb 2022 at 05:39, Diane Trout wrote: > It would... except numpy 1.22 just hit experimental on the 18th. and > numba isn't compatible with numpy 1.22. I tried adding this to > d/control, > > python3-numpy (<< 1.22), > > but my sbuild resolver still picked up numpy from experim

Bug#1005962: marked as done (dask: FTBFS in testing)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Mon, 21 Feb 2022 07:33:44 + with message-id and subject line Bug#1005962: fixed in dask 2022.01.0+dfsg-1 has caused the Debian Bug report #1005962, regarding dask: FTBFS in testing to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1005230: Does chromium REALLY need fuse now?

2022-02-20 Thread Trent W. Buck
Trent W. Buck wrote: > The error report for #1005230 only specifically mentioned GTK3. > Are these other "portal" dependencies *really* needed now? As at chromium 98.0.4758.102-1~deb11u1, chromium works with xdg-desktop-portal, fuse, flatpak removed. A minimal test script is attached. it builds &

Bug#1005230: Does chromium REALLY need fuse now?

2022-02-20 Thread Trent W. Buck
Package: chromium Followup-For: Bug #1005230 Hi, I ship chromium in prisons, where we extremely do not want unprivileged users to be able to add new drivers (fuse) and applications (flatpak/bubblewrap/xdg-desktop-portal). [*] The fix for #1005230 added indirect dependencies on fuse and bubblewrap

Processed: tagging 1006038 ...

2022-02-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1006038 + fixed-upstream patch Bug #1006038 [src:git-remote-hg] git-remote-hg: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2 Added tag(s) fixed-upstream and patch. > forwarded 1006038 > https://github.com/mnauw/git-remote-h

Bug#1006141: supertuxkart: FTBFS on armhf: Error: selected FPU does not support instruction -- `vldmia.64 r10,{d0-d7}'

2022-02-20 Thread Peter Michael Green
Tags 1006141 +patch thanks This was fixed in ubuntu a few months ago by adding ".fpu vfp" to the assembler file in question. (within the block of code that is only used on systems with the hard float ABI). https://patches.ubuntu.com/s/supertuxkart/supertuxkart_1.3+dfsg1-2ubuntu1.patch I have

Processed: re: supertuxkart: FTBFS on armhf: Error: selected FPU does not support instruction -- `vldmia.64 r10,{d0-d7}'

2022-02-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > Tags 1006141 +patch Bug #1006141 [src:supertuxkart] supertuxkart: FTBFS on armhf: Error: selected FPU does not support instruction -- `vldmia.64 r10,{d0-d7}' Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need as

Bug#1006172: [Pkg-electronics-devel] Bug#1006172: src:lepton-eda: fails to migrate to testing for too long: FTBFS on s390x

2022-02-20 Thread Bdale Garbee
Paul Gevers writes: > Your package fails to build on s390x where it build successfully in > the past. I've X-Debbugs-CC-ed the s390x porters to help you > understand why only this architecture is affected. It's hard to imagine anyone actually trying to use lepton-eda on s390x. If the porting tea

Bug#1000336: numba: FTBFS with Python 3.10

2022-02-20 Thread Diane Trout
On Sat, 2022-02-19 at 11:02 +0100, Drew Parsons wrote: > Source: numba > Followup-For: Bug #1000336 > > onetbb is now building (in experimental) for all arches except > armel and armhf. > > Is it worth at this point to make an upload of numba 0.55 to > experimental to check that it's building and

Bug#1002402: python-sparse: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

2022-02-20 Thread Diane Trout
On Mon, 2022-02-21 at 02:24 +, Peter Michael Green wrote: > > During a rebuild of all packages in sid, your package failed to > > build > > on amd64. >   >  I'm no expert on this particular package, but this looks to me like > it is not actually caused by a problem in python-sparse, but is > in

Bug#1003470: openimageio FTBFS: invalid preprocessing directive #errorDCMTK

2022-02-20 Thread Jeremy Bicha
In Ubuntu, we fixed this issue by building with C++17. You can find a diff of the rules file at https://launchpad.net/ubuntu/+source/openimageio/2.2.18.0+dfsg-1ubuntu1 This is needed to complete the libwebp transition: https://release.debian.org/transitions/html/auto-libwebp.html Thank you, Jere

Bug#1002402: python-sparse: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

2022-02-20 Thread Peter Michael Green
During a rebuild of all packages in sid, your package failed to build on amd64. I'm no expert on this particular package, but this looks to me like it is not actually caused by a problem in python-sparse, but is instead a symptom of python3-numba not being built against python 3.10 due to htt

Processed: closing 886145

2022-02-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 886145 0.99.2-2 Bug #886145 [src:shutter] shutter: Don't recommend libgoo-canvas-perl Marked as fixed in versions shutter/0.99.2-2. Bug #886145 [src:shutter] shutter: Don't recommend libgoo-canvas-perl Marked Bug as done > thanks Stopping pr

Processed: closing 870418

2022-02-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 870418 0.99.2-2 Bug #870418 [shutter] shutter: Depends on obsolete libgnome2-vfs-perl that will go away during the Buster cycle Marked as fixed in versions shutter/0.99.2-2. Bug #870418 [shutter] shutter: Depends on obsolete libgnome2-vfs-p

Bug#1006196: mozjs91: FTBFS on mipsel (eller): non262/regress/regress-303213.js: out of memory

2022-02-20 Thread Simon McVittie
On Sun, 20 Feb 2022 at 23:59:14 +, Simon McVittie wrote: > I tried building mozjs on the mips(64)el porterbox 'eller' to test my > earlier commit that resolved a build failure, and it now fails on eller > with a test failure instead: ... > FAILED! integer overflow in js : Expected value 'Inte

Processed: Re: Bug#1006152: mozjs91: FTBFS on i386: test262/built-ins/Date/UTC/fp-evaluation-order.js

2022-02-20 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1755531 Bug #1006152 [src:mozjs91] mozjs91: FTBFS on i386: test262/built-ins/Date/UTC/fp-evaluation-order.js Set Bug forwarded-to-address to 'https://bugzilla.mozilla.org/show_bug.cgi?id=1755531'. -- 10061

Bug#1006152: mozjs91: FTBFS on i386: test262/built-ins/Date/UTC/fp-evaluation-order.js

2022-02-20 Thread Simon McVittie
Control: forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1755531 On Sat, 19 Feb 2022 at 22:38:34 +, Simon McVittie wrote: > After applying patches to fix compilation on i386 and mipsel (see commits > 3f0f229d, 585dadd4) there is a test failure unresolved on i386: > > ## test262/buil

Processed: closing 973059

2022-02-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 973059 1.9-1 Bug #973059 [src:logging-tree] logging-tree: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13 Marked as fixed in versions logging-tree/1.9-1. Bug #973059 [src:logging-tree] loggin

Processed: unarchiving 870418, reopening 870418, unarchiving 886145, reopening 886145, unarchiving 724871 ...

2022-02-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # src:shutter was reintroduced: > https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org > unarchive 870418 Bug #870418 {Done: Debian FTP Masters } [shutter] shutter: Depends on obsolete libgnome2-vfs-per

Processed: unarchiving 973059, reopening 973059

2022-02-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # src:logging-tree was reintroduced: > https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org > unarchive 973059 Bug #973059 {Done: Debian FTP Masters } [src:logging-tree] logging-tree: FTBFS: dh_auto_tes

Bug#1006196: mozjs91: FTBFS on mipsel (eller): non262/regress/regress-303213.js: out of memory

2022-02-20 Thread Simon McVittie
Source: mozjs91 Version: 91.6.0-1 Severity: serious Tags: ftbfs I tried building mozjs on the mips(64)el porterbox 'eller' to test my earlier commit that resolved a build failure, and it now fails on eller with a test failure instead: ## non262/regress/regress-303213.js: rc = 0, run time = 0.1473

Processed: reassign 996706 to mariadb-server-core-10.6, reassign 993219 to mariadb-server-core-10.6 ...

2022-02-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 996706 mariadb-server-core-10.6 1:10.6.5-1 Bug #996706 [mariadb-server-core] mariadb-server-10.5: run directory is not created in multi-instance mode Warning: Unknown package 'mariadb-server-core' Bug reassigned from package 'mariadb-ser

Processed: your mail

2022-02-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1005977 normal Bug #1005977 [fwupd] fwupd: Cannot update anymore, fwupdx64.efi... cannot be found Severity set to 'normal' from 'grave' > End of message, stopping processing here. Please contact me if you need assistance. -- 1005977: h

Bug#1000928: marked as done (codelite: Please upgrade to llvm-toolchain-12 or 13)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 23:03:39 + with message-id and subject line Bug#997219: fixed in codelite 14.0+dfsg-2 has caused the Debian Bug report #997219, regarding codelite: Please upgrade to llvm-toolchain-12 or 13 to be marked as done. This means that you claim that the problem ha

Bug#997219: marked as done (codelite: FTBFS: IHunSpell.cpp:67:17: error: use of deleted function ‘std::unordered_set<_Value, _Hash, _Pred, _Alloc>::unordered_set() [with _Value = wxString; _Hash = IHu

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 23:03:39 + with message-id and subject line Bug#997219: fixed in codelite 14.0+dfsg-2 has caused the Debian Bug report #997219, regarding codelite: FTBFS: IHunSpell.cpp:67:17: error: use of deleted function ‘std::unordered_set<_Value, _Hash, _Pred, _Alloc>:

Bug#984159: marked as done (gnubiff: ftbfs with GCC-11)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 23:03:52 + with message-id and subject line Bug#984159: fixed in gnubiff 2.2.17-4 has caused the Debian Bug report #984159, regarding gnubiff: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#997219: marked as done (codelite: FTBFS: IHunSpell.cpp:67:17: error: use of deleted function ‘std::unordered_set<_Value, _Hash, _Pred, _Alloc>::unordered_set() [with _Value = wxString; _Hash = IHu

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 23:03:39 + with message-id and subject line Bug#1000928: fixed in codelite 14.0+dfsg-2 has caused the Debian Bug report #1000928, regarding codelite: FTBFS: IHunSpell.cpp:67:17: error: use of deleted function ‘std::unordered_set<_Value, _Hash, _Pred, _Alloc

Bug#1000928: marked as done (codelite: Please upgrade to llvm-toolchain-12 or 13)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 23:03:39 + with message-id and subject line Bug#1000928: fixed in codelite 14.0+dfsg-2 has caused the Debian Bug report #1000928, regarding codelite: Please upgrade to llvm-toolchain-12 or 13 to be marked as done. This means that you claim that the problem

Bug#1005448: marked as done (ruby-certificate-authority: FTBFS: ERROR: Test "ruby3.0" failed: NoMethodError:)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 22:50:47 + with message-id and subject line Bug#1005448: fixed in ruby-certificate-authority 1.0.0-1 has caused the Debian Bug report #1005448, regarding ruby-certificate-authority: FTBFS: ERROR: Test "ruby3.0" failed: NoMethodError: to be marked as done.

Bug#1005448: marked as pending in ruby-certificate-authority

2022-02-20 Thread Antonio Terceiro
Control: tag -1 pending Hello, Bug #1005448 in ruby-certificate-authority 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/ruby-team/ruby-certificate-authority/-

Processed: Bug#1005448 marked as pending in ruby-certificate-authority

2022-02-20 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1005448 [src:ruby-certificate-authority] ruby-certificate-authority: FTBFS: ERROR: Test "ruby3.0" failed: NoMethodError: Added tag(s) pending. -- 1005448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005448 Debian Bug Tracking System Cont

Processed: Re: Bug#1005920 closed by Debian FTP Masters (reply to Julien Puydt ) (Bug#1005920: fixed in coq-doc 8.15.0-2)

2022-02-20 Thread Debian Bug Tracking System
Processing control commands: > found -1 8.15.0-2 Bug #1005920 {Done: Julien Puydt } [src:coq-doc] coq-doc: FTBFS: Error: Library "zarith" not found. Marked as found in versions coq-doc/8.15.0-2; no longer marked as fixed in versions coq-doc/8.15.0-2 and reopened. -- 1005920: https://bugs.debia

Bug#1005920: closed by Debian FTP Masters (reply to Julien Puydt ) (Bug#1005920: fixed in coq-doc 8.15.0-2)

2022-02-20 Thread Andreas Beckmann
Control: found -1 8.15.0-2 This looks like more missing Build-Depends(-Indep): [...] Running[3870]: (cd _build/default/doc && /usr/bin/env sphinx-build -q -W -b html sphinx refman-html) Running[3871]: (cd _build/default/doc && /usr/bin/env sphinx-build -q -W -b latex sphinx refman-pdf) Command

Bug#1005448: ruby-certificate-authority: FTBFS: ERROR: Test "ruby3.0" failed: NoMethodError:

2022-02-20 Thread Antonio Terceiro
Control: forwarded -1 https://github.com/cchandler/certificate_authority/issues/61 I tried updating to the latest upstream release, and this issue is still there. It's caused by the fact that ruby3.0 now carries version 3.0.0 of the openssl ruby extension, and this packages is not compatible with

Processed: Re: ruby-certificate-authority: FTBFS: ERROR: Test "ruby3.0" failed: NoMethodError:

2022-02-20 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/cchandler/certificate_authority/issues/61 Bug #1005448 [src:ruby-certificate-authority] ruby-certificate-authority: FTBFS: ERROR: Test "ruby3.0" failed: NoMethodError: Set Bug forwarded-to-address to 'https://github.com/cchandler/cer

Bug#1004037: marked as done (src:plink2: fails to migrate to testing for too long: autopkgtest regression)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 21:04:03 + with message-id and subject line Bug#1004037: fixed in plink2 2.00~a3-220218+dfsg-1 has caused the Debian Bug report #1004037, regarding src:plink2: fails to migrate to testing for too long: autopkgtest regression to be marked as done. This mean

Bug#1000782: marked as done (plink2: autopkgtest regression: Segmentation fault)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 21:04:03 + with message-id and subject line Bug#1000782: fixed in plink2 2.00~a3-220218+dfsg-1 has caused the Debian Bug report #1000782, regarding plink2: autopkgtest regression: Segmentation fault to be marked as done. This means that you claim that the p

Processed: severity of 1004392 is normal

2022-02-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1004392 normal Bug #1004392 {Done: Ansgar } [systemd] systemd: Incorrect location of configuration files Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1004392: h

Bug#1004037: Segmentation fault in plink2 (Was: src:plink2: fails to migrate to testing for too long: autopkgtest regression)

2022-02-20 Thread Andreas Tille
Cool! This finally works. Thanks a lot for your patience, Andreas. Am Sun, Feb 20, 2022 at 09:43:10AM -0800 schrieb Chris Chang: > Hmm. Ordinarily, that download link would be fine. I had not updated it > this time because the issue only affects gcc 11+, so it did not affect any > of the preco

Bug#1001341: marked as done (genetic: autopkgtest needs update for python3.10: 'Sequence' from 'collections' is removed)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 19:49:18 + with message-id and subject line Bug#1001341: fixed in genetic 0.1.1b+git20170527.98255cb-3 has caused the Debian Bug report #1001341, regarding genetic: autopkgtest needs update for python3.10: 'Sequence' from 'collections' is removed to be mark

Bug#1001489: marked as done (twodict: (autopkgtest) needs update for python3.10: 'collections' has no attribute 'KeysView')

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 19:34:39 + with message-id and subject line Bug#1001489: fixed in twodict 1.2-3 has caused the Debian Bug report #1001489, regarding twodict: (autopkgtest) needs update for python3.10: 'collections' has no attribute 'KeysView' to be marked as done. This me

Bug#990201: CVE-2021-33622 (was: Re: Accepted singularity-container 3.9.5+ds1-1 (source) into experimental)

2022-02-20 Thread Nilesh Patra
Hi Salvatore, On Sun, Feb 20, 2022 at 08:01:34PM +0100, Salvatore Bonaccorso wrote: > >[ Andreas Tille ] > >* Team upload. > >* Version > 3.6.x are closing CVE-2021-33622 > > Closes: #990201 > > Can you help isolate on that? > https://support.sylabs.io/support/solutions/articles/

Bug#1001295: marked as done (dominate: needs update for python3.10: 'Callable' from 'collections' is removed)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 19:18:42 + with message-id and subject line Bug#1001295: fixed in dominate 2.6.0-1 has caused the Debian Bug report #1001295, regarding dominate: needs update for python3.10: 'Callable' from 'collections' is removed to be marked as done. This means that yo

Bug#990201: CVE-2021-33622 (was: Re: Accepted singularity-container 3.9.5+ds1-1 (source) into experimental)

2022-02-20 Thread Salvatore Bonaccorso
Hi Nilesh, hi Andreas, On Sun, Feb 20, 2022 at 02:37:12PM +, Debian FTP Masters wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Format: 1.8 > Date: Sun, 20 Feb 2022 19:27:46 +0530 > Source: singularity-container > Architecture: source > Version: 3.9.5+ds1-1 > Distribution: expe

Bug#996737: marked as done (ksysguard: apt dist-upgrade wants to remove ksysguard due to broken dependencies)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 18:51:23 + with message-id and subject line Bug#1005973: Removed package(s) from unstable has caused the Debian Bug report #996737, regarding ksysguard: apt dist-upgrade wants to remove ksysguard due to broken dependencies to be marked as done. This means

Bug#984337: marked as done (slowmovideo: ftbfs with GCC-11)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 18:50:50 + with message-id and subject line Bug#1005926: Removed package(s) from unstable has caused the Debian Bug report #984337, regarding slowmovideo: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with

Bug#996072: marked as done (gnome-shell-extension-tilix-dropdown: does not declare compatibility with GNOME Shell 41)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 18:49:46 + with message-id and subject line Bug#1005914: Removed package(s) from unstable has caused the Debian Bug report #996072, regarding gnome-shell-extension-tilix-dropdown: does not declare compatibility with GNOME Shell 41 to be marked as done. Thi

Bug#994062: marked as done (gnome-shell-extension-tilix-dropdown: No JS module 'tweener' found in search path)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 18:49:46 + with message-id and subject line Bug#1005914: Removed package(s) from unstable has caused the Debian Bug report #994062, regarding gnome-shell-extension-tilix-dropdown: No JS module 'tweener' found in search path to be marked as done. This means

Bug#993200: marked as done (gnome-shell-extension-tilix-shortcut: does not declare compatibility with GNOME Shell 41)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 18:50:16 + with message-id and subject line Bug#1005915: Removed package(s) from unstable has caused the Debian Bug report #993200, regarding gnome-shell-extension-tilix-shortcut: does not declare compatibility with GNOME Shell 41 to be marked as done. Thi

Bug#959741: marked as done (gnome-shell-extension-tilix-shortcut: it does not appear in Nautilus contextual menu)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 18:50:16 + with message-id and subject line Bug#1005915: Removed package(s) from unstable has caused the Debian Bug report #959741, regarding gnome-shell-extension-tilix-shortcut: it does not appear in Nautilus contextual menu to be marked as done. This me

Processed: Fixed in latest upload already

2022-02-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1005621 1.2.1-2 Bug #1005621 [src:coq-hierarchy-builder] coq-hierarchy-builder: FTBFS: dh_install: error: missing files, aborting Ignoring request to alter fixed versions of bug #1005621 to the same values previously set > thanks Stopping

Bug#1006119: uwsgi: FTBFS with ruby3.0 as default

2022-02-20 Thread Antonio Terceiro
Control: tag -1 + patch On Sat, 19 Feb 2022 14:19:46 +0100 Paul Gevers wrote: > Source: uwsgi > Version: 2.0.20-2 > Severity: serious > Tags: ftbfs > Justification: FTBFS > Control: block -1 by 1004915 > > Dear maintainer, > > I tried to binNMU your package for the ongoing ruby3.0 as default ru

Processed: Re: uwsgi: FTBFS with ruby3.0 as default

2022-02-20 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + patch Bug #1006119 [src:uwsgi] uwsgi: FTBFS with ruby3.0 as default Added tag(s) patch. -- 1006119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1004037: Segmentation fault in plink2 (Was: src:plink2: fails to migrate to testing for too long: autopkgtest regression)

2022-02-20 Thread Chris Chang
Hmm. Ordinarily, that download link would be fine. I had not updated it this time because the issue only affects gcc 11+, so it did not affect any of the precompiled binaries and I wanted to keep the posted source identical to that used to compile those binaries. On the other hand, the only diff

Bug#1004556: marked as done (libmpich-dev: The simplest MPI program compiled with mpich crashes)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 16:34:17 + with message-id and subject line Bug#1004556: fixed in mpich 4.0-2 has caused the Debian Bug report #1004556, regarding libmpich-dev: The simplest MPI program compiled with mpich crashes to be marked as done. This means that you claim that the pr

Bug#978867: marked as done (mpich: ftbfs with autoconf 2.70)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 16:34:17 + with message-id and subject line Bug#978867: fixed in mpich 4.0-2 has caused the Debian Bug report #978867, regarding mpich: ftbfs with autoconf 2.70 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1006162: marked as done (expat: autopkgtest regressions (from CVE-2022-25313 fix))

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 16:34:02 + with message-id and subject line Bug#1006162: fixed in expat 2.4.5-2 has caused the Debian Bug report #1006162, regarding expat: autopkgtest regressions (from CVE-2022-25313 fix) to be marked as done. This means that you claim that the problem ha

Processed: severity of 1006028 is important, tagging 1006028

2022-02-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1006028 important Bug #1006028 [src:php-crypt-gpg] php-crypt-gpg: FTBFS: PHPUnit\Framework\Exception: PHP Fatal error: Uncaught Crypt_GPG_BadPassphraseException: Cannot export private key. Incorrect passphrase provided for keys: "First

Processed: severity of 1006149 is important

2022-02-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1006149 important Bug #1006149 [src:linux] linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 1006149: ht

Bug#1002428: marked as done (python-escript: FTBFS: RuntimeError: Unknown key (ASFLAGS) in dpkg-buildflags:)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 15:38:23 + with message-id <4b1a809a-f560-4a93-8e5b-88303a8f7...@sceal.ie> and subject line Fixed in last upload has caused the Debian Bug report #1002428, regarding python-escript: FTBFS: RuntimeError: Unknown key (ASFLAGS) in dpkg-buildflags: to be marked

Processed: Re: Bug#1006009: qtimageformats-opensource-src: FTBFS on mipsel: test failure

2022-02-20 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 libwebp7 1.2.1-7 Bug #1006009 [src:qtimageformats-opensource-src] qtimageformats-opensource-src: FTBFS on mipsel: test failure Bug reassigned from package 'src:qtimageformats-opensource-src' to 'libwebp7'. No longer marked as found in versions qtimagefor

Bug#1006009: qtimageformats-opensource-src: FTBFS on mipsel: test failure

2022-02-20 Thread Dmitry Shachnev
Control: reassign -1 libwebp7 1.2.1-7 Control: affects -1 src:qtimageformats-opensource-src Hi Sebastian and libwebp maintainers! On Fri, Feb 18, 2022 at 10:39:23PM +0100, Sebastian Ramacher wrote: > Source: qtimageformats-opensource-src > Version: 5.15.2-2 > Severity: serious > Tags: ftbfs > Jus

Bug#990201: marked as done (singularity-container: CVE-2021-33622)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 14:37:12 + with message-id and subject line Bug#990201: fixed in singularity-container 3.9.5+ds1-1 has caused the Debian Bug report #990201, regarding singularity-container: CVE-2021-33622 to be marked as done. This means that you claim that the problem has

Bug#997255: marked as done (qd: FTBFS: fpu.cpp:110:25: error: variable or field ‘FC_FUNC_’ declared void)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 14:49:10 + with message-id and subject line Bug#997255: fixed in qd 2.3.23+dfsg.1-1 has caused the Debian Bug report #997255, regarding qd: FTBFS: fpu.cpp:110:25: error: variable or field ‘FC_FUNC_’ declared void to be marked as done. This means that you c

Processed: bug 1006162 is forwarded to https://github.com/libexpat/libexpat/pull/566

2022-02-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1006162 https://github.com/libexpat/libexpat/pull/566 Bug #1006162 [src:expat] expat: autopkgtest regressions (from CVE-2022-25313 fix) Set Bug forwarded-to-address to 'https://github.com/libexpat/libexpat/pull/566'. > thanks Stopping p

Processed: src:opentsne: fails to migrate to testing for too long: FTBFS on i386

2022-02-20 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.6.1-2 Bug #1006177 [src:opentsne] src:opentsne: fails to migrate to testing for too long: FTBFS on i386 Marked as fixed in versions opentsne/0.6.1-2. Bug #1006177 [src:opentsne] src:opentsne: fails to migrate to testing for too long: FTBFS on i386 Marked

Bug#1006177: src:opentsne: fails to migrate to testing for too long: FTBFS on i386

2022-02-20 Thread Paul Gevers
Source: opentsne Version: 0.5.0-2 Severity: serious Control: close -1 0.6.1-2 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1004706 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unsta

Processed: src:lua-system: fails to migrate to testing for too long: autopkgtest regression

2022-02-20 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.2.1-5 Bug #1006176 [src:lua-system] src:lua-system: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions lua-system/0.2.1-5. Bug #1006176 [src:lua-system] src:lua-system: fails to migrate to testing for too long: a

Bug#1006176: src:lua-system: fails to migrate to testing for too long: autopkgtest regression

2022-02-20 Thread Paul Gevers
Source: lua-system Version: 0.2.1-2 Severity: serious Control: close -1 0.2.1-5 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1004099 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and uns

Processed: src:lua-say: fails to migrate to testing for too long: autopkgtest regression

2022-02-20 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.3-1-7 Bug #1006175 [src:lua-say] src:lua-say: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions lua-say/1.3-1-7. Bug #1006175 [src:lua-say] src:lua-say: fails to migrate to testing for too long: autopkgtest regr

Bug#1006175: src:lua-say: fails to migrate to testing for too long: autopkgtest regression

2022-02-20 Thread Paul Gevers
Source: lua-say Version: 1.3-1-5 Severity: serious Control: close -1 1.3-1-7 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1004098 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstab

Processed: src:lua-mediator: fails to migrate to testing for too long: autopkgtest regression

2022-02-20 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.1.2-0-6 Bug #1006174 [src:lua-mediator] src:lua-mediator: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions lua-mediator/1.1.2-0-6. Bug #1006174 [src:lua-mediator] src:lua-mediator: fails to migrate to testing f

Bug#1006174: src:lua-mediator: fails to migrate to testing for too long: autopkgtest regression

2022-02-20 Thread Paul Gevers
Source: lua-mediator Version: 1.1.2-0-3 Severity: serious Control: close -1 1.1.2-0-6 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1004097 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing a

Bug#1006172: src:lepton-eda: fails to migrate to testing for too long: FTBFS on s390x

2022-02-20 Thread Paul Gevers
Source: lepton-eda Version: 1.9.16-3 Severity: serious Control: close -1 1.9.17-2 X-Debbugs-CC: debian-s3...@lists.debian.org Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between

Processed: src:lua-cliargs: fails to migrate to testing for too long: autopkgtest regression

2022-02-20 Thread Debian Bug Tracking System
Processing control commands: > close -1 3.0-2-4 Bug #1006173 [src:lua-cliargs] src:lua-cliargs: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions lua-cliargs/3.0-2-4. Bug #1006173 [src:lua-cliargs] src:lua-cliargs: fails to migrate to testing for too lo

Bug#1006173: src:lua-cliargs: fails to migrate to testing for too long: autopkgtest regression

2022-02-20 Thread Paul Gevers
Source: lua-cliargs Version: 3.0-2-1 Severity: serious Control: close -1 3.0-2-4 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1004096 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and un

Processed: src:lepton-eda: fails to migrate to testing for too long: FTBFS on s390x

2022-02-20 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.9.17-2 Bug #1006172 [src:lepton-eda] src:lepton-eda: fails to migrate to testing for too long: FTBFS on s390x Marked as fixed in versions lepton-eda/1.9.17-2. Bug #1006172 [src:lepton-eda] src:lepton-eda: fails to migrate to testing for too long: FTBFS o

Processed: notfound 1005891 in 1.1.0+ds1-1

2022-02-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1005891 1.1.0+ds1-1 Bug #1005891 {Done: Shengjing Zhu } [src:runc] runc: failing autopkgtest on one of ci.d.n amd64 workers No longer marked as found in versions runc/1.1.0+ds1-1. > thanks Stopping processing here. Please contact me if

Bug#1005891: marked as done (runc: failing autopkgtest on one of ci.d.n amd64 workers)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 21:36:57 +0800 with message-id and subject line Re: Bug#1005891: runc: failing autopkgtest on one of ci.d.n amd64 workers has caused the Debian Bug report #1005891, regarding runc: failing autopkgtest on one of ci.d.n amd64 workers to be marked as done. This

Bug#1005891: runc: failing autopkgtest on one of ci.d.n amd64 workers

2022-02-20 Thread Paul Gevers
Hi, On 20-02-2022 11:04, Shengjing Zhu wrote: That's great to know. Could you retry runc's autopkgtest on ci-worker13. If it succeeds, can we close this bug? I hit the retry button three times, two of those were executed on ci-worker13 and all three passed. Paul OpenPGP_signature Descript

Processed: Re: Bug#1001001 closed by Salvatore Bonaccorso (Re: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204!)

2022-02-20 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1001001 {Done: Salvatore Bonaccorso } [src:linux] linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204! 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to r

Bug#1001001: closed by Salvatore Bonaccorso (Re: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204!)

2022-02-20 Thread Paul Gevers
Control: reopen -1 Control: found -1 5.10.84-1 Hi, Sad to say, but this week we had two hangs again. The one on ci-worker-arm64-06 had this: Feb 15 08:51:12 ci-worker-arm64-06 kernel: kernel BUG at include/linux/swapops.h:204! Feb 15 08:51:12 ci-worker-arm64-06 kernel: Internal error: Oops -

Processed: bug 1005527 is forwarded to https://github.com/python-hyper/wsproto/issues/169, tagging 1005527

2022-02-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1005527 https://github.com/python-hyper/wsproto/issues/169 Bug #1005527 [src:python-wsproto] python-wsproto: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13 Set Bug forwar

Bug#993241: marked as done (minidlna FTBFS: configure: error: Could not find libid3tag)

2022-02-20 Thread Debian Bug Tracking System
Your message dated Sun, 20 Feb 2022 10:50:27 + with message-id and subject line Bug#993241: fixed in minidlna 1.3.0+dfsg-2.1 has caused the Debian Bug report #993241, regarding minidlna FTBFS: configure: error: Could not find libid3tag to be marked as done. This means that you claim that the

Bug#1005891: runc: failing autopkgtest on one of ci.d.n amd64 workers

2022-02-20 Thread Shengjing Zhu
On Sun, Feb 20, 2022 at 6:00 PM Paul Gevers wrote: > > Hi, > > On 20-02-2022 09:20, Shengjing Zhu wrote: > > It's because ci-worker13 still runs on the buster kernel. > > > > Any chance we can upgrade ci-worker13 to bullseye? So we can have a > > consistent testbed. Otherwise I can work around tha

Bug#1005891: runc: failing autopkgtest on one of ci.d.n amd64 workers

2022-02-20 Thread Paul Gevers
Hi, On 20-02-2022 09:20, Shengjing Zhu wrote: It's because ci-worker13 still runs on the buster kernel. Any chance we can upgrade ci-worker13 to bullseye? So we can have a consistent testbed. Otherwise I can work around that by disabling relevant failed tests. That wasn't possible until a cou

Processed: ruby3.0 defaults

2022-02-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1004915 by 1005448 Bug #1004915 [release.debian.org] transition: ruby2.7-rm 1004915 was blocked by: 1006119 1001217 1001022 998499 1005947 1004915 was not blocking any bugs. Added blocking bug(s) of 1004915: 1005448 > block 1004915 by 100542

Processed: ruby3.0 defaults

2022-02-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1004915 by 1001022 Bug #1004915 [release.debian.org] transition: ruby2.7-rm 1004915 was blocked by: 1005947 1001217 1004915 was blocking: 1006119 Added blocking bug(s) of 1004915: 1001022 > block 1004915 by 998499 Bug #1004915 [release.debia

Bug#995224: [Debian-med-packaging] Bug#995224: relion-cuda: FTBFS with cub 1.14

2022-02-20 Thread Sascha Steinbiss
Hi Andreas, thanks for your quick reply! On 19.02.22 22:17, Andreas Beckmann wrote: > On 19/02/2022 20.13, Sascha Steinbiss wrote: >>     79 | #error The version of CUB in your include path is not compatible >> with this release of Thrust. CUB is now included in the CUDA Toolkit, so >> you no lon

Bug#1006149: linux-image-5.16.0-1-amd64: [RKL] hard lock during init with >1 connected displays & 0500 chipset

2022-02-20 Thread Felix Miata
Package: src:linux Version: 5.16.7-2 Followup-For: Bug #1006149 Upstream fix is in 5.17rc4 per https://gitlab.freedesktop.org/drm/intel/-/issues/4762 CPU, chipset and IGP were all released >5 months prior to Bullseye release, early 2021. -- Package-specific info: ** Version: Linux version 5.16.0

Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads

2022-02-20 Thread Petra R.-P.
Hello Diederik, Thanks for your quick reply: Am Sa., 19. Feb. 2022, um 22:36 +0100 schrieb Diederik de Haas : > On Saturday, 19 February 2022 22:04:14 CET Petra R.-P. wrote: > > Package: src:linux > > Version: 5.16.7-2 [...] > > pn firmware-iwlwifi > > I see you don't have firmware-i

Bug#1005891: runc: failing autopkgtest on one of ci.d.n amd64 workers

2022-02-20 Thread Shengjing Zhu
On Thu, Feb 17, 2022 at 4:39 AM Paul Gevers wrote: > > Source: runc > Version: 1.1.0+ds1-1 > Severity: serious > X-Debbugs-CC: debian...@lists.debian.org > Tags: sid bookworm > User: debian...@lists.debian.org > Usertags: flaky > > Dear maintainer(s), > > I looked at the results of the autopkgtest