Bug#906356: marked as done (freefem: FTBFS in buster/sid (Cannot find "doc/freefem/*.gif"))
Your message dated Thu, 20 Sep 2018 00:34:15 + with message-id and subject line Bug#906356: fixed in freefem 3.5.8-7 has caused the Debian Bug report #906356, regarding freefem: FTBFS in buster/sid (Cannot find "doc/freefem/*.gif") 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.) -- 906356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:freefem Version: 3.5.8-6 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i debian/rules override_dh_autoreconf make[1]: Entering directory '/<>' libtoolize libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'admin'. libtoolize: linking file 'admin/ltmain.sh' libtoolize: You should add the contents of the following files to 'aclocal.m4': libtoolize: '/usr/share/aclocal/libtool.m4' libtoolize: '/usr/share/aclocal/ltoptions.m4' libtoolize: '/usr/share/aclocal/ltsugar.m4' libtoolize: '/usr/share/aclocal/ltversion.m4' libtoolize: '/usr/share/aclocal/lt~obsolete.m4' [... snipped ...] libtool: install: chmod 644 /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libfreefem.a libtool: install: ranlib /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libfreefem.a libtool: warning: remember to run 'libtool --finish /usr/lib/x86_64-linux-gnu' /bin/mkdir -p '/<>/debian/tmp/usr/include/fem' /usr/bin/install -c -m 644 femDisk.hpp femCommon.hpp femFunction.hpp femGibbs.hpp femGraphic.hpp femGraphicDeviceIndependent.hpp femIdentifier.hpp femLexical.hpp femMesh.hpp femMisc.hpp femSolver.hpp femSolver1.hpp femSolver1c.hpp femParser.hpp femTreeNode.hpp '/<>/debian/tmp/usr/include/fem' make[4]: Leaving directory '/<>/freefem/fem' make[3]: Leaving directory '/<>/freefem/fem' make[3]: Entering directory '/<>/freefem' make[4]: Entering directory '/<>/freefem' /bin/mkdir -p '/<>/debian/tmp/usr/bin' /bin/bash ../libtool --mode=install /usr/bin/install -c freefem '/<>/debian/tmp/usr/bin' libtool: warning: 'fem/libfreefem.la' has not been installed in '/usr/lib/x86_64-linux-gnu' libtool: install: /usr/bin/install -c .libs/freefem /<>/debian/tmp/usr/bin/freefem /bin/mkdir -p '/<>/debian/tmp/usr/share/man/man1' /usr/bin/install -c -m 644 freefem.1 '/<>/debian/tmp/usr/share/man/man1' make[4]: Leaving directory '/<>/freefem' make[3]: Leaving directory '/<>/freefem' make[2]: Leaving directory '/<>/freefem' Making install in freefem-api make[2]: Entering directory '/<>/freefem-api' make[3]: Entering directory '/<>/freefem-api' make[3]: Nothing to be done for 'install-exec-am'. make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/<>/freefem-api' make[2]: Leaving directory '/<>/freefem-api' Making install in examples make[2]: Entering directory '/<>/examples' make[3]: Entering directory '/<>/examples' make[3]: Nothing to be done for 'install-exec-am'. make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/<>/examples' make[2]: Leaving directory '/<>/examples' make[2]: Entering directory '/<>' make[3]: Entering directory '/<>' make[3]: Nothing to be done for 'install-exec-am'. /bin/mkdir -p '/<>/debian/tmp/usr/share/doc/freefem/' /usr/bin/install -c -m 644 ChangeLog README NEWS TODO '/<>/debian/tmp/usr/share/doc/freefem/' make[3]: Leaving directory '/<>' make[2]: Leaving directory '/<>' make[1]: Leaving directory '/<>' dh_install -i dh_install: Cannot find (any matches for) "doc/freefem/*.gif" (tried in ., debian/tmp) dh_install: freefem-doc missing files: doc/freefem/*.gif dh_install: missing files, aborting make: *** [debian/rules:6: binary-indep] Error 25 dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess returned exit status 2 The build was made with "dpkg-buildpackage -A" in my autobuilder. Most probably, it also fails here in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/freefem.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: freefem Source-Version: 3.5.8-7 We believe that the bug you reported is fixed in the latest version of freefem, which is due to be
Bug#883778: problems building guile-2.0 on armel
Control: affects -1 guile-2.2 Does this issue still affect guile-2.2? https://buildd.debian.org/status/package.php?p=guile-2.2 Because guile-2.2 was never built on armel but guile-2.0 was, this is blocking aisleriot and other packages from migrating to Testing. Thanks, Jeremy Bicha
Processed: Re: Bug#883778: problems building guile-2.0 on armel
Processing control commands: > affects -1 guile-2.2 Bug #883778 [guile-2.0] problems building guile-2.0 on armel Added indication that 883778 affects guile-2.2 -- 883778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#909094: gnome-shell-extension-workspaces-to-dock: Version 48 with gnome-shell 3.28 makes the Desktop unusable
Processing control commands: > severity -1 important Bug #909094 [gnome-shell-extension-workspaces-to-dock] gnome-shell-extension-workspaces-to-dock: Version 48 with gnome-shell 3.28 makes the Desktop unusable Severity set to 'important' from 'serious' -- 909094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909094: gnome-shell-extension-workspaces-to-dock: Version 48 with gnome-shell 3.28 makes the Desktop unusable
Control: severity -1 important On Wed, Sep 19, 2018 at 2:37 AM Sophie Brun wrote: > > The way forward for Kali might be to just push glib2.0, gnome-shell, > > mutter, and gnome-shell-extensions to Testing early. > > I fixed the issue for Kali by forking the package and reverting last > changes. > > > As long as we can get glib to build on armel, all these should land in > > Testing in a couple days. > > Yes I noticed that but I thought I had to report anyway this (very > annoying) bug. > I hope Gnome Shell will migrate quickly. GNOME Shell is migrating to Testing now so I'm lowering the severity of this bug. Jonathan, could you look at bumping the dependency as requested? It looks like you didn't push your latest changes so it might be easier for you to take care of this bug. https://bugs.debian.org/909094 Thanks, Jeremy Bicha
Bug#908553: more info
Hi. I cannot reproduce this. I talked to upstream. He can't reproduce it either, but he thinks this is related to the locale somehow. Can you try to run LANG=C pcb-rnd If you do that, does it still crash? Are you doing anything special with locales that would help us reproduce? Thanks.
Bug#909173: marked as done (libepoxy-dev: New pkg-config dependencies that are not package dependencies)
Your message dated Wed, 19 Sep 2018 22:04:16 + with message-id and subject line Bug#909173: fixed in libepoxy 1.5.2-0.2 has caused the Debian Bug report #909173, regarding libepoxy-dev: New pkg-config dependencies that are not package dependencies 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.) -- 909173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libepoxy-dev Version: 1.5.2-0.1 Severity: serious Control: affects -1 src:goffice https://buildd.debian.org/status/package.php?p=goffice ... checking for GTK... no configure: error: Package requirements ( gtk+-3.0>= 3.8.7 ) were not met: Package 'gl', required by 'epoxy', not found --- End Message --- --- Begin Message --- Source: libepoxy Source-Version: 1.5.2-0.2 We believe that the bug you reported is fixed in the latest version of libepoxy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 909...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated libepoxy 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, 19 Sep 2018 10:39:51 +0100 Source: libepoxy Binary: libepoxy-dev libepoxy0 libepoxy0-udeb Architecture: source Version: 1.5.2-0.2 Distribution: unstable Urgency: medium Maintainer: Jérémy Lal Changed-By: Simon McVittie Description: libepoxy-dev - OpenGL function pointer management library- development libepoxy0 - OpenGL function pointer management library libepoxy0-udeb - OpenGL function pointer management library - minimal runtime (udeb) Closes: 909173 Changes: libepoxy (1.5.2-0.2) unstable; urgency=medium . * Non-maintainer upload * libepoxy-dev Depends on libgl1-mesa-dev and libegl1-mesa-dev. Those packages provide gl.pc and egl.pc, which are depended on by epoxy.pc since 1.5.2 (Closes: #909173) * Work around #874077 by creating an Xvfb screen where GLX can work Checksums-Sha1: e156ce8ac8f84d8b47edfe0f3f3e007f415bfc89 2098 libepoxy_1.5.2-0.2.dsc f8a7f6dfcb655b831dc6555e7e70830835b42b7c 17308 libepoxy_1.5.2-0.2.debian.tar.xz 7f21e82a10011fd949dc34321dd6623caf978ddb 8862 libepoxy_1.5.2-0.2_source.buildinfo Checksums-Sha256: 1c64bbebd936752c1cd5e050b5f95e4d766fd874dd724773d51f0f83df896776 2098 libepoxy_1.5.2-0.2.dsc 8dcde324a0d76953291aeefefd1cb6eec00d4836b61b44077492980ee6373faa 17308 libepoxy_1.5.2-0.2.debian.tar.xz 2f928812012377527a09339fff1bf28faf771b688764c8819d74fbd26a46ac05 8862 libepoxy_1.5.2-0.2_source.buildinfo Files: 533ddc3e102091018d72b5f6b94a87a1 2098 libs optional libepoxy_1.5.2-0.2.dsc afaf9b52ea0bdcd7721c653939508224 17308 libs optional libepoxy_1.5.2-0.2.debian.tar.xz 9f2ea1d95ee11e131fb526dcecf42997 8862 libs optional libepoxy_1.5.2-0.2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAluiH/wACgkQ4FrhR4+B TE/jfA/+LzLr0kI2p4LVw7ga2Zzae5+BEtF5MAOlyg72UMFx7j372eivcWa7o7MM X7Gz8N9kOgOzrlScdmlBmPWob5K0m076ss9BRXmGPGP1CewxGJHRlt9oiojZ01cs bYte81XOC39OWKi0lfY5xNyJNMTtCaa84hn32SmW/dXms9Eu67IkeKzAjZluDRdc SJQfzBybpYMGY+bO9VP5aJAmn/DVPzAWBNU5sj6DGAFo8z4MbeTv0pDxnkabx8Ts GwI+buVKV7Rnlr5eU+xJH4hK3ZqosxHC/D/UpIkcCFpf5bCVdDoXdSW/4vlH1RFC sm6iUUoDzaHDuat2uqvdWtyOyvZXj1ZOYb25Hv2ZaNw1cpdHwOjFrSqMqbDM3hUc D00Q5K/hK22121yl3+lH9Wp2MIdg6sRqSzZ0Bmy3PPTHwmvhKM47Ogrz4nPrR3t3 ftft0rc1pWeyJz5P4gs0w3FiZ2eFz8i4Izk1VfPc+RSJsnh+Hp+AkKoqJUK9ps89 NaUgpkAsi4kft1XRZXDIyfVl9cX/e4H0CE7Z445eFDOM2BxOaLaH46nQ6JKY5fqm 74INNMZxupPkIDhavqaDNChdi0widVtRwb4VNTr3tS8agBr5LzZdp00hqpVU5OIZ DbnEUeatfLiE8KKzIS9Gz3UDQP6tsuGDj1f5MyfU2iu8lWioouo= =WKee -END PGP SIGNATURE End Message ---
Bug#906389: marked as done (node-mime-types: FTBFS in buster/sid (cp: cannot stat '/usr/share/node-mime/types.json': No such file or directory))
Your message dated Wed, 19 Sep 2018 17:46:34 -0400 with message-id and subject line Re:node-mime-types: FTBFS in buster/sid (cp: cannot stat '/usr/share/node-mime/types.json': No such file or directory) has caused the Debian Bug report #906389, regarding node-mime-types: FTBFS in buster/sid (cp: cannot stat '/usr/share/node-mime/types.json': No such file or directory) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 906389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906389 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:node-mime-types Version: 2.1.17-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i debian/rules override_dh_auto_build make[1]: Entering directory '/<>' cd node_modules/mime-db/ && nodejs scripts/extensions # just copy the file from node-mime cp /usr/share/node-mime/types.json node_modules/mime-db/src/deb.types.json cp: cannot stat '/usr/share/node-mime/types.json': No such file or directory make[1]: *** [debian/rules:21: override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:8: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The build was made with "dpkg-buildpackage -A" in my autobuilder. Most probably, it also fails here in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-mime-types.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Version: 2.1.20-1 The new version uploaded today builds fine. Thanks, Jeremy Bicha--- End Message ---
Bug#896660: marked as done (vagrant: Vagrant should depend on rsync)
Your message dated Wed, 19 Sep 2018 21:21:23 + with message-id and subject line Bug#896660: fixed in vagrant 2.1.2+dfsg-2 has caused the Debian Bug report #896660, regarding vagrant: Vagrant should depend on rsync 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.) -- 896660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vagrant Version: 2.0.2+dfsg-3 Severity: important Hi, On a somewhat-fresh buster install, I ran into the following issue immediately after installing vagrant: > $ vagrant up > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Box 'debian/stretch64' could not be found. Attempting to find > and install... > default: Box Provider: virtualbox > default: Box Version: >= 0 > ==> default: Loading metadata for box 'debian/stretch64' > default: URL: https://vagrantcloud.com/debian/stretch64 > ==> default: Adding box 'debian/stretch64' (v9.4.0) for provider: virtualbox > default: Downloading: > https://vagrantcloud.com/debian/boxes/stretch64/versions/9.4.0/providers/virtualbox.box > ==> default: Successfully added box 'debian/stretch64' (v9.4.0) for > 'virtualbox'! > ==> default: Importing base box 'debian/stretch64'... > ==> default: Matching MAC address for NAT networking... > ==> default: Checking if box 'debian/stretch64' is up to date... > ==> default: Setting the name of the VM: > ansible-bad_default_1524480379880_70283 > # run> terminated with exception (report_on_exception is true): > Traceback (most recent call last): > 106: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/batch_action.rb:82:in > `block (2 levels) in run' > 105: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:188:in > `action' > 104: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:188:in > `call' > 103: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/environment.rb:592:in > `lock' > 102: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:202:in > `block in action' > 101: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:227:in > `action_raw' > 100: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in > `run' >99: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/busy.rb:19:in > `busy' >98: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in > `block in run' >97: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builder.rb:116:in > `call' >96: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in > `call' >95: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in > `call' >94: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in > `call' >93: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/call.rb:53:in > `call' >92: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in > `run' >91: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/busy.rb:19:in > `busy' >90: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in > `block in run' >89: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builder.rb:116:in > `call' >88: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in > `call' >87: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:95:in > `block in finalize_action' >86: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in > `call' >85: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/handle_box.rb:56:in > `call' >84: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in > `call' >83: from > /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:95:in > `block
Bug#896660: Bug #896660 in vagrant marked as pending
Control: tag -1 pending Hello, Bug #896660 in vagrant reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/vagrant/commit/977a36c78675bb676b44da33e4360323051c6767 Add missing dependency on rsync Closes: #896660 (this message was generated automatically) -- Greetings https://bugs.debian.org/896660
Processed: Bug #896660 in vagrant marked as pending
Processing control commands: > tag -1 pending Bug #896660 [vagrant] vagrant: Vagrant should depend on rsync Added tag(s) pending. -- 896660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#896660: Bug #896660 in vagrant marked as pending
Control: tag -1 pending Hello, Bug #896660 in vagrant reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/vagrant/commit/cbba215ca3e366c921456e2a54763b07dc95008b Add missing dependency on rsync Closes: #896660 (this message was generated automatically) -- Greetings https://bugs.debian.org/896660
Processed: Bug #896660 in vagrant marked as pending
Processing control commands: > tag -1 pending Bug #896660 [vagrant] vagrant: Vagrant should depend on rsync Ignoring request to alter tags of bug #896660 to the same tags previously set -- 896660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909219: FTBFS in pbuilder, missed dependency
Package: gimagereader Version: 3.2.3-3.3 Severity: serious Dear maintainer, had to rebuild gimagereader because of the current libsane mess, result: -- Checking for module 'gtkmm-3.0' -- Package 'gl', required by 'epoxy', not found CMake Error at /usr/share/cmake-3.12/Modules/FindPkgConfig.cmake:436 (message): A required package was not found Call Stack (most recent call first): /usr/share/cmake-3.12/Modules/FindPkgConfig.cmake:602 (_pkg_check_modules_internal) CMakeLists.txt:71 (PKG_CHECK_MODULES) Adding libgl1-mesa-dev solve that diff --git a/debian/control b/debian/control index 603c9eb..3ef3dbb 100644 --- a/debian/control +++ b/debian/control @@ -7,6 +7,7 @@ Build-Depends: debhelper (>= 10), intltool (>= 0.35.0), libcairomm-1.0-dev, + libgl1-mesa-dev, libgtkmm-3.0-dev, libgtksourceviewmm-3.0-dev, libgtkspellmm-3.0-dev (>= 3.0.4), The build now: -- Checking for module 'gtkmm-3.0' -- Found gtkmm-3.0, version 3.22.2 -- Checking for module 'gtksourceviewmm-3.0' Cheers Alf -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-rc3-siduction-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gimagereader depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.0-1 ii libatkmm-1.6-1v5 2.24.2-3 ii libc62.27-6 ii libcairomm-1.0-1v5 1.12.2-3 ii libfontconfig1 2.13.0-5 ii libgcc1 1:8.2.0-7 ii libglib2.0-0 2.58.0-4 ii libglibmm-2.4-1v52.56.0-2 ii libgomp1 8.2.0-7 ii libgtk-3-0 3.24.0-3 ii libgtkmm-3.0-1v5 3.22.2-2 ii libgtksourceviewmm-3.0-0v5 3.18.0-3 ii libgtkspellmm-3.0-0v53.0.5+dfsg-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libjson-glib-1.0-0 1.4.2-4 ii libpangomm-1.4-1v5 2.40.1-4 ii libpodofo0.9.5 0.9.5-11 ii libpoppler-glib8 0.63.0-2 ii libsane 1.0.27-2~2 ii libsigc++-2.0-0v52.10.0-2.1 ii libstdc++6 8.2.0-7 ii libtesseract44.00~git2904-07acc2b2-1 ii libxml++2.6-2v5 2.40.1-2 gimagereader recommends no packages. gimagereader suggests no packages. -- no debconf information
Processed: tagging 909215
Processing commands for cont...@bugs.debian.org: > tags 909215 + upstream Bug #909215 [glusterfs] glusterfs: Multiple security issues Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 909215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909216: libjaxen-java FTBFS: java.lang.IllegalArgumentException: Illegal character in local name: 'pre:foo'
Source: libjaxen-java Version: 1.1.6-3 Severity: serious Tags: ftbfs Some recent change in unstable makes libjaxen-java FTBFS: https://tests.reproducible-builds.org/debian/history/libjaxen-java.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libjaxen-java.html ... [ERROR] Tests run: 7, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.03 s <<< FAILURE! - in org.jaxen.test.DOM4JXPathTest [ERROR] testJaxen20AttributeNamespaceNodes(org.jaxen.test.DOM4JXPathTest) Time elapsed: 0.002 s <<< ERROR! java.lang.IllegalArgumentException: Illegal character in local name: 'pre:foo'. at org.dom4j.QName.validateNCName(QName.java:346) at org.dom4j.QName.(QName.java:153) at org.dom4j.tree.QNameCache.createQName(QNameCache.java:245) at org.dom4j.tree.QNameCache.get(QNameCache.java:115) at org.dom4j.DocumentFactory.createQName(DocumentFactory.java:191) at org.dom4j.tree.FlyweightAttribute.(FlyweightAttribute.java:69) at org.dom4j.tree.DefaultAttribute.(DefaultAttribute.java:65) at org.jaxen.test.DOM4JXPathTest.testJaxen20AttributeNamespaceNodes(DOM4JXPathTest.java:130) [ERROR] testNamespaceNodesAreInherited(org.jaxen.test.DOM4JXPathTest) Time elapsed: 0.001 s <<< ERROR! java.lang.IllegalArgumentException: Illegal character in local name: 'pre:foo'. at org.dom4j.QName.validateNCName(QName.java:346) at org.dom4j.QName.(QName.java:153) at org.dom4j.tree.QNameCache.createQName(QNameCache.java:245) at org.dom4j.tree.QNameCache.get(QNameCache.java:115) at org.dom4j.DocumentFactory.createQName(DocumentFactory.java:191) at org.dom4j.tree.FlyweightAttribute.(FlyweightAttribute.java:69) at org.dom4j.tree.DefaultAttribute.(DefaultAttribute.java:65) at org.jaxen.test.DOM4JXPathTest.testNamespaceNodesAreInherited(DOM4JXPathTest.java:159) [INFO] Running org.jaxen.test.DefaultNamestepTest [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.jaxen.test.DefaultNamestepTest [INFO] Running org.jaxen.test.NameTest [INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.025 s - in org.jaxen.test.NameTest [INFO] Running org.jaxen.test.FunctionCallExceptionTest [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.jaxen.test.FunctionCallExceptionTest [INFO] Running org.jaxen.test.CountTest [INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.034 s - in org.jaxen.test.CountTest [INFO] Running org.jaxen.test.RoundTest [INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 s - in org.jaxen.test.RoundTest [INFO] Running org.jaxen.test.AxisTest [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s - in org.jaxen.test.AxisTest [INFO] Running org.jaxen.test.PriorityTest [INFO] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s - in org.jaxen.test.PriorityTest [INFO] [INFO] Results: [INFO] [ERROR] Errors: [ERROR] org.jaxen.test.DOM4JXPathTest#testJaxen20AttributeNamespaceNodes IllegalArgumentException [ERROR] org.jaxen.test.DOM4JXPathTest#testNamespaceNodesAreInherited IllegalArgumentException [INFO] [ERROR] Tests run: 716, Failures: 0, Errors: 2, Skipped: 0 [INFO] [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 24.739 s [INFO] Finished at: 2019-10-22T13:34:45-12:00 [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.21.0:test (default-test) on project jaxen: There are test failures. [ERROR] [ERROR] Please refer to /build/1st/libjaxen-java-1.1.6/target/surefire-reports for the individual test results. [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream. [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/build/1st/libjaxen-java-1.1.6 -Dclassworlds.conf=/etc/maven/m2-debian.conf org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/libjaxen-java-1.1.6/debian -Dmaven.repo.local=/build/1st/libjaxen-java-1.1.6/debian/maven-repo --batch-mode test returned exit code 1 make: *** [debian/rules:4: build] Error 2
Bug#909215: glusterfs: Multiple security issues
Package: glusterfs X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for glusterfs. CVE-2018-10904[0]: | It was found that glusterfs server does not properly sanitize file | paths in the "trusted.io-stats-dump" extended attribute which is used | by the "debug/io-stats" translator. Attacker can use this flaw to | create files and execute arbitrary code. To exploit this attacker | would require sufficient access to modify the extended attributes of | files on a gluster volume. CVE-2018-10907[1]: | It was found that glusterfs server is vulnerable to multiple stack | based buffer overflows due to functions in server-rpc-fopc.c | allocating fixed size buffers using 'alloca(3)'. An authenticated | attacker could exploit this by mounting a gluster volume and sending a | string longer that the fixed buffer size to cause crash or potential | code execution. CVE-2018-10911[2]: | A flaw was found in the way dic_unserialize function of glusterfs does | not handle negative key length values. An attacker could use this flaw | to read memory from other locations into the stored dict value. CVE-2018-10913[3]: | An information disclosure vulnerability was discovered in glusterfs | server. An attacker could issue a xattr request via glusterfs FUSE to | determine the existence of any file. CVE-2018-10914[4]: | It was found that an attacker could issue a xattr request via | glusterfs FUSE to cause gluster brick process to crash which will | result in a remote denial of service. If gluster multiplexing is | enabled this will result in a crash of multiple bricks and gluster | volumes. CVE-2018-10923[5]: | It was found that the "mknod" call derived from mknod(2) can create | files pointing to devices on a glusterfs server node. An authenticated | attacker could use this to create an arbitrary device and read data | from any device attached to the glusterfs server node. CVE-2018-10926[6]: | A flaw was found in RPC request using gfs3_mknod_req supported by | glusterfs server. An authenticated attacker could use this flaw to | write files to an arbitrary location via path traversal and execute | arbitrary code on a glusterfs server node. CVE-2018-10927[7]: | A flaw was found in RPC request using gfs3_lookup_req in glusterfs | server. An authenticated attacker could use this flaw to leak | information and execute remote denial of service by crashing gluster | brick process. CVE-2018-10928[8]: | A flaw was found in RPC request using gfs3_symlink_req in glusterfs | server which allows symlink destinations to point to file paths | outside of the gluster volume. An authenticated attacker could use | this flaw to create arbitrary symlinks pointing anywhere on the server | and execute arbitrary code on glusterfs server nodes. CVE-2018-10929[9]: | A flaw was found in RPC request using gfs2_create_req in glusterfs | server. An authenticated attacker could use this flaw to create | arbitrary files and execute arbitrary code on glusterfs server nodes. CVE-2018-10930[10]: | A flaw was found in RPC request using gfs3_rename_req in glusterfs | server. An authenticated attacker could use this flaw to write to a | destination outside the gluster volume. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-10904 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10904 [1] https://security-tracker.debian.org/tracker/CVE-2018-10907 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10907 [2] https://security-tracker.debian.org/tracker/CVE-2018-10911 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10911 [3] https://security-tracker.debian.org/tracker/CVE-2018-10913 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10913 [4] https://security-tracker.debian.org/tracker/CVE-2018-10914 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10914 [5] https://security-tracker.debian.org/tracker/CVE-2018-10923 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10923 [6] https://security-tracker.debian.org/tracker/CVE-2018-10926 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10926 [7] https://security-tracker.debian.org/tracker/CVE-2018-10927 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10927 [8] https://security-tracker.debian.org/tracker/CVE-2018-10928 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10928 [9] https://security-tracker.debian.org/tracker/CVE-2018-10929 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10929 [10] https://security-tracker.debian.org/tracker/CVE-2018-10930 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10930 Please adjust the affected versions in the BTS as needed. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#909214: mailman-hyperkitty FTBFS: FAIL: test_archive_message_unserializable (mailman_hyperkitty.tests.test_archiver.ArchiverTestCase)
Source: mailman-hyperkitty
Version: 1.1.0-8
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mailman-hyperkitty.html
...
FAIL: test_archive_message_unserializable
(mailman_hyperkitty.tests.test_archiver.ArchiverTestCase)
--
Traceback (most recent call last):
File
"/build/1st/mailman-hyperkitty-1.1.0/mailman_hyperkitty/tests/test_archiver.py",
line 357, in test_archive_message_unserializable
self.assertEqual(logger.error.call_count, 1)
AssertionError: 2 != 1
--
Ran 14 tests in 0.982s
FAILED (failures=1)
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1:
python3.7 setup.py test
dh_auto_test: pybuild --test -i python{version} -p "3.7 3.6" returned exit code
13
make: *** [debian/rules:6: build] Error 25
Bug#908824: marked as done (libnet-server-mail-perl FTBFS: t/starttls.t failure)
Your message dated Wed, 19 Sep 2018 19:34:08 + with message-id and subject line Bug#908824: fixed in libnet-server-mail-perl 0.25-4 has caused the Debian Bug report #908824, regarding libnet-server-mail-perl FTBFS: t/starttls.t failure 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.) -- 908824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libnet-server-mail-perl Version: 0.25-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=libnet-server-mail-perl=all=0.25-1=1536904015=0 ... Test Summary Report --- t/starttls.t (Wstat: 9 Tests: 3 Failed: 0) Non-zero wait status: 9 Parse errors: No plan found in TAP output Files=4, Tests=33, 2 wallclock secs ( 0.05 usr 0.04 sys + 0.67 cusr 0.20 csys = 0.96 CPU) Result: FAIL Failed 1/4 test programs. 0/33 subtests failed. make[1]: *** [Makefile:861: test_dynamic] Error 255 --- End Message --- --- Begin Message --- Source: libnet-server-mail-perl Source-Version: 0.25-4 We believe that the bug you reported is fixed in the latest version of libnet-server-mail-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 908...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Damyan Ivanov (supplier of updated libnet-server-mail-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: SHA256 Format: 1.8 Date: Wed, 19 Sep 2018 19:26:04 + Source: libnet-server-mail-perl Binary: libnet-server-mail-perl Architecture: source Version: 0.25-4 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: Damyan Ivanov Closes: 908824 Description: libnet-server-mail-perl - versatile and extensible mail server framework Changes: libnet-server-mail-perl (0.25-4) unstable; urgency=medium . * Team upload . * drop fix-autopkgtest.patch * patch test certificate to use 4096-bit RSA key Fixes tests with openssl 1.1.1 and Closes: #908824 Checksums-Sha1: 364da40c934d83567b070f964209c4057edc2ea6 2246 libnet-server-mail-perl_0.25-4.dsc 30669074f05af6db50a074655c889b8f674f4297 12028 libnet-server-mail-perl_0.25-4.debian.tar.xz Checksums-Sha256: 13f792aa2d2f3010040753ecb4eb08ea49bad0a6573680351590fbd7563e5d37 2246 libnet-server-mail-perl_0.25-4.dsc 31364653b28c12ca039a11f63a007de9cba3d7491fdf0b1902c1d4b6242a1bc3 12028 libnet-server-mail-perl_0.25-4.debian.tar.xz Files: 49e44189a5911493f53af9c34a5abb75 2246 perl optional libnet-server-mail-perl_0.25-4.dsc 92be6dc3c460f1c3fd3525cb5f6f9ee5 12028 perl optional libnet-server-mail-perl_0.25-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErqDETssFbpNjDZ0z276dTZnSoAQFAluioygACgkQ276dTZnS oASSxg//TsMujRRgAYf7vWQJqHsSB194/NfokIj92YX+xL9r+KanMwvSia4/XpMd GSkWnzM7OVm0qtRbcJqVvXFWlepG8YkRbSnNTzdXc0VvQ5Fe3W4GdWibxiDIkJMw NONHoVyvpP5TEtVm+2lcOipasMkwT1iNSQvCoJJxkB8dqEnfOd7N3P4CLVf9B/0d Cg6FiYAiPxGovbnKT17FYSmfjdVqVM+rmiVAdYvSJPYsWpBXBaRw/8NmR4AB4od4 GbU9ezaOGUdverfimR2POKXhlRkDZ7evYo255irZf95Ue2aXXWi+h3hvX16xUJj2 Qsw6lWJMWC+UOsJ/02BiicusaGX4QMDeNiC3NPXMN6sy+7CAd86+vrViur79Q8Ez ecMNyGb/wNwmY9Y5nzOUuTvliwM9bXmq81SD/hhIFMYRv3SNnLAq440gLGLUi+Au wwS/mLX02b6YKZhQHIIi0ARDLDTQ2MB6xruBuwLyJHQcbJXde8F+jJ1gzomdLWEu CwwW5S2qwBirifXTdqjeuYfQv8Yoilhsr1ZlqwZfHeOr70SuVrfJW726CQF3ZVBH g22FXY0cvGp5/4UveF1s6EO1Emlld4ttgZd+5Tm2uVPnK3wRBfmD4fLHbdQ0AIkY YnsTGGy9RLvoNbdX1UuncV2cI5D2OFEY9RuWiFQPrYCGUgG0ypw= =MeGn -END PGP SIGNATURE End Message ---
Bug#896990: (no subject)
On Wed, Sep 19, 2018 at 08:28:29AM -0400, Tiago Bortoletto Vaz wrote: > Please note that flickrbackup is marked for removal already (#904925). How broken is the package? Can it still do anything useful? I am asking since it might make sense to also request removal from stable if it is now completely useless. > Bests, 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
Bug#908824: Bug #908824 in libnet-server-mail-perl marked as pending
Control: tag -1 pending Hello, Bug #908824 in libnet-server-mail-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libnet-server-mail-perl/commit/de7a5559c393f4df0db31990161ea8ffa8094f11 patch test certificate to use 4096-bit RSA key Fixes tests with openssl 1.1.1 and Closes: #908824 (this message was generated automatically) -- Greetings https://bugs.debian.org/908824
Processed: Bug #908824 in libnet-server-mail-perl marked as pending
Processing control commands: > tag -1 pending Bug #908824 [src:libnet-server-mail-perl] libnet-server-mail-perl FTBFS: t/starttls.t failure Added tag(s) pending. -- 908824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: gimp-help: diff for NMU version 2.8.2-0.2
Processing control commands: > tags 906358 + pending Bug #906358 [src:gimp-help] gimp-help: FTBFS in buster/sid (You must have automake 1.10 or newer installed) Added tag(s) pending. -- 906358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906358: gimp-help: diff for NMU version 2.8.2-0.2
Control: tags 906358 + pending Dear maintainer, I've prepared an NMU for gimp-help (versioned as 2.8.2-0.2) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. 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 diff -Nru gimp-help-2.8.2/debian/changelog gimp-help-2.8.2/debian/changelog --- gimp-help-2.8.2/debian/changelog 2015-09-01 01:30:38.0 +0300 +++ gimp-help-2.8.2/debian/changelog 2018-09-19 21:21:52.0 +0300 @@ -1,3 +1,11 @@ +gimp-help (2.8.2-0.2) unstable; urgency=medium + + * Non-maintainer upload. + * Add upstream fix for FTBFS with automake 1.16, +thanks to Juhani Numminen. (Closes: #906358) + + -- Adrian Bunk Wed, 19 Sep 2018 21:21:52 +0300 + gimp-help (2.8.2-0.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru gimp-help-2.8.2/debian/patches/autogen-automake-1.16.patch gimp-help-2.8.2/debian/patches/autogen-automake-1.16.patch --- gimp-help-2.8.2/debian/patches/autogen-automake-1.16.patch 1970-01-01 02:00:00.0 +0200 +++ gimp-help-2.8.2/debian/patches/autogen-automake-1.16.patch 2018-09-19 21:21:52.0 +0300 @@ -0,0 +1,17 @@ +Description: autogen.sh - allow automake-1.16. +Origin: https://gitlab.gnome.org/GNOME/gimp-help/commit/6b6238801f86136f711b15c867b80fbcef8b7b01 +Bug: https://bugzilla.gnome.org/794819 +Bug-Debian: https://bugs.debian.org/906358 +Last-Update: 2018-08-31 + +--- a/autogen.sh b/autogen.sh +@@ -21,7 +21,7 @@ + + echo -n "Looking for latest automake version ... " + required_automake_minor=10 +-minor=15 ++minor=16 + while [ $minor -ge $required_automake_minor ]; do + ver=1.$minor + if (automake-$ver --version) < /dev/null > /dev/null 2>&1; then
Bug#908824: libnet-server-mail-perl FTBFS: t/starttls.t failure
-=| Damyan Ivanov, 19.09.2018 04:55:54 + |=-
> -=| Xavier, 18.09.2018 22:58:48 +0200 |=-
> > [1]
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libnet-server-mail-perl.html)
> > [2]
> > https://buildd.debian.org/status/package.php?p=libnet-server-mail-perl
>
> The buildd used libio-socket-ssl-perl 2.059-1, which misses a lot of
> openssl 1.1.1 fixes.
>
> Perhaps bumping the (build) dependency to version 2.060-3 would help?
>
> Hmm, the reproducible-builds log also shows 2.059-1, but I guess
> bumping the version is still worth a try -- may be the failure is
> hard to trigger.
That didn't work, and now I am able to make the test fail with
a slightly different error:
t/starttls.t ..
ok 1 - Accepted client for Test01: STARTTLS support
ok 2 - Accepted client for Test02: STARTTLS invalid parameters
ok 3 - Accepted client for Test03: STARTTLS handshake
# Error: TLS handshake failed SSL connect attempt failed error:1408F10B:SSL
routines:ssl3_get_record:wrong version number at t/starttls.t line 117.
# kill 9, 24096 (server)
All 3 subtests passed
Test Summary Report
---
t/starttls.t (Wstat: 9 Tests: 3 Failed: 0)
Non-zero wait status: 9
Parse errors: No plan found in TAP output
Looking at the test certificate, it has a 1024-bit key, which may be
the root reason, although the error message above doesn't confirm
that.
... and a minute later the test succeeds, after replacing
t/certs/server-{cert,key}.pem with a senf-signed 4096-bit certificate
Will prepare a proper patch, forward it upstream and upload.
-- dam
Bug#909126: marked as done (ompl-plannerarena: missing Breaks+Replaces: ompl-demos (<< 1.4))
Your message dated Wed, 19 Sep 2018 19:04:13 + with message-id and subject line Bug#909126: fixed in ompl 1.4.0+ds1-2 has caused the Debian Bug report #909126, regarding ompl-plannerarena: missing Breaks+Replaces: ompl-demos (<< 1.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.) -- 909126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ompl-plannerarena Version: 1.4.0+ds1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../ompl-plannerarena_1.4.0+ds1-1_all.deb ... Unpacking ompl-plannerarena (1.4.0+ds1-1) ... dpkg: error processing archive /var/cache/apt/archives/ompl-plannerarena_1.4.0+ds1-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/plannerarena.1.gz', which is also in package ompl-demos 1.2.1+ds1-1 Errors were encountered while processing: /var/cache/apt/archives/ompl-plannerarena_1.4.0+ds1-1_all.deb cheers, Andreas ompl-demos=1.2.1+ds1-1_ompl-plannerarena=1.4.0+ds1-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: ompl Source-Version: 1.4.0+ds1-2 We believe that the bug you reported is fixed in the latest version of ompl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 909...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Leopold Palomo-Avellaneda (supplier of updated ompl 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, 19 Sep 2018 17:49:27 +0200 Source: ompl Binary: libompl-dev libompl15 ompl-demos ompl-plannerarena Architecture: source Version: 1.4.0+ds1-2 Distribution: experimental Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Leopold Palomo-Avellaneda Description: libompl-dev - Open Motion Planning Library (OMPL) development files libompl15 - Open Motion Planning Library (OMPL) ompl-demos - Open Motion Planning Library (OMPL) demos ompl-plannerarena - Open Motion Planning Library (OMPL) plannerarena Closes: 909126 Changes: ompl (1.4.0+ds1-2) experimental; urgency=medium . * Closes: #909126. Fixed missing Breaks+Replaces: ompl-demos (<< 1.4) Checksums-Sha1: c2dcccf6d4f04c37dc87476f3c556a6eabb4df9b 2376 ompl_1.4.0+ds1-2.dsc 0bf75c63ec3bcde79907fb0c2b7b7ee0cb6779d6 22760103 ompl_1.4.0+ds1.orig.tar.gz 56a225d711a341154657fd4aeb5415af4f718b99 6516 ompl_1.4.0+ds1-2.debian.tar.xz 7ff21a4562f882ad8a64268ca3d48578881eb889 11286 ompl_1.4.0+ds1-2_source.buildinfo Checksums-Sha256: 610e3532be6a2317294f1018517e0fd9a34a123815bbf215cc280a96349c 2376 ompl_1.4.0+ds1-2.dsc 67ddac520fac70f63cf57e6099bf52eb3566e48c66d94baf3d8a811df0af8ed3 22760103 ompl_1.4.0+ds1.orig.tar.gz ecae793355088fb460f43e23f15aaa35bbf0991764965d1d0f5ebf64f4d5d003 6516 ompl_1.4.0+ds1-2.debian.tar.xz 7ab1cfbf71baae9635b06b6b403707c25bad8c686020ad0f088517534e4a77f2 11286 ompl_1.4.0+ds1-2_source.buildinfo Files: 7d33aeef54b6c6c76c99d1d6648fe986 2376 libs optional ompl_1.4.0+ds1-2.dsc b005535c9a0e47f6dcacb84a0c0be6a0 22760103 libs optional ompl_1.4.0+ds1.orig.tar.gz 3690e56da315071e405a1d4a390d739f 6516 libs optional ompl_1.4.0+ds1-2.debian.tar.xz 7e24b57d274527cdc671f1f62a0245f5 11286 libs optional ompl_1.4.0+ds1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEjF/vEZvRbmgP2ZRLBfSnqUmi2aoFAluim0AACgkQBfSnqUmi 2aqS6A/+JYe6NZuONs/6Vy/iqIxGlt0zzv7coUJ1g6aaPmOCkVXckLqItzPOg2zn oGBxtcOJe38pk0fL3n4qTl/Ln4D7YRrA10gYaG6XT7Gi9eiqGcPfvoMy0+MfzoDE nkF18RiKHZztAsEIU8+8d9FTSRektyoUe4fo5PSPTe1kdSMUfELs6iXqQnIASy+j nzMRxy7cUXlP6278zIV3RAGYtwWwYUMIMpHy570Y4NmSNW8tYyRuOFW1GfrK+iUf DzDV+a4QvaIf75uP+ZG+KtGv6JF3Lfm1dl0Dzx9StRodShGn+sZTAAT5ERf8ihfo
Bug#909210: Does it make sense to ship automake-1.15 in buster?
Package: automake-1.15 Version: 1:1.15.1-5 Severity: serious The 1.15 -> 1.16 changes were relatively minor. All FTBFS it caused should already be filed as bugs, and most have already been fixed. So far I haven't seen a single one that would have been difficult to fix. There are currently no reverse (build) dependencies on automake-1.15 in unstable, and I do not think there should ever be any. I might be missing something, but my current impression is that we should not ship automake-1.15 in buster.
Bug#908824: closed by Damyan Ivanov (Re: Bug#908824: libnet-server-mail-perl FTBFS: t/starttls.t failure)
Control: reopen -1 Doesn't seem to work: https://buildd.debian.org/status/package.php?p=libnet-server-mail-perl=sid 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
Processed: Re: Bug#908824 closed by Damyan Ivanov (Re: Bug#908824: libnet-server-mail-perl FTBFS: t/starttls.t failure)
Processing control commands:
> reopen -1
Bug #908824 {Done: Damyan Ivanov }
[src:libnet-server-mail-perl] libnet-server-mail-perl FTBFS: t/starttls.t
failure
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.25-3.
--
908824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#908824: marked as done (libnet-server-mail-perl FTBFS: t/starttls.t failure)
Your message dated Wed, 19 Sep 2018 18:08:25 + with message-id <20180919180825.2rixqclmqa5iowwk@fbd7c150-3361-11e8-8c11-5badabdd4a8d> and subject line Re: Bug#908824: libnet-server-mail-perl FTBFS: t/starttls.t failure has caused the Debian Bug report #908824, regarding libnet-server-mail-perl FTBFS: t/starttls.t failure 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.) -- 908824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libnet-server-mail-perl Version: 0.25-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=libnet-server-mail-perl=all=0.25-1=1536904015=0 ... Test Summary Report --- t/starttls.t (Wstat: 9 Tests: 3 Failed: 0) Non-zero wait status: 9 Parse errors: No plan found in TAP output Files=4, Tests=33, 2 wallclock secs ( 0.05 usr 0.04 sys + 0.67 cusr 0.20 csys = 0.96 CPU) Result: FAIL Failed 1/4 test programs. 0/33 subtests failed. make[1]: *** [Makefile:861: test_dynamic] Error 255 --- End Message --- --- Begin Message --- Version: 0.25-3 Forgot to close in the change log: Changes: libnet-server-mail-perl (0.25-3) unstable; urgency=medium . * Team upload . * tighten libio-socket-ssl-perl (build) dependency to >= 2.060-3~ * bump debhelper compatibility level to 11--- End Message ---
Bug#909205: FTBFS: 3 test failures
Source: chef Version: 13.8.7-2 Severity: serious Justification: fails to build from source This is the bottom of the build log: Finished in 1 minute 57.8 seconds (files took 6.76 seconds to load) 11422 examples, 3 failures, 24 pending Failed examples: rspec ./spec/unit/run_context/child_run_context_spec.rb:54 # Chef::RunContext::ChildRunContext with a run context with stuff in it and a child run context resource_collection is not the same as the parent rspec ./spec/unit/shell/shell_session_spec.rb:203 # Shell::SoloLegacySession returns a collection based on it's compilation object and the extra recipe provided by chef-shell rspec ./spec/unit/shell/shell_session_spec.rb:220 # Shell::SoloLegacySession generates its resource collection from the compiled cookbooks and the ad hoc recipe -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- debconf information excluded signature.asc Description: PGP signature
Bug#909203: libreswan: Hardcoded dependency on libunbound2 - stalls unbound transition
Package: libreswan
Version: 3.25-1
Severity: serious
Hi,
The libreswan package has a hardcoded dependency on libunbound2, which
prevents us from replacing libunbound2 with libunbound8. Please
remove that dependency and rely on ${shlib:Depends} (which pick ups
libunbound8 automatically).
Thanks,
~Niels
Processed: block 906417 with 907718
Processing commands for cont...@bugs.debian.org:
> block 906417 with 907718
Bug #906417 {Done: Thomas Goirand } [src:vitrage] vitrage:
FTBFS in buster/sid (failing tests)
Warning: Unknown package 'src:vitrage'
906417 was not blocked by any bugs.
906417 was not blocking any bugs.
Added blocking bug(s) of 906417: 907718
Warning: Unknown package 'src:vitrage'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
906417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#772479: marked as done (irssi-plugin-xmpp needs rebuild on new uploads of irssi)
Your message dated Wed, 19 Sep 2018 17:21:18 + with message-id and subject line Bug#772479: fixed in irssi-plugin-xmpp 0.54-2.1 has caused the Debian Bug report #772479, regarding irssi-plugin-xmpp needs rebuild on new uploads of irssi 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.) -- 772479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772479 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: irssi-plugin-otr Version: 1.0.0-1 Severity: grave X-Debbugs-CC: ir...@packages.debian.org Hello! Upgrading irssi from 0.8.16-1+b1 to 0.8.17-1 seems to break the OTR plugin for me. Opening a new query window and executing "/otr init" resulted usually in the initialisation of an OTR session. Doing it now seems to not send anything to the remote user I tried to init an OTR session with and instead a message like this shows up in the status window: 14:50:16 [oftc] OTR: Initiating OTR session... 14:50:20 [oftc] -!- H�G(�ff.�: No such nick/channel OTR inits from the remote end don't trigger any interesting status messages, but the query window contains the usual "Gone secure" message, but nearly after every message from the remote (sprinkled in with a message telling me that this wasn't sent inside the OTR session) and the indicator claims it is still plaintext. I haven't really investigated which one is true as that smells fishy either way. (I think it is unrelated, but for completeness: the remote end is Pidgin, but a simple webclient as remote doesn't show any message along the lines of "?OTRv23?" if I try to init either; irssi is connected via ZNC). Downgrading irssi to the previous version solves this issue. I have CC'ed irssi maintainers in case they have an idea what is wrong and/or as this if unsolved effects jessie might warrant a Breaks. Best regards David Kalnischkies signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: irssi-plugin-xmpp Source-Version: 0.54-2.1 We believe that the bug you reported is fixed in the latest version of irssi-plugin-xmpp, 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 772...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Kahn Gillmor (supplier of updated irssi-plugin-xmpp 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, 19 Sep 2018 10:14:11 -0400 Source: irssi-plugin-xmpp Binary: irssi-plugin-xmpp Architecture: source Version: 0.54-2.1 Distribution: unstable Urgency: medium Maintainer: Florian Schlichting Changed-By: Daniel Kahn Gillmor Description: irssi-plugin-xmpp - XMPP plugin for irssi Closes: 772479 Changes: irssi-plugin-xmpp (0.54-2.1) unstable; urgency=medium . * Non-maintainer upload, rebuilding against newer irssi (Closes: #772479) . [ Florian Schlichting ] * Move packaging to salsa.d.o . [ Daniel Kahn Gillmor ] * d/copyright: use https and fix upstream git * d/watch: use version 4, look at github releases * d/clean: clean up generated object files * introduce brittle versioning to roughly match irssi ABI Checksums-Sha1: d5f792104d67f90f239d9d7b24f08fadd1422e0a 1365 irssi-plugin-xmpp_0.54-2.1.dsc 9d821b5afbd72ddcdd6c1c9cd5f88be73b6ca0fd 29960 irssi-plugin-xmpp_0.54-2.1.debian.tar.xz 13e53e938fd8de1c6d49a6bac0e834e922bd3bd1 7467 irssi-plugin-xmpp_0.54-2.1_amd64.buildinfo Checksums-Sha256: 60ddd7ffad5933c243e7ef6f3c73545554a219cd748684d342b93abd524a2108 1365 irssi-plugin-xmpp_0.54-2.1.dsc b583563509041724229f9d3481438a8fcfbcc4acabf263476dbc5eba20caf6ce 29960 irssi-plugin-xmpp_0.54-2.1.debian.tar.xz 2928bd73c31e60f9816c77f33d06fc53f551d0285ab65edba44d03fa122b19ca 7467 irssi-plugin-xmpp_0.54-2.1_amd64.buildinfo Files: 9406317e0f0277f296d17c4e7c25f178 1365 net optional irssi-plugin-xmpp_0.54-2.1.dsc 9cfdba15df8b309f2bb03f84db1a173a 29960 net optional irssi-plugin-xmpp_0.54-2.1.debian.tar.xz 5035a549496ad1ceeb0044be07eb8ea9 7467 net optional irssi-plugin-xmpp_0.54-2.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQTTaP514aqS9uSbmdJsHx7ezFD6UwUCW6KBkwAKCRBsHx7ezFD6
Bug#908824: Bug #908824 in libnet-server-mail-perl marked as pending
Control: tag -1 pending Hello, Bug #908824 in libnet-server-mail-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libnet-server-mail-perl/commit/d06354cbe487096a0adf6adb5539dc044936b831 tighten libio-socket-ssl-perl (build) dependency to >= 2.060-3~ in an attempt to fix build failures hopefully Closes: #908824 (this message was generated automatically) -- Greetings https://bugs.debian.org/908824
Processed: Bug #908824 in libnet-server-mail-perl marked as pending
Processing control commands: > tag -1 pending Bug #908824 [src:libnet-server-mail-perl] libnet-server-mail-perl FTBFS: t/starttls.t failure Added tag(s) pending. -- 908824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#772479: irssi-plugin-xmpp does not work at all on buster
On Sat 2018-09-15 09:09:58 +0300, Adrian Bunk wrote: > It also needs a proper narrowly versioned dependency. while irssi packaging doesn't release the ABI, i still want irssi-plugin-xmpp to work for now. So I've added a (fairly brittle) build-dep and runtime versioning limits to irssi-plugin-xmpp, and uploaded it as an NMU 0.54-2.1. I did this because of Florian's lowNMU declaration and the package's presence in the collab-maint-equivalent debian/ group on salsa. The NMU also included a bit of minor package cleanup. I've uploaded the changes (and the git tag for the NMU) to salsa. Hope this work is useful! --dkg signature.asc Description: PGP signature
Bug#907953: network-manager-strongswan FTBFS with glib 2.58
BR forwarded to upstream. https://wiki.strongswan.org/issues/2765
Bug#909196: geany: webhelper seems ported to webkit2gtk, please reenable it
Package: geany-plugin-webhelper Version: geany-plugin-webhelper unable to install in testing Severity: grave when upgrade geany-plugin-webhelper are missing and due that breaks my geany instalation i make pressure due i'm unnable to use webhelper and geany becomes unnusable.. crash when push save button (due make refresh to the plugin that does not exist and config file said are enabled, but its a older version) The geany and geany-plugins packages are 1.33-1 version, geany-plugin-webhelper still only in 1.29 and it is unable to install cause dependencies error: geany-plugin-webhelper: Depende: geany-abi-71 Depende: geany-plugins-common (=1.29+dfsg-1) pero se va a instalar 1.33+dfsg-1+b1 Seems problema around webkit support was resolved with that commit: https://github.com/geany/geany-plugins/pull/746/commits/4039a13882f4b9e2127f6e7b018bdbdffe36e2a2 and the bugt reported https://github.com/geany/geany-plugins/issues/412 ; i added notes about it! Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Processed: Re: Bug#906342: byte-buddy: FTBFS in buster/sid (ExceptionInInitializerError: com.sun.tools.javac.code.TypeTags)
Processing commands for cont...@bugs.debian.org: > retitle 906342 lombok: Lombok fails with JDK 10 (ClassNotFoundException: > com.sun.tools.javac.code.TypeTags) Bug #906342 [src:byte-buddy] byte-buddy: FTBFS in buster/sid (Cannot find parent dependency net.bytebuddy:byte-buddy-parent:pom:debian) Changed Bug title to 'lombok: Lombok fails with JDK 10 (ClassNotFoundException: com.sun.tools.javac.code.TypeTags)' from 'byte-buddy: FTBFS in buster/sid (Cannot find parent dependency net.bytebuddy:byte-buddy-parent:pom:debian)'. > reassign 906342 liblombok-java 1.16.18+ds-3 Bug #906342 [src:byte-buddy] lombok: Lombok fails with JDK 10 (ClassNotFoundException: com.sun.tools.javac.code.TypeTags) Bug reassigned from package 'src:byte-buddy' to 'liblombok-java'. No longer marked as found in versions byte-buddy/1.7.11-1. Ignoring request to alter fixed versions of bug #906342 to the same values previously set Bug #906342 [liblombok-java] lombok: Lombok fails with JDK 10 (ClassNotFoundException: com.sun.tools.javac.code.TypeTags) Marked as found in versions lombok/1.16.18+ds-3. > affects 906342 src:byte-buddy Bug #906342 [liblombok-java] lombok: Lombok fails with JDK 10 (ClassNotFoundException: com.sun.tools.javac.code.TypeTags) Added indication that 906342 affects src:byte-buddy > forwarded 906342 https://github.com/rzwitserloot/lombok/issues/1572 Bug #906342 [liblombok-java] lombok: Lombok fails with JDK 10 (ClassNotFoundException: com.sun.tools.javac.code.TypeTags) Set Bug forwarded-to-address to 'https://github.com/rzwitserloot/lombok/issues/1572'. > fixed 906342 1.16.22-1 Bug #906342 [liblombok-java] lombok: Lombok fails with JDK 10 (ClassNotFoundException: com.sun.tools.javac.code.TypeTags) Marked as fixed in versions lombok/1.16.22-1. > user debian-j...@lists.debian.org Setting user to debian-j...@lists.debian.org (was ebo...@apache.org). > usertag 906342 + default-java10 There were no usertags set. Usertags are now: default-java10. > close 906342 Bug #906342 [liblombok-java] lombok: Lombok fails with JDK 10 (ClassNotFoundException: com.sun.tools.javac.code.TypeTags) Marked Bug as done > End of message, stopping processing here. Please contact me if you need assistance. -- 906342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906342 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906342: byte-buddy: FTBFS in buster/sid (Cannot find parent dependency net.bytebuddy:byte-buddy-parent:pom:debian)
This is actually an issue with lombok not supporting Java 10. It was fixed with the upload of lombok/1.16.22-1.
Bug#883974: retitle 883974
control: retitle -1 abinit: FTBFS on armel: test failures control: notfound -1 8.0.8-1 control: notfound -1 8.0.8-4 control: found -1 8.8.4-1 Hello, version 8.8.4-1 seems to have fixed the failing tests issue on mips64el and amd64, but the same tests now fail on armel. Best, Andrius -- Andrius Merkys Vilnius University Institute of Biotechnology, Saulėtekio al. 7, room V325 LT-10257 Vilnius, Lithuania
Processed: retitle 883974
Processing control commands: > retitle -1 abinit: FTBFS on armel: test failures Bug #883974 [src:abinit] abinit: FTBFS on mips64el: test failures Changed Bug title to 'abinit: FTBFS on armel: test failures' from 'abinit: FTBFS on mips64el: test failures'. > notfound -1 8.0.8-1 Bug #883974 [src:abinit] abinit: FTBFS on armel: test failures No longer marked as found in versions abinit/8.0.8-1. > notfound -1 8.0.8-4 Bug #883974 [src:abinit] abinit: FTBFS on armel: test failures No longer marked as found in versions abinit/8.0.8-4. > found -1 8.8.4-1 Bug #883974 [src:abinit] abinit: FTBFS on armel: test failures Marked as found in versions abinit/8.8.4-1. -- 883974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883974 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#839840: marked as done (ghci segfaults on armel, related to doctest failure)
Your message dated Wed, 19 Sep 2018 17:16:08 +0300 with message-id <20180919141608.22nzrs5g45s3z...@gmail.com> and subject line Re: Bug#839840: ghci segfaults on armel, related to doctest failure has caused the Debian Bug report #839840, regarding ghci segfaults on armel, related to doctest failure 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.) -- 839840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ghc Version: 7.10.3-9 Severity: serious clint@abel ~/haskell-http-api-data-0.2.4 % ghci -isrc -XCPP -D"MIN_VERSION_base(X,Y,Z)=1" GHCi, version 7.10.3: http://www.haskell.org/ghc/ :? for help Prelude> :l src/Web/HttpApiData.hs [1 of 2] Compiling Web.HttpApiData.Internal ( src/Web/HttpApiData/Internal.hs, interpreted ) [2 of 2] Compiling Web.HttpApiData ( src/Web/HttpApiData.hs, interpreted ) Ok, modules loaded: Web.HttpApiData, Web.HttpApiData.Internal. *Web.HttpApiData> :set -XOverloadedStrings *Web.HttpApiData> import Control.Applicative *Web.HttpApiData Control.Applicative> import Data.Time *Web.HttpApiData Control.Applicative Data.Time> import Data.Int *Web.HttpApiData Control.Applicative Data.Time Data.Int> import Data.Text (Text) *Web.HttpApiData Control.Applicative Data.Time Data.Int Data.Text> import Data.Time (Day) *Web.HttpApiData Control.Applicative Data.Time Data.Int Data.Text Data.Time> import Data.Version *Web.HttpApiData Control.Applicative Data.Time Data.Int Data.Text Data.Time Data.Version> toUrlPiece True "true" *Web.HttpApiData Control.Applicative Data.Time Data.Int Data.Text Data.Time Data.Version> parseUrlPiece "false" :: Either Text Bool zsh: segmentation fault ghci -isrc -XCPP -D"MIN_VERSION_base(X,Y,Z)=1" The backtrace is useless. --- End Message --- --- Begin Message --- Version: 8.4.3-6 On Wed, Oct 05, 2016 at 05:12PM, Clint Adams wrote: > clint@abel ~/haskell-http-api-data-0.2.4 > % ghci -isrc -XCPP -D"MIN_VERSION_base(X,Y,Z)=1" > GHCi, version 7.10.3: http://www.haskell.org/ghc/ :? for help > Prelude> :l src/Web/HttpApiData.hs > [1 of 2] Compiling Web.HttpApiData.Internal ( > src/Web/HttpApiData/Internal.hs, interpreted ) > [2 of 2] Compiling Web.HttpApiData ( src/Web/HttpApiData.hs, interpreted ) > Ok, modules loaded: Web.HttpApiData, Web.HttpApiData.Internal. > *Web.HttpApiData> :set -XOverloadedStrings > *Web.HttpApiData> import Control.Applicative > *Web.HttpApiData Control.Applicative> import Data.Time > *Web.HttpApiData Control.Applicative Data.Time> import Data.Int > *Web.HttpApiData Control.Applicative Data.Time Data.Int> import Data.Text > (Text) > *Web.HttpApiData Control.Applicative Data.Time Data.Int Data.Text> import > Data.Time (Day) > *Web.HttpApiData Control.Applicative Data.Time Data.Int Data.Text Data.Time> > import Data.Version > *Web.HttpApiData Control.Applicative Data.Time Data.Int Data.Text Data.Time > Data.Version> toUrlPiece True > "true" > *Web.HttpApiData Control.Applicative Data.Time Data.Int Data.Text Data.Time > Data.Version> parseUrlPiece "false" :: Either Text Bool > zsh: segmentation fault ghci -isrc -XCPP -D"MIN_VERSION_base(X,Y,Z)=1" On Fri, 7 Oct 2016 11:10:50 +0200 Sven Bartscher wrote: > This bug I reported upstream[1] might be related to that. > > [1]: https://ghc.haskell.org/trac/ghc/ticket/11831 I can reproduce both of these with ghc-8.2.2, but not with ghc-8.4.3 (available in experimental as of now). Marking this as fixed for now, and will reopen if doctests continue to fail on armel. Cheers, -- Ilias--- End Message ---
Bug#898950: Processed: severity of 898950 is serious
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: severity -1 important control: retitle -1 "verve-focus program missing from package" On Mon, 2018-09-17 at 20:33 +, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > > > severity 898950 serious > > Bug #898950 [xfce4-verve-plugin] xfce4-verve-plugin: the essential `verve- > focus` program is missing in this version, which makes it useless > Severity set to 'serious' from 'important' > > thanks Hi Adrian, I'm unsure why you think this bug is release critical, and there is no content in your mail which help. I disagree with this, so I'm lowering the severity again, but feel free to comment on this. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAluiTkYACgkQ3rYcyPpX RFtITwf/RR0cKilDOjhshcXqa3SfE/UbrkD/1dRpnSOlrfFN8CB34QHwIM91rE1S U4mIjAMbkBstv0J0hr1wdjJ1ynpMbXZJhwNeUvyhBO1t6YBQnhn2jC8/OkYfJWxr GZWhlB6z4cx+Vsm24Zc2elhUeYj6bTbaxAL82M6APtMHj8umPzdIBlOCzsgpqTHy N4jpDmEp1iUkcSB6hleKmkMK0hDCUthPvgVaIffn6RJHoFngYd3hLXQ+v1V2gLPP 6uYtq4vlCIbi+cxnh47JenzR18Fy3O/eLBM9uSio4RRl2EaZvPfLaSf/QXuR2hgg WcJUJYnFl60cwkhClzcm9VkV4KsYoQ== =EubS -END PGP SIGNATURE-
Processed: Re: Processed: severity of 898950 is serious
Processing control commands: > severity -1 important Bug #898950 [xfce4-verve-plugin] xfce4-verve-plugin: the essential `verve-focus` program is missing in this version, which makes it useless Severity set to 'important' from 'serious' > retitle -1 "verve-focus program missing from package" Bug #898950 [xfce4-verve-plugin] xfce4-verve-plugin: the essential `verve-focus` program is missing in this version, which makes it useless Changed Bug title to '"verve-focus program missing from package"' from 'xfce4-verve-plugin: the essential `verve-focus` program is missing in this version, which makes it useless'. -- 898950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898950 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#902631: NMU?
Hi, Nicolas, you planned to do NMU. I support proposed solution (src package fork). Can you go ahead please? This blocks my package. Thanks a lot. -- Best regards Ondřej Nový PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B signature.asc Description: Message signed with OpenPGP
Bug#890141: marked as done (node-dashdash FTBFS with Node.js 8.9.3: test failure)
Your message dated Wed, 19 Sep 2018 12:35:59 +
with message-id
and subject line Bug#890141: fixed in node-dashdash 1.14.1-2
has caused the Debian Bug report #890141,
regarding node-dashdash FTBFS with Node.js 8.9.3: test failure
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.)
--
890141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-dashdash
Version: 1.14.1-1
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-dashdash.html
...
debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/node-dashdash-1.14.1'
nodeunit test/*.test.js
[1mbasics.test.js[22m
✔ exports
✔ createParser
✔ Parser
✔ parse
✔ old Parser.parse() API
✔ slice
✔ synopsisFromOpt
✔ case 0: node tool.js
✔ case 1: node tool.js a b c
✔ case 2: node tool.js a b
✔ case 3: node tool.js -- a
✔ case 4: node tool.js a -- b
✔ case 5: node tool.js a -- --help
✔ case 6: node tool.js --help
✔ case 7: node tool.js --help a b
✔ case 8: node tool.js a --help b
✔ case 9: node tool.js a --help b
✔ case 10: node tool.js a --help b
✔ case 11: node tool.js --help=foo
✔ case 12: node tool.js --file
✔ case 13: node tool.js
✔ case 14: node tool.js --file foo.txt
✔ case 15: node tool.js --file=foo.txt
✔ case 16: node tool.js -
✔ case 17: node tool.js -h
✔ case 18: node tool.js -f
✔ case 19: node tool.js -f foo.txt
✔ case 20: node tool.js -ffoo.txt
✔ case 21: node ls.js -l -a dir
✔ case 22: node ls.js -l dir -a
✔ case 23: node ls.js -l dir -a
✔ case 24: node ls.js -la dir
✔ case 25: node tool.js -af
✔ case 26: node tool.js -af foo.txt
✔ case 27: node tool.js -affoo.txt
✔ case 28: node tool.js -v -vvf
✔ case 29: node tool.js -v -vvf foo.txt
✔ case 30: node tool.js -v -vvffoo.txt
✔ case 31: node tool.js -a 5 -b4 -c -1 -d -3.14159 -e 1.0e42 foo
✔ case 32: node tool.js -t 5a
✔ case 33: node tool.js -vvv foo bar
✔ case 34: node tool.js foo bar
✔ case 35: node tool.js -w club --weapon mallet -w sword bang
✔ case 36: node tool.js --split 10 -s 5 -s 0.01 bang
✔ case 37: node tool.js --help
✔ case 38: node option-groups-tool.js --help
✔ case 39: node tool.js -t 0
✔ case 40: node tool.js -t 42
✔ case 41: node tool.js -t42
✔ case 42: node tool.js -t -5
✔ case 43: node tool.js -t-5
✔ case 44: node tool.js -t 1e2
✔ case 45: node tool.js -t 0x32
✔ case 46: node tool.js -t 3.1
✔ case 47: node tool.js -t 42.
✔ case 48: node tool.js -t 1e-2
✔ case 49: node tool.js
✔ case 50: node tool.js -t 42
✔ case 51: node tool.js -t 1 -t 2 -t -3
✔ case 52: node tool.js -t 1 -t 1e2
✔ case 53: node tool.js -t 0
✔ case 54: node tool.js -t 42
✔ case 55: node tool.js -t42
✔ case 56: node tool.js -t -5
✔ case 57: node tool.js -t42
✔ case 58: node tool.js -t 42 -t -5
✔ case 59: node foo.js -v
✔ case 60: FOO_VERBOSE=1 node foo.js -v
✔ case 61: FOO_VERBOSE=1 node foo.js
✔ case 62: FOO_VERBOSE=0 node foo.js
✔ case 63: FOO_VERBOSE= node foo.js
✔ case 64: node tool.js --help
✔ case 65: node foo.js -t 42
✔ case 66: FOO_TIMEOUT=32 node foo.js
✔ case 67: FOO_TIMEOUT=32 node foo.js -t 52
✔ case 68: FOO_TIMEOUT=wallawalla node foo.js -t 52
✔ case 69: FOO_TIMEOUT=wallawalla node foo.js
✔ case 70: FOO_VERBOSE=blah node foo.js
✔ case 71: FOO_VERBOSE=blah node foo.js -v
✔ case 72: FOO_VERBOSE=blah node foo.js -vv
✔ case 73: node foo.js --dry-run
✔ case 74: node foo.js --foo-bar-
✔ case 75: node foo.js
✔ case 76: FOO_FILE=env.file node foo.js
✔ case 77: FOO_FILE=env.file node foo.js -f argv.file
✔ case 78: node foo.js
✔ case 79: FOO_VERBOSE=1 node foo.js
✔ case 80: FOO_VERBOSE=0 node foo.js
✔ case 81: FOO_VERBOSE=0 node foo.js -v
✔ case 82: node tool.js a --help -b --cheese
✔ case 83: node tool.js a -bcd --cheese --help
✔ case 84: node foo.js -s
✔ case 85: node foo.js -s notadate
✔ case 86: node foo.js -s 0
✔ case 87: node foo.js -s 1
✔ case 88: node foo.js -s 1396065084
✔ case 89: node foo.js -s 2014-04-01
✔ case 90: node foo.js -s 2014-04-01T
[31m✖ case 91: node foo.js -s 2014-04-01T12:01:02[39m
AssertionError: { start: 2014-04-02T00:01:02.000Z, _args: [] } deepEqual {
start: 2014-04-01T12:01:02.000Z, _args: [] }
at Object.deepEqual (/usr/lib/nodejs/nodeunit/lib/types.js:83:39)
at Object.
(/build/1st/node-dashdash-1.14.1/test/basics.test.js:1177:15)
at Object._ (/build/1st/node-dashdash-1.14.1/test/tap4nodeunit.js:56:32)
at /usr/lib/nodejs/nodeunit/lib/core.js:232:20
at /usr/lib/nodejs/nodeunit/deps/async.js:168:13
at /usr/lib/nodejs/nodeunit/deps/async.js:131:25
at /usr/lib/nodejs/nodeunit/deps/async.js:165:17
at
Bug#904714: marked as done (wreport ftbfs on arm64 and armel at least)
Your message dated Wed, 19 Sep 2018 12:36:25 + with message-id and subject line Bug#904714: fixed in wreport 3.14-1 has caused the Debian Bug report #904714, regarding wreport ftbfs on arm64 and armel at least 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.) -- 904714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:wreport Version: 3.13-1 Severity: serious Tags: sid buster Making all in doc make[3]: Entering directory '/<>/doc' No doxygen warnings about undocumented functions. Use ./configure --enable-doxy-undoc-warnings to turn them on doxygen libwreport.dox No doxygen warnings about undocumented functions. Use ./configure --enable-doxy-undoc-warnings to turn them on doxygen libwreport.dox warning: Tag `SYMBOL_CACHE_SIZE' at line 290 of file `libwreport.dox' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag `SYMBOL_CACHE_SIZE' at line 290 of file `libwreport.dox' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag `SHOW_DIRECTORIES' at line 490 of file `libwreport.dox' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag `SHOW_DIRECTORIES' at line 490 of file `libwreport.dox' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag `HTML_ALIGN_MEMBERS' at line 848 of file `libwreport.dox' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag `HTML_ALIGN_MEMBERS' at line 848 of file `libwreport.dox' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag `USE_INLINE_TREES' at line 1033 of file `libwreport.dox' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag `USE_INLINE_TREES' at line 1033 of file `libwreport.dox' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag `XML_SCHEMA' at line 1258 of file `libwreport.dox' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag `XML_DTD' at line 1264 of file `libwreport.dox' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag `XML_SCHEMA' at line 1258 of file `libwreport.dox' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: Tag `XML_DTD' at line 1264 of file `libwreport.dox' has become obsolete. To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u" warning: doxygen no longer ships with the FreeSans font. You may want to clear or change DOT_FONTNAME. Otherwise you run the risk that the wrong font is being used for dot generated graphs. warning: doxygen no longer ships with the FreeSans font. You may want to clear or change DOT_FONTNAME. Otherwise you run the risk that the wrong font is being used for dot generated graphs. error: Could not create output directory /<>/doc/apidocs make[3]: *** [Makefile:543: apidocs/index.html] Error 1 make[3]: *** Waiting for unfinished jobs /<>/wreport/style.dox:39: warning: Reached end of file while still inside a (nested) comment. Nesting level 2 (probable line reference: 3, 1) /<>/wreport/bulletin.h:343: warning: argument 'buf' of command @param is not found in the argument list of wreport::BufrBulletin::decode(const std::string , const char *fname="(memory)", size_t offset=0) /<>/wreport/bulletin.h:355: warning: The following parameters of wreport::BufrBulletin::decode(const std::string , const char *fname="(memory)", size_t offset=0) are not documented: parameter 'raw' /<>/wreport/bulletin.h:373: warning: argument 'buf' of command @param is not found in the argument list of wreport::BufrBulletin::decode(const std::string , const BufrCodecOptions , const char *fname="(memory)", size_t offset=0)
Bug#896990: (no subject)
Please note that flickrbackup is marked for removal already (#904925). Bests, -- tiago
Bug#906679: FYI - upstream fix
Hi, I came by the same FTBFS and wanted to let you know that we picked upstream [1] to fix it. Hope that helps to get it resolved for you as well! [1]: https://github.com/OpenSC/pam_p11/commit/55b3888d5e9208948a40725350ca2f50020c4838 -- Christian Ehrhardt Software Engineer, Ubuntu Server Canonical Ltd
Processed: severity of 892256 is serious
Processing commands for cont...@bugs.debian.org: > severity 892256 serious Bug #892256 [system-config-printer] system-config-printer: Doesn't launch anymore Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 892256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#890141 closed by Pirate Praveen (seems the bug is gone with nodejs 8.11.2)
Processing control commands:
> reopen -1
Bug #890141 {Done: Pirate Praveen }
[src:node-dashdash] node-dashdash FTBFS with Node.js 8.9.3: test failure
Bug reopened
Ignoring request to alter fixed versions of bug #890141 to the same values
previously set
--
890141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#890141: closed by Pirate Praveen (seems the bug is gone with nodejs 8.11.2)
Control: reopen -1 > successful build log attached. Still fails for me, and still fails in reproducible. What timezone are you using? After looking at the error, I figured out the following was to reproduce the problem: $ TZ=UTC dpkg-buildpackage -b $ TZ=UTC+1 dpkg-buildpackage -b 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
Processed: seems the bug is gone with nodejs 8.11.2
Processing control commands: > notfound -1 1.14.1-1 Bug #890141 [src:node-dashdash] node-dashdash FTBFS with Node.js 8.9.3: test failure No longer marked as found in versions node-dashdash/1.14.1-1. -- 890141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890141 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909173: libepoxy: diff for NMU version 1.5.2-0.2
Control: tags 909173 + patch
Control: tags 909173 + pending
I've prepared an NMU for libepoxy (versioned as 1.5.2-0.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should alter that delay.
The changes are also available here:
https://salsa.debian.org/smcv/libepoxy
or in the form of a merge request:
https://salsa.debian.org/debian/libepoxy/merge_requests/1
I took the opportunity to fix the build-time tests on Debian's version
of xvfb-run, on at least amd64. I don't know whether this will make the
tests pass on all architectures, so I've left it ignoring test failures
on non-Ubuntu systems for now; but if buildd logs indicate that the tests
passed on all release architectures, it would be good to stop ignoring
test failures (i.e. use the Ubuntu case) for all vendors.
smcv
diffstat for libepoxy-1.5.2 libepoxy-1.5.2
changelog | 10 ++
control |5 -
rules |4 ++--
3 files changed, 16 insertions(+), 3 deletions(-)
diff -Nru libepoxy-1.5.2/debian/changelog libepoxy-1.5.2/debian/changelog
--- libepoxy-1.5.2/debian/changelog 2018-09-18 20:09:26.0 +0100
+++ libepoxy-1.5.2/debian/changelog 2018-09-19 10:39:51.0 +0100
@@ -1,3 +1,13 @@
+libepoxy (1.5.2-0.2) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * libepoxy-dev Depends on libgl1-mesa-dev and libegl1-mesa-dev.
+Those packages provide gl.pc and egl.pc, which are depended on by
+epoxy.pc since 1.5.2 (Closes: #909173)
+ * Work around #874077 by creating an Xvfb screen where GLX can work
+
+ -- Simon McVittie Wed, 19 Sep 2018 10:39:51 +0100
+
libepoxy (1.5.2-0.1) unstable; urgency=medium
* Non-maintainer upload
diff -Nru libepoxy-1.5.2/debian/control libepoxy-1.5.2/debian/control
--- libepoxy-1.5.2/debian/control 2018-09-18 20:09:26.0 +0100
+++ libepoxy-1.5.2/debian/control 2018-09-19 10:39:51.0 +0100
@@ -21,7 +21,10 @@
Section: libdevel
Architecture: any
Multi-Arch: same
-Depends: libepoxy0 (= ${binary:Version}), ${misc:Depends}
+Depends: libegl1-mesa-dev,
+ libepoxy0 (= ${binary:Version}),
+ libgl1-mesa-dev,
+ ${misc:Depends}
Description: OpenGL function pointer management library- development
It hides the complexity of dlopen(), dlsym(), glXGetProcAddress(),
eglGetProcAddress(), etc. from the app developer, with very little
diff -Nru libepoxy-1.5.2/debian/rules libepoxy-1.5.2/debian/rules
--- libepoxy-1.5.2/debian/rules 2018-09-18 20:09:26.0 +0100
+++ libepoxy-1.5.2/debian/rules 2018-09-19 10:39:51.0 +0100
@@ -7,9 +7,9 @@
# See https://bugs.debian.org/874077
override_dh_auto_test:
ifeq (yes,$(shell dpkg-vendor --derives-from Ubuntu && echo yes))
- xvfb-run dh_auto_test
+ xvfb-run -a -s "-screen 0 1024x768x24" dh_auto_test
else
- -xvfb-run dh_auto_test
+ -xvfb-run -a -s "-screen 0 1024x768x24" dh_auto_test
endif
# No symbols for udebs, specify the highest version from symbols file:
Bug#890141: marked as done (node-dashdash FTBFS with Node.js 8.9.3: test failure)
Your message dated Wed, 19 Sep 2018 15:38:27 +0530
with message-id
and subject line seems the bug is gone with nodejs 8.11.2
has caused the Debian Bug report #890141,
regarding node-dashdash FTBFS with Node.js 8.9.3: test failure
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.)
--
890141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-dashdash
Version: 1.14.1-1
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-dashdash.html
...
debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/node-dashdash-1.14.1'
nodeunit test/*.test.js
[1mbasics.test.js[22m
✔ exports
✔ createParser
✔ Parser
✔ parse
✔ old Parser.parse() API
✔ slice
✔ synopsisFromOpt
✔ case 0: node tool.js
✔ case 1: node tool.js a b c
✔ case 2: node tool.js a b
✔ case 3: node tool.js -- a
✔ case 4: node tool.js a -- b
✔ case 5: node tool.js a -- --help
✔ case 6: node tool.js --help
✔ case 7: node tool.js --help a b
✔ case 8: node tool.js a --help b
✔ case 9: node tool.js a --help b
✔ case 10: node tool.js a --help b
✔ case 11: node tool.js --help=foo
✔ case 12: node tool.js --file
✔ case 13: node tool.js
✔ case 14: node tool.js --file foo.txt
✔ case 15: node tool.js --file=foo.txt
✔ case 16: node tool.js -
✔ case 17: node tool.js -h
✔ case 18: node tool.js -f
✔ case 19: node tool.js -f foo.txt
✔ case 20: node tool.js -ffoo.txt
✔ case 21: node ls.js -l -a dir
✔ case 22: node ls.js -l dir -a
✔ case 23: node ls.js -l dir -a
✔ case 24: node ls.js -la dir
✔ case 25: node tool.js -af
✔ case 26: node tool.js -af foo.txt
✔ case 27: node tool.js -affoo.txt
✔ case 28: node tool.js -v -vvf
✔ case 29: node tool.js -v -vvf foo.txt
✔ case 30: node tool.js -v -vvffoo.txt
✔ case 31: node tool.js -a 5 -b4 -c -1 -d -3.14159 -e 1.0e42 foo
✔ case 32: node tool.js -t 5a
✔ case 33: node tool.js -vvv foo bar
✔ case 34: node tool.js foo bar
✔ case 35: node tool.js -w club --weapon mallet -w sword bang
✔ case 36: node tool.js --split 10 -s 5 -s 0.01 bang
✔ case 37: node tool.js --help
✔ case 38: node option-groups-tool.js --help
✔ case 39: node tool.js -t 0
✔ case 40: node tool.js -t 42
✔ case 41: node tool.js -t42
✔ case 42: node tool.js -t -5
✔ case 43: node tool.js -t-5
✔ case 44: node tool.js -t 1e2
✔ case 45: node tool.js -t 0x32
✔ case 46: node tool.js -t 3.1
✔ case 47: node tool.js -t 42.
✔ case 48: node tool.js -t 1e-2
✔ case 49: node tool.js
✔ case 50: node tool.js -t 42
✔ case 51: node tool.js -t 1 -t 2 -t -3
✔ case 52: node tool.js -t 1 -t 1e2
✔ case 53: node tool.js -t 0
✔ case 54: node tool.js -t 42
✔ case 55: node tool.js -t42
✔ case 56: node tool.js -t -5
✔ case 57: node tool.js -t42
✔ case 58: node tool.js -t 42 -t -5
✔ case 59: node foo.js -v
✔ case 60: FOO_VERBOSE=1 node foo.js -v
✔ case 61: FOO_VERBOSE=1 node foo.js
✔ case 62: FOO_VERBOSE=0 node foo.js
✔ case 63: FOO_VERBOSE= node foo.js
✔ case 64: node tool.js --help
✔ case 65: node foo.js -t 42
✔ case 66: FOO_TIMEOUT=32 node foo.js
✔ case 67: FOO_TIMEOUT=32 node foo.js -t 52
✔ case 68: FOO_TIMEOUT=wallawalla node foo.js -t 52
✔ case 69: FOO_TIMEOUT=wallawalla node foo.js
✔ case 70: FOO_VERBOSE=blah node foo.js
✔ case 71: FOO_VERBOSE=blah node foo.js -v
✔ case 72: FOO_VERBOSE=blah node foo.js -vv
✔ case 73: node foo.js --dry-run
✔ case 74: node foo.js --foo-bar-
✔ case 75: node foo.js
✔ case 76: FOO_FILE=env.file node foo.js
✔ case 77: FOO_FILE=env.file node foo.js -f argv.file
✔ case 78: node foo.js
✔ case 79: FOO_VERBOSE=1 node foo.js
✔ case 80: FOO_VERBOSE=0 node foo.js
✔ case 81: FOO_VERBOSE=0 node foo.js -v
✔ case 82: node tool.js a --help -b --cheese
✔ case 83: node tool.js a -bcd --cheese --help
✔ case 84: node foo.js -s
✔ case 85: node foo.js -s notadate
✔ case 86: node foo.js -s 0
✔ case 87: node foo.js -s 1
✔ case 88: node foo.js -s 1396065084
✔ case 89: node foo.js -s 2014-04-01
✔ case 90: node foo.js -s 2014-04-01T
[31m✖ case 91: node foo.js -s 2014-04-01T12:01:02[39m
AssertionError: { start: 2014-04-02T00:01:02.000Z, _args: [] } deepEqual {
start: 2014-04-01T12:01:02.000Z, _args: [] }
at Object.deepEqual (/usr/lib/nodejs/nodeunit/lib/types.js:83:39)
at Object.
(/build/1st/node-dashdash-1.14.1/test/basics.test.js:1177:15)
at Object._ (/build/1st/node-dashdash-1.14.1/test/tap4nodeunit.js:56:32)
at /usr/lib/nodejs/nodeunit/lib/core.js:232:20
at /usr/lib/nodejs/nodeunit/deps/async.js:168:13
at /usr/lib/nodejs/nodeunit/deps/async.js:131:25
at /usr/lib/nodejs/nodeunit/deps/async.js:165:17
at
Bug#890141: seems the bug is gone with nodejs 8.11.2
Control: notfound -1 1.14.1-1 successful build log attached. sbuild (Debian sbuild) 0.77.1 (10 September 2018) on nishumbha +==+ | node-dashdash 1.14.1-1 (amd64) Wed, 19 Sep 2018 10:01:56 + | +==+ Package: node-dashdash Version: 1.14.1-1 Source Version: 1.14.1-1 Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: full I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-amd64-sbuild-8ec254db-c90e-462c-9f85-df92e5451b6a' with '<>' I: NOTICE: Log filtering will replace 'build/node-dashdash-4ogwx7/resolver-JEh6XO' with '<>' +--+ | Update chroot| +--+ Get:1 http://deb.debian.org/debian unstable InRelease [233 kB] Get:2 http://deb.debian.org/debian unstable/main Sources.diff/Index [27.9 kB] Get:3 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [27.9 kB] Get:4 http://deb.debian.org/debian unstable/main Sources 2018-09-17-0814.05.pdiff [8467 B] Get:5 http://deb.debian.org/debian unstable/main Sources 2018-09-17-1409.40.pdiff [20.1 kB] Get:6 http://deb.debian.org/debian unstable/main Sources 2018-09-17-2011.05.pdiff [18.8 kB] Get:7 http://deb.debian.org/debian unstable/main Sources 2018-09-18-0208.19.pdiff [6791 B] Get:8 http://deb.debian.org/debian unstable/main Sources 2018-09-18-0807.59.pdiff [6828 B] Get:9 http://deb.debian.org/debian unstable/main Sources 2018-09-18-1411.47.pdiff [16.7 kB] Get:10 http://deb.debian.org/debian unstable/main Sources 2018-09-18-2009.52.pdiff [26.1 kB] Get:11 http://deb.debian.org/debian unstable/main Sources 2018-09-19-0208.44.pdiff [6085 B] Get:12 http://deb.debian.org/debian unstable/main Sources 2018-09-19-0806.18.pdiff [3355 B] Get:13 http://deb.debian.org/debian unstable/main amd64 Packages 2018-09-17-0814.05.pdiff [5159 B] Get:14 http://deb.debian.org/debian unstable/main amd64 Packages 2018-09-17-1409.40.pdiff [28.6 kB] Get:15 http://deb.debian.org/debian unstable/main amd64 Packages 2018-09-17-2011.05.pdiff [14.4 kB] Get:16 http://deb.debian.org/debian unstable/main amd64 Packages 2018-09-18-0208.19.pdiff [20.7 kB] Get:17 http://deb.debian.org/debian unstable/main amd64 Packages 2018-09-18-0807.59.pdiff [10.3 kB] Get:18 http://deb.debian.org/debian unstable/main amd64 Packages 2018-09-18-1411.47.pdiff [15.5 kB] Get:19 http://deb.debian.org/debian unstable/main amd64 Packages 2018-09-18-2009.52.pdiff [15.5 kB] Get:12 http://deb.debian.org/debian unstable/main Sources 2018-09-19-0806.18.pdiff [3355 B] Get:20 http://deb.debian.org/debian unstable/main amd64 Packages 2018-09-19-0208.44.pdiff [10.1 kB] Get:21 http://deb.debian.org/debian unstable/main amd64 Packages 2018-09-19-0806.18.pdiff [1183 B] Get:21 http://deb.debian.org/debian unstable/main amd64 Packages 2018-09-19-0806.18.pdiff [1183 B] Fetched 523 kB in 2s (265 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... The following packages were automatically installed and are no longer required: ca-certificates e2fsprogs-l10n libgpm2 libssl1.1 openssl Use 'apt autoremove' to remove them. The following packages will be upgraded: apt cpp-8 g++-8 gcc-8 gcc-8-base libapt-pkg5.0 libasan5 libatomic1 libcc1-0 libgcc-8-dev libgcc1 libgnutls30 libgomp1 libitm1 liblsan0 libmpx2 libquadmath0 libstdc++-8-dev libstdc++6 libtsan0 libubsan1 linux-libc-dev 22 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 4691 kB/32.9 MB of archives. After this operation, 50.2 kB of additional disk space will be used. Get:1 http://deb.debian.org/debian unstable/main amd64 libapt-pkg5.0 amd64 1.7.0~rc1 [954 kB] Get:2 http://deb.debian.org/debian unstable/main amd64 libgnutls30 amd64 3.5.19-1+b1 [891 kB] Get:3 http://deb.debian.org/debian unstable/main amd64 apt amd64 1.7.0~rc1 [1319 kB] Get:4 http://deb.debian.org/debian unstable/main amd64 linux-libc-dev amd64 4.18.8-1 [1527 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 4691 kB in 0s (59.9 MB/s) (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
Processed: libepoxy: diff for NMU version 1.5.2-0.2
Processing control commands: > tags 909173 + patch Bug #909173 [libepoxy-dev] libepoxy-dev: New pkg-config dependencies that are not package dependencies Added tag(s) patch. > tags 909173 + pending Bug #909173 [libepoxy-dev] libepoxy-dev: New pkg-config dependencies that are not package dependencies Added tag(s) pending. -- 909173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909181: libmariadb-dev: does not depend on zlib1g-dev, while mariadb_config reports `-lz`
Package: libmariadb-dev Version: 1:3.0.6-1 Severity: serious Hi, libmariadb-dev on Debian/stretch behaved like that: % mariadb_config --libs -L/usr/lib/x86_64-linux-gnu -lmariadb while libmariadb-dev on (current, as of 2018-09-19) Debian/buster behaves like that: % mariadb_config --libs -L/usr/lib/x86_64-linux-gnu/ -lmariadb -lz -ldl -lm -lpthread -lssl -lcrypto But libmariadb-dev does NOT depend on zlib1g-dev: % apt-cache show libmariadb-dev | grep Depends Depends: libmariadb3 (= 1:3.0.6-1), libc6 (>= 2.3.4) That means projects depending on libmariadb-dev will stop building, if they don't have zlib1g-dev in their Build-Depends already. Possible solutions: 1) hide those new depends (-lz ...) again 2) add relevant library/libraries to Depends The first option is probably preferable, because it looks like those are implementation details, and they should not leak into transitive dependers. regards, -mika-
Processed: affects 909173
Processing commands for cont...@bugs.debian.org: > affects 909173 + src:gtk+3.0 Bug #909173 [libepoxy-dev] libepoxy-dev: New pkg-config dependencies that are not package dependencies Added indication that 909173 affects src:gtk+3.0 > thanks Stopping processing here. Please contact me if you need assistance. -- 909173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#908290: marked as done (Please package 0.7.11)
Your message dated Wed, 19 Sep 2018 09:35:37 + with message-id and subject line Bug#908290: fixed in zfs-linux 0.7.11-1 has caused the Debian Bug report #908290, regarding Please package 0.7.11 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.) -- 908290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zfs-linux Severity: important Tags: patch --- Please enter the report below this line. --- The recent release of zfsonlinux 0.7.10 adds support for Linux kernel 4.18. There are some slight changes in upstream that can simplify the Debian packaging, and have been incorporated into [1] (it uses the upstream version of the dkms configuration file). It also ships upstream's bash completion file, instead of a second copy that looks to have fallen out of maintenance, in addition to several other cleanups. The release of 0.7.10 should (I believe) supersede [2]. [1] https://salsa.debian.org/zfsonlinux-team/zfs/merge_requests/9 [2] https://salsa.debian.org/zfsonlinux-team/zfs/merge_requests/10 --- End Message --- --- Begin Message --- Source: zfs-linux Source-Version: 0.7.11-1 We believe that the bug you reported is fixed in the latest version of zfs-linux, 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 908...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mo Zhou (supplier of updated zfs-linux 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, 19 Sep 2018 08:45:18 + Source: zfs-linux Binary: libnvpair1linux libuutil1linux libzfslinux-dev libzfs2linux libzpool2linux zfs-dkms zfs-initramfs zfs-dracut zfsutils-linux zfs-zed zfs-test zfs-dbg Architecture: source Version: 0.7.11-1 Distribution: unstable Urgency: medium Maintainer: Debian ZFS on Linux maintainers Changed-By: Mo Zhou Description: libnvpair1linux - Solaris name-value library for Linux libuutil1linux - Solaris userland utility library for Linux libzfs2linux - OpenZFS filesystem library for Linux libzfslinux-dev - OpenZFS filesystem development files for Linux libzpool2linux - OpenZFS pool library for Linux zfs-dbg- Debugging symbols for OpenZFS userland libraries and tools zfs-dkms - OpenZFS filesystem kernel modules for Linux zfs-dracut - OpenZFS root filesystem capabilities for Linux - dracut zfs-initramfs - OpenZFS root filesystem capabilities for Linux - initramfs zfs-test - OpenZFS test infrastructure an support scripts zfs-zed- OpenZFS Event Daemon zfsutils-linux - command-line tools to manage OpenZFS filesystems Closes: 895873 900714 908290 Changes: zfs-linux (0.7.11-1) unstable; urgency=medium . [ Aron Xu ] * Add dpkg-dev to Depends of zfs-dkms (Closes: #900714) . [ Nicolas Braud-Santoni ] * Use canonical HTTPS format URL for Vcs-Git (Closes: #895873) . [ Mo Zhou ] * New upstream version 0.7.11 (Closes: #908290) * Bump linux_compat to 4.18 . * Replace get_next.sh with one-liner awk script in rules. * Append myself to Uploaders and refresh auto-generated control. * Use HTTPS format URI in watch file. * Recommends linux-libc-dev (<< LINUX_NEXT~) instead of (<< LINUX_NEXT). Checksums-Sha1: 0d18da4bf99aa3d1ca6b21ffd444d5d76958d9d0 3004 zfs-linux_0.7.11-1.dsc afed1dc6fe5a905f83538dfd9fd0bd66f4791d86 6561125 zfs-linux_0.7.11.orig.tar.gz 084c8f6747d483e18034daf4d52a664884a424d7 42944 zfs-linux_0.7.11-1.debian.tar.xz dfebccc2b61467b88bf08280df17f8e94cf1224b 6872 zfs-linux_0.7.11-1_source.buildinfo Checksums-Sha256: 7e1fd577c01bef6906f2178ccb9685c261ecd0ef27c811bff02090755e09ef45 3004 zfs-linux_0.7.11-1.dsc 4dff9ecce6e02061242d9435febe88c1250de83b96d392b712bccf31c459517a 6561125 zfs-linux_0.7.11.orig.tar.gz 3bee034133ee478d4f2ca098e4d2dfb6e9fec6d01702ed61bd8f862e4850d57b 42944 zfs-linux_0.7.11-1.debian.tar.xz b8df8eba83f657fd274b28fb57b5cdaff1b6cbfec70d05a55e016425a08776ad 6872 zfs-linux_0.7.11-1_source.buildinfo Files: 3b3c9da6b5236e934468d8fb31ad808f 3004 contrib/kernel optional zfs-linux_0.7.11-1.dsc ad51229183cac5d7ec5fe7577c778a53 6561125 contrib/kernel optional
Processed: severity of 909165 is serious
Processing commands for cont...@bugs.debian.org: > severity 909165 serious Bug #909165 [linkchecker-gui] linkchecker-gui: linkcheker-gui does not start Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 909165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909096: marked as done (zfs-dkms 0.7.9-3 build fails on 4.18.0-1-amd64 cause spl-0.7.9 stuff)
Your message dated Wed, 19 Sep 2018 09:35:37 + with message-id and subject line Bug#908290: fixed in zfs-linux 0.7.11-1 has caused the Debian Bug report #908290, regarding zfs-dkms 0.7.9-3 build fails on 4.18.0-1-amd64 cause spl-0.7.9 stuff 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.) -- 908290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zfs-dkms Version: 0.7.9-3 Severity: normal Dear Maintainer, you are doing great work - thanks a lot for your effort and time! * What led up to the situation? apt-upgrade * What was the outcome of this action? Errmsgs: DKMS: install completed. Building initial module for 4.18.0-1-amd64 configure: error: *** Please make sure the kmod spl devel package for your *** distribution is installed then try again. If that fails you *** can specify the location of the spl objects with the *** '--with-spl-obj=PATH' option. Failed to find spl_config.h in *** any of the following: /usr/src/spl-0.7.9/4.18.0-1-amd64 /usr/src/spl-0.7.9 Error! Bad return status for module build on kernel: 4.18.0-1-amd64 (x86_64) Consult /var/lib/dkms/zfs/0.7.9/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 Processing triggers for hicolor-icon-theme (0.17-2) ... Errors were encountered while processing: zfs-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) tail -f /var/lib/dkms/zfs/0.7.9/build/make.log DKMS make.log for zfs-0.7.9 for kernel 4.18.0-1-amd64 (x86_64) Tue 18 Sep 14:14:55 CEST 2018 make: *** No targets specified and no makefile found. Stop. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (999, 'testing'), (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'oldoldstable-updates'), (103, 'unstable'), (102, 'stable'), (101, 'oldstable'), (100, 'oldoldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages zfs-dkms depends on: ii debconf [debconf-2.0] 1.5.69 ii dkms 2.6.1-1 ii lsb-release9.20170808 ii spl-dkms 0.7.9-3 Versions of packages zfs-dkms recommends: ii linux-libc-dev 4.18.6-1 ii zfs-zed 0.7.9-3 ii zfsutils-linux 0.7.9-3 zfs-dkms suggests no packages. -- debconf information: zfs-dkms/stop-build-for-32bit-kernel: true * zfs-dkms/note-incompatible-licenses: zfs-dkms/stop-build-for-unknown-kernel: true --- End Message --- --- Begin Message --- Source: zfs-linux Source-Version: 0.7.11-1 We believe that the bug you reported is fixed in the latest version of zfs-linux, 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 908...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mo Zhou (supplier of updated zfs-linux 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, 19 Sep 2018 08:45:18 + Source: zfs-linux Binary: libnvpair1linux libuutil1linux libzfslinux-dev libzfs2linux libzpool2linux zfs-dkms zfs-initramfs zfs-dracut zfsutils-linux zfs-zed zfs-test zfs-dbg Architecture: source Version: 0.7.11-1 Distribution: unstable Urgency: medium Maintainer: Debian ZFS on Linux maintainers Changed-By: Mo Zhou Description: libnvpair1linux - Solaris name-value library for Linux libuutil1linux - Solaris userland utility library for Linux libzfs2linux - OpenZFS filesystem library for Linux libzfslinux-dev - OpenZFS filesystem development files for Linux libzpool2linux - OpenZFS pool library for Linux zfs-dbg- Debugging symbols for OpenZFS userland libraries and tools zfs-dkms - OpenZFS filesystem kernel modules for Linux zfs-dracut - OpenZFS root filesystem capabilities for Linux -
Bug#909168: marked as done ([src:gforth] Installs the gforth package files into the wrong directory)
Your message dated Wed, 19 Sep 2018 09:34:26 + with message-id and subject line Bug#909168: fixed in gforth 0.7.3+dfsg-7 has caused the Debian Bug report #909168, regarding [src:gforth] Installs the gforth package files into the wrong 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.) -- 909168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debhelper Version: 11.4 Severity: serious Hi, Thanks for maintaining and extending debhelper! I don't have much information right now, maybe I'll look into it in the evening (Eastern European time), but trying to build gforth in a chroot containing debhelper-11.4 results in a package where all the paths passed to the GNU configure script as "\$prefix/something" are actually defined as "/something", thus placing binaries in /bin, include files in /include, etc. Installing debhelper-11.3.5 fixes the problem. Thanks again for everything you're doing for debhelper and Debian, and keep up the great work! G'luck, Peter -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), LANGUAGE=bg_BG.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages debhelper depends on: ii autotools-dev20180224.1 ii dh-autoreconf19 ii dh-strip-nondeterminism 0.042-1 ii dpkg 1.19.0.5+b1 ii dpkg-dev 1.19.0.5 ii dwz 0.12-2 ii file 1:5.34-2 ii libdpkg-perl 1.19.0.5 ii man-db 2.8.4-2 ii perl 5.26.2-7 ii po-debconf 1.0.20 debhelper recommends no packages. Versions of packages debhelper suggests: pn dh-make -- no debconf information signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: gforth Source-Version: 0.7.3+dfsg-7 We believe that the bug you reported is fixed in the latest version of gforth, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 909...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Pentchev (supplier of updated gforth 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, 19 Sep 2018 12:04:22 +0300 Source: gforth Binary: gforth gforth-lib gforth-common Architecture: source Version: 0.7.3+dfsg-7 Distribution: unstable Urgency: medium Maintainer: Peter Pentchev Changed-By: Peter Pentchev Description: gforth - GNU Forth Language Environment gforth-common - GNU Forth architecture-independent dictionaries gforth-lib - GNU Forth Language Environment architecture-dependent files Closes: 909168 Changes: gforth (0.7.3+dfsg-7) unstable; urgency=medium . * Bring up to compliance with Debian Policy 4.2.1: install the upstream release notes (NEWS) as NEWS and not changelog; do not install the detailed upstream changelog at all. * Drop the Lintian overrides related to B-D: debhelper-compat - Lintian 2.5.98 no longer emits these warnings and errors. * Add Lintian overrides for the README files in the GForth library. * Install the gforth package files into the correct build directory in the override_dh_install target, thus fixing a long-standing bug exposed by a recent change in debhelper. Closes: #909168 Checksums-Sha1: bdca0496569095eb8317fab4233b251a053c08d1 2096 gforth_0.7.3+dfsg-7.dsc 1746ae7f6c9e01b6ba172826e3b1fa9a8b9377d3 40868 gforth_0.7.3+dfsg-7.debian.tar.xz a4a41535d8f54d6e34f0f047b471b475998e264b 6792 gforth_0.7.3+dfsg-7_amd64.buildinfo Checksums-Sha256: c0e9e34a2b0f7be77437c4fb988b815e776326ff6876e384e2cb57fc8aabb951 2096 gforth_0.7.3+dfsg-7.dsc e36eb9c8baf569fa4be4481943c28f696ff9256c71fdd4f7f818881c3b3cc0df 40868 gforth_0.7.3+dfsg-7.debian.tar.xz
Processed: severity of 909177 is serious
Processing commands for cont...@bugs.debian.org: > severity 909177 serious Bug #909177 [snapper-gui] snapper-gui should depend on snapper otherwise it crashes at start Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 909177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909177 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905706: marked as done (libpicard-java-doc: ships /usr/share/javascript/jquery/jquery.min.js)
Your message dated Wed, 19 Sep 2018 09:05:32 + with message-id and subject line Bug#905706: fixed in picard-tools 2.18.14+dfsg-1 has caused the Debian Bug report #905706, regarding libpicard-java-doc: ships /usr/share/javascript/jquery/jquery.min.js 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.) -- 905706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpicard-java-doc Version: 2.18.2+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package libpicard-java-doc. Preparing to unpack .../libpicard-java-doc_2.18.2+dfsg-1_all.deb ... Unpacking libpicard-java-doc (2.18.2+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/libpicard-java-doc_2.18.2+dfsg-1_all.deb (--unpack): trying to overwrite '/usr/share/javascript/jquery/jquery.min.js', which is also in package libjs-jquery 3.2.1-1 Errors were encountered while processing: /var/cache/apt/archives/libpicard-java-doc_2.18.2+dfsg-1_all.deb cheers, Andreas libjs-jquery=3.2.1-1_libpicard-java-doc=2.18.2+dfsg-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: picard-tools Source-Version: 2.18.14+dfsg-1 We believe that the bug you reported is fixed in the latest version of picard-tools, 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 905...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated picard-tools 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, 19 Sep 2018 09:20:48 +0200 Source: picard-tools Binary: picard-tools libpicard-java libpicard-java-doc Architecture: source Version: 2.18.14+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: libpicard-java - Java library to manipulate SAM and BAM files libpicard-java-doc - Documentation for the java picard library picard-tools - Command line tools to manipulate SAM and BAM files Closes: 905706 Changes: picard-tools (2.18.14+dfsg-1) unstable; urgency=medium . * New upstream version * Standards-Version: 4.2.1 * Fix link Closes: #905706 * Versioned Build-Depends: libhtsjdk-java (>= 2.16.1~) * d/rules: Respect DEB_BUILD_OPTIONS in override_dh_auto_test * Simplified d/copyright by not mentioning every single file Checksums-Sha1: 1510dc363c8cac2fcd7c39688e45aa713886504a 2677 picard-tools_2.18.14+dfsg-1.dsc d71e83b42674a1b70b61670f87799f499ef190b5 20570188 picard-tools_2.18.14+dfsg.orig.tar.xz c3a560003a54bb14c03864493847807403c54c43 15052 picard-tools_2.18.14+dfsg-1.debian.tar.xz Checksums-Sha256: 599525be1a9e3e3ed09d0c4986fbcc6593dcb72c1a0e9f9b377b760f3aaca397 2677 picard-tools_2.18.14+dfsg-1.dsc 8e93da3319403f1af5a332188fe79195fafcb9bc5a939bf6304040b4feba6631 20570188 picard-tools_2.18.14+dfsg.orig.tar.xz fe0daac0888baa5cffaef0c438342bbf73bb3ecd77c263cb7f41b05737c738d9 15052 picard-tools_2.18.14+dfsg-1.debian.tar.xz Files: bb81928b2708a32cd84e6d0e9f41517a 2677 science optional picard-tools_2.18.14+dfsg-1.dsc e91cef83461050857a4139503f982f2d 20570188 science optional picard-tools_2.18.14+dfsg.orig.tar.xz 2179667b75d6d78b124624fdf96e4d66 15052 science optional picard-tools_2.18.14+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAluiCy4RHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtF39g//S+/KYVozRTGLjecu1SYK+e3bAPSY5JAz 10KT8JAX4h/9xVjvoPL0NySfeZ3v4uk6mU4CgsyeNI3v7s9GLxiIiY9sHvatM1Tu phXiAuhIrtWDoHwg4DBsdTeQdcgR+ueSMI72AKiBoVuMx8jqqp/Gw4UPP9JOF0Uy bdyuBNVC0DAuDyR5sWWqEi2TRSRVMQQKrOzDb21ASf7EZUk6uQNHK9bM5/EM7353 VfzI+n+z69AXgmRvQzaCh1U+8pafc9R3neD+Chc6EoICIaXMCO+A+KYNn5GPma2l sXULHMOeUhHbQlt+oZvNYvvbsigokRknTjerU7DmN2VjVnTOBjY3rxNP9zxvoCsy PuLaEIeuMKu9hyOfSCbPJGmlevuhDhwUR6yTg8sMCirSsyzitLg8hClYk6NFQGQB
Processed: tagging 909168
Processing commands for cont...@bugs.debian.org: > tags 909168 + buster sid Bug #909168 [src:gforth] [src:gforth] Installs the gforth package files into the wrong directory Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 909168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#908955: marked as done (/usr/lib/libglide3.so.3: undefined symbol: __LINE__)
Your message dated Wed, 19 Sep 2018 09:04:43 + with message-id and subject line Bug#908955: fixed in glide 2002.04.10ds1-14 has caused the Debian Bug report #908955, regarding /usr/lib/libglide3.so.3: undefined symbol: __LINE__ 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.) -- 908955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libglide3 Version: 2002.04.10ds1-12 Severity: grave I known no one has such a card to test it, but I've just got one compiling xdraw3.o with -fdollars-in-identifiers causes __LINE__ to became an undefined symbol even if specifying -x assembler-with-cpp because is used as $__LINE__ -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libglide3 depends on: ii debconf [debconf-2.0] 1.5.69 ii libc6 2.27-6 ii libx11-6 2:1.6.6-1 ii libxext6 2:1.3.3-1+b2 ii libxxf86dga1 2:1.1.4-1+b3 ii libxxf86vm11:1.1.4-1+b2 pn pciutils libglide3 recommends no packages. libglide3 suggests no packages. --- End Message --- --- Begin Message --- Source: glide Source-Version: 2002.04.10ds1-14 We believe that the bug you reported is fixed in the latest version of glide, 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 908...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guillem Jover (supplier of updated glide 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, 19 Sep 2018 09:34:51 +0200 Source: glide Binary: glide2-bin libglide2 libglide2-dev libglide3 libglide3-dev Architecture: source Version: 2002.04.10ds1-14 Distribution: unstable Urgency: medium Maintainer: Guillem Jover Changed-By: Guillem Jover Description: glide2-bin - graphics library for 3Dfx Voodoo 2 based cards - support programs libglide2 - graphics library for 3Dfx Voodoo 2 based cards - shared libraries libglide2-dev - graphics library for 3Dfx Voodoo 2 based cards - development file libglide3 - graphics library for 3Dfx Voodoo 3+ based cards - shared librarie libglide3-dev - graphics library for 3Dfx Voodoo 3+ based cards - development fil Closes: 908955 Changes: glide (2002.04.10ds1-14) unstable; urgency=medium . * Sort fields in debian/control and debian/copyright. * Do not consider dollar signs as part of the symbol names in assembler code, thus getting rid of non-existing unresolvable inserted symbols. (Closes: #908955) - debian/patches/glide3x-link-unresolved: Update patch. - debian/patches/z12-local-libtool: Likewise. * Fix installation permissions to always set write rights for the owner, so that we can build without root, as fakeroot was shadowing these issues. - debian/patches/z13-install-perms: New patch. * Set R³ to no. * Bump Standards-Version to 4.2.1 (no changes needed). * Bump debhelper compatibility level to 11. * Update copyright years. * Add Comment field in debian/copyright describing why the source tarball was repackaged. * Fix building twice in a row by removing autoconf cruft via debian/clean. Checksums-Sha1: ecea031d0b097280500c328523ac6f67f9ff3c0c 2243 glide_2002.04.10ds1-14.dsc 7bb040f7d791e7ecbb66eda7e621f3c1cc24e5ff 79904 glide_2002.04.10ds1-14.debian.tar.xz 6c856b82819d3436de55217f9f13284478833596 8043 glide_2002.04.10ds1-14_i386.buildinfo Checksums-Sha256: 5038be9d17508df3370b7bd4c16ce68752a8063c9b5402be44d19af663b58380 2243 glide_2002.04.10ds1-14.dsc 1f2b3448cac8237c6b190136882a9a37f8bba64cd9ada21388645266f73da4cd 79904 glide_2002.04.10ds1-14.debian.tar.xz d09b743ca07fd2bc5cf8ee5006f0da9bc8625154e8dac84ef2b293d8b204c5c8 8043 glide_2002.04.10ds1-14_i386.buildinfo Files: b2cbb27aa31777ba0c609611533bb7c3 2243 libs optional
Processed: libepoxy-dev: New pkg-config dependencies that are not package dependencies
Processing control commands: > affects -1 src:goffice Bug #909173 [libepoxy-dev] libepoxy-dev: New pkg-config dependencies that are not package dependencies Added indication that 909173 affects src:goffice -- 909173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909173: libepoxy-dev: New pkg-config dependencies that are not package dependencies
Package: libepoxy-dev Version: 1.5.2-0.1 Severity: serious Control: affects -1 src:goffice https://buildd.debian.org/status/package.php?p=goffice ... checking for GTK... no configure: error: Package requirements ( gtk+-3.0>= 3.8.7 ) were not met: Package 'gl', required by 'epoxy', not found
Bug#908648: marked as done (libarpack2 needs fix applied for igraph)
Your message dated Wed, 19 Sep 2018 08:34:29 + with message-id and subject line Bug#908648: fixed in arpack 3.6.3-1 has caused the Debian Bug report #908648, regarding libarpack2 needs fix applied for igraph 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.) -- 908648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libarpack2 Version: 3.6.0-1 Severity: serious Tags: fixed-upstream Forwarded: https://github.com/opencollab/arpack-ng/issues/142 Control: block #902760 by -1 libarpack2 needs this fix applied for igraph. If required I can do an NMU. --- End Message --- --- Begin Message --- Source: arpack Source-Version: 3.6.3-1 We believe that the bug you reported is fixed in the latest version of arpack, 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 908...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated arpack 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, 19 Sep 2018 10:05:11 +0200 Source: arpack Binary: libarpack2 libarpack2-dev libparpack2 libparpack2-dev Architecture: source Version: 3.6.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Sylvestre Ledru Description: libarpack2 - Fortran77 subroutines to solve large scale eigenvalue problems libarpack2-dev - Fortran77 subroutines to solve large scale eigenvalue problems (d libparpack2 - Parallel subroutines to solve large scale eigenvalue problems libparpack2-dev - Parallel subroutines to solve large scale eigenvalue problems (de Closes: 908648 Changes: arpack (3.6.3-1) unstable; urgency=medium . * New upstream release fix a regression with dnaupd (Closes: #908648) * Standards-Version: 4.2.1 Checksums-Sha1: 13c1ba2c7a5ecf26df1ef6460b026fa16a83342f 2147 arpack_3.6.3-1.dsc f6dac662159529dec2319c08a1a75f8ff6ae2601 970355 arpack_3.6.3.orig.tar.gz ea695fdd93b8974aec3405f2ea3557b08320c6ed 8584 arpack_3.6.3-1.debian.tar.xz 24b21d374484b907238174ff483ecb4a51abd9b4 8325 arpack_3.6.3-1_amd64.buildinfo Checksums-Sha256: 6e40caf7d5f86f5b0dd1019c665708324c965c026b405fc3fab7c895d73642d0 2147 arpack_3.6.3-1.dsc 64f3551e5a2f8497399d82af3076b6a33bf1bc95fc46bbcabe66442db366f453 970355 arpack_3.6.3.orig.tar.gz 12a83bbca191031732dbdb294bb225395af7697cf11a1578a8eb759f9f836552 8584 arpack_3.6.3-1.debian.tar.xz cd099da21b51e2e0cba76b60395df2490860ab4a570f966b647674261b7a335a 8325 arpack_3.6.3-1_amd64.buildinfo Files: 1150bdb8281926ba826dc6fb686c4134 2147 math optional arpack_3.6.3-1.dsc a159a998d1805e18a68ca1995f79a245 970355 math optional arpack_3.6.3.orig.tar.gz 75314da677850ccd5bb5ebeae497b331 8584 math optional arpack_3.6.3-1.debian.tar.xz eec660b18ebac5c55f10afb06f17b345 8325 math optional arpack_3.6.3-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAluiBpQACgkQfmUo2nUv G+FqpQ//aXvW+HQjeIZLpFRXbzRglkcPQGzquxMVU5UCVHomMR6wEwkN+82ZrP04 JIhyl+a5Qo/ioBbkJlUG8WSoKfVcdS4kzDpY5EMIPWi3g841zTY6ko8PKfRqjirl vbgDw54GueLqk/AQptmih/hfWl2LAM0v0uz6DCoPpJzwmEtX3NLV4m6/z3TjQViw plxwzBm1xMUGz6MKsGoVgV+OF1erY6uEIJ6Ct0a68MX2SiXogamO2E7HoZ9UwOBC ZTun58Z5TAnUnftrpuGRmzcC9X9XnmBsXUEFbqIhOx/OkM6r+B6C9iA4cDzVOelt ZA5Ynh7rBcrqAXyY35QQFuow/dHHXMvi7f/cnT7QaoPkWpDLFxuOky+h2ruoY6jW 2coTSieCjtD3V6xsihMp0CQQpVpBM/YpifDPR/spwXdh8xviHVIXnZZ3K6fQqyT7 +QnIXS8+Q8+wzzUHd/hgXqt0QINU102GCJFJt//CkDoafucD+uQmIZQyd/2k9oLZ ZqzxvyOPQ/OXLL5jrt0xCsNsO/NH7qo8yO79b1ae5UyHJGCRehfCwTPyN/Om3Hqz 12U3qoov5B50GWtRogYkoeUsnn0HOkcEf1ShPkXjoxjgZHiCLup8QHTZw2bioe72 oeFogJJPV4/8gRJnhq9DsJkas+QZ5xQO6ean/+7Bykcf0M6RLBI= =1dFM -END PGP SIGNATURE End Message ---
Bug#909000: Workarround
As a workarround you can install gnupg from backports and enigmail from testing. I guess Daniel will also backport Enigmail 2.0.8 now it's in testing. -- Paul van der Vlis Linux systeembeheer Groningen https://www.vandervlis.nl/
Processed: Re: Bug#909089: debhelper: GNU configure $prefix expanded too early?
Processing commands for cont...@bugs.debian.org: > clone 909089 -1 Bug #909089 [debhelper] debhelper: GNU configure $prefix expanded too early? Bug 909089 cloned as bug 909168 > notfound -1 11.4 Bug #909168 [debhelper] debhelper: GNU configure $prefix expanded too early? No longer marked as found in versions debhelper/11.4. > reassign -1 src:gforth Bug #909168 [debhelper] debhelper: GNU configure $prefix expanded too early? Bug reassigned from package 'debhelper' to 'src:gforth'. Ignoring request to alter found versions of bug #909168 to the same values previously set Ignoring request to alter fixed versions of bug #909168 to the same values previously set > retitle -1 [src:gforth] Installs the gforth package files into the wrong > directory Bug #909168 [src:gforth] debhelper: GNU configure $prefix expanded too early? Changed Bug title to '[src:gforth] Installs the gforth package files into the wrong directory' from 'debhelper: GNU configure $prefix expanded too early?'. > found -1 0.7.3+dfsg-1 Bug #909168 [src:gforth] [src:gforth] Installs the gforth package files into the wrong directory Marked as found in versions gforth/0.7.3+dfsg-1. > severity 909089 minor Bug #909089 [debhelper] debhelper: GNU configure $prefix expanded too early? Severity set to 'minor' from 'serious' > retitle 909089 [debhelper] Actually exposes long-standing bugs in source > packages Bug #909089 [debhelper] debhelper: GNU configure $prefix expanded too early? Changed Bug title to '[debhelper] Actually exposes long-standing bugs in source packages' from 'debhelper: GNU configure $prefix expanded too early?'. > thanks Stopping processing here. Please contact me if you need assistance. -- 909089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909089 909168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909089: debhelper: GNU configure $prefix expanded too early?
clone 909089 -1
notfound -1 11.4
reassign -1 src:gforth
retitle -1 [src:gforth] Installs the gforth package files into the wrong
directory
found -1 0.7.3+dfsg-1
severity 909089 minor
retitle 909089 [debhelper] Actually exposes long-standing bugs in source
packages
thanks
On Wed, Sep 19, 2018 at 06:15:00AM +, Niels Thykier wrote:
> Sven Joachim:
> > On 2018-09-18 14:09 +0300, Peter Pentchev wrote:
> >
> >> Package: debhelper
> >> Version: 11.4
> >> Severity: serious
> >>
> >> Hi,
> >>
> >> Thanks for maintaining and extending debhelper!
> >>
> >> I don't have much information right now, maybe I'll look into it in
> >> the evening (Eastern European time), but trying to build gforth in
> >> a chroot containing debhelper-11.4 results in a package where all
> >> the paths passed to the GNU configure script as "\$prefix/something"
> >> are actually defined as "/something", thus placing binaries in /bin,
> >> include files in /include, etc. Installing debhelper-11.3.5 fixes
> >> the problem.
> >
> > Bisection shows that commit a7ec05c10093f ("dh: Track which options have
> > been passed") has triggered the problem. I had a look at the gforth
> > build logs with debhelper 11.3.5 and 11.4, but could not spot an obvious
> > cause. Maybe Niels has more luck.
> >
> > Cheers,
> >Sven
Thanks a lot for taking the time to look into this! However, see below...
>
> Hi,
>
> @Sven: Thanks for bisecting it. FTR, which version of gforth did you
> test with?
[snip]
> @Peter: Could you try to add a "dh_installdirs" (or mkdir -p $(DG)/)
> before the following line?
>
> mv /<>/debian/tmp/* /<>/debian/gforth/
Of course you are right... :)
Actually the "culprit" was b4d25f15, "dh: Remove broken (and obsolete)
compat item" - the change that dropped the "create package build dirs if
a command is skipped" functionality and, well, exposed bugs in source
packages that depended on it.
My bad; I do make a point of reading the "vXX" notes in the debhelper
manual page before I bump the compat level of each of my packages and
thinking whether any of these affect the package in question, and I
guess I did not realize that this change really affects
gforth-0.7.3+dfsg-1 where I bumped the compat level to 10 *immediately
after* introducing the "install into the temp directory and then move
files to the actual package build dirs if needed so that we can properly
build both arch-indep and arch-dep packages". It really was immediately
afterwards... and I completely missed it. Of course, it didn't break
back then, but that's no excuse :)
Sorry for raising a serious bug, and thanks A LOT for taking a look at
it quickly and figuring out what the problem was! Feel free to close
this bug, since it is really not a bug in debhelper, but in any other
source packages; of course, feel free to also use it as reference if
anybody else comes screaming "debhelper 11.4 broke my package and I did
not change anything, I swear!" :)
So, yeah, thanks again to everyone who chimed in, sorry for the
confusion, and keep up the great work!
G'luck,
Peter
--
Peter Pentchev roam@{ringlet.net,debian.org,FreeBSD.org} p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
signature.asc
Description: PGP signature
Processed: Re: Bug#909155: apt-cache show multiple packages produces invalid output
Processing control commands: > tag -1 confirmed Bug #909155 [apt] apt-cache show multiple packages produces invalid output Added tag(s) confirmed. -- 909155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909155: apt-cache show multiple packages produces invalid output
Control: tag -1 confirmed On Wed, Sep 19, 2018 at 07:01:29AM +0200, Helmut Grohne wrote: > Package: apt > Version: 1.7.0~rc1 > Severity: serious > File: /usr/bin/apt-cache > > If you do a fresh sid debootstrap and then you can get the following > interaction: > > $ apt-cache show gcc-8-base=installed libgcc1=installed > Package: gcc-8-base [...] > Package: libgcc1 [...] > Package: libx32gomp1-dbg [...] git bisect says bf53f39c9a0221b67074053ed36fc502d5a0 is the first bad commit commit bf53f39c9a0221b67074053ed36fc502d5a0 Author: David Kalnischkies Date: Wed Apr 11 12:59:06 2018 +0200 Support --with-source in show & search commands This changed how show worked, so it's a fairly isolated problem. > I'm filing this at severity serious, because I think it is the tip of an > iceberg. The rc severity will prevent apt-listbugs users from installing > to leave time for investigation. Please downgrade the severity once the > problem is understood to be harmless. > We've been running 1.7.y in Ubuntu with this commit since June, and not noticed the problem. It's a problem strictly in show. That said, I don't want that to be broken in testing either, so I'll leave it as RC. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Processed: bug 908686 is forwarded to https://github.com/pimutils/todoman/issues/324
Processing commands for cont...@bugs.debian.org: > forwarded 908686 https://github.com/pimutils/todoman/issues/324 Bug #908686 [src:todoman] todoman FTBFS with python-click 6.7+git20180829-1 Set Bug forwarded-to-address to 'https://github.com/pimutils/todoman/issues/324'. > thanks Stopping processing here. Please contact me if you need assistance. -- 908686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908686 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 863039 is serious
Processing commands for cont...@bugs.debian.org:
> severity 863039 serious
Bug #863039 {Done: Adrian Bunk } [libwvstreams4.6-base]
libwvstreams4.6-base: wvdial crashes with Assertion `*current_task->stack_magic
== WVTASK_MAGIC' failed
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
863039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#909094: gnome-shell-extension-workspaces-to-dock: Version 48 with gnome-shell 3.28 makes the Desktop unusable
Hello, > The way forward for Kali might be to just push glib2.0, gnome-shell, > mutter, and gnome-shell-extensions to Testing early. I fixed the issue for Kali by forking the package and reverting last changes. > As long as we can get glib to build on armel, all these should land in > Testing in a couple days. Yes I noticed that but I thought I had to report anyway this (very annoying) bug. I hope Gnome Shell will migrate quickly. Thanks Sophie
Bug#909161: hylafax: CVE-2018-17141
Source: hylafax Version: 3:6.0.6-1 Severity: grave Tags: patch security upstream Control: fixed -1 3:6.0.6-7+deb9u1 Hi, The following vulnerability was published for hylafax: CVE-2018-17141[0]. Fix commited as [1]. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-17141 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17141 [1] http://git.hylafax.org/HylaFAX?a=commit;h=82fa7bdbffc253de4d3e80a87d47fdbf68eabe36 Regards, Salvatore
Processed: hylafax: CVE-2018-17141
Processing control commands: > fixed -1 3:6.0.6-7+deb9u1 Bug #909161 [src:hylafax] hylafax: CVE-2018-17141 The source 'hylafax' and version '3:6.0.6-7+deb9u1' do not appear to match any binary packages Marked as fixed in versions hylafax/3:6.0.6-7+deb9u1. -- 909161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909161 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909089: debhelper: GNU configure $prefix expanded too early?
Sven Joachim:
> On 2018-09-18 14:09 +0300, Peter Pentchev wrote:
>
>> Package: debhelper
>> Version: 11.4
>> Severity: serious
>>
>> Hi,
>>
>> Thanks for maintaining and extending debhelper!
>>
>> I don't have much information right now, maybe I'll look into it in
>> the evening (Eastern European time), but trying to build gforth in
>> a chroot containing debhelper-11.4 results in a package where all
>> the paths passed to the GNU configure script as "\$prefix/something"
>> are actually defined as "/something", thus placing binaries in /bin,
>> include files in /include, etc. Installing debhelper-11.3.5 fixes
>> the problem.
>
> Bisection shows that commit a7ec05c10093f ("dh: Track which options have
> been passed") has triggered the problem. I had a look at the gforth
> build logs with debhelper 11.3.5 and 11.4, but could not spot an obvious
> cause. Maybe Niels has more luck.
>
> Cheers,
>Sven
>
Hi,
@Sven: Thanks for bisecting it. FTR, which version of gforth did you
test with?
@Both: I checked the configure lines and they are identical
(bit-for-bit) in the log, so we are probably looking for something
different.
I have compared the build logs from Peter with the amd64 build on the
buildds (with some messaging) and I do not see any obvious problems (I
assume the differences shown are due to -6 vs. -7).
"""
Generated the files with:
grep dh_ \
| grep -v 'The use of "debhelper-compat (= 11)" is experimental' \
| sed 's/-a //'
--- dh_broken.log 2018-09-19 08:00:04.640018651 +0200
+++ dh_ok.log 2018-09-19 08:00:20.952018495 +0200
@@ -1,6 +1,5 @@
debian/rules override_dh_auto_clean
dh_auto_clean
- dh_autoreconf_clean -O--no-parallel
dh_clean -O--no-parallel
dh_update_autotools_config -O--no-parallel
dh_autoreconf -O--no-parallel
@@ -15,8 +14,7 @@
debian/rules override_dh_install
dh_installdocs -O--no-parallel
debian/rules override_dh_installchangelogs
-dh_installchangelogs -X ChangeLog
-set -e; for p in $(dh_listpackages); do \
+dh_installchangelogs NEWS
dh_installman -O--no-parallel
dh_installemacsen -O--no-parallel
dh_lintian -O--no-parallel
"""
The dh_autoreconf_clean omission is expected (dh-autoreconf made it
optional so we could avoid calling it in the initial clean where it is
always a no-op) and the remaining diffs looks like a change to the rules.
I also checked the make install part and both logs installs the files
into /<>/debian/tmp/usr/...
@Peter: Could you try to add a "dh_installdirs" (or mkdir -p $(DG)/)
before the following line?
mv /<>/debian/tmp/* /<>/debian/gforth/
https://sources.debian.org/src/gforth/0.7.3+dfsg-6/debian/rules/#L81
Thanks,
~Niels
