Bug#1069382: libxcb: FTBFS on arm64: KeyError: 'xcb_redirect_t'
Is there any way to fix or work around this? It's been blocking new version of obs-studio from entering testing for a while. Thanks! Shmerl.
Bug#1071007:
All -- ::: Re: 1071007, ALL CONCERNED ::: I am associated with the upstream project. This is a real bug. Discovered it some time last week. This seems to have been introduced when we added the new pyproject file with a setuptools backend. For some unknown reason, the installed package would dump its files into either the dist-packages/site-packages dir rather than a package-named subdir, or it would for even more mysterious reasons dump the src files into _both_ dirs at the same time. This behavior was present no matter the install method -- whether pip, rpm, etc. I have resolved this bug in upstream PR #2111 (below), with a switch from setuptools to Poetry, among several other more minor tasks. This PR is currently undergoing review, but I expect it to be merged shortly. Once merged, the packager here can pull and repack (or they can patch to in the interim). https://github.com/sherlock-project/sherlock/pull/2111 ::: FOR THE PKG MAINTAINER ::: Since Poetry doesn't support dynamic versioning in the same way setuptools did, that part of the workflow has to change a bit once this PR is merged. Dynamic versioning now occurs via `poetry build` with the `poetry-version-plugin` plugin installed alongside. Since many automated workflows rely on pip, you may need to adapt it slightly. Reference the spec file here for an example of how I adapted the rpm build workflow for this. L43 and L44 run a quick sed to fetch and populate the version number from the __init__ as the single source of truth. https://github.com/ppfeister/pkg/blob/3959a6ef6c8a2318ae183a8e5d85241eb8f756bf/sherlock/sherlock-project.spec If you're able to use Poetry with plugins as part of your workflow, then that change may be moot. ::: ALL /> ::: Feel free to reach out if you have any questions.
Bug#1071007: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py
Em sáb., 18 de mai. de 2024 às 21:08, Samuel Henrique escreveu: > > Control: reopen -1 = > > I see on git that the bug was closed with a Conflicts+Replaces stanza, but > that's not the correct solution for this issue. > > As discussed on this bugreport, the fix is to not ship the file. > > Reopening to block the problematic package to migrate to testing. > > Cheers, > > -- > Samuel Henrique > In addition, 'Conflicts' is a very extreme solution for many use cases. Eriberto
Bug#1071313: marked as done (guestfs-tools: FTBFS: guestfsd: error: minix: /dev/sda1: mkfs: failed to execute mkfs.minix: No such file or directory)
Your message dated Sun, 19 May 2024 01:19:38 + with message-id and subject line Bug#1071313: fixed in libguestfs 1:1.52.0-6 has caused the Debian Bug report #1071313, regarding guestfs-tools: FTBFS: guestfsd: error: minix: /dev/sda1: mkfs: failed to execute mkfs.minix: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1071313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071313 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:guestfs-tools Version: 1.52.0-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead dh_autoreconf configure.ac: warning: AM_GNU_GETTEXT is used, but not AM_GNU_GETTEXT_VERSION or AM_GNU_GETTEXT_REQUIRE_VERSION libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'. libtoolize: copying file 'build-aux/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' [... snipped ...] /dev/disk/by-diskseq: total 0 lrwxrwxrwx 1 0 0 9 May 17 18:30 1 -> ../../sda lrwxrwxrwx 1 0 0 9 May 17 18:30 2 -> ../../sdb /dev/disk/by-id: total 0 lrwxrwxrwx 1 0 0 9 May 17 18:30 scsi-0QEMU_QEMU_HARDDISK_appliance -> ../../sdb lrwxrwxrwx 1 0 0 9 May 17 18:30 scsi-0QEMU_QEMU_HARDDISK_hd0 -> ../../sda /dev/disk/by-path: total 0 lrwxrwxrwx 1 0 0 9 May 17 18:30 pci-:00:02.0-scsi-0:0:0:0 -> ../../sda lrwxrwxrwx 1 0 0 9 May 17 18:30 pci-:00:02.0-scsi-0:0:1:0 -> ../../sdb /dev/disk/by-uuid: total 0 lrwxrwxrwx 1 0 0 9 May 17 18:30 b6cf2551-a800-4675-b55b-ad7f7474d0ac -> ../../sdb /dev/input: total 0 crw--- 1 0 0 13, 63 May 17 18:30 mice /dev/mapper: total 0 crw--- 1 0 0 10, 236 May 17 18:30 control /dev/net: total 0 crw-rw-rw- 1 0 0 10, 200 May 17 18:30 tun /dev/pts: total 0 c- 1 0 0 5, 2 May 17 18:30 ptmx /dev/shm: total 0 /dev/snd: total 0 crw--- 1 0 0 116, 1 May 17 18:30 seq crw--- 1 0 0 116, 33 May 17 18:30 timer /dev/vfio: total 0 crw-rw-rw- 1 0 0 10, 196 May 17 18:30 vfio /dev/virtio-ports: total 0 lrwxrwxrwx 1 0 0 11 May 17 18:30 org.libguestfs.channel.0 -> ../vport2p1 + cat /proc/mounts /dev/root / ext2 rw,noatime 0 0 /proc /proc proc rw,relatime 0 0 /sys /sys sysfs rw,relatime 0 0 /dev /dev devtmpfs rw,relatime,size=616296k,nr_inodes=154074,mode=755,inode64 0 0 /dev/pts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0 shmfs /dev/shm tmpfs rw,relatime,inode64 0 0 tmpfs /run tmpfs rw,nosuid,relatime,size=249604k,mode=755,inode64 0 0 + cat /proc/mdstat cat: /proc/mdstat: No such file or directory + lvm config + lvm pvs + lvm vgs + lvm lvs + ip a 1: \x1b[36mlo: \x1b[0m mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback \x1b[33m00:00:00:00:00:00\x1b[0m brd \x1b[33m00:00:00:00:00:00\x1b[0m inet \x1b[35m127.0.0.1\x1b[0m/8 brd \x1b[35m127.255.255.255 \x1b[0mscope host lo valid_lft forever preferred_lft forever inet6 \x1b[34m::1\x1b[0m/128 scope host proto kernel_lo valid_lft forever preferred_lft forever + ip r + cat /etc/resolv.conf cat: /etc/resolv.conf: No such file or directory + lsmod Module Size Used by dm_mod221184 0 sg 45056 0 virtio_snd 40960 0 snd_pcm 192512 1 virtio_snd snd_timer 53248 1 snd_pcm snd 155648 3 virtio_snd,snd_timer,snd_pcm soundcore 16384 1 snd libcrc32c 12288 0 crc8 12288 0 crc7 12288 0 crc_itu_t 12288 0 ext4 1130496 1 crc16 12288 1 ext4 mbcache16384 1 ext4 jbd2 196608 1 ext4 virtio_vdpa16384 0 vdpa 36864 1 virtio_vdpa virtio_mmio16384 0 virtio_mem 49152 0 virtio_input 16384 0 virtio_dma_buf 12288 0 virtio_balloon 32768 0 virtio_scsi28672 1 sd_mod
Processed: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py
Processing control commands:
> reopen -1 =
Bug #1071007 {Done: Josenilson Ferreira da Silva }
[sherlock] sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions sherlock/0.14.3+git20240515.0ecb496-1.
--
1071007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1071007: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py
Control: reopen -1 = I see on git that the bug was closed with a Conflicts+Replaces stanza, but that's not the correct solution for this issue. As discussed on this bugreport, the fix is to not ship the file. Reopening to block the problematic package to migrate to testing. Cheers, -- Samuel Henrique
Bug#1071007: marked as done (sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py)
Your message dated Sat, 18 May 2024 23:34:18 + with message-id and subject line Bug#1071007: fixed in sherlock 0.14.3+git20240515.0ecb496-1 has caused the Debian Bug report #1071007, regarding sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py 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.) -- 1071007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sherlock Version: 0.14.3+git20240511.b83f5be-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + pycrc sherlock has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/python3/dist-packages/__init__.py is contained in the packages * pycrc/0.10.0-2 as present in trixie|unstable * sherlock/0.14.3+git20240511.b83f5be-1 as present in unstable These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected file. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. --- End Message --- --- Begin Message --- Source: sherlock Source-Version: 0.14.3+git20240515.0ecb496-1 Done: Josenilson Ferreira da Silva We believe that the bug you reported is fixed in the latest version of sherlock, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josenilson Ferreira da Silva (supplier of updated sherlock 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, 18 May 2024 19:10:45 -0300 Source: sherlock Architecture: source Version: 0.14.3+git20240515.0ecb496-1 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Josenilson Ferreira da Silva Closes: 1071007 Changes: sherlock (0.14.3+git20240515.0ecb496-1) unstable; urgency=medium . * New upstream version 0.14.3+git20240515.0ecb496 * debian/control: - Bumped Standards-Version to 4.7.0 - Tags added for conflict resolution with pycrc package (Closes: #1071007) * debian/docs: - README.md moved to 'docs' directory in new version Checksums-Sha1: 145e81570257305a43fe391b9487c04799a49729 2431 sherlock_0.14.3+git20240515.0ecb496-1.dsc 5d47e02e0653bc25ac4dbf4876806a8675bf0ab5 187092 sherlock_0.14.3+git20240515.0ecb496.orig.tar.xz 44a94897173d4bc3e64f9d30d07bf44d411bae58 5276 sherlock_0.14.3+git20240515.0ecb496-1.debian.tar.xz 06a5cc1f4d2c4fd827e2f2e35fb73379629911e5 9416 sherlock_0.14.3+git20240515.0ecb496-1_source.buildinfo Checksums-Sha256: 7c310f9af8145ad5bc7ed0095ccdadc911f168325ef92c5348461b34676e3c5a 2431 sherlock_0.14.3+git20240515.0ecb496-1.dsc d0ac603d7ac7d0a055686c85874ebd3aed5aab3097c56193f5f94a48eca7e555 187092 sherlock_0.14.3+git20240515.0ecb496.orig.tar.xz 71bc18c8db59b0d2bb8a1f7f1548335ddc63f89b96ffcd91c00b43070672721c 5276 sherlock_0.14.3+git20240515.0ecb496-1.debian.tar.xz 6ec77ae7741ea83f0132954a8e87e47e95e7a724c4faf63c3cb97a1707c9 9416 sherlock_0.14.3+git20240515.0ecb496-1_source.buildinfo Files: 17e1ff96468cfecdb3862d398c8f0424 2431 misc optional sherlock_0.14.3+git20240515.0ecb496-1.dsc b097112bbb62b02fdbf42b5d963e053c 187092 misc optional sherlock_0.14.3+git20240515.0ecb496.orig.tar.xz f5ec1b9c2a6ac82dcd07bd55a918bd3b 5276 misc optional sherlock_0.14.3+git20240515.0ecb496-1.debian.tar.xz 4084cc682d59780ef056cbf9f2565885 9416 misc optional sherlock_0.14.3+git20240515.0ecb496-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEqBlNXRF+LQLfMNMNB6n1YjE0Rs0FAmZJNiwACgkQB6n1YjE0 Rs2WSg/8CtUgKtL2+2xJ13KTx//9sijA8IdH17IPfvpqJlAOJXl0zeyjPjxbjEIo D1W7X1CEHoVyme6NH0vLbrwIkvBVGIwuMFLVoUwcLiAXHXhKKTUHhi7WBmF2WZsn
Bug#983365: linphone-desktop: chat messages
Control: severity -1 important This bugs seems to be at least partially fixed, at least it seems that the messages are now showing up, so this bug should no longer be RC. (If I'm wrong, severity can be readjusted if needed) -- tobi
Processed: Re: linphone-desktop: chat messages
Processing control commands: > severity -1 important Bug #983365 [src:linphone] linphone-desktop: chat messages Severity set to 'important' from 'grave' -- 983365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 1071416 in 1.2.5-2
Processing commands for cont...@bugs.debian.org: > fixed 1071416 1.2.5-2 Bug #1071416 [gogglesmm] gogglesmm: FTBFS for armel, x390x and more Marked as fixed in versions gogglesmm/1.2.5-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1071416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071416: gogglesmm: FTBFS for armel, x390x and more
Package: gogglesmm Version: 1.2.5-1 Severity: serious Tags: upstream ftbfs help Justification: fails to build from source on some architectures Forwarded: https://github.com/gogglesmm/gogglesmm/issues/118 This is for documentation https://buildd.debian.org/status/logs.php?pkg=gogglesmm=1.2.5-1 This has been forwarded upstream https://github.com/gogglesmm/gogglesmm/issues/118 but maybe someone can help out? For the time being I uploaded a new version 1.2.5-2 which is only for the known working architectures. Cord
Processed: tagging 1071321
Processing commands for cont...@bugs.debian.org: > # yeah, confirmed via sbuild, and I will further investigate the next chance > I get > tags 1071321 + confirmed Bug #1071321 [src:libdumbnet] libdumbnet: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1071321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071413: src:rust-debversion: fails to migrate to testing for too long: RC buggy Depends
Source: rust-debversion Version: 0.2.2-1 Severity: serious Control: close -1 0.3.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:rust-debversion has been trying to migrate for 70 days [2]. Hence, I am filing this bug. The version in unstable apparently has a new dependency chain that ends with rust-rsa which has an unresolved RC security issue and isn't migrating to testing. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=rust-debversion OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:rust-debversion: fails to migrate to testing for too long: RC buggy Depends
Processing control commands: > close -1 0.3.0-1 Bug #1071413 [src:rust-debversion] src:rust-debversion: fails to migrate to testing for too long: RC buggy Depends Marked as fixed in versions rust-debversion/0.3.0-1. Bug #1071413 [src:rust-debversion] src:rust-debversion: fails to migrate to testing for too long: RC buggy Depends Marked Bug as done -- 1071413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071413 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071412: src:tracker: fails to migrate to testing for too long: autopkgtest regression
Source: tracker Version: 3.4.2-3 Severity: serious Control: close -1 3.7.3-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1068468 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:tracker has been trying to migrate for 71 days [2]. Hence, I am filing this bug. The version in unstable fails its own autopkgtest as reported in bug 1068468. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=tracker OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:tracker: fails to migrate to testing for too long: autopkgtest regression
Processing control commands:
> close -1 3.7.3-1
Bug #1071412 [src:tracker] src:tracker: fails to migrate to testing for too
long: autopkgtest regression
Marked as fixed in versions tracker/3.7.3-1.
Bug #1071412 [src:tracker] src:tracker: fails to migrate to testing for too
long: autopkgtest regression
Marked Bug as done
> block -1 by 1068468
Bug #1071412 {Done: Paul Gevers } [src:tracker] src:tracker:
fails to migrate to testing for too long: autopkgtest regression
1071412 was not blocked by any bugs.
1071412 was not blocking any bugs.
Added blocking bug(s) of 1071412: 1068468
--
1071412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1070237: marked as done (wsclean: error while loading shared libraries: libradler.so: cannot open shared object file)
Your message dated Sat, 18 May 2024 18:34:39 + with message-id and subject line Bug#1070237: fixed in wsclean 3.4-2 has caused the Debian Bug report #1070237, regarding wsclean: error while loading shared libraries: libradler.so: cannot open shared object file 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.) -- 1070237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wsclean Version: 3.4-1+b2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: offri...@gmail.com Dear Maintainer, There is something wrong with the packaging of WSClean; running WSClean fails with the following error: wsclean: error while loading shared libraries: libradler.so: cannot open shared object file: No such file or directory Radler is a component of wsclean that is normally compiled along wsclean, linked into a static library and subsequently linked into the wsclean binary. I think that Debian's WSClean package builds radler as a shared object, but does not ship the library. Thanks, André -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_NL.UTF-8, LC_CTYPE=en_NL.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wsclean depends on: ii libboost-filesystem1.83.0 1.83.0-2+b2 ii libc6 2.37-18 ii libcasa-casa7 3.5.0-2+b3 ii libcasa-fits7 3.5.0-2+b3 ii libcasa-measures7 3.5.0-2+b3 ii libcasa-ms7 3.5.0-2+b3 ii libcasa-tables7 3.5.0-2+b3 ii libcfitsio10t64 [libcfitsio10] 4.3.1-1.1+b1 ii libfftw3-double33.3.10-1+b1 ii libfftw3-single33.3.10-1+b1 ii libgcc-s1 14-20240330-1 ii libgsl272.7.1+dfsg-6+b1 ii libhdf5-103-1 1.10.10+repack-3+b1 ii libhdf5-cpp-103-1 1.10.10+repack-3+b1 ii libstdc++6 14-20240330-1 wsclean recommends no packages. Versions of packages wsclean suggests: pn wsclean-dev -- no debconf information --- End Message --- --- Begin Message --- Source: wsclean Source-Version: 3.4-2 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of wsclean, 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 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ole Streicher (supplier of updated wsclean 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, 18 May 2024 17:35:57 +0200 Source: wsclean Architecture: source Version: 3.4-2 Distribution: unstable Urgency: medium Maintainer: Debian Astro Team Changed-By: Ole Streicher Closes: 1070237 Changes: wsclean (3.4-2) unstable; urgency=medium . * Link Radler a static instead of shared library. Closes: #1070237 * Push Standards-Version to 4.7.0. No changes needed * Add superficial autopkgtest Checksums-Sha1: 49fcac57260096d7de08a24dbc5e06f81089e43e 2275 wsclean_3.4-2.dsc 98bc6e9d1c76c6b65b6d979b93de290b3b8e4e50 13808 wsclean_3.4-2.debian.tar.xz Checksums-Sha256: b61c50b7fc1cda8f57a7c5f1c46b3ae113da832bde3ad7502cea51beac8e7c1d 2275 wsclean_3.4-2.dsc e0ea6b60e61e92929ef3ded25be5399cd066647be16aac4241f93dbde8fbcfab 13808 wsclean_3.4-2.debian.tar.xz Files: fe1079e0d49085129dc1c392ab2cf589 2275 science optional wsclean_3.4-2.dsc 108a1ba00dbdde5a5dd2ade94672058a 13808 science optional wsclean_3.4-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE7/BpV0Ra2/h0L3qtmk9WvbkOGL0FAmZI0TEACgkQmk9WvbkO GL3O2Q//Vz+liMtV+F6CRXzsLxEWXm2xyJxxNqmyXrfnkODeW3HvZDnMBqTxT6Wp FtFGYeiCw9zsGTFoFGErTnqYoXKOYFOAPfSwQPH/IA6473OTWn3Ik0/J+RS+I3DW SEF1dyBQeoychssXV2/UAAwuI7i7lmUvuYuG2oPKnhJfbLREFkgiFswIigIlj4Jq
Processed: src:diffoscope: fails to migrate to testing for too long: FTBFS and blocked by Build-Depends
Processing control commands: > close -1 267 Bug #1071410 [src:diffoscope] src:diffoscope: fails to migrate to testing for too long: FTBFS and blocked by Build-Depends The source 'diffoscope' and version '267' do not appear to match any binary packages Marked as fixed in versions diffoscope/267. Bug #1071410 [src:diffoscope] src:diffoscope: fails to migrate to testing for too long: FTBFS and blocked by Build-Depends Marked Bug as done -- 1071410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071410: src:diffoscope: fails to migrate to testing for too long: FTBFS and blocked by Build-Depends
Source: diffoscope Version: 259 Severity: serious Control: close -1 267 Tags: sid trixie ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:diffoscope has been trying to migrate for 71 days [2]. Hence, I am filing this bug. The version in unstable failed to build and is also blocked by apktool, which was removed from testing due to an unresolved RC bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=diffoscope OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:fakeroot: fails to migrate to testing for too long: FTBFS on armel, armhf
Processing control commands: > close -1 1.34-1 Bug #1071409 [src:fakeroot] src:fakeroot: fails to migrate to testing for too long: FTBFS on armel, armhf Marked as fixed in versions fakeroot/1.34-1. Bug #1071409 [src:fakeroot] src:fakeroot: fails to migrate to testing for too long: FTBFS on armel, armhf Marked Bug as done -- 1071409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071409: src:fakeroot: fails to migrate to testing for too long: FTBFS on armel, armhf
Source: fakeroot Version: 1.33-1 Severity: serious Control: close -1 1.34-1 Tags: sid trixie ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:fakeroot has been trying to migrate for 73 days [2]. Hence, I am filing this bug. The version in unstable failed to build on armel and armhf. On reproducible-builds, a build on i386, arm64 and armhf today also failed (only amd64 passed). If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=fakeroot OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1070237: wsclean: error while loading shared libraries: libradler.so: cannot open shared object file
Hi Andre, thank you for the patch! I now created a new version with the patch and uploaded it. I also added a simple test as you proposed. Indeed, I normally just take the tarball from the repository and if I cant directly find a later fix, I ask upstream about what to do :-) CMake is still a bit of a mystery to me... Cheers Ole Am 18.05.24 um 15:38 schrieb André Offringa: Hi Ole, Thanks for looking into this. I did some analysis and found that Radler was in fact still build as static library in wsclean version 3.4. This was corrected only in: - https://git.astron.nl/RD/radler/-/merge_requests/123 and - https://gitlab.com/aroffringa/wsclean/-/merge_requests/591 These were merged only after releasing v3.4. My bug report was therefore not accurate in assuming that this was caused by a Debian setting. To make WSClean 3.4 work, either those commits would have to be applied to the code base to link radler statically, or the libradler.so library needs to be shipped along with wsclean. The first option I have tested with the script provided below in a wsclean v3.4 git cloned directory, and that works. I guess you're not checking out the git repositories in the Debian build so I've also made a patch that can be applied with "patch -s -p1 < link-radler-statically.patch" from the wsclean v3.4 dir. It's attached to this mail. I hope this patch suffices for the Debian build, otherwise let me know if I can do something else to help. When we release a newer wsclean version, the patch is no longer necessary. However, the release of wsclean v3.5 will probably take some time, and does have quite some changes, so a 3.4 build would be nice. Another thing: would it be possible to run 'wsclean --version' in the build just to see if it succeeds? That should at least catch any linking issues like here. There's also a much bigger wsclean test-suite, but that might be a bit overkill for Debian, as it takes a considerable amount of time and resources to run, and getting the tests correctly through all debian platforms will be a bit challenging I think (not unlike Casacore, whose tests are actually somewhat less demanding). Thanks for your help, Ole! Regards, André # Building WSClean 3.4 with Radler as static library # Make sure submodules are present and at the right commit # (not sure this is necessary in the Debian build) mkdir build cd build cmake .. cd .. # Merge https://gitlab.com/aroffringa/wsclean/-/merge_requests/591 git cherry-pick 45c51219c0ea2deafb5de9edf2dddfda509f779b # Merge https://git.astron.nl/RD/radler/-/merge_requests/123 cd external/radler git cherry-pick 7fec4c029d62dcb664d894eae6909fa4ca92b642 cd ../../build make -j`nproc`
Processed (with 2 errors): Re: Bug#1070618: phpcpd: FTBFS with phpunit 11: There were 7 PHPUnit errors
Processing control commands: > severity -1 serious Bug #1070618 [src:phpcpd] phpcpd: FTBFS with phpunit 11: There were 7 PHPUnit errors Severity set to 'serious' from 'normal' > user debian-rele...@lists.debian.org Unknown command or malformed arguments to command. > usertag -1 bsp-2024-05-mdc-ber Unknown command or malformed arguments to command. -- 1070618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:geoalchemy2: fails to migrate to testing for too long: B-D on mysql which isn't allowed to migrate
Processing control commands: > close -1 0.14.6-1 Bug #1071403 [src:geoalchemy2] src:geoalchemy2: fails to migrate to testing for too long: B-D on mysql which isn't allowed to migrate Marked as fixed in versions geoalchemy2/0.14.6-1. Bug #1071403 [src:geoalchemy2] src:geoalchemy2: fails to migrate to testing for too long: B-D on mysql which isn't allowed to migrate Marked Bug as done -- 1071403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071403: src:geoalchemy2: fails to migrate to testing for too long: B-D on mysql which isn't allowed to migrate
Source: geoalchemy2 Version: 0.13.3-2 Severity: serious Control: close -1 0.14.6-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:geoalchemy2 has been trying to migrate for 73 days [2]. Hence, I am filing this bug. The version in unstable build depends on mysql, which for security support isn't allowed to migrate (Debian has MariaDB). If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=geoalchemy2 OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:gnome-shell-extension-arc-menu: fails to migrate to testing for too long: unsatisfiable dependency
Processing control commands: > close -1 55-1 Bug #1071402 [src:gnome-shell-extension-arc-menu] src:gnome-shell-extension-arc-menu: fails to migrate to testing for too long: unsatisfiable dependency Marked as fixed in versions gnome-shell-extension-arc-menu/55-1. Bug #1071402 [src:gnome-shell-extension-arc-menu] src:gnome-shell-extension-arc-menu: fails to migrate to testing for too long: unsatisfiable dependency Marked Bug as done -- 1071402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071402 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071402: src:gnome-shell-extension-arc-menu: fails to migrate to testing for too long: unsatisfiable dependency
Source: gnome-shell-extension-arc-menu Version: 49+forkv29-4 Severity: serious Control: close -1 55-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:gnome-shell-extension-arc-menu has been trying to migrate for 75 days [2]. Hence, I am filing this bug. The version in unstable has unsatisfiable dependencies. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=gnome-shell-extension-arc-menu OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071401: src:cross-toolchain-base-mipsen: unsatisfied build dependency in testing: linux-source-6.6 (>= 6.6.11)
Source: cross-toolchain-base-mipsen Version: 27 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071399: src:ndcube: unsatisfied build dependency in testing: python3-sunpy
Source: ndcube Version: 2.2.0-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071400: src:specutils: unsatisfied build dependency in testing: python3-spectral-cube
Source: specutils Version: 1.14.0-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071398: src:tea-cli: unsatisfied build dependency in testing: golang-github-go-git-go-git-dev
Source: tea-cli Version: 0.9.2-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1071397: src:ngspetsc: unsatisfied build dependency in testing: fenicsx
Source: ngspetsc Version: 0.0~git20240318.f83b50a-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: bug 1071165 is forwarded to https://github.com/ashmanix/obs-plugin-countdown/issues/62
Processing commands for cont...@bugs.debian.org: > forwarded 1071165 https://github.com/ashmanix/obs-plugin-countdown/issues/62 Bug #1071165 [obs-ashmanix-countdown] obs-ashmanix-countdown: import conflict, plugin not starting on obs 30.1.2.1-1 Set Bug forwarded-to-address to 'https://github.com/ashmanix/obs-plugin-countdown/issues/62'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1071165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1071165 is grave
Processing commands for cont...@bugs.debian.org: > severity 1071165 grave Bug #1071165 [obs-ashmanix-countdown] obs-ashmanix-countdown: import conflict, plugin not starting on obs 30.1.2.1-1 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1071165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071362: rpy2 segfaults in tests under Debian bulk rebuild
On 18 May 2024 at 07:59, Dirk Eddelbuettel wrote: | | Hi Laurent, | | We a build issue in Debian found via bulk rebuilds. Which everything current | in 'unstable', rpy2 (version 3.5.16) segfaults in a test when embedding. | | Details are at https://bugs.debian.org/1071362 | | If you kee 1071...@bugs.debian.org in the email headers replies will get | appended there. Let me know if I can help in any way. And simplest to reply-all to this now that the forwarding has been registered. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1070237: wsclean: error while loading shared libraries: libradler.so: cannot open shared object file
Hi Ole,
Thanks for looking into this. I did some analysis and found that Radler
was in fact still build as static library in wsclean version 3.4. This
was corrected only in:
- https://git.astron.nl/RD/radler/-/merge_requests/123
and
- https://gitlab.com/aroffringa/wsclean/-/merge_requests/591
These were merged only after releasing v3.4. My bug report was therefore
not accurate in assuming that this was caused by a Debian setting.
To make WSClean 3.4 work, either those commits would have to be applied
to the code base to link radler statically, or the libradler.so library
needs to be shipped along with wsclean. The first option I have tested
with the script provided below in a wsclean v3.4 git cloned directory,
and that works. I guess you're not checking out the git repositories in
the Debian build so I've also made a patch that can be applied with
"patch -s -p1 < link-radler-statically.patch" from the wsclean v3.4 dir.
It's attached to this mail. I hope this patch suffices for the Debian
build, otherwise let me know if I can do something else to help.
When we release a newer wsclean version, the patch is no longer
necessary. However, the release of wsclean v3.5 will probably take some
time, and does have quite some changes, so a 3.4 build would be nice.
Another thing: would it be possible to run 'wsclean --version' in the
build just to see if it succeeds? That should at least catch any linking
issues like here. There's also a much bigger wsclean test-suite, but
that might be a bit overkill for Debian, as it takes a considerable
amount of time and resources to run, and getting the tests correctly
through all debian platforms will be a bit challenging I think (not
unlike Casacore, whose tests are actually somewhat less demanding).
Thanks for your help, Ole!
Regards,
André
# Building WSClean 3.4 with Radler as static library
# Make sure submodules are present and at the right commit
# (not sure this is necessary in the Debian build)
mkdir build
cd build
cmake ..
cd ..
# Merge https://gitlab.com/aroffringa/wsclean/-/merge_requests/591
git cherry-pick 45c51219c0ea2deafb5de9edf2dddfda509f779b
# Merge https://git.astron.nl/RD/radler/-/merge_requests/123
cd external/radler
git cherry-pick 7fec4c029d62dcb664d894eae6909fa4ca92b642
cd ../../build
make -j`nproc`
diff --git a/CMakeLists.txt b/CMakeLists.txt
index f3f9b3d5..46b4501e 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -235,7 +235,7 @@ add_definitions(-DHAVE_GSL)
# Radler
set(RADLER_INSTALL_PREFIX ${CMAKE_BINARY_DIR}/external/radler)
set(RADLER_LIB
-${RADLER_INSTALL_PREFIX}/lib/libradler${CMAKE_SHARED_LIBRARY_SUFFIX})
+${RADLER_INSTALL_PREFIX}/lib/libradler${CMAKE_STATIC_LIBRARY_SUFFIX})
ExternalProject_Add(
radler-module
SOURCE_DIR ${CMAKE_SOURCE_DIR}/external/radler
@@ -409,16 +409,17 @@ set(ALL_LIBRARIES
include("${CMAKE_CURRENT_LIST_DIR}/external/aocommon/CMake/CheckBLAS.cmake")
check_blas(LIBRARIES ${ALL_LIBRARIES})
# Radler lib cannot be checked on BLAS consistenty as it doesn't exist
-# at cmake time.
-list(APPEND ALL_LIBRARIES ${RADLER_LIB})
+# at cmake time. It needs to be first in the link order because Radler
+# itself also depends on some of the libraries in the ALL_LIBRARIES list.
+list(PREPEND ALL_LIBRARIES ${RADLER_LIB})
add_library(wsclean-lib STATIC ${WSCLEANFILES})
-target_link_libraries(wsclean-lib PRIVATE pybind11::embed ${ALL_LIBRARIES})
+target_link_libraries(wsclean-lib PRIVATE ${ALL_LIBRARIES} pybind11::embed)
set_target_properties(wsclean-lib PROPERTIES OUTPUT_NAME wsclean)
set_target_properties(wsclean-lib PROPERTIES SOVERSION ${WSCLEAN_VERSION_SO})
add_library(wsclean-shared SHARED ${WSCLEANFILES})
-target_link_libraries(wsclean-shared PRIVATE pybind11::embed ${ALL_LIBRARIES})
+target_link_libraries(wsclean-shared PRIVATE ${ALL_LIBRARIES} pybind11::embed)
set_target_properties(wsclean-shared PROPERTIES SOVERSION ${WSCLEAN_VERSION_SO})
add_executable(wsclean main/main.cpp)
@@ -445,9 +446,6 @@ install(TARGETS wsclean DESTINATION bin)
install(TARGETS wsclean-lib DESTINATION lib)
install(TARGETS chgcentre DESTINATION bin)
install(FILES interface/wscleaninterface.h DESTINATION include)
-# Installing the radler library to ${CMAKE_INSTALL_FULL_LIBDIR}
-# ensures that users do not manually have to set the LD_LIBRARY_PATH
-install(FILES ${RADLER_LIB} DESTINATION ${CMAKE_INSTALL_FULL_LIBDIR})
if(MPI_FOUND)
install(TARGETS wsclean-mp DESTINATION bin)
diff --git a/tests/CMakeLists.txt b/tests/CMakeLists.txt
index 6d9e036e..9997ab6a 100644
--- a/tests/CMakeLists.txt
+++ b/tests/CMakeLists.txt
@@ -89,7 +89,7 @@ ExternalProject_Add(
BUILD_COMMAND ""
INSTALL_COMMAND "")
-set(TEST_LIBRARIES pybind11::embed ${ALL_LIBRARIES}
+set(TEST_LIBRARIES ${ALL_LIBRARIES} pybind11::embed
${Boost_UNIT_TEST_FRAMEWORK_LIBRARY})
target_link_libraries(unittest PRIVATE ${TEST_LIBRARIES})
diff --git a/external/radler/cpp/CMakeLists.txt
Bug#1071039: marked as done (iptux FTBFS on 32bit with 64bit time_t)
Your message dated Sat, 18 May 2024 13:35:29 +
with message-id
and subject line Bug#1071039: fixed in iptux 0.9.1-2
has caused the Debian Bug report #1071039,
regarding iptux FTBFS on 32bit with 64bit time_t
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.)
--
1071039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: iptux
Version: 0.9.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=iptux=0.9.1-1
...
FAILED: src/iptux-core/libiptux-core.so.0.9.1.p/internal_SendFileData.cpp.o
c++ -Isrc/iptux-core/libiptux-core.so.0.9.1.p -Isrc/iptux-core
-I../src/iptux-core -Isrc -I../src -Isrc/api -I../src/api
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include
-I/usr/include/sysprof-6 -I/usr/include/jsoncpp -I/usr/include/sigc++-2.0
-I/usr/lib/arm-linux-gnueabihf/sigc++-2.0/include -fdiagnostics-color=always
-D_GLIBCXX_ASSERTIONS=1 -Wall -Winvalid-pch -Wextra -Wpedantic -std=c++14
-Werror=format -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ
src/iptux-core/libiptux-core.so.0.9.1.p/internal_SendFileData.cpp.o -MF
src/iptux-core/libiptux-core.so.0.9.1.p/internal_SendFileData.cpp.o.d -o
src/iptux-core/libiptux-core.so.0.9.1.p/internal_SendFileData.cpp.o -c
../src/iptux-core/internal/SendFileData.cpp
../src/iptux-core/internal/SendFileData.cpp: In member function ‘void
iptux::SendFileData::SendDirFiles()’:
../src/iptux-core/internal/SendFileData.cpp:205:16: error: format ‘%lx’ expects
argument of type ‘long unsigned int’, but argument 8 has type ‘__time64_t’ {aka
‘long long int’} [-Werror=format=]
205 |":%s:%.9" PRIx64 ":%lx:%lx=%lx:%lx=%lx:", dirname,
|^~~~
../src/iptux-core/internal/SendFileData.cpp:205:16: error: format ‘%lx’ expects
argument of type ‘long unsigned int’, but argument 10 has type ‘__time64_t’
{aka ‘long long int’} [-Werror=format=]
205 |":%s:%.9" PRIx64 ":%lx:%lx=%lx:%lx=%lx:", dirname,
|^~~~
../src/iptux-core/internal/SendFileData.cpp:243:36: error: format ‘%lx’ expects
argument of type ‘long unsigned int’, but argument 6 has type ‘__time64_t’ {aka
‘long long int’} [-Werror=format=]
243 |":.:0:%lx:%lx=%lx:%lx=%lx:", IPMSG_FILE_RETPARENT,
| ~~^
||
|long unsigned int
| %llx
../src/iptux-core/internal/SendFileData.cpp:243:44: error: format ‘%lx’ expects
argument of type ‘long unsigned int’, but argument 8 has type ‘__time64_t’ {aka
‘long long int’} [-Werror=format=]
243 |":.:0:%lx:%lx=%lx:%lx=%lx:", IPMSG_FILE_RETPARENT,
| ~~^
||
|long unsigned int
| %llx
../src/iptux-core/internal/SendFileData.cpp:264:32: warning: cast between
incompatible function types from ‘int (*)(DIR*)’ to ‘GFunc’ {aka ‘void
(*)(void*, void*)’} [-Wcast-function-type]
264 | g_queue_foreach(, GFunc(closedir), NULL);
|^~~
cc1plus: some warnings being treated as errors
...
FAILED: src/iptux-core/libiptux-core.so.0.9.1.p/internal_TcpData.cpp.o
c++ -Isrc/iptux-core/libiptux-core.so.0.9.1.p -Isrc/iptux-core
-I../src/iptux-core -Isrc -I../src -Isrc/api -I../src/api
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include
-I/usr/include/sysprof-6 -I/usr/include/jsoncpp -I/usr/include/sigc++-2.0
-I/usr/lib/arm-linux-gnueabihf/sigc++-2.0/include -fdiagnostics-color=always
-D_GLIBCXX_ASSERTIONS=1 -Wall -Winvalid-pch -Wextra -Wpedantic -std=c++14
-Werror=format -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ
src/iptux-core/libiptux-core.so.0.9.1.p/internal_TcpData.cpp.o -MF
src/iptux-core/libiptux-core.so.0.9.1.p/internal_TcpData.cpp.o.d -o
Bug#1071076: marked as done (inotify-info: baseline ABI violation, builds with -march=native)
Your message dated Sat, 18 May 2024 13:04:44 + with message-id and subject line Bug#1071076: fixed in inotify-info 0.0.1-2 has caused the Debian Bug report #1071076, regarding inotify-info: baseline ABI violation, builds with -march=native 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.) -- 1071076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: inotify-info Version: 0.0.1-1 Severity: serious Dear maintainer, inotify-info builds with -march=native, which means the instruction set it uses depends on the buildd that is used. For instance the i386 package uses AVX instructions. In addition -march=native is not supported on all architectures. This is unfortunately not visible in the build log, you might want to make the build system as verbose as reasonably possible as recommended by the debian policy. Regards Aurelien --- End Message --- --- Begin Message --- Source: inotify-info Source-Version: 0.0.1-2 Done: Daniel Baumann We believe that the bug you reported is fixed in the latest version of inotify-info, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann (supplier of updated inotify-info 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, 18 May 2024 14:41:59 +0200 Source: inotify-info Architecture: source Version: 0.0.1-2 Distribution: sid Urgency: medium Maintainer: Daniel Baumann Changed-By: Daniel Baumann Closes: 1071076 Changes: inotify-info (0.0.1-2) sid; urgency=medium . * Uploading to sid. * Building without -march=native (Closes: #1071076). * Refreshing dwz.patch. * Renumbering patches. Checksums-Sha1: 1c07aed64601eff437f7d2c96fa857ae0692ad9a 1966 inotify-info_0.0.1-2.dsc b703b1f48d65a797280905bdcdeae4ca853b9fab 2812 inotify-info_0.0.1-2.debian.tar.xz 49ee9594bfbbf6048b90861a6fc2646b0ebba573 6192 inotify-info_0.0.1-2_amd64.buildinfo Checksums-Sha256: ef79a6d8b0e478bfceb947ae2ef6e2e6cf217681863b7b4108123470d83e7793 1966 inotify-info_0.0.1-2.dsc c55640784b4457549d44a332fea936d437731da8befd1e480e0304daed943acb 2812 inotify-info_0.0.1-2.debian.tar.xz 515bfbfcbdee39003117a86ae3957d117bf9dd8a968e4bd48c001718b28073dd 6192 inotify-info_0.0.1-2_amd64.buildinfo Files: 8ec753c8745c86d3232483144e3c5c3f 1966 utils optional inotify-info_0.0.1-2.dsc b1020a6a4cbd96a04387ba44e724a4d8 2812 utils optional inotify-info_0.0.1-2.debian.tar.xz a9388227fadff367051ba8bfa9a62bff 6192 utils optional inotify-info_0.0.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmZIoqMACgkQVc8b+Yar uccAlw//QB0fkTd7Vb4G3gSCDkAk7GrY5SX93gf31I3gXjhkEoAVsvhj/mSLu6rV kP7IVNoU2pACMvAeR9z+sVvLCk1dmUjG9Imn8dG/xKWa0VBJ3fJho7pZrWig/kS7 jHZXRNPNDC9Z75sXr2TKVO6Oozd0csMCNlAvLhSjx4BVNFlu5U/scj6bnzuWHj5j FH94yRxKFzNGkeoBgAY8pSauDvhW3nJyoVjhzqG2J/j+2JXumJoSlMR34p4zatFw yYfO77Py3SwyIljpmCsOR58lNkEf22C6KT/s5i341FqKP6SEIzA1WeVHWrBI6atz cUbVJ8W2pkdi3BdQvs5MqNTZZWn+Z5Cy9SaF9N+wHCno0J/DBaQcAjSlVibRde25 c2R/UuCtKDP8EBTkdyBt8uKaeOcXzWPspncf9Iira7aWuMoXK4dbUeXSGGWg0lWu /X53UARr0K380FV7NeF54Aglj0S6UMKPGDlU3Cw9wxGBQrvFLdtT1A1+MkhTxhFE v558UQGL8rfPb91xmFKvr/YhFC6LvfZ31bsAYGOXxTzg7Cqm8e2Q8UXKJ7D2bws1 xLP1vbcONbDA9lG1JSE0r/EfSXM36weuUUvonK4S77a1QU3j2qMIexAgMAfV1ud2 dAP5xpexor3bgzM2b9w70N+RgTWLR6ldoeQDvssznn53+g8TEgk= =++db -END PGP SIGNATURE- pgpCk06OyQ908.pgp Description: PGP signature --- End Message ---
Bug#1071362: marked as forwarded (rpy2: FTBFS: rpy2/tests/rinterface/test_embedded_r.py s.......Fatal Python error: Segmentation fault)
Your message dated Sat, 18 May 2024 07:59:17 -0500 with message-id <26184.42533.131357.172...@rob.eddelbuettel.com> has caused the report #1071362, regarding rpy2: FTBFS: rpy2/tests/rinterface/test_embedded_r.py s...Fatal Python error: Segmentation fault to be marked as having been forwarded to the upstream software author(s) Laurent Gautier (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.) -- 1071362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071362 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Hi Laurent, We a build issue in Debian found via bulk rebuilds. Which everything current in 'unstable', rpy2 (version 3.5.16) segfaults in a test when embedding. Details are at https://bugs.debian.org/1071362 If you kee 1071...@bugs.debian.org in the email headers replies will get appended there. Let me know if I can help in any way. Cheers, Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org--- End Message ---
Bug#1071382: marked as done (nodejs: FTBFS: flaky test)
Your message dated Sat, 18 May 2024 12:52:40 + with message-id and subject line Bug#1071382: fixed in nodejs 20.13.1+dfsg-2 has caused the Debian Bug report #1071382, regarding nodejs: FTBFS: flaky test 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.) -- 1071382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nodejs Version: 20.13.1+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org The test sequential/test-worker-heapsnapshot-options is flaky. The builds of 20.13.1+dfsg-1 failed on mips64el and s390. It also failed once on armhf, but a give back worked. https://buildd.debian.org/status/fetch.php?pkg=nodejs=mips64el=20.13.1%2Bdfsg-1=1715802567=0 not ok 3548 sequential/test-worker-heapsnapshot-options --- duration_ms: 2713.46500 severity: fail exitcode: 1 stack: |- (node:200641) internal/test/binding: These APIs are for internal testing only. Do not use them. (Use `node --trace-warnings ...` to show where the warning was created) /<>/test/common/heap.js:46 toNode.incomingEdges.push(edge); ^ TypeError: Cannot read properties of undefined (reading 'incomingEdges') at createJSHeapSnapshot (/<>/test/common/heap.js:46:12) at new State (/<>/test/common/heap.js:108:21) at recordState (/<>/test/common/heap.js:207:10) at /<>/test/sequential/test-worker-heapsnapshot-options.js:16:22 Node.js v20.13.1 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 20.13.1+dfsg-2 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of nodejs, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs 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, 18 May 2024 14:26:22 +0200 Source: nodejs Architecture: source Version: 20.13.1+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Closes: 1071382 Changes: nodejs (20.13.1+dfsg-2) unstable; urgency=medium . * Flaky sequential/test-worker-heapsnapshot-options. Closes: #1071382 Checksums-Sha1: 966f96eced14f03c9d6b04b89870a62d02ac025b 4142 nodejs_20.13.1+dfsg-2.dsc 8cdac10d3fc3341910e4a321b97ceba0b49f76c1 161272 nodejs_20.13.1+dfsg-2.debian.tar.xz e5a0df9760dd65802f69e3fb852dd441ee5db3ad 10804 nodejs_20.13.1+dfsg-2_source.buildinfo Checksums-Sha256: 116a0558b9cf8358fa2e495c43f07fedec8986a1071a9f46ba9b491bda5879ea 4142 nodejs_20.13.1+dfsg-2.dsc 9cd8895008b2356ef35046f2aabea18c3a5c784251ee63e4f671a3f36cd2 161272 nodejs_20.13.1+dfsg-2.debian.tar.xz 5c600edfcb889526708466fe22164981025fce4a0afadb5029b60bc7f8151aae 10804 nodejs_20.13.1+dfsg-2_source.buildinfo Files: 7f7b769442ed54d27cbfe1dba4fb43a5 4142 javascript optional nodejs_20.13.1+dfsg-2.dsc 3cdecc0473f5687a0d0ac410677aca5b 161272 javascript optional nodejs_20.13.1+dfsg-2.debian.tar.xz fa10375df7e6a7492471d3428587761f 10804 javascript optional nodejs_20.13.1+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAmZInpUSHGthcG91ZXJA bWVsaXgub3JnAAoJEGYRwF7dOfN06jQP/2+Hpn6UaFyMaebOlpIrDI6UhsWdIux6 19MkqfWMhGgJP1qc8g0xxZP6VAI3E8S6glPDe+0FJFJB4z128LWHMqL8C6XQrsh0 DuJkJqgQpoPQPCanxP7imrYYnJBh0pAl9QDNjdKupNp8qFro1x4r/2h9r0MmcuGJ a84pdSek3LYvu45kBdLY3zgtiHyoyJ1jZmMs7xqAlS4EkGN9BVq/LW80haJHgSUd uPd/wd1EdmZN7Nrv91+4wUJQxgMl3RstZ7XIfL65KyCWRsl/xjPOIFyz/1AvJBp8 eqNsGVynfVd87AyzEIcrphbt6HYfJ8/RQRl0yZ2srF3o4OIAmgYr7kTu9xGb0avr dYznE12cMhZ38xA9j7DgW/XFl0wOoivcOPihanv7ryRWR2mO0wCC657JX+cnbJ1i kyyUn2JYXSizlMiX2HNvqYr0bR2lpTHXOalhnibSqD9F2loNZpxbtlTq4CxUjfHR f6cWJrZBXQj+dG0hNX9DFgJL+1yVNX0xyitQNOsmSpDYo3eDyCaae6ARZ0Mi0G2B iUQBmwPIjql1rWL+Fx/DtKDmc2vg1m2A+Pr7jkSM3lrPgNzegvxRx85Dlhy1YHmQ zJFZXHrPZQ0mi0Tk5sdj8oTQUUmgkNScbWVt+ptR31v6NOnXyPQvTP1J7u+aC1kb WAy2BL+YoQX3 =kSAe
Bug#1071382: marked as pending in nodejs
Control: tag -1 pending Hello, Bug #1071382 in nodejs 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/js-team/nodejs/-/commit/cb01f624ef3a1ce3ed6b534348682b84d152ec91 Flaky sequential/test-worker-heapsnapshot-options. Closes: #1071382 (this message was generated automatically) -- Greetings https://bugs.debian.org/1071382
Processed: Bug#1071382 marked as pending in nodejs
Processing control commands: > tag -1 pending Bug #1071382 [src:nodejs] nodejs: FTBFS: flaky test Added tag(s) pending. -- 1071382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071324: marked as done (libhtp: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file)
Your message dated Sat, 18 May 2024 12:20:25 +
with message-id
and subject line Bug#1071324: fixed in libhtp 1:0.5.48-2
has caused the Debian Bug report #1071324,
regarding libhtp: FTBFS: dpkg-gensymbols: error: some symbols or patterns
disappeared in the symbols file
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.)
--
1071324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libhtp
Version: 1:0.5.48-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --with autoreconf
dh_update_autotools_config
dh_autoreconf
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f -exec md5sum {} + -o
-type l -printf "symlink %p
" > debian/autoreconf.before
grep -q ^XDT_ configure.ac
autoreconf -f -i
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'
configure.ac:156: warning: The macro `AC_TRY_LINK' is obsolete.
configure.ac:156: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from...
m4/iconv.m4:20: AM_ICONV_LINK is expanded from...
m4/iconv.m4:188: AM_ICONV is expanded from...
configure.ac:156: the top level
configure.ac:156: warning: The macro `AC_TRY_RUN' is obsolete.
configure.ac:156: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from...
m4/iconv.m4:20: AM_ICONV_LINK is expanded from...
m4/iconv.m4:188: AM_ICONV is expanded from...
configure.ac:156: the top level
configure.ac:156: warning: The macro `AC_TRY_COMPILE' is obsolete.
configure.ac:156: You should run autoupdate.
./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
m4/iconv.m4:188: AM_ICONV is expanded from...
configure.ac:156: the top level
configure.ac:86: installing './compile'
configure.ac:89: installing './config.guess'
configure.ac:89: installing './config.sub'
configure.ac:7: installing './install-sh'
configure.ac:7: installing './missing'
Makefile.am: installing './INSTALL'
htp/Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o
-path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f -exec md5sum {} + -o
-type l -printf "symlink %p
" > debian/autoreconf.after
dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc
Bug#1071366: marked as done (starlink-pal: FTBFS: palDfltin.c:185:3: error: implicit declaration of function ‘strlcpy’; did you mean ‘strncpy’?)
Your message dated Sat, 18 May 2024 12:20:46 +
with message-id
and subject line Bug#1071366: fixed in starlink-pal 0.9.10-2
has caused the Debian Bug report #1071366,
regarding starlink-pal: FTBFS: palDfltin.c:185:3: error: implicit declaration
of function ‘strlcpy’; did you mean ‘strncpy’?
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.)
--
1071366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:starlink-pal
Version: 0.9.10-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build
dh_update_autotools_config
debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
cp pal.news NEWS
dh_autoreconf
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:25: installing 'build-aux/compile'
configure.ac:26: installing 'build-aux/config.guess'
configure.ac:26: installing 'build-aux/config.sub'
configure.ac:11: installing 'build-aux/install-sh'
configure.ac:11: installing 'build-aux/missing'
Makefile.am: installing 'build-aux/depcomp'
parallel-tests: installing 'build-aux/test-driver'
make[1]: Leaving directory '/<>'
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- --without-cnf --with-pthreads
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --without-cnf
--with-pthreads
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... none
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu
format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format...
func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for file... file
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking for stdio.h... yes
Bug#1071362: rpy2: FTBFS: rpy2/tests/rinterface/test_embedded_r.py s.......Fatal Python error: Segmentation fault
On 17 May 2024 at 23:05, Santiago Vila wrote: | Dirk Eddelbuettel wrote: | > Is there a chance this could be spurious? | | Unlikely because it also happens here: | | https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rpy2.html Ok, I will get in touch with Laurent. Dirk | Thanks. -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Processed: Re: wsclean: error while loading shared libraries: libradler.so: cannot open shared object file
Processing control commands: > severity -1 serious Bug #1070237 [wsclean] wsclean: error while loading shared libraries: libradler.so: cannot open shared object file Severity set to 'serious' from 'grave' -- 1070237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070237: wsclean: error while loading shared libraries: libradler.so: cannot open shared object file
Control: severity -1 serious Hi Andre, sorry that I only now found time to look into your Debian bug. Indeed, from the build log [1] the libradler is build as shared lib, but not installed into the package, while it was supposed to be built as a static lib. However, I couldn't figure out why this is the case; the only flags I give to cmake are -DDEB_HOST_MULTIARCH=$(DEB_HOST_MULTIARCH) -DPORTABLE=yes which do not affect the build of the radler lib. From the log, the full command line for cmake (including what the Debian build system adds) is cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DDEB_HOST_MULTIARCH=x86_64-linux-gnu -DPORTABLE=yes .. For radler itself, it is cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DDEB_HOST_MULTIARCH=x86_64-linux-gnu -DPORTABLE=yes .. As you are upstream, do you have an idea? Is there a way to enforce building a static library over a dynamic one? For the other external libs, it seems to work. Best Ole p.s. setting the severity to "serious" as this is conform to Debian rules. "grave" is only used if the package breaks other, unrelated packages. Both are RC. [1] https://buildd.debian.org/status/fetch.php?pkg=wsclean=amd64=3.4-1%2Bb3=1710526039=0
Processed: closing 1062567
Processing commands for cont...@bugs.debian.org: > # no transition for libpg-query required > close 1062567 Bug #1062567 [src:libpg-query] libpg-query: NMU diff for 64-bit time_t transition Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1062567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071382: nodejs: FTBFS: flaky test
Source: nodejs Version: 20.13.1+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org The test sequential/test-worker-heapsnapshot-options is flaky. The builds of 20.13.1+dfsg-1 failed on mips64el and s390. It also failed once on armhf, but a give back worked. https://buildd.debian.org/status/fetch.php?pkg=nodejs=mips64el=20.13.1%2Bdfsg-1=1715802567=0 not ok 3548 sequential/test-worker-heapsnapshot-options --- duration_ms: 2713.46500 severity: fail exitcode: 1 stack: |- (node:200641) internal/test/binding: These APIs are for internal testing only. Do not use them. (Use `node --trace-warnings ...` to show where the warning was created) /<>/test/common/heap.js:46 toNode.incomingEdges.push(edge); ^ TypeError: Cannot read properties of undefined (reading 'incomingEdges') at createJSHeapSnapshot (/<>/test/common/heap.js:46:12) at new State (/<>/test/common/heap.js:108:21) at recordState (/<>/test/common/heap.js:207:10) at /<>/test/sequential/test-worker-heapsnapshot-options.js:16:22 Node.js v20.13.1 Cheers -- Sebastian Ramacher
Bug#1071330: marked as done (msgraph: FTBFS: (/<>/obj-x86_64-linux-gnu/tests/user:641808): GLib-Net-WARNING **: 17:38:49.590: Failed to load TLS database: System trust contains zero trust
Your message dated Sat, 18 May 2024 10:39:09 +0200 with message-id and subject line Re: Bug#1071330: msgraph: FTBFS: (/<>/obj-x86_64-linux-gnu/tests/user:641808): GLib-Net-WARNING **: 17:38:49.590: Failed to load TLS database: System trust contains zero trusted certificates; please investigate your GnuTLS configuration has caused the Debian Bug report #1071330, regarding msgraph: FTBFS: (/<>/obj-x86_64-linux-gnu/tests/user:641808): GLib-Net-WARNING **: 17:38:49.590: Failed to load TLS database: System trust contains zero trusted certificates; please investigate your GnuTLS configuration 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.) -- 1071330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:msgraph Version: 0.2.1-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf dh_auto_configure cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1 The Meson build system Version: 1.4.0 Source dir: /<> Build dir: /<>/obj-x86_64-linux-gnu Build type: native build Project name: msgraph Project version: 0.2.1 C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-25) 13.2.0") C linker for the host machine: cc ld.bfd 2.42 Host machine cpu family: x86_64 Host machine cpu: x86_64 Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1 Run-time dependency glib-2.0 found: YES 2.80.2 Run-time dependency gio-2.0 found: YES 2.80.2 Run-time dependency json-glib-1.0 found: YES 1.8.0 Run-time dependency rest-1.0 found: YES 0.9.1 Run-time dependency libsoup-3.0 found: YES 3.4.4 Run-time dependency goa-1.0 found: YES 3.50.1 Run-time dependency libuhttpmock-1.0 found: YES 0.10.0 Configuring config.h using configuration Configuring msg-version.h using configuration Compiler for C supports link arguments -Wl,--version-script,/<>/src/libmsgraph.map: NO Run-time dependency gobject-introspection-1.0 found: YES 1.80.1 Dependency gobject-introspection-1.0 found: YES 1.80.1 (cached) Program /usr/bin/x86_64-linux-gnu-g-ir-scanner found: YES (/usr/bin/x86_64-linux-gnu-g-ir-scanner) Dependency gobject-introspection-1.0 found: YES 1.80.1 (cached) Program /usr/bin/x86_64-linux-gnu-g-ir-compiler found: YES (/usr/bin/x86_64-linux-gnu-g-ir-compiler) Configuring msg.toml using configuration Program gi-docgen found: YES (/usr/bin/gi-docgen) Build targets in project: 9 msgraph 0.2.1 User defined options buildtype : plain libdir: lib/x86_64-linux-gnu localstatedir : /var prefix: /usr sysconfdir: /etc wrap_mode : nodownload python.bytecompile: -1 Found ninja-1.12.1 at /usr/bin/ninja dh_auto_build cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j2 -v [1/43] cc -Isrc/libmsgraph-0.so.0.2.1.p -Isrc -I../src -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/json-glib-1.0 -I/usr/include/rest-1.0 -I/usr/include/libsoup-3.0 -I/usr/include/libxml2 -I/usr/include/goa-1.0 -I/usr/lib/x86_64-linux-gnu/goa-1.0/include -I/<>/obj-x86_64-linux-gnu -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=gnu11 -DMSG_COMPILATION -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ src/libmsgraph-0.so.0.2.1.p/contact_msg-contact.c.o -MF src/libmsgraph-0.so.0.2.1.p/contact_msg-contact.c.o.d -o src/libmsgraph-0.so.0.2.1.p/contact_msg-contact.c.o -c ../src/contact/msg-contact.c [2/43] cc -Isrc/libmsgraph-0.so.0.2.1.p -Isrc -I../src -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/json-glib-1.0 -I/usr/include/rest-1.0 -I/usr/include/libsoup-3.0 -I/usr/include/libxml2 -I/usr/include/goa-1.0 -I/usr/lib/x86_64-linux-gnu/goa-1.0/include -I/<>/obj-x86_64-linux-gnu -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall
Processed: bug 1071293 is not forwarded
Processing commands for cont...@bugs.debian.org: > notforwarded 1071293 Bug #1071293 [ddcci-dkms] ddcci-dkms: Fails to build on linux-image-6.8.9-amd64 Unset Bug forwarded-to-address > thanks Stopping processing here. Please contact me if you need assistance. -- 1071293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1071335: upstream commits
Processing control commands: > tags 1071335 pending Bug #1071335 [src:pptpd] pptpd: FTBFS: our_syslog.h:38:62: error: implicit declaration of function ‘strerror’ Added tag(s) pending. -- 1071335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071335 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071335: upstream commits
Control: tags 1071335 pending
James Cameron wrote...
> You may be interested in these upstream commits;
>
> b01478d ("Fix some parts of macro expansion are not guarded")
> 0194b80 ("strerror and memset require string.h")
Thanks a lot for having an eye on the Debian packaging. As you'd expect,
version 1.5 builds fine again, will do some more checks and upload
during the weekend.
Christoph
signature.asc
Description: PGP signature
Bug#1068186: mozc: FTBFS with abseil 20230802: ../../base/init_mozc.cc:90:29: error: ‘absl::debian5::flags_internal::ArgvListAction’ has not been declared
Hi,
On Fri, 17 May 2024 21:16:15 +0900 Kentaro HAYASHI
wrote:
> Control: tags -1 patch
>
> On Fri, 17 May 2024 14:06:37 +0900 Kentaro HAYASHI
>
> > This issue was already fixed in upstream.
> >
> > Non-public Abseil API is used for CLI parsing
> > https://github.com/google/mozc/issues/790
> >
> > Above ftbfs error was fixed with the following commit:
> >
> >
> > https://github.com/google/mozc/commit/cad4064c8884eb711e0e19b4b79d2ff5610823dc
>
> Attached patch will solve the reported compile error in this
> bugreport, but even though it was fixed, another abseil linkage error
> occurs.
>
> /usr/bin/ld: obj/base/base_core.file_util.o: undefined reference to
> symbol '_ZN4absl7debian5lsERSoNS0_11string_viewE'
> /usr/bin/ld:
> /lib/x86_64-linux-gnu/libabsl_string_view.so.20230802: error adding
> symbols: DSO missing from command line
>
> I'm not sure how to link it correctly in appropriate way.
I've attached additional patch
(0011-Fix-missing-abseil-gyp-link-settings.patch )
to fix rest of FTBFS issues.
To build correctly, the following patch files are required.
* 0010-Fix-the-compile-error-of-ParseCommandLineFlags-with.patch [1]
* 0011-Fix-missing-abseil-gyp-link-settings.patch
Regards,
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068186#21
From: Kentaro Hayashi
Date: Sat, 18 May 2024 17:05:16 +0900
Subject: Fix missing abseil libraries
It fixes the following error:
/usr/bin/ld: obj/base/base_core.file_util.o: undefined reference to
symbol '_ZN4absl7debian5lsERSoNS0_11string_viewE'
/usr/bin/ld:
/lib/x86_64-linux-gnu/libabsl_string_view.so.20230802: error adding
symbols: DSO missing from command line
/usr/bin/ld: obj/unix/emacs/mozc_emacs_helper_lib.client_pool.o:
undefined reference to symbol
'_ZN4absl7debian516raw_log_internal21internal_log_functionB5cxx11E'
/usr/bin/ld:
/lib/x86_64-linux-gnu/libabsl_raw_logging_internal.so.20230802: error
adding symbols: DSO missing from command line collect2: error: ld
returned 1 exit status
Signed-off-by: Kentaro Hayashi
---
src/base/absl.gyp | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/base/absl.gyp b/src/base/absl.gyp
index 4bacb59..6105498 100644
--- a/src/base/absl.gyp
+++ b/src/base/absl.gyp
@@ -47,7 +47,7 @@
['use_libabseil==1', {
'link_settings': {
'libraries': [
- '-latomic -labsl_base -labsl_int128 -labsl_base -labsl_hash -labsl_city -labsl_flags_reflection -labsl_raw_hash_set -labsl_str_format_internal -labsl_throw_delegate -labsl_time_zone -labsl_hashtablez_sampler -labsl_synchronization -labsl_time -labsl_strings_internal -labsl_strings -labsl_spinlock_wait -labsl_status -labsl_statusor -labsl_flags_internal -labsl_flags_usage_internal -labsl_flags_marshalling -labsl_flags_parse',
+ '-latomic -labsl_base -labsl_int128 -labsl_base -labsl_hash -labsl_city -labsl_flags_reflection -labsl_raw_hash_set -labsl_str_format_internal -labsl_throw_delegate -labsl_time_zone -labsl_hashtablez_sampler -labsl_synchronization -labsl_time -labsl_strings_internal -labsl_strings -labsl_spinlock_wait -labsl_status -labsl_statusor -labsl_flags_internal -labsl_flags_usage_internal -labsl_flags_marshalling -labsl_flags_parse -labsl_string_view -labsl_raw_logging_internal',
],
},
},],
Processed: tags
Processing commands for cont...@bugs.debian.org: > tags 1069909 + ftbfs Bug #1069909 [dcraw] dcraw: FTBFS due to conflicting memmem prototype Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1071358: r-cran-rgeos: FTBFS: geos.c:102:13: error: format not a string literal and no format arguments
Processing control commands: > block -1 by 1071375 Bug #1071358 [src:r-cran-rgeos] r-cran-rgeos: FTBFS: geos.c:102:13: error: format not a string literal and no format arguments 1071358 was not blocked by any bugs. 1071358 was not blocking any bugs. Added blocking bug(s) of 1071358: 1071375 -- 1071358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1071358: r-cran-rgeos: FTBFS: geos.c:102:13: error: format not a string literal and no format arguments
Processing control commands: > block -1 by 1071375 Bug #1071358 [src:r-cran-rgeos] r-cran-rgeos: FTBFS: geos.c:102:13: error: format not a string literal and no format arguments 1071358 was blocked by: 1071375 1071358 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #1071358 to the same blocks previously set -- 1071358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071358: r-cran-rgeos: FTBFS: geos.c:102:13: error: format not a string literal and no format arguments
Control: block -1 by 1071375 thanks Hi Santiago, Am Fri, May 17, 2024 at 10:41:36PM +0200 schrieb Santiago Vila: > Package: src:r-cran-rgeos > Version: 0.6-4-2 > Severity: serious > Tags: ftbfs thanks a lot for your QA effort. It turns out that the package is not maintained at CRAN any more. To reduce the maintenance effort of the R pkg team this package will be removed from Debian (see bug #1071375). Kind regards Andreas. -- https://fam-tille.de
Processed: fixed 1060580 in xrdp/0.9.24-5
Processing commands for cont...@bugs.debian.org:
> fixed 1060580 xrdp/0.9.24-5
Bug #1060580 {Done: Gürkan Myczko } [src:xrdp] xrdp:
Please switch Build-Depends to systemd-dev
Marked as fixed in versions xrdp/0.9.24-5.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1060580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1060480: marked as done (e17: Please switch Build-Depends to systemd-dev)
Your message dated Sat, 18 May 2024 06:20:37 + with message-id and subject line Bug#1060480: fixed in e17 0.26.0-4 has caused the Debian Bug report #1060480, regarding e17: Please switch Build-Depends to systemd-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.) -- 1060480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: e17 Version: 0.26.0-2 Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: systemd-dev Hi, your package e17 declares a Build-Depends on systemd and/or udev. In most cases, this build dependency is added to get the paths that are defined in udev.pc or systemd.pc (via pkgconfig). Since systemd_253-2 [1], these two pkgconfig files have been split into a separate package named systemd-dev. This package is arch:all, so even available on non-Linux architectures, which will simplify the installation of upstream provided service files / udev rules. To not make existing source packages FTBFS, the systemd and udev package have a Depends: systemd-dev. This dependency will be removed at some point though before trixie is released. Once this happens, this issue will be bumped to RC. Please update your build dependencies accordingly at your earliest convenience. If all you need is the systemd.pc or udev.pc pkgconfig file, please replace any systemd or udev Build-Depends with systemd-dev. In most cases that should be sufficient. If your package needs further resources from systemd or udev to build successfully, it's fine to keep those Build-Depends in addition to systemd-dev. To ease stable backports, a version of systemd with those changes is provided via bookworm-backports. In case you have further questions, please contact the systemd team at . On behalf of the systemd team, Michael [1] https://salsa.debian.org/systemd-team/systemd/-/merge_requests/196 --- End Message --- --- Begin Message --- Source: e17 Source-Version: 0.26.0-4 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of e17, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler (supplier of updated e17 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, 18 May 2024 06:57:07 +0200 Source: e17 Architecture: source Version: 0.26.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Pkg-e Team Changed-By: Andreas Metzler Closes: 1060480 Changes: e17 (0.26.0-4) unstable; urgency=medium . * Build-depend on systemd-dev instead of systemd. (systemd is still pulled in via bluez -> udev -> systemd). Closes: #1060480 . e17 (0.26.0-3) unstable; urgency=medium . * Install wayland .desktop file with a different name. When the xsession and wayland-session desktop file had the same name, gdm would only show & start the wayland session. Renaming the wayland session seems to fix this. https://gitlab.gnome.org/GNOME/gdm/-/issues/898 Checksums-Sha1: b5aa83c6275fa9b50d6d359733ad839804cbd2ac 2412 e17_0.26.0-4.dsc e4798aa4ffe5057b653d9f2bca7584c0358e1b08 18256 e17_0.26.0-4.debian.tar.xz Checksums-Sha256: 687783d8a4b72966dada93de8199636fdd3b2c74312c9092aa8fcb8446d8214d 2412 e17_0.26.0-4.dsc d8b42c9fd38fcdc13b8d47fbc9527188412d1426b6847edeadf57075821b401a 18256 e17_0.26.0-4.debian.tar.xz Files: 4e2521665a1da40aa2746bef67ba799e 2412 x11 optional e17_0.26.0-4.dsc 11d2d1095fae8bda726aafde6032ddff 18256 x11 optional e17_0.26.0-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmZIPa4ACgkQpU8BhUOC FITTzA/+JuN1C5A9qx1WV25PPYSPpKhUMfTksgYEqW6MQwt5PY7+4tn7xxiF8Xsg U8wYL5/C2QaBVYd7y47BddixlCNnZ2Swh+OLiy4SzCQorTFGy0KeFD7vlAEgDM2R 3cRRyxeepjBn33TlBAYdvRPTSK+RFZk38CMjHleI7LL/By5vKohA4Lnlm95HIp0o Rej+G2FvdD7Seh0wj9OgzVs+fx92UoAkcjGYrjR3eCajkHO8LFsmm2vlizOwmEdN mpHL+s7/gBP5n2/JizfLUH0KHryTux6P86YIj70K4incro/2Qk66KfGvRcjWApfO kpmTZ98A86BbsKiFbrrKVGcudGvp1uMV5IULDzLMIWRPq+pXAI8tdgginJp/Escs
