Bug#1081426: Fix this for upstream

I have pull request this for upsteam: https://github.com/exult/exult/pull/560, and it has been accepted.

Processed: src:delve: fails to migrate to testing for too long

Processing control commands: > close -1 1.23.0-1 Bug #1081603 [src:delve] src:delve: fails to migrate to testing for too long Marked as fixed in versions delve/1.23.0-1. Bug #1081603 [src:delve] src:delve: fails to migrate to testing for too long Marked Bug as done -- 1081603: https://bugs.debia

Bug#1081603: src:delve: fails to migrate to testing for too long

Source: delve Version: 1.22.1-1 Severity: serious Control: close -1 1.23.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as hav

Bug#1081602: src:microsocks: fails to migrate to testing for too long

Source: microsocks Version: 1.0.3-2 Severity: serious Control: close -1 1.0.4-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as

Bug#1081601: src:python-skbio: fails to migrate to testing for too long

Source: python-skbio Version: 0.6.1-3 Severity: serious Control: close -1 0.6.2-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days a

Processed: src:microsocks: fails to migrate to testing for too long

Processing control commands: > close -1 1.0.4-2 Bug #1081602 [src:microsocks] src:microsocks: fails to migrate to testing for too long Marked as fixed in versions microsocks/1.0.4-2. Bug #1081602 [src:microsocks] src:microsocks: fails to migrate to testing for too long Marked Bug as done -- 10

Processed: src:python-skbio: fails to migrate to testing for too long

Processing control commands: > close -1 0.6.2-1 Bug #1081601 [src:python-skbio] src:python-skbio: fails to migrate to testing for too long Marked as fixed in versions python-skbio/0.6.2-1. Bug #1081601 [src:python-skbio] src:python-skbio: fails to migrate to testing for too long Marked Bug as do

Bug#1081600: src:rust-ring: fails to migrate to testing for too long

Source: rust-ring Version: 0.17.5-1 Severity: serious Control: close -1 0.17.8-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as

Processed: src:rust-ring: fails to migrate to testing for too long

Processing control commands: > close -1 0.17.8-1 Bug #1081600 [src:rust-ring] src:rust-ring: fails to migrate to testing for too long Marked as fixed in versions rust-ring/0.17.8-1. Bug #1081600 [src:rust-ring] src:rust-ring: fails to migrate to testing for too long Marked Bug as done -- 10816

Bug#1081599: src:halide: fails to migrate to testing for too long

Source: halide Version: 18.0.0-6 Severity: serious Control: close -1 18.0.0-8 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as ha

Processed: src:halide: fails to migrate to testing for too long

Processing control commands: > close -1 18.0.0-8 Bug #1081599 [src:halide] src:halide: fails to migrate to testing for too long Marked as fixed in versions halide/18.0.0-8. Bug #1081599 [src:halide] src:halide: fails to migrate to testing for too long Marked Bug as done -- 1081599: https://bugs.

Bug#1081598: cheese: fails to start with cheese-window.vala Parse error

Package: cheese Version: 44.1-1+b4 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, cheese fails to start ** (cheese:22772): ERROR **: 17:49:39.250: cheese-window.vala:1322: Error: :56:5: Parse error: unexpected character `'', expected character `]' Trace/

Bug#1080048: mlucas - program to perform Lucas-Lehmer test on a Mersenne number

