Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

After installing a debug version of glibmm, I've attached the related backtrace showing the glibmm code lines. The "binding.cc" is the glib/glibmm/binding.cc file. The old (working) version doesn't appear to use the related g_quark_from_static_string() function that crashes. -- Ryan Thoryk r

Bug#994971: closed by Debian FTP Masters (reply to Andreas Beckmann ) (Bug#994971: fixed in nvidia-graphics-drivers 470.63.01-1)

Hello ! Just installed 470.63.01-1 this morning and I can confirm that the issue is fixed. I have OpenCL activated without any other action. Thanks a lot for the quick resolution. Have a nice day, --   Pascal Obry /  Magny Les Hameaux (78)   The best way to travel is by means of imagination

Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

I tried force-downgrading the libglibmm package to the Debian Bullseye version (2.66 back to 2.64), the crash goes away, and my audio hardware works again with Jack. -- Ryan Thoryk r...@thoryk.com r...@tliquest.net

Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages

I wanted to chime in on this bug, since I'm getting basically the same issue. I'm running Debian Testing. My situation is a little different, because I'm using an M-Audio firewire device with Jack2 on a VIA VT6315 card, and so I need the firewire module. I recently swapped out the firewire c

Bug#995282: marked as done (amule crashes on start)

Your message dated Fri, 01 Oct 2021 04:04:43 + with message-id and subject line Bug#995282: fixed in amule 1:2.3.3-2 has caused the Debian Bug report #995282, regarding amule crashes on start to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#995349: ncbi-entrez-direct: FTBFS: no required module provides package github.com/fiam/gounidecode/unidecode

Steve Langasek writes: > rchive.go:40:2: no required module provides package > github.com/fiam/gounidecode/unidecode: go.mod file not found in current > directory or any parent directory; see 'go help modules' [etc.] Thanks for the report! AFAICT, my approach to go.mod and go.sum (moving both

Processed: Re: Bug#995392: ghostscript: ps2pdf trashes some characters

Processing control commands: > tags -1 upstream Bug #995392 [ghostscript] ghostscript: ps2pdf trashes some characters Added tag(s) upstream. > forwarded -1 https://bugs.ghostscript.com/show_bug.cgi?id=704478 Bug #995392 [ghostscript] ghostscript: ps2pdf trashes some characters Set Bug forwarded-to

Bug#995392: ghostscript: ps2pdf trashes some characters

Control: tags -1 upstream Control: forwarded -1 https://bugs.ghostscript.com/show_bug.cgi?id=704478 On 2021-09-30 18:49:02 +0200, Jonas Smedegaard wrote: > Quoting Vincent Lefevre (2021-09-30 18:28:51) > > On 2021-09-30 17:18:46 +0200, Jonas Smedegaard wrote: > > > This seems an upstream bug, and

Bug#995362: zint breaks zbar autopkgtest: unable to open file `/tmp/magick-VxkNk3KeW43pSnBYixIpsF9xU8qRmIzE': No such file or directory @ error/constitute.c/ReadImage/614

On Thu, 2021-09-30 at 09:18 -0400, John Scott wrote: > Outside a minimal chroot, on my desktop system, zbarimg seems to > process SVGs just fine. So this may be a case of a Recommends > (somewhere) not being installed wreaking havok, but in my opinion > zbarimg should still not behave this way when

Bug#974792: beignet FTBFS with llvm-toolchain-11

I'm not aware of a fix for this, and beignet is abandoned upstream and mostly useful for old hardware (on newer hardware it is replaced by intel-opencl-icd). However, I may look at it more later (and at least try llvm-toolchain-12, though I'd expect that to be worse if anything). Hence, I'm f

Bug#986709: rsnapshot is stable, not dead

On 2021-09-30 6:13 p.m., Michael Lustfield wrote: On Sun, 26 Sep 2021 13:49:36 -0400 John Brooks wrote: [...] So... My first response was a wordier version of the message you replied to, emphasizing the bit where my opinion is moot. What's written below is as much as I'm willing to dip back

Processed: reassign 994697 to git-annex, found 994697 in git-annex/8.20210903-1, affects 994697

Processing commands for cont...@bugs.debian.org: > reassign 994697 git-annex Bug #994697 [libgit-annex-perl] libgit-annex-perl: Test failure - autopkgtest and build Bug reassigned from package 'libgit-annex-perl' to 'git-annex'. No longer marked as found in versions libgit-annex-perl/0.007-1. Ign

Bug#995424: libgmsh4: SONAME bump without package rename

