Bug#1016963: Tests was successfully at BananaPi M3

Hello Vagrant I tested the following versions successfully at the BananaPi M3: - bookworm/testing: 2022.04+dfsg-2+b1 - sid/unstable: 2022.10+dfsg-2 - experimental: 2023.01~rc4+dfsg-1 I also updated the Wiki page. Best regards Bernhard signature.asc Description: This is a digitally

Bug#1028040: pycoast: FTBFS with pillow 9.4.0

Source: pycoast Version: 1.6.1+dfsg-1 Severity: serious Tags: ftbfs Hi Maintainer As can be seen on reproducible builds [1], pycoast fails to build from source since the upload of pillow 9.4.0. I've copied what I hope is the relevant part of the log below. Regards Graham [1]

Bug#1004441: unblocking chromium?

Dear Chromium team, Security team, On 27-01-2022 17:15, Moritz Muehlenhoff wrote: On Wed, Jan 26, 2022 at 09:38:42PM +0100, Paul Gevers wrote: So, I'm proposing the following: we unblock chromium from testing, with the understanding that prior to bookworm's release, we have a discussion with

Bug#1027621: marked as done (mkdocstrings-python-handlers: FTBFS: ImportError: cannot import name 'LegacyVersion' from 'packaging.version' (/usr/lib/python3/dist-packages/packaging/version.py))

Your message dated Fri, 06 Jan 2023 07:19:57 + with message-id and subject line Bug#1027621: fixed in mkdocstrings-python-handlers 0.8.3-1 has caused the Debian Bug report #1027621, regarding mkdocstrings-python-handlers: FTBFS: ImportError: cannot import name 'LegacyVersion' from

Processed: src:raku-json-class: fails to migrate to testing for too long: unresolved RC bug

Processing control commands: > close -1 0.0.19-1 Bug #1028038 [src:raku-json-class] src:raku-json-class: fails to migrate to testing for too long: unresolved RC bug Marked as fixed in versions raku-json-class/0.0.19-1. Bug #1028038 [src:raku-json-class] src:raku-json-class: fails to migrate to

Bug#1028038: src:raku-json-class: fails to migrate to testing for too long: unresolved RC bug

Source: raku-json-class Version: 0.0.18-1 Severity: serious Control: close -1 0.0.19-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1023576 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing

Bug#1027285: marked as done (matplotlib: axes3d.quiver() fails when providing args to Line3DCollection)

Your message dated Fri, 06 Jan 2023 05:20:06 + with message-id and subject line Bug#1027285: fixed in matplotlib 3.6.2-4 has caused the Debian Bug report #1027285, regarding matplotlib: axes3d.quiver() fails when providing args to Line3DCollection to be marked as done. This means that you

Bug#1027049: marked as done (python-matplotlib-data: missing copyright file)

Your message dated Fri, 06 Jan 2023 05:20:06 + with message-id and subject line Bug#1027049: fixed in matplotlib 3.6.2-4 has caused the Debian Bug report #1027049, regarding python-matplotlib-data: missing copyright file to be marked as done. This means that you claim that the problem has

Bug#974616: nomacs uses internal libexiv2 functions to get the user comment

Hi Vincent, Since Debian has updated nomacs to 3.17.2206. Please help to report this issue to upstream if it is still a problem in 3.17.2206, thanks. -- ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org http://czchen.info/ Key fingerprint = BA04 346D C2E1 FE63 C790 8793 CC65 B0CD EC27 5D5B

Processed: Bug#1027285 marked as pending in matplotlib

Processing control commands: > tag -1 pending Bug #1027285 [src:matplotlib] matplotlib: axes3d.quiver() fails when providing args to Line3DCollection Added tag(s) pending. -- 1027285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027285 Debian Bug Tracking System Contact

Bug#1027285: marked as pending in matplotlib

Control: tag -1 pending Hello, Bug #1027285 in matplotlib 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#1027900: parole 4.16.0-2 does not start

Severity grave because parole segfaults on start rendering it entirely unusable (4.16.0-2 on sid/amd64): $ parole Segmentation fault Kind regards, -- Ash Joubert (they/them) Director / Game Developer Transient Software Limited New Zealand

Processed: severity of 1027900 is grave

Processing commands for cont...@bugs.debian.org: > severity 1027900 grave Bug #1027900 [parole] parole 4.16.0-2 does not start Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1027900:

