Bug#896484: marked as done (jmodeltest FTBFS with TeX Live 2018)
Your message dated Sun, 29 Apr 2018 06:05:07 +
with message-id
and subject line Bug#896484: fixed in jmodeltest 2.1.10+dfsg-6
has caused the Debian Bug report #896484,
regarding jmodeltest FTBFS with TeX Live 2018
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.)
--
896484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jmodeltest
Version: 2.1.10+dfsg-5
Severity: serious
Tags: buster sid patch
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jmodeltest.html
...
! Package inputenc Error: Unicode character χ (U+3C7)
(inputenc)not set up for use with LaTeX.
See the inputenc package documentation for explanation.
Type H for immediate help.
...
l.75 ...stic is asymptotically distributed as a χ
2 with q degrees of freedo...
?
! Emergency stop.
...
l.75 ...stic is asymptotically distributed as a χ
2 with q degrees of freedo...
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on manual.log.
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 1
Fix is attached.
Description: Fix FTBFS with TeX Live 2018
Author: Adrian Bunk
--- jmodeltest-2.1.10+dfsg.orig/manual/sec-theory.tex
+++ jmodeltest-2.1.10+dfsg/manual/sec-theory.tex
@@ -72,7 +72,7 @@ In traditional statistical theory, a wid
LRT=2(l_1-l_0)
\]
where $l_1$ is the maximum likelihood under the more parameter-rich, complex
model (alternative hypothesis) and $l_0$ is the maximum likelihood under the
less parameter-rich simple model (null hypothesis).
- When the models compared are nested (the null hypothesis is a special case of
the alternative hypothesis) and the null hypothesis is correct, the LRT
statistic is asymptotically distributed as a χ2 with q degrees of freedom,
where q is the difference in number of free parameters between the two models
\citep{Kendall-1979, Goldman-1993b}. Note that, to preserve the nesting of the
models, the likelihood scores need to be estimated upon the same tree. When
some parameter is fixed at its boundary (p-inv, α), a mixed χ2 is used instead
\citep{Ohta-1992, Goldman-2000}. The behavior of the χ2 approximation for the
LRT has been investigated with quite a bit of detail \citep{Goldman-1993a,
Goldman-1993b, Yang-1995, Whelan-1999, Goldman-2000}.
+ When the models compared are nested (the null hypothesis is a special case of
the alternative hypothesis) and the null hypothesis is correct, the LRT
statistic is asymptotically distributed as a $\chi^2$ with q degrees of
freedom, where q is the difference in number of free parameters between the two
models \citep{Kendall-1979, Goldman-1993b}. Note that, to preserve the nesting
of the models, the likelihood scores need to be estimated upon the same tree.
When some parameter is fixed at its boundary (p-inv, $\alpha$), a mixed
$\chi^2$ is used instead \citep{Ohta-1992, Goldman-2000}. The behavior of the
$\chi^2$ approximation for the LRT has been investigated with quite a bit of
detail \citep{Goldman-1993a, Goldman-1993b, Yang-1995, Whelan-1999,
Goldman-2000}.
\subsection{Hierarchical Likelihood Ratio Tests (hLRT)}
\label{sec:hlrt}
--- End Message ---
--- Begin Message ---
Source: jmodeltest
Source-Version: 2.1.10+dfsg-6
We believe that the bug you reported is fixed in the latest version of
jmodeltest, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 896...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated jmodeltest 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, 29 Apr 2018 07:35:03 +0200
Source: jmodeltest
Binary: jmodeltest
Architecture: source
Version: 2.1.10+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Andreas Ti
Processed: Re: diffoscope FTBFS with file 5.33
Processing commands for cont...@bugs.debian.org: > tags 897099 + pending Bug #897099 [src:diffoscope] diffoscope FTBFS with file 5.33 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 897099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897099 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897099: diffoscope FTBFS with file 5.33
tags 897099 + pending thanks I've updated the diffoscope testsuite to support file 5.33: https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=f800b207a3bde7450705f205ac37993d0666be5c tests/comparators/test_containers.py | 8 +--- tests/comparators/test_gzip.py | 2 ++ tests/comparators/test_ipk.py | 2 ++ tests/data/archive12.diff.txt | 4 ++-- tests/data/containers/magic_gzip | 2 +- tests/data/gzip_metadata_expected_diff | 4 ++-- tests/data/ipk_metadata_expected_diff | 4 ++-- tests/data/quine_expected_diff | 2 +- tests/test_presenters.py | 3 ++- tests/test_quines.py | 2 ++ tests/utils/tools.py | 9 + 11 files changed, 30 insertions(+), 12 deletions(-) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#897099: diffoscope FTBFS with file 5.33
clone 897099 -1 reassign -1 file retitle -1 returns empty string for Berkeley DB databases severity -1 important found -1 5.33-1 affects -1 + diffoscope thanks Hi Adrian, > FTBFS with file 5.33 So, the causes of these are different. The following tests: tests/comparators/test_gzip.py::test_metadata tests/comparators/test_ipk.py::test_metadata tests/test_presenters.py::test_text_proper_indentation tests/test_quines.py::test_difference tests/comparators/test_gzip.py::test_metadata tests/comparators/test_ipk.py::test_metadata .. are failing because file 5.33 is now appending a ", original size XXX" to some output: $ buster file -v | head -n1 file-5.32 $ buster file tests/data/quine.gz tests/data/quine.gz: gzip compressed data, was "recursive", from FAT filesystem (MS-DOS, OS/2, NT) $ sid file -v | head -n1 file-5.33 $ sid tests/data/quine.gz tests/data/quine.gz: gzip compressed data, was "recursive", from FAT filesystem (MS-DOS, OS/2, NT), original size 250 However, the following failing tests: tests/comparators/test_berkeley_db.py::test_identification tests/comparators/test_berkeley_db.py::test_diff tests/comparators/test_berkeley_db.py::test_compare_non_existing ... are caused by file returning an empty string for berkeley DB databases: $ file ./tests/data/test1.db ./tests/data/test1.db: , created: Thu Jan 1 00:38:24 1970 ^ Cloning and re-assigning this second issue. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Processed: Re: Bug#897099: diffoscope FTBFS with file 5.33
Processing commands for cont...@bugs.debian.org: > clone 897099 -1 Bug #897099 [src:diffoscope] diffoscope FTBFS with file 5.33 Bug 897099 cloned as bug 897153 > reassign -1 file Bug #897153 [src:diffoscope] diffoscope FTBFS with file 5.33 Bug reassigned from package 'src:diffoscope' to 'file'. No longer marked as found in versions diffoscope/93. Ignoring request to alter fixed versions of bug #897153 to the same values previously set > retitle -1 returns empty string for Berkeley DB databases Bug #897153 [file] diffoscope FTBFS with file 5.33 Changed Bug title to 'returns empty string for Berkeley DB databases' from 'diffoscope FTBFS with file 5.33'. > severity -1 important Bug #897153 [file] returns empty string for Berkeley DB databases Severity set to 'important' from 'serious' > found -1 5.33-1 Bug #897153 [file] returns empty string for Berkeley DB databases There is no source info for the package 'file' at version '5.33-1' with architecture '' Unable to make a source version for version '5.33-1' Marked as found in versions 5.33-1. > affects -1 + diffoscope Bug #897153 [file] returns empty string for Berkeley DB databases Added indication that 897153 affects diffoscope > thanks Stopping processing here. Please contact me if you need assistance. -- 897099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897099 897153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 897152 to Package erroneously expects googletest headers in /usr/include
Processing commands for cont...@bugs.debian.org: > retitle 897152 Package erroneously expects googletest headers in /usr/include Bug #897152 [src:flightcrew] x Changed Bug title to 'Package erroneously expects googletest headers in /usr/include' from 'x'. > thanks Stopping processing here. Please contact me if you need assistance. -- 897152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897152 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 897104 with 897152
Processing commands for cont...@bugs.debian.org: > block 897104 with 897152 Bug #897104 [googletest] googletest: breakage due to files moved to other packages 897104 was blocked by: 897149 897104 was not blocking any bugs. Added blocking bug(s) of 897104: 897152 > thanks Stopping processing here. Please contact me if you need assistance. -- 897104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897104: googletest: breakage due to files moved to other packages
Hi, The googletest package provides full sources -- including header files -- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of the headers was mistakenly installed into /usr/include. All the listed packages rely on this behaviour and now fail to build since googletest version 1.8.0-9 no longer installs the duplicate header files. I can suggest three alternative approaches to fix this. 1. Modify the build to look for headers in /usr/src/googletest. 2. Change to using pre-build libraries, in which case you would switch build-dependencies to libgtest-dev and libgmock-dev rather than using googletest. 3. Add build-dependency on libgtest-dev to ensure the headers are located in /usr/include as before. If gmock is used, then add a dependency on libgmock-dev as well. -Steve signature.asc Description: PGP signature
Bug#897152: x
Package: src:flightcrew Severity: serious Justification: fails to build from source (but built successfully in the past) Subject: Package erroneously expects googletest headers in /usr/include Package: apt Version: 1.6.1 Severity: serious Justification: fails to build from source (but built successfully in the past) control: block 897104 by -1 Hi, The googletest package provides full sources -- including header files -- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of the headers was mistakenly installed into /usr/include. Your package relies on this behaviour and now fails to build since googletest version 1.8.0-9 no longer installs the duplicate header files. I can suggest three alternative approaches to fix this. 1. Modify the build to look for headers in /usr/src/googletest. 2. Change to using pre-build libraries, in which case you would switch build-dependencies to libgtest-dev and libgmock-dev rather than using googletest. 3. Add build-dependency on libgtest-dev to ensure the headers are located in /usr/include as before. If gmock is used, then add a dependency on libgmock-dev as well. -Steve -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#897151: Package erroneously expects googletest headers in /usr/include
Package: src:protobuf Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, The googletest package provides full sources -- including header files -- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of the headers was mistakenly installed into /usr/include. Your package relies on this behaviour and now fails to build since googletest version 1.8.0-9 no longer installs the duplicate header files. I can suggest three alternative approaches to fix this. 1. Modify the build to look for headers in /usr/src/googletest. 2. Change to using pre-build libraries, in which case you would switch build-dependencies to libgtest-dev and libgmock-dev rather than using googletest. 3. Add build-dependency on libgtest-dev to ensure the headers are located in /usr/include as before. If gmock is used, then add a dependency on libgmock-dev as well. -Steve
Processed: block 897104 with 897149
Processing commands for cont...@bugs.debian.org: > block 897104 with 897149 Bug #897104 [googletest] googletest: breakage due to files moved to other packages 897104 was not blocked by any bugs. 897104 was not blocking any bugs. Added blocking bug(s) of 897104: 897149 > thanks Stopping processing here. Please contact me if you need assistance. -- 897104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897149: Package erroneously expects googletest headers in /usr/include
Package: apt Version: 1.6.1 Severity: serious Justification: fails to build from source (but built successfully in the past) control: block 897104 by -1 Hi, The googletest package provides full sources -- including header files -- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of the headers was mistakenly installed into /usr/include. Your package relies on this behaviour and now fails to build since googletest version 1.8.0-9 no longer installs the duplicate header files. I can suggest three alternative approaches to fix this. 1. Modify the build to look for headers in /usr/src/googletest. 2. Change to using pre-build libraries, in which case you would switch build-dependencies to libgtest-dev and libgmock-dev rather than using googletest. 3. Add build-dependency on libgtest-dev to ensure the headers are located in /usr/include as before. If gmock is used, then add a dependency on libgmock-dev as well. -Steve
Bug#896425: marked as done (python3-django-cors-headers: corsheaders fails to import)
Your message dated Sun, 29 Apr 2018 12:05:51 +1000
with message-id <87h8nuahs0@silverfish.pri>
and subject line corsheaders fails to import
has caused the Debian Bug report #896425,
regarding python3-django-cors-headers: corsheaders fails to import
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
896425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-django-cors-headers
Version: 2.1.0+github-2
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-django-cors-headers importing the module corsheaders
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/corsheaders/__init__.py", line 1, in
from .checks import check_settings # noqa: F401
File "/usr/lib/python3/dist-packages/corsheaders/checks.py", line 5, in
from django.core import checks
ModuleNotFoundError: No module named 'django'
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
--- End Message ---
--- Begin Message ---
Source: django-cors-headers
Source-Version: 2.1.0+github-3
This is actually a duplicate of 896419, because they both are for the
same source package.
--
Brian May
https://linuxpenguins.xyz/brian/--- End Message ---
Bug#896256: marked as done (python-pygal: pygal fails to import)
Your message dated Sun, 29 Apr 2018 01:51:03 +
with message-id
and subject line Bug#896256: fixed in python-pygal 2.4.0-2
has caused the Debian Bug report #896256,
regarding python-pygal: pygal fails to import
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
896256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pygal
Version: 2.4.0-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python-pygal importing the module pygal
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/pygal/__init__.py", line 28, in
import pkg_resources
ImportError: No module named pkg_resources
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
--- End Message ---
--- Begin Message ---
Source: python-pygal
Source-Version: 2.4.0-2
We believe that the bug you reported is fixed in the latest version of
python-pygal, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 896...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ulises Vitulli (supplier of updated python-pygal 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: Sat, 28 Apr 2018 12:31:05 -0300
Source: python-pygal
Binary: python-pygal python3-pygal
Architecture: source all
Version: 2.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Ulises Vitulli
Changed-By: Ulises Vitulli
Description:
python-pygal - Python svg graph plotting library
python3-pygal - Python3 svg graph plotting library
Closes: 896256
Changes:
python-pygal (2.4.0-2) unstable; urgency=medium
.
* Fix pygal fails to import (Closes: #896256).
* Bump up Standards-Version.
Checksums-Sha1:
452ca6e1ebb115f80e6765aa16741994154a0092 2097 python-pygal_2.4.0-2.dsc
2d800b7a31dc2e859cbd85c036675423e4e5566e 2292
python-pygal_2.4.0-2.debian.tar.xz
f7653d95a643af04f8ce20e2976244ab6297d62a 64364 python-pygal_2.4.0-2_all.deb
022b057c498af2c1167a185987ce6016fb30944b 9453
python-pygal_2.4.0-2_amd64.buildinfo
4f5ce1f19622d7c17210bf57969078843aee14b0 63256 python3-pygal_2.4.0-2_all.deb
Checksums-Sha256:
b0d395801cfe59b7b4d7f0d1d25588b9b4d47af574dabd89a8a1c54bcf8e6c5e 2097
python-pygal_2.4.0-2.dsc
1b7c99aadb390b35dcf38f85eba47b429e2e21ab98e1871bddb2f18b41d9bdf8 2292
python-pygal_2.4.0-2.debian.tar.xz
b5bf57bc41c7b07f963e3def592c5039038acbc6bcc8eff86f3540dfd8831e8f 64364
python-pygal_2.4.0-2_all.deb
fe9bfc72cf8485dc25bd90a8a752b0716a84cd212c9d1667fcc69e211dda247f 9453
python-pygal_2.4.0-2_amd64.buildinfo
a031b07f141c9e81d53e6292c35db8dcc44b7989b4c43ff0b87732461f04b90d 63256
python3-pygal_2.4.0-2_all.deb
Files:
bfc73aa9c533642d0980fc3cb713163f 2097 python optional python-pygal_2.4.0-2.dsc
2edf3088e201d318c663ea0637bff59a 2292 python optional
python-pygal_2.4.0-2.debian.tar.xz
5424c4deda2d0806b2a4182d663af936 64364 python optional
python-pygal_2.4.0-2_all.deb
586a646c674fb17d4cdec1b8c0b1b9c7 9453 python optional
python-pygal_2.4.0-2_amd64.buildinfo
35193fe4e50239131e6b053e29b08aa9 63256 python optional
python3-pygal_2.4.0-2_all.deb
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEvQqKQ/VtTywBCMYlg8MHkAqShqAFAlrlHuwACgkQg8MHkAqS
hqDrQA/7Bt/yKPXDKmqbdXDwvF3Hngxwq6a2m6NEKa+L3Ke8YK1+9MIrwnQRTKpP
o5tFf7LkUZN3VrvVwwZtl3fcOR4G3keSSwWYJwMfZRyEJE1pd142PJ41/J7MJk1o
8dHYcGXZkwyBtWHbS7te136US4KIb1boexDXB2OFzuaN+nWr00Ta2B2wpSNkfj+Q
RCWgjHBvOUkP7M64QHaiog2W0BQ9yggLT3VmSat4mtci0xVnRMxN/IIrqafvrFua
rWF7UkIud95cUGKKImCYOPsg2319n4DhQm5co6KpYbjIFE8X7ZzbW6LnLNEPPCl9
vtaHGifovhMf3OtEVIM+71bcxtomVjbMWEC06mAbMSXYxVWS6fjKiqVDoKz21xbu
9aIudS3sHdKUA3o5jnM6KECA4wu+di+KHuvnnGDCKavJCIb/5nnpJjfhEOB09Xtc
ESH2ki3
Bug#896998: closed by Matthias Klose (Bug#896998: fixed in python-pip 9.0.1-2.2)
On Sat, Apr 28, 2018 at 03:15:07PM +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the src:python-pip package: > > #896998: python-pip: missing required _vendor module in 9.0.1-2.1 > > It has been closed by Matthias Klose . ... > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Format: 1.8 > Date: Sat, 28 Apr 2018 15:31:03 +0200 > Source: python-pip > Binary: python-pip python3-pip python-pip-whl > Architecture: source > Version: 9.0.1-2.2 > Distribution: unstable > Urgency: medium > Maintainer: Debian Python Modules Team > > Changed-By: Matthias Klose > Description: > python-pip - Python package installer > python-pip-whl - Python package installer > python3-pip - Python package installer > Closes: 896998 > Changes: > python-pip (9.0.1-2.2) unstable; urgency=medium > . >* Non-maintainer upload. >* debian/pip.dependencies: Add certifi. >* debian/rules: run dirtbike for certifi. >* pip/_vendor/__init__.py: Use the unvendored urllib3. Closes: #896998. Thank you Matthias, I'm grateful that you fixed this so quickly! :-) Cheers, Nicholas signature.asc Description: PGP signature
Bug#895068: xerces-c: baseline violation on i386' from 'freecad does not start : "Illegal Instruction" returned
The fix for stable has been uploaded to proposed-updates, and should be included in the next point release. Oldstable was not affected by this bug, so nothing was needed there.
Processed: fixed 895068 in 3.1.4+debian-2+deb9u1
Processing commands for cont...@bugs.debian.org:
> fixed 895068 3.1.4+debian-2+deb9u1
Bug #895068 {Done: William Blough } [src:xerces-c] xerces-c:
baseline violation on i386
Marked as fixed in versions xerces-c/3.1.4+debian-2+deb9u1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
895068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: fixed 894050 in 3.1.1-5.1+deb8u4
Processing commands for cont...@bugs.debian.org: > fixed 894050 3.1.1-5.1+deb8u4 Bug #894050 [src:xerces-c] xerces-c: CVE-2017-12627: Null pointer dereference while processing the path to DTD allows denial of service Marked as fixed in versions xerces-c/3.1.1-5.1+deb8u4. > thanks Stopping processing here. Please contact me if you need assistance. -- 894050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 894050
Processing commands for cont...@bugs.debian.org: > close 894050 Bug #894050 [src:xerces-c] xerces-c: CVE-2017-12627: Null pointer dereference while processing the path to DTD allows denial of service Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 894050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 894050 in 3.1.4+debian-2+deb9u1
Processing commands for cont...@bugs.debian.org: > fixed 894050 3.1.4+debian-2+deb9u1 Bug #894050 [src:xerces-c] xerces-c: CVE-2017-12627: Null pointer dereference while processing the path to DTD allows denial of service Marked as fixed in versions xerces-c/3.1.4+debian-2+deb9u1. > thanks Stopping processing here. Please contact me if you need assistance. -- 894050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#896227: marked as done (python3-pyroma: pyroma fails to import)
Your message dated Sat, 28 Apr 2018 21:35:30 +
with message-id
and subject line Bug#896227: fixed in pyroma 2.3-1
has caused the Debian Bug report #896227,
regarding python3-pyroma: pyroma fails to import
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
896227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pyroma
Version: 2.0.2-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-pyroma importing the module pyroma
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/pyroma/__init__.py", line 4, in
from pyroma import projectdata, distributiondata, pypidata, ratings
File "/usr/lib/python3/dist-packages/pyroma/projectdata.py", line 7, in
from distutils import core
ImportError: cannot import name 'core'
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
--- End Message ---
--- Begin Message ---
Source: pyroma
Source-Version: 2.3-1
We believe that the bug you reported is fixed in the latest version of
pyroma, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 896...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Federico Ceratto (supplier of updated pyroma 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: Sat, 28 Apr 2018 15:59:20 +0100
Source: pyroma
Binary: python-pyroma python3-pyroma
Architecture: source
Version: 2.3-1
Distribution: unstable
Urgency: medium
Maintainer: Federico Ceratto
Changed-By: Federico Ceratto
Description:
python-pyroma - Python packaging quality checker
python3-pyroma - Python packaging quality checker (Python3 build)
Closes: 896227
Changes:
pyroma (2.3-1) unstable; urgency=medium
.
* Add dependency on python3-distutils. Thanks Matthias Klose
(Closes: #896227)
* New upstream release
Checksums-Sha1:
583bb7ef6175b5f41969582a0efdba91210d817b 2005 pyroma_2.3-1.dsc
ee5fa6902d59620aad88600f0ca322e619de7cbc 342100 pyroma_2.3.orig.tar.gz
2ad5268d1aa2b7b593be1424292c2b2d1c112daf 2848 pyroma_2.3-1.debian.tar.xz
72c68577f732e0304a2230cdf6b05f7b8be2e372 6706 pyroma_2.3-1_amd64.buildinfo
Checksums-Sha256:
ed62404b9a0c483a1bbf08a8a3c8e7759456248bb0f9576f6fe83d8051740a33 2005
pyroma_2.3-1.dsc
3775fd4e1b2218a2babc08ed884f0fa00dc626f162eeb9e9c6c081a2ca1452a2 342100
pyroma_2.3.orig.tar.gz
b8840988b95567037601ccdf0da4b3fd3f07feb118d9f00f607719e5e64a8601 2848
pyroma_2.3-1.debian.tar.xz
9bb62ff1725ea6dd762010d6d4ad38abc7891c359831d9f04140d6e14f510080 6706
pyroma_2.3-1_amd64.buildinfo
Files:
6c659d5062cd0926c005c68edac37a2d 2005 python optional pyroma_2.3-1.dsc
b7e542e2c5db96cf32b09d64f86a89d3 342100 python optional pyroma_2.3.orig.tar.gz
a5d682fe528faefb90ec591ea801dd3a 2848 python optional
pyroma_2.3-1.debian.tar.xz
5f5c4a7a4b7a31c5a33ea8cf4c2b3a3e 6706 python optional
pyroma_2.3-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEfKfd+zM5IUCMbyuWbzG8RPUXfaoFAlrk5nQACgkQbzG8RPUX
faq5ww/+N5nDxQIFe97PomxzD4ZCJgkyAjt0A531NApSLndNxFjbguMd4SOYxega
5CW7Qyou0I0/Wc4gMCy5vj/C4EpLdDK5VZX0ZWs3nIF2w0wiEKQ2ceJwNHlgNrVX
pqk7tAKHXRekJSKrRTxYBNXRl38DRYBACrl3eJ64FMnWhbWnNpCSLBnSYivop/oG
DT1kt3sLUf08rhY+3d1c+552jXy51IKeeN+aeMLj7plRTFdjilkfHbpKSEz52WnM
x3yncWpW3Xp5siJ5Foc6IL/XHUah6GLTYtGizJ5bhgpGfAWxQ/Kir5/DfFGXjGG1
hrDeKYAFUmDpa9LBlNhtfMReoDtOpvwxZnQRFRtdngXlFflFFI9/pbcEBBrhcvfR
GEGdLtgrVCe6VfrwMOnkfK46XOcenZDBpJ/vz+Ya367QyJO5hosKZSz/ghJZutLd
xCjQVa6uusa9JHUcdeseED6mTmAB0xUMq8k/qhQeFwfOt3n6IjiEEEdJbac4ftp0
JrQbsslnxXPKf+FAwGZfTGJ6hOZD9XtsIFj7ZRwzoSOg+VkYkbY3PsNdX+f0bBju
mViUHy5azX/FwfxiWnpl/wppqQ2PU9ocFkJzgSSi8Q8aWWKOhzySOGSqEh62tq9e
cNDQS3ETv
Bug#892399: marked as done (kodi: build-depends on GCC 6)
Your message dated Sat, 28 Apr 2018 21:35:03 + with message-id and subject line Bug#892399: fixed in kodi 2:17.6+dfsg1-2 has caused the Debian Bug report #892399, regarding kodi: build-depends on GCC 6 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.) -- 892399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kodi Severity: serious Tags: sid buster User: debian-...@lists.debian.org Usertags: gcc-6-rm Hi, kodi build-depends on GCC 6. We now have GCC 7 (default) and GCC 8 in the archive, so please make your package build with a newer compiler (preferably the default one) again, since we'd like to remove GCC 6 from testing before the buster release. Cheers, Emilio --- End Message --- --- Begin Message --- Source: kodi Source-Version: 2:17.6+dfsg1-2 We believe that the bug you reported is fixed in the latest version of kodi, 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 892...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Balint Reczey (supplier of updated kodi 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: Sat, 28 Apr 2018 20:50:46 +0200 Source: kodi Binary: kodi kodi-data kodi-bin kodi-eventclients-common kodi-eventclients-dev kodi-eventclients-wiiremote kodi-eventclients-ps3 kodi-eventclients-kodi-send kodi-addons-dev kodi-repository-kodi xbmc xbmc-bin xbmc-eventclients-common xbmc-eventclients-dev xbmc-eventclients-wiiremote xbmc-eventclients-ps3 xbmc-eventclients-xbmc-send xbmc-addons-dev Architecture: source Version: 2:17.6+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Balint Reczey Description: kodi - Open Source Home Theatre (executable binaries) kodi-addons-dev - Open Source Home Theatre (Addons Dev package) kodi-bin - Open Source Home Theatre (architecture-dependent files) kodi-data - Open Source Home Theatre (arch-independent data package) kodi-eventclients-common - Open Source Home Theatre (Event Client Common package) kodi-eventclients-dev - Open Source Home Theatre (Event Client Dev package) kodi-eventclients-kodi-send - Open Source Home Theatre (Event Client Kodi-SEND package) kodi-eventclients-ps3 - Open Source Home Theatre (Event Client PS3 package) kodi-eventclients-wiiremote - Open Source Home Theatre (Event Client WII Remote support package kodi-repository-kodi - Open Source Home Theatre (official addons repository feed) xbmc - transitional dummy package xbmc-addons-dev - transitional dummy package xbmc-bin - transitional dummy package xbmc-eventclients-common - transitional dummy package xbmc-eventclients-dev - transitional dummy package xbmc-eventclients-ps3 - transitional dummy package xbmc-eventclients-wiiremote - transitional dummy package xbmc-eventclients-xbmc-send - transitional dummy package Closes: 892399 Launchpad-Bugs-Fixed: 1685918 Changes: kodi (2:17.6+dfsg1-2) unstable; urgency=medium . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Set Vcs-* to salsa.debian.org . [ Rechi ] * Drop build dependencies on libboost-* Boost isn't required since v17. . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Balint Reczey ] * Ship only Kodi desktop session without the xbmc.desktop duplicate link * Stop build-depending on versioned GCC, this workaround is not needed anymore (Closes: #892399) Thanks to Adrian Bunk who also proposed a patch and a delayed NMU. * Stop shipping kodi.service Please use a lightweight display manager set up to autologin instead. * Add d/source.lintian-overrides to d/source/lintian-overrides to keep lintian happy . [ Rolf Leggewie ] * demote hard font dependencies from Depends to Recommends (LP: #1685918) Checksums-Sha1: a99ecada05be9416f67c9b81b7b114e176dc4bc9 5705 kodi_17.6+dfsg1-2.dsc 13c9942ea5ffef6141e4106fc6c7dbac9155677c 105268 kodi_17.6+dfsg1-2.debian.tar.xz d1a48a0d25a17213a2bc7f32042e626b097a611e 17680 kodi_17.6+dfsg1-2_sou
Processed: Re: Bug#897133: juffed FTBFS with cmake 3.11.1-1
Processing control commands: > severity -1 normal Bug #897133 [src:juffed] juffed FTBFS with cmake 3.11.1-1 Severity set to 'normal' from 'serious' -- 897133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897133: juffed FTBFS with cmake 3.11.1-1
Control: severity -1 normal We and play this for some time - i noticed it and it is not serious. If you think it is serious, fix it - or be quiet. I would see it as serious if we are near a freeze - but we are not. God damn, i really hate it - maybe i should just quit maintaining the package right now and file a RM request. And no, i really want any discussions about and i really don't want to be polite. If you wanted to see me pissed - congratulations, goal reached, i'm really and serious pissed.
Bug#896356: marked as done (python-kajiki: kajiki fails to import)
Your message dated Sat, 28 Apr 2018 21:13:10 +
with message-id
and subject line Bug#896356: fixed in python-kajiki 0.7.1-2
has caused the Debian Bug report #896356,
regarding python-kajiki: kajiki fails to import
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
896356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-kajiki
Version: 0.7.1-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python-kajiki importing the module kajiki
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/kajiki/__init__.py", line 7, in
from .loader import MockLoader, FileLoader, PackageLoader
File "/usr/lib/python2.7/dist-packages/kajiki/loader.py", line 7, in
import pkg_resources
ImportError: No module named pkg_resources
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
--- End Message ---
--- Begin Message ---
Source: python-kajiki
Source-Version: 0.7.1-2
We believe that the bug you reported is fixed in the latest version of
python-kajiki, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 896...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated python-kajiki 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: Sat, 28 Apr 2018 19:44:06 +
Source: python-kajiki
Binary: python-kajiki python-kajiki-doc python3-kajiki
Architecture: source all
Version: 0.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Thomas Goirand
Description:
python-kajiki - Really fast well-formed xml templates - Python 2.x
python-kajiki-doc - Really fast well-formed xml templates - doc
python3-kajiki - Really fast well-formed xml templates - Python 3.x
Closes: 896332 896356
Changes:
python-kajiki (0.7.1-2) unstable; urgency=medium
.
[ Ondřej Nový ]
* d/control: Set Vcs-* to salsa.debian.org
* d/copyright: Use https protocol in Format field
* d/watch: Use https protocol
* d/changelog: Remove trailing whitespaces
.
[ Thomas Goirand ]
* Team upload.
* Ran wrap-and-sort -bast.
* Add missing python{3,}-pkg-resources runtime depends
(Closes: #896356, #896332).
Checksums-Sha1:
9826f7916b7a65c6e8aea3873e3675021a0e321d 2338 python-kajiki_0.7.1-2.dsc
7c17733bb8f5fececfe143cf0eb984f4dc257c05 3684
python-kajiki_0.7.1-2.debian.tar.xz
879fe0fa24ab9291e7c79e9c4f356c05fb780347 86376
python-kajiki-doc_0.7.1-2_all.deb
84addbfbef43419f9ddd58e415c0302bf287d785 55296 python-kajiki_0.7.1-2_all.deb
070fb51c5e3226d027d9b0d8a10fffebafc1 8628
python-kajiki_0.7.1-2_amd64.buildinfo
13a5432a6810fb787e4cc335d0cc9bada54a960d 55096 python3-kajiki_0.7.1-2_all.deb
Checksums-Sha256:
0ae3e3b31f7a25d5ebf5c9984feb8b96efc17e80e135cac8e27b8b250b3a8284 2338
python-kajiki_0.7.1-2.dsc
95fcbdb2c956b2e08a1b66bcf3ca113e2014917289a9422368dbfd40971ef931 3684
python-kajiki_0.7.1-2.debian.tar.xz
5c246c84b60cd3d14deb24c5c49022c90fbfa9e79de457e099a7e931ce2da0b5 86376
python-kajiki-doc_0.7.1-2_all.deb
cf2a4b306aa78ba4f59c99211852f1bd24d1c6f52b0dfc2ccb0b314d6b2d88d1 55296
python-kajiki_0.7.1-2_all.deb
73cd4ae5480067b9d66f9725c0a938445019574530c36c001b8084b3654ae5a0 8628
python-kajiki_0.7.1-2_amd64.buildinfo
2ec983c6708b1e2fd7cdab798454bffaf27f23eea8d814a7b2ae88954e52f8dc 55096
python3-kajiki_0.7.1-2_all.deb
Files:
188e7c38c35af232424ef8ddff1a2007 2338 python optional python-kajiki_0.7.1-2.dsc
cd734e298c6c075a59b9525de6887bc7 3684 python optional
python-kajiki_0.7.1-2.debian.tar.xz
59e3a60d9882a6f9b175ada6efb0662e 86376 doc optional
pytho
Bug#896332: marked as done (python3-kajiki: kajiki fails to import)
Your message dated Sat, 28 Apr 2018 21:13:10 +
with message-id
and subject line Bug#896332: fixed in python-kajiki 0.7.1-2
has caused the Debian Bug report #896332,
regarding python3-kajiki: kajiki fails to import
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
896332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896332
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-kajiki
Version: 0.7.1-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-kajiki importing the module kajiki
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/kajiki/__init__.py", line 7, in
from .loader import MockLoader, FileLoader, PackageLoader
File "/usr/lib/python3/dist-packages/kajiki/loader.py", line 7, in
import pkg_resources
ModuleNotFoundError: No module named 'pkg_resources'
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
--- End Message ---
--- Begin Message ---
Source: python-kajiki
Source-Version: 0.7.1-2
We believe that the bug you reported is fixed in the latest version of
python-kajiki, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 896...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated python-kajiki 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: Sat, 28 Apr 2018 19:44:06 +
Source: python-kajiki
Binary: python-kajiki python-kajiki-doc python3-kajiki
Architecture: source all
Version: 0.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Thomas Goirand
Description:
python-kajiki - Really fast well-formed xml templates - Python 2.x
python-kajiki-doc - Really fast well-formed xml templates - doc
python3-kajiki - Really fast well-formed xml templates - Python 3.x
Closes: 896332 896356
Changes:
python-kajiki (0.7.1-2) unstable; urgency=medium
.
[ Ondřej Nový ]
* d/control: Set Vcs-* to salsa.debian.org
* d/copyright: Use https protocol in Format field
* d/watch: Use https protocol
* d/changelog: Remove trailing whitespaces
.
[ Thomas Goirand ]
* Team upload.
* Ran wrap-and-sort -bast.
* Add missing python{3,}-pkg-resources runtime depends
(Closes: #896356, #896332).
Checksums-Sha1:
9826f7916b7a65c6e8aea3873e3675021a0e321d 2338 python-kajiki_0.7.1-2.dsc
7c17733bb8f5fececfe143cf0eb984f4dc257c05 3684
python-kajiki_0.7.1-2.debian.tar.xz
879fe0fa24ab9291e7c79e9c4f356c05fb780347 86376
python-kajiki-doc_0.7.1-2_all.deb
84addbfbef43419f9ddd58e415c0302bf287d785 55296 python-kajiki_0.7.1-2_all.deb
070fb51c5e3226d027d9b0d8a10fffebafc1 8628
python-kajiki_0.7.1-2_amd64.buildinfo
13a5432a6810fb787e4cc335d0cc9bada54a960d 55096 python3-kajiki_0.7.1-2_all.deb
Checksums-Sha256:
0ae3e3b31f7a25d5ebf5c9984feb8b96efc17e80e135cac8e27b8b250b3a8284 2338
python-kajiki_0.7.1-2.dsc
95fcbdb2c956b2e08a1b66bcf3ca113e2014917289a9422368dbfd40971ef931 3684
python-kajiki_0.7.1-2.debian.tar.xz
5c246c84b60cd3d14deb24c5c49022c90fbfa9e79de457e099a7e931ce2da0b5 86376
python-kajiki-doc_0.7.1-2_all.deb
cf2a4b306aa78ba4f59c99211852f1bd24d1c6f52b0dfc2ccb0b314d6b2d88d1 55296
python-kajiki_0.7.1-2_all.deb
73cd4ae5480067b9d66f9725c0a938445019574530c36c001b8084b3654ae5a0 8628
python-kajiki_0.7.1-2_amd64.buildinfo
2ec983c6708b1e2fd7cdab798454bffaf27f23eea8d814a7b2ae88954e52f8dc 55096
python3-kajiki_0.7.1-2_all.deb
Files:
188e7c38c35af232424ef8ddff1a2007 2338 python optional python-kajiki_0.7.1-2.dsc
cd734e298c6c075a59b9525de6887bc7 3684 python optional
python-kajiki_0.7.1-2.debian.tar.xz
59e3a60d9882a6f9b175ada6efb0662e 86376 doc optiona
Bug#884350: marked as done (grr-client-templates-installer: belongs in package area contrib (not main))
Your message dated Sat, 28 Apr 2018 21:07:40 + with message-id and subject line Bug#884350: fixed in grr 3.1.0.2+dfsg-5 has caused the Debian Bug report #884350, regarding grr-client-templates-installer: belongs in package area contrib (not main) 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.) -- 884350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: grr-client-templates-installer Version: 3.1.0.2+dfsg-4 Severity: serious Justification: Policy 2.2.1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package description includes this: > This package contains a download script that fetches compoments which > are used to build Linux, Windows, and MacOSX client installers are > built and which cannot currently be built from source on a Debian > system Debian Policy § 2.2.1 includes this: > the packages in main [...] must not require or recommend a package > outside of main for compilation or execution This package therefore belongs in the contrib package area. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAloyZvwACgkQLHwxRsGg ASEEdBAAqmm4zZDXOk336bvxjmu6Y6yutHWk0PlFejN/rd13/KI8b/huaY7EVtzf YoR9/VTNEbqzOLbBp8z4kk2JW0lfH+vIjepbhHvM0ear3dtWoC9Cxionqd5q7lpF cClf8hxKm768t6EB2osDdCW96TMKPcOOTytLZtUSopuDMfLnPJstQOZvWFb1/m/9 JTBy8fGLbDPLqYo2V83XoRsXRKDKUWnqhA9FEFyw7Krn8SFSSOY6HgvvRjMn0kGe SQhj/llf1F6O5+1K9wdiRlR5mSDvjlfD5cQ2/Zrqo01me3uRpP4QZNaX6KvkoIB6 re/o80AOgWW/+gboCnCUUhtadSexhJ/cJDdzTFUH/lyn9Nqi3W/S+bA/sH7J87x6 1PJ+D6vnu3ZWzmrHRkCcOriHD+gSLliidszESbsmzjeka4s8HmtzZiVS9bfTjFEZ 1DzvlFwNFkynYp7pv3sPkye3xazsefbVrbDcoyZbNIyjiqqYx+s95r9uaIUUDObC O8tYKxD2bGcO0PSJYzY1Oxf+uFnkU25t0q9WItA2E7GswXcfSvlB70RC5wz1W3sw N25YvESLeRU/2gevVUBIwOi/hei961kZ6osox2D8W4oqCkDOwMiu8TJx7NClYxBe JMPFfaxwLEzBs0Mu84hAegQzaiveud0aXZ1HqcpI65mU7mcZ6Ic= =EopP -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: grr Source-Version: 3.1.0.2+dfsg-5 We believe that the bug you reported is fixed in the latest version of grr, 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 884...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated grr 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: Sat, 28 Apr 2018 21:58:09 +0200 Source: grr Binary: grr-server grr-client-templates-installer Architecture: source Version: 3.1.0.2+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Hilko Bengen Description: grr-client-templates-installer - incident response framework - installer for client templates grr-server - incident response framework - server Closes: 884350 Changes: grr (3.1.0.2+dfsg-5) unstable; urgency=medium . [ Sascha Steinbiss ] * Configure test installation before running autopkgtest. * set testing Django secret key . [ Raphaël Hertzog ] * Update team maintainer address to Debian Security Tools * Update Vcs-Git and Vcs-Browser for the move to salsa.debian.org . [ Hilko Bengen ] * Modify debian/watch so that release candidates are found * Update Makefile.nanny: Fix static build, strip binaries * Turn Depends for client template package into Suggests (Closes: #884350) * Build Windows "nanny" programs from source, using MinGW * update-grr-client-templates: Do not download nanny binaries * Refuse to be installed with "current" client template packages thata include nanny binaries * Copy forensic-artifacts definitions into grr-server package, set Buil-tUsing header Checksums-Sha1: 11ee9b6f8da38cbbb7ec68032a6a2f1fd42b15f7 2527 grr_3.1.0.2+dfsg-5.dsc f8ec79911c01d6f0501ba40878dcb108bc3495f6 26104 grr_3.1.0.2+dfsg-5.debian.tar.xz b70b7eacd43797a3feaba339ffcb3cb2a0d18b88 8379 grr_3.1.0.2+dfsg-5_source.buildinfo Checksums-Sha256: 04a9260071db032a77d7fbc9fc28102164abea4e6c78575606eaa87a7d48eb9b 2527 grr_3.1.0.2+dfsg-5.dsc 657b8206f90b5ffa881ac9998dbb217f6c01727b7df3f4a9f080d2bbd4a4 26104 grr_3.1.0.2+dfsg-5.debian.tar.xz 088caf580a15d515794dd1ada85bca63d83b5959e8e95f864e
Bug#897115: marked as done (aoflagger FTBFS with cmake 3.11.1)
Your message dated Sat, 28 Apr 2018 21:05:15 + with message-id and subject line Bug#897115: fixed in aoflagger 2.10.0-3 has caused the Debian Bug report #897115, regarding aoflagger FTBFS with cmake 3.11.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 897115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: aoflagger Version: 2.10.0-2 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/aoflagger.html ... -- Looking for posix_fallocate -- Looking for posix_fallocate - found CMake Error at CMake/CheckCXXSymbolExists.cmake:48 (_CHECK_SYMBOL_EXISTS): Unknown CMake command "_CHECK_SYMBOL_EXISTS". Call Stack (most recent call first): src/CMakeLists.txt:9 (CHECK_CXX_SYMBOL_EXISTS) -- Configuring incomplete, errors occurred! --- End Message --- --- Begin Message --- Source: aoflagger Source-Version: 2.10.0-3 We believe that the bug you reported is fixed in the latest version of aoflagger, 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 897...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ole Streicher (supplier of updated aoflagger 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: Sat, 28 Apr 2018 21:41:14 +0200 Source: aoflagger Binary: aoflagger libaoflagger0 aoflagger-dev Architecture: source Version: 2.10.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Astro Team Changed-By: Ole Streicher Description: aoflagger - Find RFI in radio astronomical observations aoflagger-dev - Find RFI in radio astronomical observations (development files) libaoflagger0 - Find RFI in radio astronomical observations (shared lib) Closes: 897115 Changes: aoflagger (2.10.0-3) unstable; urgency=medium . * Remove outdated CheckCXXSymbolExists (Closes: #897115) * Push Standards-Version to 4.1.4. No changes needed. * Remove unneeded --parallel from d/rules * Mark aoflagger-dev as Multi-Arch: same as hinted Checksums-Sha1: cefc8cb05734b974cf06a7e1995517a6ab1f36b2 2450 aoflagger_2.10.0-3.dsc 064b2f74f3c17bc46bccd889f8fa1ac2f277eabc 10076 aoflagger_2.10.0-3.debian.tar.xz Checksums-Sha256: 777f409e8f8b8485672de4ddb6a8c88e6def66ab681a5cad99df9f33dae6bbc4 2450 aoflagger_2.10.0-3.dsc 37f6f8e0b75a002c00199a4afd69f552ff45947e52c69667083237ad3b46fba8 10076 aoflagger_2.10.0-3.debian.tar.xz Files: 5bc41fdec623cfe0e2b0e3a0414f72df 2450 science optional aoflagger_2.10.0-3.dsc 23ec772a28a651148b7fd4a4f99aa525 10076 science optional aoflagger_2.10.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE7/BpV0Ra2/h0L3qtmk9WvbkOGL0FAlrk0IMACgkQmk9WvbkO GL1FtQ/6A/3NwCT2c+HwaKw+G45Gk9QM9kcUuXoofDP6MX31Gliib7EjkAQN8FnW gB8u9xJoz05jcTpmLy0z1igENpPnmZjuyeaxdFe7d6sikjtoARVUk8bk9MMzTUNz 45MAM/HJK5RkoagDSL5Jy9DP+XWI6wxcR4wC1YmgfUnSHG2DPzYUTy69eZV8cHrj Kl627XGlXnLhWoE/P+DnFAt1ZO/t1nfqdT9CLnBAUP+p9VPOeiUZaITU96ZPN3cq fCa2fNGGgdrU6P0LPuEP5WHXudyb13DnBwEakcI2Xw3TFAorTys7T+skuWQ0EzBW z+B6P0qiRyKsDZstBEOwD8b5X2FWjdwb/MLY9moU4r6a+hDR1oyoP1gxnFLd4ukk Qk0Cf3kNdJ8Gp3TqkkjAahBvb+JgxhFBYI6x8FUE/2fPeecaY0jAtP3YHtzq9sQ9 WM2h19lfYSZIserhkX/iDBl/wXKCpoBECzfjeX3XJMfgLdUYHTiEhnUpfa1TOfNM s+ccUH8tKiZ/SLcIx0Mda8y+Inv6BNPdQ0Y+yzeUnBSZjLhOr0tHGP2kEsF8lL3u B1VrJxGEfTNvuGCRuUcTuwTOJMkeUfPopkXg1G+xe2pLiLuWznwZRnsv2B/XpMJo FziTeiDYQ/dJe+uhjLc1+JMUl0hwHjwhG9BQ/Cjl3JF/YxGLHC0= =VD5d -END PGP SIGNATURE End Message ---
Processed: Re: Bug#897133: juffed FTBFS with cmake 3.11.1-1
Processing control commands: > severity -1 serious Bug #897133 [src:juffed] juffed FTBFS with cmake 3.11.1-1 Severity set to 'serious' from 'normal' -- 897133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: mark python3.7 as notfound in recent upload
Processing commands for cont...@bugs.debian.org:
> notfound 894204 python3.7/3.7.0~b3-1
Bug #894204 {Done: Matthias Klose }
[libpython3.6-stdlib,libpython3.7-stdlib]
libpython3.6-stdlib,libpython3.7-stdlib: missing Breaks: python3-distutils (<<
3.6.5~rc1-2)
No longer marked as found in versions python3.7/3.7.0~b3-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
894204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: juffed FTBFS with cmake 3.11.1-1
Processing control commands: > severity -1 normal Bug #897133 [src:juffed] juffed FTBFS with cmake 3.11.1-1 Severity set to 'normal' from 'serious' > forward -1 https://github.com/Mezomish/juffed/pull/102 Unknown command or malformed arguments to command. -- 897133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#896356: Bug #896356 in python-kajiki marked as pending
Control: tag -1 pending
Hello,
Bug #896356 in python-kajiki 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-kajiki/commit/6dbb58ee164a32d07e027f7004b06b403c21c3ef
* Add missing python{3,}-pkg-resources runtime depends
(Closes: #896356, #896332).
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/896356
Bug#897133: juffed FTBFS with cmake 3.11.1-1
Control: severity -1 normal Control: forward -1 https://github.com/Mezomish/juffed/pull/102 https://github.com/Mezomish/juffed/pull/102 - so until this is merged i will do nothing about it. Cheers Alf
Processed: Bug #896332 in python-kajiki marked as pending
Processing control commands: > tag -1 pending Bug #896332 [python3-kajiki] python3-kajiki: kajiki fails to import Added tag(s) pending. -- 896332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#896332: Bug #896332 in python-kajiki marked as pending
Control: tag -1 pending
Hello,
Bug #896332 in python-kajiki 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-kajiki/commit/6dbb58ee164a32d07e027f7004b06b403c21c3ef
* Add missing python{3,}-pkg-resources runtime depends
(Closes: #896356, #896332).
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/896332
Processed: Bug #896356 in python-kajiki marked as pending
Processing control commands: > tag -1 pending Bug #896356 [python-kajiki] python-kajiki: kajiki fails to import Added tag(s) pending. -- 896356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#888678: Please NMU dirdiff
Hello Sergei, dirdiff is going to be removed from unstable/testing on the 5th of Mai. Unless you have been in communication with Santiago and he has a plan on how to move forward with this issue, I'd ask you to please do the NMU. I am no tcl/tk expert but I have read your patch and it looks good to me. So, unless Santiago objects, I'd ask you to please NMU. Also, it'd be nice, if you could tell upstream (Paul Mackerras) about the fixes so it gets included upstream. *t
Bug#897133: juffed FTBFS with cmake 3.11.1-1
Source: juffed Version: 0.10-85-g5ba17f9-17 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/juffed.html ... /usr/bin/c++ -DCSS3_FOUND -DHAVE_ENCA -DJUFF_FORTRAN_LEXER -DJUFF_PASCAL_LEXER -DJUFF_PROPERTIES_LEXER -DJUFF_TCL_LEXER -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_XML_LIB -Djuffed_engine_qsci_EXPORTS -I/build/1st/juffed-0.10-85-g5ba17f9/build/juffed-engine-qsci_autogen/include -I/build/1st/juffed-0.10-85-g5ba17f9/build -I/usr/include/x86_64-linux-gnu/qt5/Qsci -I/usr/include/x86_64-linux-gnu/qt5/Qsci/Qsci -I/build/1st/juffed-0.10-85-g5ba17f9/src/3rd_party/qtsingleapplication -I/build/1st/juffed-0.10-85-g5ba17f9/src/app/ui -I/build/1st/juffed-0.10-85-g5ba17f9/src/app/qsci -I/build/1st/juffed-0.10-85-g5ba17f9/./include -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -Wall -Wextra -O2 -g -DNDEBUG -fPIC -fPIC -std=gnu++11 -o CMakeFiles/juffed-engine-qsci.dir/juffed-engine-qsci_autogen/mocs_compilation.cpp.o -c /build/1st/juffed-0.10-85-g5ba17f9/build/juffed-engine-qsci_autogen/mocs_compilation.cpp In file included from /build/1st/juffed-0.10-85-g5ba17f9/build/juffed-engine-qsci_autogen/HJY3QJUKGU/moc_qscilexerada.cpp:9:0, from /build/1st/juffed-0.10-85-g5ba17f9/build/juffed-engine-qsci_autogen/mocs_compilation.cpp:2: /build/1st/juffed-0.10-85-g5ba17f9/build/juffed-engine-qsci_autogen/HJY3QJUKGU/../../../src/app/qsci/lexers/qscilexerada.h:7:19: error: expected identifier before numeric constant #define SCLEX_ADA 20 ^ /build/1st/juffed-0.10-85-g5ba17f9/build/juffed-engine-qsci_autogen/HJY3QJUKGU/../../../src/app/qsci/lexers/qscilexerada.h:7:19: error: expected ‘}’ before numeric constant /build/1st/juffed-0.10-85-g5ba17f9/build/juffed-engine-qsci_autogen/HJY3QJUKGU/../../../src/app/qsci/lexers/qscilexerada.h:7:19: error: expected unqualified-id before numeric constant In file included from /usr/include/x86_64-linux-gnu/qt5/Qsci/qscicommand.h:27:0, from /usr/include/x86_64-linux-gnu/qt5/Qsci/qsciscintilla.h:32, from /build/1st/juffed-0.10-85-g5ba17f9/build/juffed-engine-qsci_autogen/NUETKEGESQ/../../../src/app/qsci/JuffScintilla.h:26, from /build/1st/juffed-0.10-85-g5ba17f9/build/juffed-engine-qsci_autogen/NUETKEGESQ/moc_JuffScintilla.cpp:9, from /build/1st/juffed-0.10-85-g5ba17f9/build/juffed-engine-qsci_autogen/mocs_compilation.cpp:7: ...
Bug#897132: svnkit FTBFS with libsvn-java 1.10.0-1
Source: svnkit
Version: 1.8.14-1
Severity: serious
Tags: buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/svnkit.html
...
compile-library:
[mkdir] Created dir: /build/1st/svnkit-1.8.14/svnkit/bin
[mkdir] Created dir: /build/1st/svnkit-1.8.14/svnkit-cli/bin
[mkdir] Created dir: /build/1st/svnkit-1.8.14/svnkit-javahl16/bin
[javac] /build/1st/svnkit-1.8.14/debian/build.xml:20: warning:
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to
false for repeatable builds
[javac] Compiling 1074 source files to /build/1st/svnkit-1.8.14/svnkit/bin
[javac] Using ant.build.javac.target 1.5 is no longer supported, switching
to 1.7
[javac] Using ant.build.javac.target 1.5 is no longer supported, switching
to 1.7
[javac] Using ant.build.javac.source 1.5 is no longer supported, switching
to 1.7
[javac] warning: [options] bootstrap class path not set in conjunction with
-source 1.7
[javac]
/build/1st/svnkit-1.8.14/svnkit/src/main/java/org/tmatesoft/svn/core/internal/util/SVNPathUtil.java:58:
warning: non-varargs call of varargs method with inexact argument type for
last parameter;
[javac] SVNErrorMessage err =
SVNErrorMessage.create(SVNErrorCode.FS_PATH_SYNTAX, "Invalid control character
''{0}'' in path ''{1}''", new String[]{"0x" +
SVNFormatUtil.getHexNumberFromByte((byte) ch), path});
[javac]
^
[javac] cast to Object for a varargs call
[javac] cast to Object[] for a non-varargs call and to suppress this
warning
[javac]
/build/1st/svnkit-1.8.14/svnkit/src/main/java/org/tmatesoft/svn/core/wc/admin/SVNAdminClient.java:1622:
warning: non-varargs call of varargs method with inexact argument type for
last parameter;
[javac] SVNErrorMessage err =
SVNErrorMessage.create(SVNErrorCode.IO_ERROR, "Session is rooted at ''{0}'' but
the repos root is ''{1}''", new SVNURL[] {
[javac]
^
[javac] cast to Object for a varargs call
[javac] cast to Object[] for a non-varargs call and to suppress this
warning
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 3 warnings
[javac] /build/1st/svnkit-1.8.14/debian/build.xml:23: warning:
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to
false for repeatable builds
[javac] Compiling 124 source files to
/build/1st/svnkit-1.8.14/svnkit-cli/bin
[javac] Using ant.build.javac.target 1.5 is no longer supported, switching
to 1.7
[javac] Using ant.build.javac.target 1.5 is no longer supported, switching
to 1.7
[javac] Using ant.build.javac.source 1.5 is no longer supported, switching
to 1.7
[javac] warning: [options] bootstrap class path not set in conjunction with
-source 1.7
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 1 warning
[javac] /build/1st/svnkit-1.8.14/debian/build.xml:26: warning:
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to
false for repeatable builds
[javac] Compiling 38 source files to
/build/1st/svnkit-1.8.14/svnkit-javahl16/bin
[javac] Using ant.build.javac.target 1.5 is no longer supported, switching
to 1.7
[javac] Using ant.build.javac.target 1.5 is no longer supported, switching
to 1.7
[javac] Using ant.build.javac.source 1.5 is no longer supported, switching
to 1.7
[javac] warning: [options] bootstrap class path not set in conjunction with
-source 1.7
[javac]
/build/1st/svnkit-1.8.14/svnkit-javahl16/src/main/java/org/apache/subversion/javahl/SVNClient.java:14:
error: SVNClient is not abstract and does not override abstract method
logMessages(String,Revision,List,boolean,boolean,boolean,Set,boolean,long,LogMessageCallback)
in ISVNClient
[javac] public class SVNClient implements ISVNClient {
[javac]^
[javac]
/build/1st/svnkit-1.8.14/svnkit-javahl16/src/main/java/org/tmatesoft/svn/core/javahl17/SVNClientImpl.java:38:
error: SVNClientImpl is not abstract and does not override abstract method
logMessages(String,Revision,List,boolean,boolean,boolean,Set,boolean,long,LogMessageCallback)
in ISVNClient
[javac] public class SVNClientImpl implements ISVNClient {
[javac]^
[javac]
/build/1st/svnkit-1.8.14/s
Bug#896598: [Debian-med-packaging] Bug#896598: libglademm2.4: Intent to Adopt
On Sun, Apr 22, 2018 at 11:10:35PM +0200, Gert Wollny wrote: > Hi Adrian, Hi Gert, > while I generally agree that dropping all the gnome2 related libraries > from Debian is not a good idea, in this case, where aeskulap is the > only reverse dependency I'm aware of, There are some others like ll-scope. Nothing extremely important, but still slightly popular. > I wonder whether is is really a > good idea to put effort into providing this library package? Th effort consists in practice of one upload, perhaps a second one if something happens. > Best, > Gert cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: forcibly merging 884616 896264
Processing commands for cont...@bugs.debian.org: > forcemerge 884616 896264 Bug #884616 [python-visual] exception "ValueError: The truth value..." on import Bug #896264 [python-visual] python-visual: visual fails to import Severity set to 'grave' from 'serious' Added tag(s) buster and sid. Merged 884616 896264 > thanks Stopping processing here. Please contact me if you need assistance. -- 884616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884616 896264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897124: crystalhd cannot be rebuilt from source: autoreconf fails in filters/gst/gst-plugin
Control: severity -1 normal On Sat, Apr 28, 2018 at 07:14:04PM +0200, Helmut Grohne wrote: > Source: crystalhd > Version: 1:0.0~git20110715.fdd2f19-12 > Severity: serious > User: helm...@debian.org > Usertags: rebootstrap > > I was trying to fix a cross compilation issue in crystalhd and noticed > that filters/gst/gst-plugin/src/Makefile.in would not be regenerated > from the corresponding Makefile.am. Unfortunately, the bug is right > there and I cannot fix it, because Makefile.in cannot be rebuilt. > Trying to autoreconf filters/gst/gst-plugin results in: > > libtoolize: putting auxiliary files in '.'. > libtoolize: copying file './ltmain.sh' > libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac, > libtoolize: and rerunning libtoolize and aclocal. >... > Thus I conclude that crystalhd cannot be built from source (DFSG #3). > Alternatively, autoreconfing involves a more complex invocation, the > build instructions are missing (DFSG #2). Works for me when following the clear instructions from the error message. > Helmut cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: Re: Bug#897124: crystalhd cannot be rebuilt from source: autoreconf fails in filters/gst/gst-plugin
Processing control commands: > severity -1 normal Bug #897124 [src:crystalhd] crystalhd cannot be rebuilt from source: autoreconf fails in filters/gst/gst-plugin Severity set to 'normal' from 'serious' -- 897124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897127: psensor FTBFS on i386/armhf: FAIL: test-cppcheck.sh
Source: psensor Version: 1.1.5-1 Severity: serious Tags: buster sid Some recent change in unstable makes psensor FTBFS on i386/armhf: https://tests.reproducible-builds.org/debian/history/psensor.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/psensor.html ... FAIL: test-cppcheck.sh == *** stack smashing detected ***: terminated Aborted FAIL test-cppcheck.sh (exit status: 1) Testsuite summary for psensor 1.1.5 # TOTAL: 6 # PASS: 5 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See tests/test-suite.log Please report to jea...@gmail.com Makefile:754: recipe for target 'test-suite.log' failed make[4]: *** [test-suite.log] Error 1
Processed: severity of 865952 is grave
Processing commands for cont...@bugs.debian.org: > severity 865952 grave Bug #865952 [cl-fiveam] cl-fiveam: Fails to load the ASDF system Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 865952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897059: [Pkg-phototools-devel] Bug#897059: (no subject)
forwarded 897059 https://github.com/gphoto/libgphoto2/issues/265 thanks Em 28-04-2018 11:10, Matti Hämäläinen escreveu: > > Hello, > > Submitted a report to libgphoto2 Github issue tracker: > https://github.com/gphoto/libgphoto2/issues/265 >
Processed: Re: [Pkg-phototools-devel] Bug#897059: (no subject)
Processing commands for cont...@bugs.debian.org: > forwarded 897059 https://github.com/gphoto/libgphoto2/issues/265 Bug #897059 [libgphoto2-6] libgphoto2-6: libgphoto2 causes corrupted image file transfers Set Bug forwarded-to-address to 'https://github.com/gphoto/libgphoto2/issues/265'. > thanks Stopping processing here. Please contact me if you need assistance. -- 897059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897059 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#895332: marked as done (flightgear: no flightgear package present in Buster repo)
On 20 Apr 2018, at 20:07, Jaap Keuter wrote: > > On Tue, 10 Apr 2018 15:10:37 +0200 Markus Wanner wrote: > ... >> >> Given there's not FTBFS for the build failure on arm, I suggest we >> relabel this one. >> >> Kind Regards >> >> Markus >> > > Hi, > > It would be nice if this could be addressed by submitting newly released > 2018.1.1 to the (arm*) builders and see what they come up with. > Unfortunately the newly added file QQuickDrawable.cxx and QQuickDrawable.hxx still give trouble. Maybe the library dependancies need to be reviewed? Thanks, Jaap
Processed: fixed 878267 in 1.2.12-5+deb8u1, fixed 878267 in 1.2.12-5+deb9u1
Processing commands for cont...@bugs.debian.org:
> fixed 878267 1.2.12-5+deb8u1
Bug #878267 {Done: Felix Geyer } [src:sdl-image1.2]
sdl-image1.2: CVE-2017-2887: Incorrect XCF property handling
The source 'sdl-image1.2' and version '1.2.12-5+deb8u1' do not appear to match
any binary packages
Marked as fixed in versions sdl-image1.2/1.2.12-5+deb8u1.
> # upcoming DSA
> fixed 878267 1.2.12-5+deb9u1
Bug #878267 {Done: Felix Geyer } [src:sdl-image1.2]
sdl-image1.2: CVE-2017-2887: Incorrect XCF property handling
The source 'sdl-image1.2' and version '1.2.12-5+deb9u1' do not appear to match
any binary packages
Marked as fixed in versions sdl-image1.2/1.2.12-5+deb9u1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
878267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878267
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#897124: crystalhd cannot be rebuilt from source: autoreconf fails in filters/gst/gst-plugin
Source: crystalhd Version: 1:0.0~git20110715.fdd2f19-12 Severity: serious User: helm...@debian.org Usertags: rebootstrap I was trying to fix a cross compilation issue in crystalhd and noticed that filters/gst/gst-plugin/src/Makefile.in would not be regenerated from the corresponding Makefile.am. Unfortunately, the bug is right there and I cannot fix it, because Makefile.in cannot be rebuilt. Trying to autoreconf filters/gst/gst-plugin results in: libtoolize: putting auxiliary files in '.'. libtoolize: copying file './ltmain.sh' libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac, libtoolize: and rerunning libtoolize and aclocal. libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am. configure.ac:14: error: possibly undefined macro: AS_VERSION If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:35: error: possibly undefined macro: AS_COMPILER_FLAG autoreconf: /usr/bin/autoconf failed with exit status: 1 Thus I conclude that crystalhd cannot be built from source (DFSG #3). Alternatively, autoreconfing involves a more complex invocation, the build instructions are missing (DFSG #2). Helmut
Bug#894642: gst-plugins-espeak: diff for NMU version 0.4.0-3.1
Control: tags 894642 + patch Control: tags 894642 + pending Dear maintainer, I've prepared an NMU for gst-plugins-espeak (versioned as 0.4.0-3.1) and uploaded it to DELAYED/8. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed diff -Nru gst-plugins-espeak-0.4.0/debian/changelog gst-plugins-espeak-0.4.0/debian/changelog --- gst-plugins-espeak-0.4.0/debian/changelog 2017-10-05 09:57:39.0 +0300 +++ gst-plugins-espeak-0.4.0/debian/changelog 2018-04-28 20:07:37.0 +0300 @@ -1,3 +1,10 @@ +gst-plugins-espeak (0.4.0-3.1) unstable; urgency=low + + * Non-maintainer upload. + * Fix FTBFS with GStreamer 1.14. (Closes: #894642) + + -- Adrian Bunk Sat, 28 Apr 2018 20:07:37 +0300 + gst-plugins-espeak (0.4.0-3) unstable; urgency=medium * Add patch 1001 to set "english" (not "default") as default voice, to diff -Nru gst-plugins-espeak-0.4.0/debian/patches/1002_gstreamer_1_14.patch gst-plugins-espeak-0.4.0/debian/patches/1002_gstreamer_1_14.patch --- gst-plugins-espeak-0.4.0/debian/patches/1002_gstreamer_1_14.patch 1970-01-01 02:00:00.0 +0200 +++ gst-plugins-espeak-0.4.0/debian/patches/1002_gstreamer_1_14.patch 2018-04-28 20:07:31.0 +0300 @@ -0,0 +1,16 @@ +Description: Stop using -export-symbols-regex + The old regex is no longer correct for GStreamer 1.14. +Author: Adrian Bunk +Bug-Debian: https://bugs.debian.org/894642 + +--- gst-plugins-espeak-0.4.0.orig/configure.ac gst-plugins-espeak-0.4.0/configure.ac +@@ -42,7 +42,7 @@ GST_ALL_LDFLAGS="-no-undefined" + AC_SUBST(GST_ALL_LDFLAGS) + + dnl set proper LDFLAGS for plugins +-GST_PLUGIN_LDFLAGS="-module -avoid-version -export-symbols-regex '^_*gst_plugin_desc\$\$' $GST_ALL_LDFLAGS" ++GST_PLUGIN_LDFLAGS="-module -avoid-version $GST_ALL_LDFLAGS" + AC_SUBST(GST_PLUGIN_LDFLAGS) + + AC_OUTPUT(Makefile m4/Makefile src/Makefile) diff -Nru gst-plugins-espeak-0.4.0/debian/patches/series gst-plugins-espeak-0.4.0/debian/patches/series --- gst-plugins-espeak-0.4.0/debian/patches/series 2017-10-05 09:40:02.0 +0300 +++ gst-plugins-espeak-0.4.0/debian/patches/series 2018-04-28 20:05:48.0 +0300 @@ -1 +1,2 @@ 1001_set_english_as_default.patch +1002_gstreamer_1_14.patch
Processed: gst-plugins-espeak: diff for NMU version 0.4.0-3.1
Processing control commands: > tags 894642 + patch Bug #894642 [src:gst-plugins-espeak] gst-plugins-espeak FTBFS with GStreamer 1.14 Added tag(s) patch. > tags 894642 + pending Bug #894642 [src:gst-plugins-espeak] gst-plugins-espeak FTBFS with GStreamer 1.14 Added tag(s) pending. -- 894642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#896499: marked as done (libopenscap-perl: Can't locate loadable object for module openscap_pm)
Your message dated Sat, 28 Apr 2018 17:08:11 + with message-id and subject line Bug#896499: fixed in openscap 1.2.16-1 has caused the Debian Bug report #896499, regarding libopenscap-perl: Can't locate loadable object for module openscap_pm 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.) -- 896499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libopenscap-perl Version: 1.2.15-1 Severity: grave Justification: renders package unusable User: debian-p...@lists.debian.org Usertags: use-failure The Perl module in this package seems to be unusable: # perl -e 'use openscap' Can't locate loadable object for module openscap_pm in @INC (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/openscap.pm line 11. Compilation failed in require at -e line 1. BEGIN failed--compilation aborted at -e line 1. -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Source: openscap Source-Version: 1.2.16-1 We believe that the bug you reported is fixed in the latest version of openscap, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 896...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pierre Chifflier (supplier of updated openscap 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: Sat, 28 Apr 2018 18:33:35 +0200 Source: openscap Binary: libopenscap-dev libopenscap8 python-openscap libopenscap-perl libopenscap8-dbg Architecture: source amd64 Version: 1.2.16-1 Distribution: unstable Urgency: medium Maintainer: Pierre Chifflier Changed-By: Pierre Chifflier Description: libopenscap-dev - Set of libraries enabling integration of the SCAP line of standar libopenscap-perl - Set of libraries enabling integration of the SCAP line of standar libopenscap8 - Set of libraries enabling integration of the SCAP line of standar libopenscap8-dbg - Set of libraries enabling integration of the SCAP line of standar python-openscap - Set of libraries enabling integration of the SCAP line of standar Closes: 896499 Changes: openscap (1.2.16-1) unstable; urgency=medium . * New upstream version 1.2.16 * Refreshed quilt patches * Rename install perl so file (Closes: #896499) * Change priority from extra to optional Checksums-Sha1: 20b285078fc6bafbd445634cb1d0e90690febc81 2040 openscap_1.2.16-1.dsc 459a56d3b6b3b70fbce15751d37665f6b68caeaf 12489871 openscap_1.2.16.orig.tar.gz c2caf8e2246b01a8f167be1037519cc6e1ef0d55 69840 openscap_1.2.16-1.debian.tar.xz bfbb4e20f7c5cbc3784b80e06ac82490c164e7ca 162816 libopenscap-dev_1.2.16-1_amd64.deb 962137ed1c7d3537dd2d1ec83d3f29eeb36f66e0 332368 libopenscap-perl_1.2.16-1_amd64.deb b6b4cfee045d3fb569c5b008a86ea2620231b43c 5937628 libopenscap8-dbg_1.2.16-1_amd64.deb aef7c0f1478b55ff385286a5ceb02d2ba7ee424b 2472200 libopenscap8_1.2.16-1_amd64.deb 2f9f555a497694c7579c47a05d0cf0aab2f4282a 10187 openscap_1.2.16-1_amd64.buildinfo 3bbf78ef98767c02c89e155f4c151868b0d3ebde 237256 python-openscap_1.2.16-1_amd64.deb Checksums-Sha256: 4bd4470bf7b45467b4f0b1a1b2c1d7dc11f2c67480a73789203881c5d1bd64f2 2040 openscap_1.2.16-1.dsc 7cc7853faddaa54fea69f642ace6ba561920ca3fd9199ae8f5c322e1281b18fb 12489871 openscap_1.2.16.orig.tar.gz fbbf8f476c4e897ee85b117c2698a13a118461e6aeded1fc341f5ccb19961e07 69840 openscap_1.2.16-1.debian.tar.xz e4e07bc76078b70c792b2c279f07790a976a09718598c799581242190436e93d 162816 libopenscap-dev_1.2.16-1_amd64.deb b0b87e982a193901457a9bf85099f9ea74c1ddaecc0b2b7fbf8e9e15926b080c 332368 libopenscap-perl_1.2.16-1_amd64.deb fbdb015e12a440467942dcfc8ffe36cd4fff109fc20f316dfa3526fd60878e3b 5937628 libopenscap8-dbg_1.2.16-1_amd64.deb 549057f89fb45616c86c8c5ef8df12f6d2e81f8ce37d40bed10edfd209a6ac0f 2472200 libopenscap8_1.2.16-1_amd64.deb c225bba31c23cc11e03493f5331905b5568a6d01c69090727a0e094e45e07bab 10187 openscap
Processed: fixed 884672 in 4.2.2-1
Processing commands for cont...@bugs.debian.org:
> fixed 884672 4.2.2-1
Bug #884672 {Done: Andreas Tille } [src:rdflib] 2to3 binary
moved to the 2to3 package
Marked as fixed in versions rdflib/4.2.2-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
884672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#897059: Your mail
reopen 897059 thanks On Sat, 28 Apr 2018 17:10:35 +0300 (EEST) =?ISO-8859-15?Q?Matti_H=E4m=E4l=E4inen?= wrote: > > Hello, > > Submitted a report to libgphoto2 Github issue tracker: > https://github.com/gphoto/libgphoto2/issues/265 Ok. I will set forwarded. Regards, Herbert
Processed: Re: Your mail
Processing commands for cont...@bugs.debian.org:
> reopen 897059
Bug #897059 {Done: Herbert Parentes Fortes Neto }
[libgphoto2-6] libgphoto2-6: libgphoto2 causes corrupted image file transfers
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions gphoto2/2.5.17-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
897059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#897112: marked as done (psi FTBFS with Qt 5.10)
Your message dated Sat, 28 Apr 2018 16:51:46 + with message-id and subject line Bug#897112: fixed in psi 1.3-4 has caused the Debian Bug report #897112, regarding psi FTBFS with Qt 5.10 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.) -- 897112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: psi Version: 1.3-3 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/psi.html ... debian/rules build dh build --parallel dh_update_autotools_config -O--parallel debian/rules override_dh_auto_configure make[1]: Entering directory '/build/1st/psi-1.3' #qt-qconf ls -al total 228 drwxr-xr-x 20 pbuilder1 pbuilder1 840 May 20 05:05 . drwxr-xr-x 3 pbuilder1 pbuilder1 120 May 20 05:05 .. -rw-r--r-- 1 pbuilder1 pbuilder1 1048 Jul 19 2017 .gitignore -rw-r--r-- 1 pbuilder1 pbuilder1 371 Aug 18 2017 .gitmodules drwxr-xr-x 3 pbuilder1 pbuilder1 140 May 20 05:05 .pc -rw-r--r-- 1 pbuilder1 pbuilder196 May 25 2015 .qmake.cache.in -rw-r--r-- 1 pbuilder1 pbuilder189 Nov 28 2014 .qmake.conf drwxr-xr-x 4 pbuilder1 pbuilder1 120 May 28 2017 3rdparty -rw-r--r-- 1 pbuilder1 pbuilder1 11255 Sep 23 2017 CMakeLists.txt -rw-r--r-- 1 pbuilder1 pbuilder1 15862 Jan 20 2013 COPYING -rw-r--r-- 1 pbuilder1 pbuilder1 1226 Jan 20 2013 INSTALL -rw-r--r-- 1 pbuilder1 pbuilder1 6364 Sep 23 2017 README -rw-r--r-- 1 pbuilder1 pbuilder1 7909 Sep 23 2017 Readme-cmake-ru.txt -rw-r--r-- 1 pbuilder1 pbuilder1 4411 Sep 23 2017 Readme-cmake.txt -rw-r--r-- 1 pbuilder1 pbuilder1 8120 May 23 2017 TODO drwxr-xr-x 3 pbuilder1 pbuilder1 240 Sep 23 2017 admin drwxr-xr-x 2 pbuilder1 pbuilder1 100 Jan 20 2013 certs -rw-r--r-- 1 pbuilder1 pbuilder1 4142 May 23 2017 client_icons.txt drwxr-xr-x 3 pbuilder1 pbuilder160 May 28 2017 cmake -rwxr-xr-x 1 pbuilder1 pbuilder1 83709 May 20 05:05 configure drwxr-xr-x 4 pbuilder1 pbuilder1 380 May 20 05:06 debian drwxr-xr-x 2 pbuilder1 pbuilder1 220 Jul 25 2017 doc drwxr-xr-x 9 pbuilder1 pbuilder1 180 Jul 25 2017 iconsets -rw-r--r-- 1 pbuilder1 pbuilder1 23664 May 23 2017 iconsets.qrc drwxr-xr-x 7 pbuilder1 pbuilder1 480 May 20 05:05 iris -rw-r--r-- 1 pbuilder1 pbuilder1 281 Jan 20 2013 l10n.pro drwxr-xr-x 2 pbuilder1 pbuilder1 120 May 28 2017 mac drwxr-xr-x 2 pbuilder1 pbuilder1 120 Sep 23 2017 options -rw-r--r-- 1 pbuilder1 pbuilder188 Jul 19 2017 pluginsconf.pri.in -rw-r--r-- 1 pbuilder1 pbuilder1 1770 May 23 2017 psi.appdata.xml -rw-r--r-- 1 pbuilder1 pbuilder1 2189 Feb 21 2016 psi.desktop -rw-r--r-- 1 pbuilder1 pbuilder1 1049 Jul 25 2017 psi.pro -rw-r--r-- 1 pbuilder1 pbuilder1 1001 Jun 17 2017 psi.qc -rw-r--r-- 1 pbuilder1 pbuilder1 256 Jan 20 2013 psi.qrc drwxr-xr-x 6 pbuilder1 pbuilder1 120 Jul 25 2017 qa drwxr-xr-x 2 pbuilder1 pbuilder1 620 May 20 05:05 qcm drwxr-xr-x 2 pbuilder1 pbuilder1 180 Jan 20 2013 sound drwxr-xr-x 21 pbuilder1 pbuilder1 9100 May 20 05:05 src drwxr-xr-x 3 pbuilder1 pbuilder160 Jul 25 2017 themes drwxr-xr-x 2 pbuilder1 pbuilder160 Jan 20 2013 tools -rw-r--r-- 1 pbuilder1 pbuilder1 4 Sep 23 2017 version drwxr-xr-x 2 pbuilder1 pbuilder1 160 Sep 23 2017 win32 QT_SELECT=5 ./configure --prefix=/usr --no-separate-debug-info # --enable-debug Configuring Psi ... Verifying Qt build environment ... fail Reason: Unable to find the 'qmake' tool for Qt 5. Be sure you have a proper Qt 4.0+ build environment set up. This means not just Qt, but also a C++ compiler, a make tool, and any other packages necessary for compiling C++ programs. If you are certain everything is installed, then it could be that Qt is not being recognized or that a different version of Qt is being detected by mistake (for example, this could happen if $QTDIR is pointing to a Qt 3 installation). At least one of the following conditions must be satisfied: 1) --qtdir is set to the location of Qt 2) $QTDIR is set to the location of Qt 3) QtCore is in the pkg-config database 4) qmake is in the $PATH This script will use the first one it finds to be true, checked in the above order. #3 and #4 are the recommended options. #1 and #2 are mainly for overriding the system configuration. make[1]: *** [debian/rules:15: override_dh_auto_configure] Error 1 --- End Message --- --- Begin Message --- Source: psi Source-Version: 1.3-4 We believe that the bug you reported is fixed in the latest version of psi, which is due to be installed in the Debian FTP archive. A summar
Bug#884672: marked as done (2to3 binary moved to the 2to3 package)
Your message dated Sat, 28 Apr 2018 18:51:46 +0200 with message-id <20180428165146.tgnwd44n6trlx...@an3as.eu> and subject line Rdflib migrated to Salsa - bug fixed when building for upload has caused the Debian Bug report #884672, regarding 2to3 binary moved to the 2to3 package 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.) -- 884672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:rdflib Severity: serious Tags: sid buster The 2to3 binary is now built using Python3, and therefore had to move out of the python (2) package. It's now provided in it's own 2to3 package. Please add a build dependency on 2to3, and check if the autopkg test dependencies need an update as well. --- End Message --- --- Begin Message --- Hi, when I did the move to Salsa I realised the build issue described in #884672. Thus fixed it but forgot to close the bug which is done now manually. Kind regards Andreas. -- http://fam-tille.de--- End Message ---
Bug#897113: marked as done (ktorrent FTBFS with cmake 3.11.1)
Your message dated Sat, 28 Apr 2018 16:35:38 + with message-id and subject line Bug#897113: fixed in ktorrent 5.1.0-3 has caused the Debian Bug report #897113, regarding ktorrent FTBFS with cmake 3.11.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 897113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897113 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ktorrent Version: 5.1.0-2 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ktorrent.html ... cd /build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/ktorrent && /usr/bin/c++ -DKCOREADDONS_LIB -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_CAST_TO_ASCII -DQT_NO_CAST_TO_BYTEARRAY -DQT_NO_DEBUG -DQT_NO_URL_CAST_FROM_STRING -DQT_STRICT_ITERATORS -DQT_USE_FAST_OPERATOR_PLUS -DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB -DQT_XML_LIB -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I/build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/ktorrent -I/build/1st/ktorrent-5.1.0/ktorrent -I/build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/ktorrent/ktorrent_app_autogen/include -I/build/1st/ktorrent-5.1.0/libktcore -I/build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/libktcore -I/build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu -isystem /usr/include/KF5/KConfigCore -isystem /usr/include/KF5 -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem /usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KI18n -isystem /usr/include/KF5/KCMUtils -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KCodecs -isystem /usr/include/KF5/KWidgetsAddons -isystem /usr/include/KF5/KConfigGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem /usr/include/KF5/KAuth -isystem /usr/include/KF5/KService -isystem /usr/include/KF5/KParts -isystem /usr/include/KF5/KIOWidgets -isystem /usr/include/KF5/KIOCore -isystem /usr/include/KF5/KJobWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/KF5/KCompletion -isystem /usr/include/KF5/KXmlGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem /usr/include/KF5/KTextWidgets -isystem /usr/include/KF5/SonnetUi -isystem /usr/include/KF5/Solid -isystem /usr/include/KF5/libktorrent -isystem /usr/include/KF5/KArchive -isystem /usr/include/KF5/KCrash -isystem /usr/include/x86_64-linux-gnu -isystem /usr/include/KF5/KDBusAddons -isystem /usr/include/KF5/KIconThemes -isystem /usr/include/KF5/KIOFileWidgets -isystem /usr/include/KF5/KBookmarks -isystem /usr/include/KF5/KItemViews -isystem /usr/include/KF5/KNotifications -isystem /usr/include/KF5/KNotifyConfig -isystem /usr/include/KF5/KWindowSystem -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x -fno-operator-names -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Wvla -Wdate-time -fexceptions -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -std=gnu++11 -o CMakeFiles/ktorrent_app.dir/ktorrent_app_autogen/mocs_compilation.cpp.o -c /build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/ktorrent/ktorrent_app_autogen/mocs_compilation.cpp In file included from /build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/ktorrent/ktorrent_app_autogen/2NRMJ5X7RK/moc_torrentcreatordlg.cpp:9:0, from /build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/ktorrent/ktorrent_app_autogen/mocs_compilation.cpp:10: /build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/ktorrent/ktorrent_app_autogen/2NRMJ5X7RK/../../../../ktorrent/dialogs/torrentcreatordlg.h:86:16: error: field 'update_timer' has incomplete type 'QTimer' QTimer update_timer; ^~~~ In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:44:0, from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qdialog.h:44, from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QDialog:1, from /build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/ktorrent/ktorrent_app_autogen/2NRMJ5X7RK/../../../../ktorrent/dialogs/addpeersdlg.h:25, from /build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/ktorrent/ktorrent_app_autogen/2NRMJ5X7RK/moc_addpeersdlg.cpp:9, from /build/1st/ktorrent-5.1.0/obj-x86_64-
Bug#890926: marked as done (go-dep FTBFS with golang-1.10-go: go: cannot find GOROOT directory: /usr/lib/go-1.8)
Your message dated Sat, 28 Apr 2018 16:35:25 + with message-id and subject line Bug#890926: fixed in go-dep 0.3.2-3 has caused the Debian Bug report #890926, regarding go-dep FTBFS with golang-1.10-go: go: cannot find GOROOT directory: /usr/lib/go-1.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 890926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890926 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: go-dep Version: 0.3.2-2 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/go-dep.html ... debian/rules override_dh_auto_build make[1]: Entering directory '/build/1st/go-dep-0.3.2' go: cannot find GOROOT directory: /usr/lib/go-1.8 *** Cannot use default go. Forcing go-1.8. GOPATH=/build/1st/go-dep-0.3.2/obj-x86_64-linux-gnu go generate github.com/golang/dep go: cannot find GOROOT directory: /usr/lib/go-1.8 make[1]: *** [debian/rules:23: override_dh_auto_build] Error 2 --- End Message --- --- Begin Message --- Source: go-dep Source-Version: 0.3.2-3 We believe that the bug you reported is fixed in the latest version of go-dep, 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 890...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated go-dep 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: Sat, 28 Apr 2018 18:10:37 +0200 Source: go-dep Binary: go-dep Architecture: source Version: 0.3.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Hilko Bengen Description: go-dep - Go dependency management tool Closes: 890926 Changes: go-dep (0.3.2-3) unstable; urgency=medium . [ Alexandre Viau ] * Point Vcs-* urls to salsa.debian.org. . [ Hilko Bengen ] * Fix Go version detection recognize two-part version numbers such as 1.10 (Closes: #890926) * Bump Standards-Version Checksums-Sha1: 643cdc30e85b6acb1f5a7d17d745e27d7e7ee7ed 2070 go-dep_0.3.2-3.dsc 0a2cd081482e2c083f5cf81b48af78a383f82ad5 4364 go-dep_0.3.2-3.debian.tar.xz 555acb3eaa691256cbd87e3611eb1a272ed3af33 5883 go-dep_0.3.2-3_source.buildinfo Checksums-Sha256: 22913a82dd01bb7c475c4a3911691ec0d9d002e4f9541f356386af0b5e73c7e9 2070 go-dep_0.3.2-3.dsc 8237a257a1aeb18f6cd38d1c66c2b20e712b879d8604bd3de7cd7363c050ccaf 4364 go-dep_0.3.2-3.debian.tar.xz 3bf255e4f8931800bee4814c26e490aa6875161175a0f06c24a3daf7f9ed960b 5883 go-dep_0.3.2-3_source.buildinfo Files: 5617d846c90f9a8dfb75877d735aaf66 2070 devel optional go-dep_0.3.2-3.dsc 97e5c4f679a61a509f6b9d654f5b 4364 devel optional go-dep_0.3.2-3.debian.tar.xz 4f6757c9df82651391c1fa2e32d30566 5883 devel optional go-dep_0.3.2-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAlrknbUSHGJlbmdlbkBk ZWJpYW4ub3JnAAoJEHW3EGNcITp+XyAQALwle02kyi9AamQSTZxHOBopLqG5HmwP XjuZYZYbsm4rFX3SZ3aS6VVl8tzPnjLTWS7qteO5XSH4ZVoGR6oehznGIbxdDIlT 7HHskvRM45GCIBindIzMtFysWkB0jLsTvTjpQhOCDLZ4rH01huBor7mNBoD+kZ8P QwQoy1fSm4NAYTUzYahpxkixfBPsy5QDep2CWpUcDGZBNBTyNC1VnsC8ZqovbCeQ kX36RFp2HphxGjYXCq4IfVljMCUHjFNBF8qp+ljBOezWSEuHh89u+hkIvapF95uV 9Hmvt1Jw9uKRKtSqNf2g7kZ9BRsf7AZM6m5RvjAJd45s60lnOjiGjPAJI/EXcgHV ih9UN6rrDRJnT1g470RsF4wk3ulVqY6yZ1A/HV/k25pamlc/ZeVZ0E0NCns+jIgl GC9CGJjHY/uyigfat+XjSYibLHwsrRCFl/R4qMN2MbAgg8eV2ysBSUanXm1bfYxv GZG7BJNF2pag+mXXXDmDm+GruPxZJw2cVTrWJibZd8QepoieSOSDY0aH4+BJOimG OJ/6y29STVwAFDsjlOhxTnENH7WuvOgTDnblJgF9ed4jLjg8/JgA+26Kcy3ajJyP 0wbjHQpxBalg4SnrrhFx4IH6do8ZOFQOPqNSaalmBs8Qvg1/OeUeFdLQ8N82zePw zci7m1gK21mq =tQo1 -END PGP SIGNATURE End Message ---
Bug#897118: marked as done (telepathy-qt FTBFS with Qt 5.10: symbol disappeared)
Your message dated Sat, 28 Apr 2018 16:21:56 + with message-id and subject line Bug#897118: fixed in telepathy-qt 0.9.7-5 has caused the Debian Bug report #897118, regarding telepathy-qt FTBFS with Qt 5.10: symbol disappeared 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.) -- 897118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: telepathy-qt Version: 0.9.7-4 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/telepathy-qt.html ... dh_makeshlibs dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libtelepathy-qt5-0/DEBIAN/symbols doesn't match completely debian/libtelepathy-qt5-0.symbols --- debian/libtelepathy-qt5-0.symbols (libtelepathy-qt5-0_0.9.7-4_amd64) +++ dpkg-gensymbolsU6d42g 2019-05-31 09:26:20.782865888 -1200 @@ -1,5 +1,5 @@ libtelepathy-qt5.so.0 libtelepathy-qt5-0 #MINVER# - (optinal=inline)_ZN10QByteArray7reserveEi@Base 0.9.7 +#MISSING: 0.9.7-4# (optinal=inline)_ZN10QByteArray7reserveEi@Base 0.9.7 _ZN2Tp10AccountSet11qt_metacallEN11QMetaObject4CallEiPPv@Base 0.9.5 _ZN2Tp10AccountSet11qt_metacastEPKc@Base 0.9.5 _ZN2Tp10AccountSet12accountAddedERKNS_9SharedPtrINS_7AccountEEE@Base 0.9.5 dh_makeshlibs: failing due to earlier errors make: *** [debian/rules:13: binary] Error 2 --- End Message --- --- Begin Message --- Source: telepathy-qt Source-Version: 0.9.7-5 We believe that the bug you reported is fixed in the latest version of telepathy-qt, 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 897...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated telepathy-qt 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: Sat, 28 Apr 2018 17:44:10 +0200 Source: telepathy-qt Binary: libtelepathy-qt5-0 libtelepathy-qt5-farstream0 libtelepathy-qt5-dev Architecture: source Version: 0.9.7-5 Distribution: unstable Urgency: medium Maintainer: Debian KDE Extras Team Changed-By: Pino Toscano Description: libtelepathy-qt5-0 - Telepathy framework - Qt 5 library libtelepathy-qt5-dev - Qt 5 Telepathy library (headers and static library) libtelepathy-qt5-farstream0 - Telepathy/Farsight integration - Qt 5 library Closes: 897118 Changes: telepathy-qt (0.9.7-5) unstable; urgency=medium . * Team upload. * Update symbols file. (Closes: #897118) * Bump Standards-Version to 4.1.4, no changes required. Checksums-Sha1: 367dec646e4f2ce07ca899fff1db597dc9a9fa46 2549 telepathy-qt_0.9.7-5.dsc 30f2c192b0319ed3efc66224ea9f50fefe7ecc59 35712 telepathy-qt_0.9.7-5.debian.tar.xz fb8edd13e2b0421f03b755387d5abaf09aef7c10 12345 telepathy-qt_0.9.7-5_source.buildinfo Checksums-Sha256: 4223b6db7ed49a45963096b9483c66f1ae40be7c14731cdad7be313d452b5d01 2549 telepathy-qt_0.9.7-5.dsc 9e028c465fdb17ecef1b7d9338e95bff3cf73c2f67e888a460095fd34032ec45 35712 telepathy-qt_0.9.7-5.debian.tar.xz bca26951a3b5adbbbf322fb01f7498067bbb98c6c84d6c0ea2889ea69e51f801 12345 telepathy-qt_0.9.7-5_source.buildinfo Files: c97e0876b25d461860727bcdfdc60dc8 2549 libs optional telepathy-qt_0.9.7-5.dsc 0b5d6544428cdaa611722833b913b1fe 35712 libs optional telepathy-qt_0.9.7-5.debian.tar.xz 9154645f64835011b46020f72d28925c 12345 libs optional telepathy-qt_0.9.7-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAlrkl04ACgkQLRkciEOx P01W/BAAmB5brABNttcsjYnrAeCF8FNknLmY3u2rfHpIe8rDaYtGFkoagLPeq2VH 7xZE/qcS9BTAHHwweSnPJkPHrMc26pr95hYDMLTw6An+mJVAqbg58h1+tcXazd3y JLEN2MMe2FRXR8ryuzs/QafxqsOpzwTMLTXbZlSqXlrpbg4Dv3tuCtKjOMfC5R/L HDwmIgopfyEwjr6X0RxOznusH6DWZV0DsuoROCrztf/jEcy3yG+55lcUtdfLB0fW 0vXa7Bq/PqgapHOG4IAePbt55OjiEoZxVlFUUdzTFov5raPdlRxyrF6lxoAOVTfW Xzcnorlk3QRZobIkDsX5BM0L7UsxGm6VMo1ei4G1jW0hi+t3GOJqEIG5JBmmMpBl /tkc3q2cRXr48fwQozBYBMaL65tdkUNB+W94Xt7JoixzNhO8wH8I0JqWvanhtihH iQ5yaRNsPyJD5k4a8x9y65yuKArdLcJkcPhVpH4r1L1wuf/TzTClRjxrl0LDiVTD Mc8hegxDJqxbvUmOb+yfRz1Han9WmzSbgCxcOQg35MsAyeD0i86Fk/8cs4vVLLcO U/bKllT/DL9ORCaNsNMUxTLWkJXaEKKsYDRBW6hnZU6p4nmn3osmW
Processed: severity of 884488 is important
Processing commands for cont...@bugs.debian.org: > severity 884488 important Bug #884488 [ktorrent] [ktorrent] Freezes at start Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 884488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug #890926 in dep marked as pending
Processing control commands: > tag -1 pending Bug #890926 [src:go-dep] go-dep FTBFS with golang-1.10-go: go: cannot find GOROOT directory: /usr/lib/go-1.8 Added tag(s) pending. -- 890926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890926 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#890926: Bug #890926 in dep marked as pending
Control: tag -1 pending Hello, Bug #890926 in dep 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/go-team/packages/dep/commit/e575ddd298fdd53827dcb3c0d1b75a35741f5892 Fix Go version detection recognize two-part version numbers such as 1.10 (Closes: #890926) (this message was generated automatically) -- Greetings https://bugs.debian.org/890926
Bug#897101: marked as done (flann FTBFS with cmake 3.11.1)
Your message dated Sat, 28 Apr 2018 16:05:12 + with message-id and subject line Bug#897101: fixed in flann 1.9.1+dfsg-3 has caused the Debian Bug report #897101, regarding flann FTBFS with cmake 3.11.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 897101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flann Version: 1.9.1+dfsg-2 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/flann.html ... -- Configuring done CMake Error at src/cpp/CMakeLists.txt:32 (add_library): No SOURCES given to target: flann_cpp CMake Error at src/cpp/CMakeLists.txt:86 (add_library): No SOURCES given to target: flann --- End Message --- --- Begin Message --- Source: flann Source-Version: 1.9.1+dfsg-3 We believe that the bug you reported is fixed in the latest version of flann, 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 897...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated flann 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: Sat, 28 Apr 2018 17:37:51 +0200 Source: flann Binary: libflann-dev libflann1.9 flann-doc Architecture: source Version: 1.9.1+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Jochen Sprickerhof Description: flann-doc - Fast Library for Approximate Nearest Neighbors - documentation libflann-dev - Fast Library for Approximate Nearest Neighbors - development libflann1.9 - Fast Library for Approximate Nearest Neighbors - runtime Closes: 897101 Changes: flann (1.9.1+dfsg-3) unstable; urgency=medium . * Team upload. . [ Mathieu Malaterre ] * Remove self from Uploaders . [ Jochen Sprickerhof ] * Add patch for cmake 3.11 (Closes: #897101) * Update packaging Checksums-Sha1: 9721c57aaa5758bfbf7b19db1537dd5c47bbe80c 2277 flann_1.9.1+dfsg-3.dsc 1c80ea5f0906df9f4765149e1a3b1f006e388410 6956 flann_1.9.1+dfsg-3.debian.tar.xz 8195f7072c8857640ef4252d0ed994df0ad487a1 7264 flann_1.9.1+dfsg-3_source.buildinfo Checksums-Sha256: 38acaea1b8abccd6d3aac3ca591086fdd2a4cc7c38f94361e28c88ad1f296559 2277 flann_1.9.1+dfsg-3.dsc 53ed7ef6249d01a2edd516bb0a675da1b320ac5ad2cc3f89e1078a3a649e2911 6956 flann_1.9.1+dfsg-3.debian.tar.xz 08718782dbab1dc873656ddb248b25fec5bc5b7a49fbb5a0df41212fa2c9e6db 7264 flann_1.9.1+dfsg-3_source.buildinfo Files: 51331831ce9a94b92ab19e11fc9c5973 2277 libs optional flann_1.9.1+dfsg-3.dsc ef0c83505bed0a2c7c3744ac2b207780 6956 libs optional flann_1.9.1+dfsg-3.debian.tar.xz c27418c2d3821cf8c58dd12419e5aee0 7264 libs optional flann_1.9.1+dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAlrkllYUHGpzcHJpY2tl QGRlYmlhbi5vcmcACgkQW//cwljmlDNnJg/+IFQvNNbGuCJS2WW4/ur08gA4VerE sjyjgP4kuPfuCiTd0Qgcr1/9KUWMMAqBAGpfERZbmN1H9hQDvK6AphR8yZTgt4CG 2js1ksGUrxAVCYPT8HaEhdqug0bKVrFXwc3TnQd/W/keNp93qYA7mKvFgpvzwOW/ Q/CXC1wHo/bG8/JX7Mx+5w+TQeHxkkerWCFbrsr3T6WVyDYQj+Mu9JYGUXqEKRZx nqvI+C4cbRztojndjuAzxOWf3nmMV+p7tzxZWgo6R0vZ9TjWypqtOdL8RyWatCd3 jzwEqGhT5BBXekCPWfliYQxNnnkK1WH2d3vc5NKeIjKS0LcsshY/QQoY/KYtIJb+ 15ksfQ8di7SgtqiuvjQnwaA7cBOreB0dJEXFGGY0DROFaoC1GQzv0KMkhrwyMwIj V6ZkPRkIVWEG3JR5cL5PTTX5R0AOTRqyXEkg12R5na/JGypysQ88Zfmd9X6yPLOC MlI6N+S8Y159uLqJ7Z0ayfbHwdWyQuf2Yc34KylalGeQXYrVT832wD1B3l8ZkHRZ wU2IEwbHihWpeut3HwS/JjgBV//G6gGu2y266Oh8UZyBjRoSSy3swZLbimVZnkIU 0utHhvd+9fBDWRnOB3nod0OpJOliUGeS6kIv4WzX9yPOqI6YoqNebMqF7zg3Th56 x90j8SNO5WaVL9k= =/71y -END PGP SIGNATURE End Message ---
Bug#896219: Added python3-distutils dependency
Control: reopen -1
Control: severity -1 important
Control: retitle -1 please avoid the usage of distutils at runtime
Control: tags -1 + patch
While the addition of the dependency fixes the issue, please could you consider
to avoid the usage of distutils at runtime?
diff -Nru importmagic-0.1.7/debian/changelog importmagic-0.1.7/debian/changelog
--- importmagic-0.1.7/debian/changelog 2018-04-28 08:01:34.0 +0200
+++ importmagic-0.1.7/debian/changelog 2018-04-28 17:38:29.0 +0200
@@ -1,3 +1,10 @@
+importmagic (0.1.7-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Avoid usage of distutils at runtime.
+
+ -- Matthias Klose Sat, 28 Apr 2018 17:38:29 +0200
+
importmagic (0.1.7-2) unstable; urgency=medium
[ OndÅej Nový ]
diff -Nru importmagic-0.1.7/debian/patches/avoid-distutils-usage.diff importmagic-0.1.7/debian/patches/avoid-distutils-usage.diff
--- importmagic-0.1.7/debian/patches/avoid-distutils-usage.diff 1970-01-01 01:00:00.0 +0100
+++ importmagic-0.1.7/debian/patches/avoid-distutils-usage.diff 2018-04-28 17:38:23.0 +0200
@@ -0,0 +1,24 @@
+--- a/importmagic/index.py
b/importmagic/index.py
+@@ -8,18 +8,14 @@ import json
+ import logging
+ import re
+ from contextlib import contextmanager
+-from distutils import sysconfig
+
+ from importmagic.util import parse_ast
+
+
+ LIB_LOCATIONS = sorted(set((
+-(sysconfig.get_python_lib(standard_lib=True), 'S'),
+-(sysconfig.get_python_lib(plat_specific=True), '3'),
+-(sysconfig.get_python_lib(standard_lib=True, prefix=sys.prefix), 'S'),
+-(sysconfig.get_python_lib(plat_specific=True, prefix=sys.prefix), '3'),
+-(sysconfig.get_python_lib(standard_lib=True, prefix='/usr/local'), 'S'),
+-(sysconfig.get_python_lib(plat_specific=True, prefix='/usr/local'), '3'),
++('/usr/lib/python%d.%d' % sys.version_info[:2], 'S'),
++('/usr/lib/python3/dist-packages', '3'),
++('/usr/local/lib/python3/dist-packages', '3'),
+ )), key=lambda l: -len(l[0]))
+
+ # Regex matching modules that we never attempt to index.
diff -Nru importmagic-0.1.7/debian/patches/series importmagic-0.1.7/debian/patches/series
--- importmagic-0.1.7/debian/patches/series 2018-04-28 07:46:08.0 +0200
+++ importmagic-0.1.7/debian/patches/series 2018-04-28 17:30:24.0 +0200
@@ -1,2 +1,3 @@
use-debian-six.patch
look-for-test-data.patch
+avoid-distutils-usage.diff
Processed: Re: Added python3-distutils dependency
Processing control commands:
> reopen -1
Bug #896219 {Done: Diane Trout } [python3-importmagic]
python3-importmagic: importmagic fails to import
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions importmagic/0.1.7-2.
> severity -1 important
Bug #896219 [python3-importmagic] python3-importmagic: importmagic fails to
import
Severity set to 'important' from 'serious'
> retitle -1 please avoid the usage of distutils at runtime
Bug #896219 [python3-importmagic] python3-importmagic: importmagic fails to
import
Changed Bug title to 'please avoid the usage of distutils at runtime' from
'python3-importmagic: importmagic fails to import'.
> tags -1 + patch
Bug #896219 [python3-importmagic] please avoid the usage of distutils at runtime
Added tag(s) patch.
--
896219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#895387: marked as done (wavelet-decompose overlaps with gimp 2.10)
Your message dated Sat, 28 Apr 2018 15:35:58 + with message-id and subject line Bug#895387: fixed in gimp 2.10.0-2 has caused the Debian Bug report #895387, regarding wavelet-decompose overlaps with gimp 2.10 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.) -- 895387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gimp-plugin-registry Version: 7.20140602+b4 Severity: important gimp 2.10 RC 1 (now in experimental) contains /usr/lib/gimp/2.0/plug-ins/wavelet-decompose, which overlaps with this package. Can you please remove it from this package so it is superseded by gimp, and gimp can Breaks/Replaces on an older version of this package? Thanks, Ari -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gimp-plugin-registry depends on: ii gimp 2.10.0~RC1-1 ii libatk1.0-0 2.28.1-1 ii libblas3 [libblas.so.3] 3.7.1-4 ii libc62.27-3 ii libcairo21.15.10-2 ii libfftw3-single3 3.3.7-1 ii libfontconfig1 2.12.6-0.1 ii libfreetype6 2.8.1-2 ii libgcc1 1:8-20180321-1 ii libgdk-pixbuf2.0-0 2.36.11-2 ii libgimp2.0 2.10.0~RC1-1 ii libgl1 1.0.0-2 ii libgl1-mesa-glx 17.3.7-1 ii libglew2.0 2.0.0-5 ii libglib2.0-0 2.56.0-4 ii libglu1-mesa [libglu1] 9.0.0-2.1 ii libgtk2.0-0 2.24.32-1 ii libgtkglext1 1.2.0-7 ii libice6 2:1.0.9-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblapack3 [liblapack.so.3] 3.7.1-4 ii liblcms2-2 2.9-1 ii liblqr-1-0 0.4.2-2.1 ii libpango-1.0-0 1.42.0-1 ii libpangocairo-1.0-0 1.42.0-1 ii libpangoft2-1.0-01.42.0-1 ii libpangox-1.0-0 0.0.2-5+b2 ii libsm6 2:1.2.2-1+b3 ii libstdc++6 8-20180321-1 ii libtiff-tools4.0.9-4 ii libtiff5 4.0.9-4 ii libx11-6 2:1.6.5-1 ii libxmu6 2:1.1.2-2 ii libxt6 1:1.1.5-1 ii python 2.7.14-4 ii xdg-utils1.1.2-2 Versions of packages gimp-plugin-registry recommends: pn gimp-gmic Versions of packages gimp-plugin-registry suggests: pn icc-profiles --- End Message --- --- Begin Message --- Source: gimp Source-Version: 2.10.0-2 We believe that the bug you reported is fixed in the latest version of gimp, 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 895...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bicha (supplier of updated gimp 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: Sat, 28 Apr 2018 10:42:04 -0400 Source: gimp Binary: gimp gimp-data gimp-python libgimp2.0 libgimp2.0-dev libgimp2.0-doc Architecture: source Version: 2.10.0-2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bicha Description: gimp - GNU Image Manipulation Program gimp-data - Data files for GIMP gimp-python - Python scripting support for GIMP libgimp2.0 - Libraries for the GNU Image Manipulation Program libgimp2.0-dev - Headers and other files for compiling plugins for GIMP libgimp2.0-doc - Developers' Documentation for the GIMP library Closes: 827083 880186 887717 895387 896812 Launchpad-Bugs-Fixed: 1739684 1759625 Changes: gimp (2.10.0-2) unstable; urgency=medium . * Fix arch:all
Bug#896314: marked as done (python3-cap-ng: capng fails to import)
Your message dated Sat, 28 Apr 2018 15:36:43 +
with message-id
and subject line Bug#896314: fixed in libcap-ng 0.7.9-1
has caused the Debian Bug report #896314,
regarding python3-cap-ng: capng fails to import
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
896314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-cap-ng
Version: 0.7.7-3.1+b1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-cap-ng importing the module capng
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/capng.py", line 14, in swig_import_helper
return importlib.import_module(mname)
File "/usr/lib/python3.6/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 994, in _gcd_import
File "", line 971, in _find_and_load
File "", line 955, in _find_and_load_unlocked
File "", line 658, in _load_unlocked
File "", line 571, in module_from_spec
File "", line 922, in create_module
File "", line 219, in _call_with_frames_removed
ImportError:
/usr/lib/python3/dist-packages/_capng.cpython-36m-x86_64-linux-gnu.so:
undefined symbol: capng_print_caps_numeric
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/capng.py", line 17, in
_capng = swig_import_helper()
File "/usr/lib/python3/dist-packages/capng.py", line 16, in swig_import_helper
return importlib.import_module('_capng')
File "/usr/lib/python3.6/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
ImportError:
/usr/lib/python3/dist-packages/_capng.cpython-36m-x86_64-linux-gnu.so:
undefined symbol: capng_print_caps_numeric
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
--- End Message ---
--- Begin Message ---
Source: libcap-ng
Source-Version: 0.7.9-1
We believe that the bug you reported is fixed in the latest version of
libcap-ng, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 896...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pierre Chifflier (supplier of updated libcap-ng 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: Sat, 28 Apr 2018 17:10:47 +0200
Source: libcap-ng
Binary: libcap-ng-dev libcap-ng0 libcap-ng-utils python-cap-ng python3-cap-ng
Architecture: source amd64
Version: 0.7.9-1
Distribution: unstable
Urgency: medium
Maintainer: Pierre Chifflier
Changed-By: Pierre Chifflier
Description:
libcap-ng-dev - Development and header files for libcap-ng
libcap-ng-utils - Utilities for analysing and setting file capabilities
libcap-ng0 - An alternate POSIX capabilities library
python-cap-ng - Python bindings for libcap-ng
python3-cap-ng - Python3 bindings for libcap-ng
Closes: 725926 829061 896314
Changes:
libcap-ng (0.7.9-1) unstable; urgency=medium
.
* New upstream version 0.7.9 (Closes: #896314, #725926)
* Add symbols file (Closes: #829061)
Checksums-Sha1:
aac000acebfd74971231966c8bcb6dcc44277277 1912 libcap-ng_0.7.9-1.dsc
f29f1eefdfbbd93501d9c7a54ac340d4ca660634 449038 libcap-ng_0.7.9.orig.tar.gz
c739297121b11e662e48e0b1ba3f68926c7e8b0b 5636 libcap-ng_0.7.9-1.debian.tar.xz
907836e09b95da1cf21bdb5b5025b076fc22350c 26500 libcap-ng-dev_0.7.9-1_amd64.deb
29930fd38ff9a90399530530178340bba29fa546 30208
libcap-ng-utils-dbgsym_0.7.9-1_amd64.deb
a078569f8bc6f0e60bea6726535297c38ec75584 19948
libcap-ng-utils_0.7.9-1_amd64.deb
de8e8f96f5f00b5fdab2621fc1098e8a8f8db6fe 16420
libcap-ng0
Bug#897118: telepathy-qt FTBFS with Qt 5.10: symbol disappeared
Source: telepathy-qt Version: 0.9.7-4 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/telepathy-qt.html ... dh_makeshlibs dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libtelepathy-qt5-0/DEBIAN/symbols doesn't match completely debian/libtelepathy-qt5-0.symbols --- debian/libtelepathy-qt5-0.symbols (libtelepathy-qt5-0_0.9.7-4_amd64) +++ dpkg-gensymbolsU6d42g 2019-05-31 09:26:20.782865888 -1200 @@ -1,5 +1,5 @@ libtelepathy-qt5.so.0 libtelepathy-qt5-0 #MINVER# - (optinal=inline)_ZN10QByteArray7reserveEi@Base 0.9.7 +#MISSING: 0.9.7-4# (optinal=inline)_ZN10QByteArray7reserveEi@Base 0.9.7 _ZN2Tp10AccountSet11qt_metacallEN11QMetaObject4CallEiPPv@Base 0.9.5 _ZN2Tp10AccountSet11qt_metacastEPKc@Base 0.9.5 _ZN2Tp10AccountSet12accountAddedERKNS_9SharedPtrINS_7AccountEEE@Base 0.9.5 dh_makeshlibs: failing due to earlier errors make: *** [debian/rules:13: binary] Error 2
Bug#896267: marked as done (python3-yapf: yapf fails to import)
Your message dated Sat, 28 Apr 2018 15:14:34 +
with message-id
and subject line Bug#896267: fixed in yapf 0.21.0-2
has caused the Debian Bug report #896267,
regarding python3-yapf: yapf fails to import
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
896267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896267
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-yapf
Version: 0.21.0-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-yapf importing the module yapf
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/yapf/__init__.py", line 36, in
from yapf.yapflib import file_resources
File "/usr/lib/python3/dist-packages/yapf/yapflib/file_resources.py", line
24, in
from lib2to3.pgen2 import tokenize
ModuleNotFoundError: No module named 'lib2to3'
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
--- End Message ---
--- Begin Message ---
Source: yapf
Source-Version: 0.21.0-2
We believe that the bug you reported is fixed in the latest version of
yapf, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 896...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ana Custura (supplier of updated yapf 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: Sat, 28 Apr 2018 14:22:10 +0100
Source: yapf
Binary: python-yapf yapf python3-yapf yapf3
Architecture: source all
Version: 0.21.0-2
Distribution: unstable
Urgency: medium
Maintainer: Ana Custura
Changed-By: Ana Custura
Description:
python-yapf - public modules for yapf (Python 2)
python3-yapf - public modules for yapf (Python 3)
yapf - Python code formatter for different styles (Python 2)
yapf3 - Python code formatter for different styles (Python 3)
Closes: 896267
Changes:
yapf (0.21.0-2) unstable; urgency=medium
.
* Adds missing dependency on python3-lib2to3 (Closes: #896267)
Checksums-Sha1:
2892656710781d99eac8cc13319e214ffe24a1b5 2127 yapf_0.21.0-2.dsc
6931f6810d61750ba3cf215e24d9504dd7395700 3404 yapf_0.21.0-2.debian.tar.xz
1d3e312316df8c9c4703cb9431fa812b4909d128 105472 python-yapf_0.21.0-2_all.deb
ed2ae0d66dc9eef0f8b9438e5a7093608357dfe1 105592 python3-yapf_0.21.0-2_all.deb
d4f59cd79c2603acab3dab7989ce8da06674c04a 21840 yapf3_0.21.0-2_all.deb
4bebdf37ab1d9cbac6aad01e7bb2f92ac0ecf21d 21836 yapf_0.21.0-2_all.deb
3777e616c783181761515f45ffe03cf3559d815a 7110 yapf_0.21.0-2_amd64.buildinfo
Checksums-Sha256:
0119d4ca1c04f0b564e49aea1b8a8e9ab3a9502ef7dc733df35c93f461a6c5f2 2127
yapf_0.21.0-2.dsc
1f86396de149bf0b5f325ef19676ad1c8b1d8216e19905e6f2a5e1c0a58fddcd 3404
yapf_0.21.0-2.debian.tar.xz
34558d564b213f27c581be128a5405b230a7764e9d2646535fc9df8e1bca5570 105472
python-yapf_0.21.0-2_all.deb
ed1b8809b36069f1e76919c661e66696080ca4d4d3c0d56c6b9ef2878faad6ec 105592
python3-yapf_0.21.0-2_all.deb
470d7e7f545737594e3f12e216cb20fe998dfba07add0214a6698c890097186e 21840
yapf3_0.21.0-2_all.deb
ace5c469af5803c1b54c1892e27153b83bf22a8e819fcf937b202455c4d5581f 21836
yapf_0.21.0-2_all.deb
feb14c7ba866ae71ba4e0cf4d1c27f7339911521b015602feb29f83577383c26 7110
yapf_0.21.0-2_amd64.buildinfo
Files:
dba8befb218ec4d67ae9b050096cb355 2127 python optional yapf_0.21.0-2.dsc
7d3eb38abfa5c9c628449966ed4fc30e 3404 python optional
yapf_0.21.0-2.debian.tar.xz
aa84d4597dceb353c4fa96e18a453549 105472 python optional
python-yapf_0.21.0-2_all.deb
597ef667b2eff8e60c5754d24d9668ba 105592 python optional
python3-yapf_0.21.0-2_all.deb
b23e5eecae1aeb671058a17e1e8f5f79 21840 python optional yapf3_0.21.0-2_all.deb
6fdc27f2e29430b1303330538a715339 21836 python optional yapf_0.21.0-2_all.d
Bug#897006: [petsc-maint] Bug#897006: petsc FTBFS on mips: f951: out of memory
On Sat, Apr 28, 2018 at 08:29:48AM -0500, Satish Balay wrote: > > Also we print a summary of compile flags up in the log: > > Using Fortran compile: mpif90 -c -g -O2 -fstack-protector-strong -fPIC > -Wdate-time -D_FORTIFY_SOURCE=2 > -fdebug-prefix-map=/<>/petsc-3.9.0+dfsg1=. > -I/<>/petsc-3.9.0+dfsg1/include > -I/<>/petsc-3.9.0+dfsg1/mips-linux-gnu-real-debug/include > -I/usr/include/suitesparse -I/usr/include/superlu -I/usr/include/superlu-dist > -I/usr/include/hypre -I/usr/include/hdf5/openmpi -I/usr/include/scotch > -Wdate-time -D_FORTIFY_SOURCE=2 The failing command is: mpif90 -c -g -O2 -fstack-protector-strong -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fdebug-prefix-map=/home/bunk/build/petsc-3.9.0+dfsg1=. -I/home/bunk/build/petsc-3.9.0+dfsg1/include -I/home/bunk/build/petsc-3.9.0+dfsg1/mips-linux-gnu-real-debug/include -I/usr/include/suitesparse -I/usr/include/superlu -I/usr/include/superlu-dist -I/usr/include/hypre -I/usr/include/hdf5/serial -I/usr/include/scotch -Wdate-time -D_FORTIFY_SOURCE=2 -MMD -MP /home/bunk/build/petsc-3.9.0+dfsg1/src/dm/f90-mod/petscdmmod.F -o mips-linux-gnu-real-debug/obj/dm/f90-mod/petscdmmod.o -J/home/bunk/build/petsc-3.9.0+dfsg1/mips-linux-gnu-real-debug/include I am hitting the 2 GB limit even after changing to -g0 -O0. > Also - current build is with: > Using MAKEFLAGS: -j4 -l4 w -j4 -Oline --jobserver-auth=3,4 -- > PETSC_DIR=/<>/petsc-3.9.0+dfsg1 > PETSC_ARCH=mips-linux-gnu-real-debug > CFLAGS=-fdebug-prefix-map=/<>/petsc-3.9.0+dfsg1=. > CXXFLAGS=-fdebug-prefix-map=/<>/petsc-3.9.0+dfsg1=. > FCFLAGS=-fdebug-prefix-map=/<>/petsc-3.9.0+dfsg1=. > FFLAGS=-fdebug-prefix-map=/<>/petsc-3.9.0+dfsg1=. > > If '-j1' is used - memory usage will go down a bit. [but might not be > sufficient to clear the 2 GB limit] This won't make a difference. Overall memory usage is not a problem here, the machines do have 8 GB RAM. > Satish cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#896998: marked as done (python-pip: missing required _vendor module in 9.0.1-2.1)
Your message dated Sat, 28 Apr 2018 15:11:54 + with message-id and subject line Bug#896998: fixed in python-pip 9.0.1-2.2 has caused the Debian Bug report #896998, regarding python-pip: missing required _vendor module in 9.0.1-2.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 896998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896998 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pip Version: 9.0.1-2.1 Severity: serious User: debian...@lists.debian.org Usertags: regression With the upload of version 9.0.1-2.1 of python-pip, the autopkgtest¹ started to fail with lots of instances of the error copied below (full log² attached). The error shows that even importing main from pip fails, I *assume* this makes python-pip nearly useless. Looking at the filelist of the two different packages, indeed the _vendor directory is missing in the latest version. (I created the diffs by taking the filelists from packages.d.o). Please investigate the situation. Paul ¹ https://ci.debian.net/packages/p/python-pip/unstable/amd64/ ² https://ci.debian.net/data/autopkgtest/unstable/amd64/p/python-pip/208814/log.gz Traceback (most recent call last): File "/usr/bin/pip", line 9, in from pip import main File "/usr/lib/python2.7/dist-packages/pip/__init__.py", line 21, in from pip._vendor.requests.packages.urllib3.exceptions import DependencyWarning ImportError: No module named requests.packages.urllib3.exceptions python-pip.log.gz Description: application/gzip 2,7c2,7 < /usr/lib/python3/dist-packages/pip-9.0.1.egg-info/PKG-INFO < /usr/lib/python3/dist-packages/pip-9.0.1.egg-info/dependency_links.txt < /usr/lib/python3/dist-packages/pip-9.0.1.egg-info/entry_points.txt < /usr/lib/python3/dist-packages/pip-9.0.1.egg-info/not-zip-safe < /usr/lib/python3/dist-packages/pip-9.0.1.egg-info/requires.txt < /usr/lib/python3/dist-packages/pip-9.0.1.egg-info/top_level.txt --- > /usr/lib/python3/dist-packages/pip-1.5.6.egg-info/PKG-INFO > /usr/lib/python3/dist-packages/pip-1.5.6.egg-info/dependency_links.txt > /usr/lib/python3/dist-packages/pip-1.5.6.egg-info/entry_points.txt > /usr/lib/python3/dist-packages/pip-1.5.6.egg-info/not-zip-safe > /usr/lib/python3/dist-packages/pip-1.5.6.egg-info/requires.txt > /usr/lib/python3/dist-packages/pip-1.5.6.egg-info/top_level.txt 10c10 < /usr/lib/python3/dist-packages/pip/_vendor/__init__.py --- > /usr/lib/python3/dist-packages/pip/backwardcompat/__init__.py 15c15 < /usr/lib/python3/dist-packages/pip/commands/check.py --- > /usr/lib/python3/dist-packages/pip/commands/bundle.py 17d16 < /usr/lib/python3/dist-packages/pip/commands/download.py 19d17 < /usr/lib/python3/dist-packages/pip/commands/hash.py 25a24 > /usr/lib/python3/dist-packages/pip/commands/unzip.py 27,28c26 < /usr/lib/python3/dist-packages/pip/compat/__init__.py < /usr/lib/python3/dist-packages/pip/compat/dictconfig.py --- > /usr/lib/python3/dist-packages/pip/commands/zip.py 33,37c31 < /usr/lib/python3/dist-packages/pip/models/__init__.py < /usr/lib/python3/dist-packages/pip/models/index.py < /usr/lib/python3/dist-packages/pip/operations/__init__.py < /usr/lib/python3/dist-packages/pip/operations/check.py < /usr/lib/python3/dist-packages/pip/operations/freeze.py --- > /usr/lib/python3/dist-packages/pip/log.py 39,43c33,34 < /usr/lib/python3/dist-packages/pip/req/__init__.py < /usr/lib/python3/dist-packages/pip/req/req_file.py < /usr/lib/python3/dist-packages/pip/req/req_install.py < /usr/lib/python3/dist-packages/pip/req/req_set.py < /usr/lib/python3/dist-packages/pip/req/req_uninstall.py --- > /usr/lib/python3/dist-packages/pip/req.py > /usr/lib/python3/dist-packages/pip/runner.py 45,57c36 < /usr/lib/python3/dist-packages/pip/utils/__init__.py < /usr/lib/python3/dist-packages/pip/utils/appdirs.py < /usr/lib/python3/dist-packages/pip/utils/build.py < /usr/lib/python3/dist-packages/pip/utils/deprecation.py < /usr/lib/python3/dist-packages/pip/utils/encoding.py < /usr/lib/python3/dist-packages/pip/utils/filesystem.py < /usr/lib/python3/dist-packages/pip/utils/glibc.py < /usr/lib/python3/dist-packages/pip/utils/hashes.py < /usr/lib/python3/dist-packages/pip/utils/logging.py < /usr/lib/python3/dist-packages/pip/utils/outdated.py < /usr/lib/python3/dist-packages/pip/utils/packaging.py < /usr/lib/python3/dist-packages/pip/utils/setuptools_build.py < /usr/lib/python3/dist-packages/pip/utils/ui.py --- > /usr/lib/python3/dist-packages/pip/util.py 3,8c3,8 < /usr/lib/python2.7/dist-packages/pip-9.0.1.egg-info/PKG-INFO < /usr/lib/python2.7/dist-packages/pip-9.0.1.egg-info/dependency_links.t
Processed: severity of 897060 is important ...
Processing commands for cont...@bugs.debian.org: > severity 897060 important Bug #897060 [src:linux] linux-image-4.15.0-3-amd64: System does not boot after upgrading to buster Severity set to 'important' from 'critical' > retitle 897060 i915: Call through null pointer during probe of GM45 Bug #897060 [src:linux] linux-image-4.15.0-3-amd64: System does not boot after upgrading to buster Changed Bug title to 'i915: Call through null pointer during probe of GM45' from 'linux-image-4.15.0-3-amd64: System does not boot after upgrading to buster'. > thanks Stopping processing here. Please contact me if you need assistance. -- 897060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897060 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897115: aoflagger FTBFS with cmake 3.11.1
Source: aoflagger Version: 2.10.0-2 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/aoflagger.html ... -- Looking for posix_fallocate -- Looking for posix_fallocate - found CMake Error at CMake/CheckCXXSymbolExists.cmake:48 (_CHECK_SYMBOL_EXISTS): Unknown CMake command "_CHECK_SYMBOL_EXISTS". Call Stack (most recent call first): src/CMakeLists.txt:9 (CHECK_CXX_SYMBOL_EXISTS) -- Configuring incomplete, errors occurred!
Bug#897114: ifrit FTBFS with cmake 3.11.1
Source: ifrit Version: 4.1.2-5 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ifrit.html ... fakeroot debian/rules binary dh binary --buildsystem=cmake --sourcedirectory=build dh_update_autotools_config -O--buildsystem=cmake -O--sourcedirectory=build dh_auto_configure -O--buildsystem=cmake -O--sourcedirectory=build cd obj-x86_64-linux-gnu && cmake ../build -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" -- The C compiler identification is GNU 7.3.0 -- The CXX compiler identification is GNU 7.3.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- The imported target "vtkRenderingPythonTkWidgets" references the file "/usr/lib/x86_64-linux-gnu/libvtkRenderingPythonTkWidgets.so" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/cmake/vtk-6.3/VTKTargets.cmake" but not all the files it references. -- The imported target "vtk" references the file "/usr/bin/vtk" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/cmake/vtk-6.3/VTKTargets.cmake" but not all the files it references. CMake Error at /usr/share/cmake-3.11/Modules/FindQt.cmake:166 (message): Multiple versions of Qt found please set DESIRED_QT_VERSION Call Stack (most recent call first): CMakeLists.txt:174 (INCLUDE) -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found version "2.7.15rc1") CMake Error: Error required internal CMake variable not set, cmake may not be built correctly. Missing variable is: QT_MOC_EXECUTABLE -- Configuring incomplete, errors occurred!
Bug#897113: ktorrent FTBFS with cmake 3.11.1
Source: ktorrent Version: 5.1.0-2 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ktorrent.html ... cd /build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/ktorrent && /usr/bin/c++ -DKCOREADDONS_LIB -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_CAST_TO_ASCII -DQT_NO_CAST_TO_BYTEARRAY -DQT_NO_DEBUG -DQT_NO_URL_CAST_FROM_STRING -DQT_STRICT_ITERATORS -DQT_USE_FAST_OPERATOR_PLUS -DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB -DQT_XML_LIB -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I/build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/ktorrent -I/build/1st/ktorrent-5.1.0/ktorrent -I/build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/ktorrent/ktorrent_app_autogen/include -I/build/1st/ktorrent-5.1.0/libktcore -I/build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/libktcore -I/build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu -isystem /usr/include/KF5/KConfigCore -isystem /usr/include/KF5 -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem /usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KI18n -isystem /usr/include/KF5/KCMUtils -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KCodecs -isystem /usr/include/KF5/KWidgetsAddons -isystem /usr/include/KF5/KConfigGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem /usr/include/KF5/KAuth -isystem /usr/include/KF5/KService -isystem /usr/include/KF5/KParts -isystem /usr/include/KF5/KIOWidgets -isystem /usr/include/KF5/KIOCore -isystem /usr/include/KF5/KJobWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/KF5/KCompletion -isystem /usr/include/KF5/KXmlGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem /usr/include/KF5/KTextWidgets -isystem /usr/include/KF5/SonnetUi -isystem /usr/include/KF5/Solid -isystem /usr/include/KF5/libktorrent -isystem /usr/include/KF5/KArchive -isystem /usr/include/KF5/KCrash -isystem /usr/include/x86_64-linux-gnu -isystem /usr/include/KF5/KDBusAddons -isystem /usr/include/KF5/KIconThemes -isystem /usr/include/KF5/KIOFileWidgets -isystem /usr/include/KF5/KBookmarks -isystem /usr/include/KF5/KItemViews -isystem /usr/include/KF5/KNotifications -isystem /usr/include/KF5/KNotifyConfig -isystem /usr/include/KF5/KWindowSystem -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x -fno-operator-names -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Wvla -Wdate-time -fexceptions -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -std=gnu++11 -o CMakeFiles/ktorrent_app.dir/ktorrent_app_autogen/mocs_compilation.cpp.o -c /build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/ktorrent/ktorrent_app_autogen/mocs_compilation.cpp In file included from /build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/ktorrent/ktorrent_app_autogen/2NRMJ5X7RK/moc_torrentcreatordlg.cpp:9:0, from /build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/ktorrent/ktorrent_app_autogen/mocs_compilation.cpp:10: /build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/ktorrent/ktorrent_app_autogen/2NRMJ5X7RK/../../../../ktorrent/dialogs/torrentcreatordlg.h:86:16: error: field 'update_timer' has incomplete type 'QTimer' QTimer update_timer; ^~~~ In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:44:0, from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qdialog.h:44, from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QDialog:1, from /build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/ktorrent/ktorrent_app_autogen/2NRMJ5X7RK/../../../../ktorrent/dialogs/addpeersdlg.h:25, from /build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/ktorrent/ktorrent_app_autogen/2NRMJ5X7RK/moc_addpeersdlg.cpp:9, from /build/1st/ktorrent-5.1.0/obj-x86_64-linux-gnu/ktorrent/ktorrent_app_autogen/mocs_compilation.cpp:2: /usr/include/x86_64-linux-gnu/qt5/QtGui/qwindowdefs.h:76:7: note: forward declaration of 'class QTimer' class QTimer; ^~ make[3]: *** [ktorrent/CMakeFiles/ktorrent_app.dir/build.make:709: ktorrent/CMakeFiles/ktorrent_app.dir/ktorrent_app_autogen/mocs_compilation.cpp.o] Error 1
Bug#897112: psi FTBFS with Qt 5.10
Source: psi Version: 1.3-3 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/psi.html ... debian/rules build dh build --parallel dh_update_autotools_config -O--parallel debian/rules override_dh_auto_configure make[1]: Entering directory '/build/1st/psi-1.3' #qt-qconf ls -al total 228 drwxr-xr-x 20 pbuilder1 pbuilder1 840 May 20 05:05 . drwxr-xr-x 3 pbuilder1 pbuilder1 120 May 20 05:05 .. -rw-r--r-- 1 pbuilder1 pbuilder1 1048 Jul 19 2017 .gitignore -rw-r--r-- 1 pbuilder1 pbuilder1 371 Aug 18 2017 .gitmodules drwxr-xr-x 3 pbuilder1 pbuilder1 140 May 20 05:05 .pc -rw-r--r-- 1 pbuilder1 pbuilder196 May 25 2015 .qmake.cache.in -rw-r--r-- 1 pbuilder1 pbuilder189 Nov 28 2014 .qmake.conf drwxr-xr-x 4 pbuilder1 pbuilder1 120 May 28 2017 3rdparty -rw-r--r-- 1 pbuilder1 pbuilder1 11255 Sep 23 2017 CMakeLists.txt -rw-r--r-- 1 pbuilder1 pbuilder1 15862 Jan 20 2013 COPYING -rw-r--r-- 1 pbuilder1 pbuilder1 1226 Jan 20 2013 INSTALL -rw-r--r-- 1 pbuilder1 pbuilder1 6364 Sep 23 2017 README -rw-r--r-- 1 pbuilder1 pbuilder1 7909 Sep 23 2017 Readme-cmake-ru.txt -rw-r--r-- 1 pbuilder1 pbuilder1 4411 Sep 23 2017 Readme-cmake.txt -rw-r--r-- 1 pbuilder1 pbuilder1 8120 May 23 2017 TODO drwxr-xr-x 3 pbuilder1 pbuilder1 240 Sep 23 2017 admin drwxr-xr-x 2 pbuilder1 pbuilder1 100 Jan 20 2013 certs -rw-r--r-- 1 pbuilder1 pbuilder1 4142 May 23 2017 client_icons.txt drwxr-xr-x 3 pbuilder1 pbuilder160 May 28 2017 cmake -rwxr-xr-x 1 pbuilder1 pbuilder1 83709 May 20 05:05 configure drwxr-xr-x 4 pbuilder1 pbuilder1 380 May 20 05:06 debian drwxr-xr-x 2 pbuilder1 pbuilder1 220 Jul 25 2017 doc drwxr-xr-x 9 pbuilder1 pbuilder1 180 Jul 25 2017 iconsets -rw-r--r-- 1 pbuilder1 pbuilder1 23664 May 23 2017 iconsets.qrc drwxr-xr-x 7 pbuilder1 pbuilder1 480 May 20 05:05 iris -rw-r--r-- 1 pbuilder1 pbuilder1 281 Jan 20 2013 l10n.pro drwxr-xr-x 2 pbuilder1 pbuilder1 120 May 28 2017 mac drwxr-xr-x 2 pbuilder1 pbuilder1 120 Sep 23 2017 options -rw-r--r-- 1 pbuilder1 pbuilder188 Jul 19 2017 pluginsconf.pri.in -rw-r--r-- 1 pbuilder1 pbuilder1 1770 May 23 2017 psi.appdata.xml -rw-r--r-- 1 pbuilder1 pbuilder1 2189 Feb 21 2016 psi.desktop -rw-r--r-- 1 pbuilder1 pbuilder1 1049 Jul 25 2017 psi.pro -rw-r--r-- 1 pbuilder1 pbuilder1 1001 Jun 17 2017 psi.qc -rw-r--r-- 1 pbuilder1 pbuilder1 256 Jan 20 2013 psi.qrc drwxr-xr-x 6 pbuilder1 pbuilder1 120 Jul 25 2017 qa drwxr-xr-x 2 pbuilder1 pbuilder1 620 May 20 05:05 qcm drwxr-xr-x 2 pbuilder1 pbuilder1 180 Jan 20 2013 sound drwxr-xr-x 21 pbuilder1 pbuilder1 9100 May 20 05:05 src drwxr-xr-x 3 pbuilder1 pbuilder160 Jul 25 2017 themes drwxr-xr-x 2 pbuilder1 pbuilder160 Jan 20 2013 tools -rw-r--r-- 1 pbuilder1 pbuilder1 4 Sep 23 2017 version drwxr-xr-x 2 pbuilder1 pbuilder1 160 Sep 23 2017 win32 QT_SELECT=5 ./configure --prefix=/usr --no-separate-debug-info # --enable-debug Configuring Psi ... Verifying Qt build environment ... fail Reason: Unable to find the 'qmake' tool for Qt 5. Be sure you have a proper Qt 4.0+ build environment set up. This means not just Qt, but also a C++ compiler, a make tool, and any other packages necessary for compiling C++ programs. If you are certain everything is installed, then it could be that Qt is not being recognized or that a different version of Qt is being detected by mistake (for example, this could happen if $QTDIR is pointing to a Qt 3 installation). At least one of the following conditions must be satisfied: 1) --qtdir is set to the location of Qt 2) $QTDIR is set to the location of Qt 3) QtCore is in the pkg-config database 4) qmake is in the $PATH This script will use the first one it finds to be true, checked in the above order. #3 and #4 are the recommended options. #1 and #2 are mainly for overriding the system configuration. make[1]: *** [debian/rules:15: override_dh_auto_configure] Error 1
Bug#897111: pypandoc FTBFS with pandoc 2.1.2
Source: pypandoc
Version: 1.4+ds0-1
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pypandoc.html
...
==
ERROR: test_convert_with_custom_writer (tests.TestPypandoc)
--
Traceback (most recent call last):
File "/build/1st/pypandoc-1.4+ds0/tests.py", line 182, in
test_convert_with_custom_writer
received = pypandoc.convert_file(file_name, lua_file_name)
File "/build/1st/pypandoc-1.4+ds0/pypandoc/__init__.py", line 140, in
convert_file
outputfile=outputfile, filters=filters)
File "/build/1st/pypandoc-1.4+ds0/pypandoc/__init__.py", line 324, in
_convert_input
'Pandoc died with exitcode "%s" during conversion: %s' % (p.returncode,
stderr)
RuntimeError: Pandoc died with exitcode "1" during conversion: pandoc:
/tmp/tmpcfrhkwfoo-bar+baz/tmpe3s0o8.lua: openFile: does not exist (No such file
or directory)
==
FAIL: test_basic_conversion_from_file (tests.TestPypandoc)
--
Traceback (most recent call last):
File "/build/1st/pypandoc-1.4+ds0/tests.py", line 156, in
test_basic_conversion_from_file
self.assertEqualExceptForNewlineEnd(expected, received)
File "/build/1st/pypandoc-1.4+ds0/tests.py", line 399, in
assertEqualExceptForNewlineEnd
self.assertEqual(expected.rstrip('\n'), received.rstrip('\n'))
AssertionError: u'some title\n==' != u'#some title'
- some title
? -
+ #some title? +
- ==
==
FAIL: test_basic_conversion_from_file_with_format (tests.TestPypandoc)
--
Traceback (most recent call last):
File "/build/1st/pypandoc-1.4+ds0/tests.py", line 189, in
test_basic_conversion_from_file_with_format
self.assertEqualExceptForNewlineEnd(expected, received)
File "/build/1st/pypandoc-1.4+ds0/tests.py", line 399, in
assertEqualExceptForNewlineEnd
self.assertEqual(expected.rstrip('\n'), received.rstrip('\n'))
AssertionError: u'some title\n==' != u'#some title'
- some title
? -
+ #some title? +
- ==
==
FAIL: test_basic_conversion_from_string (tests.TestPypandoc)
--
Traceback (most recent call last):
File "/build/1st/pypandoc-1.4+ds0/tests.py", line 197, in
test_basic_conversion_from_string
self.assertEqualExceptForNewlineEnd(expected, received)
File "/build/1st/pypandoc-1.4+ds0/tests.py", line 399, in
assertEqualExceptForNewlineEnd
self.assertEqual(expected.rstrip('\n'), received.rstrip('\n'))
AssertionError: u'some title\n==' != u'#some title'
- some title
? -
+ #some title? +
- ==
==
FAIL: test_basic_conversion_to_file (tests.TestPypandoc)
--
Traceback (most recent call last):
File "/build/1st/pypandoc-1.4+ds0/tests.py", line 231, in
test_basic_conversion_to_file
self.assertEqualExceptForNewlineEnd(expected, written)
File "/build/1st/pypandoc-1.4+ds0/tests.py", line 399, in
assertEqualExceptForNewlineEnd
self.assertEqual(expected.rstrip('\n'), received.rstrip('\n'))
AssertionError: u'some title\n==' != u'#some title'
- some title
? -
+ #some title? +
- ==
==
FAIL: test_conversion_from_markdown_with_extensions (tests.TestPypandoc)
--
Traceback (most recent call last):
File "/build/1st/pypandoc-1.4+ds0/tests.py", line 222, in
test_conversion_from_markdown_with_extensions
self.assertEqualExceptForNewlineEnd(expected_without_extension,
received_without_extension)
File "/build/1st/pypandoc-1.4+ds0/tests.py", line 399, in
assertEqualExceptForNewlineEnd
self.assertEqual(expected.rstrip('\n'), received.rstrip('\n'))
AssertionError: u'strike' !=
u'~strike~'
- strike
?^ ^^
+ ~strike~
?^ ^
==
FAIL: test_conversion_from_non_plain_text_file (tests.TestPypandoc)
--
Traceback (most recent call last):
File "/build/1st/pypandoc-1.4+ds0/tests.py", line 319, in
test_conversion_from_non_plain_text_file
self.assertEqualExceptForNewlineEnd(expected, received)
File "/build/1st/pypandoc-1.4+ds0/tests.py", line 399, in
assertEqualExceptForNewlineEnd
self.assertEqual(expected.rstrip('\n'), received.rstrip('\n'))
Asse
Bug#897108: gitano FTBFS with pandoc 2.1.2
Source: gitano Version: 1.1-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gitano.html ... debian/rules override_dh_auto_build make[1]: Entering directory '/build/1st/gitano-1.1' make make[2]: Entering directory '/build/1st/gitano-1.1' NOTE: Coverage gathering is not enabled make[2]: Leaving directory '/build/1st/gitano-1.1' make -C doc/admin make[2]: Entering directory '/build/1st/gitano-1.1/doc/admin' pandoc --standalone --toc --chapters -V documentclass:report -V geometry:margin=1in -V graphics:true -V papersize:a4paper -H titling.tex -H header.tex -o gitano-admin-doc.pdf 000.mdwn --chapters has been removed. Use --top-level-division=chapter instead. Try pandoc --help for more information. make[2]: *** [Makefile:6: gitano-admin-doc.pdf] Error 2
Bug#897110: libpandoc-wrapper-perl FTBFS with pandoc 2.1.2
Source: libpandoc-wrapper-perl
Version: 0.6.1-1
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libpandoc-wrapper-perl.html
...
--smart/-S has been removed. Use +smart or -smart extension instead.
For example: pandoc -f markdown+smart -t markdown-smart.
Try pandoc --help for more information.
at t/convert.t line 11.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 25 just after 1.
t/convert.t .
ok 1 - html => latex
Dubious, test returned 25 (wstat 6400, 0x1900)
...
--smart/-S has been removed. Use +smart or -smart extension instead.
For example: pandoc -f markdown+smart -t markdown-smart.
Try pandoc --help for more information.
# Failed test 'run'
# at t/methods.t line 79.
# got: '2'
# expected: '0'
# Failed test 'use default arguments'
# at t/methods.t line 80.
# got: ''
# expected: '…
# '
--smart/-S has been removed. Use +smart or -smart extension instead.
For example: pandoc -f markdown+smart -t markdown-smart.
Try pandoc --help for more information.
# Failed test 'run'
# at t/methods.t line 82.
# got: '2'
# expected: '0'
# Failed test 'override default arguments'
# at t/methods.t line 83.
# got: ''
# expected: '\emph{\ldots{}}
# '
# Looks like you failed 4 tests of 34.
t/methods.t .
ok 1 - import
ok 2 - Pandoc->require
ok 3 - require returns singleton
ok 4 - pandoc->require
ok 5 - require throws)
ok 6 - require throws
ok 7 - Pandoc->new
ok 8 - Pandoc->new creates new instance
ok 9 - threw Regexp ((?^:pandoc executable not found))
ok 10 - default executable
ok 11 - set executable
ok 12 - threw Regexp ((?^:pandoc executable not found))
ok 13 - pandoc->version
ok 14 - 'pandoc->version is a version object' isa 'Pandoc::Version'
ok 15 - compare same versions
ok 16 - expect same version
ok 17 - compare lower versions
ok 18 - expect lower version
ok 19 - compare higher versions
ok 20 - expect higher version
ok 21 - invalid version
ok 22 - arguments
ok 23 - executable and arguments
ok 24 - arguments
not ok 25 - run
not ok 26 - use default arguments
not ok 27 - run
not ok 28 - override default arguments
ok 29 - threw Regexp ((?^:^first default argument must be an -option))
ok 30 - set arguments
ok 31 - set arguments with array ref
ok 32 - pandoc->libs
ok 33 - input_formats
ok 34 - output_formats
1..34
Dubious, test returned 4 (wstat 1024, 0x400)
Failed 4/34 subtests
...
Test Summary Report
---
t/convert.t (Wstat: 6400 Tests: 1 Failed: 0)
Non-zero exit status: 25
Parse errors: No plan found in TAP output
t/methods.t (Wstat: 1024 Tests: 34 Failed: 4)
Failed tests: 25-28
Non-zero exit status: 4
Files=11, Tests=115, 3 wallclock secs ( 0.10 usr 0.02 sys + 1.65 cusr 0.56
csys = 2.33 CPU)
Result: FAIL
dh_auto_test: perl Build test --verbose 1 returned exit code 1
make: *** [debian/rules:20: build] Error 2
Bug#897107: vmdb2 FTBFS with pandoc 2.1.2
Source: vmdb2 Version: 0.12-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vmdb2.html ... I: pybuild base:217: /usr/bin/python3 setup.py build running build running build_py creating /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb copying vmdb/version.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb copying vmdb/step_list_tests.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb copying vmdb/step_list.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb copying vmdb/state.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb copying vmdb/spec_tests.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb copying vmdb/spec.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb copying vmdb/runcmd.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb copying vmdb/app.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb copying vmdb/__init__.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb creating /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb/plugins copying vmdb/plugins/virtuals_plugin.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb/plugins copying vmdb/plugins/rootfs_cache_plugin.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb/plugins copying vmdb/plugins/qemudebootstrap_plugin.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb/plugins copying vmdb/plugins/partition_plugin.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb/plugins copying vmdb/plugins/mount_plugin.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb/plugins copying vmdb/plugins/mkimg_plugin.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb/plugins copying vmdb/plugins/mkfs_plugin.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb/plugins copying vmdb/plugins/grub_plugin.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb/plugins copying vmdb/plugins/error_plugin.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb/plugins copying vmdb/plugins/echo_plugin.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb/plugins copying vmdb/plugins/debootstrap_plugin.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb/plugins copying vmdb/plugins/chroot_plugin.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb/plugins copying vmdb/plugins/apt_plugin.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb/plugins copying vmdb/plugins/ansible_plugin.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb/plugins copying vmdb/plugins/__init__.py -> /build/1st/vmdb2-0.12/.pybuild/cpython3_3.6_vmdb2/build/vmdb/plugins running build_scripts creating build creating build/scripts-3.6 copying and adjusting vmdb2 -> build/scripts-3.6 changing mode of build/scripts-3.6/vmdb2 from 644 to 755 ERROR:root:Command failed: make -C yarns b"make[1]: Entering directory '/build/1st/vmdb2-0.12/yarns'\npandoc -H ugly.css --smart --toc --chapters --number-sections \\\n-V geometry:lettersize \\\n\t--standalone --self-contained -o yarns.html *.yarn\nmake[1]: Leaving directory '/build/1st/vmdb2-0.12/yarns'\n" b'--smart/-S has been removed. Use +smart or -smart extension instead.\nFor example: pandoc -f markdown+smart -t markdown-smart.\n--chapters has been removed. Use --top-level-division=chapter instead.\nTry pandoc --help for more information.\nmake[1]: *** [Makefile:25: yarns.html] Error 2\n' building yarns Traceback (most recent call last): File "setup.py", line 79, in 'build': Build, File "/usr/lib/python3.6/distutils/core.py", line 148, in setup dist.run_commands() File "/usr/lib/python3.6/distutils/dist.py", line 955, in run_commands self.run_command(cmd) File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command cmd_obj.run() File "setup.py", line 35, in run self.format_yarns() File "setup.py", line 65, in format_yarns cliapp.runcmd(['make', '-C', 'yarns']) File "/usr/lib/python3/dist-packages/cliapp/runcmd.py", line 64, in runcmd raise cliapp.AppException(msg) cliapp.app.AppException: Command failed: make -C yarns b"make[1]: Entering directory '/build/1st/vmdb2-0.12/yarns'\npandoc -H ugly.css --smart --toc --chapters --number-sections \\\n-V geometry:lettersize \\\n\t--standalone --self-contained -o yarns.html *.yarn\nmake[1]: Leaving directory '/build/1st/vmdb2-0.12/yarns'\n" b'--smart/-S has been removed. Use +smart or -smart extension instead.\nFor example: pandoc -f markdown+smart -t markdown-smart.\n--chapters has been removed. Use --top-level-division=chapter instead.\nTry pandoc --help for more information.\nmake[1]: *** [Makefile:25: yarns.html] Error 2\n' E: pybuild pybuild:336: build: plugin distutils failed with: exit code=1: /usr/bi
Bug#897106: jpylyzer FTBFS with pandoc 2.1.2
Source: jpylyzer Version: 1.18.0-2 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jpylyzer.html ... dh_auto_build python setup.py build --force running build running build_py creating build creating build/lib.linux-x86_64-2.7 creating build/lib.linux-x86_64-2.7/jpylyzer copying jpylyzer/shared.py -> build/lib.linux-x86_64-2.7/jpylyzer copying jpylyzer/jpylyzer.py -> build/lib.linux-x86_64-2.7/jpylyzer copying jpylyzer/etpatch.py -> build/lib.linux-x86_64-2.7/jpylyzer copying jpylyzer/config.py -> build/lib.linux-x86_64-2.7/jpylyzer copying jpylyzer/byteconv.py -> build/lib.linux-x86_64-2.7/jpylyzer copying jpylyzer/boxvalidator.py -> build/lib.linux-x86_64-2.7/jpylyzer copying jpylyzer/__main__.py -> build/lib.linux-x86_64-2.7/jpylyzer copying jpylyzer/__init__.py -> build/lib.linux-x86_64-2.7/jpylyzer copying jpylyzer/shared.py -> build/lib.linux-x86_64-2.7/jpylyzer copying jpylyzer/jpylyzer.py -> build/lib.linux-x86_64-2.7/jpylyzer copying jpylyzer/etpatch.py -> build/lib.linux-x86_64-2.7/jpylyzer copying jpylyzer/config.py -> build/lib.linux-x86_64-2.7/jpylyzer copying jpylyzer/byteconv.py -> build/lib.linux-x86_64-2.7/jpylyzer copying jpylyzer/boxvalidator.py -> build/lib.linux-x86_64-2.7/jpylyzer copying jpylyzer/__main__.py -> build/lib.linux-x86_64-2.7/jpylyzer copying jpylyzer/__init__.py -> build/lib.linux-x86_64-2.7/jpylyzer (cd doc && pandoc -s --toc --toc-depth=2 -N --chapters --latex-engine=xelatex -o jpylyzerUserManual.pdf jpylyzerUserManual.md) --chapters has been removed. Use --top-level-division=chapter instead. --latex-engine has been removed. Use --pdf-engine instead. Try pandoc --help for more information. make[1]: *** [debian/rules:22: override_dh_auto_build] Error 2
Bug#897105: cafeobj FTBFS with pandoc 2.1.2
Source: cafeobj Version: 1.5.7-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cafeobj.html ... make -C doc/refman reference-manual.pdf make[2]: Entering directory '/build/1st/cafeobj-1.5.7/doc/refman' pandoc -f markdown --table-of-contents --toc-depth=2 --template=template.tex --biblatex -V biblio-files=manual.bib -V papersize=a4paper -V mainfont='FreeSerif' -V sansfont='FreeSans' -V monofont='FreeMono' -V documentclass=memoir --latex-engine=xelatex --template=template.tex -t latex -s -o reference-manual.tex reference-manual.md introduction.md overview.md cloudsync.md reference-head.md reference.md --latex-engine has been removed. Use --pdf-engine instead. Try pandoc --help for more information. make[2]: *** [Makefile:71: reference-manual.tex] Error 2
Bug#897104: googletest: breakage due to files moved to other packages
Package: googletest Version: 1.8.0-9 Severity: serious Control: affects -1 src:apt src:flightcrew src:protobuf src:synergy src:aff4 src:meson src:fmtlib src:cctz https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apt.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/flightcrew.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/protobuf.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/synergy.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/aff4.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/meson.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fmtlib.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cctz.html The proper way, also for stretch -> buster upgrades, would be to move the contents of the googletest binary package elsewhere and turn it into an empty meta package depending on all other packages.
Processed: googletest: breakage due to files moved to other packages
Processing control commands: > affects -1 src:apt src:flightcrew src:protobuf src:synergy src:aff4 src:meson > src:fmtlib src:cctz Bug #897104 [googletest] googletest: breakage due to files moved to other packages Added indication that 897104 affects src:apt, src:flightcrew, src:protobuf, src:synergy, src:aff4, src:meson, src:fmtlib, and src:cctz -- 897104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#890887: babl FTBFS on s390x: FAIL: float-to-8bit
Processing control commands: > severity -1 important Bug #890887 [src:babl] babl FTBFS on s390x: FAIL: float-to-8bit Severity set to 'important' from 'serious' -- 890887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890887 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897059: (no subject)
Hello, Submitted a report to libgphoto2 Github issue tracker: https://github.com/gphoto/libgphoto2/issues/265 -- ] ccr/TNSP ^ pWp :: c...@tnsp.org :: https://tnsp.org/~ccr/ ] https://tnsp.org/hg/ -- https://www.openhub.net/accounts/ccr ] PGP key: 7BED 62DE 898D D1A4 FC4A F392 B705 E735 307B AAE3
Bug#890887: babl FTBFS on s390x: FAIL: float-to-8bit
Control: severity -1 important I've ignored build tests failures for babl on s390x in 0.1.46-2 since the test isn't reliable and failure would hold up the gegl/gimp transition. Humorously, it looks like the build tests did pass this time though! https://buildd.debian.org/status/logs.php?pkg=babl&arch=s390x Thanks, Jeremy Bicha
Processed: affects 896596
Processing commands for cont...@bugs.debian.org: > affects 896596 src:ruby-gnome2 src:ruby-poppler Bug #896596 [libpoppler-glib8] poppler-glib always returns 0 length for PopplerInputStream Added indication that 896596 affects src:ruby-gnome2 and src:ruby-poppler > thanks Stopping processing here. Please contact me if you need assistance. -- 896596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897101: flann FTBFS with cmake 3.11.1
Source: flann Version: 1.9.1+dfsg-2 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/flann.html ... -- Configuring done CMake Error at src/cpp/CMakeLists.txt:32 (add_library): No SOURCES given to target: flann_cpp CMake Error at src/cpp/CMakeLists.txt:86 (add_library): No SOURCES given to target: flann
Bug#897100: kicad FTBFS with cmake 3.11.1
Source: kicad Version: 4.0.7+dfsg1-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kicad.html ... -- Looking for strtok_r -- Looking for strtok_r - found CMake Error at CMakeModules/CheckCXXSymbolExists.cmake:41 (_CHECK_SYMBOL_EXISTS): Unknown CMake command "_CHECK_SYMBOL_EXISTS". Call Stack (most recent call first): CMakeModules/PerformFeatureChecks.cmake:86 (check_cxx_symbol_exists) CMakeLists.txt:141 (perform_feature_checks)
Bug#897099: diffoscope FTBFS with file 5.33
Source: diffoscope
Version: 93
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope.html
...
=== FAILURES ===
_ test_text_proper_indentation _
capsys = <_pytest.capture.CaptureFixture object at 0x7f3475f7c828>
def test_text_proper_indentation(capsys):
out = run(capsys, pair=('archive1.tar', 'archive2.tar'))
> assert out == get_data('archive12.diff.txt')
E assert '--- archive1... -a\\n\u2502 \u2502 +b\\n' == '--- archive1
-a\\n\u2502 \u2502 +b\\n'
E --- archive1.tar
E +++ archive2.tar
E \u251c\u2500\u2500 file list
E \u2502 @@ -1 +1 @@
E \u2502 --rw-r--r-- 0 lamby (1000) lamby (1000) 22
2017-03-19 22:26:58.00 compressed.gz
E \u2502 +-rw-r--r-- 0 lamby (1000) lamby (1000) 33
2017-03-19 22:27:42.00 compressed.gz
E \u251c\u2500\u2500 compressed.gz
E \u2502 \u251c\u2500\u2500 filetype from file(1)
E \u2502 \u2502 @@ -1 +1 @@
E - \u2502 \u2502 -gzip compressed data, max compression, from Unix,
original size 2
E ?
-
E + \u2502 \u2502 -gzip compressed data, max compression, from Unix
E - \u2502 \u2502 +gzip compressed data, was "compressed", last
modified: Sun Mar 19 22:27:42 2017, max compression, from Unix, original size 2
E ?
-
E + \u2502 \u2502 +gzip compressed data, was "compressed", last
modified: Sun Mar 19 22:27:42 2017, max compression, from Unix
E \u2502 \u251c\u2500\u2500 compressed
E \u2502 \u2502 @@ -1 +1 @@
E \u2502 \u2502 -a
E \u2502 \u2502 +b
...
= 9 failed, 362 passed, 18 skipped in 1001.16 seconds ==
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: cd
/build/1st/diffoscope-93/.pybuild/cpython3_3.6/build; python3.6 -m pytest -vv
-r sxX -l --cov=diffoscope --cov-report=term-missing --cov-report=html
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.6 returned
exit code 13
make: *** [debian/rules:35: binary] Error 25
Bug#897006: [petsc-maint] Bug#897006: petsc FTBFS on mips: f951: out of memory
On Sat, 28 Apr 2018, Matthew Knepley wrote: > On Sat, Apr 28, 2018 at 5:58 AM, Adrian Bunk wrote: > > mips and mipsel are the only architectures where we have only 2 GB > > address space for userspace, so when the compiler needs more than > > 2 GB of memory you are getting this error. > > > > On other 32bit buildds you have 3 GB or even 4 GB address space, > > mips/mipsel is the canary for huge memory usage. > > > > gcc sometimes has huge memory usage compiling C++ hitting this 2 GB > > limit, it is possible that there are also problems with Fortran code. > > > > It is very annoying that the buildd log hides the compiler flags, > > if you fix that I'll take a look regarding a workaround. > > > > make V=1 Also we print a summary of compile flags up in the log: Using Fortran compile: mpif90 -c -g -O2 -fstack-protector-strong -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fdebug-prefix-map=/<>/petsc-3.9.0+dfsg1=. -I/<>/petsc-3.9.0+dfsg1/include -I/<>/petsc-3.9.0+dfsg1/mips-linux-gnu-real-debug/include -I/usr/include/suitesparse -I/usr/include/superlu -I/usr/include/superlu-dist -I/usr/include/hypre -I/usr/include/hdf5/openmpi -I/usr/include/scotch -Wdate-time -D_FORTIFY_SOURCE=2 Also - current build is with: Using MAKEFLAGS: -j4 -l4 w -j4 -Oline --jobserver-auth=3,4 -- PETSC_DIR=/<>/petsc-3.9.0+dfsg1 PETSC_ARCH=mips-linux-gnu-real-debug CFLAGS=-fdebug-prefix-map=/<>/petsc-3.9.0+dfsg1=. CXXFLAGS=-fdebug-prefix-map=/<>/petsc-3.9.0+dfsg1=. FCFLAGS=-fdebug-prefix-map=/<>/petsc-3.9.0+dfsg1=. FFLAGS=-fdebug-prefix-map=/<>/petsc-3.9.0+dfsg1=. If '-j1' is used - memory usage will go down a bit. [but might not be sufficient to clear the 2 GB limit] Satish
Bug#897059: marked as done (libgphoto2-6: libgphoto2 causes corrupted image file transfers)
Your message dated Sat, 28 Apr 2018 13:19:49 + with message-id and subject line Bug#897059: fixed in gphoto2 2.5.17-1 has caused the Debian Bug report #897059, regarding libgphoto2-6: libgphoto2 causes corrupted image file transfers 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.) -- 897059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897059 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgphoto2-6 Version: 2.5.17 Severity: normal Dear Maintainer, After upgrading libgphoto2 to latest packaged version 2.5.17, I immediately noticed that the CR2 RAW files fetched via "gphoto2 -P" were unreadable by Darktable, Adobe Lightroom and other RAW image software. My cameras are Canon EOS 7D Mark II and Canon EOS 500D, connected via USB. The problem occurs with both cameras. I quickly noticed that repeated transfers resulted in files with different SHA256 sums. Downgrading to libgphoto2 to previous 2.5.16 makes the problem go away, checksums are always consistent. With 2.5.17, each file had different checksum for each transfer, pointing to serious corruption. I should state that this is a VERY SERIOUS ISSUE! Usually when I transfer photos from camera, I also immediately delete them from the camera's memory card. Fortunately I noticed the problem with only few pictures taken, so I personally suffered almost no loss... but it could have been much worse! I have no idea if this affects only Canon cameras, as the changelog for 2.5.17 states various EOS -related changes, but I think notifying upstream would be appropriate. -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.5-qcmm (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) --- End Message --- --- Begin Message --- Source: gphoto2 Source-Version: 2.5.17-1 We believe that the bug you reported is fixed in the latest version of gphoto2, 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 897...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Herbert Parentes Fortes Neto (supplier of updated gphoto2 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: Sat, 28 Apr 2018 08:55:09 -0300 Source: gphoto2 Binary: gphoto2 Architecture: source amd64 Version: 2.5.17-1 Distribution: unstable Urgency: medium Maintainer: Debian PhotoTools Maintainers Changed-By: Herbert Parentes Fortes Neto Description: gphoto2- digital camera command-line client Closes: 897059 Changes: gphoto2 (2.5.17-1) unstable; urgency=medium . * New upstream version 2.5.17. (Closes: #897059) * debian/control: - Bump Standards-Version from 4.1.3 to 4.1.14 - Update Homepage field * debian/copyright: - Fix year for Felipe Castro - po/eo.po. * debian/source: - Add options file. Ignore po directory changes. Checksums-Sha1: 9a4a9ff5d73151eee5e1179c40ebd3e8d3ff2db6 2223 gphoto2_2.5.17-1.dsc b3cbb95088691439864ec60e7056ea3ff5df3765 445432 gphoto2_2.5.17.orig.tar.gz ea45c825eddd5e668f51c2c2298c527784f9474f 88188 gphoto2_2.5.17-1.debian.tar.xz bc9f51b5b42f2f6919c74ff2f54876c4ec5dc2af 133900 gphoto2-dbgsym_2.5.17-1_amd64.deb 0965a271f31cfc47a3914338b647033b3361770e 7407 gphoto2_2.5.17-1_amd64.buildinfo 6e2c89e076cac6f965ea6e882be52a330777d722 190564 gphoto2_2.5.17-1_amd64.deb Checksums-Sha256: ede9520eb409d788fcbdedf4c434e9e49cdbcedfeb7873d739c6eb119afc382a 2223 gphoto2_2.5.17-1.dsc 5837085450a8ddf10152962b3574b95e21f330d49923effc2b02f2aa4733ad53 445432 gphoto2_2.5.17.orig.tar.gz 555737df24a59df5903596e06c87ce45b55c725fd150a0310e49c2c3693257ed 88188 gphoto2_2.5.17-1.debian.tar.xz 1eeb03a623e4b15a2ca42de85d223a853b97753e0b780406cf55dca7ac5c4ab0 133900 gphoto2-dbgsym_2.5.17-1_amd64.deb 3da5b355ff74a0040ece1550b7456b16716e1281766d8eb8c723a9d7c1563e6d 7407 gphoto2_2.5.17-1_amd64.buildinfo 75c738b9a170df94107f1a8c6e0e958c726989e80d2525268dc2efef8b8c88ce 190564 gphoto2_2.5.17-1_amd64.deb Files: c933018
Bug#897098: ppl FTBFS with TeX Live 2018
Source: ppl
Version: 1:1.2-2
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ppl.html
...
pl-1.2/doc/bugseng_logo.pdf>] [4] [1] [2] (./index.tex
Underfull \hbox (badness 1) detected at line 9
[][][]
pdfTeX warning (ext4): destination with the same identifier (name{page.1}) has
been already used, duplicate ignored
\relax
l.25
[1]) (/build/1st/ppl-1.2/doc/gpl.tex
! LaTeX Error: Can be used only in preamble.
See the LaTeX manual or LaTeX Companion for explanation.
Type H for immediate help.
...
l.1 \documentclass
[a4paper,12pt]{article}
?
! Emergency stop.
...
l.1 \documentclass
[a4paper,12pt]{article}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[2]: *** [Makefile:6: refman.pdf] Error 1
Bug#895387: marked as done (wavelet-decompose overlaps with gimp 2.10)
Your message dated Sat, 28 Apr 2018 13:05:33 + with message-id and subject line Bug#895387: fixed in gimp 2.10.0-1 has caused the Debian Bug report #895387, regarding wavelet-decompose overlaps with gimp 2.10 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.) -- 895387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gimp-plugin-registry Version: 7.20140602+b4 Severity: important gimp 2.10 RC 1 (now in experimental) contains /usr/lib/gimp/2.0/plug-ins/wavelet-decompose, which overlaps with this package. Can you please remove it from this package so it is superseded by gimp, and gimp can Breaks/Replaces on an older version of this package? Thanks, Ari -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gimp-plugin-registry depends on: ii gimp 2.10.0~RC1-1 ii libatk1.0-0 2.28.1-1 ii libblas3 [libblas.so.3] 3.7.1-4 ii libc62.27-3 ii libcairo21.15.10-2 ii libfftw3-single3 3.3.7-1 ii libfontconfig1 2.12.6-0.1 ii libfreetype6 2.8.1-2 ii libgcc1 1:8-20180321-1 ii libgdk-pixbuf2.0-0 2.36.11-2 ii libgimp2.0 2.10.0~RC1-1 ii libgl1 1.0.0-2 ii libgl1-mesa-glx 17.3.7-1 ii libglew2.0 2.0.0-5 ii libglib2.0-0 2.56.0-4 ii libglu1-mesa [libglu1] 9.0.0-2.1 ii libgtk2.0-0 2.24.32-1 ii libgtkglext1 1.2.0-7 ii libice6 2:1.0.9-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblapack3 [liblapack.so.3] 3.7.1-4 ii liblcms2-2 2.9-1 ii liblqr-1-0 0.4.2-2.1 ii libpango-1.0-0 1.42.0-1 ii libpangocairo-1.0-0 1.42.0-1 ii libpangoft2-1.0-01.42.0-1 ii libpangox-1.0-0 0.0.2-5+b2 ii libsm6 2:1.2.2-1+b3 ii libstdc++6 8-20180321-1 ii libtiff-tools4.0.9-4 ii libtiff5 4.0.9-4 ii libx11-6 2:1.6.5-1 ii libxmu6 2:1.1.2-2 ii libxt6 1:1.1.5-1 ii python 2.7.14-4 ii xdg-utils1.1.2-2 Versions of packages gimp-plugin-registry recommends: pn gimp-gmic Versions of packages gimp-plugin-registry suggests: pn icc-profiles --- End Message --- --- Begin Message --- Source: gimp Source-Version: 2.10.0-1 We believe that the bug you reported is fixed in the latest version of gimp, 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 895...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bicha (supplier of updated gimp 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: Sat, 28 Apr 2018 08:44:18 -0400 Source: gimp Binary: gimp gimp-data gimp-python libgimp2.0 libgimp2.0-dev libgimp2.0-doc Architecture: source Version: 2.10.0-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bicha Description: gimp - GNU Image Manipulation Program gimp-data - Data files for GIMP gimp-python - Python scripting support for GIMP libgimp2.0 - Libraries for the GNU Image Manipulation Program libgimp2.0-dev - Headers and other files for compiling plugins for GIMP libgimp2.0-doc - Developers' Documentation for the GIMP library Closes: 827083 880186 887717 895387 896812 Launchpad-Bugs-Fixed: 1739684 1759625 Changes: gimp (2.10.0-1) unstable; urgency=medium . * New upstream
Bug#897059: [Pkg-phototools-devel] Bug#897059: Bug#897059: libgphoto2-6: libgphoto2 causes corrupted image file transfers
Em 28-04-2018 09:35, Matti Hämäläinen escreveu: > On Sat, 28 Apr 2018, Herbert Fortes wrote: > >> Em 27-04-2018 21:26, Matti Hämäläinen escreveu: >>> >>> Hello, >>> >>> I tested against the current upstream GIT version >>> (91a8425a4fa27def793fa9db2bcb4a71c26c927b) >>> of libgphoto2, and the problem exists there as well. >>> >>> If gphoto debug logs are needed, I can provide ones against working 2.5.16 >>> and non-working, but they are rather large (about 100M uncompressed each, >>> 75M both tar+xz'd). >>> >> >> I think the problem is that you are using gphoto2 version 2.5.16 >> with libgphoto2 version 2.5.17. >> >> There is a gphoto2 version 2.5.17. I forgot to upload it. :(. I am >> really sorry about that. >> >> I am starting to do the pachage now. > > Sorry to bring bad news, but I now tested gphoto2 from GIT (with GIT > libgphoto2) as well, and the problem persists with that. :( Humm, I just did the upload closing this bug. I will reopen it. And I think is better to send an email to the upstream as you suggested on the first email. A debug log is good But with that size can you put somewhere? Probably the upstream will like to see it. Regards, Herbert > > -- > [ .. LD_LIBRARY_PATH=/opt/lib ] > $ /opt/bin/gphoto2 --version > gphoto2 2.5.17.1 > > Copyright (c) 2000-2018 Lutz Mueller and others > > gphoto2 comes with NO WARRANTY, to the extent permitted by law. You may > redistribute copies of gphoto2 under the terms of the GNU General Public > License. For more information about these matters, see the files named > COPYING. > > This version of gphoto2 is using the following software versions and options: > gphoto2 2.5.17.1 gcc, popt(m), exif, no cdk, no aa, jpeg, > readline > libgphoto2 2.5.17.1 all camlibs, gcc, ltdl, EXIF > libgphoto2_port 0.12.0 iolibs: disk ptpip serial usb1 usbdiskdirect > usbscsi, gcc, ltdl, USB, serial without locking > > > I wrote a short shell script for testing, > https://tnsp.org/~ccr/gphoto2/testgphoto.sh > probably not useful, but who knows. :) If more information is needed, I can > try things out. > > Matti > > > > ___ > Pkg-phototools-devel mailing list > pkg-phototools-de...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-phototools-devel >
Processed: uwsgi must drop libapache2-mod-proxy-uwsgi{,-dbg}
Processing control commands:
> affects -1 libapache2-mod-proxy-uwsgi-dbg
Bug #897097 [src:uwsgi] uwsgi must drop libapache2-mod-proxy-uwsgi{,-dbg}
Added indication that 897097 affects libapache2-mod-proxy-uwsgi-dbg
--
897097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#897097: uwsgi must drop libapache2-mod-proxy-uwsgi{,-dbg}
Source: uwsgi Version: 2.0.15-10.4 Severity: serious Control: affects -1 libapache2-mod-proxy-uwsgi-dbg libapache2-mod-proxy-uwsgi is now a transitional package in src:apache2.
