Bug#1076058: marked as done (librust-wayland-sys-0.29-dev: impossible to install: depends on librust-memoffset-0.6+default-dev)

Your message dated Tue, 9 Jul 2024 20:53:26 -0400 with message-id and subject line Re: Bug#1076058: librust-wayland-sys-0.29-dev: impossible to install: depends on librust-memoffset-0.6+default-dev has caused the Debian Bug report #1076058, regarding librust-wayland-sys-0.29-dev: impossible to

Bug#1076060: LICENSE.txt says Apache 2.0, not GPL-3

Package: meshtastic Severity: serious User: paul...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks The LICENSE file is Apache 2. The pyproject.toml says GPL-3. I did some looking upstream, and there's a bug[1] and a PR that was fixed last week[2]. I don't love the

Processed: severity 1052507

Processing commands for cont...@bugs.debian.org: > severity 1052507 serious Bug #1052507 [src:azure-cosmos-python] azure-cosmos-python: upstream has moved to another repository Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need

Processed: 1073411 1072312

Processing commands for cont...@bugs.debian.org: > severity 1073411 normal Bug #1073411 [src:azure-cli] azure-cli: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 Severity set to 'normal' from 'serious' > severity 1072312 normal

Bug#1076058: librust-wayland-sys-0.29-dev: impossible to install: depends on librust-memoffset-0.6+default-dev

Package: librust-wayland-sys-0.29-dev Version: 0.29.5-2+b1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Binary package is impossible to install, as it depends on missing package librust-memoffset-0.6+default-dev. -BEGIN PGP

Bug#1076057: librust-wayland-sys-dev: impossible to install: depends on librust-memoffset-0.6+default-dev

Package: librust-wayland-sys-dev Version: 0.31.1-2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Binary package is impossible to install, as it depends on missing package librust-memoffset-0.6+default-dev. -BEGIN PGP SIGNATURE-

Processed: BTS housekeeping

Processing commands for cont...@bugs.debian.org: > # build dependencies were not installable during time_t transition > close 1069473 Bug #1069473 [src:prelude-manager] prelude-manager: FTBFS on armhf: unsatisfiable build-dependencies Marked Bug as done > close 1069479 Bug #1069479

Bug#1068468: marked as done (tracker: failing autopkgtest)

Your message dated Tue, 09 Jul 2024 22:50:19 + with message-id and subject line Bug#1068468: fixed in tracker 3.7.3-2 has caused the Debian Bug report #1068468, regarding tracker: failing autopkgtest to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > reassign 1069429 src:openmpi Bug #1069429 [src:dbcsr] dbcsr: FTBFS on armhf: tests fail Bug reassigned from package 'src:dbcsr' to 'src:openmpi'. No longer marked as found in versions dbcsr/2.6.0-2. Ignoring request to alter fixed versions of bug

Processed: tagging 1063190 as pending

Processing commands for cont...@bugs.debian.org: > tags 1063190 +pending Bug #1063190 [src:owncloud-client] owncloud-client: NMU diff for 64-bit time_t transition Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1063190:

Bug#1068468: marked as pending in tracker

Control: tag -1 pending Hello, Bug #1068468 in tracker reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1068468 marked as pending in tracker

Processing control commands: > tag -1 pending Bug #1068468 [src:tracker] tracker: failing autopkgtest Added tag(s) pending. -- 1068468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1061241: endless-sky: debian/copyright incomplete

Hi, Thanks for pointing out this. The upload for 0.10.4-1 was from me, so I am trying to fix the issue now. But before this, it seems I can learn more from here.:) On Sun, Jan 21, 2024 at 10:56:05AM +, Damyan Ivanov wrote: The upgrade to 0.10.4 missed the changes in upstream licensing and

Bug#1076036: python3-setuptools: uninstallable in unstable

On Tue, Jul 09, 2024 at 07:57:51PM +0100, Colin Watson wrote: > Following > https://tracker.debian.org/news/1543129/accepted-python3-stdlib-extensions-3124-1-source-into-unstable/, > python3-setuptools is uninstallable in unstable: Indeed, setuptools Build-Depends: dh-python Depends:

Processed: closing 1069373

Processing commands for cont...@bugs.debian.org: > close 1069373 0.4.0~alpha7-2 Bug #1069373 [src:oxigraph] oxigraph: FTBFS on arm64: unsatisfiable build-dependencies: librust-oxhttp-0.1+default-dev, librust-oxhttp-0.1+rayon-dev, librust-oxhttp-0.1+rustls-dev Marked as fixed in versions

Bug#1076036: python3-setuptools: uninstallable in unstable

Package: python3-setuptools Version: 68.1.2-2 Severity: grave Justification: renders package unusable Following https://tracker.debian.org/news/1543129/accepted-python3-stdlib-extensions-3124-1-source-into-unstable/, python3-setuptools is uninstallable in unstable: # apt install

Processed: hplip: diff for NMU version 3.22.10+dfsg0-5.1

Processing control commands: > tags 1075760 + pending Bug #1075760 [hplip-gui] hplip-gui breaks with python 3.12 Added tag(s) pending. -- 1075760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1075760: hplip: diff for NMU version 3.22.10+dfsg0-5.1

Control: tags 1075760 + pending Dear maintainer, I've prepared an NMU for hplip (versioned as 3.22.10+dfsg0-5.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should delay it longer. Regards. diff -Nru hplip-3.22.10+dfsg0/debian/changelog hplip-3.22.10+dfsg0/debian/changelog

Processed: playmidi: FTBFS when built in parallel

Processing commands for cont...@bugs.debian.org: > retitle 1076021 playmidi: FTBFS when built in parallel Bug #1076021 {Done: Santiago Vila } [playmidi] playmidi: FTBFS Changed Bug title to 'playmidi: FTBFS when built in parallel' from 'playmidi: FTBFS'. > thanks Stopping processing here.

Bug#1076031: freecad seems linked to python 3.11

Package: freecad Version: 0.21.2+dfsg1-4 Severity: grave Justification: renders package unusable ldd /usr/bin/freecad | grep found libpyside2.cpython-311-x86_64-linux-gnu.so.5.15 => not found libshiboken2.cpython-311-x86_64-linux-gnu.so.5.15 => not found -- System Information:

Bug#1076030: superlu-dist: FTBFS with mpich as default MPI implementation on 32 bit architectures: 0% tests passed, 17 tests failed out of 17

Source: superlu-dist Version: 8.2.1+dfsg1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=superlu-dist=armel=8.2.1%2Bdfsg1-1%2Bb3=1720482168=0 est 1

Bug#1076029: openfoam: FTBFS with mpich as default MPI implementation on armhf and i386: PstreamGlobals.H:42:10: fatal error: mpi.h: No such file or directory

Source: openfoam Version: 1912.200626-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=openfoam=armhf=1912.200626-2%2Bb4=1720486618=0 g++ -std=c++11

Bug#1076028: h5py: FTBFS with mpich as default MPI implementation on armel, armhf, i386: build/h5py/_debian_h5py_mpi/tests/test_file.py::TestMPI::test_mpio make[1]: *** [debian/rules:125: override_dh_

Source: h5py Version: 3.11.0-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=h5py=armel=3.11.0-2%2Bb1=1720479778=0

Bug#1076027: abinit: FTBFS with mpich as default MPI implementation on 32 bit architectures: Error: Type mismatch in argument ‘block_displ’ at (1); passed INTEGER(8) to INTEGER(4)

Source: abinit Version: 9.10.4-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=abinit=armel=9.10.4-3%2Bb2=1720487900=0 mpifort -DHAVE_CONFIG_H -I.

Bug#1076026: elpa: FTBFS with mpich as default MPI on i386: FAIL validate_complex_2stage_banded_default.sh (exit status: 15)

Source: elpa Version: 2022.11.001-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=elpa=i386=2022.11.001-3%2Bb1=1720479509=0 FAIL:

Bug#1076025: elpa: FTBFS with mpich as default MPI implementation on armel and armhf: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

Source: elpa Version: 2022.11.001-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=elpa=armel=2022.11.001-3%2Bb1=1720487973=0 dpkg-gensymbols: warning:

Bug#1076021: marked as done (playmidi: FTBFS)

Your message dated Tue, 09 Jul 2024 17:35:25 + with message-id and subject line Bug#1076021: fixed in playmidi 2.4debian-17 has caused the Debian Bug report #1076021, regarding playmidi: FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1039883: linux: ext4 corruption with symlinks

Control: tag -1 patch fixed-upstream A fix was applied to the ext4 "dev" branch earlier today: I would still want to wait at least a week or two before cherry-picking it, in

Processed: Re: linux: ext4 corruption with symlinks

Processing control commands: > tag -1 patch fixed-upstream Bug #1039883 [src:linux] linux: ext4 corruption with symlinks Added tag(s) patch and fixed-upstream. -- 1039883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039883 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1076021: playmidi: FTBFS

Package: playmidi Version: 2.4debian-16 Severity: serious Tags: ftbfs This is to let everybody know that I'm aware that the QA upload I've just made does not build ok. I'll try to fix this myself. Thanks.

Bug#1072816: marked as done (sploitscan: Configuration files installed in Python modules directory)

Your message dated Tue, 09 Jul 2024 16:49:29 + with message-id and subject line Bug#1072816: fixed in sploitscan 0.10.3-1 has caused the Debian Bug report #1072816, regarding sploitscan: Configuration files installed in Python modules directory to be marked as done. This means that you claim

Processed: closing 1075978

Processing commands for cont...@bugs.debian.org: > close 1075978 0.7-2-2 Bug #1075978 [src:rmpi] rmpi: FTBFS on 32 bit architectures: configure: error: "Cannot find mpi.h header file" The source 'rmpi' and version '0.7-2-2' do not appear to match any binary packages Marked as fixed in versions

Bug#1063190: [Pkg-owncloud-maintainers] Bug#1063190: closing 1063190 [owncloud-client+t64 RC]

El mar, 9 jul 2024 a las 14:26, Pierre-Elliott Bécue () escribió: > > Feel free to upload it even not as a NMU. (you can add a Team Upload > entry if you prefer) > > If you decide to NMU, don't --delay it. :) > > I have no time for owncloud-client now, but otherwise I'll try to look > into it in

Bug#1074706: [Pkg-pascal-devel] Bug#1074706: fpc: FTBFS: make[1]: *** [Makefile:9: de] Error 1

On 02/07/2024 14:30, Lucas Nussbaum wrote: Source: fpc Version: 3.2.2+dfsg-33 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240702 ftbfs-trixie Hi, Project developers During a rebuild of all packages in sid, your package failed to build

Bug#1075978: rmpi: FTBFS on 32 bit architectures: configure: error: "Cannot find mpi.h header file"

On 9 July 2024 at 18:42, Adrian Bunk wrote: | On Tue, Jul 09, 2024 at 10:34:43AM -0500, Dirk Eddelbuettel wrote: | > | > Adrian, | | Hi Dirk, | | > Will the patch to configure.ac, with the build system as it is, ensure | > autoconf is called or should I do that manually and hence also patch |

Bug#1072535: puma: flaky autopkgtest -> now fails always

Hi, On Mon, 3 Jun 2024 22:01:32 +0200 Paul Gevers wrote: I noticed that it regularly fails. It stopped being flaky and now always fails: 163s 1) Failure: 163s TestExampleCertExpiration#test_certs_not_expired

Bug#1075978: rmpi: FTBFS on 32 bit architectures: configure: error: "Cannot find mpi.h header file"

On Tue, Jul 09, 2024 at 10:34:43AM -0500, Dirk Eddelbuettel wrote: > > Adrian, Hi Dirk, > Will the patch to configure.ac, with the build system as it is, ensure > autoconf is called or should I do that manually and hence also patch > configure? just add the patch. The autoreconf sequence is