Bug#1026206: g++-13: fails to compile #include due to __float128 vs fixincludes

On Fri, 16 Dec 2022 11:06:37 +0100 Helmut Grohne wrote: > Package: g++-13 > Version: 13-20221214-1 > Severity: serious > > Hi Matthias, > > thanks for pushing gcc-13 into experimental already. That leaves plenty > of time to work on it. I've located a quite fundamental problem with it >

Bug#1028029: xscreensaver: contains non-free fonts

Correction, Gallant is in fact BSD licensed: http://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/sys/dev/wsfont/gallant12x22.h

Processed: nomacs uses internal libexiv2 functions to get the user comment

Processing control commands: > found -1 3.17.2206+dfsg-1 Bug #974616 [nomacs] nomacs uses internal libexiv2 functions to get the user comment Marked as found in versions nomacs/3.17.2206+dfsg-1. -- 974616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974616 Debian Bug Tracking System

Bug#974616: nomacs uses internal libexiv2 functions to get the user comment

Control: found -1 3.17.2206+dfsg-1 Since charset=Ascii still appears before the "User Comment" metadata of the image, this shows that nomacs still uses internal libexiv2 functions, which could silently yield erratic behavior (and possibly security issues) in case such functions change. Perhaps a

Bug#1028029: xscreensaver: contains non-free fonts

False. Luxi Mono is from Red Hat, I'm sure you've heard of them. OCRA is an ANSI Standard, and is public domain. Gallant is a reproduction of the Sun font created by Joshua M. Clulow and released, as far as I am aware, into the public domain.

Bug#1023039: marked as done (python-xmlsec: FTBFS with xmlsec1 1.2.35)

Your message dated Fri, 06 Jan 2023 02:46:33 + with message-id and subject line Bug#1023039: fixed in python-xmlsec 1.3.13-1 has caused the Debian Bug report #1023039, regarding python-xmlsec: FTBFS with xmlsec1 1.2.35 to be marked as done. This means that you claim that the problem has been

Bug#1028029: xscreensaver: contains non-free fonts

Package: xscreensaver Version: 6.02+dfsg1-2 Severity: serious The fonts luximr.ttf, OCRAStd.otf, and possibly gallant12x22.ttf have non-free licenses. Please repack to get rid of them.

Bug#1028027: vice: contains non-free font file

Package: vice Severity: serious Version: 3.6.1+dfsg-4 The package includes C64_Pro_Mono-STYLE.ttf which has a non-free license. So please repack to get rid of it. As your package is in contrib, you can easily extract it to a new non-free package and depend on it.

Bug#1028026: vistrails: contains non-free font file

Package: vistrails Severity: serious Version: 3.0~git+9dc22bd-4 vistrails packages the file "Franklin Gothic No. 2 Roman.ttf" twice. This has a non-free license. Please repack to remove it.

Bug#1023496: marked as done (target-factory: FTBFS with protobuf 3.21)

Your message dated Fri, 06 Jan 2023 00:51:21 + with message-id and subject line Bug#1023496: fixed in target-factory 2.5-8 has caused the Debian Bug report #1023496, regarding target-factory: FTBFS with protobuf 3.21 to be marked as done. This means that you claim that the problem has been

Processed: Bug#1023039 marked as pending in python-xmlsec

Processing control commands: > tag -1 pending Bug #1023039 [python-xmlsec] python-xmlsec: FTBFS with xmlsec1 1.2.35 Added tag(s) pending. -- 1023039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023039 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1023039: marked as pending in python-xmlsec

Control: tag -1 pending Hello, Bug #1023039 in python-xmlsec 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#1028023: librepo FTBFS on MIPS

Source: librepo Version: 1.14.5-1 Severity: serious Tags: ftbfs patch X-Debbugs-Cc: Holger Levsen https://buildd.debian.org/status/logs.php?pkg=librepo=1.14.5-1 ... == ERROR: test_download_packages_with_resume_02

Bug#1023039: python-xmlsec: FTBFS with xmlsec1 1.2.35

Source: python-xmlsec Version: 1.3.12-1 Followup-For: Bug #1023039 The test failure in dynamic signature actually comes from libxmlsec1. It is expected: there's even a patch in libxmlsec1 that skips those tests. I suggest to just do the same in python-xmlsec (skip those two failing tests).

