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

Hi Chris, Am Sat, Feb 19, 2022 at 11:37:34PM -0800 schrieb Chris Chang: > To elaborate: when I look at > https://salsa.debian.org/med-team/plink2/-/tree/master , I can see that > plink2.cc, include/plink2_base.h, and include/plink2_base.cc don't have the > same contents as the v2.00a3-20220218

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

To elaborate: when I look at https://salsa.debian.org/med-team/plink2/-/tree/master , I can see that plink2.cc, include/plink2_base.h, and include/plink2_base.cc don't have the same contents as the v2.00a3-20220218 GitHub tag/release. So I don't know where you grabbed the code from this time, but

Bug#1006038: git-remote-hg: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2

Control: forwarded -1 https://github.com/mnauw/git-remote-hg/issues/48 On Sat, 2022-02-19 at 07:31 +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. This appears to be caused by git 1:2.35.1-1 in unstable, the autopkgtests regressed

Processed: Re: Bug#1006038: git-remote-hg: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2

Processing control commands: > forwarded -1 https://github.com/mnauw/git-remote-hg/issues/48 Bug #1006038 [src:git-remote-hg] git-remote-hg: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2 Set Bug forwarded-to-address to 'https://github.com/mnauw/git-remote-hg/issues/48'. --

Processed: Re: Bug#1006162: expat: autopkgtest regressions (from CVE-2022-25313 fix)

Processing control commands: > tags -1 +confirmed Bug #1006162 [src:expat] expat: autopkgtest regressions (from CVE-2022-25313 fix) Added tag(s) confirmed. -- 1006162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006162 Debian Bug Tracking System Contact ow...@bugs.debian.org with

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

Control: tags -1 +confirmed Hi Salvatore, On Sun, Feb 20, 2022 at 8:15 AM Salvatore Bonaccorso wrote: > There appears to be regressions from the CVE-2022-25313 fix in 2.4.5. > They are known already upstream, cf. > https://github.com/NixOS/nixpkgs/pull/160826#issuecomment-1046074523 > > I will

Processed: affects 1006162, affects 1006162

Processing commands for cont...@bugs.debian.org: > # fix typo > affects 1006162 - src;python3.9 Bug #1006162 [src:expat] expat: autopkgtest regressions (from CVE-2022-25313 fix) Removed indication that 1006162 affects src;python3.9 > affects 1006162 + src:python3.9 Bug #1006162 [src:expat]

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

Source: expat Version: 2.4.5-1 Severity: serious Justification: autopkgtest regression X-Debbugs-Cc: car...@debian.org Control: affects -1 src:libxml-parser-perl,src:python2.7,src:python3.10,src;python3.9 Hi Laszlo, There appears to be regressions from the CVE-2022-25313 fix in 2.4.5. They are

Processed: expat: autopkgtest regressions (from CVE-2022-25313 fix)

Processing control commands: > affects -1 src:libxml-parser-perl,src:python2.7,src:python3.10,src;python3.9 Bug #1006162 [src:expat] expat: autopkgtest regressions (from CVE-2022-25313 fix) Added indication that 1006162 affects src:libxml-parser-perl, src:python2.7, src:python3.10, and

Bug#993350: xsane: Scanimage detects scanner but Xsane won't start it

Hi, after updating libsane1 yesterday xsane works as expected. Georg

Processed: your mail

Processing commands for cont...@bugs.debian.org: > # https://salsa.debian.org/dpward/sane-backends.git develop > tags 1005737 + patch Bug #1005737 [sane-utils] Purging sane-utils deletes the scanner group, created by libsane1 Added tag(s) patch. > tags 1005736 + patch Bug #1005736 [sane-utils]

Processed: your mail

Processing commands for cont...@bugs.debian.org: > retitle 1005737 Purging sane-utils deletes the scanner group, created by > libsane1 Bug #1005737 [sane-utils] Purging package deletes the scanner group, which belongs to system Changed Bug title to 'Purging sane-utils deletes the scanner group,

Bug#1005961: marked as done (nq,fq: trying to overwrite '/usr/bin/fq', which is also in package nq 0.3.1-4)

