Bug#1042042: android-platform-build: FTBFS: Vector.h:259:28: error: cannot convert ‘const android::Vector*’ to ‘android::VectorImpl*’

2024-03-07 Thread Vladimir Petko
Package: android-platform-build Followup-For: Bug #1042042 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch Control: tags -1 patch Dear Maintainer, The attached patch resolves the above ftbfs by adding patches for BouncyCastle and libziparchive-dev API changes. In

Processed: Re: android-platform-build: FTBFS: Vector.h:259:28: error: cannot convert ‘const android::Vector*’ to ‘android::VectorImpl*’

2024-03-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1042042 [src:android-platform-build] android-platform-build: FTBFS: Vector.h:259:28: error: cannot convert ‘const android::Vector*’ to ‘android::VectorImpl*’ Added tag(s) patch. -- 1042042:

Processed: found 1064967 in 1:20170731~dfsg-1, found 1064967 in 1:20230101~dfsg-1 ...

2024-03-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1064967 1:20170731~dfsg-1 Bug #1064967 [src:fontforge] fontforge: CVE-2024-25081 CVE-2024-25082 Marked as found in versions fontforge/1:20170731~dfsg-1. > found 1064967 1:20230101~dfsg-1 Bug #1064967 [src:fontforge] fontforge:

Processed: libcypher-parser: diff for NMU version 0.6.2-0.1

2024-03-07 Thread Debian Bug Tracking System
Processing control commands: > tags 1012975 + patch Bug #1012975 [src:libcypher-parser] libcypher-parser: ftbfs with GCC-12 Added tag(s) patch. > tags 1012975 + pending Bug #1012975 [src:libcypher-parser] libcypher-parser: ftbfs with GCC-12 Added tag(s) pending. -- 1012975:

Bug#1064252: closed by Salvatore Bonaccorso (Re: Bug#1064252: linux-image-6.1.0-17-amd64: CONFIG_SYSTEM_TRUSTED_KEYS="y" is in the default config "y")

2024-03-07 Thread TomK
Since .config lists the response to this as "y" WITH THE DOUBLE QUOTES, IT is not possible to change it in menuconfig, and the quotes break the compile. So, the stock linux-image-6.5-amd64 config file in /boot, if copied to .config into the source directory, it's booby trapped with a config

Processed: fontforge: diff for NMU version 1:20230101~dfsg-1.1

2024-03-07 Thread Debian Bug Tracking System
Processing control commands: > tags 1064967 + patch Bug #1064967 [src:fontforge] fontforge: CVE-2024-25081 CVE-2024-25082 Added tag(s) patch. > tags 1064967 + pending Bug #1064967 [src:fontforge] fontforge: CVE-2024-25081 CVE-2024-25082 Added tag(s) pending. -- 1064967:

Bug#1064967: fontforge: diff for NMU version 1:20230101~dfsg-1.1

2024-03-07 Thread Adrian Bunk
Control: tags 1064967 + patch Control: tags 1064967 + pending Dear maintainer, I've prepared an NMU for fontforge (versioned as 1:20230101~dfsg-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. @Security team: If wanted, I could afterwards also prepare (pu or

Bug#1061731: fwupd: Failed to load daemon: failed to load engine: Failed to load config: Key file does not have group “redfish”

2024-03-07 Thread Richard B
Hello. I can confirm that upgrading fwupd and libfwupd2 on Trixie to 1.9.14-1 and installing the package maintainer's version of /etc/fwupd/fwupd.conf allowed the fwupd status to start: sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state

Bug#1064676: additional information

2024-03-07 Thread Vladimir Petko
Dear Maintainers, Would it be possible to consider a merge request[1] that addresses this issue? Best Regards, Vladimir. [1] https://salsa.debian.org/android-tools-team/android-platform-tools-apksig/-/merge_requests/6

Bug#1064763: possible fix

2024-03-07 Thread Daniel Kondor
Hi, I've looked into this, and I believe that the attached two patches should fix this. However, I cannot test this on Debian -- I'm on Ubuntu 22.04 where cairo-dock-plug-ins builds and installs well with or without the patches. It would be great to know if these really fix the problem, so