Package: libgmsh4 Version: 4.8.4+ds1-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org, elb...@debian.org The package name of shared libraries is supposed to follow the SONAME of the library. In the case of libgmsh, the SONAME in testing is libgmsh.so.4.7 and the package should have been name

Bug#986709: rsnapshot is stable, not dead

On Sun, 26 Sep 2021 13:49:36 -0400 John Brooks wrote: > [...] > Michael, > > I think it is important that you clarify or modify your stance given > that upon further inspection by others here, there are no serious > outstanding functional or security issues with the program. Even > self-asser

Bug#995419: rust-utf-8: autopkgtest regression: crate directory not found: /usr/share/cargo/registry/utf-8-0.7.6

It passes when run with only packages from testing. This is not entirely correct, the version of rust-utf-8 in testing has no autopkgtests at all. So this is a case of a newly added (by a newer version of debcargo) test failing, not a case of an existing test regressing. Investigating, it seems

Bug#995392: ghostscript: ps2pdf trashes some characters

Control: notfound -1 9.53.3~dfsg-8 Apologies, I somehow missed the part about pdftotext and the glyph's normal appearance in your original message. I can reproduce that with both files produced by 9.54.0~dfsg-5 but *not* the one produced by 9.53.3~dfsg-8 (attached for reference), using the sam

Processed: Re: ghostscript: ps2pdf trashes some characters

Processing control commands: > notfound -1 9.53.3~dfsg-8 Bug #995392 [ghostscript] ghostscript: ps2pdf trashes some characters Ignoring request to alter found versions of bug #995392 to the same values previously set -- 995392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995392 Debian Bug

Processed: bug 994697 is forwarded to https://git-annex.branchable.com/todo/recent_change_to_fileRef_breaks_reinject_--known/

Processing commands for cont...@bugs.debian.org: > forwarded 994697 > https://git-annex.branchable.com/todo/recent_change_to_fileRef_breaks_reinject_--known/ Bug #994697 [libgit-annex-perl] libgit-annex-perl: Test failure - autopkgtest and build Changed Bug forwarded-to-address to 'https://git-

Processed: bug 994697 is forwarded to https://git-annex.branchable.com/todo/recent_change_to_fileRef_breaks_reinject_--known/?updated

Processing commands for cont...@bugs.debian.org: > forwarded 994697 > https://git-annex.branchable.com/todo/recent_change_to_fileRef_breaks_reinject_--known/?updated Bug #994697 [libgit-annex-perl] libgit-annex-perl: Test failure - autopkgtest and build Set Bug forwarded-to-address to 'https://

Bug#995392: ghostscript: ps2pdf trashes some characters

Hi Vincent, For what it's worth, I do not see the corruption you're describing with `gv chartest-gs.pdf` nor when converting it myself from your input file using versions 9.53.3~dfsg-8 or 9.54.0~dfsg-5. I noticed that your file used a different internal conversion command compared to when I

Processed: Re: Bug#994697: libgit-annex-perl: Test failure - autopkgtest and build

Processing control commands: > tag -1 + confirmed Bug #994697 [libgit-annex-perl] libgit-annex-perl: Test failure - autopkgtest and build Added tag(s) confirmed. -- 994697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994697 Debian Bug Tracking System Contact ow...@bugs.debian.org with pro

Bug#994697: libgit-annex-perl: Test failure - autopkgtest and build

control: tag -1 + confirmed Hello, On Sun 19 Sep 2021 at 05:30PM +02, gregor herrmann wrote: > Package: libgit-annex-perl > Version: 0.007-1 > Severity: serious > Tags: ftbfs sid bookworm > Justification: fails to build from source (but built successfully in the past) > > -BEGIN PGP SIGNED M

Bug#995421: rust-bumpalo: autopkgtest armhf regression: oom_instead_of_bump_pointer_overflow

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

Bug#995419: rust-utf-8: autopkgtest regression: crate directory not found: /usr/share/cargo/registry/utf-8-0.7.6

Source: rust-utf-8 Version: 0.7.6-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 rust-utf-8 the autopkgtest of rust-utf-8 fails in testing when that autopkgtest is run with the binary p

Bug#978773: marked as done (bmake: ftbfs with autoconf 2.70)

Your message dated Thu, 30 Sep 2021 20:34:48 + with message-id and subject line Bug#978773: fixed in bmake 20200710-15 has caused the Debian Bug report #978773, regarding bmake: ftbfs with autoconf 2.70 to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#995308: libcrypt1: symlink points to libpthread