Your message dated Sat, 19 Feb 2022 22:48:52 + with message-id and subject line Bug#1005961: fixed in fq 0.0.5-1 has caused the Debian Bug report #1005961, regarding nq,fq: trying to overwrite '/usr/bin/fq', which is also in package nq 0.3.1-4 to be marked as done. This means that you claim

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

Source: mozjs91 Version: 91.6.0-1 Severity: serious Tags: ftbfs After applying patches to fix compilation on i386 and mipsel (see commits 3f0f229d, 585dadd4) there is a test failure unresolved on i386: ## test262/built-ins/Date/UTC/fp-evaluation-order.js: rc = 3, run time = 0.022397

Processed: reassign 1006128 to src:meta-kde, tagging 1002658, tagging 1006132

Processing commands for cont...@bugs.debian.org: > reassign 1006128 src:meta-kde 5:111 Bug #1006128 [kde] kde: Keyboard Control key does not work in KDE on Debian 11 Warning: Unknown package 'kde' Bug reassigned from package 'kde' to 'src:meta-kde'. Ignoring request to alter found versions of bug

Processed: Re: playitslowly doesn't start (hasn't for awhile)

Processing control commands: > found -1 1.5.0-1 Bug #1006017 [playitslowly] playitslowly doesn't start (hasn't for awhile) Marked as found in versions playitslowly/1.5.0-1. -- 1006017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006017 Debian Bug Tracking System Contact

Bug#1006017: playitslowly doesn't start (hasn't for awhile)

Followup-For: Bug #1006017 Control: found -1 1.5.0-1 This seems to go back to stretch: # xvfb-run playitslowly Traceback (most recent call last): File "", line 890, in _find_spec AttributeError: 'DynamicImporter' object has no attribute 'find_spec' During handling of the above exception,

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

On Saturday, 19 February 2022 22:04:14 CET Petra R.-P. wrote: > Package: src:linux > Version: 5.16.7-2 > > This new kernel version does not boot on two fairly similar > old IBM T41 Thinkpads. > ... > linux-image-5.15.0-3-686, which I am using to write this > message, runs fine. > > pn

Bug#1002658: marked as done (FTBFS with OCaml 4.13.1)

Your message dated Sat, 19 Feb 2022 21:20:52 + with message-id and subject line Bug#1002658: fixed in xen 4.16.0+51-g0941d6cb-1 has caused the Debian Bug report #1002658, regarding FTBFS with OCaml 4.13.1 to be marked as done. This means that you claim that the problem has been dealt with.

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

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 longer need to use your own checkout of CUB. Define THRUST_IGNORE_CUB_VERSION_CHECK to ignore

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

Package: src:linux Version: 5.16.7-2 Severity: critical Justification: breaks the whole system Dear Maintainer, This new kernel version does not boot on two fairly similar old IBM T41 Thinkpads. What reproducibly happens is as follows: After the lines Loading Linux 5.16.0-1-686 ...

Bug#1005419: marked as done (Fails to build with xtables-addons 3.19)

Your message dated Sat, 19 Feb 2022 20:51:55 + with message-id and subject line Bug#1005419: fixed in west-chamber 20100405+svn2007.r124-14 has caused the Debian Bug report #1005419, regarding Fails to build with xtables-addons 3.19 to be marked as done. This means that you claim that

Processed: Re: Bug#1003894: fixed in h2database 2.1.210-1

Processing control commands: > fixed -1 1.4.197-4+deb10u1 Bug #1003894 {Done: Markus Koschany } [src:h2database] h2database: CVE-2021-42392 Marked as fixed in versions h2database/1.4.197-4+deb10u1. > fixed -1 1.4.197-4+deb11u1 Bug #1003894 {Done: Markus Koschany } [src:h2database] h2database:

Bug#1003894: fixed in h2database 2.1.210-1

Control: fixed -1 1.4.197-4+deb10u1 Control: fixed -1 1.4.197-4+deb11u1 signature.asc Description: This is a digitally signed message part

Bug#1006144: pychromecast: autopkgtest regression: ModuleNotFoundError: No module named 'requests'

Source: pychromecast Version: 9.4.0-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of pychromecast the autopkgtest of pychromecast fails in testing when that autopkgtest is run with the

