Bug#958312: marked as done (docker.io: signal SIGSEGV: segmentation violation shortly after starting the daemon)
Your message dated Tue, 21 Apr 2020 07:04:12 + with message-id and subject line Bug#958312: fixed in docker.io 19.03.7+dfsg1-2 has caused the Debian Bug report #958312, regarding docker.io: signal SIGSEGV: segmentation violation shortly after starting the daemon 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.) -- 958312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: docker.io Version: 19.03.7+dfsg1-1 Severity: critical Tags: patch upstream Justification: breaks unrelated software Dear Maintainer, The update to 19.03.7 led to a reproducible issue with docker shortly after starting the daemon: Apr 20 14:30:27 fsn dockerd[488555]: panic: runtime error: invalid memory address or nil pointer dereference Apr 20 14:30:27 fsn dockerd[488555]: [signal SIGSEGV: segmentation violation code=0x1 addr=0x11 pc=0x55a05b5ac02b] Apr 20 14:30:27 fsn dockerd[488555]: goroutine 2029 [running]: Apr 20 14:30:27 fsn dockerd[488555]: github.com/docker/libnetwork.(*resolver).ServeDNS(0xc000e38380, 0x55a05cbea2c0, 0xc0014b94a0, 0xc0018bd5f0) Apr 20 14:30:27 fsn dockerd[488555]: /build/docker.io-CrAKu8/docker.io-19.03.7+dfsg1/.gopath/src/github.com/docker/libnetwork/resolver.go:487 +0x79b Apr 20 14:30:27 fsn dockerd[488555]: github.com/miekg/dns.(*Server).serveDNS(0xc000dab200, 0xc000c0f200, 0x21, 0x200, 0xc0014b94a0) Apr 20 14:30:27 fsn dockerd[488555]: /build/docker.io-CrAKu8/docker.io-19.03.7+dfsg1/.gopath/src/github.com/miekg/dns/server.go:609 +0x2e2 Apr 20 14:30:27 fsn dockerd[488555]: github.com/miekg/dns.(*Server).serveUDPPacket(0xc000dab200, 0xc0011cf6b0, 0xc000c0f200, 0x21, 0x200, 0xc00020a7e0, 0xc000fa7c00) Apr 20 14:30:27 fsn dockerd[488555]: /build/docker.io-CrAKu8/docker.io-19.03.7+dfsg1/.gopath/src/github.com/miekg/dns/server.go:549 +0xb4 Apr 20 14:30:27 fsn dockerd[488555]: created by github.com/miekg/dns.(*Server).serveUDP Apr 20 14:30:27 fsn dockerd[488555]: /build/docker.io-CrAKu8/docker.io-19.03.7+dfsg1/.gopath/src/github.com/miekg/dns/server.go:479 +0x28c Apr 20 14:30:27 fsn systemd[1]: docker.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Still testing out, but https://github.com/SamWhited/libnetwork/commit/bea32b018c874ef35396ef46a3908ca0f9367d76 was merged in upstream, seems relevant and is part of upstream 19.03.8 So either apply that to 19.3.7 or update to 19.3.8? -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages docker.io depends on: ii adduser 3.118 ii iptables1.8.4-3 ii libc6 2.30-4 ii libdevmapper1.02.1 2:1.02.167-1+b1 ii libltdl72.4.6-14 ii libnspr42:4.25-1 ii libnss3 2:3.51-1 ii libseccomp2 2.4.3-1+b1 ii libsystemd0 245.5-1 ii lsb-base11.1.0 ii runc1.0.0~rc10+dfsg1-1 ii tini0.18.0-1+b1 Versions of packages docker.io recommends: ii ca-certificates 20190110 ii cgroupfs-mount 1.4 ii git 1:2.26.1-1 ii needrestart 3.5-1 ii xz-utils 5.2.4-1+b1 Versions of packages docker.io suggests: pn aufs-tools ii btrfs-progs5.6-1 ii debootstrap1.0.123 pn docker-doc ii e2fsprogs 1.45.6-1 pn rinse ii xfsprogs 5.4.0-1 ii zfsutils-linux [zfsutils] 0.8.3-2 -- no debconf information >From bea32b018c874ef35396ef46a3908ca0f9367d76 Mon Sep 17 00:00:00 2001 From: Sam Whited Date: Wed, 18 Mar 2020 12:06:23 -0400 Subject: [PATCH] Fixes a panic in the DNS resolver Under certain conditions it appears that the DNS response and returned error can be nil. When this happens, checking resp.Truncated results in a nil panic so we must first check that the response is not nil before checking if a truncated response was received. See moby/moby#40715 Signed-off-by: Sam Whited --- resolver.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/resolver.go b/resolver.go index 7e02a37a5b..
Bug#936873: Bug#727005: switch python bindings to python3
On 2020-03-18 15:13, Matthias Klose wrote: > swig3 had support for Python3, and now we have swig 4.0 in the archive. Any > update on this? I understood this to be for the debian hebrew packaging team, to approve and apply the patch submitted by Andreas Henriksson[1] (the related debian bug 727005). 1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727005#14 -- hkp://keys.gnupg.net CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
Bug#956959: closed by Debian FTP Masters (reply to Dmitry Smirnov ) (Bug#956959: fixed in xpra 3.0.9+dfsg1-1)
reopen 956959 found 956959 3.0.9+dfsg1-1 thanks On Mon, Apr 20, 2020 at 01:39:17AM +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the xpra package: > > #956959: can no longer connect after dist-upgrading server Hi, Unfortunately, 3.0.9 does not solve the problem. (I've upgraded both on the client and the server.) sesse@bigscreen:~$ xpra start ssh:sgunders@10.172.139.131 --start=urxvt 2020-04-21 09:59:40,056 Xpra GTK3 X11 client version 3.0.9-r26127 64-bit 2020-04-21 09:59:40,205 running on Linux Debian unstable sid 2020-04-21 09:59:40,206 window manager is 'Mutter (Muffin)' 2020-04-21 09:59:40,224 Warning: failed to import opencv: 2020-04-21 09:59:40,224 No module named 'cv2' 2020-04-21 09:59:40,224 webcam forwarding is disabled 2020-04-21 09:59:40,506 GStreamer version 1.16.2 for Python 3.8.2 64-bit 2020-04-21 09:59:40,587 No OpenGL_accelerate module loaded: No module named 'OpenGL_accelerate' 2020-04-21 09:59:40,898 OpenGL enabled with GeForce GTX 950/PCIe/SSE2 2020-04-21 09:59:41,169 Connected (version 2.0, client OpenSSH_8.2p1) 2020-04-21 09:59:41,827 Authentication (publickey) successful! 2020-04-21 09:59:42,466 missing some build information: cannot import name 'build_info' from 'xpra' (/usr/lib/python3/dist-packages/xpra/__init__.py) 2020-04-21 09:59:42,468 keyboard settings: rules=evdev, model=pc105, layout=no 2020-04-21 09:59:42,470 desktop size is 3840x2160 with 1 screen: 2020-04-21 09:59:42,470 :0.0 (1016x572 mm - DPI: 96x95) workarea: 3840x2120 2020-04-21 09:59:42,470 SAM HDMI-0 (521x293 mm - DPI: 187x187) 2020-04-21 09:59:42,512 Warning: the python netifaces package is missing 2020-04-21 09:59:42,630 Error: failed to receive anything, not an xpra server? 2020-04-21 09:59:42,630 could also be the wrong protocol, username, password or port 2020-04-21 09:59:42,630 or the session was not found 2020-04-21 09:59:42,631 Connection lost /* Steinar */ -- Homepage: https://www.sesse.net/
Processed: Re: Bug#956959 closed by Debian FTP Masters (reply to Dmitry Smirnov ) (Bug#956959: fixed in xpra 3.0.9+dfsg1-1)
Processing commands for cont...@bugs.debian.org:
> reopen 956959
Bug #956959 {Done: Dmitry Smirnov } [xpra] can no longer
connect after dist-upgrading server
'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 xpra/3.0.9+dfsg1-1.
> found 956959 3.0.9+dfsg1-1
Bug #956959 [xpra] can no longer connect after dist-upgrading server
Marked as found in versions xpra/3.0.9+dfsg1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
956959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Bug#954499 marked as pending in python-eventlet
Processing control commands:
> tag -1 pending
Bug #954499 [src:python-eventlet] python-eventlet: FTBFS: dh_auto_test: error:
pybuild --test --test-nose -i python{version} -p "3.7 3.8" returned exit code 13
Added tag(s) pending.
--
954499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#954499: marked as pending in python-eventlet
Control: tag -1 pending Hello, Bug #954499 in python-eventlet 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/python-eventlet/-/commit/3a164a05d82821ea81186b3334ace74d1c8be084 New upstream release (Closes: #954499). (this message was generated automatically) -- Greetings https://bugs.debian.org/954499
Bug#954258: marked as done (src:r-cran-ranger: fails to migrate to testing for too long)
Your message dated Tue, 21 Apr 2020 11:42:56 +0200 with message-id and subject line has caused the Debian Bug report #954258, regarding src:r-cran-ranger: fails to migrate to testing for too long 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.) -- 954258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-ranger Version: 0.11.2-1 Severity: serious Control: fixed -1 0.12.1-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:r-cran-ranger in its current version in unstable has been trying to migrate for 63 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have marked the version in unstable as fixing this bug, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=r-cran-ranger signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Last version is now in testing.--- End Message ---
Bug#954600: marked as done (graphite-api: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit code 13)
Your message dated Tue, 21 Apr 2020 11:07:16 +
with message-id
and subject line Bug#954600: fixed in graphite-api 1.1.3-6
has caused the Debian Bug report #954600,
regarding graphite-api: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.8 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.)
--
954600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: graphite-api
Version: 1.1.3-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye
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,sphinxdoc --buildsystem pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.8 setup.py config
> Warning: 'classifiers' should be a list, got type 'tuple'
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3 setup.py build
> Warning: 'classifiers' should be a list, got type 'tuple'
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8/build/graphite_api
> copying graphite_api/app.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api
> copying graphite_api/carbonlink.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api
> copying graphite_api/__init__.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api
> copying graphite_api/search.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api
> copying graphite_api/node.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api
> copying graphite_api/readers.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api
> copying graphite_api/storage.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api
> copying graphite_api/middleware.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api
> copying graphite_api/config.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api
> copying graphite_api/functions.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api
> copying graphite_api/intervals.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api
> copying graphite_api/encoders.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api
> copying graphite_api/utils.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api
> creating /<>/.pybuild/cpython3_3.8/build/graphite_api/_vendor
> copying graphite_api/_vendor/__init__.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api/_vendor
> copying graphite_api/_vendor/whisper.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api/_vendor
> creating /<>/.pybuild/cpython3_3.8/build/graphite_api/render
> copying graphite_api/render/datalib.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api/render
> copying graphite_api/render/__init__.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api/render
> copying graphite_api/render/grammar.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api/render
> copying graphite_api/render/glyph.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api/render
> copying graphite_api/render/attime.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api/render
> creating /<>/.pybuild/cpython3_3.8/build/graphite_api/finders
> copying graphite_api/finders/__init__.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api/finders
> copying graphite_api/finders/whisper.py ->
> /<>/.pybuild/cpython3_3.8/build/graphite_api/finders
> running egg_info
> creating graphite_api.egg-info
> writing graphite_api.egg-info/PKG-INFO
> writing dependency_links to graphite_api.egg-info/dependency_links.txt
> writing requirements to graphite_api.egg-info/requires.txt
> writing top-level names to graphite_api.egg-info/top_level.txt
> writing manifest file 'graphite_api.egg-info/SOURCES.txt'
> reading manifest file 'graphite_api.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '*' found under directory
> 'tests'
> writing manifest file 'graphite_api.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: python3.8 setup.py test
> Warning: 'classifiers' should be a list, got type 'tuple'
> running test
> WARNING: Testing via this command is deprecated and will be removed in a
> future version. Users looking for a generic test entry point independent of
> test runner are encouraged to use tox.
> running egg_info
> writing graphite_api.egg-info/PKG-INFO
> writing dependency_links to graphite_api.egg-info/dependency_links.txt
> writing
Bug#955176: marked as done (LGPL license missing)
Your message dated Tue, 21 Apr 2020 12:18:40 + with message-id and subject line Bug#955176: fixed in syrthes 4.3.5+20200129-dfsg1-1 has caused the Debian Bug report #955176, regarding LGPL license missing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 955176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: syrthes Version: 4.3.5+20200129-dfsg1-1~exp1 Severity: serious thanks Dear Maintainer, please add the missing LGPL licenses of some header files to your debian/copyright. Thanks! Thorsten --- End Message --- --- Begin Message --- Source: syrthes Source-Version: 4.3.5+20200129-dfsg1-1 Done: Gilles Filippini We believe that the bug you reported is fixed in the latest version of syrthes, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gilles Filippini (supplier of updated syrthes package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 21 Apr 2020 13:30:25 +0200 Source: syrthes Architecture: source Version: 4.3.5+20200129-dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Gilles Filippini Closes: 955176 957857 Changes: syrthes (4.3.5+20200129-dfsg1-1) unstable; urgency=medium . * Fix FTBFS with GCC-10 (closes: #957857) * d/copyright: Fix missing LGPL license statement (closes: #955176) * Compat level 12 . * Upload to unstable Checksums-Sha1: 8482124af7523babb410d841e88d6e56adde51b2 2206 syrthes_4.3.5+20200129-dfsg1-1.dsc e16dd8e7d7f2d8c186938f9749fd31006672e425 14176 syrthes_4.3.5+20200129-dfsg1-1.debian.tar.xz bf4e481288dfc6ae4029e0216ec83c80dbdd2c6e 13005 syrthes_4.3.5+20200129-dfsg1-1_amd64.buildinfo Checksums-Sha256: ceaf528055143a70f713e60202020d5a2a710805f369fa256a083d2e6ff525ed 2206 syrthes_4.3.5+20200129-dfsg1-1.dsc dba052c680e5ed38a859af00dc0962195629e6f599058b448d9d2b2fb973cda4 14176 syrthes_4.3.5+20200129-dfsg1-1.debian.tar.xz 1745fd86d1b73e37d886cf8f23edd9311b94c6fad041c972550cbd3af442eb81 13005 syrthes_4.3.5+20200129-dfsg1-1_amd64.buildinfo Files: 085507c3533a4f355dc27fc834eed9eb 2206 science optional syrthes_4.3.5+20200129-dfsg1-1.dsc df38d9355d16bbff5b4b885c5a58f451 14176 science optional syrthes_4.3.5+20200129-dfsg1-1.debian.tar.xz 18497ce0cf5ccbf2549ab75fd635a95e 13005 science optional syrthes_4.3.5+20200129-dfsg1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQFEBAEBCgAuFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAl6e4YsQHHBpbmlAZGVi aWFuLm9yZwAKCRDv6Gxsf/7Pg7oSB/9TRQ8yF2FRlg9t7KVrflIiGFD7oDvVqKsD 6VJ4BdgVUdJfE+w/XanfWmWo6XT4LantL3HyC8U3rJEFf3VYhprAHn0/qIaD9Xjs uyEYcEmoerrbHrckr1g1dwSo3+mLkgbLhNMRab1/yBXXHwmQKqXCMVuNgdu+gF7+ Wp/cM8oyhATgN6pkucir5GhY4upnp2Swh4FQSWG3xhQNZ9A9kaRsV4Laqbd3UGMX k1ZBmEtkXOZI5hC3QpdGP9ZQ6WtKGdSiy0zfDBJUcdwoxblDPwwvfWU9ZRvsxJoT ULnty7BN8f4Gi0RNfImKKp6v+R09PUzoua1feSKAF36LvNCcQ+RG =YTKl -END PGP SIGNATURE End Message ---
Bug#953376: Mailman 2 will be removed from Debian
Hi, On Sun, March 8, 2020 20:01, Scott Kitterman wrote: > Package: src:mailman > Version: 1:2.1.29-1 > Severity: serious > Justification: Policy 2.2.1 > > This package Depends/Build-Depends on python-dnspython which is an NBS > cruft package. Please update your package to use python3-dnspython, which > is still provided (if the package will be ported to python3). Mailman 2.1.x is Python 2 only. Upstream has explicitly indicated there will be no effort to port it to Python 3: https://mail.python.org/pipermail/mailman-users/2019-April/084333.html So it seems the time has come to remove Mailman 2 from Debian, and let people migrate to Mailman 3. Cheers, Thijs
Bug#958398: rust-xdg: autopkgtest failure, permission denied.
Package: rust-xdg
Version: 2.2.0-2
Severity: serious
rust-xdg's autopkgtest is failing
https://ci.debian.net/data/autopkgtest/unstable/amd64/r/rust-xdg/4759045/log.gz
test_runtime_good stdout
thread 'test_runtime_good' panicked at 'called `Result::unwrap()` on an `Err` value: Os {
code: 1, kind: PermissionDenied, message: "Operation not permitted" }',
src/libcore/result.rs:1165:5
stack backtrace:
0: ::fmt
1: core::fmt::write
2: std::io::Write::write_fmt
3: std::io::impls::>::write_fmt
4: std::panicking::default_hook::{{closure}}
5: std::panicking::default_hook
6: std::panicking::rust_panic_with_hook
7: std::panicking::continue_panic_fmt
8: rust_begin_unwind
9: core::panicking::panic_fmt
10: core::result::unwrap_failed
11: core::result::Result::unwrap
at /usr/src/rustc-1.40.0/src/libcore/result.rs:933
12: xdg::test_runtime_good
at src/lib.rs:775
13: xdg::test_runtime_good::{{closure}}
at src/lib.rs:766
14: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.40.0/src/libcore/ops/function.rs:227
15: as core::ops::function::FnOnce>::call_once
16: __rust_maybe_catch_panic
17: test::run_test_in_process
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose
backtrace.
I would guess that this needs a fix similar to
https://salsa.debian.org/rust-team/debcargo-conf/-/commit/d79e7153031cbb2485d722b7bf4aec9d33b9a61e
but implementing such a fix is beyond my skills.
This is blocking the migration of rust-xdg to testing and hence making newsboat
unbuildable in testing.
Processed: unarchiving 948215, reopening 948215, tagging 948215
Processing commands for cont...@bugs.debian.org:
> unarchive 948215
Bug #948215 {Done: Daniel Leidert } [jekyll] FTBFS after
ruby-i18n has been updated to version 1.x
Unarchived Bug 948215
> reopen 948215
Bug #948215 {Done: Daniel Leidert } [jekyll] FTBFS after
ruby-i18n has been updated to version 1.x
'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 jekyll/3.8.3+dfsg-7.
> tags 948215 + buster
Bug #948215 [jekyll] FTBFS after ruby-i18n has been updated to version 1.x
Added tag(s) buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
948215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#948215: marked as pending in jekyll
Control: tag -1 pending Hello, Bug #948215 in jekyll reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/jekyll/-/commit/3d727627cfe1caf54108d28353b7ea92d96c60f5 Add patch to allow Jekyll to run with ruby-i18n 1.x too * d/patches/0017-allow-jekyll-to-run-with-ruby-i18n-1.x.patch: Add patch. - Allow ruby-i18n 0.x and 1.x (closes: #948215). * d/patches/series: Add patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/948215
Processed: Bug#948215 marked as pending in jekyll
Processing control commands: > tag -1 pending Bug #948215 [jekyll] FTBFS after ruby-i18n has been updated to version 1.x Added tag(s) pending. -- 948215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958403: node-cross-spawn: unneeded for Debian, does risky path mangling, and does it wrong in current release 5.1.0
Package: node-cross-spawn Version: 5.1.0-2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 the sole purpose of Node.js module cross-spawn is to reimplement builtin Node.js functions child_process.sync and child_process.spawnSync compatible with Windows. Code involved mangling paths using regular expressions, which I fear can cause security issues if done wrong. Current release 5.1.0 seems to be doing it wrong for Unix (i.e. on platforms already implemented in Node.js), judging from changelog entries of later releases. According to its README.md, on Debian it should be possible to simply replace calls to cross-spawn.spawn with child_process.sync, and calls to cross-spawn.sync with child_process.spawnSync. Please let's avoid shipping this package with Bullseye and instead patch the (quite few, it seems) reverse dependencies to use node.js child_process() calls instead. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl6fA40ACgkQLHwxRsGg ASF3WA//TDcek1RTqzcH3ypFg5KiRa+/btpG2Wgr8Q/dC9pQ+FvrbncaARgiTsKP wWEx5ZxIHtGYgt3zCPYQPyrEmvauJ78yILCJhJyLCxrwTxHuXlz52/T7/WAyAjmm VKNPNOIZiLQGCfpiZ8VV5IaWL5KznUzRqXHQktg/qspByetOfXh4CV24HWo7UffJ OC8v4wbBOqmYqLlidkazeVIPpmwBukT9uSj/Q+/Nd5koE9H9jmvRfJb0/ExcSMgi XOPoPiHhgX6P9oUIPzjFL9ZpRF3QDIbxuEGV1VLt9l8DZQnrcJWIJ47fnvxTJtE9 OMPWS6qD8o4Ui18vJFJl/9sC5ZDdnmziWyMSLMWYNZg06cwMEWgJZChW2c04OCzN OzMzbaIxLpuDAWGVTbq4+6D7j3IJU5w7ZhFq48k1YCJ3tpWVm75hmiW0w4NBuqFB axdtJD4K2MDTaEDvqEg7o2MQJ+DbGaGpVKrYnTmh3llSmuBb4ImtfDhxuA6K7fTL pdy60x8ml4Kqq6doNy3cSBGlk42FWtY2kuqxF1+1b8/sXnW16j915Y9bnBYGxFBN 9zOieb6hPxF23W8kzkvxXOup4/0znTs7hJe8II36uyaOg1Wbc1MjhMUoHOkGtHcz Pqm9zH8bT5uV4WonaIbEZyNSkDUuZfbQmyKllFT5Gt3BSU30CM8= =64E7 -END PGP SIGNATURE-
Bug#953376: [Pkg-mailman-hackers] Bug#953376: Mailman 2 will be removed from Debian
Thijs Kinkhorst wrote: >On Sun, March 8, 2020 20:01, Scott Kitterman wrote: >> Package: src:mailman >> Version: 1:2.1.29-1 >> Severity: serious >> Justification: Policy 2.2.1 >> >> This package Depends/Build-Depends on python-dnspython which is an NBS >> cruft package. Please update your package to use python3-dnspython, >> which is still provided (if the package will be ported to python3). >Mailman 2.1.x is Python 2 only. >Upstream has explicitly indicated there will be no effort to port it to Python >3: >https://mail.python.org/pipermail/mailman-users/2019-April/084333.html >So it seems the time has come to remove Mailman 2 from Debian, and let people >migrate to Mailman 3. I thought this may be the case. I was looking at the possibility of whether I could build 2.1.30 even if it was to go in backports until the eventual removal of the package on the next Debian version, but would this removal cause problems for this? Andrew.
Bug#958408: etherape: crashes with "critical: read_all() failed on control socket"
Package: etherape Version: 0.9.18-1 Severity: grave Justification: renders package unusable Dear Maintainer, starting etherape with 'sudo /usr/bin/etherape -n -i wlp2s0', I get: EtherApe-INFO: 17:31:05.960: Protokoll sctp nicht unterstützt EtherApe-INFO: 17:31:05.961: Protokoll ddp nicht unterstützt EtherApe-INFO: 17:31:05.961: Protokoll ddp nicht unterstützt EtherApe-INFO: 17:31:05.962: Protokoll ddp nicht unterstützt EtherApe-INFO: 17:31:05.962: Protokoll ddp nicht unterstützt EtherApe-INFO: 17:31:06.255: Ergebnis von get_interface: »« EtherApe-INFO: 17:31:06.261: Verfügbare Schnittstellen für die Erfassung: usbmon5 usbmon4 usbmon3 usbmon2 usbmon1 nfqueue nflog lo any wlp2s0 enp1s0 EtherApe-INFO: 17:31:06.294: Verweistyp ist Ethernet EtherApe-INFO: 17:31:06.296: Diagramm gestartet EtherApe-INFO: 17:31:09.865: Neuer Knoten: IP: 10.0.1.4. Anzahl der Knoten 1 EtherApe-INFO: 17:31:09.866: Neuer Knoten: IP: 51.15.185.201. Anzahl der Knoten 2 unexpected EOF in read_all() critical: read_all() failed on control socket Speicherzugriffsfehler /var/log/syslog shows: Apr 21 17:31:06 debian kernel: [38534.252175] device wlp2s0 entered promiscuous mode Apr 21 17:31:06 debian dbus-daemon[378]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.80' (uid=0 pid=27621 comm="/usr/bin/etherape -n -i wlp2s0 ") Apr 21 17:31:06 debian systemd[1]: Starting Hostname Service... Apr 21 17:31:06 debian dbus-daemon[378]: [system] Successfully activated service 'org.freedesktop.hostname1' Apr 21 17:31:06 debian systemd[1]: Started Hostname Service. Apr 21 17:31:10 debian kernel: [38538.022726] etherape[27621]: segfault at 0 ip b6de3756 sp bfc87d18 error 4 in libc-2.28.so[b6ca1000+14e000] Apr 21 17:31:10 debian kernel: [38538.022758] Code: 66 90 66 90 57 8b 4c 24 08 66 0f 6e 4c 24 0c 66 0f ef d2 89 cf 66 0f 60 c9 66 0f 60 c9 83 e1 0f 66 0f 70 c9 00 74 4d 83 e7 f0 <66> 0f 6f 07 66 0f 74 d0 66 0f 74 c1 66 0f d7 d2 66 0f d7 c0 d3 fa Apr 21 17:31:10 debian kernel: [38538.047907] device wlp2s0 left promiscuous mode Apr 21 17:31:37 debian systemd[1]: systemd-hostnamed.service: Succeeded. What I have done so far: reinstalling - etherape (0.9.18-1) - etherape-data (0.9.18-1) - libgoocanvas-2.0-9 (2.0.4-1) - libgoocanvas-2.0-common (2.0.4-1) - libc6 (2.28-10) - libc6-dev (2.28-10) But no success! (In Debian Jessie I've used etherape for many years without problems) -- System Information: Debian Release: 10.3 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.19.0-8-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages etherape depends on: ii etherape-data0.9.18-1 ii libatk1.0-0 2.30.0-2 ii libc-ares2 1.14.0-1 ii libc62.28-10 ii libcairo-gobject21.16.0-4 ii libcairo21.16.0-4 ii libfribidi0 1.0.5-3.1+deb10u1 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgoocanvas-2.0-9 2.0.4-1 ii libgtk-3-0 3.24.5-1 ii libpango-1.0-0 1.42.4-7~deb10u1 ii libpangocairo-1.0-0 1.42.4-7~deb10u1 ii libpcap0.8 1.8.1-6 ii libpopt0 1.16-12 etherape recommends no packages. etherape suggests no packages. -- no debconf information
Bug#955081: marked as pending in deap
Control: tag -1 pending Hello, Bug #955081 in deap 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/deap/-/commit/4b6a0899db3b58784e5bf8a440289933785f24cf Add Adapt-conf.py-for-sphinx-2.0.patch Resolves a FTBFS with the new sphinx. (Closes: #955081) (this message was generated automatically) -- Greetings https://bugs.debian.org/955081
Processed: Bug#955081 marked as pending in deap
Processing control commands: > tag -1 pending Bug #955081 [src:deap] deap: FTBFS with Sphinx 2.4: ImportError: cannot import name 'algorithms' from 'deap' (../deap/__init__.py) Added tag(s) pending. -- 955081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#955054 marked as pending in pygments
Processing control commands: > tag -1 pending Bug #955054 [src:pygments] pygments: FTBFS with Sphinx 2.4: Theme error: An error happened in rendering the page docs/api. Added tag(s) pending. -- 955054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955081: marked as done (deap: FTBFS with Sphinx 2.4: ImportError: cannot import name 'algorithms' from 'deap' (../deap/__init__.py))
Your message dated Tue, 21 Apr 2020 17:33:48 +
with message-id
and subject line Bug#955081: fixed in deap 1.3.1-2
has caused the Debian Bug report #955081,
regarding deap: FTBFS with Sphinx 2.4: ImportError: cannot import name
'algorithms' from 'deap' (../deap/__init__.py)
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.)
--
955081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955081
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: deap
Version: 1.3.1-1
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx2.4
Hi,
deap fails to build with Sphinx 2.4, currently available in
experimental.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> PYTHONPATH=/<>/../ sphinx-build -b html -d _build/doctrees .
> _build/html
> Running Sphinx v2.4.3
> WARNING: Support for evaluating Python 2 syntax is deprecated and will be
> removed in Sphinx 4.0. Convert /<>/doc/conf.py to Python 3
> syntax.
> making output directory... done
> WARNING: favicon file 'deap_orange_icon_32.ico' does not exist
> loading intersphinx inventory from http://docs.python.org/objects.inv...
> loading intersphinx inventory from
> http://docs.scipy.org/doc/numpy/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'http://docs.scipy.org/doc/numpy/objects.inv' not
> fetchable due to :
> HTTPConnectionPool(host='127.0.0.1', port=9): Max retries exceeded with url:
> http://docs.scipy.org/doc/numpy/objects.inv (Caused by ProxyError('Cannot
> connect to proxy.', NewConnectionError(' object at 0x7f2db902bc70>: Failed to establish a new connection: [Errno 111]
> Connection refused')))
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'http://docs.python.org/objects.inv' not fetchable due
> to :
> HTTPConnectionPool(host='127.0.0.1', port=9): Max retries exceeded with url:
> http://docs.python.org/objects.inv (Caused by ProxyError('Cannot connect to
> proxy.', NewConnectionError(' 0x7f2db87cb100>: Failed to establish a new connection: [Errno 111] Connection
> refused')))
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 43 source files that are out of date
> updating environment: [new config] 43 added, 0 changed, 0 removed
> reading sources... [ 2%] about
> reading sources... [ 4%] api/algo
> reading sources... [ 6%] api/base
> reading sources... [ 9%] api/benchmarks
> reading sources... [ 11%] api/creator
> reading sources... [ 13%] api/gp
> reading sources... [ 16%] api/index
> reading sources... [ 18%] api/tools
> reading sources... [ 20%] contributing
> reading sources... [ 23%] examples/bipop_cmaes
> reading sources... [ 25%] examples/cmaes
> reading sources... [ 27%] examples/cmaes_plotting
> reading sources... [ 30%] examples/coev_coop
> reading sources... [ 32%] examples/eda
> reading sources... [ 34%] examples/es_fctmin
> reading sources... [ 37%] examples/es_onefifth
> reading sources... [ 39%] examples/ga_knapsack
> reading sources... [ 41%] examples/ga_onemax
> reading sources... [ 44%] examples/ga_onemax_numpy
> reading sources... [ 46%] examples/ga_onemax_short
> reading sources... [ 48%] examples/gp_ant
> reading sources... [ 51%] examples/gp_multiplexer
> reading sources... [ 53%] examples/gp_parity
> reading sources... [ 55%] examples/gp_spambase
> reading sources... [ 58%] examples/gp_symbreg
> reading sources... [ 60%] examples/index
> reading sources... [ 62%] examples/nsga3
> reading sources... [ 65%] examples/pso_basic
> reading sources... [ 67%] examples/pso_multiswarm
> reading sources... [ 69%] index
> reading sources... [ 72%] installation
> reading sources... [ 74%] overview
> reading sources... [ 76%] porting
> reading sources... [ 79%] releases
> reading sources... [ 81%] tutorials/advanced/benchmarking
> reading sources... [ 83%] tutorials/advanced/checkpoint
> reading sources... [ 86%] tutorials/advanced/constraints
> reading sources... [ 88%] tutorials/advanced/gp
> reading sources... [ 90%] tutorials/advanced/numpy
> reading sources... [ 93%] tutorials/basic/part1
> reading sources... [ 95%] tutorials/basic/part2
> reading sources... [ 97%] tutorials/basic/part3
> reading sources... [100%] tutorials/basic/part4
>
> WARNING: autodoc: failed to import module 'algorithms' from module 'deap';
> the following exception was raised:
> No module named 'tools'
> WARNING: autodoc: failed to import function 'algorithms.eaSimple' from module
> 'deap'; the fo
Bug#955054: marked as pending in pygments
Control: tag -1 pending Hello, Bug #955054 in pygments 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/pygments/-/commit/1c2457565eced489b16a59834a7a09806dd25ba1 Add Adapt-conf.py-for-sphinx-2.0.patch Resolves a FTBFS with the new sphinx. (Closes: #955054) (this message was generated automatically) -- Greetings https://bugs.debian.org/955054
Bug#955053: marked as done (scoop: FTBFS with Sphinx 2.4: Theme error: An error happened in rendering the page index.)
Your message dated Tue, 21 Apr 2020 17:35:03 + with message-id and subject line Bug#955053: fixed in scoop 0.7.1.1-7 has caused the Debian Bug report #955053, regarding scoop: FTBFS with Sphinx 2.4: Theme error: An error happened in rendering the page index. 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.) -- 955053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scoop Version: 0.7.1.1-6 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx2.4 Hi, scoop fails to build with Sphinx 2.4, currently available in experimental. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_install > I: pybuild base:217: /usr/bin/python3.7 setup.py install --root > /<>/debian/python3-scoop > running install > running build > running build_py > running install_lib > creating /<>/debian/python3-scoop > creating /<>/debian/python3-scoop/usr > creating /<>/debian/python3-scoop/usr/lib > creating /<>/debian/python3-scoop/usr/lib/python3.7 > creating /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages > creating > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop > copying /<>/.pybuild/cpython3_3.7_scoop/build/scoop/fallbacks.py > -> /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop > copying /<>/.pybuild/cpython3_3.7_scoop/build/scoop/shared.py -> > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop > copying > /<>/.pybuild/cpython3_3.7_scoop/build/scoop/encapsulation.py -> > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop > creating > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop/_comm > copying > /<>/.pybuild/cpython3_3.7_scoop/build/scoop/_comm/scoopexceptions.py > -> > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop/_comm > copying > /<>/.pybuild/cpython3_3.7_scoop/build/scoop/_comm/__init__.py -> > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop/_comm > copying > /<>/.pybuild/cpython3_3.7_scoop/build/scoop/_comm/scooptcp.py -> > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop/_comm > copying > /<>/.pybuild/cpython3_3.7_scoop/build/scoop/_comm/scoopzmq.py -> > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop/_comm > creating > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop/_comm/__pycache__ > copying > /<>/.pybuild/cpython3_3.7_scoop/build/scoop/_comm/__pycache__/__init__.cpython-37.pyc > -> > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop/_comm/__pycache__ > copying > /<>/.pybuild/cpython3_3.7_scoop/build/scoop/_comm/__pycache__/scoopzmq.cpython-37.pyc > -> > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop/_comm/__pycache__ > copying > /<>/.pybuild/cpython3_3.7_scoop/build/scoop/_comm/__pycache__/scoopexceptions.cpython-37.pyc > -> > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop/_comm/__pycache__ > copying /<>/.pybuild/cpython3_3.7_scoop/build/scoop/_debug.py -> > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop > copying /<>/.pybuild/cpython3_3.7_scoop/build/scoop/__init__.py > -> /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop > copying /<>/.pybuild/cpython3_3.7_scoop/build/scoop/__main__.py > -> /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop > creating > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop/launch > copying > /<>/.pybuild/cpython3_3.7_scoop/build/scoop/launch/__init__.py > -> > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop/launch > copying > /<>/.pybuild/cpython3_3.7_scoop/build/scoop/launch/brokerLaunch.py > -> > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop/launch > copying > /<>/.pybuild/cpython3_3.7_scoop/build/scoop/launch/workerLaunch.py > -> > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop/launch > creating > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop/discovery > copying > /<>/.pybuild/cpython3_3.7_scoop/build/scoop/discovery/__init__.py > -> > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop/discovery > creating > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop/discovery/__pycache__ > copying > /<>/.pybuild/cpython3_3.7_scoop/build/scoop/discovery/__pycache__/minusconf.cpython-37.pyc > -> > /<>/debian/python3-scoop/usr/lib/python3.7/dist-packages/scoop/discovery/__pycache__ > copying > /<>/.pybuild/cpython3_3.7_scoop/build/scoop/discovery/__pycache__
Bug#953376: [Pkg-mailman-hackers] Bug#953376: Mailman 2 will be removed from Debian
On Tue, April 21, 2020 18:02, Andrew Hodgson wrote: > Thijs Kinkhorst wrote: >>On Sun, March 8, 2020 20:01, Scott Kitterman wrote: >>> Package: src:mailman >>> Version: 1:2.1.29-1 >>> Severity: serious >>> Justification: Policy 2.2.1 >>> >>> This package Depends/Build-Depends on python-dnspython which is an NBS >>> cruft package. Please update your package to use python3-dnspython, >>> which is still provided (if the package will be ported to python3). > >>Mailman 2.1.x is Python 2 only. > >>Upstream has explicitly indicated there will be no effort to port it to >> Python 3: >>https://mail.python.org/pipermail/mailman-users/2019-April/084333.html > >>So it seems the time has come to remove Mailman 2 from Debian, and let >> people migrate to Mailman 3. > > I thought this may be the case. I was looking at the possibility of > whether I could build 2.1.30 even if it was to go in backports until the > eventual removal of the package on the next Debian version, but would this > removal cause problems for this? This is indeed not possible, because Backports requires package versions to come from testing and mailman is already no longer in testing. Continued support for any mailman 2.x packages needs to be outside of the Debian archive since Debian will have removed Python 2 both from stable and testing/unstable starting from the next release. Cheers, Thijs Cheers, Thijs
Bug#958352: marked as done (xfig: autopkgtest needs update for new version of debhelper: hidden problem)
Your message dated Tue, 21 Apr 2020 18:35:20 + with message-id and subject line Bug#958352: fixed in xfig 1:3.2.7b-3 has caused the Debian Bug report #958352, regarding xfig: autopkgtest needs update for new version of debhelper: hidden problem 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.) -- 958352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xfig Version: 1:3.2.7b-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, debhel...@packages.debian.org Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:debhelper Dear maintainer(s), With a recent upload of debhelper the autopkgtest of xfig fails in testing when that autopkgtest is run with the binary packages of debhelper from unstable. It passes when run with only packages from testing. In tabular form: passfail debhelper from testing13 xfig from testing1:3.2.7b-2 all others from testingfrom testing I copied some of the output at the bottom of this report. I don't spot anything in there, you may want to avoid redirecting to /dev/null during testing. Currently this regression is blocking the migration of debhelper to testing [1]. Of course, debhelper shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in debhelper was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from debhelper should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=debhelper https://ci.debian.net/data/autopkgtest/testing/amd64/x/xfig/5068355/log.gz autopkgtest [01:32:00]: test xfig-testsuite: [--- Running autoconf Running dh_auto_configure Building required test programs Running testsuite /bin/bash './testsuite' AUTOTEST_PATH='/usr/bin' ## --- ## ## xfig 3.2.7b test suite. ## ## --- ## Rudimentary tests 1: Report version ok 2: Validate desktop file ok Integration tests 3: ignore too many comment lines, ticket #47 ok Unit tests 4: Allow coordinates equal to INT_MIN FAILED (testsuite.at:82) 5: Test round_coords() FAILED (testsuite.at:87) ## - ## ## Test results. ## ## - ## ERROR: All 5 tests were run, 2 failed unexpectedly. ## -- ## ## testsuite.log was created. ## ## -- ## Please send `tests/testsuite.log' and all information you think might help: To: Subject: [xfig 3.2.7b] testsuite: 4 5 failed You may investigate any problem if you feel able to do so, in which case the test suite provides a good starting point. Its output may be found below `tests/testsuite.dir'. make: *** [Makefile:618: installcheck-local] Error 1 autopkgtest [01:32:05]: test xfig-testsuite: ---] autopkgtest [01:32:05]: test xfig-testsuite: - - - - - - - - - - results - - - - - - - - - - xfig-testsuite FAIL stderr: ERROR: All 5 tests were run, signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: xfig Source-Version: 1:3.2.7b-3 Done: Roland Rosenfeld We believe that the bug you reported is fixed in the latest version of xfig, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roland Rosenfeld (supplier of updated xfig 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
Bug#958415: src:mir-core: fails to migrate to testing for too long
Source: mir-core Version: 1.0.1-2 Severity: serious Control: close -1 1.0.2-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:mir-core in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=mir-core signature.asc Description: OpenPGP digital signature
Processed: src:mir-core: fails to migrate to testing for too long
Processing control commands: > close -1 1.0.2-1 Bug #958415 [src:mir-core] src:mir-core: fails to migrate to testing for too long Marked as fixed in versions mir-core/1.0.2-1. Bug #958415 [src:mir-core] src:mir-core: fails to migrate to testing for too long Marked Bug as done -- 958415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 948215 in 3.8.3+dfsg-7
Processing commands for cont...@bugs.debian.org: > fixed 948215 3.8.3+dfsg-7 Bug #948215 [jekyll] FTBFS after ruby-i18n has been updated to version 1.x Marked as fixed in versions jekyll/3.8.3+dfsg-7. > thanks Stopping processing here. Please contact me if you need assistance. -- 948215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925754: Fixed in newer release of libopenshot / libopenshot-audio
Control: block 925754 by 925755 Control: notforwarded 925754 Control: forwarded 925755 https://github.com/OpenShot/libopenshot-audio/issues/33 Hi, > On Wed, 29 Jan 2020 10:08:55 +0100 Matthias Klose wrote: > > libopenshot-audio 0.1.8 still fails to build > > Quite right, sorry. libopenshot-audio-0.1.8 fixed building with GCC *less > than* 9, > but GCC9 coming along broke it again. > > On Fedora / RPM Fusion we were building with commit 7001b68[1], > which was at the time an unreleased commit on the development branch. > > However, since then both 0.1.9 and 0.2.0 have been released, > including fixes to build with GCC 9 and 10 respectively, IIRC. > (I know 0.2.0 builds with GCC 10 for sure, since I've done it myself.) > > Current releases: > > libopenshot-audio-0.2.0: > https://github.com/OpenShot/libopenshot-audio/archive/v0.2.0.tar.gz > > libopenshot-0.2.5: > https://github.com/OpenShot/libopenshot/archive/v0.2.5.tar.gz > > OpenShot 2.5.1 (openshot-qt): > https://github.com/OpenShot/openshot-qt/archive/v2.5.1.tar.gz > > > [1]: > https://github.com/OpenShot/libopenshot-audio/commit/7001b68787c0881a44bcafba98cccae509a31644 libopenshot-audio builds with Clang without any modifications. Using this OpenShot (again with Clang) gets a bit farther: /usr/include/libopenshot-audio/JuceLibraryCode/modules/juce_audio_basics/../juce_core/unit_tests/juce_UnitTest.h:73:17: note: candidate found by name lookup is 'juce::UnitTest' class JUCE_API UnitTest ^ /<>/tests/Cache_Tests.cpp:50:2: error: reference to 'UnitTest' is ambiguous I've seen this is fixed in a commit upstream, and I think cherrypicking it helped, but the -audio Debian package uses the Juce embedded code copies instead of the ones in juce-modules-source as best as I can tell. I'm uneasy about this and hope that a new release of OpenShot made with the practices described in /usr/share/doc/juce-modules-source/README.Debian will make an elegant solution. signature.asc Description: This is a digitally signed message part.
Bug#952181: marked as done (pkg-config: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)
Your message dated Tue, 21 Apr 2020 19:03:39 + with message-id and subject line Bug#952181: fixed in pkg-config 0.29.2-1 has caused the Debian Bug report #952181, regarding pkg-config: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 952181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pkg-config Version: 0.29-6 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/check' > PASS: check-cflags > PASS: check-libs > PASS: check-mixed-flags > PASS: check-non-l-flags > PASS: check-define-variable > PASS: check-libs-private > PASS: check-requires-private > PASS: check-circular-requires > PASS: check-includedir > PASS: check-conflicts > PASS: check-missing > PASS: check-special-flags > PASS: check-sort-order > PASS: check-duplicate-flags > PASS: check-whitespace > PASS: check-cmd-options > PASS: check-version > PASS: check-requires-version > ../pkg-config --list-all : > 'sub1 Subdirectory package 1 - Test package 1 for subdirectory > broken Broken package - Module with broken .pc file > sub2 Subdirectory package 2 - Test package 2 for subdirectory' != 'sub1 > Subdirectory package 1 - Test package 1 for subdirectory > sub2 Subdirectory package 2 - Test package 2 for subdirectory > broken Broken package - Module with broken .pc file' > FAIL: check-print-options > PASS: check-path > PASS: check-sysroot > PASS: check-uninstalled > PASS: check-debug > PASS: check-gtk > PASS: check-tilde > PASS: check-relocatable > == > 1 of 26 tests failed > Please report to https://bugs.freedesktop.org/enter_bug.cgi?product=pkg-config > == > make[3]: *** [Makefile:427: check-TESTS] Error 1 > make[3]: Leaving directory '/<>/check' > make[2]: *** [Makefile:553: check-am] Error 2 > make[2]: Leaving directory '/<>/check' > make[1]: *** [Makefile:706: check-recursive] Error 1 > make[1]: Leaving directory '/<>' > dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2020/02/22/pkg-config_0.29-6_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: pkg-config Source-Version: 0.29.2-1 Done: Tollef Fog Heen We believe that the bug you reported is fixed in the latest version of pkg-config, 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 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tollef Fog Heen (supplier of updated pkg-config package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 21 Apr 2020 20:30:00 +0200 Source: pkg-config Architecture: source Version: 0.29.2-1 Distribution: unstable Urgency: medium Maintainer: Tollef Fog Heen Changed-By: Tollef Fog Heen Closes: 732797 922173 952181 Changes: pkg-config (0.29.2-1) unstable; urgency=medium . * New upstream version. Closes: #922173 - Fixes pkg.m4 output to report the modules that were missing. Closes: #732797 * Import patch from Philip Withnall to make print_package_list()'s output deterministic, to avoid breaking check/check-print-options. Closes: #952181. Checksums-Sha1: dfa5b25d36c315477b78c19ceeb71ff6a6406625 1771 pkg-config_0.29.2-1.dsc 76e501663b29cb7580245720edfb6106164fad2b 2016830 pkg-config_0.29.2.orig.tar.gz 8f864494b36ce23977e34d75336f2bff067dfb5b 9202 pkg-config_0.29.2-1.dif
Processed: src:olive-editor: fails to migrate to testing for too long
Processing control commands:
> close -1 20200210-1
Bug #958416 [src:olive-editor] src:olive-editor: fails to migrate to testing
for too long
Marked as fixed in versions olive-editor/20200210-1.
Bug #958416 [src:olive-editor] src:olive-editor: fails to migrate to testing
for too long
Marked Bug as done
> block -1 by 950564
Bug #958416 {Done: Paul Gevers } [src:olive-editor]
src:olive-editor: fails to migrate to testing for too long
958416 was not blocked by any bugs.
958416 was not blocking any bugs.
Added blocking bug(s) of 958416: 950564
--
958416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958416
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Fixed in newer release of libopenshot / libopenshot-audio
Processing control commands: > block 925754 by 925755 Bug #925754 [src:libopenshot] libopenshot: ftbfs with GCC-9 925754 was blocked by: 925723 925755 925754 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #925754 to the same blocks previously set > notforwarded 925754 Bug #925754 [src:libopenshot] libopenshot: ftbfs with GCC-9 Ignoring request to change the forwarded-to-address of bug#925754 to the same value > forwarded 925755 https://github.com/OpenShot/libopenshot-audio/issues/33 Bug #925755 [src:libopenshot-audio] libopenshot-audio: ftbfs with GCC-9 Ignoring request to change the forwarded-to-address of bug#925755 to the same value -- 925754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925754 925755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925755 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958416: src:olive-editor: fails to migrate to testing for too long
Source: olive-editor Version: 2019-1 Severity: serious Control: close -1 20200210-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 950564 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:olive-editor in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=olive-editor signature.asc Description: OpenPGP digital signature
Processed: Re: Fixed in newer release of libopenshot / libopenshot-audio
Processing control commands: > block 925754 by 925755 Bug #925754 [src:libopenshot] libopenshot: ftbfs with GCC-9 925754 was blocked by: 925723 925754 was not blocking any bugs. Added blocking bug(s) of 925754: 925755 > notforwarded 925754 Bug #925754 [src:libopenshot] libopenshot: ftbfs with GCC-9 Unset Bug forwarded-to-address > forwarded 925755 https://github.com/OpenShot/libopenshot-audio/issues/33 Bug #925755 [src:libopenshot-audio] libopenshot-audio: ftbfs with GCC-9 Set Bug forwarded-to-address to 'https://github.com/OpenShot/libopenshot-audio/issues/33'. -- 925754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925754 925755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925755 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: swi-prolog breaks eye autopkgtest: Failed 7/15 subtests
Processing control commands: > found -1 swi-prolog/8.1.28+dfsg-1 Bug #958419 [src:swi-prolog, src:eye] swi-prolog breaks eye autopkgtest: Failed 7/15 subtests Marked as found in versions swi-prolog/8.1.28+dfsg-1. > found -1 eye/19.0928.2249~ds-1 Bug #958419 [src:swi-prolog, src:eye] swi-prolog breaks eye autopkgtest: Failed 7/15 subtests Marked as found in versions eye/19.0928.2249~ds-1. -- 958419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958419: swi-prolog breaks eye autopkgtest: Failed 7/15 subtests
Source: swi-prolog, eye Control: found -1 swi-prolog/8.1.28+dfsg-1 Control: found -1 eye/19.0928.2249~ds-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of swi-prolog the autopkgtest of eye fails in testing when that autopkgtest is run with the binary packages of swi-prolog from unstable. It passes when run with only packages from testing. In tabular form: passfail swi-prolog from testing8.1.28+dfsg-1 eyefrom testing19.0928.2249~ds-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of swi-prolog to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=swi-prolog https://ci.debian.net/data/autopkgtest/testing/amd64/e/eye/5057663/log.gz autopkgtest [05:57:12]: test command1: prove debian/tests/*.t autopkgtest [05:57:12]: test command1: [--- # Failed test 'Process terminated without a signal' # at debian/tests/eye.pvm.t line 9. # got: '6' # expected: '0' # Failed test 'bare command, stderr' # at debian/tests/eye.pvm.t line 11. # '[FATAL ERROR: at Sun Apr 19 05:57:12 2020 # /usr/bin/eye.pvm: incompatible version (file: 66, Prolog: 67)] # ' # doesn't match '(?^:Usage: eye.pvm)' # Failed test 'Process terminated without a signal' # at debian/tests/eye.pvm.t line 13. # got: '6' # expected: '0' # Failed test 'help, stderr' # at debian/tests/eye.pvm.t line 15. # '[FATAL ERROR: at Sun Apr 19 05:57:12 2020 # /usr/bin/eye.pvm: incompatible version (file: 66, Prolog: 67)] # ' # doesn't match '(?^:Usage: eye.pvm)' # Failed test 'Process terminated without a signal' # at debian/tests/eye.pvm.t line 17. # got: '6' # expected: '0' # Failed test 'help, stderr' # at debian/tests/eye.pvm.t line 18. # '' # doesn't match '(?^:r:because)' # Failed test 'help, stderr' # at debian/tests/eye.pvm.t line 19. # '[FATAL ERROR: at Sun Apr 19 05:57:12 2020 # /usr/bin/eye.pvm: incompatible version (file: 66, Prolog: 67)] # ' # doesn't match '(?^s:starting .*\nGET .*\nnetworking .*\nreasoning)' # Looks like you failed 7 tests of 15. debian/tests/eye.pvm.t .. Dubious, test returned 7 (wstat 1792, 0x700) Failed 7/15 subtests Test Summary Report --- debian/tests/eye.pvm.t (Wstat: 1792 Tests: 15 Failed: 7) Failed tests: 2, 5, 7, 10, 12, 14-15 Non-zero exit status: 7 Files=1, Tests=15, 0 wallclock secs ( 0.03 usr 0.00 sys + 0.06 cusr 0.01 csys = 0.10 CPU) Result: FAIL autopkgtest [05:57:13]: test command1: ---] signature.asc Description: OpenPGP digital signature
Bug#958421: node-cli-boxes breaks node-boxen autopkgtest: TypeError: Invalid border style: single-double
Source: node-cli-boxes, node-boxen
Control: found -1 node-cli-boxes/2.2.0-2
Control: found -1 node-boxen/1.3.0-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of node-cli-boxes the autopkgtest of node-boxen
fails in testing when that autopkgtest is run with the binary packages
of node-cli-boxes from unstable. It passes when run with only packages
from testing. In tabular form:
passfail
node-cli-boxes from testing2.2.0-2
node-boxen from testing1.3.0-1
all others from testingfrom testing
I copied some of the output at the bottom of this report. As the
autopkgtest succeeds in unstable and node-boxen is blocked by the
migration of node-cli-boxen, I strongly believe that a *versioned*
(test) dependency and/or breaks is missing somewhere. If node-cli-boxes
really breaks node-boxen 1.3.0-1, it should add a versioned breaks.
After that, the migration software will test the combination from
unstable for the migration.
Currently this regression is blocking the migration of node-cli-boxes to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=node-cli-boxes
https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-boxen/5068858/log.gz
/usr/share/nodejs/boxen/index.js:48
throw new TypeError(`Invalid border style:
${borderStyle}`);
^
TypeError: Invalid border style: single-double
at getBorderChars (/usr/share/nodejs/boxen/index.js:48:10)
at module.exports (/usr/share/nodejs/boxen/index.js:86:16)
at Test.t
(/tmp/autopkgtest-lxc.ytsynf20/downtmp/autopkgtest_tmp/smokeAc3ms5/test.js:196:13)
at Test.bound [as _cb] (/usr/lib/nodejs/tape/lib/test.js:87:32)
at Test.run (/usr/lib/nodejs/tape/lib/test.js:106:10)
at Test.bound [as run] (/usr/lib/nodejs/tape/lib/test.js:87:32)
at Immediate.next (/usr/lib/nodejs/tape/lib/results.js:71:15)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
signature.asc
Description: OpenPGP digital signature
Processed: node-cli-boxes breaks node-boxen autopkgtest: TypeError: Invalid border style: single-double
Processing control commands: > found -1 node-cli-boxes/2.2.0-2 Bug #958421 [src:node-cli-boxes, src:node-boxen] node-cli-boxes breaks node-boxen autopkgtest: TypeError: Invalid border style: single-double Marked as found in versions node-cli-boxes/2.2.0-2. > found -1 node-boxen/1.3.0-1 Bug #958421 [src:node-cli-boxes, src:node-boxen] node-cli-boxes breaks node-boxen autopkgtest: TypeError: Invalid border style: single-double Marked as found in versions node-boxen/1.3.0-1. -- 958421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#956842: printrun: FTBFS with python 3.8
Hi, I need that package too, but it won't install right now. Please consider fixing it.
Bug#958423: php-defaults breaks php-codecoverage autopkgtest: Class 'DOMDocument' not found
Source: php-defaults, php-codecoverage Control: found -1 php-defaults/75 Control: found -1 php-codecoverage/7.0.10+dfsg-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of php-defaults the autopkgtest of php-codecoverage fails in testing when that autopkgtest is run with the binary packages of php-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail php-defaults from testing75 php-codecoverage from testing7.0.10+dfsg-1 all others from testingfrom testing I copied some of the output at the bottom of this report. The autopkgtest passes in unstable, so it seems that php-defaults needs to migrate together with some other package at the same time, but there's no package relation in place to force that. I reported a similar error message in bug #953727, but that was re-assigned to xdebug. Currently this regression is blocking the migration of php-defaults to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=php-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-codecoverage/5030079/log.gz autopkgtest [14:13:53]: test command1: mkdir --parents vendor ; cp debian/autoload.php vendor ; phpunit autopkgtest [14:13:53]: test command1: [--- Class 'DOMDocument' not found autopkgtest [14:13:54]: test command1: ---] signature.asc Description: OpenPGP digital signature
Processed: php-defaults breaks php-codecoverage autopkgtest: Class 'DOMDocument' not found
Processing control commands: > found -1 php-defaults/75 Bug #958423 [src:php-defaults, src:php-codecoverage] php-defaults breaks php-codecoverage autopkgtest: Class 'DOMDocument' not found Marked as found in versions php-defaults/75. > found -1 php-codecoverage/7.0.10+dfsg-1 Bug #958423 [src:php-defaults, src:php-codecoverage] php-defaults breaks php-codecoverage autopkgtest: Class 'DOMDocument' not found Marked as found in versions php-codecoverage/7.0.10+dfsg-1. -- 958423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: php-defaults breaks php-sabredav autopkgtest: Trying to access array offset on value of type bool
Processing control commands: > found -1 php-defaults/75 Bug #958424 [src:php-defaults, src:php-sabredav] php-defaults breaks php-sabredav autopkgtest: Trying to access array offset on value of type bool Marked as found in versions php-defaults/75. > found -1 php-sabredav/1.8.12-8 Bug #958424 [src:php-defaults, src:php-sabredav] php-defaults breaks php-sabredav autopkgtest: Trying to access array offset on value of type bool Marked as found in versions php-sabredav/1.8.12-8. -- 958424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958424: php-defaults breaks php-sabredav autopkgtest: Trying to access array offset on value of type bool
Source: php-defaults, php-sabredav Control: found -1 php-defaults/75 Control: found -1 php-sabredav/1.8.12-8 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of php-defaults the autopkgtest of php-sabredav fails in testing when that autopkgtest is run with the binary packages of php-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail php-defaults from testing75 php-sabredav from testing1.8.12-8 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of php-defaults to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=php-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-sabredav/5082295/log.gz There were 2 errors: 1) Sabre\DAV\Auth\Backend\AbstractDigestTest::testAuthenticateNoHeaders Trying to access array offset on value of type bool /usr/share/php/Sabre/HTTP/DigestAuth.php:125 /usr/share/php/Sabre/DAV/Auth/Backend/AbstractDigest.php:61 /tmp/autopkgtest-lxc.r33sttz0/downtmp/build.m2T/src/tests/Sabre/DAV/Auth/Backend/AbstractDigestTest.php:22 2) Sabre\HTTP\DigestAuthTest::testInvalidDigest2 Trying to access array offset on value of type bool /usr/share/php/Sabre/HTTP/DigestAuth.php:136 /usr/share/php/Sabre/HTTP/DigestAuth.php:100 /tmp/autopkgtest-lxc.r33sttz0/downtmp/build.m2T/src/tests/Sabre/HTTP/DigestAuthTest.php:164 signature.asc Description: OpenPGP digital signature
Processed: Re: adios: FTBFS (error: could not find mpi library for Fortran)
Processing control commands: > severity -1 serious Bug #955715 [src:adios] adios: FTBFS (error: could not find mpi library for Fortran) Severity set to 'serious' from 'important' -- 955715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 953697
Processing commands for cont...@bugs.debian.org: > close 953697 Bug #953697 [src:rust-derive-more] src:rust-derive-more: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937144: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).
On 4/20/20 2:51 PM, peter green wrote: > On 20/04/2020 08:57, Thomas Goirand wrote: >>> Option 1: fix all four packages to be python 2 free. >>> >>> Option 2: Remove python2 stuff from traceback2, python-funcsigs and >>> numba. Break the dependencies of nipype in sid. >>> >>> Option 3: Remove python2 stuff from traceback2, modify python-funcsigs >>> so it still builds the python2 package but does not run tests with >>> python 2. >> Funcsigs is a backport of the PEP 362 function signature features from >> Python 3.3's inspect module. > Thanks for the info. >> Python 2 has never been removed from this >> package. Though instead, we shall remove this source package entirely >> from Debian. > # Broken Depends: > nipype: python-nipype > pytest: pypy-pytest > python-logfury: python3-logfury > python-oslo.utils: python3-oslo.utils > > # Broken Build-Depends: > beaker: python3-funcsigs > kombu: python3-funcsigs > nipype: python-funcsigs > pagure: python3-funcsigs > pytest: pypy-funcsigs > python-oslo.log: python3-funcsigs > python-oslo.utils: python3-funcsigs (>= 0.4) > ripe-atlas-cousteau: python3-funcsigs You can remove all of the python-oslo* from the list. The versions in Experimental, which are the next version of OpenStack, are fixed. In 2 weeks of time, I'll upload all what I staged in Experimental to Sid (maybe 150 packages?) and that's going to fix it all. For the others, probably I should start filling bugs... > If what you say is correct then it sounds like the python3-funcsigs > revese depedencies could be dealt with fairly easily. > > But that still leaves the question of what to do about the dependency of > pytest on pypy-funcsigs ? should pypy modules be removed from pytest and > it's reverse-dependencies in the same way that regular python2 modules > were? how feasible is that? are pypy-* packages only useful with python2 > pypy or are they also useful with python3 pypy? I really don't know about pypy. Probably the pypy-pytest should indeed go away, as the initial plan was to switch to pypy3. Maybe tumbleweed (Stefano Rivera) would be able to answer. I'm adding him as Cc. >> Traceback2 *already* has Python 2 support removed in Sid. I uploaded >> this on the 21st of march, pressured by its potential autoremoval. > > Sorry it seems I got my package names mixed up when writing the list of > options. I said traceback2 where I meant unittest2. So, if I'm following correctly, what you seem to propose, is to remove Python 2 from unittest2. If that's the case, then I agree with such a plan. I just didn't dare to do it yet. Though in fact, I already worked on that, but stopped, also because unittest2 FTBFS when I try building it on my laptop. So I've pushed it in its normal Git repo [1] under a py2-removal branch. If anyone has some time available to look at it, that'd be nice (I currently don't...). Cheers, Thomas Goirand (zigo) [1] https://salsa.debian.org/python-team/modules/unittest2/
Bug#925755: Fixed in newer release of libopenshot / libopenshot-audio
On Tue, 21 Apr 2020 15:04:59 -0400 John Scott wrote: > > libopenshot-audio builds with Clang without any modifications. Using this > OpenShot (again with Clang) gets a bit farther: > /usr/include/libopenshot-audio/JuceLibraryCode/modules/juce_audio_basics/../juce_core/unit_tests/juce_UnitTest.h:73:17: note: candidate found by name lookup is 'juce::UnitTest' > class JUCE_API UnitTest > ^ > /<>/tests/Cache_Tests.cpp:50:2: error: reference to 'UnitTest' is ambiguous > > I've seen this is fixed in a commit upstream, and I think cherrypicking it > helped, but the -audio Debian package uses the Juce embedded code copies > instead of the ones in juce-modules-source as best as I can tell. What version of libopenshot is that result from? The Clang namespacing was fixed with the merge of 2a1fe80[1] on 2019-10-29, and would be included in both libopenshot-0.2.4 and libopenshot-0.2.5. That's a merge commit and it touches a bunch of files, but basically all of our headers now qualify juce symbols with the juce:: namespace prefix, and the test sources now #define DONT_SET_USING_JUCE_NAMESPACE which prevents JUCE from exporting its symbols into the global namespace. AFAICT that's the only way to prevent UnitTest++ and JUCE from clashing over ambiguous 'UnitTest' symbols. But all this should have been solved months ago. > I'm uneasy about this and hope that a new release of OpenShot made with the > practices described in /usr/share/doc/juce-modules-source/README.Debian will > make an elegant solution. Is there a copy of that file online somewhere? It's not part of the JUCE distribution as far as I can tell, and it's definitely not located at that path on my Fedora machine. [1]: https://github.com/OpenShot/libopenshot/commit/2a1fe80
Bug#937144: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).
Hi Thomas (2020.04.21_21:20:16_+) > > But that still leaves the question of what to do about the dependency of > > pytest on pypy-funcsigs ? should pypy modules be removed from pytest and > > it's reverse-dependencies in the same way that regular python2 modules > > were? how feasible is that? are pypy-* packages only useful with python2 > > pypy or are they also useful with python3 pypy? Pretty much, yes. pypy itself (the python 2.7 pypy) will continue to exist for the foreseeable future, to support building pypy3. But we don't need to ship modules for it. I'd be pretty happy if we had working virtualenv, and nothing else. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#954594: marked as done (golang-github-inconshreveable-log15: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/inconshreveable/log15 github.com/inconshreve
Your message dated Tue, 21 Apr 2020 21:35:46 + with message-id and subject line Bug#954594: fixed in golang-github-inconshreveable-log15 2.15-1 has caused the Debian Bug report #954594, regarding golang-github-inconshreveable-log15: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/inconshreveable/log15 github.com/inconshreveable/log15/ext github.com/inconshreveable/log15/term returned exit code 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.) -- 954594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954594 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-inconshreveable-log15 Version: 2.14-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200321 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=golang --with=golang >dh_update_autotools_config -O--buildsystem=golang >dh_autoreconf -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang >dh_auto_build -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 > github.com/inconshreveable/log15 github.com/inconshreveable/log15/ext > github.com/inconshreveable/log15/term > internal/race > runtime/internal/sys > runtime/internal/atomic > internal/cpu > sync/atomic > runtime/internal/math > unicode > internal/bytealg > unicode/utf8 > encoding > math/bits > internal/testlog > unicode/utf16 > math > internal/nettrace > runtime/cgo > runtime > internal/reflectlite > sync > internal/singleflight > math/rand > errors > sort > io > strconv > internal/oserror > vendor/golang.org/x/net/dns/dnsmessage > syscall > bytes > reflect > strings > internal/syscall/unix > time > github.com/inconshreveable/log15/term > context > internal/poll > internal/fmtsort > encoding/binary > os > encoding/base64 > golang.org/x/sys/unix > fmt > net > github.com/go-stack/stack > encoding/json > github.com/mattn/go-isatty > log > github.com/mattn/go-colorable > log/syslog > github.com/inconshreveable/log15 > github.com/inconshreveable/log15/ext >dh_auto_test -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 > github.com/inconshreveable/log15 github.com/inconshreveable/log15/ext > github.com/inconshreveable/log15/term > === RUN TestLazy > === PAUSE TestLazy > === RUN TestInvalidLazy > === PAUSE TestInvalidLazy > === RUN TestCtx > === PAUSE TestCtx > === RUN TestJson > === PAUSE TestJson > === RUN TestJSONMap > --- PASS: TestJSONMap (0.00s) > === RUN TestLogfmt > === PAUSE TestLogfmt > === RUN TestMultiHandler > === PAUSE TestMultiHandler > === RUN TestBufferedHandler > === PAUSE TestBufferedHandler > === RUN TestLogContext > === PAUSE TestLogContext > === RUN TestMapCtx > === PAUSE TestMapCtx > === RUN TestLvlFilterHandler > === PAUSE TestLvlFilterHandler > === RUN TestNetHandler > === PAUSE TestNetHandler > === RUN TestMatchFilterHandler > === PAUSE TestMatchFilterHandler > === RUN TestMatchFilterBuiltin > === PAUSE TestMatchFilterBuiltin > === RUN TestFailoverHandler > === PAUSE TestFailoverHandler > === RUN TestIndependentSetHandler > === PAUSE TestIndependentSetHandler > === RUN TestInheritHandler > === PAUSE TestInheritHandler > === RUN TestCallerFileHandler > === PAUSE TestCallerFileHandler > === RUN TestCallerFuncHandler > === PAUSE TestCallerFuncHandler > === RUN TestCallerStackHandler > === PAUSE TestCallerStackHandler > === RUN TestConcurrent > --- PASS: TestConcurrent (0.05s) > === CONT TestLazy > --- PASS: TestLazy (0.00s) > === CONT TestCallerStackHandler > TestCallerStackHandler: log15_test.go:555: Wrong context value, got > [/<>/obj-x86_64-linux-gnu/src/github.com/inconshreveable/log15/log15_test.go:523 > > /<>/obj-x86_64-linux-gnu/src/github.com/inconshreveable/log15/log15_test.go:526 > /usr/lib/go-1.14/src/testing/testing.go:992 > /usr/lib/go-1.14/src/runtime/asm_amd64.s:1373] expected string matching > [/<>/obj-x86_64-linux-gnu/src/github.com/inconshreveable/log15/log15_test.go:523 > > /<>/obj-x86_64-linux-gnu/src/github.com/inconshreveable/log15/log15_test.go:526] > === CONT TestLvlFilterHandler > === CONT TestIndependentSetHandler > --- PASS: TestIndependentSetHandler (0.00s) > === CONT TestMatchFilterBuiltin > --- FAIL: TestCallerStackHandler (0.00s) > === CONT TestMatchFilterHandler > --- PASS: TestMatchFilterBuiltin (0.00s) > === CONT TestNetHandler > === CONT T
Bug#955068: marked as done (skimage: FTBFS with Sphinx 2.4: dh_sphinxdoc: error: debian/python-skimage-doc/usr/share/doc/python-skimage-doc/html/./../dev/_static/docversions.js is missing)
Your message dated Tue, 21 Apr 2020 21:41:05 +
with message-id
and subject line Bug#955068: fixed in skimage 0.16.2-3
has caused the Debian Bug report #955068,
regarding skimage: FTBFS with Sphinx 2.4: dh_sphinxdoc: error:
debian/python-skimage-doc/usr/share/doc/python-skimage-doc/html/./../dev/_static/docversions.js
is missing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
955068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: skimage
Version: 0.16.2-2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx2.4
Hi,
skimage fails to build with Sphinx 2.4, currently available in
experimental.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> python3.8 tools/build_modref_templates.py
> /<>/doc/tools/apigen.py:205: UserWarning: Viewer requires Qt
> mod = __import__(uri, fromlist=[uri.split('.')[-1]])
> WARNING: Empty - skimage.external
> WARNING: Empty - skimage.scripts
> outdir:
> 27 files written
> Build API docs...done.
> Copying release notes
> python3.8 -m sphinx -b html -d build/doctrees -D mathjax_path=MathJax.js
> source build/html
> Running Sphinx v2.4.3
> Adding copy buttons to code blocks...
> making output directory... done
> [autosummary] generating autosummary for: api/api.rst, api/skimage.color.rst,
> api/skimage.data.rst, api/skimage.draw.rst, api/skimage.exposure.rst,
> api/skimage.external.tifffile.rst, api/skimage.feature.rst,
> api/skimage.filters.rank.rst, api/skimage.filters.rst,
> api/skimage.future.graph.rst, ..., user_guide/getting_started.rst,
> user_guide/numpy_images.rst, user_guide/plugins.rst,
> user_guide/transforming_image_data.rst,
> user_guide/tutorial_parallelization.rst,
> user_guide/tutorial_segmentation.rst, user_guide/tutorials.rst,
> user_guide/video.rst, user_guide/viewer.rst, values.rst
> loading intersphinx inventory from
> /usr/share/doc/python3.7/html/objects.inv...
> loading intersphinx inventory from ./_intersphinx/numpy-objects.inv...
> /usr/lib/python3.8/importlib/__init__.py:127: UserWarning: Viewer requires Qt
> return _bootstrap._gcd_import(name[level:], package, level)
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory '/usr/share/doc/python3.7/html/objects.inv' not
> fetchable due to : [Errno 2] No such file or
> directory: '/usr/share/doc/python3.7/html/objects.inv'
> loading intersphinx inventory from ./_intersphinx/scipy-objects.inv...
> loading intersphinx inventory from ./_intersphinx/sklearn-objects.inv...
> loading intersphinx inventory from
> /usr/share/doc/python-matplotlib-doc/html/objects.inv...
> generating gallery...
> generating gallery for auto_examples/data... [ 33%] plot_specific.py
> generating gallery for auto_examples/data... [ 66%] plot_scientific.py
> generating gallery for auto_examples/data... [100%] plot_general.py
>
> generating gallery for auto_examples/numpy_operations... [ 50%]
> plot_camera_numpy.py
> generating gallery for auto_examples/numpy_operations... [100%]
> plot_view_as_blocks.py
>
> generating gallery for auto_examples/color_exposure... [ 10%]
> plot_rgb_to_gray.py
> generating gallery for auto_examples/color_exposure... [ 20%]
> plot_rgb_to_hsv.py
> generating gallery for auto_examples/color_exposure... [ 30%]
> plot_histogram_matching.py
> generating gallery for auto_examples/color_exposure... [ 40%]
> plot_ihc_color_separation.py
> generating gallery for auto_examples/color_exposure... [ 50%]
> plot_adapt_rgb.py
> generating gallery for auto_examples/color_exposure... [ 60%]
> plot_regional_maxima.py
> generating gallery for auto_examples/color_exposure... [ 70%]
> plot_local_equalize.py
> generating gallery for auto_examples/color_exposure... [ 80%]
> plot_log_gamma.py
> generating gallery for auto_examples/color_exposure... [ 90%] plot_equalize.py
> generating gallery for auto_examples/color_exposure... [100%]
> plot_tinting_grayscale_images.py
>
> generating gallery for auto_examples/edges... [ 7%] plot_contours.py
> generating gallery for auto_examples/edges... [ 15%] plot_convex_hull.py
> generating gallery for auto_examples/edges... [ 23%] plot_canny.py
> generating gallery for auto_examples/edges... [ 30%] plot_marching_cubes.py
> generating gallery for auto_examples/edges... [ 38%] plot_ridge_filter.py
> generating gallery for auto_examples/edges... [ 46%] plot_active_contours.py
> generating gallery for auto_examples/edges... [ 53%] plot_shapes.py
> generating gall
Bug#955097: marked as done (yade: FTBFS with Sphinx 2.4: latex error)
Your message dated Tue, 21 Apr 2020 21:43:02 + with message-id and subject line Bug#955097: fixed in yade 2020.01a-7 has caused the Debian Bug report #955097, regarding yade: FTBFS with Sphinx 2.4: latex error to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 955097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yade Version: 2020.01a-6 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx2.4 Hi, yade fails to build with Sphinx 2.4, currently available in experimental. Relevant part (hopefully): > make[3]: Entering directory '/<>/debian/build' > make[3]: Nothing to be done for 'preinstall'. > make[3]: Leaving directory '/<>/debian/build' > Install the project... > /usr/bin/cmake -P cmake_install.cmake > -- Install configuration: "None" > -- Installing: /<>/debian/tmp/usr/bin/yade-batch > -- Installing: /<>/debian/tmp/usr/bin/yade > CMake Error: failed to create symbolic link '/usr/bin/yade.py': permission > denied > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/config.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/libVersions.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/__init__.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/DEM-PFV-check.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkAvoidSelfInteractionMask.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkBlockGen.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkCapillaryModels.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkClumpHopper.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkColliderConstantness.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkColliderCorrectness.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkDEM-PFVPressureInjection.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkGravity.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkJCFpm.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkLiquidMigration.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkList.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkLubrication.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkLubricationWithRoughness.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkMPI.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkPolyhedraCrush.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkPotentialBlocks.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkPotentialParticles.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkSaveLoadClumps.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkTestDummy.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkTestTriax.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkViscElEng.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkViscElPM.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkViscElPM2.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkWeight.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/checkWirePM.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/checks/check_TwoPhaseFlowEngine_PressureInjection.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/gui/testGui.sh > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/gui/testGuiEmpty.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/yade/py/yade/tests/gui/testGuiSimple.py > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-g
Bug#958419: marked as done (swi-prolog breaks eye autopkgtest: Failed 7/15 subtests)
Your message dated Tue, 21 Apr 2020 21:48:42 + with message-id and subject line Bug#958419: fixed in eye 20.0411.2226~ds-1 has caused the Debian Bug report #958419, regarding swi-prolog breaks eye autopkgtest: Failed 7/15 subtests 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.) -- 958419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: swi-prolog, eye Control: found -1 swi-prolog/8.1.28+dfsg-1 Control: found -1 eye/19.0928.2249~ds-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of swi-prolog the autopkgtest of eye fails in testing when that autopkgtest is run with the binary packages of swi-prolog from unstable. It passes when run with only packages from testing. In tabular form: passfail swi-prolog from testing8.1.28+dfsg-1 eyefrom testing19.0928.2249~ds-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of swi-prolog to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=swi-prolog https://ci.debian.net/data/autopkgtest/testing/amd64/e/eye/5057663/log.gz autopkgtest [05:57:12]: test command1: prove debian/tests/*.t autopkgtest [05:57:12]: test command1: [--- # Failed test 'Process terminated without a signal' # at debian/tests/eye.pvm.t line 9. # got: '6' # expected: '0' # Failed test 'bare command, stderr' # at debian/tests/eye.pvm.t line 11. # '[FATAL ERROR: at Sun Apr 19 05:57:12 2020 # /usr/bin/eye.pvm: incompatible version (file: 66, Prolog: 67)] # ' # doesn't match '(?^:Usage: eye.pvm)' # Failed test 'Process terminated without a signal' # at debian/tests/eye.pvm.t line 13. # got: '6' # expected: '0' # Failed test 'help, stderr' # at debian/tests/eye.pvm.t line 15. # '[FATAL ERROR: at Sun Apr 19 05:57:12 2020 # /usr/bin/eye.pvm: incompatible version (file: 66, Prolog: 67)] # ' # doesn't match '(?^:Usage: eye.pvm)' # Failed test 'Process terminated without a signal' # at debian/tests/eye.pvm.t line 17. # got: '6' # expected: '0' # Failed test 'help, stderr' # at debian/tests/eye.pvm.t line 18. # '' # doesn't match '(?^:r:because)' # Failed test 'help, stderr' # at debian/tests/eye.pvm.t line 19. # '[FATAL ERROR: at Sun Apr 19 05:57:12 2020 # /usr/bin/eye.pvm: incompatible version (file: 66, Prolog: 67)] # ' # doesn't match '(?^s:starting .*\nGET .*\nnetworking .*\nreasoning)' # Looks like you failed 7 tests of 15. debian/tests/eye.pvm.t .. Dubious, test returned 7 (wstat 1792, 0x700) Failed 7/15 subtests Test Summary Report --- debian/tests/eye.pvm.t (Wstat: 1792 Tests: 15 Failed: 7) Failed tests: 2, 5, 7, 10, 12, 14-15 Non-zero exit status: 7 Files=1, Tests=15, 0 wallclock secs ( 0.03 usr 0.00 sys + 0.06 cusr 0.01 csys = 0.10 CPU) Result: FAIL autopkgtest [05:57:13]: test command1: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: eye Source-Version: 20.0411.2226~ds-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of eye, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated eye package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 21 Apr 2
Processed: RFS: fdkaac/1.0.0-1 [RC] -- command line encoder frontend for libfdk-aac
Processing control commands: > block 955248 by -1 Bug #955248 [src:fdkaac] fdkaac: FTBFS against fdk-aac 2.0.1-1 955248 was not blocked by any bugs. 955248 was not blocking any bugs. Added blocking bug(s) of 955248: 958428 -- 955248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955248 958428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955248: fdkaac: diff for NMU version 1.0.0-0.1
Håvard Flaget Aasen writes: > Control: tags 955248 + patch > Control: tags 955248 + pending > > > Dear maintainer, > I've prepared an NMU for fdkaac (versioned as 1.0.0-0.1) and uploaded it > to mentors. Please feel free to tell me if I should delete it. Dear Håvard, Thanks for preparing a package. I've updated the upstream version to 1.0.0 in my git repository and uploaded a package to mentors. You can now delete the NMU from mentors. -- Marius Gavrilescu
Processed: closing 843137
Processing commands for cont...@bugs.debian.org: > close 843137 Bug #843137 [sbuild] sbuild: fails to deal with sid chroots (missing gpg) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 843137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958430: Vagrant libvirt image debian/buster64 version 10.3.0 grub error
Package: cloud.debian.org Severity: grave Justification: renders package unusable Dear Maintainer, The libvirt image debian/buster64 version 10.3.0 fails to boot an gives grub error below. No files seems to be available under /boot Booting from Hard Disk... error: file `/boot/grub/i386-pc/normal.mod' not found. Entering rescue mode... grub rescue> ls (hd0,msdos1)/boot grub rescue> Thanks, Pascal
Processed: py2removal bugs severity updates - 2020-04-21 23:51:24.549470+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # and https://lists.debian.org/debian-python/2019/12/msg00076.html > # and https://lists.debian.org/debian-python/2020/03/msg00087.html > # mail threads for more details on this severity update > # python-sqlalchemy is a module and has 0 external rdeps or not in testing > # python-sqlalchemy-ext is a module and has 0 external rdeps or not in testing > severity 938555 serious Bug #938555 [src:sqlalchemy] sqlalchemy: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 938555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#885518: marked as done (lptools: Recommends unmaintained pygtk)
Your message dated Wed, 22 Apr 2020 02:33:48 + with message-id and subject line Bug#885518: fixed in lptools 0.2.0-6 has caused the Debian Bug report #885518, regarding lptools: Recommends unmaintained pygtk 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.) -- 885518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885518 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lptools Version: 0.2.0-2 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject Introspection bindings (and gtk3). For more information on GObject Introspection see [1] and [2]. Please try to do this before the Buster release as we're going to try to remove pygtk this cycle. If you have any question don't hesitate to ask. [1] https://wiki.gnome.org/Projects/GObjectIntrospection [2] https://wiki.gnome.org/Projects/PyGObject On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Source: lptools Source-Version: 0.2.0-6 Done: =?utf-8?q?Jelmer_Vernoo=C4=B3?= We believe that the bug you reported is fixed in the latest version of lptools, 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 885...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jelmer Vernooij (supplier of updated lptools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 22 Apr 2020 01:42:55 + Source: lptools Architecture: source Version: 0.2.0-6 Distribution: unstable Urgency: medium Maintainer: Nathan Handler Changed-By: Jelmer Vernooij Closes: 885518 Changes: lptools (0.2.0-6) unstable; urgency=medium . * Drop recommends of deprecated pygtk, as well as the two scripts that use it: lp-review-notifier and lp-review-list. Closes: #885518 * Update standards version to 4.5.0, no changes needed. * Set Bug-Database / Bug-Submit fields. * Set Rules-Requires-Root. Checksums-Sha1: 87bbcbb75e0c1be1d3948289fe9133fae0fa0d29 1926 lptools_0.2.0-6.dsc 7b8778cf14c890b67de6e4c4ea668c5763d529ad 9048 lptools_0.2.0-6.debian.tar.xz 76a17b41ec2d1165f8b9a763c984d658c0694516 6010 lptools_0.2.0-6_amd64.buildinfo Checksums-Sha256: 1358c0dfdd14d4f33f8e72a901e0a2326f781bb6fd24c612081a1837a21464c1 1926 lptools_0.2.0-6.dsc c35ef03b73a20f84326eeb4ef807ff8ff5017dc12e33f5db884d39ead3f58c20 9048 lptools_0.2.0-6.debian.tar.xz d98637a809e60bc22ed2cba24ccd79fa634961725b78149f58f0fd2c68bc8c42 6010 lptools_0.2.0-6_amd64.buildinfo Files: 684879b3b82de2c08f46250bbcd19d2c 1926 python optional lptools_0.2.0-6.dsc 946f508d4ed0afcdfeaec7ad4e16d7ea 9048 python optional lptools_0.2.0-6.debian.tar.xz 2852d301544d14ab470ae32fe93747f8 6010 python optional lptools_0.2.0-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAl6foa0ACgkQV5wWDUye I+jmAA//SxQW86BW65c6cchIq/z3BaGG4PUaklGuGpV8g5wLvMNnTDR0Ec84ALOu 4jgqD8a1FzO1QjxZM4I1wNB/aL9tcGczn+Lb+FPiXllZT7BBbfwZlz8Dov/ohTpl Nr8rrhsMKdbdnl3g8QSfJBWhLvosyb+v2XUAuhMBnpxSlcqUuep5IMfJsHKb8SJj e1UHB0yNqoZ43tTGEvBI3hrUrTghgIH7MXSmgPwah9TH30dfJJRearNW2uupycdb suzPc/1ox1Qz+U9Fp3l702Rc60n/iO0PXYTspFZxFjMl+qo/XSYTrjnAot53ePw2 NsbUitESNWIEJOwir2djQrjIXy4qwb1FotGhPc5xlKGyuJ9E0mmawvnggsYXvGVr h8c3A94lqs7AO6QvtE0PE5h7/h3klaaBpxHO7IetScnhaJnKNrkNztrbttt2mMdx g2GbBFSSuZ/RKPDGo07JX1OiS+FWLW3yvte/osCXdCdz6HfYfumvtazdd23ydW5J icnJw7V2aMHE963WhUecLkPCVeStJRC9dHMSKoewE7kGRafINi+bxpzSM4tk7mUV 4WvP2brAeWqHVGFEpAPRVK1Z/t6Sg9BJjYXNefViH33B9wrBS58qvzk2U84Ny5bl 6kDu2RuzajlkUK0b5tB/FTaKurCDEt9pOu+RNltYM3uFntDdpOI= =6L8b -END PGP SIGNATURE End Message ---
Bug#947564: marked as done (FTBFS with scons 3.1.2-1)
Your message dated Tue, 21 Apr 2020 23:34:00 -0400
with message-id <6d4f97f03f62a009b98f3e9ce0af66ab800a0101.ca...@debian.org>
and subject line Re: Fixed in gpick_0.2.6~rc1-2
has caused the Debian Bug report #947564,
regarding FTBFS with scons 3.1.2-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.)
--
947564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gpick
Version: 0.2.6~rc1-1
Severity: important
Usertags: scons_ftbfs
Hello,
in the context of the change to Python3 also Scons was revised. With
the current version 3.1.2-1 from Experimental the changeover is
finished so far.
However, an error occurred while building your package. The build log
is attached.
Please check it and fix the error.
CU
Jörg
--
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56
Old pgp Key: BE581B6E (revoked since 2014-12-31).
Jörg Frings-Fürst
D-54470 Lieser
git: https://jff.email/cgit/
Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst
My wish list:
- Please send me a picture from the nature at your home.
dpkg-checkbuilddeps: error: Unmet build dependencies: libdbus-glib-1-dev (>=
0.76) libboost-dev lemon ragel libboost-test-dev libboost-system-dev
libboost-filesystem-dev
[1;33mW: Unmet build-dependency in source[0m
dh clean
debian/rules override_dh_clean
make[1]: Entering directory
'/data/entwicklung/linux/debian/trans_scons/gpick-0.2.6~rc1'
dh_testdir
dh_testroot
scons -c -C src
Could not change directory to
/data/entwicklung/linux/debian/trans_scons/gpick-0.2.6~rc1/src
scons: Entering directory
`/data/entwicklung/linux/debian/trans_scons/gpick-0.2.6~rc1/src'
scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Cleaning targets ...
scons: done cleaning targets.
Removing autogenerated file .sconsign.dblite
find -name "*.pyc" -delete
rm -f build-stamp configure-stamp
rm -rf .sconsign.dblite config.log .sconf_temp/ build/
dh_clean
make[1]: Leaving directory
'/data/entwicklung/linux/debian/trans_scons/gpick-0.2.6~rc1'
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building gpick using existing ./gpick_0.2.6~rc1.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building gpick in gpick_0.2.6~rc1-1.debian.tar.xz
dpkg-source: info: building gpick in gpick_0.2.6~rc1-1.dsc
[0mI: Generating source changes file for original dsc[0m
dpkg-genchanges: info: including full source code in upload
[1;33mW: cgroups are not available on the host, not using them.[0m
[0mI: pbuilder: network access will be disabled during build[0m
[0mI: Current time: Fri Dec 27 13:37:12 CET 2019[0m
[0mI: pbuilder-time-stamp: 1577450232[0m
[0mI: Building the build Environment[0m
[0mI: extracting base tarball [/var/cache/pbuilder/sid-amd64-base.tgz][0m
[0mI: copying local configuration[0m
[0mI: mounting /proc filesystem[0m
[0mI: mounting /sys filesystem[0m
[0mI: creating /{dev,run}/shm[0m
[0mI: mounting /dev/pts filesystem[0m
[0mI: redirecting /dev/ptmx to /dev/pts/ptmx[0m
[0mI: Mounting /var/cache/debs[0m
[0mI: policy-rc.d already exists[0m
[1;33mW: Could not create compatibility symlink because /tmp/buildd exists and
it is not a directory[0m
[0mI: Obtaining the cached apt archive contents[0m
[0mI: Copying source file[0m
[0mI: copying [../gpick_0.2.6~rc1-1.dsc][0m
[0mI: copying [../gpick_0.2.6~rc1.orig.tar.gz][0m
[0mI: copying [../gpick_0.2.6~rc1-1.debian.tar.xz][0m
[0mI: Extracting source[0m
dpkg-source: warning: extracting unsigned source package (gpick_0.2.6~rc1-1.dsc)
dpkg-source: info: extracting gpick in gpick-0.2.6~rc1
dpkg-source: info: unpacking gpick_0.2.6~rc1.orig.tar.gz
dpkg-source: info: unpacking gpick_0.2.6~rc1-1.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 01_reproducible_build.patch
dpkg-source: info: applying 02_desktop_file.patch
dpkg-source: info: applying 04_appdata_file_path.patch
[0mI: using fakeroot in build.[0m
[0mI: Installing the build-deps[0m
[0mI: user script /var/cache/pbuilder/build//571568/tmp/hooks/D05deps
starting[0m
Get:1 file:/var/cache/debs ./ InRelease
Ign:1 file:/var/cache/debs ./ InRelease
Get:2 file:/var/cache/debs ./ Release
Ign:2 file:/var/cache/debs ./ Release
Get:3 file:/var/cache/debs ./ Packages
Ign:3 file:/var/cache/debs ./ Packag
Bug#937144: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).
On Tue, Apr 21, 2020 at 11:20:16PM +0200, Thomas Goirand wrote: > You can remove all of the python-oslo* from the list. The versions in > Experimental, which are the next version of OpenStack, are fixed. In 2 > weeks of time, I'll upload all what I staged in Experimental to Sid > (maybe 150 packages?) and that's going to fix it all. Will the new OpenStack version also fix this issue? #955116 python-murano-pkg-check: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx' object has no attribute 'info' -- Valentin
Bug#958191: patch
Control: tag -1 patch I've opened a merge request [1] addressing this. [1] https://salsa.debian.org/debian/dracut/-/merge_requests/1
Processed: patch
Processing control commands: > tag -1 patch Bug #958191 [dracut] processor microcode is not loaded (not dracut: early cpio is not produced) Added tag(s) patch. -- 958191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942988: displaycal: Python2 removal in sid/bullseye
On 17 avril 2020 11:32, Scott Talbert wrote: [...] > It looks like upstream doesn't seem to be making much progress on > this. Do you think that we need to start working on Python 3 support > ourselves? Duplicate work is a bad idea. Otherwise upstream is still active in displaycal forums (18/04/2020) : https://hub.displaycal.net/forums/topic/battery-life/ Christian
