Processed: Re: Bug#998361: pam FTBFS

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

Bug#998361: pam FTBFS

Control: tags -1 + patch On Tue, Nov 02, 2021 at 10:11:40PM +0100, Johannes Schauer Marin Rodrigues wrote: > our CI runs for the DPKG_ROOT tests failed today because pam FTBFS. I > rebuilt pam locally in a fresh sbuild chroot without any modifications > and arrived at the same build failure. I

Bug#997031: marked as done (nvidia-cuda-gdb: cuda-gdb 'Segmentation fault' at startup if libpython2.7 is installed)

Your message dated Wed, 03 Nov 2021 05:08:37 + with message-id and subject line Bug#997031: fixed in nvidia-cuda-toolkit 11.3.1-5 has caused the Debian Bug report #997031, regarding nvidia-cuda-gdb: cuda-gdb 'Segmentation fault' at startup if libpython2.7 is installed to be marked as done.

Bug#997875: marked as done (astroid breaks pylint-flask autopkgtest: No module named 'typing_extensions')

Your message dated Wed, 03 Nov 2021 04:03:43 + with message-id and subject line Bug#997875: fixed in astroid 2.8.4-1 has caused the Debian Bug report #997875, regarding astroid breaks pylint-flask autopkgtest: No module named 'typing_extensions' to be marked as done. This means that you

Bug#997355: marked as done (pylint: FTBFS: ModuleNotFoundError: No module named 'typing_extensions')

Your message dated Wed, 03 Nov 2021 04:03:43 + with message-id and subject line Bug#997875: fixed in astroid 2.8.4-1 has caused the Debian Bug report #997875, regarding pylint: FTBFS: ModuleNotFoundError: No module named 'typing_extensions' to be marked as done. This means that you claim

Processed: reassign 997355 to src:astroid, forcibly merging 997875 997355

Processing commands for cont...@bugs.debian.org: > reassign 997355 src:astroid Bug #997355 [astroid] pylint: FTBFS: ModuleNotFoundError: No module named 'typing_extensions' Bug reassigned from package 'astroid' to 'src:astroid'. Ignoring request to alter found versions of bug #997355 to the same

Bug#997875: marked as pending in astroid

Control: tag -1 pending Hello, Bug #997875 in astroid 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 (with 1 error): reassign 997355 to astroid, forcibly merging 997875 997355

Processing commands for cont...@bugs.debian.org: > reassign 997355 astroid Bug #997355 [src:pylint] pylint: FTBFS: ModuleNotFoundError: No module named 'typing_extensions' Bug reassigned from package 'src:pylint' to 'astroid'. No longer marked as found in versions pylint/2.7.2-3. Ignoring

Processed: Bug#997875 marked as pending in astroid

Processing control commands: > tag -1 pending Bug #997875 [src:astroid] astroid breaks pylint-flask autopkgtest: No module named 'typing_extensions' Added tag(s) pending. -- 997875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997875 Debian Bug Tracking System Contact

Bug#997232: marked as done (netperfmeter: FTBFS: cpustatus.cc:33:10: fatal error: sys/sysctl.h: No such file or directory)

Your message dated Wed, 03 Nov 2021 03:33:27 + with message-id and subject line Bug#997232: fixed in netperfmeter 1.9.1-1 has caused the Debian Bug report #997232, regarding netperfmeter: FTBFS: cpustatus.cc:33:10: fatal error: sys/sysctl.h: No such file or directory to be marked as done.

Bug#997740: marked as done (python-pkginfo: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 176))

Your message dated Wed, 03 Nov 2021 01:18:27 + with message-id and subject line Bug#997740: fixed in python-pkginfo 1.7.1-1 has caused the Debian Bug report #997740, regarding python-pkginfo: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 176) to be

Bug#998358: Subject: grepmail: autopkgtest doesn't do anything

Thanks a lot Paul. Really, in our machines the package is built and Makefile exists. I need to check some packages of mine. I think there are some tests around grepmail in upstream source. However, don't worry because this upload was a first work. Now, Marcos will package the new upstream

Bug#998347: librust-bindgen+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7+default-dev

