Bug#1080115: fixed in upstream release 0.15.0

2024-10-16 Thread Paolo Greppi
According to the issue: https://github.com/magic-wormhole/magic-wormhole/issues/537 this should be fixed upstream in releases 0.15.0 and later. A fix for the version in sid is to pin the attr module to version 23.2.0 but ATM python3-attr in sid is at version 24.2.0-1: https://packages.debian.or

Bug#1082933: marked as done (geoalchemy2: build failure on s390x)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Thu, 17 Oct 2024 05:34:28 + with message-id and subject line Bug#1082933: fixed in geoalchemy2 0.15.2-1 has caused the Debian Bug report #1082933, regarding geoalchemy2: build failure on s390x to be marked as done. This means that you claim that the problem has been dealt w

Processed (with 1 error): merge related bugs

2024-10-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1080115 1079401 Bug #1080115 [src:magic-wormhole] magic-wormhole: FTBFS: ImportError: cannot import name 'provides' from 'attr.validators' (/usr/lib/python3/dist-packages/attr/validators.py) Unable to merge bugs because: package of #1

Bug#1085151: marked as done (openmpi: FTBFS on arch:all: missing files, aborting)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Thu, 17 Oct 2024 04:35:34 + with message-id and subject line Bug#1085151: fixed in openmpi 5.0.5-3 has caused the Debian Bug report #1085151, regarding openmpi: FTBFS on arch:all: missing files, aborting to be marked as done. This means that you claim that the problem has b

Bug#1085168: marked as done (genders: FTBFS on mips64el and ppc64el: parallel build issue?)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Thu, 17 Oct 2024 03:19:08 + with message-id and subject line Bug#1085168: fixed in genders 1.27-3-3 has caused the Debian Bug report #1085168, regarding genders: FTBFS on mips64el and ppc64el: parallel build issue? to be marked as done. This means that you claim that the pr

Bug#1085175: marked as done (genders: Frequent parallel build failure)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Thu, 17 Oct 2024 03:19:08 + with message-id and subject line Bug#1085168: fixed in genders 1.27-3-3 has caused the Debian Bug report #1085168, regarding genders: Frequent parallel build failure to be marked as done. This means that you claim that the problem has been dealt

Bug#1078212:

2024-10-16 Thread Matthew Scutter
This fix causes openmpi-bin to be uninstallable on sid 8.406 Some packages could not be installed. This may mean that you have 8.406 requested an impossible situation or if you are using the unstable 8.406 distribution that some required packages have not yet been created 8.406 or been moved out of

Bug#1085214: marked as done (xpenguins FTBFS on 32-bit with 64-bit time_t with gcc 14)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 22:20:29 + with message-id and subject line Bug#1085214: fixed in xpenguins 3.2.3-2 has caused the Debian Bug report #1085214, regarding xpenguins FTBFS on 32-bit with 64-bit time_t with gcc 14 to be marked as done. This means that you claim that the proble

Bug#1077834: marked as done (dm-writeboost-dkms: module fails to build for Linux 6.10: error: 'struct block_device' has no member named 'bd_inode')

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 22:18:59 + with message-id and subject line Bug#1077834: fixed in dm-writeboost 2.2.17-0.3 has caused the Debian Bug report #1077834, regarding dm-writeboost-dkms: module fails to build for Linux 6.10: error: 'struct block_device' has no member named 'bd_in

Processed: your mail

2024-10-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1085111 https://github.com/mikedh/trimesh/pull/2248 Bug #1085111 [src:trimesh] trimesh FTBFS: ValueError: The truth value of an array with more than one element is ambiguous. Set Bug forwarded-to-address to 'https://github.com/mikedh/tr

Bug#1085058: marked as done (iaito: FTBFS: Package libxxhash was not found in the pkg-config search path.)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 21:04:55 + with message-id and subject line Bug#1085058: fixed in iaito 5.9.4+ds-2 has caused the Debian Bug report #1085058, regarding iaito: FTBFS: Package libxxhash was not found in the pkg-config search path. to be marked as done. This means that you c

