Bug#971754: ABI breakage from 1.4.1 to 1.4.2
Hi Paul, On Fri, 2021-01-15 at 22:37 +0100, Paul Gevers wrote: > > Can you do this please? srt is orphaned, your package depend on it, > could you please help us get us out of this situation? (if this > happens soon, we'll accept the transition to fix this). I've created a MR in salsa for this change: https://salsa.debian.org/debian/libsrt/-/merge_requests/2 If that looks acceptable and correct to you then I'll upload it. signature.asc Description: This is a digitally signed message part
Bug#979597: cairosvg: diff for NMU version 2.5.0-1.1
Control: tags 979597 + patch
Control: tags 979597 + pending
Dear maintainer,
I've prepared an NMU for cairosvg (versioned as 2.5.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards,
Salvatore
diff -Nru cairosvg-2.5.0/debian/changelog cairosvg-2.5.0/debian/changelog
--- cairosvg-2.5.0/debian/changelog 2020-11-30 17:51:18.0 +0100
+++ cairosvg-2.5.0/debian/changelog 2021-01-16 09:45:26.0 +0100
@@ -1,3 +1,11 @@
+cairosvg (2.5.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Don't use overlapping groups for regular expressions (CVE-2021-21236)
+(Closes: #979597)
+
+ -- Salvatore Bonaccorso Sat, 16 Jan 2021 09:45:26 +0100
+
cairosvg (2.5.0-1) unstable; urgency=low
[ Debian Janitor ]
diff -Nru cairosvg-2.5.0/debian/patches/0002-Don-t-use-overlapping-groups-for-regular-expressions.patch cairosvg-2.5.0/debian/patches/0002-Don-t-use-overlapping-groups-for-regular-expressions.patch
--- cairosvg-2.5.0/debian/patches/0002-Don-t-use-overlapping-groups-for-regular-expressions.patch 1970-01-01 01:00:00.0 +0100
+++ cairosvg-2.5.0/debian/patches/0002-Don-t-use-overlapping-groups-for-regular-expressions.patch 2021-01-16 09:43:01.0 +0100
@@ -0,0 +1,59 @@
+From: Guillaume Ayoub
+Date: Fri, 1 Jan 2021 00:05:55 +0100
+Subject: =?UTF-8?q?Don=E2=80=99t=20use=20overlapping=20groups=20for=20regu?=
+ =?UTF-8?q?lar=20expressions?=
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+Origin: https://github.com/Kozea/CairoSVG/commit/063185b60588a41d4df661ad70f9f7b699901abc
+Bug-Debian: https://bugs.debian.org/979597
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2021-21236
+
+The section between 'rgb(' and the final ')' contains multiple overlapping
+groups.
+
+Since all three infinitely repeating groups accept spaces, a long string of
+spaces causes catastrophic backtracking when it is not followed by a closing
+parenthesis.
+
+The complexity is cubic, so doubling the length of the malicious string of
+spaces makes processing take 8 times as long.
+---
+ cairosvg/colors.py | 8
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+diff --git a/cairosvg/colors.py b/cairosvg/colors.py
+index 96d94e1a3210..68eed88db2c7 100644
+--- a/cairosvg/colors.py
b/cairosvg/colors.py
+@@ -187,8 +187,8 @@ COLORS = {
+ 'transparent': (0, 0, 0, 0),
+ }
+
+-RGBA = re.compile(r'rgba\([ \n\r\t]*(.+?)[ \n\r\t]*\)')
+-RGB = re.compile(r'rgb\([ \n\r\t]*(.+?)[ \n\r\t]*\)')
++RGBA = re.compile(r'rgba\((.+?)\)')
++RGB = re.compile(r'rgb\((.+?)\)')
+ HEX_RRGGBB = re.compile('#[0-9a-f]{6}')
+ HEX_RGB = re.compile('#[0-9a-f]{3}')
+
+@@ -212,14 +212,14 @@ def color(string, opacity=1):
+ if match:
+ r, g, b, a = tuple(
+ float(i.strip(' %')) / 100 if '%' in i else float(i) / 255
+-for i in match.group(1).split(','))
++for i in match.group(1).strip().split(','))
+ return (r, g, b, a * 255 * opacity)
+
+ match = RGB.search(string)
+ if match:
+ r, g, b = tuple(
+ float(i.strip(' %')) / 100 if '%' in i else float(i) / 255
+-for i in match.group(1).split(','))
++for i in match.group(1).strip().split(','))
+ return (r, g, b, opacity)
+
+ match = HEX_RRGGBB.search(string)
+--
+2.30.0
+
diff -Nru cairosvg-2.5.0/debian/patches/series cairosvg-2.5.0/debian/patches/series
--- cairosvg-2.5.0/debian/patches/series 2020-11-30 17:51:18.0 +0100
+++ cairosvg-2.5.0/debian/patches/series 2021-01-16 09:43:43.0 +0100
@@ -1 +1,2 @@
0001-Remove-pytest-options-for-plugins-not-packaged-for-D.patch
+0002-Don-t-use-overlapping-groups-for-regular-expressions.patch
Processed: cairosvg: diff for NMU version 2.5.0-1.1
Processing control commands: > tags 979597 + patch Bug #979597 [src:cairosvg] cairosvg: CVE-2021-21236: Regular Expression Denial of Service (REDoS) Added tag(s) patch. > tags 979597 + pending Bug #979597 [src:cairosvg] cairosvg: CVE-2021-21236: Regular Expression Denial of Service (REDoS) Added tag(s) pending. -- 979597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963477: ruby-rack: CVE-2020-8184
Hi Salvatore, On Sun, Jan 3, 2021 at 1:34 AM Salvatore Bonaccorso wrote: > Not any right now. Well there is CVE-2020-26247 but that one might be > too risky at this stage (AFAIU it is a breaking change, and thus ws > moved to the 1.11.x version). Lucas uploaded a new version, thereby fixing this as well. So yay! \o/ - u
Bug#937831: python-imaplib2: Python2 removal in sid/bullseye
Hi Ilias, On Thu, Sep 19, 2019 at 06:49:36PM +0300, Ilias Tsitsimpis wrote: > Control: usertag -1 + py2keep > Control: forwarded -1 https://github.com/imaplib2/imaplib2/issues/7 > > This package is dead upstream, but is needed by OfflineIMAP, which has > been tagged as `py2keep`, so I am tagging this package as well. Upstream is moving to collective maintenance 'Jazzband'. The python3 port of offlineimap (offlineimap3) has landed in unstable and will not migrate to testing as 'python3-imaplib2' is not available. If we assume offlineimap will be removed from testing, can you please remove the binary package 'python-imaplib2' and only keep 'python3-imaplib2' while closing the bug.. -- Regards Sudip
Bug#937184: offlineimap: Python2 removal in sid/bullseye
Hi All, On Mon, Nov 09, 2020 at 08:14:38PM +0100, Moritz Mühlenhoff wrote: > On Sun, Aug 02, 2020 at 06:24:44PM +0300, Ilias Tsitsimpis wrote: > > Control: severity -1 serious > > > > On Sun, Jul 26, 2020 at 01:21PM, Moritz Mühlenhoff wrote: > > > Nine months later there's no progress, let's remove? > > > > Agreed. > > > > Raising the severity to serious to remove from testing, and then I will > > request for removal. > > Now that offlineimap3 is available in experimental, let's go ahead with > removal > of src:offlineimap? I have uploaded offlineimap3 to unstable but will not migrate untill we have 'python3-imaplib2' in testing, which is blocked by #937831, which is again blocked by this #937184. Can we go ahead with this removal please? I can then add a dummy transitional package so that users of offlineimap can upgrade to offlineimap3 with Bullseye. Since I have the ITA on offlineimap, do I file the RM bug or that needs to be done by Ilias ? -- Regards Sudip
Bug#950404: ndpi FTBFS
control: severity -1 important On Mon, 21 Dec 2020 12:09:44 + Nicholas Brown wrote: > Upstream issues that tracks the UT failures reported on i386 and s390x > https://github.com/ntop/nDPI/issues/1092 I asked to remove problematic architectures, so the severity can be set to important now Opened #980216 in ftp.debian.org by Gianfranco Costamagna (locutusofborg) «RM: ndpi [i386 ppc64el s390x] -- RoQA; FTBFS». https://bugs.debian.org/980216 G.
Processed: Re: ndpi FTBFS
Processing control commands: > severity -1 important Bug #950404 [src:ndpi] ndpi FTBFS on arm64, i386, ppc64el and s390x due to test failures Severity set to 'important' from 'serious' -- 950404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937184: offlineimap: Python2 removal in sid/bullseye
On Sat, Jan 16, 2021 at 11:12:21AM +, Sudip Mukherjee wrote: > Hi All, > > On Mon, Nov 09, 2020 at 08:14:38PM +0100, Moritz Mühlenhoff wrote: > > On Sun, Aug 02, 2020 at 06:24:44PM +0300, Ilias Tsitsimpis wrote: > > > Control: severity -1 serious > > > > > > On Sun, Jul 26, 2020 at 01:21PM, Moritz Mühlenhoff wrote: > > > > Nine months later there's no progress, let's remove? > > > > > > Agreed. > > > > > > Raising the severity to serious to remove from testing, and then I will > > > request for removal. > > > > Now that offlineimap3 is available in experimental, let's go ahead with > > removal > > of src:offlineimap? > > I have uploaded offlineimap3 to unstable but will not migrate untill we > have 'python3-imaplib2' in testing, which is blocked by #937831, which is > again blocked by this #937184. > > Can we go ahead with this removal please? I can then add a dummy > transitional package so that users of offlineimap can upgrade to > offlineimap3 with Bullseye. > > Since I have the ITA on offlineimap, do I file the RM bug or that needs > to be done by Ilias ? Or on second thought, will it be easier if I upload an offlineimap upload marking the binary package as dummy transitional package instead of going through RM and then NEW ? -- Regards Sudip
Bug#980211: libextractor: FTBFS against librpm9 (test failure)
this seems to be architecture specific. It only fails on arm64, armel (but succeeds on armhf) i386, mipsel, mips64el, hppa, sparc64, x32
Bug#919058: marked as done (its-tools: crashes when freeing xmlDocs)
Your message dated Sat, 16 Jan 2021 12:18:26 +
with message-id
and subject line Bug#919058: fixed in debmake-doc 1.16-1
has caused the Debian Bug report #919058,
regarding its-tools: crashes when freeing xmlDocs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
919058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mate-utils
Version: 1.20.2-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=mate-utils
...
Traceback (most recent call last):
File "/usr/bin/itstool", line 1611, in
doc.merge_translations(translations, opts.lang, strict=opts.strict)
File "/usr/bin/itstool", line 999, in merge_translations
lcnode.setProp(attr, origlang)
File "/usr/lib/python2.7/dist-packages/libxml2.py", line 3588, in setProp
if ret is None:raise treeError('xmlSetProp() failed')
libxml2.treeError: xmlSetProp() failed
Warning: Could not merge hu translation for msgid:
Permission is granted to copy, distribute and/or modify this document under the
terms of the GNU Free Documentation License (GFDL), Version 1.1 or any later
version published by the Free Software Foundation with no Invariant Sections,
no Front-Cover Texts, and no Back-Cover Texts. You can find a copy of the GFDL
at this <_:ulink-1/> or in the file COPYING-DOCS distributed with this manual.
make[4]: *** [Makefile:603: pt/pt.stamp] Error 1
If it cannot easily be fixed properly,
passing --no-parallel to dh would like work around it.
--- End Message ---
--- Begin Message ---
Source: debmake-doc
Source-Version: 1.16-1
Done: Osamu Aoki
We believe that the bug you reported is fixed in the latest version of
debmake-doc, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Osamu Aoki (supplier of updated debmake-doc package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 13 Jan 2021 14:22:36 +0900
Source: debmake-doc
Architecture: source
Version: 1.16-1
Distribution: unstable
Urgency: medium
Maintainer: Osamu Aoki
Changed-By: Osamu Aoki
Closes: 919058 923667 948781
Changes:
debmake-doc (1.16-1) unstable; urgency=medium
.
[ Holger Wansing ]
* Updated Debian Policy links.
.
[ Osamu Aoki ]
* Fix basedir.
* Major source restructuring to use po4a and change main commit branch to
master and avoid using itstools. Closes: #919058, #948781
* Make review of the build log easier by adjusting parallel build process.
* Fix zh-cn and zh-tw POs and made some recovery of old de translation.
(More restructuring and further recovery need to be done)
* Mention dgit-maint-merge(7). Closes: #923667
Checksums-Sha1:
2ec49aa8e1ed25aacde44409a28253128c9c2fd8 2248 debmake-doc_1.16-1.dsc
df6d5dd77aadd4b2268fe78ee9ff93c081865b38 553404 debmake-doc_1.16.orig.tar.xz
c116a74282479f2792425aea635eecb564b9a490 5092 debmake-doc_1.16-1.debian.tar.xz
6e43e830bc4acdab5a98394a88fcd2dadf5fa840 11771
debmake-doc_1.16-1_source.buildinfo
Checksums-Sha256:
8a73675f79b9ca872f5cc9020b409a36dd7dc13f7cd8411268e21c1f0068cb8c 2248
debmake-doc_1.16-1.dsc
64e924b63b12f1e893f8570c6a36fb49a2d959ec8b7c74bebe9fcbec04cf28bd 553404
debmake-doc_1.16.orig.tar.xz
ff9a02e11a78a94377b8c6b5518577a12d8129d7c32a16eb34691b63d503b4ab 5092
debmake-doc_1.16-1.debian.tar.xz
0004bde6c7a58c38524aa64953a49ea2f1f5a907d4b8bbb022b97cd6ab06c11b 11771
debmake-doc_1.16-1_source.buildinfo
Files:
af07250889f11f653491e8289ca6f34a 2248 doc optional debmake-doc_1.16-1.dsc
0ffe0797fa4a30aabd5b05fbba11c0e3 553404 doc optional
debmake-doc_1.16.orig.tar.xz
8b3878b02583e737b685495f931c8f01 5092 doc optional
debmake-doc_1.16-1.debian.tar.xz
bb35817755fa589980de08e3116ac00f 11771 doc optional
debmake-doc_1.16-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEMTNyTWIHiBV56V1iHhNWiB3Y15EFAmAC1lEACgkQHhNWiB3Y
15FvYg/+N416/roVEhIc1yiy3Eu7WWwbUI388a0wmLSVUqxUnt2PNhD2J4ZZO+iL
27MFzSp8xXa0tPAYZ3o96kpzsyJJ8hMzT6Osdqv6sUHJHf/y3uR9qOo0iE5KzHUn
l/vQsswbTSf4MBbuWh9c0zdMLXFfOtfCSYaVPHKjrsC3cmKzhipsmSqagGmGaxTu
NFi881
Bug#948781: marked as done (debmake-doc: FTBFS: Segmentation fault)
Your message dated Sat, 16 Jan 2021 12:18:26 + with message-id and subject line Bug#948781: fixed in debmake-doc 1.16-1 has caused the Debian Bug report #948781, regarding debmake-doc: FTBFS: Segmentation fault to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 948781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: debmake-doc Version: 1.14-1 Severity: serious Tags: ftbfs Dear maintainer, your package failed to rebuild in a standard sid chroot: itstool -i xslt/docbook.its -m po/ja.mo -o po/ja/ debmake-doc.en.x02 mkdir -p po/de/ itstool -i xslt/docbook.its -m po/de.mo -o po/de/ debmake-doc.en.x02 mkdir -p po/ msgfmt -D po zh-cn.po -o po/zh-cn.mo mkdir -p po/zh-cn/ itstool -i xslt/docbook.its -m po/zh-cn.mo -o po/zh-cn/ debmake-doc.en.x02 mkdir -p po/ msgfmt -D po ru.po -o po/ru.mo mkdir -p po/ru/ itstool -i xslt/docbook.its -m po/ru.mo -o po/ru/ debmake-doc.en.x02 make[2]: *** [Makefile.dbk:125: debmake-doc.zh-cn.x02] Segmentation fault make[2]: *** Waiting for unfinished jobs Traceback (most recent call last): File "/usr/bin/itstool", line 1614, in doc.merge_translations(translations, opts.lang, strict=opts.strict) File "/usr/bin/itstool", line 1000, in merge_translations lcpar = lcpar.parent File "/usr/lib/python3/dist-packages/libxml2.py", line 296, in get_parent return nodeWrap(ret) File "/usr/lib/python3/dist-packages/libxml2.py", line 580, in nodeWrap if name[0:8] == "document": TypeError: 'NoneType' object is not subscriptable make[2]: *** [Makefile.dbk:125: debmake-doc.de.x02] Error 1 cp po/ja/debmake-doc.en.x02 debmake-doc.ja.x02 rm po/ja/debmake-doc.en.x02 rmdir po/ja cp po/ru/debmake-doc.en.x02 debmake-doc.ru.x02 rm po/ru/debmake-doc.en.x02 rmdir po/ru make[2]: Leaving directory '/build/1st/debmake-doc-1.14' make[1]: *** [Makefile:31: build] Error 2 make[1]: Leaving directory '/build/1st/debmake-doc-1.14' dh_auto_build: make -j16 "INSTALL=install --strip-program=true" returned exit code 2 make: *** [debian/rules:20: build] Error 255 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: debmake-doc Source-Version: 1.16-1 Done: Osamu Aoki We believe that the bug you reported is fixed in the latest version of debmake-doc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 948...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Osamu Aoki (supplier of updated debmake-doc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 13 Jan 2021 14:22:36 +0900 Source: debmake-doc Architecture: source Version: 1.16-1 Distribution: unstable Urgency: medium Maintainer: Osamu Aoki Changed-By: Osamu Aoki Closes: 919058 923667 948781 Changes: debmake-doc (1.16-1) unstable; urgency=medium . [ Holger Wansing ] * Updated Debian Policy links. . [ Osamu Aoki ] * Fix basedir. * Major source restructuring to use po4a and change main commit branch to master and avoid using itstools. Closes: #919058, #948781 * Make review of the build log easier by adjusting parallel build process. * Fix zh-cn and zh-tw POs and made some recovery of old de translation. (More restructuring and further recovery need to be done) * Mention dgit-maint-merge(7). Closes: #923667 Checksums-Sha1: 2ec49aa8e1ed25aacde44409a28253128c9c2fd8 2248 debmake-doc_1.16-1.dsc df6d5dd77aadd4b2268fe78ee9ff93c081865b38 553404 debmake-doc_1.16.orig.tar.xz c116a74282479f2792425aea635eecb564b9a490 5092 debmake-doc_1.16-1.debian.tar.xz 6e43e830bc4acdab5a98394a88fcd2dadf5fa840 11771 debmake-doc_1.16-1_source.buildinfo Checksums-Sha256: 8a73675f79b9ca872f5cc9020b409a3
Bug#979555: marked as done (r-bioc-delayedarray: tests fail on Debian unstable & testing)
Your message dated Sat, 16 Jan 2021 12:20:16 + with message-id and subject line Bug#979555: fixed in r-bioc-delayedarray 0.16.0+dfsg-2 has caused the Debian Bug report #979555, regarding r-bioc-delayedarray: tests fail on Debian unstable & testing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: r-bioc-delayedarray Version: 0.16.0+dfsg-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 control: forwarded -1 https://github.com/Bioconductor/DelayedArray/issues/84 I noticed the tests are failing in unstable in testing, so I've reported this upstream. -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl/4HVYSHGNydXNvZUBk ZWJpYW4ub3JnAAoJEDwmdj9sZ+biaPAQAMow9LJ1t0YwheEbJr/H+tC9nQjfW8oo he+YJePEwgUWGdC7T6daqCgk83YJNJOXOtOUuz5XSf2WX8qG/VjuUtoRCLhIKGUW o8y7qXNTLZbyfp3cYBrylo/OnSiDVhaOFxtOkrL5c3uqqH5xBve+lZ5iSKh/qcAp TWsa0v3Pe5nMM8OWfIHoLO9agBXpW/CckwgJ18wbarbcCDKNthbClbp/THuPFYL8 SGOqAa2o1oYZxnpgZMB2EJhJ3KgUVZqTVxWc7DnXkXe3qh46HkoF/lH2TkHJ3t/2 ZjGZgh6YI4atVO2WNTJ0USh4znR1/hgMuUysIWmZF4UDHlUdUk0+BktsztX5LDRe 5WEZP9jM3z0ZO2B1kAX3OYjSg/By4aqBiZaXxoRTx5E4d/I3dU0PYdSUphQkMGDQ YDI+U3my0mAPeR0Rl4sdPMZBf5nuNP8ty9grjHsgHSmlLI2J2OQckJtLd0g48AH+ VOfPfMTOuxmG64mxh6aMK5WO3qubwwHf/VKvcTfcKYR/v/UpWmHV+wHFROZTDrmC FVvSIpBvEpoS0kyFJOexyAmjP23+zgD+qzT8M4tZt1wI3jnsoHUBPFYt79n6CRyU Q91IrhbIqMvd6JHDVJWZPUmhHrZ4RF2LOPsaWp4zYJ1SxjNJgVAhlOZ4UA8G5jjF oghKZu4M8l4f =LDKJ -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: r-bioc-delayedarray Source-Version: 0.16.0+dfsg-2 Done: Michael R. Crusoe We believe that the bug you reported is fixed in the latest version of r-bioc-delayedarray, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael R. Crusoe (supplier of updated r-bioc-delayedarray package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 16 Jan 2021 12:51:43 +0100 Source: r-bioc-delayedarray Architecture: source Version: 0.16.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Michael R. Crusoe Closes: 979555 Changes: r-bioc-delayedarray (0.16.0+dfsg-2) unstable; urgency=medium . * Team upload. * Run the tests via autopkgtest-pkg-r, not BiocGenerics:::testPackage. Same testsuite, but run in a manner that works. Closes: #979555 * Standards-Version: 4.5.1 (routine-update) * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. Checksums-Sha1: 88ce864af1a50b4443c67b51ec41ab2412a79cab 2280 r-bioc-delayedarray_0.16.0+dfsg-2.dsc 2866596cde0c48527476d3ed2eba214b9a609c39 4396 r-bioc-delayedarray_0.16.0+dfsg-2.debian.tar.xz 9108db7056fba1d7b21ec274c2fbe2414ce9bef6 10744 r-bioc-delayedarray_0.16.0+dfsg-2_source.buildinfo Checksums-Sha256: 86d6cb8ef5d32fa7d20e8a2c1766e6eb390a3e5e5a5e31cf414df007c292e753 2280 r-bioc-delayedarray_0.16.0+dfsg-2.dsc 55524d775d677f94fe4691cd968fe69b18ed3d413d9970ef5504de601ff79283 4396 r-bioc-delayedarray_0.16.0+dfsg-2.debian.tar.xz 480cc829de770a3b5004bdf25dc64132ee910e8ba1513214e29c3f7c3a1af9a5 10744 r-bioc-delayedarray_0.16.0+dfsg-2_source.buildinfo Files: 93415289be7169d4470a36dfacc9926c 2280 gnu-r optional r-bioc-delayedarray_0.16.0+dfsg-2.dsc 43ae755322564425967dd68b8d10aca4 4396 gnu-r optional r-bioc-delayedarray_0.16.0+dfsg-2.debian.tar.xz 9e69754d6df73961c1d83d1b5701cac2 10744 gnu-r optional r-bioc-delayedarray_0.16.0+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAmAC1lUACgkQPCZ2P2xn 5uKOCw/9Es/30112iHYjde3p192iqB6Yg1YByygrG7UdjZ1Ycbl1Lg52Op09w8Sh a08DlpvshErbDtoMAhO8Em1LWiNHK+EL+LE6r0ydWBDZ/W8M+L1GgS631NOcXYPw SbI6+KOSV8Wm6nN0qC8IWDouq80pbaYPnAYNUBBXNQXp3/qE/XoxJTx+92OgocWQ 6ouQhk46wRxLZkcu3A/R9PXfyv4ULXliVFHPaG49K5uCyIZCtv5IccK+kKQJamoM wt34BAlxAprA3J/tsGvY0W0btutbX99paK6xaQfVS+UgUhI819emQqwb1IhaZg9w J0i65KkpE/+qjTXsFB7bM+Tk+k0r+qR4RN9+qpxbWpPfs8KpH8TMeygQM/ZgjdFT T
Bug#948105: marked as pending in libgdata
Control: tag -1 pending Hello, Bug #948105 in libgdata 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/gnome-team/libgdata/-/commit/20fc00727a98286c30a885e74eeb865a891c8c18 debian/control.in: Rename libuhttpmock-dev to libuhttpmock-0.0-dev Closes: #948105 (this message was generated automatically) -- Greetings https://bugs.debian.org/948105
Processed: Bug#948105 marked as pending in libgdata
Processing control commands: > tag -1 pending Bug #948105 [src:libgdata] Remove build dep on libuhttpmock-dev Added tag(s) pending. -- 948105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971754: ABI breakage from 1.4.1 to 1.4.2
Hi Sebastian, On 16-01-2021 09:41, Sebastian Dröge wrote: > On Fri, 2021-01-15 at 22:37 +0100, Paul Gevers wrote: >> >> Can you do this please? srt is orphaned, your package depend on it, >> could you please help us get us out of this situation? (if this >> happens soon, we'll accept the transition to fix this). > > I've created a MR in salsa for this change: > https://salsa.debian.org/debian/libsrt/-/merge_requests/2 > > If that looks acceptable and correct to you then I'll upload it. I was expecting a new upstream release to be incorporated, but I understand upstream didn't release anything new yet. For whatever it's worth, your MR doesn't look too weird. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#949933: swiftsc: diff for NMU version 0.5-1.2
Control: tags 949933 + patch Control: tags 949933 + pending Control: tags 952353 + patch Control: tags 952353 + pending Dear maintainer, to fix the FTBFS problems for this package, I've prepared an NMU for swiftsc (versioned as 0.5-1.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. Christoph diff -Nru swiftsc-0.5/debian/changelog swiftsc-0.5/debian/changelog --- swiftsc-0.5/debian/changelog>---2019-10-29 14:31:56.0 +0100 +++ swiftsc-0.5/debian/changelog>---2021-01-16 14:04:59.0 +0100 @@ -1,3 +1,11 @@ +swiftsc (0.5-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Update build dependencies to make package buildable again. +Closes: #949933, #952353 + + -- Christoph Biedl Sat, 16 Jan 2021 14:04:59 +0100 + swiftsc (0.5-1.1) unstable; urgency=medium · * Non-maintainer upload. diff -Nru swiftsc-0.5/debian/control swiftsc-0.5/debian/control --- swiftsc-0.5/debian/control>-2019-10-29 14:31:26.0 +0100 +++ swiftsc-0.5/debian/control>-2021-01-16 14:02:03.0 +0100 @@ -2,7 +2,7 @@ Section: python Priority: optional Maintainer: Kouhei Maeda -Build-Depends: debhelper (>= 8.0.0), pep8, python3-all, python3-setuptools, python3-requests, python3-magic, python3-pytest, python3-mock +Build-Depends: debhelper (>= 8.0.0), dh-python, pycodestyle, python3-all, python3-setuptools, python3-requests, python3-magic, python3-pytest, python3-mock Standards-Version: 3.9.4 X-Python-Version: >= 2.6, >= 3.2 Homepage: https://github.com/mkouhei/swiftsc signature.asc Description: PGP signature
Processed: swiftsc: diff for NMU version 0.5-1.2
Processing control commands: > tags 949933 + patch Bug #949933 [src:swiftsc] swiftsc build depends on the removed pep8 transitional package Ignoring request to alter tags of bug #949933 to the same tags previously set > tags 949933 + pending Bug #949933 [src:swiftsc] swiftsc build depends on the removed pep8 transitional package Ignoring request to alter tags of bug #949933 to the same tags previously set > tags 952353 + patch Bug #952353 [src:swiftsc] swiftsc: FTBFS: dh: error: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 3) line 1. Ignoring request to alter tags of bug #952353 to the same tags previously set > tags 952353 + pending Bug #952353 [src:swiftsc] swiftsc: FTBFS: dh: error: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 3) line 1. Ignoring request to alter tags of bug #952353 to the same tags previously set -- 949933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949933 952353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: swiftsc: diff for NMU version 0.5-1.2
Processing control commands: > tags 949933 + patch Bug #949933 [src:swiftsc] swiftsc build depends on the removed pep8 transitional package Added tag(s) patch. > tags 949933 + pending Bug #949933 [src:swiftsc] swiftsc build depends on the removed pep8 transitional package Added tag(s) pending. > tags 952353 + patch Bug #952353 [src:swiftsc] swiftsc: FTBFS: dh: error: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 3) line 1. Added tag(s) patch. > tags 952353 + pending Bug #952353 [src:swiftsc] swiftsc: FTBFS: dh: error: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 3) line 1. Added tag(s) pending. -- 949933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949933 952353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971754: ABI breakage from 1.4.1 to 1.4.2
On Sat, 2021-01-16 at 14:05 +0100, Paul Gevers wrote: > > I was expecting a new upstream release to be incorporated, but I > understand upstream didn't release anything new yet. For whatever > it's worth, your MR doesn't look too weird. Thanks, I've uploaded it to delayed/1 in case someone disagrees. Otherwise it'll be on the NEW queue tomorrow for the new binary packages, and once it's done there a binNMU for gst-plugins-bad1.0 can happen and everything can migrate to testing. signature.asc Description: This is a digitally signed message part
Bug#980194: [Pkg-privacy-maintainers] Bug#980194: Bug#980194: mat2: autopkgtest regression in testing: AssertionError: ValueError not raised
Hi Paul, On 21-01-15 22:57:54, Georg Faerber wrote: > I'm wondering if this is related to the recent upload of media-types > [1]. > > This test [2], which installed media-types 1.0.1, was successful, > whereas the test [3], which installed media-types 1.1.0, wasn't. I've requested a test [1] in testing with media-types from unstable, which was successful. The problem seems a regression in media-types, which is fixed in media-types >= 3.0.0. Given this, is there anything else required from my side? Cheers, Georg [1] https://ci.debian.net/data/autopkgtest/testing/amd64/m/mat2/9735398/log.gz
Bug#980225: lvm2-lockd: lvmlockd.service fails to start as of the latest update to 2.03.11-1 in sid
Package: lvm2-lockd Version: 2.03.11-1 Severity: grave Justification: renders package unusable Dear Maintainer, after the update of lvm2 packages to version 2.03.11-1 in sid, the lvmlockd.service fails to start and just hangs till systemctl times out and exits with an error. The previous version worked flawlessly on my laptop. Please let me know if there are any checks I can do to help nailing down the problem, and/or any relevant configuration details that I can provide. Thanks in advance, best regards Giacomo Mulas -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (401, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.4-jak (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to it_IT.UTF-8), LANGUAGE=it_IT,en_EN Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lvm2-lockd depends on: ii libc6 2.31-9 ii libdlm3 4.0.9-2 ii libsanlock-client1 3.8.2-1+b2 ii libselinux1 3.1-2+b2 ii libudev1247.2-4 ii lvm22.03.11-1 lvm2-lockd recommends no packages. lvm2-lockd suggests no packages. -- no debconf information
Bug#980228: kservice: flaky autopkgtest
Source: kservice
Version: 5.70.0-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
kservice is a key package, which is why we noticed an autopkgtest
failures as part of our checks on the status of bullseye. I looked into
the history of your autopkgtest [1] and it fails regularly on nearly all
architectures. I copied some of the output at the bottom of this report
(but it's not always the same).
Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.
Please do get in touch if we need to dive into this together. Or if you
want to discuss this issue.
Paul
https://ci.debian.net/packages/k/kservice/
https://ci.debian.net/data/autopkgtest/testing/amd64/k/kservice/9693624/log.gz
autopkgtest [21:20:54]: test testsuite: [---
Openbox-Message: Unable to find a valid menu file
"/var/lib/openbox/debian-menu.xml"
kbuildsycoca5 running...
cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=-j1
Running tests...
/usr/bin/ctest --force-new-ctest-process -j1
Test project
/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/obj-x86_64-linux-gnu
Start 1: ksycocatest
1/11 Test #1: ksycocatest ..***Failed0.69 sec
* Start testing of KSycocaTest *
Config: Using QtTest library 5.15.2, Qt 5.15.2
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 10.2.1
20201207), debian unknown
QDEBUG : KSycocaTest::initTestCase() created
"/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/share/kservicetypes5/fakeGlobalServiceType.desktop"
PASS : KSycocaTest::initTestCase()
QSYSTEM: KSycocaTest::ensureCacheValidShouldCreateDB()
"kf5-applications.menu" not found in
("/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/config/menus")
PASS : KSycocaTest::ensureCacheValidShouldCreateDB()
kbuildsycoca5 running...
"kf5-applications.menu" not found in
("/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/config/menus")
QDEBUG : KSycocaTest::kBuildSycocaShouldEmitDatabaseChanged() waiting
for signal
QDEBUG : KSycocaTest::kBuildSycocaShouldEmitDatabaseChanged() got signal
QDEBUG : KSycocaTest::kBuildSycocaShouldEmitDatabaseChanged() created
"/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/share/kservicetypes5/fakeGlobalServiceType.desktop"
PASS : KSycocaTest::kBuildSycocaShouldEmitDatabaseChanged()
QDEBUG : KSycocaTest::dirInFutureShouldRebuildSycocaOnce() Time changed
for
/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/share/kservicetypes5
QDEBUG : KSycocaTest::dirInFutureShouldRebuildSycocaOnce()
QDateTime(2021-01-14 21:21:00.812 UTC Qt::LocalTime)
QDateTime(2021-01-14 21:22:00.000 UTC Qt::LocalTime)
QSYSTEM: KSycocaTest::dirInFutureShouldRebuildSycocaOnce()
"kf5-applications.menu" not found in
("/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/config/menus")
QDEBUG : KSycocaTest::dirInFutureShouldRebuildSycocaOnce() Time changed
back for
/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/share/kservicetypes5
QDEBUG : KSycocaTest::dirInFutureShouldRebuildSycocaOnce()
QDateTime(2021-01-14 21:21:00.838 UTC Qt::LocalTime)
QDateTime(2021-01-14 21:21:00.000 UTC Qt::LocalTime)
PASS : KSycocaTest::dirInFutureShouldRebuildSycocaOnce()
QDEBUG : KSycocaTest::dirTimestampShouldBeCheckedRecursively() Time
changed for
/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/config/menus/fakeSubserviceDirectory
QDEBUG : KSycocaTest::dirTimestampShouldBeCheckedRecursively()
QDateTime(2021-01-14 21:21:00.838 UTC Qt::LocalTime)
QDateTime(2021-01-14 21:22:00.000 UTC Qt::LocalTime)
QDEBUG : KSycocaTest::dirTimestampShouldBeCheckedRecursively() Waited
1s, calling ensureCacheValid (should rebuild)
QSYSTEM: KSycocaTest::dirTimestampShouldBeCheckedRecursively()
"kf5-applications.menu" not found in
("/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/config/menus")
QDEBUG : KSycocaTest::dirTimestampShouldBeCheckedRecursively() Waited
1s, calling ensureCacheValid (should not rebuild)
PASS : KSycocaTest::dirTimestampShouldBeCheckedRecursively()
QDEBUG : KSycocaTest::recursiveCheckShouldIgnoreLinksGoingUp() Time
changed for
/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/config
QDEBUG : KSycocaTest::recursiveCheckShouldIgnoreLinksGoingUp()
QDateTime(2021-01-14 21:21:0
Bug#980194: marked as done (mat2: autopkgtest regression in testing: AssertionError: ValueError not raised)
Your message dated Sat, 16 Jan 2021 15:10:43 +0100
with message-id <14d0a78a-7b87-72b7-da32-932eca5e5...@debian.org>
and subject line Re: [Pkg-privacy-maintainers] Bug#980194: Bug#980194: mat2:
autopkgtest regression in testing: AssertionError: ValueError not raised
has caused the Debian Bug report #980194,
regarding mat2: autopkgtest regression in testing: AssertionError: ValueError
not raised
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
980194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mat2
Version: 0.12.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a very recent change in testing the autopkgtest of your package
started to fail. I copied some of the output at the bottom of this
report. Can you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
https://ci.debian.net/data/autopkgtest/testing/amd64/m/mat2/9718736/log.gz
=== FAILURES
===
_ TestGetMeta.test_png
_
self =
def test_png(self):
proc = subprocess.Popen(mat2_binary + ['--show',
'./tests/data/dirty.png'],
stdout=subprocess.PIPE)
stdout, _ = proc.communicate()
> self.assertIn(b'Comment: This is a comment, be careful!', stdout)
E AssertionError: b'Comment: This is a comment, be careful!' not
found in b"[-] ./tests/data/dirty.png's format (image/vnd.mozilla.apng)
is not supported\n"
tests/test_climat2.py:192: AssertionError
___ TestCorruptedEmbedded.test_docx
self =
def test_docx(self):
shutil.copy('./tests/data/embedded_corrupted.docx',
'./tests/data/clean.docx')
parser, _ = parser_factory.get_parser('./tests/data/clean.docx')
with self.assertRaises(ValueError):
> parser.remove_all()
E AssertionError: ValueError not raised
tests/test_corrupted_files.py:69: AssertionError
_ TestCorruptedFiles.test_png2
_
self =
def test_png2(self):
shutil.copy('./tests/test_libmat2.py', './tests/clean.png')
with self.assertRaises(ValueError):
> parser_factory.get_parser('./tests/clean.png')
E AssertionError: ValueError not raised
tests/test_corrupted_files.py:126: AssertionError
_ TestCorruptedFiles.test_tar
__
self =
def test_tar(self):
with tarfile.TarFile.open('./tests/data/clean.tar', 'w') as zout:
zout.add('./tests/data/dirty.flac')
zout.add('./tests/data/dirty.docx')
zout.add('./tests/data/dirty.jpg')
zout.add('./tests/data/embedded_corrupted.docx')
tarinfo = tarfile.TarInfo(name='./tests/data/dirty.png')
tarinfo.mtime = time.time()
tarinfo.uid = 1337
tarinfo.gid = 1338
tarinfo.size = os.stat('./tests/data/dirty.png').st_size
with open('./tests/data/dirty.png', 'rb') as f:
zout.addfile(tarinfo, f)
p, mimetype = parser_factory.get_parser('./tests/data/clean.tar')
self.assertEqual(mimetype, 'application/x-tar')
with self.assertRaises(ValueError):
> p.get_meta()
E AssertionError: ValueError not raised
tests/test_corrupted_files.py:321: AssertionError
_ TestCorruptedFiles.test_zip
__
self =
def test_zip(self):
with zipfile.ZipFile('./tests/data/clean.zip', 'w') as zout:
zout.write('./tests/data/dirty.flac')
zout.write('./tests/data/dirty.docx')
zout.write('./tests/data/dirty.jpg')
zout.write('./tests/data/embedded_corrupted.docx')
p, mimetype = parser_factory.get_parser('./tests/data/clean.zip')
self.assertEqual(mimetype, 'application/zip')
with self.assertRaises(ValueError):
> p.get_meta()
E AssertionError: ValueError not raised
tests/test_corrupted_files.py:243: AssertionError
TestReadOnlyArchiveMembers.test_onlymember_tar
self =
def test_onlymember_tar(self):
with tarfile.open('./tests/data/clean.tar', 'w') as zout:
z
Processed: tagging 980228
Processing commands for cont...@bugs.debian.org: > tags 980228 + pending Bug #980228 [src:kservice] kservice: flaky autopkgtest Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 980228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980231: node-mysticatea-eslint-plugin: autopkgtest regression in testing: 'es5.js' should include existing rule 'multiline-comment-style'
Source: node-mysticatea-eslint-plugin Version: 11.0.0~ds-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent change somewhere outside of your package the autopkgtest of your package started to fail. I copied some of the output at the bottom of this report. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-mysticatea-eslint-plugin/9705343/log.gz not ok 105 'es5.js' should include existing rule 'multiline-comment-style'. The expression evaluated to a falsy value: assert(ruleId in config.rules) AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value: assert(ruleId in config.rules) at Context. (tests/lib/configs/es5.js:39:13) at callFn (/usr/share/nodejs/mocha/lib/runnable.js:364:21) at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:352:5) at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:677:10) at /usr/share/nodejs/mocha/lib/runner.js:801:12 at next (/usr/share/nodejs/mocha/lib/runner.js:594:14) at /usr/share/nodejs/mocha/lib/runner.js:604:7 at next (/usr/share/nodejs/mocha/lib/runner.js:486:14) at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:572:5) at processImmediate (internal/timers.js:461:21) OpenPGP_signature Description: OpenPGP digital signature
Bug#980225: lvm2-lockd: lvmlockd.service fails to start as of the latest update to 2.03.11-1 in sid
Control: tag -1 confirmed Hi On Sat, Jan 16, 2021 at 02:41:30PM +0100, Giacomo Mulas wrote: > after the update of lvm2 packages to version 2.03.11-1 in sid, > the lvmlockd.service fails to start and just hangs till > systemctl times out and exits with an error. The previous version > worked flawlessly on my laptop. I found the problem. Some of the binaries are not longer built with systemd notify support, so they fail to report startup success. Bastian -- It is necessary to have purpose. -- Alice #1, "I, Mudd", stardate 4513.3
Processed: Re: Bug#980225: lvm2-lockd: lvmlockd.service fails to start as of the latest update to 2.03.11-1 in sid
Processing control commands: > tag -1 confirmed Bug #980225 [lvm2-lockd] lvm2-lockd: lvmlockd.service fails to start as of the latest update to 2.03.11-1 in sid Added tag(s) confirmed. -- 980225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980225 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980232: tortoisehg is not installable due to new mercurial
Package: tortoisehg Version: 5.5.2-3 Severity: serious Tags: sid bullseye Justification: not installable Dear maintainer(s), Mercurial in unstable has been updated. This update makes tortoisehg not installable due to an upper limit it it's Depends. Please fix tortoisehg to work with the newer mercurial. Paul -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled OpenPGP_signature Description: OpenPGP digital signature
Bug#980202: FTBFS: gscan2pdf tests fail
Thanks for the head up. I note that it built fine in sid a month ago: https://buildd.debian.org/status/fetch.php?pkg=gscan2pdf&arch=all&ver=2.10.2-1&stamp=1608242025&raw=0 but that it didn't a couple of days ago in reproducible-builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gscan2pdf.html I guess something changed in the amd64 dependencies, because I can reproduce the problem now, too. OpenPGP_signature Description: OpenPGP digital signature
Bug#980228: marked as done (kservice: flaky autopkgtest)
Your message dated Sat, 16 Jan 2021 15:03:52 +
with message-id
and subject line Bug#980228: fixed in kservice 5.77.0-3
has caused the Debian Bug report #980228,
regarding kservice: flaky autopkgtest
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
980228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kservice
Version: 5.70.0-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
kservice is a key package, which is why we noticed an autopkgtest
failures as part of our checks on the status of bullseye. I looked into
the history of your autopkgtest [1] and it fails regularly on nearly all
architectures. I copied some of the output at the bottom of this report
(but it's not always the same).
Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.
Please do get in touch if we need to dive into this together. Or if you
want to discuss this issue.
Paul
https://ci.debian.net/packages/k/kservice/
https://ci.debian.net/data/autopkgtest/testing/amd64/k/kservice/9693624/log.gz
autopkgtest [21:20:54]: test testsuite: [---
Openbox-Message: Unable to find a valid menu file
"/var/lib/openbox/debian-menu.xml"
kbuildsycoca5 running...
cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=-j1
Running tests...
/usr/bin/ctest --force-new-ctest-process -j1
Test project
/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/obj-x86_64-linux-gnu
Start 1: ksycocatest
1/11 Test #1: ksycocatest ..***Failed0.69 sec
* Start testing of KSycocaTest *
Config: Using QtTest library 5.15.2, Qt 5.15.2
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 10.2.1
20201207), debian unknown
QDEBUG : KSycocaTest::initTestCase() created
"/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/share/kservicetypes5/fakeGlobalServiceType.desktop"
PASS : KSycocaTest::initTestCase()
QSYSTEM: KSycocaTest::ensureCacheValidShouldCreateDB()
"kf5-applications.menu" not found in
("/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/config/menus")
PASS : KSycocaTest::ensureCacheValidShouldCreateDB()
kbuildsycoca5 running...
"kf5-applications.menu" not found in
("/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/config/menus")
QDEBUG : KSycocaTest::kBuildSycocaShouldEmitDatabaseChanged() waiting
for signal
QDEBUG : KSycocaTest::kBuildSycocaShouldEmitDatabaseChanged() got signal
QDEBUG : KSycocaTest::kBuildSycocaShouldEmitDatabaseChanged() created
"/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/share/kservicetypes5/fakeGlobalServiceType.desktop"
PASS : KSycocaTest::kBuildSycocaShouldEmitDatabaseChanged()
QDEBUG : KSycocaTest::dirInFutureShouldRebuildSycocaOnce() Time changed
for
/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/share/kservicetypes5
QDEBUG : KSycocaTest::dirInFutureShouldRebuildSycocaOnce()
QDateTime(2021-01-14 21:21:00.812 UTC Qt::LocalTime)
QDateTime(2021-01-14 21:22:00.000 UTC Qt::LocalTime)
QSYSTEM: KSycocaTest::dirInFutureShouldRebuildSycocaOnce()
"kf5-applications.menu" not found in
("/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/config/menus")
QDEBUG : KSycocaTest::dirInFutureShouldRebuildSycocaOnce() Time changed
back for
/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/share/kservicetypes5
QDEBUG : KSycocaTest::dirInFutureShouldRebuildSycocaOnce()
QDateTime(2021-01-14 21:21:00.838 UTC Qt::LocalTime)
QDateTime(2021-01-14 21:21:00.000 UTC Qt::LocalTime)
PASS : KSycocaTest::dirInFutureShouldRebuildSycocaOnce()
QDEBUG : KSycocaTest::dirTimestampShouldBeCheckedRecursively() Time
changed for
/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/config/menus/fakeSubserviceDirectory
QDEBUG : KSycocaTest::dirTimestampShouldBeCheckedRecursively()
QDateTime(2021-01-14 21:21:00.838 UTC Qt::LocalTime)
QDateTime(2021-01-14 21:22:00.000 UTC Qt::LocalTime)
QDE
Processed: unarchiving 861682, closing 861682, archiving 861682
Processing commands for cont...@bugs.debian.org:
> unarchive 861682
Bug #861682 {Done: Jochen Sprickerhof } [libpoco-dev]
libpoco-dev: missing Depends on libssl-dev
Unarchived Bug 861682
> close 861682 1.7.8+dfsg1-1
Bug #861682 {Done: Jochen Sprickerhof } [libpoco-dev]
libpoco-dev: missing Depends on libssl-dev
Marked as fixed in versions poco/1.7.8+dfsg1-1.
Bug #861682 {Done: Jochen Sprickerhof } [libpoco-dev]
libpoco-dev: missing Depends on libssl-dev
Bug 861682 is already marked as done; not doing anything.
> archive 861682
Bug #861682 {Done: Jochen Sprickerhof } [libpoco-dev]
libpoco-dev: missing Depends on libssl-dev
archived 861682 to archive/82 (from 861682)
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
861682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#980238: do not depend on the non-public binutils ABI
Package: src:ucx Version: 1.10.0~rc1-2 Severity: serious Tags: sid bullseye ucx should not depend on the non-public binutils ABI. This always generated an upper dependency on libbinutils. If you think it's worth having this dependency, please statically link with libbinutils and record the the version used in a Built-Using flag. Or just configure with --disable-backtrace-detail.
Bug#980240: Cyrus-common: /etc/cron.daily/cyrus-imapd is not working
Package: cyrus-common Version: 3.0.8-6+deb10u4 Severity: grave Tags: patch Justification: causes non-serious data loss Dear maintainer, during a installation of Cyrus-common id discovered a bug in the file: /etc/cron.daily/cyrus-imapd The script is not executed because the Cyrus version check does not match the cyrus version installed on Debian Buster. Als a result the cyrus mailbox db is not exported, which can cause the loss of mailbox cwconfiguration, if the db gets corrupted. here is the diff relativ to /etc to fix the problem: --- a/cron.daily/cyrus-imapd +++ b/cron.daily/cyrus-imapd @@ -33,7 +33,7 @@ umask 022 && [ -f /usr/lib/cyrus/cyrus-hardwired-config.txt ] \ || exit 0 # Check if Cyrus is installed (vs. removed but not purged) -grep -qE '^PACKAGE_VERSION[[:blank:]]+[30][.][245]' \ +grep -qE '^PACKAGE_VERSION[[:blank:]]+3.0[.][2458]' \ /usr/lib/cyrus/cyrus-hardwired-config.txt >/dev/null 2>&1 || exit 0 # 1. backup mailbox database Cheers /alex -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-13-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cyrus-common depends on: ii adduser 3.118 ii db-upgrade-util 5.3.1+nmu1 ii db-util 5.3.1+nmu1 ii debconf [debconf-2.0] 1.5.71 ii dpkg1.19.7 ii e2fsprogs 1.44.5-1+deb10u3 ii gawk1:4.2.1+dfsg-1 ii init-system-helpers 1.56+nmu1 ii libc6 2.28-10 ii libclamav9 0.102.4+dfsg-0+deb10u1 ii libcom-err2 1.44.5-1+deb10u3 ii libgcc1 1:8.3.0-6 ii libgssapi-krb5-21.17-3+deb10u1 ii libical33.0.4-3 ii libicu6363.1-6+deb10u1 ii libjansson4 2.12-1 ii libk5crypto31.17-3+deb10u1 ii libkrb5-3 1.17-3+deb10u1 ii libkrb5support0 1.17-3+deb10u1 ii libldap-2.4-2 2.4.47+dfsg-3+deb10u4 ii libpcre32:8.39-12 ii libsasl2-2 2.1.27+dfsg-1+deb10u1 ii libsasl2-modules2.1.27+dfsg-1+deb10u1 ii libsnmp30 5.7.3+dfsg-5+deb10u1 ii libsqlite3-03.27.2-3+deb10u1 ii libssl1.1 1.1.1d-0+deb10u4 ii libstdc++6 8.3.0-6 ii libwrap07.6.q-28 ii libxapian30 1.4.11-1 ii libxml2 2.9.4+dfsg1-7+deb10u1 ii libzephyr4 3.1.2-1+b3 ii lsb-base10.2019051400 ii netbase 5.6 ii perl5.28.1-6+deb10u1 ii postfix [mail-transport-agent] 3.4.14-0+deb10u1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages cyrus-common recommends: ii cyrus-admin 3.0.8-6+deb10u4 ii cyrus-imapd 3.0.8-6+deb10u4 Versions of packages cyrus-common suggests: ii apt-listchanges3.19 ii cyrus-admin3.0.8-6+deb10u4 pn cyrus-caldav pn cyrus-clients pn cyrus-doc ii cyrus-imapd3.0.8-6+deb10u4 pn cyrus-murder pn cyrus-nntpd pn cyrus-pop3d pn cyrus-replication ii sasl2-bin 2.1.27+dfsg-1+deb10u1 -- Configuration Files: /etc/cron.daily/cyrus-imapd changed [not included] /etc/cyrus.conf changed [not included] /etc/default/cyrus-imapd changed [not included] /etc/imapd.conf changed [not included] -- debconf information: * cyrus-common/removespools: true
Bug#972246: numba ftbfs in unstable with python3.9 as supported python3 version
Source: numba Followup-For: Bug #972246 X-Debbugs-Cc: Andreas Tille Hi Andreas, check the upstream bug. The fix was merged only 4 days ago, 0.52.0 does not have it. We could try backporting PR#6579 to 0.52.0. Maybe it will work but there is a reasonable chance that it won't.
Processed (with 4 errors): automake-1.15 rm
Processing commands for cont...@bugs.debian.org:
> clone 909210 -1
Bug #909210 [automake-1.15] don't ship automake-1.15 in bullseye
Bug 909210 cloned as bug 980241
No valid blocking bug(s) given; not doing anything
Failed to clone 909210: Unknown/archived blocking bug(s):950706.
> severity -1 normal
Failed to set severity of Bug -1 to normal: The 'bug' parameter ("-1") to
Debbugs::Control::set_severity did not pass regex check
.
> reassign -1 ftp.debian.org
Failed to clear fixed versions and reopen on -1: The 'bug' parameter ("-1") to
Debbugs::Control::set_package did not pass regex check
.
> retitle -1 RM: automake-1.15 -- RoQA; replaced by automake-1.16
Failed to set the title of -1: The 'bug' parameter ("-1") to
Debbugs::Control::set_title did not pass regex check
.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
909210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909210
980241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 980241 is normal, reassign 980241 to ftp.debian.org ...
Processing commands for cont...@bugs.debian.org: > severity 980241 normal Bug #980241 [automake-1.15] don't ship automake-1.15 in bullseye Severity set to 'normal' from 'serious' > reassign 980241 ftp.debian.org Bug #980241 [automake-1.15] don't ship automake-1.15 in bullseye Bug reassigned from package 'automake-1.15' to 'ftp.debian.org'. No longer marked as found in versions automake-1.15/1:1.15.1-5. Ignoring request to alter fixed versions of bug #980241 to the same values previously set > retitle 980241 RM: automake-1.15 -- RoQA; replaced by automake-1.16 Bug #980241 [ftp.debian.org] don't ship automake-1.15 in bullseye Changed Bug title to 'RM: automake-1.15 -- RoQA; replaced by automake-1.16' from 'don't ship automake-1.15 in bullseye'. > thanks Stopping processing here. Please contact me if you need assistance. -- 980241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#975131: datovka: FTBFS: src/delegates/tag_item.cpp:59:15: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined
Dear Maintainer, I tried to build your package in a sid chroot environment, and I confirm that one-line patch fixes the issue. Kind Regards
Bug#909210: Does it make sense to ship automake-1.15 in bullseye?
* Ivo De Decker : > On Thu, May 28, 2020 at 09:34:18AM -0700, Vagrant Cascadian wrote: > > I *think* they are now no remaining depends or build-depends on > > automake-1.15, seems like it could be removed now? > > dak rm seems to agree, so I added a testing removal hint (and upgraded this > bug so it doesn't come back). It's probably time to file an ftp removal bug > for unstable? Cloned as #980241 and assigned to ftp.debian.org. Best, Chris
Bug#979817: marked as done (lld: missing Breaks+Replaces: llvm (= 1:11.0-51+nmu1))
Your message dated Sat, 16 Jan 2021 16:04:42 + with message-id and subject line Bug#979817: fixed in llvm-defaults 0.51+nmu4 has caused the Debian Bug report #979817, regarding lld: missing Breaks+Replaces: llvm (= 1:11.0-51+nmu1) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lld Version: 1:11.0-51+nmu2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../lld_1%3a11.0-51+nmu2_amd64.deb ... Unpacking lld (1:11.0-51+nmu2) ... dpkg: error processing archive /var/cache/apt/archives/lld_1%3a11.0-51+nmu2_amd64.deb (--unpack): trying to overwrite '/usr/bin/wasm-ld', which is also in package llvm 1:11.0-51+nmu1 Errors were encountered while processing: /var/cache/apt/archives/lld_1%3a11.0-51+nmu2_amd64.deb The existing Replaces: llvm (= 0.51+nmu1) Breaks: llvm (= 0.51+nmu1) are versioned after the source version, not the binary version of the llvm binary package. cheers, Andreas llvm=1:11.0-51+nmu1_lld=1:11.0-51+nmu2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: llvm-defaults Source-Version: 0.51+nmu4 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of llvm-defaults, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated llvm-defaults package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 14 Jan 2021 16:39:00 +0100 Source: llvm-defaults Architecture: source Version: 0.51+nmu4 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Jonas Smedegaard Closes: 979817 Changes: llvm-defaults (0.51+nmu4) unstable; urgency=medium . * Non-maintainer upload. . * really fix relax breaks+replaces; closes: bug#979817, thanks (again) to Andreas Beckmann Checksums-Sha1: 5d943a21ad7b271eb8b777feb9a2a7b2920985ae 3140 llvm-defaults_0.51+nmu4.dsc 984082306036523e94a4af831ed8cbca2acd32f2 12740 llvm-defaults_0.51+nmu4.tar.xz fad6bc71d0f29b3af7668ccd8b5dbabb1a136010 12636 llvm-defaults_0.51+nmu4_amd64.buildinfo Checksums-Sha256: 25262c8e2d6ed5e5a835b76c0ca6fdb0ed9ba5d49a5178f1edd96e19593c69e2 3140 llvm-defaults_0.51+nmu4.dsc 031473574ad81dcce379c071482241b7270101360fa55b8d5e5a7d31ed91f5c7 12740 llvm-defaults_0.51+nmu4.tar.xz 87c1bcd06fc66a79cc2764a266f1074bebc37d7530fcb0b8e81c50e4315637be 12636 llvm-defaults_0.51+nmu4_amd64.buildinfo Files: 90ee8ffe58521b2c25e8b855c952ce09 3140 devel optional llvm-defaults_0.51+nmu4.dsc 60a8cc28293f5d34d9879d954314e7dc 12740 devel optional llvm-defaults_0.51+nmu4.tar.xz 1d975962f6cb6436f5561cb5e6582636 12636 devel optional llvm-defaults_0.51+nmu4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmAAZrEACgkQLHwxRsGg ASEoWA/+JJnFgm69TpuqIBVRPgf+4VGXDxaMogsUwr2xoutmgMOCY2ociJKpqCSB ueQkGl4s+YWhsy3SJhOVxnJvyDLHbedGMzg8CFJ/S/oXsmUL4peTP6Ozkxg99V/Q 6eYTPNPRAvn8ypYDT5AcoRNrkWKwVwIOiwYresua3mGEZZgYHaw1C6rUCoLHCdsv XDYB+Htsf4y35hFXH550y8q5jPgI/ZvIrhluhVLQEUGQPMdMxZfu5z9NQleC4cPB wkbAFngatPqZBjunqIjY7+tNcr+6F6IKc8vevVWJZ56xL7UfunxyEa0h7Bjd3/x7 T8NxAtVjr403cqsazQR7Wb2OCLP+MhjRYJOuL4VmrkWlR6IIE4IOTyTjrNWcrCgB Z/hGEIx7IQvg0XFrPzwKVDl2VMWs4NfnkGPnOcapF/g7zIPqQWvDqfjQn3aJxjzn q5rgXTz9kCbWTAxO878p0pakNp4r9ouEbFMyUvzDnSfTVjUsuEcIh6kZdnwjTb59 psNCc8QJwS/1bZLtF2R3NSxdp4WrIZJW7QhDsOyDZcvlt0VoZIi32I36z7CgeIb8 /eQ6HKQFJ1j8FqKGybYtrrQp8h4bzgyLBNLNcpQ2IvLs9MXqVUoBOHDcGGHQiMiM 9woG2eve1/zwGD835NLxuHfdMdJapDGtmmTYzZcgNxCY2NHeK
Bug#975124: dogecoin: FTBFS: qt/trafficgraphwidget.cpp:53:9: error: invalid use of incomplete type ‘class QPainterPath’
[Lucas Nussbaum] > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > qt/trafficgraphwidget.cpp: In member function ‘void > > TrafficGraphWidget::paintPath(QPainterPath&, QQueue&)’: > > qt/trafficgraphwidget.cpp:53:9: error: invalid use of incomplete type > > ‘class QPainterPath’ > >53 | path.moveTo(x, YMARGIN + h); > > | ^~~~ Perhaps the code is missing a '#include ', ref https://doc.qt.io/qt-5/qpainterpath.html >? -- Happy hacking Petter Reinholdtsen
Bug#971040: gnome-shell-extension-easyscreencast: please test with GNOME Shell 3.38 and update dependency
Control: tags -1 - fixed + pending Hello Bruno, Thanks for pointing out to the fix and providing an MR, I have also replied there. I removed the "fixed" tag as it doesn't apply to this situation, I believe "pending" would be more appropriate. I'm gonna test the fix and upload if everything works (as said on the MR, feel free to change it to apply a patch instead of changing upstream). Cheers -- Samuel Henrique
Processed: gnome-shell-extension-easyscreencast: please test with GNOME Shell 3.38 and update dependency
Processing control commands: > tags -1 - fixed + pending Bug #971040 [gnome-shell-extension-easyscreencast] gnome-shell-extension-easyscreencast: please test with GNOME Shell 3.38 and update dependency Removed tag(s) fixed. Bug #971040 [gnome-shell-extension-easyscreencast] gnome-shell-extension-easyscreencast: please test with GNOME Shell 3.38 and update dependency Added tag(s) pending. -- 971040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938509: Intent to request the removal from Debian
On Mon, 21 Dec 2020 14:03:10 +0100 Markus Koschany wrote: > Hi, > > as previously announced on debian-devel-games [1] I intend to request the > removal of this source or binary package from Debian at the end of January > 2021. If you are interested in fixing this bug, please let me know in time to > avoid the removal from Debian. > > Markus > > > [1] https://lists.debian.org/debian-devel-games/2020/12/msg00013.html Hello Markus, Last October I tried to port snowballz to python 3. I have it mostly working except for the GUI, which flickers when I move the mouse. If you could advise me on where to send a tar or diff I could fix the issues. Thanks, Caleb Marshall
Bug#980202: FTBFS: gscan2pdf tests fail
This seems to be a bug in imagemagick preventing imagemagick from migrating from unstable to testing: https://tracker.debian.org/pkg/imagemagick https://ci.debian.net/packages/g/gscan2pdf/testing/amd64/ OpenPGP_signature Description: OpenPGP digital signature
Bug#979142: marked as done (FTBFS on s390x)
Your message dated Sat, 16 Jan 2021 17:18:49 + with message-id and subject line Bug#979142: fixed in mtail 3.0.0~rc41-1 has caused the Debian Bug report #979142, regarding FTBFS on s390x to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979142 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mtail Version: 3.0.0~rc38-1 Severity: serious X-Debbugs-Cc: z...@debian.org https://buildd.debian.org/status/logs.php?pkg=mtail&ver=3.0.0%7Erc38-1&arch=s390x It has been tried 3 times, still failed to build. Fail at the same place: === RUN TestReadFromPipe/10ms_false read_pipe_integration_test.go:53: Did not see "lines_total" have delta by deadline: got 0 - 0 = 0, want 3 --- FAIL: TestReadFromPipe (65.00s) --- PASS: TestReadFromPipe/0s_true (5.00s) --- FAIL: TestReadFromPipe/10ms_false (60.00s) It causes mtail hasn't been migrated to testing for 32 days. The out-of-sync bug is rc. --- End Message --- --- Begin Message --- Source: mtail Source-Version: 3.0.0~rc41-1 Done: Filippo Giunchedi We believe that the bug you reported is fixed in the latest version of mtail, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Filippo Giunchedi (supplier of updated mtail package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 16 Jan 2021 17:41:57 +0100 Source: mtail Architecture: source Version: 3.0.0~rc41-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Filippo Giunchedi Closes: 976403 979142 Changes: mtail (3.0.0~rc41-1) unstable; urgency=medium . * New upstream release. + fix racy/flaky pipe tests (Closes: #976403, #979142) * Refresh patches. Checksums-Sha1: 76f3ccad99d246db26fd7d83815bb839d9738cdd 2304 mtail_3.0.0~rc41-1.dsc f2163a9d1bd59d6b44d4bcbc4683a43f6095a6c8 549319 mtail_3.0.0~rc41.orig.tar.gz 4ebf3d3c944d10aecdd91dbdba47f3cffcb623dc 7772 mtail_3.0.0~rc41-1.debian.tar.xz b95c152286597d89ba20afe38235b05c67af31b4 8532 mtail_3.0.0~rc41-1_amd64.buildinfo Checksums-Sha256: 6da16af2ed2f5fb9f3375dd379aaa1aa55c7efce7d7f299cc8c68d599235d60b 2304 mtail_3.0.0~rc41-1.dsc 0e1c171f74c14f716514c1f82d56526a5c8a30c3b82437a5bbe93475ba0ffaac 549319 mtail_3.0.0~rc41.orig.tar.gz c932aa144bcb997589c8c23c6711ba30549ce0ca9ff2ba8a88b816f14764be82 7772 mtail_3.0.0~rc41-1.debian.tar.xz 4f185045b62aed990aaf0e0c425d765e995e77928ac49442ef9515f11e58b978 8532 mtail_3.0.0~rc41-1_amd64.buildinfo Files: 501c1912849e1f427b2b4ff007a8478b 2304 net optional mtail_3.0.0~rc41-1.dsc f58f47f1c1ed8ff8714f48eaa93691bb 549319 net optional mtail_3.0.0~rc41.orig.tar.gz f962e7a722eb289d49e33f1ad13b14c8 7772 net optional mtail_3.0.0~rc41-1.debian.tar.xz 020e75a6d628a8ea25dffc30270acc11 8532 net optional mtail_3.0.0~rc41-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEESpRSzEXGrZapQW7YaWZyoGTcEJQFAmADHUQTHGZpbGlwcG9A ZGViaWFuLm9yZwAKCRBpZnKgZNwQlDirD/9S7sEEv4m4HxjD38QvFtlJu+kIwMiu ixMIpc+eY2C53XtV+MYVX9zTFftPfxe+tdIWGt+pZwDCkJFQ1pLyYWOAga8fFJBn 47NX2Ytqk8bMVY51mO6jIp+qZXwFd0xv5OaYurCRt5Wi4Skp38rjImZxOoOXqFqI k+kkVHDxHH6GdqJb0yUh245xEzQ8evys28c4YhGiGpmQGNjL1DNzTmY3cpwB26sX FvdlnVxYtAWSYEB1oTD4DCW5IxD0t8wynZedTbFsYmG9nivRHlehm28SJFK3FgFO O9vtjR9UvR/G1Jn3niOb0yQ/Sdu+R4CLvM6wkrqfQbNJZp5+TO7mBzU4H35L/FOi hTNCuqjYVrUt4K6sSI8P40D7kyQjx0X9q8XdYQcV5exkrUtsVdXWrLL+nj5VYGoD F7AImgspOjzmgCeTtOM8vtYm6CjA6OTCmVoR/+vaVajfXZAG6W39FvP5YHyr80TC 5n+y1bjDpV3sgKCbJCp/6LMmbnwSnXIoRLda1AZf4f+oBsYGaqGMSfLYwHhTbr// C1nV7jXkZ1KFG0Rjd50LK6i9Aj0n8Nr+qzps0BU10N6npS/qad8bVd5nCY9RtLii xqp8gkzLnwr2ixpzhn0q3jlEj7vT0FXEK5e0bY3kr+cZjH/g1sUrx6vl6aMdIdAW lZtK1GRyu8aWCw== =C46+ -END PGP SIGNATURE End Message ---
Processed: fixed 980240 in 3.2.4-4
Processing commands for cont...@bugs.debian.org: > fixed 980240 3.2.4-4 Bug #980240 [cyrus-common] Cyrus-common: /etc/cron.daily/cyrus-imapd is not working Marked as fixed in versions cyrus-imapd/3.2.4-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 980240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980240 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bump pytest 6.0 bugs to RC
Processing commands for cont...@bugs.debian.org: > # pytest 6.0.2 has been uploaded to unstable > severity 979298 serious Bug #979298 [src:python-mechanicalsoup] python-mechanicalsoup autopkgtests fail with pytest 6 Severity set to 'serious' from 'important' > severity 977067 serious Bug #977067 [src:igdiscover] igdiscover FTBFS with pytest 6 Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 977067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977067 979298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979298 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978353: marked as done (serf: FTBFS: tests failed with OpenSSL 1.1.1i)
Your message dated Sat, 16 Jan 2021 17:35:18 + with message-id and subject line Bug#978353: fixed in serf 1.3.9-9 has caused the Debian Bug report #978353, regarding serf: FTBFS: tests failed with OpenSSL 1.1.1i to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 978353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: serf Version: 1.3.9-8 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > if ! [ -d debian/distcerts ]; then \ > mkdir -p debian/testcerts/private debian/distcerts; \ > cp test/server/*.pem test/server/serfclientcert.p12 debian/distcerts/; \ > (cd debian/testcerts && python3 ../create_certs.py); \ > cp debian/testcerts/*.pem debian/testcerts/private/serfserverkey.pem > debian/testcerts/serfclientcert.p12 test/server/; \ > fi > scons check CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security" > CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" LINKFLAGS="-Wl,-z,relro -Wl,-z,now > -Wl,-z,defs -Wl,--as-needed" > scons: Reading SConscript files ... > Checking for GNU-compatible C compiler...(cached) yes > scons: done reading SConscript files. > scons: Building targets ... > gcc -o test/serf_get.o -c -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -std=c99 > -Wdeclaration-after-statement -Wmissing-prototypes -Wall -O2 -pthread > -isystem /usr/include/mit-krb5 -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG > -DLINUX -D_REENTRANT -D_GNU_SOURCE -DSERF_HAVE_GSSAPI -DMOCKHTTP_OPENSSL -I. > -I/usr/include/apr-1.0 -I/usr/include -I/usr/include test/serf_get.c > test/serf_get.c: In function 'main': > test/serf_get.c:423:21: warning: variable 'request' set but not used > [-Wunused-but-set-variable] > 423 | serf_request_t *request; > | ^~~ > gcc -o test/serf_get -Wl,-z,now -Wl,-z,defs -Wl,--as-needed -pthread > -Wl,-z,relro -Wl,-rpath=/<> test/serf_get.o -L. > -L/usr/lib/x86_64-linux-gnu -L/usr/lib -L/usr/lib/x86_64-linux-gnu/mit-krb5 > -lserf-1 -lssl -lcrypto -lz -lapr-1 -laprutil-1 -lgssapi_krb5 -lkrb5 > -lk5crypto -lcom_err > gcc -o test/serf_response.o -c -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -std=c99 > -Wdeclaration-after-statement -Wmissing-prototypes -Wall -O2 -pthread > -isystem /usr/include/mit-krb5 -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG > -DLINUX -D_REENTRANT -D_GNU_SOURCE -DSERF_HAVE_GSSAPI -DMOCKHTTP_OPENSSL -I. > -I/usr/include/apr-1.0 -I/usr/include -I/usr/include test/serf_response.c > gcc -o test/serf_response -Wl,-z,now -Wl,-z,defs -Wl,--as-needed -pthread > -Wl,-z,relro -Wl,-rpath=/<> test/serf_response.o -L. > -L/usr/lib/x86_64-linux-gnu -L/usr/lib -L/usr/lib/x86_64-linux-gnu/mit-krb5 > -lserf-1 -lssl -lcrypto -lz -lapr-1 -laprutil-1 -lgssapi_krb5 -lkrb5 > -lk5crypto -lcom_err > gcc -o test/serf_request.o -c -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -std=c99 > -Wdeclaration-after-statement -Wmissing-prototypes -Wall -O2 -pthread > -isystem /usr/include/mit-krb5 -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG > -DLINUX -D_REENTRANT -D_GNU_SOURCE -DSERF_HAVE_GSSAPI -DMOCKHTTP_OPENSSL -I. > -I/usr/include/apr-1.0 -I/usr/include -I/usr/include test/serf_request.c > gcc -o test/serf_request -Wl,-z,now -Wl,-z,defs -Wl,--as-needed -pthread > -Wl,-z,relro -Wl,-rpath=/<> test/serf_request.o -L. > -L/usr/lib/x86_64-linux-gnu -L/usr/lib -L/usr/lib/x86_64-linux-gnu/mit-krb5 > -lserf-1 -lssl -lcrypto -lz -lapr-1 -laprutil-1 -lgssapi_krb5 -lkrb5 > -lk5crypto -lcom_err > gcc -o test/serf_spider.o -c -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -std=c99 > -Wdeclaration-after-statement -Wmissing-prototypes -Wall -O2 -pthread > -isystem /usr/include/mit-krb5 -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG > -DLINUX -D_REENTRANT -D_GNU_SOURCE -DSERF_HAVE_GSSAPI -DMOCKHTTP_OPENSSL -I. > -I/usr/include/apr-1.0 -I/usr/include -I/usr/include test/serf_spider.c > test/serf_spider.c: In function 'setup_request': > test/serf_spider.c:332:30: warning: variable 'req_alloc' set but not used > [-Wunused-but-set-variable] > 332 | serf_bucket_alloc_t *req_alloc; > | ^ > t
Bug#947534: marked as done (mp3splt: build-depends on deprecated gnome-doc-utils)
Your message dated Sat, 16 Jan 2021 18:18:27 + with message-id and subject line Bug#947534: fixed in mp3splt 2.6.2+20170630-3.1 has caused the Debian Bug report #947534, regarding mp3splt: build-depends on deprecated gnome-doc-utils to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 947534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mp3splt Version: 2.6.2+20170630-3 Severity: important Control: block 936625 by -1 Control: block 889019 by -1 User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs gnome-doc-utils This package Build-Depends on gnome-doc-utils. gnome-doc-utils is a deprecated package of documentation utilities. Its most recent upstream release was in 2012, with most changes in its git repository since then being translation updates. The GNOME team do not consider gnome-doc-utils to be suitable for release in Debian 11 'bullseye'. The supported replacement is yelp.m4 in yelp-tools, as used in many GNOME 3 packages. A porting guide is available: https://wiki.gnome.org/Initiatives/GnomeGoals/NewDocumentationInfrastructure gnome-doc-utils relies on Python 2 code that seems unlikely to be converted to Python 3, so bug #936625 (part of the effort to remove Python 2 from Debian for Debian 11 'bullseye') has its severity set to serious. This means that this bug is highly likely to be elevated to serious severity at some point in future. Please convert this package to use yelp-tools, or if necessary remove the documentation processing entirely. Thanks, smcv --- End Message --- --- Begin Message --- Source: mp3splt Source-Version: 2.6.2+20170630-3.1 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of mp3splt, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 947...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler (supplier of updated mp3splt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 06 Jan 2021 17:59:57 +0100 Source: mp3splt Architecture: source Version: 2.6.2+20170630-3.1 Distribution: unstable Urgency: medium Maintainer: Ron Lee Changed-By: Andreas Metzler Closes: 947534 957561 Changes: mp3splt (2.6.2+20170630-3.1) unstable; urgency=medium . * Non-maintainer upload. * Use 3.0 (quilt) format, extract 10_Properly-zero-initialise-the-ogg-and-vorbis-state-st.patch from diff. * 20_mp3splt-gtk-0.9.2-fno-common.patch from Getoo: Fix gcc 10 build error. Closes: #957561 * Drop b-d on gnome-doc-utils, configure with --disable-gnome. Closes: #947534 * Add missing b-d on libdbus-glib-1-dev. Checksums-Sha1: 418d81def7a293a824ac2cf735ba92cc1cd1cee1 2273 mp3splt_2.6.2+20170630-3.1.dsc fbbac4f7f6713e8d7a6f034a72f983bb27093b74 7556 mp3splt_2.6.2+20170630-3.1.debian.tar.xz Checksums-Sha256: a19e300e2f978a74ec0e82452a6d5a024c5c91b7e03e2242d7524cdbac31757f 2273 mp3splt_2.6.2+20170630-3.1.dsc 2d7c2d49f4efaa9a330e3b6da78bb94df2923125d42c6fc60cf867ceb596113e 7556 mp3splt_2.6.2+20170630-3.1.debian.tar.xz Files: c58a1da2f67312234a03e269a5397af0 2273 sound optional mp3splt_2.6.2+20170630-3.1.dsc e05c02f9d0f622b45ff1750904bd486c 7556 sound optional mp3splt_2.6.2+20170630-3.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAl/19AcACgkQpU8BhUOC FIRSJw//VLqQVaB7X9XsjqeRJd+YDpsJvzfAhn7R7XqpCEE4nTVCgqJSKlatjijB U3/JGZjMPdYnZpFvXPSQMp+lsFPhvuZpoj7AdpQ8Hdb5JPJLM8PxmGRF8WWNmnra telptJRpWU0+d16XmuQ7nrROhZFX7nHD5PTtcq/MWwP4hSjU25NWDYoETuBKk3pK 4RtEhUzSgkhO66oIMhLsWOq5wQgSNmyOU+1QRRJayUBTZDwhIUCKXzC5zPNYi+QB 9/HtDdQtYMCaUL4AKdOVop3SC8/qFM+sJn7hBM16RC5w03No1IfWQcLQVaa9B/Rl K3aq/zciya7N1jsuuwo7T1d2JsEkWcAcKEzDRKSrBygjg0GU9W3kY1wcHrtwx2bU Aj5lj8Zcxrr+XaN5ZU14oGzJRaBUAtvZyG3vCyU3ab5EcJwptzn1MZYIhHTvyVhv x/wnEu2zfxF+gR4i0HbhDFFNMzWcgEtftxGjfTRti6oV/2nL2OLAAaVmnPNSnDop S2vqODKRasg7JcFoyqJtUvX4CdHhiykgQkmmF+g9Wcbv/PaLuGQ79u3KT1sLxTuz RycwgX3luRJcw3unQeK08u/L7/QOwkEwXxl9MmAQYRKqxUquiV+NNJP+bfXzhVhm Kvsv+aM63erL8+6mLZ8U4OvxviGQ//vOHfnQyf0KAhkP01br1Wk= =4lG1 -END PGP SIGNATURE--
Bug#957561: marked as done (mp3splt: ftbfs with GCC-10)
Your message dated Sat, 16 Jan 2021 18:18:27 + with message-id and subject line Bug#957561: fixed in mp3splt 2.6.2+20170630-3.1 has caused the Debian Bug report #957561, regarding mp3splt: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mp3splt Version: 2.6.2+20170630-3 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/mp3splt_2.6.2+20170630-3_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] CC options_manager.o CC preferences_manager.o CC widgets_helper.o CC drawing_helper.o CC combo_helper.o ../../mp3splt-gtk/src/widgets_helper.c: In function ‘_wh_add_in_table_with_label’: ../../mp3splt-gtk/src/widgets_helper.c:441:3: warning: ‘gtk_misc_set_alignment’ is deprecated [-Wdeprecated-declarations] 441 | gtk_misc_set_alignment(GTK_MISC(label), 0.0, 0.5); | ^~ In file included from /usr/include/gtk-3.0/gtk/gtklabel.h:32, from /usr/include/gtk-3.0/gtk/gtkaccellabel.h:35, from /usr/include/gtk-3.0/gtk/gtk.h:33, from ../../mp3splt-gtk/src/external_includes.h:75, from ../../mp3splt-gtk/src/ui_manager.h:36, from ../../mp3splt-gtk/src/widgets_helper.h:36, from ../../mp3splt-gtk/src/widgets_helper.c:38: /usr/include/gtk-3.0/gtk/deprecated/gtkmisc.h:72:6: note: declared here 72 | void gtk_misc_set_alignment (GtkMisc *misc, | ^~ ../../mp3splt-gtk/src/widgets_helper.c:441:3: warning: ‘gtk_misc_get_type’ is deprecated [-Wdeprecated-declarations] 441 | gtk_misc_set_alignment(GTK_MISC(label), 0.0, 0.5); | ^~ In file included from /usr/include/gtk-3.0/gtk/gtklabel.h:32, from /usr/include/gtk-3.0/gtk/gtkaccellabel.h:35, from /usr/include/gtk-3.0/gtk/gtk.h:33, from ../../mp3splt-gtk/src/external_includes.h:75, from ../../mp3splt-gtk/src/ui_manager.h:36, from ../../mp3splt-gtk/src/widgets_helper.h:36, from ../../mp3splt-gtk/src/widgets_helper.c:38: /usr/include/gtk-3.0/gtk/deprecated/gtkmisc.h:70:9: note: declared here 70 | GType gtk_misc_get_type (void) G_GNUC_CONST; | ^ CC radio_helper.o CC export.o CC ui_manager.o CC douglas_peucker.o CC libmp3splt_manager.o CC drag_and_drop.o CC mutex.o CCLD mp3splt-gtk /usr/bin/ld: main_window.o:/<>/gui-objs/src/../../mp3splt-gtk/src/splitpoints_window.h:62: multiple definition of `tree_columns'; splitpoints_window.o:/<>/gui-objs/src/../../mp3splt-gtk/src/splitpoints_window.h:62: first defined here /usr/bin/ld: gstreamer_control.o:/<>/gui-objs/src/../../mp3splt-gtk/src/splitpoints_window.h:62: multiple definition of `tree_columns'; splitpoints_window.o:/<>/gui-objs/src/../../mp3splt-gtk/src/splitpoints_window.h:62: first defined here /usr/bin/ld: player_control.o:/<>/gui-objs/src/../../mp3splt-gtk/src/splitpoints_window.h:62: multiple definition of `tree_columns'; splitpoints_window.o:/<>/gui-objs/src/../../mp3splt-gtk/src/splitpoints_window.h:62: first defined here /usr/bin/ld: player_window.o:/<>/gui-objs/src/../../mp3splt-gtk/src/splitpoints_window.h:62: mu
Bug#938509: Intent to request the removal from Debian
Hello, Am Samstag, den 16.01.2021, 14:13 -0300 schrieb Caleb Marshall: [...] > Hello Markus, > Last October I tried to port snowballz to python 3. I have it mostly > working except for the GUI, which flickers when I move the mouse. If you > could advise me on where to send a tar or diff I could fix the issues. > Thanks, > Caleb Marshall You could attach a compressed tarball of your diff to your next email and I can take a look at your changes. If the file is > 5 MB you could also send it to me privately. Regards, Markus signature.asc Description: This is a digitally signed message part
Bug#937184: offlineimap: Python2 removal in sid/bullseye
Am Sat, Jan 16, 2021 at 11:12:21AM + schrieb Sudip Mukherjee: > Hi All, > > On Mon, Nov 09, 2020 at 08:14:38PM +0100, Moritz Mühlenhoff wrote: > > On Sun, Aug 02, 2020 at 06:24:44PM +0300, Ilias Tsitsimpis wrote: > > > Control: severity -1 serious > > > > > > On Sun, Jul 26, 2020 at 01:21PM, Moritz Mühlenhoff wrote: > > > > Nine months later there's no progress, let's remove? > > > > > > Agreed. > > > > > > Raising the severity to serious to remove from testing, and then I will > > > request for removal. > > > > Now that offlineimap3 is available in experimental, let's go ahead with > > removal > > of src:offlineimap? > > I have uploaded offlineimap3 to unstable but will not migrate untill we > have 'python3-imaplib2' in testing, which is blocked by #937831, which is > again blocked by this #937184. > > Can we go ahead with this removal please? I can then add a dummy > transitional package so that users of offlineimap can upgrade to > offlineimap3 with Bullseye. > > Since I have the ITA on offlineimap, do I file the RM bug or that needs > to be done by Ilias ? I've went ahead and filed an RM bug. Cheers, Moritz
Bug#979520: marked as done (chromium: Security upgrade to version 87.0.4280.141)
Your message dated Sat, 16 Jan 2021 19:02:09 + with message-id and subject line Bug#979520: fixed in chromium 87.0.4280.141-0.1~deb10u1 has caused the Debian Bug report #979520, regarding chromium: Security upgrade to version 87.0.4280.141 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979520 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: chromium Version: 87.0.4280.88-0.4 Severity: normal X-Debbugs-Cc: sedat.di...@gmail.com Dear Maintainer, there is a security fixed version 87.0.4280.141 of chrome available. Can you please provide an adapted chromium package. Thanks in advance. Regards, - Sedat - [1] https://chromereleases.googleblog.com/2021/01/stable-channel-update-for-desktop.html -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (99, 'buildd-unstable'), (99, 'buildd-experimental'), (99, 'experimental'), (99, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.11.0-rc2-5-amd64-clang11-cfi (SMP w/4 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chromium depends on: ii chromium-common 87.0.4280.88-0.4 ii libasound2 1.2.4-1.1 ii libatk-bridge2.0-0 2.38.0-1 ii libatk1.0-0 2.36.0-2 ii libatomic1 10.2.1-3 ii libatspi2.0-02.38.0-2 ii libavcodec58 7:4.3.1-5 ii libavformat587:4.3.1-5 ii libavutil56 7:4.3.1-5 ii libc62.31-9 ii libcairo21.16.0-5 ii libcups2 2.3.3op1-4 ii libdbus-1-3 1.12.20-1 ii libdrm2 2.4.103-2 ii libevent-2.1-7 2.1.12-stable-1 ii libexpat12.2.10-1 ii libflac8 1.3.3-2 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1 ii libgbm1 20.3.2-1 ii libgcc-s110.2.1-3 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.4-1 ii libgtk-3-0 3.24.24-1 ii libharfbuzz0b2.6.7-1 ii libicu67 67.1-5 ii libjpeg62-turbo 1:2.0.5-2 ii libjsoncpp24 1.9.4-4 ii liblcms2-2 2.9-4+b1 ii libminizip1 1.1-8+b1 ii libnspr4 2:4.29-1 ii libnss3 2:3.60-1 ii libopenjp2-7 2.3.1-1 ii libopus0 1.3.1-0.1 ii libpango-1.0-0 1.46.2-3 ii libpangocairo-1.0-0 1.46.2-3 ii libpng16-16 1.6.37-3 ii libpulse013.0-5 ii libre2-9 20201101+dfsg-2 ii libsnappy1v5 1.1.8-1 ii libstdc++6 10.2.1-3 ii libwebp6 0.6.1-2+b1 ii libwebpdemux20.6.1-2+b1 ii libwebpmux3 0.6.1-2+b1 ii libx11-6 2:1.7.0-1 ii libx11-xcb1 2:1.7.0-1 ii libxcb1 1.14-2.1 ii libxcomposite1 1:0.4.5-1 ii libxdamage1 1:1.1.5-2 ii libxext6 2:1.3.3-1.1 ii libxfixes3 1:5.0.3-2 ii libxml2 2.9.10+dfsg-6.3+b1 ii libxrandr2 2:1.5.1-1 ii libxslt1.1 1.1.34-4 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages chromium recommends: ii chromium-sandbox 87.0.4280.88-0.4 Versions of packages chromium suggests: pn chromium-driver ii chromium-l10n87.0.4280.88-0.4 pn chromium-shell Versions of packages chromium-common depends on: ii libc6 2.31-9 ii libstdc++6 10.2.1-3 ii libx11-62:1.7.0-1 ii libxext62:1.3.3-1.1 ii x11-utils 7.7+5 ii xdg-utils 1.1.3-2 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages chromium-common recommends: ii chromium-sandbox87.0.4280.88-0.4 ii fonts-liberation1:1.07.4-11 ii gnome-shell [notification-daemon] 3.38.2-1 ii libgl1-mesa-dri 20.3.2-1 ii libu2f-udev 1.1.10-1.1 ii notification-daemon 3.20.0-4 ii plasma-workspace [notification-daemon] 4:5.20.5-1 ii system-config-printer 1.5.13-1 ii upower 0.99.11-2 Versions of packages chromium-sandbox depends on: ii libc6 2.31-9 -- no debconf information --- End Message --- --- Begin Message --- Source: chromium Source-Version: 87.0.4280.141-0.1~deb10u1 Done: Jan Luca Naumann We believe that the bug you reported is fixed in the latest version of chromium, which is due to
Bug#979533: marked as done (chromium: New 87.0.4280.141 (CVE-2020-15995 CVE-2020-16043 CVE-2021-21106 CVE-2021-21107 CVE-2021-21108 CVE-2021-21109 CVE-2021-21110 CVE-2021-21111 CVE-2021-21112 CVE-2021
Your message dated Sat, 16 Jan 2021 19:02:09 + with message-id and subject line Bug#979520: fixed in chromium 87.0.4280.141-0.1~deb10u1 has caused the Debian Bug report #979520, regarding chromium: New 87.0.4280.141 (CVE-2020-15995 CVE-2020-16043 CVE-2021-21106 CVE-2021-21107 CVE-2021-21108 CVE-2021-21109 CVE-2021-21110 CVE-2021-2 CVE-2021-21112 CVE-2021-21113 CVE-2021-21114 CVE-2021-21115 CVE-2021-21116) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979520 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: chromium Version: 87.0.4280.88-0.4 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 87.0.4280.88-0.4~deb10u1 Hi Please see https://chromereleases.googleblog.com/2021/01/stable-channel-update-for-desktop.html here is a new round of CVE fixes for chromium accordingly. CVE-2020-15995 seems a bit unclear, it was previously marked to affect only Chrome on Android, but now appears to affect as well us. Regards, Salvatore --- End Message --- --- Begin Message --- Source: chromium Source-Version: 87.0.4280.141-0.1~deb10u1 Done: Jan Luca Naumann We believe that the bug you reported is fixed in the latest version of chromium, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jan Luca Naumann (supplier of updated chromium package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 11 Jan 2021 17:04:13 +0100 Source: chromium Architecture: source Version: 87.0.4280.141-0.1~deb10u1 Distribution: buster-security Urgency: high Maintainer: Debian Chromium Team Changed-By: Jan Luca Naumann Closes: 979135 979520 Changes: chromium (87.0.4280.141-0.1~deb10u1) buster-security; urgency=high . * Non-maintainer upload. * New upstream security release (closes: 979520). - CVE-2021-21106: Use after free in autofill. Reported by Weipeng Jiang @Krace from Codesafe Team of Legendsec at Qi'anxin Group - CVE-2021-21107: Use after free in drag and drop. Reported by Leecraso and Guang Gong of 360 Alpha Lab - CVE-2021-21108: Use after free in media. Reported by Leecraso and Guang Gong of 360 Alpha Lab - CVE-2021-21109: Use after free in payments. Reported by Rong Jian and Guang Gong of 360 Alpha Lab - CVE-2021-21110: Use after free in safe browsing. Reported by Anonymous - CVE-2021-2: Insufficient policy enforcement in WebUI. Reported by Alesandro Ortiz - CVE-2021-21112: Use after free in Blink. Reported by YoungJoo Lee @ashuu_lee of Raon Whitehat - CVE-2021-21113: Heap buffer overflow in Skia. Reported by tsubmunu - CVE-2020-16043: Insufficient data validation in networking. Reported by Samy Kamkar, Ben Seri at Armis, Gregory Vishnepolsky at Armis - CVE-2021-21114: Use after free in audio. Reported by Man Yue Mo of GitHub Security Lab - CVE-2020-15995: Out of bounds write in V8. Reported by Bohan Liu @P4nda20371774 of Tencent Security Xuanwu Lab - CVE-2021-21115: Use after free in safe browsing. Reported by Leecraso and Guang Gong of 360 Alpha Lab - CVE-2021-21116: Heap buffer overflow in audio. Reported by Alison Huffman, Microsoft Browser Vulnerability Research * Use desktop gl implementation as default. (closes: 979135) Checksums-Sha1: 20283425af744575e71c221b5868c8ceb55fa6cc 3608 chromium_87.0.4280.141-0.1~deb10u1.dsc ef2fa29cf9558fc0afbd7791ea6ee8ef73ac37af 393840792 chromium_87.0.4280.141.orig.tar.xz ea3f1e325cd767960b111a4b7991913cb1e34956 190032 chromium_87.0.4280.141-0.1~deb10u1.debian.tar.xz 692f96e5a8b5ed229a3e4db06a9f0bf6fd6c3ed2 14897 chromium_87.0.4280.141-0.1~deb10u1_source.buildinfo Checksums-Sha256: 66e5c7de3b32da717e59f92ff98b4c5f4c2f89ad88c289b29229d9030dbe1579 3608 chromium_87.0.4280.141-0.1~deb10u1.dsc 577a92da6e3caacd22b0b2aedc9dc7e895652f54ec3e0f615457357be099b2ae 393840792 chromium_87.0.4280.141.orig.tar.xz
Bug#980057: marked as done (ruby-redcarpet: CVE-2020-26298)
Your message dated Sat, 16 Jan 2021 19:02:13 + with message-id and subject line Bug#980057: fixed in ruby-redcarpet 3.4.0-4+deb10u1 has caused the Debian Bug report #980057, regarding ruby-redcarpet: CVE-2020-26298 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 980057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-redcarpet Version: 3.5.0-2 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for ruby-redcarpet. CVE-2020-26298[0]: | Redcarpet is a Ruby library for Markdown processing. In Redcarpet | before version 3.5.1, there is an injection vulnerability which can | enable a cross-site scripting attack. In affected versions no HTML | escaping was being performed when processing quotes. This applies even | when the `:escape_html` option was being used. This is fixed in | version 3.5.1 by the referenced commit. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-26298 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26298 [1] https://github.com/vmg/redcarpet/commit/a699c82292b17c8e6a62e1914d5eccc252272793 [2] https://github.com/advisories/GHSA-q3wr-qw3g-3p4h Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: ruby-redcarpet Source-Version: 3.4.0-4+deb10u1 Done: Utkarsh Gupta We believe that the bug you reported is fixed in the latest version of ruby-redcarpet, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 980...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Utkarsh Gupta (supplier of updated ruby-redcarpet package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 15 Jan 2021 01:32:04 +0530 Source: ruby-redcarpet Binary: ruby-redcarpet ruby-redcarpet-dbgsym Architecture: source amd64 Version: 3.4.0-4+deb10u1 Distribution: buster-security Urgency: high Maintainer: Debian Ruby Extras Maintainers Changed-By: Utkarsh Gupta Description: ruby-redcarpet - Fast, safe and extensible Markdown to (X)HTML parser for Ruby Closes: 980057 Changes: ruby-redcarpet (3.4.0-4+deb10u1) buster-security; urgency=high . * Fix a security vulnerability using `:quote` in combination with the `:escape_html` option. (Fixes: CVE-2020-26298) (Closes: #980057) Checksums-Sha1: 4485875b9583eb45e3d24449ac1d65e0448d70ce 2271 ruby-redcarpet_3.4.0-4+deb10u1.dsc d42646e282d369d9cc3ff76bc7ac0d756a1c462f 59311 ruby-redcarpet_3.4.0.orig.tar.gz a047bff36ff16cae501f6781fa44eb3957e0f4b0 5932 ruby-redcarpet_3.4.0-4+deb10u1.debian.tar.xz 848dd551843b08b4e15ff682ff26038dd515db82 112704 ruby-redcarpet-dbgsym_3.4.0-4+deb10u1_amd64.deb b59760235e2b9ba28c2d9529d9987798878ae4b9 9380 ruby-redcarpet_3.4.0-4+deb10u1_amd64.buildinfo 8f80cbff3efd37b670a97d8a8ca295e13a8567fa 47492 ruby-redcarpet_3.4.0-4+deb10u1_amd64.deb Checksums-Sha256: 49c3bd705562802da52ecd4fbefcca2d928ecddc98dbe7a54043b35b8bebac6f 2271 ruby-redcarpet_3.4.0-4+deb10u1.dsc 506a854c0e1efce8ab84ea76d668ce529804d288298f4678753a1face221292d 59311 ruby-redcarpet_3.4.0.orig.tar.gz c4025375dcfbf4849690c487b6551ce713d43eb0e04bc91f3b0dbd529a312eea 5932 ruby-redcarpet_3.4.0-4+deb10u1.debian.tar.xz d800f78616a3e19d0e3f3551d3a86fe9e285c61e81d4e46c6c2dd40dc97e4a73 112704 ruby-redcarpet-dbgsym_3.4.0-4+deb10u1_amd64.deb fe204135e16d7fff4f8a5ea001830899c281145c5c4e935e70e75133f0862bc9 9380 ruby-redcarpet_3.4.0-4+deb10u1_amd64.buildinfo b5055a8c0ad435b080a4b361f1c0fa342a0005703fabeaf8ff2e164887c477cb 47492 ruby-redcarpet_3.4.0-4+deb10u1_amd64.deb Files: 6f102a33031260493da254fe8fbda53d 2271 ruby optional ruby-redcarpet_3.4.0-4+deb10u1.dsc ed589b29b2b26c2ae0f0c780af6796f8 59311 ruby optional ruby-redcarpet_3.4.0.orig.tar.gz b47d6303b5a79a313b01dda0cf0bbb91 5932 ruby optional ruby-redcarpet_3.4.0-4+deb10u1.debian.tar.xz 083c5b08b
Bug#980256: git-buildpackage: autopkgtest armhf regression: /usr/bin/python: not found
Source: git-buildpackage Version: 0.9.21 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of git-buildpackage the autopkgtest of git-buildpackage fails in testing on armhf when that autopkgtest is run with the binary packages of git-buildpackage from unstable. It passes when run with only packages from testing. In tabular form: passfail git-buildpackage from testing0.9.21 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from git-buildpackage/0.9.21. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=git-buildpackage https://ci.debian.net/data/autopkgtest/testing/armhf/g/git-buildpackage/9735149/log.gz + python3 -c import setuptools + mktemp -d + GBP_TEMPDIR=/tmp/tmp.thAvJcvD7A + gbp buildpackage-rpm --git-packaging-dir=packaging/ --git-export-dir=/tmp/tmp.thAvJcvD7A -D%__python3 /usr/bin/python3 -D%__python /usr/bin/python3 -bb --nodeps sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh: 1: /usr/bin/python: not found sh
Bug#980111: pam breaks frr autopkgtest on armhf and ppc64el: non-zero exit status 1
Control: reassign -1 frr/7.4-1 Hi, On Thu, Jan 14, 2021 at 05:00:26PM +0100, Paul Gevers wrote: > With a recent upload of pam the autopkgtest of frr fails in testing on > armhf and ppc64el when that autopkgtest is run with the binary packages > of pam from unstable. It passes when run with only packages from > testing. In tabular form: > >passfail > pamfrom testing1.4.0-2 > frrfrom testing7.4-1 > all others from testingfrom testing > autopkgtest [11:36:52]: test py-frr-reload: [--- Paul gave me access to a machine similart to the one that's running the test on armhf. It looks like it's a race condition in the test itself (or in the frr scripts): The test runs service frr reload and then runs vtysh -c 'show running-config' to check if the output is changed. With the new pam, this command still shows the old config immediately after the reload. A few seconds later, it shows the new config. I suspect the changes in pam affect the timing of some of the steps involved. As it looks like this is an issue in the frr test (or the frr package), I'm reassigning the bugs there. Cheers, Ivo
Processed: reassign 980111 to frr
Processing commands for cont...@bugs.debian.org: > reassign 980111 frr 7.4-1 Bug #980111 [src:pam, src:frr] pam breaks frr autopkgtest on armhf and ppc64el: non-zero exit status 1 Bug reassigned from package 'src:pam, src:frr' to 'frr'. No longer marked as found in versions frr/7.4-1 and pam/1.4.0-2. Ignoring request to alter fixed versions of bug #980111 to the same values previously set Bug #980111 [frr] pam breaks frr autopkgtest on armhf and ppc64el: non-zero exit status 1 Marked as found in versions frr/7.4-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 980111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980257: puppet-module-puppetlabs-mysql: autopkgtest regression in testing: Service "mysql" is expected to be enabled
Source: puppet-module-puppetlabs-mysql
Version: 8.1.0-3
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent change somewhere outside of your package (I suspect in
mariadb-server) the autopkgtest of your package started to fail. I
copied some of the output at the bottom of this report. Can you please
investigate the situation and fix it?
I'm wondering. Is this puppet-module installing mariadb "under water"?
In a way then the package (or at least the test) sort of depends on
mariadb. I understand you'd not want the test to depend on it because
then it is already installed, but you can at least make sure that your
test is run when mariadb gets updated, if you add a "dummy" test with
the dependency on it. Please refer to the autopkgtest specification [1]
under the hint-testsuite-triggers restriction.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1]
https://salsa.debian.org/ci-team/autopkgtest/-/raw/master/doc/README.package-tests.rst
https://ci.debian.net/data/autopkgtest/testing/amd64/p/puppet-module-puppetlabs-mysql/951/log.gz
autopkgtest [22:19:50]: test command1: [---
Package "puppet-module-puppetlabs-mysql"
is expected to be installed
Command "puppet apply --detailed-exitcodes --execute "include
mysql::client""
exit_status
is expected to eq 2
Package "mariadb-client"
is expected to be installed
Command "puppet apply --detailed-exitcodes --execute "include
mysql::server""
exit_status
is expected to eq 2
Package "mariadb-server"
is expected to be installed
Service "mysql"
is expected to be enabled (FAILED - 1)
is expected to be running
Failures:
1) Service "mysql" is expected to be enabled
Failure/Error: it { should be_enabled }
expected Service "mysql" to be enabled
/bin/sh -c ls\ /etc/rc3.d/\ \|\ grep\ --\ \'\^S..mysql\$\'\ \|\|\
grep\ \'\^\ \*start\ on\'\ /etc/init/mysql.conf
# ./spec/localhost/use_spec.rb:20:in `block (2 levels) in '
Finished in 14.27 seconds (files took 0.34764 seconds to load)
7 examples, 1 failure
Failed examples:
rspec ./spec/localhost/use_spec.rb:20 # Service "mysql" is expected to
be enabled
autopkgtest [22:20:05]: test command1: ---]
OpenPGP_signature
Description: OpenPGP digital signature
Bug#980258: ruby-rugged: tries to contact github.com during build (and fails)
Source: ruby-rugged Version: 1.1.0+ds-2 Severity: serious Tags: ftbfs Dear maintainer, I just noticed that ruby-rugged FTBFS on arm64 because it "failed to connect to github.com:". This is a violation of the Debian policy 4.9 [1]: """ For packages in the main archive, no required targets may attempt network access, except, via the loopback interface, to services on the build host that have been started by the build. """ Paul [1] https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules OpenPGP_signature Description: OpenPGP digital signature
Bug#957069: marked as done (cbmplugs: ftbfs with GCC-10)
Your message dated Sat, 16 Jan 2021 20:34:44 + with message-id and subject line Bug#957069: fixed in cbmplugs 1.2.2-1.1 has caused the Debian Bug report #957069, regarding cbmplugs: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957069 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cbmplugs Version: 1.2.2-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/cbmplugs_1.2.2-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] | ^~~~ In file included from /usr/include/gimp-2.0/libgimp/gimp.h:41, from cbmplugs.c:22: /usr/include/gimp-2.0/libgimp/gimpdrawable.h:52:16: note: declared here 52 | GimpDrawable * gimp_drawable_get(gint32 drawable_ID); |^ cbmplugs.c:798:2: warning: ‘gimp_pixel_rgn_init’ is deprecated: Use 'gimp_drawable_get_buffer' instead [-Wdeprecated-declarations] 798 | gimp_pixel_rgn_init(&pixel_rgn, drawable, 0, 0, width, height, | ^~~ In file included from /usr/include/gimp-2.0/libgimp/gimp.h:57, from cbmplugs.c:22: /usr/include/gimp-2.0/libgimp/gimppixelrgn.h:48:11: note: declared here 48 | void gimp_pixel_rgn_init (GimpPixelRgn *pr, | ^~~ cbmplugs.c:1110:2: warning: ‘gimp_pixel_rgn_set_rect’ is deprecated: Use 'gegl_buffer_set' instead [-Wdeprecated-declarations] 1110 | gimp_pixel_rgn_set_rect(&pixel_rgn, buf, 0, 0, width, height); | ^~~ In file included from /usr/include/gimp-2.0/libgimp/gimp.h:57, from cbmplugs.c:22: /usr/include/gimp-2.0/libgimp/gimppixelrgn.h:104:11: note: declared here 104 | void gimp_pixel_rgn_set_rect (GimpPixelRgn *pr, | ^~~ cbmplugs.c:1112:2: warning: ‘gimp_drawable_flush’ is deprecated: Use 'gegl_buffer_flush' instead [-Wdeprecated-declarations] 1112 | gimp_drawable_flush(drawable); | ^~~ In file included from /usr/include/gimp-2.0/libgimp/gimp.h:41, from cbmplugs.c:22: /usr/include/gimp-2.0/libgimp/gimpdrawable.h:56:16: note: declared here 56 | void gimp_drawable_flush (GimpDrawable *drawable); |^~~ cbmplugs.c: In function ‘gimp_to_bitmap’: cbmplugs.c:1367:2: warning: ‘gimp_drawable_get’ is deprecated: Use 'gimp_drawable_get_buffer' instead [-Wdeprecated-declarations] 1367 | drawable = gimp_drawable_get(drawable_ID); | ^~~~ In file included from /usr/include/gimp-2.0/libgimp/gimp.h:41, from cbmplugs.c:22: /usr/include/gimp-2.0/libgimp/gimpdrawable.h:52:16: note: declared here 52 | GimpDrawable * gimp_drawable_get(gint32 drawable_ID); |^ cbmplugs.c:1374:2: warning: ‘gimp_image_get_cmap’ is deprecated: Use 'gimp_image_get_colormap' instead [-Wdeprecated-declarations] 1374 | cmap = gimp_image_get_cmap(image_ID, &ncols); | ^~~~ In file included from /usr/include/gimp-2.0/libgimp/gimp.h:47, from cbmplugs.c:22: /usr/include/gimp-2.0/libgimp/gimpimage.h:49:16: note: declared here 49 | guchar * gimp_image_get_cmap(gint32 image_ID, |^~~ cbmplugs.c:1387:2: warning:
Bug#957000: marked as done (anypaper: ftbfs with GCC-10)
Your message dated Sat, 16 Jan 2021 21:03:42 + with message-id and subject line Bug#957000: fixed in anypaper 2.4-2.1 has caused the Debian Bug report #957000, regarding anypaper: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957000 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:anypaper Version: 2.4-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/anypaper_2.4-2_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] 218 | if (*std_err != NULL) | ^~ anypaper.c:237:17: warning: comparison between pointer and integer 237 |if (*std_out != NULL) | ^~ anypaper.c:242:17: warning: comparison between pointer and integer 242 |if (*std_err != NULL) | ^~ /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -o anypaper anypaper.o libanypaper.la -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lfontconfig -lfreetype -lglib-2.0 libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro -o anypaper anypaper.o ./.libs/libanypaper.a -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lfontconfig -lfreetype -lglib-2.0 /usr/bin/ld: ./.libs/libanypaper.a(anypaper_command.o):./anypaper/anypaper_command.h:53: multiple definition of `background_color'; anypaper.o:./anypaper/anypaper_command.h:53: first defined here /usr/bin/ld: ./.libs/libanypaper.a(anypaper_command.o):./anypaper/anypaper_command.h:48: multiple definition of `custom'; anypaper.o:./anypaper/anypaper_command.h:48: first defined here /usr/bin/ld: ./.libs/libanypaper.a(anypaper_command.o):./anypaper/anypaper_command.h:48: multiple definition of `scale'; anypaper.o:./anypaper/anypaper_command.h:48: first defined here /usr/bin/ld: ./.libs/libanypaper.a(anypaper_command.o):./anypaper/anypaper_command.h:48: multiple definition of `fullscreen'; anypaper.o:./anypaper/anypaper_command.h:48: first defined here /usr/bin/ld: ./.libs/libanypaper.a(anypaper_command.o):./anypaper/anypaper_command.h:48: multiple definition of `tile'; anypaper.o:./anypaper/anypaper_command.h:48: first defined here /usr/bin/ld: ./.libs/libanypaper.a(anypaper_command.o):./anypaper/anypaper_command.h:48: multiple definition of `maximize'; anypaper.o:./anypaper/anypaper_command.h:48: first defined here /usr/bin/ld: ./.libs/libanypaper.a(anypaper_command.o):./anypaper/anypaper_command.h:48: multiple definition of `normal'; anypaper.o:./anypaper/anypaper_command.h:48: first defined here /usr/bin/ld: ./.libs/libanypaper.a(anypaper_command.o):./anypaper/anypaper_command.h:53: multiple definition of `remaining_args'; anypaper.o:./anypaper/anypaper_command.h:53: first defined here /usr/bin/ld: ./.libs/libanypaper.a(anypaper_command.o):./anypaper/anypaper_command.h:51: multiple definition of `x_position'; anypaper.o:./anypaper/anypaper_command.h:51: first defined here /usr/bin/ld: ./.libs/libanypaper.a(anypaper_command.o):./anypaper/anypaper_command.h:51: multiple definition of `y_position'; anypaper.o:./anypaper/anypaper_command.h:51: f
Bug#980225: marked as done (lvm2-lockd: lvmlockd.service fails to start as of the latest update to 2.03.11-1 in sid)
Your message dated Sat, 16 Jan 2021 21:19:11 + with message-id and subject line Bug#980225: fixed in lvm2 2.03.11-2 has caused the Debian Bug report #980225, regarding lvm2-lockd: lvmlockd.service fails to start as of the latest update to 2.03.11-1 in sid to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 980225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980225 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lvm2-lockd Version: 2.03.11-1 Severity: grave Justification: renders package unusable Dear Maintainer, after the update of lvm2 packages to version 2.03.11-1 in sid, the lvmlockd.service fails to start and just hangs till systemctl times out and exits with an error. The previous version worked flawlessly on my laptop. Please let me know if there are any checks I can do to help nailing down the problem, and/or any relevant configuration details that I can provide. Thanks in advance, best regards Giacomo Mulas -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (401, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.4-jak (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to it_IT.UTF-8), LANGUAGE=it_IT,en_EN Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lvm2-lockd depends on: ii libc6 2.31-9 ii libdlm3 4.0.9-2 ii libsanlock-client1 3.8.2-1+b2 ii libselinux1 3.1-2+b2 ii libudev1247.2-4 ii lvm22.03.11-1 lvm2-lockd recommends no packages. lvm2-lockd suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: lvm2 Source-Version: 2.03.11-2 Done: Bastian Blank We believe that the bug you reported is fixed in the latest version of lvm2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 980...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank (supplier of updated lvm2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 16 Jan 2021 21:51:13 +0100 Source: lvm2 Architecture: source Version: 2.03.11-2 Distribution: unstable Urgency: medium Maintainer: Debian LVM Team Changed-By: Bastian Blank Closes: 980225 Changes: lvm2 (2.03.11-2) unstable; urgency=medium . * Make sure lvmlockd can use sd notify. (closes: #980225) Checksums-Sha1: da63902003930f3f8e37e3b9d5a5ccbbbe441f9e 2715 lvm2_2.03.11-2.dsc d2a8be7026a605f181404d3e4aea0b5f2326c415 32052 lvm2_2.03.11-2.debian.tar.xz e268b0996342c009044a6898f356ee4e8a9aa3a5 6503 lvm2_2.03.11-2_source.buildinfo Checksums-Sha256: 743be7ca961eb07282fc34e4e21388d43f0a38dade17d162d158e9150f94aeef 2715 lvm2_2.03.11-2.dsc 2cd2a0938c9fb3d63634add9ac17de3e8e0b981fe6b13210d7024c4ef457bdb6 32052 lvm2_2.03.11-2.debian.tar.xz cbc5b0690351becad6960985de47b564c9cdbbcf36e013dd8a4b63a6f98cc3d6 6503 lvm2_2.03.11-2_source.buildinfo Files: 1be97fadf063d3214120a3efeb5f6fec 2715 admin optional lvm2_2.03.11-2.dsc 04e1bca573c87499f736f8510f87c13a 32052 admin optional lvm2_2.03.11-2.debian.tar.xz 426b91daac09be9408edeee4be2dfbd7 6503 admin optional lvm2_2.03.11-2_source.buildinfo -BEGIN PGP SIGNATURE- iQFFBAEBCgAvFiEER3HMN63jdS1rqjxLbZOIhYpp/lEFAmADUecRHHdhbGRpQGRl Ymlhbi5vcmcACgkQbZOIhYpp/lGvgAgAm9c3ueM8dSDhkw3bT8itbTh5R3dhdpeX sPYLXfsp/6nqY3VCmKwaxDibiL/lsewqSU11UNKPdvkslRSPfVXnMoFPZ34DPKmi v/67RRI7LGGKIcuhnTll1q8XEblgEwSUG/yFjdzyddEoIDgXEk8zHmkQwpHNOBQg 8zwdLWWKd6rZC8eFVxlzrO3ZVqJsgxEc5T9l+qtvS/RWU6Bhgy6iWS59M5TNgdho 6UMFUQSSlEftGeBUYORVR70OKDxnEm+AUShRdcPtQvcWvZ2PRtRPl8mLMCMHMeL7 1o//A7lFux8TbybG4b0tQSy11lHhM1f4B4+LRvihRx14f9s1DvB3Kg== =0SB0 -END PGP SIGNATURE End Message ---
Bug#979174: node-express-generator: Incompatible with current node-commander and node-mkdirp
Control: tags -1 + bullseye Hi, On Sun, Jan 03, 2021 at 09:39:56PM +0100, Xavier Guimard wrote: > Package: node-express-generator > Version: 4.0.0-2 > Severity: grave > Tags: sid, ftbfs Tagging bugs only 'sid' and not the tag for testing usually doesn't give the correct result. Adding the bullseye tag as well. Did you add the ftbfs tag by mistake? I don't see an ftbfs anywhere. > Justification: renders package unusable > > node-express-generator isn't compatible with current node-commander, > neither node-mkdirp. As it has no reverse dependency, I suggest to > remove it from Debian If you want the package removed, you should probably file an FTP removal bug. Cheers, Ivo
Processed: Re: node-express-generator: Incompatible with current node-commander and node-mkdirp
Processing control commands: > tags -1 + bullseye Bug #979174 [node-express-generator] node-express-generator: Incompatible with current node-commander and node-mkdirp Added tag(s) bullseye. -- 979174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979174 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951948: Fixed upstream
This is due to improper use of setuptools_scm in docs/conf.py. This is fixed [1] in version 0.16.8, along with other build errors. Please consider packaging the new version. [1] https://github.com/pimutils/vdirsyncer/commit/b1214cd693d7a6c6693da3d070e8b9965a84a88e
Bug#966882: marked as done (buici-clock: FTBFS: res_y.cxx:149:10: fatal error: res_y.hxx: No such file or directory)
Your message dated Sat, 16 Jan 2021 22:33:46 + with message-id and subject line Bug#966882: fixed in buici-clock 0.4.9.4+nmu1 has caused the Debian Bug report #966882, regarding buici-clock: FTBFS: res_y.cxx:149:10: fatal error: res_y.hxx: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 966882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: buici-clock Version: 0.4.9.4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -c -g -O2 -o o/res_y.o res_y.cxx > res_y.cxx:149:10: fatal error: res_y.hxx: No such file or directory > 149 | #include "res_y.hxx" > | ^~~ > compilation terminated. > make[2]: *** [Makefile:91: o/res_y.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/08/02/buici-clock_0.4.9.4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: buici-clock Source-Version: 0.4.9.4+nmu1 Done: Sudip Mukherjee We believe that the bug you reported is fixed in the latest version of buici-clock, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sudip Mukherjee (supplier of updated buici-clock package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 14 Jan 2021 22:05:45 + Source: buici-clock Architecture: source Version: 0.4.9.4+nmu1 Distribution: unstable Urgency: medium Maintainer: Marc Singer Changed-By: Sudip Mukherjee Closes: 966882 Changes: buici-clock (0.4.9.4+nmu1) unstable; urgency=medium . * Non-maintainer upload. * Fix FTBFS. (Closes: #966882) - Remove rename and use res_y.hxx Checksums-Sha1: 80a1d33d04f6db014f88e181c0c92bb7f4b1b3c8 1500 buici-clock_0.4.9.4+nmu1.dsc b78001777fc9ebe577d4012278e7805af4c989ee 108220 buici-clock_0.4.9.4+nmu1.tar.xz 0e3503ee839ef46a8ea7b2c197d797c71a1d6db4 8753 buici-clock_0.4.9.4+nmu1_amd64.buildinfo Checksums-Sha256: b27fa8fb7d54bc747d5595aba2e88085ce1bfdfffd4d4685dc9b46edfaec5a60 1500 buici-clock_0.4.9.4+nmu1.dsc f274d9aeb359fbe820df94035cf24bf2a4f8560dc6242e7f6a05f145575f1a50 108220 buici-clock_0.4.9.4+nmu1.tar.xz 9da79a3d15ea53c04dab0fa5c736b14daaae9b4b6054f2d58376753dcf76a7ce 8753 buici-clock_0.4.9.4+nmu1_amd64.buildinfo Files: 2c4321b49a1454de5ede5021f18c6bdc 1500 x11 optional buici-clock_0.4.9.4+nmu1.dsc fc456ea22add722aab46256ab18de1a4 108220 x11 optional buici-clock_0.4.9.4+nmu1.tar.xz 3ed723d910457eca9b1b2cd899e99ef7 8753 x11 optional buici-clock_0.4.9.4+nmu1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuDQJkCg9jZvBlJrHR5mjUUbRKzUFAmAAwPIACgkQR5mjUUbR KzVGsxAAqaBCl/Q+WYj9B2GNMw75sPWxs+tWO4WPvgjwH6zElPc3kIy5cFTwRE2W MaFEM6anjzXURvqDibnI9v05cONsrT5FSeusEyIYL5ECGlX12jJ1YkIX6peFGVva 0ZAE04/XHkvo+7/V2XNy7/5Dgfw2cUZncFf/6O6gAueiWBHE2TH+j206yz0XeS62 GvGmmtdZfvbhvCX1lpOmUkTVfN9R+f93Yh0BBRlzvJ1jRIYfMcPJ+e4dRiQnB8RU ZS8mSue17PXIkqWUHXWoFkHlhz+DH3lxKOnRRqaKIKKPB1JhoTblEnJ65dFIOr74 CPCNaxia0wEWJr9da+5h8U/n6HIdyjarfpn9hBjkMEGtakHVxJrXWiYjjCulEuvu Om222rMCe6vmM+Mo3CYD71R8JsK87BqwU5KKIX+91SrN+3DS9g091XdZNXHgCFx8 mNTSEm/AQXtaQ1d+ZmWH4rd/fwlC6MkAwdkZVfz9yo5tHwR+7QxukpxuP7NbkxsT lgxqVLuK0BGuMYmL2ZsuA2T6eiPYQMSfq3S+TPi33o1FleXeU5wCg5i2vUsqKmea BYdZWlsnQceR8wTOSm6ukM+HdQpv9aIneCkJKTTrKuog0EKPadgJ2VpsnDnX9/Jz hMhHSugoJbZiptan1h8tTSBL5TddN04L1t8D/N7bTGS/SVCkHnM= =C1A4 -END PGP SIGNATURE End Message ---
Bug#980267: qdjango: FTBFS on buildds
package: src:qdjango version: 0.6.2-3 severity: serious tags: ftbfs Hi, The latest upload of qdjango to unstable fails on the buildds: https://buildd.debian.org/status/package.php?p=qdjango Cheers, Ivo
Processed: Re: libsml: ftbfs with GCC-10
Processing control commands: > tags -1 patch Bug #957478 [src:libsml] libsml: ftbfs with GCC-10 Added tag(s) patch. -- 957478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957478: libsml: ftbfs with GCC-10
Package: libsml
Version: 0.1.1+git20180125-1
Followup-For: Bug #957478
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
Control: tags -1 patch
Hi,
In Ubuntu, the attached patch was applied to achieve the following:
* d/p/gcc-10.patch: Cherrypick upstream Git commit to fix FTBFS with GCC 10.
Thanks for considering the patch.
Logan
diff -Nru libsml-0.1.1+git20180125/debian/patches/gcc-10.patch
libsml-0.1.1+git20180125/debian/patches/gcc-10.patch
--- libsml-0.1.1+git20180125/debian/patches/gcc-10.patch1969-12-31
19:00:00.0 -0500
+++ libsml-0.1.1+git20180125/debian/patches/gcc-10.patch2021-01-16
20:21:25.0 -0500
@@ -0,0 +1,200 @@
+From 0738cd50632eadb9cd2c21e07b70f984a9cf444b Mon Sep 17 00:00:00 2001
+From: r00t
+Date: Mon, 28 Dec 2020 01:03:43 +0100
+Subject: [PATCH] [test] fix building with -fno-common (gcc10 default),
+
+see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85678
+---
+ test/src/sml_boolean_test.c | 2 +-
+ test/src/sml_buffer_test.c | 2 +-
+ test/src/sml_file_test.c | 2 +-
+ test/src/sml_get_profile_pack_request_test.c | 2 +-
+ test/src/sml_list_test.c | 4 ++--
+ test/src/sml_message_test.c | 2 +-
+ test/src/sml_number_test.c | 2 +-
+ test/src/sml_octet_string_test.c | 2 +-
+ test/src/sml_open_request_test.c | 2 +-
+ test/src/sml_status_test.c | 2 +-
+ test/src/sml_time_test.c | 2 +-
+ test/src/sml_tree_test.c | 2 +-
+ test/src/sml_value_test.c| 2 +-
+ 13 files changed, 14 insertions(+), 14 deletions(-)
+
+diff --git a/test/src/sml_boolean_test.c b/test/src/sml_boolean_test.c
+index 90b5f3d..0fbebf1 100644
+--- a/test/src/sml_boolean_test.c
b/test/src/sml_boolean_test.c
+@@ -22,7 +22,7 @@
+
+ TEST_GROUP(sml_boolean);
+
+-sml_buffer *buf;
++static sml_buffer *buf;
+
+ TEST_SETUP(sml_boolean) {
+ buf = sml_buffer_init(512);
+diff --git a/test/src/sml_buffer_test.c b/test/src/sml_buffer_test.c
+index bf8e714..45eacc2 100644
+--- a/test/src/sml_buffer_test.c
b/test/src/sml_buffer_test.c
+@@ -22,7 +22,7 @@
+ TEST_GROUP(sml_buffer);
+
+ int buffer_len = 512;
+-sml_buffer *buf;
++static sml_buffer *buf;
+
+ TEST_SETUP(sml_buffer) {
+ buf = sml_buffer_init(buffer_len);
+diff --git a/test/src/sml_file_test.c b/test/src/sml_file_test.c
+index 1b1bb15..9ded16f 100644
+--- a/test/src/sml_file_test.c
b/test/src/sml_file_test.c
+@@ -22,7 +22,7 @@
+
+ TEST_GROUP(sml_file);
+
+-sml_buffer *buf;
++static sml_buffer *buf;
+
+ TEST_SETUP(sml_file) {
+ buf = sml_buffer_init(512);
+diff --git a/test/src/sml_get_profile_pack_request_test.c
b/test/src/sml_get_profile_pack_request_test.c
+index c03d6ab..44f1f07 100644
+--- a/test/src/sml_get_profile_pack_request_test.c
b/test/src/sml_get_profile_pack_request_test.c
+@@ -22,7 +22,7 @@
+
+ TEST_GROUP(sml_get_profile_pack_request);
+
+-sml_buffer *buf;
++static sml_buffer *buf;
+
+ TEST_SETUP(sml_get_profile_pack_request) {
+ buf = sml_buffer_init(512);
+diff --git a/test/src/sml_list_test.c b/test/src/sml_list_test.c
+index 9a5f583..56d6ed2 100644
+--- a/test/src/sml_list_test.c
b/test/src/sml_list_test.c
+@@ -22,7 +22,7 @@
+
+ TEST_GROUP(sml_list);
+
+-sml_buffer *buf;
++static sml_buffer *buf;
+
+ TEST_SETUP(sml_list) {
+ buf = sml_buffer_init(512);
+@@ -100,7 +100,7 @@ TEST_GROUP_RUNNER(sml_list) {
+
+ TEST_GROUP(sml_sequence);
+
+-sml_buffer *buf;
++static sml_buffer *buf;
+
+ TEST_SETUP(sml_sequence) {
+ buf = sml_buffer_init(512);
+diff --git a/test/src/sml_message_test.c b/test/src/sml_message_test.c
+index 7462435..3d4bb07 100644
+--- a/test/src/sml_message_test.c
b/test/src/sml_message_test.c
+@@ -22,7 +22,7 @@
+
+ TEST_GROUP(sml_message);
+
+-sml_buffer *buf;
++static sml_buffer *buf;
+
+ TEST_SETUP(sml_message) {
+ buf = sml_buffer_init(512);
+diff --git a/test/src/sml_number_test.c b/test/src/sml_number_test.c
+index 9a5eece..09c00ca 100644
+--- a/test/src/sml_number_test.c
b/test/src/sml_number_test.c
+@@ -23,7 +23,7 @@
+
+ TEST_GROUP(sml_number);
+
+-sml_buffer *buf;
++static sml_buffer *buf;
+
+ TEST_SETUP(sml_number) {
+ buf = sml_buffer_init(512);
+diff --git a/test/src/sml_octet_string_test.c
b/test/src/sml_octet_string_test.c
+index 2a47632..c37d219 100644
+--- a/test/src/sml_octet_string_test.c
b/test/src/sml_octet_string_test.c
+@@ -22,7 +22,7 @@
+
+ TEST_GROUP(sml_octet_string);
+
+-sml_buffer *buf;
++static sml_buffer *buf;
+
+ TEST_SETUP(sml_octet_string) {
+ buf = sml_buffer_init(512);
+diff --git a/test/src/sml_open_request_test.c
b/test/src/sml_open_request_test.c
+index 89beba5..23b917f 100644
+--- a/test/src/sml_open_request_test.c
b/test/src/sml_open_request_test.c
+@@ -22,7 +22,7 @@
+
+ TEST_GROUP(sml_open_request);
+
+-sml_buffer
Processed: Re: jamin: ftbfs with GCC-10
Processing control commands: > tags -1 patch Bug #957383 [src:jamin] jamin: ftbfs with GCC-10 Added tag(s) patch. -- 957383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957383 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957383: jamin: ftbfs with GCC-10
Package: jamin Version: 0.98.9~git20170111~199091~repack1-1 Followup-For: Bug #957383 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu hirsute ubuntu-patch Control: tags -1 patch Hi, In Ubuntu, the attached patch was applied to achieve the following: * d/p/gcc_10.patch: Fix FTBFS with GCC 10. Thanks for considering the patch. Logan diff -Nru jamin-0.98.9~git20170111~199091~repack1/debian/patches/gcc_10.patch jamin-0.98.9~git20170111~199091~repack1/debian/patches/gcc_10.patch --- jamin-0.98.9~git20170111~199091~repack1/debian/patches/gcc_10.patch 1969-12-31 19:00:00.0 -0500 +++ jamin-0.98.9~git20170111~199091~repack1/debian/patches/gcc_10.patch 2021-01-16 20:57:51.0 -0500 @@ -0,0 +1,21 @@ +--- a/src/hdeq.h b/src/hdeq.h +@@ -65,7 +65,7 @@ + int get_current_notebook1_page (); + + +-GtkNotebook *l_notebook1; ++extern GtkNotebook *l_notebook1; + + + #endif +--- a/src/callbacks.c b/src/callbacks.c +@@ -71,6 +71,7 @@ + static GtkWidget*scene_name_dialog, *about_dialog; + static GtkEntry *l_scene_name_entry; + static GdkColor l_main_color, l_eq_color, l_comp_color[XO_NBANDS], l_limiter_color; ++GtkNotebook *l_notebook1; + + + void diff -Nru jamin-0.98.9~git20170111~199091~repack1/debian/patches/series jamin-0.98.9~git20170111~199091~repack1/debian/patches/series --- jamin-0.98.9~git20170111~199091~repack1/debian/patches/series 2017-01-11 15:31:55.0 -0500 +++ jamin-0.98.9~git20170111~199091~repack1/debian/patches/series 2021-01-16 20:57:34.0 -0500 @@ -5,3 +5,4 @@ 1005_desktop_file.patch NEWS.patch fix_typos.patch +gcc_10.patch
Bug#980281: q2-dada2: autopkgtest failure: missing depends python3-biom-format
Package: q2-dada2 Version: 2020.11.1-1 Severity: serious Hi! Debci reports the following failure (source: https://ci.debian.net/packages/q/q2-dada2/testing/amd64/) ERRORS ___ ERROR collecting q2_dada2/tests/test_denoise.py ImportError while importing test module '/tmp/autopkgtest-lxc.nkzw0lkg/downtmp/autopkgtest_tmp/q2_dada2/tests/test_denoise.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: q2_dada2/__init__.py:9: in from ._denoise import denoise_single, denoise_paired, denoise_pyro q2_dada2/_denoise.py:14: in import biom E ModuleNotFoundError: No module named 'biom' That is, q2-dada2 tries to import biom but does not declare Depends: python3-biom-format. -- Juhani