Source: rust-bindgen Followup-For: Bug #998347 That is not how rust Debian packaging works; your patch will get lost with the next upload of the autogenerated package. If you want your patch to not get lost, do it via the normal process: https://salsa.debian.org/rust-team/debcargo-conf/ --

Bug#998156: contains non-DFSG-free files

Henry is correct that the MLton compiler (the runtime, basis library implementation, and compiler proper) do not depend on ckit (or any of the (re)distributed SML/NJ libraries), the benchmarks, or on mlnlffigen, nor are those components required for using MLton (unless, of course, the program

Bug#984081: marked as done (lastz: ftbfs with GCC-11)

Your message dated Tue, 02 Nov 2021 22:48:56 + with message-id and subject line Bug#984081: fixed in lastz 1.04.15-2 has caused the Debian Bug report #984081, regarding lastz: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#997713: marked as done (pushpin: FTBFS: error: failed to select a version for the requirement `base64 = "^0.12"`)

Your message dated Tue, 02 Nov 2021 22:49:19 + with message-id and subject line Bug#997713: fixed in pushpin 1.32.2-2 has caused the Debian Bug report #997713, regarding pushpin: FTBFS: error: failed to select a version for the requirement `base64 = "^0.12"` to be marked as done. This means

Bug#997772: python-cogent: FTBFS: You must configure the bibtex_bibfiles setting

Hi Andreas > > > Extension error: > > > You must configure the bibtex_bibfiles setting > > > make[2]: *** [Makefile:40: html] Error 2 this is sphinxcontrib-bibtex saying that you need to add the following to doc/conf.py: bibtex_bibfiles = "path/to/references.bib" However I can't see a .bib

Bug#998364: ruby-async-rspec: autopkgtest failures on armhf and i386

Source: ruby-async-rspec Version: 1.16.1-2 Severity: serious ruby-async-rspec is unable to migrate to testing due to autopkgtest failures on armhf and i386: Failures: | 1) RSpec::Memory on supported platform should not exceed specified size limit |Failure/Error: | expect do | "a"

Processed: Bug#984081 marked as pending in lastz

Processing control commands: > tag -1 pending Bug #984081 [src:lastz] lastz: ftbfs with GCC-11 Added tag(s) pending. -- 984081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#984081: marked as pending in lastz

Control: tag -1 pending Hello, Bug #984081 in lastz 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#997166: libcdio: FTBFS: cdda-player.c:301:28: error: format not a string literal and no format arguments [-Werror=format-security]

That link is the correct one. I was comparing to https://sources.debian.org/patches/libcdio/2.1.0-2/ncursesw.diff/ which is different so I may have this wrong. On Tue, Nov 2, 2021 at 5:47 PM Gabriel F. T. Gomes < gabr...@inconstante.net.br> wrote: > Hi, Rocky, > > On Tue, 2 Nov 2021 13:11:07

Bug#990224: [Pkg-pascal-devel] Bug#990224: leaves diversion after upgrade from sid to experimental

Hi Abou, On 02-11-2021 22:37, Abou Al Montacir wrote: > On Tue, 2021-11-02 at 21:22 +0100, Paul Gevers wrote: >> I don't follow at all. > Sorry, I don't catch what do you mean here, probably due to my non > native English. It means that I didn't understand everything you were saying as the

Bug#997166: libcdio: FTBFS: cdda-player.c:301:28: error: format not a string literal and no format arguments [-Werror=format-security]

Hi, Rocky, On Tue, 2 Nov 2021 13:11:07 -0400 Rocky Bernstein wrote: > > Hmm - as best as I can tell this patches things a little differently than > what was done in the git codebase. That was not my intention. Actually, I don't understand why you say that. The patch that I backported to

Processed: closing 997809

Processing commands for cont...@bugs.debian.org: > close 997809 Bug #997809 [src:roundcube] roundcube: Delay migration into testing Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 997809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997809

Bug#990224: leaves diversion after upgrade from sid to experimental

Hi Paul, On Tue, 2021-11-02 at 21:22 +0100, Paul Gevers wrote: > ... > I don't follow at all. Sorry, I don't catch what do you mean here, probably due to my non native English. Did you not accept the new solution, or is my explanation above not clear at all and confusing?  If you don't like the