Bug#1056028: marked as done (rust-ntp-udp: autopkgtest failure)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 22:53:39 +0200 with message-id <71ec8871-0430-4fb0-9334-3267e4b80...@debian.org> and subject line done has caused the Debian Bug report #1056028, regarding rust-ntp-udp: autopkgtest failure to be marked as done. This means that you claim that the problem has bee

Bug#1071898: closing 1071898

2024-10-16 Thread Roland Mas
close 1071898 0.9.74+ds1-2 thanks

Processed: closing 1071898

2024-10-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1071898 0.9.74+ds1-2 Bug #1071898 [src:xraylarch] xraylarch: FTBFS: unsatisfiable build-dependencies The source 'xraylarch' and version '0.9.74+ds1-2' do not appear to match any binary packages Marked as fixed in versions xraylarch/0.9.74+d

Processed: bug 1083210 is forwarded to https://github.com/firewalld/firewalld/issues/1403 ...

2024-10-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1083210 https://github.com/firewalld/firewalld/issues/1403 Bug #1083210 [src:firewalld] firewalld: flaky autopkgtest: write error: Broken pipe Changed Bug forwarded-to-address to 'https://github.com/firewalld/firewalld/issues/1403' fro

Bug#1084277: imexam: FTBFS: failing tests

2024-10-16 Thread Ole Streicher
imexam seems unmaintained since 2022. I am not sure whether it is worth to put too much efforts into the package, but I will ask for future plans there.

Processed: closing 1041089

2024-10-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1041089 1.1.0-1 Bug #1041089 [src:thin-provisioning-tools] thin-provisioning-tools FTBFS with googletest 1.13.0 Marked as fixed in versions thin-provisioning-tools/1.1.0-1. Bug #1041089 [src:thin-provisioning-tools] thin-provisioning-tools

Bug#1079329: systemd(?) still creates /lib64 on arm64

2024-10-16 Thread Luca Boccassi
On Thu, 10 Oct 2024 at 21:08, Helmut Grohne wrote: > > Hi Luca, > > On Thu, Oct 10, 2024 at 11:35:17AM +0100, Luca Boccassi wrote: > > Sorry, but I am still not following. I do not understand, why would > > lib64 not be needed? It's a 64bit architecture, no? If I download a > > Fedora 40 aarch64 i

Processed: Update bug 1085207

2024-10-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1085207 6.3.1-1 Bug #1085207 [btrfs-progs] btrfs-progs: bad csum when migrating from ext4 Marked as fixed in versions btrfs-progs/6.3.1-1. > tags 1085207 + bookworm Bug #1085207 [btrfs-progs] btrfs-progs: bad csum when migrating from ext4 Ad

Bug#1084043: marked as done (turtlefmt: FTBFS: method not found in `TurtleParser`)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 17:35:08 + with message-id and subject line Bug#1084043: fixed in turtlefmt 0.1.1-4 has caused the Debian Bug report #1084043, regarding turtlefmt: FTBFS: method not found in `TurtleParser` to be marked as done. This means that you claim that the problem ha

Processed: bug 1083210 is forwarded to https://github.com/firewalld/firewalld/issues/1365

2024-10-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1083210 https://github.com/firewalld/firewalld/issues/1365 Bug #1083210 [src:firewalld] firewalld: flaky autopkgtest: write error: Broken pipe Set Bug forwarded-to-address to 'https://github.com/firewalld/firewalld/issues/1365'. > than

Processed: Re: Bug#1083070: bmtk: tests fail: No module named 'distutils'

2024-10-16 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch pending Bug #1083070 [src:bmtk] bmtk: tests fail: No module named 'distutils' Added tag(s) patch and pending. > forwarded -1 https://github.com/AllenInstitute/bmtk/pull/385 Bug #1083070 [src:bmtk] bmtk: tests fail: No module named 'distutils' Set Bug fo

Bug#1083070: bmtk: tests fail: No module named 'distutils'

