Bug#1067872: marked as done (transition: netcdf)
Your message dated Mon, 1 Apr 2024 06:23:29 +0200 with message-id and subject line Re: Bug#1067872: transition: netcdf has caused the Debian Bug report #1067872, regarding transition: netcdf 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.) -- 1067872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal X-Debbugs-Cc: net...@packages.debian.org Control: affects -1 + src:netcdf User: release.debian@packages.debian.org Usertags: transition There is no auto-netcdf tracker because libnetcdf19t64 already migrated to testing because it didn't build depend on dpkg-dev (>= 1.22.5). Ben file: title = "netcdf"; is_affected = (.build-depends ~ /\blibnetcdf-dev\b/)|(.depends ~ /\blibnetcdf\d+(?:t64)?\b/); is_good = .depends ~ /\blibnetcdf19t64\b/; is_bad = .depends ~ /\blibnetcdf19\b/; Kind Regards, Bas --- End Message --- --- Begin Message --- On 3/28/24 7:10 AM, Bas Couwenberg wrote: There is no auto-netcdf tracker because libnetcdf19t64 already migrated to testing because it didn't build depend on dpkg-dev (>= 1.22.5). What can be rebuilt has been rebuilt now. It would still be nice to have a tracker on release.d.o to see when the stragglers are fixed. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1--- End Message ---
Bug#1059532: marked as done (abseil:riscv64: uses privileged rdcycle instruction)
Your message dated Mon, 01 Apr 2024 01:34:23 + with message-id and subject line Bug#1059532: fixed in abseil 20230802.1-3 has caused the Debian Bug report #1059532, regarding abseil:riscv64: uses privileged rdcycle instruction 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.) -- 1059532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: abseil Version: 20220623.1-1 Severity: normal Tags: upstream Control: forwarded -1 https://github.com/abseil/abseil-cpp/pull/1550 On RISC-V, Abseil's cycle counter uses the rdcycle instruction, which is a privileged instruction when running on Debian's Linux kernels. This causes some widely used Abseil functions (e.g., certain member functions on absl::Mutex) to crash with a SIGILL. --- End Message --- --- Begin Message --- Source: abseil Source-Version: 20230802.1-3 Done: Benjamin Barenblat We believe that the bug you reported is fixed in the latest version of abseil, 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 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Benjamin Barenblat (supplier of updated abseil package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 31 Mar 2024 21:05:37 -0400 Source: abseil Architecture: source Version: 20230802.1-3 Distribution: unstable Urgency: medium Maintainer: Benjamin Barenblat Changed-By: Benjamin Barenblat Closes: 1059532 Changes: abseil (20230802.1-3) unstable; urgency=medium . * Apply an upstream patch to prevent SIGILLs on RISC-V. (Closes: #1059532) Checksums-Sha1: 22a5886daf9367c888c114cda18846481512dac5 2463 abseil_20230802.1-3.dsc 793973c3d2ada7b735eb554642d86e2b0264355e 9708 abseil_20230802.1-3.debian.tar.xz 417c1dc8210284d112f8f5b78a49629de5b162e6 7895 abseil_20230802.1-3_amd64.buildinfo Checksums-Sha256: 3121ab82ad298362fc0a0a8f5e76eac982debc36992664cb750f7b098cf552f1 2463 abseil_20230802.1-3.dsc 547d26e83a5b1a62a65ca0f3a6ec018300aefe2aebc603d05920a0a500c7 9708 abseil_20230802.1-3.debian.tar.xz 3f6700708f3c092b3ff60677988097a1d7bad2a99d4ed22c26032efcc39885b9 7895 abseil_20230802.1-3_amd64.buildinfo Files: b6862eb7f8044e82bdc1659829008e54 2463 libs optional abseil_20230802.1-3.dsc 1836c13c87b4adef1c48f92561950010 9708 libs optional abseil_20230802.1-3.debian.tar.xz 25c11dd41ddd6537c2d75d140fc57b49 7895 libs optional abseil_20230802.1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEQbf+q7LkywHKVTMA5ZUVm53A7cMFAmYKCfYACgkQ5ZUVm53A 7cOkwxAAksElaezK64CHrOezOh+6+hxYA5YAFuVQ2h1My8rWaMFcmJBfjOXzkAi+ mytAsskCaSkamJ/Rcxj6AsgNVlZIYPONuFrqHFMIajCBNg6lKinPa4v4Q23odOyf I1931e6J+bYUTDawSXm2yYr/nAdrzztsoyqNtS1OPSCuO2k6Iugn6xUdBQzFNGiv 1q925JcYfarDQ6jg3Oil5jz1QWQxB488/boIheGO32AnqUVldF8Az+OUGs7x+4pR 0burNccH0bl/0aRizu1WJkYjxQQqvWWesKXMW1TNH7SO80FbEln1jW7+uZ61VpeH MbgaH4hTzpaUtJvYAL5rDKbMbPR9xfmdHMmvqXIVjbDmWvJKlJwXPff7U5UYVA1o OFsWqYLzrxI0LvDLGgwkAxjIaCqfR/KGeu6xk1wFSeL+BvolHE7CUIBCHw8L+M+g 7NOMqZQGEZCb4ADjMQqMRKbESxekpz4ObqlzZ57YCO/iNX3dEUo97JcBZA1bBCGk D1WkEAcK0yNMv43bfBCZ3YvhR3N51HEN5TmFtY6Nb99kZLrY8mChaBz8lIx5fihg Jdey8DE1jaO4a/v7yMAMN+aQTzYzfoH038N8t5WSoIN33sRAEKt1xyHnrEXVbGuY bBhIqMlRW2uTTXphTu2k+dSrTf9eRw7+8MxhOiYxNcwFPtaPZTI= =ClPq -END PGP SIGNATURE- pgpWa6EsrX3sI.pgp Description: PGP signature --- End Message ---
Bug#1021794: marked as done (libipc-run-perl: delay after child exit)
Your message dated Mon, 01 Apr 2024 01:05:33 +
with message-id
and subject line Bug#1021794: fixed in libipc-run-perl 20231003.0-2
has caused the Debian Bug report #1021794,
regarding libipc-run-perl: delay after child exit
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.)
--
1021794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021794
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libipc-run-perl
Version: 20220807.0-1
I've noticed that IPC::Run::run() sometimes takes significantly more
time than the child process itself. For example:
$ time -p perl -MIPC::Run=run -e "run('sleep 0.7')"
real 1.18
user 0.03
sys 0.01
This is how it looks under strace:
$ strace -T -e trace=pselect6 perl -MIPC::Run=run -e "run('sleep 0.7')"
[ Process PID=8271 runs in 32 bit mode. ]
pselect6(0, NULL, NULL, NULL, {tv_sec=0, tv_nsec=10}, NULL) = 0 (Timeout)
<0.000164>
pselect6(0, NULL, NULL, NULL, {tv_sec=0, tv_nsec=10}, NULL) = 0 (Timeout)
<0.000161>
pselect6(0, NULL, NULL, NULL, {tv_sec=0, tv_nsec=10}, NULL) = 0 (Timeout)
<0.000160>
...
pselect6(0, NULL, NULL, NULL, {tv_sec=0, tv_nsec=10}, NULL) = 0 (Timeout)
<0.000248>
pselect6(0, NULL, NULL, NULL, {tv_sec=0, tv_nsec=10}, NULL) = 0 (Timeout)
<0.000212>
pselect6(0, NULL, NULL, NULL, {tv_sec=0, tv_nsec=5}, NULL) = ?
ERESTARTNOHAND (To be restarted if no handler) <0.031700>
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=8272, si_uid=1000,
si_status=0, si_utime=0, si_stime=0} ---
pselect6(0, NULL, NULL, NULL, {tv_sec=0, tv_nsec=468403068}, NULL) = 0 (Timeout)
<0.469205>
+++ exited with 0 +++
So there's nearly half a second delay after the child exits.
-- System Information:
Architecture: i386
Versions of packages libipc-run-perl depends on:
ii perl5.34.0-5
ii libio-pty-perl 1:1.15-2+b1
--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Source: libipc-run-perl
Source-Version: 20231003.0-2
Done: gregor herrmann
We believe that the bug you reported is fixed in the latest version of
libipc-run-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 1021...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gregor herrmann (supplier of updated libipc-run-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: SHA512
Format: 1.8
Date: Mon, 01 Apr 2024 02:46:08 +0200
Source: libipc-run-perl
Architecture: source
Version: 20231003.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group
Changed-By: gregor herrmann
Closes: 1021794
Changes:
libipc-run-perl (20231003.0-2) unstable; urgency=medium
.
* Add 1021794_child_exit.patch: Reduce delays in detecting child exit.
Patch taken from upstream patch series (PR#172). (Closes: #1021794)
* Update years of packaging copyright.
Checksums-Sha1:
cbe9a1f99661c4ac3c279c4da8edfab9c9cfc8ee 2485 libipc-run-perl_20231003.0-2.dsc
7f38bfca451715f5d4935bcb0e9766d6a8fe8bbd 8856
libipc-run-perl_20231003.0-2.debian.tar.xz
Checksums-Sha256:
780f5dca60dc6202894430c00f903c154e3570f94eafb2ad074e52c56eb30d54 2485
libipc-run-perl_20231003.0-2.dsc
e4cf0ff8b21733689dea06a195c9e26427c4878a7017285dbf9efcc01e47cb34 8856
libipc-run-perl_20231003.0-2.debian.tar.xz
Files:
c7063a2b0642be668c5cd3090fcb70a1 2485 perl optional
libipc-run-perl_20231003.0-2.dsc
a6a277f2086fbacfb4fda825c02229da 8856 perl optional
libipc-run-perl_20231003.0-2.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmYKBL5fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYZ3hAAp95aLOX6rLjZBuaNXJmHglYW5FdYKTCz3BlKkDkrwr02tBMA+BtOAoXy
JVCJ1FDcQVwspQHtanC8mvMAC4tpJln0SVY7oNKgt6wpxTbp52ws/lpdn8rLSnzu
GKtgAWjr3w2ysR2mTUcQD78qkl4IlGz2gcFOrjlp3UrdfW94NQJ3TcGE0VcOgVgf
kZeUw95pjLJTUreoWebbSMMBBiUfPTXlsepU+7y0wsvUSgbnI33AF7BDRKIYu71S
i12vcOmkhHlxT6VIvdlgvt+5jd4zRzd++M3N25Gd9qjXdLZfPBskBgjpsa1vqe3V
16QNuK3WgXTLzuIOPK8KjMO5z6q7eYyxiBvRCjMqJbVftRNfp/e42G1JAQnAJX7q
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org:
> reassign 1068160 haskell-haskell-gi
Bug #1068160 [src:haskell-gi-glib] haskell-gi-glib: FTBFS on mips64el: couldn't
find API description for GLib.time_t
Bug reassigned from package 'src:haskell-gi-glib' to 'haskell-haskell-gi'.
No longer marked as found in versions haskell-gi-glib/2.0.29-1.
Ignoring request to alter fixed versions of bug #1068160 to the same values
previously set
> forcemerge 1067272 1068160
Bug #1067272 {Done: Ilias Tsitsimpis }
[haskell-haskell-gi] haskell-gi-glib: FTBFS: make: ***
[/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 1
Bug #1068160 [haskell-haskell-gi] haskell-gi-glib: FTBFS on mips64el: couldn't
find API description for GLib.time_t
Set Bug forwarded-to-address to
'https://github.com/haskell-gi/haskell-gi/pull/430'.
1036884 was blocked by: 1067916 1067829 1067171 1067677 1067561 1065787 1065973
1067189 1062847 1068068 1067193 1067458 1067288 1055352 1067272 1067192 1066049
1065816 1055530 1067190 1067175 1067069 1067170 1066794 1066328 1067508 1067676
1067494 1067509
1036884 was not blocking any bugs.
Added blocking bug(s) of 1036884: 1068160
Marked Bug as done
Added indication that 1068160 affects haskell-gi-glib
Marked as fixed in versions haskell-haskell-gi/0.26.7-4.
There is no source info for the package 'haskell-haskell-gi' at version
'0.26.7-2' with architecture ''
Unable to make a source version for version '0.26.7-2'
Marked as found in versions 0.26.7-2.
Added tag(s) trixie and sid.
Merged 1067272 1068160
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1036884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036884
1067272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067272
1068160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068160
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1067968: marked as done (defcon: Please replace python3-appdirs build-dependency with platformdirs)
Your message dated Sun, 31 Mar 2024 23:35:47 + with message-id and subject line Bug#1067968: fixed in defcon 0.10.3-2 has caused the Debian Bug report #1067968, regarding defcon: Please replace python3-appdirs build-dependency with platformdirs 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.) -- 1067968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: defcon Version: 0.10.3-1 Severity: important Control: block 1060427 by -1 Tags: trixie sid User: debian-pyt...@lists.debian.org Usertags: appdirs-removal python3-appdirs is dead upstream[1] and its Debian maintainer has indicated that it should not be included in trixie[2]. A recommended replacement is python3-platformdirs[3], which is a fork of appdirs with a very similar API. Please migrate from appdirs to platformdirs or some other replacement, so that appdirs can be removed. Thanks, smcv [1] https://github.com/ActiveState/appdirs/commit/8734277956c1df3b85385e6b308e954910533884 [2] https://bugs.debian.org/1060427 [3] https://pypi.org/project/platformdirs/ --- End Message --- --- Begin Message --- Source: defcon Source-Version: 0.10.3-2 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of defcon, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated defcon package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 31 Mar 2024 19:03:01 -0400 Source: defcon Architecture: source Version: 0.10.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Fonts Task Force Changed-By: Boyuan Yang Closes: 1067968 Changes: defcon (0.10.3-2) unstable; urgency=medium . * Team upload. * debian/control: + Drop useless build-dependency on python3-appdirs. (Closes: #1067968) + Move package description to the source package section. Checksums-Sha1: 1a9ee00a08829d347095c12345884291017f92e2 2606 defcon_0.10.3-2.dsc 7ee77bd75b85b24c0a7cef18182d3b3aca76bf38 426262 defcon_0.10.3.orig.tar.gz 76dab17013a6916fe5e776849d82d05b8bb22c32 3976 defcon_0.10.3-2.debian.tar.xz 0e4c88150e42198de61aedae3bd758eacb9049a0 8351 defcon_0.10.3-2_amd64.buildinfo Checksums-Sha256: 32ba6ece9203d645da70890747f4ae9f0c0ba26254eac6ae1261aa65660cb4d1 2606 defcon_0.10.3-2.dsc 225b082e0d1458be5e91c302c8351d3bc1dcb4728b9f5c1241f1bf68f24b5fff 426262 defcon_0.10.3.orig.tar.gz ba5b1a3c9e71e01f146ff1ce2514b2a470b2412ff9841308ab6a131c709e4147 3976 defcon_0.10.3-2.debian.tar.xz 4bfddaa7cdc08f03b0f80846f1f0521873ea51dec72106f7113b6ae36774ec7c 8351 defcon_0.10.3-2_amd64.buildinfo Files: 7c94f6ba39ea01a57a30dff65291f0df 2606 devel optional defcon_0.10.3-2.dsc ab853ef6adf844dcbe3574a3c917811b 426262 devel optional defcon_0.10.3.orig.tar.gz 740a5ca8dc167211ab73608e6f296a93 3976 devel optional defcon_0.10.3-2.debian.tar.xz 8d5d1fd4200145f773ae8979221cfadb 8351 devel optional defcon_0.10.3-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmYJ75kACgkQwpPntGGC Ws6W5A/8C21DMG5E/BqTMorV8ZwkeVGlpcO3MbZbqrXo0XkHvpGsu1AtVLLTCYZh rmy/q3gBAh4N8lJginZBOW4VQVMs9cVl5dQfLPrntcZmsxAvY/F3mMhHpFc5yDs7 51i3EfnpHiQJDsHV5RUY/7mzQs2cLgVAlQg01+G7XBTUYFzjnJvjaUgbIOD98wNA QkPChMBVC9IUqqgxYXy28eFDyfCmNlkLcJJY2oW6D2vKr+CffeBQVb/jLDHCR8Hf oQQaU+Sn0OxgLWXLTrhoBkuwSKmfUKIwHEMfV2QoR8If8TEgCTr5LZvK+CEzyK6M 1fKDllK4h72aqpHaRrf5WlTDkcE5eY26dM+QXSOTo6JgCnf/5N/dlt1VppzAYbRt SXZhK253TmrE6GSZ/5E58b4RiWpMQrO3113Y0YyQqEZLRXGWjdNZyEM2VV8K3lIh osjjUWr0bsIi+3OpF6bT/AhxRgOOnIpvF5DbU8qbQC1g5TaKw8ZNK9Sv2pqNbp/p /LEmd2m+SY1LKoJL0y2H8a58sgdGZSDmnFce0GJqftQf0JCMJLi7qA93TSpsYJHX p6hFTga98twVs89rrx2iPINLu5VWrnj9IXo8CzhWfld53tw18eKWIJmJiNxlUSXO NQYQMOmzoTCp+H3x9VzZ7Gb4brieOZMxmaUHusi0tzvD3OnnJJw= =9XVV -END PGP SIGNATURE- pgpF33Sv7HZex.pgp Description: PGP signature --- End Message ---
Bug#1068062: marked as done (Update Build-Depends for the time64 library renames)
Your message dated Sun, 31 Mar 2024 22:52:04 + with message-id and subject line Bug#1068062: fixed in workrave 1.10.52-2 has caused the Debian Bug report #1068062, regarding Update Build-Depends for the time64 library renames 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.) -- 1068062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: workrave Version: 1.10.52-1 Severity: serious Tags: ftbfs The package explicitly Build-Depends: libglib2.0-0, this needs to be changed to libglib2.0-0t64 if it's needed at all. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 --- Source: workrave Source-Version: 1.10.52-2 Done: Francois Marier We believe that the bug you reported is fixed in the latest version of workrave, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Francois Marier (supplier of updated workrave package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 31 Mar 2024 15:35:10 -0700 Source: workrave Architecture: source Version: 1.10.52-2 Distribution: unstable Urgency: medium Maintainer: Francois Marier Changed-By: Francois Marier Closes: 1052115 1068062 Changes: workrave (1.10.52-2) unstable; urgency=medium . * Update Build-Depends to libglib2.0-0t64 (closes: #1068062) * Add support for gnome-shell 46 (closes: #1052115) Checksums-Sha1: fc46280f85a1c55d97272707e7afd9807eab00e8 2971 workrave_1.10.52-2.dsc 268bd5b876ae42bcad5e977428098f09d5799567 20264 workrave_1.10.52-2.debian.tar.xz 7bb69cf9acbbc9aa32775776a347438039bc3eb4 21060 workrave_1.10.52-2_source.buildinfo Checksums-Sha256: f52c252faa3423c1ee57362567ea022ece17de516726195da3e4b8b65ee8789a 2971 workrave_1.10.52-2.dsc c4eb165941aa51877b2b72a5d98aa6ed63f60720cd8361d9f4dd26a599e63ac5 20264 workrave_1.10.52-2.debian.tar.xz e29227e52e30ec9766397a5410aec4619c115ded5a30d663af669f2db6562ac9 21060 workrave_1.10.52-2_source.buildinfo Files: 8d9dac28160451063e7c15b7737054b3 2971 gnome optional workrave_1.10.52-2.dsc 9decc029bd49bdd08427afccd3f5 20264 gnome optional workrave_1.10.52-2.debian.tar.xz 7729ed476222fc3ee8bebfb856599bdc 21060 gnome optional workrave_1.10.52-2_source.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEjEcLKgsxVo4RDUMlFigfLgB8mNEFAmYJ5yNfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDhD NDcwQjJBMEIzMTU2OEUxMTBENDMyNTE2MjgxRjJFMDA3Qzk4RDEACgkQFigfLgB8 mNEa8xAAnLz7jkFQvV+nf2luZ/VfOMs19yYin3g3IULVTc0VJbHYLPO+r2XgiH8S 6fXzQEjY8HgyWMkTM9tOGDozi3P+gxO3jHxZch7xisrPVH0nmubluO/DSo0hohkk 05VQVXxh6CRCmbnW2lxE2rwVH2HRe9SeORzu0WbALVFSOG7fGeAH1/vlFeI9KA3T w3xRGDxVxvByrmVjT1s7IpPrhUKVOJnirX2uYh+Qt6Q0GEOms10I0KYT6LGSg4co V+pxpMA6r3s9kYCc69CIoRo7MBrbgOjWNDM7DzXHNxBMan6qoKaFV/C6urJRUTlL /0wDcTPZL1t6XjqBhmCfH4V9U9kfNvyr1vYz51eGwSI2jVst7W0DKo6V+Wzh4I4U x2NyIRBRF/brjl2EjCi/r/QsCUlSnYp7MuP2r1rcDYJ3OU+W79vqTJ2WJtT+0fXC 4U7yxvTk8NSTJZsN+82ytiiAqtPIW5OGHlejFLhSXQ9vLGBwPw0EJgjGoJmFXKTF ybDKH4uZFlHZiwUR2QRxqKMRkhnKZ373tiHAPWiYhKw83uCQPYnWekesOZ8hjJYY DQcmz6WEDOh9IE8DXpRA8Krx3+Amz4mIkEnZd3SDNGK7DdryL6gU5b20uKhU7Tta Jz/WUuOEYzX59eamk4RF729hN1GKvL/7JNjQzB6+82XE2STXi9g= =9wt4 -END PGP SIGNATURE- pgpd9BgNljVzP.pgp Description: PGP signature --- End Message ---
Bug#1066314: marked as done (regina-rexx: FTBFS: ./rexxext.c:95:7: error: implicit declaration of function ‘getcallstack’; did you mean ‘popcallstack’? [-Werror=implicit-function-declaration])
Your message dated Sun, 31 Mar 2024 22:51:36 + with message-id and subject line Bug#1066314: fixed in regina-rexx 3.9.5+dfsg1-0.1 has caused the Debian Bug report #1066314, regarding regina-rexx: FTBFS: ./rexxext.c:95:7: error: implicit declaration of function ‘getcallstack’; did you mean ‘popcallstack’? [-Werror=implicit-function-declaration] 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.) -- 1066314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066314 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: regina-rexx Version: 3.6-2.4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > cc -DNDEBUG -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 > -DREGINA_SHARE_DIRECTORY=\"//usr/share/regina-rexx\" -funsigned-char > -DREGINA_VERSION_DATE=\""31 Dec 2011"\" -DREGINA_VERSION_MAJOR=\"3\" > -DREGINA_VERSION_MINOR=\"6\" -DREGINA_VERSION_SUPP=\"\" -DHAVE_CONFIG_H > -I. -I. -I./contrib-o rexxext.o -c ./rexxext.c > ./rexxext.c: In function ‘__regina_rex_getcallstack’: > ./rexxext.c:95:7: error: implicit declaration of function ‘getcallstack’; did > you mean ‘popcallstack’? [-Werror=implicit-function-declaration] >95 | getcallstack( TSD, parms->value ); > | ^~~~ > | popcallstack > cc1: some warnings being treated as errors > make[1]: *** [Makefile:427: rexxext.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/regina-rexx_3.6-2.4_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=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: regina-rexx Source-Version: 3.9.5+dfsg1-0.1 Done: Agustin Martin Domingo We believe that the bug you reported is fixed in the latest version of regina-rexx, 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 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Agustin Martin Domingo (supplier of updated regina-rexx 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: Mon, 01 Apr 2024 00:06:09 +0200 Source: regina-rexx Architecture: source Version: 3.9.5+dfsg1-0.1 Distribution: unstable Urgency: medium Maintainer: Alen Zekulic Changed-By: Agustin Martin Domingo Closes: 1027405 1066314 Changes: regina-rexx (3.9.5+dfsg1-0.1) unstable; urgency=medium . * Non-maintainer upload with maintaner agreement. . [ Debian Janitor ] * Use secure URI in debian/watch. * Fix day-of-week for changelog entry 2.2-1. * Update standards version to 4.5.1, no changes needed. * Use secure URI in Homepage field. * Update standards version to 4.6.1, no changes needed. . [ Agustin Martin Domingo ] * New upstream version (Closes: #1066314). - Remove REGUTIL_TERM_LIB stuff (#930005). Fixed upstream in a simpler way. - _configures_fix-alpha-compilation.diff: renamed from _AZ_configures.diff for clarity. -
Bug#1027405: marked as done (regina-rexx FTCBFS: builds for the build architecture)
Your message dated Sun, 31 Mar 2024 22:51:36 +
with message-id
and subject line Bug#1027405: fixed in regina-rexx 3.9.5+dfsg1-0.1
has caused the Debian Bug report #1027405,
regarding regina-rexx FTCBFS: builds for the build architecture
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.)
--
1027405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: regina-rexx
Version: 3.6-2.4
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
regina-rexx fails to cross build from source, because it builds for the
build architecture. Fixing this is not entirely trivial. The obvious fix
of passing --build and --host to configure is insufficient. Beyond that,
the C compiler must be forced via the CC environment variable. Even
then, the build system fails to transfer this assignment over to make.
To make matters worse, it skips checking for --version-script (and thus
symbol versioning) unless the compiler is exactly gcc. I'm attaching a
patch for your convenience.
Helmut
diff --minimal -Nru regina-rexx-3.6/debian/changelog
regina-rexx-3.6/debian/changelog
--- regina-rexx-3.6/debian/changelog2021-05-06 18:28:52.0 +0200
+++ regina-rexx-3.6/debian/changelog2022-12-23 23:43:11.0 +0100
@@ -1,3 +1,13 @@
+regina-rexx (3.6-2.5) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTCBFS: (Closes: #-1)
++ Pass --build and --host to configure.
++ Pass CC to configure and make.
++ cross.patch: Check for --version-script even if the compiler is prefixed.
+
+ -- Helmut Grohne Fri, 23 Dec 2022 23:43:11 +0100
+
regina-rexx (3.6-2.4) unstable; urgency=medium
* Non-maintainer upload with maintaner agreement.
diff --minimal -Nru regina-rexx-3.6/debian/patches/cross.patch
regina-rexx-3.6/debian/patches/cross.patch
--- regina-rexx-3.6/debian/patches/cross.patch 1970-01-01 01:00:00.0
+0100
+++ regina-rexx-3.6/debian/patches/cross.patch 2022-12-23 23:43:11.0
+0100
@@ -0,0 +1,33 @@
+--- regina-rexx-3.6.orig/configure.in
regina-rexx-3.6/configure.in
+@@ -346,9 +346,7 @@
+ AC_SUBST(GCI_SHO)
+ AC_SUBST(HAVE_GCI)
+
+-if test "$ac_cv_prog_CC" = "gcc" -o "$ac_cv_prog_CC" = "g++"; then
+- MH_CHECK_GCC_VERSION_SCRIPT
+-fi
++MH_CHECK_GCC_VERSION_SCRIPT
+
+ dnl enable_posix_threads="yes"
+ MH_CHECK_POSIX_THREADS
+--- regina-rexx-3.6.orig/configure
regina-rexx-3.6/configure
+@@ -5862,8 +5862,6 @@
+
+
+
+-if test "$ac_cv_prog_CC" = "gcc" -o "$ac_cv_prog_CC" = "g++"; then
+-
+ { $as_echo "$as_me:${as_lineno-$LINENO}: checking whether gcc understands
--version-script" >&5
+ $as_echo_n "checking whether gcc understands --version-script... " >&6; }
+ if test "${mh_cv_version_script+set}" = set; then :
+@@ -5909,8 +5907,6 @@
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: $mh_cv_version_script" >&5
+ $as_echo "$mh_cv_version_script" >&6; }
+
+-fi
+-
+
+ MH_MT_LIBS=""
+ THREADING_COMPILE=""
diff --minimal -Nru regina-rexx-3.6/debian/patches/series
regina-rexx-3.6/debian/patches/series
--- regina-rexx-3.6/debian/patches/series 2021-05-06 17:13:47.0
+0200
+++ regina-rexx-3.6/debian/patches/series 2022-12-23 23:43:11.0
+0100
@@ -7,3 +7,4 @@
_Makefile.in_Debian-Installation.diff
2000_regina-config_use-wrapper.diff
2000_Makefile.in_Do-not-hardcode-FLAGS.diff
+cross.patch
diff --minimal -Nru regina-rexx-3.6/debian/rules regina-rexx-3.6/debian/rules
--- regina-rexx-3.6/debian/rules2021-05-06 18:28:52.0 +0200
+++ regina-rexx-3.6/debian/rules2022-12-23 23:43:11.0 +0100
@@ -18,9 +18,8 @@
rexxpkg=regina-rexx
-export DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
-export DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH)
-export DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
+include /usr/share/dpkg/architecture.mk
+export DEB_HOST_ARCH DEB_BUILD_ARCH DEB_HOST_MULTIARCH
ifeq ($(DEB_BUILD_ARCH), ia64)
DEB_CFLAGS_MAINT_STRIP=""
@@ -31,7 +30,10 @@
DPKG_EXPORT_BUILDFLAGS = 1
include /usr/share/dpkg/buildflags.mk
+include /usr/share/dpkg/buildtools.mk
+
confflags=--prefix=/usr \
+ --build=$(DEB_BUILD_GNU_TYPE) --host=$(DEB_HOST_GNU_TYPE) \
--with-addon-dir=/usr/lib/$(DEB_HOST_MULTIARCH)/$(rexxpkg)/$(soversion)
\
--libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)
@@ -47,7 +49,7 @@
[ -e "$(CONFIGTGZ)" ] || tar -cvzf $(CONFIGTGZ) $(addprefix
common/,$(CONFIGS))
for i in $(CONFIGS); do cp -f
Bug#1052115: marked as done (workrave-gnome: needs update for GNOME Shell 46)
Your message dated Sun, 31 Mar 2024 22:52:04 +
with message-id
and subject line Bug#1052115: fixed in workrave 1.10.52-2
has caused the Debian Bug report #1052115,
regarding workrave-gnome: needs update for GNOME Shell 46
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.)
--
1052115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: workrave-gnome
Version: 1.10.51.1-3
Severity: important
Tags: trixie sid upstream
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-45
As with every 6-month GNOME Shell release cycle, extensions will need to
be updated for GNOME Shell 45, which is currently being prepared in
experimental. A porting guide is available here:
https://gjs.guide/extensions/upgrading/gnome-shell-45.html
For the 44 -> 45 transition, most or all extensions will need
incompatible code changes, because GNOME Shell has switched from
non-standard gjs modules ("const Foo = imports.gi.Foo") to ECMAScript
modules ("import Foo from 'gi://Foo'") and all extensions need to do
the same. This means most or all extensions will split into a branch
for Shell <= 44 (which might not be maintained upstream any more) and
a branch for Shell >= 45.
If not updated, this extension will have to be removed from testing for
the GNOME Shell 45 transition (I don't know when that will be). This
bug will be raised to serious severity when the transition is ready to
go ahead.
The upstream developer might already have made this change (I haven't
checked). If a new upstream version is compatible with Shell 45 but not
44, please upload to experimental for now.
Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: workrave
Source-Version: 1.10.52-2
Done: Francois Marier
We believe that the bug you reported is fixed in the latest version of
workrave, 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 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Francois Marier (supplier of updated workrave package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 31 Mar 2024 15:35:10 -0700
Source: workrave
Architecture: source
Version: 1.10.52-2
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier
Changed-By: Francois Marier
Closes: 1052115 1068062
Changes:
workrave (1.10.52-2) unstable; urgency=medium
.
* Update Build-Depends to libglib2.0-0t64 (closes: #1068062)
* Add support for gnome-shell 46 (closes: #1052115)
Checksums-Sha1:
fc46280f85a1c55d97272707e7afd9807eab00e8 2971 workrave_1.10.52-2.dsc
268bd5b876ae42bcad5e977428098f09d5799567 20264 workrave_1.10.52-2.debian.tar.xz
7bb69cf9acbbc9aa32775776a347438039bc3eb4 21060
workrave_1.10.52-2_source.buildinfo
Checksums-Sha256:
f52c252faa3423c1ee57362567ea022ece17de516726195da3e4b8b65ee8789a 2971
workrave_1.10.52-2.dsc
c4eb165941aa51877b2b72a5d98aa6ed63f60720cd8361d9f4dd26a599e63ac5 20264
workrave_1.10.52-2.debian.tar.xz
e29227e52e30ec9766397a5410aec4619c115ded5a30d663af669f2db6562ac9 21060
workrave_1.10.52-2_source.buildinfo
Files:
8d9dac28160451063e7c15b7737054b3 2971 gnome optional workrave_1.10.52-2.dsc
9decc029bd49bdd08427afccd3f5 20264 gnome optional
workrave_1.10.52-2.debian.tar.xz
7729ed476222fc3ee8bebfb856599bdc 21060 gnome optional
workrave_1.10.52-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQKTBAEBCgB9FiEEjEcLKgsxVo4RDUMlFigfLgB8mNEFAmYJ5yNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDhD
NDcwQjJBMEIzMTU2OEUxMTBENDMyNTE2MjgxRjJFMDA3Qzk4RDEACgkQFigfLgB8
mNEa8xAAnLz7jkFQvV+nf2luZ/VfOMs19yYin3g3IULVTc0VJbHYLPO+r2XgiH8S
6fXzQEjY8HgyWMkTM9tOGDozi3P+gxO3jHxZch7xisrPVH0nmubluO/DSo0hohkk
05VQVXxh6CRCmbnW2lxE2rwVH2HRe9SeORzu0WbALVFSOG7fGeAH1/vlFeI9KA3T
w3xRGDxVxvByrmVjT1s7IpPrhUKVOJnirX2uYh+Qt6Q0GEOms10I0KYT6LGSg4co
V+pxpMA6r3s9kYCc69CIoRo7MBrbgOjWNDM7DzXHNxBMan6qoKaFV/C6urJRUTlL
/0wDcTPZL1t6XjqBhmCfH4V9U9kfNvyr1vYz51eGwSI2jVst7W0DKo6V+Wzh4I4U
x2NyIRBRF/brjl2EjCi/r/QsCUlSnYp7MuP2r1rcDYJ3OU+W79vqTJ2WJtT+0fXC
4U7yxvTk8NSTJZsN+82ytiiAqtPIW5OGHlejFLhSXQ9vLGBwPw0EJgjGoJmFXKTF
Processed: Re: opari2: please make the build reproducible
Processing control commands: > close -1 2.0.7-2 Bug #1026877 [src:opari2] opari2: please make the build reproducible Marked as fixed in versions opari2/2.0.7-2. Bug #1026877 [src:opari2] opari2: please make the build reproducible Marked Bug as done -- 1026877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964789: marked as done (ITA: zatacka -- arcade multiplayer game like nibbles)
Your message dated Sun, 31 Mar 2024 22:15:06 + with message-id and subject line Bug#964789: fixed in zatacka 1.1.0-1 has caused the Debian Bug report #964789, regarding ITA: zatacka -- arcade multiplayer game like nibbles 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.) -- 964789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: normal As described in https://bugs.debian.org/962551 , package zatacka has a dead upstream with inactive packaging maintainer in Debian. As a result, I orphan this package in hope that others may make better maintenance on it. There is an active fork at https://bugs.debian.org/904633 and the new maintainer should consider switching to this new upstream. Anyone who want to adopt this package can directly go ahead and do not need to notify me. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: zatacka Binary: zatacka Version: 0.1.8-6 Maintainer: Debian Games Team Uploaders: Boyuan Yang , Build-Depends: debhelper (>= 9), autotools-dev, dh-autoreconf, autoconf, libsdl1.2-dev, libsdl-ttf2.0-dev, libsdl-image1.2-dev, fonts- dejavu Architecture: any Standards-Version: 3.9.5 Format: 3.0 (quilt) Files: f5c305f23e5cdbf0b9e3f944be8fe4cb 2001 zatacka_0.1.8-6.dsc d7a4019b7dbd25da9c513d0c9d4b8ae8 397999 zatacka_0.1.8.orig.tar.gz 8940a470c16fff144c1d49138a38fe1f 12620 zatacka_0.1.8-6.debian.tar.xz Vcs-Browser: https://github.com/alexdantas/zatacka.debian Vcs-Git: git://github.com/alexdantas/zatacka.debian.git -b master Checksums-Sha256: bdaf09ba839190a3daee5c7db0139a4d6e6d81623b9dd1baea22779b8df4afa6 2001 zatacka_0.1.8-6.dsc 9eb8263dbec805cf0a6564b15269347f30dd2db094f47ed9e0d2710d1fbc3848 397999 zatacka_0.1.8.orig.tar.gz aab8358fafa2dbfef851fdaa1fd6203097f891aba90bdf45f0aea0793b0aa3d0 12620 zatacka_0.1.8-6.debian.tar.xz Homepage: http://zatacka.sourceforge.net/ Package-List: zatacka deb games optional arch=any Directory: pool/main/z/zatacka Priority: source Section: games Package: zatacka Version: 0.1.8-6 Installed-Size: 200 Maintainer: Debian Games Team Architecture: amd64 Depends: libc6 (>= 2.4), libsdl-image1.2 (>= 1.2.10), libsdl-ttf2.0-0, libsdl1.2debian (>= 1.2.11), libstdc++6 (>= 4.1.1), fonts-dejavu-core Description-en: arcade multiplayer game like nibbles This is an arcade multiplayer game for 2 - 6 players on one keyboard, clone of Achtung die Kurve classical dos game. You handle your line and you must sidetrack lines of other players and of course walls. When some player dies, survival gets one point. When only one player is left alive, the round is finished. Each game has eleven rounds. Description-md5: eb458df8c5238adbbe1fbe2844399917 Homepage: http://zatacka.sourceforge.net/ Tag: game::arcade, implemented-in::c, interface::graphical, interface::x11, role::program, uitoolkit::sdl, use::gameplaying, x11::application Section: games Priority: optional Filename: pool/main/z/zatacka/zatacka_0.1.8-6_amd64.deb Size: 65160 MD5sum: 1fa6b22d8ef4ea75050f42dce5fd89ef SHA256: f892da1bc1ecb9372d5b28799868b4feda4524bb3a53680e931cb4c959440580 -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: zatacka Source-Version: 1.1.0-1 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of zatacka, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated zatacka package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 31 Mar 2024 23:04:51 +0200 Source: zatacka Binary: zatacka zatacka-dbgsym Architecture: source amd64 Version: 1.1.0-1 Distribution: unstable Urgency: medium Maintainer: Debian
Bug#904633: marked as done (newer upstream/forked version available)
Your message dated Sun, 31 Mar 2024 22:15:06 + with message-id and subject line Bug#904633: fixed in zatacka 1.1.0-1 has caused the Debian Bug report #904633, regarding newer upstream/forked version 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.) -- 904633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zatacka Version: 0.1.8-5.1 Severity: normal Please upgrade to the newer version, 0.3.1 available at https://github.com/simenheg/zatackax Thanks --- End Message --- --- Begin Message --- Source: zatacka Source-Version: 1.1.0-1 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of zatacka, 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 904...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated zatacka package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 31 Mar 2024 23:04:51 +0200 Source: zatacka Binary: zatacka zatacka-dbgsym Architecture: source amd64 Version: 1.1.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Alexandre Detiste Description: zatacka- arcade multiplayer game like nibbles Closes: 626767 738090 904633 908387 908572 964789 Changes: zatacka (1.1.0-1) unstable; urgency=medium . * Adopt package (Closes: #964789) * Update watch file for new maintainer (Closes: #904633, #908387, #908572, #626767) (LP: #246734, #1565485) * Remove .desktop file, upstream provides one now * Install upstream icon (Closes: #738090) (LP: #/922847) * Replace fonts-dejavu-core by fonts-jura * Add dependency on libsdl-mixer1.2-dev * Provide virtual package zatackax * Copyright review Checksums-Sha1: 56430251dc13f2b4d47759f3d707bc39e383e719 2000 zatacka_1.1.0-1.dsc 35d09252d4ffa7aab10c65b27e4d69c7f764d57c 3835877 zatacka_1.1.0.orig.tar.gz b927dbc34d2369151b4784c1d8b3ed7fb23826c5 14088 zatacka_1.1.0-1.debian.tar.xz 1999b64c9d987a408c64d5c1d684cb193a5254da 65280 zatacka-dbgsym_1.1.0-1_amd64.deb ad1ae91b12ee6c81ada0fb9c752428bc73cbd16e 13257 zatacka_1.1.0-1_amd64.buildinfo aaefd945abebaf2ff9ffae1da39dab5e3f6463c8 3381060 zatacka_1.1.0-1_amd64.deb Checksums-Sha256: e2f9acfa8619c6805dc46317b85ba68ba05f8ae5728fd71919675719bf77833c 2000 zatacka_1.1.0-1.dsc 9339b75a76c9a6cb97d80e79a7108989d504b0b43eecad3ba2362606d6e5e41d 3835877 zatacka_1.1.0.orig.tar.gz d153e7dd78849e1ffd6895b2434cea7d0e5aab51d1e48898a84b29e8b20367ec 14088 zatacka_1.1.0-1.debian.tar.xz caa100ba6fa13f47e774b16f32a8e158b51c22c6145d424de76e572c5f9a56b2 65280 zatacka-dbgsym_1.1.0-1_amd64.deb 3c8a4505150879a4cba3bb0e6ca07c59b781e8443297bb45d3b27576b165650b 13257 zatacka_1.1.0-1_amd64.buildinfo 447d502069ab296efe5ae3af7b31e3eb41967b09b41302199e30a19c113c737b 3381060 zatacka_1.1.0-1_amd64.deb Files: 7752ec641a10a1f67efc416779d0e70d 2000 games optional zatacka_1.1.0-1.dsc 578609b93d2158ac3ef40e8475149946 3835877 games optional zatacka_1.1.0.orig.tar.gz 8b16978c46f98042e47bb60409991478 14088 games optional zatacka_1.1.0-1.debian.tar.xz b303cec41b136890f9ac16920c2abab5 65280 debug optional zatacka-dbgsym_1.1.0-1_amd64.deb be3ef1608a719305fbd5b494c841d92c 13257 games optional zatacka_1.1.0-1_amd64.buildinfo 0464f5c21fcda728d13408b1ed402b69 3381060 games optional zatacka_1.1.0-1_amd64.deb -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmYJ0woRHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBodihAAvedCqs+tjzE/TTbabm/4QFJtrfTbW3Fq IO/6hR9kMg26a8any1CUOBTLwiUtUYsrIG36+xMXLtknvYFslztLzEpNyJ8qcTts PLLGS6cDfIGUn/4QHTYYjUzr3b+/8zFNQcTqkOqJmRzFTn+qDbgxDl5Upbu3xabY pFH/6fyVlvpeQyfaatqc00Tk6d8U+wY8JoUTRgDwMzMD1bdhsaqO0K581xM2A7Gw AUT7+i8NJ1KpVx27KHVLSmWphcVOAwX9eij/ErzdeePL0QMKf5cIsVV8QglhILFa Cq/XYd+lJPwLBddLQpFa18uDNADbWipgPtalbz+nM+FUB6mX+y7sl0Aw1BxPHV5K 7SS0ofzDEi6rjh9m5+6Rggwr+V2H9YIMZgFE6DgY+qiiBzNa9mZl3NVoqEkkivT7 tnaX6RNRdXGzN6/cWFBXtcXcfCn0yYG0wZ8ktxg0yH/2KY0U2x66rjRWiVbHXIXg C0aCAT/5x1WPYMvsNae6JjpPR71WF22nP/tNd7E6h9kHFVayXY/WHwVU9edVZRG2
Bug#908572: marked as done (zatacka: Crashes with segmentation fault on changing settings)
Your message dated Sun, 31 Mar 2024 22:15:06 + with message-id and subject line Bug#908572: fixed in zatacka 1.1.0-1 has caused the Debian Bug report #908572, regarding zatacka: Crashes with segmentation fault on changing settings 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.) -- 908572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908572 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zatacka Version: 0.1.8-5+b3 Severity: important Dear Maintainer, I am using Zatacka 0.1.8-5+b3 on Debian Stretch. Whenever I change some settings and try to start the game, the game crashes printing "Segmentation Fault" on terminal. The exact steps are as follows: 1. $ zatacka 2. Press 'R' twice to set Resolution to 1024x768 3. Press 'F' for fullscreen 4. Press 'Space' to start the game 5. The game should crash. If not, press 'Space' again Here's the backtrace: (gdb) bt #0 0x77748113 in SDL_MapRGB () from /usr/lib/x86_64-linux- gnu/libSDL-1.2.so.0 #1 0x637c in loop (screen=0x557b0da0) at fx.cpp:103 #2 0x56f8 in main (argc=, argv=) at main.cpp:41 -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages zatacka depends on: ii libc62.24-11+deb9u3 ii libsdl-image1.2 1.2.12-5+deb9u1 ii libsdl-ttf2.0-0 2.0.11-3+b1 ii libsdl1.2debian 1.2.15+dfsg1-4 ii libstdc++6 6.3.0-18+deb9u1 zatacka recommends no packages. zatacka suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: zatacka Source-Version: 1.1.0-1 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of zatacka, 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 908...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated zatacka package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 31 Mar 2024 23:04:51 +0200 Source: zatacka Binary: zatacka zatacka-dbgsym Architecture: source amd64 Version: 1.1.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Alexandre Detiste Description: zatacka- arcade multiplayer game like nibbles Closes: 626767 738090 904633 908387 908572 964789 Changes: zatacka (1.1.0-1) unstable; urgency=medium . * Adopt package (Closes: #964789) * Update watch file for new maintainer (Closes: #904633, #908387, #908572, #626767) (LP: #246734, #1565485) * Remove .desktop file, upstream provides one now * Install upstream icon (Closes: #738090) (LP: #/922847) * Replace fonts-dejavu-core by fonts-jura * Add dependency on libsdl-mixer1.2-dev * Provide virtual package zatackax * Copyright review Checksums-Sha1: 56430251dc13f2b4d47759f3d707bc39e383e719 2000 zatacka_1.1.0-1.dsc 35d09252d4ffa7aab10c65b27e4d69c7f764d57c 3835877 zatacka_1.1.0.orig.tar.gz b927dbc34d2369151b4784c1d8b3ed7fb23826c5 14088 zatacka_1.1.0-1.debian.tar.xz 1999b64c9d987a408c64d5c1d684cb193a5254da 65280 zatacka-dbgsym_1.1.0-1_amd64.deb ad1ae91b12ee6c81ada0fb9c752428bc73cbd16e 13257 zatacka_1.1.0-1_amd64.buildinfo aaefd945abebaf2ff9ffae1da39dab5e3f6463c8 3381060 zatacka_1.1.0-1_amd64.deb Checksums-Sha256: e2f9acfa8619c6805dc46317b85ba68ba05f8ae5728fd71919675719bf77833c 2000 zatacka_1.1.0-1.dsc 9339b75a76c9a6cb97d80e79a7108989d504b0b43eecad3ba2362606d6e5e41d 3835877 zatacka_1.1.0.orig.tar.gz d153e7dd78849e1ffd6895b2434cea7d0e5aab51d1e48898a84b29e8b20367ec 14088 zatacka_1.1.0-1.debian.tar.xz caa100ba6fa13f47e774b16f32a8e158b51c22c6145d424de76e572c5f9a56b2 65280 zatacka-dbgsym_1.1.0-1_amd64.deb 3c8a4505150879a4cba3bb0e6ca07c59b781e8443297bb45d3b27576b165650b 13257 zatacka_1.1.0-1_amd64.buildinfo
Bug#908387: marked as done (zatacka: Crashes with segmentation fault on launch)
Your message dated Sun, 31 Mar 2024 22:15:06 + with message-id and subject line Bug#908387: fixed in zatacka 1.1.0-1 has caused the Debian Bug report #908387, regarding zatacka: Crashes with segmentation fault on launch 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.) -- 908387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zatacka Version: 0.1.8-5+b3 Severity: important Dear Maintainer, I'm using Zatacka 0.1.8-5+b3 on Debian stable. On launch, Zatacka crashes printing "Segmentation fault" on terminal. $ zatacka Segmentation fault -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages zatacka depends on: ii libc62.24-11+deb9u3 ii libsdl-image1.2 1.2.12-5+deb9u1 ii libsdl-ttf2.0-0 2.0.11-3+b1 ii libsdl1.2debian 1.2.15+dfsg1-4 ii libstdc++6 6.3.0-18+deb9u1 zatacka recommends no packages. zatacka suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: zatacka Source-Version: 1.1.0-1 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of zatacka, 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 908...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated zatacka package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 31 Mar 2024 23:04:51 +0200 Source: zatacka Binary: zatacka zatacka-dbgsym Architecture: source amd64 Version: 1.1.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Alexandre Detiste Description: zatacka- arcade multiplayer game like nibbles Closes: 626767 738090 904633 908387 908572 964789 Changes: zatacka (1.1.0-1) unstable; urgency=medium . * Adopt package (Closes: #964789) * Update watch file for new maintainer (Closes: #904633, #908387, #908572, #626767) (LP: #246734, #1565485) * Remove .desktop file, upstream provides one now * Install upstream icon (Closes: #738090) (LP: #/922847) * Replace fonts-dejavu-core by fonts-jura * Add dependency on libsdl-mixer1.2-dev * Provide virtual package zatackax * Copyright review Checksums-Sha1: 56430251dc13f2b4d47759f3d707bc39e383e719 2000 zatacka_1.1.0-1.dsc 35d09252d4ffa7aab10c65b27e4d69c7f764d57c 3835877 zatacka_1.1.0.orig.tar.gz b927dbc34d2369151b4784c1d8b3ed7fb23826c5 14088 zatacka_1.1.0-1.debian.tar.xz 1999b64c9d987a408c64d5c1d684cb193a5254da 65280 zatacka-dbgsym_1.1.0-1_amd64.deb ad1ae91b12ee6c81ada0fb9c752428bc73cbd16e 13257 zatacka_1.1.0-1_amd64.buildinfo aaefd945abebaf2ff9ffae1da39dab5e3f6463c8 3381060 zatacka_1.1.0-1_amd64.deb Checksums-Sha256: e2f9acfa8619c6805dc46317b85ba68ba05f8ae5728fd71919675719bf77833c 2000 zatacka_1.1.0-1.dsc 9339b75a76c9a6cb97d80e79a7108989d504b0b43eecad3ba2362606d6e5e41d 3835877 zatacka_1.1.0.orig.tar.gz d153e7dd78849e1ffd6895b2434cea7d0e5aab51d1e48898a84b29e8b20367ec 14088 zatacka_1.1.0-1.debian.tar.xz caa100ba6fa13f47e774b16f32a8e158b51c22c6145d424de76e572c5f9a56b2 65280 zatacka-dbgsym_1.1.0-1_amd64.deb 3c8a4505150879a4cba3bb0e6ca07c59b781e8443297bb45d3b27576b165650b 13257 zatacka_1.1.0-1_amd64.buildinfo 447d502069ab296efe5ae3af7b31e3eb41967b09b41302199e30a19c113c737b 3381060 zatacka_1.1.0-1_amd64.deb Files: 7752ec641a10a1f67efc416779d0e70d 2000 games optional zatacka_1.1.0-1.dsc 578609b93d2158ac3ef40e8475149946 3835877 games optional zatacka_1.1.0.orig.tar.gz 8b16978c46f98042e47bb60409991478 14088 games optional zatacka_1.1.0-1.debian.tar.xz b303cec41b136890f9ac16920c2abab5 65280 debug optional zatacka-dbgsym_1.1.0-1_amd64.deb be3ef1608a719305fbd5b494c841d92c 13257 games optional zatacka_1.1.0-1_amd64.buildinfo
Bug#738090: marked as done (zatacka: please provide icon for desktop file)
Your message dated Sun, 31 Mar 2024 22:15:06 + with message-id and subject line Bug#738090: fixed in zatacka 1.1.0-1 has caused the Debian Bug report #738090, regarding zatacka: please provide icon for desktop file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 738090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zatacka Version: 0.1.8-3 Severity: wishlist User: pkg-games-de...@lists.alioth.debian.org Usertags: desktop-integration goals not-gamesteam Dear maintainer, currently zatacka does not supply desktop and menu icons. Hence the game is not well integrated into the user's desktop environment. Please consider helping to improve the desktop integration of games in Debian. https://wiki.debian.org/Games/JessieReleaseGoal Regards, Markus signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: zatacka Source-Version: 1.1.0-1 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of zatacka, 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 738...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated zatacka package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 31 Mar 2024 23:04:51 +0200 Source: zatacka Binary: zatacka zatacka-dbgsym Architecture: source amd64 Version: 1.1.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Alexandre Detiste Description: zatacka- arcade multiplayer game like nibbles Closes: 626767 738090 904633 908387 908572 964789 Changes: zatacka (1.1.0-1) unstable; urgency=medium . * Adopt package (Closes: #964789) * Update watch file for new maintainer (Closes: #904633, #908387, #908572, #626767) (LP: #246734, #1565485) * Remove .desktop file, upstream provides one now * Install upstream icon (Closes: #738090) (LP: #/922847) * Replace fonts-dejavu-core by fonts-jura * Add dependency on libsdl-mixer1.2-dev * Provide virtual package zatackax * Copyright review Checksums-Sha1: 56430251dc13f2b4d47759f3d707bc39e383e719 2000 zatacka_1.1.0-1.dsc 35d09252d4ffa7aab10c65b27e4d69c7f764d57c 3835877 zatacka_1.1.0.orig.tar.gz b927dbc34d2369151b4784c1d8b3ed7fb23826c5 14088 zatacka_1.1.0-1.debian.tar.xz 1999b64c9d987a408c64d5c1d684cb193a5254da 65280 zatacka-dbgsym_1.1.0-1_amd64.deb ad1ae91b12ee6c81ada0fb9c752428bc73cbd16e 13257 zatacka_1.1.0-1_amd64.buildinfo aaefd945abebaf2ff9ffae1da39dab5e3f6463c8 3381060 zatacka_1.1.0-1_amd64.deb Checksums-Sha256: e2f9acfa8619c6805dc46317b85ba68ba05f8ae5728fd71919675719bf77833c 2000 zatacka_1.1.0-1.dsc 9339b75a76c9a6cb97d80e79a7108989d504b0b43eecad3ba2362606d6e5e41d 3835877 zatacka_1.1.0.orig.tar.gz d153e7dd78849e1ffd6895b2434cea7d0e5aab51d1e48898a84b29e8b20367ec 14088 zatacka_1.1.0-1.debian.tar.xz caa100ba6fa13f47e774b16f32a8e158b51c22c6145d424de76e572c5f9a56b2 65280 zatacka-dbgsym_1.1.0-1_amd64.deb 3c8a4505150879a4cba3bb0e6ca07c59b781e8443297bb45d3b27576b165650b 13257 zatacka_1.1.0-1_amd64.buildinfo 447d502069ab296efe5ae3af7b31e3eb41967b09b41302199e30a19c113c737b 3381060 zatacka_1.1.0-1_amd64.deb Files: 7752ec641a10a1f67efc416779d0e70d 2000 games optional zatacka_1.1.0-1.dsc 578609b93d2158ac3ef40e8475149946 3835877 games optional zatacka_1.1.0.orig.tar.gz 8b16978c46f98042e47bb60409991478 14088 games optional zatacka_1.1.0-1.debian.tar.xz b303cec41b136890f9ac16920c2abab5 65280 debug optional zatacka-dbgsym_1.1.0-1_amd64.deb be3ef1608a719305fbd5b494c841d92c 13257 games optional zatacka_1.1.0-1_amd64.buildinfo 0464f5c21fcda728d13408b1ed402b69 3381060 games optional zatacka_1.1.0-1_amd64.deb -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmYJ0woRHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBodihAAvedCqs+tjzE/TTbabm/4QFJtrfTbW3Fq IO/6hR9kMg26a8any1CUOBTLwiUtUYsrIG36+xMXLtknvYFslztLzEpNyJ8qcTts PLLGS6cDfIGUn/4QHTYYjUzr3b+/8zFNQcTqkOqJmRzFTn+qDbgxDl5Upbu3xabY pFH/6fyVlvpeQyfaatqc00Tk6d8U+wY8JoUTRgDwMzMD1bdhsaqO0K581xM2A7Gw
Bug#626767: marked as done (zatacka: window manager close button does not work)
Your message dated Sun, 31 Mar 2024 22:15:06 + with message-id and subject line Bug#626767: fixed in zatacka 1.1.0-1 has caused the Debian Bug report #626767, regarding zatacka: window manager close button does not work 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.) -- 626767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zatacka Version: 0.1.8-2 Severity: normal I cannot close zatacka via the window manager close button. -- System Information: Debian Release: wheezy/sid APT prefers experimental APT policy: (900, 'experimental'), (800, 'unstable'), (700, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-rc7-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages zatacka depends on: ii libc62.13-4 Embedded GNU C Library: Shared lib ii libgcc1 1:4.6.0-7 GCC support library ii libsdl-image1.2 1.2.10-2+b2 image loading library for Simple D ii libsdl-ttf2.0-0 2.0.9-1 ttf library for Simple DirectMedia ii libsdl1.2debian 1.2.14-6.3 Simple DirectMedia Layer ii libstdc++6 4.6.0-7 The GNU Standard C++ Library v3 -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: zatacka Source-Version: 1.1.0-1 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of zatacka, 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 626...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated zatacka package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 31 Mar 2024 23:04:51 +0200 Source: zatacka Binary: zatacka zatacka-dbgsym Architecture: source amd64 Version: 1.1.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Alexandre Detiste Description: zatacka- arcade multiplayer game like nibbles Closes: 626767 738090 904633 908387 908572 964789 Changes: zatacka (1.1.0-1) unstable; urgency=medium . * Adopt package (Closes: #964789) * Update watch file for new maintainer (Closes: #904633, #908387, #908572, #626767) (LP: #246734, #1565485) * Remove .desktop file, upstream provides one now * Install upstream icon (Closes: #738090) (LP: #/922847) * Replace fonts-dejavu-core by fonts-jura * Add dependency on libsdl-mixer1.2-dev * Provide virtual package zatackax * Copyright review Checksums-Sha1: 56430251dc13f2b4d47759f3d707bc39e383e719 2000 zatacka_1.1.0-1.dsc 35d09252d4ffa7aab10c65b27e4d69c7f764d57c 3835877 zatacka_1.1.0.orig.tar.gz b927dbc34d2369151b4784c1d8b3ed7fb23826c5 14088 zatacka_1.1.0-1.debian.tar.xz 1999b64c9d987a408c64d5c1d684cb193a5254da 65280 zatacka-dbgsym_1.1.0-1_amd64.deb ad1ae91b12ee6c81ada0fb9c752428bc73cbd16e 13257 zatacka_1.1.0-1_amd64.buildinfo aaefd945abebaf2ff9ffae1da39dab5e3f6463c8 3381060 zatacka_1.1.0-1_amd64.deb Checksums-Sha256: e2f9acfa8619c6805dc46317b85ba68ba05f8ae5728fd71919675719bf77833c 2000 zatacka_1.1.0-1.dsc 9339b75a76c9a6cb97d80e79a7108989d504b0b43eecad3ba2362606d6e5e41d 3835877 zatacka_1.1.0.orig.tar.gz d153e7dd78849e1ffd6895b2434cea7d0e5aab51d1e48898a84b29e8b20367ec 14088 zatacka_1.1.0-1.debian.tar.xz caa100ba6fa13f47e774b16f32a8e158b51c22c6145d424de76e572c5f9a56b2 65280 zatacka-dbgsym_1.1.0-1_amd64.deb 3c8a4505150879a4cba3bb0e6ca07c59b781e8443297bb45d3b27576b165650b 13257 zatacka_1.1.0-1_amd64.buildinfo 447d502069ab296efe5ae3af7b31e3eb41967b09b41302199e30a19c113c737b 3381060 zatacka_1.1.0-1_amd64.deb Files: 7752ec641a10a1f67efc416779d0e70d 2000 games optional zatacka_1.1.0-1.dsc 578609b93d2158ac3ef40e8475149946 3835877 games optional zatacka_1.1.0.orig.tar.gz 8b16978c46f98042e47bb60409991478 14088 games optional zatacka_1.1.0-1.debian.tar.xz b303cec41b136890f9ac16920c2abab5 65280 debug optional
Bug#1067626: marked as done (FTBFS: fopen_fails test failed)
Your message dated Sun, 31 Mar 2024 22:09:52 + with message-id and subject line Bug#1067626: fixed in pacemaker 2.1.7-1 has caused the Debian Bug report #1067626, regarding FTBFS: fopen_fails test failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1067626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067626 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pacemaker Version: 2.1.6-5 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=pacemaker=armel=2.1.6-5=1711156223=0 PASS: pcmk__output_new_test 1 - empty_formatters PASS: pcmk__output_new_test 2 - invalid_params PASS: pcmk__output_new_test 3 - no_such_format PASS: pcmk__output_new_test 4 - create_fails PASS: pcmk__output_new_test 5 - init_fails FAIL: pcmk__output_new_test 6 - fopen_fails PASS: pcmk__output_new_test 7 - everything_succeeds PASS: pcmk__output_new_test 8 - no_fmt_name_given ERROR: pcmk__output_new_test - exited with status 1 -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 --- Source: pacemaker Source-Version: 2.1.7-1 Done: Ferenc Wágner We believe that the bug you reported is fixed in the latest version of pacemaker, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ferenc Wágner (supplier of updated pacemaker package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 31 Mar 2024 22:36:16 +0200 Source: pacemaker Architecture: source Version: 2.1.7-1 Distribution: unstable Urgency: medium Maintainer: Debian HA Maintainers Changed-By: Ferenc Wágner Closes: 1067626 Changes: pacemaker (2.1.7-1) unstable; urgency=medium . * [09de5bf] New upstream release (2.1.7) (Closes: #1067626) * [ad97704] Refresh our patches * [e71f255] Update symbols files (all removed symbols were internal) * [13bce35] The cts Python directory is not installed anymore. Upstream migrated all of its contents into the _cts module of the pacemaker Python package (see commit 1fdea434). Checksums-Sha1: 6d54dbf79e559888cf3deeba7d7a41dc9f57c2ac 3646 pacemaker_2.1.7-1.dsc 767c5c564a300ec096884ccc7dc469a0bab6e9d7 6056266 pacemaker_2.1.7.orig.tar.gz b3d0a89787d17d2e06ba1ea19cac5a2d4443c0d5 51612 pacemaker_2.1.7-1.debian.tar.xz 0ac5e0c78ec1b3187a5c4dc11df9426921869bc1 25112 pacemaker_2.1.7-1_amd64.buildinfo Checksums-Sha256: 29e7ca35ebe8a0b80c077a8ff0c7c764976a996e0ba3a07a1fe8dd4ba6373124 3646 pacemaker_2.1.7-1.dsc 17e18ec4d7ab138df641a22b812026c6f70cb7e2f7db6b3ded098de81b0b135a 6056266 pacemaker_2.1.7.orig.tar.gz 2adda8de501e043ea5c5ab75c5f2e0388cf5a0c019e804dc14faebc0b8c2b844 51612 pacemaker_2.1.7-1.debian.tar.xz 425ea8aac6cd55367c39038b0fc3277a2a15bde09c99f06855a831e4628c27bf 25112 pacemaker_2.1.7-1_amd64.buildinfo Files: 33bb3d9bd3103a7c41988d960f061b22 3646 admin optional pacemaker_2.1.7-1.dsc f91bd46791c8b302e82e8eb608770238 6056266 admin optional pacemaker_2.1.7.orig.tar.gz 2f24c3185cc8999458243d5ca3cf5b49 51612 admin optional pacemaker_2.1.7-1.debian.tar.xz 8b0bb1b234ce7e8bb7441483b8538a45 25112 admin optional pacemaker_2.1.7-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEwddEx0RNIUL7eugtOsj3Fkd+2yMFAmYJ1KMACgkQOsj3Fkd+ 2yOWoQ/+I5jCqxTKkDxGxY+mytpIZcKDMQiyGANzSe9JeKzgxC9DmmBcZCmkP0A3 uIWE0SaN1KXSR5MeG7NMhH4Qp7qIhSxo1iGjLHRzHhTowMxM6aryzPd/QXG3Sag9 Lj8Anmxecs6slv88XKAfmC4TupqpaGdnh1oCn4x09H607RWsZoxzo1oVmgCMkx8L pBnrtuR0MOxFXsgM+GvX1NLDmigpyGmKfoDGgaXchDAT0La3w5Ogo74v5Gqy1L7I
Bug#1066722: marked as done (xracer: FTBFS: spatscal.c:102:17: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declaration])
Your message dated Sun, 31 Mar 2024 21:44:30 + with message-id and subject line Bug#1066722: fixed in xracer 0.96.9.1-12 has caused the Debian Bug report #1066722, regarding xracer: FTBFS: spatscal.c:102:17: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declaration] 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.) -- 1066722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xracer Version: 0.96.9.1-11 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include -Wdate-time > -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -O3 -Wall -Wpointer-arith -Wmissing-prototypes -Wmissing-declarations > -Wcast-align -Wwrite-strings -c -o store.o store.c > mpeg2dec.c:215:12: warning: ‘Decode_Bitstream’ defined but not used > [-Wunused-function] > 215 | static int Decode_Bitstream(struct mpeg2obj *m) > |^~~~ > spatscal.c: In function ‘Read_Lower_Layer_Component_Framewise’: > spatscal.c:102:17: error: implicit declaration of function ‘exit’ > [-Werror=implicit-function-declaration] > 102 | if (fd==NULL) exit(-1); > | ^~~~ > spatscal.c:12:1: note: include ‘’ or provide a declaration of ‘exit’ >11 | #include "global.h" > +++ |+#include >12 | > spatscal.c:102:17: warning: incompatible implicit declaration of built-in > function ‘exit’ [-Wbuiltin-declaration-mismatch] > 102 | if (fd==NULL) exit(-1); > | ^~~~ > spatscal.c:102:17: note: include ‘’ or provide a declaration of > ‘exit’ > spatscal.c: In function ‘Read_Lower_Layer_Component_Fieldwise’: > spatscal.c:130:17: warning: incompatible implicit declaration of built-in > function ‘exit’ [-Wbuiltin-declaration-mismatch] > 130 | if (fd==NULL) exit(-1); > | ^~~~ > spatscal.c:130:17: note: include ‘’ or provide a declaration of > ‘exit’ > spatscal.c:140:19: warning: incompatible implicit declaration of built-in > function ‘exit’ [-Wbuiltin-declaration-mismatch] > 140 | if (fd==NULL) exit(-1); > | ^~~~ > spatscal.c:140:19: note: include ‘’ or provide a declaration of > ‘exit’ > store.c: In function ‘_mpeg2Write_Frame’: > store.c:158:15: error: implicit declaration of function ‘memcpy’ > [-Werror=implicit-function-declaration] > 158 | memcpy (p, row_start, row_size); > | ^~ > store.c:37:1: note: include ‘’ or provide a declaration of ‘memcpy’ >36 | #include "global.h" > +++ |+#include >37 | > store.c:158:15: warning: incompatible implicit declaration of built-in > function ‘memcpy’ [-Wbuiltin-declaration-mismatch] > 158 | memcpy (p, row_start, row_size); > | ^~ > store.c:158:15: note: include ‘’ or provide a declaration of > ‘memcpy’ > store.c:172:11: error: implicit declaration of function ‘memset’ > [-Werror=implicit-function-declaration] > 172 | memset (p, 0, row_size); > | ^~ > store.c:172:11: note: include ‘’ or provide a declaration of > ‘memset’ > store.c:172:11: warning: incompatible implicit declaration of built-in > function ‘memset’ [-Wbuiltin-declaration-mismatch] > store.c:172:11: note: include ‘’ or provide a declaration of > ‘memset’ > store.c:231:15: warning: incompatible implicit declaration of built-in > function ‘memcpy’ [-Wbuiltin-declaration-mismatch] > 231 | memcpy (p, row_start, row_size); > | ^~ > store.c:231:15: note: include ‘’ or provide a declaration of > ‘memcpy’ > store.c:245:11: warning: incompatible implicit declaration of built-in > function ‘memset’ [-Wbuiltin-declaration-mismatch] > 245 | memset (p, 0, row_size); > | ^~ > store.c:245:11: note: include ‘’ or provide a declaration of > ‘memset’ > gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include
Bug#1057910: marked as done (apticron: use systemd.pc to place systemd system units)
Your message dated Sun, 31 Mar 2024 21:34:27 +
with message-id
and subject line Bug#1057910: fixed in apticron 1.2.9
has caused the Debian Bug report #1057910,
regarding apticron: use systemd.pc to place systemd system units
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.)
--
1057910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apticron
Version: 1.2.8
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2
Dear Maintainer,
your package installs systemd system units, currently into /lib.
These files need to be moved to /usr/lib as part of Debian's usr-merge
effort [1].
Attached you will find a patch to delegate the exact placement of
these files to systemd.pc (using pkg-config). This immediately works
in unstable, placing the files into /usr/lib.
It also works for backports to older releases, where it will continue
install into /lib.
If during the trixie cycle your package will undergo structural
changes or any other file moves, please see the wiki and upload
to experimental first when these changes are done.
Later during the trixie cycle I expect this bug class to raise in
priority.
Thank you for considering,
Chris
[1] https://wiki.debian.org/UsrMerge
>From 637ac22e5191448b93fcbb6952145bd70cdf4f18 Mon Sep 17 00:00:00 2001
From: Chris Hofstaedtler
Date: Sun, 10 Dec 2023 16:05:37 +0100
Subject: Use systemd.pc to place systemd system units
---
debian/apticron-systemd.install | 4 ++--
debian/control | 2 +-
debian/rules| 1 +
3 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/debian/apticron-systemd.install b/debian/apticron-systemd.install
index 475d96a..dcd293d 100755
--- a/debian/apticron-systemd.install
+++ b/debian/apticron-systemd.install
@@ -2,5 +2,5 @@
debian/readme_conf => etc/apticron/README
apticron => usr/sbin/apticron
apticron.conf => usr/lib/apticron/apticron.conf
-apticron.service => lib/systemd/system/apticron.service
-apticron.timer => lib/systemd/system/apticron.timer
+apticron.service ${env:deb_systemdsystemunitdir}/
+apticron.timer ${env:deb_systemdsystemunitdir}/
diff --git a/debian/control b/debian/control
index 3f3416b..ce5d70e 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: apticron
Section: admin
Priority: optional
Maintainer: Tiago Bortoletto Vaz
-Build-Depends: po-debconf, debhelper-compat (= 13), dh-exec
+Build-Depends: po-debconf, debhelper-compat (= 13), dh-exec, pkgconf, systemd-dev
Standards-Version: 4.6.2
Vcs-Browser: https://salsa.debian.org/debian/apticron
Vcs-Git: https://salsa.debian.org/debian/apticron.git
diff --git a/debian/rules b/debian/rules
index 2d33f6a..0f38519 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,4 +1,5 @@
#!/usr/bin/make -f
+export deb_systemdsystemunitdir = $(shell pkg-config --variable=systemdsystemunitdir systemd | sed s,^/,,)
%:
dh $@
--
2.39.2
--- End Message ---
--- Begin Message ---
Source: apticron
Source-Version: 1.2.9
Done: Tiago Bortoletto Vaz
We believe that the bug you reported is fixed in the latest version of
apticron, 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 1057...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Tiago Bortoletto Vaz (supplier of updated apticron package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 31 Mar 2024 16:33:29 -0400
Source: apticron
Architecture: source
Version: 1.2.9
Distribution: unstable
Urgency: medium
Maintainer: Tiago Bortoletto Vaz
Changed-By: Tiago Bortoletto Vaz
Closes: 1057910
Changes:
apticron (1.2.9) unstable; urgency=medium
.
* Use systemd.pc to place systemd system units (thanks to Chris
Hofstaedtler). Closes: #1057910
Checksums-Sha1:
aabc53ec0041ecef9b66917fee6ca38f56019b61 1646 apticron_1.2.9.dsc
e681ffad6b9c6a88a83cd232dc52eff1c6f913bd 20776 apticron_1.2.9.tar.xz
e7bb29b66679a1a353923b80bd54f8492b9a68fa 6729 apticron_1.2.9_amd64.buildinfo
Checksums-Sha256:
14aff683a99267f430d5a7bb2274a964264556976c17ae1266c89e118d96c92f 1646
apticron_1.2.9.dsc
Bug#1066527: marked as done (xsystem35: FTBFS: sactcg.c:211:27: error: implicit declaration of function ‘sjis2euc’ [-Werror=implicit-function-declaration])
Your message dated Sun, 31 Mar 2024 21:10:35 + with message-id and subject line Bug#1066527: fixed in xsystem35 1.7.3-pre5-11 has caused the Debian Bug report #1066527, regarding xsystem35: FTBFS: sactcg.c:211:27: error: implicit declaration of function ‘sjis2euc’ [-Werror=implicit-function-declaration] 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.) -- 1066527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xsystem35 Version: 1.7.3-pre5-10 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I../.. -I../.. -I../.. -I../../src -I../../src -I../../libltdl > -I../../libltdl -I../../modules/lib -I../../modules/lib > -I../../modules/NIGHTDLL -I../../modules/NIGHTDLL -Wdate-time > -D_FORTIFY_SOURCE=2 -g -Wall -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c -o sprite_eupdate.lo > sprite_eupdate.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. > -I../../src -I../../src -I../../libltdl -I../../libltdl -I../../modules/lib > -I../../modules/lib -I../../modules/NIGHTDLL -I../../modules/NIGHTDLL > -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c NIGHTDLL.c -fPIC -DPIC -o > .libs/NIGHTDLL.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. > -I../../src -I../../src -I../../libltdl -I../../libltdl -I../../modules/lib > -I../../modules/lib -I../../modules/NIGHTDLL -I../../modules/NIGHTDLL > -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c nt_scenario.c -fPIC -DPIC -o > .libs/nt_scenario.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. > -I../../src -I../../src -I../../libltdl -I../../libltdl -I../../modules/lib > -I../../modules/lib -I../../modules/NIGHTDLL -I../../modules/NIGHTDLL > -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c sprite_update.c -fPIC -DPIC -o > .libs/sprite_update.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. > -I../../src -I../../src -I../../libltdl -I../../libltdl -I../../modules/lib > -I../../modules/lib -I../../modules/NIGHTDLL -I../../modules/NIGHTDLL > -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c sprite_eupdate.c -fPIC -DPIC -o > .libs/sprite_eupdate.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. > -I../../src -I../../src -I../../libltdl -I../../libltdl -I../../modules/lib > -I../../modules/lib -I../../modules/NIGHTDLL -I../../modules/NIGHTDLL > -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c sactstring.c -fPIC -DPIC -o > .libs/sactstring.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. > -I../../src -I../../src -I../../libltdl
Bug#1065514: marked as done (qpdfview FTCBFS: fails running lrelease and runs the build arch qmake6)
Your message dated Sun, 31 Mar 2024 21:10:21 + with message-id and subject line Bug#1065514: fixed in qpdfview 0.5.0+ds-5 has caused the Debian Bug report #1065514, regarding qpdfview FTCBFS: fails running lrelease and runs the build arch qmake6 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.) -- 1065514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qpdfview Version: 0.5.0+ds-4 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs qpdfview fails to cross build from source. The immediate failure is running lrelease, which requires a build dependency on qmake6:native. While at it, I also enabled the use of the qmake6 build system that was recently added to debhelper. I note that this does not make a cross build succeed as it fails to locate a working moc. I think this is a problem with the toolchain rather than qpdfview. Helmut diff --minimal -Nru qpdfview-0.5.0+ds/debian/changelog qpdfview-0.5.0+ds/debian/changelog --- qpdfview-0.5.0+ds/debian/changelog 2024-01-19 21:28:53.0 +0100 +++ qpdfview-0.5.0+ds/debian/changelog 2024-03-05 18:08:04.0 +0100 @@ -1,3 +1,11 @@ +qpdfview (0.5.0+ds-4.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Improve cross building: Depend on qmake6:native and use qmake6 +buildsystem. (Closes: #-1) + + -- Helmut Grohne Tue, 05 Mar 2024 18:08:04 +0100 + qpdfview (0.5.0+ds-4) unstable; urgency=medium * d/control, rules: build using QT6. diff --minimal -Nru qpdfview-0.5.0+ds/debian/control qpdfview-0.5.0+ds/debian/control --- qpdfview-0.5.0+ds/debian/control2024-01-19 21:22:25.0 +0100 +++ qpdfview-0.5.0+ds/debian/control2024-03-05 18:08:04.0 +0100 @@ -3,6 +3,7 @@ Priority: optional Maintainer: Louis-Philippe Véronneau Build-Depends: + debhelper (>= 13.11.9~), debhelper-compat (= 13), libcups2-dev, libdjvulibre-dev, @@ -14,6 +15,7 @@ libsynctex-dev, pkg-config, qmake6, + qmake6:native, qt6-base-dev, qt6-tools-dev-tools, zlib1g-dev, diff --minimal -Nru qpdfview-0.5.0+ds/debian/rules qpdfview-0.5.0+ds/debian/rules --- qpdfview-0.5.0+ds/debian/rules 2024-01-19 21:28:45.0 +0100 +++ qpdfview-0.5.0+ds/debian/rules 2024-03-05 18:07:43.0 +0100 @@ -6,13 +6,11 @@ export QT_SELECT := 6 %: - dh $@ --buildsystem=qmake + dh $@ --buildsystem=qmake6 override_dh_auto_configure: /usr/lib/qt6/bin/lrelease qpdfview.pro - ln -s /usr/bin/qmake6 ./qmake - PATH=`pwd`:$(PATH) dh_auto_configure --buildsystem=qmake -- \ - DEFINES+="_FILE_OFFSET_BITS=64" qpdfview.pro + dh_auto_configure -- DEFINES+="_FILE_OFFSET_BITS=64" qpdfview.pro override_dh_installchangelogs: dh_installchangelogs CHANGES --- End Message --- --- Begin Message --- Source: qpdfview Source-Version: 0.5.0+ds-5 Done: Louis-Philippe Véronneau We believe that the bug you reported is fixed in the latest version of qpdfview, 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 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Louis-Philippe Véronneau (supplier of updated qpdfview package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 31 Mar 2024 16:10:56 -0400 Source: qpdfview Architecture: source Version: 0.5.0+ds-5 Distribution: unstable Urgency: medium Maintainer: Louis-Philippe Véronneau Changed-By: Louis-Philippe Véronneau Closes: 1065514 Changes: qpdfview (0.5.0+ds-5) unstable; urgency=medium . [ Helmut Grohne ] * Improve cross building: Depend on qmake6:native and use qmake6 buildsystem. (Closes: #1065514) . [ Louis-Philippe Véronneau ] * d/control: replace obsolete pkg-config package by new pkgconf. Checksums-Sha1: d5f2d2b23403f9bee53725101457456edfd40671 1802 qpdfview_0.5.0+ds-5.dsc 6d99413219275a23daa1a5d0247bc099f929b7ac 9268 qpdfview_0.5.0+ds-5.debian.tar.xz 353494f1214711c10e84761bd1e34ddc0a097e45 15385 qpdfview_0.5.0+ds-5_amd64.buildinfo Checksums-Sha256: 2e11f4bdc05d2c63f9dca5c04c1bffaeb5d58b51bb110c99fb5d6d541fa5b2d4 1802
Bug#1064677: marked as done (puppetdb: FTBFS: make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1)
Your message dated Sun, 31 Mar 2024 21:10:09 + with message-id and subject line Bug#1064677: fixed in puppetdb 8.4.1-1 has caused the Debian Bug report #1064677, regarding puppetdb: FTBFS: make[1]: *** [debian/rules:26: override_dh_auto_test] Error 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.) -- 1064677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064677 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: puppetdb Version: 7.12.1-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240224 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 '/<>' > export pg_ver=$(/usr/share/postgresql-common/supported-versions --installed); > \ > export PATH=$PATH:/<>/debian/bin && \ > ./ext/bin/with-pdbbox \ > --box $(mktemp -d "core-test-XX")/box \ > --pgbin /usr/lib/postgresql/$pg_ver/bin \ > --pgport 5432 \ > -- lein test > ++ printf 'rm -rf %q' core-test-sruDNB/box > + trap 'rm -rf core-test-sruDNB/box' EXIT > + export PDBBOX=core-test-sruDNB/box > + PDBBOX=core-test-sruDNB/box > + /<>/ext/bin/pdbbox-init --sandbox core-test-sruDNB/box --pgbin > /usr/lib/postgresql/16/bin --pgport 5432 --bind-addr ip6-localhost > --bind-addr localhost > The files belonging to this database system will be owned by user "user42". > This user must also own the server process. > > The database cluster will be initialized with locale "C". > The default text search configuration will be set to "english". > > Data page checksums are disabled. > > creating directory /<>/core-test-sruDNB/box/pg/data ... ok > creating subdirectories ... ok > selecting dynamic shared memory implementation ... posix > selecting default max_connections ... 100 > selecting default shared_buffers ... 128MB > selecting default time zone ... Etc/UTC > creating configuration files ... ok > running bootstrap script ... ok > performing post-bootstrap initialization ... ok > syncing data to disk ... ok > > Success. You can now start the database server using: > > /usr/lib/postgresql/16/bin/pg_ctl -D > /<>/core-test-sruDNB/box/pg/data -l logfile start > > waiting for server to start2024-02-24 22:51:08.895 UTC [1237302] LOG: > starting PostgreSQL 16.2 (Debian 16.2-1) on x86_64-pc-linux-gnu, compiled by > gcc (Debian 13.2.0-13) 13.2.0, 64-bit > 2024-02-24 22:51:08.895 UTC [1237302] LOG: listening on IPv4 address > "127.0.0.1", port 5432 > 2024-02-24 22:51:08.897 UTC [1237302] LOG: could not bind IPv4 address > "127.0.0.1": Address already in use > 2024-02-24 22:51:08.897 UTC [1237302] HINT: Is another postmaster already > running on port 5432? If not, wait a few seconds and retry. > 2024-02-24 22:51:08.897 UTC [1237302] LOG: could not bind IPv4 address > "127.0.0.1": Address already in use > 2024-02-24 22:51:08.897 UTC [1237302] HINT: Is another postmaster already > running on port 5432? If not, wait a few seconds and retry. > 2024-02-24 22:51:08.897 UTC [1237302] WARNING: could not create listen > socket for "localhost" > 2024-02-24 22:51:08.905 UTC [1237302] LOG: listening on Unix socket > "sock/.s.PGSQL.5432" > 2024-02-24 22:51:08.912 UTC [1237305] LOG: database system was shut down at > 2024-02-24 22:51:08 UTC > 2024-02-24 22:51:08.918 UTC [1237302] LOG: database system is ready to > accept connections > done > server started > 32+0 records in > 32+0 records out > 32 bytes copied, 8.6944e-05 s, 368 kB/s > 32+0 records in > 32+0 records out > 32 bytes copied, 0.00111872 s, 28.6 kB/s > 32+0 records in > 32+0 records out > 32 bytes copied, 0.00010492 s, 305 kB/s > 32+0 records in > 32+0 records out > 32 bytes copied, 8.9158e-05 s, 359 kB/s > ALTER ROLE > ALTER ROLE > ALTER ROLE > ALTER ROLE > GRANT ROLE > GRANT ROLE > GRANT ROLE > GRANT ROLE > ALTER ROLE > ALTER ROLE > ALTER ROLE > CREATE EXTENSION > REVOKE > GRANT > ALTER DEFAULT PRIVILEGES > REVOKE > GRANT > GRANT > GRANT > CREATE EXTENSION > REVOKE > GRANT > ALTER DEFAULT PRIVILEGES > REVOKE > GRANT > GRANT > GRANT > Certificate request self-signature ok > subject=C = US, ST = confusion, L = unknown, O = none, CN = pdb.localhost > waiting for server to shut down2024-02-24 22:51:11.154 UTC [1237302] LOG: > received fast shutdown request > 2024-02-24 22:51:11.159 UTC [1237302] LOG: aborting any active transactions > 2024-02-24 22:51:11.162 UTC [1237302] LOG: background worker "logical > replication launcher" (PID 1237308) exited with exit code 1 >
Bug#1057678: marked as done (puppetdb: FTBFS with default Java 21 due to the FIPS clause in project.clj)
Your message dated Sun, 31 Mar 2024 21:10:09 +
with message-id
and subject line Bug#1057678: fixed in puppetdb 8.4.1-1
has caused the Debian Bug report #1057678,
regarding puppetdb: FTBFS with default Java 21 due to the FIPS clause in
project.clj
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.)
--
1057678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: puppetdb
Version: 7.12.1-3
Severity: important
Tags: ftbfs
User: debian-j...@lists.debian.org
Usertags: default-java21
Dear Maintainer,
The package fails to build with default Java 21 due to the :fips clause in
project.clj.
The relevant part of the build log:
-
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
lein pom debian/pom.xml
puppetserver test dependency unconfigured (ignoring)
java.lang.Exception: Error loading /<>/project.clj
at leiningen.core.project$read_raw$fn__8409.invoke (project.clj:1115)
leiningen.core.project$read_raw.invokeStatic (project.clj:1109)
leiningen.core.project$read_raw.invoke (project.clj:1105)
leiningen.core.project$read.invokeStatic (project.clj:1126)
leiningen.core.project$read.invoke (project.clj:1123)
leiningen.core.project$read.invokeStatic (project.clj:1127)
leiningen.core.project$read.invoke (project.clj:1123)
leiningen.core.main$_main$fn__7764.invoke (main.clj:448)
leiningen.core.main$_main.invokeStatic (main.clj:442)
leiningen.core.main$_main.doInvoke (main.clj:439)
clojure.lang.RestFn.applyTo (RestFn.java:137)
clojure.lang.Var.applyTo (Var.java:705)
clojure.core$apply.invokeStatic (core.clj:667)
clojure.main$main_opt.invokeStatic (main.clj:514)
clojure.main$main_opt.invoke (main.clj:510)
clojure.main$main.invokeStatic (main.clj:664)
clojure.main$main.doInvoke (main.clj:616)
clojure.lang.RestFn.applyTo (RestFn.java:137)
clojure.lang.Var.applyTo (Var.java:705)
clojure.main.main (main.java:40)
Caused by: clojure.lang.Compiler$CompilerException: Syntax error macroexpanding
at (/<>/project.clj:139:1).
#:clojure.error{:phase :execution, :line 139, :column 1, :source
"/<>/project.clj"}
at clojure.lang.Compiler.load (Compiler.java:7665)
clojure.lang.Compiler.loadFile (Compiler.java:7591)
clojure.lang.RT$3.invoke (RT.java:327)
leiningen.core.project$read_raw$fn__8409.invoke (project.clj:1113)
leiningen.core.project$read_raw.invokeStatic (project.clj:1109)
leiningen.core.project$read_raw.invoke (project.clj:1105)
leiningen.core.project$read.invokeStatic (project.clj:1126)
leiningen.core.project$read.invoke (project.clj:1123)
leiningen.core.project$read.invokeStatic (project.clj:1127)
leiningen.core.project$read.invoke (project.clj:1123)
leiningen.core.main$_main$fn__7764.invoke (main.clj:448)
leiningen.core.main$_main.invokeStatic (main.clj:442)
leiningen.core.main$_main.doInvoke (main.clj:439)
clojure.lang.RestFn.applyTo (RestFn.java:137)
clojure.lang.Var.applyTo (Var.java:705)
clojure.core$apply.invokeStatic (core.clj:667)
clojure.main$main_opt.invokeStatic (main.clj:514)
clojure.main$main_opt.invoke (main.clj:510)
clojure.main$main.invokeStatic (main.clj:664)
clojure.main$main.doInvoke (main.clj:616)
clojure.lang.RestFn.applyTo (RestFn.java:137)
clojure.lang.Var.applyTo (Var.java:705)
clojure.main.main (main.java:40)
Caused by: clojure.lang.ExceptionInfo: Unsupported major Java version. Expects
8, 11, or 17.
{:major 21, :minor 0}
at leiningen.core.project$eval694.invokeStatic (project.clj:282)
leiningen.core.project$eval694.invoke (project.clj:139)
clojure.lang.Compiler.eval (Compiler.java:7194)
clojure.lang.Compiler.load (Compiler.java:7653)
clojure.lang.Compiler.loadFile (Compiler.java:7591)
clojure.lang.RT$3.invoke (RT.java:327)
leiningen.core.project$read_raw$fn__8409.invoke (project.clj:1113)
leiningen.core.project$read_raw.invokeStatic (project.clj:1109)
leiningen.core.project$read_raw.invoke (project.clj:1105)
leiningen.core.project$read.invokeStatic (project.clj:1126)
leiningen.core.project$read.invoke (project.clj:1123)
leiningen.core.project$read.invokeStatic (project.clj:1127)
leiningen.core.project$read.invoke (project.clj:1123)
leiningen.core.main$_main$fn__7764.invoke (main.clj:448)
leiningen.core.main$_main.invokeStatic (main.clj:442)
leiningen.core.main$_main.doInvoke (main.clj:439)
clojure.lang.RestFn.applyTo (RestFn.java:137)
clojure.lang.Var.applyTo
Bug#1068151: marked as done (Pre-installed vendors list contains broken links)
Your message dated Sun, 31 Mar 2024 20:47:56 + (UTC) with message-id <9489a182-e124-46da-bf5c-b209aae47...@me.com> and subject line has caused the Debian Bug report #1068151, regarding Pre-installed vendors list contains broken links 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.) -- 1068151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: www.debian.org Severity: normal Dear www team, The list of computer vendors that pre-install Debian found at /distrib/pre-installed [1] contains broken links and outdated entries of companies that do not exist anymore. Specifically, here is a list of entries I suggest be *removed*, grouped by region as they appear on the page (note that all of these links are broken in some way): - Canada: JCCSS (Jeremy Carter's Computer Service and Sales) Reason: website is down - Costa Rica: Luis-Alberto Montero Reason: domain was sold to another party - Germany: Sanux.de Reason: website seems to have been lost - Germany: Xtops.DE Reason: website is not functional - Italy: Binario Etico Reason: website down - Mexico: GOLIARDOS TECHNOLOGY S.A. de C.V. Reason: website down - Poland: Scrascom Komputery Poleasingowe Reason: website down - Switzerland: FOX Elektronix - Fux Reason: website down - United States: Psychsoftpc Reason: website down Additionally, here is a list of entries I suggest be *modified*, along with their modification and justification: - India: NaveenGanesan.com Change: Update link to https://naveenganesan.com/naveenlinux Reason: Old link leads to a 404; website owner updated the location of their Debian page from /computing to /naveenlinux - Netherlands: SnaakSystems Changes: 1) Update link to https://novacustom.com 2) Update email to i...@novacustom.com 3) Update 1st line of address to NovaCustom (the rest of the address is still valid) Reason: rebranding (domain was updated from laptopzelfsamenstellen.nl to novacustom.com ) [1] https://www.debian.org/distrib/pre-installed Cheers, Justin--- End Message --- --- Begin Message --- There was a mistake in formatting the bug; please ignore it.--- End Message ---
Bug#1067649: marked as done (Verification page is not accessible from the homepage)
Your message dated Sun, 31 Mar 2024 20:06:55 + with message-id and subject line Re: Bug#1067649: Verification page is not accessible from the homepage has caused the Debian Bug report #1067649, regarding Verification page is not accessible from the homepage 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.) -- 1067649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067649 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: www.debian.org Severity: important X-Debbugs-CC: debian...@lists.debian.org Dear www and CD teams, When the Download link in our homepage was changed to start the iso download right away, the old download page [1] became inaccessible (at least not easily-accessible), making it very hard to find the verification page [2]. I could only find it clicking on "other downloads", then "Download mirrors", and scrolling up until the top of the page, where a menu appears on the right, containing the link to the verify page (I guess many of our users would totally miss it!). My suggestion would be to replace the line "other downloads" with 2 separate links side-by-side: "verify authenticity" | "check all download options" And incorporate the content of the old download page into those 2 targets, the verify and "Getting Debian" page [3] (current target of other downloads). [1] https://www.debian.org/download [2] https://www.debian.org/CD/verify [3] https://www.debian.org/distrib/ Cheers, Tassia. --- End Message --- --- Begin Message --- Thanks, Thomas! I think we can close this bug for now. Link renaming could be done in a later moment, when the website content is being reorganized. Cheers, Tassia.--- End Message ---
Bug#1067121: marked as done (supysonic: flaky autopkgtest including times out)
Your message dated Sun, 31 Mar 2024 19:51:56 + with message-id and subject line Bug#1067121: fixed in supysonic 0.7.6+ds-4 has caused the Debian Bug report #1067121, regarding supysonic: flaky autopkgtest including times out 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.) -- 1067121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067121 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: supysonic Version: 0.7.6+ds-3 Severity: serious User: debian...@lists.debian.org Usertags: flaky timeout Dear maintainer(s), I looked at the results of the autopkgtest of your package. I noticed that it regularly fails. What's worse, sometimes that failure is due to it timing out after 2h47, while a normal run only takes minutes. It seems to hang. From a quick inspection, I didn't see this on amd64, but it happens on arm64, armel, armhf, i386 (failure but no timeout) ppc64el and s390x. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Don't hesitate to reach out if you need help and some more information from our infrastructure. Paul OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: supysonic Source-Version: 0.7.6+ds-4 Done: Louis-Philippe Véronneau We believe that the bug you reported is fixed in the latest version of supysonic, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Louis-Philippe Véronneau (supplier of updated supysonic package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 31 Mar 2024 15:30:11 -0400 Source: supysonic Architecture: source Version: 0.7.6+ds-4 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Louis-Philippe Véronneau Closes: 1067121 Changes: supysonic (0.7.6+ds-4) unstable; urgency=medium . * d/patches: rename 0004_-test_user to 0010 to fix 'number' collision with the other 0004 patch. * d/patches: add 0011 to skip test_move_out, as it's flaky. (Closes: #1067121) Checksums-Sha1: dd40d7c52198d458c77209e35c1d5011ca047d18 1826 supysonic_0.7.6+ds-4.dsc b8cd525a00b5ec1c6ea58a48225e4e47f1eeded7 19888 supysonic_0.7.6+ds-4.debian.tar.xz 76b581a45ed8d67145835ea0fa42aec1a93bf653 8617 supysonic_0.7.6+ds-4_amd64.buildinfo Checksums-Sha256: 9500e1354f80993df8754dc329400d44d50b7d79e6b237be4a2d12c3831fe6ea 1826 supysonic_0.7.6+ds-4.dsc 32f8fab3dc982ee4683b6c9e32deb07d6de924114a5a29ab2a2204b0f6185b33 19888 supysonic_0.7.6+ds-4.debian.tar.xz 19ba963f2c11dcfe429de2b2b76b7fc6df61b70e3079438642af7045bc6e03f2 8617 supysonic_0.7.6+ds-4_amd64.buildinfo Files: bef865a69b25e0d23cf80d6a7b8f0799 1826 sound optional supysonic_0.7.6+ds-4.dsc 761fbdb3d62cba3e5043fff4f58b1c4b 19888 sound optional supysonic_0.7.6+ds-4.debian.tar.xz db96503e705634afb619daffe41cc571 8617 sound optional supysonic_0.7.6+ds-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQTKp0AHB6gWsCAvw830JXpQshz6hQUCZgm7wAAKCRD0JXpQshz6 hYQPAPsEd4HE7rP766mb7IrL2ZasiKnJz+ZCenIMflU2VL3hlAD/R3eceMTUhn8w IuAk7lY+O1aH287qhDkEyUWNNoP06gY= =MAhV -END PGP SIGNATURE- pgpELFlDL2k_j.pgp Description: PGP signature --- End Message ---
Bug#1067947: marked as done (golang-github-stvp-tempredis: please make the build reproducible)
Your message dated Sun, 31 Mar 2024 19:20:17 + with message-id and subject line Bug#1067947: fixed in golang-github-stvp-tempredis 0.0~git20231107.8a695b6-2 has caused the Debian Bug report #1067947, regarding golang-github-stvp-tempredis: please make the build reproducible 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.) -- 1067947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067947 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-stvp-tempredis Version: 0.0~git20231107.8a695b6-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: randomness X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Hi, Whilst working on the Reproducible Builds effort [0], we noticed that golang-github-stvp-tempredis could not be built reproducibly. This is because the package build generates a Redis dump.rdb database during the tests. This (nondeterministic) file is then shipped in the binary package. Patch attached that removes these after running the tests. [0] https://reproducible-builds.org/ Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- a/debian/rules 2024-03-29 10:35:18.997786394 + --- b/debian/rules 2024-03-29 10:55:36.280785041 + @@ -2,3 +2,6 @@ %: dh $@ --buildsystem=golang --with=golang + +execute_after_dh_auto_test: + find obj-* -name dump.rdb -delete --- End Message --- --- Begin Message --- Source: golang-github-stvp-tempredis Source-Version: 0.0~git20231107.8a695b6-2 Done: Sascha Steinbiss We believe that the bug you reported is fixed in the latest version of golang-github-stvp-tempredis, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sascha Steinbiss (supplier of updated golang-github-stvp-tempredis package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 31 Mar 2024 21:05:43 +0200 Source: golang-github-stvp-tempredis Architecture: source Version: 0.0~git20231107.8a695b6-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Sascha Steinbiss Closes: 1067947 Changes: golang-github-stvp-tempredis (0.0~git20231107.8a695b6-2) unstable; urgency=medium . * Stop shipping nondeterministic Redis database file generated during build. Thanks to Chris Lamb for the patch. Closes: #1067947 * Bump Standards-Version. * Switch section to golang. * Bump copyright date for debian/ directory. Checksums-Sha1: 52c3368d2fb78ac1029446e2d4aff61fbffaebcd 2417 golang-github-stvp-tempredis_0.0~git20231107.8a695b6-2.dsc d88a82945dc908933f6dd6cc0003ee85d06e8d17 2572 golang-github-stvp-tempredis_0.0~git20231107.8a695b6-2.debian.tar.xz bcd287da20f9e0be51aca8500c7c6a6e35d41202 6646 golang-github-stvp-tempredis_0.0~git20231107.8a695b6-2_amd64.buildinfo Checksums-Sha256: 6c0a411b1be50ac8e115ff27941f3eed4082724c9808664a211f56187e54dfee 2417 golang-github-stvp-tempredis_0.0~git20231107.8a695b6-2.dsc 7bcc3d6cea3d719e162c02a429f6a2f9c924b27fc5fc8361cbf7ab5f20f4cafe 2572 golang-github-stvp-tempredis_0.0~git20231107.8a695b6-2.debian.tar.xz 6f22798b70129926955d430ef8063463387c88a6f982339fd1f12ded79d58562 6646 golang-github-stvp-tempredis_0.0~git20231107.8a695b6-2_amd64.buildinfo Files: c6cfa5e03528135e2b9d4e7aeafe0b49 2417 golang optional golang-github-stvp-tempredis_0.0~git20231107.8a695b6-2.dsc c6a60e11e8981819faa47aaeedf70a91 2572 golang optional golang-github-stvp-tempredis_0.0~git20231107.8a695b6-2.debian.tar.xz 08f28848fa988ba7ccb52161ad8cbf66 6646 golang optional golang-github-stvp-tempredis_0.0~git20231107.8a695b6-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEWzS6WqtVB+kDQm6F6NN64vCfSHIFAmYJtdsACgkQ6NN64vCf SHLATA/7BvmyImUVuxPaow/6a3A8tmM8zNnW+2jrmWTHdUb8lK8naA+46ask+ggg pBKfZWzXVq20WLXxgYkiep8LbEpcL6CzELTQugZdyZefOByEBEJkdFAXfkM13BDJ Ja0LU4HufC6dgVBhWFL7YpIAdpb261+Ict4/e6PT0PkRox9qWbowPwEbQq3JEydO zhgBdutnspJE7jjvO/JZkPOgh/kUZYBSzIBHVaduPy1kLdzJBHCv7IxPYJOUGQea
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> close 1001981
Bug #1001981 [onioncircuits] onioncircuits: Doesn't start: Permission denied:
'/usr/local/lib/python3.9/dist-packages/usb-0.0.83.dev0.dist-info'
Marked Bug as done
> tags 1001981 + unreproducible
Bug #1001981 {Done: Sascha Steinbiss } [onioncircuits]
onioncircuits: Doesn't start: Permission denied:
'/usr/local/lib/python3.9/dist-packages/usb-0.0.83.dev0.dist-info'
Added tag(s) unreproducible.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1001981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001981
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > close 901144 Bug #901144 [onioncircuits] onioncircuits: Fails to display information on Tor Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 901144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#900015: marked as done (libmbedtls-dev: add pkg-config support)
Your message dated Sun, 31 Mar 2024 18:34:33 + with message-id and subject line Bug#900015: fixed in mbedtls 2.28.8-1 has caused the Debian Bug report #900015, regarding libmbedtls-dev: add pkg-config support 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.) -- 900015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900015 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mbedtls-dev version: 2.8.0-1 Severity: important Control: forwarded -1 https://github.com/ARMmbed/mbedtls/issues/228 Control: block 899036 by -1 Control: block 899035 by -1 lbgit2 now supports using mbedTLS but missing pkg-config support for mbedTLS is causing builds of many reverse dependencies like geany-plugins and gitgo. --- End Message --- --- Begin Message --- Source: mbedtls Source-Version: 2.28.8-1 Done: Andrea Pappacoda We believe that the bug you reported is fixed in the latest version of mbedtls, 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 900...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrea Pappacoda (supplier of updated mbedtls package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 31 Mar 2024 20:02:32 +0200 Source: mbedtls Architecture: source Version: 2.28.8-1 Distribution: unstable Urgency: medium Maintainer: Debian IoT Maintainers Changed-By: Andrea Pappacoda Closes: 900015 Changes: mbedtls (2.28.8-1) unstable; urgency=medium . * New upstream version 2.28.8 * d/libmbedtls-dev.install: install new pkg-config files (Closes: #900015) * d/.symbols: add new PSA symbols Checksums-Sha1: acea8bfedcecf2db4320775f8fd35701853021dc 1825 mbedtls_2.28.8-1.dsc 2d10159272723fc3adaddb64346fcc1b68967776 4041565 mbedtls_2.28.8.orig.tar.gz 7091f7b27d3c0b0083d8efa9978b801f2082b3e6 16000 mbedtls_2.28.8-1.debian.tar.xz c769fe993d35c9a88b3263fdc66d1aa92f340758 10867 mbedtls_2.28.8-1_amd64.buildinfo Checksums-Sha256: 40dc28f22291e73ecf5bc72c713fece29243ab23ac429103d851b55d1c33497d 1825 mbedtls_2.28.8-1.dsc edfe26dbc923a1d94aa53153d25b74f5dd51e89bfd222a6945eadec031fc9eb2 4041565 mbedtls_2.28.8.orig.tar.gz 4c4cb0d60049b5848b1332afa3567ef75c3f015db5d56eeca9a68d6cb7c54833 16000 mbedtls_2.28.8-1.debian.tar.xz d3e68212747c85217a21ff44607123b061809beb94012a34ac04021baf5a51de 10867 mbedtls_2.28.8-1_amd64.buildinfo Files: 128c87ad22301dfab86b87499d4eac56 1825 libs optional mbedtls_2.28.8-1.dsc 9fbf05d89942d7a25fce5c1127d56bfc 4041565 libs optional mbedtls_2.28.8.orig.tar.gz a362aaf0fa8d8f1515bd5f8f5eb3a794 16000 libs optional mbedtls_2.28.8-1.debian.tar.xz 1c3e9e4b48a21e4878a226fb4482ecfe 10867 libs optional mbedtls_2.28.8-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQS6VuNIvZRFHt7JcAdKkgiiRVB3pwUCZgmougAKCRBKkgiiRVB3 pyvkAP42mJCAMaEp/fVf5PgOnBEzmkHus6+rpk1e0fo3hfo6DQEA7R42TeU+Ax3f YcYrBbkMFP57Ll64n8flE3Nq6O+7Sww= =MkIn -END PGP SIGNATURE- pgp4f7YHsB6fT.pgp Description: PGP signature --- End Message ---
Bug#1066594: marked as done (octave-iso2mesh: FTBFS: nl_single_file.c:2505:26: error: implicit declaration of function ‘lsame_’ [-Werror=implicit-function-declaration])
Your message dated Sun, 31 Mar 2024 17:41:47 +
with message-id
and subject line Bug#1066594: fixed in octave-iso2mesh 1.9.6+ds-10
has caused the Debian Bug report #1066594,
regarding octave-iso2mesh: FTBFS: nl_single_file.c:2505:26: error: implicit
declaration of function ‘lsame_’ [-Werror=implicit-function-declaration]
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.)
--
1066594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: octave-iso2mesh
Version: 1.9.6+ds-9
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> make[4]: Entering directory '/<>/meshfix'
> [ 37%] Building C object
> CMakeFiles/meshfix.dir/contrib/jrs_predicates/jrs_predicates.c.o
> [ 39%] Building CXX object
> CMakeFiles/meshfix.dir/src/detectIntersections.cpp.o
> [ 41%] Building CXX object CMakeFiles/meshfix.dir/src/holeFilling.cpp.o
> /<>/meshfix/src/holeFilling.cpp: In member function ‘void
> ExtTriMesh::fairSelection(Triangle*)’:
> /<>/meshfix/src/holeFilling.cpp:378:31: warning: cast to pointer
> from integer of different size [-Wint-to-pointer-cast]
> 378 | ((Vertex *)n->data)->info = (void *)i;
> | ^
> [ 43%] Building CXX object CMakeFiles/meshfix.dir/src/sparseLSystem.cpp.o
> [ 45%] Building CXX object CMakeFiles/meshfix.dir/src/mwExtensions.cpp.o
> [ 47%] Building CXX object CMakeFiles/meshfix.dir/src/smoothing.cpp.o
> [ 50%] Building C object
> CMakeFiles/meshfix.dir/contrib/OpenNL3.2.1/src/nl_single_file.c.o
> /<>/meshfix/contrib/OpenNL3.2.1/src/nl_single_file.c: In
> function ‘dtpsv_’:
> /<>/meshfix/contrib/OpenNL3.2.1/src/nl_single_file.c:2505:26:
> error: implicit declaration of function ‘lsame_’
> [-Werror=implicit-function-declaration]
> 2505 | if (!NL_FORTRAN_WRAP(lsame)(uplo, "U") &&
> | ^
> /<>/meshfix/contrib/OpenNL3.2.1/src/nl_single_file.c:420:28:
> note: in definition of macro ‘NL_FORTRAN_WRAP’
> 420 | #define NL_FORTRAN_WRAP(x) x##_
> |^
> /<>/meshfix/contrib/OpenNL3.2.1/src/nl_single_file.c:2526:25:
> error: implicit declaration of function ‘xerbla_’
> [-Werror=implicit-function-declaration]
> 2526 | NL_FORTRAN_WRAP(xerbla)("DTPSV ", );
> | ^~
> /<>/meshfix/contrib/OpenNL3.2.1/src/nl_single_file.c:420:28:
> note: in definition of macro ‘NL_FORTRAN_WRAP’
> 420 | #define NL_FORTRAN_WRAP(x) x##_
> |^
> /<>/meshfix/contrib/OpenNL3.2.1/src/nl_single_file.c: In
> function ‘nlSolve_SUPERLU’:
> /<>/meshfix/contrib/OpenNL3.2.1/src/nl_single_file.c:3513:5:
> error: implicit declaration of function ‘dCreate_CompCol_Matrix’; did you
> mean ‘cCreate_CompCol_Matrix’? [-Werror=implicit-function-declaration]
> 3513 | dCreate_CompCol_Matrix(
> | ^~
> | cCreate_CompCol_Matrix
> /<>/meshfix/contrib/OpenNL3.2.1/src/nl_single_file.c:3521:5:
> error: implicit declaration of function ‘dCreate_Dense_Matrix’; did you mean
> ‘cCreate_Dense_Matrix’? [-Werror=implicit-function-declaration]
> 3521 | dCreate_Dense_Matrix(
> | ^~~~
> | cCreate_Dense_Matrix
> /<>/meshfix/contrib/OpenNL3.2.1/src/nl_single_file.c:3557:5:
> error: implicit declaration of function ‘dgssv’; did you mean ‘cgssv’?
> [-Werror=implicit-function-declaration]
> 3557 | dgssv(, , perm, perm_r, , , , , );
> | ^
> | cgssv
> cc1: some warnings being treated as errors
> make[4]: *** [CMakeFiles/meshfix.dir/build.make:160:
> CMakeFiles/meshfix.dir/contrib/OpenNL3.2.1/src/nl_single_file.c.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/octave-iso2mesh_1.9.6+ds-9_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
Bug#1055321: marked as done (pipx: shell completions are not installed)
Your message dated Sun, 31 Mar 2024 17:08:45 + with message-id and subject line Bug#1055321: fixed in python-pipx 1.5.0-1 has caused the Debian Bug report #1055321, regarding pipx: shell completions are not installed 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.) -- 1055321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pipx Version: 1.2.1-1 Severity: wishlist X-Debbugs-Cc: debian.10.il...@xoxy.net Dear Maintainer, Running `pipx completions` shows that pipx supports shell completions for bash, zsh, fish, and tcsh. It would be nice if the first three were installed in the system locations when `pipx` is installed. The relevant locations are: /usr/share/bash-completion/completions/ /usr/share/zsh/vendor-completions/ /usr/share/fish/vendor_completions.d/ Thanks for considering it! - Ilya -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'testing'), (500, 'stable'), (100, 'bookworm-fasttrack'), (100, 'bookworm-backports-staging') Architecture: amd64 (x86_64) Kernel: Linux 6.1.55-06875-g6b8d148f8722 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages pipx depends on: ii python3 [python3-supported-min] 3.11.4-5+b1 ii python3-argcomplete 2.0.0-1 ii python3-packaging23.1-1 ii python3-userpath 1.9.1-1 ii python3-venv 3.11.4-5+b1 Versions of packages pipx recommends: ii fonts-font-awesome 5.0.10+really4.7.0~dfsg-4.1 ii libjs-bootstrap44.6.1+dfsg1-4 ii libjs-highlight.js 9.18.5+dfsg1-2 ii libjs-jquery3.6.1+dfsg+~3.5.14-1 ii libjs-lunr 2.3.9~dfsg-2 pn mkdocs pipx suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: python-pipx Source-Version: 1.5.0-1 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of python-pipx, 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 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated python-pipx package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 31 Mar 2024 12:45:12 -0400 Source: python-pipx Architecture: source Version: 1.5.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Stefano Rivera Closes: 1055321 Changes: python-pipx (1.5.0-1) unstable; urgency=medium . * New upstream release. * Ship a fish command completion. (Closes: #1055321) * Patch: Avoid needing markdown-gfm-admonition. Checksums-Sha1: ce69f6c6c8706e10086feb90412a7ba3f86afdf6 1791 python-pipx_1.5.0-1.dsc c8de74da07729043e6ccc2050be79b2e31abd3b5 374890 python-pipx_1.5.0.orig.tar.gz 69f45a5bbb39fdf2f0024bd79c23fa448400dfab 9280 python-pipx_1.5.0-1.debian.tar.xz 19565a7880d43a5aef1d9350e0f6f2d7d97ae242 8280 python-pipx_1.5.0-1_source.buildinfo Checksums-Sha256: b553482933b9d3751feab1171736bfee0f6eb9808714b373ab039ed1a1c8f4e4 1791 python-pipx_1.5.0-1.dsc fffc8c7419d35830bb68515dd285105c1cd7af14d69f813bc166e81b7e2d9df4 374890 python-pipx_1.5.0.orig.tar.gz 298a2e66f4c2e930aef756fa3968fe5392a130421ded543dd1b7198a7cbb4cf1 9280 python-pipx_1.5.0-1.debian.tar.xz d0a9225f9452872de2e8a80a67be1d37dff0aac821f1aa0f850607016ca6920c 8280 python-pipx_1.5.0-1_source.buildinfo Files: b647e3d5798b71413093866079268232 1791 python optional python-pipx_1.5.0-1.dsc 0661f830a1eec2989ab684b6d64f4f80 374890 python optional python-pipx_1.5.0.orig.tar.gz bb2fd72484d811a992054d86f656ad39 9280 python optional python-pipx_1.5.0-1.debian.tar.xz 73f64256bf234b1e349f450c8e8e9679 8280 python optional python-pipx_1.5.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCZgmTdhQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2DD5AQC0vmcoqP9Dq3t1jzTZsn++wOFPCFkd
Bug#1067879: marked as done (mp3check: suggests dead-upstream mpg321 instead of mpg123)
Your message dated Sun, 31 Mar 2024 17:06:48 + with message-id and subject line Bug#1067879: fixed in mp3check 0.8.7-5 has caused the Debian Bug report #1067879, regarding mp3check: suggests dead-upstream mpg321 instead of mpg123 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.) -- 1067879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067879 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mp3check Version: 0.8.7-4 Severity: normal X-Debbugs-Cc: ametz...@bebt.de User: ametz...@debian.org Usertags: mpg321-removal Hello, this package suggests mpg321. mpg321 is dead upstream (last change 2012, about 12 years ago), it was initially created because of license issues with mpg123, however mpg123 moved to Debian main in 2006. Please consider moving to another player, e.g. mpg123. mpg123 license nowadays is LGPL-2.1, while mpg321 uses GPL-2+. Since LGPL-2.1 can be relicensed to GPL-2+ there should not be any problemds on that side. cu Andreas --- End Message --- --- Begin Message --- Source: mp3check Source-Version: 0.8.7-5 Done: Joachim Reichel We believe that the bug you reported is fixed in the latest version of mp3check, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joachim Reichel (supplier of updated mp3check package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 31 Mar 2024 15:23:44 +0200 Source: mp3check Architecture: source Version: 0.8.7-5 Distribution: unstable Urgency: medium Maintainer: Joachim Reichel Changed-By: Joachim Reichel Closes: 1067879 Changes: mp3check (0.8.7-5) unstable; urgency=medium . * Add comment in debian/watch to explain why the watch file no longer works. * Add new Vcs-* fields in debian/control. * Remove Suggests: mpg321 (instead of replacing it with mpg123) since it seems to be completely unused (Closes: #1067879). * Update Standards-Version to 4.6.2 (no changes needed). Checksums-Sha1: d42978c84ffc53b456d33fe7773c323202fe1bee 1825 mp3check_0.8.7-5.dsc 73a9b15b85eca614d838856ef6333ea0a654caf3 7988 mp3check_0.8.7-5.debian.tar.xz e8e861194e8300fb270ff88dc8b3fd0dedd524a3 6315 mp3check_0.8.7-5_amd64.buildinfo Checksums-Sha256: 58883464a22ebfdaebe95995b4c3e7a8cf7ff3f4bee0db64882911d3f12448d6 1825 mp3check_0.8.7-5.dsc 0ab2bc65c7a5136805c9d8f748d11549d60f582d0ed388c71ae34d41f63f4a9f 7988 mp3check_0.8.7-5.debian.tar.xz a996fe7782f7647ba9e70a951ad861563878e42c234bdf5e96848442e7c2c44f 6315 mp3check_0.8.7-5_amd64.buildinfo Files: cfe897fbeedbef9c081bcc042162cd7c 1825 sound optional mp3check_0.8.7-5.dsc 655ca67902c09de386309df9ae43341b 7988 sound optional mp3check_0.8.7-5.debian.tar.xz 55b93a911f444d2107b6c09b6aa5106c 6315 sound optional mp3check_0.8.7-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErX6NzLwwsr4xjsEVuPr/HEOIZ3EFAmYJkmQACgkQuPr/HEOI Z3H8zA//VTHEwIjOnmFP3AVoNa4LZnb/NO8d3HMtwWKjxdxolF530pHQkpm8z14D xSePCJspkA2oaIHK15WJONSB9JRo6VbfSRGo1MHoBAc2a9omitzRmbFJifWPrr9P xjSByw5J+iiHcroKR0L2EP75XsBxGvjehwJro4AszRv95RYM6QIrtvP/ZGJpkgm4 isU8+zhCDPRY4D+NFAKVS6pTZchvvhi8tAlcsuh6OgvCa8sWNAEveNFq9k1Z5cAF uymlchO3H+/GmgQBroodZYFsBoke6CH3ps/JddRIETI4BTjSWoVRKxG8+jiREaPO pTqCvT4510KyqmjuLo9UcWd+c6g4Link7ZINW+doWApCR+Wnli/UdYaCYtK69Mqv TXsHyLK9LOO/9sRxDlTKC7NOvt03zmreWVz+3PN1OeByodyie4jAIw7tIPregFX5 oj3VUMKDw5Q2utTICIsMTT/rm1LsQ9r24FDSDnCc0jIjLmBwAkPd+qTB/S69jjAK 5ZdxKSH+ZWUXQ9NKvSaobD2nGh+4Mb8kCbXaYhgTcN+7E6Svigrq5F56z0lAnIDm UYDWn1RFL8rL6CO8vsC78yOeT1V7FS788peb5cxbUazjkceNRorVPVuRQaGli4rX bvpzNRKR/T3M87ycG1WxY7+08KPDBjxdYSO8fPg313t2/CoFjBk= =6Cjj -END PGP SIGNATURE- pgpbShlH7hYyU.pgp Description: PGP signature --- End Message ---
Bug#1067880: marked as done (normalize-audio: suggests dead-upstream mpg321 instead of mpg123)
Your message dated Sun, 31 Mar 2024 17:06:57 + with message-id and subject line Bug#1067880: fixed in normalize-audio 0.7.7-18 has caused the Debian Bug report #1067880, regarding normalize-audio: suggests dead-upstream mpg321 instead of mpg123 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.) -- 1067880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067880 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: normalize-audio Version: 0.7.7-17 Severity: normal X-Debbugs-Cc: ametz...@bebt.de User: ametz...@debian.org Usertags: mpg321-removal Hello, this package suggests mpg321. mpg321 is dead upstream (last change 2012, about 12 years ago), it was initially created because of license issues with mpg123, however mpg123 moved to Debian main in 2006. Please consider moving to another player, e.g. mpg123. mpg123 license nowadays is LGPL-2.1, while mpg321 uses GPL-2+. Since LGPL-2.1 can be relicensed to GPL-2+ there should not be any problemds on that side. cu Andreas --- End Message --- --- Begin Message --- Source: normalize-audio Source-Version: 0.7.7-18 Done: Joachim Reichel We believe that the bug you reported is fixed in the latest version of normalize-audio, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joachim Reichel (supplier of updated normalize-audio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 31 Mar 2024 18:33:17 +0200 Source: normalize-audio Architecture: source Version: 0.7.7-18 Distribution: unstable Urgency: medium Maintainer: Joachim Reichel Changed-By: Joachim Reichel Closes: 1067880 Changes: normalize-audio (0.7.7-18) unstable; urgency=medium . * Replace mpg321 by mpg123 in Build-Depends: and Suggests: (Closes: #1067880). * Replace pkg-config by pkgconf in Build-Depends:. * Update Standards-Version to 4.6.2 (no changes needed). Checksums-Sha1: 4408042a1770b56242c68b52a8f26e65035f4854 1980 normalize-audio_0.7.7-18.dsc 20d84d5d9f0bf6cc58368f451d367cb488616bf9 11972 normalize-audio_0.7.7-18.debian.tar.xz a45e3540208ec74128a670e404a3417e9a56578a 8424 normalize-audio_0.7.7-18_amd64.buildinfo Checksums-Sha256: c6e01f1617017bb9f20934400235ddb824e8a9a5d6d3b524e027d06f7ef59015 1980 normalize-audio_0.7.7-18.dsc 170e69b1bb663b4eee583c0e0ee08495ad768f074d78e45b94316c13e84e2e0d 11972 normalize-audio_0.7.7-18.debian.tar.xz 624389b62a5079a1325f031e6768f6356b28f2bf34a15c3cd46f4fbe1ff6aaf5 8424 normalize-audio_0.7.7-18_amd64.buildinfo Files: 4252c661cca5f94b1a3a5f1e1398f761 1980 sound optional normalize-audio_0.7.7-18.dsc f65dd41773c33bff9c46ef365c71f8f3 11972 sound optional normalize-audio_0.7.7-18.debian.tar.xz 868655606907833cda61fcac7be782e4 8424 sound optional normalize-audio_0.7.7-18_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErX6NzLwwsr4xjsEVuPr/HEOIZ3EFAmYJk3QACgkQuPr/HEOI Z3EISRAAoN6yzC4ux+dSeQmr+g/HRhImJcO54H76sJPe1F2MbJo4NzceuGt5tfRz vEP7Sx+DJdr8HU7GtB0BypE+Ck18WB/8gY6F2lXuGE5xkYPNdZl6f9ly13cSUK/t fgxMuHtjUfJs6PHY2DXb9nOsgMarFIbu5DoMocTjFNQlNYOuDg7X9L9u0MO/qWsN CVzFyYDyYWdjtixE7rCMEw/OEWcxB5BergZSfN5z2/TwZynt1mt0Ph8OTTIgZTg2 lVBU5wCzbsTJcJyhrweENv0LLDqDuTg/TE1rN0p5UUDtMCelAEoSwLsJ3qIDsbnd cENwkjbPbhjoYpgaRoEdjJTLKDtQod2FtG41QAavKr2D4tdgrwdOThuM5mPz5lIN H568PXsSlsEvJh5g0jN7AVNxeSRCbcR4hOhapAhDvxsaGDoiLpYMXWEWF3lShKIt U2ULEVcgmBB2EZgjJqbkgDUpa53Z16bTuKLp3nKDbajiBqWaPrBDciXIMmvwK0Ef YXL8rUsy2/iEhQToaRGx1jAJ5PoPeHNK5YNyV7qbSUyjye/68MlGJxmx+j/5YQAi a6++lfFsd0M0VatVNz9a+xCqiD09Pfq5zsouqYrq0pKgsUn2J9FgIcUWb7glXuJH 2MH66VQFOgAHFYEKiMzORMCqNDTl3i2VisyF0ony2CoFH47bZKQ= =R0Yp -END PGP SIGNATURE- pgpar5GzXiOmz.pgp Description: PGP signature --- End Message ---
Bug#1063989: marked as done (xonsh: autopkgtest regression with pytest 8)
Your message dated Sun, 31 Mar 2024 16:53:52 + with message-id and subject line Bug#1063989: fixed in xonsh 0.15.1+dfsg-1 has caused the Debian Bug report #1063989, regarding xonsh: autopkgtest regression with pytest 8 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.) -- 1063989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xonsh Version: 0.14.4+dfsg-1 Severity: important User: debian-pyt...@lists.debian.org Usertags: pytest-8 Dear maintainer, your package has a autopkgtest regression with pytest 8. Typically, packages will start failing if they - have deprecation warnings of type PytestRemovedIn8Warning, or - assume a particular pytest stdout/stderr output which might have changed, or - rely on implementation details of the pytest test collector, in particular the pytest.Package class, which has been redesigned for pytest 8. Please refer to the upstream changelog [1] for a complete list of breaking changes and the pytest (pseudo-)excuses [2] related to your package for details of the regression. It is possible that the autopkgtest regression is not directly caused by xonsh, but by one of its dependencies. In that case, feel free to reassign the bug and mark your package as affected, but do not close the bug until the autopkgtest passes. Cheers Timo [1] https://docs.pytest.org/en/8.0.x/changelog.html#pytest-8-0-0rc1-2023- 12-30 [2] https://qa.debian.org/excuses.php?experimental=1=pytest --- End Message --- --- Begin Message --- Source: xonsh Source-Version: 0.15.1+dfsg-1 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of xonsh, 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 1063...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated xonsh package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 31 Mar 2024 12:30:13 -0400 Source: xonsh Architecture: source Version: 0.15.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Stefano Rivera Closes: 1063989 Changes: xonsh (0.15.1+dfsg-1) unstable; urgency=medium . * Team upload. * New upstream release. - Supports pytest 8. (Closes: #1063989) * Refresh patches. * Drop revert-pytest-8.patch, no longer needed. * Bump copyright years. Checksums-Sha1: d72b9253bf1f1e3190d2cd498049f9b584cb4fdf 1877 xonsh_0.15.1+dfsg-1.dsc 0d3a7f04f5eebcb01c649e782b0dfb18861f1571 545260 xonsh_0.15.1+dfsg.orig.tar.xz d4e2a085746ef82008720d593a04689a7baeb2b9 12936 xonsh_0.15.1+dfsg-1.debian.tar.xz d6a94e1287f13ec176ea407f7b55fe0363702f59 8358 xonsh_0.15.1+dfsg-1_source.buildinfo Checksums-Sha256: f71791252941baf169784961dfaab9a2646b831b00ec57211fbc1131351ef2e8 1877 xonsh_0.15.1+dfsg-1.dsc 86a7e3dbe3cba04754dcb75aca522afbb32c4d2e269c565f6fe2320fe110e7f2 545260 xonsh_0.15.1+dfsg.orig.tar.xz 5c86b3c30e5206f97fe3ef0baa3b3221636d55354f560a79752158f176947517 12936 xonsh_0.15.1+dfsg-1.debian.tar.xz 88e7040854471e2cd5c0b3b0b82f9b6167957c9d7bd2980733b5b98142270901 8358 xonsh_0.15.1+dfsg-1_source.buildinfo Files: 369edb1251a5152fd39d0721994bc5f8 1877 shells optional xonsh_0.15.1+dfsg-1.dsc ac656524c4ec6259f3ee01c215ffae74 545260 shells optional xonsh_0.15.1+dfsg.orig.tar.xz f36135afc37b3e0564d40dcee9a1fc5b 12936 shells optional xonsh_0.15.1+dfsg-1.debian.tar.xz adc1c58e19e11368ca1f4b5106711e17 8358 shells optional xonsh_0.15.1+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCZgmP3hQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2B8IAQDsRQs6qdSNXXBENXJIpGnGkGZr0wDP hrefCQD56Z89xQEAnYbea+3xu00laNARESccFI3/k6BKdZOnISz0WMHbSQs= =FHTK -END PGP SIGNATURE- pgpjq1modDHM9.pgp Description: PGP signature --- End Message ---
Bug#1049381: marked as done (pipx: manpage shows as generate_man.py)
Your message dated Sun, 31 Mar 2024 12:11:17 -0400 with message-id <3zgkm6diinxqzw2a6l4eb44kqj5en7u4nrt4gbxnr2sxcbclg6@gy6iejrvtxc7> and subject line Re: Bug#1049381: pipx: manpage shows as generate_man.py has caused the Debian Bug report #1049381, regarding pipx: manpage shows as generate_man.py to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1049381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pipx Version: 1.2.0-2 Severity: minor X-Debbugs-Cc: christop...@bocki.com Dear Maintainer, when i open the manpage it shows the script-name 'generate_man.py(1)' instead of 'pipx(1)' and uses that for all described commands. I checked a stable system aswell but it is only happening on trixie/sid. Cheers, Christopher Bock -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pipx depends on: ii python3 3.11.4-5+b1 ii python3-argcomplete 2.0.0-1 ii python3-importlib-metadata 4.12.0-1 ii python3-packaging 23.1-1 ii python3-userpath1.9.0-1 ii python3-venv3.11.4-5+b1 Versions of packages pipx recommends: ii fonts-font-awesome 5.0.10+really4.7.0~dfsg-4.1 ii libjs-bootstrap44.6.1+dfsg1-4 ii libjs-highlight.js 9.18.5+dfsg1-2 ii libjs-jquery3.6.1+dfsg+~3.5.14-1 ii libjs-lunr 2.3.9~dfsg-2 ii mkdocs 1.4.2+dfsg-2 pipx suggests no packages. -- no debconf information -- lg, ~cb --- End Message --- --- Begin Message --- Version: 1.3.3-1 I think this was fixed in 1.3.3, upstream. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272--- End Message ---
Bug#1068102: marked as done (FileNotFoundError in process_manpages())
Your message dated Sun, 31 Mar 2024 15:49:34 +
with message-id
and subject line Bug#1068102: fixed in debputy 0.1.24
has caused the Debian Bug report #1068102,
regarding FileNotFoundError in process_manpages()
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.)
--
1068102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dh-debputy
Version: 0.1.23
Severity: normal
I've tried to convert the cpuid package to dh-sequence-zz-debputy, when
building it I got:
dh_debputy
debputy: info: Loaded plugin debputy
debputy: info: The following directories are considered search dirs (in order):
debputy: info: * debian/tmp (skipped; absent)
debputy: info: * .
debputy: info: The following directories are considered for "not-installed"
paths;
debputy: info: * debian/tmp (skipped; absent)
debputy: info: Looking up build-ids via: file -00 -N
/<>/debian/.debhelper/_debputy/scratch-dir/_pb-615671/generated-
fs-content/no-package/tmpqr8svzjr__cpuid
debputy: info: Removing unnecessary ELF debug info via: strip --remove-
section=.comment --remove-section=.note
/<>/debian/.debhelper/_debputy/scratch-dir/_pb-615671/generated-
fs-content/no-package/tmpqr8svzjr__cpuid
debputy: info: Ensuring manpages have utf-8 encoding via: man-recode --to-code
UTF-8 --suffix .encoded /<>/debian/.debhelper/_debputy/scratch-
dir/_pb-615671/generated-fs-content/no-package/tmp7zgxlblf__cpuid.1.gz
/<>/debian/.debhelper/_debputy/scratch-dir/_pb-615671/generated-
fs-content/no-package/tmp8zbqi23u__cpuinfo2cpuid.1.gz
debputy: warning: Unhandled exception (Re-run with --debug to see the raw stack
trace)
debputy: warning: - 8< BEGIN STACK TRACE 8< -
Traceback (most recent call last):
File "/usr/share/dh-debputy/debputy/commands/debputy_cmd/__main__.py", line
1459, in main
ROOT_COMMAND(cmd_arg)
File "/usr/share/dh-debputy/debputy/commands/debputy_cmd/context.py", line
609, in __call__
self._aliases[v](command_arg)
File "/usr/share/dh-debputy/debputy/commands/debputy_cmd/context.py", line
609, in __call__
self._aliases[v](command_arg)
File "/usr/share/dh-debputy/debputy/commands/debputy_cmd/context.py", line
442, in __call__
return self._handler(context)
^^
File "/usr/share/dh-debputy/debputy/commands/debputy_cmd/__main__.py", line
749, in _dh_integration_generate_debs
run_package_processors(manifest, package_metadata_context, fs_root)
File "/usr/share/dh-debputy/debputy/deb_packaging_support.py", line 826, in
run_package_processors
.run_package_processor(fs_root, None, package_metadata_context)
File "/usr/share/dh-debputy/debputy/plugin/api/impl_types.py", line 788, in
run_package_processor
self.package_processor(fs_root, unused, context)
File "/usr/share/dh-debputy/debputy/plugin/debputy/package_processors.py",
line 120, in process_manpages
os.rename(f"{manpage}.encoded", manpage)
FileNotFoundError: [Errno 2] No such file or directory:
'/<>/debian/.debhelper/_debputy/scratch-dir/_pb-615671/generated-
fs-content/no-package/tmp7zgxlblf__cpuid.1.gz.encoded' ->
'/<>/debian/.debhelper/_debputy/scratch-dir/_pb-615671/generated-
fs-content/no-package/tmp7zgxlblf__cpuid.1.gz'
Note that cpuid.1 is not mentioned in the packaging. It's installed to
debian/cpuid/usr/share/man/man1/cpuid.1.gz at the moment of the error.
All changes:
diff --git a/debian/control b/debian/control
index bc4f9ac..83f15f5 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: cpuid
Section: admin
Priority: optional
Maintainer: Andrey Rahmatullin
-Build-Depends: debhelper-compat (= 13)
+Build-Depends: debhelper-compat (= 13), dh-sequence-zz-debputy
Standards-Version: 4.6.1
Vcs-Git: https://salsa.debian.org/debian/cpuid.git
Vcs-Browser: https://salsa.debian.org/debian/cpuid
@@ -11,7 +11,6 @@ Rules-Requires-Root: no
Package: cpuid
Architecture: any-i386 any-amd64
-Depends: ${shlibs:Depends}, ${perl:Depends}, ${misc:Depends}
Description: tool to dump x86 CPUID information about the CPU(s)
cpuid dumps detailed information about the CPU(s) gathered from the
CPUID instruction, and also determines the exact model of CPU(s). It
diff --git a/debian/debputy.manifest b/debian/debputy.manifest
new file mode 100644
index 000..669437f
--- /dev/null
+++ b/debian/debputy.manifest
@@ -0,0 +1,4 @@
+manifest-version: '0.1'
+installations:
+- install-docs:
+source: FUTURE
diff --git a/debian/docs b/debian/docs
deleted file mode 100644
index 3cb5077..000
--- a/debian/docs
Processed: closing 1067304
Processing commands for cont...@bugs.debian.org: > # this was a transient issues > close 1067304 Bug #1067304 [src:gmsh] gmsh: FTBFS: unsatisfiable build-dependencies Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1067304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067304 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067985: marked as done (nmu: libevent_2.1.12-stable-8.1)
Your message dated Sun, 31 Mar 2024 16:55:31 +0200 with message-id and subject line Re: Bug#1067985: nmu: libevent_2.1.12-stable-8.1 has caused the Debian Bug report #1067985, regarding nmu: libevent_2.1.12-stable-8.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.) -- 1067985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067985 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal X-Debbugs-Cc: libev...@packages.debian.org Control: affects -1 + src:libevent User: release.debian@packages.debian.org Usertags: binnmu nmu libevent_2.1.12-stable-8.1 . armhf . unstable . -m "Rebuild on buildd" --- End Message --- --- Begin Message --- On 2024-03-29 20:01:21 +0500, Andrey Rakhmatullin wrote: > Package: release.debian.org > Severity: normal > X-Debbugs-Cc: libev...@packages.debian.org > Control: affects -1 + src:libevent > User: release.debian@packages.debian.org > Usertags: binnmu > > nmu libevent_2.1.12-stable-8.1 . armhf . unstable . -m "Rebuild on buildd" Scheduled Cheers -- Sebastian Ramacher--- End Message ---
Bug#1068128: marked as done (nmu: opencolorio_2.1.3+dfsg-1.1)
Your message dated Sun, 31 Mar 2024 16:55:14 +0200 with message-id and subject line Re: Bug#1068128: nmu: opencolorio_2.1.3+dfsg-1.1 has caused the Debian Bug report #1068128, regarding nmu: opencolorio_2.1.3+dfsg-1.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.) -- 1068128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal X-Debbugs-Cc: opencolo...@packages.debian.org Control: affects -1 + src:opencolorio User: release.debian@packages.debian.org Usertags: binnmu nmu opencolorio_2.1.3+dfsg-1.1 . armel armhf . unstable . -m "Rebuild on buildds" --- End Message --- --- Begin Message --- On 2024-03-31 16:40:09 +0500, Andrey Rakhmatullin wrote: > Package: release.debian.org > Severity: normal > X-Debbugs-Cc: opencolo...@packages.debian.org > Control: affects -1 + src:opencolorio > User: release.debian@packages.debian.org > Usertags: binnmu > > nmu opencolorio_2.1.3+dfsg-1.1 . armel armhf . unstable . -m "Rebuild on > buildds" Scheduled Cheers -- Sebastian Ramacher--- End Message ---
Bug#1067494: marked as done (obs-studio: FTBFS on time64_t archs)
Your message dated Sun, 31 Mar 2024 13:39:07 +
with message-id
and subject line Bug#1067494: fixed in obs-studio 30.0.2+dfsg-3
has caused the Debian Bug report #1067494,
regarding obs-studio: FTBFS on time64_t archs
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.)
--
1067494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: obs-studio
Version: 30.0.2+dfsg-2.1
Severity: serious
Hello, looks like we got a failure due to time64_t transition.
/usr/bin/cc -DENABLE_HEVC -DHAVE_OBSCONFIG_H -DHAVE_UDEV -Dlinux_v4l2_EXPORTS -I/<>/libobs
-I/<>/obj-arm-linux-gnueabihf/config -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fno-stack-clash-protection
-fdebug-prefix-map=/<>=/usr/src/obs-studio-30.0.2+dfsg-2.1build2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64
-Wdate-time -D_FORTIFY_SOURCE=3 -DFFMPEG_MUX_FIXED=\"/usr/lib/arm-linux-gnueabihf/obs-plugins/obs-ffmpeg/obs-ffmpeg-mux\"
-DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -fvisibility=hidden -Wno-error=deprecated-declarations -std=gnu17 -fPIC -Werror -Wextra -Wvla -Wno-error=vla
-Wswitch -Wno-error=switch -Wformat -Wformat-security -Wunused-parameter -Wno-unused-function -Wno-missing-field-initializers -fno-strict-aliasing
-Werror-implicit-function-declaration -Wno-missing-braces -Wno-error=maybe-uninitialized -DSIMDE_ENABLE_OPENMP -fopenmp-simd -MD -MT
plugins/linux-v4l2/CMakeFiles/linux-v4l2.dir/v4l2-input.c.o -MF plugins/linux-v4l2/CMakeFiles/linux-v4l2.dir/v4l2-input.c.o.d -o
plugins/linux-v4l2/CMakeFiles/linux-v4l2.dir/v4l2-input.c.o -c /<>/plugins/linux-v4l2/v4l2-input.c
/<>/plugins/linux-v4l2/v4l2-input.c: In function ‘v4l2_thread’:
/<>/plugins/linux-v4l2/v4l2-input.c:66:43: error: format ‘%ld’
expects argument of type ‘long int’, but argument 4 has type ‘__suseconds64_t’ {aka ‘long
long int’} [-Werror=format=]
66 | #define blog(level, msg, ...) blog(level, "v4l2-input: " msg,
##__VA_ARGS__)
| ^~
/<>/plugins/linux-v4l2/v4l2-input.c:262:17: note: in expansion of
macro ‘blog’
262 | blog(LOG_DEBUG,
| ^~~~
cc1: all warnings being treated as errors
[137/484] /usr/bin/cc -DENABLE_HEVC -DHAVE_OBSCONFIG_H -Dlinux_jack_EXPORTS -I/<>/libobs
-I/<>/obj-arm-linux-gnueabihf/config -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fno-stack-clash-protection
-fdebug-prefix-map=/<>=/usr/src/obs-studio-30.0.2+dfsg-2.1build2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64
-Wdate-time -D_FORTIFY_SOURCE=3 -DFFMPEG_MUX_FIXED=\"/usr/lib/arm-linux-gnueabihf/obs-plugins/obs-ffmpeg/obs-ffmpeg-mux\"
-DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -fvisibility=hidden -Wno-error=deprecated-declarations -std=gnu17 -fPIC -Werror -Wextra -Wvla -Wno-error=vla
-Wswitch -Wno-error=switch -Wformat -Wformat-security -Wunused-parameter -Wno-unused-function -Wno-missing-field-initializers -fno-strict-aliasing
-Werror-implicit-function-declaration -Wno-missing-braces -Wno-error=maybe-uninitialized -DSIMDE_ENABLE_OPENMP -fopenmp-simd -MD -MT
plugins/linux-jack/CMakeFiles/linux-jack.dir/linux-jack.c.o -MF plugins/linux-jack/CMakeFiles/linux-jack.dir/linux-jack.c.o.d -o
plugins/linux-jack/CMakeFiles/linux-jack.dir/linux-jack.c.o -c /<>/plugins/linux-jack/linux-jack.c
I did "fix" with an ugly hacky patch, just for armhf platform, but I don't know
how to properly solve it.
diff -Nru obs-studio-30.0.2+dfsg/debian/patches/time64.patch
obs-studio-30.0.2+dfsg/debian/patches/time64.patch
--- obs-studio-30.0.2+dfsg/debian/patches/time64.patch 1970-01-01
01:00:00.0 +0100
+++ obs-studio-30.0.2+dfsg/debian/patches/time64.patch 2024-03-22
13:31:40.0 +0100
@@ -0,0 +1,18 @@
+Description: Use time64_t everywhere
+Author: Gianfranco Costamagna
+Last-Update: 2024-03-21
+
+--- obs-studio-30.0.2+dfsg.orig/plugins/linux-v4l2/v4l2-input.c
obs-studio-30.0.2+dfsg/plugins/linux-v4l2/v4l2-input.c
+@@ -260,7 +260,11 @@ static void *v4l2_thread(void *vptr)
+ }
+
+ blog(LOG_DEBUG,
++#ifndef __arm__
+"%s: ts: %06ld buf id #%d, flags 0x%08X, seq #%d, len %d, used
%d",
++#else
++ "%s: ts: %06lld buf id #%d, flags 0x%08X, seq #%d, len %d, used
%d",
++#endif
+data->device_id, buf.timestamp.tv_usec, buf.index,
+
Processed: RFS: graphviz-dot-mode/0.4.2+git20230325.8ff793b-1 [Team] -- Emacs mode for the dot-language used by graphviz
Processing commands for cont...@bugs.debian.org: > close 1067933 Bug #1067933 [sponsorship-requests] RFS: graphviz-dot-mode/0.4.2+git20230325.8ff793b-1 [Team] -- Emacs mode for the dot-language used by graphviz Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1067933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067942: marked as done (Depends on pre-t64 libglib2.0-0)
Your message dated Sun, 31 Mar 2024 12:50:08 + with message-id and subject line Bug#1067942: fixed in ibus 1.5.29-2 has caused the Debian Bug report #1067942, regarding Depends on pre-t64 libglib2.0-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.) -- 1067942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ibus Version: 1.5.29-1+b1 Severity: serious ibus has an explicit Depends: libglib2.0-0, this needs to be changed to libglib2.0-0t64. -- Package-specific info: ibus is /usr/bin/ibus ibus-setup is /usr/bin/ibus-setup ! !!! im-config is missing. Please install it. !!! !!! Please also read usr/share/doc/im-config/README.Debian.gz !!! ! XMODIFIERS= GTK_IM_MODULE= QT_IM_MODULE= WAYLAND_DISPLAY= XDG_CURRENT_DESKTOP=KDE XDG_MENU_PREFIX= XDG_RUNTIME_DIR=/run/user/1000 XDG_SEAT=seat0 XDG_SESSION_CLASS=user XDG_SESSION_DESKTOP=KDE XDG_SESSION_ID=3 XDG_SESSION_TYPE=x11 == ls -l /usr/lib/ibus/ibus-* /usr/libexec/ibus-* == /bin/ls: cannot access '/usr/lib/ibus/ibus-*': No such file or directory -rwxr-xr-x 1 root root 22832 Mar 13 06:45 /usr/libexec/ibus-dconf -rwxr-xr-x 1 root root 14640 Mar 13 06:45 /usr/libexec/ibus-engine-simple -rwxr-xr-x 1 root root 170288 Mar 13 06:45 /usr/libexec/ibus-extension-gtk3 -rwxr-xr-x 1 root root 18736 Mar 13 06:45 /usr/libexec/ibus-memconf -rwxr-xr-x 1 root root 96560 Mar 13 06:45 /usr/libexec/ibus-portal -rwxr-xr-x 1 root root 121144 Mar 13 06:45 /usr/libexec/ibus-ui-emojier -rwxr-xr-x 1 root root 371232 Mar 13 06:45 /usr/libexec/ibus-ui-gtk3 -rwxr-xr-x 1 root root 100280 Mar 13 06:45 /usr/libexec/ibus-x11 == dpkg-query -l 'ibus*' == Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii ibus 1.5.29-1+b1 amd64Intelligent Input Bus - core un ibus-clutter (no description available) ii ibus-data 1.5.29-1 all Intelligent Input Bus - data files un ibus-doc (no description available) un ibus-gtk (no description available) un ibus-gtk3(no description available) un ibus-gtk4(no description available) === gsettings === org.freedesktop.ibus.general dconf-preserve-name-prefixes ['/desktop/ibus/engine/pinyin', '/desktop/ibus/engine/bopomofo', '/desktop/ibus/engine/hangul'] org.freedesktop.ibus.general embed-preedit-text true org.freedesktop.ibus.general enable-by-default false org.freedesktop.ibus.general engines-order @as [] org.freedesktop.ibus.general preload-engines @as [] org.freedesktop.ibus.general switcher-delay-time 400 org.freedesktop.ibus.general use-global-engine true org.freedesktop.ibus.general use-system-keyboard-layout false org.freedesktop.ibus.general use-xmodmap true org.freedesktop.ibus.general version '' org.freedesktop.ibus.general xkb-latin-layouts ['af', 'af(fa-olpc)', 'af(ps-olpc)', 'af(ps)', 'af(uz)', 'af(uz-olpc)', 'am', 'am(eastern)', 'am(eastern-alt)', 'am(phonetic)', 'am(phonetic-alt)', 'am(western)', 'ara', 'ara(azerty)', 'ara(azerty_digits)', 'ara(buckwalter)', 'ara(digits)', 'ara(qwerty)', 'ara(qwerty_digits)', 'az(cyrillic)', 'bd', 'bd(probhat)', 'bg', 'bg(bas_phonetic)', 'bg(phonetic)', 'brai', 'brai(left_hand)', 'brai(right_hand)', 'bt', 'by', 'by(phonetic)', 'by(legacy)', 'ca(ike)', 'cn(tib)', 'cn(tib_asciinum)', 'cn(ug)', 'cz', 'cz(ucw)', 'de(ru)', 'dev', 'et', 'fr(geo)', 'ge', 'ge(os)', 'gr', 'gr(extended)', 'gr(nodeadkeys)', 'gr(polytonic)', 'gr(simple)', 'gur', 'il', 'il(biblical)', 'il(lyx)', 'il(phonetic)', 'id(melayu-phonetic)', 'id(melayu-phoneticx)', 'id(pegon-phonetic)', 'in', 'in(ben)', 'in(ben_baishakhi)', 'in(ben_bornona)', 'in(ben_gitanjali)', 'in(ben_inscript)', 'in(ben_probhat)', 'in(bolnagri)', 'in(deva)', 'in(guj)', 'in(guj-kagapa)', 'in(guru)', 'in(hin-kagapa)', 'in(hin-wx)', 'in(jhelum)', 'in(kan)', 'in(kan-kagapa)', 'in(mal)', 'in(mal_enhanced)', 'in(mal_lalitha)', 'in(mar-kagapa)', 'in(ori)', 'in(san-kagapa)', 'in(tam)', 'in(tamilnet)', 'in(tamilnet_TAB)', 'in(tamilnet_TSCII)', 'in(tamilnet_tamilnumbers)', 'in(tam_tamilnumbers)', 'in(tel)', 'in(tel-kagapa)', 'in(urd-phonetic)',
Bug#1068121: marked as done (python-fusepy: hard-coded dependencies on pre-t64 libraries)
Your message dated Sun, 31 Mar 2024 11:47:36 + with message-id and subject line Bug#1068121: fixed in python-fusepy 3.0.1-5 has caused the Debian Bug report #1068121, regarding python-fusepy: hard-coded dependencies on pre-t64 libraries 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.) -- 1068121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068121 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-fusepy Version: 3.0.1-4 Severity: serious X-Debbugs-Cc: sramac...@debian.org python-fusepy builds binary packages with hardcoded dependencies on shared library packages that were renamed as part of the time_t 64 transition. The dependencies need to be updated for this change - or if possible - changed to be generated by debhelper. There's a patch available from Ubuntu: https://patches.ubuntu.com/p/python-fusepy/python-fusepy_3.0.1-4ubuntu1.patch Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: python-fusepy Source-Version: 3.0.1-5 Done: Sascha Steinbiss We believe that the bug you reported is fixed in the latest version of python-fusepy, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sascha Steinbiss (supplier of updated python-fusepy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 31 Mar 2024 12:32:20 +0200 Source: python-fusepy Architecture: source Version: 3.0.1-5 Distribution: unstable Urgency: medium Maintainer: Sascha Steinbiss Changed-By: Sascha Steinbiss Closes: 1068121 Changes: python-fusepy (3.0.1-5) unstable; urgency=medium . * Avoid hard-coding run-time dependency on shared library. Thanks to Matthias Klose for the patch from Ubuntu. Closes: #1068121 * Bump copyright dates for debian/ directory. * Add Repository* to d/upstream/metadata. * Bump Standards-Version. * Add Rules-Requires-Root: no. Checksums-Sha1: 4d5acfa96a176a5b1cb01c1832c3af7e28316a5f 1981 python-fusepy_3.0.1-5.dsc c6230eaca1c9f7c3eb53b6b09d59b68522a8191f 2732 python-fusepy_3.0.1-5.debian.tar.xz 1cc8e2f969a09c78c2d67616c7ffe97dafe82334 6958 python-fusepy_3.0.1-5_amd64.buildinfo Checksums-Sha256: a394634761f8beb0319347d01cd68ccfc4f8c9198cdebdca40ab824e04ea670e 1981 python-fusepy_3.0.1-5.dsc f280bcfe89560807d36f0e2c9751f744d4b84d2fa9227c3699b21ddd103b518c 2732 python-fusepy_3.0.1-5.debian.tar.xz 93c69301a675ba1962e98f221889aad820ef3d957c37a01e7f607df7c5a6b509 6958 python-fusepy_3.0.1-5_amd64.buildinfo Files: c0d3987f7301e2a80c67d847c6d08316 1981 python optional python-fusepy_3.0.1-5.dsc 0f11fda3300f8995820ac52ff39670ff 2732 python optional python-fusepy_3.0.1-5.debian.tar.xz 1921fc06c2425b045d00ed92f147b336 6958 python optional python-fusepy_3.0.1-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEWzS6WqtVB+kDQm6F6NN64vCfSHIFAmYJP68ACgkQ6NN64vCf SHI4OQ//e8yh/9pomzbxZU1U+Zs81G4z8F/LsRaS5wRmEFm3jy1AyM1VEyu6kIWw 6FeKVZY621oOomVrQceNRvJySVmyUzT3Q1pXuAAVMUr8XBSfXxgxN+LJ0FwN3E7l eZJocLrr32V+WxoR1jH4QJo/r5qCoToCIV5ltxCoUKSpduNGQCBVRz2mTQihRrWO WDHYeC/aHPixbSEXcVr78fupmA6cegY0wAbSXHufXC7umwuAadeg/O+RNx933S87 RPTrNF72pgh/0khxi/npmbrTxGK77gNHSHqrxaLNhQrsxlb0qsockzkyCVv8GWy/ XgVDmoY5XIPstB5/j6sIb7suZYAFjZ/PNGeJVR0pj7KmPNLLUs6G1ocl4Qh9Nfgx ucDVXeFw3c8k1FCd7xxyI7ymnOZ49qq4GBTZpJZtB3l6clhcfSnKKtjhbTpGx74l g8iBgWZhwt2XwQJmfGqWHcOK+gIy+hKFJUNQHMN801IzI7jIaB8Ytiv6XrRDiNR4 Z1HT/Ye7AuKSn9rrTQYPyLtiMcpH8INr843Vxa1Vrz8cIHeOUAA8WoHDA63GKVnK bgaPJprzNhgf6QEuo5Fshc8LR+JqRGwCVp+0mJWI78nC5skxCdtIYJsW2NgX/4jo Vf6K10AksF7AOG4UQa+S13TtKfZj3W5x1RUSra5uu6/6vxQbgLs= =R7n5 -END PGP SIGNATURE- pgpCHh2gvk2Hj.pgp Description: PGP signature --- End Message ---
Bug#1067243: marked as done (openssh: please build without -fzero-call-used-regs=used on m68k)
Your message dated Sun, 31 Mar 2024 11:47:29 +
with message-id
and subject line Bug#1067243: fixed in openssh 1:9.7p1-3
has caused the Debian Bug report #1067243,
regarding openssh: please build without -fzero-call-used-regs=used on m68k
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.)
--
1067243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openssh
Version: 1:9.7p1-2
Severity: important
Justification: FTBFS on d-ports arch
Tags: ftbfs
X-Debbugs-Cc: t...@mirbsd.de, debian-...@lists.debian.org
On m68k, gcc-13 currently ICEs when -fzero-call-used-regs=used is
used (see #1066891) in moduli.c, packet.c, etc. but the configury
detects it and so it gets used. The upstream GCC bug comments say
there is no plan to backport the possible fix to releases, but it
has a short reproducer by doko:
$ cat moduli.i
int snprintf_eta;
double snprintf_time_per_line;
int snprintf(char *, int, char *, ...) {
snprintf_eta = snprintf_time_per_line;
}
$ m68k-linux-gnu-gcc -c -O2 -fzero-call-used-regs=used -fPIE moduli.i
during RTL pass: zero_call_used_regs
moduli.i: In function ‘snprintf’:
moduli.i:5:1: internal compiler error: in change_address_1, at emit-rtl.cc:2287
Maybe this could be used in the configure script?
I can confirm that appending…
int snprintf_eta;
double snprintf_time_per_line;
int snprintf(char *str, size_t size, const char *format, ...) {
snprintf_eta = snprintf_time_per_line;
}
… (lightly changed from the above) to the program from
m4/openssh.m4 OSSH_COMPILER_FLAG_TEST_PROGRAM fails with:
(pbuild-15711)root@ara2:/tmp# gcc -O2 -fPIE -fno-strict-aliasing
-fzero-call-used-regs=used t.c
during RTL pass: zero_call_used_regs
t.c: In function 'snprintf':
t.c:51:1: internal compiler error: in change_address_1, at emit-rtl.cc:2287
51 | }
| ^
[…]
Alternatively, just hardcode disabling this flag on m68k for now,
which we’ll eventually have to revert once GCC is on a fixed release
(14 probably).
Thanks in advance!
--- End Message ---
--- Begin Message ---
Source: openssh
Source-Version: 1:9.7p1-3
Done: Colin Watson
We believe that the bug you reported is fixed in the latest version of
openssh, 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 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Colin Watson (supplier of updated openssh package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 31 Mar 2024 11:55:38 +0100
Source: openssh
Architecture: source
Version: 1:9.7p1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenSSH Maintainers
Changed-By: Colin Watson
Closes: 1067243
Changes:
openssh (1:9.7p1-3) unstable; urgency=medium
.
* Fix gssapi-keyex declaration further (thanks, Andreas Hasenack;
LP: #2053146).
* Extend -fzero-call-used-regs check to catch m68k gcc bug (closes:
#1067243).
* debian/tests/regress: Set a different IP address for UNKNOWN.
* Re-enable ssh-askpass-gnome on all architectures.
* regress: Redirect conch stdin from /dev/zero (re-enables conch interop
tests).
* Drop "Work around RSA SHA-2 signature issues in conch" patch (no longer
needed now that Twisted is fixed).
Checksums-Sha1:
fae4063c0d69a6a70ddb6cb3540ac4a65db63964 3341 openssh_9.7p1-3.dsc
f04d1a038b78270fb388bf39684fe493f302ec47 189708 openssh_9.7p1-3.debian.tar.xz
Checksums-Sha256:
754950e744b1cd844fd74c23a97b5f7b3cc26f6fd63f051bb94f4b3ae77b6834 3341
openssh_9.7p1-3.dsc
a5a21e53e1c5ff4f4ed94b7740d7d4d9dd4d9f63b2950b3914d1a9f199f8d1db 189708
openssh_9.7p1-3.debian.tar.xz
Files:
d09797f5ed421e28be0b918a85efe791 3341 net standard openssh_9.7p1-3.dsc
ba1391311beb6622f4b01306cec3af7d 189708 net standard
openssh_9.7p1-3.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmYJQVUACgkQOTWH2X2G
UAsytBAAhrg4Ls74PXvWNAy0hlAlK6Ioyfg6GWYco6vKBMKsj2EWLKsFpLGFVMS8
ag+Bk/EbFjkQxZ/fRowVAEkfQ/Qtl0DCaXtzzh7rxCQggWo163s4vwN5tW2B/Yz9
q4Bq4Cx38dWcPiKZ0TWkFP1VpVKy4Zw1vPrFZScF1RQkYGw68ALmfRdcuXnOuWqJ
Bug#1056861: marked as done (python-llfuse: ftbfs with cython 3.0.x)
Your message dated Sun, 31 Mar 2024 11:08:51 + with message-id and subject line Bug#1056861: fixed in python-llfuse 1.4.1+dfsg-3 has caused the Debian Bug report #1056861, regarding python-llfuse: ftbfs with cython 3.0.x 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.) -- 1056861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-llfuse Version: 1.4.1+dfsg-2 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: cython3 [This bug is targeted to the upcoming trixie release] The package fails to build in a test rebuild on at least arm64 with cython 3.0.5, but succeeds to build with cython 0.29.36. Please update the package to build with cython 3.0.5 (available in experimental). If the package cannot be built with cython 3.0.5, please change the build dependency from cython3 to cython3-legacy (available now in unstable). There is no replacement for cython3-dbg. Build logs building with cython 3.0.5 can be found at https://people.debian.org/~stefanor/cython3/cython-3.0.5/ See also https://lists.debian.org/debian-python/2023/11/msg00034.html --- End Message --- --- Begin Message --- Source: python-llfuse Source-Version: 1.4.1+dfsg-3 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of python-llfuse, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated python-llfuse package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 31 Mar 2024 10:46:48 +0200 Source: python-llfuse Built-For-Profiles: noudeb Architecture: source Version: 1.4.1+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Sebastian Ramacher Closes: 1056861 Changes: python-llfuse (1.4.1+dfsg-3) unstable; urgency=medium . * Team upload . [ Debian Janitor ] * Update standards version to 4.6.1, no changes needed. . [ Bas Couwenberg ] * Switch to cython3-legacy. (Closes: #1056861) . [ Sebastian Ramacher ] * Remove left-overs from dbgsym migration Checksums-Sha1: efaff444fa5c203b5d5ca877f8af29d0a9efaa87 1778 python-llfuse_1.4.1+dfsg-3.dsc 437f3e17c1fcf23b363a81296f15cf8a44174b8f 144840 python-llfuse_1.4.1+dfsg-3.debian.tar.xz 595367339c42b4b8874852c0cfc86cc88a24d394 9420 python-llfuse_1.4.1+dfsg-3_source.buildinfo Checksums-Sha256: b2f45d5cf11aa1d2bd779ff4a1f02b8aedfc30b3c9ed272cf1e01a38c73660f7 1778 python-llfuse_1.4.1+dfsg-3.dsc 893cc4e80924996de0c7b9e163893a81fdc5cb5af8394f2a4941b9d7d490903d 144840 python-llfuse_1.4.1+dfsg-3.debian.tar.xz d7d3a4ac687a4f56b9374dd39544911d2ac3493c21f2779f5f2dcd1fa5c19ba3 9420 python-llfuse_1.4.1+dfsg-3_source.buildinfo Files: ea9d69ade7503f2b468393e42bc6dc75 1778 python optional python-llfuse_1.4.1+dfsg-3.dsc 851dd0f3979ca495f2a306fee59d6c81 144840 python optional python-llfuse_1.4.1+dfsg-3.debian.tar.xz ed956c868d0dfb9337084ad74a63a529 9420 python optional python-llfuse_1.4.1+dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iIsEARYIADMWIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZgkjvhUcc3JhbWFjaGVy QGRlYmlhbi5vcmcACgkQIZNrNmAPzYkj+wEA6LyKBSnIsgrRuD1r/CnrjNPABYx1 TfN0+hRnPHDDP98A/jUYVqtI0Ix9T3vftzU+CYJpAZyMWm/GJJPEVNBYa7kA =fc0N -END PGP SIGNATURE- pgp2BcGa0AEqp.pgp Description: PGP signature --- End Message ---
Bug#1062404: marked as done (orthanc-python: flaky autopkgtest: Test failed with)
Your message dated Sun, 31 Mar 2024 11:06:09 + with message-id and subject line Bug#1062404: fixed in orthanc-python 4.1+ds-3 has caused the Debian Bug report #1062404, regarding orthanc-python: flaky autopkgtest: Test failed with 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.) -- 1062404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: orthanc-python Version: 4.1+ds-2 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package. I noticed that it regularly fails on several architectures because it currently blocks glibc. Unfortunately the log seems to be missing the actual problem as it ends with: 45s W0131 12:12:35.955520 MAIN FromDcmtkBridge.cpp:382] Loading external DICOM dictionary: "/usr/share/libdcmtk17/private.dic" 45s Test failed with Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Don't hesitate to reach out if you need help and some more information from our infrastructure. Paul E.g. https://ci.debian.net/packages/o/orthanc-python/testing/amd64/42028712/ https://ci.debian.net/packages/o/orthanc-python/testing/s390x/42546158/ https://ci.debian.net/packages/o/orthanc-python/testing/ppc64el/42417046/ OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: orthanc-python Source-Version: 4.1+ds-3 Done: Sebastien Jodogne We believe that the bug you reported is fixed in the latest version of orthanc-python, 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 1062...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Jodogne (supplier of updated orthanc-python 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, 30 Mar 2024 14:06:27 +0100 Source: orthanc-python Architecture: source Version: 4.1+ds-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Sebastien Jodogne Closes: 1062404 Changes: orthanc-python (4.1+ds-3) unstable; urgency=medium . * autopkgtest: Fix the waiting for Orthanc to start. Closes: #1062404 Checksums-Sha1: d4c0fd78fe94264fcf57badc7d41b01a9bc52d7a 2244 orthanc-python_4.1+ds-3.dsc c0f40ecf86e7e5c938ffc7050eef44fe3585043c 5348 orthanc-python_4.1+ds-3.debian.tar.xz ec9edb757f2b45319097714ac6b7a0ca3dc7e474 15899 orthanc-python_4.1+ds-3_source.buildinfo Checksums-Sha256: 78ca1192b4b53e92ef37dcc2780651f67c40f06290b96e7af291ba3d121e19ba 2244 orthanc-python_4.1+ds-3.dsc 7ba92e0785669ec42ee65abe035d6bbce1b68997493b34c711393c28853b6d0f 5348 orthanc-python_4.1+ds-3.debian.tar.xz 33607bf8402958328de04604acfd64e809810879de45682e986f7d94e779231c 15899 orthanc-python_4.1+ds-3_source.buildinfo Files: 4d70c4c1d0adb58e0978ecfd8dba4ae8 2244 science optional orthanc-python_4.1+ds-3.dsc 6d01dee147b14bfb9eea35f40945cd1f 5348 science optional orthanc-python_4.1+ds-3.debian.tar.xz 863055c4c40dc0a4e88cac2d643af3bc 15899 science optional orthanc-python_4.1+ds-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEk76fGX7V0MMOWT2Lp3ZYKzEqw10FAmYIIowUHHMuam9kb2du ZUBnbWFpbC5jb20ACgkQp3ZYKzEqw12vMw//SpWQ3Ku5wLGv693eTDInB+7CbHsX JRFEFLwucBUe/dk7FcTXvxcCijBAdd397//BJIoUd+RN5pdQR4lPkYDbBmSRX5QU ZLa61+mE/KfM55zht5yOfB8cW3tmcFMlWIrmCpFOnN/2JP3/UbJHhvf84W8IVQ/G kcI+SGalV2OwczjIInxHFsRSw2hICejIEtzjC1gp3xD7pNINHealHqHO8F+calFC km+MYR74hT8kZ6kFyL00nKts+cygBazdzXJehGyXnih//t2bWyMzxdC63zVWpyvS sz7Fj+w59TYyrkVxArOWqQ3OqUtus+YIUJnJKYcGPzxQ5dh4zvnxikzm5O4GpI0G lgvrl9H10Z1ZygGxPl35I2Fk98y2RH6j1fP8Eo+dBkTywsced7OV6Xa9gH13ItM4 eB58Ges7N7WUN2ph8a0EKEFm27H+VW8oX7o1NRjpmUAk/JEsXMxGFao/lNWpNFgT evDL5dqsl6PzkW8sKS/UYUhCgnHCyxzANMkTojkpuxfruw3CJ/eJ1uQM3ghL6V2I 3H+Onsd7z3nqXOxBpG01fVVg6k2TX0goyOV3a5pz4FBHaU1IJhpXZfGGwY8qvs/q
Bug#1039701: marked as done (libsigrok4: Built-in driver list is empty when compiled with LTO)
Your message dated Sun, 31 Mar 2024 11:42:33 +0100
with message-id
and subject line Re: [Pkg-electronics-devel] Bug#1039701: libsigrok4: Built-in
driver list is empty when compiled with LTO
has caused the Debian Bug report #1039701,
regarding libsigrok4: Built-in driver list is empty when compiled with LTO
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.)
--
1039701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsigrok4
Version: 0.5.2-4
Severity: normal
Tags: patch upstream
This bug only shows up when libsigrok is compiled with LTO and was reported
(https://sigrok.org/bugzilla/show_bug.cgi?id=1433) and fixed
(http://sigrok.org/gitweb/?p=libsigrok.git;a=commit;h=da5286bfa5d2dad1e24b9c9442c9875332d84e64)
upstream.
I have opened a MR on
https://salsa.debian.org/electronics-team/sigrok/libsigrok/-/merge_requests/3.
Groet, Regards,
Victor Westerhuis
-- System Information:
Debian Release: bookworm/sid
APT prefers lunar-updates
APT policy: (500, 'lunar-updates'), (500, 'lunar-security'), (500, 'lunar'),
(100, 'lunar-backports')
Architecture: amd64 (x86_64)
Kernel: Linux 6.2.0-23-generic (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libsigrok4 depends on:
ii libbluetooth3 5.66-0ubuntu1
ii libc6 2.37-0ubuntu2
ii libftdi1-2 1.5-6build2
ii libglib2.0-0 2.76.1-1
ii libhidapi-hidraw0 0.13.1-1
ii libieee1284-3 0.2.11-14build2
ii libserialport0 0.1.1-4
ii libusb-1.0-0 2:1.0.26-1
ii libzip41.7.3-1ubuntu2
libsigrok4 recommends no packages.
libsigrok4 suggests no packages.
-- no debconf information
>From a4aefa75a767e90fd4013ee9c307934edff28c56 Mon Sep 17 00:00:00 2001
From: Victor Westerhuis
Date: Wed, 28 Jun 2023 12:46:14 +0200
Subject: [PATCH] Unbreak list of builtin drivers for LTO configurations
LP: 2025248
---
...k-list-of-builtin-drivers-for-LTO-co.patch | 74 +++
debian/patches/series | 1 +
2 files changed, 75 insertions(+)
create mode 100644
debian/patches/03-driver_list-unbreak-list-of-builtin-drivers-for-LTO-co.patch
diff --git
a/debian/patches/03-driver_list-unbreak-list-of-builtin-drivers-for-LTO-co.patch
b/debian/patches/03-driver_list-unbreak-list-of-builtin-drivers-for-LTO-co.patch
new file mode 100644
index ..82ab8469
--- /dev/null
+++
b/debian/patches/03-driver_list-unbreak-list-of-builtin-drivers-for-LTO-co.patch
@@ -0,0 +1,74 @@
+From: Gerhard Sittig
+Date: Tue, 3 Nov 2020 18:25:18 +0100
+Subject: driver_list: unbreak list of builtin drivers for LTO configurations
+
+Check for the availability of the "no_reorder" linker attribute, which
+keeps the list of builtin drivers in shape on LTO enabled build setups.
+Keep backwards compatibility for platforms which lack support for the
+"no_reorder" attribute. Phrase the implementation such that other
+keywords as well as user provided external specs are possible.
+
+This resolves bug #1433.
+
+Submitted-By: Ivan Mironov
+
+Origin:
http://sigrok.org/gitweb/?p=libsigrok.git;a=commit;h=3decd3b1f0cbb3a035f72e9eade42279d0507b89
+Bug: https://sigrok.org/bugzilla/show_bug.cgi?id=1433
+---
+ src/driver_list_start.c | 1 +
+ src/driver_list_stop.c | 1 +
+ src/libsigrok-internal.h | 10 ++
+ 3 files changed, 12 insertions(+)
+
+diff --git a/src/driver_list_start.c b/src/driver_list_start.c
+index 7b6c775..535e331 100644
+--- a/src/driver_list_start.c
b/src/driver_list_start.c
+@@ -28,6 +28,7 @@
+ */
+
+ SR_PRIV const struct sr_dev_driver *sr_driver_list__start[]
++ SR_DRIVER_LIST_NOREORDER
+ __attribute__((section (SR_DRIVER_LIST_SECTION),
+ used, aligned(sizeof(struct sr_dev_driver *
+ = { NULL /* Dummy item, as zero length arrays are not allowed by C99 */ };
+diff --git a/src/driver_list_stop.c b/src/driver_list_stop.c
+index ff2c51d..eefda05 100644
+--- a/src/driver_list_stop.c
b/src/driver_list_stop.c
+@@ -28,6 +28,7 @@
+ */
+
+ SR_PRIV const struct sr_dev_driver *sr_driver_list__stop[]
++ SR_DRIVER_LIST_NOREORDER
+ __attribute__((section (SR_DRIVER_LIST_SECTION),
+ used, aligned(sizeof(struct sr_dev_driver *
+ = { NULL /* Dummy item, as zero length arrays are not allowed by C99 */ };
+diff --git a/src/libsigrok-internal.h b/src/libsigrok-internal.h
+index
Bug#1066964: marked as done (ITA: newlib -- C library and math library for)
Your message dated Sun, 31 Mar 2024 11:02:51 + with message-id and subject line Bug#1066964: fixed in newlib 4.4.0.20231231-3 has caused the Debian Bug report #1066964, regarding ITA: newlib -- C library and math library for 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.) -- 1066964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066964 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: normal The newlib package is orphaned as its last maintianer, Agustin Henze no longer find the time to maintain it. I got his approval to orphan it, an it is now listing Debian QA Group as the maintainer. See https://tracker.debian.org/pkg/newlib > for the details. Note, picolib can be an alternative to newlib. -- Happy hacking Petter Reinholdtsen --- End Message --- --- Begin Message --- Source: newlib Source-Version: 4.4.0.20231231-3 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of newlib, 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 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated newlib 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, 30 Mar 2024 13:03:01 +0100 Source: newlib Architecture: source Version: 4.4.0.20231231-3 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 1066964 Changes: newlib (4.4.0.20231231-3) unstable; urgency=medium . * Adopt the package for the Debian GCC Maintainers. Closes: #1066964. * amdgcn: Implement proper locks, taken from newlib trunk. Checksums-Sha1: 5620f0e995c673f621a202213604497d490114fb 2356 newlib_4.4.0.20231231-3.dsc cc6e136635ef7bf12d39f0fac2e3af2abd168d37 16376 newlib_4.4.0.20231231-3.debian.tar.xz 1ef9b88cc8215198bfb6a1f086b4a1768ca652cb 6718 newlib_4.4.0.20231231-3_source.buildinfo Checksums-Sha256: 8d9e0cc289d027e65e5c3caec5629aec0da92b5680405953cd3d434468441436 2356 newlib_4.4.0.20231231-3.dsc b81295fd544253581fdd70e458bd8886e90a7744792301f8a21bc86042b8d9bb 16376 newlib_4.4.0.20231231-3.debian.tar.xz 4ae5e1637730d89caa5e7216d6f41b999439b3bf7074fab34a359536ba2d3738 6718 newlib_4.4.0.20231231-3_source.buildinfo Files: 926b1328182bc741ad5b20e7df42b564 2356 devel optional newlib_4.4.0.20231231-3.dsc 93e94147fe3605aa28bbec287c86efd4 16376 devel optional newlib_4.4.0.20231231-3.debian.tar.xz 6f1125ea0de335872d4e9496ef9a51f1 6718 devel optional newlib_4.4.0.20231231-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmYIA0gQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9aLTEACJwa/M/wOdItM1EsqjFKp2VXL0OZRNW1U/ JmyYUbabNjW9mOhwdiVnuQTcFNkA1sVvYCBaCHhh/oqnE4HSaWDTmbWrS3Dy5+e1 LkMh4iiiqcLTm45yFHmPypXB2TOy+8ASGdRssJ3fE8nmHogjZuhVDi9pkbgIhT8O 0fu14/8mdYOuOj0/1LpA9Vl4JZw+0xol35vuUn5VjcjF419mb/iShPpGQwtlfjzB Q5Jg89rfPT/ce18ZR8xuHo8yAd4vRzqEklEkZxp3fIf77tZNiEtUqg/KHP0KCrIb qdJK3Vh9aFK2+Fims4u+1ApLHLHtXQJmOrPQMpuEck3db9Af7RKc3dSMsgeQFPl1 fbiSY0loAMF4NCHwf09Id9bCq32nxZQ4cpQVhvzTWrPlAzkPgqCXpuaYGe2cNk7b nd2EKIzs6WqAUjJ9M6X991n8z1OQ+kcuFT1XvTBDRXKgp0x9wuA/L2kTRehIHvDB aRLwmmSICwZzoNVgOEvL++ZNLDvnr23OJNm5XV9vGtXDVTSLaHj25tqSpFGc24Gl rjlfxgg1kbi1HDExmnbIbhHMdoQ4HykEXsGzsd1APgxapeTUZgjep7dwjRKDVpSM l6LvARB+X0EqLju+mUZK8dzD3uqR1wZ942rmKEmkVcv+VMZt+l50vbQbRmwDWnN4 m+I/C0rayA== =DrDj -END PGP SIGNATURE- pgpk28SgjU7qL.pgp Description: PGP signature --- End Message ---
Bug#1018413: marked as done (mom: build-depends on python3-nose or uses it for autopkgtest)
Your message dated Sun, 31 Mar 2024 10:58:05 + with message-id and subject line Bug#1018413: fixed in mom 0.6.4-0.1 has caused the Debian Bug report #1018413, regarding mom: build-depends on python3-nose or uses it for autopkgtest 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.) -- 1018413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018413 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mom Version: 0.6.0-2 User: python-modules-t...@lists.alioth.debian.org Usertags: nose-rm Dear Maintainer, Your package still uses nose [1], which is an obsolete testing framework for Python, dead and unmaintained since 2015 [2][3]. If you received this bug report, it means that your package either has a build-dependency on python3-nose or uses that package in debian/tests/control. If that is not the case, please reply and CC me explicitly. Please port your package to one of the alternatives: nose2 [4], pytest [5] or unittest from Python standard library [6]. There is a script called nose2pytest [7] which can assist with migrating from nose to pytest. This mass bug filing was discussed on debian-devel in [8]. [1]: https://tracker.debian.org/pkg/nose [2]: https://github.com/nose-devs/nose/commit/0f40fa995384afad [3]: https://pypi.org/project/nose/#history [4]: https://docs.nose2.io/en/latest/ [5]: https://docs.pytest.org/en/latest/ [6]: https://docs.python.org/3/library/unittest.html [7]: https://github.com/pytest-dev/nose2pytest [8]: https://lists.debian.org/debian-devel/2022/08/msg00184.html -- Dmitry Shachnev --- End Message --- --- Begin Message --- Source: mom Source-Version: 0.6.4-0.1 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of mom, 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 1018...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated mom 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, 30 Mar 2024 13:34:45 +0100 Source: mom Architecture: source Version: 0.6.4-0.1 Distribution: unstable Urgency: medium Maintainer: Dmitry Smirnov Changed-By: Alexandre Detiste Closes: 1014781 1018413 Changes: mom (0.6.4-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream release. (Closes: #1014781) * Fix watchfile for new GitHub API * Remove obsolete build dependencies: * python3-mock * python3-nose (Closes: #1018413) * Use new dh-sequence-python3 * janitor: * Add upstream metadata * Set upstream metadata fields: Repository. * Update standards version to 4.6.2, no changes needed. * Bump debhelper from old 12 to 13. Checksums-Sha1: bab066a33efccc1822a70c2f69096ce5283b98d1 1909 mom_0.6.4-0.1.dsc 8772c4ebb50522115285d71aa38eb1ea0f5afd78 61156 mom_0.6.4.orig.tar.xz 74f560d3d95a67653e8ef176aebb24df4c649dbf 6048 mom_0.6.4-0.1.debian.tar.xz a0d4025938ed69d3508fb8b9f3e4ceab4145ee3b 7838 mom_0.6.4-0.1_source.buildinfo Checksums-Sha256: 8b7e22e0cd930ad5b49b5f1646724fa1642a87a7d07e699012d1ee7d8574cadc 1909 mom_0.6.4-0.1.dsc 0181692fb57d54a2261a6184c975e8ec345ab0b389afc9a9532bcab0226a8d01 61156 mom_0.6.4.orig.tar.xz da9a5b526d92624715e678e44c36114d54aa85ef27ffa31b0b2d0f79a076601f 6048 mom_0.6.4-0.1.debian.tar.xz bc16301440dc77e996b43c119ae46fe2b1630f68651a87c4424db36a2699c612 7838 mom_0.6.4-0.1_source.buildinfo Files: ce49da9ef027324a843c160c7a3c3318 1909 admin optional mom_0.6.4-0.1.dsc 866c1a958abc32021b088c0849a293ea 61156 admin optional mom_0.6.4.orig.tar.xz 46418acb335053334b5e1e0a561f62fc 6048 admin optional mom_0.6.4-0.1.debian.tar.xz b655edd187b0603c2fa92736d6633a42 7838 admin optional mom_0.6.4-0.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmYIGMURHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBof6BAAsBS86XD0OBblqWJIhDCOvF6DekPCj+2M HsUP1apJZaRjsQ0keYrf0DF/iEbGw4OOdW/2OMJjxtH8z/ISOvVYROVcGzHVI8i9 EKGMMoLU+y9p95mZfoGsqJCarLmyl/aWIjBkBISa9fnDi8vV0wNQaatTmiAOTr1m vPxrBZP6RMPV0f7XWUYiOl7kID8JR2GQCmpLoGHAI6mC8LWFAXXVtsbi8AUNexJT
Bug#1068105: marked as done (drop the Python3-Version attribute)
Your message dated Sun, 31 Mar 2024 10:56:31 + with message-id and subject line Bug#1068105: fixed in libsbml 5.20.2+dfsg-3 has caused the Debian Bug report #1068105, regarding drop the Python3-Version attribute 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.) -- 1068105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libsbml Version: 5.20.2+dfsg-2.1 Severity: important Tags: sid trixie ftbfs patch User: debian-pyt...@lists.debian.org Usertags: python3.12 please drop the Python3-Version attribute. we're not using these anymore, and it prevents the package to be built with 3.12. diff -Nru libsbml-5.20.2+dfsg/debian/control libsbml-5.20.2+dfsg/debian/control --- libsbml-5.20.2+dfsg/debian/control 2024-03-09 18:21:16.0 + +++ libsbml-5.20.2+dfsg/debian/control 2024-03-29 13:44:06.0 + @@ -37,7 +37,6 @@ Vcs-Browser: https://salsa.debian.org/med-team/libsbml Vcs-Git: https://salsa.debian.org/med-team/libsbml.git Homepage: http://www.sbml.org/ -X-Python3-Version: 3.11 Rules-Requires-Root: no Testsuite: autopkgtest-pkg-python --- End Message --- --- Begin Message --- Source: libsbml Source-Version: 5.20.2+dfsg-3 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of libsbml, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated libsbml 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, 30 Mar 2024 21:36:28 +0100 Source: libsbml Architecture: source Version: 5.20.2+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 1068105 Changes: libsbml (5.20.2+dfsg-3) unstable; urgency=medium . * Drop the Python3-Version attribute Closes: #1068105 * Fix doc-base file Checksums-Sha1: f1ae2819fd6e4130e9a44e1ff162270c96bc7de9 3825 libsbml_5.20.2+dfsg-3.dsc ffddb3620d0d366fd534269ad6e5d248b40b6779 24008 libsbml_5.20.2+dfsg-3.debian.tar.xz 01a89a6bdbcbf9e3ec29accc85423f0173da3f72 34054 libsbml_5.20.2+dfsg-3_source.buildinfo Checksums-Sha256: 262c901b623314ac2fd71fc4cd0805958b1b8475b9ecdae4f9734041d244e7dd 3825 libsbml_5.20.2+dfsg-3.dsc 0371041516597fe4e35f4407e948f20e7bf2ab3f17aec7daed2e733dbfc4 24008 libsbml_5.20.2+dfsg-3.debian.tar.xz a2615e697b391e0f2514ce926a7015b697b50a6692ea3f63171225a79b6a1cdb 34054 libsbml_5.20.2+dfsg-3_source.buildinfo Files: 0e893ebf504922945ad37668661d1da3 3825 science optional libsbml_5.20.2+dfsg-3.dsc b131bf50da5c79ed7a13d25d49cb32d6 24008 science optional libsbml_5.20.2+dfsg-3.debian.tar.xz 310d157430218fdb5d21cba2d19324f0 34054 science optional libsbml_5.20.2+dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJCBAEBCgAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmYIeCAOHHRpbGxlYUBy a2kuZGUACgkQV4oElNHGRtFcJw//aaUhTPfU6s7eOGnuO4p0MW3YA/he+cDu+vFU rA3yhOcSfxS6EYNPwhhIy6U8pKFAZNgr8sj3FxyY3HF2FGsQ5Ef8eZGYNGEtObEj DqcjwWw/hx7kVKTV/5sK4mkvppkbJGJpp4vZ/vqQwJ3kLd1vWeTLvl1c/6gCEFHX Elh5pBkwKzdfFv+nmKinFB8J40th8kgB2BezDtAkJEIqbDPLKER9mYiID6TR5WtT WXxYiDhihFx02+my0uX8AEPvkru/iN0ghQBBBCEVh6HmfzhUf3fIOaCDmxoNH3Hb nMmohyrM1UuSSMBIGXgZD4RLpZ0+V5FD5TG8/n79OcdUTTnmHRxKusMXB6IRe+97 /M1qtQ8LSb8OzaL24GMZ/Z8gae/5gsNRxaXcnTUl5dKUZOW42VySDc5fXOwJELsz r15KkgQDMqItZ2/Y5ZsARzh8sESsYkm6FseGq1EEbLx4+9dXyxfMkOB6QJv7BkOd aCmiECuNOMAISq7/jrAxjU9S0EN2F63Ti3IOqXVn9u1raqyilkzvsgPSZWz4eTtl frhZpsGYcUU0xJpmkx8FZxw0qp6TblTVOhn+6L2O+QAfKtW7Wir6jdjwNkBuHd6x /rHn5yL8PiP4/Qp6Cm31O5HJGL8cTTJutT/yIrx7O5GYcbvVew5I0C4/sXFRSEdk nPYnl8M= =LZ5g -END PGP SIGNATURE- pgpQiTgt1MPLZ.pgp Description: PGP signature --- End Message ---
Bug#1014781: marked as done (momd crashing due to error in HypervisorInterfaces/libvirtInterface.py)
Your message dated Sun, 31 Mar 2024 10:58:05 +
with message-id
and subject line Bug#1014781: fixed in mom 0.6.4-0.1
has caused the Debian Bug report #1014781,
regarding momd crashing due to error in HypervisorInterfaces/libvirtInterface.py
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1014781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mom
Version: 0.6.0-2
Severity: grave
Tags: patch
Justification: renders package unusable
Hello Dear Maintainer,
Looks like momd is "broken" in bullseye :-(
Service is failling every start with exception :
Jul 11 20:48:21 minas-anor momd[149966]: File
"/usr/lib/python3/dist-packages/mom/HypervisorInterfaces/libvirtInterface.py",
line 128, in _domainGetPid
Jul 11 20:48:21 minas-anor momd[149966]: matches =
re.findall(r"^\s*(\d+)\s+.*" + uuid, p1, re.M)
Jul 11 20:48:21 minas-anor momd[149966]: File
"/usr/lib/python3.9/re.py", line 241, in findall
Jul 11 20:48:21 minas-anor momd[149966]: return _compile(pattern,
flags).findall(string)
Jul 11 20:48:21 minas-anor momd[149966]: TypeError: cannot use a string
pattern on a bytes-like object
Comparing with current code for libvirtInterface.py in mom github
https://github.com/oVirt/mom/blob/master/mom/HypervisorInterfaces/libvirtInterface.py
I made modification in libvirtInterface.py line 128
#p1 = Popen(["ps", "axww"], stdout=PIPE).communicate()[0]
p1 = Popen(["ps", "axww"], stdout=PIPE).communicate()[0].decode("utf-8")
Sorry for not attaching a patch file, not sure it is needed for this change
After this little change momd is now working correctly and tacking care of VM
ballooning :-)
For the moment, i'm only using KVM + momd + balloning on test servers
(that's why i only discovered the issue now)
don't know if some other users are impacted in production.
I suppose bug is related to python 3.9, but not shure at all
Think a little "patch" release will be needed for debian package
Thank you for your time maintaining debian :-))
Here more complete log extract if needed
Jul 11 20:48:21 minas-anor momd[149966]: 2022-07-11 20:48:21,840 -
mom.GuestManager - ERROR - Guest Manager crashed
Jul 11 20:48:21 minas-anor momd[149966]: Traceback (most recent call last):
Jul 11 20:48:21 minas-anor momd[149966]: File
"/usr/lib/python3/dist-packages/mom/GuestManager.py", line 86, in run
Jul 11 20:48:21 minas-anor momd[149966]:
self._spawn_guest_monitors(domain_list)
Jul 11 20:48:21 minas-anor momd[149966]: File
"/usr/lib/python3/dist-packages/mom/GuestManager.py", line 112, in
_spawn_guest_monitors
Jul 11 20:48:21 minas-anor momd[149966]: info =
self.hypervisor_iface.getVmInfo(id)
Jul 11 20:48:21 minas-anor momd[149966]: File
"/usr/lib/python3/dist-packages/mom/HypervisorInterfaces/libvirtInterface.py",
line 189, in getVmInfo
Jul 11 20:48:21 minas-anor momd[149966]: data['pid'] =
self._domainGetPid(data['uuid'])
Jul 11 20:48:21 minas-anor momd[149966]: File
"/usr/lib/python3/dist-packages/mom/HypervisorInterfaces/libvirtInterface.py",
line 128, in _domainGetPid
Jul 11 20:48:21 minas-anor momd[149966]: matches =
re.findall(r"^\s*(\d+)\s+.*" + uuid, p1, re.M)
Jul 11 20:48:21 minas-anor momd[149966]: File "/usr/lib/python3.9/re.py",
line 241, in findall
Jul 11 20:48:21 minas-anor momd[149966]: return _compile(pattern,
flags).findall(string)
Jul 11 20:48:21 minas-anor momd[149966]: TypeError: cannot use a string pattern
on a bytes-like object
Jul 11 20:48:26 minas-anor momd[149966]: 2022-07-11 20:48:26,825 - mom - ERROR
- Thread 'GuestManager' has exited
-- System Information:
Debian Release: 11.4
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'stable-security')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-8-amd64 (SMP w/6 CPU threads)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_IE:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mom depends on:
ii libvirt-daemon 7.0.0-3
ii libvirt-daemon-system 7.0.0-3
ii procps 2:3.3.17-5
ii python33.9.2-3
ii python3-libvirt7.0.0-2
ii python3-six1.16.0-2
mom recommends no packages.
mom suggests no packages.
-- Configuration Files:
/etc/momd.conf changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mom
Source-Version:
Bug#1068047: marked as done (Suspicious commit merged in 2021 from account responsible for xz backdoor)
Your message dated Sun, 31 Mar 2024 10:46:58 + with message-id and subject line Bug#1068047: fixed in libarchive 3.7.2-2 has caused the Debian Bug report #1068047, regarding Suspicious commit merged in 2021 from account responsible for xz backdoor 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.) -- 1068047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libarchive13t64 Version: 3.7.2-1.1 Severity: important X-Debbugs-Cc: r...@debian.org So far it looks like no one has been able to figure out an obvious way for this to be exploitable, but I wanted to make sure that you were aware of this upstream issue: https://github.com/libarchive/libarchive/pull/1609 The author of this commit is the same GitHub account that was used to create the xz backdoor. Upstream has merged a revert of this change at: https://github.com/libarchive/libarchive/pull/2101 It may be worth expediting getting this change into Debian in case the potential attacker knows something that we don't. However, I don't have any reason to currently believe that this is a security vulnerability, so I've kept the severity at important and not applied the security tag. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libarchive13t64 depends on: ii libacl12.3.2-1 ii libbz2-1.0 1.0.8-5.1 ii libc6 2.37-15.1 ii liblz4-1 1.9.4-1+b2 ii liblzma5 5.6.1+really5.4.5-1 ii libnettle8t64 3.9.1-2.2 ii libxml22.9.14+dfsg-1.3+b2 ii libzstd1 1.5.5+dfsg2-2 ii zlib1g 1:1.3.dfsg-3.1 libarchive13t64 recommends no packages. Versions of packages libarchive13t64 suggests: pn lrzip -- no debconf information --- End Message --- --- Begin Message --- Source: libarchive Source-Version: 3.7.2-2 Done: Peter Pentchev We believe that the bug you reported is fixed in the latest version of libarchive, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Pentchev (supplier of updated libarchive 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, 30 Mar 2024 20:11:06 +0200 Source: libarchive Architecture: source Version: 3.7.2-2 Distribution: unstable Urgency: medium Maintainer: Peter Pentchev Changed-By: Peter Pentchev Closes: 1068047 Changes: libarchive (3.7.2-2) unstable; urgency=medium . [ Luca Boccassi ] * libarchive-dev: depend on -dev packages in an attempt to fix pkg-config --static --libs Addresses: 1056317; more work needed on libarchive's own configure tests . [ Peter Pentchev ] * Acknowledge Lukas Märdian 64-bit-time_t-related NMU. Thanks! * Add the year 2024 to my debian/* copyright notice. * Re-sort the dependencies lists in the debian/control file. * Switch the pkg-config dependency over to pkgconf. * Add the robust-error-reporting upstream patch. Closes: #1068047 Checksums-Sha1: a9840b89785c21b07962f5560890a62b70f17b54 2714 libarchive_3.7.2-2.dsc d8a0948b6814ee525e85ec44003af28470f84f15 27352 libarchive_3.7.2-2.debian.tar.xz Checksums-Sha256: 9fd4fe779a50bf73660bf59b3af0c6c8cbe32bcb48b4b8922eb23cd90d9bde9c 2714 libarchive_3.7.2-2.dsc cb596068a92fe55060ea5e46a5da8c9e9cd37b03a17bff7bc3cea62baa1c455e 27352 libarchive_3.7.2-2.debian.tar.xz Files: dec84a91f32a212810d5a4072bc0fb15 2714 libs optional libarchive_3.7.2-2.dsc a09a0817264db40619efeacb80a8d304 27352 libs optional libarchive_3.7.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAmYIWTYQHHJvYW1AZGVi aWFuLm9yZwAKCRBlHu+wJSffE/3WD/0Y9dKqonT5upiqkcr2XIRTlKXOoPgQvh+T
Bug#1067904: marked as done ($frontend-$version-for-host: versioned dependency too strict)
Your message dated Sun, 31 Mar 2024 10:42:46 +
with message-id
and subject line Bug#1067904: fixed in gcc-14 14-20240330-1
has caused the Debian Bug report #1067904,
regarding $frontend-$version-for-host: versioned dependency too strict
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.)
--
1067904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-14
Severity: wishlist
Tags: patch
User: helm...@debian.org
Usertags rebootstrap
Hi Matthias,
thanks for merging my -for-host work. I'm looking into making practical
use of it and a major issue is the following dependency:
$FRONTEND-$VERSION-for-host:$DEB_HOST_ARCH ->
$FRONTEND-$VERSION-$DEB_HOST_GNU_TYPE (= ${gcc:Version})
While this works nicely for native compilers, trying to use the
-for-host package with a cross toolchain is doomed to fail, because it
always has different version. The equal constraint is too strict to make
practical use of these -for-host packages. I think we should change (=
${gcc:Version}) to (>= ${gcc:SoftVersion}) as is done elsewhere. Do you
agree?
I'm attaching the obvious patch.
Helmut
commit 843e8ae7602a0ec16c67d7064396fa2acd1182cd
Author: Helmut Grohne
Date: Fri Mar 22 09:35:04 2024 +0100
use gcc:SoftVersion for -for-host dependencies
diff --git a/debian/control.m4 b/debian/control.m4
index 4b6c61b8..61a4d3a8 100644
--- a/debian/control.m4
+++ b/debian/control.m4
@@ -804,7 +804,7 @@ Package: gcc`'PV`'-for-host
Architecture: ifdef(`TARGET',`TARGET',`any')
TARGET_PACKAGE`'dnl
Multi-Arch: same
-Depends: BASEDEP, gcc`'PV`'${target:suffix} (= ${gcc:Version}),
+Depends: BASEDEP, gcc`'PV`'${target:suffix} (>= ${gcc:SoftVersion}),
cpp`'PV`'-for-host (= ${gcc:Version}), ${misc:Depends}
BUILT_USING`'dnl
Description: GNU C compiler for the host architecture
@@ -929,7 +929,7 @@ Architecture: ifdef(`TARGET',`TARGET',`any')
TARGET_PACKAGE`'dnl
Multi-Arch: same
Section: ifdef(`TARGET',`devel',`interpreters')
-Depends: BASEDEP, cpp`'PV`'${target:suffix} (= ${gcc:Version}), ${misc:Depends}
+Depends: BASEDEP, cpp`'PV`'${target:suffix} (>= ${gcc:SoftVersion}), ${misc:Depends}
BUILT_USING`'dnl
Description: GNU C preprocessor for the host architecture
A macro processor that is used automatically by the GNU C compiler
@@ -1019,7 +1019,7 @@ Package: g++`'PV`'-for-host
Architecture: ifdef(`TARGET',`TARGET',`any')
TARGET_PACKAGE`'dnl
Multi-Arch: same
-Depends: BASEDEP, g++`'PV`'${target:suffix} (= ${gcc:Version}),
+Depends: BASEDEP, g++`'PV`'${target:suffix} (>= ${gcc:SoftVersion}),
gcc`'PV`'-for-host (= ${gcc:Version}), ${misc:Depends}
BUILT_USING`'dnl
Description: GNU C++ compiler for the host architecture
@@ -2522,7 +2522,7 @@ Package: gobjc++`'PV`'-for-host
Architecture: ifdef(`TARGET',`TARGET',`any')
TARGET_PACKAGE`'dnl
Multi-Arch: same
-Depends: BASEDEP, gobjc++`'PV`'${target:suffix} (= ${gcc:Version}),
+Depends: BASEDEP, gobjc++`'PV`'${target:suffix} (>= ${gcc:SoftVersion}),
gobjc`'PV`'-for-host (= ${gcc:Version}), g++`'PV`'-for-host (= ${gcc:Version}),
${misc:Depends}
BUILT_USING`'dnl
@@ -2599,7 +2599,7 @@ Package: gobjc`'PV`'-for-host
Architecture: ifdef(`TARGET',`TARGET',`any')
TARGET_PACKAGE`'dnl
Multi-Arch: same
-Depends: BASEDEP, gobjc`'PV`'${target:suffix} (= ${gcc:Version}),
+Depends: BASEDEP, gobjc`'PV`'${target:suffix} (>= ${gcc:SoftVersion}),
gobjc`'PV`'-for-host (= ${gcc:Version}), ${misc:Depends}
BUILT_USING`'dnl
Description: GNU Objective-C compiler for the host architecture
@@ -2844,7 +2844,7 @@ Package: gfortran`'PV`'-for-host
Architecture: ifdef(`TARGET',`TARGET',`any')
TARGET_PACKAGE`'dnl
Multi-Arch: same
-Depends: BASEDEP, gfortran`'PV`'${target:suffix} (= ${gcc:Version}),
+Depends: BASEDEP, gfortran`'PV`'${target:suffix} (>= ${gcc:SoftVersion}),
gcc`'PV`'-for-host (= ${gcc:Version}), ${misc:Depends}
BUILT_USING`'dnl
Description: GNU Fortran compiler for the host architecture
@@ -3111,7 +3111,7 @@ Package: gccgo`'PV`'-for-host
Architecture: ifdef(`TARGET',`TARGET',`any')
TARGET_PACKAGE`'dnl
Multi-Arch: same
-Depends: BASEDEP, gccgo`'PV`'${target:suffix} (= ${gcc:Version}),
+Depends: BASEDEP, gccgo`'PV`'${target:suffix} (>= ${gcc:SoftVersion}),
gcc`'PV`'-for-host (= ${gcc:Version}), ${misc:Depends}
BUILT_USING`'dnl
Description: GNU Go compiler for the host architecture
@@ -3821,7 +3821,7 @@ Package: gnat`'PV`'-for-host
Architecture: ifdef(`TARGET',`TARGET',`any')
TARGET_PACKAGE`'dnl
Multi-Arch: same
-Depends: BASEDEP, gnat`'PV`'${target:suffix} (= ${gcc:Version}),
Bug#1067272: marked as done (haskell-gi-glib: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 1)
Your message dated Sun, 31 Mar 2024 10:43:57 +
with message-id
and subject line Bug#1067272: fixed in haskell-haskell-gi 0.26.7-4
has caused the Debian Bug report #1067272,
regarding haskell-gi-glib: FTBFS: make: ***
[/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 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.)
--
1067272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-gi-glib
Version: 2.0.29-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep
> dh_installdirs -A
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-gi-glib-doc.substvars
> dh_installdirs -plibghc-gi-glib-doc \
>
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 2] Compiling Main ( Setup.hs, Setup.o )
> [2 of 2] Linking debian/hlibrary.setup
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'configure_recipe'
> Running find . ! -newer /tmp/CDluqVSv3P -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-gi-glib-dev
> libghc-gi-glib-prof
> libghc-gi-glib-doc
> Running dh_listpackages
> libghc-gi-glib-dev
> libghc-gi-glib-prof
> libghc-gi-glib-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro
> --haddockdir=/usr/lib/ghc-doc/haddock/gi-glib-2.0.29/ --datasubdir=gi-glib
> --htmldir=/usr/share/doc/libghc-gi-glib-doc/html/ --enable-library-profiling
> Non-zero exit code 1.
> Using Parsec parser
> [1;91mERROR: [97mcouldn't find API description for GLib.time_t[22;94m
> Please report this at https://github.com/haskell-gi/haskell-gi/issues[0m
> CallStack (from HasCallStack):
> error, called at lib/Data/GI/CodeGen/Util.hs:126:6 in
> haskell-gi-0.26.7-C46MepbmwZA1H8dt48knUn:Data.GI.CodeGen.Util
> terror, called at lib/Data/GI/CodeGen/Code.hs:556:13 in
> haskell-gi-0.26.7-C46MepbmwZA1H8dt48knUn:Data.GI.CodeGen.Code
> findAPIByName, called at lib/Data/GI/CodeGen/GObject.hs:17:44 in
> haskell-gi-0.26.7-C46MepbmwZA1H8dt48knUn:Data.GI.CodeGen.GObject
> at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 109.
>
> Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
> "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
> "--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
> "--libexecdir=/usr/lib", ...) called at
> /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 133
>
> Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
> "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
> "--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
> "--libexecdir=/usr/lib", ...) called at
> /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 637
> Debian::Debhelper::Buildsystem::Haskell::Recipes::configure_recipe()
> called at -e line 1
> make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp]
> Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/19/haskell-gi-glib_2.0.29-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240319;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240319=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.
Bug#1031125: marked as done (ell FTBFS on hppa b/c of missing LFS suppport)
Your message dated Sun, 31 Mar 2024 10:39:00 + with message-id and subject line Bug#1031125: fixed in ell 0.64-1 has caused the Debian Bug report #1031125, regarding ell FTBFS on hppa b/c of missing LFS suppport 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.) -- 1031125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ell Tags: ftbfs, hppa, patch Version: 0.56-3 ell sometimes fails to build from source on hppa: https://buildd.debian.org/status/fetch.php?pkg=ell=hppa=0.56-3=1676182857=0 Reason is, that ell is not compiled with Large File Support (LFS). To solve this issue, please change in debian/rules this line: export DEB_BUILD_MAINT_OPTIONS = hardening=+all to export DEB_BUILD_MAINT_OPTIONS = hardening=+all future=+lfs With that change, ell will reliably build on hppa and will reliably work on all 32-bit platforms at runtime. Thanks, Helge --- End Message --- --- Begin Message --- Source: ell Source-Version: 0.64-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of ell, 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 1031...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated ell 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, 30 Mar 2024 13:03:54 +0100 Source: ell Binary: libell-dev libell0 libell0-dbgsym Architecture: source amd64 Version: 0.64-1 Distribution: unstable Urgency: medium Maintainer: Nobuhiro Iwamatsu Changed-By: Jonas Smedegaard Description: libell-dev - development files for the Embedded Linux library libell0- Embedded Linux library Closes: 1031125 Changes: ell (0.64-1) unstable; urgency=medium . [ upstream ] * new release . [ Jonas Smedegaard ] * enable LFS support for HPPA, by setting future=+lfs in DEB_BUILD_MAINT_OPTIONS; closes: bug#1031125, thanks to Helge Deller * update symbols: + add 1 symbol + strip debian revision from 5 symbols * drop obsolete Homepage URI Checksums-Sha1: ddc625d937aba4f8e75e55ef8a45eabaecf8c184 1982 ell_0.64-1.dsc e7aa161d27212ae021bfadae7d9b5a672503a336 567908 ell_0.64.orig.tar.xz 94885d2b57f154a40d0875f9db985ec85853e456 12108 ell_0.64-1.debian.tar.xz 3812941dc2fbce19d754968c58dc962df335a072 7690 ell_0.64-1_amd64.buildinfo 1309b80b473fc86e81ca83ff7e16e57da6953f8e 261012 libell-dev_0.64-1_amd64.deb 1f1e9330f2eaa41494dcc3ed4e8bb22b4ca199dd 721460 libell0-dbgsym_0.64-1_amd64.deb 5344574a2d25abadabbedd4b49e6f2f3607a4a8f 217276 libell0_0.64-1_amd64.deb Checksums-Sha256: 02846a4b87efb339855a59263ff4b6f9330e17b8583c2b07d2655f6f15942d22 1982 ell_0.64-1.dsc 760f3901078409f66cadf1bb24c8bdc60f13d53f6dd66b88631221d2494f8405 567908 ell_0.64.orig.tar.xz adfcd65fed38a21f9fa675513dbf9cd729f26743b7bf0bb72dfbf609e2b95581 12108 ell_0.64-1.debian.tar.xz 99d6f0abd7c273b1706f63b83f68eaf81a27f5e0ef63076284342cdb75550990 7690 ell_0.64-1_amd64.buildinfo 519033653e01ee8c59136aca8ba9553e407ada6e78b49fe1a47d60417cab477b 261012 libell-dev_0.64-1_amd64.deb 0cd9f5b5beb85ce060e40876ba21615904be480aed278657ecc50c25c2a5ab0d 721460 libell0-dbgsym_0.64-1_amd64.deb b6a5e03ba5192b3a551f7143087d00a12f530f67e89cb892c7baaf89879d2bba 217276 libell0_0.64-1_amd64.deb Files: 23a552cce702f441b12e8aa7b7689317 1982 devel optional ell_0.64-1.dsc 6e6038771c713fd742a282b41ce14040 567908 devel optional ell_0.64.orig.tar.xz 26ec03525c4b6f75a92cb41e5d75b637 12108 devel optional ell_0.64-1.debian.tar.xz d120ec77dafc1029f25b2c80f4716514 7690 devel optional ell_0.64-1_amd64.buildinfo 0e28f081de5a76656ec95a752899d0fb 261012 libdevel optional libell-dev_0.64-1_amd64.deb bf2a4a7fa92f1d33f0aba63d3bcfce5f 721460 debug optional libell0-dbgsym_0.64-1_amd64.deb e5e785dae2f00f688673be53983757b1 217276 libs optional libell0_0.64-1_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmYIBywACgkQLHwxRsGg ASFijxAAoEX4sURyxJ34yX57jdBVEcc7SUPAXze0fyKpmoBbHAHm6zcuiC25DfZ6 gkXc8MsbS1B9mHb20sTDNRbl4cGzrp2MSQmJQSJkwaH/xyOSIRoR0Dvkms/1udZM
Bug#1068043: marked as done (BinNMU 1.11-1+b1 depends on both, libmspack0 and libmspack0t64, and is hence uninstallable (at least on armhf))
Your message dated Sun, 31 Mar 2024 10:36:56 + with message-id and subject line Bug#1068043: fixed in cabextract 1.11-2 has caused the Debian Bug report #1068043, regarding BinNMU 1.11-1+b1 depends on both, libmspack0 and libmspack0t64, and is hence uninstallable (at least on armhf) 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.) -- 1068043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cabextract Version: 1.11-1 Severity: serious X-Debbugs-Cc: a...@debian.org >From aptitude's dependency view on armhf: iFA (pin --\ cabextract 0 72.7 kB 1.11-1 1.11-1+b1 --\ Depends (3) --- libc6 (>= 2.34) --- libmspack0 (>= 0.9.1-1) --- libmspack0t64 (>= 0.4) (UNSATISFIED) As libmspack0t64 breaks libmspack0 they can't be installed together. This is likely caused by hardcoding a dependency on libmspack0 in debian/control: https://sources.debian.org/src/cabextract/1.11-1/debian/control/#L10 -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 'testing'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: armhf (armv7l) Kernel: Linux 6.6.15-armmp-lpae (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages cabextract depends on: ii libc6 2.37-15.1 ii libmspack0 0.11-1 cabextract recommends no packages. cabextract suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: cabextract Source-Version: 1.11-2 Done: Eric Sharkey We believe that the bug you reported is fixed in the latest version of cabextract, 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 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Eric Sharkey (supplier of updated cabextract 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, 30 Mar 2024 20:21:18 -0400 Source: cabextract Architecture: source Version: 1.11-2 Distribution: unstable Urgency: low Maintainer: Eric Sharkey Changed-By: Eric Sharkey Closes: 1068043 Changes: cabextract (1.11-2) unstable; urgency=low . * Remove hard-coded versioned dependency on libmspack0 to resolve dependency problem on armhf architecture: Closes: #1068043 Checksums-Sha1: 7ba445f8adb5d70028db0c8429e1a6392e612e51 1719 cabextract_1.11-2.dsc 3d3841c7c09f2d91c564f5988f80a836744453a7 6728 cabextract_1.11-2.debian.tar.xz 6c7133c946b36bd87b15260e4ab3872a623d592c 7818 cabextract_1.11-2_amd64.buildinfo Checksums-Sha256: 4ad4989b6c192b5f6e3929be4185e537fcfcdbce467b2c68206ffbb85dba3a63 1719 cabextract_1.11-2.dsc 4e39c5c1768035ccc7e25c0e67d82c5fe8cef4bc4a4fb87ae103ebc00ef6de64 6728 cabextract_1.11-2.debian.tar.xz 4e23d2a0f4c648ce94c9445d94f0208a3f21c8fb323916bcbcf92545e735a8e7 7818 cabextract_1.11-2_amd64.buildinfo Files: 80ef693cf2cbca2306ad357e04d58ffc 1719 utils optional cabextract_1.11-2.dsc 451d36d8132db020d00ff6152620ac74 6728 utils optional cabextract_1.11-2.debian.tar.xz 37267223a4be6f18cd42ddb353a3e2c2 7818 utils optional cabextract_1.11-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEELpjU0Pi3I6H/MmtbReLNpaf9kPkFAmYIuUEACgkQReLNpaf9 kPkmWg//fdr9LaH4BgSvlS26Qy5/U0EP+wyzygMI3n000QbwtqI7LOnZ5CzfJLTI 2daMCi8Di7nbsh3Jk+TVeUlY3KMDjQNfY++FaCJ29TxU91NDFH9Zb4dqjL78epU5 JOiFAfmwZIdW9AN+HL4/so9vHj+sXxkVYY/9ObfvhKLNbNbb5GuJK/YgetefZG0b BztOEvKf8jReKsJzTsKmlFlP5fjqJBRGkToZ3Lbfyr2F17VbIGQ6xYyvOPAZHt47 EGvJ5e11W3d8x6jQEfCVvvPOjqIhJ53wZdX5wcxSmhbihf/XAs3hJkwM15YLuILn 1kPeDizZwo8CRIAcVzrqUP8CV/2zzXMwEwNuaJdik4HvHj4e8PeYSOMZuAY3tpD2 474ds47OrrugPEeTJWrgF2neAYhBgiwRADb/bQowpt/eFSh4+DK6MO5F3Jv0LuiY OGhntHiGZUi77Lj4gs2dye+4GqZtlSzKjERk18pbRldajyUb1LXA+dVSlETOidUG cV2Cu1ISuu+oXlh7K0rQM+AfAHg4UCMwRHMLunsJgk2ZPe6RDFFGElVt7PJp2Jsd CGi42/5H9mw0v4YfEfdfZJVDDLdNyhHx1P94DpBiRUNZHqGOjgy+eLoOYdIaxOW4
Bug#1067919: marked as done (Update Build-Depends for the time64 library renames)
Your message dated Sun, 31 Mar 2024 10:37:09 + with message-id and subject line Bug#1067919: fixed in calindori 24.02.1-1 has caused the Debian Bug report #1067919, regarding Update Build-Depends for the time64 library renames 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.) -- 1067919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: calindori Version: 24.02.0-1 Severity: serious Tags: ftbfs The package explicitly Build-Depends: libqt5*, these need to be changed to libqt5*t64 (where applicable) if these deps are needed at all. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 --- Source: calindori Source-Version: 24.02.1-1 Done: Marco Mattiolo We believe that the bug you reported is fixed in the latest version of calindori, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marco Mattiolo (supplier of updated calindori 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, 29 Mar 2024 10:06:56 +0100 Source: calindori Architecture: source Version: 24.02.1-1 Distribution: unstable Urgency: medium Maintainer: DebianOnMobile Maintainers Changed-By: Marco Mattiolo Closes: 1067919 Changes: calindori (24.02.1-1) unstable; urgency=medium . * New upstream release * Update d/copyright after upstream changes * Update d/control for build-deps after time64 transition (Closes: #1067919) * Update d/control to make build-deps list transition-proof Checksums-Sha1: 7e8db2a9ceca9aadeef83bd2f17e33040734acb3 2711 calindori_24.02.1-1.dsc d248e12f3596f897171e2fa223ba10045c09c376 385320 calindori_24.02.1.orig.tar.xz a92c5742b236557b5a69748ba2d277726c085fc3 833 calindori_24.02.1.orig.tar.xz.asc 7821cfc0835991af64e1543c830052df98cb9f63 24060 calindori_24.02.1-1.debian.tar.xz a91640fd2b2a36bdf710726552c7d90ffa1a0f18 14305 calindori_24.02.1-1_source.buildinfo Checksums-Sha256: 47884ed0aef669add7a95d04e2f6a75c9fd9bd5522b15f26120ce27b3191112e 2711 calindori_24.02.1-1.dsc c4e97f344c6befe4b847f1162779ae914a40eea94f7487e7c87da0ecc886ec05 385320 calindori_24.02.1.orig.tar.xz 9553dbd487d3ce9667dd61a5502283bfb23c4bd093fffbcb594f1fd3f86d76c3 833 calindori_24.02.1.orig.tar.xz.asc 23e4a40d6a8640c1c995b813e08668eae4e468bfe0e0c478e8a9c571ac132307 24060 calindori_24.02.1-1.debian.tar.xz 04cd58b784eddf2ef083389242fd61c77be090ca7aab3bdbcee671637843616f 14305 calindori_24.02.1-1_source.buildinfo Files: 652077b347b84b566009cc286e15ef1e 2711 kde optional calindori_24.02.1-1.dsc f16bba7d3e0d9aeb46cd7cf61683bd40 385320 kde optional calindori_24.02.1.orig.tar.xz acc984f9d9f36736c387776469fa2f69 833 kde optional calindori_24.02.1.orig.tar.xz.asc 780c60ac2bf946299132a5c1a4d8513a 24060 kde optional calindori_24.02.1-1.debian.tar.xz d6531f210355158fb58318275072299c 14305 kde optional calindori_24.02.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEeW2zk9w/9AIituoi0+u1lmu5kZYFAmYIPuIACgkQ0+u1lmu5 kZbtahAAp/EwYlxTWGfePSuGxmpd/ucI7eQZk22zIgt0IWpMmz/bVQaH+ZM2o03Y yEauDp6DVPGcMP61yjUpemOgxNQveMkUhzBiyVy5sXT5IbSZtD0ItzATySKX2XNF HXVXQVftAURL5Bq4iAiX+KZBhk0LpMCHe9HzJL8mbW4xJkRn3Br04i5QlMuoMbpH W9ul8lSdyfjPFlCE4XJU1v2XtfgtnTJKdO3hkp3hF7Z3J5+mVMoeJXkfS8eXkphw zSGKvNUHyJJmYTLHsGjk445en5whU8j0wsu49h8v0yrcn5HnfK6ClZXjIdvlDPGs 1RbWnUx4f6FFv6Ypo5NFob54XUGh17TzQ64OJLsrkdyiC88UZZQIvG5Q0DESQQq5 ICvYCXZ3mUNoUZVkqhKrfKgKPQjQU0Qk7oMuU6bk1vXqO8ax+VKSiWIOx+QcZhDV
Bug#1068069: marked as done (nmu: juce_7.0.5+ds-1)
Your message dated Sun, 31 Mar 2024 11:39:22 +0200 with message-id and subject line Re: Bug#1068069: nmu: juce_7.0.5+ds-1 has caused the Debian Bug report #1068069, regarding nmu: juce_7.0.5+ds-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.) -- 1068069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068069 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal X-Debbugs-Cc: j...@packages.debian.org Control: affects -1 + src:juce User: release.debian@packages.debian.org Usertags: binnmu nmu juce_7.0.5+ds-1 . ANY . unstable . -m "Rebuild for time_t" https://packages.debian.org/sid/juce-tools --- End Message --- --- Begin Message --- On 2024-03-30 13:34:42 +0500, Andrey Rakhmatullin wrote: > Package: release.debian.org > Severity: normal > X-Debbugs-Cc: j...@packages.debian.org > Control: affects -1 + src:juce > User: release.debian@packages.debian.org > Usertags: binnmu > > nmu juce_7.0.5+ds-1 . ANY . unstable . -m "Rebuild for time_t" Done, though there is a FTBFS bug on mips64el that will need to be fixed in some way. Cheers -- Sebastian Ramacher--- End Message ---