Bug#1006143: kas: autopkgtest regression: ModuleNotFoundError: No module named 'snack'

Source: kas Version: 2.6.3-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of kas the autopkgtest of kas fails in testing when that autopkgtest is run with the binary packages of kas

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

Hi all, greetings from the Debian Med Sprint 2021! [...] > /usr/bin/nvcc -M -D__CUDACC__ > /build/relion-cuda-3.1.0/src/acc/cuda/cuda_projector_plan.cu -o >

Processed: Add additional command line options

Processing commands for cont...@bugs.debian.org: > retitle 1005993 Add additional command line options Bug #1005993 [diodon] diodon: The man page is entirely useless, violating section 12.1 of policy Changed Bug title to 'Add additional command line options' from 'diodon: The man page is

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 1005479 normal Bug #1005479 [src:toil] toil: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13 Severity set to 'normal' from 'serious' > thanks Stopping processing here.

Processed: ruby3.0

Processing commands for cont...@bugs.debian.org: > block 1004915 by 1005947 Bug #1004915 [release.debian.org] transition: ruby2.7-rm 1004915 was blocked by: 1001217 1004915 was blocking: 1006119 Added blocking bug(s) of 1004915: 1005947 > thanks Stopping processing here. Please contact me if you

Processed: ruby3.0

Processing commands for cont...@bugs.debian.org: > block 1004915 by 1001217 Bug #1004915 [release.debian.org] transition: ruby2.7-rm 1004915 was not blocked by any bugs. 1004915 was blocking: 1006119 Added blocking bug(s) of 1004915: 1001217 > thanks Stopping processing here. Please contact me

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

Source: supertuxkart Version: 1.3+dfsg1-2 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org supertuxkart FTBFS on armhf: [ 26%] Building ASM object

Bug#1005890: marked as done (gsocket: flaky autopkgtest)

Your message dated Sat, 19 Feb 2022 17:33:46 + with message-id and subject line Bug#1005890: fixed in gsocket 1.4.33-2 has caused the Debian Bug report #1005890, regarding gsocket: flaky autopkgtest to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#287371: [xml/sgml-pkgs] Bug#287371: xsltproc: Probable memory leak (when using document()?)

On 2022-02-19 18:01:52 +0100, Mattia Rizzolo wrote: > On Thu, Feb 10, 2022 at 01:08:33PM +0100, Vincent Lefevre wrote: > > This is no different than CVE-2013-0338 and CVE-2013-0339[*]. The > > point is that from a small document, one can exhaust the memory > > of the machine. CVE-2013-0338 and

Bug#1006041: marked as done (pymarkups: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13)

Your message dated Sat, 19 Feb 2022 17:05:05 + with message-id and subject line Bug#1006041: fixed in pymarkups 3.1.3-2 has caused the Debian Bug report #1006041, regarding pymarkups: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13 to be

Bug#1005787: marked as done (redis: CVE-2022-0543)

Your message dated Sat, 19 Feb 2022 17:02:39 + with message-id and subject line Bug#1005787: fixed in redis 5:5.0.14-1+deb10u2 has caused the Debian Bug report #1005787, regarding redis: CVE-2022-0543 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1005787: marked as done (redis: CVE-2022-0543)

Your message dated Sat, 19 Feb 2022 17:02:12 + with message-id and subject line Bug#1005787: fixed in redis 5:6.0.16-1+deb11u2 has caused the Debian Bug report #1005787, regarding redis: CVE-2022-0543 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1005230: marked as done (chromium: essential dependencies (libgtk-3-0) no longer depended on)

Your message dated Sat, 19 Feb 2022 17:02:07 + with message-id and subject line Bug#1005230: fixed in chromium 98.0.4758.102-1~deb11u1 has caused the Debian Bug report #1005230, regarding chromium: essential dependencies (libgtk-3-0) no longer depended on to be marked as done. This means

Bug#287371: [xml/sgml-pkgs] Bug#287371: xsltproc: Probable memory leak (when using document()?)

