Bug#1042484: util-linux-locales: /usr/share/man/fr/man1/lastb.1.gz is also in package manpages-fr 4.19.0-5
Package: util-linux-locales Version: 2.39.1-3 Severity: serious Justification: 6 X-Debbugs-Cc: jean-m...@6jf.be Dear Maintainer, Upgrading util-linux-locales from 2.38.1-6 to 2.39.1-3 failed and returned this error message: Preparing to unpack .../util-linux-locales_2.39.1-3_all.deb ... Unpacking util-linux-locales (2.39.1-3) over (2.38.1-6) ... dpkg: error processing archive /var/cache/apt/archives/util-linux-locales_2.39.1-3_all.deb (--unpack): trying to overwrite '/usr/share/man/fr/man1/lastb.1.gz', which is also in package manpages-fr 4.19.0-5 Errors were encountered while processing: /var/cache/apt/archives/util-linux-locales_2.39.1-3_all.deb Please, fix this problem. Thank you so much. Regards, Jean-Marc -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages util-linux-locales depends on: ii util-linux 2.39.1-3 util-linux-locales recommends no packages. util-linux-locales suggests no packages. -- no debconf information
Processed (with 1 error): New "fileconflict" usertag for debian...@lists.debian.org
Processing commands for cont...@bugs.debian.org:
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was hel...@subdivi.de).
> # discodos
> usertags 966115 + fileconflict
Usertags were: edos-file-overwrite.
Usertags are now: fileconflict edos-file-overwrite.
> affects 966115 + mono-devel
Bug #966115 [discodos] discodos: /usr/bin/disco is already shipped by mono-devel
Added indication that 966115 affects mono-devel
> # firebird-utils
> usertags 1040321 + fileconflict
There were no usertags set.
Usertags are now: fileconflict.
> affects 1040321 + firebird3.0-server
Bug #1040321 [firebird-utils] firebird-utils: undeclared file conflict with
firebird3.0-server
Added indication that 1040321 affects firebird3.0-server
> # kodi-addons-dev
> usertags 1040319 + fileconflict
There were no usertags set.
Usertags are now: fileconflict.
> affects 1040319 + kodi-addons-dev-common
Bug #1040319 [kodi-addons-dev] kodi-addons-dev: undeclared file conflict with
kodi-addons-dev-common
Added indication that 1040319 affects kodi-addons-dev-common
> # libocct-data-exchange-dev
> usertags 1035009 + fileconflict
There were no usertags set.
Usertags are now: fileconflict.
> affects 1035009 + liboce-modeling-dev liboce-visualization-dev
Failed to mark 1035009 as affecting package(s): Not altering archived bugs; see
unarchive.
> # libreoffice-uiconfig-report-builder
> usertags 1041899 + fileconflict
There were no usertags set.
Usertags are now: fileconflict.
> affects 1041899 + libreoffice-report-builder
Bug #1041899 {Done: Rene Engelhard }
[libreoffice-uiconfig-report-builder] libreoffice-uiconfig-report-builder:
undeclared file conflicts with libreoffice-report-builder/unstable
Added indication that 1041899 affects libreoffice-report-builder
> # libsequoia-octopus-librnp
> usertags 1041832 + fileconflict
There were no usertags set.
Usertags are now: fileconflict.
> affects 1041832 + thunderbird
Bug #1041832 [libsequoia-octopus-librnp] libsequoia-octopus-librnp: undeclared
file conflict with thunerbird
Added indication that 1041832 affects thunderbird
> # nex
> usertags 1022957 + fileconflict
Usertags were: edos-file-overwrite.
Usertags are now: fileconflict edos-file-overwrite.
> affects 1022957 + nvi
Bug #1022957 [nex] nex: /usr/bin/nex is already provided by the nvi package
Added indication that 1022957 affects nvi
> # nfs-ganesha-ceph
> usertags 1040362 + fileconflict
There were no usertags set.
Usertags are now: fileconflict.
> affects 1040362 + nfs-ganesha
Bug #1040362 [nfs-ganesha-ceph] nfs-ganesha-ceph: undeclared file conflict with
nfs-ganesha from bullseye
Added indication that 1040362 affects nfs-ganesha
> # python3-notebook
> usertags 1036996 + fileconflict
There were no usertags set.
Usertags are now: fileconflict.
> affects 1036996 + cadabra2
Bug #1036996 [jupyter-notebook] cadabra2,python3-notebook: undeclared file
conflict on /usr/lib/python3/dist-packages/notebook/static/components/codemirror
Added indication that 1036996 affects cadabra2
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1022957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022957
1036996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036996
1040319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040319
1040321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040321
1040362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040362
1041832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041832
1041899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041899
966115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bug 1033907 is forwarded to https://github.com/numba/numba/issues/9109
Processing commands for cont...@bugs.debian.org: > forwarded 1033907 https://github.com/numba/numba/issues/9109 Bug #1033907 [src:numba] numba: autopkgtest regression: segmentation fault on arm64 Set Bug forwarded-to-address to 'https://github.com/numba/numba/issues/9109'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1033907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033907: numba: autopkgtest regression: segmentation fault on arm64
Debian's llvmlite package was updated recently So I updated numba to 0.57.1 and released it to unstable, but even with the updates it still crashes on arm64. I forwarded it to upstream. Diane On Mon, 3 Jul 2023 13:36:53 +0200 Andreas Tille wrote: > Hi > > On Sun, 21 May 2023 11:39:29 -0700 Diane Trout wrote: > > Unfortunately it also wants llvmlite 0.40.0. > > Could you please be more verbose about this "unfortunately"? > > > It'd probably be easier to get upstream to help with debugging 0.57 > > I fully agree that we should target at latest upstream instead of > trying to stick to our heavily patched old version. > > Kind regards > Andreas. > > -- > http://fam-tille.de > >
Bug#1037993: marked as done (dahdi-dkms: module fails to build for Linux 6.3)
Your message dated Sat, 29 Jul 2023 01:18:52 + with message-id and subject line Bug#1037993: fixed in dahdi-linux 1:3.1.0+git20230717~dfsg-1 has caused the Debian Bug report #1037993, regarding dahdi-dkms: module fails to build for Linux 6.3 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.) -- 1037993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037993 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dahdi-dkms Version: 1:2.11.1.0.20170917~dfsg-8.4 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: piuparts DKMS make.log for dahdi-2.11.1.0.20170917 for kernel 6.3.0-1-amd64 (x86_64) Thu Jun 15 09:40:51 UTC 2023 make -C /lib/modules/6.3.0-1-amd64/build KBUILD_EXTMOD=/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi DAHDI_INCLUDE=/var/lib/dkms/dahdi/2.11.1.0.20170917/build/include DAHDI_MODULES_EXTRA="dahdi_dummy.o dahdi_echocan_oslec.o " HOTPLUG_FIRMWARE=yes modules DAHDI_BUILD_ALL=m make[1]: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64' CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_adpcm_chan.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_channel.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_open.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_stats.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_conf_bridge.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_debug.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_events.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_interrupts.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_memory.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_miscellaneous.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_mixer.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_phasing_tsst.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_playout_buf.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_remote_debug.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tlv.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tone_detection.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tsi_cnct.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tsst.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/apilib/bt/octapi_bt0.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/apilib/largmath/octapi_largmath.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/apilib/llman/octapi_llman.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/oct612x-user.o LD [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/oct612x.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/wct4xxp/base.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/wct4xxp/vpm450m.o LD [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/wct4xxp/wct4xxp.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/wctc4xxp/base.o In file included from /usr/src/linux-headers-6.3.0-1-common/include/linux/string.h:254, from /usr/src/linux-headers-6.3.0-1-common/include/linux/bitmap.h:11, from /usr/src/linux-headers-6.3.0-1-common/include/linux/cpumask.h:12, from
Bug#1040318: marked as done (mumax3: hardcoded dependency on libcudart11.0)
Your message dated Sat, 29 Jul 2023 00:05:04 + with message-id and subject line Bug#1040318: fixed in mumax3 3.10-8 has caused the Debian Bug report #1040318, regarding mumax3: hardcoded dependency on libcudart11.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1040318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mumax3 Version: 3.10-7 Severity: serious Tags: sid trixie Control: block 1036676 with -1 Hi, while rebuilding your package for the CUDA 12 transition, I noticed that the package retained a dependency on libcudart11.0 despite of that package not being available during the rebuild. Why is that dependency is hardcoded in d/control? Andreas --- End Message --- --- Begin Message --- Source: mumax3 Source-Version: 3.10-8 Done: Roland Mas We believe that the bug you reported is fixed in the latest version of mumax3, 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 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roland Mas (supplier of updated mumax3 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, 29 Jul 2023 01:11:00 +0200 Source: mumax3 Binary: mumax3 mumax3-dbgsym Architecture: source amd64 Version: 3.10-8 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Roland Mas Description: mumax3 - GPU-accelerated micromagnetic simulator Closes: 1040318 Changes: mumax3 (3.10-8) unstable; urgency=medium . * Bug fix: "hardcoded dependency on libcudart11.0", thanks to Andreas Beckmann (Closes: #1040318). Checksums-Sha1: 9b81c99380f5ab10c900138603a963822b5ba89a 2011 mumax3_3.10-8.dsc 84bc751b544ec47592d680b14097e85ada147368 12748 mumax3_3.10-8.debian.tar.xz d9c2a4876e4b9be597d49e4ac1fa1bce910f2402 16180552 mumax3-dbgsym_3.10-8_amd64.deb 431076e59e7ec932142a7690218fb6aa9289b2dc 8688 mumax3_3.10-8_amd64.buildinfo cf649c663aac697d4af4ab3e085c005cea299ee4 12645368 mumax3_3.10-8_amd64.deb Checksums-Sha256: 89cab241ec9cdbda045b0de41999d940bcfde00cc5873861787820502ef1d830 2011 mumax3_3.10-8.dsc c2f4857d1b51e39224628fdd53aa270280481ab7ede6f25d228861fca45a16dc 12748 mumax3_3.10-8.debian.tar.xz 0bb761f7cfc81b068aab4f2f16de388049d4692af1afac56025aefb0efed07d4 16180552 mumax3-dbgsym_3.10-8_amd64.deb 1846d67cf0a6a5093e63070f3e849343a7ed1f68600cd977b7d07c2a77535a27 8688 mumax3_3.10-8_amd64.buildinfo 8dee876482dc8dff2a96e7f25057796a589e7cfc857758741f121cef93e9f2c7 12645368 mumax3_3.10-8_amd64.deb Files: bfbdf77eb83ac6f903e6c186d9dd0c9b 2011 contrib/science optional mumax3_3.10-8.dsc 1efa867ae8371a8d46164fdad608e0bc 12748 contrib/science optional mumax3_3.10-8.debian.tar.xz 45e1935b4694c9f5cba0b174cc67a20f 16180552 contrib/debug optional mumax3-dbgsym_3.10-8_amd64.deb c08a23d3835e63b490fbc463f2e4644d 8688 contrib/science optional mumax3_3.10-8_amd64.buildinfo 297ba2be579d64dce084ad4f2e19b28c 12645368 contrib/science optional mumax3_3.10-8_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEtBU2D1kett1zr/uD0w3s0lmTIvwFAmTEUXgACgkQ0w3s0lmT IvylRg/+JPX24d1gwNyn3Medr+cidcTN2NgXWjh6JwfxD1PUovuDrpMtZdqlF5vX 7YRXZnr6iGlnUpb7mduiyqD8r107K7KzyRxhbV13wuLppBUNV0ulCn+1qKEi+AnZ MnRjTvP1SAFA9K2NjttZNm/dfWtfxVXdKblfvnUO/NvmBPSGF2MGt74Nf+VhsBrS oDCmTGepIxycFFo5iaVSPHiy1qRMIHC5xV8r+17nKaCMG85cehPRJQupIrGFSGTr K4n3KgNYG6ygV9P2z1RG1AQPxnC+F/16H9Jc8Dr0MGIvcDlC8iUi1g7VDwmBQOo7 Qpz/xRidaN3zzS5kdrvOY8AtcLjCJVssJqbZCFEBV13qDRmnDUjnOTlHeqYUJ3hG zh30i+ZqU7oyyYyR3iBieIiz4brhvOx9m8nljAByqld5Zu39RDpo1vSEIW32dgbh Ka5ZMVWTkgesDcPYWd7tIIpMVfJAM2aEgB+GB/3mKWw+g2SHckJYPEm4FQG8tzZW eMZVW/yr5ygxctNht6qQmfFB1n1d1LnOBst8wBcLYnS1h60RjAWlty0cnV8Ogito SZt2duhQ7EvXQbzVvkah/mTBuZY6sROnxV7taDSeg4lz5EcZMPzxMw4AnTZyOGM1 vaN25l1W+s/DNNOITo9SiBjThwyltCPUDlFKryaPMMIw/7YqOMo= =bDGa -END PGP SIGNATURE End Message ---
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 1042321 pending Bug #1042321 [src:qt6-sensors] qt6-sensors: FTBFS: dh_missing: error: missing files, aborting Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 1042321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tag as pending
Processing commands for cont...@bugs.debian.org: > tag 1042329 pending Bug #1042329 [src:qt6-3d] qt6-3d: FTBFS: dh_missing: error: missing files, aborting Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042329 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 1042275 pending Bug #1042275 [src:qt6-speech] qt6-speech: FTBFS: dh_missing: error: missing files, aborting Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 1042275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tag as pending
Processing commands for cont...@bugs.debian.org: > tag 1042283 pending Bug #1042283 [src:qt6-remoteobjects] qt6-remoteobjects: FTBFS: dh_missing: error: missing files, aborting Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tag as pending
Processing commands for cont...@bugs.debian.org: > tag 1042285 pending Bug #1042285 [src:qt6-wayland] qt6-wayland: FTBFS: dh_missing: error: missing files, aborting Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042224: marked as done (trinity: FTBFS: ioctls/kvm.c:11:15: error: ‘KVM_SET_MEMORY_REGION’ undeclared here (not in a function); did you mean ‘KVM_SET_USER_MEMORY_REGION’?)
Your message dated Fri, 28 Jul 2023 22:12:07 +
with message-id
and subject line Bug#1042224: fixed in trinity 1.9+git20230728.e71872454d26-1
has caused the Debian Bug report #1042224,
regarding trinity: FTBFS: ioctls/kvm.c:11:15: error: ‘KVM_SET_MEMORY_REGION’
undeclared here (not in a function); did you mean ‘KVM_SET_USER_MEMORY_REGION’?
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.)
--
1042224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trinity
Version: 1.9+git20230109.87f1530-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -Wall -Wextra -I. -Iinclude/ -include
> config.h -Wimplicit -D_GNU_SOURCE -D__linux__ -std=gnu11 -Wformat=2
> -Winit-self -Wnested-externs -Wpacked -Wshadow -Wswitch-enum -Wundef
> -Wwrite-strings -Wno-format-nonliteral -Wstrict-prototypes
> -Wmissing-prototypes -fsigned-char -Wno-missing-field-initializers
> -Wlogical-op -Wstrict-aliasing=3 -o ioctls/kvm.o -c ioctls/kvm.c
> In file included from ioctls/kvm.c:7:
> ioctls/kvm.c:11:15: error: ‘KVM_SET_MEMORY_REGION’ undeclared here (not in a
> function); did you mean ‘KVM_SET_USER_MEMORY_REGION’?
>11 | IOCTL(KVM_SET_MEMORY_REGION),
> | ^
> include/ioctls.h:53:22: note: in definition of macro ‘IOCTL’
>53 | { .request = _request, .name = #_request, }
> | ^~~~
> cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -Wall -Wextra -I. -Iinclude/ -include
> config.h -Wimplicit -D_GNU_SOURCE -D__linux__ -std=gnu11 -Wformat=2
> -Winit-self -Wnested-externs -Wpacked -Wshadow -Wswitch-enum -Wundef
> -Wwrite-strings -Wno-format-nonliteral -Wstrict-prototypes
> -Wmissing-prototypes -fsigned-char -Wno-missing-field-initializers
> -Wlogical-op -Wstrict-aliasing=3 -o ioctls/logger.o -c ioctls/logger.c
> make[2]: *** [Makefile:117: ioctls/kvm.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/07/26/trinity_1.9+git20230109.87f1530-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: trinity
Source-Version: 1.9+git20230728.e71872454d26-1
Done: gustavo panizzo
We believe that the bug you reported is fixed in the latest version of
trinity, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1042...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gustavo panizzo (supplier of updated trinity package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 28 Jul 2023 23:14:24 +0200
Source: trinity
Architecture: source
Version: 1.9+git20230728.e71872454d26-1
Distribution: unstable
Urgency: medium
Maintainer: gustavo panizzo
Changed-By: gustavo panizzo
Closes: 1042224
Changes:
trinity (1.9+git20230728.e71872454d26-1) unstable; urgency=medium
.
* Package an upstream snapshot (Closes: #1042224)
Checksums-Sha1:
28951141be45f49fb13a0ee397c1960d72f28109 1460
trinity_1.9+git20230728.e71872454d26-1.dsc
b9d432ca989c89ea3fafc9817ceb72e7311221e5 278937
trinity_1.9+git20230728.e71872454d26.orig.tar.gz
Bug#1041447: marked as done (comitup: fails to install, remove, distupgrade, and install again)
Your message dated Fri, 28 Jul 2023 22:06:28 + with message-id and subject line Bug#1041447: fixed in comitup 1.38-2 has caused the Debian Bug report #1041447, regarding comitup: fails to install, remove, distupgrade, and install again 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.) -- 1041447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041447 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: comitup Version: 1.38-1.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install (in 'bullseye'), remove (but not purge), distupgrade to 'bookworm', and install again. Before the second installation the package is in config-files-remaining state. The configuration is remaining from the last version that was successfully configured - which is from the previous release. Like a plain failure on initial install this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): ... Setting up comitup (1.15-1) ... comitup-no-wifi - No wifi devices found Comitup is a wifi device manager. 'sudo iw list' indicates that there are no devices to manage. Created symlink /etc/systemd/system/multi-user.target.wants/comitup.service → /lib/systemd/system/comitup.service. ... Removing comitup (1.15-1) ... ... Setting up comitup (1.38-1.1) ... Installing new version of config file /etc/comitup.conf ... [ESC][0;1;31mFailed to enable unit, unit /etc/systemd/system/comitup.service is masked.[ESC][0m dpkg: error processing package comitup (--configure): installed comitup package post-installation script subprocess returned error exit status 1 Processing triggers for dbus (1.14.8-2~deb12u1) ... Errors were encountered while processing: comitup ... cheers, Andreas comitup_1.38-1.1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: comitup Source-Version: 1.38-2 Done: David Steele We believe that the bug you reported is fixed in the latest version of comitup, 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 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Steele (supplier of updated comitup package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 28 Jul 2023 17:12:44 -0400 Source: comitup Architecture: source Version: 1.38-2 Distribution: unstable Urgency: medium Maintainer: David Steele Changed-By: David Steele Closes: 1041447 Changes: comitup (1.38-2) unstable; urgency=medium . * Ensure service is unmasked in post install (Closes: #1041447). Checksums-Sha1: d558d1accf0a126e7ad93cf0ffc65a4ed7a86e3b 2438 comitup_1.38-2.dsc 19403510af1c45b92171b2ce0e6c987607e0a865 18884 comitup_1.38-2.debian.tar.xz 98ff314b63bb7570219b4577bbc5c1d05147deda 7337 comitup_1.38-2_source.buildinfo Checksums-Sha256: 3bb195aa1f844012cc61391798fd7b82359107c991d32ecbcd97f8e1eec2c2c0 2438 comitup_1.38-2.dsc 2dc5f45452a842e89adaa8faccadbd3f6a8fddd6776c833c92bc1b9e3d6c 18884 comitup_1.38-2.debian.tar.xz 20d6d6c4333bd943cf87c770f97aeea30b5f79f24475dd3ede816ed98b5acad6 7337 comitup_1.38-2_source.buildinfo Files: 827d7b86ba28c3a6e4ead2924d9321d8 2438 net optional comitup_1.38-2.dsc 9dea059179366999412c91ba2bc8d672 18884 net optional comitup_1.38-2.debian.tar.xz 6a458d4cc7452112ef3a4779bb1054df 7337 net optional comitup_1.38-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEi4SQsUoAbTYxHS3FCVnEo9z4n78FAmTEOBUSHHN0ZWVsZUBk ZWJpYW4ub3JnAAoJEAlZxKPc+J+/6dgQAI5StrJUvGPQEsNSRHUS8U7LmQcrgoMw H20pEQKhEfgvNrhlfQi8SECMdL8SttT6PCVrWMsV8k70hphRHFQvv/j4LIOXdoq8 oK5fP/BKOdT53wmTmDvXS/T1DZ55W6tzRIVVvjiPbfOyQQrvCPdlzJ9VauLKclku V1v5I6BfKrCeLkjhr/roLCa8g27xzfk1muWOnkUuoGa62JzHHkQq98dXSIh9c0oW Ks6PaLpNN0F9N0SkdBr29qQjRtfV+RT85Uy35IDyGhub6c44IgJ6e0uRzYeC1lBB pmid1IDl+T5H1Z+ItE8yz4LxBAncLZ84kTcz8TXvDluxbYcEqWnowe/3xymu5dLW Byfl1uoSY5fITsOWLegmdu8O7rADt1YJFfO0mawPYQvAxoICJTv7AcR/TxSYNrLq Ps6atdIXo+ErbbNUl2nhLZfzQMTi94PXSj6+oROs8/U0IvfiqagrY2w/6tHNS/Pw
Processed: Tag as pending
Processing commands for cont...@bugs.debian.org: > tag 1042304 pending Bug #1042304 [src:qt6-scxml] qt6-scxml: FTBFS: dh_missing: error: missing files, aborting Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042304 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 925834
Processing commands for cont...@bugs.debian.org: > tags 925834 + ftbfs Bug #925834 [src:spd] spd: ftbfs with GCC-9 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 925834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925834 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 925834
Processing commands for cont...@bugs.debian.org: > tags 925834 + ftbfs Bug #925834 [src:spd] spd: ftbfs with GCC-9 Ignoring request to alter tags of bug #925834 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 925834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925834 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 1037753 1042028
Processing commands for cont...@bugs.debian.org:
> forcemerge 1037753 1042028
Bug #1037753 {Done: Dennis Filder } [src:lime] lime: ftbfs
with GCC-13
Bug #1042028 [src:lime] lime: FTBFS: lime_settings.hpp:49:24: error: ‘uint16_t’
in namespace ‘std’ does not name a type; did you mean ‘wint_t’?
1042028 was blocked by: 1041349
1042028 was not blocking any bugs.
Removed blocking bug(s) of 1042028: 1041349
Marked Bug as done
Marked as fixed in versions lime/5.2.0+dfsg-2.
Bug #1037753 {Done: Dennis Filder } [src:lime] lime: ftbfs
with GCC-13
Added tag(s) ftbfs.
Merged 1037753 1042028
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1037753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037753
1042028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Tag as pending
Processing commands for cont...@bugs.debian.org: > tag 1042257 pending Bug #1042257 [src:qt6-serialbus] qt6-serialbus: FTBFS: dh_missing: error: missing files, aborting Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037579: Patch for FTBFS
tags 1037579 + patch thanks Dear maintainers, please find attached a patch to fix the FTBFS with gcc13. The main issue was missing headers for the uint32_t and uint64_t definitions. I can prepare an NMU in case you don't have time to upload new package. Best Regards, François Author: Francois Mazen Description: Fix fail to build from source due to missing header with GCC13. Forwarded: not-needed --- a/src/armnnUtils/VerificationHelpers.hpp +++ b/src/armnnUtils/VerificationHelpers.hpp @@ -4,6 +4,7 @@ // #include +#include #include #include --- a/include/armnn/profiling/ISendTimelinePacket.hpp +++ b/include/armnn/profiling/ISendTimelinePacket.hpp @@ -6,6 +6,7 @@ #pragma once #include +#include #include #include signature.asc Description: This is a digitally signed message part
Processed: tagging 985813
Processing commands for cont...@bugs.debian.org: > tags 985813 + ftbfs Bug #985813 [rust-libnotcurses-sys] rust-libnotcurses-sys FTBFS ffi related errors. Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 985813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985813 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Tag as pending
Processing commands for cont...@bugs.debian.org: > tag 1042273 pending Bug #1042273 [src:qt6-connectivity] qt6-connectivity: FTBFS: dh_missing: error: missing files, aborting Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tag as pending
Processing commands for cont...@bugs.debian.org: > tag 1042323 pending Bug #1042323 [src:qt6-charts] qt6-charts: FTBFS: dh_missing: error: missing files, aborting Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042460: found 1042460 in 1:8.4p1-5, closing 1042460
found 1042460 1:8.4p1-5 close 1042460 1:9.3p2-1 thanks
Bug#1042297: marked as done (qt6-virtualkeyboard: FTBFS: dh_missing: error: missing files, aborting)
Your message dated Fri, 28 Jul 2023 16:44:11 -0300
with message-id <3241362.Fm8zU9ui5b@gryffindor>
and subject line Re: Bug#1042297: qt6-virtualkeyboard: FTBFS: dh_missing:
error: missing files, aborting
has caused the Debian Bug report #1042297,
regarding qt6-virtualkeyboard: FTBFS: dh_missing: error: missing files, aborting
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.)
--
1042297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qt6-virtualkeyboard
Version: 6.4.2+dfsg-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Reproducible builds: remove build paths from .prl files
> sed -i -e '/^QMAKE_PRL_BUILD_DIR/d'
> debian/tmp/usr/lib/x86_64-linux-gnu/libQt6*.prl
> make[1]: Leaving directory '/<>'
>dh_install -O--buildsystem=cmake\+ninja
>dh_installdocs -O--buildsystem=cmake\+ninja
>dh_installchangelogs -O--buildsystem=cmake\+ninja
>dh_installsystemduser -O--buildsystem=cmake\+ninja
>dh_perl -O--buildsystem=cmake\+ninja
>dh_link -O--buildsystem=cmake\+ninja
>dh_strip_nondeterminism -O--buildsystem=cmake\+ninja
>dh_compress -O--buildsystem=cmake\+ninja
>dh_fixperms -O--buildsystem=cmake\+ninja
>dh_missing -O--buildsystem=cmake\+ninja
> dh_missing: warning:
> usr/lib/x86_64-linux-gnu/qt6/examples/virtualkeyboard/basic/basic exists in
> debian/tmp but is not installed to anywhere
> dh_missing: error: missing files, aborting
> The following debhelper tools have reported what they installed (with
> files per package)
>* dh_install: libqt6hunspellinputmethod6 (2), libqt6virtualkeyboard6
> (2), qml6-module-qtquick-virtualkeyboard (71), qt6-virtualkeyboard-dev (56),
> qt6-virtualkeyboard-plugin (1)
>* dh_installdocs: libqt6hunspellinputmethod6 (0),
> libqt6virtualkeyboard6 (0), qml6-module-qtquick-virtualkeyboard (0),
> qt6-virtualkeyboard-dev (0), qt6-virtualkeyboard-plugin (0)
> If the missing files are installed by another tool, please file a bug
> against it.
> When filing the report, if the tool is not part of debhelper itself,
> please reference the
> "Logging helpers and dh_missing" section from the "PROGRAMMING" guide
> for debhelper (10.6.3+).
> (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
> Be sure to test with dpkg-buildpackage -A/-B as the results may vary
> when only a subset is built
> If the omission is intentional or no other helper can take care of this
> consider adding the
> paths to debian/not-installed.
>
> Remember to be careful with paths containing "x86_64-linux-gnu", where
> you might need to
> use a wildcard or (assuming compat 13+) e.g. ${DEB_HOST_MULTIARCH} in
> debian/not-installed
> to ensure it works on all architectures (see #961104).
> make: *** [debian/rules:12: binary] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/07/26/qt6-virtualkeyboard_6.4.2+dfsg-2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 6.4.2+dfsg-3
Hi Lucas!
This was actually fixed already in the archive by version -3, so closing.
Thanks for your work, Lisandro.
El miércoles, 26 de julio de 2023 17:14:13 -03 Lucas Nussbaum escribió:
> Source: qt6-virtualkeyboard
> Version: 6.4.2+dfsg-2
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20230726 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > # Reproducible builds:
Processed: found 1042460 in 1:8.4p1-5, closing 1042460
Processing commands for cont...@bugs.debian.org: > found 1042460 1:8.4p1-5 Bug #1042460 [openssh-client] openssh-client: ssh-agent CVE-2023-38408 Marked as found in versions openssh/1:8.4p1-5. > close 1042460 1:9.3p2-1 Bug #1042460 [openssh-client] openssh-client: ssh-agent CVE-2023-38408 Marked as fixed in versions openssh/1:9.3p2-1. Bug #1042460 [openssh-client] openssh-client: ssh-agent CVE-2023-38408 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1042460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042460 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042297: qt6-virtualkeyboard: FTBFS: dh_missing: error: missing files, aborting
Version: 6.4.2+dfsg-3
Hi Lucas!
This was actually fixed already in the archive by version -3, so closing.
Thanks for your work, Lisandro.
El miércoles, 26 de julio de 2023 17:14:13 -03 Lucas Nussbaum escribió:
> Source: qt6-virtualkeyboard
> Version: 6.4.2+dfsg-2
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20230726 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > # Reproducible builds: remove build paths from .prl files
> > sed -i -e '/^QMAKE_PRL_BUILD_DIR/d'
> > debian/tmp/usr/lib/x86_64-linux-gnu/libQt6*.prl
> > make[1]: Leaving directory '/<>'
> >dh_install -O--buildsystem=cmake\+ninja
> >dh_installdocs -O--buildsystem=cmake\+ninja
> >dh_installchangelogs -O--buildsystem=cmake\+ninja
> >dh_installsystemduser -O--buildsystem=cmake\+ninja
> >dh_perl -O--buildsystem=cmake\+ninja
> >dh_link -O--buildsystem=cmake\+ninja
> >dh_strip_nondeterminism -O--buildsystem=cmake\+ninja
> >dh_compress -O--buildsystem=cmake\+ninja
> >dh_fixperms -O--buildsystem=cmake\+ninja
> >dh_missing -O--buildsystem=cmake\+ninja
> > dh_missing: warning:
> > usr/lib/x86_64-linux-gnu/qt6/examples/virtualkeyboard/basic/basic exists in
> > debian/tmp but is not installed to anywhere
> > dh_missing: error: missing files, aborting
> > The following debhelper tools have reported what they installed (with
> > files per package)
> > * dh_install: libqt6hunspellinputmethod6 (2), libqt6virtualkeyboard6
> > (2), qml6-module-qtquick-virtualkeyboard (71), qt6-virtualkeyboard-dev
> > (56), qt6-virtualkeyboard-plugin (1)
> > * dh_installdocs: libqt6hunspellinputmethod6 (0),
> > libqt6virtualkeyboard6 (0), qml6-module-qtquick-virtualkeyboard (0),
> > qt6-virtualkeyboard-dev (0), qt6-virtualkeyboard-plugin (0)
> > If the missing files are installed by another tool, please file a bug
> > against it.
> > When filing the report, if the tool is not part of debhelper itself,
> > please reference the
> > "Logging helpers and dh_missing" section from the "PROGRAMMING" guide
> > for debhelper (10.6.3+).
> > (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
> > Be sure to test with dpkg-buildpackage -A/-B as the results may vary
> > when only a subset is built
> > If the omission is intentional or no other helper can take care of this
> > consider adding the
> > paths to debian/not-installed.
> >
> > Remember to be careful with paths containing "x86_64-linux-gnu", where
> > you might need to
> > use a wildcard or (assuming compat 13+) e.g. ${DEB_HOST_MULTIARCH} in
> > debian/not-installed
> > to ensure it works on all architectures (see #961104).
> > make: *** [debian/rules:12: binary] Error 25
>
>
> The full build log is available from:
> http://qa-logs.debian.net/2023/07/26/qt6-virtualkeyboard_6.4.2+dfsg-2_unstable.log
>
> All bugs filed during this archive rebuild are listed at:
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
> or:
> https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results
>
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
>
> If you reassign this bug to another package, please mark it as 'affects'-ing
> this package. See https://www.debian.org/Bugs/server-control#affects
>
> If you fail to reproduce this, please provide a build log and diff it with
> mine
> so that we can identify if something relevant changed in the meantime.
>
>
signature.asc
Description: This is a digitally signed message part.
Bug#1042469: ocamldap FTBFS without pcre-ocaml
Source: ocamldap Version: 2.4.2-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=ocamldap=arm64=2.4.2-3%2Bb3=1690571368=0 ... dh_auto_build -a -O--buildsystem=ocaml_dune dune build -p ldap File "src/ldap/dune", line 9, characters 17-21: 9 | (libraries str pcre ssl)) Error: Library "pcre" not found. -> required by library "ldap" in _build/default/src/ldap -> required by _build/default/META.ldap -> required by _build/install/default/lib/ldap/META -> required by _build/default/ldap.install -> required by alias install dh_auto_build: error: dune build -p ldap returned exit code 1 make: *** [debian/rules:7: binary-arch] Error 25
Processed: closing 1042214
Processing commands for cont...@bugs.debian.org: > close 1042214 4.4.1-1 Bug #1042214 [src:guiqwt] guiqwt: FTBFS: ImportError: cannot import name 'get_subpackages' from 'guidata.utils' (/usr/lib/python3/dist-packages/guidata/utils/__init__.py) Marked as fixed in versions guiqwt/4.4.1-1. Bug #1042214 [src:guiqwt] guiqwt: FTBFS: ImportError: cannot import name 'get_subpackages' from 'guidata.utils' (/usr/lib/python3/dist-packages/guidata/utils/__init__.py) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1042214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042214: closing 1042214
close 1042214 4.4.1-1 thanks solver with a previous upload
Bug#1042419: marked as done (rust-ureq - update for new cookie-store)
Your message dated Fri, 28 Jul 2023 18:22:12 + with message-id and subject line Bug#1042419: fixed in rust-ureq 2.7.1-2 has caused the Debian Bug report #1042419, regarding rust-ureq - update for new cookie-store 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.) -- 1042419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rust-ureq Tags: trixie, sid Severity: serious I just updated rust-cookie-store. Ureq needs it's debian dependencies adjusting to account for this (the cargo dependencies already allow the new version. Debdiff attatched, I may or may not NMU this later.diff -Nru rust-ureq-2.7.1/debian/changelog rust-ureq-2.7.1/debian/changelog --- rust-ureq-2.7.1/debian/changelog2023-07-16 22:38:59.0 + +++ rust-ureq-2.7.1/debian/changelog2023-07-28 02:54:32.0 + @@ -1,3 +1,11 @@ +rust-ureq (2.7.1-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Bump debian dependency on cookie_store to 0.19 +(cargo dependency already allows this version) + + -- Peter Michael Green Fri, 28 Jul 2023 02:54:32 + + rust-ureq (2.7.1-1) unstable; urgency=medium [ upstream ] diff -Nru rust-ureq-2.7.1/debian/control rust-ureq-2.7.1/debian/control --- rust-ureq-2.7.1/debian/control 2023-07-16 10:47:12.0 + +++ rust-ureq-2.7.1/debian/control 2023-07-28 02:54:27.0 + @@ -8,7 +8,7 @@ librust-brotli-decompressor-2+default-dev , librust-chunked-transfer-1+default-dev , librust-cookie-0.16-dev , - librust-cookie-store-0.16+preserve-order-dev , + librust-cookie-store-0.19+preserve-order-dev , librust-encoding-rs-0.8+default-dev , librust-env-logger-0.9+default-dev , librust-flate2-1+default-dev (>= 1.0.22) , @@ -42,7 +42,7 @@ librust-brotli-decompressor-2+default-dev, librust-chunked-transfer-1+default-dev, librust-cookie-0.16-dev, - librust-cookie-store-0.16+preserve-order-dev, + librust-cookie-store-0.19+preserve-order-dev, librust-encoding-rs-0.8+default-dev, librust-flate2-1+default-dev (>= 1.0.22), librust-http-0.2+default-dev, --- End Message --- --- Begin Message --- Source: rust-ureq Source-Version: 2.7.1-2 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of rust-ureq, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated rust-ureq package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 28 Jul 2023 09:25:07 +0200 Source: rust-ureq Architecture: source Version: 2.7.1-2 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Closes: 1042419 Changes: rust-ureq (2.7.1-2) unstable; urgency=medium . * drop patches 2003 2005, obsoleted by Debian package updates; tighten autopkgtest to test feature tls without feature native-certs; tighten (build-)dependencies and autopkgtest-dependencies for crates cookie-store rustls; closes: bug#1042419, thanks to Peter Green * drop superfluous autopkgtest dependencies * change patch 2004 to extend dependency ofr crate rustls-webpki (not switch to webpki, rustls-webpki is in Debian now); (build-)depend on package for crate rustls-webpki (not webpki) Checksums-Sha1: 972ff8511041ad6fbba0168fd5a7a99103f1d4ad 3432 rust-ureq_2.7.1-2.dsc e9800be7ad584b3664ef6d098c5ef12e11863457 14392 rust-ureq_2.7.1-2.debian.tar.xz 22654358a90eb4ff38716a7a1fae9eb3e021285e 16360 rust-ureq_2.7.1-2_amd64.buildinfo Checksums-Sha256: cb4c31e9764808ef93425a10b5a441b8f9070964fed034b420abbcc2e9681747 3432 rust-ureq_2.7.1-2.dsc 846fe7788e5019500f28283408186406a9beca93a5570eb2a71bc3c826f34de9 14392 rust-ureq_2.7.1-2.debian.tar.xz 173a5fa33c7cbcb81d29ac583cda80a21e493faf970cc90705d8519a3102e50f 16360 rust-ureq_2.7.1-2_amd64.buildinfo Files: 58509c8bd83a6016bac88d5238802807 3432 rust optional rust-ureq_2.7.1-2.dsc 049ad7a7b7e2f9f0bc71f51782a246bd 14392 rust optional rust-ureq_2.7.1-2.debian.tar.xz
Processed: bug 1042345 is forwarded to https://github.com/scrapy/w3lib/issues/212
Processing commands for cont...@bugs.debian.org:
> forwarded 1042345 https://github.com/scrapy/w3lib/issues/212
Bug #1042345 [src:python-w3lib] python-w3lib: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Set Bug forwarded-to-address to 'https://github.com/scrapy/w3lib/issues/212'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1042345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1039472: Fix for bookworm available as well?
Hi Andreas, all, we suffer from this issue on bookworm desktops (KDE plasma desktop) where installing arduino causes the troubles described above (… error processing package ca-certificates-java …). For the time being, we decided to skip arduino, but this is no solution in the long run. Are there any plans to fix this in bookworm too? Or is there a workaround available to get rid of the problem? Many thanks and best regards, Andi
Bug#1042354: marked as done (golang-github-marten-seemann-qtls-go1-19: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/marten-seemann/qtls-go1-19 returned exit code 1)
Your message dated Fri, 28 Jul 2023 16:57:02 + with message-id and subject line Bug#1042375: Removed package(s) from unstable has caused the Debian Bug report #1042354, regarding golang-github-marten-seemann-qtls-go1-19: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/marten-seemann/qtls-go1-19 returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-marten-seemann-qtls-go1-19 Version: 0.1.0-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --builddirectory=_build --buildsystem=golang --with=golang >dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang >dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang >dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang >dh_auto_build -O--builddirectory=_build -O--buildsystem=golang > cd _build && go install -trimpath -v -p 8 > github.com/marten-seemann/qtls-go1-19 > internal/goarch > internal/coverage/rtcov > internal/unsafeheader > internal/goos > internal/goexperiment > runtime/internal/syscall > runtime/internal/atomic > internal/race > internal/abi > internal/cpu > runtime/internal/math > runtime/internal/sys > sync/atomic > unicode > unicode/utf8 > container/list > internal/itoa > math/bits > crypto/internal/alias > crypto/subtle > crypto/internal/boring/sig > unicode/utf16 > vendor/golang.org/x/crypto/cryptobyte/asn1 > internal/nettrace > vendor/golang.org/x/crypto/internal/alias > golang.org/x/crypto/internal/alias > golang.org/x/crypto/cryptobyte/asn1 > internal/bytealg > math > runtime > internal/reflectlite > sync > internal/testlog > internal/singleflight > internal/godebug > runtime/cgo > internal/intern > math/rand > errors > sort > io > internal/oserror > path > internal/safefilepath > strconv > crypto/internal/nistec/fiat > syscall > vendor/golang.org/x/net/dns/dnsmessage > hash > bytes > crypto/internal/randutil > strings > crypto > reflect > crypto/rc4 > net/netip > internal/syscall/execenv > time > internal/syscall/unix > context > io/fs > internal/poll > embed > internal/fmtsort > encoding/binary > os > encoding/base64 > crypto/md5 > crypto/internal/edwards25519/field > crypto/cipher > vendor/golang.org/x/crypto/internal/poly1305 > golang.org/x/crypto/internal/poly1305 > crypto/internal/nistec > golang.org/x/crypto/curve25519/internal/field > encoding/pem > crypto/internal/boring > crypto/des > crypto/internal/edwards25519 > crypto/aes > crypto/sha512 > crypto/hmac > crypto/sha1 > crypto/sha256 > vendor/golang.org/x/crypto/chacha20 > vendor/golang.org/x/crypto/hkdf > fmt > net > path/filepath > io/ioutil > crypto/ecdh > golang.org/x/crypto/chacha20 > golang.org/x/crypto/curve25519 > vendor/golang.org/x/sys/cpu > golang.org/x/sys/cpu > golang.org/x/crypto/hkdf > golang.org/x/crypto/chacha20poly1305 > vendor/golang.org/x/crypto/chacha20poly1305 > encoding/hex > net/url > math/big > crypto/elliptic > crypto/internal/bigmod > crypto/internal/boring/bbig > crypto/dsa > crypto/rand > encoding/asn1 > crypto/ed25519 > crypto/rsa > crypto/x509/pkix > vendor/golang.org/x/crypto/cryptobyte > golang.org/x/crypto/cryptobyte > crypto/ecdsa > crypto/x509 > crypto/tls > github.com/marten-seemann/qtls-go1-19 >dh_auto_test -O--builddirectory=_build -O--buildsystem=golang > cd _build && go test -vet=off -v -p 8 > github.com/marten-seemann/qtls-go1-19 > === RUN TestSignatureSelection > --- PASS: TestSignatureSelection (0.00s) > === RUN TestLegacyTypeAndHash > --- PASS: TestLegacyTypeAndHash (0.00s) > === RUN TestSupportedSignatureAlgorithms > --- PASS: TestSupportedSignatureAlgorithms (0.00s) > === RUN TestRoundUp > --- PASS: TestRoundUp (0.00s) > === RUN TestRemovePadding > --- PASS: TestRemovePadding (0.00s) > === RUN TestCertificateSelection > --- PASS: TestCertificateSelection (0.00s) > === RUN TestDynamicRecordSizingWithStreamCipher > --- PASS: TestDynamicRecordSizingWithStreamCipher (0.00s) > === RUN TestDynamicRecordSizingWithCBC > --- PASS: TestDynamicRecordSizingWithCBC (0.00s) > === RUN TestDynamicRecordSizingWithAEAD > --- PASS: TestDynamicRecordSizingWithAEAD (0.00s) > === RUN TestDynamicRecordSizingWithTLSv13 > --- PASS:
Bug#1042102: Also fixed in upstream stable-4.17 branch
This commit got also included in the upstream stable-4.17 branch: https://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=a91b946345b0c0550d0ee28816a15d3fc16abc50 signature.asc Description: This is a digitally signed message part.
Bug#978513: marked as done (kfreebsd-10: non-standard gcc/g++ used for build (gcc-9))
Your message dated Fri, 28 Jul 2023 16:47:41 + with message-id and subject line Bug#1041056: Removed package(s) from unstable has caused the Debian Bug report #978513, regarding kfreebsd-10: non-standard gcc/g++ used for build (gcc-9) 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.) -- 978513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978513 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kfreebsd-10 Severity: important Tags: sid bullseye User: debian-...@lists.debian.org Usertags: non-standard-compiler, gcc-9, gcc-9-legacy This package builds with a non standard compiler version; please check if this package can be built with the default version of gcc/g++, or with gcc-10/g++-10. If the package cannot be built with GCC 10 because of a compiler bug, please file a report for gcc-10. Please keep this report open until the package uses the default compiler version (or gcc-10) for the package build. If the package cannot be built anymore, please file a bug report for ftp.debian.org, asking for the removal of the package. --- End Message --- --- Begin Message --- Version: 10.3~svn300087+ds1-1+rm Dear submitter, as the package kfreebsd-10 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1041056 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#943607: marked as done (pkg-mozilla-archive-keyring: Key expires soon (2019-11-13))
Your message dated Fri, 28 Jul 2023 16:45:27 + with message-id and subject line Bug#1041016: Removed package(s) from unstable has caused the Debian Bug report #943607, regarding pkg-mozilla-archive-keyring: Key expires soon (2019-11-13) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 943607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943607 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pkg-mozilla-archive-keyring Version: 1.2 Severity: important Dear Maintainer, I was recently cleaning up my keystore, when I noticed that the mozilla archive key is about to expire in three weeks: 2019-11-13. You can see it like this: $ apt-key list 06C4AE2A pub rsa4096 2010-11-20 [SC] [expires: 2019-11-13] 85F0 6FBC 75E0 67C3 F305 C3C9 85A3 D265 06C4 AE2A uid [ unknown] Debian Mozilla team APT archive I think it's a bad thing if this key expires before the new key is distributed, so I opened this bug. Let me know if I misunderstood the key system. Cheers, Ben -- System Information: Debian Release: bullseye/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information --- End Message --- --- Begin Message --- Version: 1.2+nmu1+rm Dear submitter, as the package pkg-mozilla-archive-keyring has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1041016 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1040054: marked as done (ruby-fission: autopkgtest needs update for new version of ruby-cfpropertylist: Could not find 'CFPropertyList' (~> 2.2))
Your message dated Fri, 28 Jul 2023 16:42:54 + with message-id and subject line Bug#1040834: Removed package(s) from unstable has caused the Debian Bug report #1040054, regarding ruby-fission: autopkgtest needs update for new version of ruby-cfpropertylist: Could not find 'CFPropertyList' (~> 2.2) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1040054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-fission Version: 0.5.0-4 Severity: serious X-Debbugs-CC: ruby-cfpropertyl...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:ruby-cfpropertylist Dear maintainer(s), With a recent upload of ruby-cfpropertylist the autopkgtest of ruby-fission fails in testing when that autopkgtest is run with the binary packages of ruby-cfpropertylist from unstable. It passes when run with only packages from testing. In tabular form: passfail ruby-cfpropertylistfrom testing3.0.6-2 ruby-fission from testing0.5.0-4 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of ruby-cfpropertylist to testing [1]. Of course, ruby-cfpropertylist shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in ruby-cfpropertylist was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from ruby-cfpropertylist should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=ruby-cfpropertylist https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-fission/34996323/log.gz 31s 31s ┌──┐ 31s │ Checking Rubygems dependency resolution on ruby3.1 │ 31s └──┘ 31s 31s GEM_PATH= ruby3.1 -e gem\ \"fission\" 32s /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'CFPropertyList' (~> 2.2) among 99 total gem(s) (Gem::MissingSpecError) 32s Checked in 'GEM_PATH=/home/debci/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0' at: /usr/share/rubygems-integration/all/specifications/fission-0.5.0.gemspec, execute `gem env` for more information 32s from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in `block in activate_dependencies' 32s from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' 32s from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `activate_dependencies' 32s from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in `activate' 32s from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `block in gem' 32s from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `synchronize' 32s from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `gem' 32sfrom -e:1:in `' 32s /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not find 'CFPropertyList' (~> 2.2) - did find: [CFPropertyList-3.0.6] (Gem::MissingSpecVersionError) 32s Checked in 'GEM_PATH=/home/debci/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0' , execute `gem env` for more information 32s from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1411:in `block in activate_dependencies' 32s from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' 32s from
Bug#947521: marked as done (florence: build-depends on deprecated gnome-doc-utils)
Your message dated Fri, 28 Jul 2023 16:41:33 + with message-id and subject line Bug#1040826: Removed package(s) from unstable has caused the Debian Bug report #947521, regarding florence: build-depends on deprecated gnome-doc-utils 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.) -- 947521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: florence Version: 0.6.3-1.2 Severity: important Control: block 936625 by -1 Control: block 889019 by -1 User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs gnome-doc-utils This package Build-Depends on gnome-doc-utils. gnome-doc-utils is a deprecated package of documentation utilities. Its most recent upstream release was in 2012, with most changes in its git repository since then being translation updates. The GNOME team do not consider gnome-doc-utils to be suitable for release in Debian 11 'bullseye'. The supported replacement is yelp.m4 in yelp-tools, as used in many GNOME 3 packages. A porting guide is available: https://wiki.gnome.org/Initiatives/GnomeGoals/NewDocumentationInfrastructure gnome-doc-utils relies on Python 2 code that seems unlikely to be converted to Python 3, so bug #936625 (part of the effort to remove Python 2 from Debian for Debian 11 'bullseye') has its severity set to serious. This means that this bug is highly likely to be elevated to serious severity at some point in future. Please convert this package to use yelp-tools, or if necessary remove the documentation processing entirely. Thanks, smcv --- End Message --- --- Begin Message --- Version: 0.6.3-1.2+rm Dear submitter, as the package florence has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1040826 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#972261: marked as done (FTBFS with OCaml 4.11.1 (-unsafe-string is not available))
Your message dated Fri, 28 Jul 2023 16:41:00 + with message-id and subject line Bug#1040821: Removed package(s) from unstable has caused the Debian Bug report #972261, regarding FTBFS with OCaml 4.11.1 (-unsafe-string is not available) 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.) -- 972261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ocaml-melt Version: 1.4.0-3 Severity: serious Tags: ftbfs Dear Maintainer, Your package ocaml-melt FTBFS with OCaml 4.11.1 because -unsafe-string is no longer available. Cheers, -- Stéphane -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Version: 1.4.0-3+rm Dear submitter, as the package ocaml-melt has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1040821 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1039916: marked as done (ruby-derailed-benchmarks: autopkgtest needs update for new version of ruby-memory-profiler: Could not find 'memory_profiler' (~> 0))
Your message dated Fri, 28 Jul 2023 16:40:33 + with message-id and subject line Bug#1040798: Removed package(s) from unstable has caused the Debian Bug report #1039916, regarding ruby-derailed-benchmarks: autopkgtest needs update for new version of ruby-memory-profiler: Could not find 'memory_profiler' (~> 0) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1039916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039916 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-derailed-benchmarks Version: 1.7.0-2 Severity: serious X-Debbugs-CC: ruby-memory-profi...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:ruby-memory-profiler Dear maintainer(s), With a recent upload of ruby-memory-profiler the autopkgtest of ruby-derailed-benchmarks fails in testing when that autopkgtest is run with the binary packages of ruby-memory-profiler from unstable. It passes when run with only packages from testing. In tabular form: passfail ruby-memory-profiler from testing1.0.1-2 ruby-derailed-benchmarks from testing1.7.0-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of ruby-memory-profiler to testing [1]. Of course, ruby-memory-profiler shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in ruby-memory-profiler was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from ruby-memory-profiler should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=ruby-memory-profiler https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-derailed-benchmarks/34928925/log.gz 19s 19s ┌──┐ 19s │ Checking Rubygems dependency resolution on ruby3.1 │ 19s └──┘ 19s 19s GEM_PATH= ruby3.1 -e gem\ \"derailed_benchmarks\" 19s /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'memory_profiler' (~> 0) among 102 total gem(s) (Gem::MissingSpecError) 19s Checked in 'GEM_PATH=/home/debci/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0' at: /usr/share/rubygems-integration/all/specifications/derailed_benchmarks-1.7.0.gemspec, execute `gem env` for more information 19s from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in `block in activate_dependencies' 19s from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' 19s from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `activate_dependencies' 19s from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in `activate' 19s from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `block in gem' 19s from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `synchronize' 19s from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `gem' 19sfrom -e:1:in `' 19s /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not find 'memory_profiler' (~> 0) - did find: [memory_profiler-1.0.1] (Gem::MissingSpecVersionError) 19s Checked in 'GEM_PATH=/home/debci/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0' , execute `gem env` for more information 19s from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1411:in `block in activate_dependencies'
Bug#1016375: marked as done (openjdk-18 should not be in stable releases)
Your message dated Fri, 28 Jul 2023 16:40:08 + with message-id and subject line Bug#1040789: Removed package(s) from unstable has caused the Debian Bug report #1016375, regarding openjdk-18 should not be in stable releases 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.) -- 1016375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openjdk-18 Version: 18.0.2+9-2 Severity: serious openjdk-18 should not be in stable releases, this bug should keep it out of testing. --- End Message --- --- Begin Message --- Version: 18.0.2+9-2+rm Dear submitter, as the package openjdk-18 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1040789 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1033705: marked as done (golang-gitaly-proto: autopkgtest regression: test dependency ruby-gitaly-proto doesn't exist)
Your message dated Fri, 28 Jul 2023 16:39:39 + with message-id and subject line Bug#1040772: Removed package(s) from unstable has caused the Debian Bug report #1033705, regarding golang-gitaly-proto: autopkgtest regression: test dependency ruby-gitaly-proto doesn't exist 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.) -- 1033705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033705 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-gitaly-proto Version: 1.37.0+dfsg-1 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), Your package has an autopkgtest, great. However, it fails since September 2020. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-gitaly-proto/32182231/log.gz autopkgtest [15:18:15]: test command1: preparing testbed Reading package lists... Building dependency tree... Reading state information... Correcting dependencies...Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) autopkgtest-satdep:amd64 < 0 @iU K Nb Ib > Broken autopkgtest-satdep:amd64 Depends on ruby-gitaly-proto:amd64 < none @un H > Removing autopkgtest-satdep:amd64 because I can't find ruby-gitaly-proto:amd64 Done Done OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 1.37.0+dfsg-1+rm Dear submitter, as the package golang-gitaly-proto has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1040772 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#906011: marked as done (pdftk does not properly attribute iText, may violate GPL)
Your message dated Fri, 28 Jul 2023 16:37:12 +
with message-id
and subject line Bug#1032736: Removed package(s) from unstable
has caused the Debian Bug report #906011,
regarding pdftk does not properly attribute iText, may violate GPL
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.)
--
906011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pdftk
Version: 2.02-2
Severity: serious
Tags: upstream
Justification: Policy 2.1
pdftk is under GPLv2.
It uses at least two LGPLv2 libraries, iText and iconv.
Notably, iText is PDF-processing software essential to pdftk's main purpose.
iText is embedded directly into pdftk's source in modified form
(https://www.pdflabs.com/docs/pdftk-license/).
(iconv does not appear to be embedded.)
It appears that (for iText) it is using the provision allowing converting
LGPLv2 to GPLv2.
In that case, it's bound by GPLv2 2(c), which says:
"If the modified program normally reads commands interactively when run, you
must cause it, when started running for such interactive use in the most
ordinary way, to print or display an announcement including an appropriate
copyright notice".
There is such a notice (pdftk --help) with copyright and warranty info.
However, it does not mention iText.
Alternatively, if it is using LGPLv2 6 ("As an exception to the Sections above,
you may also compile or
link a "work that uses the Library"") (though I am not sure if this is usable
if the library is embedded in the source),
there are similar requirements:
"If the work during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference directing
the user to the copy of this License."
All the authors of iText should be included in this runtime copyright statement
and the man page.
-- System Information:
Debian Release: 8.11
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages pdftk depends on:
ii libc6 2.19-18+deb8u10
ii libgcc1 1:4.9.2-10+deb8u1
ii libgcj154.9.2-10+deb8u1
ii libstdc++6 4.9.2-10+deb8u1
pdftk recommends no packages.
Versions of packages pdftk suggests:
ii poppler-utils [xpdf-utils] 0.26.5-2+deb8u4
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.02-5+rm
Dear submitter,
as the package pdftk has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1032736
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#901761: marked as done (Not installable at amd64 because of libgcj17 dependency)
Your message dated Fri, 28 Jul 2023 16:37:12 + with message-id and subject line Bug#1032736: Removed package(s) from unstable has caused the Debian Bug report #901761, regarding Not installable at amd64 because of libgcj17 dependency 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.) -- 901761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pdftk Version: 2.02-4+b2 I am using the Docker image debian:sid and I am executing "apt-get install pdftk". The output is The following packages have unmet dependencies: pdftk : Depends: libgcj17 (>= 5) but it is not installable E: Unable to correct problems, you have held broken packages. I see at https://packages.debian.org/de/sid/pdftk that pdftk depends on libgcj17, which is only available at hurd-i386, kfreebsd-amd64, and kfreebsd-i386 (https://packages.debian.org/de/sid/libgcj17). Checking debian strech, I found that libgcj17 is available for amd64 (https://packages.debian.org/de/stretch/libgcj17). Does the build of pdftk be modified or should the team behind libgcj17 be contacted? --- End Message --- --- Begin Message --- Version: 2.02-5+rm Dear submitter, as the package pdftk has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1032736 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#892539: marked as done (pdftk: Depends on GCJ which is going away)
Your message dated Fri, 28 Jul 2023 16:37:12 + with message-id and subject line Bug#1032736: Removed package(s) from unstable has caused the Debian Bug report #892539, regarding pdftk: Depends on GCJ which is going away 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.) -- 892539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pdftk Severity: serious Tags: sid buster User: debian-...@lists.debian.org Usertags: gcj-rm Hi, pdftk depends or build-depends on GCJ. GCJ has been dropped upstream since GCC 7, so we are dropping it from Debian. Thus please either drop support for GCJ if you are just building an alternative package with GCJ support (e.g. ant-gcj, ecj-gcj) or switch to default-jdk / default-jre as appropriate. Cheers, Emilio --- End Message --- --- Begin Message --- Version: 2.02-5+rm Dear submitter, as the package pdftk has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1032736 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: Bug#1037579: Patch for FTBFS
Processing commands for cont...@bugs.debian.org: > tags 1037579 + patch Bug #1037579 [src:armnn] armnn: ftbfs with GCC-13 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1037579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1041789: RM: unison-2.51+4.13.1 -- RoQA; newer version packaged
Processing control commands: > reassign -1 ftp.debian.org Bug #1041789 [src:unison-2.51+4.13.1] RM: unison-2.51+4.13.1 -- RoQA; newer version packaged Bug reassigned from package 'src:unison-2.51+4.13.1' to 'ftp.debian.org'. No longer marked as found in versions unison-2.51+4.13.1/2.51.5-1. Ignoring request to alter fixed versions of bug #1041789 to the same values previously set -- 1041789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041789: RM: unison-2.51+4.13.1 -- RoQA; newer version packaged
Control: reassign -1 ftp.debian.org Le 23/07/2023 à 18:49, Bastian Germann a écrit : Source: unison-2.51+4.13.1 Version: 2.51.5-1 Severity: serious Why is unison-2.51+4.13.1 not removed yet when unison-2.52 is available? It is OK to remove unison-2.51+4.13.1 from unstable now. Note that I would like to keep unison-2.52 (even if a newer version is packaged) at least in trixie, to allow synchronizing between bookworm and trixie. Cheers, -- Stéphane
Processed: reopening 1042431
Processing commands for cont...@bugs.debian.org:
> reopen 1042431
Bug #1042431 {Done: Wouter Verhelst }
[src:libmedia-convert-perl] libmedia-convert-perl: autopkgtest fails
'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 libmedia-convert-perl/1.0.5-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1042431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1039922: marked as done (mesa breaks gtk4 autopkgtest: panel surface gone)
Your message dated Fri, 28 Jul 2023 15:21:14 + with message-id and subject line Bug#1039922: fixed in mesa 23.1.4-1 has caused the Debian Bug report #1039922, regarding mesa breaks gtk4 autopkgtest: panel surface gone 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.) -- 1039922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039922 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mesa, gtk4 Control: found -1 mesa/23.1.2-1 Control: found -1 gtk4/4.8.3+ds-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of mesa the autopkgtest of gtk4 fails in testing when that autopkgtest is run with the binary packages of mesa from unstable. It passes when run with only packages from testing. In tabular form: passfail mesa from testing23.1.2-1 gtk4 from testing4.8.3+ds-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of mesa to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=mesa https://ci.debian.net/data/autopkgtest/testing/amd64/g/gtk4/34938030/log.gz 227s Waiting for socket... 227s Date: 2023-06-29 UTC 227s [02:18:03.553] weston 10.0.1 227shttps://wayland.freedesktop.org 227sBug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/ 227sBuild: 10.0.1 227s [02:18:03.553] Command line: weston --backend=headless-backend.so --socket=wayland-152 --idle-time=0 227s [02:18:03.553] OS: Linux, 6.1.0-9-amd64, #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08), x86_64 227s [02:18:03.553] Flight recorder: enabled 227s [02:18:03.553] Starting with no config file. 227s [02:18:03.553] Output repaint window is 7 ms maximum. 227s [02:18:03.553] Loading module '/usr/lib/x86_64-linux-gnu/libweston-10/headless-backend.so' 227s [02:18:03.553] Registered plugin API 'weston_windowed_output_api_v1' of size 16 227s [02:18:03.553] Color manager: no-op 227s [02:18:03.553] Output 'headless' using color profile: built-in default sRGB SDR profile 227s [02:18:03.553] Output 'headless' enabled with head(s) headless 227s [02:18:03.553] Compositor capabilities: 227sarbitrary surface rotation: no 227sscreen capture uses y-flip: no 227scursor planes: no 227sarbitrary resolutions: no 227sview mask clipping: no 227sexplicit sync: no 227scolor operations: no 227spresentation clock: CLOCK_MONOTONIC_RAW, id 4 227spresentation clock resolution: 0.1 s 227s [02:18:03.553] Loading module '/usr/lib/x86_64-linux-gnu/weston/desktop-shell.so' 227s [02:18:03.553] launching '/usr/lib/x86_64-linux-gnu/weston-keyboard' 227s [02:18:03.554] Note: support for the deprecated wl_shell interface is disabled. If a legacy client still needs it, it can be re-enabled by passing -Ddeprecated-wl-shell=true to Meson when building Weston. 227s [02:18:03.554] launching '/usr/lib/x86_64-linux-gnu/weston-desktop-shell' 228s libEGL warning: failed to get driver name for fd 0 228s 228s libEGL warning: MESA-LOADER: failed to retrieve device information 228s 228s libEGL warning: failed to get driver name for fd 0 228s 230s [02:18:06.642] caught signal 15 230s [02:18:06.642] panel surface gone 230s [02:18:06.642] background surface gone 230s autopkgtest [02:18:06]: test python3-gi-wayland OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: mesa Source-Version: 23.1.4-1 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of mesa, 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 1039...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen
Bug#1042408: pyglet: requires update for ffmpeg 6.0
Hi, On Thu, 27 Jul 2023 21:05:04 +0200 Sebastian Ramacher wrote: python3-pyglet hard-codes dependencies of libraries from ffmpeg. As ffmpeg is currently undergoing a transition due to SONAME bumps, please update the package accordingly. I can update the dependencies manually again, but I'd prefer a more automated option in the long run. Maybe d/rules could look for the installed ffmpeg library packages and construct a substitution variable? Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Bug#1042126: marked as done (user-mode-linux: FTBFS: build-dependency not installable: linux-source-6.3)
Your message dated Fri, 28 Jul 2023 14:47:00 + with message-id and subject line Bug#1042126: fixed in user-mode-linux 6.4um1 has caused the Debian Bug report #1042126, regarding user-mode-linux: FTBFS: build-dependency not installable: linux-source-6.3 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.) -- 1042126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: user-mode-linux Version: 6.3um1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), quilt, linux-source-6.3, > python3-docutils, xz-utils, m4, kmod, libvdeplug-dev | libvdeplug2-dev, > libpcap-dev, bc, dpkg (>= 1.16.2), libssl-dev, bison, flex, gcc-multilib, > build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), quilt, linux-source-6.3, > python3-docutils, xz-utils, m4, kmod, libvdeplug-dev, libpcap-dev, bc, dpkg > (>= 1.16.2), libssl-dev, bison, flex, gcc-multilib, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [471 B] > Get:5 copy:/<>/apt_archive ./ Packages [546 B] > Fetched 1974 B in 0s (164 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: linux-source-6.3 but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/07/26/user-mode-linux_6.3um1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: user-mode-linux Source-Version: 6.4um1 Done: Ritesh Raj Sarraf We believe that the bug you reported is fixed in the latest version of user-mode-linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ritesh Raj Sarraf (supplier of updated user-mode-linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 28 Jul 2023 19:24:31 +0530 Source: user-mode-linux Architecture: source Version: 6.4um1 Distribution: unstable Urgency: medium Maintainer: User Mode Linux Maintainers
Bug#1042460: openssh-client: ssh-agent CVE-2023-38408
Package: openssh-client Version: 1:8.4p1-5+deb11u1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: mnalis-debian...@voyager.hr, Debian Security Team "The PKCS#11 feature in ssh-agent in OpenSSH before 9.3p2 has an insufficiently trustworthy search path, leading to remote code execution if an agent is forwarded to an attacker-controlled system." While it does not affect all users of ssh-agent, it does affect many of them and commonly suggested workaround (using jumphosts instead of agent forwarding) is not applicable to many use cases (git push over ssh, using libpam-ssh-agent-auth, etc.) https://security-tracker.debian.org/tracker/CVE-2023-38408 indicates that the new fixed version 1:9.3p2-1 has been uploaded in sid and trixie, however bookworm (stable) and bullseye (oldstable) still have no security fix since CVE release on 2023-07-20. (workaround by pinning fixed version from trixie is not possible, due to significant libraries clash; and there are no Debian backports either) -- System Information: Debian Release: 11.7 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-23-amd64 (SMP w/1 CPU thread) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages openssh-client depends on: ii adduser 3.118 ii dpkg 1.20.12 ii libc6 2.31-13+deb11u6 ii libedit2 3.1-20210910-1 ii libfido2-11.6.0-2 ii libgssapi-krb5-2 1.18.3-6+deb11u3 ii libselinux1 3.1-3 ii libssl1.1 1.1.1n-0+deb11u5 ii passwd1:4.8.1-1 ii zlib1g1:1.2.11.dfsg-2+deb11u2 Versions of packages openssh-client recommends: pn xauth Versions of packages openssh-client suggests: pn keychain pn libpam-ssh pn monkeysphere pn ssh-askpass -- no debconf information
Processed: Re: Bug#1042433: libcerf: FTBFS on mipsel
Processing control commands:
> forcemerge 1042434 -1
Bug #1042434 {Done: Roland Mas } [src:libcerf] libcerf:
base line violatin: builds with -march=native
Bug #1042433 [src:libcerf] libcerf: FTBFS on mipsel
Marked Bug as done
The source libcerf and version 2.3-2 do not appear to match any binary packages
Marked as fixed in versions libcerf/2.3-2.
Bug #1042434 {Done: Roland Mas } [src:libcerf] libcerf:
base line violatin: builds with -march=native
Added tag(s) ftbfs.
Merged 1042433 1042434
--
1042433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042433
1042434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1042433: libcerf: FTBFS on mipsel
Control: forcemerge 1042434 -1 On Fri, Jul 28, 2023 at 10:15:37AM +0200, Sebastian Ramacher wrote: > Source: libcerf > Version: 2.3-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > X-Debbugs-Cc: sramac...@debian.org > > https://buildd.debian.org/status/fetch.php?pkg=libcerf=mipsel=2.3-1=1690485564=0 > > cd /<>/obj-mipsel-linux-gnu/lib && /usr/bin/cc -Dcerf_EXPORTS > -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG > -std=gnu99 -fPIC -pedantic -Wall -Wno-sign-compare -fno-omit-frame-pointer > -march=native -O3 -MD -MT lib/CMakeFiles/cerf.dir/err_fcts.c.o -MF > CMakeFiles/cerf.dir/err_fcts.c.o.d -o CMakeFiles/cerf.dir/err_fcts.c.o -c > /<>/lib/err_fcts.c > cc1: error: ‘-march=mips1’ requires ‘-mfp32’ > cc1: error: ‘-march=mips1’ requires ‘-mfp32’ >... This was effectively the same issue as #1042434, -march=native is known to be buggy on the oldest of the MIPS buildds. > Cheers cu Adrian
Bug#1042419: rust-ureq - update for new cookie-store
On 28/07/2023 08:07, Jonas Smedegaard wrote: Control: block -1 by 1042427 Quoting Peter Green (2023-07-28 05:20:53) I just updated rust-cookie-store. Ureq needs it's debian dependencies adjusting to account for this (the cargo dependencies already allow the new version. Thanks for the update, and the notice. Your package update is however blocked by bug#1042427 :-( Looks like this is now fixed. https://tracker.debian.org/news/1448563/accepted-rust-digest-0107-2-source-into-unstable/ * Enable oid feature and const-oid optional dependency
Bug#1042427: marked as done (librust-sha2-dev: impossible to install)
Your message dated Fri, 28 Jul 2023 15:24:45 +0100 with message-id <0fbca959-256b-d557-7f90-e67b26c4f...@debian.org> and subject line Re: Bug#1042419: rust-ureq - update for new cookie-store has caused the Debian Bug report #1042427, regarding librust-sha2-dev: impossible to install 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.) -- 1042427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042427 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-sha2-dev Version: 0.10.7-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Depends on librust-digest-0.10+oid-dev which is unavailable. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTDZlYACgkQLHwxRsGg ASHr6g/+Iam1nLCjSspAqzN7EPY9XdRv05YR4aSPKGM/qKCxC1Ca9KeR/MUOTOe8 sMiAy/TbsIRiJ+PHRWdYgL9b9HcXkqly5SDauREjjSk15CyYTDUK392asQj/FfID 7YIzC9zbQaIPNreY325XCjakotesb4Oa+WMva2X4Eh2V+xC+dMV2FhzKBMTqGqAP Ua9z4bygdKd96MnGpMfWCAVRv7nE+7MEXImju0n5AalRQ/pj3YGu0Qi9nv5KDwBj bqcfixUXM9H//ledT0RELLEdAd3TGx/tnUG+wf8evQRA8cV7qc+SvnSi3KBM1Nm/ 6EGiw82kGEmrYGn/2oKL0YaqNHVfF0EBDS7t3yDvSf493pwzvLg8b/6KWRgpdY8J 6899uVei8EQW1Glg/aLliq0CpP0L6IpNDERM6Te+OIIhihkKOjv8JTWHX0z7Q8Kj upBBFx8iFUqTdQeilbJPpwup7CgPyQRCwysvSqjeF+6oU/AsQ35Nq+9MzaWVWNet lgTbMZQ7xp3nDHLJPIN68FGSK6XhLGHZk32Hx6Xj4ojaKq3I+1Ctp/455CgXWCwT o9FII/8wcKi+aZpTbwa9O/+wBenYrVfkJIESX11QF2ylaBw+vQUCnQ1ZIfOZBORz UqHZTJbF6Nw72/Z33B0EBty+VzFD/TMBRiLgpTelUyj6gQ7b/VA= =G1HN -END PGP SIGNATURE- --- End Message --- --- Begin Message --- On 28/07/2023 08:07, Jonas Smedegaard wrote: Control: block -1 by 1042427 Quoting Peter Green (2023-07-28 05:20:53) I just updated rust-cookie-store. Ureq needs it's debian dependencies adjusting to account for this (the cargo dependencies already allow the new version. Thanks for the update, and the notice. Your package update is however blocked by bug#1042427 :-( Looks like this is now fixed. https://tracker.debian.org/news/1448563/accepted-rust-digest-0107-2-source-into-unstable/ * Enable oid feature and const-oid optional dependency --- End Message ---
Bug#1041076: dolphin-emu FTBFS with imgui 1.89.6
Upstream is dealing with this here :
https://github.com/dolphin-emu/dolphin/pull/12065
Please find a minimal patch in attachement.
On Fri, 14 Jul 2023 20:09:01 +0300 Adrian Bunk wrote:
> Source: dolphin-emu
> Version: 5.0-19368+dfsg-2
> Severity: serious
> Tags: ftbfs
>
>
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dolphin-emu.html
>
> ...
> In file included from /build/1st/dolphin-emu-5.0-
19368+dfsg/Externals/implot/implot/implot_internal.h:39,
> from /build/1st/dolphin-emu-5.0-
19368+dfsg/Externals/implot/implot/implot_items.cpp:26:
> /usr/include/imgui/imgui_internal.h:101:2: error: #error Please
'#define IMGUI_DEFINE_MATH_OPERATORS' _BEFORE_ including imgui.h!
> 101 | #error Please '#define IMGUI_DEFINE_MATH_OPERATORS' _BEFORE_
including imgui.h!
> | ^
> In file included from /build/1st/dolphin-emu-5.0-
19368+dfsg/Externals/implot/implot/implot_internal.h:39,
> from /build/1st/dolphin-emu-5.0-
19368+dfsg/Externals/implot/implot/implot.cpp:126:
> /usr/include/imgui/imgui_internal.h:101:2: error: #error Please
'#define IMGUI_DEFINE_MATH_OPERATORS' _BEFORE_ including imgui.h!
> 101 | #error Please '#define IMGUI_DEFINE_MATH_OPERATORS' _BEFORE_
including imgui.h!
> | ^
> ...
>
>
--- a/Externals/implot/implot/implot.cpp
+++ b/Externals/implot/implot/implot.cpp
@@ -122,6 +122,7 @@
*/
+#define IMGUI_DEFINE_MATH_OPERATORS
#include "implot.h"
#include "implot_internal.h"
--- a/Externals/implot/implot/implot_internal.h
+++ b/Externals/implot/implot/implot_internal.h
@@ -31,10 +31,6 @@
#pragma once
-#ifndef IMGUI_DEFINE_MATH_OPERATORS
-#define IMGUI_DEFINE_MATH_OPERATORS
-#endif
-
#include
#include "imgui_internal.h"
--- a/Externals/implot/implot/implot_items.cpp
+++ b/Externals/implot/implot/implot_items.cpp
@@ -22,6 +22,7 @@
// ImPlot v0.14
+#define IMGUI_DEFINE_MATH_OPERATORS
#include "implot.h"
#include "implot_internal.h"
--- a/Source/Core/VideoCommon/OnScreenUI.cpp
+++ b/Source/Core/VideoCommon/OnScreenUI.cpp
@@ -356,35 +356,37 @@
}
void OnScreenUI::SetKeyMap(const DolphinKeyMap& key_map)
{
- // Right now this is a 1:1 mapping. But might not be true later
static constexpr DolphinKeyMap dolphin_to_imgui_map = {
ImGuiKey_Tab, ImGuiKey_LeftArrow, ImGuiKey_RightArrow, ImGuiKey_UpArrow,
ImGuiKey_DownArrow, ImGuiKey_PageUp,ImGuiKey_PageDown, ImGuiKey_Home,
ImGuiKey_End, ImGuiKey_Insert,ImGuiKey_Delete, ImGuiKey_Backspace,
- ImGuiKey_Space, ImGuiKey_Enter, ImGuiKey_Escape, ImGuiKey_KeyPadEnter,
+ ImGuiKey_Space, ImGuiKey_Enter, ImGuiKey_Escape, ImGuiKey_KeypadEnter,
ImGuiKey_A, ImGuiKey_C, ImGuiKey_V, ImGuiKey_X,
ImGuiKey_Y, ImGuiKey_Z,
};
- static_assert(dolphin_to_imgui_map.size() == ImGuiKey_COUNT); // Fail if ImGui adds keys
auto lock = GetImGuiLock();
if (!ImGui::GetCurrentContext())
return;
+ m_dolphin_to_imgui_map.clear();
for (int dolphin_key = 0; dolphin_key <= static_cast(DolphinKey::Z); dolphin_key++)
{
-int imgui_key = dolphin_to_imgui_map[DolphinKey(dolphin_key)];
+const int imgui_key = dolphin_to_imgui_map[DolphinKey(dolphin_key)];
if (imgui_key >= 0)
- ImGui::GetIO().KeyMap[imgui_key] = (key_map[DolphinKey(dolphin_key)] & 0x1FF);
+{
+ const int mapped_key = key_map[DolphinKey(dolphin_key)];
+ m_dolphin_to_imgui_map[mapped_key & 0x1FF] = imgui_key;
+}
}
}
void OnScreenUI::SetKey(u32 key, bool is_down, const char* chars)
{
auto lock = GetImGuiLock();
- if (key < std::size(ImGui::GetIO().KeysDown))
-ImGui::GetIO().KeysDown[key] = is_down;
+ if (auto iter = m_dolphin_to_imgui_map.find(key); iter != m_dolphin_to_imgui_map.end())
+ImGui::GetIO().AddKeyEvent((ImGuiKey)iter->second, is_down);
if (chars)
ImGui::GetIO().AddInputCharactersUTF8(chars);
--- a/Source/Core/VideoCommon/OnScreenUI.h
+++ b/Source/Core/VideoCommon/OnScreenUI.h
@@ -3,6 +3,7 @@
#pragma once
+#include
#include
#include
#include
@@ -65,6 +66,7 @@
std::unique_ptr m_imgui_vertex_format;
std::vector> m_imgui_textures;
std::unique_ptr m_imgui_pipeline;
+ std::map m_dolphin_to_imgui_map;
std::mutex m_imgui_mutex;
u64 m_imgui_last_frame_time = 0;
Bug#1042434: marked as done (libcerf: base line violatin: builds with -march=native)
Your message dated Fri, 28 Jul 2023 13:36:40 + with message-id and subject line Bug#1042434: fixed in libcerf 2.3-2 has caused the Debian Bug report #1042434, regarding libcerf: base line violatin: 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.) -- 1042434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042434 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libcerf Version: 2.3-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org Building with -march=native means that whatever instruction set extensions are available on the buildd, are enabled. For example, if the build is performed on any resonably new enough buildd, SSE2 will be enabled on the i386 builds. Users of i386 without this instruction set will be unable to use libcerf. https://buildd.debian.org/status/fetch.php?pkg=libcerf=i386=2.3-1=1690485692=0 [ 1%] Building C object lib/CMakeFiles/cerf.dir/erfcx.c.o cd /<>/obj-i686-linux-gnu/lib && /usr/bin/cc -Dcerf_EXPORTS -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -std=gnu99 -fPIC -pedantic -Wall -Wno-sign-compare -fno-omit-frame-pointer -march=native -O3 -MD -MT lib/CMakeFiles/cerf.dir/erfcx.c.o -MF CMakeFiles/cerf.dir/erfcx.c.o.d -o CMakeFiles/cerf.dir/erfcx.c.o -c /<>/lib/erfcx.c Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: libcerf Source-Version: 2.3-2 Done: Roland Mas We believe that the bug you reported is fixed in the latest version of libcerf, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roland Mas (supplier of updated libcerf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 28 Jul 2023 15:10:23 +0200 Source: libcerf Architecture: source Version: 2.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Roland Mas Closes: 867708 958285 1042434 Changes: libcerf (2.3-2) unstable; urgency=medium . * Bug fix: "base line violatin: builds with -march=native", thanks to Sebastian Ramacher (Closes: #1042434). * Bug fix: "package short description mentions development files instead of documentation", thanks to Beatrice Torracca (Closes: #867708). * Bug fix: "DebSci Additional info upstream homepage (also deprecated Debian CVS note)", thanks to Ben Tris (Closes: #958285). Checksums-Sha1: 61ae166845e765bae1a3bf75750fd81ba8f2307e 2078 libcerf_2.3-2.dsc 651880a628602d38a4a88ae2ce1ee9dad24fe7d1 4332 libcerf_2.3-2.debian.tar.xz f937b2e2429823622d0226988eade54757315220 7520 libcerf_2.3-2_amd64.buildinfo Checksums-Sha256: f68194f4f4bfbfe6a201181f8eff947279e9b2c61e853ebe0f404d9f4e099fc4 2078 libcerf_2.3-2.dsc 47a15ab5c5f2211c6f509cfa8eafabbc7e68277b2f72b35a43474537f10a5652 4332 libcerf_2.3-2.debian.tar.xz 80751f3509d1d44934c819d80217fcb3f3f54bb543ab85c960fd34b484f65b0a 7520 libcerf_2.3-2_amd64.buildinfo Files: 6ee44de56b19e5bc50c2027c381258e8 2078 science optional libcerf_2.3-2.dsc f617b212f1a3c6f1a484fb0445d1cd9c 4332 science optional libcerf_2.3-2.debian.tar.xz a801c4f4baa4bb7cbcfb3300e2a10778 7520 science optional libcerf_2.3-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEtBU2D1kett1zr/uD0w3s0lmTIvwFAmTDvnIACgkQ0w3s0lmT Ivy9VQ//djRjIfIFRSDIalKLMcuvVPRGqJzzHqSH4VHlHhilX41iE8pXalzMojND z0V1aLpYyCUbBz+1/0r5K3xgLMWCUN0fmSaWd/0rpJnok7C12JTYB1c6qYwSsRSA VA/cGE5hXAlSsa4mQjPBVCRaCfhumb5gIvwEb+ls+aFP9VK2T46CdNKs0ax9GQm0 N84o9L2JU88TGR+UIusX4Ql3ufjlcNp2QL0Pgp6sHqy9Vds0bYACqT0/fU53abdc ATZmQQ5hASuCbu9nud0NYk9bTaSgGfWuLoPqNBc1WFe9ch51w6kl3dJMfpn+/IwQ 8pMljf2c47DyY9IdJ8lhjFZdWQmYt/TUAEirDkIz/58hyr0vhwZzS46EqdYzWrvm ZwVkvs+b5yvz+kVGruTuG3Ck9KIlvhwDwZ4asoVAvPYZtVJHXGZDrf+AJPtT2KeB HP4qkQXdGt2TOncWRK5kp7t4pSa5DcqjSGQDsUSCgoElVZuuf3BjvDvso2v/wSLL PObO/86y6ZnJwS3gOEcCl+ymp1Iydl4UOFalcrG3N4APs/mtdo8rYoLeFBHm2PPS Us5fTWsjZIsHp5fKw5A1EanuCJ1kSq1KniKCElghheQnaGb2eYtjNHCJXwPZ4UBM hZFAdw+neUSt1ngXKtNG/XkL2N0X0Yd1X0t2qF1Uqhqai07FyqM= =YKWr -END PGP SIGNATURE End
Bug#1042457: php-net-dns2: incompatible with PHP 8.x: Uncaught ValueError: fread()
Package: php-net-dns2
Version: 1.5.0-1
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: z...@gsystem.sk
Dear Maintainer,
after upgrading to Debian 12, Horde stopped working. It logs messages like:
PHP Fatal error: Uncaught ValueError: fread(): Argument #2 ($length) must be
greater than 0 in /usr/share/php/Net/DNS2/Cache/File.php:142
Stack trace:
#0 /usr/share/php/Net/DNS2/Cache/File.php(142): fread()
#1 [internal function]: Net_DNS2_Cache_File->__destruct()
#2 {main}
thrown in /usr/share/php/Net/DNS2/Cache/File.php on line 142, referer:
https://localhost/horde/imp/dynamic.php?page=mailbox
It's a known bug of Net_DNS2, already fixed upstream.
A quick fix:
--- /usr/share/php/Net/DNS2/Cache/File.php- 2020-10-19 22:19:24.0
+0200
+++ /usr/share/php/Net/DNS2/Cache/File.php 2023-07-28 14:41:16.342298660
+0200
@@ -139,7 +139,11 @@
//
// read the file contents
//
-$data = @fread($fp, filesize($this->cache_file));
+$data = false;
+$file_size = @filesize($this->cache_file);
+if ( ($file_size !== false) && ($file_size > 0) ) {
+$data = @fread($fp, $file_size);
+}
if ( ($data !== false) && (strlen($data) > 0) ) {
//
-- System Information:
Debian Release: 12.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'oldoldstable-updates'), (500, 'oldoldstable'), (500, 'stable'), (100,
'bookworm-fasttrack'), (100, 'bookworm-backports-staging')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-23-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=sk_SK.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages php-net-dns2 depends on:
ii php-common 2:93
php-net-dns2 recommends no packages.
php-net-dns2 suggests no packages.
-- no debconf information
Processed: closing 1041844
Processing commands for cont...@bugs.debian.org: > close 1041844 44.0-1 Bug #1041844 [src:geary] geary FTBFS with vala 0.56.9 Marked as fixed in versions geary/44.0-1. Bug #1041844 [src:geary] geary FTBFS with vala 0.56.9 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1041844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1042255: p11-kit: libsoup3 fails to build from source
Processing commands for cont...@bugs.debian.org: > affects 1042255 src:glib-networking Bug #1042255 [src:p11-kit] libsoup3: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 5 returned exit code 1 Added indication that 1042255 affects src:glib-networking > End of message, stopping processing here. Please contact me if you need assistance. -- 1042255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042352: marked as done (glib-networking: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 3)
Your message dated Fri, 28 Jul 2023 14:09:57 +0300 with message-id and subject line Re: glib-networking: FTBFS has caused the Debian Bug report #1042352, regarding glib-networking: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 3 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.) -- 1042352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glib-networking Version: 2.74.0-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- \ > -Dauto_features=enabled \ > -Denvironment_proxy=disabled \ > -Dinstalled_tests=true > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson setup .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dauto_features=enabled > -Denvironment_proxy=disabled -Dinstalled_tests=true > The Meson build system > Version: 1.2.0 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: glib-networking > Project version: 2.74.0 > C compiler for the host machine: cc (gcc 13.1.0 "cc (Debian 13.1.0-9) 13.1.0") > C linker for the host machine: cc ld.bfd 2.40.90.20230720 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Compiler for C supports arguments -Werror=declaration-after-statement: YES > Compiler for C supports arguments -Werror=implicit-function-declaration: YES > Compiler for C supports link arguments > -Wl,--version-script,/<>/glib-networking.map: YES > Found pkg-config: /usr/bin/pkg-config (1.8.1) > Run-time dependency glib-2.0 found: YES 2.76.4 > Run-time dependency gio-2.0 found: YES 2.76.4 > Run-time dependency gobject-2.0 found: YES 2.76.4 > Run-time dependency gmodule-2.0 found: YES 2.76.4 > Run-time dependency libproxy-1.0 found: YES 0.4.18 > Run-time dependency gsettings-desktop-schemas found: YES 44.0 > Header "dlfcn.h" has symbol "RTLD_NOLOAD" : YES > Run-time dependency gnutls found: YES 3.7.9 > Configuring config.h using configuration > Program msgfmt found: YES (/usr/bin/msgfmt) > Program msginit found: YES (/usr/bin/msginit) > Program msgmerge found: YES (/usr/bin/msgmerge) > Program xgettext found: YES (/usr/bin/xgettext) > Configuring org.gtk.GLib.PACRunner.service using configuration > Configuring glib-pacrunner.service using configuration > Configuring environment-libproxy.test using configuration > Configuring gnome.test using configuration > Configuring certificate-gnutls.test using configuration > Checking for size of "time_t" : 8 > Configuring file-database-gnutls.test using configuration > Checking for size of "time_t" : 8 (cached) > Configuring connection-gnutls.test using configuration > Checking for size of "time_t" : 8 (cached) > Dependency gio-2.0 found: YES 2.76.4 (cached) > Program gio-querymodules found: YES > (/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules) > Build targets in project: 85 > > glib-networking 2.74.0 > > GnuTLS support : YES > OpenSSL support : NO > Environment proxy support: NO > libproxy support : YES > GNOME proxy support : YES > > User defined options > auto_features: enabled > buildtype: plain > libdir : lib/x86_64-linux-gnu > localstatedir: /var > prefix : /usr > sysconfdir : /etc > wrap_mode: nodownload > environment_proxy: disabled > installed_tests : true > > Found ninja-1.11.1 at /usr/bin/ninja > make[1]: Leaving directory '/<>' >dh_auto_build > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v > [1/108] /usr/bin/msgfmt -o po/ar/LC_MESSAGES/glib-networking.mo ../po/ar.po > [2/108] /usr/bin/msgfmt -o po/an/LC_MESSAGES/glib-networking.mo ../po/an.po > [3/108] /usr/bin/msgfmt -o po/ab/LC_MESSAGES/glib-networking.mo ../po/ab.po > [4/108] /usr/bin/msgfmt -o po/as/LC_MESSAGES/glib-networking.mo ../po/as.po > [5/108] /usr/bin/msgfmt -o po/bs/LC_MESSAGES/glib-networking.mo ../po/bs.po > [6/108] /usr/bin/msgfmt -o po/bg/LC_MESSAGES/glib-networking.mo ../po/bg.po > [7/108] /usr/bin/msgfmt -o po/be/LC_MESSAGES/glib-networking.mo ../po/be.po > [8/108]
Bug#1037854: marked as done (scipy: ftbfs with GCC-13)
Your message dated Fri, 28 Jul 2023 13:06:42 +0200
with message-id <8955eb054d1ce2651cdba19a86c59...@debian.org>
and subject line Re:Bug #1037854 scipy: ftbfs with GCC-13
has caused the Debian Bug report #1037854,
regarding scipy: ftbfs with GCC-13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1037854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:scipy
Version: 1.10.1-2
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/scipy_1.10.1-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html
[...]
| ^
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:312:1:
note: in expansion of macro ‘SCALAR_COMBINER’
312 | SCALAR_COMBINER(uint32_t)
| ^~~
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:304:31:
error: template argument 2 is invalid
304 | struct __combined {
\
| ^
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:312:1:
note: in expansion of macro ‘SCALAR_COMBINER’
312 | SCALAR_COMBINER(uint32_t)
| ^~~
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:314:17:
error: ‘uint64_t’ was not declared in this scope
314 | SCALAR_COMBINER(uint64_t)
| ^~~~
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:304:21:
note: in definition of macro ‘SCALAR_COMBINER’
304 | struct __combined {
\
| ^~~~
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:314:17:
note: ‘uint64_t’ is defined in header ‘’; did you forget to ‘#include
’?
314 | SCALAR_COMBINER(uint64_t)
| ^~~~
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:304:21:
note: in definition of macro ‘SCALAR_COMBINER’
304 | struct __combined {
\
| ^~~~
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:314:17:
error: ‘uint64_t’ was not declared in this scope
314 | SCALAR_COMBINER(uint64_t)
| ^~~~
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:304:27:
note: in definition of macro ‘SCALAR_COMBINER’
304 | struct __combined {
\
| ^~~~
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:314:17:
note: ‘uint64_t’ is defined in header ‘’; did you forget to ‘#include
’?
314 | SCALAR_COMBINER(uint64_t)
| ^~~~
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:304:27:
note: in definition of macro ‘SCALAR_COMBINER’
304 | struct __combined {
\
| ^~~~
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:304:31:
error: template argument 1 is invalid
304 | struct __combined {
\
| ^
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:314:1:
note: in expansion of macro ‘SCALAR_COMBINER’
314 |
Processed: close 1041476
Processing commands for cont...@bugs.debian.org: > close 1041476 254-1 Bug #1041476 [src:systemd] systemd: keep 254-rcX out of testing The source 'systemd' and version '254-1' do not appear to match any binary packages Marked as fixed in versions systemd/254-1. Bug #1041476 [src:systemd] systemd: keep 254-rcX out of testing Marked Bug as done > End of message, stopping processing here. Please contact me if you need assistance. -- 1041476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041476 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042157: marked as done (uranium: FTBFS: dh_install: error: missing files, aborting)
Your message dated Fri, 28 Jul 2023 10:45:11 + with message-id and subject line Bug#1042157: fixed in uranium 5.0.0-3 has caused the Debian Bug report #1042157, regarding uranium: FTBFS: dh_install: error: missing files, aborting 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.) -- 1042157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042157 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: uranium Version: 5.0.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' > make[2]: Nothing to be done for 'preinstall'. > make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' > Install the project... > /usr/bin/cmake -P cmake_install.cmake > -- Install configuration: "None" > -- Installing: /<>/debian/tmp/usr/share/uranium//resources > -- Installing: /<>/debian/tmp/usr/share/uranium//resources/i18n > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/cs_CZ > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/cs_CZ/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/cs_CZ/LC_MESSAGES/uranium.mo > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/nl_NL > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/nl_NL/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/nl_NL/LC_MESSAGES/uranium.mo > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/ru_RU > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/ru_RU/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/ru_RU/LC_MESSAGES/uranium.mo > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/ja_JP > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/ja_JP/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/ja_JP/LC_MESSAGES/uranium.mo > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/pt_PT > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/pt_PT/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/pt_PT/LC_MESSAGES/uranium.mo > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/zh_CN > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/zh_CN/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/zh_CN/LC_MESSAGES/uranium.mo > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/hu_HU > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/hu_HU/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/hu_HU/LC_MESSAGES/uranium.mo > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/tr_TR > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/tr_TR/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/tr_TR/LC_MESSAGES/uranium.mo > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/zh_TW > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/zh_TW/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/zh_TW/LC_MESSAGES/uranium.mo > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/fi_FI > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/fi_FI/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/fi_FI/LC_MESSAGES/uranium.mo > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/de_DE > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/de_DE/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/de_DE/LC_MESSAGES/uranium.mo > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/it_IT > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/it_IT/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/it_IT/LC_MESSAGES/uranium.mo > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/fr_FR > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/fr_FR/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/fr_FR/LC_MESSAGES/uranium.mo > -- Installing: > /<>/debian/tmp/usr/share/uranium//resources/i18n/es_ES > -- Installing: >
Bug#1042158: marked as done (rust-netlink-proto: FTBFS: build-dependency not installable: librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~))
Your message dated Fri, 28 Jul 2023 10:44:13 + with message-id and subject line Bug#1042158: fixed in rust-netlink-proto 0.11.2-1 has caused the Debian Bug report #1042158, regarding rust-netlink-proto: FTBFS: build-dependency not installable: librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-netlink-proto Version: 0.10.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, > libstd-rust-dev, librust-bytes-1+default-dev, > librust-futures-0.3+default-dev, librust-log-0.4+default-dev (>= 0.4.8-~~), > librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~), > librust-netlink-sys-0.8+tokio-socket-dev (>= 0.8.3-~~), > librust-netlink-sys-0.8-dev (>= 0.8.3-~~), librust-thiserror-1+default-dev > (>= 1.0.30-~~), librust-tokio-1+io-util-dev, build-essential, fakeroot > Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, > libstd-rust-dev, librust-bytes-1+default-dev, > librust-futures-0.3+default-dev, librust-log-0.4+default-dev (>= 0.4.8-~~), > librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~), > librust-netlink-sys-0.8+tokio-socket-dev (>= 0.8.3-~~), > librust-netlink-sys-0.8-dev (>= 0.8.3-~~), librust-thiserror-1+default-dev > (>= 1.0.30-~~), librust-tokio-1+io-util-dev, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [515 B] > Get:5 copy:/<>/apt_archive ./ Packages [591 B] > Fetched 2069 B in 0s (152 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: > librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~) but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/07/26/rust-netlink-proto_0.10.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: rust-netlink-proto Source-Version: 0.11.2-1 Done: Reinhard Tartler We believe that the bug you reported is fixed in the latest version of rust-netlink-proto, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the
Bug#1041385: marked as done (librust-netlink-proto-dev: impossible to install)
Your message dated Fri, 28 Jul 2023 10:44:13 + with message-id and subject line Bug#1041385: fixed in rust-netlink-proto 0.11.2-1 has caused the Debian Bug report #1041385, regarding librust-netlink-proto-dev: impossible to install 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.) -- 1041385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-netlink-proto-dev Version: 0.10.0-1+b1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Impossible to install: Depends on missing package librust-netlink-packet-core-0.4+default-dev -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmS2VpAACgkQLHwxRsGg ASGcNA/6AyKMVC6CDJmtvKJy/Cu48JPhuc0jQIyKFzm6eCju3bDYtejKYwxhOmKl pCOqoQPErQQj06B+zxTNlPY735WQtZxFiYUMh2okv7Im94u5NFhl53ipNaWkVjYH IyQt7P0yWSSLk3V4/dy3sgcdLAAZNA+TfIgQDtm3OETLgqMzB3kK1jnZdOTfFcvo V+VV/CZP8KfslZspomsBxyVmoDc6fGMmI4Hd047cniHcb4DvgzaLnH1i3n0oqfnc HFw+/M/Q2SruF68ULeGcfwgMLsKsNJZzhTFz1wWdAO078gcGR2zxGUort5ncWBmL Gg9EzfW1Gg2lAmlwenDBx/RH5CKu25iqkvRSsbTWGVcdnpLblfDQfhMXOa7+GeqY 38sSPco8CpXlR0TGcli5mVP6nTZN9ExHvc/ZkA8r5gegl7EU2w8fJ7jMjm1cEcyP CLozTr7wv3D7qdRVScx6XabgUpLiMACUNT7b05nrgOIDYtgr/HxAUpVYM6C+bzX5 I2Kyh53hAWiqRlvMfJTIdRCvmm4Yan721b8wrOxhS+tgpAlv5+sqg/m2E3nji6LS yqIA7GgFITQUoDFxyy2E13ncFZgPpAOtvevdV6vZSAa0assIgaK4wH7EeLOdLQ8Q l6jPYXQj1DZUS4pXBhMhUyf8Ww4tr31rLTJCLTLU4HWXI3ThcVo= =YB6S -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: rust-netlink-proto Source-Version: 0.11.2-1 Done: Reinhard Tartler We believe that the bug you reported is fixed in the latest version of rust-netlink-proto, 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 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Reinhard Tartler (supplier of updated rust-netlink-proto package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 28 Jul 2023 06:13:21 -0400 Source: rust-netlink-proto Architecture: source Version: 0.11.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Reinhard Tartler Closes: 1041385 1042158 Changes: rust-netlink-proto (0.11.2-1) unstable; urgency=medium . * Package netlink-proto 0.11.2 from crates.io using debcargo 2.6.0 * Fix build and package installation, closes: #1041385, #1042158 * avoid dependency on netlink-packet-audit and drop examples and benches from build Checksums-Sha1: cc2efbbb3fe366d0ff9832f4b5b295b383c05f3c 3145 rust-netlink-proto_0.11.2-1.dsc 94b5879c1baf971f9ddbb5d6e2bc4258b353b050 20802 rust-netlink-proto_0.11.2.orig.tar.gz 477d4f1b0eb683f17a6272e2fc469b128587d699 3696 rust-netlink-proto_0.11.2-1.debian.tar.xz 1cf3447d30dfcc66b14d1b12a03945b557607ed9 7854 rust-netlink-proto_0.11.2-1_source.buildinfo Checksums-Sha256: e2e474a7c6a0f27231dab2f0d29a98cc79ce95d59a1f445a41c6a311620e 3145 rust-netlink-proto_0.11.2-1.dsc bc321725b8c60732af780181cfa4249ff10c3ece56aee57465f7754ef030925f 20802 rust-netlink-proto_0.11.2.orig.tar.gz aca98c5156ae6c0ee779a37ade048086ad8553343e2514d9c391dca392ea7bc6 3696 rust-netlink-proto_0.11.2-1.debian.tar.xz c257cf35731c0e5b3a239074f60660561af829c7a8415fb4bf1bdfad7ac368e0 7854 rust-netlink-proto_0.11.2-1_source.buildinfo Files: c1c5fe2bf09a62b965e09318300e3f84 3145 rust optional rust-netlink-proto_0.11.2-1.dsc 92248dbb10b363072d1cc9010a2ad552 20802 rust optional rust-netlink-proto_0.11.2.orig.tar.gz 026ce2e85cb8af492b31ba2a9a8691c3 3696 rust optional rust-netlink-proto_0.11.2-1.debian.tar.xz 4f18e331c4969a510a7613046ff8a430 7854 rust optional rust-netlink-proto_0.11.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmTDlMUUHHNpcmV0YXJ0 QHRhdXdhcmUuZGUACgkQSadpd5QoJssdUg//dVkG7NYtbzFvK5Hud3jbXF/tQuxY 6QXhqWLvG3PohHlc1i1DCKZi5XP6p6Z1iGQUtdGw4DW8hT4aWrPfpt8DqtElKbmW iMIClkLly8ElhcEESznw+loY/63TrmD7Ik8LPdbdETNeNfeQuWkG9G1ybUEFxTe2 GFfNWNrvupkkY3JykwCOt5dHIRkDoDxnLUq3e3GuWpoIva0e/4WxO3HDWvWQ2Bmb /drl7IJw0WGlCvLyM5Yjf9GNB+InjX3B1xOeCI3gqQjB5LHMCJ4Rr7OId5VwL1dq
Processed: tagging 1042432
Processing commands for cont...@bugs.debian.org: > tags 1042432 + upstream Bug #1042432 [src:mat2] mat2: autopkgtest regression with ffmpeg 6.0 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1042432 is forwarded to https://0xacab.org/jvoisin/mat2/-/issues/193
Processing commands for cont...@bugs.debian.org: > forwarded 1042432 https://0xacab.org/jvoisin/mat2/-/issues/193 Bug #1042432 [src:mat2] mat2: autopkgtest regression with ffmpeg 6.0 Set Bug forwarded-to-address to 'https://0xacab.org/jvoisin/mat2/-/issues/193'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042157: [3dprinter-general] Bug#1042157: uranium: FTBFS: dh_install: error: missing files, aborting
Re: Timo Röhling > https://lists.debian.org/debian-devel/2023/07/msg00307.html Thanks for the explanation, I'm preparing an upload. Cheers, Christoph
Processed: Bug#1042157 marked as pending in uranium
Processing control commands: > tag -1 pending Bug #1042157 [src:uranium] uranium: FTBFS: dh_install: error: missing files, aborting Added tag(s) pending. -- 1042157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042157 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042157: marked as pending in uranium
Control: tag -1 pending Hello, Bug #1042157 in uranium 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/3dprinting-team/uranium/-/commit/e5d2fb259d40f65ac490f97ed05ce5673e049ef4 Set DEB_PYTHON_INSTALL_LAYOUT=deb_system, thanks Timo Röhling! (Closes: #1042157) (this message was generated automatically) -- Greetings https://bugs.debian.org/1042157
Bug#1041242: This also breaks imagemagick (imagemagick) and vipsthumbnail (libvips-tools)
I think this is also affecting imagemagick and vipsthumbnail. I do have all the libheif-plugin-* packages installed. I'm running testing and have libheif 1.16.2-2 installed. $ convert -debug IMG_3192.HEIC test.jpg convert-im6.q16: unrecognized event type `IMG_3192.HEIC' @ error/convert.c/ConvertImageCommand/1193. $ vipsthumbnail --size=256x256 ./IMG_3192.HEIC (vipsthumbnail:396906): VIPS-WARNING **: 11:43:28.704: error in tile 0 x 0 (vipsthumbnail:396906): VIPS-WARNING **: 11:43:28.704: error in tile 0 x 0 (vipsthumbnail:396906): VIPS-WARNING **: 11:43:28.704: error in tile 0 x 10 (vipsthumbnail:396906): VIPS-WARNING **: 11:43:28.705: error in tile 0 x 20 (vipsthumbnail:396906): VIPS-WARNING **: 11:43:28.705: error in tile 0 x 0 vipsthumbnail: unable to thumbnail ./IMG_3192.HEIC ./IMG_3192.HEIC: bad seek to 1446629 heif: Unsupported feature: Unsupported codec (4.3000)
Bug#1042274: marked as done (golang-github-tklauser-go-sysconf: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/tklauser/go-sysconf github.com/tklauser/go-sysconf/cgotest
Your message dated Fri, 28 Jul 2023 09:06:06 + with message-id and subject line Bug#1042274: fixed in golang-github-tklauser-go-sysconf 0.3.11-1 has caused the Debian Bug report #1042274, regarding golang-github-tklauser-go-sysconf: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/tklauser/go-sysconf github.com/tklauser/go-sysconf/cgotest returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042274 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-tklauser-go-sysconf Version: 0.3.9-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --builddirectory=_build --buildsystem=golang --with=golang >dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang >dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang >dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang >dh_auto_build -O--builddirectory=_build -O--buildsystem=golang > cd _build && go install -trimpath -v -p 8 > github.com/tklauser/go-sysconf github.com/tklauser/go-sysconf/cgotest > internal/goarch > internal/unsafeheader > internal/goos > internal/coverage/rtcov > internal/goexperiment > internal/cpu > runtime/internal/atomic > runtime/internal/syscall > internal/race > internal/abi > runtime/internal/math > runtime/internal/sys > sync/atomic > unicode > unicode/utf8 > math/bits > internal/itoa > encoding > internal/bytealg > math > runtime > internal/reflectlite > sync > internal/testlog > internal/godebug > internal/sysinfo > runtime/cgo > math/rand > errors > sort > io > internal/oserror > internal/safefilepath > path > strconv > syscall > bytes > strings > reflect > bufio > internal/syscall/execenv > time > internal/syscall/unix > context > io/fs > internal/poll > os > internal/fmtsort > encoding/binary > io/ioutil > path/filepath > fmt > golang.org/x/sys/unix > flag > runtime/trace > runtime/debug > testing > github.com/tklauser/numcpus > github.com/tklauser/go-sysconf > github.com/tklauser/go-sysconf/cgotest >dh_auto_test -O--builddirectory=_build -O--buildsystem=golang > cd _build && go test -vet=off -v -p 8 github.com/tklauser/go-sysconf > github.com/tklauser/go-sysconf/cgotest > === RUN TestGetNproc > --- PASS: TestGetNproc (0.00s) > === RUN TestSysconf > sysconf_test.go:27: clock ticks = 100 > --- PASS: TestSysconf (0.00s) > === RUN TestOpenMax > --- PASS: TestOpenMax (0.00s) > === RUN TestGetconf > sysconf_test.go:87: Sysconf(OPEN_MAX/4) returned 1048576, want 1024 > --- FAIL: TestGetconf (0.01s) > === RUN ExampleSysconf_invalidParameter > --- PASS: ExampleSysconf_invalidParameter (0.00s) > FAIL > FAIL github.com/tklauser/go-sysconf 0.010s > === RUN TestSysconfCgoMatch > sysconf_cgotest_linux.go:164: AIO_LISTIO_MAX = -1 > sysconf_cgotest_linux.go:164: AIO_MAX = -1 > sysconf_cgotest_linux.go:164: AIO_PRIO_DELTA_MAX = 20 > sysconf_cgotest_linux.go:164: ARG_MAX = 2097152 > sysconf_cgotest_linux.go:164: ATEXIT_MAX = 2147483647 > sysconf_cgotest_linux.go:164: BC_BASE_MAX = 99 > sysconf_cgotest_linux.go:164: BC_DIM_MAX = 2048 > sysconf_cgotest_linux.go:164: BC_SCALE_MAX = 99 > sysconf_cgotest_linux.go:164: BC_STRING_MAX = 1000 > sysconf_cgotest_linux.go:164: CHILD_MAX = 126959 > sysconf_cgotest_linux.go:164: CLK_TCK = 100 > sysconf_cgotest_linux.go:164: COLL_WEIGHTS_MAX = 255 > sysconf_cgotest_linux.go:164: DELAYTIMER_MAX = 2147483647 > sysconf_cgotest_linux.go:164: EXPR_NEST_MAX = 32 > sysconf_cgotest_linux.go:164: GETGR_R_SIZE_MAX = 1024 > sysconf_cgotest_linux.go:164: GETPW_R_SIZE_MAX = 1024 > sysconf_cgotest_linux.go:164: HOST_NAME_MAX = 64 > sysconf_cgotest_linux.go:164: IOV_MAX = 1024 > sysconf_cgotest_linux.go:164: LINE_MAX = 2048 > sysconf_cgotest_linux.go:164: LOGIN_NAME_MAX = 256 > sysconf_cgotest_linux.go:164: MQ_OPEN_MAX = -1 > sysconf_cgotest_linux.go:164: MQ_PRIO_MAX = 32768 > sysconf_cgotest_linux.go:164: NGROUPS_MAX = 65536 > sysconf_cgotest_linux.go:164: OPEN_MAX = 1048576 > sysconf_cgotest_linux.go:164: PAGE_SIZE = 4096 > sysconf_cgotest_linux.go:164: PAGESIZE = 4096 > sysconf_cgotest_linux.go:164: PTHREAD_DESTRUCTOR_ITERATIONS = 4 >
Bug#1038422: ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]
Hi Richard,
I'm sorry for my tardy response. I just returned from holiday.
On 2023-07-23 05:11, Richard Laager wrote:
> Some questions from upstream, with my commentary added...
>
>> How busy is this sustem? Is it just a simple client or also a server? If
>> server, how busy?
This is a server and participates in the NTP Pool project, so the NTPsec
process is fairly busy. From the logs the server is handling about 1.5
to 1.7 million NTP requests per hour.
>>
>> From the stack trace, the server side is trying to decode a NTS cookie. Is
>> this box setup as a NTS server? That needs a certificate and key so it takes
>> more than just upgrading from bullseye to bookworm.
>
> It's not, right? We previously established that this is using the stock
> ntp.conf?
>
No, it is not configured as an NTS server.
>> What are the chances that a valid NTP request with NTS arrived at this
>> system? ntpq -c ntsinfo will show counters.
>
I'd say the chances are fairly high that an invalid NTP request with NTS
has arrived. But the counters are all zero.
cyclone@karita:~$ ntpq -c ntsinfo
NTS client sends: 0
NTS client recvs good: 0
NTS client recvs w error: 0
NTS server recvs good: 0
NTS server recvs w error: 0
NTS server sends: 0
NTS make cookies: 0
NTS decode cookies: 0
NTS decode cookies old: 0
NTS decode cookies old2:0
NTS decode cookies older: 0
NTS decode cookies too old: 0
NTS decode cookies error: 0
NTS KE client probes good: 0
NTS KE client probes bad: 0
NTS KE serves good: 0
NTS KE serves bad: 0
cyclone@karita:~$
> It would be good if you could check this. But if an NTS request is crashing
> ntpd, you might never see non-zero counters.
>
>> The log file from starting up might be helpful.
Here's the syslog entries from the most recent restart. I took the
liberty of scrubbing the high portions of the IP addresses.
2023-07-28T06:58:39.890236+00:00 karita ntpd[30320]: INIT: ntpd
ntpsec-1.2.2: Starting
2023-07-28T06:58:39.891073+00:00 karita ntpd[30320]: INIT: Command line:
/usr/sbin/ntpd -p /run/ntpd.pid -c /etc/ntpsec/ntp.conf -g -N -u
ntpsec:ntpsec
2023-07-28T06:58:39.891132+00:00 karita ntp-systemd-wrapper[30320]:
2023-07-28T06:58:39 ntpd[30320]: INIT: ntpd ntpsec-1.2.2: Starting
2023-07-28T06:58:39.892382+00:00 karita ntp-systemd-wrapper[30320]:
2023-07-28T06:58:39 ntpd[30320]: INIT: Command line: /usr/sbin/ntpd -p
/run/ntpd.pid -c /etc/ntpsec/ntp.conf -g -N -u ntpsec:ntpsec
2023-07-28T06:58:39.892502+00:00 karita systemd[1]: Started
ntpsec.service - Network Time Service.
2023-07-28T06:58:39.894804+00:00 karita ntpd[30322]: INIT: precision =
0.060 usec (-24)
2023-07-28T06:58:39.895396+00:00 karita ntpd[30322]: INIT: successfully
locked into RAM
2023-07-28T06:58:39.899405+00:00 karita ntpd[30322]: CONFIG: readconfig:
parsing file: /etc/ntpsec/ntp.conf
2023-07-28T06:58:39.899544+00:00 karita ntpd[30322]: CONFIG: restrict
nopeer ignored
2023-07-28T06:58:39.900054+00:00 karita ntpd[30322]: CLOCK: leapsecond
file ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature
2023-07-28T06:58:39.900121+00:00 karita ntpd[30322]: CLOCK: leapsecond
file ('/usr/share/zoneinfo/leap-seconds.list'): loaded,
expire=2023-12-28T00:00Z last=2017-01-01T00:00Z ofs=37
2023-07-28T06:58:39.900198+00:00 karita ntpd[30322]: INIT: Using
SO_TIMESTAMPNS(ns)
2023-07-28T06:58:39.900262+00:00 karita ntpd[30322]: IO: Listen and drop
on 0 v6wildcard [::]:123
2023-07-28T06:58:39.900367+00:00 karita ntpd[30322]: IO: Listen and drop
on 1 v4wildcard 0.0.0.0:123
2023-07-28T06:58:39.900518+00:00 karita ntpd[30322]: IO: Listen normally
on 2 lo 127.0.0.1:123
2023-07-28T06:58:39.900589+00:00 karita ntpd[30322]: IO: Listen normally
on 3 eth0 xxx.yyy.zzz.201:123
2023-07-28T06:58:39.900662+00:00 karita ntpd[30322]: IO: Listen normally
on 4 lo [::1]:123
2023-07-28T06:58:39.900913+00:00 karita ntpd[30322]: IO: Listen normally
on 5 eth0 [::::5ce7]:123
2023-07-28T06:58:39.901000+00:00 karita ntpd[30322]: IO: Listen normally
on 6 eth0 [fe80:::::dfe%2]:123
2023-07-28T06:58:39.901065+00:00 karita ntpd[30322]: IO: Listening on
routing socket on fd #23 for interface updates
2023-07-28T06:58:39.912520+00:00 karita ntpd[30322]: INIT: MRU 10922
entries, 13 hash bits, 65536 bytes
2023-07-28T06:58:39.912607+00:00 karita ntpd[30322]: INIT: Built with
OpenSSL 3.0.7 1 Nov 2022, 3070
2023-07-28T06:58:39.912652+00:00 karita ntpd[30322]: INIT: Running with
OpenSSL 3.0.9 30 May 2023, 3090
2023-07-28T06:58:39.912976+00:00 karita ntpd[30322]: NTSc: Using system
default root certificates.
2023-07-28T06:58:42.938515+00:00 karita ntpd[30322]: DNS: dns_probe:
0.debian.pool.ntp.org, cast_flags:8, flags:101
2023-07-28T06:58:42.957881+00:00 karita
Bug#1042274: marked as pending in golang-github-tklauser-go-sysconf
Control: tag -1 pending Hello, Bug #1042274 in golang-github-tklauser-go-sysconf reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/golang-github-tklauser-go-sysconf/-/commit/f8ccc6ce218d8af6fabf9ea26b57c56dee03acbd Skip test OPEN_MAX with getconf (Closes: #1042274) (this message was generated automatically) -- Greetings https://bugs.debian.org/1042274
Processed: Bug#1042274 marked as pending in golang-github-tklauser-go-sysconf
Processing control commands: > tag -1 pending Bug #1042274 [src:golang-github-tklauser-go-sysconf] golang-github-tklauser-go-sysconf: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/tklauser/go-sysconf github.com/tklauser/go-sysconf/cgotest returned exit code 1 Added tag(s) pending. -- 1042274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042274 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042431: marked as done (libmedia-convert-perl: autopkgtest fails)
Your message dated Fri, 28 Jul 2023 08:42:29 + with message-id and subject line Bug#1042431: fixed in libmedia-convert-perl 1.0.5-2 has caused the Debian Bug report #1042431, regarding libmedia-convert-perl: autopkgtest fails 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.) -- 1042431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libmedia-convert-perl Version: 1.0.4-3 Severity: serious Tags: sid trixie X-Debbugs-Cc: sramac...@debian.org libmedia-convert-perl's autopkgtest fail with ffmpeg 6.0: https://ci.debian.net/data/autopkgtest/testing/amd64/libm/libmedia-convert-perl/36194915/log.gz 166s Test Summary Report 166s --- 166s t/avsync.t (Wstat: 256 (exited 1) Tests: 15 Failed: 1) 166s Failed test: 15 166s Non-zero exit status: 1 166s t/probe.t(Wstat: 256 (exited 1) Tests: 11 Failed: 1) 166s Failed test: 3 166s Non-zero exit status: 1 166s Files=11, Tests=126, 92 wallclock secs ( 0.04 usr 0.02 sys + 90.55 cusr 2.94 csys = 93.55 CPU) 166s Result: FAIL Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: libmedia-convert-perl Source-Version: 1.0.5-2 Done: Wouter Verhelst We believe that the bug you reported is fixed in the latest version of libmedia-convert-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Wouter Verhelst (supplier of updated libmedia-convert-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA384 Format: 1.8 Date: Thu, 27 Jul 2023 09:29:39 +0200 Source: libmedia-convert-perl Architecture: source Version: 1.0.5-2 Distribution: unstable Urgency: medium Maintainer: Wouter Verhelst Changed-By: Wouter Verhelst Closes: 1042431 Changes: libmedia-convert-perl (1.0.5-2) unstable; urgency=medium . * debian/control: add missing libsemver-perl dependency. Closes: #1042431. * Media::Convert::Asset: revert accidental removal of audio_channel_count * Media::Convert::Asset::av1: sync docs with reality Checksums-Sha1: 124682cf82f4bfdc97091002e4e8d3d8e3e39325 1520 libmedia-convert-perl_1.0.5-2.dsc 68e0f0333bbfc141eaf4451b9202175b3137851e 19376 libmedia-convert-perl_1.0.5-2.debian.tar.xz 15be2b2fca35fc4c52a824c30719a0cba709337f 13049 libmedia-convert-perl_1.0.5-2_source.buildinfo Checksums-Sha256: 82f101d93b3da9a06cec8f4f0d44aeac39c4ab3a838e0a5d78cb84acb0f741a2 1520 libmedia-convert-perl_1.0.5-2.dsc 3b17ee6715e8956e07f360b1d328e8558dbb631e316d9a94e4faf517b1549d24 19376 libmedia-convert-perl_1.0.5-2.debian.tar.xz 5c6f1e1e6d094844027b4b88f7d77e99183f732d011f267d8fe3c0e10df14fe4 13049 libmedia-convert-perl_1.0.5-2_source.buildinfo Files: 5a6de6b58ebb7308627f09143a297f99 1520 perl optional libmedia-convert-perl_1.0.5-2.dsc e198a4509d59bc4a96ca09f15e5d4227 19376 perl optional libmedia-convert-perl_1.0.5-2.debian.tar.xz ccdef09be85dd7b1f95902ab705d938b 13049 perl optional libmedia-convert-perl_1.0.5-2_source.buildinfo -BEGIN PGP SIGNATURE- iKgEARMJADAWIQQZhIYJILYM7Y0TCTdH038p5i64/wUCZMN1tBIcd291dGVyQGRl Ymlhbi5vcmcACgkQR9N/KeYuuP/Z+QF/bUsOhSJyf+fDrkBOEpfgZwKvD4QkZuzr Eoqi0y8vpu+DwsBA3kgrB2M1OWzCECQ0AYDz3B86kR3kbGe3D8vIZV3x3rrKvNCE PyAweSr1OLDD1bfls3xIjo38pPWbJIRCfCA= =r+Ro -END PGP SIGNATURE End Message ---
Bug#1042424: marked as done (src:ola: fails to migrate to testing for too long: uploader built arch:all binaries)
Your message dated Fri, 28 Jul 2023 08:42:45 + with message-id and subject line Bug#1042424: fixed in ola 0.10.9.nojsmin-4 has caused the Debian Bug report #1042424, regarding src:ola: fails to migrate to testing for too long: uploader built arch:all binaries 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.) -- 1042424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ola Version: 0.10.9.nojsmin-2 Severity: serious Control: close -1 0.10.9.nojsmin-3 Tags: sid trixie pending 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:ola has been trying to migrate for 32 days [2]. Hence, I am filing this 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. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=ola OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: ola Source-Version: 0.10.9.nojsmin-4 Done: Wouter Verhelst We believe that the bug you reported is fixed in the latest version of ola, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Wouter Verhelst (supplier of updated ola 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: SHA384 Format: 1.8 Date: Fri, 28 Jul 2023 09:48:08 +0200 Source: ola Architecture: source Version: 0.10.9.nojsmin-4 Distribution: unstable Urgency: medium Maintainer: Wouter Verhelst Changed-By: Wouter Verhelst Closes: 1042424 Changes: ola (0.10.9.nojsmin-4) unstable; urgency=medium . * no-change upload to get everything built on the buildd hosts after last month's NEW upload. Closes: #1042424. Checksums-Sha1: 90631734daee5d031220a34e3b0f0f438885def8 1946 ola_0.10.9.nojsmin-4.dsc f37d662149a730a4c852eba28d08c51cc98ae2b3 35536 ola_0.10.9.nojsmin-4.debian.tar.xz 51fc1ba8098a86244d1ecbcb4b58381167891311 8214 ola_0.10.9.nojsmin-4_source.buildinfo Checksums-Sha256: 4b36a3fb2bbbc98af5ab87eb117f8e0fc7227631aeb425e175db0388383ff16b 1946 ola_0.10.9.nojsmin-4.dsc 7b37a8109832f27915beeb728c809a0a8f95a78d4ecf7f4a21effa10dc5143b2 35536 ola_0.10.9.nojsmin-4.debian.tar.xz 517fd1924cbf9bc457bcd9f0d28fefd9983551c895da61ac52cacd49b7c0961e 8214 ola_0.10.9.nojsmin-4_source.buildinfo Files: 361789da7897618f27566f0da11f056a 1946 libs optional ola_0.10.9.nojsmin-4.dsc c24fd90902bc6b69d5ca531103431a69 35536 libs optional ola_0.10.9.nojsmin-4.debian.tar.xz 832af6af4b39a364557ffd2b0ff770c4 8214 libs optional ola_0.10.9.nojsmin-4_source.buildinfo -BEGIN PGP SIGNATURE- iKgEARMJADAWIQQZhIYJILYM7Y0TCTdH038p5i64/wUCZMNz8BIcd291dGVyQGRl
Bug#1042157: [3dprinter-general] Bug#1042157: uranium: FTBFS: dh_install: error: missing files, aborting
Hi Christoph, * Christoph Berg [2023-07-28 10:26]: did cmake intentionally change Python_SITELIB to point to /usr/local? No, that is a side effect of migrating from the deprecated distutils.sysconfig module to the sysconfig module. From the Python side, the behavior is actually desirable, though. I posted an explanation on debian-devel yesterday: https://lists.debian.org/debian-devel/2023/07/msg00307.html Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Bug#1042255: p11-kit: libsoup3 fails to build from source
Control: reassign -1 src:p11-kit 0.25.0-3 Control: affects -1 src:libsoup3 Control: tags -1 +patch I have submitted a merge proposal to the p11-kit packaging with the patch to fix this issue. https://salsa.debian.org/gnutls-team/p11-kit/-/merge_requests/6 Thank you, Jeremy Bícha
Processed: Re: Bug#1042255: p11-kit: libsoup3 fails to build from source
Processing control commands: > reassign -1 src:p11-kit 0.25.0-3 Bug #1042255 [src:libsoup3] libsoup3: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 5 returned exit code 1 Bug reassigned from package 'src:libsoup3' to 'src:p11-kit'. No longer marked as found in versions libsoup3/3.2.2-2. Ignoring request to alter fixed versions of bug #1042255 to the same values previously set Bug #1042255 [src:p11-kit] libsoup3: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 5 returned exit code 1 Marked as found in versions p11-kit/0.25.0-3. > affects -1 src:libsoup3 Bug #1042255 [src:p11-kit] libsoup3: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 5 returned exit code 1 Added indication that 1042255 affects src:libsoup3 > tags -1 +patch Bug #1042255 [src:p11-kit] libsoup3: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 5 returned exit code 1 Added tag(s) patch. -- 1042255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042157: [3dprinter-general] Bug#1042157: uranium: FTBFS: dh_install: error: missing files, aborting
Hi Timo,
did cmake intentionally change Python_SITELIB to point to /usr/local?
Re: Gregor Riepl
> > purelib: directory for site-specific, non-platform-specific files
> > (https://docs.python.org/3/library/sysconfig.html)
> >
> > "site-specific" doesn't sound like packages should install anything
> > there.
>
> "site-specific" may be meant from the perspective of the Python interpreter,
> not the whole system, so it does sound correct to me - especially if you
> consider that Python modules are separated into the standard library and
> dist-packages.
>
> > Perhaps the bug is that Python_SITELIB is used and it should be
> > something else?
>
> I've tried Python_STDLIB (=sysconfig.get_path('stdlib')), but that's
> definitely wrong: It points to /usr/lib/python3.11
>
> Python packages are normally installed into /usr/lib/python3/dist-packages/
> (or /usr/lib/python3.11/dist-packages/ if they're interpreter-specific).
> Uranium used to be installed into /usr/lib/python3/dist-packages/, because
> it's a pure Python library and doesn't depend on the interpreter version.
>
> Python_STDARCH and Python_SITEARCH have the same values as Python_STDLIB and
> Python_SITELIB, and I don't see any other useful FindPython[1] variables.
> IMHO, Python_SITELIB is still the best choice, unless there's some other way
> to install Python modules in cmake that doesn't involve these variables.
>
> I'm going to ask the debian-python list for help, perhaps they know more
> about the correct paths to use.
> In the meantime, I do think this issue should block cmake 3.27 migration
> until we've sorted it out, so the bug should be reassigned to cmake.
>
>
> [1] https://cmake.org/cmake/help/latest/module/FindPython.html
>
Christoph
Bug#1042434: libcerf: base line violatin: builds with -march=native
Source: libcerf Version: 2.3-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org Building with -march=native means that whatever instruction set extensions are available on the buildd, are enabled. For example, if the build is performed on any resonably new enough buildd, SSE2 will be enabled on the i386 builds. Users of i386 without this instruction set will be unable to use libcerf. https://buildd.debian.org/status/fetch.php?pkg=libcerf=i386=2.3-1=1690485692=0 [ 1%] Building C object lib/CMakeFiles/cerf.dir/erfcx.c.o cd /<>/obj-i686-linux-gnu/lib && /usr/bin/cc -Dcerf_EXPORTS -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -std=gnu99 -fPIC -pedantic -Wall -Wno-sign-compare -fno-omit-frame-pointer -march=native -O3 -MD -MT lib/CMakeFiles/cerf.dir/erfcx.c.o -MF CMakeFiles/cerf.dir/erfcx.c.o.d -o CMakeFiles/cerf.dir/erfcx.c.o -c /<>/lib/erfcx.c Cheers -- Sebastian Ramacher
Bug#1042433: libcerf: FTBFS on mipsel
Source: libcerf Version: 2.3-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=libcerf=mipsel=2.3-1=1690485564=0 cd /<>/obj-mipsel-linux-gnu/lib && /usr/bin/cc -Dcerf_EXPORTS -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -std=gnu99 -fPIC -pedantic -Wall -Wno-sign-compare -fno-omit-frame-pointer -march=native -O3 -MD -MT lib/CMakeFiles/cerf.dir/err_fcts.c.o -MF CMakeFiles/cerf.dir/err_fcts.c.o.d -o CMakeFiles/cerf.dir/err_fcts.c.o -c /<>/lib/err_fcts.c cc1: error: ‘-march=mips1’ requires ‘-mfp32’ cc1: error: ‘-march=mips1’ requires ‘-mfp32’ When starting uncoordinated transitions, please ensure first (by uploading to experimental) that builds do not regress. Cheers -- Sebastian Ramacher
Bug#1042424: src:ola: fails to migrate to testing for too long: uploader built arch:all binaries
Hi Paul,
On Fri, Jul 28, 2023 at 08:18:56AM +0200, Paul Gevers wrote:
> Your package is only blocked because the arch:all binary package(s) aren't
> built on a buildd. Unfortunately the Debian infrastructure doesn't allow
> arch:all packages to be properly binNMU'ed. Hence, I will shortly do a
> no-changes source-only upload to DELAYED/15, closing this bug. Please let me
> know if I should delay or cancel that upload.
Thanks. I forgot about this one, and yes, a no-changes source-only
upload was still required. The delay is unnecessary; I've just uploaded
-4 which is essentially the same, directly to the upload queue.
Thanks for nudging me.
--
w@uter.{be,co.za}
wouter@{grep.be,fosdem.org,debian.org}
I will have a Tin-Actinium-Potassium mixture, thanks.
Processed: Re: Bug#1042431: libmedia-convert-perl: autopkgtest regression with ffmpeg 6.0
Processing control commands: > retitle -1 libmedia-convert-perl: autopkgtest fails Bug #1042431 [src:libmedia-convert-perl] libmedia-convert-perl: autopkgtest regression with ffmpeg 6.0 Changed Bug title to 'libmedia-convert-perl: autopkgtest fails' from 'libmedia-convert-perl: autopkgtest regression with ffmpeg 6.0'. -- 1042431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1042431: libmedia-convert-perl: autopkgtest regression with ffmpeg 6.0
Processing control commands: > retitle -1 libmedia-convert-perl: autopkgtest fails Bug #1042431 [src:libmedia-convert-perl] libmedia-convert-perl: autopkgtest fails Ignoring request to change the title of bug#1042431 to the same title -- 1042431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042431: libmedia-convert-perl: autopkgtest regression with ffmpeg 6.0
Control: retitle -1 libmedia-convert-perl: autopkgtest fails
On Fri, Jul 28, 2023 at 09:51:06AM +0200, Sebastian Ramacher wrote:
> Source: libmedia-convert-perl
> Version: 1.0.4-3
> Severity: serious
> Tags: sid trixie
> X-Debbugs-Cc: sramac...@debian.org
>
> libmedia-convert-perl's autopkgtest fail with ffmpeg 6.0:
Actually, it just fails ;-) I've got a fix upcoming.
--
w@uter.{be,co.za}
wouter@{grep.be,fosdem.org,debian.org}
I will have a Tin-Actinium-Potassium mixture, thanks.
Bug#1042432: mat2: autopkgtest regression with ffmpeg 6.0
Source: mat2
Version: 0.13.3-1
Severity: serious
Tag: sid trixie
X-Debbugs-Cc: sramac...@debian.org
mat2's autopkgtests fail with ffmpeg 6.0:
https://ci.debian.net/data/autopkgtest/testing/amd64/m/mat2/36194920/log.gz
126s === FAILURES
===
126s ___ TestCleaning.test_all_parametred
___
126s
126s self =
126s
126s def test_all_parametred(self):
126s for case in self.data:
126s with self.subTest(case=case):
126s if 'ffmpeg' in case:
126s try:
126s video._get_ffmpeg_path()
126s except RuntimeError:
126s raise unittest.SkipTest
126s
126s print('[+] Testing %s' % case['name'])
126s target = './tests/data/clean.' + case['name']
126s shutil.copy('./tests/data/dirty.' + case['name'], target)
126s p1 = case['parser'](target)
126s
126s for k, v in p1.get_meta().items():
126s if k not in case['meta']:
126s continue
126s if isinstance(v, dict):
126s for _k, _v in v.items():
126s if _k in case['meta'][k]:
126s self.assertEqual(_v, case['meta'][k][_k])
126s else:
126s self.assertEqual(v, case['meta'][k])
126s
126s p1.lightweight_cleaning = True
126s self.assertTrue(p1.remove_all())
126s
126s p2 = case['parser'](p1.output_filename)
126s meta = p2.get_meta()
126s if meta:
126s for k, v in p2.get_meta().items():
126s > self.assertIn(k, case['expected_meta'], '"%s" is
not in "%s" (%s)' % (k, case['expected_meta'], case['name']))
126s E AssertionError: 'CompressorName' not found in
{'AverageBitrate': 465641, 'BufferSize': 0, 'CompatibleBrands': ['isom',
'iso2', 'avc1', 'mp41'], 'ColorProfiles': 'nclx', 'ColorPrimaries': 'BT.709',
'ColorRepresentation': 'nclx 1 1 1', 'CompressorID': 'avc1', 'GraphicsMode':
'srcCopy', 'HandlerDescription': 'SoundHandler', 'HandlerType': 'Metadata',
'HandlerVendorID': 'Apple', 'MajorBrand': 'Base Media v1 [IS0 14496-12:2003]',
'MatrixCoefficients': 'BT.709', 'MaxBitrate': 465641, 'MediaDataOffset': 48,
'MediaDataSize': 379872, 'MediaHeaderVersion': 0, 'MinorVersion': '0.2.0',
'MovieDataOffset': 48, 'MovieHeaderVersion': 0, 'NextTrackID': 3,
'PreferredRate': 1, 'Rotation': 0, 'TimeScale': 1000, 'TrackHeaderVersion': 0,
'TrackID': 1, 'TrackLayer': 0, 'TransferCharacteristics': 'BT.709'} :
"CompressorName" is not in "{'AverageBitrate': 465641, 'BufferSize': 0,
'CompatibleBrands': ['isom', 'iso2', 'avc1', 'mp41'], 'ColorProfiles': 'nclx',
'ColorPrimaries': 'BT.709', 'ColorRepresentation': 'nclx 1 1 1',
'CompressorID': 'avc1', 'GraphicsMode': 'srcCopy', 'HandlerDescription':
'SoundHandler', 'HandlerType': 'Metadata', 'HandlerVendorID': 'Apple',
'MajorBrand': 'Base Media v1 [IS0 14496-12:2003]', 'MatrixCoefficients':
'BT.709', 'MaxBitrate': 465641, 'MediaDataOffset': 48, 'MediaDataSize': 379872,
'MediaHeaderVersion': 0, 'MinorVersion': '0.2.0', 'MovieDataOffset': 48,
'MovieHeaderVersion': 0, 'NextTrackID': 3, 'PreferredRate': 1, 'Rotation': 0,
'TimeScale': 1000, 'TrackHeaderVersion': 0, 'TrackID': 1, 'TrackLayer': 0,
'TransferCharacteristics': 'BT.709'}" (mp4)
126s
126s tests/test_libmat2.py:557: AssertionError
Cheers
--
Sebastian Ramacher
Bug#1042431: libmedia-convert-perl: autopkgtest regression with ffmpeg 6.0
Source: libmedia-convert-perl Version: 1.0.4-3 Severity: serious Tags: sid trixie X-Debbugs-Cc: sramac...@debian.org libmedia-convert-perl's autopkgtest fail with ffmpeg 6.0: https://ci.debian.net/data/autopkgtest/testing/amd64/libm/libmedia-convert-perl/36194915/log.gz 166s Test Summary Report 166s --- 166s t/avsync.t (Wstat: 256 (exited 1) Tests: 15 Failed: 1) 166s Failed test: 15 166s Non-zero exit status: 1 166s t/probe.t(Wstat: 256 (exited 1) Tests: 11 Failed: 1) 166s Failed test: 3 166s Non-zero exit status: 1 166s Files=11, Tests=126, 92 wallclock secs ( 0.04 usr 0.02 sys + 90.55 cusr 2.94 csys = 93.55 CPU) 166s Result: FAIL Cheers -- Sebastian Ramacher
Bug#1042419: rust-ureq - update for new cookie-store
Control: block -1 by 1042427 Quoting Peter Green (2023-07-28 05:20:53) > I just updated rust-cookie-store. Ureq needs it's debian > dependencies adjusting to account for this (the cargo > dependencies already allow the new version. Thanks for the update, and the notice. Your package update is however blocked by bug#1042427 :-( - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Processed: Re: Bug#1042419: rust-ureq - update for new cookie-store
Processing control commands: > block -1 by 1042427 Bug #1042419 [rust-ureq] rust-ureq - update for new cookie-store 1042419 was not blocked by any bugs. 1042419 was not blocking any bugs. Added blocking bug(s) of 1042419: 1042427 -- 1042419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042157: [3dprinter-general] Bug#1042157: uranium: FTBFS: dh_install: error: missing files, aborting
purelib: directory for site-specific, non-platform-specific files
(https://docs.python.org/3/library/sysconfig.html)
"site-specific" doesn't sound like packages should install anything
there.
"site-specific" may be meant from the perspective of the Python
interpreter, not the whole system, so it does sound correct to me -
especially if you consider that Python modules are separated into the
standard library and dist-packages.
> Perhaps the bug is that Python_SITELIB is used and it should be
> something else?
I've tried Python_STDLIB (=sysconfig.get_path('stdlib')), but that's
definitely wrong: It points to /usr/lib/python3.11
Python packages are normally installed into
/usr/lib/python3/dist-packages/ (or /usr/lib/python3.11/dist-packages/
if they're interpreter-specific). Uranium used to be installed into
/usr/lib/python3/dist-packages/, because it's a pure Python library and
doesn't depend on the interpreter version.
Python_STDARCH and Python_SITEARCH have the same values as Python_STDLIB
and Python_SITELIB, and I don't see any other useful FindPython[1]
variables.
IMHO, Python_SITELIB is still the best choice, unless there's some other
way to install Python modules in cmake that doesn't involve these variables.
I'm going to ask the debian-python list for help, perhaps they know more
about the correct paths to use.
In the meantime, I do think this issue should block cmake 3.27 migration
until we've sorted it out, so the bug should be reassigned to cmake.
[1] https://cmake.org/cmake/help/latest/module/FindPython.html
Bug#1042427: librust-sha2-dev: impossible to install
Package: librust-sha2-dev Version: 0.10.7-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Depends on librust-digest-0.10+oid-dev which is unavailable. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTDZlYACgkQLHwxRsGg ASHr6g/+Iam1nLCjSspAqzN7EPY9XdRv05YR4aSPKGM/qKCxC1Ca9KeR/MUOTOe8 sMiAy/TbsIRiJ+PHRWdYgL9b9HcXkqly5SDauREjjSk15CyYTDUK392asQj/FfID 7YIzC9zbQaIPNreY325XCjakotesb4Oa+WMva2X4Eh2V+xC+dMV2FhzKBMTqGqAP Ua9z4bygdKd96MnGpMfWCAVRv7nE+7MEXImju0n5AalRQ/pj3YGu0Qi9nv5KDwBj bqcfixUXM9H//ledT0RELLEdAd3TGx/tnUG+wf8evQRA8cV7qc+SvnSi3KBM1Nm/ 6EGiw82kGEmrYGn/2oKL0YaqNHVfF0EBDS7t3yDvSf493pwzvLg8b/6KWRgpdY8J 6899uVei8EQW1Glg/aLliq0CpP0L6IpNDERM6Te+OIIhihkKOjv8JTWHX0z7Q8Kj upBBFx8iFUqTdQeilbJPpwup7CgPyQRCwysvSqjeF+6oU/AsQ35Nq+9MzaWVWNet lgTbMZQ7xp3nDHLJPIN68FGSK6XhLGHZk32Hx6Xj4ojaKq3I+1Ctp/455CgXWCwT o9FII/8wcKi+aZpTbwa9O/+wBenYrVfkJIESX11QF2ylaBw+vQUCnQ1ZIfOZBORz UqHZTJbF6Nw72/Z33B0EBty+VzFD/TMBRiLgpTelUyj6gQ7b/VA= =G1HN -END PGP SIGNATURE-
Processed: Re: Bug#1034443: fixed in brial 1.2.11-2.1
Processing control commands:
> fixed -1 1.2.11-2
Bug #1034443 {Done: Peter Michael Green } [python3-brial]
python3-brial: uninstallable on arcitectures where sagemath is unavailable,
breaks building of singular
Marked as fixed in versions brial/1.2.11-2.
--
1034443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034443
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: src:r-cran-sp: fails to migrate to testing for too long: triggers autopkgtest regression
Processing control commands: > close -1 1:2.0-0+dfsg-1 Bug #1042426 [src:r-cran-sp] src:r-cran-sp: fails to migrate to testing for too long: triggers autopkgtest regression Marked as fixed in versions r-cran-sp/1:2.0-0+dfsg-1. Bug #1042426 [src:r-cran-sp] src:r-cran-sp: fails to migrate to testing for too long: triggers autopkgtest regression Marked Bug as done -- 1042426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034443: fixed in brial 1.2.11-2.1
Control: fixed -1 1.2.11-2 Hi, On Tue, 09 May 2023 14:33:51 + Debian FTP Masters wrote: brial (1.2.11-2.1) unstable; urgency=medium . * Non-Maintainer upload. * Limit architectures for python3-brial package to architectures where sagemath is available (Closes: #1034443). It seems this change was taken over by the consecutive Maintainer upload, but the changelog entry was not. The BTS reads the changelog to conclude which versions are affected by a certain bug and hence concluded that the version in unstable was affected again. Teaching the BTS that the version in unstable is fine to enable migration of brial to testing. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1042426: src:r-cran-sp: fails to migrate to testing for too long: triggers autopkgtest regression
Source: r-cran-sp Version: 1:1.6-0+dfsg-1 Severity: serious Control: close -1 1:2.0-0+dfsg-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:r-cran-sp has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable triggers an autopkgtest failure in r-cran-rgdal. 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=r-cran-sp OpenPGP_signature Description: OpenPGP digital signature
