Bug#994269: marked as done (node-jest/experimental FTBFS: build hang)
Your message dated Sun, 26 Sep 2021 04:50:22 + with message-id and subject line Bug#994269: fixed in node-jest 27.2.1~ds+~cs67.45.24-1 has caused the Debian Bug report #994269, regarding node-jest/experimental FTBFS: build hang 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.) -- 994269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994269 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-jest Version: 27.1.0~ds+~cs67.45.23-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/experimental/amd64/node-jest.html https://buildd.debian.org/status/package.php?p=node-jest=experimental ... dh_auto_build --buildsystem=nodejs Found debian/nodejs/additional_components Adding component(s): packages/babel-jest, packages/babel-plugin-jest-hoist, packages/babel-preset-jest, packages/diff-sequences, packages/expect, packages/jest, packages/jest-changed-files, packages/jest-circus, packages/jest-cli, packages/jest-config, packages/jest-console, packages/jest-core, packages/jest-create-cache-key-function, packages/jest-diff, packages/jest-docblock, packages/jest-each, packages/jest-environment, packages/jest-environment-jsdom, packages/jest-environment-node, packages/jest-fake-timers, packages/jest-get-type, packages/jest-globals, packages/jest-haste-map, packages/jest-jasmine2, packages/jest-leak-detector, packages/jest-matcher-utils, packages/jest-message-util, packages/jest-mock, packages/jest-phabricator, packages/jest-regex-util, packages/jest-repl, packages/jest-reporters, packages/jest-resolve, packages/jest-resolve-dependencies, packages/jest-runner, packages/jest-runtime, packages/jest-serializer, packages/jest-snapshot, packages/jest-source-map, packages/jest-test-result, packages/jest-test-sequencer, packages/jest-transform, packages/jest-types, packages/jest-util, packages/jest-validate, packages/jest-watcher, packages/jest-worker, packages/pretty-format, packages/test-utils No build command found, searching known files No build command found, searching known files Found debian/nodejs/bcoe-v8-coverage/build cd ./bcoe-v8-coverage && sh -ex ../debian/nodejs/bcoe-v8-coverage/build + rm -rf dist + mkdir node_modules + ln -s /usr/share/nodejs/tslib node_modules/ + mkdir -p node_modules/@types + ln -s /usr/share/nodejs/@types/mocha node_modules/@types/ + rollup -c ../debian/bcoe-rollup-config.js ../bcoe-v8-coverage/src/lib/index.ts → ../bcoe-v8-coverage/dist/lib... (!) Plugin typescript: @rollup/plugin-typescript: Rollup 'sourcemap' option must be set to generate source maps. created ../bcoe-v8-coverage/dist/lib in 3s E: Build killed with signal TERM after 150 minutes of inactivity --- End Message --- --- Begin Message --- Source: node-jest Source-Version: 27.2.1~ds+~cs67.45.24-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-jest, 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 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-jest 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, 26 Sep 2021 06:30:11 +0200 Source: node-jest Architecture: source Version: 27.2.1~ds+~cs67.45.24-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 994269 Changes: node-jest (27.2.1~ds+~cs67.45.24-1) experimental; urgency=medium . * New upstream version 27.2.1~ds+~cs67.45.24 (Closes: #994269) * Unfuzz patches * Update typescript workaround patch * Update lintian overrides * node-debbundle-jest depends on node-babel-plugin-lodash Checksums-Sha1: 95b3b618c6a853ea06dbb4fb619b4ecf3c97db39 11286 node-jest_27.2.1~ds+~cs67.45.24-1.dsc 5e2b6b2574330b67f817f5c7cfb6e85e67ea4b49 2576 node-jest_27.2.1~ds+~cs67.45.24.orig-astral-regex.tar.xz 8afa646c9ae53bb545541ab3113cae36671de509 8924 node-jest_27.2.1~ds+~cs67.45.24.orig-babel-preset-moxy.tar.xz 8e0cbe207c3fd77bb11c1b586c3d4a1dce733c9a 13760 node-jest_27.2.1~ds+~cs67.45.24.orig-bcoe-v8-coverage.tar.xz c01d296fc675c1ce8d287b568bf779c731954f98
Bug#992527: [Pkg-javascript-devel] Bug#992527: node-srs: FTBFS with GDAL 3.3.1
On Wed, 15 Sep 2021 18:49:12 +0200 Yadd wrote: > Le 15/09/2021 à 16:10, Sebastiaan Couwenberg a écrit : > > Since this only exists as part of the node-carto dependency chain, > > removing this package along with node-millstone and node-carto is > > probably a better idea than spending time fixing this issue. > > Hi JS Team, > > OK to remove node-srs, node-miilstone and node-carto ? Yes, please. I was about to send an intent to RM these packages to pkg-javascript-devel@. As long as this issue is not fixed (either by switching to node-gdal-async or removing the package), the rdeps of the old gdal library cannot be removed. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processed: tagging 995038, tagging 995040, tagging 994859, tagging 994877, tagging 994930, tagging 994937 ...
Processing commands for cont...@bugs.debian.org: > tags 995038 + sid bookworm Bug #995038 [src:ddccontrol] ddccontrol FTBFS: autoreconf: error: intltoolize failed with exit status: 1 Added tag(s) bookworm and sid. > tags 995040 + sid bookworm Bug #995040 [src:iverilog] iverilog FTBFS: configure: error: C preprocessor "/lib/cpp" fails sanity check Added tag(s) sid and bookworm. > tags 994859 + sid bookworm Bug #994859 [src:tmispell-voikko] tmispell-voikko FTBFS: error: format not a string literal and no format arguments [-Werror=format-security] Added tag(s) sid and bookworm. > tags 994877 + sid bookworm Bug #994877 [dokuwiki] dokuwiki: During install error /var/lib/dpkg/info/dokuwiki.postinst:123 tempfile: not found Added tag(s) bookworm and sid. > tags 994930 + sid bookworm Bug #994930 [guile-2.2] guile-2.2: FTBFS due to web-server.test error Added tag(s) bookworm and sid. > tags 994937 + sid bookworm Bug #994937 [openscad] openscad: FTBFS ( due to cgal changes ?) Added tag(s) sid and bookworm. > tags 994835 + sid bookworm Bug #994835 [vice] vice: Fails to build -- missing JPEG support Added tag(s) bookworm and sid. > tags 994824 + sid bookworm Bug #994824 [slop] slop: FTBFS on sid Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 994824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994824 994835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994835 994859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994859 994877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994877 994930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994930 994937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994937 995038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995038 995040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: merging 995015 995016
Processing commands for cont...@bugs.debian.org: > merge 995015 995016 Bug #995015 [dnsdiag] dnsdiag: Error when running: DeprecationWarning Bug #995016 [dnsdiag] dnsdiag: Error when running: DeprecationWarning Merged 995015 995016 > thanks Stopping processing here. Please contact me if you need assistance. -- 995015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995015 995016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993978: marked as done (linux-image-5.10.0-8-arm64: host hangs after some time of use)
Your message dated Sat, 25 Sep 2021 22:02:07 + with message-id and subject line Bug#993978: fixed in linux 5.10.46-5 has caused the Debian Bug report #993978, regarding linux-image-5.10.0-8-arm64: host hangs after some time of use 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.) -- 993978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993978 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 5.10.46-4 X-Debbugs-CC: debian...@lists.debian.org, a...@debian.org Severity: serious Justification: data loss Hi, As discussed over IRC, here is the bug report for one of the hanging arm64 hosts we have for ci.debian.net. Since the upgrade of our hosts to bullseye (days before the bullseye release) we have been experiencing random loss of access to our hosts. For the hosts that have some form of out-of-bound access, I tried to use that to see what's going on, but at AWS our account doesn't have the right permissions to use the serial port out-of-bound access and all other forms that I tried on all hosts that I have access to some for of out-of-bound access that didn't work. Since the bullseye release I've rebooted (externally triggered) already dozens of times and for those host that don't allow rebooting (AWS again) I had to reprovision the hosts. All the architectures (amd64, arm64, ppc64el and s390x) that we have experience these hangs. I'm absolutely not claiming that the root cause is the same, but on buster we didn't experience this (our s390x host never workerd on buster so I don't claim regression there), so there is a pattern. However, the symptoms don't look completely the same everywhere. On one of our arm64 hosts (we call ci-worker-armel-01) I found the attached logging as the final logs in the journal. Paul -- Package-specific info: ** Version: Linux version 5.10.0-8-arm64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.46-4 (2021-08-03) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-arm64 root=UUID=05ed5059-7820-4ab3-a3b7-37cc7dede2cf ro console=tty0 console=ttyS1,115200n8 quiet ** Tainted: W (512) * kernel issued warning ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information ** Loaded modules: cfg80211 rdma_ucm streebog_generic sha3_generic rmd320 rmd256 rmd160 rmd128 poly1305_generic poly1305_neon nhpoly1305_neon nhpoly1305 libpoly1305 michael_mic crc32_generic blake2b_generic twofish_generic twofish_common serpent_generic fcrypt cast6_generic cast5_generic cast_common camellia_generic blowfish_generic blowfish_common aes_arm64 ghash_generic gcm aegis128 aes_generic nf_log_ipv6 nf_conntrack_ftp nf_log_ipv4 nf_log_common nft_log nft_synproxy nf_synproxy_core nft_limit nft_objref nft_osf nfnetlink_osf nft_numgen nft_nat nf_conntrack_sip nft_quota nft_meta_bridge nf_flow_table_ipv4 nft_flow_offload nf_flow_table_inet nf_flow_table aes_ce_ccm cbc des_generic libdes ecb sha512_generic sha512_arm64 md4 af_packet_diag netlink_diag nft_masq nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv6 nft_reject nft_ct sctp_diag udp_diag raw_diag unix_diag iptable_mangle iptable_filter tcp_diag inet_diag 8021q garp mrp nfsd auth_rpcgss nfs_acl lockd grace sunrpc nf_conntrack_netlink xfrm_user xfrm_algo overlay algif_rng algif_skcipher algif_aead can_bcm sctp bluetooth jitterentropy_rng drbg ansi_cprng ecdh_generic rfkill ecc qrtr ns can_j1939 can_isotp can_raw can algif_hash af_alg xt_nat xt_addrtype iptable_nat dummy xt_multiport vhost_net vhost vhost_iotlb tap tun veth xt_conntrack ipt_REJECT nf_reject_ipv4 xt_CHECKSUM nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter xt_tcpudp nft_compat bridge stp llc nf_tables nfnetlink binfmt_misc nls_ascii nls_cp437 vfat fat dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua aes_ce_blk crypto_simd cryptd aes_ce_cipher ghash_ce efi_pstore gf128mul libaes sha2_ce sha256_arm64 sha1_ce sbsa_gwdt acpi_ipmi ipmi_ssif dm_mod evdev ipmi_devintf ipmi_msghandler arm_cmn xgene_hwmon cppc_cpufreq ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi scsi_mod bonding drm fuse configfs efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq crc32c_generic libcrc32c raid1 raid0 multipath linear md_mod mlx5_ib ib_uverbs ib_core mlx5_core nvme nvme_core igb t10_pi crc_t10dif mlxfw crct10dif_generic
Processed: bug 995073 is forwarded to https://github.com/yarnpkg/berry/issues/3496
Processing commands for cont...@bugs.debian.org: > forwarded 995073 https://github.com/yarnpkg/berry/issues/3496 Bug #995073 [gitlab] gitlab: yarnpkg fails with error An unexpected error occurred: "Release not found: 2.4.2". Set Bug forwarded-to-address to 'https://github.com/yarnpkg/berry/issues/3496'. > thanks Stopping processing here. Please contact me if you need assistance. -- 995073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995073 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995073: gitlab: yarnpkg fails with error An unexpected error occurred: "Release not found: 2.4.2".
On 25/9/21 11:11 PM, Ondrej Zary wrote: > Package: gitlab > Version: 13.12.9+ds1-1~fto10+1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > installing gitlab 13.12.9+ds1-1~fto10+1 on buster amd64 fails with: > > Installing node modules... > Resolving 2.4.2 to a url... > error An unexpected error occurred: "Release not found: 2.4.2". > info If you think this is a bug, please open a bug report with the > information provided in "/var/lib/gitlab/yarn-error.log". > info Visit https://yarnpkg.com/en/docs/cli/policies for documentation about > this command. yarn 3.0 needs nodejs 12. So this was a work around used to force yarn 2.x. Looks like there is no way to install 2.x versions of yarn anymore :( So we will have to update minimum version of nodejs to 12 (already done for latest versions in bullseye) and use yarn set version berry. I guess you will have to use nodejs from official repos or we will have to backport nodejs 12 to buster. signature.asc Description: OpenPGP digital signature
Bug#994551: libcifpp1: please split off static files to separate package
Hi Nilesh, Nilesh Patra, on 2021-09-25: > > Hi Étienne, all, > > > I took the liberty to implement the change you suggest, and push > > to Salsa [1]. > > I do not see your changes on salsa, the last commit is 3 months old > there. > Did you forget to push? Yes, I forgot, sorry about that; I just pushed as soon as I realized it. Thanks for the notice, :) -- .''`. Étienne Mollier : :' : gpg: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/tty1, please excuse my verbosity `- signature.asc Description: PGP signature
Bug#993627: marked as done (ndpi: Bus error on armhf when built on 64bit hardware)
Your message dated Sat, 25 Sep 2021 20:35:11 + with message-id and subject line Bug#993627: fixed in ndpi 4.0-3 has caused the Debian Bug report #993627, regarding ndpi: Bus error on armhf when built on 64bit hardware to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 993627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ndpi Version: 4.0-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=ndpi=armhf ... Bus error openvpn.pcapERROR ... make[1]: *** [debian/rules:35: override_dh_auto_test] Error 1 This is likely an alignment problem, similar to the fixed #917238. --- End Message --- --- Begin Message --- Source: ndpi Source-Version: 4.0-3 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of ndpi, 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 993...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated ndpi 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: Sat, 25 Sep 2021 21:57:52 +0200 Source: ndpi Architecture: source Version: 4.0-3 Distribution: unstable Urgency: medium Maintainer: Ludovico Cavedon Changed-By: Gianfranco Costamagna Closes: 993627 Changes: ndpi (4.0-3) unstable; urgency=medium . * Team upload [ Bernhard Übelacker ] * debian/patches/fix-unaligned-memory-accesses-with-get_u_int64_t-at- armhf.patch * debian/patches/use-get_u_int64_t-to-avoid-unaligned-memory-access-at- armhf.patch: - fix two armhf unaligned accesses. (Closes: #993627) Checksums-Sha1: 667d109334c110217be2cc80ccad3f4a21e8122b 2105 ndpi_4.0-3.dsc 3ab39442ae76823084c434e1ee0f8d9c0c2ec611 15440 ndpi_4.0-3.debian.tar.xz a2d7e7402fe4c3776e729e43a3b084f2d33ae09e 8679 ndpi_4.0-3_source.buildinfo Checksums-Sha256: 482346cc3e8e03e77e5c23dbced234333bd1d9b06dba31b8b91ecb51f29162a6 2105 ndpi_4.0-3.dsc 65dfc6501dfa6d499e7e9c75aabe236bd602789df6f1e8e6a13e6061613f5c22 15440 ndpi_4.0-3.debian.tar.xz 775c9992a499086e24257238b3e0651fe19fef66debd6b4eb26cc6858f714326 8679 ndpi_4.0-3_source.buildinfo Files: c5c5b8aa97552466afdcfdb83cb398e7 2105 libs optional ndpi_4.0-3.dsc 8f18f69153b92c4ec212c8227f8a5a65 15440 libs optional ndpi_4.0-3.debian.tar.xz 7d80dc0edc61121f989c6fa1d3f23f5e 8679 libs optional ndpi_4.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmFPf9EACgkQ808JdE6f XdkikQ/+JUNkRZixLcv2DATeGNKN6qXX93wjLlAJCdyNndefyJYS92wAe/Nhx0pk knFUdUgIL1T4z1tYlAvtzl3lATs+P0/TLXFTSTgGEa3pLGBCgM6Gwd5Ejkxs328K yQDoewbhLVM3PK3pdb7lqvu0a615j+SEl4Lk3/QBtXjI+v+igwCIZPyiSfru6UQk 2+ybTjMWWWrV1BDhSUUqhn7WDl45U6BX2CHT8oHoX4oDyjndUEMsmTLd3OZvtqAz gfAacb7ZEdMpATQZJSKjp5sl8lJ8FMyZdIZyOdAZ99unIGqy/qR+Ak8FlA97BX9C 1qIkl/nFp3qvph1xn3ynmCYv1MPABjdOW7ww4cpLLbbd6ESBW9E0ZpRH6+eyvKdv bc+N3MLiqxaGFl5qHSYALIIoRsx4x2ggOs1BS0ANngZoelFKsIGY6CTu17JDijQ1 ynPQz/Oe61oodBUWMsSe2bpsy8vRAGGfhCy/mulSUK5uOvA8t2llW7q3dQ2qntOY bGtXtBTdz+Zs2tgZ8UdUt0tscXQ7kLhhVCi5O2v7hOG8u1UnbadLhv37h9h8Xb9I X3ca+ARVNeaLwtCxyjNtkOqCP1sEOONCxadf7PQJR+g9GE/z1krHcYb+l9tfH6Bu CwCSNnm6bEkCPDJr+NYSXRjb/4zQT3RD5se/066WQA9gm72w+AM= =af68 -END PGP SIGNATURE End Message ---
Bug#995085: dlt-viewer: missing installed headers in -dev packages
Source: dlt-viewer Version: 2.21.2+dfsg-2 Severity: serious tags: patch Fixed: 2.21.2+dfsg-3 Hello, the package doesn't install lots of header files, see https://bugs.debian.org/993564 for more information. G.
Bug#995014: linux/linux-signe-* break zfs-linux autopkgtest: None of the expected "capability" interfaces were detected
Hi, On 24-09-2021 22:02, Salvatore Bonaccorso wrote: > zfs-linux needs an update to be compatible with Linux 5.14 and above. > This should be resolved in the 2.0.6 version upstream which was > uploaded earlier to unstable, at least according to > > https://github.com/openzfs/zfs/releases/tag/zfs-2.0.6 With version 2.0.6-1, the test still fails on ppc64el [1], but with a different error. Please investigate. Paul [1] https://ci.debian.net/data/autopkgtest/testing/ppc64el/z/zfs-linux/15513926/log.gz ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'mmu_feature_keys' OpenPGP_signature Description: OpenPGP digital signature
Bug#992914: libassa: FTBFS due to RPC removal from glibc
Thanks for the bug report and patch. I've come up with an alternate patch that only affects the utils/ directory. This patch will show up in my next upload in the next few days (currently on mentors.debian.net). On Wed, 25 Aug 2021 00:03:42 +0200 Aurelien Jarno wrote: > Source: libassa > Version: 3.5.1-7 > Severity: serious > Tags: patch ftbfs > Justification: fails to build from source (but built successfully in the past) > > The glibc SunRPC implementation has been marked obsolete for some time. > It has been removed upstream from glibc 2.32, and it got disabled in the > recent glibc uploads. The TI RPC implementation should be used instead. > > libassa was already supposed to use libtirpc, but in practice was still > linked to glibc due a missing entry in Makefile.am. Please find attach a > patch fixing the FTBFS.
Bug#995020: macaulay2: autopkgtest regression and flaky test: SIGSEGV
Hi Torrance, On 25-09-2021 04:56, Torrance, Douglas wrote: > There's a problem though -- this macaulay2 autopkgtest regression is now > preventing ntl from migrating to testing! [1] This seems like a chicken > and > egg situation -- we need it to migrate for the tests to pass, but we need > the tests to pass for it to migrate... I must confess that transitions aren't perfectly handled by the migration software (britney) of the release team yet. britney tries to figure which packages should come from unstable and adds them as pinned packages, but hasn't any special notion of transitions. > Is there a good solution for this? Not yet. > One very hacky idea would be to upload > a new macaulay2 package with a very basic autopkgtest that's guaranteed to > pass for the time being until everything migrates. Is there a better > solution? Yes: * macaulay2 could (temporarily) add *versioned* test dependencies on libsingular4m1 and libflint-2.8.0 (then autopkgtest will do the right thing). * macaulay2 could add *versioned* dependencies on libsingular4m1 and libflint-2.8.0 * I could manually trigger the test with the combination. Let's pick the last option for now and see if it works. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: un-confuse bts
Processing commands for cont...@bugs.debian.org:
> reassign 994265 src:pypy 7.3.5+dfsg-2
Bug #994265 {Done: Stefano Rivera } [src:pypy,
src:python-virtualenv] pypy breaks python-virtualenv autopkgtest on ppc64el:
RuntimeError: maximum recursion depth exceeded
Bug reassigned from package 'src:pypy, src:python-virtualenv' to 'src:pypy'.
No longer marked as found in versions python-virtualenv/20.4.0+ds-2 and
pypy/7.3.5+dfsg-2.
No longer marked as fixed in versions pypy/7.3.5+dfsg-3.
Bug #994265 {Done: Stefano Rivera } [src:pypy] pypy breaks
python-virtualenv autopkgtest on ppc64el: RuntimeError: maximum recursion depth
exceeded
Marked as found in versions pypy/7.3.5+dfsg-2.
> fixed 994265 7.3.5+dfsg-3
Bug #994265 {Done: Stefano Rivera } [src:pypy] pypy breaks
python-virtualenv autopkgtest on ppc64el: RuntimeError: maximum recursion depth
exceeded
Marked as fixed in versions pypy/7.3.5+dfsg-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
994265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#994971: NVENC issue
It has also affected the NVENC compatibility, using OBS-Studio it simply does not detect it and gives an error when wanting to record, it had to be reverted to the previous version.
Bug#995032: marked as done (GNOME components segfault as a result of libffi transition)
Your message dated Sat, 25 Sep 2021 17:49:33 + with message-id and subject line Bug#995032: fixed in gobject-introspection 1.70.0-2 has caused the Debian Bug report #995032, regarding GNOME components segfault as a result of libffi transition 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.) -- 995032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell Version: 40.4-3+b1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I had my system running for quite some time, but did update the packages. Now today I restated the system and I ran into a white-screen when GDM is supposed to come up, saying "Oh no!" ...". With lightdm I can start the session but get the whitescreen as soon as the session starts. I grepped for all possible relevent strings in /var/log/syslog: Sep 25 04:39:36 vogon gnome-session[35272]: gnome-session-binary[35272]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist Sep 25 04:39:36 vogon gnome-session-binary[35272]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist Sep 25 04:39:36 vogon gnome-session[35272]: gnome-session-binary[35272]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist Sep 25 04:39:36 vogon gnome-session-binary[35272]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist Sep 25 04:39:36 vogon gnome-session-binary[35272]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist Sep 25 04:39:36 vogon gnome-session[35272]: gnome-session-binary[35272]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist Sep 25 04:39:38 vogon pulseaudio[35258]: Failed to open cookie file '/var/lib/gdm3/.config/pulse/cookie': Datei oder Verzeichnis nicht gefunden Sep 25 04:39:38 vogon pulseaudio[35258]: Failed to load authentication key '/var/lib/gdm3/.config/pulse/cookie': Datei oder Verzeichnis nicht gefunden Sep 25 04:39:38 vogon pulseaudio[35258]: Failed to open cookie file '/var/lib/gdm3/.pulse-cookie': Datei oder Verzeichnis nicht gefunden Sep 25 04:39:38 vogon pulseaudio[35258]: Failed to load authentication key '/var/lib/gdm3/.pulse-cookie': Datei oder Verzeichnis nicht gefunden Sep 25 04:39:38 vogon pulseaudio[35258]: org.bluez.ProfileManager1.RegisterProfile() failed: org.bluez.Error.NotPermitted: UUID already registered Sep 25 04:39:38 vogon pulseaudio[35258]: org.bluez.ProfileManager1.RegisterProfile() failed: org.bluez.Error.NotPermitted: UUID already registered Sep 25 04:39:38 vogon kernel: [ 4179.134171] gnome-shell[35301]: segfault at 7f08d249d030 ip 7f08d2e5434e sp 7ffe24d063a0 error 7 in libglib-2.0.so.0.7000.0[7f08d2e0b000+8b000] Sep 25 04:39:38 vogon gdm-launch-environment]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Sep 25 04:39:39 vogon /usr/libexec/gdm-x-session[35402]: _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed Sep 25 04:39:39 vogon /usr/libexec/gdm-x-session[35402]: #011(WW) warning, (EE) error, (NI) not implemented, (??) unknown. Sep 25 04:39:39 vogon systemd[34922]: onedrive.service: Failed with result 'exit-code'. Sep 25 04:39:39 vogon /usr/libexec/gdm-x-session[35402]: xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) Sep 25 04:39:40 vogon gnome-session[35422]: gnome-session-binary[35422]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist Sep 25 04:39:40 vogon gnome-session-binary[35422]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist Sep 25 04:39:40 vogon gnome-session[35422]: gnome-session-binary[35422]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist Sep 25 04:39:40 vogon gnome-session-binary[35422]: WARNING:
Bug#995073: gitlab: yarnpkg fails with error An unexpected error occurred: "Release not found: 2.4.2".
Package: gitlab Version: 13.12.9+ds1-1~fto10+1 Severity: grave Justification: renders package unusable Dear Maintainer, installing gitlab 13.12.9+ds1-1~fto10+1 on buster amd64 fails with: Installing node modules... Resolving 2.4.2 to a url... error An unexpected error occurred: "Release not found: 2.4.2". info If you think this is a bug, please open a bug report with the information provided in "/var/lib/gitlab/yarn-error.log". info Visit https://yarnpkg.com/en/docs/cli/policies for documentation about this command. -- System Information: Debian Release: 10.10 APT prefers oldstable-proposed-updates-debug APT policy: (500, 'oldstable-proposed-updates-debug'), (500, 'oldstable-debug'), (500, 'oldstable'), (100, 'buster-fasttrack'), (100, 'buster-backports') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-0.bpo.8-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=sk_SK.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages gitlab depends on: ii asciidoctor 2.0.10-2~bpo10+1 pn bc ii bundler 2.1.4-2~bpo10+1 ii bzip2 1.0.6-9.2~deb10u1 pn dbconfig-pgsql | dbconfig-no-t ii debconf [debconf-2.0] 1.5.71 pn gitlab-common pn gitlab-workhorse ii libruby2.7 [ruby-rexml] 2.7.3-2~fto10+1 ii lsb-base10.2019051400 ii msmtp-mta [mail-transport-agen 1.8.3-1 ii nginx-full [nginx] 1.14.2-2+deb10u4 pn node-autosize pn node-axios pn node-babel-loader pn node-babel-plugin-lodash pn node-babel7 pn node-bootstrap ii node-brace-expansion1.1.8-1 ii node-cache-loader 4.1.0-6~bpo10+1 pn node-chart.js pn node-clipboard pn node-codemirror pn node-compression-webpack-plugi pn node-copy-webpack-plugin ii node-core-js3.6.1-2~bpo10+2 ii node-css-loader 5.0.1+~cs14.0.5-1~bpo10+1 pn node-d3 pn node-d3-scale pn node-d3-selection pn node-dateformat pn node-exports-loader ii node-file-loader6.2.0-2~bpo10+1 pn node-font-awesome pn node-fuzzaldrin-plus ii node-glob 7.1.6-1~bpo10+1 ii node-imports-loader 0.8.0-2~bpo10+1 pn node-jed ii node-jquery 3.5.1+dfsg-4~bpo10+1 pn node-jquery-ujs pn node-js-cookie ii node-js-yaml3.13.1+dfsg-2~bpo10+1 pn node-jszip pn node-jszip-utils pn node-katex ii node-lodash 4.17.21+dfsg+~cs8.31.189.20210220-1~bpo10+1 pn node-marked pn node-mermaid ii node-minimatch 3.0.4-3 pn node-mousetrap pn node-pdfjs-dist pn node-popper.js pn node-prismjs pn node-prosemirror-markdown pn node-prosemirror-model pn node-raven-js ii node-raw-loader 4.0.2-2~bpo10+1 pn node-style-loader pn node-three-orbit-controls pn node-three-stl-loader ii node-timeago.js 4.0.2-2~bpo10+1 pn node-underscore ii node-url-loader 4.1.1-3~bpo10+1 ii node-uuid 8.3.2+~8.3.0-1~bpo10+1 pn node-vue pn node-vue-resource pn node-vue-template-compiler pn node-webpack-stats-plugin ii node-worker-loader 3.0.5-2~bpo10+1 pn node-xterm ii nodejs 10.24.0~dfsg-1~deb10u1 pn ohai ii openssh-client 1:7.9p1-10+deb10u2 ii postgresql-client 11+200+deb10u4 ii postgresql-client-11 [postgres 11.12-0+deb10u1 pn postgresql-contrib pn puma ii rake12.3.1-3+deb10u1 pn redis-server pn ruby-ace-rails-ap pn ruby-acme-client ii ruby-actioncable [node-rails-a 2:6.0.3.7+dfsg-1~fto10+1 pn ruby-activerecord-explain-anal ii ruby-acts-as-taggable-on7.0.0-1~bpo10+1 pn ruby-addressable ii ruby-akismet3.0.0-1~bpo10+1 pn ruby-apollo-upload-server ii ruby-asana 0.10.3-1~bpo10+1 pn ruby-asciidoctor-include-ext pn ruby-asciidoctor-kroki ii ruby-asciidoctor-plantuml 0.0.12-1~bpo10+1 pn
Processed: Bug#995032 marked as pending in gobject-introspection
Processing control commands: > tag -1 pending Bug #995032 [src:gobject-introspection] GNOME components segfault as a result of libffi transition Ignoring request to alter tags of bug #995032 to the same tags previously set -- 995032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995032: marked as pending in gobject-introspection
Control: tag -1 pending Hello, Bug #995032 in gobject-introspection reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/gobject-introspection/-/commit/fd1f05b1bc71ca14c6eac36fb3d916c7704deb91 d/control.in: Add Breaks on cjs, gjs, etc. that expect the libffi7 ABI Newer versions of these libraries have been binNMU'd against the libffi8 ABI, and future versions of them will pick up a dependency on libgirepository-1.0-1-with-libffi8, but their versions in bullseye and testing are not compatible with a version of gobject-introspection that was compiled against libffi8. Don't allow co-installation of old cjs, gjs, etc. with new gobject-introspection. Closes: #995032 (this message was generated automatically) -- Greetings https://bugs.debian.org/995032
Processed: Bug#995032 marked as pending in gobject-introspection
Processing control commands: > tag -1 pending Bug #995032 [src:gobject-introspection] GNOME components segfault as a result of libffi transition Added tag(s) pending. -- 995032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995032: marked as pending in gobject-introspection
Control: tag -1 pending Hello, Bug #995032 in gobject-introspection reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/gobject-introspection/-/commit/46f58f10d6ef2faeeacc23c8f2a34641421be849 Generate a dependency on libgirepository-1.0-1-with-libffi8 where needed A few gobject-introspection symbols have libffi data structures in their arguments or results, resulting in crashes if a dependent package is not expecting the same ABI of libffi. Add a Provides on a virtual package with a programmatically-generated name such as libgirepository-1.0-1-with-libffi8, and generate dependencies on that virtual package if the affected symbols are used, so that gobject-introspection and its users are all on the same side of each libffi transition. Closes: #995032 (this message was generated automatically) -- Greetings https://bugs.debian.org/995032
Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages
On 2021-09-25 15:31:31 +0200, Francesco Poli wrote: > On Sat, 25 Sep 2021 12:25:16 +0200 Sebastian Ramacher wrote: > > [...] > > So this is crashing somewhere during the initialization of libglibmm. > > Hence I'm reassigning to libglibmm. > [...] > > Thanks, Sebastian! > > > By the way, I am now wondering whether I really need jackd2-firewire. > Maybe I can keep it out of my system, even after this bug gets fixed?!? > I don't think I have a FireWire port, hence maybe the JACK FireWire > support is useless to me. > Could you please confirm? If you don't have a firewire port, then jackd2-firewire is of no use. Cheers > > -- > http://www.inventati.org/frx/ > There's not a second to spare! To the laboratory! > . Francesco Poli . > GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#995050: ecere-sdk FTBFS with gcc 10
Thank you Adrian for reporting this. We have fixes for this upstream: commit *c94efd6390599a4a291b7fe8b3d2d62699247380* Author: Jerome St-Louis Date: Sun Sep 6 03:35:01 2020 -0400 compiler/bootstrap: Updated for GCC 10 Common fixes commit *7d835dd5c6e17ad1626ec7b6f1725e0f7f8a9371* Author: Rejean Loyer Date: Mon Aug 3 13:18:51 2020 -0400 compiler/ecs: add -no-attribute-common for targetting wasm. workaround "Common symbols are not yet implemented for Wasm" message coming from emscripten-releases\llvm-project\llvm\li b\MC\MCWasmStreamer.cpp's MCWasmStreamer::emitCommonSymbol function. commit *ca58cfa4e26e03271e32ee6aae3206956fdc26fd* Author: Jerome St-Louis Date: Wed May 20 07:25:49 2020 -0400 compiler/libec: Fixed multiple definitions issues breaking on GCC 10 without -fcommon There is also a more recent commit fixes for GCC 11 which will surely show up sooner or later: commit *53ec01de1c42cf342a35dc125a4fef01ffb5fced* (origin/master, master) Author: Jerome St-Louis Date: Thu Aug 5 21:07:56 2021 -0400 compiler/libec/lexer.l: Initial fix for failure to build on GCC 11 - bootstrap updated - # 0 instead of # 1 generated by preprocessor triggered problem in lexer's preprocessor() - NOTE: This was likely resulting in declMode, defaultDeclMode and structDeclMode not being set properly - It may also be related to #1135 There are other important fixes on master since 0.44.15, including fixes for #898832 . In general, the master branch of our repo is currently (HEAD: 53ec01de1c42cf342a35dc125a4fef01ffb5fced) very conservatively stable, and would be a good candidate for a patch 0.44.15 release. On our side we are overdue for a new release, but we hope to bring in a lot of new improvements and functionality for the next 0.44.16 release, which is proving difficult to complete given that our development branch (/lates//t/) is now more than 1200 commits ahead of master. We are also quite busy with our geospatial software endeavours (making use of the Ecere SDK). If someone is willing to help with the Debian packaging / update to close these bugs, myself and possibly others in our community will be more than happy to provide assistance and otherwise contribute to the effort. Thank you! Best regards, -Jerome On 9/25/21 6:27 AM, Adrian Bunk wrote: Source: ecere-sdk Version: 0.44.15-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=ecere-sdk=0.44.15-1%2Bb4 ... gcc -Wl,-z,relro -Wl,--no-undefined -Wl,--no-undefined -Wl,--no-undefined -Wl,--no-undefined -L../ecere/obj/bootstrap.linux -L../libec/obj/bootstrap.linux obj/bootstrap.linux/ecp.o obj/bootstrap.linux/ecp.main.o-lecereBootstrap -lecBootstrap -lm -ldl -o obj/bootstrap.linux/ecp /usr/bin/ld: obj/bootstrap.linux/ecp.main.o:./compiler/bootstrap/ecp/bootstrap/ecp.main.c:52: multiple definition of `__ecereVMethodID___ecereNameSpace__ecere__sys__File_Eof'; obj/bootstrap.linux/ecp.o:./compiler/bootstrap/ecp/bootstrap/ecp.c:388: first defined here /usr/bin/ld: obj/bootstrap.linux/ecp.main.o:./compiler/bootstrap/ecp/bootstrap/ecp.main.c:54: multiple definition of `__ecereVMethodID___ecereNameSpace__ecere__sys__File_Puts'; obj/bootstrap.linux/ecp.o:./compiler/bootstrap/ecp/bootstrap/ecp.c:384: first defined here /usr/bin/ld: obj/bootstrap.linux/ecp.main.o:./compiler/bootstrap/ecp/bootstrap/ecp.main.c:56: multiple definition of `__ecereVMethodID___ecereNameSpace__ecere__sys__File_Read'; obj/bootstrap.linux/ecp.o:./compiler/bootstrap/ecp/bootstrap/ecp.c:390: first defined here /usr/bin/ld: obj/bootstrap.linux/ecp.main.o:./compiler/bootstrap/ecp/bootstrap/ecp.main.c:58: multiple definition of `__ecereVMethodID___ecereNameSpace__ecere__sys__File_Seek'; obj/bootstrap.linux/ecp.o:./compiler/bootstrap/ecp/bootstrap/ecp.c:396: first defined here /usr/bin/ld: obj/bootstrap.linux/ecp.main.o:./compiler/bootstrap/ecp/bootstrap/ecp.main.c:60: multiple definition of `__ecereVMethodID___ecereNameSpace__ecere__sys__File_Write'; obj/bootstrap.linux/ecp.o:./compiler/bootstrap/ecp/bootstrap/ecp.c:392: first defined here ... /usr/bin/ld: ../libec/obj/bootstrap.linux/libecBootstrap.a(shortcuts.o):./compiler/bootstrap/libec/bootstrap/shortcuts.c:298: multiple definition of `__ecereVMethodID___ecereNameSpace__ecere__sys__File_Write'; obj/bootstrap.linux/ecp.o:./compiler/bootstrap/ecp/bootstrap/ecp.c:392: first defined here /usr/bin/ld: ../libec/obj/bootstrap.linux/libecBootstrap.a(shortcuts.o):./compiler/bootstrap/libec/bootstrap/shortcuts.c:300: multiple definition of `__ecereVMethodID___ecereNameSpace__ecere__sys__File_Seek'; obj/bootstrap.linux/ecp.o:./compiler/bootstrap/ecp/bootstrap/ecp.c:396: first defined here /usr/bin/ld: ../libec/obj/bootstrap.linux/libecBootstrap.a(type.o):./compiler/bootstrap/libec/bootstrap/type.c:392: multiple definition of `__ecereVMethodID___ecereNameSpace__ecere__sys__File_Seek';
Bug#994265: marked as done (pypy breaks python-virtualenv autopkgtest on ppc64el: RuntimeError: maximum recursion depth exceeded)
Your message dated Sat, 25 Sep 2021 16:36:17 + with message-id and subject line Bug#994265: fixed in pypy 7.3.5+dfsg-3 has caused the Debian Bug report #994265, regarding pypy breaks python-virtualenv autopkgtest on ppc64el: RuntimeError: maximum recursion depth exceeded 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.) -- 994265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pypy, python-virtualenv Control: found -1 pypy/7.3.5+dfsg-2 Control: found -1 python-virtualenv/20.4.0+ds-2 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of pypy the autopkgtest of python-virtualenv fails in testing on ppc64el when that autopkgtest is run with the binary packages of pypy from unstable. It passes when run with only packages from testing. In tabular form: passfail pypy from testing7.3.5+dfsg-2 python-virtualenv from testing20.4.0+ds-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of pypy to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=pypy https://ci.debian.net/data/autopkgtest/testing/ppc64el/p/python-virtualenv/15222817/log.gz File "/usr/lib/pypy/lib-python/2.7/sre_parse.py", line 701, in _parse p = _parse_sub(source, state, nested + 1) File "/usr/lib/pypy/lib-python/2.7/sre_parse.py", line 349, in _parse_sub itemsappend(_parse(source, state, nested + 1)) File "/usr/lib/pypy/lib-python/2.7/sre_parse.py", line 701, in _parse p = _parse_sub(source, state, nested + 1) File "/usr/lib/pypy/lib-python/2.7/sre_parse.py", line 349, in _parse_sub itemsappend(_parse(source, state, nested + 1)) File "/usr/lib/pypy/lib-python/2.7/sre_parse.py", line 422, in _parse subpattern = SubPattern(state) File "/usr/lib/pypy/lib-python/2.7/sre_parse.py", line 99, in __init__ def __init__(self, pattern, data=None): RuntimeError: maximum recursion depth exceeded ASSERT:Execute bare pip testSystemPackagesNotAvailable Traceback (most recent call last): File "", line 1, in ImportError: No module named six DEPRECATION: pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support pip 21.0 will remove support for this functionality. testSystemPackagesAvailable DEPRECATION: pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support pip 21.0 will remove support for this functionality. testSetuptoolsAvailable Ran 4 tests. FAILED (failures=1) OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: pypy Source-Version: 7.3.5+dfsg-3 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of pypy, 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 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated pypy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 25 Sep 2021 09:12:52 -0700 Source: pypy Architecture: source Version: 7.3.5+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Stefano Rivera Changed-By: Stefano Rivera Closes: 994265 Changes: pypy (7.3.5+dfsg-3) unstable; urgency=medium . * Fix PPC JIT backend code generation. (Closes: #994265) Checksums-Sha1:
Bug#994910: tripwire segfaults while reading files in /etc
Package: tripwire Version: 2.4.3.7-3+b3 Followup-For: Bug #994910 Reproduced here following a libc6 upgrade. I suspect this is because tripwire is statically linked and there has been a new release of libc6, so I suspect the nsswitch interface has broken (which is a standard problem with statically linking with libc6 on Linux). This would also explain why rebuilding the package made the problem go away. If this is correct, a BinNMU should fix the problem. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tripwire depends on: ii debconf [debconf-2.0] 1.5.77 ii postfix [mail-transport-agent] 3.5.6-1+b1 tripwire recommends no packages. tripwire suggests no packages. -- Configuration Files: /etc/tripwire/twcfg.txt changed [not included] /etc/tripwire/twpol.txt changed [not included] -- debconf information: * tripwire/installed: * tripwire/use-sitekey: true tripwire/local-passphrase-incorrect: false tripwire/broken-passphrase: tripwire/upgrade: true tripwire/email-report: tripwire/change-in-default-policy: * tripwire/use-localkey: true tripwire/site-passphrase-incorrect: false * tripwire/rebuild-config: true * tripwire/rebuild-policy: true
Processed: closing 994444
Processing commands for cont...@bugs.debian.org: > close 99 1.6.1-3 Bug #99 [src:panicparse] panicparse: autopkgtest failure Marked as fixed in versions panicparse/1.6.1-3. Bug #99 [src:panicparse] panicparse: autopkgtest failure Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 99: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=99 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 995032 to src:gobject-introspection, affects 995032
Processing commands for cont...@bugs.debian.org: > reassign 995032 src:gobject-introspection 1.70.0-1 Bug #995032 [gnome-shell] GNOME components segfault as a result of libffi transition Bug reassigned from package 'gnome-shell' to 'src:gobject-introspection'. No longer marked as found in versions gnome-shell/40.4-3. Ignoring request to alter fixed versions of bug #995032 to the same values previously set Bug #995032 [src:gobject-introspection] GNOME components segfault as a result of libffi transition Marked as found in versions gobject-introspection/1.70.0-1. > affects 995032 + gnome-shell python3-gi libcjs0 libgjs0g > libglib-object-introspection-perl ruby-gobject-introspection Bug #995032 [src:gobject-introspection] GNOME components segfault as a result of libffi transition Added indication that 995032 affects gnome-shell, python3-gi, libcjs0, libgjs0g, libglib-object-introspection-perl, and ruby-gobject-introspection > thanks Stopping processing here. Please contact me if you need assistance. -- 995032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#994612: marked as done (nodjes: Please fix nodejs debci regression)
Your message dated Sat, 25 Sep 2021 15:01:54 +
with message-id
and subject line Done
has caused the Debian Bug report #994612,
regarding nodjes: Please fix nodejs debci regression
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.)
--
994612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nodjes
Version: 12.22.5~dfsg-3
Severity: serious
Dear Maintainer,
Debci fail with against 12.22.5~dfsg-2 with:
duration_ms: 0.293
severity: fail
exitcode: 1
stack: |-
assert.js:101
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
+ actual - expected
+ 'EOVERFLOW'
- 'Unknown system error -75'
at /tmp/autopkgtest-
lxc.zt0_cfzb/downtmp/build.DQ4/src/test/parallel/test-uv-errno.js:21:10
at Array.forEach ()
at Object. (/tmp/autopkgtest-
lxc.zt0_cfzb/downtmp/build.DQ4/src/test/parallel/test-uv-errno.js:15:6)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at Object.Module._extensions..js
(internal/modules/cjs/loader.js:1027:10)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
at Function.executeUserEntryPoint [as runMain]
(internal/modules/run_main.js:60:12)
at internal/main/run_main_module.js:17:47 {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: 'EOVERFLOW',
expected: 'Unknown system error -75',
operator: 'strictEqual'
}
...
This RC bug is for blocking nodejs to unstable until we find the problem.
I do not find myself the problem -75 is for me 'EOVERFLOW', and I do not
understand why it build normally and why debci fail.
--- End Message ---
--- Begin Message ---
Version: 12.22.5~dfsg-4--- End Message ---
Bug#994551: libcifpp1: please split off static files to separate package
Hi Étienne, all, > I took the liberty to implement the change you suggest, and push > to Salsa [1]. I do not see your changes on salsa, the last commit is 3 months old there. Did you forget to push? > Since this is an RC bug which propagates on > several packages, and since it would have to go through NEW, for > manual review; Actually, this bug is now triggering an ugly autorm on several packages. And since it needs to travel via NEW, they might end up getting removed from testing. @Andrius, since you wrote: > So far, there has not been other libcifppX binary package, thus no > damage is done. However, future libcifppX packages should not contain > static files, in particular these: and since this is not doing any damage for now, do you think we could reduce the severity to important for now? We cannot do another upload on top of the one we will be sending to NEW w/o hooping via NEW again, anyway, so I find it safe to drop the severity for now. Let me know? Nilesh signature.asc Description: PGP signature
Processed: cloning 994108, reassign -1 to gcc-9-doc, retitle -1 to gcc-9-doc: do not release with bookworm
Processing commands for cont...@bugs.debian.org: > clone 994108 -1 Bug #994108 [src:gcc-9] gcc-9: do not release with bookworm Bug 994108 cloned as bug 995061 > reassign -1 gcc-9-doc 9.4.0-1 Bug #995061 [src:gcc-9] gcc-9: do not release with bookworm Bug reassigned from package 'src:gcc-9' to 'gcc-9-doc'. No longer marked as found in versions gcc-9/9.4.0-2. Ignoring request to alter fixed versions of bug #995061 to the same values previously set Bug #995061 [gcc-9-doc] gcc-9: do not release with bookworm Marked as found in versions gcc-9-doc/9.4.0-1. > retitle -1 gcc-9-doc: do not release with bookworm Bug #995061 [gcc-9-doc] gcc-9: do not release with bookworm Changed Bug title to 'gcc-9-doc: do not release with bookworm' from 'gcc-9: do not release with bookworm'. > thanks Stopping processing here. Please contact me if you need assistance. -- 994108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994108 995061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995061 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 994931, fixed 994931 in 247.9-2+b1
Processing commands for cont...@bugs.debian.org:
> close 994931
Bug #994931 [systemd] systemd: silently removed configuration files for
systemd-timesyncd
Marked Bug as done
> fixed 994931 247.9-2+b1
Bug #994931 {Done: Michael Biebl } [systemd] systemd:
silently removed configuration files for systemd-timesyncd
Marked as fixed in versions systemd/247.9-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
994931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 995020 https://github.com/Macaulay2/M2/issues/2244 Bug #995020 [src:macaulay2] macaulay2: autopkgtest regression and flaky test: SIGSEGV Set Bug forwarded-to-address to 'https://github.com/Macaulay2/M2/issues/2244'. > thanks Stopping processing here. Please contact me if you need assistance. -- 995020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages
On Sat, 25 Sep 2021 12:25:16 +0200 Sebastian Ramacher wrote: [...] > So this is crashing somewhere during the initialization of libglibmm. > Hence I'm reassigning to libglibmm. [...] Thanks, Sebastian! By the way, I am now wondering whether I really need jackd2-firewire. Maybe I can keep it out of my system, even after this bug gets fixed?!? I don't think I have a FireWire port, hence maybe the JACK FireWire support is useless to me. Could you please confirm? -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpFHXxgnj18j.pgp Description: PGP signature
Processed: Re: mpi4py breaks gyoto autopkgtest on i386: 1 process returned, a non-zero exit code
Processing control commands: > found -1 gyoto/1.4.4-4 Bug #994784 [src:openmpi,src:gyoto] openmpi breaks gyoto autopkgtest on i386 Ignoring request to alter found versions of bug #994784 to the same values previously set > found -1 gyoto/1.4.4-3 Bug #994784 [src:openmpi,src:gyoto] openmpi breaks gyoto autopkgtest on i386 Marked as found in versions gyoto/1.4.4-3. > notfound -1 gyoto/1.4.4-5 Bug #994784 [src:openmpi,src:gyoto] openmpi breaks gyoto autopkgtest on i386 Ignoring request to alter found versions of bug #994784 to the same values previously set -- 994784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#994784: mpi4py breaks gyoto autopkgtest on i386: 1 process returned, a non-zero exit code
Control: found -1 gyoto/1.4.4-4 Control: found -1 gyoto/1.4.4-3 Control: notfound -1 gyoto/1.4.4-5 Hi Paul, Le 24/09/2021 à 21:42, Paul Gevers a écrit : > Is the workaround inside the binary, or only (needed) in the test suite? > In other words, did openmpi *break* gyoto on i386 in some cases? If yes, > Ideally openmpi is updated with a versioned Breaks on gyoto with the > right unfixed package. The migration software then will schedule the set > and the migration will happen if everything's fine. The workaround is only in the test suite. There remains a bug, either within openmpi or within gyoto but triggered by the new version of openmpi. Concerning gyoto, I would only rate it "normal" though, not "serious", if you can confirm that the workaround actually worked in the testing testbed. If this is the case, I would decrease the severity of the bug and keep it opened. It would be great if the openmpi mainainers could have a look, but I guess they will need a me to provide a minimal example which will not be easy to provide, unless they experience the same symptoms in other situations. Regards, Thibaut.
Bug#995032: gnome-session segfaults - no GNOME session possible at all (white screen to contact the system administrator)
Am Samstag, dem 25.09.2021 um 03:48 -0400 schrieb Jeremy Bicha: > On Sat, Sep 25, 2021 at 12:30 AM Michael Ott wrote: > > The problem is not gnome-shell. It is the gobject-introspection. > > After downgrade this packages from 1.70.0-1+b1 to 1.70.0-1 it works > > again. Indeed, version 1.70.0-1+b1 had already been installed on the system. > gobject-introspection was rebuilt as part of the libffi transition. > (That's where the +b1 part of the version name comes from.) The > transition is still in progress. Maybe the problem is that you didn't > have the rebuilt gjs installed? > > The rebuilt gjs is version 1.68.4-1+b1 I checked the apt logs and it seems this version was pulled into my system only today and may have not been available at the time of writing the report. Now the system seems to work again. I agree with Simon. If possibe we should avoid such breakages (even in Sid). Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages
On Sat, Sep 25, 2021 at 6:25 AM Sebastian Ramacher wrote: > So this is crashing somewhere during the initialization of libglibmm. > Hence I'm reassigning to libglibmm. Sebastian, My first guess is that this is more fallout from the incomplete libffi transition. See https://bugs.debian.org/995032 Thanks, Jeremy Bicha
Processed: Re: Bug#995032: GNOME components segfault as a result of libffi transition
Processing control commands: > retitle 995032 GNOME components segfault as a result of libffi transition Bug #995032 [gnome-shell] GNOME components segfault as a result of libffi transition Ignoring request to change the title of bug#995032 to the same title -- 995032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995032: GNOME components segfault as a result of libffi transition
Control: retitle 995032 GNOME components segfault as a result of libffi transition On Sat, 25 Sep 2021 at 03:48:20 -0400, Jeremy Bicha wrote: > On Sat, Sep 25, 2021 at 12:30 AM Michael Ott wrote: > > The problem is not gnome-shell. It is the gobject-introspection. > > After downgrade this packages from 1.70.0-1+b1 to 1.70.0-1 it works > > again. > > gobject-introspection was rebuilt as part of the libffi transition. > (That's where the +b1 part of the version name comes from.) The > transition is still in progress. Maybe the problem is that you didn't > have the rebuilt gjs installed? > > The rebuilt gjs is version 1.68.4-1+b1 > > Here's the list of other packages involved in the transition: > https://release.debian.org/transitions/html/auto-libffi.html Last time we had a libffi transition, in early 2020, we ended up sprinkling versioned Breaks throughout GNOME to force the whole system to be either "old libffi" or "new libffi". This is because some GNOME components, notably gobject-introspection, have libffi data structures in their public API, so in partial upgrades we get one library passing an old-libffi data structure to another library that expects a new-libffi data structure, and crashes. See the gobject-introspection 1.62.0-4 and -5 changelogs for part of what we had to do to fix this. If libffi is going to continue to break ABI somewhat regularly, then I think we are going to need a more systematic way to prevent broken partial upgrades, and it would be very helpful for the libffi maintainer and the release team to keep this failure mode in mind when allocating transition slots (for example doing libffi transitions when there is not a new major version of GLib trying to migrate, as there is at the moment). smcv
Processed: Re: Bug#995032: GNOME components segfault as a result of libffi transition
Processing control commands: > retitle 995032 GNOME components segfault as a result of libffi transition Bug #995032 [gnome-shell] gnome-session segfaults - no GNOME session possible at all (white screen to contact the system administrator) Changed Bug title to 'GNOME components segfault as a result of libffi transition' from 'gnome-session segfaults - no GNOME session possible at all (white screen to contact the system administrator)'. -- 994560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994560 995032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995051: python3.9: FTBFS on i386: test timeout
Source: python3.9 Version: 3.9.7-4 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org Control: block 994560 by -1 python3.9 fails to build on i386 due to tests that timeout: | 0:27:34 load avg: 0.91 [398/407/2] test_xmlrpc_net skipped (resource denied) | | test_xmlrpc_net skipped -- Use of the 'network' resource not enabled | | 0:27:34 load avg: 0.91 [399/407/2] test_xxtestfuzz passed | | 0:27:35 load avg: 0.92 [400/407/2] test_yield_from passed | | 0:27:35 load avg: 0.92 [401/407/2] test_zipapp passed | | 0:28:02 load avg: 0.95 [402/407/2] test_zipfile passed | | 0:28:03 load avg: 0.95 [403/407/2] test_zipfile64 skipped (resource denied) | | test_zipfile64 skipped -- test requires loads of disk-space bytes and a long time to run | | 0:28:03 load avg: 0.95 [404/407/2] test_zipimport passed | | 0:28:05 load avg: 0.95 [405/407/2] test_zipimport_support passed | | 0:28:06 load avg: 0.95 [406/407/2] test_zlib passed | | 0:28:07 load avg: 0.95 [407/407/2] test_zoneinfo passed | | E: Build killed with signal TERM after 150 minutes of inactivity https://buildd.debian.org/status/fetch.php?pkg=python3.9=i386=3.9.7-4=1632563540=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: python3.9: FTBFS on i386: test timeout
Processing control commands: > block 994560 by -1 Bug #994560 [release.debian.org] transition: libffi 994560 was blocked by: 995045 995007 991096 995036 995044 994560 was not blocking any bugs. Added blocking bug(s) of 994560: 995051 -- 994560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994560 995051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995050: ecere-sdk FTBFS with gcc 10
Source: ecere-sdk Version: 0.44.15-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=ecere-sdk=0.44.15-1%2Bb4 ... gcc -Wl,-z,relro -Wl,--no-undefined -Wl,--no-undefined -Wl,--no-undefined -Wl,--no-undefined -L../ecere/obj/bootstrap.linux -L../libec/obj/bootstrap.linux obj/bootstrap.linux/ecp.o obj/bootstrap.linux/ecp.main.o-lecereBootstrap -lecBootstrap -lm -ldl -o obj/bootstrap.linux/ecp /usr/bin/ld: obj/bootstrap.linux/ecp.main.o:./compiler/bootstrap/ecp/bootstrap/ecp.main.c:52: multiple definition of `__ecereVMethodID___ecereNameSpace__ecere__sys__File_Eof'; obj/bootstrap.linux/ecp.o:./compiler/bootstrap/ecp/bootstrap/ecp.c:388: first defined here /usr/bin/ld: obj/bootstrap.linux/ecp.main.o:./compiler/bootstrap/ecp/bootstrap/ecp.main.c:54: multiple definition of `__ecereVMethodID___ecereNameSpace__ecere__sys__File_Puts'; obj/bootstrap.linux/ecp.o:./compiler/bootstrap/ecp/bootstrap/ecp.c:384: first defined here /usr/bin/ld: obj/bootstrap.linux/ecp.main.o:./compiler/bootstrap/ecp/bootstrap/ecp.main.c:56: multiple definition of `__ecereVMethodID___ecereNameSpace__ecere__sys__File_Read'; obj/bootstrap.linux/ecp.o:./compiler/bootstrap/ecp/bootstrap/ecp.c:390: first defined here /usr/bin/ld: obj/bootstrap.linux/ecp.main.o:./compiler/bootstrap/ecp/bootstrap/ecp.main.c:58: multiple definition of `__ecereVMethodID___ecereNameSpace__ecere__sys__File_Seek'; obj/bootstrap.linux/ecp.o:./compiler/bootstrap/ecp/bootstrap/ecp.c:396: first defined here /usr/bin/ld: obj/bootstrap.linux/ecp.main.o:./compiler/bootstrap/ecp/bootstrap/ecp.main.c:60: multiple definition of `__ecereVMethodID___ecereNameSpace__ecere__sys__File_Write'; obj/bootstrap.linux/ecp.o:./compiler/bootstrap/ecp/bootstrap/ecp.c:392: first defined here ... /usr/bin/ld: ../libec/obj/bootstrap.linux/libecBootstrap.a(shortcuts.o):./compiler/bootstrap/libec/bootstrap/shortcuts.c:298: multiple definition of `__ecereVMethodID___ecereNameSpace__ecere__sys__File_Write'; obj/bootstrap.linux/ecp.o:./compiler/bootstrap/ecp/bootstrap/ecp.c:392: first defined here /usr/bin/ld: ../libec/obj/bootstrap.linux/libecBootstrap.a(shortcuts.o):./compiler/bootstrap/libec/bootstrap/shortcuts.c:300: multiple definition of `__ecereVMethodID___ecereNameSpace__ecere__sys__File_Seek'; obj/bootstrap.linux/ecp.o:./compiler/bootstrap/ecp/bootstrap/ecp.c:396: first defined here /usr/bin/ld: ../libec/obj/bootstrap.linux/libecBootstrap.a(type.o):./compiler/bootstrap/libec/bootstrap/type.c:392: multiple definition of `__ecereVMethodID___ecereNameSpace__ecere__sys__File_Seek'; obj/bootstrap.linux/ecp.o:./compiler/bootstrap/ecp/bootstrap/ecp.c:396: first defined here collect2: error: ld returned 1 exit status make[4]: *** [Makefile:101: obj/bootstrap.linux/ecp] Error 1
Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages
Control: tags -1 =
Control: reassign -1 libglibmm-2.4-1v5 2.66.1-1
On 2021-09-25 12:03:54 +0200, Francesco Poli wrote:
> Control: tags -1 - moreinfo
>
>
> On Fri, 24 Sep 2021 21:46:57 +0200 Sebastian Ramacher wrote:
>
> [...]
> > I haven't tried that yet, but otherwise you can always install -dbgsym
> > packages until all symbols are resolved.
>
> I have just tried.
> Not sure the Debuginfod method worked fine enough, but here's what I
> did.
> I first re-installed jackd2-firewire:
>
> # aptitude install jackd2-firewire+M
> The following NEW packages will be installed:
> jackd2-firewire{a} libconfig++9v5{a} libffado2{a} libxml++2.6-2v5{a}
> 0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
> [...]
>
> Then, as a regular user:
>
> $ export DEBUGINFOD_URLS="https://debuginfod.debian.net;
> $ gdb -batch -n -ex 'set pagination off' -ex run -ex bt -ex 'bt full' -ex
> 'thread apply all bt full' --args jackd --realtime -d alsa --device hw:PCH
> --softmode --hwmeter --rate 44100 > jackd_bt.out 2>&1
The relevant part seems to be:
Thread 1 "jackd" received signal SIGSEGV, Segmentation fault.
__strcmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:101
Download failed: Invalid argument. Continuing without source file
./string/../sysdeps/x86_64/multiarch/strcmp-avx2.S.
101 ../sysdeps/x86_64/multiarch/strcmp-avx2.S: Inappropriate ioctl for
device.
#0 __strcmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:101
#1 0x76bc4b19 in g_str_equal () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x76bc3563 in g_hash_table_lookup () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x76be674a in g_quark_from_static_string () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x76dfdbb0 in ?? () from
/usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
#5 0x77fe210e in call_init (l=, argc=argc@entry=10,
argv=argv@entry=0x7fffe168, env=env@entry=0x7fffe1c0) at dl-init.c:74
#6 0x77fe21f0 in call_init (env=0x7fffe1c0, argv=0x7fffe168,
argc=10, l=) at dl-init.c:37
#7 _dl_init (main_map=0x5557ae80, argc=10, argv=0x7fffe168,
env=0x7fffe1c0) at dl-init.c:121
#8 0x77b41b6d in __GI__dl_catch_exception (exception=,
operate=, args=) at dl-error-skeleton.c:182
#9 0x77fe6484 in dl_open_worker (a=a@entry=0x7fffd3d0) at
dl-open.c:783
#10 0x77b41b10 in __GI__dl_catch_exception (exception=0x7fffd3b0,
operate=0x77fe60e0 , args=0x7fffd3d0) at
dl-error-skeleton.c:208
#11 0x77fe5d0a in _dl_open (file=0x7fffd3b0
"\340\323\377\377\377\177", mode=-2147483390, caller_dlopen=0x77f5f80c,
nsid=-2, argc=10, argv=0x7fffe168, env=0x7fffe1c0) at dl-open.c:864
#12 0x77817258 in dlopen_doit (a=a@entry=0x7fffd600) at dlopen.c:66
#13 0x77b41b10 in __GI__dl_catch_exception
(exception=exception@entry=0x7fffd5a0, operate=0x77817200
, args=0x7fffd600) at dl-error-skeleton.c:208
#14 0x77b41bcf in __GI__dl_catch_error (objname=0x5557ccb0,
errstring=0x5557ccb8, mallocedp=0x5557cca8, operate=,
args=) at dl-error-skeleton.c:227
#15 0x77817a65 in _dlerror_run (operate=operate@entry=0x77817200
, args=args@entry=0x7fffd600) at dlerror.c:170
#16 0x778172e4 in __dlopen (file=, mode=)
at dlopen.c:87
#17 0x77f5f80c in ?? () from
/usr/lib/x86_64-linux-gnu/libjackserver.so.0
#18 0x77f60a8d in ?? () from
/usr/lib/x86_64-linux-gnu/libjackserver.so.0
#19 0x77f64f5e in jackctl_server_create2 () from
/usr/lib/x86_64-linux-gnu/libjackserver.so.0
#20 0x8111 in ?? ()
#21 0x77a31e4a in __libc_start_main (main=0x75b0, argc=10,
argv=0x7fffe168, init=, fini=,
rtld_fini=, stack_end=0x7fffe158) at ../csu/libc-start.c:314
So this is crashing somewhere during the initialization of libglibmm.
Hence I'm reassigning to libglibmm.
Cheers
>
> The output file is attached (compressed with xz).
>
> I am not familiar with jackd source code, hence I do not fully grasp
> the backtrace, but I seem to understand that the segfault definitely
> has something to do with some dl_open related to jackd2-firewire and
> the libglibmm-2.4-1v5 package.
>
> As I said in another message, jackd works flawlessly, as soon as I
> purge jackd2-firewire .
> Have you had a chance to try and reproduce the bug with jackd2-firewire
> installed (assuming that you had previously tried without that package)?
>
>
> P.S.: I dropped the moreinfo tag from the bug report, as I think I
> provided the requested additional information. Needless to say, feel
> free to re-add the tag, in case you need anything more!
>
> --
> http://www.inventati.org/frx/
> There's not a second to spare! To the laboratory!
> . Francesco Poli .
> GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
--
Processed: Re: Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages
Processing control commands: > tags -1 = Bug #994969 [jackd2] jackd2: segfaults after today's upgrade of other Debian testing packages Removed tag(s) unreproducible. > reassign -1 libglibmm-2.4-1v5 2.66.1-1 Bug #994969 [jackd2] jackd2: segfaults after today's upgrade of other Debian testing packages Bug reassigned from package 'jackd2' to 'libglibmm-2.4-1v5'. No longer marked as found in versions jackd2/1.9.19~dfsg-2. Ignoring request to alter fixed versions of bug #994969 to the same values previously set Bug #994969 [libglibmm-2.4-1v5] jackd2: segfaults after today's upgrade of other Debian testing packages Marked as found in versions glibmm2.4/2.66.1-1. -- 994969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages
Processing control commands: > tags -1 - moreinfo Bug #994969 [jackd2] jackd2: segfaults after today's upgrade of other Debian testing packages Removed tag(s) moreinfo. -- 994969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#994969: jackd2: segfaults after today's upgrade of other Debian testing packages
Control: tags -1 - moreinfo
On Fri, 24 Sep 2021 21:46:57 +0200 Sebastian Ramacher wrote:
[...]
> I haven't tried that yet, but otherwise you can always install -dbgsym
> packages until all symbols are resolved.
I have just tried.
Not sure the Debuginfod method worked fine enough, but here's what I
did.
I first re-installed jackd2-firewire:
# aptitude install jackd2-firewire+M
The following NEW packages will be installed:
jackd2-firewire{a} libconfig++9v5{a} libffado2{a} libxml++2.6-2v5{a}
0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
[...]
Then, as a regular user:
$ export DEBUGINFOD_URLS="https://debuginfod.debian.net;
$ gdb -batch -n -ex 'set pagination off' -ex run -ex bt -ex 'bt full' -ex
'thread apply all bt full' --args jackd --realtime -d alsa --device hw:PCH
--softmode --hwmeter --rate 44100 > jackd_bt.out 2>&1
The output file is attached (compressed with xz).
I am not familiar with jackd source code, hence I do not fully grasp
the backtrace, but I seem to understand that the segfault definitely
has something to do with some dl_open related to jackd2-firewire and
the libglibmm-2.4-1v5 package.
As I said in another message, jackd works flawlessly, as soon as I
purge jackd2-firewire .
Have you had a chance to try and reproduce the bug with jackd2-firewire
installed (assuming that you had previously tried without that package)?
P.S.: I dropped the moreinfo tag from the bug report, as I think I
provided the requested additional information. Needless to say, feel
free to re-add the tag, in case you need anything more!
--
http://www.inventati.org/frx/
There's not a second to spare! To the laboratory!
. Francesco Poli .
GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
jackd_bt.out.xz
Description: application/xz
pgp2sxQXNVl8U.pgp
Description: PGP signature
Bug#992609: careless upload of Erlang v24 without a transition tracking with the release team (was: rabbitmq-server fails to start after erlang v24 update)
On Fri, Aug 27, 2021 at 10:26:39PM +0200, Paul Gevers wrote: > Hi, > > Sorry my previous message was weird. > > On 27-08-2021 22:11, Paul Gevers wrote: > > On 27-08-2021 21:58, Antonio Terceiro wrote: > >> One thing that happens when you do this type of change without > >> coordination is that all CI pipelines on unstable where rabbitmq-server > >> is installed are now broken. For example all merge requests against > >> debci at the moment have their tests in "failed" status. This creates > >> unnecessary noise for a lot of people. > > > > rabbitmq-server already got an update, so unstable should be fine (if > > not, shout (or better, file bugs)). I expect you mean testing, as I > > think that the point is that erlang already migrated before the issue > > was detected, otherwise an RC bug would have prevented the migration. > > > > That's why it was suggested earlier that rabbitmq-server should grow an > > autopkgtest as that have would prevented the migration. > > What I should have said: > we could have prevented migration of erlang until the reverse > dependencies were ready by having an RC bug on erlang. That would have > been totally appropriate if it would have lasted an reasonable time. I > *think* rabbitmq-server has problems migrating now *because* erlang > migrated, but that should clear up once the references are tested again. > However, it *also* has issues with being uninstallable. FWIW, I just did that: I made a new rabbitmq-server upload adding a superficial autopkgtest to rabbitmq-server that just checks if the service is running after installation. This should avoid testing being broken because erlang migrated before rabbitmq-server has been fixed. signature.asc Description: PGP signature
Processed: closing 993138
Processing commands for cont...@bugs.debian.org: > close 993138 3.9.4-1.1 Bug #993138 [rabbitmq-server] rabbitmq-server: uninstallable - typo in Depends: ? Marked as fixed in versions rabbitmq-server/3.9.4-1.1. Bug #993138 [rabbitmq-server] rabbitmq-server: uninstallable - typo in Depends: ? Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 993138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993138: closing 993138
close 993138 3.9.4-1.1 thanks I forgot to close this bug in the changelog.
Bug#995021: osmnx: autopkgtest regression on armhf: iteration over a 0-d array
Hello Paul, thanks for pointing out the issue.
I will try to have a look this week-end.
Cheers,
Jerome
On 24/09/2021 22:23, Paul Gevers wrote:
Source: osmnx
Version: 1.1.1+ds-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of osmnx the autopkgtest of osmnx fails in testing
on armhf when that autopkgtest is run with the binary packages of osmnx
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
osmnx from testing1.1.1+ds-2
all others from testingfrom testing
I copied some of the output at the bottom of this report. On top of the
failure, you test seems to be sending requests to the internet, please
use the needs-internet restriction [0] to mark is as such.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0]
https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst
[1] https://qa.debian.org/excuses.php?package=osmnx
https://ci.debian.net/data/autopkgtest/testing/armhf/o/osmnx/15474259/log.gz
=== FAILURES
===
test_elevation
multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
File "/usr/lib/python3.9/multiprocessing/pool.py", line 125, in worker
result = (True, func(*args, **kwds))
File "/usr/lib/python3.9/multiprocessing/pool.py", line 51, in starmapstar
return list(itertools.starmap(args[0], args[1]))
File
"/tmp/autopkgtest-lxc.2hzrzn35/downtmp/build.elV/src/osmnx/elevation.py", line
49, in _query_raster
return zip(nodes.index, values)
TypeError: iteration over a 0-d array
"""
The above exception was the direct cause of the following exception:
def test_elevation():
G = ox.graph_from_address(address=address, dist=500,
dist_type="bbox", network_type="bike")
rasters = list(Path("tests/input_data").glob("elevation*.tif"))
# add node elevations from a single raster file (some nodes will
be null)
G = ox.elevation.add_node_elevations_raster(G, rasters[0], cpus=1)
# add node elevations from multiple raster files
G = ox.elevation.add_node_elevations_raster(G, rasters)
/usr/share/doc/python-osmnx-doc/examples/tests/test_osmnx.py:201:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
osmnx/elevation.py:98: in add_node_elevations_raster
results = sma.get()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
self = , timeout = None
def get(self, timeout=None):
self.wait(timeout)
if not self.ready():
raise TimeoutError
if self._success:
return self._value
else:
raise self._value
E TypeError: iteration over a 0-d array
/usr/lib/python3.9/multiprocessing/pool.py:771: TypeError
--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B
OpenPGP_signature
Description: OpenPGP digital signature
Processed: Re: Bug#994453: linux-image-5.14.0-trunk-amd64: Kernel hangs at loading initramfs Ryzon based laptop
Processing control commands: > severity -1 important Bug #994453 [src:linux] linux-image-5.14.0-trunk-amd64: Kernel hangs at loading initramfs Ryzon based laptop Severity set to 'important' from 'critical' -- 994453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#994453: linux-image-5.14.0-trunk-amd64: Kernel hangs at loading initramfs Ryzon based laptop
Control: severity -1 important On Thu, Sep 16, 2021 at 10:23:53AM +0200, Gert Wollny wrote: > Package: src:linux > Version: 5.14.3-1~exp1 > Severity: critical > Justification: breaks the whole system No, it does not. The kernel is the system. Bastian
Processed: block 994560 with 995007
Processing commands for cont...@bugs.debian.org: > block 994560 with 995007 Bug #994560 [release.debian.org] transition: libffi 994560 was blocked by: 995044 995045 991096 995036 994560 was not blocking any bugs. Added blocking bug(s) of 994560: 995007 > thanks Stopping processing here. Please contact me if you need assistance. -- 994560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 991096 is serious, tagging 991096, block 994560 with 991096 995044 995036 995045
Processing commands for cont...@bugs.debian.org: > severity 991096 serious Bug #991096 [src:llvm-toolchain-9] fix ftbfs with linux 5.11 Severity set to 'serious' from 'important' > tags 991096 + ftbfs Bug #991096 [src:llvm-toolchain-9] fix ftbfs with linux 5.11 Added tag(s) ftbfs. > block 994560 with 991096 995044 995036 995045 Bug #994560 [release.debian.org] transition: libffi 994560 was not blocked by any bugs. 994560 was not blocking any bugs. Added blocking bug(s) of 994560: 995044, 995036, 991096, and 995045 > thanks Stopping processing here. Please contact me if you need assistance. -- 991096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991096 994560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995045: llvm-toolchain-11: FTBFS with linux 5.14: fatal error: linux/cyclades.h: No such file or directory
Source: llvm-toolchain-11 Version: 1:11.0.1-2 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org | [ 8%] Building CXX object projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_platform_limits_posix.cpp.o | cd /<>/build-llvm/projects/compiler-rt/lib/sanitizer_common && /usr/bin/g++-10 -DHAVE_RPC_XDR_H=0 -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/<>/build-llvm/projects/compiler-rt/lib/sanitizer_common -I/<>/compiler-rt/lib/sanitizer_common -I/<>/build-llvm/include -I/<>/llvm/include -I/<>/compiler-rt/lib/sanitizer_common/.. -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wno-comment -ffunction-sections -fdata-sections -Wall -std=c++14 -Wno-unused-parameter -O2 -DNDEBUG -g1 -m64 -fPIC -fno-builtin -fno-exceptions -fomit-frame-pointer -funwind-tables -fno-stack-protector -fvisibility=hidden -fno-lto -O3 -g -Wno-variadic-macros -Wno-non-virtual-dtor -fno-rtti -Wframe-larger-than=570 -std=c++14 -MD -MT projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_platform_limits_posix.cpp.o -MF CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_platform_limits_posix.cpp.o.d -o CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_platform_limits_posix.cpp.o -c /<>/compiler-rt/lib/sanitizer_common/sanitizer_platform_limits_posix.cpp | /<>/compiler-rt/lib/sanitizer_common/sanitizer_platform_limits_posix.cpp:133:10: fatal error: linux/cyclades.h: No such file or directory | 133 | #include | | ^~ | compilation terminated. See https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-11=amd64=1%3A11.0.1-2%2Bb1=1632526952=0 Cheers -- Sebastian Ramacher
Bug#995044: esorex: FTBFS on mips64el: FAIL: 1
Source: esorex
Version: 3.13.5+ds1-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
esorex failed to build on mips64el:
| FAIL: esorex_python-test
|
|
|
| Start time : 2021-09-24T15:38:49
| Program name : esorex_python-test
| Severity level : [ DEBUG ]
|
| 15:38:49 [ DEBUG ] cpl_test_init_macro: [tid=000] cpl_test_init_macro() was
called with errno=2: No such file or directory (Unless you are debugging code
prior to the cpl_init() call you can ignore this message)
| 15:38:49 [ DEBUG ] cpl_test_init_macro: [tid=000] sizeof(cpl_size): 8
| 15:38:49 [ DEBUG ] cpl_test_init_macro: [tid=000] sizeof(OFF_T)=8
| 15:38:49 [ DEBUG ] cpl_test_init_macro: [tid=000] CPL = 7.1.4, CFITSIO =
3.49, WCSLIB, FFTW (normal precision) = 3.3.8, FFTW (single precision) = 3.3.8,
CPL FLOP counting is unavailable, enable with -DCPL_ADD_FLOPS, OPENMP = 201511
| 15:38:49 [ DEBUG ] main: [tid=000] Test 1 OK at esorex_python-test.c:66:
(setenv("PATH", path, 0x1) == 0) = 1.
| 15:38:49 [ DEBUG ] cpl_errorstate_dump_debug: [tid=000] No error(s) to dump
| 15:38:49 [ DEBUG ] test_error_from_interpreter: [tid=000] Test 2 OK at
esorex_python-test.c:119: (modulelist != NULL) = 1.
| 15:38:49 [ DEBUG ] cpl_errorstate_dump_debug: [tid=000] No error(s) to dump
| 15:38:49 [ DEBUG ] mock_python: [tid=000] Test 3 OK at
esorex_python-test.c:93: (cpl_test_get_failed() == 0) = 1.
| 15:38:49 [ DEBUG ] cpl_errorstate_dump_debug: [tid=000] No error(s) to dump
| 15:38:49 [ DEBUG ] mock_python: [tid=000] Test 4 OK at
esorex_python-test.c:103: (file != NULL) = 1.
| 15:38:49 [ DEBUG ] cpl_errorstate_dump_debug: [tid=000] No error(s) to dump
| 15:38:49 [ DEBUG ] mock_python: [tid=000] Test 5 OK at
esorex_python-test.c:106: (bytes_written == bytes_to_write) = 1.
| 15:38:49 [ DEBUG ] cpl_errorstate_dump_debug: [tid=000] No error(s) to dump
| 15:38:49 [ DEBUG ] mock_python: [tid=000] Test 6 OK at
esorex_python-test.c:108: (fclose_result == 0) = 1.
| 15:38:49 [ DEBUG ] cpl_errorstate_dump_debug: [tid=000] No error(s) to dump
| 15:38:49 [ DEBUG ] mock_python: [tid=000] Test 7 OK at
esorex_python-test.c:112: (chmod("./mock_python_test/python", mode) == 0) = 1.
| 15:38:49 [ DEBUG ] cpl_errorstate_dump_debug: [tid=000] No error(s) to dump
| 15:38:49 [ DEBUG ] run_python_command: [tid=000] Command sent to Python
interpreter:
| import sys, os, json; _data = json.load(os.fdopen(3,'r'));
exec(_data['script'])
| 15:38:49 [ DEBUG ] run_python_command: [tid=000] Input to Python interpreter:
| 15:38:49 [ DEBUG ] run_python_command: [tid=000] 0001 {
| 15:38:49 [ DEBUG ] run_python_command: [tid=000] 0002 "script": "import
inspect\nvalid_modules = {}\nfor path in _data['paths']:\n module =
os.path.splitext(os.path.basename(path))[0]\n
sys.path.append(os.path.dirname(path))\n try:\n__import__(module)\nfor
name, cls in inspect.getmembers(sys.modules[module],
predicate=inspect.isclass):\n if len([base for base in cls.__mro__ if
base.__name__ == 'CplPlugin']) > 0:\nif path not in valid_modules:\n
valid_modules[path] = set()\nvalid_modules[path].add(cls)\n
except:\nimport traceback\ntraceback.print_exc()\n del
sys.path[-1]\nresults = {}\nfor path, clslist in valid_modules.items():\n
results[path] = []\n for cls in clslist:\nplugin = {'class':
cls.__name__}\ntry:\n inst = cls()\nexcept:\n continue\n
try:\n name = inst.name\nexcept:\n name = cls.__name__\n
try:\n version = inst.version\nexcept:\n version = None\n
try:\n synopsis = inst.synopsis
| 15:38:49 [ DEBUG ] run_python_command: [tid=000] 0003 "paths": [
| 15:38:49 [ DEBUG ] run_python_command: [tid=000] 0004 ".\/test.py"
| 15:38:49 [ DEBUG ] run_python_command: [tid=000] 0005 ]
| 15:38:49 [ DEBUG ] run_python_command: [tid=000] 0006 }
| FAIL esorex_python-test (exit status: 141)
See
https://buildd.debian.org/status/fetch.php?pkg=esorex=mips64el=3.13.5%2Bds-1%2Bb1=1632497947=0
Cheers
--
Sebastian Ramacher
Bug#995032: gnome-session segfaults - no GNOME session possible at all (white screen to contact the system administrator)
On Sat, Sep 25, 2021 at 12:30 AM Michael Ott wrote: > The problem is not gnome-shell. It is the gobject-introspection. > After downgrade this packages from 1.70.0-1+b1 to 1.70.0-1 it works > again. gobject-introspection was rebuilt as part of the libffi transition. (That's where the +b1 part of the version name comes from.) The transition is still in progress. Maybe the problem is that you didn't have the rebuilt gjs installed? The rebuilt gjs is version 1.68.4-1+b1 Here's the list of other packages involved in the transition: https://release.debian.org/transitions/html/auto-libffi.html Thanks, Jeremy Bicha
Bug#994921: marked as done (librnd3-dev: missing Breaks+Replaces: librnd-dev)
Your message dated Sat, 25 Sep 2021 06:18:47 +
with message-id
and subject line Bug#994921: fixed in librnd 3.0.0-3
has caused the Debian Bug report #994921,
regarding librnd3-dev: missing Breaks+Replaces: librnd-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.)
--
994921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librnd3-dev
Version: 3.0.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'bullseye'.
It installed fine in 'bullseye', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>From the attached log (scroll to the bottom...):
Preparing to unpack .../librnd3-dev_3.0.0-2_amd64.deb ...
Unpacking librnd3-dev (3.0.0-2) ...
dpkg: error processing archive
/var/cache/apt/archives/librnd3-dev_3.0.0-2_amd64.deb (--unpack):
trying to overwrite '/usr/include/librnd/config.h', which is also in package
librnd-dev 2.3.1-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/librnd3-dev_3.0.0-2_amd64.deb
I'm not sure whether it would be helpful, but a (versioned?)
Provides: librnd-dev (= ${binary:Version})
could ease upgrading from librnd-dev to librnd3-dev.
BTW, why has the -dev package been renamed from librnd-dev to librnd3-dev?
It's not for co-installability of new and old versions since librnd-dev
was removed from sid.
cheers,
Andreas
librnd-dev=2.3.1-1_librnd3-dev=3.0.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: librnd
Source-Version: 3.0.0-3
Done: Bdale Garbee
We believe that the bug you reported is fixed in the latest version of
librnd, 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 994...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bdale Garbee (supplier of updated librnd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 25 Sep 2021 00:01:00 -0600
Source: librnd
Architecture: source
Version: 3.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Electronics Team
Changed-By: Bdale Garbee
Closes: 994921
Changes:
librnd (3.0.0-3) unstable; urgency=medium
.
* add breaks/replaces/provides to improve librnd3-dev replacement of
librnd-dev, closes: #994921
Checksums-Sha1:
5e4167c4263efb669e762c414d4da0125a5e83df 2594 librnd_3.0.0-3.dsc
ea92bd60f02c4a14ab61ba6a7951131c231c6f6d 7188 librnd_3.0.0-3.debian.tar.xz
7dca35ff490cbda2285747e04161ac367879cb83 18331 librnd_3.0.0-3_amd64.buildinfo
Checksums-Sha256:
005843a17442c50826b03fce79071428011ae2f23843f65bb12e91cd1f53ec8e 2594
librnd_3.0.0-3.dsc
295c4693a76c98de638fff4924b696d4d1ccd7d765d508f1d76f6f9822c3d729 7188
librnd_3.0.0-3.debian.tar.xz
cf13ac3578d2ad3cbf251d9200897abd123b56794768873091f8bf63e4f9c0dc 18331
librnd_3.0.0-3_amd64.buildinfo
Files:
4259e71239f51735958d1d122388e008 2594 electronics optional librnd_3.0.0-3.dsc
996e83e6f026cf9d55f77ba0ad02a6b2 7188 electronics optional
librnd_3.0.0-3.debian.tar.xz
5874c30eeaa2b4414d1ff93a15e19c2d 18331 electronics optional
librnd_3.0.0-3_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEHguq2FwiMqGzzpLrtwRxBYMLn6EFAmFOvDsACgkQtwRxBYML
n6GJ5Q//ZHYb31MuJ5Dwxmw/MbW7Q18XCmZLNoxrwuF8Ik9bFxRvykz5eeEp3PG2
xhlXphLZc5MmKjasLaYVmREd3TN1J1uahxzEpjsgGqepUEc0/7AGRiLXMiPuIEXf
lW8bxd4PRzZmszwUX3tAFH3qdn6R7jFhz+B0eQew5vmt8vIKu91RpTJCjc8fXG4d
L0n9vQMvEmbBb9wRVnN/lZ3g6tRQwp1vhjcpFtJGAjIpFxQM+lv3CXarEmNZhW9p
uX4tQfb67e+qg5J2EWbLiYuzCLiFqiqL2hAQEJ4jkWghdSNmTWIm/KGcepfM5DKr
uuGvUooUg4C3uHXltRXMqqzHKh601dwyhUbMOU11dLPWXWQqzouP+Y6afCPdoQNp
Xp8rbgxCbYQraDLdsHOhnuOh/0DumKPIsVtGFsSOIDBwfwvxs9M0qECCltVvMYCp
4L2sUAnN0GOJtki7V2PhdULhfiXBUJEW+wQfR12RqI1hgZ+Rt7o+jQYD5H/xJuXZ
Fa8Dh1B64saAGtxO5/I5JIDUTIoHUhLW0sl69O/Ap1rRvq+42z6tOabbFrhOqgaP
Bug#995032:
I have the same problem since updating today. I don't have gobject-inspection installed but I see segfault with libglib2.0-0. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#995040: iverilog FTBFS: configure: error: C preprocessor "/lib/cpp" fails sanity check
Source: iverilog Version: 11.0-1 Severity: serious Tags: ftbfs iverilog fails to build from source in unstable on amd64. I'm not exactly sure what the relevant parts of the build log are. Here is my guess: | ... | checking how to run the C preprocessor... /lib/cpp | configure: error: in `/<>': | configure: error: C preprocessor "/lib/cpp" fails sanity check | See `config.log' for more details | tail -v -n \+0 config.log | ==> config.log <== | ... | configure:8905: result: /lib/cpp | configure:8919: -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c | ./configure: line 2189: -Wdate-time: command not found | configure:8919: $? = 127 | ... | configure:8952: error: in `/<>': | configure:8954: error: C preprocessor "/lib/cpp" fails sanity check | See `config.log' for more details | ... Seems to reproduce reliably. Also seen in cross builds: http://crossqa.debian.net/build/iverilog_11.0-1_amd64_20210825212934.log Hope this helps. Helmut
Bug#995038: ddccontrol FTBFS: autoreconf: error: intltoolize failed with exit status: 1
Source: ddccontrol Version: 0.4.4-1.2 Severity: serious Tags: ftbfs ddccontrol fails to build from source in unstable on amd64. A build ends as follows: |debian/rules override_dh_autoreconf | make[1]: Entering directory '/<>' | ./autogen.sh | Running autoreconf... | Copying file ABOUT-NLS | Copying file config.rpath | Creating directory m4 | Copying file m4/codeset.m4 | Copying file m4/fcntl-o.m4 | Copying file m4/gettext.m4 | Copying file m4/glibc2.m4 | Copying file m4/glibc21.m4 | Copying file m4/iconv.m4 | Copying file m4/intdiv0.m4 | Copying file m4/intl.m4 | Copying file m4/intldir.m4 | Copying file m4/intlmacosx.m4 | Copying file m4/intmax.m4 | Copying file m4/inttypes-pri.m4 | Copying file m4/inttypes_h.m4 | Copying file m4/lcmessage.m4 | Copying file m4/lib-ld.m4 | Copying file m4/lib-link.m4 | Copying file m4/lib-prefix.m4 | Copying file m4/lock.m4 | Copying file m4/longlong.m4 | Copying file m4/nls.m4 | Copying file m4/po.m4 | Copying file m4/printf-posix.m4 | Copying file m4/progtest.m4 | Copying file m4/size_max.m4 | Copying file m4/stdint_h.m4 | Copying file m4/threadlib.m4 | Copying file m4/uintmax_t.m4 | Copying file m4/visibility.m4 | Copying file m4/wchar_t.m4 | Copying file m4/wint_t.m4 | Copying file m4/xsize.m4 | Copying file po/Makefile.in.in | Copying file po/Makevars.template | Copying file po/Rules-quot | libtoolize: putting auxiliary files in '.'. | libtoolize: copying file './ltmain.sh' | libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. | libtoolize: copying file 'm4/libtool.m4' | libtoolize: copying file 'm4/ltoptions.m4' | libtoolize: copying file 'm4/ltsugar.m4' | libtoolize: copying file 'm4/ltversion.m4' | libtoolize: copying file 'm4/lt~obsolete.m4' | intltoolize: 'po/Makefile.in.in' exists: use '--force' to overwrite | intltoolize: 'po/Makefile.in.in' is out of date: use '--force' to overwrite | autoreconf: error: intltoolize failed with exit status: 1 | make[1]: *** [debian/rules:12: override_dh_autoreconf] Error 1 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:9: build] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Helmut
Bug#994921: [Pkg-electronics-devel] Bug#994921: librnd3-dev: missing Breaks+Replaces: librnd-dev
Andreas Beckmann writes:
> I'm not sure whether it would be helpful, but a (versioned?)
> Provides: librnd-dev (= ${binary:Version})
> could ease upgrading from librnd-dev to librnd3-dev.
Yes, that makes sense.
> BTW, why has the -dev package been renamed from librnd-dev to librnd3-dev?
> It's not for co-installability of new and old versions since librnd-dev
> was removed from sid.
Upstream anticipates that it will be useful to have librnd3-dev and
librnd4-dev able to co-exist once librnd4 is released in the future, so
recommended I change the package name to avoid future confusion.
Bdale
signature.asc
Description: PGP signature
