Bug#923104: h5py: autopkgtest regression
Source: h5py Version: 2.9.0-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Hi Maintainer Since the upload of 2.9.0-1, h5py has been failing its own autopkgtests [1] with the following error: Testing with python3.7: ...s...xxs/usr/lib/python3/dist-packages/h5py/_hl/files.py:258: H5pyDeprecationWarning: File.fid has been deprecated. Use File.id instead. "Use File.id instead.", H5pyDeprecationWarning) ...s..ss...ss.xx.x..x.. -- Ran 509 tests in 1.578s OK (skipped=15, expected failures=6) Testing with python3.7-dbg: ... ..python3.7-dbg: /build/h5py-bLiaZi/h5py-2.9.0/h5py/h5fd.c:19007: __Pyx_PyCFunction_FastCall: Assertion `!PyErr_Occurred()' failed. bash: line 1: 1153 Aborted $py-dbg -c "import h5py; h5py.run_tests()" autopkgtest [16:54:50]: test command2: ---] autopkgtest [16:54:50]: test command2: - - - - - - - - - - results - - - - - - - - - - command2 FAIL non-zero exit status 134 Regards Graham [1] https://ci.debian.net/packages/h/h5py/unstable/amd64/
Bug#922306: linux: btrfs corruption (compressed data + hole data)
Control: found -1 4.3~rc5-1~exp1 Control: tags -1 + upstream patch Upstream patch submission at https://lore.kernel.org/linux-btrfs/20190214151720.23563-1-fdman...@kernel.org/ Regards, Salvatore
Processed: Re: Bug#922306: linux: btrfs corruption (compressed data + hole data)
Processing control commands: > found -1 4.3~rc5-1~exp1 Bug #922306 [src:linux] linux: btrfs corruption (compressed data + hole data) Ignoring request to alter found versions of bug #922306 to the same values previously set > tags -1 + upstream patch Bug #922306 [src:linux] linux: btrfs corruption (compressed data + hole data) Ignoring request to alter tags of bug #922306 to the same tags previously set -- 922306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922306 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#922306: linux: btrfs corruption (compressed data + hole data)
Processing control commands: > found -1 4.3~rc5-1~exp1 Bug #922306 [src:linux] linux: btrfs corruption (compressed data + hole data) Marked as found in versions linux/4.3~rc5-1~exp1. > tags -1 + upstream patch Bug #922306 [src:linux] linux: btrfs corruption (compressed data + hole data) Ignoring request to alter tags of bug #922306 to the same tags previously set -- 922306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922306 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#831835: "Survey regarding your Extension bcma for Mozilla Firefox"
If this is not a spam and you are serious, please repost it to https://notabug.org/themusicgod1/cloudflare-tor/ thanks
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 831835 + jessie stretch Bug #831835 [iceweasel] iceweasel: Padlock icon indicates a secure SSL connection established w MitM-ed Added tag(s) jessie and stretch. > thanks Stopping processing here. Please contact me if you need assistance. -- 831835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921488: Bug #921488 in mariadb-10.3 marked as pending
Control: tag -1 pending Hello, Bug #921488 in mariadb-10.3 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/mariadb-team/mariadb-10.3/commit/21008f9fdfe0f13a360c61034ead65d3ae144606 Use bundled SSL libraries instead of system OpenSSL (Closes: #921488) It has been disputed whether MySQL and MariaDB can license-wise use OpenSSL or not. Building with '-DWITH_SSL=bundled' makes the server use YaSSL and the Connector/C use GnuTLS. Once OpenSSL 3.0 is released, switch back to it. Since OpenSSL is missing, libmariadb3 will lack the sha256_password plugin. (this message was generated automatically) -- Greetings https://bugs.debian.org/921488
Processed: Bug #921488 in mariadb-10.3 marked as pending
Processing control commands: > tag -1 pending Bug #921488 [libmariadb3] libmariadb3: OpenSSL license contamination of GPL reverse-dependencies Ignoring request to alter tags of bug #921488 to the same tags previously set -- 921488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#780323: marked as done (/bin/cp: cp: *deletes* files' contents with --attributes-only option)
Your message dated Sun, 24 Feb 2019 09:57:00 + with message-id and subject line Re: coreutils RC bugs not properly closed has caused the Debian Bug report #780323, regarding /bin/cp: cp: *deletes* files' contents with --attributes-only option 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.) -- 780323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: coreutils Version: 8.13-3.5 Severity: critical File: /bin/cp Justification: causes serious data loss creating two files, identical names, different dates. after executing cp --attributes-only second file has no data. cp shouldn't delete anything, just copy. debian stable shouldn't have this issue. it's fixed in 8.17, there is no backport to stable since May 2012. yavor@host:~$ cat > a data yavor@host:~$ mkdir b yavor@host:~$ touch -d "2015-01-01 00:00:00" a yavor@host:~$ cat > b/a data2 yavor@host:~$ cp --attributes-only a b/a yavor@host:~$ cat b/a yavor@host:~$ ls -la b/ total 8 drwxr-xr-x 2 yavor yavor 4096 Mar 12 04:51 . drwxr-xr-x 3 yavor yavor 4096 Mar 12 04:48 .. -rw-r--r-- 1 yavor yavor0 Mar 12 04:52 a -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages coreutils depends on: ii dpkg 1.16.15 ii install-info 4.13a.dfsg.1-10 ii libacl1 2.2.51-8 ii libattr1 1:2.4.46-8 ii libc6 2.13-38+deb7u8 ii libselinux1 2.1.9-5 coreutils recommends no packages. coreutils suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- On Wed, 2 Nov 2016 15:00:01 -0400 Sandro Tosi wrote: > Hello Michael, the bugs in the recipients list are not properly closed > (according to their version graph in the BTS) and so they still appear > unresolved - could you please fix their found/fixed versions? > > thanks, > -- > Sandro "morph" Tosi > My website: http://sandrotosi.me/ > Me at Debian: http://wiki.debian.org/SandroTosi > G+: https://plus.google.com/u/0/+SandroTosi > > Adding a missing -done. Thanks, ~Niels--- End Message ---
Bug#743955: marked as done (coreutils: corrupted files on heavily fragmented ext3 and ext4 partitions)
Your message dated Sun, 24 Feb 2019 09:57:00 + with message-id <1599e831-959d-d1a1-2319-15c0e6cce...@thykier.net> and subject line Re: coreutils RC bugs not properly closed has caused the Debian Bug report #743955, regarding coreutils: corrupted files on heavily fragmented ext3 and ext4 partitions 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.) -- 743955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: coreutils Version: 8.13-3.5 Severity: grave Dear Maintainer, this bug is described here: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12656 and can be summarized as follows: + cp could read from freed memory and could even make corrupt copies. + This could happen only with a very fragmented input file and when using + its FIEMAP/extent-based copying code. [bug introduced in coreutils-8.11] It is present in the wheezy coreutils version and is fixed in jessie/sid. A backport of the fix or an update of coreutils would be welcomed for wheezy. -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages coreutils depends on: ii dpkg 1.16.12 ii install-info 4.13a.dfsg.1-10 ii libacl1 2.2.51-8 ii libattr1 1:2.4.46-8 ii libc6 2.13-38+deb7u1 ii libselinux1 2.1.9-5 coreutils recommends no packages. coreutils suggests no packages. -- no debconf information -- Laurent. --- End Message --- --- Begin Message --- On Wed, 2 Nov 2016 15:00:01 -0400 Sandro Tosi wrote: > Hello Michael, the bugs in the recipients list are not properly closed > (according to their version graph in the BTS) and so they still appear > unresolved - could you please fix their found/fixed versions? > > thanks, > -- > Sandro "morph" Tosi > My website: http://sandrotosi.me/ > Me at Debian: http://wiki.debian.org/SandroTosi > G+: https://plus.google.com/u/0/+SandroTosi > > Adding a missing -done. Thanks, ~Niels--- End Message ---
Bug#921761: sssd: FTBFS (failing tests)
On Sun, Feb 24, 2019 at 12:35:02AM +0100, Dominik George wrote: > Fedora project seems to know how to fix this, but I cannot get my head > wrapped around how the hell you find out how they did it… > > https://bugzilla.redhat.com/show_bug.cgi?id=1645912 > > -nik The fix referenced in the RedHat bug tracker in krb5 is unrelated to this bug and does not fix it. signature.asc Description: PGP signature
Bug#923125: FTBFS: cannot find files in override_dh_install
Source: sssd Version: 1.16.3-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 After fixing #921761, sssd still fails to build in a clean chroot: dh_install dh_install: Cannot find (any matches for) "usr/lib/*/krb5/plugins/authdata/sssd_pac_plugin.so" (tried in ., debian/tmp) dh_install: sssd-common missing files: usr/lib/*/krb5/plugins/authdata/sssd_pac_plugin.so dh_install: Cannot find (any matches for) "usr/lib/*/sssd/sssd_pac" (tried in ., debian/tmp) dh_install: sssd-ad-common missing files: usr/lib/*/sssd/sssd_pac dh_install: missing files, aborting make[1]: *** [debian/rules:69: override_dh_install] Error 25 -BEGIN PGP SIGNATURE- iQKJBAEBCgBzFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlxybmQxGmh0dHBzOi8v d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYyMcZG9taW5p ay5nZW9yZ2VAaXQucGlyYXRlbnBhcnRlaS5kZQAKCRC3mjwWoMTyluqqEAC9fbLv L9q/zDG6XR/XobwSrT4YCJ7D1lEHV+N7RrgmMtWJfwoDa3GlJ6S2MS/IbgVyrFLt 44HsTUOsK7e4tr8oGUua81xPZV+29y8b4Uk09pMvtMyYrdoRFlO69hYI/8oa2pmH 9EY0usLY+fOtTw9jjr29yLEoNzDiHRik0XyjDoHqUjW/EWLwTRrRpjINVhGjHYUU UeVkVl2lKXxtpI62+Xp2PswfrhRMDRQ1CHiJBG1IgcHyMj8Nxhmd5JLq39P+cTgg Csbgfwp1v3JozQzUt9RDdUbp/UDx25psplhEw0ifqNeDWECQiu6h2NLcmloTsG4i pAER62c2xcsYQzt0RqYhr90OwLddgA1XV5YE/S1NSo4sBzhaWYN4FPUimPRe6MIF 9u+wrAEmI6KpFJXYMolc4CtX7lSr8my0Jd3T84Z9dQfz39AYEtlGrznEUzNXQNhF HnyjBOzgmG/HBTCXH4SVakG8NY5Z1heeE/UoadcCMi2ZRqPwsqT0f3s82xENoMNh TXVjvqRN271+xQxH/qXkbNrT3jqp6IF+kbFCRJLs8mVE4ZWkkZH1/pfcHX6e52Kw uR3ilfkdNsdoxL8jmxvWDUfPHG8aQjEt/4U/3ObDBCcwHcS9CnzwkcwXXkDX2niE XV25Ir+LJJ0FoiqychfN/sFmd6xxD/jRuzOCuA== =nTiW -END PGP SIGNATURE-
Bug#921761: sssd: FTBFS (failing tests)
Control: tag -1 + patch The releveant upstream fix is: https://github.com/SSSD/sssd/commit/08bba3a6e3e4e21f2e20b71cca463d50420aa9ee#diff-7adf0a00d9dca84b2fbdd1759c1ac2a6.patch With this patch applied, the test passes again. Unfortunately, sssd still does not build, maybe for some other incompatibility with krb5. I will upload sssd to DELAYED/2 once both are fixed. signature.asc Description: PGP signature
Bug#920000: NMU
user debian-rele...@lists.debian.org
usertag 92 + bsp-2019-02-de-bonn
tag 92 pending
thank you
Greetings from the BSP taking place at Teckids e.V./tarent solutions
GmbH in Bonn this weekend. I have applied Laurent's patch and uploaded
nacl/20110221-6.1 to DELAYED/2. Feel free to reschedule my upload as you
see fit. The debiff is attached to this mail.
On another note, the master branch at
https://salsa.debian.org/debian/nacl.git does not reflect the state of
the source package -- it contains extra files. You may want to fix that.
Cheers,
-Hilko
diff -Nru nacl-20110221/debian/changelog nacl-20110221/debian/changelog
--- nacl-20110221/debian/changelog 2018-10-23 15:04:30.0 +0200
+++ nacl-20110221/debian/changelog 2019-02-24 10:54:10.0 +0100
@@ -1,3 +1,11 @@
+nacl (20110221-6.1) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * Update patch to remove superfluous build flags, thanks to Laurent Bigonville
+(Closes: #92)
+
+ -- Hilko Bengen Sun, 24 Feb 2019 10:54:10 +0100
+
nacl (20110221-6) unstable; urgency=medium
[ Ondřej Nový ]
diff -Nru nacl-20110221/debian/patches/0002-remove-superfluous-compiler-flags.patch nacl-20110221/debian/patches/0002-remove-superfluous-compiler-flags.patch
--- nacl-20110221/debian/patches/0002-remove-superfluous-compiler-flags.patch 2018-10-22 08:10:48.0 +0200
+++ nacl-20110221/debian/patches/0002-remove-superfluous-compiler-flags.patch 2019-02-24 10:54:10.0 +0100
@@ -11,35 +11,32 @@
okcompilers/cpp | 9 +++--
2 files changed, 6 insertions(+), 12 deletions(-)
-diff --git a/okcompilers/c b/okcompilers/c
-index 7218da3..2667f82 100644
--- a/okcompilers/c
+++ b/okcompilers/c
-@@ -1,8 +1,5 @@
+@@ -1,8 +1 @@
-gcc -m64 -O3 -fomit-frame-pointer -funroll-loops
-gcc -m64 -O -fomit-frame-pointer
-gcc -m64 -fomit-frame-pointer
-gcc -m32 -O3 -fomit-frame-pointer -funroll-loops
-gcc -m32 -O -fomit-frame-pointer
-gcc -m32 -fomit-frame-pointer
-+gcc -O3 -fomit-frame-pointer -funroll-loops
-+gcc -O -fomit-frame-pointer
-+gcc -fomit-frame-pointer
- spu-gcc -mstdmain -march=cell -O3 -funroll-loops -fomit-frame-pointer -Drandom=rand -Dsrandom=srand
- spu-gcc -mstdmain -march=cell -O -fomit-frame-pointer -Drandom=rand -Dsrandom=srand
-diff --git a/okcompilers/cpp b/okcompilers/cpp
-index d1b9ae6..35304e4 100644
+-spu-gcc -mstdmain -march=cell -O3 -funroll-loops -fomit-frame-pointer -Drandom=rand -Dsrandom=srand
+-spu-gcc -mstdmain -march=cell -O -fomit-frame-pointer -Drandom=rand -Dsrandom=srand
++gcc ${CFLAGS}
--- a/okcompilers/cpp
+++ b/okcompilers/cpp
-@@ -1,8 +1,5 @@
+@@ -1,8 +1 @@
-g++ -m64 -O3 -fomit-frame-pointer -funroll-loops
-g++ -m64 -O -fomit-frame-pointer
-g++ -m64 -fomit-frame-pointer
-g++ -m32 -O3 -fomit-frame-pointer -funroll-loops
-g++ -m32 -O -fomit-frame-pointer
-g++ -m32 -fomit-frame-pointer
-+g++ -O3 -fomit-frame-pointer -funroll-loops
-+g++ -O -fomit-frame-pointer
-+g++ -fomit-frame-pointer
- spu-g++ -mstdmain -march=cell -O3 -funroll-loops -fomit-frame-pointer -Drandom=rand -Dsrandom=srand
- spu-g++ -mstdmain -march=cell -O -fomit-frame-pointer -Drandom=rand -Dsrandom=srand
+-spu-g++ -mstdmain -march=cell -O3 -funroll-loops -fomit-frame-pointer -Drandom=rand -Dsrandom=srand
+-spu-g++ -mstdmain -march=cell -O -fomit-frame-pointer -Drandom=rand -Dsrandom=srand
++g++ ${CFLAGS}
+--- a/okcompilers/archivers
b/okcompilers/archivers
+@@ -1,2 +1 @@
+ ar
+-ar -X64
diff -Nru nacl-20110221/debian/rules nacl-20110221/debian/rules
--- nacl-20110221/debian/rules 2018-10-22 08:11:09.0 +0200
+++ nacl-20110221/debian/rules 2019-02-24 10:54:10.0 +0100
@@ -2,6 +2,8 @@
#export DH_VERBOSE=1
+CFLAGS = $(shell dpkg-buildflags --get CFLAGS)
+
override_dh_auto_build:
# some quick tests for the status of /sys to help debug failures
-ls /sys
@@ -13,5 +15,15 @@
# DJB "makefile"-ish
./do
+override_dh_auto_configure:
+ [ -f okcompilers/c.orig ] || cp okcompilers/c okcompilers/c.orig
+ [ -f okcompilers/cpp.orig ] || cp okcompilers/cpp okcompilers/cpp.orig
+ sed -i 's|$${CFLAGS}|$(CFLAGS) -fPIC|g' okcompilers/c okcompilers/cpp
+
%:
dh $@
+
+override_dh_auto_clean:
+ mv -f okcompilers/c.orig okcompilers/c || true
+ mv -f okcompilers/cpp.orig okcompilers/cpp || true
+ dh_auto_clean
Processed: NMU
Processing commands for cont...@bugs.debian.org: > user debian-rele...@lists.debian.org Setting user to debian-rele...@lists.debian.org (was ben...@debian.org). > usertag 92 + bsp-2019-02-de-bonn There were no usertags set. Usertags are now: bsp-2019-02-de-bonn. > tag 92 pending Bug #92 [src:nacl] Please build nacl with -fPIC and use CFLAGS from dpkg-buildflags Added tag(s) pending. > thank you Stopping processing here. Please contact me if you need assistance. -- 92: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=92 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: sssd: FTBFS (failing tests)
Processing control commands: > tag -1 + patch Bug #921761 [src:sssd] sssd: FTBFS (failing tests) Added tag(s) patch. -- 921761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923125: FTBFS: cannot find files in override_dh_install
Control: tag -1 + pending Control: tag 921761 + pending This is due to the check for a matching Kerberos version explicitly checks all known good versions up to 1.16, but now we have 1.17 in Debian. I looked at the upstream changelog and found nothing that could break the plugin build. Addind 1.17 to the list of known good versions fixes sssd's build. Thus, I will upload to DELAYED/2 together with the patch for #921761. signature.asc Description: PGP signature
Processed: Re: FTBFS: cannot find files in override_dh_install
Processing control commands: > tag -1 + pending Bug #923125 [src:sssd] FTBFS: cannot find files in override_dh_install Added tag(s) pending. > tag 921761 + pending Bug #921761 [src:sssd] sssd: FTBFS (failing tests) Added tag(s) pending. -- 921761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921761 923125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921761: marked as done (sssd: FTBFS (failing tests))
Your message dated Sun, 24 Feb 2019 11:21:27 + with message-id and subject line Bug#921761: fixed in sssd 1.16.3-3.1 has caused the Debian Bug report #921761, regarding sssd: FTBFS (failing tests) 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.) -- 921761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sssd Version: 1.16.3-3 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch --with quilt,autoreconf,python2,python3,systemd \ --builddirectory=build dh_quilt_patch -a -O--builddirectory=build Applying patch fix-curl-ftbfs.diff patching file src/util/tev_curl.c Now at patch fix-curl-ftbfs.diff dh_update_autotools_config -a -O--builddirectory=build dh_autoreconf -a -O--builddirectory=build Creating directory build Copying file build/config.rpath Copying file build/mkinstalldirs Copying file po/Makevars.template [... snipped ...] 1 FAILED TEST(S) FAIL test_copy_ccache (exit status: 1) SKIP: src/tests/whitespace_test === Git repository is required for this test! SKIP src/tests/whitespace_test (exit status: 77) SKIP: src/tests/double_semicolon_test = Git repository is required for this test! SKIP src/tests/double_semicolon_test (exit status: 77) Testsuite summary for sssd 1.16.3 # TOTAL: 99 # PASS: 96 # SKIP: 2 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See ./test-suite.log Please report to sssd-de...@lists.fedorahosted.org make[6]: *** [Makefile:35425: test-suite.log] Error 1 make[6]: Leaving directory '/<>/build' make[5]: *** [Makefile:35533: check-TESTS] Error 2 make[5]: Leaving directory '/<>/build' make[4]: *** [Makefile:36409: check-am] Error 2 make[4]: Leaving directory '/<>/build' make[3]: *** [Makefile:35310: check-recursive] Error 1 make[3]: Leaving directory '/<>/build' make[2]: *** [Makefile:36411: check] Error 2 make[2]: Leaving directory '/<>/build' dh_auto_test: cd build && make -j1 check VERBOSE=1 VERBOSE=yes returned exit code 2 make[1]: *** [debian/rules:46: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:3: build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) The build was made in my autobuilder with "dpkg-buildpackage -B" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sssd.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: sssd Source-Version: 1.16.3-3.1 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominik George (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: Sun, 24 Feb 2019 11:05:55 +0100 Source: sssd Binary: libipa-hbac-dev libipa-hbac0 libipa-hbac0-dbgsym libnss-sss libnss-sss-dbgsym libpam-sss libpam-sss-dbgsym libsss-certmap-dev libsss-certmap0 libsss-certmap0-dbgsym libsss-idmap-dev libsss-idmap0 libsss-idmap0-dbgsym libsss-nss-idmap-dev libsss-nss-idmap0 libsss-nss-idmap0-dbgsym libsss-simpleifp-dev libsss-simpleifp0 libsss-simpleifp0-dbgsym libsss-sud
Bug#923125: marked as done (FTBFS: cannot find files in override_dh_install)
Your message dated Sun, 24 Feb 2019 11:21:27 + with message-id and subject line Bug#923125: fixed in sssd 1.16.3-3.1 has caused the Debian Bug report #923125, regarding FTBFS: cannot find files in override_dh_install 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.) -- 923125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sssd Version: 1.16.3-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 After fixing #921761, sssd still fails to build in a clean chroot: dh_install dh_install: Cannot find (any matches for) "usr/lib/*/krb5/plugins/authdata/sssd_pac_plugin.so" (tried in ., debian/tmp) dh_install: sssd-common missing files: usr/lib/*/krb5/plugins/authdata/sssd_pac_plugin.so dh_install: Cannot find (any matches for) "usr/lib/*/sssd/sssd_pac" (tried in ., debian/tmp) dh_install: sssd-ad-common missing files: usr/lib/*/sssd/sssd_pac dh_install: missing files, aborting make[1]: *** [debian/rules:69: override_dh_install] Error 25 -BEGIN PGP SIGNATURE- iQKJBAEBCgBzFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlxybmQxGmh0dHBzOi8v d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYyMcZG9taW5p ay5nZW9yZ2VAaXQucGlyYXRlbnBhcnRlaS5kZQAKCRC3mjwWoMTyluqqEAC9fbLv L9q/zDG6XR/XobwSrT4YCJ7D1lEHV+N7RrgmMtWJfwoDa3GlJ6S2MS/IbgVyrFLt 44HsTUOsK7e4tr8oGUua81xPZV+29y8b4Uk09pMvtMyYrdoRFlO69hYI/8oa2pmH 9EY0usLY+fOtTw9jjr29yLEoNzDiHRik0XyjDoHqUjW/EWLwTRrRpjINVhGjHYUU UeVkVl2lKXxtpI62+Xp2PswfrhRMDRQ1CHiJBG1IgcHyMj8Nxhmd5JLq39P+cTgg Csbgfwp1v3JozQzUt9RDdUbp/UDx25psplhEw0ifqNeDWECQiu6h2NLcmloTsG4i pAER62c2xcsYQzt0RqYhr90OwLddgA1XV5YE/S1NSo4sBzhaWYN4FPUimPRe6MIF 9u+wrAEmI6KpFJXYMolc4CtX7lSr8my0Jd3T84Z9dQfz39AYEtlGrznEUzNXQNhF HnyjBOzgmG/HBTCXH4SVakG8NY5Z1heeE/UoadcCMi2ZRqPwsqT0f3s82xENoMNh TXVjvqRN271+xQxH/qXkbNrT3jqp6IF+kbFCRJLs8mVE4ZWkkZH1/pfcHX6e52Kw uR3ilfkdNsdoxL8jmxvWDUfPHG8aQjEt/4U/3ObDBCcwHcS9CnzwkcwXXkDX2niE XV25Ir+LJJ0FoiqychfN/sFmd6xxD/jRuzOCuA== =nTiW -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: sssd Source-Version: 1.16.3-3.1 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 923...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominik George (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: Sun, 24 Feb 2019 11:05:55 +0100 Source: sssd Binary: libipa-hbac-dev libipa-hbac0 libipa-hbac0-dbgsym libnss-sss libnss-sss-dbgsym libpam-sss libpam-sss-dbgsym libsss-certmap-dev libsss-certmap0 libsss-certmap0-dbgsym libsss-idmap-dev libsss-idmap0 libsss-idmap0-dbgsym libsss-nss-idmap-dev libsss-nss-idmap0 libsss-nss-idmap0-dbgsym libsss-simpleifp-dev libsss-simpleifp0 libsss-simpleifp0-dbgsym libsss-sudo libsss-sudo-dbgsym libwbclient-sssd libwbclient-sssd-dbgsym libwbclient-sssd-dev python-libipa-hbac python-libipa-hbac-dbgsym python-libsss-nss-idmap python-libsss-nss-idmap-dbgsym python-sss python-sss-dbgsym python3-libipa-hbac python3-libipa-hbac-dbgsym python3-libsss-nss-idmap python3-libsss-nss-idmap-dbgsym python3-sss python3-sss-dbgsym sssd sssd-ad sssd-ad-common sssd-ad-common-dbgsym sssd-ad-dbgsym sssd-common sssd-common-dbgsym sssd-dbus sssd-dbus-dbgsym sssd-ipa sssd-ipa-dbgsym sssd-kcm sssd-kcm-dbgsym sssd-krb5 sssd-krb5-common sssd-krb5-common-dbgsym sssd-krb5-dbgsym sssd-ldap sssd-ldap-dbgsym sssd-proxy sssd-proxy-dbgsym sssd-tools sssd-tools-dbgsym Architecture: source amd64 Version: 1.16.3-3.1 Distribution: unstable Urgency: high Maintainer: Debian SSSD Team Changed-By: Dominik George Description: libipa-hbac-dev - FreeIPA HBAC Evaluator library -- development files libipa-hbac0 - FreeIPA HBAC Evaluator library libnss-sss - Nss library for the System Security Services Daemon libpam-sss - Pam module for the System Security Services Daemon libsss-certmap-dev - Certificate mapping library for SSSD -- development files libsss-certmap0 - Certificate mapping library for SSSD
Bug#916702: marked as done (freezegun FTBFS: test failures)
Your message dated Sun, 24 Feb 2019 11:19:44 +
with message-id
and subject line Bug#916702: fixed in freezegun 0.3.11-0.1
has caused the Debian Bug report #916702,
regarding freezegun FTBFS: test failures
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.)
--
916702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freezegun
Version: 0.3.10-2
Severity: serious
Tags: ftbfs
Some recent change in unstable makes freezegun FTBFS:
https://tests.reproducible-builds.org/debian/history/freezegun.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/freezegun.html
...
debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/freezegun-0.3.10'
pyversions: missing X(S)-Python-Version in control file, fall back to
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
for python in python2.7; do \
$python /usr/bin/nosetests tests; \
done
SS..S
NameStmts Miss Cover Missing
-
freezegun/__init__.py 8 0 100%
freezegun/api.py 422 2893% 30-31, 35-36, 40-41, 45, 50,
72-73, 89, 158, 406, 443, 554, 556, 563-565, 581, 587, 604-605, 633-635, 654-657
-
TOTAL 430 2893%
--
Ran 93 tests in 2.412s
OK (SKIP=3)
for python in python3.6 python3.7; do \
$python /usr/bin/nosetests tests; \
done
...S.
NameStmts Miss Cover Missing
-
freezegun/__init__.py 8 0 100%
freezegun/_async.py11 191% 12
freezegun/api.py 422 2195% 30-31, 35-36, 50, 72-73, 89, 158,
443, 554, 556, 563-565, 587, 633-635, 654-657
-
TOTAL 441 2295%
--
Ran 93 tests in 1.868s
OK (SKIP=1)
...S.FF..
==
FAIL: Test that we can go back in time after setting a future date.
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
File "/build/1st/freezegun-0.3.10/tests/test_uuid.py", line 28, in
test_uuid1_future
assert_equal(time_from_uuid(uuid.uuid1()), future_target)
AssertionError: FakeDatetime(2020, 1, 19, 23, 8, 44, 720600) !=
datetime.datetime(2056, 2, 6, 14, 3, 21)
'FakeDatetime(2020, 1, 19, 23, 8, 44, 720600) != datetime.datetime(2056, 2,
6, 14, 3, 21)' = '%s != %s' % _common_shorten_repr(FakeDatetime(2020, 1, 19,
23, 8, 44, 720600), datetime.datetime(2056, 2, 6, 14, 3, 21))
'FakeDatetime(2020, 1, 19, 23, 8, 44, 720600) != datetime.datetime(2056, 2,
6, 14, 3, 21)' = self._formatMessage('FakeDatetime(2020, 1, 19, 23, 8, 44,
720600) != datetime.datetime(2056, 2, 6, 14, 3, 21)', 'FakeDatetime(2020, 1,
19, 23, 8, 44, 720600) != datetime.datetime(2056, 2, 6, 14, 3, 21)')
>> raise self.failureException('FakeDatetime(2020, 1, 19, 23, 8, 44, 720600)
>> != datetime.datetime(2056, 2, 6, 14, 3, 21)')
==
FAIL: Test that we can go forward in time after setting some time in the past.
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
File "/build/1st/freezegun-0.3.10/tests/test_uuid.py", line 42, in
test_uuid1_past
assert_equal(time_from_uuid(uuid.uuid1()), past_target)
AssertionError: FakeDatetime(2020, 1, 19, 23, 8, 44, 748940) !=
datetime.datetime(1978, 7, 6, 23, 6, 31)
'FakeDatetime(2020, 1, 19, 23, 8, 44, 748940) != datetime.datetime(1978, 7,
6, 23, 6, 31)' = '%s != %s' % _common_shorten_repr(FakeDatetime(2020, 1, 19,
23, 8, 44, 748940), datetime.datetime(1978, 7, 6, 23, 6, 31))
Bug#922404: marked as done (freeipmi install fails)
Your message dated Sun, 24 Feb 2019 11:19:34 + with message-id and subject line Bug#922404: fixed in freeipmi 1.6.3-1.1 has caused the Debian Bug report #922404, regarding freeipmi install fails 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.) -- 922404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: freeipmi Version: 1.6.3-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? installing freeipmi * What exactly did you do (or not do) that was effective (or ineffective)? apt install freeipmi * What was the outcome of this action? postinstall failed: Setting up freeipmi-ipmidetect (1.6.3-1) ... Job for ipmidetectd.service failed because the control process exited with error code. See "systemctl status ipmidetectd.service" and "journalctl -xe" for details. invoke-rc.d: initscript ipmidetectd, action "start" failed. ● ipmidetectd.service - IPMI Node Detection Monitoring Daemon Loaded: loaded (/lib/systemd/system/ipmidetectd.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2019-02-15 14:06:15 UTC; 5ms ago Process: 966 ExecStart=/usr/sbin/ipmidetectd $OPTIONS (code=exited, status=1/FAILURE) Feb 15 14:06:15 tester systemd[1]: Starting IPMI Node Detection Monitoring Daemon... Feb 15 14:06:15 tester ipmidetectd[966]: ipmidetectd: No nodes configured Feb 15 14:06:15 tester systemd[1]: ipmidetectd.service: Control process exited, code=exited, status=1/FAILURE Feb 15 14:06:15 tester systemd[1]: ipmidetectd.service: Failed with result 'exit-code'. Feb 15 14:06:15 tester systemd[1]: Failed to start IPMI Node Detection Monitoring Daemon. dpkg: error processing package freeipmi-ipmidetect (--configure): installed freeipmi-ipmidetect package post-installation script subprocess returned error exit status 1 * What outcome did you expect instead? I expected postinstall to succeed *** End of the template - remove these template lines *** Note: This bug is also reported on launchpad: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1808637 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-45-generic (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages freeipmi depends on: ii freeipmi-bmc-watchdog 1.6.3-1 ii freeipmi-common1.6.3-1 ih freeipmi-ipmidetect1.6.3-1 ii freeipmi-tools 1.6.3-1 freeipmi recommends no packages. freeipmi suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: freeipmi Source-Version: 1.6.3-1.1 We believe that the bug you reported is fixed in the latest version of freeipmi, 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 922...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominik George (supplier of updated freeipmi 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, 23 Feb 2019 14:06:54 +0100 Source: freeipmi Binary: freeipmi freeipmi-bmc-watchdog freeipmi-bmc-watchdog-dbgsym freeipmi-common freeipmi-ipmidetect freeipmi-ipmidetect-dbgsym freeipmi-ipmiseld freeipmi-ipmiseld-dbgsym freeipmi-tools freeipmi-tools-dbgsym libfreeipmi-dev libfreeipmi17 libfreeipmi17-dbgsym libipmiconsole-dev libipmiconsole2 libipmiconsole2-dbgsym libipmidetect-dev libipmidetect0 libipmidetect0-dbgsym libipmimonitoring-dev libipmimonitoring6 libipmimonitoring6-dbgsym Architecture: source amd64 all Version: 1.6.3-1.1 Distribution: unstable Urgency: high Maintainer: Bernd Zeimetz Changed-By: Dominik George Description: freeipmi - GNU implementation of the IPMI protocol freeipmi-bmc-watchdog - GNU implementation of the IPMI protocol - BMC watchdog freeipmi-common - GNU implementation of the IPMI p
Bug#917216: Bug has been fixed
user debian-rele...@lists.debian.org usertag 917216 + bsp-2019-02-de-bonn fixed 917216 python-apt 1.8.1 thank you Greetings from the BSP taking place at Teckids e.V./tarent solutions GmbH in Bonn this weekend. This bug can be closed as the fix was added before python-apt/1.8.1 by yourself: , | commit 0e8f51100ceff26c6af93f5070671ee602996bf8 | Author: Julian Andres Klode | Date: Fri Jan 25 17:30:33 2019 +0100 ` Cheers, -Hilko
Processed: Bug #899907 in libvorbisidec marked as pending
Processing control commands: > tag -1 pending Bug #899907 [src:libvorbisidec] libvorbisidec: Invalid maintainer address pkg-xiph-ma...@lists.alioth.debian.org Added tag(s) pending. -- 899907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#899907: Bug #899907 in libvorbisidec marked as pending
Control: tag -1 pending Hello, Bug #899907 in libvorbisidec 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/multimedia-team/libvorbisidec/commit/1574df22367eef079822ae8910f437513fd88811 Set Maintainer address to Debian Multimedia Maintainers (closes: #899907) (this message was generated automatically) -- Greetings https://bugs.debian.org/899907
Bug#918164: Broken with Thunderbird 60
Hi everyone, On Sat, 23 Feb 2019 12:16:37 +0100 Carsten Schoenert wrote: > On Thu, Jan 03, 2019 at 11:21:19PM +0100, Moritz Muehlenhoff wrote: > > The plugin is broken with Thunderbird 60 in stretch and sid, after > > installation it's disabled and only prints "Timeline is > > incompatible with Thunderbird 60.4". ... > currently the package xul-ext-timeline is useless as it isn't usable > in any release of Debian any more. > ... > We should remove this package completely from the Debian archives. I agree that the package should be removed. Therefore i filed a removal bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923141 Thanks for taking care of security and Thunderbird! :-) Best wishes, Matthias pgpuzIivO4yC1.pgp Description: Digitale Signatur von OpenPGP
Bug#920823: phpmyadmin: CVE-2019-6799: PMASA-2019-1
Hi, FYI I prepared a patch for jessie, see: https://lists.debian.org/debian-lts/2019/02/msg00164.html For stretch, it is worth noting that the fix depends on whether mysql or mysqli is enabled, whether open_basedir is in effect, and whether we're protecting against user SQL queries or phpmyadmin-generated queries (during CSV import). (but no more phpX-mysql vs. phpX-mysqlnd AFAICS.) Cheers! Sylvain
Processed: let's try that again
Processing commands for cont...@bugs.debian.org: > found 917216 1.8.0 Bug #917216 [python-apt] python-apt FTBFS against apt/1.8.0~alpha3 There is no source info for the package 'python-apt' at version '1.8.0' with architecture '' Unable to make a source version for version '1.8.0' Marked as found in versions 1.8.0. > fixed 917216 1.8.1 Bug #917216 [python-apt] python-apt FTBFS against apt/1.8.0~alpha3 Marked as fixed in versions python-apt/1.8.1. > thank you Stopping processing here. Please contact me if you need assistance. -- 917216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Some diagnosis
Processing commands for cont...@bugs.debian.org: > user debian-rele...@lists.debian.org Setting user to debian-rele...@lists.debian.org (was ben...@debian.org). > usertag 915319 + bsp-2019-02-de-bonn There were no usertags set. Usertags are now: bsp-2019-02-de-bonn. > tag 915319 + confirmed Bug #915319 [src:kde-runtime] kde-runtime FTBFS with samba 4.9 Added tag(s) confirmed. > thank you Stopping processing here. Please contact me if you need assistance. -- 915319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915319: Some diagnosis
user debian-rele...@lists.debian.org
usertag 915319 + bsp-2019-02-de-bonn
tag 915319 + confirmed
thank you
Greetings from the BSP taking place at Teckids e.V./tarent
solutions GmbH in Bonn this weekend.
I have been able to confirm the symptom: The CMake-based build system is
unable to find the smbclient functions it needs:
,
| -- Checking for module 'smbclient'
| -- Found smbclient, version 0.4.0
| -- Looking for smbc_set_context
| -- Looking for smbc_set_context - not found
| -- Looking for smbc_option_set
| -- Looking for smbc_option_set - not found
`
I don't yet know how to debug this further, but it seems to me that the
detection code in /usr/share/kde4/apps/cmake/modules/FindSamba.cmake
somehow fails:
,
|set(CMAKE_REQUIRED_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES}
${SAMBA_LIBRARIES})
|set(CMAKE_REQUIRED_INCLUDES ${CMAKE_REQUIRED_INCLUDES}
${SAMBA_INCLUDE_DIR})
|check_symbol_exists(smbc_set_context "libsmbclient.h"
SAMBA_HAVE_SMBC_SET_CONTEXT)
|check_symbol_exists(smbc_option_set "libsmbclient.h"
SAMBA_HAVE_SMBC_OPTION_SET)
`
The file /usr/include/samba-4.0/libsmbclient.h clearly contains both
symbols.
Cheers,
-Hilko
Processed: closing 917216
Processing commands for cont...@bugs.debian.org: > close 917216 Bug #917216 [python-apt] python-apt FTBFS against apt/1.8.0~alpha3 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 917216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?
Hi,
On Sat, 02 Feb 2019 15:38:01 +0100 Didier 'OdyX' Raboud wrote:
> Gunnar and myself have started working on a draft, the latest version of
> which is available at
>
>
> https://salsa.debian.org/debian/tech-ctte/blob/master/914897_merged_usr/ballot.md
I found that some important arguments are still missing. A recent mail by
Guillem [1] nicely summarizes also many of my own thoughts. I'm going to paste
the relevant content into this mail for convenience of the reader:
[1] https://lists.debian.org/20190219044924.gb21...@gaara.hadrons.org
Quoting Guillem Jover (2019-02-19 05:49:24)
> The underlaying problem with the merged-/usr-via-symlinks is not
> really that it has generated bugs, many transitions we perform incur
> those, for the better. The problem is that it has generated those when
> it was really not necessary in the first place, has made things
> unnecessarily more complicated for everyone, and it's a terrible hack
> trying to reap "quick" benefits at the cost of everyhing else, with
> long lasting consequences even after a full migration to /usr would
> have been finished. And here's why:
>
> 1) The merged-/usr-via-symlinks deployment method used by both
>debootstrap and usrmerge, means that those systems will get
>permanent filesystem aliasing problems, forever. Even when all
>files might have been moved to their /usr counterparts in the
>packages! This is due to the fact that different pathnames can
>end up pointing (before any canonicalization!) to the same dentry.
>
>This does not only affect dpkg (dpkg, dpkg-divert, dpkg-trigger,
>etc), and update-alternatives (in a worse way), but any program
>that uses pathanmes in the filesystem as keys in databases f.ex.
>
> 2) It bypasses the packaging system understanding of what is on the
>filesystem and creates mismatches between what's on binary packages
>and what's on disk.
>
> 3) Switching packages to the merged-/usr layout could have been
>accomplished automatically via debhelper for a coverage of around
>99% (?) of the archive. With something along the lines of:
>
> ,---
> D=debian/tmp
> for d in /bin /sbin /lib; do
>for p in $(find $D/$d ! -type d); do
> b="${p##$D/}"
> m="$D/usr$b"
> if [ ! -e "$m" ]; then
>mkdir -p "$(dirname $m)"
>mv "$p" "$m"
>ln -s "${m##$D}" "$p"
> fi
>done
> done
> `---
>
>With the property that it would handle gracefully all cases were the
>maintainer has checked that no compat symlinks are required and has
>then progressively moved the pathname installation to their final
>destination under /usr.
>
> 4) Due to having to support the broken merged-/usr-via-symlinks
>deployment, when we want to move the contents of the binary
>packages to the merged-/usr layout, we require now to include tons
>of logic in (probably new) maintainer scripts, when we have been
>trying to remove them altogether. :( With even more files untracked
>by dpkg itself, bypassing the packaging system even more, when the
>compat symlinks could have been shipped in the binary packages.
>
> 5) Most new installations will not even benefit from this hacky and
>rushed deployment, as long as they do not use a separate parition
>for /usr!
>
> 6) The merged-/usr-via-symlinks deployment hack is irreversible right
>now.
Just like Guillem, I'm personally not against merged-/usr but against how we
implement it. In addition to Guillems arguments, I also want to make another.
With how merged-/usr is getting deployed via debootstrap, we are placing more
of the instructions of how a Debian system is supposed to be setup *outside* of
the packages themselves (and into debootstrap). It would make a cleaner design
if we could have all necessary definitions of how to create a Debian chroot
from scratch (on a Debian system) in the packages *themselves* instead of
requiring code around the packages that is doing some magic setup (usually
debootstrap). With mmdebstrap I am trying to write a POC to show that it is
possible to set up a Debian chroot with only very little magic and the help of
apt. My goal is to move the remaining magic setup that is currently required
into apt and dpkg (the respective maintainers are in favor of that plan but I'm
waiting for the buster release). If merged-/usr is getting implemented in the
way as it is done by debootstrap, then every debootstrap-like program has to
reproduce these mechanisms which are already architecture specific and thus not
trivial to maintain over time. It would be more elegant if the way merged-/usr
is being deployed is being encoded in the packages themselves so that we can
further *reduce* the amount of code that needs to live outside of packages
until we eventually need zero setup code before debootstrap-like programs can
install binary packages into a chroot. If we decide to deploy mer
Bug#921030: marked as done (Fails to import the ansible module since its migration to Python 3)
Your message dated Sun, 24 Feb 2019 13:19:04 + with message-id and subject line Bug#921030: fixed in ansible-lint 4.1.0+dfsg.1-1 has caused the Debian Bug report #921030, regarding Fails to import the ansible module since its migration to Python 3 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.) -- 921030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921030 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ansible-lint Version: 3.4.20+git.20180203-1 Severity: grave Tags: sid Dear maintainer, Running ansible-lint with the current ansible version in sid results in an ImportError for the ansible Python 2 module. The ansible maintainers have migrated the ansible module to Python 3 so I expect this migration also needs to happen with ansible-lint. This will also affect testing as soon as ansible migrates, which AFAICT should happen tomorrow. Thanks for your work! -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ansible-lint depends on: ii ansible 2.7.6+dfsg-1 ii python 2.7.15-4 ii python-six 1.12.0-1 ii python-yaml 3.13-2 ansible-lint recommends no packages. ansible-lint suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: ansible-lint Source-Version: 4.1.0+dfsg.1-1 We believe that the bug you reported is fixed in the latest version of ansible-lint, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Henrique (supplier of updated ansible-lint package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 24 Feb 2019 12:30:38 + Source: ansible-lint Architecture: source Version: 4.1.0+dfsg.1-1 Distribution: unstable Urgency: medium Maintainer: Gregory Colpart Changed-By: Samuel Henrique Closes: 918783 921030 Changes: ansible-lint (4.1.0+dfsg.1-1) unstable; urgency=medium . * New upstream version 4.1.0+dfsg.1 (closes: #918783) - dfsg.1: Remove docs dir, which contains non-free code and we don't use any of it anyway. * Use python3 instead of python2 (closes: #921030) * Bump DH level to 12 * Bump Standards-Version to 4.3.0 * Add myself as an uploader * Move packaging to salsa * Add autopkgtests * d/docs: update docs of new release * d/control: add new build dependencies of latest release * d/copyright: update all entries * d/p/disable_scm_version.patch: new patch to disable usage of pypi * d/rules: use pybuild instead of distutils * d/watch: create file and point to GitHub * wrap-and-sort -a Checksums-Sha1: f326f73eaca4699eb23069c56bfb3029ab8b109c 2108 ansible-lint_4.1.0+dfsg.1-1.dsc 57194f4a58bed300d5bf855c74474909c445f10f 58931 ansible-lint_4.1.0+dfsg.1.orig.tar.gz 4cccb73b0ac5f4986a26c96f542709622acd0311 5772 ansible-lint_4.1.0+dfsg.1-1.debian.tar.xz 799c59c8b0fcc449689c53b17e9ed28a4d0bbee1 7075 ansible-lint_4.1.0+dfsg.1-1_amd64.buildinfo Checksums-Sha256: e8b410c5599d6552bdea37ddc1a05a9a2265fca2319d719496f14951ddac24c2 2108 ansible-lint_4.1.0+dfsg.1-1.dsc e7a87066336338c2767922a6314277bc332cabcbcbf34dd544cb3f43a8e176b3 58931 ansible-lint_4.1.0+dfsg.1.orig.tar.gz 3c588e1b09572c1dbbd38346da35797f865140608b5410f77fa2b68af26fe51f 5772 ansible-lint_4.1.0+dfsg.1-1.debian.tar.xz fc6c837d1fdb629146f90ee1579d4e1b02898fc8ce8ec59e40c788103e885b06 7075 ansible-lint_4.1.0+dfsg.1-1_amd64.buildinfo Files: ba7bfb4933242e2bf92cfac211004c76 2108 misc optional ansible-lint_4.1.0+dfsg.1-1.dsc e5745d53d5b0568a7597070b72527d9a 58931 misc optional ansible-lint_4.1.0+dfsg.1.orig.tar.gz 7c9d63aa39f299d97edac1fc30f91172 5772 misc optional ansible-lint_4.1.0+dfsg.1-1.debian.tar.xz f36392a1562bd
Bug#921296: marked as done (ccfits: FTBFS with upcoming doxygen 1.8.15)
Your message dated Sun, 24 Feb 2019 14:19:13 +0100 with message-id <20190224131913.ga11...@aurel32.net> and subject line Re: Bug#921296: ccfits: FTBFS with upcoming doxygen 1.8.15 has caused the Debian Bug report #921296, regarding ccfits: FTBFS with upcoming doxygen 1.8.15 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.) -- 921296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921296 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ccfits Severity: serious Dear Maintainer, I tested your package against a draft package for doxygen 1.8.15: https://bugs.debian.org/919413 and it FTBFS with this error: make[2]: *** [Makefile:8: refman.pdf] Error 1 Paolo -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled ~ --- End Message --- --- Begin Message --- On 2019-02-11 06:29, Aurelien Jarno wrote: > On 2019-02-04 10:53, Aurelien Jarno wrote: > > On 2019-02-04 01:04, Paolo Greppi wrote: > > > Source: ccfits > > > Severity: serious > > > > > > Dear Maintainer, > > > > > > I tested your package against a draft package for doxygen 1.8.15: > > > https://bugs.debian.org/919413 > > > > > > and it FTBFS with this error: > > > make[2]: *** [Makefile:8: refman.pdf] Error 1 > > > > > > > That actually looks like a bug in doxygen. CCfits depends on > > doxygen-latex, which according to its description should provide > > everything needed: > > > > | Package: doxygen-latex > > | ... > > | Description-en: Documentation system for C, C++, Java, Python and other > > languages > > | Doxygen is a documentation system for C, C++, Java, Objective-C, Python, > > IDL > > | and to some extent PHP, C#, and D. It can generate an on-line class > > browser > > | (in HTML) and/or an off-line reference manual (in LaTeX) from a set of > > | documented source files. > > | . > > | This dependency package adds dependencies for all LaTeX packages required > > | to build documents using the default stylesheet. > > > > ccfits doesn't do anything fancy, it just generates the latex file using > > doxygen and then run pdflatex on it. If a dependency is missing for > > that, it should be added to doxygen-latex. > > > > ccfits is now marked for autoremoval. Sending this email to reset the > autoremoval while waiting for an answer. I don't think a new version of doxygen breaking many packages should be uploaded now that buster is in freeze period. Right now this bug will trigger the removal of ccfits while it builds fine with the current doxygen. In addition to that ccfits just uses doxygen in the standard way, that is calling "doxygen Doxyfile" to generate refman.tex and then calling "pdflatex refman". If it fails with a newer version of doxygen, it's a bug in doxygen, not in ccfits. I am therefore closing the bug. Please feel free to open a new one once the new doxygen version is ready to be uploaded and you can show that this is a bug in ccfits. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net--- End Message ---
Processed: Re: Bug#921176: redis-server service is failing to start in buster lxc container
Processing control commands: > reassign -1 lxc Bug #921176 [apparmor] redis-server inside lxc is failing to start when apparmor is enabled - apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=6706 comm="(s-server)" flags="rw, rslave" Bug reassigned from package 'apparmor' to 'lxc'. Ignoring request to alter found versions of bug #921176 to the same values previously set Ignoring request to alter fixed versions of bug #921176 to the same values previously set > severity -1 important Bug #921176 [lxc] redis-server inside lxc is failing to start when apparmor is enabled - apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=6706 comm="(s-server)" flags="rw, rslave" Severity set to 'important' from 'serious' -- 921176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921176: redis-server service is failing to start in buster lxc container
Control: reassign -1 lxc Control: severity -1 important Hi, Pirate Praveen: > In dmesg inside container (same error on the host as well), so it seems > apparmor is blocking it. > [14760.307180] audit: type=1400 audit(1549992481.311:156): > apparmor="DENIED" operation="mount" info="failed flags match" error=-13 > profile="lxc-container-default-cgns" name="/" pid=20531 > comm="(s-server)" flags="rw, rslave" The lxc-container-default-cgns profile is shipped by the lxc package ⇒ reassigning. This looks very much like LXC bug #916639 so please retry with: lxc 1:3.1.0+really3.0.3-3 or newer? If that's not sufficient, you might need to set these options for your container: lxc.apparmor.profile = generated lxc.apparmor.allow_nesting = 1 (On sid, these settings are in /etc/lxc/default.conf already but I'm not familiar with LXC and I don't know if they'll apply to pre-existing containers.) Thanks in advance! Also, I'm setting severity to non-RC as it would be unfortunate to block the migration to testing of… the very version that likely fixes this bug. Once it's clarified that this is #916639, I'll fix the metadata. Cheers, -- intrigeri
Bug#914632: uw-imap: CVE-2018-19518
lördag 23 februari 2019 kl. 15:26:25 CET skrev Salvatore Bonaccorso: > On Sun, Jan 13, 2019 at 06:24:36PM +0100, Magnus Holmgren wrote: > > söndag 13 januari 2019 kl. 08:31:28 CET skrev Salvatore Bonaccorso: > > > On Fri, Dec 28, 2018 at 10:22:53AM +0100, Moritz Mühlenhoff wrote: > > > > On Wed, Dec 26, 2018 at 05:20:40PM +0100, Magnus Holmgren wrote: > > > > > I'm wondering if anyone would complain if I'd disable RSH (SSH) > > > > > connections > > > > > altogether. > > > > > > > > Full ack, that seems like the most sensible fix. > > > > > > Any news on this approach, or did you spot any problem with that way? > > > > Here's my plan. Removing the RSHPATH define should disable the insecure > > code, I reckon. I just haven't been able to make gbp use my long PGP key > > id... > Any news on this? I thought I'd write a NEWS.Debian entry about disabling RSH, but then I realised it wouldn't be disabled completely, only by default; code using the library can still set rshpath by calling tcp_parameters(SET_RSHPATH, path). But maybe that's just fine. I also haven't got around to actually verifying that the patch works as intended. Perhaps wanting to run imapd via remote shell is so rare that there's no need to write a NEWS.Debian entry? -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#923001: error message on start
Control: severity -1 important On Sat, 23 Feb 2019 21:20:42 -0500 Michael Gilbert wrote: > control: severity -1 serious > > Increasing severity since policy 10.7.3 is violated: > > "Obsolete configuration files without local changes should be removed > by the package during upgrade." > > The file in /etc/chromium.d is obsolete. > > Best wishes, > Mike Should does not mean must but I intend to remove it anyway. Markus signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#923001: error message on start
Processing control commands: > severity -1 important Bug #923001 [chromium-ublock-origin] chromium: failed to load extension message on start Severity set to 'important' from 'serious' -- 923001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923013: [Pkg-xen-devel] Bug#923013: xen: FTBFS when built with dpkg-buildpackage -A
> All of this seems to be related to the dh-exec usage for putting files > in the xen-utils-common package with a different name. This is the first > time this package is using dh-exec. > > [...] > > Interestingly, 'etc/default/xencommons => /etc/default/xen' does not > result in a similar error? > > I also found this one, which seems to be related: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831786 > > Do you have an idea / suggestion how we can deal with this? Based on your analysis, maybe applying the patch below. After all, the "fail-missing" thing is just an extra protection which helps avoiding mistakes when installing things, but in this case it seems to be more troublesome than helpful. --- a/debian/rules +++ b/debian/rules @@ -307,8 +307,11 @@ override_dh_compress: # By default, files in debian/tmp which are not handled by anything # in rules are ignored. This makes them into errors. -override_dh_missing: - dh_missing --fail-missing +# +# Disabled because of Bug #831786 +# +# override_dh_missing: +# dh_missing --fail-missing # We are dropping the config file /etc/default/xen which appeared in Thanks.
Bug#921667: [pkg-apparmor] Bug#921667: lxc, lava-dev: lxc fails to install along lava-dev --install-recommends
Hi, Pierre-Elliott Bécue: Setting up lxc (1:3.1.0+really3.0.3-2) ... Warning from stdin (line 1): config file '/etc/apparmor/parser.conf' not found Cache read/write disabled: interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.) Warning: unable to find a suitable fs in /proc/mounts, is it mounted? Use --subdomainfs to override. dpkg: error processing package lxc (--configure): installed lxc package post-installation script subprocess returned error exit status 1 >> > See my staged commits. >> > >> > https://salsa.debian.org/lxc-team/lxc/commit/a0e6b5f26227236e44ab8ff4cee745228201bb7d typo: s/runn/run/ >> weirdy, if you first install apparmor, then install lxc in a separate >> apt invocaation, it works just fine. and, if you do `apt install -f` >> after the initial failure, it also works fine. > I think it's a matter of AppArmor doing some magic at the end via a > trigger. apparmor.postinst starts apparmor.service on package configuration; so far, that's pretty much standard; but then apparmor.service mounts securityfs if it was not mounted yet… and apparmor_parser uses securityfs to interact with the Linux kernel. lxc.postinst calls apparmor_parser. So if lxc is configured before apparmor, indeed the call to "apparmor_parser -r -W -T /etc/apparmor.d/lxc-containers" will fail. FTR dh-apparmor handles this situation by generating this postinst code snippet, which is equivalent to what lxc.postinst has, modulo different output: if aa-enabled --quiet 2>/dev/null; then apparmor_parser -r -T -W "$APP_PROFILE" || true fi This is clearly not ideal, because depending on package configuration ordering, some profiles may be loaded and some might not be. I've not thought much about this problem yet, but I suspect that for service packages such as LXC, handling this sort of things at the systemd unit level might give us more robust ordering than what we're currently doing via postinst. Food for thought :) Cheers, -- intrigeri
Bug#921757: Can't reproduce
user debian-rele...@lists.debian.org usertag 921757 + bsp-2019-02-de-bonn tag 921757 + unreproducible thank you Greetings from the BSP taking place at Teckids e.V./tarent solutions GmbH in Bonn this weekend. I have tried to reproduce the bug using an up-to-date sid-amd64 chroot but couldn't. My guess from the test script log is that qemu-img (from package qemu-utils) was missing in the build attempt. Cheers, -Hilko
Processed: Can't reproduce
Processing commands for cont...@bugs.debian.org: > user debian-rele...@lists.debian.org Setting user to debian-rele...@lists.debian.org (was ben...@debian.org). > usertag 921757 + bsp-2019-02-de-bonn There were no usertags set. Usertags are now: bsp-2019-02-de-bonn. > tag 921757 + unreproducible Bug #921757 [src:os-autoinst] os-autoinst: FTBFS (failing tests) Added tag(s) unreproducible. > thank you Stopping processing here. Please contact me if you need assistance. -- 921757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912122: linux-ftpd: diff for NMU 0.17-36.1
tags 912122 patch user debian-rele...@lists.debian.org usertags 912122 + bsp-2019-02-de-bonn thanks Dear maintainer, find attached the fix for linux-ftpd. This goes beyond the usual scope of an NMU but it seemed wise to brush up the entire build system so it is robust for any forseeable changes to the Debian toolchain. For a full explanation, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911154#44 Upload to DELAYED+3 will follow in a few hours, I'd like to give myself a moment to settle down, then ultimately revisit the changes done. Feel free to tell me if I should wait a little longer. Packaging could still take a lot of love. It might be an idea to drop linux-ftpd in favour of linux-ftpd-ssl, however linux-ftp has patches that might be worth preserving. Regards, Christoph diff -Nru linux-ftpd-0.17/debian/changelog linux-ftpd-0.17/debian/changelog --- linux-ftpd-0.17/debian/changelog2016-12-06 16:09:38.0 +0100 +++ linux-ftpd-0.17/debian/changelog2019-02-24 14:39:25.0 +0100 @@ -1,3 +1,10 @@ +linux-ftpd (0.17-36.1) unstable; urgency=high + + * Non-maintainer upload + * Use cmake as build system. Closes: #912122 + + -- Christoph Biedl Sun, 24 Feb 2019 14:39:25 +0100 + linux-ftpd (0.17-36) unstable; urgency=low * Step up to Standards version 3.9.8, no changes. diff -Nru linux-ftpd-0.17/debian/compat linux-ftpd-0.17/debian/compat --- linux-ftpd-0.17/debian/compat 2016-12-06 15:39:49.0 +0100 +++ linux-ftpd-0.17/debian/compat 2018-12-05 00:45:35.0 +0100 @@ -1 +1 @@ -9 +10 diff -Nru linux-ftpd-0.17/debian/control linux-ftpd-0.17/debian/control --- linux-ftpd-0.17/debian/control 2016-12-06 16:05:24.0 +0100 +++ linux-ftpd-0.17/debian/control 2018-12-05 00:45:35.0 +0100 @@ -3,7 +3,7 @@ Priority: extra Maintainer: Mats Erik Andersson Uploaders: Alberto Gonzalez Iniesta -Build-Depends: bison, debhelper (>= 9), libpam0g-dev | libpam-dev +Build-Depends: bison, debhelper (>= 10~), libpam0g-dev | libpam-dev, cmake Standards-Version: 3.9.8 Homepage: http://ftp.uk.linux.org/pub/linux/Networking/netkit/ diff -Nru linux-ftpd-0.17/debian/dirs linux-ftpd-0.17/debian/dirs --- linux-ftpd-0.17/debian/dirs 2016-12-06 15:39:49.0 +0100 +++ linux-ftpd-0.17/debian/dirs 1970-01-01 01:00:00.0 +0100 @@ -1,4 +0,0 @@ -etc/pam.d -usr/share/man/man5 -usr/share/man/man8 -usr/sbin diff -Nru linux-ftpd-0.17/debian/ftpd.install linux-ftpd-0.17/debian/ftpd.install --- linux-ftpd-0.17/debian/ftpd.install 1970-01-01 01:00:00.0 +0100 +++ linux-ftpd-0.17/debian/ftpd.install 2018-12-05 00:45:35.0 +0100 @@ -0,0 +1,4 @@ + +debian/ftpchrootetc/ +debian/ftpusers etc/ +debian/pam.d/ftpetc/pam.d/ diff -Nru linux-ftpd-0.17/debian/ftpd.manpages linux-ftpd-0.17/debian/ftpd.manpages --- linux-ftpd-0.17/debian/ftpd.manpages1970-01-01 01:00:00.0 +0100 +++ linux-ftpd-0.17/debian/ftpd.manpages2018-12-05 00:45:35.0 +0100 @@ -0,0 +1,2 @@ + +debian/ftpchroot.5 diff -Nru linux-ftpd-0.17/debian/patches/001-from_hamm.diff linux-ftpd-0.17/debian/patches/001-from_hamm.diff --- linux-ftpd-0.17/debian/patches/001-from_hamm.diff 2016-12-06 15:39:49.0 +0100 +++ linux-ftpd-0.17/debian/patches/001-from_hamm.diff 2018-12-05 00:45:35.0 +0100 @@ -4,8 +4,8 @@ and Rainer Weikusat Forwarded: no Last-Update: 2002-02-09 linux-ftpd-0.17.orig/ftpd/ftpcmd.y -+++ linux-ftpd-0.17/ftpd/ftpcmd.y +--- a/ftpd/ftpcmd.y b/ftpd/ftpcmd.y @@ -55,6 +55,7 @@ #include #include @@ -110,8 +110,8 @@ break; } default: reply(504, "SIZE not implemented for Type %c.", "?AEIL"[type]); linux-ftpd-0.17.orig/ftpd/ftpd.8 -+++ linux-ftpd-0.17/ftpd/ftpd.8 +--- a/ftpd/ftpd.8 b/ftpd/ftpd.8 @@ -67,7 +67,9 @@ .It Fl A Permit only anonymous ftp connections or accounts listed in @@ -145,8 +145,8 @@ .It Pa ~ftp/pub Make this directory mode 555 and owned by .Dq root . linux-ftpd-0.17.orig/ftpd/ftpd.c -+++ linux-ftpd-0.17/ftpd/ftpd.c +--- a/ftpd/ftpd.c b/ftpd/ftpd.c @@ -80,6 +80,7 @@ #include #include @@ -1059,8 +1059,8 @@ return (0); } } linux-ftpd-0.17.orig/ftpd/logwtmp.c -+++ linux-ftpd-0.17/ftpd/logwtmp.c +--- a/ftpd/logwtmp.c b/ftpd/logwtmp.c @@ -41,7 +41,6 @@ "$Id: logwtmp.c,v 1.5 1999/07/16 00:34:29 dholland Exp $"; @@ -1077,23 +1077,8 @@ #include "extern.h" static int fd = -1; linux-ftpd-0.17.orig/support/Makefile -+++ linux-ftpd-0.17/support/Makefile -@@ -1,6 +1,6 @@ - include ../MCONFIG - --OBJS=daemon.o setproctitle.o isexpired.o vis.o -+OBJS=setproctitle.o isexpired.o vis.o - - all: libsupport.a - -@@ -16,4 +16,3 @@ - rm -f *.o libsupport.a - - setproctitle.o: setproctitle.h --daemon.o: daemon.h linux-ftpd-0.17.orig/support/setproctitle.c -+++ linux-ftpd-0.17/support/setproctitle.c +--- a/support/setpro
Bug#912125: netkit-ftp: diff for NMU 0.17-34.1
tags 912125 patch
user debian-rele...@lists.debian.org
usertags 912125 + bsp-2019-02-de-bonn
thanks
Dear maintainer,
find attached the fix for netkit-ftp.
This goes beyond the usual scope of an NMU but it seemed wise to brush
up the entire build system so it is robust for any forseeable changes
to the Debian toolchain.
For a full explanation, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911154#44
Upload to DELAYED+3 will follow in a few hours, I'd like to give
myself a moment to settle down, then ultimately revisit the
changes done. Feel free to tell me if I should wait a little longer.
Packaging could still take a lot of love.
It might be an idea to drop netkit-ftp in favour of netkit-ftp-ssl,
however netkit-ftp has patches that might be worth preserving.
Regards,
Christoph
diff -Nru netkit-ftp-0.17/debian/changelog netkit-ftp-0.17/debian/changelog
--- netkit-ftp-0.17/debian/changelog2016-12-06 16:23:57.0 +0100
+++ netkit-ftp-0.17/debian/changelog2019-02-24 14:39:21.0 +0100
@@ -1,3 +1,10 @@
+netkit-ftp (0.17-34.1) unstable; urgency=high
+
+ * Non-maintainer upload
+ * Use cmake as build system. Closes: #912125
+
+ -- Christoph Biedl Sun, 24 Feb 2019
14:39:21 +0100
+
netkit-ftp (0.17-34) unstable; urgency=low
* Increase Standards to 3.9.8, no changes.
diff -Nru netkit-ftp-0.17/debian/compat netkit-ftp-0.17/debian/compat
--- netkit-ftp-0.17/debian/compat 2016-12-02 16:04:37.0 +0100
+++ netkit-ftp-0.17/debian/compat 2018-12-09 23:52:23.0 +0100
@@ -1 +1 @@
-9
+10
diff -Nru netkit-ftp-0.17/debian/control netkit-ftp-0.17/debian/control
--- netkit-ftp-0.17/debian/control 2016-12-02 16:24:22.0 +0100
+++ netkit-ftp-0.17/debian/control 2018-12-09 23:52:23.0 +0100
@@ -3,7 +3,7 @@
Priority: standard
Maintainer: Mats Erik Andersson
Uploaders: Alberto Gonzalez Iniesta
-Build-Depends: debhelper (>= 9), dpkg-dev (>= 1.15.7), libreadline-dev
+Build-Depends: debhelper (>= 10~), dpkg-dev (>= 1.15.7), libreadline-dev, cmake
Standards-Version: 3.9.8
Package: ftp
diff -Nru netkit-ftp-0.17/debian/dirs netkit-ftp-0.17/debian/dirs
--- netkit-ftp-0.17/debian/dirs 2016-12-02 16:04:37.0 +0100
+++ netkit-ftp-0.17/debian/dirs 1970-01-01 01:00:00.0 +0100
@@ -1,3 +0,0 @@
-usr/bin
-usr/share/man/man1
-usr/share/man/man5
diff -Nru netkit-ftp-0.17/debian/ftp.install netkit-ftp-0.17/debian/ftp.install
--- netkit-ftp-0.17/debian/ftp.install 1970-01-01 01:00:00.0 +0100
+++ netkit-ftp-0.17/debian/ftp.install 2018-12-09 23:52:23.0 +0100
@@ -0,0 +1,2 @@
+
+usr/bin/netkit-ftp
diff -Nru netkit-ftp-0.17/debian/ftp.manpages
netkit-ftp-0.17/debian/ftp.manpages
--- netkit-ftp-0.17/debian/ftp.manpages 1970-01-01 01:00:00.0 +0100
+++ netkit-ftp-0.17/debian/ftp.manpages 2018-12-09 23:52:23.0 +0100
@@ -0,0 +1,3 @@
+
+debian/tmp/usr/share/man/man1/netkit-ftp.1
+debian/tmp/usr/share/man/man5/netkit-netrc.5
diff -Nru netkit-ftp-0.17/debian/patches/010_patches_in_sarge.diff
netkit-ftp-0.17/debian/patches/010_patches_in_sarge.diff
--- netkit-ftp-0.17/debian/patches/010_patches_in_sarge.diff2016-12-02
16:04:37.0 +0100
+++ netkit-ftp-0.17/debian/patches/010_patches_in_sarge.diff2018-12-09
23:53:19.0 +0100
@@ -4,19 +4,8 @@
Author: Herbert Xu
Forwarded: no
Last-Update: 2003-06-29
netkit-ftp-0.17.orig/ftp/Makefile
-+++ netkit-ftp-0.17/ftp/Makefile
-@@ -8,7 +8,7 @@
- LIBS += -lreadline $(LIBTERMCAP)
- endif
-
--ftp: cmds.o cmdtab.o domacro.o ftp.o glob.o main.o ruserpass.o
-+ftp: cmds.o cmdtab.o domacro.o ftp.o main.o ruserpass.o
- $(CC) $(LDFLAGS) $^ $(LIBS) -o $@
-
- domacro.o ftp.o glob.o main.o ruserpass.o: ftp_var.h pathnames.h
netkit-ftp-0.17.orig/ftp/cmds.c
-+++ netkit-ftp-0.17/ftp/cmds.c
+--- a/ftp/cmds.c
b/ftp/cmds.c
@@ -50,6 +50,7 @@
#include
@@ -955,8 +944,8 @@
+#warning "Unix auto-mode code skipped"
+#endif /* unix */
+}
netkit-ftp-0.17.orig/ftp/cmds.h
-+++ netkit-ftp-0.17/ftp/cmds.h
+--- a/ftp/cmds.h
b/ftp/cmds.h
@@ -42,6 +42,7 @@
void makedir(int argc, char *argv[]);
void removedir(int argc, char *argv[]);
@@ -965,8 +954,8 @@
void account(int argc, char *argv[]);
void doproxy(int argc, char *argv[]);
void reset(void);
netkit-ftp-0.17.orig/ftp/cmdtab.c
-+++ netkit-ftp-0.17/ftp/cmdtab.c
+--- a/ftp/cmdtab.c
b/ftp/cmdtab.c
@@ -56,6 +56,7 @@
const char chmodhelp[] = "change file permissions of remote file";
const char connecthelp[] = "connect to remote ftp";
@@ -983,8 +972,8 @@
{ "sendport", porthelp, 0, 0, 0, NULL, setport, NULL },
{ "put",sendhelp, 1, 1, 1, put, NULL, NULL },
{ "pwd",pwdhelp,0, 1, 1, NULL, pwd, NULL },
netkit-ftp-0.17.orig/ftp/domacro.c
-+++ netkit-ftp-0.17/ftp/domacro.c
+--- a/ftp/domacro.c
b/ftp/domacro.c
@@ -40,9 +40,21 @@
#include
#include
@@ -1094,8 +1083,8 @@
}
+ line
Bug#912123: linux-ftpd-ssl: diff for NMU 0.17.36+0.3-2.1
tags 912123 patch user debian-rele...@lists.debian.org usertags 912123 + bsp-2019-02-de-bonn thanks Dear maintainer, find attached the fix for linux-ftpd-ssl. This goes beyond the usual scope of an NMU but it seemed wise to brush up the entire build system so it is robust for any forseeable changes to the Debian toolchain. For a full explanation, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911154#44 Upload to DELAYED+3 will follow in a few hours, I'd like to give myself a moment to settle down, then ultimately revisit the changes done. Feel free to tell me if I should wait a little longer. Packaging could still take a lot of love. It might be an idea to drop linux-ftp in favour of linux-ftpd-ssl, however linux-ftp hasd patches that might be worth preserving. Regards, Christoph diff -Nru linux-ftpd-ssl-0.17.36+0.3/debian/changelog linux-ftpd-ssl-0.17.36+0.3/debian/changelog --- linux-ftpd-ssl-0.17.36+0.3/debian/changelog 2017-01-24 15:35:15.0 +0100 +++ linux-ftpd-ssl-0.17.36+0.3/debian/changelog 2019-02-24 14:39:30.0 +0100 @@ -1,3 +1,10 @@ +linux-ftpd-ssl (0.17.36+0.3-2.1) unstable; urgency=high + + * Non-maintainer upload + * Use cmake as build system. Closes: #912123 + + -- Christoph Biedl Sun, 24 Feb 2019 14:39:30 +0100 + linux-ftpd-ssl (0.17.36+0.3-2) unstable; urgency=low * Adaption to libssl of recent version. diff -Nru linux-ftpd-ssl-0.17.36+0.3/debian/compat linux-ftpd-ssl-0.17.36+0.3/debian/compat --- linux-ftpd-ssl-0.17.36+0.3/debian/compat2016-12-25 23:06:11.0 +0100 +++ linux-ftpd-ssl-0.17.36+0.3/debian/compat2019-02-24 14:39:30.0 +0100 @@ -1 +1 @@ -9 +10 diff -Nru linux-ftpd-ssl-0.17.36+0.3/debian/control linux-ftpd-ssl-0.17.36+0.3/debian/control --- linux-ftpd-ssl-0.17.36+0.3/debian/control 2017-01-16 21:04:22.0 +0100 +++ linux-ftpd-ssl-0.17.36+0.3/debian/control 2019-02-24 14:39:30.0 +0100 @@ -3,7 +3,7 @@ Priority: extra Maintainer: Mats Erik Andersson Uploaders: Alberto Gonzalez Iniesta -Build-Depends: bison, debhelper (>= 9), libpam0g-dev | libpam-dev, libssl-dev | libssl1.0-dev +Build-Depends: bison, debhelper (>= 10~), libpam0g-dev | libpam-dev, libssl-dev | libssl1.0-dev, cmake Standards-Version: 3.9.8 Package: ftpd-ssl diff -Nru linux-ftpd-ssl-0.17.36+0.3/debian/dirs linux-ftpd-ssl-0.17.36+0.3/debian/dirs --- linux-ftpd-ssl-0.17.36+0.3/debian/dirs 2016-12-25 23:06:11.0 +0100 +++ linux-ftpd-ssl-0.17.36+0.3/debian/dirs 1970-01-01 01:00:00.0 +0100 @@ -1,5 +0,0 @@ -etc/pam.d -usr/share/man/man5 -usr/share/man/man8 -usr/sbin -etc/ftpd-ssl diff -Nru linux-ftpd-ssl-0.17.36+0.3/debian/ftpd-ssl.install linux-ftpd-ssl-0.17.36+0.3/debian/ftpd-ssl.install --- linux-ftpd-ssl-0.17.36+0.3/debian/ftpd-ssl.install 1970-01-01 01:00:00.0 +0100 +++ linux-ftpd-ssl-0.17.36+0.3/debian/ftpd-ssl.install 2019-02-24 14:39:30.0 +0100 @@ -0,0 +1,6 @@ + +debian/openssl.cnf etc/ftpd-ssl/ +debian/pam.d/ftpetc/pam.d/ + +debian/ftpchrootetc/ +debian/ftpusers etc/ diff -Nru linux-ftpd-ssl-0.17.36+0.3/debian/ftpd-ssl.links linux-ftpd-ssl-0.17.36+0.3/debian/ftpd-ssl.links --- linux-ftpd-ssl-0.17.36+0.3/debian/ftpd-ssl.links1970-01-01 01:00:00.0 +0100 +++ linux-ftpd-ssl-0.17.36+0.3/debian/ftpd-ssl.links2019-02-24 14:39:30.0 +0100 @@ -0,0 +1,2 @@ + +usr/share/man/man8/in.ftpd.8usr/share/man/man8/ftpd.8 diff -Nru linux-ftpd-ssl-0.17.36+0.3/debian/ftpd-ssl.manpages linux-ftpd-ssl-0.17.36+0.3/debian/ftpd-ssl.manpages --- linux-ftpd-ssl-0.17.36+0.3/debian/ftpd-ssl.manpages 1970-01-01 01:00:00.0 +0100 +++ linux-ftpd-ssl-0.17.36+0.3/debian/ftpd-ssl.manpages 2019-02-24 14:39:30.0 +0100 @@ -0,0 +1,2 @@ + +debian/ftpchroot.5 diff -Nru linux-ftpd-ssl-0.17.36+0.3/debian/patches/001-from_hamm.diff linux-ftpd-ssl-0.17.36+0.3/debian/patches/001-from_hamm.diff --- linux-ftpd-ssl-0.17.36+0.3/debian/patches/001-from_hamm.diff 2016-12-25 23:06:11.0 +0100 +++ linux-ftpd-ssl-0.17.36+0.3/debian/patches/001-from_hamm.diff 2018-12-01 19:06:05.0 +0100 @@ -4,8 +4,8 @@ and Rainer Weikusat Forwarded: no Last-Update: 2002-02-09 linux-ftpd-0.17.orig/ftpd/ftpcmd.y -+++ linux-ftpd-0.17/ftpd/ftpcmd.y +--- a/ftpd/ftpcmd.y b/ftpd/ftpcmd.y @@ -55,6 +55,7 @@ #include #include @@ -110,8 +110,8 @@ break; } default: reply(504, "SIZE not implemented for Type %c.", "?AEIL"[type]); linux-ftpd-0.17.orig/ftpd/ftpd.8 -+++ linux-ftpd-0.17/ftpd/ftpd.8 +--- a/ftpd/ftpd.8 b/ftpd/ftpd.8 @@ -67,7 +67,9 @@ .It Fl A Permit only anonymous ftp connections or accounts listed in @@ -145,8 +145,8 @@ .It Pa ~ftp/pub Make this directory mode 555 and owned by .Dq root . linux-ftpd-0.17.orig/ftpd/ftpd.c -+++ linux-ftpd-0.17/ftpd/ftpd.c +--- a/ftpd/ftpd.c b/ftpd/ftpd.c @@ -80,6 +80,7 @@ #include #include @@ -1059,8 +1059,8 @@
Bug#859224: netkit-ftp-ssl: diff for NMU 0.17.34+0.2-4.1
tags 912126 patch
user debian-rele...@lists.debian.org
usertags 859224 + bsp-2019-02-de-bonn
usertags 912126 + bsp-2019-02-de-bonn
thanks
Dear maintainer,
find attached the fix for netkit-ftp-ssl.
For #912126, this goes beyond the usual scope of an NMU but it seemed
wise to brush up the entire build system so it is robust for any
forseeable changes to the Debian toolchain.
For a full explanation, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911154#44
Upload to DELAYED+3 will follow in a few hours, I'd like to give
myself a moment to settle down, then ultimately revisit the
changes done. Feel free to tell me if I should wait a little longer.
Packaging could still take a lot of love.
It might be an idea to drop netkit-ftp in favour of netkit-ftp-ssl,
however netkit-ftp has patches that might be worth preserving.
Regards,
Christoph
diff -Nru netkit-ftp-ssl-0.17.34+0.2/debian/changelog
netkit-ftp-ssl-0.17.34+0.2/debian/changelog
--- netkit-ftp-ssl-0.17.34+0.2/debian/changelog 2017-02-08 18:39:46.0
+0100
+++ netkit-ftp-ssl-0.17.34+0.2/debian/changelog 2019-02-24 14:39:23.0
+0100
@@ -1,3 +1,12 @@
+netkit-ftp-ssl (0.17.34+0.2-4.1) unstable; urgency=high
+
+ * Non-maintainer upload
+ * Use cmake as build system. Closes: #912126
+ * Migrate to openssl 1.1, patches by Sebastian Andrzej Siewior.
+Closes: #859224
+
+ -- Christoph Biedl Sun, 24 Feb 2019
14:39:23 +0100
+
netkit-ftp-ssl (0.17.34+0.2-4) unstable; urgency=medium
* Correctly reuse SSL session identity in data connection.
diff -Nru netkit-ftp-ssl-0.17.34+0.2/debian/compat
netkit-ftp-ssl-0.17.34+0.2/debian/compat
--- netkit-ftp-ssl-0.17.34+0.2/debian/compat2017-02-06 01:13:00.0
+0100
+++ netkit-ftp-ssl-0.17.34+0.2/debian/compat2019-02-24 14:39:23.0
+0100
@@ -1 +1 @@
-9
+10
diff -Nru netkit-ftp-ssl-0.17.34+0.2/debian/control
netkit-ftp-ssl-0.17.34+0.2/debian/control
--- netkit-ftp-ssl-0.17.34+0.2/debian/control 2017-02-08 18:30:50.0
+0100
+++ netkit-ftp-ssl-0.17.34+0.2/debian/control 2019-02-24 14:39:23.0
+0100
@@ -4,7 +4,7 @@
Maintainer: Mats Erik Andersson
Uploaders: Alberto Gonzalez Iniesta
Standards-Version: 3.9.8
-Build-Depends: debhelper (>= 9), libeditline-dev, libncurses5-dev,
libssl1.0-dev | libssl-dev (<< 1.1.0~)
+Build-Depends: debhelper (>= 10~), libeditline-dev, libncurses5-dev,
libssl1.0-dev | libssl-dev (<< 1.1.0~), cmake
Package: ftp-ssl
Architecture: any
@@ -23,5 +23,5 @@
to normal ftp protocol.
.
Advantages over normal ftp(d): Your passwords and the data you send
- will not go in cleartext over the line. Nobody can get it with
- tcpdump or similar tools.
+ will not go in cleartext over the line. Nobody can get it with
+ tcpdump or similar tools.
diff -Nru netkit-ftp-ssl-0.17.34+0.2/debian/dirs
netkit-ftp-ssl-0.17.34+0.2/debian/dirs
--- netkit-ftp-ssl-0.17.34+0.2/debian/dirs 2017-02-06 01:13:00.0
+0100
+++ netkit-ftp-ssl-0.17.34+0.2/debian/dirs 1970-01-01 01:00:00.0
+0100
@@ -1,3 +0,0 @@
-usr/bin
-usr/share/man/man1
-usr/share/man/man5
diff -Nru netkit-ftp-ssl-0.17.34+0.2/debian/ftp-ssl.install
netkit-ftp-ssl-0.17.34+0.2/debian/ftp-ssl.install
--- netkit-ftp-ssl-0.17.34+0.2/debian/ftp-ssl.install 1970-01-01
01:00:00.0 +0100
+++ netkit-ftp-ssl-0.17.34+0.2/debian/ftp-ssl.install 2019-02-24
14:39:23.0 +0100
@@ -0,0 +1,2 @@
+
+usr/bin/ftp-ssl
diff -Nru netkit-ftp-ssl-0.17.34+0.2/debian/ftp-ssl.manpages
netkit-ftp-ssl-0.17.34+0.2/debian/ftp-ssl.manpages
--- netkit-ftp-ssl-0.17.34+0.2/debian/ftp-ssl.manpages 1970-01-01
01:00:00.0 +0100
+++ netkit-ftp-ssl-0.17.34+0.2/debian/ftp-ssl.manpages 2019-02-24
14:39:23.0 +0100
@@ -0,0 +1,3 @@
+
+debian/tmp/usr/share/man/man1/ftp-ssl.1
+debian/tmp/usr/share/man/man5/netrc-ssl.5
diff -Nru
netkit-ftp-ssl-0.17.34+0.2/debian/patches/0001-ftp-ssl-shutdown-the-session-properly.patch
netkit-ftp-ssl-0.17.34+0.2/debian/patches/0001-ftp-ssl-shutdown-the-session-properly.patch
---
netkit-ftp-ssl-0.17.34+0.2/debian/patches/0001-ftp-ssl-shutdown-the-session-properly.patch
1970-01-01 01:00:00.0 +0100
+++
netkit-ftp-ssl-0.17.34+0.2/debian/patches/0001-ftp-ssl-shutdown-the-session-properly.patch
2019-02-24 14:39:23.0 +0100
@@ -0,0 +1,56 @@
+From 48939773820c9fb2c48ec444b156099d1bae Mon Sep 17 00:00:00 2001
+From: Sebastian Andrzej Siewior
+Date: Sat, 11 Nov 2017 11:10:07 +
+Subject: [PATCH 1/2] ftp-ssl: shutdown the session properly
+
+If the SSL session is not shutdown properly, the following SSL_free will
+free all SSL related structs including the session making it impossible
+to be reused in a later connection.
+
+Signed-off-by: Sebastian Andrzej Siewior
+---
+ ftp/ftp.c | 5 +
+ 1 file changed, 5 insertions(+)
+
+--- a/ftp/ftp.c
b/ftp/ftp.c
+@@ -951,6 +951,7 @@
+
+ #ifdef USE_SSL
+ if (ssl_data_active_flag && (ssl_data_con!=NULL)) {
++ SSL_shutdown(ssl_data_con);
Bug#912132: netkit-telnet-ssl: diff for NMU 0.17.41+0.2-3.2
tags 912132 patch
user debian-rele...@lists.debian.org
usertags 912132 + bsp-2019-02-de-bonn
thanks
Dear maintainer,
find attached the fix for netkit-telnet-ssl.
This goes beyond the usual scope of an NMU but it seemed wise to brush
up the entire build system so it is robust for any forseeable changes
to the Debian toolchain.
For a full explanation, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911154#44
Upload to DELAYED+3 will follow in a few hours, I'd like to give
myself a moment to settle down, then ultimately revisit the
changes done. Feel free to tell me if I should wait a little longer.
Packaging could still take a lot of love.
Small changes in /usr/share/doc/
- BUGS is no longer installed
- The two README files were renamed during installation, this was
not recreated
It might be an idea to drop netkit-telnet in favour of
netkit-telnet-ssl, however netkit-telnet has that might be worth
preserving.
Regards,
Christoph
diff -Nru netkit-telnet-ssl-0.17.41+0.2/debian/changelog
netkit-telnet-ssl-0.17.41+0.2/debian/changelog
--- netkit-telnet-ssl-0.17.41+0.2/debian/changelog 2018-07-28
16:14:32.0 +0200
+++ netkit-telnet-ssl-0.17.41+0.2/debian/changelog 2019-02-24
14:38:52.0 +0100
@@ -1,3 +1,10 @@
+netkit-telnet-ssl (0.17.41+0.2-3.2) unstable; urgency=high
+
+ * Non-maintainer upload
+ * Use cmake to build the package. Closes: #912132
+
+ -- Christoph Biedl Sun, 24 Feb 2019
14:38:52 +0100
+
netkit-telnet-ssl (0.17.41+0.2-3.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru netkit-telnet-ssl-0.17.41+0.2/debian/compat
netkit-telnet-ssl-0.17.41+0.2/debian/compat
--- netkit-telnet-ssl-0.17.41+0.2/debian/compat 2017-01-10 23:04:09.0
+0100
+++ netkit-telnet-ssl-0.17.41+0.2/debian/compat 2019-02-24 14:38:52.0
+0100
@@ -1 +1 @@
-9
+10
diff -Nru netkit-telnet-ssl-0.17.41+0.2/debian/control
netkit-telnet-ssl-0.17.41+0.2/debian/control
--- netkit-telnet-ssl-0.17.41+0.2/debian/control2017-01-16
23:16:04.0 +0100
+++ netkit-telnet-ssl-0.17.41+0.2/debian/control2019-02-24
14:38:52.0 +0100
@@ -4,7 +4,7 @@
Maintainer: Mats Erik Andersson
Uploaders: Alberto Gonzalez Iniesta
Standards-Version: 3.9.8
-Build-Depends: debhelper (>= 9), libncurses-dev, libssl-dev | libssl1.0-dev
+Build-Depends: debhelper (>= 10~), libncurses-dev, libssl-dev | libssl1.0-dev,
cmake
Package: telnet-ssl
Architecture: any
diff -Nru netkit-telnet-ssl-0.17.41+0.2/debian/dirs
netkit-telnet-ssl-0.17.41+0.2/debian/dirs
--- netkit-telnet-ssl-0.17.41+0.2/debian/dirs 2017-01-10 23:04:10.0
+0100
+++ netkit-telnet-ssl-0.17.41+0.2/debian/dirs 1970-01-01 01:00:00.0
+0100
@@ -1,3 +0,0 @@
-usr/bin
-usr/share/doc/telnet-ssl
-usr/share/man/man1
diff -Nru netkit-telnet-ssl-0.17.41+0.2/debian/docs
netkit-telnet-ssl-0.17.41+0.2/debian/docs
--- netkit-telnet-ssl-0.17.41+0.2/debian/docs 2017-01-10 23:04:09.0
+0100
+++ netkit-telnet-ssl-0.17.41+0.2/debian/docs 1970-01-01 01:00:00.0
+0100
@@ -1,4 +0,0 @@
-BUGS
-README
-README.SSL
-VERSION
diff -Nru netkit-telnet-ssl-0.17.41+0.2/debian/menu
netkit-telnet-ssl-0.17.41+0.2/debian/menu
--- netkit-telnet-ssl-0.17.41+0.2/debian/menu 2017-01-10 23:04:10.0
+0100
+++ netkit-telnet-ssl-0.17.41+0.2/debian/menu 1970-01-01 01:00:00.0
+0100
@@ -1,3 +0,0 @@
-?package(telnet-ssl): \
- needs="text" section="Applications/Network/Communication" \
- title="Telnet-SSL" command="/usr/bin/telnet-ssl" hints="Terminal"
diff -Nru netkit-telnet-ssl-0.17.41+0.2/debian/patches/010-full_set_in_18.diff
netkit-telnet-ssl-0.17.41+0.2/debian/patches/010-full_set_in_18.diff
--- netkit-telnet-ssl-0.17.41+0.2/debian/patches/010-full_set_in_18.diff
2017-01-10 23:04:09.0 +0100
+++ netkit-telnet-ssl-0.17.41+0.2/debian/patches/010-full_set_in_18.diff
2019-02-24 14:38:52.0 +0100
@@ -21,42 +21,8 @@
Forwarded: no
Last-Update: 2015-01-26
netkit-telnet-0.17.orig/Makefile
-+++ netkit-telnet-0.17/Makefile
-@@ -1,8 +1,7 @@
- # You can do "make SUB=blah" to make only a few, or edit here, or both
- # You can also run make directly in the subdirs you want.
-
--SUB = telnet telnetd
--# not yet: telnetlogin
-+SUB = telnet telnetd telnetlogin
-
- %.build:
- (cd $(patsubst %.build, %, $@) && $(MAKE))
netkit-telnet-0.17.orig/configure
-+++ netkit-telnet-0.17/configure
-@@ -117,7 +117,7 @@
-
- cat << EOF > __conftest.cc
- template class fnord { public: T x; fnord(T y) { x=y; }};
--int main() { fnord a(0); return a.x; }
-+int main() { fnord *a = new fnord(0); return a->x; }
- EOF
-
- if [ x"$CXX" = x ]; then
netkit-telnet-0.17.orig/telnet/Makefile
-+++ netkit-telnet-0.17/telnet/Makefile
-@@ -7,7 +7,7 @@
-
- # -DAUTHENTICATE
- CXXFLAGS += -DUSE_TERMIO -DKLUDGELINEMODE
--LIBS += $(LIBTERMCAP)
-+LIBS = $(LIBTERMCAP)
-
- SRCS = commands.cc main.cc network.cc ring.cc sys_bsd.cc telnet
Bug#912131: netkit-telnet: diff for NMU 0.17-41.2
tags 912131 patch
user debian-rele...@lists.debian.org
usertags 912131 + bsp-2019-02-de-bonn
thanks
Dear maintainer,
find attached the fix for netkit-telnet.
This goes beyond the usual scope of an NMU but it seemed wise to brush
up the entire build system so it is robust for any forseeable changes
to the Debian toolchain.
For a full explanation, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911154#44
Upload to DELAYED+3 will follow in a few hours, I'd like to give
myself a moment to settle down, then ultimately revisit the
changes done. Feel free to tell me if I should wait a little longer.
Packaging could still take a lot of love.
It might be an idea to drop netkit-telnet in favour of
netkit-telnet-ssl, however netkit-telnet has that might be worth
preserving.
Regards,
Christoph
diff -Nru netkit-telnet-0.17/debian/changelog
netkit-telnet-0.17/debian/changelog
--- netkit-telnet-0.17/debian/changelog 2018-12-02 21:12:12.0 +0100
+++ netkit-telnet-0.17/debian/changelog 2019-02-24 14:25:14.0 +0100
@@ -1,3 +1,10 @@
+netkit-telnet (0.17-41.2) unstable; urgency=high
+
+ * Non-maintainer upload
+ * Use cmake to build the package. Closes: #912131
+
+ -- Christoph Biedl Sun, 24 Feb 2019
14:25:14 +0100
+
netkit-telnet (0.17-41.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru netkit-telnet-0.17/debian/compat netkit-telnet-0.17/debian/compat
--- netkit-telnet-0.17/debian/compat2016-11-05 14:51:10.0 +0100
+++ netkit-telnet-0.17/debian/compat2019-02-24 14:25:14.0 +0100
@@ -1 +1 @@
-9
+10
diff -Nru netkit-telnet-0.17/debian/control netkit-telnet-0.17/debian/control
--- netkit-telnet-0.17/debian/control 2016-11-05 15:44:10.0 +0100
+++ netkit-telnet-0.17/debian/control 2019-02-24 14:25:14.0 +0100
@@ -4,7 +4,7 @@
Maintainer: Mats Erik Andersson
Uploaders: Alberto Gonzalez Iniesta
Standards-Version: 3.9.8
-Build-Depends: debhelper (>= 9), libncurses-dev
+Build-Depends: debhelper (>= 10~), libncurses-dev, cmake
Package: telnet
Architecture: any
diff -Nru netkit-telnet-0.17/debian/dirs netkit-telnet-0.17/debian/dirs
--- netkit-telnet-0.17/debian/dirs 2016-11-05 14:51:10.0 +0100
+++ netkit-telnet-0.17/debian/dirs 1970-01-01 01:00:00.0 +0100
@@ -1,3 +0,0 @@
-usr/bin
-usr/share/doc/telnet
-usr/share/man/man1
diff -Nru netkit-telnet-0.17/debian/patches/010-full_set_in_18.diff
netkit-telnet-0.17/debian/patches/010-full_set_in_18.diff
--- netkit-telnet-0.17/debian/patches/010-full_set_in_18.diff 2016-11-05
14:51:10.0 +0100
+++ netkit-telnet-0.17/debian/patches/010-full_set_in_18.diff 2019-02-24
14:25:14.0 +0100
@@ -21,42 +21,8 @@
Forwarded: no
Last-Update: 2015-01-26
netkit-telnet-0.17.orig/Makefile
-+++ netkit-telnet-0.17/Makefile
-@@ -1,8 +1,7 @@
- # You can do "make SUB=blah" to make only a few, or edit here, or both
- # You can also run make directly in the subdirs you want.
-
--SUB = telnet telnetd
--# not yet: telnetlogin
-+SUB = telnet telnetd telnetlogin
-
- %.build:
- (cd $(patsubst %.build, %, $@) && $(MAKE))
netkit-telnet-0.17.orig/configure
-+++ netkit-telnet-0.17/configure
-@@ -117,7 +117,7 @@
-
- cat << EOF > __conftest.cc
- template class fnord { public: T x; fnord(T y) { x=y; }};
--int main() { fnord a(0); return a.x; }
-+int main() { fnord *a = new fnord(0); return a->x; }
- EOF
-
- if [ x"$CXX" = x ]; then
netkit-telnet-0.17.orig/telnet/Makefile
-+++ netkit-telnet-0.17/telnet/Makefile
-@@ -7,7 +7,7 @@
-
- # -DAUTHENTICATE
- CXXFLAGS += -DUSE_TERMIO -DKLUDGELINEMODE
--LIBS += $(LIBTERMCAP)
-+LIBS = $(LIBTERMCAP)
-
- SRCS = commands.cc main.cc network.cc ring.cc sys_bsd.cc telnet.cc \
- terminal.cc tn3270.cc utilities.cc genget.cc environ.cc netlink.cc
netkit-telnet-0.17.orig/telnet/commands.cc
-+++ netkit-telnet-0.17/telnet/commands.cc
+--- a/telnet/commands.cc
b/telnet/commands.cc
@@ -86,10 +86,6 @@
#define HELPINDENT ((int) sizeof ("connect"))
@@ -374,8 +340,8 @@
#if defined(IP_OPTIONS) && defined(HAS_IPPROTO_IP)
/*
netkit-telnet-0.17.orig/telnet/main.cc
-+++ netkit-telnet-0.17/telnet/main.cc
+--- a/telnet/main.cc
b/telnet/main.cc
@@ -45,7 +45,10 @@
#include
@@ -477,8 +443,8 @@
*argp++ = argv[0]; /* host */
if (argc > 1)
*argp++ = argv[1]; /* port */
netkit-telnet-0.17.orig/telnet/netlink.cc
-+++ netkit-telnet-0.17/telnet/netlink.cc
+--- a/telnet/netlink.cc
b/telnet/netlink.cc
@@ -81,20 +81,23 @@
::close(net);
}
@@ -545,8 +511,8 @@
}
return 2;
}
netkit-telnet-0.17.orig/telnet/netlink.h
-+++ netkit-telnet-0.17/telnet/netlink.h
+--- a/telnet/netlink.h
b/telnet/netlink.h
@@ -6,8 +6,7 @@
netlink();
~netlink();
@@ -557,8 +523,8 @@
char *srcroute, int srlen,
int tos);
void close(int doshutdown);
-
Processed: Tagging
Processing commands for cont...@bugs.debian.org: > tags 912122 patch Bug #912122 [src:linux-ftpd] linux-ftpd misses the generator for configure Added tag(s) patch. > tags 912123 patch Bug #912123 [src:linux-ftpd-ssl] linux-ftpd-ssl misses the generator for configure Added tag(s) patch. > tags 912125 patch Bug #912125 [src:netkit-ftp] netkit-ftp misses the generator for configure Added tag(s) patch. > tags 912126 patch Bug #912126 [src:netkit-ftp-ssl] netkit-ftp-ssl misses the generator for configure Added tag(s) patch. > tags 912131 patch Bug #912131 [src:netkit-telnet] netkit-telnet misses the generator for configure Added tag(s) patch. > tags 912132 patch Bug #912132 [src:netkit-telnet-ssl] netkit-telnet-ssl misses the generator for configure Added tag(s) patch. > user debian-rele...@lists.debian.org Setting user to debian-rele...@lists.debian.org (was debian.a...@manchmal.in-ulm.de). > usertags 859224 + bsp-2019-02-de-bonn There were no usertags set. Usertags are now: bsp-2019-02-de-bonn. > usertags 912122 + bsp-2019-02-de-bonn There were no usertags set. Usertags are now: bsp-2019-02-de-bonn. > usertags 912123 + bsp-2019-02-de-bonn There were no usertags set. Usertags are now: bsp-2019-02-de-bonn. > usertags 912125 + bsp-2019-02-de-bonn Usertags were: bsp-2019-02-de-bonn. Usertags are now: bsp-2019-02-de-bonn. > usertags 912126 + bsp-2019-02-de-bonn There were no usertags set. Usertags are now: bsp-2019-02-de-bonn. > usertags 912131 + bsp-2019-02-de-bonn Usertags were: bsp-2019-02-de-bonn. Usertags are now: bsp-2019-02-de-bonn. > usertags 912132 + bsp-2019-02-de-bonn There were no usertags set. Usertags are now: bsp-2019-02-de-bonn. > thanks Stopping processing here. Please contact me if you need assistance. -- 912122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912122 912123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912123 912125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912125 912126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912126 912131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912131 912132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912132 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914632: uw-imap: CVE-2018-19518
Hi Magnus,
>Perhaps wanting to run imapd via remote shell is so rare that there's
>no need to write a NEWS.Debian entry?
in case of doubt just write one, it does not hurt.
Are you going to upload within the next five days or so, or
do you need help? (We’re at a BSP and currently fixing stuff…)
Thanks,
//mirabilos
--
> Wish I had pine to hand :-( I'll give lynx a try, thanks.
Michael Schmitz on nntp://news.gmane.org/gmane.linux.debian.ports.68k
a.k.a. {news.gmane.org/nntp}#news.gmane.linux.debian.ports.68k in pine
Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?
Johannes Schauer writes: > With how merged-/usr is getting deployed via debootstrap, we are placing more > of the instructions of how a Debian system is supposed to be setup *outside* > of > the packages themselves (and into debootstrap). It would make a cleaner design > if we could have all necessary definitions of how to create a Debian chroot > from scratch (on a Debian system) in the packages *themselves* instead of > requiring code around the packages that is doing some magic setup (usually > debootstrap). One could drop the magic setup if merged-/usr was mandatory: (1) have /bin -> /usr/bin symlinks shipped in base-files (2) have all packages install to /usr The additional complexity of having to setup symlinks outside the packaging system comes from supporting both merged and nonmerged setups. debootstrap or the usrmerge package implement some way to setup the symlink which would not be necessary if they were included in the packages; it would not be necessary if (1) was implemented (plus handling system upgrades from legacy installations). On merged-/usr systems, packages could just switch install location gradually; they would install to the same location anyway, no compat symlinks or maintainer script logic required. Ansgar
Processed: Tagging
Processing commands for cont...@bugs.debian.org: > tags 859224 pending Bug #859224 [netkit-ftp-ssl] netkit-ftp-ssl: Please migrate to openssl1.1 in Buster Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 859224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?
On Sun, 24 Feb 2019 14:16:03 +0100 Johannes Schauer wrote: > I found that some important arguments are still missing. A recent mail by > Guillem [1] nicely summarizes also many of my own thoughts. I'm going to paste > the relevant content into this mail for convenience of the reader: I think those have actually been addressed before, even if they're not explicitly listed or refuted in the draft. Guillem seems to accept moving away from current filesystem layout, but also opposes the resulting layout used by other distributions (which includes the /bin -> /usr/bin symlink). Do you share that view? The main issue with Guillem's view is that in practice it would make the transition more cumbersome and error-prone. If there is no directory-level symlink, then migrating things requires either creating individual symlinks for everything instead, or having a flag day to make sure nothing references the old location any more. In practice either of those is more problematic than a directory symlink. > > 1) The merged-/usr-via-symlinks deployment method used by both > >debootstrap and usrmerge, means that those systems will get > >permanent filesystem aliasing problems, forever. Even when all > >files might have been moved to their /usr counterparts in the > >packages! This is due to the fact that different pathnames can > >end up pointing (before any canonicalization!) to the same dentry. > > > >This does not only affect dpkg (dpkg, dpkg-divert, dpkg-trigger, > >etc), and update-alternatives (in a worse way), but any program > >that uses pathanmes in the filesystem as keys in databases f.ex. This has already been in use, both in Debian and in other distributions, for quite some time. No major problems have been reported. Arguing about "any program" is not useful when discussing only Debian choices, because the layout is used by other distributions in any case and programs have to cope. > > 2) It bypasses the packaging system understanding of what is on the > >filesystem and creates mismatches between what's on binary packages > >and what's on disk. This also has not caused major problems, but it can be solved straightforwardly in dpkg if needed. Dpkg can special-case any legacy /bin path contained in a package and internally change it to /usr/bin. > > 3) Switching packages to the merged-/usr layout could have been > >accomplished automatically via debhelper for a coverage of around > >99% (?) of the archive. With something along the lines of: This would just create a more cumbersome and error-prone migration. > > 4) Due to having to support the broken merged-/usr-via-symlinks > >deployment, when we want to move the contents of the binary > >packages to the merged-/usr layout, we require now to include tons > >of logic in (probably new) maintainer scripts, when we have been > >trying to remove them altogether. :( With even more files untracked > >by dpkg itself, bypassing the packaging system even more, when the > >compat symlinks could have been shipped in the binary packages. This seems to be based on questionable implicit assumptions. Namely that the move would want to create an individual per-file compatibility symlink in /bin for non-merged systems, and this is the part which would cause problems. There seem to be neither technical reasons to prefer non-merged systems for any use nor practical difficulties migrating existing systems to the merged layout, so long-term it seems OK to deal with this by just requiring merged-usr and not shipping any individual compatibility links for non-merged systems. This allows the simplest possible move - just install the files in /usr normally. > > 5) Most new installations will not even benefit from this hacky and > >rushed deployment, as long as they do not use a separate parition > >for /usr! Is there a point to this? Yes, migrating to merged /usr is mostly an internal implementation detail for most users. But this does not exactly give any argument against the migration, other than calling it "hacky and rushed" while it seems to be the most practical way to do things. > > 6) The merged-/usr-via-symlinks deployment hack is irreversible right > >now. This is not a reason to avoid using the merged-usr layout. > Just like Guillem, I'm personally not against merged-/usr but against how we > implement it. Not against, except for the directory symlinks being part of the merged-usr layout?
Processed: forcibly merging 918825 922260
Processing commands for cont...@bugs.debian.org:
> forcemerge 918825 922260
Bug #918825 {Done: Sebastien Badia } [src:python-ncclient]
python-ncclient: FTBFS with Sphinx 1.8: No module named 'sphinx.ext.pngmath'
Bug #922260 [src:python-ncclient] python-ncclient: FTBFS (Could not import
extension sphinx.ext.pngmath)
Marked Bug as done
Marked as fixed in versions python-ncclient/0.6.0-2.
Bug #918825 {Done: Sebastien Badia } [src:python-ncclient]
python-ncclient: FTBFS with Sphinx 1.8: No module named 'sphinx.ext.pngmath'
Added tag(s) ftbfs.
Merged 918825 922260
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
918825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918825
922260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#921757: Can reproduce
Processing commands for cont...@bugs.debian.org: > tags 921757 - unreproducible Bug #921757 [src:os-autoinst] os-autoinst: FTBFS (failing tests) Removed tag(s) unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. -- 921757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921757: Can reproduce
tags 921757 - unreproducible thanks I still can reproduce the failure I reported. Just checked right now: https://people.debian.org/~sanvila/build-logs/os-autoinst/ and there are also build failures here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/os-autoinst.html and here: https://buildd.debian.org/status/package.php?p=os%2dautoinst (but I've not checked if the failures in reproducible-builds.org or buildd.debian.org are of the same kind than the ones I can reproduce in my autobuilders). For the problem I reported, I can provide ssh access to anybody willing to debug the problem. Please contact me privately for details. Thanks.
Bug#859224: netkit-ftp-ssl: diff for NMU 0.17.34+0.2-4.1
On 2019-02-24 16:25:32 [+0100], Christoph Biedl wrote: > diff -Nru netkit-ftp-ssl-0.17.34+0.2/debian/control > netkit-ftp-ssl-0.17.34+0.2/debian/control > --- netkit-ftp-ssl-0.17.34+0.2/debian/control 2017-02-08 18:30:50.0 > +0100 > +++ netkit-ftp-ssl-0.17.34+0.2/debian/control 2019-02-24 14:39:23.0 > +0100 > @@ -4,7 +4,7 @@ > Maintainer: Mats Erik Andersson > Uploaders: Alberto Gonzalez Iniesta > Standards-Version: 3.9.8 > -Build-Depends: debhelper (>= 9), libeditline-dev, libncurses5-dev, > libssl1.0-dev | libssl-dev (<< 1.1.0~) > +Build-Depends: debhelper (>= 10~), libeditline-dev, libncurses5-dev, > libssl1.0-dev | libssl-dev (<< 1.1.0~), cmake you need to drop libssl1.0-dev from here and simply depend on libssl-dev. Sebastian
Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?
Le mardi, 19 février 2019, 01.59:18 h CET Steve McIntyre a écrit : > While I'm not necessarily disagreeing with the overall point(s) here, > some of the points in this list of arguments seem dubious at > best. Maybe you could expand? Sure. Sorry for publishing a new ballot before answering. > >* booting with `/` only is not systematically tested in Debian anymore; > > I'm assuming you mean "/ without /usr" here? Yes. Clarified this point by merging it with the "separate / and /usr" one above. > >* the packaging infrastructure to install files outside of `/usr` is not > > standard and represents technical debt: > > I have no idea what you're suggesting here. Same here (clarified in the ballot). What I'm trying to say here is that installing (e.g.) libs to /lib instead of /usr/lib is usually a deviation from standard software building (either in upstream packaging, or in debian/rules), that needs to be maintained on the long-term. Cheers, OdyX signature.asc Description: This is a digitally signed message part.
Processed (with 1 error): forcibly merging 921779 921299 921299 921783 921789 921802 921838 921299
Processing commands for cont...@bugs.debian.org: > forcemerge 921779 921299 921299 921783 921789 921802 921838 921299 Bug #921779 [src:doxygen] cascade of FTBFS Unable to merge bugs because: package of #921783 is 'doxygen' not 'src:doxygen' package of #921299 is 'doxygen' not 'src:doxygen' package of #921838 is 'doxygen' not 'src:doxygen' package of #921789 is 'doxygen' not 'src:doxygen' package of #921802 is 'doxygen' not 'src:doxygen' Failed to forcibly merge 921779: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 921299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921299 921779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921779 921783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921783 921789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921789 921802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921802 921838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 921299 to doxygen
Processing commands for cont...@bugs.debian.org: > reassign 921299 doxygen Bug #921299 [doxygen] "Doxygen breaks caffe" Ignoring request to reassign bug #921299 to the same package > thanks Stopping processing here. Please contact me if you need assistance. -- 921299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 921299 to doxygen
Processing commands for cont...@bugs.debian.org: > reassign 921299 doxygen Bug #921299 [doxygen] "Doxygen breaks caffe" Ignoring request to reassign bug #921299 to the same package > thanks Stopping processing here. Please contact me if you need assistance. -- 921299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 921779 921299 921299 921783 921789 921802 921838 921299
Processing commands for cont...@bugs.debian.org: > forcemerge 921779 921299 921299 921783 921789 921802 921838 921299 Bug #921779 [doxygen] cascade of FTBFS Bug #921783 [doxygen] graphite2: FTBFS (LaTeX error) Removed indication that 921783 affects src:graphite2 Added indication that 921783 affects toulbar2,src:librostlab-blast,src:primesieve,src:bliss Added tag(s) help and moreinfo. Bug #921838 [doxygen] ppl: FTBFS (LaTeX error) Removed indication that 921838 affects src:ppl Added indication that 921838 affects toulbar2,src:librostlab-blast,src:primesieve,src:bliss Added tag(s) help and moreinfo. Bug #921779 [doxygen] cascade of FTBFS Added tag(s) sid, buster, and moreinfo. Bug #921299 [doxygen] "Doxygen breaks caffe" Added indication that 921299 affects toulbar2,src:librostlab-blast,src:primesieve,src:bliss Added tag(s) buster, ftbfs, sid, and help. Bug #921802 [doxygen] primesieve: FTBFS (LaTeX error) Removed indication that 921802 affects src:primesieve Added indication that 921802 affects toulbar2,src:librostlab-blast,src:primesieve,src:bliss Added tag(s) help and moreinfo. Bug #921789 [doxygen] librostlab-blast: FTBFS (LaTeX error) Removed indication that 921789 affects src:librostlab-blast Added indication that 921789 affects toulbar2,src:librostlab-blast,src:primesieve,src:bliss Added tag(s) moreinfo and help. Merged 921299 921779 921783 921789 921802 921838 > thanks Stopping processing here. Please contact me if you need assistance. -- 921299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921299 921779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921779 921783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921783 921789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921789 921802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921802 921838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 921838 to doxygen
Processing commands for cont...@bugs.debian.org: > reassign 921838 doxygen Bug #921838 [doxygen] ppl: FTBFS (LaTeX error) Ignoring request to reassign bug #921838 to the same package > thanks Stopping processing here. Please contact me if you need assistance. -- 921838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 921779 to doxygen
Processing commands for cont...@bugs.debian.org: > reassign 921779 doxygen Bug #921779 [src:doxygen] cascade of FTBFS Bug reassigned from package 'src:doxygen' to 'doxygen'. No longer marked as found in versions doxygen/1.8.13-10. Ignoring request to alter fixed versions of bug #921779 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 921779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 921783 to doxygen
Processing commands for cont...@bugs.debian.org: > reassign 921783 doxygen Bug #921783 [doxygen] graphite2: FTBFS (LaTeX error) Ignoring request to reassign bug #921783 to the same package > thanks Stopping processing here. Please contact me if you need assistance. -- 921783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921783 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 921802 to doxygen
Processing commands for cont...@bugs.debian.org: > reassign 921802 doxygen Bug #921802 [doxygen] primesieve: FTBFS (LaTeX error) Ignoring request to reassign bug #921802 to the same package > thanks Stopping processing here. Please contact me if you need assistance. -- 921802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 921789 to doxygen
Processing commands for cont...@bugs.debian.org: > reassign 921789 doxygen Bug #921789 [doxygen] librostlab-blast: FTBFS (LaTeX error) Ignoring request to reassign bug #921789 to the same package > thanks Stopping processing here. Please contact me if you need assistance. -- 921789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 921299 to doxygen
Processing commands for cont...@bugs.debian.org: > reassign 921299 doxygen Bug #921299 [doxygen] "Doxygen breaks caffe" Ignoring request to reassign bug #921299 to the same package > thanks Stopping processing here. Please contact me if you need assistance. -- 921299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923164: leiningen-clojure: FTBFS (Could not resolve dependencies for project leiningen-core:leiningen-core:jar:2.8.1)
Package: src:leiningen-clojure Version: 2.8.1-9 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with bash-completion --with javahelper --buildsystem=maven dh_update_autotools_config -i -O--buildsystem=maven dh_autoreconf -i -O--buildsystem=maven dh_auto_configure -i -O--buildsystem=maven mh_patchpoms -pleiningen --debian-build --keep-pom-version --maven-repo=/<>/debian/maven-repo jh_linkjars -i -O--buildsystem=maven debian/rules override_dh_auto_build make[1]: Entering directory '/<>' cp resources/leiningen/bootclasspath-deps.clj \ leiningen-core/src/leiningen/bootclasspath-deps.clj dh_auto_build -- -f leiningen-core/pom.xml install /usr/lib/jvm/java-8-openjdk-amd64/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode -f leiningen-core/pom.xml install -DskipTests -Dnotimestamp=true -Dlocale=en_US [INFO] Scanning for projects... [INFO] [INFO] ---< leiningen-core:leiningen-core > [INFO] Building leiningen-core 2.8.1 [INFO] [ jar ]- [WARNING] The POM for bultitude:bultitude:jar:debian is missing, no dependency information available [WARNING] The POM for org.clojure:clojure:jar:debian is missing, no dependency information available [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 1.658 s [INFO] Finished at: 2019-02-24T12:14:02Z [INFO] [ERROR] Failed to execute goal on project leiningen-core: Could not resolve dependencies for project leiningen-core:leiningen-core:jar:2.8.1: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact bultitude:bultitude:jar:debian has not been downloaded from it before. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException dh_auto_build: /usr/lib/jvm/java-8-openjdk-amd64/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode -f leiningen-core/pom.xml install -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1 make[1]: *** [debian/rules:67: override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:63: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/leiningen-clojure.html If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Processed: reassign 920459 to doxygen, forcibly merging 921779 920459, reassign 921779 to texlive-latex-extra ...
Processing commands for cont...@bugs.debian.org: > reassign 920459 doxygen Bug #920459 [doxygen] Doxygen breaks toulbar2 Ignoring request to reassign bug #920459 to the same package > forcemerge 921779 920459 Bug #921779 [doxygen] cascade of FTBFS Bug #921299 [doxygen] "Doxygen breaks caffe" Bug #921783 [doxygen] graphite2: FTBFS (LaTeX error) Bug #921789 [doxygen] librostlab-blast: FTBFS (LaTeX error) Bug #921802 [doxygen] primesieve: FTBFS (LaTeX error) Bug #921838 [doxygen] ppl: FTBFS (LaTeX error) Bug #920459 [doxygen] Doxygen breaks toulbar2 916715 was blocked by: 920459 916715 was not blocking any bugs. Removed blocking bug(s) of 916715: 920459 Added indication that 920459 affects toulbar2,src:librostlab-blast,src:primesieve,src:bliss Added tag(s) moreinfo, ftbfs, and help. Bug #921299 [doxygen] "Doxygen breaks caffe" Bug #921783 [doxygen] graphite2: FTBFS (LaTeX error) Bug #921789 [doxygen] librostlab-blast: FTBFS (LaTeX error) Bug #921802 [doxygen] primesieve: FTBFS (LaTeX error) Bug #921838 [doxygen] ppl: FTBFS (LaTeX error) Merged 920459 921299 921779 921783 921789 921802 921838 > reassign 921779 texlive-latex-extra Bug #921779 [doxygen] cascade of FTBFS Bug #920459 [doxygen] Doxygen breaks toulbar2 Bug #921299 [doxygen] "Doxygen breaks caffe" Bug #921783 [doxygen] graphite2: FTBFS (LaTeX error) Bug #921789 [doxygen] librostlab-blast: FTBFS (LaTeX error) Bug #921802 [doxygen] primesieve: FTBFS (LaTeX error) Bug #921838 [doxygen] ppl: FTBFS (LaTeX error) Bug reassigned from package 'doxygen' to 'texlive-latex-extra'. Bug reassigned from package 'doxygen' to 'texlive-latex-extra'. Bug reassigned from package 'doxygen' to 'texlive-latex-extra'. Bug reassigned from package 'doxygen' to 'texlive-latex-extra'. Bug reassigned from package 'doxygen' to 'texlive-latex-extra'. Bug reassigned from package 'doxygen' to 'texlive-latex-extra'. Bug reassigned from package 'doxygen' to 'texlive-latex-extra'. Ignoring request to alter found versions of bug #921779 to the same values previously set Ignoring request to alter found versions of bug #920459 to the same values previously set Ignoring request to alter found versions of bug #921299 to the same values previously set Ignoring request to alter found versions of bug #921783 to the same values previously set Ignoring request to alter found versions of bug #921789 to the same values previously set Ignoring request to alter found versions of bug #921802 to the same values previously set Ignoring request to alter found versions of bug #921838 to the same values previously set Ignoring request to alter fixed versions of bug #921779 to the same values previously set Ignoring request to alter fixed versions of bug #920459 to the same values previously set Ignoring request to alter fixed versions of bug #921299 to the same values previously set Ignoring request to alter fixed versions of bug #921783 to the same values previously set Ignoring request to alter fixed versions of bug #921789 to the same values previously set Ignoring request to alter fixed versions of bug #921802 to the same values previously set Ignoring request to alter fixed versions of bug #921838 to the same values previously set > retitle 921779 tabu.sty: Breaks with xcolor in many circumstances Bug #921779 [texlive-latex-extra] cascade of FTBFS Bug #920459 [texlive-latex-extra] Doxygen breaks toulbar2 Bug #921299 [texlive-latex-extra] "Doxygen breaks caffe" Bug #921783 [texlive-latex-extra] graphite2: FTBFS (LaTeX error) Bug #921789 [texlive-latex-extra] librostlab-blast: FTBFS (LaTeX error) Bug #921802 [texlive-latex-extra] primesieve: FTBFS (LaTeX error) Bug #921838 [texlive-latex-extra] ppl: FTBFS (LaTeX error) Changed Bug title to 'tabu.sty: Breaks with xcolor in many circumstances' from 'cascade of FTBFS'. Changed Bug title to 'tabu.sty: Breaks with xcolor in many circumstances' from 'Doxygen breaks toulbar2'. Changed Bug title to 'tabu.sty: Breaks with xcolor in many circumstances' from '"Doxygen breaks caffe"'. Changed Bug title to 'tabu.sty: Breaks with xcolor in many circumstances' from 'graphite2: FTBFS (LaTeX error)'. Changed Bug title to 'tabu.sty: Breaks with xcolor in many circumstances' from 'librostlab-blast: FTBFS (LaTeX error)'. Changed Bug title to 'tabu.sty: Breaks with xcolor in many circumstances' from 'primesieve: FTBFS (LaTeX error)'. Changed Bug title to 'tabu.sty: Breaks with xcolor in many circumstances' from 'ppl: FTBFS (LaTeX error)'. > affects 921779 + doxygen Bug #921779 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #920459 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921299 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921783 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921789 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921802 [texlive-latex-extra] tabu.sty: Breaks with xcolor
Processed: tagging 921779
Processing commands for cont...@bugs.debian.org: > tags 921779 - help moreinfo Bug #921779 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #920459 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921299 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921783 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921789 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921802 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921838 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Removed tag(s) help and moreinfo. Removed tag(s) help and moreinfo. Removed tag(s) help and moreinfo. Removed tag(s) help and moreinfo. Removed tag(s) moreinfo and help. Removed tag(s) moreinfo and help. Removed tag(s) help and moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459 921299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921299 921779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921779 921783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921783 921789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921789 921802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921802 921838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 921779 in 2018.20190131-1
Processing commands for cont...@bugs.debian.org: > found 921779 2018.20190131-1 Bug #921779 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #920459 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921299 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921783 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921789 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921802 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921838 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Marked as found in versions texlive-extra/2018.20190131-1. Marked as found in versions texlive-extra/2018.20190131-1. Marked as found in versions texlive-extra/2018.20190131-1. Marked as found in versions texlive-extra/2018.20190131-1. Marked as found in versions texlive-extra/2018.20190131-1. Marked as found in versions texlive-extra/2018.20190131-1. Marked as found in versions texlive-extra/2018.20190131-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459 921299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921299 921779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921779 921783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921783 921789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921789 921802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921802 921838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919053: golang-gopkg-square-go-jose.v2 FTBFS: FAIL: TestVectorsRSA
reopen 919053 found 919053 2.1.6-1 thanks I don't know why this was closed, but it's definitely not fixed. There are build failures here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-gopkg-square-go-jose.v2.html and TestVectorsRSA fails also here: https://ci.debian.net/data/packages/unstable/amd64/g/golang-gopkg-square-go-jose.v2/latest-autopkgtest/log.gz In my autobuilders, this fails randomly with a failure rate betweenn 55% and 60% (I can provide ssh access if required, please contact me privately for details). Thanks.
Processed: Re: golang-gopkg-square-go-jose.v2 FTBFS: FAIL: TestVectorsRSA
Processing commands for cont...@bugs.debian.org:
> reopen 919053
Bug #919053 {Done: Adrian Bunk }
[src:golang-gopkg-square-go-jose.v2] golang-gopkg-square-go-jose.v2 FTBFS:
FAIL: TestVectorsRSA
Bug reopened
Ignoring request to alter fixed versions of bug #919053 to the same values
previously set
> found 919053 2.1.6-1
Bug #919053 [src:golang-gopkg-square-go-jose.v2] golang-gopkg-square-go-jose.v2
FTBFS: FAIL: TestVectorsRSA
Ignoring request to alter found versions of bug #919053 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
919053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919053
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tabu: breaks with color and/or xcolor when spread or negative X coefficients are used
Processing commands for cont...@bugs.debian.org: > outlook 920459 I have a patch and am currently testing r-depends. --mirabilos Outlook recorded from message bug 920459 message Outlook recorded from message bug 920459 message Outlook recorded from message bug 920459 message Outlook recorded from message bug 920459 message Outlook recorded from message bug 920459 message Outlook recorded from message bug 920459 message Outlook recorded from message bug 920459 message > owner 920459 t...@debian.org Bug #920459 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921299 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921779 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921783 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921789 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921802 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921838 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Owner recorded as t...@debian.org. Owner recorded as t...@debian.org. Owner recorded as t...@debian.org. Owner recorded as t...@debian.org. Owner recorded as t...@debian.org. Owner recorded as t...@debian.org. Owner recorded as t...@debian.org. > # FTBFS bugs need to affect the source package, not the binary package > affects 920459 - toulbar2 Bug #920459 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921299 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921779 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921783 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921789 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921802 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921838 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Removed indication that 920459 affects toulbar2 Removed indication that 921299 affects toulbar2 Removed indication that 921779 affects toulbar2 Removed indication that 921783 affects toulbar2 Removed indication that 921789 affects toulbar2 Removed indication that 921802 affects toulbar2 Removed indication that 921838 affects toulbar2 > affects 920459 + src:toulbar2 Bug #920459 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921299 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921779 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921783 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921789 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921802 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921838 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Added indication that 920459 affects src:toulbar2 Added indication that 921299 affects src:toulbar2 Added indication that 921779 affects src:toulbar2 Added indication that 921783 affects src:toulbar2 Added indication that 921789 affects src:toulbar2 Added indication that 921802 affects src:toulbar2 Added indication that 921838 affects src:toulbar2 > thanks Stopping processing here. Please contact me if you need assistance. -- 920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459 921299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921299 921779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921779 921783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921783 921789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921789 921802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921802 921838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923013: [Pkg-xen-devel] Bug#923013: xen: FTBFS when built with dpkg-buildpackage -A
Ok, so... On 2/24/19 3:39 PM, Santiago Vila wrote: >> All of this seems to be related to the dh-exec usage for putting files >> in the xen-utils-common package with a different name. This is the first >> time this package is using dh-exec. >> >> [...] >> >> Interestingly, 'etc/default/xencommons => /etc/default/xen' does not >> result in a similar error? >> >> I also found this one, which seems to be related: >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831786 >> >> Do you have an idea / suggestion how we can deal with this? > > Based on your analysis, maybe applying the patch below. > > After all, the "fail-missing" thing is just an extra protection which > helps avoiding mistakes when installing things, but in this case > it seems to be more troublesome than helpful. > > --- a/debian/rules > +++ b/debian/rules > @@ -307,8 +307,11 @@ override_dh_compress: > > # By default, files in debian/tmp which are not handled by anything > # in rules are ignored. This makes them into errors. > -override_dh_missing: > - dh_missing --fail-missing > +# > +# Disabled because of Bug #831786 > +# > +# override_dh_missing: > +#dh_missing --fail-missing > > > # We are dropping the config file /etc/default/xen which appeared in Oh right. This accidentally quoted line helped me find out that etc/default/xencommons is listed in debian/not-installed because it was not installed before. However, now it is again, but it was not removed from not-installed, and this solves the mystery of dh_missing not complaining about it. It seems useful to me to keep the dh_missing --fail-missing, so the workaround for the dh-exec bug will now be to also list etc/bash_completion.d/xl.sh in not-installed, with a short explanation in a comment. Now I can do dpkg-buildpackage -A without the error. https://salsa.debian.org/xen-team/debian-xen/commit/69f65e1f7676cb387c9742a4e8ab96ee53e36d1d (this commit hash will likely disapper again later, but today it'll be there :) ). Hans
Bug#917030: Bug #917030 in python-pykmip marked as pending
Control: tag -1 pending Hello, Bug #917030 in python-pykmip reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/python-pykmip/commit/e5f467144e4c9fa115f223c8f569baa84e69cfd4 * CVE-2018-1000872: Resource Management Errors (similar issue to CVE-2015-5262) vulnerability in PyKMIP server that can result in DOS: the server can be made unavailable by one or more clients opening all of the available sockets. Applied upstream patch: Fix a denial-of-service bug by setting the server socket timeout (Closes: #917030). (this message was generated automatically) -- Greetings https://bugs.debian.org/917030
Bug#917030: Bug #917030 in python-pykmip marked as pending
Control: tag -1 pending Hello, Bug #917030 in python-pykmip reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/python-pykmip/commit/3a64ac798175adfc846a6e4176b1dbac5d4052ea * CVE-2018-1000872: Resource Management Errors (similar issue to CVE-2015-5262) vulnerability in PyKMIP server that can result in DOS: the server can be made unavailable by one or more clients opening all of the available sockets. Applied upstream patch: Fix a denial-of-service bug by setting the server socket timeout (Closes: #917030). (this message was generated automatically) -- Greetings https://bugs.debian.org/917030
Processed: Bug #917030 in python-pykmip marked as pending
Processing control commands: > tag -1 pending Bug #917030 [src:python-pykmip] python-pykmip: CVE-2018-1000872 Added tag(s) pending. -- 917030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917030 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug #917030 in python-pykmip marked as pending
Processing control commands: > tag -1 pending Bug #917030 [src:python-pykmip] python-pykmip: CVE-2018-1000872 Ignoring request to alter tags of bug #917030 to the same tags previously set -- 917030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917030 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914632: uw-imap: CVE-2018-19518
On Sun, Feb 24, 2019 at 02:53:41PM +0100, Magnus Holmgren wrote: > Perhaps wanting to run imapd via remote shell is so rare that there's no need > to write a NEWS.Debian entry? I agree, I don't think this needs a NEWS.Debian. Cheers, Moritz
Processed: affects 921779
Processing commands for cont...@bugs.debian.org: > affects 921779 + frobby Bug #921779 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #920459 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921299 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921783 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921789 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921802 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921838 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Added indication that 921779 affects frobby Added indication that 920459 affects frobby Added indication that 921299 affects frobby Added indication that 921783 affects frobby Added indication that 921789 affects frobby Added indication that 921802 affects frobby Added indication that 921838 affects frobby > thanks Stopping processing here. Please contact me if you need assistance. -- 920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459 921299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921299 921779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921779 921783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921783 921789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921789 921802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921802 921838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 921779
Processing commands for cont...@bugs.debian.org: > affects 921779 + fltk1.3 Bug #921779 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #920459 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921299 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921783 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921789 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921802 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921838 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Added indication that 921779 affects fltk1.3 Added indication that 920459 affects fltk1.3 Added indication that 921299 affects fltk1.3 Added indication that 921783 affects fltk1.3 Added indication that 921789 affects fltk1.3 Added indication that 921802 affects fltk1.3 Added indication that 921838 affects fltk1.3 > thanks Stopping processing here. Please contact me if you need assistance. -- 920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459 921299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921299 921779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921779 921783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921783 921789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921789 921802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921802 921838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 921779
Processing commands for cont...@bugs.debian.org: > affects 921779 + src:libstxxl Bug #921779 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #920459 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921299 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921783 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921789 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921802 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921838 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Added indication that 921779 affects src:libstxxl Added indication that 920459 affects src:libstxxl Added indication that 921299 affects src:libstxxl Added indication that 921783 affects src:libstxxl Added indication that 921789 affects src:libstxxl Added indication that 921802 affects src:libstxxl Added indication that 921838 affects src:libstxxl > thanks Stopping processing here. Please contact me if you need assistance. -- 920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459 921299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921299 921779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921779 921783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921783 921789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921789 921802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921802 921838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 921779
Processing commands for cont...@bugs.debian.org: > affects 921779 - fltk1.3 frobby Bug #921779 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #920459 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921299 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921783 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921789 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921802 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921838 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Removed indication that 921779 affects fltk1.3 and frobby Removed indication that 920459 affects fltk1.3 and frobby Removed indication that 921299 affects fltk1.3 and frobby Removed indication that 921783 affects fltk1.3 and frobby Removed indication that 921789 affects fltk1.3 and frobby Removed indication that 921802 affects fltk1.3 and frobby Removed indication that 921838 affects fltk1.3 and frobby > thanks Stopping processing here. Please contact me if you need assistance. -- 920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459 921299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921299 921779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921779 921783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921783 921789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921789 921802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921802 921838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 921779
Processing commands for cont...@bugs.debian.org: > affects 921779 + src:fltk1.3 src:frobby Bug #921779 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #920459 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921299 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921783 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921789 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921802 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921838 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Added indication that 921779 affects src:fltk1.3 and src:frobby Added indication that 920459 affects src:fltk1.3 and src:frobby Added indication that 921299 affects src:fltk1.3 and src:frobby Added indication that 921783 affects src:fltk1.3 and src:frobby Added indication that 921789 affects src:fltk1.3 and src:frobby Added indication that 921802 affects src:fltk1.3 and src:frobby Added indication that 921838 affects src:fltk1.3 and src:frobby > thanks Stopping processing here. Please contact me if you need assistance. -- 920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459 921299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921299 921779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921779 921783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921783 921789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921789 921802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921802 921838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?
Le jeudi, 21 février 2019, 15.28:23 h CET Ian Jackson a écrit : > Back in the wider world, of course many people build packages on > Debian systems for installation `somewhere else'. I have done it > myself and probably many of the people reading this message have too. > > What is implicitly going on here is that it is mostly-tacitly[2] being > assumed (or declared) that `I built this .deb on my laptop[1] and gave > it to my friend' is wrongheaded. I don't think it is wrongheaded, but I do think that assuming that it is meant to work consistently under any circumstances, is. There are _so many_ circumstances that make this exercise error-prone: "I built this amd64 .deb and gave it to my friend for use on their RasbperryPi arm64 host" "I built this .deb on my laptop on which I had installed a /usr/local/bin/ grep" "I built this .deb an gave it to my friend who runs CentOS" etc > I don't think doing that is wrongheaded. Certainly it is extremely > common; we don't have any public pronouncements saying it is somehow > wrong; and we have had little discussion where we as a project decided > that this was now a use case which we feel free to just break. Frankly, while it's not _broken_ per se, it is and has always really been fragile. True, merged-/usr arguably worsens _one_ aspect of building packages on one's host, but in ways that are really easy to detect, and warn for. > Personally I think that this is a very important thing to keep > working. It is the very core of users' collective software freedom. You seem to be conflating "building on one's host" with "outside of any chroot", and equating this with "users' collective software freedom" is really making your point a disservice. Being able to improve, build and share binary artifacts of free software is _vital_, and the whole point of building software distributions in the first place, but insisting that these rights are only "truly" exercised when builds are done outside of chroots is disingenuine. .deb packages already have to be built using certain tools, so we do set the limit (of what minimal set of tools are mandatory) somewhere, and my point is that this limit might not be at the right place. I'd be totally OK with saying "the only supported way to build .deb packages from buster on is using by pdebuild; however, you _can_ use dpkg-buildpackage alone, but be aware (and you'll get warnings) that this can lead to building .deb packages with undesireable properties." The second half of the sentence is already true, and has always been; we probably just failed at communicating it sufficiently clearly. > And that software freedom needs to be easy to exercise in practice. > Despite a lot of excellent tooling, chroots are still not entirely > trivial to set up and maintain. Then that's maybe what we should be fixing. > I would invite the TC to read this manpage, which is trying to explain > to a Debian user how to change the programs on their own computer > https://manpages.debian.org/stretch-backports/dgit/dgit-user.7.en.html > and then consider how much even worse it would be if we had to write > about chroots too. Perhaps dpkg-buildpackage should be grown to build in a chroot by default? Or get an option to do that? Really, I think we should stop considering that .debs built outside of "controlled environments" are more than temporary software transports. Our "standard" package building tools should build in such environments by default. > To TC members who are minded to uphold the current approach, I would > ask: can you please explicitly state your opinion on this ? That is: > > Is it OK for a Debian user to build .deb on their laptop and give it > to their friend ? Yes; provided that said .deb is built in a sane (sanitized / controlled) environment. As you're talking about non-chroot builds; it is OK, provided that the tools warn about that. In that area, I think the "Build-Tainted-By" are steps in the right direction. > If it is OK, how will we make sure that it does not pointlessly break ? As it is already broken in many ways, your question is biased. But I think the good way is to normalize "proper builds", by making sure our standard tools "do the right thing" by default. > I readily admit that there are many ways that this can produce a > result significantly different to the official Debian package, > particularly because the package build system may configure itself > differently in the the presence of unexpected. The resulting package > is probably not going to be suitable for wide distribution. > > But those kind of problems are (a) not serious in practice > (b) generally have obvious symptoms and (c) are easily worked around > by various means. Working around a usrmerge-generated failure is > difficult; it usually involves doing serious violence to the upstream > build system, or perhaps horrific rules file bodges. Given a Build-Tainted-By flag in the binary artifact
Processed: affects 921779
Processing commands for cont...@bugs.debian.org: > affects 921779 + src:qevercloud Bug #921779 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #920459 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921299 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921783 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921789 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921802 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921838 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Added indication that 921779 affects src:qevercloud Added indication that 920459 affects src:qevercloud Added indication that 921299 affects src:qevercloud Added indication that 921783 affects src:qevercloud Added indication that 921789 affects src:qevercloud Added indication that 921802 affects src:qevercloud Added indication that 921838 affects src:qevercloud > thanks Stopping processing here. Please contact me if you need assistance. -- 920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459 921299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921299 921779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921779 921783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921783 921789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921789 921802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921802 921838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#917030: marked as done (python-pykmip: CVE-2018-1000872)
Your message dated Sun, 24 Feb 2019 18:20:16 + with message-id and subject line Bug#917030: fixed in python-pykmip 0.7.0-3 has caused the Debian Bug report #917030, regarding python-pykmip: CVE-2018-1000872 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.) -- 917030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917030 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pykmip Version: 0.7.0-2 Severity: important Tags: patch security upstream Forwarded: https://github.com/OpenKMIP/PyKMIP/issues/430 Hi, The following vulnerability was published for python-pykmip. CVE-2018-1000872[0]: | OpenKMIP PyKMIP version All versions before 0.8.0 contains a CWE 399: | Resource Management Errors (similar issue to CVE-2015-5262) | vulnerability in PyKMIP server that can result in DOS: the server can | be made unavailable by one or more clients opening all of the | available sockets. This attack appear to be exploitable via A client | or clients open sockets with the server and then never close them. | This vulnerability appears to have been fixed in 0.8.0. 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-2018-1000872 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000872 [1] https://github.com/OpenKMIP/PyKMIP/issues/430 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: python-pykmip Source-Version: 0.7.0-3 We believe that the bug you reported is fixed in the latest version of python-pykmip, 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 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated python-pykmip 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: Sun, 24 Feb 2019 17:30:07 +0100 Source: python-pykmip Binary: python-pykmip python3-pykmip Architecture: source all Version: 0.7.0-3 Distribution: unstable Urgency: high Maintainer: Debian OpenStack Changed-By: Thomas Goirand Description: python-pykmip - implementation of the Key Management Interoperability Protocol - python3-pykmip - KMIP v1.1 library - Python 3.x Closes: 917030 Changes: python-pykmip (0.7.0-3) unstable; urgency=high . [ Ondřej Nový ] * d/control: Add trailing tilde to min version depend to allow backports * d/control: Use team+openst...@tracker.debian.org as maintainer . [ Thomas Goirand ] * CVE-2018-1000872: Resource Management Errors (similar issue to CVE-2015-5262) vulnerability in PyKMIP server that can result in DOS: the server can be made unavailable by one or more clients opening all of the available sockets. Applied upstream patch: Fix a denial-of-service bug by setting the server socket timeout (Closes: #917030). Checksums-Sha1: b2588a52063c45accae7c3b2414389a6db3bc9ef 2579 python-pykmip_0.7.0-3.dsc 1d05b65a003a46a26d4a84dba7b30e57ea0b9b19 5284 python-pykmip_0.7.0-3.debian.tar.xz f36446db24f2420c5c553ad1ff0295fef682ff3f 123156 python-pykmip_0.7.0-3_all.deb 1c469c30a3ef3cdd33167e427f48bd122e6f 9395 python-pykmip_0.7.0-3_amd64.buildinfo 774d34b0d8ecaf4f5b66e96c020ba75c78a37305 118328 python3-pykmip_0.7.0-3_all.deb Checksums-Sha256: 83045bb9bb0ff5b50bc70b6550e60117d19bd6e84db781895ce806c261424dd7 2579 python-pykmip_0.7.0-3.dsc 788e357347de57d6c97c9c2cd28d58092c0f455b0ab3576574731eeb751e134e 5284 python-pykmip_0.7.0-3.debian.tar.xz 3d64d97c3bb0e12bd8b6a510df6fd1448e97a57d54891fbfb7ebdb6ca4fac934 123156 python-pykmip_0.7.0-3_all.deb f10d18f6a9364d92eb5c1a1a5e029673dd1b944ada48bfab428813d818360ec0 9395 python-pykmip_0.7.0-3_amd64.buildinfo 3c328101d17d7f317cea86f85e30dd7a8d8cf0d5f22b32f9ffab989ccf10d987 118328 python3-pykmip_0.7.0-3_all.deb Files: 0abcd1c94ad4fc247d6d079f94ce9ad0 2579 python optional python-pykmip_0.7.0-3.dsc 87009bc93fb7d27494a46ef45725df76 5284 python optional python-pykmip_0.7.0-3.debian.tar.xz 6c445e5437f91ffaec59f71c99bc3417 123156
Bug#921294: No need to block buster
Control: severity 921297 normal Control: severity 921298 normal Control: severity 921294 normal Control: severity 921300 normal As the new doxygen will not make it into buster (as apparently, it causes major breakage), there is no need to block reverse dependencies as long as they build with the doxygen currently in buster. (Mind that they actually do *not* currently build, but for anotehr reason - see #921779). signature.asc Description: PGP signature
Processed: No need to block buster
Processing control commands: > severity 921297 normal Bug #921297 [src:qevercloud] qevercloud: FTBFS with upcoming doxygen 1.8.15 Severity set to 'normal' from 'serious' > severity 921298 normal Bug #921298 [src:libstxxl] libstxxl: FTBFS with upcoming doxygen 1.8.15 Severity set to 'normal' from 'serious' > severity 921294 normal Bug #921294 [src:fltk1.3] fltk1.3: FTBFS with upcoming doxygen 1.8.15 Severity set to 'normal' from 'serious' > severity 921300 normal Bug #921300 [frobby] frobby: FTBFS with upcoming doxygen 1.8.15 Severity set to 'normal' from 'serious' -- 921294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921294 921297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921297 921298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921298 921300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922863: tomcat8: post-installation script subprocess failed during upgrade
Control: tag -1 + moreinfo unreproducible Control: severity -1 important Hi, > During upgrade: > > [...] > Setting up tomcat8 (8.5.38-1) ... > [ ok ] Stopping Tomcat servlet engine: tomcat8. > [FAIL] Starting Tomcat servlet engine: tomcat8 failed! > invoke-rc.d: initscript tomcat8, action "restart" failed. > dpkg: error processing package tomcat8 (--configure): > installed tomcat8 package post-installation script subprocess returned error > exit status 1 > [...] > Errors were encountered while processing: > tomcat8 > E: Sub-process /usr/bin/dpkg returned an error code (1) > Setting up tomcat8 (8.5.38-1) ... > [FAIL] Starting Tomcat servlet engine: tomcat8 failed! > invoke-rc.d: initscript tomcat8, action "restart" failed. > dpkg: error processing package tomcat8 (--configure): > installed tomcat8 package post-installation script subprocess returned error > exit status 1 > Errors were encountered while processing: > tomcat8 I cannot reproduce this under systemd. Can you please provide more details from your system that show why this might fail? You can edit /var/lib/dpkg/info/tomcat8.postinst and add a set -x near the set -e at the top, then dpkg-reconfigure tomcat8, for example. -nik signature.asc Description: PGP signature
Processed: Re: tomcat8: post-installation script subprocess failed during upgrade
Processing control commands: > tag -1 + moreinfo unreproducible Bug #922863 [tomcat8] tomcat8: post-installation script subprocess failed during upgrade Added tag(s) unreproducible and moreinfo. > severity -1 important Bug #922863 [tomcat8] tomcat8: post-installation script subprocess failed during upgrade Severity set to 'important' from 'grave' -- 922863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921030: Fails to import the ansible module since its migration to Python 3
Hi Samuel, On Sun, Feb 24, 2019 at 03:25:26AM +, Samuel Henrique wrote: > I'm working on this: https://salsa.debian.org/debian/ansible-lint > I think i'm close to an upload now, there's only some problems with .js > sources. I review your patches and all is right, in particular your removal of docs in upstream tarball. Thank you for your work! Regards, -- Grégory Colpart
Bug#915559: Heads up on the inactivity.
Dear maintainer This bug is probably very the root-cause to the following bug chain: ThisBug#915559: coreutils: Use renameat2 from glibc instead of syscall Leading to: Bug#921924: fakechroot: mv(1) cannot be used inside fakechroot Leading to: Bug#922572: debootstrap variant fakeroot fails due to dash diversion. And maybe a heap load of others so is it possible to get it fixed. /Regards /P
Bug#920459: tabu: breaks with color and/or xcolor when spread or negative X coefficients are used
retitle 920459 tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
found 920459 2018.20190131-1
forwarded 920459 https://github.com/tabu-fixed/tabu/pull/14
tags 920459 + patch
thanks
Hi Norbert,
please find attached a patch that fixes tabu when either color or
xcolor are used in a document and tabu is used with either stretch
(instead of to) or negative X column coëfficients. I’ve also for‐
warded this upstream.
I would appreciate a quick review, as this is blocking multiple
other packages and release-critical, and would prefer to upload
this within five days or so. If you can give me a go I can do a
maintainer-approved undelayed NMU. If I don’t hear anything back,
I intend to do a regular delayed NMU in five days. I’ve tested
this by rebuilding src:bliss twice, once without once with this
patch applied, failing the former but passing the latter.
Thanks,
//mirabilos
--
[17:15:07] Lukas Degener: Kleines Asterix-Latinum für Softwaretechniker:
veni, vidi, fixi(t) ;-)diff -Nru texlive-extra-2018.20190131/debian/changelog
texlive-extra-2018.20190131/debian/changelog
--- texlive-extra-2018.20190131/debian/changelog2019-01-31
04:55:18.0 +0100
+++ texlive-extra-2018.20190131/debian/changelog2019-02-24
17:47:26.0 +0100
@@ -1,3 +1,10 @@
+texlive-extra (2018.20190131-1.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * Patch tabu to fix multiple FTBFS in other packages (Closes: #920459)
+
+ -- Thorsten Glaser Sun, 24 Feb 2019 17:47:26 +0100
+
texlive-extra (2018.20190131-1) unstable; urgency=medium
* new upstream checkout
diff -Nru texlive-extra-2018.20190131/debian/patches/fix-tabu-920459
texlive-extra-2018.20190131/debian/patches/fix-tabu-920459
--- texlive-extra-2018.20190131/debian/patches/fix-tabu-920459 1970-01-01
01:00:00.0 +0100
+++ texlive-extra-2018.20190131/debian/patches/fix-tabu-920459 2019-02-24
17:47:21.0 +0100
@@ -0,0 +1,23 @@
+# DP: see #920459 and https://github.com/tabu-fixed/tabu/issues/1
+# DP: forwarded as https://github.com/tabu-fixed/tabu/pull/14
+
+--- a/texmf-dist/source/latex/tabu/tabu.dtx
b/texmf-dist/source/latex/tabu/tabu.dtx
+@@ -6099,6 +6099,7 @@ morekeywords=[7]{yellow},
+ \ifdim \tabu@temp\p@>\z@ \ifdim \tabu@temp\tabucolX<\tabu@target
+ \tabu@target=\tabu@temp\tabucolX
\fi\fi
+ \setbox\tabu@box \hbox \bgroup
++\color@begingroup%
+ \begin{varwidth}\tabu@target
+ \let\FV@ListProcessLine \tabu@FV@ListProcessLine % \hbox to
natural width...
+ \narrowragged \arraybackslash \parfillskip \@flushglue
+--- a/texmf-dist/tex/latex/tabu/tabu.sty
b/texmf-dist/tex/latex/tabu/tabu.sty
+@@ -1663,6 +1663,7 @@
+ \ifdim \tabu@temp\p@>\z@ \ifdim \tabu@temp\tabucolX<\tabu@target
+ \tabu@target=\tabu@temp\tabucolX
\fi\fi
+ \setbox\tabu@box \hbox \bgroup
++\color@begingroup%
+ \begin{varwidth}\tabu@target
+ \let\FV@ListProcessLine \tabu@FV@ListProcessLine % \hbox to
natural width...
+ \narrowragged \arraybackslash \parfillskip \@flushglue
diff -Nru texlive-extra-2018.20190131/debian/patches/series
texlive-extra-2018.20190131/debian/patches/series
--- texlive-extra-2018.20190131/debian/patches/series 2018-12-11
04:24:38.0 +0100
+++ texlive-extra-2018.20190131/debian/patches/series 2019-02-24
17:44:44.0 +0100
@@ -4,3 +4,4 @@
tmp-dir-for-pdfjam
sympytex-path
fix-gbrief-multiple
+fix-tabu-920459
Processed: tabu: breaks with color and/or xcolor when spread or negative X coefficients are used
Processing commands for cont...@bugs.debian.org: > retitle 920459 tabu: breaks with color and/or xcolor when spread or negative > X coefficients are used Bug #920459 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921299 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921779 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921783 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921789 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921802 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Bug #921838 [texlive-latex-extra] tabu.sty: Breaks with xcolor in many circumstances Changed Bug title to 'tabu: breaks with color and/or xcolor when spread or negative X coefficients are used' from 'tabu.sty: Breaks with xcolor in many circumstances'. Changed Bug title to 'tabu: breaks with color and/or xcolor when spread or negative X coefficients are used' from 'tabu.sty: Breaks with xcolor in many circumstances'. Changed Bug title to 'tabu: breaks with color and/or xcolor when spread or negative X coefficients are used' from 'tabu.sty: Breaks with xcolor in many circumstances'. Changed Bug title to 'tabu: breaks with color and/or xcolor when spread or negative X coefficients are used' from 'tabu.sty: Breaks with xcolor in many circumstances'. Changed Bug title to 'tabu: breaks with color and/or xcolor when spread or negative X coefficients are used' from 'tabu.sty: Breaks with xcolor in many circumstances'. Changed Bug title to 'tabu: breaks with color and/or xcolor when spread or negative X coefficients are used' from 'tabu.sty: Breaks with xcolor in many circumstances'. Changed Bug title to 'tabu: breaks with color and/or xcolor when spread or negative X coefficients are used' from 'tabu.sty: Breaks with xcolor in many circumstances'. > found 920459 2018.20190131-1 Bug #920459 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921299 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921779 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921783 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921789 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921802 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921838 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Ignoring request to alter found versions of bug #920459 to the same values previously set Ignoring request to alter found versions of bug #921299 to the same values previously set Ignoring request to alter found versions of bug #921779 to the same values previously set Ignoring request to alter found versions of bug #921783 to the same values previously set Ignoring request to alter found versions of bug #921789 to the same values previously set Ignoring request to alter found versions of bug #921802 to the same values previously set Ignoring request to alter found versions of bug #921838 to the same values previously set > forwarded 920459 https://github.com/tabu-fixed/tabu/pull/14 Bug #920459 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921299 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921779 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921783 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921789 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921802 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Bug #921838 [texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or negative X coefficients are used Set Bug forwarded-to-address to 'https://github.com/tabu-fixed/tabu/pull/14'. Set Bug forwarded-to-address to 'https://github.com/tabu-fixed/tabu/pull/14'. Set Bug forwarded-to-address to 'https://github.com/tabu-fixed/tabu/pull/14'. Set Bug forwarded-to-address to 'https://github.com/tabu-fixed/tabu/pull/14'. Set Bug forwarded-to-address to 'https://github.com/tabu-fixed/tabu/pull/14'. Set Bug forwarded-to-address to 'https://github.com/tabu-fixed/tabu/pull/14'. Set Bug forwarded-to-address to 'https://github.com/tabu-fixed/tabu/pull/14'. > tags 920459 + patch Bug #920459 [texlive-latex-extra] tabu: breaks with color a
Bug#887140: libjogl2-java FTBFS on architectures that use zero (timeout)
libjogl2-java still FTBFS on armel, mips64el and mipsel. I don't know why the build process requires so much time on these platforms excluding mips64el which never built before. On mips the build succeeded after six hours. I don't believe that mips and arm architectures are really supported by upstream. We had to add several patches to change the build system and I doubt there are many users on arm[el] and mips[el] that need libjogl2-java. So as a workaround we could request the removal of binary packages from those architectures and simply stop building them. If someone has a better idea, please let us know, otherwise I will go ahead with this plan. Markus signature.asc Description: OpenPGP digital signature
Bug#914632: RFC: proposed fix for CVE-2018-19518 in uw-imap
söndag 30 december 2018 kl. 09:38:57 CET skrev Salvatore Bonaccorso: > There is an alternative approach wich was raised by Magnus in the > respective bug: https://bugs.debian.org/914632#12 (and see followup > from Moritz). So, is it OK to upload this (assuming there's no code out there that actually uses SET_RSHPATH or SET_SSHPATH)? (By no longer defining RSHPATH, rshpath doesn't get set by the following code and tcp_aopen() will return NIL without doing anything. #ifdef RSHPATH /* rsh path defined yet? */ if (!rshpath) rshpath = cpystr (RSHPATH); #endif ) -- Magnus Holmgrenholmg...@debian.org Debian Developer commit e644cfbd0aac25ef320912e58e0d37cb715b2b88 Author: Magnus Holmgren Date: Sun Jan 13 21:07:41 2019 +0100 [CVE-2018-19518] 2013_disable_rsh.patch (new): Disable access to IMAP mailboxes through running imapd over rsh (Closes: #914632). diff --git a/debian/changelog b/debian/changelog index b6960d1..cc7b885 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +uw-imap (8:2007f~dfsg-5+deb9u1) stretch-security; urgency=high + + * [CVE-2018-19518] 2013_disable_rsh.patch (new): Disable access to IMAP +mailboxes through running imapd over rsh, and therefore ssh (Closes: +#914632). Code using the library can enable it with tcp_parameters() +after making sure that the IMAP server name is sanitized. + + -- Magnus Holmgren Sun, 24 Feb 2019 19:45:23 +0100 + uw-imap (8:2007f~dfsg-5) unstable; urgency=low * 1006_openssl1.1_autoverify.patch (new): Use new features for diff --git a/debian/patches/2013_disable_rsh.patch b/debian/patches/2013_disable_rsh.patch new file mode 100644 index 000..7a68644 --- /dev/null +++ b/debian/patches/2013_disable_rsh.patch @@ -0,0 +1,11 @@ +--- a/src/osdep/unix/Makefile b/src/osdep/unix/Makefile +@@ -985,7 +985,7 @@ onceenv: +-DMD5ENABLE=\"$(MD5PWD)\" -DMAILSPOOL=\"$(MAILSPOOL)\" \ +-DANONYMOUSHOME=\"$(MAILSPOOL)/anonymous\" \ +-DACTIVEFILE=\"$(ACTIVEFILE)\" -DNEWSSPOOL=\"$(NEWSSPOOL)\" \ +- -DRSHPATH=\"$(RSHPATH)\" -DLOCKPGM=\"$(LOCKPGM)\" \ ++ -DLOCKPGM=\"$(LOCKPGM)\" \ +-DLOCKPGM1=\"$(LOCKPGM1)\" -DLOCKPGM2=\"$(LOCKPGM2)\" \ +-DLOCKPGM3=\"$(LOCKPGM3)\" > OSCFLAGS + echo $(BASELDFLAGS) $(EXTRALDFLAGS) > LDFLAGS diff --git a/debian/patches/series b/debian/patches/series index ced3fcc..80d69e8 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -9,3 +9,4 @@ 2012_krb5_multidev.patch 1005_poll.patch 1006_openssl1.1_autoverify.patch +2013_disable_rsh.patch signature.asc Description: This is a digitally signed message part.