On Thursday, September 30th, 2021 at 12:08 PM, Aurelien Jarno wrote: > It could be that this libpthread.so.1 file is actually a copy of an old > > libcrypt.so.1. It's something you can check with: > > readelf --dynamic /lib/x86_64-linux-gnu/libpthread.so.1 | grep SONAME And it actually is: ~

Bug#978773: bmake: ftbfs with autoconf 2.70

Hi, On Thu, 30 Sep 2021, at 22:18, Boyuan Yang wrote: > On Thu, 31 Dec 2020 14:26:45 + Matthias Klose wrote: >> Package: src:bmake >> Version: 20200710-5 >> Severity: normal >> Tags: sid bookworm >> User: d...@debian.org >> Usertags: ftbfs-ac270 >> >> [This bug report is not targeted to the

Bug#995418: python-colorlog breaks macsyfinder autopkgtest: module 'colorlog' has no attribute 'logging'

Source: python-colorlog, macsyfinder Control: found -1 python-colorlog/6.4.1-1 Control: found -1 macsyfinder/2.0~rc1-3 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upl

Bug#978773: bmake: ftbfs with autoconf 2.70

Control: tags -1 +patch X-Debbugs-CC: andre...@debian.org Hi, On Thu, 31 Dec 2020 14:26:45 + Matthias Klose wrote: > Package: src:bmake > Version: 20200710-5 > Severity: normal > Tags: sid bookworm > User: d...@debian.org > Usertags: ftbfs-ac270 > > [This bug report is not targeted to the u

Processed: python-colorlog breaks macsyfinder autopkgtest: module 'colorlog' has no attribute 'logging'

Processing control commands: > found -1 python-colorlog/6.4.1-1 Bug #995418 [src:python-colorlog, src:macsyfinder] python-colorlog breaks macsyfinder autopkgtest: module 'colorlog' has no attribute 'logging' Marked as found in versions python-colorlog/6.4.1-1. > found -1 macsyfinder/2.0~rc1-3 Bug

Processed: Re: bmake: ftbfs with autoconf 2.70

Processing control commands: > tags -1 +patch Bug #978773 [src:bmake] bmake: ftbfs with autoconf 2.70 Added tag(s) patch. -- 978773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978773 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#995162: cannot install together with i386

On Thu, Sep 30, 2021 at 09:27:50PM +0200, Giovanni Mascellani wrote: > Thanks for the info. Unless I am mistaken, this means that any package which > installs a shared PNG breaks at every binNMU, unless the binNMU is for all > architectures. Wouldn't it be better if dh_strip_nondeterminism used the

Bug#995412: libstring-copyright-perl breaks licensecheck autopkgtest: lots of different outputs

Quoting Paul Gevers (2021-09-30 21:34:54) > With a recent upload of libstring-copyright-perl the autopkgtest of > licensecheck fails in testing when that autopkgtest is run with the > binary packages of libstring-copyright-perl from unstable. It passes > when run with only packages from testing.

Bug#995308: libcrypt1: symlink points to libpthread

>Can you please try to call /usr/sbin/ldconfig.old to check if the wrong link is recreated? That's needed to confirm if ldconfig is the culprit here. >Can you confirm it's libpthread.so.1 and not libpthread.so.0? If so can you please tell how did you install that file? Here is a shell log, literal

Processed: tiff is now in unstable

Processing commands for cont...@bugs.debian.org: > severity 989951 serious Bug #989951 [pylibtiff] The autopkgtests are failing with the new tiff version Severity set to 'serious' from 'normal' > affects 989951 src:tiff Bug #989951 [pylibtiff] The autopkgtests are failing with the new tiff version

Bug#995162: cannot install together with i386

Hi Mattia, Il 29/09/21 19:28, Mattia Rizzolo ha scritto: This is triggered by the binNMU, which varies the date of the changelog, so that dh_strip_nondeterminism will normalize the metadata of the .png to the binNMU build time instead of the time of the source upload as it was before. Thanks f

Bug#995412: libstring-copyright-perl breaks licensecheck autopkgtest: lots of different outputs

4 - info at end { ok 1 - Can run '/usr/bin/licensecheck -m --shortname-scheme=debian --copyright --lines 0 t/devscripts/info-at-eof.h' ok 2 - Process terminated without a signal ok 3 - Check return from '/usr/bin/licensecheck -m --shortname-scheme=debian --copyright --lines 0

Processed: libstring-copyright-perl breaks licensecheck autopkgtest: lots of different outputs

Processing control commands: > found -1 libstring-copyright-perl/0.003011-1 Bug #995412 [src:libstring-copyright-perl, src:licensecheck] libstring-copyright-perl breaks licensecheck autopkgtest: lots of different outputs Marked as found in versions libstring-copyright-perl/0.003011-1. > found -1

Bug#995411: ruby-omniauth-ultraauth: autopkgtest needs update for new version of ruby-omniauth-openid-connect: Could not find 'omniauth_openid_connect' (~> 0.3.0)

Source: ruby-omniauth-ultraauth Version: 0.0.2-1.1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, ruby-omniauth-openid-conn...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:ruby-omniauth-openid-connect Dear main

Processed: ruby-omniauth-ultraauth: autopkgtest needs update for new version of ruby-omniauth-openid-connect: Could not find 'omniauth_openid_connect' (~> 0.3.0)

Processing control commands: > affects -1 src:ruby-omniauth-openid-connect Bug #995411 [src:ruby-omniauth-ultraauth] ruby-omniauth-ultraauth: autopkgtest needs update for new version of ruby-omniauth-openid-connect: Could not find 'omniauth_openid_connect' (~> 0.3.0) Added indication that 995411

Bug#995410: breezy: FTBFS:

Source: breezy Version: 3.2.1-1 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu impish Hi Jelmer, While tracking a build failure of breezy 3.2.1 in Ubuntu, I found that it is currently also reproducible in Debian unstable: [...] =

Bug#994285: libseccomp: FTBFS on arm64, armhf, mips64el and mipsel

Hi, On 30.09.21 08:40, Johannes Schauer Marin Rodrigues wrote: Hi Felix, On Fri, 17 Sep 2021 07:15:16 +0200 Johannes Schauer Marin Rodrigues wrote: you set the upstream bug to https://github.com/seccomp/libseccomp/issues/336 but I don't think that is correct. The failures is not the same for

Bug#978830: https://gitlab.com/kalilinux/packages/gtkhash

Dear maintainer, I had to update this package for Kali Linux. I updated it to latest upstream version 1.4, and cherry-picked an upstream patch to fix this FTBFS. You can find this package at https://gitlab.com/kalilinux/packages/gtkhash. Please feel free to cherry-pick all the commits you ne

Bug#993562: marked as done (dlt-viewer: missing .h files in dev package)

Your message dated Thu, 30 Sep 2021 19:02:07 + with message-id and subject line Bug#993562: fixed in dlt-viewer 2.21.2+dfsg-2+deb11u1 has caused the Debian Bug report #993562, regarding dlt-viewer: missing .h files in dev package to be marked as done. This means that you claim that the proble

Bug#993935: marked as done (debian-edu-ltsp-install: Netboot image exposes private data and crypto keys)

Your message dated Thu, 30 Sep 2021 18:47:07 + with message-id and subject line Bug#993935: fixed in debian-edu-config 2.11.56+deb11u1 has caused the Debian Bug report #993935, regarding debian-edu-ltsp-install: Netboot image exposes private data and crypto keys to be marked as done. This me

Bug#980692: dask: FTBFS: dh_sphinxdoc: error: debian/python-dask-doc/usr/share/doc/python-dask-doc/html/_static/js/html5shiv.min.js is missing

On Thu, 2021-09-30 at 17:43 +0200, Drew Parsons wrote: > Can anyone say why this Bug#980692 is still holding up the dask > migration? > > The bug is fully marked fixed and closed now, it shouldn't be in the > way > any more. I tried closing the bug again with the currently available version. M

Processed: closing 980692

Processing commands for cont...@bugs.debian.org: > close 980692 2021.08.1+dfsg-3 Bug #980692 {Done: Diane Trout } [src:dask] dask: FTBFS: dh_sphinxdoc: error: debian/python-dask-doc/usr/share/doc/python-dask-doc/html/_static/js/html5shiv.min.js is missing Marked as fixed in versions dask/2021.0

Bug#994971: marked as done (OpenCL not working with latest Nvidia driver)

Your message dated Thu, 30 Sep 2021 17:37:31 + with message-id and subject line Bug#994971: fixed in nvidia-graphics-drivers 470.63.01-1 has caused the Debian Bug report #994971, regarding OpenCL not working with latest Nvidia driver to be marked as done. This means that you claim that the pr

Bug#995038: marked as done (ddccontrol FTBFS: autoreconf: error: intltoolize failed with exit status: 1)

Your message dated Thu, 30 Sep 2021 16:49:16 + with message-id and subject line Bug#995038: fixed in ddccontrol 0.5.2-2 has caused the Debian Bug report #995038, regarding ddccontrol FTBFS: autoreconf: error: intltoolize failed with exit status: 1 to be marked as done. This means that you cl

Bug#995392: ghostscript: ps2pdf trashes some characters

Quoting Vincent Lefevre (2021-09-30 18:28:51) > On 2021-09-30 17:18:46 +0200, Jonas Smedegaard wrote: > > This seems an upstream bug, and it would be helpful if you report it > > upstream as well. Their bugtracker is at https://bugs.ghostscript.com/ > > OK. I'll do it tonight (I could also try t

Bug#995402: FTBFS: test failure

Source: libclass-dbi-sweet-perl Version: 0.11-1.1 Severity: serious Tags: ftbfs sid bookworm upstream Justification: fails to build from source Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=134150 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The package fails it's test suite with t

Bug#995308: marked as done (libcrypt1: symlink points to libpthread)

Your message dated Thu, 30 Sep 2021 18:34:35 +0200 with message-id and subject line Re: libcrypt1: symlink points to libpthread has caused the Debian Bug report #995308, regarding libcrypt1: symlink points to libpthread to be marked as done. This means that you claim that the problem has been dea

Bug#995392: ghostscript: ps2pdf trashes some characters

On 2021-09-30 17:18:46 +0200, Jonas Smedegaard wrote: > This seems an upstream bug, and it would be helpful if you report it > upstream as well. Their bugtracker is at https://bugs.ghostscript.com/ OK. I'll do it tonight (I could also try to find the cause). -- Vincent Lefèvre - Web:

Bug#994860: nvidia-driver: Does not build against new kernel 5.14.0-1-amd64

I hit this on Debian testing. Use the following patch at your own peril, it "works for me". Thanks for not upstreaming your driver nvidia, can't wait for GPU prices to crash so I can replace it with a card from a sane vendor. Raphael Fixes build on 5.14.6 kernels. Index: nvidia-current-470.57.0

Bug#995308: libcrypt1: symlink points to libpthread

On 2021-09-30 15:46, shichimohedron wrote: > >Can you please try to call /usr/sbin/ldconfig.old to check if the wrong > link is recreated? That's needed to confirm if ldconfig is the culprit > here. > >Can you confirm it's libpthread.so.1 and not libpthread.so.0? If so can > you please tell how did

Bug#980692: dask: FTBFS: dh_sphinxdoc: error: debian/python-dask-doc/usr/share/doc/python-dask-doc/html/_static/js/html5shiv.min.js is missing

Can anyone say why this Bug#980692 is still holding up the dask migration? The bug is fully marked fixed and closed now, it shouldn't be in the way any more. Drew

Bug#995392: ghostscript: ps2pdf trashes some characters

Hi Vincent, Quoting Vincent Lefevre (2021-09-30 16:53:01) > The ps2pdf trashes some characters, making text non-searchable and > partly unreadable via pdftotext (even though the glyph appears to be > OK). There was no such issue in the recent past. Thanks for reporting this! This seems an upst

Bug#995392: ghostscript: ps2pdf trashes some characters

Package: ghostscript Version: 9.54.0~dfsg-5 Severity: grave Justification: causes non-serious data loss The ps2pdf trashes some characters, making text non-searchable and partly unreadable via pdftotext (even though the glyph appears to be OK). There was no such issue in the recent past. LaTeX so

Bug#995387: dpkg: remove-on-upgrade deletes symlink targets owned by another package

Package: dpkg Version: 1.20.6 Severity: grave Justification: breaks unrelated packages by removing their conffiles Hi Guillem, attached is a small package demonstrating the misbehavior of remove-on-upgrade which may delete symlink targets. It builds foo.deb (which has 'remove-on-upgrade /etc/old-

Bug#995185: Reported and fixed upstream

Hi, I reported upstream, a fix was found -- 2.21.1 should be out in a few days. Cheers, J.Puydt

Processed: Test does fail

Processing control commands: > tags -1 + confirmed Bug #994785 [src:python-ase] python-ase: autopkgtest regression on arm64/ppc64el: TestSlab.test_vibration_on_surface Added tag(s) confirmed. > forwarded -1 https://gitlab.com/ase/ase/-/issues/976 Bug #994785 [src:python-ase] python-ase: autopkgte

Bug#994785: Test does fail

Control: tags -1 + confirmed Control: forwarded -1 https://gitlab.com/ase/ase/-/issues/976 OK, this test does reproducibly fail at least on arm64 both during build time and autopkgtest. I have forwarded the issue upstream. Andrius

Bug#994971: OpenCL not working with latest Nvidia driver

On 28/09/2021 23.28, Sebastian Ramacher wrote: This smells like #994919 in debhelper, i.e, nvidia-driver needs to be rebuilt with a fixed debhelper version. Thanks. That sounds plausible, and explains my problems to reliably reproduce it elsewhere. Can we quickly find out which packages have

Processed: Re: Bug#995362: zint breaks zbar autopkgtest: unable to open file `/tmp/magick-VxkNk3KeW43pSnBYixIpsF9xU8qRmIzE': No such file or directory @ error/constitute.c/ReadImage/614

Processing control commands: > reassign -1 zbar-tools Bug #995362 [src:zint, src:zbar] zint breaks zbar autopkgtest: unable to open file `/tmp/magick-VxkNk3KeW43pSnBYixIpsF9xU8qRmIzE': No such file or directory @ error/constitute.c/ReadImage/614 Bug reassigned from package 'src:zint, src:zbar' t

Bug#995362: zint breaks zbar autopkgtest: unable to open file `/tmp/magick-VxkNk3KeW43pSnBYixIpsF9xU8qRmIzE': No such file or directory @ error/constitute.c/ReadImage/614

Control: reassign -1 zbar-tools Control: notfound -1 zint/2.10.0-1 Control: owner -1 ! I think I've partially identified what is happening. It turns out that the version of zint in testing, despite being passed the --filetype=SVG flag, actually produces a PNG, which in the past has been happily

Bug#995164: marked as done (golang-github-skip2-go-qrcode-dev: missing Breaks+Replaces: go-qrcode (<< 0.0~git20200617.da1b656))

Your message dated Thu, 30 Sep 2021 12:33:34 + with message-id and subject line Bug#995164: fixed in go-qrcode 0.0~git20200617.da1b656-3 has caused the Debian Bug report #995164, regarding golang-github-skip2-go-qrcode-dev: missing Breaks+Replaces: go-qrcode (<< 0.0~git20200617.da1b656) to be

Bug#995163: marked as done (golang-github-jessevdk-go-flags-dev: missing Breaks+Replaces: golang-go-flags-dev (<< 1.4.0-3~))

Your message dated Thu, 30 Sep 2021 12:33:40 + with message-id and subject line Bug#995163: fixed in golang-go-flags 1.4.0-5 has caused the Debian Bug report #995163, regarding golang-github-jessevdk-go-flags-dev: missing Breaks+Replaces: golang-go-flags-dev (<< 1.4.0-3~) to be marked as done

Bug#995163: marked as pending in golang-go-flags

Control: tag -1 pending Hello, Bug #995163 in golang-go-flags reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/golang-go-flags/-/commit/d5a7d497

Processed: Bug#995163 marked as pending in golang-go-flags

Processing control commands: > tag -1 pending Bug #995163 [golang-github-jessevdk-go-flags-dev] golang-github-jessevdk-go-flags-dev: missing Breaks+Replaces: golang-go-flags-dev (<< 1.4.0-3~) Added tag(s) pending. -- 995163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995163 Debian Bug T

Bug#993016: marked as done (libdap: Includes rpc/types.h which is no longer provided by libc6-dev)

Your message dated Thu, 30 Sep 2021 12:04:05 + with message-id and subject line Bug#993016: fixed in libdap 3.20.8-2 has caused the Debian Bug report #993016, regarding libdap: Includes rpc/types.h which is no longer provided by libc6-dev to be marked as done. This means that you claim that t

Bug#995325: marked as done (libdap: dap-config removal breaks autopkgtest and gdal build)

Your message dated Thu, 30 Sep 2021 12:04:05 + with message-id and subject line Bug#995325: fixed in libdap 3.20.8-2 has caused the Debian Bug report #995325, regarding libdap: dap-config removal breaks autopkgtest and gdal build to be marked as done. This means that you claim that the proble

Bug#995308: libcrypt1: symlink points to libpthread

On 2021-09-29 10:33, Flying Sea Buckthorn wrote: > Package: libcrypt1 > Version: 1:4.4.18-4 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: shichimohed...@protonmail.com > > Dear Maintainer, > > Recently I have upgraded from Buster to Bullseye and, among other things,

Bug#995308: libcrypt1: symlink points to libpthread

On 2021-09-30 02:45, Marco d'Itri wrote: > Maybe then the glibc people know what could make ldconfig create a link > to the wrong library. I don't see how that could happen. ldconfig uses the SONAME entry to create the links. First we have to get confirmed that ldconfig is the culprit. > On Sep

Bug#995308: libcrypt1: symlink points to libpthread

On 2021-09-29 22:07, shichimohedron wrote: > >Is this about libcrypto.so.1 or libcrypt.so.1? > This is about libcrypt.so.1. Sorry for mistyping the filename. > > >Does it still happen after something like this? > > > mv /usr/sbin/ldconfig /usr/sbin/ldconfig.old > > cp -a /bin/true /usr/sbin/ldcon

Bug#995215: marked as done (postgresql-semver: Wait for acceptance of backport)

Your message dated Thu, 30 Sep 2021 03:34:34 -0700 with message-id and subject line Version info added too late to prevent migration has caused the Debian Bug report #995215, regarding postgresql-semver: Wait for acceptance of backport to be marked as done. This means that you claim that the pro

Bug#981671: marked as done (golang-github-linkedin-goavro: autopkgtest failure on 32bit)

Your message dated Thu, 30 Sep 2021 10:34:04 + with message-id and subject line Bug#981671: fixed in golang-github-linkedin-goavro 2.10.1-1 has caused the Debian Bug report #981671, regarding golang-github-linkedin-goavro: autopkgtest failure on 32bit to be marked as done. This means that you

Bug#995365: Cannot import module: ImportError: cannot import name 'ENOENT' from 'sphinx.util.osutil'

Package: python3-sphinxcontrib.plantuml Version: 0.5-6 Severity: grave Tags: fixed-upstream Dear maintainer, With the lastest sphinx update (>4.0), the plantuml contrib module fails to import and render the package unusable: $ python3 -c 'import sphinxcontrib.plantuml' Traceback (most recent cal

Processed: zint breaks zbar autopkgtest: unable to open file `/tmp/magick-VxkNk3KeW43pSnBYixIpsF9xU8qRmIzE': No such file or directory @ error/constitute.c/ReadImage/614

Processing control commands: > found -1 zint/2.10.0-1 Bug #995362 [src:zint, src:zbar] zint breaks zbar autopkgtest: unable to open file `/tmp/magick-VxkNk3KeW43pSnBYixIpsF9xU8qRmIzE': No such file or directory @ error/constitute.c/ReadImage/614 Marked as found in versions zint/2.10.0-1. > found

Bug#995362: zint breaks zbar autopkgtest: unable to open file `/tmp/magick-VxkNk3KeW43pSnBYixIpsF9xU8qRmIzE': No such file or directory @ error/constitute.c/ReadImage/614

Source: zint, zbar Control: found -1 zint/2.10.0-1 Control: found -1 zbar/0.23.92-3 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of zint the autopkgtest of zbar

Bug#995330: marked as done (ggcov: FTBFS)

Your message dated Thu, 30 Sep 2021 09:48:40 + with message-id and subject line Bug#995330: fixed in ggcov 0.10-4 has caused the Debian Bug report #995330, regarding ggcov: FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it i

Bug#995361: rust-trybuild: autopkgtest needs update for new version of rust-dissimilar: failed to select a version for the requirement `dissimilar = "=1.0.1"`

Source: rust-trybuild Version: 1.0.33-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, rust-dissimi...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:rust-dissimilar Dear maintainer(s), With a recent upload of ru

Processed: rust-trybuild: autopkgtest needs update for new version of rust-dissimilar: failed to select a version for the requirement `dissimilar = "=1.0.1"`

Processing control commands: > affects -1 src:rust-dissimilar Bug #995361 [src:rust-trybuild] rust-trybuild: autopkgtest needs update for new version of rust-dissimilar: failed to select a version for the requirement `dissimilar = "=1.0.1"` Added indication that 995361 affects src:rust-dissimila

Bug#995360: pytorch: autopkgtest regression: fft: ATen not compiled with MKL support

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

Processed: ruby-gitlab-labkit: autopkgtest needs update for new version of ruby-jaeger-client: Could not find 'jaeger-client' (~> 0.10)

Processing control commands: > affects -1 src:ruby-jaeger-client Bug #995359 [src:ruby-gitlab-labkit] ruby-gitlab-labkit: autopkgtest needs update for new version of ruby-jaeger-client: Could not find 'jaeger-client' (~> 0.10) Added indication that 995359 affects src:ruby-jaeger-client -- 9953

Bug#995359: ruby-gitlab-labkit: autopkgtest needs update for new version of ruby-jaeger-client: Could not find 'jaeger-client' (~> 0.10)

Source: ruby-gitlab-labkit Version: 0.12.2-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, ruby-jaeger-cli...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:ruby-jaeger-client Dear maintainer(s), With a recent u

Processed: ruby-graphql breaks ruby-batch-loader autopkgtest: uninitialized constant GraphQL::StaticValidation::Validator::Timeout

Processing control commands: > found -1 ruby-graphql/1.11.8-2 Bug #995358 [src:ruby-graphql, src:ruby-batch-loader] ruby-graphql breaks ruby-batch-loader autopkgtest: uninitialized constant GraphQL::StaticValidation::Validator::Timeout Marked as found in versions ruby-graphql/1.11.8-2. > found -

Bug#995358: ruby-graphql breaks ruby-batch-loader autopkgtest: uninitialized constant GraphQL::StaticValidation::Validator::Timeout

Source: ruby-graphql, ruby-batch-loader Control: found -1 ruby-graphql/1.11.8-2 Control: found -1 ruby-batch-loader/2.0.1+dfsg-2 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a

Bug#995356: python-parameterized: autopkgtest regression: AssertionError in tearDownModule

Source: python-parameterized Version: 0.8.1-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 python-parameterized the autopkgtest of python-parameterized fails in testing when that autopk

Bug#995355: node-public-encrypt: autopkgtest regression: deprecation warning on stderr

Source: node-public-encrypt Version: 4.0.0-3 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of node-public-encrypt the autopkgtest of node-public-encrypt fails in testing when that autopkgte

Processed: ruby-async-http: autopkgtest needs update for new version of ruby-protocol-http: Could not find 'protocol-http' (~> 0.20.0)

Processing control commands: > affects -1 src:ruby-protocol-http src:ruby-protocol-http1 Bug #995354 [src:ruby-async-http] ruby-async-http: autopkgtest needs update for new version of ruby-protocol-http: Could not find 'protocol-http' (~> 0.20.0) Added indication that 995354 affects src:ruby-prot

Bug#995354: ruby-async-http: autopkgtest needs update for new version of ruby-protocol-http: Could not find 'protocol-http' (~> 0.20.0)

Source: ruby-async-http Version: 0.52.5-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, ruby-protocol-h...@packages.debian.org, ruby-protocol-h...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:ruby-protocol-http

Bug#995353: ruby-protocol-http: autopkgtest regression on armhf and i386 (both 32 bits)

Source: ruby-protocol-http Version: 0.22.5-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 ruby-protocol-http the autopkgtest of ruby-protocol-http fails in testing when that autopkgtest

Bug#995328: marked as done (eccodes: FTBFS with CMake 3.21.x (Flow control statements are not properly nested))

Your message dated Thu, 30 Sep 2021 08:33:35 + with message-id and subject line Bug#995328: fixed in eccodes 2.23.0-1.1 has caused the Debian Bug report #995328, regarding eccodes: FTBFS with CMake 3.21.x (Flow control statements are not properly nested) to be marked as done. This means that

Bug#995351: src:fonts-ipaexfont: fails to migrate to testing for too long: piuparts regression

Source: fonts-ipaexfont Version: 00401-3 Severity: serious Control: close -1 00401-4 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 day

Processed: src:fonts-ipaexfont: fails to migrate to testing for too long: piuparts regression

Processing control commands: > close -1 00401-4 Bug #995351 [src:fonts-ipaexfont] src:fonts-ipaexfont: fails to migrate to testing for too long: piuparts regression Marked as fixed in versions fonts-ipaexfont/00401-4. Bug #995351 [src:fonts-ipaexfont] src:fonts-ipaexfont: fails to migrate to tes

Bug#995349: ncbi-entrez-direct: FTBFS: no required module provides package github.com/fiam/gounidecode/unidecode

Source: ncbi-entrez-direct Version: 14.6.20210224+dfsg-4 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu impish Hi Aaron, The ncbi-entrez-direct package currently fails to build in Debian unstable: [...] go build -v -gccgoflags '-g -O2 -ffile-prefix-map=/tmp/ncbi-e

Bug#994567: closed by Debian FTP Masters (reply to Antonio Terceiro ) (Bug#994567: fixed in black 21.4b2-2)

Control: clone -1 -2 Control: retitle -2 black: autopkgtest; please don't exit 0 on unsupported archs Control: reopen -2 Control: severity -2 important Hi, On 28-09-2021 23:24, Debian Bug Tracking System wrote: > black (21.4b2-2) unstable; urgency=medium > . >* Team upload. >* debian/te

Processed: Re: Bug#994567 closed by Debian FTP Masters (reply to Antonio Terceiro ) (Bug#994567: fixed in black 21.4b2-2)

Processing control commands: > clone -1 -2 Bug #994567 {Done: Antonio Terceiro } [src:black] black: autopkgtest regression: ModuleNotFoundError: No module named 'aiohttp_cors' Bug 994567 cloned as bug 995344 > retitle -2 black: autopkgtest; please don't exit 0 on unsupported archs Bug #995344 {Do