On Thu, Feb 10, 2022 at 01:08:33PM +0100, Vincent Lefevre wrote: > This is no different than CVE-2013-0338 and CVE-2013-0339[*]. The > point is that from a small document, one can exhaust the memory > of the machine. CVE-2013-0338 and CVE-2013-0339 are about entity > expansion, but there are the

Bug#1006127: wireless-regdb stable policy

Hi, On Sat, Feb 19, 2022 at 04:30:35PM +, Jiaxun Yang wrote: > > > 在 2022/2/19 16:27, Salvatore Bonaccorso 写道: > > Hi, > > > > On Sat, Feb 19, 2022 at 02:49:32PM +, Jiaxun Yang wrote: > > > Package: wireless-regdb > > > Version: 2021.08.28-1 > > > Severity: grave > > > > > > Dear

Processed: Bug#1006041 marked as pending in pymarkups

Processing control commands: > tag -1 pending Bug #1006041 [src:pymarkups] pymarkups: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13 Added tag(s) pending. -- 1006041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006041 Debian Bug

Bug#1006041: marked as pending in pymarkups

Control: tag -1 pending Hello, Bug #1006041 in pymarkups 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:

Processed: myspell: do not ship with bookworm

Processing control commands: > block -1 by 1006131 1006132 Bug #1006134 [src:myspell] myspell: do not ship with bookworm 1006134 was not blocked by any bugs. 1006134 was not blocking any bugs. Added blocking bug(s) of 1006134: 1006131 and 1006132 -- 1006134:

Bug#1006134: myspell: do not ship with bookworm

Source: myspell Version: 1:3.0+pre3.1-24.2 Severity: serious Tags: bookworm sid Control: block -1 by 1006131 1006132 We don't want to release myspell with bookworm. The only 2 packages that Build-Depends on myspell-tools are marked as blockers. Anything else that I found only uses myspell-tools

Bug#1006132: ifrench-gut: please stop build-depending on myspell-tools

Source: ifrench-gut Version: 1:1.0-32.1 Severity: serious Dear maintainer, we plan to remove src:myspell really soon, and together with it also the package "myspell-tools". Your package still depends on it. Please see whether you can move whatever the package is doing to hunspell-tools, or

Bug#1006131: rus-ispell: please stop build-depending on myspell-tools

Source: rus-ispell Version: 0.99g5-27 Severity: serious Dear maintainer, we plan to remove src:myspell really soon, and together with it also the package "myspell-tools". Your package still depends on it. Please see whether you can move whatever the package is doing to hunspell-tools, or

Bug#1006127: wireless-regdb stable policy

在 2022/2/19 16:27, Salvatore Bonaccorso 写道: Hi, On Sat, Feb 19, 2022 at 02:49:32PM +, Jiaxun Yang wrote: Package: wireless-regdb Version: 2021.08.28-1 Severity: grave Dear Maintainer wireless-regdb stores regulation information for various regions. It's importatnt to keep it updated

Bug#1006127: wireless-regdb stable policy

Hi, On Sat, Feb 19, 2022 at 02:49:32PM +, Jiaxun Yang wrote: > Package: wireless-regdb > Version: 2021.08.28-1 > Severity: grave > > Dear Maintainer > > wireless-regdb stores regulation information for various regions. It's > importatnt to keep > it updated on every system to ensure legal

Bug#1006037: marked as done (gnome-initial-setup: FTBFS: build-dependency not installable: libgnome-desktop-4-dev)

Your message dated Sat, 19 Feb 2022 16:03:58 + with message-id and subject line Bug#1006037: fixed in gnome-desktop 42~beta-1 has caused the Debian Bug report #1006037, regarding gnome-initial-setup: FTBFS: build-dependency not installable: libgnome-desktop-4-dev to be marked as done. This

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

If you build off the current head, the version string should say "18 Feb 2022", not "17 Feb 2022". On Sat, Feb 19, 2022 at 7:02 AM Andreas Tille wrote: > Hi again, > > Am Sat, Feb 19, 2022 at 12:28:21AM -0800 schrieb Chris Chang: > > Ok, new release/tag created. > > I've built the new version

Processed (with 1 error): Re: Bug#1006037: gnome-initial-setup: FTBFS: build-dependency not installable: libgnome-desktop-4-dev