Bug#1016963: Help with testing u-boot!

On 2022-12-28, Rick Thomas wrote: > A Cubox-i running Debian bullseye (11.6). According to versions> It has "u-boot-tools" (version 2021.01+dfsg-5) installed, > but none of the u-boot- packages installed. > > If I reboot it and watch the serial console, I see it showing "U-boot > 2021.01-dfsg-5"

Bug#1024036: marked as done (nipy FTBFS with Python 3.11 as supported version)

Your message dated Thu, 05 Jan 2023 23:35:23 + with message-id and subject line Bug#1024036: fixed in nipy 0.5.0-5 has caused the Debian Bug report #1024036, regarding nipy FTBFS with Python 3.11 as supported version to be marked as done. This means that you claim that the problem has been

Bug#1025119: python-ratelimiter: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine'

Source: python-ratelimiter Version: 1.2.0.post0-3 Followup-For: Bug #1025119 It looks like the upstream package is no longer maintained[1], so it could be challenging to find a good resolution for this bug. There are a couple of unmerged possible fixes provided by contributors[2][3] --

Processed: Bug#1024036 marked as pending in nipy

Processing control commands: > tag -1 pending Bug #1024036 [src:nipy] nipy FTBFS with Python 3.11 as supported version Added tag(s) pending. -- 1024036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1024036: marked as pending in nipy

Control: tag -1 pending Hello, Bug #1024036 in nipy 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#1027171: marked as done (mplcursors: autopkgtest fail with matplotlib/3.6.2)

Your message dated Thu, 05 Jan 2023 22:38:50 + with message-id and subject line Bug#1027171: fixed in mplcursors 0.5.2-1 has caused the Debian Bug report #1027171, regarding mplcursors: autopkgtest fail with matplotlib/3.6.2 to be marked as done. This means that you claim that the problem

Bug#1027839: marked as done (createrepo-c FTBFS with Python 3.11 as default version)

Your message dated Thu, 05 Jan 2023 22:35:06 + with message-id and subject line Bug#1027839: fixed in createrepo-c 0.17.3-2 has caused the Debian Bug report #1027839, regarding createrepo-c FTBFS with Python 3.11 as default version to be marked as done. This means that you claim that the

Bug#1028022: libclamunrar9: Not buildable/installable with clamav 1.0/libclamav11

Package: libclamunrar9 Version: 0.102.3-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) It will take some time to update libclamunrar to provide libclamunrar11. This should not block the clamav transition, so libclamunrar will

Bug#935271: marked as done (lua-apr: FTBFS on all architectures)

Your message dated Thu, 05 Jan 2023 22:24:18 + with message-id and subject line Bug#1027998: Removed package(s) from unstable has caused the Debian Bug report #935271, regarding lua-apr: FTBFS on all architectures to be marked as done. This means that you claim that the problem has been

Bug#1027661: marked as done (python-griffe: FTBFS: ImportError: cannot import name 'LegacyVersion' from 'packaging.version' (/usr/lib/python3/dist-packages/packaging/version.py))

Your message dated Thu, 05 Jan 2023 22:11:03 + with message-id and subject line Bug#1027661: fixed in python-griffe 0.25.3-1 has caused the Debian Bug report #1027661, regarding python-griffe: FTBFS: ImportError: cannot import name 'LegacyVersion' from 'packaging.version'

Bug#1027733: libc6: new libc6 breaks GNU Screen handling of some Unicode characters

Hi Axel, On 2023-01-05 03:25, Axel Beckert wrote: > Hi Aurelien, > > Axel Beckert wrote: > > Aurelien Jarno wrote: > > > An alternative is to not try to support all systems and reinvent the > > > wheel, and instead assume a POSIX system. > > > > I'd say on Debian — independent of the actually

Processed: found 1027934 in 2022.0.0+dfsg-1

Processing commands for cont...@bugs.debian.org: > found 1027934 2022.0.0+dfsg-1 Bug #1027934 [src:hugin] hugin: misses link_directories Marked as found in versions hugin/2022.0.0+dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027934:

Processed: Re: Bug#1027176: u-boot-amlogic: broken non-EFI boot on amlogic boards

Processing control commands: > retitle 1027176 u-boot-amlogic: broken non-EFI boot on amlogic boards Bug #1027176 [u-boot-amlogic] u-boot-amlogic: broken non-EFI boot on odroid-c2 Changed Bug title to 'u-boot-amlogic: broken non-EFI boot on amlogic boards' from 'u-boot-amlogic: broken non-EFI