Bug#796536: marked as done (criu: package not yet ready for stable release / fast moving (blocking bug))

Your message dated Tue, 2 Nov 2021 22:29:42 +0100 with message-id and subject line Re: Bug#796536: criu: package not yet ready for stable release / fast moving (blocking bug) has caused the Debian Bug report #796536, regarding criu: package not yet ready for stable release / fast moving

Processed: lastz ftbfs with gcc11 fixed upstream

Processing commands for cont...@bugs.debian.org: > # considering pushing a patch for this one, so it stops making noise > tags 984081 confirmed fixed-upstream Bug #984081 [src:lastz] lastz: ftbfs with GCC-11 Added tag(s) confirmed and fixed-upstream. > forwarded 984081

Bug#998359: age fails reading passphrase-protected key files

Package: age Version: 1.0.0~rc1-2+b3 Severity: grave Justification: renders package unusable Dear Maintainer, this is how you can reproduce the bug: $ age-keygen | age -p > tmp/key.age Public key: age17sxjygr9yuvv7s5yd657gfw6v2c9597938ur2smug4u9fysrxdms2p9h0y Enter passphrase (leave empty to

Bug#996878: python3-prelude: python3 import prelude throws an ImportError exception

Hi, I tracked the issue down to https://sources.debian.org/patches/libprelude/5.2.0-4/025-Fix-PyIOBase_Type.patch Although the patch changes the content of bindings/python/libpreludecpp-python.i, swig is never called during the build to recreate _prelude.cxx. The final package therefore

Bug#998358: Subject: grepmail: autopkgtest doesn't do anything

Source: grepmail X-Debbugs-Cc: mar...@talau.info, eribe...@debian.org Version: 5.3104-1 Severity: serious Justification: RC policy Dear Marcos, Joao, I appreciate your attention to the orphaned package grepmail and the fact that you try to save it from removal from testing, but in the process

Bug#990224: lazarus-src-2.0: leaves diversion after upgrade from sid to experimental

Hi Abou, On 30-10-2021 12:25, Abou Al Montacir wrote: > The issue here is that LPK files are needed by binary libs (pascal units > / ppu) and source packages. > The right solution would be probably to move them into a separate > packages that is used by both source and binaries. > However, that

Bug#997066: marked as done (ceph: FTBFS: ld: ../../lib/libkv.a(LevelDBStore.cc.o):(.data.rel.ro._ZTI17CephLevelDBLogger[_ZTI17CephLevelDBLogger]+0x10): undefined reference to `typeinfo for leveldb::Lo

Your message dated Tue, 2 Nov 2021 21:16:25 +0100 with message-id and subject line Bug was in leveldb has caused the Debian Bug report #997066, regarding ceph: FTBFS: ld: ../../lib/libkv.a(LevelDBStore.cc.o):(.data.rel.ro._ZTI17CephLevelDBLogger[_ZTI17CephLevelDBLogger]+0x10): undefined

Processed: src:win32-loader: fails to migrate to testing for too long

Processing control commands: > close -1 0.10.5 Bug #998353 [src:win32-loader] src:win32-loader: fails to migrate to testing for too long Marked as fixed in versions win32-loader/0.10.5. Bug #998353 [src:win32-loader] src:win32-loader: fails to migrate to testing for too long Marked Bug as done

Bug#998353: src:win32-loader: fails to migrate to testing for too long

Source: win32-loader Version: 0.10.4 Severity: serious Control: close -1 0.10.5 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The following template feels a bit weird for the somewhat special package that win32-loader is, but I leave it

Bug#998351: Should libdbd-sqlite2-perl be shipped in bookworm?

Package: libdbd-sqlite2-perl Severity: serious Tags: bookworm sid libdbd-sqlite2-perl uses a vendored copy of SQLite 2. SQLite 3 was released in 2004, and the the regular SQLite 2 package is no longer shipped since bullseye (see #607969).

Bug#997740: [Python-modules-team] Bug#997740: python-pkginfo: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 176)

HI, This bugs is fixed in the new upstream release [0] [0] https://bugs.launchpad.net/pkginfo/+bug/1933322 Cheers, Arias Emmanuel @eamanu yaerobi.com On Sun, Oct 24, 2021 at 9:34 AM Lucas Nussbaum wrote: > Source: python-pkginfo > Version: 1.4.2-3 > Severity: serious > Justification: FTBFS

Processed: rust-bindgen: diff for NMU version 0.59.1-1.1

Processing control commands: > tags 998347 + patch Bug #998347 {Done: Ximin Luo } [librust-bindgen+env-logger-dev] librust-bindgen+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7+default-dev Added tag(s) patch. > tags 998347 + pending Bug #998347 {Done:

Bug#998347: rust-bindgen: diff for NMU version 0.59.1-1.1

Control: tags 998347 + patch Control: tags 998347 + pending Dear maintainer, I've prepared an NMU for rust-bindgen (versioned as 0.59.1-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, - Jonas diff -Nru

Processed: rust-quickcheck: diff for NMU version 0.9.2-1.1

Processing control commands: > tags 998345 + patch Bug #998345 {Done: Ximin Luo } [librust-quickcheck+env-logger-dev] librust-quickcheck+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7-dev Added tag(s) patch. > tags 998345 + pending Bug #998345 {Done:

Bug#998345: rust-quickcheck: diff for NMU version 0.9.2-1.1

Control: tags 998345 + patch Control: tags 998345 + pending Dear maintainer, I've prepared an NMU for rust-quickcheck (versioned as 0.9.2-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, - Jonas diff -Nru

Bug#998345: librust-quickcheck+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7-dev

Source: rust-quickcheck Followup-For: Bug #998345 Control: close -1 > Correction: It is the binary package librust-quickcheck+env-logger-dev > which depends on librust-env-logger-0.7-dev. env-logger-0.7 is sitting in NEW. There is no action to take on this package, therefore closing. --

Bug#998347: closing 998347

notfound 998347 0.59.1-1 close 998347 thanks env-logger-0.7 is sitting in NEW. There is no action to take on this package, therefore closing.

Bug#998345: closing 998345

close 998345 thanks See my previous message.

Processed: Re: librust-quickcheck+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7-dev

Processing control commands: > close -1 Bug #998345 {Done: Ximin Luo } [librust-quickcheck+env-logger-dev] librust-quickcheck+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7-dev Bug 998345 is already marked as done; not doing anything. -- 998345:

Processed: closing 998347

Processing commands for cont...@bugs.debian.org: > notfound 998347 0.59.1-1 Bug #998347 [librust-bindgen+env-logger-dev] librust-bindgen+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7+default-dev No longer marked as found in versions

Bug#998345: rust-quickcheck: invalid bug report

Source: rust-quickcheck Followup-For: Bug #998345 Control: notfound -1 0.9.2-1 Control: close -1 Not sure how you came to this conclusion. Package: librust-rand+std-dev Provides: librust-rand-0.7+default-dev (= ${binary:Version}), $ sudo aptitude install librust-quickcheck-dev [sudo] password

Processed: notfound 998345 in 0.9.2-1

Processing commands for cont...@bugs.debian.org: > notfound 998345 0.9.2-1 Bug #998345 [librust-quickcheck+env-logger-dev] librust-quickcheck+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7-dev Ignoring request to alter found versions of bug #998345 to the

Processed: closing 998345

Processing commands for cont...@bugs.debian.org: > close 998345 Bug #998345 [librust-quickcheck+env-logger-dev] librust-quickcheck+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7-dev Marked Bug as done > thanks Stopping processing here. Please contact me

Bug#998345: librust-quickcheck-dev: uninstallable - depends on non-existing package librust-rand-0.7+default-dev

Control: reassign -1 librust-quickcheck+env-logger-dev Control: retitle -1 librust-quickcheck+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7-dev Quoting Jonas Smedegaard (2021-11-02 21:19:38) > The package librust-quickcheck-dev is uninstallable: It

Processed: Re: librust-quickcheck-dev: uninstallable - depends on non-existing package librust-rand-0.7+default-dev

Processing control commands: > reassign -1 librust-quickcheck+env-logger-dev Bug #998345 [librust-quickcheck-dev] librust-quickcheck-dev: uninstallable - depends on non-existing package librust-rand-0.7+default-dev Bug reassigned from package 'librust-quickcheck-dev' to

Bug#998347: librust-bindgen+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7+default-dev

Package: librust-bindgen+env-logger-dev Version: 0.59.1-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The package librust-bindgen+env-logger-dev is uninstallable: It depends on non-existing package librust-env-logger-0.7+default-dev.

Bug#997232: netperfmeter: FTBFS: cpustatus.cc:33:10: fatal error: sys/sysctl.h: No such file or directory

On Sat, 23 Oct 2021 21:18:54 +0200 Lucas Nussbaum wrote: Source: netperfmeter Version: 1.8.6~rc2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd

Bug#997977: marked as done (/lib/systemd/system/monopd.service:8: Special user nobody configured, this is not safe!)

Your message dated Tue, 02 Nov 2021 18:20:45 + with message-id and subject line Bug#997977: fixed in monopd 0.10.2-5 has caused the Debian Bug report #997977, regarding /lib/systemd/system/monopd.service:8: Special user nobody configured, this is not safe! to be marked as done. This means

Processed: Re: pygithub: FTBFS: error in PyGithub setup command: use_2to3 is invalid.

Processing control commands: > tag -1 patch Bug #997630 [src:pygithub] pygithub: FTBFS: error in PyGithub setup command: use_2to3 is invalid. Added tag(s) patch. -- 997630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997630 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#997630: pygithub: FTBFS: error in PyGithub setup command: use_2to3 is invalid.

Control: tag -1 patch From: Romain Porte Date: Tue, 2 Nov 2021 15:19:51 +0100 Subject: setup.py: remove 2to3 Should be dropped when package is updated, because latest upstream releases are not using this flag anymore. Forward: not-needed --- setup.py | 1 - 1 file changed, 1 deletion(-) diff

Bug#998295: marked as done (puma: 401 runs, 1086 assertions, 1 failures, 0 errors, 6 skips)

Your message dated Tue, 02 Nov 2021 18:06:11 + with message-id and subject line Bug#998295: fixed in puma 5.5.2-1 has caused the Debian Bug report #998295, regarding puma: 401 runs, 1086 assertions, 1 failures, 0 errors, 6 skips to be marked as done. This means that you claim that the

Bug#997977: marked as pending in monopd

Control: tag -1 pending Hello, Bug #997977 in monopd 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: closing 998330

Processing commands for cont...@bugs.debian.org: > close 998330 2.4.0-2 Bug #998330 [src:cvise] cvise FTBFS: test failure Marked as fixed in versions cvise/2.4.0-2. Bug #998330 [src:cvise] cvise FTBFS: test failure Marked Bug as done > thanks Stopping processing here. Please contact me if you

Processed: Bug#997977 marked as pending in monopd

Processing control commands: > tag -1 pending Bug #997977 [monopd] /lib/systemd/system/monopd.service:8: Special user nobody configured, this is not safe! Added tag(s) pending. -- 997977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997977 Debian Bug Tracking System Contact

Bug#998345: librust-quickcheck-dev: uninstallable - depends on non-existing package librust-rand-0.7+default-dev

Package: librust-quickcheck-dev Version: 0.9.2-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The package librust-quickcheck-dev is uninstallable: It depends on non-existing package librust-rand-0.7+default-dev. - Jonas -BEGIN PGP

Bug#997701: marked as done (golang-github-mattn-go-runewidth: FTBFS: open /usr/share/unicode/emoji/emoji-data.txt: no such file or directory)

Your message dated Tue, 02 Nov 2021 17:19:21 + with message-id and subject line Bug#997701: fixed in golang-github-mattn-go-runewidth 0.0.13-2 has caused the Debian Bug report #997701, regarding golang-github-mattn-go-runewidth: FTBFS: open /usr/share/unicode/emoji/emoji-data.txt: no such

Bug#997166: libcdio: FTBFS: cdda-player.c:301:28: error: format not a string literal and no format arguments [-Werror=format-security]

Hmm - as best as I can tell this patches things a little differently than what was done in the git codebase. It looks like this changes to use library ncursesw whereas change in git changes the source code and adjusts the source code so that the previous curses library is okay to use. I don't

Bug#997166: marked as done (libcdio: FTBFS: cdda-player.c:301:28: error: format not a string literal and no format arguments [-Werror=format-security])

Your message dated Tue, 02 Nov 2021 17:07:06 + with message-id and subject line Bug#997166: fixed in libcdio 2.1.0-3 has caused the Debian Bug report #997166, regarding libcdio: FTBFS: cdda-player.c:301:28: error: format not a string literal and no format arguments [-Werror=format-security]

Bug#997089: libreoffice: FTBFS: segfault in '/<>/instdir/sdk/examples/java/Inspector'

Hi, Am Thu, Oct 28, 2021 at 07:18:19PM +0200 schrieb Rene Engelhard: > And interestingly, (after rm'ing the stale unopkg lockfile..) it passed. > > Also after a new attempt with manual > > $ make clean && make subsequencheck > > in odk worked, too. > > > Just looks like a flaky test... (Even

Bug#997166: libcdio: FTBFS: cdda-player.c:301:28: error: format not a string literal and no format arguments [-Werror=format-security]

Hi, Rocky, Lucas, Thanks for doing all the hard work of reporting and fixing the bug. I have just uploaded a new version o libcdio with the fix. Cheers, Gabriel

Bug#998109: python3-numpy: numpy.typing is missing

control: severity -1 important > This bug is blocking other python packages which require numpy 1.20, > (and use numpy.typing) so raising severity to serious. sorry but that's not how RC severity works, that's for policy violations, which in this case there are none. I understand you may want

Processed: Re: Bug#998109: python3-numpy: numpy.typing is missing

Processing control commands: > severity -1 important Bug #998109 [python3-numpy] python3-numpy: numpy.typing is missing Severity set to 'important' from 'serious' -- 998109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998109 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#998052: marked as done (ltt-control build depends liblttng-ust-dev (< 2.13.0~) but 2.13.0-2 is to be installed)

Your message dated Tue, 02 Nov 2021 16:33:51 + with message-id and subject line Bug#998052: fixed in ltt-control 2.13.1-1 has caused the Debian Bug report #998052, regarding ltt-control build depends liblttng-ust-dev (< 2.13.0~) but 2.13.0-2 is to be installed to be marked as done. This

Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14

Re: Sébastien Villemot > I am going to package cl-uax-15 and cl-global-vars (ITPs are marked as > blocking the present bug), and then upgrade cl-postmodern. That sounds excellent, merci! Christoph

Bug#997159: burp: FTBFS: src/client/monitor/status_client_ncurses.c:350:9: error: format not a string literal and no format arguments [-Werror=format-security]

I've temporarily disabled the format-security error: https://salsa.debian.org/debian/burp/-/commit/625692bd42884fbb97f132967e3c4e70430aaddf I will contact the developer to raise the issue. Thanks! On 23/10/21 21:05, Lucas Nussbaum wrote: Source: burp Version: 2.2.18-8 Severity: serious

Bug#980627: ruby-databojects-mysql

Am Dienstag, dem 02.11.2021 um 13:36 +0100 schrieb Daniel Leidert: > Am Mittwoch, dem 27.10.2021 um 11:02 -0300 schrieb Lucas Kanashiro: > > [..] > > * ruby-databojects-mysql > [..] Digging some more: This project has been archived upstream and the homepage points to https://rom-rb.org/ now,

Processed: tagging 979101

Processing commands for cont...@bugs.debian.org: > tags 979101 + fixed-upstream Bug #979101 [devtodo] Legally problematic GPL-3+ readline dependency Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 979101:

Bug#998330: cvise FTBFS: test failure

Source: cvise Version: 2.4.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=cvise=2.4.0-1 ... === FAILURES === ___ TestCvise.test_simple_reduction self =

Bug#997209: marked as done (eegdev: FTBFS: ./doc/examples/library-usage/eegdev_acq.c:214: undefined reference to `rpl_free')

Your message dated Tue, 02 Nov 2021 14:34:59 + with message-id and subject line Bug#997209: fixed in eegdev 0.2-6 has caused the Debian Bug report #997209, regarding eegdev: FTBFS: ./doc/examples/library-usage/eegdev_acq.c:214: undefined reference to `rpl_free' to be marked as done. This

Processed: Bug#996311 marked as pending in ruby-lapack

Processing control commands: > tag -1 pending Bug #996311 [src:ruby-lapack] ruby-lapack: FTBFS: ERROR: Test "ruby2.7" failed. Added tag(s) pending. -- 996311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#996311: marked as pending in ruby-lapack

Control: tag -1 pending Hello, Bug #996311 in ruby-lapack 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#997630 marked as pending in pygithub

Processing control commands: > tag -1 pending Bug #997630 [src:pygithub] pygithub: FTBFS: error in PyGithub setup command: use_2to3 is invalid. Added tag(s) pending. -- 997630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997630 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#997630: marked as pending in pygithub

Control: tag -1 pending Hello, Bug #997630 in pygithub 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#997209: marked as pending in eegdev

Control: tag -1 pending Hello, Bug #997209 in eegdev 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#997209 marked as pending in eegdev

Processing control commands: > tag -1 pending Bug #997209 [src:eegdev] eegdev: FTBFS: ./doc/examples/library-usage/eegdev_acq.c:214: undefined reference to `rpl_free' Added tag(s) pending. -- 997209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997209 Debian Bug Tracking System Contact

Bug#997209: [Help needed] eegdev: FTBFS: ./doc/examples/library-usage/eegdev_acq.c:214: undefined reference to `rpl_free'

Nilesh Patra writes: > I have no idea why it can not find free() -- looks like something changed > with new autotools. > I don't know much about autotools, and need help to figure out what might be > wrong -- would you have any pointers? These errors look like fallout from a new check: >

Bug#995021: osmnx: autopkgtest regression on armhf: iteration over a 0-d array

On Mon, 1 Nov 2021 20:49:58 +0100 Paul Gevers wrote: Hello Paul, Is this run on all cores? Our armhf worker has 160 cores, so you may be running into limits you didn't expect. I can reproduce the issue on my amd64 box by substituting mp.cpu_count() by 160 in the called function. We are

Bug#995346:

Processed: severity of 986487 is serious, tagging 986487, found 997414 in 0.25+git20210925-1, tagging 997518 ...

Processing commands for cont...@bugs.debian.org: > severity 986487 serious Bug #986487 [caftools] caftools: FTBFS with glibc >= 2.32 Severity set to 'serious' from 'normal' > tags 986487 + sid bookworm ftbfs Bug #986487 [caftools] caftools: FTBFS with glibc >= 2.32 Added tag(s) sid, ftbfs, and

Bug#997729: marked as done (ghdl: FTBFS: Unhandled version llvm 11.1.0)

Your message dated Tue, 02 Nov 2021 12:51:16 + with message-id and subject line Bug#997729: fixed in ghdl 1.0.0+dfsg-5 has caused the Debian Bug report #997729, regarding ghdl: FTBFS: Unhandled version llvm 11.1.0 to be marked as done. This means that you claim that the problem has been

Processed: Re: python3-numpy: numpy.typing is missing

Processing control commands: > severity -1 serious Bug #998109 [python3-numpy] python3-numpy: numpy.typing is missing Severity set to 'serious' from 'important' > affects -1 src:pygmsh src:python-meshplex Bug #998109 [python3-numpy] python3-numpy: numpy.typing is missing Added indication that

Bug#997209: [Help needed] eegdev: FTBFS: ./doc/examples/library-usage/eegdev_acq.c:214: undefined reference to `rpl_free'

Hi all, On Sat, 23 Oct 2021 21:11:26 +0200 Lucas Nussbaum wrote: Source: eegdev Version: 0.2-5 Relevant part (hopefully): > /usr/bin/ld: library-usage/eegdev_acq.o: in function `main': > ./doc/examples/library-usage/eegdev_acq.c:214: undefined reference to `rpl_free' > /usr/bin/ld:

Bug#980627: ruby-databojects-mysql (was: [RFH] Fix FTBFSes to kick off the ruby3.0 transition)

Am Mittwoch, dem 27.10.2021 um 11:02 -0300 schrieb Lucas Kanashiro: [..] > * ruby-databojects-mysql [..] My finding so far is that the debian/start_mysqld_and_auto_install.sh scripts requires elevated permissions, but fakeroot is not enough: > + mysql_install_db --no-defaults

Bug#998296: marked as done (adios: autopktest failure)

Your message dated Tue, 02 Nov 2021 12:33:26 + with message-id and subject line Bug#998296: fixed in adios 1.13.1-30 has caused the Debian Bug report #998296, regarding adios: autopktest failure to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#997385: marked as done (pydicom: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet')

Your message dated Tue, 02 Nov 2021 12:34:05 + with message-id and subject line Bug#997385: fixed in pydicom 2.0.0-2 has caused the Debian Bug report #997385, regarding pydicom: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet' to be marked as done. This means that

Bug#998108: firefox freezes shortly after start

On Sat, 30 Oct 2021 15:04:01 +0200 Christoph Anton Mitterer wrote: > Since about yesterday (possibly since the rebuilt package came in) > firefox freezes shortly after being started. > There is no high CPU activity then, it just takes no input anymore > (no keyboard, no mouse clicks). > This

Processed: Bug#997385 marked as pending in pydicom

Processing control commands: > tag -1 pending Bug #997385 [src:pydicom] pydicom: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet' Added tag(s) pending. -- 997385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997385 Debian Bug Tracking System Contact

Bug#997385: marked as pending in pydicom

Control: tag -1 pending Hello, Bug #997385 in pydicom 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: retitle 997484 to python3-sqlalchemy: Undeclared dependency on python3-greenlet!=0.4.17

Processing commands for cont...@bugs.debian.org: > retitle 997484 python3-sqlalchemy: Undeclared dependency on > python3-greenlet!=0.4.17 Bug #997484 [python3-sqlalchemy] python3-sqlalchemy: Undeclared dependency on python3-greenlet Changed Bug title to 'python3-sqlalchemy: Undeclared

Bug#995843: abook: complete d/copyright file

Hey Jochen, resolving would need to enhance the copyright file so that it fulfills all the required information. Bastian already did a good job and likely the patch provided should be sufficient for that. I haven't gotten around yet to upload that, but plan to do so in the next few days.

Processed: Re: Bug#998126: pipewire-pulse-dbgsym: dbgsym files overlap between packages

Processing control commands: > tags -1 help Bug #998126 [src:pipewire] pipewire-pulse-dbgsym: dbgsym files overlap between packages Added tag(s) help. -- 998126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#998126: pipewire-pulse-dbgsym: dbgsym files overlap between packages

Control: tags -1 help Hi, Le sam. 30 oct. 2021 à 21:09, Martin-Éric Racine a écrit : > > Selecting previously unselected package libpipewire-0.3-0-dbgsym:i386. > (Reading database ... 127295 files and directories currently installed.) > Preparing to unpack

Bug#997245: marked as done (lynkeos.app: FTBFS: MyImageAligner.m:851:16: error: too few arguments to function ‘dgesvd_’)

Your message dated Tue, 02 Nov 2021 11:49:41 + with message-id and subject line Bug#997245: fixed in lynkeos.app 3.4+dfsg1-3 has caused the Debian Bug report #997245, regarding lynkeos.app: FTBFS: MyImageAligner.m:851:16: error: too few arguments to function ‘dgesvd_’ to be marked as done.

Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14

Hi Christoph, Le mercredi 06 octobre 2021 à 23:14 +0200, Christoph Berg a écrit : > Package: pgloader > Version: 3.6.2-1 > Severity: grave > Tags: ftbfs > > pgloader is currently not supporting PG14's new default of scram > authentication: > >

Processed: ITP: cl-global-vars -- efficient global variables in Common Lisp

Processing control commands: > block 995846 by -1 Bug #995846 [pgloader] FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14 995846 was blocked by: 998321 995846 was not blocking any bugs. Added blocking bug(s) of 995846: 998322 -- 995846:

  1   2   >