Hi, FYI: The mclucas package ( program to perform Lucas-Lehmer test on a Mersenne number) will likely get removed from Debian sid soonish (and won't be released with upcoming trixie) unless someone spends some time on it soonish. See https://tracker.debian.org/pkg/mlucas and https://bugs.debian.o

Processed: downgrading, building sequentially is nice to have, but not a must

Processing control commands: > severity -1 important Bug #1081446 [src:gcc-12-cross] gcc-12-cross: FTBFS because of Makefile bug: ../../gnatbind: No such file or directory Severity set to 'important' from 'serious' -- 1081446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081446 Debian Bug

Processed: downgrading, building sequentially is nice to have, but not a must

Processing control commands: > severity -1 important Bug #1081448 [src:gcc-14-cross] gcc-14-cross: FTBFS because of Makefile bug: ../../gnatbind: No such file or directory Severity set to 'important' from 'serious' -- 1081448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081448 Debian Bug

Processed: downgrading, building sequentially is nice to have, but not a must

Processing control commands: > severity -1 important Bug #1081445 [src:gcc-11-cross] gcc-11-cross: FTBFS because of Makefile bug: ../../gnatbind: No such file or directory Severity set to 'important' from 'serious' -- 1081445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081445 Debian Bug

Processed: downgrading, building sequentially is nice to have, but not a must

Processing control commands: > severity -1 important Bug #1081447 [src:gcc-13-cross] gcc-13-cross: FTBFS because of Makefile bug: ../../gnatbind: No such file or directory Severity set to 'important' from 'serious' -- 1081447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081447 Debian Bug

Bug#1081446: downgrading, building sequentially is nice to have, but not a must

Control: severity -1 important Downgrading, building sequentially is nice to have, but not a must. And as you write, your fix just papers over a dependency issue. Please could you address this upstream, if it's really important for you?

Bug#1069959: libcbor FTBFS on hppa and mips to due different NaN encoding

Hi On 2024-09-11 23:01, Bo YU wrote: > Hi, > > Sorry for jumping into this topic. > > Is there anything I can do to push for updates to this package? > > Becasue the package blocked debci team to create riscv64/testing chroot > on our riscv64 workers due to this FTBFS on mips64el lead to fail t

Bug#1052105: marked as done (gnome-shell-extension-no-annoyance: needs update for GNOME Shell 46)

Your message dated Fri, 13 Sep 2024 04:18:56 + with message-id and subject line Bug#1052105: fixed in gnome-shell-extension-no-annoyance 0+20240813-8312e01-1 has caused the Debian Bug report #1052105, regarding gnome-shell-extension-no-annoyance: needs update for GNOME Shell 46 to be marked a

Bug#1081581: pg-partman: Build-depends on NBS postgresql-16-pgtap - will FTBFS when it is decrufted

Source: pg-partman Version: 4.7.2-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) postgresql-16-pgtap is NBS (replaced by postgresql-17-pgtap). Please update your build-depends. Scott K

Bug#1002430: marked as done (python-gear: FTBFS: ssl.SSLError: [SSL: NO_CIPHERS_AVAILABLE] no ciphers available (_ssl.c:997))

Your message dated Fri, 13 Sep 2024 02:58:48 + with message-id and subject line Bug#1081497: Removed package(s) from unstable has caused the Debian Bug report #1002430, regarding python-gear: FTBFS: ssl.SSLError: [SSL: NO_CIPHERS_AVAILABLE] no ciphers available (_ssl.c:997) to be marked as do

Bug#1019042: marked as done (rust-qwertone: FTBFS - dep issue)

Your message dated Fri, 13 Sep 2024 02:35:20 + with message-id and subject line Bug#1019042: fixed in qwertone 0.4.0-2 has caused the Debian Bug report #1019042, regarding rust-qwertone: FTBFS - dep issue to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: Re: Bug#1081078: guix: FTBFS: FAIL: tests/store.scm - export/import several paths

Processing control commands: > reassign 1081078 guile-gcrypt Bug #1081078 {Done: Vagrant Cascadian } [src:guix] guix: FTBFS: FAIL: tests/store.scm - export/import several paths Bug reassigned from package 'src:guix' to 'guile-gcrypt'. No longer marked as found in versions guix/1.4.0-7. No longer

Bug#1081078: guix: FTBFS: FAIL: tests/store.scm - export/import several paths

Control: reassign 1081078 guile-gcrypt Control: affects 1081078 guix > On 2024-09-08, Santiago Vila wrote: >> FAIL: tests/nar.scm - restore-file-set (signed, valid) >> FAIL: tests/nar.scm - restore-file-set with directories (signed, valid) >> FAIL: tests/nar.scm - restore-file-set (corrupt) ... >>

Bug#1052105: gnome-shell-extension-no-annoyance: needs update for GNOME Shell 46

On Wed, Aug 28, 2024 at 8:40 PM Hank Knox wrote: > I submitted a merge request for the first step, the updated files from > the new upstream source. Thank you for working on this package. I need to inform you that we will be uploading GNOME Shell 47 to Unstable soon after 47.0 is released in a fe

Bug#1079059: marked as done (libsbig4t64: file loss due to concurrent package rename and /usr-move (DEP17 P1))

Your message dated Thu, 12 Sep 2024 23:36:02 + with message-id and subject line Bug#1079059: fixed in libsbig 4.9.9-6 has caused the Debian Bug report #1079059, regarding libsbig4t64: file loss due to concurrent package rename and /usr-move (DEP17 P1) to be marked as done. This means that yo