Bug#1027176: u-boot-amlogic: broken non-EFI boot on amlogic boards

Control: retitle 1027176 u-boot-amlogic: broken non-EFI boot on amlogic boards On 2023-01-05, Frédéric Danis wrote: > On 03/01/2023 18:55, Vagrant Cascadian wrote: >> Sounds like the bug *is* reproducible with unstable and experiemental >> versions, from reading the logs; looks like the same

Bug#1012226: marked as done (unattended-upgrades: flaky autopkgtest: kernel-patterns seems to regularly get confused)

Your message dated Thu, 05 Jan 2023 21:56:45 + with message-id and subject line Bug#1012226: fixed in unattended-upgrades 2.9.1+nmu3 has caused the Debian Bug report #1012226, regarding unattended-upgrades: flaky autopkgtest: kernel-patterns seems to regularly get confused to be marked as

Bug#1028020: gnustep-base FTBFS on architectures with 32bit time_t

Source: gnustep-base Version: 1.28.1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=gnustep-base=1.28.1-1 ... base/NSTimeZone/localtime.m: Failed test: (2023-01-04 07:15:42.752 +) localtime.m:47 ... post-2038 standard time offset vs UTC found for

Bug#1028018: openimageio FTBFS with Python 3.11 as default version

Source: openimageio Version: 2.3.18.0+dfsg-5 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=openimageio=amd64=2.3.18.0%2Bdfsg-5%2Bb2=1672901486=0 ... dh_missing -a -O--buildsystem=cmake -O--builddirectory=build dh_missing: warning:

Bug#1027690: Segmentation fault

I might be affected by the same bug. I get the following error message: $ lmms Notice: could not set realtime priority. VST sync support disabled in your configuration Segmentation fault

Bug#1003473: marked as done (php-horde-lz4: fails to build with php8.1)

Your message dated Thu, 05 Jan 2023 21:27:43 + with message-id and subject line Bug#1003473: fixed in php-horde-lz4 1.0.10-9 has caused the Debian Bug report #1003473, regarding php-horde-lz4: fails to build with php8.1 to be marked as done. This means that you claim that the problem has

Bug#1003784: marked as pending in php-horde-wicked

Control: tag -1 pending Hello, Bug #1003784 in php-horde-wicked 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#1003784 marked as pending in php-horde-wicked

Processing control commands: > tag -1 pending Bug #1003784 [src:php-horde-wicked] php-horde-wicked: (autopkgtest) needs update for php8.1: Text_Wiki_Parse_Paragraph::process(): Argument #1 ($matches) must be passed by reference, value given Added tag(s) pending. -- 1003784:

Bug#1028008: mayavi2 FTBFS with Python 3.11 as default version

Source: mayavi2 Version: 4.8.0-1.1 Severity: serious Forwarded: https://github.com/enthought/mayavi/pull/1199 https://buildd.debian.org/status/fetch.php?pkg=mayavi2=amd64=4.8.0-1.1%2Bb1=1672941910=0 ... tvtk/src/array_ext.c:2313:15: error: too few arguments to function ‘PyCode_New’ 2313 |

Bug#1028004: wine32-development is not installable on sid amd64

Package: wine32-development Version: 7.21~repack-1 Severity: grave Currently attempting to install wine32-development:i386 on sid results in an unresolvable scenario. This renders the package, as well as every 32 bit windows application on the system, completely unusable. # apt-get install

Bug#1016963: Please test u-boot for rock-pi-4-rk3399

On 2023-01-05, Christopher Obbard wrote: > On Thu, 2023-01-05 at 13:21 -0300, Walter Lozano wrote: >> Thank you for your help here! I also did some testing, and everything >> looks OK. The only thing to mention is that the the script >> u-boot-install-rockchip  does not auto detect my board. >>

Bug#1016963: Please test u-boot for Mini-X

On 2023-01-04, Jochen Sprickerhof wrote: > * Vagrant Cascadian [2022-12-28 16:56]: >>> If you have access to any of these boards, please consider testing >>> u-boot versions as packaged in debian for versions from debian stable >>> (2021.01*), testing (2022.04*), unstable (2022.10*) and

Bug#1016963: please test u-boot for roc-pc-rk3399 rock-pi-e-rk3328

On 2023-01-05, Christopher Obbard wrote: > I've tested the following platforms and updated the wiki with my > results: > > > - roc-pc-rk3399, 2023.01-rc4+dfsg-1 from experimental > - SD boot: works > - MAC address: correctly derived from serial number > > - roc-pc-rk3399,

Bug#1027511: marked as done (mkdocstrings: FTBFS: ImportError: cannot import name 'LegacyVersion' from 'packaging.version' (/usr/lib/python3/dist-packages/packaging/version.py))

Your message dated Thu, 05 Jan 2023 19:53:01 + with message-id and subject line Bug#1027511: fixed in mkdocstrings 0.19.1-1 has caused the Debian Bug report #1027511, regarding mkdocstrings: FTBFS: ImportError: cannot import name 'LegacyVersion' from 'packaging.version'

Bug#1023530: closed by Debian FTP Masters (reply to Laurent Bigonville ) (Bug#1023530: fixed in nut 2.8.0-6)

Control: reopen -1 On 31-12-2022 14:12, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the src:nut package: #1023530: nut: flaky autopkgtest: varying failures It has been closed by Debian FTP Masters (reply to Laurent

Bug#1027523: marked as done (autoimport: FTBFS: ImportError: cannot import name 'LegacyVersion' from 'packaging.version' (/usr/lib/python3/dist-packages/packaging/version.py))

Your message dated Thu, 5 Jan 2023 19:08:13 + with message-id <20230105190813.4bkyoo5to7qhj...@4angle.com> and subject line Fixed in pdm-pep517 version 1.0.6+ds1-2 has caused the Debian Bug report #1027523, regarding autoimport: FTBFS: ImportError: cannot import name 'LegacyVersion' from

Processed: Re: Bug#1023530 closed by Debian FTP Masters (reply to Laurent Bigonville ) (Bug#1023530: fixed in nut 2.8.0-6)

Processing control commands: > reopen -1 Bug #1023530 {Done: Laurent Bigonville } [src:nut] nut: flaky autopkgtest: varying failures 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No

Bug#1027909: marked as done (golang-github-libgit2-git2go: FTBFS in bookworm (undeclared build-dependency on tzdata))

Your message dated Thu, 05 Jan 2023 19:22:42 + with message-id and subject line Bug#1027909: fixed in golang-github-libgit2-git2go 34.0.0-3 has caused the Debian Bug report #1027909, regarding golang-github-libgit2-git2go: FTBFS in bookworm (undeclared build-dependency on tzdata) to be

Bug#1026331: closing 1026331

close 1026331 thanks

Processed: closing 1026331

Processing commands for cont...@bugs.debian.org: > close 1026331 Bug #1026331 [src:lintian-brush] lintian-brush: autopkgtest regression: test_matches_package_version Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1026331:

Bug#1027909: marked as pending in golang-github-libgit2-git2go

Control: tag -1 pending Hello, Bug #1027909 in golang-github-libgit2-git2go 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#1027909 marked as pending in golang-github-libgit2-git2go

Processing control commands: > tag -1 pending Bug #1027909 [src:golang-github-libgit2-git2go] golang-github-libgit2-git2go: FTBFS in bookworm (undeclared build-dependency on tzdata) Added tag(s) pending. -- 1027909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027909 Debian Bug Tracking

Processed: found 1026204 in 1.34+dfsg-1

Processing commands for cont...@bugs.debian.org: > found 1026204 1.34+dfsg-1 Bug #1026204 [tar] tar FTBFS on armel, armhf, i386, hppa, powerpc and sparc64 Marked as found in versions tar/1.34+dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026204:

Bug#1026633: marked as done (grig: FTBFS: rig-daemon.c:2286: undefined reference to `rig_get_split')

Your message dated Thu, 05 Jan 2023 18:50:26 + with message-id and subject line Bug#1026633: fixed in grig 0.9.0-1 has caused the Debian Bug report #1026633, regarding grig: FTBFS: rig-daemon.c:2286: undefined reference to `rig_get_split' to be marked as done. This means that you claim that

Processed: severity of 1026204 is serious

Processing commands for cont...@bugs.debian.org: > severity 1026204 serious Bug #1026204 [tar] tar FTBFS on armel, armhf, i386, hppa, powerpc and sparc64 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1026204:

Bug#1013046: marked as done (systemc: ftbfs with GCC-12 (symbol changes))

Your message dated Thu, 05 Jan 2023 18:10:29 + with message-id and subject line Bug#1013046: fixed in systemc 2.3.4-1 has caused the Debian Bug report #1013046, regarding systemc: ftbfs with GCC-12 (symbol changes) to be marked as done. This means that you claim that the problem has been

Processed: tagging 1027934, found 1027759 in 2.22.2, reassign 1027857 to itcl3, tagging 1027565

Processing commands for cont...@bugs.debian.org: > tags 1027934 + sid bookworm Bug #1027934 [src:hugin] hugin: misses link_directories Added tag(s) sid and bookworm. > found 1027759 2.22.2 Bug #1027759 [devscripts] devscripts: Wrong usage of pylint as a module breaks Marked as found in versions

Bug#1027994: cadvisor fails to gather process metrics on bullseye because of cgroup change

On Fri, Jan 6, 2023 at 2:00 AM Sukhbir Singh wrote: > a new release of the cadvisor package is warranted. > The current version in sid is broken for a long time. And it won't make it to bookworm. I no longer use cadvisor. So it really needs a new maintainer. -- Shengjing Zhu

Bug#1027994: cadvisor fails to gather process metrics on bullseye because of cgroup change

Package: cadvisor Version: 0.38.7+ds1-2 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: ssingh+deb...@wikimedia.org Dear Maintainer, The current version of cadvisor on Debian bullseye fails to gather process metrics because of a bug in the upstream version

Processed: found

Processing commands for cont...@bugs.debian.org: > found 1027980 4.8-1 Bug #1027980 [src:sed] sed: Known FTBFS in gnulib-tests Marked as found in versions sed/4.8-1. > End of message, stopping processing here. Please contact me if you need assistance. -- 1027980:

Bug#1023918: marked as done (ziproxy: license conflict with libsasl2)

Your message dated Thu, 05 Jan 2023 17:09:34 + with message-id and subject line Bug#1023918: fixed in ziproxy 3.3.2-6 has caused the Debian Bug report #1023918, regarding ziproxy: license conflict with libsasl2 to be marked as done. This means that you claim that the problem has been dealt

Bug#1016963: Please test u-boot for rock-pi-4-rk3399

On Thu, 2023-01-05 at 13:21 -0300, Walter Lozano wrote: > Hi Christopher and Vagrant > > On 1/5/23 12:10, Christopher Obbard wrote: > > On Wed, 2022-12-28 at 15:53 -0800, Vagrant Cascadian wrote: > > > On 2022-12-28, Vagrant Cascadian wrote: > > > > On 2022-12-22, Vagrant Cascadian wrote: > > > >

Bug#1027952: pcre2 causes crashes in link-grammar

On Thu, Jan 05, 2023 at 03:07:58AM +0200, Adrian Bunk wrote: >... > #0 0x7f46a39011b1 in ?? () from /lib/x86_64-linux-gnu/libpcre2-8.so.0 > #1 0x7f46a38ebb85 in ?? () from /lib/x86_64-linux-gnu/libpcre2-8.so.0 > #2 0x7f46a38fa10f in pcre2_match_8 () >from

Bug#1024576: marked as done (librepo: FTBFS against libgpgme-dev >= 1.18.0-2)

Your message dated Thu, 05 Jan 2023 16:22:06 + with message-id and subject line Bug#1024576: fixed in librepo 1.14.5-1 has caused the Debian Bug report #1024576, regarding librepo: FTBFS against libgpgme-dev >= 1.18.0-2 to be marked as done. This means that you claim that the problem has

Bug#1016963: Please test u-boot for rock-pi-4-rk3399

Hi Christopher and Vagrant On 1/5/23 12:10, Christopher Obbard wrote: On Wed, 2022-12-28 at 15:53 -0800, Vagrant Cascadian wrote: On 2022-12-28, Vagrant Cascadian wrote: On 2022-12-22, Vagrant Cascadian wrote: On 2022-08-20, Vagrant Cascadian wrote: On 2022-08-10, Vagrant Cascadian wrote:

Bug#1027025: psi4: FTBFS with Python 3.11 as default version

