Bug#1070020: marked as done (autopkgtest: (unrelated) packages not found)

2024-05-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 May 2024 08:02:34 +0200 with message-id <171566655467.5069.3895332051438530915@localhost> and subject line Re: Bug#1070020: autopkgtest: (unrelated) packages not found has caused the Debian Bug report #1070020, regarding autopkgtest: (unrelated) packages not found to be m

Bug#1070919: compyle: FTBFS in bullseye

2024-05-13 Thread Antonio Valentino
Dear Santiago, On Sat, 11 May 2024 21:46:59 +0200 Santiago Vila wrote: Package: src:compyle Version: 0.7-2 Severity: serious Control: close -1 0.8.1-4 Tags: ftbfs bullseye Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: ---

Bug#1070994: marked as done (src:praat: fails to migrate to testing for too long: FTBFS on arm64, armel, armhf, ppc64el and riscv64)

2024-05-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 May 2024 02:35:16 + with message-id and subject line Bug#1070994: fixed in praat 6.4.12+dfsg-3 has caused the Debian Bug report #1070994, regarding src:praat: fails to migrate to testing for too long: FTBFS on arm64, armel, armhf, ppc64el and riscv64 to be marked as

Bug#1070994: marked as pending in praat

2024-05-13 Thread Rafael Laboissière
Control: tag -1 pending Hello, Bug #1070994 in praat 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: https://salsa.debian.org/med-team/praat/-/commit/4bc9983356bccecef97c445d8357b1be533

Processed: Bug#1070994 marked as pending in praat

2024-05-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1070994 [src:praat] src:praat: fails to migrate to testing for too long: FTBFS on arm64, armel, armhf, ppc64el and riscv64 Added tag(s) pending. -- 1070994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070994 Debian Bug Tracking System Co

Processed: user debian...@lists.debian.org, usertagging 1025090, usertagging 1060321, affects 1060321 ...

2024-05-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 1025090 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 1060321 piuparts There were no usertags set. Usertags

Processed: Bug#1071035 marked as pending in golang-github-fatih-semgroup

2024-05-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1071035 [golang-golang-x-sync] FAIL: TestGroup_deadlock Added tag(s) pending. -- 1071035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071035 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1071035: marked as pending in golang-github-fatih-semgroup

2024-05-13 Thread Reinhard Tartler
Control: tag -1 pending Hello, Bug #1071035 in golang-github-fatih-semgroup 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: https://salsa.debian.org/go-team/packages/golang-github-fati

Bug#1071083: thawab: depends on no longer available gir1.2-webkit2-4.0

2024-05-13 Thread Andreas Beckmann
Package: thawab Version: 4.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: The following packages have unmet dependencies: thawab : Depends: gir1.2-webkit2-4.0 but it is not ins

Bug#1071082: FTBFS against jgit/6.7.0-1 in unstable

2024-05-13 Thread Pierre Gruet
Source: plm Version: 2.9.2-1 Severity: serious Tags: ftbfs patch Dear Maintainer, I have just uploaded jgit/6.7.0 to unstable, in order to fix a security issue. However, plm fails to build against it because some -- previously -- deprecated methods have been removed. The enclosed patch will allo

Bug#1071081: phpunit-environment/experimental FTBFS: Error: Call to undefined method SebastianBergmann\Environment\Runtime::getRawBinary()

2024-05-13 Thread Adrian Bunk
Source: phpunit-environment Version: 7.1.0-1 Severity: serious Tags: ftbfs Forwarded: https://github.com/sebastianbergmann/environment/commit/ff8e9b0dc10315e13f3a7951eec6b227e66997e7 https://buildd.debian.org/status/fetch.php?pkg=phpunit-environment&arch=all&ver=7.1.0-1&stamp=1715633007&raw=0 ..

Bug#1063004: synfig: NMU diff for 64-bit time_t transition

2024-05-13 Thread Adrian Bunk
On Sat, Feb 24, 2024 at 12:41:14PM -0800, Steve Langasek wrote: > Control: tags -1 - pending > Control: severity -1 serious > > Unfortunately, it appears synfig ftbfs in unstable and experimental: > > [...] > checking for Magick++ >= 6.4.2... configure: error: *** Unable to find > Magick++ >

Bug#1071060: marked as done (pycrc: Must not ship /usr/lib/python3/dist-packages/__init__.py)

