Processed: tagging 1030653, bug 1030653 is forwarded to https://github.com/wmayner/pyemd/pull/64
Processing commands for cont...@bugs.debian.org: > tags 1030653 + patch Bug #1030653 [src:pyemd] pyemd: missing dependency on numpy Added tag(s) patch. > forwarded 1030653 https://github.com/wmayner/pyemd/pull/64 Bug #1030653 [src:pyemd] pyemd: missing dependency on numpy Set Bug forwarded-to-address to 'https://github.com/wmayner/pyemd/pull/64'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1030653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030653 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030475: marked as done (projectile: FTBFS: make[1]: *** [debian/rules:12: override_dh_elpa_test] Error 255)
Your message dated Mon, 06 Feb 2023 07:05:14 + with message-id and subject line Bug#1030475: fixed in projectile 2.7.0-2 has caused the Debian Bug report #1030475, regarding projectile: FTBFS: make[1]: *** [debian/rules:12: override_dh_elpa_test] Error 255 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.) -- 1030475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030475 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: projectile Version: 2.7.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230203 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 '/<>' > buttercup -L . \ > --eval "(with-eval-after-load 'comp (push 'insert-file-contents > native-comp-never-optimize-functions))" > Loading /etc/emacs/site-start.d/00debian.el (source)... > Loading /etc/emacs/site-start.d/50autoconf.el (source)... > Running tests on Emacs 28.2 > Running 193 specs. > > projectile-project-name > return projectile-project-name when present > [32m return projectile-project-name when present[0m (2.71ms) > uses projectile-project-name-function to get the project name from the > project dir > [32m uses projectile-project-name-function to get the project name from the > project dir[0m (0.12ms) > acts on the current project is not passed a project dir explicitly > [32m acts on the current project is not passed a project dir explicitly[0m > (0.12ms) > > projectile-prepend-project-name > prepends the project name to its parameter > [32m prepends the project name to its parameter[0m (0.09ms) > > projectile-expand-root > expands a relative path into an absolute path within a project > [32m expands a relative path into an absolute path within a project[0m > (0.23ms) > > projectile-expand-file-name-wildcard > expands a filename not containing wildcards > [32m expands a filename not containing wildcards[0m (0.10ms) > does not try to resolve wildcards if there are none in the pattern > [32m does not try to resolve wildcards if there are none in the pattern[0m > (0.12ms) > returns the first wildcard result if any exist > [32m returns the first wildcard result if any exist[0m (0.08ms) > returns the expanded result if the are no wildcard results > [32m returns the expanded result if the are no wildcard results[0m (0.10ms) > > projectile--combine-plists > Items in second plist override elements in first > [32m Items in second plist override elements in first[0m (0.10ms) > Nil elements in second plist override elements in first > [32m Nil elements in second plist override elements in first[0m (0.15ms) > > projectile-register-project-type > prepends new projects to projectile-project-types > [32m prepends new projects to projectile-project-types[0m (0.34ms) > > projectile-update-project-type > Updates existing project type in projectile-project-types > [32m Updates existing project type in projectile-project-types[0m (0.20ms) > Updates existing project type with nil value > [32m Updates existing project type with nil value[0m (0.13ms) > Updates existing project type using all options > [32m Updates existing project type using all options[0m (0.18ms) > Error when attempt to update nonexistent project type > [32m Error when attempt to update nonexistent project type[0m (0.12ms) > changes project type precedence > [32m changes project type precedence[0m (1.53ms) > errors if :precedence not valid > [32m errors if :precedence not valid[0m (0.14ms) > > projectile-project-type > detects the type of Projectile's project > [32m detects the type of Projectile's project[0m (34.60ms) > caches the project type > [32m caches the project type[0m (0.89ms) > detects the type of Projectile's project when it is passed as args > [32m detects the type of Projectile's project when it is passed as args[0m > (9.29ms) > override by projectile-project-type > is respected when no DIR is passed > [32mis respected when no DIR is passed[0m (0.09ms) > has no effect when DIR is passed > [32mhas no effect when DIR is passed[0m (1.13ms) > > projectile-ignored-directory-p > checks if directory should be ignored > [32m checks if directory should be ignored[0m (0.21ms) > > projectile-ignored-file-p > checks if file should be ignored > [32m checks if file should be ignored[0m (0.11ms) > > projectile-ignored-files > returns list of igno
Bug#997130: marked as done (acmetool: FTBFS: util_test.go:24: error: x509: signature over certificate returned by signer is invalid: crypto/rsa: verification error)
Your message dated Mon, 06 Feb 2023 07:04:00 + with message-id and subject line Bug#997130: fixed in acmetool 0.2.2-1 has caused the Debian Bug report #997130, regarding acmetool: FTBFS: util_test.go:24: error: x509: signature over certificate returned by signer is invalid: crypto/rsa: verification error 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.) -- 997130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997130 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: acmetool Version: 0.2.1-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build -- -ldflags "-X > github.com/hlandau/acmetool/hooks.DefaultPath=/etc/acme/hooks -X > github.com/hlandau/buildinfo.RawBuildInfo=YWNtZXRvb2wgRGViaWFuIHZlcnNpb24gMC4yLjEtNA==" > cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 -ldflags "-X > github.com/hlandau/acmetool/hooks.DefaultPath=/etc/acme/hooks -X > github.com/hlandau/buildinfo.RawBuildInfo=YWNtZXRvb2wgRGViaWFuIHZlcnNpb24gMC4yLjEtNA==" > github.com/hlandau/acmetool github.com/hlandau/acmetool/cli > github.com/hlandau/acmetool/cmd/acmetool github.com/hlandau/acmetool/fdb > github.com/hlandau/acmetool/hooks github.com/hlandau/acmetool/interaction > github.com/hlandau/acmetool/redirector github.com/hlandau/acmetool/responder > github.com/hlandau/acmetool/responder/reshttp > github.com/hlandau/acmetool/solver github.com/hlandau/acmetool/storage > github.com/hlandau/acmetool/storageops github.com/hlandau/acmetool/util > internal/unsafeheader > internal/goexperiment > internal/abi > internal/cpu > runtime/internal/atomic > runtime/internal/sys > runtime/internal/math > internal/race > sync/atomic > unicode > internal/bytealg > unicode/utf8 > crypto/internal/subtle > crypto/subtle > math/bits > internal/itoa > runtime > math > internal/nettrace > golang.org/x/sys/internal/unsafeheader > github.com/rivo/uniseg > container/list > unicode/utf16 > vendor/golang.org/x/crypto/cryptobyte/asn1 > vendor/golang.org/x/crypto/internal/subtle > encoding > gopkg.in/hlandau/service.v2/gsptcall > internal/reflectlite > sync > internal/testlog > internal/singleflight > math/rand > gopkg.in/hlandau/configurable.v1 > runtime/cgo > errors > sort > io > strconv > internal/oserror > bytes > strings > reflect > syscall > bufio > path > hash > crypto > vendor/golang.org/x/net/dns/dnsmessage > internal/syscall/unix > time > internal/syscall/execenv > regexp/syntax > github.com/shiena/ansicolor > encoding/binary > internal/fmtsort > github.com/mitchellh/go-wordwrap > io/fs > internal/poll > crypto/cipher > context > crypto/sha1 > regexp > golang.org/x/sys/unix > crypto/aes > os > crypto/des > github.com/hlandau/goutils/text > crypto/elliptic/internal/fiat > crypto/internal/randutil > crypto/sha512 > crypto/ed25519/internal/edwards25519/field > fmt > io/ioutil > net > path/filepath > math/big > encoding/hex > os/exec > os/user > log > github.com/coreos/go-systemd/unit > github.com/hlandau/goutils/os > github.com/mattn/go-isatty > github.com/hlandau/xlog > crypto/rand > github.com/hlandau/acmetool/hooks > github.com/mattn/go-runewidth > os/signal > gopkg.in/hlandau/svcutils.v1/chroot > gopkg.in/hlandau/svcutils.v1/passwd > gopkg.in/cheggaaa/pb.v1 > github.com/hlandau/acmetool/interaction > crypto/elliptic > encoding/asn1 > crypto/ed25519/internal/edwards25519 > vendor/golang.org/x/crypto/cryptobyte > crypto/ed25519 > crypto/hmac > crypto/md5 > crypto/rc4 > crypto/rsa > crypto/ecdsa > crypto/sha256 > crypto/dsa > crypto/x509/pkix > encoding/base64 > net/url > vendor/golang.org/x/crypto/chacha20 > encoding/pem > vendor/golang.org/x/crypto/poly1305 > vendor/golang.org/x/sys/cpu > vendor/golang.org/x/crypto/curve25519 > vendor/golang.org/x/crypto/hkdf > vendor/golang.org/x/crypto/chacha20poly1305 > crypto/x509 > github.com/godbus/dbus > compress/flate > hash/crc32 > vendor/golang.org/x/text/transform > compress/gzip > vendor/golang.org/x/text/unicode/bidi > vendor/golang.org/x/text/unicode/norm > crypto/tls > vendor/golang.org/x/text/secure/bidirule > net/textproto > vendor/golang.org/x/net/http2/hpack > vendor/golang.org/x/net/idna > mime > github.com/coreos/go-systemd/dbus > vendor/golang.org/x/net/http/httpguts > vendor/golang.org/x/net/http/httpproxy > mime/quotedprintable > mime/multipart > net/http/internal > net/http/internal/ascii > html > encoding/json > golang.org/x/text/transform > golang.org/x/text/unicode
Bug#1030568: marked as done (src:cross-toolchain-base-mipsen: fails to migrate to testing for too long: unsatisfiable Build-Depends)
Your message dated Mon, 06 Feb 2023 07:04:22 + with message-id and subject line Bug#1030568: fixed in cross-toolchain-base-mipsen 24 has caused the Debian Bug report #1030568, regarding src:cross-toolchain-base-mipsen: fails to migrate to testing for too long: unsatisfiable Build-Depends 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.) -- 1030568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cross-toolchain-base-mipsen Version: 21 Severity: serious Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s) and mips* porter(s), Please consider this an official warning for the mipsel and mips64el ports. Several key packages that are specific for mips* are behind in testing for way too long (bug #1023706, #1026129, #1026128) and so far I've only seen action after reminders. 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:cross-toolchain-base-mipsen has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package has a Build-Depends on linux-source-6.0 but that's no longer the linux version in testing. 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. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=cross-toolchain-base-mipsen OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: cross-toolchain-base-mipsen Source-Version: 24 Done: YunQiang Su We believe that the bug you reported is fixed in the latest version of cross-toolchain-base-mipsen, 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 1030...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. YunQiang Su (supplier of updated cross-toolchain-base-mipsen 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: Mon, 06 Feb 2023 14:45:10 +0800 Source: cross-toolchain-base-mipsen Architecture: source Version: 24 Distribution: unstable Urgency: medium Maintainer: Cross Toolchain Base Team Changed-By: YunQiang Su Closes: 1030568 Changes: cross-toolchain-base-mipsen (24) unstable; urgency=medium . * Rebase cross-toolchain-base 66 - Build using glibc 2.36-8. - Build using binutils 2.40-2. - Build using linux 6.1.4. - Build using gcc 12.2.0-14. * Build-Dep on linux-source metapackage. (Closes: #1030568) Checksums-Sha1: 8278e875bba01e111334e0ee82185ecf04759677 11182 cross-toolchain-base-mipsen_24.dsc e19057923925753fa781908c7443eee54819089f 42592 cross-toolchain-base-mipsen_24.tar.xz c8cc6f6a0665bbe22b974d238b43af804f258e6f 9076 cross-toolchain-base-mipsen_24_source.buildinfo Checksums-Sha256: 000f548b6ae0365b7b915c5e089e4bd0c5009b61c1d4bf5ccb82ab368c40470e 11182 cross-toolchain-base-mipsen_24.dsc 3969305e5275f0496ac9428a20353e5cf9aecc94c67c3520f83f3b639de35ad5 42592 cross-toolchain-base-mipsen_24.tar.xz 740de2c434531e8a07a98890c85ddf2b816a5b463162c80de2eb9190d496b872 9076 cross-toolchain-base-mipsen_24_source.buildinfo Files: 9d2dad07c5ea95162b951533e69a1173 11182 devel optional cross-toolchain-base-mipsen_24.dsc dcd096531280c1514e64209e3842a310 42592 devel optional cross-toolchain-base-mipsen_24.tar.xz fde3ade98a89baf064f21539fd805db2 9076 devel optional cross-toolchain-base-mipsen_24_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEEzJPpNyx4YT9lsL4DQafa2Aqh014FAmPgoyEPHHN5cUBkZWJp YW4ub3JnAAoJEEGn2tgKodNeT5sP/3mnVtz0/czKxv/wFV9Nzgf6chfqUvtsAC2i otwF1RxwRQh/2/L+i+PQFDBJF87g5Pwg
Processed: notfound 1030545 in 1:7.2+dfsg-1+b1
Processing commands for cont...@bugs.debian.org: > notfound 1030545 1:7.2+dfsg-1+b1 Bug #1030545 [src:qemu] qemu: qemu-img and qemu-system-s390x hang on s390x The source 'qemu' and version '1:7.2+dfsg-1+b1' do not appear to match any binary packages No longer marked as found in versions qemu/1:7.2+dfsg-1+b1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1030545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997130: marked as pending in acmetool
Control: tag -1 pending Hello, Bug #997130 in acmetool reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/acmetool/-/commit/51cb87026ab18000d161b359efce35eb59083e5c Fix FTBFS due to signature verification error Closes: #997130 (this message was generated automatically) -- Greetings https://bugs.debian.org/997130
Processed: Bug#997130 marked as pending in acmetool
Processing control commands: > tag -1 pending Bug #997130 [src:acmetool] acmetool: FTBFS: util_test.go:24: error: x509: signature over certificate returned by signer is invalid: crypto/rsa: verification error Added tag(s) pending. -- 997130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997130 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030568: src:cross-toolchain-base-mipsen: fails to migrate to testing for too long: unsatisfiable Build-Depends
Paul Gevers 于2023年2月5日周日 15:03写道： > > Source: cross-toolchain-base-mipsen > Version: 21 > Severity: serious > Tags: sid bookworm > User: release.debian@packages.debian.org > Usertags: out-of-sync > > Dear maintainer(s) and mips* porter(s), > > Please consider this an official warning for the mipsel and mips64el > ports. Several key packages that are specific for mips* are behind in > testing for way too long (bug #1023706, #1026129, #1026128) and so far > I've only seen action after reminders. > > 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:cross-toolchain-base-mipsen has been > trying to migrate for 61 days [2]. Hence, I am filing this bug. Your > package has a Build-Depends on linux-source-6.0 but that's no longer the > linux version in testing. > > 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. > Sorry for the delay. I will do so in future. And I will set up an CI to do so. > Paul > > [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html > [2] https://qa.debian.org/excuses.php?package=cross-toolchain-base-mipsen -- YunQiang Su
Processed: retitle 1030653 to pyemd: missing dependency on numpy
Processing commands for cont...@bugs.debian.org: > retitle 1030653 pyemd: missing dependency on numpy Bug #1030653 [src:pyemd] pyemd: autopkgtest regression Changed Bug title to 'pyemd: missing dependency on numpy' from 'pyemd: autopkgtest regression'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1030653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030653 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030653: pyemd: autopkgtest regression
Source: pyemd Version: 0.5.1.54.g802fa86-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer The autopkgtests of pyemd 0.5.1.54.g802fa86-1 are failing in testing [1] and unstable [2]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/p/pyemd/testing/amd64/ [2] https://ci.debian.net/packages/p/pyemd/unstable/amd64/ ERRORS [31m [1m_ ERROR collecting test/test_pyemd.py __ [0m [1m [31mtest/test_pyemd.py [0m:6: in import numpy as np [1m [31mE ModuleNotFoundError: No module named 'numpy' [0m [31m [1m_ ERROR collecting test/test_pyemd.py __ [0m [31mImportError while importing test module '/tmp/autopkgtest-lxc.u3ik84nf/downtmp/build.TqX/src/test/test_pyemd.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3/dist-packages/_pytest/python.py:618: in _importtestmodule mod = import_path(self.path, mode=importmode, root=self.config.rootpath) /usr/lib/python3/dist-packages/_pytest/pathlib.py:533: in import_path importlib.import_module(module_name) /usr/lib/python3.11/importlib/__init__.py:126: in import_module return _bootstrap._gcd_import(name[level:], package, level) :1206: in _gcd_import ??? :1178: in _find_and_load ??? :1149: in _find_and_load_unlocked ??? :690: in _load_unlocked ??? /usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:168: in exec_module exec(co, module.__dict__) test/test_pyemd.py:6: in import numpy as np E ModuleNotFoundError: No module named 'numpy' [0m
Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)
Control: retitle -1 mariadb: FTBFS on s390x: crash on munmap(), free(), aligned_free() For the record, the latest build https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=s390x&ver=1%3A10.11.1-3&stamp=1675662468&raw=0 shows other test failures again, but the stack trace seem to have munmap(), free(), aligned_free() etc in common: main.bootstrap_innodb 'innodb' w2 [ fail ] Found warnings/errors in server log file! Test ended at 2023-02-06 05:41:47 line Attempting backtrace. You can use the following information to find out ^ Found warnings in /<>/builddir/mysql-test/var/2/log/mysqld.1.err ok - found 'core' (0/5) Core generated by '/<>/builddir/sql/mariadbd' Output from gdb follows. The first stack trace is from the failing thread. The following stack traces are from all threads (so the failing one is duplicated). -- [New LWP 2264728] [New LWP 2264825] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/s390x-linux-gnu/libthread_db.so.1". Core was generated by `/<>/builddir/sql/mariadbd --defaults-group-su'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x03ffb4448992 in kill () from /lib/s390x-linux-gnu/libc.so.6 [Current thread is 1 (Thread 0x3ffb536a820 (LWP 2264728))] #0 0x03ffb4448992 in kill () from /lib/s390x-linux-gnu/libc.so.6 #1 0x02aa06f107c4 in handle_fatal_signal (sig=) at ./sql/signal_handler.cc:367 #2 #3 0x02aa073fc26a in my_read (Filedes=, Buffer=0xd , Count=4096, MyFlags=) at ./mysys/my_read.c:63 #4 0x02aa06f10266 in output_core_info () at ./sql/signal_handler.cc:90 #5 0x02aa06f10792 in handle_fatal_signal (sig=) at ./sql/signal_handler.cc:351 #6 #7 0x03ffb450e632 in munmap () from /lib/s390x-linux-gnu/libc.so.6 #8 0x03ffb44a7790 in free () from /lib/s390x-linux-gnu/libc.so.6 #9 0x02aa07140022 in aligned_free (ptr=) at ./include/aligned.h:37 #10 pfs_free (ptr=, size=0, klass=0x2aa086c6900 ) at ./storage/perfschema/pfs_global.cc:83 #11 pfs_free (ptr=, size=0, klass=0x2aa086c6900 ) at ./storage/perfschema/pfs_global.cc:78 #12 pfs_free_array (klass=0x2aa086c6900 , n=n@entry=256, size=size@entry=32, ptr=) at ./storage/perfschema/pfs_global.cc:134 #13 0x02aa07135e82 in PFS_thread_allocator::free_array (this=, array=array@entry=0x2aa08f4fd30) at ./storage/perfschema/pfs_buffer_container.cc:659 #14 0x02aa071425da in PFS_buffer_scalable_container::cleanup (this=) at ./storage/perfschema/pfs_buffer_container.h:506 #15 PFS_buffer_scalable_container::cleanup (this=) at ./storage/perfschema/pfs_buffer_container.h:491 #16 cleanup_instruments () at ./storage/perfschema/pfs_instr.cc:233 #17 0x02aa0715000c in cleanup_performance_schema () at ./storage/perfschema/pfs_server.cc:296 #18 0x02aa071504f0 in shutdown_performance_schema () at ./storage/perfschema/pfs_server.cc:326 #19 0x02aa06bbf912 in mysqld_exit (exit_code=exit_code@entry=0) at ./sql/mysqld.cc:1943 #20 0x02aa06bca4fe in mysqld_main (argc=, argv=) at ./sql/mysqld.cc:6040 #21 0x03ffb442b84a in ?? () from /lib/s390x-linux-gnu/libc.so.6 #22 0x03ffb442b932 in __libc_start_main () from /lib/s390x-linux-gnu/libc.so.6 #23 0x02aa06bbd378 in _start () main.host_cache_size_functionality 'innodb' w2 [ fail ] Found warnings/errors in server log file! Test ended at 2023-02-06 05:44:47 line Attempting backtrace. You can use the following information to find out ^ Found warnings in /<>/builddir/mysql-test/var/2/log/mysqld.1.err ok - found 'core' (2/5) Core generated by '/<>/builddir/sql/mariadbd' Output from gdb follows. The first stack trace is from the failing thread. The following stack traces are from all threads (so the failing one is duplicated). -- [New LWP 2267523] [New LWP 2268734] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/s390x-linux-gnu/libthread_db.so.1". Core was generated by `/<>/builddir/sql/mariadbd --defaults-group-su'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x03ffa7e48992 in kill () from /lib/s390x-linux-gnu/libc.so.6 [Current thread is 1 (Thread 0x3ffa8d6a820 (LWP 2267523))] #0 0x03ffa7e48992 in kill () from /lib/s390x-linux-gnu/libc.so.6 #1 0x02aa0f2907c4 in handle_fatal_signal (sig=) at ./sql/signal_handler.cc:367 #2 #3 0x02aa0f77c26a in my_read (Filedes=, Buffer=0xd , Count=4096, MyFlags=) at ./mysys/my_read.c:63 #4 0x02aa0f290266 in output_core_info () at ./sql/signal_handler.cc:90 #5 0x02aa0f290792 in handle_fatal_signal (sig=) at ./sql/signal_handler.cc:351 #6 #7 0x03ffa7f0e632 in munmap () from /lib/s390x-linux-gnu/libc.so.6 #8 0x03ffa7ea7790 in free () from /lib/s390x-linux-gnu/libc.so.6 #9 0x02aa0f4c0022 in aligned_free (ptr=) at ./include/aligned.h:37 #10 pfs_free (ptr=, size=2841600, klass=0x2aa10a46700 ) at ./storage/perfschema/pfs_global.cc:83 #11 pfs_free (ptr=, size=2841600, klass=0x2aa10a4670
Processed: Re: Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)
Processing control commands: > retitle -1 mariadb: FTBFS on s390x: crash on munmap(), Bug #1030510 [src:mariadb] mariadb: FTBFS on s390x: crash on test main.plugin_auth 'innodb' Changed Bug title to 'mariadb: FTBFS on s390x: crash on munmap(),' from 'mariadb: FTBFS on s390x: crash on test main.plugin_auth 'innodb''. -- 1030510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 935209
Processing commands for cont...@bugs.debian.org: > close 935209 0.5.4-1 Bug #935209 [src:servefile] servefile: Please port to Python 3 and/or drop Python 2 package Bug #966793 [src:servefile] servefile: Unversioned Python removal in sid/bullseye Marked as fixed in versions servefile/0.5.4-1. Marked as fixed in versions servefile/0.5.4-1. Bug #935209 [src:servefile] servefile: Please port to Python 3 and/or drop Python 2 package Bug #966793 [src:servefile] servefile: Unversioned Python removal in sid/bullseye Marked Bug as done Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 935209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935209 966793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966793 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unarchiving 935209, reopening 935209
Processing commands for cont...@bugs.debian.org:
> # src:servefile was reintroduced:
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 935209
Bug #935209 {Done: Debian FTP Masters }
[src:servefile] servefile: Please port to Python 3 and/or drop Python 2 package
Bug #966793 {Done: Debian FTP Masters }
[src:servefile] servefile: Unversioned Python removal in sid/bullseye
Unarchived Bug 935209
Unarchived Bug 966793
> reopen 935209
Bug #935209 {Done: Debian FTP Masters }
[src:servefile] servefile: Please port to Python 3 and/or drop Python 2 package
Bug #966793 {Done: Debian FTP Masters }
[src:servefile] servefile: Unversioned Python removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.4.4-1+rm.
No longer marked as fixed in versions 0.4.4-1+rm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
935209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935209
966793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1030604: mariadb breaks mariadb-10.6 autopkgtest: Variable 'innodb_compression_algorithm' can't be set to the value of 'lz4'
Hi! The error message "Variable 'innodb_compression_algorithm' can't be set to the value of 'lz4'" is from the first test, and it fails. Actually all tests fail because in MariaDB 10.11 the compression methods are packaged in separate packages. The root cause here is that the test in 10.6 depends on simply 'mariadb-server'. With a new 'mariadb-server' from 10.11 the test of 10.6 will fail. The test would not fail if the autopkgtests originally had a dependency on 'mariadb-server-10.6'. It does not seem worth the effort to upload a new src:mariadb-10.6 just to fix this. It is a pure test issue and not a symptom of a real failure. Can we have a temporary override to shut down the src:mariadb-10.6 autopkgtests in Debian CI so that 10.11 can enter Debian testing/Bookworm and I can then file request to remove src:mariadb-10.6 from testing and unstable?
Bug#1030622: tex-common package post-installation script subprocess returned error exit status 1
Hello, Le 05/02/2023 à 20:52, Hilmar Preuße a écrit : Today the new texlive-base & texlive-extra did migrate to testing and hence were upgraded on your system. The texlive-lang did not migrate yet, this will happen soon. Once texlive-lang-japanese is upgraded, please repeat the test. Is suspect an incompatibility in these packages, as I'm not able to reproduce the issue using unstable. Then, a dependency (Breaks and/or Conflicts) is missing somewhere... I just upgraded texlive-lang-* and indeed the problem seems to have disappeared. Cheers, -- Stéphane
Bug#1026962: openjfx: tries to build with -j64 on a host with 2 processors
On Sun, Feb 05, 2023 at 08:14:31PM +, James Addison wrote: > Source: openjfx > Followup-For: Bug #1026962 > > Could the following build-related scripting be something to do with it? > > - > https://salsa.debian.org/java-team/openjfx/-/blob/debian/11.0.11+1-1.1/modules/javafx.web/src/main/native/Tools/Scripts/webkitdirs.pm#L494-499 I don't think it's this one, because nproc returns the right value on a s390x porterbox, as does /proc/cpuinfo. > - > https://salsa.debian.org/java-team/openjfx/-/blob/debian/11.0.11+1-1.1/modules/javafx.web/src/main/native/Tools/Scripts/build-webkit#L300-305 YES! > (perhaps something about the way that numberOfCPUs is being evaluated on s390x > hosts isn't matching the expectations of the build script) I will try another build on the porterbox defining NUMBER_OF_PROCESSORS. Thank you for this pointer. signature.asc Description: PGP signature
Bug#1017299: marked as done (golang-gopkg-hlandau-service.v2: FTBFS: cannot find package "github.com/erikdubbelboer/gspt")
Your message dated Mon, 06 Feb 2023 04:34:16 + with message-id and subject line Bug#1017299: fixed in golang-gopkg-hlandau-service.v2 2.0.17-1 has caused the Debian Bug report #1017299, regarding golang-gopkg-hlandau-service.v2: FTBFS: cannot find package "github.com/erikdubbelboer/gspt" 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.) -- 1017299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-gopkg-hlandau-service.v2 Version: 2.0.16-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=golang --with=golang >dh_update_autotools_config -O--buildsystem=golang >dh_autoreconf -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang >dh_auto_build -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 > gopkg.in/hlandau/service.v2 gopkg.in/hlandau/service.v2/daemon > gopkg.in/hlandau/service.v2/daemon/bansuid > gopkg.in/hlandau/service.v2/gsptcall > src/gopkg.in/hlandau/service.v2/gsptcall/gsptcall-cgo.go:5:8: cannot find > package "github.com/erikdubbelboer/gspt" in any of: > /usr/lib/go-1.19/src/github.com/erikdubbelboer/gspt (from $GOROOT) > > /<>/obj-x86_64-linux-gnu/src/github.com/erikdubbelboer/gspt > (from $GOPATH) > dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 > gopkg.in/hlandau/service.v2 gopkg.in/hlandau/service.v2/daemon > gopkg.in/hlandau/service.v2/daemon/bansuid > gopkg.in/hlandau/service.v2/gsptcall returned exit code 1 > make: *** [debian/rules:4: build] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/08/13/golang-gopkg-hlandau-service.v2_2.0.16-4_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220813&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: golang-gopkg-hlandau-service.v2 Source-Version: 2.0.17-1 Done: Peter Colberg We believe that the bug you reported is fixed in the latest version of golang-gopkg-hlandau-service.v2, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Colberg (supplier of updated golang-gopkg-hlandau-service.v2 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: Sun, 05 Feb 2023 23:04:10 -0500 Source: golang-gopkg-hlandau-service.v2 Architecture: source Version: 2.0.17-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Peter Colberg Closes: 1017299 Changes: golang-gopkg-hlandau-service.v2 (2.0.17-1) unstable; urgency=medium . [ Debian Janitor ] * Bump debhelper from old 11 to 12. * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Remove constraints unnecessary since buster . [ Peter Colberg ] * New upstream version 2.0.17 * Fix FTBFS due to case-sensitive import path. Thanks to Arun Kumar Pariyar (Closes: #1017299) * Bump debhelper compat level to 13 * Set Section to golang * Set Rules-Requires-Root to no * Drop unneeded shlibs fro
Bug#919348: xfce4-screensaver: Accidental upload to unstable while fixing bug #919151
Could this bug be closed and allow xfce4-screensaver to flow to testing/stable? I know there are concerns about the stability but the 4.16 release has been out for 2 years. And as far as I know light-locker is still recommended over xfce4-screensaver so this package would not be a default for everybody. But closing this bug would allow for those of us who wish to use the package to do so without resorting to more complicated means of doing so. Please consider closing the bug. Thank you.
Bug#1030466: marked as done (datalad-container: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_install] Error 2)
Your message dated Mon, 06 Feb 2023 03:19:22 + with message-id and subject line Bug#1030466: fixed in datalad-container 1.1.9-1 has caused the Debian Bug report #1030466, regarding datalad-container: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_install] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1030466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030466 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: datalad-container Version: 1.1.7-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230203 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 '/<>' > py3versions: no X-Python3-Version in control file, using supported versions > dh_auto_install > I: pybuild base:240: /usr/bin/python3 setup.py install --root > /<>/debian/datalad-container > running install > /usr/lib/python3/dist-packages/setuptools/command/install.py:34: > SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and > pip and other standards-based tools. > warnings.warn( > running build > running build_py > running egg_info > writing datalad_container.egg-info/PKG-INFO > writing dependency_links to datalad_container.egg-info/dependency_links.txt > writing entry points to datalad_container.egg-info/entry_points.txt > writing requirements to datalad_container.egg-info/requires.txt > writing top-level names to datalad_container.egg-info/top_level.txt > reading manifest file 'datalad_container.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no files found matching 'LICENSE' > no previously-included directories found matching 'docs/build' > adding license file 'COPYING' > writing manifest file 'datalad_container.egg-info/SOURCES.txt' > UPDATING > /<>/.pybuild/cpython3_3.11_datalad-container/build/datalad_container/_version.py > set > /<>/.pybuild/cpython3_3.11_datalad-container/build/datalad_container/_version.py > to '1.1.7' > running install_lib > creating /<>/debian/datalad-container/usr > creating /<>/debian/datalad-container/usr/lib > creating /<>/debian/datalad-container/usr/lib/python3.11 > creating > /<>/debian/datalad-container/usr/lib/python3.11/dist-packages > creating > /<>/debian/datalad-container/usr/lib/python3.11/dist-packages/datalad_container > copying > /<>/.pybuild/cpython3_3.11_datalad-container/build/datalad_container/__init__.py > -> > /<>/debian/datalad-container/usr/lib/python3.11/dist-packages/datalad_container > creating > /<>/debian/datalad-container/usr/lib/python3.11/dist-packages/datalad_container/adapters > copying > /<>/.pybuild/cpython3_3.11_datalad-container/build/datalad_container/adapters/__init__.py > -> > /<>/debian/datalad-container/usr/lib/python3.11/dist-packages/datalad_container/adapters > copying > /<>/.pybuild/cpython3_3.11_datalad-container/build/datalad_container/adapters/docker.py > -> > /<>/debian/datalad-container/usr/lib/python3.11/dist-packages/datalad_container/adapters > creating > /<>/debian/datalad-container/usr/lib/python3.11/dist-packages/datalad_container/adapters/tests > copying > /<>/.pybuild/cpython3_3.11_datalad-container/build/datalad_container/adapters/tests/__init__.py > -> > /<>/debian/datalad-container/usr/lib/python3.11/dist-packages/datalad_container/adapters/tests > copying > /<>/.pybuild/cpython3_3.11_datalad-container/build/datalad_container/adapters/tests/test_docker.py > -> > /<>/debian/datalad-container/usr/lib/python3.11/dist-packages/datalad_container/adapters/tests > copying > /<>/.pybuild/cpython3_3.11_datalad-container/build/datalad_container/definitions.py > -> > /<>/debian/datalad-container/usr/lib/python3.11/dist-packages/datalad_container > copying > /<>/.pybuild/cpython3_3.11_datalad-container/build/datalad_container/containers_add.py > -> > /<>/debian/datalad-container/usr/lib/python3.11/dist-packages/datalad_container > copying > /<>/.pybuild/cpython3_3.11_datalad-container/build/datalad_container/find_container.py > -> > /<>/debian/datalad-container/usr/lib/python3.11/dist-packages/datalad_container > copying > /<>/.pybuild/cpython3_3.11_datalad-container/build/datalad_container/containers_remove.py > -> > /<>/debian/datalad-container/usr/lib/python3.11/dist-packages/datalad_container > copying > /<>/.pybuild/cpython3_3.11_datalad-container/build/datalad_container/containers_run.py > -> > /<>/debian/datalad-container/usr/lib/python3.11/dist-packages/d
Bug#1029594: Fails to authenticate mit o365
Hi Carsten, 1) Did you use Thunderbird's Release Candidate Build 1 instead of Release Candidate Build 2 for the Debian 102.7.1 release [1]? It appears you uploaded the Debian package on the "2023-01-24" [2]. Build 2 was only released on the 31st of January. $ diff -rq build1/thunderbird-102.7.1/comm/mailnews/base/src/ debian/thunderbird-102.7.1/comm/mailnews/base/src/ $ diff -rq build2/thunderbird-102.7.1/comm/mailnews/base/src/ debian/thunderbird-102.7.1/comm/mailnews/base/src/ Files build2/thunderbird-102.7.1/comm/mailnews/base/src/OAuth2.jsm and debian/thunderbird-102.7.1/comm/mailnews/base/src/OAuth2.jsm differ Files build2/thunderbird-102.7.1/comm/mailnews/base/src/OAuth2Providers.jsm and debian/thunderbird-102.7.1/comm/mailnews/base/src/OAuth2Providers.jsm differ 2) The authentication successfully completed with the upstream build of Thunderbird 102.7.1 [3], whereas the authentication was in an infinite loop with the Debian build of Thunderbird 102.7.1. Regards, Harshula [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1814536 [2] https://tracker.debian.org/news/1413005/accepted-thunderbird-110271-1-source-into-unstable/ [3] https://download-origin.cdn.mozilla.net/pub/thunderbird/releases/102.7.1/linux-x86_64/en-US/thunderbird-102.7.1.tar.bz2 https://download-origin.cdn.mozilla.net/pub/thunderbird/candidates/102.7.1-candidates/build1/source/ Filethunderbird-102.7.1.source.tar.xz 477M24-Jan-2023 03:33 Filethunderbird-102.7.1.source.tar.xz.asc 833 24-Jan-2023 03:33 $ sha256sum thunderbird-102.7.1.source.tar.xz 74cbf32140cbbd7954093f7adc1a1d0cf8a9b0f77dfd9d344540a111fed9ac20 thunderbird-102.7.1.source.tar.xz https://download-origin.cdn.mozilla.net/pub/thunderbird/candidates/102.7.1-candidates/build2/source/ Filethunderbird-102.7.1.source.tar.xz 487M31-Jan-2023 15:46 Filethunderbird-102.7.1.source.tar.xz.asc 833 31-Jan-2023 15:46 $ sha256sum thunderbird-102.7.1.source.tar.xz 00c9a215ec99b4ce1683c8581b5bb44759ad31cb1303bdec173c053fcee27c91 thunderbird-102.7.1.source.tar.xz https://download-origin.cdn.mozilla.net/pub/thunderbird/releases/102.7.1/source/ Filethunderbird-102.7.1.source.tar.xz 487M01-Feb-2023 02:10 Filethunderbird-102.7.1.source.tar.xz.asc 833 01-Feb-2023 02:10 $ sha256sum thunderbird-102.7.1.source.tar.xz 00c9a215ec99b4ce1683c8581b5bb44759ad31cb1303bdec173c053fcee27c91 thunderbird-102.7.1.source.tar.xz $ diff -rq build1/thunderbird-102.7.1/ build2/thunderbird-102.7.1 Files build1/thunderbird-102.7.1/comm/chat/protocols/xmpp/xmpp-base.jsm and build2/thunderbird-102.7.1/comm/chat/protocols/xmpp/xmpp-base.jsm differ Files build1/thunderbird-102.7.1/comm/mail/base/content/mailContextMenus.js and build2/thunderbird-102.7.1/comm/mail/base/content/mailContextMenus.js differ Files build1/thunderbird-102.7.1/comm/mail/base/content/utilityOverlay.js and build2/thunderbird-102.7.1/comm/mail/base/content/utilityOverlay.js differ Files build1/thunderbird-102.7.1/comm/mail/components/compose/content/MsgComposeCommands.js and build2/thunderbird-102.7.1/comm/mail/components/compose/content/MsgComposeCommands.js differ Only in build2/thunderbird-102.7.1/comm/mail/components/extensions/test/browser: browser_ext_compose_bug1804796.js Files build1/thunderbird-102.7.1/comm/mail/components/extensions/test/browser/browser.ini and build2/thunderbird-102.7.1/comm/mail/components/extensions/test/browser/browser.ini differ Files build1/thunderbird-102.7.1/comm/mail/themes/windows/mail/mailWindow1.css and build2/thunderbird-102.7.1/comm/mail/themes/windows/mail/mailWindow1.css differ Files build1/thunderbird-102.7.1/comm/mailnews/base/src/OAuth2.jsm and build2/thunderbird-102.7.1/comm/mailnews/base/src/OAuth2.jsm differ Files build1/thunderbird-102.7.1/comm/mailnews/base/src/OAuth2Providers.jsm and build2/thunderbird-102.7.1/comm/mailnews/base/src/OAuth2Providers.jsm differ Files build1/thunderbird-102.7.1/comm/mailnews/compose/src/nsMsgCompose.cpp and build2/thunderbird-102.7.1/comm/mailnews/compose/src/nsMsgCompose.cpp differ Files build1/thunderbird-102.7.1/comm/mailnews/import/modules/AddrBookFileImporter.jsm and build2/thunderbird-102.7.1/comm/mailnews/import/modules/AddrBookFileImporter.jsm differ Files build1/thunderbird-102.7.1/comm/mailnews/import/test/unit/resources/addressbook.json and build2/thunderbird-102.7.1/comm/mailnews/import/test/unit/resources/addressbook.json differ Only in build2/thunderbird-102.7.1/comm/mailnews/import/test/unit/resources: dos_vcard_addressbook.vcf Files build1/thunderbird-102.7.1/comm/mailnews/import/test/unit/test_AddrBookFileImporter.js and build2/thunderbird-102.7.1/comm/mailnews/import/test/unit/test_AddrBookFileImporter.js differ Files build1/thunderbird-102.7.1/sourcestamp.txt and build2/thunderbird-102.7.1/sou
Bug#1030400: marked as done (bidi-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact com.fasterxml.jackson.dataformat:jackson-dataformat-cbor:jar:debian
Your message dated Mon, 06 Feb 2023 02:35:31 + with message-id and subject line Bug#1030400: fixed in bidi-clojure 2.1.6-2 has caused the Debian Bug report #1030400, regarding bidi-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact com.fasterxml.jackson.dataformat:jackson-dataformat-cbor:jar:debian has not been downloaded from it before. 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.) -- 1030400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bidi-clojure Version: 2.1.6-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230203 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 '/<>' > lein test > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact com.fasterxml.jackson.core:jackson-core:jar:debian has not been > downloaded from it before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact com.fasterxml.jackson.core:jackson-core:jar:debian has not been > downloaded from it before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact > com.fasterxml.jackson.dataformat:jackson-dataformat-smile:jar:debian has not > been downloaded from it before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact com.fasterxml.jackson.dataformat:jackson-dataformat-smile:jar:debian > has not been downloaded from it before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact > com.fasterxml.jackson.dataformat:jackson-dataformat-cbor:jar:debian has not > been downloaded from it before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact com.fasterxml.jackson.dataformat:jackson-dataformat-cbor:jar:debian > has not been downloaded from it before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:23: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/02/03/bidi-clojure_2.1.6-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230203;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230203&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: bidi-clojure Source-Version: 2.1.6-2 Done: Jérôme Charaoui We believe that the bug you reported is fixed in the latest version of bidi-clojure, 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 1030...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérôme Charaoui (supplier of updated bidi-clojure 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: Sun, 05 Feb 2023 20:46:04 -0500 Source: bidi-clojure Architecture: source Version: 2.1.6-2 Distribution: unstable Urgency: medium Maintainer: Debian Clojure Maintainers Changed-By: Jérôme Charaoui Closes: 1030400 Changes: bidi-clojure (2.1.6-2) unstable; urgency=medium . [ Louis-Philippe Véronneau ] * d/control: New email for the Clojure Team. . [ Jérôme Charaoui ] * d/control: bump ring-mock build-dep (Closes: #1030400) * d
Processed: severity of 1030590 is serious
Processing commands for cont...@bugs.debian.org: > severity 1030590 serious Bug #1030590 [devscripts] debrelease: doesn't work (related to DEBRELEASE_DEBS_DIR) Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1030590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028163: sshfs-fuse bug
El 5/2/23 a las 21:54, Steven Robbins escribió: the test manifestly runs fine on buildds Actually, that's not really true. The tests do not even *run* on the buildds, because they are skipped. Take this one for example: https://buildd.debian.org/status/fetch.php?pkg=sshfs-fuse&arch=amd64&ver=3.7.3-1&stamp=1670232073&raw=0 test/test_sshfs.py::test_sshfs[True-True-0-False] SKIPPED (FUSE kern...) [ 6%] test/test_sshfs.py::test_sshfs[True-True-0-True] SKIPPED (FUSE kerne...) [ 12%] test/test_sshfs.py::test_sshfs[True-True-1-False] SKIPPED (FUSE kern...) [ 18%] test/test_sshfs.py::test_sshfs[True-True-1-True] SKIPPED (FUSE kerne...) [ 25%] test/test_sshfs.py::test_sshfs[True-False-0-False] SKIPPED (FUSE ker...) [ 31%] test/test_sshfs.py::test_sshfs[True-False-0-True] SKIPPED (FUSE kern...) [ 37%] test/test_sshfs.py::test_sshfs[True-False-1-False] SKIPPED (FUSE ker...) [ 43%] test/test_sshfs.py::test_sshfs[True-False-1-True] SKIPPED (FUSE kern...) [ 50%] test/test_sshfs.py::test_sshfs[False-True-0-False] SKIPPED (FUSE ker...) [ 56%] test/test_sshfs.py::test_sshfs[False-True-0-True] SKIPPED (FUSE kern...) [ 62%] test/test_sshfs.py::test_sshfs[False-True-1-False] SKIPPED (FUSE ker...) [ 68%] test/test_sshfs.py::test_sshfs[False-True-1-True] SKIPPED (FUSE kern...) [ 75%] test/test_sshfs.py::test_sshfs[False-False-0-False] SKIPPED (FUSE ke...) [ 81%] test/test_sshfs.py::test_sshfs[False-False-0-True] SKIPPED (FUSE ker...) [ 87%] test/test_sshfs.py::test_sshfs[False-False-1-False] SKIPPED (FUSE ke...) [ 93%] test/test_sshfs.py::test_sshfs[False-False-1-True] SKIPPED (FUSE ker...) [100%] and also: SKIPPED [16] test/test_sshfs.py:33: FUSE kernel module does not seem to be loaded Those tests are being skipped in the buildds at least since version 2.10+repack-2. Thanks.
Bug#1029136: marked as done (configuration files not properly migrated on switch to unversioned packages)
Your message dated Mon, 06 Feb 2023 00:54:24 + with message-id and subject line Bug#1029136: fixed in mariadb 1:10.11.1-3 has caused the Debian Bug report #1029136, regarding configuration files not properly migrated on switch to unversioned packages 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.) -- 1029136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mariadb-server Version: 1:10.11.1-1 Severity: serious The latest update switch to unversioned packages. One issue I immediately noticed is that /etc/init.d/mariadb was installed 644, i.e. is not executable. Even, after purging the now obsolete -10.6 packages, I got this: Löschen der Konfigurationsdateien von mariadb-server-10.6 (1:10.6.11-2) ... Löschen der Konfigurationsdateien von mariadb-client-10.6 (1:10.6.11-2) ... [master 28eeae9] committing changes in /etc made by "aptitude" Author: Michael Biebl 12 files changed, 80 deletions(-) delete mode 100644 logcheck/ignore.d.paranoid/mariadb-server-10_6 delete mode 100644 logcheck/ignore.d.server/mariadb-server-10_6 delete mode 100644 logcheck/ignore.d.workstation/mariadb-server-10_6 delete mode 12 rc0.d/K01mariadb delete mode 12 rc1.d/K01mariadb delete mode 12 rc2.d/S01mariadb delete mode 12 rc3.d/S01mariadb delete mode 12 rc4.d/S01mariadb delete mode 12 rc5.d/S01mariadb delete mode 12 rc6.d/K01mariadb delete mode 12 systemd/system/multi-user.target.wants/mariadb.service This is not good. May advice would be to keep (emtpy) transitional packages mariadb-server-10.6/mariadb-client-10.6 and mariadb-server-10.5/mariadb-client-10.5 which itself depend on the unversioned mariadb package. This will not only make the upgrade smoother, it will also ensure that if you purge the empty transitional packages, you do not accidentally remove any import configuration state. Post bookworm you can then safely drop those empty transitional packages. Regards, Michael -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND 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 Versions of packages mariadb-server depends on: ii adduser3.130 ii debconf [debconf-2.0] 1.5.82 ii galera-4 26.4.11-1+b2 ii gawk 1:5.1.0-1 ii iproute2 6.1.0-1 ii libc6 2.36-8 ii libdbi-perl1.643-4 ii libpam0g 1.5.2-6 ii libssl33.0.7-1 ii libstdc++6 12.2.0-14 ii lsb-base 11.5 ii lsof 4.95.0-1 ii mariadb-client 1:10.11.1-1 ii mariadb-common 1:10.11.1-1 ii mariadb-server-core1:10.11.1-1 ii passwd 1:4.13+dfsg1-1 ii perl 5.36.0-7 ii procps 2:4.0.2-3 ii psmisc 23.6-1 ii rsync 3.2.7-1 ii socat 1.7.4.4-2 ii sysvinit-utils [lsb-base] 3.06-2 ii zlib1g 1:1.2.13.dfsg-1 Versions of packages mariadb-server recommends: ii libhtml-template-perl 2.97-2 ii pv 1.6.20-1 Versions of packages mariadb-server suggests: ii bsd-mailx [mailx] 8.1.2-0.20220412cvs-1 pn mariadb-test ii netcat-openbsd 1.219-1 -- Configuration Files: /etc/logcheck/ignore.d.paranoid/mariadb-server [Errno 13] Keine Berechtigung: '/etc/logcheck/ignore.d.paranoid/mariadb-server' /etc/logcheck/ignore.d.server/mariadb-server [Errno 13] Keine Berechtigung: '/etc/logcheck/ignore.d.server/mariadb-server' -- debconf information excluded --- End Message --- --- Begin Message --- Source: mariadb Source-Version: 1:10.11.1-3 Done: Otto Kekäläinen We believe that the bug you reported is fixed in the latest version of mariadb, 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 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maint
Bug#1026509: marked as done (openjpa: FTBFS: [exec] Execute failed: java.io.IOException: Cannot run program "svn" (in directory "/<>/openjpa-lib"): error=2, No such file or directory
Your message dated Mon, 06 Feb 2023 00:55:15 + with message-id and subject line Bug#1012101: fixed in openjpa 2.4.2-8 has caused the Debian Bug report #1012101, regarding openjpa: FTBFS: [exec] Execute failed: java.io.IOException: Cannot run program "svn" (in directory "/<>/openjpa-lib"): error=2, No such file or directory 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.) -- 1012101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openjpa Version: 2.4.2-7 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > mh_patchpoms -plibopenjpa-java --debian-build --keep-pom-version > --maven-repo=/<>/debian/maven-repo >dh_auto_build > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > [0m[0m[INFO] Scanning for projects... > [INFO] > > [INFO] Reactor Build Order: > [INFO] > [INFO] OpenJPA Parent POM > [pom] > [INFO] OpenJPA Utilities Library > [jar] > [INFO] OpenJPA Kernel > [jar] > [INFO] OpenJPA JDBC > [jar] > [INFO] OpenJPA Persistence > [jar] > [INFO] OpenJPA Persistence JDBC > [jar] > [INFO] OpenJPA XML Store > [jar] > [INFO] OpenJPA Slice > [jar] > [INFO] OpenJPA JEST > [jar] > [INFO] OpenJPA Aggregate Jar > [bundle] > [INFO] > [INFO] -< org.apache.openjpa:openjpa-parent > >-- > [INFO] Building OpenJPA Parent POM 2.4.2 > [1/10] > [INFO] [ pom > ]- > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:testCompile (test-source-compile) @ > openjpa-parent --- > [INFO] Not compiling test sources > [INFO] > [INFO] ---< org.apache.openjpa:openjpa-lib > >--- > [INFO] Building OpenJPA Utilities Library 2.4.2 > [2/10] > [INFO] [ jar > ]- > [WARNING] The artifact > org.apache.maven.plugins:maven-resources-plugin:jar:2.6 has been relocated to > org.apache.maven.plugins:maven-resources-plugin:jar:3.3.0 > [INFO] > [INFO] --- maven-resources-plugin:3.3.0:resources (default-resources) @ > openjpa-lib --- > [INFO] Copying 9 resources > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ > openjpa-lib --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 159 source files to > /<>/openjpa-lib/target/classes > [INFO] > /<>/openjpa-lib/src/main/java/org/apache/openjpa/lib/rop/SoftRandomAccessResultList.java: > Some input files use or override a deprecated API. > [INFO] > /<>/openjpa-lib/src/main/java/org/apache/openjpa/lib/rop/SoftRandomAccessResultList.java: > Recompile with -Xlint:deprecation for details. > [INFO] > /<>/openjpa-lib/src/main/java/org/apache/openjpa/lib/meta/XMLMetaDataParser.java: > Some input files use unchecked or unsafe operations. > [INFO] > /<>/openjpa-lib/src/main/java/org/apache/openjpa/lib/meta/XMLMetaDataParser.java: > Recompile with -Xlint:unchecked for details. > [INFO] > [INFO] --- maven-antrun-plugin:1.8:run (set subversion revision) @
Bug#1012101: marked as done (openjpa: FTBFS with OpenJDK 17 due to type inference changes)
Your message dated Mon, 06 Feb 2023 00:55:15 + with message-id and subject line Bug#1012101: fixed in openjpa 2.4.2-8 has caused the Debian Bug report #1012101, regarding openjpa: FTBFS with OpenJDK 17 due to type inference changes 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.) -- 1012101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openjpa Version: 2.4.2-7 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 openjpa fails to build with OpenJDK 17: [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ openjpa-persistence --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 234 source files to /<>/openjpa-persistence/target/classes [INFO] /<>/openjpa-persistence/src/main/java/org/apache/openjpa/persistence/OpenJPAEntityManagerFactorySPI.java: Some input files use or override a deprecated API. [INFO] /<>/openjpa-persistence/src/main/java/org/apache/openjpa/persistence/OpenJPAEntityManagerFactorySPI.java: Recompile with -Xlint:deprecation for details. [INFO] /<>/openjpa-persistence/src/main/java/org/apache/openjpa/persistence/meta/Members.java: Some input files use unchecked or unsafe operations. [INFO] /<>/openjpa-persistence/src/main/java/org/apache/openjpa/persistence/meta/Members.java: Recompile with -Xlint:unchecked for details. [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /<>/openjpa-persistence/src/main/java/org/apache/openjpa/persistence/criteria/SubqueryImpl.java:[213,35] incompatible types: java.util.Set cannot be converted to java.u til.Set> [INFO] 1 error [INFO] - --- End Message --- --- Begin Message --- Source: openjpa Source-Version: 2.4.2-8 Done: Emmanuel Bourg We believe that the bug you reported is fixed in the latest version of openjpa, 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 1012...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated openjpa 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: Mon, 06 Feb 2023 01:29:28 +0100 Source: openjpa Architecture: source Version: 2.4.2-8 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Closes: 1012101 Changes: openjpa (2.4.2-8) unstable; urgency=medium . * Team upload. * Fixed the build failure with Java 17 (Closes: #1012101) * Standards-Version updated to 4.6.2 Checksums-Sha1: 03f150353ab4fde4cabc09c6781fba7389debfbd 2679 openjpa_2.4.2-8.dsc 66182bfa0b271d7f66db6752ac635bf6c5eb4321 13080 openjpa_2.4.2-8.debian.tar.xz 438370cf0a8a5a8d54abe274861813eff81be749 18374 openjpa_2.4.2-8_source.buildinfo Checksums-Sha256: c08f830a4620288838e4cbc322d6332fd0b2bb6050c35b99454ef2ebe39a3c47 2679 openjpa_2.4.2-8.dsc 525784ba3bece76f0437e1e620fe95a5c9d32e90c65b16296cc2c8d1849c64e8 13080 openjpa_2.4.2-8.debian.tar.xz 90f8d69fab3ea6d072db6c435b86665f5e495097b7e08364e0b0a03b23f166e2 18374 openjpa_2.4.2-8_source.buildinfo Files: ad0cba271ac687e8c02bf955ec1ad9f3 2679 java optional openjpa_2.4.2-8.dsc 79a300bb220a27d97f3ba9bf15861a57 13080 java optional openjpa_2.4.2-8.debian.tar.xz 15990239e15f092ce14f04dc106d72da 18374 java optional openjpa_2.4.2-8_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAmPgSgESHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCsbzEP/3IDyFatSbW5ERNO9ufaW0u/WyP7IKl5 yW9A/3HJ072O0FSV2mFIKFAL/dUhtpZsPjwyD1h+QLrNEVk4rtrWj/nDnQaqmmcb x/i0ibsyccyGfqfjP6WuS4nivzfeGuz8q30AbgcC8Cn7l1qaSHGizGEFS48LG43t NtbGHFtIdYiT43UD2I9wvbJCrZDlUzRH8wHeg0gZfBVMcqZTzNXZyZ+bGIO5jGV0 PmBohAAV5oGDUt/2zILHQDhwhIo834g1eeQt0mYipr/ETkGZJxjCE8t77T79KLX7 dZWu3bIqZTxPiExO9no0vtSv1m9jMe716nHIWcnppcciz+y0cSKrOz9Lba2VyuHh f3O7Ur4SNtyDv20MOEcUqrfWTUkaQ/Kqsb0j9d8RGVuTirbdZzIC8Cb+mcWuJKLa Ylxhawhap7GTNyDmGOiG7CZP3VsaX9CovZmle7uZqRRN84jhU
Processed: sshfs-fuse: FTBFS (tries to use the ssh service from the host machine)
Processing commands for cont...@bugs.debian.org: > tags 1028163 + patch Bug #1028163 [src:sshfs-fuse] sshfs-fuse: FTBFS (tries to use the ssh service from the host machine) Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1028163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028163 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028163: sshfs-fuse: FTBFS (tries to use the ssh service from the host machine)
tags 1028163 + patch
thanks
Hi.
I propose that we make the package compliant with Policy 4.2 by disabling
the tests which blindly assume there is a ssh service running in the host
machine.
(Otherwise, what kind of build-depends should be used for that?)
The attached patch works for me.
To do it right without breaking Policy 4.2, the package should maybe
enable its own ssh service on a non-standard port to avoid conflict
with a more than possible standard ssh service in the host machine,
which may or may not be present.
Thanks.--- a/test/test_sshfs.py
+++ b/test/test_sshfs.py
@@ -30,6 +30,7 @@ def name_generator(__ctr=[0]):
__ctr[0] += 1
return 'testfile_%d' % __ctr[0]
+@pytest.mark.skip(reason="packages must not require network access to be
built")
@pytest.mark.parametrize("debug", (False, True))
@pytest.mark.parametrize("cache_timeout", (0,1))
@pytest.mark.parametrize("sync_rd", (True, False))
Processed: forcibly merging 1012101 1026509
Processing commands for cont...@bugs.debian.org: > forcemerge 1012101 1026509 Bug #1012101 [src:openjpa] openjpa: FTBFS with OpenJDK 17 due to type inference changes Bug #1026509 [src:openjpa] openjpa: FTBFS: [exec] Execute failed: java.io.IOException: Cannot run program "svn" (in directory "/<>/openjpa-lib"): error=2, No such file or directory Merged 1012101 1026509 > thanks Stopping processing here. Please contact me if you need assistance. -- 1012101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012101 1026509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029036: marked as done (inventor: includes non-free source)
Your message dated Mon, 06 Feb 2023 00:24:02 + with message-id and subject line Bug#1029036: fixed in inventor 2.1.5-10+dfsg-1 has caused the Debian Bug report #1029036, regarding inventor: includes non-free source to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1029036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: inventor Version: 2.1.5-10-25 Severity: serious Your package cointains stdmacro with the comment: .\"Copyright (c) 1984 AT&T .\" All Rights Reserved .\" THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF AT&T .\" The copyright notice above does not evidence any actual .\" or intended publication of such source code. This file is non-free, so please repack to get rid of it. --- End Message --- --- Begin Message --- Source: inventor Source-Version: 2.1.5-10+dfsg-1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of inventor, 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 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated inventor 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: Mon, 06 Feb 2023 00:50:57 +0100 Source: inventor Architecture: source Version: 2.1.5-10+dfsg-1 Distribution: unstable Urgency: high Maintainer: Debian Science Team Changed-By: Bastian Germann Closes: 1029036 Changes: inventor (2.1.5-10+dfsg-1) unstable; urgency=high . * Team upload * d/copyright: Convert to machine-readable format * Exclude non-free/non-source files (Closes: #1029036) . [ Debian Janitor ] * Update standards version to 4.6.1, no changes needed. * Remove fields on binary packages that duplicate source: + Field Priority from inventor-clients, inventor-data, inventor-demo, inventor-dev, inventor-doc, libinventor1. + Field Section from inventor-dev. * Apply multi-arch hints. + inventor-data, inventor-doc: Add Multi-Arch: foreign. Checksums-Sha1: 9ff1ba8293b934d13c6bdd368439c5d1750c2696 2289 inventor_2.1.5-10+dfsg-1.dsc 3b2d15ab15ef42c03164ccea8fbd454083c86b9b 5131944 inventor_2.1.5-10+dfsg.orig.tar.xz 0337fa291e2716e8a4f12e7f1b7e48ed2791236b 39256 inventor_2.1.5-10+dfsg-1.debian.tar.xz 6a7b10c36f2b86b67847dddb567c313fb6d66e98 8855 inventor_2.1.5-10+dfsg-1_source.buildinfo Checksums-Sha256: b6a2dfbe9a75e7773857d421121c54931ae4d3df63b1854d4f4f34684fd0e53b 2289 inventor_2.1.5-10+dfsg-1.dsc b04cb0937e649c4498667e2052dc1a62ac4a7ed7b23af878b865bb2479a06bb3 5131944 inventor_2.1.5-10+dfsg.orig.tar.xz 8494adb18b21adece83b8c6c31b88f2c2226e8221997a2a6a357433b4d44d8ee 39256 inventor_2.1.5-10+dfsg-1.debian.tar.xz f577a3e8ce8c43e5fbaa8c190e5468f00f813e06ee6d543a567efe335ac4d20a 8855 inventor_2.1.5-10+dfsg-1_source.buildinfo Files: 4a68ae5cb31d24486b97cb67d00a43f7 2289 devel optional inventor_2.1.5-10+dfsg-1.dsc 4d320a11c40d934c8cafe0af91f4d39c 5131944 devel optional inventor_2.1.5-10+dfsg.orig.tar.xz 4eb961335510c3c5ed811fd7916edf3c 39256 devel optional inventor_2.1.5-10+dfsg-1.debian.tar.xz 1aa4d110d7ef9b9b0f20da3ce2ea9725 8855 devel optional inventor_2.1.5-10+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmPgQoMQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFPfpDADSIfzaxE2hJx6guDf5jD1Z6hjOF1gJbw9a 0gTr8UO2ae0R0JsDNlni0IYX817eeB52v1opFFdoIRq3js5PBp4qRH9KzNJW/C8O WTsNIJNu4q9GRaec4wQRl9daUGqmK69bMo3BnBmU26Scb4TfGFpppZJpkULF3C8A PPETDGywoyYQVCAb8MLmPqObpl/KX4DDc9Q13G7NzHY4MzD//CiNQiN4ovb7+4Vw qM/dciB+1Yrp67A5fvUCOzdUtOF6c8xbGasGuSEqMln/TZ5AuxV0oN98xUA+S23G oN6BeZ1QI1szA+m9ovzEhkrET3x2sewYoR6kW0K/F9/4+fzlKJtBn8CeFO4mW4WN lZO1gcm22pbTbdoCHHwiwDDdjw2iYzqR49ew9NSOdb/4sc/AMDaQ6Rw6oyQrn4vE 5wWF2UySZQY4QoN8TT9w3Nn/BCelAYWky1+pt6v1hW9XXKG28A/XD79iHsRDvVZs 0L92/Pr29V8MQvoGA6S9j6NPGjgddRU= =r9xD -END PGP SIGNATURE End Message ---
Bug#1012070: marked as done (simple-xml: FTBFS with OpenJDK 17 due to an illegal reflective access during the tests)
Your message dated Mon, 06 Feb 2023 00:25:12 + with message-id and subject line Bug#1012070: fixed in simple-xml 2.7.1-4 has caused the Debian Bug report #1012070, regarding simple-xml: FTBFS with OpenJDK 17 due to an illegal reflective access during the tests 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.) -- 1012070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: simple-xml Version: 2.7.1-3 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 simple-xml fails to build with OpenJDK 17 due to a test failure. The cause isn't explicit in the log, but the JUnit report (report/TEST-org.simpleframework.xml.core.MixTest.txt) leads to an illegal reflective access: Testsuite: org.simpleframework.xml.core.MixTest Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.067 sec Testcase: testMix took 0.061 sec Caused an ERROR Unable to make field protected int[] java.util.Calendar.fields accessible: module java.base does not "opens java.util" to unnamed module @4cfaf581 java.lang.reflect.InaccessibleObjectException: Unable to make field protected int[] java.util.Calendar.fields accessible: module java.base does not "opens java.util" to unnamed module @4cfaf581 at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354) at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297) at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178) at java.base/java.lang.reflect.Field.setAccessible(Field.java:172) at org.simpleframework.xml.core.FieldScanner.process(FieldScanner.java:247) at org.simpleframework.xml.core.FieldScanner.process(FieldScanner.java:228) at org.simpleframework.xml.core.FieldScanner.extract(FieldScanner.java:161) at org.simpleframework.xml.core.FieldScanner.scan(FieldScanner.java:99) at org.simpleframework.xml.core.FieldScanner.(FieldScanner.java:80) at org.simpleframework.xml.core.DetailExtractor.getFields(DetailExtractor.java:147) at org.simpleframework.xml.core.DetailExtractor.getFields(DetailExtractor.java:130) at org.simpleframework.xml.core.Support.getFields(Support.java:308) at org.simpleframework.xml.core.ObjectScanner.field(ObjectScanner.java:432) at org.simpleframework.xml.core.ObjectScanner.scan(ObjectScanner.java:371) at org.simpleframework.xml.core.ObjectScanner.(ObjectScanner.java:82) at org.simpleframework.xml.core.DefaultScanner.(DefaultScanner.java:64) at org.simpleframework.xml.core.ScannerFactory.getInstance(ScannerFactory.java:84) at org.simpleframework.xml.core.Support.getScanner(Support.java:357) at org.simpleframework.xml.core.Source.getScanner(Source.java:271) at org.simpleframework.xml.core.Source.getDecorator(Source.java:286) at org.simpleframework.xml.core.Composite.writeNamespaces(Composite.java:1272) at org.simpleframework.xml.core.Composite.writeElement(Composite.java:1232) at org.simpleframework.xml.core.Composite.writeUnion(Composite.java:1127) at org.simpleframework.xml.core.Composite.writeElements(Composite.java:1098) at org.simpleframework.xml.core.Composite.writeSection(Composite.java:1004) at org.simpleframework.xml.core.Composite.write(Composite.java:975) at org.simpleframework.xml.core.Composite.write(Composite.java:952) at org.simpleframework.xml.core.Traverser.write(Traverser.java:236) at org.simpleframework.xml.core.Traverser.write(Traverser.java:208) at org.simpleframework.xml.core.Traverser.write(Traverser.java:186) at org.simpleframework.xml.core.Persister.write(Persister.java:1180) at org.simpleframework.xml.core.Persister.write(Persister.java:1162) at org.simpleframework.xml.core.Persister.write(Persister.java:1140) at org.simpleframework.xml.core.Persister.write(Persister.java:1259) at org.simpleframework.xml.core.Persister.write(Persister.java:1241) at org.simpleframework.xml.core.Persister.write(Persister.java:1222) at org.simpleframework.xml.core.MixTest.testMix(MixTest.java:87) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.inter
Processed: severity of 1023021 is important
Processing commands for cont...@bugs.debian.org: > severity 1023021 important Bug #1023021 [src:gitit] gitit: FTBFS on mipsel Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1023021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: cp -a fails to preserve ownership information on 32-bit arches
Processing control commands: > affects -1 + mmdebstrap Bug #1030638 [fakeroot] cp -a fails to preserve ownership information on 32-bit arches Added indication that 1030638 affects mmdebstrap -- 1030638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030638: cp -a fails to preserve ownership information on 32-bit arches
Package: fakeroot Version: 1.30.1-1.1 Severity: grave Control: affects -1 + mmdebstrap Hi, since glibc 2.34 and coreutils 9.1, fakeroot fails to preserve ownership information when running "cp -a" on a file owned by a user other than root. On armel, armhf and i386 (our 32 bit arches), you can reproduce this problem by running inside fakeroot: $ touch foo $ chown 0:42 foo $ ls -lha foo $ cp -a foo bar $ ls -lha bar" which will print this: -rw-r--r-- 1 root shadow 0 Feb 5 23:00 foo -rw-r--r-- 1 root root 0 Feb 5 23:00 bar I submitted an improvement to the `cp-a` test which adds a check for the ownership information in addition to the mode checks as a merge request for that test here: https://salsa.debian.org/clint/fakeroot/-/merge_requests/19 Observe how the salsaci pipeline succeds for amd64 but fails on i386. The reason is that on i386, fakeroot will not retain the ownership information. A quick comparison of the strace output on arm64 (which does not have this problem) and armhf (which does have this problem) shows that arm64 calls fchown() while armhf calls fchown32() which is not wrapped by fakeroot. Maybe that is the problem? This breaks my package mmdebstrap in a similar way as #1023286 did. Since I think that `cp -a` functionality is quite essential, I'm making this bug RC. Feel free to adjust accordingly. Thanks! cheers, josch
Bug#1027540: marked as done (newsboat: FTBFS: src/poddlthread.cpp:63:29: error: ‘CURLOPT_PROGRESSFUNCTION’ is deprecated: since 7.32.0. Use CURLOPT_XFERINFOFUNCTION [-Werror=deprecated-declarations])
Your message dated Sun, 05 Feb 2023 23:34:37 + with message-id and subject line Bug#1027540: fixed in newsboat 2.21-1.5 has caused the Debian Bug report #1027540, regarding newsboat: FTBFS: src/poddlthread.cpp:63:29: error: ‘CURLOPT_PROGRESSFUNCTION’ is deprecated: since 7.32.0. Use CURLOPT_XFERINFOFUNCTION [-Werror=deprecated-declarations] 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.) -- 1027540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: newsboat Version: 2.21-1.4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -std=c++11 -O2 -ggdb -Iinclude -Istfl -Ifilter -I. -Irss -Werror -Wall > -Wextra -Wunreachable-code -DLOCALEDIR=\"/usr/share/locale\" > -I/usr/include/x86_64-linux-gnu -I/usr/include/libxml2 > -I/usr/include/json-c -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o src/poddlthread.o > -c src/poddlthread.cpp >Compiling memchr v2.5.0 > Running `rustc --crate-name build_script_build --edition=2018 > /usr/share/cargo/registry/memchr-2.5.0/build.rs --error-format=json > --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin > --emit=dep-info,link -C embed-bitcode=no -C debug-assertions=off --cfg > 'feature="default"' --cfg 'feature="std"' -C metadata=5269c8e0eb441a04 -C > extra-filename=-5269c8e0eb441a04 --out-dir > /<>/target/release/build/memchr-5269c8e0eb441a04 -L > dependency=/<>/target/release/deps --cap-lints allow` > msgfmt --check --statistics -o po/ca.mo po/ca.po > 289 translated messages, 54 fuzzy translations, 51 untranslated messages. > msgfmt --check --statistics -o po/de.mo po/de.po > 394 translated messages. > msgfmt --check --statistics -o po/es.mo po/es.po > 345 translated messages, 23 fuzzy translations, 26 untranslated messages. > msgfmt --check --statistics -o po/fr.mo po/fr.po > 317 translated messages, 36 fuzzy translations, 41 untranslated messages. > msgfmt --check --statistics -o po/hu.mo po/hu.po > 281 translated messages, 52 fuzzy translations, 61 untranslated messages. > msgfmt --check --statistics -o po/it.mo po/it.po > 339 translated messages, 25 fuzzy translations, 30 untranslated messages. > msgfmt --check --statistics -o po/ja.mo po/ja.po > msgfmt --check --statistics -o po/nb.mo po/nb.po > 65 translated messages, 14 fuzzy translations, 315 untranslated messages. > msgfmt --check --statistics -o po/nl.mo po/nl.po > 289 translated messages, 50 fuzzy translations, 55 untranslated messages. > msgfmt --check --statistics -o po/pl.mo po/pl.po > 394 translated messages. > msgfmt --check --statistics -o po/pt_BR.mo po/pt_BR.po > 317 translated messages, 36 fuzzy translations, 41 untranslated messages. > msgfmt --check --statistics -o po/ru.mo po/ru.po > 394 translated messages. > msgfmt --check --statistics -o po/sk.mo po/sk.po > 394 translated messages. > msgfmt --check --statistics -o po/sv.mo po/sv.po > 316 translated messages, 34 fuzzy translations, 44 untranslated messages. > msgfmt --check --statistics -o po/tr.mo po/tr.po > 325 translated messages, 33 fuzzy translations, 36 untranslated messages. > msgfmt --check --statistics -o po/uk.mo po/uk.po > 394 translated messages. > 394 translated messages. >Compiling cfg-if v1.0.0 >Compiling cc v1.0.73 > Running `rustc --crate-name cfg_if --edition=2018 > /usr/share/cargo/registry/cfg-if-1.0.0/src/lib.rs --error-format=json > --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib > --emit=dep-info,metadata,link -C embed-bitcode=no -C debug-assertions=off -C > metadata=843ddd9d32ebc04b -C extra-filename=-843ddd9d32ebc04b --out-dir > /<>/target/release/deps -L > dependency=/<>/target/release/deps --cap-lints allow` > Running `rustc --crate-name cc --edition=2018 > /usr/share/cargo/registry/cc-1.0.73/src/lib.rs --error-format=json > --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib > --emit=dep-info,metadata,link -C embed-bitcode=no -C debug-assertions=off -C > metadata=feed38afe533cdd8 -C extra-filename=-feed38afe533cdd8 --out-dir > /<>/target/release/deps -L > dependency=/<>/target/release/deps --cap-lints allow` >Compiling autocfg v1.1.0 > Running `rustc --crate-name autocfg > /usr/share/cargo
Bug#1030622: tex-common package post-installation script subprocess returned error exit status 1
On Sun, 05 Feb 2023, Hilmar Preuße wrote:
> (/usr/share/texlive/texmf-dist/tex/platex/base/plcore.ltx
> ! Argument of \platexNILa has an extra }.
>
> \par
> l.52 ...ter\expandafter\expandafter{\platexBANNER}
There was one change concerning platex since the release of the new
latex, I guess that is needed
commit 9016960eb053b949ab2b9c73c31fd8d598fd5f13
Author: Karl Berry
Date: Thu Dec 15 20:43:14 2022 +
platex (15dec22)
git-svn-id: svn://tug.org/texlive/trunk@65278
c570f23f-e606-0410-a88d-b1316a301751
Best
Norbert
--
PREINING Norbert https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#1011172: marked as done (segment: FTBFS with OpenJDK 17: Attempting to assign weaker access privileges to CharSequence.isEmpty())
Your message dated Sun, 05 Feb 2023 23:20:48 + with message-id and subject line Bug#1011172: fixed in segment 1.4.2-2 has caused the Debian Bug report #1011172, regarding segment: FTBFS with OpenJDK 17: Attempting to assign weaker access privileges to CharSequence.isEmpty() 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.) -- 1011172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: segment Version: 1.4.2-1 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 segment fails to build with OpenJDK 17: [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /<>/src/main/java/net/sourceforge/segment/srx/legacy/Buffer.java:[99,25] isEmpty() in net.sourceforge.segment.srx.legacy.Buffer cannot implement isEmpty() in java.lang.CharSequence attempting to assign weaker access privileges; was public [INFO] 1 error [INFO] - --- End Message --- --- Begin Message --- Source: segment Source-Version: 1.4.2-2 Done: Emmanuel Bourg We believe that the bug you reported is fixed in the latest version of segment, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated segment 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: Sun, 05 Feb 2023 23:55:04 +0100 Source: segment Architecture: source Version: 1.4.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Closes: 1011172 Changes: segment (1.4.2-2) unstable; urgency=medium . * Team upload. * Fixed the build failure with Java 17 (Closes: #1011172) * Standards-Version updated to 4.6.2 * Switch to debhelper level 13 Checksums-Sha1: b86855e635df81b08be534fea8e9be837c53ccfd 2023 segment_1.4.2-2.dsc 62a72273e00fe01a68c3936b6043424760166aa1 3644 segment_1.4.2-2.debian.tar.xz c53288331c76a6844cecc2b77976c9d4d62daad0 14883 segment_1.4.2-2_source.buildinfo Checksums-Sha256: 5e9320c9b76d2d20fd342c48c67f02f60318265026b4172845ac11447e93f18e 2023 segment_1.4.2-2.dsc 48f25f1a68a585b2d06bcefbdee1358a2a5dd0e8d5f943079adb8f304e91160d 3644 segment_1.4.2-2.debian.tar.xz 9bc948cd7115ea966eb4b599cb8a20b298ca85b9271e6f6952cb9a0c5d96c2b3 14883 segment_1.4.2-2_source.buildinfo Files: afadbb0be79a09436229fc48efd3ff13 2023 java optional segment_1.4.2-2.dsc 510e719198c9ac63f491f0c42e10ed92 3644 java optional segment_1.4.2-2.debian.tar.xz 0df726eb9e7b5268d198c12a1e865c3a 14883 java optional segment_1.4.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAmPgNDwSHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCs8HYP/iA7s5G514+NCcchZwoHTo9rWMnKV0Mp qUl19j+hjYn/EayWv7tAub2buUszY5DYKeJylo2EIFfjXFTJz4Bt5UiM9rXT60c9 PvjmL0MnxG2BhDWMHxzGcYWBpWcA8otbCBB0p8VpJonFIqgrqNHKqiKc46TxIJDC jInkDRykFrlDJLrRsgyJi2ZLgyDHy4KRll0ByNcrYC+/1neqbktYlF0UBvP3AuI3 a6VB/RHKyM7ftbfRg33ExzUQ2rROZm2fTjrcbTHxD019y7BYxPC6KOp2wcteylfP +14bP4WjKXS3jXaq6XavbfVUZgCOnPle31Gj1Wcz/rW5+3j52TvggTXw1itrxBh6 2YRF/KMLH6LkRwp67LkToVg4zNPmEJMm1ezxkakmFjLdfzYu5AAT7Iw1nlhUEtEk 5bqQa6gu2wINoxr7SWSVkshRAPfu07k+y4pqMkSpS3QW1dt1GUAuYWDy2fO9mkua u/O5oHdMjw8uGlI/tppv6SRC4esF+xs9MyFdfgLnrqXwGpScfjbdXRe1bcfjlxtB XGrJmWv8CfNwwwFAMOnp3qzw08vOmHfR/o46Brh6n2G4XPHbjZZTtk8RqdZ1emsx WwAFoQfJUA94/02IzpI4hYxygP4yim6mApb4yjxNU1LCyEcNg7RtwuSNp4rDRLtK hI3Nom7wkatr =BknM -END PGP SIGNATURE End Message ---
Bug#1028641: marked as done (libquazip1-qt5-dev: Missing dependencies on "qtbase5-dev, zlib1g-dev")
Your message dated Sun, 05 Feb 2023 23:07:44 + with message-id and subject line Bug#1028641: fixed in libquazip1-qt5 1.4-1 has caused the Debian Bug report #1028641, regarding libquazip1-qt5-dev: Missing dependencies on "qtbase5-dev, zlib1g-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.) -- 1028641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028641 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libquazip1-qt5-dev Version: 1.3-1 Severity: serious /usr/lib/x86_64-linux-gnu/cmake/QuaZip-Qt5-1.3/QuaZip-Qt5_SharedTargets.cmake: INTERFACE_LINK_LIBRARIES "Qt5::Core;ZLIB::ZLIB" I am not sure the cmake file should add these to the linker line for rdeps, but if it does then libquazip1-qt5-dev needs dependencies on qtbase5-dev, zlib1g-dev With the missing dependencies added, users like reverse dependencies will no longer have to manually copy such implementation details of libquazip to their own build dependencies. --- End Message --- --- Begin Message --- Source: libquazip1-qt5 Source-Version: 1.4-1 Done: Ben Westover We believe that the bug you reported is fixed in the latest version of libquazip1-qt5, 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 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Westover (supplier of updated libquazip1-qt5 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: Sun, 05 Feb 2023 15:48:12 -0500 Source: libquazip1-qt5 Architecture: source Version: 1.4-1 Distribution: unstable Urgency: high Maintainer: Ben Westover Changed-By: Ben Westover Closes: 1028641 Changes: libquazip1-qt5 (1.4-1) unstable; urgency=high . * New upstream version * Add dependencies on Qt5 and zlib1g (Closes: #1028641) Checksums-Sha1: d423d876dfab4beb5b0a68bda2cefe9dfdc03458 1948 libquazip1-qt5_1.4-1.dsc 9e0869f132c985763f08b9805b6d514917192a31 157819 libquazip1-qt5_1.4.orig.tar.gz 2e6669cc150fd9d1e79ab6b75b079ed98f61cec7 4060 libquazip1-qt5_1.4-1.debian.tar.xz d610bf38a31d507579f786ce1d059d545086151e 8186 libquazip1-qt5_1.4-1_source.buildinfo Checksums-Sha256: 25f007af505ad8d3ff1c7fefbc0ac267ae24a60c30e2ee4ce319e3ec5e486c1f 1948 libquazip1-qt5_1.4-1.dsc 79633fd3a18e2d11a7d5c40c4c79c1786ba0c74b59ad752e8429746fe1781dd6 157819 libquazip1-qt5_1.4.orig.tar.gz 2c6a8f5f3162e6c7f0645c387209a1fd45f9dce1565f95ed978752692fd650ef 4060 libquazip1-qt5_1.4-1.debian.tar.xz d3866cd5ed2e3bb40ead89d665c15d3763f922114e6958581399ab7061b09d33 8186 libquazip1-qt5_1.4-1_source.buildinfo Files: e22fa7fb7e51b4bf49a99e8d150db182 1948 libs optional libquazip1-qt5_1.4-1.dsc f861638a19acaece2aaea11f7ec3b812 157819 libs optional libquazip1-qt5_1.4.orig.tar.gz 91555b3d44d96b43fcdbc18850b4596a 4060 libs optional libquazip1-qt5_1.4-1.debian.tar.xz 1251425ef0a8c982813e8911755ed8ab 8186 libs optional libquazip1-qt5_1.4-1_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmPgNMQQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFCD6DACbKxEETLts5UVpU2sHRy8t8oChiiqxxOEl ++f8kPKxV5+ujNsvZQbl0YJZ62ElO234jHxqPZ5XDAAkzwd6qP/9+tmDniniFDYk GaGpSamJVb+gB8vyfaRyTtVBOBtgg1xPp0NIbjGxxT6p6AFFtafHdWNIwdRS5K7l QXeGV6zvIk9ENZMGOlNKrraW5adqVlX1JyInOcwv1WNIWmEVq/ybCtpEOOSduIsW H0oqHrXSZox7+UAENpwawDAybHl09zsQfGUWWpbaRPtTBBlHtH0RsUSCMDoCofJE zYrvnU3nYsS6Ko8X9zPFEimRZeve3vDIC31tbK7mO/95rOf65cFz+miLm/RX4Xc5 DtRQzd2GGDn0Nlkapz6M2bHqugNchW+q4SfZmGtkMg2IGyV/o3uq6BO5hYuWWckl Ue8PJbDKBb0/t2HgAx587DzXBGM6UeJ21jOQIGmcm7jf7BsQRoPf2cAmcDHDL7Yx p/EztsgUnWlB3JeKAqxkX2qfOuqFfBo= =12WM -END PGP SIGNATURE End Message ---
Bug#1020576: please update sage for pari 2.15.0 and gap 4.12.0
Control: tags -1 patch
Hi,
as Adrian indicated, the setuptools issue is now fixed and the
dt-reorder-cython-setuptools-import.patch is not needed anymore.
However, there are now several unrelated problems causing sagemath to FTBFS.
First of all giac.h can't be compiled, as uchar is not defined.
Workaround: Add '#define uchar u_char' at the beginning of
/usr/include/giac/giac.h.
Then debian/rules needs to be adapted to Python 3.11:
$ sed -i 's/python3.10/python3.11/' debian/rules
Further backporting some patches from upstream (on top of what is currently in
git) is necessary:
# Python 3.11
de38bac21e2 src/sage: Apply python-3.11.patch from
https://github.com/void-linux/void-packages/commit/6229f313450ecae88743b4d5e99da2ed4de44e07
9eb08f3afde inspect.ArgSpec -> inspect.FullArgSpec
8955607c71c dict_del_by_value: move python internal definitions to a separate
file
76040803c8a dict_del_by_value: add internal definitions for python 3.11
014c2ac9a6f deprecated uu -> base64
dc8e155994a sage.misc.fpickle: fix for python 3.11
fd4d6975790 src/sage/misc/fpickle.pyx: Fix docstring markup
8b0dac2322d Fix FullArgSpec usage after 9eb08f3afde3266bbd667e196513240a0fe245f4
db45aebfd6b warnings: ignore deprecation for 'import cgi' in cython
664fc008ed5 warnings: ignore deprecation for 'import sre_constants' in pyparsing
0f63cce4ed1 src/sage/repl/display/formatter.py: Replace use of SAGE_EXTCODE in
doctest by importlib.resources
08e1161c23c warnings: ignore deprecation of importlib.resources.path/read_binary
ed9fe6746f9 remove traces of # py3 and some # py2
44480f4827e doctests: fixes due to ArgSpec -> FullArgSpec change
482dd1ac3d2 doctests: AssertionError message changed in python 3.11
7b6fa565f42 doctests: message added more info in python 3.11
c928c2c7978 src/sage/all.py: Filter out imghdr deprecation warnings
ac0105e720d Filter out locale DeprecationWarning
# Sphinx 5.2
3ee509aec95 remove unused, and removed from sphinx 5, imported
get_module_members
18c92459b33 fix syntax so extlinks stop complaining
c27e4e4c979 migrate from filename_set to record_dependencies as suggested in
https://www.sphinx-doc.org/en/master/extdev/deprecated.html
c2e610cfba0 Fix build with sphinx 5.2
# Matplotlib 3.6
5501e0de0dc Support matplotlib 3.6
4645a0d0c10 Removing faulty plot
f0a77039bb2 Add back doctest
8371dd75013 Missing part of the fix
a8741d8c60d Edit the doctest
64589686c26 More edis of the doctest
# SymPy 1.10
609dd9deaea sage.manifolds: Update doctests for SymPy 1.10
# SciPy 1.8
9c8235e44ff Fix deprecation warning with scipy 1.8
# Singular 4.3.1p3
42342b90043 Apply
https://github.com/archlinux/svntogit-community/blob/packages/sagemath/trunk/sagemath-singular-4.3.1.p3.patch
6e03fbe3161 Singular supports larger exponents now, adapt tests
267177af61d Fix one more test
d2b0016b838 Account for different bahavior of pTakeOutComp and pTakeOutComp1
This makes it possible to compile sagemath, but then 138 tests fail, which is
larger then the threshold of 100.
Many are due to new deprecation warnings that can simply be ignored for now,
e.g. with the attached dt-ignore-deprecation-warnings.patch.
With that patch only 97 tests fail, so building sagemath works again!
Best regards,
RogoDescription: ignore some deprecation warnings
Author: Rogo
--- a/sage/src/sage/all.py
+++ b/sage/src/sage/all.py
@@ -126,6 +126,18 @@ warnings.filterwarnings('ignore', category=DeprecationWarning,
message=r"Use setlocale\(\), getencoding\(\) and getlocale\(\) instead",
module='docutils.io')
+# ignore some deprecation warnings
+warnings.filterwarnings('ignore', category=DeprecationWarning,
+message="msvccompiler is deprecated and slated to be removed in the future. Please discontinue use or file an issue with pypa/distutils describing your use case.")
+warnings.filterwarnings('ignore', category=FutureWarning,
+message=r"In the future `np.(bool|bytes)` will be defined as the corresponding NumPy scalar. \(This may have returned Python scalars in past versions.")
+warnings.filterwarnings('ignore', category=DeprecationWarning,
+message="'imghdr' is deprecated and slated for removal in Python 3.13")
+warnings.filterwarnings('ignore', category=DeprecationWarning,
+message="'cgi' is deprecated and slated for removal in Python 3.13")
+warnings.filterwarnings('ignore', category=DeprecationWarning,
+message=r"Passing unrecognized arguments to super\(ToggleButtons\).__init__\(style=\{'button_width': 'initial'\}\).")
+
end setup warnings ###
Processed: Re: Bug#1020576: please update sage for pari 2.15.0 and gap 4.12.0
Processing control commands: > tags -1 patch Bug #1020576 [src:sagemath] "FTBFS with setuptools >= 64" Added tag(s) patch. -- 1020576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1011172 marked as pending in segment
Processing control commands: > tag -1 pending Bug #1011172 [src:segment] segment: FTBFS with OpenJDK 17: Attempting to assign weaker access privileges to CharSequence.isEmpty() Added tag(s) pending. -- 1011172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011172: marked as pending in segment
Control: tag -1 pending Hello, Bug #1011172 in segment 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/java-team/segment/-/commit/4529ccc8200ae98fcd94474a1b9974c751ba86ec Fixed the build failure with Java 17 (Closes: #1011172) (this message was generated automatically) -- Greetings https://bugs.debian.org/1011172
Bug#1027153: marked as done (ruby-rails-html-sanitizer: CVE-2022-23517 CVE-2022-23518 CVE-2022-23519 CVE-2022-23520)
Your message dated Sun, 05 Feb 2023 22:50:54 + with message-id and subject line Bug#1027153: fixed in ruby-rails-html-sanitizer 1.4.4-1 has caused the Debian Bug report #1027153, regarding ruby-rails-html-sanitizer: CVE-2022-23517 CVE-2022-23518 CVE-2022-23519 CVE-2022-23520 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.) -- 1027153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-rails-html-sanitizer X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for ruby-rails-html-sanitizer. CVE-2022-23517[0]: | rails-html-sanitizer is responsible for sanitizing HTML fragments in | Rails applications. Certain configurations of rails-html-sanitizer | < 1.4.4 use an inefficient regular expression that is susceptible | to excessive backtracking when attempting to sanitize certain SVG | attributes. This may lead to a denial of service through CPU resource | consumption. This issue has been patched in version 1.4.4. https://github.com/rails/rails-html-sanitizer/security/advisories/GHSA-5x79-w82f-gw8w https://github.com/rails/rails-html-sanitizer/commit/56c61c0cebd1e493e8ad7bca2a0191609a4a6979 CVE-2022-23518[1]: | rails-html-sanitizer is responsible for sanitizing HTML fragments in | Rails applications. Versions >= 1.0.3, < 1.4.4 are vulnerable to | cross-site scripting via data URIs when used in combination with | Loofah >= 2.1.0. This issue is patched in version 1.4.4. https://github.com/rails/rails-html-sanitizer/issues/135 https://github.com/rails/rails-html-sanitizer/security/advisories/GHSA-mcvf-2q2m-x72m CVE-2022-23519[2]: | rails-html-sanitizer is responsible for sanitizing HTML fragments in | Rails applications. Prior to version 1.4.4, a possible XSS | vulnerability with certain configurations of Rails::Html::Sanitizer | may allow an attacker to inject content if the application developer | has overridden the sanitizer's allowed tags in either of the following | ways: allow both "math" and "style" elements, or allow both "svg" and | "style" elements. Code is only impacted if allowed tags are being | overridden. . This issue is fixed in version 1.4.4. All users | overriding the allowed tags to include "math" or "svg" and "style" | should either upgrade or use the following workaround immediately: | Remove "style" from the overridden allowed tags, or remove "math" and | "svg" from the overridden allowed tags. https://github.com/rails/rails-html-sanitizer/security/advisories/GHSA-9h9g-93gc-623h CVE-2022-23520[3]: | rails-html-sanitizer is responsible for sanitizing HTML fragments in | Rails applications. Prior to version 1.4.4, there is a possible XSS | vulnerability with certain configurations of Rails::Html::Sanitizer | due to an incomplete fix of CVE-2022-32209. Rails::Html::Sanitizer may | allow an attacker to inject content if the application developer has | overridden the sanitizer's allowed tags to allow both "select" and | "style" elements. Code is only impacted if allowed tags are being | overridden. This issue is patched in version 1.4.4. All users | overriding the allowed tags to include both "select" and "style" | should either upgrade or use this workaround: Remove either "select" | or "style" from the overridden allowed tags. NOTE: Code is _not_ | impacted if allowed tags are overridden using either the :tags option | to the Action View helper method sanitize or the :tags option to the | instance method SafeListSanitizer#sanitize. https://github.com/rails/rails-html-sanitizer/security/advisories/GHSA-rrfc-7g8p-99q8 If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-23517 https://www.cve.org/CVERecord?id=CVE-2022-23517 [1] https://security-tracker.debian.org/tracker/CVE-2022-23518 https://www.cve.org/CVERecord?id=CVE-2022-23518 [2] https://security-tracker.debian.org/tracker/CVE-2022-23519 https://www.cve.org/CVERecord?id=CVE-2022-23519 [3] https://security-tracker.debian.org/tracker/CVE-2022-23520 https://www.cve.org/CVERecord?id=CVE-2022-23520 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: ruby-rails-html-sanitizer Source-Version: 1.4.4-1 Done: Abhijith PA We believe that the bug you reported is fixed in the latest version of ruby-rails-html-sanitizer, which is due to be installed
Bug#1030635: rust-isahc: autopkgtest failure on s390x
Source: rust-isahc
Version: 1.7.2+ds-18
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/s390x/r/rust-isahc/31083641/log.gz
...
running 2 tests
test request_errors_if_read_timeout_is_reached ... FAILED
test timeout_during_response_body_produces_error ... FAILED
failures:
request_errors_if_read_timeout_is_reached stdout
thread 'request_errors_if_read_timeout_is_reached' panicked at 'assertion
failed: `result` matches `Err(e) if e == isahc :: error :: ErrorKind :: Timeout`
value: `Ok(Response { status: 200, version: HTTP/1.1, headers: {}, body:
Body(?) })`', tests/timeouts.rs:28:5
stack backtrace:
0: rust_begin_unwind
at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:584:5
1: core::panicking::panic_fmt
at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:142:14
2: timeouts::request_errors_if_read_timeout_is_reached
at ./tests/timeouts.rs:28:5
3: timeouts::request_errors_if_read_timeout_is_reached::{{closure}}
at ./tests/timeouts.rs:14:1
4: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
5: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose
backtrace.
timeout_during_response_body_produces_error stdout
thread 'timeout_during_response_body_produces_error' panicked at 'called
`Result::unwrap_err()` on an `Ok` value: 98304', tests/timeouts.rs:61:43
stack backtrace:
0: rust_begin_unwind
at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:584:5
1: core::panicking::panic_fmt
at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:142:14
2: core::result::unwrap_failed
at /usr/src/rustc-1.63.0/library/core/src/result.rs:1805:5
3: core::result::Result::unwrap_err
at /usr/src/rustc-1.63.0/library/core/src/result.rs:1194:22
4: timeouts::timeout_during_response_body_produces_error
at ./tests/timeouts.rs:61:9
5: timeouts::timeout_during_response_body_produces_error::{{closure}}
at ./tests/timeouts.rs:35:1
6: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
7: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose
backtrace.
failures:
request_errors_if_read_timeout_is_reached
timeout_during_response_body_produces_error
test result: FAILED. 0 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out;
finished in 0.54s
error: test failed, to rerun pass `--test timeouts`
Running
`/tmp/tmp.6iU3rvj85w/target/s390x-unknown-linux-gnu/debug/deps/unix-457994c20ca0a0bc
--skip accept_headers_populated_by_default --skip
header_can_be_inserted_in_httpclient_builder --skip
headers_in_request_builder_must_override_headers_in_httpclient_builder --skip
headers_in_request_builder_must_override_multiple_headers_in_httpclient_builder
--skip multiple_headers_with_same_key_can_be_inserted_in_httpclient_builder
--skip deflate_encoded_response_is_decoded_automatically --skip
gzip_encoded_response_is_decoded_automatically`
running 0 tests
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out;
finished in 0.00s
error: 3 targets failed:
`--test encoding`
`--test net`
`--test timeouts`
autopkgtest [12:03:05]: test rust-isahc-1:text-decoding:
---]
autopkgtest [12:03:06]: test rust-isahc-1:text-decoding: - - - - - - - - - -
results - - - - - - - - - -
rust-isahc-1:text-decoding FAIL non-zero exit status 101
autopkgtest [12:03:06]: summary
rust-isahc:@ FAIL non-zero exit status 101
rust-isahc-1:unstable-interceptors FAIL non-zero exit status 101
rust-isahc-1:FAIL non-zero exit status 101
rust-isahc-1:default FAIL non-zero exit status 101
rust-isahc-1:cookies FAIL non-zero exit status 101
rust-isahc-1:http2 FAIL non-zero exit status 101
rust-isahc-1:jsonFAIL non-zero exit status 101
rust-isahc-1:psl FAIL non-zero exit status 101
rust-isahc-1:spnego FAIL non-zero exit status 101
rust-isahc-1:static-curl FAIL non-zero exit status 101
rust-isahc-1:static-ssl FAIL non-zero exit status 101
rust-isahc-1:text-decoding FAIL non-zero exit status 101
Bug#1012102: marked as done (groovycsv: FTBFS with OpenJDK 17 due to an illegal reflective access during the tests)
Your message dated Sun, 05 Feb 2023 22:50:01 + with message-id and subject line Bug#1012102: fixed in groovycsv 1.3-3 has caused the Debian Bug report #1012102, regarding groovycsv: FTBFS with OpenJDK 17 due to an illegal reflective access during the tests 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.) -- 1012102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: groovycsv Version: 1.3-2 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 groovycsv fails to build with OpenJDK 17, the tests make an illegal reflective access into java.base/java.lang: :test Putting task artifact state for task ':test' into context took 0.0 secs. Up-to-date check for task ':test' took 0.008 secs. It is not up-to-date because: No history is available. Starting process 'Gradle Test Executor 2'. Working directory: /<> Command: /usr/lib/jvm/java-17-openjdk-amd64/bin/java -Dorg.gradle.native=false @/tmp/gradle-worker-classpath12606975899872403165txt -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant -ea worker.org.gradle.process.internal.worker.GradleWorkerMain 'Gradle Test Executor 2' Successfully started process 'Gradle Test Executor 2' Gradle Test Executor 2 started executing tests. com.xlson.groovycsv.CsvIteratorSpec > CsvIterator should close the underlying CSVReader instance when reaching the end of the file. FAILED java.lang.ExceptionInInitializerError at org.spockframework.mock.runtime.ProxyBasedMockFactory$CglibMockFactory.createMock(ProxyBasedMockFactory.java:80) at org.spockframework.mock.runtime.ProxyBasedMockFactory.create(ProxyBasedMockFactory.java:49) at org.spockframework.mock.runtime.JavaMockFactory.create(JavaMockFactory.java:51) at org.spockframework.mock.runtime.CompositeMockFactory.create(CompositeMockFactory.java:44) at org.spockframework.lang.SpecInternals.createMock(SpecInternals.java:47) at org.spockframework.lang.SpecInternals.createMockImpl(SpecInternals.java:282) at org.spockframework.lang.SpecInternals.MockImpl(SpecInternals.java:99) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at com.xlson.groovycsv.CsvIteratorSpec.CsvIterator should close the underlying CSVReader instance when reaching the end of the file.(CsvIteratorSpec.groovy:32) Caused by: net.sf.cglib.core.CodeGenerationException: java.lang.reflect.InaccessibleObjectException-->Unable to make protected final java.lang.Class java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) throws java.lang.ClassFormatError accessible: module java.base does not "opens java.lang" to unnamed module @4cfaf581 at net.sf.cglib.core.ReflectUtils.defineClass(ReflectUtils.java:464) at net.sf.cglib.core.AbstractClassGenerator.generate(AbstractClassGenerator.java:339) at net.sf.cglib.core.AbstractClassGenerator$ClassLoaderData$3.apply(AbstractClassGenerator.java:96) at net.sf.cglib.core.AbstractClassGenerator$ClassLoaderData$3.apply(AbstractClassGenerator.java:94) at net.sf.cglib.core.internal.LoadingCache$2.call(LoadingCache.java:54) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at net.sf.cglib.core.internal.LoadingCache.createEntry(LoadingCache.java:61) at net.sf.cglib.core.internal.LoadingCache.get(LoadingCache.java:34) at net.sf.cglib.core.AbstractClassGenerator$ClassLoaderData.get(AbstractClassGenerator.java:119) at net.sf.cglib.core.AbstractClassGenerator.create(AbstractClassGenerator.java:294) at net.sf.cglib.core.KeyFactory$Generator.create(KeyFactory.java:221) at net.sf.cglib.core.KeyFactory.create(KeyFactory.java:174) at net.sf.cglib.core.KeyFactory.create(KeyFactory.java:153) at net.sf.cglib.proxy.Enhancer.(Enhancer.java:73) ... 10 more Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make protected final java.lang.Class java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) throws java.lan
Bug#1012102: marked as pending in groovycsv
Control: tag -1 pending Hello, Bug #1012102 in groovycsv 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/java-team/groovycsv/-/commit/c258c208a62e0bbf13c38db68323f70aa6667d50 Fixed the build failure with Java 17 (Closes: #1012102) (this message was generated automatically) -- Greetings https://bugs.debian.org/1012102
Processed: Bug#1012102 marked as pending in groovycsv
Processing control commands: > tag -1 pending Bug #1012102 [src:groovycsv] groovycsv: FTBFS with OpenJDK 17 due to an illegal reflective access during the tests Added tag(s) pending. -- 1012102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030448: marked as done (rows: FTBFS: pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: '-0.4.2-dev-71afc647-')
Your message dated Sun, 05 Feb 2023 22:37:22 +
with message-id
and subject line Bug#1030448: fixed in rows 0.4.2~0-2
has caused the Debian Bug report #1030448,
regarding rows: FTBFS: pkg_resources.extern.packaging.version.InvalidVersion:
Invalid version: '-0.4.2-dev-71afc647-'
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.)
--
1030448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rows
Version: 0.4.2~0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config
> /usr/lib/python3/dist-packages/setuptools/dist.py:548: UserWarning: The
> version specified ('"0.4.2-dev+71afc647"') is an invalid version, this may
> not work as expected with newer versions of setuptools, pip, and PyPI. Please
> see PEP 440 for more details.
> warnings.warn(
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build
> /usr/lib/python3/dist-packages/setuptools/dist.py:548: UserWarning: The
> version specified ('"0.4.2-dev+71afc647"') is an invalid version, this may
> not work as expected with newer versions of setuptools, pip, and PyPI. Please
> see PEP 440 for more details.
> warnings.warn(
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_rows/build/rows
> copying rows/__init__.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows
> copying rows/cli.py -> /<>/.pybuild/cpython3_3.11_rows/build/rows
> copying rows/localization.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows
> copying rows/table.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows
> copying rows/operations.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows
> copying rows/fields.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows
> creating /<>/.pybuild/cpython3_3.11_rows/build/rows/plugins
> copying rows/plugins/plugin_html.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows/plugins
> copying rows/plugins/__init__.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows/plugins
> copying rows/plugins/ods.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows/plugins
> copying rows/plugins/plugin_json.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows/plugins
> copying rows/plugins/xls.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows/plugins
> copying rows/plugins/xpath.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows/plugins
> copying rows/plugins/dicts.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows/plugins
> copying rows/plugins/postgresql.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows/plugins
> copying rows/plugins/txt.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows/plugins
> copying rows/plugins/sqlite.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows/plugins
> copying rows/plugins/plugin_pdf.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows/plugins
> copying rows/plugins/plugin_parquet.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows/plugins
> copying rows/plugins/plugin_csv.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows/plugins
> copying rows/plugins/utils.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows/plugins
> copying rows/plugins/xlsx.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows/plugins
> creating /<>/.pybuild/cpython3_3.11_rows/build/rows/utils
> copying rows/utils/__init__.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows/utils
> copying rows/utils/download.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows/utils
> copying rows/utils/date.py ->
> /<>/.pybuild/cpython3_3.11_rows/build/rows/utils
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd '/<>/.pybuild/cpython3_3.11_rows/build';
> python3.11 -m nose -v --ignore-files=_parquet.py
> --ignore-files=tests_table.py --ignore-files=tests_plugin_postgresql.py
> --attr='!skip' --exclude=test_local_file_sample_size
> test_camel_to_snake
> (tests.tests_fields.FieldUtilsTestCase.test_camel_to_snake) ... ok
> test_detect_types (tests.tests_fields.FieldUtilsTestCase.test_detect_types)
> ... ok
> test_detect_types_binary
> (tests.tests_fields.FieldUtilsTestCase.test_detect_types_binary) ... ok
> test_detect_types_different_nu
Bug#978457: marked as done (phing: Not compatible with php8.0)
Your message dated Sun, 05 Feb 2023 22:36:56 + with message-id and subject line Bug#978457: fixed in phing 2.17.4-1 has caused the Debian Bug report #978457, regarding phing: Not compatible with php8.0 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.) -- 978457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: phing Version: 2.16.1-1 Severity: important Tags: upstream Control: block 976811 by -1 phing is not compatible (at all) with PHP 8. A version 3 is on its way, but has been in alpha stage for months. It will hopefully be PHP 8 compatible. signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: phing Source-Version: 2.17.4-1 Done: William Desportes We believe that the bug you reported is fixed in the latest version of phing, 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 978...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. William Desportes (supplier of updated phing 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: Sun, 05 Feb 2023 22:12:48 +0100 Source: phing Built-For-Profiles: noudeb Architecture: source Version: 2.17.4-1 Distribution: unstable Urgency: medium Maintainer: Debian PHP PEAR Maintainers Changed-By: William Desportes Closes: 978457 Changes: phing (2.17.4-1) unstable; urgency=medium . * New upstream version 2.17.4 (Closes: #978457) [ Athos Ribeiro ] * d/watch: - use https scheme to fix broken d/watch file. - update watch file format version to 4. . [ Debian Janitor ] * Use secure copyright file specification URI. * Bump debhelper from deprecated 9 to 13. * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse. * Remove unnecessary get-orig-source-target. . [ William Desportes ] * Upgrade Standards-Version to 4.6.2 * run wrap-and-sort and cme fix dpkg * Mark as "Multi-Arch: foreign" * Replace Uploaders by myself * Set branch on Vcs-Git * Update debian/upstream/metadata * Add DEP-3 Headers to the patch * Add gbp.conf * Update drop recommends patch * Add phing-*/package.xml to d/clean * Add autopkgtests * Add a patch for PHP 8.2 dynamic properties * Add a patch to update the package summary * Add an autopkgtest using phplint * Add PHP 8.2 patches for dynamic property, IteratorAggregate and Iterator * Add "Rules-Requires-Root: no" * Depend on php-xml Checksums-Sha1: 30ccf3d2ff84f4fc36c5bed572221714cbc1bdcd 1960 phing_2.17.4-1.dsc e0e3870fbcb19483d79bfe098106627a16522c64 573539 phing_2.17.4.orig.tar.gz c8840dedb1687386362b2db084bf0e6005af660d 8584 phing_2.17.4-1.debian.tar.xz 06945899bb8272e4102111d8f590f7f6fc31a194 61853 phing_2.17.4-1_source.buildinfo Checksums-Sha256: 7ecc52f21beca68e1c9e96cec89a11885ac2251a5fd77391d3d0604e8d6f0705 1960 phing_2.17.4-1.dsc 3c21a0d94a6e54d7f2de168d2d27f5e0f14e748922baefe3ee4faeacfd0d555c 573539 phing_2.17.4.orig.tar.gz 71a319013064c95d1ce2b295804be6bd46e38f0a429164983b220ac7be9bf4a5 8584 phing_2.17.4-1.debian.tar.xz 44d2411fd6ac32809a58a8ab9e66ae2d6a40325a1061f3b8d032ad2ecdb285c2 61853 phing_2.17.4-1_source.buildinfo Files: a04024214eb8a938a731a966e10f0217 1960 php optional phing_2.17.4-1.dsc 4743c49533a5b8517c1bc26767d7ee0c 573539 php optional phing_2.17.4.orig.tar.gz 8c60c6f8b69485d0fb9c1351eb384391 8584 php optional phing_2.17.4-1.debian.tar.xz 8a98f401d420d5da260dde64dac246b3 61853 php optional phing_2.17.4-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEExNkf3872tKPGU/14kKDvG4JRqIkFAmPgKlQACgkQkKDvG4JR qIlX2Q/9FuzT0I2S02OBh8AeqvZ2Y5U1Yw0X13oeSXzXsksbLXjDr3KTv5CqYAt+ LPx33SAWM+qky8hsm7f/bB/Ql6xam+TkbQc+OHOj0e8lnVwHKRIgocGVOLQtWtMe a3E69P+WCup3aUNnumaS5HTSi16/0lniPCq3ET+Y6AETWE8Zdmi+zWq+piX8x6vT ps3VtCmH/zQ16VE9qVMPBRLJCLfS0bo6iDN1+c8kB+AExxsuP8i2dKwl8wZttWR5 hsWZyYF+30dB9R1Fa26uWvuwWo0eCOvk3lZnHOMljOwOk3bM1ZVyhOuCfjfc5S0h WsKzG9bQDsi3iguG8MkoPt6wJ8dXgIh+AwIvfOg/QjmAtxSz6X7cZHhzeXQR0kbj uLZGebNO1mUBtYnDWMqtKBEJPxPaPs316W5HB+KnLmy6riJjZzFV1
Bug#1030628: marked as done (Missing dependency on python3-six makes package unusable)
Your message dated Sun, 05 Feb 2023 22:37:12 +
with message-id
and subject line Bug#1030628: fixed in python-service-identity 18.1.0-8
has caused the Debian Bug report #1030628,
regarding Missing dependency on python3-six makes package unusable
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.)
--
1030628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-trustme
Version: 0.9.0-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/trustme
> copying trustme/__init__.py ->
> /<>/.pybuild/cpython3_3.11/build/trustme
> copying trustme/__main__.py ->
> /<>/.pybuild/cpython3_3.11/build/trustme
> copying trustme/_cli.py ->
> /<>/.pybuild/cpython3_3.11/build/trustme
> copying trustme/_version.py ->
> /<>/.pybuild/cpython3_3.11/build/trustme
> copying trustme/py.typed ->
> /<>/.pybuild/cpython3_3.11/build/trustme
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build;
> python3.11 -m pytest tests
> = test session starts
> ==
> platform linux -- Python 3.11.1, pytest-7.2.1, pluggy-1.0.0+repack
> rootdir: /<>
> collected 10 items / 1 error
>
> ERRORS
>
> _ ERROR collecting .pybuild/cpython3_3.11/build/tests/test_trustme.py
> __
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.11/build/tests/test_trustme.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> tests/test_trustme.py:21: in
> import service_identity.pyopenssl # type: ignore[import]
> /usr/lib/python3/dist-packages/service_identity/__init__.py:7: in
> from . import cryptography, pyopenssl
> /usr/lib/python3/dist-packages/service_identity/pyopenssl.py:9: in
> import six
> E ModuleNotFoundError: No module named 'six'
> === short test summary info
>
> ERROR tests/test_trustme.py
> Interrupted: 1 error during collection
>
> === 1 error in 0.18s
> ===
> E: pybuild pybuild:388: test: plugin distutils failed with: exit code=2: cd
> /<>/.pybuild/cpython3_3.11/build; python3.11 -m pytest tests
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11
> returned exit code 13
The full build log is available from:
http://qa-logs.debian.net/2023/02/03/python-trustme_0.9.0-1.1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230203;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230203&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-service-identity
Source-Version: 18.1.0-8
Done: Robie Basak
We believe that the bug you reported is fixed in the latest version of
python-service-identity, 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 clos
Bug#1029594: Fails to authenticate mit o365
Am 05.02.23 um 19:56 schrieb Chandler Sobel-Sorenson: Carsten Schoenert wrote on 2/5/23 3:39 AM: If you need your laptop or your workstation for mission critical things than Debian unstable/sid isn't the right choice. If you do so then you will need some knowledge to handle situations like happen now.I'm not. The broken package has been released to testing already. In an ideal world I would have two separate computers but not everyone has ideal situations. testing release is good for my situation and have now added notifications of important bugs for apt-listbugs config as well, so thank you for mentioning that. However, that's not the default for users. I don't understand what you want from me. Is the world going down now? For sure not! Did such situations did happen in the past? Yes, several times while I maintaining Thunderbird. Do I have a life beside Debian? Yes I have. Did you use stable for your daily work as Debian is suggesting? I don't think so. Would you be affected by this issue if you use stable? No! Does your emails help preventing others? Also here I don't think so. You even don't have tried to use some pre-compiled version from Mozilla and did give some feedback, you still do nothing more than complaining how bad the situation is. So, live with the situation like I do. We are all volunteers and do the work in our free time. Once I got time I will try to look at situation. -- Regards Carsten
Processed: Re: can wolfssl bug be closed?
Processing control commands: > severity -1 important Bug #1023697 [src:wolfssl] Keep out of testing Severity set to 'important' from 'serious' > retitle -1 Make it clear that wolfssl is only for packages that cannot use > openssl Bug #1023697 [src:wolfssl] Keep out of testing Changed Bug title to 'Make it clear that wolfssl is only for packages that cannot use openssl' from 'Keep out of testing'. -- 1023697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1023697: can wolfssl bug be closed?
Control: severity -1 important Control: retitle -1 Make it clear that wolfssl is only for packages that cannot use openssl On Tue, 17 Jan 2023 04:19:46 -0500 gs-bugs.debian@gluelogic.com wrote: Can this be closed? Are there any action items remaining for this bug? After some more messages with Moritz, wolfssl can be kept in bookworm under some conditions. It must only be used in packages that cannot use openssl so that people can harden their openssl setup and most packages are affected. wolfssl's debian/README.Debian file should prominently state something like the following: "wolfSSL is solely provided as an alternative to OpenSSL for packages whose licenses are incompatible with Apache-2.0." Please make sure to edit that file before bookworm is released. Maybe the package description should contain this as well.
Processed: severity of 1020544 is serious
Processing commands for cont...@bugs.debian.org: > # > https://buildd.debian.org/status/fetch.php?pkg=siconos&arch=s390x&ver=4.4.0%2Bdfsg-2&stamp=1675453676&raw=0 > severity 1020544 serious Bug #1020544 [siconos] siconos: FTBFS on s390x: Cholesky solve kNM_test failed Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1020544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020544 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Debian bugs control
Processing commands for cont...@bugs.debian.org: > retitle 1030510 mariadb: FTBFS on s390x: crash on test main.plugin_auth > 'innodb' Bug #1030510 [src:mariadb] mariadb: FTBFS on s390x: timeout Changed Bug title to 'mariadb: FTBFS on s390x: crash on test main.plugin_auth 'innodb'' from 'mariadb: FTBFS on s390x: timeout'. > retitle 1006531 mariadb: FTBFS on hurd-i386: cmake/plugin.cmake: Plugin > AUTH_SOCKET cannot be built Bug #1006531 [mariadb] mariadb: FTBFS on hurd-i386: undefined reference to misc functions and files Changed Bug title to 'mariadb: FTBFS on hurd-i386: cmake/plugin.cmake: Plugin AUTH_SOCKET cannot be built' from 'mariadb: FTBFS on hurd-i386: undefined reference to misc functions and files'. > forwarded 1006531 https://jira.mariadb.org/browse/MDEV-8535 Bug #1006531 [mariadb] mariadb: FTBFS on hurd-i386: cmake/plugin.cmake: Plugin AUTH_SOCKET cannot be built Set Bug forwarded-to-address to 'https://jira.mariadb.org/browse/MDEV-8535'. > user debian-s...@lists.debian.org Setting user to debian-s...@lists.debian.org (was o...@debian.org). > usertags 1030510 + s390x There were no usertags set. Usertags are now: s390x. > thanks Stopping processing here. Please contact me if you need assistance. -- 1006531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006531 1030510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028163: sshfs-fuse bug
El 5/2/23 a las 21:54, Steven Robbins escribió: There are a couple of odd things about this bug. First: it doesn't seem like an RC bug because the test manifestly runs fine on buildds -- see https://buildd.debian.org/status/package.php?p=sshfs-fuse The package is trying to access the network. This is considered RC even if it works in the official buildds. Second: the bug log shows python 3.9.2 is used. That hasn't been the default python since 2021 -- so it's an unusual test environment. Maybe I was reporting the failure in bullseye (because packages in stable must build in stable). Here is a recent build log from January in bookworm. Thanks. sshfs-fuse_3.7.3-1_amd64-20230112T160950.844Z.gz Description: application/gzip
Bug#1030096: #1030096 dask.distributed autopkgtest fail
I currently have this in a state where it sometimes succeeds and sometimes doesn't: https://salsa.debian.org/rnpalmer-guest/dask.distributed/-/tree/fix1030096 Tests I've seen to fail multiple times (and don't have a fix for): test_balance_expensive_tasks[enough work to steal] https://salsa.debian.org/rnpalmer-guest/dask.distributed/-/jobs/3902376 (Seems to be the most common problem. Using @pytest.mark.flaky to try 3 times doesn't seem to have helped, suggesting that if it fails once it keeps failing in that run. Applying part of upstream pull 7253 seemed to make things worse, but I haven't tried applying the whole thing.) test_popen_timeout https://salsa.debian.org/rnpalmer-guest/dask.distributed/-/jobs/3902745 Tests I've seen to fail once: test_stress_scatter_death https://salsa.debian.org/rnpalmer-guest/dask.distributed/-/jobs/3902040 test_tcp_many_listeners[asyncio] https://salsa.debian.org/rnpalmer-guest/dask.distributed/-/jobs/3896327
Processed: RFS: libquazip1-qt5/1.4-1 [RC] -- Qt/C++ wrapper over minizip - Version 1 (Qt5)
Processing control commands: > block 1028641 by -1 Bug #1028641 [libquazip1-qt5-dev] libquazip1-qt5-dev: Missing dependencies on "qtbase5-dev, zlib1g-dev" 1028641 was not blocked by any bugs. 1028641 was not blocking any bugs. Added blocking bug(s) of 1028641: 1030629 -- 1028641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028641 1030629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030629 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1030487: python-trustme: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Processing commands for cont...@bugs.debian.org:
> clone 1030487 -1
Bug #1030487 [src:python-trustme] python-trustme: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Bug 1030487 cloned as bug 1030628
> reassign -1 python3-service-identity 18.1.0-7
Bug #1030628 [src:python-trustme] python-trustme: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Bug reassigned from package 'src:python-trustme' to 'python3-service-identity'.
No longer marked as found in versions python-trustme/0.9.0-1.1.
Ignoring request to alter fixed versions of bug #1030628 to the same values
previously set
Bug #1030628 [python3-service-identity] python-trustme: FTBFS: dh_auto_test:
error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit
code 13
Marked as found in versions python-service-identity/18.1.0-7.
> retitle -1 Missing dependency on python3-six makes package unusable
Bug #1030628 [python3-service-identity] python-trustme: FTBFS: dh_auto_test:
error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit
code 13
Changed Bug title to 'Missing dependency on python3-six makes package unusable'
from 'python-trustme: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p 3.11 returned exit code 13'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1030487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030487
1030628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1030487: python-trustme: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
clone 1030487 -1 reassign -1 python3-service-identity 18.1.0-7 retitle -1 Missing dependency on python3-six makes package unusable thanks On Sat, Feb 04, 2023 at 08:58:30AM +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. [...] > > ImportError while importing test module > > '/<>/.pybuild/cpython3_3.11/build/tests/test_trustme.py'. > > Hint: make sure your test modules/packages have valid Python names. > > Traceback: > > /usr/lib/python3.11/importlib/__init__.py:126: in import_module > > return _bootstrap._gcd_import(name[level:], package, level) > > tests/test_trustme.py:21: in > > import service_identity.pyopenssl # type: ignore[import] > > /usr/lib/python3/dist-packages/service_identity/__init__.py:7: in > > from . import cryptography, pyopenssl > > /usr/lib/python3/dist-packages/service_identity/pyopenssl.py:9: in > > import six > > E ModuleNotFoundError: No module named 'six' Looks like python3-service-identity should have a dependency on python3-six but it does not. Steps to reproduce: apt install python3-service-identity python3 >>> from service_identity.pyopenssl import verify_hostname ... ModuleNotFoundError: No module named 'six' This is expected to work as documented at https://service-identity.readthedocs.io/en/stable/api.html I will send a fix for this to Salsa shortly. Robie signature.asc Description: PGP signature
Bug#1030574: marked as done (debian-edu-router-config: Missing dependency on procps)
Your message dated Sun, 05 Feb 2023 21:04:26 + with message-id and subject line Bug#1030574: fixed in debian-edu-router 2.12.3 has caused the Debian Bug report #1030574, regarding debian-edu-router-config: Missing dependency on procps 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.) -- 1030574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-edu-router-config Version: 2.12.2 Severity: serious https://piuparts.debian.org/sid/fail/debian-edu-router-config_2.12.2.log ... /var/lib/dpkg/info/debian-edu-router-config.postinst: line 1485: sysctl: command not found dpkg: error processing package debian-edu-router-config (--configure): installed debian-edu-router-config package post-installation script subprocess returned error exit status 127 Processing triggers for libc-bin (2.36-8) ... Errors were encountered while processing: debian-edu-router-config E: Sub-process /usr/bin/dpkg returned an error code (1) --- End Message --- --- Begin Message --- Source: debian-edu-router Source-Version: 2.12.3 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of debian-edu-router, 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 1030...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated debian-edu-router 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: Sun, 05 Feb 2023 21:28:34 +0100 Source: debian-edu-router Architecture: source Version: 2.12.3 Distribution: unstable Urgency: medium Maintainer: Debian Edu Developers Changed-By: Mike Gabriel Closes: 1030574 Changes: debian-edu-router (2.12.3) unstable; urgency=medium . * debian/control: Add to D (d-e-r-c): procps (provides sysctl cmd). (Closes: #1030574). Checksums-Sha1: e5f8760b5617ee52fe6592ffa646114041278a4d 1920 debian-edu-router_2.12.3.dsc 8e3d18bfba6022dd9310d3274196bb55a01d7bed 101964 debian-edu-router_2.12.3.tar.xz c5ab466dbcdae25bef3929511f902fe0fbc23040 6308 debian-edu-router_2.12.3_source.buildinfo Checksums-Sha256: ffc408a385d80903a2ecd90faa307957c6f62c590e9ae93220a17bc0c7e4bcea 1920 debian-edu-router_2.12.3.dsc aed2315105e97a80ad021933f71dfcd784243905f5635be8364c7f2003b4c792 101964 debian-edu-router_2.12.3.tar.xz f049074a0a50cb779626ae313017270ee9e96a2dd0f6e0fbfdf4a9348007d95c 6308 debian-edu-router_2.12.3_source.buildinfo Files: fc95132c067af9db6ba0f950803dc903 1920 admin optional debian-edu-router_2.12.3.dsc c3e9b18a7df0b637550b8826d54c751c 101964 admin optional debian-edu-router_2.12.3.tar.xz bf2a5820c99283309d6ee2263ba8c4d4 6308 admin optional debian-edu-router_2.12.3_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmPgEf8VHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxE0cQALZDTQHMOc35qeKXDap9DSEUiXyy IY5lR52vMV78/yVBk7QBeX1Pnm51N0xKCH5b5+10WvAvZgIdYhOWQk631AwyfnGP M/OWb+FlF9SZgdib5OTsdtXEeaNqQRIYvngb6qL/CWUbrcC1mjjqSFWPnXFouzdk yQoaE7Yw7i9k1wjQYy6zvZbM2/t2FJn5jFNMTSXcIbfVU3Lb4fbiO/KiTe0LfmLM lJowV93YBRMA2u+UE5+ffxPxU2GiaV4V6nYNlelQbcYXowFdOfzNbrTXaz2LNpzH mMA0+6zWziC1fvDaBssJRvXE9oy71Zj+XVrFqBzfFLa5RHi6hzLDca2Q1Rk4jtZY ZcWzl33+49KSFejApX8wULWUykBmeDFuenH7V/z2imcsU0t0ELwoyVIkWJPiR4tq jM89hllCob/+CGU8iRBHrGvocv/Ybc+13vmoYdN74Vq06hw4O23+oCYNEhBa2sfJ fVk6hdlyrCRI4YiBifwMV1XVqwiGfpAGEj4AUhB3zKaDmyY0FF24VdgMii5RpeKA duK3Xu5uAkuQkVOg75krlxHZPAfR+BcoE+hXpqpjVTiMszbtVPpWbvl33CV3GgQv 4NHwnGRS7Rss1JhOJaCkpwCuGwvk6UKzZJWCcFBQMPAHZ4ghlrA8DwseKXi5N31h tR3mWSJ0V19xHnd7 =YGLN -END PGP SIGNATURE End Message ---
Bug#1030510: mariadb: FTBFS on s390x: timeout
After restarting the build there is no longer a timeout, but a crash: main.plugin_auth 'innodb'w1 [ fail ] Found warnings/errors in server log file! Test ended at 2023-02-05 09:41:56 line Attempting backtrace. You can use the following information to find out ^ Found warnings in /<>/builddir/mysql-test/var/1/log/mysqld.1.err ok - found 'core' (0/5) Core generated by '/<>/builddir/sql/mariadbd' Output from gdb follows. The first stack trace is from the failing thread. The following stack traces are from all threads (so the failing one is duplicated). -- [New LWP 460078] [New LWP 460124] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/s390x-linux-gnu/libthread_db.so.1". Core was generated by `/<>/builddir/sql/mariadbd --defaults-group-su'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x03ff99c48992 in kill () from /lib/s390x-linux-gnu/libc.so.6 [Current thread is 1 (Thread 0x3ff9ab6a820 (LWP 460078))] #0 0x03ff99c48992 in kill () from /lib/s390x-linux-gnu/libc.so.6 #1 0x02aa226907c4 in handle_fatal_signal (sig=) at ./sql/signal_handler.cc:367 #2 #3 0x02aa22b7c26a in my_read (Filedes=, Buffer=0x3ff9ab6a820 "", Count=4096, MyFlags=) at ./mysys/my_read.c:63 #4 0x02aa22690266 in output_core_info () at ./sql/signal_handler.cc:90 #5 0x02aa22690792 in handle_fatal_signal (sig=) at ./sql/signal_handler.cc:351 #6 #7 0x03ff99d0e632 in munmap () from /lib/s390x-linux-gnu/libc.so.6 #8 0x03ff99ca7790 in free () from /lib/s390x-linux-gnu/libc.so.6 #9 0x02aa228bfe6e in aligned_free (ptr=) at ./include/aligned.h:37 #10 pfs_free (ptr=, size=2048000, klass=0x2aa23e47900 ) at ./storage/perfschema/pfs_global.cc:83 #11 pfs_free (klass=0x2aa23e47900 , size=size@entry=2048000, ptr=) at ./storage/perfschema/pfs_global.cc:78 #12 0x02aa228b5fe6 in PFS_thread_allocator::free_array (this=, array=array@entry=0x2aa24cf4d30) at ./storage/perfschema/pfs_buffer_container.cc:715 #13 0x02aa228c25da in PFS_buffer_scalable_container::cleanup (this=) at ./storage/perfschema/pfs_buffer_container.h:506 #14 PFS_buffer_scalable_container::cleanup (this=) at ./storage/perfschema/pfs_buffer_container.h:491 #15 cleanup_instruments () at ./storage/perfschema/pfs_instr.cc:233 #16 0x02aa228d000c in cleanup_performance_schema () at ./storage/perfschema/pfs_server.cc:296 #17 0x02aa228d04f0 in shutdown_performance_schema () at ./storage/perfschema/pfs_server.cc:326 #18 0x02aa2233f912 in mysqld_exit (exit_code=exit_code@entry=0) at ./sql/mysqld.cc:1943 #19 0x02aa2234a4fe in mysqld_main (argc=, argv=) at ./sql/mysqld.cc:6040 #20 0x03ff99c2b84a in ?? () from /lib/s390x-linux-gnu/libc.so.6 #21 0x03ff99c2b932 in __libc_start_main () from /lib/s390x-linux-gnu/libc.so.6 #22 0x02aa2233d378 in _start () A previous restart also had: main.mysql_upgrade 'innodb' w1 [ fail ] Found warnings/errors in server log file! [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/s390x-linux-gnu/libthread_db.so.1". Core was generated by `/<>/builddir/sql/mariadbd --defaults-group-su'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x03ffaa0c8992 in kill () from /lib/s390x-linux-gnu/libc.so.6 [Current thread is 1 (Thread 0x3ffaafea820 (LWP 1668996))] #0 0x03ffaa0c8992 in kill () from /lib/s390x-linux-gnu/libc.so.6 #1 0x02aa26c107c4 in handle_fatal_signal (sig=) at ./sql/signal_handler.cc:367 #2 #3 0x02aa270fc26a in my_read (Filedes=, Buffer=0x696c646469722f6d , Count=4096, MyFlags=) at ./mysys/my_read.c:63 #4 0x02aa26c10266 in output_core_info () at ./sql/signal_handler.cc:90 #5 0x02aa26c10792 in handle_fatal_signal (sig=) at ./sql/signal_handler.cc:351 #6 #7 0x03ffaa18e632 in munmap () from /lib/s390x-linux-gnu/libc.so.6 #8 0x03ffaa127790 in free () from /lib/s390x-linux-gnu/libc.so.6 #9 0x02aa26e40022 in aligned_free (ptr=) at ./include/aligned.h:37 #10 pfs_free (ptr=, size=2304000, klass=0x2aa283c8f00 ) at ./storage/perfschema/pfs_global.cc:83 #11 pfs_free (ptr=, size=2304000, klass=0x2aa283c8f00 ) at ./storage/perfschema/pfs_global.cc:78 #12 pfs_free_array (klass=0x2aa283c8f00 , n=n@entry=32000, size=size@entry=72, ptr=) at ./storage/perfschema/pfs_global.cc:134 #13 0x02aa26e36680 in PFS_user_allocator::free_array (this=, array=array@entry=0x2aa297ac0a0) at ./storage/perfschema/pfs_buffer_container.cc:875 #14 0x02aa26e53786 in PFS_buffer_scalable_container::cleanup (this=) at ./storage/perfschema/pfs_buffer_container.h:506 #15 PFS_buffer_scalable_container::cleanup (this=) at ./storage/perfschema/pfs_buffer_container.h:491 #16 cleanup_user () at ./storage/perfschema/pfs_user.cc:63 #17 0x02aa26e4ffb8 in cleanup_performance_schema () at ./storage/perfschema/pfs_server.cc:275 #18 0x02aa26e504f0 in shutdown_performance_schema () at ./storage/perfschema/pfs_server.cc:3
Bug#1028163: sshfs-fuse bug
There are a couple of odd things about this bug. First: it doesn't seem like an RC bug because the test manifestly runs fine on buildds -- see https://buildd.debian.org/status/package.php?p=sshfs-fuse I'd suggest to downgrade the bug on this basis. Second: the bug log shows python 3.9.2 is used. That hasn't been the default python since 2021 -- so it's an unusual test environment. -Steve signature.asc Description: This is a digitally signed message part.
Bug#1030488: marked as done (trapperkeeper-webserver-jetty9-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact puppetlabs:ring-middleware:jar:debian has
Your message dated Sun, 05 Feb 2023 20:42:40 + with message-id and subject line Bug#1030488: fixed in puppetlabs-http-client-clojure 2.1.0-4 has caused the Debian Bug report #1030488, regarding trapperkeeper-webserver-jetty9-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact puppetlabs:ring-middleware:jar:debian has not been downloaded from it before. 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.) -- 1030488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: trapperkeeper-webserver-jetty9-clojure Version: 4.4.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230203 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 '/<>' > lein test > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact puppetlabs:trapperkeeper-webserver-jetty9:jar:debian has not > been downloaded from it before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact puppetlabs:trapperkeeper-webserver-jetty9:jar:debian has not been > downloaded from it before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact puppetlabs:trapperkeeper-webserver-jetty9:jar:test:debian has > not been downloaded from it before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact puppetlabs:trapperkeeper-webserver-jetty9:jar:test:debian has not > been downloaded from it before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact puppetlabs:ring-middleware:jar:debian has not been downloaded > from it before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact puppetlabs:ring-middleware:jar:debian has not been downloaded from > it before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/02/03/trapperkeeper-webserver-jetty9-clojure_4.4.1-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230203;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230203&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: puppetlabs-http-client-clojure Source-Version: 2.1.0-4 Done: Jérôme Charaoui We believe that the bug you reported is fixed in the latest version of puppetlabs-http-client-clojure, 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 1030...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérôme Charaoui (supplier of updated puppetlabs-http-client-clojure 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: Sun, 05 Feb 2023 14:15:56 -0500 Source: puppetlabs-http-client-clojure Architecture: source Version: 2.1.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Clojure Maintainers Changed-By: Jérôme Charaoui Closes: 1030480 1030488 Changes: puppetlabs-http-client-clojure (2.1.0-4) unstable; urgency=medium . * d/rules: build without tests temporarily (Closes: #1030480, #1030488) * d/control:
Bug#1030480: marked as done (puppetlabs-http-client-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact compojure:compojure:jar:debian has not been downl
Your message dated Sun, 05 Feb 2023 20:42:40 + with message-id and subject line Bug#1030480: fixed in puppetlabs-http-client-clojure 2.1.0-4 has caused the Debian Bug report #1030480, regarding puppetlabs-http-client-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact compojure:compojure:jar:debian has not been downloaded from it before. 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.) -- 1030480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: puppetlabs-http-client-clojure Version: 2.1.0-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230203 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 '/<>' > ./dev-resources/gen-pki.sh > > Generating primary self-signed CA > ..++*+...+.+...+*++..++.++...+.+...+.+...+.+..+.+..+++..+..++..+..+..+.+++..+...+...++..+...+.+.++..+...++..+...+...++..++.+.+...+.+...+...+...++.+..+...+...+...++.+.+..+...+..+.+..+..+...+...+..+...+.+.+...+.++.+.+..+..+..+.+.+..+.+..+...+...+..+...+...+...+...+..+...++..+.+...++..+.+.+.+...+...+ > ...+...+.+...++.+*+..+.+..+.+...+..++*..+..+.+...+..+...+..+.+...+..++...++...+..+...+.+..+...+..+.+.+.+.+...+..+...+..+..++.+.+..+..++.+...++.+.+...+..+.+..+...+...+.+...+...+...+...+.+...+...+..+...++...+..+...+..+...+...+.+...+..+.+..+...+..+...+.+..+.++.+.+.+..+...+...+.+..+...+.+...+..++.+.++...+.+..++..++...++..+...+..+...+++...+..+..+.+.+...+...++...+...+...+..+...+...+.+..+..+...+..++...+..++.++...++...++...+ > - > > Generating node cert > > Creating node CSR > > Signing node CSR > Certificate request self-signature ok > subject=C = US, ST = OR, L = Portland, O = "Puppet, Inc", CN = localhost > > Generating alternate self-signed CA > ..+..+..+*...+.+..+...+..+...+...+...+.+.+.+..+++...+..+*.++...+..+.+++.+.+.+..+...+.+...+...+..+.+.+..+.+..+.+..+.+..+...+.+.+.+...+..++..++...+..++.+..+.+..+...+.+.+..+..+..+.+...+...+.+.+.+.+.+..++.+.+.++...+++...++..+...+..+...+.+...+.++...+...+.
Processed: tagging 1019604
Processing commands for cont...@bugs.debian.org: > tags 1019604 + pending Bug #1019604 [src:bsfilter] bsfilter: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1019604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019604 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027965: Fix for the RC bug in vtk
Hi Steven, * Steven Robbins [2023-02-05 10:26]: Was looking yesterday for an RC bug to fix and noticed #1027965 against VTK -- a build failure in gdcm caused by missing dependency. The fix proposed by Mathieu seems reasonable to me. I assume you mean the proposal to add a libvtk9-qt-dev dependency to libvtk9-dev? Note that libvtk9-dev already has a dependency to libvtk9-qt-dev resulting in a cyclic dependency between both. Those are known to not work well in Debian and should be avoided. The underlying problem here is that the vtk9 cmake files are not separated between libvtk9-dev and libvtk9-qt-dev so the split seems artificial to Debian and both packages should probably be merged into one or the cmake files need rewriting. Cheers Jochen signature.asc Description: PGP signature
Bug#1026962: openjfx: tries to build with -j64 on a host with 2 processors
Source: openjfx Followup-For: Bug #1026962 Could the following build-related scripting be something to do with it? - https://salsa.debian.org/java-team/openjfx/-/blob/debian/11.0.11+1-1.1/modules/javafx.web/src/main/native/Tools/Scripts/webkitdirs.pm#L494-499 - https://salsa.debian.org/java-team/openjfx/-/blob/debian/11.0.11+1-1.1/modules/javafx.web/src/main/native/Tools/Scripts/build-webkit#L300-305 (perhaps something about the way that numberOfCPUs is being evaluated on s390x hosts isn't matching the expectations of the build script)
Bug#1030622: tex-common package post-installation script subprocess returned error exit status 1
Am 05.02.2023 um 19:56 teilte Stéphane Glondu mit:
Package: tex-common
Version: 6.18
Severity: serious
Hello,
I got this when upgrading texlive today in testing:
Paramétrage de tex-common (6.18) ...
Running mktexlsr. This may take some time... done.
Running mtxrun --generate. This may take some time... done.
Running updmap-sys. This may take some time... done.
Running mktexlsr /var/lib/texmf ... done.
Building format(s) --all.
This may take some time...
fmtutil failed. Output has been stored in
/tmp/fmtutil.RDPxpv93
Please include this file if you report a bug.
Today the new texlive-base & texlive-extra did migrate to testing and
hence were upgraded on your system. The texlive-lang did not migrate
yet, this will happen soon. Once texlive-lang-japanese is upgraded,
please repeat the test. Is suspect an incompatibility in these packages,
as I'm not able to reproduce the issue using unstable.
For the records: the error message is:
**
*
* making upLaTeX format
*
**
(/usr/share/texlive/texmf-dist/tex/platex/base/plcore.ltx
! Argument of \platexNILa has an extra }.
\par
l.52 ...ter\expandafter\expandafter{\platexBANNER}
%
?
! Emergency stop.
\par
l.52 ...ter\expandafter\expandafter{\platexBANNER}
%
Hilmar
--
sigfault
Bug#1028638: marked as done (libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call)
Your message dated Sun, 05 Feb 2023 19:35:36 + with message-id and subject line Bug#1028638: fixed in libproxy 0.4.18-1.2 has caused the Debian Bug report #1028638, regarding libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call 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.) -- 1028638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gajim Version: 1.6.0-1 Severity: important Gajim 1.6.0-1 crashes while connecting to XMPP server(s). Visually the Gajim window pops up briefly and then disappears again. According to the stack trace below the crash seems related to libproxy.so.1, but I don't have any proxy configured for the account. $ gdb --ex r --args python3 $(command -v gajim) -v [shortened to remove private info, let me know if you need more detail] 01/08/23 11:06:16 (D) gajim.gui.main Window state changed: ICONIFIED: False, WITHDRAWN: False 01/08/23 11:06:16 (I) gajim.c.settings Set settings: app 01/08/23 11:06:16 (I) gajim.c.settings Signal: is_window_visible changed 01/08/23 11:06:16 (D) gajim.c.storage.cache Execution time for _commit: 1 ms 01/08/23 11:06:16 (I) gajim.c.settings Commit 01/08/23 11:06:16 (I) gajim.c.dbus.logindName org.freedesktop.login1 appeared, owned by :1.0 01/08/23 11:06:16 (I) gajim.c.dbus.logindObtained shutdown delay inhibitor 01/08/23 11:06:16 (I) gajim.gui.notification Notifications D-Bus connected 01/08/23 11:06:16 (I) gajim.c.settings Set account settings: *** 01/08/23 11:06:16 (I) gajim.c.settings Signal: last_status changed 01/08/23 11:06:16 (I) gajim.c.settings Set account settings: *** 01/08/23 11:06:16 (I) gajim.c.settings Signal: last_status_msg changed 01/08/23 11:06:16 (I) gajim.client Connect 01/08/23 11:06:16 (I) gajim.client State: 3 01/08/23 11:06:16 (I) gajim.client Signal: state-changed 01/08/23 11:06:16 (I) gajim.gui.css Get .gajim-status-connecting color: rgb(77, 166, 255) 01/08/23 11:06:16 (D) gajim.c.storage.cache Execution time for get_contact: 1 ms 01/08/23 11:06:16 (I) nbxmpp.stream (***) Connect 01/08/23 11:06:16 (I) nbxmpp.stream (***) Set state: StreamState.RESOLVE 01/08/23 11:06:16 (I) nbxmpp.http Request(140734679377472): Created 01/08/23 11:06:16 (I) nbxmpp.http Request(140734679377472): Request sent, method: GET, uri: https://***/.well-known/host-meta [New Thread 0x7fff3fbff6c0 (LWP 8799)] Thread 27 "pool-org.gajim." received signal SIGABRT, Aborted. [Switching to Thread 0x7fff53fff6c0 (LWP 8765)] __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory. (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #1 0x77d28d2f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78 #2 0x77cd9ef2 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x77cc4472 in __GI_abort () at ./stdlib/abort.c:79 #4 0x73a9d40a in () at /lib/x86_64-linux-gnu/libstdc++.so.6 #5 0x73aa861a in __gxx_personality_v0 () at /lib/x86_64-linux-gnu/libstdc++.so.6 #6 0x71c63131 in __libunwind_Unwind_Resume () at /lib/x86_64-linux-gnu/libunwind.so.8 #7 0x7fff51ebd34a in () at /lib/x86_64-linux-gnu/libproxy.so.1 #8 0x7fff51eb3e52 in () at /lib/x86_64-linux-gnu/libproxy.so.1 #9 0x7fff51eb4287 in () at /lib/x86_64-linux-gnu/libproxy.so.1 #10 0x7fff51eb4751 in px_proxy_factory_get_proxies () at /lib/x86_64-linux-gnu/libproxy.so.1 #11 0x7fff51ee761f in () at /usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so #12 0x77024793 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #13 0x773016da in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x77300d0d in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x77d26fd4 in start_thread (arg=) at ./nptl/pthread_create.c:442 #16 0x77da766c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-6-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=de_
Bug#1029461: marked as done (xemacs21-packages: FTBFS in bookworm (LaTeX Error: File `pdftexcmds.sty' not found))
Your message dated Sun, 5 Feb 2023 20:28:02 +0100 with message-id <2355b938-ea8a-f9c9-504e-76af28445...@web.de> and subject line Closing has caused the Debian Bug report #1025985, regarding xemacs21-packages: FTBFS in bookworm (LaTeX Error: File `pdftexcmds.sty' not found) 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.) -- 1025985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025985 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:xemacs21-packages Version: 2009.02.17.dfsg.3-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules build-indep chmod +x debian/makevarfile debian/makevarfile "debian/./var_file.pl" \ "MAJVERSION" "21" \ "VERSION" "2009.02.17.dfsg.3" \ "SUBNAME" "" \ "CONF_NAME" "amd64-debian-linux" \ "ARCH" "amd64" \ "HTML_FILE_LOC" "debian/html" \ "TMP_FILE_LOC" "debian/tmp" \ "PREFIX" "usr" \ "TOPDIR" "/<>" [...] Loading /usr/lib/xemacs-21.4.24/lisp/auto-autoloads... Loading /<>/xemacs-packages/edit-utils/auto-autoloads... Loading /<>/xemacs-packages/mail-lib/auto-autoloads... Loading /<>/xemacs-packages/fsf-compat/auto-autoloads... Loading /<>/xemacs-packages/texinfo/auto-autoloads... Loading /<>/xemacs-packages/xemacs-base/auto-autoloads... Compiling /<>/xemacs-packages/auctex/style/frenchb.el... While compiling toplevel forms in file /<>/xemacs-packages/auctex/style/frenchb.el: ** reference to free variable TeX-quote-after-quote ** assignment to free variable TeX-quote-language While compiling the end of the data: ** The following functions are not known to be defined: TeX-add-style-hook, TeX-add-symbols Wrote /<>/xemacs-packages/auctex/style/frenchb.elc Done xemacs21-mule -no-autoloads -vanilla -batch -eval '(setq stack-trace-on-error t load-always-display-messages t load-ignore-out-of-date-elc-files t load-show-full-path-in-messages t)' -eval '(setq load-path (list (expand-file-name "mule" lisp-directory) lisp-directory))' -l /<>/package-compile.el -- xemacs-base texinfo fsf-compat mail-lib edit-utils -- -eval '(setq load-path (cons "." (cons "preview" load-path)))' -f batch-byte-compile style/francais.el Loading /usr/lib/xemacs-21.4.24/lisp/auto-autoloads... Loading /<>/xemacs-packages/edit-utils/auto-autoloads... Loading /<>/xemacs-packages/mail-lib/auto-autoloads... Loading /<>/xemacs-packages/fsf-compat/auto-autoloads... Loading /<>/xemacs-packages/texinfo/auto-autoloads... Loading /<>/xemacs-packages/xemacs-base/auto-autoloads... Compiling /<>/xemacs-packages/auctex/style/francais.el... While compiling the end of the data in file /<>/xemacs-packages/auctex/style/francais.el: ** The following functions are not known to be defined: TeX-add-style-hook, TeX-run-style-hooks Wrote /<>/xemacs-packages/auctex/style/francais.elc Done xemacs21-mule -no-autoloads -vanilla -batch -eval '(setq stack-trace-on-error t load-always-display-messages t load-ignore-out-of-date-elc-files t load-show-full-path-in-messages t)' -eval '(setq load-path (list (expand-file-name "mule" lisp-directory) lisp-directory))' -l /<>/package-compile.el -- xemacs-base texinfo fsf-compat mail-lib edit-utils -- -eval '(setq load-path (cons "." (cons "preview" load-path)))' -f batch-byte-compile style/MinionPro.el Loading /usr/lib/xemacs-21.4.24/lisp/auto-autoloads... Loading /<>/xemacs-packages/edit-utils/auto-autoloads... Loading /<>/xemacs-packages/mail-lib/auto-autoloads... Loading /<>/xemacs-packages/fsf-compat/auto-autoloads... Loading /<>/xemacs-packages/texinfo/auto-autoloads... Loading /<>/xemacs-packages/xemacs-base/auto-autoloads... Compiling /<>/xemacs-packages/auctex/style/MinionPro.el... While compiling toplevel forms in file /<>/xemacs-packages/auctex/style/MinionPro.el: ** reference to free variable TeX-install-font-lock ** reference to free variable font-latex-match-textual-keywords-local ** assignment to free variable font-latex-match-textual-keywords-local While compiling the end of the data: ** The following functions are not known to be defined: TeX-add-style-hook, TeX-add-symbols, font-latex-match-textual-make, font-latex-match-variable-make Wrote /<>/xemacs-packages/auctex/style/MinionPro.elc Done xemacs21-mule -no-autoloads -vanilla -batch -eval '(setq stack-trace-on-error t load-always-display-messages t load-ignore-out-of-date-elc-files t load-show-full-path-in-messages t)' -eval '(setq load-path (list (expand
Bug#1029438: marked as done (auctex: FTBFS in bookworm (LaTeX Error: File `pdftexcmds.sty' not found))
Your message dated Sun, 5 Feb 2023 20:28:02 +0100 with message-id <2355b938-ea8a-f9c9-504e-76af28445...@web.de> and subject line Closing has caused the Debian Bug report #1025985, regarding auctex: FTBFS in bookworm (LaTeX Error: File `pdftexcmds.sty' not found) 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.) -- 1025985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025985 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:auctex Version: 12.2-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules binary-indep /bin/bash: line 1: git: command not found /bin/bash: line 1: git: command not found dh binary-indep --exclude .eperl --with tex dh_update_autotools_config -i -O--exclude=.eperl dh_autoreconf -i -O--exclude=.eperl configure.ac:38: warning: The macro `AC_FD_CC' is obsolete. configure.ac:38: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:26: EMACS_PATH_PREFIX is expanded from... aclocal.m4:36: EMACS_PROG_EMACS is expanded from... configure.ac:38: the top level configure.ac:40: warning: The macro `AC_FD_CC' is obsolete. configure.ac:40: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:100: EMACS_CHECK_VERSION is expanded from... configure.ac:40: the top level configure.ac:44: warning: The macro `AC_FD_CC' is obsolete. configure.ac:44: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:494: VALID_BUILD_DIR is expanded from... lib/m4sugar/m4sh.m4:699: AS_IF is expanded from... ./lib/autoconf/general.m4:1534: AC_ARG_ENABLE is expanded from... configure.ac:44: the top level configure.ac:44: warning: The macro `AC_FD_CC' is obsolete. configure.ac:44: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:494: VALID_BUILD_DIR is expanded from... lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from... lib/m4sugar/m4sh.m4:699: AS_IF is expanded from... ./lib/autoconf/general.m4:1534: AC_ARG_ENABLE is expanded from... configure.ac:44: the top level configure.ac:60: warning: The macro `AC_FD_CC' is obsolete. configure.ac:60: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:126: EMACS_EXAMINE_INSTALLATION_DIR is expanded from... aclocal.m4:160: EMACS_PATH_LISPDIR is expanded from... configure.ac:60: the top level configure.ac:102: warning: The macro `AC_FD_CC' is obsolete. configure.ac:102: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:533: AC_LISPIFY_DIR is expanded from... configure.ac:102: the top level configure.ac:109: warning: The macro `AC_FD_CC' is obsolete. configure.ac:109: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:533: AC_LISPIFY_DIR is expanded from... configure.ac:109: the top level configure.ac:112: warning: The macro `AC_FD_CC' is obsolete. configure.ac:112: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:533: AC_LISPIFY_DIR is expanded from... configure.ac:112: the top level configure.ac:118: warning: The macro `AC_FD_CC' is obsolete. configure.ac:118: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:533: AC_LISPIFY_DIR is expanded from... configure.ac:118: the top level configure.ac:131: warning: The macro `AC_FD_CC' is obsolete. configure.ac:131: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... configure.ac:131: the top level configure.ac:152: warning: The macro `AC_FD_CC' is obsolete. configure.ac:152: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... aclocal.m4:13: EMACS_LISP is expanded from... aclocal.m4:26: EMACS_PATH_PREFIX is expanded from... aclocal.m4:185: TEX_PATH_TEXMFDIR is expanded from... configure.ac:152: the
Bug#1029460: marked as done (glosstex: FTBFS in bookworm (LaTeX Error: File `pdftexcmds.sty' not found))
Your message dated Sun, 5 Feb 2023 20:28:02 +0100 with message-id <2355b938-ea8a-f9c9-504e-76af28445...@web.de> and subject line Closing has caused the Debian Bug report #1025985, regarding glosstex: FTBFS in bookworm (LaTeX Error: File `pdftexcmds.sty' not found) 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.) -- 1025985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025985 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:glosstex Version: 0.4.dfsg.1-4 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules build-arch test -x debian/rules mkdir -p "." /usr/bin/make -C . CFLAGS="-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security" CXXFLAGS="-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro" make[1]: Entering directory '/<>' cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c -o database.o database.c cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c -o error.o error.c cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c -o labels.o labels.c cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c -o list.o list.c cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c -o main.o main.c cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c -o version.o version.c cc -Wl,-z,relro database.o error.o labels.o list.o main.o version.o -o glosstex TEXINPUTS=.: latex glosstex.ins This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Debian) (preloaded format=latex) restricted \write18 enabled. entering extended mode (./glosstex.ins LaTeX2e <2022-06-01> patch level 5 L3 programming layer <2022-08-30> (/usr/share/texlive/texmf-dist/tex/latex/base/docstrip.tex Utility: `docstrip' v2.6a <2020-11-23> English documentation<2020-11-23> ** * This program converts documented macro-files into fast * * loadable files by stripping off (nearly) all comments! * ** * No Configuration file found, using default settings. * (./glosstex.ins Generating file(s) ./glosstex.sty ./glosstex.std ./glosstex.ist ./glosstex.gdf ./glosstex.cfg Processing file glosstex.dtx (package) -> glosstex.sty (std) -> glosstex.std (ist) -> glosstex.ist (gdf) -> glosstex.gdf (cfg) -> glosstex.cfg File glosstex.dtx ended by \endinput. Lines processed: 1768 Comments removed: 1092 Comments passed: 16 Codelines passed: 646 ** * * You will find the documentation in glosstex.dvi. You may remake it * by running latex on glosstex.dtx or invoking `make doc' * * To finish the installation you have to move the following * files (according to TDS): * * glosstex.sty to texmf/tex/latex/glosstex * glosstex.std to texmf/tex/latex/glosstex * glosstex.ist to texmf/makeindex * * and your own .gdf-files to texmf/glosstex. * * The files `glosstex.gdf' and `glosstex.cfg` are meant just for * this document, so you won't want to install them, normally. * * Happy TeXing! ** ) ) ) No pages of output. Transcript written on glosstex.log. make[1]: Leaving directory '/<>' touch debian/stamp-makefile-build CDBS WARNING: DEB_MAKE_CHECK_TARGET unset, not running checks fakeroot debian/rules binary-arch test -x debian/rules dh_testroot dh_prep dh_installdirs -A dh_installdirs: warning: Compatibility levels before 10 are deprecated (level 9 in use) mkdir -p "." CDBS WARNING: DEB_MAKE_CHECK_TARGET unset, not running checks CDBS WARNING: DEB_MAKE_INSTALL_TARGET unset, skipping default makefile.mk common-inst
Bug#1025985: marked as done (hypdoc.sty requires pdftexcmds.sty that is in texlive-latex-extra)
Your message dated Sun, 5 Feb 2023 20:28:02 +0100
with message-id <2355b938-ea8a-f9c9-504e-76af28445...@web.de>
and subject line Closing
has caused the Debian Bug report #1025985,
regarding hypdoc.sty requires pdftexcmds.sty that is in texlive-latex-extra
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.)
--
1025985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025985
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glosstex
Version: 0.4.dfsg.1-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
Your package fails to build with:
|Writing index file glosstex.idx
|(/usr/share/texlive/texmf-dist/tex/latex/hypdoc/hypdoc.sty
|(/usr/share/texlive/texmf-dist/tex/latex/base/atveryend-ltx.sty)
|(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
|(/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty)
|(/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty)
|
|! LaTeX Error: File `pdftexcmds.sty' not found.
|
|Type X to quit or to proceed,
|or enter new name. (Default extension: sty)
|
|Enter file name:
|! Emergency stop.
|
|
|l.111 \RequirePackage{pdftexcmds}[2018/09/10]
| ^^M
|No pages of output.
|Transcript written on glosstex.log.
|make[1]: *** [Makefile:83: glosstex.dvi] Error 1
|make[1]: Leaving directory '/<>'
|make: *** [debian/rules:12: install/glosstex] Error 2
|dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess
returned exit status 2
The full build log is available from:
https://buildd.debian.org/status/fetch.php?pkg=glosstex&arch=riscv64&ver=0.4.dfsg.1-4%2Bb1&stamp=1670830203&raw=0
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/glosstex_0.4.dfsg.1-4.rbuild.log.gz
Regards
Aurelien
--- End Message ---
--- Begin Message ---
Version: 2022.20230122-1--- End Message ---
Bug#1030615: marked as done (opendht: FTBFS on mipsel: /usr/bin/ld: ../libopendht.a(dht_proxy_server.cpp.o): undefined reference to symbol '__atomic_exchange_8@@LIBATOMIC_1.0')
Your message dated Sun, 05 Feb 2023 19:20:22 + with message-id and subject line Bug#1030615: fixed in opendht 2.4.12-1.2 has caused the Debian Bug report #1030615, regarding opendht: FTBFS on mipsel: /usr/bin/ld: ../libopendht.a(dht_proxy_server.cpp.o): undefined reference to symbol '__atomic_exchange_8@@LIBATOMIC_1.0' 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.) -- 1030615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: opendht Version: 2.4.12-1.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) https://buildd.debian.org/status/fetch.php?pkg=opendht&arch=mipsel&ver=2.4.12-1.1&stamp=1675583004&raw=0 [ 91%] Built target perftest [ 94%] Linking CXX executable dhtchat cd /<>/obj-mipsel-linux-gnu/tools && /usr/bin/cmake -E cmake_link_script CMakeFiles/dhtchat.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-return-type -Wno-deprecated -Wall -Wextra -Wnon-virtual-dtor -pedantic-errors -fvisibility=hidden -DMSGPACK_NO_BOOST -DMSGPACK_DISABLE_LEGACY_NIL -DMSGPACK_DISABLE_LEGACY_CONVERT -Wl,-z,relro -Wl,-z,now CMakeFiles/dhtchat.dir/dhtchat.cpp.o -o dhtchat ../libopendht.a /usr/lib/mipsel-linux-gnu/libreadline.so -lncurses /usr/lib/mipsel-linux-gnu/libargon2.so /usr/lib/mipsel-linux-gnu/librt.a /usr/lib/mipsel-linux-gnu/libdl.a /usr/lib/mipsel-linux-gnu/libgnutls.so /usr/lib/mipsel-linux-gnu/libnettle.so /usr/lib/mipsel-linux-gnu/libfmt.so /usr/lib/mipsel-linux-gnu/libhttp_parser.so /usr/lib/mipsel-linux-gnu/libjsoncpp.so /usr/lib/mipsel-linux-gnu/libssl.so /usr/lib/mipsel-linux-gnu/libcrypto.so make[3]: Leaving directory '/<>/obj-mipsel-linux-gnu' [ 94%] Built target dhtchat [ 97%] Linking CXX executable dhtnode cd /<>/obj-mipsel-linux-gnu/tools && /usr/bin/cmake -E cmake_link_script CMakeFiles/dhtnode.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-return-type -Wno-deprecated -Wall -Wextra -Wnon-virtual-dtor -pedantic-errors -fvisibility=hidden -DMSGPACK_NO_BOOST -DMSGPACK_DISABLE_LEGACY_NIL -DMSGPACK_DISABLE_LEGACY_CONVERT -Wl,-z,relro -Wl,-z,now CMakeFiles/dhtnode.dir/dhtnode.cpp.o -o dhtnode ../libopendht.a /usr/lib/mipsel-linux-gnu/libreadline.so -lncurses /usr/lib/mipsel-linux-gnu/libargon2.so /usr/lib/mipsel-linux-gnu/librt.a /usr/lib/mipsel-linux-gnu/libdl.a /usr/lib/mipsel-linux-gnu/libgnutls.so /usr/lib/mipsel-linux-gnu/libnettle.so /usr/lib/mipsel-linux-gnu/libfmt.so /usr/lib/mipsel-linux-gnu/libhttp_parser.so /usr/lib/mipsel-linux-gnu/libjsoncpp.so /usr/lib/mipsel-linux-gnu/libssl.so /usr/lib/mipsel-linux-gnu/libcrypto.so /usr/bin/ld: ../libopendht.a(dht_proxy_server.cpp.o): undefined reference to symbol '__atomic_exchange_8@@LIBATOMIC_1.0' /usr/bin/ld: /usr/lib/mipsel-linux-gnu/libatomic.so.1: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status make[3]: *** [tools/CMakeFiles/dhtnode.dir/build.make:113: tools/dhtnode] Error 1 make[3]: Leaving directory '/<>/obj-mipsel-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:155: tools/CMakeFiles/dhtnode.dir/all] Error 2 make[2]: *** Waiting for unfinished jobs [100%] Linking CXX executable durl cd /<>/obj-mipsel-linux-gnu/tools && /usr/bin/cmake -E cmake_link_script CMakeFiles/durl.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-return-type -Wno-deprecated -Wall -Wextra -Wnon-virtual-dtor -pedantic-errors -fvisibility=hidden -DMSGPACK_NO_BOOST -DMSGPACK_DISABLE_LEGACY_NIL -DMSGPACK_DISABLE_LEGACY_CONVERT -Wl,-z,relro -Wl,-z,now CMakeFiles/durl.dir/durl.cpp.o -o durl ../libopendht.a /usr/lib/mipsel-linux-gnu/libreadline.so -lncurses /usr/lib/mipsel-linux-gnu/libargon2.so /usr/lib/mipsel-linux-gnu/librt.a /usr/lib/mipsel-linux-gnu/libdl.a /usr/lib/mipsel-linux-gnu/libgnutls.so /usr/lib/mipsel-linux-gnu/libnettle.so /usr/lib/mipsel-linux-gnu/libfmt.so /usr/lib/mipsel-linux-gnu/libhttp_parser.so /usr/lib/mipsel-linux-gnu/libjsoncpp.so /usr/lib/mipsel-linux-gnu/libssl.so /usr/lib/mipsel-linux-gnu/libcrypto.so make[3]: Leaving directory '/<>/obj-mipsel-linux-gnu' [100%] Built target durl make[2]: Leaving directory '/<>/obj-mipsel-linux-gnu' make[1]: *** [Makefile:139: all] Error
Bug#1030622: tex-common package post-installation script subprocess returned error exit status 1
Package: tex-common Version: 6.18 Severity: serious Dear Maintainer, I got this when upgrading texlive today in testing: > Paramétrage de tex-common (6.18) ... > Running mktexlsr. This may take some time... done. > Running mtxrun --generate. This may take some time... done. > Running updmap-sys. This may take some time... done. > Running mktexlsr /var/lib/texmf ... done. > Building format(s) --all. > This may take some time... > fmtutil failed. Output has been stored in > /tmp/fmtutil.RDPxpv93 > Please include this file if you report a bug. > > dpkg: erreur de traitement du paquet tex-common (--configure) : > installed tex-common package post-installation script subprocess returned > error exit status 1 > Des erreurs ont été rencontrées pendant l'exécution : > tex-common Attached is the file, as instructed. Cheers, -- Stéphane -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tex-common depends on: ii ucf 3.0043 tex-common recommends no packages. Versions of packages tex-common suggests: ii debhelper 13.11.4 Versions of packages texlive-base depends on: ii debconf [debconf-2.0] 1.5.82 ii libpaper-utils 1.1.28+b1 ii sensible-utils 0.0.17+nmu1 ii texlive-binaries 2022.20220321.62855-5 ii ucf3.0043 ii xdg-utils 1.1.3-4.1 Versions of packages texlive-base recommends: ii lmodern 2.005-1 Versions of packages texlive-base suggests: ii evince [postscript-viewer] 43.1-2+b1 ii ghostscript [postscript-viewer] 10.0.0~dfsg-9+b1 ii perl-tk 1:804.036-1+b1 ii xpdf [pdf-viewer]3.04+git20220601-1+b2 pn xzdec Versions of packages texlive-binaries depends on: ii libc6 2.36-8 ii libcairo2 1.16.0-7 ii libfontconfig1 2.14.1-3 ii libfreetype62.12.1+dfsg-4 ii libgcc-s1 12.2.0-14 ii libgraphite2-3 1.3.14-1 ii libharfbuzz0b 6.0.0-1 ii libicu7272.1-3 ii libkpathsea62022.20220321.62855-5 ii libmpfr64.2.0-1 ii libpaper1 1.1.28+b1 ii libpixman-1-0 0.42.2-1 ii libpng16-16 1.6.39-2 ii libptexenc1 2022.20220321.62855-5 ii libstdc++6 12.2.0-14 ii libsynctex2 2022.20220321.62855-5 ii libteckit0 2.5.11+ds1-1+b1 ii libtexlua53-5 2022.20220321.62855-5 ii libtexluajit2 2022.20220321.62855-5 ii libx11-62:1.8.3-3 ii libxaw7 2:1.0.14-1 ii libxi6 2:1.8-1+b1 ii libxmu6 2:1.1.3-3 ii libxpm4 1:3.5.12-1.1 ii libxt6 1:1.2.1-1 ii libzzip-0-130.13.72+dfsg.1-1.1 ii perl5.36.0-7 ii t1utils 1.41-4 ii zlib1g 1:1.2.13.dfsg-1 Versions of packages texlive-binaries recommends: pn dvisvgm ii texlive-base 2022.20221123-1 -- debconf information excluded fmtutil.RDPxpv93.xz Description: application/xz
Bug#1029594: Fails to authenticate mit o365
Carsten Schoenert wrote on 2/5/23 3:39 AM: > If you need your laptop or your workstation for mission critical > things than Debian unstable/sid isn't the right choice. If you do so > then you will need some knowledge to handle situations like happen > now.I'm not. The broken package has been released to testing already. In an ideal world I would have two separate computers but not everyone has ideal situations. testing release is good for my situation and have now added notifications of important bugs for apt-listbugs config as well, so thank you for mentioning that. However, that's not the default for users. > Debian doesn't have any really resilient statistics as such > statistics bases on completely free choice. Debian doesn't collect > data from users without any confirmation. Then why are you making assumptions on who the majority of users are? Such assertions require evidence, such as statistics. > Most users of Thunderbird are not using M$ products or at least only > using a small set of features of Exchange or Outlook.com. Again, how do you know this? guts or feelings are not valid sources of statistics. >> Further, the actual bug in mozilla is #1814536 (OAuth2 authentication >> | 102.7.1. | Linux - fails) - still Open. This is an even broader >> than just o365 as Google uses OAuth2 as well, etc. That bug was >> reported here in Debian as grave under #1030112 but you closed it as >> a duplicate of this bug. That was perhaps mistaken. > No, it was not. > Having dozen of issues open that are about the same problem is really > not helpful to handle the issue. Okay then, as long as you are certain. > I don't really understand your problem. What is the problem here? I'm just voicing my support for keeping the severity at serious while you keep insisting it should merely be important. > Even right now the the broken package will not migrate to testing. Why do you think that? How do you determine such? Is your system configured correct? It is literally listed in testing on packages.debian.org and available to be upgraded from 102.6. > But it will > also trigger a remove of the version in testing. What do we win? Maybe less bug reports? You seem to like that ;) I'm sure we all do. > My GMail account is working with the current version in testing means > to me that Google doesn't has changed something on their side. > Obviously only MS has changed something. Okay then, that's good. Maybe the report on Mozilla is wrong then, I don't know, I am just putting out there what I've found. > So finally again as written in other answers: If you need to use > Thunderbird in a critical environment you shouldn't use unstable/sid and again as I've said and as you should know, I/we are not, Thunderbird 102.7.1 has already been released to testing. > as long you don't know how to handle the potential breakage of > packages. Debian is providing a stable release for productive use, if > you need newer version of software you can add the backport suite. Most of us should already know that. I too just want to help others not have to spend time fixing things that can be prevented with a good severity label. I have a system with stable, backports, testing, experimental, unstable, and snapshots repos working fine, for now... ;)
Bug#1030409: marked as done (precious: FTBFS: build-dependency not installable: librust-test-case-2+default-dev)
Your message dated Sun, 05 Feb 2023 19:53:57 +0100 with message-id <167562323712.1735478.14613972050470450...@auryn.jones.dk> and subject line Re: Bug#1030409: precious: FTBFS: build-dependency not installable: librust-test-case-2+default-dev has caused the Debian Bug report #1030409, regarding precious: FTBFS: build-dependency not installable: librust-test-case-2+default-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.) -- 1030409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: precious Version: 0.4.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230203 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: cmark-gfm, debhelper-compat (= 13), dh-cargo, git, > help2man, librust-anyhow-1+default-dev (>= 1.0.66), librust-clap-3+cargo-dev, > librust-clap-3+default-dev, librust-clap-3+derive-dev, > librust-env-logger-0.9+default-dev, librust-fern+colored-dev (<< 7), > librust-fern+default-dev (<< 7), librust-filetime-0.2+default-dev (>= > 0.2.18), librust-globset-0.4+default-dev (>= 0.4.9), > librust-ignore-0.4+default-dev (>= 0.4.18), librust-indexmap-1+default-dev > (>= 1.9.1), librust-indexmap-1+serde-dev (>= 1.9.1), > librust-itertools+default-dev (<< 0.11), librust-log-0.4+default-dev (>= > 0.4.17), librust-md5-0.7+default-dev, librust-once-cell-1+default-dev (>= > 1.16), librust-pathdiff-0.2+default-dev, > librust-pretty-assertions-1+default-dev (>= 1.3), librust-rayon-1+default-dev > (>= 1.5.3), librust-regex-1+default-dev (>= 1.7), librust-serde-1+default-dev > (>= 1.0.147), librust-serde-1+derive-dev (>= 1.0.147), > librust-serial-test-0.9+default-dev, librust-tempfile-3+default-dev (>= 3.3), > librust-test-case-2+default-dev, librust-thiserror-1+default-dev (>= 1.0.37), > librust-toml-0.5+default-dev (>= 0.5.9), librust-which+default-dev (<< 5), > libstring-shellquote-perl, build-essential, fakeroot > Filtered Build-Depends: cmark-gfm, debhelper-compat (= 13), dh-cargo, git, > help2man, librust-anyhow-1+default-dev (>= 1.0.66), librust-clap-3+cargo-dev, > librust-clap-3+default-dev, librust-clap-3+derive-dev, > librust-env-logger-0.9+default-dev, librust-fern+colored-dev (<< 7), > librust-fern+default-dev (<< 7), librust-filetime-0.2+default-dev (>= > 0.2.18), librust-globset-0.4+default-dev (>= 0.4.9), > librust-ignore-0.4+default-dev (>= 0.4.18), librust-indexmap-1+default-dev > (>= 1.9.1), librust-indexmap-1+serde-dev (>= 1.9.1), > librust-itertools+default-dev (<< 0.11), librust-log-0.4+default-dev (>= > 0.4.17), librust-md5-0.7+default-dev, librust-once-cell-1+default-dev (>= > 1.16), librust-pathdiff-0.2+default-dev, > librust-pretty-assertions-1+default-dev (>= 1.3), librust-rayon-1+default-dev > (>= 1.5.3), librust-regex-1+default-dev (>= 1.7), librust-serde-1+default-dev > (>= 1.0.147), librust-serde-1+derive-dev (>= 1.0.147), > librust-serial-test-0.9+default-dev, librust-tempfile-3+default-dev (>= 3.3), > librust-test-case-2+default-dev, librust-thiserror-1+default-dev (>= 1.0.37), > librust-toml-0.5+default-dev (>= 0.5.9), librust-which+default-dev (<< 5), > libstring-shellquote-perl, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [717 B] > Get:5 copy:/<>/apt_archive ./ Packages [788 B] > Fetched 2468 B in 0s (124 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help
Bug#1028862: marked as done (xorg-gtest: FTBFS: dh_auto_test: error: make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2)
Your message dated Sun, 05 Feb 2023 18:41:35 + with message-id and subject line Bug#1030548: Removed package(s) from unstable has caused the Debian Bug report #1028862, regarding xorg-gtest: FTBFS: dh_auto_test: error: make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1028862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xorg-gtest Version: 0.7.1-8 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230113 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[5]: Entering directory '/<>/examples' > FAIL: xorg-gtest-environment-example > PASS: xorg-gtest-example > == >X.org Testing Environment for Google Test 0.7.1: examples/test-suite.log > == > > # TOTAL: 2 > # PASS: 1 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: xorg-gtest-environment-example > > > [==] Running 6 tests from 2 test cases. > [--] Global test environment set-up. > [--] 5 tests from Test > [ RUN ] Test.DummyXorgServerTest > [ OK ] Test.DummyXorgServerTest (1 ms) > [ RUN ] Test.XIQueryVersion20 > unknown file: Failure > C++ exception with description "Failed to open connection to display. > This usually means that your X server did not start properly. > Check the log file, or set XORG_GTEST_CHILD_STDOUT to see the server's > error messages when starting." thrown in SetUp(). > [ FAILED ] Test.XIQueryVersion20 (1 ms) > [ RUN ] Test.XIQueryVersion22 > [ OK ] Test.XIQueryVersion22 (42 ms) > [ RUN ] Test.CreateWindowProperty > [ OK ] Test.CreateWindowProperty (42 ms) > [ RUN ] Test.CheckWindowProperty > [ OK ] Test.CheckWindowProperty (55 ms) > [--] 5 tests from Test (141 ms total) > > [--] 1 test from SubTest > [ RUN ] SubTest.ExampleAtom > [ OK ] SubTest.ExampleAtom (43 ms) > [--] 1 test from SubTest (43 ms total) > > [--] Global test environment tear-down > Warning: Failed to terminate Xorg server: Success > [==] 6 tests from 2 test cases ran. (1277 ms total) > [ PASSED ] 5 tests. > [ FAILED ] 1 test, listed below: > [ FAILED ] Test.XIQueryVersion20 > > 1 FAILED TEST > FAIL xorg-gtest-environment-example (exit status: 1) > > > Testsuite summary for X.org Testing Environment for Google Test 0.7.1 > > # TOTAL: 2 > # PASS: 1 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > See examples/test-suite.log > > make[5]: *** [Makefile:869: test-suite.log] Error 1 > make[5]: Leaving directory '/<>/examples' > make[4]: *** [Makefile:977: check-TESTS] Error 2 > make[4]: Leaving directory '/<>/examples' > make[3]: *** [Makefile:1057: check-am] Error 2 > make[3]: Leaving directory '/<>/examples' > make[2]: *** [Makefile:464: check-recursive] Error 1 > make[2]: Leaving directory '/<>' > dh_auto_test: error: make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 > returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2023/01/13/xorg-gtest_0.7.1-8_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230113;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230113&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant ch
Bug#1019914: marked as done (Useless in Debian)
Your message dated Sun, 05 Feb 2023 18:41:05 + with message-id and subject line Bug#1021589: Removed package(s) from unstable has caused the Debian Bug report #1019914, regarding Useless in Debian 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.) -- 1019914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019914 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: adldap2 Severity: serious [ Reported by a team member to see the package removed from testing ] adldap2 will be deprecated in favor of LdapRecord (https://github.com/DirectoryTree/LdapRecord), and I don't see a use case any more at the moment. No packages depend on it, so it can be removed from testing easily. Regards Katharina -- --- End Message --- --- Begin Message --- Version: 10.4.1-1.1+rm Dear submitter, as the package adldap2 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1021589 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1029136: MariaDB configuration files not properly migrated on switch to unversioned packages
> > This is now solved on > > https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/31 > > Mangling the maintainers scripts of another package is a delicate issue > as it's often fragile and can cause hard to debug failures in corner cases. > > Personally, I would have turned the versioned packages into empty > transitional packages. This would have made the upgrade process much > smoother and avoided this issue altogether (the new empty versioned > packages would have no maintainer scripts). > It's also common practice for such use cases. > > Any reason why you didn't consider this approach? I did write the code for empty packages and tested it (as visible in the merge request above) but it would have created much more moving parts and failures elsewhere. Fixing the maintainer scripts proved to be the most elegant solution.
Bug#1030530: python3.10 should not be in bookworm
Package: python3.10 Followup-For: Bug #1030530 Perhaps a strange or seemingly off-topic question, but: is it fair to assume that Python 3.11's improved (typical) performance characteristics should likely result in similar-scale energy consumption reductions? (I'd be likely, although cannot guarantee, to offer assistance -- outside of the Debian project and packaging process -- upstream to DFSG-compatible Python packages that would consider Debian's removal of Python 3.10 from bookworm a blocker, depending on the circumstances and my own capacity and willingness to help)
Bug#1029136: MariaDB configuration files not properly migrated on switch to unversioned packages
Hi Otto Am 05.02.23 um 17:55 schrieb Otto Kekäläinen: This is now solved on https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/31 Mangling the maintainers scripts of another package is a delicate issue as it's often fragile and can cause hard to debug failures in corner cases. Personally, I would have turned the versioned packages into empty transitional packages. This would have made the upgrade process much smoother and avoided this issue altogether (the new empty versioned packages would have no maintainer scripts). It's also common practice for such use cases. Any reason why you didn't consider this approach? Regards, Michael OpenPGP_signature Description: OpenPGP digital signature
Bug#1030545: qemu: qemu-img and qemu-system-s390x hang on s390x
So, many previous versions behave the same, including bullseye. However. 1. I was able to create a 512-bytes qcow2 file once in /home/mjt on zelenka. And. 2. All versions always work fine in /tmp, on a tmpfs. Is it possible that the tests were running on a tmpfs before? /mjt
Processed: Re: Bug#1030545: qemu: qemu-img and qemu-system-s390x hang on s390x
Processing control commands: > tag -1 + help Bug #1030545 [src:qemu] qemu: qemu-img and qemu-system-s390x hang on s390x Added tag(s) help. > found -1 1:5.2+dfsg-11+deb11u2 Bug #1030545 [src:qemu] qemu: qemu-img and qemu-system-s390x hang on s390x Marked as found in versions qemu/1:5.2+dfsg-11+deb11u2. -- 1030545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030545: qemu: qemu-img and qemu-system-s390x hang on s390x
Control: tag -1 + help Control: found -1 1:5.2+dfsg-11+deb11u2 05.02.2023 20:30, Michael Tokarev wrote: .. The thing is: I can't find *any* working version of qemu-img, they all hang like described. This includes 1:7.2+dfsg-1+b1 too. There's more: I installed bullseye on zelenka, and tried this qemu-img command there (1:5.2+dfsg-11+deb11u2). It hangs exactly the same way. So it looks like this problem has been there for a very long time and no one noticed it. I don't know if qemu-system-s390x hang is due to this or different, - probably different issue. Now I need a reproducer for qemu-system-s390x hang :) /mjt
Bug#1030483: marked as done (beginend-el: FTBFS: error: (file-missing (lambda (arg72 &rest arg73) (let ((f #'message)) (apply f arg72 arg73))) "Setting current directory" "No such file or directory" "
Your message dated Sun, 05 Feb 2023 17:49:31 + with message-id and subject line Bug#1030483: fixed in beginend-el 2.3.0+git20220902.c8fe2cd-1 has caused the Debian Bug report #1030483, regarding beginend-el: FTBFS: error: (file-missing (lambda (arg72 &rest arg73) (let ((f #'message)) (apply f arg72 arg73))) "Setting current directory" "No such file or directory" "/tmp/temp-fs-MQAR3w") 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.) -- 1030483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: beginend-el Version: 2.3.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230203 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 '/<>' > skipping upstream build > make[1]: Leaving directory '/<>' >dh_elpa_test > buttercup -L . > Loading /etc/emacs/site-start.d/00debian.el (source)... > Loading /etc/emacs/site-start.d/50autoconf.el (source)... > Loading /<>/test/test-helper.el (source)... > Loading /<>/test/test-helper.el (source)... > Loading /<>/test/test-helper.el (source)... > Loading /<>/test/test-helper.el (source)... > Loading /<>/test/test-helper.el (source)... > Running 40 specs. > > beginend in a dired buffer > ignores . and .. at the beginningMark set > > [32m ignores . and .. at the beginning[0m (37.46ms) > ignores . and .. at the endMark set > > [32m ignores . and .. at the end[0m (7.07ms) > ignores . at the beginning and .. at the endMark set > > [32m ignores . at the beginning and .. at the end[0m (6.98ms) > ignores . and .. in the middleMark set > > [32m ignores . and .. in the middle[0m (6.22ms) > ignores . and .. when they are hiddenMark set > > [32m ignores . and .. when they are hidden[0m (5.17ms) > ignores . and .. when they are not hiddenMark set > > [32m ignores . and .. when they are not hidden[0m (10.38ms) > ignores . and .. when they are hidden and the directory is emptyMark set > > [32m ignores . and .. when they are hidden and the directory is empty[0m > (4.45ms) > ignores . and .. when they are not hidden and the directory is emptyMark set > > [32m ignores . and .. when they are not hidden and the directory is > empty[0m (4.19ms) > > beginend > pushes mark > when going to beginning > if point is not at beginningMark set > > [31m if point is not at beginning[0m[31m FAILED[0m (71.18ms) > only onceMark set > > [31m only once[0m[31m FAILED[0m (38.91ms) > when going to end > if point is not at endMark set > > [31m if point is not at end[0m[31m FAILED[0m (26.99ms) > only onceMark set > > [31m only once[0m[31m FAILED[0m (25.86ms) > does not push mark > when going to beginning > if point is already at beginning > [31m if point is already at beginning[0m[31m FAILED[0m (3.40ms) > if point is at point-min > [31m if point is at point-min[0m[31m FAILED[0m (25.63ms) > when going to end > if point is already at end > [31m if point is already at end[0m[31m FAILED[0m (25.09ms) > if point is at point-max > [31m if point is at point-max[0m[31m FAILED[0m (26.64ms) > > beginend, when narrowing is active, > goes to point-min if beginning is outside the narrowed region > [31m goes to point-min if beginning is outside the narrowed region[0m[31m > FAILED[0m (3.86ms) > goes to beginning if beginning is inside the narrowed regionMark set > > [31m goes to beginning if beginning is inside the narrowed region[0m[31m > FAILED[0m (24.96ms) > goes to point-max if end is outside the narrowed region > [31m goes to point-max if end is outside the narrowed region[0m[31m > FAILED[0m (25.26ms) > goes to end if end is inside the narrowed region > [31m goes to end if end is inside the narrowed region[0m[31m FAILED[0m > (29.04ms) > does not move point > when going to beginning and beginning outside the narrowed region if > point is already at point-min > [31mwhen going to beginning and beginning outside the narrowed region if > point is already at point-min[0m[31m FAILED[0m (3.46ms) > when going to end and end outside the narrowed region if point is already > at point-max > [31mwhen going to end and end outside the narrowed region if point is > already at point-max[0m[31m FAILED[0m (26.75ms) > d
Bug#1030545: qemu: qemu-img and qemu-system-s390x hang on s390x
04.02.2023 23:48, Hilko Bengen wrote: .. Does 7.2+dfsg-1 work? I don't have s390x environment so have no way to deal with this one. No, it doesn't. On the porterbox (zelenka.debian.org) I was only able to install 1:7.2+dfsg-1+b1 without rebuilding. Oh, I forgot about zelenka. Tried that one yesterday. The last non-failing build before[1] also used 1:7.2+dfsg-1+b1, though. This made me think that the hang might be related to a shared library that had been updated since. It is interesting. On zelenka, I can run older versions of qemu-utils, from up to version 6.2 (haven't tried older, - it refer to older versions of liburing and libnettle). I d'loaded the .deb file from snapshot.d.o, extracted it in a local dir and run qemu-img from there. The thing is: I can't find *any* working version of qemu-img, they all hang like described. This includes 1:7.2+dfsg-1+b1 too. So I really wonder if it worked before. I also tried with a few versions of glibc, - also extracting them into a local folder and running with LD_LIBRARY_PATH pointing to it, -- the same issue, qemu-img hangs. [1] https://buildd.debian.org/status/logs.php?pkg=libguestfs&arch=s390x yet, libguestfs definitely worked before. Do we perhaps have something else which broke in between? But I really wonder how it happen that 1:7.2+dfsg-1+b1 worked, and I can't reproduce it :) I'm about to add "found: 6.2" tag to this one :)) /mjt
Bug#1030530: Python 3.10 in bookworm
On Sun, Feb 05, 2023 at 02:41:08PM +, Stefano Rivera wrote: > Hi Julian (2023.02.05_10:38:23_+) > > > Why is the current intention not to ship the python3.10 package in > > bookworm? > > Because we aim to have a single Python release supported in every stable > release. I am not suggesting that we revert to having Python 3.10 as a "supported version" (that would be a whole separate discussion); I am suggesting that we keep just the Python 3.10 interpreter and python3.10-venv in bookworm, so that users can use it to run a virtual environment if they need to do so. > > I was trying to run some experiments in a virtual environment a few > > days ago, and it turns out that several of the Python packages I > > needed do not yet run on Python 3.11. I was saved by being able to > > run in a Python 3.10 venv and download all the required packages from > > PyPI. If bookworm shipped without python3.10, I would not have been > > able to do my work. Removing python3.10 from bookworm will seriously > > affect many of our users in a similar situation to me. > > By the time bookworm releases, that probably won't be the case any more. I honestly don't know if that will be the case or not; some packages will be much slower to adapt than others. That's why I'm suggesting we leave the python3.10 and python3.10-venv packages in bookworm. > But anything that gets removed from Debian, because it isn't ready yet > obviously gets hurt in the process... I'm not sure what you mean here? Best wishes, Julian
Bug#1030615: opendht: FTBFS on mipsel: /usr/bin/ld: ../libopendht.a(dht_proxy_server.cpp.o): undefined reference to symbol '__atomic_exchange_8@@LIBATOMIC_1.0'
Source: opendht Version: 2.4.12-1.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) https://buildd.debian.org/status/fetch.php?pkg=opendht&arch=mipsel&ver=2.4.12-1.1&stamp=1675583004&raw=0 [ 91%] Built target perftest [ 94%] Linking CXX executable dhtchat cd /<>/obj-mipsel-linux-gnu/tools && /usr/bin/cmake -E cmake_link_script CMakeFiles/dhtchat.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-return-type -Wno-deprecated -Wall -Wextra -Wnon-virtual-dtor -pedantic-errors -fvisibility=hidden -DMSGPACK_NO_BOOST -DMSGPACK_DISABLE_LEGACY_NIL -DMSGPACK_DISABLE_LEGACY_CONVERT -Wl,-z,relro -Wl,-z,now CMakeFiles/dhtchat.dir/dhtchat.cpp.o -o dhtchat ../libopendht.a /usr/lib/mipsel-linux-gnu/libreadline.so -lncurses /usr/lib/mipsel-linux-gnu/libargon2.so /usr/lib/mipsel-linux-gnu/librt.a /usr/lib/mipsel-linux-gnu/libdl.a /usr/lib/mipsel-linux-gnu/libgnutls.so /usr/lib/mipsel-linux-gnu/libnettle.so /usr/lib/mipsel-linux-gnu/libfmt.so /usr/lib/mipsel-linux-gnu/libhttp_parser.so /usr/lib/mipsel-linux-gnu/libjsoncpp.so /usr/lib/mipsel-linux-gnu/libssl.so /usr/lib/mipsel-linux-gnu/libcrypto.so make[3]: Leaving directory '/<>/obj-mipsel-linux-gnu' [ 94%] Built target dhtchat [ 97%] Linking CXX executable dhtnode cd /<>/obj-mipsel-linux-gnu/tools && /usr/bin/cmake -E cmake_link_script CMakeFiles/dhtnode.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-return-type -Wno-deprecated -Wall -Wextra -Wnon-virtual-dtor -pedantic-errors -fvisibility=hidden -DMSGPACK_NO_BOOST -DMSGPACK_DISABLE_LEGACY_NIL -DMSGPACK_DISABLE_LEGACY_CONVERT -Wl,-z,relro -Wl,-z,now CMakeFiles/dhtnode.dir/dhtnode.cpp.o -o dhtnode ../libopendht.a /usr/lib/mipsel-linux-gnu/libreadline.so -lncurses /usr/lib/mipsel-linux-gnu/libargon2.so /usr/lib/mipsel-linux-gnu/librt.a /usr/lib/mipsel-linux-gnu/libdl.a /usr/lib/mipsel-linux-gnu/libgnutls.so /usr/lib/mipsel-linux-gnu/libnettle.so /usr/lib/mipsel-linux-gnu/libfmt.so /usr/lib/mipsel-linux-gnu/libhttp_parser.so /usr/lib/mipsel-linux-gnu/libjsoncpp.so /usr/lib/mipsel-linux-gnu/libssl.so /usr/lib/mipsel-linux-gnu/libcrypto.so /usr/bin/ld: ../libopendht.a(dht_proxy_server.cpp.o): undefined reference to symbol '__atomic_exchange_8@@LIBATOMIC_1.0' /usr/bin/ld: /usr/lib/mipsel-linux-gnu/libatomic.so.1: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status make[3]: *** [tools/CMakeFiles/dhtnode.dir/build.make:113: tools/dhtnode] Error 1 make[3]: Leaving directory '/<>/obj-mipsel-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:155: tools/CMakeFiles/dhtnode.dir/all] Error 2 make[2]: *** Waiting for unfinished jobs [100%] Linking CXX executable durl cd /<>/obj-mipsel-linux-gnu/tools && /usr/bin/cmake -E cmake_link_script CMakeFiles/durl.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-return-type -Wno-deprecated -Wall -Wextra -Wnon-virtual-dtor -pedantic-errors -fvisibility=hidden -DMSGPACK_NO_BOOST -DMSGPACK_DISABLE_LEGACY_NIL -DMSGPACK_DISABLE_LEGACY_CONVERT -Wl,-z,relro -Wl,-z,now CMakeFiles/durl.dir/durl.cpp.o -o durl ../libopendht.a /usr/lib/mipsel-linux-gnu/libreadline.so -lncurses /usr/lib/mipsel-linux-gnu/libargon2.so /usr/lib/mipsel-linux-gnu/librt.a /usr/lib/mipsel-linux-gnu/libdl.a /usr/lib/mipsel-linux-gnu/libgnutls.so /usr/lib/mipsel-linux-gnu/libnettle.so /usr/lib/mipsel-linux-gnu/libfmt.so /usr/lib/mipsel-linux-gnu/libhttp_parser.so /usr/lib/mipsel-linux-gnu/libjsoncpp.so /usr/lib/mipsel-linux-gnu/libssl.so /usr/lib/mipsel-linux-gnu/libcrypto.so make[3]: Leaving directory '/<>/obj-mipsel-linux-gnu' [100%] Built target durl make[2]: Leaving directory '/<>/obj-mipsel-linux-gnu' make[1]: *** [Makefile:139: all] Error 2 make[1]: Leaving directory '/<>/obj-mipsel-linux-gnu' dh_auto_build: error: cd obj-mipsel-linux-gnu && make -j4 "INSTALL=install --strip-program=true" VERBOSE=1 returned exit code 2 make: *** [debian/rules:19: binary-arch] Error 25 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 Cheers -- Sebastian Ramacher
Bug#1028720: marked as done (wss4j: FTBFS: [ERROR] Failed to execute goal on project wss4j: Could not resolve dependencies for project org.apache.ws.security:wss4j:bundle:1.6.19: Cannot access central
Your message dated Sun, 05 Feb 2023 16:52:39 + with message-id and subject line Bug#1028720: fixed in wss4j 1.6.19-3 has caused the Debian Bug report #1028720, regarding wss4j: FTBFS: [ERROR] Failed to execute goal on project wss4j: Could not resolve dependencies for project org.apache.ws.security:wss4j:bundle:1.6.19: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact log4j:log4j:jar:1.2.x has not been downloaded from it before. -> [Help 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.) -- 1028720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wss4j Version: 1.6.19-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230113 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=maven >dh_update_autotools_config -O--buildsystem=maven >dh_autoreconf -O--buildsystem=maven >dh_auto_configure -O--buildsystem=maven > mh_patchpoms -plibwss4j-java --debian-build --keep-pom-version > --maven-repo=/<>/debian/maven-repo >dh_auto_build -O--buildsystem=maven > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US > OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were > deprecated in JDK 13 and will likely be removed in a future release. > [0m[0m[INFO] Scanning for projects... > [INFO] > [INFO] < org.apache.ws.security:wss4j > > > [INFO] Building Apache WSS4J 1.6.19 > [INFO] ---[ bundle > ]--- > [WARNING] The POM for log4j:log4j:jar:1.2.x is missing, no dependency > information available > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 0.591 s > [INFO] Finished at: 2023-01-13T20:28:28Z > [INFO] > > [ERROR] Failed to execute goal on project wss4j: Could not resolve > dependencies for project org.apache.ws.security:wss4j:bundle:1.6.19: Cannot > access central (https://repo.maven.apache.org/maven2) in offline mode and the > artifact log4j:log4j:jar:1.2.x has not been downloaded from it before. -> > [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException > [0m[0mdh_auto_build: error: /usr/lib/jvm/default-java/bin/java -noverify > -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1 > make: *** [debian/rules:4: build] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/01/13/wss4j_1.6.19-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230113;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230113&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribut
Bug#1029136: MariaDB configuration files not properly migrated on switch to unversioned packages
This is now solved on https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/31
Processed: openlibm: diff for NMU version 0.8.1+dfsg-2.1
Processing control commands:
> tags 1020617 + patch
Bug #1020617 {Done: Paul Gevers } [src:openlibm]
src:openlibm: fails to migrate to testing for too long: FTBFS on armhf and
mips64el
Added tag(s) patch.
--
1020617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1020617: openlibm: diff for NMU version 0.8.1+dfsg-2.1
Control: tags 1020617 + patch Dear maintainer, I've prepared an NMU for openlibm (versioned as 0.8.1+dfsg-2.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru openlibm-0.8.1+dfsg/debian/changelog openlibm-0.8.1+dfsg/debian/changelog --- openlibm-0.8.1+dfsg/debian/changelog 2022-07-24 22:44:28.0 +0300 +++ openlibm-0.8.1+dfsg/debian/changelog 2023-02-05 18:38:54.0 +0200 @@ -1,3 +1,10 @@ +openlibm (0.8.1+dfsg-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Unset MARCH during build and test. (Closes: #1020617) + + -- Adrian Bunk Sun, 05 Feb 2023 18:38:54 +0200 + openlibm (0.8.1+dfsg-2) unstable; urgency=medium * Upload to unstable. diff -Nru openlibm-0.8.1+dfsg/debian/rules openlibm-0.8.1+dfsg/debian/rules --- openlibm-0.8.1+dfsg/debian/rules 2022-06-18 23:51:10.0 +0300 +++ openlibm-0.8.1+dfsg/debian/rules 2023-02-05 18:38:49.0 +0200 @@ -6,5 +6,11 @@ %: dh $@ +override_dh_auto_build: + dh_auto_build -- MARCH="" + +override_dh_auto_test: + dh_auto_test -- MARCH="" + override_dh_auto_install: dh_auto_install -- "CC=$(CC)" prefix=/usr
Processed: Bug#1028720 marked as pending in wss4j
Processing control commands: > tag -1 pending Bug #1028720 [src:wss4j] wss4j: FTBFS: [ERROR] Failed to execute goal on project wss4j: Could not resolve dependencies for project org.apache.ws.security:wss4j:bundle:1.6.19: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact log4j:log4j:jar:1.2.x has not been downloaded from it before. -> [Help 1] Added tag(s) pending. -- 1028720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028720: marked as pending in wss4j
Control: tag -1 pending Hello, Bug #1028720 in wss4j 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/java-team/wss4j/-/commit/3f2c258f8da61894fa5bb310c4bedb70e16ab2f2 Add build-dep on liblog4j1.2-java (Closes: #1028720) (this message was generated automatically) -- Greetings https://bugs.debian.org/1028720
Bug#1027965: Fix for the RC bug in vtk
Hi Steven. thanks for the notice! vtk9 upload is in my todo list for the next few days. Regards Anton Am So., 5. Feb. 2023 um 17:30 Uhr schrieb Steven Robbins : > > Hello, > > Was looking yesterday for an RC bug to fix and noticed #1027965 against VTK -- > a build failure in gdcm caused by missing dependency. The fix proposed by > Mathieu seems reasonable to me. > > Anton: I'm writing to ask your opinion about the commits in salsa since the > last upload (June 2022); specifically, do you feel they are suitable for > inclusion now? > > Should I: > > 1. apply the patch to the lastest in salsa? > 2. apply the patch to the last upload sources ignoring salsa? > 3. leave it alone and let you deal with it? > 4. something else? > > Appreciate your insight. > -Steve
Bug#1027965: Fix for the RC bug in vtk
Hello, Was looking yesterday for an RC bug to fix and noticed #1027965 against VTK -- a build failure in gdcm caused by missing dependency. The fix proposed by Mathieu seems reasonable to me. Anton: I'm writing to ask your opinion about the commits in salsa since the last upload (June 2022); specifically, do you feel they are suitable for inclusion now? Should I: 1. apply the patch to the lastest in salsa? 2. apply the patch to the last upload sources ignoring salsa? 3. leave it alone and let you deal with it? 4. something else? Appreciate your insight. -Steve signature.asc Description: This is a digitally signed message part.
Processed: owner 1028720
Processing commands for cont...@bugs.debian.org: > owner 1028720 ! Bug #1028720 [src:wss4j] wss4j: FTBFS: [ERROR] Failed to execute goal on project wss4j: Could not resolve dependencies for project org.apache.ws.security:wss4j:bundle:1.6.19: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact log4j:log4j:jar:1.2.x has not been downloaded from it before. -> [Help 1] Owner recorded as tony mancill . > thanks Stopping processing here. Please contact me if you need assistance. -- 1028720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