Bug#1081580: gnome-shell-extension-panel-osd: Intent to remove from Debian

Source: gnome-shell-extension-panel-osd Version: 1.0.50.gc032923-4 Severity: serious gnome-shell-extension-panel-osd is not compatible with GNOME Shell >= 45. The current version of GNOME Shell in Debian Unstable is 46 and will likely be 47 later this month. Meanwhile, this extension has been aba

Processed: Re: workrave-gnome: needs update for GNOME Shell 47

Processing control commands: > severity -1 serious Bug #1079260 [workrave-gnome] workrave-gnome: needs update for GNOME Shell 47 Severity set to 'serious' from 'wishlist' > tags -1 +patch Bug #1079260 [workrave-gnome] workrave-gnome: needs update for GNOME Shell 47 Added tag(s) patch. > forwarded

Processed: Re: gnome-shell-extensions-extra: needs update for GNOME Shell 47

Processing control commands: > severity -1 serious Bug #1079257 [gnome-shell-extensions-extra] gnome-shell-extensions-extra: needs update for GNOME Shell 47 Severity set to 'serious' from 'wishlist' -- 1079257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079257 Debian Bug Tracking System

Processed: gnome-shell-extension-kimpanel: needs update for GNOME Shell 47

Processing control commands: > severity -1 serious Bug #1079253 [gnome-shell-extension-kimpanel] gnome-shell-extension-kimpanel: needs update for GNOME Shell 47 Severity set to 'serious' from 'wishlist' -- 1079253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079253 Debian Bug Tracking Sy

Processed: tagging 1081515

Processing commands for cont...@bugs.debian.org: > tags 1081515 = ftbfs Bug #1081515 [weston] weston: 14.x regression: crashes during gtk4 test suite Removed tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 1081515: https://bugs.debian.org/cgi-bin/bugr

Processed: forcibly merging 1078556 1081424

Processing commands for cont...@bugs.debian.org: > forcemerge 1078556 1081424 Bug #1078556 [bash] bash: 5.2.21-2.1 to 5.2.21-2.1+b1 breaks printf %.2f .1 Bug #1078583 [bash] bash: printf '%5.1f' 1.498 prints multiple lines of numbers Bug #1078583 [bash] bash: printf '%5.1f' 1.498 prints multiple l

Processed: tagging 1077671, tagging 1069872

Processing commands for cont...@bugs.debian.org: > tags 1077671 - patch Bug #1077671 [pkgconf] pkgconf: armhf DEP8 failure due to gcc warning Removed tag(s) patch. > tags 1069872 + patch Bug #1069872 [html2text] Autopkgtests fail on non-x86 Added tag(s) patch. > thanks Stopping processing here. P

Processed: tagging 1077671

Processing commands for cont...@bugs.debian.org: > tags 1077671 + patch Bug #1077671 [pkgconf] pkgconf: armhf DEP8 failure due to gcc warning Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1077671: https://bugs.debian.org/cgi-bin/bugreport.cgi

Processed: Re: gnome-shell-extension-hamster: needs update for GNOME Shell 47

Processing control commands: > severity -1 serious Bug #1079250 [gnome-shell-extension-hamster] gnome-shell-extension-hamster: needs update for GNOME Shell 47 Severity set to 'serious' from 'wishlist' > tags -1 +patch Bug #1079250 [gnome-shell-extension-hamster] gnome-shell-extension-hamster: ne

Processed: Re: gnome-shell-extension-autohidetopbar: needs update for GNOME Shell 47

Processing control commands: > severity -1 serious Bug #1079239 [gnome-shell-extension-autohidetopbar] gnome-shell-extension-autohidetopbar: needs update for GNOME Shell 47 Severity set to 'serious' from 'wishlist' > tags -1 +patch Bug #1079239 [gnome-shell-extension-autohidetopbar] gnome-shell-

Bug#1069872: [PATCH] d/patches: fix input type=checkbox output

Closes: #1077671 --- Hi! Here is a patch fixing this bug. You can apply this with `git am`. Bye :) debian/patches/series | 1 + debian/patches/string-before-concat.patch | 25 +++ debian/tests/pkgreport.html.supposed | 8 3 files changed, 3

Bug#1081517: marked as done (libcurl-gnutls.so.4 no longer linked with needed libraries)

