Bug#932498: iptables -L goes into uninteruptable sleep
Package: iptables Version: 1.8.2-4 Severity: critical Tags: a11y Justification: breaks the whole system -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages iptables depends on: ii libc6 2.28-10 ii libip4tc0 1.8.2-4 ii libip6tc0 1.8.2-4 ii libiptc0 1.8.2-4 ii libmnl0 1.0.4-2 ii libnetfilter-conntrack3 1.0.7-1 ii libnfnetlink0 1.0.1-3+b1 ii libnftnl11 1.1.2-2 ii libxtables12 1.8.2-4 Versions of packages iptables recommends: pn nftables Versions of packages iptables suggests: ii kmod 26-1 -- no debconf information Either Fail2Ban, or netfilter-persistent, or iptables itself causes this state. It also prevents the system from shutdown or reboot, only hard reset works.
Processed: bug 928893 is not forwarded
Processing commands for cont...@bugs.debian.org: > notforwarded 928893 Bug #928893 [libblockdev-crypto2] gnome-disk-utility: disk content permanently lost when changing LUKS password Unset Bug forwarded-to-address > thanks Stopping processing here. Please contact me if you need assistance. -- 928893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928893 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#928893: gnome-disk-utility: disk content permamently lost when changing LUKS password
Control: reassign -1 libblockdev-crypto2
Control: found -1 2.20-7
Control: fixed -1 2.22-1
Control: affects -1 gnome-disk-utility
Control: affects -1 udisks2
Control: tag -1 + patch
Hi,
it turns out this is caused by a bug in libblockdev, which is fixed in
sid already (although it seems like upstream applied the fix for
unrelated reasons and it's not clear whether they realized this bug
was a possibility).
The attached patch fixes it for me:
- current sid (libblockdev 2.22-1): unreproducible
- current sid with Buster's libblockdev 2.20-7: reproduced the bug
- current sid with Buster's libblockdev + the attached patch: unreproducible
I think we should get this into Buster (10.1, if not via stable-updates).
As explained in the changelog entry, this fixes the data loss problem
but it might still leave udisks2's LUKS2 passphrase changing broken in
some cases, although broken in a way that leaves the old passphrase
working, which is better than making the device totally unusable.
Guilhem (Cc'ed) and I are investigating this possible problems and
potential solutions.
Cheers,
--
intrigeri
diff --git a/debian/changelog b/debian/changelog
index c9bfefa..a5a8c2c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,29 @@
+libblockdev (2.20-7.1) unstable; urgency=medium
+
+ * Cherry-pick upstream fix: use existing cryptsetup API for atomically
+changing a keyslot passphrase, instead of deleting the old keyslot
+before adding the new one. This avoids data loss when attempting to
+change the passphrase of a LUKS2 device via udisks2, e.g. from GNOME
+Disks (Closes: #928893).
+
+Deleting a keyslot and then adding one is risky: if anything goes
+wrong before the new keyslot is successfully added, no usable keyslot
+is left and the device cannot be unlocked anymore. There's little
+chances this causes actual problems with LUKS1, but LUKS2 defaults to
+the memory-hard Argon2 key derivation algorithm, which is implemented
+in cryptsetup with the assumption that it runs as root with no MEMLOCK
+ulimit; this assumption is wrong when run by udisks2.service under
+LimitMEMLOCK=65536, which breaks adding the new keyslot, and makes us
+hit the problematic situation (user data loss) every time.
+
+With this change, changing a LUKS2 passphrase via udisks2 will still
+fail in some cases, until the MEMLOCK ulimit problem is solved in
+cryptsetup or workaround'ed in udisks2, which Guilhem Moulin and I are
+working on. But at least, if it fails, it will fail _atomically_ and
+the original passphrase will still work.
+
+ -- intrigeri Sat, 20 Jul 2019 01:01:29 +
+
libblockdev (2.20-7) unstable; urgency=medium
* Cherry-pick Use-512bit-keys-in-LUKS-by-default.patch:
diff --git a/debian/patches/series b/debian/patches/series
index 94d3e03..ddf2825 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
Use-512bit-keys-in-LUKS-by-default.patch
+use-existing-cryptsetup-api-for-changing.patch
diff --git a/debian/patches/use-existing-cryptsetup-api-for-changing.patch b/debian/patches/use-existing-cryptsetup-api-for-changing.patch
new file mode 100644
index 000..45b4fd4
--- /dev/null
+++ b/debian/patches/use-existing-cryptsetup-api-for-changing.patch
@@ -0,0 +1,84 @@
+From: Vojtech Trefny
+Date: Tue, 12 Mar 2019 09:28:05 +0100
+X-Dgit-Generated: 2.20-7.1 8590f51cdbabf22c2b9250c108cf11446e6e91c4
+Subject: Use existing cryptsetup API for changing keyslot passphrase
+
+Instead of manually removing the keyslot and adding new a one.
+Our old code also doesn't work in FIPS mode.
+
+---
+
+--- libblockdev-2.20.orig/src/plugins/crypto.c
libblockdev-2.20/src/plugins/crypto.c
+@@ -1359,8 +1359,6 @@ gboolean bd_crypto_luks_remove_key (cons
+ gboolean bd_crypto_luks_change_key_blob (const gchar *device, const guint8 *pass_data, gsize data_len, const guint8 *npass_data, gsize ndata_len, GError **error) {
+ struct crypt_device *cd = NULL;
+ gint ret = 0;
+-gchar *volume_key = NULL;
+-gsize vk_size = 0;
+ guint64 progress_id = 0;
+ gchar *msg = NULL;
+
+@@ -1385,41 +1383,21 @@ gboolean bd_crypto_luks_change_key_blob
+ return FALSE;
+ }
+
+-vk_size = crypt_get_volume_key_size(cd);
+-volume_key = (gchar *) g_malloc (vk_size);
+-
+-ret = crypt_volume_key_get (cd, CRYPT_ANY_SLOT, volume_key, _size, (char*) pass_data, data_len);
+-if (ret < 0) {
+-g_set_error (error, BD_CRYPTO_ERROR, BD_CRYPTO_ERROR_DEVICE,
+- "Failed to load device's volume key: %s", strerror_l(-ret, c_locale));
+-crypt_free (cd);
+-g_free (volume_key);
+-bd_utils_report_finished (progress_id, (*error)->message);
+-return FALSE;
+-}
+-
+-/* ret is the number of the slot with the given pass */
+-ret = crypt_keyslot_destroy (cd, ret);
+-if (ret != 0) {
+-g_set_error (error, BD_CRYPTO_ERROR, BD_CRYPTO_ERROR_REMOVE_KEY,
+-
Processed: Re: Bug#928893: gnome-disk-utility: disk content permamently lost when changing LUKS password
Processing control commands: > reassign -1 libblockdev-crypto2 Bug #928893 [gnome-disk-utility] gnome-disk-utility: disk content permanently lost when changing LUKS password Bug reassigned from package 'gnome-disk-utility' to 'libblockdev-crypto2'. No longer marked as found in versions gnome-disk-utility/3.30.2-3. Ignoring request to alter fixed versions of bug #928893 to the same values previously set > found -1 2.20-7 Bug #928893 [libblockdev-crypto2] gnome-disk-utility: disk content permanently lost when changing LUKS password Marked as found in versions libblockdev/2.20-7. > fixed -1 2.22-1 Bug #928893 [libblockdev-crypto2] gnome-disk-utility: disk content permanently lost when changing LUKS password Marked as fixed in versions libblockdev/2.22-1. > affects -1 gnome-disk-utility Bug #928893 [libblockdev-crypto2] gnome-disk-utility: disk content permanently lost when changing LUKS password Added indication that 928893 affects gnome-disk-utility > affects -1 udisks2 Bug #928893 [libblockdev-crypto2] gnome-disk-utility: disk content permanently lost when changing LUKS password Added indication that 928893 affects udisks2 > tag -1 + patch Bug #928893 [libblockdev-crypto2] gnome-disk-utility: disk content permanently lost when changing LUKS password Added tag(s) patch. -- 928893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928893 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909523: Intent to NMU (Re: Bug#909523: Default configuration is incompatible with a non-SELinux active LSM)
On Saturday, 20 July 2019 1:09:11 AM AEST intrigeri wrote: > Done (0.10.10-0.2). This was my first attempt at using dgit to NMU so > let's hope I did not bork it. > > I'm attaching the 3 commits I did on top of 0.10.10-0.1. Awesome, thank you. I've just realised that we had no _cachefilesd_ on Salsa so I've imported old repository and applied your patches on top: https://salsa.debian.org/debian/cachefilesd -- Best wishes, Dmitry Smirnov. --- A man who knows a subject thoroughly, a man so soaked in it that he eats it, sleeps it and dreams it - this man can always teach it with success, no matter how little he knows of technical pedagogy. -- H. L. Mencken signature.asc Description: This is a digitally signed message part.
Bug#915970: marked as done (asyncpg frequently FTBFS due to test timeouts)
Your message dated Sat, 20 Jul 2019 00:34:14 + with message-id and subject line Bug#915970: fixed in asyncpg 0.18.3-2 has caused the Debian Bug report #915970, regarding asyncpg frequently FTBFS due to test timeouts 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.) -- 915970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: asyncpg Version: 0.18.2-1 Severity: normal Tags: patch Dear Maintainer, The hppa architecture is slow by and some tests timeout. See: https://buildd.debian.org/status/fetch.php?pkg=asyncpg=hppa=0.18.2-1=1544292148=0 I had a successful build with the attached patch. Would you please increase the timeouts adjusted in the patch on hppa. Thanks, Dave Anglin -- System Information: Debian Release: buster/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: hppa (parisc64) Kernel: Linux 4.14.87+ (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- ./tests/test_introspection.py.save 2018-12-08 14:02:45.169356827 -0500 +++ ./tests/test_introspection.py 2018-12-08 14:03:03.019439757 -0500 @@ -12,7 +12,7 @@ from asyncpg import connection as apg_con -MAX_RUNTIME = 0.1 +MAX_RUNTIME = 0.25 class SlowIntrospectionConnection(apg_con.Connection): --- ./tests/test_pool.py.save 2018-12-08 13:31:16.720834556 -0500 +++ ./tests/test_pool.py2018-12-08 14:36:25.113217328 -0500 @@ -28,7 +28,7 @@ # Travis' macOS is _slow_. POOL_NOMINAL_TIMEOUT = 0.5 else: -POOL_NOMINAL_TIMEOUT = 0.1 +POOL_NOMINAL_TIMEOUT = 0.5 class SlowResetConnection(pg_connection.Connection): @@ -393,7 +393,7 @@ task = self.loop.create_task(worker()) # Let the worker() run. -await asyncio.sleep(0.1, loop=self.loop) +await asyncio.sleep(0.4, loop=self.loop) # Cancel the worker. task.cancel() # Wait to make sure the cleanup has completed. --- End Message --- --- Begin Message --- Source: asyncpg Source-Version: 0.18.3-2 We believe that the bug you reported is fixed in the latest version of asyncpg, 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 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Piotr Ożarowski (supplier of updated asyncpg 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, 20 Jul 2019 02:02:02 +0200 Source: asyncpg Architecture: source Version: 0.18.3-2 Distribution: unstable Urgency: medium Maintainer: Piotr Ożarowski Changed-By: Piotr Ożarowski Closes: 915970 Changes: asyncpg (0.18.3-2) unstable; urgency=medium . [ William Grzybowski ] * d/p/0002: add patch for FTBFS due to test timeouts. (Closes: #915970) . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat. * Bump Standards-Version to 4.4.0. Checksums-Sha1: 24683bf56ff41212abce96168659826eab53afc2 2076 asyncpg_0.18.3-2.dsc 4159b6999835c6032eb2861b58581e691ceeec0f 7124 asyncpg_0.18.3-2.debian.tar.xz a3eb72c97c42fd828fee58a451cc641e66ed771a 8101 asyncpg_0.18.3-2_amd64.buildinfo Checksums-Sha256: 795aaf3500916d161c303d01e8afe9a20c144325183814cb0613ce7b31c406c8 2076 asyncpg_0.18.3-2.dsc 4b368b8d250cd82ac4ba4701f355e1e85af5740252a16f77cda54e1b08d545f6 7124 asyncpg_0.18.3-2.debian.tar.xz 36a0abb14d6e65752c68e21d3350fe163f2e92f0b47c4a7486fcb3323f42ffa7 8101 asyncpg_0.18.3-2_amd64.buildinfo Files: 0a79c5d81e5ab24ca3c1e682093b9995 2076 python optional asyncpg_0.18.3-2.dsc 7e1898038efc5f72b5a0e0701a758d41 7124 python optional asyncpg_0.18.3-2.debian.tar.xz a4bba0930e1b77681e757e4d0f354d1f 8101 python optional asyncpg_0.18.3-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEHS+omFjar2IXhi33rvbxoqdFdkUFAl0yXEkACgkQrvbxoqdF dkV1OxAArFZwbd7M4n+bzItgSPZfVav7CHhPhiAULO3skI/Mcv0cn3NoAyXwaM8E /pO9lvxVtLbnzyRQWdOuxq8dnqcP67hrl+dwp2hDfYvlROd6dht327rKecUoBxZV kaf5ZBxvhiRCuJM4hcRPTJM4bCxjduSM7EvTRefjPWFHCdZMjobkP5icosFocXBL
Bug#926712: marked as done (evolution-ews: CVE-2019-3890)
Your message dated Fri, 19 Jul 2019 22:22:22 + with message-id and subject line Bug#926712: fixed in evolution-ews 3.30.5-1.1 has caused the Debian Bug report #926712, regarding evolution-ews: CVE-2019-3890 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.) -- 926712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926712 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: evolution-ews Version: 3.30.5-1 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for evolution-ews. CVE-2019-3890[0]: No description was found (try on a search engine) 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-2019-3890 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3890 https://gitlab.gnome.org/GNOME/evolution-ews/issues/27 https://gitlab.gnome.org/GNOME/evolution-ews/issues/36 https://bugzilla.redhat.com/show_bug.cgi?id=1678313 Note: depends on evolution-data-server patch Cheers! Sylvain Beucler / Debian LTS --- End Message --- --- Begin Message --- Source: evolution-ews Source-Version: 3.30.5-1.1 We believe that the bug you reported is fixed in the latest version of evolution-ews, 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 926...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luca Boccassi (supplier of updated evolution-ews package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 02 Apr 2019 17:56:27 +0100 Source: evolution-ews Architecture: source Version: 3.30.5-1.1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Luca Boccassi Closes: 926249 926712 Changes: evolution-ews (3.30.5-1.1) unstable; urgency=medium . * Non-maintainer upload. * Backport patch to fix Office365 with OAuth2 (Closes: #926249) * Backport patch to fix CVE-2019-3890 - SSL certificates not being validated before use. Bump dependency on libedataserver1.2-dev to >= 3.30.5-1.1~ as the fix requires a change in that library. (Closes: #926712) Checksums-Sha1: 5bcc3b4c8f502eaa7aa3d695bff0523aec237d4d 2169 evolution-ews_3.30.5-1.1.dsc 1dbed5d69f7e3a8591901fee367bde2d42eb562e 11952 evolution-ews_3.30.5-1.1.debian.tar.xz 4d510b851bd69786af256e99bdf9ea84c5e1dfcd 22791 evolution-ews_3.30.5-1.1_source.buildinfo Checksums-Sha256: 98900771ddd588f0f9f232e8c8e32401d0907cef31f53e3a3df94746964c9d77 2169 evolution-ews_3.30.5-1.1.dsc 098e74dd97e6a139aa38bdd3808ed374a846077ca504b1b49350a91c95db7dbe 11952 evolution-ews_3.30.5-1.1.debian.tar.xz 19ac233de8588fc8a9653d7cd7de2c0926d748952d6c72f625a5fb69c5e874db 22791 evolution-ews_3.30.5-1.1_source.buildinfo Files: bc47a8dd124f381a20967a0c395eedf6 2169 gnome optional evolution-ews_3.30.5-1.1.dsc f58f85e765dcdd789a0217dd304090d2 11952 gnome optional evolution-ews_3.30.5-1.1.debian.tar.xz 435ee37a9d5c2a5196b660f04113b01d 22791 gnome optional evolution-ews_3.30.5-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQFFBAEBCgAvFiEE6g0RLAGYhL9yp9G8SylmgFB4UWIFAl0o+RIRHGJsdWNhQGRl Ymlhbi5vcmcACgkQSylmgFB4UWKdwwf+MbEVMivphiQACFxxu1N+/MA6eBCS+IRP /Y/O9WcI7V7nbYLkjLGmjDe+LxCNIVwONwQNkQTAIG+2k6aPXiJO1US3t181AH7T /6BurG6NSR8etwNNwjc/oCgHGqxTwZyAn8gV2pcsFgwr+mIeeXfzmvvDVk2oY1Xd KhoLZyQ2nhoZmjiBMPHZ239UdmtmMkslowVfHf1inftQzQX/yQBv+n/CeexpnM1X kllY7r3i0qBIzKo4awoqE9ZRT6uuWBTN+pYZnf4gEB+DxzE5YAwK/2NSGz4OaULN IJrCOBMfqNlcMl7EYRK6RMnX/gtipxHrmgf+hH30rPJw7WQyg7yC1w== =hoYm -END PGP SIGNATURE End Message ---
Bug#915970: marked as pending in asyncpg
Control: tag -1 pending Hello, Bug #915970 in asyncpg reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/asyncpg/commit/36fe2479df698d80282d4c2e93dd632577ac9bc0 d/p/0002: add patch for FTBFS due to test timeouts. (Closes: #915970) (this message was generated automatically) -- Greetings https://bugs.debian.org/915970
Processed: Bug#915970 marked as pending in asyncpg
Processing control commands: > tag -1 pending Bug #915970 [src:asyncpg] asyncpg frequently FTBFS due to test timeouts Added tag(s) pending. -- 915970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#932282: marked as done (libnet-pcap-perl: FTBFS: error: redefinition of ‘struct pcap_rmtauth’)
Your message dated Fri, 19 Jul 2019 20:47:01 +
with message-id
and subject line Bug#932282: fixed in libnet-pcap-perl 0.18-3
has caused the Debian Bug report #932282,
regarding libnet-pcap-perl: FTBFS: error: redefinition of ‘struct pcap_rmtauth’
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.)
--
932282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnet-pcap-perl
Version: 0.18-2
Severity: serious
Tags: ftbfs sid bullseye
X-Debbugs-Cc: libp...@packages.debian.org
This package fails to build from source on current sid/amd64.
Presumably this regressed with libpcap 1.9.0-2 so copying
the maintainer in case it's an oversight.
>From the build log:
x86_64-linux-gnu-gcc -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -Wall -Wwrite-strings -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION=\"0.18\"
-DXS_VERSION=\"0.18\" -fPIC "-I/usr/lib/x86_64-linux-gnu/perl/5.28/CORE"
-DHAVE_BLANK -DHAVE_PCAP_LIB_VERSION -DHAVE_PCAP_BREAKLOOP
-DHAVE_PCAP_COMPILE_NOPCAP -DHAVE_PCAP_DATALINK_NAME_TO_VAL
-DHAVE_PCAP_DATALINK_VAL_TO_DESCRIPTION -DHAVE_PCAP_DATALINK_VAL_TO_NAME
-DHAVE_PCAP_DUMP_FILE -DHAVE_PCAP_DUMP_FLUSH -DHAVE_PCAP_FINDALLDEVS
-DHAVE_PCAP_GETNONBLOCK -DHAVE_PCAP_GET_SELECTABLE_FD -DHAVE_PCAP_LIB_VERSION
-DHAVE_PCAP_NEXT_EX -DHAVE_PCAP_OFFLINE_FILTER -DHAVE_PCAP_OPEN_DEAD
-DHAVE_PCAP_SENDPACKET -DHAVE_PCAP_SETNONBLOCK -DHAVE_PCAP_SET_DATALINK Pcap.c
In file included from Pcap.xs:43:
stubs.inc:187:2: warning: #warning "the function pcap_list_datalinks() is not
available" [-Wcpp]
#warning "the function pcap_list_datalinks() is not available"
^~~
stubs.inc:322:2: warning: #warning "the function pcap_createsrcstr() is not
available" [-Wcpp]
#warning "the function pcap_createsrcstr() is not available"
^~~
stubs.inc:337:2: warning: #warning "the function pcap_parsesrcstr() is not
available" [-Wcpp]
#warning "the function pcap_parsesrcstr() is not available"
^~~
stubs.inc:352:2: warning: #warning "the function pcap_open() is not
available" [-Wcpp]
#warning "the function pcap_open() is not available"
^~~
stubs.inc:357:8: error: redefinition of ‘struct pcap_rmtauth’
struct pcap_rmtauth {
^~~~
In file included from /usr/include/pcap.h:43,
from Pcap.xs:32:
/usr/include/pcap/pcap.h:788:8: note: originally defined here
struct pcap_rmtauth
^~~~
In file included from Pcap.xs:43:
stubs.inc:363:10: error: conflicting types for ‘pcap_open’
pcap_t * pcap_open(const char *source, int snaplen, int flags, int
read_timeout, struct pcap_rmtauth *auth, char *err);
^
In file included from /usr/include/pcap.h:43,
from Pcap.xs:32:
/usr/include/pcap/pcap.h:835:18: note: previous declaration of ‘pcap_open’
was here
PCAP_API pcap_t *pcap_open(const char *source, int snaplen, int flags,
^
--
Niko Tyni nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libnet-pcap-perl
Source-Version: 0.18-3
We believe that the bug you reported is fixed in the latest version of
libnet-pcap-perl, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 932...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gregor herrmann (supplier of updated libnet-pcap-perl
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 19 Jul 2019 16:53:15 -0300
Source: libnet-pcap-perl
Architecture: source
Version: 0.18-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group
Changed-By: gregor herrmann
Closes: 932282
Changes:
libnet-pcap-perl (0.18-3) unstable; urgency=medium
.
[ Alex Muntada ]
* Remove inactive pkg-perl members from Uploaders.
.
[ Salvatore Bonaccorso ]
* Update Vcs-* headers for switch to salsa.debian.org
.
[ Xavier Guimard ]
* Email
Bug#932170: marked as done (bird2: FTBFS (dh_installinit: --name=bird option specified, but init script not found))
Your message dated Fri, 19 Jul 2019 20:45:21 +
with message-id
and subject line Bug#932073: fixed in debhelper 12.2.3
has caused the Debian Bug report #932073,
regarding bird2: FTBFS (dh_installinit: --name=bird option specified, but init
script not found)
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.)
--
932073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bird2
Version: 2.0.4-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in sid but it failed:
[...]
debian/rules build-indep
dh build-indep
dh_update_autotools_config -i
dh_autoreconf -i
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -g -O2 -fno-strict-aliasing
-fno-strict-overflow -fPIC" LDFLAGS="-Wl,-z,relro -Wl,-z,now -g -O2
-fno-strict-aliasing -fno-strict-overflow -fPIC -Wl,-z,defs -Wl,--as-needed"
dh_auto_configure -- --prefix=/usr --sysconfdir=/etc/bird
--mandir=\${prefix}/share/man --infodir=\${prefix}/share/info
--localstatedir=/var --runstatedir=/run/bird --docdir=\${prefix}/share/bird2
--enable-client --with-protocols=all
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu
--runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking
--prefix=/usr --sysconfdir=/etc/bird --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --localstatedir=/var --runstatedir=/run/bird
--docdir=\${prefix}/share/bird2 --enable-client --with-protocols=all
configure: WARNING: unrecognized options: --disable-silent-rules,
--disable-maintainer-mode, --disable-dependency-tracking
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
[... snipped ...]
[61] [62] [63] [64] [65] [66] [67] [68] [69] [70]
Chapter 7.
[71] (obj/doc//bird.aux) )
(see the transcript file for additional information)
Output written on obj/doc//bird.pdf (71 pages, 393856 bytes).
Transcript written on obj/doc//bird.log.
rm obj/doc/bird.tex obj/doc/prog.tex obj/doc/bird.sgml
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
dh_auto_test -i
make -j1 test VERBOSE=1
make[1]: Entering directory '/<>'
/bin/sh: 1: git: not found
rm -f obj/filter/tree_test.ok obj/filter/filter_test.ok obj/filter/trie_test.ok
obj/lib/heap_test.ok obj/lib/buffer_test.ok obj/lib/event_test.ok
obj/lib/flowspec_test.ok obj/lib/bitops_test.ok obj/lib/patmatch_test.ok
obj/lib/fletcher16_test.ok obj/lib/slist_test.ok obj/lib/checksum_test.ok
obj/lib/lists_test.ok obj/lib/mac_test.ok obj/lib/ip_test.ok
obj/lib/hash_test.ok obj/lib/printf_test.ok obj/nest/a-set_test.ok
obj/nest/a-path_test.ok
gcc -Iobj -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -g -O2 -fno-strict-aliasing -fno-strict-overflow -fPIC
-pthread -MMD -MP -o obj/filter/tree_test.o -c filter/tree_test.c
gcc -Iobj -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -g -O2 -fno-strict-aliasing -fno-strict-overflow -fPIC
-pthread -MMD -MP -o obj/test/birdtest.o -c test/birdtest.c
gcc -Iobj -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -g -O2 -fno-strict-aliasing -fno-strict-overflow -fPIC
-pthread -MMD -MP -o obj/test/bt-utils.o -c test/bt-utils.c
gcc -Wl,-z,relro -Wl,-z,now -g -O2 -fno-strict-aliasing -fno-strict-overflow
-fPIC -Wl,-z,defs -Wl,--as-needed -pthread -o obj/filter/tree_test
obj/filter/tree_test.o obj/conf/cf-parse.tab.o obj/conf/cf-lex.o
obj/conf/conf.o obj/filter/filter.o obj/filter/f-util.o obj/filter/tree.o
obj/filter/trie.o obj/lib/bitops.o obj/lib/checksum.o obj/lib/event.o
obj/lib/flowspec.o obj/lib/idm.o obj/lib/ip.o obj/lib/lists.o obj/lib/mac.o
obj/lib/md5.o obj/lib/mempool.o obj/lib/net.o obj/lib/patmatch.o
obj/lib/printf.o obj/lib/resource.o obj/lib/sha1.o obj/lib/sha256.o
obj/lib/sha512.o obj/lib/slab.o obj/lib/slists.o obj/lib/tbf.o
Bug#932073: marked as done (dh_installinit fails with "--name=foo option specified, but init script not found")
Your message dated Fri, 19 Jul 2019 20:45:21 + with message-id and subject line Bug#932073: fixed in debhelper 12.2.3 has caused the Debian Bug report #932073, regarding dh_installinit fails with "--name=foo option specified, but init script not found" 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.) -- 932073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932073 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debhelper Version: 12.2 Severity: serious Tags: ftbfs Control: affects -1 + src:openssh src:util-linux User: helm...@debian.org Usertags: rebootstrap debhelper 12.2 fixes #462389 and makes dh_installinit fail when the --name'd init script does not exist. This behaviour change makes at least openssh and util-linux FTBFS. These are two high popcon example packages. I expect more. It is unclear to me whether it can be fixed in debhelper at all. Yet I am filing the bug to have something recorded. If you determine that this should be fixed in the individual packages, please clone and reassign. Helmut --- End Message --- --- Begin Message --- Source: debhelper Source-Version: 12.2.3 We believe that the bug you reported is fixed in the latest version of debhelper, 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 932...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Niels Thykier (supplier of updated debhelper package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 19 Jul 2019 19:18:03 + Source: debhelper Architecture: source Version: 12.2.3 Distribution: unstable Urgency: medium Maintainer: Debhelper Maintainers Changed-By: Niels Thykier Closes: 932073 932262 Changes: debhelper (12.2.3) unstable; urgency=medium . * dh_installinit: Revert "Fail with an error if --name is given but there is no matching init script.". (Closes: #932073, Reopens: #462389) * Dh_Getopt.pm: Produce a better error message when -p is ignored in an architecture constrained override (e.g. during an architecture specific build and the -p argument refers to an arch:all package). Thanks to Helmut Grohne for reporting the issue. (Closes: #932262) Checksums-Sha1: 902ec533af0cb42ba595b2b32000495bfdf9787d 1714 debhelper_12.2.3.dsc 456a7fc7cb7ca584c666170c1410c50d55870e53 492468 debhelper_12.2.3.tar.xz d4553001881abddaf52a4a0c3e11b1a5515c4ef8 4535 debhelper_12.2.3_source.buildinfo Checksums-Sha256: a35d8d45097478325976207d2ba71d85bacc3d289f01d1880f7b695f5ba916f1 1714 debhelper_12.2.3.dsc 4c279d7ad09b843ca29e45d5134197e700814c95e46f5c45673790d77be6eaa1 492468 debhelper_12.2.3.tar.xz deaab4cd92b7875da85443f4302ce2897795d3f60785aabca0ae08cbdd74de25 4535 debhelper_12.2.3_source.buildinfo Files: 691147822125c3c57bfc7508c77a8d72 1714 devel optional debhelper_12.2.3.dsc 64a18f45afe1f621cd6fb5a01bb9c89e 492468 devel optional debhelper_12.2.3.tar.xz 8b0bf295be5fbda023e92807ef7e3f1e 4535 devel optional debhelper_12.2.3_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEE8f9dDX4ALfD+VfsMplt42+Z8eqwFAl0yGWQSHG5pZWxzQHRo eWtpZXIubmV0AAoJEKZbeNvmfHqs8WwP/3DKbtjsE0c4zDpCC6p6XGivW2A1BgLe Wa25UIukPr2g8TSj3eBI0077ZkNFNnhOWYt6OnOvUOsygqXc6qaxkfRRM5o3MMU+ m9A/I90XEgaN7/Pjr9Z41/SFP8VWYuu6qKirZqy73tUq30tmXOnidmaL3G83R+oD DULjfSC8RlyMQXIlo+OS7XCPAt2O/uV84ds6A6oA/c7tIjGVVQUy6MoITulv7eEm X6sUXA//4WSbnxU7nS1UdJQ21EL8ifRAIVcpSPuk0LbuwCy1Ea23uHtZXKVqLcDG KOCGVr+vJW52eizaWIQa47MAybA8Yd6pKBwN9pOMatdhzev4ChPbY7kVBLwThHdE tXOX6E9rWo4lvdBKlXDLuHgQlsNOYM+DbOX8KTZO394xdWikQk7Lf3rBFPmvyyHy KK5mmYkZ1OUDtZpOBWrMmfFUwZcnUDaq9CLu2lbytqt/Hd1P44w+QK+DKQsza6Us QzYw3EIbCk1c1vNQqgpnCsZ/IWim4FfuFrbqV9ErROy2gbeUJ8RNiNj5NgJkUxmT +cD3wOWFSFXUFxAl/qRuc689SPsduQhIz3TKGynvMOug7SSc4wn1mlQjshs0Dvug Xbc8cAzasvX9fK3i+EO75YD3iJYjJCtuhxhFiDBahAsEqGc6gGoKm2QnVj55lLUM 2UbUCBmNFAfK =DW+C -END PGP SIGNATURE End Message ---
Processed: Re: Bug#912140: libreoffice-base,libreoffice-common: trying to overwrite '/usr/lib/libreoffice/share/basic/dialog.xlc', which is also in package libreoffice-{base,common} 1:5.2.7-1+deb9u3
Processing commands for cont...@bugs.debian.org:
> close 912140 1:6.2.0~rc1-1
Bug #912140 [libreoffice-base,libreoffice-common]
libreoffice-base,libreoffice-common: trying to overwrite
'/usr/lib/libreoffice/share/basic/dialog.xlc', which is also in package
libreoffice-{base,common} 1:5.2.7-1+deb9u3
Marked as fixed in versions libreoffice/1:6.2.0~rc1-1.
Bug #912140 [libreoffice-base,libreoffice-common]
libreoffice-base,libreoffice-common: trying to overwrite
'/usr/lib/libreoffice/share/basic/dialog.xlc', which is also in package
libreoffice-{base,common} 1:5.2.7-1+deb9u3
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
912140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912140
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#912140: libreoffice-base,libreoffice-common: trying to overwrite '/usr/lib/libreoffice/share/basic/dialog.xlc', which is also in package libreoffice-{base,common} 1:5.2.7-1+deb9u3
close 912140 1:6.2.0~rc1-1
thanks
Hi,
On Fri, Jul 19, 2019 at 09:51:40PM +0200, Axel Beckert wrote:
> Rene Engelhard wrote:
> > On Sun, Nov 18, 2018 at 07:11:03PM +0100, Rene Engelhard wrote:
> > > But so we can remove --package $DPKG_MAINTSCRIPT_PACKAGE without a risk
> > > anyway:
> > > dpkg | 1.16.18 | oldoldstable | source, amd64, armel,
> > > armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc,
> > > s390, s390x, sparc
> > > (or at least it wouldn't be worse than before.)
> >
> > Done for in git (for sid, whevever this gets uploaded):
> > https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/commit/45af0362e3471c52783a0a6a4b5b384a32d013ce
>
> In the meanwhile there has been an upload to Debian Unstable after the
> Buster release, but this bug report hasn't been closed by it. Was it
one? gazillions since this bug was reported. Even various since
libreoffice (1:6.2.0~rc1-1) experimental; urgency=medium
* New upstream release candidate
- show partial signatures even if cert validation fails
(CERT-Bund#2018100828000257)
* debian/patches/aarch64-temporarily-disable-testgetCaughtException.diff:
as name says; the test is new in 6.2, never worked on arm64 (so no
regression) and the other, bigger tests (junit, uicheck) work fine.
* debian/patches/patches/fix-build-with-poppler-0.71.diff: one more patch
for poppler 0.71 (from master) (closes: #915726)
* debian/libreoffice-base.{postrm,preinst}.in: remove manual
--package $DPKG_MAINTSCRIPT_PACKAGE, since dpkg-divert defaults to it
since 1.16.0 anyway if not specified (see #912140).
* debian/control.in: update -core versioned Breaks: to -kde5, not -kde, thanks
Julien Cristau
* debian/libreoffice-mysql-connector.maintscript: add, thanks Andreas Beckmann
(closes: #915019)
* debian/rules:
- remove LD_LIBRARY_PATH setting for dh_shlibdeps and use (more) -l's
- fix running the odk/build-examples* tests on _all builds
- disable gdrive stuff. chromium isn't in buster anymore and gdrive didn't
work with chromiums id/secret anyway) (closes: #909152)
* merge from Ubuntu:
[ Evangelos Foutras ]
- poppler-fix-build-0-70.patch: fix build failure with poppler >= 0.70
-- Rene Engelhard Thu, 20 Dec 2018 06:41:55 +
> just a forgotten "Closes:" or was the commit not included?
Obviously changelog reading helps. Reading the bug to the end, too
The whole thing is included but since it's not sure but a needed fix anyway...
And this bug was tagged help since 8 months with no comment or any offer
for anything, so it can't be that important. And it is a upgrade to
inside now oldstable.
And since it it marked as affecting stretch only it is irrelevant for anything
else and also appears so...
> P.S.: I got mail from someone who ran into the exactly same issue.
> Interestingly it was on the same device model, so while there seems
> definitely some quoting missing, this issue so far only showed up
> twice and both times on Gemini PDA running Debian. Which gives more
> ground for the suspicion that one of the images for Debian on the
> Gemini PDA has a broken diversions state file.
Then they need to fix their broken stuff and this bug closed. (and
actually never have been opened.)
I am ignoring this "bug" for all matters. If you say it can be closed,
fine :-)
Regards,
Rene
Bug#932282: marked as pending in libnet-pcap-perl
Control: tag -1 pending Hello, Bug #932282 in libnet-pcap-perl 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/perl-team/modules/packages/libnet-pcap-perl/commit/1721a18fe44bb913fc3c5062a593e05c1d54170c Add patch from Fedora for libpcap 1.9.0 compatibility. Closes: #932282 (this message was generated automatically) -- Greetings https://bugs.debian.org/932282
Processed: Bug#932282 marked as pending in libnet-pcap-perl
Processing control commands: > tag -1 pending Bug #932282 [src:libnet-pcap-perl] libnet-pcap-perl: FTBFS: error: redefinition of ‘struct pcap_rmtauth’ Added tag(s) pending. -- 932282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932282 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912140: libreoffice-base,libreoffice-common: trying to overwrite '/usr/lib/libreoffice/share/basic/dialog.xlc', which is also in package libreoffice-{base,common} 1:5.2.7-1+deb9u3
Hi Rene, Rene Engelhard wrote: > On Sun, Nov 18, 2018 at 07:11:03PM +0100, Rene Engelhard wrote: > > But so we can remove --package $DPKG_MAINTSCRIPT_PACKAGE without a risk > > anyway: > > dpkg | 1.16.18 | oldoldstable | source, amd64, armel, > > armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, > > s390, s390x, sparc > > (or at least it wouldn't be worse than before.) > > Done for in git (for sid, whevever this gets uploaded): > https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/commit/45af0362e3471c52783a0a6a4b5b384a32d013ce In the meanwhile there has been an upload to Debian Unstable after the Buster release, but this bug report hasn't been closed by it. Was it just a forgotten "Closes:" or was the commit not included? P.S.: I got mail from someone who ran into the exactly same issue. Interestingly it was on the same device model, so while there seems definitely some quoting missing, this issue so far only showed up twice and both times on Gemini PDA running Debian. Which gives more ground for the suspicion that one of the images for Debian on the Gemini PDA has a broken diversions state file. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#932073: closed by Niels Thykier (Bug#932073: fixed in debhelper 12.2.1)
Helmut Grohne: > Control: reopen -1 > Control: affects -1 + src:dropbear > > On Tue, Jul 16, 2019 at 08:42:09PM +, Debian Bug Tracking System wrote: >>* dh_installinit: Fix regression where dh_installinit bailed >> out on --name if only one of the acted on packages had an >> init script file. Thanks to Helmut Grohne for reporting >> the issue. (Closes: #932073) > > The bug is partially fixed. A full build of openssh and dropbear now > works. At least the following situation (dropbar) is still broken: > > The init script lives in an arch-all package, you pass the relevant > --name and you perform an arch-only build. Here is a cross build log, > but it fully reproduces natively: > > http://crossqa.debian.net/build/dropbear_2019.78-1_mips_20190717050430.log > > I'm also confused by the following message: > > dh_link: No packages to build. Architecture mismatch: amd64, want: all any > > It happens both during native and during cross builds of dropbear. I > would have assumed that "amd64" and "mips" match the "any" part of "all > any". I'd appreciate if someone could enlighten me about this aspect. > > Helmut > Thanks reopening the bug. I have considered it for a while and I think the correct answer is to take a step back and consider whether this is truly the best approach (e.g. Guillem filed #932152 as an alternative that completely replaces --name and the related issues). Accordingly, I will revert the change and reopen #462389. For reference, I am aware of at least 3 suggested changes/patches related to this bug after Helmut reopened it. (Those are Dmitry's follow plus two independent merge requests on salsa). Thanks, ~Niels
Bug#931851: marked as done (pysolfc: pythonfc fails to start since python upgrades, new version with fix available upstream)
Your message dated Fri, 19 Jul 2019 18:20:27 + with message-id and subject line Bug#931851: fixed in pysolfc 2.6.4-1 has caused the Debian Bug report #931851, regarding pysolfc: pythonfc fails to start since python upgrades, new version with fix available upstream 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.) -- 931851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pysolfc Version: 2.0-4 Severity: grave Justification: renders package unusable -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (990, 'testing'), (150, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pysolfc depends on: ii python2.7.16-1 ii python-configobj 5.0.6-3 ii python-pygame 1.9.4.post1+dfsg-3 ii python-tk 2.7.16-2 Versions of packages pysolfc recommends: ii python-pil.imagetk [python-imaging-tk] 6.1.0-1 pn tk-tile Versions of packages pysolfc suggests: pn freecell-solver-bin pn pysolfc-cardsets -- no debconf information when started from the command line, I see python throw the following error: Traceback (most recent call last): File "/usr/games/pysolfc", line 32, in sys.exit(main(sys.argv)) File "/usr/share/games/pysolfc/pysollib/main.py", line 359, in main r = pysol_init(app, args) File "/usr/share/games/pysolfc/pysollib/main.py", line 339, in pysol_init if not app.loadCardset(cardset, progress=progress, update=1): File "/usr/share/games/pysolfc/pysollib/app.py", line 872, in loadCardset images = Images(self.dataloader, cs) File "/usr/share/games/pysolfc/pysollib/images.py", line 60, in __init__ if TOOLKIT == 'tk' and Image and Image.VERSION >= '1.1.7': AttributeError: 'module' object has no attribute 'VERSION' This is a known incompatibility with the new python Image library (pillow 0.6?), and has been addressed by the pysolfc developers in April, current version 2.6.4 is fixed. I have (testing): python-pil.imagetk/testing,unstable,now 6.1.0-1 amd64 [installiert] Python-Bildbearbeitungsbibliothek - ImageTk-Modul (Pillow-Fork) please upgrade to current upstream version! Heinz Repp --- End Message --- --- Begin Message --- Source: pysolfc Source-Version: 2.6.4-1 We believe that the bug you reported is fixed in the latest version of pysolfc, 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 931...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Juhani Numminen (supplier of updated pysolfc 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, 18 Jul 2019 21:16:29 +0300 Source: pysolfc Binary: pysolfc Architecture: source all Version: 2.6.4-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Juhani Numminen Description: pysolfc- collection of more than 1000 solitaire card games Closes: 781663 912508 919923 931851 Changes: pysolfc (2.6.4-1) unstable; urgency=medium . * Team upload. . [ Hugo Lefeuvre ] * Migrate to Python 3 (Closes: #912508). * debian/control: - Update Vcs-Git and Vcs-Browser fields (Salsa migration). - Multiple build-dependency changes due to the migration to Python 3 and documentation generation which requires several binary dependencies to be build dependencies as well. * debian/copyright: - Update copyright years. - Refresh files list and copyrights to match new upstream release. * debian/patches: - Refresh patches for new upstream release, remove merged patches. * Update docs list. * debian/rules: - Build translations from po. - Build html documentation from source. - Migrate to pybuild. * Bump watch file version to
Bug#932404: firefox-esr, FTBFS "possible zip bomb".
On Fri, Jul 19, 2019 at 08:30:32AM +0900, Mike Hommey wrote: > Download > http://ftp.mozilla.org/pub/firefox/releases/68.0.1/linux-x86_64/en-US/firefox-68.0.1.tar.bz2 > Extract it > Unzip omni.ja > > The file *is* funky, but afaik it does not have overlapping components. I think I know what's going on here--the Firefox omni.ja file uses an unusual zip layout, specific to Firefox, that puts the central directory at the *beginning* of the file, rather than the end. This is meant to allow for better disk caching when unpacking omni.ja, or something. https://bugzilla.mozilla.org/show_bug.cgi?id=559961 https://bugzilla.mozilla.org/show_bug.cgi?id=589368 You can see in this code sample, first Firefox looks for the central directory at offset 4, then falls back to the usual EOCD search. https://hg.mozilla.org/mozilla-central/file/af29567ecdba/modules/libjar/nsZipArchive.cpp#l597 https://hg.mozilla.org/mozilla-central/file/af29567ecdba/modules/libjar/nsZipArchive.cpp#l638 You can see this in the output of "zipinfo" as well; the central directory is at offset 4, and it shows warning relating to the unusual layout. (I'm using zipinfo 6.0-21+deb9u1 from Buster, which hasn't been patched yet.) $ zipinfo -v /usr/lib/firefox-esr/omni.ja The central directory is 111932 (0001B53Ch) bytes long, and its (expected) offset in bytes from the beginning of the zipfile is 4 (0004h). warning [/usr/lib/firefox-esr/omni.ja]: 16789751 extra bytes at beginning or within zipfile (attempting to process anyway) error [/usr/lib/firefox-esr/omni.ja]: reported length of central directory is -16789751 bytes too long (Atari STZip zipfile? J.H.Holm ZIPSPLIT 1.1 zipfile?). Compensating... The unzip patch starts by initializing a cover that extends from the beginning of the central directory to the end of the file. In the case of the Firefox layout, that's the *entire* file, except for the first 4 bytes. So while none of the file overlap each other, they all appear to overlap the central directory. https://github.com/madler/unzip/commit/47b3ceae397d21bf822bc2ac73052a4b1daf8e1c#diff-42593f5e58d2da2cb6b6a937a04e16ddR496 The Firefox layout has also caused problems with 7-Zip: https://sourceforge.net/tracker/?func=detail=3065694_id=14481=114481 One possible solution is to adjust the bomb-cover patch so it only covers the actual length of the central directory (and the EOCD) separately. In almost all normal zip files, these two structures will be adjacent, so the effect will be the same as now.
Bug#932080: marked as done (sssd fails to start: #886483 raises from the dead)
Your message dated Fri, 19 Jul 2019 15:51:20 + with message-id and subject line Bug#932080: fixed in sssd 2.2.0-4 has caused the Debian Bug report #932080, regarding sssd fails to start: #886483 raises from the dead 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.) -- 932080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932080 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sssd Version: 2.2.0-3 Severity: grave Justification: renders package unusable After upgrading to 2.2.0-3, sssd will not start (automatically). There are two failure modes, both likely related to #886483 I reported over a year ago. First failure mode happens if any services are listed in sssd.conf like (any service here will cause failure) service = pam, nss Startig sssd with systemctl will now (correctly) start the listed services, BUT it will also insist on trying to start the corresponding socket listener, which times out trying to get the socket, eventually causing systemd to kill the whole stack of processes, leaving no sssd processes running. It is, however, possible to start sssd manually from command line: "sssd -i" works as expected. Second failure mode is triggered by trying the obvious: commenting out the whole "service" line from sssd.conf. However, now sssd fails both from command line and from systemd because "sssd: SSSD couldn't load the configuration database [22]: Invalid argument." There does not seem to be any way of disabling all non-socket services but if at least one non-socket service is active, systemd will time out trying to load the corresponding socket. I even removed every .socket file related to sssd from my systemd but it didn't help (yes, I did a daemon-reexec and daemon-reload). Only fix I managed to find is a downgrade to 1.16.3-3.1. Cheers, Juha -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: sssd Source-Version: 2.2.0-4 We believe that the bug you reported is fixed in the latest version of sssd, 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 932...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated sssd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 19 Jul 2019 18:15:41 +0300 Source: sssd Architecture: source Version: 2.2.0-4 Distribution: unstable Urgency: medium Maintainer: Debian SSSD Team Changed-By: Timo Aaltonen Closes: 932080 Changes: sssd (2.2.0-4) unstable; urgency=medium . [ Sam Morris ] * fix-have-systemd.patch: correct detection of systemd.pc (Closes: #932080) * default-to-socket-activated-services.diff: rely on socket activation to spawn nss and pam responders Checksums-Sha1: 2a2925398e1dbc49270ef2789d17b765229bec46 5154 sssd_2.2.0-4.dsc ceda844f5d0d1d43e6cdb1195eb2179322169299 107452 sssd_2.2.0-4.diff.gz 2b57a9d8c47eceb901a46ba4070897cd48834a32 10062 sssd_2.2.0-4_source.buildinfo Checksums-Sha256: 3e9b54c26d144485636d22a849a8e5f9f30c3fc44adb8e1d01c296356c0669dc 5154 sssd_2.2.0-4.dsc 366c97605a1c768ed91379f72d4ebf2f3e94947c3dd4d3df2ead663eda334de7 107452 sssd_2.2.0-4.diff.gz dc5eec465b0e0444a37b073088afaa5b57716f08bcedb44c8da2763e696382e6 10062 sssd_2.2.0-4_source.buildinfo Files: 70572d70f6864ce91740a98c50059599 5154 utils optional sssd_2.2.0-4.dsc 8264e436058cfad06bb8ebdcc42d9ea6 107452 utils optional sssd_2.2.0-4.diff.gz 5f69c2dce74229bf3ff62ce04c1d3106 10062 utils optional sssd_2.2.0-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl0x384ACgkQy3AxZaiJ hNwMyg//Q3iNAanGzCH8oFNzIfPNol04IHt6bOMo5ZgsH342l7Sa+7Tj5FtR9TpP 1DUnobmYXONFW4tg7GlLA1JnDNuNcfRWBL64qioHVn5fANfbtOhbqg+2dwYqlGft MIHX/zSv3Z1woslye+OnJzxTK1tvtnKYzPRvmUbu+GS9q3HnEnGCY1H/y4DrNl7W
Bug#865585: marked as done (apex FTBFS: No rule to make target 'debian-nslu2-armel_config'. Stop.)
Your message dated Fri, 19 Jul 2019 15:51:28 + with message-id and subject line Bug#931626: Removed package(s) from unstable has caused the Debian Bug report #865585, regarding apex FTBFS: No rule to make target 'debian-nslu2-armel_config'. Stop. 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.) -- 865585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apex Version: 1.6.10 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=apex=armel=1.6.10%2Bb2=1438585908=0 ... debian/rules build test -f src/apex/init.c -a -f debian/rules /usr/bin/make debian-nslu2-armel_config make[1]: Entering directory '/«BUILDDIR»/apex-1.6.10+b2' Makefile:447: *** mixed implicit and normal rules: deprecated syntax Makefile:1588: *** mixed implicit and normal rules: deprecated syntax make[1]: *** No rule to make target 'debian-nslu2-armel_config'. Stop. make[1]: Leaving directory '/«BUILDDIR»/apex-1.6.10+b2' make: *** [build] Error 2 --- End Message --- --- Begin Message --- Version: 1.6.10+rm Dear submitter, as the package apex has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/931626 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---
Bug#917650: marked as done (FTBFS: include/qi.h:104:29: error: duplicate 'const' declaration specifier [-Werror=duplicate-decl-specifier])
Your message dated Fri, 19 Jul 2019 15:49:47 + with message-id and subject line Bug#931578: Removed package(s) from unstable has caused the Debian Bug report #917650, regarding FTBFS: include/qi.h:104:29: error: duplicate 'const' declaration specifier [-Werror=duplicate-decl-specifier] 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.) -- 917650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:qi Version: 2013-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi! I've been doing a full rebuild of the Debian archive, building all source packages targeting armel and armhf using arm64 hardware. We are planning in future to move all of our 32-bit armel/armhf builds to using arm64 machines, so this rebuild is to identify packages that might have problems with this configuration. qi now fails to compile for armel: gcc -Wall -Werror -I include -g -c -Os -fno-strict-aliasing -mlong-calls -fno-common -ffixed-r8 -msoft-float -fno-builtin -ffreestanding -mar ch=armv4t -mno-thumb-interwork -Wstrict-prototypes -DBUILD_HOST="mjolnir" -DBUILD_VERSION="debian_2013-1" -DBUILD_DATE="2018-12-29T18:58: 05+00:00" -DQI_CPU="s3c2442" -o src/memory-test.o src/memory-test.c In file included from src/memory-test.c:1: include/qi.h:104:29: error: duplicate 'const' declaration specifier [-Werror=duplicate-decl-specifier] const struct board_variant const * (*get_board_variant)(void); ^ cc1: all warnings being treated as errors make[2]: *** [Makefile:69: src/memory-test.o] Error 1 make[2]: Leaving directory '/<>' Looks like newer compilers are now finding more warnings, and -Werror makes this a failure. Full log online at https://www.einval.com/debian/arm/rebuild-logs/armel/FAIL/qi_2013-1_armel.log -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Version: 2013-1+rm Dear submitter, as the package qi has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/931578 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---
Bug#932452: adacontrol: FTBFS on i386 mips because of tests
Source: adacontrol Version: 1.21r3-2 Severity: serious Justification: fails to build from scratch on i386 mips Here are the relevant lines from build logs. On i386 mips hppa powerpc: => t_type_usage.txtFAILED<= ... -- Passed= 85, Failed= 1 -- --- Total run time: 1mn 20s. make[1]: *** [debian/rules:58: override_dh_auto_test-arch] Error 1 On sparc64: => tfw_stress.txt FAILED - Passed= 85, Failed= 1 -- On s390x: -- Passed= 86, Failed= 0 -- --- make[1]: *** [debian/rules:58: override_dh_auto_test-arch] Error 1
Bug#909523: marked as done (Default configuration is incompatible with a non-SELinux active LSM)
Your message dated Fri, 19 Jul 2019 15:34:23 + with message-id and subject line Bug#909523: fixed in cachefilesd 0.10.10-0.2 has caused the Debian Bug report #909523, regarding Default configuration is incompatible with a non-SELinux active LSM 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.) -- 909523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cachefilesd Version: 0.10.10-0.1 Severity: important Important since Apparmor is on by default now. I rebooted after enabling Apparmor, and cachefilesd wouldn't start: Sep 24 13:53:17 Zia cachefilesd[1105]: About to bind cache Sep 24 13:53:17 Zia kernel: CacheFiles: Security denies permission to nominate security context: error -2 Sep 24 13:53:17 Zia cachefilesd[1105]: CacheFiles bind failed: errno 2 (No such file or directory) Sep 24 13:53:17 Zia cachefilesd[1052]: Starting FilesCache daemon : cachefilesd failed! Sep 24 13:53:17 Zia systemd[1]: cachefilesd.service: Control process exited, code=exited status=1 Sep 24 13:53:17 Zia systemd[1]: cachefilesd.service: Failed with result 'exit-code'. Sep 24 13:53:17 Zia systemd[1]: Failed to start LSB: CacheFiles daemon. Trying a few more times (after the system booted) also produced the same error each time: Sep 24 13:57:12 Zia systemd[1]: Starting LSB: CacheFiles daemon... Sep 24 13:57:13 Zia cachefilesd[6213]: About to bind cache Sep 24 13:57:13 Zia cachefilesd[6213]: CacheFiles bind failed: errno 2 (No such file or directory) Sep 24 13:57:13 Zia kernel: CacheFiles: Security denies permission to nominate security context: error -2 Sep 24 13:57:13 Zia cachefilesd[6208]: Starting FilesCache daemon : cachefilesd failed! Sep 24 13:57:13 Zia systemd[1]: cachefilesd.service: Control process exited, code=exited status=1 Sep 24 13:57:13 Zia systemd[1]: cachefilesd.service: Failed with result 'exit-code'. Sep 24 13:57:13 Zia systemd[1]: Failed to start LSB: CacheFiles daemon. Rebooting with apparmor=0 on the kernel command line makes it work again. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing'), (200, 'unstable'), (150, 'stable'), (100, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-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_GB (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages cachefilesd depends on: ii libc6 2.27-6 cachefilesd recommends no packages. cachefilesd suggests no packages. -- Configuration Files: /etc/cachefilesd.conf changed [not included] /etc/default/cachefilesd changed [not included] /etc/init.d/cachefilesd changed [not included] /etc/logcheck/ignore.d.workstation/cachefilesd [Errno 13] Permission denied: '/etc/logcheck/ignore.d.workstation/cachefilesd' -- no debconf information --- End Message --- --- Begin Message --- Source: cachefilesd Source-Version: 0.10.10-0.2 We believe that the bug you reported is fixed in the latest version of cachefilesd, 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 909...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. intrigeri (supplier of updated cachefilesd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 19 Jul 2019 14:55:33 + Source: cachefilesd Architecture: source Version: 0.10.10-0.2 Distribution: unstable Urgency: medium Maintainer: Shane Wegner Changed-By: intrigeri Closes: 909523 Changes: cachefilesd (0.10.10-0.2) unstable; urgency=medium . * Non-maintainer upload. * Disable secctx in the default cachefilesd.conf (Closes: #909523). Accordingly, document in README.Debian how to set the correct security context under SELinux. Checksums-Sha1: 9b2f13ff8dbe009fdeac1c018594147b16f9b194 1718 cachefilesd_0.10.10-0.2.dsc 8c6b50fd6d562f4d4e4bb423dcce4505b20dd27b 34222 cachefilesd_0.10.10-0.2.tar.gz Checksums-Sha256:
Bug#909523: Intent to NMU (Re: Bug#909523: Default configuration is incompatible with a non-SELinux active LSM)
Hi, intrigeri: > Dmitry Smirnov: >>> If one of you feels responsible for maintaining this package but >>> temporarily lacks time, I (or one of the attendees to one of the many >>> upcoming BSPs) will gladly fix this with a NMU. >> Please, please. That would be really nice if you could. Thanks. Done (0.10.10-0.2). This was my first attempt at using dgit to NMU so let's hope I did not bork it. I'm attaching the 3 commits I did on top of 0.10.10-0.1. Cheers, -- intrigeri >From 6c9e84a021b24d98314e44c1063712596752e1aa Mon Sep 17 00:00:00 2001 From: intrigeri Date: Fri, 19 Jul 2019 14:49:19 + Subject: [PATCH 1/3] Disable secctx in the default cachefilesd.conf (Closes: #909523). This configuration line assumes that: - either there is no active LSM, which is wrong on Buster where AppArmor is enabled by default; - or SELinux is the active LSM, which is a rare configuration on Debian. When this assumption is wrong, i.e. in most cases on current Debian Buster/testing/sid, cachefilesd fails to start if this configuration line is enabled. --- cachefilesd.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cachefilesd.conf b/cachefilesd.conf index 6905281..bf14950 100644 --- a/cachefilesd.conf +++ b/cachefilesd.conf @@ -21,4 +21,4 @@ fstop 3% # Assuming you're using SELinux with the default security policy included in # this package -secctx system_u:system_r:cachefiles_kernel_t:s0 +# secctx system_u:system_r:cachefiles_kernel_t:s0 -- 2.22.0 >From a5b3654d8f7fbdf81293be906f4f8603a59bad99 Mon Sep 17 00:00:00 2001 From: intrigeri Date: Fri, 19 Jul 2019 14:54:11 + Subject: [PATCH 2/3] README.Debian: document how to set the correct security context under SELinux. --- debian/README.Debian | 7 +++ 1 file changed, 7 insertions(+) create mode 100644 debian/README.Debian diff --git a/debian/README.Debian b/debian/README.Debian new file mode 100644 index 000..4658b2b --- /dev/null +++ b/debian/README.Debian @@ -0,0 +1,7 @@ +SELinux +=== + +When the SELinux LSM is active, in order to set the correct security +context for cachefilesd, uncomment the "secctx" line in +/etc/cachefilesd.conf. + -- 2.22.0 >From 044f44ed267e084cc24103a662456b0c7199ee09 Mon Sep 17 00:00:00 2001 From: intrigeri Date: Fri, 19 Jul 2019 14:55:38 + Subject: [PATCH 3/3] cachefilesd (0.10.10-0.2) Git-Dch: Ignore --- debian/changelog | 9 + 1 file changed, 9 insertions(+) diff --git a/debian/changelog b/debian/changelog index 1ec7b2f..74c5188 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +cachefilesd (0.10.10-0.2) unstable; urgency=medium + + * Non-maintainer upload. + * Disable secctx in the default cachefilesd.conf (Closes: #909523). +Accordingly, document in README.Debian how to set the correct security +context under SELinux. + + -- intrigeri Fri, 19 Jul 2019 14:55:33 + + cachefilesd (0.10.10-0.1) unstable; urgency=medium * Non-maintainer upload. -- 2.22.0
Bug#872497: marked as done (vdr-plugin-games FTBFS with vdr 2.3.8)
Your message dated Fri, 19 Jul 2019 15:08:30 + with message-id and subject line Bug#872497: fixed in vdr-plugin-games 0.6.3-46.1 has caused the Debian Bug report #872497, regarding vdr-plugin-games FTBFS with vdr 2.3.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 872497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vdr-plugin-games Version: 0.6.3-46 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-games.html ... g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Wdate-time -D_FORTIFY_SOURCE=2 -c -DVERSION=\"0.6.3\" -D_GNU_SOURCE -DVDRVERSNUM=20308 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/vdr/include -I/usr/include/vdr/include -c screen.cpp -o screen.o screen.cpp: In function 'int Scr::palette(int)': screen.cpp:90:23: error: 'cBitmap* cOsd::GetBitmap(int)' is protected within this context screen->GetBitmap(0)->SetColor(i, PALETTE(i)); ^ In file included from screen.cpp:8:0: /usr/include/vdr/osd.h:792:12: note: declared protected here cBitmap *GetBitmap(int Area); ^ Makefile:95: recipe for target 'screen.o' failed make[3]: *** [screen.o] Error 1 --- End Message --- --- Begin Message --- Source: vdr-plugin-games Source-Version: 0.6.3-46.1 We believe that the bug you reported is fixed in the latest version of vdr-plugin-games, 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 872...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated vdr-plugin-games 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 Sep 2017 11:22:32 +0200 Source: vdr-plugin-games Binary: vdr-plugin-games Architecture: source Version: 0.6.3-46.1 Distribution: unstable Urgency: medium Maintainer: Debian VDR Team Changed-By: Gianfranco Costamagna Description: vdr-plugin-games - VDR plugin providing OSD games like tetris, snake and more Closes: 872497 Changes: vdr-plugin-games (0.6.3-46.1) unstable; urgency=medium . * Non-maintainer upload * #define DEPRECATED_GETBITMAP to make it build. (plugin needs porting) Closes: #872497 Checksums-Sha1: ec89bb8336de8beb40d1450bef3097cc742f9c67 2090 vdr-plugin-games_0.6.3-46.1.dsc edd1f149c2e811f748cb47ad1faa1eac0ecadab1 6792 vdr-plugin-games_0.6.3-46.1.debian.tar.xz b23423688b1ac2928f9303ca151b985ef1805697 7097 vdr-plugin-games_0.6.3-46.1_source.buildinfo Checksums-Sha256: 81c22bbed4ba98eeb3b9dbcc9b8b9ea1c7ede4ccbc41f5fc7fe79eb7ee563759 2090 vdr-plugin-games_0.6.3-46.1.dsc ecca91dd406f558af6a8373f4eb3e1240ba56b33b8e1bfa0a2eb02ea01ccfa6e 6792 vdr-plugin-games_0.6.3-46.1.debian.tar.xz ff73e25408eaafe31f2df289a0b4c4174df219b3c3efaa1ddf2cf67890be5731 7097 vdr-plugin-games_0.6.3-46.1_source.buildinfo Files: ef55bc763980f6fd51ba6170d71f60f9 2090 video extra vdr-plugin-games_0.6.3-46.1.dsc b74e9ac4fb4b5f3954844f8f65f1eddf 6792 video extra vdr-plugin-games_0.6.3-46.1.debian.tar.xz 2ca6c8cae0e8c38f14bb4bc70f369b3c 7097 video extra vdr-plugin-games_0.6.3-46.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl0x2HwACgkQ808JdE6f XdnxGg//a/UnoJMUORPxUS0W+JqM3+BhAipWaRLPubjpr6sJNxJnQWW6rsW8G2dN XImzoj0WvQYdwH73xQQ/xWCYMtugZaFH6LbE0cRnnka04Bop3U7SWZo2LnR2JK2D PYgk5qxmDLoO+P685bvE2di30LUZqrEKbSnLuGw1bjVb85Z5SEVjbWnid2Zszd9x Vnx38zUnMktVrw25ArE+wWIBbHJFPF6NA6gEn+UD5nk3DhbtB0m2OTo8anu2JInx 3A2HNogUuX9gEf9i6VvOTiVkNqHEUi//eVr9fJsxQURkzqe2G7iReKqQ3Uopnkzy
Bug#931985: marked as done (file: Experimental file breaks package creation at dh_shlibdeps stage due to file command)
Your message dated Fri, 19 Jul 2019 15:07:28 + with message-id and subject line Bug#931985: fixed in file 1:5.37-2 has caused the Debian Bug report #931985, regarding file: Experimental file breaks package creation at dh_shlibdeps stage due to file command 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.) -- 931985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931985 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: file Version: 1:5.37-1 Severity: critical Justification: breaks unrelated software I know it is experimental but anyway it should be fixed and if you build pacakges, you cannot anymore. Tried on two pacakges, same error. dh_shlibdeps --dpkg-shlibdeps-params=--ignore-missing-info dh_shlibdeps: Compatibility levels before 9 are deprecated (level 5 in use) dh_shlibdeps: Compatibility levels before 9 are deprecated (level 5 in use) dh_shlibdeps: file -e apptype -e ascii -e encoding -e cdf -e compress -e tar debian/tvheadend/usr/bin/tv_meta_tmdb.py died with signal 31 dh_shlibdeps: Aborting due to earlier error -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.58 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages file depends on: ii libc62.28-10 ii libmagic11:5.37-1 ii libseccomp2 2.3.3-4 ii zlib1g 1:1.2.11.dfsg-1 file recommends no packages. file suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: file Source-Version: 1:5.37-2 We believe that the bug you reported is fixed in the latest version of file, 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 931...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Biedl (supplier of updated file package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 19 Jul 2019 16:18:13 +0200 Source: file Architecture: source Version: 1:5.37-2 Distribution: unstable Urgency: medium Maintainer: Christoph Biedl Changed-By: Christoph Biedl Closes: 931985 Changes: file (1:5.37-2) unstable; urgency=medium . * New upstream version 5.37, upload to unstable * Refine seccomp support. Closes: #931985 * Cherry-pick "Add lzma decompression support" * Cherry-pick "Add lzma and bzip built-in decompression support" Checksums-Sha1: 15a2d669dae45a9d77d2ea4c91a26d44599989b9 2325 file_5.37-2.dsc e8eef00898737d8d70821eb1b0b976c83e25f3c0 36136 file_5.37-2.debian.tar.xz 9813521c7e980cb6e41806756a23232193004602 6638 file_5.37-2_powerpc.buildinfo Checksums-Sha256: 2e9d514a65bcc5bfb16e6fc0ec415bd72bd0e31bc8d80a9d7df0826258d6ca06 2325 file_5.37-2.dsc 6ff4d6a3ca5dc0022cab39052e709e5aca76eba0e30bae3a3ae6ca186ae449b4 36136 file_5.37-2.debian.tar.xz 9bef68923944f0010ec0f98aa88ac53e147f0989b5a837956e1fcf8af8e7b6c3 6638 file_5.37-2_powerpc.buildinfo Files: 044b3e8897adbe6e15ebf2344c95da49 2325 utils standard file_5.37-2.dsc a3e6bc6db469a7ea4eee4aecd0056137 36136 utils standard file_5.37-2.debian.tar.xz d6dab9dbc55e856085da0185a62de4c3 6638 utils standard file_5.37-2_powerpc.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEWXMI+726A12MfJXdxCxY61kUkv0FAl0x2HYACgkQxCxY61kU kv0uIw//XBwu/CoItH03bZmnnljGXzIb30SRfIOx6RMMlN+Bd9O5R48pzpuasgwP dDzAE2XnYRnDR2x7bUsIH3Kcv29H85sF2Jx+ZGHOqfydcCPPyagriN4mbWIaJxZY L+pxxRfDfZTNuW9tO59b2ylAiMhJKmjsJlzSLy963nS2qiihDh0ZwnCcR+jOCu6a UB4H3BEt1wYOHdDOYWwED9MS8dshx8Ykb745vzj6GF/vTmtSijvyK7F+IsObz6zy nNaAw9auQRuM9MbK279ecLx5Y4JYuMqiXBNLvvM+Dv+VmefPGukU5ugbSxAZYckL EkshJacP5a0oS8seu78kXzIaf0OSwaxS5ojvn/pct0nYbagxZyIODloTBd3Kb8GA bv0PnKHqFMlOomJIaIYNBWCBkBz/EEqJd3u/yGwyPfI5HD5n59V4Z6VKBU9RWZza +JROKC9FpWumu0TyGEKYdMPLqWqRzQVDe8EmdaJAPQ54DRv1HLjIR7AiKEZpfmnt OD0OY9Qj/jL+303F8HJ2iqm8RajjASIca7y/4R70Wr7TVNMJU0pnoOkj3IFZ9yzF rYS+I+I7Up1bzgTFjboNj9Knl+FrAXo97IOe+aKFpnqDuR34k1t/BQDps/tnOcMO
Bug#872497: vdr-plugin-games FTBFS with vdr 2.3.8
On Thu, 17 Aug 2017 23:17:07 +0300 Adrian Bunk wrote: > Source: vdr-plugin-games > Version: 0.6.3-46 > Severity: serious > Tags: buster sid > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-games.html > > ... > g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 > -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE > -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Wdate-time > -D_FORTIFY_SOURCE=2 -c -DVERSION=\"0.6.3\" -D_GNU_SOURCE -DVDRVERSNUM=20308 > -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 > -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE > -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE > -I/usr/include/vdr/include -I/usr/include/vdr/include -c screen.cpp -o > screen.o > screen.cpp: In function 'int Scr::palette(int)': > screen.cpp:90:23: error: 'cBitmap* cOsd::GetBitmap(int)' is protected within > this context > screen->GetBitmap(0)->SetColor(i, PALETTE(i)); >^ > In file included from screen.cpp:8:0: > /usr/include/vdr/osd.h:792:12: note: declared protected here >cBitmap *GetBitmap(int Area); > ^ > Makefile:95: recipe for target 'screen.o' failed > make[3]: *** [screen.o] Error 1 > > patch attached and uploaded diff -Nru vdr-plugin-games-0.6.3/debian/changelog vdr-plugin-games-0.6.3/debian/changelog --- vdr-plugin-games-0.6.3/debian/changelog 2015-09-22 20:55:36.0 +0200 +++ vdr-plugin-games-0.6.3/debian/changelog 2017-09-16 11:22:32.0 +0200 @@ -1,3 +1,11 @@ +vdr-plugin-games (0.6.3-46.1) unstable; urgency=medium + + * Non-maintainer upload + * #define DEPRECATED_GETBITMAP to make it build. +(plugin needs porting) Closes: #872497 + + -- Gianfranco Costamagna Sat, 16 Sep 2017 11:22:32 +0200 + vdr-plugin-games (0.6.3-46) unstable; urgency=medium * Now supporting the /etc/vdr/conf.d mechanism diff -Nru vdr-plugin-games-0.6.3/debian/patches/series vdr-plugin-games-0.6.3/debian/patches/series --- vdr-plugin-games-0.6.3/debian/patches/series2015-09-22 20:55:36.0 +0200 +++ vdr-plugin-games-0.6.3/debian/patches/series2017-09-16 11:22:32.0 +0200 @@ -2,3 +2,4 @@ 03_games-0.6.3-fix-INCLUDES.patch 04_gcc-4.6.patch flags.patch +vdr.patch diff -Nru vdr-plugin-games-0.6.3/debian/patches/vdr.patch vdr-plugin-games-0.6.3/debian/patches/vdr.patch --- vdr-plugin-games-0.6.3/debian/patches/vdr.patch 1970-01-01 01:00:00.0 +0100 +++ vdr-plugin-games-0.6.3/debian/patches/vdr.patch 2017-09-16 11:22:32.0 +0200 @@ -0,0 +1,17 @@ +Description: + * #define DEPRECATED_GETBITMAP to make it build. + (plugin needs porting) See: #872497 +Author: Gianfranco Costamagna +Last-Update: 2017-09-16 + +--- vdr-plugin-games-0.6.3.orig/screen.cpp vdr-plugin-games-0.6.3/screen.cpp +@@ -2,6 +2,8 @@ + #include + #include + ++#define DEPRECATED_GETBITMAP 1 ++ + #ifdef SDL + #include + #else
Bug#932339: marked as pending in lintian
Control: tag -1 pending Hello, Bug #932339 in lintian 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/lintian/lintian/commit/3ccd3625bc29c7a14d9ef82418754b6eadb158c5 Adjust systemd-general test for recent versions of debhelper. (Closes: #932339) The upgrade of debhelper to version 12.2.2 exposed several issues in Lintian. First of all, the systemd-general test had to be updated to use dh_installsystemd which apparently did not exist when the test was written. Second, it had to accommodate an update to dh_installinit which no longer allows the naming pattern $daemon.init when '--name=$daemon' is used. dh_installinit now requires the file to be called $package.$daemon.init. Some other files were also renamed. All of these issues are fixed here, except the symptom of hanging while building test packages, which will be addressed separately in the solution to This commit causes the unstable pipelines on jenkins and Gitlab to work again. Gbp-Dch: ignore Signed-off-by: Chris Lamb (this message was generated automatically) -- Greetings https://bugs.debian.org/932339
Processed: Bug#932339 marked as pending in lintian
Processing control commands: > tag -1 pending Bug #932339 [src:lintian] Building of test packages hangs in Lintian due to commit 789eb18b Added tag(s) pending. -- 932339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#932073: closed by Niels Thykier (Bug#932073: fixed in debhelper 12.2.1)
control: tags -1 +confirmed
[2019-07-17 07:41] Helmut Grohne
> part text/plain1094
> Control: reopen -1
> Control: affects -1 + src:dropbear
>
> On Tue, Jul 16, 2019 at 08:42:09PM +, Debian Bug Tracking System wrote:
> >* dh_installinit: Fix regression where dh_installinit bailed
> > out on --name if only one of the acted on packages had an
> > init script file. Thanks to Helmut Grohne for reporting
> > the issue. (Closes: #932073)
>
> The bug is partially fixed. A full build of openssh and dropbear now
> works. At least the following situation (dropbar) is still broken:
>
> The init script lives in an arch-all package, you pass the relevant
> --name and you perform an arch-only build. Here is a cross build log,
> but it fully reproduces natively:
Yep, -A/-B separation. Can someone remind me its purpose?
As for code, then instead of "$dh{DOPACKAGES}" there must be
"getpackages()", like this. Not sure how to write regression test for
this situation.
diff --git a/dh_installinit b/dh_installinit
index 5aecf25b..6a7abaf8 100755
--- a/dh_installinit
+++ b/dh_installinit
@@ -233,7 +233,7 @@ init(options => {
my %snippet_options = ('snippet-order' => 'service');
if (my $name = $dh{NAME}) {
- if (!grep { -f "debian/$_.${name}.init" || -f
"debian/$_.${name}.default" } @{$dh{DOPACKAGES}}) {
+ if (!grep { -f "debian/$_.${name}.init" || -f
"debian/$_.${name}.default" } getpackages()) {
error("--name=$dh{NAME} option specified, but init script nor
default file not found");
}
}
--
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.
Processed: Re: Bug#932073: closed by Niels Thykier (Bug#932073: fixed in debhelper 12.2.1)
Processing control commands: > tags -1 +confirmed Bug #932073 [debhelper] dh_installinit fails with "--name=foo option specified, but init script not found" Bug #932170 [debhelper] bird2: FTBFS (dh_installinit: --name=bird option specified, but init script not found) Added tag(s) confirmed. Added tag(s) confirmed. -- 932073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932073 932170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#932339: Building of test packages hangs in Lintian due to commit 789eb18b
[2019-07-17 19:24] Felix Lechner > Hi, > > Updating from version 12.1.1 in testing to 12.2.2 breaks the build > process for test packages in Lintian. The unstable pipelines on > jenkins and Gitlab are failing. > > The command 't/bin/build-test-packages' in Lintian runs for a while > but then hangs. Some of the processes that build test packages in > parallel may not terminate. The command also stalled when using > '--jobs=1'. I was unable to locate an error message. > > The issue is caused by commit 789eb18b, which was found through > bisection. This change can't hang debhelper -- it adds no loops. But it can cause debhelper errorneously fail (see #932073). This extra check was added in 12.2. Maybe it matters. But if this conjecture is true, it is strange that bisection found 789eb18b guilty, but not e5fc959, which produces even more erroneous failures. -- Note, that I send and fetch email in batch, once in a few days. Please, mention in body of your reply when you add or remove recepients.
Bug#932080: sssd fails to start: #886483 raises from the dead
FYI, the systemd.m4 typo has been fixed upstream: https://pagure.io/SSSD/sssd/c/8d64e9f5229967d382c6280d89b139e024bd2c1a Cheers, Andre'
Bug#932356: marked as done (autotest fail with gap 4.10.2)
Your message dated Fri, 19 Jul 2019 12:08:07 + with message-id and subject line Bug#932356: fixed in gap-guava 3.14+ds-2 has caused the Debian Bug report #932356, regarding autotest fail with gap 4.10.2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 932356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gap-guava Version: 3.14+ds-1 Severity: serious Dear Debian Science Maintainers, gap-guava 3.14+ds-1 is failing the autotest with gap 4.10.2. Please rebuild the package for the new GAP version. Cheers, -- Bill. Imagine a large red swirl here. --- End Message --- --- Begin Message --- Source: gap-guava Source-Version: 3.14+ds-2 We believe that the bug you reported is fixed in the latest version of gap-guava, 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 932...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jerome Benoit (supplier of updated gap-guava package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 19 Jul 2019 11:59:28 + Source: gap-guava Architecture: source Version: 3.14+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Jerome Benoit Closes: 932356 Changes: gap-guava (3.14+ds-2) unstable; urgency=medium . * Autotest fix (Closes: #932356). * Debianization: - debian/copyright: - year tupes, update; - debian/control: - debhelper, bump to 12; - Depends field, gap, bump to 4r10p2-1~ ; - Standards Version, bump to 4.4.0 (no change); - debian/compat, discard. Checksums-Sha1: c622f042f25541d8c02c443b1c6b35210269a9dd 2902 gap-guava_3.14+ds-2.dsc 869d23184c1b76b704fe40b3fb3ac0d997537a7e 6864 gap-guava_3.14+ds-2.debian.tar.xz 5b15b1e63f1bfcaf45f8db13c3f1ca28833e275e 9464 gap-guava_3.14+ds-2_source.buildinfo Checksums-Sha256: 4bfc66d74b5071e43c1ed872df436375143662cbb92a1ed0a1128b1044de85be 2902 gap-guava_3.14+ds-2.dsc 33ff44fa5a02ecf01a48c78f434fe526667680f481a94953a4c54930299fe634 6864 gap-guava_3.14+ds-2.debian.tar.xz 97e29e31fb759216999be4b7ee72fdf83ef38870cfc1259821971d639c7dd1d9 9464 gap-guava_3.14+ds-2_source.buildinfo Files: e7b60e1a8c29ee776902419d4a5a1345 2902 math optional gap-guava_3.14+ds-2.dsc 7ddd8c0a4ee01b06651a9ea8e3b705f6 6864 math optional gap-guava_3.14+ds-2.debian.tar.xz 20c9411c60be4da6c6160d3cb1a75885 9464 math optional gap-guava_3.14+ds-2_source.buildinfo -BEGIN PGP SIGNATURE- iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAl0xsVwVHGNhbGN1bHVz QHJlem96ZXIubmV0AAoJED+SGaZ/NsaLgEAgALNDHCcWMhDBZVwP7Yap1tHT6RVk zr8/lc3XP6XZDBYt21xqJX1/FtjhuTEi7Fd0Ze5+SqaeRNj/gIYvjx2Jp4fw3/CX NT0o7gXG23Ye0+kNybBc/TnRfWgWUeKJgutXuOC4eZXrtAKssThKJNcsizOVmitI U+6JBpexA08+TJ3tdAyPagOxIm1fgRVx25bpabHmOkSV6eLbwPj7RoM4sVLRuhTQ wn7fn33x2UeQ+pFZPKYbz0BADN2+mCkyZORpKq5r9ZaylCoW5otdahCxXAKU/1X0 k9RDSYVL1EpIp4njbGn0sv6oXxAFuumIdb2whj4uLPBBseLQ+Emjoy9L5AMl7bZA lj+cuZb4kjah4I+LyfL63L60UbFP3IvG+o40WHqiyXkLX8eEhzQ3Kcbkwg4krBCq rIPOFdOK+XLJYyspb9+6NKVNkFQ8GitfeYLLxU5GPy4zH3J+kq6ximNlfOUkQbAS KiAaGpcwYN9Cwn5SxtaEAon3wB1F6uWCULlLelAyUsnYhGWRR6hqjFd/9wOZC4fv lhT40hcuMpATbFfKR3KnO9oC9BSRuKzNdmbc/HrSF/aTaiTvmjbT9jRTCANWKS+F VfkP7iMrK9qffXd+uDtcOFbpuOjtq/RAc1M67eTw2Ao/aSVK1ShEqav6Uw82HET3 iJrZmmKQ/T8DxEVc450+UuJ+GsZmbz358XOdQ4UqI27a+D6UdxL1BOR1kpgLUnOo YclrXJKQ3K2IdMUajJWm3KZ8qLGMZBak24U7PMDZCqimvA/9ECyh0amoYJBRzPzu umYK5MpB4Jaj8PXJdYB7laMQOhFVnurBKNcTdCo7TnhirWTYMok5Bk6vns02HQHK nx5wNYFOc1irs+AuUQaUQBlRz3tZfrgyHR5u0Yw3dximarK6H3EIYUHu88TZfOtZ VWr8oudyjSyrp1401wXdKBMHE2OmAJMq8Hvjl/0FoXU4yLQma7j2q6v+uP976DZQ W3i4wU94uKrvdP6eIswkoSxChikGTZDbrDOVSE11y/GdMR3PYjZZPfFHDRm0Uthc sRXAL3xp/0qYVWPGaqhTVJwyHg7/FdrJ23ZJ5JdGeG2dng7TJoB5d79AbIBf9aZx ONfvvtgQbMdVcGLLR5NO0VnZsqdeY0/XdmnOh1eTNYWVI+0Kuc0pONQSXhCLjTLQ LjtFPri4c+KHp2uWYgkam7J6pH+vCD69xlJ9z+mgCCgYxdFu7o2D/jH4BNeorqjS XtG8OULSXO6FHKur4TWJt2iwyqdZJHSNGTrCTc3JgLzAzZfGuLeXdDjrEkrQ4Cdx io3/rNT6I7ePwi+iETdSyd+u4NbQzKAe/BFTynBsaxrFhlqZMiMP+BPLnQQ= =KMfG -END PGP SIGNATURE End Message ---
Bug#932258: console-setup-freebsd: missing dependency
On Wed, 2019-07-17 at 18:06:00 +0300, Anton Zinoviev wrote: > On Wed, Jul 17, 2019 at 04:15:51PM +0200, Guillem Jover wrote: > > this seems like a problem with console-setup-freebsd being arch:all > > and depending on kFreeBSD-specific packages which will not be > > available elsewhere, in the same way console-setup-linux is an > > arch:all depending on Linux-specific packages. > > Why is it a problem to have an arch:all package which is installable > only on some architectures (due to missing dependencies)? Because that's generally confusing for users, as they might not know off-hand whether the unsatisfiable problem is due to a bug or it being intended that way (even though it could be made very clear in the Description). It also triggers all kind of alarms on automatic dependency satisfiability checkers, which then need to be ignored (like apparently this being the cause for thus bug report :). And I guess in the metadata sense it seems wrong, as even though the contents do not change across different architectures (so it has one of the facets of an arch:all package) it is still not an archecture indepdenent package (one of the other facets of an arch:all package). Thanks, Guillem
Bug#812704: marked as done (nbibtex: FTBFS - nbib.dvi: file contents does not seem to settle)
Your message dated Fri, 19 Jul 2019 10:07:58 +
with message-id
and subject line Bug#812704: fixed in nbibtex 0.9.18-12
has caused the Debian Bug report #812704,
regarding nbibtex: FTBFS - nbib.dvi: file contents does not seem to settle
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.)
--
812704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nbibtex
Version: 0.9.18-11
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
rubber --warn=all --verbose --ps nbib.tex
compiling nbib.tex...
executing: latex \nonstopmode \input{nbib.tex}
compiling nbib.tex...
executing: latex \nonstopmode \input{nbib.tex}
compiling nbib.tex...
executing: latex \nonstopmode \input{nbib.tex}
compiling nbib.tex...
executing: latex \nonstopmode \input{nbib.tex}
compiling nbib.tex...
executing: latex \nonstopmode \input{nbib.tex}
[depend] while making nbib.dvi: file contents does not seem to settle
There were errors compiling nbib.aux.
Makefile:56: recipe for target 'nbib.ps' failed
make[1]: *** [nbib.ps] Error 2
The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.
Best,
Michael
nbibtex-build-log.txt.gz
Description: application/gunzip
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: nbibtex
Source-Version: 0.9.18-12
We believe that the bug you reported is fixed in the latest version of
nbibtex, 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 812...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Barak A. Pearlmutter (supplier of updated nbibtex package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 19 Jul 2019 11:17:43 +0200
Source: nbibtex
Architecture: source
Version: 0.9.18-12
Distribution: unstable
Urgency: medium
Maintainer: Barak A. Pearlmutter
Changed-By: Barak A. Pearlmutter
Closes: 812704 849900
Changes:
nbibtex (0.9.18-12) unstable; urgency=medium
.
[ Ondřej Nový ]
* d/control: Set Vcs-* to salsa.debian.org
.
[ Barak A. Pearlmutter ]
* bump dh and policy versions
* patch: use latexmk instead of rubber (closes: #812704)
* harden executables
* patch: spelling error
* adjust to dh-churn-generated documentation location change
* patch: remove problematic hypertex option
* generate PDF documentation directly
* dh --parallel now default, remove option
* suggest documentation package (closes: #849900)
* obey multiarch hinter
Checksums-Sha1:
d2666c9860c841971272ec673e9d62d8f5c0465e 1975 nbibtex_0.9.18-12.dsc
5bea5c3da18af046cc1a6b197aadfcc282407da3 8976 nbibtex_0.9.18-12.debian.tar.xz
2f25413733345622486b307fb9e7986c6da7c2b7 8564
nbibtex_0.9.18-12_source.buildinfo
Checksums-Sha256:
4a7e41e05f2a28a3655eadb470b1ee772f694790fd2d2b998304a37d97b9e41b 1975
nbibtex_0.9.18-12.dsc
dfe022b092313ac1d5544a9387efc7dc0e8caa98c7070a2b3323cae5727f4eed 8976
nbibtex_0.9.18-12.debian.tar.xz
41db2e7d87b84e0b583dcbc4a2affe4ea8fc3c79d7a2a2884f116086d1bc9aa3 8564
nbibtex_0.9.18-12_source.buildinfo
Files:
ee3cd0b0893ede260e7f150d1bc96577 1975 tex optional nbibtex_0.9.18-12.dsc
8057404d01570f6871445f20b7cbf17e 8976 tex optional
nbibtex_0.9.18-12.debian.tar.xz
8892d366fd2b2743c7312cab063a81a6 8564 tex optional
nbibtex_0.9.18-12_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEZPQp426hHMLZZlRvEltXR14ZDRgFAl0xjEQACgkQEltXR14Z
DRgVGg/+PQQcBIK4/xnfwP6O4qa5Qm4PHBNxzgO6INNr2B5uHGA0XWLWInzBoTdC
evJ070E8zcNceskUaxvEob0v0vX8mrI4DFe2ID4eN95j+Ckyf7O+zW8WnN2kb1Ub
fcgeakE5U4P1PPV/NTmlfjnHZCcYYm1lwNhuApzdk/7bS8QoCdmyt0t+Go+yNlT2
2MbJ5jNMpKcL2aagt5ElxssA3AVA+dZPG4PnPGfu9hwxfP+DGmkraA+oH78IVxeE
IuletfMqet+/Na6ZaoBDSAIcS/E1UrC07a5nTcEzLUWnKQshgDo1csj/QzdglmDL
XX5zMfqqst/dinVb+7iXtJ4hiHSHPoW+nJwa4t0GMhanLKLX67jfZrkn6avmcn1u
zwLjNJQC7nCk0WVltu5C/661igLHaJfKdEEhPRHzEEegiu1L8/y5Q81EUbxI1P6R
NjHx6moWr3aiEhOQlecTUmHB6NA5EKT5HJKz+o86VZIOBJqp/UDvQeySGoub0s0/
Bug#932404: marked as forwarded (firefox-esr, FTBFS "possible zip bomb".)
Your message dated Fri, 19 Jul 2019 11:58:15 +0200 with message-id <20190719095815.2uvjlcopdp2ncnzd@nucold> has caused the report #932404, regarding firefox-esr, FTBFS "possible zip bomb". to be marked as having been forwarded to the upstream software author(s) Mark Adler (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.) -- 932404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Hello Mark. The Debian firefox package no longer builds from source when using the patched unzip and I'm told this is a "false positive". Is it? This is the way to reproduce it: wget http://ftp.mozilla.org/pub/firefox/releases/68.0.1/linux-x86_64/en-US/firefox-68.0.1.tar.bz2 tar xvf firefox-68.0.1.tar.bz2 firefox/omni.ja firefox/browser/omni.ja unzip firefox/omni.ja unzip firefox/browser/omni.ja Thanks.--- End Message ---
Bug#932404: firefox-esr, FTBFS "possible zip bomb".
Hello Mark. The Debian firefox package no longer builds from source when using the patched unzip and I'm told this is a "false positive". Is it? This is the way to reproduce it: wget http://ftp.mozilla.org/pub/firefox/releases/68.0.1/linux-x86_64/en-US/firefox-68.0.1.tar.bz2 tar xvf firefox-68.0.1.tar.bz2 firefox/omni.ja firefox/browser/omni.ja unzip firefox/omni.ja unzip firefox/browser/omni.ja Thanks.
Processed: closing 812704
Processing commands for cont...@bugs.debian.org: > close 812704 0.9.18-12 Bug #812704 [src:nbibtex] nbibtex: FTBFS - nbib.dvi: file contents does not seem to settle The source 'nbibtex' and version '0.9.18-12' do not appear to match any binary packages Marked as fixed in versions nbibtex/0.9.18-12. Bug #812704 [src:nbibtex] nbibtex: FTBFS - nbib.dvi: file contents does not seem to settle Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 812704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812704 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#812704: closing 812704
close 812704 0.9.18-12 thanks patched to use latexmk instead of rubber
