Bug#1056852: python-cassandra-driver: ftbfs with cython 3.0.x
Control: tags -1 help Control: tags -1 moreinfo Hi, I tried building the current status in Git and realised that the suggested patch is not sufficient. I decided to relax the versioned dependency from cython[1] which at least let the configure and build step pass. Unfortunately the cython3-legacy build dependency led to 5 errors and thus I tried cython3 instead which only leads to 2 errrors which you can hopefully reproduce in a couple of minutes in Salsa CI[2] (I'm going AFK instantly so can not check any more). May be it is appropriate to skip those two tests? I'll leave this decision to you since I do not know this package sufficiently enough. Hope this helps Andreas. [1] https://salsa.debian.org/python-team/packages/python-cassandra-driver/-/blob/debian/master/debian/patches/0006-relax_vesioned_cython_dependency.patch?ref_type=heads [2] https://salsa.debian.org/python-team/packages/python-cassandra-driver/-/pipelines/631074 -- http://fam-tille.de
Processed: Re: python-cassandra-driver: ftbfs with cython 3.0.x
Processing control commands: > tags -1 help Bug #1056852 [src:python-cassandra-driver] python-cassandra-driver: ftbfs with cython 3.0.x Added tag(s) help. > tags -1 moreinfo Bug #1056852 [src:python-cassandra-driver] python-cassandra-driver: ftbfs with cython 3.0.x Added tag(s) moreinfo. -- 1056852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060143: gnss-sdr ftbfs in unstable
control: fixed -1 0.0.19-1
control: close -1
thanks
On Sat, 6 Jan 2024 12:19:35 +0100 Matthias Klose wrote:
Package: src:gnss-sdr
Version: 0.0.18-2
Severity: serious
Tags: sid trixie ftbfs
gnss-sdr ftbfs in unstable:
[...]
In file included from /usr/include/gnuradio/basic_block.h:15,
from /usr/include/gnuradio/hier_block2.h:15,
from /usr/include/gnuradio/top_block.h:15,
from
/home/packages/tmp/gnss-sdr-0.0.18/src/core/interfaces/gnss_block_interface.h:26,
from
/home/packages/tmp/gnss-sdr-0.0.18/src/algorithms/data_type_adapter/gnuradio_blocks/interleaved_byte_to_complex_byte.h:20,
from
/home/packages/tmp/gnss-sdr-0.0.18/src/algorithms/data_type_adapter/gnuradio_blocks/interleaved_byte_to_complex_byte.cc:18:
/usr/include/gnuradio/io_signature.h:194:73: error: ‘string_view’ is not
a member of ‘std’
194 | struct GR_RUNTIME_API fmt::formatter :
formatter {
|
^~~
/usr/include/gnuradio/io_signature.h:194:73: note: ‘std::string_view’ is
only available from C++17 onwards
/usr/include/gnuradio/io_signature.h:194:73: error: ‘string_view’ is not
a member of ‘std’
/usr/include/gnuradio/io_signature.h:194:73: note: ‘std::string_view’ is
only available from C++17 onwards
/usr/include/gnuradio/io_signature.h:194:84: error: template argument 1
is invalid
194 | struct GR_RUNTIME_API fmt::formatter :
formatter {
|
^
OpenPGP_signature.asc
Description: OpenPGP digital signature
Processed: Re: gnss-sdr ftbfs in unstable
Processing control commands:
> fixed -1 0.0.19-1
Bug #1060143 {Done: Adrian Bunk } [src:gnss-sdr] gnss-sdr
ftbfs in unstable
Ignoring request to alter fixed versions of bug #1060143 to the same values
previously set
> close -1
Bug #1060143 {Done: Adrian Bunk } [src:gnss-sdr] gnss-sdr
ftbfs in unstable
Bug 1060143 is already marked as done; not doing anything.
--
1060143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1042250: marked as done (bup: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)
Your message dated Sat, 27 Jan 2024 05:34:11 +
with message-id
and subject line Bug#1042250: fixed in bup 0.33.3-1
has caused the Debian Bug report #1042250,
regarding bup: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8
--verbose" VERBOSE=1 returned exit code 2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1042250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bup
Version: 0.33.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir test/tmp
> ./pylint
> ./pylint: doing nothing (pylint not found)
> ! bup version # Ensure we can't test the local bup (cf. dev/shadow-bin)
> error: something ran "bup"; bup imposter intentionally failing
> ./bup features
> bup 0.33.2
> Source 0dc9aa2a90ad06d57df2ede736587746135de30f 2023-07-01 18:52:45 -0400
> Python: 3.11.4
> Command line editing (e.g. bup ftp): yes
> Saving and restoring POSIX ACLs: yes
> Saving and restoring extended attributes (xattrs): yes
> if test yes = "$(dev/python -c 'import xdist; print("yes")' 2>/dev/null)";
> then \
>(set -x; ./pytest -n8;) \
> else \
> (set -x; ./pytest;) \
> fi
> + ./pytest -n8
> = test session starts
> ==
> platform linux -- Python 3.11.4, pytest-7.4.0, pluggy-1.2.0 --
> /<>/dev/bup-python
> cachedir: .pytest_cache
> rootdir: /<>
> configfile: pytest.ini
> testpaths: test/int, test/ext
> plugins: xdist-3.3.1
> created: 8/8 workers
> 8 workers [128 items]
>
> scheduling tests via LoadScheduling
>
> test/ext/test-meta-acls::
> test/ext/test-ls::
> test/ext/test-index-check-device::
> test/ext/test-help::
> test/ext/test-drecurse::
> test/ext/test-cat-file::
> test/ext/test_get.py::test_get[get-pick_force]
> test/ext/test_get.py::test_get[get-replace]
> [gw5] [ 0%] SKIPPED test/ext/test-index-check-device::
> test/ext/test-index-clear::
> [gw4] [ 1%] FAILED test/ext/test-help::
> test/ext/test-import-duplicity::
> [gw4] [ 2%] SKIPPED test/ext/test-import-duplicity::
> test/ext/test-import-rdiff-backup::
> [gw4] [ 3%] SKIPPED test/ext/test-import-rdiff-backup::
> test/ext/test-index::
> [gw3] [ 3%] PASSED test/ext/test-drecurse::
> test/ext/test-fsck::
> [gw2] [ 4%] PASSED test/ext/test-cat-file::
> test/ext/test-command-without-init-fails::
> [gw7] [ 5%] PASSED test/ext/test-meta-acls::
> test/ext/test-misc::
> [gw2] [ 6%] PASSED test/ext/test-command-without-init-fails::
> test/ext/test-comparative-split-join::
> [gw2] [ 7%] SKIPPED test/ext/test-comparative-split-join::
> test/ext/test-compression::
> [gw5] [ 7%] PASSED test/ext/test-index-clear::
> test/ext/test-index-save-type-change::
> [gw2] [ 8%] PASSED test/ext/test-compression::
> test/ext/test-rm-between-index-and-save::
> [gw6] [ 9%] PASSED test/ext/test-ls::
> test/ext/test-ls-remote::
> [gw5] [ 10%] PASSED test/ext/test-index-save-type-change::
> test/ext/test-list-idx::
> [gw5] [ 10%] PASSED test/ext/test-list-idx::
> test/ext/test-save-restore::
> [gw3] [ 11%] PASSED test/ext/test-fsck::
> test/ext/test-fuse::
> [gw3] [ 12%] PASSED test/ext/test-fuse::
> test/ext/test-gc::
> [gw7] [ 13%] PASSED test/ext/test-misc::
> test/ext/test-on::
> [gw7] [ 14%] PASSED test/ext/test-on::
> test/ext/test-packsizelimit::
> [gw2] [ 14%] PASSED test/ext/test-rm-between-index-and-save::
> test/ext/test-save-creates-no-unrefs::
> [gw7] [ 15%] PASSED test/ext/test-packsizelimit::
> test/ext/test-tz::
> [gw7] [ 16%] PASSED test/ext/test-tz::
> test/ext/test-web::
> [gw5] [ 17%] PASSED test/ext/test-save-restore::
> test/ext/test-save-restore-excludes::
> [gw7] [ 17%] SKIPPED test/ext/test-web::
> test/ext/test-xdev::
> [gw7] [ 18%] SKIPPED test/ext/test-xdev::
> test/ext/test_argv.py::test_argv
> [gw2] [ 19%] PASSED test/ext/test-save-creates-no-unrefs::
> test/ext/test-save-data-race::
> [gw2] [ 20%] PASSED test/ext/test-save-data-race::
> test/ext/test-save-errors::
> [gw7] [ 21%] PASSED test/ext/test_argv.py::test_argv
> test/ext/test_ftp.py::test_ftp
> [gw6] [ 21%] PASSED test/ext/test-ls-remote::
> test/ext/test-main::
> [gw6] [ 22%] PASSED test/ext/test-main::
> test/ext/test-meta::
> [gw7] [ 23%] PASSED test/ext/test_ftp.py::test_ftp
> test/ext/test_prune_older.py::test_prune_older
Bug#1054644: marked as done (xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices)
Your message dated Sat, 27 Jan 2024 05:54:08 +0100 with message-id and subject line xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices has caused the Debian Bug report #1054644, regarding xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xfsprogs-udeb Version: 6.5.0-1 Severity: serious User: debian...@lists.debian.org Usertags: openqa While doing openQA testing of Debian-Installer, I notice that XFS installs started failing a few days ago, and comparing the versions of udebs that changed between success and failure, the only likely candidate is xfsprogs-udeb, which has a version of 6.4.0-1 in the last working test, and 6.5.0-1 in the first failing one. I've also built the latest D-I with 6.4.0-1, and that restores it to a working condition. I note that if one runs e.g.: grub-probe -d /dev/vda1 at the moment of failure, the XFS filesystem is not recognised (despite being mounted as XFS at that moment). Could this be related to #1051543? I'll try testing D-I while using the patch from that bug, to see if that helps. Cheers, Phil. --- End Message --- --- Begin Message --- Version: grub2/2.12-1--- End Message ---
Bug#1059424: marked as done (xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices)
Your message dated Sat, 27 Jan 2024 05:54:08 +0100 with message-id and subject line xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices has caused the Debian Bug report #1059424, regarding xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1059424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xfsprogs-udeb Version: 6.5.0-1 Severity: serious User: debian...@lists.debian.org Usertags: openqa While doing openQA testing of Debian-Installer, I notice that XFS installs started failing a few days ago, and comparing the versions of udebs that changed between success and failure, the only likely candidate is xfsprogs-udeb, which has a version of 6.4.0-1 in the last working test, and 6.5.0-1 in the first failing one. I've also built the latest D-I with 6.4.0-1, and that restores it to a working condition. I note that if one runs e.g.: grub-probe -d /dev/vda1 at the moment of failure, the XFS filesystem is not recognised (despite being mounted as XFS at that moment). Could this be related to #1051543? I'll try testing D-I while using the patch from that bug, to see if that helps. Cheers, Phil. --- End Message --- --- Begin Message --- Version: grub2/2.12-1--- End Message ---
Bug#1060961: clapper: FTBFS: make: *** [debian/rules:6: binary] Error 25
Hi, On Tue, 16 Jan 2024 20:43:11 +0100 Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build on > amd64. thank you for your bug! > Couldn't find include 'GObject-2.0.gir' (search path: '['/usr/share/gir-1.0', > '/usr/lib/x86_64-linux-gnu/gir-1.0', > '/<>/debian/.debhelper/generated/_source/home/.local/share/gir-1.0', > 'gir-1.0', '/usr/local/share/gir-1.0', '/usr/share/gir-1.0', > '/usr/lib/x86_64-linux-gnu/gir-1.0', '/usr/share/gir-1.0', > '/usr/share/gir-1.0']') I'm unable to reproduce your bug in unstable. The day before the date from your build log, a disruptive upload of gobject-introspection happened to unstable and there have been more uploads of gobject-introspection since then. Maybe the issue is fixed now? Would you mind re-trying the build? I am building the package on arm64 and maybe that makes a difference? In any case, I'm not able to reproduce it. Thanks! cheers, josch signature.asc Description: signature
Bug#1060032: marked as done (libcircle-fe-term-perl: test failures with libtickit-widgets-perl 0.39-1)
Your message dated Sat, 27 Jan 2024 03:27:34 + with message-id and subject line Bug#1060032: fixed in libcircle-fe-term-perl 0.240250-1 has caused the Debian Bug report #1060032, regarding libcircle-fe-term-perl: test failures with libtickit-widgets-perl 0.39-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1060032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libcircle-fe-term-perl Version: 0.232470-1 Severity: serious Tags: upstream ftbfs trixie sid Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 libcircle-fe-term-perl has test failures with libtickit-widgets-perl 0.39-1 dh_auto_test /usr/bin/perl Build test --verbose 1 # Failed test 'use Circle::FE::Term::Widget::Entry;' # at t/00use.t line 15. # Tried to use 'Circle::FE::Term::Widget::Entry'. # Error: Cannot add a new method to an already-sealed class at /usr/share/perl5/Tickit/Style.pm line 246. # BEGIN failed--compilation aborted at /build/libcircle-fe-term-perl-0.232470/blib/lib/Circle/FE/Term/Widget/Entry.pm line 174. # Compilation failed in require at t/00use.t line 15. # BEGIN failed--compilation aborted at t/00use.t line 15. # Looks like you failed 1 test of 7. t/00use.t .. ok 1 - use Circle::FE::Term; ok 2 - use Circle::FE::Term::Tab; ok 3 - use Circle::FE::Term::Ribbon; ok 4 - use Circle::FE::Term::Widget::Box; ok 5 - use Circle::FE::Term::Widget::Scroller; ok 6 - use Circle::FE::Term::Widget::Label; not ok 7 - use Circle::FE::Term::Widget::Entry; 1..7 Dubious, test returned 1 (wstat 256, 0x100) Failed 1/7 subtests Test Summary Report - --- t/00use.t (Wstat: 256 (exited 1) Tests: 7 Failed: 1) Failed test: 7 Non-zero exit status: 1 Files=1, Tests=7, 0 wallclock secs ( 0.01 usr 0.01 sys + 0.17 cusr 0.02 csys = 0.21 CPU) Result: FAIL Cf. https://ci.debian.net/packages/libc/libcircle-fe-term-perl/testing/amd64/41469556/ Cheers, gregor -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmWXZPJfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgYkiQ/7BWudMEVMYzyVW8KyC18XzVOioQ+8h++5b8rG/FLdX+bcPZUfKr4S9NAX iaC4M9xoRmdPKSmDW4XG6AiJMcDGzwIjoMmogEEcjmV4UmkksFcMtZXTdZ3D8zkz Nwsod/ZGt4/gnSBFkNw5rcxApFlrWQKcUHF68yoQh+p6JbExyyIFOL/5+Hr38I+e CEOYRWe5NPZxcMrd1BI4ab/T2N5TnnWSVUN7qTjVozbS7sy9RW5xeH4PwEkJxJB7 VzTmc/iRzxWWkel8XLIfQpmx/MXTuKqB9A/UJsdhoS+WKQ4bivsEy9QBSDz2lAVB N6nPJixJFq7VOjJqWBFmCNJr/WhYNllVccxh4pmzdpIip7Tf7Weqvu0PKE/8JisT gnN25f9o2+doEy6gkW3LdjxR9jGFcBcXotGAg1jbh5rk5x/qgU2jA8BEhxBIRKgb dOGPz/sSuJYdhhXzH3yOs+4n1LZi17eChChMSfsv5DytS63j5xvqyYx/51YWrMgQ AfdMQUfHKrQo4ezwnt3I+QY4nOtGjtgAI7F88UzbxPkxtehCGiHHWX+MmYs4Wd2n X6vTDsAQIdDZsq1V3PPW5MzsA83QIu3NRwuxRSf5HjQSG/mPrLO2TD6U2aXIhM3+ WU8d91C692S3uQ7UuKh2govUN+SDvPlDniMyUm+YN1LSkdG81iM= =qvl2 -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: libcircle-fe-term-perl Source-Version: 0.240250-1 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libcircle-fe-term-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libcircle-fe-term-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 27 Jan 2024 03:49:29 +0100 Source: libcircle-fe-term-perl Architecture: source Version: 0.240250-1 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 1060032 Changes: libcircle-fe-term-perl (0.240250-1) unstable; urgency=medium . * Import upstream version 0.240250. Fixes "test failures with libtickit-widgets-perl 0.39-1" (Closes: #1060032) * Update years of upstream and packaging copyright. * Make (test) dependency on libobject-pad-perl versioned. * Drop unneeded version constraints from (build) dependencies. Checksums-Sha1: 09d04962130ea04ce0c28a10e60fffb083bf0d87
Bug#1061591: rhsrvany: tests can fail on ci.debian.net due to wine32 installation
package: src:rhsrvany version: 1.1-2 severity: serious tag: patch runsrvany64 and runpnpwait64 autopkgtests can fail on amd64 on ci.debian.net because of foreign arch wine32 installability issues [0]. This currently prevents wine from migrating to testing [1]. The attached patch solves the problem by removing wine32 install from the scripts. wine32 isn't needed since the tests run correctly on amd64 when wine and wine64 are installed, which is the case for ci.debian.net. Best wishes, Mike [0] https://ci.debian.net/packages/r/rhsrvany/testing/amd64/42392786/ [1] https://qa.debian.org/excuses.php?package=wine --- a/debian/tests/runsrvany64 +++ b/debian/tests/runsrvany64 @@ -1,5 +1,4 @@ #!/bin/sh set -e -dpkg --add-architecture i386 && apt-get update && apt-get -y install wine32 wine /usr/share/virt-tools/rhsrvany.exe install wine /usr/share/virt-tools/rhsrvany.exe uninstall --- a/debian/tests/runpnpwait64 +++ b/debian/tests/runpnpwait64 @@ -1,4 +1,3 @@ #!/bin/sh set -e -dpkg --add-architecture i386 && apt-get update && apt-get -y install wine32 wine /usr/share/virt-tools/pnp_wait.exe
Bug#1061567: marked as done (gnome-builder FTBFS: redefinition of glib_autoptr_*_GtkStackPage)
Your message dated Fri, 26 Jan 2024 23:34:19 + with message-id and subject line Bug#1061567: fixed in gnome-builder 45.0-2 has caused the Debian Bug report #1061567, regarding gnome-builder FTBFS: redefinition of glib_autoptr_*_GtkStackPage to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1061567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-builder Version: 45.0-1 Severity: serious Tags: ftbfs patch Forwarded: https://gitlab.gnome.org/GNOME/gnome-builder/-/commit/7aaaecefc2ea8a37eaeae8b4d726d119d4eb8fa3 https://buildd.debian.org/status/fetch.php?pkg=gnome-builder=riscv64=45.0-1%2Bb2=1706281444=0 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnome-builder.html ... FAILED: src/libide/tweaks/libide-tweaks-45.a.p/ide-tweaks-window.c.o cc -Isrc/libide/tweaks/libide-tweaks-45.a.p -Isrc/libide/tweaks -I../src/libide/tweaks -Isrc/libide/core -I../src/libide/core -Isrc/libide/io -I../src/libide/io -Isrc/libide/threading -I../src/libide/threading -Isrc/libide/search -I../src/libide/search -Isrc/libide/gtk -I../src/libide/gtk -Isrc/libide/plugins -I../src/libide/plugins -I/usr/include/glib-2.0 -I/usr/lib/riscv64-linux-gnu/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gtk-4.0 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/riscv64-linux-gnu -I/usr/include/webp -I/usr/include/graphene-1.0 -I/usr/lib/riscv64-linux-gnu/graphene-1.0/include -I/usr/include/libadwaita-1 -I/usr/include/appstream -I/usr/include/libdex-1 -I/usr/include/libpeas-2 -I/usr/include/gio-unix-2.0 -I/usr/include/gtksourceview-5 -I/usr/include/libxml2 -I/<>/obj-riscv64-linux-gnu -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=gnu11 -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_76 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_76 -DGDK_VERSION_MIN_REQUIRED=GDK_VERSION_4_10 -DGDK_VERSION_MAX_ALLOWED=GDK_VERSION_4_10 -DGDK_DISABLE_DEPRECATION_WARNINGS -DADW_VERSION_MIN_REQUIRED=ADW_VERSION_1_4 -DADW_VERSION_MAX_ALLOWED=ADW_VERSION_1_4 -DGTK_SOURCE_VERSION_MIN_REQUIRED=GTK_SOURCE_VERSION_5_8 -DGTK_SOURCE_VERSION_MAX_ALLOWED=GTK_SOURCE_VERSION_5_8 -Wcast-align -Wdeclaration-after-statement -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=implicit -Werror=implicit-function-declaration -Werror=incompatible-pointer-types -Werror=init-self -Werror=int-conversion -Werror=int-to-pointer-cast -Werror=main -Werror=misleading-indentation -Werror=missing-braces -Werror=missing-include-dirs -Werror=nonnull -Werror=overflow -Werror=pointer-arith -Werror=pointer-to-int-cast -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=shadow -Werror=trigraphs -Werror=undef -Werror=write-strings -Wformat-nonliteral -Werror=format-security -Werror=format=2 -Wignored-qualifiers -Wimplicit-function-declaration -Wlogical-op -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wnested-externs -Wno-cast-function-type -Wno-dangling-pointer -Wno-missing-field-initializers -Wno-sign-compare -Wno-unused-parameter -Wold-style-definition -Wpointer-arith -Wredundant-decls -Wstrict-prototypes -Wswitch-default -Wswitch-enum -Wundef -Wuninitialized -Wunused -fno-strict-aliasing -DHAVE_CONFIG_H -D_GNU_SOURCE -DIDE_COMPILATION -DG_DISABLE_CAST_CHECKS -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wmissing-declarations -fvisibility=hidden -DG_DISABLE_ASSERT -DIDE_TWEAKS_COMPILATION -MD -MQ src/libide/tweaks/libide-tweaks-45.a.p/ide-tweaks-window.c.o -MF src/libide/tweaks/libide-tweaks-45.a.p/ide-tweaks-window.c.o.d -o src/libide/tweaks/libide-tweaks-45.a.p/ide-tweaks-window.c.o -c ../src/libide/tweaks/ide-tweaks-window.c In file included from /usr/lib/riscv64-linux-gnu/glib-2.0/include/glibconfig.h:9, from /usr/include/glib-2.0/glib/gtypes.h:34, from /usr/include/glib-2.0/glib/galloca.h:34, from /usr/include/glib-2.0/glib.h:32, from /usr/include/glib-2.0/glib/gi18n.h:23, from ../src/libide/tweaks/ide-tweaks-window.c:25: /usr/include/glib-2.0/glib/gmacros.h:1338:49: error: redefinition of ‘glib_autoptr_clear_GtkStackPage’ 1338 | #define _GLIB_AUTOPTR_CLEAR_FUNC_NAME(TypeName)
Processed: set forwarded on 1061318
Processing commands for cont...@bugs.debian.org: > forwarded 1061318 https://github.com/dgibson/dtc/issues/123 Bug #1061318 [src:device-tree-compiler] device-tree-compiler ftbfs with Python 3.12 as default Set Bug forwarded-to-address to 'https://github.com/dgibson/dtc/issues/123'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1061318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1061567 marked as pending in gnome-builder
Processing control commands: > tag -1 pending Bug #1061567 [src:gnome-builder] gnome-builder FTBFS: redefinition of glib_autoptr_*_GtkStackPage Ignoring request to alter tags of bug #1061567 to the same tags previously set -- 1061567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061567: marked as pending in gnome-builder
Control: tag -1 pending Hello, Bug #1061567 in gnome-builder 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/gnome-team/gnome-builder/-/commit/eb33ce8b54b80e567ee568d59feb9eea2f64ed35 Cherry-pick build fix needed after GTK 4.12.5 Thanks: Adrian Bunk Closes: #1061567 (this message was generated automatically) -- Greetings https://bugs.debian.org/1061567
Processed: Re: Bug#1061567: gnome-builder FTBFS: redefinition of glib_autoptr_*_GtkStackPage
Processing commands for cont...@bugs.debian.org: > forwarded 1061567 https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/2156 Bug #1061567 [src:gnome-builder] gnome-builder FTBFS: redefinition of glib_autoptr_*_GtkStackPage Changed Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/2156' from 'https://gitlab.gnome.org/GNOME/gnome-builder/-/commit/7aaaecefc2ea8a37eaeae8b4d726d119d4eb8fa3'. > tags 1061567 +pending Bug #1061567 [src:gnome-builder] gnome-builder FTBFS: redefinition of glib_autoptr_*_GtkStackPage Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 1061567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060173: ruby-hiredis FTBFS with hiredis 1.2.0-6
I examined this bug a bit. In test/reader_test.rb, test_nil / test_null_multi_bulk are both failing. If these tests are commented out, the package build will complete. Doesn't sound like a great idea though as it's not clear to me why these tests regressed. -Dan
Bug#1061546: srcpd: installs file into aliased location
On 26.01.2024 09:35, Chris Hofstaedtler wrote: Hi, Please move /lib/udev/rules.d/10-liusb.rules into /usr/lib before srcpd reaches testing. hille42@hz:~/devel/srcpd$ dpkg-deb -c srcpd_2.1.6-2_amd64.deb|grep usb -rw-r--r-- root/root 151 2024-01-26 21:45 ./usr/lib/udev/rules.d/10-liusb.rules I guess this looks OK, not sure when I'll upload. Hilmar -- sigfault OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: severity of 1061577 is grave
Processing commands for cont...@bugs.debian.org: > severity 1061577 grave Bug #1061577 [src:rust-rio] rust-rio: use-after-free buffer access when a future is leaked Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1061577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061577 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059995: pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC namespacing: Resource temporarily unavailable
Hi zeha, On 26-01-2024 10:21, Chris Hofstaedtler wrote: I see this "works", but now the tests fail after one try on the problematic worker and then are never retried. Can this please be fixed? What do you have in mind? I think you need to wait until issue 166 [1] is fixed, which I guess isn't going to happen soon. Paul [1] https://salsa.debian.org/ci-team/debci/-/issues/166 OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: Bug#1061272 marked as pending in sudo
Processing control commands:
> tag -1 pending
Bug #1061272 {Done: Marc Haber } [src:sudo]
sudo: Does not build from prefered source
Added tag(s) pending.
--
1061272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1061272: marked as pending in sudo
Control: tag -1 pending Hello, Bug #1061272 in sudo 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/sudo-team/sudo/-/commit/3d86b138d4dd9268f1dd6fab8b1d177393786fe7 add --with-devel configure option Thanks: Bastien Roucariès Closes: #1061272 (this message was generated automatically) -- Greetings https://bugs.debian.org/1061272
Bug#1061272: marked as done (sudo: Does not build from prefered source)
Your message dated Fri, 26 Jan 2024 20:45:19 + with message-id and subject line Bug#1061272: fixed in sudo 1.9.15p5-3 has caused the Debian Bug report #1061272, regarding sudo: Does not build from prefered source to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1061272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061272 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sudo Severity: serious Tags: ftbfs Justification: yacc/lex are prefered source Dear Maintainer, You do not pass the --with-devel=yes configure flags thus you do not rebuild from source autogenerated file like gram.c and gram.h from gram.y Usually debian build from source grammar file particularly for sensitive security components like sudo Bastien -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armel Kernel: Linux 6.5.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information --- End Message --- --- Begin Message --- Source: sudo Source-Version: 1.9.15p5-3 Done: Marc Haber We believe that the bug you reported is fixed in the latest version of sudo, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marc Haber (supplier of updated sudo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 26 Jan 2024 21:10:13 +0100 Source: sudo Architecture: source Version: 1.9.15p5-3 Distribution: unstable Urgency: medium Maintainer: Sudo Maintainers Changed-By: Marc Haber Closes: 1061272 Changes: sudo (1.9.15p5-3) unstable; urgency=medium . * add --with-devel configure option. Thanks to Bastien Roucariès (Closes: #1061272) Checksums-Sha1: e79ad74f762ab9b6280ce45edf786475e69b6aad 2624 sudo_1.9.15p5-3.dsc c9e6d0b699aea8ab7353d1bb641395035199e677 46928 sudo_1.9.15p5-3.debian.tar.xz 7f10cd1160b0d8180d4367bdd006b5cb5f0787c5 6846 sudo_1.9.15p5-3_source.buildinfo Checksums-Sha256: 3fad99ab71f0666551be3c8889b58ad16af0ceeff411330540eaa48dc1954eca 2624 sudo_1.9.15p5-3.dsc 0592dc3fb0af36758591cdb00139961da7e204069f23893ff4fabf7704469629 46928 sudo_1.9.15p5-3.debian.tar.xz 026904bbe595bf042161d486ade1e96150803874d5102cd9c43bea021969e1e5 6846 sudo_1.9.15p5-3_source.buildinfo Files: dd1f6347f28cdd6695a976508f367ee9 2624 admin optional sudo_1.9.15p5-3.dsc cbe38ab0cdeede2b3f4158494756e160 46928 admin optional sudo_1.9.15p5-3.debian.tar.xz d6bbf8acf2a86c7ad3207c580436f889 6846 admin optional sudo_1.9.15p5-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE6QL5UJ/L0pcuNEbjj3cgEwEyBEIFAmW0FAYACgkQj3cgEwEy BEIW/g/+LeVcMFTN7kwj4OgQqkXXmHhqtHri2vahsZe1FxbKNEyVQ3KysZgEpXAE ql9VaT7aJelbfRCLVBcO0at1UjsuF5aKHO7g60vh4wvsqi44VhxhS2VoJGI7uqGp qVZcmymQ1Z/XTuya7pi8mCnu3MO+hkkpIk4lD5Ud5VC6BykAr5UbSgx+tgB2nrKx 0fyyHmGJI3Mxn1RjSByGkkAKC9/94aNZZzWv2DR6OZVDo4KLnepj1+bO6qE9hJHr KKeLl7Q6HNbp8L+hPLZ15CnrNhD2etM6cQwnXrN7osxQO6lgk5InFoqbTpTSahnA YvxVP2X75DjfP/YotJxvrdj+GD+Kdw2HnnNevCrU7BTV12R5deTHBFPQDBYJSOH1 P8uoR7DGCP43LpO+CPY4+lBavSBGX5iOUcIDJV+CebWH68RlphEJQ7ZJCy0vxE1x ZSvBrB85DxUq//ohJSKR8hORTLSFSjLn9wPkCiBCy+UptAf+70JSrQIdK65fOHln zC5nSJ4O8vd0wbfpo4Ock7jtLHnePyKQnQ6+r2bITCTvtOC225Ub3ESTHHpWohFi 2Y0wt+Id05NDMJdWKx2G+CgfD1Zb2nwdI+OJia5DJqs+OJ1EcDdLuwx1LPPmTcX9 Giyr27DqN/i10lVUBM3yrZoP/pwNAbbYmZeECRotDvOoGQno2/0= =qhyP -END PGP SIGNATURE End Message ---
Bug#1061009: marked as done (winff: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_build-arch] Error 2)
Control: reassign -1 lazarus Control: fixed -1 3.0+dfsg1-6 This issue was caused by a Lazrus bug and is now fixed. -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part
Processed: Re: marked as done (winff: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_build-arch] Error 2)
Processing control commands:
> reassign -1 lazarus
Bug #1061009 {Done: Abou Al Montacir } [src:winff]
winff: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_build-arch] Error
2
Bug reassigned from package 'src:winff' to 'lazarus'.
No longer marked as found in versions winff/1.6.2+dfsg-2.
No longer marked as fixed in versions lazarus/3.0+dfsg1-6.
> fixed -1 3.0+dfsg1-6
Bug #1061009 {Done: Abou Al Montacir } [lazarus] winff:
FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_build-arch] Error 2
Marked as fixed in versions lazarus/3.0+dfsg1-6.
--
1061009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: marked as done (ddrescueview: FTBFS: make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2)
Processing control commands:
> reassign -1 lazarus
Bug #1060995 {Done: Abou Al Montacir }
[src:ddrescueview] ddrescueview: FTBFS: make[1]: *** [debian/rules:10:
override_dh_auto_build] Error 2
Bug reassigned from package 'src:ddrescueview' to 'lazarus'.
No longer marked as found in versions ddrescueview/0.4.5-2.
No longer marked as fixed in versions lazarus/3.0+dfsg1-6.
> fixed -1 3.0+dfsg1-6
Bug #1060995 {Done: Abou Al Montacir } [lazarus]
ddrescueview: FTBFS: make[1]: *** [debian/rules:10: override_dh_auto_build]
Error 2
Marked as fixed in versions lazarus/3.0+dfsg1-6.
--
1060995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: marked as done (doublecmd: FTBFS: make[1]: *** [debian/rules:16: override_dh_install] Error 2)
Processing control commands:
> reassign -1 lazarus
Bug #1060932 {Done: Abou Al Montacir } [src:doublecmd]
doublecmd: FTBFS: make[1]: *** [debian/rules:16: override_dh_install] Error 2
Bug reassigned from package 'src:doublecmd' to 'lazarus'.
No longer marked as found in versions doublecmd/1.1.7-1.
No longer marked as fixed in versions lazarus/3.0+dfsg1-6.
> fixed -1 3.0+dfsg1-6
Bug #1060932 {Done: Abou Al Montacir } [lazarus]
doublecmd: FTBFS: make[1]: *** [debian/rules:16: override_dh_install] Error 2
Marked as fixed in versions lazarus/3.0+dfsg1-6.
--
1060932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1060995: marked as done (ddrescueview: FTBFS: make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2)
Control: reassign -1 lazarus Control: fixed -1 3.0+dfsg1-6 This issue was caused by a Lazrus bug and is now fixed. -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part
Bug#1060932: marked as done (doublecmd: FTBFS: make[1]: *** [debian/rules:16: override_dh_install] Error 2)
Control: reassign -1 lazarus Control: fixed -1 3.0+dfsg1-6 This issue was caused by a Lazrus bug and is now fixed. -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part
Processed: found 1060898 in 0.3.7-1
Processing commands for cont...@bugs.debian.org:
> found 1060898 0.3.7-1
Bug #1060898 {Done: Gürkan Myczko } [apfs-dkms] apfs-dkms:
fails to build module: super.c:17:10: fatal error: version.h: No such file or
directory
Marked as found in versions linux-apfs-rw/0.3.7-1; no longer marked as fixed in
versions linux-apfs-rw/0.3.7-1 and reopened.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1060898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#947510: marked as done (Asterisk won't response for a while after run the TTS for the first time.)
Your message dated Fri, 26 Jan 2024 18:49:04 +
with message-id
and subject line Bug#947510: fixed in asterisk-espeak 5.0~1-4
has caused the Debian Bug report #947510,
regarding Asterisk won't response for a while after run the TTS for the first
time.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
947510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: asterisk-espeak
Version: 5.0~1-3
Severity: grave
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
after install asterisk-easpeak and use via:
[quote]
exten => 888,1,NOOP(Call to 888);
same => n,Answer();
same => n,Wait(0.5);
same => n,Espeak("Hallo. Test")
same => n,Wait(5.0);
same => n,Espeak("Hallo. Entschuldigung.");
same => n,Wait(4.0);
same => n,Espeak("Hallo. Test");
same => n,Wait(15.0);
same => n,Espeak("Test Test");
same => n,Hangup();
[/quote]
Call Log:
[quote]
Using SIP RTP CoS mark 5
> 0x7f29f000e010 -- Strict RTP learning after remote address set to:
192.168.1.221:49890
-- Executing [888@firma:1] NoOp("SIP/666-", "Call to 888") in new
stack
-- Executing [888@firma:2] Answer("SIP/666-", "") in new stack
-- Executing [888@firma:3] Wait("SIP/666-", "0.5") in new stack
> 0x7f29f000e010 -- Strict RTP switching to RTP target address
192.168.1.221:49890 as source
-- Executing [888@firma:4] eSpeak("SIP/666-", ""Hallo. Test"") in
new stack
-- Playing '/tmp/espk_uWEBBn.slin' (language 'de')
-- Executing [888@firma:5] Wait("SIP/666-", "5.0") in new stack
> 0x7f29f000e010 -- Strict RTP learning complete - Locking on source
address 192.168.1.221:49890
-- Executing [888@firma:6] eSpeak("SIP/666-", ""Hallo.
Entschuldigung."") in new stack
[/quote]
The text from :6 are not playing. After hangup the phone I get a lot of
WARNING[6996]: chan_sip.c:4337 __sip_autodestruct: Autodestruct on dialog
'313537373437393038343234373834-2sf0ko0cwh5y' with owner SIP/666- in
place (Method: BYE). Rescheduling destruction for 1 ms
- -- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (300, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.3.0-3-amd64 (SMP w/6 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages asterisk-espeak depends on:
pn asterisk
pn asterisk-1fb7f5c06d7a2052e38d021b3d8ca151
ii libc6 2.29-3
ii libespeak-ng1 1.50+dfsg-4
ii libsamplerate0 0.1.9-2
asterisk-espeak recommends no packages.
asterisk-espeak suggests no packages.
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl4GbRcACgkQCfifPIyh
0l1lUg//R0u87Qk9LD1W55SOFo6LB4M15MOSxdMyKl5s8H+4HbhAp11TL8XWV5h3
+7s/rXp1a0TSO9yqpd7SfcEiGB9Uko65YqUJelmgZAFufQtPBvdLWuJ1T5hybhag
b4/WPgbnLWdJzPnjKnkl3tH4Ae8rGGcY6LnkWZycnBDeh197SK9aM0zYSyN4iRK1
M3flhQ61EKyiDgei0gGk9j9DCK6f4rIsl6xMFnCJnZBEWYjJ0+gii+K/hxC3qWFB
R9sX31+vuyEi7XWw3ILitEGfLQTzVntGBanUWPfZu3ZvLNw4FfhT1p879ue+sZZ0
LBMS336rPV/EBbOOn5VGKVdzRY0HC9je4KDNWTYtW23kQk3poByEfrzc7wdp283t
1VH0mvKHBUGaDXQmn++DTuphm5EUPTnd/KZFn9sXmirmmCwOhNgW9Yy5rjQSVpqM
9S0REe5s5BCC62604ahis59BpwkmXN3dXzF9yNhYk2blf8pjT/6mDOMN4bYFumPV
ohXZBsuX7WQCZqJpN6j+MnueIHRZvk/IKNnOKDprdL5fFUP4DQcG8d5v8Bavy9EP
l7FIazSwSgrNYsHWEEjAmsvQp+OlWl3MWHYLLVML4k35T9RTpyuMnnoJD1emLlG9
XEno9FUe7s7GAEqJuyIQT8DYBtbMlo8ntOdpVzFqCS4bMeNjnSA=
=xWpE
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: asterisk-espeak
Source-Version: 5.0~1-4
Done: Jonas Smedegaard
We believe that the bug you reported is fixed in the latest version of
asterisk-espeak, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 947...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Smedegaard (supplier of updated asterisk-espeak package)
(This message was generated automatically at their
Bug#1035547: marked as done (asterisk-espeak: depends on misspelled asterisk abi hash)
Your message dated Fri, 26 Jan 2024 18:49:04 + with message-id and subject line Bug#1035547: fixed in asterisk-espeak 5.0~1-4 has caused the Debian Bug report #1035547, regarding asterisk-espeak: depends on misspelled asterisk abi hash to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1035547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: asterisk-espeak Version: 5.0~1-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, asterisk-espeak is not installable since it depends on asterisk-1fb7f5c06d7a2052e38d021b3d8ca151 while asterisk provides asterisk-abi-1fb7f5c06d7a2052e38d021b3d8ca151 Andreas --- End Message --- --- Begin Message --- Source: asterisk-espeak Source-Version: 5.0~1-4 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of asterisk-espeak, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated asterisk-espeak package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Jan 2024 19:15:39 +0100 Source: asterisk-espeak Architecture: source Version: 5.0~1-4 Distribution: unstable Urgency: medium Maintainer: Debian VoIP Team Changed-By: Jonas Smedegaard Closes: 947510 1035547 Changes: asterisk-espeak (5.0~1-4) unstable; urgency=medium . * watch: simplify regular expression; rewrite usage comment * add patch cherry-picked upstream with small updates * add patches 1002_* cherry-picked from upstream pull request, to initialize espeak on module load; closes: bug#947510, thanks to Jörg Frings-Fürst and Fabio Muzzi * add patch 1003 cherry-picked from upstream pull request, to add AMI command * simplify rules; tighten build-dependency on asterisk-dev; stop build-depend on cdbs dh-buildinfo; use debhelper compatibility level 13 (not 9); build-depend on debhelper-compat dh-sequence-asterisk (not asterisk-dev debhelper); closes: bug#1035547, thanks to Andreas Beckmann * install to multiarch paths * declare compliance with Debian Policy 4.6.2 * simplify helper script copyright-check * drop obsolete README.source notes * update git-buildpackage config: + use DEP14 branch naming scheme + add usage comment Checksums-Sha1: f28c4c50aac5b83aabc7da1ac91c3c0e0a9bbc83 2124 asterisk-espeak_5.0~1-4.dsc 6d93fbf1e582965c582cb4583f88483b7014f288 8016 asterisk-espeak_5.0~1-4.debian.tar.xz cf068070b1c12ba7a0c45cef0d638376e34b1853 7236 asterisk-espeak_5.0~1-4_amd64.buildinfo Checksums-Sha256: e100ca50c3b0324ea6608aab7db6b4580503bd64876e25c07a0f25b96489c7f5 2124 asterisk-espeak_5.0~1-4.dsc 83da04d24c5b6c2bc2df75129c5fe7703d2b6981e773b0275244ff26023709f5 8016 asterisk-espeak_5.0~1-4.debian.tar.xz df522d98f0711487266c8a290f6f8ba299b9b521a10d555865b1a9bbd89de5ab 7236 asterisk-espeak_5.0~1-4_amd64.buildinfo Files: 386bda721b00c7fd26ca32cc01f6cb3a 2124 comm optional asterisk-espeak_5.0~1-4.dsc d26c9c0364b32d928cc06f4a761ed084 8016 comm optional asterisk-espeak_5.0~1-4.debian.tar.xz 6839374121b1c22cf7f22fe3161beb39 7236 comm optional asterisk-espeak_5.0~1-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmWz+AMACgkQLHwxRsGg ASHd2g/+Js3gcT2oaLZBDyD0zTxvHCTHXOwWQ/YkQ9o/LbvfA4Awlhk6C1WwNjUp 3BmTqj3vaf/Wti4rfHXVQXgHzyOE9JYw97L/VuaYnIplmSWjG9SfvTVGOBdkQjyw IJc/Grtuuq+GkYXurD5AUXCkPKHLNKIaWvroKpdRfN1gAMxIW5j0//mjWK4VKnuU Hquy43OY2YGoqqe6UQSWjYoEkyaw8kSRqeHUbkp5cmJtnLXdkZyCe8jtT2ShhEfF iKiEPoTpp4zSdsiZMfCtq8xIZVFB8HJ3WAHjccsjRScXVr2CJ00rFLiuvCc4jR8/ jqtV7XzaxT8w8mDC6uQqeu0JvSjFwP/T2cOAoW0L4RP4qx4ZjjCPNhR2f+QQ2J5T EVQz5WZ+UvSUaId8X/hul8KlyFwsIl4Kory9xoPRzyrOyu5+GREy/LOzzjEWoZBJ PuwwJmWrFoGVADRUJAp5DfkSPC8NFRkbpXql5G5DwZxGZQH835papKSefO4IZvYA y7gilvExcSs656U9pc3FP0WBtUDl2yLLoFS7zHo8jretJG7iP/qpbyDcabfkIUrJ ipjw+1VUQSVYrGGjzo29g/5jHNq46hGa2PO+jY9P40YQ4d7h0qhSfYprTlAcDyhr pAi7B9//wlxaPcrc45AJ84r+1lO3BLArSjr3a/kZqxtU+9hbr4c= =/6w2 -END PGP SIGNATURE
Bug#1058407: marked as done (numpydoc: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Fri, 26 Jan 2024 19:22:28 +0100
with message-id
and subject line Re: numpydoc's autopkg tests fail with Python 3.12
has caused the Debian Bug report #1056431,
regarding numpydoc: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1056431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: numpydoc
Version: 1.5.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config
> running config
> I: pybuild base:310: python3.11 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc
> copying numpydoc/__init__.py ->
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc
> copying numpydoc/numpydoc.py ->
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc
> copying numpydoc/_version.py ->
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc
> copying numpydoc/validate.py ->
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc
> copying numpydoc/__main__.py ->
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc
> copying numpydoc/docscrape_sphinx.py ->
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc
> copying numpydoc/docscrape.py ->
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc
> copying numpydoc/xref.py ->
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc
> creating /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc/tests
> copying numpydoc/tests/test_validate.py ->
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc/tests
> copying numpydoc/tests/test_full.py ->
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc/tests
> copying numpydoc/tests/test_main.py ->
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc/tests
> copying numpydoc/tests/test_numpydoc.py ->
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc/tests
> copying numpydoc/tests/test_xref.py ->
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc/tests
> copying numpydoc/tests/test_docscrape.py ->
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc/tests
> creating
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc/tests/tinybuild
> copying numpydoc/tests/tinybuild/Makefile ->
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc/tests/tinybuild
> copying numpydoc/tests/tinybuild/index.rst ->
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc/tests/tinybuild
> copying numpydoc/tests/tinybuild/numpydoc_test_module.py ->
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc/tests/tinybuild
> copying numpydoc/tests/tinybuild/conf.py ->
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc/tests/tinybuild
> creating
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc/templates
> copying numpydoc/templates/numpydoc_docstring.rst ->
> /<>/.pybuild/cpython3_3.12_numpydoc/build/numpydoc/templates
> I: pybuild base:310: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_numpydoc/build/numpydoc
> copying numpydoc/__init__.py ->
> /<>/.pybuild/cpython3_3.11_numpydoc/build/numpydoc
> copying numpydoc/numpydoc.py ->
> /<>/.pybuild/cpython3_3.11_numpydoc/build/numpydoc
> copying numpydoc/_version.py ->
> /<>/.pybuild/cpython3_3.11_numpydoc/build/numpydoc
> copying numpydoc/validate.py ->
> /<>/.pybuild/cpython3_3.11_numpydoc/build/numpydoc
> copying numpydoc/__main__.py ->
> /<>/.pybuild/cpython3_3.11_numpydoc/build/numpydoc
> copying numpydoc/docscrape_sphinx.py ->
> /<>/.pybuild/cpython3_3.11_numpydoc/build/numpydoc
> copying numpydoc/docscrape.py ->
> /<>/.pybuild/cpython3_3.11_numpydoc/build/numpydoc
> copying numpydoc/xref.py ->
> /<>/.pybuild/cpython3_3.11_numpydoc/build/numpydoc
> creating /<>/.pybuild/cpython3_3.11_numpydoc/build/numpydoc/tests
> copying numpydoc/tests/test_validate.py ->
> /<>/.pybuild/cpython3_3.11_numpydoc/build/numpydoc/tests
> copying numpydoc/tests/test_full.py ->
>
Bug#1056431: marked as done (numpydoc's autopkg tests fail with Python 3.12)
Your message dated Fri, 26 Jan 2024 19:22:28 +0100
with message-id
and subject line Re: numpydoc's autopkg tests fail with Python 3.12
has caused the Debian Bug report #1056431,
regarding numpydoc's autopkg tests fail with Python 3.12
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1056431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:numpydoc
Version: 1.5.0-1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
numpydoc's autopkg tests fail with Python 3.12:
[...]
393s Testing with python3.12:
394s = test session starts
==
394s platform linux -- Python 3.12.0+, pytest-7.4.3, pluggy-1.3.0
394s rootdir: /tmp/autopkgtest.wwyJzK/autopkgtest_tmp
394s plugins: cov-4.1.0
394s collected 217 items
394s
394s tests/test_docscrape.py
[ 22%]
394s
[ 27%]
395s tests/test_full.py .
[ 29%]
395s tests/test_main.py ..
[ 32%]
395s tests/test_numpydoc.py .
[ 36%]
395s tests/test_validate.py
. [ 59%]
395s .xF.x
[ 70%]
395s tests/test_xref.py
. [ 95%]
395s ..
[100%]
395s
395s === FAILURES
===
395s __
TestValidator.test_bad_docstrings[BadReturns-return_not_documented-msgs31]
__
395s
395s self =
395s capsys = <_pytest.capture.CaptureFixture object at 0x7f30bb20>
395s klass = 'BadReturns', func = 'return_not_documented'
395s msgs = ('No Returns section found',)
395s
395s @pytest.mark.parametrize(
395s "klass,func,msgs",
395s [
395s # See Also tests
395s (
395s "BadGenericDocStrings",
395s "unknown_section",
395s ('Found unknown section "Unknown Section".',),
395s ),
395s (
395s "BadGenericDocStrings",
395s "sections_in_wrong_order",
395s (
395s "Sections are in the wrong order. Correct order
is: Parameters, "
395s "See Also, Examples",
395s ),
395s ),
395s (
395s "BadGenericDocStrings",
395s "deprecation_in_wrong_order",
395s ("Deprecation warning should precede extended
summary",),
395s ),
395s (
395s "BadGenericDocStrings",
395s "directives_without_two_colons",
395s (
395s "reST directives ['versionchanged',
'versionadded', "
395s "'deprecated'] must be followed by two colons",
395s ),
395s ),
395s (
395s "BadSeeAlso",
395s "no_desc",
395s ('Missing description for See Also "Series.tail"
reference',),
395s ),
395s (
395s "BadSeeAlso",
395s "desc_no_period",
395s ('Missing period at end of description for See Also
"Series.iloc"',),
395s ),
395s (
395s "BadSeeAlso",
395s "desc_first_letter_lowercase",
395s ('should be capitalized for See Also "Series.tail"',),
395s ),
395s # Summary tests
395s (
395s "BadSummaries",
395s "no_summary",
395s ("No summary found",),
395s ),
395s (
395s "BadSummaries",
395s "heading_whitespaces",
395s ("Summary contains heading whitespaces",),
395s ),
395s (
395s "BadSummaries",
395s "wrong_line",
395s (
395s "should start in the line immediately after the
opening quotes",
395s "should be placed in the line after the last text",
395s ),
395s ),
395s ("BadSummaries", "no_punctuation", ("Summary does not
end with a period",)),
395s (
395s "BadSummaries",
395s "no_capitalization",
395s ("Summary does not start with a capital letter",),
395s ),
395s (
395s
Processed: closing 1060143
Processing commands for cont...@bugs.debian.org: > close 1060143 0.0.19-1 Bug #1060143 [src:gnss-sdr] gnss-sdr ftbfs in unstable Marked as fixed in versions gnss-sdr/0.0.19-1. Bug #1060143 [src:gnss-sdr] gnss-sdr ftbfs in unstable Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1060143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061567: gnome-builder FTBFS: redefinition of glib_autoptr_*_GtkStackPage
Source: gnome-builder Version: 45.0-1 Severity: serious Tags: ftbfs patch Forwarded: https://gitlab.gnome.org/GNOME/gnome-builder/-/commit/7aaaecefc2ea8a37eaeae8b4d726d119d4eb8fa3 https://buildd.debian.org/status/fetch.php?pkg=gnome-builder=riscv64=45.0-1%2Bb2=1706281444=0 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnome-builder.html ... FAILED: src/libide/tweaks/libide-tweaks-45.a.p/ide-tweaks-window.c.o cc -Isrc/libide/tweaks/libide-tweaks-45.a.p -Isrc/libide/tweaks -I../src/libide/tweaks -Isrc/libide/core -I../src/libide/core -Isrc/libide/io -I../src/libide/io -Isrc/libide/threading -I../src/libide/threading -Isrc/libide/search -I../src/libide/search -Isrc/libide/gtk -I../src/libide/gtk -Isrc/libide/plugins -I../src/libide/plugins -I/usr/include/glib-2.0 -I/usr/lib/riscv64-linux-gnu/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gtk-4.0 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/riscv64-linux-gnu -I/usr/include/webp -I/usr/include/graphene-1.0 -I/usr/lib/riscv64-linux-gnu/graphene-1.0/include -I/usr/include/libadwaita-1 -I/usr/include/appstream -I/usr/include/libdex-1 -I/usr/include/libpeas-2 -I/usr/include/gio-unix-2.0 -I/usr/include/gtksourceview-5 -I/usr/include/libxml2 -I/<>/obj-riscv64-linux-gnu -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=gnu11 -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_76 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_76 -DGDK_VERSION_MIN_REQUIRED=GDK_VERSION_4_10 -DGDK_VERSION_MAX_ALLOWED=GDK_VERSION_4_10 -DGDK_DISABLE_DEPRECATION_WARNINGS -DADW_VERSION_MIN_REQUIRED=ADW_VERSION_1_4 -DADW_VERSION_MAX_ALLOWED=ADW_VERSION_1_4 -DGTK_SOURCE_VERSION_MIN_REQUIRED=GTK_SOURCE_VERSION_5_8 -DGTK_SOURCE_VERSION_MAX_ALLOWED=GTK_SOURCE_VERSION_5_8 -Wcast-align -Wdeclaration-after-statement -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=implicit -Werror=implicit-function-declaration -Werror=incompatible-pointer-types -Werror=init-self -Werror=int-conversion -Werror=int-to-pointer-cast -Werror=main -Werror=misleading-indentation -Werror=missing-braces -Werror=missing-include-dirs -Werror=nonnull -Werror=overflow -Werror=pointer-arith -Werror=pointer-to-int-cast -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=shadow -Werror=trigraphs -Werror=undef -Werror=write-strings -Wformat-nonliteral -Werror=format-security -Werror=format=2 -Wignored-qualifiers -Wimplicit-function-declaration -Wlogical-op -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wnested-externs -Wno-cast-function-type -Wno-dangling-pointer -Wno-missing-field-initializers -Wno-sign-compare -Wno-unused-parameter -Wold-style-definition -Wpointer-arith -Wredundant-decls -Wstrict-prototypes -Wswitch-default -Wswitch-enum -Wundef -Wuninitialized -Wunused -fno-strict-aliasing -DHAVE_CONFIG_H -D_GNU_SOURCE -DIDE_COMPILATION -DG_DISABLE_CAST_CHECKS -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -Wmissing-declarations -fvisibility=hidden -DG_DISABLE_ASSERT -DIDE_TWEAKS_COMPILATION -MD -MQ src/libide/tweaks/libide-tweaks-45.a.p/ide-tweaks-window.c.o -MF src/libide/tweaks/libide-tweaks-45.a.p/ide-tweaks-window.c.o.d -o src/libide/tweaks/libide-tweaks-45.a.p/ide-tweaks-window.c.o -c ../src/libide/tweaks/ide-tweaks-window.c In file included from /usr/lib/riscv64-linux-gnu/glib-2.0/include/glibconfig.h:9, from /usr/include/glib-2.0/glib/gtypes.h:34, from /usr/include/glib-2.0/glib/galloca.h:34, from /usr/include/glib-2.0/glib.h:32, from /usr/include/glib-2.0/glib/gi18n.h:23, from ../src/libide/tweaks/ide-tweaks-window.c:25: /usr/include/glib-2.0/glib/gmacros.h:1338:49: error: redefinition of ‘glib_autoptr_clear_GtkStackPage’ 1338 | #define _GLIB_AUTOPTR_CLEAR_FUNC_NAME(TypeName) glib_autoptr_clear_##TypeName | ^~~ /usr/include/glib-2.0/glib/gmacros.h:1354:36: note: in expansion of macro ‘_GLIB_AUTOPTR_CLEAR_FUNC_NAME’ 1354 | static G_GNUC_UNUSED inline void _GLIB_AUTOPTR_CLEAR_FUNC_NAME(TypeName) (TypeName *_ptr) \ |^ /usr/include/glib-2.0/glib/gmacros.h:1371:3: note: in expansion of macro ‘_GLIB_DEFINE_AUTOPTR_CLEANUP_FUNCS’ 1371 | _GLIB_DEFINE_AUTOPTR_CLEANUP_FUNCS(TypeName, TypeName, func) | ^~ ../src/libide/tweaks/ide-tweaks-window.c:35:1: note: in expansion of macro ‘G_DEFINE_AUTOPTR_CLEANUP_FUNC’ 35 | G_DEFINE_AUTOPTR_CLEANUP_FUNC (GtkStackPage, g_object_unref) |
Bug#1061392: uploaded NMU to DELAYED/5
uploaded NMU 4.2.0-0.1 to DELAYED/5
Bug#1061466: marked as done (nautilus FTBFS with nocheck profile: ../test/automated/displayless/meson.build:1:19: ERROR: Dependency "tracker-testutils-3.0" not found, tried pkgconfig)
Your message dated Fri, 26 Jan 2024 16:05:28 + with message-id and subject line Bug#1061466: fixed in nautilus 45.2.1-4 has caused the Debian Bug report #1061466, regarding nautilus FTBFS with nocheck profile: ../test/automated/displayless/meson.build:1:19: ERROR: Dependency "tracker-testutils-3.0" not found, tried pkgconfig to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1061466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061466 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nautilus Version: 45.2.1-3 Severity: serious Tags: patch ftbfs trixie sid nautilus fails to build from source when built with the nocheck profile. Since trixie such a build failure is considered release-critical. The build system does not automatically disable tests when test dependencies are missing and fails. I'm attaching a patch for your convenience. I verified that a nocheck build results in bit-identicial artifacts to a regular build. Helmut diff --minimal -Nru nautilus-45.2.1/debian/changelog nautilus-45.2.1/debian/changelog --- nautilus-45.2.1/debian/changelog2024-01-12 02:39:25.0 +0100 +++ nautilus-45.2.1/debian/changelog2024-01-24 23:12:48.0 +0100 @@ -1,3 +1,10 @@ +nautilus (45.2.1-3.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix nocheck FTBFS (Closes: #-1) + + -- Helmut Grohne Wed, 24 Jan 2024 23:12:48 +0100 + nautilus (45.2.1-3) unstable; urgency=medium * Update tracker test patch to really skip the test failure diff --minimal -Nru nautilus-45.2.1/debian/rules nautilus-45.2.1/debian/rules --- nautilus-45.2.1/debian/rules2024-01-12 02:39:25.0 +0100 +++ nautilus-45.2.1/debian/rules2024-01-24 23:12:48.0 +0100 @@ -4,6 +4,12 @@ export DEB_LDFLAGS_MAINT_APPEND = -Wl,-O1 -Wl,-z,defs export DPKG_GENSYMBOLS_CHECK_LEVEL = 4 +ifeq ($(filter nocheck,$(DEB_BUILD_OPTIONS)),) +ENABLE_TESTS := -Dtests=all +else +ENABLE_TESTS := -Dtests=none +endif + ifeq ($(DEB_HOST_ARCH_OS),linux) ENABLE_SELINUX := -Dselinux=true else @@ -24,7 +30,7 @@ dh_auto_configure -- \ -Ddocs=true \ -Dpackagekit=true \ - -Dtests=all \ + $(ENABLE_TESTS) \ $(ENABLE_CLOUD) \ $(ENABLE_SELINUX) --- End Message --- --- Begin Message --- Source: nautilus Source-Version: 45.2.1-4 Done: Simon McVittie We believe that the bug you reported is fixed in the latest version of nautilus, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated nautilus package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 26 Jan 2024 15:14:00 + Source: nautilus Architecture: source Version: 45.2.1-4 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Simon McVittie Closes: 1061466 Changes: nautilus (45.2.1-4) unstable; urgency=medium . * Team upload . [ Helmut Grohne ] * Fix FTBFS when nocheck build option is specified (Closes: #1061466) . [ Jeremy Bícha ] * salsa-ci: Disable reprotest Checksums-Sha1: 0971da35abc306cdbddeab683c7f34a35e983d3c 3218 nautilus_45.2.1-4.dsc 3043a7e8ac4d4c7a9af223384c98353d45ddbfc6 27468 nautilus_45.2.1-4.debian.tar.xz 89bbca41bef839475c1e4cab038dee001fc8e255 18630 nautilus_45.2.1-4_source.buildinfo Checksums-Sha256: 711aa569269f0e977945216f1cee1c20ed89b5b05ae952f28884f02778b52664 3218 nautilus_45.2.1-4.dsc b338529cfce7e7aa5fd9a7512d1b57d085945349cb6e5db61092bcd7dded3c87 27468 nautilus_45.2.1-4.debian.tar.xz 9e7386ce8fa04c645fa394302329f880719eb1538fa1aaf929ca400fa043c8ba 18630 nautilus_45.2.1-4_source.buildinfo Files: 672c8dc3e0062fd3cc570fa1e634f8dc 3218 gnome optional nautilus_45.2.1-4.dsc dad453821d3cc808805a86a4d2fef702 27468 gnome optional nautilus_45.2.1-4.debian.tar.xz d4e199e5f980e2059c67b1a539820a17 18630 gnome optional nautilus_45.2.1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmWz1UYACgkQ4FrhR4+B
Bug#1061470: marked as done (vasttrafik-cli: API is offline)
Your message dated Fri, 26 Jan 2024 15:50:23 + with message-id and subject line Bug#1061470: fixed in vasttrafik-cli 1.9-1 has caused the Debian Bug report #1061470, regarding vasttrafik-cli: API is offline to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1061470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vasttrafik-cli Version: 1.5-1 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: ltw...@debian.org Dear myself. The public API has completely changed. There is no way to register new accounts and obtain tokens for the new API. Until that is solved, this package is completely useless. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.11-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vasttrafik-cli depends on: ii python3 3.11.6-1 ii python3-typedload 2.27-1 ii python3-wcwidth 0.2.5+dfsg1-1.1 ii python3-xtermcolor 1.2.1-3 vasttrafik-cli recommends no packages. vasttrafik-cli suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: vasttrafik-cli Source-Version: 1.9-1 Done: Salvo 'LtWorf' Tomaselli We believe that the bug you reported is fixed in the latest version of vasttrafik-cli, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvo 'LtWorf' Tomaselli (supplier of updated vasttrafik-cli package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Jan 2024 16:31:58 +0100 Source: vasttrafik-cli Architecture: source Version: 1.9-1 Distribution: unstable Urgency: high Maintainer: Salvo 'LtWorf' Tomaselli Changed-By: Salvo 'LtWorf' Tomaselli Closes: 1061470 Changes: vasttrafik-cli (1.9-1) unstable; urgency=high . * New upstream release * Use the new API (Closes: #1061470) Checksums-Sha1: 5ee7e62325ad1441d074c744fe9cd0853534bfc0 2270 vasttrafik-cli_1.9-1.dsc 515f34040e23ff48d8e7f9288eb587703bf03e65 150234 vasttrafik-cli_1.9.orig.tar.gz 3cd98a6eea2b9642f3945d69efe8b58e0458c8e8 833 vasttrafik-cli_1.9.orig.tar.gz.asc cf7b46921c39da7dc7a509d38368b101c65fd728 12928 vasttrafik-cli_1.9-1.debian.tar.xz 6b0fae0ccb64e3c37f139503d68bf1dce2272de0 7743 vasttrafik-cli_1.9-1_amd64.buildinfo Checksums-Sha256: 1a67f5f2da95010c3eca9f3cae5c3cfda6a03d7ca5162ee1d7968bb49ad82a64 2270 vasttrafik-cli_1.9-1.dsc a3bbe532f37c3a50f9298549f9f179d409fa4adff1c5f1ca63d35a1330afbe71 150234 vasttrafik-cli_1.9.orig.tar.gz 1a1d91c21cfd19dfd1dd9d069d0f81513b4f06257d77132d7949c2b82546613b 833 vasttrafik-cli_1.9.orig.tar.gz.asc c8761a73e50df304d5599c4a8315532ff175ca49db39a8e59f8ba49581a86581 12928 vasttrafik-cli_1.9-1.debian.tar.xz f143a0b23af60dca687a17e23ad8615a4f4db395eb892c993d42a47ea7d55e53 7743 vasttrafik-cli_1.9-1_amd64.buildinfo Files: 516210d2da706710e73803f0756e290a 2270 utils optional vasttrafik-cli_1.9-1.dsc 603107b21f4db8a8c5f99bef9f1906a0 150234 utils optional vasttrafik-cli_1.9.orig.tar.gz 1a199eeb9d1b6a200bd37127439d6d18 833 utils optional vasttrafik-cli_1.9.orig.tar.gz.asc 7141068215741b6b1ca45fb8f8d59e0f 12928 utils optional vasttrafik-cli_1.9-1.debian.tar.xz 6a22b5ed70df867fbcd03968142e3a9b 7743 utils optional vasttrafik-cli_1.9-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEQnSLnnbYmXmeH74Us6fPDIAYhs8FAmWz0VgACgkQs6fPDIAY hs+LTw//cpgXap28R5lojV4qYUiX79teL2a1sezJLFsqz/77PE4qQXoQQqyLKIob vJpjlhsS0ALq0FyV/nka2n37xlpMinuLJVPeo8RifAHczDesUJmglS6/4MPPCGfu UWCunbA+2DfOHnkrhnHZ2J0evlJ9Xvcnt+NTdWilHcrZCXLu+XTXIOx12dPBYakp A5DT2apydZr/Su4VnYsCSdkbWUIZ163HtRzKb+FsQOwQdFWpvXLTpMFHvTcCbok1 k9FCdjyxoLhG5eLDy+lk4DaOWKPylS7u1+KMyMfOP5QqmhK9EwBwN+168uHZBB9U
Processed: Bug#1060964 marked as pending in python-pure-sasl
Processing control commands: > tag -1 pending Bug #1060964 [src:python-pure-sasl] python-pure-sasl: FTBFS: tests failed Added tag(s) pending. -- 1060964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060964 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060964: marked as pending in python-pure-sasl
Control: tag -1 pending Hello, Bug #1060964 in python-pure-sasl 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/openstack-team/python/python-pure-sasl/-/commit/456914a3af1b0ea7563b15a05cb3da3ec6dfd447 Added missing dependency on python3-six (Closes: #1060964). (this message was generated automatically) -- Greetings https://bugs.debian.org/1060964
Bug#1058259: marked as done (python-ncclient: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)
Your message dated Fri, 26 Jan 2024 15:07:49 +
with message-id
and subject line Bug#1058259: fixed in python-ncclient 0.6.15-0.1
has caused the Debian Bug report #1058259,
regarding python-ncclient: FTBFS: AttributeError: module 'configparser' has no
attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1058259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058259
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-ncclient
Version: 0.6.13-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_clean
> I: pybuild base:310: python3.12 setup.py clean
> /<>/versioneer.py:421: SyntaxWarning: invalid escape sequence
> '\s'
> LONG_VERSION_PY['git'] = '''
> Traceback (most recent call last):
> File "/<>/setup.py", line 45, in
> version=versioneer.get_version(),
>
> File "/<>/versioneer.py", line 1480, in get_version
> return get_versions()["version"]
>^^
> File "/<>/versioneer.py", line 1412, in get_versions
> cfg = get_config_from_root(root)
> ^^
> File "/<>/versioneer.py", line 342, in get_config_from_root
> parser = configparser.SafeConfigParser()
> ^
> AttributeError: module 'configparser' has no attribute 'SafeConfigParser'.
> Did you mean: 'RawConfigParser'?
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> python3.12 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11"
> returned exit code 13
> make[1]: *** [debian/rules:19: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/python-ncclient_0.6.13-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-ncclient
Source-Version: 0.6.15-0.1
Done: Thomas Goirand
We believe that the bug you reported is fixed in the latest version of
python-ncclient, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated python-ncclient package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 26 Jan 2024 15:39:06 +0100
Source: python-ncclient
Architecture: source
Version: 0.6.15-0.1
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Badia
Changed-By: Thomas Goirand
Closes: 1018536 1058259
Changes:
python-ncclient (0.6.15-0.1) unstable; urgency=medium
.
* Non-maintainer upload.
.
[ Alexandre Detiste ]
* New upstream version 0.6.15 (Closes: #1058259).
* Remove dependency on python3-mock.
.
[ Sergio de Almeida Cipriano Junior ]
* Replace nose with pytest (Closes: #1018536).
* Bump Standards-Version to 4.6.2 (no changes needed).
* d/patches: Change interpreter from python to python3 in example scripts.
.
[ Thomas Goirand ]
* Add autopkgtest.
Checksums-Sha1:
79083856abb341788d4c69ae0e15132d5b40c923 2209 python-ncclient_0.6.15-0.1.dsc
0eef058ab749dbccdd4cb02f670593ccdbd5c78d 140680
python-ncclient_0.6.15.orig.tar.gz
Bug#1061345: marked as done (lib32stdc++6-14-dbg, libstdc++6-14-dbg and libx32stdc++6-14-dbg have an undeclared file conflict)
Your message dated Fri, 26 Jan 2024 13:49:15 +
with message-id
and subject line Bug#1061345: fixed in gcc-14 14-20240126-1
has caused the Debian Bug report #1061345,
regarding lib32stdc++6-14-dbg, libstdc++6-14-dbg and libx32stdc++6-14-dbg have
an undeclared file conflict
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1061345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libstdc++6-14-dbg,libx32stdc++6-14-dbg,lib32stdc++6-14-dbg
Version: 14-20240121-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + lib32stdc++6-13-dbg libstdc++6-13-dbg libx32stdc++6-13-dbg
lib32stdc++6-14-dbg, libstdc++6-14-dbg and libx32stdc++6-14-dbg have an
undeclared file conflict. This may result in an unpack error from dpkg.
The files
* /usr/lib32/debug/libstdc++.a
* /usr/lib32/debug/libstdc++.so
* /usr/lib32/debug/libstdc++.so.6
* /usr/lib32/debug/libstdc++exp.a
* /usr/lib32/debug/libstdc++fs.a
are contained in the packages
* lib32stdc++6-13-dbg/13.2.0-10 as present in trixie|unstable
* lib32stdc++6-14-dbg/14-20240121-1 as present in experimental
The files
* /usr/lib/x86_64-linux-gnu/debug/libstdc++.a
* /usr/lib/x86_64-linux-gnu/debug/libstdc++.so
* /usr/lib/x86_64-linux-gnu/debug/libstdc++.so.6
* /usr/lib/x86_64-linux-gnu/debug/libstdc++exp.a
* /usr/lib/x86_64-linux-gnu/debug/libstdc++fs.a
are contained in the packages
* libstdc++6-13-dbg/13.2.0-10 as present in trixie|unstable
* libstdc++6-14-dbg/14-20240121-1 as present in experimental
The files
* /usr/libx32/debug/libstdc++.a
* /usr/libx32/debug/libstdc++.so
* /usr/libx32/debug/libstdc++.so.6
* /usr/libx32/debug/libstdc++exp.a
* /usr/libx32/debug/libstdc++fs.a
are contained in the packages
* libx32stdc++6-13-dbg/13.2.0-10 as present in trixie|unstable
* libx32stdc++6-14-dbg/14-20240121-1 as present in experimental
These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.
Kind regards
The Debian Usr Merge Analysis Tool
This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.
--- End Message ---
--- Begin Message ---
Source: gcc-14
Source-Version: 14-20240126-1
Done: Matthias Klose
We believe that the bug you reported is fixed in the latest version of
gcc-14, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose (supplier of updated gcc-14 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 26 Jan 2024 12:42:52 +0100
Source: gcc-14
Architecture: source
Version: 14-20240126-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers
Changed-By: Matthias Klose
Closes: 1061345 1061372
Changes:
gcc-14 (14-20240126-1) unstable; urgency=medium
.
* Snapshot, taken from the trunk 20240126.
* Don't define _no_archs macros directly.
* Add missing libstdc++-{dbg,doc} conflicts. Closes: #1061345.
* Fix gm2-14 package description. Closes: #1061372.
* Re-add conflicts for gnat packages.
* Disable the ada build on armel for now. See #1061370.
Checksums-Sha1:
e7820789257ec5d692db53a0469eb6602deb69b0 46476 gcc-14_14-20240126-1.dsc
4c94be6b8d91c812c809bfe03c4b8f288fcbb8d0 90927258
gcc-14_14-20240126.orig.tar.gz
97f9c75b78060a87972482a88415c962ab499080 535092
gcc-14_14-20240126-1.debian.tar.xz
0ab312b09d22bfd5c748604fe6efe477be3c78dd 9525
gcc-14_14-20240126-1_source.buildinfo
Checksums-Sha256:
3872614e046e178d22141fabc346ccd921aeb4cd057b75ec06140b979c6801dc 46476
gcc-14_14-20240126-1.dsc
a79ae5695387942b5a8e245c08bb6f1bdc1bd975e79325d71a1392146abb290e 90927258
gcc-14_14-20240126.orig.tar.gz
Processed: Re: Bug#1061560: Need to remove /etc/dhcp/dhclient-exit-hooks.d/fetch-ldap-cert on upgrade
Processing control commands: > severity -1 serious Bug #1061560 [debian-edu-config] Need to remove /etc/dhcp/dhclient-exit-hooks.d/fetch-ldap-cert on upgrade Severity set to 'serious' from 'normal' -- 1061560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042612: marked as done (pydicom: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting)
Your message dated Fri, 26 Jan 2024 12:34:25 +
with message-id
and subject line Bug#1042612: fixed in pydicom 2.4.3-1
has caused the Debian Bug report #1042612,
regarding pydicom: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all
arguments converted during string formatting
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1042612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pydicom
Version: 2.3.1-1
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1
Hi,
pydicom fails to build with Sphinx 7.1 and docutils 0.20, both of which
are currently available in experimental.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> pybuild --build -i python{version} -p 3.11
> I: pybuild base:240: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/filebase.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/values.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/filereader.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/datadict.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/charset.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/errors.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/env_info.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/_dicom_dict.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/_storage_sopclass_uids.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/misc.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/multival.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/_version.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/encaps.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/fileset.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/dataelem.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/sequence.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/__init__.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/uid.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/dataset.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/dicomdir.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/tag.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/_private_dict.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/compat.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/fileutil.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/_uid_dict.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/valuerep.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/dicomio.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/config.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/jsonrep.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> copying pydicom/filewriter.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom
> creating
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom/overlay_data_handlers
> copying pydicom/overlay_data_handlers/__init__.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom/overlay_data_handlers
> creating /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom/sr
> copying pydicom/sr/_snomed_dict.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom/sr
> copying pydicom/sr/_concepts_dict.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom/sr
> copying pydicom/sr/coding.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom/sr
> copying pydicom/sr/__init__.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom/sr
> copying pydicom/sr/codedict.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom/sr
> copying pydicom/sr/_cid_dict.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom/sr
> creating
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom/benchmarks
> copying pydicom/benchmarks/bench_rle_decode.py ->
> /<>/.pybuild/cpython3_3.11_pydicom/build/pydicom/benchmarks
> copying
Bug#1061319: proposed package update
Control: tags -1 + patch https://launchpad.net/ubuntu/+source/cadabra2/2.4.5.4-0ubuntu1
Processed: proposed package update
Processing control commands: > tags -1 + patch Bug #1061319 [src:cadabra2] cadabra2 ftbfs with Python 3.12 as default Added tag(s) patch. -- 1061319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054688: proposed package update
Here is what we came up with. Note that there's still one test hanging, which is disabled for now. https://launchpad.net/ubuntu/+source/gringo/5.6.2-0ubuntu1
Bug#1056854: marked as done (python-djvulibre: ftbfs with cython 3.0.x)
Your message dated Fri, 26 Jan 2024 12:20:55 + with message-id and subject line Bug#1056854: fixed in python-djvulibre 0.9.0-1 has caused the Debian Bug report #1056854, regarding python-djvulibre: ftbfs with cython 3.0.x to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1056854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-djvulibre Version: 0.8.8-3 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: cython3 [This bug is targeted to the upcoming trixie release] The package fails to build in a test rebuild on at least arm64 with cython 3.0.5, but succeeds to build with cython 0.29.36. Please update the package to build with cython 3.0.5 (available in experimental). If the package cannot be built with cython 3.0.5, please change the build dependency from cython3 to cython3-legacy (available now in unstable). There is no replacement for cython3-dbg. Build logs building with cython 3.0.5 can be found at https://people.debian.org/~stefanor/cython3/cython-3.0.5/ See also https://lists.debian.org/debian-python/2023/11/msg00034.html --- End Message --- --- Begin Message --- Source: python-djvulibre Source-Version: 0.9.0-1 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of python-djvulibre, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated python-djvulibre package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Jan 2024 12:51:58 +0100 Source: python-djvulibre Architecture: source Version: 0.9.0-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Alexandre Detiste Closes: 1042661 1056468 1056854 Changes: python-djvulibre (0.9.0-1) unstable; urgency=medium . * QA upload. . [ Alexandre Detiste ] * New upstream version 0.9.0 (Closes: #1056854, #1042661, #1056468) * switch to fork found via repology.com * update copyright & homepage . [ Yogeswaran Umasankar ] * Fixed override_dh_installdocs in rules to fit new upstream. * Included python3-wheel in d/control build depends. * Patch to fix doc conf.py setup module issue. * Included __init__.py in tests/ for autopkgtests + disabled test_export_ps. Checksums-Sha1: 8bbc14fa8a16720fa8f899f0e3297940c0509b68 2379 python-djvulibre_0.9.0-1.dsc 7cbc8c440304fd464ee6a68daeb827e866351261 86433 python-djvulibre_0.9.0.orig.tar.gz 9fb07b57f1a731342cb019035af427f80b731f3a 19876 python-djvulibre_0.9.0-1.debian.tar.xz 6073c446cccb9e804a5afb1359852e16577d1aab 11716 python-djvulibre_0.9.0-1_source.buildinfo Checksums-Sha256: 5decb53fef6e2ffe6d20bb41b13b684a3f4fc725c3159f0410f5c621614d10a1 2379 python-djvulibre_0.9.0-1.dsc 3e9763814d7671cc3f10dfa7cce50f44a642b19753e6d86bdbf3c0fbbeaa3031 86433 python-djvulibre_0.9.0.orig.tar.gz 753290d108932d2e23296761a22bd4b795b51353cadc22eeffeaec58ebe2bc46 19876 python-djvulibre_0.9.0-1.debian.tar.xz d2f2e80aabab85225e3a9f9db0dd3dbc9dd885778fbeb5bad0d2d9c5b91b82b8 11716 python-djvulibre_0.9.0-1_source.buildinfo Files: 2e9cbc9d9c93c497150f4f3db71bf4aa 2379 python optional python-djvulibre_0.9.0-1.dsc 3dad5a90363dd132228d26c94af05694 86433 python optional python-djvulibre_0.9.0.orig.tar.gz 025846eae29270ca671e3800ff295413 19876 python optional python-djvulibre_0.9.0-1.debian.tar.xz 5b5bbd4cd1f9f240d6c75e4c77016da6 11716 python optional python-djvulibre_0.9.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmWzn48RHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBq3Sw//b35A/6m7Ex2osKSm1dW60wZ0dndZKST9 rXVz+Q05Uh96fdM3JatXPMk4ovukwyY552+bOVGDXIel36U3PfJXcBJh4Hl1m8tA O78phfbBmAT5ucHxlcpMm0iXz0oyxlYauQyHzNHK2jZ3vc5pJ6OzK6XgMj0zdXRP wuClmczS8BFjNOrhoIAK93du09CAJ68wr7RJ0j1LqsEwn8tah5ky4gb/jgeY/SHI /qcEB9lttbR2IDMLAFfY9PoTrWKBVYFUEShzzImuifmfTlRur6DAkOSQC7ewz1ah 2ngvmr+s2JwLxe2MWwYRYPEYaei8AB5+H2ZIz16uXlkquYDhlbijOdRUEop2r1yc
Bug#1042661: marked as done (python-djvulibre: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')
Your message dated Fri, 26 Jan 2024 12:20:55 + with message-id and subject line Bug#1042661: fixed in python-djvulibre 0.9.0-1 has caused the Debian Bug report #1042661, regarding python-djvulibre: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042661 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-djvulibre Version: 0.8.8-3 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx7.1 Hi, python-djvulibre fails to build with Sphinx 7.1 and docutils 0.20, both of which are currently available in experimental. Relevant part (hopefully): > x86_64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g -fwrapv -O2 > -Wl,-z,relro -Wl,-z,now -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 > build/temp.linux-x86_64-3.11/build/temp.linux-x86_64-3.11/src/sexpr.o > -ldjvulibre -o /<>/djvu/sexpr.cpython-311-x86_64-linux-gnu.so > -pthread > http_proxy='127.0.0.1:9' python3 setup.py build_sphinx > /<>/setup.py:39: DeprecationWarning: The distutils package is > deprecated and slated for removal in Python 3.12. Use setuptools or check PEP > 632 for potential alternatives > import distutils.core > usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] >or: setup.py --help [cmd1 cmd2 ...] >or: setup.py --help-commands >or: setup.py cmd --help > > error: invalid command 'build_sphinx' > make[1]: *** [debian/rules:25: override_dh_installdocs] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/07/30/exp/python-djvulibre_0.8.8-3_unstable_sphinx-exp.log Please see [1] for Sphinx changelog and [2] for Docutils changelog. Also see [3] for the list of deprecated/removed APIs in Sphinx and possible alternatives to them. Some notable changes in Sphinx 6 and Sphinx 7: - Sphinx no longer includes jquery.js and underscore.js by default. Please use python3-sphinxcontrib.jquery package if you are using a custom template and it still needs jquery. - The setup.py build_sphinx command was removed. Please instead call sphinx-build or "python3 -m sphinx" directly. - For packages using the extlinks extension, the caption should contain exactly one "%s" placeholder (if caption is not None). In case you have questions, please Cc sph...@packages.debian.org on reply. [1]: https://www.sphinx-doc.org/en/master/changes.html [2]: https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt [3]: https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx7.1;users=python-modules-t...@lists.alioth.debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=sphinx7.1=python-modules-t...@lists.alioth.debian.org=1=1=1=1#results If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects --- End Message --- --- Begin Message --- Source: python-djvulibre Source-Version: 0.9.0-1 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of python-djvulibre, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated python-djvulibre package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Jan 2024 12:51:58 +0100 Source: python-djvulibre Architecture: source Version: 0.9.0-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Alexandre Detiste Closes: 1042661 1056468 1056854 Changes: python-djvulibre (0.9.0-1) unstable; urgency=medium . * QA upload. . [ Alexandre Detiste ] * New upstream version 0.9.0 (Closes: #1056854, #1042661, #1056468) * switch to fork found via repology.com
Bug#1056468: marked as done (python-djvulibre's autopkg tests fail with Python 3.12)
Your message dated Fri, 26 Jan 2024 12:20:55 +
with message-id
and subject line Bug#1056468: fixed in python-djvulibre 0.9.0-1
has caused the Debian Bug report #1056468,
regarding python-djvulibre's autopkg tests fail with Python 3.12
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1056468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-djvulibre
Version: 0.8.8-3
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
python-djvulibre's autopkg tests fail with Python 3.12:
[...]
202s autopkgtest [19:00:07]: test python3-djvu: [---
203s /usr/lib/python3/dist-packages/nose/plugins/manager.py:430:
DeprecationWarning: pkg_resources is deprecated as an API. See
https://setuptools.pypa.io/en/latest/pkg_resources.html
203s import pkg_resources
203s /usr/lib/python3/dist-packages/zombie_imp/__init__.py:1:
DeprecationWarning: the imp module was removed in favour of importlib.
Someone brought it back, but it's not a good idea to use it.
203s from .imp_3_11 import *
203s Failure: ModuleNotFoundError (No module named 'distutils') ... ERROR
203s /usr/lib/python3.12/unittest/case.py:580: RuntimeWarning:
TestResult has no addDuration method
203s warnings.warn("TestResult has no addDuration method",
203s Failure: ModuleNotFoundError (No module named 'distutils') ... ERROR
203s Failure: ModuleNotFoundError (No module named 'distutils') ... ERROR
203s
203s ==
203s ERROR: Failure: ModuleNotFoundError (No module named 'distutils')
203s --
203s Traceback (most recent call last):
203s File "/usr/lib/python3/dist-packages/nose/failure.py", line 39,
in runTest
203s raise self.exc_val.with_traceback(self.tb)
203s File "/usr/lib/python3/dist-packages/nose/loader.py", line 416,
in loadTestsFromName
203s module = self.importer.importFromPath(
203s ^
203s File "/usr/lib/python3/dist-packages/nose/importer.py", line 47,
in importFromPath
203s return self.importFromDir(dir_path, fqname)
203s
203s File "/usr/lib/python3/dist-packages/nose/importer.py", line 94,
in importFromDir
203s mod = load_module(part_fqname, fh, filename, desc)
203s
203s File "/usr/lib/python3/dist-packages/zombie_imp/imp_3_11.py",
line 238, in load_module
203s return load_source(name, filename, file)
203s^
203s File "/usr/lib/python3/dist-packages/zombie_imp/imp_3_11.py",
line 175, in load_source
203s module = _load(spec)
203s ^^^
203s File "", line 960, in _load
203s File "", line 929, in _load_unlocked
203s File "", line 994, in
exec_module
203s File "", line 488, in
_call_with_frames_removed
203s File
"/tmp/autopkgtest.2t28bh/autopkgtest_tmp/tests/test_const.py", line 32,
in
203s from tools import (
203s File "/tmp/autopkgtest.2t28bh/autopkgtest_tmp/tests/tools.py",
line 18, in
203s import distutils.spawn
203s ModuleNotFoundError: No module named 'distutils'
203s
203s ==
203s ERROR: Failure: ModuleNotFoundError (No module named 'distutils')
203s --
203s Traceback (most recent call last):
203s File "/usr/lib/python3/dist-packages/nose/failure.py", line 39,
in runTest
203s raise self.exc_val.with_traceback(self.tb)
203s File "/usr/lib/python3/dist-packages/nose/loader.py", line 416,
in loadTestsFromName
203s module = self.importer.importFromPath(
203s ^
203s File "/usr/lib/python3/dist-packages/nose/importer.py", line 47,
in importFromPath
203s return self.importFromDir(dir_path, fqname)
203s
203s File "/usr/lib/python3/dist-packages/nose/importer.py", line 94,
in importFromDir
203s mod = load_module(part_fqname, fh, filename, desc)
203s
203s File "/usr/lib/python3/dist-packages/zombie_imp/imp_3_11.py",
line 238, in load_module
203s return load_source(name, filename, file)
203s^
203s File
Processed (with 2 errors): fixed and closed
Processing commands for cont...@bugs.debian.org:
> fixed 1058109 0.10.1-4
Bug #1058109 [src:sphinx-gallery] sphinx-gallery: FTBFS: NameError: name 'iae'
is not defined
The source 'sphinx-gallery' and version '0.10.1-4' do not appear to match any
binary packages
Marked as fixed in versions sphinx-gallery/0.10.1-4.
> fixed 1042675 0.10.1-4
Bug #1042675 [src:sphinx-gallery] sphinx-gallery: FTBFS with Sphinx 7.1,
docutils 0.20: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.11 --system=custom "--test-args={interpreter} -m pytest
--ignore=sphinx_gallery/tests/test_full.py -k \"not
test_embed_code_links_get_data\" sphinx_gallery/tests" returned exit code 13
The source 'sphinx-gallery' and version '0.10.1-4' do not appear to match any
binary packages
Marked as fixed in versions sphinx-gallery/0.10.1-4.
> close 1058109
Bug #1058109 [src:sphinx-gallery] sphinx-gallery: FTBFS: NameError: name 'iae'
is not defined
Marked Bug as done
> close 1042675
Bug #1042675 [src:sphinx-gallery] sphinx-gallery: FTBFS with Sphinx 7.1,
docutils 0.20: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.11 --system=custom "--test-args={interpreter} -m pytest
--ignore=sphinx_gallery/tests/test_full.py -k \"not
test_embed_code_links_get_data\" sphinx_gallery/tests" returned exit code 13
Marked Bug as done
> Best,
Unknown command or malformed arguments to command.
> Nilesh
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1042675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042675
1058109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: ERROR: Unable to connect to servers to test latency.
Processing control commands: > severity -1 serious Bug #1024830 [speedtest-cli] ERROR: Unable to connect to servers to test latency. Severity set to 'serious' from 'important' -- 1024830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1061554 is normal, affects 1061554, affects 1061554
Processing commands for cont...@bugs.debian.org: > severity 1061554 normal Bug #1061554 [systemd] pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC namespacing: Resource temporarily unavailable Severity set to 'normal' from 'serious' > affects 1061554 src:pdns Bug #1061554 [systemd] pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC namespacing: Resource temporarily unavailable Added indication that 1061554 affects src:pdns > affects 1061554 src:pdns-recursor Bug #1061554 [systemd] pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC namespacing: Resource temporarily unavailable Added indication that 1061554 affects src:pdns-recursor > thanks Stopping processing here. Please contact me if you need assistance. -- 1061554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061554 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1059995: Re: Bug#1059995: pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC namespacing: Resource temporarily unavailable
Processing commands for cont...@bugs.debian.org:
> clone 1059995 -1
Bug #1059995 {Done: Chris Hofstaedtler } [src:pdns] pdns:
flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC
namespacing: Resource temporarily unavailable
Bug 1059995 cloned as bug 1061554
> reopen -1
Bug #1061554 {Done: Chris Hofstaedtler } [src:pdns] pdns:
flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC
namespacing: Resource temporarily unavailable
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions pdns/4.8.3-3.
> reassign -1 systemd
Bug #1061554 [src:pdns] pdns: flaky autopkgtest (host dependent): pdns.service:
Failed to set up IPC namespacing: Resource temporarily unavailable
Bug reassigned from package 'src:pdns' to 'systemd'.
No longer marked as found in versions pdns/4.8.3-2.
Ignoring request to alter fixed versions of bug #1061554 to the same values
previously set
> found -1 systemd/254.3-1
Bug #1061554 [systemd] pdns: flaky autopkgtest (host dependent): pdns.service:
Failed to set up IPC namespacing: Resource temporarily unavailable
Marked as found in versions systemd/254.3-1.
> forwarded -1 https://github.com/systemd/systemd/issues/31037
Bug #1061554 [systemd] pdns: flaky autopkgtest (host dependent): pdns.service:
Failed to set up IPC namespacing: Resource temporarily unavailable
Set Bug forwarded-to-address to
'https://github.com/systemd/systemd/issues/31037'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1059995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059995
1061554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1059995: Re: Bug#1059995: pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC namespacing: Resource temporarily unavailable
clone 1059995 -1 reopen -1 reassign -1 systemd found -1 systemd/254.3-1 forwarded -1 https://github.com/systemd/systemd/issues/31037 thanks Dear systemd Packagers, Paul Gevers noted that src:pdns's autopkgtests fail every so often on a large amd64 debci worker and on s390x workers. Apparently a similar problem can be seen in src:pdns-recursor's debci runs. As there is no pdns(-recursor) code running at this point, this seems to be a problem somewhere in the space of systemd <> lxc <> apparmor <> kernel. I've opened a bug with systemd upstream, unfortunately with very little info as I don't know how to provide additional info from within a debci run. Help with providing additional info would be very welcome. Thanks, Chris
Bug#1060848: marked as done (rust-isahc: Autopkgtest failures)
Your message dated Fri, 26 Jan 2024 10:06:23 +
with message-id
and subject line Bug#1060848: fixed in rust-isahc 1.7.2+ds-25
has caused the Debian Bug report #1060848,
regarding rust-isahc: Autopkgtest failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1060848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-isahc
Version: 1.7.2+ds-24
Severity: serious
Justification: fails to migrate to testing
X-Debbugs-Cc: werdah...@riseup.net
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
See
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-isahc/40410753/log.gz.
snip:
842s error: cannot determine resolution for the macro `mock`
842s--> tests/redirects.rs:268:9
842s |
842s 268 | mock! {
842s |
842s |
842s = note: import resolution is stuck, try simplifying macro imports
842s
842s error: cannot determine resolution for the macro `mock`
842s--> tests/redirects.rs:292:14
842s |
842s 292 | let m2 = mock! {
842s |
842s |
842s = note: import resolution is stuck, try simplifying macro imports
842s
842s error: cannot determine resolution for the macro `mock`
842s--> tests/redirects.rs:300:14
842s |
842s 300 | let m1 = mock! {
842s |
842s |
842s = note: import resolution is stuck, try simplifying macro imports
842s
842s error: could not compile `isahc` due to 3 previous errors
==
This blocks testing migration for rust-transmission-client, please fix
isahc accordingly.
best,
werdahias
- -- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: OpenRC (via /run/openrc), PID 1: init
LSM: AppArmor: enabled
-BEGIN PGP SIGNATURE-
iQJJBAEBCgAzFiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmWlU6EVHHdlcmRhaGlh
c0ByaXNldXAubmV0AAoJEBi9EGs7bFR1/BAQAK4PodKtnigscZNZi9NpEEDs56rT
qsheNo3a6AzaN/3uwpjfcN7otzMxarKmS+oPgNoEDId9q4zlS0zRAAL95jT2XrSq
VayXKyGJuiU0dw6V6J4wdjjBGDAs/NgSxNSaGnrKPOjDyLUgyJunp7iW/6Oiec6p
UnfTMx8RtuJbVICtpocvLr5RsDFfusRAlncnKZ5m3sILqPAQizTyohoy3/BJRSfh
aLmefKNvLikVSUYiwIeccG+Fyclp+O+LfNroMfHNbbEJHy0UMXZaYWZmfn/nD7F5
Id6wkBxYnckV5JXZ4xRMCBHq8cPHQMQOfLe0HOZEvFkAxBEICGs8nkbLb+HWup/1
ZczOX4thxoTqSypVI3ZuFFN3c3LWUFEzeOuWjcJsy+1vIa8Kp+Ivk0P3wzMp/DNj
AVMfsUE5pB5QjQ5lU4uCK43nPXSuElmhNAyMsow3+dxSpA/hwig+pmq9DMLbLVYf
75suhPWYx4UeVbrLEmY82dDT4kPOa8FdzmOxvN/z9JDD6MOPerynU+CqAlgzQvdm
lQNfPdbBLF2ZB73UP5YL+3GxfmSM0o15xR19REfs2aZf81GzBL2+OSW2s7efMo2t
p3xGjz2j9Osf8qMz7FuiAyidKRBhGstpZx6B3erPHm5pSKijrM+l/rKNW3jBh20i
NYzu/ciejRBoGBjf
=ccy6
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: rust-isahc
Source-Version: 1.7.2+ds-25
Done: Jonas Smedegaard
We believe that the bug you reported is fixed in the latest version of
rust-isahc, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1060...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Smedegaard (supplier of updated rust-isahc package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 26 Jan 2024 10:48:00 +0100
Source: rust-isahc
Architecture: source
Version: 1.7.2+ds-25
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard
Changed-By: Jonas Smedegaard
Closes: 1060848
Changes:
rust-isahc (1.7.2+ds-25) unstable; urgency=medium
.
* update patches
* build-depend unconditionally on test-only build-dependencies
(needed by cargo install)
* have autopgktest skip skip all but one test,
due to use of non-distributed crate testserver;
closes: bug#1060848, thanks to Matthias Geiger
* update dh-cargo fork
* update copyright info: update coverage
Checksums-Sha1:
e15803f0b84d62bdd18d613d2357bef883bcd7f6 4144 rust-isahc_1.7.2+ds-25.dsc
Bug#1061551: sndfile-tools: Please disable autopkgtest on armhf
Source: sndfile-tools Version: 1.5-2 Severity: serious User: debian-...@lists.debian.org Usertags: 32bit-stackclash Tags: patch Hi, the autopkgtest "upstream-tests" is currently failing on armhf due to valgrind bug https://bugs.debian.org/1061496. tests/test-wrapper.sh: line 15: 2957099 Segmentation fault $valgrind $@ > $logfile 2>&1 valgrind /usr/bin/sndfile-generate-chirp : ok valgrind /usr/bin/sndfile-resample: 1 errors, 0 bytes leaked valgrind /usr/bin/sndfile-resample: 1 errors, 0 bytes leaked valgrind /usr/bin/sndfile-resample: 1 errors, 0 bytes leaked valgrind /usr/bin/sndfile-spectrogram : 0 errors, 280 bytes leaked valgrind /usr/bin/sndfile-waveform: 0 errors, 336 bytes leaked Please disable the test for now, it can be re-enabled once the valgrind issue is fixed. Patch attached. Thanks, Emanuele diff -Nru sndfile-tools-1.5/debian/changelog sndfile-tools-1.5/debian/changelog --- sndfile-tools-1.5/debian/changelog 2022-09-28 18:49:01.0 +0200 +++ sndfile-tools-1.5/debian/changelog 2024-01-26 11:02:37.0 +0100 @@ -1,3 +1,10 @@ +sndfile-tools (1.5-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Don't run autopkgtests on armhf due to valgrind bug #1061496. (Closes: #XXX) + + -- Emanuele Rocca Fri, 26 Jan 2024 11:02:37 +0100 + sndfile-tools (1.5-2) unstable; urgency=medium [ Debian Janitor ] diff -Nru sndfile-tools-1.5/debian/tests/control sndfile-tools-1.5/debian/tests/control --- sndfile-tools-1.5/debian/tests/control 2022-09-28 18:49:01.0 +0200 +++ sndfile-tools-1.5/debian/tests/control 2024-01-26 11:02:36.0 +0100 @@ -2,3 +2,4 @@ Depends: valgrind, @, +Architecture: !armhf
Bug#1056431: numpydoc's autopkg tests fail with Python 3.12
Control: reopen -1
Dear Maintainer,
autopkg tests still fail [1] with this error:
49s = test session starts
==
49s platform linux -- Python 3.11.7, pytest-7.4.4, pluggy-1.3.0
49s rootdir: /tmp/autopkgtest-lxc.4al_chdi/downtmp/build.77I/src
49s configfile: pyproject.toml
49s plugins: cov-4.1.0
49s collected 286 items
49s
49s numpydoc/numpydoc.py . [
0%]
49s numpydoc/validate.py . [
0%]
49s numpydoc/tests/test_docscrape.py ... [
14%]
49s . [
21%]
50s numpydoc/tests/test_full.py FF... [
23%]
50s numpydoc/tests/test_main.py ... [
25%]
51s numpydoc/tests/test_numpydoc.py . [
30%]
51s numpydoc/tests/test_validate.py [
44%]
51s x..x [
69%]
51s ... [
73%]
51s numpydoc/tests/test_xref.py [
88%]
52s ... [
95%]
52s numpydoc/tests/hooks/test_utils.py . [
97%]
52s numpydoc/tests/hooks/test_validate_hook.py
[100%]
52s
52s === FAILURES
===
52s _ test_MyClass
_
52s
52s sphinx_app =
52s
52s def test_MyClass(sphinx_app):
52s """Test that class documentation is reasonable."""
52s src_dir, out_dir = sphinx_app.srcdir, sphinx_app.outdir
52s class_rst = op.join(src_dir, "generated",
"numpydoc_test_module.MyClass.rst")
52s with open(class_rst) as fid:
52s rst = fid.read()
52s assert r"numpydoc\_test\_module" in rst # properly escaped
52s class_html = op.join(out_dir, "generated",
"numpydoc_test_module.MyClass.html")
52s with open(class_html) as fid:
52s html = fid.read()
52s # ensure that no autodoc weirdness ($) occurs
52s assert "$self" not in html
52s assert "/," not in html
52s assert "__init__" in html # inherited
52s # escaped * chars should no longer be preceded by \'s,
52s # if we see a \* in the output we know it's incorrect:
52s assert r"\*" not in html
52s # "self" should not be in the parameter list for the class:
52s assert "self," not in html
52s # check xref was embedded properly (dict should link using xref):
52s > assert "stdtypes.html#dict" in html
52s E assert 'stdtypes.html#dict' in '\n\n\n \n \n Page
source\n \n\n \n\n \n \n'
52s
52s class_html =
'/tmp/pytest-of-debci/pytest-0/root/_build/html/generated/numpydoc_test_module.MyClass.html'
52s class_rst =
'/tmp/pytest-of-debci/pytest-0/root/generated/numpydoc_test_module.MyClass.rst'
52s fid = <_io.TextIOWrapper
name='/tmp/pytest-of-debci/pytest-0/root/_build/html/generated/numpydoc_test_module.MyClass.html'
mode='r' encoding='UTF-8'>
52s html = '\n\n\n \n \n Page
source\n \n\n \n\n \n \n'
52s out_dir = _StrPath('/tmp/pytest-of-debci/pytest-0/root/_build/html')
52s rst =
'\ufeffnumpydoc\\_test\\_module.MyClass\n==\n\n..
currentmodule:: numpydoc_test_module\n\n...bric:: Methods\n\n ..
autosummary::\n \n
~MyClass.__init__\n ~MyClass.example\n \n \n\n \n \n '
52s sphinx_app =
52s src_dir = _StrPath('/tmp/pytest-of-debci/pytest-0/root')
52s
52s numpydoc/tests/test_full.py:62: AssertionError
52s Captured stdout setup
-
52s [01mRunning Sphinx v7.2.6[39;49;00m
52s [01mmaking output directory... [39;49;00mdone
52s loading intersphinx inventory from
/usr/share/doc/python3/html/objects.inv...
52s [autosummary] generating autosummary for: index.rst
52s [autosummary] generating autosummary for:
/tmp/pytest-of-debci/pytest-0/root/generated/numpydoc_test_module.MyClass.rst,
/tmp/pytest-of-debci/pytest-0/root/generated/numpydoc_test_module.my_function.rst
52s [01mbuilding [mo]: [39;49;00mtargets for 0 po files that are out of date
52s [01mwriting output... [39;49;00m
52s [01mbuilding [html]: [39;49;00mtargets for 1 source files that are out
of date
52s [01mupdating environment: [39;49;00m[new config] 3 added, 0 changed, 0
removed
52s [2K[01mreading sources... [39;49;00m[ 33%]
[35mgenerated/numpydoc_test_module.MyClass[39;49;00m
[2K[01mreading sources...
Processed: Re: numpydoc's autopkg tests fail with Python 3.12
Processing control commands:
> reopen -1
Bug #1056431 {Done: Chiara Marmo } [src:numpydoc]
numpydoc's autopkg tests fail with Python 3.12
Bug #1058407 {Done: Chiara Marmo } [src:numpydoc]
numpydoc: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.12 3.11" returned exit code 13
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions numpydoc/1.6.0-1.
No longer marked as fixed in versions numpydoc/1.6.0-1.
--
1056431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056431
1058407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1061546: srcpd: installs file into aliased location
Processing control commands: > severity -1 serious Bug #1061546 [src:srcpd] srcpd: installs file into aliased location Severity set to 'serious' from 'important' -- 1061546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061546 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061344: emboss-lib: identified for time_t transition but no ABI in shlibs
Hi Charles, I wonder how we can properly solve this bug. In the early stage of Emboss packaging obviously the packages libajax6, libajax6-dev, libnucleus6, libnucleus6-dev existed (thus the remaining Conflicts/Replaces on emboss-lib which can probably be removed right now). I wonder whether we should restore those single library package per shared library + devel package, merge static+shared library in one package or even merge libacd 6 emboss-lib (>= 6.6.0+dfsg) libajax 6 emboss-lib (>= 6.6.0+dfsg) libajaxdb 6 emboss-lib (>= 6.6.0+dfsg) libajaxg 6 emboss-lib (>= 6.6.0+dfsg) libensembl 6 emboss-lib (>= 6.6.0+dfsg) libnucleus 6 emboss-lib (>= 6.6.0+dfsg) in libemboss6 libepcre 7 emboss-lib (>= 6.6.0+dfsg) in libemboss-pcre7 (ugly since its a code copy of pcre3 but well, that's another battle field) and libeplplot 3 emboss-lib (>= 6.6.0+dfsg) in libemboss-plplot3 to express the proper sonames inside the library package names. Any more sensible suggestion is pretty welcome. Kind regards Andreas. -- http://fam-tille.de
Bug#1059995: Re: Bug#1059995: pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC namespacing: Resource temporarily unavailable
Hi Paul, * Paul Gevers [240104 18:14]: > Can you figure out decent numbers for these? Below I printed the output of > lsipc and AFAICT SHMMAX is already pretty big ;) (and the same on all our > hosts, which is also true for MSGMAX). > > On the other hand, $(ipcs -a) doesn't show anything on the host, not even if > I let it run in a while-loop (1 second interval) while I schedule the test > of pdns. So, could this be a bug in systemd (which you claim below should be > handeling this) or is this just not really supported in lxc and do you need > a full VM. Because it works elsewhere, I feel more like a bug, and it would > not be the first instance where code fails to properly handle 64 cores or > 256GB or RAM. Likely, but it is probably in systemd or in lxc or in apparmor or elsewhere. > > > > I wouldn't know what to do about this, its not really under the > > > > control of src:pdns. > > > > > > Well, maybe check for it and fail gracefully? > > > > But how? systemd sets up the IPC namespace. > > exit with 77 when you detect problems and add the skippable restriction. I see this "works", but now the tests fail after one try on the problematic worker and then are never retried. Can this please be fixed? Thanks, Chris
Processed: Just adding a blocker for a new upload as upstream tag
Processing control commands: > tags -1 upstream Bug #1056813 [src:macs] macs: ftbfs with cython 3.0.x Added tag(s) upstream. > forwarded -1 https://github.com/macs3-project/MACS/issues/615 Bug #1056813 [src:macs] macs: ftbfs with cython 3.0.x Set Bug forwarded-to-address to 'https://github.com/macs3-project/MACS/issues/615'. -- 1056813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056813 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056813: Just adding a blocker for a new upload as upstream tag
Control: tags -1 upstream Control: forwarded -1 https://github.com/macs3-project/MACS/issues/615 This is no issue about the topic of this bug report (cython) but rather an issue opened upstream to solve the problem which prevents us uploading latest macs3. Kind regards Andreas. -- http://fam-tille.de
Bug#1059256: marked as done (falcosecurity-libs: CVE-2023-49287)
Your message dated Fri, 26 Jan 2024 08:34:48 + with message-id and subject line Bug#1059256: fixed in falcosecurity-libs 0.14.1-1 has caused the Debian Bug report #1059256, regarding falcosecurity-libs: CVE-2023-49287 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1059256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: falcosecurity-libs X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for falcosecurity-libs. CVE-2023-49287[0]: | TinyDir is a lightweight C directory and file reader. Buffer | overflows in the `tinydir_file_open()` function. This vulnerability | has been patched in version 1.2.6. https://github.com/cxong/tinydir/security/advisories/GHSA-jf5r-wgf4-qhxf https://github.com/cxong/tinydir/commit/8124807260735a837226fa151493536591f6715d https://github.com/hnsecurity/vulns/blob/main/HNS-2023-04-tinydir.txt falcosecurity-libs embeds a copy of tinydir, if it's not used to open files from potentially untrusted paths, feel free to downgrade. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-49287 https://www.cve.org/CVERecord?id=CVE-2023-49287 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: falcosecurity-libs Source-Version: 0.14.1-1 Done: Dima Kogan We believe that the bug you reported is fixed in the latest version of falcosecurity-libs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dima Kogan (supplier of updated falcosecurity-libs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 24 Jan 2024 22:25:38 -0800 Source: falcosecurity-libs Binary: falcosecurity-scap-dkms libfalcosecurity0 libfalcosecurity0-dbgsym libfalcosecurity0-dev Architecture: source all amd64 Version: 0.14.1-1 Distribution: unstable Urgency: medium Maintainer: Dima Kogan Changed-By: Dima Kogan Description: falcosecurity-scap-dkms - Kernel driver for Falco and Sysdig libfalcosecurity0 - Core libraries for Falco and Sysdig libfalcosecurity0-dev - Core libraries for Falco and Sysdig Closes: 1056157 1057449 1059256 Changes: falcosecurity-libs (0.14.1-1) unstable; urgency=medium . * New upstream release (Closes: #1059256, #1057449, #1056157) Checksums-Sha1: f3dbffc3ae82bc152b11cd0ab22bb2c1d5273ed6 2571 falcosecurity-libs_0.14.1-1.dsc 83631d98843044cfc00a59b1914c47f7dbef672c 3866049 falcosecurity-libs_0.14.1.orig.tar.gz b55d4c4c02b352ee075e84554c68109dc0c4d2eb 9292 falcosecurity-libs_0.14.1-1.debian.tar.xz 3a577a15b7480e8dab36831f2ba0f1f0968ed882 14859 falcosecurity-libs_0.14.1-1_amd64.buildinfo a5b143fed07e0aebcd03c6f0e885aca8f106a4c7 135384 falcosecurity-scap-dkms_0.14.1-1_all.deb b14a187d154ea0f86b3ddfd8bda2411226d65260 24216508 libfalcosecurity0-dbgsym_0.14.1-1_amd64.deb 1f1108c399b9fe5761c47bb693326a1c46ea2277 216084 libfalcosecurity0-dev_0.14.1-1_amd64.deb 10f5660ae173d372b3fceed43ee859578c10bf46 1545572 libfalcosecurity0_0.14.1-1_amd64.deb Checksums-Sha256: d91a50aa01278564c6b5aa5147660b05ee024d3a3413b8f928bd9e22f98c38e3 2571 falcosecurity-libs_0.14.1-1.dsc defdea24bf3b176c63f10900d3716fe4373151965cc09d3fe67a31a3a9af0b13 3866049 falcosecurity-libs_0.14.1.orig.tar.gz 29329965a712448b4ef8301777f85e31cb1358ff570e12eb3d565345c0c17064 9292 falcosecurity-libs_0.14.1-1.debian.tar.xz b8feb322582f806c2f086f8a2e563ccd0b4bfeaa0c41808d9f93ee82550387df 14859 falcosecurity-libs_0.14.1-1_amd64.buildinfo fcfecd4f5a26f6dd76b079e8c9431f770e8a03e92ef519fc346b9b764849e435 135384 falcosecurity-scap-dkms_0.14.1-1_all.deb 9b15fbd7960a4d9520826c791834e5902323cdaf076b700a1af5436723fd8db1 24216508 libfalcosecurity0-dbgsym_0.14.1-1_amd64.deb a7f3911f2af80e7ea9c839ca28bb15ae39e4c4f2d9ad34a010bc95a111bc66b4 216084 libfalcosecurity0-dev_0.14.1-1_amd64.deb
Bug#1057449: marked as done (falcosecurity-scap-dkms: module build fails for Linux 6.6: ppm_fillers.c:1438:63: error: 'struct inode' has no member named 'i_ctime')
Your message dated Fri, 26 Jan 2024 08:34:48 + with message-id and subject line Bug#1057449: fixed in falcosecurity-libs 0.14.1-1 has caused the Debian Bug report #1057449, regarding falcosecurity-scap-dkms: module build fails for Linux 6.6: ppm_fillers.c:1438:63: error: 'struct inode' has no member named 'i_ctime' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1057449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: falcosecurity-scap-dkms Version: 0.11.3+repack-6 Severity: important Hi, falcosecurity-scap-dkms fails to build a module for Linux 6.6 that was just uploaded to experimental: DKMS make.log for scap-0.11.3 for kernel 6.6-amd64 (x86_64) Tue Dec 5 08:39:34 UTC 2023 make: Entering directory '/usr/src/linux-headers-6.6-amd64' CC [M] /var/lib/dkms/scap/0.11.3/build/main.o CC [M] /var/lib/dkms/scap/0.11.3/build/dynamic_params_table.o CC [M] /var/lib/dkms/scap/0.11.3/build/fillers_table.o CC [M] /var/lib/dkms/scap/0.11.3/build/flags_table.o CC [M] /var/lib/dkms/scap/0.11.3/build/ppm_events.o CC [M] /var/lib/dkms/scap/0.11.3/build/ppm_fillers.o CC [M] /var/lib/dkms/scap/0.11.3/build/event_table.o CC [M] /var/lib/dkms/scap/0.11.3/build/syscall_table32.o CC [M] /var/lib/dkms/scap/0.11.3/build/syscall_table64.o CC [M] /var/lib/dkms/scap/0.11.3/build/ppm_cputime.o CC [M] /var/lib/dkms/scap/0.11.3/build/ppm_tp.o CC [M] /var/lib/dkms/scap/0.11.3/build/socketcall_to_syscall.o /var/lib/dkms/scap/0.11.3/build/ppm_fillers.c: In function 'f_proc_startupdate': /var/lib/dkms/scap/0.11.3/build/ppm_fillers.c:1438:63: error: 'struct inode' has no member named 'i_ctime'; did you mean 'i_atime'? 1438 | ctime = file_inode(exe_file)->i_ctime.tv_sec * (uint64_t) 10 + file_inode(exe_file)->i_ctime.tv_nsec; | ^~~ | i_atime /var/lib/dkms/scap/0.11.3/build/ppm_fillers.c:1438:126: error: 'struct inode' has no member named 'i_ctime'; did you mean 'i_atime'? 1438 | ctime = file_inode(exe_file)->i_ctime.tv_sec * (uint64_t) 10 + file_inode(exe_file)->i_ctime.tv_nsec; | ^~~ | i_atime make[2]: *** [/usr/src/linux-headers-6.6-common/scripts/Makefile.build:248: /var/lib/dkms/scap/0.11.3/build/ppm_fillers.o] Error 1 make[2]: *** Waiting for unfinished jobs make[1]: *** [/usr/src/linux-headers-6.6-common/Makefile:1938: /var/lib/dkms/scap/0.11.3/build] Error 2 make: *** [/usr/src/linux-headers-6.6-common/Makefile:246: __sub-make] Error 2 make: Leaving directory '/usr/src/linux-headers-6.6-amd64' Andreas --- End Message --- --- Begin Message --- Source: falcosecurity-libs Source-Version: 0.14.1-1 Done: Dima Kogan We believe that the bug you reported is fixed in the latest version of falcosecurity-libs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1057...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dima Kogan (supplier of updated falcosecurity-libs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 24 Jan 2024 22:25:38 -0800 Source: falcosecurity-libs Binary: falcosecurity-scap-dkms libfalcosecurity0 libfalcosecurity0-dbgsym libfalcosecurity0-dev Architecture: source all amd64 Version: 0.14.1-1 Distribution: unstable Urgency: medium Maintainer: Dima Kogan Changed-By: Dima Kogan Description: falcosecurity-scap-dkms - Kernel driver for Falco and Sysdig libfalcosecurity0 - Core libraries for Falco and Sysdig libfalcosecurity0-dev - Core libraries for Falco and Sysdig Closes: 1056157 1057449 1059256 Changes: falcosecurity-libs (0.14.1-1) unstable; urgency=medium . * New upstream release (Closes:
