Processed: reassign 944854 to cyrus-common, notfound 944705 in 1.0.7+ds-1, found 944705 in 1.0.7+ds1-1 ...
Processing commands for cont...@bugs.debian.org:
> reassign 944854 cyrus-common 3.0.8-6+deb10u1
Bug #944854 [cyrus-common (3.0.8-6+deb10u1) ...] cyrus-common (3.0.8-6+deb10u1)
skiplist Unknown type of DB: BACKUP
Warning: Unknown package '3.0.8-6+deb10u1'
Warning: Unknown package '...'
Bug reassigned from package 'cyrus-common (3.0.8-6+deb10u1) ...' to
'cyrus-common'.
Ignoring request to alter found versions of bug #944854 to the same values
previously set
Ignoring request to alter fixed versions of bug #944854 to the same values
previously set
Bug #944854 [cyrus-common] cyrus-common (3.0.8-6+deb10u1) skiplist Unknown type
of DB: BACKUP
Marked as found in versions cyrus-imapd/3.0.8-6+deb10u1.
> notfound 944705 1.0.7+ds-1
Bug #944705 [python3-mako] alembic: failing tests with python3.8
There is no source info for the package 'python3-mako' at version '1.0.7+ds-1'
with architecture ''
Unable to make a source version for version '1.0.7+ds-1'
No longer marked as found in versions 1.0.7+ds-1.
> found 944705 1.0.7+ds1-1
Bug #944705 [python3-mako] alembic: failing tests with python3.8
Marked as found in versions mako/1.0.7+ds1-1.
> tags 942858 + sid bullseye
Bug #942858 [python3-leveldb] Doesn't support Python 3.8: SystemError: bad call
flags
Added tag(s) bullseye and sid.
> tags 942899 + sid bullseye experimental
Bug #942899 [src:joblib] joblib 0.14.0 is required for Python 3.8 support
Added tag(s) experimental, bullseye, and sid.
> tags 944026 + sid bullseye
Bug #944026 [python3-freezegun] freezegun: failing tests with python3.8
Added tag(s) bullseye and sid.
> tags 944995 + sid bullseye
Bug #944995 [src:gtkimageview] gtkimageview FTBFS: error: ‘GTypeDebugFlags’ is
deprecated
Added tag(s) sid and bullseye.
> notfound 944911 1.00-3+b1
Bug #944911 [src:libfiu] libfiu: FBTFS: Found too many matching python3 bindings
The source 'libfiu' and version '1.00-3+b1' do not appear to match any binary
packages
No longer marked as found in versions libfiu/1.00-3+b1.
> found 944911 1.00-3
Bug #944911 [src:libfiu] libfiu: FBTFS: Found too many matching python3 bindings
Marked as found in versions libfiu/1.00-3.
> tags 944872 + sid bullseye
Bug #944872 [src:libindicator] libindicator FTBFS: error: G_ADD_PRIVATE
[-Werror]
Added tag(s) bullseye and sid.
> tags 944853 + sid bullseye
Bug #944853 {Done: Sandro Knauß } [src:calligra] calligra:
FTBFS with Qt 5.12
Added tag(s) bullseye and sid.
> tags 934482 + sid bullseye buster
Bug #934482 [src:prctl] prctl: probably shouldn't be in testing/stable
Added tag(s) buster, bullseye, and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
934482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934482
942858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942858
942899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942899
944026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944026
944705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944705
944853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944853
944854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944854
944872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944872
944911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944911
944995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#944572: marked as done (simka: debian/rules does not trap for errors)
Your message dated Mon, 18 Nov 2019 07:05:26 +
with message-id
and subject line Bug#944572: fixed in simka 1.5.1-2
has caused the Debian Bug report #944572,
regarding simka: debian/rules does not trap for errors
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.)
--
944572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:simka
Version: 1.5.1-1
Severity: serious
Tags: patch
Dear maintainer: The debian/rules file for this package has a "for"
which does not always trap errors if they happen. To see why this
is a problem, compare the following two Makefile snippets:
for command in false true; do $${command}; done
echo MARK
for command in true false; do $${command}; done
echo MARK
The first one will succeed, the second one will not, but
in fact none of them should really succeed.
The simple patch below should fix this.
Please see Debian Policy 4.6. "Error trapping in makefiles"
for a more complete explanation:
https://www.debian.org/doc/debian-policy/ch-source.html#error-trapping-in-makefiles
Thanks.
--- a/debian/rules
+++ b/debian/rules
@@ -15,7 +15,7 @@ override_dh_install:
rm -r debian/tmp/usr/example \
debian/tmp/usr/scripts
chrpath --delete debian/simka/usr/bin/*
- for file in debian/simkamin/usr/share/simkamin/*.py; do mv "$$file"
"$${file%%.py}"; done
+ set -e; for file in debian/simkamin/usr/share/simkamin/*.py; do mv
"$$file" "$${file%%.py}"; done
mv debian/simkamin/usr/share/simkamin/simkaMin_utils
debian/simkamin/usr/share/simkamin/simkaMin_utils.py
override_dh_fixperms:
--- End Message ---
--- Begin Message ---
Source: simka
Source-Version: 1.5.1-2
We believe that the bug you reported is fixed in the latest version of
simka, 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 944...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Shayan Doust (supplier of updated simka package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Nov 2019 07:05:39 +0100
Source: simka
Binary: simka simkamin
Architecture: source
Version: 1.5.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Shayan Doust
Description:
simka - comparative metagenomics method dedicated to NGS datasets
simkamin - approximate comparative metagenomics method dedicated to NGS data
Closes: 944572
Changes:
simka (1.5.1-2) unstable; urgency=medium
.
[ Steffen Moeller ]
* d/u/metadata: yamllint
* Update metadata with ref to conda
.
[ Shayan Doust ]
* Fix debian/rules not trapping for errors (Closes: #944572)
* Specify architectures that can build this package
* More verbose output and slight change to simkamin.install
.
[ Andreas Tille ]
* Standards-Version: 4.4.1
* Remove trailing whitespace in debian/rules
* Set upstream metadata fields: Repository.
Checksums-Sha1:
1ff27e97964ecaaff512ab44ef1cc2f85189fb67 2191 simka_1.5.1-2.dsc
3157592ef3db566354f1e37f9a2d019f1d026d34 20580 simka_1.5.1-2.debian.tar.xz
Checksums-Sha256:
a64b14ea7b40d6a5c16bc1b120a1a06b5060bdb42f84eaca0c492e482b62db2f 2191
simka_1.5.1-2.dsc
59c00483c1772e134535d371c85b88e074307c5768912c8074cd974630eae4ca 20580
simka_1.5.1-2.debian.tar.xz
Files:
c0cb963d78fdae54178bda183de8c179 2191 science optional simka_1.5.1-2.dsc
ffa8cfa42c80ec14a689fcab8f6260b6 20580 science optional
simka_1.5.1-2.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl3SPfgOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtHZMw//bilvC4hKdGew9crx3W0Nnb+AIoUg94iApFIl
psLRqNEm9MMonNd4CSFd54ARg6Kho92US15X20BgCv99leH3WZmcWM4gvm8UK09m
L2WmN5Q2W+BY13+gVbKQ5Uc9TQmA7ycmBPrbT7R/tbUgm5vLg1IyBmTLuvH6S0CW
Nd8WQRY2S9Fg5mhEuQfvWsYUNNv21u7a0P4bSQ5aQiuqbluDRuYE3C79Y4q3zoSr
M8gNyJ6jKmX0+4Oj2JEEMAQwtxFFSybvbJtxq1Nb3eWvW4I5rZ4YyYyQAUYsYjVg
4v+IsXBiKKJ5cMWvvpCaPekFxLCqV0j2LV+uGgPpkfCfErztH0yMoj5wsHnqvoKj
vYY/g3UNgI6KuWxqJIAPvEqEf5iVD96nBLiDS1NkmuZfkCi/i7+OhwglvTrWWLQZ
ahB77hkcf2As7VMKvhjypENmJdGmhuPlZLDdw4+e5W9Rx7OiheiojShXWk/Zhkkl
Bug#942235: Adding Python 3.8 as a supported Python3 version
On 18.11.19 07:52, Alastair McKinstry wrote: > So I've uploaded a python-xarray 0.14.0-2 which passes on python3.7. > > Its failing on python 3.8 but apparently due to pandas not ready on 3.8, so it > should be ok to pass as the transition completes. > > xarray really needs dask >= 2.0 but version 1 is in unstable; I've disabled > some > functionality (dask='parallelize') and marked some tests xfail until this is > done. > > Alastair yes, people are aware of a needed dask update, see #942235. There's now also a dask 2.8 release available, I didn't look at that yet. > On 07/11/2019 14:08, Matthias Klose wrote: >> This weekend, I am planning to upload python3-defaults, adding python3.8 as a >> supported Python3 version. This may introduce some churn in unstable until >> the basic binNMUs are available as well. >> >> >> - python-xarray #944044. 1.4 is already broken with Python 3.7. For >> Ubuntu I fell back to 1.2.1. 1.2.3 might work as well, still seeing >> one or two test failures. >> >> Packages building on top of numpy/scipy/pandas, like the PyAstro stack, >> continue to work with these updates, despite some new test failures. >> >> Matthias >> >> [1] https://wiki.debian.org/Python/Python3.8. >> [2] >> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=python3.8;users=debian-pyt...@lists.debian.org >> >>
Processed: raise severity of issues for Python 3.8, now a supported Python3 version
Processing commands for cont...@bugs.debian.org: > severity 942684 serious Bug #942684 [src:mod-wsgi] mod-wsgi needs a new upstream version to support python3.8 Severity set to 'serious' from 'important' > severity 942685 serious Bug #942685 [src:netifaces] fix installation of 3.8 extensions Severity set to 'serious' from 'important' > severity 942686 serious Bug #942686 [src:python-apsw] fix the installation of 3.8 extensions Severity set to 'serious' from 'important' > severity 942693 serious Bug #942693 [src:python-hypothesis] new upstream version needed to support python 3.8 Severity set to 'serious' from 'important' > severity 942708 serious Bug #942708 [src:python-nacl] update pynacl for recent hypothesis version Severity set to 'serious' from 'important' > severity 942714 serious Bug #942714 [src:pycxx] pycxx needs fix for python3.8 header installation Severity set to 'serious' from 'important' > severity 942744 serious Bug #942744 [src:gst-python1.0] fix python-config call to get flags for embedded build Severity set to 'serious' from 'important' > severity 942766 serious Bug #942766 [src:matplotlib] matplotlib should error out when failing to build/install Severity set to 'serious' from 'important' > severity 942791 serious Bug #942791 [src:pymssql] fix pymssql for python 3.8 Severity set to 'serious' from 'important' > severity 942794 serious Bug #942794 [src:python-scipy] scipy ftbfs trying to build the docs with python3.8 Severity set to 'serious' from 'important' > severity 942804 serious Bug #942804 [src:petsc4py] fix build with python3.8 Severity set to 'serious' from 'important' > severity 943418 serious Bug #943418 [src:python-xlrd] python3.8 dropped time.clock() Severity set to 'serious' from 'important' > severity 943442 serious Bug #943442 [src:reprozip] reprozip needs a new upstream version for Python 3.8 Severity set to 'serious' from 'important' > severity 943495 serious Bug #943495 [src:setools] fix building with a new compiler warning when building for python3.8 Severity set to 'serious' from 'important' > severity 943501 serious Bug #943501 [src:python-xlrd] ftbfs with python3.8 (test failure) Severity set to 'serious' from 'important' > severity 943611 serious Bug #943611 [src:cegui-mk2] cegui-mk2 fails to package extensions for python 3.8 Severity set to 'serious' from 'important' > severity 943832 serious Bug #943832 [src:asyncpg] asyncpg fails tests with python3.8 Severity set to 'serious' from 'important' > severity 943966 serious Bug #943966 [cookiecutter] cookiecutter: failing tests with python3.8 Severity set to 'serious' from 'important' > severity 944026 serious Bug #944026 [python3-freezegun] freezegun: failing tests with python3.8 Severity set to 'serious' from 'important' > severity 944160 serious Bug #944160 [src:python-pulp] Fix time.clock import for python3.8 Severity set to 'serious' from 'important' > severity 944242 serious Bug #944242 [src:python-biopython] fix build & test issues with Python 3.8 Severity set to 'serious' from 'important' > severity 944250 serious Bug #944250 [src:python-jsonrpc] fix tests with python3.8 Severity set to 'serious' from 'important' > severity 944320 serious Bug #944320 [src:python-blosc] platform.linux_distribution is gone in 3.8 Severity set to 'serious' from 'important' > severity 943609 serious Bug #943609 [src:breezy] breezy ftbfs with python 3.8 Severity set to 'serious' from 'important' > severity 942678 serious Bug #942678 [src:subvertpy] subvertpy ftbfs with python 3.8 (tests) Severity set to 'serious' from 'important' > severity 942858 serious Bug #942858 [python3-leveldb] Doesn't support Python 3.8: SystemError: bad call flags Severity set to 'serious' from 'important' > severity 942899 serious Bug #942899 [src:joblib] joblib 0.14.0 is required for Python 3.8 support Severity set to 'serious' from 'important' > severity 943334 serious Bug #943334 [src:dh-python] please run the tests for all supported python versions Severity set to 'serious' from 'important' > severity 943608 serious Bug #943608 [src:beancount] tests segfault when run with Python 3.8 Severity set to 'serious' from 'important' > severity 943613 serious Bug #943613 [src:pygame] pygame doesn't find tests when run with python3.8 Severity set to 'serious' from 'important' > severity 943614 serious Bug #943614 [src:python-cytoolz] cytoolz ftbfs with python3.8 Severity set to 'serious' from 'important' > severity 943615 serious Bug #943615 [src:python-multidict] python-multidict ftbfs with python3.8 (test failures) Severity set to 'serious' from 'important' > severity 943619 serious Bug #943619 [src:python-skbio] test failures when running with python3.8 Severity set to 'serious' from 'important' > severity 943620 serious Bug #943620 [src:gammapy] gammapy's tests fail with numpy-1.17 and python3.8 Severity set to 'serious' from 'important' > severity 943621 serious Bug #943621 [src:uvloop] uvloop needs an update for python 3.8 Severity set to
Bug#944894: marked as done (/usr/bin/dh_python2: is a #!/usr/bin/python script but does not depend on python)
Your message dated Mon, 18 Nov 2019 06:50:22 + with message-id and subject line Bug#944894: fixed in python-defaults 2.7.17-2 has caused the Debian Bug report #944894, regarding /usr/bin/dh_python2: is a #!/usr/bin/python script but does not depend on python 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.) -- 944894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python2 Version: 2.7.17-1 Severity: serious File: /usr/bin/dh_python2 Justification: Policy 3.5 Control: affects -1 src:dbus-python As instructed by the py2removal mass-bug-filing templates, I have been removing references to python from packages I maintain, and replacing them with references to python2 if the Python 2 modules are still needed. This seems to have caused dbus-python to FTBFS when NMU'd for the python3.8 transition: https://buildd.debian.org/status/fetch.php?pkg=dbus-python=amd64=1.2.12-1%2Bb1=1573984727=0 > Unpacking python2 (2.7.17-1) ... ... > Unpacking dh-python (4.20191017) ... ... >debian/rules override_dh_python2 > make[1]: Entering directory '/<>' > py3versions: no X-Python3-Version in control file, using supported versions > dh_python2 > make[1]: dh_python2: Command not found > make[1]: *** [debian/rules:214: override_dh_python2] Error 127 /usr/bin/dh_python2 is in the python2 binary package, which is installed, so this "command not found" shouldn't be caused by absence of /usr/bin/dh_python2. As far as I can work out, it's actually caused by the absence of the interpreter named in its first line, which is /usr/bin/python (shells do not make it easy to distinguish between these two failure modes). dbus-python no longer build-depends on python, so /usr/bin/python2.7 and /usr/bin/python2 exist in the build environment, but /usr/bin/python does not. I think /usr/bin/dh_python2 should now be a #!/usr/bin/python2 (or maybe #!/usr/bin/python2.7) script, instead of a #!/usr/bin/python script. Regards, smcv Complete list of package versions from sbuild log: adduser_3.118 apt_1.8.4 apt-transport-https_1.8.4 autoconf_2.69-11 autoconf-archive_20190106-2 automake_1:1.16.1-4 autopoint_0.19.8.1-9 autotools-dev_20180224.1 base-files_11 base-passwd_3.5.46 bash_5.0-5 binutils_2.33.1-2 binutils-common_2.33.1-2 binutils-x86-64-linux-gnu_2.33.1-2 bsdmainutils_11.1.2+b1 bsdutils_1:2.34-0.1 build-essential_12.8 bzip2_1.0.8-2 ca-certificates_20190110 coreutils_8.30-3+b1 cpp_4:9.2.1-3.1 cpp-9_9.2.1-19 dash_0.5.10.2-6 dbus_1.12.16-2 debconf_1.5.73 debhelper_12.7.1 debian-archive-keyring_2019.1 debianutils_4.9 dh-autoreconf_19 dh-python_4.20191017 dh-strip-nondeterminism_1.6.2-1 diffutils_1:3.7-3 docbook-xml_4.5-9 docbook-xsl_1.79.1+dfsg-2 dpkg_1.19.7 dpkg-dev_1.19.7 dwz_0.13-2 e2fsprogs_1.45.4-1 fakeroot_1.24-1 fdisk_2.34-0.1 file_1:5.37-6 findutils_4.7.0-1 g++_4:9.2.1-3.1 g++-9_9.2.1-19 gcc_4:9.2.1-3.1 gcc-9_9.2.1-19 gcc-9-base_9.2.1-19 gettext_0.19.8.1-9 gettext-base_0.19.8.1-9 gir1.2-glib-2.0_1.62.0-2 gpgv_2.2.17-3 grep_3.3-1 groff-base_1.22.4-3 gzip_1.9-3+b1 hostname_3.23 init-system-helpers_1.57 intltool-debian_0.35.0+20060710.5 libacl1_2.2.53-5 libapparmor1_2.13.3-7 libapt-pkg5.0_1.8.4 libarchive-zip-perl_1.67-1 libasan5_9.2.1-19 libatomic1_9.2.1-19 libattr1_1:2.4.48-5 libaudit-common_1:2.8.5-2 libaudit1_1:2.8.5-2 libbinutils_2.33.1-2 libblkid-dev_2.34-0.1 libblkid1_2.34-0.1 libbsd0_0.10.0-1 libbz2-1.0_1.0.8-2 libc-bin_2.29-3 libc-dev-bin_2.29-3 libc6_2.29-3 libc6-dev_2.29-3 libcap-ng0_0.7.9-2.1 libcc1-0_9.2.1-19 libcom-err2_1.45.4-1 libcroco3_0.6.13-1 libdb5.3_5.3.28+dfsg1-0.6 libdbus-1-3_1.12.16-2 libdbus-1-dev_1.12.16-2 libdebconfclient0_0.250 libdebhelper-perl_12.7.1 libdpkg-perl_1.19.7 libelf1_0.176-1.1 libexpat1_2.2.9-1 libexpat1-dev_2.2.9-1 libext2fs2_1.45.4-1 libfakeroot_1.24-1 libfdisk1_2.34-0.1 libffi-dev_3.2.1-9 libffi6_3.2.1-9 libfile-stripnondeterminism-perl_1.6.2-1 libgcc-9-dev_9.2.1-19 libgcc1_1:9.2.1-19 libgcrypt20_1.8.5-3 libgdbm-compat4_1.18.1-5 libgdbm6_1.18.1-5 libgirepository-1.0-1_1.62.0-2 libglib2.0-0_2.62.2-3 libglib2.0-bin_2.62.2-3 libglib2.0-data_2.62.2-3 libglib2.0-dev_2.62.2-3 libglib2.0-dev-bin_2.62.2-3 libgmp10_2:6.1.2+dfsg-4 libgnutls30_3.6.10-4 libgomp1_9.2.1-19 libgpg-error0_1.36-7 libhogweed5_3.5.1+really3.5.1-2 libicu63_63.2-2 libidn2-0_2.2.0-2 libisl21_0.21-2 libitm1_9.2.1-19 libjs-jquery_3.3.1~dfsg-3 libjs-sphinxdoc_1.8.5-3 libjs-underscore_1.9.1~dfsg-1 liblsan0_9.2.1-19 liblz4-1_1.9.2-2 liblzma5_5.2.4-1+b1 libmagic-mgc_1:5.37-6 libmagic1_1:5.37-6 libmount-dev_2.34-0.1 libmount1_2.34-0.1
Bug#944249: gnuplot-mode does not work with emacs26
Thanks for the patches, Agustin. I just tried it out. Works for the most part. One thing that doesn't work for me is (gnuplot-mode) being executed when opening a .gp file. You added this to the package, and the dh-elpa machinery is creating the appropriate file: /etc/emacs/site-start.d/50elpa-gnuplot-mode.el I don't think this is being evaluated, however. Is it working for you? Do you know at which point in the emacs startup sequence this is sourced? Is it always supposed to be sourced? What about 'emacs -q'? Or 'emacs -Q'? Thanks
Bug#944949: dbus-python: needs an explicit build dependency on dh-python
On 17.11.19 20:53, Simon McVittie wrote: > Control: tags 944949 + moreinfo > > On Sun, 17 Nov 2019 at 19:07:39 +, Matthias Klose wrote: >> Please add an explicit build dependency on dh-python. > > As far as I can see it's been explicit since 2015. Is anything more > needed here? > > Note that the FTBFS with > > dh_python2 > make[1]: dh_python2: Command not found > > seems to be because /usr/bin/dh_python2 is a #!/usr/bin/python script in > a package that doesn't depend on python (#944894). The misleading > "Command not found" is similar to this: > > $ cat > Makefile > all: > ./script > $ cat > script > #!/usr/bin/does-not-exist > $ chmod +x script > $ make > ./script > make: ./script: Command not found > make: *** [Makefile:2: all] Error 127 > > I have a workaround which I believe should still be harmless after > dh_python2 moves out of python2 (presumably into dh-python?), which I'll > upload soon. > > If that doesn't work, I'll temporarily re-add the python B-D so the > python3.8 transition can go through, and remove it after #944894 is > resolved. > > It's unfortunate that the python3.8 transition, the effort to replace > references to python2 with python, and the migration of dh_python2 from > python2 to dh-python (?) are happening at the same time and affect > overlapping sets of packages. Perhaps one (or more) of these could be > deferred until one of the others has been done? this specific issue is unrelated. dh_python2.py was calling python, not python2. now fixed in an interim upload. Still waiting for feedback from my co-maintainer how to proceed with the dropped dh-python dependency in python3-defaults.
Bug#933932: marked as done (RM: strongwind -- RoQA; dead upstream; python2-only; last MU in 2012)
Your message dated Mon, 18 Nov 2019 06:10:21 + with message-id and subject line Bug#933932: Removed package(s) from unstable has caused the Debian Bug report #933932, regarding RM: strongwind -- RoQA; dead upstream; python2-only; last MU in 2012 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.) -- 933932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: strongwind Version: 0.9-2 Severity: serious Justification: unmaintained Hello, The state of the strongwind package is questionable. It has not been updated since feb 2012, and upstream does not exist any more. It is still using python2 syntax, and depends on python-pyatspi which is to be removed. strongwind happened to be removed from testing in 2018 due to some pyatspi2 dependency (see #896341), but that was fixed. I'm however questioning whether we should keep the package at all given its abandon state? Samuel -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: python-strongwind |0.9-2.1 | all strongwind |0.9-2.1 | source --- Reason --- RoQA; dead upstream; python2-only; last MU in 2012 -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 933...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/933932 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#944995: gtkimageview FTBFS: error: ‘GTypeDebugFlags’ is deprecated
Source: gtkimageview Version: 1.6.4+dfsg-2 Severity: serious Tags: ftbfs gtkimageview fails to cross build from source in unstable. The crucial bit is: | /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is deprecated [-Werror=deprecated-declarations] | 236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags); | | ^~~~ This is a problem, because gtkimageview builds with -Werror. Reproducible by reproducible builds: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/gtkimageview_1.6.4+dfsg-2.rbuild.log.gz Reproducible by crossqa: http://crossqa.debian.net/build/gtkimageview_1.6.4+dfsg-2_ppc64el_20191014234854.log As a first measure, dropping -Werror will likely make it build again, then you likely need to fix #618962 and drop the gtk2 variant. Helmut
Bug#944768: marked as done (gnome-shell-extension-hijra: Uninstallable)
Your message dated Mon, 18 Nov 2019 02:58:46 + with message-id <5dd208e6a85ae_3b02ac60b1dd0d441...@godard.mail> and subject line Bug#944768 fixed in hijra has caused the Debian Bug report #944768, regarding gnome-shell-extension-hijra: Uninstallable 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.) -- 944768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hijra Version: 0.4.1-2 X-Debugs-CC: aelmahmo...@users.sourceforge.net Severity: serious gnome-shell-extension-hijra depends on gnome-shell (<< 3.31) but Debian Testing has gnome-shell 3.34. The extension looks simple enough that I think you could probably drop the upper dependency limit to avoid this issue every 6 months when we package a new gnome-shell version. I was unable to test this extension because of https://bugs.debian.org/944767 Thanks, Jeremy Bicha --- End Message --- --- Begin Message --- Hello, Bug #944768 in hijra reported by you has been fixed in the Git repository. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/islamic-team/hijra/commit/30533c40bcf6b252abdc9f6649e3a441b8226216 Drop gnome-shell upper limit dependency Closes: #944768 (this message was generated automatically) -- Greetings https://bugs.debian.org/944768--- End Message ---
Bug#944768: marked as pending in hijra
Control: tag -1 pending Hello, Bug #944768 in hijra 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/islamic-team/hijra/commit/30533c40bcf6b252abdc9f6649e3a441b8226216 Drop gnome-shell upper limit dependency Closes: #944768 (this message was generated automatically) -- Greetings https://bugs.debian.org/944768
Processed: Bug#944768 marked as pending in hijra
Processing control commands:
> tag -1 pending
Bug #944768 {Done: أحمد المحمودي } [src:hijra]
gnome-shell-extension-hijra: Uninstallable
Added tag(s) pending.
--
944768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944768
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#944939: marked as done (pyfribidi: needs an explicit build dependency on dh-python)
Your message dated Mon, 18 Nov 2019 02:56:12 + with message-id and subject line Bug#944939: fixed in pyfribidi 0.12.0+repack-3 has caused the Debian Bug report #944939, regarding pyfribidi: needs an explicit build dependency on dh-python 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.) -- 944939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pyfribidi Version: 0.12.0+repack-2 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python. --- End Message --- --- Begin Message --- Source: pyfribidi Source-Version: 0.12.0+repack-3 We believe that the bug you reported is fixed in the latest version of pyfribidi, 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 944...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. أحمد المحمودي (Ahmed El-Mahmoudy) (supplier of updated pyfribidi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 18 Nov 2019 03:05:21 +0100 Source: pyfribidi Binary: python3-pyfribidi Architecture: source Version: 0.12.0+repack-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) Description: python3-pyfribidi - FriBidi Python bindings Closes: 944939 Changes: pyfribidi (0.12.0+repack-3) unstable; urgency=medium . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat. * Bump Standards-Version to 4.4.1. . [ أحمد المحمودي (Ahmed El-Mahmoudy) ] * Add Rules-Requires-Root: no * Add dh-python to build deps (Closes: #944939) Checksums-Sha1: 1f21530bb51b028a9fc152177ddc405054998ecf 1946 pyfribidi_0.12.0+repack-3.dsc 21c416c5b3b5a2e86f2931b2cc98bdcf0c704ec1 4588 pyfribidi_0.12.0+repack-3.debian.tar.xz 852d58dfb9e6560796ec2d2d71fd435928cbef76 4957 pyfribidi_0.12.0+repack-3_source.buildinfo Checksums-Sha256: 07e37a32bf5bf4464cc0b6542b752ae1a530d0728f061ea3a8c5941420157a94 1946 pyfribidi_0.12.0+repack-3.dsc 81acd7a2881ae414429db892adc46c432829a5c9a657da292230026841ae2ba7 4588 pyfribidi_0.12.0+repack-3.debian.tar.xz f94cb2583017ecdbd4cf02556f45eb06abc086111a25c82f97cb6f1be81faea3 4957 pyfribidi_0.12.0+repack-3_source.buildinfo Files: 72eb541d16954e6f35e5eec19cc3e6e3 1946 python optional pyfribidi_0.12.0+repack-3.dsc 6340995b4b17a52013e6fa4207f2c214 4588 python optional pyfribidi_0.12.0+repack-3.debian.tar.xz f43992fe949066a40fca5b84085f3044 4957 python optional pyfribidi_0.12.0+repack-3_source.buildinfo -BEGIN PGP SIGNATURE- iQFWBAEBCgBAFiEEggahliCEfm0N+LF2vBlqlO3dobcFAl3R/IAiHGFlbG1haG1v dWR5QHVzZXJzLnNvdXJjZWZvcmdlLm5ldAAKCRC8GWqU7d2ht2zHB/0T4gAsNX85 IMt/XpYP1qh4//g4WXkjMJ1gA6W1y7CzyFU1dzZjdZuQ1Y7kYD1fHEYcELTR3fZr GdjD/l+QS6czheHOssS8uIKCipfGGhcxmIq2WVZ9MML7irxVvljuls1RrBBJZu/V PyVV/Y5hykgEuWUHyUHw9kTnyFDO9SRR408HdqFqzJJI2X75QtL+IF0ivAyGcLwO KA6HswLmpJr3oUUWSLXqZeK3KjqwwG7c6ncbik/+9lBXv2MFc2ulTMOdgt3OOsZ4 lW9OdS/RbVhBOWjK/rv6WHDHoyOqInOQzF5bbbAxb+jU6qJA+f+bFU9yMHgfaIja Zpsf6t1iMIXc =VRoq -END PGP SIGNATURE End Message ---
Bug#944993: gnome-shell-extension-show-ip: primary-interface patch broke loading the extension
Package: gnome-shell-extension-show-ip
Version: 8-4
Severity: serious
Tags: patch
The primary-interface patch I proposed had a serious issue:
JS ERROR: Extension show...@sgaraud.github.com: ReferenceError: device is not
defined
I've fixed the issue upstream and in the attached patch.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-debug
APT policy: (900, 'testing-debug'), (900, 'testing'), (800,
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700,
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gnome-shell-extension-show-ip depends on:
ii gnome-shell 3.34.1+git20191024-1
gnome-shell-extension-show-ip recommends no packages.
gnome-shell-extension-show-ip suggests no packages.
-- no debconf information
--
bye,
pabs
https://wiki.debian.org/PaulWise
From 626ff48b7e29cf4178a2f439b85340e7b1e25774 Mon Sep 17 00:00:00 2001
From: Paul Wise
Date: Thu, 2 Mar 2017 18:07:14 +0800
Subject: [PATCH] Show the primary IP address when no interface was chosen
Makes it easier to see all IP addresses at a glance.
Uses NM to get which interface(s) are in the default route.
---
README.md| 1 +
extension.js | 53 +---
2 files changed, 43 insertions(+), 11 deletions(-)
diff --git a/README.md b/README.md
index 0fafb7a..eec47e3 100644
--- a/README.md
+++ b/README.md
@@ -83,6 +83,7 @@ issues](https://github.com/sgaraud/gnome-extension-show-ip/issues).
### License
Copyright (C) 2015 Sylvain Garaud
+Copyright 2017 Paul Wise
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
diff --git a/extension.js b/extension.js
index d9a7940..5dc7d9a 100644
--- a/extension.js
+++ b/extension.js
@@ -3,6 +3,7 @@
* https://github.com/sgaraud/gnome-extension-show-ip
*
* Copyright (C) 2015 Sylvain Garaud
+ * Copyright 2017 Paul Wise
*
* This file is part of Show-IP GNOME extension.
* Show IP GNOME extension is free software: you can redistribute it and/or modify
@@ -170,17 +171,30 @@ const IpMenuBase = new Lang.Class({
}
});
+this._getPrimaryDevices(this.client);
+let selectedIp = '';
+let primaryIp = '';
+let firstIp = '';
for (let device of this._devices) {
-if (device.ifc == this.selectedDevice) {
-if (Schema.get_boolean("menu")) {
-this.label.set_text(_("IP: %s").format(device.ip));
-} else {
-this.label.set_text(device.ip);
-}
-break;
+if (!selectedIp && device.ifc == this.selectedDevice) {
+selectedIp = device.ip;
+}
+if (!primaryIp && device.primary) {
+primaryIp = device.ip;
+}
+if (!firstIp) {
+firstIp = device.ip;
}
}
-if ('' == this.selectedDevice) {
+let ip = selectedIp ? selectedIp : primaryIp ? primaryIp : firstIp;
+if (ip) {
+if (Schema.get_boolean("menu")) {
+this.label.set_text(_("IP: %s").format(ip));
+} else {
+this.label.set_text(ip);
+}
+this.label.set_text(ip);
+} else {
this.label.set_text(NOT_CONNECTED);
}
},
@@ -207,6 +221,26 @@ const IpMenuBase = new Lang.Class({
this._createPopupMenu();
},
+_getPrimaryDevices: function (nmc) {
+let primary_conn = nmc.get_primary_connection();
+let primary_devices = primary_conn.get_devices();
+let primary_ifcs = [];
+let i = 0;
+if (primary_devices) {
+for (let device of primary_devices) {
+primary_ifcs[i++] = device.get_iface();
+}
+}
+for (let device of this._devices) {
+device.primary = false;
+for (let ifc of primary_ifcs) {
+if (device.ifc == ifc) {
+device.primary = true;
+}
+}
+}
+},
+
_getNetworkDevices: function (nmc) {
let _device;
this.devices = nmc.get_devices();
@@ -290,9 +324,6 @@ const IpMenuBase = new Lang.Class({
} else {
device.ip = this._decodeIp4(ipadd);
}
-if ('' == this.selectedDevice) {
-this.selectedDevice = device.ifc;
-}
break;
Processed: Bug#944767 marked as pending in hijra
Processing control commands:
> tag -1 pending
Bug #944767 {Done: أحمد المحمودي } [src:hijra]
python3-hijra: uninstallable
Added tag(s) pending.
--
944767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#944792: marked as pending in hijra
Control: tag -1 pending Hello, Bug #944792 in hijra 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/islamic-team/hijra/commit/c841882a6b1f0780b894fec37173f92dfc0d168d Add Breaks+Replaces: python-hijra Closes: #944792 (this message was generated automatically) -- Greetings https://bugs.debian.org/944792
Bug#944767: marked as pending in hijra
Control: tag -1 pending Hello, Bug #944767 in hijra 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/islamic-team/hijra/commit/d8d18cbf77daae0f692513b39983db3c721c68fc Fix indentation inpy3.diff patch Closes: #944767 (this message was generated automatically) -- Greetings https://bugs.debian.org/944767
Bug#944767: marked as done (python3-hijra: uninstallable)
Your message dated Mon, 18 Nov 2019 02:47:27 + with message-id <5dd2063f64dd4_3b02ac60b1dd0d441...@godard.mail> and subject line Bug#944767 fixed in hijra has caused the Debian Bug report #944767, regarding python3-hijra: uninstallable 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.) -- 944767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hijra Version: 0.4.1-2 X-Debbugs-CC: aelmahmo...@users.sourceforge.net Severity: grave python3-hijra is uninstallable: Setting up python3-hijra (0.4.1-2) ... Sorry: TabError: inconsistent use of tabs and spaces in indentation (HijriCal.py, line 83) dpkg: error processing package python3-hijra (--configure): installed python3-hijra package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of hijra-applet: hijra-applet depends on python3-hijra (= 0.4.1-2); however: Package python3-hijra is not configured yet. See the mention of line 83 in the log excerpt I posted. Thanks, Jeremy Bicha --- End Message --- --- Begin Message --- Hello, Bug #944767 in hijra reported by you has been fixed in the Git repository. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/islamic-team/hijra/commit/d8d18cbf77daae0f692513b39983db3c721c68fc Fix indentation inpy3.diff patch Closes: #944767 (this message was generated automatically) -- Greetings https://bugs.debian.org/944767--- End Message ---
Bug#944792: marked as done (python3-hijra: missing Breaks+Replaces: python-hijra)
Your message dated Mon, 18 Nov 2019 02:47:27 + with message-id <5dd2063f4c539_3b02ac60b1dd0d441...@godard.mail> and subject line Bug#944792 fixed in hijra has caused the Debian Bug report #944792, regarding python3-hijra: missing Breaks+Replaces: python-hijra 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.) -- 944792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-hijra Version: 0.4.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces This test intentionally skipped 'testing' to find file overwrite problems before packages migrate from 'unstable' to 'testing'. >From the attached log (scroll to the bottom...): Selecting previously unselected package python3-hijra. Preparing to unpack .../python3-hijra_0.4.1-2_all.deb ... Unpacking python3-hijra (0.4.1-2) ... dpkg: error processing archive /var/cache/apt/archives/python3-hijra_0.4.1-2_all.deb (--unpack): trying to overwrite '/usr/share/doc/python-hijra/readme-ar.html', which is also in package python-hijra 0.4.1-1 Errors were encountered while processing: /var/cache/apt/archives/python3-hijra_0.4.1-2_all.deb cheers, Andreas python-hijra=0.4.1-1_python3-hijra=0.4.1-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Hello, Bug #944792 in hijra reported by you has been fixed in the Git repository. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/islamic-team/hijra/commit/c841882a6b1f0780b894fec37173f92dfc0d168d Add Breaks+Replaces: python-hijra Closes: #944792 (this message was generated automatically) -- Greetings https://bugs.debian.org/944792--- End Message ---
Processed: Bug#944792 marked as pending in hijra
Processing control commands:
> tag -1 pending
Bug #944792 {Done: أحمد المحمودي } [python3-hijra]
python3-hijra: missing Breaks+Replaces: python-hijra
Added tag(s) pending.
--
944792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944792
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#944939: marked as pending in pyfribidi
Control: tag -1 pending Hello, Bug #944939 in pyfribidi 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/pyfribidi/commit/da7643395ee585683922d21692723fddf7ad969b Add dh-python to build deps Closes: #944939 (this message was generated automatically) -- Greetings https://bugs.debian.org/944939
Processed: Bug#944939 marked as pending in pyfribidi
Processing control commands: > tag -1 pending Bug #944939 [src:pyfribidi] pyfribidi: needs an explicit build dependency on dh-python Added tag(s) pending. -- 944939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#944947 marked as pending in python-uinput
Processing control commands: > tag -1 pending Bug #944947 [src:python-uinput] python-uinput: needs an explicit build dependency on dh-python Added tag(s) pending. -- 944947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944947 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944947: marked as pending in python-uinput
Control: tag -1 pending Hello, Bug #944947 in python-uinput 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-uinput/commit/1cbe43fea993838d6997d5e29d59524dd6ec77cf Add dh-python to build deps Closes: #944947 (this message was generated automatically) -- Greetings https://bugs.debian.org/944947
Processed: affects 923347
Processing commands for cont...@bugs.debian.org: > affects 923347 src:mysql-workbench Bug #923347 [src:mysql-connector-python] No sensible security support due to Oracle's policies Added indication that 923347 affects src:mysql-workbench > thanks Stopping processing here. Please contact me if you need assistance. -- 923347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923347 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 943961
Processing commands for cont...@bugs.debian.org: > tags 943961 + pending Bug #943961 [src:ceph] ceph: autopkgtest needs update for new version of python3.7: deprecation warning Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 943961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 936282
Processing commands for cont...@bugs.debian.org: > tags 936282 + pending Bug #936282 [src:ceph] ceph: Python2 removal in sid/bullseye Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 936282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936282 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942901: [Pkg-privacy-maintainers] Bug#942901: Bug#942901: torbrowser-launcher: Tor Browser 9.0 shows only black screens due to no write access to /dev/shm/org.mozilla.ipc.*.*
Hi,
Antoine Beaupré:
> I also had to add:
> owner @{torbrowser_home_dir}/updater ix,
FWIW, this one is fixed in upstream Git (too):
https://github.com/micahflee/torbrowser-launcher/pull/442
Bug#944044: marked as done (python-xarray migrated to testing despite 2313 failing tests)
Your message dated Sun, 17 Nov 2019 20:45:04 + with message-id and subject line Bug#944044: fixed in python-xarray 0.14.0-2 has caused the Debian Bug report #944044, regarding python-xarray migrated to testing despite 2313 failing tests to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 944044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-xarray Version: 0.14.0-1 Severity: serious Tags: sid bullseye Despite the autopkg test regressions mentioned in #935455, python-xarray migrated to testing due to a britney bug. In the autopkg test now 2313 test cases fail. That's apparently also known upstream, and afaik there is a new release being prepared. I tried to address some of these issues: Pulling two issues http://launchpadlibrarian.net/449475370/python-xarray_0.14.0-1_0.14.0-1ubuntu1.diff.gz http://launchpadlibrarian.net/449494504/python-xarray_0.14.0-1ubuntu1_0.14.0-1ubuntu2.diff.gz get's down the number of test failures to 150 while pulling in the whole trunk/brunch gets it up again to http://launchpadlibrarian.net/449597034/python-xarray_0.14.0-1ubuntu2_0.14.0-1ubuntu3.diff.gz I'm not tagging this as a patch, it's not getting the autopkg tests pass again. --- End Message --- --- Begin Message --- Source: python-xarray Source-Version: 0.14.0-2 We believe that the bug you reported is fixed in the latest version of python-xarray, 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 944...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated python-xarray package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 17 Nov 2019 18:32:58 + Source: python-xarray Architecture: source Version: 0.14.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Alastair McKinstry Closes: 944044 Changes: python-xarray (0.14.0-2) unstable; urgency=medium . [ Matthias Klose ] * Fix test failures with new cftime 1.0.4, taken from upstream. * _get_scheduler() exception if dask.multiprocessing missing, taken from upstream. . [ Alastair McKinstry ] * xfail-dask.patch: Dask version in Debian is < 2. Label some functionality XFAIL, set dask='allowed' rather than 'parallelize' where possible for the rest * xfail-rasterio.patch: Disable tests due to issue in rasterio: "WarpedVRT does not permit boundless reads". Closes: #944044 Checksums-Sha1: e3afd531e3549b2893d5db201a12911b3dc0bb2d 3033 python-xarray_0.14.0-2.dsc cf1eaf515c076129101c66f1366651f6939728d7 15336 python-xarray_0.14.0-2.debian.tar.xz Checksums-Sha256: 530b597826f04052362c78ae00b8df1f54c6fbaa65a3337832b38bc4096dd6a7 3033 python-xarray_0.14.0-2.dsc 15d1fd14ac167fd4b3dc5c56a4e5c6b6d95bfb1369ecbce5d55afc3b7722089f 15336 python-xarray_0.14.0-2.debian.tar.xz Files: 261f452b0b3e0ebdc581ca435cda6e3e 3033 python optional python-xarray_0.14.0-2.dsc 8b98842bd4cecca665e686e9134a06ab 15336 python optional python-xarray_0.14.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl3Ro0EACgkQy+a7Tl2a 06VOzRAAo7DzJJORlsC8tkUQU7LemzYNL5mq8QvTmi6ik4ITs7v8RoVbfxgv3OX1 glUupBl0bbrFMTFuGUKZplPqCUU1jQxkJjembAtxk1rMVEt46rM8HH4shadmekPQ sm2XFXx9zc4KsmKW8Fj8PpiFJnyxCIdDovJPsrsr3nKWwaJxtMsQCIsmA8hvg3Ca 5SLgcl3aPi41aUOXjaRw/QyH1DScF3CQz2bdfcFFhCMUbwHEIsIeL4CFIxzTPNHE oRk9xPsEW3voZbAK5Q/+K9YStjaAEGv5O07ey2f4LZUA5GwGmZQTYL7huk25OLQe 2slfkt9kTOkZxwtk/defTJApv0vGiFvxSGRTNQgCQbOs2dbXY3cmgAFbGQsIE3mn NkLCwCCYfWxJxojpRhT6rWbvrhO+QYSAhvpml8Jp7D6gGNZGc2MZ7BywZbczJT/z gIVY5tFwhS+RjorWJUxi1MO0u51p12eIUXd+a5I3fOhzi7pgR1Rb6+OqNlALjDGl Ur+hQL1gWhXq04cDZsQB4IzvUv56Ll4SCslmmMkcGkzobapFzYoP6Ga9lbpun5Cx mMJq7K0fGtDBJYiQwp39E8r8m9v7dHDFE4kQ+u3u/kZs6uYeKr/QAFLqA5KwUIZP xJJgZi/xxAjIW7v6UeMWhoQSZR7bWdrjb5cwWZBOso0G4jyIydQ= =iXc+ -END PGP SIGNATURE End Message ---
Bug#944949: dbus-python: needs an explicit build dependency on dh-python
Control: tags 944949 + moreinfo On Sun, 17 Nov 2019 at 19:07:39 +, Matthias Klose wrote: > Please add an explicit build dependency on dh-python. As far as I can see it's been explicit since 2015. Is anything more needed here? Note that the FTBFS with dh_python2 make[1]: dh_python2: Command not found seems to be because /usr/bin/dh_python2 is a #!/usr/bin/python script in a package that doesn't depend on python (#944894). The misleading "Command not found" is similar to this: $ cat > Makefile all: ./script $ cat > script #!/usr/bin/does-not-exist $ chmod +x script $ make ./script make: ./script: Command not found make: *** [Makefile:2: all] Error 127 I have a workaround which I believe should still be harmless after dh_python2 moves out of python2 (presumably into dh-python?), which I'll upload soon. If that doesn't work, I'll temporarily re-add the python B-D so the python3.8 transition can go through, and remove it after #944894 is resolved. It's unfortunate that the python3.8 transition, the effort to replace references to python2 with python, and the migration of dh_python2 from python2 to dh-python (?) are happening at the same time and affect overlapping sets of packages. Perhaps one (or more) of these could be deferred until one of the others has been done? smcv
Processed: Re: Bug#944949: dbus-python: needs an explicit build dependency on dh-python
Processing control commands: > tags 944949 + moreinfo Bug #944949 [src:dbus-python] dbus-python: needs an explicit build dependency on dh-python Added tag(s) moreinfo. -- 944949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#838994: Bug#891493: Bug#838994: Bug#891493: unresolved gtk2-engines-murrine situation (was: numix-gtk-theme: Undocumented and very likely also broken Breaks against murrine-themes since 2.6.7-2)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2019-11-17 at 11:00 +, Mike Gabriel wrote: > If you plan to drop maintenance sooner or later anyway, then please > state that asap (packages are in deferred-15 from today again), so > that I can change the uploads and make these bugs go away without > introducing a virtual package. Let's be realistic, I won't have time / priority for those themes, so I'm ok with dropping maintenance even right now. So go ahead with your preferred plan. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl3RouwACgkQ3rYcyPpX RFvuoggAzbl9QuKIg6U3z3qUK1cEn9486QAsCFFqyEkCpU2SdbvN0jQKsU+zlk/P YeBh80ungay/7cRp3mHX9/HDlJ550PhoiqE3Laj++OOYGC0yzUT+s7ARhwmztpOY nk3Y3BJ7xZ7zgOgR1JdMO81FbDEx7Qa49epCLjZ+Nmjci4Bwk5CuEIbIn5ujOpqR zmeyaUSYursxSV0GMNBz5bCMBOjdGbqLUNA/IzlaPCRusdjlUpwJH6NWwdAQbXJ/ XWC9fQiegEIe+9+4fEOZXWPNu4AUQb4gV5fVAh7RWh5y08Va723RqzB11iBBJ247 r4A6B66fyUWKvWOXGyGULm4pHnDRZA== =vLjy -END PGP SIGNATURE-
Bug#944943: marked as done (python-freecontact: needs an explicit build dependency on dh-python)
Your message dated Sun, 17 Nov 2019 20:33:24 +0100 with message-id <6170feb4-c526-2e38-8aaa-ff1aaa800...@debian.org> and subject line Re: Bug#944943: python-freecontact: needs an explicit build dependency on dh-python has caused the Debian Bug report #944943, regarding python-freecontact: needs an explicit build dependency on dh-python 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.) -- 944943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-freecontact Version: 1.1-5 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python. --- End Message --- --- Begin Message --- On 17.11.19 20:27, Andreas Tille wrote: > Control: tags -1 moreinfo > > Hi Matthias, > > On Sun, Nov 17, 2019 at 07:07:32PM +, Matthias Klose wrote: >> Package: src:python-freecontact >> Version: 1.1-5 >> Severity: serious >> Tags: sid bullseye >> >> python3-all and python3-dev now dropped the dependency on >> dh-python: >> >> [ Piotr Ożarowski ] >>* Remove dh-python dependency from python3-all and python3-dev packages. >> Packages should build depend on dh-python or dh-sequence-python3 >> instead. > > The package Build-Depends from dh-python since 1.1-5 > >https://packages.debian.org/source/unstable/python-freecontact > > Kind regards that bug was wrong. just needs given back after boost is built for 3.8.--- End Message ---
Bug#944894: /usr/bin/dh_python2: is a #!/usr/bin/python script but does not depend on python
On 17.11.19 13:29, Simon McVittie wrote: > Package: python2 > Version: 2.7.17-1 > Severity: serious > File: /usr/bin/dh_python2 > Justification: Policy 3.5 > Control: affects -1 src:dbus-python > > As instructed by the py2removal mass-bug-filing templates, I have been > removing references to python from packages I maintain, and replacing them > with references to python2 if the Python 2 modules are still needed. > > This seems to have caused dbus-python to FTBFS when NMU'd for the python3.8 > transition: > > https://buildd.debian.org/status/fetch.php?pkg=dbus-python=amd64=1.2.12-1%2Bb1=1573984727=0 >> Unpacking python2 (2.7.17-1) ... > ... >> Unpacking dh-python (4.20191017) ... > ... >>debian/rules override_dh_python2 >> make[1]: Entering directory '/<>' >> py3versions: no X-Python3-Version in control file, using supported versions >> dh_python2 >> make[1]: dh_python2: Command not found >> make[1]: *** [debian/rules:214: override_dh_python2] Error 127 > > /usr/bin/dh_python2 is in the python2 binary package, which is > installed, so this "command not found" shouldn't be caused by absence > of /usr/bin/dh_python2. > > As far as I can work out, it's actually caused by the absence of > the interpreter named in its first line, which is /usr/bin/python > (shells do not make it easy to distinguish between these two > failure modes). dbus-python no longer build-depends on python, so > /usr/bin/python2.7 and /usr/bin/python2 exist in the build environment, > but /usr/bin/python does not. > > I think /usr/bin/dh_python2 should now be a #!/usr/bin/python2 (or maybe > #!/usr/bin/python2.7) script, instead of a #!/usr/bin/python script. the VCS already has the pending fix to remove dh_python2 from python2.
Processed: Re: Bug#944943: python-freecontact: needs an explicit build dependency on dh-python
Processing control commands: > tags -1 moreinfo Bug #944943 [src:python-freecontact] python-freecontact: needs an explicit build dependency on dh-python Added tag(s) moreinfo. -- 944943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944943: python-freecontact: needs an explicit build dependency on dh-python
Control: tags -1 moreinfo Hi Matthias, On Sun, Nov 17, 2019 at 07:07:32PM +, Matthias Klose wrote: > Package: src:python-freecontact > Version: 1.1-5 > Severity: serious > Tags: sid bullseye > > python3-all and python3-dev now dropped the dependency on > dh-python: > > [ Piotr Ożarowski ] >* Remove dh-python dependency from python3-all and python3-dev packages. > Packages should build depend on dh-python or dh-sequence-python3 instead. The package Build-Depends from dh-python since 1.1-5 https://packages.debian.org/source/unstable/python-freecontact Kind regards Andreas. -- http://fam-tille.de
Bug#944936: minieigen: needs an explicit build dependency on dh-python
Package: src:minieigen Version: 0.50.3+dfsg1-8 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python.
Bug#944939: pyfribidi: needs an explicit build dependency on dh-python
Package: src:pyfribidi Version: 0.12.0+repack-2 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python.
Bug#944946: python-fuse: needs an explicit build dependency on dh-python
Package: src:python-fuse Version: 2:1.0.0-1 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python.
Bug#944938: ltt-control: needs an explicit build dependency on dh-python
Package: src:ltt-control Version: 2.11.0-2 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python.
Bug#944934: cracklib2: needs an explicit build dependency on dh-python
Package: src:cracklib2 Version: 2.9.6-3 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python.
Bug#944947: python-uinput: needs an explicit build dependency on dh-python
Package: src:python-uinput Version: 0.11.2-2 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python.
Bug#944945: python-scrypt: needs an explicit build dependency on dh-python
Package: src:python-scrypt Version: 0.8.0-0.2 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python.
Bug#944942: python-ssdeep: needs an explicit build dependency on dh-python
Package: src:python-ssdeep Version: 3.1+dfsg-2.1 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python.
Bug#944935: deltarpm: needs an explicit build dependency on dh-python
Package: src:deltarpm Version: 3.6+dfsg-1 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python.
Bug#944949: dbus-python: needs an explicit build dependency on dh-python
Package: src:dbus-python Version: 1.2.12-1 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python.
Bug#944943: python-freecontact: needs an explicit build dependency on dh-python
Package: src:python-freecontact Version: 1.1-5 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python.
Bug#944944: python-kyotocabinet: needs an explicit build dependency on dh-python
Package: src:python-kyotocabinet Version: 1.22-2 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python.
Bug#944948: tnetstring: needs an explicit build dependency on dh-python
Package: src:tnetstring Version: 0.3.1-2 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python.
Bug#944940: python-ethtool: needs an explicit build dependency on dh-python
Package: src:python-ethtool Version: 0.14-1 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python.
Bug#944941: pykerberos: needs an explicit build dependency on dh-python
Package: src:pykerberos Version: 1.1.14-2 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python.
Bug#944937: py-postgresql: needs an explicit build dependency on dh-python
Package: src:py-postgresql Version: 1.2.1+git20180803.ef7b9a9-1 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python.
Bug#944933: babeltrace: needs an explicit build dependency on dh-python
Package: src:babeltrace Version: 1.5.7-1 Severity: serious Tags: sid bullseye python3-all and python3-dev now dropped the dependency on dh-python: [ Piotr Ożarowski ] * Remove dh-python dependency from python3-all and python3-dev packages. Packages should build depend on dh-python or dh-sequence-python3 instead. Please add an explicit build dependency on dh-python.
Bug#942901: [Pkg-privacy-maintainers] Bug#942901: torbrowser-launcher: Tor Browser 9.0 shows only black screens due to no write access to /dev/shm/org.mozilla.ipc.*.*
On 2019-10-23 09:41:51, Paul Wise wrote:
> Package: torbrowser-launcher
> Version: 0.3.2-2
> Severity: serious
>
> Tor Browser 9.0 shows only black screens because the default apparmor
> profile does not allow write access to /dev/shm/org.mozilla.ipc.*.*
> like it does for /dev/shm/org.chromium.* and I was able to fix this
> issue by adding this workaround:
>
> ==> /etc/apparmor.d/local/torbrowser.Browser.firefox <==
> owner /{dev,run}/shm/org.mozilla.*.* rw,
I also had to add:
owner @{torbrowser_home_dir}/updater ix,
and restart apparmor:
service apparmor restart
anyone working on uploading a fix for this?
--
No animal has more liberty than the cat; but it buries the mess it
makes. The cat is the best anarchist. Until they learn that from the cat
I cannot respect them.
- For whom the bell tolls, Ernest Hemingway
Bug#943705: dh_installman: man-recode integration gets confused if both foo.1 and foo.1.gz exist
Colin Watson: > Package: debhelper > Version: 12.7.1 > Severity: important > > rumur FTBFS with debhelper 12.7.1 and man-db 2.9.0-1. Running the > binary target manually with DH_VERBOSE=1, I see the following at the > end: > > [...] > Hi Colin, Thanks for filing this bug. I think you have spotted a case of (unintentional) undefined behaviour in debhelper. > [...] > > Of course, rumur could easily work around this by removing > debian/rumur.manpages, but I assume debhelper doesn't want to create > this kind of regression. Before man-recode existed, the net effect > would have been that only the last of a group of files that differ only > by compression extension is considered. For compatibility purposes, I > think the logic in reencode_manpages will need to be adjusted to > preserve this property. > > Thanks, > Rather, I would argue that the result is "it depends(tm)". Your statement is true only when @manpages_to_reencode is constructed deterministically AND when the conflicting definitions end up in the same "parallelization bucket". However: 1) If the two conflicting definitions of the manpages end in different buckets when calling "on_items_in_parallel", then all bets are off and you get a standard race-condition. In best case, you get "one" of the input files - worst case, corrupted manpages. 2) Even then, the construction of @manpages_to_reecode depends on the order returned by filesystem (File::Find does not sort the result readdir by default; this has to be done by the preprocess option) 3) Even if the order in 2) is stable (but not sorted), the build putting the files there may be unstable due to parallelism. (prior to adding parallelization in 10.2.X, we "only" suffered from 2+3) I think the proper solution here is to either pick a "winner" deterministically OR reject the situation as a conflict and have the packager sort out the issue. I am learning towards the latter as a long term solution (compat 13) and the former as a short term (current compat levels). Suggestions/feedback welcome. Thanks, ~Niels
Processed: reassign 931695 to src:libgit-raw-perl, forcibly merging 931695 944912, tagging 931695 ...
Processing commands for cont...@bugs.debian.org: > reassign 931695 src:libgit-raw-perl 0.79-6 Bug #931695 [libgit-raw-perl] libgit-raw-perl: libgit2 0.28 transition Bug reassigned from package 'libgit-raw-perl' to 'src:libgit-raw-perl'. No longer marked as found in versions libgit-raw-perl/0.79-6. Ignoring request to alter fixed versions of bug #931695 to the same values previously set Bug #931695 [src:libgit-raw-perl] libgit-raw-perl: libgit2 0.28 transition Marked as found in versions libgit-raw-perl/0.79-6. > forcemerge 931695 944912 Bug #931695 [src:libgit-raw-perl] libgit-raw-perl: libgit2 0.28 transition Bug #944912 [src:libgit-raw-perl] libgit-raw-perl: FBTFS: ./xs/Indexer.xs:14:8: error: too many arguments to function ‘git_indexer_new’ 934927 was blocked by: 931695 931697 931693 934927 was not blocking any bugs. Added blocking bug(s) of 934927: 944912 The source libgit-raw-perl and version 0.79-6+b2 do not appear to match any binary packages Marked as found in versions libgit-raw-perl/0.79-6. Added tag(s) bullseye and sid. Bug #931695 [src:libgit-raw-perl] libgit-raw-perl: libgit2 0.28 transition The source libgit-raw-perl and version 0.79-6+b2 do not appear to match any binary packages Marked as found in versions libgit-raw-perl/0.79-6+b2. Added tag(s) ftbfs. Merged 931695 944912 > tags 931695 + ftbfs Bug #931695 [src:libgit-raw-perl] libgit-raw-perl: libgit2 0.28 transition Bug #944912 [src:libgit-raw-perl] libgit-raw-perl: FBTFS: ./xs/Indexer.xs:14:8: error: too many arguments to function ‘git_indexer_new’ Ignoring request to alter tags of bug #931695 to the same tags previously set Ignoring request to alter tags of bug #944912 to the same tags previously set > retitle 931695 libgit-raw-perl: FTBFS with libgit2 0.28 Bug #931695 [src:libgit-raw-perl] libgit-raw-perl: libgit2 0.28 transition Bug #944912 [src:libgit-raw-perl] libgit-raw-perl: FBTFS: ./xs/Indexer.xs:14:8: error: too many arguments to function ‘git_indexer_new’ Changed Bug title to 'libgit-raw-perl: FTBFS with libgit2 0.28' from 'libgit-raw-perl: libgit2 0.28 transition'. Changed Bug title to 'libgit-raw-perl: FTBFS with libgit2 0.28' from 'libgit-raw-perl: FBTFS: ./xs/Indexer.xs:14:8: error: too many arguments to function ‘git_indexer_new’'. > thanks Stopping processing here. Please contact me if you need assistance. -- 931695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931695 934927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934927 944912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942789: marked as done (libbio-{db-{biofetch,gff,seqfeature},searchio-hmmer,tools-run-remoteblast}-perl: missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3))
Your message dated Sun, 17 Nov 2019 15:49:44 +
with message-id
and subject line Bug#942789: fixed in libbio-db-seqfeature-perl 1.7.3-2
has caused the Debian Bug report #942789,
regarding
libbio-{db-{biofetch,gff,seqfeature},searchio-hmmer,tools-run-remoteblast}-perl:
missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3)
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.)
--
942789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package:
libbio-db-biofetch-perl,libbio-db-gff-perl,libbio-db-seqfeature-perl,libbio-searchio-hmmer-perl,libbio-tools-run-remoteblast-perl
Version: 1.7.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>From the attached log (scroll to the bottom...):
Preparing to unpack .../libbio-db-biofetch-perl_1.7.3-1_all.deb ...
Unpacking libbio-db-biofetch-perl (1.7.3-1) ...
dpkg: error processing archive
/var/cache/apt/archives/libbio-db-biofetch-perl_1.7.3-1_all.deb (--unpack):
trying to overwrite '/usr/share/man/man3/Bio::DB::BioFetch.3pm.gz', which is
also in package libbio-perl-perl 1.7.2-3
Errors were encountered while processing:
/var/cache/apt/archives/libbio-db-biofetch-perl_1.7.3-1_all.deb
The (<< 1.7.3) version constraint is based on my assumption that 1.7.3 split
up libbio-perl-perl into several independent source packages.
cheers,
Andreas
libbio-perl-perl=1.7.2-3_libbio-db-biofetch-perl=1.7.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libbio-db-seqfeature-perl
Source-Version: 1.7.3-2
We believe that the bug you reported is fixed in the latest version of
libbio-db-seqfeature-perl, 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 942...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael R. Crusoe (supplier of updated
libbio-db-seqfeature-perl 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, 29 Oct 2019 13:09:39 +0100
Source: libbio-db-seqfeature-perl
Architecture: source
Version: 1.7.3-2
Distribution: unstable
Urgency: medium
Maintainer: Michael R. Crusoe
Changed-By: Michael R. Crusoe
Closes: 942789
Changes:
libbio-db-seqfeature-perl (1.7.3-2) unstable; urgency=medium
.
* debian/control: Breaks+Replaces the old libbio-bio-perl. (Closes: #942789)
Checksums-Sha1:
03c7ee06cc7f76454827a2436157a8dd1861c57d 2195
libbio-db-seqfeature-perl_1.7.3-2.dsc
2ea5d85013cdf642846efcda6513ce20d8b0300e 1868
libbio-db-seqfeature-perl_1.7.3-2.debian.tar.xz
ee1257974acb5bfab027e9a35817defbf2d99a14 7440
libbio-db-seqfeature-perl_1.7.3-2_source.buildinfo
Checksums-Sha256:
28a10bff946e9c0fa72a668ae3557ff7a292f756fcca7b936af4f44d58564bb9 2195
libbio-db-seqfeature-perl_1.7.3-2.dsc
6a9ae788eb4ce7037067f4154313f01286882801bb13b5ab0256eb68e518eb3a 1868
libbio-db-seqfeature-perl_1.7.3-2.debian.tar.xz
4a9ad22f841d77d7870ae6a6d7033304101ba768ef0e92ebddd4e5a7815deb6d 7440
libbio-db-seqfeature-perl_1.7.3-2_source.buildinfo
Files:
2c5d744daed848d0632bf67afa063a18 2195 perl optional
libbio-db-seqfeature-perl_1.7.3-2.dsc
e7719ac88bde2e66ea7f295af401ff37 1868 perl optional
libbio-db-seqfeature-perl_1.7.3-2.debian.tar.xz
793c80627fb78a28136b9244ce7fe9be 7440 perl optional
libbio-db-seqfeature-perl_1.7.3-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl3RaLcACgkQPCZ2P2xn
5uIK0BAAsnnjAnO1zxMq/rXCRWWoIiR2mt1W2/XL1CutY9JoLqBuJPS1q+2i3eGk
hhcc6sdgaxA1VL+0JzGkJpiqrLg9CKFUKqbUx5op3jU5qjFelmo/Q29DOQub63Yo
MVpfk14KE8dA/Q5Pn3us3rGFkek6kjLWtlMMDyMRcASG8NkvVk+GLF9gwzTX1jUF
cqqGTKNfcTsZAauqX9hxTNhvulmk/IDEcqKlbjALM0U/HJ6I4hHNtgEPf6mkNQqp
AiVGZdBNTLdE0bsVQ+lukD4C4RILMnuTLcEyfkA79Zl9azK5eMRfpBXt1HmoDe8X
Bug#942789: marked as done (libbio-{db-{biofetch,gff,seqfeature},searchio-hmmer,tools-run-remoteblast}-perl: missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3))
Your message dated Sun, 17 Nov 2019 15:49:38 +
with message-id
and subject line Bug#942789: fixed in libbio-db-gff-perl 1.7.3-2
has caused the Debian Bug report #942789,
regarding
libbio-{db-{biofetch,gff,seqfeature},searchio-hmmer,tools-run-remoteblast}-perl:
missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3)
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.)
--
942789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package:
libbio-db-biofetch-perl,libbio-db-gff-perl,libbio-db-seqfeature-perl,libbio-searchio-hmmer-perl,libbio-tools-run-remoteblast-perl
Version: 1.7.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>From the attached log (scroll to the bottom...):
Preparing to unpack .../libbio-db-biofetch-perl_1.7.3-1_all.deb ...
Unpacking libbio-db-biofetch-perl (1.7.3-1) ...
dpkg: error processing archive
/var/cache/apt/archives/libbio-db-biofetch-perl_1.7.3-1_all.deb (--unpack):
trying to overwrite '/usr/share/man/man3/Bio::DB::BioFetch.3pm.gz', which is
also in package libbio-perl-perl 1.7.2-3
Errors were encountered while processing:
/var/cache/apt/archives/libbio-db-biofetch-perl_1.7.3-1_all.deb
The (<< 1.7.3) version constraint is based on my assumption that 1.7.3 split
up libbio-perl-perl into several independent source packages.
cheers,
Andreas
libbio-perl-perl=1.7.2-3_libbio-db-biofetch-perl=1.7.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libbio-db-gff-perl
Source-Version: 1.7.3-2
We believe that the bug you reported is fixed in the latest version of
libbio-db-gff-perl, 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 942...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael R. Crusoe (supplier of updated
libbio-db-gff-perl 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, 29 Oct 2019 13:05:38 +0100
Source: libbio-db-gff-perl
Architecture: source
Version: 1.7.3-2
Distribution: unstable
Urgency: medium
Maintainer: Michael R. Crusoe
Changed-By: Michael R. Crusoe
Closes: 942789
Changes:
libbio-db-gff-perl (1.7.3-2) unstable; urgency=medium
.
* debian/control: Breaks+Replaces the old libbio-bio-perl. (Closes: #942789)
Checksums-Sha1:
f80d7432c2d94073f47a91ff2e75bf887f3b9c64 2124 libbio-db-gff-perl_1.7.3-2.dsc
b12df0ad77a29e74a70b9f19cbd4fb5f31b3759c 1936
libbio-db-gff-perl_1.7.3-2.debian.tar.xz
5abdff9ee4f11c4f3d971687d71220962b40fc0a 7568
libbio-db-gff-perl_1.7.3-2_source.buildinfo
Checksums-Sha256:
ba2bf7d36d752fd6fd2d5fea1e347c2a10163cc345d6859e8e1743095e55b141 2124
libbio-db-gff-perl_1.7.3-2.dsc
e1893b33f4e22da5e9c964179e01f5a676258b1e5eaecf50ea6b8f6b8f91099c 1936
libbio-db-gff-perl_1.7.3-2.debian.tar.xz
b8d124728d14f87e7960179a75fc5e12e5e6edbc0be3a7f23fa49bb722e98681 7568
libbio-db-gff-perl_1.7.3-2_source.buildinfo
Files:
15125cfad056a0a7755f6caf92daedd0 2124 perl optional
libbio-db-gff-perl_1.7.3-2.dsc
42b900b3e1f5a2e1ae27b2c884409cce 1936 perl optional
libbio-db-gff-perl_1.7.3-2.debian.tar.xz
a409987500a09080b1007df3f94669e1 7568 perl optional
libbio-db-gff-perl_1.7.3-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl3RaJgACgkQPCZ2P2xn
5uI3RhAAsMrkJcDp4t9h803SYIwtYtyUCFFoK1P2E4E/ye3FN8giaDWMspKc5cl6
J6rKaqMjV0U/YPmMPOjBFR39WaqCGr3irACZOZ7zgt7zvkm606y8l/Bp557Se3SJ
qa6B+atmuBxHZeh4hx9js41PZ3Cc9ZfE57Xg/KOpMZ8WHzVO59w025kwjalYcHz3
0vHdUYlZH6u+34yFfOMYhRenQJPJRxGXYK6yTitSYP+JfRxo+bg0LUJNGf0esZEa
w78vWFzBIF83kVZjzS0MfFOT5eG02ttWtTGbflAHDMK/cGaMf1rR5C8ZHztkWuv8
yt43ha94EqkmK/BA6HolfPftjra5Al4exBvZLB37yagmN1prS4SPFp2zRFrH/0Fa
Bug#942789: marked as done (libbio-{db-{biofetch,gff,seqfeature},searchio-hmmer,tools-run-remoteblast}-perl: missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3))
Your message dated Sun, 17 Nov 2019 15:49:31 +
with message-id
and subject line Bug#942789: fixed in libbio-db-biofetch-perl 1.7.3-2
has caused the Debian Bug report #942789,
regarding
libbio-{db-{biofetch,gff,seqfeature},searchio-hmmer,tools-run-remoteblast}-perl:
missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3)
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.)
--
942789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package:
libbio-db-biofetch-perl,libbio-db-gff-perl,libbio-db-seqfeature-perl,libbio-searchio-hmmer-perl,libbio-tools-run-remoteblast-perl
Version: 1.7.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>From the attached log (scroll to the bottom...):
Preparing to unpack .../libbio-db-biofetch-perl_1.7.3-1_all.deb ...
Unpacking libbio-db-biofetch-perl (1.7.3-1) ...
dpkg: error processing archive
/var/cache/apt/archives/libbio-db-biofetch-perl_1.7.3-1_all.deb (--unpack):
trying to overwrite '/usr/share/man/man3/Bio::DB::BioFetch.3pm.gz', which is
also in package libbio-perl-perl 1.7.2-3
Errors were encountered while processing:
/var/cache/apt/archives/libbio-db-biofetch-perl_1.7.3-1_all.deb
The (<< 1.7.3) version constraint is based on my assumption that 1.7.3 split
up libbio-perl-perl into several independent source packages.
cheers,
Andreas
libbio-perl-perl=1.7.2-3_libbio-db-biofetch-perl=1.7.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libbio-db-biofetch-perl
Source-Version: 1.7.3-2
We believe that the bug you reported is fixed in the latest version of
libbio-db-biofetch-perl, 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 942...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael R. Crusoe (supplier of updated
libbio-db-biofetch-perl 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, 29 Oct 2019 12:58:25 +0100
Source: libbio-db-biofetch-perl
Architecture: source
Version: 1.7.3-2
Distribution: unstable
Urgency: medium
Maintainer: Michael R. Crusoe
Changed-By: Michael R. Crusoe
Closes: 942789
Changes:
libbio-db-biofetch-perl (1.7.3-2) unstable; urgency=medium
.
* debian/control: Breaks+Replaces the old libbio-bio-perl. (Closes: #942789)
Checksums-Sha1:
cfe26b1ef7c7544c593ca3ace55bb20babbaf8f6 2188
libbio-db-biofetch-perl_1.7.3-2.dsc
5e8029c4f625d70adb8d7a405642b27074399766 1872
libbio-db-biofetch-perl_1.7.3-2.debian.tar.xz
85c1fbcf6c208c7f5d3f08cedde67ef5530ea657 8356
libbio-db-biofetch-perl_1.7.3-2_source.buildinfo
Checksums-Sha256:
5ebbc0ae41b6cd0693efa5c1893158e1ca9071497796e4eb08d93d62316cd218 2188
libbio-db-biofetch-perl_1.7.3-2.dsc
14f573be8325665ac3395ef0975f846ad1acd923ae4959678362ae85e811c44b 1872
libbio-db-biofetch-perl_1.7.3-2.debian.tar.xz
8deee16a027d8600819d64d38224a1f0343fd278b1c6a574a6b3a3a967a6 8356
libbio-db-biofetch-perl_1.7.3-2_source.buildinfo
Files:
ca51fbc1734dc1495da16ace3991bd9b 2188 perl optional
libbio-db-biofetch-perl_1.7.3-2.dsc
15fd4b9a0cc766c1795574719b71425f 1872 perl optional
libbio-db-biofetch-perl_1.7.3-2.debian.tar.xz
94d171ea46c27796c9b5ec4e96a6f938 8356 perl optional
libbio-db-biofetch-perl_1.7.3-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl3RaHcACgkQPCZ2P2xn
5uJ6Fg/+NmW7BMd0sOaBPMXrogUqcHF8yjDZOBCEB3ZDVKVOSxGqxbBy/y1DYV5b
X0HXCh53UJ8qc9cx3BWzcFkXIHmgd6rf9MgCECj69/HKSabZESmk6mG5/mBugv9E
+DrwzKTXAuYhtFSy16NIbVbX+t5bCSPucDjK0NeCGVzCKcG7Aa6q4UQJ8ymq2f10
dCQpIRAwWpFmEi15+3Ct4eSXRBFiXRGxELSh/n0JFW7ZOrqhCuYwHmPyvZRd40PY
qMrsAP+8qmEY82JxVFBRrpb++qB7WihJm1b7Gv8GQPFfBQQbNkRKe3f5buWCs3Jz
Bug#942789: marked as done (libbio-{db-{biofetch,gff,seqfeature},searchio-hmmer,tools-run-remoteblast}-perl: missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3))
Your message dated Sun, 17 Nov 2019 15:49:57 +
with message-id
and subject line Bug#942789: fixed in libbio-tools-run-remoteblast-perl 1.7.3-2
has caused the Debian Bug report #942789,
regarding
libbio-{db-{biofetch,gff,seqfeature},searchio-hmmer,tools-run-remoteblast}-perl:
missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3)
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.)
--
942789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package:
libbio-db-biofetch-perl,libbio-db-gff-perl,libbio-db-seqfeature-perl,libbio-searchio-hmmer-perl,libbio-tools-run-remoteblast-perl
Version: 1.7.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>From the attached log (scroll to the bottom...):
Preparing to unpack .../libbio-db-biofetch-perl_1.7.3-1_all.deb ...
Unpacking libbio-db-biofetch-perl (1.7.3-1) ...
dpkg: error processing archive
/var/cache/apt/archives/libbio-db-biofetch-perl_1.7.3-1_all.deb (--unpack):
trying to overwrite '/usr/share/man/man3/Bio::DB::BioFetch.3pm.gz', which is
also in package libbio-perl-perl 1.7.2-3
Errors were encountered while processing:
/var/cache/apt/archives/libbio-db-biofetch-perl_1.7.3-1_all.deb
The (<< 1.7.3) version constraint is based on my assumption that 1.7.3 split
up libbio-perl-perl into several independent source packages.
cheers,
Andreas
libbio-perl-perl=1.7.2-3_libbio-db-biofetch-perl=1.7.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libbio-tools-run-remoteblast-perl
Source-Version: 1.7.3-2
We believe that the bug you reported is fixed in the latest version of
libbio-tools-run-remoteblast-perl, 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 942...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael R. Crusoe (supplier of updated
libbio-tools-run-remoteblast-perl 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, 29 Oct 2019 13:56:50 +0100
Source: libbio-tools-run-remoteblast-perl
Architecture: source
Version: 1.7.3-2
Distribution: unstable
Urgency: medium
Maintainer: Michael R. Crusoe
Changed-By: Michael R. Crusoe
Closes: 942789
Changes:
libbio-tools-run-remoteblast-perl (1.7.3-2) unstable; urgency=medium
.
* debian/control: Breaks+Replaces the old libbio-bio-perl. (Closes: #942789)
Checksums-Sha1:
2342b878a186eac0fe6405b38153cf32336b76f8 2248
libbio-tools-run-remoteblast-perl_1.7.3-2.dsc
78c93112bcc48d7b1e9fa153e3b75a0da4279465 1736
libbio-tools-run-remoteblast-perl_1.7.3-2.debian.tar.xz
51fdf9ef9d3151932a2dc018c40c5c15dd33f47d 7480
libbio-tools-run-remoteblast-perl_1.7.3-2_source.buildinfo
Checksums-Sha256:
a7b6a847a3fccd7d1749c11da09ae4c61f20895f61737a48c3678219166e7ef6 2248
libbio-tools-run-remoteblast-perl_1.7.3-2.dsc
a04504f22e6d62f2afdc17fbe9330a921169222694df7db3e6f6fb52a4cfaa41 1736
libbio-tools-run-remoteblast-perl_1.7.3-2.debian.tar.xz
66c870cc2cb2e0e805956f541d749359b13f509496487a892f6db1514b026788 7480
libbio-tools-run-remoteblast-perl_1.7.3-2_source.buildinfo
Files:
be6c474d4265be3e8ee5da881ea7d6d8 2248 perl optional
libbio-tools-run-remoteblast-perl_1.7.3-2.dsc
18eab98ec05e0f12273e20e844b7abb3 1736 perl optional
libbio-tools-run-remoteblast-perl_1.7.3-2.debian.tar.xz
0794bb63601e763093b11132eec5a096 7480 perl optional
libbio-tools-run-remoteblast-perl_1.7.3-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl3RaRQACgkQPCZ2P2xn
5uIoaxAArYZXBJMIvxtSWdE6kJIzI1FImcZlHyb6j7EoCG87zsCXDT39N3ftGK83
V6d0dnTFbSi7ykPFnDrhGcmMUnoOjmZFbygJWY6Euax4lsERG3omm6qMHHvnDZ/h
V4hE8cTL9wBwnocysclUfJOd+8f+5WKQerpqnft08puyR5THIMskc61FoW0t8qoa
Bug#942789: marked as done (libbio-{db-{biofetch,gff,seqfeature},searchio-hmmer,tools-run-remoteblast}-perl: missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3))
Your message dated Sun, 17 Nov 2019 15:49:51 +
with message-id
and subject line Bug#942789: fixed in libbio-searchio-hmmer-perl 1.7.3-2
has caused the Debian Bug report #942789,
regarding
libbio-{db-{biofetch,gff,seqfeature},searchio-hmmer,tools-run-remoteblast}-perl:
missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3)
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.)
--
942789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package:
libbio-db-biofetch-perl,libbio-db-gff-perl,libbio-db-seqfeature-perl,libbio-searchio-hmmer-perl,libbio-tools-run-remoteblast-perl
Version: 1.7.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>From the attached log (scroll to the bottom...):
Preparing to unpack .../libbio-db-biofetch-perl_1.7.3-1_all.deb ...
Unpacking libbio-db-biofetch-perl (1.7.3-1) ...
dpkg: error processing archive
/var/cache/apt/archives/libbio-db-biofetch-perl_1.7.3-1_all.deb (--unpack):
trying to overwrite '/usr/share/man/man3/Bio::DB::BioFetch.3pm.gz', which is
also in package libbio-perl-perl 1.7.2-3
Errors were encountered while processing:
/var/cache/apt/archives/libbio-db-biofetch-perl_1.7.3-1_all.deb
The (<< 1.7.3) version constraint is based on my assumption that 1.7.3 split
up libbio-perl-perl into several independent source packages.
cheers,
Andreas
libbio-perl-perl=1.7.2-3_libbio-db-biofetch-perl=1.7.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libbio-searchio-hmmer-perl
Source-Version: 1.7.3-2
We believe that the bug you reported is fixed in the latest version of
libbio-searchio-hmmer-perl, 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 942...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael R. Crusoe (supplier of updated
libbio-searchio-hmmer-perl 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, 29 Oct 2019 13:23:15 +0100
Source: libbio-searchio-hmmer-perl
Architecture: source
Version: 1.7.3-2
Distribution: unstable
Urgency: medium
Maintainer: Michael R. Crusoe
Changed-By: Michael R. Crusoe
Closes: 942789
Changes:
libbio-searchio-hmmer-perl (1.7.3-2) unstable; urgency=medium
.
* Remove obsolete fields Name, Contact from debian/upstream/metadata.
* Turn on the autopkgtests
* debian/control: Breaks+Replaces the old libbio-bio-perl. (Closes:
#942789)
Checksums-Sha1:
4bcc0e10015292128026e9d05f71ad4a35de3c4e 2161
libbio-searchio-hmmer-perl_1.7.3-2.dsc
47b753ff5667da5ee362ed1b0c02dd37b110df02 1876
libbio-searchio-hmmer-perl_1.7.3-2.debian.tar.xz
0cdb6b11ad73a3d91432f78661ef66bf008d9866 7445
libbio-searchio-hmmer-perl_1.7.3-2_source.buildinfo
Checksums-Sha256:
141972562240f5d78f7a0e213795024cfa050784fecde9a0b4abd7d63c54fbd4 2161
libbio-searchio-hmmer-perl_1.7.3-2.dsc
e37f213f807ec9fe319ce2544f248f6ae902234491f965faf760364cc2dba016 1876
libbio-searchio-hmmer-perl_1.7.3-2.debian.tar.xz
7e44a61a52d9ee3ec80aa443dafbbf0bbd005f5fc23e7fc635a60a10dbde9499 7445
libbio-searchio-hmmer-perl_1.7.3-2_source.buildinfo
Files:
8564dd4751bb977da4e571c5667d18d5 2161 perl optional
libbio-searchio-hmmer-perl_1.7.3-2.dsc
eb7acaaa4d29481aaf9871d7af9542d4 1876 perl optional
libbio-searchio-hmmer-perl_1.7.3-2.debian.tar.xz
86da31efa3394fc7b0b057af042c7532 7445 perl optional
libbio-searchio-hmmer-perl_1.7.3-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl3RaNsACgkQPCZ2P2xn
5uKAkhAAuiGlxgL+gqFGLQzWen/msizC/XHXJOHnHwfj84HneRlGweQBuNoBYKsI
VImWgIdZxj2aB9XeSuTo282PPwmyo5qkwKSsxDVAXQudoC2PW3AMFXp8hT4T3r0o
J3ID6MXvbEXNVsyikGiIdk0CiCcUBqBwDVUUa/3PIR4T+eB4o+/lpdVV+HHrZnmk
Bug#944912: libgit-raw-perl: FBTFS: ./xs/Indexer.xs:14:8: error: too many arguments to function ‘git_indexer_new’
Source: libgit-raw-perl Version: 0.79-6+b2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) libgit-raw-perl fails to build from source: | x86_64-linux-gnu-gcc -c -I. -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wall -Wno-unused-variable -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION=\"0.79\" -DXS_VERSION=\"0.79\" -fPIC "-I/usr/lib/x86_64-linux-gnu/perl/5.30/CORE" -DGIT_SSH -DNO_VIZ -DSTDC -DNO_GZIP -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DLIBGIT2_NO_FEATURES_H -DGIT_USE_STAT_MTIM -DGIT_USE_STAT_MTIM_NSEC -DGIT_USE_NEC -DGIT_THREADS Raw.c -o Raw.o | In file included from Raw.xs:9: | ppport.h:4594: warning: "WIDEST_UTYPE" redefined | 4594 | # define WIDEST_UTYPE U64TYPE | | | In file included from /usr/lib/x86_64-linux-gnu/perl/5.30/CORE/perl.h:2508, | from Raw.xs:2: | /usr/lib/x86_64-linux-gnu/perl/5.30/CORE/handy.h:1072: note: this is the location of the previous definition | 1072 | # define WIDEST_UTYPE U64 | | | ./xs/Indexer.xs: In function ‘XS_Git__Raw__Indexer_new’: | ./xs/Indexer.xs:14:8: error: too many arguments to function ‘git_indexer_new’ |14 | rc = git_indexer_new(, git_ensure_pv(path, "path"), | |^~~ | In file included from /usr/include/git2/index.h:11, | from /usr/include/git2/merge.h:15, | from /usr/include/git2/cherrypick.h:12, | from /usr/include/git2.h:19, | from Raw.xs:17: | /usr/include/git2/indexer.h:57:17: note: declared here |57 | GIT_EXTERN(int) git_indexer_new( | | ^~~ | make[1]: *** [Makefile:459: Raw.o] Error 1 | make[1]: Leaving directory '/<>' | dh_auto_build: make -j4 returned exit code 2 | make: *** [debian/rules:4: binary-arch] Error 255 | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 The full build log can be found there: https://buildd.debian.org/fetch.php?pkg=libgit-raw-perl=amd64=0.79-6%2Bb2=1573942153=0
Bug#944911: libfiu: FBTFS: Found too many matching python3 bindings
Source: libfiu Version: 1.00-3+b1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) libfiu fails to build from source: | ./wrap-python 3 ./test-manyfps.py | Found too many matching python3 bindingsmake[3]: *** [Makefile:96: py-run-test-manyfps] Error 1 | make[3]: *** Waiting for unfinished jobs | make[4]: Leaving directory '/<>/tests/utils' | parallel nc: 6372609 c: 8276708 e: 509422t: 15158739 | wildcard nc: 577000c: 599000e: 1566 t: 1177566 | rm test-enable_stack test-parallel-wildcard test-parallel test-ferror test-enable_stack_by_name | make[3]: Leaving directory '/<>/tests' | make[2]: *** [Makefile:58: test] Error 2 | make[2]: Leaving directory '/<>' | dh_auto_test: make -j4 test V=1 LC_ALL=C returned exit code 2 | make[1]: *** [debian/rules:28: override_dh_auto_test] Error 255 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:12: build-arch] Error 2 | dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 The full build log can be found there: https://buildd.debian.org/fetch.php?pkg=libfiu=amd64=1.00-3%2Bb1=1573820091=0
Bug#944898: marked as done (FTBFS: missing build-dependency python3-setuptools-scm)
Your message dated Sun, 17 Nov 2019 15:36:45 +
with message-id
and subject line Bug#944898: fixed in python-dnaio 0.4.1-1
has caused the Debian Bug report #944898,
regarding FTBFS: missing build-dependency python3-setuptools-scm
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.)
--
944898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-dnaio
Version: 0.4-1
Severity: serious
Dear Maintainer,
python-dnaio currently fails to build from source with the following
error message:
No local packages or working download links found for setuptools_scm
Traceback (most recent call last):
File "setup.py", line 86, in
"Topic :: Scientific/Engineering :: Bio-Informatics"
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line
144, in setup
_install_setup_requires(attrs)
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line
139, in _install_setup_requires
dist.fetch_build_eggs(dist.setup_requires)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 720, in
fetch_build_eggs
replace_conflicting=True,
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
782, in resolve
replace_conflicting=replace_conflicting
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
1065, in best_match
return self.obtain(req, installer)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
1077, in obtain
return installer(requirement)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 787, in
fetch_build_egg
return cmd.easy_install(req)
File
"/usr/lib/python3/dist-packages/setuptools/command/easy_install.py",
line 698, in easy_install
raise DistutilsError(msg)
distutils.errors.DistutilsError: Could not find suitable distribution
for Requirement.parse('setuptools_scm')
E: pybuild pybuild:341: clean: plugin distutils failed with: exit
code=1: python3.7 setup.py clean
(see
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-dnaio.html
for more details)
After adding `python3-setuptools-scm` to build-depdendencies it built
successfully in pbuilder on my local system.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.3.0-2-amd64 (SMP w/3 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--
mvh / best regards
Hans Joachim Desserud
http://desserud.orgdiff --git a/debian/control b/debian/control
index 50b63d5..703ce98 100644
--- a/debian/control
+++ b/debian/control
@@ -8,6 +8,7 @@ Build-Depends: debhelper-compat (= 12),
python3,
python3-dev,
python3-setuptools,
+ python3-setuptools-scm,
python3-pytest,
python3-xopen,
cython3
--- End Message ---
--- Begin Message ---
Source: python-dnaio
Source-Version: 0.4.1-1
We believe that the bug you reported is fixed in the latest version of
python-dnaio, 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 944...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated python-dnaio package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 17 Nov 2019 16:18:47 +0100
Source: python-dnaio
Binary: python3-dnaio
Architecture: source
Version: 0.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Andreas Tille
Description:
python3-dnaio - Python 3 library for fast parsing of FASTQ and FASTA files
Closes: 944898
Changes:
python-dnaio (0.4.1-1) unstable; urgency=medium
.
* Team upload.
* Build-Depends: python3-setuptools-scm
Closes: #944898
* Set upstream metadata fields: Repository.
* Remove obsolete fields Name from debian/upstream/metadata.
Checksums-Sha1:
Bug#937657: Issue with numpy under Python 3.8
Hi Graham, On Sun, Nov 17, 2019 at 02:16:29PM +0200, Graham Inggs wrote: > If you look on the numpy tracker page [1], you'll see there is a note: > > "This package is part of the ongoing testing transition known as > python3.8. Please avoid uploads unrelated to this transition, they > would likely delay it and require supplementary work from the release > managers." I wonder in how far this is relevant to simply *build* a package. I'm trying to build python-colormap in a pbuilder chroot and it fails and I wonder why. > [1] https://tracker.debian.org/pkg/numpy -- http://fam-tille.de
Bug#941920: marked as done (FTBFS intermittently on buildds ppc64el and amd64)
Your message dated Sun, 17 Nov 2019 14:45:18 + with message-id and subject line Bug#941920: fixed in jellyfish 2.3.0-3 has caused the Debian Bug report #941920, regarding FTBFS intermittently on buildds ppc64el and amd64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 941920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jellyfish Version: 2.3.0-1 Tags: ftbfs Severity: serious Justification: fails to build from source (but built successfully in the past) Control: block 935737 with -1 This package failed to build on ppc64el, but 2.2.10-2 in testing built successfully. So the failure is blocking testing migration. See https://buildd.debian.org/status/logs.php?pkg=jellyfish=ppc64el The migration status interferes with the ongoing Perl 5.30 transition, so it may be necessary to remove this package from testing soon. -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Source: jellyfish Source-Version: 2.3.0-3 We believe that the bug you reported is fixed in the latest version of jellyfish, 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 941...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael R. Crusoe (supplier of updated jellyfish 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: Sun, 17 Nov 2019 14:23:43 +0100 Source: jellyfish Architecture: source Version: 2.3.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Michael R. Crusoe Closes: 941920 Changes: jellyfish (2.3.0-3) unstable; urgency=medium . * Upstream only supports AMD64 (Closes: #941920) * Use secure URI in Homepage field. * Set upstream metadata fields: Repository. Checksums-Sha1: ecac9cf20510ba018f1df4eab4597532a6737ccc 2567 jellyfish_2.3.0-3.dsc 9065334565f983893d93ddb3eb8826ba7553362f 12932 jellyfish_2.3.0-3.debian.tar.xz c11a01c1ccb156561ac662dad93f27efaae8c474 10463 jellyfish_2.3.0-3_source.buildinfo Checksums-Sha256: 7900ce6f49dc6a6f4cd5a0d708b63894d7d8f9b5422501b14fa4379574cc5dda 2567 jellyfish_2.3.0-3.dsc d908ac812ca6699fe655787798c4695b454b4d627192dc6aa99c0cbe3a683eee 12932 jellyfish_2.3.0-3.debian.tar.xz d2af75fb0b41ba01ac4d03589e10ff9240ee8be4d63a4b4212ad36a9e10b6e12 10463 jellyfish_2.3.0-3_source.buildinfo Files: a591996f65d22b9e6d52b46c6d56cbe1 2567 science optional jellyfish_2.3.0-3.dsc 91ae10f426985b55e0a90ce3957622be 12932 science optional jellyfish_2.3.0-3.debian.tar.xz f4e275beb1a9ccfdc6a7ddf53d753caa 10463 science optional jellyfish_2.3.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl3RSy0ACgkQPCZ2P2xn 5uIYnhAAgHbi3BQT5l1U4JLgwnxmP6gfJST/UIQYbjMjQYAhZ5vVE94SgGi8hhbA pnRMp+Y2CfxqdrKJeZYQsQCBK0OC4DEphd/D/M/1OQiM8io9wKhoytZPx0NqIgzR V0b1OHuYjp2oiOSOu8JhflyZmLvWC+gUvi9h37p7OWAV0qPm57MvKU4y0kgfyu31 lFl2XXl9XpxtdzH5Vs0rlx3tvaUqTCrNmuWUQMyrnUH7gzzkFIVQd5yPPkJ3zle/ lAYjo/zxd1LICMs+KFbNmFXm1Y8ttTvwp0rLyu5P173Rw0G5Q6SBIG1ypGLZqpPz prv/rcGdGmBeIBk6k6+LrqIGpHBitU0W4IJl3ydBk2PoVvfWMmObDaJWvEsEkOIw FqJqtLTR3ho5zqyE0WCcSP7RcT2COvDsLxh2KYg6lRZ0DQcX7DogaytOD8N+4O+L T5qjmcCLbJYxsTxCIPgowco8YL26O6KdwHrr/nTh4UOaOT35X0SDURMMi4F/cJN+ NArlMcdG7LKIWNxRBPlTgRM+xe4RH/iyIy518hju2yP/VuwO+5aicqlrT8jKGjTn MpL/RMA4LUSB0tinbhR9LsURR3Wjmm41dO0pTOZNoMtYtqKdx9u1tYG4mgYLMkLd WOuMgNClxl1SuogmL6/dDm1Ij1018/eeln7d8l7Yp/cDOG9xPzA= =dt5b -END PGP SIGNATURE End Message ---
Bug#944898: FTBFS: missing build-dependency python3-setuptools-scm
Source: python-dnaio
Version: 0.4-1
Severity: serious
Dear Maintainer,
python-dnaio currently fails to build from source with the following
error message:
No local packages or working download links found for setuptools_scm
Traceback (most recent call last):
File "setup.py", line 86, in
"Topic :: Scientific/Engineering :: Bio-Informatics"
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line
144, in setup
_install_setup_requires(attrs)
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line
139, in _install_setup_requires
dist.fetch_build_eggs(dist.setup_requires)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 720, in
fetch_build_eggs
replace_conflicting=True,
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
782, in resolve
replace_conflicting=replace_conflicting
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
1065, in best_match
return self.obtain(req, installer)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
1077, in obtain
return installer(requirement)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 787, in
fetch_build_egg
return cmd.easy_install(req)
File
"/usr/lib/python3/dist-packages/setuptools/command/easy_install.py",
line 698, in easy_install
raise DistutilsError(msg)
distutils.errors.DistutilsError: Could not find suitable distribution
for Requirement.parse('setuptools_scm')
E: pybuild pybuild:341: clean: plugin distutils failed with: exit
code=1: python3.7 setup.py clean
(see
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-dnaio.html
for more details)
After adding `python3-setuptools-scm` to build-depdendencies it built
successfully in pbuilder on my local system.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.3.0-2-amd64 (SMP w/3 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--
mvh / best regards
Hans Joachim Desserud
http://desserud.orgdiff --git a/debian/control b/debian/control
index 50b63d5..703ce98 100644
--- a/debian/control
+++ b/debian/control
@@ -8,6 +8,7 @@ Build-Depends: debhelper-compat (= 12),
python3,
python3-dev,
python3-setuptools,
+ python3-setuptools-scm,
python3-pytest,
python3-xopen,
cython3
Bug#944894: /usr/bin/dh_python2: is a #!/usr/bin/python script but does not depend on python
Package: python2 Version: 2.7.17-1 Severity: serious File: /usr/bin/dh_python2 Justification: Policy 3.5 Control: affects -1 src:dbus-python As instructed by the py2removal mass-bug-filing templates, I have been removing references to python from packages I maintain, and replacing them with references to python2 if the Python 2 modules are still needed. This seems to have caused dbus-python to FTBFS when NMU'd for the python3.8 transition: https://buildd.debian.org/status/fetch.php?pkg=dbus-python=amd64=1.2.12-1%2Bb1=1573984727=0 > Unpacking python2 (2.7.17-1) ... ... > Unpacking dh-python (4.20191017) ... ... >debian/rules override_dh_python2 > make[1]: Entering directory '/<>' > py3versions: no X-Python3-Version in control file, using supported versions > dh_python2 > make[1]: dh_python2: Command not found > make[1]: *** [debian/rules:214: override_dh_python2] Error 127 /usr/bin/dh_python2 is in the python2 binary package, which is installed, so this "command not found" shouldn't be caused by absence of /usr/bin/dh_python2. As far as I can work out, it's actually caused by the absence of the interpreter named in its first line, which is /usr/bin/python (shells do not make it easy to distinguish between these two failure modes). dbus-python no longer build-depends on python, so /usr/bin/python2.7 and /usr/bin/python2 exist in the build environment, but /usr/bin/python does not. I think /usr/bin/dh_python2 should now be a #!/usr/bin/python2 (or maybe #!/usr/bin/python2.7) script, instead of a #!/usr/bin/python script. Regards, smcv Complete list of package versions from sbuild log: adduser_3.118 apt_1.8.4 apt-transport-https_1.8.4 autoconf_2.69-11 autoconf-archive_20190106-2 automake_1:1.16.1-4 autopoint_0.19.8.1-9 autotools-dev_20180224.1 base-files_11 base-passwd_3.5.46 bash_5.0-5 binutils_2.33.1-2 binutils-common_2.33.1-2 binutils-x86-64-linux-gnu_2.33.1-2 bsdmainutils_11.1.2+b1 bsdutils_1:2.34-0.1 build-essential_12.8 bzip2_1.0.8-2 ca-certificates_20190110 coreutils_8.30-3+b1 cpp_4:9.2.1-3.1 cpp-9_9.2.1-19 dash_0.5.10.2-6 dbus_1.12.16-2 debconf_1.5.73 debhelper_12.7.1 debian-archive-keyring_2019.1 debianutils_4.9 dh-autoreconf_19 dh-python_4.20191017 dh-strip-nondeterminism_1.6.2-1 diffutils_1:3.7-3 docbook-xml_4.5-9 docbook-xsl_1.79.1+dfsg-2 dpkg_1.19.7 dpkg-dev_1.19.7 dwz_0.13-2 e2fsprogs_1.45.4-1 fakeroot_1.24-1 fdisk_2.34-0.1 file_1:5.37-6 findutils_4.7.0-1 g++_4:9.2.1-3.1 g++-9_9.2.1-19 gcc_4:9.2.1-3.1 gcc-9_9.2.1-19 gcc-9-base_9.2.1-19 gettext_0.19.8.1-9 gettext-base_0.19.8.1-9 gir1.2-glib-2.0_1.62.0-2 gpgv_2.2.17-3 grep_3.3-1 groff-base_1.22.4-3 gzip_1.9-3+b1 hostname_3.23 init-system-helpers_1.57 intltool-debian_0.35.0+20060710.5 libacl1_2.2.53-5 libapparmor1_2.13.3-7 libapt-pkg5.0_1.8.4 libarchive-zip-perl_1.67-1 libasan5_9.2.1-19 libatomic1_9.2.1-19 libattr1_1:2.4.48-5 libaudit-common_1:2.8.5-2 libaudit1_1:2.8.5-2 libbinutils_2.33.1-2 libblkid-dev_2.34-0.1 libblkid1_2.34-0.1 libbsd0_0.10.0-1 libbz2-1.0_1.0.8-2 libc-bin_2.29-3 libc-dev-bin_2.29-3 libc6_2.29-3 libc6-dev_2.29-3 libcap-ng0_0.7.9-2.1 libcc1-0_9.2.1-19 libcom-err2_1.45.4-1 libcroco3_0.6.13-1 libdb5.3_5.3.28+dfsg1-0.6 libdbus-1-3_1.12.16-2 libdbus-1-dev_1.12.16-2 libdebconfclient0_0.250 libdebhelper-perl_12.7.1 libdpkg-perl_1.19.7 libelf1_0.176-1.1 libexpat1_2.2.9-1 libexpat1-dev_2.2.9-1 libext2fs2_1.45.4-1 libfakeroot_1.24-1 libfdisk1_2.34-0.1 libffi-dev_3.2.1-9 libffi6_3.2.1-9 libfile-stripnondeterminism-perl_1.6.2-1 libgcc-9-dev_9.2.1-19 libgcc1_1:9.2.1-19 libgcrypt20_1.8.5-3 libgdbm-compat4_1.18.1-5 libgdbm6_1.18.1-5 libgirepository-1.0-1_1.62.0-2 libglib2.0-0_2.62.2-3 libglib2.0-bin_2.62.2-3 libglib2.0-data_2.62.2-3 libglib2.0-dev_2.62.2-3 libglib2.0-dev-bin_2.62.2-3 libgmp10_2:6.1.2+dfsg-4 libgnutls30_3.6.10-4 libgomp1_9.2.1-19 libgpg-error0_1.36-7 libhogweed5_3.5.1+really3.5.1-2 libicu63_63.2-2 libidn2-0_2.2.0-2 libisl21_0.21-2 libitm1_9.2.1-19 libjs-jquery_3.3.1~dfsg-3 libjs-sphinxdoc_1.8.5-3 libjs-underscore_1.9.1~dfsg-1 liblsan0_9.2.1-19 liblz4-1_1.9.2-2 liblzma5_5.2.4-1+b1 libmagic-mgc_1:5.37-6 libmagic1_1:5.37-6 libmount-dev_2.34-0.1 libmount1_2.34-0.1 libmpc3_1.1.0-1 libmpdec2_2.4.2-2 libmpfr6_4.0.2-1 libncurses6_6.1+20191019-1 libncursesw6_6.1+20191019-1 libnettle7_3.5.1+really3.5.1-2 libp11-kit0_0.23.18.1-2 libpam-modules_1.3.1-5 libpam-modules-bin_1.3.1-5 libpam-runtime_1.3.1-5 libpam0g_1.3.1-5 libpcre16-3_2:8.39-12+b1 libpcre2-16-0_10.32-5+b1 libpcre2-32-0_10.32-5+b1 libpcre2-8-0_10.32-5+b1 libpcre2-dev_10.32-5+b1 libpcre2-posix0_10.32-5+b1 libpcre3_2:8.39-12+b1 libpcre3-dev_2:8.39-12+b1 libpcre32-3_2:8.39-12+b1 libpcrecpp0v5_2:8.39-12+b1 libperl5.30_5.30.0-9 libpipeline1_1.5.1-2 libpython2-dbg_2.7.17-1 libpython2-dev_2.7.17-1 libpython2-stdlib_2.7.17-1 libpython2.7_2.7.17-1 libpython2.7-dbg_2.7.17-1 libpython2.7-dev_2.7.17-1 libpython2.7-minimal_2.7.17-1 libpython2.7-stdlib_2.7.17-1 libpython3-all-dbg_3.7.5-3 libpython3-all-dev_3.7.5-3 libpython3-dbg_3.7.5-3 libpython3-dev_3.7.5-3
Processed: /usr/bin/dh_python2: is a #!/usr/bin/python script but does not depend on python
Processing control commands: > affects -1 src:dbus-python Bug #944894 [python2] /usr/bin/dh_python2: is a #!/usr/bin/python script but does not depend on python Added indication that 944894 affects src:dbus-python -- 944894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937657: Issue with numpy under Python 3.8
Hi Andreas On Sat, 16 Nov 2019 at 16:09, Andreas Tille wrote: > Its not about testing. Its the usual build time test. If I'd do a > source upload of this package it will FTBFS under the current state > of the archive. If you look on the numpy tracker page [1], you'll see there is a note: "This package is part of the ongoing testing transition known as python3.8. Please avoid uploads unrelated to this transition, they would likely delay it and require supplementary work from the release managers." Regards Graham [1] https://tracker.debian.org/pkg/numpy
Bug#944892: oce: autopkgtest fails due to broken CMakeLists.txt
Source: oce Version: 0.18.2-3 Severity: serious The oce autopkgtest fails since cmake 3.15 entered unstable: > CMake Warning (dev) in CMakeLists.txt: > No project() command is present. The top-level CMakeLists.txt file must > contain a literal, direct call to the project() command. Add a line of > code such as > > project(ProjectName) > > near the top of the file, but after cmake_minimum_required(). > > CMake is pretending there is a "project(Project)" command on the first > line. https://ci.debian.net/data/autopkgtest/testing/amd64/o/oce/3434170/log.gz Corresponding cmake documentation: https://cmake.org/cmake/help/v3.16/command/project.html#usage Note that this isn't a new requirement but cmake just started to print a warning. Filing as serious since this blocks cmake migration to testing.
Bug#944893: wslay: autopkgtest fails due to broken CMakeLists.txt
Source: wslay Version: 1.1.0-1 Severity: serious The wslay autopkgtest fails since cmake 3.15 entered unstable: > CMake Warning (dev) in CMakeLists.txt: > No project() command is present. The top-level CMakeLists.txt file must > contain a literal, direct call to the project() command. Add a line of > code such as > > project(ProjectName) > > near the top of the file, but after cmake_minimum_required(). > > CMake is pretending there is a "project(Project)" command on the first > line. > This warning is for project developers. Use -Wno-dev to suppress it. https://ci.debian.net/data/autopkgtest/testing/amd64/w/wslay/3434172/log.gz Corresponding cmake documentation: https://cmake.org/cmake/help/v3.16/command/project.html#usage Note that this isn't a new requirement but cmake just started to print a warning. Filing as serious since this blocks cmake migration to testing.
Bug#934382: marked as done (cvxopt: FTBFS on non-amd64 architectures)
Your message dated Sun, 17 Nov 2019 11:49:34 + with message-id and subject line Bug#934382: fixed in cvxopt 1.2.3+dfsg-2 has caused the Debian Bug report #934382, regarding cvxopt: FTBFS on non-amd64 architectures 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.) -- 934382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cvxopt Version: 1.2.3+dfsg-1 Severity: serious As shown by buildd logs [1], compiling src/C/umfpack.c fails on all architectures except amd64 because umfpack.h is not found. This is because line 61 of setup.py tests whether any files matching /usr/lib/x86_64-linux-gnu/libsuitesparse* exist, which is false on non-amd64 Debian buildds even when libsuitesparse-dev is installed. [1] https://buildd.debian.org/status/package.php?p=cvxopt --- End Message --- --- Begin Message --- Source: cvxopt Source-Version: 1.2.3+dfsg-2 We believe that the bug you reported is fixed in the latest version of cvxopt, 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 934...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Graham Inggs (supplier of updated cvxopt 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: Sun, 17 Nov 2019 11:29:33 + Source: cvxopt Architecture: source Version: 1.2.3+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Graham Inggs Closes: 934382 936357 Changes: cvxopt (1.2.3+dfsg-2) unstable; urgency=medium . * Team upload . [ Adam Conrad ] * multiarch.diff: Fix build with multiarch on !amd64 (Closes: #934382) . [ Graham Inggs ] * Stop building python-cvxopt (Closes: #936357) * Update debian/python-cvxopt-doc.doc-base Checksums-Sha1: 6c850a444b3ac43a5be1f43b6df68bb5c57e3d82 2330 cvxopt_1.2.3+dfsg-2.dsc 03f27783c95d6cd394b6a3aa844b5f1d8ba6712b 6056 cvxopt_1.2.3+dfsg-2.debian.tar.xz Checksums-Sha256: a3d71e833ad42c6b30855b31596b69f4eda5e78b2cf03391d50689e7b6333b47 2330 cvxopt_1.2.3+dfsg-2.dsc 26caa024d6b8f73cce7c2f675708b6c1e41eb793171bea5d25351ef3ce9c46d6 6056 cvxopt_1.2.3+dfsg-2.debian.tar.xz Files: b53bd785e99b000166c93f9987520b0e 2330 python optional cvxopt_1.2.3+dfsg-2.dsc 19201d2e09b66a1975aca5f688838b97 6056 python optional cvxopt_1.2.3+dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl3RMDwACgkQr8/sjmac 4cJ72g//fHBeuF6lTJrwn5J1igYo54DoMwGT7q1ChnX0kGv9BhOD0NN4LslMoZ7t Kss1r/wfZM8aMpgvqb/vRNg+mqj+jq+Fhfms54nm/kTQyP8dBbFppj0hcLn6WrKB i7DCtPaJMtIi1sOTZW29gmS2FG5JsSxq6tN0yHDhvzJVUlpvkcgOKey5/dOpalhR yXQ1yiMAHz5P46jiulw7uGox0A0nf6Zqjw4JzL5D3RD1SLDBf4ZFHyRIGiARfD6o d2QvhYP/m3xkNByBgkm7h2ItnkwwEdT6uXqckInHPU3mhxddMLhgn7WXjZGcocgi RANjB3/phN/mEzvgTS2K8YQNc9kEBiFdLCM9nPKfs5jyxH63WHL0+oJi2yU2THce RG8VlKALArvj6K0O4Iu/mYO5HGhBFoHbZE3FvJss3Zg/9tlKuUsInjtgFhMp/7oj 0wmcOImaZ4ldcaoK/9VHUnIVWxgos5m4Cj+X4YvWQBE6lEgh6jts798vMVc7LZ2x lID8Q1BF4o5+c7llTcjXmnbRCvTo7gTxgk4ZAyodDQtNC1307YfELMXpBU5ZOTxh Z8ejuM1mhFtwKgzxkbG3G3abOXQpz2Sy3ALKpuWVC0rAcZIJ0g9SzRPtCfuz+mG0 25BpZBx9maXXieAYRQZKOhLdI3SFK5QACDVTwLoT6coI2kaaUMc= =vDkN -END PGP SIGNATURE End Message ---
Bug#838994: Bug#891493: Bug#838994: Bug#891493: unresolved gtk2-engines-murrine situation (was: numix-gtk-theme: Undocumented and very likely also broken Breaks against murrine-themes since 2.6.7-2)
Hi Yves-Alexis, On Do 14 Nov 2019 15:09:07 CET, Mike Gabriel wrote: Hi Yves-Alexi, On Do 14 Nov 2019 08:03:57 CET, Yves-Alexis Perez wrote: On Wed, 2019-11-13 at 20:58 +, Mike Gabriel wrote: One last question: For the themes you maintain, is it ok if I provide the "Provides: any-murrine-theme" patches (as MRs or pushed commits) and possibly even NMU them for those murrine-like themes that need them? Like in numix-gtk-theme [1]. Alternative option is me filing wishlist bugs against all related packages. Go ahead with NMU, and yes I guess you can directly commit/push to the repository. At that point I think I should just remove myself from maintainers/uploaders of the theme packages, I'm unlikely to have time for them in the near future. Regards, - -- Yves-Alexis ok. Will do the NMUs. Let me know, if / when you remove yourself from Uploaders: / Maintainer: fields (I will probably miss it if not pinged explicitly). Re-thought this... I just rescheduled the NMUs of numix-gtk-theme and gtk2-engine-murrine, so that we can get the maintainer status straight, before the any-murrine-theme virtual package falls into the archive. As introducing a virtual package is a bit of a hassle regarding Debian Policy inclusion etc. the question here remains about your plans regarding maintainer/uploader status for those murrine theme packages. Because, if you choose to drop from maintainer/uploaders fields, I will go down a different route. In that case, we don't need a compromise, but just the next maintainer's decision. This could save us all (myself, policy team) the trouble of introducing a virtual package for this recommends situation entirely. I as maintainer would simply drop murrine-themes from Recommends: in gtk2-engine-murrine. If you plan to continue with theme maintenance (esp. gtk2-engine-murrine), I am happy to introduce the virtual package any-murrine-theme as discussed earlier, announce it on debian-devel, make sure it gets added to policy, etc.pp. If you plan to drop maintenance sooner or later anyway, then please state that asap (packages are in deferred-15 from today again), so that I can change the uploads and make these bugs go away without introducing a virtual package. Thanks for you time! Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpV5v1S5wOde.pgp Description: Digitale PGP-Signatur
Processed: block 941907 with 944844
Processing commands for cont...@bugs.debian.org: > block 941907 with 944844 Bug #941907 [release.debian.org] transition: ocaml 941907 was blocked by: 943920 941907 was not blocking any bugs. Added blocking bug(s) of 941907: 944844 > thanks Stopping processing here. Please contact me if you need assistance. -- 941907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#940839: openshot-qt: cannot start, crashes immediately
Package: openshot Version: 2.4.3+dfsg1-1 Followup-For: Bug #940839 Dear Maintainer, Starting from the gui and nothing happens, using terminal :~$ openshot-qt Compiled translation resources missing! Loading translations from: /usr/lib/python3/dist-packages/openshot_qt/language Loaded modules from installed directory: /usr/lib/python3/dist- packages/openshot_qt launch:INFO launch:INFOOpenShot (version 2.4.3) launch:INFO app:INFO openshot-qt version: 2.4.3 app:INFO libopenshot version: 0.2.2 app:INFO platform: Linux-5.2.0-3-amd64-x86_64-with-debian-bullseye-sid app:INFO processor: app:INFO machine: x86_64 app:INFO python version: 3.7.5rc1 app:INFO qt5 version: 5.11.3 app:INFO pyqt5 version: 5.12.3 language:INFO Qt Detected Languages: ['en-GB', 'en'] language:INFO LANG Environment Variable: en_GB.UTF-8 language:INFO LOCALE Environment Variable: language:INFO OpenShot Preference Language: Default project_data:INFO Setting default profile to HD 720p 23.98 fps app:INFO Setting font to Cantarell logger_libopenshot:INFO Connecting to libopenshot with debug port: 5556 app:INFO Setting custom dark theme qt.svg: link SVGID_18_-5 hasn't been detected! qt.svg: link SVGID_18_-5 hasn't been detected! qt.svg: link SVGID_22_-5 hasn't been detected! qt.svg: link SVGID_24_-2 hasn't been detected! qt.svg: link SVGID_24_-2 hasn't been detected! QMainWindow::addDockWidget: invalid 'area' argument metrics:INFO Track metric: [200] http://www.google- analytics.com/collect?cid=873cd2e2-76cb-41a1-8e30-1d7341e2c385=1=UA-4381101-5=OpenShot+Video+Editor=1=org.openshot.openshot- qt=2.4.3=en- us=Mozilla%2F5.0+%28X11%3B+Linux+x86_64%29+AppleWebKit%2F537.36+%28KHTML%2C+like+Gecko%29+Chrome%2F37.0.2062.120+Safari%2F537.36=0.2.2=3.7.5rc1=5.11.3=5.12.3=debian- bullseye%2Fsid-=screenview=start=launch-app | (35 bytes) metrics:INFO Track metric: [200] http://www.google- analytics.com/collect?cid=873cd2e2-76cb-41a1-8e30-1d7341e2c385=1=UA-4381101-5=OpenShot+Video+Editor=1=org.openshot.openshot- qt=2.4.3=en- us=Mozilla%2F5.0+%28X11%3B+Linux+x86_64%29+AppleWebKit%2F537.36+%28KHTML%2C+like+Gecko%29+Chrome%2F37.0.2062.120+Safari%2F537.36=0.2.2=3.7.5rc1=5.11.3=5.12.3=debian- bullseye%2Fsid-=screenview=main-screen | (35 bytes) ui_util:INFO Initializing UI for MainWindow ui_util:INFO Binding event MainWindow:actionNew_trigger ui_util:INFO Binding event MainWindow:actionOpen_trigger ui_util:INFO Binding event MainWindow:actionSave_trigger ui_util:INFO Binding event MainWindow:actionUndo_trigger ui_util:INFO Binding event MainWindow:actionSaveAs_trigger ui_util:INFO Binding event MainWindow:actionImportFiles_trigger ui_util:INFO Binding event MainWindow:actionImportImageSequence_trigger ui_util:INFO Binding event MainWindow:actionRedo_trigger ui_util:INFO Binding event MainWindow:actionRemoveClip_trigger ui_util:INFO Binding event MainWindow:actionRemoveTransition_trigger ui_util:INFO Binding event MainWindow:actionExportVideo_trigger ui_util:INFO Binding event MainWindow:actionUploadVideo_trigger ui_util:INFO Binding event MainWindow:actionAddTrack_trigger ui_util:INFO Binding event MainWindow:actionPreferences_trigger ui_util:INFO Binding event MainWindow:actionPlay_trigger ui_util:INFO Binding event MainWindow:actionJumpStart_trigger ui_util:INFO Binding event MainWindow:actionRewind_trigger ui_util:INFO Binding event MainWindow:actionFastForward_trigger ui_util:INFO Binding event MainWindow:actionJumpEnd_trigger ui_util:INFO Binding event MainWindow:actionSaveFrame_trigger ui_util:WARNING Icon theme camera-photo-symbolic not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionArrowTool_trigger ui_util:INFO Binding event MainWindow:actionRazorTool_trigger ui_util:INFO Binding event MainWindow:actionSnappingTool_trigger ui_util:INFO Binding event MainWindow:actionAddMarker_trigger ui_util:INFO Binding event MainWindow:actionPreviousMarker_trigger ui_util:INFO Binding event MainWindow:actionNextMarker_trigger ui_util:INFO Binding event MainWindow:actionFilesShowAll_trigger ui_util:INFO Binding event MainWindow:actionFilesShowVideo_trigger ui_util:INFO Binding event MainWindow:actionFilesShowAudio_trigger ui_util:INFO Binding event MainWindow:actionFilesShowImage_trigger ui_util:INFO Binding event MainWindow:actionTransitionsShowAll_trigger ui_util:INFO Binding event MainWindow:actionTransitionsShowCommon_trigger ui_util:INFO Binding event MainWindow:actionTimelineZoomIn_trigger ui_util:INFO Binding event MainWindow:actionTimelineZoomOut_trigger ui_util:INFO Binding event MainWindow:actionTitle_trigger ui_util:INFO
Bug#931698: fixed in python-pygit2 0.28.2-1
On Tue, 16 Jul 2019 20:40:57 + =?utf-8?b?T25kxZllaiBOb3bDvQ==?= wrote: > python-pygit2 (0.28.2-1) experimental; urgency=medium libgit2 0.28 is now in unstable, please reupload this version to unstable.
Bug#941351: marked as done (peruse: Peruse fails to start)
Your message dated Sun, 17 Nov 2019 08:42:07 +
with message-id
and subject line Bug#941351: fixed in peruse 1.2+dfsg+20191117-1
has caused the Debian Bug report #941351,
regarding peruse: Peruse fails to start
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.)
--
941351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: peruse
Version: 1.2+dfsg+20190713-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
attempting to run peruse (or perusecreator) from the command line
results in the following output:
~$ peruse
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use
QT_QPA_PLATFORM=wayland to run on Wayland anyway.
(peruse:9225): Gtk-WARNING **: 13:14:48.393: Theme parsing error: gtk.css:6:20:
The 'gtk-key-bindings' property has been renamed to '-gtk-ke
y-bindings'
Failed to load the component from disk. Reported error was:
"file:///usr/share/peruse/qml/Main.qml:26 Type PeruseMain unavailable\nfile:///u
sr/share/peruse/qml/PeruseMain.qml:300 Type Settings
unavailable\nfile:///usr/share/peruse/qml/Settings.qml:82 Type
Kirigami.SwipeListItem u
navailable\nfile:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop/SwipeListItem.qml:25
Type T.SwipeListItem una
vailable\nfile:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/SwipeListItem.qml:264
Syntax error\n"
Peruse then fails to start and crashes.
Apparently this is an issue with
/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/SwipeListItem.qml:
function updateVisibleActions(definitelyVisible = false) {
Default values for function parameters are not supported.
It should be:
function updateVisibleActions(definitelyVisible) {
if (definitelyVisible === undefined) definitelyVisible = false;
Unfortunately, then it fails on a missing component:
(peruse:10096): Gtk-WARNING **: 13:24:30.678: Theme parsing error:
gtk.css:6:20: The 'gtk-key-bindings' property has been renamed to '-gtk-k
ey-bindings'
Failed to load the component from disk. Reported error was:
"file:///usr/share/peruse/qml/Main.qml:26 Type PeruseMain unavailable\nfile:///u
sr/share/peruse/qml/PeruseMain.qml:300 Type Settings
unavailable\nfile:///usr/share/peruse/qml/Settings.qml:82 Type
Kirigami.SwipeListItem u
navailable\nfile:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop/SwipeListItem.qml:25
Type T.SwipeListItem una
vailable\nfile:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/SwipeListItem.qml:22
module \"QtQuick.Controls\" version 2.7
is not installed\n"
Cheers,
Matteo Settenvini
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (800, 'unstable'), (800, 'testing'), (780, 'experimental'), (500,
'unstable-debug'), (500, 'testing-debug'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8),
LANGUAGE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages peruse depends on:
ii kio 5.62.1-1
ii libc6 2.29-2
ii libgcc1 1:9.2.1-8
ii libkf5archive5 5.62.0-1
ii libkf5baloo55.62.0-2
ii libkf5configcore5 5.62.0-1
ii libkf5coreaddons5 5.62.0-1
ii libkf5declarative5 5.62.0-1
ii libkf5filemetadata3 5.62.0-1
ii libkf5i18n5 5.62.0-1
ii libkf5kiocore5 5.62.1-1
ii libkf5kiowidgets5 5.62.1-1
ii libqt5core5a5.11.3+dfsg1-4
ii libqt5gui5 5.11.3+dfsg1-4
ii libqt5qml5 5.11.3-4
ii libqt5quick55.11.3-4
ii libqt5sql5 5.11.3+dfsg1-4
ii libqt5widgets5 5.11.3+dfsg1-4
ii libstdc++6 9.2.1-8
ii peruse-common 1.2+dfsg+20190713-1
ii qml-module-org-kde-kirigami25.62.0-2
ii qml-module-org-kde-newstuff 5.62.0-1
ii qml-module-qt-labs-folderlistmodel 5.11.3-4
ii qml-module-qt-labs-settings 5.11.3-4
ii qml-module-qtquick-controls 5.11.3-2
ii qml-module-qtquick-dialogs 5
Processed: tagging 941351
Processing commands for cont...@bugs.debian.org: > tags 941351 + pending Bug #941351 [peruse] peruse: Peruse fails to start Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 941351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
