Bug#1024674: libphonenumber8: breaks Evolution
I did the same and it works. This mail will be send from Evolution > This issue goes away for me after a rebuild of src:evolution-data- server > and installing the freshly rebuilt libebook-contacts-1.2-4. > > Maybe we can kick off a rebuild via the transition. If not that, would > you be willing to do a sourceful upload Jeremy?
Processed: Re: dxf2gcode: FTBFS: dh_usrlocal: error: debian/dxf2gcode/usr/local/bin/dxf2gcode is not a directory
Processing control commands: > tags -1 + patch Bug #1022387 [src:dxf2gcode] dxf2gcode: FTBFS: dh_usrlocal: error: debian/dxf2gcode/usr/local/bin/dxf2gcode is not a directory Added tag(s) patch. -- 1022387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022387: dxf2gcode: FTBFS: dh_usrlocal: error: debian/dxf2gcode/usr/local/bin/dxf2gcode is not a directory
Control: tags -1 + patch Look like setuptool changed behaviour, and now require --install-data=/usr and --install-scripts=/usr/bin to function properly. This patch should fix the issue: diff --git a/debian/rules b/debian/rules index c86b1a6..2d5dbe3 100755 --- a/debian/rules +++ b/debian/rules @@ -17,4 +17,4 @@ override_dh_auto_build: python3 ./st-setup.py build override_dh_auto_install: - python3 ./st-setup.py install --prefix=usr --install-lib usr/lib/python3/dist-packages --root=debian/dxf2gcode + python3 ./st-setup.py install --root=debian/dxf2gcode --prefix=/usr --install-lib /usr/lib/python3/dist-packages --install-data=/usr --install-scripts=/usr/bin I lack commit rights, so I can not push the fix to git myself. -- Happy hacking Petter Reinholdtsen
Bug#1024674: libphonenumber8: breaks Evolution
On Wed, Nov 23, 2022 at 06:28:04AM +0100, Christoph Anton Mitterer wrote: > On Tue, 2022-11-22 at 21:11 -0800, tony mancill wrote: > > I guess it must be doing some kind of dynamic loading stuff? OTOH, it > seems to be just linked as a plain shared lib: > $ libtree /usr/lib/x86_64-linux-gnu/libebook-contacts-1.2.so.4.0.0 > libebook-contacts-1.2.so.4 > ├── libedataserver-1.2.so.27 [ld.so.conf] > ... > ├── libphonenumber.so.8 [ld.so.conf] > │ ├── libprotobuf.so.23 [ld.so.conf] > │ │ └── libz.so.1 [ld.so.conf] > │ ├── libabsl_throw_delegate.so.20220623 [ld.so.conf] > │ ├── libabsl_strings.so.20220623 [ld.so.conf] > │ │ ├── libabsl_strings_internal.so.20220623 [ld.so.conf] > │ │ │ └── libabsl_raw_logging_internal.so.20220623 [ld.so.conf] > │ │ ├── libabsl_raw_logging_internal.so.20220623 [ld.so.conf] > │ │ └── libabsl_throw_delegate.so.20220623 [ld.so.conf] > │ ├── libabsl_raw_hash_set.so.20220623 [ld.so.conf] > │ ├── libabsl_hash.so.20220623 [ld.so.conf] > │ │ ├── libabsl_city.so.20220623 [ld.so.conf] > │ │ └── libabsl_low_level_hash.so.20220623 [ld.so.conf] > │ ├── libicui18n.so.72 [ld.so.conf] > │ └── libicuuc.so.72 [ld.so.conf] > ... > > > Yes... at least evolution, but that's the only thing I have, which > depends on it. I notice that libebook-contacts wasn't part of of the protobuf transition [1], but it seems like it should have been a level 3 dependency. I'm not sure whether that's an issue with the transition tooling or if we're missing sufficient linkage between the packages. [1] https://release.debian.org/transitions/html/auto-protobuf.html > Maybe we should increase the severity, so that people will see it at > least via apt-listbugs? Ah, that's a good idea if we want to notify folks not to install libphonenumber8. Perhaps I shouldn't have reassigned the bug to evolution-data-server. Maybe we should create a new bug (or clone this one) and assign it to libphonenumber8?
Bug#1021754: marked as done (rust-zoxide: build-dependencies unsatisfiable.)
Your message dated Wed, 23 Nov 2022 06:19:13 + with message-id and subject line Bug#1021754: fixed in rust-zoxide 0.4.3-5 has caused the Debian Bug report #1021754, regarding rust-zoxide: build-dependencies unsatisfiable. 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.) -- 1021754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021754 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rust-zoxide Version: 0.4.3-4 Severity: serious The rust-zoxide package depends on version 0.2 of the float-ord crate, but testing/unstable now has version 0.3 Unfortunately when I try to prepare an update with debcargo I get. REALVER=0.4.3 SOURCEONLY=1 DEBFULLNAME="Peter Michael Green" DEBEMAIL=plugw...@debian.org ./update.sh zoxide Updating crates.io index Downloaded zoxide v0.8.3 debcargo failed: failed to parse manifest at `/root/.cargo/registry/src/github.com-1ecc6299db9ec823/zoxide-0.8.3/Cargo.toml` Caused by: feature `strip` is required The package requires the Cargo feature called `strip`, but that feature is not stabilized in this version of Cargo (1.56.0). Consider trying a more recent nightly release. See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#profile-strip-option for more information about the status of this feature. ./update.sh: abort: couldn't find crate zoxide --- End Message --- --- Begin Message --- Source: rust-zoxide Source-Version: 0.4.3-5 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-zoxide, 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 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-zoxide 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: Wed, 23 Nov 2022 05:52:50 + Source: rust-zoxide Architecture: source Version: 0.4.3-5 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 1021754 Changes: rust-zoxide (0.4.3-5) unstable; urgency=medium . * Team upload. * Package zoxide 0.4.3 from crates.io using debcargo 2.6.0 * Bump float-ord dependency to 0.3 (Closes: #1021754). Checksums-Sha1: 9d316fb6b894945d803a6dcee035a422a66da752 2474 rust-zoxide_0.4.3-5.dsc af0c60e7276bf21f7f6d578268f5e9661efee048 3224 rust-zoxide_0.4.3-5.debian.tar.xz 8714c3e2e7ced7c047d6a1ff599c8b1899932c1e 13889 rust-zoxide_0.4.3-5_source.buildinfo Checksums-Sha256: abce704abace5090b569e8aa867d0503d0b558fafc75b2c61036ca306288d447 2474 rust-zoxide_0.4.3-5.dsc 5f1d68b96c4fca548c2cfc75f7d81ac1b364727fa3af10eadc57fcbb70d610cf 3224 rust-zoxide_0.4.3-5.debian.tar.xz f133a4e1be23e7d9c21bbf48ecc8e2e0b6da5327cc98eaa3fe9d297014474766 13889 rust-zoxide_0.4.3-5_source.buildinfo Files: c481b94b5d43b3111ac2563319ffc7f8 2474 utils optional rust-zoxide_0.4.3-5.dsc 1a2a2c9ac2666eb91770746c996e5cac 3224 utils optional rust-zoxide_0.4.3-5.debian.tar.xz d3d653fd825b8c77a7086343251876dd 13889 utils optional rust-zoxide_0.4.3-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmN9uJEUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XuTrw//ZrWgV649ARkqAtqCUOuqj94u1Bkd YkJNxiO4TH9qTPdmCqeVMQUESe09CFInzI/EdtXkILTfk7z78hHQRQHjDdLxhm/D vxPHc82v5biBp2uHVye41sBTV2HDeF/lPIW9UVJCYXmGkKimGvi2U5FNLrgnI3z0 TERzuuBvd3vW7uEzOOa+zlLiFAAI4q+Aqx5A9rDTh0yW5tOlyJEG/wOErtLgCgw0 iVLoda5Lt2K2VLwDQOJy5PRQKwnZQr86Rrn3jZFR/qowyvLSu9FYXmsYLjOm5VSa cc3MT5p+XQ87cJpCCfaTb83gx2cqA+FDbTgHBm1+GDuF0eEVseytpiTH+igv0AhD UU+tRIEiB6v57Turu7MV8c4y/qMiJ6SNsFpWejGM8CaN0VJcoWyHcmSHWhnY6AH6 +iEbn4mnxEvxxA6ue6D1MoesR+SFTLNwDfNt/MwWLOpX2Q9xdwVe/DAPP85YLamW uzyyY8drrVZEAB2FnzTG4bAjzaYayQLRmKc4V7JrumZQ8vOKduZ1PdDj0UWBwq5j cpPq/AHbKsOPJGivIF1SDuQrOi1FguHwSG+Vth6by8DSA+1RSZmB8e9qu8ntP+fd i0QkYE05iQZT2R/DQsncc+csewwQv5QMgm54Ph02aoStPmq8zo3sXrvADGekZYAA mBFYIbO9Maq1LYQ= =o9e3 -END PGP SIGNATURE End Message ---
Bug#1017621: seahorse-nautilus: Fails to build with Nautilus 43
On 2022-08-18 Jeremy Bicha wrote: > Source: seahorse-nautilus [...] > The newest release of Nautilus, version 43, has switched to GTK4 and > includes major changes in the extensions API. > seahorse-nautilus will need to be converted to GTK4 and make other changes > for the new version. > Nautilus 43 is available in Debian Experimental. When we upload > nautilus 43 to Debian Unstable, we will need to remove > seahorse-nautilus from Testing unless this bug is fixed, because the > package will no longer build from source. Hello, as of today seahorse-nautilus actually FTBFS. It fails to locate gpgme (gpgme-config was dropped, superseded by pkg-config). Find attached a patch to fix this. Even with this change it later fails with checking for libnautilus-extension >= 2.12.0 glib-2.0 >= 2.10.0... no (There is now a libnautilus-extension-4.pc). cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' --- seahorse-nautilus-3.11.92.orig/configure.ac +++ seahorse-nautilus-3.11.92/configure.ac @@ -87,41 +87,7 @@ if test "$DO_CHECK" = "yes"; then fi fi -ok="no" -min_gpgme_version=1.0.0 -AC_PATH_PROG(GPGME_CONFIG, gpgme-config, "failed") -if test $GPGME_CONFIG != "failed" ; then - AC_MSG_CHECKING(for GPGME - version >= $min_gpgme_version) - req_major=`echo $min_gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\1/'` - req_minor=`echo $min_gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\2/'` - req_micro=`echo $min_gpgme_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\3/'` - gpgme_config_version=`$GPGME_CONFIG --version` - major=`echo $gpgme_config_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\1/'` - minor=`echo $gpgme_config_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\2/'` - micro=`echo $gpgme_config_version | \ - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\3/'` - - if test "$major" -eq "$req_major"; then - if test "$minor" -ge "$req_minor"; then - if test "$micro" -ge "$req_micro"; then -ok="yes" - fi - fi - fi -fi - -if test $ok = "yes"; then - GPGME_CFLAGS=`$GPGME_CONFIG --cflags` - GPGME_LIBS=`$GPGME_CONFIG --libs` - AC_MSG_RESULT(yes) -else - AC_MSG_ERROR(GPGME $min_gpgme_version or later needed) -fi +PKG_CHECK_MODULES(GPGME, [gpgme >= 1.0.0]) SEAHORSE_CFLAGS="$SEAHORSE_CFLAGS $GPGME_CFLAGS" SEAHORSE_LIBS="$SEAHORSE_LIBS $GPGME_LIBS" @@ -298,6 +264,6 @@ nautilus-ext/Makefile echo " GnuPG Version: $gnupg_version -GPGME Version: $gpgme_config_version +GPGME Version: $GPGME_VERSION Notification Support:$enable_libnotify "
Processed: protobuf: autopkgtest failure (error: file not found: com/example/tutorial/AddressBookProtos.java)
Processing control commands: > block 1023535 by -1 Bug #1023535 [release.debian.org] transition: protobuf 1023535 was blocked by: 1022248 1018945 1023535 was not blocking any bugs. Added blocking bug(s) of 1023535: 1024677 -- 1023535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023535 1024677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024677 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024677: protobuf: autopkgtest failure (error: file not found: com/example/tutorial/AddressBookProtos.java)
Source: protobuf Version: 3.21.9-3 Severity: serious Tags: upstream patch Control: block 1023535 by -1 Dear Maintainer, The autopkgtest for your package is failing: autopkgtest [02:27:53]: test simple: [--- *** Building example programs protoc $PROTO_PATH --cpp_out=. --java_out=. --python_out=. addressbook.proto pkg-config --cflags protobuf # fails if protobuf is not installed c++ -std=c++11 add_person.cc addressbook.pb.cc -o add_person_cpp `pkg-config --cflags --libs protobuf` pkg-config --cflags protobuf # fails if protobuf is not installed c++ -std=c++11 list_people.cc addressbook.pb.cc -o list_people_cpp `pkg-config --cflags --libs protobuf` javac -cp $CLASSPATH AddPerson.java ListPeople.java com/example/tutorial/AddressBookProtos.java error: file not found: com/example/tutorial/AddressBookProtos.java Usage: javac use --help for a list of possible options make: *** [Makefile:66: javac_middleman] Error 2 https://ci.debian.net/data/autopkgtest/unstable/amd64/p/protobuf/28586956/log.gz The attached patch fixes the issue by correcting the paths in the Makefile. Kind Regards, Bas --- a/examples/Makefile 2022-10-26 19:50:48.0 +0200 +++ b/examples/Makefile 2022-11-23 07:07:29.963242439 +0100 @@ -13,8 +13,8 @@ clean: rm -f add_person_cpp list_people_cpp add_person_java list_people_java add_person_python list_people_python - rm -f javac_middleman AddPerson*.class ListPeople*.class com/example/tutorial/*.class - rm -f protoc_middleman addressbook.pb.cc addressbook.pb.h addressbook_pb2.py com/example/tutorial/AddressBookProtos.java + rm -f javac_middleman AddPerson*.class ListPeople*.class com/example/tutorial/protos/*.class + rm -f protoc_middleman addressbook.pb.cc addressbook.pb.h addressbook_pb2.py com/example/tutorial/protos/*.java rm -f *.pyc rm -f go/tutorialpb/*.pb.go add_person_go list_people_go rm -f protoc_middleman_dart dart_tutorial/*.pb*.dart @@ -63,7 +63,7 @@ cd go && go test ./cmd/list_people javac_middleman: AddPerson.java ListPeople.java protoc_middleman - javac -cp $$CLASSPATH AddPerson.java ListPeople.java com/example/tutorial/AddressBookProtos.java + javac -cp $$CLASSPATH AddPerson.java ListPeople.java com/example/tutorial/protos/*.java @touch javac_middleman add_person_java: javac_middleman
Bug#1022413: marked as done (sqlmodel: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13)
Your message dated Wed, 23 Nov 2022 06:04:17 +
with message-id
and subject line Bug#1022413: fixed in sqlmodel 0.0.8-1
has caused the Debian Bug report #1022413,
regarding sqlmodel: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.10 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.)
--
1022413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sqlmodel
Version: 0.0.6-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # test_create_db_and_table: converage cant find docs_src so this test fails
> PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="PYTHONPATH=/<>
> {interpreter} -m pytest -k 'not test_create_db_and_table' " dh_auto_test
> pybuild --test --test-pytest -i python{version} -p 3.10
> I: pybuild base:240: PYTHONPATH=/<> python3.10 -m pytest -k 'not
> test_create_db_and_table'
> = test session starts
> ==
> platform linux -- Python 3.10.7, pytest-7.1.2, pluggy-1.0.0+repack
> rootdir: /<>
> plugins: anyio-3.6.1
> collected 114 items / 3 deselected / 111 selected
>
> docs_src/tutorial/fastapi/app_testing/tutorial001/test_main.py ... [
> 6%]
> docs_src/tutorial/fastapi/app_testing/tutorial001/test_main_001.py . [
> 7%]
> docs_src/tutorial/fastapi/app_testing/tutorial001/test_main_002.py . [
> 8%]
> docs_src/tutorial/fastapi/app_testing/tutorial001/test_main_003.py . [
> 9%]
> docs_src/tutorial/fastapi/app_testing/tutorial001/test_main_004.py . [
> 9%]
> docs_src/tutorial/fastapi/app_testing/tutorial001/test_main_005.py . [
> 10%]
> docs_src/tutorial/fastapi/app_testing/tutorial001/test_main_006.py . [
> 11%]
> tests/test_default.py [
> 15%]
> tests/test_instance_no_args.py . [
> 16%]
> tests/test_query.py .[
> 17%]
> tests/test_advanced/test_decimal/test_tutorial001.py . [
> 18%]
> tests/test_tutorial/test_automatic_id_none_refresh/test_tutorial001_tutorial002.py
> . [ 18%]
> .[
> 19%]
> tests/test_tutorial/test_code_structure/test_tutorial001.py .[
> 20%]
> tests/test_tutorial/test_code_structure/test_tutorial002.py .[
> 21%]
> tests/test_tutorial/test_connect/test_create_connected_tables/test_tutorial001.py
> . [ 22%]
> [
> 22%]
> tests/test_tutorial/test_connect/test_delete/test_tutorial001.py . [
> 23%]
> tests/test_tutorial/test_connect/test_insert/test_tutorial001.py . [
> 24%]
> tests/test_tutorial/test_connect/test_select/test_tutorial001_tutorial002.py
> . [ 25%]
> .[
> 26%]
> tests/test_tutorial/test_connect/test_select/test_tutorial003.py . [
> 27%]
> tests/test_tutorial/test_connect/test_select/test_tutorial004.py . [
> 27%]
> tests/test_tutorial/test_connect/test_select/test_tutorial005.py . [
> 28%]
> tests/test_tutorial/test_connect/test_update/test_tutorial001.py . [
> 29%]
> tests/test_tutorial/test_delete/test_tutorial001_tutorial002.py .. [
> 31%]
> tests/test_tutorial/test_fastapi/test_app_testing/test_tutorial001_tests001.py
> . [ 32%]
> [
> 32%]
> tests/test_tutorial/test_fastapi/test_app_testing/test_tutorial001_tests002.py
> . [ 33%]
> [
> 33%]
> tests/test_tutorial/test_fastapi/test_app_testing/test_tutorial001_tests003.py
> . [ 34%]
> [
> 34%]
> tests/test_tutorial/test_fastapi/test_app_testing/test_tutorial001_tests004.py
> . [ 35%]
> [
> 35%]
> tests/test_tutorial/test_fastapi/test_app_testing/test_tutorial001_tests005.py
> . [ 36%]
> [
> 36%]
>
Processed: retitle 1024674 to libebook-contacts-1.2-4 needs rebuild after protobuf transition, affects 1024674 ...
Processing commands for cont...@bugs.debian.org: > retitle 1024674 libebook-contacts-1.2-4 needs rebuild after protobuf > transition Bug #1024674 [libphonenumber8] libphonenumber8: breaks Evolution Changed Bug title to 'libebook-contacts-1.2-4 needs rebuild after protobuf transition' from 'libphonenumber8: breaks Evolution'. > affects 1024674 evolution Bug #1024674 [libphonenumber8] libebook-contacts-1.2-4 needs rebuild after protobuf transition Added indication that 1024674 affects evolution > reassign 1024674 evolution-data-server Bug #1024674 [libphonenumber8] libebook-contacts-1.2-4 needs rebuild after protobuf transition Bug reassigned from package 'libphonenumber8' to 'evolution-data-server'. No longer marked as found in versions libphonenumber/8.12.57+ds-1. Ignoring request to alter fixed versions of bug #1024674 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1024674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024674: libphonenumber8: breaks Evolution
On Wed, Nov 23, 2022 at 05:02:16AM +0100, Christoph Anton Mitterer wrote: > Package: libphonenumber8 > Version: 8.12.57+ds-1+b2 > Severity: serious > > After the upgrade, evolution crashes when started: > $ evolution > evolution: symbol lookup error: > /usr/lib/x86_64-linux-gnu/libebook-contacts-1.2.so.4: undefined symbol: > _ZN4i18n12phonenumbers11PhoneNumberC1EPN6google8protobuf5ArenaE This issue goes away for me after a rebuild of src:evolution-data-server and installing the freshly rebuilt libebook-contacts-1.2-4. Maybe we can kick off a rebuild via the transition. If not that, would you be willing to do a sourceful upload Jeremy? signature.asc Description: PGP signature
Processed: Bug#1022413 marked as pending in sqlmodel
Processing control commands:
> tag -1 pending
Bug #1022413 [src:sqlmodel] sqlmodel: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p 3.10 returned exit code 13
Added tag(s) pending.
--
1022413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1022413: marked as pending in sqlmodel
Control: tag -1 pending Hello, Bug #1022413 in sqlmodel 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/python-team/packages/sqlmodel/-/commit/4894b2042085d38209013f4002171b0d0fac372f update tests expected data due to recent pydantic/fastapi; Closes: #1022413 (this message was generated automatically) -- Greetings https://bugs.debian.org/1022413
Bug#1024674: libphonenumber8: breaks Evolution
On Tue, 2022-11-22 at 21:11 -0800, tony mancill wrote: > Yes, totally. I didn't mean to imply that the bug shouldn't be here. Sure... just wanted to point out, that I don't consider it your fault or so :-) > > I had evolution running, while I've upgraded. And didn't restart it > > afterwards (at least not immediately). > > > > I then noticed some weird things... when replying to a mail, there > > was > > no quoting of the mail I replied to (i.e. I got a new compose > > window, > > but no text in it). > > Also I couldn't save my composed mail as draft (some strange error > > popup within evolution itself). > > Interesting... Interesting word for weird ;-) I guess it must be doing some kind of dynamic loading stuff? OTOH, it seems to be just linked as a plain shared lib: $ libtree /usr/lib/x86_64-linux-gnu/libebook-contacts-1.2.so.4.0.0 libebook-contacts-1.2.so.4 ├── libedataserver-1.2.so.27 [ld.so.conf] ... ├── libphonenumber.so.8 [ld.so.conf] │ ├── libprotobuf.so.23 [ld.so.conf] │ │ └── libz.so.1 [ld.so.conf] │ ├── libabsl_throw_delegate.so.20220623 [ld.so.conf] │ ├── libabsl_strings.so.20220623 [ld.so.conf] │ │ ├── libabsl_strings_internal.so.20220623 [ld.so.conf] │ │ │ └── libabsl_raw_logging_internal.so.20220623 [ld.so.conf] │ │ ├── libabsl_raw_logging_internal.so.20220623 [ld.so.conf] │ │ └── libabsl_throw_delegate.so.20220623 [ld.so.conf] │ ├── libabsl_raw_hash_set.so.20220623 [ld.so.conf] │ ├── libabsl_hash.so.20220623 [ld.so.conf] │ │ ├── libabsl_city.so.20220623 [ld.so.conf] │ │ └── libabsl_low_level_hash.so.20220623 [ld.so.conf] │ ├── libicui18n.so.72 [ld.so.conf] │ └── libicuuc.so.72 [ld.so.conf] ... > > Since I suspected some issues, I restarted evolution, and only then > > I've noticed the libphonenumber related error I've mentioned in the > > initial mail. > > Ugh, so it's completely broken for you now. Yes... at least evolution, but that's the only thing I have, which depends on it. Maybe we should increase the severity, so that people will see it at least via apt-listbugs? Thanks :-) Chris. >
Bug#1024674: libphonenumber8: breaks Evolution
On Wed, Nov 23, 2022 at 05:02:16AM +0100, Christoph Anton Mitterer wrote: > After the upgrade, evolution crashes when started: > $ evolution > evolution: symbol lookup error: > /usr/lib/x86_64-linux-gnu/libebook-contacts-1.2.so.4: undefined symbol: > _ZN4i18n12phonenumbers11PhoneNumberC1EPN6google8protobuf5ArenaE Weird that it didn't fail the first time, but I'm seeing the same failure now, both with the auto-transition build and with a rebuild on my local system.
Bug#1024674: libphonenumber8: breaks Evolution
On Wed, Nov 23, 2022 at 05:51:50AM +0100, Christoph Anton Mitterer wrote: > Hey Tony. > > On Tue, 2022-11-22 at 20:40 -0800, tony mancill wrote: > > Thank you for the bug report. libphonenumber 8.12.57+ds-1 has been > > in > > testing for longer than a month at this point [1]. Has it been > > broken > > all of this time? If not, I suspect this is related the protobuf > > transition [2]. > > No, it was fine all the time with 8.12.57+ds-1+b1 (and backporting to > it fixes the issue, too). Only 8.12.57+ds-1+b2 introduced the problem. Good to know. I will start by picking through the build logs here: https://buildd.debian.org/status/fetch.php?pkg=libphonenumber=amd64=8.12.57%2Bds-1%2Bb2=1669158118=0 > But given that the dependency for evolution (or rather libebook- > contacts-1.2-4) I thought the starting point of "responsibility" (in > terms of package dependencies) should be there. Yes, totally. I didn't mean to imply that the bug shouldn't be here. > > I'm not seeing the crash here, but I'm running vanilla unstable and > > not > > unstable-debug > > I don't think this makes a difference... the unstable-debug is just > there because I have the debug repo enabled, but the packages are from > unstable: > > APT policy: (500, 'unstable-debug'), (500, 'unstable') (nodding) > I had evolution running, while I've upgraded. And didn't restart it > afterwards (at least not immediately). > > I then noticed some weird things... when replying to a mail, there was > no quoting of the mail I replied to (i.e. I got a new compose window, > but no text in it). > Also I couldn't save my composed mail as draft (some strange error > popup within evolution itself). Interesting... > Since I suspected some issues, I restarted evolution, and only then > I've noticed the libphonenumber related error I've mentioned in the > initial mail. Ugh, so it's completely broken for you now. > Perhaps we should get the protobuf people on board in this issue? I have added Laszlo to the cc: I'm rebuilding locally against the 3.21.9-4 protobuf sources to attempt to reproduce the bug. Thank you, tony signature.asc Description: PGP signature
Processed: tagging 1022308
Processing commands for cont...@bugs.debian.org: > tags 1022308 + patch Bug #1022308 [src:crawl] crawl: FTBFS: glwrapper-ogl.cc:29:14: fatal error: GL/glu.h: No such file or directory Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1022308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024674: libphonenumber8: breaks Evolution
Hey Tony. On Tue, 2022-11-22 at 20:40 -0800, tony mancill wrote: > Thank you for the bug report. libphonenumber 8.12.57+ds-1 has been > in > testing for longer than a month at this point [1]. Has it been > broken > all of this time? If not, I suspect this is related the protobuf > transition [2]. No, it was fine all the time with 8.12.57+ds-1+b1 (and backporting to it fixes the issue, too). Only 8.12.57+ds-1+b2 introduced the problem. So yes, it may be related to the transition. But given that the dependency for evolution (or rather libebook- contacts-1.2-4) I thought the starting point of "responsibility" (in terms of package dependencies) should be there. > I'm not seeing the crash here, but I'm running vanilla unstable and > not > unstable-debug I don't think this makes a difference... the unstable-debug is just there because I have the debug repo enabled, but the packages are from unstable: > APT policy: (500, 'unstable-debug'), (500, 'unstable') ^ | > You mention that it crashes > and that it ends up in a weird state while it's running. Does that > mean > it crashes and exits sometimes? Or that logs an error and continues > running? No,... sorry for not describing it clearly. I had evolution running, while I've upgraded. And didn't restart it afterwards (at least not immediately). I then noticed some weird things... when replying to a mail, there was no quoting of the mail I replied to (i.e. I got a new compose window, but no text in it). Also I couldn't save my composed mail as draft (some strange error popup within evolution itself). Since I suspected some issues, I restarted evolution, and only then I've noticed the libphonenumber related error I've mentioned in the initial mail. Perhaps we should get the protobuf people on board in this issue? Thanks, Chris.
Bug#1024674: libphonenumber8: breaks Evolution
On Wed, Nov 23, 2022 at 05:02:16AM +0100, Christoph Anton Mitterer wrote: > Package: libphonenumber8 > Version: 8.12.57+ds-1+b2 > Severity: serious > > > Hey. > > After the upgrade, evolution crashes when started: > $ evolution > evolution: symbol lookup error: > /usr/lib/x86_64-linux-gnu/libebook-contacts-1.2.so.4: undefined symbol: > _ZN4i18n12phonenumbers11PhoneNumberC1EPN6google8protobuf5ArenaE > > and it even ended up in a weird state while it was still running. Hi Chris, Thank you for the bug report. libphonenumber 8.12.57+ds-1 has been in testing for longer than a month at this point [1]. Has it been broken all of this time? If not, I suspect this is related the protobuf transition [2]. I'm not seeing the crash here, but I'm running vanilla unstable and not unstable-debug, so perhaps that's a clue. You mention that it crashes and that it ends up in a weird state while it's running. Does that mean it crashes and exits sometimes? Or that logs an error and continues running? Thank you, tony P.S. Not directly related, but I have a package for 8.13.0 ready to upload, but have been waiting for the transition to complete. [1] https://tracker.debian.org/pkg/libphonenumber [2] https://release.debian.org/transitions/html/auto-protobuf.html signature.asc Description: PGP signature
Bug#1024674: libphonenumber8: breaks Evolution
Package: libphonenumber8 Version: 8.12.57+ds-1+b2 Severity: serious Hey. After the upgrade, evolution crashes when started: $ evolution evolution: symbol lookup error: /usr/lib/x86_64-linux-gnu/libebook-contacts-1.2.so.4: undefined symbol: _ZN4i18n12phonenumbers11PhoneNumberC1EPN6google8protobuf5ArenaE and it even ended up in a weird state while it was still running. Cheers, Chris. -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-4-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libphonenumber8 depends on: ii libabsl20220623 20220623.1-1 ii libc62.36-5 ii libgcc-s112.2.0-9 ii libicu72 72.1-2 ii libprotobuf323.21.9-4 ii libstdc++6 12.2.0-9 libphonenumber8 recommends no packages. libphonenumber8 suggests no packages. -- no debconf information
Bug#1022307: [Debian-med-packaging] Bug#1022307: status on t_coffee causing biopython ftbfs
Le Tue, Nov 22, 2022 at 11:54:48PM +0100, Étienne Mollier a écrit : > > Hi, mostly retitling the open entry against biopython for the > sake of clarity, and also pinging both bugs to reset auto- > removal counters. We don't have much news from t_coffee > upstream to day unfortunately. Maybe it will be necessary to > revert the t-coffee version bump for the upcoming Debian release > or do people see other options? Hi Étienne, I think that we do not have enough evidence that t_coffee was properly tested on other architectures than amd64. Even though a particular version may build fine, and let biophython pass its tests, we do not know if t_coffee produces sound results on these architectures. Unless we know or hear from an ARM user, I would recommend to play safe and only distribute it on amd64 for this release. Have a nice day, -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from work, https://mastodon.technology/@charles_plessy Tooting from home, https://framapiaf.org/@charles_plessy
Bug#1020851: elpa-ement: fails to install along emacs
Hello, On Tue 22 Nov 2022 at 05:39PM +01, Andreas Beckmann wrote: > On 28/09/2022 16.55, Sean Whitton wrote: >> transient is included in Emacs 28 so I'm inclined to leave this to fix >> itself when Emacs 28 migrates. > > Can't this be expressed as a package relationship? > e.g. Depends: emacs-el (>= 1:28) It's against the Emacsen Team policy to have a hard dependency on Emacs -- instead, it's in Recommends. So I'd prefer not to add a dependency that I'm only going to have to remove in a few weeks when Emacs migrates. But if you think this bug is getting in the way then I can add it. -- Sean Whitton
Bug#1012950: itk-4.y buildability status
Hi, I've been reviewing whether it would be feasible at t time to fallback to gcc-11 for insighttoolkit4, but I hit another build problem. I ended up disabling python3 bindings, at last. The itk-4.y branch on salsa currently builds properly on Debian sid amd64, but I stopped producing the insighttoolkit4-python3 package, as it is now empty; I left a note in d/NEWS about that. Unless there are objections, I consider uploading ITK4 in unstable; we'll see whether it manages to make it to testing actually. insighttoolkit4-python3 does not seem to have much reverse dependencies, so I guess this binary package can be safely removed, if the rest were to stay around. In hope this helps, -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/6, please excuse my verbosity. On air: Stratovarius - A Million Light Years Away signature.asc Description: PGP signature
Processed: severity of 1012572 is serious
Processing commands for cont...@bugs.debian.org:
> severity 1012572 serious
Bug #1012572 {Done: Roger Shimizu }
[src:android-platform-frameworks-base] android-platform-frameworks-base: FTBFS
with protobuf 3.20.1+
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1012572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: status on t_coffee causing biopython ftbfs
Processing control commands: > retitle 1022307 python-biopython: FTBFS: tests choke on t_coffee Bug #1022307 [src:python-biopython] python-biopython: FTBFS: mv: cannot stat 'Tests/test_NACCESS_tool.py': No such file or directory Changed Bug title to 'python-biopython: FTBFS: tests choke on t_coffee' from 'python-biopython: FTBFS: mv: cannot stat 'Tests/test_NACCESS_tool.py': No such file or directory'. -- 1022307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: status on t_coffee causing biopython ftbfs
Processing control commands: > retitle 1022307 python-biopython: FTBFS: tests choke on t_coffee Bug #1022307 [src:python-biopython] python-biopython: FTBFS: tests choke on t_coffee Ignoring request to change the title of bug#1022307 to the same title -- 1022307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022307 1022570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022307: status on t_coffee causing biopython ftbfs
Control: retitle 1022307 python-biopython: FTBFS: tests choke on t_coffee Hi, mostly retitling the open entry against biopython for the sake of clarity, and also pinging both bugs to reset auto- removal counters. We don't have much news from t_coffee upstream to day unfortunately. Maybe it will be necessary to revert the t-coffee version bump for the upcoming Debian release or do people see other options? Have a nice day, :) -- .''`. Étienne Mollier : :' : gpg: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/3, please excuse my verbosity `-on air: Frost* - Hyperventilate signature.asc Description: PGP signature
Bug#1011084: marked as done (cargo: FTBFS on mips64el)
Your message dated Tue, 22 Nov 2022 23:44:54 +0100 with message-id and subject line Re: Bug#1011084: cargo: FTBFS on mips64el has caused the Debian Bug report #1011084, regarding cargo: FTBFS on mips64el 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.) -- 1011084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cargo Version: 0.57.0-7 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=cargo=mips64el=0.57.0-7%2Bb1=1652695874=0 [cargo 0.57.0] cargo:rerun-if-changed=src/doc/man/generated_txt/cargo.txt Compiling cargo-util v0.1.1 (/<>/crates/cargo-util) Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=cargo_util CARGO_MANIFEST_DIR=/<>/crates/cargo-util CARGO_PKG_AUTHORS='The Cargo Project Developers' CARGO_PKG_DESCRIPTION='Miscellaneous support code used by Cargo.' CARGO_PKG_HOMEPAGE='https://github.com/rust-lang/cargo' CARGO_PKG_LICENSE='MIT OR Apache-2.0' CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=cargo-util CARGO_PKG_REPOSITORY='https://github.com/rust-lang/cargo' CARGO_PKG_VERSION=0.1.1 CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=1 CARGO_PKG_VERSION_PATCH=1 CARGO_PKG_VERSION_PRE='' LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc --crate-name cargo_util --edition=2018 crates/cargo-util/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 -C metadata=a1f45a08c06173c5 -C extra-filename=-a1f45a08c06173c5 --out-dir /<>/target/mips64el-unknown-linux-gnuabi64/debug/deps --target mips64el-unknown-linux-gnuabi64 -C incremental=/<>/target/mips64el-unknown-linux-gnuabi64/debug/incremental -L dependency=/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps -L dependency=/<>/target/debug/deps --extern anyhow=/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps/libanyhow-f62a89bd0bca2533.rmeta --extern crypto_hash=/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps/libcrypto_hash-4c75664c76440375.rmeta --extern filetime=/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps/libfiletime-c83d85b5f72140af.rmeta --extern hex=/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps/libhex-1937fd047486a4d1.rmeta --extern jobserver=/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps/libjobserver-30001c053f9637c1.rmeta --extern libc=/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps/liblibc-0699ea83a53d7b65.rmeta --extern log=/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps/liblog-7715d9897b857cdb.rmeta --extern same_file=/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps/libsame_file-7b878211e7c010a7.rmeta --extern shell_escape=/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps/libshell_escape-979beb74eedcf680.rmeta --extern tempfile=/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps/libtempfile-0b90b0667fec2dfb.rmeta --extern walkdir=/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps/libwalkdir-b19ffb487036f7ce.rmeta -C debuginfo=2 --cap-lints warn -C linker=mips64el-linux-gnuabi64-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix=/<>=/usr/src/cargo-0.57.0 -Ctarget-feature=+xgot` warning: `openssl` (lib) generated 1 warning Compiling git2-curl v0.14.1 Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=git2_curl CARGO_MANIFEST_DIR=/<>/vendor/git2-curl CARGO_PKG_AUTHORS='Josh Triplett :Alex Crichton ' CARGO_PKG_DESCRIPTION='Backend for an HTTP transport in libgit2 powered by libcurl. Intended to be used with the git2 crate. ' CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE=MIT/Apache-2.0 CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=git2-curl CARGO_PKG_REPOSITORY='https://github.com/rust-lang/git2-rs' CARGO_PKG_VERSION=0.14.1 CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=14 CARGO_PKG_VERSION_PATCH=1 CARGO_PKG_VERSION_PRE='' LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc --crate-name git2_curl --edition=2018 /<>/vendor/git2-curl/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 -C metadata=ab014bf378acbe6f -C extra-filename=-ab014bf378acbe6f --out-dir /<>/target/mips64el-unknown-linux-gnuabi64/debug/deps --target mips64el-unknown-linux-gnuabi64 -L dependency=/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps -L dependency=/<>/target/debug/deps --extern
Bug#1024648: elpa-snakemake: fails to install with emacs 27: misses 'transient'
On 22/11/2022 18.40, Diane Trout wrote: On Tue, 2022-11-22 at 18:24 +0100, Andreas Beckmann wrote: There needs to be either a Depends: emacs-el (>= 1:28) or an equivaent Breaks: (emacs-el (<< 1:28) or the installation must be skipped if emacs is too old. So it looks like elpa-snakemake depends on the transient package which is currently elpa-transient and in included in emacs 28. So what do you think of this instead? Depends: emacs-el (>= 1:28) | elpa-transient, Good question. Hmm, well, I know nothing about emacs or its packaging. ;-) But if emacs-el (or -common?) bundles extensions (or however you call them), especially ones that were previously packaged separately, it should probably have versioned Provides (and maybe versioned Breaks, too) for them. (Cf. perl, perl-base which does the same.) Not sure whether these should be in -el or -common ... If these Provides were available, elpa-snakemake wouldn't need to know about the packaging details of other packages and could just use Depends: elpa-transient Andreas
Bug#1019675: marked as done (ruby-versionomy: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.)
Your message dated Tue, 22 Nov 2022 22:20:34 +
with message-id
and subject line Bug#1019675: fixed in ruby-versionomy 0.5.0-3
has caused the Debian Bug report #1019675,
regarding ruby-versionomy: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
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.)
--
1019675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-versionomy
Version: 0.5.0-2.1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-versionomy with ruby3.1 enabled, the build failed.
Relevant part of the build log (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
>
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.1
> │
> └──┘
>
> GEM_PATH=/<>/debian/ruby-versionomy/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
> ruby3.1 -e gem\ \"versionomy\"
>
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-test-files.yaml
> │
> └──┘
>
> RUBYLIB=/<>/debian/ruby-versionomy/usr/lib/ruby/vendor_ruby:.
> GEM_PATH=/<>/debian/ruby-versionomy/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
> ruby3.1 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\
> \{\ \|f\|\ require\ f\ \}
> Run options: --seed 50525
>
> # Running:
>
> .EE.
>
> Finished in 0.023531s, 3909.7426 runs/s, 18358.7912 assertions/s.
>
> 1) Error:
> Versionomy::Tests::TestStandardMisc#test_yaml:
> Psych::DisallowedClass: Tried to load unspecified class: Versionomy::Value
> /usr/lib/ruby/3.1.0/psych/class_loader.rb:99:in `find'
> /usr/lib/ruby/3.1.0/psych/class_loader.rb:28:in `load'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:424:in `resolve_class'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:165:in
> `visit_Psych_Nodes_Mapping'
> /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:30:in `visit'
> /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:6:in `accept'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:35:in `accept'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:318:in
> `visit_Psych_Nodes_Document'
> /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:30:in `visit'
> /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:6:in `accept'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:35:in `accept'
> /usr/lib/ruby/3.1.0/psych.rb:335:in `safe_load'
> /usr/lib/ruby/3.1.0/psych.rb:370:in `load'
> /<>/test/tc_standard_misc.rb:87:in `test_yaml'
>
> 2) Error:
> Versionomy::Tests::TestSemverBasic#test_yaml:
> Psych::DisallowedClass: Tried to load unspecified class: Versionomy::Value
> /usr/lib/ruby/3.1.0/psych/class_loader.rb:99:in `find'
> /usr/lib/ruby/3.1.0/psych/class_loader.rb:28:in `load'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:424:in `resolve_class'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:165:in
> `visit_Psych_Nodes_Mapping'
> /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:30:in `visit'
> /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:6:in `accept'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:35:in `accept'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:318:in
> `visit_Psych_Nodes_Document'
> /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:30:in `visit'
> /usr/lib/ruby/3.1.0/psych/visitors/visitor.rb:6:in `accept'
> /usr/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:35:in `accept'
> /usr/lib/ruby/3.1.0/psych.rb:335:in `safe_load'
> /usr/lib/ruby/3.1.0/psych.rb:370:in `load'
> /<>/test/tc_semver_basic.rb:205:in `test_yaml'
>
> 92 runs, 432 assertions, 0
Bug#1019675: marked as pending in ruby-versionomy
Control: tag -1 pending Hello, Bug #1019675 in ruby-versionomy 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/ruby-team/ruby-versionomy/-/commit/cd97ab1a7b87fcc7f7a2f4542796cf41f8df Use unsafe_load to load YAML in tests (Closes: #1019675) (this message was generated automatically) -- Greetings https://bugs.debian.org/1019675
Processed: Bug#1019675 marked as pending in ruby-versionomy
Processing control commands: > tag -1 pending Bug #1019675 [src:ruby-versionomy] ruby-versionomy: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed. Added tag(s) pending. -- 1019675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:filezilla: fails to migrate to testing for too long: FTBFS on i386
Processing control commands:
> close -1 3.61.0-1
Bug #1024664 [src:filezilla] src:filezilla: fails to migrate to testing for too
long: FTBFS on i386
Marked as fixed in versions filezilla/3.61.0-1.
Bug #1024664 [src:filezilla] src:filezilla: fails to migrate to testing for too
long: FTBFS on i386
Marked Bug as done
> block -1 by 1020327
Bug #1024664 {Done: Paul Gevers } [src:filezilla]
src:filezilla: fails to migrate to testing for too long: FTBFS on i386
1024664 was not blocked by any bugs.
1024664 was not blocking any bugs.
Added blocking bug(s) of 1024664: 1020327
--
1024664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1024664: src:filezilla: fails to migrate to testing for too long: FTBFS on i386
Source: filezilla Version: 3.60.2-1 Severity: serious Control: close -1 3.61.0-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1020327 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:filezilla has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package failed to build from source on i386, which was reported in bug #1020327. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=filezilla OpenPGP_signature Description: OpenPGP digital signature
Bug#953630: [Debichem-devel] Bug#953630: openbabel autopkg tests fail on non-amd64 architectures
Hi all, On 21-11-2022 21:36, Paul Gevers wrote: On 21-11-2022 16:01, Andrius Merkys wrote: On 2022-11-20 18:18, Paul Gevers wrote: From the BSP in Tilburg, I uploaded the attached NMU to DELAYED/5. Please let me know if I should delay more or cancel. Thanks, IMO this NMU is fine. Similar logic should be applied to the build time tests in future, since now their failures are plainly ignored. It seems this needs another round and I'll take care of it. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1024661: r-bioc-bitseq: orphaned upstream and blocking BioC 3.16 transition
Source: r-bioc-bitseq Version: 1.40.0+dfsg-1 Severity: critical Tags: ftbfs Justification: breaks unrelated software X-Debbugs-Cc: 1023...@bugs.debian.org, debia...@lists.debian.org As per upstream https://lists.debian.org/debian-r/2022/11/msg00058.html r-bioc-bitseq is not supported any more. It does not build against the packages that are part of the BioC 3.16 release (namely r-bioc-rhtslib which does not contain the header file bam.h any more) Before we might remove r-bioc-bitseq finally from Debian we want to give interested people a chance to fix the code but this bug should remove the package from testing to not block the BioC 3.16 transition. Kind regards Andreas. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (50, 'buildd-unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-4-amd64 (SMP w/8 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: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1024651: ruby-gpgme: FTBFS against libgpgme-dev >= 1.18.0-2
Source: ruby-gpgme Version: 2.0.20-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) User: pkg-gnupg-ma...@lists.alioth.debian.org Usertags: gpgme-config-transition^ The package relies on gpgme-config to detect gpgme. gpgme-config has been dropped and replaced by pkg-config pc files. cu Andreas -- checking for gpgme-config... no gpgme-config not found *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options.
Processed: Re: [Pkg-utopia-maintainers] Bug#1024275: network-manager-openvpn: can't connect to vpn after last update: can't set proper cipher.
Processing control commands: > severity -1 normal Bug #1024275 [network-manager-openvpn] network-manager-openvpn: can't connect to vpn after last update: can't set proper cipher. Severity set to 'normal' from 'serious' > notforwarded -1 Bug #1024275 [network-manager-openvpn] network-manager-openvpn: can't connect to vpn after last update: can't set proper cipher. Unset Bug forwarded-to-address -- 1024275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024275: [Pkg-utopia-maintainers] Bug#1024275: network-manager-openvpn: can't connect to vpn after last update: can't set proper cipher.
Control: severity -1 normal
Control: notforwarded -1
Am 16.11.22 um 22:54 schrieb Daniel Serpell:
Package: network-manager-openvpn
Version: 1.10.2-1
Severity: normal
Dear maintainer,
After upgrading to 1.10.2-1, I can't connect to the VPN anymore.
This is the logs from NetworkManager:
nm-openvpn[]: [] Peer Connection Initiated with
[AF_INET]:
nm-openvpn[]: OPTIONS ERROR: failed to negotiate cipher with server. Add
the server's cipher ('AES-256-CBC') to --data-ciphers (currently 'AES-256-GCM')
if you want to connect to this server.
nm-openvpn[]: ERROR: Failed to apply push options
nm-openvpn[]: Failed to open tun/tap interface
nm-openvpn[]: SIGUSR1[soft,process-push-msg-failed] received, process
restarting
Trying to change the cipher to AES-256-CBC in network properties does not work,
it reverts back to AES-256-GCM.
I recreated the failing OpenVPN connection and I can't reproduce the
problem anymore.
I thus closed the upstream issue and dropped the forwarded meta data.
My recommendation, if you can still reproduce the issue, is to file the
issue upstream [1] yourself. It's likely that upstream has further question.
Regards,
Michael
[1] https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1024648: elpa-snakemake: fails to install with emacs 27: misses 'transient'
On Tue, 2022-11-22 at 18:24 +0100, Andreas Beckmann wrote: > > There needs to be either a > Depends: emacs-el (>= 1:28) > or an equivaent > Breaks: (emacs-el (<< 1:28) > or the installation must be skipped if emacs is too old. So it looks like elpa-snakemake depends on the transient package which is currently elpa-transient and in included in emacs 28. So what do you think of this instead? Depends: emacs-el (>= 1:28) | elpa-transient, Diane
Bug#1024648: elpa-snakemake: fails to install with emacs 27: misses 'transient'
Package: elpa-snakemake Version: 2.0.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install if emacs 27 (currently still in bookworm) is already installed. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up elpa-snakemake (2.0.0-2) ... Install emacsen-common for emacs emacsen-common: Handling install of emacsen flavor emacs Install elpa-snakemake for emacs install/snakemake-2.0.0: Handling install of emacsen flavor emacs install/snakemake-2.0.0: byte-compiling for emacs In toplevel form: snakemake.el:94:1:Error: Cannot open load file: No such file or directory, transient ERROR: install script from elpa-snakemake package failed dpkg: error processing package elpa-snakemake (--configure): installed elpa-snakemake package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: elpa-snakemake There needs to be either a Depends: emacs-el (>= 1:28) or an equivaent Breaks: (emacs-el (<< 1:28) or the installation must be skipped if emacs is too old. cheers, Andreas elpa-snakemake=2.0.0-2_emacs.log.gz Description: application/gzip
Bug#1024627: gitlab: Fails to install
I've encountered this problem, here is a workaround: apt install omniauth-oauth2=1.7.1
Bug#1022326: marked as done (ruby-combustion: FTBFS: ERROR: Test "ruby3.1" failed. Bundler::GemNotFound: Could not find gem 'mysql2' in locally installed gems.)
Your message dated Tue, 22 Nov 2022 17:04:59 + with message-id and subject line Bug#1022326: fixed in ruby-combustion 1.3.7-1 has caused the Debian Bug report #1022326, regarding ruby-combustion: FTBFS: ERROR: Test "ruby3.1" failed. Bundler::GemNotFound: Could not find gem 'mysql2' in locally installed gems. 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.) -- 1022326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-combustion Version: 1.3.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.1 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-combustion/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0 > ruby3.1 -e gem\ \"combustion\" > > ┌──┐ > │ Run tests for ruby3.1 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-combustion/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0 > ruby3.1 -S rake -f debian/ruby-tests.rake > mv Gemfile.lock ./.gem2deb.Gemfile.lock > rake aborted! > Bundler::GemNotFound: Could not find gem 'mysql2' in locally installed gems. > /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/resolver.rb:271:in > `block in verify_gemfile_dependencies_are_found!' > /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/resolver.rb:254:in > `map!' > /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/resolver.rb:254:in > `verify_gemfile_dependencies_are_found!' > /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/resolver.rb:50:in > `start' > /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/resolver.rb:24:in > `resolve' > /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/definition.rb:270:in > `resolve' > /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/definition.rb:473:in > `materialize' > /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/definition.rb:191:in > `specs' > /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/definition.rb:239:in > `specs_for' > /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/runtime.rb:18:in > `setup' > /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler.rb:162:in > `setup' > /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/setup.rb:20:in > `block in ' > /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/ui/shell.rb:136:in > `with_level' > /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/ui/shell.rb:88:in > `silence' > /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/setup.rb:20:in > `' > :85:in > `require' > :85:in > `require' > /<>/debian/ruby-tests.rake:2:in `' > (See full trace by running task with --trace) > mv ./.gem2deb.Gemfile.lock Gemfile.lock > ERROR: Test "ruby3.1" failed. The full build log is available from: http://qa-logs.debian.net/2022/10/23/ruby-combustion_1.3.3-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at
Processed: tagging 1024632, found 1024632 in 1:24.3.4.1+dfsg-1
Processing commands for cont...@bugs.debian.org: > tags 1024632 + upstream fixed-upstream Bug #1024632 [erlang] erlang: CVE-2022-37026 Client Authentication Bypass Added tag(s) upstream and fixed-upstream. > found 1024632 1:24.3.4.1+dfsg-1 Bug #1024632 [erlang] erlang: CVE-2022-37026 Client Authentication Bypass Marked as found in versions erlang/1:24.3.4.1+dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1024632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024647: trac: The versiuon packaged by debian contain a bug fixed upstream that prevent it to work with python3
Package: trac Version: 1.5.3+dfsg-1 Severity: grave Tags: upstream Justification: renders package unusable Afterupgrading and oldoldstable distrib to stable 11.5, becaue of the move to python3 I had to update trac to the sid version as there is not stable version yet. It did not work at all inside apache2/cgi (old install)because of a bug already fixed upstream (reload not defined) See : https://trac.edgewall.org/changeset/17571 for the fix. -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.10.155 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages trac depends on: pn libjs-excanvas ii libjs-jquery 3.6.1+dfsg+~3.5.14-1 pn libjs-jquery-timepicker ii libjs-jquery-ui 1.13.2+dfsg-1 ii python3 3.10.6-3 ii python3-jinja2 3.0.3-2 ii python3-pkg-resources65.5.0-1 ii python3-setuptools 65.5.0-1 Versions of packages trac recommends: pn apache2 | httpd ii python3-babel 2.10.3-1 ii python3-docutils0.19+dfsg-2 ii python3-pygments2.13.0+dfsg-1 pn python3-subversion ii python3-tz 2022.6-1 Versions of packages trac suggests: pn libapache2-mod-wsgi pn python3-psycopg2 pn python3-textile pn trac-accountmanager pn trac-authopenid pn trac-bitten pn trac-bzr pn trac-customfieldadmin pn trac-email2trac pn trac-graphviz pn trac-ja-resource pn trac-mastertickets pn trac-mercurial pn trac-spamfilter pn trac-wikiprint pn trac-wikirename pn trac-wysiwyg pn trac-xmlrpc
Bug#1024627: Acknowledgement (gitlab: Fails to install)
On Tue, Nov 22 2022 at 02:39:40 PM +01:00:00 +01:00:00, Kurt Roeckx wrote: fasttrack contains a 1.7.3 version that's new enough. The 1.8.0 version from backports is too new it seems, and it what gets installed when you just do: apt install gitlab Some of the version requirements for omniauth-oauth2 is too strict, which should be fixed. But as a workaround, you can install 1.7.3 version, till we fix this properly.
Bug#1020851: elpa-ement: fails to install along emacs
On 28/09/2022 16.55, Sean Whitton wrote: transient is included in Emacs 28 so I'm inclined to leave this to fix itself when Emacs 28 migrates. Can't this be expressed as a package relationship? e.g. Depends: emacs-el (>= 1:28) Andreas
Bug#1023874: marked as done (node-readable-stream: FTBFS: Cannot use import statement outside a module)
Your message dated Tue, 22 Nov 2022 16:35:01 + with message-id and subject line Bug#1023874: fixed in node-readable-stream 4.2.0+~cs9.0.2-1 has caused the Debian Bug report #1023874, regarding node-readable-stream: FTBFS: Cannot use import statement outside a module 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.) -- 1023874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023874 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-readable-stream Version: 4.1.0+~cs9.0.2-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, node-readable-stream/experimental recently started to FTBFS, probably because some build-dependency became more strict. The version in sid is not affected. ... dh_auto_build --buildsystem=nodejs Found debian/nodejs/abort-controller/build cd ./abort-controller && sh -ex ../debian/nodejs/abort-controller/build + rollup -c (node:4756) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension. (Use `node --trace-warnings ...` to show where the warning was created) ESC[1mESC[31m[!] ESC[1mRollupError: Node tried to load your configuration file as CommonJS even though it is likely an ES module. To resolve this, change the extension of your configuration to ".mjs", set "type": "module" in your package.json file or pass the "--bundleConfigAsCjs" flag. Original error: Cannot use import statement outside a moduleESC[22mESC[1mESC[39mESC[22m ESC[36mhttps://rollupjs.org/guide/en/#--bundleconfigascjsESC[39m ESC[2m/build/node-readable-stream-4.1.0+~cs9.0.2/abort-controller/rollup.config.js:1 import babel from "@rollup/plugin-babel" ^^ SyntaxError: Cannot use import statement outside a module at Object.compileFunction (node:vm:360:18) at wrapSafe (node:internal/modules/cjs/loader:1088:15) at Module._compile (node:internal/modules/cjs/loader:1123:27) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1213:10) at Module.load (node:internal/modules/cjs/loader:1037:32) at Function.Module._load (node:internal/modules/cjs/loader:878:12) at ModuleWrap. (node:internal/modules/esm/translators:169:29) at ModuleJob.run (node:internal/modules/esm/module_job:193:25) at async Promise.all (index 0) at ESMLoader.import (node:internal/modules/esm/loader:530:24)ESC[22m dh_auto_build: error: cd ./abort-controller && sh -ex ../debian/nodejs/abort-controller/build returned exit code 1 make: *** [debian/rules:11: binary] Error 25 ... Andreas node-readable-stream_4.1.0+~cs9.0.2-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: node-readable-stream Source-Version: 4.2.0+~cs9.0.2-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-readable-stream, 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 1023...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-readable-stream 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: Tue, 22 Nov 2022 17:13:15 +0100 Source: node-readable-stream Built-For-Profiles: nocheck Architecture: source Version: 4.2.0+~cs9.0.2-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1023874 Changes: node-readable-stream (4.2.0+~cs9.0.2-1) experimental; urgency=medium . * Team upload * New upstream version 4.2.0+~cs9.0.2 * Add fix for rollup 3 (Closes: #1023874) * Update test Checksums-Sha1: 81556f35c1cf650ed7ee06bd6253f17452465828 3094 node-readable-stream_4.2.0+~cs9.0.2-1.dsc 79de33e421cdeb775c6c7e362cbe098327f1edad 8649 node-readable-stream_4.2.0+~cs9.0.2.orig-abort-controller.tar.gz 06cbf28f787d14f6b39b962f785820fbc5d91d5b 78068 node-readable-stream_4.2.0+~cs9.0.2.orig-event-target-shim.tar.gz 933ac83a52d5f93c67dccd752f5a8ef82d825817 203599 node-readable-stream_4.2.0+~cs9.0.2.orig.tar.gz 6884fbdb619cdb19883573f3b7d14b6b0830a5b9 6124 node-readable-stream_4.2.0+~cs9.0.2-1.debian.tar.xz Checksums-Sha256:
Bug#1024642: pgcharts: FTBFS: Fatal NAME-CONFLICT: [...] PGCHARTS.SQL:READ-QUERIES, POSTMODERN:READ-QUERIES
Source: pgcharts
Version: 1.0+2017-09-16-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source
Hi,
pgcharts recently started to FTBFS in both testing (emacs 27)
and unstable (emacs 28):
debian/rules override_dh_auto_build
make[1]: Entering directory '/build/pgcharts-1.0+2017-09-16'
mkdir -p build/bin
mkdir -p /build/pgcharts-1.0+2017-09-16/debian/home
buildapp --logfile /tmp/pgcharts-build.log \
--require sb-posix \
--load /usr/share/common-lisp/source/cl-asdf/build/asdf.lisp \
--asdf-path . \
--asdf-tree /usr/share/common-lisp/systems \
--load-system pgcharts \
--load src/image.lisp \
--load debian/settings.lisp\
--entry pgcharts:main \
--dynamic-space-size 4096 \
--compress-core\
--output build/bin/pgcharts
; compiling file "/usr/share/common-lisp/source/cl-asdf/build/asdf.lisp"
(written 24 SEP 2022 09:05:35 AM):
; file: /usr/share/common-lisp/source/cl-asdf/build/asdf.lisp
; in: DEFUN CALL-WITH-OUTPUT
; (WITH-OUTPUT-TO-STRING (STREAM NIL :ELEMENT-TYPE
UIOP/STREAM::ELEMENT-TYPE)
; (FUNCALL FUNCTION STREAM))
; --> LET
; ==>
; (MAKE-STRING 31 :ELEMENT-TYPE UIOP/STREAM::ELEMENT-TYPE)
;
; note: could not stack allocate:
;(WITH-OUTPUT-TO-STRING (STREAM NIL :ELEMENT-TYPE ELEMENT-TYPE)
; (FUNCALL FUNCTION STREAM))
; in: DEFUN SLURP-STREAM-STRING
; (WITH-OUTPUT-TO-STRING
; (UIOP/STREAM::OUTPUT NIL :ELEMENT-TYPE UIOP/STREAM::ELEMENT-TYPE)
; (UIOP/STREAM:COPY-STREAM-TO-STREAM UIOP/STREAM::INPUT
UIOP/STREAM::OUTPUT
; :ELEMENT-TYPE
UIOP/STREAM::ELEMENT-TYPE))
; --> LET
; ==>
; (MAKE-STRING 31 :ELEMENT-TYPE UIOP/STREAM::ELEMENT-TYPE)
;
; note: could not stack allocate:
;(WITH-OUTPUT-TO-STRING (OUTPUT NIL :ELEMENT-TYPE ELEMENT-TYPE)
; (COPY-STREAM-TO-STREAM INPUT OUTPUT :ELEMENT-TYPE ELEMENT-TYPE))
; wrote
/build/pgcharts-1.0+2017-09-16/debian/home/.cache/common-lisp/sbcl-2.2.9.debian-linux-x64/usr/share/common-lisp/source/cl-asdf/build/asdf-tmpGHU3ALSV.fasl
; compilation finished in 0:00:13.588
;
; compilation unit finished
; printed 2 notes
;; loading file #P"/usr/share/common-lisp/source/cl-asdf/build/asdf.lisp"
;; loading system "pgcharts"
Fatal NAME-CONFLICT:
USE-PACKAGE # causes name-conflicts in
# between the following symbols:
PGCHARTS.SQL:READ-QUERIES, POSTMODERN:READ-QUERIES
See also:
The ANSI Standard, Section 11.1.1.2.5
make[1]: *** [debian/rules:32: override_dh_auto_build] Error 1
Andreas
Reading package lists...
NOTICE: 'pgcharts' packaging is maintained in the 'Git' version control system
at:
https://github.com/dimitri/pgcharts.git
Please use:
git clone https://github.com/dimitri/pgcharts.git
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 15.5 MB of source archives.
Get:1 http://ftp.de.debian.org/debian bookworm/non-free pgcharts
1.0+2017-09-16-1 (dsc) [2269 B]
Get:2 http://ftp.de.debian.org/debian bookworm/non-free pgcharts
1.0+2017-09-16-1 (tar) [15.5 MB]
Get:3 http://ftp.de.debian.org/debian bookworm/non-free pgcharts
1.0+2017-09-16-1 (diff) [10.3 kB]
Fetched 15.5 MB in 0s (38.7 MB/s)
Download complete and in download only mode
+ pbuilder-bookworm build --hookdir /etc/pbuilder/hooks/bookworm --logfile
../build.log --buildresult .. pgcharts_1.0+2017-09-16-1.dsc
W: /root/.pbuilderrc does not exist
I: Logging to ../build.log
W: cgroups are not available on the host, not using them.
I: pbuilder: network access will be disabled during build
I: Current time: Tue Nov 22 16:28:09 CET 2022
I: pbuilder-time-stamp: 1669130889
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/base-testing.tgz]
I: copying local configuration
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: Mounting /var/cache/apt/archives
I: policy-rc.d already exists
I: Copying source file
I: copying [pgcharts_1.0+2017-09-16-1.dsc]
I: copying [./pgcharts_1.0+2017-09-16.orig.tar.gz]
I: copying [./pgcharts_1.0+2017-09-16-1.debian.tar.xz]
I: Extracting source
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/tmp/dpkg-verify-sig.IrU8cdyQ/trustedkeys.kbx':
General error
gpgv: Signature made Sun Jan 13 12:53:06 2019 UTC
gpgv:using RSA key 5C48FE6157F49179597087C64C5A6BAB12D2A7AE
gpgv: Can't check signature: No public key
dpkg-source: warning: cannot verify signature ./pgcharts_1.0+2017-09-16-1.dsc
dpkg-source: info: extracting pgcharts in pgcharts-1.0+2017-09-16
dpkg-source: info: unpacking
Bug#1016633: marked as done (pyhst2: FTBFS: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value')
Your message dated Tue, 22 Nov 2022 15:39:20 + with message-id and subject line Bug#1016633: fixed in pyhst2 2020c-6 has caused the Debian Bug report #1016633, regarding pyhst2: FTBFS: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value' 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.) -- 1016633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyhst2 Version: 2020c-5 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, pyhst2 recently started to FTBFS in sid (but not yet in testing): /usr/include/c++/10/type_traits:71:52: error: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value' 71 | template |^ /usr/include/c++/10/type_traits:59:29: note: 'constexpr const _Tp value' previously declared here 59 | static constexpr _Tp value = __v; | ^ Andreas sid.build.gz Description: application/gzip testing.build.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: pyhst2 Source-Version: 2020c-6 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of pyhst2, 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 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated pyhst2 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: Tue, 22 Nov 2022 15:39:59 +0100 Source: pyhst2 Binary: python3-pyhst2-cuda python3-pyhst2-cuda-dbgsym Architecture: source amd64 Version: 2020c-6 Distribution: unstable Urgency: medium Maintainer: Debian PaN Maintainers Changed-By: Andreas Beckmann Description: python3-pyhst2-cuda - Python High Speed Tomographic reconstruction Closes: 1016633 Changes: pyhst2 (2020c-6) unstable; urgency=medium . * Team upload. . [ Neil Williams ] * Trim trailing whitespace. * Set upstream metadata fields: Repository. . [ Andreas Beckmann ] * Switch Build-Depends to nvidia-cuda-toolkit-gcc. (Closes: #1016633) * Fix typos found by Lintian. * Set Rules-Requires-Root: no. * Update Lintian overrides. Checksums-Sha1: cfc3d09c250a40f1b32027323ea52a6deec80fef 2329 pyhst2_2020c-6.dsc 20c1d346c7614009fc02cb19f6ae8c389b351782 6608 pyhst2_2020c-6.debian.tar.xz 1707ffa7a4fa0285e2058663b74d17b8fc3c8dbb 13177 pyhst2_2020c-6_amd64.buildinfo 6b468288df357e0d60a233c1937c5dd68a3bd1d9 800228 python3-pyhst2-cuda-dbgsym_2020c-6_amd64.deb 866d119bc44c50866b5630093b14309b14636681 570220 python3-pyhst2-cuda_2020c-6_amd64.deb Checksums-Sha256: 20b988e653f26ec1d5894d67df17b6d793b11445c6b0cb14035492cabba1a6e1 2329 pyhst2_2020c-6.dsc 27d5f0c182453122ef6d3ac73f5cd6023bd4cff6bf1bf7377a618047e1ad0aed 6608 pyhst2_2020c-6.debian.tar.xz 0e359ecb1778d247c2827d30d2e1c4a929b9271347e300a3ee25d0955896ea9b 13177 pyhst2_2020c-6_amd64.buildinfo df60edb0a19813775f5fd7ae0a9454a512018f32cc4fd4de1f3dac263561fd9a 800228 python3-pyhst2-cuda-dbgsym_2020c-6_amd64.deb baba922a3b0eaf6363fcb0e05ec133390471e0e5cc3f71b3963979b830b5335e 570220 python3-pyhst2-cuda_2020c-6_amd64.deb Files: 3f4f01cc4817b2bc99da8ac1ae4cae60 2329 contrib/python optional pyhst2_2020c-6.dsc 9f2f8eaa5dbdb3b7d454ea616d47d43e 6608 contrib/python optional pyhst2_2020c-6.debian.tar.xz e6ce5810eab88419499c7c1c3744f7bd 13177 contrib/python optional pyhst2_2020c-6_amd64.buildinfo afb30cbc7cf09db98f4ba72b21fed84c 800228 contrib/debug optional python3-pyhst2-cuda-dbgsym_2020c-6_amd64.deb 78311c3ed78e59b00c826a0db39de0db 570220 contrib/python optional python3-pyhst2-cuda_2020c-6_amd64.deb -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmN85U4QHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCMDkD/4+hoJg2ZLk7tGh3zA8/m691p9YKs7CQUjQ CetrCbV3m8FQ4kCK9N2pzvDsgZG5j/Yvsji+xSwVTBq5WEZMIsPqXb6ZWRH8IJ7N sR4+VpInGehYe/XGVBeJuR42EmgBpfRo2Nf5Im4+8y31Ovu4ug9fLgAlgmDFiedk
Bug#1023767: neomutt: unable to find gpgme-config
Hi Daniel, * Daniel Kahn Gillmor [2022-11-21 19:24]: The attached patch appears to fix things for me so that neomutt builds successfully against libgpgme-dev 1.18.0-3, though i don't know enough about how to adequately test neomutt to be confident in the results (i don't use neomutt myself). I have built neomutt with your patch and can confirm that the GPGme integration works as expected. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Bug#1024458: marked as done (seqan-needle: binary-all FTBFS)
Your message dated Tue, 22 Nov 2022 14:44:46 + with message-id and subject line Bug#1024458: fixed in seqan-needle 1.0.1.0.0.git.3011926+ds-3 has caused the Debian Bug report #1024458, regarding seqan-needle: binary-all FTBFS 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.) -- 1024458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024458 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: seqan-needle Version: 1.0.1.0.0.git.3011926+ds-2 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=seqan-needle=all=1.0.1.0.0.git.3011926%2Bds-2=1668618292=0 ... debian/rules override_dh_auto_build-indep make[1]: Entering directory '/<>' cd obj-* && /usr/bin/make doc /bin/sh: 1: cd: can't cd to obj-* make[1]: *** [debian/rules:26: override_dh_auto_build-indep] Error 2 --- End Message --- --- Begin Message --- Source: seqan-needle Source-Version: 1.0.1.0.0.git.3011926+ds-3 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of seqan-needle, 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 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated seqan-needle 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: Tue, 22 Nov 2022 19:54:37 +0530 Source: seqan-needle Architecture: source Version: 1.0.1.0.0.git.3011926+ds-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Nilesh Patra Closes: 1023807 1024458 Changes: seqan-needle (1.0.1.0.0.git.3011926+ds-3) unstable; urgency=medium . * Team Upload. * Really move needle to usr/lib/debian-med/bin (Closes: #1023807) * d/rules: Fix arch:all build (Closes: #1024458) * Disable i386 in salsa-ci.yml since seqan-needle does not build on 32-bit Checksums-Sha1: 86b88a834b2b8e20edc7f2e5d03ad5e1d49de668 1651 seqan-needle_1.0.1.0.0.git.3011926+ds-3.dsc cd03c9338dd13c1779a134b2b2ce4e383734d923 5648 seqan-needle_1.0.1.0.0.git.3011926+ds-3.debian.tar.xz c3517b0d10e31166189230d6a5b5a19b2a49668f 7222 seqan-needle_1.0.1.0.0.git.3011926+ds-3_amd64.buildinfo Checksums-Sha256: 2d32c3807dfa9c970118eeba2a5601776966e851a597ab7e49b2930677c20e44 1651 seqan-needle_1.0.1.0.0.git.3011926+ds-3.dsc 6fac59da95ec32872d22e5f6105da6ae15fe6cfe635f3ef6675878e583a814c1 5648 seqan-needle_1.0.1.0.0.git.3011926+ds-3.debian.tar.xz 65fa75fcab6a0f7643c369a8d79d66686a4fe9c1efbfc9c7387b423ebe7e87ba 7222 seqan-needle_1.0.1.0.0.git.3011926+ds-3_amd64.buildinfo Files: 5e0c8b4760dcac840121b55da6e6cb52 1651 science optional seqan-needle_1.0.1.0.0.git.3011926+ds-3.dsc 4b4ac0bd7157606a453f8c10fa93dc88 5648 science optional seqan-needle_1.0.1.0.0.git.3011926+ds-3.debian.tar.xz 4b098eacbdcc389b6df61b20ce74fc13 7222 science optional seqan-needle_1.0.1.0.0.git.3011926+ds-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCY3zcrwAKCRAqJ5BL1yQ+ 2qzKAQDTsHW+n/3FzqbJU92gUbXKq/8H6IkbYQdv9NWb3MSXagEArOJNXiHJb8kM 2uULFXQKg+pAGhL1kWXnJPazNOPHkwA= =81Q4 -END PGP SIGNATURE End Message ---
Bug#1023807: marked as done (seqan-needle: /usr/bin/needle is already shipped by emboss)
Your message dated Tue, 22 Nov 2022 14:44:46 + with message-id and subject line Bug#1023807: fixed in seqan-needle 1.0.1.0.0.git.3011926+ds-3 has caused the Debian Bug report #1023807, regarding seqan-needle: /usr/bin/needle is already shipped by emboss 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.) -- 1023807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: seqan-needle Version: 1.0.1.0.0.git.3011926+ds-1 Severity: serious There is already a (unrelated?) /usr/bin/needle binary in the Debian archive, provided by the emboss package. Andreas --- End Message --- --- Begin Message --- Source: seqan-needle Source-Version: 1.0.1.0.0.git.3011926+ds-3 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of seqan-needle, 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 1023...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated seqan-needle 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: Tue, 22 Nov 2022 19:54:37 +0530 Source: seqan-needle Architecture: source Version: 1.0.1.0.0.git.3011926+ds-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Nilesh Patra Closes: 1023807 1024458 Changes: seqan-needle (1.0.1.0.0.git.3011926+ds-3) unstable; urgency=medium . * Team Upload. * Really move needle to usr/lib/debian-med/bin (Closes: #1023807) * d/rules: Fix arch:all build (Closes: #1024458) * Disable i386 in salsa-ci.yml since seqan-needle does not build on 32-bit Checksums-Sha1: 86b88a834b2b8e20edc7f2e5d03ad5e1d49de668 1651 seqan-needle_1.0.1.0.0.git.3011926+ds-3.dsc cd03c9338dd13c1779a134b2b2ce4e383734d923 5648 seqan-needle_1.0.1.0.0.git.3011926+ds-3.debian.tar.xz c3517b0d10e31166189230d6a5b5a19b2a49668f 7222 seqan-needle_1.0.1.0.0.git.3011926+ds-3_amd64.buildinfo Checksums-Sha256: 2d32c3807dfa9c970118eeba2a5601776966e851a597ab7e49b2930677c20e44 1651 seqan-needle_1.0.1.0.0.git.3011926+ds-3.dsc 6fac59da95ec32872d22e5f6105da6ae15fe6cfe635f3ef6675878e583a814c1 5648 seqan-needle_1.0.1.0.0.git.3011926+ds-3.debian.tar.xz 65fa75fcab6a0f7643c369a8d79d66686a4fe9c1efbfc9c7387b423ebe7e87ba 7222 seqan-needle_1.0.1.0.0.git.3011926+ds-3_amd64.buildinfo Files: 5e0c8b4760dcac840121b55da6e6cb52 1651 science optional seqan-needle_1.0.1.0.0.git.3011926+ds-3.dsc 4b4ac0bd7157606a453f8c10fa93dc88 5648 science optional seqan-needle_1.0.1.0.0.git.3011926+ds-3.debian.tar.xz 4b098eacbdcc389b6df61b20ce74fc13 7222 science optional seqan-needle_1.0.1.0.0.git.3011926+ds-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCY3zcrwAKCRAqJ5BL1yQ+ 2qzKAQDTsHW+n/3FzqbJU92gUbXKq/8H6IkbYQdv9NWb3MSXagEArOJNXiHJb8kM 2uULFXQKg+pAGhL1kWXnJPazNOPHkwA= =81Q4 -END PGP SIGNATURE End Message ---
Bug#1024637: libmartchus-qtforkawesome1: missing Breaks+Replaces: libmartchus-qtforkawesome0.0.3
Package: libmartchus-qtforkawesome1 Version: 0.1.0-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. This error may also be triggered by having a predecessor package from 'sid' installed while installing the package from 'experimental'. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libmartchus-qtforkawesome1_0.1.0-1~exp1_amd64.deb ... Unpacking libmartchus-qtforkawesome1:amd64 (0.1.0-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/libmartchus-qtforkawesome1_0.1.0-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/qt5/plugins/iconengines/libmartchus-qtforkawesomeiconengine.so', which is also in package libmartchus-qtforkawesome0.0.3:amd64 0.0.3-5 Errors were encountered while processing: /var/cache/apt/archives/libmartchus-qtforkawesome1_0.1.0-1~exp1_amd64.deb cheers, Andreas libmartchus-qtforkawesome0.0.3=0.0.3-5_libmartchus-qtforkawesome1=0.1.0-1~exp1.log.gz Description: application/gzip
Processed: Re: libretro-snes9x: FTBFS with GCC 11 (-std=c++17): comparison object must be invocable as const
Processing control commands: > tag -1 pending Bug #998228 [src:libretro-snes9x] libretro-snes9x: FTBFS with GCC 11 (-std=c++17): comparison object must be invocable as const Added tag(s) pending. -- 998228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998228: libretro-snes9x: FTBFS with GCC 11 (-std=c++17): comparison object must be invocable as const
Followup-For: Bug #998228 Control: tag -1 pending Hi, I've just uploaded a NMU to DELAYED/10 fixing this FTBFS. Please let me know if I should delay it longer or cancel it. Andreas
Bug#1024627: Acknowledgement (gitlab: Fails to install)
fasttrack contains a 1.7.3 version that's new enough. The 1.8.0 version from backports is too new it seems, and it what gets installed when you just do: apt install gitlab
Processed: CVE-2022-37026 fixed in unstable
Processing commands for cont...@bugs.debian.org: > fixed 1024632 1:24.3.4.5+dfsg-1 Bug #1024632 [erlang] erlang: CVE-2022-37026 Client Authentication Bypass Marked as fixed in versions erlang/1:24.3.4.5+dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1024632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024632: erlang: CVE-2022-37026 Client Authentication Bypass
Package: erlang X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for erlang. Initially the security team triaged this issue as minor but further investigation showed the impact might be much more severe. Red Hat and other vendors consider this issue to be urgent and critical. https://nvd.nist.gov/vuln/detail/CVE-2022-37026 https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2022-37026 Sergei what are your thoughts and do you think older versions like Buster or Stretch are affected as well? CVE-2022-37026[0]: | In Erlang/OTP before 23.3.4.15, 24.x before 24.3.4.2, and 25.x before | 25.0.2, there is a Client Authentication Bypass in certain client- | certification situations for SSL, TLS, and DTLS. 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-2022-37026 https://www.cve.org/CVERecord?id=CVE-2022-37026 Please adjust the affected versions in the BTS as needed. Regards, Markus signature.asc Description: This is a digitally signed message part
Processed: Re: tome: FTBFS with GCC 10 due to insufficient #includes
Processing control commands: > tag -1 pending Bug #966065 [src:tome] tome: FTBFS with GCC 10 due to insufficient #includes Added tag(s) pending. -- 966065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966065 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966065: tome: FTBFS with GCC 10 due to insufficient #includes
Followup-For: Bug #966065 Control: tag -1 pending Hi, I've just uploaded a NMU to DELAYED/10 fixing this FTBFS. Please let me know if I should delay it longer or cancel it. Andreas
Bug#1024627: gitlab: Fails to install
Package: gitlab Version: 15.4.2+ds1-1~fto11+3 Severity: serious Setting up gitlab (15.4.2+ds1-1~fto11+3) ... Bundler could not find compatible versions for gem "omniauth-oauth2": In Gemfile: omniauth-auth0 (~> 2.0) was resolved to 2.0.0, which depends on omniauth-oauth2 (~> 1.4) x86_64-linux omniauth-authentiq (~> 0.3.3) was resolved to 0.3.3, which depends on omniauth-oauth2 (>= 1.5) x86_64-linux omniauth-azure-activedirectory-v2 (~> 1.0) was resolved to 1.0.0, which depends on omniauth-oauth2 (~> 1.7) x86_64-linux omniauth-dingtalk-oauth2 (~> 1.0) was resolved to 1.0.0, which depends on omniauth-oauth2 (~> 1.7.1) x86_64-linux omniauth-facebook (~> 4.0) was resolved to 4.0.0, which depends on omniauth-oauth2 (~> 1.2) x86_64-linux omniauth-oauth2-generic (~> 0.2.2) was resolved to 0.2.2, which depends on omniauth-oauth2 (~> 1.0) x86_64-linux Could not find gem 'omniauth-oauth2 (~> 1.7.1)', which is required by gem 'omniauth-auth0 (~> 2.0)', in any of the sources. Kurt
Bug#1019652: marked as done (ruby-regexp-parser: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(result[1]).to eq token)
Your message dated Tue, 22 Nov 2022 13:08:53 + with message-id and subject line Bug#1019652: fixed in ruby-regexp-parser 2.1.1-2.1 has caused the Debian Bug report #1019652, regarding ruby-regexp-parser: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(result[1]).to eq token 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.) -- 1019652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-regexp-parser Version: 2.1.1-2 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-regexp-parser with ruby3.1 enabled, the build failed. Relevant part of the build log (hopefully): > Failure/Error: expect(result[1]).to eq token > > expected: :meta_sequence > got: :hex > > (compared using ==) > > Diff: > @@ -1 +1 @@ > -:meta_sequence > +:hex > Shared Example Group: "scan" called from > ./spec/scanner/escapes_spec.rb:55 > # ./spec/support/shared_examples.rb:28:in `block (4 levels) in (required)>' > > Finished in 0.91623 seconds (files took 0.29242 seconds to load) > 1561 examples, 24 failures > > Failed examples: > > rspec ./spec/parser/escapes_spec.rb:59 # EscapeSequence parsing parse escape > control sequence lower > rspec ./spec/parser/escapes_spec.rb:68 # EscapeSequence parsing parse escape > control sequence upper > rspec ./spec/parser/escapes_spec.rb:77 # EscapeSequence parsing parse escape > meta sequence > rspec ./spec/parser/escapes_spec.rb:86 # EscapeSequence parsing parse escape > meta control sequence > rspec ./spec/parser/escapes_spec.rb:95 # EscapeSequence parsing parse lower c > meta control sequence > rspec ./spec/parser/escapes_spec.rb:104 # EscapeSequence parsing parse escape > reverse meta control sequence > rspec ./spec/parser/escapes_spec.rb:113 # EscapeSequence parsing parse escape > reverse lower c meta control sequence > rspec './spec/scanner/escapes_spec.rb[1:21:1]' # Escape scanning given the > pattern (?-mix:a\x02c) scans token 1 as control escape at 1..4 > rspec './spec/scanner/escapes_spec.rb[1:22:1]' # Escape scanning given the > pattern (?-mix:a\x1Ec) scans token 1 as control escape at 1..4 > rspec './spec/scanner/escapes_spec.rb[1:23:1]' # Escape scanning given the > pattern (?-mix:a\x0A) scans token 1 as control escape at 1..5 > rspec './spec/scanner/escapes_spec.rb[1:24:1]' # Escape scanning given the > pattern (?-mix:a\x1Cb) scans token 1 as control escape at 1..5 > rspec './spec/scanner/escapes_spec.rb[1:25:1]' # Escape scanning given the > pattern (?-mix:a\x02c) scans token 1 as control escape at 1..5 > rspec './spec/scanner/escapes_spec.rb[1:26:1]' # Escape scanning given the > pattern (?-mix:a\x1Eb) scans token 1 as control escape at 1..5 > rspec './spec/scanner/escapes_spec.rb[1:27:1]' # Escape scanning given the > pattern (?-mix:a\x0Ab) scans token 1 as control escape at 1..6 > rspec './spec/scanner/escapes_spec.rb[1:28:1]' # Escape scanning given the > pattern (?-mix:a\x1Cb) scans token 1 as control escape at 1..6 > rspec './spec/scanner/escapes_spec.rb[1:29:1]' # Escape scanning given the > pattern (?-mix:a\x82c) scans token 1 as control escape at 1..7 > rspec './spec/scanner/escapes_spec.rb[1:30:1]' # Escape scanning given the > pattern (?-mix:a\x82c) scans token 1 as control escape at 1..8 > rspec './spec/scanner/escapes_spec.rb[1:31:1]' # Escape scanning given the > pattern (?-mix:a\xC2c) scans token 1 as meta_sequence escape at 1..5 > rspec './spec/scanner/escapes_spec.rb[1:32:1]' # Escape scanning given the > pattern (?-mix:a\x82c) scans token 1 as meta_sequence escape at 1..7 > rspec './spec/scanner/escapes_spec.rb[1:33:1]' # Escape scanning given the > pattern (?-mix:a\x9E) scans token 1 as meta_sequence escape at 1..7 > rspec './spec/scanner/escapes_spec.rb[1:34:1]' # Escape scanning given the > pattern (?-mix:a\x8A) scans token 1 as meta_sequence escape at 1..8 > rspec './spec/scanner/escapes_spec.rb[1:35:1]' # Escape scanning given the > pattern (?-mix:a\x9C) scans token 1 as meta_sequence escape at 1..8 > rspec './spec/scanner/escapes_spec.rb[1:36:1]' # Escape scanning given the > pattern (?-mix:a\x82c) scans token 1 as meta_sequence escape at 1..8 > rspec './spec/scanner/escapes_spec.rb[1:37:1]' # Escape scanning given the > pattern (?-mix:a\x9C) scans token 1 as meta_sequence escape at
Bug#1005422: marked as done (ruby-redis-store: FTBFS: ERROR: Test "ruby2.7" failed.)
Your message dated Tue, 22 Nov 2022 13:08:46 + with message-id and subject line Bug#1005422: fixed in ruby-redis-store 1.9.0-2 has caused the Debian Bug report #1005422, regarding ruby-redis-store: FTBFS: ERROR: Test "ruby2.7" failed. 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.) -- 1005422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-redis-store Version: 1.9.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby2.7 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-redis-store/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -e gem\ \"redis-store\" > > ┌──┐ > │ Run tests for ruby2.7 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-redis-store/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -S rake -f debian/ruby-tests.rake > redis-server --daemonize yes --port 6379& > redis-server --daemonize yes --port 6380& > redis-server --daemonize yes --port 6381& > /<>/test/redis/distributed_store_test.rb:20: warning: possibly > useless use of == in void context > /<>/test/redis/store_test.rb:46: warning: ambiguous first > argument; put parentheses or a space even after `-' operator > Run options: --seed 15180 > > # Running: > > E.EDEPRECATED: global use of must_equal from > /<>/test/redis/store_test.rb:44. Use _(obj).must_equal instead. > This will fail in Minitest 6. > DEPRECATED: global use of must_equal from > /<>/test/redis/store_test.rb:45. Use _(obj).must_equal instead. > This will fail in Minitest 6. > DEPRECATED: global use of must_equal from > /<>/test/redis/store_test.rb:46. Use _(obj).must_equal instead. > This will fail in Minitest 6. > DEPRECATED: global use of must_equal from > /<>/test/redis/store_test.rb:50. Use _(obj).must_equal instead. > This will fail in Minitest 6. > DEPRECATED: global use of must_equal from > /<>/test/redis/store_test.rb:51. Use _(obj).must_equal instead. > This will fail in Minitest 6. > DEPRECATED: global use of must_equal from > /<>/test/redis/store_test.rb:52. Use _(obj).must_equal instead. > This will fail in Minitest 6. > .EDEPRECATED: global use of must_equal from > /<>/test/redis/store_test.rb:15. Use _(obj).must_equal instead. > This will fail in Minitest 6. > ... > > Finished in 0.014812s, 1080.2339 runs/s, 742.6608 assertions/s. > > 1) Error: > Redis::DistributedStore::#supports_redis_version?#test_0001_returns redis > version: > NameError: uninitialized constant OpenStruct > /<>/test/redis/distributed_store_test.rb:9:in `setup' > > 2) Error: > Redis::DistributedStore#test_0003_sets an object: > NameError: uninitialized constant OpenStruct > /<>/test/redis/distributed_store_test.rb:9:in `setup' > > 3) Error: > Redis::DistributedStore#test_0004_gets an object: > NameError: uninitialized constant OpenStruct > /<>/test/redis/distributed_store_test.rb:9:in `setup' > > 4) Error: > Redis::DistributedStore#test_0007_passes through ring replica options: > NameError: uninitialized constant OpenStruct > /<>/test/redis/distributed_store_test.rb:9:in `setup' > > 5) Error: > Redis::DistributedStore#test_0008_uses a custom ring object: > NameError: uninitialized constant OpenStruct > /<>/test/redis/distributed_store_test.rb:9:in
Bug#1024626: blender FTBFS on 32bit
Source: blender Version: 3.3.1+dfsg-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=blender=3.3.1%2Bdfsg-1 Different errors on different architectures, e.g. ... In file included from /<>/obj-mipsel-linux-gnu/source/blender/makesdna/intern/dna_verify.c:2: /<>/source/blender/blenlib/BLI_assert.h:80:37: error: static assertion failed: "DNA member offset verify" 80 | # define BLI_STATIC_ASSERT(a, msg) _Static_assert(a, msg); | ^~ ... Is anyone working on getting blender build again on 32bit? If not, I could request removal of blender (and its reverse dependencies gfpoken and morse-simulator) on the 32bit architectures to help getting blender into bookworm.
Processed: Re: Bug#1024169: csound breaks csound-plugins autopkgtest: *** stack smashing detected ***: terminated
Processing control commands: > forwarded -1 https://github.com/csound/csound/issues/1651 Bug #1024169 [src:csound, src:csound-plugins] csound breaks csound-plugins autopkgtest: *** stack smashing detected ***: terminated Set Bug forwarded-to-address to 'https://github.com/csound/csound/issues/1651'. -- 1024169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024169: csound breaks csound-plugins autopkgtest: *** stack smashing detected ***: terminated
Control: forwarded -1 https://github.com/csound/csound/issues/1651 On Tue, 15 Nov 2022 23:50:51 +0100 =?UTF-8?Q?Bernhard_=c3=9cbelacker?= wrote: > this looks like caused by a disaggrement about the size of type OPARMS. > In libcsound64-6.0 it has 264 bytes, but in csound-plugins > only 260 bytes. > > This difference is caused by the last member "mp3_mode", that is missing > in the OPARMS type used in csound-plugins. > It got introduced in commit [1] and caused this ABI break. > > Attached are relevant parts of the debugging. You email is *extremely* helpful. I have added relevant forwarded tag. Thanks! -- Best, Nilesh signature.asc Description: PGP signature
Processed: tagging 1024561, tagging 1024576, tagging 1024497, found 1024555 in 4.1.0-0.1, tagging 1024506 ...
Processing commands for cont...@bugs.debian.org:
> tags 1024561 + sid bookworm
Bug #1024561 [src:maradns] Unmaintained, keep out of stable
Added tag(s) sid and bookworm.
> tags 1024576 + sid bookworm
Bug #1024576 [src:librepo] librepo: FTBFS against libgpgme-dev >= 1.18.0-2
Added tag(s) sid and bookworm.
> tags 1024497 + sid bookworm
Bug #1024497 [src:libcryptui] libcryptui: FTBFS against libgpgme-dev >= 1.18.0-2
Added tag(s) bookworm and sid.
> found 1024555 4.1.0-0.1
Bug #1024555 [swig] xdmf FTBFS with SWIG 4.1.0
Marked as found in versions swig/4.1.0-0.1.
> tags 1024506 - bookworm sid
Bug #1024506 [src:docker.io] docker.io: FTBFS: FAIL: builder/remotecontext/git
TestCheckoutGit
Removed tag(s) sid and bookworm.
> reassign 1022255 src:python-xarray 2022.10.0-1
Bug #1022255 {Done: Alastair McKinstry }
[src:python-xarray, src:satpy] python-xarray breaks satpy autopkgtest
Bug reassigned from package 'src:python-xarray, src:satpy' to
'src:python-xarray'.
No longer marked as found in versions python-xarray/2022.10.0-1.
No longer marked as fixed in versions python-xarray/2022.11.0-2.
Bug #1022255 {Done: Alastair McKinstry }
[src:python-xarray] python-xarray breaks satpy autopkgtest
Marked as found in versions python-xarray/2022.10.0-1.
> fixed 1022255 2022.11.0-2
Bug #1022255 {Done: Alastair McKinstry }
[src:python-xarray] python-xarray breaks satpy autopkgtest
Marked as fixed in versions python-xarray/2022.11.0-2.
> fixed 1021215 1:1.6.3-1
Bug #1021215 {Done: Sudip Mukherjee }
[src:libtraceevent] Kind request for backports of libtraceevent and libtracefs
Marked as fixed in versions libtraceevent/1:1.6.3-1.
> notfixed 1020822 0.14-0-3
Bug #1020822 {Done: Carsten Schoenert }
[src:python-flask-marshmallow] python-flask-marshmallow: autopkgtest regression
with flask 2.2.2
The source 'python-flask-marshmallow' and version '0.14-0-3' do not appear to
match any binary packages
No longer marked as fixed in versions 0.14-0-3.
> fixed 1020822 0.14.0-3
Bug #1020822 {Done: Carsten Schoenert }
[src:python-flask-marshmallow] python-flask-marshmallow: autopkgtest regression
with flask 2.2.2
Marked as fixed in versions python-flask-marshmallow/0.14.0-3.
> reassign 897275 llvm-14,llvm-15,llvm-13,llvm-16
Bug #897275 [llvm-10,llvm-13,llvm-14,llvm-15,llvm-16] llvm-6.0 should provide a
pkg-config file
Warning: Unknown package 'llvm-10'
Bug reassigned from package 'llvm-10,llvm-13,llvm-14,llvm-15,llvm-16' to
'llvm-14,llvm-15,llvm-13,llvm-16'.
Ignoring request to alter found versions of bug #897275 to the same values
previously set
Ignoring request to alter fixed versions of bug #897275 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1020822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020822
1021215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021215
1022255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022255
1024497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024497
1024506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024506
1024555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024555
1024561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024561
1024576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024576
897275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: retitle 732570 to RM: libarch-perl -- RoM; dead upstream, very low popcon count
Processing commands for cont...@bugs.debian.org: > retitle 732570 RM: libarch-perl -- RoM; dead upstream, very low popcon count Bug #732570 [ftp.debian.org] libarch-perl should be removed Changed Bug title to 'RM: libarch-perl -- RoM; dead upstream, very low popcon count' from 'libarch-perl should be removed'. > thanks Stopping processing here. Please contact me if you need assistance. -- 732570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1023046: marked as done (zabbix: FTBFS: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod))
Your message dated Tue, 22 Nov 2022 10:07:40 +
with message-id
and subject line Bug#1023046: fixed in zabbix 1:6.0.10+dfsg-1
has caused the Debian Bug report #1023046,
regarding zabbix: FTBFS: unsafe.Slice requires go1.17 or later (-lang was set
to go1.16; check go.mod)
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.)
--
1023046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zabbix
Version: 1:6.0.9+dfsg-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
While rebuilding the reverse build dependencies of another golang
package I'm updating, I noticed that zabbix fails to build in a clean
sid chroot. I suspect this was likely caused by the recent update of
the golang-golang-x-sys package, but I haven't investigated further.
> on.compileArch=`go env GOARCH` -X main.applicationName=zabbix_web_service" -o
> bin zabbix.com/cmd/zabbix_web_service
>
> [snip]
>
> golang.org/x/text/unicode/norm
> # golang.org/x/sys/unix
> vendor/golang.org/x/sys/unix/syscall.go:83:16: unsafe.Slice requires go1.17
> or later (-lang was set to go1.16; check go.mod)
> vendor/golang.org/x/sys/unix/syscall_linux.go:2255:9: unsafe.Slice requires
> go1.17 or later (-lang was set to go1.16; check go.mod)
> vendor/golang.org/x/sys/unix/syscall_unix.go:118:7: unsafe.Slice requires
> go1.17 or later (-lang was set to go1.16; check go.mod)
> vendor/golang.org/x/sys/unix/sysvshm_unix.go:33:7: unsafe.Slice requires
> go1.17 or later (-lang was set to go1.16; check go.mod)
> zabbix.com/pkg/procfs
> # golang.org/x/sys/unix
> vendor/golang.org/x/sys/unix/syscall.go:83:16: unsafe.Slice requires go1.17
> or later (-lang was set to go1.16; check go.mod)
> vendor/golang.org/x/sys/unix/syscall_linux.go:2255:9: unsafe.Slice requires
> go1.17 or later (-lang was set to go1.16; check go.mod)
> vendor/golang.org/x/sys/unix/syscall_unix.go:118:7: unsafe.Slice requires
> go1.17 or later (-lang was set to go1.16; check go.mod)
> vendor/golang.org/x/sys/unix/sysvshm_unix.go:33:7: unsafe.Slice requires
> go1.17 or later (-lang was set to go1.16; check go.mod)
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: zabbix
Source-Version: 1:6.0.10+dfsg-1
Done: Dmitry Smirnov
We believe that the bug you reported is fixed in the latest version of
zabbix, 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 1023...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dmitry Smirnov (supplier of updated zabbix 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: Tue, 22 Nov 2022 14:54:48 +1100
Source: zabbix
Architecture: source
Version: 1:6.0.10+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov
Changed-By: Dmitry Smirnov
Closes: 1023046
Changes:
zabbix (1:6.0.10+dfsg-1) unstable; urgency=medium
.
* New upstream release.
* Use bundled "golang.org/x/{sys|net}" to fix FTBFS (Closes: #1023046).
* Standards-Version: 4.6.1
Checksums-Sha1:
c9911d40177f4a25d0844907ca72d4313b5faf9e 4033 zabbix_6.0.10+dfsg-1.dsc
f5889d3b49e41ca6995707bb2dd7d10d5798e271 12363584
zabbix_6.0.10+dfsg.orig-templates.tar.xz
fa11390981460c36a4dd9d4224c68fa39f92c52a 1128628
zabbix_6.0.10+dfsg.orig-vendor.tar.xz
bd1601f142af20733c9fd4958fde80e09796a272 20783776
zabbix_6.0.10+dfsg.orig.tar.xz
a5500ef015c5d94ddd753e09ddbdf1b74a5f4cbc 229272
zabbix_6.0.10+dfsg-1.debian.tar.xz
9d2d5db2279e59dd759079736c9cb82cbbaa5bdd 19856
zabbix_6.0.10+dfsg-1_amd64.buildinfo
Checksums-Sha256:
580cfb50c9abcd6aa9336bc704d192f6a06949d0ca9112821372b2d9297d1136 4033
zabbix_6.0.10+dfsg-1.dsc
4c4e4238a3c586a4926672474ee40a86a81133c63aedb08d095118a2fa28d04f 12363584
zabbix_6.0.10+dfsg.orig-templates.tar.xz
0a453c7ca16a9a1691ee105922de7836e6cc244c574235a9624a2a326a15a6b2 1128628
zabbix_6.0.10+dfsg.orig-vendor.tar.xz
894a9ac0465ad8faa6b3ea90dbf4ff957fb2f926d86073b4f32d3c7a859f2175 20783776
zabbix_6.0.10+dfsg.orig.tar.xz
ee9b9fb4e85239dd1248b24e8e86bb4de484359dbc01d5ac931e3b22571e3e7c 229272
Bug#983815: marked as done (python-crc32c: Baseline violation on amd64/arm64/i386 and FTBFS on armhf if built on 64bit hardware)
Your message dated Tue, 22 Nov 2022 09:51:39 +
with message-id
and subject line Bug#983815: fixed in python-crc32c 2.3-1.1
has caused the Debian Bug report #983815,
regarding python-crc32c: Baseline violation on amd64/arm64/i386 and FTBFS on
armhf if built on 64bit hardware
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.)
--
983815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-crc32c
Version: 2.2-1
Severity: serious
Tags: ftbfs patch
For the FTBFS:
https://buildd.debian.org/status/logs.php?pkg=python-crc32c=armhf
Fix is attached.
Description: Fix baseline violations on x86 and arm
These extensions are not part of the baseline of any port.
Author: Adrian Bunk
--- python-crc32c-2.2.orig/setup.py
+++ python-crc32c-2.2/setup.py
@@ -39,10 +39,6 @@ def get_extra_compile_args(is_intel, is_
comp = distutils.ccompiler.get_default_compiler()
if comp == 'msvc':
return ['/O2']
-elif is_intel:
-return ['-O3', '-msse4.2', '-mpclmul']
-elif is_arm:
-return ['-O3', '-march=armv8-a+crc+crypto']
else:
return ['-O3']
@@ -63,10 +59,6 @@ class _build_ext(build_ext):
is_arm = platform in ['aarch64_be', 'aarch64', 'armv8b', 'armv8l']
distutils.log.info("platform: %s, is_intel: %d, is_arm: %d", platform,
is_intel, is_arm)
self.distribution.ext_modules[0].extra_compile_args =
get_extra_compile_args(is_intel, is_arm)
-if is_intel:
-self.distribution.ext_modules[0].define_macros += [('IS_INTEL',
None)]
-elif is_arm:
-self.distribution.ext_modules[0].define_macros += [('IS_ARM',
None)]
build_ext.run(self)
--- End Message ---
--- Begin Message ---
Source: python-crc32c
Source-Version: 2.3-1.1
Done: Adrian Bunk
We believe that the bug you reported is fixed in the latest version of
python-crc32c, 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 983...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian Bunk (supplier of updated python-crc32c 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, 19 Nov 2022 00:42:32 +0200
Source: python-crc32c
Architecture: source
Version: 2.3-1.1
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard
Changed-By: Adrian Bunk
Closes: 983815
Changes:
python-crc32c (2.3-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Fix baseline violation on x86 and arm. (Closes: #983815)
Checksums-Sha1:
8d383cfa2d2e0aff2ec6b7599b5d622c9650c039 1957 python-crc32c_2.3-1.1.dsc
4f67204400be47dadbe898f2fb505c919fa12c11 4980
python-crc32c_2.3-1.1.debian.tar.xz
Checksums-Sha256:
74a5a31f38a0147cd3c70839f11ce6d3804ad8995bb5fe3d2916a5e234821d33 1957
python-crc32c_2.3-1.1.dsc
3928ae2af6b61a5929336eddb413caddd0450489a28efc16d4b1a9cf190d67fa 4980
python-crc32c_2.3-1.1.debian.tar.xz
Files:
bfe4d864673ff992e63fbd3fe6002540 1957 python optional python-crc32c_2.3-1.1.dsc
9bfa7a1be2ceb51ae709a0be2a42b97b 4980 python optional
python-crc32c_2.3-1.1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmN4DEQACgkQiNJCh6LY
mLHoRxAAmAMcOslxfZvtNSUYYsmIXsYKZjJkU1JHkeODXnyVl00nYlj8DCWWqbzI
OHKbhI48vx3YK8J8reOaz60mSxnXvIv5Svc3Fb4rbegO8WFRGEBEv4mDf+fG6o/k
sWmVUgNAAcKc8II9+F84yPfK/rz3doERtn+OUT5CR+3Kpkv+SwTmSct4C1YmdhK7
mqDp72R3sFXizxqyRzW0LsWkfXt2Bu0dmsR5pVbNLB6ij8/c2f/RQr3XiQjX+l2D
fsTUMpQ3XI/d2V7pFYa5+eCxlRrjooJp6oHq+tCYNt1tjL5U+Z/gZ+LET0Jt+zit
Q10vtYQT+TJ6nmhGwuXmb/cfSCbGXW6jjsvM3AytROlN7ziumsnKviefIg4NHNWj
uiLWDtsHUE91+lwsMcMHjHJC+eIq8xlDs8xcBsmJtH2twxN7n+ilaH+1hxRzRV4M
WZo/YGpvYQXAWUOBcXC4XYK6aGMjdYPsut6YqVbLxALCSzga4V8KrimtZQY9w4h6
A58I2BOZm/1aC9bIMtnPICdr/A5+FFH55oo8JsHfoYZa5WVNkMsflKeAMvSYsehj
I3UUh4Ao39urgSKPktDEcLel+SL2t8wHJMtsJ1JPK3HYUCU8GajG2GbNCKjHIAb5
tXeBde/sRs6xaZJPHiQo/nKiLQWRl3IHZvOEwbFMUqlEQsRSuck=
=tclf
-END PGP SIGNATURE End Message ---
Bug#1023959: marked as done (python-crc32c ftbfs on arm64)
Your message dated Tue, 22 Nov 2022 09:51:39 + with message-id and subject line Bug#983815: fixed in python-crc32c 2.3-1.1 has caused the Debian Bug report #983815, regarding python-crc32c ftbfs on arm64 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.) -- 983815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-crc32c Version: 2.3-1 Severity: serious Tags: sid bookworm ftbfs User: debian-pyt...@lists.debian.org Usertag: python3.11 [...] In file included from crc32c_arm64.c:22: /usr/lib/gcc/aarch64-linux-gnu/12/include/arm_acle.h: In function ‘_crc32c_hw_arm64’: /usr/lib/gcc/aarch64-linux-gnu/12/include/arm_acle.h:197:1: error: inlining failed in call to ‘always_inline’ ‘__crc32cd’: target specific option mismatch 197 | __crc32cd (uint32_t __a, uint64_t __b) | ^ crc32c_arm64.c:91:12: note: called from here 91 | crc ^= __crc32cd(0, t0); |^~~~ --- End Message --- --- Begin Message --- Source: python-crc32c Source-Version: 2.3-1.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of python-crc32c, 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 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated python-crc32c 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, 19 Nov 2022 00:42:32 +0200 Source: python-crc32c Architecture: source Version: 2.3-1.1 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Adrian Bunk Closes: 983815 Changes: python-crc32c (2.3-1.1) unstable; urgency=medium . * Non-maintainer upload. * Fix baseline violation on x86 and arm. (Closes: #983815) Checksums-Sha1: 8d383cfa2d2e0aff2ec6b7599b5d622c9650c039 1957 python-crc32c_2.3-1.1.dsc 4f67204400be47dadbe898f2fb505c919fa12c11 4980 python-crc32c_2.3-1.1.debian.tar.xz Checksums-Sha256: 74a5a31f38a0147cd3c70839f11ce6d3804ad8995bb5fe3d2916a5e234821d33 1957 python-crc32c_2.3-1.1.dsc 3928ae2af6b61a5929336eddb413caddd0450489a28efc16d4b1a9cf190d67fa 4980 python-crc32c_2.3-1.1.debian.tar.xz Files: bfe4d864673ff992e63fbd3fe6002540 1957 python optional python-crc32c_2.3-1.1.dsc 9bfa7a1be2ceb51ae709a0be2a42b97b 4980 python optional python-crc32c_2.3-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmN4DEQACgkQiNJCh6LY mLHoRxAAmAMcOslxfZvtNSUYYsmIXsYKZjJkU1JHkeODXnyVl00nYlj8DCWWqbzI OHKbhI48vx3YK8J8reOaz60mSxnXvIv5Svc3Fb4rbegO8WFRGEBEv4mDf+fG6o/k sWmVUgNAAcKc8II9+F84yPfK/rz3doERtn+OUT5CR+3Kpkv+SwTmSct4C1YmdhK7 mqDp72R3sFXizxqyRzW0LsWkfXt2Bu0dmsR5pVbNLB6ij8/c2f/RQr3XiQjX+l2D fsTUMpQ3XI/d2V7pFYa5+eCxlRrjooJp6oHq+tCYNt1tjL5U+Z/gZ+LET0Jt+zit Q10vtYQT+TJ6nmhGwuXmb/cfSCbGXW6jjsvM3AytROlN7ziumsnKviefIg4NHNWj uiLWDtsHUE91+lwsMcMHjHJC+eIq8xlDs8xcBsmJtH2twxN7n+ilaH+1hxRzRV4M WZo/YGpvYQXAWUOBcXC4XYK6aGMjdYPsut6YqVbLxALCSzga4V8KrimtZQY9w4h6 A58I2BOZm/1aC9bIMtnPICdr/A5+FFH55oo8JsHfoYZa5WVNkMsflKeAMvSYsehj I3UUh4Ao39urgSKPktDEcLel+SL2t8wHJMtsJ1JPK3HYUCU8GajG2GbNCKjHIAb5 tXeBde/sRs6xaZJPHiQo/nKiLQWRl3IHZvOEwbFMUqlEQsRSuck= =tclf -END PGP SIGNATURE End Message ---
Bug#1024000: marked as done (pink-pony: FTBFS: OSError: 'pkg-config IlmBase --cflags --libs' exited 1)
Your message dated Tue, 22 Nov 2022 09:51:28 +
with message-id
and subject line Bug#1024000: fixed in pink-pony 1.4.1-3.1
has caused the Debian Bug report #1024000,
regarding pink-pony: FTBFS: OSError: 'pkg-config IlmBase --cflags --libs'
exited 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.)
--
1024000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pink-pony
Version: 1.4.1-3
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
scons: Reading SConscript files ...
Package IlmBase was not found in the pkg-config search path.
Perhaps you should add the directory containing `IlmBase.pc'
to the PKG_CONFIG_PATH environment variable
Package 'IlmBase', required by 'virtual:world', not found
OSError: 'pkg-config IlmBase --cflags --libs' exited 1:
File "/<>/SConstruct.Debian", line 10:
env.ParseConfig("pkg-config IlmBase --cflags --libs")
File "/usr/lib/python3/dist-packages/SCons/Environment.py", line 1674:
return function(self, self.backtick(command), unique)
File "/usr/lib/python3/dist-packages/SCons/Environment.py", line 597:
raise OSError("'%s' exited %d" % (command, status))
make: *** [debian/rules:37: build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: pink-pony
Source-Version: 1.4.1-3.1
Done: Adrian Bunk
We believe that the bug you reported is fixed in the latest version of
pink-pony, 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 1024...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian Bunk (supplier of updated pink-pony 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, 19 Nov 2022 00:18:31 +0200
Source: pink-pony
Architecture: source
Version: 1.4.1-3.1
Distribution: unstable
Urgency: low
Maintainer: Debian Games Team
Changed-By: Adrian Bunk
Closes: 880943 1024000
Changes:
pink-pony (1.4.1-3.1) unstable; urgency=low
.
* Non-maintainer upload.
* Fix compilation with libimath-dev. (Closes: #1024000)
* Add upstream fix for Fancy Water. (Closes: #880943)
Checksums-Sha1:
952105d6d178c590ba2a1e6f4dcdcf25bab56aee 2259 pink-pony_1.4.1-3.1.dsc
e9e58126061863ceb4d9ac114939501259bac4c0 65264
pink-pony_1.4.1-3.1.debian.tar.xz
Checksums-Sha256:
56727a87eaba4167828a286d2d76fcd9b0eb81bf314edcc77d78624aae72a49c 2259
pink-pony_1.4.1-3.1.dsc
b5757f84d9b60a93f2710dc1f3191f68a20acad67abf2fc744568235bf486f11 65264
pink-pony_1.4.1-3.1.debian.tar.xz
Files:
719afe6b772aa929354b6b6d22d771d2 2259 games optional pink-pony_1.4.1-3.1.dsc
0385d110348f745bef037369ae90dfcc 65264 games optional
pink-pony_1.4.1-3.1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmN4CAMACgkQiNJCh6LY
mLEcJBAAxU1Fw2frqIXHe9Iut+SDaB4XldiqpAoH5G8OvSColRsU8AIXG3N5MjCI
txcp8i5st9uHzsQ1X57Y+1qBvg3TaWcGbbsaWW6Li98L/PRzPWpEXOCoMiUlbTeO
FwXl3u/HsUnkIahLbtm8tgPUTR5SeT+OVM5gkzkwVNCPDghYFibyT72oOTlYJdcO
oDh98hsgFFe/yHKzbgGLU6NMAb02D5ltzsOdechh4pqZq6l+EzzJVEna8UOHO8/l
bvkEoL/0siFkOczhsMzdUDD19ATcxOmZStGrwCTS+sULJ5JES9MktJl8sdqt3yXl
dTRSCjTvYi7he080SHcMmggnIeFfT6gvVTcn/XMe3z/iuBctXlPHiLsVhbhslff9
X/WrJrrtNjkr6QHVniHv/VTWCc0foBxZ6qU2AQslvc/L/Ubr8eqnOi9JXYU6Z6/B
cybws/TFiyFKa06BE9B7DMgyyZj5nvZbIf/Y0Rg56znp48oUjxn1O2mFO4AcxjiQ
SsNLaTqC0vdk6UmKlAhsfpPf9QDR3vN8Px7anMxQCMOcFwkvfqgsmkLPeL1BETda
IC5+L/7PgdlyHWMNhwVOmNi9QKIfVp2V0tZ94BjfbqcGzmW2rr69wd6TO43FkUD0
PqnmuDJtZ9PfuzxHgFAmQ7vS/aywbf2PWM+gC+FcHu5Ok0RV7xA=
=N+dE
-END PGP SIGNATURE End Message ---
Bug#1023999: marked as done (stormbaancoureur: build-depends on missing: plib1.8.4-dev)
Your message dated Tue, 22 Nov 2022 09:51:56 + with message-id and subject line Bug#1023999: fixed in stormbaancoureur 2.1.6-3.1 has caused the Debian Bug report #1023999, regarding stormbaancoureur: build-depends on missing: plib1.8.4-dev 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.) -- 1023999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: stormbaancoureur Version: 2.1.6-3 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/package.php?p=stormbaancoureur stormbaancoureur build-depends on missing: - plib1.8.4-dev:amd64 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: stormbaancoureur Source-Version: 2.1.6-3.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of stormbaancoureur, 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 1023...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated stormbaancoureur 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, 18 Nov 2022 18:12:00 +0200 Source: stormbaancoureur Architecture: source Version: 2.1.6-3.1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Adrian Bunk Closes: 1023999 Changes: stormbaancoureur (2.1.6-3.1) unstable; urgency=medium . * Non-maintainer upload. * Build depend on libplib-dev instead of plib1.8.4-dev. (Closes: #1023999) Checksums-Sha1: 3eaf585c710439947b39d27e3434ababed31d23d 2182 stormbaancoureur_2.1.6-3.1.dsc 4f1be7683a2fea2bc53c8f8b2b0ff72afad6a6b7 12228 stormbaancoureur_2.1.6-3.1.debian.tar.xz Checksums-Sha256: b875ba37c27496da361ca740213770d45cce6963d2c6d8c63aa66c2fa5fc4c22 2182 stormbaancoureur_2.1.6-3.1.dsc a3d1da1b7c4dc2c5251e3369f637ff4827c485510fc3e3e2e654ac9d634484e1 12228 stormbaancoureur_2.1.6-3.1.debian.tar.xz Files: df7e9298b82bc8948c026a25ea0a6d3d 2182 games optional stormbaancoureur_2.1.6-3.1.dsc 2a008385b8b5becd151d1d9fb0d06736 12228 games optional stormbaancoureur_2.1.6-3.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmN3+g4ACgkQiNJCh6LY mLFq9RAAkkZkgf8scVV6jUk62NHI9r3YIyFbRNkBHDfuEbYD6CbWbbRL7L524zZ6 hnHYTuOWO02vm9imWSNm9BGUB7cYe0aSP7+GWXmWuKFt50GiUhvjjmxGLXmoe0hi Kp2XXtc4Tgz5deXALtgE/kaCwlGAdyD/qssbjD5o7rJCWkBmCDP/7By4SCzCibzW i/K/0RGfnyhj+sltq97O3AMWqxCzt6Mjz+Hrc/lCYeCxIXEbKblf6nzCC6kemfld B35wBiXg7qbf0SXEz7NAefmcU1bgwoizgrIgxkGAuiyvHAHWQHOxZjyZZII58pWI e6vCNDaClAONWGpa/6tIPJ5lQ37RZryv9MsjhTWgdwpoE6fYL44k6ph5efITultI OzZYoL7JS5DEFvpv30J8h9l7r4lJbs8nFm1YPGodeDWvXdkwLWiOkr6FaKM+grNb MYv/faUHNy0X7t0BfTsVP1lwk2eyATubWp26wWiXUFZjU9VE96+UFkUyLAJkVgsx MeD4WjqMJwhoUD3V01OYKQN7hkqUwFpowjsHpYsxIi//ivX6Wb2d2X1AxtsjCrWt AKeqwPCDoKy83qauRn5vu+s4b7sI2l7bRNraIIHmq2rG94SCJbgGFGu3l6gVakL6 e0x/QAKVpaQLokBLZPPYV4GZeKZgR9HzyRv2+52mrTQyLKSP5nI= =ngVQ -END PGP SIGNATURE End Message ---
Bug#1020153: magit: FTBFS: make[2]: *** [Makefile:111: test] Error 255
Hi,
I ended up here after realizing that a bunch of Emacs packages I use
got removed from testing due to this bug.
Lucas Nussbaum (2022-09-18):
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
>> make[2]: Entering directory '/<>'
>> Loading /<>/t/magit-tests.el (source)...
>> Debugger entered--Lisp error: (error "Cannot find suitable directory for
>> output in ‘nati...")
>> error("Cannot find suitable directory for output in `nati...")
>> comp-trampoline-compile(abort-recursive-edit)
I can reproduce this with sbuild, but not with pbuilder.
It seems to belong the same class of errors that was fixed in dh-elpa with
https://salsa.debian.org/emacsen-team/dh-elpa/-/commit/d80ee7a8a159f20316640ec9e6a928e3c57d3f6e
But magit's debian/rule has override_dh_elpa_test, so we don't benefit
from the dh-elpa fix.
The attached patch replicates the dh-elpa fix in t/magit-tests.el,
which fixes the problem allows running the test suite.
Unfortunately, 2/20 tests fail, so the attached patch won't fit the
FTBFS (which is why I'm not tagging this "patch"):
Loading /<>/t/magit-tests.el (source)...
Cannot determine Magit’s version (error "/<>/lisp/magit.el" repo
static elpa dirname hash)
Running 20 tests (2022-11-22 08:13:25+, selector ‘t’)
passed 1/20 magit--with-safe-default-directory (0.015131 sec)
Keeping test directory:
/tmp/magit-TDFbME/
Test magit-get backtrace:
signal(magit-git-error ("clone of '/tmp/magit-TDFbME/remote' into su
(condition-case err (let* ((vnew #'(lambda ( _))) (old (symbol-
(let ((dir (file-name-as-directory (make-temp-file "magit-" t))) (pr
(let ((lexical-binding nil)) (let ((dir (file-name-as-directory (mak
(lambda nil (let ((lexical-binding nil)) (let ((dir (file-name-as-di
ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
ert-run-test(#s(ert-test :name magit-get :documentation nil :body (l
ert-run-or-rerun-test(#s(ert--stats :selector t :tests [... ... ...
ert-run-tests(t #f(compiled-function (event-type event-args) #
ert-run-tests-batch(nil)
ert-run-tests-batch-and-exit()
(progn (load-file "t/magit-tests.el") (ert-run-tests-batch-and-exit)
command-line-1(("-L" "./lisp" "-L" "/usr/share/emacs/site-lisp/elpa-
command-line()
normal-top-level()
Test magit-get condition:
(magit-git-error "clone of '/tmp/magit-TDFbME/remote' into submodule path
'/tmp/magit-TDFbME/super/repo' failed (in /tmp/magit-TDFbME/super/)")
FAILED 2/20 magit-get (0.708641 sec)
passed 3/20 magit-get-boolean (0.199891 sec)
passed 4/20 magit-get-{current|next}-tag (0.749619 sec)
passed 5/20 magit-in-bare-repo (0.071072 sec)
passed 6/20 magit-in-non-bare-repo (0.080570 sec)
passed 7/20 magit-list-{|local-|remote-}branch-names (0.366282 sec)
passed 8/20 magit-process:match-prompt-match-non-first-prompt (0.91
sec)
passed 9/20 magit-process:match-prompt-nil-when-no-match (0.65 sec)
passed 10/20 magit-process:match-prompt-non-nil-when-match (0.61 sec)
passed 11/20 magit-process:match-prompt-preserves-match-group (0.000111
sec)
passed 12/20 magit-process:match-prompt-suffixes-prompt (0.98 sec)
passed 13/20 magit-process:password-prompt (0.000111 sec)
passed 14/20 magit-process:password-prompt-observed (0.001084 sec)
passed 15/20 magit-status:file-sections (0.868935 sec)
passed 16/20 magit-status:log-sections (0.907880 sec)
passed 17/20 magit-toplevel:basic (0.245211 sec)
Keeping test directory:
/tmp/magit-6jLVvi/
Test magit-toplevel:submodule backtrace:
signal(magit-git-error ("clone of '/tmp/magit-6jLVvi/remote' into su
(condition-case err (let* ((vnew #'(lambda ( _))) (old (symbol-
(let ((dir (file-name-as-directory (make-temp-file "magit-" t))) (pr
(let ((find-file-visit-truename nil)) (let ((dir (file-name-as-direc
(let ((lexical-binding nil)) (let ((find-file-visit-truename nil)) (
(lambda nil (let ((lexical-binding nil)) (let ((find-file-visit-true
ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
ert-run-test(#s(ert-test :name magit-toplevel:submodule :documentati
ert-run-or-rerun-test(#s(ert--stats :selector t :tests ... :test-map
ert-run-tests(t #f(compiled-function (event-type event-args) #
ert-run-tests-batch(nil)
ert-run-tests-batch-and-exit()
(progn (load-file "t/magit-tests.el") (ert-run-tests-batch-and-exit)
command-line-1(("-L" "./lisp" "-L" "/usr/share/emacs/site-lisp/elpa-
command-line()
normal-top-level()
Test magit-toplevel:submodule condition:
(magit-git-error "clone of '/tmp/magit-6jLVvi/remote' into submodule path
'/tmp/magit-6jLVvi/super/repo' failed (in /tmp/magit-6jLVvi/super/)")
FAILED 18/20 magit-toplevel:submodule (0.249347 sec)
passed 19/20 magit-toplevel:tramp (1.286620 sec)
passed 20/20 magit-utils:add-face-text-property (0.50 sec)
Ran 20 tests, 18 results as expected, 2
