Processed: Re: Bug#1028443: bpython: autopkgtest regressions with python 3.11
Processing control commands: > tags -1 fixed-upstream Bug #1028443 [src:bpython] bpython: autopkgtest regressions with python 3.11 Added tag(s) fixed-upstream. -- 1028443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028443: bpython: autopkgtest regressions with python 3.11
Control: tags -1 fixed-upstream
On 2023-01-10 21:18:46 -0800, Steve Langasek wrote:
> Source: bpython
> Version: 0.23-1
> Severity: serious
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu lunar
>
> Hi Sebastian,
>
> The bpython package is now failing its autopkgtests in unstable because
> /usr/bin/python3 has moved to python 3.11:
>
> [...]
> === FAILURES
> ===
> TestInspection.test_getfuncprops_print
>
>
> self = testMethod=test_getfuncprops_print>
>
> @unittest.skipIf(pypy, "pypy builtin signatures aren't complete")
> def test_getfuncprops_print(self):
> props = inspection.getfuncprops("print", print)
>
> self.assertEqual(props.func, "print")
> self.assertIn("end", props.argspec.kwonly)
> self.assertIn("file", props.argspec.kwonly)
> self.assertIn("flush", props.argspec.kwonly)
> self.assertIn("sep", props.argspec.kwonly)
> > self.assertEqual(props.argspec.kwonly_defaults["file"], "sys.stdout")
> E AssertionError: None != 'sys.stdout'
The issue is fixed upstream. I just need to find the time to cut a new
release.
Cheers
--
Sebastian Ramacher
Bug#1028451: 2nd DisplayPort doesn't get video
Package: src:linux Version: 6.1.4-1 Severity: serious Hello there, Since booting 6.1.0-1, the 2nd DisplayPort output from my Lenovo Docking Station doesn't get any output. It is _seen_ as connected by the screen, but apparently gets no video signal (or just blank). This is clearly a regression from 6.0.0-6 where this was working. I'm quite confident this is a kernel-level change (and not X11 or Plasma) as this already appears clearly at cryptsetup password prompt (which usually goes to all outputs, but not on 6.1.0-1 which only displays it on the laptop screen and the 1st connected DisplayPort. Happy to help solve this. Best, OdyX -- Package-specific info: ** Version: Linux version 6.1.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-13) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39.90.20221231) #1 SMP PREEMPT_DYNAMIC Debian 6.1.4-1 (2023-01-07) ** Command line: BOOT_IMAGE=/vmlinuz-6.1.0-1-amd64 root=/dev/mapper/turnagra--vg-root ro quiet splash cgroup_enable=memory apparmor=1 security=apparmor ** Tainted: W (512) * kernel issued warning ** Kernel log: [ 15.343546] input: HD-Audio Generic Headphone as /devices/pci:00/:00:08.1/:05:00.6/sound/card4/input38 [ 15.443246] usbcore: registered new interface driver btusb [ 15.481320] bluetooth hci0: firmware: direct-loading firmware mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin [ 15.493335] intel_rapl_common: Found RAPL domain package [ 15.493340] intel_rapl_common: Found RAPL domain core [ 15.499969] mt7921e :03:00.0: enabling device ( -> 0002) [ 15.518411] mt7921e :03:00.0: ASIC revision: 79610010 [ 15.602835] mt7921e :03:00.0: firmware: direct-loading firmware mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin [ 15.602842] mt7921e :03:00.0: HW/SW Version: 0x8a108a10, Build Time: 20221109110918a [ 15.603213] Bluetooth: hci0: Device setup in 121459 usecs [ 15.603217] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 15.614235] mt7921e :03:00.0: firmware: direct-loading firmware mediatek/WIFI_RAM_CODE_MT7961_1.bin [ 15.614240] mt7921e :03:00.0: WM Firmware Version: 01, Build Time: 20221109111005 [ 15.654966] mt7921e :03:00.0: firmware: direct-loading firmware mediatek/WIFI_RAM_CODE_MT7961_1.bin [ 15.676225] EXT4-fs (nvme0n1p2): mounting ext2 file system using the ext4 subsystem [ 15.677063] EXT4-fs (nvme0n1p2): mounted filesystem without journal. Quota mode: none. [ 15.679393] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Quota mode: none. [ 15.679984] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Quota mode: none. [ 15.689038] systemd-journald[673]: Received client request to flush runtime journal. [ 15.692904] systemd-journald[673]: File /var/log/journal/554675a9a7254eeea535d3d6aa31a8a6/system.journal corrupted or uncleanly shut down, renaming and replacing. [ 15.849074] audit: type=1400 audit(1673421894.663:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-senddoc" pid=980 comm="apparmor_parser" [ 15.849408] audit: type=1400 audit(1673421894.663:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=966 comm="apparmor_parser" [ 15.849475] audit: type=1400 audit(1673421894.663:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-oosplash" pid=979 comm="apparmor_parser" [ 15.849517] audit: type=1400 audit(1673421894.663:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="torbrowser_tor" pid=974 comm="apparmor_parser" [ 15.849866] audit: type=1400 audit(1673421894.663:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=969 comm="apparmor_parser" [ 15.849871] audit: type=1400 audit(1673421894.663:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=969 comm="apparmor_parser" [ 15.849949] audit: type=1400 audit(1673421894.663:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=977 comm="apparmor_parser" [ 15.849954] audit: type=1400 audit(1673421894.663:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=977 comm="apparmor_parser" [ 15.849957] audit: type=1400 audit(1673421894.663:12): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=977 comm="apparmor_parser" [ 15.851055] audit: type=1400 audit(1673421894.667:13): apparmor="STATUS" operation="profile_load" profile="unconfined" name="system_tor" pid=972 comm="apparmor_parser" [ 16.466830] mt7921e :03:00.0 wlp3s0: renamed from wlan0 [ 16.789424] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 16.789428] Bluetooth: BNEP filters: protocol multicast [ 16.789433] Bluetooth: BNEP socket layer initialized [ 16.790811] Bluetooth: MGMT ver 1.22
Processed: aflplusplus: FTBFS on s390x
Processing commands for cont...@bugs.debian.org: > tags 1026103 + ftbfs Bug #1026103 [src:aflplusplus] aflplusplus: FTBFS on s390x Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026103 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Duplicate libfplll7-data libfplll8-data overwriting files
Processing commands for cont...@bugs.debian.org: > merge #1028292 #1028316 Bug #1028292 [libfplll8-data] libfplll8-data: tries to overwrite /usr/share/libfplll8/strategies/default.json, already in libfplll7-data Bug #1028316 [libfplll8-data] libfplll8-data: missing Breaks+Replaces: libfplll7-data (>= 5.4.3) Marked as found in versions fplll/5.4.4-2. Bug #1028292 [libfplll8-data] libfplll8-data: tries to overwrite /usr/share/libfplll8/strategies/default.json, already in libfplll7-data Marked as found in versions fplll/5.4.4-1. Merged 1028292 1028316 > thanks Stopping processing here. Please contact me if you need assistance. -- 1028292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028292 1028316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027849: zeroc-ice: diff for NMU version 3.7.8-1.1
On Tue, Jan 10, 2023 at 05:36:32PM +0100, Jose Gutierrez de la Concha wrote: > Hi Adrian, > > Seems didn't work, I will look into it. >... > > I've prepared an NMU for zeroc-ice (versioned as 3.7.8-1.1) and uploaded > > it to DELAYED/2. Please feel free to tell me if I should cancel it. >... It's still waiting in DELAYED: https://ftp-master.debian.org/deferred.html I can change the upload to be immediate or I can cancel it if you want, but the default is that it will enter unstable in 15 hours. cu Adrian
Bug#1028449: changeo fails with python3.11: "invalid mode rU"
Package: changeo
Version: 1.2.0-1
Severity: grave
Tags: patch
Justification: renders package unusable
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar ubuntu-patch
Dear maintainers,
changeo fails its autopkgtests with python3.11, revealing a bug in the
software, because it uses a mode flag to open() which has been deprecated
since python 3 and is now obsolete in python 3.11:
[...]
Traceback (most recent call last):
File "/usr/bin/CreateGermlines.py", line 354, in
createGermlines(**args_dict)
File "/usr/bin/CreateGermlines.py", line 94, in createGermlines
reference_dict = readGermlines(references)
^
File "/usr/lib/python3/dist-packages/changeo/IO.py", line 2201, in
readGermlines
with open(file_name, 'rU') as file_handle:
^
ValueError: invalid mode: 'rU'
[...]
(https://ci.debian.net/data/autopkgtest/testing/amd64/c/changeo/30225356/log.gz)
I'm assuming this is fairly core functionality in the package so have marked
the bug grave. If it's not, then the autopkgtest regression is still
serious.
I've applied the attached trivial patch in Ubuntu to fix the regression
there.
Thanks for considering,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru changeo-1.2.0/debian/patches/open-U-obsolete.patch
changeo-1.2.0/debian/patches/open-U-obsolete.patch
--- changeo-1.2.0/debian/patches/open-U-obsolete.patch 1969-12-31
16:00:00.0 -0800
+++ changeo-1.2.0/debian/patches/open-U-obsolete.patch 2023-01-10
21:53:30.0 -0800
@@ -0,0 +1,21 @@
+Description: Drop obsolete "U" mode passed to open()
+ The "U" mode has been deprecated in python since python3 and has had no
+ effect. In python 3.11, it is now disallowed. Drop this mode flag that
+ causes runtime failures.
+Author: Steve Langasek
+Last-Update: 2023-01-10
+Forwarded: no
+
+Index: changeo-1.2.0/changeo/IO.py
+===
+--- changeo-1.2.0.orig/changeo/IO.py
changeo-1.2.0/changeo/IO.py
+@@ -2198,7 +2198,7 @@
+ repo_dict = {}
+ duplicates = []
+ for file_name in repo_files:
+-with open(file_name, 'rU') as file_handle:
++with open(file_name, 'r') as file_handle:
+ germlines = SeqIO.parse(file_handle, 'fasta')
+ for g in germlines:
+ germ_key = getAllele(g.description, 'first') if not asis else
g.id
diff -Nru changeo-1.2.0/debian/patches/series
changeo-1.2.0/debian/patches/series
--- changeo-1.2.0/debian/patches/series 1969-12-31 16:00:00.0 -0800
+++ changeo-1.2.0/debian/patches/series 2023-01-10 21:52:41.0 -0800
@@ -0,0 +1 @@
+open-U-obsolete.patch
Bug#1028447: cdist: unusable with python 3.11
Package: cdist
Version: 7.0.0-1
Severity: grave
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar
The cdist package is broken with python 3.11, as detected by the
autopkgtest:
$ cdist
Traceback (most recent call last):
File "/usr/bin/cdist", line 93, in
commandline()
File "/usr/bin/cdist", line 53, in commandline
parser, cfg = cdist.argparse.parse_and_configure(sys.argv[1:])
File "/usr/lib/python3/dist-packages/cdist/argparse.py", line 534, in
parse_and_configure
parser = get_parsers()
^
File "/usr/lib/python3/dist-packages/cdist/argparse.py", line 478, in
get_parsers
parser['scan'] = parser['sub'].add_parser(
^
File "/usr/lib/python3.11/argparse.py", line 1197, in add_parser
raise ArgumentError(self, _('conflicting subparser: %s') % name)
argparse.ArgumentError: argument command: conflicting subparser: scan
$
It looks like this is easily fixable without regression by removing the
first assignment to parser['scan'], but this seems like such an obvious bug
that I don't know if I'm missing something with historical behavior of
argparse handling multiple assignments?
Anyway, this package has no maintainer and upstream has not fixed this, and
there are no reverse-dependencies, so I would suggest the package should
just be removed.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: PGP signature
Bug#1028443: bpython: autopkgtest regressions with python 3.11
Source: bpython
Version: 0.23-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar
Hi Sebastian,
The bpython package is now failing its autopkgtests in unstable because
/usr/bin/python3 has moved to python 3.11:
[...]
=== FAILURES ===
TestInspection.test_getfuncprops_print
self =
@unittest.skipIf(pypy, "pypy builtin signatures aren't complete")
def test_getfuncprops_print(self):
props = inspection.getfuncprops("print", print)
self.assertEqual(props.func, "print")
self.assertIn("end", props.argspec.kwonly)
self.assertIn("file", props.argspec.kwonly)
self.assertIn("flush", props.argspec.kwonly)
self.assertIn("sep", props.argspec.kwonly)
> self.assertEqual(props.argspec.kwonly_defaults["file"], "sys.stdout")
E AssertionError: None != 'sys.stdout'
[...]
(https://ci.debian.net/data/autopkgtest/testing/amd64/b/bpython/30225354/log.gz)
Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: PGP signature
Processed: tagging 1025102
Processing commands for cont...@bugs.debian.org: > tags 1025102 + ftbfs Bug #1025102 [src:python-gbulb] python-gbulb: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine' Ignoring request to alter tags of bug #1025102 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1025102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028441: marked as done (gcc-12-cross-mipsen needs a source upload for testing migration)
Your message dated Wed, 11 Jan 2023 04:21:46 + with message-id and subject line Bug#1028441: fixed in gcc-12-cross-mipsen 3+c1 has caused the Debian Bug report #1028441, regarding gcc-12-cross-mipsen needs a source upload for testing migration 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.) -- 1028441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-12-cross-mipsen Version: 2+c1 Severity: serious X-Debbugs-Cc: YunQiang Su gcc-*-cross* packages in general have an (IMHO RC severity) problem that binNMUs are not possible since binary-any packages being newer than binary-all packages might cause problems. This is also the case right now, where gcc-12-mips-linux-gnu:mips64el is not installable due to The following packages have unmet dependencies: gcc-12-mips-linux-gnu : Depends: libgcc-12-dev-mips-cross (>= 12.2.0-14cross2) but 12.2.0-5cross2 is to be installed A source upload of gcc-12-cross-mipsen should be sufficient as short-term workaround for this issue. --- End Message --- --- Begin Message --- Source: gcc-12-cross-mipsen Source-Version: 3+c1 Done: YunQiang Su We believe that the bug you reported is fixed in the latest version of gcc-12-cross-mipsen, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. YunQiang Su (supplier of updated gcc-12-cross-mipsen package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 11 Jan 2023 11:53:28 +0800 Source: gcc-12-cross-mipsen Architecture: source Version: 3+c1 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: YunQiang Su Closes: 1028441 Changes: gcc-12-cross-mipsen (3+c1) unstable; urgency=medium . * Source-only upload (Closes: #1028441) * Based on gcc-12-cross 14. - Build using gcc 12.2.0-14. - Bump standards version. - Tighten build dependency on dpkg-dev. Checksums-Sha1: eecc247baa873aabc9b344494790925cfc4ceda6 60973 gcc-12-cross-mipsen_3+c1.dsc 3686cf004589bef3f0e7cf6b3faae92f8a6733ff 44120 gcc-12-cross-mipsen_3+c1.tar.xz 82f9b5e67675a19ce6a745513011b66026f18982 7373 gcc-12-cross-mipsen_3+c1_source.buildinfo Checksums-Sha256: 7036e7fbdec6d44a071e002ac78b81fec9cf86523887c684db27658717bc5500 60973 gcc-12-cross-mipsen_3+c1.dsc dec6e08fc7beed34b928da0feb945e13ea66eb2e4f721c78049464766b7d839c 44120 gcc-12-cross-mipsen_3+c1.tar.xz 572d4c5ad74bbd66a65948ea9c4cab4f402ad43e048c7fccd57066726fe52cf3 7373 gcc-12-cross-mipsen_3+c1_source.buildinfo Files: 987e129a0f0e9811f554a79f19b19a44 60973 devel optional gcc-12-cross-mipsen_3+c1.dsc ca5ca47f24dbc4681a962a91c29b2f2c 44120 devel optional gcc-12-cross-mipsen_3+c1.tar.xz b8e8608a92ed70f0eabfc349f304c7bd 7373 devel optional gcc-12-cross-mipsen_3+c1_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEEzJPpNyx4YT9lsL4DQafa2Aqh014FAmO+NEUPHHN5cUBkZWJp YW4ub3JnAAoJEEGn2tgKodNepBcP/RkXRXvXzJcg+CdNTVSzVq0EI1wVu204h6iQ 4iHTwpjkyYmqIfilH1iOZ7tSqIv7gNSGhVlbRsYhnUUrOjPQuhC19V2ThmS2hL1w zi+yhTCQEQ2BYoo/EstoKQBuWdf9Bu6LVVA7Ncj8a0VVjP7GktZQAhqKjg6Of2T9 MyN4sXe5Ms3uEdm48AhByxKUnv6DSeOjyd+KYUo5nLejgJDrSAAiubTsYhkyYpFa eL8amYZmqjxTxsP9bB1qPDY8aGpxeLjnNv38xjHS0Qk5Q1MFXn9sHJYPlwLtBTqG rOgEe2eSiCZg2cW24S67IqguGnyCAvUrVwhgGC329mQBtv3WrBriah2pIr79Ohbu IWqzejWJ0AEkywa2j0MbD79WvDhhQ+60CNYUv/AEoMJGpbStyMZQ4sKworLytS20 MB9Ef2pVJ7URbDmGrNkK2dd6Ctv7XhJsJJ5GUZV85vHdWqY0pIETuc8eCyS6LRg1 KzX1SQ9X6osUwBpcTlfvWZHl8x3tyoeAgOQYfzA2rsoLA6oPkm40pEr4BEWwn7oq FvajydarEACxepg7FlCEieYDkTEMzjQyQPafslsEiypP4U27v5hvZgNF/W9M2S8I j3kYsIT9Zl1K0yOn9/wNS/6ZY3zGuKH9WgzmRRr5+4xlpOPvkGQKIrVoNE9h7EXL nXa0ZZ1c =zqym -END PGP SIGNATURE End Message ---
Bug#1027824: marked as done (vim FTBFS on IPV6-only buildds)
Your message dated Wed, 11 Jan 2023 03:44:20 + with message-id and subject line Bug#1027824: fixed in vim 2:9.0.1000-4 has caused the Debian Bug report #1027824, regarding vim FTBFS on IPV6-only buildds 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.) -- 1027824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vim Version: 2:9.0.1000-2 Severity: serious Tags: ftbfs Justification: ftbfs X-Debbugs-Cc: car...@debian.org Hi James, Severity might not be warranted, please downgrade if you think it's needed. I noticed on the last two vim builds that the amd64 build failed, giving it back helped most of the times. The last upload failed as well: https://buildd.debian.org/status/fetch.php?pkg=vim&arch=amd64&ver=2%3A9.0.1000-3&stamp=1672773526&raw=0 Regards, Salvatore --- End Message --- --- Begin Message --- Source: vim Source-Version: 2:9.0.1000-4 Done: James McCoy We believe that the bug you reported is fixed in the latest version of vim, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James McCoy (supplier of updated vim 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: Tue, 10 Jan 2023 22:16:36 -0500 Source: vim Architecture: source Version: 2:9.0.1000-4 Distribution: unstable Urgency: medium Maintainer: Debian Vim Maintainers Changed-By: James McCoy Closes: 1027824 Changes: vim (2:9.0.1000-4) unstable; urgency=medium . * Backport patch to fix tests on IPv6-only hosts (Closes: #1027824) Checksums-Sha1: 36c3a80fdfd9d2dca54b983accf8eae9be5b62a3 3177 vim_9.0.1000-4.dsc 8a29ba79a023f477e5452ed8a1c70a92be91aae6 174648 vim_9.0.1000-4.debian.tar.xz Checksums-Sha256: 710892a773b48b0d00446884f1dea2b8193a26ee422c284580d637293f1f553c 3177 vim_9.0.1000-4.dsc 721972909d10b1212b93f41110cf3ab1fa405c487f228c59e636f828510a5a92 174648 vim_9.0.1000-4.debian.tar.xz Files: 5c957a9870fc81bcffc90a734b304389 3177 editors optional vim_9.0.1000-4.dsc 954df6f4fa67cd05b4bc3812ef44a27c 174648 editors optional vim_9.0.1000-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQKoBAEBCgCSFiEEkb+/TWlWvV33ty0j3+aRrjMbo9sFAmO+KnJfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDkx QkZCRjRENjk1NkJENURGN0I3MkQyM0RGRTY5MUFFMzMxQkEzREIUHGphbWVzc2Fu QGRlYmlhbi5vcmcACgkQ3+aRrjMbo9tdcQ//VqM9oPL8NcY9RkO2eNkrb+B3OKLm QwRcXjuNWFsaBO5jOt1HBTjdtjI5cqK53pdVBLo1kDZIHlTerj/ecMCnUEI9XtQk Qqe2dhQ7DOZURqkiQdb/N6Kz1X3wqcroAjbprW9tUPkUdaQa6mMBZ8ISiyJF5n6o 47w7XASliPSEVybAuQKxqGjeCk+gILpTQHIbLjuIu21IpdFDG38/NBnDL62V0NQA j1nmKZfNGkA8k44GLVXQKehZ/tAvCKm4bm2DaI017ygVtUT1VCqyzWin7xX9Zb1b srcDOnqX5xgeh2e2iVV9A1TZ/qVGqw6bmrSuJaaXURKwHlunQAYyHWJZI8OpGXaI 3ZdkYbx/rp7VdYUpflJmrSz9HComaZT/NQu+goji3gR0Hz789wJnsqvrCF8XX15K u35hd8dkilUoaE0EEpZVfpPFu4zejmRd77wVvuj8vWnjeCGjew7siWMyk+OOUOw2 pnUotQIN7IWM7SPHwo7gk65rGCj6UOMNG9vX+kHpTSIaBTWMljbTZRqEOVCnwrDN LXBpRV16nUJ2gVyRUb10pfdHt88jEWqErmUnZGlchU9pUqCyp+FYNX30Wx6twoIx YMohkvla5pIhZv5v1J9C/TRyEQ0gCVHPeSI4jZ61w5Dm/GUDTVWvBZEj9hnrfX8y VWRq4YHm1VbjbBk= =xD6x -END PGP SIGNATURE End Message ---
Bug#1028442: vim-ultisnips: autopkgtest fails if Vim has non-contiguous patch ranges applied
Source: vim-ultisnips
Version: 3.2-1
Severity: serious
Tags: upstream
Justification: RT
Bookworm's Vim now has a non-contiguous set of patches applied:
% vim --version | grep Included
Included patches: 1-1000, 1087, 1117-1118, 1129
This is causing the "with-vim" autopkgtests to fail to parse the Vim
version. For example:
==
ERROR: runTest
(test_Autotrigger.Autotrigger_WillProduceNoExceptionWithVimLowerThan214.runTest)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.8wvyi1gs/downtmp/build.Ujt/src/test/vim_test_case.py",
line 99, in setUp
reason_for_skipping = self.skip_if()
^^
File
"/tmp/autopkgtest-lxc.8wvyi1gs/downtmp/build.Ujt/src/test/test_Autotrigger.py",
line 56, in
if not check_required_vim_version(self)
File
"/tmp/autopkgtest-lxc.8wvyi1gs/downtmp/build.Ujt/src/test/test_Autotrigger.py",
line 8, in check_required_vim_version
if not test.vim.has_version(7, 4, 214):
^^^
File
"/tmp/autopkgtest-lxc.8wvyi1gs/downtmp/build.Ujt/src/test/vim_interface.py",
line 102, in has_version
_patch = int(line.split(":")[-1].strip().split("-")[-1])
^^^
ValueError: invalid literal for int() with base 10: '1118, 1129'
See the full log for more failures:
https://ci.debian.net/data/autopkgtest/unstable/i386/v/vim-ultisnips/30238961/log.gz
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: 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
Bug#1028441: gcc-12-cross-mipsen needs a source upload for testing migration
Source: gcc-12-cross-mipsen Version: 2+c1 Severity: serious X-Debbugs-Cc: YunQiang Su gcc-*-cross* packages in general have an (IMHO RC severity) problem that binNMUs are not possible since binary-any packages being newer than binary-all packages might cause problems. This is also the case right now, where gcc-12-mips-linux-gnu:mips64el is not installable due to The following packages have unmet dependencies: gcc-12-mips-linux-gnu : Depends: libgcc-12-dev-mips-cross (>= 12.2.0-14cross2) but 12.2.0-5cross2 is to be installed A source upload of gcc-12-cross-mipsen should be sufficient as short-term workaround for this issue.
Processed: Re: Bug#1025985: glosstext: FTBFS: LaTeX Error: File `pdftexcmds.sty' not found.
Processing control commands: > reassign -1 texlive-latex-base 2022.20220923-1 Bug #1025985 [src:glosstex] glosstext: FTBFS: LaTeX Error: File `pdftexcmds.sty' not found. Bug reassigned from package 'src:glosstex' to 'texlive-latex-base'. No longer marked as found in versions glosstex/0.4.dfsg.1-4. Ignoring request to alter fixed versions of bug #1025985 to the same values previously set Bug #1025985 [texlive-latex-base] glosstext: FTBFS: LaTeX Error: File `pdftexcmds.sty' not found. Marked as found in versions texlive-base/2022.20220923-1. > retitle -1 hypdoc.sty requires pdftexcmds.sty that is in texlive-latex-extra Bug #1025985 [texlive-latex-base] glosstext: FTBFS: LaTeX Error: File `pdftexcmds.sty' not found. Changed Bug title to 'hypdoc.sty requires pdftexcmds.sty that is in texlive-latex-extra' from 'glosstext: FTBFS: LaTeX Error: File `pdftexcmds.sty' not found.'. > affects -1 src:glosstext Bug #1025985 [texlive-latex-base] hypdoc.sty requires pdftexcmds.sty that is in texlive-latex-extra Added indication that 1025985 affects src:glosstext -- 1025985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025985 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025985: glosstext: FTBFS: LaTeX Error: File `pdftexcmds.sty' not found.
Control: reassign -1 texlive-latex-base 2022.20220923-1 Control: retitle -1 hypdoc.sty requires pdftexcmds.sty that is in texlive-latex-extra Control: affects -1 src:glosstext On Mon, Dec 12, 2022 at 11:12:45PM +0100, Aurelien Jarno wrote: > Source: glosstex > Version: 0.4.dfsg.1-4 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > > Hi, > > Your package fails to build with: > > |Writing index file glosstex.idx > |(/usr/share/texlive/texmf-dist/tex/latex/hypdoc/hypdoc.sty > |(/usr/share/texlive/texmf-dist/tex/latex/base/atveryend-ltx.sty) > |(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty > |(/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty) > |(/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty) > | > |! LaTeX Error: File `pdftexcmds.sty' not found. >... This is basically a continuation of #1016218. :-( cu Adrian
Bug#1028440: warzone2100 build fixes
The missing attachment for 1. is now attached. cu Adrian On Wed, Jan 11, 2023 at 03:23:23AM +0200, Adrian Bunk wrote: > Source: warzone2100 > Version: 4.3.3-2 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/fetch.php?pkg=warzone2100&arch=armel&ver=4.3.3-2&stamp=1673284889&raw=0 > > 1. Wcast-align build errors on mipsel/riscv64/sparc64: > Attached is the fix/workaround I submitted upstream at > https://github.com/Warzone2100/warzone2100/pull/3084 > > 2. The -latomic workaround for > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358 > needs expansion: > > --- debian/rules.old 2023-01-10 00:02:52.580028340 + > +++ debian/rules 2023-01-10 06:45:42.213281490 + > @@ -4,9 +4,9 @@ > export DEB_BUILD_MAINT_OPTIONS = hardening=+all > export DEB_CPPFLAGS_MAINT_APPEND = -DNDEBUG > > -# riscv64 needs explicit -latomic > -ifneq (,$(filter $(DEB_HOST_ARCH), riscv64)) > -export DEB_LDFLAGS_MAINT_APPEND = -latomic > +# workaround for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358 > +ifneq (,$(filter $(DEB_HOST_ARCH), armel m68k mipsel powerpc riscv64 sh4)) > +export DEB_LDFLAGS_MAINT_APPEND = -Wl,--no-as-needed -latomic > -Wl,--as-needed > endif > > %: >From ab1c0027a046bbdaca0818bdaa1cbf0ce08648c3 Mon Sep 17 00:00:00 2001 From: Adrian Bunk Date: Wed, 11 Jan 2023 03:02:52 +0200 Subject: vk_mem_alloc: Ignore -Wcast-align on GCC on all architectures The warning is not only on ARM, in Debian it has also appeared on mipsel/riscv64/sparc64. --- lib/ivis_opengl/3rdparty/vk_mem_alloc.cpp | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/lib/ivis_opengl/3rdparty/vk_mem_alloc.cpp b/lib/ivis_opengl/3rdparty/vk_mem_alloc.cpp index 2ec35af10..dad4a116e 100644 --- a/lib/ivis_opengl/3rdparty/vk_mem_alloc.cpp +++ b/lib/ivis_opengl/3rdparty/vk_mem_alloc.cpp @@ -44,9 +44,7 @@ # pragma GCC diagnostic ignored "-Wunused-variable" # pragma GCC diagnostic ignored "-Wmissing-field-initializers" # pragma GCC diagnostic ignored "-Wmissing-noreturn" -# if (defined(__arm__) || defined(__thumb__)) && !defined(__aarch64__) -#pragma GCC diagnostic ignored "-Wcast-align" -# endif +# pragma GCC diagnostic ignored "-Wcast-align" #elif defined(_MSC_VER) # pragma warning( push ) # pragma warning( disable : 4189 ) // warning C4189: 'identifier' : local variable is initialized but not referenced -- 2.30.2
Bug#1028440: warzone2100 build fixes
Source: warzone2100 Version: 4.3.3-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=warzone2100&arch=armel&ver=4.3.3-2&stamp=1673284889&raw=0 1. Wcast-align build errors on mipsel/riscv64/sparc64: Attached is the fix/workaround I submitted upstream at https://github.com/Warzone2100/warzone2100/pull/3084 2. The -latomic workaround for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358 needs expansion: --- debian/rules.old2023-01-10 00:02:52.580028340 + +++ debian/rules2023-01-10 06:45:42.213281490 + @@ -4,9 +4,9 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all export DEB_CPPFLAGS_MAINT_APPEND = -DNDEBUG -# riscv64 needs explicit -latomic -ifneq (,$(filter $(DEB_HOST_ARCH), riscv64)) -export DEB_LDFLAGS_MAINT_APPEND = -latomic +# workaround for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358 +ifneq (,$(filter $(DEB_HOST_ARCH), armel m68k mipsel powerpc riscv64 sh4)) +export DEB_LDFLAGS_MAINT_APPEND = -Wl,--no-as-needed -latomic -Wl,--as-needed endif %:
Bug#1026597: marked as done (gcc-10-cross-ports: FTBFS: collect2: error: ld returned 1 exit status)
Your message dated Wed, 11 Jan 2023 01:11:19 + with message-id <2670d6d3-60c9-481e-93a9-8e78e55d0...@debian.org> and subject line Re: Bug#1026597: gcc-10-cross-ports: FTBFS: collect2: error: ld returned 1 exit status has caused the Debian Bug report #1026597, regarding gcc-10-cross-ports: FTBFS: collect2: error: ld returned 1 exit status 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.) -- 1026597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-10-cross-ports Version: 20 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /<>/gcc/build/./gcc/xgcc -B/<>/gcc/build/./gcc/ > -B/usr/riscv64-linux-gnu/bin/ -B/usr/riscv64-linux-gnu/lib/ -isystem > /usr/riscv64-linux-gnu/include -isystem /usr/riscv64-linux-gnu/sys-include > -isystem /<>/gcc/build/sys-include-O2 -g -O2 -DIN_GCC > -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wno-narrowing -Wwrite-strings > -Wcast-qual -Wno-error=format-diag -Wstrict-prototypes -Wmissing-prototypes > -Wno-error=format-diag -Wold-style-definition -isystem ./include -fPIC -g > -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -shared -nodefaultlibs > -Wl,--soname=libgcc_s.so.1 -Wl,--version-script=libgcc.map -o > ./libgcc_s.so.1.tmp -g -O2 -B./ _negdi2_s.o _lshrdi3_s.o _ashldi3_s.o > _ashrdi3_s.o _cmpdi2_s.o _ucmpdi2_s.o _clear_cache_s.o _trampoline_s.o > __main_s.o _absvsi2_s.o _absvdi2_s.o _addvsi3_s.o _addvdi3_s.o _subvsi3_s.o > _subvdi3_s.o _mulvsi3_s.o _mulvdi3_s.o _negvsi2_s.o _negvdi2_s.o _ctors_s.o > _ffssi2_s.o _ffsdi2_s.o _clz_s.o _clzsi2_s.o _clzdi2_s.o _ctzsi2_s.o > _ctzdi2_s.o _popcount_tab_s.o _popcountsi2_s.o _popcountdi2_s.o > _paritysi2_s.o _paritydi2_s.o _powisf2_s.o _powidf2_s.o _powixf2_s.o > _powitf2_s.o _mulhc3_s.o _mulsc3_s.o _muldc3_s.o _mulxc3_s.o _multc3_s.o > _divhc3_s.o _divsc3_s.o _divdc3_s.o _divxc3_s.o _divtc3_s.o _bswapsi2_s.o > _bswapdi2_s.o _clrsbsi2_s.o _clrsbdi2_s.o _fixunssfsi_s.o _fixunsdfsi_s.o > _fixunsxfsi_s.o _fixsfdi_s.o _fixdfdi_s.o _fixxfdi_s.o _fixunssfdi_s.o > _fixunsdfdi_s.o _fixunsxfdi_s.o _floatdisf_s.o _floatdidf_s.o _floatdixf_s.o > _floatundisf_s.o _floatundidf_s.o _floatundixf_s.o _divdi3_s.o _moddi3_s.o > _divmoddi4_s.o _udivdi3_s.o _umoddi3_s.o _udivmoddi4_s.o _udiv_w_sdiv_s.o > addtf3_s.o divtf3_s.o eqtf2_s.o getf2_s.o letf2_s.o multf3_s.o negtf2_s.o > subtf3_s.o unordtf2_s.o fixtfsi_s.o fixunstfsi_s.o floatsitf_s.o > floatunsitf_s.o fixtfdi_s.o fixunstfdi_s.o floatditf_s.o floatunditf_s.o > fixtfti_s.o fixunstfti_s.o floattitf_s.o floatuntitf_s.o extendsftf2_s.o > extenddftf2_s.o trunctfsf2_s.o trunctfdf2_s.o divsf3_s.o divdf3_s.o > save-restore_s.o muldi3_s.o multi3_s.o div_s.o atomic_s.o > enable-execute-stack_s.o unwind-dw2_s.o unwind-dw2-fde-dip_s.o > unwind-sjlj_s.o unwind-c_s.o emutls_s.o libgcc.a -lc && rm -f ./libgcc_s.so > && if [ -f ./libgcc_s.so.1 ]; then mv -f ./libgcc_s.so.1 > ./libgcc_s.so.1.backup; else true; fi && mv ./libgcc_s.so.1.tmp > ./libgcc_s.so.1 && (echo "/* GNU ld script"; echo " Use the shared library, > but some functions are only in"; echo " the static library. */"; echo > "GROUP ( libgcc_s.so.1 -lgcc )" ) > ./libgcc_s.so > /usr/riscv64-linux-gnu/bin/ld: relocation R_RISCV_JAL against `__udivdi3' > which may bind externally can not be used when making a shared object; > recompile with -fPIC > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2022/12/20/gcc-10-cross-ports_20_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221220&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Version:
Processed: found
Processing commands for cont...@bugs.debian.org: > found 1028026 3.0~git+9dc22bd-4 Bug #1028026 [src:vistrails] vistrails: contains non-free font file Marked as found in versions vistrails/3.0~git+9dc22bd-4. > End of message, stopping processing here. Please contact me if you need assistance. -- 1028026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1026597: gcc-10-cross-ports: FTBFS: collect2: error: ld returned 1 exit status
Processing commands for cont...@bugs.debian.org: > reassign 1026597 src:gcc-10 Bug #1026597 [src:gcc-10-cross-ports] gcc-10-cross-ports: FTBFS: collect2: error: ld returned 1 exit status Bug reassigned from package 'src:gcc-10-cross-ports' to 'src:gcc-10'. No longer marked as found in versions gcc-10-cross-ports/20. Ignoring request to alter fixed versions of bug #1026597 to the same values previously set > affects 1026597 src:gcc-10-cross-ports Bug #1026597 [src:gcc-10] gcc-10-cross-ports: FTBFS: collect2: error: ld returned 1 exit status Added indication that 1026597 affects src:gcc-10-cross-ports > thanks Stopping processing here. Please contact me if you need assistance. -- 1026597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026569: marked as done (python-rstr: FTBFS: AttributeError: module 're' has no attribute 'sre_parse')
Your message dated Wed, 11 Jan 2023 00:30:47 +
with message-id
and subject line Bug#1026569: fixed in python-rstr 3.2.0-1
has caused the Debian Bug report #1026569,
regarding python-rstr: FTBFS: AttributeError: module 're' has no attribute
'sre_parse'
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.)
--
1026569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-rstr
Version: 2.2.6-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config
> /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of
> dash-separated 'description-file' will not be supported in future versions.
> Please use the underscore name 'description_file' instead
> warnings.warn(
> running config
> I: pybuild base:240: python3.10 setup.py config
> /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of
> dash-separated 'description-file' will not be supported in future versions.
> Please use the underscore name 'description_file' instead
> warnings.warn(
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3.11 setup.py build
> /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of
> dash-separated 'description-file' will not be supported in future versions.
> Please use the underscore name 'description_file' instead
> warnings.warn(
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_rstr/build/rstr
> copying rstr/__init__.py ->
> /<>/.pybuild/cpython3_3.11_rstr/build/rstr
> copying rstr/rstr_base.py ->
> /<>/.pybuild/cpython3_3.11_rstr/build/rstr
> copying rstr/xeger.py ->
> /<>/.pybuild/cpython3_3.11_rstr/build/rstr
> creating /<>/.pybuild/cpython3_3.11_rstr/build/rstr/tests
> copying rstr/tests/__init__.py ->
> /<>/.pybuild/cpython3_3.11_rstr/build/rstr/tests
> copying rstr/tests/test_xeger.py ->
> /<>/.pybuild/cpython3_3.11_rstr/build/rstr/tests
> copying rstr/tests/test_package_level_access.py ->
> /<>/.pybuild/cpython3_3.11_rstr/build/rstr/tests
> copying rstr/tests/test_rstr.py ->
> /<>/.pybuild/cpython3_3.11_rstr/build/rstr/tests
> I: pybuild base:240: /usr/bin/python3 setup.py build
> /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of
> dash-separated 'description-file' will not be supported in future versions.
> Please use the underscore name 'description_file' instead
> warnings.warn(
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_rstr/build/rstr
> copying rstr/__init__.py ->
> /<>/.pybuild/cpython3_3.10_rstr/build/rstr
> copying rstr/rstr_base.py ->
> /<>/.pybuild/cpython3_3.10_rstr/build/rstr
> copying rstr/xeger.py ->
> /<>/.pybuild/cpython3_3.10_rstr/build/rstr
> creating /<>/.pybuild/cpython3_3.10_rstr/build/rstr/tests
> copying rstr/tests/__init__.py ->
> /<>/.pybuild/cpython3_3.10_rstr/build/rstr/tests
> copying rstr/tests/test_xeger.py ->
> /<>/.pybuild/cpython3_3.10_rstr/build/rstr/tests
> copying rstr/tests/test_package_level_access.py ->
> /<>/.pybuild/cpython3_3.10_rstr/build/rstr/tests
> copying rstr/tests/test_rstr.py ->
> /<>/.pybuild/cpython3_3.10_rstr/build/rstr/tests
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py test
> /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of
> dash-separated 'description-file' will not be supported in future versions.
> Please use the underscore name 'description_file' instead
> warnings.warn(
> running test
> WARNING: Testing via this command is deprecated and will be removed in a
> future version. Users looking for a generic test entry point independent of
> test runner are encouraged to use tox.
> running egg_info
> creating rstr.egg-info
> writing rstr.egg-info/PKG-INFO
> /usr/lib/python3/dist-packages/setuptools/dist.py:160: UserWarning: newlines
> not allowed and will break in the future
> warnings.warn("newlines not allowed and will break in the future")
> writing dependency_links to rstr.egg-info/dependency_links.txt
> writing top-level names to rstr.egg-
Bug#1026520: marked as done (reprotest: FTBFS: AttributeError: module 're' has no attribute 'sre_parse')
Your message dated Wed, 11 Jan 2023 00:30:47 + with message-id and subject line Bug#1026569: fixed in python-rstr 3.2.0-1 has caused the Debian Bug report #1026569, regarding reprotest: FTBFS: AttributeError: module 're' has no attribute 'sre_parse' 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.) -- 1026569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026569 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: reprotest Version: 0.7.22 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/tmp/reprotest.wUfG3L/const_build_path' > dh_python3 -p reprotest --recommends-section=compare > make[1]: Leaving directory '/tmp/reprotest.wUfG3L/const_build_path' >dh_installsystemduser -O--buildsystem=pybuild >dh_perl -O--buildsystem=pybuild >dh_link -O--buildsystem=pybuild >dh_strip_nondeterminism -O--buildsystem=pybuild >dh_compress -O--buildsystem=pybuild >dh_fixperms -O--buildsystem=pybuild >dh_missing -O--buildsystem=pybuild >dh_installdeb -O--buildsystem=pybuild >dh_gencontrol -O--buildsystem=pybuild >dh_md5sums -O--buildsystem=pybuild >dh_builddeb -O--buildsystem=pybuild > dpkg-deb: building package 'reprotest' in '../reprotest_0.7.22_all.deb'. > dpkg-genchanges: info: binary-only upload (no source code included) > dpkg-buildpackage: info: binary-only upload (no source included) > - Captured stderr call > - > dpkg-source --before-build . > debian/rules binary > I: pybuild base:240: python3.11 setup.py config > I: pybuild base:240: python3.10 setup.py config > I: pybuild base:240: /usr/bin/python3.11 setup.py build > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:202: > SetuptoolsDeprecationWarning: Installing 'reprotest.virt' as data is > deprecated, please list it in `packages`. > !! > > > > # Package would be ignored # > > Python recognizes 'reprotest.virt' as an importable package, > but it is not listed in the `packages` configuration of setuptools. > > 'reprotest.virt' has been automatically added to the distribution only > because it may contain data files, but this behavior is likely to change > in future versions of setuptools (and therefore is considered deprecated). > > Please make sure that 'reprotest.virt' is included as a package by using > the `packages` configuration field or the proper discovery methods > (for example by using `find_namespace_packages(...)`/`find_namespace:` > instead of `find_packages(...)`/`find:`). > > You can read more about "package discovery" and "data files" on setuptools > documentation page. > > > !! > > check.warn(importable) > I: pybuild base:240: /usr/bin/python3 setup.py build > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:202: > SetuptoolsDeprecationWarning: Installing 'reprotest.virt' as data is > deprecated, please list it in `packages`. > !! > > > > # Package would be ignored # > > Python recognizes 'reprotest.virt' as an importable package, > but it is not listed in the `packages` configuration of setuptools. > > 'reprotest.virt' has been automatically added to the distribution only > because it may contain data files, but this behavior is likely to change > in future versions of setuptools (and therefore is considered deprecated). > > Please make sure that 'reprotest.virt' is included as a package by using > the `packages` configuration field or the proper discovery methods > (for example by using `find_namespace_packages(...)`/`find_namespace:` > instead of `find_packages(...)`/`find:`). > > You can read more about "package discovery" and "data files" on setuptools > documentation page. > > > !! > > check.warn(importable) > I: pybuild base:240: /usr/bin/python3.11 setup.py install --root > /tmp/reprotest.wUfG3L/const_build_path/debian/reprotest > /usr/lib/python3/dist-packages/setuptools/command/install.py:34: > SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and > pip and other standards-based tools. > warnings.warn( > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:20
Processed: found 1028421 in 3004.1+dfsg-2, reassign 1028422 to wnpp
Processing commands for cont...@bugs.debian.org: > found 1028421 3004.1+dfsg-2 Bug #1028421 [src:salt] Only include in Bookworm with commitment to stable updates Marked as found in versions salt/3004.1+dfsg-2. > reassign 1028422 wnpp Bug #1028422 [clipboard] RFP: clipboard -- unified terminal clipboard tool Warning: Unknown package 'clipboard' Bug reassigned from package 'clipboard' to 'wnpp'. Ignoring request to alter found versions of bug #1028422 to the same values previously set Ignoring request to alter fixed versions of bug #1028422 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1028421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028421 1028422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026622: [Pkg-xmpp-devel] Bug#1026622: python-omemo-backend-signal: FTBFS: ModuleNotFoundError: No module named 'omemo.backends'
On 2023-01-10 19:49, Stefano Rivera wrote: > So, probably time to remove this from the archive, clearly they don't > intend to support the new API. Yes, I'll file a removal request!
Bug#1028438: otpclient: OTP values are all 000000
Package: otpclient Version: 3.1.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? the update from 2.6.3-2 to 3.1.1-1 seems to be when the issue was introduced * What exactly did you do (or not do) that was effective (or ineffective)? ineffective measures taken: reboot uninstall (apt remove --purge otpclient), then reinstall (apt install otpclient) created a new database deleted otpclient config (~/.config/otpclient.cfg) i no longer have a deb for the previous version, so i am unable to test that * What was the outcome of this action? 00 is always returned for every entry (about 20 distinct entriest to choose from) * What outcome did you expect instead? valid OTP codes -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages otpclient depends on: ii libbaseencode1 1.0.15-1 ii libc62.36-8 ii libcotp121.2.7-1 ii libgcrypt20 1.10.1-3 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1 ii libglib2.0-0 2.74.4-1 ii libgtk-3-0 3.24.36-1 ii libjansson4 2.14-2 ii libpng16-16 1.6.39-2 ii libprotobuf-c1 1.4.1-1+b1 ii libqrencode4 4.1.1-1 ii libsecret-1-00.20.5-3 ii libuuid1 2.38.1-4 ii libzbar0 0.23.92-7 otpclient recommends no packages. Versions of packages otpclient suggests: pn otpclient-cli -- no debconf information
Bug#1026569: marked as pending in python-rstr
Control: tag -1 pending Hello, Bug #1026569 in python-rstr reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-rstr/-/commit/91c31f055098729d174c3aee829ca494ff60e791 New upstream release. * New upstream release. - Supports Python 3.11 (Closes: #1026569) (this message was generated automatically) -- Greetings https://bugs.debian.org/1026569
Processed: Bug#1026569 marked as pending in python-rstr
Processing control commands: > tag -1 pending Bug #1026569 [src:python-rstr] python-rstr: FTBFS: AttributeError: module 're' has no attribute 'sre_parse' Bug #1026520 [src:python-rstr] reprotest: FTBFS: AttributeError: module 're' has no attribute 'sre_parse' Added tag(s) pending. Added tag(s) pending. -- 1026520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026520 1026569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026569 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028082: marked as done (pyracerz: contains non-free Alba font)
Your message dated Tue, 10 Jan 2023 23:50:44 + with message-id and subject line Bug#1028082: fixed in pyracerz 0.2+dfsg-1 has caused the Debian Bug report #1028082, regarding pyracerz: contains non-free Alba font 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.) -- 1028082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028082 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pyracerz Version: 0.2-9 Severity: serious The Alba-font license is not very explicit and just mentions free USE. You aer not allowed to modify it or distribute modified versions. Also, from the website http://www.fontalicious.com/project/alba/ and other font download sites it seems that the free use actually means free non-commercial use. Please repack to remove/replace that font. --- End Message --- --- Begin Message --- Source: pyracerz Source-Version: 0.2+dfsg-1 Done: Reiner Herrmann We believe that the bug you reported is fixed in the latest version of pyracerz, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Reiner Herrmann (supplier of updated pyracerz 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, 08 Jan 2023 19:04:08 +0100 Source: pyracerz Architecture: source Version: 0.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Reiner Herrmann Closes: 1028082 Changes: pyracerz (0.2+dfsg-1) unstable; urgency=medium . * Team upload. . [ Debian Janitor ] * Use secure URI in Homepage field. * Bump debhelper from old 12 to 13. * Update standards version to 4.6.1, no changes needed. . [ Reiner Herrmann ] * Repack upstream tarball to exclude non-free font. * Drop non-free fonts and use a cartoony free font from Debian. (Closes: #1028082) * Update d/watch to version 4 and add handling of dfsg suffix. * d/postinst: replace deprecated --force with --force-all. * Bump Standards-Version to 4.6.2. Checksums-Sha1: 540f68056a649f85376e4a90ec6eae22a8b1182c 2164 pyracerz_0.2+dfsg-1.dsc 4adfb0539332896b1897df77a418ca87fc1cd10a 4626268 pyracerz_0.2+dfsg.orig.tar.xz d9f7f3cb6e5f1fdeeea8d0885ea72381f821cda4 14848 pyracerz_0.2+dfsg-1.debian.tar.xz be975a21fd583638c1030629c51fffd8dc8bfd1e 6885 pyracerz_0.2+dfsg-1_amd64.buildinfo Checksums-Sha256: 22facc16c5e480eac6497db940d6566cce80538a45a4b2f63dfb040d43ed54dd 2164 pyracerz_0.2+dfsg-1.dsc 75ade0d70d912dcc36ecd66061b19d0c2583d9c93665ae7a055d569b7a23baff 4626268 pyracerz_0.2+dfsg.orig.tar.xz 63b3056b93c90186b2c01873037f688e42ff05cb855954b12897b3bf16f36de6 14848 pyracerz_0.2+dfsg-1.debian.tar.xz 956d1b9fefec16d51058f3bfc63c2122066795050b7988257f384363f474a86f 6885 pyracerz_0.2+dfsg-1_amd64.buildinfo Files: 29ffc2404800200de15f201ce169827b 2164 games optional pyracerz_0.2+dfsg-1.dsc 8eb2e3a4f79e96c70e870e8a28147963 4626268 games optional pyracerz_0.2+dfsg.orig.tar.xz 330f9dc0178026db395e40e69f3b1836 14848 games optional pyracerz_0.2+dfsg-1.debian.tar.xz bd63f0ede50feffd864bf25c3dcfb875 6885 games optional pyracerz_0.2+dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAmO99V5fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1Hk8TUQAJuNwaCxdNoPydnxWk2q//oSAoW0e9wf7NUH 54NYxxusQ3wGFYOPu1ip2XBjX3qUABFFJogOaQZwwmWHZwrlEH6pSOQOty+Mk/hr p1Knoj06esBJGad/qxn3pSG2gh8CLaSPiDmPOXhakgZxH5YU6SFSbysT0z2xeuUd RaJ1dGfYxAFs9Om6mUIGHSqGaDgxO3Y+2Ela+fnhn1dKnymumdLbhprXA1xN5BtX qIu/yGDa8uCOn3i8cixVjo8ubf3lSirrUxMuncXE8S8oJwrkICLWkHUle7VeO89M aMeceiCerL50DEH9k1TiXD8a908YDozx1R2k2no456dJxLiR2OiPxJbjstyEaZyQ zj1OTRnSVc6GgrGOgRsdviQPMavQAR8wdcWHxx+IouDTArfv77aYA+uTqo3lOK8N FGQET+t4afiIARtKPM1Sc4QdDcOU0B3j81QByKUAyqxAzPFsgtm+dctx5Y2DPSOn 9WOUuqHdV/ZPqJkrvjc4GfcvERMgq8ql2Dcbfdxi7JMrm+nGornLUoVI7h/O5iRW 5CNa0txYBfy20pxFxZ8+a3TzlJHgWIyH5iBleO87JUaI6SPix4BxEFquObFagReZ KaZ4H9htnYvOO+wUOUVuqr5foeU6us1ktGhMIvAqryUAWYJWKhRSCgzZSn4O69Nb N7P9KdqV =yFvB -END PGP SIGNATURE End Me
Bug#1026622: python-omemo-backend-signal: FTBFS: ModuleNotFoundError: No module named 'omemo.backends'
I see that python-omemo 1.0.0 is a complete rewrite: https://github.com/Syndace/python-omemo/blob/main/CHANGELOG.md#100---1st-of-november-2022 This removed the omemo.backends module. I also see that the upstream has archived python-omemo-backend-signal repo, around the same time: https://github.com/Syndace/python-omemo-backend-signal So, probably time to remove this from the archive, clearly they don't intend to support the new API. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Processed: kodi: FTBFS in bullseye (fatal error: date/tz.h: No such file or directory)
Processing control commands: > fixed -1 2:20.0~rc2+dfsg-1 Bug #1028434 [src:kodi] kodi: FTBFS in bullseye (fatal error: date/tz.h: No such file or directory) Marked as fixed in versions kodi/2:20.0~rc2+dfsg-1. -- 1028434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028434 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028196: marked as done (offlineimap3: Python 3.11 breaks SQLite Multithread Check)
Your message dated Tue, 10 Jan 2023 22:21:25 + with message-id and subject line Bug#1027837: fixed in offlineimap3 0.0~git20211018.e64c254+dfsg-2 has caused the Debian Bug report #1027837, regarding offlineimap3: Python 3.11 breaks SQLite Multithread Check 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.) -- 1027837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: offlineimap3 Version: 0.0~git20211018.e64c254+dfsg-1 Severity: grave Justification: renders package unusable Hi, with the introduction of Python 3.11 offlineimap does no longer work due to a failing multithread safety check for SQLite. The issue was handled upstream in https://github.com/OfflineIMAP/offlineimap3/pull/139 The patch included upstream applies cleanly to the slightly older release in unstable and works fine as far as I can tell after a day. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages offlineimap3 depends on: ii ca-certificates 20211016 ii python3 3.11.1-1 ii python3-distro1.8.0-1 ii python3-imaplib2 2.57-5.2 offlineimap3 recommends no packages. Versions of packages offlineimap3 suggests: pn python3-gssapi -- no debconf information --- End Message --- --- Begin Message --- Source: offlineimap3 Source-Version: 0.0~git20211018.e64c254+dfsg-2 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of offlineimap3, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated offlineimap3 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: Tue, 10 Jan 2023 22:44:57 +0100 Source: offlineimap3 Architecture: source Version: 0.0~git20211018.e64c254+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Bastian Germann Closes: 1027837 Changes: offlineimap3 (0.0~git20211018.e64c254+dfsg-2) unstable; urgency=medium . * Team upload * Patch: Python 3.11 compatible threadsafety check (Closes: #1027837) Checksums-Sha1: 4b3b53156306846884f595af71b7fba040f53c34 2285 offlineimap3_0.0~git20211018.e64c254+dfsg-2.dsc 7a79178da6ed89c1005b38725ce9b929ac0fe19e 7368 offlineimap3_0.0~git20211018.e64c254+dfsg-2.debian.tar.xz 83307ad0d14dc8b5f3e31bcff3b189d881591951 6833 offlineimap3_0.0~git20211018.e64c254+dfsg-2_source.buildinfo Checksums-Sha256: 8087f85ba0ba640d70d7b8a348e7baec9ab1d2739eb815762043c99b5064ec85 2285 offlineimap3_0.0~git20211018.e64c254+dfsg-2.dsc 74ae31dff16d90505e62c77d144d8855aacc62b8a8b08848f8e3032f59265219 7368 offlineimap3_0.0~git20211018.e64c254+dfsg-2.debian.tar.xz c0e73a9bc13cca76722ac7c3e15affea5420bf1b406a0c95e297a9057a3e5f98 6833 offlineimap3_0.0~git20211018.e64c254+dfsg-2_source.buildinfo Files: 6d5d332e6331cf12b9318cf956592fee 2285 mail optional offlineimap3_0.0~git20211018.e64c254+dfsg-2.dsc 2ee4e2dcdd55778b5d426e86c71e06d1 7368 mail optional offlineimap3_0.0~git20211018.e64c254+dfsg-2.debian.tar.xz d88d1f2c4c8cd92435be68c2a6399653 6833 mail optional offlineimap3_0.0~git20211018.e64c254+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmO94HQQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFBckDADGHUbt75WeZVkNGT/rNzav5KMGYBfKCDqt JPytAS/jKr1vhNcHp76Wv5spWnxuIBljYdYw6awviRtE2p2q1HiSkI9DCHGapkyD UCQKmYJ40kEhawY93ljHhapgs2pcD6FDfGHhYYN8SACtjh6pmdeAnwUWZSswxnFl DuC1ztus+qPbtT7PkCDnDKXqCuKIXNWwu8M2TdHMb9CshjPjNoRg0zXVSoafkeK5 PwBOBWnbLIdrMHJ3uLteep4R2oIjxvl0sGa78kVhIvYVnqulXV3DwAgC5Tjcw+R9 Nf5H3V8WclRs78Ixw8GavIzwAPF+36ji6983PIwj+KJpsI62xb/7llWajn4EN31u /de8f+Fh17IK+ZePSiMBU1GDGZRVR3ykD2jXj5rGurN890WoQuJDrtJYVtBs8vxZ Gt7k7xSsRyvhQ0mlbg8KebpCtfI
Bug#1027837: marked as done (offlineimap3: "AssertionError: Your sqlite is not multithreading safe" with python3.11)
Your message dated Tue, 10 Jan 2023 22:21:25 + with message-id and subject line Bug#1027837: fixed in offlineimap3 0.0~git20211018.e64c254+dfsg-2 has caused the Debian Bug report #1027837, regarding offlineimap3: "AssertionError: Your sqlite is not multithreading safe" with python3.11 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.) -- 1027837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: offlineimap3 Version: 0.0~git20211018.e64c254+dfsg-1 Severity: grave Tags: fixed-upstream patch Justification: renders package unusable Forwarded: https://github.com/OfflineIMAP/offlineimap3/issues/136 Control: block 1026825 by -1 After upgrading to python3 (>= 3.11) I get lots of these errors: > ERROR: ERROR in syncfolder for REDACTED folder .REDACTED: Traceback (most > recent call last): > File "/usr/share/offlineimap3/offlineimap/accounts.py", line 610, in > syncfolder > statusfolder.openfiles() > File "/usr/share/offlineimap3/offlineimap/folder/LocalStatusSQLite.py", > line 107, in openfiles > assert sqlite.threadsafety == 1, 'Your sqlite is not multithreading safe.' > > AssertionError: Your sqlite is not multithreading safe and as far as I can tell, no mail is synchronized. https://github.com/OfflineIMAP/offlineimap3/pull/139 appears to be the upstream solution for this, and seems to be a suitable patch for the version currently in Debian. Please see attached or the upstream PR. smcv -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500, 'oldstable-debug'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages offlineimap3 depends on: ii ca-certificates 20211016 ii python3 3.11.1-1 ii python3-distro1.8.0-1 ii python3-imaplib2 2.57-5.2 offlineimap3 recommends no packages. Versions of packages offlineimap3 suggests: pn python3-gssapi -- no debconf information -- debsums errors found: debsums: changed file /usr/share/offlineimap3/offlineimap/folder/LocalStatusSQLite.py (from offlineimap3 package) >From 7cd32cf834b34a3d4675b29bebcd32dc1e5ef128 Mon Sep 17 00:00:00 2001 From: 0pointerexception Date: Thu, 17 Nov 2022 19:43:58 +0100 Subject: [PATCH] LocalStatusSQLite.py: Python 3.11 compatible threadsafety check Signed-off-by: 0pointerexception --- offlineimap/folder/LocalStatusSQLite.py | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/offlineimap/folder/LocalStatusSQLite.py b/offlineimap/folder/LocalStatusSQLite.py index a576b9ca..3c44643f 100644 --- a/offlineimap/folder/LocalStatusSQLite.py +++ b/offlineimap/folder/LocalStatusSQLite.py @@ -17,7 +17,7 @@ import os import sqlite3 as sqlite -from sys import exc_info +from sys import exc_info,version_info from threading import Lock from .Base import BaseFolder @@ -75,6 +75,11 @@ def __init__(self, name, repository): self.filename = os.path.join(self.getroot(), self.getfolderbasename()) self._newfolder = False # Flag if the folder is new. +""" +sqlite threading mode must be 3 as of Python 3.11, checking against +1 for versions below Python 3.11 to sustain backwards compatibility. +""" +self._threading_mode_const = 3 if version_info.minor >=11 else 1 dirname = os.path.dirname(self.filename) if not os.path.exists(dirname): @@ -102,9 +107,10 @@ def __exit__(self, exc_type, exc_val, exc_tb): if self._in_transactions < 1: self.connection.commit() + def openfiles(self): # Make sure sqlite is in multithreading SERIALIZE mode. -assert sqlite.threadsafety == 1, 'Your sqlite is not multithreading safe.' +assert sqlite.threadsafety == self._threading_mode_const, 'Your sqlite is not multithreading safe.' with self._databaseFileLock.getLock(): # Try to establish connection, no need for threadsafety in __init__. --- End Message --- --- Begin Message -
Processed: affects 1014503
Processing commands for cont...@bugs.debian.org: > affects 1014503 src:bind-dyndb-ldap Bug #1014503 [bind9-libs] bind9-libs: please provide libraries that enable reverse dependencies to use them Added indication that 1014503 affects src:bind-dyndb-ldap > thanks Stopping processing here. Please contact me if you need assistance. -- 1014503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014503 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028373: marked as done (pandas: test-failing warnings with numpy 1.24)
Your message dated Tue, 10 Jan 2023 21:31:51 + with message-id and subject line forgot to close this in the upload has caused the Debian Bug report #1028373, regarding pandas: test-failing warnings with numpy 1.24 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.) -- 1028373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pandas Version: 1.5.2+dfsg-4 Severity: serious Looks like the numpy 1.24 issues I knew about weren't the only ones. Fix in progress in Salsa. --- End Message --- --- Begin Message --- Version: 1.5.2+dfsg-5--- End Message ---
Bug#1028354: marked as done (apbs fails with python3.11: "invalid mode rU")
Your message dated Tue, 10 Jan 2023 21:35:19 + with message-id and subject line Bug#1028354: fixed in apbs 3.4.1-5 has caused the Debian Bug report #1028354, regarding apbs fails with python3.11: "invalid mode rU" 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.) -- 1028354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apbs Version: 3.4.1-4 Severity: grave Tags: patch Justification: renders package unusable User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu lunar ubuntu-patch apbs fails its autopkgtests with python3.11, revealing a bug in the software, because it uses a mode flag to open() which has been deprecated since python 3 and is now obsolete in python 3.11: [...] Testing input file apbs-mol-parallel.in Splitting the input file into 4 separate files using the inputgen utility Test failed: invalid mode: 'rU' Elapsed time: 0.000597 seconds [...] (https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/a/apbs/20221229_092334_1918a@/log.gz) This is not an autopkgtest regression in Debian because the autopkgtest itself is also buggy, using bash-specific shell syntax in a file with no interpreter line that as a result fails under /bin/sh. (I'm not sure why it gets farther on Ubuntu's autopkgtest infrastructure.) However, despite not being detected as an autopkgtest regression, it shows a significant code defect when run under python3.11 and should be fixed. Please see the attached patch. Thanks for considering, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru apbs-3.4.1/debian/patches/open-U-obsolete.patch apbs-3.4.1/debian/patches/open-U-obsolete.patch --- apbs-3.4.1/debian/patches/open-U-obsolete.patch 1969-12-31 16:00:00.0 -0800 +++ apbs-3.4.1/debian/patches/open-U-obsolete.patch 2023-01-09 13:27:36.0 -0800 @@ -0,0 +1,21 @@ +Description: Drop obsolete "U" mode passed to open() + The "U" mode has been deprecated in python since python3 and has had no + effect. In python 3.11, it is now disallowed. Drop this mode flag that + causes runtime failures. +Author: Steve Langasek +Last-Update: 2023-01-09 +Forwarded: no + +Index: apbs-3.4.1/tools/manip/inputgen.py +=== +--- apbs-3.4.1.orig/tools/manip/inputgen.py apbs-3.4.1/tools/manip/inputgen.py +@@ -311,7 +311,7 @@ +file (string) + """ + nproc = 0 +-file = open(filename, "rU") ++file = open(filename, "r") + text = "" + while 1: + line = file.readline() diff -Nru apbs-3.4.1/debian/patches/series apbs-3.4.1/debian/patches/series --- apbs-3.4.1/debian/patches/series2022-06-04 00:58:09.0 -0700 +++ apbs-3.4.1/debian/patches/series2023-01-09 13:26:06.0 -0800 @@ -5,3 +5,4 @@ python3.patch cmake.patch docs.patch +open-U-obsolete.patch --- End Message --- --- Begin Message --- Source: apbs Source-Version: 3.4.1-5 Done: Michael Banck We believe that the bug you reported is fixed in the latest version of apbs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Banck (supplier of updated apbs 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: Tue, 10 Jan 2023 21:56:38 +0100 Source: apbs Architecture: source Version: 3.4.1-5 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Michael Banck Closes: 1028354 Changes: apbs (3.4.1-5) unstable; urgency=medium . * Team upload. * Add patch to drop obsolete "U" mode passed to open(), which causes runtime errors with py
Bug#965806: marked as done (rtpg: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 10 Jan 2023 21:26:29 + with message-id and subject line Bug#1028377: Removed package(s) from unstable has caused the Debian Bug report #965806, regarding rtpg: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rtpg Version: 0.2.11-3 Severity: normal Usertags: compat-5-6-removal Hi, The package rtpg uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Version: 0.2.11-3.1+rm Dear submitter, as the package rtpg has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1028377 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#904010: marked as done (edb: FTBFS in sid (build-depends on emacs24))
Your message dated Tue, 10 Jan 2023 21:17:10 + with message-id and subject line Bug#1028387: Removed package(s) from unstable has caused the Debian Bug report #904010, regarding edb: FTBFS in sid (build-depends on emacs24) 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.) -- 904010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: edb Version: 1.31-3 User: trei...@debian.org Usertags : edos-uninstallable Severity: serious Hi, edb build-depends on emacs24 which does no longer live in sid. -Ralf. --- End Message --- --- Begin Message --- Version: 1.31-3+rm Dear submitter, as the package edb has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1028387 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#840748: marked as done (edb: install script failed for emacs25 because of :indent keyword)
Your message dated Tue, 10 Jan 2023 21:17:10 + with message-id and subject line Bug#1028387: Removed package(s) from unstable has caused the Debian Bug report #840748, regarding edb: install script failed for emacs25 because of :indent keyword 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.) -- 840748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: edb Version: 1.31-3 Severity: important Dear Maintainer, emacs25 just reached the archive, but edb seems to have problems with it Install edb for emacs25 install/edb: Handling install of emacsen flavor emacs25 install/edb: Byte-Compiling in dir /usr/share/emacs/site-lisp/edb/ ... No such keyword: :indent ERROR: install script from edb package failed dpkg: error processing package emacs25 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: emacs25 E: Sub-process /usr/bin/dpkg returned an error code (1) Regards, -- Agustin --- End Message --- --- Begin Message --- Version: 1.31-3+rm Dear submitter, as the package edb has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1028387 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: bug 1026286 is forwarded to https://github.com/numba/numba/issues/8464
Processing commands for cont...@bugs.debian.org: > forwarded 1026286 https://github.com/numba/numba/issues/8464 Bug #1026286 [python3-numba] Unsatisfiable versioned dependency on python3-numpy Set Bug forwarded-to-address to 'https://github.com/numba/numba/issues/8464'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#853443: marked as done (hidrd: ftbfs with GCC-7)
Your message dated Tue, 10 Jan 2023 21:07:38 + with message-id and subject line Bug#1028230: Removed package(s) from unstable has caused the Debian Bug report #853443, regarding hidrd: ftbfs with GCC-7 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.) -- 853443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:hidrd Version: 0.2.0-12 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-7 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The severity of this report may be raised before the buster release. There is no need to fix this issue in time for the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc7-20170126/hidrd_0.2.0-12_unstable_gcc7.log The last lines of the build log are at the end of this report. To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-7/porting_to.html [...] m4 -I "../../.." hidrd.xsd.m4 > hidrd.xsd make all-recursive make[6]: Entering directory '/<>/lib/fmt/xml' Making all in snk make[7]: Entering directory '/<>/lib/fmt/xml/snk' /bin/bash ../../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../.. -I/<> -I/<>/include -D_GNU_SOURCE -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libxml2 -Wall -Wextra -Werror -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o libhidrd_xml_snk_la-element.lo `test -f 'element.c' || echo './'`element.c /bin/bash ../../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../.. -I/<> -I/<>/include -D_GNU_SOURCE -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libxml2 -Wall -Wextra -Werror -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o libhidrd_xml_snk_la-element_break.lo `test -f 'element_break.c' || echo './'`element_break.c /bin/bash ../../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../.. -I/<> -I/<>/include -D_GNU_SOURCE -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libxml2 -Wall -Wextra -Werror -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o libhidrd_xml_snk_la-group.lo `test -f 'group.c' || echo './'`group.c /bin/bash ../../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../.. -I/<> -I/<>/include -D_GNU_SOURCE -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libxml2 -Wall -Wextra -Werror -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o libhidrd_xml_snk_la-item.lo `test -f 'item.c' || echo './'`item.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../.. -I/<> -I/<>/include -D_GNU_SOURCE -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libxml2 -Wall -Wextra -Werror -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c element.c -fPIC -DPIC -o .libs/libhidrd_xml_snk_la-element.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../.. -I/<> -I/<>/include -D_GNU_SOURCE -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libxml2 -Wall -Wextra -Werror -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c element_break.c -fPIC -DPIC -o .libs/libhidrd_xml_snk_la-element_break.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../.. -I/<> -I/<>/include -D_GNU_SOURCE -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libxml2 -Wall -Wextra -Werror -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c group.c -fPIC -DPIC -o .libs/libhidrd_xml_snk_la-group.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../.. -I/<> -I/<>/include -D_GNU_SOURCE -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libxml2 -Wall -Wextra -Werror -g -O2 -fdebug-prefix-map=/<>=. -fst
Bug#822379: marked as done (hidrd FTBFS on several platforms)
Your message dated Tue, 10 Jan 2023 21:07:38 + with message-id and subject line Bug#1028230: Removed package(s) from unstable has caused the Debian Bug report #822379, regarding hidrd FTBFS on several platforms 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.) -- 822379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: hidrd Version: 0.2.0-12 Severity: serious Justification: fails to build from source hidrd failed to build on several platforms, see https://buildd.debian.org/status/package.php?p=hidrd&suite=sid All failed builds did so thanks to the hidrd_num_test test in lib/utils: /«PKGBUILDDIR»/lib/util/.libs/lt-hidrd_num_test:num_test.c:322: Unexpected formatting result: 128 instead of -128 -- With best wishes Dmitry -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Version: 0.2.0-12+rm Dear submitter, as the package hidrd has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1028230 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1011437: marked as done (Should bind9-libs be shipped in bookworm?)
Your message dated Tue, 10 Jan 2023 21:07:06 + with message-id and subject line Bug#1011538: Removed package(s) from unstable has caused the Debian Bug report #1011437, regarding Should bind9-libs be shipped in bookworm? 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.) -- 1011437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011437 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bind9-libs Version: 1:9.11.19+dfsg-2.1 Severity: serious Tags: bookwoem sid Control: block -1 by 942502 942501 Looking at #942501 and #942502, the intention seems to be to not ship bind9-libs in bookworm. --- End Message --- --- Begin Message --- Version: 1:9.11.19+dfsg-2.1+rm Dear submitter, as the package bind9-libs has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1011538 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1026286: Unsatisfiable versioned dependency on python3-numpy
On Sat, 2022-12-17 at 20:19 +0100, Enrico Zini wrote: > Package: python3-numba > Version: 0.56.2+dfsg-2 > Severity: serious > > Hello, > > thank you for maintaining python3-numba! > > Unfortunately the package is currently uninstallable in sid. > > It depends on `python3-numpy (<< 1:1.22), python3-numpy (>= > 1:1.20.0)`, > but the version of python3-numpy in sid is 1:1.23.5-2. > Yeah I know. Numba frequently lags on python and numpy updates. I think they're closer to having numpy fixes done than python 3.11 though. There's some patches, I've got some of them applied by the system I was using for a build server broke and I haven't had a chance to fix it.
Bug#1028354: marked as pending in apbs
Control: tag -1 pending Hello, Bug #1028354 in apbs reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debichem-team/apbs/-/commit/ef60a2c4862bd5df8868126c4f940fe450dae8f8 Add patch to drop obsolete "U" mode passed to open(), which causes runtime errors with python 3.11, by Steve Langasek. Closes: #1028354. (this message was generated automatically) -- Greetings https://bugs.debian.org/1028354
Processed: Bug#1028354 marked as pending in apbs
Processing control commands: > tag -1 pending Bug #1028354 [apbs] apbs fails with python3.11: "invalid mode rU" Added tag(s) pending. -- 1028354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027851: pytorch in the upcoming stable release
Control: tags -1 + help Hi Mo, M. Zhou, on 2023-01-10: > Things has gone out of my expectation ... python 3.11 transition is > already on the way. I thought the default python version would > be 3.10, so prepared pytorch 1.12 for the next stable release. > > But python 3.11 is another story. The upstream support for 3.11 is > not fully ready: > https://github.com/pytorch/pytorch/issues/86566 > 1.13 has preliminary support. Full support is expected for the 1.14 > release which will be many months later. > > So I'm sure the next stable release will not ship pytorch due to > broken python 3.11 compatibility, and my > personal bandwidth is not enough to rush anything before the freeze. Thank you for having been able to carry pytorch this far, I mark the corresponding bug entry accordingly. If someone looks into this bug, please beware that last time I did a rebuild of pytorch with the test suite, it required a rather high-end configuration. In hope this helps, -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. On air: Earthside - Mob Mentality (feat. Lajon Witherspoon & Mo… signature.asc Description: PGP signature
Processed: Re: pytorch in the upcoming stable release
Processing control commands: > tags -1 + help Bug #1027851 [src:pytorch] pytorch FTBFS with Python 3.11 as default version Added tag(s) help. -- 1027851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027208: severity of 1027208 is important
severity 1027208 important thanks Hi. I think this is what you really meant.
Processed: severity of 1027208 is important
Processing commands for cont...@bugs.debian.org: > severity 1027208 important Bug #1027208 [src:scikit-learn] scikit-learn: autopkgtest fail with numpy/1.24.1 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1027208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1004441: unblocking chromium?
Processing control commands: > close 1004441 Bug #1004441 [release.debian.org] Chromium: decide before the freeze if it can be part of bookworm Marked Bug as done -- 1004441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004441: unblocking chromium?
Control: close 1004441 Hi, On 10-01-2023 21:05, Moritz Mühlenhoff wrote: Sounds good! Can you add a README.Debian.security to the next unstable uploads which briefly documents that? When bookworm has been released we can also add a note to Chromium DSAs to give folks a headsup. So, it sounds like we agree that chromium can be part of bookworm from security point of view. Closing the bug that reminded us to take that decision. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1028421: Only include in Bookworm with commitment to stable updates
Source: salt Severity: serious salt is currently RC-buggy and not in testing, but regardless of the remaining RC bugs getting fixed it should only get re-included with a reliable commitment to backport/test security-updates across the typical three year life cycle (two years of stable-security and one year of oldstable-security). Cheers, Moritz
Processed (with 1 error): Re: scikit-learn: autopkgtest fail with numpy/1.24.1
Processing control commands: > tags -1 important Unknown tag/s: important. Recognized are: patch wontfix moreinfo unreproducible help security upstream pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye bullseye-ignore bookworm bookworm-ignore trixie trixie-ignore. > tags -1 unreproducible Bug #1027208 [src:scikit-learn] scikit-learn: autopkgtest fail with numpy/1.24.1 Added tag(s) unreproducible. > tags -1 moreinfo Bug #1027208 [src:scikit-learn] scikit-learn: autopkgtest fail with numpy/1.24.1 Added tag(s) moreinfo. -- 1027208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027208: scikit-learn: autopkgtest fail with numpy/1.24.1
Control: tags -1 important Control: tags -1 unreproducible Control: tags -1 moreinfo Hi, I've build version 1.1.2+dfsg-92 from unstable without any problem in a pbuilder chroot. It seems the problem was solved with one of the latest uploads. Kind regards Andreas. -- http://fam-tille.de
Bug#1004441: unblocking chromium?
Am Sun, Jan 08, 2023 at 12:27:52AM -0500 schrieb Andres Salomon: > > On Fri, Jan 6 2023 at 11:36:02 AM +0200, Adrian Bunk > wrote: > > On Fri, Jan 06, 2023 at 10:18:16AM +0100, Moritz Muehlenhoff wrote: > > > ... > > > We might consider to set some expectation for oldstable-security, > > > though e.g state that > > > oldstable-security updates stop three months after the release of > > > stable or so. > > > > > > Yeah, I like that idea. I think I could comfortably handle about 6 months of > dual security support (stable+oldstable), personally. Sounds good! Can you add a README.Debian.security to the next unstable uploads which briefly documents that? When bookworm has been released we can also add a note to Chromium DSAs to give folks a headsup. Cheers, Moritz
Bug#1026286: Unsatisfiable versioned dependency on python3-numpy
On Sat, Dec 17, 2022 at 08:19:47PM +0100, Enrico Zini wrote: > thank you for maintaining python3-numba! > Unfortunately the package is currently uninstallable in sid. > It depends on `python3-numpy (<< 1:1.22), python3-numpy (>= 1:1.20.0)`, > but the version of python3-numpy in sid is 1:1.23.5-2. This seems to be the relevant upstream issue: https://github.com/numba/numba/issues/8464 Enrico -- GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini
Bug#1028192: [Pkg-xmpp-devel] Bug#1028192: Needs to block python3-nbxmpp
Am 10.01.23 um 20:03 schrieb Martin: Btw. thanks for testing the latest nbxmpp master! You're welcome! After testing the patch I also tried installing nbxmpp and gajim in a virtualenv. And there Gajim starts! "pip3 list" output within the virtualenv: Package Version Editable project location - --- - cffi 1.15.1 cryptography 39.0.0 css-parser1.0.8 gajim 1.6.0 /home/fiona/development/gajim idna 3.4 importlib-metadata6.0.0 jaraco.classes3.2.3 jeepney 0.8.0 keyring 23.13.1 more-itertools9.0.0 nbxmpp4.0.0 /home/fiona/development/python-nbxmpp packaging 23.0 Pillow9.4.0 pip 22.3.1 precis-i18n 1.0.5 protobuf 4.21.12 pycairo 1.23.0 pycparser 2.21 PyGObject 3.42.2 python-axolotl0.2.3 python-axolotl-curve25519 0.4.1.post2 SecretStorage 3.3.3 setuptools65.6.3 wheel 0.38.4 zipp 3.11.0 PyGObject is at the same version as in unstable, as is cffi. I wonder if there's an ABI incompatibility somewhere, or something similarly tricky? I'm not sure how to debug it, though.
Processed: tagging 945713, tagging 936854, tagging 942501
Processing commands for cont...@bugs.debian.org:
> tags 945713 - bullseye
Bug #945713 {Done: Bastian Germann } [src:stx2any] stx2any:
Python2 removal in sid/bullseye
Removed tag(s) bullseye.
> tags 936854 - bullseye
Bug #936854 {Done: Bastian Germann } [src:libewf] libewf:
Python2 removal in sid/bullseye
Removed tag(s) bullseye.
> tags 942501 + sid bookworm
Bug #942501 [src:milter-greylist] src:milter-greylist: please drop libbind-dev
build dependency, it's not in use and libbind-dev is going away
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936854
942501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942501
945713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1028416: systemctl kexec doesn't shutdown system properly and corrupts mounted filesystems
Package: systemd Version: 252.4-1 Severity: grave So do kexec-tools if a user has chosen to use it for reboots during package configuration. Either of the following can cause fs corruption (to the point one has to use `fsck -y`): a) the procedure described in https://wiki.archlinux.org/title/Kexec#Manually 1. `kexec -l /boot/vmlinuz-6.0.0-6-amd64 --initrd=/boot/initrd-6.0.0-6-amd64 --reuse-cmdline` 2. `systemctl kexec` b) Just choosing to use kexec for reboots when installing it, and then rebooting. -- Package-specific info: -- System Information: Debian Release: bookworm/sid Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd depends on: ii libacl1 2.3.1-2 ii libaudit1 1:3.0.7-1.1+b2 ii libblkid1 2.38.1-4 ii libc6 2.36-8 ii libcap2 1:2.66-3 ii libcryptsetup12 2:2.6.0-2 ii libfdisk1 2.38.1-4 ii libgcrypt20 1.10.1-3 ii libkmod2 30+20221128-1 ii liblz4-1 1.9.4-1 ii liblzma5 5.4.0-0.1 ii libmount1 2.38.1-4 ii libp11-kit0 0.24.1-2 ii libseccomp2 2.5.4-1+b2 ii libselinux1 3.4-1+b4 ii libssl3 3.0.7-1 ii libsystemd-shared 252.4-1 ii libsystemd0 252.4-1 ii libzstd1 1.5.2+dfsg2-3 ii mount 2.38.1-4 Versions of packages systemd suggests: ii libfido2-1 1.12.0-2 ii libqrencode4 4.1.1-1 ii libtss2-esys-3.0.2-0 3.2.1-2 ii libtss2-mu0 3.2.1-2 ii libtss2-rc0 3.2.1-2 ii policykit-1 122-1 ii polkitd 122-1 pn systemd-boot pn systemd-container pn systemd-homed ii systemd-resolved 252.4-1 pn systemd-userdbd Versions of packages systemd is related to: ii dbus-user-session 1.14.4-1 ii dracut pn initramfs-tools 0.142 pn libnss-systemd ii libpam-systemd 252.4-1 ii udev 252.4-1 -- no debconf information
Processed: Re: [Pkg-xmpp-devel] Bug#1028192: Needs to block python3-nbxmpp
Processing control commands: > clone -1 -2 Bug #1028192 [gajim] gajim: Gajim 1.6.0-1 crashes on connect Bug 1028192 cloned as bug 1028413 > reassign -2 python3-nbxmpp 4.0.0-1 Bug #1028413 [gajim] gajim: Gajim 1.6.0-1 crashes on connect Bug reassigned from package 'gajim' to 'python3-nbxmpp'. No longer marked as found in versions gajim/1.6.0-1. Ignoring request to alter fixed versions of bug #1028413 to the same values previously set Bug #1028413 [python3-nbxmpp] gajim: Gajim 1.6.0-1 crashes on connect Marked as found in versions python-nbxmpp/4.0.0-1. > retitle -2 python3-nbxmpp: Gajim 1.6.0-1 crashes on connect Bug #1028413 [python3-nbxmpp] gajim: Gajim 1.6.0-1 crashes on connect Changed Bug title to 'python3-nbxmpp: Gajim 1.6.0-1 crashes on connect' from 'gajim: Gajim 1.6.0-1 crashes on connect'. -- 1028192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028192 1028413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028413 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028192: [Pkg-xmpp-devel] Bug#1028192: Needs to block python3-nbxmpp
Control: clone -1 -2 Control: reassign -2 python3-nbxmpp 4.0.0-1 Control: retitle -2 python3-nbxmpp: Gajim 1.6.0-1 crashes on connect On 2023-01-10 18:29, Fiona Klute wrote: > In that case python3-nbxmpp 4.x must not migrate either, because it > breaks Gajim 1.5.x. I'm not sure what's the proper way to achieve that, > should I file another bug or is there some "blocks" mechanism in the BTS? I don't think so. Let's see, if cloning works. We can later merge the bug reports again. Btw. thanks for testing the latest nbxmpp master!
Bug#969907: inkscape, etc. crashing with mismatched libpoppler102 and libpoppler-glib8
What about this solution:
In src:poppler provide a virtual package
Package: libpoppler-glibYY
Provides: libpopplerXX-glibYY (= ${binary:Version})
(where XX and YY are the sonames of the respective packages)
and in src:inkscape (and maybe others) add some sed
manipulation to d/rules:
# generate a virtual package dependency to ensure inkscape uses
# matching versions of libpopplerXX and libpoppler-glibYY
# #969907
execute_after_dh_shlibdeps:
sed -ri -e '/shlibs:Depends=/ s/$$/, POPPLER-GLIB/' \
-e 's/(libpoppler[0-9]+)(.*)POPPLER/\1\2\1/' \
-e 's/libpoppler-(glib[0-9]+)(.*)GLIB/\1\2\1/' \
debian/inkscape.substvars
Just tried that and it generated:
Depends: ..., libpoppler-glib8 (>= 0.18.0), libpoppler123 (>= 22.08.0), ...,
libpoppler123-glib8
This should ensure inkscape depends on libpopplerXX and
libpoppler-glibYY with matching versions (something that
cannot be expressed easily in regular shared library
package dependencies) without unneccessarily tightening
poppler dependencies in packages that use only one of
these libraries.
(This will intentionally generate an unsatisfiable meta
dependency once inkscape no longer links to both
libpopplerXX and libpoppler-glibYY.)
Andreas
Processed: thrift: FTBFS in bullseye (expired certificates in test suite)
Processing commands for cont...@bugs.debian.org:
> reopen 1010120
Bug #1010120 {Done: Laszlo Boszormenyi (GCS) } [src:thrift]
thrift: FTBFS in bullseye (expired certificates in test suite)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions thrift/0.16.0-6.
> found 1010120 0.13.0-6
Bug #1010120 [src:thrift] thrift: FTBFS in bullseye (expired certificates in
test suite)
Ignoring request to alter found versions of bug #1010120 to the same values
previously set
> found 1010120 0.16.0-3
Bug #1010120 [src:thrift] thrift: FTBFS in bullseye (expired certificates in
test suite)
Ignoring request to alter found versions of bug #1010120 to the same values
previously set
> fixed 1010120 0.16.0-6
Bug #1010120 [src:thrift] thrift: FTBFS in bullseye (expired certificates in
test suite)
Marked as fixed in versions thrift/0.16.0-6.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1010120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1010120: thrift: FTBFS in bullseye (expired certificates in test suite)
reopen 1010120 found 1010120 0.13.0-6 found 1010120 0.16.0-3 fixed 1010120 0.16.0-6 thanks (This is to prevent the bug being archived prematurely)
Bug#1007984: marked as done (netpbm-free: uncoordinated transition, consider switching to libnetpbm-dev)
Your message dated Tue, 10 Jan 2023 18:00:48 +
with message-id
and subject line Bug#1007984: fixed in netpbm-free 2:10.98.00-1
has caused the Debian Bug report #1007984,
regarding netpbm-free: uncoordinated transition, consider switching to
libnetpbm-dev
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1007984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netpbm-free
Version: 2:10.7.00-1
Severity: important
X-Debbugs-Cc: sramac...@debian.org, ti...@debian.org
Hi Andreas
the upload of netpbm-free 2:10.97.00-1 started an uncoordinated
transition from libnetpbm{9,10} to libnetpbm11. But it also requires
all reverse dependencies to update their build dependencies to
libnetpbm11-dev. Please consider moving to an unversioned -dev package,
i.e., libnetpbm-dev to avoid that in the feature.
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: netpbm-free
Source-Version: 2:10.98.00-1
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
netpbm-free, 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 1007...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated netpbm-free 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: Thu, 26 May 2022 07:29:29 +0200
Source: netpbm-free
Binary: libnetpbm-dev libnetpbm11 libnetpbm11-dbgsym netpbm
Architecture: source amd64
Version: 2:10.98.00-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers
Changed-By: Andreas Tille
Description:
libnetpbm-dev - Graphics conversion tools development libraries and header
files
libnetpbm11 - Graphics conversion tools shared libraries
netpbm - Graphics conversion tools between image formats
Closes: 360255 733464 789874 914850 1007984
Changes:
netpbm-free (2:10.98.00-1) unstable; urgency=medium
.
* Team upload.
* Remove outdaded debian/README* files
* Unversioned development package (Provides: libnetpbm9-dev, libnetpbm10-dev)
Closes: #1007984
* Close other bugs which are not valid in this version any more
Closes: #914850, #360255, #733464, #789874
* Review d/copyright
* Lintian-overrides for false positive
Checksums-Sha1:
512ad8047dc13ddad63c52b42707d0b41d4b01b4 2296 netpbm-free_10.98.00-1.dsc
5b27ba4caf925c83ee33b0f6fe0cd80c2369c021 2139404
netpbm-free_10.98.00.orig.tar.xz
20d922bd4687907e6086cc9bc5962327dca3a6e4 1547924
netpbm-free_10.98.00-1.debian.tar.xz
9ebce41f4836bcfbb397ba10c0a17e54bcca291e 212504
libnetpbm-dev_10.98.00-1_amd64.deb
1c3488c973ed09c7e624aa95a0bef5b058c4f118 281056
libnetpbm11-dbgsym_10.98.00-1_amd64.deb
d73eec4034e892baea26a31b4a13d36a4fdac442 176040
libnetpbm11_10.98.00-1_amd64.deb
63ea73325b36a0b7395116301a2d8d0701a52f86 9785
netpbm-free_10.98.00-1_amd64.buildinfo
7fcd2f92fc7291549acefb57a0cc9b96c1783541 2002572 netpbm_10.98.00-1_amd64.deb
Checksums-Sha256:
005762b193ff1dec79834dc99978b3460e4d2e9ce48403b8ea4f57e1a925c042 2296
netpbm-free_10.98.00-1.dsc
a941b6f52d1832afe23bf5f7137d44d739edafdfd72c66aa3dbfc37cc9a0ec67 2139404
netpbm-free_10.98.00.orig.tar.xz
ae0ae8389931034add78868124f630bfa38d306a3a7ead7f5260848e9d12d046 1547924
netpbm-free_10.98.00-1.debian.tar.xz
471795d72b94df71d4a75552efe96d01adef191f46015cfad334891a2ad20669 212504
libnetpbm-dev_10.98.00-1_amd64.deb
49eb94516c7d9addb230101d4a284dbd97818889f22cf033f6b4f63dd3f7fc08 281056
libnetpbm11-dbgsym_10.98.00-1_amd64.deb
3b90e8e16dc0c5d61e37b617be81449b34b5bf0a9a648e82f3c333b3a29241bb 176040
libnetpbm11_10.98.00-1_amd64.deb
210fe6471b9aa68d81a9e5ee7647349c1e48e9ba7d212f9da1677080b8556556 9785
netpbm-free_10.98.00-1_amd64.buildinfo
7e3ef9f6e2a41fc7fe163313befa12cd065802af030b52b2f9b7492e95ce6f0f 2002572
netpbm_10.98.00-1_amd64.deb
Files:
4c7ffba19e9698a2ba622f74b65f9000 2296 graphics optional
netpbm-free_10.98.00-1.dsc
c303309d5b2095c06797c9de1618c5c3 2139404 graphics optional
netpbm-free_10.98.00.orig.tar.xz
ef9810616b10d9c15a1916d7f2aef3d1 1
Bug#1016344: marked as done (siscone: FTBFS: make[2]: *** [Makefile:30: refman.dvi] Error 2)
Your message dated Tue, 10 Jan 2023 17:51:28 + with message-id and subject line Bug#1016344: fixed in siscone 3.0.5-2 has caused the Debian Bug report #1016344, regarding siscone: FTBFS: make[2]: *** [Makefile:30: refman.dvi] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1016344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016344 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: siscone Version: 3.0.5-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220728 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/doc/devel/latex' > Makefile:41: warning: overriding recipe for target 'refman.ps' > Makefile:18: warning: ignoring old recipe for target 'refman.ps' > Makefile:44: warning: overriding recipe for target 'refman.pdf' > Makefile:21: warning: ignoring old recipe for target 'refman.pdf' > make[2]: Circular refman.ps <- refman.ps dependency dropped. > rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out *.brf *.blg *.bbl > refman.pdf > echo "Running latex..." > Running latex... > latex refman.tex > This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Debian) > (preloaded format=latex) > restricted \write18 enabled. > entering extended mode > (./refman.tex > LaTeX2e <2022-06-01> patch level 5 > L3 programming layer <2022-07-15> > (/usr/share/texlive/texmf-dist/tex/latex/base/book.cls > Document Class: book 2021/10/04 v1.4n Standard LaTeX document class > (/usr/share/texlive/texmf-dist/tex/latex/base/bk10.clo)) > (/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty) > (/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty > (/usr/share/texlive/texmf-dist/tex/latex/tools/array-2016-10-06.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/base/fixltx2e.sty > > Package fixltx2e Warning: fixltx2e is not required with releases after 2015 > (fixltx2e)All fixes are now in the LaTeX kernel. > (fixltx2e)See the latexrelease package for details. > > ) (./doxygen.sty (/usr/share/texlive/texmf-dist/tex/latex/base/alltt.sty) > (/usr/share/texlive/texmf-dist/tex/latex/tools/calc.sty) > (/usr/share/texlive/texmf-dist/tex/latex/float/float.sty) > (/usr/share/texlive/texmf-dist/tex/latex/tools/verbatim.sty) > (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg) > (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/dvips.def) > (/usr/share/texlive/texmf-dist/tex/latex/colortbl/colortbl.sty) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/mathcolor.ltx)) > (./longtable_doxygen.sty) (./tabu_doxygen.sty > (/usr/share/texlive/texmf-dist/tex/latex/varwidth/varwidth.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/fancyvrb/fancyvrb.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/tools/tabularx.sty) > (/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty) > (/usr/share/texlive/texmf-dist/tex/latex/multirow/multirow.sty) > (/usr/share/texlive/texmf-dist/tex/latex/hanging/hanging.sty) > (/usr/share/texlive/texmf-dist/tex/generic/iftex/ifpdf.sty > (/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/adjustbox/adjustbox.sty > (/usr/share/texlive/texmf-dist/tex/latex/xkeyval/xkeyval.sty > (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkeyval.tex > (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkvutils.tex))) > (/usr/share/texlive/texmf-dist/tex/latex/adjustbox/adjcalc.sty) > (/usr/share/texlive/texmf-dist/tex/latex/adjustbox/trimclip.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty) > (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg))) > (/usr/share/texlive/texmf-dist/tex/latex/collectbox/collectbox.sty) > (/usr/share/texlive/texmf-dist/tex/latex/adjustbox/tc-dvips.def)) > (/usr/share/texlive/texmf-dist/tex/latex/ifoddpage/ifoddpage.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty > (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/stackengine/stackengine.sty > (/usr/share/texlive/texmf-dist/tex/latex/etoolbox/etoolbox.sty) > (/usr/share/texlive/texmf-dist/tex/generic/listofitems/listofitems.sty > (/usr/share/texlive/texmf-d
Bug#1028192: Needs to block python3-nbxmpp
In that case python3-nbxmpp 4.x must not migrate either, because it breaks Gajim 1.5.x. I'm not sure what's the proper way to achieve that, should I file another bug or is there some "blocks" mechanism in the BTS?
Bug#1027612: python-envisage: FTBFS: AssertionError: 0 != 3
On Tue, 10 Jan 2023, Andreas Tille wrote: Hi, I've updated Git to latest upstream version which does not show the reported error any more. However, there are two other issues I seem to need help for. I've worked around the initial issue[1] FileNotFoundError: [Errno 2] No such file or directory: 'python' with a patch[2] but this finally leads to a different error[3] subprocess.CalledProcessError: Command '['python3', 'setup.py', 'bdist_egg', '--dist-dir', '/tmp/tmp14hpgj33']' returned non-zero exit status 1. Any help would be welcome Andreas. [1] https://salsa.debian.org/python-team/packages/python-envisage/-/jobs/3774020 [2] https://salsa.debian.org/python-team/packages/python-envisage/-/blob/master/debian/patches/python3.patch [3] https://salsa.debian.org/python-team/packages/python-envisage/-/jobs/3774219 I'm looking into this. It appears that something is going horribly wrong with the test egg generation (which is now being done upstream automatically). Scott
Processed: arandr: diff for NMU version 0.1.10-1.2
Processing control commands: > tag 1028138 + pending Bug #1028138 [arandr] arandr: no longer starts: module 'inspect' has no attribute 'getargspec' Added tag(s) pending. > tag 1021216 + pending Bug #1021216 [src:arandr] FTBS: ModuleNotFoundError: No module named 'docutils' Added tag(s) pending. > forwarded -1 https://gitlab.com/arandr/arandr/-/merge_requests/12 Bug #1028406 [arandr] arandr: diff for NMU version 0.1.10-1.2 Set Bug forwarded-to-address to 'https://gitlab.com/arandr/arandr/-/merge_requests/12'. -- 1021216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021216 1028138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028138 1028406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028406 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028346: marked as done (php-horde-imap-client: fails on login: Return value of Horde_Imap_Client_Tokenize::current() must be an instance of mixed,)
Your message dated Tue, 10 Jan 2023 16:50:51 +
with message-id
and subject line Bug#1028346: fixed in php-horde-imap-client 2.30.6-2
has caused the Debian Bug report #1028346,
regarding php-horde-imap-client: fails on login: Return value of
Horde_Imap_Client_Tokenize::current() must be an instance of mixed,
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.)
--
1028346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028346
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-horde-imap-client
Version: 2.30.6-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
With php7.4-fpm, after updating to 2.30.6-1 users are unable to login.
Login attempts generate the following error:
HORDE: [imp] TypeError: Return value of Horde_Imap_Client_Tokenize::current()
must be an instance of mixed, string returned in
/usr/share/php/Horde/Imap/Client/Tokenize.php:225
HORDE: Stack trace:
HORDE: #0 /usr/share/php/Horde/Imap/Client/Interaction/Server.php(102):
Horde_Imap_Client_Tokenize->current()
HORDE: #1 /usr/share/php/Horde/Imap/Client/Interaction/Server.php(84):
Horde_Imap_Client_Interaction_Server->__construct()
HORDE: #2 /usr/share/php/Horde/Imap/Client/Socket.php(4542):
Horde_Imap_Client_Interaction_Server::create()
HORDE: #3 /usr/share/php/Horde/Imap/Client/Socket.php(621):
Horde_Imap_Client_Socket->_getLine()
HORDE: #4 /usr/share/php/Horde/Imap/Client/Socket.php(375):
Horde_Imap_Client_Socket->_connect()
HORDE: #5 /usr/share/php/Horde/Imap/Client/Base.php(839):
Horde_Imap_Client_Socket->_login()
HORDE: #6 /usr/share/horde/imp/lib/Imap.php(718):
Horde_Imap_Client_Base->login()
HORDE: #7 /usr/share/horde/imp/lib/Auth.php(86): IMP_Imap->__call()
HORDE: #8 /usr/share/horde/imp/lib/Application.php(370):
IMP_Auth::authenticate()
HORDE: #9 /usr/share/php/Horde/Registry.php(1197):
IMP_Application->authAuthenticate()
HORDE: #10 /usr/share/php/Horde/Core/Auth/Application.php(170):
Horde_Registry->callAppMethod()
HORDE: #11 /usr/share/php/Horde/Auth/Base.php(161):
Horde_Core_Auth_Application->_authenticate()
HORDE: #12 /usr/share/php/Horde/Core/Auth/Application.php(141):
Horde_Auth_Base->authenticate()
HORDE: #13 /usr/share/php/Horde/Core/Auth/Application.php(138):
Horde_Core_Auth_Application->authenticate()
HORDE: #14 /usr/share/horde/login.php(155):
Horde_Core_Auth_Application->authenticate()
HORDE: #15 {main} [pid 1480064 on line 74 of
"/usr/share/php/Horde/ErrorHandler.php"]
I reverted php-horde-imap-client back to 2.30.1-4 and the problem went away.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-6-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.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 php-horde-imap-client depends on:
ii libapache2-mod-php8.1 [php-json] 8.1.12-1+b1
hi php-common2:76
ii php-horde-exception 2.0.8-9
ii php-horde-mail2.6.6-4
ii php-horde-mime2.11.2-1
ii php-horde-secret 2.0.6-9
ii php-horde-socket-client 2.1.4-1
ii php-horde-stream 1.6.3-10
ii php-horde-stream-filter 2.0.5-1
ii php-horde-translation 2.2.2-7
ii php-horde-util2.5.12-1
ii php-json 2:8.1+92+nmu1
ii php7.4-json [php-json]7.4.33-1+deb11u1
ii php8.1-cli [php-json] 8.1.12-1+b1
ii php8.1-fpm [php-json] 8.1.12-1+b1
ii php8.2-cli [php-json] 8.2.1-1
Versions of packages php-horde-imap-client recommends:
ii php-horde-cache 2.5.5-10
ii php-horde-compress-fast 1.1.1-10
ii php-horde-crypt-blowfish1.1.4-1
hi php-horde-db2.4.1-1
ii php-horde-hashtable 1.2.6-11
pn php-horde-mongo
ii php-horde-pack 1.0.7-7
pn php-horde-stringprep
ii php-horde-support 2.2.2-1
ii php-horde-test 2.6.4+debian0-7
pn php-intl
ii php-mbstring2:8.1+92+nmu1
ii php7.4-mbstring [php-mbstring] 7.4.33-1+deb11u1
ii php8.1-mbstring [php-mbstring] 8.1.12-1+b1
php-horde-imap-client suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: php
Bug#1028291: marked as done (dipy FTBFS with numpy 1.24)
Your message dated Tue, 10 Jan 2023 17:42:47 +0100
with message-id
and subject line Re: Bug#1028291: dipy FTBFS with numpy 1.24
has caused the Debian Bug report #1028291,
regarding dipy FTBFS with numpy 1.24
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.)
--
1028291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dipy
Version: 1.5.0-4
Severity: serious
Tags: ftbfs patch
Forwarded: https://github.com/dipy/dipy/pull/2700
https://buildd.debian.org/status/fetch.php?pkg=dipy&arch=amd64&ver=1.5.0-5&stamp=1673232202&raw=0
...
=== FAILURES ===
__ test_optional_str ___
def test_optional_str():
# Test optional and variable str argument exists but does not have a
value
sys.argv = [sys.argv[0]]
inputs = ['--optional_str_1']
sys.argv.extend(inputs)
parser = IntrospectiveArgumentParser()
dummy_flow = DummyWorkflowOptionalStr()
parser.add_workflow(dummy_flow)
args = parser.get_flow_args()
all_keys = ['optional_str_1']
all_results = [[]]
# Test if types and order are respected
for k, v in zip(all_keys, all_results):
npt.assert_equal(args[k], v)
# Test if **args really fits dummy_flow's arguments
return_values = dummy_flow.run(**args)
> npt.assert_array_equal(return_values, all_results + ['default'])
dipy/workflows/tests/test_iap.py:110:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
args = (, ([], 'default'), [[], 'default'])
kwds = {'err_msg': '', 'header': 'Arrays are not equal', 'strict': False,
'verbose': True}
@wraps(func)
def inner(*args, **kwds):
with self._recreate_cm():
> return func(*args, **kwds)
E ValueError: setting an array element with a sequence. The requested
array has an inhomogeneous shape after 1 dimensions. The detected shape was
(2,) + inhomogeneous part.
/usr/lib/python3.10/contextlib.py:79: ValueError
...
=== short test summary info
FAILED dipy/workflows/tests/test_iap.py::test_optional_str - ValueError: sett...
== 1 failed, 764 passed, 94 skipped, 37 warnings in 804.92s (0:13:24) ==
make[1]: *** [debian/rules:59: override_dh_auto_install] Error 1
--- End Message ---
--- Begin Message ---
Hi Adrian,
this bug is fixed in version 1.5.0-6.
Kind regards
Andreas.
--
http://fam-tille.de--- End Message ---
Bug#1027849: zeroc-ice: diff for NMU version 3.7.8-1.1
Hi Adrian, Seems didn't work, I will look into it. Cheers, Jose On Mon, Jan 9, 2023 at 10:21 PM Adrian Bunk wrote: > Control: tags 1027849 + pending > > Dear maintainer, > > I've prepared an NMU for zeroc-ice (versioned as 3.7.8-1.1) and uploaded > it to DELAYED/2. Please feel free to tell me if I should cancel it. > > cu > Adrian > -- José Gutiérrez de la Concha ZeroC, Inc.
Bug#1028405: ansible-core: autopkgtest regresses with new python3-defaults (python 3.11)
Package: ansible-core
Version: 2.14.1-1
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar ubuntu-patch
Hi Lee,
The ansible-core autopkgtests fail now that /usr/bin/python3 is python 3.11:
[...]
autopkgtest [08:17:06]: test unit: [---
FATAL: Running under Python version 3.11 instead of 3.10.
FATAL: Command "/usr/bin/env
ANSIBLE_TEST_CONTENT_ROOT=/tmp/autopkgtest-lxc.8ik95lf6/downtmp/build.jHa/src
PYTHONPATH=/tmp/ansible-test-iin32i73 /usr/bin/python3 /usr/bin/ansible-test
units --containers '{}' --truncate 0 --color no --host-path
test/results/.tmp/host-n2w5rzai --metadata
test/results/.tmp/metadata-_yj0am3d.json" returned exit status 1.
autopkgtest [08:17:07]: test unit: ---]
[...]
(https://ci.debian.net/data/autopkgtest/unstable/amd64/a/ansible-core/29976247/log.gz)
This comes down to a hard-coded "--python 3.11" option in the autopkgtest
which seems superfluous.
I have uploaded the attached patch to Ubuntu to unblock the python3-defaults
transition there.
Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru ansible-core-2.14.1/debian/tests/unit
ansible-core-2.14.1/debian/tests/unit
--- ansible-core-2.14.1/debian/tests/unit 2022-11-27 23:43:42.0
-0800
+++ ansible-core-2.14.1/debian/tests/unit 2023-01-09 21:15:02.0
-0800
@@ -2,5 +2,4 @@
/usr/bin/ansible-test units \
--python-interpreter /usr/bin/python3 \
- --python 3.10 \
--local
Processed: retitle 1028350 to davmail: autopkgtest regression on arm64, armhf and ppc64el: libjnidispatch.so not found in resource path
Processing commands for cont...@bugs.debian.org: > retitle 1028350 davmail: autopkgtest regression on arm64, armhf and ppc64el: > libjnidispatch.so not found in resource path Bug #1028350 [src:davmail] davmail: autopkgtest regression on arm64, armhf and ppc64el: Unable to store settings: /etc/davmail.properties (Permission denied) Changed Bug title to 'davmail: autopkgtest regression on arm64, armhf and ppc64el: libjnidispatch.so not found in resource path' from 'davmail: autopkgtest regression on arm64, armhf and ppc64el: Unable to store settings: /etc/davmail.properties (Permission denied)'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1028350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909750: RFC: fontconfig 2.14.1-1 experimental branch on salsa.debian.org
On Fri, 6 Jan 2023 16:14:33 +0100 Andreas Henriksson wrote: Also general feedback if it's suitable to upload the experimental package to unstable this close to the freeze (which I feel will need to happen ASAP or wait until after the release). With my piuparts hat on, I'd really like to see this change in sid. But unfortunately I'm a -ENOTIME for testing it. Andreas
Bug#1026490: marked as done (sssd: FTBFS: make[1]: *** [debian/rules:102: override_dh_missing] Error 25)
Your message dated Tue, 10 Jan 2023 15:33:03 + with message-id and subject line Bug#1026490: fixed in sssd 2.8.1-2 has caused the Debian Bug report #1026490, regarding sssd: FTBFS: make[1]: *** [debian/rules:102: override_dh_missing] Error 25 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.) -- 1026490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026490 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sssd Version: 2.8.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_missing --fail-missing > dh_missing: warning: > usr/lib/python3/dist-packages/SSSDConfig-2.8.1.egg-info/PKG-INFO exists in > debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3/dist-packages/SSSDConfig-2.8.1.egg-info/dependency_links.txt > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/python3/dist-packages/SSSDConfig-2.8.1.egg-info/top_level.txt exists > in debian/tmp but is not installed to anywhere > dh_missing: error: missing files, aborting > The following debhelper tools have reported what they installed (with > files per package) >* dh_install: libipa-hbac-dev (3), libipa-hbac0 (2), libnss-sss (1), > libpam-sss (4), libsss-certmap-dev (3), libsss-certmap0 (3), libsss-idmap-dev > (3), libsss-idmap0 (2), libsss-nss-idmap-dev (3), libsss-nss-idmap0 (2), > libsss-simpleifp-dev (4), libsss-simpleifp0 (2), libsss-sudo (1), > python3-libipa-hbac (1), python3-libsss-nss-idmap (1), python3-sss (5), sssd > (0), sssd-ad (3), sssd-ad-common (3), sssd-common (96), sssd-dbus (5), > sssd-idp (4), sssd-ipa (3), sssd-kcm (6), sssd-krb5 (4), sssd-krb5-common > (2), sssd-ldap (3), sssd-proxy (2), sssd-tools (14) >* dh_installdocs: libipa-hbac-dev (0), libipa-hbac0 (0), libnss-sss > (0), libpam-sss (0), libsss-certmap-dev (0), libsss-certmap0 (0), > libsss-idmap-dev (0), libsss-idmap0 (0), libsss-nss-idmap-dev (0), > libsss-nss-idmap0 (0), libsss-simpleifp-dev (0), libsss-simpleifp0 (0), > libsss-sudo (0), python3-libipa-hbac (0), python3-libsss-nss-idmap (0), > python3-sss (0), sssd (0), sssd-ad (0), sssd-ad-common (0), sssd-common (1), > sssd-dbus (0), sssd-idp (0), sssd-ipa (0), sssd-kcm (0), sssd-krb5 (0), > sssd-krb5-common (0), sssd-ldap (0), sssd-proxy (0), sssd-tools (0) >* dh_installexamples: libipa-hbac-dev (0), libipa-hbac0 (0), > libnss-sss (0), libpam-sss (0), libsss-certmap-dev (0), libsss-certmap0 (0), > libsss-idmap-dev (0), libsss-idmap0 (0), libsss-nss-idmap-dev (0), > libsss-nss-idmap0 (0), libsss-simpleifp-dev (0), libsss-simpleifp0 (0), > libsss-sudo (0), python3-libipa-hbac (0), python3-libsss-nss-idmap (0), > python3-sss (0), sssd (0), sssd-ad (0), sssd-ad-common (0), sssd-common (1), > sssd-dbus (0), sssd-idp (0), sssd-ipa (0), sssd-kcm (0), sssd-krb5 (0), > sssd-krb5-common (0), sssd-ldap (0), sssd-proxy (0), sssd-tools (0) > If the missing files are installed by another tool, please file a bug > against it. > When filing the report, if the tool is not part of debhelper itself, > please reference the > "Logging helpers and dh_missing" section from the "PROGRAMMING" guide > for debhelper (10.6.3+). > (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz) > Be sure to test with dpkg-buildpackage -A/-B as the results may vary > when only a subset is built > If the omission is intentional or no other helper can take care of this > consider adding the > paths to debian/not-installed. > make[1]: *** [debian/rules:102: override_dh_missing] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/12/20/sssd_2.8.1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221220&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#aff
Bug#1011881: marked as done (php-dapphp-radius: FTBFS: tests fail)
Your message dated Tue, 10 Jan 2023 16:20:51 +0100 with message-id <7b73c1c0-e80f-f627-3379-1eb7f72eb...@debian.org> and subject line fixed 1011881 2.5.8-2 has caused the Debian Bug report #1011881, regarding php-dapphp-radius: FTBFS: tests fail 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.) -- 1011881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011881 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-dapphp-radius Version: 2.5.8-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > make[1]: pyversions: No such file or directory > py3versions: no X-Python3-Version in control file, using supported versions > phpunit --include-path lib > PHPUnit 9.5.16 by Sebastian Bergmann and contributors. > > F.F...F.S 13 / 13 > (100%) > > Time: 00:00.008, Memory: 6.00 MB > > There were 3 failures: > > 1) ClientTest::testCryptCHAPMSv1 > Failed asserting that two strings are equal. > --- Expected > +++ Actual > @@ @@ > -'5f169b7d8176516f8092bce99008e097febfed2f043ec04e' > +'' > > /<>/tests/ClientTest.php:107 > > 2) ClientTest::testCryptCHAPMSv2 > Failed asserting that two strings are equal. > --- Expected > +++ Actual > @@ @@ > -'a3d12ce2f52d13fe04421205a2ce17b0e559ea8a9e594c1c' > +'' > > /<>/tests/ClientTest.php:145 > > 3) ClientTest::testMsChapV1Packet > Failed asserting that two strings are equal. > --- Expected > +++ Actual > @@ @@ > -'01870082093e4ad125399f8ac4ba6b00ab69a04001066e656d6f04067f0105060014501248a3704ac91e8191497a1f3f213eb3381a1001370b0a740c7921e45e91391a3a0137013400014521bd46aebfd2ab3ec21dd6e6bbfa2e4ff325eab720fe37' > +'0187006a093e4ad125399f8ac4ba6b00ab69a04001066e656d6f04067f01050600145012467e2ad6e452c8bfbb8ca80ff167196e1a1001370b0a740c7921e45e91391a220137011c0001' > > /<>/tests/ClientTest.php:246 > > FAILURES! > Tests: 13, Assertions: 28, Failures: 3, Skipped: 1. > make[1]: *** [debian/rules:21: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/05/25/php-dapphp-radius_2.5.8-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220525&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- fixed 1011881 2.5.8-2--- End Message ---
Processed: fixed 1011881 2.5.8-2
Processing commands for cont...@bugs.debian.org: > fixed 1011881 2.5.8-2 Bug #1011881 [src:php-dapphp-radius] php-dapphp-radius: FTBFS: tests fail Marked as fixed in versions php-dapphp-radius/2.5.8-2. > End of message, stopping processing here. Please contact me if you need assistance. -- 1011881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011881 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027908: golang-github-jedib0t-go-pretty: FTBFS in bookworm (undeclared build-dependency on tzdata)
notfixed 1027908 6.4.4-1 found 1027908 6.4.4-1 thanks Quoting Debian Policy 4.2. If build-time dependencies are specified, it must be possible to build the package and produce working binaries on a system with only essential and build-essential packages installed and also those required to satisfy the build-time relationships (including any implied relationships). In case it was not clear enough: tzdata is not build-essential, that's why it needs to be in the build-depends. Thanks.
Processed: golang-github-jedib0t-go-pretty: FTBFS in bookworm (undeclared build-dependency on tzdata)
Processing commands for cont...@bugs.debian.org:
> notfixed 1027908 6.4.4-1
Bug #1027908 {Done: Francisco Vilmar Cardoso Ruviaro }
[src:golang-github-jedib0t-go-pretty] golang-github-jedib0t-go-pretty: FTBFS in
bookworm (undeclared build-dependency on tzdata)
The source 'golang-github-jedib0t-go-pretty' and version '6.4.4-1' do not
appear to match any binary packages
No longer marked as fixed in versions golang-github-jedib0t-go-pretty/6.4.4-1.
> found 1027908 6.4.4-1
Bug #1027908 {Done: Francisco Vilmar Cardoso Ruviaro }
[src:golang-github-jedib0t-go-pretty] golang-github-jedib0t-go-pretty: FTBFS in
bookworm (undeclared build-dependency on tzdata)
The source 'golang-github-jedib0t-go-pretty' and version '6.4.4-1' do not
appear to match any binary packages
Marked as found in versions golang-github-jedib0t-go-pretty/6.4.4-1 and
reopened.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1027908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1026088: marked as done (rdma-core: add mips64* to COHERENT_DMA_ARCHS)
Your message dated Tue, 10 Jan 2023 14:57:36 + with message-id and subject line Bug#1026088: fixed in rdma-core 44.0-2 has caused the Debian Bug report #1026088, regarding rdma-core: add mips64* to COHERENT_DMA_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.) -- 1026088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rdma-core Version: 33.2-1 Severity: serious Tags: ftbfs Can you help to add the fellow 4 ports mips64 mips64el mips64r6 mips64r6el to the list of COHERENT_DMA_ARCHS in debian/rules ? -- YunQiang Su --- End Message --- --- Begin Message --- Source: rdma-core Source-Version: 44.0-2 Done: Benjamin Drung We believe that the bug you reported is fixed in the latest version of rdma-core, 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 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Benjamin Drung (supplier of updated rdma-core 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: Tue, 10 Jan 2023 13:59:10 +0100 Source: rdma-core Built-For-Profiles: noudeb Architecture: source Version: 44.0-2 Distribution: unstable Urgency: medium Maintainer: Benjamin Drung Changed-By: Benjamin Drung Closes: 1026088 Changes: rdma-core (44.0-2) unstable; urgency=medium . * debian: Add 32-bit MIPS architectures to COHERENT_DMA_ARCHS and inverse the list to NON_COHERENT_DMA_ARCHS (Closes: #1026088) Checksums-Sha1: 232fae1a4ee3aee85dbb2ad7c86d53a5f8b6f627 3190 rdma-core_44.0-2.dsc f9e399ee6eb7bec592e295abfb5339e589f0b87f 23768 rdma-core_44.0-2.debian.tar.xz 963bd8894e7336270161d07503b7f1a9570dee9a 9495 rdma-core_44.0-2_source.buildinfo Checksums-Sha256: 9ca4e7de1559d4218789590fd62f5fb0b2307ee93c2b8975af140fb5d773d33b 3190 rdma-core_44.0-2.dsc 9dc027def281b6809562f296dea05693b79a0ef784eb2795f2154c6077f4a73d 23768 rdma-core_44.0-2.debian.tar.xz 0811b7577237970a4cea573046627de84f5fb0d501279881c72953f83e8f177b 9495 rdma-core_44.0-2_source.buildinfo Files: 3910186beb6b3ad04e44d3e1f5ccda9c 3190 net optional rdma-core_44.0-2.dsc 962a77cfe433491c3088b6883b5bc3c8 23768 net optional rdma-core_44.0-2.debian.tar.xz e4f8836bc92c819ba11ce07f8f3c8fd4 9495 net optional rdma-core_44.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmO9dIQACgkQFZ61xO/I d0yRtA/8DENPch6VG1bVkTKeQKWWrNQT3kIgrRtDADEx1rWhyAjQ7oP64BLxhUUL Ht+xXi9L1j44V8HDMk4fZx4zfXvuWnBHMmeUp0xqs3zBsuKWXkb0yQ5F7f/cuVFA yA2nEnKt2WM+biFbZIaA9VlGNzD1lKLt9BKoIr3UG/ZjCTOH+dNYkQ4rt4JLYHFT PlVNwg2D4D4Czvnil8bi2i0cPWsFhNL0v3+VTcU0HsyBOlrvZ9o7ks4Ek/IO2U8A uWYiCq1rLyPvNm6yKKYS80O7E5tkOh6EbQBwb7mwD4vPW+rhqPkEZUMk0IPsxgzJ mG9FxjYBUmahbKan/+drVB72C2n7cEofYSNy48Ug43zAco9Pan53Vk9YcWVigjsw rqTAwUIlOtsAHZPQwPH+18NDDLN0yuaXeOt6IJw2vg0gPdEabQxhkmlTwyYQeLDp s6GhiY4OYwzPJ4+et91IE0cO8NroZA5eKLRFoN/N6VumWp9tglbJsEJeb28jviZX e1/NbqUY8jKI8YQJyDIfjj+wy/WQ8zPYTV4rLni+GjgpytErUkKBH5SmfGBta+2L EaTx/pvMAAA5XKKHKomKl+xipJbOo4YNbwJ4cz5RwosoJEzUpCMa6R+SOTw1Ib+T jE1GbAWT3gN9TogDG5sp7TNWuxk/QhUiwpw9tbdx1o+P1SzD/NU= =zF3J -END PGP SIGNATURE End Message ---
Bug#1027908: marked as done (golang-github-jedib0t-go-pretty: FTBFS in bookworm (undeclared build-dependency on tzdata))
Your message dated Tue, 10 Jan 2023 14:53:31 + with message-id and subject line Bug#1027908: fixed in golang-github-jedib0t-go-pretty 6.4.4-1 has caused the Debian Bug report #1027908, regarding golang-github-jedib0t-go-pretty: FTBFS in bookworm (undeclared build-dependency on tzdata) 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.) -- 1027908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:golang-github-jedib0t-go-pretty Version: 6.3.3-1 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bookworm, your package failed to build: [...] debian/rules binary-indep dh binary-indep --builddirectory=_build --buildsystem=golang --with=golang dh_update_autotools_config -i -O--builddirectory=_build -O--buildsystem=golang dh_autoreconf -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_configure -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_build -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_build: warning: github.com/jedib0t/go-pretty contains no non-test Go files, removing it from build cd _build && go install -trimpath -v -p 1 github.com/jedib0t/go-pretty/list github.com/jedib0t/go-pretty/progress github.com/jedib0t/go-pretty/table github.com/jedib0t/go-pretty/text internal/goarch internal/unsafeheader internal/abi internal/cpu internal/bytealg internal/goexperiment internal/goos runtime/internal/atomic runtime/internal/math runtime/internal/sys runtime/internal/syscall runtime internal/reflectlite errors internal/itoa math/bits math unicode/utf8 strconv internal/race sync/atomic sync unicode reflect sort internal/fmtsort io internal/oserror syscall internal/syscall/unix time internal/poll internal/syscall/execenv internal/testlog path io/fs os fmt bytes encoding encoding/binary encoding/base64 strings unicode/utf16 encoding/json github.com/rivo/uniseg regexp/syntax regexp github.com/mattn/go-runewidth github.com/jedib0t/go-pretty/text html github.com/jedib0t/go-pretty/list github.com/jedib0t/go-pretty/progress github.com/jedib0t/go-pretty/table dh_auto_test -i -O--builddirectory=_build -O--buildsystem=golang cd _build && go test -vet=off -v -p 1 github.com/jedib0t/go-pretty github.com/jedib0t/go-pretty/list github.com/jedib0t/go-pretty/progress github.com/jedib0t/go-pretty/table github.com/jedib0t/go-pretty/text testing: warning: no tests to run PASS ok github.com/jedib0t/go-pretty0.002s [no tests to run] === RUN TestNewWriter --- PASS: TestNewWriter (0.00s) === RUN TestList_AppendItem --- PASS: TestList_AppendItem (0.00s) === RUN TestList_AppendItems --- PASS: TestList_AppendItems (0.00s) === RUN TestList_Indent --- PASS: TestList_Indent (0.00s) === RUN TestList_Length --- PASS: TestList_Length (0.00s) === RUN TestList_Reset --- PASS: TestList_Reset (0.00s) === RUN TestList_SetHTMLCSSClass --- PASS: TestList_SetHTMLCSSClass (0.00s) === RUN TestList_SetOutputMirror --- PASS: TestList_SetOutputMirror (0.00s) === RUN TestList_SetStyle --- PASS: TestList_SetStyle (0.00s) === RUN TestList_UnIndent --- PASS: TestList_UnIndent (0.00s) === RUN TestList_RenderHTML --- PASS: TestList_RenderHTML (0.00s) === RUN TestList_RenderHTML_Complex --- PASS: TestList_RenderHTML_Complex (0.00s) === RUN TestList_RenderMarkdown --- PASS: TestList_RenderMarkdown (0.00s) === RUN TestList_Render --- PASS: TestList_Render (0.00s) === RUN TestList_Render_Complex --- PASS: TestList_Render_Complex (0.00s) === RUN TestList_Render_Connected --- PASS: TestList_Render_Connected (0.00s) === RUN TestList_Render_MultiLine --- PASS: TestList_Render_MultiLine (0.00s) === RUN TestList_Render_Styles --- PASS: TestList_Render_Styles (0.00s) === RUN Example --- PASS: Example (0.00s) PASS ok github.com/jedib0t/go-pretty/list 0.008s === RUN TestIndeterminateIndicatorDominoes --- PASS: TestIndeterminateIndicatorDominoes (0.31s) === RUN TestIndeterminateIndicatorMovingBackAndForth --- PASS: TestIndeterminateIndicatorMovingBackAndForth (0.29s) === RUN Test_indeterminateIndicatorMovingBackAndForth1 --- PASS: Test_indeterminateIndicatorMovingBackAndForth1 (0.00s) === RUN Test_indeterminateIndicatorMovingBackAndForth2 --- PASS: Test_indeterminateIndicatorMovingBackAndForth2 (0.00s) === RUN Test_indeterminateIndicatorMovingBackAndForth3 --- PASS: Test_indeterminateIndicatorMovingBackAndForth3 (0.00s) === RUN
Bug#1028098: marked as done (dballe: binary-all FTBFS)
Your message dated Tue, 10 Jan 2023 14:47:32 + with message-id and subject line Bug#1028098: fixed in dballe 9.4-1 has caused the Debian Bug report #1028098, regarding dballe: binary-all FTBFS 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.) -- 1028098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dballe Version: 9.3-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=dballe&arch=all&ver=9.3-2&stamp=1672991515&raw=0 ... dh_missing -i -O-Smeson -O--parallel dh_missing: warning: usr/include/dballe/dballef.mod exists in debian/tmp but is not installed to anywhere dh_missing: error: missing files, aborting ... --- End Message --- --- Begin Message --- Source: dballe Source-Version: 9.4-1 Done: Enrico Zini We believe that the bug you reported is fixed in the latest version of dballe, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Enrico Zini (supplier of updated dballe 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: Tue, 10 Jan 2023 14:47:53 +0100 Source: dballe Architecture: source Version: 9.4-1 Distribution: unstable Urgency: medium Maintainer: Enrico Zini Changed-By: Enrico Zini Closes: 1028098 Changes: dballe (9.4-1) unstable; urgency=medium . * New upstream version, see NEWS.md for what's new. * Explicitly include dballef.mod in debian/libdballef-dev.install. Closes: #1028098 Checksums-Sha1: daedb56d757ecadcb63d3995e5f57d1defbb484a 2588 dballe_9.4-1.dsc bc29be8976bb90d67754e8b8f9cd02d432c24a1d 1049123 dballe_9.4.orig.tar.gz fff6692c8507b78a9496a44c18332ff1e79e1256 10940 dballe_9.4-1.debian.tar.xz a169ac83b90fe27b40b0c4fa5294f7a7d1da4635 5500 dballe_9.4-1_source.buildinfo Checksums-Sha256: 49fce58fc25b473bdbc64d7f81e1b502f9eefe5be7c76807769bf44bc9ec62a9 2588 dballe_9.4-1.dsc 43e009edd5646341e5d3eae432c40ad7af7479b0a936b1d7973a35a323a7b395 1049123 dballe_9.4.orig.tar.gz d9513e6544225c3a603acb45f7c369863ee5730311717422ffc0e76665fddc7b 10940 dballe_9.4-1.debian.tar.xz 29fa8bf4832c3a1d483b8ff270fe05ec85e14663cbcacb317c3b3d78a21b87a6 5500 dballe_9.4-1_source.buildinfo Files: a5709c89d8606d1ab61dec2b8360d185 2588 misc optional dballe_9.4-1.dsc f7fc226c438fb6e37810bd3b77f6e040 1049123 misc optional dballe_9.4.orig.tar.gz 76246d72048ccdb3395b6635375d3abc 10940 misc optional dballe_9.4-1.debian.tar.xz 1fc7212a3a36964c536d3656bf8a78ee 5500 misc optional dballe_9.4-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEEJJAhGtA2CH5tHZqS0P9Jy+P0+2gFAmO9bmESHGVucmljb0Bk ZWJpYW4ub3JnAAoJEND/Scvj9Pto3qwQAK/T6owoP2Pzys0sfNVyS9Y13foj2xWq FMxeEonrIJDJ0YrdIFljPOsLQwtBQv3bqsnkeNU8dPILmQE7arQWi4d2TthiMImy nt+tWzbXi8NRQj8AutvomRv8zKwIVCj7/8sp8ViKJ7NQCtqpsMB3C/hU3lZiBilT TC/9AWtk9iGVnVtPjVNWCi+dAfAhBdFHlbspc0hzKe+sZrcfdBWv5lPAocoSwndl hVJ7u5fTR+jU6rbuPFxsRhy7nE6S6V8Pek234sjvq52fcko7f/FvbSn3vH3SrTya OPEr+Gk4oRuK6bSB+NdiOKga3lF1hrIF33iSYU49QFM9NYsBG8He1LL6Y4ncl/4j uQNHpJiBhE5mU5W4oOJUG8ksgno7Cy7qZ7AFdbLN++Oxz80dV0qKtjL8aYzn9iJH +eH+oTGRW76fkhTtwCBITZXwcs5Pu3wNSYdzxbhUlwRLQJzjIY/7147YUAsGgNXi QG67+2O6hDJoBFektn8koViCjnw+tutFlvbfPPAuLWkwligUELKN9sVlKYf67imc Kd9m24dyI12bJQjKbXwj7sno+PE+oCQ/+byZPAxOaZz0P2+47pDevFCOf6OB7vc+ wJMTWiwiyo7hKkkrXXP7dalBRl/b2gZkUTMef1tsBlOZF/Yuo7I+9AdNsYxt9IXL 3mlO5/yujoXf =+Sr6 -END PGP SIGNATURE End Message ---
Bug#1026667: gensio: FTBFS: make: *** [debian/rules:19: binary] Error 25
Source: gensio
Version: 2.5.1-2
Followup-For: Bug #1026667
Dear Maintainer,
Please find a merge request on Debian Salsa at
https://salsa.debian.org/debian/gensio/-/merge_requests/2 that addresses this
build failure.
Two fixups were required:
1. A hardcoded reference[1] to Python3.10 was adjusted to permit any minor
version of Python3, allowing the build to succeed on Python3.11 as well (and
easing rollback, if the Debian project decides not to upgrade to Python3.11 for
the bookworm release)
2. An additional match-pattern[2] was added to the list of build artifacts
that are generated but not used during package installation (and should
therefore not be included in the distributed package)
The first change resolves the build error described in this bugreport, and the
second change resolves a subsequent build error ("dh_missing: warning:
usr/local/lib/python3.11/dist-packages/_pygensio.a exists in debian/tmp but is
not installed to anywhere "), which is visible in the build logs from a Debian
Salsa build[3].
Thanks!
James
[1] -
https://salsa.debian.org/jayaddison/gensio/-/commit/60c18fbe4ad7b29225e74131babe7d0b09fca0ab
[2] -
https://salsa.debian.org/jayaddison/gensio/-/commit/9498260bfceeb66f7147ba7327afdafba50768fd
[3] - https://salsa.debian.org/jayaddison/gensio/-/jobs/3773705
Bug#1027908: marked as pending in golang-github-jedib0t-go-pretty
Control: tag -1 pending Hello, Bug #1027908 in golang-github-jedib0t-go-pretty reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/golang-github-jedib0t-go-pretty/-/commit/70596ad1add7307c35869b5c3f024d85ca705f5f Finish changelog for 6.4.4-1 unstable upload (Closes: #1027908) (this message was generated automatically) -- Greetings https://bugs.debian.org/1027908
Processed: Bug#1027908 marked as pending in golang-github-jedib0t-go-pretty
Processing control commands: > tag -1 pending Bug #1027908 [src:golang-github-jedib0t-go-pretty] golang-github-jedib0t-go-pretty: FTBFS in bookworm (undeclared build-dependency on tzdata) Added tag(s) pending. -- 1027908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027612: python-envisage: FTBFS: AssertionError: 0 != 3
Hi, I've updated Git to latest upstream version which does not show the reported error any more. However, there are two other issues I seem to need help for. I've worked around the initial issue[1] FileNotFoundError: [Errno 2] No such file or directory: 'python' with a patch[2] but this finally leads to a different error[3] subprocess.CalledProcessError: Command '['python3', 'setup.py', 'bdist_egg', '--dist-dir', '/tmp/tmp14hpgj33']' returned non-zero exit status 1. Any help would be welcome Andreas. [1] https://salsa.debian.org/python-team/packages/python-envisage/-/jobs/3774020 [2] https://salsa.debian.org/python-team/packages/python-envisage/-/blob/master/debian/patches/python3.patch [3] https://salsa.debian.org/python-team/packages/python-envisage/-/jobs/3774219 -- http://fam-tille.de
Bug#1026088: rdma-core: diff for NMU version 44.0-1.1
On Tue, 2023-01-10 at 00:11 +0200, Adrian Bunk wrote: > Control: tags 1026088 + patch > Control: tags 1026088 + pending > > Dear maintainer, > > I've prepared an NMU for rdma-core (versioned as 44.0-1.1) and uploaded > it to DELAYED/2. Please feel free to tell me if I should cancel it. Thanks for the patch. The list of architectures that support coherent DMA gets very long. So I decided to inverse the list: https://github.com/linux-rdma/rdma-core/pull/1296 (otherwise I would have applied your patch). I successfully tested that change on amd64 and on a mipsel porter box. I will do an upload now overriding your NMU. -- Benjamin Drung Debian & Ubuntu Developer
Bug#1028398: snapd: both Telegram-desktop and Skype cannot load and save files
Package: snapd Version: 2.57.6-1+b1 Severity: grave X-Debbugs-Cc: none, Francesco Potortì I run two snap applications: telegram-desktop and skype. I had no problems before my vacations. Now neither can save received files or read files to send. Skype ignores the save or load command, telegram hangs. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (101, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=it_IT.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 snapd depends on: ii adduser 3.129 ii apparmor 3.0.8-1 ii ca-certificates 20211016 ii dbus-user-session [default-dbus-session-bus] 1.14.4-1 ii dbus-x11 [dbus-session-bus] 1.14.4-1 ii gnupg 2.2.40-1 ii gnupg11.4.23-1.1+b1 ii libapparmor1 3.0.8-1 ii libc6 2.36-6 ii libcap2 1:2.66-3 ii libseccomp2 2.5.4-1+b2 ii libudev1 252.4-1 ii openssh-client1:9.1p1-1 ii squashfs-tools1:4.5.1-1 ii systemd 252.4-1 ii udev 252.4-1 Versions of packages snapd recommends: ii gnupg 2.2.40-1 Versions of packages snapd suggests: ii zenity 3.43.0-1 -- no debconf information
Bug#1026524: marked as pending in ironic-inspector
Control: tag -1 pending Hello, Bug #1026524 in ironic-inspector reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/ironic-inspector/-/commit/8f3e69593564c4dfb127154e87ccdce42cda0e73 * Add Rename-NodeInfo._lock-to-avoid-conflict-with-Mock._lock-in-tests.patch, fixing FTBFS and autopkgtest (Closes: #1026524). (this message was generated automatically) -- Greetings https://bugs.debian.org/1026524
Processed: Bug#1026524 marked as pending in ironic-inspector
Processing control commands: > tag -1 pending Bug #1026524 [src:ironic-inspector] ironic-inspector: FTBFS: AttributeError: '_thread.RLock' object has no attribute 'is_locked' Added tag(s) pending. -- 1026524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026524 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026576: marked as done (spaln: FTBFS: dbs.cc:568:54: error: cannot convert ‘gzFile’ {aka ‘gzFile_s*’} to ‘FILE*’)
Your message dated Tue, 10 Jan 2023 13:24:40 +
with message-id
and subject line Bug#1026576: fixed in spaln 2.4.13e+dfsg-1
has caused the Debian Bug report #1026576,
regarding spaln: FTBFS: dbs.cc:568:54: error: cannot convert ‘gzFile’ {aka
‘gzFile_s*’} to ‘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.)
--
1026576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spaln
Version: 2.4.9a+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> x86_64-linux-gnu-g++ -g -O2 -ffile-prefix-map=/<>=. -flto=auto
> -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security
> -pedantic -O3 -Wall -DM_THREAD=1 -DUSE_ZLIB=1 -c gsinfo.cc
> dbs.cc: In constructor ‘DbsDt::DbsDt(const char*)’:
> dbs.cc:568:54: error: cannot convert ‘gzFile’ {aka ‘gzFile_s*’} to ‘FILE*’
> 568 | if (fread(dbsseq, sizeof(CHAR), rss, gzfd) <= 0)
> | ^~~~
> | |
> | gzFile {aka
> gzFile_s*}
> In file included from stdtype.h:25,
> from cmn.h:25,
> from seq.h:25,
> from dbs.cc:22:
> /usr/include/stdio.h:676:51: note: initializing argument 4 of ‘size_t
> fread(void*, size_t, size_t, FILE*)’
> 676 | size_t __n, FILE *__restrict __stream) __wur;
> | ~^~~~
> dbs.cc:570:24: error: cannot convert ‘gzFile’ {aka ‘gzFile_s*’} to ‘FILE*’
> 570 | fclose(gzfd);
> |^~~~
> ||
> |gzFile {aka gzFile_s*}
> /usr/include/stdio.h:178:26: note: initializing argument 1 of ‘int
> fclose(FILE*)’
> 178 | extern int fclose (FILE *__stream);
> |~~^~~~
> In file included from seq.h:60:
> dbs.h: In instantiation of ‘DbsRec* DbsDt::readidx(file_t, const char*) [with
> file_t = gzFile_s*]’:
> dbs.cc:529:34: required from here
> dbs.h:235:16: error: cannot convert ‘gzFile_s*’ to ‘FILE*’
> 235 | rewind(fidx);
> |^~~~
> ||
> |gzFile_s*
> /usr/include/stdio.h:723:27: note: initializing argument 1 of ‘void
> rewind(FILE*)’
> 723 | extern void rewind (FILE *__stream);
> | ~~^~~~
> dbs.h:236:51: error: cannot convert ‘gzFile_s*’ to ‘FILE*’
> 236 | if (fread(recidx, sizeof(DbsRec), numidx, fidx) != numidx)
> | ^~~~
> | |
> | gzFile_s*
> /usr/include/stdio.h:676:51: note: initializing argument 4 of ‘size_t
> fread(void*, size_t, size_t, FILE*)’
> 676 | size_t __n, FILE *__restrict __stream) __wur;
> | ~^~~~
> dbs.h:238:16: error: cannot convert ‘gzFile_s*’ to ‘FILE*’
> 238 | fclose(fidx);
> |^~~~
> ||
> |gzFile_s*
> /usr/include/stdio.h:178:26: note: initializing argument 1 of ‘int
> fclose(FILE*)’
> 178 | extern int fclose (FILE *__stream);
> |~~^~~~
> dbs.h: In instantiation of ‘void DbsDt::readentry(file_t, const char*) [with
> file_t = gzFile_s*]’:
> dbs.cc:542:25: required from here
> dbs.h:199:19: error: cannot convert ‘gzFile_s*’ to ‘FILE*’
> 199 | fseek(fent, 0L, SEEK_END);
> | ^~~~
> | |
> | gzFile_s*
> /usr/include/stdio.h:713:25: note: initializing argument 1 of ‘int
> fseek(FILE*, long int, int)’
> 713 | extern int fseek (FILE *__stream, long int __off, int __whence);
> | ~~^~~~
> dbs.h:200:37: error: cannot convert ‘gzFile_s*’ to ‘FILE*’
> 200 | ent_space = (INT) ftell(fent);
> | ^~~~
> | |
> | gzFile_s*
> /usr/include/stdio.h:718:30: note: initializin
Bug#1022378: marked as done (librdfa-java: FTBFS: [ERROR] /<>/rdfa-module/src/main/java/net/rootdev/javardfa/jena/RDFaReader.java:[31,23] cannot find symbol)
Your message dated Tue, 10 Jan 2023 13:23:52 + with message-id and subject line Bug#1022378: fixed in librdfa-java 1.0.0~BETA1-3 has caused the Debian Bug report #1022378, regarding librdfa-java: FTBFS: [ERROR] /<>/rdfa-module/src/main/java/net/rootdev/javardfa/jena/RDFaReader.java:[31,23] cannot find symbol 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.) -- 1022378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: librdfa-java Version: 1.0.0~BETA1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > mh_patchpoms -plibrdfa-java --debian-build --keep-pom-version > --maven-repo=/<>/librdfa-java-1.0.0\~BETA1/debian/maven-repo >dh_auto_build > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<>/librdfa-java-1.0.0\~BETA1 > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/librdfa-java-1.0.0\~BETA1/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml > -Ddebian.dir=/<>/librdfa-java-1.0.0\~BETA1/debian > -Dmaven.repo.local=/<>/librdfa-java-1.0.0\~BETA1/debian/maven-repo > --batch-mode package -DskipTests -Dnotimestamp=true -Dlocale=en_US > [0m[0m[INFO] Scanning for projects... > [INFO] > > [INFO] Reactor Build Order: > [INFO] > [INFO] java-rdfa-parent > [pom] > [INFO] java-rdfa-htmlparser > [jar] > [INFO] java-rdfa > [bundle] > [INFO] > [INFO] < net.rootdev:java-rdfa-parent > > > [INFO] Building java-rdfa-parent 1.0.0-BETA1 > [1/3] > [INFO] [ pom > ]- > [INFO] > [INFO] --< net.rootdev:java-rdfa-htmlparser > >-- > [INFO] Building java-rdfa-htmlparser 1.0.0-BETA1 > [2/3] > [INFO] [ jar > ]- > [WARNING] The artifact > org.apache.maven.plugins:maven-surefire-plugin:jar:2.12.4 has been relocated > to org.apache.maven.plugins:maven-surefire-plugin:jar:2.22.3 > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ > java-rdfa-htmlparser --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory > /<>/htmlparser-module/src/main/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ > java-rdfa-htmlparser --- > [INFO] No sources to compile > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) > @ java-rdfa-htmlparser --- > [INFO] Not copying test resources > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ > java-rdfa-htmlparser --- > [INFO] Not compiling test sources > [INFO] > [INFO] --- maven-surefire-plugin:2.22.3:test (default-test) @ > java-rdfa-htmlparser --- > [INFO] Tests are skipped. > [INFO] > [INFO] --- maven-jar-plugin:3.3.0:jar (default-jar) @ java-rdfa-htmlparser --- > [WARNING] JAR will be empty - no content was marked for inclusion! > [INFO] Building jar: > /<>/htmlparser-module/target/java-rdfa-htmlparser-1.0.0-BETA1.jar > [INFO] > [INFO] ---< net.rootdev:java-rdfa > > > [INFO] Building java-rdfa 1.0.0-BETA1 > [3/3] > [INFO] ---[ bundle > ]--- > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ > java-rdfa --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 2 resources > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ java-rdfa > --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 27 source files to > /<>/rdfa-module/target/classes > [INFO] > /<>/rdfa-module/src/main/
Processed: Re: Bug#1028026 closed by Debian FTP Masters (reply to Alastair McKinstry ) (Bug#1028026: fixed in vistrails 3.0~git+9dc22bd-5)
Processing control commands:
> reopen -1
Bug #1028026 {Done: Alastair McKinstry } [vistrails]
vistrails: contains non-free font file
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions vistrails/3.0~git+9dc22bd-5.
> reassign -1 src:vistrails
Bug #1028026 [vistrails] vistrails: contains non-free font file
Bug reassigned from package 'vistrails' to 'src:vistrails'.
No longer marked as found in versions vistrails/3.0~git+9dc22bd-4.
Ignoring request to alter fixed versions of bug #1028026 to the same values
previously set
> notfixed -1 vistrails/3.0~git+9dc22bd-5
Bug #1028026 [src:vistrails] vistrails: contains non-free font file
The source vistrails and version 3.0~git+9dc22bd-5 do not appear to match any
binary packages
Ignoring request to alter fixed versions of bug #1028026 to the same values
previously set
> found -1 vistrails/3.0~git+9dc22bd-5
Bug #1028026 [src:vistrails] vistrails: contains non-free font file
The source vistrails and version 3.0~git+9dc22bd-5 do not appear to match any
binary packages
Marked as found in versions vistrails/3.0~git+9dc22bd-5.
--
1028026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1028026: closed by Debian FTP Masters (reply to Alastair McKinstry ) (Bug#1028026: fixed in vistrails 3.0~git+9dc22bd-5)
Control: reopen -1 Control: reassign -1 src:vistrails Control: notfixed -1 vistrails/3.0~git+9dc22bd-5 Control: found -1 vistrails/3.0~git+9dc22bd-5 Looks like you have only dropped the file from the binary package. It is still contained in the source package and you will need to repack to get rid of it.
Bug#1028026: marked as done (vistrails: contains non-free font file)
Your message dated Tue, 10 Jan 2023 12:39:11 + with message-id and subject line Bug#1028026: fixed in vistrails 3.0~git+9dc22bd-5 has caused the Debian Bug report #1028026, regarding vistrails: contains non-free font 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.) -- 1028026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vistrails Severity: serious Version: 3.0~git+9dc22bd-4 vistrails packages the file "Franklin Gothic No. 2 Roman.ttf" twice. This has a non-free license. Please repack to remove it. --- End Message --- --- Begin Message --- Source: vistrails Source-Version: 3.0~git+9dc22bd-5 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of vistrails, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated vistrails 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, 09 Jan 2023 12:47:59 + Source: vistrails Architecture: source Version: 3.0~git+9dc22bd-5 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 1028026 Changes: vistrails (3.0~git+9dc22bd-5) unstable; urgency=medium . * Drop non-free font file. Closes: #1028026 Checksums-Sha1: 502e84cf1d6195b8b19e3a5b3598fa68580c17f4 2030 vistrails_3.0~git+9dc22bd-5.dsc 6b0d95ed2173aa3256a2c8eeae9c543d73f70a14 18960 vistrails_3.0~git+9dc22bd-5.debian.tar.xz Checksums-Sha256: 28b0434ddd86bae10d7268356ab49cd2cf4b55be9791b308bd519711f8fee4d4 2030 vistrails_3.0~git+9dc22bd-5.dsc 326fcff64e68b6e6111d8965884b3567b7c28ae8d5145aae8d967eee4b166836 18960 vistrails_3.0~git+9dc22bd-5.debian.tar.xz Files: f0e190fc299df123973477b7bc226395 2030 science optional vistrails_3.0~git+9dc22bd-5.dsc 77648a4c4fc67eb396e97a06e327dd4a 18960 science optional vistrails_3.0~git+9dc22bd-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmO8MyQACgkQy+a7Tl2a 06XZUw/+NvunV900IfUFt89TtWnXkNrnWxZHeSbglQIiOdM6I2lZGdyk3GUo40gq U+7HIStPbrsRowEP/MFuzwMHWHD7vokx53tMPEL9yrCB0kV2/FL3Qb1zSfNUuRbZ EauRZ9fiGLsluvgeJN0oEm6KKgMNazqW74iXBLgDHYC3wAH/kTGFacGfp0BtGMeH IgReeKjRz0k61YEaTrjeZZgzsz8qyMvDH/ryerOHW0pIqNRNDt22TEflqlfwqI5h WW3FcrBsy3WUurMa1WoKyceGbIbaCFz2qdggV32R+oaM/NVdjnDkWmlPouZngZim QqWKAbxx1b8V6OozqwmYmjKYFI3D1K0KbnW3MRjt4pH09N1Vyfk5TTFa+jEbI402 92ScIfzZtWqzT2rciE58jESVKGCcfhgXJs6DiJNkpCdJHSc03wSVJ1G+ieB8AKH8 0lJGTrEAK736gM96G49HCsifKEz5pEsA+EimHMd1cossxPPNwiXBp1HqViKaym0S LPnHqd4g18++xoBmJAkfLIOgNgn9AwBYkps8rhgPL0p06Xn8wAM6BQrrtdhIycox SfnAn8rgI6wZcbMC1Lmw4lv/5ReCwHLO43s+bt6tgko5hcw7cFn2roJ+8TrwARyy 02rRkC0f135kbmcUL1cTiUjkUqbb2si9WrLJVZ3QhUieHPo3DN0= =5lM5 -END PGP SIGNATURE End Message ---
Bug#1028348: marked as done (src:r-cran-callr: fails to migrate to testing for too long: autopkgtest regression)
Your message dated Tue, 10 Jan 2023 12:38:20 + with message-id and subject line Bug#1028348: fixed in r-cran-callr 3.7.3-2 has caused the Debian Bug report #1028348, regarding src:r-cran-callr: fails to migrate to testing for too long: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1028348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-callr Version: 3.7.2-1 Severity: serious Control: close -1 3.7.3-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:r-cran-callr has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package fails its own autopkgtest everywhere. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=r-cran-callr OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: r-cran-callr Source-Version: 3.7.3-2 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of r-cran-callr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated r-cran-callr 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: Tue, 10 Jan 2023 09:24:19 +0100 Source: r-cran-callr Architecture: source Version: 3.7.3-2 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille Closes: 1028348 Changes: r-cran-callr (3.7.3-2) unstable; urgency=medium . * Force excludion of asciicast calls from tests Closes: #1028348 * Standards-Version: 4.6.2 (routine-update) Checksums-Sha1: 759b472b656a24531415a688ead31999f730fe54 2141 r-cran-callr_3.7.3-2.dsc 4a610e3e0d71e4d606c5b01b29a6309624b4fa47 4152 r-cran-callr_3.7.3-2.debian.tar.xz 32fd9d3705e0d1ec102a7dd1a9530834f352cf90 20238 r-cran-callr_3.7.3-2_source.buildinfo Checksums-Sha256: 65d1f45563daa561c9e701402e4ca7f156101092e424466a0924866ee66b6405 2141 r-cran-callr_3.7.3-2.dsc 6297a3b5cad8565a401b7eaf36d83730f32680ef037965da6df3a1eb7268c9cc 4152 r-cran-callr_3.7.3-2.debian.tar.xz 9dca2c8ea526cd5ad2caba8ae64d7f1ce40a5504b389eac72a934f5e21f11d35 20238 r-cran-callr_3.7.3-2_source.buildinfo Files: 80a5fcfa754d146c681a097274775893 2141 gnu-r optional r-cran-callr_3.7.3-2.dsc 961b01d873ac0edc2eed9368419ba2f7 4152 gnu-r optional r-cran-callr_3.7.3-2.debian.tar.xz 1c174b28653dbec6532fb782b6a276a1 20238 gnu-r optional r-cran-callr_3.7.3-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJCBAEBCgAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmO9Ic8OHHRpbGxlYUBy a2kuZGUACgkQV4oElNHGRtED5A/9F4CXQStkGMkz9jZk7FIfjsDk4KDqNL7MJi1N yIl/l9s5zdxaJyE/rMTSV/Gg5zKcHMdCRqWFsp7LrZiKRLsaP2Xmb+E5wS4Ox5oF xb8cLprIuaAUc01LkOVaLmLlgI75Z5UNIh9qVa
Bug#1028172: marked as done (libmpich-dev lacks dependencies required by its pkgconfig file)
Your message dated Tue, 10 Jan 2023 12:37:22 + with message-id and subject line Bug#1028172: fixed in mpich 4.0.2-3 has caused the Debian Bug report #1028172, regarding libmpich-dev lacks dependencies required by its pkgconfig 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.) -- 1028172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tiledarray Version: 1.0.0-1 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu lunar Hi Michael, tiledarray's build-dependencies are now satisfied in unstable (bug #1014548), but it fails to build from source :) [...] CMake Error at /usr/share/cmake-3.25/Modules/CMakeTestCXXCompiler.cmake:63 (message): The C++ compiler "/usr/bin/c++" is not able to compile a simple test program. It fails with the following output: Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98 Run Build Command(s):/usr/bin/gmake -f Makefile cmTC_d2ec9/fast && gmake[2]: Entering directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98' /usr/bin/gmake -f CMakeFiles/cmTC_d2ec9.dir/build.make CMakeFiles/cmTC_d2ec9.dir/build gmake[3]: Entering directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98' Building CXX object CMakeFiles/cmTC_d2ec9.dir/testCXXCompiler.cxx.o /usr/bin/c++ -I/usr/include/x86_64-linux-gnu/mpich -o CMakeFiles/cmTC_d2ec9.dir/testCXXCompiler.cxx.o -c /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98/testCXXCompiler.cxx Linking CXX executable cmTC_d2ec9 /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_d2ec9.dir/link.txt --verbose=1 /usr/bin/c++ -I/usr/include/x86_64-linux-gnu/mpich -lmpich -lpthread -lhwloc -lucp -lucs -lrt CMakeFiles/cmTC_d2ec9.dir/testCXXCompiler.cxx.o -o cmTC_d2ec9 /usr/bin/ld: cannot find -lhwloc: No such file or directory /usr/bin/ld: cannot find -lucp: No such file or directory /usr/bin/ld: cannot find -lucs: No such file or directory collect2: error: ld returned 1 exit status gmake[3]: *** [CMakeFiles/cmTC_d2ec9.dir/build.make:99: cmTC_d2ec9] Error 1 gmake[3]: Leaving directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98' gmake[2]: *** [Makefile:127: cmTC_d2ec9/fast] Error 2 gmake[2]: Leaving directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98' [...] (https://buildd.debian.org/status/fetch.php?pkg=tiledarray&arch=amd64&ver=1.0.0-1&stamp=1673126398&raw=0) Possibly an issue in a build-dependency, I see that these library options come from the output of `pkg-config --libs-only-l mpi` but libmpich-dev apparently doesn't depend on the packages providing the libs in its output. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: mpich Source-Version: 4.0.2-3 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of mpich, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated mpich 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: Tue, 10 Jan 2023 09:40:39 + Source: mpich Architecture: source Version: 4.0.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Alastair McKinstry Closes: 1028172 Changes: mpich (4.0.2-3) unstable; urgency=medium . * Standards-Version: 4.6.1 * Add Deps to libmpich-dev needed for pkg-config. Closes: #1028172 Checksums-Sha1: 2f0c0446a5f197f4c3f63b953f3aa13ca3524207 2870 mpich_4.0.2-3.dsc 51a740c8a639c01f08f690d21a322456470446e8 339140 mpich_4.0.2-3.debian.tar.xz Che
Bug#1028240: marked as done (poetry: FTBFS (requires internet access))
Your message dated Tue, 10 Jan 2023 12:04:35 + with message-id and subject line Bug#1028240: fixed in poetry 1.3.1+dfsg-2 has caused the Debian Bug report #1028240, regarding poetry: FTBFS (requires internet access) 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.) -- 1028240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028240 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: poetry Version: 1.3.1+dfsg-1 Severity: Serious Hello, looks like the package is using internet during build. No changing rebuilding with disabled internet results in tests failures dpkg-source: info: building poetry in poetry_1.3.1+dfsg-1.dsc debian/rules binary dh binary --with python3 --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild dh_auto_build -O--buildsystem=pybuild I: pybuild plugin_pyproject:107: Building wheel for python3.10 with "build" module I: pybuild base:240: python3.10 -m build --skip-dependency-check --no-isolation --wheel --outdir /poetry-1.3.1+dfsg/.pybuild/cpython3_3.10_poetry * Building wheel... Successfully built poetry-1.3.1-py3-none-any.whl I: pybuild plugin_pyproject:119: Unpacking wheel built for python3.10 with "installer" module I: pybuild plugin_pyproject:107: Building wheel for python3.11 with "build" module I: pybuild base:240: python3.11 -m build --skip-dependency-check --no-isolation --wheel --outdir /poetry-1.3.1+dfsg/.pybuild/cpython3_3.11_poetry * Building wheel... Successfully built poetry-1.3.1-py3-none-any.whl I: pybuild plugin_pyproject:119: Unpacking wheel built for python3.11 with "installer" module dh_auto_test -O--buildsystem=pybuild I: pybuild base:240: cd /poetry-1.3.1+dfsg/.pybuild/cpython3_3.10_poetry/build; python3.10 -m pytest --ignore=tests/console/commands/env/test_list.py --ignore=tests/console/commands/env/test_remove.py --ignore=tests/console/commands/env/test_use.py --ignore=tests/utils/test_env.py --ignore=tests/config/test_config.py --ignore=tests/utils/test_helpers.py -k 'not test_self_update_should_install_all_necessary_elements and not test_add_file_constraint_sdist and not test_add_file_constraint_sdist_old_installer and not test_publish_dry_run and not test_info_from_sdist and not test_installer_can_install_dependencies_from_forced_source and not test_search_for_file_sdist and not test_search_for_file_sdist_with_extras and not test_solver_can_resolve_sdist_dependencies and not test_solver_can_resolve_sdist_dependencies_with_extras and not test_solver_chooses_from_correct_repository_if_forced and not test_solver_chooses_from_correct_repository_if_forced_and_transitive_dependency and not test_solver_does_not_choose_from_secondary_repository_by_default and not test_solver_chooses_from_secondary_if_explicit and not test_get_package_information_fallback_read_setup and not test_get_package_information_skips_dependencies_with_invalid_constraints and not test_get_package_retrieves_packages_with_no_hashes and not test_fallback_can_read_setup_to_get_dependencies and not test_exporter_can_export_requirements_txt_with_file_packages and not test_exporter_can_export_requirements_txt_with_file_packages_and_markers and not test_lock_no_update and not test_locker_dumps_dependency_information_correctly and not test_package_partial_yank and not test_run_installs_with_same_version_url_files and not test_env_info_displays_complete_info and not test_skip_existing_output and not test_installer_should_use_the_locked_version_of_git_dependencies_with_extras and not test_installer_should_use_the_locked_version_of_git_dependencies_without_reference and not test_installer_uses_prereleases_if_they_are_compatible and not test_requirement_git_subdirectory and not test_check_valid and not test_check_invalid and not test_packages_property_returns_empty_list and not test_parse_dependency_specification and not test_info_setup_missing_mandatory_should_trigger_pep517' === test session starts === platform linux -- Python 3.10.9, pytest-7.2.0, pluggy-1.0.0+repack rootdir: /poetry-1.3.1+dfsg, configfile: pyproject.toml plugins: mock-3.8.2, xdist-3.1.0 gw0 [1056] / gw1 [1056] / gw2 [1056] / gw3 [1056] / gw4 [1056] / gw5 [1056] / gw6 [1056] / gw7 [1056]