Your message dated Thu, 12 Sep 2024 21:19:29 + with message-id and subject line Bug#1081533: fixed in curl 8.10.0-2 has caused the Debian Bug report #1081533, regarding libcurl-gnutls.so.4 no longer linked with needed libraries to be marked as done. This means that you claim that the problem

Bug#1081514: marked as done (libcurl-gnutls.so.4: undefined symbol: gnutls_free)

Your message dated Thu, 12 Sep 2024 21:19:29 + with message-id and subject line Bug#1081533: fixed in curl 8.10.0-2 has caused the Debian Bug report #1081533, regarding libcurl-gnutls.so.4: undefined symbol: gnutls_free to be marked as done. This means that you claim that the problem has been

Bug#1081533: marked as done (arm64: symbol lookup error: undefined symbol: gnutls_free)

Your message dated Thu, 12 Sep 2024 21:19:29 + with message-id and subject line Bug#1081533: fixed in curl 8.10.0-2 has caused the Debian Bug report #1081533, regarding arm64: symbol lookup error: undefined symbol: gnutls_free to be marked as done. This means that you claim that the problem h

Bug#1081533: marked as done (arm64: symbol lookup error: undefined symbol: gnutls_free)

Your message dated Thu, 12 Sep 2024 21:19:29 + with message-id and subject line Bug#1081517: fixed in curl 8.10.0-2 has caused the Debian Bug report #1081517, regarding arm64: symbol lookup error: undefined symbol: gnutls_free to be marked as done. This means that you claim that the problem h

Bug#1081517: marked as done (libcurl-gnutls.so.4 no longer linked with needed libraries)

Your message dated Thu, 12 Sep 2024 21:19:29 + with message-id and subject line Bug#1081514: fixed in curl 8.10.0-2 has caused the Debian Bug report #1081514, regarding libcurl-gnutls.so.4 no longer linked with needed libraries to be marked as done. This means that you claim that the problem

Bug#1081514: marked as done (libcurl-gnutls.so.4: undefined symbol: gnutls_free)

Your message dated Thu, 12 Sep 2024 21:19:29 + with message-id and subject line Bug#1081517: fixed in curl 8.10.0-2 has caused the Debian Bug report #1081517, regarding libcurl-gnutls.so.4: undefined symbol: gnutls_free to be marked as done. This means that you claim that the problem has been

Bug#1081517: marked as done (libcurl-gnutls.so.4 no longer linked with needed libraries)

Your message dated Thu, 12 Sep 2024 21:19:29 + with message-id and subject line Bug#1081517: fixed in curl 8.10.0-2 has caused the Debian Bug report #1081517, regarding libcurl-gnutls.so.4 no longer linked with needed libraries to be marked as done. This means that you claim that the problem

Bug#1081533: marked as done (arm64: symbol lookup error: undefined symbol: gnutls_free)

Your message dated Thu, 12 Sep 2024 21:19:29 + with message-id and subject line Bug#1081514: fixed in curl 8.10.0-2 has caused the Debian Bug report #1081514, regarding arm64: symbol lookup error: undefined symbol: gnutls_free to be marked as done. This means that you claim that the problem h

Bug#1081514: marked as done (libcurl-gnutls.so.4: undefined symbol: gnutls_free)

Your message dated Thu, 12 Sep 2024 21:19:29 + with message-id and subject line Bug#1081514: fixed in curl 8.10.0-2 has caused the Debian Bug report #1081514, regarding libcurl-gnutls.so.4: undefined symbol: gnutls_free to be marked as done. This means that you claim that the problem has been

Processed: Re: Bug#1081515: gtk4: FTBFS with weston 14: many tests fail with --setup=wayland: Failed to open display

Processing control commands: > retitle -1 weston: 14.x regression: crashes during gtk4 test suite Bug #1081515 [src:gtk4] gtk4: FTBFS with weston 14: many tests fail with --setup=wayland: Failed to open display Changed Bug title to 'weston: 14.x regression: crashes during gtk4 test suite' from '

Bug#1081515: gtk4: FTBFS with weston 14: many tests fail with --setup=wayland: Failed to open display

Control: retitle -1 weston: 14.x regression: crashes during gtk4 test suite Control: reassign -1 weston 14.0.0-1 Control: affects -1 + src:gtk4 On Thu, 12 Sep 2024 at 22:41:10 +0200, Aurelien Jarno wrote: > On 2024-09-12 20:59, Simon McVittie wrote: > > On Thu, 12 Sep 2024 at 11:48:21 +0100, Simon