2024-05-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 May 2024 20:38:04 + with message-id and subject line Bug#1071060: fixed in pycrc 0.10.0-3 has caused the Debian Bug report #1071060, regarding pycrc: Must not ship /usr/lib/python3/dist-packages/__init__.py to be marked as done. This means that you claim that the pr

Processed: BTS housekeeping

2024-05-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1027339 ruby-rack Bug #1027339 [src:ruby-rackup] ruby-rackup: FTBFS: build-dependency not installable: ruby-rack (>= 3.0.0~) Bug reassigned from package 'src:ruby-rackup' to 'ruby-rack'. No longer marked as found in versions ruby-rackup/

Processed: unarchiving 1058130

2024-05-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 1058130 Bug #1058130 {Done: Ulises Vitulli } [src:python-nmea2] python-nmea2: FTBFS: ModuleNotFoundError: No module named 'imp' Unarchived Bug 1058130 > thanks Stopping processing here. Please contact me if you need assistance. -- 105

Bug#1063957: python-pytest-lazy-fixture: autopkgtest regression with pytest 8

2024-05-13 Thread Julian Gilbey
On Wed, Apr 03, 2024 at 03:58:21PM -0400, Jeremy Bícha wrote: > I noticed one package affected by this issue, prettytable, has > switched to a fork, pytest-lazy-fixtures (note the s at the end of the > name). > > Would someone like to package this for Debian to fix several packages > failing to bu

Bug#1071076: inotify-info: baseline ABI violation, builds with -march=native

2024-05-13 Thread Aurelien Jarno
Source: inotify-info Version: 0.0.1-1 Severity: serious Dear maintainer, inotify-info builds with -march=native, which means the instruction set it uses depends on the buildd that is used. For instance the i386 package uses AVX instructions. In addition -march=native is not supported on all archi

Bug#1069393: marked as done (luma.core: FTBFS on arm64: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)

2024-05-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 May 2024 19:49:33 + with message-id and subject line Bug#1069393: fixed in luma.core 2.4.2-1 has caused the Debian Bug report #1069393, regarding luma.core: FTBFS on arm64: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit co

Bug#1071075: python-easydev accesses the internet during the build

2024-05-13 Thread Adrian Bunk
Source: python-easydev Version: 0.13.2+dfsg1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=python-easydev&arch=all&ver=0.13.2%2Bdfsg1-1&stamp=1714380640&raw=0 ... === FAILURES ===

Bug#1070745: marked as done (libglib2.0-0: input regression for users of ibus affecting dead keys, Compose key and non-Latin input)

2024-05-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 May 2024 19:32:44 + with message-id and subject line Bug#1070745: fixed in glib2.0 2.66.8-1+deb11u3 has caused the Debian Bug report #1070745, regarding libglib2.0-0: input regression for users of ibus affecting dead keys, Compose key and non-Latin input to be marke

Bug#1070743: marked as done (libglib2.0-0: input regression for users of ibus affecting dead keys, Compose key and non-Latin input)

2024-05-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 May 2024 19:32:44 + with message-id and subject line Bug#1070743: fixed in glib2.0 2.66.8-1+deb11u3 has caused the Debian Bug report #1070743, regarding libglib2.0-0: input regression for users of ibus affecting dead keys, Compose key and non-Latin input to be marke

Processed (with 1 error): Re: Bug#1071059: mousepad: segfaults at each launch !

2024-05-13 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1071059 [mousepad] mousepad: segfaults at each launch ! Severity set to 'important' from 'grave' > tag - unreproducible moreinfo Unknown command or malformed arguments to command. -- 1071059: https://bugs.debian.org/cgi-bin/bugreport.cgi

Bug#1071059: mousepad: segfaults at each launch !

2024-05-13 Thread Yves-Alexis Perez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: severity -1 important control: tag - unreproducible moreinfo On Mon, 2024-05-13 at 18:28 +0200, Philippe Caillaud wrote: > Dear Maintainer, > > I use mousepad almost each day for small text editing ; since a few days > (maybe > 2 or 3), mo

Processed: tagging 1071037

2024-05-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1071037 + fixed-upstream upstream Bug #1071037 [v4l2loopback-dkms] v4l2loopback-dkms: module fails to build for i386: ERROR: modpost: "__moddi3" undefined! Added tag(s) upstream and fixed-upstream. > thanks Stopping processing here. Please

Processed: bug 1071037 is forwarded to https://github.com/umlaeute/v4l2loopback/issues/550