Processed: bug 1075814 is forwarded to https://github.com/PlotPyStack/PlotPy/issues/17

Processing commands for cont...@bugs.debian.org: > forwarded 1075814 https://github.com/PlotPyStack/PlotPy/issues/17 Bug #1075814 [src:plotpy] plotpy: Fails to build on arm64 Set Bug forwarded-to-address to 'https://github.com/PlotPyStack/PlotPy/issues/17'. > thanks Stopping processing here.

Bug#1075978: rmpi: FTBFS on 32 bit architectures: configure: error: "Cannot find mpi.h header file"

Adrian, Will the patch to configure.ac, with the build system as it is, ensure autoconf is called or should I do that manually and hence also patch configure? Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1076017: purity-off: autopkgtest regression on arm64: output keeps growing

Source: purity-off Version: 0-6 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, on arm64 it recently started to fill the entire disk with its output file in $AUTOPKGTEST_TMP (in testing and unstable,

Bug#1074519: marked as done (graph-tool: autopkgtest failure with Python 3.12)

Your message dated Tue, 09 Jul 2024 14:49:03 + with message-id and subject line Bug#1074519: fixed in graph-tool 2.71+ds-2 has caused the Debian Bug report #1074519, regarding graph-tool: autopkgtest failure with Python 3.12 to be marked as done. This means that you claim that the problem

Processed: Bug#1074519 marked as pending in graph-tool

Processing control commands: > tag -1 pending Bug #1074519 [src:graph-tool] graph-tool: autopkgtest failure with Python 3.12 Added tag(s) pending. -- 1074519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074519 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug#1074519 marked as pending in graph-tool

Processing control commands: > tag -1 pending Bug #1074519 [src:graph-tool] graph-tool: autopkgtest failure with Python 3.12 Ignoring request to alter tags of bug #1074519 to the same tags previously set -- 1074519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074519 Debian Bug Tracking

Bug#1074519: marked as pending in graph-tool

Control: tag -1 pending Hello, Bug #1074519 in graph-tool reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1074519: marked as pending in graph-tool

Control: tag -1 pending Hello, Bug #1074519 in graph-tool reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1074742: marked as done (org-roam: FTBFS: make[2]: *** [Makefile:84: texi] Error 255)

Your message dated Tue, 09 Jul 2024 13:35:07 + with message-id and subject line Bug#1074742: fixed in org-roam 2.2.2-2 has caused the Debian Bug report #1074742, regarding org-roam: FTBFS: make[2]: *** [Makefile:84: texi] Error 255 to be marked as done. This means that you claim that the

Bug#1072847: fixed in lacme 0.8.3-1

Hi Guilhem, On Fri, Jul 05, 2024 at 11:15:31AM +0200, Guilhem Moulin wrote: > Hi Sakari, > > On Fri, 05 Jul 2024 at 08:23:56 +, Sakari Ailus wrote: > > The removal of the intermediate certificates (or not including the current > > ones) however is an issue as the server using the issued

Bug#1071952: marked as done (purple-lurch: FTBFS against libgcrypt 1.11)

Your message dated Tue, 09 Jul 2024 12:52:04 + with message-id and subject line Bug#1071952: fixed in purple-lurch 0.7.0-2.1 has caused the Debian Bug report #1071952, regarding purple-lurch: FTBFS against libgcrypt 1.11 to be marked as done. This means that you claim that the problem has

Bug#1066710: marked as done (purple-lurch: FTBFS: ./test/test_lurch_util.c:69:5: error: implicit declaration of function ‘lurch_util_axc_log_func’ [-Werror=implicit-function-declaration])

Your message dated Tue, 09 Jul 2024 12:52:04 + with message-id and subject line Bug#1066710: fixed in purple-lurch 0.7.0-2.1 has caused the Debian Bug report #1066710, regarding purple-lurch: FTBFS: ./test/test_lurch_util.c:69:5: error: implicit declaration of function

Processed: Re: Bug#1069407: mercurial: FTBFS on arm64: dh_auto_test: error: make -j4 check PYTHON=python3 "TESTFLAGS=--verbose --timeout 1800 --jobs 4 --blacklist /<>/debian/mercurial.tes

Processing control commands: > forcemerge 1052811 1074678 1069407 Bug #1052811 [src:mercurial] mercurial: test-http-bad-server.t intermittent failure Bug #1052811 [src:mercurial] mercurial: test-http-bad-server.t intermittent failure Marked as found in versions mercurial/6.7.2-1 and

Bug#1069407: mercurial: FTBFS on arm64: dh_auto_test: error: make -j4 check PYTHON=python3 "TESTFLAGS=--verbose --timeout 1800 --jobs 4 --blacklist /<>/debian/mercurial.test_blacklist" re

Control: forcemerge 1052811 1074678 1069407 On Sat, Apr 20, 2024 at 14:08:55 +0200, Lucas Nussbaum wrote: > Source: mercurial > Version: 6.7.2-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64 >

Bug#1076008: qemu-system-ppc: Missing NIC ?

09.07.2024 15:29, Christian Marillat пишет: On 09 juil. 2024 15:25, Michael Tokarev wrote: 09.07.2024 15:23, Christian Marillat wrote: On 09 juil. 2024 13:18, Michael Tokarev wrote: [...] I don't know what "NIC support is missing" means. Qemu can't be built without support for

Bug#1076008: qemu-system-ppc: Missing NIC ?

On 09 juil. 2024 15:25, Michael Tokarev wrote: > 09.07.2024 15:23, Christian Marillat wrote: >> On 09 juil. 2024 13:18, Michael Tokarev wrote: >> [...] >> > I don't know what "NIC support is missing" means. Qemu can't be built > without support for networking. The -nic option is

Bug#1063190: [Pkg-owncloud-maintainers] Bug#1063190: closing 1063190 [owncloud-client+t64 RC]

Hey, Agustin Martin wrote on 09/07/2024 at 09:48:14+0200: > On Fri, Jun 28, 2024 at 12:58:52PM +0200, Andreas Beckmann wrote: >> Control: found -1 5.2.1.13040+dfsg-2 >> >> On Tue, 25 Jun 2024 15:36:40 +0200 Agustin Martin >> wrote: >> > On Mon, Jun 10, 2024 at 11:46:20PM +0200, Pierre-Elliott

Bug#1073312: marked as done (libxslt: FTBFS: extensions.c:392:33: error: implicit declaration of function ‘getenv’ [-Werror=implicit-function-declaration])

Your message dated Tue, 09 Jul 2024 12:24:23 + with message-id and subject line Bug#1073312: fixed in libxslt 1.1.35-1.1 has caused the Debian Bug report #1073312, regarding libxslt: FTBFS: extensions.c:392:33: error: implicit declaration of function ‘getenv’

Bug#1076008: qemu-system-ppc: Missing NIC ?

On 09 juil. 2024 13:37, Michael Tokarev wrote: > 09.07.2024 13:18, Michael Tokarev wrote: > ..>> -net nic,model=help should display a list of available network devices. >> If you want this to happen, I suggest you to open bug report in the >> upstream qemu issue tracker.  I definitely wont add

Bug#1071937: marked as done (libxslt: FTBFS against libgcrypt 1.11)

Your message dated Tue, 09 Jul 2024 12:24:23 + with message-id and subject line Bug#1071937: fixed in libxslt 1.1.35-1.1 has caused the Debian Bug report #1071937, regarding libxslt: FTBFS against libgcrypt 1.11 to be marked as done. This means that you claim that the problem has been dealt

Bug#1076008: qemu-system-ppc: Missing NIC ?

09.07.2024 15:23, Christian Marillat wrote: On 09 juil. 2024 13:18, Michael Tokarev wrote: [...] I don't know what "NIC support is missing" means. Qemu can't be built without support for networking. The -nic option is obsolete for a long time, that's true, but it works still. Missing

Bug#1076008: qemu-system-ppc: Missing NIC ?

On 09 juil. 2024 13:18, Michael Tokarev wrote: [...] >>> I don't know what "NIC support is missing" means. Qemu can't be built >>> without support for networking. The -nic option is obsolete for a long >>> time, that's true, but it works still. >> Missing network card support. > > You gave no

Bug#1072947: marked as done (dropbear: autopkgtest remote-unlocking is flaky)

Your message dated Tue, 09 Jul 2024 12:19:19 + with message-id and subject line Bug#1072947: fixed in dropbear 2024.85-3 has caused the Debian Bug report #1072947, regarding dropbear: autopkgtest remote-unlocking is flaky to be marked as done. This means that you claim that the problem has

Bug#1073465: marked as done (python-wsgi-intercept: FTBFS: tests failed)

Your message dated Tue, 09 Jul 2024 11:50:17 + with message-id and subject line Bug#1073465: fixed in python-wsgi-intercept 1.13.0-1 has caused the Debian Bug report #1073465, regarding python-wsgi-intercept: FTBFS: tests failed to be marked as done. This means that you claim that the

Bug#1073465: marked as pending in python-wsgi-intercept

Control: tag -1 pending Hello, Bug #1073465 in python-wsgi-intercept reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1073465 marked as pending in python-wsgi-intercept

Processing control commands: > tag -1 pending Bug #1073465 [src:python-wsgi-intercept] python-wsgi-intercept: FTBFS: tests failed Added tag(s) pending. -- 1073465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1071933: marked as done (libccrtp: FTBFS against libgcrypt 1.11)

Your message dated Tue, 09 Jul 2024 11:34:11 + with message-id and subject line Bug#1071933: fixed in libccrtp 2.0.9-4.1 has caused the Debian Bug report #1071933, regarding libccrtp: FTBFS against libgcrypt 1.11 to be marked as done. This means that you claim that the problem has been dealt

Processed: libccrtp: diff for NMU version 2.0.9-4.1

Processing control commands: > tags 1071933 + patch Bug #1071933 [src:libccrtp] libccrtp: FTBFS against libgcrypt 1.11 Added tag(s) patch. > tags 1071933 + pending Bug #1071933 [src:libccrtp] libccrtp: FTBFS against libgcrypt 1.11 Added tag(s) pending. -- 1071933:

Bug#1071933: libccrtp: diff for NMU version 2.0.9-4.1

Control: tags 1071933 + patch Control: tags 1071933 + pending Dear maintainer, I've prepared an NMU for libccrtp (versioned as 2.0.9-4.1) and uploaded it to unstable. Regards. diff -Nru libccrtp-2.0.9/debian/changelog libccrtp-2.0.9/debian/changelog --- libccrtp-2.0.9/debian/changelog

Bug#1076008: qemu-system-ppc: Missing NIC ?

09.07.2024 13:18, Michael Tokarev wrote: ..>> -net nic,model=help should display a list of available network devices. If you want this to happen, I suggest you to open bug report in the upstream qemu issue tracker.  I definitely wont add debian-specific code to display help for an obsolete

Bug#1074739: marked as pending in hisat2

Control: tag -1 pending Hello, Bug #1074739 in hisat2 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1074739 marked as pending in hisat2

Processing control commands: > tag -1 pending Bug #1074739 [src:hisat2] hisat2: FTBFS: make[1]: *** [debian/rules:39: override_dh_auto_build] Error 1 Added tag(s) pending. -- 1074739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074739 Debian Bug Tracking System Contact

Bug#1057282: linux-image-6.5.0-0.deb12.1-arm64: arm64 kernel upgrade makes systems unresponsive

Hi, On 08-07-2024 10:07 p.m., Salvatore Bonaccorso wrote: If you think it worth enough knowing if either is the case, I can install the backports kernel again on the arm64 hosts, but obviously that will be annoying for us. Please let me know if I should pursue this (I would be expecting a bit

Bug#1073316: marked as done (manaplus: FTBFS: resources/wallpaper.cpp:156:24: error: ‘time’ was not declared in this scope)

Your message dated Tue, 09 Jul 2024 10:21:24 + with message-id and subject line Bug#1073316: fixed in manaplus 2.1.3.17-8 has caused the Debian Bug report #1073316, regarding manaplus: FTBFS: resources/wallpaper.cpp:156:24: error: ‘time’ was not declared in this scope to be marked as done.

Bug#1076008: qemu-system-ppc: Missing NIC ?

09.07.2024 13:11, Christian Marillat wrote: On 09 juil. 2024 12:53, Michael Tokarev wrote: Control: tag -1 + moreinfo unreproducible 09.07.2024 12:09, Christian Marillat wrote: Package: qemu-system-ppc Version: 1:9.0.1+ds-1 Severity: serious Dear Maintainer, My working configuration with

Bug#1076008: qemu-system-ppc: Missing NIC ?

On 09 juil. 2024 12:53, Michael Tokarev wrote: > Control: tag -1 + moreinfo unreproducible > > 09.07.2024 12:09, Christian Marillat wrote: >> Package: qemu-system-ppc >> Version: 1:9.0.1+ds-1 >> Severity: serious >> Dear Maintainer, >> My working configuration with 1:8.2.5+ds-2 was: >> , >>

Processed: r-bioc-cwl: build-deps are satisfiable now

Processing commands for cont...@bugs.debian.org: > notfound 1071884 1.18.0+ds-2 Bug #1071884 {Done: "Michael R. Crusoe" } [src:r-bioc-rcwl] r-bioc-rcwl: FTBFS: unsatisfiable build-dependencies No longer marked as found in versions r-bioc-rcwl/1.18.0+ds-2. > End of message, stopping processing

Processed: Re: Bug#1076008: qemu-system-ppc: Missing NIC ?

Processing control commands: > tag -1 + moreinfo unreproducible Bug #1076008 [qemu-system-ppc] qemu-system-ppc: Missing NIC ? Added tag(s) moreinfo and unreproducible. -- 1076008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076008 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1076008: qemu-system-ppc: Missing NIC ?

Control: tag -1 + moreinfo unreproducible 09.07.2024 12:09, Christian Marillat wrote: Package: qemu-system-ppc Version: 1:9.0.1+ds-1 Severity: serious Dear Maintainer, My working configuration with 1:8.2.5+ds-2 was: , | -net nic,macaddr=52:54:00:12:34:67,model=virtio -net tap ` Now

Bug#1073460: marked as done (python-zake: FTBFS: tests failed)

Your message dated Tue, 09 Jul 2024 09:49:25 + with message-id and subject line Bug#1073460: fixed in python-zake 0.2.2-7 has caused the Debian Bug report #1073460, regarding python-zake: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt

Bug#1076008: qemu-system-ppc: Missing NIC ?

Package: qemu-system-ppc Version: 1:9.0.1+ds-1 Severity: serious Dear Maintainer, My working configuration with 1:8.2.5+ds-2 was: , | -net nic,macaddr=52:54:00:12:34:67,model=virtio -net tap ` Now with 1:9.0.1+ds-1 qemu-system-ppc64 doesn't start. Apparently NIC support is missing:

Bug#1074752: marked as done (cura: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2)

Your message dated Tue, 09 Jul 2024 08:49:03 + with message-id and subject line Bug#1074752: fixed in uranium 5.0.0-5 has caused the Debian Bug report #1074752, regarding cura: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code

Bug#1074239: marked as done (cura: Cura fails to start)

Your message dated Tue, 09 Jul 2024 08:49:03 + with message-id and subject line Bug#1074239: fixed in uranium 5.0.0-5 has caused the Debian Bug report #1074239, regarding cura: Cura fails to start to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1073458: marked as done (python-observabilityclient: FTBFS: tests failed)

Your message dated Tue, 09 Jul 2024 08:40:15 + with message-id and subject line Bug#1073458: fixed in python-observabilityclient 0.1.1-3 has caused the Debian Bug report #1073458, regarding python-observabilityclient: FTBFS: tests failed to be marked as done. This means that you claim that

Bug#1073457: marked as done (python-requests-mock: FTBFS: tests failed)

Your message dated Tue, 09 Jul 2024 08:40:27 + with message-id and subject line Bug#1073457: fixed in python-requests-mock 1.12.1-1 has caused the Debian Bug report #1073457, regarding python-requests-mock: FTBFS: tests failed to be marked as done. This means that you claim that the problem

Bug#1073381: marked as done (git-build-recipe: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13)

Your message dated Tue, 09 Jul 2024 08:40:38 + with message-id and subject line Bug#1073381: fixed in python-testtools 2.7.2-1 has caused the Debian Bug report #1073381, regarding git-build-recipe: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13 to

Bug#1073460: marked as pending in python-zake

Control: tag -1 pending Hello, Bug #1073460 in python-zake reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1073460 marked as pending in python-zake

Processing control commands: > tag -1 pending Bug #1073460 [src:python-zake] python-zake: FTBFS: tests failed Added tag(s) pending. -- 1073460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073460 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug#1073458 marked as pending in python-observabilityclient

Processing control commands: > tag -1 pending Bug #1073458 [src:python-observabilityclient] python-observabilityclient: FTBFS: tests failed Added tag(s) pending. -- 1073458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073458 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1073458: marked as pending in python-observabilityclient

Control: tag -1 pending Hello, Bug #1073458 in python-observabilityclient reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1073457 marked as pending in python-requests-mock

Processing control commands: > tag -1 pending Bug #1073457 [src:python-requests-mock] python-requests-mock: FTBFS: tests failed Added tag(s) pending. -- 1073457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1073457: marked as pending in python-requests-mock

Control: tag -1 pending Hello, Bug #1073457 in python-requests-mock reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1073381 marked as pending in python-testtools

Processing control commands: > tag -1 pending Bug #1073381 [python3-testtools] git-build-recipe: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13 Added tag(s) pending. -- 1073381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073381 Debian Bug

Bug#1073381: marked as pending in python-testtools

Control: tag -1 pending Hello, Bug #1073381 in python-testtools reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1063190: closing 1063190 [owncloud-client+t64 RC]

On Fri, Jun 28, 2024 at 12:58:52PM +0200, Andreas Beckmann wrote: > Control: found -1 5.2.1.13040+dfsg-2 > > On Tue, 25 Jun 2024 15:36:40 +0200 Agustin Martin > wrote: > > On Mon, Jun 10, 2024 at 11:46:20PM +0200, Pierre-Elliott Bécue wrote: > > > close 1063190 > thanks > > > > Hi,

Bug#1061241: endless-sky: debian/copyright incomplete

Hey, We fixed the copyright file upstream to follow the Debian specification. This fix is present in the latest stable release, 0.10.8. -- tibetiroka

Bug#1074250: ifupdown2: PR offered to maintainers for merge

Package: ifupdown2 Version: 3.0.0-1.1 Followup-For: Bug #1074250 I found this bug yesterday on my systems, it was reported upstream on 4-4-2024, maintainer asked for a pull request so it could be patched but it was never offered. The maintainer just got a pull request by me to patch this issue.

Bug#1069621: rust-event-listener: no-default-features autopkgtest fails

On 09/07/2024 02:02, Matthias Geiger wrote: > On 08.07.24 18:45, Jonas Smedegaard wrote: >> Quoting Matthias Geiger (2024-07-07 11:21:07) >>> On 07.07.24 10:10, Jonas Smedegaard wrote: >>> [...] [...] >>> isahc requires sluice only for some pipe functionality in two files. >>> Since patching