Source: psi4 Version: 1:1.3.2+dfsg-3 Followup-For: Bug #1027025 I've opened a merge request[1] to address what I thought was a cmake-related build failure cause on Python 3.11, described in my previous message.. however it looks like the package has built successfully since then - so I might

Bug#1027372: marked as done (golang-github-teambition-rrule-go: FTBFS in bullseye (missing build-depends on tzdata))

Your message dated Thu, 05 Jan 2023 16:04:21 + with message-id and subject line Bug#1027372: fixed in golang-github-teambition-rrule-go 1.8.1-1 has caused the Debian Bug report #1027372, regarding golang-github-teambition-rrule-go: FTBFS in bullseye (missing build-depends on tzdata) to be

Processed: Bug#1027049 marked as pending in matplotlib

Processing control commands: > tag -1 pending Bug #1027049 [python-matplotlib-data] python-matplotlib-data: missing copyright file Added tag(s) pending. -- 1027049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1027049: marked as pending in matplotlib

Control: tag -1 pending Hello, Bug #1027049 in matplotlib 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#1027910: marked as done (golang-github-rickb777-date: FTBFS in bookworm (undeclared build-dependency on tzdata))

Your message dated Thu, 05 Jan 2023 15:34:10 + with message-id and subject line Bug#1027910: fixed in golang-github-rickb777-date 1.20.1-1 has caused the Debian Bug report #1027910, regarding golang-github-rickb777-date: FTBFS in bookworm (undeclared build-dependency on tzdata) to be marked

Bug#1016963: Please test u-boot for rock-pi-4-rk3399

On Wed, 2022-12-28 at 15:53 -0800, Vagrant Cascadian wrote: > On 2022-12-28, Vagrant Cascadian wrote: > > On 2022-12-22, Vagrant Cascadian wrote: > > > On 2022-08-20, Vagrant Cascadian wrote: > > > > On 2022-08-10, Vagrant Cascadian wrote: > > > > > This bug is just to delay migration to testing

Bug#1027952: pcre2 causes crashes in link-grammar

On Thu, Jan 05, 2023 at 09:14:48AM +, Matthew Vernon wrote: > Hi, > > On 05/01/2023 01:07, Adrian Bunk wrote: > > > https://tracker.debian.org/pkg/pcre2 > > Issues preventing migration: > > ∙ ∙ autopkgtest for link-grammar/5.11.0~dfsg-1: amd64: Pass, arm64: > > Regression ♻ (reference ♻),

Bug#1016963: please test u-boot for roc-pc-rk3399 rock-pi-e-rk3328

Hi Vagrant, On Wed, 2022-12-28 at 15:51 -0800, Vagrant Cascadian wrote: > On 2022-12-28, Vagrant Cascadian wrote: > > On 2022-12-22, Vagrant Cascadian wrote: > > > On 2022-08-20, Vagrant Cascadian wrote: > > > > On 2022-08-10, Vagrant Cascadian wrote: > > > > > This bug is just to delay migration

Processed: Re: [Pkg-nagios-devel] Bug#1027982: icinga-php-library: Includes non-source Font Awesome 5

Processing commands for cont...@bugs.debian.org: > tags 1027982 upstream wontfix Bug #1027982 [icinga-php-library] icinga-php-library: Includes non-source Font Awesome 5 Added tag(s) upstream and wontfix. > severity 1027982 normal Bug #1027982 [icinga-php-library] icinga-php-library: Includes

Bug#1027982: icinga-php-library: Includes non-source Font Awesome 5

Package: icinga-php-library Version: 0.10.1-1 Severity: serious This package contains font files from Font Awesome 5 which are licensed freely but are not built from source and cannot be built from source (missing build system). #902981 has the details. Please repack the package to get rid of

Bug#1027980: sed: Known FTBFS in gnulib-tests

Source: sed Version: 4.8-1.1 Severity: serious Tags: fixed-upstream The latest upload has uncovered a bug with sed in combination with the latest glibc which is documented at https://bugs.launchpad.net/ubuntu/+source/sed/+bug/1954348 Two of the gnulib tests fail in armel, armhf, and mipsel.

Bug#1027112: bazel-bootstrap: /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()'

Hello, >Ah, I see. So you added the missing absl_synchronization linker flag to >the bazel-bootstrap build process. I'm really curious to see if this >works because from my (admittedly inexperienced) troubleshooting the >problems seemed to be in the grpc package[1]. yes, indeed, fixing