2024-05-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1071037 https://github.com/umlaeute/v4l2loopback/issues/550 Bug #1071037 [v4l2loopback-dkms] v4l2loopback-dkms: module fails to build for i386: ERROR: modpost: "__moddi3" undefined! Set Bug forwarded-to-address to 'https://github.com/u

Bug#1071070: src:nbd: fails to migrate to testing for too long: autopkgtest failure

2024-05-13 Thread Paul Gevers
Source: nbd Version: 1:3.25-1 Severity: serious Control: close -1 1:3.26.1-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

Processed: src:nbd: fails to migrate to testing for too long: autopkgtest failure

2024-05-13 Thread Debian Bug Tracking System
Processing control commands: > close -1 1:3.26.1-1 Bug #1071070 [src:nbd] src:nbd: fails to migrate to testing for too long: autopkgtest failure Marked as fixed in versions nbd/1:3.26.1-1. Bug #1071070 [src:nbd] src:nbd: fails to migrate to testing for too long: autopkgtest failure Marked Bug as

Bug#1069447: gpaw: FTBFS on armhf: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" --test-pytest "--test-args=-v -m ci" returned exit code 13

2024-05-13 Thread Paul Gevers
Control: tags -1 moreinfo Hi Lucas, [Please CC me on replies, I'm not subscribed to the bug] On Sat, 20 Apr 2024 15:09:56 +0200 Lucas Nussbaum wrote: During a rebuild of all packages in sid, your package failed to build on armhf. Do you have any idea why we don't see the same failure on re

Processed: Re: gpaw: FTBFS on armhf: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" --test-pytest "--test-args=-v -m ci" returned exit code 13

2024-05-13 Thread Debian Bug Tracking System
Processing control commands: > tags -1 moreinfo Bug #1069447 [src:gpaw] gpaw: FTBFS on armhf: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" --test-pytest "--test-args=-v -m ci" returned exit code 13 Added tag(s) moreinfo. -- 1069447: https://bugs.debian.or

Bug#1064003: Bug#1065416: [Cross-toolchain-base-devs] Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely

2024-05-13 Thread Bastian Blank
Hi On Sun, May 12, 2024 at 11:54:42PM +0200, Helmut Grohne wrote: > On Sun, May 12, 2024 at 07:35:09PM +0200, Bastian Blank wrote: > > > 1. API expectation of *-$arch-cross packages > > I asked exactly that in > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065416#55 > I guess the best desc

Processed: src:prettytable: fails to migrate to testing for too long: FTBFS

2024-05-13 Thread Debian Bug Tracking System
Processing control commands: > close -1 3.6.0-2 Bug #1071069 [src:prettytable] src:prettytable: fails to migrate to testing for too long: FTBFS The source 'prettytable' and version '3.6.0-2' do not appear to match any binary packages Marked as fixed in versions prettytable/3.6.0-2. Bug #1071069

Bug#1071069: src:prettytable: fails to migrate to testing for too long: FTBFS

2024-05-13 Thread Paul Gevers
Source: prettytable Version: 3.6.0-1 Severity: serious Control: close -1 3.6.0-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1066757 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unst

Bug#902452: marked as done (Kamailio TLS module in Debian Stretch is unusable)

2024-05-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 May 2024 20:08:51 +0200 with message-id <442922db-f829-4e18-b088-6788ef45b...@debian.org> and subject line Re: Kamailio TLS module in Debian Stretch is unusable has caused the Debian Bug report #902452, regarding Kamailio TLS module in Debian Stretch is unusable to be mar

Processed: Re: Bug#1070288: pplatex: depends on obsolete pcre3 library

2024-05-13 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/stefanhepp/pplatex/issues/26 Bug #1070288 [src:pplatex] pplatex: depends on obsolete pcre3 library Set Bug forwarded-to-address to 'https://github.com/stefanhepp/pplatex/issues/26'. -- 1070288: https://bugs.debian.org/cgi-bin/bugrep

Bug#1070288: pplatex: depends on obsolete pcre3 library

2024-05-13 Thread Sebastian Humenda
control: forwarded -1 https://github.com/stefanhepp/pplatex/issues/26 thanks signature.asc Description: PGP signature

Processed: src:sqlmodel: fails to migrate to testing for too long: FTBFS

2024-05-13 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.0.8-6 Bug #1071067 [src:sqlmodel] src:sqlmodel: fails to migrate to testing for too long: FTBFS The source 'sqlmodel' and version '0.0.8-6' do not appear to match any binary packages Marked as fixed in versions sqlmodel/0.0.8-6. Bug #1071067 [src:sqlmode

Bug#1071067: src:sqlmodel: fails to migrate to testing for too long: FTBFS

2024-05-13 Thread Paul Gevers
Source: sqlmodel Version: 0.0.8-5 Severity: serious Control: close -1 0.0.8-6 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1066771 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstabl

Bug#1066321: marked as done (openzwave: FTBFS: cc1plus: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ [-Werror])

2024-05-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 May 2024 20:03:39 +0200 with message-id <3a0bbb4b-b96d-45e3-ba14-76247bfa3...@debian.org> and subject line Re: openzwave: FTBFS: cc1plus: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ [-Werror] has caused the Debian Bug report #1

Bug#1071063: screenkey: malformed debian/changelog

2024-05-13 Thread Chris Lamb
Package: screenkey Version: 1:1.5-4 Severity: serious User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Hi, This might not *strictly* be an RC bug, but the latest upload of screenkey has the following entry in debian/ch

Processed: Re: Bug#1071007: sherlock has an undeclared file conflict on /usr/lib/python3/dist-packages/__init__.py

2024-05-13 Thread Debian Bug Tracking System
Processing control commands: > affects -1 - pycrc Bug #1071007 [sherlock] sherlock has an undeclared file conflict on /usr/lib/python3/dist-packages/__init__.py Removed indication that 1071007 affects pycrc > clone -1 -2 -3 Bug #1071007 [sherlock] sherlock has an undeclared file conflict on /usr

Bug#1071007: sherlock has an undeclared file conflict on /usr/lib/python3/dist-packages/__init__.py

2024-05-13 Thread Axel Beckert
Control: affects -1 - pycrc Control: clone -1 -2 -3 Control: reassign -2 pycrc 0.10.0-2 Control: retitle -1 sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py Control: retitle -2 pycrc: Must not ship /usr/lib/python3/dist-packages/__init__.py Control: reassign -3 lintian 2.117.0 C

Bug#1070982: marked as done (src:click: fails to migrate to testing for too long: autopkgtest regression on !amd64)

2024-05-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 May 2024 16:49:26 + with message-id and subject line Bug#1070982: fixed in click 0.5.2-3 has caused the Debian Bug report #1070982, regarding src:click: fails to migrate to testing for too long: autopkgtest regression on !amd64 to be marked as done. This means that

Bug#1071059: mousepad: segfaults at each launch !

2024-05-13 Thread Philippe Caillaud
Package: mousepad Version: 0.6.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, I use mousepad almost each day for small text editing ; since a few days (maybe 2 or 3), mousepad stopped working : at each run, it crashes (segmentation fault) : $ mou

Bug#1071058: mumble-server: prompting due to modified conffiles which were not modified by the user: /etc/mumble/mumble-server.ini

2024-05-13 Thread Andreas Beckmann
Package: mumble-server Version: 1.5.517-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed the piuparts upgrade test because dpkg detected a conffile as being modified and then prompted the user for an action. As t

Bug#1071057: sbws: prompting due to modified conffiles which were not modified by the user: /etc/cron.d/sbws

2024-05-13 Thread Andreas Beckmann
Package: sbws Version: 1.9.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed the piuparts upgrade test because dpkg detected a conffile as being modified and then prompted the user for an action. As there is no

Bug#1068419: marked as done (perdition: dependencies unsatisfiable after binnmu for time64 transition.)

2024-05-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 May 2024 16:04:31 + with message-id and subject line Bug#1068419: fixed in perdition 2.2-3.4 has caused the Debian Bug report #1068419, regarding perdition: dependencies unsatisfiable after binnmu for time64 transition. to be marked as done. This means that you cla

Bug#1064263: marked as done (openmpi: NMU diff for 64-bit time_t transition)

2024-05-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 May 2024 15:24:35 + with message-id and subject line Bug#1064263: fixed in openmpi 5.0.3-3 has caused the Debian Bug report #1064263, regarding openmpi: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been d

Processed (with 1 error): Re: Bug#1071034: Acknowledgement (unversioned libuv1 Provides: is inadequate)

2024-05-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1071034 wishlist Bug #1071034 [src:libuv1] unversioned libuv1 Provides: is inadequate Severity set to 'wishlist' from 'serious' > retitile 1071034 Please create versioned Provides: Unknown command or malformed arguments to command. > End

Bug#1070865: marked as done (webkit2gtk/experimental FTBFS on big endian)

2024-05-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 May 2024 14:42:01 + with message-id and subject line Bug#1070865: fixed in webkit2gtk 2.45.1-2 has caused the Debian Bug report #1070865, regarding webkit2gtk/experimental FTBFS on big endian to be marked as done. This means that you claim that the problem has been

Bug#1071053: python3-pynpoint: uninstallable in sid: Depends: python3-h5py (< 3.10) but 3.10.0-1 is to be installed

2024-05-13 Thread Andreas Beckmann
Package: python3-pynpoint Version: 0.11.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: The following packages have unmet dependencies: python3-pynpoint : Depends: python3-h5py

Processed: Re: Bug#1071038: golang-google-api: timeout in test TestBundlerTimeBasedFlushDeadlock

2024-05-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 patch Bug #1071038 [src:golang-google-api] golang-google-api: timeout in test TestBundlerTimeBasedFlushDeadlock Added tag(s) patch. -- 1071038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071038 Debian Bug Tracking System Contact ow...@bugs.debian.or

Bug#1071038: golang-google-api: timeout in test TestBundlerTimeBasedFlushDeadlock

2024-05-13 Thread Reinhard Tartler
Control: tag -1 patch On 5/13/24 9:15 AM, Reinhard Tartler wrote: I suspect this issue may be triggered by the upload of golang-golang-x-sync 0.7.0 to sid. #1071035 is another issue related to code changes in the semaphore implmentation. in google-api-go, I've found exactly one upstream commi

Bug#1071038: golang-google-api: timeout in test TestBundlerTimeBasedFlushDeadlock

2024-05-13 Thread Reinhard Tartler
I suspect this issue may be triggered by the upload of golang-golang-x-sync 0.7.0 to sid. #1071035 is another issue related to code changes in the semaphore implmentation. in google-api-go, I've found exactly one upstream commit that we don't currently have in debian in the 'support/bundler' p

Bug#1035833: cpptraj: autopkgtest failure everywhere except on amd64

2024-05-13 Thread Andrius Merkys
On Wed, 10 May 2023 02:29:08 +0530 Kiran S Kunjumon wrote: === FAILURES === TEST: /tmp/autopkgtest-lxc.kz5vbtvg/downtmp/build.qgE/src/test/Test_SPAM CPPTRAJ: SPAM Test ../MasterTest.sh: line 495: 3218 Killed $c

Bug#1014539: squirrel3: CVE-2022-30292

2024-05-13 Thread Pierre-Elliott Bécue
Hello, Matthias Geiger wrote on 07/05/2024 at 00:05:36+0200: > On Thu, 18 Apr 2024 14:40:58 +0200 Matthias Geiger > wrote: > >> >> //I have prepared a fix; however this needs the FTBFS in #997441 >> adressed first. >> >> Will attach a debdiff once that has happened. >> > > See attachement. > >

Bug#1071050: kwin-bismuth: Does not work after binary-only upload as typescript transpiled incorrectly with es2022 features

2024-05-13 Thread Petr Gajdůšek
Package: kwin-bismuth Version: 3.1.4-4+b1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: petr.gajdu...@egston.com Dear Maintainer, After upgrade to 3.1.4-4+b1 kwin-bismuth no more works with following error in syslog: kwin_x11[3514]: kwin_scripting: Component failed to loa

Bug#1071049: mercurial-evolve: current version of evolve incompatible with current mercurial

2024-05-13 Thread Rémi Letot
Package: mercurial-evolve Version: 11.1.1-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: hob...@poukram.net Dear Maintainer, using the current mercurial-evolve package (version 11.1.1-1) leads to errors with mercurial 6.7: hg commit ** Unknown exception encountered wit

Processed: Re: Bug#1071035: FAIL: TestGroup_deadlock

2024-05-13 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 golang-golang-x-sync 0.7.0 Bug #1071035 [src:golang-github-fatih-semgroup] FAIL: TestGroup_deadlock Bug reassigned from package 'src:golang-github-fatih-semgroup' to 'golang-golang-x-sync'. No longer marked as found in versions golang-github-fatih-semgro

Bug#1071035: FAIL: TestGroup_deadlock

2024-05-13 Thread Reinhard Tartler
Control: reassign -1 golang-golang-x-sync 0.7.0 Control: affects -1 golang-github-fatih-semgroup This seems to be related to upgrading golang-golang-x-sync to 0.7.0. This is how to reproduce is using pristine upstream sources: siretart@x1:/tmp/docker.io $ git clone https://github.com/fatih/semg

Processed: bug 1070113 is forwarded to https://github.com/ukui/kylin-nm/issues/154

2024-05-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1070113 https://github.com/ukui/kylin-nm/issues/154 Bug #1070113 [kylin-nm] kylin-nm: predictable filenames under /tmp with system() Set Bug forwarded-to-address to 'https://github.com/ukui/kylin-nm/issues/154'. > thanks Stopping process

Processed: rust-coreutils: FTBFS on armhf,armel (`timespec` with struct literal syntax due to private fields)

2024-05-13 Thread Debian Bug Tracking System
Processing control commands: > found -1 0.0.26-1 Bug #1071048 [src:rust-coreutils] rust-coreutils: FTBFS on armhf,armel (`timespec` with struct literal syntax due to private fields) Marked as found in versions rust-coreutils/0.0.26-1. -- 1071048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bu

Bug#1071048: rust-coreutils: FTBFS on armhf,armel (`timespec` with struct literal syntax due to private fields)

2024-05-13 Thread Kentaro HAYASHI
Source: rust-coreutils Severity: serious Tags: ftbfs Control: found -1 0.0.26-1 Dear Maintainer, rust-coreutils fails to build on armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=rust-coreutils&arch=armel&ver=0.0.26-1&stamp=1714571498&raw=0 https://buildd.debian.org/status/fetch.php?p

Bug#1071045: gauche-c-wrapper: FTBFS against gauche 0.9.14 (0.98)

2024-05-13 Thread Andreas Beckmann
Source: gauche-c-wrapper Version: 0.6.1-12 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source (but built successfully in the past) User: debian...@lists.debian.org Usertags: piuparts dh_auto_build make -j16 make[1]: Entering directory '/build/gauche-c-wra

Processed: Re: Bug#1071035: FAIL: TestGroup_deadlock

2024-05-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 patch Bug #1071035 [src:golang-github-fatih-semgroup] FAIL: TestGroup_deadlock Added tag(s) patch. -- 1071035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071035 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1071035: FAIL: TestGroup_deadlock

2024-05-13 Thread Reinhard Tartler
Control: tag -1 patch I've filed https://github.com/fatih/semgroup/pull/7 as a workaround. Anthony, what's your take on this, should we include that patch in the Debian Package? -rt From bb5f94c0d8e6ddf1f24f673303d73e84c285e1ac Mon Sep 17 00:00:00 2001 From: Reinhard Tartler Date: Mon, 13

Processed: rust-mimalloc: FTBFS on armhf (E: Build killed with signal TERM after 150 minutes of inactivity)

2024-05-13 Thread Debian Bug Tracking System
Processing control commands: > found -1 0.1.29-1+b2 Bug #1071046 [src:rust-mimalloc] rust-mimalloc: FTBFS on armhf (E: Build killed with signal TERM after 150 minutes of inactivity) The source 'rust-mimalloc' and version '0.1.29-1+b2' do not appear to match any binary packages Marked as found in

Bug#1071046: rust-mimalloc: FTBFS on armhf (E: Build killed with signal TERM after 150 minutes of inactivity)

2024-05-13 Thread Kentaro HAYASHI
Source: rust-mimalloc Severity: serious Tags: ftbfs Control: found -1 0.1.29-1+b2 Dear Maintainer, rust-mimalloc fails to build on armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=rust-mimalloc&arch=armhf&ver=0.1.29-1%2Bb2&stamp=1714283560&raw=0 Regards,

Processed: rust-libmimalloc-sys : FTBFS on armhf (signal: 11, SIGSEGV: invalid memory reference)

2024-05-13 Thread Debian Bug Tracking System
Processing control commands: > found -1 0.1.25-1+b2 Bug #1071044 [src:rust-libmimalloc-sys] rust-libmimalloc-sys : FTBFS on armhf (signal: 11, SIGSEGV: invalid memory reference) The source 'rust-libmimalloc-sys' and version '0.1.25-1+b2' do not appear to match any binary packages Marked as found

Bug#1071044: rust-libmimalloc-sys : FTBFS on armhf (signal: 11, SIGSEGV: invalid memory reference)

2024-05-13 Thread Kentaro HAYASHI
Source: rust-libmimalloc-sys Severity: serious Tags: ftbfs Control: found -1 0.1.25-1+b2 Dear Maintainer, rust-libmimalloc-sys fails to build on armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=rust-libmimalloc-sys&arch=armhf&ver=0.1.25-1%2Bb2&stamp=1714271391&raw=0 Regards,

Processed: Re: [Debian-zh-dev] Bug#1071039: iptux FTBFS on 32bit with 64bit time_t

2024-05-13 Thread Debian Bug Tracking System
Processing control commands: > tags -1 upstream Bug #1071039 [src:iptux] iptux FTBFS on 32bit with 64bit time_t Added tag(s) upstream. > forwarded -1 https://github.com/iptux-src/iptux/issues/581 Bug #1071039 [src:iptux] iptux FTBFS on 32bit with 64bit time_t Set Bug forwarded-to-address to 'https

Bug#1071039: [Debian-zh-dev] Bug#1071039: iptux FTBFS on 32bit with 64bit time_t

2024-05-13 Thread 肖盛文
Control: tags -1 upstream Control: forwarded -1 https://github.com/iptux-src/iptux/issues/581 Hi Adrian, Thanks for your report. 在 2024/5/13 18:49, Adrian Bunk 写道: Source: iptux Version: 0.9.1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=iptux&ver=0.9.1-1 .

Bug#1071043: libpsml-dev: unsatisfiable (Build-)Depends: libxmlf90-dev

2024-05-13 Thread Andreas Beckmann
Package: libpsml-dev Version: 2.0.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: The following packages have unmet dependencies: libpsml-dev : Depends: libxmlf90-dev but it is

Bug#1071009: marked as done (libpoppler-cpp0t64 has an undeclared file conflict)

2024-05-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 May 2024 11:49:25 + with message-id and subject line Bug#1071009: fixed in poppler 24.02.0-4 has caused the Debian Bug report #1071009, regarding libpoppler-cpp0t64 has an undeclared file conflict to be marked as done. This means that you claim that the problem has

Bug#1071008: libx52pro0: installs udev rules twice to /usr and /

2024-05-13 Thread Andreas Beckmann
Followup-For: Bug #1071008 I noticed in piuparts that the package is currently uninstallable, probably related to this bug. Selecting previously unselected package libx52pro0. Preparing to unpack .../libx52pro0_0.1.1-3_amd64.deb ... Unpacking libx52pro0 (0.1.1-3) ... dpkg: error processin

Bug#1071039: iptux FTBFS on 32bit with 64bit time_t

2024-05-13 Thread Adrian Bunk
Source: iptux Version: 0.9.1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=iptux&ver=0.9.1-1 ... FAILED: src/iptux-core/libiptux-core.so.0.9.1.p/internal_SendFileData.cpp.o c++ -Isrc/iptux-core/libiptux-core.so.0.9.1.p -Isrc/iptux-core -I../src/iptux-core -Isrc -

Bug#1070824: Acknowledgement (legiond: depends on lenovolegionlinux-dkms which is in contrib)

2024-05-13 Thread Andreas Beckmann
Furthermore in dkms.conf you should add # linux/platform_profile.h, wmi_evaluate_method() BUILD_EXCLUSIVE_CONFIG="CONFIG_ACPI_PLATFORM_PROFILE CONFIG_ACPI_WMI" to skip building the module on unsupported kernel configurations Andreas

Bug#1071038: golang-google-api: timeout in test TestBundlerTimeBasedFlushDeadlock

2024-05-13 Thread Reinhard Tartler
Source: golang-google-api Version: 0.61.0-4 Severity: serious Justification: FTBFS I am unable to build the package (reliably) on my laptop. It turns out that the test TestBundlerTimeBasedFlushDeadlock times out after 10 minutes: It seems that the test introduced by 6114940 is hanging/deadlockin

Bug#1071037: v4l2loopback-dkms: module fails to build for i386: ERROR: modpost: "__moddi3" undefined!

2024-05-13 Thread Andreas Beckmann
Package: v4l2loopback-dkms Version: 0.13.1-1 Severity: serious DKMS make.log for v4l2loopback-0.13.1 for kernel 6.7.12-686-pae (i686) Mon May 13 09:57:13 UTC 2024 ++ To sign the module, you must set KBUILD_SIGN_KEY/KBUILD_SIGN_CERT to point to the signing key/certificate! ++ For your co

Bug#1071035: FAIL: TestGroup_deadlock

2024-05-13 Thread Reinhard Tartler
Source: golang-github-fatih-semgroup Version: 1.2.0-2 Severity: serious Justification: FTBFS Your package fails to build from source, more specifically, when running the test suite. I can reproduce on my amd64 laptop. Here is the relevant part of the log: dh_auto_test -O--builddirectory=_buil

Bug#1071034: unversioned libuv1 Provides: is inadequate

2024-05-13 Thread Antonio Russo
Source: libuv1 Version: 1.48.0-3 Severity: serious X-Debbugs-Cc: aeru...@aerusso.net Dear Maintainer, libuv1 version 1.48.0-3 has an unversioned Provides: libuv1 line, but packages (such as cmake) have versioned dependencies on libuv1. This is breaking cmake in unstable right now. It appears t

Processed: Re: Bug#1070983: supertuxkart: symbol lookup error: undefined symbol

2024-05-13 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:shaderc Bug #1070983 [supertuxkart] supertuxkart: symbol lookup error: undefined symbol Bug reassigned from package 'supertuxkart' to 'src:shaderc'. No longer marked as found in versions supertuxkart/1.4+dfsg-4. Ignoring request to alter fixed version

Bug#1070983: supertuxkart: symbol lookup error: undefined symbol

2024-05-13 Thread Tobias Frost
Control: reassign -1 src:shaderc Control: affects -1 src:supertuxkart Control: fixed -1 2023.8-1 Hi Bernd, It seems that that symbol is missing in libshaderci [1] , and it seems that it is in version 2023.8-1 (which is currently only in unstable.) So, if you feel comfortable pull in that package

Bug#1071006: marked as done (conky-all, conky-cli and conky-std have an undeclared file conflict)

2024-05-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 May 2024 09:20:51 + with message-id and subject line Bug#1071006: fixed in conky 1.21.0-2 has caused the Debian Bug report #1071006, regarding conky-all, conky-cli and conky-std have an undeclared file conflict to be marked as done. This means that you claim that th

Bug#1069254: marked as done (nwipe: FTBFS: configure: error: libconfig library not found)

2024-05-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 May 2024 08:56:43 + with message-id and subject line Bug#1069254: fixed in nwipe 0.37-1 has caused the Debian Bug report #1069254, regarding nwipe: FTBFS: configure: error: libconfig library not found to be marked as done. This means that you claim that the problem

Bug#1071031: ezurio-qcacld-2.0-dkms: several module build failures

2024-05-13 Thread Andreas Beckmann
Package: ezurio-qcacld-2.0-dkms Version: 0.0~git20230623.2cd31b6-1 Severity: serious The module fails to build for several architectures and kernel versions: Linux 6.6.*: https://ci.debian.net/packages/e/ezurio-qcacld-2.0-dkms/testing/amd64/45828215/#L3674 243s /var/lib/dkms/ezurio-qcacld-2.0/0.

Processed: Re: evolution-data-server: missing dpkg-dev (>= 1.22.5) build dependnecy for time_t transition

2024-05-13 Thread Debian Bug Tracking System
Processing control commands: > notfound -1 3.51.2-1 Bug #1065281 {Done: Michael Hudson-Doyle } [src:evolution-data-server] evolution-data-server: missing dpkg-dev (>= 1.22.5) build dependnecy for time_t transition No longer marked as found in versions evolution-data-server/3.51.2-1. > found -1 3

Bug#1065281: evolution-data-server: missing dpkg-dev (>= 1.22.5) build dependnecy for time_t transition

2024-05-13 Thread Emilio Pozuelo Monfort
Control: notfound -1 3.51.2-1 Control: found -1 3.50.3-2 Control: fixed -1 3.50.3-2.1 On Sat, 2 Mar 2024 11:53:00 +0100 Sebastian Ramacher wrote: Source: evolution-data-server Version: 3.51.2-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org Thank you for uploading the

Processed: Re: FTBFS: [Makefile:163: check] Error 1

2024-05-13 Thread Debian Bug Tracking System
Processing control commands: > tags -1 ftbfs Bug #1069321 [src:hypre] FTBFS: [Makefile:163: check] Error 1 Ignoring request to alter tags of bug #1069321 to the same tags previously set -- 1069321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069321 Debian Bug Tracking System Contact ow...

Bug#1069321: FTBFS: [Makefile:163: check] Error 1

2024-05-13 Thread Drew Parsons
Source: hypre Followup-For: Bug #1069321 Control: tags -1 ftbfs hypre is passing debci and reproducibility tests on armhf. Looks like the error reported here was a transitory issue, possibly related to openmpi upgrades.