Processed: Re: Bug#1065320: linux-image-6.1.0-18-amd64: 6.1.0-18 kernel enters ACPI Error loop during boot & requires power cycle

2024-03-07 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1065320 [src:linux] linux-image-6.1.0-18-amd64: 6.1.0-18 kernel enters ACPI Error loop during boot & requires power cycle Severity set to 'serious' from 'critical' > tags -1 + upstream fixed-upstream Bug #1065320 [src:linux]

Bug#1065320: linux-image-6.1.0-18-amd64: 6.1.0-18 kernel enters ACPI Error loop during boot & requires power cycle

2024-03-07 Thread Salvatore Bonaccorso
Control: severity -1 serious Control: tags -1 + upstream fixed-upstream Control: forwarded -1 https://lore.kernel.org/regressions/zd2bsv8vsfjml...@archie.me/ https://bugzilla.kernel.org/show_bug.cgi?id=218531 Control: found -1 6.6.15-1 Control: found -1 6.7.4-1~exp1 Hi Lee, On Sat, Mar 02,

Bug#1064252: marked as done (linux-image-6.1.0-17-amd64: CONFIG_SYSTEM_TRUSTED_KEYS="y" is in the default config "y")

2024-03-07 Thread Debian Bug Tracking System
Your message dated Thu, 7 Mar 2024 22:02:05 +0100 with message-id and subject line Re: Bug#1064252: linux-image-6.1.0-17-amd64: CONFIG_SYSTEM_TRUSTED_KEYS="y" is in the default config "y" has caused the Debian Bug report #1064252, regarding linux-image-6.1.0-17-amd64:

Bug#1061754: marked as done (python-json-log-formatter ftbfs with Python 3.12 as default)

2024-03-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Mar 2024 20:52:51 + with message-id and subject line Bug#1061754: fixed in python-json-log-formatter 0.5.2-3 has caused the Debian Bug report #1061754, regarding python-json-log-formatter ftbfs with Python 3.12 as default to be marked as done. This means that you

Processed: android-platform-tools-base: additional information

2024-03-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1058331 [src:android-platform-tools-base] android-platform-tools-base: FTBFS: SignatureExtension.java:32: error: DEROutputStream is not public in org.bouncycastle.asn1; cannot be accessed from outside package Added tag(s) patch. -- 1058331:

Bug#1058331: android-platform-tools-base: additional information

2024-03-07 Thread Vladimir Petko
Package: android-platform-tools-base Followup-For: Bug #1058331 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch Control: tags -1 patch Dear Maintainer, I apologise for submitting it as a debdiff, salsa repository appears to be out of date. The attached patch

Bug#999908: marked as done (python3-celery-haystack-ng: missing Breaks+Replaces: python3-django-celery-haystack (<< 0.20))

2024-03-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Mar 2024 20:40:38 + with message-id and subject line Bug#08: fixed in celery-haystack-ng 0.20.post2-2 has caused the Debian Bug report #08, regarding python3-celery-haystack-ng: missing Breaks+Replaces: python3-django-celery-haystack (<< 0.20) to be marked

Bug#1061754: python-json-log-formatter ftbfs with Python 3.12 as default

2024-03-07 Thread Colin Watson
On Tue, Mar 05, 2024 at 06:15:32PM +, Colin Watson wrote: > While it looks like this was fixed upstream in > https://github.com/marselester/json-log-formatter/commit/74f04ee4f6aa8e461fcb2d688459888b7279fc73 > and I guess we could cherry-pick that, I also can't reproduce this > failure in

Bug#1061618: src:haskell-misfortune: unsatisfied build dependency in testing: libghc-regex-pcre-doc

2024-03-07 Thread Peter Green
On 07/03/2024 19:43, Peter Green wrote: In raspbian, I removed the reference from misfortune.cabel, removed the build-dependencies on libghc-regex-pcre* and also (for unrelated reasons) removed the build-dependency on ghc-doc. After doing so I was able to successfully build the package. Scratch

Bug#1061618: src:haskell-misfortune: unsatisfied build dependency in testing: libghc-regex-pcre-doc

2024-03-07 Thread Peter Green
Can you please investigate the situation and figure out how to resolve it? I'm no haskell expert, but to me the dependency looks vestigal. Grepping the source tree for "pcre" finds a mention in the misfortune.cabal file but no mentions in the actual code, and there are no corresponding binary

Bug#1064420: marked as done (src:ruby-omniauth-alicloud: fails to migrate to testing for too long: uploader built arch:all binary)

2024-03-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Mar 2024 19:08:46 + with message-id and subject line Bug#1064420: fixed in ruby-omniauth-alicloud 3.0.0-2.1 has caused the Debian Bug report #1064420, regarding src:ruby-omniauth-alicloud: fails to migrate to testing for too long: uploader built arch:all binary to

Processed: closing 1051967

2024-03-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # php-psr-log-test was removed via #1052296 > close 1051967 Bug #1051967 [php-fig-log-test] php-fig-log-test: ships /usr/share/php/Psr/Log/Test/*.php, already in php-psr-log-test Marked Bug as done > thanks Stopping processing here. Please

Processed: Re: Bug#1065501: qgis FTBFS: FAILED: src/crssync/CMakeFiles/synccrsdb

2024-03-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 upstream Bug #1065501 [src:qgis] qgis FTBFS: FAILED: src/crssync/CMakeFiles/synccrsdb Added tag(s) upstream. > forwarded -1 https://github.com/qgis/QGIS/issues/56756 Bug #1065501 [src:qgis] qgis FTBFS: FAILED: src/crssync/CMakeFiles/synccrsdb Set Bug

Bug#1065501: qgis FTBFS: FAILED: src/crssync/CMakeFiles/synccrsdb

2024-03-07 Thread Sebastiaan Couwenberg
Control: tags -1 upstream Control: forwarded -1 https://github.com/qgis/QGIS/issues/56756 From the build log: Operation needs translation in QgsCoordinateReferenceSystemUtils::translateProjection: mod_krovak This is actually caused by PROJ 9.4.0 which introduced support for the Modified

Bug#1065634: wv: /usr/share/doc wv is a dangling symlink

2024-03-07 Thread Sven Joachim
Control: tags -1 + patch On 2024-03-07 18:49 +0100, Sven Joachim wrote: > Package: wv > Version: 1.2.9-6.1 > Severity: serious > X-Debbugs-Cc: Sven Joachim , Steve Langasek > > > After renaming the libwv-1.2-4 library package to libwv-1.2-4t64, the > /usr/share/doc/wv symlink has become

Processed: Re: Bug#1065634: wv: /usr/share/doc wv is a dangling symlink

2024-03-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1065634 [wv] wv: /usr/share/doc wv is a dangling symlink Added tag(s) patch. -- 1065634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1064422: marked as done (src:ohai: fails to migrate to testing for too long: uploader built arch:all binary)

2024-03-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Mar 2024 18:52:52 + with message-id and subject line Bug#1064422: fixed in ohai 18.1.3-2.1 has caused the Debian Bug report #1064422, regarding src:ohai: fails to migrate to testing for too long: uploader built arch:all binary to be marked as done. This means that

Bug#1065167: google-perftools: FTBFS on armhf/armel: static_assert(sizeof(int32_t) == sizeof(off_t), "")

2024-03-07 Thread Aliaksey Kandratsenka
Hi again. So last time I failed to check _TIME_BITS=64. I only tested _FILE_OFFSET_BITS. And 32-bit arm bits continue failing. https://buildd.debian.org/status/fetch.php?pkg=google-perftools=armel=2.15-2=1709539473=log Please also cherry-pick

Processed: Re: Bug#1065548: marked as pending in octave-statistics

2024-03-07 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1065548 [src:octave-statistics] octave-statistics: binary-any FTBFS Bug 1065548 is not marked as done; doing nothing. -- 1065548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065548 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: Re: Bug#1065548: marked as pending in octave-statistics

2024-03-07 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1065548 {Done: Rafael Laboissière } [src:octave-statistics] octave-statistics: binary-any FTBFS 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened

Bug#1065548: marked as pending in octave-statistics

2024-03-07 Thread Sébastien Villemot
Control: reopen -1 Le mercredi 06 mars 2024 à 17:25 +, Rafael Laboissière a écrit : > Control: tag -1 pending > > Hello, > > Bug #1065548 in octave-statistics 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

