Bug#892131: Bug #892131 in gem2deb marked as pending
Control: tag -1 pending Hello, Bug #892131 in gem2deb 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/gem2deb/commit/de6337b52635ea581b8bf36e14db292c3716119f dh_ruby_fixdepends: don't add unneeded dependencies on ruby Closes: #892131 (this message was generated automatically) -- Greetings https://bugs.debian.org/892131
Processed: Bug #892131 in gem2deb marked as pending
Processing control commands: > tag -1 pending Bug #892131 [gem2deb] gem2deb: generates spurious dependencies on ruby Added tag(s) pending. -- 892131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893736: marked as done (glib2.0 FTBFS: ModuleNotFoundError: No module named 'distutils')
Your message dated Thu, 22 Mar 2018 04:49:40 + with message-id and subject line Bug#893736: fixed in glib2.0 2.56.0-3 has caused the Debian Bug report #893736, regarding glib2.0 FTBFS: ModuleNotFoundError: No module named 'distutils' 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.) -- 893736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glib2.0 Version: 2.56.0-2 Severity: serious User: helm...@debian.org Usertags: rebootstrap sbuild -d sid glib2.0 ends with: | Making all in gio | make[4]: Entering directory '/<>/debian/build/deb/gio' | UNINSTALLED_GLIB_SRCDIR=../../../.. \ | UNINSTALLED_GLIB_BUILDDIR=.. \ | /usr/bin/python3 ../../../../gio/gdbus-2.0/codegen/gdbus-codegen.in \ | --interface-prefix org. \ | --generate-c-code gdbus-daemon-generated \ | --c-namespace _G \ | ../../../../gio/dbus-daemon.xml \ | | Traceback (most recent call last): | File "../../../../gio/gdbus-2.0/codegen/gdbus-codegen.in", line 53, in | from codegen import codegen_main | File "/<>/gio/gdbus-2.0/codegen/codegen_main.py", line 29, in | from . import dbustypes | File "/<>/gio/gdbus-2.0/codegen/dbustypes.py", line 22, in | from . import utils | File "/<>/gio/gdbus-2.0/codegen/utils.py", line 22, in | import distutils.version | ModuleNotFoundError: No module named 'distutils' | make[4]: *** [Makefile:5019: gdbus-daemon-generated.c] Error 1 | make[4]: Leaving directory '/<>/debian/build/deb/gio' | make[4]: *** Waiting for unfinished jobs | make[4]: Entering directory '/<>/debian/build/deb/gio' | UNINSTALLED_GLIB_SRCDIR=../../../.. \ | UNINSTALLED_GLIB_BUILDDIR=.. \ | /usr/bin/python3 ../../../../gio/gdbus-2.0/codegen/gdbus-codegen.in \ | --interface-prefix org. \ | --generate-c-code gdbus-daemon-generated \ | --c-namespace _G \ | ../../../../gio/dbus-daemon.xml \ | | Traceback (most recent call last): | File "../../../../gio/gdbus-2.0/codegen/gdbus-codegen.in", line 53, in | from codegen import codegen_main | File "/<>/gio/gdbus-2.0/codegen/codegen_main.py", line 29, in | from . import dbustypes | File "/<>/gio/gdbus-2.0/codegen/dbustypes.py", line 22, in | from . import utils | File "/<>/gio/gdbus-2.0/codegen/utils.py", line 22, in | import distutils.version | ModuleNotFoundError: No module named 'distutils' | make[4]: *** [Makefile:5019: gdbus-daemon-generated.h] Error 1 | make[4]: Leaving directory '/<>/debian/build/deb/gio' | make[3]: *** [Makefile:1279: all-recursive] Error 1 | make[2]: *** [Makefile:900: all] Error 2 | dh_auto_build: cd debian/build/deb && make -j8 -O returned exit code 2 | make[1]: *** [debian/rules:137: override_dh_auto_build] Error 25 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:24: binary-arch] Error 2 | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 Possibly some dependency is missing? I guess this is connected to the python3.6/3.6.5~rc1-2 upload. Helmut --- End Message --- --- Begin Message --- Source: glib2.0 Source-Version: 2.56.0-3 We believe that the bug you reported is fixed in the latest version of glib2.0, 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 893...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bicha (supplier of updated glib2.0 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 22 Mar 2018 00:27:02 -0400 Source: glib2.0 Binary: libglib2.0-0 libglib2.0-tests libglib2.0-udeb libglib2.0-bin libglib2.0-dev libglib2.0-dev-bin libglib2.0-data libglib2.0-doc libgio-fam Architecture: source Version: 2.56.0-3 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bicha Description: libgio-fam - GLib Input, Output and Streaming Library (fam module) libglib2.0-0 - GLib library of C routines libglib2.0-bin - Programs for the GLib library libglib2.0-data - Common files for GLib library libglib2.0-dev - Development files for the GLib libr
Bug#893770: amide: Don't depend on libgnomecanvas
Source: amide Version: 1.0.5-10 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: libgnomecanvas oldlibs As announced [1], we do not intend to release Debian 10 "Buster" with libgnomecanvas, one of the old unmaintained libgnome libraries. Your package Build-Depends and Depends on this library. I apologize for not filing this bug earlier, alongside https://bugs.debian.org/868383 amide has one more old dependency: scrollkeeper. I can submit a patch for this later if you like. [1] https://lists.debian.org/debian-devel/2018/02/msg00169.html On behalf of the Debian GNOME team, Jeremy Bicha
Bug#893736: Bug #893736 in glib2.0 marked as pending
Control: tag -1 pending Hello, Bug #893736 in glib2.0 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/glib/commit/30660d46e4c7a2ad8495519bdc88acf5a143f9df releasing package glib2.0 version 2.56.0-3 Closes: #893736 (this message was generated automatically) -- Greetings https://bugs.debian.org/893736
Processed: Bug #893736 in glib2.0 marked as pending
Processing control commands: > tag -1 pending Bug #893736 [src:glib2.0] glib2.0 FTBFS: ModuleNotFoundError: No module named 'distutils' Ignoring request to alter tags of bug #893736 to the same tags previously set -- 893736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug #893736 in glib2.0 marked as pending
Processing control commands: > tag -1 pending Bug #893736 [src:glib2.0] glib2.0 FTBFS: ModuleNotFoundError: No module named 'distutils' Added tag(s) pending. -- 893736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893736: Bug #893736 in glib2.0 marked as pending
Control: tag -1 pending Hello, Bug #893736 in glib2.0 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/glib/commit/30660d46e4c7a2ad8495519bdc88acf5a143f9df releasing package glib2.0 version 2.56.0-3 Closes: #893736 (this message was generated automatically) -- Greetings https://bugs.debian.org/893736
Processed: monotone-viz: Raising severity of libgnomecanvas dependency bug
Processing control commands: > severity -1 serious Bug #885782 [src:monotone-viz] monotone-viz: Depends on libgnomecanvas Severity set to 'serious' from 'important' -- 885782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: swami: Raising severity of libgnomecanvas dependency bug
Processing control commands: > severity -1 serious Bug #885778 [src:swami] swami: Depends on libgnomecanvas Severity set to 'serious' from 'important' -- 885778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: petri-foo: Raising severity of libgnomecanvas dependency bug
Processing control commands: > severity -1 serious Bug #885781 [src:petri-foo] petri-foo: Depends on libgnomecanvas Severity set to 'serious' from 'important' -- 885781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: etherape: Raising severity of libgnomecanvas dependency bug
Processing control commands: > severity -1 serious Bug #885796 [src:etherape] etherape: Depends on libgnomecanvas Severity set to 'serious' from 'important' -- 885796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: liblablgtksourceview2-ocaml: Raising severity of libgnome related dependency bug
Processing control commands: > severity -1 serious Bug #885677 [liblablgtksourceview2-ocaml] liblablgtksourceview2-ocaml: Depends on unmaintainted gtksourceview2 Severity set to 'serious' from 'important' -- 885677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885677 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893768: eclipse-rcp: Please don't depend on libswt-webkit-gtk-3-jni
Package: eclipse-rcp Version: 3.8.1-11 Severity: serious Tags: buster sid User: pkg-webkit-maintain...@lists.alioth.debian.org Usertags: oldlibs libwebkitgtk-1.0-0 webkit1 eclipse-rcp depends on libswt-webkit-gtk-3-jni which is the last package keeping the unmaintained webkitgtk in Debian Testing. Please investigate whether it's possible to drop this dependency. I'm guessing it's still possible for apps to use the Eclipse platform without that library: it's just that web browser powered widgets won't work? On behalf of the Debian Webkit Maintainers, Jeremy Bicha
Processed: Re: bc: Exhausts process table during build
Processing control commands: > severity -1 serious Bug #889176 [src:bc] bc: Exhausts process table during build Severity set to 'serious' from 'important' > tags -1 + patch Bug #889176 [src:bc] bc: Exhausts process table during build Added tag(s) patch. -- 889176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893761: java-propose-classpath still depends on gcj-jdk
Package: java-propose-classpath Version: 0.62 Severity: serious Tags: sid buster GCJ is now removed in unstable. Please stop depending on gcj-jdk, and consider using default-jdk as a dependency.
Processed: fixed but had to remove earlier version
Processing commands for cont...@bugs.debian.org: > fixed 893751 2.2.1 Bug #893751 [libqalculate14] libqalculate14: dpkg error, cannot overwrite libqalculate.mo which are both in libqalculate14 and libqalculate14-data There is no source info for the package 'libqalculate14' at version '2.2.1' with architecture '' Unable to make a source version for version '2.2.1' Ignoring request to alter fixed versions of bug #893751 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 893751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893751: fixed but had to remove earlier version
fixed 893751 2.2.1
thanks
Dear all,
What had happened is that I had taken the binaries from Vincent's
personal repo. at https://people.debian.org/~vlegout/qalc/ and due to
that was facing the issue.
When I removed/purged the binaries from Vincent's repo. and installed
the ones from experimental, the issue disappeared.
$ sudo aptitude purge qalculate qalculate-gtk
[sudo] password for shirish:
Sorry, try again.
[sudo] password for shirish:
Package qalculate is not installed, so it will not be purged
Package qalculate is not installed, so it will not be purged
The following packages will be REMOVED:
qalculate-gtk{p}
The following partially installed packages will be configured:
libqalculate14{b}
0 packages upgraded, 0 newly installed, 1 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 3,837 kB will be freed.
The following packages have unmet dependencies:
libqalculate14 : Depends: libqalculate14-data but it is not going to
be installed
The following actions will resolve these dependencies:
Install the following packages:
1) libqalculate14-data [2.2.1-1 (experimental)]
Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:
Remove the following packages:
1) libqalculate14 [2.2.1-1 (experimental, now)]
2) qalc [2.2.1-1 (experimental, now)]
Accept this solution? [Y/n/q/?] y
The following packages will be REMOVED:
libqalculate14{a} qalc{a} qalculate-gtk{p}
0 packages upgraded, 0 newly installed, 3 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 6,889 kB will be freed.
Do you want to continue? [Y/n/?] y
(Reading database ... 175218 files and directories currently installed.)
Removing qalculate-gtk (2.2.1-1) ...
Removing qalc (2.2.1-1) ...
Removing libqalculate14:amd64 (2.2.1-1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for desktop-file-utils (0.23-2) ...
Processing triggers for libc-bin (2.27-2) ...
Processing triggers for man-db (2.8.2-1) ...
== How can you help? (doc: https://wiki.debian.org/how-can-i-help ) ==
- Show old opportunities as well as new ones: how-can-i-help --old -
Current status: 0 (-1) broken.
I removed/purged all the libqalculate 'oldish' binaries from Vincent's
personal repo. and replaced them with the ones from experimental.
shirish@debian:~$ aptitude search libqalculate
p libqalculate-dev - Powerful
and easy to use desktop calculator - development
i libqalculate-doc - Powerful
and easy to use desktop calculator - documentation
i libqalculate14 - Powerful
and easy to use desktop calculator - library
i A libqalculate14-data - Powerful
and easy to use desktop calculator - data
p libqalculate14-dbgsym- debug
symbols for libqalculate14
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
Processed (with 5 errors): fixed but had to remove earlier version
Processing commands for cont...@bugs.debian.org: > fixed 893751 2.2.1 Bug #893751 [libqalculate14] libqalculate14: dpkg error, cannot overwrite libqalculate.mo which are both in libqalculate14 and libqalculate14-data There is no source info for the package 'libqalculate14' at version '2.2.1' with architecture '' Unable to make a source version for version '2.2.1' Marked as fixed in versions 2.2.1. > Dear all, Unknown command or malformed arguments to command. > What had happened is that I had taken the binaries from Vincent's Unknown command or malformed arguments to command. > personal repo. at https://people.debian.org/~vlegout/qalc/ and due to Unknown command or malformed arguments to command. > that was facing the issue. Unknown command or malformed arguments to command. > When I removed/purged the binaries from Vincent's repo. and installed Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. -- 893751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893751: fixed but had to remove earlier version
fixed 893751 2.2.1
Dear all,
What had happened is that I had taken the binaries from Vincent's
personal repo. at https://people.debian.org/~vlegout/qalc/ and due to
that was facing the issue.
When I removed/purged the binaries from Vincent's repo. and installed
the ones from experimental, the issue disappeared.
$ sudo aptitude purge qalculate qalculate-gtk
[sudo] password for shirish:
Sorry, try again.
[sudo] password for shirish:
Package qalculate is not installed, so it will not be purged
Package qalculate is not installed, so it will not be purged
The following packages will be REMOVED:
qalculate-gtk{p}
The following partially installed packages will be configured:
libqalculate14{b}
0 packages upgraded, 0 newly installed, 1 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 3,837 kB will be freed.
The following packages have unmet dependencies:
libqalculate14 : Depends: libqalculate14-data but it is not going to
be installed
The following actions will resolve these dependencies:
Install the following packages:
1) libqalculate14-data [2.2.1-1 (experimental)]
Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:
Remove the following packages:
1) libqalculate14 [2.2.1-1 (experimental, now)]
2) qalc [2.2.1-1 (experimental, now)]
Accept this solution? [Y/n/q/?] y
The following packages will be REMOVED:
libqalculate14{a} qalc{a} qalculate-gtk{p}
0 packages upgraded, 0 newly installed, 3 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 6,889 kB will be freed.
Do you want to continue? [Y/n/?] y
(Reading database ... 175218 files and directories currently installed.)
Removing qalculate-gtk (2.2.1-1) ...
Removing qalc (2.2.1-1) ...
Removing libqalculate14:amd64 (2.2.1-1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for desktop-file-utils (0.23-2) ...
Processing triggers for libc-bin (2.27-2) ...
Processing triggers for man-db (2.8.2-1) ...
== How can you help? (doc: https://wiki.debian.org/how-can-i-help ) ==
- Show old opportunities as well as new ones: how-can-i-help --old -
Current status: 0 (-1) broken.
I removed/purged all the libqalculate 'oldish' binaries from Vincent's
personal repo. and replaced them with the ones from experimental.
shirish@debian:~$ aptitude search libqalculate
p libqalculate-dev - Powerful
and easy to use desktop calculator - development
i libqalculate-doc - Powerful
and easy to use desktop calculator - documentation
i libqalculate14 - Powerful
and easy to use desktop calculator - library
i A libqalculate14-data - Powerful
and easy to use desktop calculator - data
p libqalculate14-dbgsym- debug
symbols for libqalculate14
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
Bug#893755: python3.6: Dropped python3-distutils dependency makes hundreds of packages FTBFS
Source: python3.6 Version: 3.6.5~rc1-2 Severity: serious This version of python3.6 dropped the dependency on python3-distutils. This causes hundreds of packages to fail to build from source. Therefore, let's delay its migration to Testing to give time for more packages to be fixed. Thanks, Jeremy Bicha
Bug#893751: libqalculate14: dpkg error, cannot overwrite libqalculate.mo which are both in libqalculate14 and libqalculate14-data
Package: libqalculate14 Version: 2.2.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, I tried to install the new package from experimental, got the following - ~$ sudo aptitude install libqalculate14-data The following NEW packages will be installed: libqalculate14-data The following partially installed packages will be configured: libqalculate14 0 packages upgraded, 1 newly installed, 0 to remove and 1 not upgraded. Need to get 0 B/133 kB of archives. After unpacking 786 kB will be used. Retrieving bug reports... Done Parsing Found/Fixed information... Done (Reading database ... 175218 files and directories currently installed.) Preparing to unpack .../libqalculate14-data_2.2.1-1_all.deb ... Unpacking libqalculate14-data (2.2.1-1) ... dpkg: error processing archive /var/cache/apt/archives/libqalculate14-data_2.2.1-1_all.deb (--unpack): trying to overwrite '/usr/share/locale/fr/LC_MESSAGES/libqalculate.mo', which is also in package libqalculate-data 2.2.1-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libqalculate14-data_2.2.1-1_all.deb == How can you help? (doc: https://wiki.debian.org/how-can-i-help ) == - Show old opportunities as well as new ones: how-can-i-help --old - E: Sub-process /usr/bin/dpkg returned an error code (1) dpkg: dependency problems prevent configuration of libqalculate14:amd64: libqalculate14:amd64 depends on libqalculate14-data; however: Package libqalculate14-data is not installed. dpkg: error processing package libqalculate14:amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: libqalculate14:amd64 The main problem seems to be in - dpkg: error processing archive /var/cache/apt/archives/libqalculate14-data_2.2.1-1_all.deb (--unpack): trying to overwrite '/usr/share/locale/fr/LC_MESSAGES/libqalculate.mo', which is also in package libqalculate-data 2.2.1-1 Please fix the same. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (100, 'experimental'), (100, 'unstable'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libqalculate14 depends on: ii libc62.27-2 ii libcurl3-gnutls 7.58.0-2 ii libgcc1 1:8-20180312-2 ii libgmp10 2:6.1.2+dfsg-3 ii libicu57 57.1-9 ii libmpfr6 4.0.1-1 pn libqalculate14-data ii libstdc++6 8-20180312-2 ii libxml2 2.9.4+dfsg1-6.1 libqalculate14 recommends no packages. libqalculate14 suggests no packages. -- no debconf information -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
Bug#889567: marked as done (dh-autoreconf: needs Breaks: quilt (<< 0.63-8.2~), dpatch (<< 2.0.38+nmu1~))
Your message dated Wed, 21 Mar 2018 23:04:54 + with message-id and subject line Bug#889567: fixed in dh-autoreconf 17 has caused the Debian Bug report #889567, regarding dh-autoreconf: needs Breaks: quilt (<< 0.63-8.2~), dpatch (<< 2.0.38+nmu1~) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 889567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debhelper,dh-autoreconf Severity: serious Control: found -1 16 Control: affects -1 src:dansguardian https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dansguardian.html ... dh_autoreconf configure.ac:14: installing './compile' src/Makefile.am:13: warning: source file 'contentscanners/clamav.cpp' is in a subdirectory, src/Makefile.am:13: but option 'subdir-objects' is disabled automake: warning: possible forward-incompatibility. automake: At least a source file is in a subdirectory, but the 'subdir-objects' automake: automake option hasn't been enabled. For now, the corresponding output automake: object file(s) will be placed in the top-level directory. However, automake: this behaviour will change in future Automake versions: they will automake: unconditionally cause object files to be placed in the same subdirectory automake: of the corresponding sources. automake: You are advised to start using 'subdir-objects' option throughout your automake: project, to avoid future incompatibilities. src/Makefile.am:31: warning: source file 'contentscanners/icapscan.cpp' is in a subdirectory, src/Makefile.am:31: but option 'subdir-objects' is disabled src/Makefile.am:39: warning: source file 'contentscanners/kavdscan.cpp' is in a subdirectory, src/Makefile.am:39: but option 'subdir-objects' is disabled src/Makefile.am:25: warning: source file 'contentscanners/clamdscan.cpp' is in a subdirectory, src/Makefile.am:25: but option 'subdir-objects' is disabled src/Makefile.am:43: warning: source file 'contentscanners/commandlinescan.cpp' is in a subdirectory, src/Makefile.am:43: but option 'subdir-objects' is disabled src/Makefile.am:48: warning: source file 'downloadmanagers/default.cpp' is in a subdirectory, src/Makefile.am:48: but option 'subdir-objects' is disabled src/Makefile.am:53: warning: source file 'downloadmanagers/fancy.cpp' is in a subdirectory, src/Makefile.am:53: but option 'subdir-objects' is disabled src/Makefile.am:57: warning: source file 'downloadmanagers/trickle.cpp' is in a subdirectory, src/Makefile.am:57: but option 'subdir-objects' is disabled src/Makefile.am:62: warning: source file 'authplugins/proxy.cpp' is in a subdirectory, src/Makefile.am:62: but option 'subdir-objects' is disabled src/Makefile.am:63: warning: source file 'authplugins/ident.cpp' is in a subdirectory, src/Makefile.am:63: but option 'subdir-objects' is disabled src/Makefile.am:64: warning: source file 'authplugins/ip.cpp' is in a subdirectory, src/Makefile.am:64: but option 'subdir-objects' is disabled src/Makefile.am:70: warning: source file 'authplugins/ntlm.cpp' is in a subdirectory, src/Makefile.am:70: but option 'subdir-objects' is disabled src/Makefile.am:65: warning: source file 'authplugins/digest.cpp' is in a subdirectory, src/Makefile.am:65: but option 'subdir-objects' is disabled dh_dpatch_patch applying patch 03_add_unconfigures to ./ ... ok. applying patch 07_fix_config_paths to ./ ... ok. applying patch 11_FixOptionContainer.cpp_on_arm to ./ ... ok. applying patch 50_clamav095_support to ./ ... ok. applying patch 60_add_gcc4.4_support to ./ ... ok. applying patch 65-fix_clamdsocket to ./ ... ok. applying patch 70-gcc4.6 to ./ ... ok. applying patch 70_fix_clamav_detection to ./ ... ok. applying patch 80_fix_libcre3_max_sub_expression_allocation to ./ ... ok. ... checking for CLAMAV... no configure: error: Package requirements (libclamav >= 4) were not met: Requested 'libclamav >= 4' but version of libclamav is 0.99.3-beta2 This is caused by: dh-autoreconf (16) unstable; urgency=medium ... * Run dh_autoreconf after dh_update_autotools_config, not before dh_auto_configure --- End Message --- --- Begin Message --- Source: dh-autoreconf Source-Version: 17 We believe that the bug you reported is fixed in the latest version of dh-autoreconf, 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 889...@bugs.debian.org, and the maintainer will
Processed (with 1 error): Re: Bug#890845: HighContrast icon theme doesn't work with GTK3
Processing control commands: > forwarded -1 Unknown command or malformed arguments to command. > tags -1 -moreinfo Bug #890845 [gnome-accessibility-themes] HighContrast icon theme doesn't work with GTK3 Removed tag(s) moreinfo. > severity -1 serious Bug #890845 [gnome-accessibility-themes] HighContrast icon theme doesn't work with GTK3 Severity set to 'serious' from 'normal' -- 890845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#893471: Missing dependency: puppet-module-nanliu-staging
Processing commands for cont...@bugs.debian.org: > owner 893471 ! Bug #893471 [puppet-module-puppetlabs-mysql] Missing dependency: puppet-module-nanliu-staging Owner recorded as Sebastien Badia . > tags 893471 + pending confirmed moreinfo Bug #893471 [puppet-module-puppetlabs-mysql] Missing dependency: puppet-module-nanliu-staging Added tag(s) pending, moreinfo, and confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 893471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#893736: glib2.0 FTBFS: ModuleNotFoundError: No module named 'distutils'
Processing control commands: > found -1 2.54.3-2 Bug #893736 [src:glib2.0] glib2.0 FTBFS: ModuleNotFoundError: No module named 'distutils' Marked as found in versions glib2.0/2.54.3-2. -- 893736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893471: Missing dependency: puppet-module-nanliu-staging
owner -1 ! tags -1 + pending confirmed moreinfo thanks Hi Thomas, nanliu-staging seems an un-maintained fork of the voxpupuli module https://github.com/nanliu/puppet-staging https://github.com/voxpupuli/puppet-staging puppetlabs-mysql depends on the voxpupuli original module (puppet/staging), we should maybe RoM the puppet-module-nanliu-staging package and introduce the puppet-module-puppet-staging (https://forge.puppet.com/puppet/staging) one. The only reverse dependency of puppet-module-nanliu-staging is puppet-module-puppetlabs-rabbitmq and upstream has dropped nanliu-staging for puppet/archive https://github.com/voxpupuli/puppet-rabbitmq/blob/49f5e1fdc38cf10d92250f8a1c24ca9929df5f02/metadata.json#L66-L67 from voxpupuli too (https://forge.puppet.com/puppet/archive) If it's okay for you, I'm preparing an ITP for https://github.com/voxpupuli/puppet-staging Let me kown… Cheers, Sebastien, for the Debian puppet-team signature.asc Description: PGP signature
Bug#893736: glib2.0 FTBFS: ModuleNotFoundError: No module named 'distutils'
Control: found -1 2.54.3-2 I am uploading a fixed glib2.0 soon, but let's let the current version migrate to Testing to not block several pieces of GNOME 3.28. The bug is triggered by the recent python3.6 upload. Thanks, Jeremy Bicha
Bug#893608: marked as done (sbuild: Silent arch:all defaults change breaks buildd setups)
Your message dated Wed, 21 Mar 2018 22:16:03 + with message-id and subject line Bug#893608: fixed in sbuild 0.75.0-1 has caused the Debian Bug report #893608, regarding sbuild: Silent arch:all defaults change breaks buildd setups 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.) -- 893608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sbuild Version: 0.74.0-1 Severity: serious [Feel free to downgrade severity, but from my PoV this needs addressing before Buster is released] Hi, In the latest upload, #870263 was fixed (which I support, for what it's worth; any+all builds is the right default for users), meaning that buildd setups now build arch:all packages, which we *have* to work around by setting $build_arch_all=0 in sbuild.conf. Without this, uploads are rejected by the archive (the buildd's signing key does not have upload rights for arch:all packages, the arch:all packages already exist, etc). This is therefore a breaking change, and so deserves at least a mention in the NEWS file. Moreover, having to configure this in sbuild.conf is sub-optimal; ideally, buildd would pass --no-arch-all to sbuild when an arch:any build is requested by wanna-build; as far as I know, the assumption is always that a non-Architecture:all build is arch:any. We probably also don't want lintian run during buildd builds as it fork-bombs on packages like gcc-8-cross-ports (#890873), and there's lintian.debian.org doing that for x86, which is probably good enough, though I suppose in an ideal world it would be run too. Regards, James --- End Message --- --- Begin Message --- Source: sbuild Source-Version: 0.75.0-1 We believe that the bug you reported is fixed in the latest version of sbuild, 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 893...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Stapelberg (supplier of updated sbuild 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, 21 Mar 2018 22:24:01 +0100 Source: sbuild Binary: libsbuild-perl sbuild sbuild-debian-developer-setup buildd Architecture: source Version: 0.75.0-1 Distribution: unstable Urgency: medium Maintainer: Debian buildd-tools Developers Changed-By: Michael Stapelberg Description: buildd - Daemon for automatically building Debian binary packages from Deb libsbuild-perl - Library for building Debian binary packages from Debian sources sbuild - Tool for building Debian binary packages from Debian sources sbuild-debian-developer-setup - Convenience script to set up an sbuild environment for Debian Dev Closes: 893226 893608 Changes: sbuild (0.75.0-1) unstable; urgency=medium . * New upstream release. * buildd: only build arch:any packages (closes: #893608) * buildd: do not run lintian * remove harmful unnecessary lintian binary check (closes: #893226) Checksums-Sha1: c58983a70ec8647b37d486161ea990c4f0d8b678 2489 sbuild_0.75.0-1.dsc 83f4d6fad00b29e9daced8ac75f9185c3f9be89a 195312 sbuild_0.75.0.orig.tar.xz 3bf0de60333ff60a0dc6f611f48ab2f96c35ade9 49384 sbuild_0.75.0-1.debian.tar.xz 0eff64761da1f42dfb6848376eb62b58bc18bfa7 6684 sbuild_0.75.0-1_amd64.buildinfo Checksums-Sha256: 465054d60f012507c557b040344ca9053e54f3178b704d626d02c009ffbc6520 2489 sbuild_0.75.0-1.dsc 05cee6e7e27348003941af50d3fddde05075ec3c78a126d99617a2f0f0b1cfe3 195312 sbuild_0.75.0.orig.tar.xz 5b80200c968eca30b47d286a75afb6ba7e9e15f64ef77f21fcd2948632c44633 49384 sbuild_0.75.0-1.debian.tar.xz 8599b0eed374784441d8cd7a4b026a4109dcec9ac923601c580d770ab1ea2b71 6684 sbuild_0.75.0-1_amd64.buildinfo Files: 5513205dff0a176114a454a8574efa92 2489 devel extra sbuild_0.75.0-1.dsc a2240e3546538fd92007af4d6a1ce312 195312 devel extra sbuild_0.75.0.orig.tar.xz f6e2132b5c7095d121cfd56c646deb0e 49384 devel extra sbuild_0.75.0-1.debian.tar.xz d95081eaf8a382ef9ccc4e68aed42006 6684 devel extra sbuild_0.75.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEQk4U1wPnxtQ9nW82TnFg7UrI7h0FAlqyzuEACgkQTnFg7UrI 7h2trA/+NuNMK6+bYOWpo03L8MMCQZye24pnyeigKUPQp+QPZSlwFiJ
Bug#893315: marked as done (sbuild's autopkgtests fail due to the lack of a lintian dependency)
Your message dated Wed, 21 Mar 2018 22:16:03 + with message-id and subject line Bug#893226: fixed in sbuild 0.75.0-1 has caused the Debian Bug report #893226, regarding sbuild's autopkgtests fail due to the lack of a lintian dependency 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.) -- 893226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sbuild Version: 0.74.0-1 Severity: important Ubuntu's autopkgtest schroots (for example) do not have lintian installed by default. This makes the autopkgtests fail because the lintian binary is not found. Here is the log from the amd64 autopkgtest: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/sbuild/20180317_191912_dacda@/log.gz Adding lintian to the dependencies in debian/tests/control fixes this. Please fix this in the Debian packaging. -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 --- End Message --- --- Begin Message --- Source: sbuild Source-Version: 0.75.0-1 We believe that the bug you reported is fixed in the latest version of sbuild, 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 893...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Stapelberg (supplier of updated sbuild 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, 21 Mar 2018 22:24:01 +0100 Source: sbuild Binary: libsbuild-perl sbuild sbuild-debian-developer-setup buildd Architecture: source Version: 0.75.0-1 Distribution: unstable Urgency: medium Maintainer: Debian buildd-tools Developers Changed-By: Michael Stapelberg Description: buildd - Daemon for automatically building Debian binary packages from Deb libsbuild-perl - Library for building Debian binary packages from Debian sources sbuild - Tool for building Debian binary packages from Debian sources sbuild-debian-developer-setup - Convenience script to set up an sbuild environment for Debian Dev Closes: 893226 893608 Changes: sbuild (0.75.0-1) unstable; urgency=medium . * New upstream release. * buildd: only build arch:any packages (closes: #893608) * buildd: do not run lintian * remove harmful unnecessary lintian binary check (closes: #893226) Checksums-Sha1: c58983a70ec8647b37d486161ea990c4f0d8b678 2489 sbuild_0.75.0-1.dsc 83f4d6fad00b29e9daced8ac75f9185c3f9be89a 195312 sbuild_0.75.0.orig.tar.xz 3bf0de60333ff60a0dc6f611f48ab2f96c35ade9 49384 sbuild_0.75.0-1.debian.tar.xz 0eff64761da1f42dfb6848376eb62b58bc18bfa7 6684 sbuild_0.75.0-1_amd64.buildinfo Checksums-Sha256: 465054d60f012507c557b040344ca9053e54f3178b704d626d02c009ffbc6520 2489 sbuild_0.75.0-1.dsc 05cee6e7e27348003941af50d3fddde05075ec3c78a126d99617a2f0f0b1cfe3 195312 sbuild_0.75.0.orig.tar.xz 5b80200c968eca30b47d286a75afb6ba7e9e15f64ef77f21fcd2948632c44633 49384 sbuild_0.75.0-1.debian.tar.xz 8599b0eed374784441d8cd7a4b026a4109dcec9ac923601c580d770ab1ea2b71 6684 sbuild_0.75.0-1_amd64.buildinfo Files: 5513205dff0a176114a454a8574efa92 2489 devel extra sbuild_0.75.0-1.dsc a2240e3546538fd92007af4d6a1ce312 195312 devel extra sbuild_0.75.0.orig.tar.xz f6e2132b5c7095d121cfd56c646deb0e 49384 devel extra sbuild_0.75.0-1.debian.tar.xz d95081eaf8a382ef9ccc4e68aed42006 6684 devel extra sbuild_0.75.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEQk4U1wPnxtQ9nW82TnFg7UrI7h0FAlqyzuEACgkQTnFg7UrI 7h2trA/+NuNMK6+bYOWpo03L8MMCQZye24pnyeigKUPQp+QPZSlwFiJI0qIuan0X VlHtana+4af+od2P5otUC2TF/Egmr+M9ik2cvf3GrifhuNuhm2R+327+i0YLELbj TZzRKUl6eqDp3g94LvTWqjcBT3huoXs/TDIuyZv+hUXCfT7cNlcndFMONla39mHK qdnHglHV5ATN5qWa0AX9CLfkI4ljuQ0rr9Y3pvX2e4JNGlQ1WJnT7iihUN+NTMCg RmRiNAG7xqZNjWu90QbVuMiy8SFr+etaDAIxq9EFAbrPkKdj1PE0aH11v0xLXXVl Yo2td+RI0uA25NCj75t+XUfYo5okROsl3V3UKFAEKMXErzTE/a0SSxBDHR8VqCqD LKqT0t4U89HB7ngw506hLW3jkUbWT6ljJ5w2dwWYviHTGnnq1Vm7Zln92roPa8xJ +oryrMVUl/3Gw9Q1nbJQ+QHwx+PWUJJLC4uU8BqD1LQRSQoESpLEkxIH2gPLXATT kMfYPcGLh1QyJ2gJUtQdQXgrFa+IuXK0bvmXzdfF9mRLElBdvR6fV+9CUIevsszz BvXJpQl5VYKdXFLeN6tSxMoep
Bug#893691: marked as done (sbuild: Missing Depends on lintian after defaults change)
Your message dated Wed, 21 Mar 2018 22:16:03 + with message-id and subject line Bug#893226: fixed in sbuild 0.75.0-1 has caused the Debian Bug report #893226, regarding sbuild: Missing Depends on lintian after defaults change 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.) -- 893226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sbuild Version: 0.74.0-1 Severity: serious Hi, Now that lintian defaults to enabled in 0.74.0-1, sbuild by default will need lintian installed, but it has no dependency on it, and thus fails with: > Error reading configuration: LINTIAN binary 'lintian' does not exist or is > not executable at /usr/share/perl5/Sbuild/Conf.pm line 76 Please fix this (I don't care if it's Depends or the default) so sbuild isn't broken out of the box. James --- End Message --- --- Begin Message --- Source: sbuild Source-Version: 0.75.0-1 We believe that the bug you reported is fixed in the latest version of sbuild, 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 893...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Stapelberg (supplier of updated sbuild 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, 21 Mar 2018 22:24:01 +0100 Source: sbuild Binary: libsbuild-perl sbuild sbuild-debian-developer-setup buildd Architecture: source Version: 0.75.0-1 Distribution: unstable Urgency: medium Maintainer: Debian buildd-tools Developers Changed-By: Michael Stapelberg Description: buildd - Daemon for automatically building Debian binary packages from Deb libsbuild-perl - Library for building Debian binary packages from Debian sources sbuild - Tool for building Debian binary packages from Debian sources sbuild-debian-developer-setup - Convenience script to set up an sbuild environment for Debian Dev Closes: 893226 893608 Changes: sbuild (0.75.0-1) unstable; urgency=medium . * New upstream release. * buildd: only build arch:any packages (closes: #893608) * buildd: do not run lintian * remove harmful unnecessary lintian binary check (closes: #893226) Checksums-Sha1: c58983a70ec8647b37d486161ea990c4f0d8b678 2489 sbuild_0.75.0-1.dsc 83f4d6fad00b29e9daced8ac75f9185c3f9be89a 195312 sbuild_0.75.0.orig.tar.xz 3bf0de60333ff60a0dc6f611f48ab2f96c35ade9 49384 sbuild_0.75.0-1.debian.tar.xz 0eff64761da1f42dfb6848376eb62b58bc18bfa7 6684 sbuild_0.75.0-1_amd64.buildinfo Checksums-Sha256: 465054d60f012507c557b040344ca9053e54f3178b704d626d02c009ffbc6520 2489 sbuild_0.75.0-1.dsc 05cee6e7e27348003941af50d3fddde05075ec3c78a126d99617a2f0f0b1cfe3 195312 sbuild_0.75.0.orig.tar.xz 5b80200c968eca30b47d286a75afb6ba7e9e15f64ef77f21fcd2948632c44633 49384 sbuild_0.75.0-1.debian.tar.xz 8599b0eed374784441d8cd7a4b026a4109dcec9ac923601c580d770ab1ea2b71 6684 sbuild_0.75.0-1_amd64.buildinfo Files: 5513205dff0a176114a454a8574efa92 2489 devel extra sbuild_0.75.0-1.dsc a2240e3546538fd92007af4d6a1ce312 195312 devel extra sbuild_0.75.0.orig.tar.xz f6e2132b5c7095d121cfd56c646deb0e 49384 devel extra sbuild_0.75.0-1.debian.tar.xz d95081eaf8a382ef9ccc4e68aed42006 6684 devel extra sbuild_0.75.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEQk4U1wPnxtQ9nW82TnFg7UrI7h0FAlqyzuEACgkQTnFg7UrI 7h2trA/+NuNMK6+bYOWpo03L8MMCQZye24pnyeigKUPQp+QPZSlwFiJI0qIuan0X VlHtana+4af+od2P5otUC2TF/Egmr+M9ik2cvf3GrifhuNuhm2R+327+i0YLELbj TZzRKUl6eqDp3g94LvTWqjcBT3huoXs/TDIuyZv+hUXCfT7cNlcndFMONla39mHK qdnHglHV5ATN5qWa0AX9CLfkI4ljuQ0rr9Y3pvX2e4JNGlQ1WJnT7iihUN+NTMCg RmRiNAG7xqZNjWu90QbVuMiy8SFr+etaDAIxq9EFAbrPkKdj1PE0aH11v0xLXXVl Yo2td+RI0uA25NCj75t+XUfYo5okROsl3V3UKFAEKMXErzTE/a0SSxBDHR8VqCqD LKqT0t4U89HB7ngw506hLW3jkUbWT6ljJ5w2dwWYviHTGnnq1Vm7Zln92roPa8xJ +oryrMVUl/3Gw9Q1nbJQ+QHwx+PWUJJLC4uU8BqD1LQRSQoESpLEkxIH2gPLXATT kMfYPcGLh1QyJ2gJUtQdQXgrFa+IuXK0bvmXzdfF9mRLElBdvR6fV+9CUIevsszz BvXJpQl5VYKdXFLeN6tSxMoep8jpUestOEJnjqZdUJn7QaEUYASftdSS8c43rBc6 fEPB2Mbhr0AmTMko4mSJvY0v6KjgITk22TQpuFWbt8igAQoPLiU= =C73l -END PGP SIGNATURE End Message ---
Bug#893226: marked as done (sbuild: Error reading configuration: LINTIAN binary 'lintian' does not exist)
Your message dated Wed, 21 Mar 2018 22:16:03 + with message-id and subject line Bug#893226: fixed in sbuild 0.75.0-1 has caused the Debian Bug report #893226, regarding sbuild: Error reading configuration: LINTIAN binary 'lintian' does not exist 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.) -- 893226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sbuild Version: 0.74.0-1 Severity: important Hi! Even with unmodified conffiles and ~/.sbuildrc moved away, sbuild fails at startup with: Error reading configuration: LINTIAN binary 'lintian' does not exist or is not executable at /usr/share/perl5/Sbuild/Conf.pm line 76. You need to either add a hard Depends on lintian, or to handle its lack gracefully. And, lintian gets run entirely within the chroot, right? If so, what's the point of requiring it on the host... Obviously, a machine one can even think of running sbuild has enough storage that installing lintian with all its dependencies is not exactly a burden. Meow! -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: armhf (armv7l) Kernel: Linux 4.16.0-rc4-00028-gace1e265867f (SMP w/4 CPU cores; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages sbuild depends on: ii adduser 3.117 ii libsbuild-perl 0.74.0-1 ii perl5.26.1-5 Versions of packages sbuild recommends: ii autopkgtest 5.1 ii debootstrap 1.0.93+nmu1 ii schroot 1.6.10-4 Versions of packages sbuild suggests: pn deborphan ii kmod 25-1 ii wget 1.19.4-1 -- no debconf information --- End Message --- --- Begin Message --- Source: sbuild Source-Version: 0.75.0-1 We believe that the bug you reported is fixed in the latest version of sbuild, 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 893...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Stapelberg (supplier of updated sbuild 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, 21 Mar 2018 22:24:01 +0100 Source: sbuild Binary: libsbuild-perl sbuild sbuild-debian-developer-setup buildd Architecture: source Version: 0.75.0-1 Distribution: unstable Urgency: medium Maintainer: Debian buildd-tools Developers Changed-By: Michael Stapelberg Description: buildd - Daemon for automatically building Debian binary packages from Deb libsbuild-perl - Library for building Debian binary packages from Debian sources sbuild - Tool for building Debian binary packages from Debian sources sbuild-debian-developer-setup - Convenience script to set up an sbuild environment for Debian Dev Closes: 893226 893608 Changes: sbuild (0.75.0-1) unstable; urgency=medium . * New upstream release. * buildd: only build arch:any packages (closes: #893608) * buildd: do not run lintian * remove harmful unnecessary lintian binary check (closes: #893226) Checksums-Sha1: c58983a70ec8647b37d486161ea990c4f0d8b678 2489 sbuild_0.75.0-1.dsc 83f4d6fad00b29e9daced8ac75f9185c3f9be89a 195312 sbuild_0.75.0.orig.tar.xz 3bf0de60333ff60a0dc6f611f48ab2f96c35ade9 49384 sbuild_0.75.0-1.debian.tar.xz 0eff64761da1f42dfb6848376eb62b58bc18bfa7 6684 sbuild_0.75.0-1_amd64.buildinfo Checksums-Sha256: 465054d60f012507c557b040344ca9053e54f3178b704d626d02c009ffbc6520 2489 sbuild_0.75.0-1.dsc 05cee6e7e27348003941af50d3fddde05075ec3c78a126d99617a2f0f0b1cfe3 195312 sbuild_0.75.0.orig.tar.xz 5b80200c968eca30b47d286a75afb6ba7e9e15f64ef77f21fcd2948632c44633 49384 sbuild_0.75.0-1.debian.tar.xz 8599b0eed374784441d8cd7a4b026a4109dcec9ac923601c580d770ab1ea2b71 6684 sbuild_0.75.0-1_amd64.buildinfo Files: 5513205dff0a176114a454a8574efa92 2489 devel extra sbuild_0.75.0-1.dsc a2240e3546538fd92007af4d6a1ce312 195312 devel extra sbuild_0.75.0.orig.tar.xz f6e2132b5c7095d121cfd56c646deb0e 49384 devel extra sbuild_0.75.0-1
Bug#891351: Details
Hi, can you install scilab-cli to see if it works better? Snark on #debian-science
Bug#893366: marked as done (libwayland-dev: Uninstallable due to conflicting wayland-egl.pc)
Your message dated Wed, 21 Mar 2018 21:28:13 + with message-id and subject line Bug#893366: fixed in wayland 1.14.92-1 has caused the Debian Bug report #893366, regarding libwayland-dev: Uninstallable due to conflicting wayland-egl.pc 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.) -- 893366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libwayland-dev Version: 1.14.91-1 Severity: serious Hi! This package ships the file /usr/lib//pkgconfig/wayland-egl.pc which conflicts with the one installed by libegl1-mesa-dev, w/o any Replaces field or similar. The problem also is that the file providing the shared library is also not pulled in by libwayland-dev, so packages that would find the pkg-config file would then fail to build, and they should really not be depending on the shared library directly. Thanks, Guillem --- End Message --- --- Begin Message --- Source: wayland Source-Version: 1.14.92-1 We believe that the bug you reported is fixed in the latest version of wayland, 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 893...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated wayland 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, 21 Mar 2018 21:42:58 +0200 Source: wayland Binary: libwayland-client0 libwayland-egl1 libwayland-server0 libwayland-cursor0 libwayland-dev libwayland-doc libwayland-bin Architecture: source Version: 1.14.92-1 Distribution: experimental Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Description: libwayland-bin - wayland compositor infrastructure - binary utilities libwayland-client0 - wayland compositor infrastructure - client library libwayland-cursor0 - wayland compositor infrastructure - cursor library libwayland-dev - wayland compositor infrastructure - development files libwayland-doc - wayland compositor infrastructure - documentation files libwayland-egl1 - wayland compositor infrastructure - EGL library libwayland-server0 - wayland compositor infrastructure - server library Closes: 893366 Changes: wayland (1.14.92-1) experimental; urgency=medium . [ Timo Aaltonen ] * New upstream pre-release. * signing-keys.asc: Updated. * libwayland-dev.install: Drop static libs, they're not provided anymore. * libwayland-egl1.symbols: Updated. * control: Adjust Breaks/Provides for libwayland-egl migration. . [ Héctor Orón Martínez ] * control: Fix uninstallability issues. (Closes: #893366) Checksums-Sha1: 80b397f7c82717859ee0a50544039c4223c8ba26 2249 wayland_1.14.92-1.dsc d86a35744617790e4a7e056168d95a7e09a79f45 320179 wayland_1.14.92-1.tar.gz 5b45b42693c71b0ed28c8ec4165177a57df804fa 6253 wayland_1.14.92-1_source.buildinfo Checksums-Sha256: c1e6d8f0e33a1497676c3b5f094d0b9516cf1345ad77218049b5f63a828377ff 2249 wayland_1.14.92-1.dsc 4489f1d29172710db56fa55fc01deb53ebd5f02e499e7084c69898d7215a1c98 320179 wayland_1.14.92-1.tar.gz 620dd296bea4e21c4d7f32c4b2adf82799e1e7b7c6a0611706678bdc76f06107 6253 wayland_1.14.92-1_source.buildinfo Files: d0139a8ac039b678ffb01d8cec308985 2249 x11 optional wayland_1.14.92-1.dsc 10d538f42092ebba6a99bf3ef33e30a4 320179 x11 optional wayland_1.14.92-1.tar.gz b2f4f400ab96a2a5fa5e4f10aa822182 6253 x11 optional wayland_1.14.92-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAlqythYACgkQy3AxZaiJ hNz4NBAAjnXMDzmYTBZPfcsSdCiLyMYcT4jaTc7/7thux7kvGPVQT1wwzldF/yH1 5B8XS6ba0Un1gA1zg8wckk4RhdTiVXxfcluXDRaxj8NVV0L2f392964t+WTbpnXG lDM0pvyWTlwhX/J1kQmniR2lbK5njS/tXZb/HVOAABbv6BmHKEXsLkFqjorbXwO/ S+VWirfYPc1DqwFLlix5jcZ21VQ3zKhl1G0bKBx+rrTnDGq+Hc5Voa6DBrXu0Oxn yE3KQuKeNkI7fhs+gyHYWCcJQlKJHJyQxJsb2mOyQue9D3ta0e9Gu0+7LJ5qKB6B llCKLT6aUxpcDxaC6k3KET0bHLtBPoCLhNqKH3FxcCpKeztqFySqXWEwdREUhqgS nOXtFSnmRY4kaIa3/Jr1y4LKNjGOAU7af9sMX/Pzi/WNCsXA7heP/XJt03pLHRzP zV+fVi0qwXtpTpNv0kPJvFrvpQIVedrQa9a6GGScybA+D77RHOfuxiGBm0caGZDT Q/Fsr001fHBAcG4ZYE17MOCyFSHFX5BTYxSBwQ3vOyeDXSr4yJwGgFILLe6hTOmB enJi8AOdYd8Fnu1BqF/hi68WExOaD0Hly+Hp6l0t/yTUrJ
Bug#893736: glib2.0 FTBFS: ModuleNotFoundError: No module named 'distutils'
Source: glib2.0 Version: 2.56.0-2 Severity: serious User: helm...@debian.org Usertags: rebootstrap sbuild -d sid glib2.0 ends with: | Making all in gio | make[4]: Entering directory '/<>/debian/build/deb/gio' | UNINSTALLED_GLIB_SRCDIR=../../../.. \ | UNINSTALLED_GLIB_BUILDDIR=.. \ | /usr/bin/python3 ../../../../gio/gdbus-2.0/codegen/gdbus-codegen.in \ | --interface-prefix org. \ | --generate-c-code gdbus-daemon-generated \ | --c-namespace _G \ | ../../../../gio/dbus-daemon.xml \ | | Traceback (most recent call last): | File "../../../../gio/gdbus-2.0/codegen/gdbus-codegen.in", line 53, in | from codegen import codegen_main | File "/<>/gio/gdbus-2.0/codegen/codegen_main.py", line 29, in | from . import dbustypes | File "/<>/gio/gdbus-2.0/codegen/dbustypes.py", line 22, in | from . import utils | File "/<>/gio/gdbus-2.0/codegen/utils.py", line 22, in | import distutils.version | ModuleNotFoundError: No module named 'distutils' | make[4]: *** [Makefile:5019: gdbus-daemon-generated.c] Error 1 | make[4]: Leaving directory '/<>/debian/build/deb/gio' | make[4]: *** Waiting for unfinished jobs | make[4]: Entering directory '/<>/debian/build/deb/gio' | UNINSTALLED_GLIB_SRCDIR=../../../.. \ | UNINSTALLED_GLIB_BUILDDIR=.. \ | /usr/bin/python3 ../../../../gio/gdbus-2.0/codegen/gdbus-codegen.in \ | --interface-prefix org. \ | --generate-c-code gdbus-daemon-generated \ | --c-namespace _G \ | ../../../../gio/dbus-daemon.xml \ | | Traceback (most recent call last): | File "../../../../gio/gdbus-2.0/codegen/gdbus-codegen.in", line 53, in | from codegen import codegen_main | File "/<>/gio/gdbus-2.0/codegen/codegen_main.py", line 29, in | from . import dbustypes | File "/<>/gio/gdbus-2.0/codegen/dbustypes.py", line 22, in | from . import utils | File "/<>/gio/gdbus-2.0/codegen/utils.py", line 22, in | import distutils.version | ModuleNotFoundError: No module named 'distutils' | make[4]: *** [Makefile:5019: gdbus-daemon-generated.h] Error 1 | make[4]: Leaving directory '/<>/debian/build/deb/gio' | make[3]: *** [Makefile:1279: all-recursive] Error 1 | make[2]: *** [Makefile:900: all] Error 2 | dh_auto_build: cd debian/build/deb && make -j8 -O returned exit code 2 | make[1]: *** [debian/rules:137: override_dh_auto_build] Error 25 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:24: binary-arch] Error 2 | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 Possibly some dependency is missing? I guess this is connected to the python3.6/3.6.5~rc1-2 upload. Helmut
Bug#893735: paraview FTBFS on armel/armhf: QVTKOpenGLWidget.cxx:458:3: error: 'QOpenGLFunctions_3_2_Core' was not declared in this scope
Source: paraview
Version: 5.4.1+dfsg4-1
Severity: serious
https://buildd.debian.org/status/package.php?p=paraview&suite=sid
...
/<>/paraview-5.4.1+dfsg4/VTK/GUISupport/Qt/QVTKOpenGLWidget.cxx: In
member function 'virtual void QVTKOpenGLWidget::paintGL()':
/<>/paraview-5.4.1+dfsg4/VTK/GUISupport/Qt/QVTKOpenGLWidget.cxx:458:3:
error: 'QOpenGLFunctions_3_2_Core' was not declared in this scope
QOpenGLFunctions_3_2_Core* f =
^
/<>/paraview-5.4.1+dfsg4/VTK/GUISupport/Qt/QVTKOpenGLWidget.cxx:458:3:
note: suggested alternative: 'QOpenGLFunctionsPrivate'
QOpenGLFunctions_3_2_Core* f =
^
QOpenGLFunctionsPrivate
/<>/paraview-5.4.1+dfsg4/VTK/GUISupport/Qt/QVTKOpenGLWidget.cxx:458:30:
error: 'f' was not declared in this scope
QOpenGLFunctions_3_2_Core* f =
^
/<>/paraview-5.4.1+dfsg4/VTK/GUISupport/Qt/QVTKOpenGLWidget.cxx:459:83:
error: no matching function for call to
'QOpenGLContext::versionFunctions()'
QOpenGLContext::currentContext()->versionFunctions();
^
In file included from
/usr/include/arm-linux-gnueabihf/qt5/QtGui/QOpenGLContext:1:0,
from
/<>/paraview-5.4.1+dfsg4/VTK/GUISupport/Qt/QVTKOpenGLWidget.cxx:18:
/usr/include/arm-linux-gnueabihf/qt5/QtGui/qopenglcontext.h:193:11: note:
candidate: template TYPE* QOpenGLContext::versionFunctions() const
TYPE *versionFunctions() const
^~~~
/usr/include/arm-linux-gnueabihf/qt5/QtGui/qopenglcontext.h:193:11: note:
template argument deduction/substitution failed:
VTK/GUISupport/Qt/CMakeFiles/vtkGUISupportQt.dir/build.make:453: recipe for
target
'VTK/GUISupport/Qt/CMakeFiles/vtkGUISupportQt.dir/QVTKOpenGLWidget.cxx.o' failed
make[3]: ***
[VTK/GUISupport/Qt/CMakeFiles/vtkGUISupportQt.dir/QVTKOpenGLWidget.cxx.o] Error
1
On armel/armhf (and on arm64 in Ubuntu) Qt is compiled for OpenGL ES
instead of full OpenGL.
This is caused by:
https://gitlab.kitware.com/vtk/vtk/commit/53c566782950cd94ccd877cb906607e4cc33e1f7
The following fixes the build:
--- paraview-5.4.1+dfsg4.orig/VTK/GUISupport/Qt/QVTKOpenGLWidget.cxx
+++ paraview-5.4.1+dfsg4/VTK/GUISupport/Qt/QVTKOpenGLWidget.cxx
@@ -19,7 +19,7 @@
#include
#include
#include
-#include
+//#include
#include
#include
#include
@@ -453,6 +453,7 @@ void QVTKOpenGLWidget::paintGL()
// before proceeding with blit-ing.
this->makeCurrent();
+#if 0
// blit from this->FBO to QOpenGLWidget's FBO.
vtkQVTKOpenGLWidgetDebugMacro("paintGL::blit-to-defaultFBO");
QOpenGLFunctions_3_2_Core* f =
@@ -485,6 +486,7 @@ void QVTKOpenGLWidget::paintGL()
f->glColorMask(colorMask[0], colorMask[1], colorMask[2], colorMask[3]);
f->glClearColor(clearColor[0], clearColor[1], clearColor[2],
clearColor[3]);
}
+#endif /* 0 */
}
//-
This is obviously not a patch that should be applied,
it serves only to show that it is really just a small piece
of recently added code that prevents compilation here.
If possible, this should be fixed.
In case fixing is not possible or desirable, please:
- change the build dependency from libqt5opengl5-dev
to libqt5opengl5-desktop-dev, and
- file a removal bug for the old armel+armhf binaries
against ftp.debian.org
Bug#893729: sympy FTBFS: python3-distutils is now a separate package
Given that the errors suggest it tried and failed to find both
setuptools and distutils, it probably already can use either (though I
haven't tried to check this), if they are installed...
On 21/03/18 20:30, Ghislain Vaillant wrote:
Another option could be to patch the build system to use setuptools instead
of distutils as recommended by the PyPA?
Le mer. 21 mars 2018 à 20:45, Rebecca N. Palmer a
écrit :
Source: sympy
Severity: serious
Control: tags -1 patch
X-Debbugs-Cc: debian-pyt...@lists.debian.org
python3-distutils has been moved out of python3.6 (as of 3.6.5~rc1-2),
so if you need it, please build-depend on it. (Or python3-setuptools,
given that this looks like it might prefer that.)
(Has anyone checked whether there are more of these?)
dpkg-buildpackage: info: source package sympy
dpkg-buildpackage: info: source version 1.1.1-4
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Yaroslav Halchenko
dpkg-buildpackage: info: host architecture amd64
dpkg-source --before-build sympy-1.1.1
fakeroot debian/rules clean
dh clean --with python2,python3 --buildsystem=pybuild
debian/rules override_dh_auto_clean
make[1]: Entering directory
'/home/rnpalmer/Debian/builds/stackbuild/sympy-1.1.1'
dh_auto_clean
I: pybuild base:217: python2.7 setup.py clean
/usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown
distribution option: 'install_requires'
warnings.warn(msg)
running clean
I: pybuild base:217: python3.6 setup.py clean
Traceback (most recent call last):
File "setup.py", line 46, in
from setuptools import setup, Command
ModuleNotFoundError: No module named 'setuptools'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "setup.py", line 49, in
from distutils.core import setup, Command
ModuleNotFoundError: No module named 'distutils'
E: pybuild pybuild:330: clean: plugin distutils failed with: exit
code=1: python3.6 setup.py clean
dh_auto_clean: pybuild --clean -i python{version} -p 3.6 returned exit
code 13
make[1]: *** [debian/rules:29: override_dh_auto_clean] Error 25
make[1]: Leaving directory
'/home/rnpalmer/Debian/builds/stackbuild/sympy-1.1.1'
make: *** [debian/rules:10: clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess
returned exit status 2
Bug#893729: sympy FTBFS: python3-distutils is now a separate package
Another option could be to patch the build system to use setuptools instead
of distutils as recommended by the PyPA?
Le mer. 21 mars 2018 à 20:45, Rebecca N. Palmer a
écrit :
> Source: sympy
> Severity: serious
> Control: tags -1 patch
> X-Debbugs-Cc: debian-pyt...@lists.debian.org
>
> python3-distutils has been moved out of python3.6 (as of 3.6.5~rc1-2),
> so if you need it, please build-depend on it. (Or python3-setuptools,
> given that this looks like it might prefer that.)
>
> (Has anyone checked whether there are more of these?)
>
> dpkg-buildpackage: info: source package sympy
> dpkg-buildpackage: info: source version 1.1.1-4
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Yaroslav Halchenko
>
> dpkg-buildpackage: info: host architecture amd64
> dpkg-source --before-build sympy-1.1.1
> fakeroot debian/rules clean
> dh clean --with python2,python3 --buildsystem=pybuild
> debian/rules override_dh_auto_clean
> make[1]: Entering directory
> '/home/rnpalmer/Debian/builds/stackbuild/sympy-1.1.1'
> dh_auto_clean
> I: pybuild base:217: python2.7 setup.py clean
> /usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown
> distribution option: 'install_requires'
>warnings.warn(msg)
> running clean
> I: pybuild base:217: python3.6 setup.py clean
> Traceback (most recent call last):
>File "setup.py", line 46, in
> from setuptools import setup, Command
> ModuleNotFoundError: No module named 'setuptools'
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>File "setup.py", line 49, in
> from distutils.core import setup, Command
> ModuleNotFoundError: No module named 'distutils'
> E: pybuild pybuild:330: clean: plugin distutils failed with: exit
> code=1: python3.6 setup.py clean
> dh_auto_clean: pybuild --clean -i python{version} -p 3.6 returned exit
> code 13
> make[1]: *** [debian/rules:29: override_dh_auto_clean] Error 25
> make[1]: Leaving directory
> '/home/rnpalmer/Debian/builds/stackbuild/sympy-1.1.1'
> make: *** [debian/rules:10: clean] Error 2
> dpkg-buildpackage: error: fakeroot debian/rules clean subprocess
> returned exit status 2
>
>
Bug#890400: Any news about a new upstream version with new SONAME?
Dear Andreas, I could somehow udate the symbols list, but still get a lintian warning [1]. I have pushed my commits, would you mind giving them a look? Will proceed with other libs once I have confirmation that everything is ok. Best, Julien. [1] https://lintian.debian.org/tags/symbols-declares-dependency-on-other-package.html On Wed, Mar 21, 2018 at 6:15 PM, Andreas Tille wrote: > Hi Julien, > > On Wed, Mar 21, 2018 at 05:25:10PM +0100, Julien Yann Dutheil wrote: > > I'm starting to package libbpp-core4 from upstream. It works fine but I > > have a warning because of the symbol files which are not matching. My > > understanding is that this is due to your previous (unreleased) patch > which > > was incrementing the interface number for version 2.3.2. How can I solve > > that? (basically, discard the previous symbols and use the new one > instead, > > as they correspond to the new "official" .so.4 version?). > > The build log contains a diff you can use as patch. > > > I have not pushed > > my commits yet, let me know if you need them already. > > Feel free to push and ping me in case of trouble so I can fix it. > > Kind regards > >Andreas. > > -- > http://fam-tille.de > > -- Julien Y. Dutheil, Ph-D 0 (+49) 6421 178 986 § Max Planck Institute for Evolutionary Biology Molecular Systems Evolution Department of Evolutionary Genetics Plön -- GERMANY § Institute of Evolutionary Sciences - Montpellier University of Montpellier 2 -- FRANCE
Bug#892201: nlohmann-json build issues with gcc 7.2
On Wed, 7 Mar 2018 11:50:31 +0100, Muri Nicanor said: > Hi Dominique, uhoreg offered to package version 3 > (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885540) of > nlohmann-json and already created an ITP for that: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886865 It may be worth backporting the fix to the 2.x branch, since the 3.x package will be a separate package, so even after the 3.x package is released, the bug will still be present in the 2.x package. But it may also be worth looking into whether the issue is still present when compiling with gcc 7.3, as it may have just been a bug in gcc 7.2. > cheers, muri > On 03/06/2018 05:36 PM, Dominique Belhachemi wrote: >> Package: nlohmann-json Version: 2.1.1-1 Severity: grave >> >> Some applications don't compile with nlohmann-json 2.1.1 and gcc 7.2 >> . >> >> You can find details here: >> >> https://github.com/nlohmann/json/issues/742 >> >> Please update the package. >> >> Thanks -Dominique >>
Processed: bug 893472 is forwarded to https://github.com/miyagawa/Plack-Middleware-Deflater/pull/13
Processing commands for cont...@bugs.debian.org: > forwarded 893472 https://github.com/miyagawa/Plack-Middleware-Deflater/pull/13 Bug #893472 [libplack-middleware-deflater-perl] libplack-middleware-deflater-perl: broken on big endian hosts Set Bug forwarded-to-address to 'https://github.com/miyagawa/Plack-Middleware-Deflater/pull/13'. > thanks Stopping processing here. Please contact me if you need assistance. -- 893472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893472 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: sympy FTBFS: python3-distutils is now a separate package
Processing control commands: > tags -1 patch Bug #893729 [src:sympy] sympy FTBFS: python3-distutils is now a separate package Added tag(s) patch. -- 893729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893729 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893729: sympy FTBFS: python3-distutils is now a separate package
Source: sympy
Severity: serious
Control: tags -1 patch
X-Debbugs-Cc: debian-pyt...@lists.debian.org
python3-distutils has been moved out of python3.6 (as of 3.6.5~rc1-2),
so if you need it, please build-depend on it. (Or python3-setuptools,
given that this looks like it might prefer that.)
(Has anyone checked whether there are more of these?)
dpkg-buildpackage: info: source package sympy
dpkg-buildpackage: info: source version 1.1.1-4
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Yaroslav Halchenko
dpkg-buildpackage: info: host architecture amd64
dpkg-source --before-build sympy-1.1.1
fakeroot debian/rules clean
dh clean --with python2,python3 --buildsystem=pybuild
debian/rules override_dh_auto_clean
make[1]: Entering directory
'/home/rnpalmer/Debian/builds/stackbuild/sympy-1.1.1'
dh_auto_clean
I: pybuild base:217: python2.7 setup.py clean
/usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown
distribution option: 'install_requires'
warnings.warn(msg)
running clean
I: pybuild base:217: python3.6 setup.py clean
Traceback (most recent call last):
File "setup.py", line 46, in
from setuptools import setup, Command
ModuleNotFoundError: No module named 'setuptools'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "setup.py", line 49, in
from distutils.core import setup, Command
ModuleNotFoundError: No module named 'distutils'
E: pybuild pybuild:330: clean: plugin distutils failed with: exit
code=1: python3.6 setup.py clean
dh_auto_clean: pybuild --clean -i python{version} -p 3.6 returned exit
code 13
make[1]: *** [debian/rules:29: override_dh_auto_clean] Error 25
make[1]: Leaving directory
'/home/rnpalmer/Debian/builds/stackbuild/sympy-1.1.1'
make: *** [debian/rules:10: clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess
returned exit status 2
Bug#890384: marked as done (ignition-math4: baseline violation on amd64)
Your message dated Wed, 21 Mar 2018 19:08:46 + with message-id and subject line Bug#890384: fixed in ignition-math4 4.0.0+dfsg1-3 has caused the Debian Bug report #890384, regarding ignition-math4: baseline violation on amd64 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.) -- 890384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890384 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ignition-math4 Version: 4.0.0+dfsg1-1 Severity: serious https://sources.debian.org/src/ignition-math4/4.0.0+dfsg1-1/debian/rules/#L10 ifeq ($(DEB_HOST_ARCH),amd64) SSE_FLAGS = -mfpmath=sse -msse -msse2 -msse3 -mssse3 -DSSE endif SSE3 and SSSE3 are not part of the amd64 baseline. "-mfpmath=sse -msse -msse2" are already enabled by default on amd64, no need to do that manually. The SSE define does not seem to be used anywhere in the code. --- End Message --- --- Begin Message --- Source: ignition-math4 Source-Version: 4.0.0+dfsg1-3 We believe that the bug you reported is fixed in the latest version of ignition-math4, 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 890...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jose Luis Rivero (supplier of updated ignition-math4 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, 21 Mar 2018 17:46:55 + Source: ignition-math4 Binary: libignition-math4 libignition-math4-dev Architecture: source Version: 4.0.0+dfsg1-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Jose Luis Rivero Description: libignition-math4 - Ignition Robotics Math Library - Shared library libignition-math4-dev - Ignition Robotics Math Library - Development files Closes: 890384 Changes: ignition-math4 (4.0.0+dfsg1-3) unstable; urgency=medium . * Do not set any of the SSE flags in rules file (Closes: #890384) * Move control Vcs- to salsa * Use https in debian copyright Checksums-Sha1: c00983c7d888bf942f0bec2e5fb5b6da665eeb21 1957 ignition-math4_4.0.0+dfsg1-3.dsc 479b65c67a430145784998df9fc0311e142f1327 5104 ignition-math4_4.0.0+dfsg1-3.debian.tar.xz ff899434afe49d4e69fa3eb06c95f0b0b3becabb 7325 ignition-math4_4.0.0+dfsg1-3_source.buildinfo Checksums-Sha256: e4064f9b68484ce3a4240d16a26775323b1229900be4bfeff483498c5c2c3873 1957 ignition-math4_4.0.0+dfsg1-3.dsc 6644e3fdb82e60db27afec81aac25f58dc54d10dcadc956fdbf4639a33e5db18 5104 ignition-math4_4.0.0+dfsg1-3.debian.tar.xz 2d3d686a80230a437cc31e6b11108b775761bbb50b95da82488acb55eed14d6d 7325 ignition-math4_4.0.0+dfsg1-3_source.buildinfo Files: 7d593fa32f106c02404f64b942ec4d35 1957 science optional ignition-math4_4.0.0+dfsg1-3.dsc f8222459c0f155d77ab4475b390e221b 5104 science optional ignition-math4_4.0.0+dfsg1-3.debian.tar.xz 81f3cd20515840a506461b6ae01120bd 7325 science optional ignition-math4_4.0.0+dfsg1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQFOBAEBCgA4FiEEoIFhu+wcwGOWFFkDXpRsCQr/BCcFAlqyobkaHGpyaXZlcm9A b3NyZm91bmRhdGlvbi5vcmcACgkQXpRsCQr/BCcb4Qf/YaDf9M9BTT/V2MimAFQY +bZSGeDBkIkiwGfzt37kiokXmEpDX3uNwlxTTgiC2FHg8g3AHjwD+rs911EDxy4R 08s4kOQrjVVeUMp535qLmTPxHX7LGk4bVODGe2d3j4jrYWGBOv6dnJSyqLg1D4ls dwRrUtuNJak75UfEv4GHDDph41RiPQ0PcyyLA8zx0jRGjrNtfND9UC7eX3bcBLq8 GIxDtKSJdfU3t4qo1qsAr2hf0GiLtSVpoYXFXvltJWijoUoAOeol3UcDOGiOpbOS M9QYymllJInRdHxye+oncSuzL/SzCcKWaOsdEUR7CIYNFhxyjseZNiP0cwKUoPnx +Q== =TzBL -END PGP SIGNATURE End Message ---
Processed: affects 893697
Processing commands for cont...@bugs.debian.org: > affects 893697 src:setools Bug #893697 [python3-networkx] sesearch needs python3-lib2to3 Added indication that 893697 affects src:setools > thanks Stopping processing here. Please contact me if you need assistance. -- 893697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893442: lynkeos.app: FTBFS on ppc64el: AltiVec argument passed to unprototyped function
Hi Yavor, thanks for already digging into this issue. I'm not an altivec expert but I was interested to look into this and maybe help. On Sun, 18 Mar 2018 22:33:16 +0200, Yavor Doganov wrote: > Source: lynkeos.app > Version: 2.10+dfsg1-2 > Severity: serious > Tags: patch > User: debian-powe...@lists.debian.org > Usertags: ppc64el > > I would appreciate if someone knowledgeable from -powerpc confirms > that the attached patch is correct. The build failure is: > > gcc /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m > -c \ > -MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I.. > -I/<>/lynkeos.app-2.10+dfsg1/GNUstep.. > -I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources > -I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../ThreadConnectionSources > -I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../ThirdPartySources/SMDoubleSlider > -DNO_FRAMEWORK_CHECK=1 -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 > -DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 > -fno-strict-aliasing -fexceptions -fobjc-exceptions -D_NATIVE_OBJC_EXCEPTIONS > -pthread -fPIC -Wall -DGSWARN -DGSDIAGNOSE -Wno-import -g -O2 -g -O2 > -fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. > -fstack-protector-strong -Wformat -Werror=format-security -fgnu-runtime > -Wno-unknown-pragmas -Wno-cpp -fconstant-string-class=NSConstantString -I. > -I/usr/local/include/GNUstep -I/usr/include/GNUstep \ >-o obj/Lynkeos.obj/MyDeconvolution.m.o > /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m: In > function 'vector_Process_One_line': > /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:72:44: > warning: excess elements in vector initializer > 0x04050607, 0x04050607 }; > ^~ > /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:72:44: > note: (near initialization for 'Vperma') > /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:72:56: > warning: excess elements in vector initializer > 0x04050607, 0x04050607 }; > ^~ > /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:72:56: > note: (near initialization for 'Vperma') > /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:74:44: > warning: excess elements in vector initializer > 0x0C0D0E0F, 0x0C0D0E0F }; > ^~ > /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:74:44: > note: (near initialization for 'Vpermb') > /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:74:56: > warning: excess elements in vector initializer > 0x0C0D0E0F, 0x0C0D0E0F }; > ^~ > /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:74:56: > note: (near initialization for 'Vpermb') > /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:88:13: > warning: implicit declaration of function 'vec_madd' > [-Wimplicit-function-declaration] >Vdx = vec_madd( vec_ld(0,expXptr), Vdy, Vzero ); > ^~~~ > /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:88:23: > warning: implicit declaration of function 'vec_ld'; did you mean 'vector'? > [-Wimplicit-function-declaration] >Vdx = vec_madd( vec_ld(0,expXptr), Vdy, Vzero ); >^~ >vector > /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:88:7: > error: AltiVec argument passed to unprototyped function >Vdx = vec_madd( vec_ld(0,expXptr), Vdy, Vzero ); >^~~ > /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:89:41: > warning: implicit declaration of function 'vec_cmplt' > [-Wimplicit-function-declaration] >const __vector __bool int Vmask = vec_cmplt(Vdx,Vthr); > ^ > /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:89:7: > error: AltiVec argument passed to unprototyped function >const __vector __bool int Vmask = vec_cmplt(Vdx,Vthr); >^ > /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:90:27: > warning: implicit declaration of function 'vec_and'; did you mean 'vscanf'? > [-Wimplicit-function-declaration] >__vector REAL Vge = vec_and(Vdx,Vmask); >^~~ >vscanf > /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:90:7: > error: AltiVec argument passed to unprototyped function >__vector REAL Vge = vec_and(Vdx,Vmask); >^~~~ > /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:91:27: > warning: implicit declaration of function 'vec_andc'; did you mean 'vscanf'? > [-Wimplicit-function-declaration] >
Processed: Re: Bug#893622: deepin-movie-reborn: Fails to build
Processing control commands: > retitle -1 deepin-movie-reborn: Fails to build on !amd64 Bug #893622 [src:deepin-movie-reborn] deepin-movie-reborn: Fails to build Changed Bug title to 'deepin-movie-reborn: Fails to build on !amd64' from 'deepin-movie-reborn: Fails to build'. > severity -1 important Bug #893622 [src:deepin-movie-reborn] deepin-movie-reborn: Fails to build on !amd64 Severity set to 'important' from 'serious' -- 893622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893622 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893622: deepin-movie-reborn: Fails to build
Control: retitle -1 deepin-movie-reborn: Fails to build on !amd64 Control: severity -1 important On Tue, Mar 20, 2018 at 11:37:32AM -0400, Jeremy Bicha wrote: > Source: deepin-movie-reborn > Version: 3.2.3-1 > Severity: serious > > deepin-movie-reborn fails to build from source: > > https://buildd.debian.org/status/package.php?p=deepin-movie-reborn Builds on amd64, so technically not RC: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/deepin-movie-reborn.html > Thanks, > Jeremy Bicha 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#888508: marked as done (gitlab: multiple CVEs from GitLab Security Release: 10.3.4, 10.2.6, and 10.1.6 advisory)
Your message dated Wed, 21 Mar 2018 18:05:27 + with message-id and subject line Bug#888508: fixed in gitlab 10.5.5+dfsg-1 has caused the Debian Bug report #888508, regarding gitlab: multiple CVEs from GitLab Security Release: 10.3.4, 10.2.6, and 10.1.6 advisory 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.) -- 888508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888508 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gitlab Version: 8.13.11+dfsg1-12 Severity: grave Tags: upstream security Hi See https://about.gitlab.com/2018/01/16/gitlab-10-dot-3-dot-4-released/ for which several go back to 8.9.0 versions. There are three CVEs out of https://security-tracker.debian.org/tracker/source-package/gitlab belonging to that list wich are yet marked undetermined, because not clear from the advisory if 8.13.11=dfsg1-12 might be affected. But assuming the 'version affected' information is correct, they are not, please confirm so we can adjust the security-tracker information. Regards, Salvatore -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: gitlab Source-Version: 10.5.5+dfsg-1 We believe that the bug you reported is fixed in the latest version of gitlab, 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 888...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated gitlab package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 18 Mar 2018 15:17:08 +0530 Source: gitlab Binary: gitlab Architecture: source Version: 10.5.5+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Pirate Praveen Description: gitlab - git powered software platform to collaborate on code (non-omnibus Closes: 888508 890757 Changes: gitlab (10.5.5+dfsg-1) unstable; urgency=medium . [ Dmitry Smirnov ] * Depends += "ruby-excon (>= 0.60.0~)" * Added new patch to fix Markdown rendering (Closes: #890757). * Depends: set minimum version for "rake". . [ Pirate Praveen ] * New upstream version 10.5.5 (Closes: #888508) - Fixes multiple security vulnerabilities in 10.3.4 (CVE-2017-0914, CVE-2017-0916, CVE-2017-0917, CVE-2017-0918, CVE-2017-0923, CVE-2017-0925, CVE-2017-0926, CVE-2017-0927, CVE-2017-3710) * Remove files no longer present in vendor from Files-Excluded * Refresh patches * Add new node-* dependencies already in the archive as depends * Tighten dependencies * Bump debhelper compat to 10 and standards version to 4.1.3 Checksums-Sha1: 8335491d4fa010ec1ae525b33c24f9ae300eb2b8 2523 gitlab_10.5.5+dfsg-1.dsc 9f726e11889c0bd7f5e730c019f1468c349ee8fe 44727574 gitlab_10.5.5+dfsg.orig.tar.gz 76ba841f3f52f394c3ba1f3aa5eaeaa9a1b40b32 61472 gitlab_10.5.5+dfsg-1.debian.tar.xz 9ba15455174c4a67b7b2fc8fc2d99a5bd1d67ecf 8025 gitlab_10.5.5+dfsg-1_source.buildinfo Checksums-Sha256: a206cdf1042f34c33cfd339c41c97c380dfb2b31df3a0e30d9525c772f756db1 2523 gitlab_10.5.5+dfsg-1.dsc d75e02a5c428bf5201ba6a96eeba7346dd16bb489093940b9623509b4d0f3654 44727574 gitlab_10.5.5+dfsg.orig.tar.gz 6af9dbaa6e1dec89abdc0bd2a3993f081296c155a871d80e3ad5a3fe07de1b14 61472 gitlab_10.5.5+dfsg-1.debian.tar.xz e5a45f9e917c2ff6063ee079f60d994b1ac30a45ccef5097b103681716e7 8025 gitlab_10.5.5+dfsg-1_source.buildinfo Files: 905ab61ee2a44a36c8af3491446616e7 2523 contrib/net optional gitlab_10.5.5+dfsg-1.dsc 21f94a6b4537850d46fd7cece9d54d76 44727574 contrib/net optional gitlab_10.5.5+dfsg.orig.tar.gz 193dff203a7aecff132699c058364c73 61472 contrib/net optional gitlab_10.5.5+dfsg-1.debian.tar.xz 5db348f2df8c57f988f1cde2c3a1ea93 8025 contrib/net optional gitlab_10.5.5+dfsg-1_source.buildinfo -BEGIN PGP SI
Bug#888165: marked as done (ruby-puppet-syntax: FTBFS on ruby2.5: OpenSSL::ASN1::ASN1Error: oid exists)
Your message dated Wed, 21 Mar 2018 19:00:07 +0100 with message-id <20180321180007.GD2961@debian> and subject line Re: [DRE-maint] Bug#888165: ruby-puppet-syntax: FTBFS on ruby2.5: OpenSSL::ASN1::ASN1Error: oid exists has caused the Debian Bug report #888165, regarding ruby-puppet-syntax: FTBFS on ruby2.5: OpenSSL::ASN1::ASN1Error: oid exists to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 888165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-puppet-syntax Version: 2.4.1-1 Severity: important User: debian-r...@lists.debian.org Usertags: ruby2.5 Dear Maintainer, This package fails to build against ruby2.5. Soon, there will be a transition to ruby2.5, and this package will FTBFS in sid. There may be some details on the wiki about common problems: https://wiki.debian.org/Teams/Ruby/Ruby25Transition Build log excerpt: Failures: 1) PuppetSyntax::Manifests should return nothing from a valid file with a class using tag parameter Failure/Error: Puppet::Test::TestHelper.initialize OpenSSL::ASN1::ASN1Error: oid exists # ./lib/puppet-syntax/manifests.rb:12:in `check' # ./spec/puppet-syntax/manifests_spec.rb:21:in `block (2 levels) in ' 2) PuppetSyntax::Manifests should return an error from an invalid file Failure/Error: Puppet::Test::TestHelper.initialize OpenSSL::ASN1::ASN1Error: oid exists # ./lib/puppet-syntax/manifests.rb:12:in `check' # ./spec/puppet-syntax/manifests_spec.rb:29:in `block (2 levels) in ' 3) PuppetSyntax::Manifests should return a warning from an invalid file Failure/Error: Puppet::Test::TestHelper.initialize OpenSSL::ASN1::ASN1Error: oid exists # ./lib/puppet-syntax/manifests.rb:12:in `check' # ./spec/puppet-syntax/manifests_spec.rb:44:in `block (2 levels) in ' 4) PuppetSyntax::Manifests should ignore warnings about storeconfigs Failure/Error: Puppet::Test::TestHelper.initialize OpenSSL::ASN1::ASN1Error: oid exists # ./lib/puppet-syntax/manifests.rb:12:in `check' # ./spec/puppet-syntax/manifests_spec.rb:55:in `block (2 levels) in ' 5) PuppetSyntax::Manifests should read more than one valid file Failure/Error: Puppet::Test::TestHelper.initialize OpenSSL::ASN1::ASN1Error: oid exists # ./lib/puppet-syntax/manifests.rb:12:in `check' # ./spec/puppet-syntax/manifests_spec.rb:64:in `block (2 levels) in ' 6) PuppetSyntax::Manifests should continue after finding an error in the first file Failure/Error: Puppet::Test::TestHelper.initialize OpenSSL::ASN1::ASN1Error: oid exists # ./lib/puppet-syntax/manifests.rb:12:in `check' # ./spec/puppet-syntax/manifests_spec.rb:72:in `block (2 levels) in ' 7) PuppetSyntax::Manifests deprecation notices on puppet 4.0.0 and above should instead be failures Failure/Error: Puppet::Test::TestHelper.initialize OpenSSL::ASN1::ASN1Error: oid exists # ./lib/puppet-syntax/manifests.rb:12:in `check' # ./spec/puppet-syntax/manifests_spec.rb:96:in `block (4 levels) in ' 8) PuppetSyntax::Manifests app_management app_management = false (default) should fail to parse an application manifest Failure/Error: Puppet::Test::TestHelper.initialize OpenSSL::ASN1::ASN1Error: oid exists # ./lib/puppet-syntax/manifests.rb:12:in `check' # ./spec/puppet-syntax/manifests_spec.rb:148:in `block (4 levels) in ' 9) PuppetSyntax::Manifests app_management app_management = true should successfully parse an application manifest on Puppet >= 4.3.0 Failure/Error: Puppet::Test::TestHelper.initialize OpenSSL::ASN1::ASN1Error: oid exists # ./lib/puppet-syntax/manifests.rb:12:in `check' # ./spec/puppet-syntax/manifests_spec.rb:163:in `block (4 levels) in ' 10) PuppetSyntax::Manifests future_parser future_parser = false (default) should succeed on Puppet >= 4.0.0 Failure/Error: Puppet::Test::TestHelper.initialize OpenSSL::ASN1::ASN1Error: oid exists # ./lib/puppet-syntax/manifests.rb:12:in `check' # ./spec/puppet-syntax/manifests_spec.rb:201:in `block (4 levels) in ' Finished in 0.11609 seconds (files took 0.82926 seconds to load) 44 examples, 10 failures, 2 pending Failed examples: rspec ./spec/puppet-syntax/manifests_spec.rb:19 # PuppetSyntax::Manifests should return nothing from a valid file with a class using tag parameter rspec ./spec/puppet-syntax/manifests_spec.rb:27 # PuppetSyntax::Manife
Bug#881796: marked as done (CVE-2017-1001001: pluxml: XSS and missing httponly flag)
Your message dated Wed, 21 Mar 2018 17:41:20 + with message-id and subject line Bug#881796: fixed in pluxml 5.6-1 has caused the Debian Bug report #881796, regarding CVE-2017-1001001: pluxml: XSS and missing httponly flag 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.) -- 881796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pluxml Version: 5.5-2 Severity: grave Tags: security upstream https://nvd.nist.gov/vuln/detail/CVE-2017-1001001 https://github.com/pluxml/PluXml/issues/253 PluXml version 5.6 is vulnerable to stored cross-site scripting vulnerability, within the article creation page, which can result in escalation of privileges. Two problems: - Cross-site scripting vulnerability with "writer" role - Missing HttpOnly flag -- Henri Salo signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: pluxml Source-Version: 5.6-1 We believe that the bug you reported is fixed in the latest version of pluxml, 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 881...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tanguy Ortolo (supplier of updated pluxml 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, 21 Mar 2018 10:48:19 +0100 Source: pluxml Binary: pluxml Architecture: source all Version: 5.6-1 Distribution: unstable Urgency: medium Maintainer: Tanguy Ortolo Changed-By: Tanguy Ortolo Description: pluxml - light blog/CMS engine powered by XML Closes: 855162 881796 Changes: pluxml (5.6-1) unstable; urgency=medium . * New upstream release. * debian/po/es.po: Update Spanish translation. (Closes: #855162) * debian/postinst: - add new config parameter bypage_tags. - update the software version parameter in the generated configuration file. * debian/patches: - fix-mandatory-captcha.patch: remove patch applied upstream. - mitigate_CVE-2017-1001001.patch: mitigate a security issue CVE-2017-1001001 (Closes: #881796) * debian/compat: use debhelper compatibility level 11. * debian/control: - depend on debhelper >= 9. - switch priority from extra (deprecated) to optional. - add Rules-Requires-Root: binary-targets, necessary to run chmod and chown in debian/rules. - add default-mta to the recommends. - update Standards-Version to 4.1.3 (changes required). * debian/copyright: use a secure format URL. * debian/rules: remove inappropriate exec rights on a PHP class file. * debian/source/lintian-overrides: remove obsolete overrides. Checksums-Sha1: fbe30fc30ebf6250b77d8673093dc3b6e5f7304d 1794 pluxml_5.6-1.dsc 4b883327a9fb7332fca1476764596dde2a66ea2f 300708 pluxml_5.6.orig.tar.gz 5127526336ef903a982de4fe9c64b175a04a7407 32256 pluxml_5.6-1.debian.tar.xz 0e1ecd678c2f618cb8b9ed4997278512f9fe8bbb 236956 pluxml_5.6-1_all.deb 91e8aea4106976a98a92a21ff54c7fb2a9d266fd 6418 pluxml_5.6-1_amd64.buildinfo Checksums-Sha256: cf40cdbfd3c303d1e4f8e9d4dbc6d6118df1754260e3cf282b52e518fcad3590 1794 pluxml_5.6-1.dsc 2443dff5531abdf5d2dd91364946aa13420d88d61a4781b298e14d88ef2cfc3e 300708 pluxml_5.6.orig.tar.gz 563b779a3e40bb510021085884b86dd4a95375fb42b41868cc1e1fb366c29cff 32256 pluxml_5.6-1.debian.tar.xz 7a51a8299ff4d19ee8a985d9b3b91f63ffe55d5695e21c243e89d995139e9ade 236956 pluxml_5.6-1_all.deb 3d349a99d2cf9d62398de57446d8289057ef97830bd7f0540a609361e413c8a9 6418 pluxml_5.6-1_amd64.buildinfo Files: 65e237367cbe039edf4936fcf655da37 1794 web optional pluxml_5.6-1.dsc 1663b67b1ca83f9c70047819b5d2c4ea 300708 web optional pluxml_5.6.orig.tar.gz a9b580caf7448faf36e1236ed45ff173 32256 web optional pluxml_5.6-1.debian.tar.xz 3e6a0747f68a4a989317fd69e540f26c 236956 web optional pluxml_5.6-1_all.deb c741a89b2441c8ab1d69246f99162905 6418 web optional pluxml_5.6-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEC1QNJk2lrQnjLj0t6vLNUcUAaBkFAlqyhOMACgkQ6vLNUcUA aBn79g/9Eglf4rsy/QHZuiRtci8GOQD8C1U4MBbZ62eWGuLAtsCR9442RxPhTVQG CdGrVqraX3oZtbNgeBuRoKYUnmyjaNJXtfndCFbgTn6vlvFX//8pCGR9Keg+vmA
Processed: bug 888165 is forwarded to https://github.com/puppetlabs/puppet/pull/6538
Processing commands for cont...@bugs.debian.org: > forwarded 888165 https://github.com/puppetlabs/puppet/pull/6538 Bug #888165 [src:ruby-puppet-syntax] ruby-puppet-syntax: FTBFS on ruby2.5: OpenSSL::ASN1::ASN1Error: oid exists Changed Bug forwarded-to-address to 'https://github.com/puppetlabs/puppet/pull/6538' from 'https://github.com/voxpupuli/puppet-syntax/issues/89'. > thanks Stopping processing here. Please contact me if you need assistance. -- 888165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#872493: marked as done (vdr-plugin-sudoku FTBFS with vdr 2.3.8)
Your message dated Wed, 21 Mar 2018 17:36:59 + with message-id and subject line Bug#893364: Removed package(s) from unstable has caused the Debian Bug report #872493, regarding vdr-plugin-sudoku FTBFS with vdr 2.3.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 872493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vdr-plugin-sudoku Version: 0.3.5-20 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-sudoku.html ... g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Wl,-z,relro -I/usr/include/vdr/include -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"sudoku"' -Wdate-time -D_FORTIFY_SOURCE=2 -c -o bitmap.o bitmap.cpp bitmap.cpp: In member function 'void SudokuPlugin::Bitmap::text(const char*, bool)': bitmap.cpp:54:11: error: 'max' was not declared in this scope int y = max((Height() - wrapper.Lines() * font->Height()) / 2, 0); ^~~ bitmap.cpp:54:11: note: suggested alternative: In file included from /usr/include/c++/7/vector:60:0, from sudoku.h:29, from bitmap.h:24, from bitmap.cpp:21: /usr/include/c++/7/bits/stl_algobase.h:265:5: note: 'std::max' max(const _Tp& __a, const _Tp& __b, _Compare __comp) ^~~ : recipe for target 'bitmap.o' failed make[2]: *** [bitmap.o] Error 1 --- End Message --- --- Begin Message --- Version: 0.3.5-20+rm Dear submitter, as the package vdr-plugin-sudoku has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/893364 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#872492: marked as done (vdr-plugin-spider FTBFS with vdr 2.3.8)
Your message dated Wed, 21 Mar 2018 17:36:29 + with message-id and subject line Bug#893363: Removed package(s) from unstable has caused the Debian Bug report #872492, regarding vdr-plugin-spider FTBFS with vdr 2.3.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 872492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vdr-plugin-spider Version: 0.2.2-21 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-spider.html ... g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Wl,-z,relro -I/usr/include/vdr/include -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"spider"' -Wdate-time -D_FORTIFY_SOURCE=2 -c -o bitmap.o bitmap.cpp bitmap.cpp: In member function 'void SpiderPlugin::Bitmap::text(const char*, bool)': bitmap.cpp:77:11: error: 'max' was not declared in this scope int y = max((Height() - wrapper.Lines() * font->Height()) / 2, 0); ^~~ bitmap.cpp:77:11: note: suggested alternative: In file included from /usr/include/c++/7/vector:60:0, from spider.h:30, from bitmap.h:26, from bitmap.cpp:23: /usr/include/c++/7/bits/stl_algobase.h:265:5: note: 'std::max' max(const _Tp& __a, const _Tp& __b, _Compare __comp) ^~~ bitmap.cpp: In constructor 'SpiderPlugin::Bitmap::Bitmap(int, int, const char*, const char*)': bitmap.cpp:54:11: warning: ignoring return value of 'int asprintf(char**, const char*, ...)', declared with attribute warn_unused_result [-Wunused-result] asprintf(&path, "%s/%s.xpm", dir, name); ^~~ bitmap.cpp: In constructor 'SpiderPlugin::Bitmap::Bitmap(int, int, const char*, const char*, const char*)': bitmap.cpp:65:11: warning: ignoring return value of 'int asprintf(char**, const char*, ...)', declared with attribute warn_unused_result [-Wunused-result] asprintf(&path, "%s/%s_%s.xpm", dir, suit, rank); ^~~~ : recipe for target 'bitmap.o' failed make[2]: *** [bitmap.o] Error 1 --- End Message --- --- Begin Message --- Version: 0.2.2-21+rm Dear submitter, as the package vdr-plugin-spider has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/893363 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: Re: sbuild: Silent arch:all defaults change breaks buildd setups
Processing control commands: > tags -1 + pending Bug #893608 [sbuild] sbuild: Silent arch:all defaults change breaks buildd setups Added tag(s) pending. -- 893608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893608: sbuild: Silent arch:all defaults change breaks buildd setups
control: tags -1 + pending Hi James, James Clarke writes: > In the latest upload, #870263 was fixed (which I support, for what it's worth; > any+all builds is the right default for users), meaning that buildd setups now > build arch:all packages, which we *have* to work around by setting > $build_arch_all=0 in sbuild.conf. Without this, uploads are rejected by the > archive (the buildd's signing key does not have upload rights for arch:all > packages, the arch:all packages already exist, etc). This is therefore a > breaking change, and so deserves at least a mention in the NEWS file. > Moreover, > having to configure this in sbuild.conf is sub-optimal; ideally, buildd would > pass --no-arch-all to sbuild when an arch:any build is requested by > wanna-build; > as far as I know, the assumption is always that a non-Architecture:all build > is > arch:any. Addressed by the following commit IIUC: https://anonscm.debian.org/cgit/buildd-tools/sbuild.git/commit/?id=821144b5ef48bb11bf98657349ba808c25452721 > We probably also don't want lintian run during buildd builds as it fork-bombs > on > packages like gcc-8-cross-ports (#890873), and there's lintian.debian.org > doing > that for x86, which is probably good enough, though I suppose in an ideal > world > it would be run too. https://anonscm.debian.org/cgit/buildd-tools/sbuild.git/commit/?id=e8da1ee764d8b3b5aaa0fe82aac8e877f1cc4f4d -- Best regards, Michael
Bug#842303: marked as done ([web2py] License problem and source missing)
Your message dated Wed, 21 Mar 2018 17:21:03 + with message-id and subject line Bug#892866: Removed package(s) from unstable has caused the Debian Bug report #842303, regarding [web2py] License problem and source missing 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.) -- 842303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: web2py Version: 2.12.3-1 Severity: serious usertags: source-is-missing severity: serious X-Debbugs-CC: ftpmas...@debian.org Hi, your package includes some files that seem to lack sources in preferred forms of modification (analytic seems to be google analytic under non free license): applications/admin/static/codemirror/addon/hint/html-hint.js line length is 577 characters (>512) applications/admin/static/codemirror/emmet.min.js applications/admin/static/js/analytics.min.js applications/admin/static/js/bootstrap.min.js applications/admin/static/js/calendar.js line length is 32013 characters (>512) applications/admin/static/js/dd_belatedpng.js line length is 6549 characters (>512) applications/admin/static/js/hogan-2.0.0.js line length is 5779 characters (>512) applications/admin/static/js/jquery.flot.js line length is 2952 characters (>512) applications/admin/static/js/jquery.flot.resize.js line length is 863 characters (>512) applications/admin/static/js/jquery.js line length is 32038 characters (>512) applications/admin/static/js/modernizr.custom.js line length is 14752 characters (>512) applications/admin/static/js/share.js line length is 529 characters (>512) applications/admin/static/js/typeahead.min.js applications/admin/static/plugin_jqmobile/dd_belatedpng.js line length is 6549 characters (>512) applications/admin/static/plugin_jqmobile/jquery.mobile-1.2.0.min.js applications/admin/static/plugin_jqmobile/jquery.mobile-1.3.1.min.js applications/examples/static/js/analytics.min.js applications/examples/static/js/bootstrap.min.js applications/examples/static/js/calendar.js line length is 32013 characters (>512) applications/examples/static/js/dd_belatedpng.js line length is 6549 characters (>512) applications/examples/static/js/jquery.js line length is 32038 characters (>512) applications/examples/static/js/modernizr.custom.js line length is 14752 characters (>512) applications/examples/static/js/share.js line length is 529 characters (>512) applications/welcome/static/js/analytics.min.js applications/welcome/static/js/bootstrap.min.js applications/welcome/static/js/calendar.js line length is 32013 characters (>512) applications/welcome/static/js/jquery.js line length is 32038 characters (>512) applications/welcome/static/js/modernizr-2.8.3.min.js applications/welcome/static/js/respond-1.4.2.min.js applications/welcome/static/js/share.js line length is 529 characters (>512) According to Debian Free Software Guidelines [1] (DFSG) #2: "The program must include source code, and must allow distribution in source code as well as compiled form." In some cases this could also constitute a license violation for some copyleft licenses such as the GNU GPL. (While sometimes the licence allows not to ship the source, the DFSG always mandates source code.) In order to solve this problem, you could: 1. add the source files to "debian/missing-sources" directory. 2. repack the origin tarball and add the missing source files to it. Both way satisfy the requirement to ship all source code. The second option might be preferable due to the following reasons [2]: - Upstream can do it too and you could even supply a patch to them, thus full filling our social contract [3], see particularly §2. - If source and non-source are in different locations, ftpmasters may miss the source and (needlessly) reject the package. - The source isn't duplicated in every .diff.gz/.debian.tar.* (though this only really matters for larger sources). You could also ask debian...@lists.debian.org or #debian-qa for more guidance. [1] https://www.debian.org/social_contract.en.html#guidelines [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736873#8 [3] https://www.debian.org/social_contract signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- Version: 2.12.3-1+rm Dear submitter, as the package web2py has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry tha
Bug#891220: marked as done (web2py: CVE-2016-3952 CVE-2016-3953 CVE-2016-3954 CVE-2016-3957)
Your message dated Wed, 21 Mar 2018 17:21:03 + with message-id and subject line Bug#892866: Removed package(s) from unstable has caused the Debian Bug report #891220, regarding web2py: CVE-2016-3952 CVE-2016-3953 CVE-2016-3954 CVE-2016-3957 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.) -- 891220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: web2py Version: 2.12.3-1 Severity: grave Tags: security upstream Hi, the following vulnerabilities were published for web2py. CVE-2016-3952[0]: | web2py before 2.14.1, when using the standalone version, allows remote | attackers to obtain environment variable values via a direct request | to examples/template_examples/beautify. NOTE: this issue can be | leveraged by remote attackers to gain administrative access. CVE-2016-3953[1]: | The sample web application in web2py before 2.14.2 might allow remote | attackers to execute arbitrary code via vectors involving use of a | hardcoded encryption key when calling the session.connect function. CVE-2016-3954[2]: | web2py before 2.14.2 allows remote attackers to obtain the | session_cookie_key value via a direct request to | examples/simple_examples/status. NOTE: this issue can be leveraged by | remote attackers to execute arbitrary code using CVE-2016-3957. CVE-2016-3957[3]: | The secure_load function in gluon/utils.py in web2py before 2.14.2 | uses pickle.loads to deserialize session information stored in | cookies, which might allow remote attackers to execute arbitrary code | by leveraging knowledge of encryption_key. 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-2016-3952 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3952 [1] https://security-tracker.debian.org/tracker/CVE-2016-3953 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3953 [2] https://security-tracker.debian.org/tracker/CVE-2016-3954 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3954 [3] https://security-tracker.debian.org/tracker/CVE-2016-3957 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3957 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Version: 2.12.3-1+rm Dear submitter, as the package web2py has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/892866 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#885552: marked as done (libgksu: Don't release with buster)
Your message dated Wed, 21 Mar 2018 17:20:33 + with message-id and subject line Bug#892771: Removed package(s) from unstable has caused the Debian Bug report #885552, regarding libgksu: Don't release with buster 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.) -- 885552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885552 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgksu Severity: serious Tags: sid buster User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs gksu gksu has been deprecated for years. The intent of gksu is to allow running apps with elevated privileges but the way to do that is for the app developer to use PolicyKit to request elevated privileges for the specific actions that need done instead of for the whole app to run as root. For the next major stable release of Debian (codenamed Buster), the Debian GNOME team plans to default to GNOME on Wayland where gksu does not even work. Therefore, the Debian GNOME team intends to either remove gksu or replace it with a non-functional warning message. gksu is unmaintained (last upload 2014) and is a security vulnerability. On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Version: 2.0.13~pre1-9+rm Dear submitter, as the package libgksu has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/892771 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#867236: marked as done (gksu: Unsuitable for release in buster)
Your message dated Wed, 21 Mar 2018 17:18:42 + with message-id and subject line Bug#892768: Removed package(s) from unstable has caused the Debian Bug report #867236, regarding gksu: Unsuitable for release in buster 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.) -- 867236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867236 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gksu Version: 2.0.2-9 Severity: serious Usertags: oldlibs gksu Tags: sid buster gksu has been deprecated for years. The intent of gksu is to allow running apps with elevated privileges but the way to do that is for the app developer to use PolicyKit to request elevated privileges for the specific actions that need done instead of for the whole app to run as root. For the next major stable release of Debian (codenamed Buster), the Debian GNOME team plans to default to GNOME on Wayland where gksu does not even work. Therefore, the Debian GNOME team intends to either remove gksu or replace it with a non-functional warning message. gksu is unmaintained (last upload 2014) and is a security vulnerability. On behalf of the Debian GNOME team, Jeremy --- End Message --- --- Begin Message --- Version: 2.0.2-9+rm Dear submitter, as the package gksu has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/892768 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#822603: marked as done (network-config: depends on gksu which is deprecated)
Your message dated Wed, 21 Mar 2018 17:17:30 + with message-id and subject line Bug#892767: Removed package(s) from unstable has caused the Debian Bug report #822603, regarding network-config: depends on gksu which is deprecated 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.) -- 822603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822603 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: network-config Severity: important Tags: sid stretch User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs gksu Hi, network-config depends on gksu, which is deprecated and unmaintained. Thus we want to remove it from the archive. network-config should switch to a supported and securer way to become root, particularly one that doesn't mean running your whole application as root (including the GUI), e.g. using polkit. Please try to do this before the Stretch release as we're going to try to remove gksu this cycle. We'll bump this to serious when the list of rdeps is small and we're getting ready to removing gksu completely. If you have any question don't hesitate to ask. https://www.freedesktop.org/wiki/Software/polkit/ https://wiki.debian.org/PolicyKit Cheers, Emilio --- End Message --- --- Begin Message --- Version: 0.2-2+rm Dear submitter, as the package network-config has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/892767 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#890400: Any news about a new upstream version with new SONAME?
Hi Julien, On Wed, Mar 21, 2018 at 05:25:10PM +0100, Julien Yann Dutheil wrote: > I'm starting to package libbpp-core4 from upstream. It works fine but I > have a warning because of the symbol files which are not matching. My > understanding is that this is due to your previous (unreleased) patch which > was incrementing the interface number for version 2.3.2. How can I solve > that? (basically, discard the previous symbols and use the new one instead, > as they correspond to the new "official" .so.4 version?). The build log contains a diff you can use as patch. > I have not pushed > my commits yet, let me know if you need them already. Feel free to push and ping me in case of trouble so I can fix it. Kind regards Andreas. -- http://fam-tille.de
Bug#893723: nagvis: PHP Fatal error: Redefinition of parameter $_unused_flag
Package: nagvis
Version: 1:1.7.10+dfsg1-3.2
Severity: grave
Tags: patch
Justification: renders package unusable
Dear Maintainer,
We installed the nagvis and nagvis-demos package. Opening nagvis in a browser
lead to a HTTP/500 internal server error. In the apache error log we had the
following lines:
[Wed Mar 21 16:16:45.976333 2018] [:error] [pid 28158] [client
192.168.12.252:61683] PHP Fatal error: Redefinition of parameter $_unused_flag
in /usr/share/nagvis/share/server/core/classes/objects/NagVisMapObj.php on line
247, referer:
http://kameraserver/nagvis/frontend/nagvis-js/index.php?mod=Map&act=view&show=demo-germany
We followed the advice of the user hurr1c4ne on the following forum thread:
https://monitoring-portal.org/woltlab/index.php?thread/37078-php-fatal-error-redefinition-of-parameter-unused-flag-in-usr-share-nagvis-share/
This solved the problem for us. The post of hurr1c4n is as follows:
Have the same situation on my Ubuntu 16.04.1 Server.
I just changed the following lines
/usr/share/nagvis/share/server/core/classes/objects/NagiosService.php
:103
function queueState($_unused_flag = true) {
/usr/share/nagvis/share/server/core/classes/objects/NagVisMapObj.php
:247
public function queueState($_unused_flag = true) {
After this changes, the error messages are gone and the website works as
expected.
This helped to get the demo maps running.
Best regards,
Jan
-- System Information:
Debian Release: 9.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages nagvis depends on:
ii debconf [debconf-2.0] 1.5.61
ii graphviz 2.38.0-17
ii php 1:7.0+49
ii php-common1:49
ii php-gd1:7.0+49
ii php-net-socket1.0.14-2
ii php-php-gettext 1.0.12-0.1
ii php-sqlite3 1:7.0+49
ii php7.0 [php] 7.0.27-0+deb9u1
ii php7.0-gd [php-gd]7.0.27-0+deb9u1
ii php7.0-sqlite3 [php-sqlite3] 7.0.27-0+deb9u1
ii ucf 3.0036
nagvis recommends no packages.
Versions of packages nagvis suggests:
pn check-mk-livestatus
ii nagvis-demos 1:1.7.10+dfsg1-3.2
-- debconf information:
nagvis/delete_on_purge: false
* nagvis/monitoring_system: icinga
Bug#890400: Any news about a new upstream version with new SONAME?
Dear Andreas, I'm starting to package libbpp-core4 from upstream. It works fine but I have a warning because of the symbol files which are not matching. My understanding is that this is due to your previous (unreleased) patch which was incrementing the interface number for version 2.3.2. How can I solve that? (basically, discard the previous symbols and use the new one instead, as they correspond to the new "official" .so.4 version?). I have not pushed my commits yet, let me know if you need them already. Thanks, Julien. On Wed, Mar 14, 2018 at 9:38 AM, Andreas Tille wrote: > Hi Julien, > > On Wed, Mar 14, 2018 at 09:19:51AM +0100, Julien Yann Dutheil wrote: > > I am almost done! As we were to change the soname, I took the chance to > fix > > another gcc7 issue, that is to remove all dynamic exception > specifications > > in all libraries. Got interupted by some travelling, but I plan to finish > > this by the end of this week. > > Sorry again for the delay, > > That's fine - thanks for the update > > Andreas. > > -- > http://fam-tille.de > > -- Julien Y. Dutheil, Ph-D 0 (+49) 6421 178 986 § Max Planck Institute for Evolutionary Biology Molecular Systems Evolution Department of Evolutionary Genetics Plön -- GERMANY § Institute of Evolutionary Sciences - Montpellier University of Montpellier 2 -- FRANCE
Processed: affects 893697
Processing commands for cont...@bugs.debian.org: > affects 893697 + setools Bug #893697 [python3-networkx] sesearch needs python3-lib2to3 Added indication that 893697 affects setools > thanks Stopping processing here. Please contact me if you need assistance. -- 893697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: [DSE-Dev] Bug#893697: sesearch needs python3-lib2to3
Processing commands for cont...@bugs.debian.org: > reassign 893697 python3-networkx 1.11-2 Bug #893697 [setools] sesearch needs python3-lib2to3 Bug reassigned from package 'setools' to 'python3-networkx'. No longer marked as found in versions setools/4.1.1-3. Ignoring request to alter fixed versions of bug #893697 to the same values previously set Bug #893697 [python3-networkx] sesearch needs python3-lib2to3 Marked as found in versions python-networkx/1.11-2. > severity 893697 serious Bug #893697 [python3-networkx] sesearch needs python3-lib2to3 Severity set to 'serious' from 'important' > tags 893697 + sid buster Bug #893697 [python3-networkx] sesearch needs python3-lib2to3 Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 893697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#864184: marked as done (oping: No more works as non-root)
Your message dated Wed, 21 Mar 2018 15:21:47 + with message-id and subject line Bug#864184: fixed in liboping 1.10.0-2 has caused the Debian Bug report #864184, regarding oping: No more works as non-root 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.) -- 864184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: oping Version: 1.10.0-1 Severity: important Hi, since the upload of 1.10.0-1, neither oping nor noping work as unprivileged user (i.e. non-root) anymore. noping crashes with "ping_send failed: Operation not permitted" and leaves the terminal in broken state: It doesn't seem to switch the terminal back properly into scrolling mode. Calling "reset" usually helps to fix the terminal. oping exits with exit-code 1 as follows: ~ → oping 192.168.1.232 PING 192.168.1.232 (192.168.1.232) 56 bytes of data. ping_send failed: Operation not permitted Downgrading both, oping and liboping0 suffices to fix this issue, so it was introduced in the 1.10.0-1 upload. (Just downgrading oping doesn't seem to suffice.) -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages oping depends on: ii libc6 2.24-11 ii libncursesw5 6.0+20161126-1 ii liboping0 1.10.0-1 ii libtinfo5 6.0+20161126-1 oping recommends no packages. oping suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: liboping Source-Version: 1.10.0-2 We believe that the bug you reported is fixed in the latest version of liboping, 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 864...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barak A. Pearlmutter (supplier of updated liboping 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, 21 Mar 2018 13:57:02 + Source: liboping Binary: liboping-dev liboping0 oping libnet-oping-perl Architecture: source amd64 Version: 1.10.0-2 Distribution: unstable Urgency: medium Maintainer: Sebastian Harl Changed-By: Barak A. Pearlmutter Description: libnet-oping-perl - module for ICMP latency measurement liboping-dev - C/C++ library to generate ICMP ECHO_REQUESTs (development files) liboping0 - C/C++ library to generate ICMP ECHO_REQUESTs oping - sends ICMP_ECHO requests to network hosts Closes: 864184 Changes: liboping (1.10.0-2) unstable; urgency=medium . * Bump policy * dh11 * Merge upstream bug fixes and suid fix a88c51f3 (closes: #864184) * Secure some URLs * Obay arbitrary lintian dictates Checksums-Sha1: 7e7e44f7c5c4dc0dbcc310532189a2bd21ef94e9 2048 liboping_1.10.0-2.dsc a27834a28500cb4e8818ef081a64611f29b32e3e 12212 liboping_1.10.0-2.debian.tar.xz 70432b94f243770a5725c12dc803e6626802524a 35636 libnet-oping-perl-dbgsym_1.10.0-1.21-2_amd64.deb 684aa84e7e8d405816d7a7c78a77c9aa742a230f 23820 libnet-oping-perl_1.10.0-1.21-2_amd64.deb 93f0292a3e3779b37b125ff3f01f67610da543c4 46888 liboping-dev_1.10.0-2_amd64.deb 3f9c0618426873898e93ee007a23d388186c1d38 20908 liboping0-dbgsym_1.10.0-2_amd64.deb c5e17093579ab6612bd68287bca3382a9f816c88 19500 liboping0_1.10.0-2_amd64.deb 9ad5c5613344522434f0bc96f2f8c3474a9505f5 7218 liboping_1.10.0-2_amd64.buildinfo cce24bfffeb3e238b65bf144b3e8515242008908 40164 oping-dbgsym_1.10.0-2_amd64.deb 491cb991013f5bc91f51b11b3cfa02ffcedeadf9 36664 oping_1.10.0-2_amd64.deb Checksums-Sha256: 405620e5703cb221c21eb9b64e5c909cfa09ad041cc7b60bdb4f1fe86f678116 2048 liboping_1.10.0-2.dsc 5884b5131cea17c8dbd5c33be6e8d773793045e026cf302ca24087e20fc38876 12212 liboping_1.10.0-2.debian.tar.xz 50e19976e26db34e22745d1036df6abd7ee452d0d4b468dba4dba51fabb964d2 35636 libnet-oping-p
Bug#864184: Raising severity
Just uploaded fix. > I'm happy to upload an NMU if you're busy. In the future please feel free to just NMU, 0 day, I don't mind. For historic reasons the packaging repo is on github; I should really move it to salsa Debian, and just mirror on github, to make this sort of thing easier. --Barak.
Bug#892539: pdftk: Depends on GCJ which is going away
I use pdftk regularly, and really hope we can manage to keep it in Debian. Is there a plan for adressing this before gcj is removed? -- Happy hacking Petter Reinholdtsen
Bug#681726: Time to remove eclipse from Testing?
Markus Koschany: > On Wed, 15 Nov 2017 18:01:07 +0200 Adrian Bunk wrote: > [...] >> I tried to sort out what I could find as required for getting the >> ancient eclipse out of testing in [1]: >> >> 1. src:bnd >> You fixed that already. >> >> 2. batik -> maven -> guice -> libspring-java -> aspectj -> eclipse-platform >> Is there some good way to break this dependency chain? >> >> 3. split libequinox-osgi-java out of src:eclise >> Or as a short-term hack, build only libequinox-osgi-java from src:eclipse. > > I have spent some time this weekend on Eclipse again. I have created a > standalone src:libequinox-osgi-java package and successfully rebuilt all > reverse-dependencies. We only have to make a small adjustment in > src:netbeans and src:libnb-platform18-java and update the osgi patch. > > If there are no objections I could go ahead and upload > libequinox-osgi-java to NEW. > > eclipse-rcp: > > * svnkit: > > There are two Eclipse specific classes that fail to build. As a > workaround we could remove one of them and patch SVNWCUtil. > > * android-sdktools and android-platform-tools-swt > > According to [1] both packages should be removed anyway. > > After that there would be only three packages left (not counting the > eclipse plugins) that build-depend on either eclipse-platform (aspectj) > or eclipse-jdt (lombok, biogenesis) > > Next I'm going to try if a separate eclipse-jdt package from [2] could > be a drop-in-replacement for our current package. The latest stable > release appears to be S4_8_0_M5. > > Regards, > > Markus > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879175#10 > [2] https://github.com/eclipse/eclipse.jdt.core As far as I know, android-sdktools and android-platform-tools-swt are both deprecated by Google. So it should be fine to remove them also. There is a chance that other parts of the Android SDK depend on JARs from Eclipse, but I guess that's not likely/ .hc
Bug#892964: marked as done (mercurial: CVE-2018-1000132)
Your message dated Wed, 21 Mar 2018 14:48:54 +0100 with message-id and subject line Security bugs fixed in mercurial 4.5.2-1 has caused the Debian Bug report #892964, regarding mercurial: CVE-2018-1000132 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.) -- 892964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892964 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mercurial Version: 3.1.2-1 Severity: grave Tags: security upstream Hi, the following vulnerability was published for mercurial. CVE-2018-1000132[0]: | Mercurial version 4.5 and earlier contains a Incorrect Access Control | (CWE-285) vulnerability in Protocol server that can result in | Unauthorized data access. This attack appear to be exploitable via | network connectivity. This vulnerability appears to have been fixed in | 4.5.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-1000132 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000132 [1] https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_4.5.1_.2F_4.5.2_.282018-03-06.29 Regards, Salvatore --- End Message --- --- Begin Message --- Source: mercurial Version: 4.5.2-1 Apologies for not including this in the package changelog. The 4.5.2 release (just uploaded) includes fixes for these security bugs. Cheers, Julien--- End Message ---
Bug#872225: libtss-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libtss.so -> /debian/libtss0/usr/lib/x86_64-linux-gnu/libtss.so.0
On Wed, 07 Feb 2018 23:29:36 + Luca Boccassi wrote: > On Tue, 15 Aug 2017 10:35:34 +0200 Andreas Beckmann > wrote: > > Package: libtss-dev > > Version: 1045-1 > > Severity: serious > > User: debian...@lists.debian.org > > Usertags: piuparts > > > > Hi, > > > > during a test with piuparts I noticed your package ships (or creates) > > a broken symlink. > > > > >From the attached log (scroll to the bottom...): > > > > 0m10.9s ERROR: FAIL: Broken symlinks: > > /usr/lib/x86_64-linux-gnu/libtss.so -> > /debian/libtss0/usr/lib/x86_64-linux-gnu/libtss.so.0 > > > > > > The target looks like an (incorrect) build-time path. > > > > > > cheers, > > > > Andreas > > Dear maintainer, > > The fix for this is quite simple, patch inlined. > > -- > Kind regards, > Luca Boccassi > > > --- a/debian/rules > +++ b/debian/rules > @@ -115,7 +115,7 @@ override_dh_auto_install: > dh_install -Pdebian/$(LIBPKG) -p$(LIBPKG) $(USRLIB)/$(VERSIONED_LIB) $(USRLIB) > > dh_link -Pdebian/$(LIBPKG) -p$(LIBPKG) $(USRLIB)/$(VERSIONED_LIB) $(USRLIB)/$(LIBSONAME) > - dh_link -Pdebian/$(DEVPKG) -p$(DEVPKG) debian/$(LIBPKG)/$(USRLIB)/$(LIBSONAME) $(USRLIB)/$(LIBSYM) > + dh_link -Pdebian/$(DEVPKG) -p$(DEVPKG) $(USRLIB)/$(LIBSONAME) $(USRLIB)/$(LIBSYM) > > > cp -p $(TMP)/$(MAN1)/* $(DESTMAN1) Dear Maintainer, I'm quite interested on having this package available in testing and buster, so I'll do an NMU to delayed/10 sometimes this week with the above patch unless I receive an objection. -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#892743: marked as done (permissions bypass on http server)
Your message dated Wed, 21 Mar 2018 14:48:54 +0100 with message-id and subject line Security bugs fixed in mercurial 4.5.2-1 has caused the Debian Bug report #892743, regarding permissions bypass on http server 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.) -- 892743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mercurial Version: 4.0-1+deb9u1 Severity: grave Tags: security As seen in https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_4.5.1_.2F_4.5.2_.282018-03-06.29 : All versions of Mercurial prior to 4.5.2 have vulnerabilities in the HTTP server that allow permissions bypass to: * Perform writes on repositories that should be read-only * Perform reads on repositories that shouldn't allow read access (...) the relevant changesets from 4.5.2 are 2c647da851ed::2ecb0fc535b1. These can be viewed online at e.g. https://www.mercurial-scm.org/repo/hg/rev/2ecb0fc535b1. The author of these commits has backports to 4.4 and 4.3 on a personal fork at https://hg.mozilla.org/users/gszorc_mozilla.com/hg. The backports for 4.4 are a4843835c835::7cf827e5f8af and for 4.3 are db527ae12671::86f9a022ccb8. To obtain these changesets, run e.g. hg pull -r 7cf827e5f8af https://hg.mozilla.org/users/gszorc_mozilla.com/hg. --- End Message --- --- Begin Message --- Source: mercurial Version: 4.5.2-1 Apologies for not including this in the package changelog. The 4.5.2 release (just uploaded) includes fixes for these security bugs. Cheers, Julien--- End Message ---
Bug#878101: nemo: Nemo segfault on thumbnailing of a moved file
Hello, The issue was fixed in later versions of nemo (think 3.4+, but not 100% sure), and I think this was the fix, which was already reported here: https://github.com/linuxmint/nemo/commit/b58bea5384436fda9cb6b31f7010f72d3c74e76a#diff-53011b366ae6f19d5347ce06d362d6ca I'll test your patched version and report the results. Can we expect the fix to be pushed to Stretch repos? This bug is really annoying. And man, Debian always has some buggy nemo version in stable branches - with Jessie, I switched to pcmanfm, as I couldn't live with the bugs in nemo. I'm really close to switching to pcmanfm in Stretch too, because of this bug, as nemo is almost unusable.
Bug#892468: marked as done (proftp: Prevent migration to testing)
Your message dated Wed, 21 Mar 2018 13:57:24 +0100 with message-id <20180321125724.mrlwygtjti53g...@ba.issia.cnr.it> and subject line Re: Bug#892468: proftp: Prevent migration to testing has caused the Debian Bug report #892468, regarding proftp: Prevent migration to testing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 892468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: proftpd-basic Version: 1.3.6-1 Severity: critical Justification: breaks unrelated software Dear Maintainer, for now we want to prevent the package from migrating to testing until we are sure all bugs are fixed. For now already three bugs were reported telling that some modules do not build any more: - Bug#892371: proftpd-mod-vroot FTBFS with proftpd 1.3.6-1 - Bug#892372: proftpd-mod-msg FTBFS with proftpd 1.3.6-1 - Bug#892373: proftpd-mod-fsync FTBFS with proftpd 1.3.6-1 Hilmar -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 4.15.0-1-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages proftpd-basic depends on: ii adduser3.117 ii debianutils4.8.4 ii libacl12.2.52-3+b1 ii libattr1 1:2.4.47-2+b2 ii libc6 2.27-1 ii libcap21:2.25-1.2 ii libhiredis0.13 0.13.3-2.2 ii libmemcached11 1.0.18-4.2 ii libmemcachedutil2 1.0.18-4.2 ii libncurses56.1-1 ii libpam-runtime 1.1.8-3.7 ii libpam0g 1.1.8-3.7 ii libpcre3 2:8.39-9 ii libssl1.1 1.1.0g-2 ii libtinfo5 6.1-1 ii libwrap0 7.6.q-27 ii lsb-base 9.20170808 ii netbase5.4 ii sed4.4-2 ii ucf3.0038 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages proftpd-basic recommends: pn proftpd-doc Versions of packages proftpd-basic suggests: ii openbsd-inetd [inet-superserver] 0.20160825-3 ii openssl 1.1.0g-2 pn proftpd-mod-geoip pn proftpd-mod-ldap pn proftpd-mod-mysql pn proftpd-mod-odbc pn proftpd-mod-pgsql pn proftpd-mod-sqlite -- debconf information: * shared/proftpd/inetd_or_standalone: from inetd --- End Message --- --- Begin Message --- Related erros are now fixes, so closing. On Fri, Mar 09, 2018 at 12:13:55PM +0100, Hilmar Preuße wrote: Package: proftpd-basic Version: 1.3.6-1 Severity: critical Justification: breaks unrelated software Dear Maintainer, for now we want to prevent the package from migrating to testing until we are sure all bugs are fixed. For now already three bugs were reported telling that some modules do not build any more: - Bug#892371: proftpd-mod-vroot FTBFS with proftpd 1.3.6-1 - Bug#892372: proftpd-mod-msg FTBFS with proftpd 1.3.6-1 - Bug#892373: proftpd-mod-fsync FTBFS with proftpd 1.3.6-1 -- Francesco P. Lovergine--- End Message ---
Bug#893193: marked as done (adql FTBFS with openjdk-9)
Your message dated Wed, 21 Mar 2018 13:04:21 + with message-id and subject line Bug#893193: fixed in adql 1.3-5 has caused the Debian Bug report #893193, regarding adql FTBFS with openjdk-9 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.) -- 893193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893193 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: adql Version: 1.3-4 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/adql.html ... junitValidation: [junit] Testsuite: adql.TestADQLQuery [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.279 sec [junit] [junit] Testcase: testReplace took 1.889 sec [junit] Testcase: testADQLQuery took 0.002 sec [junit] Testcase: testSearch took 0.029 sec [junit] Testsuite: adql.TestIN [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.69 sec [junit] [junit] Testcase: testIN took 1.534 sec [junit] Testsuite: adql.TestIdentifierField [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.162 sec [junit] [junit] Testcase: testIsCaseSensitive took 0.002 sec [junit] Testsuite: adql.db.TestDBChecker [junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.472 sec [junit] [junit] Testcase: testGeometry took 3.819 sec [junit] Testcase: testTypesChecking took 0.386 sec [junit] Testcase: testNumericOrStringValueExpressionPrimary took 0.074 sec [junit] Testcase: testCoordSys took 0.374 sec [junit] Testcase: testUDFManagement took 0.464 sec [junit] Testsuite: adql.db.TestFunctionDef [junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.296 sec [junit] [junit] Testcase: testCompareToFunctionDef took 0.456 sec [junit] Testcase: testIsNumeric took 0.001 sec [junit] Testcase: testParse took 1.26 sec [junit] Testcase: testToString took 0 sec [junit] Testcase: testCompareToADQLFunction took 0.126 sec [junit] Testcase: testIsGeometry took 0 sec [junit] Testcase: testIsString took 0.001 sec [junit] Testsuite: adql.db.TestSTCS [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.884 sec [junit] [junit] Testcase: buildRegion took 3.6 sec [junit] Testcase: parseCoordSys took 0.104 sec [junit] Testcase: parseRegion took 0.587 sec [junit] Testcase: serializeCoordSys took 0.075 sec [junit] Testsuite: adql.parser.TestADQLParser [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.61 sec [junit] [junit] Testcase: test took 1.369 sec [junit] Testsuite: adql.query.from.TestCrossJoin [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.584 sec [junit] [junit] Testcase: testGetDBColumns took 0.12 sec [junit] Testsuite: adql.query.from.TestInnerJoin [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.005 sec [junit] [junit] Testcase: testGetDBColumns took 0.604 sec [junit] Testsuite: adql.translator.TestPgSphereTranslator [junit] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.905 sec [junit] [junit] Testcase: testTranslateGeometryToDB took 3.118 sec [junit] FAILED [junit] expected:<...6d,0.997763534763054[3]d),(44.1514718625761...> but was:<...6d,0.997763534763054[5]d),(44.1514718625761...> [junit] junit.framework.AssertionFailedError: expected:<...6d,0.997763534763054[3]d),(44.1514718625761...> but was:<...6d,0.997763534763054[5]d),(44.1514718625761...> [junit] at adql.translator.TestPgSphereTranslator.testTranslateGeometryToDB(TestPgSphereTranslator.java:300) [junit] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [junit] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [junit] [junit] Testcase: testTranslateGeometryFromDB took 0.128 sec [junit] Testcase: testConvertTypeFromDB took 0.008 sec [junit] Testcase: testConvertTypeToDB took 0.001 sec [junit] Test adql.translator.TestPgSphereTranslator FAILED BUILD FAILED /build/1st/adql-1.3/buildADQL.xml:86: Failed JUnit validation for ADQL Lib.! Total time: 1 minute 48 seconds make[1]: *** [debian/rules:15: override_dh_auto_test] Error 1 --- End Message --- --- Begin Message --- Sou
Bug#893260: marked as done (libitext5-java FTBFS with openjdk-9)
Your message dated Wed, 21 Mar 2018 13:06:57 + with message-id and subject line Bug#893260: fixed in libitext5-java 5.5.6-3 has caused the Debian Bug report #893260, regarding libitext5-java FTBFS with openjdk-9 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.) -- 893260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893260 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libitext5-java Version: 5.5.6-2 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libitext5-java.html ... [[1;34mINFO[m] [1;32mTests run: [0;1;32m2[m, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.742 s - in com.itextpdf.text.pdf.table.[1mColorsInTaggedDocumentsTest[m [[1;34mINFO[m] Running com.itextpdf.text.error_messages.[1mErrorMessageTest[m [[1;34mINFO[m] [1;32mTests run: [0;1;32m4[m, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s - in com.itextpdf.text.error_messages.[1mErrorMessageTest[m [[1;34mINFO[m] Running com.itextpdf.text.pdf.[1mPdfReaderSelectPagesTest[m [[1;34mINFO[m] [1;32mTests run: [0;1;32m1[m, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s - in com.itextpdf.text.pdf.[1mPdfReaderSelectPagesTest[m [[1;34mINFO[m] Running com.itextpdf.text.pdf.parser.[1mTextRenderInfoTest[m [[1;33mWARNING[m] Corrupted STDOUT by directly writing to native stream in forked JVM 1. See FAQ web page and the dump file /build/1st/libitext5-java-5.5.6/target/surefire-reports/2018-03-17T02-52-09_912-jvmRun1.dumpstream [[1;34mINFO[m] [[1;34mINFO[m] Results: [[1;34mINFO[m] [[1;33mWARNING[m] [1;33mTests run: 73, Failures: 0, Errors: 0, Skipped: 2[m [[1;34mINFO[m] [[1;34mINFO[m] [1m[m [[1;34mINFO[m] [1;31mBUILD FAILURE[m [[1;34mINFO[m] [1m[m [[1;34mINFO[m] Total time: 03:28 min [[1;34mINFO[m] Finished at: 2018-03-17T02:52:54-12:00 [[1;34mINFO[m] Final Memory: 21M/72M [[1;34mINFO[m] [1m[m [[1;31mERROR[m] Failed to execute goal [32morg.apache.maven.plugins:maven-surefire-plugin:2.20.1:test[m [1m(default-test)[m on project [36mitextpdf[m: [1;31mThere are test failures.[m [[1;31mERROR[m] [1;31m[m [[1;31mERROR[m] [1;31mPlease refer to /build/1st/libitext5-java-5.5.6/target/surefire-reports for the individual test results.[m [[1;31mERROR[m] [1;31mPlease refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.[m [[1;31mERROR[m] [1;31mThe forked VM terminated without properly saying goodbye. VM crash or System.exit called?[m [[1;31mERROR[m] [1;31mCommand was /bin/sh -c cd /build/1st/libitext5-java-5.5.6 && /usr/lib/jvm/java-9-openjdk-amd64/bin/java --add-modules java.se.ee -Xms512m -Xmx1024m -jar /build/1st/libitext5-java-5.5.6/target/surefire/surefirebooter6685411707041150823.jar /build/1st/libitext5-java-5.5.6/target/surefire 2018-03-17T02-52-09_912-jvmRun1 surefire5377113704316930954tmp surefire_012190913596490826417tmp[m [[1;31mERROR[m] [1;31mError occurred in starting fork, check output in log[m [[1;31mERROR[m] [1;31mProcess Exit Code: 134[m [[1;31mERROR[m] [1;31mCrashed tests:[m [[1;31mERROR[m] [1;31mcom.itextpdf.text.pdf.parser.TextRenderInfoTest[m [[1;31mERROR[m] [1;31morg.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?[m [[1;31mERROR[m] [1;31mCommand was /bin/sh -c cd /build/1st/libitext5-java-5.5.6 && /usr/lib/jvm/java-9-openjdk-amd64/bin/java --add-modules java.se.ee -Xms512m -Xmx1024m -jar /build/1st/libitext5-java-5.5.6/target/surefire/surefirebooter6685411707041150823.jar /build/1st/libitext5-java-5.5.6/target/surefire 2018-03-17T02-52-09_912-jvmRun1 surefire5377113704316930954tmp surefire_012190913596490826417tmp[m [[1;31mERROR[m] [1;31mError occurred in starting fork, check output in log[m [[1;31mERROR[m] [1;31mProcess Exit Code: 134[m [[1;31mERROR[m] [1;31mCrashed tests:[m [[1;31mERROR[m] [1;31mcom.itextpdf.text.pdf.parser.TextRenderInfoTest[m [[1;31mERROR[m] [1;31m at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:686)[m [[1;31mERROR[m] [1;31m at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535)[m [[1;31mERROR
Bug#893704: please remove dependency pdftk (will be removed when GCJ is removed)
Package: src:impressive Version: 0.12.0-1 Severity: serious Tags: sid buster patch please remove the dependency on pdftk (will be removed when GCJ is removed). patch to build without pdftk: http://launchpadlibrarian.net/361431082/impressive_0.12.0-1_0.12.0-1ubuntu1.diff.gz
Bug#893668: adminer: CVE-2018-7667
Hi Salvatore, > I think there litte which upstream could do in addition to what was > done in 4.4.0 upstream do mitigate the issue, or am I missing > something? I agree. I filed this bug mostly to track the uploads to wheezy, jessie, jessie-backports and stretch :) Can I get an ACK from you to upload those to *-security? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#893703: sdaps depends on pdftk (likely to be removed when gcj is removed)
Package: src:sdaps Version: 1.2.1-1 Severity: serious Tags: sid buster sdaps depends on pdftk (likely to be removed when gcj is removed). The sources mention that it can be built with pyPDF instead, however it doesn't work with the python-pypdf2 package in Debian.
Bug#893702: Please stop build-depending on pdftk
Package: src:diffoscope Version: 91 Severity: serious Tags: sid buster patch pdftk still still depends on GCJ, and is likely to be removed when gcj is removed. Please stop build-depending on pdftk. patch at http://launchpadlibrarian.net/361431924/diffoscope_91build1_91ubuntu1.diff.gz
Bug#893701: kamailio-java-modules package (GCJ based) needs to be removed or ported to OpenJDK
Package: src:kamailio Version: 5.1.2-1 Severity: serious Tags: sid buster patch GCJ is removed in unstable. Please remove kamailio-java-modules package (GCJ based) or port it to OpenJDK. A patch for removal: http://launchpadlibrarian.net/361439657/kamailio_5.1.2-1ubuntu1_5.1.2-1ubuntu2.diff.gz
Processed: Re: [buildd-tools-devel] Bug#893691: sbuild: Missing Depends on lintian after defaults change
Processing control commands: > forcemerge -1 893226 Bug #893691 [sbuild] sbuild: Missing Depends on lintian after defaults change Bug #893226 [sbuild] sbuild: Error reading configuration: LINTIAN binary 'lintian' does not exist Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' Bug #893315 [sbuild] sbuild's autopkgtests fail due to the lack of a lintian dependency Merged 893226 893315 893691 -- 893226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893226 893315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893315 893691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893664: sambamba: Fails to build on i386
Control: forwarded -1 https://github.com/biod/sambamba/issues/344 Control: tags -1 upstream Hi, I'm just quoting Matthias Klumpp about this bug: On Tue, Mar 20, 2018 at 06:16:54PM +0100, Matthias Klumpp wrote: > > Just in case you are wondering and because I just came across the > FTBFS: The current Sambamba build failure on i386 is highly likely an > upstream bug. > They apparently didn't account for people wanting to compile Sambamba > on a non-64bit architecture, so it likely makes sense to raise this > issue upstream. Thus I have opened an issue upstream[1]. Kind regards Andreas. [1] https://github.com/biod/sambamba/issues/344 -- http://fam-tille.de
Bug#893691: [buildd-tools-devel] Bug#893691: sbuild: Missing Depends on lintian after defaults change
Control: forcemerge -1 893226 On Wed, Mar 21, 2018 at 09:21:58AM +, James Clarke wrote: > Hi, > Now that lintian defaults to enabled in 0.74.0-1, sbuild by default will > need lintian installed, but it has no dependency on it, and thus fails > with: > > > Error reading configuration: LINTIAN binary 'lintian' does not exist or is > > not executable at /usr/share/perl5/Sbuild/Conf.pm line 76 Already reported. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Processed: Re: sambamba: Fails to build on i386
Processing control commands: > forwarded -1 https://github.com/biod/sambamba/issues/344 Bug #893664 [src:sambamba] sambamba: Fails to build on i386 Set Bug forwarded-to-address to 'https://github.com/biod/sambamba/issues/344'. > tags -1 upstream Bug #893664 [src:sambamba] sambamba: Fails to build on i386 Added tag(s) upstream. -- 893664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893664 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893696: libgtk-3-0: All wayland clients crash (seems to happen when the screen was locked for a while)
Control: forwarded -1 https://gitlab.gnome.org/GNOME/gtk/issues/114 Control: tags -1 + pending fixed-upstream On Wed, 21 Mar 2018 at 11:08:18 +0100, Marcus Lundblad wrote: > libgtk-3-0: All wayland clients crash (seems to happen when the screen was > locked for a while) > > This seems to be this upstream issue > https://gitlab.gnome.org/GNOME/gtk/issues/114 I've pushed the upstream patches to the packaging git repository, along with a couple of other upstream fixes from the 3.22.x branch. I'm not able to release this right now, but other GNOME team members are welcome to do so. I don't seem to get this myself - GNOME Terminal reliably keeps running across long periods of the screen being locked. Do you have an unusual input method configured, or anything else that would cause you to be able to reproduce this crash when I can't? For now I've described it in the changelog as "Wayland client crashes under unspecified circumstances". smcv
Processed: Re: Bug#893696: libgtk-3-0: All wayland clients crash (seems to happen when the screen was locked for a while)
Processing control commands: > forwarded -1 https://gitlab.gnome.org/GNOME/gtk/issues/114 Bug #893696 [libgtk-3-0] libgtk-3-0: All wayland clients crash (seems to happen when the screen was locked for a while) Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/gtk/issues/114'. > tags -1 + pending fixed-upstream Bug #893696 [libgtk-3-0] libgtk-3-0: All wayland clients crash (seems to happen when the screen was locked for a while) Added tag(s) fixed-upstream. -- 893696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893696: Bug #893696 in gtk+3.0 marked as pending
Control: tag -1 pending Hello, Bug #893696 in gtk+3.0 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/gtk3/commit/22a5d9c3b310e5195084f5ed6c42685b6cd37aa1 Add patches from upstream fixing Wayland client crashes under unspecified circumstances (Closes: #893696) (this message was generated automatically) -- Greetings https://bugs.debian.org/893696
Processed: Bug #893696 in gtk+3.0 marked as pending
Processing control commands: > tag -1 pending Bug #893696 [libgtk-3-0] libgtk-3-0: All wayland clients crash (seems to happen when the screen was locked for a while) Added tag(s) pending. -- 893696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#868202: Remove build-depends and depends on python3-trollius
Hi Iain, python3-trollius is still a dependency of python3-qtile, probably an oversight! Also, I would be glad to help you maintaining qtile if you need so - even if I'm not yet a DD. Thanks in advance, Jérôme signature.asc Description: OpenPGP digital signature
Processed: severity of 893696 is grave
Processing commands for cont...@bugs.debian.org: > severity 893696 grave Bug #893696 [libgtk-3-0] libgtk-3-0: All wayland clients crash (seems to happen when the screen was locked for a while) Severity set to 'grave' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 893696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#893696: libgtk-3-0: All wayland clients crash (seems to happen when the screen was locked for a while)
Package: libgtk-3-0 Version: 3.22.29-1 Severity: critical Tags: upstream Justification: causes serious data loss This seems to be this upstream issue https://gitlab.gnome.org/GNOME/gtk/issues/114 Thanks, Marcus -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8), LANGUAGE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libgtk-3-0 depends on: ii adwaita-icon-theme 3.28.0-1 ii hicolor-icon-theme 0.17-1 ii libatk-bridge2.0-0 2.26.2-1 ii libatk1.0-0 2.28.1-1 ii libc6 2.27-2 ii libcairo-gobject2 1.15.10-1 ii libcairo2 1.15.10-1 ii libcolord2 1.3.3-2 ii libcups22.2.6-5 ii libepoxy0 1.4.3-1 ii libfontconfig1 2.12.6-0.1 ii libfreetype62.8.1-2 ii libgdk-pixbuf2.0-0 2.36.11-1 ii libglib2.0-02.54.3-2 ii libgtk-3-common 3.22.29-1 ii libjson-glib-1.0-0 1.4.2-3 ii libpango-1.0-0 1.40.14-1 ii libpangocairo-1.0-0 1.40.14-1 ii libpangoft2-1.0-0 1.40.14-1 ii librest-0.7-0 0.8.0-2 ii libsoup2.4-12.62.0-1 ii libwayland-client0 1.14.0-2 ii libwayland-cursor0 1.14.0-2 ii libwayland-egl1-mesa [libwayland-egl1] 17.3.6-1 ii libx11-62:1.6.4-3 ii libxcomposite1 1:0.4.4-2 ii libxcursor1 1:1.1.15-1 ii libxdamage1 1:1.1.4-3 ii libxext62:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxi6 2:1.7.9-1 ii libxinerama12:1.1.3-1+b3 ii libxkbcommon0 0.8.0-1 ii libxml2 2.9.4+dfsg1-6.1 ii libxrandr2 2:1.5.1-1 ii shared-mime-info1.9-2 Versions of packages libgtk-3-0 recommends: ii libgtk-3-bin 3.22.29-1 Versions of packages libgtk-3-0 suggests: ii gvfs 1.34.1-2 ii librsvg2-common 2.40.20-2 -- debconf-show failed
Bug#892072: marked as done (weechat: build against ruby2.5)
Your message dated Wed, 21 Mar 2018 10:02:21 + with message-id and subject line Bug#892072: fixed in weechat 2.1-1 has caused the Debian Bug report #892072, regarding weechat: build against ruby2.5 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.) -- 892072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892072 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: weechat Version: 1.9.1-1 Severity: serious Justification: will FTBFS soon Tags: patch Hi, I am about to upload ruby-defaults to unstable, switching the default Ruby to ruby2.5, and ruby2.3 support will be removed right after that. Please consider applying the attached patch, obtained from upstream. Even better: please work with upstream to be able to build against the default ruby, instead of hardcoding a list of ruby versions. Otherwise, every time there is a Ruby transition, weechat will be a blocker. Hunting down these issues is quite time consuming. -- 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.15.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 From cb98f528301c422bdf990bdba1108e53a86ea4db Mon Sep 17 00:00:00 2001 From: Jakub Jirutka Date: Tue, 26 Dec 2017 18:30:18 +0100 Subject: [PATCH] core: add detection for Ruby 2.5 --- cmake/FindRuby.cmake | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cmake/FindRuby.cmake b/cmake/FindRuby.cmake index 673dde716..49bce219a 100644 --- a/cmake/FindRuby.cmake +++ b/cmake/FindRuby.cmake @@ -33,7 +33,7 @@ endif() find_package(PkgConfig) if(PKG_CONFIG_FOUND) - pkg_search_module(RUBY ruby-2.4 ruby-2.3 ruby-2.2 ruby-2.1 ruby-2.0 ruby-1.9 ruby-1.8) + pkg_search_module(RUBY ruby-2.5 ruby-2.4 ruby-2.3 ruby-2.2 ruby-2.1 ruby-2.0 ruby-1.9 ruby-1.8) endif() if(RUBY_FOUND) @@ -41,7 +41,7 @@ if(RUBY_FOUND) mark_as_advanced(RUBY_LIB) else() find_program(RUBY_EXECUTABLE -NAMES ruby2.4.0 ruby240 ruby2.4 ruby2.3.0 ruby230 ruby2.3 ruby23 ruby2.2.3 ruby223 ruby2.2.2 ruby222 ruby2.2.1 ruby221 ruby2.2.0 ruby220 ruby2.2 ruby22 ruby2.1.7 ruby217 ruby2.1.6 ruby216 ruby2.1.5 ruby215 ruby2.1.4 ruby214 ruby2.1.3 ruby213 ruby2.1.2 ruby212 ruby2.1.1 ruby211 ruby2.1.0 ruby210 ruby2.1 ruby21 ruby2.0 ruby20 ruby1.9.3 ruby193 ruby1.9.2 ruby192 ruby1.9.1 ruby191 ruby1.9 ruby19 ruby1.8 ruby18 ruby +NAMES ruby2.5.0 ruby250 ruby2.5 ruby2.4.0 ruby240 ruby2.4 ruby2.3.0 ruby230 ruby2.3 ruby23 ruby2.2.3 ruby223 ruby2.2.2 ruby222 ruby2.2.1 ruby221 ruby2.2.0 ruby220 ruby2.2 ruby22 ruby2.1.7 ruby217 ruby2.1.6 ruby216 ruby2.1.5 ruby215 ruby2.1.4 ruby214 ruby2.1.3 ruby213 ruby2.1.2 ruby212 ruby2.1.1 ruby211 ruby2.1.0 ruby210 ruby2.1 ruby21 ruby2.0 ruby20 ruby1.9.3 ruby193 ruby1.9.2 ruby192 ruby1.9.1 ruby191 ruby1.9 ruby19 ruby1.8 ruby18 ruby PATHS /usr/bin /usr/local/bin /usr/pkg/bin ) if(RUBY_EXECUTABLE) signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: weechat Source-Version: 2.1-1 We believe that the bug you reported is fixed in the latest version of weechat, 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 892...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bouthenot (supplier of updated weechat 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, 21 Mar 2018 07:46:21 +0100 Source: weechat Binary: weechat weechat-curses weechat-headless weechat-core weechat-plugins weechat-python weechat-perl weechat-ruby weechat-lua weechat-tcl weechat-guile weechat-javascript weechat-php weechat-doc weechat-dev Architecture: source amd64 all Version: 2.1-1 Distribution: unstable Urgency: medium Maintainer: Emmanuel Bouthenot Changed-By: Emmanuel Bouthenot Description: weechat- Fast, light and extensible chat cli
Bug#893245: marked as done (sahara-dashboard: Cannot fulfill the build dependencies)
Your message dated Wed, 21 Mar 2018 10:02:16 + with message-id and subject line Bug#893245: fixed in sahara-dashboard 8.0.0-1 has caused the Debian Bug report #893245, regarding sahara-dashboard: Cannot fulfill the build 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.) -- 893245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sahara-dashboard Version: 5.0.0-1 Severity: serious Tags: buster sid The following packages have unmet dependencies: builddeps:sahara-dashboard : Depends: python-django-openstack-auth (>= 2.4.1) but it is not going to be installed This is dues to the OpenStack Python 2 -> 3. --- End Message --- --- Begin Message --- Source: sahara-dashboard Source-Version: 8.0.0-1 We believe that the bug you reported is fixed in the latest version of sahara-dashboard, 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 893...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated sahara-dashboard package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 12 Mar 2018 14:28:25 +0100 Source: sahara-dashboard Binary: python3-sahara-dashboard Architecture: source all Version: 8.0.0-1 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Description: python3-sahara-dashboard - OpenStack data processing cluster as a service - dashboard plugin Closes: 893245 Changes: sahara-dashboard (8.0.0-1) unstable; urgency=medium . [ Thomas Goirand ] * Added missing EPOC in (build-)depends: openstack-dashboard. * New upstream release: - Doesn't depend on django-openstack-auth (Closes: #893245). * Fixed (build-)depends for this release. * Switched to Python 3. * Removed all patches applied upstream. . [ Ondřej Nový ] * d/rules: Removed UPSTREAM_GIT with default value * d/control: Set Vcs-* to salsa.debian.org . [ Daniel Baumann ] * Updating copyright format url. * Updating maintainer field. * Running wrap-and-sort -bast. * Removing gbp.conf, not used anymore or should be specified in the developers dotfiles. * Correcting permissions in debian packaging files. * Deprecating priority extra as per policy 4.0.1. Checksums-Sha1: 8db0428a2d1d572110f563dc204ee3cda060ff91 2965 sahara-dashboard_8.0.0-1.dsc 04113d6819dde4f9ee51e5b071b97953d567ed07 179256 sahara-dashboard_8.0.0.orig.tar.xz b3dada5bbd08836a83b34413f8e637b579bff285 3428 sahara-dashboard_8.0.0-1.debian.tar.xz 3680d3c357221dcbf950add820f5c5aa0c18a631 97728 python3-sahara-dashboard_8.0.0-1_all.deb ec1f42f6b7c91c95ce23efd2a30d049e46109da0 17937 sahara-dashboard_8.0.0-1_amd64.buildinfo Checksums-Sha256: a6c4b6eb45d06019f9240f72bacc72b3008f623e24876dc8df6e431e951084c5 2965 sahara-dashboard_8.0.0-1.dsc bb4ee8a4828bd07e78ec7b5cb7e56004fd2f248f3b334ef9544358a175eefe1f 179256 sahara-dashboard_8.0.0.orig.tar.xz e32163f25003a7821517ad4a057ade92cafea5bff559dee7a091a084c2c668ac 3428 sahara-dashboard_8.0.0-1.debian.tar.xz 13a37b66d8857e12234f1eadfa97438202cc096219ccf7aceeb88d1b18b7f1cc 97728 python3-sahara-dashboard_8.0.0-1_all.deb 4154aacba8165cf00bcca7b639af7bde06e2c31b591b97aae6b752bcfed14ec6 17937 sahara-dashboard_8.0.0-1_amd64.buildinfo Files: 6258d8acc342da7a89c4c04b1c2cbd51 2965 python optional sahara-dashboard_8.0.0-1.dsc 1c3fd97c7da2e4c308b08ffc0abb545a 179256 python optional sahara-dashboard_8.0.0.orig.tar.xz 3ed1d0e66170ca04ea49080d251c6a84 3428 python optional sahara-dashboard_8.0.0-1.debian.tar.xz 9252faa21653fbaf6814efea543278a7 97728 python optional python3-sahara-dashboard_8.0.0-1_all.deb d5f5689d216713bfe6184b8ae99127b1 17937 python optional sahara-dashboard_8.0.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEtKCq/KhshgVdBnYUq1PlA1hod6YFAlquTEYACgkQq1PlA1ho d6Y1YA/9EmMF/2XxXNcWjUkQlelrsuVOI8h/psOGo2RvpLgkQ0jrJfkkNKl8PsU/ 9LunkQ0bFXnkorhE1IiJMuhYzaqdMYpT6+1h2tg1VD0oN9Zj7Xyi2ws/8mKg4RbC 0tGf1C7pu3vIRpKe8hh4w4QtyiL5xUexfgY6gVqTWd0VWI+QmNMQp621zYpItY/p tk6tDJBT1Yqbq3Sr1swlsz/nULtSIvaicmVeGNRUUExvimvi
Bug#892881: marked as done (python-networking-arista build-depends on cruft package python-neutron)
Your message dated Wed, 21 Mar 2018 10:02:09 + with message-id and subject line Bug#892881: fixed in networking-arista 2017.2.2-1 has caused the Debian Bug report #892881, regarding python-networking-arista build-depends on cruft package python-neutron 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.) -- 892881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892881 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-networking-arista Severity: serious Tags: buster, sid python-networking arista depends on python-neutron which is no longer built by the neutron source package. It appears to have been replaced by python3-neutron. --- End Message --- --- Begin Message --- Source: networking-arista Source-Version: 2017.2.2-1 We believe that the bug you reported is fixed in the latest version of networking-arista, 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 892...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated networking-arista 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: Tue, 20 Mar 2018 22:22:58 +0100 Source: networking-arista Binary: python3-networking-arista Architecture: source all Version: 2017.2.2-1 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Description: python3-networking-arista - OpenStack virtual network service - Arista plugin Closes: 892881 Changes: networking-arista (2017.2.2-1) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org . [ Thomas Goirand ] * New upstream release. * Switched to Python 3 (Closes: #892881). Checksums-Sha1: 3d10e1facccd3342aeac9bec5a4a2f8cbe7e91d5 2697 networking-arista_2017.2.2-1.dsc b226ba213e923f6f13bb8bbafcc3ad93893d44d1 69060 networking-arista_2017.2.2.orig.tar.xz 9687ae048cef0b3a1d6e46e370f5b0c8682fedee 2920 networking-arista_2017.2.2-1.debian.tar.xz a77256fc4373e74df14e208d323c952520ed55ec 15701 networking-arista_2017.2.2-1_amd64.buildinfo 96ba85c62a331e8374dd2722d88f7e62d4835248 4820 python3-networking-arista_2017.2.2-1_all.deb Checksums-Sha256: cdab73d1cccfcdc88c10ec7ac4bbb82f84f723a3556c36f26b1b062d271c5a8c 2697 networking-arista_2017.2.2-1.dsc 1cea9d973ba10698d46c45e9d2852d3393d46222995528c562fffbc6c8f4287f 69060 networking-arista_2017.2.2.orig.tar.xz f70e3ae6363c526bfad98ec1aefe60fe53ab2095b91447ce3ea6aa48c30b81ac 2920 networking-arista_2017.2.2-1.debian.tar.xz 8ec25e807eb63661e0d0c430633ff0476c9d6295df9b0e1c8176484f09ef777e 15701 networking-arista_2017.2.2-1_amd64.buildinfo 72bf34a108bd701cafff4bbebc0e3cdc4427d9b3f9907ccae1d156bf42f3588e 4820 python3-networking-arista_2017.2.2-1_all.deb Files: d634eedda6f524a1d90b35dfa05ebe55 2697 net optional networking-arista_2017.2.2-1.dsc 8966ac005c88be2e7baa5e590aca5e57 69060 net optional networking-arista_2017.2.2.orig.tar.xz 600f9512a2cdd5fd75713e4616915e85 2920 net optional networking-arista_2017.2.2-1.debian.tar.xz 7b7b0a123d867955c40915ef901ecfc3 15701 net optional networking-arista_2017.2.2-1_amd64.buildinfo 103861fd399dc081f3f2f73c48ade32d 4820 python optional python3-networking-arista_2017.2.2-1_all.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtKCq/KhshgVdBnYUq1PlA1hod6YFAlqxfq8ACgkQq1PlA1ho d6bH2RAAhiWiFqbcilUwLOps2rwkhUOiXj/xg11DPAhgVaxDZFR1zL8paVtvnnRS Mn66DgDdN76Nk0NLCfh7QAwcKErXWC7ssikEB0QkPD/DZdNBxlMX3yImy16t5MsY 8ALG+TsPG4N/Dif++Ps90bdjD9uRnNjn5wgVlGttmSj/M34VnaFJguXOCGkm6n1T XeWhcN1f/uIsN5z5ojKZc7hdyAHY5x53sMsC1Q0Z32X7G0AonldUwyS3V1AAY+Ge WTr7P9LkLKcIvAlMWHMpe2FfmX7bHo0ym+C/+YgzbgvXsIRulDUjwMjS1ZOOt6nK qkty9I++P6GsC0X19W3vUwjh3fxnrzMOT7DSO1QjGO1wP/KoK+FsGeoITeDU3i9E hzbWHiSIvAFyDH54k97yQP3MLbC+Vch8RO8Sh75aman0QPtfndWAU4maaJkWOpw6 u2FEfcrKKCsjjFmV7NXOfv5mQmiju78EAKZGyMrhwwGfYA6m1jYa1l5d8k88PAPP ZG8VqRqSC3lstRBxmTE2Bf8Spv67Lzw4yqaUV23s+SY063xnWFjyHnTJyd8WNiyQ zzAMkuU4DHHhRaJUY4B+JS6slPJhcJ0aYi2wjs4sT08dJ3kqrCl3RR3y93Bxj8Aw +rGx1BhK/GmzjHor+aUa/gh+SK/2nw+gneFKtICOyJQVHbpbaMo= =9zbH -END PGP SIGNATURE End Message ---
Bug#875336: FTBFS with Java 9: _ as identifier
On Tue, 20 Mar 2018 23:07:13 +0800 =?UTF-8?B?5q635ZWf6IGwIHwgS2FpLUNodW5nIFlhbg==?= wrote: > I just tried building it and Groovy was fine enough, but now Gradle > complains > > Theoretically, ALL Gradle packages FTBFS since the current version is too old > to play with Java 9's fancy version number. Please take a look at the debdiff I attached to #873227 [1]. I would like to get some feedback if it fixes these additional FTBFS. [1] https://bugs.debian.org/873227
Bug#873227: Please upgrade to 4.1: Java 9 support
Please see the attached debdiff to enable some basic OpenJDK 9 support
for gradle 3.4.1. The patches were downloaded from gradle upstream to
prevent the dreadful "Could not determine java version from '9.0.x'".
After applying the patches and rebuilding with OpenJDK 8, gradle can
then build itself with openjdk 9. I have also rebuild groovy, gant,
spock (FTBFS due to source/target 1.5), and dom4j (FTBFS due to
failing tests) which all previously failed.
Hopefully this should unblock #875336.
Please note that the debdiff includes the fix for #893487 for convenience.
thanks
On Fri, 25 Aug 2017 17:01:23 +0100 Chris West
wrote:
> Source: gradle
> Version: 3.2.1-1
> Severity: normal
> User: debian-j...@lists.debian.org
> Usertags: default-java9
>
> Gradle doesn't officially support running under Java 9 until 4.1, which
> was released a fortnight ago.
>
> The version in Debian seems to actually be much better at surviving real
> builds than other random versions of Gradle I have lying around, but it
> would still be nice totally eliminate this as a java-9 blocker.
>
> Cheers,
> Chris.
>
>
>
diff -Nru gradle-3.4.1/debian/changelog gradle-3.4.1/debian/changelog
--- gradle-3.4.1/debian/changelog 2017-11-29 16:09:02.0 +0100
+++ gradle-3.4.1/debian/changelog 2018-03-19 12:19:49.0 +0100
@@ -1,3 +1,15 @@
+gradle (3.4.1-3) UNRELEASED; urgency=medium
+
+ * d/p/cast-estimated-runtime-to-long.patch: fix FTBFS due to missing cast.
+(Closes: #893487)
+ * d/p/support-running-gradle-on-jdk-10-500485df3a18.patch,
+d/p/add-test-case-for-10-internal_c1fe5e40a76b.patch,
+d/p/support-zulu9-version-number_d9c35cf9d74c.patch: prevent failures when
+building projects with openjdk 9.
+
+
+ -- Tiago Stürmer Daitx Mon, 19 Mar 2018 11:19:49 +
+
gradle (3.4.1-2) experimental; urgency=medium
* Team upload.
diff -Nru gradle-3.4.1/debian/patches/add-test-case-for-10-internal_c1fe5e40a76b.patch gradle-3.4.1/debian/patches/add-test-case-for-10-internal_c1fe5e40a76b.patch
--- gradle-3.4.1/debian/patches/add-test-case-for-10-internal_c1fe5e40a76b.patch 1970-01-01 01:00:00.0 +0100
+++ gradle-3.4.1/debian/patches/add-test-case-for-10-internal_c1fe5e40a76b.patch 2018-03-19 12:19:49.0 +0100
@@ -0,0 +1,21 @@
+From c1fe5e40a76b79a98e8916c2ce3b4e1e6ed3f343 Mon Sep 17 00:00:00 2001
+From: Cedric Champeau
+Date: Thu, 13 Jul 2017 16:16:46 +0200
+Subject: [PATCH] Add test case for `10-internal`
+
+---
+ .../base-services/src/test/groovy/org/gradle/api/JavaVersionSpec.groovy | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/subprojects/base-services/src/test/groovy/org/gradle/api/JavaVersionSpec.groovy b/subprojects/base-services/src/test/groovy/org/gradle/api/JavaVersionSpec.groovy
+index 75459ed3f06..fbb243ba992 100644
+--- a/subprojects/base-services/src/test/groovy/org/gradle/api/JavaVersionSpec.groovy
b/subprojects/base-services/src/test/groovy/org/gradle/api/JavaVersionSpec.groovy
+@@ -65,6 +65,7 @@ public class JavaVersionSpec extends Specification {
+ JavaVersion.toVersion("9-ea") == JavaVersion.VERSION_1_9
+
+ JavaVersion.toVersion("10-ea") == JavaVersion.VERSION_1_10
++JavaVersion.toVersion("10-internal") == JavaVersion.VERSION_1_10
+ }
+
+ def convertClassVersionToJavaVersion() {
diff -Nru gradle-3.4.1/debian/patches/cast-estimated-runtime-to-long.patch gradle-3.4.1/debian/patches/cast-estimated-runtime-to-long.patch
--- gradle-3.4.1/debian/patches/cast-estimated-runtime-to-long.patch 1970-01-01 01:00:00.0 +0100
+++ gradle-3.4.1/debian/patches/cast-estimated-runtime-to-long.patch 2018-03-19 12:15:47.0 +0100
@@ -0,0 +1,22 @@
+Description: gradle 3.4.1 FTBFS with a missing cast to long
+ estimatedRuntime must be cast to long otherwise gradle 3.4.1 FTBFS with
+ buildSrc/src/main/groovy/org/gradle/testing/DistributedPerformanceTest.groovy:
+ 134: [Static type checking] - Cannot assign value of type java.math.BigDecimal
+ to variable of type long.
+Author: Tiago Stürmer Daitx
+Bug-Debian: https://bugs.debian.org/893487
+Forwarded: no
+Last-Update: 2018-03-19
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/buildSrc/src/main/groovy/org/gradle/testing/DistributedPerformanceTest.groovy
b/buildSrc/src/main/groovy/org/gradle/testing/DistributedPerformanceTest.groovy
+@@ -131,7 +131,7 @@ class DistributedPerformanceTest extends
+ def scenarios = scenarioList.readLines()
+ .collect { line ->
+ def parts = Splitter.on(';').split(line).toList()
+-new Scenario(id : parts[0], estimatedRuntime: new BigDecimal(parts[1]), templates: parts.subList(2, parts.size()))
++new Scenario(id : parts[0], estimatedRuntime: new BigDecimal(parts[1]) as long, templates: parts.subList(2, parts.size()))
+ }
+ .sort{ -it.estimatedRuntime }
+
diff -Nru gradle-3.4.1/debian/patches/series gradle-3.4.1/debian/patches/series
--- gradle-
Bug#893691: sbuild: Missing Depends on lintian after defaults change
Package: sbuild Version: 0.74.0-1 Severity: serious Hi, Now that lintian defaults to enabled in 0.74.0-1, sbuild by default will need lintian installed, but it has no dependency on it, and thus fails with: > Error reading configuration: LINTIAN binary 'lintian' does not exist or is > not executable at /usr/share/perl5/Sbuild/Conf.pm line 76 Please fix this (I don't care if it's Depends or the default) so sbuild isn't broken out of the box. James
Bug#872077: marked as done ([xtables-addons-dkms] Error building against Linux 4.12)
Your message dated Wed, 21 Mar 2018 09:21:55 + with message-id and subject line Bug#872077: fixed in xtables-addons 3.0-0.1 has caused the Debian Bug report #872077, regarding [xtables-addons-dkms] Error building against Linux 4.12 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.) -- 872077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xtables-addons-dkms Version: 2.12-0.1 Severity: grave Hello! Same issue as #851576: cannot build xtables-addons-dkms against Linux 4.12. Please consider packaging xtables-addons 2.13 (released 29 Jun 2017), which has support for Linux 4.12 and successfully builds with new kernel. No critical changes in Debian source package are required so far. NMU is acceptable choice (like Ben Hutchings did in #851576). -- SY, Konstantin Demin --- End Message --- --- Begin Message --- Source: xtables-addons Source-Version: 3.0-0.1 We believe that the bug you reported is fixed in the latest version of xtables-addons, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 872...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mateusz Łukasik (supplier of updated xtables-addons 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: Tue, 13 Mar 2018 18:45:14 +0100 Source: xtables-addons Binary: xtables-addons-common xtables-addons-dkms xtables-addons-source Architecture: source amd64 all Version: 3.0-0.1 Distribution: unstable Urgency: medium Maintainer: Pierre Chifflier Changed-By: Mateusz Łukasik Description: xtables-addons-common - Extensions targets and matches for iptables [tools, libs] xtables-addons-dkms - Extensions targets and matches for iptables xtables-addons-source - Extensions targets and matches for iptables [modules sources] Closes: 866673 872077 877362 Changes: xtables-addons (3.0-0.1) unstable; urgency=medium . * Non-maintainer upload. . [ Dominik George ] * New upstream release + Support for Linux 4.12, 4.13, 4.14 (Closes: #872077) + Fix buffer overflow in xt_DNETMAP (Closes: #877362) * Update Standards-Version and compat level. + Remove explicit dependency on dh-autoreconf. . [ Mateusz Łukasik ] * New upstream release 3.0. . [ Helmut Grohne ] * Fix FTCBFS: cross.patch (Closes: #866673) Checksums-Sha1: 3294707921ce2213855e5e639be049ca687cbd7c 2169 xtables-addons_3.0-0.1.dsc f1284df76b7da98331ce47fdeb4260169aaccd83 321960 xtables-addons_3.0.orig.tar.xz b6edfdda8b2bb9de6cbf7b5367440a4ed5553317 11216 xtables-addons_3.0-0.1.debian.tar.xz 616d7057a1de8421194e09f8cad49d250212a778 169040 xtables-addons-common-dbgsym_3.0-0.1_amd64.deb 836beac9d55c2cbba8082b2126161fc4130236a7 59780 xtables-addons-common_3.0-0.1_amd64.deb 8279bb22d2198ed7fa0f57dcf2a3edd7e61f623c 283468 xtables-addons-dkms_3.0-0.1_all.deb 0ccaa3dd0a6bf7186292c8dae9481404fe9bc448 320456 xtables-addons-source_3.0-0.1_all.deb c19b5b41874694d0dcac4db2694c901fc388f49d 6775 xtables-addons_3.0-0.1_amd64.buildinfo Checksums-Sha256: bdb5dfa9f6372db03b74af967d9a85f8af1c4ab304d717d8dcefd8885a70da28 2169 xtables-addons_3.0-0.1.dsc 95580b851c79c0bbc484e0d0ea23f53e5c7f439ad73d509e426598565392690d 321960 xtables-addons_3.0.orig.tar.xz f34c624ead9b7f092fbf8ddd6b319966e9ef2946f38bd6703f6d6e15ac8aa979 11216 xtables-addons_3.0-0.1.debian.tar.xz 5d27a6a6bf97007feec5c572a39ae908c2514e339167c97a18c9bbfce4df6e55 169040 xtables-addons-common-dbgsym_3.0-0.1_amd64.deb 33bd74f9c9e70ea03e675fe76a46414ec2aaa6da505a8f8b57bd2f74711768bf 59780 xtables-addons-common_3.0-0.1_amd64.deb 037c55d4145a8984622e3741c4d94b4c910dcf05d6847e67e55ad24f07f5756e 283468 xtables-addons-dkms_3.0-0.1_all.deb 83575ebf9f0452ff3656b8b92525778ab6ed638ac7772970d8ce67fc11eb5465 320456 xtables-addons-source_3.0-0.1_all.deb 3266068d317c5d1f527b9fb4e8afd7d958d619f3d6601059facc8dc78bd4ce97 6775 xtables-addons_3.0-0.1_amd64.buildinfo Files: 169f0872210e864e4b16729cea42906e 2169 admin extra xtables-addons_3.0-0.1.dsc b37ed4d9c28cdcd5558c55934be8d051 321960 admin extra xtables-addons_3.0.orig.tar.xz 992809740570ddc0d523cacf0