Processed: reassign and close

Processing commands for cont...@bugs.debian.org: > reassign 1026570 dask.distributed 2022.02.0+ds.1-2 Bug #1026570 [src:python-streamz] python-streamz: FTBFS: ValueError: I/O operation on closed file. Bug reassigned from package 'src:python-streamz' to 'dask.distributed'. No longer marked as

Processed: Bug#1026590 marked as pending in dask.distributed

Processing control commands: > tag -1 pending Bug #1026590 [src:dask.distributed] dask.distributed: FTBFS: RuntimeError: IOLoop is closed Added tag(s) pending. -- 1026590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026590 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1026590: marked as pending in dask.distributed

Control: tag -1 pending Hello, Bug #1026590 in dask.distributed 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#1027379: marked as done (nfdump: FTBFS in bullseye (missing build-depends on tzdata))

Your message dated Thu, 05 Jan 2023 11:52:01 + with message-id and subject line Bug#1027379: fixed in nfdump 1.7.1-2 has caused the Debian Bug report #1027379, regarding nfdump: FTBFS in bullseye (missing build-depends on tzdata) to be marked as done. This means that you claim that the

Bug#1027966: marked as done (building of cross-toolchain-base broken, wrong assumption of dpkg-buildinfo)

Your message dated Thu, 05 Jan 2023 11:49:38 + with message-id and subject line Bug#1027966: fixed in dpkg 1.21.17 has caused the Debian Bug report #1027966, regarding building of cross-toolchain-base broken, wrong assumption of dpkg-buildinfo to be marked as done. This means that you claim

Processed: Add libvtk6-qt-dev to dependencies

Processing control commands: > tags -1 patch Bug #1027965 [libvtk9-dev] VTK-vtk-module-find-packages.cmake should not require Qt5 Added tag(s) patch. -- 1027965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027965 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1027965: Add libvtk6-qt-dev to dependencies

Control: tags -1 patch Since 2016 it seems that a hack has been put in place in vtk package consumer to always include vtk-qt package: https://salsa.debian.org/med-team/vtk-dicom/-/commit/0d3fde678cd86459a485df7492307b94a5afc97e I suspect it would be better done in vtk9 package itself. Typical

Bug#1027971: virtualbox : Depends: python3 (< 3.11) but 3.11.1-1 is installed

Package: virtualbox Version: 7.0.4-dfsg-5 Severity: grave Justification: renders package unusable Dear Maintainer, trying to install virtualbox on sid, but its dependencies are wrong. python3 (<< 3.11), python3 (>= 3.10~), python3.10 Please upgrade to 3.11.1-1. TIA, Michael -- System

Processed: Bug#1027966 in package dpkg marked as pending

Processing control commands: > tag 1027966 pending Bug #1027966 [dpkg-dev] building of cross-toolchain-base broken, wrong assumption of dpkg-buildinfo Added tag(s) pending. -- 1027966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027966 Debian Bug Tracking System Contact

Bug#1027966: in package dpkg marked as pending

Control: tag 1027966 pending Hi! Bug #1027966 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=4c03965ef --- dpkg-genbuildinfo: Do

Processed: your mail

Processing commands for cont...@bugs.debian.org: > affects 1027965 src:gdcm Bug #1027965 [libvtk9-dev] VTK-vtk-module-find-packages.cmake should not require Qt5 Added indication that 1027965 affects src:gdcm > affects 1027965 src:vtk-dicom Bug #1027965 [libvtk9-dev]

Bug#1027759: pylint: Missing dependency on python3-tomli for python3 < 3.11

Control: reopen -1 Control: reassign -1 devscripts Control: retitle -1 devscripts: Wrong usage of pylint as a module breaks Hi! On Thu, 2023-01-05 at 00:18:13 -0500, Sandro Tosi wrote: > > Package: pylint > > Version: 2.15.9-1 > > Severity: serious > > It looks like the recent release is

Processed: Re: Bug#1027759: pylint: Missing dependency on python3-tomli for python3 < 3.11

Processing control commands: > reopen -1 Bug #1027759 {Done: Sandro Tosi } [pylint] pylint: Missing dependency on python3-tomli for python3 < 3.11 Bug reopened Ignoring request to alter fixed versions of bug #1027759 to the same values previously set > reassign -1 devscripts Bug #1027759

  1   2   >