Bug#1065634: wv: /usr/share/doc wv is a dangling symlink

2024-03-07 Thread Sven Joachim
Package: wv Version: 1.2.9-6.1 Severity: serious X-Debbugs-Cc: Sven Joachim , Steve Langasek After renaming the libwv-1.2-4 library package to libwv-1.2-4t64, the /usr/share/doc/wv symlink has become dangling. , | $ file /usr/share/doc/wv | /usr/share/doc/wv: broken symbolic link to

Bug#1065626: libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common

2024-03-07 Thread Vincent Lefevre
On 2024-03-07 17:15:05 +, Simon McVittie wrote: > I can confirm that version 2.24.33-4 of libgtk2.0-common, libgtk2.0-0t64 > and libgtk2.0-bin are, in fact, installable (I have them installed > right now). I can't see any dependency relationships between them that > look suspicious. > > If

Bug#1053169: marked as done (Please remove librbd-dev build-depends on all 32 bits arch)

2024-03-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Mar 2024 17:30:37 + with message-id and subject line Bug#1053169: fixed in tcmu 1.5.4-6 has caused the Debian Bug report #1053169, regarding Please remove librbd-dev build-depends on all 32 bits arch to be marked as done. This means that you claim that the problem

Processed: Re: Bug#1065626: libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common

2024-03-07 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 aptitude,libgtk2.0-0t64 Bug #1065626 [libgtk2.0-0t64] libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common Bug reassigned from package 'libgtk2.0-0t64' to 'aptitude,libgtk2.0-0t64'. No longer

Bug#1065626: libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common

2024-03-07 Thread Simon McVittie
Control: reassign -1 aptitude,libgtk2.0-0t64 Control: tags -1 + moreinfo On Thu, 07 Mar 2024 at 16:10:17 +0100, Vincent Lefevre wrote: > During an upgrade with aptitude: > > dpkg: dependency problems prevent removal of libgtk2.0-common: > libgtk2.0-bin depends on libgtk2.0-common. >

Processed: tagging 1064722

2024-03-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1064722 + confirmed Bug #1064722 [src:erlang-p1-xml] erlang-p1-xml: FTBFS: dh_auto_test: error: make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile test returned exit code 2 Added tag(s) confirmed. > thanks Stopping

Bug#1065625: libmtp9t64 / libmtp-runtime dependency problem makes dpkg fail with attempt of removal of libmtp-common

2024-03-07 Thread Vincent Lefevre
On 2024-03-07 16:00:35 +0100, Vincent Lefevre wrote: > Will install 11 packages, and remove 3 packages. > 8192 B of disk space will be used > > [...] > [HOLD, DEPENDENCIES] libmtp-common:amd64 1.1.21-3 > [...] > [INSTALL, DEPENDENCIES] libgphoto2-6t64:amd64

Bug#1065626: libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common

2024-03-07 Thread Vincent Lefevre
Package: libgtk2.0-0t64 Version: 2.24.33-4 Severity: serious During an upgrade with aptitude: dpkg: dependency problems prevent removal of libgtk2.0-common: libgtk2.0-bin depends on libgtk2.0-common. libgtk2.0-0t64:amd64 depends on libgtk2.0-common. dpkg: error processing package

Bug#1065625: libmtp9t64 / libmtp-runtime dependency problem makes dpkg fail with attempt of removal of libmtp-common

2024-03-07 Thread Vincent Lefevre
Package: libmtp9t64 Version: 1.1.21-3.1 Severity: serious During an upgrade with aptitude: dpkg: dependency problems prevent removal of libmtp-common: libmtp9t64:amd64 depends on libmtp-common. libmtp-runtime depends on libmtp-common. dpkg: error processing package libmtp-common (--purge):

Bug#1065613: gjs: Fails to build on ppc64el

2024-03-07 Thread Jeremy Bícha
Source: gjs Version: 1.79.90-1 Severity: serious Tags: ftbfs sid Forwarded: https://gitlab.gnome.org/GNOME/gjs/-/issues/605 The new version of gjs is failing to build on ppc64 and ppc64el. I have reported this issue upstream. Thank you, Jeremy Bícha

