Bug#840094: blends-dev: Does not recognize multiline dependencies
Hi Andreas & all, On 09.11.2016 15:35, Andreas Tille wrote: >> We have a clear definition of how these files should look like, namely >> RFC822, and this also defines continuation lines. > > Unfortunately in this specific feature tasks files are not RFC822 > compliant, which sucks, yes. Its even not documented (I just checked > since I intended to document it at some point in time but can't find it > :-( ) If one of our main tools is not compliant with our documented specifications, and this may cause incomplete metapackages (which are one central part of the blend), then I would still rate this as an RC bug, independently of whether it is easy to fix or not. >> I would think that there is also a quick fix for it -- the tool already >> handles continuation lines for the tasks description, so one could >> probably just take that. I have no glue of all the Perl $@^!~ special >> chars, but wouldn't do it something like the attached patch (after >> removing the obvious errors from it)? >> >> Or something else just adopted from lines 556-562 of blends-gen-control? > > While I fully agree that we should fix this I'm not fully convinced how > to sensibly proceed here. The problematic thing is that we are quite > short before a release and if we might break metapackage creation in > some way we might get in trouble. I'm no Perl programmer myself (even > if I think your patch looks sensible) and so IMHO staying conservative > and add some line ending escapes could be the less invasive change. I checked my patch, and it does *not* work correctly, it will produce syntax errors in the debian/control file, if RFC822 continuation lines are used. For tasks that have all in one line, or that have metapackages, everything seems to be OK, however. > If you (and Bas and other readers here) think we should fix the issue > right now I'm fine if you apply the patch below and we should seriously > test the metapackage creation of each Blend *before* 2016-12-05. > > What do you think? I am ready to test and also to fix; however my know-how ends here. I don't know what is wrong with the fix. Just wondering, and starting to really get worried: None of the debian-blends maintainers has enough Perl knowledge to fix this? If we all do not know Perl, why do we use that language in one of our central tools? That sounds to me even more RC than the bug itself... Cheers Ole
Bug#842326: marked as done ([PATCH] [RC] Fix FTBS for when building against upcoming lirc-0.9.4)
Your message dated Thu, 10 Nov 2016 07:48:39 + with message-id and subject line Bug#842326: fixed in ncmpc 0.25-0.1 has caused the Debian Bug report #842326, regarding [PATCH] [RC] Fix FTBS for when building against upcoming lirc-0.9.4 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.) -- 842326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ncmpc Version:0.24-1 Lirc is undergoing a major update, and ncmpc fails to build against the new version. The problem is two-fold: the configure file needs an update, but the autoreconf setup in 0.24 is broken. The enclosed patch for the complete debian/directories are based on an update to latest upstream 0.25 - this fixes the autoreconf issues. The new patch introduced updates configure.ac and Makefile.am to use the new pkgconfig name. It also adds an autoreconf invocation to the build, building successfully against the new lirc. Note that this patch requires lirc 0.9.4+, it is not backwards-compatible. Cheers! --alec diff -rNU2 ncmpc-0.24/debian/changelog ncmpc-0.25/debian/changelog --- ncmpc-0.24/debian/changelog 2014-07-15 20:50:26.0 +0200 +++ ncmpc-0.25/debian/changelog 2016-10-28 07:07:22.284504344 +0200 @@ -1,2 +1,8 @@ +ncmpc (0.25-1) unstable; urgency=medium + + * New upstream release + + -- Alec Leamas Fri, 28 Oct 2016 07:05:23 +0200 + ncmpc (0.24-1) unstable; urgency=medium diff -rNU2 ncmpc-0.24/debian/control ncmpc-0.25/debian/control --- ncmpc-0.24/debian/control 2014-04-27 13:38:06.0 +0200 +++ ncmpc-0.25/debian/control 2016-10-28 07:09:01.705005546 +0200 @@ -3,5 +3,5 @@ Priority: optional Maintainer: Sebastian Harl -Build-Depends: debhelper (>= 7), dpkg-dev (>= 1.14.6), autotools-dev, libncursesw5-dev, libglib2.0-dev, liblircclient-dev, libmpdclient-dev (>= 2.5~), doxygen +Build-Depends: debhelper (>= 7), dpkg-dev (>= 1.14.6), autotools-dev, libncursesw5-dev, libglib2.0-dev, liblircclient-dev, libmpdclient-dev (>= 2.5~), doxygen, dh-autoreconf Standards-Version: 3.9.5 Homepage: http://mpd.wikia.com/wiki/Client:Ncmpc diff -rNU2 ncmpc-0.24/debian/patches/series ncmpc-0.25/debian/patches/series --- ncmpc-0.24/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ ncmpc-0.25/debian/patches/series 2016-10-28 07:27:45.233858444 +0200 @@ -0,0 +1 @@ +Use-correct-lirc-pkgconfig-name.patch diff -rNU2 ncmpc-0.24/debian/patches/Use-correct-lirc-pkgconfig-name.patch ncmpc-0.25/debian/patches/Use-correct-lirc-pkgconfig-name.patch --- ncmpc-0.24/debian/patches/Use-correct-lirc-pkgconfig-name.patch 1970-01-01 01:00:00.0 +0100 +++ ncmpc-0.25/debian/patches/Use-correct-lirc-pkgconfig-name.patch 2016-10-28 07:29:07.622541987 +0200 @@ -0,0 +1,40 @@ +Description: Use lirc instead of liblircclient0 pkg-config name + +Upcoming lirc-0.9-4 drops support for the old liblircclient0 +pkg-config name, leading to FTBS errors. + +Author: Alec Leamas + +--- ncmpc-0.25.orig/Makefile.am ncmpc-0.25/Makefile.am +@@ -7,7 +7,7 @@ AUTOMAKE_OPTIONS = foreign 1.11 dist-xz + AM_CPPFLAGS = \ + $(LIBMPDCLIENT_CFLAGS) \ + $(GLIB_CFLAGS) \ +- $(LIBLIRCCLIENT_CFLAGS) \ ++ $(LIRC_CFLAGS) \ + -DLOCALE_DIR=\""$(datadir)/locale"\"\ + -DSYSCONFDIR=\""$(sysconfdir)"\" + +@@ -69,7 +69,7 @@ src_ncmpc_LDADD = \ + $(CURSES_LIB) \ + $(LIBMPDCLIENT_LIBS) \ + $(GLIB_LIBS) \ +- $(LIBLIRCCLIENT_LIBS) ++ $(LIRC_LIBS) + + src_ncmpc_SOURCES = \ + src/Compiler.h \ +--- ncmpc-0.25.orig/configure.ac ncmpc-0.25/configure.ac +@@ -184,8 +184,8 @@ AC_ARG_ENABLE([lirc], + [Enable LIRC support]),, + [enable_lirc=no]) + if test x$enable_lirc = xyes; then +- PKG_CHECK_MODULES([LIBLIRCCLIENT], [liblircclient0],, +- [AC_MSG_ERROR([liblircclient0 not found])]) ++ PKG_CHECK_MODULES([LIRC], [lirc],, ++ [AC_MSG_ERROR([lirc not found])]) + AC_DEFINE([ENABLE_LIRC], [1], [Enable LIRC support]) + fi + diff -rNU2 ncmpc-0.24/debian/rules ncmpc-0.25/debian/rules --- ncmpc-0.24/debian/rules 2014-07-12 19:08:06.0 +0200 +++ ncmpc-0.25/debian/rules 2016-10-28 07:08:45.188675100 +0200 @@ -25,4 +25,5 @@ config.status: configure dh_testdir + dh_autoreconf ./configure --host=$(DEB_HOST_GNU_TYPE) \ --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr \ --- End Message --- --- Begin Message --- Source: ncmpc Source-Version: 0.25-0.1 We believe that the bug you reported is fixed in the latest version of ncmpc, 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#840094: blends-dev: Does not recognize multiline dependencies
Hi Bas, On Wed, Nov 09, 2016 at 06:27:13PM +0100, Sebastiaan Couwenberg wrote: > On 11/09/2016 03:35 PM, Andreas Tille wrote: > > If you (and Bas and other readers here) think we should fix the issue > > right now I'm fine if you apply the patch below and we should seriously > > test the metapackage creation of each Blend *before* 2016-12-05. > > > > What do you think? > > I think supporting the deb822 format should be a Blends release goal for > buster, I fully agree. I admit I did way less for blends-dev than I intended to do but other tasks that felt more urgent occupied all my Debian time. > it's indeed to late in the stretch dev cycle in my opinion. That would mean to lower the severity of #840094. Ole, are you OK with this? In addition we might mention this in the docs and publish it on the web page at least. Kind regards Andreas. -- http://fam-tille.de
Bug#840468: mame: FTBFS[arm64]: immediate value out of range 0 to 63
This should be fixed in gcc-6 6.2.0-13 now.
Bug#843838: Fail to access config file
Hi, the directory listing /etc/bacula: # ls -l /etc/bacula/ insgesamt 104 -rw-r- 1 root dirmngr 9343 Feb 20 2016 bacula-dir.conf -rw-r- 1 root bacula 9156 Aug 18 14:12 bacula-dir.conf.dist -rw-r- 1 root dirmngr 1024 Sep 29 2013 bacula-fd.conf -rw-r- 1 root root1127 Aug 18 14:12 bacula-fd.conf.dist -rw-r- 1 bacula dirmngr 3338 Sep 12 2014 bacula-sd.conf -rw-r- 1 bacula bacula 8070 Aug 18 14:12 bacula-sd.conf.dist -rw-r- 1 root dirmngr 175 Feb 24 2014 bat.conf -rw-r- 1 root bacula 180 Aug 18 14:12 bat.conf.dist -rw-r- 1 root dirmngr 172 Sep 29 2013 bconsole.conf -rw-r- 1 root bacula 266 Aug 18 14:12 bconsole.conf.dist -rw--- 1 root root 442 Feb 24 2014 common_default_passwords -rw--- 1 root dirmngr 442 Dez 12 2013 common_default_passwords.dist -rw-r- 1 root dirmngr 926 Okt 20 2014 filesets.conf drwxr-xr-x 2 root root4096 Nov 9 06:13 scripts -rw-r- 1 root dirmngr 3396 Sep 12 2014 server-ixion.conf -rw-r- 1 root dirmngr 3433 Mai 1 2014 server-neptun.conf -rw-r- 1 root dirmngr 583 Apr 18 2014 tray-monitor.conf -rw-r- 1 root dirmngr 583 Dez 12 2013 tray-monitor.conf.dist -rw-r- 1 root dirmngr 3590 Feb 20 2016 ws-merkur.conf -rw-r- 1 root dirmngr 3436 Mai 2 2014 ws-triton.conf -rw-r- 1 root dirmngr 3127 Mai 1 2014 ws-zaubermaus.conf CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#843838: Fail to access config file
Package: bacula-director Version: 7.4.4+dfsg-3 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, after upgrade baculu bacule-director don't start anymore. Nov 10 07:39:29 merkur systemd[1]: Starting Bacula Director Daemon service... Nov 10 07:39:29 merkur bacula-dir[24610]: bacula-dir: ERROR TERMINATION at parse_conf.c:919 Nov 10 07:39:29 merkur bacula-dir[24610]: Config error: Cannot open config file "/etc/bacula/bacula-dir.conf": Keine Berechtigung Nov 10 07:39:29 merkur bacula-dir[24610]: 10-Nov 07:39 bacula-dir: ERROR TERMINATION at parse_conf.c:919 Nov 10 07:39:29 merkur bacula-dir[24610]: Config error: Cannot open config file "/etc/bacula/bacula-dir.conf": Keine Berechtigung Nov 10 07:39:29 merkur systemd[1]: bacula-director.service: Control process exited, code=exited status=1 Nov 10 07:39:29 merkur systemd[1]: Failed to start Bacula Director Daemon service. Nov 10 07:39:29 merkur systemd[1]: bacula-director.service: Unit entered failed state. Nov 10 07:39:29 merkur systemd[1]: bacula-director.service: Failed with result 'exit-code'. - -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bacula-director depends on: ii bacula-common 7.4.4+dfsg-3 ii bacula-director-mysql 7.4.4+dfsg-3 ii bsd-mailx [mailx] 8.1.2-0.20160123cvs-3 ii init-system-helpers1.45 ii libc6 2.24-5 ii libcap21:2.25-1 ii libgcc11:6.2.0-10 ii libssl1.0.21.0.2j-1 ii libstdc++6 6.2.0-10 ii libwrap0 7.6.q-25 ii lsb-base 9.20161101 ii ucf3.0036 ii zlib1g 1:1.2.8.dfsg-2+b3 bacula-director recommends no packages. Versions of packages bacula-director suggests: pn bacula-doc - -- no debconf information -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYJBd7AAoJEAn4nzyModJdEP4QAI9Sud21FefTt6l0SXzBmBsq Fqu7EAF+0xgHUE0S+1JaVLV8DyjGtGNiQi06vKWC6AdExJG21MeoVmeQrs42pqYS 7kRfGNlUsvg/hYKQa+tO1pJcUW7Qw7uw9jbzUUA7s1jBecIBFi28V+s9W9ai0rtR Og46QbQ81j/x6P4OnZ86MM6L4/RbRxWq+C9QRo0NjGju52JSvtCFTjKdEGguBYSZ Wc0yCrI+L2Ncbh6WJqdp0xMA8B8vKQw12BrJxYur0E++ZBeXbNMGbAgnrfz3HvRJ qWxOmqO0R2Zh+ZdgHvdd50+Zm/IqiZVORd8lEoNd9T5KHYWrxBSei3yyNN+b0oGK nFgPm0YRpf3x6dKKkIuCov8Qg458rkbOWx45BJeU40BBkVovcBc7+wEvREfGLKgs CtamdWJUQtmu3tPUYh/4rloZdnq3rvY89tShGa6tUIWFblw85gl9zeVssrZo5OSC JorkJdn9HJ9KFunmqR4I0i+uaCdZOnLZD8YKBt1sK1GNxBP4XbIaEb7JnfZM2vrq ap7dH84sdXPHoLkX9vG6UcNYzFASR/0X0EbXeNWdEYBsZBG8VDdizam3oOu+zV9w 7nki7PHvQxinkLX8QIMVr5ZKCTIPUTv3pl9netMAy75/FhL89wgYrjBmL6aBhWLx RyqFIztZEZgYA344ldDc =hKUx -END PGP SIGNATURE-
Processed: bug 840824 is forwarded to https://github.com/aptinio/text-table/issues/14
Processing commands for cont...@bugs.debian.org: > forwarded 840824 https://github.com/aptinio/text-table/issues/14 Bug #840824 [src:ruby-text-table] ruby-text-table: FTBFS (failing tests) Set Bug forwarded-to-address to 'https://github.com/aptinio/text-table/issues/14'. > thanks Stopping processing here. Please contact me if you need assistance. -- 840824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 840824
Processing commands for cont...@bugs.debian.org: > tags 840824 + confirmed Bug #840824 [src:ruby-text-table] ruby-text-table: FTBFS (failing tests) Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 840824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 843614 in python-cryptography/1.5.3-1
Processing commands for cont...@bugs.debian.org: > notfound 843614 python-cryptography/1.5.3-1 Bug #843614 {Done: Tristan Seligmann } [python-cryptography] AttributeError: 'module' object has no attribute 'SSL_ST_INIT' No longer marked as found in versions python-cryptography/1.5.3-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 843614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843614: marked as done (AttributeError: 'module' object has no attribute 'SSL_ST_INIT')
Your message dated Thu, 10 Nov 2016 06:13:12 + with message-id and subject line Fixed in python-openssl has caused the Debian Bug report #843614, regarding AttributeError: 'module' object has no attribute 'SSL_ST_INIT' 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.) -- 843614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-cryptography Version: 1.5.3-1 Severity: grave Justification: renders package unusable Processes using python-twisted fail immediately that python-cryptography is upgraded and run normally when python-cryptography is downgraded back to 1.5.2-1 in testing. Traceback (most recent call last): File "/usr/bin/lava-server", line 77, in main() File "/usr/bin/lava-server", line 74, in main execute_from_command_line(django_options) File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 367, in execute_from_command_line utility.execute() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 359, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 294, in run_from_argv self.execute(*args, **cmd_options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 345, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/lava_scheduler_app/management/commands/scheduler.py", line 43, in handle from twisted.internet import reactor File "/usr/lib/python2.7/dist-packages/twisted/internet/reactor.py", line 38, in from twisted.internet import default File "/usr/lib/python2.7/dist-packages/twisted/internet/default.py", line 56, in install = _getInstallFunction(platform) File "/usr/lib/python2.7/dist-packages/twisted/internet/default.py", line 44, in _getInstallFunction from twisted.internet.epollreactor import install File "/usr/lib/python2.7/dist-packages/twisted/internet/epollreactor.py", line 24, in from twisted.internet import posixbase File "/usr/lib/python2.7/dist-packages/twisted/internet/posixbase.py", line 18, in from twisted.internet import error, udp, tcp File "/usr/lib/python2.7/dist-packages/twisted/internet/tcp.py", line 28, in from twisted.internet._newtls import ( File "/usr/lib/python2.7/dist-packages/twisted/internet/_newtls.py", line 21, in from twisted.protocols.tls import TLSMemoryBIOFactory, TLSMemoryBIOProtocol File "/usr/lib/python2.7/dist-packages/twisted/protocols/tls.py", line 41, in from OpenSSL.SSL import Error, ZeroReturnError, WantReadError File "/usr/lib/python2.7/dist-packages/OpenSSL/__init__.py", line 8, in from OpenSSL import rand, crypto, SSL File "/usr/lib/python2.7/dist-packages/OpenSSL/SSL.py", line 112, in SSL_ST_INIT = _lib.SSL_ST_INIT AttributeError: 'module' object has no attribute 'SSL_ST_INIT' 2016-11-08 10:02:13,934 Closing LAVA Daemon. $ dpkg -S /usr/lib/python2.7/dist-packages/OpenSSL/SSL.py python-openssl: /usr/lib/python2.7/dist-packages/OpenSSL/SSL.py python-openssl has not changed, but python-cryptography changed in todays sid upgrade. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf, arm64 Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-cryptography depends on: ii libc62.24-5 ii libssl1.0.2 1.0.2j-1 ii python 2.7.11-2 pn python-cffi-backend-api-max pn python-cffi-backend-api-min ii python-enum341.1.6-1 ii python-idna 2.1-1 ii python-ipaddress 1.0.17-1 ii python-pyasn10.1.9-2 ii python-setuptools28.7.1-1 ii python-six 1.10.0-3 pn python:any python-cryptography recommends no packages. Versions of packages python-cryptography suggests: pn python-cryptography-doc pn python-cryptography-vectors -- no debconf information --- End Message --- --- Begin Message --- Control: notfound -1 python-cryptography/1.5.3-1 This issue is fixed in python-openssl 16.2.0 (by the conditional import). If any downstream sof
Processed: fixed in new upload
Processing commands for cont...@bugs.debian.org: > fixed 840316 6.0.0+debian-3 Bug #840316 [diaspora] diaspora: fails to install: Could not find gem 'unicorn-worker-killer (~> 0.4.4)' There is no source info for the package 'diaspora' at version '6.0.0+debian-3' with architecture '' Unable to make a source version for version '6.0.0+debian-3' Marked as fixed in versions 6.0.0+debian-3. > End of message, stopping processing here. Please contact me if you need assistance. -- 840316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#840316: marked as done (diaspora: fails to install: Could not find gem 'unicorn-worker-killer (~> 0.4.4)')
Your message dated Thu, 10 Nov 2016 11:18:49 +0530 with message-id and subject line Re: diaspora: fails to install: Could not find gem 'unicorn-worker-killer (~> 0.4.4)' has caused the Debian Bug report #840316, regarding diaspora: fails to install: Could not find gem 'unicorn-worker-killer (~> 0.4.4)' 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.) -- 840316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: diaspora Version: 0.6.0.0+debian-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package diaspora. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 33691 files and directories currently installed.) Preparing to unpack .../diaspora_0.6.0.0+debian-2_all.deb ... You already have a PostgreSQL database named 'diaspora_production'... Unpacking diaspora (0.6.0.0+debian-2) ... Setting up diaspora (0.6.0.0+debian-2) ... Setting up environment varibales... Using /etc/diaspora.conf... export DB_NAME=diaspora_production RAILS_ENV=production DB=postgres ENVIRONMENT_URL=https://localhost Verifying we have all required libraries... Could not find gem 'unicorn-worker-killer (~> 0.4.4)' in any of the gem sources listed in your Gemfile or available on this machine. dpkg: error processing package diaspora (--configure): subprocess installed post-installation script returned error exit status 7 Errors were encountered while processing: diaspora cheers, Andreas diaspora_0.6.0.0+debian-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#842515: marked as done (github-backup: FTBFS with newer directory)
Your message dated Thu, 10 Nov 2016 05:33:37 + with message-id and subject line Bug#842515: fixed in github-backup 1.20160522-2 has caused the Debian Bug report #842515, regarding github-backup: FTBFS with newer directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 842515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: github-backup Version: 1.20160522-1 Severity: serious Because we've updated GHC to 8.0, the version of the directory library has also been updated, and you'll need something like https://github.com/joeyh/github-backup/commit/848f6b64f75f4d267ba364405fb2a7b284969020 --- End Message --- --- Begin Message --- Source: github-backup Source-Version: 1.20160522-2 We believe that the bug you reported is fixed in the latest version of github-backup, 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 842...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James McCoy (supplier of updated github-backup package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 10 Nov 2016 00:22:04 -0500 Source: github-backup Binary: github-backup Architecture: source Version: 1.20160522-2 Distribution: unstable Urgency: medium Maintainer: James McCoy Changed-By: James McCoy Description: github-backup - backs up data from GitHub Closes: 842515 Changes: github-backup (1.20160522-2) unstable; urgency=medium . * Add remove-System.Directory-import patch to fix build with recent directory module. (Closes: #842515) Checksums-Sha1: 3f1966950b951cf1382158f0dbf6717335f1d9c3 2254 github-backup_1.20160522-2.dsc 18a2c34d3d983abe80e09498ea76cb3825fc73c9 4924 github-backup_1.20160522-2.debian.tar.xz Checksums-Sha256: 0283a58e8c2fad7fae2302176fd79990ca061a1251c503e595312c0d55e0bfdc 2254 github-backup_1.20160522-2.dsc f9155cb2bf1229f584f9e0dc2ad0c3fa23c038a94a412f339cbb476bbaac01fe 4924 github-backup_1.20160522-2.debian.tar.xz Files: ac62069fdca88359ddfe4cd57501b7d7 2254 utils optional github-backup_1.20160522-2.dsc 8166a6c613dde5c6bdc3187575a6cd27 4924 utils optional github-backup_1.20160522-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJ8BAEBCgBmBQJYJATKXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ5MUJGQkY0RDY5NTZCRDVERjdCNzJEMjNE RkU2OTFBRTMzMUJBM0RCAAoJEN/mka4zG6PbVV4QALDvSD5x+HntFGW073LP/CRp F631rlabNGiOU7kbQTbS8I/BuLfH8dqsQVAFtqfbXjzVj6zX/oD+IUOeA7ZN6P4x yBECLRFGpmvi3GpHOgqcGtbH/gAQVouUKAAlOV++73NrQjXWuwl3h1yPn1uQUtrP ALy5egHhkYB9feAdxbrg95Ou4LcOvXyqAHnfl4K5gfvpeZHUpft0N2+eTT0pPXcB poRTekDauaigLPb4y0e8aAyg01yhH2MpHPwvkg4FquNLsg5CqkARCmR2NYDQF3Tz 0Bj/2IG4ubKdxfiYWpjhzj1/j8dNe3Bp6FWj1BrvP2T4nMkvvuQZQ7vQfkseTnRJ ltl9QI1GcAP3/5DXj6yshmd5oOEYhbv/grwo98Pxi1GMSAtXtAkLsZFQaxfp/3y6 dFKwq6xZf85P3Hn8CHCcNolTZnSB+EwAZ8FIi10kwwknLo7n6qXiM/sKhtD84yI2 2M8esdFPOGNzqht4mIGTVFX1f72xFbXq+9g9skMav9yxemstfc5SpBCs4Aj2JloI SU7nxdElaHfGFFf76HEEqsVDcunKxLkPqR9b+HdUFe9O3Ns88pJmnYACliIKK6kI Bq5R8l4gV03p5Js8OUz9k8idRyLs4NKkwNfor6nbiLHou0TOVIL0Ty13ezID1t36 OToOBk4yg33wPjAQg6lv =dPRe -END PGP SIGNATURE End Message ---
Bug#842394: marked as done (haskell-cabal: this version should not be released with stretch)
Your message dated Thu, 10 Nov 2016 05:21:23 + with message-id <20161110052123.ga16...@scru.org> and subject line newer Cabal has caused the Debian Bug report #842394, regarding haskell-cabal: this version should not be released with stretch 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.) -- 842394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-cabal Version: 1.22.8.0-1 Severity: serious stretch should be released either without the haskell-cabal package or with a newer version than is shipped with ghc --- End Message --- --- Begin Message --- Version: 1.24.1.0-1 This one can go in.--- End Message ---
Bug#842515: github-backup: FTBFS with newer directory
On Sat, Oct 29, 2016 at 10:46:24PM +, Clint Adams wrote: > Because we've updated GHC to 8.0, the version of the directory library > has also been updated, and you'll need something like > https://github.com/joeyh/github-backup/commit/848f6b64f75f4d267ba364405fb2a7b284969020 That's already included in the latest release ... I'm finally able to install all the build-deps again, so I'll see where else things are breaking. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#843614: Fixed in python-openssl 16.2.0-1?
Hi, I was able to use torbrowser-launcher again after upgrading python-openssl to 16.2.0-1. The new version ensures that SSL_ST_INIT is defined before referencing it. I don't know if that's considered a fix for this issue, though. -- Matt https://ftbfs.org/~kraai/
Bug#842878: Asterisk crashes with pjproject 2.5.5
OK, confirmed. The patch (r5401) works, we're back with the previous behavior: [Nov 9 20:43:33] ERROR[14871]: res_pjsip.c:2883 ast_sip_create_dialog_uac: Could not create dialog to endpoint '' as URI '' is not valid [Nov 9 20:43:33] ERROR[14871]: chan_pjsip.c:1947 request: Failed to create outgoing session to endpoint '' [Nov 9 20:43:33] WARNING[14935][C-0001]: app_dial.c:2524 dial_exec_full: Unable to create channel of type 'PJSIP' (cause 3 - No route to destination) [Nov 9 20:43:33] ERROR[14871]: res_pjsip.c:2883 ast_sip_create_dialog_uac: Could not create dialog to endpoint '' as URI '' is not valid [Nov 9 20:43:33] ERROR[14871]: chan_pjsip.c:1947 request: Failed to create outgoing session to endpoint '' [Nov 9 20:43:33] WARNING[14935][C-0001]: app_dial.c:2524 dial_exec_full: Unable to create channel of type 'PJSIP' (cause 3 - No route to destination) And the call goes through just fine. I guess the problem you had when reproducing the issue was another problem. Probably including some more of the upstream patches would be a good measure indeed.
Bug#822749: heimdal ftbfs on all 32bit architectures
Package: heimdal Version: 1.7~git20160703+dfsg-1 Followup-For: Bug #822749 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu zesty ubuntu-patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * debian/patches/use_off_t_for_constants.patch: Use off_t in for constants used in iprop log seeks. Thanks to Nicolas Williams . Closes: #822749, LP: #1629055. Thanks for considering the patch. diff -Nru heimdal-1.7~git20160703+dfsg/debian/patches/series heimdal-1.7~git20160703+dfsg/debian/patches/series --- heimdal-1.7~git20160703+dfsg/debian/patches/series 2016-07-03 07:28:39.0 -0700 +++ heimdal-1.7~git20160703+dfsg/debian/patches/series 2016-11-09 17:02:46.0 -0800 @@ -16,3 +16,4 @@ 061_disable_test_plugin 062_disable_test_iprop parallel-build +use_off_t_for_constants.patch diff -Nru heimdal-1.7~git20160703+dfsg/debian/patches/use_off_t_for_constants.patch heimdal-1.7~git20160703+dfsg/debian/patches/use_off_t_for_constants.patch --- heimdal-1.7~git20160703+dfsg/debian/patches/use_off_t_for_constants.patch 1969-12-31 16:00:00.0 -0800 +++ heimdal-1.7~git20160703+dfsg/debian/patches/use_off_t_for_constants.patch 2016-11-09 17:05:47.0 -0800 @@ -0,0 +1,35 @@ +Description: Use off_t in for constants used in iprop log seeks + On 32-bit architectures with _FILE_OFFSET_BITS=64, + sizeof(off_t) > sizeof(size_t) . + . + LOG_HEADER_SZ was #define'd as an expression of type size_t, so in + order to get the sign extension right we need -(off_t)LOG_HEADER_SZ + instead of (off_t)(-LOG_HEADER_SZ). However, we can just define the + *_SZ macros to cast to off_t, then we don't need to worry about + negation. +Author: Nicolas Williams +Origin: upstream, https://github.com/heimdal/heimdal/commit/7c8b66d76b562912c09c0955a53da2f26afbc8f7 +Bug: https://github.com/heimdal/heimdal/issues/175 +Bug-Debian: https://bugs.debian.org/822749 +Bug-Ubuntu: https://launchpad.net/bugs/1629055 +Last-Update: 2016-11-10 + +--- heimdal-1.7~git20160703+dfsg.orig/lib/kadm5/log.c heimdal-1.7~git20160703+dfsg/lib/kadm5/log.c +@@ -174,11 +174,11 @@ RCSID("$Id$"); + * will deadlock with ipropd-slave -- don't do that. + */ + +-#define LOG_HEADER_SZ (sizeof(uint32_t) * 4) +-#define LOG_TRAILER_SZ (sizeof(uint32_t) * 2) +-#define LOG_WRAPPER_SZ (LOG_HEADER_SZ + LOG_TRAILER_SZ) +-#define LOG_UBER_LEN(sizeof(uint64_t) + sizeof(uint32_t) * 2) +-#define LOG_UBER_SZ (LOG_WRAPPER_SZ + LOG_UBER_LEN) ++#define LOG_HEADER_SZ ((off_t)(sizeof(uint32_t) * 4)) ++#define LOG_TRAILER_SZ ((off_t)(sizeof(uint32_t) * 2)) ++#define LOG_WRAPPER_SZ ((off_t)(LOG_HEADER_SZ + LOG_TRAILER_SZ)) ++#define LOG_UBER_LEN((off_t)(sizeof(uint64_t) + sizeof(uint32_t) * 2)) ++#define LOG_UBER_SZ ((off_t)(LOG_WRAPPER_SZ + LOG_UBER_LEN)) + + #define LOG_NOPEEK 0 + #define LOG_DOPEEK 1 -- System Information: Debian Release: stretch/sid APT prefers yakkety-updates APT policy: (500, 'yakkety-updates'), (500, 'yakkety-security'), (500, 'yakkety'), (400, 'yakkety-proposed') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-26-generic (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Nishanth Aravamudan Ubuntu Server Canonical Ltd
Bug#842878: Asterisk crashes with pjproject 2.5.5
r5401 seems to be the fix: https://trac.pjsip.org/repos/ticket/1946 However I'm having trouble adding a patch with this source package :-(
Bug#842878: Asterisk crashes with pjproject 2.5.5
On 11/09/2016 06:26 PM, Gedalya wrote: > asterisk: ../src/pjsip/sip_auth_client.c:507: pjsip_auth_clt_deinit: > Assertion `sess && sess->endpt' failed. > Aborted > > This is me calling myself via my outbound trunk and coming back in via my > inbound trunk. > The problem comes up only on the inbound calls, at the point where I dial > them to the phones and other devices. > If I just call e.g. my mobile phone it works fine, I can complete the call > and asterisk continues fine. Per [0] + google translate and testing and confirming locally, the problem is isolated to missing (not currently registered) SIP peers. Making sure the Dial() app is only dialing registered and available peers makes the problem go away. Next step would be to see if there is a patch upstream addressing this. [0] https://forum.asterisk.ru/viewtopic.php?f=5&t=7772&start=10
Bug#842939: marked as done (xul-ext-wot: WOT find guilty to sell user data)
Your message dated Thu, 10 Nov 2016 00:21:33 + with message-id and subject line Bug#842939: fixed in wot 20151208-3 has caused the Debian Bug report #842939, regarding xul-ext-wot: WOT find guilty to sell user data 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.) -- 842939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xul-ext-wot Severity: important Hi, I'm setting this bug only to important even if it should be probably be RC. However, I have no technical proof for my claim just a German news story who found evidence that WOT is selling large user data sets to private companies. If you understand German please have a look at http://www.ndr.de/nachrichten/netzwelt/Nackt-im-Netz-Millionen-Nutzer-ausgespaeht,nacktimnetz100.html In case you agree that this is critical I think this addon should be removed from Debian. I'm also wondering about other addons like add blockers whether these are doing the same since they probably also get all user URLs in their hand. Kind regards Andreas. -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xul-ext-wot depends on: pn iceweasel xul-ext-wot recommends no packages. xul-ext-wot suggests no packages. --- End Message --- --- Begin Message --- Source: wot Source-Version: 20151208-3 We believe that the bug you reported is fixed in the latest version of wot, 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 842...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. W. Martin Borgert (supplier of updated wot 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: Wed, 09 Nov 2016 20:25:45 + Source: wot Binary: xul-ext-wot Architecture: source all Version: 20151208-3 Distribution: unstable Urgency: high Maintainer: Debian Mozilla Extension Maintainers Changed-By: W. Martin Borgert Description: xul-ext-wot - Transitional package to safely remove WOT Closes: 842939 Changes: wot (20151208-3) unstable; urgency=high . * Team upload * Removed all code, because this is malware (Closes: #842939) * Changed homepage to Debian wiki page about the malware incident * Minor changes Checksums-Sha1: c99a235f9064b2df81df5a57f012b64c342f7be8 1890 wot_20151208-3.dsc 39cea37d545817f100fb32218b27ca64efcbb85d 170524 wot_20151208-3.debian.tar.xz a1c1fd318e22bd701fe7e23038df256df9034c4f 4333 wot_20151208-3_20161110T000715z-198588a1.buildinfo 05937c43af3b341036b2e8ff40edde52602fdd9d 8022 xul-ext-wot_20151208-3_all.deb Checksums-Sha256: cdde0005ebf61912bfea583dc4703d34e2dbb3d0e418e32a9cf8d3a7429a4491 1890 wot_20151208-3.dsc 1b733135722bb820fe5df17e4a142aaa7c1386bee3c3ab57d7136a26545b4e67 170524 wot_20151208-3.debian.tar.xz 5828f657249f149566aa604b8be9fb3d6152620b813cd0888b19449339b65121 4333 wot_20151208-3_20161110T000715z-198588a1.buildinfo 2b1ca97418d08d0ce9c74ac51c75bcfbfaa315c78b2fd0cf94bf1247eab6c5b8 8022 xul-ext-wot_20151208-3_all.deb Files: fffdc5f4aa767a84fdf63fdf47d08ba6 1890 web optional wot_20151208-3.dsc 6591e91bb8bfd8c3ffb2911b239e3983 170524 web optional wot_20151208-3.debian.tar.xz 198588a136813fab5980ff7c36a25455 4333 web optional wot_20151208-3_20161110T000715z-198588a1.buildinfo bab1aa8a1f810fd385ecd7bcfc0a5b57 8022 web optional xul-ext-wot_20151208-3_all.deb -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJYI7pHAAoJEOPgocKGuWPqrRQP/3fAeSOae0MptaTluNWHvHfU QjHptWDHxWb1lGtRqiFJQlE6356RUr/VImwCuZxWemTfZlJxgti6VFkwds78C14b IxA47fnF/bKEaW4AkO0RYIzdzmFWvEAgWl6VNPIpDaPOtg2l+a05QM6zMbioJ0MR 2oAqRi7SWspZpXhFac2YNBQdwrU0iK/3pPIbbcuGzwkFgo5r4As0pQ8Ml38bLiDl S4HD1xqr0MB9vZVOd36JVV6RkaHq3Q8vvcbZhC1VNOO9U0xxNFNaxKN1x7j6VpLD ABuIf9EsTiBu7p+HVq+6yTZccWOCoVxxU6TICGNBK1W1tuuOIQyXJRw/u2pthvSZ j28ZWXLH7iij3ctxGQ1mSyvlcGV6r7E7k0fBjsgojR1lR774PIYuLOq+z0EZ2nnh tt3u
Bug#841257: sendmail: Privilege escalation from group smmsp to (user) root
Dear Andreas, > I have a completely untested patch sitting in GIT - do you have a > possibility to test packages built from that? I could replace files, or DEB packages, on some test machines. Do not know whether that testing would be exhaustive: do not know how many features of the sendmail package I use. Or if the changes are "small" then could just inspect. Cheers, Paul
Bug#842878: Asterisk crashes with pjproject 2.5.5
On 11/09/2016 04:51 AM, Bernhard Schmidt wrote: > I have now uploaded Asterisk 13.12.1~dfsg-1 into sid, should be built > and available within a few hours. This works well for me with pjproject > from sid. Maybe it really just needed a recompile, but you had already > tested that in the beginning. Would it be possible that something went > wrong there? I don't see what or how. I definitely rebuilt against the new pjproject. I'm getting the same problems now, with the new packages in the debian archive. Note that I can make outbound calls just fine. The problem is perhaps triggered by something specific in my inward dialing plan. This is with the new packages: -- Executing *desk-out:1] Goto("PJSIP/*-", "desk-out,*,1") in new stack -- Goto (desk-out,*,1) -- Executing [*@desk-out:1] Set("PJSIP/*-", "CALLERID(num)=*") in new stack -- Executing [*@desk-out:2] Goto("PJSIP/*-", "out-vitel,*,1") in new stack -- Goto (out-vitel,*,1) -- Executing [*@out-vitel:1] MixMonitor("PJSIP/*-", "/var/local/callrec/2016-11/1478733136.0.wav") in new stack == Begin MixMonitor Recording PJSIP/*- -- Executing [*@out-vitel:2] Set("PJSIP/*-", "CDR(peername)=*") in new stack -- Executing [*@out-vitel:3] Dial("PJSIP/*-", "PJSIP/*@trunk-didlogic") in new stack -- Called PJSIP/*@trunk-didlogic -- Executing [*@from-external:1] Goto("PJSIP/trunk-vitelity-in-0002", "internal,gedalya-all,1") -- Goto (internal,gedalya-all,1) -- Executing [gedalya-all@internal:1] Set("PJSIP/trunk-vitelity-in-0002", "CDR(peername)=trunk-vitelity-in") in new stack -- Executing [gedalya-all@internal:2] MixMonitor("PJSIP/trunk-vitelity-in-0002", "/var/local/callrec/2016-11/1478733137.2.wav") in new stack == Begin MixMonitor Recording PJSIP/trunk-vitelity-in-0002 -- Executing [gedalya-all@internal:3] Dial("PJSIP/trunk-vitelity-in-0002", "PJSIP/*&PJSIP/*&PJSIP/*&PJSIP/*&PJSIP/*,30") in new stack asterisk: ../src/pjsip/sip_auth_client.c:507: pjsip_auth_clt_deinit: Assertion `sess && sess->endpt' failed. Aborted This is me calling myself via my outbound trunk and coming back in via my inbound trunk. The problem comes up only on the inbound calls, at the point where I dial them to the phones and other devices. If I just call e.g. my mobile phone it works fine, I can complete the call and asterisk continues fine. I'll try patching pjproject now and see how that goes.
Bug#843711: biber: FTBFS (failing tests)
On Thu, Nov 10, 2016 at 12:41:39AM +0900, Norbert Preining wrote: > > But that'd be just bandaid IMO and a real fix would either revert the > > relevant Unicode::Collate change if it's a bug, or adapt biber to work > > If one could find out what the relevant change is. It is rather unfortunate > that the two version of the same things don't produce the same :-( % perl -MUnicode::Collate -le 'print $Unicode::Collate::VERSION, " ", Unicode::Collate->new->viewSortKey("Foo")' gives this output with the versions available on jessie and sid: 1.04 [1680 176D 176D | 0020 0020 0020 | 0008 0002 0002 | |] 1.07 [1680 176D 176D | 0020 0020 0020 | 0008 0002 0002 | |] 1.14 [19A9 1AA1 1AA1 | 0020 0020 0020 | 0008 0002 0002 | |] 1.17 [1C60 1D58 1D58 | 0020 0020 0020 | 0008 0002 0002 | |] So the U::C sort key generation has changed (again), and the biber test suite hardcodes md5sums of the old sort keys. Given https://github.com/plk/biber/commit/9bebd3ef0cb57b5ca4f15885d0cbfecc4939a835 I suspect biber just needs to adapt again. -- Niko Tyni nt...@debian.org
Bug#842939: Handling of "malware" in Debian
On 2016-11-09 18:44, Holger Levsen wrote: On Wed, Nov 09, 2016 at 07:14:45PM +0100, W. Martin Borgert wrote: If users of testing or unstable have the malware installed now and the package gets removed from the archive, users are left with the malware, right? yes That's why I thought about uploading an empty package to unstable, yes, of course. Whilst that's in progress, let's at least limit damage through new installations: jmw@respighi:~$ head -n 3 hints/jmw # 20161109 # #842939 damage limitation remove wot/20151208-2 A 'fixed' package can still migrate later. it should be released with stretch, but can be safely removed later. i'm not sure about the releasing with stretch part. Maybe it would be better to have the updated, empty package in stretch in 5plusX days and then remove it before the release, say on January 1st. Let's not actually release it, but a leaf package like this is trivially removed again. (Strictly speaking use of Stretch is still 'at own risk' and unsupported, so this is overkill, but it's small effort to be nice.) -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 i have six years of solaris sysadmin experience, from 8->10. i am well qualified to say it is made from bonghits layered on top of bonghits
Processed: Re: Bug#836595: ruby-celluloid-io: FTBFS randomly (failing tests)
Processing commands for cont...@bugs.debian.org: > retitle 836595 ruby-celluloid-io: FTBFS randomly (failing tests) Bug #836595 [src:ruby-celluloid-io] ruby-celluloid-io: FTBFS too much often (failing tests) Changed Bug title to 'ruby-celluloid-io: FTBFS randomly (failing tests)' from 'ruby-celluloid-io: FTBFS too much often (failing tests)'. > thanks Stopping processing here. Please contact me if you need assistance. -- 836595: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#836595: ruby-celluloid-io: FTBFS randomly (failing tests)
retitle 836595 ruby-celluloid-io: FTBFS randomly (failing tests) thanks (I never liked the "too much often" wording)
Bug#828236: Processed: tagging 828236
Hi Kurt, On Sunday, 25 September 2016 19:51:08 CET Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > > tags 828236 + patch > > Bug #828236 [src:apache2] apache2: FTBFS with openssl 1.1.0 > Added tag(s) patch. I am sorry, but I don't feel qualified to review that patch (or the upstream branch 2.4.x-openssl-1.1.0-compat which has a different implementation). In apache, there is lots of subtle interaction between TLS-renegotiation and access control. Therefore I want to have the patch reviewed by someone who knows mod_ssl well before I include it in Debian. Also, having openssl 1.1 support only in testing/unstable won't give apache enough exposure to ensure that nothing is broken in complex configurations. Currently there is no movement upstream to finish the openssl 1.1 support any time soon. This means that it is very unlikely that apache2 will get fixed in time for stretch. Cheers, Stefan
Bug#843823: marked as done (vlc-plugin-base: It depends on liblirc-client0 but it doesn't exists)
Your message dated Wed, 9 Nov 2016 23:17:59 +0100 with message-id <20161109221759.m34spmp6patx4...@ramacher.at> and subject line Re: Bug#843823: vlc-plugin-base: It depends on liblirc-client0 but it doesn't exists has caused the Debian Bug report #843823, regarding vlc-plugin-base: It depends on liblirc-client0 but it doesn't exists 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.) -- 843823: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vlc-plugin-base Version: 1:2.2.4-dmo7 Severity: grave Justification: renders package unusable Dear Maintainer, vlc became uninstallable (or upgradable) because vlc-plugin-base depends on liblirc-client0 but the package in the system is liblircclient0 (without -). -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- On 2016-11-09 17:10:35, Julian Yezid Castellanos Pinzon wrote: > Package: vlc-plugin-base > Version: 1:2.2.4-dmo7 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > vlc became uninstallable (or upgradable) because vlc-plugin-base depends on > liblirc-client0 but the package in the system is liblircclient0 (without -). You are using a vlc-plugin-base from dmo. Report the bug there. Closing -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message ---
Bug#843823: vlc-plugin-base: It depends on liblirc-client0 but it doesn't exists
Package: vlc-plugin-base Version: 1:2.2.4-dmo7 Severity: grave Justification: renders package unusable Dear Maintainer, vlc became uninstallable (or upgradable) because vlc-plugin-base depends on liblirc-client0 but the package in the system is liblircclient0 (without -). -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#843774: marked as done ([pgadmin3] pgadmin segfault at startup with postresql-9.6 installed and a connexion configured in .pgadmin3)
Your message dated Wed, 09 Nov 2016 22:05:14 + with message-id and subject line Bug#843344: fixed in pgadmin3 1.22.1-3 has caused the Debian Bug report #843344, regarding [pgadmin3] pgadmin segfault at startup with postresql-9.6 installed and a connexion configured in .pgadmin3 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.) -- 843344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843344 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pgadmin3 Version: 1.22.1-2 Severity: important Tags: patch --- Please enter the report below this line. ---pgadmin3 segfaults at starup in pgConn::GetStatus (db/pgConn.cpp:1011) when .pgadmin3 exists (minimal one pointing to localhost attached) and have a server connexion configured.According to those threads [1][2], it seems that compiling with -fno-delete-null-pointer-checks on GCC6 corrects the problem.Here is the backtrace:gdb --quiet pgadmin3 Reading symbols from pgadmin3...Reading symbols from /usr/lib/debug/.build- id/5f/5de51f2d0bf14d6b6f50a56a755a95b68b3512.debug...done.done.(gdb) runStarting program: /usr/bin/pgadmin3 [Thread debugging using libthread_db enabled]Using host libthread_db library "/lib/x86_64- linux-gnu/libthread_db.so.1".13:46:32: Warning: Mismatch between the program and library build versions detected.The library used 3.0 (wchar_t,compiler with C++ ABI 1009,wx containers,compatible with 2.8),and your program used 3.0 (wchar_t,compiler with C++ ABI 1010,wx containers,compatible with 2.8).13:46:33: Debug: Adding duplicate image handler for 'PNG file' Program received signal SIGSEGV, Segmentation fault.pgConn::GetStatus (this=0x0) at db/pgConn.cpp:10111011db/pgConn.cpp: Aucun fichier ou dossier de ce type.(gdb) bt#0 pgConn::GetStatus (this=0x0) at db/pgConn.cpp:1011#1 0x55ac26e1 in pluginUtilityFactory::CheckEnable (this=0x57137970, obj=0x572748d0) at frm/plugins.cpp:383#2 0x55db770a in menuFactoryList::CheckMenu (this=0x571165f0, obj=obj@entry=0x57 2748d0, menubar=0x571b7c20, toolbar=0x57116610) at utils/factory.cpp:266#3 0x559d55ba in frmMain::setDisplay (thi s=this@entry=0x570c20b0, data=0x572748d0, props=props@entry=0x0 , sqlbox=sqlbox@entry=0x0) at frm/events.cpp:600#4 0x559d9202 in frmMain::execSelChange (this=this@entry=0x570c20b0, item=..., currentNode=) at frm/events.cpp:512#5 0x559d9945 in frmMain::OnExpand (this=0x570c20b0, event=...) at frm/events.cpp:277#6 0x75b8e59e in wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, wxEvent&) const () from /usr/lib/x86_64-linux-gnu/libwx_baseu- 3.0.so.0#7 0x75d14a87 in wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) () from /usr/lib/x86_64-linux-gnu/libwx_baseu- 3.0.so.0#8 0x75d14b7b in wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0#9 0x75d14f2b in wxEvtHandler::TryHereOnly(wxEvent&) () from /usr/lib/x86_64-linux- gnu/libwx_baseu-3.0.so.0#10 0x75d14d33 in wxEvtHandler::DoTryChain(wxEvent&) () from /usr/lib/x86_64-linux- gnu/libwx_baseu-3.0.so.0#11 0x75d15015 in wxEvtHandler::ProcessEvent(wxEvent&) () from /usr/lib/x86_64-linux- gnu/libwx_baseu-3.0.so.0#12 0x768b46c8 in wxWindowBase::TryAfter(wxEvent&) () from /usr/lib/x86_64-linux- gnu/libwx_gtk2u_core-3.0.so.0#13 0x7692205b in wxScrollHelperEvtHandler::ProcessEvent(wxEvent&) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0#14 0x76939703 in wxGenericTreeCtrl::Expand(wxTreeItemId const&) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0#15 0x55a41d92 in frmMain::frmMain (this=0x570c20b0, title=...) at frm/frmMain.cpp:239#16 0x5575f02c in pgAdmin3::OnInit (this=0x56565310) at pgAdmin3.cpp:786#17 0x75c22332 in wxEntry(int&, wchar_t**) () from /usr/lib/x86_64-linux-gnu/libwx_baseu- 3.0.so.0#18 0x556f9ae2 in main (argc=, argv=) at pgAdmin3.cpp:126(gdb) quitA debugging session is active. Inferior 1 [process 19364] will be killed. Quit anyway? (y or n) y I tried to modify debian/rules with:override_dh_auto_build: $(MA KE) CFLAGS+="-g -fno-delete-null-pointer-checks" CXXFLAGS+="-g -fno- delete-null-pointer-checks" But was not able to compile from source package cause of the following error:/postgresql -I/usr/include/postgresql/9.6/server -I/usr/include/postgresql -DHAVE_CONNINFO_PARSE -I/usr/lib/x86_64- linux-gnu/wx/include/gtk2-unicode-3.0 -I/usr/include/wx-3.0
Bug#843078: marked as done (pokerth: -std=gnu++98 workaround no longer works with Qt 5.7)
Your message dated Wed, 09 Nov 2016 22:05:26 + with message-id and subject line Bug#843078: fixed in pokerth 1.1.1-7 has caused the Debian Bug report #843078, regarding pokerth: -std=gnu++98 workaround no longer works with Qt 5.7 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.) -- 843078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843078 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pokerth Version: 1.1.1-6 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, pokerth fails to build from source in unstable/amd64: […] /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:72:88: error: '>>' should be '> >' within a nested template argument list template struct List_Append, List> { typedef List Value; }; ^~ In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs.h:50:0, from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:46, from /usr/include/x86_64-linux-gnu/qt5/QtCore/qcoreapplication.h:46, from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qapplication.h:43, from src/pokerth.cpp:35: /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:98:22: error: expected ',' or '...' before '&&' token void operator,(T &&value, const ApplyReturnValue &container) { ^~ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:98:67: error: 'void QtPrivate::operator,(T)' must take exactly two arguments void operator,(T &&value, const ApplyReturnValue &container) { ^ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:215:62: error: '>>' should be '> >' within a nested template argument list template <> struct CheckCompatibleArguments, List<>> { enum { value = true }; }; ^~ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:216:75: error: '>>' should be '> >' within a nested template argument list template struct CheckCompatibleArguments> { enum { value = true }; }; ^~ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:218:78: error: '>>' should be '> >' within a nested template argument list struct CheckCompatibleArguments, List> ^~ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:221:78: error: '>>' should be '> >' within a nested template argument list && CheckCompatibleArguments, List>::value }; ^~ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:238:113: error: '>>' should be '> >' within a nested template argument list template struct ComputeFunctorArgumentCount> ^~ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:241:56: error: expected type-specifier before 'decltype' template static auto test(F f) -> decltype(((f.operator()((dummy())...)), int())); ^~~~ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:241:56: error: expected initializer before 'decltype' /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:251:104: error: '>>' should be '> >' within a nested template argument list template struct FunctorReturnType> { ^~ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:253:26: error: expected identifier typedef decltype(dummy().operator()((dummy())...)) Value; ^~ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:253:40: error: expected unqualified-id before '(' token typedef decltype(dummy().operator()((dummy())...)) Value; ^ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:253:40: error: expected ')' befo
Bug#843344: marked as done (pgadmin3 segfaults on start)
Your message dated Wed, 09 Nov 2016 22:05:14 + with message-id and subject line Bug#843344: fixed in pgadmin3 1.22.1-3 has caused the Debian Bug report #843344, regarding pgadmin3 segfaults on start 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.) -- 843344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843344 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pgadmin3 Version: 1.22.1-2 Severity: grave Justification: renders package unusable pgadmin crashes in plugin.cc:383 when obj->GetConnection() returns 0 instead of: if (!obj || !(obj->GetConnection()->GetStatus() == PGCONN_OK)) it should read: if (!obj || !obj->GetConnection() || !(obj->GetConnection()->GetStatus() == PGCONN_OK)) maybe this is related to my recent upgrade from pg9.5 to pg9.6 (including all libraries) another reason could be that I enabled PG debugging of stored procedures forpg9.5 but not yet for pg9.6 Since it will probably not be fixed on upstream please could you kindly fix it for the debian package -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-rc7-amd64 (SMP w/8 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pgadmin3 depends on: ii libc6 2.24-3 ii libgcc1 1:6.2.0-1 ii libpq59.6.1-2 ii libssl1.0.2 1.0.2j-1 ii libstdc++66.2.0-1 ii libwxbase3.0-0v5 3.0.2+dfsg-2 ii libwxgtk3.0-0v5 3.0.2+dfsg-2 ii libxml2 2.9.4+dfsg1-1 ii libxslt1.11.1.29-2 ii pgadmin3-data 1.22.1-2 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages pgadmin3 recommends: ii pgagent3.4.1-3 ii postgresql-client-9.6 [postgresql-client] 9.6.1-2 Versions of packages pgadmin3 suggests: ii postgresql-contrib 9.6+177 -- no debconf information --- End Message --- --- Begin Message --- Source: pgadmin3 Source-Version: 1.22.1-3 We believe that the bug you reported is fixed in the latest version of pgadmin3, 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 843...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Berg (supplier of updated pgadmin3 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: Wed, 09 Nov 2016 22:47:57 +0100 Source: pgadmin3 Binary: pgadmin3 pgadmin3-dbg pgadmin3-data Architecture: source Version: 1.22.1-3 Distribution: unstable Urgency: high Maintainer: Debian PostgreSQL Maintainers Changed-By: Christoph Berg Description: pgadmin3 - graphical administration tool for PostgreSQL pgadmin3-data - graphical administration tool for PostgreSQL - documentation pgadmin3-dbg - graphical administration tool for PostgreSQL (debugging symbols) Closes: 843344 Changes: pgadmin3 (1.22.1-3) unstable; urgency=high . * Fix segfault on startup, thanks to Bernhard Rieder for the patch! (Closes: #843344) Checksums-Sha1: ba0e04aa002770d6fe67735aa791c9e701817f33 2291 pgadmin3_1.22.1-3.dsc b1a23a6425809160903991a1173bee136401f49a 19168 pgadmin3_1.22.1-3.debian.tar.xz Checksums-Sha256: c68bcded349e54f1340276f1162d1f1cdf76da537574c9d3f01a1bd44141b6eb 2291 pgadmin3_1.22.1-3.dsc 5faff256d0095cdd4a51fe0c23b15ebaf1916aa04c908aadc68b9ba8cadddbe4 19168 pgadmin3_1.22.1-3.debian.tar.xz Files: 90d944b8bf20fa4cf480a775db229eb7 2291 database optional pgadmin3_1.22.1-3.dsc eba9df3bf880d0e95719354ebbba2e68 19168 database optional pgadmin3_1.22.1-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJYI5pjAAoJEExaa6sS0qeu030P/jG51giLKJjHiIUA2R8A3SSO LX2pt7qwo7wX9YQKOpaeYprj4fdlH7IFnL1kZ4IurdJSrQJ39X3PJolVIZ7hv8Xl K2obq6ABqtJ3P222hKNGKwVRoipaqYWhsEtVdIjgwmUCGNW1qzMmNH5BaoU+EuCB C8IOJ2aHzvj+A1GuQE9AOY/ypB4LR1HA66N1wQtZRYVQ8buG+00cUkRbbQNxOv43 5l8CkjQ1dST7Jy8gR6y5aTjTXRXJQ3w6oVNC0iXXuO8f40CSoESa7bYZrMIH/98f XJZ+hxNJkaETtO4tLKCjF7YrEMsi8XL7zvB+uef+9XckGeFgbCKiRmBW0F/YzDZL S2OfxWIlD+euu
Processed: Re: Bug#843727: fix inside
Processing control commands: > tags -1 pending Bug #843727 [desktop-base] desktop-base: experimental version does not install Added tag(s) pending. -- 843727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843727: fix inside
control: tags -1 pending Le mercredi 9 novembre 2016, 22:45:32 CET Eric Valette a écrit : > the wrong code is calling "which update-initramfs" outside of if > because then the set -e catch an error and there is no way the > test on $? can work > > correct code is: > > if which update-initramfs > /dev/null; then > update-initramfs -u > fi Yes, was preparing that already after reading your last mail. :-) It’s now committed to SVN and will be in the next upload. Cheers, --Aurélien
Bug#828608: xmltooling: FTBFS with openssl 1.1.0
On Wed, Nov 09, 2016 at 09:26:00PM +, Cantor, Scott wrote: > On 11/9/16, 3:55 PM, "Pkg-shibboleth-devel on behalf of Kurt Roeckx" > behalf of k...@roeckx.be> wrote: > > > Can I just say this is really ugly code? It's called "internal", > > you really have no business of touching this. And that just for > > some debug log. > > The debugging information is a minor portion of the functionality. I have > every business touching it, this is how Shibboleth enforces requirements on a > TLS certificate. The SSL_CTX callback is the only way to do this evaluation > with the necessary inputs before it's already sent data off to an attacker. > All (or certainly the vast majority) of those APIs are public. The non-public > APIs used out of necessity are libcrypto bits related to public key > manipulation and are elsewhere. Please note that I'm only talking about this piece of code: CURLcode infocode = curl_easy_getinfo(ctx->m_handle, CURLINFO_TLS_SSL_PTR, &tlsinfo); if (infocode == CURLE_OK && tlsinfo && tlsinfo->backend == CURLSSLBACKEND_OPENSSL && tlsinfo->internals) { SSL* ssl = reinterpret_cast(tlsinfo->internals); const SSL_CIPHER* cipher = SSL_get_current_cipher(ssl); log.debug("SSL version: %s, cipher: %s", SSL_get_version(ssl), cipher ? SSL_CIPHER_get_name(cipher) : "unknown"); This is curl_header_hook(). It's not related to any of the that has to do with SSL, and just uses it to print some debug info. > > Since libcurl seems to be exposing this functionality, I think you > > need to use the same version of openssl than libcurl is using. > > libcurl really shouldn't have been exposing this. > > There is no other interface in any client library that provides even a > pretense of serious control over TLS trust handling. It's been part of > libcurl for 15 years, or longer. > > I know they prefer people not to use it, but they haven't provided any > alternative, so it is what it is. Yes, so we need something in Debian where both xmltooling and libcurl are using the same openssl version. Have you looked at what needs to be done for supporting openssl 1.1.0? Would it be useful to that I send a patch for it? Kurt
Processed: forcibly merging 843774 843344
Processing commands for cont...@bugs.debian.org: > forcemerge 843774 843344 Bug #843774 [pgadmin3] [pgadmin3] pgadmin segfault at startup with postresql-9.6 installed and a connexion configured in .pgadmin3 Bug #843774 [pgadmin3] [pgadmin3] pgadmin segfault at startup with postresql-9.6 installed and a connexion configured in .pgadmin3 Marked as found in versions pgadmin3/1.22.1-1. Bug #843344 [pgadmin3] pgadmin3 segfaults on start Severity set to 'grave' from 'important' Marked as found in versions pgadmin3/1.22.1-2. Added tag(s) patch. Merged 843344 843774 > thanks Stopping processing here. Please contact me if you need assistance. -- 843344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843344 843774: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843727: fix inside
the wrong code is calling "which update-initramfs" outside of if because then the set -e catch an error and there is no way the test on $? can work correct code is: if which update-initramfs > /dev/null; then update-initramfs -u fi -- eric
Bug#828608: xmltooling: FTBFS with openssl 1.1.0
On 11/9/16, 3:55 PM, "Pkg-shibboleth-devel on behalf of Kurt Roeckx" wrote: > Can I just say this is really ugly code? It's called "internal", > you really have no business of touching this. And that just for > some debug log. The debugging information is a minor portion of the functionality. I have every business touching it, this is how Shibboleth enforces requirements on a TLS certificate. The SSL_CTX callback is the only way to do this evaluation with the necessary inputs before it's already sent data off to an attacker. All (or certainly the vast majority) of those APIs are public. The non-public APIs used out of necessity are libcrypto bits related to public key manipulation and are elsewhere. > Since libcurl seems to be exposing this functionality, I think you > need to use the same version of openssl than libcurl is using. > libcurl really shouldn't have been exposing this. There is no other interface in any client library that provides even a pretense of serious control over TLS trust handling. It's been part of libcurl for 15 years, or longer. I know they prefer people not to use it, but they haven't provided any alternative, so it is what it is. >Curl should be doing this by default, and actually has a setting for this ... Implementing SAML properly has requirements that are not met by anything libcurl is capable of doing on its own. > Is there a reason it implements it's own certificate verification > rather than using curl's? I guess curl didn't do this always. This probably is not the place to provide a primer on trust management in federation systems. > It at least looks to me you could just remove all code that is > related to libssl and let curl do it for you. That would be incorrect, but Ferenc understands that. -- Scott
Bug#843727: requested infos
apt-get -f install Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Le paquet suivant a été installé automatiquement et n'est plus nécessaire : libkodiplatform16 Veuillez utiliser « apt autoremove » pour le supprimer. 0 mis à jour, 0 nouvellement installés, 0 à enlever et 2 non mis à jour. 1 partiellement installés ou enlevés. Après cette opération, 0 o d'espace disque supplémentaires seront utilisés. Paramétrage de desktop-base (9.0.0~exp1) ... + dpkg-maintscript-helper rm_conffile /etc/default/kdm.d/10_desktop-base 9.0.0~ desktop-base -- configure 8.0.2 + [[ configure = \c\o\n\f\i\g\u\r\e ]] + read theme priority + update-alternatives --install /usr/share/desktop-base/active-theme desktop-theme /usr/share/desktop-base/softwaves-theme 50 + read theme priority + update-alternatives --install /usr/share/desktop-base/active-theme desktop-theme /usr/share/desktop-base/lines-theme 40 + read theme priority + update-alternatives --install /usr/share/images/desktop-base/desktop-background desktop-background /usr/share/desktop-base/active-theme/wallpaper/contents/images/1920x1080.svg 70 + read theme filename priority + update-alternatives --install /usr/share/images/desktop-base/desktop-background desktop-background /usr/share/desktop-base/softwaves-theme/wallpaper/contents/images/1280x720.svg 65 + read theme filename priority + update-alternatives --install /usr/share/images/desktop-base/desktop-background desktop-background /usr/share/desktop-base/softwaves-theme/wallpaper/contents/images/1280x800.svg 65 + read theme filename priority + update-alternatives --install /usr/share/images/desktop-base/desktop-background desktop-background /usr/share/desktop-base/softwaves-theme/wallpaper/contents/images/1920x1080.svg 65 + read theme filename priority + update-alternatives --install /usr/share/images/desktop-base/desktop-background desktop-background /usr/share/desktop-base/softwaves-theme/wallpaper/contents/images/1920x1200.svg 65 + read theme filename priority + update-alternatives --install /usr/share/images/desktop-base/desktop-background desktop-background /usr/share/desktop-base/softwaves-theme/wallpaper/contents/images/2560x1440.svg 65 + read theme filename priority + update-alternatives --install /usr/share/images/desktop-base/desktop-background desktop-background /usr/share/desktop-base/softwaves-theme/wallpaper/contents/images/2560x1600.svg 65 + read theme filename priority + update-alternatives --install /usr/share/images/desktop-base/desktop-background desktop-background /usr/share/desktop-base/lines-theme/wallpaper/contents/images/1280x1024.svg 60 + read theme filename priority + update-alternatives --install /usr/share/images/desktop-base/desktop-background desktop-background /usr/share/desktop-base/lines-theme/wallpaper/contents/images/1600x1200.svg 60 + read theme filename priority + update-alternatives --install /usr/share/images/desktop-base/desktop-background desktop-background /usr/share/desktop-base/lines-theme/wallpaper/contents/images/1920x1080.svg 60 + read theme filename priority + update-alternatives --install /usr/share/images/desktop-base/desktop-background desktop-background /usr/share/desktop-base/lines-theme/wallpaper/contents/images/1920x1200.svg 60 + read theme filename priority + update-alternatives --install /usr/share/images/desktop-base/desktop-background desktop-background /usr/share/desktop-base/lines-theme/wallpaper/contents/images/2560x1080.svg 60 + read theme filename priority + read background priority + update-alternatives --install /usr/share/images/desktop-base/desktop-background desktop-background /usr/share/images/desktop-base/joy-wallpaper_1600x1200.svg 50 + read background priority + update-alternatives --install /usr/share/images/desktop-base/desktop-background desktop-background /usr/share/images/desktop-base/joy-wallpaper_1280x1024.svg 50 + read background priority + update-alternatives --install /usr/share/images/desktop-base/desktop-background desktop-background /usr/share/images/desktop-base/joy-wallpaper_1920x1080.svg 50 + read background priority + update-alternatives --install /usr/share/images/desktop-base/desktop-background desktop-background /usr/share/images/desktop-base/joy-wallpaper_1920x1200.svg 50 + read background priority + update-alternatives --install /usr/share/images/desktop-base/desktop-background desktop-background /usr/share/images/desktop-base/joy-inksplat-wallpaper_1920x1080.svg 50 + read background priority + update-alternatives --install /usr/share/images/desktop-base/desktop-background desktop-background /usr/share/images/desktop-base/spacefun-wallpaper.svg 50 + read background priority + update-alternatives --install /usr/share/images/desktop-base/desktop-background desktop-background /usr/share/images/desktop-base/spacefun-wallpaper-widescreen.svg 50 + read background priority + update-alter
Bug#828542: marked as done (shellinabox: FTBFS with openssl 1.1.0)
Your message dated Wed, 09 Nov 2016 21:23:29 + with message-id and subject line Bug#828542: fixed in shellinabox 2.20 has caused the Debian Bug report #828542, regarding shellinabox: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 828542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: shellinabox Version: 2.19 Severity: important Control: block 827061 by -1 Hi, OpenSSL 1.1.0 is about to released. During a rebuild of all packages using OpenSSL this package fail to build. A log of that build can be found at: https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/shellinabox_2.19_amd64-20160529-1535 On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the reasons why it might fail. There are also updated man pages at https://www.openssl.org/docs/manmaster/ that should contain useful information. There is a libssl-dev package available in experimental that contains a recent snapshot, I suggest you try building against that to see if everything works. If you have problems making things work, feel free to contact us. Kurt --- End Message --- --- Begin Message --- Source: shellinabox Source-Version: 2.20 We believe that the bug you reported is fixed in the latest version of shellinabox, 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 828...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marc Singer (supplier of updated shellinabox 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: Wed, 09 Nov 2016 09:52:24 -0800 Source: shellinabox Binary: shellinabox Architecture: source amd64 Version: 2.20 Distribution: unstable Urgency: medium Maintainer: Marc Singer Changed-By: Marc Singer Description: shellinabox - publish command line shell through AJAX interface Closes: 828542 839066 839067 Changes: shellinabox (2.20) unstable; urgency=medium . * Fixed issue #222, LOGIN service * Fixed issue #360, ignore escape sequences to fix dir listing * Fix for function key presses * Adjusting scale on IE * New option to disable peer check (#364) * Add option for custom SSH port * Support for APL characters * PDF documentation * Fix for BSD build * New ready event support * OpenSSL 1.1 fixes (Closes: #828542) * May build with MUSL library * Documentation added that SSL support is optional and requires installation of openssl on Debian. (Closes: #839067) * Jessie requires explicit installation of openssl because the default package does not include the necessary utilities to support creation of certificates. (Closes: #839066) Checksums-Sha1: 86cd163df62988dea0ec64ccf019002fc22b275f 1616 shellinabox_2.20.dsc 41d28d816cf63fdf3e0de45bdd1878a2d88aac7b 666368 shellinabox_2.20.tar.xz f89a138d3e3aa5a1837ed519af663cd4638d8882 277692 shellinabox-dbgsym_2.20_amd64.deb 461aa427866eaac9a52554a55470fc707404ffd4 124930 shellinabox_2.20_amd64.deb Checksums-Sha256: 01bf4a5b0ea3b2dfb725c7c60e545056ee4d567df69c89cec78ad954aab9e830 1616 shellinabox_2.20.dsc 3a234302fe8d8fdabe20ed31d3b198599e369c6b79cdc4dd11fa43a7fd4803fa 666368 shellinabox_2.20.tar.xz a9afa598ed8553d067ffd7f9cbecb1d02a7d85a0308b752c47c3ce4404c410a1 277692 shellinabox-dbgsym_2.20_amd64.deb e8a74c40ea3cc6370b6d26586a20997aa7b60538e7e603387a25ef7d9f180bcb 124930 shellinabox_2.20_amd64.deb Files: 9bd1a91d8a7fa2447c45823a8d8d882c 1616 web optional shellinabox_2.20.dsc 27307bc2ebf718ae9e241a092b4c15f0 666368 web optional shellinabox_2.20.tar.xz e92a1683f7a15ed16f8b7e24ae480b24 277692 debug extra shellinabox-dbgsym_2.20_amd64.deb cfe8f7006cbdd242c9dacf8965a5923b 124930 web optional shellinabox_2.20_amd64.deb -BEGIN PGP SIGNATURE- iQIsBAEBCAAWBQJYI3zZDxxlbGZAZGViaWFuLm9yZwAKCRAazBH+fTkhPJTZD/4i BJYlrjqXtuuafg1iFxagzQ0Ii4vs5d2AG3lOxG9dHlaRBfXZ6/L8crKm47Q4MmWj 2J6kxt4m3JboF5FJ/AVTT+ongru7JK8bXBnNcV6dbfS1IaUA113x8/XlhkxcFW1L E75UDm1A9ylNOfZoddQaV4JcxKtEqV+wO7XxKEuJ4bQtVgnC7u5aK+RRoeIBFDwW BjHoh0VcPSrb+HGdiNmhTzChptzBosS8fQYROu4qQLWhy99JOb2C+jjkZlqN8cZR cVkpaLRq
Bug#839454: marked as done (syslog-ng-incubator: FTBFS: dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2)
Your message dated Wed, 09 Nov 2016 21:24:13 + with message-id and subject line Bug#839454: fixed in syslog-ng-incubator 0.5.0-3 has caused the Debian Bug report #839454, regarding syslog-ng-incubator: FTBFS: dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 839454: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839454 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: syslog-ng-incubator Version: 0.5.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161001 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/debian/build-tree' > /usr/share/syslog-ng/tools/lex-rules.am:14: warning: overriding recipe for > target '.y.c' > make[4]: warning: ignoring old recipe for target '.y.c' > PASS: modules/grok/tests/test_grok > FAIL: modules/date/tests/test_date > = >syslog-ng-incubator 0.5.0: ./test-suite.log > = > > # TOTAL: 2 > # PASS: 1 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: modules/date/tests/test_date > == > > [2016-10-01T12:45:59.824883] Failed to open the time zone file; filename='', > message='Failed to open file \'\': open() failed: No such file or directory' > [2016-10-01T12:45:59.824906] Bogus timezone spec, must be in the format > [+-]HH:MM, offset must be less than 24:00; value='America/Phoenix' > > ### > # > # FAIL: ASSERTION FAILED: incorrect date parsed msg=Tue, 27 Jan 2015 > 11:48:46 offset=0 format=%a, %d %b %Y %T; actual='2015-01-27T11:48:46+00:00', > expected='2015-01-27T11:48:46-07:00' actual_length=25 expected_length=25 > # > ### > > FAIL modules/date/tests/test_date (exit status: 1) > > > Testsuite summary for syslog-ng-incubator 0.5.0 > > # TOTAL: 2 > # PASS: 1 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > See ./test-suite.log > Please report to viktor.juh...@balabit.com > > Makefile:2162: recipe for target 'test-suite.log' failed > make[4]: *** [test-suite.log] Error 1 > make[4]: Leaving directory '/<>/debian/build-tree' > Makefile:2268: recipe for target 'check-TESTS' failed > make[3]: *** [check-TESTS] Error 2 > make[3]: Leaving directory '/<>/debian/build-tree' > Makefile:2480: recipe for target 'check-am' failed > make[2]: *** [check-am] Error 2 > make[2]: Leaving directory '/<>/debian/build-tree' > Makefile:2483: recipe for target 'check' failed > make[1]: *** [check] Error 2 > make[1]: Leaving directory '/<>/debian/build-tree' > dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2 If the failure looks somehow time/timezone related: Note that this rebuild was performed without the 'tzdata' package installed in the chroot. tzdata used be (transitively) part of build-essential, but it no longer is. If this package requires it to build, it should be added to build-depends. For the release team's opinion on this, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185 If the failure looks LSB-related: similarly to tzdata, lsb-base is not installed in the build chroot. The full build log is available from: http://aws-logs.debian.net/2016/10/01/syslog-ng-incubator_0.5.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: syslog-ng-incubator Source-Version: 0.5.0-3 We believe that the bug you reported is fixed in the latest version of syslog-ng-incubator, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the
Bug#762799: marked as done (zpb-ttf: Maintainer address bounces)
Your message dated Wed, 09 Nov 2016 22:21:54 +0100 with message-id <1478726514.8285.0.ca...@debian.org> and subject line Re: bordeaux-threads: maintainer address bounces has caused the Debian Bug report #762799, regarding zpb-ttf: Maintainer address bounces 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.) -- 762799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bordeaux-threads Version: 0.8.3-1 Severity: serious X-Debbugs-Cc: d...@tapoueh.org [ CCed last uploader. ] The maintainer address bounces, see below. Ansgar Mail Delivery System writes: > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > > nowhere@levallois.eu.org > retry timeout exceeded > > -- This is a copy of the message, including all the headers. -- > [...] > From: Debian FTP Masters > To: Pierre THIERRY , Dimitri Fontaine > , [...] > Subject: bordeaux-threads_0.8.3-1_amd64.changes ACCEPTED into unstable > Message-Id: > Date: Thu, 18 Sep 2014 17:33:33 + --- End Message --- --- Begin Message --- The package has now been orphaned on behalf of the MIA Team. -- tobi (for the MIA Team)--- End Message ---
Processed: fixed 843644 in 16.2.0-1
Processing commands for cont...@bugs.debian.org: > fixed 843644 16.2.0-1 Bug #843644 {Done: Sandro Tosi } [python-openssl] AttributeError: 'module' object has no attribute Bug #843818 {Done: Sandro Tosi } [python-openssl] fails to start with AttributeError: 'module' object has no attribute 'SSL_ST_INIT' Marked as fixed in versions pyopenssl/16.2.0-1. Marked as fixed in versions pyopenssl/16.2.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 843644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843644 843818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 843644 to python-openssl, forcibly merging 843644 843818, affects 843644
Processing commands for cont...@bugs.debian.org: > reassign 843644 python-openssl 16.1.0-1 Bug #843644 {Done: Sandro Tosi } [pyopenssl] AttributeError: 'module' object has no attribute Bug reassigned from package 'pyopenssl' to 'python-openssl'. Ignoring request to alter found versions of bug #843644 to the same values previously set No longer marked as fixed in versions pyopenssl/16.2.0-1. Bug #843644 {Done: Sandro Tosi } [python-openssl] AttributeError: 'module' object has no attribute Marked as found in versions pyopenssl/16.1.0-1. > forcemerge 843644 843818 Bug #843644 {Done: Sandro Tosi } [python-openssl] AttributeError: 'module' object has no attribute Bug #843818 [python-openssl] fails to start with AttributeError: 'module' object has no attribute 'SSL_ST_INIT' Severity set to 'critical' from 'grave' Marked Bug as done Added indication that 843818 affects bugwarrior,bugs-everywhere,ansible Marked as found in versions pyopenssl/16.1.0-1. Merged 843644 843818 > affects 843644 + virt-manager Bug #843644 {Done: Sandro Tosi } [python-openssl] AttributeError: 'module' object has no attribute Bug #843818 {Done: Sandro Tosi } [python-openssl] fails to start with AttributeError: 'module' object has no attribute 'SSL_ST_INIT' Added indication that 843644 affects virt-manager Added indication that 843818 affects virt-manager > thanks Stopping processing here. Please contact me if you need assistance. -- 843644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843644 843818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): reassign 843818 to python-openssl, forcibly merging 843644 843818, affects 843644
Processing commands for cont...@bugs.debian.org: > reassign 843818 python-openssl Bug #843818 [virt-manager] fails to start with AttributeError: 'module' object has no attribute 'SSL_ST_INIT' Bug reassigned from package 'virt-manager' to 'python-openssl'. No longer marked as found in versions virt-manager/1:1.4.0-3. Ignoring request to alter fixed versions of bug #843818 to the same values previously set > forcemerge 843644 843818 Bug #843644 {Done: Sandro Tosi } [pyopenssl] AttributeError: 'module' object has no attribute Unable to merge bugs because: package of #843818 is 'python-openssl' not 'pyopenssl' Failed to forcibly merge 843644: Did not alter merged bugs. > affects 843644 + virt-manager Failed to mark 843644 as affecting package(s): failed to get lock on /org/bugs.debian.org/spool/lock/843644 -- Unable to lock /org/bugs.debian.org/spool/lock/843644 Resource temporarily unavailable. Unable to lock /org/bugs.debian.org/spool/lock/843644 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629. Unable to lock /org/bugs.debian.org/spool/lock/843644 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629. Unable to lock /org/bugs.debian.org/spool/lock/843644 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629. Unable to lock /org/bugs.debian.org/spool/lock/843644 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629. Unable to lock /org/bugs.debian.org/spool/lock/843644 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629. Unable to lock /org/bugs.debian.org/spool/lock/843644 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629. Unable to lock /org/bugs.debian.org/spool/lock/843644 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629. Unable to lock /org/bugs.debian.org/spool/lock/843644 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629. Unable to lock /org/bugs.debian.org/spool/lock/843644 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629. at /usr/local/lib/site_perl/Debbugs/Common.pm line 587. > thanks Stopping processing here. Please contact me if you need assistance. -- 843644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843644 843818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843818: fails to start with AttributeError: 'module' object has no attribute 'SSL_ST_INIT'
Package: virt-manager Version: 1:1.4.0-3 Severity: grave Trying to run virt-manager, I get $ virt-manager Traceback (most recent call last): File "/usr/share/virt-manager/virt-manager", line 33, in from virtinst import util as util File "/usr/share/virt-manager/virtinst/__init__.py", line 89, in from virtinst.distroinstaller import DistroInstaller File "/usr/share/virt-manager/virtinst/distroinstaller.py", line 23, in from . import urlfetcher File "/usr/share/virt-manager/virtinst/urlfetcher.py", line 34, in import requests File "/usr/lib/python2.7/dist-packages/requests/__init__.py", line 52, in from .packages.urllib3.contrib import pyopenssl File "/usr/lib/python2.7/dist-packages/requests/packages/__init__.py", line 58, in vendored('urllib3.contrib.pyopenssl') File "/usr/lib/python2.7/dist-packages/requests/packages/__init__.py", line 32, in vendored __import__(vendored_name, globals(), locals(), level=0) File "/usr/lib/python2.7/dist-packages/urllib3/contrib/pyopenssl.py", line 54, in import OpenSSL.SSL File "/usr/lib/python2.7/dist-packages/OpenSSL/__init__.py", line 8, in from OpenSSL import rand, crypto, SSL File "/usr/lib/python2.7/dist-packages/OpenSSL/SSL.py", line 112, in SSL_ST_INIT = _lib.SSL_ST_INIT AttributeError: 'module' object has no attribute 'SSL_ST_INIT' -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages virt-manager depends on: ii dconf-gsettings-backend [gsettings-backend] 0.26.0-2 ii gconf2 3.2.6-4 ii gir1.2-gtk-3.0 3.22.3-1 ii gir1.2-gtk-vnc-2.0 0.6.0-1 ii gir1.2-libosinfo-1.0 1.0.0-2 ii gir1.2-libvirt-glib-1.0 0.2.3-2 ii gir1.2-vte-2.91 0.46.1-1 ii librsvg2-common 2.40.16-1 ii python-dbus 1.2.4-1 ii python-gi3.22.0-1 ii python-gi-cairo 3.22.0-1 ii python-libvirt 2.4.0-1 ii python-requests 2.11.1-1 pn python2.7:any pn python:any ii virtinst 1:1.4.0-3 Versions of packages virt-manager recommends: ii gir1.2-spice-client-gtk-3.0 0.33-3 pn gnome-icon-theme ii libvirt-daemon-system2.4.0-1+b1 Versions of packages virt-manager suggests: ii gnome-keyring 3.20.0-3 ii ksshaskpass [ssh-askpass] 4:5.8.2-1 pn python-gnomekeyring pn python-guestfs ii ssh-askpass1:1.2.4.1-9 ii virt-viewer4.0-1 -- no debconf information
Bug#843783: marked as done (deluge-gtk: fails to start: AttributeError: 'module' object has no attribute 'SSL_ST_INIT')
Your message dated Wed, 09 Nov 2016 22:00:05 +0100 with message-id <147872520544.19555.8999601644944339...@auryn.jones.dk> and subject line Re: Bug#843783: deluge-gtk: fails to start: AttributeError: 'module' object has no attribute 'SSL_ST_INIT' has caused the Debian Bug report #843783, regarding deluge-gtk: fails to start: AttributeError: 'module' object has no attribute 'SSL_ST_INIT' 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.) -- 843783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843783 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: deluge-gtk Version: 1.3.13-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 My deluge-gtk recently stopped being able to start at all, leaving the following in .xsession-errors: Traceback (most recent call last): File "/usr/bin/deluge-gtk", line 11, in load_entry_point('deluge==1.3.13', 'gui_scripts', 'deluge-gtk')() File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 564, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2608, in load_entry_point return ep.load() File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2268, in load return self.resolve() File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2274, in resolve module = __import__(self.module_name, fromlist=['__name__'], level=0) File "/usr/lib/python2.7/dist-packages/deluge/ui/gtkui/__init__.py", line 1, in from gtkui import start File "/usr/lib/python2.7/dist-packages/deluge/ui/gtkui/gtkui.py", line 41, in from twisted.internet import gtk2reactor File "/usr/lib/python2.7/dist-packages/twisted/internet/gtk2reactor.py", line 23, in from twisted.internet import _glibbase File "/usr/lib/python2.7/dist-packages/twisted/internet/_glibbase.py", line 20, in from twisted.internet import base, posixbase, selectreactor File "/usr/lib/python2.7/dist-packages/twisted/internet/posixbase.py", line 18, in from twisted.internet import error, udp, tcp File "/usr/lib/python2.7/dist-packages/twisted/internet/tcp.py", line 28, in from twisted.internet._newtls import ( File "/usr/lib/python2.7/dist-packages/twisted/internet/_newtls.py", line 21, in from twisted.protocols.tls import TLSMemoryBIOFactory, TLSMemoryBIOProtocol File "/usr/lib/python2.7/dist-packages/twisted/protocols/tls.py", line 41, in from OpenSSL.SSL import Error, ZeroReturnError, WantReadError File "/usr/lib/python2.7/dist-packages/OpenSSL/__init__.py", line 8, in from OpenSSL import rand, crypto, SSL File "/usr/lib/python2.7/dist-packages/OpenSSL/SSL.py", line 112, in SSL_ST_INIT = _lib.SSL_ST_INIT AttributeError: 'module' object has no attribute 'SSL_ST_INIT' - Jonas - -- System Information: Debian Release: stretch/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages deluge-gtk depends on: ii deluge-common1.3.13-1 ii dunst [notification-daemon] 1.1.0-2 ii librsvg2-common 2.40.16-1 ii python 2.7.11-2 ii python-glade22.24.0-5.1 ii python-jarabe [notification-daemon] 0.106.1-1 ii python-notify0.1.1-4 pn python:any ii xdg-utils1.1.1-1 Versions of packages deluge-gtk recommends: ii python-pygame 1.9.1release+dfsg-10+b2 deluge-gtk suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQIcBAEBAgAGBQJYIz+iAAoJECx8MUbBoAEheFYQAKAZneEcU3Dk2NU3Z1RmcVi+ yEKwGwDmPCeE+401PDvsoZl32+rlUbMrqB22GtgqgZ+ER9DrtAIgFdJFvSiO+FsH xHwbib9Ymu02VQItw/obDGaUq2Z7g/y0n4bqY4r/admFD/w9F53nBrI5sdles/OW cbb1j43sIc4//xUk3NENPubnZH4JP2rBM7WVAjTQrSeOBj0F+7jvy3uV66JwGfOc o0Yv5Fv5jyKWNRqNu9+QM9jnwT3w9ZgG4z6u2rrWVzhb/BLw70KNlTnRJuJ8jM/R 0hmASVEVkQvKz3dDOjy6m9N/m8jwmP/EmqVyShUedAJHwdRKjOG9K6m3iYnQigD6 2QpVL4GIusrXhcGq8qPT3AYy1jNtJ33drfT3R3jyiVc8TEytnEiyzyGoNOhJKSur Dx2dgKLnk2TxOl3KbUrDgLvkUTWg6VxKO8xpY0JKOSO4MEVZGJY6DxIJhVXsrbHL lQmpAKEnC4m0/AAtmu1Q2ceCfNrofindXyNBY8uHSf+cJ0LN+USSt036sjQoHx/5 h8C12EpqtaEI5sF662LIcO5KAjc3bL4IS6oH6WZOUyiEDpF1E+zEfJl
Bug#843631: marked as done (Downstream incompatibilities due to SSL_ST_*)
Your message dated Wed, 09 Nov 2016 22:00:05 +0100 with message-id <147872520544.19555.8999601644944339...@auryn.jones.dk> and subject line Re: Bug#843783: deluge-gtk: fails to start: AttributeError: 'module' object has no attribute 'SSL_ST_INIT' has caused the Debian Bug report #843783, regarding Downstream incompatibilities due to SSL_ST_* 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.) -- 843783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843783 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-openssl Version: 16.1.0-1 Severity: critical Justification: breaks unrelated software Hello, I get the following exception when running my Ansible playbook. Looking at the trace the error appears to be coming all the way from Python OpenSSL library, so filing a bug here. ``` Traceback (most recent call last): File "/usr/bin/ansible-playbook", line 92, in exit_code = cli.run() File "/usr/lib/python2.7/dist-packages/ansible/cli/playbook.py", line 154, in run results = pbex.run() File "/usr/lib/python2.7/dist-packages/ansible/executor/playbook_executor.py", line 81, in run self._tqm.load_callbacks() File "/usr/lib/python2.7/dist-packages/ansible/executor/task_queue_manager.py", line 171, in load_callbacks for callback_plugin in callback_loader.all(class_only=True): File "/usr/lib/python2.7/dist-packages/ansible/plugins/__init__.py", line 368, in all self._module_cache[path] = self._load_module_source(name, path) File "/usr/lib/python2.7/dist-packages/ansible/plugins/__init__.py", line 319, in _load_module_source module = imp.load_source(name, path, module_file) File "/usr/lib/python2.7/dist-packages/ansible/plugins/callback/hipchat.py", line 32, in from ansible.module_utils.urls import open_url File "/usr/lib/python2.7/dist-packages/ansible/module_utils/urls.py", line 128, in from urllib3.contrib.pyopenssl import ssl_wrap_socket File "/usr/lib/python2.7/dist-packages/urllib3/contrib/pyopenssl.py", line 54, in import OpenSSL.SSL File "/usr/lib/python2.7/dist-packages/OpenSSL/__init__.py", line 8, in from OpenSSL import rand, crypto, SSL File "/usr/lib/python2.7/dist-packages/OpenSSL/SSL.py", line 112, in SSL_ST_INIT = _lib.SSL_ST_INIT AttributeError: 'module' object
Bug#828608: xmltooling: FTBFS with openssl 1.1.0
On Wed, Nov 09, 2016 at 07:13:58PM +0100, Ferenc Wágner wrote: > struct curl_tlssessioninfo* tlsinfo = nullptr; > CURLcode infocode = curl_easy_getinfo(ctx->m_handle, > CURLINFO_TLS_SSL_PTR, &tlsinfo); > if (infocode == CURLE_OK && tlsinfo && tlsinfo->backend == > CURLSSLBACKEND_OPENSSL && tlsinfo->internals) { > SSL* ssl = reinterpret_cast(tlsinfo->internals); > const SSL_CIPHER* cipher = SSL_get_current_cipher(ssl); > log.debug("SSL version: %s, cipher: %s", > SSL_get_version(ssl), cipher ? SSL_CIPHER_get_name(cipher) : "unknown"); Can I just say this is really ugly code? It's called "internal", you really have no business of touching this. And that just for some debug log. > xmltooling::xml_ssl_ctx_callback(CURL* curl, SSL_CTX* ssl_ctx, void* userptr) > { Since libcurl seems to be exposing this functionality, I think you need to use the same version of openssl than libcurl is using. libcurl really shouldn't have been exposing this. > CURLSOAPTransport* conf = reinterpret_cast(userptr); > > // Default flags manually disable SSLv2 and SSLv3 so we're not dependent > on libcurl > // to do it. Also disable the ticket option where implemented, since this > breaks a > // variety of servers. Newer libcurl also does this for us. > #ifdef SSL_OP_NO_TICKET > SSL_CTX_set_options(ssl_ctx, conf->m_openssl_ops|SSL_OP_NO_TICKET); > #else > SSL_CTX_set_options(ssl_ctx, conf->m_openssl_ops); > #endif I guess this is from the day that there were servers that where tls extension intolerant. They all really should support this now. But libcurl just ignores the ticket anyway, but does support the session id, so it's actually good that curl currently sets this itself. But curl should really add support for session tickets instead. > #ifndef XMLTOOLING_NO_XMLSEC > if (conf->m_cred) > conf->m_cred->attach(ssl_ctx); > > if (conf->m_trustEngine) { > SSL_CTX_set_verify(ssl_ctx,SSL_VERIFY_PEER,nullptr); Curl should be doing this by default, and actually has a setting for this ... > #if (OPENSSL_VERSION_NUMBER >= 0x00907000L) > // With 0.9.7, we can pass a callback argument directly. > SSL_CTX_set_cert_verify_callback(ssl_ctx,verify_callback,userptr); Is there a reason it implements it's own certificate verification rather than using curl's? I guess curl didn't do this always. > #else > // With 0.9.6, there's no argument, so we're going to use a really > embarrassing hack and > // stuff the argument in the depth property where it will get copied > to the context object > // that's handed to the callback. > SSL_CTX_set_cert_verify_callback(ssl_ctx,reinterpret_cast (*)()>(verify_callback),nullptr); > SSL_CTX_set_verify_depth(ssl_ctx,reinterpret_cast(userptr)); Code that still supports 0.9.6? Can I suggest you rip that? It at least looks to me you could just remove all code that is related to libssl and let curl do it for you. But it's of course still using libcrypto for other things. Kurt
Processed: reassign 843783 to python-openssl
Processing commands for cont...@bugs.debian.org: > reassign 843783 python-openssl Bug #843783 [python-cryptography] deluge-gtk: fails to start: AttributeError: 'module' object has no attribute 'SSL_ST_INIT' Bug #843631 [python-cryptography] Downstream incompatibilities due to SSL_ST_* Bug reassigned from package 'python-cryptography' to 'python-openssl'. Bug reassigned from package 'python-cryptography' to 'python-openssl'. Ignoring request to alter found versions of bug #843783 to the same values previously set Ignoring request to alter found versions of bug #843631 to the same values previously set Ignoring request to alter fixed versions of bug #843783 to the same values previously set Ignoring request to alter fixed versions of bug #843631 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 843631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843631 843783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843783 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#797941: marked as done (src:pbnj: maintainer address bounces)
Your message dated Wed, 09 Nov 2016 21:46:12 +0100 with message-id <1478724372.7401.0.ca...@debian.org> and subject line Re: src:pbnj: maintainer address bounces has caused the Debian Bug report #797941, regarding src:pbnj: maintainer address bounces 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.) -- 797941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pbnj Severity: serious Tags: sid The maintainer address for pbnj bounces, see below. Given the package was last uploaded by the maintainer in 2007, maybe the package should be orphaned? Ansgar Mail Delivery System writes: > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > > ja...@ccs.neu.edu > SMTP error from remote mail server after RCPT TO:: > host amber.ccs.neu.edu [129.10.116.51]: 550 unknown user > > -- This is a copy of the message, including all the headers. -- > [...] > To: ja...@ccs.neu.edu (Joshua D. Abraham), gregor herrmann > X-DAK: dak process-upload > X-Debian: DAK > X-Debian-Package: pbnj > Precedence: bulk > Auto-Submitted: auto-generated > MIME-Version: 1.0 > Content-Type: text/plain; charset="utf-8" > Content-Transfer-Encoding: 8bit > Subject: pbnj_2.04-4.1_sourceonly.changes ACCEPTED into unstable > Message-Id: > Date: Mon, 31 Aug 2015 17:23:33 + > > > > Accepted: > > Format: 1.8 > Date: Wed, 26 Aug 2015 18:37:26 +0200 > Source: pbnj > Binary: pbnj > Architecture: source > Version: 2.04-4.1 > Distribution: unstable > Urgency: medium > Maintainer: Joshua D. Abraham > Changed-By: gregor herrmann > Closes: 795637 > Description: > pbnj - a suite of tools to monitor changes on a network > Changes: > pbnj (2.04-4.1) unstable; urgency=medium > . >* Non-maintainer upload. >* Fix "FTBFS with perl 5.22 in experimental (MakeMaker changes)": > use DESTDIR in debian/rules. > (Closes: #795637) > Checksums-Sha1: > e639e9d6ffbf13ce22995a8d5dc3f98846f2d7d1 1959 pbnj_2.04-4.1.dsc > 0a497e7c312526937613ff9238cbb7be0562293f 2841 pbnj_2.04-4.1.diff.gz > Checksums-Sha256: > 717239508ec532f3f59e5f520efb511aa9e756680c358ca22237cdba294ab572 1959 > pbnj_2.04-4.1.dsc > 16f0653da19de1b6e2819ebd67a59fb047196320927b4674af612ce8d1594821 2841 > pbnj_2.04-4.1.diff.gz > Files: > 3563b6f8fab4f91601346ce046338bcb 1959 net optional pbnj_2.04-4.1.dsc > 6b6fd5e1386e11c477ffa7647c632485 2841 net optional pbnj_2.04-4.1.diff.gz > > > > Thank you for your contribution to Debian. --- End Message --- --- Begin Message --- The package has been orphaned on request and behalf of the maintainer. -- tobi (for the MIA team)--- End Message ---
Processed: Re: gazebo: diff for NMU version 7.3.1+dfsg-1.1
Processing control commands: > tags -1 pending Bug #843243 [gazebo] gazebo: diff for NMU version 7.3.1+dfsg-1.1 Bug #843249 [gazebo] gazebo: diff for NMU version 7.3.1+dfsg-1.1 Added tag(s) pending. Added tag(s) pending. -- 843243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843243 843249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843249 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843243: gazebo: diff for NMU version 7.3.1+dfsg-1.1
control: tags -1 pending On deferred/5 (patch attached) G. On Sat, 5 Nov 2016 12:11:51 + (UTC) Gianfranco Costamagna wrote: > Package: gazebo > Version: 7.3.1+dfsg-1 > Severity: serious > Justification: FTBFS with ongoing boost1.62 transition > > Tags: patch > > Dear maintainer, > > I've prepared an NMU for gazebo (versioned as 7.3.1+dfsg-1.1) and > not uploaded it :) > > it is a cherry-pick of an upstream build fix (even if I found it after > uploading > the fix in Ubuntu). > Can you please apply and upload? this is fixing a build failure with the > current > sid package. > > Regards. > > The NMU needs to sed UNRELEASED/unstable and to close this bug :) > > > G. diff -Nru gazebo-7.3.1+dfsg/debian/changelog gazebo-7.3.1+dfsg/debian/changelog --- gazebo-7.3.1+dfsg/debian/changelog 2016-09-16 00:09:49.0 +0200 +++ gazebo-7.3.1+dfsg/debian/changelog 2016-11-09 21:36:30.0 +0100 @@ -1,3 +1,11 @@ +gazebo (7.3.1+dfsg-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * d/p/fix-boost1.62.patch: cherry-pick upstream commit to fix +a boost1.62 build failure due to a missing include (Closes: #843243). + + -- Gianfranco Costamagna Sat, 05 Nov 2016 13:06:20 +0100 + gazebo (7.3.1+dfsg-1) unstable; urgency=medium * Imported Upstream version 7.3.1 diff -Nru gazebo-7.3.1+dfsg/debian/patches/fix-boost1.62.patch gazebo-7.3.1+dfsg/debian/patches/fix-boost1.62.patch --- gazebo-7.3.1+dfsg/debian/patches/fix-boost1.62.patch1970-01-01 01:00:00.0 +0100 +++ gazebo-7.3.1+dfsg/debian/patches/fix-boost1.62.patch2016-11-09 21:36:30.0 +0100 @@ -0,0 +1,14 @@ +Description: fix a build failure with boost1.62 +Author: Carlos Agüero +Origin: https://bitbucket.org/osrf/gazebo/commits/5a7cfea81159d5287a561bc8be035f89f0dc303d + +--- gazebo-7.3.1+dfsg.orig/gazebo/rendering/Camera.cc gazebo-7.3.1+dfsg/gazebo/rendering/Camera.cc +@@ -25,6 +25,7 @@ + + #include + #include ++#include + #include + + #ifndef _WIN32 diff -Nru gazebo-7.3.1+dfsg/debian/patches/series gazebo-7.3.1+dfsg/debian/patches/series --- gazebo-7.3.1+dfsg/debian/patches/series 2016-09-15 23:57:55.0 +0200 +++ gazebo-7.3.1+dfsg/debian/patches/series 2016-11-09 21:36:30.0 +0100 @@ -4,3 +4,4 @@ 0009-fix-gcc6-linking.patch 0001-fix_tinyxml_constant.patch 0004-fix-status-double-declaration.patch +fix-boost1.62.patch signature.asc Description: OpenPGP digital signature
Bug#793090: marked as done (src:ipgrab: maintainer address bounces)
Your message dated Wed, 09 Nov 2016 21:34:09 +0100 with message-id <1478723649.7260.1.ca...@debian.org> and subject line Re: src:ipgrab: maintainer address bounces has caused the Debian Bug report #793090, regarding src:ipgrab: maintainer address bounces 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.) -- 793090: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ipgrab Source-Version: 0.9.10-1 Tags: sid Severity: serious X-Debbugs-Cc: Martin Michlmayr The maintainer address for ipgrab bounces, see below. Ansgar Mail Delivery System writes: > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > > ebros...@netgarage.org > SMTP error from remote mail server after RCPT TO:: > host mail.netgarage.org [176.9.4.150]: 550 5.1.1 : > Recipient address rejected: User unknown in virtual mailbox table > > -- This is a copy of the message, including all the headers. -- > > Return-path: [...] > From: Debian FTP Masters > To: Dennis Krzyzaniak , Martin Michlmayr > , > X-DAK: dak process-upload > X-Debian: DAK > X-Debian-Package: ipgrab > Precedence: bulk > Auto-Submitted: auto-generated > MIME-Version: 1.0 > Content-Type: text/plain; charset="utf-8" > Content-Transfer-Encoding: 8bit > Subject: ipgrab_0.9.10-1.1_amd64.changes ACCEPTED into unstable > Message-Id: > Date: Thu, 16 Jul 2015 18:19:36 + > > > > Accepted: > > Format: 1.8 > Date: Thu, 16 Jul 2015 11:04:54 -0400 > Source: ipgrab > Binary: ipgrab > Architecture: source amd64 > Version: 0.9.10-1.1 > Distribution: unstable > Urgency: medium > Maintainer: Dennis Krzyzaniak > Changed-By: Martin Michlmayr > Description: > ipgrab - tcpdump-like utility that prints detailed header information > Closes: 739562 777917 > Changes: > ipgrab (0.9.10-1.1) unstable; urgency=medium > . >* Non-maintainer upload. >* Fix build failure with GCC 5. Patch from Tim Potter. (Closes: #777917) >* Fix build failure with clang. Patch from Arthur Marble. (Closes: > #739562) > Checksums-Sha1: > be0724d0efbd33c7988b7c87993bbb97a503707a 1683 ipgrab_0.9.10-1.1.dsc > 0338a725d887b5521f0f19d222f4034b4cc2fd18 5360 ipgrab_0.9.10-1.1.debian.tar.xz > 6bdda64e591328a01d293712909dbbb39a605d11 82254 ipgrab_0.9.10-1.1_amd64.deb > Checksums-Sha256: > 52f18304d9b7a15ef2f7f666308e320289381b9eefed4d67a785ad3b541ac176 1683 > ipgrab_0.9.10-1.1.dsc > 0ebb6bade0171faa1d658d97bf31da00536d6529382ffd13ea04e7fb9293f705 5360 > ipgrab_0.9.10-1.1.debian.tar.xz > b0797d6ec228244f86768e45b416e3e8378c190adf83b93b733c16e1779193b2 82254 > ipgrab_0.9.10-1.1_amd64.deb > Files: > 3dd2e264c33483d4cc6779eae8cd62d0 1683 net optional ipgrab_0.9.10-1.1.dsc > 192a57a8ea634a524ab693df3b1e7a12 5360 net optional > ipgrab_0.9.10-1.1.debian.tar.xz > e6c7cb8cbe5c07cbc4cc5ae7fa5899f1 82254 net optional > ipgrab_0.9.10-1.1_amd64.deb > > > > Thank you for your contribution to Debian. --- End Message --- --- Begin Message --- The package has now been orphaned on behalf of the MIA Team, see #843812 -- tobi (for the MIA Team)--- End Message ---
Bug#843783: deluge-gtk: fails to start: AttributeError: 'module' object has no attribute 'SSL_ST_INIT'
Quoting Andrew Starr-Bochicchio (2016-11-09 16:36:40) > On Wed, Nov 9, 2016 at 10:24 AM, Jonas Smedegaard wrote: > > > > My deluge-gtk recently stopped being able to start at all, leaving the > > following in .xsession-errors: > > Thanks for the report. This looks like is a bug in > python-cryptography. See: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843631 Thanks for that hint. I can confirm that lowering python-cryptography from unstable 1.5.3-1 to testing 1.5.2-1 make deluge-gtk work again. Reassigning + force-merging + tagging affects accordingly. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
Processed: canl-c: FTBFS with openssl 1.1.0
Processing control commands: > block 828258 by 828236 Bug #828258 [src:canl-c] canl-c: FTBFS with openssl 1.1.0 828258 was not blocked by any bugs. 828258 was blocking: 827061 Added blocking bug(s) of 828258: 828236 -- 828258: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: gridsite: FTBFS with openssl 1.1.0
Processing control commands: > block 828330 by 828236 Bug #828330 [src:gridsite] gridsite: FTBFS with openssl 1.1.0 828330 was not blocked by any bugs. 828330 was blocking: 827061 Added blocking bug(s) of 828330: 828236 -- 828330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#828608: xmltooling: FTBFS with openssl 1.1.0
On Wed, Nov 09, 2016 at 07:13:58PM +0100, Ferenc Wágner wrote: > wf...@niif.hu (Ferenc Wágner) writes: > > > Can you recommend a reliable way to decide whether there really are any > > conflicts between the different OpenSSL libraries used by libcurl and > > xmltooling? > > I've found two code fragments which pass OpenSSL structures between curl > (OpenSSL 1.1) and XMLTooling (OpenSSL 1.0) in CURLSOAPTransport.cpp: Yes, they look problematic. > So the issue isn't clear-cut at all (at least to me). Can we have > libcurl4-openssl1.0-dev? Any other ideas? We can also just try to move xmltooling to openssl 1.1? Kurt
Bug#843644: marked as done (AttributeError: 'module' object has no attribute)
Your message dated Wed, 09 Nov 2016 19:34:21 + with message-id and subject line Bug#843644: fixed in pyopenssl 16.2.0-1 has caused the Debian Bug report #843644, regarding AttributeError: 'module' object has no attribute 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.) -- 843644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-openssl Version: 16.1.0-1 Severity: critical Justification: breaks unrelated software Hello, I get the following exception when running my Ansible playbook. Looking at the trace the error appears to be coming all the way from Python OpenSSL library, so filing a bug here. ``` Traceback (most recent call last): File "/usr/bin/ansible-playbook", line 92, in exit_code = cli.run() File "/usr/lib/python2.7/dist-packages/ansible/cli/playbook.py", line 154, in run results = pbex.run() File "/usr/lib/python2.7/dist-packages/ansible/executor/playbook_executor.py", line 81, in run self._tqm.load_callbacks() File "/usr/lib/python2.7/dist-packages/ansible/executor/task_queue_manager.py", line 171, in load_callbacks for callback_plugin in callback_loader.all(class_only=True): File "/usr/lib/python2.7/dist-packages/ansible/plugins/__init__.py", line 368, in all self._module_cache[path] = self._load_module_source(name, path) File "/usr/lib/python2.7/dist-packages/ansible/plugins/__init__.py", line 319, in _load_module_source module = imp.load_source(name, path, module_file) File "/usr/lib/python2.7/dist-packages/ansible/plugins/callback/hipchat.py", line 32, in from ansible.module_utils.urls import open_url File "/usr/lib/python2.7/dist-packages/ansible/module_utils/urls.py", line 128, in from urllib3.contrib.pyopenssl import ssl_wrap_socket File "/usr/lib/python2.7/dist-packages/urllib3/contrib/pyopenssl.py", line 54, in import OpenSSL.SSL File "/usr/lib/python2.7/dist-packages/OpenSSL/__init__.py", line 8, in from OpenSSL import rand, crypto, SSL File "/usr/lib/python2.7/dist-packages/OpenSSL/SSL.py", line 112, in SSL_ST_INIT = _lib.SSL_ST_INIT AttributeError: 'module' object has no attribute
Bug#837570: Fix for the msrtool FTBFS
Control: tags -1 patch A fix for the msrtool FTBFS is attached. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed Description: Don't build with -fno-pic -fno-pic isn't needed, and it breaks building when the compiler defaults to PIE. Author: Adrian Bunk Bug-Debian: https://bugs.debian.org/837570 --- msrtool-20141027.orig/Makefile.in +++ msrtool-20141027/Makefile.in @@ -23,7 +23,7 @@ PROGRAM = msrtool CC = @CC@ INSTALL = @INSTALL@ PREFIX = @PREFIX@ -CFLAGS = @CFLAGS@ -fno-pic +CFLAGS = @CFLAGS@ LDFLAGS = @LDFLAGS@ TARGETS = geodegx2.o geodelx.o cs5536.o k8.o intel_pentium3_early.o intel_pentium3.o intel_pentium4_early.o intel_pentium4_later.o intel_core1.o intel_core2_early.o intel_core2_later.o intel_nehalem.o intel_atom.o
Processed: Fix for the msrtool FTBFS
Processing control commands: > tags -1 patch Bug #837570 [src:msrtool] msrtool: FTBFS with bindnow and PIE enabled Added tag(s) patch. -- 837570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 840458 https://github.com/linbox-team/linbox/issues/44 Bug #840458 [src:linbox] linbox: FTBFS on i386: illegal instruction in test-{cra,charpoly} Set Bug forwarded-to-address to 'https://github.com/linbox-team/linbox/issues/44'. > thanks Stopping processing here. Please contact me if you need assistance. -- 840458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840458 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bts
Processing commands for cont...@bugs.debian.org: > reopen 497471 Bug #497471 {Done: "FedEx International Next Flight" } [cdimage.debian.org] sarge images have syslinux binaries without source Bug reopened Ignoring request to alter fixed versions of bug #497471 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 497471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843432: marked as done (libwww-curl-perl: FTBFS: error: 'CURL_STRICTER' undeclared)
Your message dated Wed, 09 Nov 2016 18:49:34 + with message-id and subject line Bug#843432: fixed in libwww-curl-perl 4.17-3 has caused the Debian Bug report #843432, regarding libwww-curl-perl: FTBFS: error: 'CURL_STRICTER' undeclared 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.) -- 843432: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libwww-curl-perl Version: 4.17-2 Severity: serious User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org, c...@packages.debian.org As noticed by the reproducible-builds.org CI system, this package fails to build on current sid. It looks like this broke with the recent curl 7.51.0-1 upload, so cc'ing the curl maintainers too. https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/libwww-curl-perl.html Excerpt from a local amd64 build log: x86_64-linux-gnu-gcc -c -I/usr/include -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION=\"4.17\" -DXS_VERSION=\"4.17\" -fPIC "-I/usr/lib/x86_64-linux-gnu/perl/5.24/CORE" Curl.c In file included from Curl.xs:574:0: curlopt-constants.c: In function 'constant': curlopt-constants.c:19:58: warning: 'return' with no value, in function returning non-void if (strEQ(name, "DID_MEMORY_FUNC_TYPEDEFS")) return CURL_DID_MEMORY_FUNC_TYPEDEFS; ^~ curlopt-constants.c:2:1: note: declared here constant(const char *name) ^~~~ curlopt-constants.c:128:49: error: 'CURL_STRICTER' undeclared (first use in this function) if (strEQ(name, "STRICTER")) return CURL_STRICTER; ^ curlopt-constants.c:128:49: note: each undeclared identifier is reported only once for each function it appears in curlopt-constants.c:2051:44: warning: overflow in implicit constant conversion [-Woverflow] if (strEQ(name, "ANY")) return CURLAUTH_ANY; ^~~~ curlopt-constants.c:2052:48: warning: overflow in implicit constant conversion [-Woverflow] if (strEQ(name, "ANYSAFE")) return CURLAUTH_ANYSAFE; ^~~~ Makefile:357: recipe for target 'Curl.o' failed make[1]: *** [Curl.o] Error 1 -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Source: libwww-curl-perl Source-Version: 4.17-3 We believe that the bug you reported is fixed in the latest version of libwww-curl-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 843...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libwww-curl-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 09 Nov 2016 19:24:25 +0100 Source: libwww-curl-perl Binary: libwww-curl-perl Architecture: source Version: 4.17-3 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 843432 Description: libwww-curl-perl - Perl bindings to libcurl Changes: libwww-curl-perl (4.17-3) unstable; urgency=medium . [ gregor herrmann ] * Rename autopkgtest configuration file(s) as per new pkg-perl- autopkgtest schema. . [ Salvatore Bonaccorso ] * debian/control: Use HTTPS transport protocol for Vcs-Git URI . [ gregor herrmann ] * debian/copyright: change Copyright-Format 1.0 URL to HTTPS. . [ Martín Ferrari ] * Remove myself from Uploaders. . [ gregor herrmann ] * Remove Jonathan Yu from Uploaders. Thanks for your work! * Remove Jose Luis Rivas from Uploaders. Thanks for your work! * Remove Nathan Handler from Uploaders. Thanks for your work! * Remove Ryan Niebur from Uploaders. Thanks for your
Bug#828608: xmltooling: FTBFS with openssl 1.1.0
On 11/9/16, 1:13 PM, "Pkg-shibboleth-devel on behalf of Ferenc Wágner" wrote: >wf...@niif.hu (Ferenc Wágner) writes: > > > Can you recommend a reliable way to decide whether there really are any >> conflicts between the different OpenSSL libraries used by libcurl and >> xmltooling? I didn't see this earlier, but certainly it's impossible to mix libraries like that, full stop. That's never possible, whether there's any explicit data structure overlap or not. It would be like mixing C/C++ runtime versions. -- Scott
Bug#843073: dpkg-shlibdeps: broken on i386 with merged /usr
Hi Michael, On Wed, Nov 09, 2016 at 07:16:53PM +0100, Michael Biebl wrote: > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/systemd.html > Do you also have builds for i386? (which this issue is about, amd64 is fine) yes, they are linked from that url as well, though you can also go directly to https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/systemd.html I've just checked https://jenkins.debian.net/view/reproducible/view/Debian_setup_i386/job/reproducible_setup_pbuilder_unstable_i386_profitbricks2/257/console and found nothing of usrmerge in there, which makes sense, as we use debootstrap from stable… what we could maybe do, is to use debootstrap from jessie-backports and vary this regularily, so we would setup half of our pbuilders with merged /usr and the other half without. cc:ing the reproducible builds list for feedback. -- cheers, Holger signature.asc Description: Digital signature
Bug#843073: dpkg-shlibdeps: broken on i386 with merged /usr
Hi Holger, Am 09.11.2016 um 18:10 schrieb Holger Levsen: > On Sat, Nov 05, 2016 at 08:58:06PM +0100, Michael Biebl wrote: >> As this breaks packages to build successfully, I'm bumping this to RC. >> E.g. I'm unable to successfully build systemd in a freshly created >> chroot on i386. I suspect once the buildds update their chroot, it will >> affect a lot more packages. > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/systemd.html > shows that we could build systemd on sid. The builds are being done in > recently created pbuilder setups though. Are you sure those buildds actually use a merged-usr setup? I've just checked the build log of 232-2, and the configure log has checking for quotaon... /sbin/quotaon checking for quotacheck... /sbin/quotacheck checking for setcap... /usr/sbin/setcap checking for kill... /bin/kill checking for kmod... /bin/kmod checking for kexec... /sbin/kexec checking for sulogin... /sbin/sulogin checking for mount... /bin/mount checking for umount... /bin/umount This indicates, that the chroot is not actually using a merged-usr setup, otherwise it would have detected the binaries in /usr/bin. Can you check the buildds and post the output of ls -l from the chroot's root directory? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#840329: marked as done (taglib-extras: FTBFS: CMake Error at cmake/modules/FindTaglib.cmake:132 (message): Could not find Taglib)
Your message dated Wed, 09 Nov 2016 18:23:56 + with message-id and subject line Bug#840329: fixed in taglib-extras 1.0.1-3.1 has caused the Debian Bug report #840329, regarding taglib-extras: FTBFS: CMake Error at cmake/modules/FindTaglib.cmake:132 (message): Could not find Taglib 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.) -- 840329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840329 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: taglib-extras Version: 1.0.1-3 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, taglib-extras fails to build from source in unstable/amd64: [..] ignore line: [/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_06e1e.dir/link.txt --verbose=1] ignore line: [/usr/bin/c++ -fvisibility=hidden -fvisibility-inlines-hidden -v CMakeFiles/cmTC_06e1e.dir/CMakeCXXCompilerABI.cpp.o -o cmTC_06e1e -rdynamic ] ignore line: [Using built-in specs.] ignore line: [COLLECT_GCC=/usr/bin/c++] ignore line: [COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper] ignore line: [Target: x86_64-linux-gnu] ignore line: [Configured with: ../src/configure -v --with-pkgversion='Debian 6.2.0-5' --with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-6 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu] ignore line: [Thread model: posix] ignore line: [gcc version 6.2.0 20160927 (Debian 6.2.0-5) ] ignore line: [COMPILER_PATH=/usr/lib/gcc/x86_64-linux-gnu/6/:/usr/lib/gcc/x86_64-linux-gnu/6/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/6/:/usr/lib/gcc/x86_64-linux-gnu/] ignore line: [LIBRARY_PATH=/usr/lib/gcc/x86_64-linux-gnu/6/:/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/6/../../../../lib/:/lib/x86_64-linux-gnu/:/lib/../lib/:/usr/lib/x86_64-linux-gnu/:/usr/lib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/6/../../../:/lib/:/usr/lib/] ignore line: [COLLECT_GCC_OPTIONS='-fvisibility=hidden' '-fvisibility-inlines-hidden' '-v' '-o' 'cmTC_06e1e' '-rdynamic' '-shared-libgcc' '-mtune=generic' '-march=x86-64'] link line: [ /usr/lib/gcc/x86_64-linux-gnu/6/collect2 -plugin /usr/lib/gcc/x86_64-linux-gnu/6/liblto_plugin.so -plugin-opt=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper -plugin-opt=-fresolution=/tmp/ccIWsPIW.res -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lc -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lgcc --sysroot=/ --build-id --eh-frame-hdr -m elf_x86_64 --hash-style=gnu -export-dynamic -dynamic-linker /lib64/ld-linux-x86-64.so.2 -o cmTC_06e1e /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/crt1.o /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/crti.o /usr/lib/gcc/x86_64-linux-gnu/6/crtbegin.o -L/usr/lib/gcc/x86_64-linux-gnu/6 -L/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu -L/usr/lib/gcc/x86_64-linux-gnu/6/../../../../lib -L/lib/x86_64-linux-gnu -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/6/../../.. CMakeFiles/cmTC_06e1e.dir/CMakeCXXCompilerABI.cpp.o -lstdc++ -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc /usr/lib/gcc/x86_64-linux-gnu/6/crtend.o /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/crtn.o] arg [/usr/lib/gcc/x86_64-linux-gnu/6/collect2] ==> ignore arg [-plugin] ==> ignore arg [/us
Bug#828608: xmltooling: FTBFS with openssl 1.1.0
On Wed, Nov 09, 2016 at 04:34:32PM +0100, Ferenc Wágner wrote: > Hi, > > I switched xmltooling to libssl1.0-dev just like I switched > xml-security-c beforehand. I got the following warnings: > > libtool: link: g++ -Wall -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -O2 -DNDEBUG -Wl,-z > -Wl,relro -Wl,-z -Wl,now -o .libs/xmltoolingtest > xmltoolingtest-xmltoolingtest.o xmltoolingtest-ComplexXMLObjectTest.o > xmltoolingtest-DateTimeTest.o xmltoolingtest-ExceptionTest.o > xmltoolingtest-MarshallingTest.o xmltoolingtest-SOAPTest.o > xmltoolingtest-UnmarshallingTest.o xmltoolingtest-TemplateEngineTest.o > xmltoolingtest-EncryptionTest.o > xmltoolingtest-FilesystemCredentialResolverTest.o > xmltoolingtest-InlineKeyResolverTest.o xmltoolingtest-KeyInfoTest.o > xmltoolingtest-MemoryStorageServiceTest.o > xmltoolingtest-NonVisibleNamespaceTest.o xmltoolingtest-PKIXEngineTest.o > xmltoolingtest-SecurityHelperTest.o xmltoolingtest-SignatureTest.o -lpthread > ../xmltooling/.libs/libxmltooling.so -lxml-security-c -lssl -lcrypto > /usr/lib/x86_64-linux-gnu/libcurl.so -lxerces-c -pthread > /usr/bin/ld: warning: libssl.so.1.1, needed by > /usr/lib/x86_64-linux-gnu/libcurl.so, may conflict with libssl.so.1.0.2 > /usr/bin/ld: warning: libcrypto.so.1.1, needed by > /usr/lib/x86_64-linux-gnu/libcurl.so, may conflict with libcrypto.so.1.0.2 > > Can you recommend a reliable way to decide whether there really are any > conflicts between the different OpenSSL libraries used by libcurl and > xmltooling? I think those warnings can be ignored. What I'm confused about is why you link to libssl, and not just libcrypto. Kurt
Bug#828608: xmltooling: FTBFS with openssl 1.1.0
wf...@niif.hu (Ferenc Wágner) writes: > Can you recommend a reliable way to decide whether there really are any > conflicts between the different OpenSSL libraries used by libcurl and > xmltooling? I've found two code fragments which pass OpenSSL structures between curl (OpenSSL 1.1) and XMLTooling (OpenSSL 1.0) in CURLSOAPTransport.cpp: #ifdef HAVE_CURLINFO_TLS_SSL_PTR if (!ctx->m_cipherLogged) { Category& log = Category::getInstance(XMLTOOLING_LOGCAT ".SOAPTransport.CURL"); if (log.isDebugEnabled()) { struct curl_tlssessioninfo* tlsinfo = nullptr; CURLcode infocode = curl_easy_getinfo(ctx->m_handle, CURLINFO_TLS_SSL_PTR, &tlsinfo); if (infocode == CURLE_OK && tlsinfo && tlsinfo->backend == CURLSSLBACKEND_OPENSSL && tlsinfo->internals) { SSL* ssl = reinterpret_cast(tlsinfo->internals); const SSL_CIPHER* cipher = SSL_get_current_cipher(ssl); log.debug("SSL version: %s, cipher: %s", SSL_get_version(ssl), cipher ? SSL_CIPHER_get_name(cipher) : "unknown"); } } ctx->m_cipherLogged = true; } #endif and xmltooling::xml_ssl_ctx_callback(CURL* curl, SSL_CTX* ssl_ctx, void* userptr) { CURLSOAPTransport* conf = reinterpret_cast(userptr); // Default flags manually disable SSLv2 and SSLv3 so we're not dependent on libcurl // to do it. Also disable the ticket option where implemented, since this breaks a // variety of servers. Newer libcurl also does this for us. #ifdef SSL_OP_NO_TICKET SSL_CTX_set_options(ssl_ctx, conf->m_openssl_ops|SSL_OP_NO_TICKET); #else SSL_CTX_set_options(ssl_ctx, conf->m_openssl_ops); #endif #ifndef XMLTOOLING_NO_XMLSEC if (conf->m_cred) conf->m_cred->attach(ssl_ctx); if (conf->m_trustEngine) { SSL_CTX_set_verify(ssl_ctx,SSL_VERIFY_PEER,nullptr); #if (OPENSSL_VERSION_NUMBER >= 0x00907000L) // With 0.9.7, we can pass a callback argument directly. SSL_CTX_set_cert_verify_callback(ssl_ctx,verify_callback,userptr); #else // With 0.9.6, there's no argument, so we're going to use a really embarrassing hack and // stuff the argument in the depth property where it will get copied to the context object // that's handed to the callback. SSL_CTX_set_cert_verify_callback(ssl_ctx,reinterpret_cast(verify_callback),nullptr); SSL_CTX_set_verify_depth(ssl_ctx,reinterpret_cast(userptr)); #endif } #endif if (conf->m_ssl_callback && !conf->m_ssl_callback(conf, ssl_ctx, conf->m_ssl_userptr)) return CURLE_SSL_CERTPROBLEM; return CURLE_OK; } So the issue isn't clear-cut at all (at least to me). Can we have libcurl4-openssl1.0-dev? Any other ideas? -- Thanks, Feri
Bug#843073: dpkg-shlibdeps: broken on i386 with merged /usr
Am 09.11.2016 um 18:10 schrieb Holger Levsen: > Hi, > > On Sat, Nov 05, 2016 at 08:58:06PM +0100, Michael Biebl wrote: >> As this breaks packages to build successfully, I'm bumping this to RC. >> E.g. I'm unable to successfully build systemd in a freshly created >> chroot on i386. I suspect once the buildds update their chroot, it will >> affect a lot more packages. > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/systemd.html > shows that we could build systemd on sid. The builds are being done in > recently created pbuilder setups though. Do you also have builds for i386? (which this issue is about, amd64 is fine) -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#842815: Help needed for HDF5 1.10 transition of libsis-jhdf5-java
Hi, Andreas Tille wrote: > I admit I do not have the slightest idea what to do. I also realised > that the host that once hosted the code[1] does not respond any more. > Axel, could you find out where the code was moved? I contacted upstream (Andreas and Olivier were in Cc) and they seem to have changed the hostname for the publically available SVN server: > [1] http://svncisd.ethz.ch/ It's now https://svnsis.ethz.ch/ and the specific library in questions seems to be at https://svnsis.ethz.ch/repos/cisd/jhdf5/. Hope, this helps. Andreas: I'm not sure if the "help" tag was for the "where has the upstream code gone" issue or for general ideas on how to do the transition, so I'm leaving the "help" tag for now. Regards, Axel -- ,''`. | Axel Beckert , http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#843631: Twisted SSL layer is not importable
affects 843631 twisted https://ci.debian.net/data/packages/unstable/amd64/t/twisted/20161109_095205.autopkgtest.log.gz
Processed (with 1 error): Twisted SSL layer is not importable
Processing commands for cont...@bugs.debian.org: > affects 843631 twisted Bug #843631 [python-cryptography] Downstream incompatibilities due to SSL_ST_* Bug #843783 [python-cryptography] deluge-gtk: fails to start: AttributeError: 'module' object has no attribute 'SSL_ST_INIT' Added indication that 843631 affects twisted Added indication that 843783 affects twisted > https://ci.debian.net/data/packages/unstable/amd64/t/twisted/20161109_095205.autopkgtest.log.gz Unknown command or malformed arguments to command. > End of message, stopping processing here. Please contact me if you need assistance. -- 843631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843631 843783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843783 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#831100: marked as done (conquest-dicom-server: FTBFS with GCC 6: cpp_type_traits.h:212:12: error: redefinition of 'struct std::__is_integer')
Your message dated Wed, 09 Nov 2016 17:59:20 + with message-id and subject line Bug#843785: Removed package(s) from unstable has caused the Debian Bug report #831100, regarding conquest-dicom-server: FTBFS with GCC 6: cpp_type_traits.h:212:12: error: redefinition of 'struct std::__is_integer' 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.) -- 831100: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831100 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: conquest-dicom-server Version: 1.4.17d-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160713 qa-ftbfs Justification: FTBFS with GCC 6 on amd64 Hi, During a rebuild of all packages in sid using the gcc-defaults package available in experimental to make GCC default to version 6, your package failed to build on amd64. For more information about GCC 6 and Stretch, see: - https://wiki.debian.org/GCC6 - https://lists.debian.org/debian-devel-announce/2016/06/msg7.html Relevant part (hopefully): > /usr/bin/g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong > -Wformat -Werror=format-security -Ijasper-1.900.1-6ct/src/libjasper/include > -Ijpeg-6c -I/usr/include/lua5.1 -DUNIX -DNATIVE_ENDIAN=1 -DHAVE_LIBJASPER > -DHAVE_LIBJPEG -DUSESQLITE -Wno-write-strings total.cpp -o dgate-sqlite > -lpthread -llua5.1 -lsqlite3 jpeg-6c/libjpeg.a > jasper-1.900.1-6ct/src/libjasper/.libs/libjasper.a -Wno-multichar -Wl,-z,relro > In file included from > jasper-1.900.1-6ct/src/libjasper/include/jasper/jasper.h:65:0, > from nkiqrsop.cpp:255, > from total.cpp:135: > jasper-1.900.1-6ct/src/libjasper/include/jasper/jas_config.h:65:0: warning: > "HAVE_STDDEF_H" redefined > #define HAVE_STDDEF_H 1 > > In file included from jpeg-6c/jpeglib.h:25:0, > from nkiqrsop.cpp:250, > from total.cpp:135: > jpeg-6c/jconfig.h:11:0: note: this is the location of the previous definition > #define HAVE_STDDEF_H > > In file included from > jasper-1.900.1-6ct/src/libjasper/include/jasper/jasper.h:65:0, > from nkiqrsop.cpp:255, > from total.cpp:135: > jasper-1.900.1-6ct/src/libjasper/include/jasper/jas_config.h:71:0: warning: > "HAVE_STDLIB_H" redefined > #define HAVE_STDLIB_H 1 > > In file included from jpeg-6c/jpeglib.h:25:0, > from nkiqrsop.cpp:250, > from total.cpp:135: > jpeg-6c/jconfig.h:12:0: note: this is the location of the previous definition > #define HAVE_STDLIB_H > > In file included from /usr/include/c++/6/cmath:42:0, > from /usr/include/c++/6/math.h:36, > from > jasper-1.900.1-6ct/src/libjasper/include/jasper/jas_fix.h:79, > from > jasper-1.900.1-6ct/src/libjasper/include/jasper/jasper.h:72, > from nkiqrsop.cpp:255, > from total.cpp:135: > /usr/include/c++/6/bits/cpp_type_traits.h:212:12: error: redefinition of > 'struct std::__is_integer' > struct __is_integer > ^~ > /usr/include/c++/6/bits/cpp_type_traits.h:138:12: error: previous definition > of 'struct std::__is_integer' > struct __is_integer > ^~ > In file included from total.cpp:104:0: > filepdu.cxx: In member function 'DICOMDataObject* > PDU_Service::LoadDICOMDataObject(char*)': > filepdu.cxx:126:20: warning: ignoring return value of 'size_t fread(void*, > size_t, size_t, FILE*)', declared with attribute warn_unused_result > [-Wunused-result] > fread(s, 1, 4, fp); > ^ > filepdu.cxx:136:17: warning: ignoring return value of 'size_t fread(void*, > size_t, size_t, FILE*)', declared with attribute warn_unused_result > [-Wunused-result] > fread(s,1,6,fp); > ^ > In file included from total.cpp:114:0: > rtc.cxx: In member function 'BOOL RTC::AttachRTC(char*)': > rtc.cxx:213:39: warning: ignoring return value of 'char* fgets(char*, int, > FILE*)', declared with attribute warn_unused_result [-Wunused-result] > fgets ( s, 1024 - sizeof( INT ), fp ); >^ > rtc.cxx:225:38: warning: ignoring return value of 'char* fgets(char*, int, > FILE*)', declared with attribute warn_unused_result [-Wunused-result] > fgets( s, 1024 - sizeof(INT), fp); > ^ > rtc.cxx:238:40: warning: ignoring return value of 'char* fgets(char*, int, > FILE*)', declared with attribute warn_unused_result [-Wunused-result] > fgets (s, 1024
Bug#843796: civicrm: FTBFS: dh_linktree: link destination debian/civicrm-common/usr/share/civicrm/bower_components/jquery-ui/themes/smoothness/images is a directory
Source: civicrm Version: 4.7.8+dfsg-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, civicrm fails to build from source in unstable/amd64: […] Enabling conf security. Enabling conf serve-cgi-bin. Enabling site 000-default. Created symlink /etc/systemd/system/multi-user.target.wants/apache2.service → /lib/systemd/system/apache2.service. Created symlink /etc/systemd/system/multi-user.target.wants/apache-htcacheclean.service → /lib/systemd/system/apache-htcacheclean.service. invoke-rc.d: could not determine current runlevel invoke-rc.d: policy-rc.d denied execution of start. insserv: warning: current start runlevel(s) (empty) of script `apache-htcacheclean' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `apache-htcacheclean' overrides LSB defaults (0 1 6). Setting up php-net-smtp (1.7.1-2) ... Setting up php-http-request (1.4.4-5) ... Setting up libx11-6:amd64 (2:1.6.3-1) ... Setting up php7.0-cli (7.0.12-2) ... update-alternatives: using /usr/bin/php7.0 to provide /usr/bin/php (php) in auto mode update-alternatives: using /usr/bin/phar7.0 to provide /usr/bin/phar (phar) in auto mode update-alternatives: using /usr/bin/phar.phar7.0 to provide /usr/bin/phar.phar (phar.phar) in auto mode Creating config file /etc/php/7.0/cli/php.ini with new version Setting up php-cli (1:7.0+46) ... Setting up smarty3 (3.1.29-2) ... Setting up php-pear (1:1.10.1+submodules+notgz-8) ... Setting up php-validate (0.8.5-4) ... Setting up libxpm4:amd64 (1:3.5.11-1+b1) ... Setting up libapache2-mod-php5 (5.6.26+dfsg-1) ... Creating config file /etc/php5/apache2/php.ini with new version Module mpm_event disabled. Enabling module mpm_prefork. apache2_switch_mpm Switch to prefork invoke-rc.d: could not determine current runlevel invoke-rc.d: policy-rc.d denied execution of restart. apache2_invoke: Enable module php5 invoke-rc.d: could not determine current runlevel invoke-rc.d: policy-rc.d denied execution of restart. Setting up php-auth-sasl (1.0.6-3) ... Setting up php-mail-mime (1.10.0-2) ... Setting up php-fpdf (3:1.8.1.dfsg-2) ... Setting up libfpdf-tpl-php (1.2-2) ... Setting up php-services-json (1.0.3-1) ... Setting up pkg-php-tools (1.34) ... Setting up libgd3:amd64 (2.2.3-87-gd0fec80-3) ... Setting up php5 (5.6.26+dfsg-1) ... Setting up libfpdi-php (1.4.1-1) ... Setting up php7.0-gd (7.0.12-2) ... Creating config file /etc/php/7.0/mods-available/gd.ini with new version Setting up php-gd (1:7.0+46) ... Setting up php-dompdf (0.6.2+dfsg-3) ... Setting up civicrm-build-deps (4.7.8+dfsg-1) ... Processing triggers for libc-bin (2.24-5) ... Processing triggers for systemd (232-2) ... ** ** Environment ** ** PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin HOSTNAME=266499a3043a TERM=xterm PAGER=more DISPLAY=:0 DOCKER_IMAGE=lamby-debian-sid DEB_BUILD_OPTIONS=parallel=9 PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip HOME=/home/lamby LOGNAME=lamby SHLVL=1 PWD=/home/lamby/temp/cdt.20161109174634.bVmTIyyBNC.db.civicrm/civicrm-4.7.8+dfsg OLDPWD=/home/lamby/temp/cdt.20161109174634.bVmTIyyBNC.db.civicrm GPG_TTY=/dev/console QUILT_PATCHES=debian/patches QUILT_NO_DIFF_INDEX=1 QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index DEBEMAIL=la...@debian.org DEBFULLNAME=Chris Lamb EDITOR=vim LESS=-cgiFx4M GPG_KEY=1E953E27D4311E58 BLASTER=A220 I5 D1 H5 P330 T6 _=/usr/bin/env ** ** Building civicrm 4.7.8+dfsg-1 on amd64 ** ** dpkg-buildpackage -rfakeroot -D -us -uc -b dpkg-buildpackage: info: source package civicrm dpkg-buildpackage: info: source version 4.7.8+dfsg-1 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Dmitry Smirnov dpkg-source --before-build civicrm-4.7.8+dfsg dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean I: civicrm_4.7.8 dh clean --parallel --buildsystem=phppear --with phpcomposer dh_testdir -O--parallel -O--buildsystem=phppear dh_auto_clean -O--parallel -O--buildsystem=phppear debian/rules override_dh_clean make[1]: Entering directory '/home/lamby/temp/cdt.20161109174634.bVmTIyyBNC.db.civicrm/civicrm-4.7.8+dfsg'
Processed: reassign 843783 to python-cryptography, forcibly merging 843631 843783
Processing commands for cont...@bugs.debian.org: > reassign 843783 python-cryptography Bug #843783 [python-openssl] deluge-gtk: fails to start: AttributeError: 'module' object has no attribute 'SSL_ST_INIT' Bug reassigned from package 'python-openssl' to 'python-cryptography'. Ignoring request to alter found versions of bug #843783 to the same values previously set Ignoring request to alter fixed versions of bug #843783 to the same values previously set > forcemerge 843631 843783 Bug #843631 [python-cryptography] Downstream incompatibilities due to SSL_ST_* Bug #843783 [python-cryptography] deluge-gtk: fails to start: AttributeError: 'module' object has no attribute 'SSL_ST_INIT' Severity set to 'critical' from 'grave' Added indication that 843783 affects deluge-gtk,bugwarrior,ansible,bugs-everywhere Merged 843631 843783 > thanks Stopping processing here. Please contact me if you need assistance. -- 843631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843631 843783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843783 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843644: Workaround
I fixed that installing python3-openssl then, removing python-openssl. Not much broken dependencies fortunately.
Bug#843797: koji: FTBFS: help2man: can't get `--help' info from ./cli/koji
Source: koji Version: 1.10.0-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, koji fails to build from source in unstable/amd64: […] dh_auto_build make -j1 make[2]: Entering directory '/home/lamby/temp/cdt.20161109174748.li6xI7ndXh.db.koji/koji-1.10.0' read the makefile make[2]: Leaving directory '/home/lamby/temp/cdt.20161109174748.li6xI7ndXh.db.koji/koji-1.10.0' PYTHONPATH=. help2man --no-info --version-string=1.10.0 -n "Koji build client" ./cli/koji > debian/koji.1 help2man: can't get `--help' info from ./cli/koji Try `--no-discard-stderr' if option outputs to stderr debian/rules:11: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 1 make[1]: Leaving directory '/home/lamby/temp/cdt.20161109174748.li6xI7ndXh.db.koji/koji-1.10.0' debian/rules:8: recipe for target 'build' failed make: *** [build] Error 2 […] The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- koji.1.10.0-1.unstable.amd64.log.txt.gz Description: Binary data
Processed (with 1 error): reassign 843783 to python-openssl, forcibly merging 843631 843783
Processing commands for cont...@bugs.debian.org: > reassign 843783 python-openssl Bug #843783 [deluge-gtk] deluge-gtk: fails to start: AttributeError: 'module' object has no attribute 'SSL_ST_INIT' Bug reassigned from package 'deluge-gtk' to 'python-openssl'. No longer marked as found in versions deluge/1.3.13-1. Ignoring request to alter fixed versions of bug #843783 to the same values previously set > forcemerge 843631 843783 Bug #843631 [python-cryptography] Downstream incompatibilities due to SSL_ST_* Unable to merge bugs because: package of #843783 is 'python-openssl' not 'python-cryptography' Failed to forcibly merge 843631: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 843631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843631 843783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843783 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 843631
Processing commands for cont...@bugs.debian.org: > affects 843631 deluge-gtk Bug #843631 [python-cryptography] Downstream incompatibilities due to SSL_ST_* Added indication that 843631 affects deluge-gtk > thanks Stopping processing here. Please contact me if you need assistance. -- 843631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#828535: ruby2.3: FTBFS with openssl 1.1.0
Control: severity -1 important Hi, On Tue, Sep 13, 2016 at 07:02:07PM +0200, Kurt Roeckx wrote: > On Tue, Sep 13, 2016 at 10:21:34AM -0300, Antonio Terceiro wrote: > > Do we have a timeline for OpenSSL 1.1? > > It currently seems to be when we can get the number of packages > that FTBFS to a reasonable number. Clearly it won't be viable to update Ruby 2.3 to OpenSSL 1.1, so I have uploaded a fixed package that builds against OpenSSL 1.0. Instead of closing this bug, I will leave it open so that when Ruby 2.4 comes we don't forget to make it build against OpenSSL 1.1. Let me know if that is confusing for you when keeping track of the transition; I can always close this one and do something else to record this need for Ruby 2.4. signature.asc Description: PGP signature
Processed: Re: Bug#828535: ruby2.3: FTBFS with openssl 1.1.0
Processing control commands: > severity -1 important Bug #828535 [src:ruby2.3] ruby2.3: FTBFS with openssl 1.1.0 Severity set to 'important' from 'serious' -- 828535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#836595: ruby-celluloid-io: FTBFS too much often (failing tests)
On Wed, Nov 09, 2016 at 09:06:26PM +0530, Pirate Praveen wrote: > Errno::EADDRINUSE: >Address already in use - bind(2) for "127.0.0.1" port 12345 Note: I'm not the only one to get those errors. You can find them in reproducible builds as well: https://tests.reproducible-builds.org/debian/logs/unstable/amd64/ruby-celluloid-io_0.16.2-2.build2.log.gz My only recommendation is that each and every test which is known not to work realiably is just disabled (in addition to forwarding the bug upstream). Thanks.
Processed: Re: Bug#802190: genparse: FTBFS: Tests fail with segmentation fault
Processing commands for cont...@bugs.debian.org: > tags 802190 + pending fixed-upstream Bug #802190 [src:genparse] genparse: FTBFS: Tests fail with segmentation fault Added tag(s) fixed-upstream and pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 802190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#802190: genparse: FTBFS: Tests fail with segmentation fault
tags 802190 + pending fixed-upstream thanks Fix in patch submitted to upstream: https://sourceforge.net/p/genparse/bugs/19/ Waiting for upstream to release a fixed version of the program.
Bug#836595: ruby-celluloid-io: FTBFS too much often (failing tests)
On Wed, Nov 09, 2016 at 10:41:13PM +0530, Pirate Praveen wrote: > On 2016, നവംബർ 9 10:22:53 PM IST, Santiago Vila wrote: > >I don't think so, because I always build a package at a time. > > Can you try to reproduce it in another setup? May be sbuild on local system. Just take a look at the build logs I attached to this bug report: It failed for me on five different autobuilders. I'm always using sbuild on a single CPU virtual machine. In such setup the probability of failure seems to be around 20%. Thanks.
Bug#843477: marked as done (src:kamailio: stop using libval-dev for DNSSEC validation)
Your message dated Wed, 09 Nov 2016 17:20:20 + with message-id and subject line Bug#843477: fixed in kamailio 4.4.4-1 has caused the Debian Bug report #843477, regarding src:kamailio: stop using libval-dev for DNSSEC validation 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.) -- 843477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:kamailio Version: 4.4.3-2 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, please stop using libdnsval-dev for DNSSEC validation. src:dnsval is very poorly upstream maintained (SVN repository, issue tracker, mailing list are non-functional) and I am going to schedule it for removal for stretch. In a long term you should migrated to better and maintained library (preferrably getdns or just libunbound), but now please just drop it. Cheers, Ondrej - -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-41-generic (SMP w/24 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQJ8BAEBCgBmBQJYH6ugXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHKTEP+gJ+XH9lI2j1G1YQlp479mrT QyD8IZKnJfqm/w08+q834MF/3jtBi+YR+7mElbMP4NpHELMgCxg5Pt9PqcO6D0dh IowNEegvaqVLfYPwMfhDbNGVgRN4QqPTVwZ4jwsWhcPDRdGMhsWxnhf9lAiwhkNX 4oom93kEpA/LrNoP+Be/5z1VL8m/NpFTE/ORXTQ6fmVSf+QgHS2rWLBrdvVeI5Sn rn34N+K8PQhhrruuoQyXyDInUKa1wQSWZ1zy6apPHkrGnD0f1YjR84k5MY+rg8St MYewM1rdEU6fMphQccCDuAtXJ7E58c4zFGeZlli6uTPXDrlOAIAThmEyGupn//2Q izuVK7Jhr6guSJpl8jWNOg2IsSriQSc0mMJyUf4O5a1ZTBg31IyhZDnLk44SdPhK /zIjPuTNMjlERmah9dQkx2J9ORe75hTT9L0QA3fRWHsHBoHnIP4aMuyjpqgJcREH HJ9bQwD7/B3bv8IKsSy7M9v0aKbBjA/P/+8OPIqqbWk3dOVFG0+PAVNvWQrVJ6Ge 7wl0zVYAD6YqiKZNFTRpf6NYJ7SN64lJhg8OvkXbl5Vyy6XLvY5aNhk/ukCW2ap3 r0UQcb3dEVx+5sncXtdB5FlYgNJ2rdAEtAAeDwHO1toPxWYqFiOAZbF0N0N/1WN9 t5LdwPupjo9F0UQQTKmU =GkaB -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: kamailio Source-Version: 4.4.4-1 We believe that the bug you reported is fixed in the latest version of kamailio, 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 843...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Victor Seva (supplier of updated kamailio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 09 Nov 2016 17:40:45 +0100 Source: kamailio Binary: kamailio kamailio-dbg kamailio-geoip-modules kamailio-sqlite-modules kamailio-json-modules kamailio-memcached-modules kamailio-lua-modules kamailio-mono-modules kamailio-python-modules kamailio-redis-modules kamailio-mysql-modules kamailio-postgres-modules kamailio-cpl-modules kamailio-radius-modules kamailio-unixodbc-modules kamailio-presence-modules kamailio-perl-modules kamailio-snmpstats-modules kamailio-purple-modules kamailio-xmpp-modules kamailio-xml-modules kamailio-carrierroute-modules kamailio-berkeley-modules kamailio-berkeley-bin kamailio-ldap-modules kamailio-ims-modules kamailio-utils-modules kamailio-sctp-modules kamailio-java-modules kamailio-tls-modules kamailio-outbound-modules kamailio-websocket-modules kamailio-autheph-modules kamailio-kazoo-modules kamailio-cnxcc-modules kamailio-erlang-modules kamailio-extra-modules Architecture: source amd64 Version: 4.4.4-1 Distribution: unstable Urgency: medium Maintainer: Debian VoIP Team Changed-By: Victor Seva Description: kamailio - very fast and configurable SIP proxy kamailio-autheph-modules - authentication using ephemeral credentials module for Kamailio kamailio-berkeley-bin - Berkeley database module for Kamailio - helper program kamailio-berkeley-modules - Berkeley database module for Kamailio kamailio-carrierroute-modules - carrierroute module for Kamailio kamailio-cnxcc-modules - cnxcc modules for Kamailio kamail
Bug#843631: Downstream incompatibilities due to SSL_ST_*
I had the same problem... waiting for a fix. Regards, -- Lucas Kanashiro signature.asc Description: PGP signature
Bug#836595: ruby-celluloid-io: FTBFS too much often (failing tests)
On 2016, നവംബർ 9 10:22:53 PM IST, Santiago Vila wrote: >I don't think so, because I always build a package at a time. Can you try to reproduce it in another setup? May be sbuild on local system.
Bug#843073: dpkg-shlibdeps: broken on i386 with merged /usr
Hi, On Sat, Nov 05, 2016 at 08:58:06PM +0100, Michael Biebl wrote: > As this breaks packages to build successfully, I'm bumping this to RC. > E.g. I'm unable to successfully build systemd in a freshly created > chroot on i386. I suspect once the buildds update their chroot, it will > affect a lot more packages. https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/systemd.html shows that we could build systemd on sid. The builds are being done in recently created pbuilder setups though. -- cheers, Holger signature.asc Description: Digital signature
Bug#843711: marked as done (biber: FTBFS (failing tests))
Your message dated Wed, 09 Nov 2016 17:03:34 + with message-id and subject line Bug#843711: fixed in biber 2.6-2 has caused the Debian Bug report #843711, regarding biber: 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.) -- 843711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:biber Version: 2.6-1 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed: [...] debian/rules build-indep dh build-indep --with tex dh_testdir -i dh_update_autotools_config -i dh_auto_configure -i perl -I. Build.PL --installdirs vendor --config "optimize=-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config "ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" Checking prerequisites... requires: ! Encode::EUCJPASCII is not installed ! Lingua::Translit is not installed ! Mozilla::CA is not installed ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install the versions [... snipped ...] Non-zero exit status: 24 t/dateformats.t (Wstat: 4096 Tests: 41 Failed: 16) Failed tests: 20-22, 24, 26, 28, 31, 33-41 Non-zero exit status: 16 t/encoding.t (Wstat: 2304 Tests: 10 Failed: 9) Failed tests: 1-8, 10 Non-zero exit status: 9 t/names.t(Wstat: 8192 Tests: 72 Failed: 32) Failed tests: 32-57, 59-60, 65-68 Non-zero exit status: 32 t/options.t (Wstat: 768 Tests: 9 Failed: 3) Failed tests: 7-9 Non-zero exit status: 3 t/related-entries.t (Wstat: 768 Tests: 13 Failed: 3) Failed tests: 1-2, 10 Non-zero exit status: 3 t/set-dynamic.t (Wstat: 1536 Tests: 7 Failed: 6) Failed tests: 2-7 Non-zero exit status: 6 t/set-legacy.t (Wstat: 256 Tests: 3 Failed: 1) Failed test: 1 Non-zero exit status: 1 t/set-static.t (Wstat: 768 Tests: 5 Failed: 3) Failed tests: 1-2, 5 Non-zero exit status: 3 t/skips.t(Wstat: 2048 Tests: 15 Failed: 8) Failed tests: 7, 9-15 Non-zero exit status: 8 t/sort-complex.t (Wstat: 1280 Tests: 9 Failed: 5) Failed tests: 2-6 Non-zero exit status: 5 t/sortlists.t(Wstat: 512 Tests: 15 Failed: 2) Failed tests: 13-14 Non-zero exit status: 2 t/xdata.t(Wstat: 512 Tests: 5 Failed: 2) Failed tests: 1-2 Non-zero exit status: 2 Files=42, Tests=1046, 40 wallclock secs ( 0.25 usr 0.08 sys + 36.73 cusr 2.18 csys = 39.24 CPU) Result: FAIL Failed 16/42 test programs. 130/1046 subtests failed. dh_auto_test: perl Build test --verbose 1 test_files=t/annotations.t t/basic-misc.t t/bcfvalidation.t t/biblatexml.t t/bibtex-aliases.t t/bibtex-output.t t/configfile.t t/crossrefs.t t/dateformats.t t/dm-constraints.t t/encoding.t t/extratitle.t t/extratitleyear.t t/extrayear.t t/full-bbl.t t/full-bblxml.t t/full-bibtex.t t/full-dot.t t/labelalpha.t t/labelname.t t/names.t t/names_x.t t/options.t t/related-entries.t t/sections-complex.t t/sections.t t/set-dynamic.t t/set-legacy.t t/set-static.t t/skips.t t/sort-case.t t/sort-complex.t t/sort-order.t t/sort-uc.t t/sorting.t t/sortlists.t t/tool-bltxml-inout.t t/tool-bltxml.t t/tool.t t/uniqueness.t t/utils.t t/xdata.t returned exit code 2 debian/rules:17: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' debian/rules:9: recipe for target 'build-indep' failed make: *** [build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2 The above is just the last part of the build log. For a full build log please see: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/biber_2.6-1.rbuild.log Note: Even if this package is Arch:all, please consider uploading in source-only form, so that we get official build logs available here: https://buildd.debian.org/status/package.php?p=biber Thanks. --- End Message --- --- Begin Message --- Source: biber Source-Version: 2.6-2 We believe that the bug you reported is fixed in the latest version of biber, which is due to be installed in the Debian FTP archive. A summary of the changes between this ve
Bug#836595: ruby-celluloid-io: FTBFS too much often (failing tests)
On Wed, Nov 09, 2016 at 09:06:26PM +0530, Pirate Praveen wrote: > On Sun, 4 Sep 2016 13:35:32 +0200 (CEST) Santiago Vila > wrote: > > All failures have this in common, are you sure other tests (from other > packages) are not using the same port at the same time? > > > Errno::EADDRINUSE: >Address already in use - bind(2) for "127.0.0.1" port 12345 I don't think so, because I always build a package at a time. Thanks.
Processed: your mail
Processing commands for cont...@bugs.debian.org: > affects 843614 torbrowser-launcher Bug #843614 [python-cryptography] AttributeError: 'module' object has no attribute 'SSL_ST_INIT' Ignoring request to set affects of bug 843614 to the same value previously set > End of message, stopping processing here. Please contact me if you need assistance. -- 843614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843774: pgadmin3: It crashes even when .pgadmin3 isn't present
Dear Landry and pgadmin3 Maintainers, Removing that file doesn't help. Pgadmin3 will crash after creating a new one. I find this package completely unusable. The following backtrace has been obtained after removing that file: gdb /usr/bin/pgadmin3 GNU gdb (Debian 7.11.1-2) 7.11.1 [...] Reading symbols from /usr/bin/pgadmin3...Reading symbols from /usr/lib/debug/.build-id/5f/5de51f2d0bf14d6b6f50a56a755a95b68b3512.debug...done. done. (gdb) run Starting program: /usr/bin/pgadmin3 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 17:03:41: Warning: Mismatch between the program and library build versions detected. The library used 3.0 (wchar_t,compiler with C++ ABI 1009,wx containers,compatible with 2.8), and your program used 3.0 (wchar_t,compiler with C++ ABI 1010,wx containers,compatible with 2.8). 17:03:41: Debug: Adding duplicate image handler for 'PNG file' [New Thread 0x7fffe6090700 (LWP 12420)] [New Thread 0x7fffe588f700 (LWP 12421)] Thread 1 "pgadmin3" received signal SIGSEGV, Segmentation fault. pgConn::GetStatus (this=0x0) at db/pgConn.cpp:1011 1011db/pgConn.cpp: No such file or directory. (gdb) bt #0 pgConn::GetStatus (this=0x0) at db/pgConn.cpp:1011 #1 0x55ac26e1 in pluginUtilityFactory::CheckEnable (this=0x56eb6530, obj=0x56fe8da0) at frm/plugins.cpp:383 #2 0x55db770a in menuFactoryList::CheckMenu (this=0x56e995f0, obj=obj@entry=0x56fe8da0, menubar=0x56f2c6b0, toolbar=0x56e99610) at utils/factory.cpp:266 #3 0x559d55ba in frmMain::setDisplay (this=this@entry=0x56e657c0, data=0x56fe8da0, props=props@entry=0x0, sqlbox=sqlbox@entry=0x0) at frm/events.cpp:600 #4 0x559d9202 in frmMain::execSelChange (this=this@entry=0x56e657c0, item=..., currentNode=) at frm/events.cpp:512 #5 0x559d9945 in frmMain::OnExpand (this=0x56e657c0, event=...) at frm/events.cpp:277 #6 0x7598659e in wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, wxEvent&) const () from /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0 #7 0x75b0ca87 in wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) () from /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0 #8 0x75b0cb7b in wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) () from /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0 #9 0x75b0cf2b in wxEvtHandler::TryHereOnly(wxEvent&) () from /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0 #10 0x75b0cd33 in wxEvtHandler::DoTryChain(wxEvent&) () from /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0 #11 0x75b0d015 in wxEvtHandler::ProcessEvent(wxEvent&) () from /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0 #12 0x766ac6c8 in wxWindowBase::TryAfter(wxEvent&) () from /lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0 #13 0x7671a05b in wxScrollHelperEvtHandler::ProcessEvent(wxEvent&) () from /lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0 #14 0x76731703 in wxGenericTreeCtrl::Expand(wxTreeItemId const&) () from /lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0 #15 0x76733710 in wxGenericTreeCtrl::OnMouse(wxMouseEvent&) () from /lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0 #16 0x7598659e in wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, wxEvent&) const () from /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0 #17 0x75b0ca87 in wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) () from /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0 #18 0x75b0cb7b in wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) () from /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0 #19 0x75b0cf2b in wxEvtHandler::TryHereOnly(wxEvent&) () from /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0 #20 0x75b0cfb3 in wxEvtHandler::ProcessEventLocally(wxEvent&) () from /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0 #21 0x75b0d015 in wxEvtHandler::ProcessEvent(wxEvent&) () from /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0 #22 0x7671a05b in wxScrollHelperEvtHandler::ProcessEvent(wxEvent&) () from /lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0 #23 0x75b0cd87 in wxEvtHandler::SafelyProcessEvent(wxEvent&) () from /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0 #24 0x764c5fb6 in ?? () from /lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0 #25 0x734fe84c in ?? () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #26 0x72ed4f75 in g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #27 0x72ee6f82 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #28 0x72eef66f in g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #29 0x72eeffaf in g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #30 0x7361698c in ?? () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #31 0x734fd014 in gtk_propagate_ev
Processed: pgadmin3: It crashes even when .pgadmin3 isn't present
Processing commands for cont...@bugs.debian.org: > severity 843774 grave Bug #843774 [pgadmin3] [pgadmin3] pgadmin segfault at startup with postresql-9.6 installed and a connexion configured in .pgadmin3 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 843774: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 841763 to apt
Processing commands for cont...@bugs.debian.org: > reassign 841763 apt 1.2.10 Bug #841763 [unattended-upgrades] unattended-upgrades: Breaks hard when apt is upgraded Bug reassigned from package 'unattended-upgrades' to 'apt'. No longer marked as found in versions unattended-upgrades/0.92 and unattended-upgrades/0.86.5+build1. Ignoring request to alter fixed versions of bug #841763 to the same values previously set Bug #841763 [apt] unattended-upgrades: Breaks hard when apt is upgraded Marked as found in versions apt/1.2.10. > thanks Stopping processing here. Please contact me if you need assistance. -- 841763: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#843727: desktop-base: experimental version does not install
On Wed, 2016-11-09 at 16:45 +0100, Eric Valette wrote: > On 11/09/2016 04:16 PM, Yves-Alexis Perez wrote: > > On Wed, 2016-11-09 at 15:52 +0100, Eric Valette wrote: > > Can you add set -x to the postinst file? > > I did a "sh -x ...dektop-base.postinst configure" and saw no error Can you retry with what I asked? Add set -x to the postinst file then re-run the install process (dpkg --configure -a for example). > > > What is you dpkg version? > > 1.18.13 THanks -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#843727: desktop-base: experimental version does not install
On 11/09/2016 04:16 PM, Yves-Alexis Perez wrote: On Wed, 2016-11-09 at 15:52 +0100, Eric Valette wrote: Can you add set -x to the postinst file? I did a "sh -x ...dektop-base.postinst configure" and saw no error What is you dpkg version? 1.18.13 -- eric