Processing commands for cont...@bugs.debian.org: > reassign 1006037 src:gnome-desktop Bug #1006037 [gnome-desktop] gnome-initial-setup: FTBFS: build-dependency not installable: libgnome-desktop-4-dev Bug reassigned from package 'gnome-desktop' to 'src:gnome-desktop'. Ignoring request to alter

Processed: Re: Bug#1006037: gnome-initial-setup: FTBFS: build-dependency not installable: libgnome-desktop-4-dev

Processing commands for cont...@bugs.debian.org: > reassign 1006037 gnome-desktop Bug #1006037 [src:gnome-initial-setup] gnome-initial-setup: FTBFS: build-dependency not installable: libgnome-desktop-4-dev Bug reassigned from package 'src:gnome-initial-setup' to 'gnome-desktop'. No longer marked

Bug#1006127: wireless-regdb stable policy

Package: wireless-regdb Version: 2021.08.28-1 Severity: grave Dear Maintainer wireless-regdb stores regulation information for various regions. It's importatnt to keep it updated on every system to ensure legal compliance on user's system. For example, China resctrcted transmission power for

Bug#1005311:

Hi, I tested the nvidia legacy 340.108-12+b1 driver with xserver-xorg-core 2:21.1.3-2+b1 (xorg-video-abi-25) and it seems it's working fine by just adding: Section "ServerFlags" Option "IgnoreABI" "1" EndSection in /etc/X11/xorg.conf.d/20-nvidia.conf Is there hope that the legacy 340.108

Processed: bug 1006056 is forwarded to https://github.com/newren/git-filter-repo/issues/344

Processing commands for cont...@bugs.debian.org: > forwarded 1006056 https://github.com/newren/git-filter-repo/issues/344 Bug #1006056 [src:git-filter-repo] git-filter-repo: FTBFS: t9390-filter-repo.sh failed Set Bug forwarded-to-address to

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

Hi again, Am Sat, Feb 19, 2022 at 12:28:21AM -0800 schrieb Chris Chang: > Ok, new release/tag created. I've built the new version now. The bad news is that it keeps on SEGFAULTing for me: ... (gdb) run Starting program: /usr/lib/plink2/plink2-sse3 --debug --pfile tmp_data --export vcf

Bug#997359: marked as done (Inkscape crashes when running as batch without X11)

Your message dated Sat, 19 Feb 2022 14:42:07 + with message-id and subject line Bug#997359: fixed in inkscape 1.1.2-1 has caused the Debian Bug report #997359, regarding Inkscape crashes when running as batch without X11 to be marked as done. This means that you claim that the problem has

Processed: Re: Bug#1006115: linux-image-amd64: System does not boot with 5.16

Processing control commands: > severity -1 important Bug #1006115 [src:linux] linux-image-amd64: System does not boot with 5.16 Severity set to 'important' from 'critical' > tags -1 + moreinfo Bug #1006115 [src:linux] linux-image-amd64: System does not boot with 5.16 Added tag(s) moreinfo. --

Bug#1006115: linux-image-amd64: System does not boot with 5.16

Control: severity -1 important Control: tags -1 + moreinfo On Sat, Feb 19, 2022 at 12:27:11PM +, Julien-Benjamin wrote: > Package: linux-image-amd64 > Version: 5.16.7-2 > Severity: critical > Justification: breaks the whole system > > After upgrading from 5.15 to 5.16 (testing branch), the

Processed: reassign 1006115 to src:linux

Processing commands for cont...@bugs.debian.org: > reassign 1006115 src:linux 5.16.7-2 Bug #1006115 [linux-image-amd64] linux-image-amd64: System does not boot with 5.16 Bug reassigned from package 'linux-image-amd64' to 'src:linux'. No longer marked as found in versions

Processed: tagging 1001217

Processing commands for cont...@bugs.debian.org: > tags 1001217 + ftbfs Bug #1001217 [dislocker] FTBFS against Ruby 3.0 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1001217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001217 Debian

Processed: severity of 1001217 is serious

Processing commands for cont...@bugs.debian.org: > severity 1001217 serious Bug #1001217 [dislocker] FTBFS against Ruby 3.0 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1001217:

Processed: Bug#997359 marked as pending in inkscape

Processing control commands: > tag -1 pending Bug #997359 [inkscape] Inkscape crashes when running as batch without X11 Added tag(s) pending. -- 997359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#997359: marked as pending in inkscape

Control: tag -1 pending Hello, Bug #997359 in inkscape 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:

Bug#990201: Update golang-github-appc-cni to 1.0 (was Re: singularity-container: CVE-2021-33622)

Hi, Am Fri, Feb 18, 2022 at 10:19:01PM +0100 schrieb Andreas Tille: > > So I do not know where this error comes from; or if you have something else > > locally. > > I'll simply revert the version bump ... I did so and uploaded to experimental[1]. I think once all preconditions are in unstable

Processed: uwsgi: FTBFS with ruby3.0 as default

Processing control commands: > block -1 by 1004915 Bug #1006119 [src:uwsgi] uwsgi: FTBFS with ruby3.0 as default 1006119 was not blocked by any bugs. 1006119 was not blocking any bugs. Added blocking bug(s) of 1006119: 1004915 -- 1006119:

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

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 ruby transition. It failed: https://buildd.debian.org/status/package.php?p=uwsgi Paul *** uWSGI

Processed (with 1 error): src:dmrgpp: fails to migrate to testing for too long: autopkgtest regression

Processing control commands: > close -1 6.02-2 Bug #1006118 [src:dmrgpp] src:dmrgpp: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions dmrgpp/6.02-2. Bug #1006118 [src:dmrgpp] src:dmrgpp: fails to migrate to testing for too long: autopkgtest regression

Bug#1006118: src:dmrgpp: fails to migrate to testing for too long: autopkgtest regression

Source: dmrgpp Version: 6.00-2 Severity: serious Control: close -1 6.02-2 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 1003061 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable

Processed: src:lomiri-app-launch: fails to migrate to testing for too long: depends on new non-migrating package

Processing control commands: > close -1 0.1.1-1 Bug #1006117 [src:lomiri-app-launch] src:lomiri-app-launch: fails to migrate to testing for too long: depends on new non-migrating package Marked as fixed in versions lomiri-app-launch/0.1.1-1. Bug #1006117 [src:lomiri-app-launch]

Bug#1006117: src:lomiri-app-launch: fails to migrate to testing for too long: depends on new non-migrating package

Source: lomiri-app-launch Version: 0.0.90-10 Severity: serious Control: close -1 0.1.1-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than

Bug#1003020: marked as done (openblas breaks hypre autopkgtest on armhf: test times out after 2:47h)

Your message dated Sat, 19 Feb 2022 12:33:55 + with message-id and subject line Bug#1003020: fixed in hypre 2.22.1-7 has caused the Debian Bug report #1003020, regarding openblas breaks hypre autopkgtest on armhf: test times out after 2:47h to be marked as done. This means that you claim

Bug#1006029: gtk+3.0: FTBFS: various icons no longer present in adwaita-icon-theme

