Processed: Re: Bug#905767: emacs25: FTBFS due to test failures on arm64 in a binNMU against new version of libmagick
Processing control commands: > reassign -1 src:emacs25 Bug #905767 [emacs25] emacs25: FTBFS due to test failures on arm64 in a binNMU against new version of libmagick Bug reassigned from package 'emacs25' to 'src:emacs25'. No longer marked as found in versions emacs25/25.2+1-6. Ignoring request to alter fixed versions of bug #905767 to the same values previously set -- 905767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905767: emacs25: FTBFS due to test failures on arm64 in a binNMU against new version of libmagick
Control: reassign -1 src:emacs25 Rob Browning: > Niels Thykier writes: > >> Package: emacs25 >> Version: 25.2+1-6+b3 >> Severity: serious >> Tags: ftbfs >> Justification: fails to build from source > > This should be fixed in emacs 1:25.2+1-9, which hopefully will be able > to completely replace emacs25 in sid/buster soon. > > Thanks > Indeed. This was intended for src:emacs25 (I had not seen we had an src:emacs now). Reassining to the proper package. :) Thanks ~Niels
Bug#903182: marked as done (mtr: FTBFS in buster/sid (dh_installman: Cannot find "mtr/mtr.8"))
Your message dated Fri, 10 Aug 2018 05:48:54 + with message-id and subject line Bug#903182: fixed in mtr 0.92-1.1 has caused the Debian Bug report #903182, regarding mtr: FTBFS in buster/sid (dh_installman: Cannot find "mtr/mtr.8") to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 903182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mtr Version: 0.92-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch dh_update_autotools_config -a dh_autoreconf -a debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' ./bootstrap.sh touch configure.in && \ touch aclocal.m4 && \ touch configure head -n 1 debian/changelog | sed 's/[^(]*(\([^-]*\)-.*/\1/' > .tarball-version autoreconf -fi autoreconf: 'configure.ac' and 'configure.in' both present. autoreconf: proceeding with 'configure.ac' [... snipped ...] dh_auto_install --builddirectory=mtr --destdir=debian/mtr cd mtr && make -j1 install DESTDIR=/<>/debian/mtr AM_UPDATE_INFO_DIR=no make[2]: Entering directory '/<>/mtr' make[3]: Entering directory '/<>/mtr' /bin/mkdir -p '/<>/debian/mtr/usr/bin' /usr/bin/install -c mtr mtr-packet '/<>/debian/mtr/usr/bin' make install-exec-hook make[4]: Entering directory '/<>/mtr' `setcap cap_net_raw+ep /<>/debian/mtr/usr/bin/mtr-packet` \ || chmod u+s /<>/debian/mtr/usr/bin/mtr-packet /bin/bash: line 1: setcap: command not found make[4]: Leaving directory '/<>/mtr' /bin/mkdir -p '/<>/debian/mtr/usr/share/bash-completion/completions' /usr/bin/install -c -m 644 ../bash-completion/mtr '/<>/debian/mtr/usr/share/bash-completion/completions' /bin/mkdir -p '/<>/debian/mtr/usr/share/man/man8' /usr/bin/install -c -m 644 ../mtr.8 ../mtr-packet.8 '/<>/debian/mtr/usr/share/man/man8' make[3]: Leaving directory '/<>/mtr' make[2]: Leaving directory '/<>/mtr' dh_auto_install --builddirectory=mtr-tiny --destdir=debian/mtr-tiny cd mtr-tiny && make -j1 install DESTDIR=/<>/debian/mtr-tiny AM_UPDATE_INFO_DIR=no make[2]: Entering directory '/<>/mtr-tiny' make[3]: Entering directory '/<>/mtr-tiny' /bin/mkdir -p '/<>/debian/mtr-tiny/usr/bin' /usr/bin/install -c mtr mtr-packet '/<>/debian/mtr-tiny/usr/bin' make install-exec-hook make[4]: Entering directory '/<>/mtr-tiny' `setcap cap_net_raw+ep /<>/debian/mtr-tiny/usr/bin/mtr-packet` \ || chmod u+s /<>/debian/mtr-tiny/usr/bin/mtr-packet /bin/bash: line 1: setcap: command not found make[4]: Leaving directory '/<>/mtr-tiny' /bin/mkdir -p '/<>/debian/mtr-tiny/usr/share/bash-completion/completions' /usr/bin/install -c -m 644 ../bash-completion/mtr '/<>/debian/mtr-tiny/usr/share/bash-completion/completions' /bin/mkdir -p '/<>/debian/mtr-tiny/usr/share/man/man8' /usr/bin/install -c -m 644 ../mtr.8 ../mtr-packet.8 '/<>/debian/mtr-tiny/usr/share/man/man8' make[3]: Leaving directory '/<>/mtr-tiny' make[2]: Leaving directory '/<>/mtr-tiny' make[1]: Leaving directory '/<>' dh_installdocs -a debian/rules override_dh_installchangelogs-arch make[1]: Entering directory '/<>' dh_installchangelogs -a NEWS make[1]: Leaving directory '/<>' dh_installman -a dh_installman: Cannot find (any matches for) "mtr/mtr.8" (tried in .) dh_installman: Aborting due to earlier error debian/rules:7: recipe for target 'binary-arch' failed make: *** [binary-arch] Error 25 dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 The build was made with "dpkg-buildpackage -B" in my autobuilder but it also fails in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mtr.html [ Note: There has been a recent change in debhelper behaviour, the current behaviour is the intended one. See Bug #903133 for details ]. Thanks. --- End Message --- --- Begin Message --- Source: mtr Source-Version: 0.92-1.1 We believe that the bug you reported is fixed in the latest version of mtr, 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 903...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software
Bug#881835: marked as done (mbr FTBFS on !amd64 !i386: debhelper got stricter)
Your message dated Fri, 10 Aug 2018 05:48:48 + with message-id and subject line Bug#881835: fixed in mbr 1.1.11-5.2 has caused the Debian Bug report #881835, regarding mbr FTBFS on !amd64 !i386: debhelper got stricter 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.) -- 881835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mbr Version: 1.1.11-5.1 Severity: serious Justification: fails to build from source (but built successfully in the past) User: helm...@debian.org Usertags: rebootstrap E.g. mips64el: | dh_installdirs -p mbr-udeb sbin | dh_installdirs: All requested packages have been excluded (e.g. via a Build-Profile). | dh_installdocs -p mbr debian/README-1st.Debian NEWS README AUTHORS | dh_installdocs: Compatibility levels before 9 are deprecated (level 7 in use) | dh_installchangelogs | dh_installchangelogs: Compatibility levels before 9 are deprecated (level 7 in use) | /usr/bin/make install INSTALL_PROGRAM="install -s" | make[1]: Entering directory '/<>' | make[2]: Entering directory '/<>' | make[3]: Entering directory '/<>' | test -z "/<>/debian/mbr//sbin" || mkdir -p -- "/<>/debian/mbr//sbin" | install -s 'install-mbr' '/<>/debian/mbr//sbin/install-mbr' | test -z "/<>/debian/mbr/usr/share/man/man8" || mkdir -p -- "/<>/debian/mbr/usr/share/man/man8" | /usr/bin/install -c -m 644 './install-mbr.8' '/<>/debian/mbr/usr/share/man/man8/install-mbr.8' | make[3]: Leaving directory '/<>' | make[2]: Leaving directory '/<>' | make[1]: Leaving directory '/<>' | cp `pwd`/debian/mbr/sbin/install-mbr `pwd`/debian/mbr-udeb/sbin/ | cp: cannot create regular file '/<>/debian/mbr-udeb/sbin/': No such file or directory | debian/rules:34: recipe for target 'install' failed | make: *** [install] Error 1 | dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/mbr.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/mbr.html This is likely because debhelper became more strict recently. You cannot reproduce this on amd64 or i386 (except by cross building). Helmut --- End Message --- --- Begin Message --- Source: mbr Source-Version: 1.1.11-5.2 We believe that the bug you reported is fixed in the latest version of mbr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 881...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Niels Thykier (supplier of updated mbr 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: Mon, 06 Aug 2018 18:53:12 + Source: mbr Binary: mbr mbr-udeb Architecture: source Version: 1.1.11-5.2 Distribution: unstable Urgency: medium Maintainer: Santiago Garcia Mantinan Changed-By: Niels Thykier Description: mbr- Master Boot Record for IBM-PC compatible computers. mbr-udeb - Master Boot Record for IBM-PC compatible computers (udeb) Closes: 881835 Changes: mbr (1.1.11-5.2) unstable; urgency=medium . * Non-maintainer upload. . [ Simon McVittie ] * Only copy install-mbr to debian/mbr-udeb/sbin if we are going to build the mbr-udeb package, fixing FTBFS on non-x86 architectures. In recent debhelper versions, dh_installdirs does not create directories for binary packages that are not applicable to the current architecture. (Closes: #881835) . [ Niels Thykier ] * Set Rules-Requires-Root (R³) to no. * Replace use of "Priority: extra" with "Priority: optional" as the former is now obsolete and replaced by the latter. * Use Package-Type without the "XC-" prefix as it is no longer required. Checksums-Sha1: eda726dd8b1acd6d5ef2d067ace9f6ff04e142c8 1735 mbr_1.1.11-5.2.dsc cfe0e5db8d8c97ffdc556243ccff7f8db4d99e23 10072 mbr_1.1.11-5.2.diff.gz 4436738582f77b02099446f43951bfe26cb93912 5322 mbr_1.1.11-5.2_source.buildinfo Checksums-Sha256: c453b4c2dc6b727542903c6d2c895e507db3a5c500209e2b68bdf3720d764c1f 1735 mbr_1.1.11-5.2.dsc ef3712820ee91533cc4898aa2ae4439fec7be87443bd9d89737b92288a9cadcf 10072 mbr_1.1.11-5.2.diff.gz
Bug#903182: mtr: FTBFS in buster/sid (dh_installman: Cannot find "mtr/mtr.8")
Samuel Henrique: > Hello Niels, > > I only had the time to look at this now, thanks for the fix, feel free > to upload it now if you rather not wait for the 7 (now 4) days. > > Regards, > Thanks for reviewing. I have uploaded it directly to unstable now. :) Thanks, ~Niels
Bug#905767: emacs25: FTBFS due to test failures on arm64 in a binNMU against new version of libmagick
Niels Thykier writes: > Package: emacs25 > Version: 25.2+1-6+b3 > Severity: serious > Tags: ftbfs > Justification: fails to build from source This should be fixed in emacs 1:25.2+1-9, which hopefully will be able to completely replace emacs25 in sid/buster soon. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
Bug#905811: moria does not trap errors from make
Source: moria Version: 5.6.debian.1-2 Severity: serious Justification: debian policy 4.6 The Debian policy requires that a build aborts on errors rather than continuing. The moria package is interesting in this regard: ( cd build ; $(MAKE) ) It tries to cd to build and then runs make wherever it lands. As it happens, the clean target removes the build folder. So the cd fails and it runs the build directly in the source directory. That's actually the correct thing to do as the upstream Makefile's default target insists on setting up the build directory. The cd call can only succeed after setting up the build directory and nothing else in debian/rules takes care of that. I therefore think that that this chaining (that happens in more places) is in violation of the Debian policy section 4.6. It also is grossly misleading and makes contributing to the package unnecessarily difficult. Helmut
Bug#897498: marked as done (2ping: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13)
Your message dated Fri, 10 Aug 2018 04:03:51 +
with message-id
and subject line Bug#897498: fixed in 2ping 4.1.2-1
has caused the Debian Bug report #897498,
regarding 2ping: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.6
returned exit code 13
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.)
--
897498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: 2ping
Version: 4.1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with=python3,systemd --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.6 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.6_2ping/build/twoping
> copying twoping/utils.py ->
> /<>/.pybuild/cpython3_3.6_2ping/build/twoping
> copying twoping/best_poller.py ->
> /<>/.pybuild/cpython3_3.6_2ping/build/twoping
> copying twoping/packets.py ->
> /<>/.pybuild/cpython3_3.6_2ping/build/twoping
> copying twoping/__init__.py ->
> /<>/.pybuild/cpython3_3.6_2ping/build/twoping
> copying twoping/monotonic_clock.py ->
> /<>/.pybuild/cpython3_3.6_2ping/build/twoping
> copying twoping/crc32.py ->
> /<>/.pybuild/cpython3_3.6_2ping/build/twoping
> copying twoping/cli.py ->
> /<>/.pybuild/cpython3_3.6_2ping/build/twoping
> copying twoping/args.py ->
> /<>/.pybuild/cpython3_3.6_2ping/build/twoping
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: python3.6 setup.py test
> running test
> running egg_info
> creating 2ping.egg-info
> writing 2ping.egg-info/PKG-INFO
> writing dependency_links to 2ping.egg-info/dependency_links.txt
> writing entry points to 2ping.egg-info/entry_points.txt
> writing top-level names to 2ping.egg-info/top_level.txt
> writing manifest file '2ping.egg-info/SOURCES.txt'
> reading manifest file '2ping.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file '2ping.egg-info/SOURCES.txt'
> running build_ext
> test_encrypt (tests.test_cli.TestCLIEncryptAES256) ... skipped 'PyCrypto
> required'
> test_hmac (tests.test_cli.TestCLIHMACCRC32) ... ok
> test_hmac (tests.test_cli.TestCLIHMACMD5) ... ok
> test_hmac (tests.test_cli.TestCLIHMACSHA1) ... ok
> test_hmac (tests.test_cli.TestCLIHMACSHA256) ... ok
> test_hmac (tests.test_cli.TestCLIHMACSHA512) ... ok
> test_adaptive (tests.test_cli.TestCLIStandard) ... ok
> test_flood (tests.test_cli.TestCLIStandard) ... ok
> test_monotonic_clock (tests.test_cli.TestCLIStandard) ... ok
> test_notice (tests.test_cli.TestCLIStandard) ... ok
> test_notice_utf8 (tests.test_cli.TestCLIStandard) ... ERROR
> test_random (tests.test_cli.TestCLIStandard) ... ok
> test_time (tests.test_cli.TestCLIStandard) ... ok
> test_twoping_checksum_hello (tests.test_utils.TestUtils) ... ok
> test_twoping_checksum_iter (tests.test_utils.TestUtils) ... ok
> test_twoping_checksum_junk (tests.test_utils.TestUtils) ... ok
> test_twoping_checksum_packet (tests.test_utils.TestUtils) ... ok
> test_encrypted_encrypt_decrypt (tests.test_packets.TestPacketsOpcodes) ...
> skipped 'PyCrypto required'
> test_extended_batteries_dump (tests.test_packets.TestPacketsOpcodes) ... ok
> test_extended_batteries_load (tests.test_packets.TestPacketsOpcodes) ... ok
> test_extended_monotonicclock_dump (tests.test_packets.TestPacketsOpcodes) ...
> ok
> test_extended_monotonicclock_load (tests.test_packets.TestPacketsOpcodes) ...
> ok
> test_extended_notice (tests.test_packets.TestPacketsOpcodes) ... ok
> test_extended_random_dump (tests.test_packets.TestPacketsOpcodes) ... ok
> test_extended_random_load (tests.test_packets.TestPacketsOpcodes) ... ok
> test_extended_unknown (tests.test_packets.TestPacketsOpcodes) ... ok
> test_extended_version (tests.test_packets.TestPacketsOpcodes) ... ok
> test_extended_wallclock_dump (tests.test_packets.TestPacketsOpcodes) ... ok
> test_extended_wallclock_load (tests.test_packets.TestPacketsOpcodes) ... ok
> test_opcode_courtesy_expiration (tests.test_packets.TestPacketsOpcodes) ... ok
> test_opcode_encrypted (tests.test_packets.TestPacketsOpcodes) ... ok
> test_opcode_extended (tests.test_packets.TestPacketsOpcodes) ... ok
>
Processed: tagging 897806
Processing commands for cont...@bugs.debian.org: > tags 897806 + patch Bug #897806 [src:lmms] lmms: ftbfs with GCC-8 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 897806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905674: undistributable
Dear Ole (and others potentially interested in having GNU Parallel in
Debian's and derivatives' repositories),
I don't know if you have been following the emails on the Debian BTS
regarding GNU Parallel having restrictions regardings its distribution etc.
Since this issue has surfaced itself once again, but now in a more intense
manner, I believe that, if you have not yet been informed, you may want to
give your opinion (and I will decide how I should follow my maintainership
within the constraints of your software and the contraints of Debian).
Thanks,
Rogério Brito...
On Aug 08 2018, Adam Borowski wrote:
> Actually, it seems to me it's not even distributable.
>
> The wording sounds like a requirement rather than something non-mandatory --
> reinforced by providing the alternative of paying €1. Yet the license
> is GPL3+, which expressly forbids additional fees. This is even described
> in FSF's GPL FAQ:
> https://www.gnu.org/licenses/gpl-faq.en.html#RequireCitation
>
> Thus, the copyright holder can distribute this software, but no one else
> can.
>
> As the requirement is not a part of the license, we could just remove the
> demand nagware from the code. But alas, the upstream (Ole Tange) threatened
> legal action if you do so without renaming the package. And it doesn't seem
> to be just hot wind, as he registered it: US trademark number 87867112,
> filed Apr 07, 2018.
>
> Multiple people tried persuading the upstream to drop this requirement,
> without success. Thus, diplomacy doesn't appear to be likely to help,
> although letting rms know may work (this package has been blessed as an
> official GNU one, obviously before the requirement was added).
>
> Thus, only options I see are:
> * renaming the package and removing offending code, or
> * complete removal
>
>
> Meow!
> --
> // If you believe in so-called "intellectual property", please immediately
> // cease using counterfeit alphabets. Instead, contact the nearest temple
> // of Amon, whose priests will provide you with scribal services for all
> // your writing needs, for Reasonable And Non-Discriminatory prices.
>
--
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
Bug#897857: marked as done (setools: ftbfs with GCC-8)
Your message dated Fri, 10 Aug 2018 02:36:36 +
with message-id
and subject line Bug#897857: fixed in swig 3.0.12-1.2
has caused the Debian Bug report #897857,
regarding setools: ftbfs with GCC-8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
897857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:setools
Version: 4.1.1-3
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.
The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/setools_4.1.1-3_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.
To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-8/porting_to.html
[...]
copying setoolsgui/apol/netifconquery.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/exclude_types.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/choose_analysis.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/commonquery.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/boolquery.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/genfsconquery.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/permmapping.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/categoryquery.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/objclassquery.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/typeattrquery.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/typequery.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/boundsquery.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/apol.qhc ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/apol.qch ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
running build_ext
running build_yacc
Generating parser
bison -y -d libqpol/policy_parse.y -o libqpol/policy_parse.c
running build_lex
Generating scanner
flex -o libqpol/policy_scan.c libqpol/policy_scan.l
building 'setools.policyrep._qpol' extension
swigging setools/policyrep/qpol.i to setools/policyrep/qpol_wrap.c
swig -python -Ilibqpol/include -o setools/policyrep/qpol_wrap.c
setools/policyrep/qpol.i
creating build
creating build/temp.linux-amd64-3.6
creating build/temp.linux-amd64-3.6/setools
creating build/temp.linux-amd64-3.6/setools/policyrep
creating build/temp.linux-amd64-3.6/libqpol
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wno-sign-compare -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-Ilibqpol -Ilibqpol/include -I/usr/include/python3.6m -c
setools/policyrep/qpol_wrap.c -o
build/temp.linux-amd64-3.6/setools/policyrep/qpol_wrap.o -Werror -Wextra
-Waggregate-return -Wfloat-equal -Wformat -Wformat=2 -Winit-self
-Wmissing-format-attribute -Wmissing-include-dirs -Wnested-externs
-Wold-style-definition -Wpointer-arith -Wredundant-decls -Wstrict-prototypes
-Wunknown-pragmas -Wwrite-strings -Wno-missing-field-initializers
-Wno-unused-parameter -Wno-cast-qual -Wno-shadow -Wno-unreachable-code
-fno-exceptions
setools/policyrep/qpol_wrap.c:1819:23: error: cast between incompatible
function types from 'PyObject * (*)(PyObject *)' {aka 'struct _object *
(*)(struct _object *)'} to 'PyObject * (*)(PyObject *, PyObject *)' {aka
'struct _object * (*)(struct _object *, struct _object *)'}
[-Werror=cast-function-type]
{(char *)"disown",
Bug#900420: marked as done (setools: ftbfs with GCC-8)
Your message dated Fri, 10 Aug 2018 02:36:36 +
with message-id
and subject line Bug#897857: fixed in swig 3.0.12-1.2
has caused the Debian Bug report #897857,
regarding setools: ftbfs with GCC-8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
897857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:setools
Version: 4.1.1-3
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.
The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/setools_4.1.1-3_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.
To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-8/porting_to.html
[...]
copying setoolsgui/apol/netifconquery.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/exclude_types.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/choose_analysis.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/commonquery.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/boolquery.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/genfsconquery.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/permmapping.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/categoryquery.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/objclassquery.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/typeattrquery.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/typequery.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/boundsquery.ui ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/apol.qhc ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
copying setoolsgui/apol/apol.qch ->
/<>/.pybuild/cpython3_3.6/build/setoolsgui/apol
running build_ext
running build_yacc
Generating parser
bison -y -d libqpol/policy_parse.y -o libqpol/policy_parse.c
running build_lex
Generating scanner
flex -o libqpol/policy_scan.c libqpol/policy_scan.l
building 'setools.policyrep._qpol' extension
swigging setools/policyrep/qpol.i to setools/policyrep/qpol_wrap.c
swig -python -Ilibqpol/include -o setools/policyrep/qpol_wrap.c
setools/policyrep/qpol.i
creating build
creating build/temp.linux-amd64-3.6
creating build/temp.linux-amd64-3.6/setools
creating build/temp.linux-amd64-3.6/setools/policyrep
creating build/temp.linux-amd64-3.6/libqpol
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wno-sign-compare -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-Ilibqpol -Ilibqpol/include -I/usr/include/python3.6m -c
setools/policyrep/qpol_wrap.c -o
build/temp.linux-amd64-3.6/setools/policyrep/qpol_wrap.o -Werror -Wextra
-Waggregate-return -Wfloat-equal -Wformat -Wformat=2 -Winit-self
-Wmissing-format-attribute -Wmissing-include-dirs -Wnested-externs
-Wold-style-definition -Wpointer-arith -Wredundant-decls -Wstrict-prototypes
-Wunknown-pragmas -Wwrite-strings -Wno-missing-field-initializers
-Wno-unused-parameter -Wno-cast-qual -Wno-shadow -Wno-unreachable-code
-fno-exceptions
setools/policyrep/qpol_wrap.c:1819:23: error: cast between incompatible
function types from 'PyObject * (*)(PyObject *)' {aka 'struct _object *
(*)(struct _object *)'} to 'PyObject * (*)(PyObject *, PyObject *)' {aka
'struct _object * (*)(struct _object *, struct _object *)'}
[-Werror=cast-function-type]
{(char *)"disown",
Bug#903182: mtr: FTBFS in buster/sid (dh_installman: Cannot find "mtr/mtr.8")
Hello Niels, I only had the time to look at this now, thanks for the fix, feel free to upload it now if you rather not wait for the 7 (now 4) days. Regards, -- Samuel Henrique
Bug#897857:
On Fri, Aug 10, 2018 at 10:36:59AM +1200, Michael Hudson-Doyle wrote: > On Fri, 10 Aug 2018 at 09:37, Olly Betts wrote: > > I actually addressed this upstream in SWIG back in May (by fixing the > > generated code rather than disabling the warning), but there's not > > been a release in a while. I'll take a look and see if the fix can be > > backported to the Debian package. The potential problem is that it was > > after clean-up of support for older Python versions, and it seems > > unhelpful in the wider context for the Debian swig package to generate > > code which supports a narrower range of Python versions than the > > corresponding upstream SWIG version. > > Hm yes. On some level it would be fine to only support versions of Python > supported by Debian, but on another that would be a bit hostile. Indeed. The patch needed some adjustment, but that wasn't as painful as I feared. I can't easily test it with all the Python versions which SWIG claims to support (which unbelievably is still 2.0 and up in 1.3.x) but the older of those don't define METH_O so don't take most of the codepaths this changes anyway. I've confirmed my changes address the issue when running the upstream testsuite with GCC 8 and current Python, and fixed two other new GCC 8 warnings which most SWIG-generated Python bindings will trigger. Cheers, Olly
Processed: swig: diff for NMU version 3.0.12-1.2
Processing control commands: > tags 897857 + patch Bug #897857 [swig] setools: ftbfs with GCC-8 Bug #900420 [swig] setools: ftbfs with GCC-8 Added tag(s) patch. Added tag(s) patch. > tags 897857 + pending Bug #897857 [swig] setools: ftbfs with GCC-8 Bug #900420 [swig] setools: ftbfs with GCC-8 Added tag(s) pending. Added tag(s) pending. -- 897857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897857 900420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897857: swig: diff for NMU version 3.0.12-1.2
Control: tags 897857 + patch
Control: tags 897857 + pending
Dear maintainer,
I've prepared an NMU for swig (versioned as 3.0.12-1.2) and uploaded it.
NMU diff is attached.
Cheers,
Olly
diff -Nru swig-3.0.12/debian/changelog swig-3.0.12/debian/changelog
--- swig-3.0.12/debian/changelog 2018-06-18 00:25:41.0 +1200
+++ swig-3.0.12/debian/changelog 2018-08-10 12:48:36.0 +1200
@@ -1,3 +1,15 @@
+swig (3.0.12-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * python-fix-function-cast-warnings.patch: Fix GCC8 warnings in generated
+Python code. (Closes: #897857)
+ * python-fix-gcc8-strncpy-warning.patch: Fix more GCC8 warnings in generated
+Python code.
+ * fix-gcc8-memset-warnings.patch: Fix GCC8 warnings in generated code for
+various languages.
+
+ -- Olly Betts Fri, 10 Aug 2018 12:48:36 +1200
+
swig (3.0.12-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru swig-3.0.12/debian/patches/fix-gcc8-memset-warnings.patch swig-3.0.12/debian/patches/fix-gcc8-memset-warnings.patch
--- swig-3.0.12/debian/patches/fix-gcc8-memset-warnings.patch 1970-01-01 12:00:00.0 +1200
+++ swig-3.0.12/debian/patches/fix-gcc8-memset-warnings.patch 2018-08-10 12:48:36.0 +1200
@@ -0,0 +1,212 @@
+Description: Fix new GCC8 warnings in generated code
+ Backported from upstream git master based on the following ranges of commits:
+ git diff 74345c92^..b229d92f
+ git diff dd26e8a0^..a67eff0a
+ git diff ef1351c7..7ac21f37
+Author: Mike Romberg
+Origin: upstream
+Last-Updated: 2018-08-10
+
+--- a/Lib/python/pycontainer.swg
b/Lib/python/pycontainer.swg
+@@ -434,8 +434,8 @@
+ {
+ swig::SwigVar_PyObject item = PySequence_GetItem(_seq, _index);
+ try {
+- return swig::as(item, true);
+- } catch (std::exception& e) {
++ return swig::as(item);
++ } catch (const std::invalid_argument& e) {
+ char msg[1024];
+ sprintf(msg, "in sequence element %d ", (int)_index);
+ if (!PyErr_Occurred()) {
+--- a/Lib/python/pystdcommon.swg
b/Lib/python/pystdcommon.swg
+@@ -107,14 +107,14 @@
+
+ template
+ struct traits_as {
+-static Type as(PyObject *obj, bool throw_error) {
++static Type as(PyObject *obj) {
+ Type v;
+ int res = asval(obj, );
+ if (!obj || !SWIG_IsOK(res)) {
+ if (!PyErr_Occurred()) {
+ ::%type_error(swig::type_name());
+ }
+- if (throw_error) throw std::invalid_argument("bad type");
++ throw std::invalid_argument("bad type");
+ }
+ return v;
+ }
+@@ -122,7 +122,7 @@
+
+ template
+ struct traits_as {
+-static Type as(PyObject *obj, bool throw_error) {
++static Type as(PyObject *obj) {
+ Type *v = 0;
+ int res = (obj ? traits_asptr::asptr(obj, ) : SWIG_ERROR);
+ if (SWIG_IsOK(res) && v) {
+@@ -134,21 +134,17 @@
+ return *v;
+ }
+ } else {
+- // Uninitialized return value, no Type() constructor required.
+- static Type *v_def = (Type*) malloc(sizeof(Type));
+ if (!PyErr_Occurred()) {
+ %type_error(swig::type_name());
+ }
+- if (throw_error) throw std::invalid_argument("bad type");
+- memset(v_def,0,sizeof(Type));
+- return *v_def;
++ throw std::invalid_argument("bad type");
+ }
+ }
+ };
+
+ template
+ struct traits_as {
+-static Type* as(PyObject *obj, bool throw_error) {
++static Type* as(PyObject *obj) {
+ Type *v = 0;
+ int res = (obj ? traits_asptr::asptr(obj, ) : SWIG_ERROR);
+ if (SWIG_IsOK(res)) {
+@@ -157,15 +153,14 @@
+ if (!PyErr_Occurred()) {
+ %type_error(swig::type_name());
+ }
+- if (throw_error) throw std::invalid_argument("bad type");
+- return 0;
++ throw std::invalid_argument("bad type");
+ }
+ }
+ };
+
+ template
+- inline Type as(PyObject *obj, bool te = false) {
+-return traits_as::category>::as(obj, te);
++ inline Type as(PyObject *obj) {
++return traits_as::category>::as(obj);
+ }
+
+ template
+--- a/Lib/ruby/rubycontainer.swg
b/Lib/ruby/rubycontainer.swg
+@@ -183,8 +183,8 @@
+ {
+ VALUE item = rb_ary_entry(_seq, _index );
+ try {
+- return swig::as(item, true);
+- } catch (std::exception& e) {
++ return swig::as(item);
++ } catch (const std::invalid_argument& e) {
+ char msg[1024];
+ sprintf(msg, "in sequence element %d ", _index);
+ VALUE lastErr = rb_gv_get("$!");
+@@ -926,7 +926,7 @@
+ VALUE elem = argv[0];
+ int idx = 0;
+ try {
+- Sequence::value_type val = swig::as( elem, true );
++ Sequence::value_type val = swig::as( elem );
+ if ( i >= len ) {
+ $self->resize(i-1, val);
+ return $self;
+@@ -943,7 +943,7 @@
+ }
+
+ }
+- catch( std::invalid_argument )
++ catch( const std::invalid_argument & )
+ {
+ rb_raise( rb_eArgError, "%s",
+ Ruby_Format_TypeError( "",
+@@ -967,10 +967,10 @@
+ Sequence::iterator start = $self->begin();
+ VALUE elem = argv[idx];
+ try {
+- Sequence::value_type val = swig::as(
Processed: Re: Bug#905130: hedgewars: FTBFS on armhf (tests fails))
Processing commands for cont...@bugs.debian.org:
> reopen 905130
Bug #905130 {Done: Gianfranco Costamagna }
[src:hedgewars] hedgewars: FTBFS on armhf (tests fails)
Bug reopened
Ignoring request to alter fixed versions of bug #905130 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
905130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#905130: hedgewars: FTBFS on armhf (tests fails))
reopen 905130 thanks Hi Lisandro, I was going to make a report about hedgewars myself, as it seems that this package is one of the factors blocking the Qt transition (see https://release.debian.org/transitions/html/qtbase-abi-5-11-0.html). And then I saw this bug report which looks like it was mistakenly closed before being fixed. Thank you for taking responsibility for this - I do appreciate it! I'm reopening the bug report in the meantime so that others can also see it is still live. When you have taken care of it and either fixed the bug or removed hedgewars from armhf, then please feel free to close it again. Best wishes, Julian On Thu, Aug 02, 2018 at 03:30:03PM +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the src:hedgewars package: > > #905130: hedgewars: FTBFS on armhf (tests fails) > > It has been closed by Gianfranco Costamagna . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Gianfranco Costamagna > by > replying to this email. > > > -- > 905130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905130 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > Date: Thu, 2 Aug 2018 17:26:29 +0200 > From: Gianfranco Costamagna > Subject: hedgewars: FTBFS on armhf (tests fails) > To: 905130-d...@bugs.debian.org > > I'll take care of this, I already reported the bug, but I'll probably ask to > remove hedgewars > from armhf. > > G. > Date: Tue, 31 Jul 2018 11:29:49 -0300 > From: Lisandro Damián Nicanor Pérez Meyer > Subject: hedgewars: FTBFS on armhf (tests fails) > To: Debian Bug Tracking System > > Source: hedgewars > Version: 0.9.24.1-dfsg-4 > Severity: serious > Justification: FTBFS > > Hi! durent the ongoing Qt transition your package FTBFS on armhf due to tests > failures. > > 5/7 Test #1: drillrockets_boom.lua Passed8.23 sec > 6/7 Test #2: drillrockets_drill.lua ... Passed 14.54 sec > 7/7 Test #7: twothousandmines.lua . Passed 82.14 sec > > 86% tests passed, 1 tests failed out of 7 > > Total Test time (real) = 84.47 sec > > The following tests FAILED: > 6 - stuckcake.lua (Failed) > Errors while running CTest > make[1]: *** [Makefile:144: test] Error 8 > make[1]: Leaving directory '/<>/obj-arm-linux-gnueabihf' > dh_auto_test: cd obj-arm-linux-gnueabihf && make -j4 test ARGS\+=-j4 returned > exit code 2 > make: *** [debian/rules:4: build-arch] Error 2 > > Regards, Lisandro.
Bug#905130: hedgewars: FTBFS on armhf (tests fails))
Hi Julian! On Thu, 9 Aug 2018 at 20:56, Julian Gilbey wrote: > > reopen 905130 > thanks > > Hi Lisandro, > > I was going to make a report about hedgewars myself, as it seems that > this package is one of the factors blocking the Qt transition (see > https://release.debian.org/transitions/html/qtbase-abi-5-11-0.html). > And then I saw this bug report which looks like it was mistakenly > closed before being fixed. > > Thank you for taking responsibility for this - I do appreciate it! > I'm reopening the bug report in the meantime so that others can also > see it is still live. When you have taken care of it and either fixed > the bug or removed hedgewars from armhf, then please feel free to > close it again. Thanks, but I was not the one who closed it! ;-)
Bug#905735: emacs-goodies-el: postinst failure due to missing lcomp.el
On Wed, 8 Aug 2018 22:50:16 -0400, Nicholas D Steeves wrote: [...] > It is highly probable that this bug occurred due to breaking changes > introduced with emacsen-common 3.0.2, rather than from removal of this > file. But I have emacsen-common 2.0.8 installed as per the report. >> -- System Information: Debian Release: buster/sid APT prefers testing >> APT policy: (990, 'testing'), (300, 'unstable') Architecture: amd64 >> (x86_64) Foreign Architectures: i386 > I see you're mixing testing and unstable. Are you willing to test an > upgrade to unversioned emacs? It would be a valuable data-point to > solving this emacs-goodies-el bug! If so, please use the following > procedure: > # This bit returns goodies to the state it was for Stretch > apt purge --autoremove emacs-goodies-el > wget > https://snapshot.debian.org/archive/debian/20161122T032842Z/pool/main/e/emacs-goodies-el/emacs-goodies-el_36.3_all.deb > # this next line might be paranoia > apt autoremove --purge > # and finally install the package > dpkg -i emacs-goodies-el_36.3_all.deb > # This installs emacs-goodies-el from stretch, and will pull in the > new unversioned emacs. Please note the list of packages, in case you > need to roll back. > apt install emacs-goodies-el=40.1 The last step failed for me: ------ Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: emacs-goodies-el : Depends: emacsen-common (>= 3.0.2) but 2.0.8 is to be installed Recommends: elpa-bm but it is not installable E: Unable to correct problems, you have held broken packages. --- --- But succeeded by letting it choose my default testing version of the package (40.0): --- --- $ sudo aptitude safe-upgrade The following packages will be upgraded: emacs-goodies-el 1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/96.4 kB of archives. After unpacking 3,177 kB will be freed. Do you want to continue? [Y/n/?] y Reading changelogs... Done (Reading database ... 682251 files and directories currently installed.) Preparing to unpack .../emacs-goodies-el_40.0_all.deb ... Remove emacs-goodies-el for emacs25 remove/emacs-goodies-el: purging byte-compiled files for emacs25 Unpacking emacs-goodies-el (40.0) over (36.3) ... Processing triggers for install-info (6.5.0.dfsg.1-4) ... Setting up emacs-goodies-el (40.0) ... Install emacsen-common for emacs25 emacsen-common: Handling install of emacsen flavor emacs25 Install emacs-goodies-el for emacs25 install/emacs-goodies-el: Handling emacs25, logged in /tmp/elc_b2o0sx.log Building autoloads for emacs25 in /usr/share/emacs25/site-lisp/emacs-goodies-el install/emacs-goodies-el: Deleting /tmp/elc_b2o0sx.log Current status: 0 (-1) upgradable. --- --- Thank you for your quick follow-up and hopefully this is useful. -- Seb
Bug#897857:
On Fri, 10 Aug 2018 at 09:37, Olly Betts wrote: > On Thu, Aug 02, 2018 at 09:23:26PM +1200, Michael Hudson-Doyle wrote: > > upstream just "fixed" this by disabling the warning, fwiw > > This bug was reported in setools but reassigned to swig - I think you > must mean "setools" by "upstream" there? > Ah yes. Sorry for the lack of clarity. > I actually addressed this upstream in SWIG back in May (by fixing the > generated code rather than disabling the warning), but there's not > been a release in a while. I'll take a look and see if the fix can be > backported to the Debian package. The potential problem is that it was > after clean-up of support for older Python versions, and it seems > unhelpful in the wider context for the Debian swig package to generate > code which supports a narrower range of Python versions than the > corresponding upstream SWIG version. > Hm yes. On some level it would be fine to only support versions of Python supported by Debian, but on another that would be a bit hostile. > Ignoring the warning is reasonable. The code in question does invoke > undefined behaviour, but it should be safe in practice with the calling > conventions used on Linux. > I agree. > Compiling packages with -Werror seems unwise in general, but I really > wouldn't recommend compiling SWIG-generated code in packages with > -Werror. > Totally agree! It's fine to use it during development but using it in distributed source is just a timebomb. Cheers, mwh
Bug#905140: [Pkg-cmake-team] Bug#905140: Bug #905140 in cmake marked as pending
Hi, On 09.08.2018 22:38, Svante Signell wrote: Hello, What about the bugs with patches, e.g. for Hurd and kFreeBSD. Still somebody needs to NMU this package... You don't seem interested in fixing bugs to your package, except RC ones. Not the ideal way Debian maintainers should work with their packages... Instead of making wild accusations I suggest that instead you respond to questions on bugs you opened. I'm not interested in maintaining patches for things that clearly belong upstream. Once upstream has reviewed the changes I'm happy to cherry-pick them. #905138 on 2018-08-01: Have you forwarded your non-packaging changes upstream to cmake / libuv (#905140 is already fixed in 3.12)? I really don't want to carry those as patches. The same applies to #900240 Cheers, Felix
Bug#897866: marked as done (snapd-glib: ftbfs with GCC-8)
Your message dated Thu, 09 Aug 2018 22:05:12 + with message-id and subject line Bug#897866: fixed in snapd-glib 1.42-1 has caused the Debian Bug report #897866, regarding snapd-glib: ftbfs with GCC-8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 897866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897866 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:snapd-glib Version: 1.38-1 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-8 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The severity of this report will be raised before the buster release. The full build log can be found at: http://aws-logs.debian.net/2018/05/01/gcc8/snapd-glib_1.38-1_unstable_gcc8.log.gz The last lines of the build log are at the end of this report. To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-8/porting_to.html [...] make[3]: Leaving directory '/<>/doc' make[2]: Leaving directory '/<>/doc' make[2]: Entering directory '/<>' make[3]: Entering directory '/<>' make[3]: Nothing to be done for 'install-exec-am'. make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/<>' make[2]: Leaving directory '/<>' make[1]: Leaving directory '/<>' dh_install -a dh_installdocs -a dh_installchangelogs -a dh_perl -a dh_link -a dh_strip_nondeterminism -a dh_compress -a dh_fixperms -a dh_missing -a dh_strip -a debian/rules override_dh_makeshlibs make[1]: Entering directory '/<>' dh_makeshlibs -V -- -c4 dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libsnapd-qt1/DEBIAN/symbols doesn't match completely debian/libsnapd-qt1.symbols --- debian/libsnapd-qt1.symbols (libsnapd-qt1_1.38-1_amd64) +++ dpkg-gensymbolslnDkmR 2018-05-02 12:04:06.255824472 + @@ -275,7 +275,7 @@ (c++)"QSnapdUserInformation::username() const@Base" 1.25 (c++)"QSnapdUserInformation::~QSnapdUserInformation()@Base" 1.25 (c++)"QSnapdWrappedObject::~QSnapdWrappedObject()@Base" 1.5 - (c++|optional)"QString::QString(QString const&)@Base" 0 +#MISSING: 1.38-1# (c++|optional)"QString::QString(QString const&)@Base" 0 (c++|optional)"QString::toStdString[abi:cxx11]() const@Base" 0 (c++|optional)"QString::~QString()@Base" 0 (c++|regex)"^.*::metaObject\(\) const@Base$" 0 @@ -291,6 +291,9 @@ (c++|regex)"^typeinfo for .*@Base$" 0 (c++|regex)"^typeinfo name for .*@Base$" 0 (c++|regex)"^vtable for .*$" 0 + _Z27qRegisterNormalizedMetaTypeIP14QSnapdAuthDataEiRK10QByteArrayPT_N9QtPrivate21MetaTypeDefinedHelperIS5_Xaasr12QMetaTypeId2IS5_E7DefinedntsrSA_9IsBuiltInEE11DefinedTypeE@Base 1.38-1 + _Z27qRegisterNormalizedMetaTypeIP21QSnapdUserInformationEiRK10QByteArrayPT_N9QtPrivate21MetaTypeDefinedHelperIS5_Xaasr12QMetaTypeId2IS5_E7DefinedntsrSA_9IsBuiltInEE11DefinedTypeE@Base 1.38-1 + _Z27qRegisterNormalizedMetaTypeIP23QSnapdSystemInformationEiRK10QByteArrayPT_N9QtPrivate21MetaTypeDefinedHelperIS5_Xaasr12QMetaTypeId2IS5_E7DefinedntsrSA_9IsBuiltInEE11DefinedTypeE@Base 1.38-1 (c++)"login(QString const&, QString const&)@Base" 1.8 (c++)"login(QString const&, QString const&, QString const&)@Base" 0 (optional)stream_wrapper_get_type@Base 1.9 dh_makeshlibs: failing due to earlier errors make[1]: *** [debian/rules:12: override_dh_makeshlibs] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:6: binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 --- End Message --- --- Begin Message --- Source: snapd-glib Source-Version: 1.42-1 We believe that the bug you reported is fixed in the latest version of snapd-glib, 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#898113: ltrace crashes and hangs on armhf
[Christoph Biedl > Tried to handle this bug but it seems this fix doesn't help - and > honestly I fail to see how adding a definition in > sysdeps/linux-gnu/arm/plt.c should help against the problem. I tested the patch, and can confirm that it did not change anything on armhf (abel.debian.org). I suspect the correct fix for Debian is to add a configure test to detect when PTRACE_SINGLESTEP is not supported, and ask ftpmasters to remove the binary packages from all arm architectures. The alternative is to rewrite ltrace to use a different kernel mechanism for tracing, and that is more than one can ask of the Debian package maintainer. :) I found this in NEWS in the source tarball: *** [arm] Tracing is not supported at all on ARM ltrace might work on older kernels, but no attempt was made to fully support it. Newer kernels don't support PTRACE_SINGLESTEP, which ltrace depends on. Before singlestepping is implemented in software, ARM is considered unsupported. It seem prettly clear to me that until arm handle PTRACE_SINGLESTEP, ltrace will not work on arm. Note, the readdir_r() patch is already part of the ltrace package, applied using debian/patches/deprecated-readdir_r.diff. -- Happy hacking Petter Reinholdtsen
Bug#897857:
On Thu, Aug 02, 2018 at 09:23:26PM +1200, Michael Hudson-Doyle wrote: > upstream just "fixed" this by disabling the warning, fwiw This bug was reported in setools but reassigned to swig - I think you must mean "setools" by "upstream" there? I actually addressed this upstream in SWIG back in May (by fixing the generated code rather than disabling the warning), but there's not been a release in a while. I'll take a look and see if the fix can be backported to the Debian package. The potential problem is that it was after clean-up of support for older Python versions, and it seems unhelpful in the wider context for the Debian swig package to generate code which supports a narrower range of Python versions than the corresponding upstream SWIG version. Ignoring the warning is reasonable. The code in question does invoke undefined behaviour, but it should be safe in practice with the calling conventions used on Linux. Compiling packages with -Werror seems unwise in general, but I really wouldn't recommend compiling SWIG-generated code in packages with -Werror. We do try upstream to keep the generated code warning-free, but it's common for new compiler versions to result in new warnings, and there are cases where it's hard to avoid the warnings (indeed even after my fix you can still get this warning when keyword argument support is enabled, because the Python C API inherently relies on casting function pointers to a different type of function pointer when METH_KEYWORD is used). Cheers, Olly
Bug#901413: marked as done (mnemosyne: Mnemosyne 2.6 does not find cheroot module)
Your message dated Thu, 09 Aug 2018 21:18:52 + with message-id and subject line Bug#901413: fixed in mnemosyne 2.6.1+ds-1 has caused the Debian Bug report #901413, regarding mnemosyne: Mnemosyne 2.6 does not find cheroot module 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.) -- 901413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901413 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mnemosyne Version: 2.6+ds-1 Severity: serious Justification: Policy 3.5 Dear Maintainer, when starting Mnemosyne 2.6 it immediately exits with the following error message: ---8<8<8<8<--- Log body An unexpected error has occurred. Please forward the following info to the developers: Traceback (innermost last): File "/usr/bin/mnemosyne", line 262, in debug_file=options.debug_file) File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py", line 200, in initialise self.activate_components() File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py", line 296, in activate_components sync_server.activate() File "/usr/lib/python3/dist-packages/mnemosyne/pyqt_ui/qt_sync_server.py", line 196, in activate component_manager=self.component_manager) File "/usr/lib/python3/dist-packages/mnemosyne/pyqt_ui/qt_sync_server.py", line 67, in __init__ super().__init__(ui=self, **kwds) File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/sync_server.py", line 31, in __init__ port=config["sync_server_port"], **kwds) File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/component.py", line 57, in __init__ super().__init__(**kwds) # For parent classes other than 'Object'. File "/usr/lib/python3/dist-packages/openSM2sync/server.py", line 98, in __init__ from cheroot import wsgi ModuleNotFoundError: No module named 'cheroot' An unexpected error has occurred. Please forward the following info to the developers: Traceback (innermost last): File "/usr/bin/mnemosyne", line 262, in debug_file=options.debug_file) File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py", line 200, in initialise self.activate_components() File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py", line 296, in activate_components sync_server.activate() File "/usr/lib/python3/dist-packages/mnemosyne/pyqt_ui/qt_sync_server.py", line 196, in activate component_manager=self.component_manager) File "/usr/lib/python3/dist-packages/mnemosyne/pyqt_ui/qt_sync_server.py", line 67, in __init__ super().__init__(ui=self, **kwds) File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/sync_server.py", line 31, in __init__ port=config["sync_server_port"], **kwds) File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/component.py", line 57, in __init__ super().__init__(**kwds) # For parent classes other than 'Object'. File "/usr/lib/python3/dist-packages/openSM2sync/server.py", line 98, in __init__ from cheroot import wsgi ModuleNotFoundError: No module named 'cheroot' --->8>8>8>8--- This is doe to the missing cheroot Python package. See also this discussion upstream: https://groups.google.com/d/topic/mnemosyne-proj-users/mcuTpPIH61k/discussion Currently, we do not have packaged cheroot in Debian. To resolve this bug, we need to create a python3-cheroot package in Debian and make mnemosyne depend on it. Cheroot can be obtained from https://pypi.org/project/Cheroot/ Best regards, Felix -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mnemosyne depends on: ii libjs-sphinxdoc 1.7.4-1 ii libqt5sql5-sqlite 5.10.1+dfsg-7 ii python3 3.6.5-3 ii python3-cherrypy3 8.9.1-2 ii python3-matplotlib 2.2.2-4 ii python3-pyqt5 5.10.1+dfsg-2 ii python3-pyqt5.qtsql 5.10.1+dfsg-2 ii python3-pyqt5.qtwebchannel 5.10.1+dfsg-2 ii python3-pyqt5.qtwebengine 5.10.1+dfsg-2 ii python3-webob 1:1.7.3-2 mnemosyne recommends no packages.
Bug#903181: marked as done (mnemosyne: FTBFS in buster/sid (dh_installdocs: Cannot find "README"))
Your message dated Thu, 09 Aug 2018 21:18:52 + with message-id and subject line Bug#903181: fixed in mnemosyne 2.6.1+ds-1 has caused the Debian Bug report #903181, regarding mnemosyne: FTBFS in buster/sid (dh_installdocs: Cannot find "README") 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.) -- 903181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mnemosyne Version: 2.6+ds-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with=python3,sphinxdoc --buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_autoreconf -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:217: python3.6 setup.py config running config /usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution option: 'app' warnings.warn(msg) debian/rules override_dh_auto_build make[1]: Entering directory '/<>/mnemosyne-2.6+ds' make build-all-deps make[2]: Entering directory '/<>/mnemosyne-2.6+ds' # Also rebuilds the docs and the translations. [... snipped ...] copying mo/id/LC_MESSAGES/mnemosyne.mo -> /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/id/LC_MESSAGES creating /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/nl creating /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/nl/LC_MESSAGES copying mo/nl/LC_MESSAGES/mnemosyne.mo -> /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/nl/LC_MESSAGES creating /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/sv creating /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/sv/LC_MESSAGES copying mo/sv/LC_MESSAGES/mnemosyne.mo -> /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/sv/LC_MESSAGES creating /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/eo creating /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/eo/LC_MESSAGES copying mo/eo/LC_MESSAGES/mnemosyne.mo -> /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/eo/LC_MESSAGES creating /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/da creating /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/da/LC_MESSAGES copying mo/da/LC_MESSAGES/mnemosyne.mo -> /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/da/LC_MESSAGES creating /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/cs creating /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/cs/LC_MESSAGES copying mo/cs/LC_MESSAGES/mnemosyne.mo -> /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/cs/LC_MESSAGES creating /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/zh_TW creating /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/zh_TW/LC_MESSAGES copying mo/zh_TW/LC_MESSAGES/mnemosyne.mo -> /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/zh_TW/LC_MESSAGES creating /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/hu creating /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/hu/LC_MESSAGES copying mo/hu/LC_MESSAGES/mnemosyne.mo -> /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/hu/LC_MESSAGES creating /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/tr creating /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/tr/LC_MESSAGES copying mo/tr/LC_MESSAGES/mnemosyne.mo -> /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/share/locale/tr/LC_MESSAGES running install_egg_info running egg_info creating Mnemosyne.egg-info writing Mnemosyne.egg-info/PKG-INFO writing dependency_links to Mnemosyne.egg-info/dependency_links.txt writing top-level names to Mnemosyne.egg-info/top_level.txt writing manifest file 'Mnemosyne.egg-info/SOURCES.txt' reading manifest file 'Mnemosyne.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'README' warning: no files found matching 'mnemosyne/libmnemosyne/LICENSE' writing manifest file 'Mnemosyne.egg-info/SOURCES.txt' Copying Mnemosyne.egg-info to /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/lib/python3.6/dist-packages/Mnemosyne-2.6.egg-info Skipping SOURCES.txt running install_scripts creating /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/bin copying build/scripts-3.6/mnemosyne -> /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/bin changing mode of /<>/mnemosyne-2.6+ds/debian/mnemosyne/usr/bin/mnemosyne to 775 dh_installdocs -i -O--buildsystem=pybuild dh_installdocs: Cannot find (any matches for) "README" (tried in .) debian/rules:7: recipe for
Bug#889557: ovito: (Build-)Depends on obsolete libbotan1.10-dev
Dear ovito Maintainers, is there any update on progress of porting to botan2, or at least moving off botan1.10? Cheers, Chris
Processed: severity of 905799 is normal
Processing commands for cont...@bugs.debian.org: > severity 905799 normal Bug #905799 [ftp.debian.org] RM: tk8.5 -- ROQA; obsolete Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 905799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#889556: monotone: (Build-)Depends on obsolete libbotan1.10-dev
Hi Markus, * Markus Wanner [180809 20:52]: > On 03/09/2018 10:32 AM, Jack Lloyd wrote: > > 2.4.0 was just (in last week or so) packaged for buster - > > https://packages.debian.org/buster/libbotan-2-4 > > oh, very nice. Looks like I searched only "stable". Thank you for the hint. Is there any update on progress of switching to botan2 for monotone? Cheers, Chris
Bug#896085: tk8.5: Time to remove from Debian
Control: clone 896085 -2 Control: reassign -2 ftp.debian.org Control: retitle -2 RM: tk8.5 -- ROQA; obsolete Control: affects -2 src:tk8.5 * Sergei Golovan [180809 20:47]: > Source: tk8.5 > > Tcl/Tk 8.5 has reached its end-of-life, so it's time to remove it from Debian. > Applications which use Tcl/Tk should switch to 8.6 which is available > for a few years already. netgen has just moved off tk8.5 in unstable, so the current status is: Will remove the following packages from unstable: libtk8.5 | 8.5.19-3 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, ppc64el, s390x tk8.5 | 8.5.19-3 | source, amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, ppc64el, s390x tk8.5-dev | 8.5.19-3 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, ppc64el, s390x tk8.5-doc | 8.5.19-3 | all Maintainer: Debian Tcl/Tk Packagers --- Reason --- -- Checking reverse dependencies... # Broken Depends: netgen: netgen [hurd-i386 kfreebsd-amd64 kfreebsd-i386] oce: oce-draw [kfreebsd-amd64 kfreebsd-i386] oce is BD-Uninstallable on kfreebsd* for 91 days. netgen is BD-Uninstallable on hurd, kfreebsd*. Thanks, Chris
Processed: Re: Bug#896085: tk8.5: Time to remove from Debian
Processing control commands: > clone 896085 -2 Bug #896085 [src:tk8.5] tk8.5: Time to remove from Debian Bug 896085 cloned as bug 905799 > reassign -2 ftp.debian.org Bug #905799 [src:tk8.5] tk8.5: Time to remove from Debian Bug reassigned from package 'src:tk8.5' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #905799 to the same values previously set Ignoring request to alter fixed versions of bug #905799 to the same values previously set > retitle -2 RM: tk8.5 -- ROQA; obsolete Bug #905799 [ftp.debian.org] tk8.5: Time to remove from Debian Changed Bug title to 'RM: tk8.5 -- ROQA; obsolete' from 'tk8.5: Time to remove from Debian'. > affects -2 src:tk8.5 Bug #905799 [ftp.debian.org] RM: tk8.5 -- ROQA; obsolete Added indication that 905799 affects src:tk8.5 -- 896085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896085 905799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Fixed, close bug
Processing commands for cont...@bugs.debian.org: > fixed 904340 6.2.1804+dfsg1-1 Bug #904340 [netgen] netgen: Depends on obsolete tk8.5 Marked as fixed in versions netgen/6.2.1804+dfsg1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 904340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905140: Bug #905140 in cmake marked as pending
Hello, What about the bugs with patches, e.g. for Hurd and kFreeBSD. Still somebody needs to NMU this package... You don't seem interested in fixing bugs to your package, except RC ones. Not the ideal way Debian maintainers should work with their packages... On Thu, 2018-08-09 at 19:58 +, Felix Geyer wrote: > Control: tag -1 pending > > Hello, > > Bug #905140 in cmake 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/cmake-team/cmake/commit/12de5624a18704f1a9d7 > 368a3267b7dddea0b3ec > > --- > - > New upstream release. > > Fixes FTBFS with recent version of libuv1. (Closes: #905140) > > --- > - > > (this message was generated automatically)
Bug#904340: marked as done (netgen: Depends on obsolete tk8.5)
Your message dated Thu, 9 Aug 2018 22:37:23 +0200 with message-id and subject line Fixed, close bug has caused the Debian Bug report #904340, regarding netgen: Depends on obsolete tk8.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.) -- 904340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: netgen Version: 4.9.13.dfsg-11 Severity: serious In #896085 it has been suggested that tk8.5 should go away before stretch. This bug informs you of this ;-) C. --- End Message --- --- Begin Message --- fixed 904340 6.2.1804+dfsg1-1 thanks The newest netgen does not depent on any particular tk version. Closing the bug. Regards Anton--- End Message ---
Bug#904340: Fixed, close bug
fixed 904340 6.2.1804+dfsg1-1 thanks The newest netgen does not depent on any particular tk version. Closing the bug. Regards Anton
Bug#905140: marked as done (cmake: FTBFS with recent version of libuv1)
Your message dated Thu, 09 Aug 2018 20:34:57 +
with message-id
and subject line Bug#905140: fixed in cmake 3.12.1-1
has caused the Debian Bug report #905140,
regarding cmake: FTBFS with recent version of libuv1
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.)
--
905140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905140
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cmake
Version: 3.11.2-1
Severity: serious
Tags: patch
Usertags: linux-any, freebsd-any, hurd-any
Hello,
cmake FTBFS with recent a version of libuv1: 1.22.0-x. The build for
most architectures was made 60+ days ago, then with 1.20.3-x. Since
then two upstream versions was released and the specific change was for
1.21.0:
* core: move all include files except uv.h to uv/ (Saúl Ibarra
Corretgé)
The attached patch, Source_Modules_FindLibUV.cmake.diff, fixes the
build for linux-any architectures by looking for libuv header files in
/usr/include/uv in addition to /usr/include/uv-* headers. This patch
also affects #900240 and #905138 and is needed for successful builds.
Index: cmake-3.11.2/Source/Modules/FindLibUV.cmake
===
--- cmake-3.11.2.orig/Source/Modules/FindLibUV.cmake
+++ cmake-3.11.2/Source/Modules/FindLibUV.cmake
@@ -63,6 +63,8 @@ mark_as_advanced(LibUV_INCLUDE_DIR)
set(_LibUV_H_REGEX "#[ \t]*define[ \t]+UV_VERSION_(MAJOR|MINOR|PATCH)[ \t]+[0-9]+")
if(LibUV_INCLUDE_DIR AND EXISTS "${LibUV_INCLUDE_DIR}/uv-version.h")
file(STRINGS "${LibUV_INCLUDE_DIR}/uv-version.h" _LibUV_H REGEX "${_LibUV_H_REGEX}")
+elseif(LibUV_INCLUDE_DIR AND EXISTS "${LibUV_INCLUDE_DIR}/uv/version.h")
+ file(STRINGS "${LibUV_INCLUDE_DIR}/uv/version.h" _LibUV_H REGEX "${_LibUV_H_REGEX}")
elseif(LibUV_INCLUDE_DIR AND EXISTS "${LibUV_INCLUDE_DIR}/uv.h")
file(STRINGS "${LibUV_INCLUDE_DIR}/uv.h" _LibUV_H REGEX "${_LibUV_H_REGEX}")
else()
--- End Message ---
--- Begin Message ---
Source: cmake
Source-Version: 3.12.1-1
We believe that the bug you reported is fixed in the latest version of
cmake, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 905...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Felix Geyer (supplier of updated cmake package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 09 Aug 2018 21:35:37 +0200
Source: cmake
Binary: cmake cmake-data cmake-curses-gui cmake-qt-gui cmake-doc
Architecture: source
Version: 3.12.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian CMake Team
Changed-By: Felix Geyer
Description:
cmake - cross-platform, open-source make system
cmake-curses-gui - curses based user interface for CMake (ccmake)
cmake-data - CMake data files (modules, templates and documentation)
cmake-doc - extended documentation in various formats for CMake
cmake-qt-gui - Qt based user interface for CMake (cmake-gui)
Closes: 905140
Changes:
cmake (3.12.1-1) unstable; urgency=medium
.
* New upstream release.
- Fixes FTBFS with recent version of libuv1. (Closes: #905140)
* Drop qt_import_dir_variable.diff, not needed anymore.
Checksums-Sha1:
336a253ffa828b01fb6649c89066299e04c49202 2999 cmake_3.12.1-1.dsc
5359cd2e36051b0746580298d42518b0aef27979 8090272 cmake_3.12.1.orig.tar.gz
1055aebdc42b329a49450525830ae8eef3b34b37 28116 cmake_3.12.1-1.debian.tar.xz
Checksums-Sha256:
6b2b2c110c260e5699650677a6dda945f600f2faeeb65518bfa8ccaf4b04e50a 2999
cmake_3.12.1-1.dsc
c53d5c2ce81d7a957ee83e3e635c8cda5dfe20c9d501a4828ee28e1615e57ab2 8090272
cmake_3.12.1.orig.tar.gz
d1a835d6fd3b65a2a5cbf5d9fd8d9eaa48fa3cd5e8337db2a45b891b542d9d44 28116
cmake_3.12.1-1.debian.tar.xz
Files:
075279c8c3bc10512003484244dca10d 2999 devel optional cmake_3.12.1-1.dsc
10109246a51102bfda45ff3935275fbf 8090272 devel optional
cmake_3.12.1.orig.tar.gz
c625d78e8474b001a79f0289a9aa4130 28116 devel optional
cmake_3.12.1-1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEFkxwUS95KUdnZKtW/iLG/YMTXUUFAltsnPcACgkQ/iLG/YMT
XUVyDhAArv+BqSYgowi4iojDSj4R2DTEGlfTKg56t/mBEZldwnnoXS9Ojc+ghKlZ
vs/6iaY0DWV833V9Azj08asIZsK44oiERlz9r+79MipHBbPo06DQMrkssC6+xJ6X
Bug#889003: marked as done (netgen FTBFS with libtogl-dev 2.0-1)
Your message dated Thu, 9 Aug 2018 22:11:39 +0200 with message-id and subject line Fixed, close bug has caused the Debian Bug report #889003, regarding netgen FTBFS with libtogl-dev 2.0-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.) -- 889003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: netgen Version: 4.9.13.dfsg-11 Severity: serious https://buildd.debian.org/status/package.php?p=netgen=sid ... libtool: link: g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -rdynamic -Wl,-z -Wl,relro -o netgen demoview.o ngappinit.o ngpkg.o onetcl.o nginterface.o nginterface_v2.o parallelfunc.o parallelinterface.o ../libsrc/visualization/libvisual.a ../libsrc/csg/.libs/libcsg.a ../libsrc/geom2d/.libs/libgeom2d.a ../libsrc/interface/.libs/libinterface.a ../libsrc/stlgeom/.libs/libstl.a ../libsrc/occ/.libs/libocc.a ../libsrc/meshing/.libs/libmesh.a ../libsrc/gprim/.libs/libgprim.a ../libsrc/linalg/.libs/libla.a ../libsrc/general/.libs/libgen.a -L/usr/lib -lTKernel -lTKGeomBase -lTKMath -lTKG2d -lTKG3d -lTKXSBase -lTKOffset -lTKFillet -lTKShHealing -lTKMesh -lTKMeshVS -lTKTopAlgo -lTKGeomAlgo -lTKBool -lTKPrim -lTKBO -lTKIGES -lTKBRep -lTKSTEPBase -lTKSTEP -lTKSTL -lTKSTEPAttr -lTKSTEP209 -lTKXDESTEP -lTKXDEIGES -lTKXCAF -lTKLCAF -lFWOSPlugin -L/usr/lib/tk8.5/Togl1.7 -lTogl -lGLU -L/usr/lib/x86_64-linux-gnu -ltk8.5 -ltcl8.5 -ljpeg -lGL -lXmu -lpthread ngpkg.o: In function `Ng_Init': ./ng/ngpkg.cpp:5228: undefined reference to `Togl_CreateFunc' ./ng/ngpkg.cpp:5229: undefined reference to `Togl_DestroyFunc' ./ng/ngpkg.cpp:5230: undefined reference to `Togl_DisplayFunc' ./ng/ngpkg.cpp:5231: undefined reference to `Togl_ReshapeFunc' ./ng/ngpkg.cpp:5233: undefined reference to `Togl_CreateCommand' ./ng/ngpkg.cpp:5234: undefined reference to `Togl_CreateCommand' collect2: error: ld returned 1 exit status Makefile:526: recipe for target 'netgen' failed make[3]: *** [netgen] Error 1 --- End Message --- --- Begin Message --- fixed 889003 6.2.1804+dfsg1-1 thanks The newest netgen was successfullly built in the sid against current libtogl-dev. Closing the bug. Regards Anton--- End Message ---
Processed: Fixed, close bug
Processing commands for cont...@bugs.debian.org: > fixed 889003 6.2.1804+dfsg1-1 Bug #889003 [src:netgen] netgen FTBFS with libtogl-dev 2.0-1 Marked as fixed in versions netgen/6.2.1804+dfsg1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 889003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#889003: Fixed, close bug
fixed 889003 6.2.1804+dfsg1-1 thanks The newest netgen was successfullly built in the sid against current libtogl-dev. Closing the bug. Regards Anton
Bug#905140: Bug #905140 in cmake marked as pending
Control: tag -1 pending Hello, Bug #905140 in cmake 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/cmake-team/cmake/commit/12de5624a18704f1a9d7368a3267b7dddea0b3ec New upstream release. Fixes FTBFS with recent version of libuv1. (Closes: #905140) (this message was generated automatically) -- Greetings https://bugs.debian.org/905140
Processed: Bug #905140 in cmake marked as pending
Processing control commands: > tag -1 pending Bug #905140 [src:cmake] cmake: FTBFS with recent version of libuv1 Added tag(s) pending. -- 905140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905409: upgrade of util-linux and login break the xhost command for other users
On 09/08/2018 21:06, Helge Kreutzmann wrote: +Use a separate X display (e.g. "Switch User" in GNOME, or the equivalent fast-user-switching feature in other desktop environments), here probably it is better to say that the user can switch from one to other user with the Ctrl-Alt-Fx keys +Use ssh, e.g. "ssh -X -oForwardX11Trusted=no otheruser@localhost". and here, I think it is better to write somethings like: +Use ssh, e.g. "ssh -X -oForwardX11Trusted=no $OTHERUSER@$LOCALHOST". +Where $OTHERUSER is the user you want to use to execute commands +and $LOCALHOST is your localhost (it can be: localhost, 127.0.0.1, ...) and probably it is better to mention that you need sshd process active in your system (you must install openssh-server). I don't know if it is better to evidence that with this solution you can have performance problems and not all can work correctly as you expected. +Allow \fBsu\fR explicit display access by issuing "xhost +si:localuser:otheruser" in and here, I think it is better to write somethings like: +explicit display access by issuing "xhost +si:localuser:$OTHERUSER" ... +the originating X session and "DISPLAY=:0 command" under \fBsu\fR. and here +the originating X session and "DISPLAY=:0 $COMMAND" under \fBsu\fR. +or export the DISPLAY variable as "export DISPLAY=:0" +and then execute all the commands with GUI you like: "$COMMAND &" +where $COMMAND is the GUI command you like to exec (eg: qcalculate &) Probably it is better to put some link to documentation man sshd man ssh_config man sshd_config man xhost ... Ciao Davide -- Dizionari: http://linguistico.sourceforge.net/wiki Motivi per non comprare/usare ms-windows-vista: http://badvista.fsf.org/ Non autorizzo la memorizzazione del mio indirizzo su outlook
Processed: fixed 905735 in emacs-goodies-el/40.1
Processing commands for cont...@bugs.debian.org: > fixed 905735 emacs-goodies-el/40.1 Bug #905735 [emacs-goodies-el] emacs-goodies-el: postinst failure due to missing lcomp.el Marked as fixed in versions emacs-goodies-el/40.1. > thanks Stopping processing here. Please contact me if you need assistance. -- 905735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 905735 is serious
Processing commands for cont...@bugs.debian.org: > severity 905735 serious Bug #905735 [emacs-goodies-el] emacs-goodies-el: postinst failure due to missing lcomp.el Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 905735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 905578 is serious
Processing commands for cont...@bugs.debian.org: > severity 905578 serious Bug #905578 [emacs-goodies-el] Install script from emacs-goodies-el package failed Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 905578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905409: upgrade of util-linux and login break the xhost command for other users
Hello Chris, On Wed, Aug 08, 2018 at 08:58:24PM +0200, Chris Hofstaedtler wrote: > * Helge Kreutzmann [180808 18:57]: > > On Tue, Aug 07, 2018 at 08:20:23PM +0100, Simon McVittie wrote: > > > Andreas already asked for a merge request, so it seems that proposing a > > > patch would indeed be welcome. > > > > I'll do, incorporating your excellent explaination. I'll do so until > > the end of the week (latest). > > Gentle reminder about this. Here you are: --- ./su.1.orig 2017-09-27 11:05:13.717361420 +0200 +++ ./su.1 2018-08-09 21:04:24.370998117 +0200 @@ -261,6 +261,27 @@ .RS .br session required pam_lastlog.so nowtmp +.PP +.RE +Further by default +.B su +does not allow the commands to access the current X display. To allow +graphical applications with the privileges of a different user +(called "otheruser" in this example) several +options exists. These are, in order of preference (security-wise): +.RS 10 +.TP +o +Use a separate X display (e.g. "Switch User" in GNOME, or the equivalent fast-user-switching feature in other desktop environments), or a "thicker" remoting layer like VNC, Spice or Xpra. +.TP +o +Use ssh, e.g. "ssh -X -oForwardX11Trusted=no otheruser@localhost". +.TP +o +Allow \fBsu\fR explicit display access by issuing "xhost +si:localuser:otheruser" in +the originating X session and "DISPLAY=:0 command" under \fBsu\fR. +This has serious security implications and hence should only be used in +trusted environments. .RE .SH "SEE ALSO" .BR setpriv (1), Feel free to update. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: Digital signature
Bug#905767:
Just ignore this test. See https://bugs.debian.org/879020 .
Processed (with 1 error): control
Processing commands for cont...@bugs.debian.org:
> forcemerge 879020 905767
Bug #879020 {Done: Rob Browning } [src:emacs25] emacs25:
FTBFS on alpha: eieio-test-37-obsolete-name-in-constructor FAILED
Unable to merge bugs because:
package of #905767 is 'emacs25' not 'src:emacs25'
Failed to forcibly merge 879020: Did not alter merged bugs.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
879020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879020
905767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#893044: marked as done (slurm-llnl: CVE-2018-7033: Issue in accounting_storage/mysql plugin by always escaping strings within the slurmdbd)
Your message dated Thu, 9 Aug 2018 18:15:20 +0200 with message-id <20180809161520.GA32640@ischia> and subject line Re: Bug#893044: closing 893044 has caused the Debian Bug report #893044, regarding slurm-llnl: CVE-2018-7033: Issue in accounting_storage/mysql plugin by always escaping strings within the slurmdbd 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.) -- 893044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: slurm-llnl Version: 14.03.9-5 Severity: grave Tags: patch security upstream Forwarded: https://bugs.schedmd.com/show_bug.cgi?id=4792 Hi, the following vulnerability was published for slurm-llnl, filling as grave to be on safe side, but details are yet not disclosed in the upstream report. CVE-2018-7033[0]: |Issue in accounting_storage/mysql plugin by always escaping strings |within the slurmdbd If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-7033 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7033 [1] https://bugs.schedmd.com/show_bug.cgi?id=4792 Regards, Salvatore --- End Message --- --- Begin Message --- Package: slurm-llnl Version: 14.03.9-5+deb8u4 Hi Stephane, On Mon, Jul 30, 2018 at 11:07:21AM +0200, Stephane Vaillant wrote: > The problem seems to be located in CVE-2018-7033-2.patch (provided in the > slurm-llnl_14.03.9-5+deb8u3.debian.tar.xz archive) : > - if (gres_req) > - xstrcat(query, ", gres_req"); > - if (gres_alloc) > - xstrcat(query, ", gres_alloc"); > + if (job_ptr->gres_req) > + xstrcat(query, ", job_ptr->gres_req"); > + if (job_ptr->gres_alloc) > + xstrcat(query, ", job_ptr->gres_alloc"); the patch was fixed, by quoting the columns name. Thank you for your investigations and report. Best regards, -- Gennaro Oliva--- End Message ---
Bug#901952: find the commit
It looks this commit is the problem: http://git.savannah.gnu.org/cgit/tar.git/commit/?id=dee7e3f16e74e07504bb8f4d80426005fe4364ae tar no longer strips a quoting level when reading lines from the manifest file.
Bug#905788: FTBFS: cannot find -lgpod
Package: src:libgpod Version: 0.8.3-11 Severity: serious Justification: fails to build from source (but built successfully in the past) Tags: ftbfs Trying to build the package in a fresh sid sbuild chroot I get libtool: warning: relinking '_gpod.la' libtool: install: (cd /<>/build/python2.7/bindings/python; /bin/bash "/<>/build/python2.7/libtool" --tag CC --mode=relink gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -module -avoid-version -shared -Wl,-z,relro -Wl,-O1 -Wl,--as-needed -o _gpod.la -rpath /usr/lib/python2.7/dist- packages/gpod _gpod_la-gpod_wrap.lo -lgobject-2.0 -lsqlite3 -lplist -Wl,-- export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 -lxml2 -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0 -lgobject-2.0 -lglib-2.0 ../../src/libgpod.la -inst- prefix-dir /<>/debian/tmp) Byte-compiling python modules (optimized versions) ... __init__.pygtkpod.pyipod.py Byte-compiling python modules (optimized versions) ... gpod.py libtool: relink: gcc -shared -fPIC -DPIC .libs/_gpod_la-gpod_wrap.o -L/<>/debian/tmp/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux- gnu -lsqlite3 -lplist -lgmodule-2.0 -lxml2 -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0 -lgpod -g -O2 -fstack-protector-strong -Wl,-z -Wl,relro -Wl,-O1 -Wl,--as-needed -Wl,--export-dynamic -pthread -pthread -Wl,-soname -Wl,_gpod.so -o .libs/_gpod.so /usr/bin/ld: cannot find -lgpod collect2: error: ld returned 1 exit status libtool: error: error: relink '_gpod.la' with the above command before installing it -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash -- WBR, wRAR signature.asc Description: PGP signature
Bug#896230: python-gpod: gpod fails to import
On Mon, Apr 23, 2018 at 08:28:22PM +0100, Mark Williams wrote: > Installing python-gobject seems to work around this. Suggest this is added > to dependencies. Thank you for this observation, it seems dh_python2 --depends=gobject doesn't produce the correct depends on python-gobject-2. -- WBR, wRAR signature.asc Description: PGP signature
Processed: bug 897895 is forwarded to https://github.com/libsigcplusplus/libsigcplusplus/issues/1 ...
Processing commands for cont...@bugs.debian.org: > forwarded 897895 https://github.com/libsigcplusplus/libsigcplusplus/issues/1 Bug #897895 [libsigc++-2.0-dev] rsbackup: ftbfs with GCC-8 Set Bug forwarded-to-address to 'https://github.com/libsigcplusplus/libsigcplusplus/issues/1'. > tags 897895 + upstream fixed-upstream Bug #897895 [libsigc++-2.0-dev] rsbackup: ftbfs with GCC-8 Added tag(s) fixed-upstream and upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 897895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#903255: marked as done (r8168-dkms: After update driver no longer works)
Your message dated Thu, 09 Aug 2018 15:05:46 + with message-id and subject line Bug#903255: fixed in r8168 8.046.00-1 has caused the Debian Bug report #903255, regarding r8168-dkms: After update driver no longer works 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.) -- 903255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: r8168-dkms Version: 8.045.08-3 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? An upgrade * What exactly did you do (or not do) that was effective (or ineffective)? I tried to unload the driver and reload it again, but same error messages were shown and and network card didn't work. * What was the outcome of this action? The message: r8168 :04:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0013 address=0x flags=0x] is shown is dmesg on boot. Every time the module is unloaded and reloaded the following messages are shown: [ 1403.320110] r8168 :04:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0013 address=0x flags=0x] [ 1403.320134] r8168 :04:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0013 address=0x0040 flags=0x] * What outcome did you expect instead? Driver been loaded and network card works *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (800, 'testing'), (600, 'unstable'), (500, 'stable'), (400, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages r8168-dkms depends on: ii dkms 2.3-3 r8168-dkms recommends no packages. r8168-dkms suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: r8168 Source-Version: 8.046.00-1 We believe that the bug you reported is fixed in the latest version of r8168, 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 903...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated r8168 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: Thu, 09 Aug 2018 15:54:32 +0200 Source: r8168 Binary: r8168-dkms Architecture: source Version: 8.046.00-1 Distribution: unstable Urgency: medium Maintainer: Andreas Beckmann Changed-By: Andreas Beckmann Description: r8168-dkms - dkms source for the r8168 network driver Closes: 903255 Changes: r8168 (8.046.00-1) unstable; urgency=medium . * New upstream release 8.046.00 (2018-08-03). (Closes: #903255) * Remove kernel support patches that were fixed upstream. * Refresh remaining patches. * Bump Standards-Version to 4.2.0 (no changes needed). * Use the real upstream as Homepage, not the unofficial mirror. Checksums-Sha1: f1204fbddbcc657016557ae735656e8ce10f5f1e 1932 r8168_8.046.00-1.dsc a62127c1f498c36dcf18ca7a548af51eedcc221f 106363 r8168_8.046.00.orig.tar.bz2 ef2e31c7a1660eb3bdfccb79dd9ff142b9819049 5468 r8168_8.046.00-1.debian.tar.xz b4948f751800d25e2be7e071148b474c2cc8a045 5534 r8168_8.046.00-1_source.buildinfo Checksums-Sha256: 4b9d3c0fff44e4d89ca007de8af5ae2c62a2547bc54e9bccc05cd2a3b314d759 1932 r8168_8.046.00-1.dsc 0dfe35904c15ee7578ffa9d77acdf2c4c873a3ef04c261259469e3c081b8dd51 106363 r8168_8.046.00.orig.tar.bz2 09d5d90a4a2a74b579208867e704e110ec19497f508177ae8991180fa429a23c 5468 r8168_8.046.00-1.debian.tar.xz 2f8dd886e107d0068e69bd5c495a0e1cce0c9f2b312a5d2e3b2fc0e08c22f490 5534 r8168_8.046.00-1_source.buildinfo Files: 5e0e38cc1548e6a62fda5c349ac752b8 1932 non-free/kernel optional r8168_8.046.00-1.dsc 4707cd0958bf0f8b95cfa413ce568318 106363 non-free/kernel optional
Processed: Re: Bug#905413 closed by Jonathan Carter (Bug#905413: fixed in gamemode 1.2-3)
Processing control commands:
> reassign -1 src:gamemode 1.2-2
Bug #905413 {Done: Jonathan Carter } [libgamemode0-dev]
libgamemode0-dev: missing Depends: libgamemode0 (= ${binary:Version})
Warning: Unknown package 'libgamemode0-dev'
Bug reassigned from package 'libgamemode0-dev' to 'src:gamemode'.
Warning: Unknown package 'src:gamemode'
Warning: Unknown package 'src:gamemode'
No longer marked as found in versions gamemode/1.2-2.
Warning: Unknown package 'src:gamemode'
Warning: Unknown package 'src:gamemode'
No longer marked as fixed in versions gamemode/1.2-3.
Warning: Unknown package 'src:gamemode'
Bug #905413 {Done: Jonathan Carter } [src:gamemode]
libgamemode0-dev: missing Depends: libgamemode0 (= ${binary:Version})
Warning: Unknown package 'src:gamemode'
Marked as found in versions gamemode/1.2-2.
Warning: Unknown package 'src:gamemode'
> found -1 1.2-3
Bug #905413 {Done: Jonathan Carter } [src:gamemode]
libgamemode0-dev: missing Depends: libgamemode0 (= ${binary:Version})
Warning: Unknown package 'src:gamemode'
Marked as found in versions gamemode/1.2-3 and reopened.
Warning: Unknown package 'src:gamemode'
--
905413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#905413: closed by Jonathan Carter (Bug#905413: fixed in gamemode 1.2-3)
Control: reassign -1 src:gamemode 1.2-2 Control: found -1 1.2-3 Thanks for naming the -dev packages in the normal way. But they now depend on the not existing libgamemode, libgamemodeauto packages - these of course need the SOVERSION suffix, so libgamemode0, libgamemodeauto0. Andreas
Processed: tagging 897784
Processing commands for cont...@bugs.debian.org: > tags 897784 + ftbfs Bug #897784 [src:libbpp-seq] libbpp-seq: ftbfs with GCC-8 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 897784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904825: marked as done (aces3 ftbfs in unstable)
Your message dated Thu, 09 Aug 2018 13:34:49 + with message-id and subject line Bug#904825: fixed in openmpi 3.1.1.real-5 has caused the Debian Bug report #904825, regarding aces3 ftbfs in unstable 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.) -- 904825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:aces3 Version: 3.0.8-5.1 Tags: sid buster Severity: serious aces3 ftbfs in unstable: [...] mpif77 -DMPIF2C -DMPI2 -DC_SUFFIX -DCB_SUFFIX -D__fortran -D__fortran77 -g -O2 -Wall -fno-aggressive-loop-optimizations -o xaces3 \ find_seg.o reorder_coefficients.o reorder_rohf.o joda_exit.o clear_static_data_requests.o init_data.o nuclear_nuclear_repulsion_energy.o worker_termination.o check_jodadone.o find_jobflow.o write_default_sial_programs.o int_send_common.o int_gen_sizer.o geometry.o reset_internal_system_data.o write_zmat_auto.o get_sial_config_params.o aces_com_parallel_aces.o nuclear_nuclear_gradient.o beta.o scf_init.o set_ecp_charges.o worker_work.o decode_fmo_params.o timer_data.o descramble_coefficients.o int_gen_init.o handle_gradient.o molread.o det_segsizes.o handle_hessian.o worker_init.o joda_prep.o verify_aces2_params.o c_exit.o sumz.o ../sia/manager/check_consistency.o ../sia/manager/check_for_server_array.o ../sia/manager/check_preparesum_work.o ../sia/manager/check_work_stack_for_delay.o ../sia/manager/claim_memory_block.o ../sia/manager/clear_server_stats.o ../sia/manager/diskcall.o ../sia/manager/distribute_server_info.o ../sia/manager/do_backup.o ../sia/manager/find_clean_block.o ../sia/manager/find_free_diskloc.o ../sia/manager/find_oldest_dirty_block.o ../sia/manager/find_server_table_ptr.o ../sia/manager/insert_work_node.o ../sia/manager/make_free_block.o ../sia/manager/mark_block_clean.o ../sia/manager/mark_block_dirty.o ../sia/manager/pop_clean_block.o ../sia/manager/pop_work_node.o ../sia/manager/prequest_copy_slice.o ../sia/manager/print_server_data.o ../sia/manager/process_prepare_message.o ../sia/manager/process_preparesum_message.o ../sia/manager/process_prequest_message.o ../sia/manager/process_request_message.o ../sia/manager/process_server_blocks_to_list_msg.o ../sia/manager/process_server_blocks_to_list_no_mpi_io.o ../sia/manager/process_server_checkpoint_msg.o ../sia/manager/process_server_commit_msg.o ../sia/manager/process_server_copy_message.o ../sia/manager/process_server_delete_message.o ../sia/manager/process_server_list_to_blocks_msg.o ../sia/manager/process_server_restart_msg.o ../sia/manager/process_work_queue_entry.o ../sia/manager/ptr_check.o ../sia/manager/push_clean_block.o ../sia/manager/push_work_node.o ../sia/manager/remove_from_dirty_list.o ../sia/manager/remove_work_head.o ../sia/manager/server_abort_job.o ../sia/manager/sip_server_init.o ../sia/manager/sip_server_work.o ../sia/manager/syscopy.o ../sia/manager/translate_key.o ../sia/worker/block_map_table_setup.o ../sia/worker/build_segment_table.o ../sia/worker/built_cmp2zmat.o ../sia/worker/determine_stack_blocksizes.o ../sia/worker/fragment_orbitals.o ../sia/worker/fshells_to_segments.o ../sia/worker/get_subrange_segments.o ../sia/worker/get_symbolic_constant.o ../sia/worker/init_c.o ../sia/worker/init_eps.o ../sia/worker/init_fock.o ../sia/worker/init_fockrohf.o ../sia/worker/init_oed_integrals.o ../sia/worker/print_symbolic_constants.o ../sia/worker/refill_block_map_table.o ../sia/worker/remap.o ../sia/worker/send_static_data.o ../sia/worker/shells_to_segments.o ../sia/worker/sial_compile_and_send_tables.o ../sia/worker/sial_compile_and_send_tables1.o ../sia/worker/sip_fmain.o ../sia/worker/stack_distribution.o ../sia/worker/vmlgen.o ../sia/worker/vtdemo_init.o ../sia/worker/write_eig_data.o ../aces/aces_library/special_directory/direct_integral/aces_to_erd.o ../aces/aces_library/special_directory/direct_integral/binpack.o ../aces/aces_library/special_directory/direct_integral/comp_dipole_moment.o ../aces/aces_library/special_directory/direct_integral/comp_first_moment.o ../aces/aces_library/special_directory/direct_integral/comp_fock_der.o ../aces/aces_library/special_directory/direct_integral/comp_overlap_der.o ../aces/aces_library/special_directory/direct_integral/comp_return_derv_xyz.o ../aces/aces_library/special_directory/direct_integral/comp_return_h1.o ../aces/aces_library/special_directory/direct_integral/comp_return_h1_nodiag.o ../aces/aces_library/special_directory/direct_integral/comp_return_ovl.o ../aces/aces_library/special_directory/direct_integral/comp_return_x.o
Bug#903063: marked as done (coquelicot FTBFS: update Build-Depends: ruby-ronn -> ronn)
Your message dated Thu, 09 Aug 2018 13:18:53 + with message-id and subject line Bug#903063: fixed in coquelicot 0.9.6-1.1 has caused the Debian Bug report #903063, regarding coquelicot FTBFS: update Build-Depends: ruby-ronn -> ronn 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.) -- 903063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: coquelicot Version: 0.9.6-1 Severity: serious Since ronn got split out of ruby-ronn, coquelicot fails to build from source. It was not possible to have ruby-ronn temporarily depend on ronn, because that would have created a dependency cycle. Please update Build-Depends and replace ruby-ronn with ronn as coquelicot uses the command line tool. Helmut --- End Message --- --- Begin Message --- Source: coquelicot Source-Version: 0.9.6-1.1 We believe that the bug you reported is fixed in the latest version of coquelicot, 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 903...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro (supplier of updated coquelicot 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: Thu, 09 Aug 2018 09:59:43 -0300 Source: coquelicot Binary: coquelicot Architecture: source Version: 0.9.6-1.1 Distribution: unstable Urgency: medium Maintainer: Jérémy Bobbio Changed-By: Antonio Terceiro Description: coquelicot - "one-click" file sharing web application with a focus on users' p Closes: 903063 Changes: coquelicot (0.9.6-1.1) unstable; urgency=medium . * Non-maintainer upload. * Point Vcs-* to salsa.debian.org * Replace ruby-ronn with ronn in Build-Depends (Closes: #903063) Checksums-Sha1: cea343d083b62490213f4a120aba4f3d8646 2393 coquelicot_0.9.6-1.1.dsc c406cd4316643de05633d6dc3adcf34ba46959fd 34456 coquelicot_0.9.6-1.1.debian.tar.xz 859553ddf35fa05514ed6896b68fb68f3c7c4414 7897 coquelicot_0.9.6-1.1_source.buildinfo Checksums-Sha256: acacfbac1e14d299bc77575897f77e73893afacdb37a82845d74d62e155c6879 2393 coquelicot_0.9.6-1.1.dsc 1baf7729b6102d99e56f8efdc4f91e354eda2d449bd59d3762dae7ccac97c7ad 34456 coquelicot_0.9.6-1.1.debian.tar.xz 1b341739fdd7b5d9354f59c21831d4d471d352260fb76e1577002f047af516f0 7897 coquelicot_0.9.6-1.1_source.buildinfo Files: c6b727040a9a04a20759a6329ac5bc60 2393 web optional coquelicot_0.9.6-1.1.dsc baca24f974de2ff8b403178a2134e780 34456 web optional coquelicot_0.9.6-1.1.debian.tar.xz 064ac1edb3bb45600b3fad9122173c78 7897 web optional coquelicot_0.9.6-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAltsOycACgkQ/A2xu81G C96SoBAAs6WpNRMKcvhtvu+ZM+y5NCxttc/nMiRZbD42HfKH33+XFkeoR8orq+Xw dK19JHUmY1kF6Qwp5OGcW+UxhI0KFSYRXmWUQOFTPiGLTeE1sF3DLnmSQ4HqTeN2 /7LbxFDNPNW39Z6aXuY51xhqtsbMbcKi13GUa85aUllsI9wKqzeP4pGKZJjfUbM8 L4EyJBqZksBw407ZQygeX2O+MxfmH/Aw+QpRCIoOBwyTM75neFM5V2QHOuXiItFm NkfceGl1oOpNlSalFY2X4xOVmx/O9pztYFK0YEsqHdwiBsk6Rjk5lVmvrvtqZIZZ pCQjuYIusmR58s6D/F35uw3jfmwSsGYcnQFfE2rE7oM5etG1HdGC6KHq2kzB72um RBgDV1fSpIvdce65XsH0iEZHRVXolWFm28rlc2ESy/OwbOxi3e+tMIppD1R+WweN mawE5nTDtAEozYFztZvkGt1b5/tzv30BorBBwTvtSKS2Qw+DNtgVz+QhsGPIOPac Dn6KjfqRNPEYsDMpXdiLblw7GLGNaBG4aUphu4mVjf76nh+QC6CsnE4zzngQFIum h5vvxKZOyCorDKJGp+qqjVNGU9Yo9rHXsa8GU02papq6/EGmKKPd0v40LUFgC/KM 4l1qNrC7P0loBnTSIV51Rq+XwM2BRGF+malL2unCRwB6ciJV/io= =q48r -END PGP SIGNATURE End Message ---
Bug#897795: librcsb-core-wrapper: ftbfs with GCC-8
Control: tags -1 patch On Fri, May 04, 2018 at 12:22:25PM +, Matthias Klose wrote: >... > src/GenString.C: In static member function 'static bool > String::IsNumber(const string&)': > src/GenString.C:539:12: error: catching polymorphic type 'class > std::exception' by value [-Werror=catch-value=] > catch (exception) > ^ > cc1plus: all warnings being treated as errors > make[3]: *** [Makefile:156: GenString.o] Error 1 >... A workaround is attached. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed Description: Stop building with -Werror This works around a FTBFS with gcc 8. Author: Adrian Bunk Bug-Debian: https://bugs.debian.org/897795 --- librcsb-core-wrapper-1.005.orig/etc/make.platform.gnu4 +++ librcsb-core-wrapper-1.005/etc/make.platform.gnu4 @@ -34,7 +34,7 @@ ABI= # WARNINGS_AS_ERRORS defines flags to instruct all compilers to treat all # warnings as errors. -WARNINGS_AS_ERRORS=-Werror +#WARNINGS_AS_ERRORS=-Werror # ALL_WARNINGS defines flags to instruct all compilers to report all # warnings.
Processed: Re: Bug#897795: librcsb-core-wrapper: ftbfs with GCC-8
Processing control commands: > tags -1 patch Bug #897795 [src:librcsb-core-wrapper] librcsb-core-wrapper: ftbfs with GCC-8 Added tag(s) patch. -- 897795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897795 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897875: tempest-for-eliza: diff for NMU version 1.0.5-2.1
Control: tags 897875 + patch
Control: tags 897875 + pending
Dear maintainer,
I've prepared an NMU for tempest-for-eliza (versioned as 1.0.5-2.1)
and uploaded it to DELAYED/14. Please feel free to tell me if I should
cancel it.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
diff -Nru tempest-for-eliza-1.0.5/debian/changelog tempest-for-eliza-1.0.5/debian/changelog
--- tempest-for-eliza-1.0.5/debian/changelog 2015-07-12 23:57:24.0 +0300
+++ tempest-for-eliza-1.0.5/debian/changelog 2018-08-09 15:40:50.0 +0300
@@ -1,3 +1,10 @@
+tempest-for-eliza (1.0.5-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix logic errors discovered by gcc 8. (Closes: #897875)
+
+ -- Adrian Bunk Thu, 09 Aug 2018 15:40:50 +0300
+
tempest-for-eliza (1.0.5-2) unstable; urgency=medium
* Flesh out documentation
diff -Nru tempest-for-eliza-1.0.5/debian/patches/fix-logic-errors.patch tempest-for-eliza-1.0.5/debian/patches/fix-logic-errors.patch
--- tempest-for-eliza-1.0.5/debian/patches/fix-logic-errors.patch 1970-01-01 02:00:00.0 +0200
+++ tempest-for-eliza-1.0.5/debian/patches/fix-logic-errors.patch 2018-08-09 15:23:38.0 +0300
@@ -0,0 +1,17 @@
+Description: Fix logic errors discovered by gcc 8
+Author: Adrian Bunk
+Bug-Debian: https://bugs.debian.org/897875
+
+--- tempest-for-eliza-1.0.5.orig/mp3player.cpp
tempest-for-eliza-1.0.5/mp3player.cpp
+@@ -103,8 +103,8 @@ int main(int argc, char *argv[])
+ fprintf(stderr, "Couldn't set video mode: %s\n", SDL_GetError());
+ exit(1);
+ }
+- if ((screen->flags | SDL_HWPALETTE) == 0) error("i can't get hardware palette support.");
+- if ((screen->flags | SDL_FULLSCREEN) == 0) error("cannot set fullscreen mode.");
++ if ((screen->flags & SDL_HWPALETTE) == 0) error("i can't get hardware palette support.");
++ if ((screen->flags & SDL_FULLSCREEN) == 0) error("cannot set fullscreen mode.");
+ if (screen->format->BitsPerPixel != 8) error("cannot set 8bpp mode.");
+
+ SDL_LockSurface (screen);
diff -Nru tempest-for-eliza-1.0.5/debian/patches/series tempest-for-eliza-1.0.5/debian/patches/series
--- tempest-for-eliza-1.0.5/debian/patches/series 1970-01-01 02:00:00.0 +0200
+++ tempest-for-eliza-1.0.5/debian/patches/series 2018-08-09 15:22:39.0 +0300
@@ -0,0 +1 @@
+fix-logic-errors.patch
Processed: tempest-for-eliza: diff for NMU version 1.0.5-2.1
Processing control commands: > tags 897875 + patch Bug #897875 [src:tempest-for-eliza] tempest-for-eliza: ftbfs with GCC-8 Added tag(s) patch. > tags 897875 + pending Bug #897875 [src:tempest-for-eliza] tempest-for-eliza: ftbfs with GCC-8 Added tag(s) pending. -- 897875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#903063: Bug #903063 in coquelicot marked as pending
Control: tag -1 pending Hello, Bug #903063 in coquelicot 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/debian/coquelicot/commit/30b31c6e09b05732df239bfd557c815a53bd721d Replace ruby-ronn with ronn in Build-Depends Closes: #903063 (this message was generated automatically) -- Greetings https://bugs.debian.org/903063
Processed: Bug #903063 in coquelicot marked as pending
Processing control commands: > tag -1 pending Bug #903063 [coquelicot] coquelicot FTBFS: update Build-Depends: ruby-ronn -> ronn Added tag(s) pending. -- 903063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905782: Invalid dependency to mitmproxy old python2 module
Package: bdfproxy Version: 0.3.9-2 Severity: grave Since mitmproxy has been updated to python3, creating a mitmproxy python3-exclusive library, bdfproxy must be ported to python3 in order to work properly. -- Philippe.
Bug#904450: libredis-fast-perl: Incomplete debian/copyright?
tags #904450 confirmed thanks Ouch. Sorry for missing that. The convenience copy should have been removed. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Processed: Re: Bug#904450: libredis-fast-perl: Incomplete debian/copyright?
Processing commands for cont...@bugs.debian.org: > tags #904450 confirmed Bug #904450 [src:libredis-fast-perl] libredis-fast-perl: Incomplete debian/copyright? Warning: Unknown package 'src:libredis-fast-perl' Added tag(s) confirmed. Warning: Unknown package 'src:libredis-fast-perl' > thanks Stopping processing here. Please contact me if you need assistance. -- 904450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904450 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Pending
Processing commands for cont...@bugs.debian.org: > Tags 904450 + pending Bug #904450 [src:libredis-fast-perl] libredis-fast-perl: Incomplete debian/copyright? Warning: Unknown package 'src:libredis-fast-perl' Added tag(s) pending. Warning: Unknown package 'src:libredis-fast-perl' > stop Stopping processing here. Please contact me if you need assistance. -- 904450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904450 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Fixed upstream
Processing commands for cont...@bugs.debian.org: > tags 897840 fixed-upstream Bug #897840 [src:python-escript] python-escript: ftbfs with GCC-8 Added tag(s) fixed-upstream. > forwarded 897840 > https://bazaar.launchpad.net/~esys/escript-finley/trunk/revision/5325 Bug #897840 [src:python-escript] python-escript: ftbfs with GCC-8 Set Bug forwarded-to-address to 'https://bazaar.launchpad.net/~esys/escript-finley/trunk/revision/5325'. > thanks Stopping processing here. Please contact me if you need assistance. -- 897840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#888555: marked as done (clang-tools: fails to upgrade from 'sid' - trying to overwrite /usr/share/man/man1/clang-apply-replacements.1.gz)
Your message dated Thu, 09 Aug 2018 10:19:23 + with message-id and subject line Bug#888555: fixed in llvm-defaults 0.42 has caused the Debian Bug report #888555, regarding clang-tools: fails to upgrade from 'sid' - trying to overwrite /usr/share/man/man1/clang-apply-replacements.1.gz to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 888555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: clang-tools Version: 1:5.0-41~exp2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package clang-tools. Preparing to unpack .../clang-tools_1%3a5.0-41~exp2_amd64.deb ... Unpacking clang-tools (1:5.0-41~exp2) ... dpkg: error processing archive /var/cache/apt/archives/clang-tools_1%3a5.0-41~exp2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/clang-apply-replacements.1.gz', which is also in package clang 1:4.0-40 Errors were encountered while processing: /var/cache/apt/archives/clang-tools_1%3a5.0-41~exp2_amd64.deb Full list of conflicting files: usr/share/man/man1/clang-apply-replacements.1.gz usr/share/man/man1/clang-check.1.gz usr/share/man/man1/clang-query.1.gz usr/share/man/man1/sancov.1.gz usr/share/man/man1/scan-build.1.gz usr/share/man/man1/scan-view.1.gz cheers, Andreas clang=1%4.0-40_clang-tools=1%5.0-41~exp2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: llvm-defaults Source-Version: 0.42 We believe that the bug you reported is fixed in the latest version of llvm-defaults, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 888...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated llvm-defaults 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: Fri, 20 Jul 2018 10:30:58 +0200 Source: llvm-defaults Binary: llvm llvm-runtime llvm-dev clang clang-tools clang-tidy clang-format libclang1 libclang-dev lldb lld Architecture: source Version: 0.42 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Gianfranco Costamagna Description: clang - C, C++ and Objective-C compiler (LLVM based) clang-format - Tool to format C/C++/Obj-C code clang-tidy - clang-based C++ linter tool clang-tools - clang-based tools libclang-dev - clang library - Development package libclang1 - C, C++ and Objective-C compiler (LLVM based) lld- LLVM-based linker lldb - Next generation, high-performance debugger llvm - Low-Level Virtual Machine (LLVM) llvm-dev - Low-Level Virtual Machine (LLVM), libraries and headers llvm-runtime - Low-Level Virtual Machine (LLVM), bytecode interpreter Closes: 888555 Launchpad-Bugs-Fixed: 1777136 Changes: llvm-defaults (0.42) unstable; urgency=medium . [ Dimitri John Ledkov ] * Enable lldb on ppc64el. LP: #1777136 . [ Gianfranco Costamagna ] * Break/Replace for clang-tools newly owned packages (Closes: #888555) Checksums-Sha1: 7993ef8e7b917bfec8de37e5b38064c65f8f4857 2294 llvm-defaults_0.42.dsc 6652dbfb5790f0aa93f34165739716ecad567084 9796 llvm-defaults_0.42.tar.xz e5e4dab028ccbb0c259887437384331e2959f3fd 6625 llvm-defaults_0.42_source.buildinfo Checksums-Sha256: 99ebd8674b7ffbd40cdde03c46b3c782c941df5789085db0a9b888c1b2cee136 2294 llvm-defaults_0.42.dsc 508b40c2d3ff08a03a0df281ef24c40e88bc3da10a0c6fdc8e8e68f1fff87eab 9796 llvm-defaults_0.42.tar.xz 3e4a72be5ebf8607b9fb2fdbcf4e375521b0a9284bee3b88b34319b0c530aec3 6625 llvm-defaults_0.42_source.buildinfo Files: b633d18868c6205d7205e14b92726f1d 2294 devel optional llvm-defaults_0.42.dsc
Processed: tagging 897872
Processing commands for cont...@bugs.debian.org: > tags 897872 + ftbfs Bug #897872 [src:sumo] sumo: ftbfs with GCC-8 Bug #904667 [src:sumo] sumo FTBFS due to a C++ error Added tag(s) ftbfs. Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 897872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897872 904667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904667 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 897869
Processing commands for cont...@bugs.debian.org: > tags 897869 + ftbfs Bug #897869 [src:sphde] sphde: ftbfs with GCC-8 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 897869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 897873
Processing commands for cont...@bugs.debian.org: > tags 897873 + ftbfs Bug #897873 [src:sympathy] sympathy: ftbfs with GCC-8 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 897873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 888338
Processing commands for cont...@bugs.debian.org: > tags 888338 + ftbfs Bug #888338 [src:libavg] libavg: FTBFS with FFmpeg 4.0 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 888338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reopening 902462
Processing commands for cont...@bugs.debian.org:
> reopen 902462
Bug #902462 {Done: Jonathan Carter } [src:flask-restful]
flask-restful: FTBFS in buster/sid (failing tests)
'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 flask-silk/0.2-13.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
902462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#903326: calcurse: diff for NMU version 4.3.0-2.1
Control: tags 903326 + pending Dear maintainer, I've prepared an NMU for calcurse (versioned as 4.3.0-2.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed diff -Nru calcurse-4.3.0/debian/changelog calcurse-4.3.0/debian/changelog --- calcurse-4.3.0/debian/changelog 2018-05-02 16:27:29.0 +0300 +++ calcurse-4.3.0/debian/changelog 2018-08-09 12:34:01.0 +0300 @@ -1,3 +1,11 @@ +calcurse (4.3.0-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Stop trying to install docs removed upstream, fixes FTBFS. +(Closes: #903326) + + -- Adrian Bunk Thu, 09 Aug 2018 12:34:01 +0300 + calcurse (4.3.0-2) unstable; urgency=medium * The Akamai Technologies paid volunteer days release. diff -Nru calcurse-4.3.0/debian/docs calcurse-4.3.0/debian/docs --- calcurse-4.3.0/debian/docs 2017-01-06 16:05:20.0 +0200 +++ calcurse-4.3.0/debian/docs 2018-08-09 12:33:58.0 +0300 @@ -1,5 +1,3 @@ -NEWS -README AUTHORS doc/manual.txt doc/submitting-patches.txt
Processed: calcurse: diff for NMU version 4.3.0-2.1
Processing control commands: > tags 903326 + pending Bug #903326 [src:calcurse] calcurse: FTBFS in buster/sid (dh_installdocs: Cannot find "NEWS") Added tag(s) pending. -- 903326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#896299: Problem is urgent for us
I am not sure if there is already a solution for this bug, but our system encountered this problem when we tried to migrate to the newest Debian version (fresh installation). So, is there any solution or workaround on the horizon as we need Lucene/ Python-Lucene for a productive system. Thanks in advance.
Bug#905765: marked as done (python3-django-prometheus: Doesn't work with the django in stable, new compatible upstream is available)
Your message dated Thu, 09 Aug 2018 09:18:48 +
with message-id
and subject line Bug#905765: fixed in django-prometheus 1.0.15-1
has caused the Debian Bug report #905765,
regarding python3-django-prometheus: Doesn't work with the django in stable,
new compatible upstream is available
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.)
--
905765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-django-prometheus
Version: 1.0.6-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The version of python3-django-prometheus doesn't work with
python3-django in stable, because it relies on functions deprecated in
1.8 and removed in 1.10. There for python3-django-premetheus is only
useful for those stable users that have clearly older django version
that the one supplied in stable.
There is a new upstream version that should work fine with django 1.10.
Cheers, and have a wonderful day!
--
Lynoure
-- System Information:
Debian Release: 9.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-7-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_IE:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages python3-django-prometheus depends on:
ii python33.5.3-1
ii python3-prometheus-client 0.0.18-1
python3-django-prometheus recommends no packages.
python3-django-prometheus suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: django-prometheus
Source-Version: 1.0.15-1
We believe that the bug you reported is fixed in the latest version of
django-prometheus, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 905...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Chris Lamb (supplier of updated django-prometheus 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: Thu, 09 Aug 2018 11:05:22 +0200
Source: django-prometheus
Binary: python-django-prometheus python3-django-prometheus
Built-For-Profiles: nocheck
Architecture: source all
Version: 1.0.15-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Chris Lamb
Description:
python-django-prometheus - Django middlewares to enable monitoring with
Prometheus (Python 2
python3-django-prometheus - Django middlewares to enable monitoring with
Prometheus (Python 3
Closes: 905765
Changes:
django-prometheus (1.0.15-1) unstable; urgency=medium
.
[ Chris Lamb ]
* New upstream release. (Closes: #905765)
* Add myself to Uploaders.
* Add missing Depends on python{,3}-django.
* Move to debhelper compat level 11.
* Bump Standards-Version to 4.2.0.
* Install examples/*.
.
[ Ondřej Nový ]
* Convert git repository from git-dpm to gbp layout
* Fixed homepage (https)
* d/control: Set Vcs-* to salsa.debian.org
* d/copyright: Use https protocol in Format field
Checksums-Sha1:
7388dfef6655373b981d14a393f9e5cf85722ade 2337 django-prometheus_1.0.15-1.dsc
afa7a63f55f0b0436711b9034c0044f8d0802c5d 177764
django-prometheus_1.0.15.orig.tar.gz
303aca0fe2744ee1d7d75175ed5cb0b6f79ed05b 2044
django-prometheus_1.0.15-1.debian.tar.xz
7d790399c4eb185c654fb5d8a051274bcdac91de 7157
django-prometheus_1.0.15-1_amd64.buildinfo
10bbfa87bd2e0bc73472b22907b30ad7e7973e32 162264
python-django-prometheus_1.0.15-1_all.deb
e1f25406cada920373b541a6697b635227dfbdba 13472
python3-django-prometheus_1.0.15-1_all.deb
Checksums-Sha256:
23dde7318797de252d05c766576eedff4c193f007b2df9492f808692c789ec94 2337
django-prometheus_1.0.15-1.dsc
ee6a50c5706cd8d6343b5111e39960ea9602308834476477d85f6950e103d09d 177764
django-prometheus_1.0.15.orig.tar.gz
412c658089ac54bd1571f84f794e62008269816de93d102f4163af9b61ceea01 2044
django-prometheus_1.0.15-1.debian.tar.xz
e387f54af288fd7078fbddbafd664b494f8263580cd6d44e94ab52f5c1283994 7157
django-prometheus_1.0.15-1_amd64.buildinfo
Processed: Bug #905765 in django-prometheus marked as pending
Processing control commands: > tag -1 pending Bug #905765 [python3-django-prometheus] python3-django-prometheus: Doesn't work with the django in stable, new compatible upstream is available Added tag(s) pending. -- 905765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905765: Bug #905765 in django-prometheus marked as pending
Control: tag -1 pending Hello, Bug #905765 in django-prometheus 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/python-team/modules/django-prometheus/commit/c25e074bb10dfcbe6ff11b19b475ede420abe258 New upstream release. (Closes: #905765) (this message was generated automatically) -- Greetings https://bugs.debian.org/905765
Bug#903189: marked as done (python-ptrace: FTBFS in buster/sid (dh_installdocs: Cannot find "README"))
Your message dated Thu, 09 Aug 2018 09:04:08 + with message-id and subject line Bug#903189: fixed in python-ptrace 0.9.3-2.1 has caused the Debian Bug report #903189, regarding python-ptrace: FTBFS in buster/sid (dh_installdocs: Cannot find "README") 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.) -- 903189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-ptrace Version: 0.9.3-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with=python2,python3 --buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:217: python2.7 setup.py config running config I: pybuild base:217: python3.6 setup.py config running config dh_auto_build -i -O--buildsystem=pybuild I: pybuild base:217: /usr/bin/python setup.py build running build running build_py creating /<>/.pybuild/cpython2_2.7_ptrace/build/ptrace creating /<>/.pybuild/cpython2_2.7_ptrace/build/ptrace/binding [... snipped ...] byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/func_call.py to func_call.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/cpu_info.py to cpu_info.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/debugger/parse_expr.py to parse_expr.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/debugger/syscall_state.py to syscall_state.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/debugger/breakpoint.py to breakpoint.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/debugger/process_event.py to process_event.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/debugger/memory_mapping.py to memory_mapping.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/debugger/signal_reason.py to signal_reason.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/debugger/backtrace.py to backtrace.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/debugger/__init__.py to __init__.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/debugger/process.py to process.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/debugger/ptrace_signal.py to ptrace_signal.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/debugger/application.py to application.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/debugger/child.py to child.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/debugger/process_error.py to process_error.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/debugger/debugger.py to debugger.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/ctypes_tools.py to ctypes_tools.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/disasm.py to disasm.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/process_tools.py to process_tools.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/terminal.py to terminal.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/__init__.py to __init__.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/signames.py to signames.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/version.py to version.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/func_arg.py to func_arg.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/os_tools.py to os_tools.cpython-36.pyc byte-compiling /<>/debian/python3-ptrace/usr/lib/python3.6/dist-packages/ptrace/binding/cpu.py
Bug#905767: emacs25: FTBFS due to test failures on arm64 in a binNMU against new version of libmagick
Package: emacs25
Version: 25.2+1-6+b3
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
The latest binNMU of emacs25 on arm64 FTBFS due to the following test failure:
"""
[...]
passed 35/37 eieio-test-35-named-object
passed 36/37 eieio-test-36-build-class-alist
Test eieio-test-37-obsolete-name-in-constructor backtrace:
#[nil "\304\305\306!\307D\310\311\312\216\313 \"\211)\204 \31
ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
ert-run-test([cl-struct-ert-test eieio-test-37-obsolete-name-in-cons
ert-run-or-rerun-test([cl-struct-ert--stats (not (tag :expensive-tes
ert-run-tests((not (tag :expensive-test)) #[385 "\306\307\"\203G\2
ert-run-tests-batch((not (tag :expensive-test)))
ert-run-tests-batch-and-exit((not (tag :expensive-test)))
eval((ert-run-tests-batch-and-exit (quote (not (tag :expensive-test)
command-line-1(("-L" ":/<>/emacs25-25.2+1/debian/b
command-line()
normal-top-level()
Test eieio-test-37-obsolete-name-in-constructor condition:
(ert-test-failed
((should
(equal
(eieio--testing "toto")
'...))
:form
(equal
[eieio-class-tag--eieio--testing]
("toto" 2))
:value nil :explanation
(different-types
[eieio-class-tag--eieio--testing]
("toto" 2
FAILED 37/37 eieio-test-37-obsolete-name-in-constructor
Ran 37 tests, 36 results as expected, 1 unexpected (2018-07-18 08:49:03+)
1 unexpected results:
FAILED eieio-test-37-obsolete-name-in-constructor
ERROR: eieio-tests.log
"""
Thanks,
~Niels
Bug#888555: clang-tools: fails to upgrade from 'sid' - trying to overwrite /usr/share/man/man1/clang-apply-replacements.1.gz
On Sun, 10 Jun 2018 10:04:52 +0200 Andreas Beckmann wrote: > Followup-For: Bug #888555 > Control: found -1 1:6.0-41~exp5 > > Hi, > > the list of conflicting files has now grown to include binaries as well: > > usr/bin/c-index-test > usr/bin/clang-apply-replacements > usr/bin/clang-check > usr/bin/clang-query > usr/bin/sancov > usr/bin/scan-build > usr/bin/scan-view > usr/share/man/man1/clang-apply-replacements.1.gz > usr/share/man/man1/clang-check.1.gz > usr/share/man/man1/clang-query.1.gz > usr/share/man/man1/sancov.1.gz > usr/share/man/man1/scan-build.1.gz > usr/share/man/man1/scan-view.1.gz > > > Andreas Ping on this bug. It is stalling the migration of llvm-defaults, which in turn will remove all blockers for removing llvm-toolchain-4.0 from testing (except one #893408, which I have just bumped to serious) Thanks, ~Niels
Bug#905765: python3-django-prometheus: Doesn't work with the django in stable, new compatible upstream is available
Package: python3-django-prometheus Version: 1.0.6-1 Severity: grave Justification: renders package unusable Dear Maintainer, The version of python3-django-prometheus doesn't work with python3-django in stable, because it relies on functions deprecated in 1.8 and removed in 1.10. There for python3-django-premetheus is only useful for those stable users that have clearly older django version that the one supplied in stable. There is a new upstream version that should work fine with django 1.10. Cheers, and have a wonderful day! -- Lynoure -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-7-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-django-prometheus depends on: ii python33.5.3-1 ii python3-prometheus-client 0.0.18-1 python3-django-prometheus recommends no packages. python3-django-prometheus suggests no packages. -- no debconf information
Bug#905763: marked as done (virtualbox-5.2: libcurl3 and libcurl4)
Your message dated Thu, 9 Aug 2018 10:10:41 +0200 with message-id and subject line Re: virtualbox-5.2: libcurl3 and libcurl4 has caused the Debian Bug report #905763, regarding virtualbox-5.2: libcurl3 and libcurl4 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.) -- 905763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: virtualbox-5.2 Version: 5.2.16-123759~Debian~stretch Severity: critical Justification: breaks unrelated software Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-amd64 (SMP w/12 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages virtualbox-5.2 depends on: ii adduser3.117 ii debconf [debconf-2.0] 1.5.67 ii libc6 2.27-3 ii libcurl3 7.60.0-1 ii libdevmapper1.02.1 2:1.02.145-4.1 ii libgcc11:8.1.0-9 ii libgl1 1.0.0+git20180308-3 ii libgl1-mesa-glx18.1.3-1 ii libopus0 1.3~beta+20180518-1 ii libpng16-161.6.34-1 ii libqt5core5a 5.10.1+dfsg-7 ii libqt5gui5 5.10.1+dfsg-7 ii libqt5opengl5 5.10.1+dfsg-7 ii libqt5printsupport55.10.1+dfsg-7 ii libqt5widgets5 5.10.1+dfsg-7 ii libqt5x11extras5 5.10.1-2 ii libsdl1.2debian1.2.15+dfsg2-1 ii libssl1.1 1.1.0h-4 ii libstdc++6 8.1.0-9 ii libvpx41.6.1-3+deb9u1 ii libx11-6 2:1.6.5-1 ii libxcb11.13-1 ii libxcursor11:1.1.15-1 ii libxext6 2:1.3.3-1+b2 ii libxinerama1 2:1.1.3-1+b3 ii libxml22.9.4+dfsg1-7+b1 ii libxmu62:1.1.2-2 ii libxt6 1:1.1.5-1 ii psmisc 23.1-1+b1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages virtualbox-5.2 recommends: ii atril [pdf-viewer] 1.20.2-1 ii binutils 2.30.90.20180705-1 ii build-essential 12.5 ii dpkg-dev 1.19.0.5 ii evince [pdf-viewer] 3.28.2-1 ii gcc 4:7.3.0-3 ii kmod 25-1 ii libasound2 1.1.6-1 ii libgl1 1.0.0+git20180308-3 ii libpulse012.0-1 ii libsdl-ttf2.0-0 2.0.11-4 ii linux-headers-amd64 4.16+94 pn linux-image ii make 4.2.1-1 ii okular [pdf-viewer] 4:17.12.2-2 virtualbox-5.2 suggests no packages. -- debconf information: virtualbox/old-installation-found: virtualbox/old-running: virtualbox/group-vboxusers: virtualbox/module-compilation-failed: --- End Message --- --- Begin Message --- On Thu, 09 Aug 2018 09:36:08 +0200 Friedrich Dominicus wrote: > Package: virtualbox-5.2 > Version: 5.2.16-123759~Debian~stretch > Severity: critical > Justification: breaks unrelated software > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the outcome of this action? >* What outcome did you expect instead? > > *** End of the template - remove these template lines *** > this package is not part of any Debian release, but provided by upstream. closing G. > > > -- System Information: > Debian Release: buster/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'stable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.16.0-2-amd64 (SMP w/12 CPU cores) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= > (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages virtualbox-5.2 depends on: > ii adduser3.117 > ii debconf [debconf-2.0] 1.5.67 > ii libc6
Processed: severity of 893408 is serious
Processing commands for cont...@bugs.debian.org: > severity 893408 serious Bug #893408 [src:gazebo] gazebo: Please use clang-format insteal of clang-format-4.0 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 893408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905763: virtualbox-5.2: libcurl3 and libcurl4
Package: virtualbox-5.2 Version: 5.2.16-123759~Debian~stretch Severity: critical Justification: breaks unrelated software Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-amd64 (SMP w/12 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages virtualbox-5.2 depends on: ii adduser3.117 ii debconf [debconf-2.0] 1.5.67 ii libc6 2.27-3 ii libcurl3 7.60.0-1 ii libdevmapper1.02.1 2:1.02.145-4.1 ii libgcc11:8.1.0-9 ii libgl1 1.0.0+git20180308-3 ii libgl1-mesa-glx18.1.3-1 ii libopus0 1.3~beta+20180518-1 ii libpng16-161.6.34-1 ii libqt5core5a 5.10.1+dfsg-7 ii libqt5gui5 5.10.1+dfsg-7 ii libqt5opengl5 5.10.1+dfsg-7 ii libqt5printsupport55.10.1+dfsg-7 ii libqt5widgets5 5.10.1+dfsg-7 ii libqt5x11extras5 5.10.1-2 ii libsdl1.2debian1.2.15+dfsg2-1 ii libssl1.1 1.1.0h-4 ii libstdc++6 8.1.0-9 ii libvpx41.6.1-3+deb9u1 ii libx11-6 2:1.6.5-1 ii libxcb11.13-1 ii libxcursor11:1.1.15-1 ii libxext6 2:1.3.3-1+b2 ii libxinerama1 2:1.1.3-1+b3 ii libxml22.9.4+dfsg1-7+b1 ii libxmu62:1.1.2-2 ii libxt6 1:1.1.5-1 ii psmisc 23.1-1+b1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages virtualbox-5.2 recommends: ii atril [pdf-viewer] 1.20.2-1 ii binutils 2.30.90.20180705-1 ii build-essential 12.5 ii dpkg-dev 1.19.0.5 ii evince [pdf-viewer] 3.28.2-1 ii gcc 4:7.3.0-3 ii kmod 25-1 ii libasound2 1.1.6-1 ii libgl1 1.0.0+git20180308-3 ii libpulse012.0-1 ii libsdl-ttf2.0-0 2.0.11-4 ii linux-headers-amd64 4.16+94 pn linux-image ii make 4.2.1-1 ii okular [pdf-viewer] 4:17.12.2-2 virtualbox-5.2 suggests no packages. -- debconf information: virtualbox/old-installation-found: virtualbox/old-running: virtualbox/group-vboxusers: virtualbox/module-compilation-failed:
Bug#905761: backuppc: FTBFS with merged /usr
Package: backuppc
Version: 3.3.1-5
Severity: serious
Hi,
backuppc fails to build with merged /usr in a sbuild chroot, created with
current debootstrap. Debootstrap enabled merged /usr since version 1.0.85, see
https://bugs.debian.org/839046
The build fails when a patch is applied to the generated config.pl file. Since
the path to cat is now /usr/bin/cat instead of /bin/cat, the patch fails to
apply.
Here's the failing part of the patch:
-
@@ -224,7 +227,7 @@
# Full path to various commands for archiving
#
$Conf{SplitPath} = '/usr/bin/split';
-$Conf{ParPath} = '/usr/bin/par2';
+$Conf{ParPath} = '/usr/bin/par2' if -x '/usr/bin/par2';
$Conf{CatPath} = '/bin/cat';
$Conf{GzipPath} = '/bin/gzip';
$Conf{Bzip2Path} = '/bin/bzip2';
-
And here's the failing part of the build log:
--
install --mode=644 debian/apache.conf debian/backuppc/etc/backuppc
rmdir debian/backuppc/var/lib/backuppc/conf/
rmdir: failed to remove 'debian/backuppc/var/lib/backuppc/conf/': No such file o
r directory
make: [debian/rules:67: install] Error 1 (ignored)
(cd debian/backuppc/usr/share/backuppc/cgi-bin; ln -s ../image; ln -s /usr/lib/b
ackuppc/cgi-bin/index.cgi )
patch --no-backup-if-mismatch -p0 < debian/config.pl.diff
patching file debian/backuppc/etc/backuppc/config.pl
Hunk #2 FAILED at 227.
Hunk #4 succeeded at 1021 (offset -3 lines).
1 out of 7 hunks FAILED -- saving rejects to file debian/backuppc/etc/backuppc/c
onfig.pl.rej
make: *** [debian/rules:69: install] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit
status 2
-
Full build log attached.
Apparently, the official builds' chroots didn't use merged /usr when the
package was last built (February 2018), but at some point some of them will,
leading to inability to build backuppc on official infrastructure.
IMO, adapting the patch to the merged /usr would not work, since then the patch
will fail on systems without merged /usr.
-- dam
sbuild (Debian sbuild) 0.77.0 (06 July 2018) on pc1.creditreform.bg
+==+
| backuppc 3.3.1-5 (amd64) Wed, 08 Aug 2018 14:22:31 + |
+==+
Package: backuppc
Version: 3.3.1-5
Source Version: 3.3.1-5
Distribution: sid
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary
I: NOTICE: Log filtering will replace
'var/run/schroot/mount/sid+exp-perl-amd64-b67b90b7-ae44-4d20-b602-62f9cb7b4d9a'
with '<>'
I: NOTICE: Log filtering will replace 'build/backuppc-t497R0/resolver-4nL5LG'
with '<>'
+--+
| Update chroot|
+--+
Get:1 http://proxy:/debian sid InRelease [233 kB]
Get:2 http://proxy:/debian experimental InRelease [101 kB]
Get:3 http://perl.debian.net/test-repo perl-5.28 InRelease [2871 B]
Get:4 http://proxy:/debian sid/main amd64 Packages.diff/Index [27.9 kB]
Get:5 http://proxy:/debian sid/main amd64 Packages 2018-08-04-0814.44.pdiff
[20.5 kB]
Get:6 http://proxy:/debian sid/main amd64 Packages 2018-08-04-1411.17.pdiff
[9739 B]
Get:7 http://proxy:/debian sid/main amd64 Packages 2018-08-04-2013.33.pdiff
[17.8 kB]
Get:8 http://proxy:/debian sid/main amd64 Packages 2018-08-05-0209.24.pdiff
[15.5 kB]
Get:9 http://proxy:/debian sid/main amd64 Packages 2018-08-05-0806.31.pdiff
[2966 B]
Get:10 http://proxy:/debian sid/main amd64 Packages
2018-08-05-1409.33.pdiff [18.0 kB]
Get:11 http://proxy:/debian sid/main amd64 Packages
2018-08-05-2014.01.pdiff [9558 B]
Get:12 http://proxy:/debian sid/main amd64 Packages
2018-08-06-0208.11.pdiff [4773 B]
Get:13 http://proxy:/debian sid/main amd64 Packages
2018-08-06-0809.42.pdiff [5408 B]
Get:14 http://proxy:/debian sid/main amd64 Packages
2018-08-06-1412.59.pdiff [16.0 kB]
Get:15 http://proxy:/debian sid/main amd64 Packages
2018-08-06-2047.08.pdiff [31.4 kB]
Get:16 http://proxy:/debian sid/main amd64 Packages
2018-08-07-0215.15.pdiff [9234 B]
Get:17 http://proxy:/debian sid/main amd64 Packages
2018-08-07-0814.06.pdiff [5576 B]
Get:18 http://proxy:/debian sid/main amd64 Packages
2018-08-07-1417.50.pdiff [17.6 kB]
Get:19 http://proxy:/debian sid/main amd64 Packages
2018-08-07-2009.40.pdiff [13.1 kB]
Get:20 http://proxy:/debian sid/main amd64 Packages
2018-08-08-0208.47.pdiff [4775 B]
Get:21 http://proxy:/debian sid/main amd64 Packages
2018-08-08-0809.52.pdiff [7784 B]
Get:21 http://proxy:/debian sid/main amd64 Packages
2018-08-08-0809.52.pdiff [7784 B]
Get:22