Processed: bug 1018437 is forwarded to https://salsa.debian.org/debian/piuparts/-/merge_requests/65

Processing commands for cont...@bugs.debian.org: > forwarded 1018437 https://salsa.debian.org/debian/piuparts/-/merge_requests/65 Bug #1018437 [src:piuparts] piuparts: build-depends on python3-nose or uses it for autopkgtest Set Bug forwarded-to-address to 'https://salsa.debian.org/debian/piupar

Bug#1001528: marked as done (FTBFS with eigen3/3.4.0)

Your message dated Thu, 12 Sep 2024 20:51:23 + with message-id and subject line Bug#1001528: fixed in purify 4.1.0-1 has caused the Debian Bug report #1001528, regarding FTBFS with eigen3/3.4.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#1081515: gtk4: FTBFS with weston 14: many tests fail with --setup=wayland: Failed to open display

On 2024-09-12 20:59, Simon McVittie wrote: > Control: retitle -1 gtk4: FTBFS with weston 14: many tests fail with > --setup=wayland: Failed to open display > Control: severity -1 serious > > (Please remove -ports from cc in replies, this is no longer believed to > be -ports specific) > > On Thu,

Processed: tagging 1018525

Processing commands for cont...@bugs.debian.org: > tags 1018525 + wontfix Bug #1018525 [src:python-lockfile] python-lockfile: build-depends on python3-nose or uses it for autopkgtest Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 1018525: h

Processed: severity of 1018437 is serious

Processing commands for cont...@bugs.debian.org: > severity 1018437 serious Bug #1018437 [src:piuparts] piuparts: build-depends on python3-nose or uses it for autopkgtest Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1

Processed: Re: Bug#1081515: gtk4: FTBFS with weston 14: many tests fail with --setup=wayland: Failed to open display

Processing control commands: > retitle -1 gtk4: FTBFS with weston 14: many tests fail with --setup=wayland: > Failed to open display Bug #1081515 [src:gtk4] gtk4: FTBFS on -ports architectures: many tests fail with --setup=wayland: Failed to open display Changed Bug title to 'gtk4: FTBFS with we

Bug#1081561: php-twig: CVE-2024-45411

Source: php-twig Version: 3.8.0-3 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 3.5.1-1 Hi, The following vulnerability was published for php-twig. CVE-2024-45411[0]: | Twig is a template language for PHP. Under some circumstance

Processed: php-twig: CVE-2024-45411

Processing control commands: > found -1 3.5.1-1 Bug #1081561 [src:php-twig] php-twig: CVE-2024-45411 Marked as found in versions php-twig/3.5.1-1. -- 1081561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: ruby-saml: CVE-2024-45409

Processing control commands: > found -1 1.13.0-1 Bug #1081560 [src:ruby-saml] ruby-saml: CVE-2024-45409 Marked as found in versions ruby-saml/1.13.0-1. -- 1081560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1081560: ruby-saml: CVE-2024-45409

Source: ruby-saml Version: 1.15.0-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 1.13.0-1 Hi, The following vulnerability was published for ruby-saml. CVE-2024-45409[0]: | The Ruby SAML library is for implementing the client sid

Processed: [bts-link] source package src:jpy

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:jpy > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting

Processed: [bts-link] source package gnome-shell-extension-flypie

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package > gnome-shell-extension-flypie > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@

Processed: [bts-link] source package src:ponyorm

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:ponyorm > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Set

Processed: [bts-link] source package src:firebird3.0

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:firebird3.0 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: [bts-link] source package src:firebird4.0

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:firebird4.0 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Bug#1078293: marked as done (lxqt-config: FTBFS: Could not find a package configuration file provided by "Qt5LinguistTools")

Your message dated Thu, 12 Sep 2024 17:36:41 + with message-id and subject line Bug#1078293: fixed in lxqt-config 1.4.0-2 has caused the Debian Bug report #1078293, regarding lxqt-config: FTBFS: Could not find a package configuration file provided by "Qt5LinguistTools" to be marked as done.

Bug#1079588: marked as done (mandos-client postrm purge can mysteriously fail)

Your message dated Thu, 12 Sep 2024 17:36:52 + with message-id and subject line Bug#1079588: fixed in mandos 1.8.17-1 has caused the Debian Bug report #1079588, regarding mandos-client postrm purge can mysteriously fail to be marked as done. This means that you claim that the problem has been

Processed: [bts-link] source package src:gnupg2

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:gnupg2 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Sett