2024-10-16 Thread Étienne Mollier
Control: tags -1 patch pending Control: forwarded -1 https://github.com/AllenInstitute/bmtk/pull/385 Control: block -1 by 1085151 Hi, Drew Parsons, on 2024-10-01: > bmtk has started failing debci tests, due to a requirement for > distutils which is no longer packaged for debian I have an upload

Bug#1085030: marked as done (libghc-swish-doc: Rebuild against GHC 9.6)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 17:34:27 + with message-id and subject line Bug#1085030: fixed in haskell-swish 0.10.9.0-2 has caused the Debian Bug report #1085030, regarding libghc-swish-doc: Rebuild against GHC 9.6 to be marked as done. This means that you claim that the problem has be

Processed: Re: plasma-desktop 4:6.2.0-1 is uninstallable on a fresh chroot

2024-10-16 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1085139 [plasma-desktop] plasma-desktop 4:6.2.0-1 is uninstallable on a fresh chroot Severity set to 'important' from 'grave' -- 1085139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085139 Debian Bug Tracking System Contact ow...@

Bug#1085139: plasma-desktop 4:6.2.0-1 is uninstallable on a fresh chroot

2024-10-16 Thread Patrick Franz
Control: severity -1 important Hi, On Tue, 15 Oct 2024 13:36:24 +0300 Faidon Liambotis wrote: > Package: plasma-desktop > Version: 4:6.2.0-1 > Severity: grave > > I asked around on #debian-kde before filing this bug, but I don't think > there was a clear answer there. I'm not sure if you're w

Processed: Update bug 1085207

2024-10-16 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1085207 [btrfs-progs] btrfs-progs: bad csum when migrating from ext4 Severity set to 'serious' from 'normal' > found -1 4.4.1-1.1 Bug #1085207 [btrfs-progs] btrfs-progs: bad csum when migrating from ext4 Marked as found in versions btrfs-prog

Processed: Update bug 1080510 -- sorry

2024-10-16 Thread Debian Bug Tracking System
Processing control commands: > severity -1 minor Bug #1080510 [src:onnxruntime] onnxruntime: please upgrade to latest upstream release 1.19.2 Severity set to 'minor' from 'serious' > notfound -1 4.4.1-1.1 Bug #1080510 [src:onnxruntime] onnxruntime: please upgrade to latest upstream release 1.19.

Bug#1080510: Update bug 1080510 -- sorry

2024-10-16 Thread 陈 晟祺
Control: severity -1 minor Control: notfound -1 4.4.1-1.1 Control: notforwarded -1 Control: tags -1 - patch fixed-upstream Control: close -1 Really sorry for the mess. I accidentally sent to the wrong bug#. Shengqi Chen

Processed: Update bug 1085207

2024-10-16 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1080510 {Done: Dylan Aïssi } [src:onnxruntime] onnxruntime: please upgrade to latest upstream release 1.19.2 Severity set to 'serious' from 'minor' > found -1 4.4.1-1.1 Bug #1080510 {Done: Dylan Aïssi } [src:onnxruntime] onnxruntime: please

Processed: geoalchemy2: autopkgtest failure on i386 & s390x

2024-10-16 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1082933 [src:geoalchemy2] geoalchemy2: build failure on s390x Added tag(s) patch. -- 1082933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1082933: geoalchemy2: autopkgtest failure on i386 & s390x

2024-10-16 Thread Sebastiaan Couwenberg
Control: tags -1 patch The autopkgtest failure on i386 cannot be fixed, as postgis no longer support 32-bit architectures. For an Architecture: all package the autopkgtest failure on s390x should not be a blocker either. The attached patch excludes the 32-bit and big endian architectures from

Bug#1085214: xpenguins FTBFS on 32-bit with 64-bit time_t with gcc 14

2024-10-16 Thread Adrian Bunk
Source: xpenguins Version: 3.2.1-2 Severity: serious Tags: ftbfs patch X-Debbugs-Cc: Alexandre Detiste https://tests.reproducible-builds.org/debian/rb-pkg/trixie/armhf/xpenguins.html https://buildd.debian.org/status/logs.php?pkg=xpenguins&ver=3.2.3-1 ... xpenguins_core.c: In function ‘xpenguins_