Processed: found 1065585 in 6.6.3-1~exp1

2024-03-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1065585 6.6.3-1~exp1 Bug #1065585 [src:linux] linux-headers-6.7.7-amd64: Depends: linux-compiler-gcc-13-x86 -> linux-image-6.7.7-amd64, gcc-13 => uninstallable on x32 Marked as found in versions linux/6.6.3-1~exp1. > thanks Stopping

Processed: fix 1065610 tags

2024-03-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1065610 1:1.52.0-2.1 Bug #1065610 [libguestfs0t64] libguestfs0t64: All appliance dependencies lost during time_t transition Marked as found in versions libguestfs/1:1.52.0-2.1. > notfound 1065610 1.52.0-2.1 Bug #1065610 [libguestfs0t64]

Bug#1065610: libguestfs0t64: All appliance dependencies lost during time_t transition

2024-03-07 Thread James Cowgill
Package: libguestfs0t64 Version: 1.52.0-2.1 Severity: serious Hi, During the time_t transition all the appliance dependencies of libguestfs0 were lost: $ debdiff libguestfs0_1%3a1.52.0-2+b1_amd64.deb libguestfs0t64_1%3a1.52.0-2.1_amd64.deb ... Control files: lines which differ (wdiff format)

Processed: Re: libdebuginfod1t64 dependency problem breaks the upgrade

2024-03-07 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 libdebuginfod1t64 dependency problem makes dpkg fail with attempt > of removal of libdebuginfod-common Bug #1065603 [libdebuginfod1t64] libdebuginfod1t64 dependency problem breaks the upgrade Changed Bug title to 'libdebuginfod1t64 dependency problem

Bug#1065603: libdebuginfod1t64 dependency problem breaks the upgrade

2024-03-07 Thread Vincent Lefevre
Control: retitle -1 libdebuginfod1t64 dependency problem makes dpkg fail with attempt of removal of libdebuginfod-common On 2024-03-07 11:28:21 +0100, Vincent Lefevre wrote: > When I wanted to upgrade, this ended up with > > dpkg: dependency problems prevent removal of libdebuginfod-common: >

Bug#1064886: sqlite-utils: Fails with "ModuleNotFoundError"

2024-03-07 Thread Edward Betts
Hi Sebastian, The click_default_group module is in the python3-click-default-group package, sqlite-utils depends on python3-click-default-group. Do you have python3-click-default-group installed? The module will be installed as /usr/lib/python3/dist-packages/click_default_group.py Do you have

Bug#1065603: libdebuginfod1t64 dependency problem breaks the upgrade

2024-03-07 Thread Vincent Lefevre
Package: libdebuginfod1t64 Version: 0.190-1.1 Severity: serious When I wanted to upgrade, this ended up with dpkg: dependency problems prevent removal of libdebuginfod-common: libdebuginfod1t64:amd64 depends on libdebuginfod-common (>= 0.190-1.1). dpkg: error processing package

Bug#1065599: gcc-14-offload-nvptx: openmp offload compile fails due to missing libgomp.spec

2024-03-07 Thread Giacomo Mulas
Package: gcc-14-offload-nvptx Version: 14-20240303-1 Severity: grave Justification: renders package unusable Dear Maintainer, due to a different organisation in file installation with respect to gcc-12-offload-nvptx, compiling code to offload openmp to nvptx fails with the following:

Bug#1065598: gcc-13-offload-nvptx: openmp offload compile fails due to missing libgomp.spec

2024-03-07 Thread Giacomo Mulas
Package: gcc-13-offload-nvptx Version: 13.2.0-18 Severity: grave Justification: renders package unusable Dear Maintainer, due to a different organisation in file installation with respect to gcc-12-offload-nvptx, compiling code to offload openmp to nvptx fails with the following:

Bug#1063484: libuv1: CVE-2024-24806

2024-03-07 Thread Dominique Dumont
On Wednesday, 6 March 2024 21:07:56 CET Salvatore Bonaccorso wrote: > Thank you very much. Looks good to me, feel free to upload as well to > security-master (and build as well with -sa). Done. All the best