Processed: bug 906978 is forwarded to https://github.com/etingof/pysmi/issues/39
Processing commands for cont...@bugs.debian.org: > forwarded 906978 https://github.com/etingof/pysmi/issues/39 Bug #906978 [src:pysmi] pysmi: FTBFS in buster/sid (failing tests) Set Bug forwarded-to-address to 'https://github.com/etingof/pysmi/issues/39'. > thanks Stopping processing here. Please contact me if you need assistance. -- 906978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906978 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907559: [j...@apache.org: [jira] [Commented] (BATIK-1239) Class XMLConstants vanished from Batik]
[Uploaders of batik package in CC as well.] Markus, this is kind of a response to your suggestion to communicate with upstream. I admit I do not know what conclusion to draw from it. Kind regards Andreas. - Forwarded message from "Glenn Adams (JIRA)" - Date: Thu, 30 Aug 2018 04:36:00 + (UTC) From: "Glenn Adams (JIRA)" To: ti...@debian.org Subject: [jira] [Commented] (BATIK-1239) Class XMLConstants vanished from Batik [ https://issues.apache.org/jira/browse/BATIK-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16597050#comment-16597050 ] Glenn Adams commented on BATIK-1239: I performed the modularization a few years back when converting to a maven build architecture. One of the problems being addressed in that process was eliminating circularities among the graph of batik artifact dependencies, which resulted in the current modularization choices. It is clear that other choices are possible as well, and it is only in the use of these artifacts in a particular application of batik that it can be determined whether the modularization is adequate or needs improvements. I am not (at present) working on batik, and I know of no member of the XML Graphics project that is planning to make changes, other than Simon's work to respond to occasional bug requests. In light of the volunteer nature of the project, I suggest you contribute one or more patches that addresses the issues you encounter. > Class XMLConstants vanished from Batik > -- > > Key: BATIK-1239 > URL: https://issues.apache.org/jira/browse/BATIK-1239 > Project: Batik > Issue Type: Bug > Components: Utilities >Affects Versions: 1.10 > Environment: Debian >Reporter: Andreas Tille >Priority: Major > > Hi, > I'm facing a problem in Debian with a package that is using Batik that does > not explicitly contain XMLConstants but fails to start anyway. The issue is > discussed in the according [bug report|https://bugs.debian.org/907559] and > the suggestion was to contact Batik authors whether there is a hint how to > deal with the issue. > Kind regards, Andreas. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - End forwarded message - -- http://fam-tille.de
Bug#895959: libnet-ssleay-perl: FTBFS with openssl 1.1.1
-=| Kurt Roeckx, 24.08.2018 18:52:57 +0200 |=- > On Fri, Aug 24, 2018 at 10:27:16AM +, Damyan Ivanov wrote: > > -=| Kurt Roeckx, 23.08.2018 22:32:13 +0200 |=- > > > Note that the SIGPIPE issue is probably a known upstream issue > > > that still needs to be fixed, we're at least still working on a > > > SIGPIPE issue. > > > > > > But that does not mean that the other issues in libnet-ssleay-perl > > > should not get fixed. > > > > I tried applying all the patches from the fedora package of > > Net-SSLeay, and it didn't help much. > > > > It was mentioned in the upstream ticket that an additional fix is > > needed on libssl side, see > > https://bugzilla.redhat.com/show_bug.cgi?id=1615098 > > > > The reproducer from there fails with 1.1.1~~pre9-1 from unstable. > > > > Does this seem like something that needs to be fixed on the openssl > > side? > > This is something that should get fixed in whatever calls > TLSv1_method(). You should never call that function. It's also > been deprecated. > > The problem is that TLSv1_method() only supports TLS 1.0, and the > default config now says that TLS 1.2 is the minimum verison. You > should either use SSLv23_method() or TLS_method(), which support all > protocol versions that are enabled. I worked around this in Net::SSLeay by patching the routine that sets certificate and key to return an error condition only if any of the underlying routines return an error condition (https://salsa.debian.org/perl-team/modules/packages/libnet-ssleay-perl/blob/master/debian/patches/ok-result-is-no-error.patch). Previously it would check the error stack and ignore the return codes. On a more general note, the package seems ready for unstable to me. Reviews are welcome. If no obstacles appear, I plan to upload on late Sunday. -- dam
Bug#906380: libtool: FTBFS in buster/sid
at bottom :- On 30/08/2018, Juhani Numminen wrote: > Hello, > > Looking at the log[1] at reproducible builds, it looks like a test failure: > >> Support for older libltdl interfaces. >> >> 102: Makefile.incFAILED >> (old-ltdl-iface.at:134) > > I had a look at Fedora's libtool repository, and there's an interesting > commit: > "ftbfs: caused by automake 1.16.1"[2]. > > It might be the same issue that we're seeing, because that commit patches > the file tests/old-ltdl-iface.at, and the first build failure at RB[3] > happened in 2018-08-13 in buster, while automake 1.16.1 had migrated to > buster > in 2018-08-10[4]. > > > With best regards, > Juhani > > [1] > https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libtool_2.4.6-2.1.rbuild.log.gz > [2] > https://src.fedoraproject.org/rpms/libtool/c/20511dec725523a30496f1183322f8c6658acfdd > [3] https://tests.reproducible-builds.org/debian/history/libtool.html > [4] https://tracker.debian.org/pkg/automake-1.16 > > -- > To unsubscribe, send mail to 906380-unsubscr...@bugs.debian.org. > I, and I guess others would welcome a test build if it helps to see if the issue is resolved. See how to apply patch [1] and see if you can do the same thing - 1. https://unix.stackexchange.com/questions/324680/how-to-apply-a-patch-in-a-debian-package Look forward to seeing a new deb package and trying it out to see if it fixes the issue. Can't compile any packages due to the libtool issues :( -- 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#564173: wmcalc: wrong result in simple calculation, then abort on _XSend:
This bug still persists in wmcalc 0.6, although a fix has been submitted upstream [1]. [1] https://groups.google.com/forum/#!topic/wmaker-dev/4uEVw8bm-cU
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> unarchive 564173
Bug #564173 {Done: Sandro Tosi } [wmcalc] wmcalc: wrong
result in simple calculation, then abort on _XSend:
Unarchived Bug 564173
> reopen 564173
Bug #564173 {Done: Sandro Tosi } [wmcalc] wmcalc: wrong
result in simple calculation, then abort on _XSend:
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.3-7+rm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
564173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564173
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#906018: marked as done (python-distorm3: missing python dependencies)
Your message dated Thu, 30 Aug 2018 01:33:55 + with message-id and subject line Bug#906018: fixed in distorm3 3.3.4-3 has caused the Debian Bug report #906018, regarding python-distorm3: missing python 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.) -- 906018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-distorm3 Version: 3.3.4-2 Severity: serious python-distorm3 does not have any python dependencies. --- End Message --- --- Begin Message --- Source: distorm3 Source-Version: 3.3.4-3 We believe that the bug you reported is fixed in the latest version of distorm3, 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 906...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho (supplier of updated distorm3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 28 Aug 2018 19:31:14 -0300 Source: distorm3 Binary: libdistorm3-3 libdistorm3-dev python-distorm3 Architecture: source Version: 3.3.4-3 Distribution: unstable Urgency: medium Maintainer: Joao Eriberto Mota Filho Changed-By: Joao Eriberto Mota Filho Description: libdistorm3-3 - powerful disassembler library for x86/AMD64 binary streams libdistorm3-dev - powerful disassembler library for x86/AMD64 binary streams (devel python-distorm3 - powerful disassembler library for x86/AMD64 binary streams (Pytho Closes: 906018 Changes: distorm3 (3.3.4-3) unstable; urgency=medium . * Migrated DH level to 11. * debian/control: - Added python as dependency for python-distorm3. Thanks to Adrian Bunk (Closes: #906018) - Bumped Standards-Version to 4.2.1. - Changed Vcs-* URLs to salsa.debian.org. - Removed ancient X-Python-Version field. * debian/copyright: - Updated packaging copyright years. - Using a secure copyright format in URI. * debian/tests/*: added to perform tests. Checksums-Sha1: aa63e0482a77f4f2bf33bc8975da40f431eb3be5 2011 distorm3_3.3.4-3.dsc 0c8d50d4ae98e30a4e85e7089c6aa12d7236338d 5064 distorm3_3.3.4-3.debian.tar.xz a4fbe45cdfa1b9b9784c8dda5672a50ee23302f2 5888 distorm3_3.3.4-3_source.buildinfo Checksums-Sha256: a31f4f4658f317a6b970cdab4e62e620051acea13dfbe6490819f42368c8f52d 2011 distorm3_3.3.4-3.dsc b9a31ed30b62a131e9ae7eec89a37d95f7048e86cac1ac8847862138d1c4182d 5064 distorm3_3.3.4-3.debian.tar.xz 52fb9af55a36b7de17ec56133d449a57f0298e17836aa9b3f5c3dd2a6fe0dd0d 5888 distorm3_3.3.4-3_source.buildinfo Files: 52005288ea30faf34b79cd375efaa096 2011 libs optional distorm3_3.3.4-3.dsc 3749fe4a64126ec22f1d1368f1a46db3 5064 libs optional distorm3_3.3.4-3.debian.tar.xz 9427559109b5beb594355e21a54cfc7b 5888 libs optional distorm3_3.3.4-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAluF8qkACgkQ3mO5xwTr 6e/IYA//X3IymSzt2p/KT6ZoaPWY96fLnYthettJscNk8E/lOHvUSDezhXpmxueC ijGtjYsNo/xelz4lZE35/qzcudA0BDHaNX9nKa6u/XXENM+iqAwekrAYDk1GvG1d eVoUbA966JV+IMtUfGoEU+i+8bCcHuwUTQi5/ap6ze1vBgg8Wj8FPRyK9wTtZ0tY 5xQWz70zDyZr2M1ECiO7sAmg0YYFQkUfr4nW8MUZo/EAqkYHb9e4Tdyf+dLYkwBg 8dZaBtrhZdYvDISISqdvmQZ6MKDrDYUNWPyunxGq0W44KZhip3GSKq6kCLGsZs/N s5BzIgYAEJu697VN/Iei/IPKqEKE5FMEoESrMG/KBqYZy/CJ9V+gSZ4FYhWRjcoW RM3bJg+ATQcCq0girmeoXn85i6VhJ1GKiiIG0cjEecpOxnL3gY26dZ4azFWz9H0m /JTWVn2DXd2xldglKz54xDMecV5HoOI4QItLvdE+dEXub3yjqdyvQ5cbEDN0umNi abavTjyAGVxb8g71Hg9aIBZJllZ6bxYgnBnqmGkVeeStLC3r5F6fUpOIBT/l8z+A mm5JABRhEpvMO+CBFn6Fgt8q00evll3VLADZ+CgVCvtj081b0plmHjnJJhukwLud FVnVbALBkBgYe4gmo9//+J72vOgHRSMy+TkoSepDwki2C7xdqhw= =rPxQ -END PGP SIGNATURE End Message ---
Processed: bug 902220 is forwarded to aspectc-develop...@aspectc.org
Processing commands for cont...@bugs.debian.org: > forwarded 902220 aspectc-develop...@aspectc.org Bug #902220 [aspectc++] Needs porting to LLVM 6.0.1 Set Bug forwarded-to-address to 'aspectc-develop...@aspectc.org'. > thanks Stopping processing here. Please contact me if you need assistance. -- 902220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Needs porting to LLVM 6.0.1
Processing control commands: > retitle -1 Needs porting to LLVM 6.0.1 Bug #902220 [aspectc++] aspect++: Please use llvm-dev instead of llvm-4.0-dev Changed Bug title to 'Needs porting to LLVM 6.0.1' from 'aspect++: Please use llvm-dev instead of llvm-4.0-dev'. -- 902220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907466: Package doesn't ship xml files anymore
Package: iso-codes Version: 4.0-1 Followup-For: Bug #907466 Dear Maintainer, This bug affects gnome-control-center (package version 1:3.28.2-1). It breaks the functionality of the Region & Language panel, where it's not possible to list or change languages or formats and causes a segmentation fault when trying to add keyboard layouts. Running gnome-control-center from a terminal produces the following output: *** BEGIN OUTPUT *** $ gnome-control-center region (gnome-control-center:2244): GnomeDesktop-WARNING **: 21:41:43.080: Failed to load '/usr/share/xml/iso-codes/iso_639.xml': Failed to open file “/usr/share/xml/iso-codes/iso_639.xml”: No such file or directory (gnome-control-center:2244): GnomeDesktop-WARNING **: 21:41:43.080: Failed to load '/usr/share/xml/iso-codes/iso_639_3.xml': Failed to open file “/usr/share/xml/iso-codes/iso_639_3.xml”: No such file or directory (gnome-control-center:2244): GnomeDesktop-WARNING **: 21:41:43.080: Failed to load '/usr/share/xml/iso-codes/iso_3166.xml': Failed to open file “/usr/share/xml/iso-codes/iso_3166.xml”: No such file or directory (gnome-control-center:2244): GLib-CRITICAL **: 21:41:43.080: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (gnome-control-center:2244): GLib-CRITICAL **: 21:41:43.089: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (gnome-control-center:2244): GLib-CRITICAL **: 21:41:43.089: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (gnome-control-center:2244): GLib-CRITICAL **: 21:41:43.089: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (gnome-control-center:2244): GLib-CRITICAL **: 21:41:43.143: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (gnome-control-center:2244): GLib-CRITICAL **: 21:41:43.143: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (gnome-control-center:2244): GLib-CRITICAL **: 21:41:43.214: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (gnome-control-center:2244): GLib-CRITICAL **: 21:41:43.214: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (gnome-control-center:2244): GLib-CRITICAL **: 21:41:43.214: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (gnome-control-center:2244): GLib-CRITICAL **: 21:41:43.214: g_string_insert_len: assertion 'len == 0 || val != NULL' failed Segmentation fault *** END OUTPUT *** Regards, Leandro Perona -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.17.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 iso-codes depends on no packages. iso-codes recommends no packages. Versions of packages iso-codes suggests: pn isoquery -- no debconf information
Bug#902220: Needs porting to LLVM 6.0.1
Control: retitle -1 Needs porting to LLVM 6.0.1 Well, I just checked, even the latest trunk does not support LLVM 6.0.1. Or rather, it builds (with some minor, obvious modifications), but doesn't work. I haven't tested LLVM 6.0.0, it may or may not work. This needs to be looked into more. -rt
Bug#902522: marked as done (sorl-thumbnail: FTBFS in buster/sid (failing tests))
Your message dated Thu, 30 Aug 2018 00:04:14 + with message-id and subject line Bug#902522: fixed in sorl-thumbnail 12.3+git20170708-2 has caused the Debian Bug report #902522, regarding sorl-thumbnail: FTBFS in buster/sid (failing tests) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 902522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sorl-thumbnail Version: 12.3+git20170708-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster with "dpkg-buildpackage -A" but it failed: [...] debian/rules build-indep dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_autoreconf -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:217: python2.7 setup.py config running config I: pybuild base:217: python3.6 setup.py config running config debian/rules override_dh_auto_build make[1]: Entering directory '/<>/sorl-thumbnail-12.3+git20170708' dh_auto_build I: pybuild base:217: /usr/bin/python setup.py build [... snipped ...] = test session starts == platform linux2 -- Python 2.7.15, pytest-3.3.2, py-1.5.3, pluggy-0.6.0 Django settings: tests.settings.pgmagick (from environment variable) rootdir: /<>/sorl-thumbnail-12.3+git20170708, inifile: setup.cfg plugins: django-3.1.2 collected 68 items tests/thumbnail_tests/test_alternative_resolutions.py . [ 1%] tests/thumbnail_tests/test_backends.py ...F.s.. [ 19%] tests/thumbnail_tests/test_commands.py [ 25%] tests/thumbnail_tests/test_engines.py ..s.ss [ 63%] tests/thumbnail_tests/test_filters.py s.s. [ 69%] tests/thumbnail_tests/test_kvstore.py . [ 70%] tests/thumbnail_tests/test_parsers.py . [ 77%] tests/thumbnail_tests/test_storage.py [ 83%] tests/thumbnail_tests/test_templatetags.py ss. [100%] === FAILURES === _ TestDescriptors.test_is_valid_image __ self = def test_is_valid_image(self): with same_open_fd_count(self): > self.ENGINE.is_valid_image(b'invalidbinaryimage.jpg') tests/thumbnail_tests/test_backends.py:99: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = raw_data = 'invalidbinaryimage.jpg' def is_valid_image(self, raw_data): blob = Blob() blob.update(raw_data) > im = Image(blob) E RuntimeError: Magick: Unable to deduce image format () reported by magick/blob.c:739 (BlobToImage) sorl/thumbnail/engines/pgmagick_engine.py:29: RuntimeError 1 failed, 59 passed, 8 skipped in 1.22 seconds debian/rules:22: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>/sorl-thumbnail-12.3+git20170708' debian/rules:10: recipe for target 'build-indep' failed make: *** [build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The above is how the build ends in my autobuilder and it's not necessarily the relevant part. The failure is not, however, related to using dpkg-buildpackage -A, as it also fails in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sorl-thumbnail.html If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the page for this package. Thanks. --- End Message --- --- Begin Message --- Source: sorl-thumbnail Source-Version: 12.3+git20170708-2 We believe that the bug you reported is fixed in the latest version of sorl-thumbnail, 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 902...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution
Processed: severity of 892077 is grave
Processing commands for cont...@bugs.debian.org: > severity 892077 grave Bug #892077 [rakarrack] rakarrack: Segfaults after jackd upgrade Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 892077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: teg: Port to GooCanvas / GTK+ 3 / GSettings
Processing commands for cont...@bugs.debian.org: > tags 885751 + patch Bug #885751 [src:teg] teg: Depends on libgnomeui Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 885751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#902220: Processed: reopening 902220
On Wed, Aug 29, 2018 at 05:31:08PM -0400, Reinhard Tartler wrote: > > > On 08/29/2018 08:24 AM, Adrian Bunk wrote: > > AspectC++ upstream code already seems to support LLVM 6 (untested). > > That's contradictory to > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906972#10 It is not. The one year old code in unstable does not support LLVM 6 for obvious reasons. > This needs to be looked into more. > > Also, why do you need to have this bug at severity serious? If llvm-4.0 was > removed from testing, that would prevent packages such as aspectc++ from > migrating as well? This is a release critical bug in aspectc++. This makes it visible that there is a problem in aspectc++ that needs fixing. Bugs in other reverse dependencies were already made release critical by the release team earlier (and fixed by the maintainers). This bug was fixed and closed, so noone corrected the severity. > -rt 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#906380: libtool: FTBFS in buster/sid
Hello, Looking at the log[1] at reproducible builds, it looks like a test failure: > Support for older libltdl interfaces. > > 102: Makefile.incFAILED > (old-ltdl-iface.at:134) I had a look at Fedora's libtool repository, and there's an interesting commit: "ftbfs: caused by automake 1.16.1"[2]. It might be the same issue that we're seeing, because that commit patches the file tests/old-ltdl-iface.at, and the first build failure at RB[3] happened in 2018-08-13 in buster, while automake 1.16.1 had migrated to buster in 2018-08-10[4]. With best regards, Juhani [1] https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libtool_2.4.6-2.1.rbuild.log.gz [2] https://src.fedoraproject.org/rpms/libtool/c/20511dec725523a30496f1183322f8c6658acfdd [3] https://tests.reproducible-builds.org/debian/history/libtool.html [4] https://tracker.debian.org/pkg/automake-1.16
Bug#906228: marked as done (crtmpserver-dev still depends on libssl1.0-dev)
Your message dated Wed, 29 Aug 2018 21:34:08 + with message-id and subject line Bug#906228: fixed in crtmpserver 1.0~dfsg-5.5 has caused the Debian Bug report #906228, regarding crtmpserver-dev still depends on libssl1.0-dev 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.) -- 906228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: crtmpserver-dev Version: 1.0~dfsg-5.4 Severity: serious crtmpserver-dev still depends on libssl1.0-dev, this was missed during the switch to OpenSSL 1.1. --- End Message --- --- Begin Message --- Source: crtmpserver Source-Version: 1.0~dfsg-5.5 We believe that the bug you reported is fixed in the latest version of crtmpserver, 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 906...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adam Borowski (supplier of updated crtmpserver 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, 22 Aug 2018 22:39:22 +0200 Source: crtmpserver Binary: crtmpserver crtmpserver-libs crtmpserver-apps crtmpserver-dev Architecture: source Version: 1.0~dfsg-5.5 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Adam Borowski Description: crtmpserver - High performance RTMP/RTSP streaming server crtmpserver-apps - base applications for the crtmpserver platform crtmpserver-dev - Development files for the crtmpserver platform crtmpserver-libs - shared libraries for the crtmpserver platform Closes: 906228 Changes: crtmpserver (1.0~dfsg-5.5) unstable; urgency=medium . * Non-maintainer upload. * Update crtmpserver-dev's dependency on libssl1.0-dev (Closes: #906228). * Add missing Depends: lsd-base for binary:crtmpserver. Checksums-Sha1: ddd0dbe65fbf2ed36f40413bd104ff4a5669277b 2326 crtmpserver_1.0~dfsg-5.5.dsc 2aa88126c64d6fe00d178594105e85dd7f39640d 30772 crtmpserver_1.0~dfsg-5.5.debian.tar.xz 6677517db42a370a82e14fc0f82e04b9cf96fe88 6594 crtmpserver_1.0~dfsg-5.5_source.buildinfo Checksums-Sha256: 4683d7e606e4bdf552f465a8dceb60ccfe74b31842aa5c136545aa1b74ce6134 2326 crtmpserver_1.0~dfsg-5.5.dsc 95f3cee4b5359c3d933f9c3c7666caceac218296126e9e1f329ea8a6ff9820f4 30772 crtmpserver_1.0~dfsg-5.5.debian.tar.xz 9b91025d3c29c084649277e5d6be2ba5d92f5e5544b3656cf4a0ab64a62a4874 6594 crtmpserver_1.0~dfsg-5.5_source.buildinfo Files: 71df4a46c61a32d76469551870f7bb65 2326 video optional crtmpserver_1.0~dfsg-5.5.dsc 1d5ba4c5ad82bc321f8484db0bd76292 30772 video optional crtmpserver_1.0~dfsg-5.5.debian.tar.xz 18fe058f25d707233bd76212458feda9 6594 video optional crtmpserver_1.0~dfsg-5.5_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlt9yigUHGtpbG9ieXRl QGFuZ2JhbmQucGwACgkQweDZLphvfH5DSxAA1i8eb78FLn4cEAvXtnRSniciY8HL /UbxnhmUNi+IC+p8l/YBJYiXTUV9rJohYecjmIXNh1tPFZTI1gmsPRPGlRMGjYmq tDF0D5837qPrITyxn9QvequE4q8pFnGyjsukD70BmUBcOsKAgpr3Enqt3FtJOi9F zQXCzhHkfkgikPh4qlP3/MCERXGP2V7QOwu1geWl70adBfPb521sX5RSsl71kgpY JdtwVh9g9V3q1UjQ80pSmb+U49uIKeaV50ned69DOJmVrDwxrtCEtW3+Rh2zalH/ w+UwLTXhb/rBOExKkkqgsl5Dtklj2tsegX8VV6DwAA4o1Xf7+KTiuROkUvWgXcIe 4wZNJNgLwMhxnF1xa9Dgk3nBFwMBF+OUIlJr8x7cZDTO4FkkkEq2VXn2/hFRJBRh XGOCWgUfMBmTzXF/9XnRTF+uig2Z9zJrydoP7PGOxpzfk4r3SxCRf/aGYP8kDSKx HfmXx7p7GvmQmz5ljdTWdEZE2myLE9RddZFYDJbjJYX/5OjQ7u46XKSd1ZeZY0Yj K9jIOJH9GIwpxg42Z9Ywq1YEo89iauUzDuptqKPSeDZ6xe2vlIrt0ztKTCDXnMM1 WUtqSH9Jx9rbokgL7FyGNGSzRTb5FMO2Nt1LqcFqMn/Nl/vUA8AjFshaliZ0rsm9 j/AOfHjDS7ECmVw= =hTOH -END PGP SIGNATURE End Message ---
Bug#902220: Processed: reopening 902220
On 08/29/2018 08:24 AM, Adrian Bunk wrote: > AspectC++ upstream code already seems to support LLVM 6 (untested). That's contradictory to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906972#10 This needs to be looked into more. Also, why do you need to have this bug at severity serious? If llvm-4.0 was removed from testing, that would prevent packages such as aspectc++ from migrating as well? -rt
Bug#907585: marked as done (Contains Linux kernel iamge with source not provided)
Your message dated Wed, 29 Aug 2018 21:04:11 + with message-id and subject line Bug#907585: fixed in firmware-nonfree 20180825+dfsg-1 has caused the Debian Bug report #907585, regarding Contains Linux kernel iamge with source not provided 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.) -- 907585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firmware-cavium Version: 20180518-1 Severity: serious Tags: upstream It was reported upstream that the file liquidio/lio_23xx_vsw.bin contains a Linux kernel image, but without the proper licence text or source code accompanying it in this repository. Ben. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled firmware-cavium depends on no packages. firmware-cavium recommends no packages. Versions of packages firmware-cavium suggests: ii initramfs-tools 0.133~1.gbp3490d3 --- End Message --- --- Begin Message --- Source: firmware-nonfree Source-Version: 20180825+dfsg-1 We believe that the bug you reported is fixed in the latest version of firmware-nonfree, 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 907...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated firmware-nonfree 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, 29 Aug 2018 21:14:09 +0100 Source: firmware-nonfree Binary: firmware-linux firmware-linux-nonfree firmware-adi firmware-ralink firmware-amd-graphics firmware-atheros firmware-bnx2 firmware-bnx2x firmware-brcm80211 firmware-cavium firmware-intelwimax firmware-intel-sound firmware-ipw2x00 firmware-ivtv firmware-iwlwifi firmware-libertas firmware-misc-nonfree firmware-myricom firmware-netronome firmware-netxen firmware-qcom-media firmware-qlogic firmware-realtek firmware-samsung firmware-siano firmware-ti-connectivity Architecture: source Version: 20180825+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Description: firmware-adi - Binary firmware for Analog Devices Inc. DSL modem chips (dummmy p firmware-amd-graphics - Binary firmware for AMD/ATI graphics chips firmware-atheros - Binary firmware for Atheros wireless cards firmware-bnx2 - Binary firmware for Broadcom NetXtremeII firmware-bnx2x - Binary firmware for Broadcom NetXtreme II 10Gb firmware-brcm80211 - Binary firmware for Broadcom/Cypress 802.11 wireless cards firmware-cavium - Binary firmware for Cavium Ethernet adapters firmware-intel-sound - Binary firmware for Intel sound DSPs firmware-intelwimax - Binary firmware for Intel WiMAX Connection firmware-ipw2x00 - Binary firmware for Intel Pro Wireless 2100, 2200 and 2915 firmware-ivtv - Binary firmware for iTVC15-family MPEG codecs (ivtv and pvrusb2 d firmware-iwlwifi - Binary firmware for Intel Wireless cards firmware-libertas - Binary firmware for Marvell wireless cards firmware-linux - Binary firmware for various drivers in the Linux kernel (meta-pac firmware-linux-nonfree - Binary firmware for various drivers in the Linux kernel (meta-pac firmware-misc-nonfree - Binary firmware for various drivers in the Linux kernel firmware-myricom - Binary firmware for Myri-10G Ethernet adapters firmware-netronome - Binary firmware for Netronome network adapters firmware-netxen - Binary firmware for QLogic Intelligent Ethernet (3000 and 3100 Se firmware-qcom-media - Binary firmware for Qualcomm graphics/video firmware-qlogic - Binary firmware for QLogic HBAs firmware-ralink - Binary firmware for Ralink wireless cards (dummmy package) firmware-realtek - Binary firmware for Realtek
Bug#906471: marked as done (hddemux: FTBFS in buster/sid (undefined reference to `UV__ERR'))
Your message dated Wed, 29 Aug 2018 21:04:33 + with message-id and subject line Bug#906471: fixed in hddemux 0.4-1 has caused the Debian Bug report #906471, regarding hddemux: FTBFS in buster/sid (undefined reference to `UV__ERR') 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.) -- 906471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:hddemux Version: 0.3-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch dh_update_autotools_config -a dh_autoreconf -a dh_auto_configure -a dh_auto_build -a make -j1 make[1]: Entering directory '/<>' gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_GNU_SOURCE -g -O3 -Wl,-z,relro -Wl,-z,now -luv -lrt -lpthread -lnsl -ldl -lsystemd -std=c11 -pedantic -Wall -Werror -o hddemux hddemux.c /usr/bin/ld: /tmp/cc4N4SQd.o: in function `inbound_first_read': ./hddemux.c:503: undefined reference to `UV__ERR' /usr/bin/ld: ./hddemux.c:503: undefined reference to `UV__ERR' /usr/bin/ld: /tmp/cc4N4SQd.o: in function `stream_read': ./hddemux.c:656: undefined reference to `UV__ERR' /usr/bin/ld: ./hddemux.c:656: undefined reference to `UV__ERR' /usr/bin/ld: ./hddemux.c:657: undefined reference to `UV__ERR' collect2: error: ld returned 1 exit status make[1]: *** [Makefile:11: hddemux] Error 1 make[1]: Leaving directory '/<>' dh_auto_build: make -j1 returned exit code 2 make: *** [debian/rules:4: build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 The build was made with "dpkg-buildpackage -B" in my autobuilder. Most probably, it also fails here in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hddemux.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: hddemux Source-Version: 0.4-1 We believe that the bug you reported is fixed in the latest version of hddemux, 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 906...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Kahn Gillmor (supplier of updated hddemux 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, 29 Aug 2018 16:52:12 -0400 Source: hddemux Binary: hddemux Architecture: source Version: 0.4-1 Distribution: unstable Urgency: medium Maintainer: Daniel Kahn Gillmor Changed-By: Daniel Kahn Gillmor Description: hddemux- HTTP/1.x and DNS demultiplexer Closes: 872188 906471 Changes: hddemux (0.4-1) unstable; urgency=medium . * new upstream release - Closes: #906471, #872188 - yes, i can actually count to 16 in hex - added a simple, totally incomplete test suite - fix makefile for --Wl,--as-needed (addresses) - actually verify whether the loop closes correctly - use UV_* symbols instead of libuv-internal UV__* - add real test suite * move to dh 11 * Standards-Version: bump to 4.2.1 (no changes needed) * use Rules-Requires-Root: no * move to salsa * use DEP-14 branch naming * add autopkgtest * handle upstream test suite Checksums-Sha1: ea6c3a9c3079de7cc2d1134410c4d5b06fd52b64 1501 hddemux_0.4-1.dsc 2be59da506a29ac66c386e025c5bc18498997c8f 33148 hddemux_0.4.orig.tar.gz 7848ac3b594e28dc796fdcf73dd56ec0254abdf5 5504 hddemux_0.4-1.debian.tar.xz d1f8bf3bcb036ecd8b93cefd84c1619deab219a9 8002 hddemux_0.4-1_amd64.buildinfo Checksums-Sha256: 703a21f8089cb193404112a6e71f0082ab2229f1ce9ddf5c1f8fab4d50cb4adf 1501 hddemux_0.4-1.dsc 1601916407cb151a2bc435ae49ef46a277defe671eb2c292cb5a9a09bc02a0af 33148 hddemux_0.4.orig.tar.gz
Processed: Re: Bug#906789: missing python3-pkg-resources dependency
Processing control commands: > tag -1 patch Bug #906789 [yapf3] missing python3-pkg-resources dependency Ignoring request to alter tags of bug #906789 to the same tags previously set -- 906789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907590: grafana: CVE-2018-15727: authentication bypass flaw
Source: grafana Version: 2.6.0+dfsg-3 Severity: grave Tags: security upstream Hi, The following vulnerability was published for grafana. CVE-2018-15727[0]: | Grafana 2.x, 3.x, and 4.x before 4.6.4 and 5.x before 5.2.3 allows | authentication bypass because an attacker can generate a valid | "remember me" cookie knowing only a username of an LDAP or OAuth user. 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-15727 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-15727 [1] https://grafana.com/blog/2018/08/29/grafana-5.2.3-and-4.6.4-released-with-important-security-fix/ Regards, Salvatore
Processed: Re: Bug#906789: missing python3-pkg-resources dependency
Processing control commands: > tag -1 patch Bug #906789 [yapf3] missing python3-pkg-resources dependency Added tag(s) patch. -- 906789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906789: missing python3-pkg-resources dependency
Control: tag -1 patch Hi Navaneeth and Ana, On Tue, Aug 21, 2018 at 06:08:04AM +0200, navaneeth wrote: > Package: yapf3 > Version: 0.22.0-2 > > yapf3 should depend on python3-pkg-resources. Without that module, it > fails with a module not found error. I have filed a PR here to fix this bug: https://salsa.debian.org/python-team/modules/yapf/merge_requests/1 Cheers, Nicholas signature.asc Description: PGP signature
Processed: Re: Bug#904755: closed by Ana Custura (Bug#904755: fixed in yapf 0.22.0-2)
Processing control commands: > tag -1 patch Bug #904755 [yapf] yapf: missing dependency on python-pkg-resources Added tag(s) patch. -- 904755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904755 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904755: closed by Ana Custura (Bug#904755: fixed in yapf 0.22.0-2)
Control: tag -1 patch Hi Adrian and Ana, On Mon, Aug 27, 2018 at 01:22:25PM +0300, Adrian Bunk wrote: > Control: reopen -1 > > On Sun, Aug 12, 2018 at 03:39:08PM +, Debian Bug Tracking System wrote: > >... > > yapf (0.22.0-2) unstable; urgency=medium > > . > >* debian/control: > >- adds missing dependency on python-pkg-resources (Closes: #904755) > >... > > This isn't fixed: > > Package: yapf > Version: 0.22.0-5 > Depends: python:any, python-yapf (= 0.22.0-5) > > Package: yapf > Version: 0.22.0-2 > Depends: python:any, python-yapf (= 0.22.0-2) I have filed a PR here to fix this bug: https://salsa.debian.org/python-team/modules/yapf/merge_requests/1 Cheers, Nicholas signature.asc Description: PGP signature
Bug#896238: marked as done (python3-gphoto2cffi: gphoto2cffi fails to import)
Your message dated Wed, 29 Aug 2018 20:34:08 +
with message-id
and subject line Bug#896238: fixed in gphoto2-cffi 0.3~a1-1.1
has caused the Debian Bug report #896238,
regarding python3-gphoto2cffi: gphoto2cffi fails to import
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.)
--
896238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-gphoto2cffi
Version: 0.3~a1-1+b1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-gphoto2cffi importing the module gphoto2cffi
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/gphoto2cffi/__init__.py", line 1, in
from .gphoto2 import (Camera, list_cameras, supported_cameras,
File "/usr/lib/python3/dist-packages/gphoto2cffi/gphoto2.py", line 15, in
from . import errors, backend
File "/usr/lib/python3/dist-packages/gphoto2cffi/backend.py", line 56, in
'extract_exif': _lib.GP_FILE_OPERATION_EXIF})
File "/usr/lib/python3.6/enum.py", line 293, in __call__
return cls._create_(value, names, module=module, qualname=qualname,
type=type, start=start)
File "/usr/lib/python3.6/enum.py", line 399, in _create_
enum_class = metacls.__new__(metacls, class_name, bases, classdict)
File "/usr/lib/python3.6/enum.py", line 153, in __new__
enum_class = super().__new__(metacls, cls, bases, classdict)
TypeError: type.__new__() argument 1 must be str, not bytes
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
--- End Message ---
--- Begin Message ---
Source: gphoto2-cffi
Source-Version: 0.3~a1-1.1
We believe that the bug you reported is fixed in the latest version of
gphoto2-cffi, 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 896...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian Bunk (supplier of updated gphoto2-cffi 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, 27 Aug 2018 22:41:25 +0300
Source: gphoto2-cffi
Binary: python-gphoto2cffi python3-gphoto2cffi
Architecture: source
Version: 0.3~a1-1.1
Distribution: unstable
Urgency: high
Maintainer: Aigars Mahinovs
Changed-By: Adrian Bunk
Description:
python-gphoto2cffi - GPhoto2 bindings with simpler API
python3-gphoto2cffi - GPhoto2 bindings with simpler API
Closes: 896238
Changes:
gphoto2-cffi (0.3~a1-1.1) unstable; urgency=high
.
* Non-maintainer upload.
* Add upstream fix to unbreak python3-gphoto2cffi. (Closes: #896238)
Checksums-Sha1:
cfe116da9b81011069350b3f0d247c604701e515 1988 gphoto2-cffi_0.3~a1-1.1.dsc
5fe8bd4ba5d8424cf31b37d968be890589b0b31a 2496
gphoto2-cffi_0.3~a1-1.1.debian.tar.xz
Checksums-Sha256:
a107184b73fd724930d1771ef9b5cc1bdbd34efe3b8b793711bcd434416ceb23 1988
gphoto2-cffi_0.3~a1-1.1.dsc
bfe0231dc70a698de4eab0f82f159117ea0bc3cbb20b6fa435e1a4eec7391097 2496
gphoto2-cffi_0.3~a1-1.1.debian.tar.xz
Files:
6a80d6cd042f0df3389b39ee18ddaf6b 1988 python optional
gphoto2-cffi_0.3~a1-1.1.dsc
6cbc1f076b7189c9b18c28d381b9d39c 2496 python optional
gphoto2-cffi_0.3~a1-1.1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAluEVbQACgkQiNJCh6LY
mLHKlg//bbyy4tdrXPrL5darf/G4uKPC9DYzojJvabrM+Gz3hajieN3lCQg/vAAK
2hA0VRDr4dNHKufltSgbAh20hB0cUNregvWP/dwWUCIINgz6HOxLpt5ueNW/zdY2
IKKSxq88hUjvWAdTlqCUDol4J3XoC/c29znOnoNRRHKbf7BqVWKce8PAfJZ6XLFV
/Iw+XxpqprSMFYkfIh6XJG4SsvpD772fGEmEVv0SKT2IH7PcrfuLKtg+tkww5bfE
VOO7fUVmKkO0+Q4vaUnhSJmVan7+uh36USDTosYhg5dX+FBVf1pmeGkPvsdDN47S
hCBWCrbxFj7rsJnwPKPsfVOn9vcZfpYYfVRswZrFFitweSM6SdBXDxBaKkUbfVHQ
FnEWTe5qCKZymLBSbvvKuls77NKEN+aabwmq8mjl118bYUIs3Z7fHInGwoYTizFV
Processed: bug 907585 is forwarded to https://marc.info/?l=linux-netdev
Processing commands for cont...@bugs.debian.org: > forwarded 907585 https://marc.info/?l=linux-netdev Bug #907585 [firmware-cavium] Contains Linux kernel iamge with source not provided Set Bug forwarded-to-address to 'https://marc.info/?l=linux-netdev'. > thanks Stopping processing here. Please contact me if you need assistance. -- 907585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 907585 is forwarded to https://marc.info/?l=linux-netdev=153538208012629
Processing commands for cont...@bugs.debian.org: > forwarded 907585 https://marc.info/?l=linux-netdev=153538208012629 Bug #907585 [firmware-cavium] Contains Linux kernel iamge with source not provided Changed Bug forwarded-to-address to 'https://marc.info/?l=linux-netdev=153538208012629' from 'https://marc.info/?l=linux-netdev'. > thanks Stopping processing here. Please contact me if you need assistance. -- 907585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#906568 closed by Mathieu Parent (Bug#906562: fixed in samba 2:4.8.4+dfsg-2)
Processing control commands:
> reopen -1
Bug #906568 {Done: Mathieu Parent } [samba]
samba-dsdb-modules not installable
Bug #906562 {Done: Mathieu Parent } [samba]
samba-dsdb-modules not installable
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions samba/2:4.8.4+dfsg-2.
No longer marked as fixed in versions samba/2:4.8.4+dfsg-2.
> severity -1 grave
Bug #906568 [samba] samba-dsdb-modules not installable
Bug #906562 [samba] samba-dsdb-modules not installable
Ignoring request to change severity of Bug 906568 to the same value.
Ignoring request to change severity of Bug 906562 to the same value.
--
906562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906562
906568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#906568: closed by Mathieu Parent (Bug#906562: fixed in samba 2:4.8.4+dfsg-2)
Control: reopen -1 Control: severity -1 grave The following packages have unmet dependencies: samba-dsdb-modules : Depends: libldb1 (< 2:1.4.0+really1.3.6~) but 2:1.4.0+really1.3.6-1 is to be installed E: Unable to correct problems, you have held broken packages. Elimar -- From The Collaborative International Dictionary of English v.0.48 [gcide]: . arsehole \arse"hole`\ ([aum]rs"h[=o]l`), n. 1. execretory opening at the end of the alimentary canal.
Bug#907306: marked as done (configure: error: gdk-pixbuf-query-loaders not found in path)
Your message dated Wed, 29 Aug 2018 19:49:12 +
with message-id
and subject line Bug#907306: fixed in librsvg 2.44.1-1
has caused the Debian Bug report #907306,
regarding configure: error: gdk-pixbuf-query-loaders not found in path
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.)
--
907306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:librsvg
Version: 2.40.20-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with gnome,gir
dh_update_autotools_config -i
debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf --as-needed
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
[... snipped ...]
mkdir_p='$(MKDIR_P)'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
runstatedir='/run'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''
## --- ##
## confdefs.h. ##
## --- ##
/* confdefs.h */
#define PACKAGE_NAME "RSVG"
#define PACKAGE_TARNAME "librsvg"
#define PACKAGE_VERSION "2.40.20"
#define PACKAGE_STRING "RSVG 2.40.20"
#define PACKAGE_BUGREPORT
"https://bugzilla.gnome.org/enter_bug.cgi?product=librsvg;
#define PACKAGE_URL ""
#define PACKAGE "librsvg"
#define VERSION "2.40.20"
#define STDC_HEADERS 1
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_MEMORY_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
#define HAVE_DLFCN_H 1
#define LT_OBJDIR ".libs/"
#define HAVE_STRTOK_R 1
configure: exit 1
dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --enable-pixbuf-loader
--enable-introspection --enable-vala --enable-gtk-doc returned exit code 1
make[1]: *** [debian/rules:14: override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
The build was made in my autobuilder with either "dpkg-buildpackage -A"
(if the package allows it) or "dpkg-buildpackage -B" (if it does not).
Most probably, it also fails here in reproducible builds:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/librsvg.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: librsvg
Source-Version: 2.44.1-1
We believe that the bug you reported is fixed in the latest version of
librsvg, 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 907...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Simon McVittie (supplier of updated librsvg package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 29 Aug 2018 17:38:27 +0100
Source: librsvg
Binary: librsvg2-dev librsvg2-2 librsvg2-common librsvg2-doc librsvg2-bin
gir1.2-rsvg-2.0
Architecture: source
Version: 2.44.1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME
Bug#907559: cgview: Does not start
Control: forwarded -1 https://issues.apache.org/jira/browse/BATIK-1239 On Wed, Aug 29, 2018 at 08:23:38PM +0200, Markus Koschany wrote: > > Wouldn't it help more if I simply try to package batik-constants? > > I thought it would be more likely to get a more precise answer from them > because they certainly know their code best. I am not even sure if > batik-constants is a long term solution or if they want to change that > again in the future. Depending on the cgview code it may have been > possible to patch the sources and make them compatible with Batik 1.10 > without packaging batik-constants. If this all sounds too far-fetched, > then packaging batik-constants is the way to go. Thanks for your insight. I have opened an upstream bug report[1] (no idea how to contact upstream otherwise). Kind regards Andreas. [1] https://issues.apache.org/jira/browse/BATIK-1239 -- http://fam-tille.de
Processed: Re: Bug#907559: cgview: Does not start
Processing control commands: > forwarded -1 https://issues.apache.org/jira/browse/BATIK-1239 Bug #907559 [cgview] cgview: Does not start Set Bug forwarded-to-address to 'https://issues.apache.org/jira/browse/BATIK-1239'. -- 907559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907559 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 865271 is serious
Processing commands for cont...@bugs.debian.org: > severity 865271 serious Bug #865271 [php-cassandra] [php-cassandra] The package does not contain the actual module (cassandra.so). Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 865271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907451: libbiod FTBFS: Error: cannot implicitly convert expression
Am Mi., 29. Aug. 2018 um 19:56 Uhr schrieb Andreas Tille : > > Hi Matthias, > On Tue, Aug 28, 2018 at 03:39:56PM +0200, Matthias Klumpp wrote: > > > > ... > > > > [30/149] ldc2 -Ibiod@sha -I. -I.. -I -I../ -I/usr/include/d > > > > -enable-color -O -g -release -wi -relocation-model=pic -of > > > > 'biod@sha/bio_maf_reader.d.o' -c ../bio/maf/reader.d > > > > FAILED: biod@sha/bio_maf_reader.d.o > > > > ldc2 -Ibiod@sha -I. -I.. -I -I../ -I/usr/include/d -enable-color -O -g > > > > -release -wi -relocation-model=pic -of 'biod@sha/bio_maf_reader.d.o' > > > > -c ../bio/maf/reader.d > > > > ../bio/maf/reader.d(40): Deprecation: struct > > > > `std.stdio.File.ByLine!(char, char).ByLine` is deprecated - Use .byLine > > > > ../bio/maf/reader.d(53): Error: cannot implicitly convert expression > > > > `this._f.byLine(cast(Flag)true, '\x0a')` of type `ByLineImpl!(char, > > > > char)` to `ByLine!(char, char)` > > > > ../bio/maf/reader.d(53):`this._lines = > > > > this._f.byLine(cast(Flag)true, '\x0a')` is the first assignment of > > > > `this._lines` therefore it represents its initialization > > > > ../bio/maf/reader.d(53):`opAssign` methods are not used for > > > > initialization, but for subsequent assignments > > > > [ > > > > Looks like an upstream issue - have you filed a bug there already? > > Upstream code das not changed since first release in Debian (Sat, 04 Mar > 2017) I have no idea what kind of bug I should file. :-( As I wrote before: Am Mi., 29. Aug. 2018 um 16:08 Uhr schrieb Matthias Klumpp : > [...] > You don't even need to file a bug - looks like upstream fixed this > already in > https://github.com/biod/BioD/commit/dd07f3497979b5d7f32ad32476da5108ffc5121e, > so all you need to do is take that patch.
Bug#907451: marked as done (libbiod FTBFS: Error: cannot implicitly convert expression)
Your message dated Wed, 29 Aug 2018 19:04:38 + with message-id and subject line Bug#907451: fixed in libbiod 0.1.0-6 has caused the Debian Bug report #907451, regarding libbiod FTBFS: Error: cannot implicitly convert expression 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.) -- 907451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbiod Version: 0.1.0-5 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libbiod.html ... [30/149] ldc2 -Ibiod@sha -I. -I.. -I -I../ -I/usr/include/d -enable-color -O -g -release -wi -relocation-model=pic -of 'biod@sha/bio_maf_reader.d.o' -c ../bio/maf/reader.d FAILED: biod@sha/bio_maf_reader.d.o ldc2 -Ibiod@sha -I. -I.. -I -I../ -I/usr/include/d -enable-color -O -g -release -wi -relocation-model=pic -of 'biod@sha/bio_maf_reader.d.o' -c ../bio/maf/reader.d ../bio/maf/reader.d(40): Deprecation: struct `std.stdio.File.ByLine!(char, char).ByLine` is deprecated - Use .byLine ../bio/maf/reader.d(53): Error: cannot implicitly convert expression `this._f.byLine(cast(Flag)true, '\x0a')` of type `ByLineImpl!(char, char)` to `ByLine!(char, char)` ../bio/maf/reader.d(53):`this._lines = this._f.byLine(cast(Flag)true, '\x0a')` is the first assignment of `this._lines` therefore it represents its initialization ../bio/maf/reader.d(53):`opAssign` methods are not used for initialization, but for subsequent assignments [ --- End Message --- --- Begin Message --- Source: libbiod Source-Version: 0.1.0-6 We believe that the bug you reported is fixed in the latest version of libbiod, 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 907...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated libbiod package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 29 Aug 2018 20:38:20 +0200 Source: libbiod Binary: libbiod0 libbiod-dev Architecture: source Version: 0.1.0-6 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: libbiod-dev - bioinformatics library in D (development files) libbiod0 - bioinformatics library in D Closes: 907451 Changes: libbiod (0.1.0-6) unstable; urgency=medium . * Point Vcs fields to salsa.debian.org * Standards-Version: 4.2.1 * Cherry pick patch from upstream (thanks for the hint to Matthias Klumpp) Closes: #907451 Checksums-Sha1: 704292db2de785569ad6cef0217ffc36d9d5cf7d 2042 libbiod_0.1.0-6.dsc d6627b88236ba711e097db05abeb5a2646596ff2 21984 libbiod_0.1.0-6.debian.tar.xz Checksums-Sha256: f722593eea2b24fa5092ce552e71ec493c29a1788d1b343b20c3a8c0025a4d63 2042 libbiod_0.1.0-6.dsc 0f5149e3e3271b09ef6ee211a377274cdd9e00897c553ad59552d1928be5b87a 21984 libbiod_0.1.0-6.debian.tar.xz Files: 9eeaa766bf61f024397221907b6499ec 2042 science optional libbiod_0.1.0-6.dsc 47d12686dbfff131c0b6e80da03362d0 21984 science optional libbiod_0.1.0-6.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAluG6S0RHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtHtZw//Z8ALGv3Va3cetVUH7jZpi5A/cUJL3xSS QZNkSCaOiHimoOi6C8+LZf/e9ZFoH0qxfJP7kxXryqXBsMHYepIzIQZApqq6R2dQ +suv9dPIsCflWKM70danQrI40uQ0pyIesXD22GRUbsnRfd88eaEo+U4045En7hGZ 1bgQnEF91SodXFW4H1cl1/SpZFqunkVdxc4NcN6evgW8NNhfyg8stuuvJ5/8wBiV xJZQPQo/itJlcv+qmqPbvnVqQjXzhl0EfvpG6FY2JyJSTkntUwnHCaM1A50eAvKT MGGmThPEHEXmGAdT3QIEO02+BLYo/zBaD6WX8FgZM+UqcSazC5j6eI7Ur/Fo91Ml nD23Lqoew18bd6zFkBJ3zUZDeyvcYVNdtOVd7QlI6lrhenUkdT4WB7AcH/87RFMs WyR1sufA5+A5BaczuP6L9Z+CCOhpA9pR6M77aDe1Nes7d61eufIWcTOOVB8adumM 3SkHYj7L8lkpIC/331/m6rk1YEjYRYXubAkiba0g55pqAztiOZyyLsjnRYNmUK3T SvYvQZ02CX+pRRlHq7cfa+eXHgjzQ9VUJRdqcyz5BN4eXEkr4pnotqPkFDMnP3Ie toRa+a1VFxis+8TvGi3WFQO5WzIU2yAm28Vc4fUiR7Zd+g3EJqMg0VcJXVMlxORh eQKKs7412BU= =DQul -END PGP SIGNATURE End Message ---
Bug#907489: sambamba FTBFS
Control: forwarded -1 https://github.com/biod/sambamba/issues/362 Control: tags -1 upstream On Wed, Aug 29, 2018 at 04:14:48PM +0200, Matthias Klumpp wrote: > > This appears to be a different issue to me - this one is a bit weirder > than the BioD one. You can either apply the BioD patch and see if that > fixes the problem, It does not unfortunately. > or directly report it upstream. This does not look > Debian-specific at all, it rather looks like a generic upstream issue > that happened because we are currently in a transition to a more > recent compiler in Debian. I reported issue #362. Thanks a lot for your help Andreas. -- http://fam-tille.de
Processed: Re: Bug#907489: sambamba FTBFS
Processing control commands: > forwarded -1 https://github.com/biod/sambamba/issues/362 Bug #907489 [src:sambamba] sambamba FTBFS Set Bug forwarded-to-address to 'https://github.com/biod/sambamba/issues/362'. > tags -1 upstream Bug #907489 [src:sambamba] sambamba FTBFS Added tag(s) upstream. -- 907489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907585: Contains Linux kernel iamge with source not provided
Package: firmware-cavium Version: 20180518-1 Severity: serious Tags: upstream It was reported upstream that the file liquidio/lio_23xx_vsw.bin contains a Linux kernel image, but without the proper licence text or source code accompanying it in this repository. Ben. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled firmware-cavium depends on no packages. firmware-cavium recommends no packages. Versions of packages firmware-cavium suggests: ii initramfs-tools 0.133~1.gbp3490d3
Bug#907493: ghostscript breaks cups autopkgtest: test times out
Control: tags -1 moreinfo Hi, On 29-08-18 20:20, Jonas Smedegaard wrote: > Thanks - that is indeed helpful, but provides only the _cups_ commands. > > Inside those are some Ghostscript command (and some data) which I would > need to check if/what fails with Ghostscript. Both of them are "ELF 64-bit LSB shared object" so it would help if the cups maintainers could help here. Paul signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#907493: ghostscript breaks cups autopkgtest: test times out
Processing control commands: > tags -1 moreinfo Bug #907493 [src:ghostscript, src:cups] ghostscript breaks cups autopkgtest: test times out Added tag(s) moreinfo. -- 907493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907559: cgview: Does not start
Am 29.08.2018 um 19:31 schrieb Andreas Tille: [...] >> Maybe you should raise this issue with upstream (Batik and/or cgview) > > Well cgview is not actively maintained (but has quite a number of users) > and what exactly should I say to Batik upstream if they decided to move > it to a noew project? I admit I have no idea what to say and where to > report. > > Wouldn't it help more if I simply try to package batik-constants? I thought it would be more likely to get a more precise answer from them because they certainly know their code best. I am not even sure if batik-constants is a long term solution or if they want to change that again in the future. Depending on the cgview code it may have been possible to patch the sources and make them compatible with Batik 1.10 without packaging batik-constants. If this all sounds too far-fetched, then packaging batik-constants is the way to go. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#907493: ghostscript breaks cups autopkgtest: test times out
Quoting Paul Gevers (2018-08-29 19:58:37) > Control: tags -1 - moreinfo > > On Wed, 29 Aug 2018 09:41:37 +0200 Jonas Smedegaard wrote: > > It would be most helpful if someone could dig out from that convoluted > > ci-in-cups test the actual ghostscript command causing cups to hang. > > Looking here: > https://sources.debian.org/src/cups/2.2.8-5/debian/tests/cups/ > > it runs: > /usr/share/cups/test-drivers > > As the log ends with: > * Driver drv:///sample.drv/dymo.ppd > - Create test printer: done. > - Print test job with /usr/share/cups/data/topsecret.pdf: > > I guess it successfully runs this command > /usr/sbin/lpadmin -p $DUMMY_PRINTER_NAME -E -m $driver -v > file:///dev/null > and fails with this command: > rid=$(/usr/bin/lp -d $DUMMY_PRINTER_NAME $file | sed -e > 's/^.*request id is \(.*\) (.*)$/\1/g') > > where > DUMMY_PRINTER_NAME=test-printer0 > driver=drv:///sample.drv/dymo.ppd > file=/usr/share/cups/data/topsecret.pdf > > Is that enough for you to continue? Thanks - that is indeed helpful, but provides only the _cups_ commands. Inside those are some Ghostscript command (and some data) which I would need to check if/what fails with Ghostscript. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Processed: Re: redisearch: "Apache 2.0 with Commons License" violates DFSG §6
Processing commands for cont...@bugs.debian.org: > affects 906920 907577 Bug #906920 [redisearch] redisearch: "Apache 2.0 with Commons License" violates DFSG §6 Added indication that 906920 affects 907577 > thanks Stopping processing here. Please contact me if you need assistance. -- 906920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907493: ghostscript breaks cups autopkgtest: test times out
Control: tags -1 - moreinfo On Wed, 29 Aug 2018 09:41:37 +0200 Jonas Smedegaard wrote: > It would be most helpful if someone could dig out from that convoluted > ci-in-cups test the actual ghostscript command causing cups to hang. Looking here: https://sources.debian.org/src/cups/2.2.8-5/debian/tests/cups/ it runs: /usr/share/cups/test-drivers As the log ends with: * Driver drv:///sample.drv/dymo.ppd - Create test printer: done. - Print test job with /usr/share/cups/data/topsecret.pdf: I guess it successfully runs this command /usr/sbin/lpadmin -p $DUMMY_PRINTER_NAME -E -m $driver -v file:///dev/null and fails with this command: rid=$(/usr/bin/lp -d $DUMMY_PRINTER_NAME $file | sed -e 's/^.*request id is \(.*\) (.*)$/\1/g') where DUMMY_PRINTER_NAME=test-printer0 driver=drv:///sample.drv/dymo.ppd file=/usr/share/cups/data/topsecret.pdf Is that enough for you to continue? Paul signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#907493: ghostscript breaks cups autopkgtest: test times out
Processing control commands: > tags -1 - moreinfo Bug #907493 [src:ghostscript, src:cups] ghostscript breaks cups autopkgtest: test times out Removed tag(s) moreinfo. -- 907493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#883181: linux-image-4.9.0-4-amd64: Default stretch kernel raises cgroup strack traces under high load
Hi, The last linux kernel in stretch being 4.9.110, could you re-test with this kernel please ? Thanks, Regards, Romain On Thu, Nov 30, 2017 at 11:54:00AM +, Tom Stocker wrote: > Package: src:linux > Version: 4.9.51-1 > Severity: serious > Justification: Policy 2.2.1 > > > > -- Package-specific info: > ** Version: > Linux version 4.9.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version > 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.51-1 (2017-09-28) > > ** Command line: > BOOT_IMAGE=/boot/vmlinuz-4.9.0-4-amd64 > root=/dev/mapper/de--bln--vm--017--vg-root ro quiet > > ** Not tainted > > ** Kernel log: > [1.533757] EXT4-fs (dm-1): mounted filesystem with ordered data mode. > Opts: (null) > [1.847797] ip_tables: (C) 2000-2006 Netfilter Core Team > [1.912833] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT > +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS > +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN) > [1.912859] systemd[1]: Detected virtualization vmware. > [1.912863] systemd[1]: Detected architecture x86-64. > [1.914546] systemd[1]: Set hostname to . > [2.058639] random: crng init done > [2.131752] systemd[1]: Set up automount Arbitrary Executable File Formats > File System Automount Point. > [2.131812] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. > [2.131843] systemd[1]: Listening on Syslog Socket. > [2.131885] systemd[1]: Started Forward Password Requests to Wall > Directory Watch. > [2.131920] systemd[1]: Listening on udev Control Socket. > [2.131955] systemd[1]: Started Dispatch Password Requests to Console > Directory Watch. > [2.363268] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro > [2.516531] systemd-journald[833]: Received request to flush runtime > journal from PID 1 > [2.819683] input: Power Button as > /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 > [2.819691] ACPI: Power Button [PWRF] > [2.819819] ACPI: AC Adapter [ACAD] (on-line) > [2.875315] input: PC Speaker as /devices/platform/pcspkr/input/input5 > [2.881700] vmw_vmci :00:07.7: Found VMCI PCI device at 0x11080, irq 16 > [2.881767] vmw_vmci :00:07.7: Using capabilities 0xc > [2.882410] Guest personality initialized and is active > [2.882410] VMCI host device registered (name=vmci, major=10, minor=58) > [2.882410] Initialized host personality > [2.930410] [drm] Initialized > [2.941291] sd 0:0:0:0: Attached scsi generic sg0 type 0 > [2.941374] sd 0:0:1:0: Attached scsi generic sg1 type 0 > [2.941446] sd 0:0:2:0: Attached scsi generic sg2 type 0 > [2.941516] sd 0:0:3:0: Attached scsi generic sg3 type 0 > [2.941562] sr 2:0:0:0: Attached scsi generic sg4 type 5 > [3.012775] [drm] DMA map mode: Using physical TTM page addresses. > [3.012868] [drm] Capabilities: > [3.012873] [drm] Rect copy. > [3.012874] [drm] Cursor. > [3.012875] [drm] Cursor bypass. > [3.012876] [drm] Cursor bypass 2. > [3.012877] [drm] 8bit emulation. > [3.012878] [drm] Alpha cursor. > [3.012879] [drm] Extended Fifo. > [3.012880] [drm] Multimon. > [3.012881] [drm] Pitchlock. > [3.012882] [drm] Irq mask. > [3.012883] [drm] Display Topology. > [3.012884] [drm] GMR. > [3.012885] [drm] Traces. > [3.012886] [drm] GMR2. > [3.012887] [drm] Screen Object 2. > [3.012888] [drm] Command Buffers. > [3.012889] [drm] Command Buffers 2. > [3.012890] [drm] Guest Backed Resources. > [3.012891] [drm] DX Features. > [3.012893] [drm] Max GMR ids is 64 > [3.012894] [drm] Max number of GMR pages is 65536 > [3.012895] [drm] Max dedicated hypervisor surface memory is 0 kiB > [3.012896] [drm] Maximum display memory size is 4096 kiB > [3.012898] [drm] VRAM at 0xe800 size is 4096 kiB > [3.012899] [drm] MMIO at 0xfe00 size is 256 kiB > [3.012901] [drm] global init. > [3.013022] [TTM] Zone kernel: Available graphics memory: 60855752 kiB > [3.013023] [TTM] Zone dma32: Available graphics memory: 2097152 kiB > [3.013024] [TTM] Initializing pool allocator > [3.013029] [TTM] Initializing DMA pool allocator > [3.013122] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [3.013127] [drm] No driver support for vblank timestamp query. > [3.013382] [drm] Screen Target Display device initialized > [3.013441] [drm] width 640 > [3.013453] [drm] height 480 > [3.013465] [drm] bpp 32 > [3.014570] [drm] Fifo max 0x0004 min 0x1000 cap 0x077f > [3.015450] [drm] Using command buffers with DMA pool. > [3.015460] [drm] DX: no. > [3.015695] fbcon: svgadrmfb (fb0) is primary device > [3.017598] Console: switching to colour frame buffer device 100x37 > [3.096662] ppdev: user-space parallel port driver > [3.112337] [drm] Initialized vmwgfx 2.12.0
Bug#907451: libbiod FTBFS: Error: cannot implicitly convert expression
Hi Matthias, On Tue, Aug 28, 2018 at 03:39:56PM +0200, Matthias Klumpp wrote: > > > ... > > > [30/149] ldc2 -Ibiod@sha -I. -I.. -I -I../ -I/usr/include/d -enable-color > > > -O -g -release -wi -relocation-model=pic -of > > > 'biod@sha/bio_maf_reader.d.o' -c ../bio/maf/reader.d > > > FAILED: biod@sha/bio_maf_reader.d.o > > > ldc2 -Ibiod@sha -I. -I.. -I -I../ -I/usr/include/d -enable-color -O -g > > > -release -wi -relocation-model=pic -of 'biod@sha/bio_maf_reader.d.o' -c > > > ../bio/maf/reader.d > > > ../bio/maf/reader.d(40): Deprecation: struct > > > `std.stdio.File.ByLine!(char, char).ByLine` is deprecated - Use .byLine > > > ../bio/maf/reader.d(53): Error: cannot implicitly convert expression > > > `this._f.byLine(cast(Flag)true, '\x0a')` of type `ByLineImpl!(char, > > > char)` to `ByLine!(char, char)` > > > ../bio/maf/reader.d(53):`this._lines = > > > this._f.byLine(cast(Flag)true, '\x0a')` is the first assignment of > > > `this._lines` therefore it represents its initialization > > > ../bio/maf/reader.d(53):`opAssign` methods are not used for > > > initialization, but for subsequent assignments > > > [ > > Looks like an upstream issue - have you filed a bug there already? Upstream code das not changed since first release in Debian (Sat, 04 Mar 2017) I have no idea what kind of bug I should file. :-( Kind regards Andreas. -- http://fam-tille.de
Bug#907118: error:141a318a:ssl routines:tls_process_ske_dhe:dh key too small
On Tue, Aug 28, 2018 at 09:53:58AM -0300, Antonio Terceiro wrote:
> On Thu, Aug 23, 2018 at 03:24:52PM -0600, dann frazier wrote:
> > Package: bip
> > Version: 0.8.9-1.1
> > Severity: normal
> > Tags: patch
> >
> > I run bip on a stretch system, and connect to it from a hexchat client on
> > sid. After a recent upgrade of the client, which pulled in openssl 1.1,
> > hexchat began failing to connect to my server with the message:
> >
> > error:141a318a:ssl routines:tls_process_ske_dhe:dh key too small
> >
> > I found that backporting bip 0.9.0~rc3-1 to jessie worked. I further found
> > that just cherry-picking the following commit back to bip 0.8.9 seems to be
> > sufficient:
> >
> > 39414f8 Handle OpenSSL version 1.1
>
> I just tried backporting commit 39414f8 to the bip version in stretch,
> and it doesn't really fix the issue. There is probably some other commit
> that is needed.
I literally poked that patch into debian/patches{/series}, quilt
applied it and rebuilt, and it started working for me. Maybe there's
something different about our configs?
Bug#907559: cgview: Does not start
[Bug #907559 in CC which should collect information about this issue] Hi Markus, On Wed, Aug 29, 2018 at 05:16:38PM +0200, Markus Koschany wrote: > the newer Batik version in testing does not provide the XMLConstant > class anymore. They have split the functionality and moved it into a new > project called Batik Constants. > > https://mvnrepository.com/artifact/org.apache.xmlgraphics/batik-constants > > See also https://issues.apache.org/jira/browse/BATIK-1185 Ahhh, thanks for this helpful information. > Maybe you should raise this issue with upstream (Batik and/or cgview) Well cgview is not actively maintained (but has quite a number of users) and what exactly should I say to Batik upstream if they decided to move it to a noew project? I admit I have no idea what to say and where to report. Wouldn't it help more if I simply try to package batik-constants? Kind regards Andreas. -- http://fam-tille.de
Bug#904361: marked as done (python3-aiopg: fails to install with Python 3.7)
Your message dated Wed, 29 Aug 2018 17:18:57 + with message-id and subject line Bug#904361: fixed in aiopg 0.15.0-1 has caused the Debian Bug report #904361, regarding python3-aiopg: fails to install with Python 3.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 904361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-aiopg Version: 0.14.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 902788 with -1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up python3-aiopg (0.14.0-1) ... File "/usr/lib/python3/dist-packages/aiopg/connection.py", line 109 self._conn = psycopg2.connect(dsn, async=True, **kwargs) ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/aiopg/utils.py", line 18 ensure_future = asyncio.async ^ SyntaxError: invalid syntax dpkg: error processing package python3-aiopg (--configure): installed python3-aiopg package post-installation script subprocess returned error exit status 1 "async" has become a reserved keyword in Python 3.7 cheers, Andreas python3-aiopg=0.14.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: aiopg Source-Version: 0.15.0-1 We believe that the bug you reported is fixed in the latest version of aiopg, 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 904...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb (supplier of updated aiopg package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 29 Aug 2018 18:10:23 +0100 Source: aiopg Binary: python3-aiopg Architecture: source all Version: 0.15.0-1 Distribution: unstable Urgency: medium Maintainer: Piotr Ożarowski Changed-By: Chris Lamb Description: python3-aiopg - PostgreSQL integration with asyncio Closes: 904361 Changes: aiopg (0.15.0-1) unstable; urgency=medium . [ Chris Lamb ] * New upstream release. - Fix "async" import issue. (Closes: #904361) * debian/control: - Use for build-depends. - Bump Standards-Version to 4.2.1. - Use "https" Homepage URI. - wrap-and-sort. * Move to debhelper compat level 11. . [ Ondřej Nový ] * Convert git repository from git-dpm to gbp layout . [ Chris Lamb ] Checksums-Sha1: a9ad8dd37578c33f186374e32a06711dd6f1bbe3 2029 aiopg_0.15.0-1.dsc 7bef4561b4fcd36a9e8c654193060d0733e93e9b 27163 aiopg_0.15.0.orig.tar.gz 89790c41a49f1cc4439c67ddc46a497ce1b58012 2540 aiopg_0.15.0-1.debian.tar.xz bb9f60ded2e178380622a933c2315c35e6e18889 6630 aiopg_0.15.0-1_amd64.buildinfo b1840299d021046735e283283385e81e5a755a21 27176 python3-aiopg_0.15.0-1_all.deb Checksums-Sha256: 0a859669e91ebe7eab39da0b2bf9383db1b7cc7e3d8a30ea3ff357f7e5336124 2029 aiopg_0.15.0-1.dsc 2fa57bee0b7b8422408a79de085c3423e0b0633be3a0046b66a53594bf69a837 27163 aiopg_0.15.0.orig.tar.gz 03c97f34f66b5442c24d229619370fc1c8b4ea9ae8734f88f4a0624c5cfcf2e3 2540 aiopg_0.15.0-1.debian.tar.xz 69b83d640753e01b94a50ea4d8c28702728ad8fd280cc5db55f225fa2865a15b 6630 aiopg_0.15.0-1_amd64.buildinfo 1b4bb408a43789524b23a8ca3f08accd95f4b5640ccd37254c11adcaa67b0d5d 27176 python3-aiopg_0.15.0-1_all.deb Files: 0d7c203f8a7e10a455f66f4fa77d0ddf 2029 python optional aiopg_0.15.0-1.dsc 487029f0dfd45be181745f9a24bd2b05 27163 python optional aiopg_0.15.0.orig.tar.gz 9ffd426777aa8a4e45ab59270ffcfd34 2540 python optional aiopg_0.15.0-1.debian.tar.xz 09b20492122c65bb950718d3b500c8e8 6630 python optional aiopg_0.15.0-1_amd64.buildinfo 26310f418a4ad6092eefa78f919b7114 27176 python optional python3-aiopg_0.15.0-1_all.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAluG0+EACgkQHpU+J9Qx HliDtxAAhZofzRXR98/IWbFfmNtFiQg5IGI3a82rtpM6Sr+IWS4B/S5Y0je5LMpo
Processed: affects 907466
Processing commands for cont...@bugs.debian.org: > affects 907466 gedit Bug #907466 [iso-codes] Package doesn't ship xml files anymore Added indication that 907466 affects gedit > thanks Stopping processing here. Please contact me if you need assistance. -- 907466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907466 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#907553: Acknowledgement (libminc: wrong cmake installation path)
Processing control commands: > tags -1 patch Bug #907553 [src:libminc] libminc: wrong cmake installation path Added tag(s) patch. -- 907553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907553 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907553: Acknowledgement (libminc: wrong cmake installation path)
control: tags -1 patch
diff -Nru libminc-2.4.03/debian/changelog libminc-2.4.03/debian/changelog
--- libminc-2.4.03/debian/changelog 2018-08-26 17:10:28.0 +
+++ libminc-2.4.03/debian/changelog 2018-08-29 15:57:15.0 +
@@ -1,3 +1,9 @@
+libminc (2.4.03-1ubuntu1) cosmic; urgency=medium
+
+ * Fixup installation path (Closes: #907553)
+
+ -- Gianfranco Costamagna Wed, 29 Aug 2018
17:57:15 +0200
+
libminc (2.4.03-1) unstable; urgency=medium
* re-upload to sid
diff -Nru libminc-2.4.03/debian/libminc-dev.install
libminc-2.4.03/debian/libminc-dev.install
--- libminc-2.4.03/debian/libminc-dev.install 2018-08-26 17:10:28.0
+
+++ libminc-2.4.03/debian/libminc-dev.install 2018-08-29 15:57:15.0
+
@@ -1,5 +1,5 @@
usr/lib/*/lib*.so
-usr/lib/*/cmake/*.cmake
+usr/lib/*/cmake
usr/include/*
diff -Nru libminc-2.4.03/debian/patches/installation-cmake-path
libminc-2.4.03/debian/patches/installation-cmake-path
--- libminc-2.4.03/debian/patches/installation-cmake-path 1970-01-01
00:00:00.0 +
+++ libminc-2.4.03/debian/patches/installation-cmake-path 2018-08-29
15:57:14.0 +
@@ -0,0 +1,11 @@
+--- libminc-2.4.03.orig/CMakeLists.txt
libminc-2.4.03/CMakeLists.txt
+@@ -534,7 +534,7 @@ IF(LIBMINC_INSTALL_LIB_DIR AND NOT LIBMI
+
${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/Use${LIBMINC_EXTERNAL_LIB_PREFIX}LIBMINC.cmake
+
${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/${LIBMINC_EXTERNAL_LIB_PREFIX}LIBMINCConfig.cmake
+ DESTINATION
+- ${LIBMINC_INSTALL_LIB_DIR}/cmake
++ ${LIBMINC_INSTALL_LIB_DIR}/cmake/LIBMINC
+ COMPONENT Development)
+
+ ENDIF(LIBMINC_INSTALL_LIB_DIR AND NOT LIBMINC_INSTALL_NO_DEVELOPMENT)
diff -Nru libminc-2.4.03/debian/patches/series
libminc-2.4.03/debian/patches/series
--- libminc-2.4.03/debian/patches/series2018-08-26 17:10:28.0
+
+++ libminc-2.4.03/debian/patches/series2018-08-29 15:57:15.0
+
@@ -4,3 +4,4 @@
remove-rpath.patch
initialize_arrays_in_tests.patch
disable-dimension-test.patch
+installation-cmake-path
G.
Il mercoledì 29 agosto 2018, 12:27:06 CEST, Debian Bug Tracking System
ha scritto:
Thank you for filing a new Bug report with Debian.
You can follow progress on this Bug here: 907553:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907553.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.
Your message has been sent to the package maintainer(s):
Debian Med Packaging Team
If you wish to submit further information on this problem, please
send it to 907...@bugs.debian.org.
Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.
--
907553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#907226: marked as done (cutesdr: FTBFS with Qt 5.11)
Your message dated Wed, 29 Aug 2018 15:04:01 + with message-id and subject line Bug#907226: fixed in cutesdr 1.20-2 has caused the Debian Bug report #907226, regarding cutesdr: FTBFS with Qt 5.11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 907226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cutesdr Version: 1.20-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch dh_update_autotools_config -a dh_auto_configure -a qmake -makefile "QMAKE_CFLAGS_RELEASE=-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" "QMAKE_CFLAGS_DEBUG=-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" "QMAKE_CXXFLAGS_RELEASE=-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" "QMAKE_CXXFLAGS_DEBUG=-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" QMAKE_LFLAGS_RELEASE=-Wl,-z,relro QMAKE_LFLAGS_DEBUG=-Wl,-z,relro QMAKE_STRIP=: PREFIX=/usr Info: creating stash file /<>/.qmake.stash dh_auto_build -a make -j1 make[1]: Entering directory '/<>' /usr/lib/qt5/bin/uic unixforms/mainwindow.ui -o ui_mainwindow.h /usr/lib/qt5/bin/uic unixforms/sdrdiscoverdlg.ui -o ui_sdrdiscoverdlg.h /usr/lib/qt5/bin/uic unixforms/sounddlg.ui -o ui_sounddlg.h /usr/lib/qt5/bin/uic unixforms/sdrsetupdlg.ui -o ui_sdrsetupdlg.h /usr/lib/qt5/bin/uic unixforms/ipeditframe.ui -o ui_ipeditframe.h /usr/lib/qt5/bin/uic unixforms/editnetdlg.ui -o ui_editnetdlg.h /usr/lib/qt5/bin/uic unixforms/displaydlg.ui -o ui_displaydlg.h /usr/lib/qt5/bin/uic unixforms/sliderctrl.ui -o ui_sliderctrl.h /usr/lib/qt5/bin/uic unixforms/demodsetupdlg.ui -o ui_demodsetupdlg.h /usr/lib/qt5/bin/uic unixforms/testbench.ui -o ui_testbench.h /usr/lib/qt5/bin/uic unixforms/aboutdlg.ui -o ui_aboutdlg.h /usr/lib/qt5/bin/uic unixforms/noiseprocdlg.ui -o ui_noiseprocdlg.h /usr/lib/qt5/bin/uic unixforms/chatdialog.ui -o ui_chatdialog.h /usr/lib/qt5/bin/uic unixforms/recordsetupdlg.ui -o ui_recordsetupdlg.h /usr/lib/qt5/bin/uic unixforms/filetxdlg.ui -o ui_filetxdlg.h g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG -DQT_MULTIMEDIA_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -I. -isystem /usr/include/libdrm -I. -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o main.o gui/main.cpp g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG -DQT_MULTIMEDIA_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -I. -isystem /usr/include/libdrm -I. -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o sounddlg.o gui/sounddlg.cpp g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W
Bug#907226: cutesdr: FTBFS with Qt 5.11
Reiner Herrmann writes: > the attached patch fixes the FTBFS by including the missing header. ... > ++#include Hi, Thanks so much, but I see the upstream author Moe Wheatley has now also included this fix, so I have pulled a few more commits from upstreams work towards a version 1.21 onto a revised Debian packaging for version 1.20. I just want you to know that even though I did not apply your fix directly, I appreciate receiving it. -Maitland
Bug#906980: kmer: autopkgtest fails with segfault in testing/unstable while it passes in stable
Hi Andreas, On Mon, 27 Aug 2018 at 17:02 Andreas Tille wrote: > > Ah, finally a pretty simple solution for a quite hidden problem. > I admit I have expected something more serious :-) > BTW, I wonder whether there are tools that would warn about issues > described in[1] - I think there are good means to detect this > automatically. > I checked clang-tidy and it can warn about such issues. One more tool I would like to know now together with continuing of learning C. > Would you please forward this solution to upstream? May be once you > contact upstream asking for a versioned release for download would be a > good idea. > I wrote to upstream about the bug. Hope, they are interested in providing new releases. > Please note that I moved the data file into a separate package > kmer-examples to avoid duplication of the data files and enable users > installing the code without the data. Thus the package needs to pass > the new queue (hope this will happen soon). > Yes, thank you for this! I was not sure about putting data in a separate package as the data were small and there were no lintian warnings about this. Thanks a lot for you fine work. I think this issue is something you > can be really proud about since your work uncovered an issue and you > finally was able to fix it. I was happy to finally delete kmer from my list as it was hanging for so long :-P > I really hope you will be able to > continue this work even if GSoC is close to finished. May be, if you > have time you could continue a bit. I'd be very happy about this. > Many, many thanks to you for mentoring me! I definitely have time till September 10 before my master program starts. I would like to look into unicycler and maybe something else. With regards, Liubov
Bug#907489: sambamba FTBFS
Am Di., 28. Aug. 2018 um 20:16 Uhr schrieb Andreas Tille : > > Control: tags -1 help > > Hi Matthias, > > do you have any idea? Its most probably connected to the > libbiod bug. > [...] This appears to be a different issue to me - this one is a bit weirder than the BioD one. You can either apply the BioD patch and see if that fixes the problem, or directly report it upstream. This does not look Debian-specific at all, it rather looks like a generic upstream issue that happened because we are currently in a transition to a more recent compiler in Debian. Cheers, Matthias -- I welcome VSRE emails. See http://vsre.info/
Bug#907451: libbiod FTBFS: Error: cannot implicitly convert expression
Am Di., 28. Aug. 2018 um 15:39 Uhr schrieb Matthias Klumpp : > > Am Di., 28. Aug. 2018 um 10:40 Uhr schrieb Andreas Tille : > > > > On Tue, Aug 28, 2018 at 10:12:32AM +0300, Adrian Bunk wrote: > > > Source: libbiod > > > Version: 0.1.0-5 > > > Severity: serious > > > Tags: ftbfs > > > > > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libbiod.html > > > > > > ... > > > [30/149] ldc2 -Ibiod@sha -I. -I.. -I -I../ -I/usr/include/d -enable-color > > > -O -g -release -wi -relocation-model=pic -of > > > 'biod@sha/bio_maf_reader.d.o' -c ../bio/maf/reader.d > > > FAILED: biod@sha/bio_maf_reader.d.o > > > ldc2 -Ibiod@sha -I. -I.. -I -I../ -I/usr/include/d -enable-color -O -g > > > -release -wi -relocation-model=pic -of 'biod@sha/bio_maf_reader.d.o' -c > > > ../bio/maf/reader.d > > > ../bio/maf/reader.d(40): Deprecation: struct > > > `std.stdio.File.ByLine!(char, char).ByLine` is deprecated - Use .byLine > > > ../bio/maf/reader.d(53): Error: cannot implicitly convert expression > > > `this._f.byLine(cast(Flag)true, '\x0a')` of type `ByLineImpl!(char, > > > char)` to `ByLine!(char, char)` > > > ../bio/maf/reader.d(53):`this._lines = > > > this._f.byLine(cast(Flag)true, '\x0a')` is the first assignment of > > > `this._lines` therefore it represents its initialization > > > ../bio/maf/reader.d(53):`opAssign` methods are not used for > > > initialization, but for subsequent assignments > > > [ > > Looks like an upstream issue - have you filed a bug there already? You don't even need to file a bug - looks like upstream fixed this already in https://github.com/biod/BioD/commit/dd07f3497979b5d7f32ad32476da5108ffc5121e, so all you need to do is take that patch. -- I welcome VSRE emails. See http://vsre.info/
Bug#907466: Package doesn't ship xml files anymore
On Tue, 28 Aug 2018 11:58:46 +0200 Laurent Bigonville wrote: > Package: iso-codes > Version: 4.0-1 > Severity: serious > > Hi, > > Since 4.0-1, iso-codes package is not shipping the xml files anymore: > >* New upstream version 4.0 > - This new release does no longer include the XML data files. >Please use the JSON data files from now on. > > This causes at least one other package to break (gnome-software) > > Could you please check the package that are actually using the xml files > and help them to transition to the JSON ones Possibly affected: https://codesearch.debian.net/search?q=iso-codes.*xml $ curl -s https://codesearch.debian.net/results/feb40fd23d0d6182/packages.json | jq -r '.Packages[]' gtranslator apper openjfx ldm choose-mirror network-manager-applet pluma epiphany-browser gimagereader performous onboard django-countries gaupol lintian java-gnome quodlibet iso-codes libisocodes ibus firefox kaffeine python-apt gst-plugins-base1.0 software-properties workrave https://codesearch.debian.net/search?q=iso_codes_parse.*%5C.xml gspell, hexchat, gtkspell3 -- -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#907168: marked as done (pytest-httpbin FTBFS with OpenSSL 1.1.1)
Your message dated Wed, 29 Aug 2018 13:49:17 +
with message-id
and subject line Bug#907168: fixed in pytest-httpbin 0.3.0-4
has caused the Debian Bug report #907168,
regarding pytest-httpbin FTBFS with OpenSSL 1.1.1
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.)
--
907168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest-httpbin
Version: 0.3.0-3
Severity: serious
Tags: ftbfs
Control: block 907015 by -1
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pytest-httpbin.html
...
I: pybuild base:217: python2.7 -m pytest -v -x -s
= test session starts ==
platform linux2 -- Python 2.7.15, pytest-3.6.4, py-1.5.4, pluggy-0.6.0 --
/usr/bin/python2.7
cachedir: .pytest_cache
rootdir: /build/1st/pytest-httpbin-0.3.0, inifile:
plugins: httpbin-0.3.0
collecting ... collected 19 items
tests/test_httpbin.py::test_httpbin_gets_injected PASSED
tests/test_httpbin.py::test_httpbin_accepts_get_requests 127.0.0.1 - -
[23/Aug/2018 22:26:12] "GET /get HTTP/1.1" 200 218
PASSED
tests/test_httpbin.py::test_httpbin_secure_accepts_get_requests pytest-httpbin
server hit an exception serving request: [SSL: CA_MD_TOO_WEAK] ca md too weak
(_ssl.c:2779)
attempting to ignore so the rest of the tests can run
FAILED
=== FAILURES ===
___ test_httpbin_secure_accepts_get_requests ___
httpbin_secure =
def test_httpbin_secure_accepts_get_requests(httpbin_secure):
> assert requests.get(httpbin_secure.url + '/get').status_code == 200
tests/test_httpbin.py:15:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python2.7/dist-packages/requests/api.py:72: in get
return request('get', url, params=params, **kwargs)
/usr/lib/python2.7/dist-packages/requests/api.py:58: in request
return session.request(method=method, url=url, **kwargs)
/usr/lib/python2.7/dist-packages/requests/sessions.py:508: in request
resp = self.send(prep, **send_kwargs)
/usr/lib/python2.7/dist-packages/requests/sessions.py:618: in send
r = adapter.send(request, **kwargs)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self =
request = , stream = False
timeout =
verify = '/build/1st/pytest-httpbin-0.3.0/pytest_httpbin/certs/cacert.pem'
cert = None, proxies = OrderedDict([('no', 'localhost')])
def send(self, request, stream=False, timeout=None, verify=True, cert=None,
proxies=None):
"""Sends PreparedRequest object. Returns Response object.
:param request: The :class:`PreparedRequest `
being sent.
:param stream: (optional) Whether to stream the request content.
:param timeout: (optional) How long to wait for the server to send
data before giving up, as a float, or a :ref:`(connect timeout,
read timeout) ` tuple.
:type timeout: float or tuple or urllib3 Timeout object
:param verify: (optional) Either a boolean, in which case it
controls whether
we verify the server's TLS certificate, or a string, in which
case it
must be a path to a CA bundle to use
:param cert: (optional) Any user-provided SSL certificate to be
trusted.
:param proxies: (optional) The proxies dictionary to apply to the
request.
:rtype: requests.Response
"""
conn = self.get_connection(request.url, proxies)
self.cert_verify(conn, request.url, verify, cert)
url = self.request_url(request, proxies)
self.add_headers(request)
chunked = not (request.body is None or 'Content-Length' in
request.headers)
if isinstance(timeout, tuple):
try:
connect, read = timeout
timeout = TimeoutSauce(connect=connect, read=read)
except ValueError as e:
# this may raise a string formatting error.
err = ("Invalid timeout {0}. Pass a (connect, read) "
"timeout tuple, or a single float to set "
"both timeouts to the same value".format(timeout))
raise ValueError(err)
elif isinstance(timeout, TimeoutSauce):
pass
else:
timeout = TimeoutSauce(connect=timeout, read=timeout)
try:
if not chunked:
resp
Bug#898380: marked as done (libreadline-java-doc: fails to upgrade from 'stretch' - trying to overwrite /usr/share/doc/libreadline-java/NEWS.gz)
Your message dated Wed, 29 Aug 2018 13:34:10 + with message-id and subject line Bug#898380: fixed in libreadline-java 0.8.0.1+dfsg-9 has caused the Debian Bug report #898380, regarding libreadline-java-doc: fails to upgrade from 'stretch' - trying to overwrite /usr/share/doc/libreadline-java/NEWS.gz 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.) -- 898380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libreadline-java-doc Version: 0.8.0.1+dfsg-7 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stretch'. It installed fine in 'stretch', then the upgrade to 'buster' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package libreadline-java-doc. Preparing to unpack .../libreadline-java-doc_0.8.0.1+dfsg-7_all.deb ... Unpacking libreadline-java-doc (0.8.0.1+dfsg-7) ... dpkg: error processing archive /var/cache/apt/archives/libreadline-java-doc_0.8.0.1+dfsg-7_all.deb (--unpack): trying to overwrite '/usr/share/doc/libreadline-java/NEWS.gz', which is also in package libreadline-java 0.8.0.1+dfsg-5 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libreadline-java-doc_0.8.0.1+dfsg-7_all.deb This is probably fallout from changed dh_installdocs behaviour in debhelper compat level 11. cheers, Andreas libreadline-java=0.8.0.1+dfsg-5_libreadline-java-doc=0.8.0.1+dfsg-7.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: libreadline-java Source-Version: 0.8.0.1+dfsg-9 We believe that the bug you reported is fixed in the latest version of libreadline-java, 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 898...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated libreadline-java 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, 29 Aug 2018 14:57:45 +0200 Source: libreadline-java Binary: libreadline-java libreadline-java-doc Architecture: source Version: 0.8.0.1+dfsg-9 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Description: libreadline-java - GNU readline and BSD editline wrappers for Java libreadline-java-doc - API docs for readline/editline wrappers for Java Closes: 898380 Changes: libreadline-java (0.8.0.1+dfsg-9) unstable; urgency=medium . * Team upload. * Declare compliance with Debian Policy 4.2.1. * Set Breaks and Replaces in debian/control. The documentation is now only installed by libreadline-java-doc but was installed by both packages in Stretch. (Closes: #898380) Checksums-Sha1: 066eaa88f32914b1abaa6def199bb479fb267f99 2361 libreadline-java_0.8.0.1+dfsg-9.dsc b42f61b580834966444b9e1d3e43493e30b89ba5 9716 libreadline-java_0.8.0.1+dfsg-9.debian.tar.xz c8b466dfc9724286ec67310f98d41cf191cbd459 12169 libreadline-java_0.8.0.1+dfsg-9_amd64.buildinfo Checksums-Sha256: 1476f636614923c36791fd0ec40dc9c94bd8dd71db561337f1c4553bd82fafaa 2361 libreadline-java_0.8.0.1+dfsg-9.dsc 69ac2d4c3c8848b0d6d68325cce317d1fee5c1205dfa6a1c04e26a80a42a6831 9716 libreadline-java_0.8.0.1+dfsg-9.debian.tar.xz 5affbdb773adb587cd9db7b438fc3f67109e8c24d2afadf0935bba30b3237987 12169 libreadline-java_0.8.0.1+dfsg-9_amd64.buildinfo Files: c3e3831efc7cb04ad7288d8591cba827 2361 java optional libreadline-java_0.8.0.1+dfsg-9.dsc a4245e55196648aae4931e801d0c2d5e 9716 java optional libreadline-java_0.8.0.1+dfsg-9.debian.tar.xz 42246c817b01c8181a262b91c69bfb68 12169 java optional libreadline-java_0.8.0.1+dfsg-9_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAluGmgxfFIAALgAo
Processed: found 907559 in 0.0.20100111-3
Processing commands for cont...@bugs.debian.org: > found 907559 0.0.20100111-3 Bug #907559 [cgview] cgview: Does not start Marked as found in versions cgview/0.0.20100111-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 907559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907559 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: libminc: wrong cmake installation path
Processing control commands: > severity -1 serious Bug #907553 [src:libminc] libminc: wrong cmake installation path Severity set to 'serious' from 'normal' > affects -1 src:minc-tools Bug #907553 [src:libminc] libminc: wrong cmake installation path Added indication that 907553 affects src:minc-tools -- 907553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907553 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Processed: reopening 902220
Processing control commands: > severity -1 serious Bug #902220 [aspectc++] aspect++: Please use llvm-dev instead of llvm-4.0-dev Severity set to 'serious' from 'normal' -- 902220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#902220: Processed: reopening 902220
Control: severity -1 normal
Hi Adrian,
Thanks for your bug maintenance work, much appreciated!
On 08/28/2018 08:27 PM, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
>
>> reopen 902220
> Bug #902220 {Done: Reinhard Tartler } [aspectc++]
> aspect++: Please use llvm-dev instead of llvm-4.0-dev
Are you sure about the severity "serious" of this bug? AspectC++ still needs
porting to llvm-6.0 and won't build right now. llvm-4.0-dev is still in testing
at this point. Please provide a reference to the llvm upgrade timeline that I
could share with upstream.
Best,
-rt
Processed: Re: Processed: reopening 902220
Processing control commands: > severity -1 normal Bug #902220 [aspectc++] aspect++: Please use llvm-dev instead of llvm-4.0-dev Severity set to 'normal' from 'serious' -- 902220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907559: cgview: Does not start
Package: cgview Severity: grave Justification: renders package unusable Hi, cgview in sid/testing does not start while the same code base in stable works perfectly. It just dies with: $ cgview Error: Unable to initialize main class ca.ualberta.stothard.cgview.CgviewIO Caused by: java.lang.NoClassDefFoundError: org/apache/batik/util/XMLConstants Olivier Sallou suspected that the issue could be caused by the version of Batik which is 1.8 in stable and 1.10 in testing/sid. I've checked both source code and JARs for instance like $ grep -wl XMLConstants /usr/share/java/batik* /usr/share/java/batik-all-1.10.jar /usr/share/java/batik-all.jar /usr/share/java/batik-constants-1.10.jar /usr/share/java/batik-constants.jar /usr/share/java/batik.jar /usr/share/java/batik-libs.jar on a machine (testing) where it fails and where cgview works (stable): $ $ grep -wl XMLConstants /usr/share/java/batik* /usr/share/java/batik-1.8.jar /usr/share/java/batik-all-1.8.jar /usr/share/java/batik-all.jar /usr/share/java/batik.jar /usr/share/java/batik-libs-1.8.jar /usr/share/java/batik-libs.jar /usr/share/java/batik-util-1.8.jar /usr/share/java/batik-util.jar The only interesting difference is that on stable (batik-1.8) the symbol is inside /usr/share/java/batik-util.jar while it is not any more in batik 1.10. The tricky thing is that the string XMLConstants itself is not part of the cgview source code so simply changing util in something else that can be found is not possible and may be the bug is simply in one of the dependencies and not in cgview itself. That's why I take the freedom to add Debian Java list in CC of this bug report. Kind regards Andreas. -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core) 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 cgview depends on: pn default-jre | java8-runtime pn jarwrapper pn libbatik-java pn libcommons-lang-java pn libjargs-java pn libxerces2-java cgview recommends no packages. cgview suggests no packages.
Bug#896786: rss2email: missing build dependency on python3-distutils
On Tue, Apr 24, 2018 at 12:42:34PM +0300, Adrian Bunk wrote:
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rss2email.html
>
> ...
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.6 setup.py clean
> Traceback (most recent call last):
> File "setup.py", line 21, in
> from distutils.core import setup
> ModuleNotFoundError: No module named 'distutils.core'
> E: pybuild pybuild:336: 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: *** [debian/rules:4: clean] Error 25
>
>
> Due to
>
> python3.6 (3.6.5~rc1-2) unstable; urgency=medium
>
> * python3.6: Drop dependency on python3-distutils.
> ...
> -- Matthias Klose Tue, 20 Mar 2018 14:29:58 +0800
May I also point that the current upstream seems poorly maintained and
eventually should be replaced by another repo (see
https://github.com/wking/rss2email/issues/93 and
https://github.com/wking/rss2email/issues/105).
Unfortunaletly the situation may not be better there :
https://github.com/rss2email/rss2email/issues/18
In any case, the Debian side needs work, whatever source for upstream is
;)
Hth if anyone cares about rss2email.
Best regards,
--
Olivier BERGER
http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingenieur Recherche - Dept INF
Institut Mines-Telecom, Telecom SudParis, Evry (France)
Processed: severity of 897284 is normal
Processing commands for cont...@bugs.debian.org: > severity 897284 normal Bug #897284 [rss2email] rss2email: barfs "sax parsing error: :2:0: syntax error:" even on debian rss feeds Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 897284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897284: rss2email: barfs "sax parsing error: :2:0: syntax error:" even on debian rss feeds
On Tue, May 01, 2018 at 11:48:37AM +0200, Gregor Zattler wrote: > Dear Maintainer, > > I configured r2e as described in the man page quick start and run > it. It did not work but gave this info: > >* What exactly did you do (or not do) that was effective (or > ineffective)? > > $ r2e -V -V -V -V -V -V -V -V -V -V -V run > load feed configuration from ['/etc/xdg/rss2email.cfg', > '/home/grfz/.config/rss2email.cfg'] > loaded configuration from ['/home/grfz/.config/rss2email.cfg'] > load feed data from /home/grfz/.local/share/rss2email.json > fetch debian-news (url -> https://www.debian.org/News/news) > process debian-news (url -> https://www.debian.org/News/news) May I suggest that you post an excerpt of r2e list ? I think you probably misconfigured the Debian feed. I think the trace should exhibit something like : fetch debian-news (https://www.debian.org/News/news -> u...@example.com) which gives me the impression that you mistyped the arguments of the r2e add, using "url" instead of the URL of the feed and the URL instead of the optional recipient of the mails. Tell me if I'm guessing right. Then this show-stopper bug could probably be closed. Hope this helps -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France)
Processed: tagging 897284
Processing commands for cont...@bugs.debian.org: > tags 897284 + moreinfo Bug #897284 [rss2email] rss2email: barfs "sax parsing error: :2:0: syntax error:" even on debian rss feeds Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 897284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906244: gimp: crashes while starting
Package: gimp Version: 2.10.6-2 Followup-For: Bug #906244 Dear Maintainer, Gimp crashes upon initiation. The starting splash screen appears but is grey and after the Crash Debug screen appears. Restart GIMP button cannot restart gimp. After closing the gimp crash debug screen gimp will restart but after three restarts the same crash report was observed. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.17.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.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gimp depends on: ii gimp-data2.10.6-2 ii libaa1 1.4p5-44+b2 ii libbabl-0.1-00.1.56-1 ii libbz2-1.0 1.0.6-9 ii libc62.27-5 ii libcairo21.15.12-1 ii libfontconfig1 2.13.0-5 ii libfreetype6 2.8.1-2 ii libgcc1 1:8.2.0-4 ii libgdk-pixbuf2.0-0 2.36.12-2 ii libgegl-0.4-00.4.8-1 ii libgexiv2-2 0.10.8-1 ii libgimp2.0 2.10.6-2 ii libglib2.0-0 2.56.1-2 ii libgs9 9.22~dfsg-3 ii libgtk2.0-0 2.24.32-3 ii libgudev-1.0-0 232-2 ii libharfbuzz0b1.8.8-2 ii libheif1 1.3.2-1 ii libilmbase23 2.2.1-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-2 2.9-2 ii liblzma5 5.2.2-1.3 ii libmng1 1.0.10+dfsg-3.1+b5 ii libmypaint-1.3-0 1.3.0-2 ii libopenexr23 2.2.1-4 ii libopenjp2-7 2.3.0-1 ii libpango-1.0-0 1.42.4-2 ii libpangocairo-1.0-0 1.42.4-2 ii libpangoft2-1.0-01.42.4-2 ii libpng16-16 1.6.34-2 ii libpoppler-glib8 0.63.0-2 ii librsvg2-2 2.40.20-3 ii libstdc++6 8.2.0-4 ii libtiff5 4.0.9-6 ii libwebp6 0.6.1-2 ii libwebpdemux20.6.1-2 ii libwebpmux3 0.6.1-2 ii libwmf0.2-7 0.2.8.4-12 ii libx11-6 2:1.6.6-1 ii libxcursor1 1:1.1.15-1 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxmu6 2:1.1.2-2 ii libxpm4 1:3.5.12-1 ii xdg-utils1.1.3-1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages gimp recommends: ii ghostscript 9.22~dfsg-3 Versions of packages gimp suggests: ii gimp-data-extras 1:2.0.2-1 pn gimp-help-en | gimp-help pn gimp-python ii gvfs-backends 1.36.2-1 ii libasound21.1.6-1 -- no debconf information
Processed: forwarded #902820
Processing commands for cont...@bugs.debian.org: > forwarded #902820 t...@gene.com Bug #902820 [src:gmap] gmap: FTBFS on stretch/amd64 if CPU has SSE2 and nothing more Set Bug forwarded-to-address to 't...@gene.com'. > End of message, stopping processing here. Please contact me if you need assistance. -- 902820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906350: doxia: FTBFS in buster/sid (Cannot find parent dependency org.apache.maven:maven-parent:pom:27)
Control: tags -1 confirmed > [ERROR] The build could not read 1 project -> [Help 1] > [ERROR] > [ERROR] The project org.apache.maven.doxia:doxia:1.7 > (/<>/pom.xml) has 1 error > [ERROR] Invalid packaging for parent POM > org.apache.maven:maven-parent:27, must be "pom" but is "jar" @ > org.apache.maven:maven-parent:27 This issue was caused by the relocation of org.apache.maven:maven-parent in libmaven-parent-java. The relocated pom.xml file is of type jar now instead of type pom. This should be fixed in maven-debian-helper or in libmaven-parent-java in my opinion. See also #907554. Markus signature.asc Description: OpenPGP digital signature
Processed: Re: doxia: FTBFS in buster/sid (Cannot find parent dependency org.apache.maven:maven-parent:pom:27)
Processing control commands: > tags -1 confirmed Bug #906350 [src:doxia] doxia: FTBFS in buster/sid (Cannot find parent dependency org.apache.maven:maven-parent:pom:27) Added tag(s) confirmed. -- 906350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#900821: linux-image-4.9.0-6-amd64: apache reads wrong data over cifs filesystems served by samba
Hi! I have rechecked everything again. Salvatore, I'm testing on an up to date buster running kernel 4.17.17-1 and I still see the kernel warning messages and the downloads are breaking and wget still shows this king of messages: 2018-08-29 13:45:31 (122 MB/s) - Read error at byte 1056768/6538880 (Bad address). Retrying. So I see no progresses with newer versions or anything like that. Don't know what are the differences between your setup and mine, maybe it is the file length? What seems to work ok is the workaround of setting EnableSendfile to on, this avoids the original problem I had found on Stretch and also the problems I later found on buster with the kernel warnings and broken downloads. Hope this helps. Regards. -- Manty/BestiaTester -> http://manty.net
Bug#906375: libitext5-java: FTBFS in buster/sid (method marshal in class org.apache.jcp.xml.dsig.internal.dom.DOMXMLSignature cannot be applied to given types)
On 28/08/2018 21:31, Jochen Sprickerhof wrote: > As a quick fix we could probably hack around the visibility modifiers of > Marshaller, but I guess that would be rather ugly. Just mentioning it > for completeness. +1 for adjusting the xml-security API. Emmanuel Bourg
Bug#893817: Fwd: [saltstack/salt-jenkins] [Py3][Tornado 5.0] IOLoop tests failing with asyncio (#995)
Hi, Upstream isn't fixing this in the next minor release of Salt, so it looks like we won't be able to ship Salt 2018.3 in Debian any time soon (unless we switch back to making it use Py2 temporarily). I'm sorry to be bringing the bad news, and I would suggest waiting for the Fluorine release: - switching back and forth between py2 and py3 would likely break things, - the ones who absolutely need Salt in buster or sid are likely using the vendor's repository (as Salt has been broken in Debian for ~half a year) Of course, as I'm not in the Salt team, my opinion should likely be taken with... a grain of salt ;) Best, nicoo - Forwarded message from Daniel Wallace - Date: Tue, 28 Aug 2018 05:46:22 -0700 From: Daniel Wallace To: saltstack/salt-jenkins Cc: Nicolas Braud-Santoni , Comment Subject: Re: [saltstack/salt-jenkins] [Py3][Tornado 5.0] IOLoop tests failing with asyncio (#995) This is not going to be fixed in 2018.3.3, you will have to stick with salt with python2 for versions where python-tornado is already upgraded. This is will be fixed in Fluorine for python3 and if it is not too complicated it may be backported to 2018.3 once it has finished, but it is not holding up the 2018.3.3 release. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/saltstack/salt-jenkins/issues/995#issuecomment-416570266 - End forwarded message - signature.asc Description: PGP signature
Bug#907505: marked as done (/bin/gzip: error while loading shared libraries: cannot restore segment prot after reloc)
Your message dated Wed, 29 Aug 2018 09:19:26 + with message-id and subject line Bug#907505: fixed in logrotate 3.14.0-4 has caused the Debian Bug report #907505, regarding /bin/gzip: error while loading shared libraries: cannot restore segment prot after reloc 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.) -- 907505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: logrotate Version: 3.14.0-3 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** Yesterday on my servers the logrotate package was updated. The change in this upgrade was the migration from invocation by cron to a systemd timer. This night logrotate tried to run and do its job, and failed: Aug 28 00:00:01 fu.fsck.at logrotate[14276]: error: Compressing program wrote following message to stderr when compressing log /var/log/syslog.1: Aug 28 00:00:01 fu.fsck.at logrotate[14276]: /bin/gzip: error while loading shared libraries: cannot restore segment prot after reloc: Operation not permitted Aug 28 00:00:01 fu.fsck.at logrotate[14276]: error: failed to compress log /var/log/syslog.1 I encountered this error on all i686 systems, but not on the amd64 systems. Some results from googling indicate that this might be related to SELinux. I do not use SELinux, but apparmor. However, there are no rules active related to logrotate or gzip. After reading https://github.com/systemd/systemd/issues/5400 I suspect that MemoryDenyWriteExecute in the logrotate.service file is causing this. -- Package-specific info: Contents of /etc/logrotate.d total 40 -rw-r--r-- 1 root root 120 Oct 21 2017 alternatives -rw-r--r-- 1 root root 442 Sep 3 2017 apache2 -rw-r--r-- 1 root root 173 Aug 6 2012 apt -rw-r--r-- 1 root root 130 Aug 21 22:23 btmp -rw-r--r-- 1 root root 112 Oct 21 2017 dpkg -rw-r--r-- 1 root root 313 Mar 19 2014 fail2ban -rw-r--r-- 1 root root 120 Nov 27 2014 munin-node -rw-r--r-- 1 root root 501 Jul 1 2017 rsyslog -rw-r--r-- 1 root root 235 May 27 2015 unattended-upgrades -rw-r--r-- 1 root root 145 Feb 19 2018 wtmp -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 4.17.0-3-686-pae (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages logrotate depends on: ii cron [cron-daemon] 3.0pl1-130 ii libacl1 2.2.52-3+b1 ii libc6 2.27-5 ii libpopt01.16-11 ii libselinux1 2.8-1+b1 ii systemd-sysv239-7 Versions of packages logrotate recommends: ii bsd-mailx [mailx] 8.1.2-0.20180807cvs-1 logrotate suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: logrotate Source-Version: 3.14.0-4 We believe that the bug you reported is fixed in the latest version of logrotate, 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 907...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Göttsche (supplier of updated logrotate 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, 29 Aug 2018 00:21:11 +0200 Source: logrotate Binary: logrotate Architecture: source Version: 3.14.0-4 Distribution: unstable Urgency: medium Maintainer: Christian Göttsche Changed-By: Christian Göttsche Description: logrotate - Log rotation utility Closes: 730420 907505 Changes: logrotate (3.14.0-4) unstable; urgency=medium . * d/control: - add Multi-Arch: foreign (Closes: #730420) - bump to std version 4.2.1 (no further changes) * d/tests: - fix and add simple test * d/patches: drop MemoryDenyWriteExecute from systemd service (Closes: #907505) Checksums-Sha1: cbbd2c60c348889cb6ba3924ec1a64118e1919a3 1943 logrotate_3.14.0-4.dsc dc16bea61c2349a7006458dbd5d24efa483c667c 18048 logrotate_3.14.0-4.debian.tar.xz
Processed: tagging 907538
Processing commands for cont...@bugs.debian.org: > tags 907538 + ftbfs Bug #907538 [src:audit] audit: FTBFS: /usr/bin/ld: lookup_test.o: file not recognized: file truncated Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 907538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 907538 is forwarded to https://github.com/linux-audit/audit-userspace/pull/63
Processing commands for cont...@bugs.debian.org: > forwarded 907538 https://github.com/linux-audit/audit-userspace/pull/63 Bug #907538 [src:audit] audit: FTBFS: /usr/bin/ld: lookup_test.o: file not recognized: file truncated Changed Bug forwarded-to-address to 'https://github.com/linux-audit/audit-userspace/pull/63' from 'https://github.com/linux-audit/audit-userspace/issues/65'. > thanks Stopping processing here. Please contact me if you need assistance. -- 907538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 907538 is forwarded to https://github.com/linux-audit/audit-userspace/issues/65
Processing commands for cont...@bugs.debian.org: > forwarded 907538 https://github.com/linux-audit/audit-userspace/issues/65 Bug #907538 [src:audit] audit: FTBFS: /usr/bin/ld: lookup_test.o: file not recognized: file truncated Set Bug forwarded-to-address to 'https://github.com/linux-audit/audit-userspace/issues/65'. > thanks Stopping processing here. Please contact me if you need assistance. -- 907538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907538: audit: FTBFS: /usr/bin/ld: lookup_test.o: file not recognized: file truncated
Source: audit Version: 1:2.8.4-1 Severity: serious The latest upload of audit FTBFS on various architectures. It looks like a test program is built twice in parallel and make stumbles upon that[1]: , | make[5]: Entering directory '/<>/debian/build/auparse/test' | gcc -DHAVE_CONFIG_H -I. -I../../../../auparse/test -I../.. -I../../../../auparse -I../../../../lib -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o auparse_test.o ../../../../auparse/test/auparse_test.c | ../../../../auparse/test/auparselol_test.c: In function 'main': | ../../../../auparse/test/auparselol_test.c:219:46: warning: format '%lu' expects argument of type 'long unsigned int', but argument 4 has type 'unsigned int' [-Wformat=] | "%s: No memory to allocate %lu bytes\n", | ~~^ | %u | argv[0], sizeof(int)); | ~~~ | /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -static -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o auparselol_test auparselol_test.o ../../auparse/libauparse.la ../../lib/libaudit.la | libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o auparselol_test auparselol_test.o ../../auparse/.libs/libauparse.a /<>/debian/build/lib/.libs/libaudit.a ../../lib/.libs/libaudit.a -lcap-ng | /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -static -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o auparse_test auparse_test.o ../../auparse/libauparse.la ../../lib/libaudit.la | gcc -DHAVE_CONFIG_H -I. -I../../../../auparse/test -I../.. -I../../../../auparse -I../../../../lib -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o auparselol_test.o ../../../../auparse/test/auparselol_test.c | gcc -DHAVE_CONFIG_H -I. -I../../../../auparse/test -I../.. -I../../../../auparse -I../../../../lib -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o lookup_test.o ../../../../auparse/test/lookup_test.c | make[5]: Nothing to be done for '../../../../auparse/test/auparse_test.py'. | ../../../../auparse/test/auparselol_test.c: In function 'main': | ../../../../auparse/test/auparselol_test.c:219:46: warning: format '%lu' expects argument of type 'long unsigned int', but argument 4 has type 'unsigned int' [-Wformat=] | "%s: No memory to allocate %lu bytes\n", | ~~^ | %u | argv[0], sizeof(int)); | ~~~ | libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o auparse_test auparse_test.o ../../auparse/.libs/libauparse.a /<>/debian/build/lib/.libs/libaudit.a ../../lib/.libs/libaudit.a -lcap-ng | /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -static -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o auparse_test auparse_test.o ../../auparse/libauparse.la ../../lib/libaudit.la | /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -static -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o auparselol_test auparselol_test.o ../../auparse/libauparse.la ../../lib/libaudit.la | libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o auparselol_test auparselol_test.o ../../auparse/.libs/libauparse.a /<>/debian/build/lib/.libs/libaudit.a ../../lib/.libs/libaudit.a -lcap-ng | libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o auparse_test auparse_test.o ../../auparse/.libs/libauparse.a /<>/debian/build/lib/.libs/libaudit.a ../../lib/.libs/libaudit.a -lcap-ng | /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o lookup_test lookup_test.o ../../auparse/libauparse.la ../../lib/libaudit.la | libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o
Processed: Upstream ticket exists
Processing commands for cont...@bugs.debian.org: > forwarded 907156 https://sourceforge.net/p/chessx/bugs/254/ Bug #907156 [src:chessx] chessx: FTBFS in buster/sid (invalid use of incomplete type 'class QButtonGroup') Set Bug forwarded-to-address to 'https://sourceforge.net/p/chessx/bugs/254/'. > tags 907156 fixed-upstream Bug #907156 [src:chessx] chessx: FTBFS in buster/sid (invalid use of incomplete type 'class QButtonGroup') Added tag(s) fixed-upstream. > End of message, stopping processing here. Please contact me if you need assistance. -- 907156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907168: [Python-modules-team] Bug#907168: pytest-httpbin FTBFS with OpenSSL 1.1.1
Hi, út 28. 8. 2018 v 15:36 odesílatel Pierre-Elliott Bécue napsal: > This would imply to do a Debian patch in upstream's source. > I had similar bug in eventlet, solution: https://github.com/eventlet/eventlet/pull/516 https://salsa.debian.org/python-team/modules/python-eventlet/commit/32dc98ce3519b42b4edfe02b9599b916b052c84c -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Bug#907157: cura-engine: FTBFS in buster/sid (Error copying directory)
Control: tags -1 fixed-upstream patch Juhani Numminen kirjoitti 28.08.2018 klo 23:50: > Dear maintainer, > > Applying this patch might fix the FTBFS. I haven't tried myself yet. > > https://github.com/Ultimaker/CuraEngine/commit/5aad55bf67e52ce5bdb27a3925af8a4cab441b38#diff-af3b638bc2a3e6c650974192a53c7291 Seems to work (on amd64, cowbuilder). > Cheers, > Juhani
Processed: Re: cura-engine: FTBFS in buster/sid (Error copying directory)
Processing control commands: > tags -1 fixed-upstream patch Bug #907157 [src:cura-engine] cura-engine: FTBFS in buster/sid (Error copying directory) Added tag(s) patch and fixed-upstream. -- 907157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907157 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#907493: ghostscript breaks cups autopkgtest: test times out
Processing control commands: > tags -1 + moreinfo Bug #907493 [src:ghostscript, src:cups] ghostscript breaks cups autopkgtest: test times out Added tag(s) moreinfo. -- 907493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906623: heimdal: FTBFS in buster/sid (hcrypto/engine.h: No such file or directory)
On Wed, Aug 29, 2018 at 01:34:53PM +1000, Brian May wrote: > Santiago Vila writes: > > > make[3]: Entering directory '/<>/heimdal-7.5.0+dfsg/lib/hcrypto' > > CC test_rand.o > > In file included from test_rand.c:42: > > rand.h:46:10: fatal error: hcrypto/engine.h: No such file or directory > > #include > > ^~ > > compilation terminated. > > make[3]: *** [Makefile:2060: test_rand.o] Error 1 > > make[3]: Leaving directory '/<>/heimdal-7.5.0+dfsg/lib/hcrypto' > > make[2]: *** [Makefile:565: all-recursive] Error 1 > > make[2]: Leaving directory '/<>/heimdal-7.5.0+dfsg/lib' > > make[1]: *** [Makefile:613: all-recursive] Error 1 > > make[1]: Leaving directory '/<>/heimdal-7.5.0+dfsg' > > dh_auto_build: make -j1 returned exit code 2 > > make: *** [debian/rules:7: build-indep] Error 2 > > dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit > > status 2 > > > > I simply cannot reproduce this error. > > Are you sure you didn't accidentally delete the supplied > ./lib/hcrypto/engine.h file? I'm using sbuild on a single-cpu virtual machine, so no, I'm not accidentally deleting anything. Please try using sbuild on a single-cpu virtual machine, and, if you still can't reproduce it, I could offer a virtual machine for you to ssh into it and see it directly (please contact me privately for details). Thanks.
Bug#907493: ghostscript breaks cups autopkgtest: test times out
Control: tags -1 + moreinfo Quoting Graham Inggs (2018-08-29 00:56:49) > Control: severity -1 serious > Control: found -1 ghostscript/9.22~dfsg-3 > > Hi Jonas > > I'm bumping the severity of this bug to prevent ghostscript from > migrating until the cups autopkgtest regression has been investigated. Thanks for reporting, Paul, and for blocking, Graham. It would be most helpful if someone could dig out from that convoluted ci-in-cups test the actual ghostscript command causing cups to hang. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Processed: block 907015 with 907528
Processing commands for cont...@bugs.debian.org: > block 907015 with 907528 Bug #907015 [src:openssl] openssl version 1.1.1 breaks multiple reverse dependencies; versioned Breaks needed 907015 was blocked by: 898803 906955 895959 898807 907135 898802 891625 907215 907339 907216 900160 898805 907427 900159 907049 897651 898800 907031 900156 900158 898804 906997 900152 900153 907033 907079 907168 900154 900161 897643 907518 907022 907219 907055 897658 906981 907028 900157 907491 907340 907278 897652 891665 907118 898801 900982 907015 was not blocking any bugs. Added blocking bug(s) of 907015: 907528 > thanks Stopping processing here. Please contact me if you need assistance. -- 907015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907015 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907505: /bin/gzip: error while loading shared libraries: cannot restore segment prot after reloc
Probably caused by #890279