Bug#1078292: marked as done (lxqt-archiver: FTBFS: Could not find a package configuration file provided by "Qt5LinguistTools")

Your message dated Thu, 12 Sep 2024 17:21:15 + with message-id and subject line Bug#1078292: fixed in lxqt-archiver 0.9.1-1 has caused the Debian Bug report #1078292, regarding lxqt-archiver: FTBFS: Could not find a package configuration file provided by "Qt5LinguistTools" to be marked as don

Processed: reassign 1081533 to libcurl3t64-gnutls, forcibly merging 1081517 1081533, affects 1081533

Processing commands for cont...@bugs.debian.org: > reassign 1081533 libcurl3t64-gnutls 8.10.0-1 Bug #1081533 [curl] arm64: symbol lookup error: undefined symbol: gnutls_free Bug reassigned from package 'curl' to 'libcurl3t64-gnutls'. Ignoring request to alter found versions of bug #1081533 to the

Processed (with 1 error): forcibly merging 1081517 1081533, affects 1081533

Processing commands for cont...@bugs.debian.org: > forcemerge 1081517 1081533 Bug #1081517 [libcurl3t64-gnutls] libcurl-gnutls.so.4 no longer linked with needed libraries Bug #1081514 [libcurl3t64-gnutls] libcurl-gnutls.so.4: undefined symbol: gnutls_free Unable to merge bugs because: package of

Bug#1081517: libcurl-gnutls.so.4 no longer linked with needed libraries