Bug#1085029: marked as done (libghc-intern-doc: Rebuild against GHC 9.6)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 16:35:10 + with message-id and subject line Bug#1085029: fixed in haskell-intern 0.9.5-3 has caused the Debian Bug report #1085029, regarding libghc-intern-doc: Rebuild against GHC 9.6 to be marked as done. This means that you claim that the problem has bee

Bug#1085028: marked as done (libghc-hsyaml-doc: Rebuild against GHC 9.6)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 16:35:03 + with message-id and subject line Bug#1085028: fixed in haskell-hsyaml 0.2.1.4-2 has caused the Debian Bug report #1085028, regarding libghc-hsyaml-doc: Rebuild against GHC 9.6 to be marked as done. This means that you claim that the problem has b

Processed: Update bug 1083286

2024-10-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1083286 important Bug #1083286 [libxnnpack0] libxnnpack0: rmoved symbols (xnn_setup_convolution2d_nhwc_qc8 xnn_create_convolution2d_nhwc_qc8) cause third party packages to fail Severity set to 'important' from 'serious' > thanks Stoppin

Bug#1066323: marked as done (uniutils: FTBFS: uniname.c:531:43: error: implicit declaration of function ‘isspace’ [-Werror=implicit-function-declaration])

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 15:07:27 + with message-id and subject line Bug#1066323: fixed in uniutils 2.28-1 has caused the Debian Bug report #1066323, regarding uniutils: FTBFS: uniname.c:531:43: error: implicit declaration of function ‘isspace’ [-Werror=implicit-function-declaratio

Bug#1084375: marked as done (rust-rustls: FTBFS: error: failed to select a version for the requirement `base64 = "^0.21"`)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 14:50:49 + with message-id and subject line Bug#1084375: fixed in rust-rustls 0.21.12-6 has caused the Debian Bug report #1084375, regarding rust-rustls: FTBFS: error: failed to select a version for the requirement `base64 = "^0.21"` to be marked as done.

Bug#1084377: marked as done (rust-xor-name: FTBFS: error: lint `box_pointers` has been removed: it does not detect other kinds of allocations, and existed only for historical reasons)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 14:39:10 + with message-id and subject line Bug#1084377: fixed in rust-xor-name 5.0.0-8 has caused the Debian Bug report #1084377, regarding rust-xor-name: FTBFS: error: lint `box_pointers` has been removed: it does not detect other kinds of allocations, an

Bug#1084298: marked as done (meli: FTBFS: error: failed to select a version for the requirement `base64 = ">=0.13, <=0.21"`)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 14:37:03 + with message-id and subject line Bug#1084298: fixed in meli 0.8.7+20241007+dfsg-1 has caused the Debian Bug report #1084298, regarding meli: FTBFS: error: failed to select a version for the requirement `base64 = ">=0.13, <=0.21"` to be marked as

Bug#1081873: marked as done (pymdown-extensions: FTBFS: E AssertionError: False is not true)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 13:16:23 + with message-id and subject line Bug#1081873: fixed in pymdown-extensions 10.11.2-1 has caused the Debian Bug report #1081873, regarding pymdown-extensions: FTBFS: E AssertionError: False is not true to be marked as done. This means that you clai

Bug#1082313: marked as done (dokuwiki,php-random-compat: aliasing conflict on /usr/share/php/random_compat)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 12:34:47 + with message-id and subject line Bug#1082313: fixed in dokuwiki 0.0.20220731.a-3 has caused the Debian Bug report #1082313, regarding dokuwiki,php-random-compat: aliasing conflict on /usr/share/php/random_compat to be marked as done. This means

Bug#1082314: marked as done (dokuwiki,php-phpseclib: aliasing conflict on /usr/share/php/phpseclib)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 12:34:47 + with message-id and subject line Bug#1082314: fixed in dokuwiki 0.0.20220731.a-3 has caused the Debian Bug report #1082314, regarding dokuwiki,php-phpseclib: aliasing conflict on /usr/share/php/phpseclib to be marked as done. This means that you

