Bug#1013156: gdcm: vtk[6,7] removal

Hi, in the bug log there is some discussion to drop C# and Java VTK bindings. This would mean to drop the packages libvtkgdcm-cil and libvtkgdcm-java. I'm perfectly fine with this and I just pushed a change in d/control where I replaced s/vtk7/vtk9/ globally. The build[1] is currently failing

Bug#1022348: gpgme1.0: FTBFS: Could not find gpg-error-config. Please install the libgpg-error development package.

Control: tags -1 patch Control: tags -1 fixed-upstream On 2022-10-25 Andreas Metzler wrote: > Control: forwarded -1 https://dev.gnupg.org/T6204 > On 2022-10-23 Lucas Nussbaum wrote: > > Source: gpgme1.0 > > Version: 1.18.0-1 > [...] > > > Could not find gpg-error-config. Please install the

Processed: Re: Bug#1022348: gpgme1.0: FTBFS: Could not find gpg-error-config. Please install the libgpg-error development package.

Processing control commands: > tags -1 patch Bug #1022348 [src:gpgme1.0] gpgme1.0: FTBFS: Could not find gpg-error-config. Please install the libgpg-error development package. Added tag(s) patch. > tags -1 fixed-upstream Bug #1022348 [src:gpgme1.0] gpgme1.0: FTBFS: Could not find

Processed: libcache-memcached-fast-perl: autopkgtest regression: missing symbols

Processing control commands: > block 1019353 by -1 Bug #1019353 [release.debian.org] transition: perl 5.36 1019353 was blocked by: 1020446 1022132 1016761 1022152 1021735 1021324 1019353 was blocking: 1022003 Added blocking bug(s) of 1019353: 1022793 -- 1019353:

Bug#1022793: libcache-memcached-fast-perl: autopkgtest regression: missing symbols

Source: libcache-memcached-fast-perl Version: 0.28-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Control: block 1019353 by -1 Dear maintainer(s), With a recent upload of libcache-memcached-fast-perl the autopkgtest of libcache-memcached-fast-perl fails in testing

Processed: removed packages don't block transition

Processing commands for cont...@bugs.debian.org: > unblock 1019353 by 1022124 Bug #1019353 [release.debian.org] transition: perl 5.36 1019353 was blocked by: 1022124 1020446 1021658 1022132 1022133 1021735 1022780 1016761 1022150 1022152 1021324 1019353 was blocking: 1022003 Removed blocking

Bug#1022277: marked as done (libstringprep-java: FTBFS: [ERROR] Plugin org.codehaus.mojo:build-helper-maven-plugin:3.0.0 or one of its dependencies could not be resolved: Cannot access central (https:

Your message dated Wed, 26 Oct 2022 05:19:26 + with message-id and subject line Bug#1022277: fixed in libstringprep-java 1.1-3 has caused the Debian Bug report #1022277, regarding libstringprep-java: FTBFS: [ERROR] Plugin org.codehaus.mojo:build-helper-maven-plugin:3.0.0 or one of its

Bug#1021193:

I looked for exactly this bug as I fixed the same issue in binutils-riscv-unknown-elf today, but somehow I missed it. This should be fixed in version 18 by using dpkg-query instead of hand-hacked shell bits: upstream_version := $(shell dpkg-query -W -f="\$${source:Upstream-Version}\n"

Processed: fixed 1022778 in 2:4.17.2+dfsg-2

Processing commands for cont...@bugs.debian.org: > fixed 1022778 2:4.17.2+dfsg-2 Bug #1022778 {Done: Michael Tokarev } [samba] samba: Upgrade failed: unhandled file move /etc/pam.d/samba both in samba and samba-common Marked as fixed in versions samba/2:4.17.2+dfsg-2. > thanks Stopping

Bug#1022788: cockpit: FTBFS on armel/mipsel/mips64el: dh_auto_test failures

Hello Michael, hello Lis, Michael Biebl [2022-10-26 1:41 +0200]: > cockpit seems to fail its test suite on the aforementioned architectures Thanks for the report! > on armel: > ~ > Bail out! GLib-FATAL-WARNING: GChildWatchSource: Exit status of a child > process was requested but

Bug#1022791: tripwire --check segfaults on startup (probably needs rebuild)

Package: tripwire Version: 2.4.3.7-4+b3 Severity: grave X-Debbugs-Cc: r...@debian.org Looks like tripwire needs another rebuild against the latest libc6. tripwire --check and tripwire --init both segfault once they start analyzing the file system. Rebuilding the package with no changes causes it

Bug#1017817: New upload should resolve native compilation fork bomb problem

Hello, Could you see if the upload I just made, 28.2+1-2, still shows the problem, please? It includes a backported upstream fix. Thanks. -- Sean Whitton signature.asc Description: PGP signature

Bug#1022781: Unable to lock an existing session

Hi Martin, Your bug report is appreciated. On Tue, Oct 25, 2022 at 08:33:23PM +0200, martin f krafft wrote: > Package: xautolock > Version: 1:2.2-7 > Severity: critical > Tags: security > > This is not software you can rely on to lock your screen: I guess the exit value of your `xautolock

Processed: found 1022527 in 0.6.6-1

Processing commands for cont...@bugs.debian.org: > found 1022527 0.6.6-1 Bug #1022527 [src:ddupdate] ddupdate: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command Marked as found in versions ddupdate/0.6.6-1. > thanks Stopping processing here. Please contact me if

Bug#1022788: cockpit: FTBFS on armel/mipsel/mips64el: dh_auto_test failures

Source: cockpit Version: 276.1-1 Severity: serious cockpit seems to fail its test suite on the aforementioned architectures on armel: ~ (cockpit-bridge:13294): cockpit-bridge-WARNING **: 11:53:58.528: couldn't create runtime dir: /run/user/2952: Permission denied cockpit-bridge-Message:

Processed: openjfx: diff for NMU version 11.0.11+0-1.1

Processing control commands: > tags 1004638 + patch Bug #1004638 {Done: Philipp Kern } [src:openjfx] openjfx: FTBFS with ffmpeg 5.0 Ignoring request to alter tags of bug #1004638 to the same tags previously set > tags 1004638 + pending Bug #1004638 {Done: Philipp Kern } [src:openjfx] openjfx:

Bug#1004638: openjfx: diff for NMU version 11.0.11+0-1.1

Control: tags 1004638 + patch Control: tags 1004638 + pending Control: tags 1013009 + patch Control: tags 1013009 + pending Dear maintainer, I've prepared an NMU for openjfx (versioned as 11.0.11+0-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer.

Processed: openjfx: diff for NMU version 11.0.11+0-1.1

Processing control commands: > tags 1004638 + patch Bug #1004638 {Done: Philipp Kern } [src:openjfx] openjfx: FTBFS with ffmpeg 5.0 Added tag(s) patch. > tags 1004638 + pending Bug #1004638 {Done: Philipp Kern } [src:openjfx] openjfx: FTBFS with ffmpeg 5.0 Added tag(s) pending. > tags 1013009 +

Processed: tagging 1020819

Processing commands for cont...@bugs.debian.org: > tags 1020819 + pending Bug #1020819 [subtitlecomposer] subtitlecomposer: Cannot load any video: "Option refcounted_frames not found" error (removed from FFmpeg) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you

Bug#1022783: closing 1022783

close 1022783 0.9.4-2 thanks -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB

Processed: closing 1022783

Processing commands for cont...@bugs.debian.org: > close 1022783 0.9.4-2 Bug #1022783 {Done: Peter Green } [librust-spin-dev] librust-curl-dev: impossible to install Marked as fixed in versions rust-spin/0.9.4-2. Bug #1022783 {Done: Peter Green } [librust-spin-dev] librust-curl-dev: impossible

Bug#1019783: marked as done (openyahtzee: Please transition to wxwidgets3.2)

Your message dated Tue, 25 Oct 2022 22:22:01 + with message-id and subject line Bug#1019783: fixed in openyahtzee 1.9.3-5 has caused the Debian Bug report #1019783, regarding openyahtzee: Please transition to wxwidgets3.2 to be marked as done. This means that you claim that the problem has

Bug#1019773: marked as done (asc: Please transition to wxwidgets3.2)

Your message dated Tue, 25 Oct 2022 21:49:35 + with message-id and subject line Bug#1019773: fixed in asc 2.6.1.0-9 has caused the Debian Bug report #1019773, regarding asc: Please transition to wxwidgets3.2 to be marked as done. This means that you claim that the problem has been dealt

Bug#1022385: [Pkg-electronics-devel] Bug#1022385: pcb-rnd: FTBFS: diff: out.copper_p2.svg: No such file or directory

Lucas Nussbaum writes: > Source: pcb-rnd > Version: 3.0.5-3 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20221023 ftbfs-bookworm > > During a rebuild of all packages in sid, your package failed to build > on amd64. Thanks for

Processed: Bug#1019773 marked as pending in asc

Processing control commands: > tag -1 pending Bug #1019773 [src:asc] asc: Please transition to wxwidgets3.2 Added tag(s) pending. -- 1019773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019773 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1019773: marked as pending in asc

Control: tag -1 pending Hello, Bug #1019773 in asc 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#1022722: marked as done (tftp-hpa: missing versioned Breaks+Replaces: tftp (<< 0.17-23.1))

Your message dated Tue, 25 Oct 2022 20:52:19 + with message-id and subject line Bug#1022722: fixed in tftp-hpa 5.2+20150808-1.4 has caused the Debian Bug report #1022722, regarding tftp-hpa: missing versioned Breaks+Replaces: tftp (<< 0.17-23.1) to be marked as done. This means that you

Bug#1019724: marked as done (warning: stray \ before - causes autopkgtest failure)

Your message dated Tue, 25 Oct 2022 20:35:04 + with message-id and subject line Bug#1019724: fixed in grep 3.8-3 has caused the Debian Bug report #1019724, regarding warning: stray \ before - causes autopkgtest failure to be marked as done. This means that you claim that the problem has been

Processed: Raising severity of remaining wxwidgets3.2 transition blockers

Processing commands for cont...@bugs.debian.org: > severity 1019833 serious Bug #1019833 {Done: Andreas Metzler } [src:hugin] hugin: Please transition to wxwidgets3.2 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#1022786: glirc: unsatisfiable build-dependency libghc-attoparsec-dev (<< 0.14)

Source: glirc Version: 2.36-3 Severity: serious Hi, glirc build-depends on libghc-attoparsec-dev (<< 0.14). However, the current version of that package in sid is 0.14.4-2+b1. -Ralf.

Bug#1022785: guacamole-client: build-depends on removed libangular-maven-plugin-java

Source: guacamole-client Version: 0.9.9+dfsg-1 Severity: serious Hi, guacamole-client build-depends on libangular-maven-plugin-java but that package only exists in oldoldstable. -Ralf.

Bug#1022783: marked as done (librust-curl-dev: impossible to install)

Your message dated Tue, 25 Oct 2022 20:43:57 +0100 with message-id <019f3465-cc65-6bcd-517e-e9864a78c...@debian.org> and subject line re: librust-curl-dev: impossible to install has caused the Debian Bug report #1022783, regarding librust-curl-dev: impossible to install to be marked as done. This

Processed: Re: Bug#1022783: librust-curl-dev: impossible to install

Processing control commands: > reassign 1022783 librust-spin-dev 0.9.4-1 Bug #1022783 [librust-curl-dev] librust-curl-dev: impossible to install Bug reassigned from package 'librust-curl-dev' to 'librust-spin-dev'. No longer marked as found in versions rust-curl/0.4.44-1. Ignoring request to

Bug#1022783: librust-curl-dev: impossible to install

Control: reassign 1022783 librust-spin-dev 0.9.4-1 Control: affects 1022783 + librust-curl-dev On Tue 2022-10-25 21:28:38 +0200, Jonas Smedegaard wrote: > Package is impossible to install: > > # apt install librust-curl-dev > Reading package lists... Done > Building dependency tree... Done >

Processed: reassign 1021753 to src:ganeti

Processing commands for cont...@bugs.debian.org: > reassign 1021753 src:ganeti Bug #1021753 [ganeti] ganeti: conflicting curl build-depends Bug reassigned from package 'ganeti' to 'src:ganeti'. No longer marked as found in versions ganeti/3.0.2-1. Ignoring request to alter fixed versions of bug

Processed: reassign 974792 to src:beignet

Processing commands for cont...@bugs.debian.org: > reassign 974792 src:beignet Bug #974792 [beignet] beignet: Please upgrade to llvm-toolchain-11 Bug #974805 [beignet] beignet: Please upgrade to llvm-toolchain-11 Bug reassigned from package 'beignet' to 'src:beignet'. Bug reassigned from package

Bug#1022783: librust-curl-dev: impossible to install

Package: librust-curl-dev Version: 0.4.44-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package is impossible to install: # apt install librust-curl-dev Reading package lists... Done Building dependency tree... Done Reading state

Processed: Mark bug 1022344 as help needed

Processing commands for cont...@bugs.debian.org: > tags 1022344 +help Bug #1022344 [src:libuser] libuser: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 Added tag(s) help. > thanks Stopping processing here. Please contact me if you need

Processed: closing 1022433

Processing commands for cont...@bugs.debian.org: > close 1022433 1.4-4 Bug #1022433 [src:pgsql-asn1oid] pgsql-asn1oid: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked as fixed in versions pgsql-asn1oid/1.4-4. Bug #1022433

Processed: closing 1022528

Processing commands for cont...@bugs.debian.org: > close 1022528 2.10.0-8 Bug #1022528 [src:postgresql-plproxy] postgresql-plproxy: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked as fixed in versions postgresql-plproxy/2.10.0-8. Bug

Processed: closing 1022517

Processing commands for cont...@bugs.debian.org: > close 1022517 2.8.0-3 Bug #1022517 [src:postgresql-mysql-fdw] postgresql-mysql-fdw: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked as fixed in versions postgresql-mysql-fdw/2.8.0-3.

Processed: closing 1022479

Processing commands for cont...@bugs.debian.org: > close 1022479 3.5-1 Bug #1022479 [src:pgq] pgq: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked as fixed in versions pgq/3.5-1. Bug #1022479 [src:pgq] pgq: FTBFS: Error: debian/control

Processed: closing 1022484

Processing commands for cont...@bugs.debian.org: > close 1022484 1.1.2-1 Bug #1022484 [src:postgresql-debversion] postgresql-debversion: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked as fixed in versions

Processed: closing 1022489

Processing commands for cont...@bugs.debian.org: > close 1022489 1.8.0.final-2 Bug #1022489 [src:postgres-decoderbufs] postgres-decoderbufs: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked as fixed in versions

Processed: closing 1022467

Processing commands for cont...@bugs.debian.org: > close 1022467 1.2.4-2 Bug #1022467 [src:pgpointcloud] pgpointcloud: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked as fixed in versions pgpointcloud/1.2.4-2. Bug #1022467

Processed: closing 1022460

Processing commands for cont...@bugs.debian.org: > close 1022460 1.2.2-1 Bug #1022460 {Done: Adrian Bunk } [src:postgresql-periods] postgresql-periods: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked as fixed in versions

Processed: closing 1022460

Processing commands for cont...@bugs.debian.org: > close 1022460 Bug #1022460 [src:postgresql-periods] postgresql-periods: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked Bug as done > thanks Stopping processing here. Please contact

Processed: closing 1022501

Processing commands for cont...@bugs.debian.org: > close 1022501 1.1.1+2021-11-10-2 Bug #1022501 [src:pgsphere] pgsphere: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked as fixed in versions pgsphere/1.1.1+2021-11-10-2. Bug #1022501

Processed: closing 1022512

Processing commands for cont...@bugs.debian.org: > close 1022512 1.0.4-5 Bug #1022512 [src:postgresql-pgmp] postgresql-pgmp: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked as fixed in versions postgresql-pgmp/1.0.4-5. Bug #1022512

Processed: closing 1022510

Processing commands for cont...@bugs.debian.org: > close 1022510 1:1.5-1 Bug #1022510 [src:pldebugger] pldebugger: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked as fixed in versions pldebugger/1:1.5-1. Bug #1022510 [src:pldebugger]

Processed: closing 1022455

Processing commands for cont...@bugs.debian.org: > close 1022455 1.0.4-10 Bug #1022455 [src:postgresql-prioritize] postgresql-prioritize: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked as fixed in versions

Bug#1022781: Unable to lock an existing session

Package: xautolock Version: 1:2.2-7 Severity: critical Tags: security This is not software you can rely on to lock your screen: ``` lotus:~% xautolock -locknow Could not locate a running xautolock. lotus:~% ps aux | grep '[x]autolo' madduck 172688 0.0 0.0 6584 2756 ?SOct23

Processed: closing 1022524

Processing commands for cont...@bugs.debian.org: > close 1022524 1.3-5 Bug #1022524 [src:postgresql-numeral] postgresql-numeral: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked as fixed in versions postgresql-numeral/1.3-5. Bug

Processed: closing 1022424

Processing commands for cont...@bugs.debian.org: > close 1022424 1:8.4.5-2 Bug #1022424 [src:plr] plr: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked as fixed in versions plr/1:8.4.5-2. Bug #1022424 [src:plr] plr: FTBFS: Error:

Processed: closing 1022444

Processing commands for cont...@bugs.debian.org: > close 1022444 2.2.2-2 Bug #1022444 [src:plpgsql-check] plpgsql-check: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked as fixed in versions plpgsql-check/2.2.2-2. Bug #1022444

Processed: closing 1022465

Processing commands for cont...@bugs.debian.org: > close 1022465 2.0.0-7 Bug #1022465 [src:postgresql-q3c] postgresql-q3c: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked as fixed in versions postgresql-q3c/2.0.0-7. Bug #1022465

Processed: block

Processing commands for cont...@bugs.debian.org: > block 1019353 with 1022780 Bug #1019353 [release.debian.org] transition: perl 5.36 1019353 was blocked by: 1021735 1022132 1021324 1021658 1022124 1022133 1016761 1022150 1022152 1020446 1019353 was blocking: 1022003 Added blocking bug(s) of

Bug#1022778: marked as done (samba: Upgrade failed: unhandled file move /etc/pam.d/samba both in samba and samba-common)

Your message dated Tue, 25 Oct 2022 21:02:49 +0300 with message-id and subject line Re: Bug#1022778: samba: Upgrade failed: unhandled file move /etc/pam.d/samba both in samba and samba-common has caused the Debian Bug report #1022778, regarding samba: Upgrade failed: unhandled file move

Bug#1022780: libobject-remote-perl: FTBFS on various architectures: test failures

Package: libobject-remote-perl Version: 0.004001-2 Severity: serious Tags: ftbfs User: debian-p...@lists.debian.org Usertags: perl-5.36-transition This package fails its test suite with Perl 5.36 on various architectures including i386, armel, armhf and ppc64el. This also makes the package fail

Bug#1022775: marked as done (samba: breaks apt upgrade)

Your message dated Tue, 25 Oct 2022 17:53:28 + with message-id and subject line Bug#1022775: fixed in samba 2:4.17.2+dfsg-2 has caused the Debian Bug report #1022775, regarding samba: breaks apt upgrade to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1022775: marked as done (samba: breaks apt upgrade)

Your message dated Tue, 25 Oct 2022 17:52:34 + with message-id and subject line Bug#1022775: fixed in samba 2:4.16.6+dfsg-3 has caused the Debian Bug report #1022775, regarding samba: breaks apt upgrade to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1022778: samba: Upgrade failed: unhandled file move /etc/pam.d/samba both in samba and samba-common

Package: samba Severity: grave Version: 2:4.16.6+dfsg-2 X-Debbugs-CC: m...@tls.msk.ru Dear Debian samba maintainers, The following dpkg error will occur when upgrading samba to 2:4.16.6+dfsg-2 from 2:4.16.5+dfsg-2+b1: ... Preparing to unpack .../samba_2%3a4.16.6+dfsg-2_amd64.deb ... Unpacking

Processed (with 2 errors): your mail

Processing commands for cont...@bugs.debian.org: > merge 1022776 1022775 Bug #1022776 [samba] samba: unable to upgarde to 2:4.16.6+dfsg-2 Unable to merge bugs because: severity of #1022775 is 'serious' not 'normal' Failed to merge 1022776: Did not alter merged bugs. > I was too late, sorry! :-)

Processed: Re: [Pkg-samba-maint] Bug#1022775: samba: breaks apt upgrade

Processing control commands: > tag -1 + confirmed pending Bug #1022775 [samba] samba: breaks apt upgrade Added tag(s) confirmed and pending. > severity -1 serious Bug #1022775 [samba] samba: breaks apt upgrade Severity set to 'serious' from 'normal' -- 1022775:

Bug#1019533: marked as done (scipy breaks libflame autopkgtest on i386: Floating point exception)

Your message dated Tue, 25 Oct 2022 17:06:40 + with message-id and subject line Bug#1019478: fixed in libflame 5.2.0-4 has caused the Debian Bug report #1019478, regarding scipy breaks libflame autopkgtest on i386: Floating point exception to be marked as done. This means that you claim that

Bug#1019525: marked as done (libflame: flaky autopkgtest: numpy-with-libflame times out)

Your message dated Tue, 25 Oct 2022 17:06:40 + with message-id and subject line Bug#1019525: fixed in libflame 5.2.0-4 has caused the Debian Bug report #1019525, regarding libflame: flaky autopkgtest: numpy-with-libflame times out to be marked as done. This means that you claim that the

Bug#1019478: marked as done (libflame: failing numpy tests (avx512) in testing transition tests)

Your message dated Tue, 25 Oct 2022 17:06:40 + with message-id and subject line Bug#1019478: fixed in libflame 5.2.0-4 has caused the Debian Bug report #1019478, regarding libflame: failing numpy tests (avx512) in testing transition tests to be marked as done. This means that you claim that

Bug#1018074: marked as done (libflame: flaky autopkgtest on s390x: test_concatenate_int32_overflow Killed)

Your message dated Tue, 25 Oct 2022 17:06:40 + with message-id and subject line Bug#1018074: fixed in libflame 5.2.0-4 has caused the Debian Bug report #1018074, regarding libflame: flaky autopkgtest on s390x: test_concatenate_int32_overflow Killed to be marked as done. This means that you

Bug#1022420: marked as done (rust-semver: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 101)

Your message dated Tue, 25 Oct 2022 16:19:58 + with message-id and subject line Bug#1022420: fixed in rust-semver 1.0.14-1 has caused the Debian Bug report #1022420, regarding rust-semver: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 101 to be marked

Bug#1022348: gpgme1.0: FTBFS: Could not find gpg-error-config. Please install the libgpg-error development package.

Control: forwarded -1 https://dev.gnupg.org/T6204 On 2022-10-23 Lucas Nussbaum wrote: > Source: gpgme1.0 > Version: 1.18.0-1 [...] > > Could not find gpg-error-config. Please install the libgpg-error > > development package. > > make[4]: *** [Makefile:760: all-local] Error 1 [...] There is a

Processed: Re: Bug#1022348: gpgme1.0: FTBFS: Could not find gpg-error-config. Please install the libgpg-error development package.

Processing control commands: > forwarded -1 https://dev.gnupg.org/T6204 Bug #1022348 [src:gpgme1.0] gpgme1.0: FTBFS: Could not find gpg-error-config. Please install the libgpg-error development package. Set Bug forwarded-to-address to 'https://dev.gnupg.org/T6204'. -- 1022348:

Bug#1022733: marked as done (nova: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

Your message dated Tue, 25 Oct 2022 16:09:04 + with message-id and subject line Bug#1022733: fixed in nova 2:26.0.0-2 has caused the Debian Bug report #1022733, regarding nova: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity to be marked as done. This means that you

Bug#1004310: marked as done (knxd: ftbfs with glibc 2.34: don't use common unix function name as variable name)

Your message dated Tue, 25 Oct 2022 16:08:26 + with message-id and subject line Bug#1004310: fixed in knxd 0.14.54.1 has caused the Debian Bug report #1004310, regarding knxd: ftbfs with glibc 2.34: don't use common unix function name as variable name to be marked as done. This means that

Bug#1017139: marked as done (knxd: FTBFS: knxd_args.cpp:71:13: error: ‘char link [99]’ redeclared as different kind of entity)

Your message dated Tue, 25 Oct 2022 16:08:26 + with message-id and subject line Bug#1004310: fixed in knxd 0.14.54.1 has caused the Debian Bug report #1004310, regarding knxd: FTBFS: knxd_args.cpp:71:13: error: ‘char link [99]’ redeclared as different kind of entity to be marked as done.

Processed: Bug#1022733 marked as pending in nova

Processing control commands: > tag -1 pending Bug #1022733 [src:nova] nova: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Added tag(s) pending. -- 1022733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022733 Debian Bug Tracking System Contact

Bug#1022733: marked as pending in nova

Control: tag -1 pending Hello, Bug #1022733 in nova 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#1021859: marked as done (pgbouncer FTBFS: test failures)

Your message dated Tue, 25 Oct 2022 14:36:27 + with message-id and subject line Bug#1021859: fixed in pgbouncer 1.17.0-4 has caused the Debian Bug report #1021859, regarding pgbouncer FTBFS: test failures to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1002789: python-pycdlib: FTBFS: failed tests

Control: severity -1 important Can't reproduce ...

Processed: Re: Bug#1002789: python-pycdlib: FTBFS: failed tests

Processing control commands: > severity -1 important Bug #1002789 [src:python-pycdlib] python-pycdlib: FTBFS: failed tests Severity set to 'important' from 'serious' -- 1002789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002789 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1019762: marked as done (saga: Please transition to wxwidgets3.2)

Your message dated Tue, 25 Oct 2022 13:35:25 + with message-id and subject line Bug#1019762: fixed in saga 8.4.0+dfsg-1 has caused the Debian Bug report #1019762, regarding saga: Please transition to wxwidgets3.2 to be marked as done. This means that you claim that the problem has been dealt

Bug#1003479: swig: Missing support for php8.1

On Sun, 16 Oct 2022 08:51:35 + Philipp Kern wrote: On Mon, Jan 10, 2022 at 10:21:11PM +0100, Vincent Danjean wrote: > Looking at upstream, support for php8 will be present in swig 4.1.0 that is > not yet released. It looks like it's due to be released in a week (2022-10-24). 4.1.0 was

Bug#1022732: marked as done (macaulay2: FTBFS: make: *** [debian/rules:18: binary] Error 25)

Your message dated Tue, 25 Oct 2022 12:20:09 + with message-id and subject line Bug#1022732: fixed in macaulay2 1.20+ds-8 has caused the Debian Bug report #1022732, regarding macaulay2: FTBFS: make: *** [debian/rules:18: binary] Error 25 to be marked as done. This means that you claim that

Bug#1019782: marked as done (gnudatalanguage: Please transition to wxwidgets3.2)

Your message dated Tue, 25 Oct 2022 12:04:40 + with message-id and subject line Bug#1019782: fixed in gnudatalanguage 1.0.1-4 has caused the Debian Bug report #1019782, regarding gnudatalanguage: Please transition to wxwidgets3.2 to be marked as done. This means that you claim that the

Bug#981522: marked as done (varmon - ship with bullseye?)

Your message dated Tue, 25 Oct 2022 11:57:56 + with message-id and subject line Bug#1022329: Removed package(s) from unstable has caused the Debian Bug report #981522, regarding varmon - ship with bullseye? to be marked as done. This means that you claim that the problem has been dealt with.

Bug#981523: marked as done (fusesmb: ship with bullseye?)

Your message dated Tue, 25 Oct 2022 11:58:33 + with message-id and subject line Bug#1022328: Removed package(s) from unstable has caused the Debian Bug report #981523, regarding fusesmb: ship with bullseye? to be marked as done. This means that you claim that the problem has been dealt with.

Bug#965860: marked as done (varmon: Removal of obsolete debhelper compat 5 and 6 in bookworm)

Your message dated Tue, 25 Oct 2022 11:57:56 + with message-id and subject line Bug#1022329: Removed package(s) from unstable has caused the Debian Bug report #965860, regarding varmon: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim

Bug#534756: marked as done (fusesmb.cache fails on 64-bit)

Your message dated Tue, 25 Oct 2022 11:58:33 + with message-id and subject line Bug#1022328: Removed package(s) from unstable has caused the Debian Bug report #534756, regarding fusesmb.cache fails on 64-bit to be marked as done. This means that you claim that the problem has been dealt

Bug#1022402: marked as done (pgaudit-1.6: FTBFS: make: *** [debian/rules:10: clean] Error 1)

Your message dated Tue, 25 Oct 2022 11:57:22 + with message-id and subject line Bug#1022273: Removed package(s) from unstable has caused the Debian Bug report #1022402, regarding pgaudit-1.6: FTBFS: make: *** [debian/rules:10: clean] Error 1 to be marked as done. This means that you claim

Bug#1014966: onionshare: CVE-2021-41867 CVE-2021-41868 CVE-2022-21688 CVE-2022-21689 CVE-2022-21690 CVE-2022-21691 CVE-2022-21692 CVE-2022-21693 CVE-2022-21694 CVE-2022-21695 CVE-2022-21696

Hi Moritz, Le 25/10/2022 à 11:15, Moritz Muehlenhoff a écrit : Hi Clément, Sadly, upstream rectified and confirms it affects 2.2 [0], and has been tested and reproduced on Bullseye. We do need to fix it. Upstream has a few suggestions, but I guess our choices are either uploading 2.5 to

Bug#1019782: marked as pending in gnudatalanguage

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

Processing control commands: > tag -1 pending Bug #1019782 [src:gnudatalanguage] gnudatalanguage: Please transition to wxwidgets3.2 Added tag(s) pending. -- 1019782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1021732: marked as done (libimage-exiftool-perl breaks mat2 autopkgtest: 'ColorProfiles' not found in ...)

Your message dated Tue, 25 Oct 2022 11:19:24 + with message-id and subject line Bug#1021732: fixed in mat2 0.13.0-2 has caused the Debian Bug report #1021732, regarding libimage-exiftool-perl breaks mat2 autopkgtest: 'ColorProfiles' not found in ... to be marked as done. This means that you

Bug#1012538: knocked out usability - module 'collections' has no attribute 'Callable'

On Thu, 9 Jun 2022 09:43:39 +0200 Christoph Berg wrote: > Re: Tyler Schwend > > The Debian packaged version is much older than the current version. > > The problem with chirp is that upstream isn't moving to python 3, the > porting branch seems stalled: > >

Bug#1014966: onionshare: CVE-2021-41867 CVE-2021-41868 CVE-2022-21688 CVE-2022-21689 CVE-2022-21690 CVE-2022-21691 CVE-2022-21692 CVE-2022-21693 CVE-2022-21694 CVE-2022-21695 CVE-2022-21696

Hi Clément, > Sadly, upstream rectified and confirms it affects 2.2 [0], and has been > tested and reproduced on Bullseye. We do need to fix it. Upstream has a few > suggestions, but I guess our choices are either uploading 2.5 to stable, if > that's possible. python-stem at least will need to be

Bug#1021732: [Pkg-privacy-maintainers] Bug#1021732: Bug#1021732: libimage-exiftool-perl breaks mat2 autopkgtest: 'ColorProfiles' not found in ...

Hi nodens, On 22-10-25 09:16:29, Clément Hermann wrote: > Do you mind if I cherry-pick the upstream fix and upload today ? > This is blocking the perl 5.36 transition. I do not, please do, and thanks in advance. Please push your changes, including the tag. Cheers, Georg

Bug#1021732: [Pkg-privacy-maintainers] Bug#1021732: libimage-exiftool-perl breaks mat2 autopkgtest: 'ColorProfiles' not found in ...

Hi Georg, Le 14/10/2022 à 11:12, Georg Faerber a écrit : Control: forwarded -1 https://0xacab.org/jvoisin/mat2/-/issues/178 Control: tags -1 + fixed-upstream upstream Hi Paul, On 22-10-13 19:52:35, Paul Gevers wrote: With a recent upload of libimage-exiftool-perl the autopkgtest of mat2

Bug#1014966: onionshare: CVE-2021-41867 CVE-2021-41868 CVE-2022-21688 CVE-2022-21689 CVE-2022-21690 CVE-2022-21691 CVE-2022-21692 CVE-2022-21693 CVE-2022-21694 CVE-2022-21695 CVE-2022-21696

Le 24/10/2022 à 20:41, Clément Hermann a écrit : - CVE-2022-21694 affects Bullseye, but that might be an acceptable risk ? The issue is that CSP can only be turned on or off, not configured to allow js etc, so it is only useful for static

Processed: Re: Processed: tagging 1019724

Processing control commands: > affects -1 -src:kbuild Bug #1019724 [grep] warning: stray \ before - causes autopkgtest failure Removed indication that 1019724 affects src:kbuild -- 1019724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019724 Debian Bug Tracking System Contact

Bug#1019724: Processed: tagging 1019724

control: affects -1 -src:kbuild On Thu, 20 Oct 2022 17:58:44 +0300 Adrian Bunk wrote: On Thu, Oct 20, 2022 at 04:17:18PM +0200, Santiago Ruano Rincón wrote: > El 20/10/22 a las 11:30, Debian Bug Tracking System escribió: > > Processing commands for cont...@bugs.debian.org: > > > > > tags

Bug#1021571: marked as done (smarty3: Parse error in /usr/share/php/smarty3/sysplugins/smarty_internal_templateparser.php on line 24)

Your message dated Tue, 25 Oct 2022 06:20:25 + with message-id and subject line Bug#1021571: fixed in smarty-lexer 3.1.32+dfsg1-5 has caused the Debian Bug report #1021571, regarding smarty3: Parse error in /usr/share/php/smarty3/sysplugins/smarty_internal_templateparser.php on line 24 to be

  1   2   >