On Sat, Feb 19, 2022 at 6:05 AM Simon McVittie wrote: > I think this means adwaita-icon-theme has dropped some icons that GTK 3 > assumes will be present. > > (See also, all the bugs complaining that icons disappeared, most recently > #1005997 - but my understanding is that there is no real

Bug#986487: marked as done (caftools: FTBFS with glibc >= 2.32)

Your message dated Sat, 19 Feb 2022 11:19:13 + with message-id and subject line Bug#986487: fixed in caftools 2.0.3-2 has caused the Debian Bug report #986487, regarding caftools: FTBFS with glibc >= 2.32 to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Re: Bug#1006029: gtk+3.0: FTBFS: various icons no longer present in adwaita-icon-theme

Processing control commands: > reassign -1 adwaita-icon-theme 42~beta-1 Bug #1006029 [src:gtk+3.0] gtk+3.0: FTBFS: dh_auto_test: error: cd debian/build/deb && make -j8 check VERBOSE=1 -k check -j1 returned exit code 2 Bug reassigned from package 'src:gtk+3.0' to 'adwaita-icon-theme'. No longer

Bug#1006029: gtk+3.0: FTBFS: various icons no longer present in adwaita-icon-theme

Control: reassign -1 adwaita-icon-theme 42~beta-1 Control: affects -1 + gtk+3.0 On Sat, 19 Feb 2022 at 07:31:29 +0100, Lucas Nussbaum wrote: > The full build log is available from: > http://qa-logs.debian.net/2022/02/18/gtk+3.0_3.24.31-1_unstable.log This also seems to be an autopkgtest

Bug#972212: marked as done (singularity-container: CVE-2020-15229)

Your message dated Sat, 19 Feb 2022 10:53:19 + with message-id and subject line Bug#972212: fixed in singularity-container 3.9.4+ds2-1 has caused the Debian Bug report #972212, regarding singularity-container: CVE-2020-15229 to be marked as done. This means that you claim that the problem

Bug#970465: marked as done (singularity-container: CVE-2020-25039 CVE-2020-25040)

Your message dated Sat, 19 Feb 2022 10:53:19 + with message-id and subject line Bug#970465: fixed in singularity-container 3.9.4+ds2-1 has caused the Debian Bug report #970465, regarding singularity-container: CVE-2020-25039 CVE-2020-25040 to be marked as done. This means that you claim that

Bug#965040: marked as done (singularity-container: CVE-2020-13845 CVE-2020-13846 CVE-2020-13847)

Your message dated Sat, 19 Feb 2022 10:53:19 + with message-id and subject line Bug#965040: fixed in singularity-container 3.9.4+ds2-1 has caused the Debian Bug report #965040, regarding singularity-container: CVE-2020-13845 CVE-2020-13846 CVE-2020-13847 to be marked as done. This means that

Bug#970453: coq-float looks dead upstream: RM?

Hi, I was looking around at all coq-related packages and found this poor thing, which seems pretty dead. I propose to ask for its removal ; I'll proceed in a few weeks if nobody objects. Cheers, J.Puydt

Bug#1000336: numba: FTBFS with Python 3.10

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 passing tests for the other arches? Drew

Processed: severity of 1006017 is serious

Processing commands for cont...@bugs.debian.org: > severity 1006017 serious Bug #1006017 [playitslowly] playitslowly doesn't start (hasn't for awhile) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1006017:

Bug#1006028: php-crypt-gpg: FTBFS: PHPUnit\Framework\Exception: PHP Fatal error: Uncaught Crypt_GPG_BadPassphraseException: Cannot export private key. Incorrect passphrase provided for keys: "First Ke

Control: tag -1 moreinfo On Sat, 19 Feb 2022 at 07:38:04 +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. Seems like a false-positive to me. It does build here, and also did build on the buildds [0] (and Salsa CI too). Perhaps

Processed: Re: Bug#1006028: php-crypt-gpg: FTBFS: PHPUnit\Framework\Exception: PHP Fatal error: Uncaught Crypt_GPG_BadPassphraseException: Cannot export private key. Incorrect passphrase provided for

Processing control commands: > tag -1 moreinfo 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 Keypair Test Key (do not

Bug#1006110: graphicsmagick: FTBFS on mipsel: test failure

Source: graphicsmagick Version: 1.4+really1.3.37+hg16662-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org graphicsmagick FTBFS on mipsel: PASS: tests/rwfile.tap 629 - WEBP bilevel (lossless) PASS:

Bug#1006061: marked as done (node-deep-for-each: FTBFS: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/module-transformations' is not defined by "exports" in /usr/share/nodejs/@babel/pr

Your message dated Sat, 19 Feb 2022 09:04:21 + with message-id and subject line Bug#1006061: fixed in node-babel7 7.17.4+~cs214.260.190-2 has caused the Debian Bug report #1006061, regarding node-deep-for-each: FTBFS: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath

Bug#1005981: Please migrate away from dpatch

On Fri, Feb 18, 2022 at 02:41:57PM -0800, Bill Poser wrote: > I am the developer of redet. I don't understand this bug report. redet does > not use anything called dpatch so far as I know. Is this something added in > the Debianization of redet downstream from me? Yes, exactly. It's a legacy

Bug#1006061: marked as pending in node-babel

Control: tag -1 pending Hello, Bug #1006061 in node-babel 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:

Processed: Bug#1006061 marked as pending in node-babel

Processing control commands: > tag -1 pending Bug #1006061 [node-jest-debbundle] node-deep-for-each: FTBFS: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/module-transformations' is not defined by "exports" in /usr/share/nodejs/@babel/preset-env/package.json Added tag(s) pending.

Bug#1006014: [Pkg-freeipa-devel] Bug#1006014: FTBFS: void value not ignored as it ought to be

Ryan Tandy kirjoitti 19.2.2022 klo 0.46: Source: bind-dyndb-ldap Version: 11.9-4 Severity: serious Tags: ftbfs Dear Maintainer, bind-dyndb-ldap fails to build from source on amd64: /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time

Bug#1006079: marked as done (node-ipaddr.js: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.)

Your message dated Sat, 19 Feb 2022 08:37:54 + with message-id and subject line Bug#1006079: fixed in node-ipaddr.js 2.0.1~dfsg-3 has caused the Debian Bug report #1006079, regarding node-ipaddr.js: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356. to be marked as

Bug#1006077: marked as done (node-dabh-diagnostics: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.)

Your message dated Sat, 19 Feb 2022 08:37:25 + with message-id and subject line Bug#1006077: fixed in node-dabh-diagnostics 2.0.2-5 has caused the Debian Bug report #1006077, regarding node-dabh-diagnostics: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356. to be

Bug#1006076: marked as done (node-kuler: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.)

Your message dated Sat, 19 Feb 2022 08:37:59 + with message-id and subject line Bug#1006076: fixed in node-kuler 2.0.0-3 has caused the Debian Bug report #1006076, regarding node-kuler: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356. to be marked as done. This

Bug#1006075: marked as done (node-err-code: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.)

Your message dated Sat, 19 Feb 2022 08:37:31 + with message-id and subject line Bug#1006075: fixed in node-err-code 2.0.3+dfsg-3 has caused the Debian Bug report #1006075, regarding node-err-code: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356. to be marked as

Bug#1006071: marked as done (node-autoprefixer: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.)

Your message dated Sat, 19 Feb 2022 08:37:00 + with message-id and subject line Bug#1006071: fixed in node-autoprefixer 10.4.2.0+dfsg1+~cs24.7.3-2 has caused the Debian Bug report #1006071, regarding node-autoprefixer: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line

Bug#1006074: marked as done (node-grunt-legacy-util: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.)

Your message dated Sat, 19 Feb 2022 08:37:48 + with message-id and subject line Bug#1006074: fixed in node-grunt-legacy-util 2.0.1-2 has caused the Debian Bug report #1006074, regarding node-grunt-legacy-util: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356. to be

Bug#1006069: marked as done (node-browser-stdout: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.)

Your message dated Sat, 19 Feb 2022 08:37:05 + with message-id and subject line Bug#1006069: fixed in node-browser-stdout 1.3.1-6 has caused the Debian Bug report #1006069, regarding node-browser-stdout: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356. to be

Bug#1006067: marked as done (node-rai: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.)

Your message dated Sat, 19 Feb 2022 08:38:04 + with message-id and subject line Bug#1006067: fixed in node-rai 0.1.12-7 has caused the Debian Bug report #1006067, regarding node-rai: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356. to be marked as done. This

Bug#1006062: marked as done (node-grunt-contrib-nodeunit: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.)

Your message dated Sat, 19 Feb 2022 08:37:42 + with message-id and subject line Bug#1006062: fixed in node-grunt-contrib-nodeunit 2.0.0-6 has caused the Debian Bug report #1006062, regarding node-grunt-contrib-nodeunit: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line

Bug#1006057: marked as done (node-tildify: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356.)

Your message dated Sat, 19 Feb 2022 08:38:10 + with message-id and subject line Bug#1006057: fixed in node-tildify 2.0.0-4 has caused the Debian Bug report #1006057, regarding node-tildify: FTBFS: Unable to parse '' at /usr/share/perl5/Debian/Dependency.pm line 356. to be marked as done.

  1   2   >