Bug#1084356: marked as done (ros-joint-state-publisher: FTBFS: ModuleNotFoundError: No module named 'sensor_msgs')

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 12:14:08 + with message-id and subject line Bug#1084356: fixed in ros-joint-state-publisher 1.15.1-4 has caused the Debian Bug report #1084356, regarding ros-joint-state-publisher: FTBFS: ModuleNotFoundError: No module named 'sensor_msgs' to be marked as do

Bug#1085049: marked as done (python3-pyvkfft-cuda has an undeclared file conflict on /usr/lib/python3/dist-packages/pyvkfft/cuda.py)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 12:13:57 + with message-id and subject line Bug#1085049: fixed in pyvkfft-cuda 2024.1.4+ds1-3 has caused the Debian Bug report #1085049, regarding python3-pyvkfft-cuda has an undeclared file conflict on /usr/lib/python3/dist-packages/pyvkfft/cuda.py to be m

Bug#1079583: marked as done (jpy FTBFS on Zero-Assembler architectures with OpenJDK 21)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 12:08:24 + with message-id and subject line Bug#1079583: fixed in jpy 0.18.0-2 has caused the Debian Bug report #1079583, regarding jpy FTBFS on Zero-Assembler architectures with OpenJDK 21 to be marked as done. This means that you claim that the problem ha

Processed: odoo bugs

2024-10-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 1061261 + upstream Bug #1061261 [odoo-16] odoo: Uses deprecated/to be removed PyPDF2 Added tag(s) upstream. > tag 1084606 + upstream Bug #1084606 [src:odoo] odoo: removal of Python standard libraries in Python 3.13 Added tag(s) upstream. > ta

Processed: reassign 1084851 to sponsorship-requests, tagging 1084827, tagging 1084807, tagging 953935 ...

2024-10-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1084851 sponsorship-requests Bug #1084851 {Done: souravbhattacha...@tutamail.com} [sponsorship-requests] RFS: python3-nextdns/3.3.0-1 [ITP] -- Python wrapper for NextDNS API Ignoring request to reassign bug #1084851 to the same package >

Bug#1083178: marked as done (mercurial: FTBFS: Failed test-patchbomb.t: output changed)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 10:41:12 + with message-id and subject line Bug#1083178: fixed in mercurial 6.8.1-1 has caused the Debian Bug report #1083178, regarding mercurial: FTBFS: Failed test-patchbomb.t: output changed to be marked as done. This means that you claim that the probl

Processed: Re: ros-joint-state-publisher: FTBFS: ModuleNotFoundError: No module named 'sensor_msgs'

2024-10-16 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1084356 {Done: Timo Röhling } [src:ros-joint-state-publisher] ros-joint-state-publisher: FTBFS: ModuleNotFoundError: No module named 'sensor_msgs' 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cle

Bug#1084356: ros-joint-state-publisher: FTBFS: ModuleNotFoundError: No module named 'sensor_msgs'

2024-10-16 Thread Andreas Beckmann
Followup-For: Bug #1084356 Control: reopen -1 I can still reproduce the FTBFS reported by Santiago by rebuilding 1.15.1-3 in an up-to-date sid pbuilder environment. Andreas

Bug#1073467: marked as done (freecol: FTBFS: make: *** [debian/rules:8: binary] Error 25)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 10:22:00 + with message-id and subject line Bug#1073467: fixed in freecol 1.2.0-1 has caused the Debian Bug report #1073467, regarding freecol: FTBFS: make: *** [debian/rules:8: binary] Error 25 to be marked as done. This means that you claim that the probl

Bug#1084381: marked as done (spectral-cube: FTBFS: failing tests)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 09:19:20 + with message-id and subject line Bug#1084353: fixed in radio-beam 0.3.7-5 has caused the Debian Bug report #1084353, regarding spectral-cube: FTBFS: failing tests to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1084353: marked as done (radio-beam: FTBFS: E astropy.units.core.UnitScaleError: cannot create a unit with a scale of 0.)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 09:19:20 + with message-id and subject line Bug#1084353: fixed in radio-beam 0.3.7-5 has caused the Debian Bug report #1084353, regarding radio-beam: FTBFS: E astropy.units.core.UnitScaleError: cannot create a unit with a scale of 0. to be marked as done.