On Thu, 12 Sep 2024 at 17:48:57 +0100, Simon McVittie wrote: > As a future improvement, it might be worthwhile to restructure the GNUTLS > patch so that it works more like this (pseudo-diff, hopefully you will > see what I mean): > > > diff... > ---... > +++... > libcurl_la_CPPFLAGS = $(

Bug#1081517: libcurl-gnutls.so.4 no longer linked with needed libraries

Control: tags -1 + patch On Thu, 12 Sep 2024 at 10:20:59 -0300, Carlos Henrique Lima Melara wrote: > > E ImportError: /lib/i386-linux-gnu/libcurl-gnutls.so.4: undefined symbol: > > gnutls_free > > We are aware of the issue and will try to solve by > the end of the week - or as soon as we have

Processed: Re: Bug#1081517: libcurl-gnutls.so.4 no longer linked with needed libraries

Processing control commands: > tags -1 + patch Bug #1081517 [libcurl3t64-gnutls] libcurl-gnutls.so.4 no longer linked with needed libraries Bug #1081514 [libcurl3t64-gnutls] libcurl-gnutls.so.4: undefined symbol: gnutls_free Added tag(s) patch. Added tag(s) patch. -- 1081514: https://bugs.debi

Bug#1081549: twine: Depends: python3-pkginfo (< 1.11.0~) but 1.11.1-1 is to be installed

Package: twine Version: 5.1.1-1 Severity: serious The following packages have unmet dependencies: twine : Depends: python3-pkginfo (< 1.11.0~) but 1.11.1-1 is to be installed

Bug#1076378: marked as done (node-xterm: Unable to build package node-xterm from sources in Debian Bookworm because of error TS2769)

Your message dated Thu, 12 Sep 2024 16:32:09 + with message-id and subject line Bug#1076378: fixed in node-xterm 3.8.1+~cs0.9.0-1+deb12u1 has caused the Debian Bug report #1076378, regarding node-xterm: Unable to build package node-xterm from sources in Debian Bookworm because of error TS2769

Bug#1080489: marked as done (Reports causing unbounded filesystem usage growth)

Your message dated Thu, 12 Sep 2024 16:32:09 + with message-id and subject line Bug#1080489: fixed in puppetserver 7.9.5-2+deb12u1 has caused the Debian Bug report #1080489, regarding Reports causing unbounded filesystem usage growth to be marked as done. This means that you claim that the pr

Bug#1078911: marked as done (missing reports cleanup job)

Your message dated Thu, 12 Sep 2024 16:32:09 + with message-id and subject line Bug#1078911: fixed in puppetserver 7.9.5-2+deb12u1 has caused the Debian Bug report #1078911, regarding missing reports cleanup job to be marked as done. This means that you claim that the problem has been dealt w

Bug#1077865: marked as done (rust-impl-trait-for-tuples: autopkgtest regression: thread 'fail' panicked at /usr/share/cargo/registry/trybuild-1.0.91/src/run.rs:101:13:)

Your message dated Thu, 12 Sep 2024 16:21:58 + with message-id and subject line Bug#1077865: fixed in rust-impl-trait-for-tuples 0.2.2-2 has caused the Debian Bug report #1077865, regarding rust-impl-trait-for-tuples: autopkgtest regression: thread 'fail' panicked at /usr/share/cargo/registry

Processed: Re: gnome-shell-extension-pomodoro: needs update for GNOME Shell 47

Processing control commands: > severity -1 serious Bug #1079259 [gnome-shell-pomodoro] gnome-shell-extension-pomodoro: needs update for GNOME Shell 47 Severity set to 'serious' from 'wishlist' -- 1079259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079259 Debian Bug Tracking System Conta

Processed: affects 1081517

Processing commands for cont...@bugs.debian.org: > affects 1081517 + git epiphany-browser blender Bug #1081517 [libcurl3t64-gnutls] libcurl-gnutls.so.4 no longer linked with needed libraries Bug #1081514 [libcurl3t64-gnutls] libcurl-gnutls.so.4: undefined symbol: gnutls_free Added indication tha

Processed: affects 1081517

Processing commands for cont...@bugs.debian.org: > affects 1081517 + src:mutter Bug #1081517 [libcurl3t64-gnutls] libcurl-gnutls.so.4 no longer linked with needed libraries Bug #1081514 [libcurl3t64-gnutls] libcurl-gnutls.so.4: undefined symbol: gnutls_free Added indication that 1081517 affects

Bug#1081543: FTBFS with PostgreSQL RC releases

Source: python-psycopg2cffi Version: 2.8.1-2 Severity: serious Tags: ftbfs Justification: FTBFS This package failed build from source in a rebuild. The rebuild was for Python 3.13, but the failure is unrelated to that. Log snippet: debian/rules override_dh_auto_install make[1]: Entering dire

Bug#1078408: marked as done (autofs: FTBFS: cyrus-sasl.c:112:25: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int, const char **, unsigned int *)’ [-Wincom

Your message dated Thu, 12 Sep 2024 15:08:11 + with message-id and subject line Bug#1078408: fixed in autofs 5.1.9-1.2 has caused the Debian Bug report #1078408, regarding autofs: FTBFS: cyrus-sasl.c:112:25: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void

Bug#1081514: libcurl-gnutls.so.4: undefined symbol: gnutls_free

I observed that more packages are affected by this bug. Here I list some of them on loong64 architecture: run "git clone xxx", I got: /usr/lib/git-core/git-remote-https: symbol lookup error: /lib/loongarch64-linux-gnu/libcurl-gnutls.so.4: undefined symbol: gnutls_free run "epiphany-browser", I go

Bug#1081539: FTBFS with Python 3.12.6

Source: python-pyeclib Version: 1.6.1-2 Severity: serious Tags: ftbfs Justification: FTBFS This package failed build from source during a rebuild. Interestingly, this was a build with Python 3.13 available, and the 3.13 part passed tests, but 3.12.6 triggered a test failure. I can reproduce this i

Bug#1079572: libfabric ftbfs on i386

On Sat, 24 Aug 2024 21:05:54 +0200 Matthias Klose wrote: Package: src:libfabric Version: 1.17.0-3 Severity: serious Tags: sid trixie libfabric ftbfs at least on i386, there might be more follow-up errors: [...] prov/hook/src/hook_domain.c:124:54: error: passing argument 2 of ‘domain->base_o

Bug#1018475: marked as done (python-csa: build-depends on python3-nose or uses it for autopkgtest)

Your message dated Thu, 12 Sep 2024 14:50:28 + with message-id and subject line Bug#1018475: fixed in python-csa 0.1.12-1.2 has caused the Debian Bug report #1018475, regarding python-csa: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This means that you claim

Bug#1081537: fuse transitional package is required for upgrades

Patch attached. Thank you, Jeremy Bícha From 87c8fda73670e158da7fd797cfbf2a35cbcc0d94 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jeremy=20B=C3=ADcha?= Date: Thu, 12 Sep 2024 10:37:58 -0400 Subject: [PATCH] Add fuse transitional package to upgrade to fuse3 Closes: #918984 Closes: #927291 Closes: #1

Bug#1081537: fuse transitional package is required for upgrades

Source: fuse3 Version: 3.14.0-7 Severity: serious Control: affects -1 src:fuse Tags: patch X-Debbugs-CC: j...@debian.org fuse 2.9.9-9 stopped building the fuse binary package. The fuse3 binary package has Provides, Conflicts, Breaks: fuse. This is insufficient for apt to be able to perform the upg

Bug#1081357: oz: Needs explicit Depends on libvirt-daemon-driver-qemu

Thanks for caring about this package - feel free to NMU and push changes to salsa! I think it would be better if this package was team maintained. I no longer use it, and upstream broke the self tests with some changes in the last release and wasn’t responsive in fixing them, so the state of th

Processed: fuse transitional package is required for upgrades

Processing control commands: > affects -1 src:fuse Bug #1081537 [src:fuse3] fuse transitional package is required for upgrades Added indication that 1081537 affects src:fuse -- 1081537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081537 Debian Bug Tracking System Contact ow...@bugs.debian

Bug#1081357: oz: Needs explicit Depends on libvirt-daemon-driver-qemu

Am 12.09.24 um 16:23 schrieb Michael Biebl: Helmut mentioned on IRC that it's probably also a good idea to add a versioned Breaks against oz to libvirt-daemon. We further discussed this on IRC. Since it only seems to affect the autopkgtest, a versioned Breaks is probably not necessary or

Processed: Re: oz: Needs explicit Depends on libvirt-daemon-driver-qemu

Processing control commands: > severity -1 serious Bug #1081357 [src:oz] oz: Needs explicit Depends on libvirt-daemon-driver-qemu Severity set to 'serious' from 'normal' -- 1081357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081357 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1081514: libcurl-gnutls.so.4: undefined symbol: gnutls_free

On Thursday, 12 September 2024 22:51:39 AEST Simon McVittie wrote: > Looks like a duplicate of which is a > regression in libcurl3t64-gnutls. libcurl4t64 (curl with OpenSSL) looks OK > according to packages.debian.org. Yes the same issue. Thanks for the quick res

Processed: affects 1081514

Processing commands for cont...@bugs.debian.org: > affects 1081514 src:python-pyproj src:postgis Bug #1081514 [libcurl3t64-gnutls] libcurl-gnutls.so.4: undefined symbol: gnutls_free Bug #1081517 [libcurl3t64-gnutls] libcurl-gnutls.so.4 no longer linked with needed libraries Added indication that

Bug#1081517: libcurl-gnutls.so.4 no longer linked with needed libraries

Hi, On Thu, Sep 12, 2024 at 02:03:42PM GMT, Adrian Bunk wrote: > Package: libcurl3t64-gnutls > Version: 8.10.0-1 > Severity: grave > Tags: ftbfs > Control: affects -1 src:python-memray > > https://buildd.debian.org/status/fetch.php?pkg=python-memray&arch=i386&ver=1.14.0%2Bdfsg-1&stamp=1726096433&

Processed: tagging 1081517

Processing commands for cont...@bugs.debian.org: > tags 1081517 - moreinfo Bug #1081517 [libcurl3t64-gnutls] libcurl-gnutls.so.4 no longer linked with needed libraries Bug #1081514 [libcurl3t64-gnutls] libcurl-gnutls.so.4: undefined symbol: gnutls_free Removed tag(s) moreinfo. Removed tag(s) mor

Bug#1081532: autoconf2.13: Keep out of trixie

Source: autoconf2.13 Severity: serious Version: 2.13-69 With the last reverse dependency xemacs21 not being in trixie, this package can leave as well. If xemacs21 can otherwise enter trixie again and has not migrated to a newer autoconf, please just close this bug to let it migrate.

Processed: affects 1081517

Processing commands for cont...@bugs.debian.org: > affects 1081517 + flatpak Bug #1081517 [libcurl3t64-gnutls] libcurl-gnutls.so.4 no longer linked with needed libraries Bug #1081514 [libcurl3t64-gnutls] libcurl-gnutls.so.4: undefined symbol: gnutls_free Added indication that 1081517 affects fla

Processed: Re: Bug#1081514: libcurl-gnutls.so.4: undefined symbol: gnutls_free

Processing control commands: > reassign -1 libcurl3t64-gnutls 8.10.0-1 Bug #1081514 [flatpak] libcurl-gnutls.so.4: undefined symbol: gnutls_free Bug reassigned from package 'flatpak' to 'libcurl3t64-gnutls'. No longer marked as found in versions flatpak/1.15.10-1. Ignoring request to alter fixed v

  1   2   >