Bug#1024830: ERROR: Unable to connect to servers to test latency.
Control: severity -1 important On Fri, 26 Jan 2024 11:46:15 +0100 Yves-Alexis Perez wrote: > On Sat, 26 Nov 2022 08:35:40 +0100 cuboid_06_wavers wrote: > > running speedtest > > > > * What was the outcome of this action? > > > > ERROR: Unable to connect to servers to test latency. > > Same thing happens here. As far as I can tell that makes the package pretty > unusable so I guess the severity could be raised. I'm not able to reproduce this, speedtest-cli works fine for me, so lets let it back into testing until it is confirmed really broken. Could you all paste the output of your speedtests? Mine are below. Also probably a good idea to try the --secure or --single options. $ speedtest-cli Retrieving speedtest.net configuration... Testing from Optus (49.194.242.10)... Retrieving speedtest.net server list... Selecting best server based on ping... Hosted by Aussie Broadband (Adelaide) [1162.27 km]: 411.184 ms Testing download speed Download: 50.96 Mbit/s Testing upload speed.. Upload: 18.01 Mbit/s $ speedtest-cli Retrieving speedtest.net configuration... Testing from Optus (49.194.242.10)... Retrieving speedtest.net server list... Selecting best server based on ping... Hosted by Optus (Rockingham) [3294.66 km]: 31.062 ms Testing download speed Download: 50.11 Mbit/s Testing upload speed.. Upload: 19.37 Mbit/s $ speedtest-cli --list Retrieving speedtest.net configuration... 12495) Telstra (Adelaide, Australia) [1162.25 km] 15135) Aussie Broadband (Adelaide, Australia) [1162.27 km] 10613) Optus (Rockingham, Australia) [3294.66 km] 48851) PT. Superspace Teknologi Indonesia (Kupang, Indonesia) [3851.65 km] 36160) Arsenet Global Solusi (Kupang, Indonesia) [3851.65 km] 57225) MTM Bali (Mataram, Indonesia) [4556.24 km] 58325) GMEDIA (Mataram, Indonesia) [4556.24 km] 59213) ALUSNet (Denpasar, Indonesia) [4623.59 km] 58275) IPN (Denpasar, Indonesia) [4623.59 km] 62212) Spicelink Broadband (Denpasar, Indonesia) [4623.59 km] -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1056736: smartmontools: please do not force people to use update-smart-drivedb and install foreign code
On Sat, 25 Nov 2023 18:56:03 +0100 Christoph Anton Mitterer wrote: > The most recent upgrade forces people to use > update-smart-drivedb by doing it already in the postinst and not leaving it > up to the user whether he wants to use such a tool. > > Security-wise this is really a bad idea. > > Downloader packages (i.e. packages that install further code from > outside Debian) - and this effectively just that - are generally questionable. You have missed the documentation of the --install option that the postinst uses, it just copies the file from /usr to /var when the /usr file is newer than the /var file, it does not download any files. Previously the postinst was always force copying from /usr to /var, now it only does the copying when the /usr file is newer. I suggest that this bug be closed. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1042628: case: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:13: override_dh_auto_build] Error 2
Control: tags -1 + unreproducible On Sun, 30 Jul 2023 20:30:36 +0200 Lucas Nussbaum wrote: > case fails to build with Sphinx 7.1 and docutils 0.20, both of which > are currently available in experimental. I am unable to reproduce this when building case 1.5.3+dfsg-5 with experimental python3-sphinx 7.2.6-1 and python3-docutils 0.20.1+dfsg-1. Could you recheck this build failure and close it if it is fixed? -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1055203: git-cola: files in /usr/local/share/{applications,doc,git-cola,locale,metainfo}/
Package: git-cola Version: 3.12.0-3 Severity: serious Justification: Policy 9.1.2 According to the FHS and Debian Policy 9.1.2, packages must not put files in the /usr/local/ directory, but git-cola 3.12.0-3 does that: https://www.debian.org/doc/debian-policy/ch-opersys.html#site-specific-programs I note that lintian does produce errors for this situation: https://udd.debian.org/lintian/?packages=git-cola Here is the full list of files in the /usr/local/ directory: $ dpkg -L git-cola | grep /usr/local/ /usr/local/share /usr/local/share/applications /usr/local/share/applications/git-cola-folder-handler.desktop /usr/local/share/applications/git-cola.desktop /usr/local/share/applications/git-dag.desktop /usr/local/share/doc /usr/local/share/doc/git-cola /usr/local/share/doc/git-cola/git-cola.rst /usr/local/share/doc/git-cola/git-dag.rst /usr/local/share/doc/git-cola/hotkeys.html /usr/local/share/doc/git-cola/hotkeys_de.html /usr/local/share/doc/git-cola/hotkeys_zh_CN.html /usr/local/share/doc/git-cola/hotkeys_zh_TW.html /usr/local/share/doc/git-cola/index.rst /usr/local/share/doc/git-cola/relnotes.rst /usr/local/share/doc/git-cola/thanks.rst /usr/local/share/git-cola /usr/local/share/git-cola/bin /usr/local/share/git-cola/bin/ssh-askpass /usr/local/share/git-cola/bin/ssh-askpass-darwin /usr/local/share/git-cola/icons /usr/local/share/git-cola/icons/a-z-order.svg /usr/local/share/git-cola/icons/arrow-down.svg /usr/local/share/git-cola/icons/arrow-up.svg /usr/local/share/git-cola/icons/check.svg /usr/local/share/git-cola/icons/circle-slash-red.svg /usr/local/share/git-cola/icons/circle-slash.svg /usr/local/share/git-cola/icons/dark /usr/local/share/git-cola/icons/dark/a-z-order.svg /usr/local/share/git-cola/icons/dark/arrow-down.svg /usr/local/share/git-cola/icons/dark/arrow-up.svg /usr/local/share/git-cola/icons/dark/check.svg /usr/local/share/git-cola/icons/dark/circle-slash-red.svg /usr/local/share/git-cola/icons/dark/circle-slash.svg /usr/local/share/git-cola/icons/dark/desktop-download.svg /usr/local/share/git-cola/icons/dark/diff.svg /usr/local/share/git-cola/icons/dark/document-save-symbolic.svg /usr/local/share/git-cola/icons/dark/edit-copy.svg /usr/local/share/git-cola/icons/dark/edit-cut.svg /usr/local/share/git-cola/icons/dark/edit-paste.svg /usr/local/share/git-cola/icons/dark/edit-redo.svg /usr/local/share/git-cola/icons/dark/edit-select-all.svg /usr/local/share/git-cola/icons/dark/edit-undo.svg /usr/local/share/git-cola/icons/dark/ellipsis.svg /usr/local/share/git-cola/icons/dark/eye.svg /usr/local/share/git-cola/icons/dark/file-binary.svg /usr/local/share/git-cola/icons/dark/file-code.svg /usr/local/share/git-cola/icons/dark/file-directory.svg /usr/local/share/git-cola/icons/dark/file-download.svg /usr/local/share/git-cola/icons/dark/file-media.svg /usr/local/share/git-cola/icons/dark/file-text.svg /usr/local/share/git-cola/icons/dark/file-zip.svg /usr/local/share/git-cola/icons/dark/fold.svg /usr/local/share/git-cola/icons/dark/folder-new.svg /usr/local/share/git-cola/icons/dark/folder.svg /usr/local/share/git-cola/icons/dark/gear.svg /usr/local/share/git-cola/icons/dark/git-branch.svg /usr/local/share/git-cola/icons/dark/git-cola.svg /usr/local/share/git-cola/icons/dark/git-commit.svg /usr/local/share/git-cola/icons/dark/git-compare.svg /usr/local/share/git-cola/icons/dark/git-merge.svg /usr/local/share/git-cola/icons/dark/last-first-order.svg /usr/local/share/git-cola/icons/dark/link-external.svg /usr/local/share/git-cola/icons/dark/modified.svg /usr/local/share/git-cola/icons/dark/partial.svg /usr/local/share/git-cola/icons/dark/pencil.svg /usr/local/share/git-cola/icons/dark/plus.svg /usr/local/share/git-cola/icons/dark/primitive-dot.svg /usr/local/share/git-cola/icons/dark/question-plain.svg /usr/local/share/git-cola/icons/dark/question.svg /usr/local/share/git-cola/icons/dark/repo-pull.svg /usr/local/share/git-cola/icons/dark/repo-push.svg /usr/local/share/git-cola/icons/dark/repo.svg /usr/local/share/git-cola/icons/dark/screen-full.svg /usr/local/share/git-cola/icons/dark/search.svg /usr/local/share/git-cola/icons/dark/staged.svg /usr/local/share/git-cola/icons/dark/star.svg /usr/local/share/git-cola/icons/dark/sync.svg /usr/local/share/git-cola/icons/dark/tag.svg /usr/local/share/git-cola/icons/dark/telescope.svg /usr/local/share/git-cola/icons/dark/three-bars.svg /usr/local/share/git-cola/icons/dark/trashcan.svg /usr/local/share/git-cola/icons/dark/unfold.svg /usr/local/share/git-cola/icons/dark/upstream.svg /usr/local/share/git-cola/icons/dark/x.svg /usr/local/share/git-cola/icons/dark/zoom-fit-best.svg /usr/local/share/git-cola/icons/dark/zoom-in.svg /usr/local/share/git-cola/icons/dark/zoom-out.svg
Bug#1055043: Debian carnivore: port from Python 2 to 3
Package: qa.debian.org Severity: serious User: qa.debian@packages.debian.org Usertags: carnivore X-Debbugs-CC: m...@qa.debian.org, debian-pyt...@lists.debian.org The carnivore system which tracks the activity of Debian members is written in Python 2, which has been removed from Debian, so carnivore needs porting to Python 3 and volunteers are needed to work on that. https://salsa.debian.org/qa/qa/-/tree/master/carnivore/ https://salsa.debian.org/qa/qa/-/blob/master/data/cronjobs/carnivore https://salsa.debian.org/qa/qa/-/blob/data/cronjobs/ddpo.carnivore https://salsa.debian.org/qa/qa/-/blob/data/ddpo/extract_carnivore.pl -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1052327: libdbd-odbc-perl: Test failure in t/rt_57957.t
Control: tags -1 + fixed-upstream On Tue, 2023-10-10 at 12:48 +0800, Paul Wise wrote: > The fix is to increment both pointers at once. > > *p++ = *q++; > > This fixes the libdbd-odbc-perl test failures too. > > I have sent the attached patch to upstream. Upstream released this fix in version 0.1. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1052847: python-marshmallow: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13
On Tue, 26 Sep 2023 15:23:12 +0200 Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
...
> > ImportError while loading conftest
> > '/<>/.pybuild/cpython3_3.11_marshmallow/build/tests/conftest.py'.
> > tests/conftest.py:4: in
> > from tests.base import User, UserSchema, Blog
> > tests/base.py:14: in
> > central = pytz.timezone("US/Central")
> > /usr/lib/python3/dist-packages/pytz/__init__.py:202: in timezone
> > raise UnknownTimeZoneError(zone)
> > E pytz.exceptions.UnknownTimeZoneError: 'US/Central'
This was caused by the split of tzdata-legacy from tzdata, the fix is
to add tzdata-legacy to build-depends and I notice that you already
fixed the issue in git and tagged an upload but haven't uploaded yet.
Would you like me to upload for you or can you take care of it?
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Bug#1052835: marked as pending in utf8proc
On Sat, 30 Sep 2023 18:35:04 + Mo Zhou wrote: > Bug #1052835 in utf8proc 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/julia-team/utf8proc/-/commit/ba942e99629cb82bf92805c10e407826ac22bf24 > > > Patch to support unicode-data 15.1.0 (Closes: #1052835) > I note that this RC-bug-fix hasn't been uploaded yet nor sent upstream, would you and the Julia team like some help with those tasks? -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1052327: libdbd-odbc-perl: Test failure in t/rt_57957.t
Control: reassign -1 libsqliteodbc 0.-1
Control: retitle -1 libsqliteodbc: regression: crashes (SIGSEGV) with line
comments
Control: affects -1 + libdbd-odbc-perl
Control: tags -1 + patch
Control: forwarded -1 Christian Werner
On Wed, 20 Sep 2023 17:00:50 +0200 gregor herrmann wrote:
> As noticed by ci.debian.org, t/rt_57957.t started to fail at some
> point between 2023-09-02 and 2023-09-18.
The two tests that fail are the line comment ones:
4 - Prepare with line comment named placeholder
6 - Prepare with line comment and ? placeholder
They both fail by causing a SIGSEGV in Perl itself.
Executing the same SQL within sqlite3 does not cause a SIGSEGV:
$ sqlite3
SQLite version 3.43.1 2023-09-11 12:01:27
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> select -- placeholder ? in a comment
1;
1
When I modify the SQL a bit so that gdb can actually load the core dump
from inside pbuilder, I get a backtrace inside sqliteodbc.
When I downgrade libsqliteodbc from 0.-1 to 0.9998-3+b1 then the
crash no longer happens, so this is a bug in sqliteodbc.
When I modify the pyodbc tests to include a test with a line comment,
then I get a Python crash and the crash is fixed with 0.9998-3+b1.
Looking at the diff from 0.9998-3 to 0.-1, I see that this version
added support for line comments by adding this case to the code:
case '-':
*p++ = *q;
if (!inq && q[1] == '-') {
++q;
while (*q) {
*p++ = *q;
if (*q == '\n') {
break;
}
}
}
break;
So this is crashing because the q pointer isn't getting incremented so
it never reaches the \n character nor the end of the SQL string, but
the p pointer is getting incremented within the infinite loop, so it
gets incremented past the end of its allocated memory.
The fix is to increment both pointers at once.
*p++ = *q++;
This fixes the libdbd-odbc-perl test failures too.
I have sent the attached patch to upstream.
--
bye,
pabs
https://wiki.debian.org/PaulWise
From 0bc7d682561c1a3e4cec4627e45c8cefa91f14a9 Mon Sep 17 00:00:00 2001
From: Paul Wise
Date: Tue, 10 Oct 2023 12:45:17 +0800
Subject: [PATCH] Fix crash with line comments in SQL fixup
The handling of line comments is crashing because the q pointer isn't
getting incremented so it never reaches the \n character nor the end
of the SQL string, but the p pointer is getting incremented within the
infinite loop, so it gets incremented past the end of its allocated memory.
This crash was introduced in version 0..
---
sqlite3odbc.c | 2 +-
sqlite4odbc.c | 2 +-
sqliteodbc.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/sqlite3odbc.c b/sqlite3odbc.c
index 94b407e..27f394f 100644
--- a/sqlite3odbc.c
+++ b/sqlite3odbc.c
@@ -2581,7 +2581,7 @@ errout:
if (!inq && q[1] == '-') {
++q;
while (*q) {
- *p++ = *q;
+ *p++ = *q++;
if (*q == '\n') {
break;
}
diff --git a/sqlite4odbc.c b/sqlite4odbc.c
index 78f2b1e..031cd1f 100644
--- a/sqlite4odbc.c
+++ b/sqlite4odbc.c
@@ -2561,7 +2561,7 @@ errout:
if (!inq && q[1] == '-') {
++q;
while (*q) {
- *p++ = *q;
+ *p++ = *q++;
if (*q == '\n') {
break;
}
diff --git a/sqliteodbc.c b/sqliteodbc.c
index c9c7a29..bad61ab 100644
--- a/sqliteodbc.c
+++ b/sqliteodbc.c
@@ -1730,7 +1730,7 @@ errout:
if (!inq && q[1] == '-') {
++q;
while (*q) {
- *p++ = *q;
+ *p++ = *q++;
if (*q == '\n') {
break;
}
--
2.42.0
signature.asc
Description: This is a digitally signed message part
Bug#1053672: Apple copyright notices in test .xlsx files
On Sun, 2023-10-08 at 15:04 +0100, Rebecca N. Palmer wrote: > Given this, why is that copyright notice there, and what does it imply > that we should do? (E.g. does Apple Numbers automatically copy > Apple-owned items (e.g. fonts) into files it creates? If so, is there a > way to remove these items to get a Free file?) *.xlsx files are actually just *.zip files containing XML and other files. The Apple copyright for both of the files you mention comes from the Apple copyright listed for the ICC profile embedded in the EXIF data in the JPEG file that was saved as a thumbnail of the spreadsheet. I am not sure what that means for the license of the test cases in openpyxl and but it would be easy to fix by either deleting the thumbnail, or removing the ICC profile, but that would alter the test cases, probably that wouldn't affect the tests passing/failing though. $ unzip conditional-formatting.xlsx Archive: conditional-formatting.xlsx inflating: [Content_Types].xml inflating: _rels/.rels inflating: xl/_rels/workbook.xml.rels inflating: xl/workbook.xml extracting: docProps/thumbnail.jpeg inflating: xl/theme/theme1.xml inflating: xl/styles.xml inflating: xl/worksheets/sheet1.xml inflating: docProps/core.xml inflating: docProps/app.xml $ grep -ri apple grep: conditional-formatting.xlsx: binary file matches grep: docProps/thumbnail.jpeg: binary file matches $ exiftool docProps/thumbnail.jpeg | grep -i apple Profile CMM Type: Apple Computer Inc. Primary Platform: Apple Computer Inc. Device Manufacturer : Apple Computer Inc. Profile Creator : Apple Computer Inc. Profile Copyright : Copyright 2007 Apple Inc., all rights reserved. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1053295: golang-ginkgo: dropped transitional package golang-ginkgo-dev, which is still used
On Mon, 2023-10-02 at 16:46 +0100, Martina Ferrari wrote: > Thanks for the report, I was scratching my head over the weekend > wondering why this package was not migrating.. I guess I was too eager > to remove the transitional package, "cme check dpkg" told me it was safe > to remove, but I did not think of the packages that have not been > updated in a long while.. I will apply your suggestion in a bit. You may also want to file bugs against those packages or transition them so that you can later drop the Provides? -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1053295: golang-ginkgo: dropped transitional package golang-ginkgo-dev, which is still used
Source: golang-ginkgo Version: 1.16.5-4 Severity: serious golang-ginkgo is failing to migrate to testing, because it dropped the transitional package golang-ginkgo-dev, which makes a lot of golang packages uninstallable, because they haven't migrated to the new package golang-github-onsi-ginkgo-dev yet. The britney log indicates the src/bin packages with newly uninstallable Depends/Build-Depends and the ftp-master cruft report confirms the problems in more detail. https://release.debian.org/britney/update_output.txt https://release.debian.org/doc/britney/short-intro-to-migrations.html#debugging-failed-migration-attempts https://ftp-master.debian.org/cruft-report-daily.txt Probably the solution to this is for golang-github-onsi-ginkgo-dev to add Provides: golang-ginkgo-dev so it doesn't have to go through NEW. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1039613: nmap breaks udptunnel autopkgtest: UDPTunnel communication failed
On Tue, 27 Jun 2023 21:40:14 +0200 Paul Gevers wrote: > Source: nmap, udptunnel > Control: found -1 nmap/7.94+dfsg1-1 > Control: found -1 udptunnel/1.1-9 ... > With a recent upload of nmap the autopkgtest of udptunnel fails in > testing when that autopkgtest is run with the binary packages of nmap > from unstable. It passes when run with only packages from testing. I think this is likely to be a bug in nmap ncat, when I remove udptunnel from the script by connecting ncat directly to ncat, then the failure still happens with the autopkgtest. I was able to reproduce this issue outside a chroot. I have attached a pair of scripts; bad fails and good succeeds. In the good case, I use `sleep` to hold stdin of `ncat -l` open for 2s, in the bad case I let it use the stdin provided by the shell (a GNOME terminal pty here). Looking at the diff between the verbose logs is interesting. In the good case one select fd is ready and one becomes ready later, the latter one gets used, but in the bad case both fds appear to be ready immediately but neither of them get used. -NCAT DEBUG: select returned 1 fds ready -NCAT DEBUG: fd 3 is ready -NCAT DEBUG: selecting, fdmax 3 -NCAT DEBUG: select returned 1 fds ready +NCAT DEBUG: select returned 2 fds ready So the issue can be worked around in the udptunnel script by piping sleep to the ncat listener instead of launching ncat and then sleeping, or the ncat change that caused this can get bisected and fixed. -- bye, pabs https://wiki.debian.org/PaulWise bad Description: application/shellscript + rm rx tx + echo foo + sleep 2s + ncat - -u -l 127.0.0.1 1234 Ncat: Version 7.94 ( https://nmap.org/ncat ) NCAT DEBUG: Initialized fdlist with 102 maxfds Ncat: Listening on 127.0.0.1:1234 NCAT DEBUG: Added fd 3 to list, nfds 1, maxfd 3 NCAT DEBUG: Added fd 0 to list, nfds 2, maxfd 3 NCAT DEBUG: Initialized fdlist with 100 maxfds NCAT DEBUG: selecting, fdmax 3 + ncat -u 127.0.0.1 1234 NCAT DEBUG: select returned 1 fds ready NCAT DEBUG: fd 3 is ready NCAT DEBUG: Swapping fd[0] (3) with fd[1] (0) NCAT DEBUG: Removed fd 3 from list, nfds 1, maxfd 0 Ncat: Connection from 127.0.0.1:57558. NCAT DEBUG: Added fd 3 to list, nfds 2, maxfd 3 NCAT DEBUG: Added fd 3 to list, nfds 1, maxfd 3 NCAT DEBUG: selecting, fdmax 3 NCAT DEBUG: select returned 2 fds ready NCAT DEBUG: fd 0 is ready NCAT DEBUG: EOF on stdin + sleep 2s + head -vn-0 tx rx ==> tx <== foo ==> rx <== + echo tx tx + hd tx 66 6f 6f 0a |foo.| 0004 + echo rx rx + hd rx + echo diff diff + diff -u tx rx --- tx 2023-07-23 16:49:32.411502343 +0800 +++ rx 2023-07-23 16:49:32.411502343 +0800 @@ -1 +0,0 @@ -foo good Description: application/shellscript + rm rx tx + echo foo + + sleep 2sncat -u 127.0.0.1 1234 + ncat - -u -l 127.0.0.1 1234 Ncat: Version 7.94 ( https://nmap.org/ncat ) NCAT DEBUG: Initialized fdlist with 102 maxfds Ncat: Listening on 127.0.0.1:1234 NCAT DEBUG: Added fd 3 to list, nfds 1, maxfd 3 NCAT DEBUG: Added fd 0 to list, nfds 2, maxfd 3 NCAT DEBUG: Initialized fdlist with 100 maxfds NCAT DEBUG: selecting, fdmax 3 NCAT DEBUG: select returned 1 fds ready NCAT DEBUG: fd 3 is ready NCAT DEBUG: Swapping fd[0] (3) with fd[1] (0) NCAT DEBUG: Removed fd 3 from list, nfds 1, maxfd 0 Ncat: Connection from 127.0.0.1:36688. NCAT DEBUG: Added fd 3 to list, nfds 2, maxfd 3 NCAT DEBUG: Added fd 3 to list, nfds 1, maxfd 3 NCAT DEBUG: selecting, fdmax 3 NCAT DEBUG: select returned 1 fds ready NCAT DEBUG: fd 3 is ready NCAT DEBUG: selecting, fdmax 3 + sleep 2s NCAT DEBUG: select returned 1 fds ready NCAT DEBUG: fd 0 is ready NCAT DEBUG: EOF on stdin + head -vn-0 tx rx ==> tx <== foo ==> rx <== foo + echo tx tx + hd tx 66 6f 6f 0a |foo.| 0004 + echo rx rx + hd rx 66 6f 6f 0a |foo.| 0004 + echo diff diff + diff -u tx rx signature.asc Description: This is a digitally signed message part
Bug#1037974: ddcci-dkms: code fails to build and package fails to install with Linux 6.3 headers
Package: ddcci-dkms
Version: 0.4.2-4
Severity: serious
When I try to install ddcci-dkms with the Linux 6.3 headers installed,
the build of the code fails and then the install of the package fails.
I think there are two problems here:
* The code needs to be adapted to the latest Linux kernel version.
* The package should not fail to install when the module build fails.
This might be a problem in dkms itself, or in ddcci's integration.
I note that the combination of these issues also will break
installation of Linux 6.3 when ddcci-dkms is installed.
$ sudo apt install ddcci-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
ddcci-dkms
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 21.7 kB of archives.
After this operation, 95.2 kB of additional disk space will be used.
Get:1 https://deb.debian.org/debian testing/main amd64 ddcci-dkms all
0.4.2-4 [21.7 kB]
Fetched 21.7 kB in 1s (17.0 kB/s)
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Selecting previously unselected package ddcci-dkms.
(Reading database ... 730615 files and directories currently installed.)
Preparing to unpack .../ddcci-dkms_0.4.2-4_all.deb ...
Unpacking ddcci-dkms (0.4.2-4) ...
Setting up ddcci-dkms (0.4.2-4) ...
Loading new ddcci-0.4.2 DKMS files...
Building for 6.3.0-1-amd64
Building initial module for 6.3.0-1-amd64
Error! Bad return status for module build on kernel: 6.3.0-1-amd64 (x86_64)
Consult /var/lib/dkms/ddcci/0.4.2/build/make.log for more information.
dpkg: error processing package ddcci-dkms (--configure):
installed ddcci-dkms package post-installation script subprocess returned
error exit status 10
Errors were encountered while processing:
ddcci-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
$ cat /var/lib/dkms/ddcci/0.4.2/build/make.log
DKMS make.log for ddcci-0.4.2 for kernel 6.3.0-1-amd64 (x86_64)
Thu 15 Jun 2023 10:23:01 AWST
make: Entering directory '/var/lib/dkms/ddcci/0.4.2/build'
make -C "ddcci"
make[1]: Entering directory '/var/lib/dkms/ddcci/0.4.2/build/ddcci'
make -C "/lib/modules/6.3.0-1-amd64/build"
M="/var/lib/dkms/ddcci/0.4.2/build/ddcci" modules
make[2]: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64'
CC [M] /var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.o
/var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1053:27: error: initialization
of ‘int (*)(const struct device *, struct kobj_uevent_env *)’ from incompatible
pointer type ‘int (*)(struct device *, struct kobj_uevent_env *)’
[-Werror=incompatible-pointer-types]
1053 | .uevent = ddcci_device_uevent,
| ^~~
/var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1053:27: note: (near
initialization for ‘ddcci_device_type.uevent’)
/var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1056:27: error: initialization
of ‘char * (*)(const struct device *, umode_t *, kuid_t *, kgid_t *)’ {aka
‘char * (*)(const struct device *, short unsigned int *, kuid_t *, kgid_t *)’}
from incompatible pointer type ‘char * (*)(struct device *, umode_t *, kuid_t
*, kgid_t *)’ {aka ‘char * (*)(struct device *, short unsigned int *, kuid_t *,
kgid_t *)’} [-Werror=incompatible-pointer-types]
1056 | .devnode = ddcci_devnode
| ^
/var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1056:27: note: (near
initialization for ‘ddcci_device_type.devnode’)
/var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1062:27: error: initialization
of ‘int (*)(const struct device *, struct kobj_uevent_env *)’ from incompatible
pointer type ‘int (*)(struct device *, struct kobj_uevent_env *)’
[-Werror=incompatible-pointer-types]
1062 | .uevent = ddcci_device_uevent,
| ^~~
/var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1062:27: note: (near
initialization for ‘ddcci_dependent_type.uevent’)
/var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1065:27: error: initialization
of ‘char * (*)(const struct device *, umode_t *, kuid_t *, kgid_t *)’ {aka
‘char * (*)(const struct device *, short unsigned int *, kuid_t *, kgid_t *)’}
from incompatible pointer type ‘char * (*)(struct device *, umode_t *, kuid_t
*, kgid_t *)’ {aka ‘char * (*)(struct device *, short unsigned int *, kuid_t *,
kgid_t *)’} [-Werror=incompatible-pointer-types]
1065 | .devnode = ddcci_dependent_devnode
| ^~~
/var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1065:27: note: (near
initialization for ‘ddcci_dependent_type.devnode’)
In file included from
/usr/src/linux-headers-6.3.0-1-common/include/linux/build_bug.h:5,
from
Bug#1034582: opencpn: broken symlinks: MathJax.js highlight.min.js due to missing dependencies
Package: opencpn Version: 5.8.0+dfsg-1 Severity: serious File: /usr/share/opencpn/plugins/chartdldr_pi/data/doc/MathJax.js File: /usr/share/opencpn/plugins/chartdldr_pi/data/doc/highlight.min.js User: debian...@lists.debian.org Usertags: adequate broken-symlink opencpn 5.8.0+dfsg-1 introduced two broken symlinks: /usr/share/opencpn/plugins/chartdldr_pi/data/doc/MathJax.js -> ../../../../../javascript/mathjax/MathJax.js /usr/share/opencpn/plugins/chartdldr_pi/data/doc/highlight.min.js -> ../../../../../javascript/highlight.js/highlight.min.js This appears to be because opencpn switched to using the packaged versions of these files, but only added the libjs-mathjax and libjs-highlight.js packages to the Build-Depends. Since there is nothing to auto-populate Depends for JavaScript packages (please talk to the JS team about adding that) and the packages weren't added manually to Depends, the added symlinks aren't working unless the user already had the packages installed. This bug was filed at severity serious because of the missing dependencies. Here is some information about the symlinks: $ adequate opencpn opencpn: broken-symlink /usr/share/opencpn/plugins/chartdldr_pi/data/doc/MathJax.js -> ../../../../../javascript/mathjax/MathJax.js opencpn: broken-symlink /usr/share/opencpn/plugins/chartdldr_pi/data/doc/highlight.min.js -> ../../../../../javascript/highlight.js/highlight.min.js $ readlink /usr/share/opencpn/plugins/chartdldr_pi/data/doc/MathJax.js /usr/share/opencpn/plugins/chartdldr_pi/data/doc/highlight.min.js ../../../../../javascript/mathjax/MathJax.js ../../../../../javascript/highlight.js/highlight.min.js $ chase /usr/share/opencpn/plugins/chartdldr_pi/data/doc/MathJax.js /usr/share/opencpn/plugins/chartdldr_pi/data/doc/highlight.min.js chase: ../../../../../javascript/mathjax: No such file or directory chase: ../../../../../javascript/highlight.js: No such file or directory $ apt-file search javascript/mathjax/MathJax.js libjs-mathjax: /usr/share/javascript/mathjax/MathJax.js $ apt-file search javascript/highlight.js/highlight.min.js libjs-highlight.js: /usr/share/javascript/highlight.js/highlight.min.js $ apt-cache show opencpn opencpn-data | grep libjs ; echo $? 1 Here is the log of the upgrade: Log started: 2023-04-18 17:09:54 apt-listchanges: Reading changelogs... apt-listchanges: Mailing root: apt-listchanges: changelogs for chianamo apt-listchanges: Reading changelogs... Selecting previously unselected package libcxx-serial1:amd64. Preparing to unpack .../libcxx-serial1_1.2.1-5+b1_amd64.deb ... Unpacking libcxx-serial1:amd64 (1.2.1-5+b1) ... Preparing to unpack .../opencpn-data_5.8.0+dfsg-1_all.deb ... Unpacking opencpn-data (5.8.0+dfsg-1) over (5.6.2+dfsg-3) ... Preparing to unpack .../opencpn_5.8.0+dfsg-1_amd64.deb ... Unpacking opencpn (5.8.0+dfsg-1) over (5.6.2+dfsg-3) ... Setting up opencpn-data (5.8.0+dfsg-1) ... Setting up libcxx-serial1:amd64 (1.2.1-5+b1) ... Setting up opencpn (5.8.0+dfsg-1) ... Processing triggers for mailcap (3.70+nmu1) ... Processing triggers for desktop-file-utils (0.26-1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for gnome-menus (3.36.0-1.1) ... Processing triggers for libc-bin (2.36-9) ... Processing triggers for man-db (2.11.2-2) ... Log ended: 2023-04-18 17:10:17 Here is the changelog of the version that introduced this: opencpn (5.8.0+dfsg-1) unstable; urgency=medium * New upstream release * Drop upstreamed patches, rebase remaining * Exclude MathJax and highlight js libraries, use packages instead. * Add new build deps: - libssl-dev - googletest - libglew-dev - repidjson-dev - libjs-highlight.js - libjs-mathjax * Update deprecated libpixbuf-dev build dep * Update d/copyright using cme. -- Alec Leamas Fri, 14 Apr 2023 09:37:20 +0200 -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (950, 'testing-security'), (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-7-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages opencpn depends on: ii bzip2 1.0.8-5+b1 ii libarchive133.6.2-1 ii libbz2-1.0 1.0.8-5+b1 ii libc6 2.36-9 ii libcurl3-gnutls 7.88.1-8 ii libcxx-serial1 1.2.1-5+b1 ii libelf1 0.188-2.1
Bug#1030004: itinerary: missing dependency on qml-module-qt-labs-qmlmodels
Package: itinerary Version: 22.08.2-1+b1 Severity: serious itinerary just hangs on start under GNOME, after I installed the qml-module-qt-labs-qmlmodels package then the GUI showed up. $ itinerary QSocketNotifier: Can only be used with threads started with QThread org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.itinerary: Performing a full transfer search... 0 has portal: true QQmlApplicationEngine failed to load component qrc:/main.qml:192:9: Type App.TimelinePage unavailable qrc:/TimelinePage.qml:10:1: module "Qt.labs.qmlmodels" is not installed -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages itinerary depends on: ii kio 5.102.0-1 ii libc62.36-8 ii libkf5calendarcore5abi2 5:5.102.0-1 ii libkf5contacts5 5:5.102.0-1 ii libkf5coreaddons55.102.0-1 ii libkf5crash5 5.102.0-1 ii libkf5dbusaddons55.102.0-1 ii libkf5filemetadata3 5.102.0-1 ii libkf5holidays5 1:5.102.0-1 ii libkf5i18n5 5.102.0-1 ii libkf5i18nlocaledata55.102.0-1 ii libkf5kiowidgets55.102.0-1 ii libkf5networkmanagerqt6 5.102.0-1 ii libkf5notifications5 5.102.0-1 ii libkf5unitconversion55.102.0-1 ii libkf5windowsystem5 5.102.0-1 ii libkosmindoormap122.08.2-1+b1 ii libkpimitinerary5 [libkpimitinerary5-22.12] 22.12.0-2+b2 ii libkpimpkpass5 [libkpimpkpass5-22.12]22.12.0-2 ii libkpublictransport1 22.12.1-1 ii libqt5core5a [qtbase-abi-5-15-8] 5.15.8+dfsg-2 ii libqt5dbus5 5.15.8+dfsg-2 ii libqt5gui5 5.15.8+dfsg-2 ii libqt5network5 5.15.8+dfsg-2 ii libqt5positioning5 5.15.8+dfsg-2 ii libqt5qml5 5.15.8+dfsg-2 ii libqt5quick5 5.15.8+dfsg-2 ii libqt5quickcontrols2-5 5.15.8+dfsg-2 ii libqt5widgets5 5.15.8+dfsg-2 ii libstdc++6 12.2.0-14 ii qml-module-org-kde-kitemmodels 5.102.0-1 ii qml-module-org-kde-kopeninghours 22.12.0-1+b1 ii qml-module-org-kde-kosmindoormap 22.08.2-1+b1 ii qml-module-org-kde-prison5.102.0-1 ii qml-module-qt-labs-platform 5.15.8+dfsg-2 ii qml-module-qtlocation5.15.8+dfsg-2 ii qml-module-qtmultimedia 5.15.8-2 ii qml-module-qtpositioning 5.15.8+dfsg-2 ii zlib1g 1:1.2.13.dfsg-1 itinerary recommends no packages. itinerary suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1029749: pypi2deb: crashes with Python 3.11: AttributeError: module 'asyncio' has no attribute 'coroutine'. Did you mean: 'coroutines'?
Package: pypi2deb Version: 3.20220721 Severity: serious Usertags: crash User: debian-pyt...@lists.debian.org Usertags: python3.11 With Python 3.11 in a clean sid chroot, both py2dsp and pypi2debian crash with an error about the asyncio module attributes. This can also be seen on a mixed bookworm/sid system when forcing python3.11 usage. $ py2dsp Traceback (most recent call last): File "/usr/bin/py2dsp", line 32, in from pypi2deb.debianize import debianize File "/usr/share/pypi2deb/pypi2deb/debianize.py", line 29, in from pypi2deb.tools import execute File "/usr/share/pypi2deb/pypi2deb/tools.py", line 92, in @asyncio.coroutine ^ AttributeError: module 'asyncio' has no attribute 'coroutine'. Did you mean: 'coroutines'? $ pypi2debian Traceback (most recent call last): File "/usr/bin/pypi2debian", line 35, in from pypi2deb.debianize import debianize File "/usr/share/pypi2deb/pypi2deb/debianize.py", line 29, in from pypi2deb.tools import execute File "/usr/share/pypi2deb/pypi2deb/tools.py", line 92, in @asyncio.coroutine ^ $ python3.11 /usr/bin/py2dsp Traceback (most recent call last): File "/usr/bin/py2dsp", line 32, in from pypi2deb.debianize import debianize File "/usr/share/pypi2deb/pypi2deb/debianize.py", line 29, in from pypi2deb.tools import execute File "/usr/share/pypi2deb/pypi2deb/tools.py", line 92, in @asyncio.coroutine ^ AttributeError: module 'asyncio' has no attribute 'coroutine'. Did you mean: 'coroutines'? -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages pypi2deb depends on: ii build-essential 12.9 ii devscripts 2.22.2 ii dh-python5.20230109 ii python3 3.11.1-1 ii python3-aiohttp 3.8.3-1+b1 ii python3-debian 0.1.49 ii python3-github 1.55-3 ii python3-jinja2 3.0.3-2 ii python3-redis4.3.4-3 Versions of packages pypi2deb recommends: pn python3-msgpack Versions of packages pypi2deb suggests: pn cython pn cython3 pn pypy pn python-all-dev pn python-nose pn python-pytest pn python-setuptools pn python3-all-dev pn python3-nose pn python3-pytest pn python3-setuptools pn python3-sphinx -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1029481: fixed with version 3.1.0-2
On Mon, 2023-01-23 at 11:21 +0100, Christoph Martin wrote: > The other lines reported with > > dgrep -A5 'auto-generated' debmake > > are false-positives since they are files from the debmake package and > not from yq. That was just an illustration of where the yq package description that was containing "auto-generated" was copied from, not a demonstration of the problematic parts of the yq package, which was the first command. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1029481: yq: unmodified incorrect package description from debmake template
Package: yq Version: 3.1.0-1 Severity: serious The current description of the yq package is rather bogus. It appears that the debmake template was not modified. $ apt-cache show yq | grep-dctrl -s Description-en . Description-en: auto-generated package by debmake This Debian binary package was auto-generated by the debmake(1) command provided by the debmake package. $ chronic apt source -qq yq $ head -n1 yq*/README* yq: Command-line YAML/XML/TOML processor - jq wrapper for YAML, XML, TOML documents $ dgrep -A5 'auto-generated' debmake /usr/lib/python3/dist-packages/debmake/control.py:desc = "auto-generated package by debmake" /usr/lib/python3/dist-packages/debmake/control.py-# /usr/lib/python3/dist-packages/debmake/control.py-if para["desc_long"].rstrip(): /usr/lib/python3/dist-packages/debmake/control.py-desc_long = para["desc_long"].rstrip() /usr/lib/python3/dist-packages/debmake/control.py-elif para["desc"].strip(): /usr/lib/python3/dist-packages/debmake/control.py-desc_long = " " + para["desc"].strip() -- /usr/lib/python3/dist-packages/debmake/para.py:help="pedantically check auto-generated files", /usr/lib/python3/dist-packages/debmake/para.py-) /usr/lib/python3/dist-packages/debmake/para.py-p.add_argument( /usr/lib/python3/dist-packages/debmake/para.py-"-T", /usr/lib/python3/dist-packages/debmake/para.py-"--tutorial", /usr/lib/python3/dist-packages/debmake/para.py-action="store_true", -- /usr/share/debmake/extra0desc_long/_long: This Debian binary package was auto-generated by the /usr/share/debmake/extra0desc_long/_long- debmake(1) command provided by the debmake package. -- /usr/share/debmake/extra0desc_long/_long_tutorial: This Debian binary package was auto-generated by the /usr/share/debmake/extra0desc_long/_long_tutorial- debmake(1) command provided by the debmake package. /usr/share/debmake/extra0desc_long/_long_tutorial- . /usr/share/debmake/extra0desc_long/_long_tutorial- = This comes from the unmodified template file = /usr/share/debmake/extra0desc_long/_long_tutorial- . /usr/share/debmake/extra0desc_long/_long_tutorial- Please edit this template file (debian/control) and other package files -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1028697: marked as pending in pydispatcher
Control: tag -1 pending Hello, Bug #1028697 in pydispatcher 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/pydispatcher/-/commit/e80bfbc79f96c00cad6438fbd53a2974dcfb9a07 Fix documentation build with Python 3.11. (Closes: #1028697) (this message was generated automatically) -- Greetings https://bugs.debian.org/1028697
Bug#1026781: pkgconf: breaks adequate missing-pkgconfig-dependency check due to behaviour change in: pkg-config --exists --print-errors
Package: pkgconf
Severity: serious
When a pkg doesn't have its dependencies satisfied, pkgconf --cflags
etc all print an error message and return a failure exit code.
With pkg-config, --exists does this check too, exits with an error and
with --print-errors present, prints the same error as --cflags etc do.
With pkgconf, --exists exits with an error only when the .pc file
doesn't actually exist, so I think it doesn't check if dependencies
are satisfied either, since with --print-errors no errors are printed.
This breaks the adequate test missing-pkgconfig-dependency, which runs
pkg-config and parses the output for errors about missing dependencies,
see below for the code that does this parsing.
pkg-config --exists --print-errors foo
An example of the behaviour under pkg-config:
$ pkg-config --exists --print-errors mpv ; echo $?
Package wayland-protocols was not found in the pkg-config search path.
Perhaps you should add the directory containing `wayland-protocols.pc'
to the PKG_CONFIG_PATH environment variable
Package 'wayland-protocols', required by 'mpv', not found
1
An example of the behaviour under pkgconf:
$ pkgconf --exists --print-errors mpv ; echo $?
0
$ pkgconf --cflags mpv ; echo $?
Package wayland-protocols was not found in the pkg-config search path.
Perhaps you should add the directory containing `wayland-protocols.pc'
to the PKG_CONFIG_PATH environment variable
Package 'wayland-protocols', required by 'mpv', not found
1
This is the bug that lead me to this pkgconf bug:
https://bugs.debian.org/1026624
Here is the code from adequate that performs this check,
please ensure that the error message matches the regex below.
$ dgrep -EC4 pkg-?conf adequate
/usr/bin/adequate- check_elfs(%file_map);
/usr/bin/adequate- check_paths(%file_map);
/usr/bin/adequate- check_alternatives(\%package_map, \%file_map);
/usr/bin/adequate- check_binfmts(@packages);
/usr/bin/adequate: check_pkgconfig(%file_map);
/usr/bin/adequate- flush_debconf();
/usr/bin/adequate- return;
/usr/bin/adequate-}
/usr/bin/adequate-
--
/usr/bin/adequate- }
/usr/bin/adequate- return;
/usr/bin/adequate-}
/usr/bin/adequate-
/usr/bin/adequate:sub check_pkgconfig
/usr/bin/adequate:: Tags(qw(missing-pkgconfig-dependency))
/usr/bin/adequate-{
/usr/bin/adequate- my %file_map = @_;
/usr/bin/adequate- my %pkg_map = ();
/usr/bin/adequate: -x '/usr/bin/pkg-config' or return;
/usr/bin/adequate- while (my ($debpkg, $files) = each %file_map) {
/usr/bin/adequate- for my $file (@{$files}) {
/usr/bin/adequate: $file =~
m{^/usr/(?:share|lib(?:/[^/]+)?)/pkgconfig/([^/]+)[.]pc$} or next;
/usr/bin/adequate- my $pkg = $1;
/usr/bin/adequate- $pkg_map{$pkg} = $debpkg;
/usr/bin/adequate- }
/usr/bin/adequate- }
/usr/bin/adequate- while (my ($pkg, $debpkg) = each %pkg_map) {
/usr/bin/adequate- local $ENV{LC_ALL} = 'C';
/usr/bin/adequate- flush_std_fh();
/usr/bin/adequate: my $pkgconfig_pid = open(my $pkgconfig, '-|') //
die "can't fork: $ERRNO";
/usr/bin/adequate: if ($pkgconfig_pid) { # parent
/usr/bin/adequate: while (<$pkgconfig>) {
/usr/bin/adequate- if (m/^Package '(.+)', required by
'\Q$pkg\E', not found$/) {
/usr/bin/adequate- my $deppkg = $1;
/usr/bin/adequate: tag $debpkg,
'missing-pkgconfig-dependency', $pkg, '=>', $deppkg;
/usr/bin/adequate- }
/usr/bin/adequate- }
/usr/bin/adequate: wait or die "pkg-config --exists: $ERRNO";
/usr/bin/adequate: close $pkgconfig; ## no critic
(CheckedSyscalls)
/usr/bin/adequate- } else { # child
/usr/bin/adequate- open(STDERR, '>') or die "can't
redirect stderr: $ERRNO";
/usr/bin/adequate: exec('pkg-config', '--exists',
'--print-errors', $pkg);
/usr/bin/adequate: die "can't exec pkg-config: $ERRNO";
/usr/bin/adequate- }
/usr/bin/adequate- }
/usr/bin/adequate- return;
/usr/bin/adequate-}
-- System Information:
Debian Release: bookworm/sid
APT prefers testing-debug
APT policy: (900, 'testing-debug'), (900, 'testing'), (800,
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700,
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
merged-usr: no
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_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages pkgconf depends on:
ii pkgconf-bin 1.8.0-11
pkgconf recommends no packages.
pkgconf suggests
Bug#1026624: mpv-mpris: FTBFS: mpris.c:1:10: fatal error: gio/gio.h: No such file or directory
Control: reassign -1 libmpv-dev Control: affects -1 src:mpv-mpris Control: retitle -1 libmpv-dev: missing dependency on wayland-protocols On Tue, 2022-12-20 at 18:16 +0100, Lucas Nussbaum wrote: > [mpv-mpris] failed to build on amd64. > > Relevant part (hopefully): ... > > Package wayland-protocols was not found in the pkg-config search path. > > Perhaps you should add the directory containing `wayland-protocols.pc' > > to the PKG_CONFIG_PATH environment variable > > Package 'wayland-protocols', required by 'mpv', not found This is a bug in libmpv-dev, it should dep on wayland-protocols: # pkg-config --cflags mpv Package wayland-protocols was not found in the pkg-config search path. Perhaps you should add the directory containing `wayland-protocols.pc' to the PKG_CONFIG_PATH environment variable Package 'wayland-protocols', required by 'mpv', not found # apt install wayland-protocols Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: wayland-protocols 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 71.8 kB of archives. After this operation, 549 kB of additional disk space will be used. Get:1 https://deb.debian.org/debian sid/main amd64 wayland-protocols all 1.27-1 [71.8 kB] Fetched 71.8 kB in 0s (243 kB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package wayland-protocols. (Reading database ... 24263 files and directories currently installed.) Preparing to unpack .../wayland-protocols_1.27-1_all.deb ... Unpacking wayland-protocols (1.27-1) ... Setting up wayland-protocols (1.27-1) ... # pkg-config --cflags mpv -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/uuid -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/fribidi -I/usr/include/x86_64-linux-gnu -I/usr/include/libxml2 -I/usr/include/lua5.2 -I/usr/include/SDL2 -I/usr/include/uchardet -I/usr/include/pipewire-0.3 -I/usr/include/spa-0.2 -D_REENTRANT -I/usr/include/libdrm -I/usr/include/sixel -I/usr/include/spirv_cross # grep wayland-protocols /usr/lib/x86_64-linux-gnu/pkgconfig/mpv.pc Requires.private: wayland-client >= 1.15.0, libass >= 0.12.2, libavcodec >= 58.12.100, libavfilter >= 7.14.100, libavformat >= 58.9.100, libavutil >= 56.12.100, libswresample >= 3.0.100, libswscale >= 5.0.101, libcdio_paranoia, dvdnav >= 4.2.0, dvdread >= 4.1.0, mujs >= 1.0.0, lcms2 >= 2.6, libarchive >= 3.4.0, libavdevice >= 57.0.0, libbluray >= 0.3.0, lua52 >= 5.2.0, rubberband >= 1.8.0, sdl2, uchardet, zimg >= 2.9, zlib, alsa >= 1.0.18, jack, libpipewire-0.3 >= 0.3.19, libpulse >= 1.0, caca >= 0.99.beta18, libdrm >= 2.4.75, gbm >= 17.1.0, libjpeg, libplacebo >= 4.157.0, libsixel >= 1.5, spirv-cross-c-shared, wayland-cursor >= 1.15.0, wayland-protocols >= 1.15, xkbcommon >= 0.3.0, x11 >= 1.0.0, xscrnsaver >= 1.0.0, xext >= 1.0.0, xinerama >= 1.0.0, xpresent >= 1.0.0, xrandr >= 1.2.0, xv, egl > 1.4.0, wayland-egl >= 9.0.0, vulkan, ffnvcodec >= 8.2.15.7, libva >= 1.1.0, libva-drm >= 1.1.0, libva-wayland >= 1.1.0, libva-x11 >= 1.1.0, vdpau >= 0.2 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1025739: Is an autogenerated configure shell script non-editable source
On Sat, 2022-12-10 at 10:28 +0100, Andreas Tille wrote: > So far for the actual case (bug report in CC). > > For the general case I somehow understand the consensus here on the list > that a missing configure.ac can be considered a bug but the severity > serious is not really rectified. If I understood this correctly I would > reset the severity to important at the beginning of next week. Personally I feel that severity serious is the correct one, but it sounds like the fix for the bug is quite simple: https://lists.debian.org/msgid-search/y5rir8qidvj4r...@argenau.bebt.de -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1024106: traceshark: QCustomPlot transition
On Tue, 15 Nov 2022 09:58:37 + Sudip Mukherjee wrote: > I think this should not have "Severity: serious" yet. The qcustomplot > transition has not yet started. imho, It will start when Sebastian > confirms and its uploaded to unstable and then these are serious > severity. The transition has started, it would be good to get traceshark fixed. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1025661: rust-plotters: invalid Uploaders field: missing comma between Jelmer Vernooij and Blair Noctis
Source: rust-plotters Version: 0.3.4-1 Severity: serious rust-plotters 0.3.4-1 introduced an invalid Uploaders field, that is missing a comma between Jelmer Vernooij and Blair Noctis. $ apt-cache showsrc rust-plotters | grep -E '^$|^Version|^Uploaders' Version: 0.3.4-1 Uploaders: Jelmer Vernooij Blair Noctis According to Debian policy 5.6.3 the Uploaders field must separate individual uploaders using commas: List of the names and email addresses of co-maintainers of the package, if any. ... The format of each entry is the same as that of the Maintainer field, and multiple entries must be comma separated. https://www.debian.org/doc/debian-policy/ch-controlfields.html#uploaders This is causing the DDPO and BLS cron jobs to send error mails, please fix it as soon as possible. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1023978: scikit-learn: FTBFS with Python 3.11 as a supported version
Control: tags -1 + fixed-upstream patch Control: forwarded -1 https://github.com/scikit-learn/scikit-learn/commit/63f92d4adb61aed58d656544cc6caa9d68cb6065 On Sun, 13 Nov 2022 12:26:18 + Graham Inggs wrote: > scikit-learn FTBFS with Python 3.11 as a supported version. I noticed that upstream has some commits adding 3.11 support, but none of them seem like they would fix the build failure. Looking at the changes to the file with the failing test I found the commit above and then confirmed that this hunk from it fixes the build. --- a/sklearn/datasets/tests/test_lfw.py +++ b/sklearn/datasets/tests/test_lfw.py @@ -84,8 +84,8 @@ def setup_module(): for i in range(5): first_name, second_name = random_state.sample(FAKE_NAMES, 2) -first_index = random_state.choice(np.arange(counts[first_name])) -second_index = random_state.choice(np.arange(counts[second_name])) +first_index = np_rng.choice(np.arange(counts[first_name])) +second_index = np_rng.choice(np.arange(counts[second_name])) f.write( ( "%s\t%d\t%s\t%d\n" -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#984149: Bug#1024209: genparse: Fix ftbfs: Use "std=c++14" flag to build
close 1024209 tags 984149 + patch user debian-ri...@lists.debian.org usertags 1024209 - riscv64 thanks On Wed, 2022-11-16 at 11:58 +0800, Yifan Xu wrote: > To: Debian Bug Tracking System > Followup-For: Bug #984149 Please submit followups for existing bug reports to the existing bugs instead of submitting new bug reports containing the followups. I have forwarded your mail to bug #984149 just now: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984149#16 > User: debian-ri...@lists.debian.org > Usertags: riscv64 > X-Debbugs-Cc: debian-ri...@lists.debian.org This bug isn't riscv64-specific so you should not add the riscv64 usertags and should not CC the debian-riscv mailing list. > Dear Maintainer, I note that this package is orphaned so it doesn't have a maintainer. https://tracker.debian.org/pkg/genparse I also note that the upstream of this package isn't very active: https://sourceforge.net/p/genparse/ > This patch will make this package build with C++14 standard, as this package > doesn`t install any header files in /usr/include, so this patch should be OK. When submitting patches to the BTS, it is a good idea to mark the bug as having a patch using the patch tag. Add this to the pseudo-headers: Control: tags -1 + patch https://www.debian.org/Bugs/Reporting#control https://www.debian.org/Bugs/server-control#tag https://www.debian.org/Bugs/Developer#tags The patch to debian/rules seems like it should have been made to the upstream build system so both patches could be sent upstream instead. In addition both patches are workarounds not proper fixes, since they switch the package to an older version of C++ instead of fixing it to work with the current version of C++. Since this package is orphaned in Debian, unmaintained upstream, nothing in Debian seems to depend on it and fails to build with current versions of its build dependencies, perhaps it should be just removed from Debian instead of fixing it? If you agree, please file a removal: https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#removing-packages -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#984149: Fwd: Bug#984149: genparse: Fix ftbfs: Use "std=c++14" flag to build
Forwarding a response that went to the wrong place.
--
bye,
pabs
https://wiki.debian.org/PaulWise
--- Begin Message ---
Source: genparse
Version: 0.9.2-1
Followup-For: Bug #984149
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org
Dear Maintainer,
This patch will make this package build with C++14 standard, as this package
doesn`t install any header files in /usr/include, so this patch should be OK.
I tried build on amd64/riscv64 and both succeed with this patch.
Thanks,
Yifan Xu
--- rules 2016-11-10 20:18:01.0 +0800
+++ genparse-0.9.2/debian/rules 2022-11-15 17:59:38.254170492 +0800
@@ -4,6 +4,7 @@
export DEB_BUILD_MAINT_OPTIONS = hardening=+all
export DEB_CFLAGS_MAINT_APPEND = -Wall -pedantic
+export DEB_CPPFLAGS_MAINT_APPEND = -std=c++14
export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
RM = \
Description: fix ftbfs: use std=c++14 flag to build
.
genparse (0.9.2-2) unstable; urgency=medium
.
* Add -std=c++14 flag
Author: Yifan Xu
---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:
Bug-Debian: https://bugs.debian.org/984149
Last-Update: 2022-11-15
--- genparse-0.9.2.orig/tests/misc/test-lib.sh
+++ genparse-0.9.2/tests/misc/test-lib.sh
@@ -27,7 +27,7 @@ error_() { echo "$0: $@" 1>&2; exit 1; }
framework_failure() { error_ 'failure in testing framework'; }
CFLAGS=-I.
-CXXFLAGS=-I.
+CXXFLAGS="-std=c++14 -I."
GNULIB_CPPFLAGS=-I$srcdir/../../gnulib/lib
GNULIB_LDFLAGS="-L../../gnulib/lib -lgnu"
--- End Message ---
signature.asc
Description: This is a digitally signed message part
Bug#1023529: subversion: FTBFS: segfault in Python tests with SWIG 4.1.0
Source: subversion Version: 1.14.2-3 Severity: serious Tags: ftbfs patch fixed-upstream Forwarded: https://github.com/swig/swig/issues/2373 https://github.com/apache/subversion/commit/8ff4cfd06ce554e9df31a088c9d09f45278c6de4 https://svn.apache.org/repos/asf/subversion/trunk@1904167 subversion FTBFS in sid (on all arches, but detected below on amd64 and by the buildds on riscv64) due to a segfault in the Python tests when building with SWIG 4.1.0. The issue has been fixed upstream in the subversion git/svn repos, see the URLs above. pabs@barriere:~$ dd-schroot-cmd -y -c $sessionid apt-get build-dep subversion ... Get:286 https://deb.debian.org/debian sid/main amd64 swig4.0 amd64 4.1.0-0.1 [1387 kB] Get:287 https://deb.debian.org/debian sid/main amd64 swig all 4.1.0-0.1 [321 kB] ... Selecting previously unselected package swig4.0. Preparing to unpack .../285-swig4.0_4.1.0-0.1_amd64.deb ... Unpacking swig4.0 (4.1.0-0.1) ... Selecting previously unselected package swig. Preparing to unpack .../286-swig_4.1.0-0.1_all.deb ... Unpacking swig (4.1.0-0.1) ... ... Setting up swig4.0 (4.1.0-0.1) ... ... Setting up swig (4.1.0-0.1) ... ... pabs@barriere:~$ schroot -r -c $sessionid (sid_amd64-dchroot)pabs@barriere:~$ apt source subversion ... (sid_amd64-dchroot)pabs@barriere:~$ cd subversion-*/ (sid_amd64-dchroot)pabs@barriere:~/subversion-1.14.2$ debuild -J10 ... finished... make[2]: Leaving directory '/home/pabs/subversion-1.14.2/BUILD' make[1]: Leaving directory '/home/pabs/subversion-1.14.2' debian/rules override_dh_auto_test-arch make[1]: Entering directory '/home/pabs/subversion-1.14.2' /usr/bin/make -f debian/rules check-swig-py check-swig-pl check-swig-rb check-javahl check make[2]: Entering directory '/home/pabs/subversion-1.14.2' make[2]: warning: -j10 forced in makefile: resetting jobserver mode. set -e; for v in 3.10; do rm -f /home/pabs/subversion-1.14.2/BUILD/subversion/bindings/swig/python; ln -sfT python$v /home/pabs/subversion-1.14.2/BUILD/subversion/bindings/swig/python; pyinc=$(python$v-config --includes); pylib=$(python$v -c 'from distutils import sysconfig; print(sysconfig.get_python_lib())'); /usr/bin/make -C /home/pabs/subversion-1.14.2/BUILD LTFLAGS="--tag=CC --verbose" LTCXXFLAGS="--tag=CXX --verbose" check-swig-py PYTHON=python$v PYVER=$v CLEANUP=1 LC_ALL=C; ln -sfT python3.10 /home/pabs/subversion-1.14.2/BUILD/subversion/bindings/swig/python; done :1: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives :1: DeprecationWarning: The distutils.sysconfig module is deprecated, use sysconfig instead make[3]: Entering directory '/home/pabs/subversion-1.14.2' make[3]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. mkdir /home/pabs/subversion-1.14.2/BUILD/subversion/bindings/swig/python/libsvn if [ "LD_LIBRARY_PATH" = "DYLD_LIBRARY_PATH" ]; then for d in /home/pabs/subversion-1.14.2/BUILD/subversion/bindings/swig/python/libsvn_swig_py /home/pabs/subversion-1.14.2/BUILD/subversion/bindings/swig/python/../../../libsvn_*; do if [ -n "$DYLD_LIBRARY_PATH" ]; then LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$d/.libs"; else LD_LIBRARY_PATH="$d/.libs"; fi; done; export LD_LIBRARY_PATH; fi; \ cd /home/pabs/subversion-1.14.2/BUILD/subversion/bindings/swig/python; \ python3.10 /home/pabs/subversion-1.14.2/BUILD/../subversion/bindings/swig/python/tests/run_all.py make[3]: *** [Makefile:944: check-swig-py] Segmentation fault make[3]: Leaving directory '/home/pabs/subversion-1.14.2/BUILD' make[2]: *** [debian/rules:252: check-swig-py] Error 2 make[2]: Leaving directory '/home/pabs/subversion-1.14.2' make[1]: *** [debian/rules:232: override_dh_auto_test-arch] Error 2 make[1]: Leaving directory '/home/pabs/subversion-1.14.2' make: *** [debian/rules:197: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 debuild: fatal error at line 1182: dpkg-buildpackage -us -uc -ui -J10 failed -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1019812: wxhexeditor: Please transition to wxwidgets3.2
Control: tags -1 + fixed-upstream patch Control: forwarded -1 https://github.com/EUA/wxHexEditor/commit/28151fc64cb6d01a08dc80ef750d4bca96c147e7 https://github.com/EUA/wxHexEditor/commit/ebe2449fac22089825d124935a215fd1c0739403 On Wed, 14 Sep 2022 15:42:16 -0400 Scott Talbert wrote: > Please transition wxhexeditor from wxwidgets3.0 to wxwidgets3.2. This causes a build failure due to WX_CLEAR_ARRAY calls not having a terminating semicolon in the version in Debian. Fixing those makes the package build and I have tested that the package works afterwards. The missing semicolons are fixed in the two upstream commits above. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1022102: rust-linux-raw-sys: invalid Uploaders field: missing name
Source: rust-linux-raw-sys
Version: 0.0.46-1
Severity: serious
Usertags: uploaders
rust-linux-raw-sys 0.0.46-1 introduced an invalid Uploaders field,
that is missing the name for the uploader .
$ apt-cache showsrc rust-linux-raw-sys | grep -E '^$|^Version|^Uploaders'
Version: 0.0.46-1
Uploaders:
According to Debian policy 5.6.3 the Uploaders field must include both
names and email addresses:
List of the names and email addresses of co-maintainers of the
package, if any.
https://www.debian.org/doc/debian-policy/ch-controlfields.html#uploaders
This is causing the DDPO and BLS cron jobs to send error mails,
please fix it as soon as possible.
Subject: Cron nice -15 flock -n /srv/qa.debian.org/lock/ddpo
/srv/qa.debian.org/data/cronjobs/ddpo
Uploader without name: rust-linux-raw-sys at
../extract_archive.pl line 122.
Use of uninitialized value in concatenation (.) or string at
../extract_archive.pl line 201.
Cron nice -15 flock -n /srv/qa.debian.org/lock/bls
/srv/qa.debian.org/data/cronjobs/bls
Cannot parse uploader «
» from package ('rust-linux-raw-sys', 0, 1, 0, 0)
-- System Information:
Debian Release: bookworm/sid
APT prefers testing-debug
APT policy: (900, 'testing-debug'), (900, 'testing'), (800,
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700,
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Bug#1020885: libshumate-1.0-1: move pkg-config file to the -dev package
Package: libshumate-1.0-1 Version: 1.0.1-1 Control: found -1 1.0.0~alpha.1-1 Severity: serious File: /usr/lib/x86_64-linux-gnu/pkgconfig/shumate-1.0.pc User: debian...@lists.debian.org Usertags: adequate missing-pkgconfig-dependency The shumate-1.0.pc file should be moved from the libshumate-1.0-1 package to the libshumate-dev package, since the shumate-1.0.pc is only used at compile time. This issue has been present since version 1.0.0~alpha.1-1 according to the binary packages available on the snapshot.debian.org service. from the release team advised me on #debian-gnome that this issue represents a serious issue, hence the severity above. This issue was detected by adequate, hence the usertags above. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libshumate-1.0-1 depends on: ii libc62.34-8 ii libcairo21.16.0-6 ii libgdk-pixbuf-2.0-0 2.42.9+dfsg-1 ii libglib2.0-0 2.74.0-1 ii libgraphene-1.0-01.10.8-1 ii libgtk-4-1 4.8.1+ds-1 ii libshumate-common1.0.1-1 ii libsoup-3.0-03.2.0-1 ii libsqlite3-0 3.39.3-1 libshumate-1.0-1 recommends no packages. libshumate-1.0-1 suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1017313: postfix: FTBFS: unistd.h:363:13: error: conflicting types for ‘closefrom’; have ‘void(int)’
On Fri, 2022-09-23 at 10:45 -0400, Antoine Beaupré wrote: > Would this patch cut it? Not sure where to forward this upstream > either... I think the problem is that HAS_CLOSEFROM is not getting defined even though the unistd.h header clearly has closefrom(). That should be fixed first. Of course the definition of the compat function should be changed to match the common definitions of closefrom() too. Your patch is missing changing the definition and implementation of closefrom in sys_compat.c, currently it is defined as returning an int and does return -1 on errors, 0 on success. PS: I note that closefrom is not in POSIX, maybe postfix should be closing individual files more manually or using close_range instead. https://www.gnu.org/software/libc/manual/html_node/Opening-and-Closing-Files.html#index-closefrom https://www.gnu.org/software//gnulib/manual/html_node/closefrom.html -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1019721: libopenmpi-dev: Cannot uninstall rmdir: failed to remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such file or directory
On Wed, 2022-09-14 at 07:41 +0200, Andreas Metzler wrote: > Is there a way to find all packages built against broken dh-fortran- > mod so all affected packages can be rebuilt? I am not sure of the correct regex, but the binary package control search should work, if it doesn't then you need a local mirror: https://binarycontrol.debian.net/?q=%2Fusr%2Flib%2F%5C%24multiarch%2Ffortran%2Fgfortran= -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1016362: ncbi-igblast: invalid Uploaders field: missing comma between David Miguel Susano Pinto and Steffen Moeller
Source: ncbi-igblast Version: 1.18.0-1 Severity: serious Usertags: uploaders ncbi-igblast 1.18.0-1 introduced an invalid Uploaders field, that is missing a comma between David Miguel Susano Pinto and Steffen Moeller. $ apt-cache showsrc ncbi-igblast | grep -E '^$|^Version|^Uploaders' Version: 1.18.0-1 Uploaders: David Miguel Susano Pinto Steffen Moeller According to Debian policy 5.6.3 the Uploaders field must separate individual uploaders using commas: List of the names and email addresses of co-maintainers of the package, if any. ... The format of each entry is the same as that of the Maintainer field, and multiple entries must be comma separated. https://www.debian.org/doc/debian-policy/ch-controlfields.html#uploaders This is causing the DDPO and BLS cron jobs to send error mails, please fix it as soon as possible. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#938850: unarchiving 938850, reopening 938850, unarchiving 947278, reopening 947278
Control: close 991543 1.0~prerelease-2+rm
Control: close 947278 1.0~prerelease-2+rm
Control: close 938850 1.0~prerelease-2+rm
On Thu, 2022-07-28 at 01:19 +0200, Chris Hofstaedtler wrote:
> Not sure how you determined this
I have a pair of scripts (attached) and a crontab for this:
cd ~/.cache/detect-reintroduced-packages
cat /var/lib/apt/lists/*.debian.org_*_dists_*_*_source_Sources > Sources
cp Sources Sources.old.tmp
debian-reopen-reintroduced-bugs
mv Sources.old.tmp Sources.old
> it looks like src:xmlelements is not in unstable/experimental now?
https://tracker.debian.org/news/1257974/removed-10prerelease-2-from-experimental/
> Maybe the bugs want to be closed again?
Not sure why ftp-master didn't do that. Agreed, doing so above
and also closing the additional bug that got filed too.
--
bye,
pabs
https://wiki.debian.org/PaulWise
debian-reopen-reintroduced-bugs
Description: application/shellscript
#!/usr/bin/python3
# pabs got this from themill on #debian-devel 2020-05
# written by Stuart Prescott
import sys
from typing import List, Dict
from debian.deb822 import Sources, Removals
def source_packages(filename: str) -> List[str]:
with open(filename) as fh:
source_pkgs = []
for s in Sources.iter_paragraphs(fh):
if s.get('Extra-Source-Only') == 'yes':
continue
source_pkgs.append(s['Source'] if 'Source' in s else s['Package'])
return source_pkgs
def removed_packages(filename: str) -> Dict[str, str]:
with open(filename) as fh:
removed_pkgs: List[Dict[str, str]] = []
for r in Removals.iter_paragraphs(fh):
if 'sources' not in r:
continue
if r['suite'] == 'unstable':
removed_pkgs.extend(r.sources)
return {r['source']: r for r in removed_pkgs}
old_sources = source_packages('Sources.old')
new_sources = source_packages('Sources')
added_sources = set(new_sources) - set(old_sources)
if not added_sources:
sys.exit(0)
rm_sources = removed_packages('removals-full.822')
reintroduced_sources = [s for s in added_sources if s in rm_sources]
if reintroduced_sources:
print("Found reintroduced sources:")
for s in reintroduced_sources:
if 'also-bugs' in rm_sources[s]:
extra_msg = 'extra triage needed'
else:
extra_msg = ''
print(" {source}/{version}{extra}".format(
source=s,
extra=extra_msg,
version=rm_sources[s]['version'],
))
sys.exit(1)
signature.asc
Description: This is a digitally signed message part
Bug#1012895: aptitude: ftbfs with GCC-12
On Tue, 2022-07-26 at 00:28 +0200, Axel Beckert wrote: > Paul Wise wrote: > > I tried to build aptitude, found it fails due to cwidget bug #1015925. > > Do you intend to NMU that? I'd prefer the cwidget team take care of it, since I don't have access to their VCS, but if they don't have time right now, then I can do it. > > and has debian/patches/ > > Correct, this is mostly used for short-term fixes. Hmm, OK. I would have expected these would go into new upstream point releases, like 0.8.13.1 or similar. > > that seems to be unused. > > Not really true. It's just that we haven't made a real "upstream" > release for quite a while because Manuel is mostly busy with the RISC > V port. > ... I see, thanks for the info. > As far I understood, it doesn't make sense to upload a new aptitude > package before #1015925 is fixed. Agreed. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1015028: celery: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13
Control: tags -1 + fixed-upstream patch Control: forwarded -1 https://github.com/celery/celery/commit/b260860988469ef8ad74f2d4225839c2fa91d590 Control: retitle -1 celery: FTBFS: test failures due to billiard upgrade: ImportError: cannot import name 'buf_t' from 'billiard.compat' On Sat, 16 Jul 2022 15:41:55 +0200 Lucas Nussbaum wrote: > > > from billiard.compat import buf_t, isblocking, setblocking > > E ImportError: cannot import name 'buf_t' from 'billiard.compat' > > (/usr/lib/python3/dist-packages/billiard/compat.py) This issue was caused by the update of python3-billiard to 4.0.0-1 and is fixed in celery upstream alpha version v5.3.0a1. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1015029: marked as pending in tldextract
Control: tag -1 pending Hello, Bug #1015029 in tldextract 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-tldextract/-/commit/0c3de2413e8759795eafdde4d3662b184832c4eb Manually clean _version.py since pybuild doesn't yet (Closes: #1015029) (this message was generated automatically) -- Greetings https://bugs.debian.org/1015029
Bug#1012895: aptitude: ftbfs with GCC-12
Control: tags -1 + patch On Thu, 16 Jun 2022 12:07:38 + Matthias Klose wrote: > The package fails to build in a test rebuild on at least amd64 with > gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The > severity of this report will be raised before the bookworm release. I tried to build aptitude, found it fails due to cwidget bug #1015925. I tried to look at this failure, which also happens after fixing that. I don't know enough C++ but seems that the operator<< function in the test_parsers.cc file taking std::optional as a parameter is not being found by GCC 12 even though it should be found. The g++ output was verbose but the clang++ output was very clear. The issue is that the operator<< functions are not declared before the call site, so forward declarations before HelperMacros.h are needed: #include template std::ostream <<(std::ostream , const std::optional o); template std::ostream <<(std::ostream , const std::vector v); #include I'm not sure how to contribute this change to the package because this should be a native package but isn't and has debian/patches/ but also an upstream master branch that seems to be unused. I suggest merging the contents of debian/patches/ to the upstream master branch and then cherry-picking the FTBFS patches to a new minor release branch instead of using debian/patches/. I've filed two merge requests with two different approaches, one is a commit for the master branch and one a patch for the debian-sid branch. https://salsa.debian.org/apt-team/aptitude/-/merge_requests/14 https://salsa.debian.org/apt-team/aptitude/-/merge_requests/13 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1015925: libcwidget-dev: causes aptitude FTBFS due to missing #include
Package: libcwidget-dev Version: 0.5.18-5 Severity: serious File: /usr/include/cwidget/generic/threads/threads.h The threads.h file in libcwidget-dev uses various pthread_* functions but does not #include , which means that aptitude and any other application using that header but not #include will FTBFS because the pthread_* functions are not able to be found. This bug appears to have been exposed by the change from GCC 11 to 12 in Debian unstable, since aptitude does not FTBFS in Debian bookworm. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libcwidget-dev depends on: ii libcwidget40.5.18-5 ii libncurses-dev [libncursesw5-dev] 6.3+20220423-2 pn libsigc++-2.0-dev ii pkg-config 0.29.2-1 libcwidget-dev recommends no packages. Versions of packages libcwidget-dev suggests: pn libcwidget-doc -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1012077: linuxinfo FTBFS on riscv64
Control: severity -1 important On Sun, 29 May 2022 14:45:29 -0400 Alan Beadle wrote: > Package: linuxinfo > Severity: serious > Tags: ftbfs patch upstream > Justification: fails to build from source ... > linuxinfo currently fails to build on riscv64 Please note that FTBFS bugs on unofficial non-release arches like riscv64 are not RC and so should only be filed at important severity. Please note that bugs in specific Debian architectures should be usertagged properly and XCCed to the architecture mailing list. Thanks for xiao sheng wen(肖盛文) for fixing this particular bug. https://wiki.debian.org/Teams/Debbugs/ArchitectureTags https://www.debian.org/Bugs/Reporting#xcc -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1010998: simh: Upstream license change conflicts with DFSG
Control: forwarded -1 https://groups.io/g/simh/topic/new_license/91108560 Control: notfound -1 3.8.1-6.1 Control: found -1 3.8.12-1 On Sat, 14 May 2022 17:27:33 -0400 Joan Touzet wrote: > Package: simh > Version: 3.8.1-6.1 ... > Upstream has added licensing information that is both inaccurate as well as > now > violates the terms of the DFSG. The change isn't present in the version in Debian, fixing the versions. https://github.com/simh/simh/commits/master/LICENSE.txt https://github.com/simh/simh/tags Debian doesn't even appear to use the GitHub version of simh: https://sources.debian.org/src/simh/3.8.1-6.1/debian/watch/ https://sources.debian.org/src/simh/3.8.1-6.1/debian/copyright/ > If this package is to remain in debian, it will need to move to the non-free > section. Or just not get updated or switch to a fork of simh that was made from the commit just before the license change. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1001209: dnsmasq: Regression: Fails to direct queries to 127.0.1.1#10053
Control: forwarded -1 https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=089a11f3400485f215f5e29c77e41d7730f2c806 Control: tags -1 + fixed-upstream On Fri, 10 Dec 2021 20:48:18 +0100 Sven Mueller wrote: > judging from the Dnsmasq list, the problem is that --local is > supposed to > be an alias for --server, but the recent rewrite of the address logic > apparently made it an alias of --adress instead. ... > Basically, AFAICT, this boils down to: > Make --local a proper alias for --server again. Looking at the upstream git repository, this is fixed upstream in commit 089a11f34 from 2021-10-05 and tag v2.87test4 according to: https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=shortlog#:~:text=--local I note there is also a CVE fix in the recent commits. https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=03345ecefeb0d82e3c3a4c28f27c3554f0611b39 Simon, could you release 2.87 and upload it to Debian please? Otherwise dnsmasq will be removed from Debian bookworm. https://tracker.debian.org/pkg/dnsmasq https://udd.debian.org/cgi-bin/autoremovals.cgi If you don't have time then I can upload a test release. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1008556: gnome-shell-extension-sound-device-chooser: does not declare compatibility with GNOME Shell 42
Control: tags -1 + fixed-upstream On Mon, 28 Mar 2022 16:36:23 +0100 Simon McVittie wrote: > Forwarded: > https://github.com/kgshank/gse-sound-output-device-chooser/issues/229 Upstream has now made a new release fixing this issue. Please update the Debian package to the new upstream release. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1008041: wmforecast: invalid Uploaders field: missing comma between Doug Torrance and Andreas Metzler
Source: wmforecast Version: 1.8-1 Severity: serious Usertags: uploaders wmforecast 1.8-1 introduced an invalid Uploaders field, that is missing a comma between Doug Torrance and Andreas Metzler. $ apt-cache showsrc wmforecast | grep -E '^$|^Version|^Uploaders' Version: 1.7-1.1 Uploaders: Doug Torrance , Andreas Metzler Version: 1.8-1 Uploaders: Doug Torrance Andreas Metzler According to Debian policy 5.6.3 the Uploaders field must separate individual uploaders using commas: List of the names and email addresses of co-maintainers of the package, if any. ... The format of each entry is the same as that of the Maintainer field, and multiple entries must be comma separated. https://www.debian.org/doc/debian-policy/ch-controlfields.html#uploaders This is causing the DDPO and BLS cron jobs to send error mails, please fix it as soon as possible. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#969885: megadown: [python] is required and it's not installed
On Tue, 08 Sep 2020 12:53:00 +0200 Jan Gerber wrote: > in sid /usr/bin/python no longer exists, must be python2 or python3 > dependency is on python3:any but the script calls python not python3: > > [python] is required and it's not installed > > ERROR: there are dependencies not present! The latest upstream version relaxes this to a warning and in addition the switch to python is trivial, just replace "python" with "python3". -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1007941: megadown: Should we remove this package?
On Fri, 18 Mar 2022 20:06:14 -0400 Boyuan Yang wrote: > The package you maintain (megadown, https://tracker.debian.org/pkg/megadown ) > has a longstanding release-critical bug (depends on removed python2), which > made the package unusable. In the latest upstream version the package only needs Python 2 for MegaCrypter password protected links, not in general and in addition the fix for using Python 3 is trivial: s/python/python3/ -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1005953: needrestart: user session restart needing detection broken probably by cgroupv2 from systemd 247.2-4
Control: severity -1 important On Fri, 18 Feb 2022 09:42:03 +0800 Paul Wise wrote: > I've filed this at severity serious because it means that the user > notification scripts in the needrestart package don't work, which means > the needrestart-session package is not very useful any more. It seems this bug is going to cause autoremoval on April 3rd. The inclusion of needrestart in Debian in general is more important than the user session functionality. The needrestart-session package has a GUI tool that can be run manually, so it doesn't become entirely useless. For these reasons I am decreasing the severity of this bug. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1000229: binary package is missing /usr/sbin/memlockd
Control: tags -1 + patch pending On Fri, 19 Nov 2021 23:02:53 +0100 Sven Hartge wrote: > The subject says it all: The package is missing the binary: This is caused by the install target in debian/rules doing things manually instead of leaving everything to dh_* scripts and configuration files for them, which means that an arch-any build with dpkg-buildpackage -B does not run the debian/rules install target. I've attached a patch for a minimal NMU that fixes the issue and I have uploaded that NMU to Debian with a 7 days delay. Please either incorporate the patch into your next upload or reschedule the NMU to occur as soon as possible. Note that after applying the patch you will need to delete debian/memlockd-default, since the debdiff doesn't seem to include removal of the file somehow. I note this package needs a lot of polish. There are a lot of low priority but trivial to fix lintian warnings. There are a lot of unnecessary comments in the debian/ directory. The debian/docs file is empty and can be deleted. The debian/dirs file can be deleted, debhelper creates dirs as needed. The debian/copyright looks very out of date. `wrap-and-sort -sabt` needs running. autopkgtests are needed. debian/watch needs updating, memlockd 1.3 needs uploading upstream, the upstream website needs links converting to https. The upstream project should really get imported into git, from the Debian tarballs on snapshot.debian.org if there isn't anything better. -- bye, pabs https://wiki.debian.org/PaulWise diff -u memlockd-1.3/debian/changelog memlockd-1.3/debian/changelog --- memlockd-1.3/debian/changelog +++ memlockd-1.3/debian/changelog @@ -1,3 +1,10 @@ +memlockd (1.3-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix package when building only arch-any packages (Closes: #1000229) + + -- Paul Wise Sun, 06 Mar 2022 07:24:13 +0800 + memlockd (1.3-2) unstable; urgency=medium * Made it install correctly when systemctl isn't installed, closes: ##999587 only in patch2: unchanged: --- memlockd-1.3.orig/debian/memlockd.default +++ memlockd-1.3/debian/memlockd.default @@ -0,0 +1,10 @@ +# Defaults for memlockd initscript +# sourced by /etc/init.d/memlockd +# installed at /etc/default/memlockd + +# +# This is a POSIX shell fragment +# + +# Additional options that are passed to the Daemon. +DAEMON_OPTS="-u memlockd" only in patch2: unchanged: --- memlockd-1.3.orig/debian/memlockd.install +++ memlockd-1.3/debian/memlockd.install @@ -0,0 +1,2 @@ +memlockd usr/sbin +memlockd.cfg etc only in patch2: unchanged: --- memlockd-1.3.orig/debian/memlockd.manpages +++ memlockd-1.3/debian/memlockd.manpages @@ -0,0 +1 @@ +memlockd.8 only in patch2: unchanged: --- memlockd-1.3.orig/debian/rules +++ memlockd-1.3/debian/rules @@ -17,19 +17,8 @@ %: dh $@ -install: build - dh_installdirs - cp memlockd debian/memlockd/usr/sbin - cp memlockd.cfg debian/memlockd/etc - cp debian/memlockd-default debian/memlockd/etc/default/memlockd - dh_installsystemd --restart-after-upgrade memlockd.service +override_dh_installchangelogs: dh_installchangelogs -X changes.txt - dh_installdocs - dh_installinit - dh_installman memlockd.8 - dh_installdeb - dh_strip - dh_compress # dh_make generated override targets # This is example for Cmake (See https://bugs.debian.org/641051 ) signature.asc Description: This is a digitally signed message part
Bug#1005527: python-wsproto: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
On Sun, 13 Feb 2022 08:45:58 +0100 Lucas Nussbaum wrote: > Source: python-wsproto ... > During a rebuild of all packages in sid, your package failed to build > on amd64. Upstream has fixed this in git, so I asked them to make a new release: https://github.com/python-hyper/wsproto/issues/171 https://github.com/python-hyper/wsproto/commit/76c130fe6309235bb40161ed0e9fc9721ec55ab1 https://github.com/python-hyper/wsproto/pull/170 https://github.com/python-hyper/wsproto/issues/169 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1005858: gh,gitsome: File conflict, both ship /usr/bin/gh
Control: forwarded -1 https://github.com/donnemartin/gitsome/issues/177 On Sat, 26 Feb 2022 23:43:14 +0800 SZ Lin (林上智) wrote: > The "gitsome" has used "gh" since 2017, and thus would you mind renaming > the "gh" in your package to avoid the conflict issue? Since gh is the official GitHub client, probably it should retain "gh" and gitsome should move to "git some" or similar, as I have suggested in the above upstream issue. The only commentor there agreed with me. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1006408: reportbug: regression: broken lookup of bugs after filtering for "listbug" but not "bug"
Package: reportbug Version: 11.4.0 Severity: serious If I `reportbug reportbug` then filter by "listbug" then select item 1, reportbug looks up bug number #1, which it fails to find, instead of looking up the first bug, which is #786740, which it finds correctly. If I `reportbug reportbug` then filter by "bug" then select item 1, reportbug correctly looks up bug number #786740, which it finds fine. The issue also occurs when reporting against xserver-xorg-video-intel and filtering by "-l". I can't figure out the pattern of why some terms fail and others don't. I can reproduce this in a clean sid chroot, but not in a clean bullseye chroot, so I think this is a regression since 7.10.3. I don't think we should ship reportbug in this state for Debian bookworm, not being able to lookup bugs when filtering for some terms but not others is very annoying. It also is likely to result in duplicate bug reports if people don't notice the lookup failure. If you disagree with this assessment please downgrade the bug to important. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages reportbug depends on: ii apt 2.3.15 ii python3 3.9.8-1 ii python3-reportbug 11.4.0 ii sensible-utils 0.0.17 reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail ii debconf 1.5.79 ii debsums 3.0.2 pn dlocate pn emacs-bin-common ii exim4 4.95-3 ii exim4-daemon-light [mail-transport-agent] 4.95-3+b1 ii file 1:5.41-2 ii gnupg 2.2.27-3 ii python3-urwid 2.1.2-2+b1 ii reportbug-gtk 11.4.0 ii xdg-utils 1.1.3-4.1 Versions of packages python3-reportbug depends on: ii apt 2.3.15 ii file 1:5.41-2 ii python3 3.9.8-1 ii python3-apt 2.3.0+b1 ii python3-debian 0.1.43 ii python3-debianbts 3.2.0 ii python3-requests 2.25.1+dfsg-2 ii sensible-utils 0.0.17 python3-reportbug suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1005820: fwupd : segfault of service
Control: reassign 1005820 libgusb2 Control: forcemerge 1005416 1005820 On Fri, 18 Feb 2022 20:14:16 + Mario Limonciello wrote: > It was fixed by an upgrade to libgusb. This can be closed. Doing that in this message I think. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1006038: git-remote-hg: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2
Control: forwarded -1 https://github.com/mnauw/git-remote-hg/issues/48 On Sat, 2022-02-19 at 07:31 +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. This appears to be caused by git 1:2.35.1-1 in unstable, the autopkgtests regressed too with the new git version. https://tracker.debian.org/pkg/git I've forwarded this issue upstream for debugging/fixing. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1005953: needrestart: user session restart needing detection broken probably by cgroupv2 from systemd 247.2-4
Package: needrestart Version: 3.5-5 Severity: serious X-Debbugs-CC: syst...@packages.debian.org User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: cgroupv2 needrestart detects that user@1000.service needs to be restarted, instead of that the pabs user sessions have outdated binaries. The session detection definitely used to work at one point though. I've filed this at severity serious because it means that the user notification scripts in the needrestart package don't work, which means the needrestar-session package is not very useful any more. Looking at my mail archives, that started 2021-01-07 12:27 and in the upgrade before that systemd was upgraded from 247.1-3+deb11u1 to systemd 247.2-4, so that was probably the cause. Aside from the minor new upstream version, systemd 247.2-4 moved some libraries from /lib to /usr/lib. systemd upstream seems to have deleted their 247.2 git tag and there is no reference to it in their NEWS files. Looking at the Debian NEWS file, systemd 247.2-2 switched to cgroupv2, so I think that is probably the cause of this bug. I will test this theory next time I reboot. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-3-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages needrestart depends on: ii binutils 2.38-1 ii dpkg 1.21.1 ii gettext-base 0.21-4 ii libintl-perl 1.26-3 ii libmodule-find-perl0.15-1 ii libmodule-scandeps-perl1.31-1 ii libproc-processtable-perl 0.634-1+b1 ii libsort-naturally-perl 1.03-2 ii libterm-readkey-perl 2.38-1+b3 ii perl 5.34.0-3 ii xz-utils 5.2.5-2 Versions of packages needrestart recommends: ii libpam-systemd 250.3-2 Versions of packages needrestart suggests: ii iucode-tool 2.3.1-1 ii libnotify-bin0.7.9-3 ii needrestart-session 0.3-9 -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#992575: Bugs closed in libtorrent-rasterbar 2.0.5
Control: fixed -1 libtorrent-rasterbar/2.0.5-1 On Wed, 2022-02-02 at 15:50 +0100, Christian Marillat wrote: > Subject: Bugs closed in libtorrent-rasterbar 2.0.5 > Cc: 969780-cl...@bugs.debian.org, 992575-cl...@bugs.debian.org, > 856600-cl...@bugs.debian.org, 987120-cl...@bugs.debian.org, > 916399-cl...@bugs.debian.org, 999422-cl...@bugs.debian.org > > #969780 > #992575 > #856600 > #987120 > #916399 > #999422 Please use a versioned -done message next time: https://www.debian.org/Bugs/Developer#closing -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1004111: unattended-upgrades: regression: packages with conffile prompts are no longer skipped, leading to upgrade failures
Control: severity -1 normal Control: tags -1 + moreinfo Control: retitle -1 unattended-upgrades: upgrade of chromium-browser and others skipped on Raspberry Pi OS On Thu, 20 Jan 2022 16:42:21 -0600 Judah Richardson wrote: > This bug has showing up on this end in unattended-upgrades 2.8 on my > Raspberry Pi Model 3B+ running Raspberry Pi OS 11.2 since January 6, 2022. Since Raspberry Pi OS is a derivative of Debian, not Debian itself, bugs in Raspberry Pi OS should only be filed in the Debian bug tracker when they can be reproduced in Debian itself too. > unattended-upgrades: regression: packages with conffile prompts are no longer > skipped, leading to upgrade failures ... > Here's the error email I received from root on January 6, 2022: The subject of the bug report was about packages with conffile prompts attempting to be upgraded instead of skipped, but the filed bug report showed no failed upgrades, just skipped upgrades, so I retitled it. The information included in the bug report also isn't enough to determine why there are packages on the system that have been skipped when upgrading. Please supply the output of the following commands: apt policy apt policy chromium-browser chromium-browser-l10n chromium-codecs-ffmpeg-extra libraspberrypi0 libraspberrypi-bin libraspberrypi-dev libraspberrypi-doc lxplug-updater lynis raspberrypi-bootloader raspberrypi-kernel vcdbg apt upgrade --simulate apt full-upgrade --simulate aptitude upgrade --simulate aptitude dist-upgrade --simulate apt upgrade apt full-upgrade -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#931519: 931519 resolved
Control: fixed -1 4.0.3 On Fri, 2022-01-28 at 20:07 -0600, Dirk Eddelbuettel wrote: > Per email by Graham from 14 Nov 2020 this has been resolved. Resolved upstream in 2020 but not in Debian until 2021. > By now we have an even newer version 4.0.3. Please use a versioned -done message next time: https://www.debian.org/Bugs/Developer#closing -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#997194: mtr: FTBFS: ../ui/curses.c:435:17: error: format not a string literal and no format arguments [-Werror=format-security]
Control: forwarded -1 https://github.com/traviscross/mtr/pull/411 https://github.com/traviscross/mtr/commit/aeb493e08eabcb4e6178bda0bb84e9cd01c9f213 Control: tags -1 + upstream patch On Sun, 28 Nov 2021 16:51:05 +0100 Sven Joachim wrote: > In the meantime upstream has accepted a pull request (not tested by me) Unfortunately there has not yet been an upstream release containing a fix for this issue and mtr will soon be removed from Debian testing because the bug is unfixed. Could the patch be backported? -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#997601: fail2ban: FTBFS: error in fail2ban setup command: use_2to3 is invalid.
Control: forwarded -1 https://github.com/fail2ban/fail2ban/issues/3098 https://github.com/fail2ban/fail2ban/commit/5ac303df8a171f748330d4c645ccbf1c2c7f3497 Control: tags -1 + upstream fixed-upstream On Sat, 23 Oct 2021 23:15:13 +0200 Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. ... > > error in fail2ban setup command: use_2to3 is invalid. This has been fixed upstream but there has been no release yet. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#991449: fix for CVE-2021-32749 breaks systems with mail from bsd-mailx
Control: forwarded -1 https://github.com/fail2ban/fail2ban/issues/3059 https://savannah.gnu.org/bugs/?60937 https://git.savannah.gnu.org/cgit/mailutils.git/commit/?id=4befcfd015256c568121653038accbd84820198f On Fri, 23 Jul 2021 19:44:08 + (UTC) Thorsten Alteholz wrote: > According to upstreams security advisory [1] CVE-2021-32749 only affects > systems where the mail utility from the mailutils package is installed. > The recommended fix [2] is to add a new parameter "-E" to the invocation > of mail. Unfortunately this fix breaks other implementations of mail, > especially the version from package bsd-mailx. Thus upstream recommends in > the Workaround section of the advisory to only manually patch the > systems where the mailutils-mail is used. > > According to popcon the numbers of systems where mailutils-mail and > bsd-mailx-mail are used is about even. So applying upstreams fix now > breaks about half of the systems using fail2ban. > > The corresponding upstream bug #3069 [3] did not get any attention yet. The bug got forwarded to mailutils upstream and fixed there by disabling the escape sequence in non-interactive situations. The next step is for fail2ban to revert the workaround for the appropriate versions of mail, I've suggested how that they should do that on the upstream bug #3059. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#943306: rust-cargo-lichking: build-dependency not satisfiable
Control: tags -1 fixed-upstream Control: forwarded -1 https://github.com/Nemo157/cargo-lichking/commit/fb3dce3cd01aec138bc3a485ea7aaf829eca53ae On Wed, 2019-10-23 at 08:10 +0200, Ralf Treinen wrote: > rust-cargo-lichking build-depends on librust-cargo-0.32+default-dev, > which doesn't exist in the archive. This has been fixed upstream in version 0.9.0. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1001395: python-boto: (autopkgtest) needs update for python3.10: 'Mapping' from 'collections' removed
On Sun, 19 Dec 2021 13:03:38 +0800 Paul Wise wrote: > On Sat, 11 Dec 2021 10:15:42 -0800 Noah Meyerhans wrote: > > > On sid we currently see the follow rdeps: > > There are a few more in Build-Depends Also there are a few Recommends and Suggests: $ reverse-depends -s python3-boto Reverse-Recommends * python3-datalad * toil Reverse-Suggests * duplicity [amd64 arm64 armel armhf i386 mips64el mipsel ppc64el s390x] * monitoring-plugins-contrib [amd64 arm64 armel armhf i386 mips64el mipsel ppc64el s390x] * python3-dask * python3-django-extensions * python3-kombu Reverse-Depends * augur * debian-cloud-images-packages [amd64 arm64 ppc64el] * heat-cfntools * python3-bioblend Packages without architectures listed are reverse-dependencies in: all, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1001395: python-boto: (autopkgtest) needs update for python3.10: 'Mapping' from 'collections' removed
On Sun, 19 Dec 2021 13:03:38 +0800 Paul Wise wrote: > smart-open: python3-boto This one build-deps on both python3-boto and python3-boto3. It also has an unrelated failure to build as the test suite cannot import the google.cloud Python module. Filed as #1001932. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1001932: smart-open: FTBFS: ERROR smart_open/tests/test_gcs.py: ModuleNotFoundError: No module named 'google'
Source: smart-open
Version: 5.2.1-1
Severity: serious
Tags: ftbfs
When trying to rebuild smart-open in pbuilder, I get a test failure:
$ pdebuild
...
= test session starts
==
platform linux -- Python 3.9.9, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
rootdir: /build/smart-open-5.2.1, configfile: tox.ini
collected 306 items / 1 error / 305 selected
ERRORS
_ ERROR collecting
.pybuild/cpython3_3.9_smart-open/build/smart_open/tests/test_gcs.py _
ImportError while importing test module
'/build/smart-open-5.2.1/.pybuild/cpython3_3.9_smart-open/build/smart_open/tests/test_gcs.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.9/importlib/__init__.py:127: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
smart_open/tests/test_gcs.py:20: in
import google.cloud
E ModuleNotFoundError: No module named 'google'
=== short test summary info
ERROR smart_open/tests/test_gcs.py
Interrupted: 1 error during collection
=== 1 error in 2.32s
===
E: pybuild pybuild:355: test: plugin distutils failed with: exit code=2: cd
/build/smart-open-5.2.1/.pybuild/cpython3_3.9_smart-open/build; python3.9 -m
pytest smart_open/tests
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p
"3.10 3.9" returned exit code 13
make: *** [debian/rules:13: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit
status 2
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Bug#1001395: python-boto: (autopkgtest) needs update for python3.10: 'Mapping' from 'collections' removed
On Sat, 11 Dec 2021 10:15:42 -0800 Noah Meyerhans wrote: > On sid we currently see the follow rdeps: There are a few more in Build-Depends, the totality of them are spread across several different teams and individuals. I would suggest an MBF (mini bug filing) if python-boto is going to be removed from Debian. $ ssh mirror.ftp-master.debian.org dak rm -s unstable -Rn python-boto ... # Broken Depends: augur: augur debian-cloud-images: debian-cloud-images-packages [amd64 arm64 ppc64el] heat-cfntools: heat-cfntools python-bioblend: python3-bioblend # Broken Build-Depends: google-compute-image-packages: python3-boto heat-cfntools: python3-boto (>= 2.12.0) patroni: python3-boto python-bioblend: python3-boto python-glance-store: python3-boto salt: python3-boto smart-open: python3-boto swift: python3-boto toil: python3-boto $ dd-list augur debian-cloud-images heat-cfntools python-bioblend google-compute-image-packages heat-cfntools patroni python-glance-store salt smart-open swift toil Adrian Vondendriesch patroni (U) Andreas Tille augur (U) Andriy Senkovych salt (U) Benjamin Drung salt (U) Corey Bryant python-glance-store (U) Debian Cloud Team google-compute-image-packages Debian Cloud Team debian-cloud-images Debian Med Packaging Team augur smart-open toil Debian OpenStack heat-cfntools python-glance-store swift Debian PostgreSQL Maintainers patroni Debian Python Modules Team python-bioblend Debian Salt Team salt Franklin G Mendoza salt (U) Helen Koike google-compute-image-packages (U) Joe Healy salt (U) Lucas Kanashiro google-compute-image-packages (U) Michael Banck patroni (U) Michael R. Crusoe toil (U) Michal Arbet python-glance-store (U) swift (U) Mickael Asseline python-glance-store (U) Nilesh Patra augur (U) Noah Meyerhans debian-cloud-images (U) Ondřej Nový salt (U) swift (U) Sao I Kuan smart-open (U) Steffen Moeller python-bioblend (U) toil (U) Thomas Goirand debian-cloud-images (U) heat-cfntools (U) python-glance-store (U) swift (U) -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1001307: ceres-solver: invalid Uploaders field: missing comma between Anton Gladky and Francois Mazen
Source: ceres-solver Version: 2.0.0+dfsg1-1~exp1 Severity: serious ceres-solver 2.0.0+dfsg1-1~exp1 introduced an invalid Uploaders field, that is missing a comma between Anton Gladky and Francois Mazen. $ apt-cache showsrc ceres-solver | grep -E '^$|^Version|^Uploaders' Version: 1.14.0-14 Uploaders: Philipp Huebner , Anton Gladky Version: 2.0.0+dfsg1-1~exp1 Uploaders: Anton Gladky Francois Mazen According to Debian policy 5.6.3 the Uploaders field must separate individual uploaders using commas: List of the names and email addresses of co-maintainers of the package, if any. ... The format of each entry is the same as that of the Maintainer field, and multiple entries must be comma separated. https://www.debian.org/doc/debian-policy/ch-controlfields.html#uploaders This is causing the DDPO and BLS cron jobs to send error mails, please fix it as soon as possible. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1000872: [Parl-devel] Bug#1000872: parl-desktop-world depends on removed package.
On Tue, 2021-11-30 at 14:44 +, peter green wrote: > parl-desktop-world depends on thunderbird-l10n-si which is no longer > built from the thunderbird source package, it is still present in > unstable as a cruft package but is completely gone from testing. I suggest to depend on thunderbird-l10n-all, firefox-esr-l10n-all, instead of depending on the individual *-l10n-* packages. You might also want to request -all metapackages for libreoffice/hunspell/etc. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#994385: marked as pending in uvloop
Control: tag -1 pending Hello, Bug #994385 in uvloop 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/uvloop/-/commit/dc15694f79c67f0d91cd2737d8dc28b143b94dea Drop the package built for the Python debug interpreter (Closes: #994385) (this message was generated automatically) -- Greetings https://bugs.debian.org/994385
Bug#1000357: ddcci-dkms: install and module build failure with Linux 5.15: error: initialization of 'void (*)(struct device *)' from incompatible pointer type 'int (*)(struct device *)' [-Werror=incom
Package: ddcci-dkms Version: 0.4.1-1 Severity: serious When I try to install ddcci-dkms with linux-headers-amd64 5.15.3-1 installed, the installation fails because the build of the ddcci module fails because of an incompatible pointer type in the source code: $ sudo apt install linux-headers-amd64 ... $ sudo apt install ddcci-dkms ... Setting up ddcci-dkms (0.4.1-1) ... Loading new ddcci-0.4.1 DKMS files... Building for 5.15.0-1-amd64 Building initial module for 5.15.0-1-amd64 Error! Bad return status for module build on kernel: 5.15.0-1-amd64 (x86_64) Consult /var/lib/dkms/ddcci/0.4.1/build/make.log for more information. dpkg: error processing package ddcci-dkms (--configure): installed ddcci-dkms package post-installation script subprocess returned error exit status 10 Processing triggers for libc-bin (2.32-4) ... Errors were encountered while processing: ddcci-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) $ cat /var/lib/dkms/ddcci/0.4.1/build/make.log DKMS make.log for ddcci-0.4.1 for kernel 5.15.0-1-amd64 (x86_64) Mon Nov 22 01:53:32 UTC 2021 make: Entering directory '/var/lib/dkms/ddcci/0.4.1/build' make -C "ddcci" make[1]: Entering directory '/var/lib/dkms/ddcci/0.4.1/build/ddcci' make -C "/lib/modules/5.15.0-1-amd64/build" M="/var/lib/dkms/ddcci/0.4.1/build/ddcci" modules make[2]: Entering directory '/usr/src/linux-headers-5.15.0-1-amd64' CC [M] /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.o /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.c:1295:27: error: initialization of 'void (*)(struct device *)' from incompatible pointer type 'int (*)(struct device *)' [-Werror=incompatible-pointer-types] 1295 | .remove = ddcci_device_remove | ^~~ /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.c:1295:27: note: (near initialization for 'ddcci_bus_type.remove') cc1: some warnings being treated as errors make[3]: *** [/usr/src/linux-headers-5.15.0-1-common/scripts/Makefile.build:282: /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.o] Error 1 make[2]: *** [/usr/src/linux-headers-5.15.0-1-common/Makefile:1892: /var/lib/dkms/ddcci/0.4.1/build/ddcci] Error 2 make[2]: Leaving directory '/usr/src/linux-headers-5.15.0-1-amd64' make[1]: *** [Makefile:38: ddcci.ko] Error 2 make[1]: Leaving directory '/var/lib/dkms/ddcci/0.4.1/build/ddcci' make: *** [Makefile:28: ddcci] Error 2 make: Leaving directory '/var/lib/dkms/ddcci/0.4.1/build' -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (860, 'testing-proposed-updates-debug'), (860, 'testing-proposed-updates'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ddcci-dkms depends on: ii dkms 2.8.7-2 ddcci-dkms recommends no packages. ddcci-dkms suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#999862: sso.debian.org: SSO no longer seems to work
On Wed, 2021-11-17 at 20:55 +, Julian Gilbey wrote: > So it would seem that sso.debian.org may no longer be functional, > which prevents me from logging into tracker.debian.org. My current certificate still works on tracker.d.o and the sso test URL. I created a new cert and imported it into my browser (Firefox ESR 91) and it worked for the sso.d.o test site and for tracker.d.o. I wasn't able to get curl working with either the old or new certs. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#995781: [Debian-med-packaging] Bug#995781: python-sqlsoup autopkgtest fails with SQLAlchemy 1.4.23+ds1-2
On Tue, 2021-11-16 at 10:41 -0500, Mike Bayer wrote: > I've done both as well as taken down the readthedocs page. Looks good, thanks for that. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#995781: [Debian-med-packaging] Bug#995781: python-sqlsoup autopkgtest fails with SQLAlchemy 1.4.23+ds1-2
On Fri, 08 Oct 2021 16:51:06 -0400 Mike Bayer wrote: > SQLSoup's repository is currently at > https://github.com/zzzeek/sqlsoup > > However it has not been maintained for many years and would not be > expected to work with modern versions of SQLAlchemy. I suggest that you make this official by either mentioning that SQLSoup is no longer maintained in the README.md, or using the "archived" feature on GitHub, which marks the repository as read-only and adds a banner about the repository no longer being maintained. https://docs.github.com/en/repositories/archiving-a-github-repository/archiving-repositories FTR, I've filed a bug upstream against Python plac, which is the only other thing in Debian that uses SQLSoup (for its build-time tests). https://github.com/ialbert/plac/issues/62 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#998712: irrlicht: invalid Uploaders field: missing comma between Vincent Cheng and Julien Puydt
Source: irrlicht Version: 1.8.4+dfsg1-2 Severity: serious Justification: Policy 5.6.3 irrlicht 1.8.4+dfsg1-2 introduced an invalid uploaders field, that is missing a comma between Vincent Cheng and Julien Puydt. $ apt-cache showsrc irrlicht | grep -E '^$|^Version|^Uploaders' Version: 1.8.4+dfsg1-1.1 Uploaders: Christoph Egger , Vincent Cheng Version: 1.8.4+dfsg1-2 Uploaders: Vincent Cheng Julien Puydt According to Debian policy 5.6.3 the Uploaders field must separate individual uploaders using commas: List of the names and email addresses of co-maintainers of the package, if any. ... The format of each entry is the same as that of the Maintainer field, and multiple entries must be comma separated. This is causing the DDPO and BLS cron jobs to send error mails. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#998581: git-imerge: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13
On Thu, 2021-11-04 at 20:45 +0100, Lucas Nussbaum wrote: > Source: git-imerge ... > > ERROR: Could not install packages due to an EnvironmentError: > > [Errno 13] Permission denied: '/usr/lib/python3.9/dist-packages' This is apparently caused by a change in dh-python that will be reverted. For now please don't file any more bugs about this. https://salsa.debian.org/python-team/tools/dh-python/-/commit/169bc6ba400d27cfc143dc7f9f6f4b5db471def1 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#617856: New version of apt-show-versions fixes 617856
On Mon, 2021-10-25 at 13:00 +0200, Christoph Martin wrote: > I will try to upload a new release. I could not do so in the last > weeks, because my signature-key had expired and the new one did not yet > make it into the keyring. You could upload to mentors.debian.net and file an RFS request: https://mentors.debian.net/sponsors/rfs-howto/ -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#617856: New version of apt-show-versions fixes 617856
On Fri, 8 Oct 2021 11:31:39 +0200 Christoph Martin wrote: > tags 617856 + pending > thanks > > Upload of new version is pending. Could you upload the package? -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#995933: smart-notifier: crashes: AttributeError: 'gi.repository.Gtk' object has no attribute 'main'
Package: smart-notifier
Version: 0.28-7
Severity: serious
Usertags: crash
When smart-notifier starts, it crashes when starting the GUI service.
I assume that this means it will not notify about SMART errors,
please downgrade this bug if that isn't the case.
$ smart-notifier
...
Traceback (most recent call last):
File "/usr/bin/smart-notifier", line 14, in
smart_notifier.gui.service()
File "/usr/share/smart-notifier/smart_notifier/gui.py", line 52, in service
Gtk.main()
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 32,
in __getattr__
return getattr(self._introspection_module, name)
File "/usr/lib/python3/dist-packages/gi/module.py", line 123, in
__getattr__
raise AttributeError("%r object has no attribute %r" % (
AttributeError: 'gi.repository.Gtk' object has no attribute 'main'
-- System Information:
Debian Release: bookworm/sid
APT prefers testing-debug
APT policy: (900, 'testing-debug'), (900, 'testing'), (800,
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700,
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages smart-notifier depends on:
ii dbus1.12.20-2
ii gir1.2-gtk-3.0 3.24.30-3
ii python3 3.9.2-3
ii python3-dbus1.2.18-2
ii python3-gi 3.42.0-1+b1
ii smartmontools 7.2-1
smart-notifier recommends no packages.
smart-notifier suggests no packages.
-- no debconf information
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Bug#992668: ricochet-im: does not start
Control: fixed -1 + 1.1.4-3+b5 On Sat, 18 Sep 2021 13:06:25 +0800 Paul Wise wrote: > I'll request the release team to rebuild it in bullseye/bookworm. The rebuild has now happened for unstable/testing. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#992668: ricochet-im: does not start
On Sun, 2021-09-19 at 00:20 -0400, The Hermit wrote: > Failed at: > root@nevermore:/usr/src# sudo debi --upgrade > debi: cannot find readable debian/changelog anywhere! > Are you in the source code tree? Woops, debi needs to be run from the unpacked source package. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#992668: ricochet-im: does not start
Control: usertatgs -1 + confirmed On Sat, 21 Aug 2021 23:57:06 -0400 The Hermit wrote: > hermit@~:ricochet > /usr/include/c++/9/bits/move.h:194:7: runtime error: load of value 279, which > is not a valid value for type 'Type' I get this too and I noticed that rebuilding ricochet fixes it. I'll request the release team to rebuild it in bullseye/bookworm. Until that happens, you can rebuild it using these commands: sudo apt install devscripts sudo apt build-dep ricochet-im apt source --build ricochet-im sudo debi --upgrade -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#993870: marked as pending in quesoglc
Control: tag -1 pending Hello, Bug #993870 in quesoglc 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/games-team/quesoglc/-/commit/08d8aa2c374debae4306eea2921b4978568a9bf8 Work around breakage after autoconf upgrade (Closes: #993870) (this message was generated automatically) -- Greetings https://bugs.debian.org/993870
Bug#993870: guesoglc FTBFS: make[2]: *** No rule to make target '../src/glew.c', needed by 'libGLC_la-glew.lo'. Stop.
Control: tags -1 + sid On Tue, 7 Sep 2021 12:14:21 +0200 Helmut Grohne wrote: > quesoglc fails to build from source in unstable. This seems to have been caused by the update to autoconf, it does not occur with bookworm and upgrading autoconf to sid causes the issue. Looking at the config.log, the old autoconf seems to do the check twice, which works the first time but fails the second time. The g++ command-line is identical for all three of the checks. The new autoconf seems to only do the check once, which then fails. The failure with the old autoconf is due to missing -DGLEW_MX=1, which is a bug in the patch adding GLEW mx support. The failure with the new autoconf seems to be C++ related, the same test file links successfully when named .c and built with gcc. The difference is that autoconf 2.71 removed this from conftest.cpp: #ifdef __cplusplus extern "C" #endif OTOH the library is entirely C not C++ so it should use conftest.c instead of conftest.cpp for detecting the tests. It looks like AX_CHECK_GLU pulls in C++ support, but as far as I can tell it restores the language correctly after modifying it. Moving the AX_CHECK_GLU check after the GLEW check fixes the build. When I delete build/m4/ax_check_glu.m4 and try to use the one from autoconf-archive, the build fails due to a circular dependency: configure.in:157: error: m4_require: circular dependency of AC_LANG_COMPILER(C++) When I then add AC_PROG_CXX before AX_CHECK_GLU then that failure doesn't happen and the build succeeds as conftest.c is used this time. Unfortunately that workaround does not work for the original copy of the AX_CHECK_GLU macro in the upstream tarball. Removing use of AC_PROG_CXX/AC_LANG_PUSH/POP from the original copy of the AX_CHECK_GLU macro in the upstream tarball works around the issue. I have zero idea where to go from here but I'm going to apply that workaround for now and the next upstream release will drop the embedded code and m4 copies so should not be affected by this bug either. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#976697: webext-umatrix: no longer developed upstream, remove or switch to LibreMatrix or?
On Sat, 2021-09-04 at 17:08 +0200, Axel Beckert wrote: > Also it is unclear to me why the source is the Mozilla XPI while the > package works with both and upstream offers different download files > for Firefox and for Chromium/Chrome. (Then again, I haven't worked on > browser extensions since Mozilla ditched XUL…) I tried updating webext-umatrix to the latest release and immediately encountered this issue too as the build fails with the upstream source instead of the upstream prebuilt XPI file. I think that using prebuilt XPI files when the upstream project has a git repository has a risk of DFSG item 2 violations. Debian using XPI files is one of the reasons I started this discussion about not using upstream packaging ecosystems: Debian choice of upstream tarballs for packaging https://lists.debian.org/msgid-search/937697e40caf519e18119635db07d7b74b37b980.ca...@debian.org That said, I expect building WebExtensions from source properly is going to be a large undertaking that will require lots of node-* packages and other dependencies to be added to Debian. So a reasonable way to start is probably to update to the latest XPI and then start working on the dependencies etc. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#991778: dlint: Dlint fails to find version number of dig
Control: severity -1 important Control: tags -1 + unreproducible On Sun, 01 Aug 2021 19:00:34 +0200 Patrik Schindler wrote: > On my Debian Buster system, dig fails to work with > > ;; This program requires DiG version 2.1 or newer, which I cannot find. I can't reproduce this in a Debian buster chroot. Could you investigate more closely why it fails on your system? > Checking on this, I saw that the "ver" call in line 109 doesn't output a > version number anymore. So I changed that to dig -v. The command there still works for me in buster: $ dig localhost any | grep DiG | head -1 | sed -e 's/.*DiG \([0-9.]*\).*/\1/' 9.11.5 > The following replacement for line 109 works for me. > > ver=`dig -v 2>&1 | grep DiG | head -1 | sed -e 's/^DiG \([0-9.]\+\).*$/\1/'` This seems like a much more correct way to check the version, so it should be used instead anyway. > Versions of packages dlint depends on: > ii dnsutils 1:9.11.5.P4+dfsg-5.1+deb10u5 I also have 1:9.11.5.P4+dfsg-5.1+deb10u5. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#992747: qgis-providers: upgrade to 3.16.10+dfsg-1: crssync created file in root dir: /.config/Unknown Organization/crssync.conf
On Mon, 2021-08-23 at 06:23 +0200, Sebastiaan Couwenberg wrote: > HOME=/root Do you have these files instead? /root/.config/*/crssync.conf -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#992747: qgis-providers: upgrade to 3.16.10+dfsg-1: crssync created file in root dir: /.config/Unknown Organization/crssync.conf
On Mon, 2021-08-23 at 05:46 +0200, Sebastiaan Couwenberg wrote: > Control: tags -1 unreproducible Hmm, perhaps it was caused by my use of unattended-upgrades, which might not set the HOME or XDG_* environment variables. > This may be a regression, something like this happened before (#948727). Seems that was probably caused by env vars being missing or /root too. > On my unstable system qgis has been upgraded to 3.16.10 too, but it > doesn't have this config: Are you doing upgrades manually as root or using sudo apt? Can you check what environment variables are set in apt? -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#992747: qgis-providers: upgrade to 3.16.10+dfsg-1: crssync created file in root dir: /.config/Unknown Organization/crssync.conf
Package: qgis-providers Version: 3.16.10+dfsg-1 Severity: serious Usertags: cruft The upgrade to 3.16.10+dfsg-1 runs crssync from a trigger. This appears to have created a file in the root directory / (not /root) but package maintscripts should not create files outside of the /etc /var FHS dirs. Probably the workaround to this is to create a temporary directory, run crssync from there and clean up the directory afterwards. $ find /.config/ /.config/ /.config/Unknown Organization /.config/Unknown Organization/crssync.conf $ find /.config/ -ls 786433 4 drwxr-xr-x 3 root root 4096 Aug 23 01:06 /.config/ 786434 4 drwxr-xr-x 2 root root 4096 Aug 23 01:06 /.config/Unknown\ Organization 786436 4 -rw-r--r-- 1 root root 39 Aug 23 01:06 /.config/Unknown\ Organization/crssync.conf $ head -vn-0 '/.config/Unknown Organization/crssync.conf' ==> /.config/Unknown Organization/crssync.conf <== [qgis] localized_data_paths=@Invalid() $ find /var/lib/dpkg/info/ -iname *qgis* -print0 | xargs -0 grep -C3 crssync /var/lib/dpkg/info/qgis-providers.md5sums:520dd53ec7c06525d237428b26a835bd usr/lib/qgis/crssync /var/lib/dpkg/info/qgis-providers.md5sums-1143645206cd6dc0a226a1e1948def6e usr/lib/qgis/plugins/libarcgisfeatureserverprovider.so /var/lib/dpkg/info/qgis-providers.md5sums-f3af7f7a302169ee3413d9dc5a7c8e88 usr/lib/qgis/plugins/libarcgismapserverprovider.so /var/lib/dpkg/info/qgis-providers.md5sums-76b5faa93481a2461de3cb6d50e1f515 usr/lib/qgis/plugins/libbasicauthmethod.so -- /var/lib/dpkg/info/qgis-providers.postinst-set -e /var/lib/dpkg/info/qgis-providers.postinst- /var/lib/dpkg/info/qgis-providers.postinst-if [ "$1" = "triggered" ] || [ "$1" = "configure" ]; then /var/lib/dpkg/info/qgis-providers.postinst: if [ -w /usr/share/qgis/resources/srs.db ] && [ -x /usr/lib/qgis/crssync ]; then /var/lib/dpkg/info/qgis-providers.postinst: /usr/lib/qgis/crssync /var/lib/dpkg/info/qgis-providers.postinst- fi /var/lib/dpkg/info/qgis-providers.postinst-fi /var/lib/dpkg/info/qgis-providers.postinst- -- /var/lib/dpkg/info/qgis-providers.triggers:interest-noawait qgis-crssync -- /var/lib/dpkg/info/qgis-providers.list-/usr /var/lib/dpkg/info/qgis-providers.list-/usr/lib /var/lib/dpkg/info/qgis-providers.list-/usr/lib/qgis /var/lib/dpkg/info/qgis-providers.list:/usr/lib/qgis/crssync /var/lib/dpkg/info/qgis-providers.list-/usr/lib/qgis/plugins /var/lib/dpkg/info/qgis-providers.list-/usr/lib/qgis/plugins/libarcgisfeatureserverprovider.so /var/lib/dpkg/info/qgis-providers.list-/usr/lib/qgis/plugins/libarcgismapserverprovider.so -- /var/lib/dpkg/info/qgis-providers-common.postinst-#!/bin/sh /var/lib/dpkg/info/qgis-providers-common.postinst-set -e /var/lib/dpkg/info/qgis-providers-common.postinst- /var/lib/dpkg/info/qgis-providers-common.postinst:if [ "$1" = "configure" ] && [ -x /usr/lib/qgis/crssync ]; then /var/lib/dpkg/info/qgis-providers-common.postinst- cp /usr/share/qgis/resources/srs-template.db /usr/share/qgis/resources/srs.db /var/lib/dpkg/info/qgis-providers-common.postinst: dpkg-trigger qgis-crssync /var/lib/dpkg/info/qgis-providers-common.postinst-fi /var/lib/dpkg/info/qgis-providers-common.postinst- /var/lib/dpkg/info/qgis-providers-common.postinst- $ grep -B3 -A1 qgis-providers /var/log/apt/history.log Start-Date: 2021-08-23 01:05:16 Commandline: /usr/bin/unattended-upgrade Install: libqgis-gui3.16.10:amd64 (3.16.10+dfsg-1, automatic), libqgis-app3.16.10:amd64 (3.16.10+dfsg-1, automatic), libqgispython3.16.10:amd64 (3.16.10+dfsg-1, automatic), libqgis-core3.16.10:amd64 (3.16.10+dfsg-1, automatic), libqgis-server3.16.10:amd64 (3.16.10+dfsg-1, automatic), libqgis-analysis3.16.10:amd64 (3.16.10+dfsg-1, automatic), libqgis-3d3.16.10:amd64 (3.16.10+dfsg-1, automatic), libqgis-native3.16.10:amd64 (3.16.10+dfsg-1, automatic) Upgrade: qgis-common:amd64 (3.10.14+dfsg-1, 3.16.10+dfsg-1), python3-qgis:amd64 (3.10.14+dfsg-1, 3.16.10+dfsg-1), python3-qgis-common:amd64 (3.10.14+dfsg-1, 3.16.10+dfsg-1), qgis:amd64 (3.10.14+dfsg-1, 3.16.10+dfsg-1), libqgis-customwidgets:amd64 (3.10.14+dfsg-1, 3.16.10+dfsg-1), qgis-providers-common:amd64 (3.10.14+dfsg-1, 3.16.10+dfsg-1), qgis-providers:amd64 (3.10.14+dfsg-1, 3.16.10+dfsg-1) End-Date: 2021-08-23 01:07:02 $ grep -C40 qgis-providers /var/log/apt/term.log ... Log started: 2021-08-23 01:05:16 (Reading database ... 582863 files and directories currently installed.) Preparing to unpack .../00-qgis-common_3.16.10+dfsg-1_all.deb ... Unpacking qgis-common (3.16.10+dfsg-1) over (3.10.14+dfsg-1) ... Preparing to unpack .../01-qgis_3.16.10+dfsg-1_amd64.deb ... Unpacking qgis (3.16.10+dfsg-1) over (3.10.14+dfsg-1) ... Preparing to unpack .../02-python3-qgis_3.16.10+dfsg-1_amd64.deb ... Unpacking python3-qgis (3.16.10+dfsg-1) over (3.10.14+dfsg-1) ... Preparing to unpack .../03-qgis-providers_3.16.10+dfsg-1_amd64.deb ... Unpacking qgis-providers (3.16.10+dfsg-1) over
Bug#992381: freefem++: missing comma in Uploaders field
Source: freefem++ Version: 4.9+dfsg1-1 Severity: serious Usertags: uploaders X-Debbugs-CC: Francois Mazen freefem++ 4.9+dfsg1-1 introduced an invalid uploaders field, that is missing a comma between Ricardo Mones & Joseph Nahmias. $ apt-cache showsrc freefem++ | grep -E '^$|^Version|^Uploaders' Version: 3.61.1+dfsg1-6 Uploaders: Christophe Trophime , Dimitrios Eftaxiopoulos Version: 4.9+dfsg1-1 Uploaders: Christophe Trophime , Dimitrios Eftaxiopoulos Francois Mazen According to Debian policy 5.6.3 the Uploaders field must separate individual uploaders using commas: List of the names and email addresses of co-maintainers of the package, if any. ... The format of each entry is the same as that of the Maintainer field, and multiple entries must be comma separated. https://www.debian.org/doc/debian-policy/ch-controlfields.html#uploaders -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#991505: bind: duplicate, old version of bind9 source package, remove from experimental?
Source: bind Severity: serious Version: 1:9.13.3-1 X-Debbugs-CC: Ondřej Surý , Bernhard Schmidt src:bind in Debian experimental seems to be an older version than src:bind9 but still the same software. I suggest that src:bind be removed from Debian experimental since it is a duplicate. https://sources.debian.org/src/bind/experimental/debian/watch https://sources.debian.org/src/bind9/unstable/debian/watch -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#991151: corekeeper: postrm: invoke-rc.d: initscript procps, action "reload" failed.
On Sun, 2021-07-18 at 04:31 -0700, Craig Small wrote: > Which makes zero sense for procps which has no daemon. The restart action also makes zero sense for things that have no daemon. In the procps case, the Linux kernel is the software that is being restarted/reloaded, so reload actually makes *more* sense than restart, since restarting Linux means reboot or kexec but the procps init script doesn't do either of those things. > Why would you change from restart to reload in this case? I didn't change anything, procps changed to drop the reload action. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#991151: corekeeper: postrm: invoke-rc.d: initscript procps, action "reload" failed.
On Fri, 2021-07-16 at 12:41 +1000, Craig Small wrote: > I can add an alias easily enough. Using reload is very wrong so > corekeeper do the right thing but it's a one line change for procps. Can you elaborate on what you mean by "Using reload is very wrong"? -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#991151: corekeeper: postrm: invoke-rc.d: initscript procps, action "reload" failed.
On Fri, 2021-07-16 at 02:25 +, Thorsten Glaser wrote: > … this isn’t right. This is an RC bug in corekeeper but nōn-RC > in procps because of Policy §9.3.2: I still think it is RC as it is a feature regression breaking install of reverse dependencies in supported configurations (sysvinit). > So I think it’d be better to clone the bugreport, asking procps nicely > to implement “reload” while fixing corekeeper for bullseye first. If the procps maintainer doesn't plan to fix this in bullseye and buster, then I guess I will have to workaround it in corekeeper. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#991151: corekeeper: postrm: invoke-rc.d: initscript procps, action "reload" failed.
Control: reassign -1 procps 3.3.15-2 Control: retitle -1 procps: dropped the reload option from the init script, breaking corekeeper Control: affects -1 corekeeper On Fri, 2021-07-16 at 01:15 +, Thorsten Glaser wrote: > Yes, the procps init script does not have the action reload. Looks like this is a regression in procps in buster and later. I've bounced the thread to the procps maintainer and reassigned. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#991151: corekeeper: postrm: invoke-rc.d: initscript procps, action "reload" failed.
On Thu, 2021-07-15 at 21:34 +0200, Thorsten Glaser wrote: > invoke-rc.d: initscript procps, action "reload" failed. I don't have this problem on amd64 with systemd, can you reproduce it on amd64 with sysvinit? I'm thinking of switching to systemd-coredump, are you interested in adopting corekeeper? -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#989193: fixed in apparmor-profiles-extra 1.34
On Wed, 09 Jun 2021 07:18:32 + intrigeri wrote: >* apt-cacher-ng: allow link operations on the contents of the cache > directory > (Closes: #989193). Thanks to Eduard Bloch for the patch. Here is a little bump to postpone the autoremoval so the fix gets into testing. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#964511: Tests are failing, need to depends on the svg loader
On Wed, 2021-06-09 at 11:00 +0200, Ondřej Tůma wrote: > Here is fixed package in mentors, i hope right fixed... > https://mentors.debian.net/package/formiko/ That looks good to me. > And here is unblock request > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989643 I see the release team approved it. I've uploaded and removed the moreinfo tag. > And sorry for my bad fixing procedure, I'm so inexperienced > maintainer. No problem, everyone starts at the beginning and gets more experienced. Thanks for maintaining formiko, I'm using it for editing my website. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#964511: Tests are failing, need to depends on the svg loader
On Tue, 2021-06-08 at 16:24 +0200, Ondřej Tůma wrote: > I'm waiting for Ondrej N. now. For future reference, if your usual sponsor doesn't have time, you can file a request for sponsoring, details are available here: https://mentors.debian.net/intro-maintainers > I was prepare new Debian 1.3.0.-2 version, which has backported all > improvements with Sebastien's changes too. When you do that, it is generally a good idea to notify the bug that the fixed version is available and just waiting a sponsor. For low severity bugs run tagpending from devscripts but for severity important or higher bugs mailing the bug with details & tag pending is needed. https://manpages.debian.org/tagpending https://www.debian.org/Bugs/Reporting#control https://www.debian.org/Bugs/server-control#tag https://www.debian.org/Bugs/Developer#tags These changes you have made need fixes: * the second test in debian/tests/control needs to be marked as a superficial test too according to #974458 * debian/changelog for superficial issue should (Closes: #974458) * debian/changelog for rsvg issue should (Closes: #964511) * the reason for the addition of python3-docutils to the build deps should be documented in debian/changelog * the reason for the update of the X-Python3-Version field should be documented in debian/changelog * there is a debian/changelog entry about upstream metadata but those changes don't seem to be in the package These changes made in 1.3.0-2 are not suitable under the freeze policy: https://release.debian.org/bullseye/freeze_policy.html * the release team usually reject debhelper compat bumps, unless you can prove that the change does not change the binary packages in a meaningful way. You can do that by building once with debhelper debian/compat 11 and once with debhelper-compat 12 and attach diffoscope output for the .changes files between the two builds. https://manpages.debian.org/diffoscope https://diffoscope.org/ > Here branch of debian's package git repository: > https://github.com/ondratu/formiko-debian/tree/1.3.0 Please make the changes I have listed above, file an unblock request (reportbug release.debian.org, select unblock), upload a source package to mentors and file an RFS, then I will upload the package to Debian, once the release team approve the changes. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#964511: Tests are failing, need to depends on the svg loader
On Wed, 8 Jul 2020 21:29:07 +0200 Ondřej Tůma wrote: > thank's for report. I'm working now on version 1.4.3, which is last > upstream stable version. So I apply patch to new version too. It is now too late to get 1.4.3 into bullseye and the bug is now going to cause formiko to be removed from bullseye unless it is fixed soon. https://tracker.debian.org/pkg/formiko Will you be able to fix this issue or should Sebastien upload his NMU? -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
