Bug#960571: Missing dependency on fontconfig
Package: rst2pdf Version: 0.93-7 Severity: serious Hi, rst2pdf calls fc-match in findfonts.py, but does not list a dependency on fontconfig. If you don't have it installed, building the document will succeed but the document itself is empty. Cheers, Thijs
Bug#945739: marked as done (RM: symeig -- RoQA; package obsolete; blocking py2 removal)
Your message dated Thu, 14 May 2020 04:38:56 + with message-id and subject line Bug#945739: Removed package(s) from unstable has caused the Debian Bug report #945739, regarding RM: symeig -- RoQA; package obsolete; blocking py2 removal 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.) -- 945739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: symeig Version: 1.5-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: python-symeig | 1.5-2 | all python-symeig-dbg | 1.5-2 | all symeig | 1.5-2 | source --- Reason --- RoQA; package obsolete; blocking py2 removal -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 945...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/945739 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: Re: Bug#960327: squid: autopkgtest regression: test_daemons (__main__.BasicTest)
Processing control commands: > tags -1 + patch Bug #960327 [src:squid] squid: autopkgtest regression: test_daemons (__main__.BasicTest) Added tag(s) patch. -- 960327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960327 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960327: squid: autopkgtest regression: test_daemons (__main__.BasicTest)
Control: tags -1 + patch On Monday, May 11 2020, Paul Gevers wrote: > Dear maintainer(s), > > With a recent upload of squid the autopkgtest of squid fails in testing > when that autopkgtest is run with the binary packages of squid from > unstable. It passes when run with only packages from testing. In tabular > form: > >passfail > squid from testing4.11-4 > all others from testingfrom testing > > I copied some of the output at the bottom of this report. > > Currently this regression is blocking the migration to testing [1]. Can > you please investigate the situation and fix it? > > More information about this bug and the reason for filing it can be found on > https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation > > Paul > > [1] https://qa.debian.org/excuses.php?package=squid > > https://ci.debian.net/data/autopkgtest/testing/amd64/s/squid/5424910/log.gz > autopkgtest [00:09:42]: test squid: [--- > Considering dependency setenvif for ssl: > Module setenvif already enabled > Considering dependency mime for ssl: > Module mime already enabled > Considering dependency socache_shmcb for ssl: > Enabling module socache_shmcb. > Enabling module ssl. > See /usr/share/doc/apache2/README.Debian.gz on how to configure SSL and > create self-signed certificates. > To activate the new configuration, you need to run: > systemctl restart apache2 > Enabling site default-ssl. > To activate the new configuration, you need to run: > systemctl reload apache2 > test_daemons (__main__.BasicTest) > Test daemon ... FAIL > test_ftp_proxy (__main__.BasicTest) > Test ftp ... ok > test_http_proxy (__main__.BasicTest) > Test http ... ok > test_https_proxy (__main__.BasicTest) > Test https ... ok > test_squidclient (__main__.BasicTest) > Test squidclient ... ok > test_zz_apparmor (__main__.BasicTest) > Test apparmor ... ok > > == > FAIL: test_daemons (__main__.BasicTest) > Test daemon > -- > Traceback (most recent call last): > File > "/tmp/autopkgtest-lxc.lb13ubw0/downtmp/build.JEa/src/debian/tests/test-squid.py", > line 120, in test_daemons > self.assertTrue(check_pidfile(exe, pidfile)) > AssertionError: False is not true > > -- > Ran 6 tests in 236.530s > > FAILED (failures=1) > autopkgtest [00:13:40]: test squid: ---] Here's a patch that fixes the issue above. Please note that even after fixing this specific issue, I still see another failure with test_zz_apparmor. I've posted a merge request to also fix this problem here: https://salsa.debian.org/squid-team/squid/-/merge_requests/12 Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible https://sergiodj.net/ diff --git a/debian/changelog b/debian/changelog index a504329d..7b501b4d 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +squid (4.11-5) UNRELEASED; urgency=medium + + * Fix 'pidfile' on d/t/tests-squid.py. +The pidfile lives under '/run/squid/', not '/run/'. (Closes: #960327) + + -- Sergio Durigan Junior Wed, 13 May 2020 21:22:29 -0400 + squid (4.11-4) unstable; urgency=medium [ Amos Jeffries ] diff --git a/debian/tests/test-squid.py b/debian/tests/test-squid.py index 53a5af9a..c5de7b95 100644 --- a/debian/tests/test-squid.py +++ b/debian/tests/test-squid.py @@ -114,7 +114,7 @@ class BasicTest(HttpdCommon): def test_daemons(self): '''Test daemon''' -pidfile = "/run/squid.pid" +pidfile = "/run/squid/squid.pid" exe = "squid" self.assertTrue(check_pidfile(exe, pidfile)) signature.asc Description: PGP signature
Bug#960561: amanda-common should depend on libjson-perl
Subject: amanda-common should depend on libjson-perl Package: amanda-common Version: 1:3.5.1-2+b2 Severity: serious Justification: Policy 3.5 Dear Maintainer, /usr/lib/x86_64-linux-gnu/amanda/perl/Amanda/Message.pm says "use JSON;" on line 29, but libjson-perl is not declared as a dependency. -- System Information: Debian Release: 10.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/1 CPU core) 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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages amanda-common depends on: ii adduser 3.118 ii bsd-mailx [mailx] 8.1.2-0.20180807cvs-1 ii debconf [debconf-2.0] 1.5.71 ii libc6 2.28-10 ii libcurl4 7.64.0-4+deb10u1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libssl1.1 1.1.1d-0+deb10u3 ii openbsd-inetd [inet-superserver] 0.20160825-4 ii perl 5.28.1-6 ii perl-base [perlapi-5.28.0] 5.28.1-6 ii update-inetd 4.49 amanda-common recommends no packages. Versions of packages amanda-common suggests: ii amanda-client 1:3.5.1-2+b2 -- debconf information excluded
Bug#960488: marked as done (eslint: autopkgtest failure: missing test dependency to node-babel7)
Your message dated Wed, 13 May 2020 22:04:27 + with message-id and subject line Bug#960488: fixed in eslint 5.16.0~dfsg-6 has caused the Debian Bug report #960488, regarding eslint: autopkgtest failure: missing test dependency to node-babel7 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.) -- 960488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: eslint Version: 5.16.0~dfsg-5 Severity: serious Justification: unknwon Hi, node-babel7 seems required by autopkgtest test: not ok 344 - /tmp/autopkgtest-lxc.9p09fhxf/downtmp/build.w0w/src/lib/formatters/codeframe.js --- message: '"@babel/code-frame" is not found.' severity: error data: line: 8 column: 38 ruleId: node/no-missing-require ... Cheers, Xavier --- End Message --- --- Begin Message --- Source: eslint Source-Version: 5.16.0~dfsg-6 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of eslint, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated eslint 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, 13 May 2020 23:44:00 +0200 Source: eslint Architecture: source Version: 5.16.0~dfsg-6 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jonas Smedegaard Closes: 960488 Changes: eslint (5.16.0~dfsg-6) unstable; urgency=medium . * fix have autopkgtest depend on node-babel7 (not node-babel-code-frame); closes: bug#960488, thanks to Xavier Guimard Checksums-Sha1: 4d5aaf93e5e812bdd1a08fd25ba2629b1a712db1 3476 eslint_5.16.0~dfsg-6.dsc de9ff38d4cfd4912c9c90f5ac64059e423545d91 27892 eslint_5.16.0~dfsg-6.debian.tar.xz 26164be1c884853e3ac9817323bf1961d08c5537 14207 eslint_5.16.0~dfsg-6_amd64.buildinfo Checksums-Sha256: fad4de5b1da7c025b5dbe5f603ba86601c119c8ef91452952b8436fa6d120daf 3476 eslint_5.16.0~dfsg-6.dsc ff0486889078f4b215dde4a6601d58ff69fe6a4a98c2e62c8a85942e9740450e 27892 eslint_5.16.0~dfsg-6.debian.tar.xz c1538847a7d54b4eef8b4d440fb57a3e73b67106027874c060af5e6f8de4fe3b 14207 eslint_5.16.0~dfsg-6_amd64.buildinfo Files: 0847b2bc37c70b22d0c1aaa7119ee473 3476 javascript optional eslint_5.16.0~dfsg-6.dsc bb16eb6bb465045a2d50331eda38268c 27892 javascript optional eslint_5.16.0~dfsg-6.debian.tar.xz c26437832f6d25d2c9189b4fb124bbb7 14207 javascript optional eslint_5.16.0~dfsg-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl68awUACgkQLHwxRsGg ASEWUQ//aI9yPO0BAuuBg/p6URxdvRndXGRzMBFOv1XUp2hH1TGhhey1tFpWKwET bo3to94WSdOb+PfI/lvi1q9/igpAIQn1bNnNCvqZqQrKJm2U7cRBMmtxWCdHcAai +fEFoamfcxJnxFeW2Xc4BdzOQsFiUYnL9gWceO3NW863JrWiKw0MhCewifEdLeM8 Dwvet0hQjHo1E6a9p4+GuoKftlEen9yjn9llS46rNiZlI3EvcefWHpoGjZH/5eHw HhRd+RyPu6rFIauxLQYtxGBnQc+S3OyiDckuE4TFV7DiUcJtM2QZA970Jz8mWDQj 4FKcnlO4uA1y21XXK4IvhLG93SSxn9LcVfcI+zu5cD2ay+SHIVEEbatGZrtfaAFx JNYkChTwOE5MwnhSuzZId7rMlnpdoIpInoOnumbFoqN7z/pC+rbUIm9YMnBDFTxs CCYWfBpHQlFoS6o8wbBCoYiiO2LcQGi1I6/hIwquUVhKhzfgdhFLtHva+h+se8kO a4Mh/+gZIfm4VrLVP4wmo/s3z7NaTwPfi25x3C8A3roFo4pGOaSrVLPfSqo1mIBj 9Buvlc/ZReiFRbPkjWmrYqq+z4lQocyo554xfd8eUxdD5bB75oCJzmh/oMV1ZEiv 7e+GljG10ztH9S63WKnjMs+V86pj5kQPwDVr5MEseEzrd0cR6iM= =MuBQ -END PGP SIGNATURE End Message ---
Processed: Bug#960488 marked as pending in eslint
Processing control commands: > tag -1 pending Bug #960488 [eslint] eslint: autopkgtest failure: missing test dependency to node-babel7 Added tag(s) pending. -- 960488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960488: marked as pending in eslint
Control: tag -1 pending Hello, Bug #960488 in eslint reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/eslint/-/commit/725b0c294c59d48a63e8b4d2a379b683b073fdce fix have autopkgtest depend on node-babel7 (not node-babel-code-frame); closes: bug#960488, thanks to Xavier Guimard (this message was generated automatically) -- Greetings https://bugs.debian.org/960488
Processed: Re: Pushing verbose mode
Processing control commands: > tags -1 patch Bug #960294 [src:tigr-glimmer] tigr-glimmer does not trap errors from make Ignoring request to alter tags of bug #960294 to the same tags previously set -- 960294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960294 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960294: Pushing verbose mode
Control: tags -1 patch Hi Helmut, Helmut Grohne, on 2020-05-13 14:14:19 +0200: > I fear you only implemented a partial solution (based on my > recommendation here). In my tests, failures still go unchecked. I think > at least one issue is the linker rule in src/c_make.gen starting with > line 359. You added "set -e" there. The command snippet has an outer if > branch to select the linker (C vs C++) and an inner branch that removes > the linked file on failure. Unfortunately, the failure path does not > propagate the failure, because it is already captured in the if. Thus > swallowing errors. I didn't see this when writing my bug report either. Yes, I must admit the symbols soup does not make this structure very apparent. I modified the patch and tried to adapt the logic here without drifting too much out of the original file, yet it required reorganizing the commands a bit. After some testing, error codes from the linking stage should be returned properly; if otherwise then I would tend to think the linker didn't return an error code in the first place. > Beyond this, I strongly recommend implementing verbose build logs. The > issue would have been much easier to spot with verbose build logs. Build > logs have been a release goal[1]. Building verbosely is also recommended > by the Debian policy section 4.9. Unfortunately, the build system at > hand doesn't make this possible without patching. Agreed. I did a thorough rereading of the Makefiles, and got rid of the "@" prefix of most commands. Build logs are now showing what is happening, so even if changes here over are not sufficient to close the bug yet, at least the verbosity level should now allow to see more clearly what is happening. I made the patch available on Salsa. If maybe you wish to have a try and review changes, before further package upload, you can grab it here: https://salsa.debian.org/med-team/tigr-glimmer/-/blob/master/debian/patches/make-errs.patch I hope this one will help. > Helmut > > [1] https://wiki.debian.org/ReleaseGoals/VerboseBuildLogs Kind Regards, -- Étienne Mollier Fingerprint: 5ab1 4edf 63bb ccff 8b54 2fa9 59da 56fe fff3 882d Help find cures against the Covid-19 ! Give CPU cycles: * Rosetta@home: https://boinc.bakerlab.org/rosetta/ * Folding@home: https://foldingathome.org/ signature.asc Description: PGP signature
Bug#959455: fakeroot-ng: diff for NMU version 0.18-4.1
Control: tags 959455 + patch Control: tags 959455 + pending Dear maintainer, I've prepared an NMU for fakeroot-ng (versioned as 0.18-4.1) and uploaded it to mentors for sponsoring. Please feel free to tell me if I should remove it. -- Regards Sudip diff -Nru fakeroot-ng-0.18/debian/changelog fakeroot-ng-0.18/debian/changelog --- fakeroot-ng-0.18/debian/changelog 2014-04-12 17:35:09.0 +0100 +++ fakeroot-ng-0.18/debian/changelog 2020-05-13 21:10:17.0 +0100 @@ -1,3 +1,10 @@ +fakeroot-ng (0.18-4.1) unstable; urgency=medium + + * Non-maintainer upload. + * Remove dependency on linux-kernel-headers. (Closes: #959455) + + -- Sudip Mukherjee Wed, 13 May 2020 21:10:17 +0100 + fakeroot-ng (0.18-4) unstable; urgency=medium * Remove /dev/shm. Again. diff -Nru fakeroot-ng-0.18/debian/control fakeroot-ng-0.18/debian/control --- fakeroot-ng-0.18/debian/control 2014-04-12 17:42:55.0 +0100 +++ fakeroot-ng-0.18/debian/control 2020-05-13 21:06:07.0 +0100 @@ -2,7 +2,7 @@ Section: utils Priority: extra Maintainer: Shachar Shemesh -Build-Depends: debhelper (>= 9), autotools-dev, linux-kernel-headers, gcc (>= 4:4.7), g++ (>= 4:4.7) +Build-Depends: debhelper (>= 9), autotools-dev, gcc (>= 4:4.7), g++ (>= 4:4.7) Homepage: http://fakeroot-ng.lingnu.com Standards-Version: 3.9.5.0
Bug#960391: marked as done (evdi-dkms: drmP.h removed in linux 5.5)
Your message dated Wed, 13 May 2020 21:04:56 + with message-id and subject line Bug#960391: fixed in evdi 1.7.0+dfsg-1 has caused the Debian Bug report #960391, regarding evdi-dkms: drmP.h removed in linux 5.5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 960391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: evdi-dkms Version: 1.6.4+dfsg-1 Severity: grave Justification: renders package unusable evdi-dkms is currently unable to build the kernel module. /var/lib/dkms/evdi/1.6.4+dfsg/build/make.log reports: CC [M] /var/lib/dkms/evdi/1.6.4+dfsg/build/evdi_gem.o /var/lib/dkms/evdi/1.6.4+dfsg/build/evdi_drv.c:11:10: fatal error: drm/drmP.h: No such file or directory 11 | #include | ^~~~ compilation terminated. The problem is known upstream, https://github.com/DisplayLink/evdi/issues/185 https://github.com/DisplayLink/evdi/issues/199 Marking this bug with severity grave since it affects the standard linux kernel in unstable, linux-image-amd64 5.6.7-1 -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages evdi-dkms depends on: ii dkms 2.8.1-5 Versions of packages evdi-dkms recommends: ii libevdi0 1.6.4+dfsg-1 evdi-dkms suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: evdi Source-Version: 1.7.0+dfsg-1 Done: Hanno Stock We believe that the bug you reported is fixed in the latest version of evdi, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hanno Stock (supplier of updated evdi 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, 13 May 2020 17:12:15 +0200 Source: evdi Architecture: source Version: 1.7.0+dfsg-1 Distribution: experimental Urgency: medium Maintainer: Hanno Stock Changed-By: Hanno Stock Closes: 948983 954396 960391 Changes: evdi (1.7.0+dfsg-1) experimental; urgency=medium . * new upstream release 1.7.0 - fixes incompatibility with newer kernels (closes: #960391, #954396, #948983) * drop patch 0001-Make-library-Makefile-respect-LDFLAGS.patch * bump debhelper compatibility level to 13 * update symbols for libevdi0 * bump standards version to 4.5.0 * d/control: set rules-requires-root to no Checksums-Sha1: 20271830a51deccb4eb25cc239820bcfe4127d96 2025 evdi_1.7.0+dfsg-1.dsc 76ece500bab39cd215d6f9b3ef1bde1c7f3ed256 36240 evdi_1.7.0+dfsg.orig.tar.xz 670ad3158fdcd741ca782d643217930d93c61333 4420 evdi_1.7.0+dfsg-1.debian.tar.xz b4fb0ba5cfdadf8f094631a8f11ccb90929eed0f 7191 evdi_1.7.0+dfsg-1_amd64.buildinfo Checksums-Sha256: 162d9b8feaf7a1f573d0a0028216aea6e1234b6be4656aa1399c0e6969b72236 2025 evdi_1.7.0+dfsg-1.dsc fc2f141a7f4f80c065b2f2810b255b6aac2262cc0eda7bd28192998d62e3b1ee 36240 evdi_1.7.0+dfsg.orig.tar.xz 571eff5bf05f3a978ff3d5c43df7431ce33668a5e95fc0668cb9aaf157a1c00a 4420 evdi_1.7.0+dfsg-1.debian.tar.xz 7b18501f95b91ece9381bfa4e6a1f7857ced6582ffed9dd432c831060557c5ce 7191 evdi_1.7.0+dfsg-1_amd64.buildinfo Files: 39b7cdbd6db6aa71bc9ef4dbcbb9e04a 2025 misc optional evdi_1.7.0+dfsg-1.dsc a9deef70a1a6f04d92ee7b2db5f7a288 36240 misc optional evdi_1.7.0+dfsg.orig.tar.xz cec0d1db698607f2e624e9c719040631 4420 misc optional evdi_1.7.0+dfsg-1.debian.tar.xz c7127dda9e82f74bfe6a5ddbdefba6ee 7191 misc optional evdi_1.7.0+dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEECEGLvkRyDy26xQXsunokltrkDRwFAl68XkUACgkQunokltrk DRwPAg//dxd69jPlFXEXAD5jOII19Evt3oRvxXCCx+ccectxGBC6OmBbRYIvPcSI fqO6+GS4/T1hALyv5trSg6pQyiSydqaF5UoHi4Iirhmy95WNskVjO/J7j/Uo53Lf
Processed: fakeroot-ng: diff for NMU version 0.18-4.1
Processing control commands: > tags 959455 + patch Bug #959455 [src:fakeroot-ng] fakeroot-ng: Build-Depends on obsolete package linux-kernel-headers Added tag(s) patch. > tags 959455 + pending Bug #959455 [src:fakeroot-ng] fakeroot-ng: Build-Depends on obsolete package linux-kernel-headers Added tag(s) pending. -- 959455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#945739: symeig - RM?
Processing control commands: > reassign -1 ftp.debian.org Bug #945739 [src:symeig] symeig: Python2 removal in sid/bullseye Bug reassigned from package 'src:symeig' to 'ftp.debian.org'. No longer marked as found in versions symeig/1.5-2. Ignoring request to alter fixed versions of bug #945739 to the same values previously set > retitle -1 RM: symeig -- RoQA; package obsolete; blocking py2 removal Bug #945739 [ftp.debian.org] symeig: Python2 removal in sid/bullseye Changed Bug title to 'RM: symeig -- RoQA; package obsolete; blocking py2 removal' from 'symeig: Python2 removal in sid/bullseye'. -- 945739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945739: symeig - RM?
Control: reassign -1 ftp.debian.org Control: retitle -1 RM: symeig -- RoQA; package obsolete; blocking py2 removal
Bug#945739: symeig - RM?
the last changelog msg I see is symeig (1.5-2) unstable; urgency=low * Deprecating symeig as a separate package -- functionality was included in scipy (>=0.7.0), please use scipy.linalg.eigh instead. * Transitional packages became architecture 'all' instead of 'any' * Boosted policy to 3.8.3: - -dbg got correct "section: debug" and "priority: extra" -- Yaroslav Halchenko Mon, 16 Nov 2009 08:55:44 -0500 so indeed it is time for it to RiP ;) please RM On Wed, 13 May 2020, Scott Talbert wrote: > Hi, > It seems that symeig has no (longer?) reverse depends and it seems to be > abandoned upstream. Is the best solution just to remove it? -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
Processed: NMU fixes are missing in libgraphics-colornames-perl 3.5.0-1
Processing commands for cont...@bugs.debian.org:
> unarchive 839022
Bug #839022 {Done: Andreas Tille }
[libgraphics-colornames-perl] libgraphics-colornames-perl: Build-Depends on
perl-modules-5.22
Unarchived Bug 839022
> found 839022 3.5.0-1
Bug #839022 {Done: Andreas Tille }
[libgraphics-colornames-perl] libgraphics-colornames-perl: Build-Depends on
perl-modules-5.22
There is no source info for the package 'libgraphics-colornames-perl' at
version '3.5.0-1' with architecture ''
Unable to make a source version for version '3.5.0-1'
Marked as found in versions 3.5.0-1 and reopened.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
839022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#945739: symeig - RM?
Hi, It seems that symeig has no (longer?) reverse depends and it seems to be abandoned upstream. Is the best solution just to remove it? Thanks, Scott
Bug#960349: marked as done (libmrpt-tfest-dev,libmrpt-bayes-dev: missing Breaks+Replaces: libmrpt-dev (<< 1:2))
Your message dated Wed, 13 May 2020 19:19:21 + with message-id and subject line Bug#960349: fixed in mrpt 1:2.0.3-1 has caused the Debian Bug report #960349, regarding libmrpt-tfest-dev,libmrpt-bayes-dev: missing Breaks+Replaces: libmrpt-dev (<< 1:2) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 960349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmrpt-tfest-dev,libmrpt-bayes-dev Version: 1:2.0.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' 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/ch-relationships.html#overwriting-files-and-replacing-packages-replaces This test intentionally skipped 'testing' to find file overwrite problems before packages migrate from 'unstable' to 'testing'. >From the attached log (scroll to the bottom...): ... Selecting previously unselected package libmrpt-bayes-dev. Preparing to unpack .../23-libmrpt-bayes-dev_1%3a2.0.2-1_amd64.deb ... Unpacking libmrpt-bayes-dev (1:2.0.2-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-lpS9iV/23-libmrpt-bayes-dev_1%3a2.0.2-1_amd64.deb (--unpack): trying to overwrite '/usr/include/mrpt/bayes/include/mrpt/bayes/CKalmanFilterCapable.h', which is also in package libmrpt-dev 1:1.5.6-1+b1 ... Selecting previously unselected package libmrpt-tfest-dev. Preparing to unpack .../27-libmrpt-tfest-dev_1%3a2.0.2-1_amd64.deb ... Unpacking libmrpt-tfest-dev (1:2.0.2-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-lpS9iV/27-libmrpt-tfest-dev_1%3a2.0.2-1_amd64.deb (--unpack): trying to overwrite '/usr/include/mrpt/tfest/include/mrpt/tfest/indiv-compat-decls.h', which is also in package libmrpt-dev 1:1.5.6-1+b1 Errors were encountered while processing: /tmp/apt-dpkg-install-lpS9iV/23-libmrpt-bayes-dev_1%3a2.0.2-1_amd64.deb /tmp/apt-dpkg-install-lpS9iV/27-libmrpt-tfest-dev_1%3a2.0.2-1_amd64.deb cheers, Andreas libmrpt-dev=1:1.5.6-1+b1_libmrpt-tfest-dev=1:2.0.2-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: mrpt Source-Version: 1:2.0.3-1 Done: =?utf-8?q?Jos=C3=A9_Luis_Blanco_Claraco?= We believe that the bug you reported is fixed in the latest version of mrpt, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. José Luis Blanco Claraco (supplier of updated mrpt 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, 13 May 2020 17:46:04 +0200 Source: mrpt Architecture: source Version: 1:2.0.3-1 Distribution: unstable Urgency: medium Maintainer: José Luis Blanco Claraco Changed-By: José Luis Blanco Claraco Closes: 960349 Changes: mrpt (1:2.0.3-1) unstable; urgency=medium . * Fix missing Breaks+Replaces in debian/control (Closes: #960349). * New version of upstream sources. Checksums-Sha1: c224fba0038f7f1e926763e10357021649ea1b0c 7496 mrpt_2.0.3-1.dsc 3e9b57ae6e8caf29afff1ea2dbbce8d87ba54014 32249344 mrpt_2.0.3.orig.tar.gz 7e8d6a81f42a916169f07c4833b7da1546279367 18184 mrpt_2.0.3-1.debian.tar.xz 6154ebcb0559aea35e4c3bd6980426e54509 59121 mrpt_2.0.3-1_amd64.buildinfo Checksums-Sha256: 88dce78ee6139a90504aa262fad7f19f070ac549f4e4bb7421a944b535d9e12d 7496 mrpt_2.0.3-1.dsc e9e292b42c24753c6e03024cb58aaefcfa84961e5de1d4328afed062b92e5e21 32249344 mrpt_2.0.3.orig.tar.gz d21775e7894585c7f46e51a656cb293293bb377416a10780cfd3991591f3426a 18184 mrpt_2.0.3-1.debian.tar.xz 8cd1d7cd67ad137f690b5cdb2272d67382d92c273585b6a9678564a39cacabb5 59121 mrpt_2.0.3-1_amd64.buildinfo Files: 904652d86e881f1fb64db293df4fc878 7496 science optional mrpt_2.0.3-1.dsc 830e445f079cfc23b3e5746bd9db5094 32249344 science optional mrpt_2.0.3.orig.tar.gz e1e863d8a0ca9fcd6437ec5953035d58 18184 science optional mrpt_2.0.3-1.debian.tar.xz
Bug#960508: marked as done (removal of pcb-rnd-{core,doc,rnd-import-net} makes files disappear from pcb-rnd/stable)
Your message dated Wed, 13 May 2020 19:19:41 +
with message-id
and subject line Bug#960508: fixed in pcb-rnd 2.2.1-2
has caused the Debian Bug report #960508,
regarding removal of pcb-rnd-{core,doc,rnd-import-net} makes files disappear
from pcb-rnd/stable
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.)
--
960508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pcb-rnd-core,pcb-rnd-doc,pcb-rnd-import-net
Version: 2.2.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks
Hi,
during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.
The installation sequence to reproduce this problem is
apt-get install pcb-rnd/buster
# (1)
apt-get install pcb-rnd-core
apt-get remove pcb-rnd-core
# (2)
The list of installed files at points (1) and (2) should be identical,
but the following files have disappeared:
/usr/bin/fp2subc
/usr/bin/pcb-prj2lht
/usr/bin/pcb-rnd
/usr/share/man/man1/fp2subc.1.gz
/usr/share/man/man1/pcb-prj2lht.1.gz
/usr/share/man/man1/pcb-rnd.1.gz
/usr/share/pcb-rnd/default2.lht
/usr/share/pcb-rnd/default4.lht
/usr/share/pcb-rnd/default_font
/usr/share/pcb-rnd/pcblib/connector/BNC_LAY.fp
/usr/share/pcb-rnd/pcblib/connector/DB15F.fp
/usr/share/pcb-rnd/pcblib/connector/DB15M.fp
/usr/share/pcb-rnd/pcblib/connector/DB25F.fp
/usr/share/pcb-rnd/pcblib/connector/DB25M.fp
...
/usr/share/pcb-rnd/pcblib/tru-hole/TO247.fp
/usr/share/pcb-rnd/pcblib/tru-hole/TO247_2.fp
/usr/share/pcb-rnd/pcblib/tru-hole/TO251.fp
/usr/share/pcb-rnd/pcblib/tru-hole/TO264.fp
/usr/share/pcb-rnd/pcblib/tru-hole/TO39.fp
/usr/share/pcb-rnd/pcblib/tru-hole/TO92.fp
This is a serious bug violating policy 7.6, see
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
and also see the footnote that describes this incorrect behavior:
https://www.debian.org/doc/debian-policy/ch-relationships.html#id13
The pcb-rnd-core package has the following relationships with pcb-rnd:
Conflicts: n/a
Breaks:n/a
Replaces: pcb-rnd (<< 2.2.0-2)
>From the attached log (scroll to the bottom...):
2m24.4s DEBUG: Modified(user, group, mode, size, target):
/var/lib/dpkg/info/pcb-rnd.list expected(root, root, - 100644, 17589, None) !=
found(root, root, - 100644, 12508, None)
2m24.4s ERROR: FAIL: After purging files have disappeared:
/usr/bin/fp2subc owned by: pcb-rnd-core
/usr/bin/pcb-prj2lht owned by: pcb-rnd-core
/usr/bin/pcb-rnd owned by: pcb-rnd-core
/usr/share/man/man1/fp2subc.1.gz owned by: pcb-rnd-core
/usr/share/man/man1/pcb-prj2lht.1.gz owned by: pcb-rnd-core
...
/usr/share/pcb-rnd/pcblib/tru-hole/TO251.fpowned by: pcb-rnd-core
/usr/share/pcb-rnd/pcblib/tru-hole/TO264.fpowned by: pcb-rnd-core
/usr/share/pcb-rnd/pcblib/tru-hole/TO39.fp owned by: pcb-rnd-core
/usr/share/pcb-rnd/pcblib/tru-hole/TO92.fp owned by: pcb-rnd-core
2m24.4s ERROR: FAIL: After purging files have been modified:
/var/lib/dpkg/info/pcb-rnd.listnot owned
Similar problems happen with pcb-rnd-doc and pcb-rnd-import-net.
Please add
Breaks: pcb-rnd (<< 2.2.0-2)
to all three packages to prevent such partial upgrades.
cheers,
Andreas
pcb-rnd=2.1.1-1_pcb-rnd-core=2.2.0-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pcb-rnd
Source-Version: 2.2.1-2
Done: Bdale Garbee
We believe that the bug you reported is fixed in the latest version of
pcb-rnd, 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 960...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bdale Garbee (supplier of updated pcb-rnd 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, 13 May 2020 12:46:59 -0600
Source: pcb-rnd
Architecture: source
Version: 2.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Electronics Team
Processed: severity of 960458 is serious
Processing commands for cont...@bugs.debian.org: > # Raise to RC to indicate release critical for the regression stable -> > testing as long it would be unfixed > severity 960458 serious Bug #960458 [src:libreswan] libreswan: CVE-2020-1763 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 960458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960458 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952055: marked as pending in paulstretch
Control: tag -1 pending Hello, Bug #952055 in paulstretch reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/multimedia-team/paulstretch/-/commit/ca5d45c568549f61a7fd5e455aad2988e2ddc96e Fix FTBFS. (Closes: #952055) Signed-off-by: Sudip Mukherjee (this message was generated automatically) -- Greetings https://bugs.debian.org/952055
Bug#960438: marked as done (blender: OpenColorIO configuration error prevents launching)
Your message dated Wed, 13 May 2020 20:40:54 +0200 with message-id <87d0777k5l.fsf@localhost> and subject line Re: Bug#960438: blender: OpenColorIO configuration error prevents launching has caused the Debian Bug report #960438, regarding blender: OpenColorIO configuration error prevents launching 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.) -- 960438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: blender Version: 2.82.a+dfsg-1+b2 Severity: normal Dear Maintainer, Blender recently updated, and will not launch. I receive the error: OpenColorIO Error: Error: Loading the OCIO profile '/usr/share/blender/datafiles/colormanagement/config.ocio' failed. The specified file does not appear to be an OCIO configuration. Aborted I am unable to use blender given this error with OpenColorIO. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages blender depends on: ii blender-data 2.82.a+dfsg-1 ii fonts-dejavu 2.37-1 ii libavcodec58 7:4.2.2-1+b1 ii libavdevice58 7:4.2.2-1+b1 ii libavformat58 7:4.2.2-1+b1 ii libavutil56 7:4.2.2-1+b1 ii libboost-locale1.67.0 1.67.0-17+b1 ii libc6 2.30-8 ii libfftw3-double3 3.3.8-2 ii libfreetype6 2.10.1-2 ii libgcc-s1 10.1.0-1 ii libgl11.3.1-1 ii libglew2.12.1.0-4+b1 ii libgomp1 10.1.0-1 ii libilmbase24 2.3.0-6 ii libjack-jackd2-0 [libjack-0.125] 1.9.12~dfsg-2+b1 ii libjemalloc2 5.2.1-1 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libopenal11:1.19.1-1+b1 ii libopencolorio1v5 1.1.1~dfsg0-6+b1 ii libopenexr24 2.3.0-6 ii libopenimageio2.1 2.1.13.0~dfsg0-1 ii libopenjp2-7 2.3.1-1 ii libopenvdb7.0 7.0.0-3 ii libosdcpu3.4.33.4.3-2+b1 ii libosdgpu3.4.33.4.3-2+b1 ii libpcre3 2:8.39-12+b1 ii libpng16-16 1.6.37-2 ii libpython3.8 3.8.3~rc1-1 ii libsdl1.2debian 1.2.15+dfsg2-5 ii libsndfile1 1.0.28-7 ii libspnav0 0.2.3-1+b2 ii libstdc++610.1.0-1 ii libswscale5 7:4.2.2-1+b1 ii libtbb2 2020.2-2 ii libtiff5 4.1.0+git191117-2 ii libx11-6 2:1.6.9-2+b1 ii libxfixes31:5.0.3-2 ii libxi62:1.7.9-1 ii libxml2 2.9.10+dfsg-5 ii libxrender1 1:0.9.10-1 ii libxxf86vm1 1:1.1.4-1+b2 ii zlib1g1:1.2.11.dfsg-2 blender recommends no packages. blender suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Hi! On 2020-05-12 at 07:17 (-07), Paul Roge wrote: > Dear Maintainer, > > Blender recently updated, and will not launch. I receive the error: > > OpenColorIO Error: Error: Loading the OCIO profile > '/usr/share/blender/datafiles/colormanagement/config.ocio' failed. The > specified file does not appear to be an OCIO configuration. > Aborted > > I am unable to use blender given this error with OpenColorIO. Recent fix of #959201 solved this issue. Thus, closing. Cheers. -- Matteo F. Vescovi signature.asc Description: PGP signature --- End Message ---
Processed: Bug#952055 marked as pending in paulstretch
Processing control commands:
> tag -1 pending
Bug #952055 [src:paulstretch] paulstretch: FTBFS: XMLwrapper.cpp:32:26: error:
invalid use of incomplete type ‘mxml_node_t’ {aka ‘struct _mxml_node_s’}
Added tag(s) pending.
--
952055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#959632: marked as done (ironic-inspector: FTBFS: AttributeError: module 'construct.core' has no attribute 'Embedded')
Your message dated Wed, 13 May 2020 18:33:55 + with message-id and subject line Bug#959632: fixed in ironic-inspector 10.1.0-1 has caused the Debian Bug report #959632, regarding ironic-inspector: FTBFS: AttributeError: module 'construct.core' has no attribute 'Embedded' 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.) -- 959632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ironic-inspector Version: 8.2.2-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200501 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > make[1]: pyversions: Command not found > py3versions: no X-Python3-Version in control file, using supported versions > for i in 3.8 ; do \ > python$i setup.py install --install-layout=deb --root > /<>/debian/tmp ; \ > done > running install > [pbr] Generating AUTHORS > [pbr] AUTHORS complete (0.0s) > running build > running build_py > creating build > creating build/lib > creating build/lib/ironic_inspector > creating build/lib/ironic_inspector/common > copying ironic_inspector/common/swift.py -> build/lib/ironic_inspector/common > copying ironic_inspector/common/__init__.py -> > build/lib/ironic_inspector/common > copying ironic_inspector/common/i18n.py -> build/lib/ironic_inspector/common > copying ironic_inspector/common/rpc_service.py -> > build/lib/ironic_inspector/common > copying ironic_inspector/common/keystone.py -> > build/lib/ironic_inspector/common > copying ironic_inspector/common/context.py -> > build/lib/ironic_inspector/common > copying ironic_inspector/common/lldp_tlvs.py -> > build/lib/ironic_inspector/common > copying ironic_inspector/common/ironic.py -> build/lib/ironic_inspector/common > copying ironic_inspector/common/rpc.py -> build/lib/ironic_inspector/common > copying ironic_inspector/common/lldp_parsers.py -> > build/lib/ironic_inspector/common > copying ironic_inspector/common/service_utils.py -> > build/lib/ironic_inspector/common > creating build/lib/ironic_inspector/conf > copying ironic_inspector/conf/default.py -> build/lib/ironic_inspector/conf > copying ironic_inspector/conf/dnsmasq_pxe_filter.py -> > build/lib/ironic_inspector/conf > copying ironic_inspector/conf/swift.py -> build/lib/ironic_inspector/conf > copying ironic_inspector/conf/__init__.py -> build/lib/ironic_inspector/conf > copying ironic_inspector/conf/pxe_filter.py -> build/lib/ironic_inspector/conf > copying ironic_inspector/conf/discovery.py -> build/lib/ironic_inspector/conf > copying ironic_inspector/conf/processing.py -> build/lib/ironic_inspector/conf > copying ironic_inspector/conf/capabilities.py -> > build/lib/ironic_inspector/conf > copying ironic_inspector/conf/opts.py -> build/lib/ironic_inspector/conf > copying ironic_inspector/conf/iptables.py -> build/lib/ironic_inspector/conf > copying ironic_inspector/conf/ironic.py -> build/lib/ironic_inspector/conf > copying ironic_inspector/conf/pci_devices.py -> > build/lib/ironic_inspector/conf > copying ironic_inspector/rules.py -> build/lib/ironic_inspector > copying ironic_inspector/process.py -> build/lib/ironic_inspector > copying ironic_inspector/__init__.py -> build/lib/ironic_inspector > copying ironic_inspector/node_cache.py -> build/lib/ironic_inspector > copying ironic_inspector/api_tools.py -> build/lib/ironic_inspector > copying ironic_inspector/db.py -> build/lib/ironic_inspector > copying ironic_inspector/introspect.py -> build/lib/ironic_inspector > copying ironic_inspector/wsgi_service.py -> build/lib/ironic_inspector > copying ironic_inspector/policy.py -> build/lib/ironic_inspector > copying ironic_inspector/version.py -> build/lib/ironic_inspector > copying ironic_inspector/introspection_state.py -> build/lib/ironic_inspector > copying ironic_inspector/main.py -> build/lib/ironic_inspector > copying ironic_inspector/dbsync.py -> build/lib/ironic_inspector > copying ironic_inspector/utils.py -> build/lib/ironic_inspector > creating build/lib/ironic_inspector/pxe_filter > copying ironic_inspector/pxe_filter/interface.py -> > build/lib/ironic_inspector/pxe_filter > copying ironic_inspector/pxe_filter/dnsmasq.py -> > build/lib/ironic_inspector/pxe_filter > copying ironic_inspector/pxe_filter/__init__.py -> > build/lib/ironic_inspector/pxe_filter > copying ironic_inspector/pxe_filter/iptables.py -> > build/lib/ironic_inspector/pxe_filter > copying
Processed: Bug#959632 marked as pending in ironic-inspector
Processing control commands: > tag -1 pending Bug #959632 [src:ironic-inspector] ironic-inspector: FTBFS: AttributeError: module 'construct.core' has no attribute 'Embedded' Added tag(s) pending. -- 959632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959632: marked as pending in ironic-inspector
Control: tag -1 pending Hello, Bug #959632 in ironic-inspector reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/ironic-inspector/-/commit/b6104b7af768f6b33eee8c388c75c8a515720dac * Add Use_latest_version_of_python_construct.patch (Closes: #959632), fixing FTBFS with latest construct. (this message was generated automatically) -- Greetings https://bugs.debian.org/959632
Bug#959586: marked as done (openimageio: FTBFS: ld: /usr/lib/libOpenColorIO.so.1: undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]')
Your message dated Wed, 13 May 2020 17:34:59 + with message-id and subject line Bug#959201: fixed in yaml-cpp 0.6.3-7 has caused the Debian Bug report #959201, regarding openimageio: FTBFS: ld: /usr/lib/libOpenColorIO.so.1: undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]' 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.) -- 959201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openimageio Version: 2.1.13.0~dfsg0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200501 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/c++ -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now > CMakeFiles/filter_test.dir/filter_test.cpp.o -o ../../bin/filter_test > -Wl,-rpath,"/<>/build/lib" ../../lib/libOpenImageIO.so.2.1.13 > /usr/lib/x86_64-linux-gnu/libImath.so /usr/lib/x86_64-linux-gnu/libIex.so > /usr/lib/x86_64-linux-gnu/libHalf.so > /usr/lib/x86_64-linux-gnu/libIlmThread.so -lpthread > /usr/lib/x86_64-linux-gnu/libIlmImf.so /usr/lib/x86_64-linux-gnu/libImath.so > /usr/lib/x86_64-linux-gnu/libIex.so /usr/lib/x86_64-linux-gnu/libHalf.so > /usr/lib/x86_64-linux-gnu/libIlmThread.so -lpthread > /usr/lib/x86_64-linux-gnu/libIlmImf.so /usr/lib/x86_64-linux-gnu/libz.so > /usr/lib/x86_64-linux-gnu/libopencv_core.so > /usr/lib/x86_64-linux-gnu/libopencv_imgproc.so > /usr/lib/x86_64-linux-gnu/libopencv_videoio.so > /usr/bin/ld: /usr/lib/libOpenColorIO.so.1: undefined reference to > `YAML::detail::node_data::empty_scalar[abi:cxx11]' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/05/01/openimageio_2.1.13.0~dfsg0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: yaml-cpp Source-Version: 0.6.3-7 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of yaml-cpp, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated yaml-cpp 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, 13 May 2020 19:26:42 +0200 Source: yaml-cpp Binary: libyaml-cpp0.6 libyaml-cpp-dev Architecture: source Version: 0.6.3-7 Distribution: unstable Urgency: medium Maintainer: Simon Quigley Changed-By: Gianfranco Costamagna Description: libyaml-cpp-dev - YAML parser and emitter for C++ - development files libyaml-cpp0.6 - YAML parser and emitter for C++ Closes: 959201 Changes: yaml-cpp (0.6.3-7) unstable; urgency=medium . * Team upload [ Adrian Bunk ] * From Adrian Bunk, fix other c++ symbols that broke ABI (Closes: #959201) Checksums-Sha1: 02e654c62965e38d18e4242f9e33178fd52bb4f9 1973 yaml-cpp_0.6.3-7.dsc 971ae408c790f8d350b44fc144a4ea4811cd47ab 24896 yaml-cpp_0.6.3-7.debian.tar.xz 20e87bfa06b6c07e334eb1b72fc5b98d53a0db15 8662 yaml-cpp_0.6.3-7_source.buildinfo Checksums-Sha256: a0c7763b1908bb7822e288e15c3faf2f24bd766f2a199aa5f1a99381bf6e6967 1973 yaml-cpp_0.6.3-7.dsc b67b8b5ad8b86dd8caa8c5104760a92662fefe7d71f5e773f038d860d0adfaf0 24896 yaml-cpp_0.6.3-7.debian.tar.xz f3b2c91471f9cc58ac6799ea5b33e3e63eb6014c1f95f8a42d5f9506afc14798 8662 yaml-cpp_0.6.3-7_source.buildinfo Files: 76eb4e0b10c4ee87716f3a8897aef169 1973 devel optional yaml-cpp_0.6.3-7.dsc c7833d15c348f38222c02a040fb99c78 24896 devel optional yaml-cpp_0.6.3-7.debian.tar.xz 26ba6069156ae830d0efadd6cf84da51 8662 devel optional
Bug#959657: marked as done (olive-editor: Does not start: symbol lookup error)
Your message dated Wed, 13 May 2020 17:34:59 + with message-id and subject line Bug#959201: fixed in yaml-cpp 0.6.3-7 has caused the Debian Bug report #959201, regarding olive-editor: Does not start: symbol lookup error 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.) -- 959201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: olive-editor Version: 20200210-1 Severity: grave Justification: renders package unusable olive-editor: symbol lookup error: /lib/libOpenColorIO.so.1: undefined symbol: _ZN4YAML6detail9node_data12empty_scalarB5cxx11E Clearly the dependencies are not tight enough, and the package needs to be rebuilt for the current library versions. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.utf-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.utf-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages olive-editor depends on: ii ffmpeg 7:4.2.2-1+b1 ii frei0r-plugins 1.7.0-1 ii libavcodec58 7:4.2.2-1+b1 ii libavfilter7 7:4.2.2-1+b1 ii libavformat58 7:4.2.2-1+b1 ii libavutil56 7:4.2.2-1+b1 ii libc6 2.30-4 ii libgcc-s1 10-20200418-1 ii libopencolorio1v5 1.1.1~dfsg0-6+b1 ii libopenimageio2.1 2.1.13.0~dfsg0-1 ii libqt5core5a 5.12.5+dfsg-10 ii libqt5gui5 5.12.5+dfsg-10 ii libqt5multimedia5 5.12.5-1+b1 ii libqt5multimedia5-plugins 5.12.5-1+b1 ii libqt5widgets5 5.12.5+dfsg-10 ii libstdc++6 10-20200418-1 ii libswresample3 7:4.2.2-1+b1 ii libswscale5 7:4.2.2-1+b1 olive-editor recommends no packages. olive-editor suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: yaml-cpp Source-Version: 0.6.3-7 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of yaml-cpp, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated yaml-cpp 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, 13 May 2020 19:26:42 +0200 Source: yaml-cpp Binary: libyaml-cpp0.6 libyaml-cpp-dev Architecture: source Version: 0.6.3-7 Distribution: unstable Urgency: medium Maintainer: Simon Quigley Changed-By: Gianfranco Costamagna Description: libyaml-cpp-dev - YAML parser and emitter for C++ - development files libyaml-cpp0.6 - YAML parser and emitter for C++ Closes: 959201 Changes: yaml-cpp (0.6.3-7) unstable; urgency=medium . * Team upload [ Adrian Bunk ] * From Adrian Bunk, fix other c++ symbols that broke ABI (Closes: #959201) Checksums-Sha1: 02e654c62965e38d18e4242f9e33178fd52bb4f9 1973 yaml-cpp_0.6.3-7.dsc 971ae408c790f8d350b44fc144a4ea4811cd47ab 24896 yaml-cpp_0.6.3-7.debian.tar.xz 20e87bfa06b6c07e334eb1b72fc5b98d53a0db15 8662 yaml-cpp_0.6.3-7_source.buildinfo Checksums-Sha256: a0c7763b1908bb7822e288e15c3faf2f24bd766f2a199aa5f1a99381bf6e6967 1973 yaml-cpp_0.6.3-7.dsc b67b8b5ad8b86dd8caa8c5104760a92662fefe7d71f5e773f038d860d0adfaf0 24896 yaml-cpp_0.6.3-7.debian.tar.xz f3b2c91471f9cc58ac6799ea5b33e3e63eb6014c1f95f8a42d5f9506afc14798 8662 yaml-cpp_0.6.3-7_source.buildinfo Files: 76eb4e0b10c4ee87716f3a8897aef169 1973 devel optional yaml-cpp_0.6.3-7.dsc c7833d15c348f38222c02a040fb99c78 24896 devel optional yaml-cpp_0.6.3-7.debian.tar.xz 26ba6069156ae830d0efadd6cf84da51 8662 devel optional yaml-cpp_0.6.3-7_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl68LkAACgkQ808JdE6f
Bug#959596: marked as done (blender: FTBFS: subprocess.CalledProcessError: Command '['/<>/obj-x86_64-linux-gnu/bin/blender', '--help']' returned non-zero exit status 127.)
Your message dated Wed, 13 May 2020 17:34:59 + with message-id and subject line Bug#959201: fixed in yaml-cpp 0.6.3-7 has caused the Debian Bug report #959201, regarding blender: FTBFS: subprocess.CalledProcessError: Command '['/<>/obj-x86_64-linux-gnu/bin/blender', '--help']' returned non-zero exit status 127. 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.) -- 959201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: blender Version: 2.82.a+dfsg-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200501 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > cd /<>/obj-x86_64-linux-gnu/source/creator && > ../../../doc/manpage/blender.1.py > /<>/obj-x86_64-linux-gnu/bin/blender > /<>/obj-x86_64-linux-gnu/source/creator/blender.1 > /<>/obj-x86_64-linux-gnu/bin/blender: symbol lookup error: > /usr/lib/libOpenColorIO.so.1: undefined symbol: > _ZN4YAML6detail9node_data12empty_scalarB5cxx11E > executing: /<>/obj-x86_64-linux-gnu/bin/blender --help > Traceback (most recent call last): > File "../../../doc/manpage/blender.1.py", line 55, in > blender_help = subprocess.run( > File "/usr/lib/python3.8/subprocess.py", line 512, in run > raise CalledProcessError(retcode, process.args, > subprocess.CalledProcessError: Command > '['/<>/obj-x86_64-linux-gnu/bin/blender', '--help']' returned > non-zero exit status 127. > make[3]: *** [source/creator/CMakeFiles/blender_man_page.dir/build.make:60: > source/creator/CMakeFiles/blender_man_page] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/05/01/blender_2.82.a+dfsg-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: yaml-cpp Source-Version: 0.6.3-7 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of yaml-cpp, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated yaml-cpp 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, 13 May 2020 19:26:42 +0200 Source: yaml-cpp Binary: libyaml-cpp0.6 libyaml-cpp-dev Architecture: source Version: 0.6.3-7 Distribution: unstable Urgency: medium Maintainer: Simon Quigley Changed-By: Gianfranco Costamagna Description: libyaml-cpp-dev - YAML parser and emitter for C++ - development files libyaml-cpp0.6 - YAML parser and emitter for C++ Closes: 959201 Changes: yaml-cpp (0.6.3-7) unstable; urgency=medium . * Team upload [ Adrian Bunk ] * From Adrian Bunk, fix other c++ symbols that broke ABI (Closes: #959201) Checksums-Sha1: 02e654c62965e38d18e4242f9e33178fd52bb4f9 1973 yaml-cpp_0.6.3-7.dsc 971ae408c790f8d350b44fc144a4ea4811cd47ab 24896 yaml-cpp_0.6.3-7.debian.tar.xz 20e87bfa06b6c07e334eb1b72fc5b98d53a0db15 8662 yaml-cpp_0.6.3-7_source.buildinfo Checksums-Sha256: a0c7763b1908bb7822e288e15c3faf2f24bd766f2a199aa5f1a99381bf6e6967 1973 yaml-cpp_0.6.3-7.dsc b67b8b5ad8b86dd8caa8c5104760a92662fefe7d71f5e773f038d860d0adfaf0 24896 yaml-cpp_0.6.3-7.debian.tar.xz f3b2c91471f9cc58ac6799ea5b33e3e63eb6014c1f95f8a42d5f9506afc14798 8662 yaml-cpp_0.6.3-7_source.buildinfo Files: 76eb4e0b10c4ee87716f3a8897aef169 1973 devel optional yaml-cpp_0.6.3-7.dsc c7833d15c348f38222c02a040fb99c78 24896 devel optional yaml-cpp_0.6.3-7.debian.tar.xz 26ba6069156ae830d0efadd6cf84da51 8662 devel optional yaml-cpp_0.6.3-7_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl68LkAACgkQ808JdE6f
Bug#959201: marked as done (jami-daemon: dring does not start due to a symbol lookup error)
Your message dated Wed, 13 May 2020 17:34:59 + with message-id and subject line Bug#959201: fixed in yaml-cpp 0.6.3-7 has caused the Debian Bug report #959201, regarding jami-daemon: dring does not start due to a symbol lookup error 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.) -- 959201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jami-daemon Version: 20190215.1.f152c98~ds1-1+b1 Severity: grave Justification: renders package unusable Hi, Jami fails to connect to its daemon dring because it cannot start due to a symbol lookup error: /usr/lib/ring/dring: symbol lookup error: /usr/lib/ring/dring: undefined symbol: _ZN4YAML6detail9node_data12empty_scalarB5cxx11E Cheers, Bruno -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.utf-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.utf-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages jami-daemon depends on: ii libargon2-10~20171227-0.2 ii libasound2 1.2.2-2.1 ii libavcodec58 7:4.2.2-1+b1 ii libavdevice58 7:4.2.2-1+b1 ii libavfilter7 7:4.2.2-1+b1 ii libavformat58 7:4.2.2-1+b1 ii libavutil567:4.2.2-1+b1 ii libc6 2.30-4 ii libdbus-c++-1-0v5 0.9.0-8.1 ii libgcc-s1 [libgcc1]10-20200418-1 ii libgcc11:10-20200418-1 ii libgnutls303.6.13-2 ii libixml10 1:1.8.4-2 ii libjsoncpp11.7.4-3.1 ii libnatpmp1 20150609-7+b2 ii libnettle7 3.5.1+really3.5.1-2 ii libpcre3 2:8.39-12+b1 ii libpulse0 13.0-5 ii librestbed0 [librestbed0] 4.0~dfsg1-5 ii libsecp256k1-0 0.1~20170810-2 ii libstdc++6 10-20200418-1 ii libswresample3 7:4.2.2-1+b1 ii libswscale57:4.2.2-1+b1 ii libudev1 245.5-2 ii libupnp13 1:1.8.4-2 ii libuuid1 2.34-0.1 ii libyaml-cpp0.6 0.6.3-1 ii zlib1g 1:1.2.11.dfsg-2 jami-daemon recommends no packages. jami-daemon suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: yaml-cpp Source-Version: 0.6.3-7 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of yaml-cpp, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated yaml-cpp 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, 13 May 2020 19:26:42 +0200 Source: yaml-cpp Binary: libyaml-cpp0.6 libyaml-cpp-dev Architecture: source Version: 0.6.3-7 Distribution: unstable Urgency: medium Maintainer: Simon Quigley Changed-By: Gianfranco Costamagna Description: libyaml-cpp-dev - YAML parser and emitter for C++ - development files libyaml-cpp0.6 - YAML parser and emitter for C++ Closes: 959201 Changes: yaml-cpp (0.6.3-7) unstable; urgency=medium . * Team upload [ Adrian Bunk ] * From Adrian Bunk, fix other c++ symbols that broke ABI (Closes: #959201) Checksums-Sha1: 02e654c62965e38d18e4242f9e33178fd52bb4f9 1973 yaml-cpp_0.6.3-7.dsc 971ae408c790f8d350b44fc144a4ea4811cd47ab 24896 yaml-cpp_0.6.3-7.debian.tar.xz 20e87bfa06b6c07e334eb1b72fc5b98d53a0db15 8662 yaml-cpp_0.6.3-7_source.buildinfo Checksums-Sha256: a0c7763b1908bb7822e288e15c3faf2f24bd766f2a199aa5f1a99381bf6e6967 1973 yaml-cpp_0.6.3-7.dsc b67b8b5ad8b86dd8caa8c5104760a92662fefe7d71f5e773f038d860d0adfaf0 24896 yaml-cpp_0.6.3-7.debian.tar.xz
Bug#959556: marked as done (olive-editor: FTBFS: ld: /usr/lib/libOpenColorIO.so: undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]')
Your message dated Wed, 13 May 2020 17:34:59 + with message-id and subject line Bug#959201: fixed in yaml-cpp 0.6.3-7 has caused the Debian Bug report #959201, regarding olive-editor: FTBFS: ld: /usr/lib/libOpenColorIO.so: undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]' 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.) -- 959201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: olive-editor Version: 20200210-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200501 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/c++ -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -Wl,--as-needed > CMakeFiles/olive-editor.dir/olive-editor_autogen/mocs_compilation.cpp.o > CMakeFiles/olive-editor.dir/core.cpp.o CMakeFiles/olive-editor.dir/main.cpp.o > CMakeFiles/olive-editor.dir/audio/audiomanager.cpp.o > CMakeFiles/olive-editor.dir/audio/bufferaverage.cpp.o > CMakeFiles/olive-editor.dir/audio/outputdeviceproxy.cpp.o > CMakeFiles/olive-editor.dir/audio/outputmanager.cpp.o > CMakeFiles/olive-editor.dir/audio/sampleformat.cpp.o > CMakeFiles/olive-editor.dir/audio/tempoprocessor.cpp.o > CMakeFiles/olive-editor.dir/codec/ffmpeg/ffmpegcommon.cpp.o > CMakeFiles/olive-editor.dir/codec/ffmpeg/ffmpegdecoder.cpp.o > CMakeFiles/olive-editor.dir/codec/ffmpeg/ffmpegencoder.cpp.o > CMakeFiles/olive-editor.dir/codec/oiio/oiiodecoder.cpp.o > CMakeFiles/olive-editor.dir/codec/decoder.cpp.o > CMakeFiles/olive-editor.dir/codec/encoder.cpp.o > CMakeFiles/olive-editor.dir/codec/frame.cpp.o > CMakeFiles/olive-editor.dir/codec/waveinput.cpp.o > CMakeFiles/olive-editor.dir/codec/waveoutput.cpp.o > CMakeFiles/olive-editor.dir/common/bezier.cpp.o > CMakeFiles/olive-editor.dir/common/debug.cpp.o > CMakeFiles/olive-editor.dir/common/filefunctions.cpp.o > CMakeFiles/olive-editor.dir/common/flipmodifiers.cpp.o > CMakeFiles/olive-editor.dir/common/qtversionabstraction.cpp.o > CMakeFiles/olive-editor.dir/common/rational.cpp.o > CMakeFiles/olive-editor.dir/common/threadedobject.cpp.o > CMakeFiles/olive-editor.dir/common/timecodefunctions.cpp.o > CMakeFiles/olive-editor.dir/common/timerange.cpp.o > CMakeFiles/olive-editor.dir/config/config.cpp.o > CMakeFiles/olive-editor.dir/dialog/about/about.cpp.o > CMakeFiles/olive-editor.dir/dialog/actionsearch/actionsearch.cpp.o > CMakeFiles/olive-editor.dir/dialog/export/export.cpp.o > CMakeFiles/olive-editor.dir/dialog/export/exportaudiotab.cpp.o > CMakeFiles/olive-editor.dir/dialog/export/exportvideotab.cpp.o > CMakeFiles/olive-editor.dir/dialog/footageproperties/streamproperties/streamproperties.cpp.o > > CMakeFiles/olive-editor.dir/dialog/footageproperties/streamproperties/audiostreamproperties.cpp.o > > CMakeFiles/olive-editor.dir/dialog/footageproperties/streamproperties/videostreamproperties.cpp.o > CMakeFiles/olive-editor.dir/dialog/footageproperties/footageproperties.cpp.o > CMakeFiles/olive-editor.dir/dialog/keyframeproperties/keyframeproperties.cpp.o > CMakeFiles/olive-editor.dir/dialog/loadsave/loadsave.cpp.o > CMakeFiles/olive-editor.dir/dialog/preferences/tabs/preferencesgeneraltab.cpp.o > > CMakeFiles/olive-editor.dir/dialog/preferences/tabs/preferencesbehaviortab.cpp.o > CMakeFiles/olive-editor.dir/dialog/preferences/tabs/preferencesdisktab.cpp.o > CMakeFiles/olive-editor.dir/dialog/preferences/tabs/preferencesappearancetab.cpp.o > > CMakeFiles/olive-editor.dir/dialog/preferences/tabs/preferencesqualitytab.cpp.o > > CMakeFiles/olive-editor.dir/dialog/preferences/tabs/preferencesaudiotab.cpp.o > CMakeFiles/olive-editor.dir/dialog/preferences/tabs/preferenceskeyboardtab.cpp.o > CMakeFiles/olive-editor.dir/dialog/preferences/tabs/preferencestab.cpp.o > CMakeFiles/olive-editor.dir/dialog/preferences/keysequenceeditor.cpp.o > CMakeFiles/olive-editor.dir/dialog/preferences/preferences.cpp.o > CMakeFiles/olive-editor.dir/dialog/projectproperties/projectproperties.cpp.o > CMakeFiles/olive-editor.dir/dialog/rendercancel/rendercancel.cpp.o > CMakeFiles/olive-editor.dir/dialog/sequence/sequence.cpp.o > CMakeFiles/olive-editor.dir/dialog/speedduration/speedduration.cpp.o > CMakeFiles/olive-editor.dir/node/audio/pan/pan.cpp.o > CMakeFiles/olive-editor.dir/node/audio/volume/volume.cpp.o >
Bug#959620: marked as done (mypaint: FTBFS: AssertionError: Failed doctest test for lib.layer.tree.RootLayerStack.walk)
Your message dated Wed, 13 May 2020 16:33:55 +
with message-id
and subject line Bug#959620: fixed in mypaint 2.0.0+git20200502-1
has caused the Debian Bug report #959620,
regarding mypaint: FTBFS: AssertionError: Failed doctest test for
lib.layer.tree.RootLayerStack.walk
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.)
--
959620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mypaint
Version: 2.0.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Known to be failing, just ignore failure for now
> # As suggested by upstream
> python3 setup.py nosetests \
> --ignore-files="(objfactory)|(widgets).py"
> running nosetests
> running egg_info
> creating MyPaint.egg-info
> writing MyPaint.egg-info/PKG-INFO
> writing dependency_links to MyPaint.egg-info/dependency_links.txt
> writing top-level names to MyPaint.egg-info/top_level.txt
> writing manifest file 'MyPaint.egg-info/SOURCES.txt'
> reading manifest file 'MyPaint.egg-info/SOURCES.txt'
> writing manifest file 'MyPaint.egg-info/SOURCES.txt'
> copying
> build/lib.linux-x86_64-3.8/lib/_mypaintlib.cpython-38-x86_64-linux-gnu.so ->
> lib
> Unable to init server: Could not connect: Connection refused
> Unable to init server: Could not connect: Connection refused
> /<>/gui/accelmap.py:17: PyGIWarning: Gtk was imported without
> specifying a version first. Use gi.require_version('Gtk', '3.0') before
> import to ensure that the right version gets loaded.
> from gi.repository import Gtk
> Doctest: gui.brushmanager.BrushManager.__init__ ...
> /usr/lib/python3.8/doctest.py:1336: RuntimeWarning: coroutine '' was
> never awaited
> exec(compile(example.source, filename, "single",
> RuntimeWarning: Enable tracemalloc to get the object allocation traceback
> FAIL
> Doctest: gui.brushmanager.BrushManager.export_group ... ok
> Doctest: gui.brushmanager.BrushManager.get_brush_by_name ... ok
> Doctest: gui.brushmanager.BrushManager.import_brushpack ... FAIL
> Doctest: gui.brushmanager.BrushManager.save_brushorder ... ok
> Doctest: gui.brushmanager.ManagedBrush.__init__ ... ok
> Doctest: gui.brushmanager.ManagedBrush.description ... ok
> Doctest: gui.brushmanager.ManagedBrush.get_preview ... FAIL
> Doctest: gui.brushmanager.ManagedBrush.notes ... ok
> Doctest: gui.brushmanager.ManagedBrush.preview ... FAIL
> Doctest: gui.brushmanager._device_name_uuid ... ok
> Doctest: gui.brushmanager._quote_device_name ... ok
> Doctest: gui.filehandling._get_case_insensitive_glob ... ok
> Doctest: gui.freehand.PressureAndTiltInterpolator ... FAIL
> Doctest: gui.meta.get_libs_version_string ... ok
> Doctest: gui.mvp.Presenter ... ok
> Doctest: gui.uicolor.from_gdk_color ... ok
> Doctest: gui.uicolor.from_gdk_rgba ... ok
> Doctest: gui.uicolor.to_gdk_color ... ok
> Doctest: gui.uicolor.to_gdk_rgba ... ok
> Doctest: lib.alg.convex_hull ... ok
> Doctest: lib.alg.intersection_of_segments ... ok
> Doctest: lib.alg.nearest_point_in_segment ... ok
> Doctest: lib.alg.pairwise ... ok
> Doctest: lib.alg.point_in_convex_poly ... ok
> Doctest: lib.alg.poly_area ... ok
> Doctest: lib.alg.poly_centroid ... ok
> Doctest: lib.brush.BrushInfo._load_old_format ... ok
> Doctest: lib.brush.BrushInfo.from_json ... ok
> Doctest: lib.brush.brushinfo_quote ... ok
> Doctest: lib.brush.brushinfo_unquote ... ok
> Doctest: lib.brushsettings.BrushInputInfo ... ok
> Doctest: lib.brushsettings.BrushSettingInfo ... ok
> Doctest: lib.color.HCYColor.__eq__ ... ok
> Doctest: lib.color.HCYColor.__init__ ... ok
> Doctest: lib.color.HCYColor.interpolate ... FAIL
> Doctest: lib.color.HCY_to_RGB ... FAIL
> Doctest: lib.color.HSVColor ... ok
> Doctest: lib.color.HSVColor.__eq__ ... ok
> Doctest: lib.color.HSVColor.__init__ ... ok
> Doctest: lib.color.HSVColor.interpolate ... FAIL
> Doctest: lib.color.RGBColor.__eq__ ... ok
> Doctest: lib.color.RGBColor.__init__ ... ok
> Doctest: lib.color.RGBColor.interpolate ... FAIL
> Doctest: lib.color.UIColor ... ok
> Doctest: lib.color.UIColor.get_luma ... ok
> Doctest: lib.color.UIColor.new_from_pixbuf_average ... ok
> Doctest: lib.color.UIColor.to_contrasting ... ok
> Doctest: lib.color.UIColor.to_fill_pixel ... ok
> Doctest: lib.color.UIColor.to_greyscale ... ok
> Doctest: lib.color.YCbCrColor.__eq__ ... ok
> Doctest: lib.color.YCbCrColor.interpolate ... FAIL
> Doctest:
Bug#955695: probably because of libsmali-java update from 2.3.3 to 2.4
My guess is that this issue was caused by the libsmali-java update from 2.3.3 to 2.4. Hopefuilly its a small fix.
Processed: closing 951925
Processing commands for cont...@bugs.debian.org: > close 951925 Bug #951925 [src:flare-engine] flare-engine FTBFS: Could NOT find SDL2 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 951925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951925 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958318: marked as done (src:python-setuptools: Incomplete debian/copyright)
Your message dated Wed, 13 May 2020 13:50:51 + with message-id and subject line Bug#958318: fixed in python-setuptools 44.0.0-3 has caused the Debian Bug report #958318, regarding src:python-setuptools: Incomplete debian/copyright 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.) -- 958318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-setuptools Version: 40.8.0-1 Severity: serious Justification: Policy 2.3 While reviewing src:setuptools in New, I noticed a number of omissions from debian/copyright which apply to this package as well. Copyright and license information from the following files is missing. Under current Debian Policy (4.5.0) these are all required. An upcoming policy change will relax the requirement so that license text and copyright attributions that are shipped in text form in the package are not required to be in debian/copyright. Once that change is part of policy, then only the changes relative to LICENSE and pkg_resources/_vendor/ appdirs.py will be required (the license text is missing from appdirs.py). Scott K LICENSE: Copyright (C) 2016 Jason R Coombs Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. pkg_resources/_vendor/pyparsing.py: setuptools/_vendor/pyparsing.py: # Copyright (c) 2003-2018 Paul T. McGuire pkg_resources/_vendor/six.py: setuptools/_vendor/six.py: # Copyright (c) 2010-2015 Benjamin Peterson # Copyright (c) 2010-2015 Benjamin Peterson # # Permission is hereby granted, free of charge, to any person obtaining a copy # of this software and associated documentation files (the "Software"), to deal # in the Software without restriction, including without limitation the rights # to use, copy, modify, merge, publish, distribute, sublicense, and/or sell # copies of the Software, and to permit persons to whom the Software is # furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in all # copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE # AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER # LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, # OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. pkg_resources/_vendor/appdirs.py: # Copyright (c) 2005-2010 ActiveState Software Inc. # Copyright (c) 2013 Eddy Petrișor According to the link in the file, the license is: # This is the MIT license Copyright (c) 2010 ActiveState Software Inc. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
Bug#956674: marked as done (prooftree must build depend on coq)
Your message dated Wed, 13 May 2020 13:50:46 + with message-id and subject line Bug#956674: fixed in prooftree 0.13-2 has caused the Debian Bug report #956674, regarding prooftree must build depend on coq 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.) -- 956674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: prooftree Version: 0.13-1 Severity: serious Tags: bullseye sid prooftree must build depend on coq, to prevent building on architectures where it would not be installable. --- End Message --- --- Begin Message --- Source: prooftree Source-Version: 0.13-2 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of prooftree, 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 956...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated prooftree 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, 13 May 2020 15:30:43 +0200 Source: prooftree Binary: prooftree Architecture: source Version: 0.13-2 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Gianfranco Costamagna Description: prooftree - proof-tree visualization for Proof General Closes: 956674 Changes: prooftree (0.13-2) unstable; urgency=medium . [ Stephane Glondu ] * Update Vcs-* . [ Gianfranco Costamagna ] * Team upload * Build-depend on coq to avoid it being uninstallable where coq is not built (Closes: #956674) Checksums-Sha1: ad130d5fd7b90c035f5135fbf17408127fd6f30c 1976 prooftree_0.13-2.dsc 008ba591d7425e40a17b2c93be1dee9d46bfe528 2464 prooftree_0.13-2.debian.tar.xz 757808adef1833e171b905dd019fbacc721f98bf 14260 prooftree_0.13-2_source.buildinfo Checksums-Sha256: 2f666cb9fc165b5365425fdbc4a4e8f5751681df9360305e38acde7d0610390d 1976 prooftree_0.13-2.dsc fa84356b16d6388816e42d6c7b3f909739cbbea23eb360f12ba9c5cdf5c35d1c 2464 prooftree_0.13-2.debian.tar.xz 9f5aa539cd778a9bf136fa530382c32426801114e7dd1c404537d9c007a41dc1 14260 prooftree_0.13-2_source.buildinfo Files: d95c1cf644c9cc7c16f8fa08d7e40584 1976 science optional prooftree_0.13-2.dsc 180dd0d00a17cd94eb640365893c9ac9 2464 science optional prooftree_0.13-2.debian.tar.xz 34a12bc69dedd4a57cd3afd57869ee66 14260 science optional prooftree_0.13-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl679sAACgkQ808JdE6f XdmTshAAvvb64K9+UyuS0aAuyQmsBzpoVPcPMnbBUgbfk6VFkofz52YQ/0S7Z0Zp Uwxe3Y3q05m9NNMImdFqwylNa565tK7kFF0Za1q+gwgkR+akUKLiVWhLiECHRQSd nbeluIGY+DC8UBzIziQm/cJ7Svm+441XxvIvwLbG3a0FsJUtYJ7JURm6amSAeQEV 6ob0aZLrg/ndXTyrw6ZnNED5dIvrsWcCQs2QexH8L0MTjP1NaLVybrg/eWKi8gWl EmBzjustfzeMcnc9ogwszH5IS3nbD/MOQXORqoBXA5YTr5tVr/2lKcgqHRkN8+7S heGOemeXN85IVnnHwBAwDCiDdJf8V/Q7olMS+QqcApkOfM6zKt/VAE7XdcpV0FL7 +4SGSp2gjWVudUzY96ZY2kOgV2rjTxiloN6zv1k1wNIg5EQFGFpyLgOzLx6j1gEi pBb4/3Mmjj0+CQ6NfaTixjTe4mZ4W5rnvYx7TyNpYwPQGMoY/xgySO0kzGahhtDV x5ocC9qwsYInhIQd/GdPuFcZTIEhRZFvqYKY36mwEJiTV9S2gQIVMNxVZLNaujs2 LjEhanskdAW4TWuDncDtOsKhX0SWLWjUpKQivkzowt9l7Stv/GpRfnyLn5QPPUUb zcbOXwN9G8zzSutCkamkBQPRjfVsPp+8tSV49S5B6uHOM+HLiF8= =mKZJ -END PGP SIGNATURE End Message ---
Bug#955096: marked as done (vitables: FTBFS with Sphinx 2.4: Sphinx error: Builder name qthelp not registered or available through entry point)
Your message dated Wed, 13 May 2020 13:34:59 + with message-id and subject line Bug#955096: fixed in vitables 3.0.0-1.1 has caused the Debian Bug report #955096, regarding vitables: FTBFS with Sphinx 2.4: Sphinx error: Builder name qthelp not registered or available through entry point 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.) -- 955096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vitables Version: 3.0.0-1 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx2.4 Hi, vitables fails to build with Sphinx 2.4, currently available in experimental. Relevant part (hopefully): > make[2]: Entering directory '/<>/doc' > sphinx-build -b qthelp -d _build/doctrees . _build/qthelp > Running Sphinx v2.4.3 > > Sphinx error: > Builder name qthelp not registered or available through entry point > make[2]: *** [Makefile:86: qthelp] Error 2 The full build log is available from: http://qa-logs.debian.net/2020/03/26/vitables_3.0.0-1_unstable_sphinx243.log Please see [1] for Sphinx changelog, which may give a hint of what changes in Sphinx caused this error. Also see [2] for the list of deprecated/removed APIs and possible alternatives to them. Sphinx 2.4 is going to be uploaded to unstable in a couple of weeks. When that happens, the severity of this bug will be bumped to serious. In case you have questions, please Cc sph...@packages.debian.org on reply. [1]: https://www.sphinx-doc.org/en/2.0/changes.html [2]: https://www.sphinx-doc.org/en/2.0/extdev/deprecated.html#dev-deprecated-apis A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: vitables Source-Version: 3.0.0-1.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of vitables, 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 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated vitables 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 Apr 2020 15:33:51 +0300 Source: vitables Architecture: source Version: 3.0.0-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Adrian Bunk Closes: 955096 Changes: vitables (3.0.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Build depend on python3-sphinxcontrib.qthelp. (Closes: #955096) Checksums-Sha1: caba95647dd1c7fba61e37dcffc5fac3ea23e064 2138 vitables_3.0.0-1.1.dsc e71105daacd618b19fcc190a667e73c8d1025624 4408 vitables_3.0.0-1.1.debian.tar.xz Checksums-Sha256: 842a2b571cc6950258e48112db11fb7ea2654513c983da323bc93c0453de44c3 2138 vitables_3.0.0-1.1.dsc f9532f52339f706a5d2cb5834f0c9d2d1c71ba297fef3ee4792284c7fe290548 4408 vitables_3.0.0-1.1.debian.tar.xz Files: 1ffb5cec7109fe80754599430a072429 2138 science optional vitables_3.0.0-1.1.dsc 69cd42bb57ebab4b795b735ad7155880 4408 science optional vitables_3.0.0-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl6pdNIACgkQiNJCh6LY mLGi8g/+Lo6EFvMBKncstPhfVOlSiAaGjeRo6mnfRF/BWJ08aHyO5pQNccyp+8sh PFxrZ/MSIQOiOknrTzjy3oDqf+6w04AjsGVQB+PT3tQUqFz1YYP+XvabGHJernyw UmAzVghJdQtP4Zrv2c5Y2v7mnrEtTnC5QG5Pfkz9AtTvq4Jm4g1S6JXW2hsU+2b7 Nab9QnwOFA+OMUDSMRYiLKr6RXEUJjhBlM7l4YbFiC2VFnfnIXvIVApf/nNonspq 2w3EYvNdRjW2CrFd4MI+2qslcNqRbDboc5E5uxnN4jl+psFdGGOUvyhx8v2iRmnj u6ul1x0xlRMzQ7JmpbCCoY5iBC+5jnLmna9bxDCfBSpNxzB8XAkSbsqHRn1jiFtX PE3CUqSD8Et3xAVBpyb0mjX5IF7dwJMjcJ9ktyUnOuf7uctc15JLmdjna8th+wXp zPC4gWwflJ/qkhtU3H+qTqThqVySewG8D1TbIIF3lsxSWpxHS6J2Bpc114kmguf9 8OpFWCXcQKwUkBLWkIa4M3LojLDjrBK+bQApOrCWGvAed9zJEe72iRAI7jkFu+n3 DK4ji7a6JY7gncIrz1ejyR0tGuXvGHP4CAFrzKHMR3nF6poRUHrnD8frm6fmjT/+
Bug#956674: marked as pending in prooftree
Control: tag -1 pending Hello, Bug #956674 in prooftree reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ocaml-team/prooftree/-/commit/dc36cd1bb3f96f2f00b1c150de13f8b5a9b464f4 Build-depend on coq to avoid it being uninstallable where coq is not built (Closes: #956674) (this message was generated automatically) -- Greetings https://bugs.debian.org/956674
Processed: Bug#956674 marked as pending in prooftree
Processing control commands: > tag -1 pending Bug #956674 [src:prooftree] prooftree must build depend on coq Added tag(s) pending. -- 956674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: lower severity of bug reports with a py2keep tag
Processing commands for cont...@bugs.debian.org: > severity 936251 important Bug #936251 [src:bup] bup: Python2 removal in sid/bullseye Severity set to 'important' from 'serious' > severity 938858 important Bug #938858 [src:xxdiff] xxdiff: Python2 removal in sid/bullseye Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 936251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936251 938858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960340: marked as done (isospec: FTBFS on ppc64el)
Your message dated Wed, 13 May 2020 13:19:33 + with message-id and subject line Bug#960340: fixed in isospec 2.0.2+dfsg1-2 has caused the Debian Bug report #960340, regarding isospec: FTBFS on ppc64el 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.) -- 960340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: isospec Version: 2.0.2+dfsg1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) isospec failed to build on ppc64el: https://buildd.debian.org/status/fetch.php?pkg=isospec=ppc64el=2.0.2%2Bdfsg1-1=1589192318=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: isospec Source-Version: 2.0.2+dfsg1-2 Done: Filippo Rusconi We believe that the bug you reported is fixed in the latest version of isospec, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Filippo Rusconi (supplier of updated isospec 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, 13 May 2020 14:40:03 +0200 Source: isospec Binary: libisospec++-dev libisospec++-doc libisospec++2 libisospec++2-dbgsym python3-isospec python3-isospec-dbgsym r-cran-isospec r-cran-isospec-dbgsym Architecture: source amd64 all Version: 2.0.2+dfsg1-2 Distribution: unstable Urgency: low Maintainer: The Debichem Group Changed-By: Filippo Rusconi Description: libisospec++-dev - Isotopic fine structure calculator (C++ development files) libisospec++-doc - Isotopic fine structure calculator (C++ API documentation) libisospec++2 - Isotopic fine structure calculator (C++ runtime) python3-isospec - Isotopic fine structure calculator for Python 3 r-cran-isospec - Isotopic fine structure calculator for GNU R Closes: 960340 Changes: isospec (2.0.2+dfsg1-2) unstable; urgency=low . * Reinstate the -mtune -march build flags path for the build of the C++ extension of the Python module. (Closes: #960340). Thanks to Sebastian Ramacher for the bug report. Checksums-Sha1: 7cef47a3ef2dc2fb952e5ac2a3349df44a81d102 2520 isospec_2.0.2+dfsg1-2.dsc 3af279c2ea4b63f8f0465b309f6b98919254db60 32492 isospec_2.0.2+dfsg1-2.debian.tar.xz a9a5a40354ccf8d0107be8213931379c112cbcb2 14000 isospec_2.0.2+dfsg1-2_amd64.buildinfo daddada9c82da2815a98e91f0afb972b96056160 41296 libisospec++-dev_2.0.2+dfsg1-2_amd64.deb 28bdfc5582831878110600ae3e7d5b978896e5f2 646280 libisospec++-doc_2.0.2+dfsg1-2_all.deb cfda0b0d26deec9c923ea452fb72c31c90ae2983 410588 libisospec++2-dbgsym_2.0.2+dfsg1-2_amd64.deb 81eaa75d4b25d590118b749a2314c44f66907f79 65648 libisospec++2_2.0.2+dfsg1-2_amd64.deb 26279d95b71d40fe5fdc8f2925c0537ed7a0156d 408556 python3-isospec-dbgsym_2.0.2+dfsg1-2_amd64.deb 6f14719a1a9b00208b89a115860bd806b826288b 75780 python3-isospec_2.0.2+dfsg1-2_amd64.deb 27a4d570ffe38a100010dbb8dbc225f1026934f3 870840 r-cran-isospec-dbgsym_2.0.2+dfsg1-2_amd64.deb 2ec727c7ca67d4bc2370f8361e250f45a944b108 135944 r-cran-isospec_2.0.2+dfsg1-2_amd64.deb Checksums-Sha256: f82c8289adfa61ea9508b64e5d72ed38d2353e406d9c29c6d85dcc4efb974e20 2520 isospec_2.0.2+dfsg1-2.dsc 1bf5f2d5b023a0cdd6cd987e084aab508e2221d9d559868332fe902250b9abc6 32492 isospec_2.0.2+dfsg1-2.debian.tar.xz 0653be52e54cc08e92b78be466956bbc91814f7ca892cdd5d03ad289f9fb6532 14000 isospec_2.0.2+dfsg1-2_amd64.buildinfo 3312798193d61915aa328aba02c9b0ca4b5737a06476f453df80b488cd4722a4 41296 libisospec++-dev_2.0.2+dfsg1-2_amd64.deb 9fc8019a5a7ec47c36ef5ccb6c9af37e3ef119020a18a4aeaec86c8ddc97e8e5 646280 libisospec++-doc_2.0.2+dfsg1-2_all.deb 2b00d69bdc0444b338d927221f30b796dda46b77089c704adf695e3e8a0eb3f7 410588 libisospec++2-dbgsym_2.0.2+dfsg1-2_amd64.deb eae19fbece30632fd21ad35212b7967596aab17b2b504f485dd5f5c8969e4973 65648 libisospec++2_2.0.2+dfsg1-2_amd64.deb 924dfcac707d317704278e1dd78f28ae99f23c744ca53d3d88b858d58d9cfb03 408556 python3-isospec-dbgsym_2.0.2+dfsg1-2_amd64.deb 338950b1a4813b64d46090a6cc867c7dff834f4240bd40f7c5c6fbc1ec026542 75780
Bug#958566: Improved patch added.
Tags: patch
Improved patch is included, which contains correct indentation.
It also displays more information about the chosen version of firmware.
#!/bin/sh
set -e
#
make_download_vars()
{
if [ -n "$latest" ]; then
VERSION="6.30.163.46"
BROADCOM_WL="broadcom-wl-${VERSION}"
WL_APSTA="${BROADCOM_WL}.wl_apsta.o"
SHA512SUM="0144894fbbb5e8ebab6c423d9bd0f3249be94f2f468a50b8bf721a3b17f1f6e57467c79e87abc8d136bfc92e701ed046885fead892e9a73efa5217d710311ae9"
else
VERSION="5.100.138"
BROADCOM_WL="broadcom-wl-${VERSION}"
WL_APSTA="${BROADCOM_WL}/linux/wl_apsta.o"
SHA512SUM="02487e76e3eca7fe97ce2ad7dc9c5d39fac82b8d5f7786cce047f9c85e2426f5b7ea085d84c7d4aae43e0fe348d603e3229211bab601726794ef633441d37a8b"
fi
DOWNLOAD="${BROADCOM_WL}.tar.bz2"
URL="https://www.lwfinger.com/b43-firmware/${DOWNLOAD};
FIRMWARE_INSTALL_DIR="/lib/firmware"
B43="b43"
}
#
# stable sections below, not updated for firmware updates #
#
. /usr/share/debconf/confmodule
install_firmware ()
{
tmp=$(mktemp -q -d)
cd $tmp
# use apt proxy
APT_PROXIES=$(apt-config shell \
http_proxy Acquire::http::Proxy \
https_proxy Acquire::https::Proxy \
ftp_proxy Acquire::ftp::Proxy \
)
if [ -n "$APT_PROXIES" ]; then
eval export $APT_PROXIES
fi
if ! wget --timeout=60 "${URL}"; then
echo "$0: Some problem occurred during the firmware download. Please
check your internet connection." 1>&2
exit 1
fi
if ! sha512sum -c /dev/stdin << EOF; then
${SHA512SUM} ${DOWNLOAD}
EOF
echo "$0: Downloaded firmware did not match known SHA512 checksum,
aborting." 1>&2
exit 1
fi
if [ "${DOWNLOAD}" != "${WL_APSTA}" ]; then
if ! tar xvjf "${DOWNLOAD}" "${WL_APSTA}"; then
echo "$0: Unpacking firmware file failed, unable to continue
(is /tmp full?)." 1>&2
exit 1
fi
fi
catalog="${FIRMWARE_INSTALL_DIR}/${B43}/firmware-${B43}-installer.catalog"
if [ -f "${catalog}" ]; then
echo "$0: Deleting old extracted firmware..." 1>&2
xargs -r -0 -a "${catalog}" dpkg-query -S 2>&1 1>/dev/null | sed
-es',[^/]\+,,' | xargs -r rm --
rm "${catalog}"
fi
mkdir -p "${FIRMWARE_INSTALL_DIR}/${B43}"
retcode=0
b43-fwcutter -w "${FIRMWARE_INSTALL_DIR}" "${WL_APSTA}" | while read line
do echo "${line}"
file="${line#Extracting }"
if [ "${file}" != "${line}" ]
thenif [ "${retcode}" -ne 0 ]
thenrm "${FIRMWARE_INSTALL_DIR}/${file}"
elif [ -z "${FIRMWARE_INSTALL_DIR}/${file}" ] || \
! printf %s/%s\\000 "${FIRMWARE_INSTALL_DIR}" "${file}" >>
"${catalog}"
thenecho "$0: Failed during extraction of ${file} from
${WL_APSTA}" 1>&2
echo "$0: Warning, manual removal/cleaning of
${FIRMWARE_INSTALL_DIR}/${B43} may be needed!" 1>&2
rm "${FIRMWARE_INSTALL_DIR}/${file}"
retcode=1
fi
fi
done
rm -f "${DOWNLOAD}" "${WL_APSTA}"
rm -rf "${BROADCOM_WL}"
# otherwise can't delete things
cd /
rmdir $tmp || echo "$0: DEBUG: targeted cleaning failed" 1>&2
rm -rf $tmp
[ ${retcode} -eq 0 ] || exit ${retcode}
}
# check environment
if [ "$(stat -c %d/%i /)" != "$(stat -Lc %d/%i /proc/1/root 2>/dev/null)" ];
then
echo "A chroot environment has been detected."
echo "Remember this firmware needs kernel >= 2.6.25."
unconditional=1
else
echo "No chroot environment found. Starting normal installation"
fi
if [ -z "$unconditional" ]; then
# check kernel version
if dpkg --compare-versions 2.6.25 gt `uname -r | cut -d- -f1`; then
echo "Kernel too old. This firmware needs >= 2.6.25!."
echo "Aborting!"
exit 0
fi
# install firmware unconditional if the corresponding debconf value is
true
# this is usefull for live-systems or similar systems that should work
on
# changing hardware
db_get b43-fwcutter/install-unconditional
if [ "$RET" = "true" ] ; then
unconditional=1
fi
fi
# check chip
pci=`lspci -n -d 14e4: | grep -o "14e4:[1234567890abcdef]\+"` || true
if [ -z "$pci" ]; then
echo "No known supported Broadcom 802.11 chips found."
if [ -z "$unconditional" ]; then
echo "Not installing firmware."
echo
echo "Aborting."
fi
exit 0
fi
if [ -n "$pci" ] ; then
for device in $pci; do
device_id=${device#14e4:}
case $device_id in
4301 | 4325)
legacy=1
;;
4306)
chip=`lspci -n
Bug#960294: closed by Debian FTP Masters (reply to Etienne Mollier ) (Bug#960294: fixed in tigr-glimmer 3.02b-4)
Control: reopen -1 On Mon, May 11, 2020 at 08:51:11PM +, Debian Bug Tracking System wrote: > * Reinforce Makefiles error checking. Closes: #960294 I fear you only implemented a partial solution (based on my recommendation here). In my tests, failures still go unchecked. I think at least one issue is the linker rule in src/c_make.gen starting with line 359. You added "set -e" there. The command snippet has an outer if branch to select the linker (C vs C++) and an inner branch that removes the linked file on failure. Unfortunately, the failure path does not propagate the failure, because it is already captured in the if. Thus swallowing errors. I didn't see this when writing my bug report either. Beyond this, I strongly recommend implementing verbose build logs. The issue would have been much easier to spot with verbose build logs. Build logs have been a release goal[1]. Building verbosely is also recommended by the Debian policy section 4.9. Unfortunately, the build system at hand doesn't make this possible without patching. Helmut [1] https://wiki.debian.org/ReleaseGoals/VerboseBuildLogs
Processed: Re: Bug#960294 closed by Debian FTP Masters (reply to Etienne Mollier ) (Bug#960294: fixed in tigr-glimmer 3.02b-4)
Processing control commands:
> reopen -1
Bug #960294 {Done: Etienne Mollier }
[src:tigr-glimmer] tigr-glimmer does not trap errors from make
'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 tigr-glimmer/3.02b-4.
--
960294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#960503: xfonts-terminus: 50-enable-terminus.conf missing, fonts are not enabled
Processing commands for cont...@bugs.debian.org: > severity 960503 normal Bug #960503 [xfonts-terminus] xfonts-terminus: 50-enable-terminus.conf missing, fonts are not enabled Severity set to 'normal' from 'grave' > retitle 960503 After upgrade from 1.40 fonts are no longer enabled Bug #960503 [xfonts-terminus] xfonts-terminus: 50-enable-terminus.conf missing, fonts are not enabled Changed Bug title to 'After upgrade from 1.40 fonts are no longer enabled' from 'xfonts-terminus: 50-enable-terminus.conf missing, fonts are not enabled'. > thanks Stopping processing here. Please contact me if you need assistance. -- 960503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960503 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960508: removal of pcb-rnd-{core,doc,rnd-import-net} makes files disappear from pcb-rnd/stable
Package: pcb-rnd-core,pcb-rnd-doc,pcb-rnd-import-net Version: 2.2.0-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts replaces-without-breaks Hi, during a test with piuparts and DOSE tools I noticed your package causes removal of files that also belong to another package. This is caused by using Replaces without corresponding Breaks. The installation sequence to reproduce this problem is apt-get install pcb-rnd/buster # (1) apt-get install pcb-rnd-core apt-get remove pcb-rnd-core # (2) The list of installed files at points (1) and (2) should be identical, but the following files have disappeared: /usr/bin/fp2subc /usr/bin/pcb-prj2lht /usr/bin/pcb-rnd /usr/share/man/man1/fp2subc.1.gz /usr/share/man/man1/pcb-prj2lht.1.gz /usr/share/man/man1/pcb-rnd.1.gz /usr/share/pcb-rnd/default2.lht /usr/share/pcb-rnd/default4.lht /usr/share/pcb-rnd/default_font /usr/share/pcb-rnd/pcblib/connector/BNC_LAY.fp /usr/share/pcb-rnd/pcblib/connector/DB15F.fp /usr/share/pcb-rnd/pcblib/connector/DB15M.fp /usr/share/pcb-rnd/pcblib/connector/DB25F.fp /usr/share/pcb-rnd/pcblib/connector/DB25M.fp ... /usr/share/pcb-rnd/pcblib/tru-hole/TO247.fp /usr/share/pcb-rnd/pcblib/tru-hole/TO247_2.fp /usr/share/pcb-rnd/pcblib/tru-hole/TO251.fp /usr/share/pcb-rnd/pcblib/tru-hole/TO264.fp /usr/share/pcb-rnd/pcblib/tru-hole/TO39.fp /usr/share/pcb-rnd/pcblib/tru-hole/TO92.fp This is a serious bug violating policy 7.6, see https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces and also see the footnote that describes this incorrect behavior: https://www.debian.org/doc/debian-policy/ch-relationships.html#id13 The pcb-rnd-core package has the following relationships with pcb-rnd: Conflicts: n/a Breaks:n/a Replaces: pcb-rnd (<< 2.2.0-2) >From the attached log (scroll to the bottom...): 2m24.4s DEBUG: Modified(user, group, mode, size, target): /var/lib/dpkg/info/pcb-rnd.list expected(root, root, - 100644, 17589, None) != found(root, root, - 100644, 12508, None) 2m24.4s ERROR: FAIL: After purging files have disappeared: /usr/bin/fp2subc owned by: pcb-rnd-core /usr/bin/pcb-prj2lht owned by: pcb-rnd-core /usr/bin/pcb-rnd owned by: pcb-rnd-core /usr/share/man/man1/fp2subc.1.gz owned by: pcb-rnd-core /usr/share/man/man1/pcb-prj2lht.1.gz owned by: pcb-rnd-core ... /usr/share/pcb-rnd/pcblib/tru-hole/TO251.fpowned by: pcb-rnd-core /usr/share/pcb-rnd/pcblib/tru-hole/TO264.fpowned by: pcb-rnd-core /usr/share/pcb-rnd/pcblib/tru-hole/TO39.fp owned by: pcb-rnd-core /usr/share/pcb-rnd/pcblib/tru-hole/TO92.fp owned by: pcb-rnd-core 2m24.4s ERROR: FAIL: After purging files have been modified: /var/lib/dpkg/info/pcb-rnd.listnot owned Similar problems happen with pcb-rnd-doc and pcb-rnd-import-net. Please add Breaks: pcb-rnd (<< 2.2.0-2) to all three packages to prevent such partial upgrades. cheers, Andreas pcb-rnd=2.1.1-1_pcb-rnd-core=2.2.0-3.log.gz Description: application/gzip
Bug#960506: celery: missing Breaks+Replaces: python-celery-common (<< 4.4.2-3)
Package: celery Version: 4.4.2-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' 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/ch-relationships.html#overwriting-files-and-replacing-packages-replaces This test intentionally skipped 'testing' to find file overwrite problems before packages migrate from 'unstable' to 'testing'. >From the attached log (scroll to the bottom...): Preparing to unpack .../python-celery-common_4.2.1-3_all.deb ... Unpacking python-celery-common (4.2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/python-celery-common_4.2.1-3_all.deb (--unpack): trying to overwrite '/usr/bin/celery', which is also in package celery 4.4.2-4 Errors were encountered while processing: /var/cache/apt/archives/python-celery-common_4.2.1-3_all.deb cheers, Andreas celery=4.4.2-4_python-celery-common=4.2.1-3.log.gz Description: application/gzip
Bug#960503: xfonts-terminus: 50-enable-terminus.conf missing, fonts are not enabled
Package: xfonts-terminus Version: 4.48-2 Severity: grave Justification: renders package unusable Hi, the new version lacks the 50-enable-terminus.conf, meaning the fonts are not usable anymore. Please either add a dependency to fonts-terminus-otb (as long as you don't apply #960502) or create the file(s) again. Cheers Jochen -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xfonts-terminus depends on: ii xfonts-utils 1:7.7+6 xfonts-terminus recommends no packages. Versions of packages xfonts-terminus suggests: pn xfonts-terminus-oblique pn xserver | xfs -- no debconf information
Bug#872113: marked as done (waagent: fdisk dependency needed)
Your message dated Wed, 13 May 2020 11:07:40 + with message-id and subject line Bug#872113: fixed in waagent 2.2.47-1 has caused the Debian Bug report #872113, regarding waagent: fdisk dependency needed 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.) -- 872113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872113 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: waagent Version: 2.2.12-2 Severity: important User: util-li...@packages.debian.org Usertags: fdisk-dependency Hello, As recently announced on debian-devel-announce[1] packages who need any of sfdisk, cfdisk or fdisk will need to add a dependency on the new fdisk package. Your package waagent showed up on codesearch.debian.net and a very quick analysis suggested you might want to add a dependency (and/or build-dependency if you use it at build-time, eg. tests). Please use the backwards-compatible way of specifying the dependency as suggested in the debian-devel-announce mail: fdisk | util-linux (<< 2.29.2-3~) (and if only for tests you might want to add the build profile ) Please reassign this bug report to the binary package shipping the affected part of your source. If your more detailed analysis shows this should be a recommends, suggests or even no relationship at all to the fdisk package then please just close this bug report stating the results of your analysis (and if so sorry for bothering you). Regards, Andreas Henriksson [1]: https://lists.debian.org/debian-devel-announce/2017/08/msg5.html --- End Message --- --- Begin Message --- Source: waagent Source-Version: 2.2.47-1 Done: Bastian Blank We believe that the bug you reported is fixed in the latest version of waagent, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 872...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank (supplier of updated waagent 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, 13 May 2020 12:46:19 +0200 Source: waagent Architecture: source Version: 2.2.47-1 Distribution: unstable Urgency: medium Maintainer: Bastian Blank Changed-By: Bastian Blank Closes: 872113 Changes: waagent (2.2.47-1) unstable; urgency=medium . * New upstream version. * Remove recurring message for disabled auto-update. * Depend on fdisk. (closes: #872113) Checksums-Sha1: 6629b02afc231cb047ab22bbb0f0b79d7236ed77 1549 waagent_2.2.47-1.dsc 812382aa9e34f5e8840f0e88890b536c5c46d4a1 1336396 waagent_2.2.47.orig.tar.xz 7979e1f97a4b34300fea299ebcf55dd73268662c 10848 waagent_2.2.47-1.debian.tar.xz 12dc3f96857a78ec461a1c655944e8abba6652a9 6237 waagent_2.2.47-1_source.buildinfo Checksums-Sha256: 56d32f07425ff2ac2976b28f1683bc0349b3942e7189152176bf5d147340837f 1549 waagent_2.2.47-1.dsc cb3904fd6341409604376d7ffe56cf48f34bb651c3a6a6581be05bbf83012ad2 1336396 waagent_2.2.47.orig.tar.xz b31d8175b3e0d7a602f19ae58faeb5a4869ff33bc3f7d2b69995b8f38804b78f 10848 waagent_2.2.47-1.debian.tar.xz e86ad16d9e329e7eb09db69bd67560664eb6f610306bbdb1f9d5b2c360c8c280 6237 waagent_2.2.47-1_source.buildinfo Files: 760c06c102587f5a71e247739b2b88cd 1549 admin optional waagent_2.2.47-1.dsc dd5cfa4add8e3cd617ac08329f8720c7 1336396 admin optional waagent_2.2.47.orig.tar.xz 0d347bd02fafaf6ffca1f7244d4f9a4b 10848 admin optional waagent_2.2.47-1.debian.tar.xz fd7ff1d9628658465dc04a15af6d3ae6 6237 admin optional waagent_2.2.47-1_source.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEER3HMN63jdS1rqjxLbZOIhYpp/lEFAl670JgACgkQbZOIhYpp /lHKbQf+LhBngUe2NdFAtHME9FN+OOnQz1LgjK6GoP59MBL+rKyeX+bMV7la/YKS ZTBCKZddoNezdpgxyQTHdcdRlzbMGyliFL6ekyD3SfBXHp2+Spt9zQpCfCk0JrJb lfDLRuVvD5r/4bjmNf7ihFITT0HoMKLx4YxSS+jdoNG/l5zzSu90Ov41vOz5Mdc3 hI8/UN6BuBJp1N0EpPahXBhULotsV/A8HnbxHtgH72D7v9OVbArEva7KU5+Ega2z GKXanyqQTH7Og569MDQCZY2W1Uf1Io2aUk7Lkl4SdukRcIoPA5GVgPcyLTXgMiwO SQ0V5ILBz8gSswhgqWYtX1V2fVWBOg== =FBNH -END PGP SIGNATURE End Message ---
Bug#960344: marked as done (libkf5dav-dev,libkf5dav-data: missing Breaks+Replaces: libkpimkdav-{dev,data})
Your message dated Wed, 13 May 2020 10:49:05 +
with message-id
and subject line Bug#960344: fixed in kdav 20.04.0-2
has caused the Debian Bug report #960344,
regarding libkf5dav-dev,libkf5dav-data: missing Breaks+Replaces:
libkpimkdav-{dev,data}
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
960344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960344
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkf5dav-dev,libkf5dav-data
Version: 20.04.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>From the attached log (scroll to the bottom...):
...
Preparing to unpack .../10-libkf5dav-data_20.04.0-1_all.deb ...
Unpacking libkf5dav-data (20.04.0-1) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-KCmgJU/10-libkf5dav-data_20.04.0-1_all.deb (--unpack):
trying to overwrite '/usr/share/locale/ar/LC_MESSAGES/libkdav.mo', which is
also in package libkpimkdav-data 19.08.3-1
...
Preparing to unpack .../20-libkf5dav-dev_20.04.0-1_amd64.deb ...
Unpacking libkf5dav-dev:amd64 (20.04.0-1) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-KCmgJU/20-libkf5dav-dev_20.04.0-1_amd64.deb (--unpack):
trying to overwrite
'/usr/lib/x86_64-linux-gnu/qt5/mkspecs/modules/qt_kdav.pri', which is also in
package libkpimkdav-dev:amd64 19.08.3-1
Errors were encountered while processing:
/tmp/apt-dpkg-install-KCmgJU/10-libkf5dav-data_20.04.0-1_all.deb
/tmp/apt-dpkg-install-KCmgJU/20-libkf5dav-dev_20.04.0-1_amd64.deb
cheers,
Andreas
libkpimkdav-dev=19.08.3-1_libkf5dav-dev=20.04.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: kdav
Source-Version: 20.04.0-2
Done: =?utf-8?q?Sandro_Knau=C3=9F?=
We believe that the bug you reported is fixed in the latest version of
kdav, 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 960...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sandro Knauß (supplier of updated kdav 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, 13 May 2020 12:20:36 +0200
Source: kdav
Architecture: source
Version: 20.04.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers
Changed-By: Sandro Knauß
Closes: 960344
Changes:
kdav (20.04.0-2) experimental; urgency=medium
.
* Mark libkf5dav-{data,dev} to Replace libkpimkdav-{data,dev} (Closes:
#960344).
Checksums-Sha1:
68646cc7fcc9fb28d06e1e62d9156cb5fc534729 2554 kdav_20.04.0-2.dsc
429f27ba12e3f4ab1b4e02de2c4b8c5e235692ed 11740 kdav_20.04.0-2.debian.tar.xz
1d9b6ca1aff0fa76aec54a20b8ec2ee48c607590 16432 kdav_20.04.0-2_source.buildinfo
Checksums-Sha256:
f07c018e42a5484b00170f45d179ff85dc8bdeef35e049941c287b6d5e346a7f 2554
kdav_20.04.0-2.dsc
8985d45b1b1ab56f755b453dd72a4dca7dde79e7bedcdc742ef46e471fe0781b 11740
kdav_20.04.0-2.debian.tar.xz
6060121e4da2ecce6676e380486920446148e567b7ad75dc038a3cc260ced82c 16432
kdav_20.04.0-2_source.buildinfo
Files:
141416333e30e6ea208c6f73c3280fea 2554 libs optional kdav_20.04.0-2.dsc
a3e0952870859051a0fb88e6f8bd5454 11740 libs optional
kdav_20.04.0-2.debian.tar.xz
794f6361713f49e5438a517f53d852e6 16432 libs optional
kdav_20.04.0-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCgAvFiEEOewRoCAWtykmSRoG462wCFBgVjYFAl67y38RHGhlZmVlQGRl
Ymlhbi5vcmcACgkQ462wCFBgVjZL3RAAgHur+LgoreL5PUtlz7GlHR3NA+pYpbSh
IQNCcGwyI874oiLZQF9DxZ8pIAgFneEnsYDLa1anLEcrvkk64Xrn02Wadio2Xt5D
v2wrWPqiYIpA53Upsm7SQtTcpaMYVOjftWnGSoY66M9bu0GrqNBw2sx98SJSJdGk
fFOacRQD8KRU1HeVmBoJPYyjZIOO8XBG6Pitup1jD0NPx4C+wt/N6FUq/3QPDPBP
CWKZXTKMeIaRAhty/Qd92OoOgnSW/ekBAI8uq0wLt52Tcn04YZvOI8F/pmceI268
PbrM+WzVZN+yTDl9BwqMs/fBTnQeTFQLA+wRWcVqFm6JX3fFvWeVXNE5uYXfp4MO
Bug#960496: opensurgsim: FTBFS: no path found matching pattern /usr/share/javascript/jquery/jquery.js
Source: opensurgsim Version: 0.7.0-9 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) opensugsim currently fails to build: |dh_linktree | dpkg-query: no path found matching pattern /usr/share/javascript/jquery/jquery.js | dh_linktree: error: dpkg --search -- /usr/share/javascript/jquery/jquery.js subprocess returned exit status 1 | make: *** [debian/rules:7: binary] Error 25 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#959584: marked as done (gnome-photos: FTBFS: FAILED: src/photos-resources.c)
Your message dated Wed, 13 May 2020 10:18:26 + with message-id and subject line Bug#959584: fixed in gnome-photos 3.34.1-2 has caused the Debian Bug report #959584, regarding gnome-photos: FTBFS: FAILED: src/photos-resources.c 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.) -- 959584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-photos Version: 3.34.1-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200501 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- -Ddogtail=false > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Ddogtail=false > The Meson build system > Version: 0.54.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: gnome-photos > Project version: 3.34.1 > Using 'CFLAGS' from environment with value: '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Using 'LDFLAGS' from environment with value: '-Wl,-z,relro -Wl,-z,now -Wl,-O1 > -Wl,-z,defs -Wl,--as-needed' > Using 'CPPFLAGS' from environment with value: '-Wdate-time > -D_FORTIFY_SOURCE=2' > Using 'CFLAGS' from environment with value: '-g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Using 'LDFLAGS' from environment with value: '-Wl,-z,relro -Wl,-z,now -Wl,-O1 > -Wl,-z,defs -Wl,--as-needed' > Using 'CPPFLAGS' from environment with value: '-Wdate-time > -D_FORTIFY_SOURCE=2' > C compiler for the host machine: cc (gcc 9.3.0 "cc (Debian 9.3.0-11) 9.3.0") > C linker for the host machine: cc ld.bfd 2.34 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Checking if "_NL_MEASUREMENT_MEASUREMENT" compiles: YES > Compiler for C supports arguments -Wall: YES > Compiler for C supports arguments -Winvalid-pch: YES > Compiler for C supports arguments -fno-strict-aliasing: YES > Compiler for C supports arguments -Wcast-align: YES > Compiler for C supports arguments -Wclobbered: YES > Compiler for C supports arguments -Wdeclaration-after-statement: YES > Compiler for C supports arguments -Wempty-body: YES > Compiler for C supports arguments -Wformat=2: YES > Compiler for C supports arguments -Wignored-qualifiers: YES > Compiler for C supports arguments -Wimplicit-fallthrough=3: YES > Compiler for C supports arguments -Winit-self: YES > Compiler for C supports arguments -Winline: YES > Compiler for C supports arguments -Wmissing-declarations: YES > Compiler for C supports arguments -Wmissing-field-initializers: YES > Compiler for C supports arguments -Wmissing-format-attribute: YES > Compiler for C supports arguments -Wmissing-include-dirs: YES > Compiler for C supports arguments -Wmissing-noreturn: YES > Compiler for C supports arguments -Wmissing-parameter-type: YES > Compiler for C supports arguments -Wmissing-prototypes: YES > Compiler for C supports arguments -Wnested-externs: YES > Compiler for C supports arguments -Wold-style-definition: YES > Compiler for C supports arguments -Woverride-init: YES > Compiler for C supports arguments -Wpacked: YES > Compiler for C supports arguments -Wpointer-arith: YES > Compiler for C supports arguments -Wredundant-decls: YES > Compiler for C supports arguments -Wshadow: YES > Compiler for C supports arguments -Wsign-compare: YES > Compiler for C supports arguments -Wstrict-prototypes: YES > Compiler for C supports arguments -Wswitch-default: YES > Compiler for C supports arguments -Wswitch-enum: YES > Compiler for C supports arguments -Wtype-limits: YES > Compiler for C supports arguments -Wundef: YES > Compiler for C supports arguments -Wuninitialized: YES > Compiler for C supports arguments -Wunused: YES > Compiler for C supports arguments -Wwrite-strings: YES > Compiler for C supports arguments -Wno-cast-function-type > -Wcast-function-type: YES > Compiler for C supports arguments -Wno-error=cast-function-type > -Werror=cast-function-type: YES > Compiler for C supports arguments -Wno-missing-field-initializers > -Wmissing-field-initializers: YES > Compiler for C supports arguments -Wno-error=missing-field-initializers > -Werror=missing-field-initializers: YES > Compiler for C supports arguments
Bug#960404: marked as done (minizinc FTBFS with bison 3.6.1)
Your message dated Wed, 13 May 2020 10:18:51 + with message-id and subject line Bug#960404: fixed in minizinc 2.4.3-2 has caused the Debian Bug report #960404, regarding minizinc FTBFS with bison 3.6.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.) -- 960404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: minizinc Version: 2.4.3-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/minizinc.html ... /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp: In function 'int mzn_yyparse(void*)': /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp:97:11: error: request for member 'filename' in 'yylsp', which is of pointer type 'MiniZinc::ParserLocation*' (maybe you meant to use '->' ?) 97 | Current.filename(Rhs[1].filename()); \ | ^~~~ /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp:5176:3: note: in expansion of macro 'YYLLOC_DEFAULT' 5176 | YYLLOC_DEFAULT (*yylsp, yyerror_range, 2); | ^~ /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp:98:11: error: request for member 'first_line' in 'yylsp', which is of pointer type 'MiniZinc::ParserLocation*' (maybe you meant to use '->' ?) 98 | Current.first_line(Rhs[1].first_line()); \ | ^~ /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp:5176:3: note: in expansion of macro 'YYLLOC_DEFAULT' 5176 | YYLLOC_DEFAULT (*yylsp, yyerror_range, 2); | ^~ /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp:99:11: error: request for member 'first_column' in 'yylsp', which is of pointer type 'MiniZinc::ParserLocation*' (maybe you meant to use '->' ?) 99 | Current.first_column(Rhs[1].first_column()); \ | ^~~~ /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp:5176:3: note: in expansion of macro 'YYLLOC_DEFAULT' 5176 | YYLLOC_DEFAULT (*yylsp, yyerror_range, 2); | ^~ /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp:100:11: error: request for member 'last_line' in 'yylsp', which is of pointer type 'MiniZinc::ParserLocation*' (maybe you meant to use '->' ?) 100 | Current.last_line(Rhs[N].last_line()); \ | ^ /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp:5176:3: note: in expansion of macro 'YYLLOC_DEFAULT' 5176 | YYLLOC_DEFAULT (*yylsp, yyerror_range, 2); | ^~ /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp:101:11: error: request for member 'last_column' in 'yylsp', which is of pointer type 'MiniZinc::ParserLocation*' (maybe you meant to use '->' ?) 101 | Current.last_column(Rhs[N].last_column()); | ^~~ /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp:5176:3: note: in expansion of macro 'YYLLOC_DEFAULT' 5176 | YYLLOC_DEFAULT (*yylsp, yyerror_range, 2); | ^~ make[3]: *** [CMakeFiles/minizinc_parser.dir/build.make:88: CMakeFiles/minizinc_parser.dir/parser.tab.cpp.o] Error 1 --- End Message --- --- Begin Message --- Source: minizinc Source-Version: 2.4.3-2 Done: Kari Pahula We believe that the bug you reported is fixed in the latest version of minizinc, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kari Pahula (supplier of updated minizinc 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, 13 May 2020 12:59:18 +0300 Source: minizinc Architecture: source Version: 2.4.3-2 Distribution: unstable Urgency: medium Maintainer: Kari Pahula Changed-By: Kari Pahula Closes: 960404 Changes: minizinc (2.4.3-2) unstable; urgency=medium . * Protect "Current" in YYLLOC_DEFAULT macro with parentheses in lib/parser.y to build with new Bison (Closes: #960404) * Standards-Version 4.5.0 and dh compat 13 (no changes necessary) Checksums-Sha1: 3b307dec079fc8a19447cf72729b269e3ab7984b 1798 minizinc_2.4.3-2.dsc
Processed: Bug#959584 marked as pending in gnome-photos
Processing control commands: > tag -1 pending Bug #959584 [src:gnome-photos] gnome-photos: FTBFS: FAILED: src/photos-resources.c Added tag(s) pending. -- 959584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959584: marked as pending in gnome-photos
Control: tag -1 pending Hello, Bug #959584 in gnome-photos reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/gnome-photos/-/commit/884189f0868e475de97b2b6333bc54fabad36f02 Build-Depend on librsvg2-common:native This package contains the SVG backend for gdk-pixbuf, which is necessary to ensure that gdk-pixbuf-pixdata can actually load SVGs. It was previously pulled in via the dependency chain libgtk-3-0 -> adwaita-icon-theme -> librsvg2-common Closes: #959584 (this message was generated automatically) -- Greetings https://bugs.debian.org/959584
Processed: transition: gdal
Processing control commands: > forwarded -1 https://release.debian.org/transitions/html/auto-gdal.html Bug #960495 [release.debian.org] transition: gdal Set Bug forwarded-to-address to 'https://release.debian.org/transitions/html/auto-gdal.html'. > block -1 by 960369 953138 Bug #960495 [release.debian.org] transition: gdal 960495 was not blocked by any bugs. 960495 was not blocking any bugs. Added blocking bug(s) of 960495: 960369 and 953138 -- 960495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 925797 in opensurgsim/0.7.0-9, notfixed 925797 in gpgme1.0/1.13.1-7
Processing commands for cont...@bugs.debian.org:
> fixed 925797 opensurgsim/0.7.0-9
Bug #925797 {Done: Daniel Kahn Gillmor }
[src:opensurgsim] opensurgsim: ftbfs with GCC-9
Marked as fixed in versions opensurgsim/0.7.0-9.
> notfixed 925797 gpgme1.0/1.13.1-7
Bug #925797 {Done: Daniel Kahn Gillmor }
[src:opensurgsim] opensurgsim: ftbfs with GCC-9
No longer marked as fixed in versions gpgme1.0/1.13.1-7.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
925797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#960459: marked as done (memcached/1.6.5-2 FTBFS on s390x)
Your message dated Wed, 13 May 2020 09:19:18 + with message-id and subject line Bug#960459: fixed in memcached 1.6.6-1 has caused the Debian Bug report #960459, regarding memcached/1.6.5-2 FTBFS on s390x 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.) -- 960459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: memcached Version: 1.6.5-2 Severity: serious Dear Maintainer, The latest version of memcached (1.6.5-2) FTBFS on s390x: https://buildd.debian.org/status/fetch.php?pkg=memcached=s390x=1.6.5-2=1587246609=0 This failure is blocking its migration to testing. -- Lucas Kanashiro --- End Message --- --- Begin Message --- Source: memcached Source-Version: 1.6.6-1 Done: Chris Lamb We believe that the bug you reported is fixed in the latest version of memcached, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb (supplier of updated memcached 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, 13 May 2020 10:10:16 +0100 Source: memcached Built-For-Profiles: nocheck Architecture: source Version: 1.6.6-1 Distribution: unstable Urgency: medium Maintainer: Chris Lamb Changed-By: Chris Lamb Closes: 960459 Changes: memcached (1.6.6-1) unstable; urgency=medium . * New upstream release. - Fixes FTBFS on s390x and other architectures. (Closes: #960459) Checksums-Sha1: 95219c574ebc9092982f2bec3377cf067181263d 1934 memcached_1.6.6-1.dsc d8895b12dc9fc82b389f1713e2c09cc6ca3d03e4 543661 memcached_1.6.6.orig.tar.gz 828a27fd927ce88c08084db11aa692c4610e3d91 15280 memcached_1.6.6-1.debian.tar.xz f3abac9be2c12b5bdde4fd513e6f3269d53c230f 6065 memcached_1.6.6-1_amd64.buildinfo Checksums-Sha256: 91a61f0bc419b2c8136322f1bcd461d6d73bf844881c17e9189c8d7527f1bd0e 1934 memcached_1.6.6-1.dsc 908f0eecfa559129c9e44edc46f02e73afe8faca355b4efc5c86d902fc3e32f7 543661 memcached_1.6.6.orig.tar.gz d1bd3ade5c9ff92a904e4b0489307b5f2e9877cadd79a5d06ff1b3e6b8a47eef 15280 memcached_1.6.6-1.debian.tar.xz 576722262a260de3d882bcd3ee46f85963dde626274a7d08f711641729ae2301 6065 memcached_1.6.6-1_amd64.buildinfo Files: eb5c0282c2d61333ffae5e07f3cb7252 1934 web optional memcached_1.6.6-1.dsc 6711343b85e47a793dc892cfbddc130c 543661 web optional memcached_1.6.6.orig.tar.gz 3c90030b6f61e59aa5a2fb64fdc71db9 15280 web optional memcached_1.6.6-1.debian.tar.xz 798de2318325257edf13b4b1a319b181 6065 web optional memcached_1.6.6-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl67ua8ACgkQHpU+J9Qx Hlg3yA//VWdLyxF9Wq9DZDoCg4UTH6DV9ZIxIfMoF//YAGhhlg7kB8Bc9B230GHs lhTzH737AOphQHfaT65Xs7IEeG0225gH1cMEUkL7z/CqdUAsV9928+fjSNKWaxZd mMDHdlH1DokG1NwgK9WxL/fXEpcMkbvbrEmnoG9I5XdQ3f4DFtXl2/gl58Oaic7N rcjRjO41YWO5N8s2LIqwhbfSFzirX8Qusmx/m1mxQBKcfxMaDXaFDb/4iJC8CA78 sYGh1wHvlZTDCkfojUi+xCKgfbyGrPLvUyYw2CMJhaPLJcfDggThC+CtpoK8qps4 zDE6XqLAN6EP8YVFm4Tx6PW++KMrfSfcEUk2h54bMeDRYQ47h3zYGsDEMWsUdqkH CVwUcBmrHAoh0ZCma94IlRdsrOJGLY58UGzyrpOJQM+AuSVhn6YUMoWliDd5UIms QnxQ7QEc1LfPcrlor0zlPM48Un5mEOJ2QKH4Z4N1qNGO6Jg4VQckGphR+fFVWgaK vhJEMLEO9xlFzrEJVJbUO2vX7Hs0l/1h7maI26q+AGgDkraDwqQAQmuVFR5Pd0bK U9xHEHDHKZuxJiOGE0ZvlIDgowzF2Zi+ancQ1DXuh0+yF7iPBitauZjpam2h5x+0 5WYJ1JETZm8ODSmeVgQ1T7mT5pjtnJ0QCzY88Xe3lxx1LXLqTx0= =r734 -END PGP SIGNATURE End Message ---
Bug#960411: marked as done (python-pybedtools build-dependencies unsatisfiable on armel, armhf and mipsel)
Your message dated Wed, 13 May 2020 08:33:42 + with message-id and subject line Bug#960411: fixed in python-pybedtools 0.8.0-4 has caused the Debian Bug report #960411, regarding python-pybedtools build-dependencies unsatisfiable on armel, armhf and mipsel 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.) -- 960411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960411 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pybedtools Version: 0.8.0-3 Severity: serious bedtools is no longer available in testing on armel, armhf or mipsel (or i386 but python-pybedtools never seems to have built there) which makes the build-dependencies of python-pybedtools unsatisfiable on those architectures. Either https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955403 needs to be fixed or python-pybedtools needs to be removed from the architectures in question. --- End Message --- --- Begin Message --- Source: python-pybedtools Source-Version: 0.8.0-4 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of python-pybedtools, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated python-pybedtools 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, 13 May 2020 09:14:53 +0200 Source: python-pybedtools Architecture: source Version: 0.8.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 960411 Changes: python-pybedtools (0.8.0-4) unstable; urgency=medium . * Team upload. * Rebuild against available architectures Closes: #960411 * Standards-Version: 4.5.0 (routine-update) * Remove trailing whitespace in debian/rules (routine-update) * Add salsa-ci file (routine-update) * Rules-Requires-Root: no (routine-update) * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Add missing shebang lines in scripts * Move example script to examples * Fix permission of script Checksums-Sha1: 402ad1bacdd9510e2f58bec72f4056422e51988c 2531 python-pybedtools_0.8.0-4.dsc a99dbf1bfaf385d255d1d7ad214dd902db8977b4 31536 python-pybedtools_0.8.0-4.debian.tar.xz 9397c5274ec372734b8453bff80ada1659193e39 11107 python-pybedtools_0.8.0-4_amd64.buildinfo Checksums-Sha256: 5ddc9f5dfadc5d4b7aca28c77381d67276489977ccafee2e37d5d2c283a07049 2531 python-pybedtools_0.8.0-4.dsc cc8a1ce4c11fd155ba7884276992f65e4698dfe47a05c9a31a02855fe122a83b 31536 python-pybedtools_0.8.0-4.debian.tar.xz c61123947d1ef62b817df8c17231f24f5e736b2a27fd3cf34f1412a6b4d9d226 11107 python-pybedtools_0.8.0-4_amd64.buildinfo Files: a3ad9308335c0c874a8c81826c3ce415 2531 python optional python-pybedtools_0.8.0-4.dsc ce75f07e7f13418c93b43e23f703bbaa 31536 python optional python-pybedtools_0.8.0-4.debian.tar.xz 32fcf87d87058f4597445e7278629514 11107 python optional python-pybedtools_0.8.0-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl67rMcRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtEgMg//TDh037uI1ewdZg86r/o980e4YqQEDu4B 639aA46idbi7zcWWd6TPt/dmh9rDFOzXZUsT9ncgwQ4DwqunT+pssaihqZUugwxv EjpYId7iCPyZjOmhEz3Y3+whFcW3XKgvIkQW+u+EsuXTzgj6T4pMFegaZUPCqoD7 r8OaEull2V2MoVF6w3SmsAzvKca3I+Bn307PkCBNaqe+RZmn7zPva5kSt78TneYI ZIi086s8u2aUKBum827hfCZhgQSsgUvs8Jf0BSIAY0CIJePXyI7WwCzXwEyt+1zl QAQMf5Z5tHUw/3SH1egIxlIgDsl8+uNvgukI6LlFecxGxeuXTR3P7oepIzooXIP5 2JHHMFhzxlhaIP/kJUYiWXtdLZylF8S3zhQKoFSD2eXO8Q186XuX1TjJMFVUGw+E VC9pp+E/1hFIfahTF8RTJfmbsGy+vqMAXeCT22YHv/6JsNMbEbalweZHpomhl4vi MU19hDW68B3GSybZSbSoOh5147jRmXhd2k8wbAF9dkyijDwQzmAB6KkfTx3QHVER 8tS7Mh/YrnFgFueDYCSsniBSZGogbSNyqe/YX7iv6gbH+pWDKCB8JkIK2O9G3Z7Y nTQ4qzQuCabGXSwrMLHzSBgUf+E6r22Sxfs9tGtz8Vv0BcH5ybCBhqt3xFZy0cAB i2A7rJVLCYI= =d4mg -END PGP SIGNATURE End Message ---
Bug#959940: marked as done (hdmf FTBFS with h5py 2.10.0)
Your message dated Wed, 13 May 2020 08:26:08 +
with message-id
and subject line Bug#959940: fixed in h5py 2.10.0-8
has caused the Debian Bug report #959940,
regarding hdmf FTBFS with h5py 2.10.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
959940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959940
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hdmf
Version: 1.5.4-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:pynwb
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hdmf.html
...
==
ERROR: test_dynamic_container_constructor_name_default_name
(tests.unit.build_tests.test_io_map.TestDynamicContainer)
--
Traceback (most recent call last):
File
"/build/1st/hdmf-1.5.4/.pybuild/cpython3_3.8_hdmf/build/tests/unit/build_tests/test_io_map.py",
line 313, in test_dynamic_container_constructor_name_default_name
with self.assertWarns(Warning):
File "/usr/lib/python3.8/unittest/case.py", line 255, in __enter__
if getattr(v, '__warningregistry__', None):
File
"/usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/h5py_warnings.py",
line 36, in __getattr__
return getattr(self._mod, attr)
File
"/usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/h5py_warnings.py",
line 35, in __getattr__
self._mod = self._import()
File
"/usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/h5py_warnings.py",
line 39, in _import
return import_module(self._mod)
File "/usr/lib/python3.8/importlib/__init__.py", line 118, in import_module
if name.startswith('.'):
File
"/usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/h5py_warnings.py",
line 35, in __getattr__
self._mod = self._import()
File
"/usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/h5py_warnings.py",
line 39, in _import
return import_module(self._mod)
File "/usr/lib/python3.8/importlib/__init__.py", line 118, in import_module
if name.startswith('.'):
...
File
"/usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/h5py_warnings.py",
line 35, in __getattr__
self._mod = self._import()
File
"/usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/h5py_warnings.py",
line 39, in _import
return import_module(self._mod)
File "/usr/lib/python3.8/importlib/__init__.py", line 118, in import_module
if name.startswith('.'):
File
"/usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/h5py_warnings.py",
line 35, in __getattr__
self._mod = self._import()
RecursionError: maximum recursion depth exceeded
--
Ran 464 tests in 3.412s
FAILED (errors=8)
E: pybuild pybuild:352: test: plugin distutils failed with: exit code=1: cd
/build/1st/hdmf-1.5.4/.pybuild/cpython3_3.8_hdmf/build; python3.8 -m unittest
discover -v
dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit
code 13
make: *** [debian/rules:7: build] Error 25
--- End Message ---
--- Begin Message ---
Source: h5py
Source-Version: 2.10.0-8
Done: Drew Parsons
We believe that the bug you reported is fixed in the latest version of
h5py, 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 959...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Drew Parsons (supplier of updated h5py 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, 13 May 2020 15:45:16 +0800
Source: h5py
Architecture: source
Version: 2.10.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Drew Parsons
Closes: 958319 959940
Changes:
h5py (2.10.0-8) unstable; urgency=medium
.
* Team upload.
* reinstate upstream deprecation patches. Closes: #959940.
* add debian patch use_system_lzf.patch to use lzf from liblzf-dev.
(still needs localpath('lzf') to access lzf_filter.h)
Build-Depends: liblzf-dev. Closes: #958319.
Checksums-Sha1:
ece9bcf66687feb5703309a12f8904b267368e9a 2860 h5py_2.10.0-8.dsc
Bug#960488: eslint: autopkgtest failure: missing test dependency to node-babel7
Package: eslint Version: 5.16.0~dfsg-5 Severity: serious Justification: unknwon Hi, node-babel7 seems required by autopkgtest test: not ok 344 - /tmp/autopkgtest-lxc.9p09fhxf/downtmp/build.w0w/src/lib/formatters/codeframe.js --- message: '"@babel/code-frame" is not found.' severity: error data: line: 8 column: 38 ruleId: node/no-missing-require ... Cheers, Xavier
Bug#960481: syslog-ng FTBFS with bison 3.6.1
Source: syslog-ng
Version: 3.25.1-3
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/syslog-ng.html
...
lib/pragma-grammar.y: In function 'pragma_parse':
lib/pragma-grammar.y:402:73: error: 'YYEMPTY' undeclared (first use in this
function)
402 | stmt_and_eol { if (yychar !=
YYEMPTY) { cfg_lexer_unput_token(lexer, ); } PRAGMA_END(); YYACCEPT; }
|
^~~
lib/pragma-grammar.y:402:73: note: each undeclared identifier is reported only
once for each function it appears in
make[3]: *** [Makefile:15459: lib/libsyslog_ng_la-pragma-grammar.lo] Error 1
Bug#960480: verilator FTBFS with bison 3.6.1
Source: verilator Version: 4.028-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/verilator.html ... In file included from ../verilog.l:23, from ../V3ParseLex.cpp:32: ./V3ParseBison.h:409:62: warning: missing terminating " character 409 | yVL_CLOCK = 610, /* "/*verilator sc_clock*/" */ | ^ ./V3ParseBison.h:409:62: error: missing terminating " character 409 | yVL_CLOCK = 610, /* "/*verilator sc_clock*/" */ | ^ ./V3ParseBison.h:410:61: warning: missing terminating " character 410 | yVL_CLOCKER = 611, /* "/*verilator clocker*/" */ | ^ /V3ParseBison.h:410:61: error: missing terminating " character 410 | yVL_CLOCKER = 611, /* "/*verilator clocker*/" */ | ^ ./V3ParseBison.h:411:64: warning: missing terminating " character 411 | yVL_NO_CLOCKER = 612, /* "/*verilator no_clocker*/" */ |^ ./V3ParseBison.h:411:64: error: missing terminating " character 411 | yVL_NO_CLOCKER = 612, /* "/*verilator no_clocker*/" */ |^ ./V3ParseBison.h:412:66: warning: missing terminating " character 412 | yVL_CLOCK_ENABLE = 613,/* "/*verilator clock_enable*/" */ | ^ ./V3ParseBison.h:412:66: error: missing terminating " character 412 | yVL_CLOCK_ENABLE = 613,/* "/*verilator clock_enable*/" */ | ^ ...
Processed: libdaq-dev: Missing dependencies on libdumbnet-dev, libnetfilter-queue-dev, libpcap0.8-dev
Processing control commands: > affects -1 src:snort Bug #960479 [libdaq-dev] libdaq-dev: Missing dependencies on libdumbnet-dev, libnetfilter-queue-dev, libpcap0.8-dev Added indication that 960479 affects src:snort -- 960479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960479 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960479: libdaq-dev: Missing dependencies on libdumbnet-dev, libnetfilter-queue-dev, libpcap0.8-dev
Package: libdaq-dev Version: 2.0.7-2 Severity: serious Tags: ftbfs Control: affects -1 src:snort https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/snort.html ... checking for dlsym in -ldl... yes checking for daq_load_modules in -ldaq_static... no ERROR! daq_static library not found, go get it from http://www.snort.org/. ... configure:13020: checking for daq_load_modules in -ldaq_static configure:13045: gcc -o conftest -g -O2 -ffile-prefix-map=/build/1st/snort-2.9.15.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -Wl,-z,relro -Wl,-z,now -lpcre -ldumbnet conftest.c -ldaq_static -ldumbnet -lpcre -lpcap -lnsl -lm -lm -lcrypto -ldl -L/usr/lib/x86_64-linux-gnu -ldaq_static_modules -lsfbpf -lpcap -lsfbpf -lnfnetlink -lnetfilter_queue -lsfbpf -lpcap -ldumbnet >&5 /usr/bin/ld: cannot find -lnfnetlink /usr/bin/ld: cannot find -lnetfilter_queue collect2: error: ld returned 1 exit status ... This is due to: $ daq-modules-config --static --libs -L/usr/lib/x86_64-linux-gnu -ldaq_static_modules -lsfbpf -lpcap -lsfbpf -lnfnetlink -lnetfilter_queue -lsfbpf -lpcap -ldumbnet $