Bug#1084304: marked as done (mypy: FTBFS: FAILED mypyc/test/test_run.py::TestRun::run-dicts.test::testDictIterationMethodsRun)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 10:50:48 +0200 with message-id and subject line Re: mypy: FTBFS: FAILED mypyc/test/test_run.py::TestRun::run-dicts.test::testDictIterationMethodsRun has caused the Debian Bug report #1084304, regarding mypy: FTBFS: FAILED mypyc/test/test_run.py::TestRun::run-d

Bug#1085192: [Debian-on-mobile-maintainers] Bug#1085192: phoc: build-depends on missing: libwlroots-dev:loong64 (>= 0.17.0)

2024-10-16 Thread zhangdandan
在 2024/10/16 下午4:12, Guido Günther 写道: Hi, thanks for looking into this. On Wed, Oct 16, 2024 at 02:50:15PM +0800, zhangdandan wrote: 3. Solution Please take care of the d/control file in phoc packages. ```  libwlroots-dev (>= 0.17.0),  libwlroots-dev (<< 0.18~), ``` How would that change an

Processed: Re-assigning bug to radio-beam

2024-10-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1084381 src:radio-beam 0.3.7-4 Bug #1084381 [src:spectral-cube] spectral-cube: FTBFS: failing tests Bug reassigned from package 'src:spectral-cube' to 'src:radio-beam'. No longer marked as found in versions spectral-cube/0.6.5-4. Ignoring

Bug#1085192: [Debian-on-mobile-maintainers] Bug#1085192: phoc: build-depends on missing: libwlroots-dev:loong64 (>= 0.17.0)

2024-10-16 Thread John Paul Adrian Glaubitz
Hi Guido, On Wed, 2024-10-16 at 10:12 +0200, Guido Günther wrote: > How would that change anything? There is not libwlroots-dev >= 0.18.0. Hasn't phoc been ported to wlroots 0.18.0 yet? > Looks like the only solution would be to reintroduce wlroots 0.17 source > package as wlroots-0.17 so both s

Bug#1085192: [Debian-on-mobile-maintainers] Bug#1085192: phoc: build-depends on missing: libwlroots-dev:loong64 (>= 0.17.0)

2024-10-16 Thread Guido Günther
Hi, thanks for looking into this. On Wed, Oct 16, 2024 at 02:50:15PM +0800, zhangdandan wrote: > 3. Solution > Please take care of the d/control file in phoc packages. > ``` >  libwlroots-dev (>= 0.17.0), >  libwlroots-dev (<< 0.18~), > ``` How would that change anything? There is not libwlroots-

Bug#1085192: phoc: build-depends on missing: libwlroots-dev:loong64 (>= 0.17.0)

2024-10-16 Thread John Paul Adrian Glaubitz
Hello Dandan, On Wed, 2024-10-16 at 14:50 +0800, zhangdandan wrote: > The build status of phoc is BD-Uninstallable for loong64 and other > architectures in the Debian Package Auto-Building environment. Such bugs are actually rated as serious as it makes the package FTBFS on any architectures. Bu

Processed: severity of 1085192 is serious

2024-10-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1085192 serious Bug #1085192 [src:phoc] phoc: build-depends on missing: libwlroots-dev:loong64 (>= 0.17.0) Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1085192:

Bug#1082978: marked as done (ros-interactive-markers: FTBFS: ERROR: The following tests failed to run: * testserver_test)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 09:14:12 +0200 with message-id and subject line Fwd: ros-interactive-markers_1.12.0-10_source.changes ACCEPTED into unstable has caused the Debian Bug report #1082978, regarding ros-interactive-markers: FTBFS: ERROR: The following tests failed to run: * tests