Bug#1032914: phog: ships /etc/pam.d/greetd
Quack, On 2023-03-24 18:24, Arnaud Ferraris wrote: Well yes, it was only supposed to be transitional waiting for https://lists.sr.ht/~kennylevinsen/greetd/patches/36264 to land upstream, but I went a bit too optimistic on that one, my bad... That's fine. The greeter PAM config drops the gnome-keyring/kwallet bits in order to be a bit lighter at runtime (those lines cause at least "gnome-keyring-daemon" to be started for user "_greetd", which is basically useless as it's a system user with no actual use of a keyring). Therefore I feel it's best to keep both config separate, but I'd be fine with a single config if you prefer it that way. Ok, makes sense, I was not aware it spawned anything. Thanks for the comments, I'm attaching the updated patches. Thanks for your work. I just merged it and will be uploading shortly. Regards. \_o< -- Marc Dequènes
Bug#888025: gpgsm: UI asks insane, unanswerable trust questions
Dear maintainer,
I've recently started to re-experience that bug (#888025), probably because
someone is sending me emails using some "certificate".
It is in the form of a popups when Kmail is opened in the background. Those
popups come randomly without user action.
I understand it would be useless to answer yes to the popup. Additionally, it
doesn't seem legit/safe at all, for someone who doesn't have the necessary
knowledge, to answer yes to "do you ultimately trust XXX to correctly certify
user certificates?"
I've read the explanations/comments in the bug, but I didn't understand
anything, sorry.
The certificate in the popup is the same as this one:
```
$ awk -v cmd='openssl x509 -noout -subject' '/BEGIN/{close(cmd)};{print |
cmd}' < /etc/ssl/certs/ca-certificates.crt | grep 'Manchester.*AAA'
subject=C = GB, ST = Greater Manchester, L = Salford, O = Comodo CA Limited,
CN = AAA Certificate Services
```
I've been told to try: `sudo dpkg-reconfigure ca-certificates`, but that didn't
change anything.
It won't crash the system, but it's very very annoying/disruptive for the
user.
Thanks,
Chris
Processed: gpgsm: UI asks insane, unanswerable trust questions
Processing commands for cont...@bugs.debian.org: > severity 888025 grave Bug #888025 [gpgsm] gpgsm: UI asks insane, unanswerable trust questions Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 888025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032032: FTBFS: error: AM_INIT_AUTOMAKE expanded multiple times
On Thu, 30 Mar 2023, Markus Koschany wrote: Control: tags -1 pending Hi Thomas, Am Donnerstag, dem 30.03.2023 um 17:05 +0200 schrieb Thomas Uhle: > Dear maintainers, > > could someone of you please prepare a new version of fenix-plugins with my > patch added to save it from being auto-removed. thanks for your patch! Looks good to me. I'm going to upload a new revision in a minute. Cheers, Markus Hi Markus, thanks a lot! Cheers, Thomas
Bug#1033715: marked as done (gir1.2-rest-1.0: Missing dependency on librest-1.0-0)
Your message dated Thu, 30 Mar 2023 20:57:54 + with message-id and subject line Bug#1033715: fixed in librest 0.9.1-6 has caused the Debian Bug report #1033715, regarding gir1.2-rest-1.0: Missing dependency on librest-1.0-0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1033715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: librest Version: 0.9.1-2 Severity: serious Tags: pending bookworm sid gir1.2-rest-1.0 is missing its automatic dependency on librest-1.0-0 I accidentally introduced this regression in 0.9.1-2. It's fixed by running the gir debhelper sequence. Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: librest Source-Version: 0.9.1-6 Done: Jeremy Bicha We believe that the bug you reported is fixed in the latest version of librest, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bicha (supplier of updated librest 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, 30 Mar 2023 15:52:01 -0400 Source: librest Built-For-Profiles: noudeb Architecture: source Version: 0.9.1-6 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bicha Closes: 1033715 Launchpad-Bugs-Fixed: 2013267 Changes: librest (0.9.1-6) unstable; urgency=medium . * Build-Depend on dh-sequence-gir to fix missing dependencies from the gir packages (Closes: #1033715) (LP: #2013267) Checksums-Sha1: de2a48d2cd6fc06dfd9813b42cd4c098810213c3 2553 librest_0.9.1-6.dsc 9cda4b2a689cdf6a582de9601ba1e0d4e13d88b7 7544 librest_0.9.1-6.debian.tar.xz 611a1d882a553468e4c3d0372ae6fe6cf3201e22 17451 librest_0.9.1-6_source.buildinfo Checksums-Sha256: 2c62ba0eb9e27c9128a9f12246c81c4a2ed65083b7bb3c770db40e37e8fc98a7 2553 librest_0.9.1-6.dsc 05a05bab7af3ea1a8d1dec16c94dc8741555f4a1a9cbca6d9748a52628e6d7f1 7544 librest_0.9.1-6.debian.tar.xz 3525810ed4c4c1b97ed6320d754b9971a0661ed544cf33c6a9673422614831af 17451 librest_0.9.1-6_source.buildinfo Files: e895add7eaae6e8d61834929a152ec21 2553 libs optional librest_0.9.1-6.dsc 7d4cc29af54952aab000380b37f6ce4f 7544 libs optional librest_0.9.1-6.debian.tar.xz fd4ab0fbf05858041df422002907ee99 17451 libs optional librest_0.9.1-6_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmQl6HEACgkQ5mx3Wuv+ bH3KeQ/9FeyaBrbdynFWErHF+QbV9PWS8SONmj+uXFmzrnvh9I+oMAwt9XIMDzqa k6rY0v2BhLmeGeMu5W2acXmqih9UfChKeUuA20T8cGEwiq4mCR6AZs7pBATSc5Fq UnekoVw7l/bW0TXuEyoTkAJNckWb6FMeAZCkOFIgXkooVPAXlEZckYCUCeu0/K5b jLx5chYzTF+r3prtcJYFhyslPyyUzggvKyM5rcTK7qJNQI8zSwvhN6ChL5flaOG1 /qgtqxgC7Fyp3v928PnPvWj+JAZ9RYlT/fKl4jONADNjmJaeftnERrzKX/h94ZOF q6cXjZ2aq7AFsjRLVDFJy1td7uVE88pw0Im4qe+cGqHBisWphnGKDFjJ7tXDfhfu QIsfu5PnlBLGmkU4yYnoF5jqL1gHOOb7TlBqOlgSYh4JKHqXPuOrIyDLk1Z+Rc7i 1EAWbrw/W+Zzn35ebPHE7jLlGh2umSYTArxLRMv6Kv2eQQZP5Mhjtqd7tfE2u4rw v6AHTaMay2oKm2mmVeTJEo/qUBq5G7r4z/aGF7MRA1AfnFI4vJQDRD92xhMnkwDd fLCMjHc0GKYeIDR0X4mJ6aUfbtvJyojeeVVytQYp3HAsAP5qF/bv59DEkQSdcFTQ qu19AeDLVH0xforQezM+r+jsBI+wD2MjMioL+wM6JHy+GVgoYfs= =b0dG -END PGP SIGNATURE End Message ---
Bug#1032032: marked as done (FTBFS: error: AM_INIT_AUTOMAKE expanded multiple times)
Your message dated Thu, 30 Mar 2023 20:52:35 + with message-id and subject line Bug#1032032: fixed in fenix-plugins 0.0.20070803-9 has caused the Debian Bug report #1032032, regarding FTBFS: error: AM_INIT_AUTOMAKE expanded multiple times 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.) -- 1032032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fenix-plugins Version: 0.0.20070803-8 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi! I'm afraid your package fails to build; I see a lot of autoconf warnings, then they get fatal: Makefile.am: installing './depcomp' configure.ac:12: error: AM_INIT_AUTOMAKE expanded multiple times /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... configure.ac:11: the top level /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... configure.ac:12: the top level autom4te: error: /usr/bin/m4 failed with exit status: 1 aclocal: error: /usr/bin/autom4te failed with exit status: 1 autoreconf: error: aclocal failed with exit status: 1 dh_autoreconf: error: autoreconf -f -i agua-1.0 exec-0.4a fgfx-1.0 fire-1.0 fsock-1.0 image-1.0 mixer-1.0 mpeg-1.0 net-1.0 tcpsock-2.0 ttf-1.0 returned exit code 1 It appears the package is not compatible with new autotools; they have been updated quite a while ago but as the package is 32-bit only the failure wasn't noticed during usual QA efforts. I've verified the fail on i386 and armhf. Full log attached. Meow! -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (120, 'experimental'), (1, 'experimental-debug') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.2.0-00034-g2ff294a21c8d (SMP w/64 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) sbuild (Debian sbuild) 0.85.0 (04 January 2023) on valinor.angband.pl +==+ | fenix-plugins (i386) Sun, 26 Feb 2023 01:31:02 + | +==+ Package: fenix-plugins Distribution: unstable Machine Architecture: amd64 Host Architecture: i386 Build Architecture: i386 Build Type: binary I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-i386-sbuild-f27f2fb3-5a2c-41fa-94ad-2023f47260fb' with '<>' I: NOTICE: Log filtering will replace 'build/fenix-plugins-gpzT6Q/resolver-zNf5Pt' with '<>' +--+ | Update chroot| +--+ Hit:1 http://apt-rosy.angband.pl:3142/debian unstable InRelease Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. +--+ | Fetch source files | +--+ Check APT - Checking available source versions... Download source files with APT -- Reading package lists... NOTICE: 'fenix-plugins' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/games-team/fenix-plugins.git Please use: git clone https://salsa.debian.org/games-team/fenix-plugins.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 7775 kB of source archives. Get:1 http://apt-rosy.angband.pl:3142/debian unstable/main fenix-plugins 0.0.20070803-8 (dsc) [2749 B] Get:2 http://apt-rosy.angband.pl:3142/debian unstable/main fenix-plugins 0.0.20070803-8 (tar) [7766 kB] Get:3 http://apt-rosy.angband.pl:3142/debian unstable/main fenix-plugins 0.0.20070803-8 (diff) [6336 B] Fetched 7775 kB in 0s (262 MB/s) Download complete and in download only mode I: NOTICE: Log filtering will replace 'build/fenix-plugins-gpzT6Q/fenix-plugins-0.0.20070803' with '<>' I: NOTICE: Log filtering will replace 'build/fenix-plugins-gpzT6Q' with '<>'
Bug#1033617: libopenexr-dev: Cannot just upgrade libopenexr-dev to 3.1.5-4 because of file conflict with older version of libilmbase-dev
Hello, that's true, somehow I messed up the version number, sorry. I had libilmbase-dev version 2.5.7-2+b1 installed when I ran into this issue according to my aptitude log. I also tried out to reproduce the issue again in Docker & succeeded, see the attached Dockerfile. However, after seeing how old both package versions are and that these exact versions were not available at the same time, I do not know how I ended up with exactly these versions and using them until just a few days ago. Maybe another package which wasn't updated for quite a while had a hardlocked dependency. To know for sure, I would need to restore the full list of packages & versions I had installed before upgrading by reading the dpkg logs. Best Regards, Felix Stupp Am Mittwoch, 29. März 2023, 19:06:29 CEST schrieben Sie: > On 2023-03-28 Felix Stupp wrote: > > Package: libopenexr-dev > > Version: 3.1.5-4 > > Severity: serious > > Justification: Policy 7.4 > > X-Debbugs-Cc: me+debian-b...@banananet.work > > > Dear Maintainer, > > > I cannot upgrade this package from version 2.5.7-1 to version 3.1.5-4 > > due to a file conflict with the package libilmbase-dev on version > > 2.5.4-1. I tried with apt & aptitude as well. Both want to replace > > libilmbase-dev with libopenexr-dev in a single execution of them, but > > fail to do that in a way that dpkg allows that (tries first to install > > the new package and then uninstall the old one). > > Currently I see no other solution than removing the old one first aside > > with all packages depending it on it, and then installing the new one > > with all packages which were removed before. > [...] > > Hello, > > I cannot reporoduce this from your description because the original > setup you started with > > libopenexr-dev + libopenexr25 2.5.7-1 > libilmbase-dev + libilmbase25 2.5.4-1 > > is not installable, libopenexr25 2.5.7-1 depends on libilmbase25 (>= 2.5.7). > > cu Andreas > FROM docker.io/library/debian:bookworm-20230320 # Install tools required further RUN apt-get update && apt-get install -y aptitude # Disable current and enable snapshot repository RUN sed -i -r 's~# ~URIs: ~;s~URIs:( http://deb.debian.org)~#\1~' /etc/apt/sources.list.d/debian.sources # Enable old enough snapshot repository RUN sed -i -r 's~# ~URIs: ~;s~/20[0-9]*(T[0-9]*Z)$~/20210929\1~;s~URIs:( http://deb.debian.org)~#\1~' /etc/apt/sources.list.d/debian.sources RUN aptitude -o Acquire::Check-Valid-Until=false update # Install packages to break RUN aptitude install -y libopenexr-dev=2.5.7-1 # Jump to specific date RUN sed -i -r 's~/20[0-9]*(T[0-9]*Z)$~/20221010\1~' /etc/apt/sources.list.d/debian.sources RUN cat /etc/apt/sources.list.d/debian.sources RUN aptitude -o Acquire::Check-Valid-Until=false update # Install packages to break RUN aptitude install -y libilmbase-dev=2.5.7-2+b1 # Reset to newer repository RUN sed -i -r 's~# ~URIs: ~;s~URIs:( http://snapshot.debian.org)~#\1~' /etc/apt/sources.list.d/debian.sources RUN aptitude update # Try to upgrade package with following command: # apt install -y libopenexr-dev>=3.1.5-4
Bug#1031716: python3-protobuf: Do reverse dependencies need stricter version constraints?
On Tue, Feb 21, 2023 at 02:23:34PM +0200, Adrian Bunk wrote: > Looking at #1028371, should generated dependencies on python3-protobuf be > python3-protobuf (>= 3.21), python3-protobuf (<< 3.22) > to ensure that the binary package is used with the same version > as the protobuf-compiler used during the build? I'm not the maintainer, but a drive-by contributor. I looked a bit into this, given its RC severity. With my still somewhat limited understanding, a strict version alignment between protobuf-compiler and python3-protobuf would probably resolve this particular symptom, but the issues here seem to run deeper. Specifically: * The protobuf project provides three different versions of Python bindings: pure Python, C++, and libupb-based[1]. These are selectable using the PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION environment variable. * Debian's python3-protobuf, from src:protobuf, ships the pure Python version, as well as the C++ bindings. The default implementation in Debian is "cpp". * The upb implementation is not included in src:protobuf, but in the upb upstream source[2], i.e. what is src:upb in Debian, even though the snapshot we have in Debian does not contain sources to Python bindings. * Upstream has switched the default implementation to "upb", and deprecated the "cpp" implementation. There is, in fact, no way for one to fetch the "cpp" version from PyPI. This is documented extensively in their May 2022 release notes[3]. However, Debian still ships, and defaults to, cpp, a major departure from upstream. * Relatedly, when they made that switch, they also made changes to their versioning scheme, disconnecting the Python library's version from the source version. As a result, the Python API (both upb, as well as pure Python), is now versioned at "4.21", rather than "3.21". The Debian binary package python3-protobuf is versioned as "3.21.12-1", which is not a version that exists, or will ever exist, upstream. That binary package in fact, is shipping an egg named protobuf-4.21.12.egg-info. (This is all also well documented in their release notes[3]). * Finally, in the same release notes document[3], they also state: "Python upb requires generated code that has been generated from protoc 3.19.0 or newer.". Indeed, if one fetches protobuf 4.21 from PyPI, and runs: python3 -c 'import bernhard' or PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=upb python3 -c 'import bernhard' ...a traceback message is emitted, but a much more informative one: > TypeError: Descriptors cannot not be created directly. > > If this call came from a _pb2.py file, your generated code is out of > date and must be regenerated with protoc >= 3.19.0. > > If you cannot immediately regenerate your protos, some other possible workarounds are: > 1. Downgrade the protobuf package to 3.20.x or lower. > 2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python (but this will > use pure-Python parsing and will be much slower). > > More information: https://developers.google.com/protocol-buffers/docs/news/2022-05-06#python-updates * The release notes specifically mention "upb" requiring protoc (protobuf-compiler) >= 3.19, but not "cpp". However, as established above, "cpp" is deprecated and not used by anyone (but Debian), and therefore they either meant "the non-Pure-Python implementation" there, or did not pay as much attention to forward- and backwards-compatibility, or informative error messages for their deprecated backend. It's likely, but not entirely clear, that the protoc dependency requirement is >= 3.19 here as well. * Finally note that the 3.21.12-1+b2 Python implementation still works with python3-bernhard, Built-Using: protobuf-compiler (= 3.12.4-1+b3): PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python python3 -c 'import bernhard' All in all: it's almost certainly necessary to make the dependency tighter, to something like >= 3.19, if not tight to = 3.21. I still feel uneasy about Debian shipping a version of python3-protobuf that includes, and defaults to, an implementation that is deprecated upstream (and on top of it, is misversioned). I'm not sure what to make of this so late in the release cycle, though. For trixie the path forward is probably something along the lines of updating src:upb to a newer upstream, building the upb-based extension as python3-protobuf-upb, and then changing src:protobuf to not build the cpp extension, make python3-protobuf Arch: all, and then Recommend (or Depend) on python3-protobuf-upb as the native/fast implementation. Faidon 1: https://github.com/protocolbuffers/protobuf/tree/main/python 2: https://github.com/protocolbuffers/upb/tree/main/python 3: https://protobuf.dev/news/2022-05-06/
Processed: Re: Bug#1032032: FTBFS: error: AM_INIT_AUTOMAKE expanded multiple times
Processing control commands: > tags -1 pending Bug #1032032 [src:fenix-plugins] FTBFS: error: AM_INIT_AUTOMAKE expanded multiple times Added tag(s) pending. -- 1032032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032032: FTBFS: error: AM_INIT_AUTOMAKE expanded multiple times
Control: tags -1 pending Hi Thomas, Am Donnerstag, dem 30.03.2023 um 17:05 +0200 schrieb Thomas Uhle: > Dear maintainers, > > could someone of you please prepare a new version of fenix-plugins with my > patch added to save it from being auto-removed. thanks for your patch! Looks good to me. I'm going to upload a new revision in a minute. Cheers, Markus signature.asc Description: This is a digitally signed message part
Bug#1033715: gir1.2-rest-1.0: Missing dependency on librest-1.0-0
Source: librest Version: 0.9.1-2 Severity: serious Tags: pending bookworm sid gir1.2-rest-1.0 is missing its automatic dependency on librest-1.0-0 I accidentally introduced this regression in 0.9.1-2. It's fixed by running the gir debhelper sequence. Thank you, Jeremy Bícha
Bug#1033714: at runtime, flanker tries to create files under /usr
Package: python3-flanker
Version: 0.9.14-3
Severity: serious
At runtime, flanker tries to create files under /usr but /usr is
read-only, see:
https://www.debian.org/doc/debian-policy/ch-opersys.html
https://www.debian.org/doc/packaging-manuals/fhs/fhs-3.0.html#purpose18
In python 3.9.2, run:
import flanker.addresslib.address
flanker.addresslib.address.parse('u...@example.com')
Note the permission denied errors:
Symbol 'mailbox_or_url_list' is unreachable
Symbol 'delim' is unreachable
Symbol 'mailbox_or_url' is unreachable
Symbol 'url' is unreachable
Couldn't create 'flanker.addresslib._parser.mailbox_parsetab'. [Errno
13] Permission denied:
'/usr/lib/python3/dist-packages/flanker/addresslib/_parser/mailbox_parsetab.py'
Symbol 'mailbox_or_url_list' is unreachable
Symbol 'delim' is unreachable
Symbol 'mailbox_or_url' is unreachable
Symbol 'mailbox' is unreachable
Symbol 'url' is unreachable
Symbol 'angle_addr' is unreachable
Symbol 'name_addr' is unreachable
Symbol 'phrase' is unreachable
Couldn't create 'flanker.addresslib._parser.addr_spec_parsetab'.
[Errno 13] Permission denied:
'/usr/lib/python3/dist-packages/flanker/addresslib/_parser/addr_spec_parsetab.py'
Symbol 'mailbox_or_url_list' is unreachable
Symbol 'delim' is unreachable
Symbol 'mailbox_or_url' is unreachable
Symbol 'mailbox' is unreachable
Symbol 'addr_spec' is unreachable
Symbol 'angle_addr' is unreachable
Symbol 'name_addr' is unreachable
Symbol 'phrase' is unreachable
Symbol 'local_part' is unreachable
Symbol 'domain' is unreachable
Symbol 'quoted_string' is unreachable
Symbol 'domain_literal' is unreachable
Symbol 'quoted_string_text' is unreachable
Symbol 'domain_literal_text' is unreachable
Couldn't create 'flanker.addresslib._parser.url_parsetab'. [Errno 13]
Permission denied:
'/usr/lib/python3/dist-packages/flanker/addresslib/_parser/url_parsetab.py'
Symbol 'mailbox_or_url_list' is unreachable
Symbol 'delim' is unreachable
Couldn't create 'flanker.addresslib._parser.mailbox_or_url_parsetab'.
[Errno 13] Permission denied:
'/usr/lib/python3/dist-packages/flanker/addresslib/_parser/mailbox_or_url_parsetab.py'
Couldn't create
'flanker.addresslib._parser.mailbox_or_url_list_parsetab'. [Errno 13]
Permission denied:
'/usr/lib/python3/dist-packages/flanker/addresslib/_parser/mailbox_or_url_list_parsetab.py'
These files should probably be generated from debian/rules and included
in the binary package.
Thanks,
Daniel Kauffman
Business Experience Designer
Rock Solid Solutions LLC
Bug#1033667: marked as done (verilator: Uninstallable in sid because of ${sphinxdoc:Built-Using} dependency)
Your message dated Thu, 30 Mar 2023 19:35:54 +
with message-id
and subject line Bug#1033667: fixed in verilator 5.006-3
has caused the Debian Bug report #1033667,
regarding verilator: Uninstallable in sid because of ${sphinxdoc:Built-Using}
dependency
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1033667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: verilator
Version: 5.006-2
Severity: serious
Tags: patch
Dear Maintainer,
In a clean sid chroot, verilator is not installable:
# apt install verilator
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
verilator : Depends: sphinx (= 5.3.0-3)
E: Unable to correct problems, you have held broken packages.
This is because that package has ${sphinxdoc:Built-Using} among its
dependencies.
That substitution variable is intended to be used in Built-Using field of
architecture-dependent packages, NOT in Depends field.
I have created a merge request [1] on salsa to fix this.
[1]: https://salsa.debian.org/electronics-team/verilator/-/merge_requests/3
--
Dmitry Shachnev
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: verilator
Source-Version: 5.006-3
Done: Carsten Schoenert
We believe that the bug you reported is fixed in the latest version of
verilator, 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 1033...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Carsten Schoenert (supplier of updated verilator
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, 30 Mar 2023 20:05:11 +0200
Source: verilator
Architecture: source
Version: 5.006-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Electronics Team
Changed-By: Carsten Schoenert
Closes: 1030913 1031711 1033667
Changes:
verilator (5.006-3) unstable; urgency=medium
.
* Team upload
[ Dmitry Shachnev ]
* [38e486b] Move ${sphinxdoc:Built-Using} to the correct field.
(Closes: #1033667)
.
[ Carsten Schoenert ]
* [975c120] d/gbp.conf: Adjust to debian/bookworm
* [e05438c] Rebuild patch queue from patch-queue branch
Added patches:
Fix-build-on-hppa.patch
Fix-date-on-the-front-page-of-verilator.pdf-3956-3957.patch
(Closes: #1030913, #1031711)
Checksums-Sha1:
30d25f23986c718b58ebcc1fbfafcf19a14d7dc0 2198 verilator_5.006-3.dsc
ade185287b052725f86c4ef8fce4514d8e792e1f 13424 verilator_5.006-3.debian.tar.xz
dbc42ce92872322f3d1a773145ef8966730c036f 9796 verilator_5.006-3_amd64.buildinfo
Checksums-Sha256:
70ccc8d6384d88bfd38a2261fd226932ccbff1ecb746f61b34f65e4ef93b14c8 2198
verilator_5.006-3.dsc
f7a7e14a3d8078db92504a9ead01806a47f99a4556b75edba997650805588ced 13424
verilator_5.006-3.debian.tar.xz
fbc1293081a9cf97ac277316c6a929915b88eff85b7f9d225147ee3c90dc9fcc 9796
verilator_5.006-3_amd64.buildinfo
Files:
c3aa7846392574b0dc4cb298e49867b4 2198 electronics optional
verilator_5.006-3.dsc
761b1e5e9b6e3c94b8afff31e567eccd 13424 electronics optional
verilator_5.006-3.debian.tar.xz
f12aa16ff51bf1f8d543f2c22b58a443 9796 electronics optional
verilator_5.006-3_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEtw38bxNP7PwBHmKqgwFgFCUdHbAFAmQl32MACgkQgwFgFCUd
HbAgwA//fxKZ/kvI2PgFTr5LjRG7/xtmW6NCsNDbJwlN7RwhKoO/cV6JrcKCtiql
LuV2R0UAUZab5oMPfFuiSiQrF36+KBWCgsyM9vKDvrgVN70kgZt0UaUNd3/pbCUf
4HKdTyhktpM23jVSlkwQMgK33xN5xDT7dF8M0rROxooyPS+a8SdZRGuDEk/zNRo4
nMcUacsr4YV/Q+KrDwE1zTLpsaTWSKMPIa3wGw42vi5V0WrVKB8moKJyJTbPolZo
S1GRmU57JJUoFwzdNnC3fIvxSF+cqTyAduw6jQ4w+8LAhbvRCPYju+aAzeA4FDGj
gYropztcO3LaK3/Bs3xluUKMZCs6zyxgBBgHjlXp2R5mOQE5RSisDfHPPBMgvlTf
QamcMZjLCeOL4j1go/bAV2xPwrPuWkyJEiDhV3inXhAPC0eGE3OYEmIP77SKPalU
Processed: kore: autopkgtest regression: Killing leaked background processes
Processing control commands: > tags -1 bookworm-ignore Bug #1033711 [src:kore] kore: autopkgtest regression: Killing leaked background processes Added tag(s) bookworm-ignore. -- 1033711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033711: kore: autopkgtest regression: Killing leaked background processes
Source: kore Version: 4.1.0-6 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails since May 2022. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore, although from the log I'm not sure this doesn't hint at serious issues. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/k/kore/32029176/log.gz autopkgtest [09:24:03]: test myapp-clang: [--- created myapp/src/myapp.c created myapp/conf/myapp.conf created myapp/conf/build.conf created myapp/.gitignore created dh2048.pem myapp created successfully! WARNING: DO NOT USE THE GENERATED DH PARAMETERS AND CERTIFICATES IN PRODUCTION active flavordev output type dso kore binary /usr/bin/kore kore features-DKORE_USE_PGSQL -DKORE_USE_TASKS -I/usr/include/postgresql /tmp/autopkgtest-lxc.5m5g54p3/downtmp/wrapper.sh: Killing leaked background processes: 1562 1566 1572 1573 1574 PID TTY STAT TIME COMMAND 1562 ?S 0:00 timeout --preserve-status -k 60s -s SIGQUIT 60s kodev run 1566 ?S 0:00 kore [parent] 1572 ?S 0:00 kore [wrk 1] 1573 ?S 0:00 kore [wrk 2] 1574 ?S 0:00 kore [keymgr] autopkgtest [09:24:15]: test myapp-clang: ---] OpenPGP_signature Description: OpenPGP digital signature
Processed: kel-agent: autopkgtest regression: panic: test timed out after 10m0s
Processing control commands: > tags -1 bookworm-ignore Bug #1033710 [src:kel-agent] kel-agent: autopkgtest regression: panic: test timed out after 10m0s Added tag(s) bookworm-ignore. -- 1033710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033710: kel-agent: autopkgtest regression: panic: test timed out after 10m0s
Source: kel-agent
Version: 0.4.6-2
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package has an autopkgtest, great. However, it fails since June
2022, which aligns roughly with the upload of version 0.4.6-1. It seems
that 0.4.6-2 was alowed to migrate because version 0.2.2-1 regressed in
testing at the same time. Can you please investigate the situation and
fix it? I copied some of the output at the bottom of this report. I note
that I see the following in the build logs:
"""
suite_test.go:29: These integration tests freeze when building in
sbuild chroot
--- SKIP: TestIntegrationSuite (0.00s)
"""
so it might be that the "solution" for building has to be applied for
autopkgtesting as well.
The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing. [Release Team member hat on] Because
we're currently in the hard freeze for bookworm, I have marked this bug
as bookworm-ignore. Targeted fixes are still welcome.
More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html
https://ci.debian.net/data/autopkgtest/testing/amd64/k/kel-agent/32233832/log.gz
make[1]: Leaving directory
'/tmp/autopkgtest-lxc.m1xmj9qe/downtmp/autopkgtest_tmp'
dh_auto_test -O--builddirectory=_build -O--buildsystem=golang
cd _build && go test -vet=off -v -p 64 github.com/k0swe/kel-agent
github.com/k0swe/kel-agent/integration
github.com/k0swe/kel-agent/internal/config
github.com/k0swe/kel-agent/internal/ws
github.com/k0swe/kel-agent/internal/wsjtx_wrapper
? github.com/k0swe/kel-agent [no test files]
=== RUN TestIntegrationSuite
=== RUN TestIntegrationSuite/TestReceive
wsjtx-fake.go:28: fake is connected to 127.0.0.1:2237
suite_test.go:65: suite reports fake is connected
=== RUN TestIntegrationSuite/TestReceive/clear
=== CONT TestIntegrationSuite/TestReceive
wsjtx-fake.go:37: sending message
wsjtx-fake.go:43: listening for receives
panic: test timed out after 10m0s
goroutine 19 [running]:
testing.(*M).startAlarm.func1()
/usr/lib/go-1.19/src/testing/testing.go:2036 +0x8e
created by time.goFunc
/usr/lib/go-1.19/src/time/sleep.go:176 +0x32
goroutine 1 [chan receive, 9 minutes]:
testing.(*T).Run(0xc00013e820, {0x8c7845?, 0x50e005?}, 0x8fb620)
/usr/lib/go-1.19/src/testing/testing.go:1494 +0x37a
testing.runTests.func1(0xc00011d440?)
/usr/lib/go-1.19/src/testing/testing.go:1846 +0x6e
testing.tRunner(0xc00013e820, 0xc00014fcd8)
/usr/lib/go-1.19/src/testing/testing.go:1446 +0x10b
testing.runTests(0xc01220?, {0xbfb9a0, 0x1, 0x1}, {0x7f83d4d14108?,
0x40?, 0xc0a020?})
/usr/lib/go-1.19/src/testing/testing.go:1844 +0x456
testing.(*M).Run(0xc01220)
/usr/lib/go-1.19/src/testing/testing.go:1726 +0x5d9
main.main()
_testmain.go:47 +0x1aa
goroutine 6 [chan receive, 9 minutes]:
testing.(*T).Run(0xc00013e9c0, {0x8181fa?, 0xc00013e9c0?}, 0xc00025c000)
/usr/lib/go-1.19/src/testing/testing.go:1494 +0x37a
github.com/stretchr/testify/suite.runTests({0x978da0, 0xc00013e9c0},
{0xc12a98?, 0x1, 0x1})
/tmp/autopkgtest-lxc.m1xmj9qe/downtmp/autopkgtest_tmp/_build/src/github.com/stretchr/testify/suite/suite.go:220
+0x128
github.com/stretchr/testify/suite.Run(0xc00013e9c0, {0x974878,
0xc00011f450})
/tmp/autopkgtest-lxc.m1xmj9qe/downtmp/autopkgtest_tmp/_build/src/github.com/stretchr/testify/suite/suite.go:193
+0x6e5
github.com/k0swe/kel-agent/integration.TestIntegrationSuite(0xc00013e9c0)
/tmp/autopkgtest-lxc.m1xmj9qe/downtmp/autopkgtest_tmp/_build/src/github.com/k0swe/kel-agent/integration/suite_test.go:31
+0x8a
testing.tRunner(0xc00013e9c0, 0x8fb620)
/usr/lib/go-1.19/src/testing/testing.go:1446 +0x10b
created by testing.(*T).Run
/usr/lib/go-1.19/src/testing/testing.go:1493 +0x35f
goroutine 7 [select, 9 minutes]:
github.com/k0swe/kel-agent/internal/wsjtx_wrapper.(*Handler).ListenToWsjtx(0xc000244460,
0x8fb620?)
/tmp/autopkgtest-lxc.m1xmj9qe/downtmp/autopkgtest_tmp/_build/src/github.com/k0swe/kel-agent/internal/wsjtx_wrapper/wsjtx.go:53
+0x1a9
created by github.com/k0swe/kel-agent/internal/ws.newHub
/tmp/autopkgtest-lxc.m1xmj9qe/downtmp/autopkgtest_tmp/_build/src/github.com/k0swe/kel-agent/internal/ws/hub.go:54
+0x17b
goroutine 8 [select, 9 minutes]:
github.com/k0swe/kel-agent/internal/ws.(*Hub).run(0xc0001098c0)
/tmp/autopkgtest-lxc.m1xmj9qe/downtmp/autopkgtest_tmp/_build/src/github.com/k0swe/kel-agent/internal/ws/hub.go:71
+0x12f
created by github.com/k0swe/kel-agent/internal/ws.Start
/tmp/autopkgtest-lxc.m1xmj9qe/downtmp/autopkgtest_tmp/_build/src/github.com/k0swe/kel-agent/internal/ws/server.go:27
+0x14a
goroutine 9 [IO
Bug#1033602: marked as done (nvidia-graphics-drivers: dh_missing finds missing files and I think it is my fault)
Your message dated Thu, 30 Mar 2023 18:43:28 + with message-id and subject line Bug#1033602: fixed in nvidia-graphics-drivers 530.41.03-1 has caused the Debian Bug report #1033602, regarding nvidia-graphics-drivers: dh_missing finds missing files and I think it is my fault 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.) -- 1033602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers Version: 530.41.03 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, I am trying to debuild nvidia-graphics drivers 530.41.03 (since I would love to test the new 6.3.x kernels and I have read that the new version supports those, I'd love to see if it is true) I tried to follow the README.sources included in the git Since I could not find the instruction to debuild the code I tried to use debuild -us -uc as usual Sadly at the end of the process dh_missing finds missing files (I'd like to know how those can be included in the build) The outcome I am expecting is to have the 530.41.03 dkms, bins, libs, debs ... etc, so I can test I am mainly blaming myself, and I would be grateful if you can give me a hint about what am I missing. Thanks in advance for your time and effort. p.s. queue the boring error log make[2]: Leaving directory '/usr/src/nvidia/nvidia-graphics-drivers' dh_lintian dh_perl dh_link dh_compress dh_fixperms dh_missing dh_missing: warning: kernel-open/Kbuild exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/kernel/Kbuild") dh_missing: warning: kernel-open/Makefile exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/kernel/Makefile") dh_missing: warning: kernel-open/common/inc/conftest.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/cpuopsys.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-caps.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-dmabuf.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-firmware.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-gpu-info.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-hash.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-hypervisor.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-ioctl-numa.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-ioctl-numbers.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-ioctl.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-kernel-interface-api.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-kref.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-kthread-q.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-linux.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-list-helpers.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-lock.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-memdbg.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-mm.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-modeset-interface.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-msi.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-pci-types.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-pci.h exists in debian/tmp but is not installed to anywhere dh_missing: warning: kernel-open/common/inc/nv-pgprot.h exists in debian/tmp but is not
Bug#1033636: swi-prolog ships shared libraries, breaks partial upgrades
Control: tags -1 + patch
On 2023-03-29 08:50 -0700, Steve Langasek wrote:
> On Wed, Mar 29, 2023 at 03:45:26PM +0500, Lev Lamberov wrote:
>> Thanks for reporting!
>
>> I've tagged this bug report with 'help'. I'm a bit overwhelmed at the
>> moment and don't think I will have time for it or any other Debian stuff
>> in the coming weeks. NMU is most welcome.
>
> Afraid I don't have capacity to help with this either. I've applied a
> quick-stop fix to Ubuntu to have swi-prolog-core declare Breaks: against
> older incompatible versions of logol - and also libppl-swi, which turns out
> to also be affected. Doing the same in Debian may be enough for the current
> release, but it's good to not lose sight of a long-term fix since there are
> bound to be other SONAME changes in the future.
If only the Breaks are added, the situation will resurface as soon as
libswipl.so.10 comes along. To prevent this from happening, I have
attached a minimal fix that provides the libswipl9 virtual package and a
shlibs file. Rebuilding logol-bin then made it depend on libswipl9 as
desired. The second patch adds the necessary Breaks (ppl actually needs
a binNMU, its version in bookworm is the same as in bullseye).
I think that libswipl9 should be split into its own package after the
bookworm release, the freeze policy forbids doing that now.
Cheers,
Sven
From b9d119873ed8d7fa891bce356cffe4432c82f517 Mon Sep 17 00:00:00 2001
From: Sven Joachim
Date: Thu, 30 Mar 2023 19:29:55 +0200
Subject: [PATCH 1/2] Provide a virtual libswipl9 package in swi-prolog-core
Provide the libswipl9 virtual package and ship a minimal shlibs file
to ensure that reverse dependencies pick up the dependency on
libswipl9 rather than swi-prolog-core.
Closes: #1033636
---
debian/control| 3 ++-
debian/swi-prolog-core.shlibs | 1 +
2 files changed, 3 insertions(+), 1 deletion(-)
create mode 100644 debian/swi-prolog-core.shlibs
diff --git a/debian/control b/debian/control
index eb2b7309..ed7a4d28 100644
--- a/debian/control
+++ b/debian/control
@@ -104,7 +104,8 @@ Provides: swi-prolog-abi-${swi-prolog:ABI},
swi-prolog-abi-foreign-${swi-prolog:FABI},
swi-prolog-abi-binary-${swi-prolog:BABI},
swi-prolog-abi-qlf-${swi-prolog:QLF},
- swi-prolog-abi-states-${swi-prolog:SSTATES}
+ swi-prolog-abi-states-${swi-prolog:SSTATES},
+ libswipl9
Description: ISO/Edinburgh-style Prolog interpreter - core system
SWI-Prolog is a fast and powerful ISO/Edinburgh-style Prolog compiler with a
rich set of built-in predicates. It offers a fast, robust and small
diff --git a/debian/swi-prolog-core.shlibs b/debian/swi-prolog-core.shlibs
new file mode 100644
index ..6251db33
--- /dev/null
+++ b/debian/swi-prolog-core.shlibs
@@ -0,0 +1 @@
+libswipl 9 libswipl9
--
2.40.0
From 4ed85ac59ee892ed199da19f0d9dd0874e31a05f Mon Sep 17 00:00:00 2001
From: Sven Joachim
Date: Thu, 30 Mar 2023 19:31:40 +0200
Subject: [PATCH 2/2] Add Versioned Breaks against logol-bin and libppl-swi
Older versions of these packages were linked against libswipl.so.8
rather than libswipl.so.9 and will stop working after swi-prolog-core
has been upgraded.
Note that libppl-swi actually has not been rebuilt yet.
---
debian/control | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/debian/control b/debian/control
index ed7a4d28..fce48eb2 100644
--- a/debian/control
+++ b/debian/control
@@ -98,7 +98,9 @@ Suggests: elpa-ediprolog,
swi-prolog-java (= ${binary:Version}),
swi-prolog-odbc (= ${binary:Version}),
swi-prolog-bdb (= ${binary:Version})
-Breaks: swi-prolog-nox (<< 8.1.30+dfsg-1)
+Breaks: swi-prolog-nox (<< 8.1.30+dfsg-1),
+logol-bin (<< 1.7.9+dfsg-6),
+libppl-swi (<< 1:1.2-8.1+b1)
Replaces: swi-prolog-nox (<< 8.1.30+dfsg-1)
Provides: swi-prolog-abi-${swi-prolog:ABI},
swi-prolog-abi-foreign-${swi-prolog:FABI},
--
2.40.0
Processed: Re: Bug#1033636: swi-prolog ships shared libraries, breaks partial upgrades
Processing control commands: > tags -1 + patch Bug #1033636 [src:swi-prolog] swi-prolog ships shared libraries, breaks partial upgrades Added tag(s) patch. -- 1033636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033636 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: golang-gitaly-proto: autopkgtest regression: test dependency ruby-gitaly-proto doesn't exist
Processing control commands: > tags -1 bookworm-ignore Bug #1033705 [src:golang-gitaly-proto] golang-gitaly-proto: autopkgtest regression: test dependency ruby-gitaly-proto doesn't exist Added tag(s) bookworm-ignore. -- 1033705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033705 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033705: golang-gitaly-proto: autopkgtest regression: test dependency ruby-gitaly-proto doesn't exist
Source: golang-gitaly-proto Version: 1.37.0+dfsg-1 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), Your package has an autopkgtest, great. However, it fails since September 2020. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-gitaly-proto/32182231/log.gz autopkgtest [15:18:15]: test command1: preparing testbed Reading package lists... Building dependency tree... Reading state information... Correcting dependencies...Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) autopkgtest-satdep:amd64 < 0 @iU K Nb Ib > Broken autopkgtest-satdep:amd64 Depends on ruby-gitaly-proto:amd64 < none @un H > Removing autopkgtest-satdep:amd64 because I can't find ruby-gitaly-proto:amd64 Done Done OpenPGP_signature Description: OpenPGP digital signature
Bug#1033703: gffread: autopkgtest regression: test dependency not in testing
Source: gffread Version: 0.12.7-3 Severity: serious Control: tags -1 bookworm User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails in testing since trinityrnaseq-examples was removed on 2022-04-05. Can you please investigate the situation and fix it? The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze, I've marked this bug as bookworm-ignore, but targeted fixes are welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html OpenPGP_signature Description: OpenPGP digital signature
Processed: gffread: autopkgtest regression: test dependency not in testing
Processing control commands: > tags -1 bookworm Bug #1033703 [src:gffread] gffread: autopkgtest regression: test dependency not in testing Added tag(s) bookworm. -- 1033703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: freefem++: autopkgtest regression: warnings on stderr
Processing control commands: > tags -1 bookworm-ignore Bug #1033702 [src:freefem++] freefem++: autopkgtest regression: warnings on stderr Added tag(s) bookworm-ignore. -- 1033702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033702 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > fixed 1004253 0.5.0-1 Bug #1004253 [prometheus-bind-exporter] broken for BIND in stable Marked as fixed in versions prometheus-bind-exporter/0.5.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1004253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004253 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033702: freefem++: autopkgtest regression: warnings on stderr
Source: freefem++ Version: 4.11+dfsg1-2 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), Your package has an autopkgtest, great. However, it started to fail in August 2022 on amd64, armhf and i386. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team hat on] Because of the timing (we're in hard freeze) I've marked this bug as bookworm-ignore as the problem is "only" warnings. A targeted fix is still welcome (adding allow-stderr restriction for the test, code fixing needs to wait until the release). More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/f/freefem++/32183287/log.gz build-and-run-libFAIL stderr: In file included from /usr/include/freefem++/AFunction.hpp:93, autopkgtest [16:24:09]: test build-and-run-lib: - - - - - - - - - - stderr - - - - - - - - - - In file included from /usr/include/freefem++/AFunction.hpp:93, from /usr/include/freefem++/ff++.hpp:21, from /tmp/autopkgtest-lxc.okwz3yij/downtmp/build.NQ2/src/plugin/seq/myfunction.cpp:30: /usr/include/freefem++/String.hpp:195:19: warning: ‘template_Arg1, class _Arg2, class _Result> struct std::binary_function’ is deprecated [-Wdeprecated-declarations] 195 | struct pairless : binary_function,const char *, bool> | ^~~ In file included from /usr/include/c++/12/string:48, from /usr/include/c++/12/bits/locale_classes.h:40, from /usr/include/c++/12/bits/ios_base.h:41, from /usr/include/c++/12/ios:42, from /usr/include/c++/12/istream:38, from /usr/include/c++/12/fstream:38, from /usr/include/freefem++/ff++.hpp:12: /usr/include/c++/12/bits/stl_function.h:131:12: note: declared here 131 | struct binary_function |^~~ OpenPGP_signature Description: OpenPGP digital signature
Processed (with 4 errors): your mail
Processing commands for cont...@bugs.debian.org:
> reopen 1004253
Bug #1004253 {Done: Guillem Jover }
[prometheus-bind-exporter] broken for BIND in stable
'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 0.5.0-1.
> fixed 0.5.0-1
Unknown command or malformed arguments to command.
> Re-opening prematurely-done bug since the fixed version has not been
Unknown command or malformed arguments to command.
> backported to bullseye (yet), and this bug is quite clear that it
Unknown command or malformed arguments to command.
> affects stable (bullseye, as of writing this).
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1004253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1033701: frama-c: autopkgtest regression: cannot load plug-in 'why3'
Source: frama-c Version: 20220511-manganese-3 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it started to fail everywhere except on armel recently (February/March 2023). Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/f/frama-c/32265125/log.gz autopkgtest [06:15:54]: test eva: [--- [kernel] User Error: cannot load plug-in 'why3': cannot load module Details: implementation mismatch on Dynlink [kernel] User Error: cannot load plug-in 'frama-c-wp': cannot load module Details: no implementation available for Why3 [kernel] User Error: Deferred error message was emitted during execution. See above messages for more information. [kernel] Frama-C aborted: invalid user input. autopkgtest [06:15:54]: test eva: ---] OpenPGP_signature Description: OpenPGP digital signature
Bug#1032539: lnav: FTBFS in testing: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Hi
On Fri, Mar 17, 2023 at 09:03:12PM +0100, Salvatore Bonaccorso wrote:
> Control: tags -1 + help
>
> On Sat, Mar 11, 2023 at 08:38:17AM +0100, Lucas Nussbaum wrote:
> > Hi,
> >
> > On 10/03/23 at 23:25 +, Samuel Henrique wrote:
> > > Hello Daniel
> > >
> > > > > I couldn't find anything in the release notes which look like a
> > > > > breaking change[0]
> > > >
> > > > Lots of people and CI systems run all the tests flawlessly all the
> > > > time, so
> > > > there is reason to suspect that there is something slightly unusual in
> > > > your
> > > > test setup that causes these problems. Meaning that I suspect this is
> > > > not a
> > > > curl problem, this is a curl test problem.
> > > >
> > > > Are these problems different or the same as the ones already filed at
> > > > https://github.com/curl/curl/issues/10682 ?
> > >
> > > I think it's a different issue, we have good evidence that those
> > > failures are triggered by an IPv6-only host and I acknowledge your
> > > solution to document that tests require IPv4 support for now.
> > >
> > > Salvatore can double check but the build logs indicate that the host
> > > used to build lnav had an IPv4 address.
> > >
> > > I also don't think lnav is running any of the curl's tests, but rather
> > > making use of the curl library to run their tests, which leads me to
> > > believe that whatever issue it is, it has to be something very
> > > specific and uncommon (and not related to curl's tests), otherwise
> > > there would be more reports.
> > >
> > > By the way I should have replied on that issue just in case: but feel
> > > free to close it if you'd like to track IPv6-only support somewhere
> > > else, or to rename it if you'd like to use it to track support for
> > > that. Me and sergiodj are thinking about giving it a try at solving
> > > that but we're not sure when (in the packaging, for now, we are
> > > ignoring those test results).
> > >
> > > Me and sergiodj are also currently investigating a test issue related
> > > to ppc64el, we have got some good insights already, but would like to
> > > fully understand what's going on and have a patch ready before
> > > reporting. Also that issue only affects curl's own tests so it can't
> > > be related to this.
> > >
> > > Cheers,
> >
> > Regarding the issue I reported in this bug:
> >
> > This triggers on a host with both IPv4 and IPv6.
> >
> > With curl 7.88.1-6, both tests test_sql_fs_func.sh and test_sql_fs_func.sh
> > fail
> >
> > With curl 7.87.0-2, test_sql_fs_func.sh fails and test_sql_str_func.sh
> > passes
> >
> >
> >
> > The failure for test_sql_str_func.sh with version 7.88.1-6 is:
> >
> > Command: test: env TEST_COMMENT=invalid_url ./drive_sql
> > BEGIN test_sql_str_func.sh_3855d2cc0ab29171cae8e722f130adec25eae36e.out
> > END test_sql_str_func.sh_3855d2cc0ab29171cae8e722f130adec25eae36e.out
> > BEGIN test_sql_str_func.sh_3855d2cc0ab29171cae8e722f130adec25eae36e.err
> > error: sqlite3_exec failed --
> > lnav-error:{"level":"error","message":{"str":"invalid URL:
> > ???https://bad@[fe::???","attrs":[]},"reason":{"str":"Bad IPv6
> > address","attrs":[]},"snippets":[],"help":{"str":"","attrs":[]}}
> > END test_sql_str_func.sh_3855d2cc0ab29171cae8e722f130adec25eae36e.err
> > ERR: test: env TEST_COMMENT=invalid_url ./drive_sql
> > ---
> > /root/lnav-0.11.1/test/expected/test_sql_str_func.sh_3855d2cc0ab29171cae8e722f130adec25eae36e.err
> >2022-10-11 03:12:58.0 +
> > +++ test_sql_str_func.sh_3855d2cc0ab29171cae8e722f130adec25eae36e.err
> > 2023-03-11 07:27:53.862049124 +
> > @@ -1 +1 @@
> > -error: sqlite3_exec failed --
> > lnav-error:{"level":"error","message":{"str":"invalid URL:
> > ???https://bad@[fe::???","attrs":[]},"reason":{"str":"Port number was not a
> > decimal number between 0 and
> > 65535","attrs":[]},"snippets":[],"help":{"str":"","attrs":[]}}
> > +error: sqlite3_exec failed --
> > lnav-error:{"level":"error","message":{"str":"invalid URL:
> > ???https://bad@[fe::???","attrs":[]},"reason":{"str":"Bad IPv6
> > address","attrs":[]},"snippets":[],"help":{"str":"","attrs":[]}}
> > FAIL! EXPECTED ERR DIFF
> >
> > The failure for test_sql_fs_func.sh is:
> >
> > Command: test: ./drive_sql select joinpath('foo', 'bar', 'baz', '/root')
> > BEGIN test_sql_fs_func.sh_73df81c6889d1f06fb3f3b6bf30c6046b3f52c8b.out
> > Row 0:
> > Column joinpath('foo', 'bar', 'baz', '{top_srcdir_parent}'):
> > {top_srcdir_parent}
> > END test_sql_fs_func.sh_73df81c6889d1f06fb3f3b6bf30c6046b3f52c8b.out
> > OUT: test: ./drive_sql select joinpath('foo', 'bar', 'baz', '/root')
> > ---
> > /root/lnav-0.11.1/test/expected/test_sql_fs_func.sh_73df81c6889d1f06fb3f3b6bf30c6046b3f52c8b.out
> > 2022-10-11 03:12:58.0 +
> > +++ test_sql_fs_func.sh_73df81c6889d1f06fb3f3b6bf30c6046b3f52c8b.out
> > 2023-03-11 07:26:52.144915467 +
> > @@ -1,2 +1,2 @@
> > Row 0:
> > - Column joinpath('foo', 'bar', 'baz', '/root'): /root
> >
Bug#1032032: FTBFS: error: AM_INIT_AUTOMAKE expanded multiple times
Dear maintainers, could someone of you please prepare a new version of fenix-plugins with my patch added to save it from being auto-removed. Without any feedback until next week, I also could provide a NMU to Debian Mentors. But even then I will need a sponsor who will upload the changes to Debian unstable. Best regards, Thomas Uhle
Processed: tagging 1032930
Processing commands for cont...@bugs.debian.org:
> tags 1032930 + experimental
Bug #1032930 {Done: Christoph Berg } [src:libnest2d] pynest2d:
FTBFS with cmake 3.25: Libnest2D could not be found because dependency clipper
could not be found.
Added tag(s) experimental.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1032930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1033699: fpga-icestorm: autopkgtest regression: icetime: No such file or directory
Source: fpga-icestorm Version: 0~20220915gita545498-3 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), Your package has an autopkgtest, great. However, it fails since about November 2022, which seems to coincide with the upload of version 0~20220915gita545498-3. It seems that the package was allowed to migrate because the test was flaky before. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because of the timing with respect to the freeze, I've marked this bug as bookworm-ignore, although a targeted fix is still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/f/fpga-icestorm/32086800/log.gz Info: Program finished normally. icetime -d hx8k -mtr example.rpt example.asc make: icetime: No such file or directory make: *** [Makefile:18: example.rpt] Error 127 make: Leaving directory '/tmp/autopkgtest-lxc.l0ba3eev/downtmp/build.geY/src/examples/hx8kboard' autopkgtest [09:28:34]: test examples-compile: ---] OpenPGP_signature Description: OpenPGP digital signature
Processed: fpga-icestorm: autopkgtest regression: icetime: No such file or directory
Processing control commands: > tags -1 bookworm-ignore Bug #1033699 [src:fpga-icestorm] fpga-icestorm: autopkgtest regression: icetime: No such file or directory Added tag(s) bookworm-ignore. -- 1033699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> tags 1004253 bullseye
Bug #1004253 {Done: Guillem Jover }
[prometheus-bind-exporter] broken for BIND in stable
Added tag(s) bullseye.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1004253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: fonts-rit-sundar: autopkgtest fails: output on stderr: Program root: /usr
Processing control commands: > tags -1 bookworm-ignore Bug #1033698 [src:fonts-rit-sundar] fonts-rit-sundar: autopkgtest fails: output on stderr: Program root: /usr Added tag(s) bookworm-ignore. -- 1033698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033698 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033698: fonts-rit-sundar: autopkgtest fails: output on stderr: Program root: /usr
Source: fonts-rit-sundar Version: 2.0.0+20170909-2 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it recently started to fail (January/February 2023). Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. I suspect it's related to the /usr-merge changes. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because of the timing in the release (we're in hard freeze) and because the test itself still passes and there's only additional output on stderr, I tagged the bug as bookworm-ignore. A targeted fix is still appropriate. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/f/fonts-rit-sundar/32247687/log.gz autopkgtest [10:20:47]: test command1: [--- Program root: /usr Generating RIT-Sundar.sfd => RIT-Sundar.ttf Testing font RIT-Sundar autopkgtest [10:20:49]: test command1: ---] OpenPGP_signature Description: OpenPGP digital signature
Bug#1033697: flycheck: autopkgtest fails: trampoline file does not exists
Source: flycheck
Version: 32~git.20200527.9c435db3-3
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package has an autopkgtest, great. However, it fails since January
2023. Can you please investigate the situation and fix it? I copied some
of the output at the bottom of this report.
The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing.
More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html
https://ci.debian.net/data/autopkgtest/testing/amd64/f/flycheck/32470842/log.gz
[31mUtilities flycheck-buffer-saved-p considers an unmodified buffer
with backing file saved[0m
Traceback (most recent call last):
spy-on(buffer-file-name :and-return-value "test-buffer-name")
buttercup--spy-on-and-call-replacement(buffer-file-name (lambda
( arg...
comp-subr-trampoline-install(buffer-file-name)
comp-trampoline-search(buffer-file-name)
native-elisp-load("/home/debci/.emacs.d/eln-cache/28.2-ffd0c654/subr--tram...
error: (native-lisp-load-failed "file does not exists"
"/home/debci/.emacs.d/eln-cache/28.2-ffd0c654/subr--trampoline-627565722d66696c652d6e616d65_buffer_file_name_0.eln")
[31mUtilities flycheck-buffer-saved-p considers a modified buffer with
backing file unsaved[0m
Traceback (most recent call last):
spy-on(buffer-file-name :and-return-value "test-buffer-name")
buttercup--spy-on-and-call-replacement(buffer-file-name (lambda
( arg...
comp-subr-trampoline-install(buffer-file-name)
comp-trampoline-search(buffer-file-name)
native-elisp-load("/home/debci/.emacs.d/eln-cache/28.2-ffd0c654/subr--tram...
error: (native-lisp-load-failed "file does not exists"
"/home/debci/.emacs.d/eln-cache/28.2-ffd0c654/subr--trampoline-627565722d66696c652d6e616d65_buffer_file_name_0.eln")
Ran 109 out of 110 specs, 2 failed, in 389.98ms.
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1033692: marked as done (ikiwiki-hosting-web: `ikisite backup` regressed with Debian 12 git version)
Your message dated Thu, 30 Mar 2023 10:48:56 + with message-id and subject line Bug#1033692: fixed in ikiwiki-hosting 0.20220716-2 has caused the Debian Bug report #1033692, regarding ikiwiki-hosting-web: `ikisite backup` regressed with Debian 12 git version 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.) -- 1033692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ikiwiki-hosting-web Version: 0.20220716-1 Severity: serious Tags: patch pending upstream Forwarded: https://ikiwiki-hosting.branchable.com/bugs/ikisite_backup_fails_on_Debian_12___40__git_2.39.2__41__/ After upgrading a server with ikiwiki-hosting to the Debian 12 prerelease, the cron job that runs `ikisite backup` no longer works. Minimal reproducer: # ikisite backup mysite.example.com --filename=/dev/null fatal: Need a repository to create a bundle. error: git failed I think this is because git now distrusts directories not owned by the current user. The solution seems to be to switch uid to the site's owning user before generating the backup's git bundle. I proposed a fix upstream already. smcv --- End Message --- --- Begin Message --- Source: ikiwiki-hosting Source-Version: 0.20220716-2 Done: Simon McVittie We believe that the bug you reported is fixed in the latest version of ikiwiki-hosting, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated ikiwiki-hosting 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: Thu, 30 Mar 2023 10:56:12 +0100 Source: ikiwiki-hosting Architecture: source Version: 0.20220716-2 Distribution: unstable Urgency: medium Maintainer: Simon McVittie Changed-By: Simon McVittie Closes: 1033692 Changes: ikiwiki-hosting (0.20220716-2) unstable; urgency=medium . * d/p/ikisite-backup-Create-the-bundle-as-the-site-s-user.patch: Add patch fixing `ikisite backup` with bookworm's git version (Closes: #1033692) - d/tests/create-delete: Add a regression test for `ikisite backup`, among other subcommands * d/p/ikiwiki-hosting.conf-Indicate-that-systemd-unit-needs-to-.patch: Mark patch as forwarded * d/control: Add missing dependency on rsync, detected by this version's additional test coverage Checksums-Sha1: e1e343677fd57654111ab8a65b6278ae209f27e1 2334 ikiwiki-hosting_0.20220716-2.dsc 028c33f0c35f5f9b52d00fc94ee803e5362b1286 22524 ikiwiki-hosting_0.20220716-2.debian.tar.xz dd9d22133c954680c42b66f7334d523f904df115 6082 ikiwiki-hosting_0.20220716-2_source.buildinfo Checksums-Sha256: cf29d70ad0d260cde25dc405ee32d76ea97ea7d812d8265336248114973fca94 2334 ikiwiki-hosting_0.20220716-2.dsc 55b192d06faf5ef06d63bee71fbffbd075071e14a5c6c6c0f2346abf21d8437e 22524 ikiwiki-hosting_0.20220716-2.debian.tar.xz 6bf455a48dbb0d0644160f8951106f13fe2d5ea004aa8b93d54707631e30a6e0 6082 ikiwiki-hosting_0.20220716-2_source.buildinfo Files: 745c91606a9a6a5fc30e897faa30e843 2334 admin optional ikiwiki-hosting_0.20220716-2.dsc b161da229ce575bbad9f625ffbc099ed 22524 admin optional ikiwiki-hosting_0.20220716-2.debian.tar.xz e0701be83c3486793b38bfc229ae2faa 6082 admin optional ikiwiki-hosting_0.20220716-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmQlZegACgkQ4FrhR4+B TE85BhAAnOeDNeT6mltuLPLTDq6A4ypeMt63A1avFW+f0RXmCxvKsqUavl4WBvZW Pr4hbVx4phPe+5YEcmCXbznTfG/IrtX7n7zVBq9S78q8rI7ams8PmeUuIOjOLswR g/RvbQL4wD/CIsqqXKpMvINVoSR4LbvsgDhn17NmikMV8HzrhGtvUrbSd69EUP0I zo8lDjvXVor40QRtnetWXKkii3EARr0RfKFSC0M2TghwPuQjYbeb9TtjzY+rjxNX 02Lg3xKecAI8r6kiIePjE2e8EQLmSUWjycAmaItoxvTzAZ9KpNyOWL0vbImHEWU6 guPx1/VhAYW3PeYadxJrQ64baMUNzA/P3UjcFmrphye3LdXcqX3R8td3JmQU3ODV TEf8N7bQ1sfErKjO+du8Y10xXFrPGB8sRGYaDk7lZChDS74QAp4Td09RjPC2jYyx Z49ee/wVVZUO155Hv9XzruGFYvKpKO0ul3FeGjkdNa0MAS4b9hOt+Rg3O2m7S+HX UGLbG9ECJNlzorNOToW2cuaNpsTt1zw2FsHPwyT5unVC86eQIrBHeuq1ef8RNiQ6 uypJdkcrq9nYnpc5+dN+poy7JVF+B19iEsDhLlBPCKOFRvp4s2jxwV7hiM80iwz4 C+pZFEXRgygAWN734ImR2sHMU7ioKVEtldZcRMJO/iOaoOBIHeo= =/edF -END
Bug#1033435: marked as done (cloud-sptheme: FTBFS in testing: Could not import extension cloud_sptheme.ext.autodoc_sections (exception: cannot import name 'Markup' from 'jinja2' (/usr/lib/python3/dist
Your message dated Thu, 30 Mar 2023 09:48:54 + with message-id and subject line Bug#1033435: fixed in cloud-sptheme 1.10.1.post20200504175005-6 has caused the Debian Bug report #1033435, regarding cloud-sptheme: FTBFS in testing: Could not import extension cloud_sptheme.ext.autodoc_sections (exception: cannot import name 'Markup' from 'jinja2' (/usr/lib/python3/dist-packages/jinja2/__init__.py)) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1033435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cloud-sptheme Version: 1.10.1.post20200504175005-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230323 ftbfs-bookworm Hi, During a rebuild of all packages in testing (bookworm), your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with python3,sphinxdoc --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 > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:240: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.11/build/cloud_sptheme > copying cloud_sptheme/make_helper.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme > copying cloud_sptheme/__init__.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme > copying cloud_sptheme/utils.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme > creating /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext > copying cloud_sptheme/ext/escaped_samp_literals.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext > copying cloud_sptheme/ext/autodoc_sections.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext > copying cloud_sptheme/ext/table_styling.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext > copying cloud_sptheme/ext/auto_redirect.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext > copying cloud_sptheme/ext/docfield_markup.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext > copying cloud_sptheme/ext/__init__.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext > copying cloud_sptheme/ext/relbar_toc.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext > copying cloud_sptheme/ext/autoattribute_search_bases.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext > copying cloud_sptheme/ext/page_only.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext > copying cloud_sptheme/ext/perpage.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext > copying cloud_sptheme/ext/index_styling.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext > copying cloud_sptheme/ext/issue_tracker.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext > copying cloud_sptheme/ext/allow_unreferenced_footnotes.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext > copying cloud_sptheme/ext/role_index.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext > copying cloud_sptheme/ext/relbar_links.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext > creating /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/tests > copying cloud_sptheme/tests/test_ext_relbar_toc.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/tests > copying cloud_sptheme/tests/__init__.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/tests > copying cloud_sptheme/tests/utils.py -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/tests > creating > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext/static > copying cloud_sptheme/ext/static/auto_redirect.css -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext/static > copying cloud_sptheme/ext/static/auto_redirect.html_t -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext/static > copying cloud_sptheme/ext/static/table_styling.css -> > /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext/static > I: pybuild pybuild:333: SPHINX_THEME="classic" http_proxy="127.0.0.1:9" > python3.11 -m sphinx -N -b html docs/ > /<>/debian/cloud-sptheme/docs/html > Running Sphinx v5.3.0 > > Extension error: > Could not import extension cloud_sptheme.ext.autodoc_sections (exception: > cannot import name 'Markup' from 'jinja2' > (/usr/lib/python3/dist-packages/jinja2/__init__.py)) > E: pybuild pybuild:388: build: plugin distutils failed with: exit code=2: > SPHINX_THEME="classic" http_proxy="127.0.0.1:9" python3.11 -m
Bug#1033435: marked as pending in cloud-sptheme
Control: tag -1 pending Hello, Bug #1033435 in cloud-sptheme 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/cloud-sptheme/-/commit/e74c45b08fc4840ddfdd08954e5267ff6b6b8747 Move from jinja2 to markupsafe (Closes: #1033435) (this message was generated automatically) -- Greetings https://bugs.debian.org/1033435
Processed: Bug#1033435 marked as pending in cloud-sptheme
Processing control commands: > tag -1 pending Bug #1033435 [src:cloud-sptheme] cloud-sptheme: FTBFS in testing: Could not import extension cloud_sptheme.ext.autodoc_sections (exception: cannot import name 'Markup' from 'jinja2' (/usr/lib/python3/dist-packages/jinja2/__init__.py)) Added tag(s) pending. -- 1033435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033692: ikiwiki-hosting-web: `ikisite backup` regressed with Debian 12 git version
Package: ikiwiki-hosting-web Version: 0.20220716-1 Severity: serious Tags: patch pending upstream Forwarded: https://ikiwiki-hosting.branchable.com/bugs/ikisite_backup_fails_on_Debian_12___40__git_2.39.2__41__/ After upgrading a server with ikiwiki-hosting to the Debian 12 prerelease, the cron job that runs `ikisite backup` no longer works. Minimal reproducer: # ikisite backup mysite.example.com --filename=/dev/null fatal: Need a repository to create a bundle. error: git failed I think this is because git now distrusts directories not owned by the current user. The solution seems to be to switch uid to the site's owning user before generating the backup's git bundle. I proposed a fix upstream already. smcv
Bug#1028780: python-libzim: FTBFS: libzim/libwrapper.h:161:29: error: ‘class zim::Archive’ has no member named ‘getMediaCount’
I suggest moving the zimlib experimental version to unstable so that python-libzim can migrate.
Bug#1033508: marked as done (refstack-client: autopkgtest regression: Invalid version: '0.0.0.02021.08.18.fa73ef2524')
Your message dated Thu, 30 Mar 2023 08:35:50 +
with message-id
and subject line Bug#1033508: fixed in refstack-client
0.0.0~2021.08.18.fa73ef2524-5
has caused the Debian Bug report #1033508,
regarding refstack-client: autopkgtest regression: Invalid version:
'0.0.0.02021.08.18.fa73ef2524'
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.)
--
1033508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: refstack-client
Version: 0.0.0~2021.08.18.fa73ef2524-4
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package has an autopkgtest, great. However, it recently (around
beginning of February 2023) started to fail in testing.
Paul
https://ci.debian.net/data/autopkgtest/testing/amd64/r/refstack-client/32427783/log.gz
Traceback (most recent call last):
File "/tmp/autopkgtest-lxc.zvo2tfw5/downtmp/build.pFl/src/setup.py",
line 27, in
setuptools.setup(
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line
108, in setup
return distutils.core.setup(**attrs)
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py",
line 185, in setup
return run_commands(dist)
^^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py",
line 201, in run_commands
dist.run_commands()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py",
line 969, in run_commands
self.run_command(cmd)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1213,
in run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py",
line 988, in run_command
cmd_obj.run()
File "/usr/lib/python3/dist-packages/pbr/packaging.py", line 243, in run
return du_install.install.run(self)
File
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/install.py",
line 698, in run
self.run_command('build')
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py",
line 318, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1213,
in run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py",
line 988, in run_command
cmd_obj.run()
File
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py",
line 132, in run
self.run_command(cmd_name)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py",
line 318, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1213,
in run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py",
line 988, in run_command
cmd_obj.run()
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py",
line 63, in run
self.build_package_data()
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py",
line 159, in build_package_data
for target, srcfile in self._get_package_data_output_mapping():
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py",
line 151, in _get_package_data_output_mapping
for package, src_dir, build_dir, filenames in self.data_files:
^^^
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py",
line 72, in __getattr__
self.data_files = self._get_data_files()
^^
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py",
line 84, in _get_data_files
self.analyze_manifest()
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py",
line 181, in analyze_manifest
self.run_command('egg_info')
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py",
line 318, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1213,
in run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py",
line 987, in run_command
cmd_obj.ensure_finalized()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py",
line 111, in ensure_finalized
self.finalize_options()
File "/usr/lib/python3/dist-packages/setuptools/command/egg_info.py",
line 219, in
Bug#1032930: closing 1032930
close 1032930 5.0.0-2 thanks libnest2d (5.0.0-2) unstable; urgency=medium * Patch incorrect package name in Findclipper.cmake. Closes: #1032930 -- Gregor Riepl Wed, 29 Mar 2023 02:12:38 +0200
Processed: closing 1032930
Processing commands for cont...@bugs.debian.org: > close 1032930 5.0.0-2 Bug #1032930 [src:libnest2d] pynest2d: FTBFS with cmake 3.25: Libnest2D could not be found because dependency clipper could not be found. Marked as fixed in versions libnest2d/5.0.0-2. Bug #1032930 [src:libnest2d] pynest2d: FTBFS with cmake 3.25: Libnest2D could not be found because dependency clipper could not be found. Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1032930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033667: verilator: Uninstallable in sid because of ${sphinxdoc:Built-Using} dependency
Hello Dimitry,
Am Wed, Mar 29, 2023 at 09:10:17PM +0300 schrieb Dmitry Shachnev:
> In a clean sid chroot, verilator is not installable:
...
> This is because that package has ${sphinxdoc:Built-Using} among its
> dependencies.
>
> That substitution variable is intended to be used in Built-Using field of
> architecture-dependent packages, NOT in Depends field.
>
> I have created a merge request [1] on salsa to fix this.
>
> [1]: https://salsa.debian.org/electronics-team/verilator/-/merge_requests/3
nice catch!
Thanks also for preparing a patch/MR on this!
I've to admit I haven't looked that much on th existing structure in
d/control while working on verilator weeks ago as the package could be
build successfully in the past.
Will have a look on this the next days!
Regards
Carsten
