Bug#910220: libdmtx-dev: copyright file missing after upgrade (policy 12.5)

[Roberto Lumbreras]

Hi Reiner,

I'll release a fix for this issue ASAP. Thank you!


On Tue, Nov 20, 2018 at 5:06 PM Reiner Herrmann  wrote:

> Control: tags -1 + patch
>
> In 0.7.5-1 /usr/share/doc/libdmtx-dev has been symlinked to libdmtx0a
> with "dh_installdocs --link-doc=libdmtx0a".
> But according to dh_installdocs(1) this requires a "dir to symlink"
> migration. As this is missing, the directory still exists after an
> upgrade, but is empty.
> With the attached patch, dpkg-maintscript-helper(1) is used to perform
> the migration on the next upgrade.
>
> Please make sure that the version inside the file matches before
> uploading.
>
> Kind regards,
>   Reiner
>


-- 
Regards,
Roberto Lumbreras
Debian developer

Bug#914166: marked as done (gitlab: CVE-2018-19359: Unauthorized service template creation)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 06:49:40 +
with message-id 
and subject line Bug#914166: fixed in gitlab 11.3.10+dfsg-1
has caused the Debian Bug report #914166,
regarding gitlab: CVE-2018-19359: Unauthorized service template creation
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.)


-- 
914166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitlab
Version: 10.8.7+dfsg-1
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for gitlab.

CVE-2018-19359[0]:
Unauthorized service template creation

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-19359
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19359
[1] 
https://about.gitlab.com/2018/11/19/critical-security-release-gitlab-11-dot-4-dot-6-released/

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gitlab
Source-Version: 11.3.10+dfsg-1

We believe that the bug you reported is fixed in the latest version of
gitlab, 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 914...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated gitlab package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 21 Nov 2018 11:49:29 +0530
Source: gitlab
Binary: gitlab gitlab-common
Architecture: source all
Version: 11.3.10+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 gitlab - git powered software platform to collaborate on code (non-omnibus
 gitlab-common - git powered software platform to collaborate on code (common)
Closes: 914166
Changes:
 gitlab (11.3.10+dfsg-1) experimental; urgency=medium
 .
   * New upstream version 11.3.10+dfsg (Closes: #914166) (Fixes: CVE-2018-19359)
   * Relax ruby-js-regex version
   * Tighten dependencies (update minimum versions)
Checksums-Sha1:
 47e1bd5f286eda21f75632a0ed9e608655d4ffaa 2552 gitlab_11.3.10+dfsg-1.dsc
 90a1195a4cd9a8cb489ec1f8c03b24e57cc9184d 38760492 
gitlab_11.3.10+dfsg.orig.tar.xz
 f013289c99c2f14919c2344a9c1eb1ae726ddb97 65240 
gitlab_11.3.10+dfsg-1.debian.tar.xz
 3f51e680b2b4873e61285572470ddb48abd6497b 134236 
gitlab-common_11.3.10+dfsg-1_all.deb
 6f422f08e977ebdf40856858ee31a5b3befcd19a 39254508 gitlab_11.3.10+dfsg-1_all.deb
 945684a626737ec998bfabe39086d7039e12b44f 9164 
gitlab_11.3.10+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 2803be93a8ef34c3c399765a6a9f07b68c4a7f7c0f1c00b94a788237fbe3cd49 2552 
gitlab_11.3.10+dfsg-1.dsc
 a733382f8bdd155a55db99dd142573517ce55ea79366e7f766c652879bce0ab0 38760492 
gitlab_11.3.10+dfsg.orig.tar.xz
 13a7f4ffbe855d168184f0596aa546f60e9f8fabe9b910944042f10d30741454 65240 
gitlab_11.3.10+dfsg-1.debian.tar.xz
 52ed75557097afa84440e6bea495bade4ef1552b8dd8f2c450924e04e9f5 134236 
gitlab-common_11.3.10+dfsg-1_all.deb
 1511023d1e181021a2022fc70b1d3d184f9ae2e11718f358267982fc21c4001b 39254508 
gitlab_11.3.10+dfsg-1_all.deb
 e5ad9fe5626ef910191e7a105fe03bc27b8ef7d3dd25c58ac97f0b71860f69eb 9164 
gitlab_11.3.10+dfsg-1_amd64.buildinfo
Files:
 b278712c82e8900dd6d98720ca015e11 2552 contrib/net optional 
gitlab_11.3.10+dfsg-1.dsc
 c4ad863439ca020f81e6e16a1d3bee36 38760492 contrib/net optional 
gitlab_11.3.10+dfsg.orig.tar.xz
 5c9e3e94103aee406853a6d4b92f90f4 65240 contrib/net optional 
gitlab_11.3.10+dfsg-1.debian.tar.xz
 2d9f913ec13438fd9441131406283c3b 134236 contrib/net optional 
gitlab-common_11.3.10+dfsg-1_all.deb
 110bda391eade1adcb8625959094bf0e 39254508 contrib/net optional 
gitlab_11.3.10+dfsg-1_all.deb
 ca2995ea37250b676b8fce339f018673 9164 contrib/net optional 
gitlab_11.3.10+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE/OFtr184QaN6dPMgC3aSB2Kmt4UFAlv0/KYACgkQC3aSB2Km
t4U+IQ//dBmagFlqMuFK+rpgZBYfbuTDBFdPJxHRw132zwrCtKsTpARRbjzzCjdo
qIzftxA8oku0b+9QDvR/+F6GmMXpi8GXALepyrRUxK5FgcthTPFXxubYxApvIlpq

Bug#914141: marked as done (python-escript FTBFS with boost 1.67)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 06:19:46 +
with message-id 
and subject line Bug#914141: fixed in python-escript 5.2-3
has caused the Debian Bug report #914141,
regarding python-escript FTBFS with boost 1.67
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.)


-- 
914141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-escript
Version: 5.2-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=python-escript=sid

...
Install file: "debian/tmp2/posix/weipa/py/__init__.pyc" as 
"debian/stage2/esys/weipa/__init__.pyc"
/<>/debian/stage2/bin/run-escript 
/<>/debian/tmp2/scripts/release_sanity.py
Traceback (most recent call last):
  File "/<>/debian/tmp2/scripts/release_sanity.py", line 8, in 

from esys.escript import *
  File "escript/py_src/__init__.py", line 28, in 
from esys.escriptcore.escriptcpp import *
ImportError: /<>/debian/stage2/lib/libescript.so: undefined 
symbol: _ZTVN5boost6python17error_already_setE
scons: *** [dummy] Error 1
scons: building terminated because of errors.

*** Config Summary (see config.log and /lib/buildvars for details) ***
Escript revision 6702
  Install prefix:  /<>/debian/stage2
  Python:  /usr/bin/python2 (Version 2.7.15)
   boost:  /usr (Version 1.67.0)
   numpy:  YES (with headers)
  Solver library:  paso
   Direct solver:  NONE
 domains:  dudley, finley, ripley, speckley
  netcdf:  YES (4 + 3)
   weipa:  YES
  openmp:  YES
gdal:  YES
  pyproj:  YES
   scipy:  YES
silo:  YES

  DISABLED features: boomeramg cppunit cuda debug gmsh gzip lapack mkl mpi papi 
parmetis sympy trilinos umfpack visit
  Treating warnings as errors

WARNING: Cannot import sympy. Symbolic toolbox and nonlinear PDEs will not be 
available.
WARNING: matplotlib not found, will skip some unit tests
WARNING: gmsh not available. Skipping tests usersguide/trapezoid.py 
usersguide/quad.py usersguide/brick.py usersguide/refine.py 
cookbook/example04a.py cookbook/example04b.py cookbook/example05a.py 
cookbook/example05b.py cookbook/example05c.py cookbook/example06.py 
cookbook/example08c.py cookbook/example09m.py cookbook/example09a.py 
cookbook/example10m.py inversion/dc_forward.py!

ERROR: build stopped due to errors

make[1]: *** [debian/rules:61: override_dh_auto_build] Error 2


The Ubuntu diff seems to contain a fix.
--- End Message ---
--- Begin Message ---
Source: python-escript
Source-Version: 5.2-3

We believe that the bug you reported is fixed in the latest version of
python-escript, 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 914...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated python-escript 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 20 Nov 2018 07:03:31 +
Source: python-escript
Binary: python-escript python-escript-mpi python3-escript python3-escript-mpi 
python-escript-doc
Architecture: source amd64 all
Version: 5.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Description:
 python-escript - Escript/Finley finite elements Python2 system (with OpenMP)
 python-escript-doc - Documentation for Escript/Finley
 python-escript-mpi - Escript/Finley finite elements Python2 system (OpenMP + 
MPI)
 python3-escript - Escript/Finley finite elements Python3 system (with OpenMP)
 python3-escript-mpi - Escript/Finley finite elements Python3 system (OpenMP + 
MPI)
Closes: 914141
Changes:
 python-escript (5.2-3) unstable; urgency=medium
 .
   * Fix from Michael Hudson-Doyle for boost python name change.
 Closes: #914141
Checksums-Sha1:
 e9052cfa325d37d39be5abd8c5da2a30d940c199 2767 python-escript_5.2-3.dsc
 335a10e858e0cddf852b2d9b4bf1a4722ecd70e7 15232 
python-escript_5.2-3.debian.tar.xz
 3db59a3f1c07c192e8ba7b21717431a072a4d32d 41613900 
python-escript-dbgsym_5.2-3_amd64.deb
 c88d3f8ab981777a400c25ca3dca67c35fb8a9bb 13761836 
python-escript-doc_5.2-3_all.deb
 

Bug#911956: [src:yaml-cpp] FTBFS with boost1.67

[Andreas Tille]

Hi,

whoever wants to really care for this package please take over.  I'm
simply in Uploaders since it was de facto orphaned and some packages of
mine were depending from it.  I never really intended to maintain the
package and would be really happy if someone else takes over.  Feel
free to remove me from Uploaders.

Kind regards

 Andreas.

On Sun, Nov 18, 2018 at 05:34:10PM -0500, Boyuan Yang wrote:
> X-Debbugs-CC: ti...@debian.org lifong...@gmail.com p...@paulnovo.us
> 
> Hi Andreas and all yaml-cpp maintainers,
> 
> It's a pretty severe situation. The transition of package yaml-cpp from 0.5.x
> to 0.6.x is a long overdue and with the approach of Buster freeze, we might
> need to do the transition ASAP or we'd never finish the transition before
> Buster release. Besides, no upload was made since 2016 and many bugs are
> unfixed.
> 
> Andreas, I know you might be overwhelmed by other work either in Debian or
> outside of Debian (I saw ~1000 packages on your DDPO page...) but I'd like to
> know you opinion torwards this package since you look like the only one active
> among the maintainers / uploaders. (Lifeng and Paul: I'd also be glad to hear
> from you if you are reading this email.)
> 
> My personal suggestion is that we fix the libboost 1.67 transition first and
> see if we could finish yaml-cpp 0.6.x transition in the rest of the time.
> 
> --
> Thanks,
> Boyuan Yang
> 
> 
> 在 2018-10-26五的 17:09 +0200，Giovanni Mascellani写道：
> > Package: src:yaml-cpp
> > Version: 0.5.2-4
> > Severity: wishlist
> > Tags: patch
> > User: team+bo...@tracker.debian.org
> > Usertags: boost1.67
> > 
> > Dear Maintainer,
> > 
> > your package fails to build with boost1.67. You can find a build log
> > attached. If you want to attempt the build yourself, an updated version
> > of boost-defaults which brings in boost1.67 dependencies can be found
> > adding this line to your sources.list file:
> > 
> >   deb https://people.debian.org/~gio/reprepro unstable main
> > 
> > This bug has severity whishlist for the moment, but it will raised to RC
> > as soon as version 1.67 of Boost is promoted to default.
> > 
> > More specifically, your package fails building because boost::next and
> > boost::prior were moved to the header boost/next_prior.hpp. The attached
> > patch should fix this issue.
> > 
> > Please consider applying the attached patch as soon as boost1.67 is made
> > default in order to avoid FTBFS.
> > 
> > Thanks and all the best, Giovanni.



-- 
http://fam-tille.de

Bug#914254: bacula: fails to restore properly

[Carsten Leonhardt]

Package: src:bacula
Version: 9.2.2-1
Severity: serious

On 20.11.18 21:59, Sven Hartge wrote:

[...] when "-u root -g root -k" is set, even though the process runs as
root, it doesn't have the proper capabilities anymore.

Processed: Re: Bug#914225: linux-image-4.9.0-8-amd64: Kernel Oops / divide zero when logging in via gdm

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #914225 [src:linux] linux-image-4.9.0-8-amd64: Kernel Oops / divide zero 
when logging in via gdm
Severity set to 'important' from 'critical'
> tag -1 moreinfo
Bug #914225 [src:linux] linux-image-4.9.0-8-amd64: Kernel Oops / divide zero 
when logging in via gdm
Added tag(s) moreinfo.

-- 
914225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914225
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#914225: linux-image-4.9.0-8-amd64: Kernel Oops / divide zero when logging in via gdm

[Ben Hutchings]

Control: severity -1 important
Control: tag -1 moreinfo

On Tue, 2018-11-20 at 10:45 -0800, Mike Neilly wrote:
[...]
> ** Tainted: PO (4097)
>  * Proprietary module has been loaded.
>  * Out-of-tree module has been loaded.
[...]

Is this reproducible without using the proprietary nvidia driver?

Ben.

-- 
Ben Hutchings
Time is nature's way of making sure that
everything doesn't happen at once.




signature.asc
Description: This is a digitally signed message part

Bug#902714: marked as done (minieigen: FTBFS with Boost >= 1.65)

[Debian Bug Tracking System]

Your message dated Tue, 20 Nov 2018 22:24:31 +
with message-id 
and subject line Bug#902714: fixed in minieigen 0.50.3+dfsg1-6
has caused the Debian Bug report #902714,
regarding minieigen: FTBFS with Boost >= 1.65
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.)


-- 
902714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: minieigen
Version: 0.50.3+dfsg1-5
Severity: wishlist
Tags: ftbfs patch

Hi Maintainer

The attached patch from upstream allows minieigen to build with recent
versions of Boost.
Severity is wishlist since Debian are stuck with Boost 1.62.

Regards
Graham
Description: Make minieigen more compliant with user defined data types
 Remove std::abs from code, use Eigen::NumTraits instead of
 boost::is_complex to check if data type is complex
Origin: upstream, https://github.com/eudoxos/minieigen/commit/7bd0a2e82477a2172b428a3801d9cae0800f
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/minieigen/+bug/1765330
Author: Jeb Collins 
Last-Update: 2016-02-17

--- a/src/visitors.hpp
+++ b/src/visitors.hpp
@@ -104,8 +104,8 @@
 	template static MatrixBaseT __div__scalar(const MatrixBaseT& a, const Scalar2& scalar){ return a/scalar; }
 	template static MatrixBaseT __idiv__scalar(MatrixBaseT& a, const Scalar2& scalar){ a/=scalar; return a; }
 
-	template static	void visit_reductions_noncomplex(PyClass& cl, typename boost::enable_if >::type* dummy = 0){ /* do nothing*/ }
-	template static	void visit_reductions_noncomplex(PyClass& cl, typename boost::disable_if >::type* dummy = 0){
+	template static	void visit_reductions_noncomplex(PyClass& cl, typename boost::enable_if_c::IsComplex >::type* dummy = 0){ /* do nothing*/ }
+	template static	void visit_reductions_noncomplex(PyClass& cl, typename boost::disable_if_c::IsComplex >::type* dummy = 0){
 		// must be wrapped since there are overloads:
 		//   maxCoeff(), maxCoeff(IndexType*), maxCoeff(IndexType*,IndexType*)
 		cl
@@ -118,8 +118,8 @@
 
 	// we want to keep -0 (rather than replacing it by 0), but that does not work for complex numbers
 	// hence two versions
-	template static bool prune_element(const Scalar& num, RealScalar absTol, typename boost::disable_if >::type* dummy=0){ return std::abs(num)<=absTol || num!=-0; }
-	template static bool prune_element(const Scalar& num, RealScalar absTol, typename boost::enable_if >::type* dummy=0){ return std::abs(num)<=absTol; }
+	template static bool prune_element(const Scalar& num, RealScalar absTol, typename boost::disable_if_c::IsComplex >::type* dummy=0){using namespace std; return abs(num)<=absTol || num!=-0; }
+	template static bool prune_element(const Scalar& num, RealScalar absTol, typename boost::enable_if_c::IsComplex >::type* dummy=0){using namespace std; return abs(num)<=absTol; }
 	
 	static MatrixBaseT pruned(const MatrixBaseT& a, double absTol=1e-6){ // typename MatrixBaseT::Scalar absTol=1e-6){
 		MatrixBaseT ret(MatrixBaseT::Zero(a.rows(),a.cols()));
@@ -358,9 +358,9 @@
 		visit_if_decompositions_meaningful(cl);
 	}
 	// for complex numbers, do nothing
-	template static	void visit_if_decompositions_meaningful(PyClass& cl, typename boost::enable_if >::type* dummy = 0){ /* do nothing */ }
+	template static	void visit_if_decompositions_meaningful(PyClass& cl, typename boost::enable_if_c::IsComplex >::type* dummy = 0){ /* do nothing */ }
 	// for non-complex numbers, define decompositions
-	template static	void visit_if_decompositions_meaningful(PyClass& cl, typename boost::disable_if >::type* dummy = 0){
+	template static	void visit_if_decompositions_meaningful(PyClass& cl, typename boost::disable_if_c::IsComplex >::type* dummy = 0){
 		cl
 		.def("jacobiSVD",::jacobiSVD,"Compute SVD decomposition of square matrix, retuns (U,S,V) such that self=U*S*V.transpose()")
 		.def("svd",::jacobiSVD,"Alias for :obj:`jacobiSVD`.")
--- End Message ---
--- Begin Message ---
Source: minieigen
Source-Version: 0.50.3+dfsg1-6

We believe that the bug you reported is fixed in the latest version of
minieigen, 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 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated minieigen package)

(This message was generated automatically at their request; if you
believe that there is 

Bug#913599: Bug #913599 in ceph marked as pending

[Gaudenz Steinlin]

Control: tag -1 pending

Hello,

Bug #913599 in ceph 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/ceph-team/ceph/commit/d17fa35130e4716fd2a9351c69a0d79f133044bc


Use -mfloat-abi=softfp on armel for NEON instructions

There was already a patch to do the same for Jewel, but it got removed
when the build system changed to cmake because it patched an autotools
file which was no longer present. This adds the same logic to the new
cmake based build system.

Closes: #913599



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/913599

Processed: Bug #913599 in ceph marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #913599 [src:ceph] ceph: FTBFS on armel: #error "NEON intrinsics not 
available with the soft-float ABI.  Please use -mfloat-abi=softfp or 
-mfloat-abi=hard"
Added tag(s) pending.

-- 
913599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#914052: marked as done (uhd FTBFS with boost 1.67)

[Debian Bug Tracking System]

Your message dated Tue, 20 Nov 2018 21:22:15 +
with message-id 
and subject line Bug#914052: fixed in uhd 3.13.0.2-4
has caused the Debian Bug report #914052,
regarding uhd FTBFS with boost 1.67
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.)


-- 
914052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914052
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uhd
Version: 3.13.0.2-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=uhd=sid

...
-- Configuring LibUHD - Python API support...
--   Dependency ENABLE_LIBUHD = ON
--   Dependency BOOST_PYTHON_FOUND = 
--   Dependency HAVE_PYTHON_MODULE_NUMPY = TRUE
--   Dependency PythonLibs_FOUND = TRUE
CMake Error at cmake/Modules/UHDComponent.cmake:56 (MESSAGE):
  Dependencies for required component LibUHD - Python API not met.
Call Stack (most recent call first):
  CMakeLists.txt:430 (LIBUHD_REGISTER_COMPONENT)


-- Configuring incomplete, errors occurred!
--- End Message ---
--- Begin Message ---
Source: uhd
Source-Version: 3.13.0.2-4

We believe that the bug you reported is fixed in the latest version of
uhd, 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 914...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated uhd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 19 Nov 2018 19:17:58 -0500
Source: uhd
Binary: uhd-host libuhd3.13.0 libuhd-dev python3-uhd
Architecture: source
Version: 3.13.0.2-4
Distribution: unstable
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Description:
 libuhd-dev - universal hardware driver for Ettus Research products - headers
 libuhd3.13.0 - universal hardware driver for Ettus Research products - library
 python3-uhd - universal hardware driver for Ettus Research products - Python3
 uhd-host   - universal hardware driver for Ettus Research products - host apps
Closes: 914052
Changes:
 uhd (3.13.0.2-4) unstable; urgency=medium
 .
   * Fix build for default Python3 version and Boost Python components
 (Closes: #914052)
Checksums-Sha1:
 b66ac9e07136ef20845b7dbf7913f0c2c43e8217 2795 uhd_3.13.0.2-4.dsc
 1ddc01e4fde4d94031334420b25ff5fd2a0887cd 674476 uhd_3.13.0.2-4.debian.tar.xz
 30cb3c2f9eecda11e9c07c228547e492caedafd8 15356 uhd_3.13.0.2-4_amd64.buildinfo
Checksums-Sha256:
 35b64985d184d141a6fa7d1dab2633946e643e97083680bf8f64387d83d83f02 2795 
uhd_3.13.0.2-4.dsc
 ba6cbd9a0fa761a9dbb026916c7f1f2c7f0bc06b5cb89cd9b6d1d392111f1de2 674476 
uhd_3.13.0.2-4.debian.tar.xz
 d813b96e7eb92d535c8cbd703416de0d75f96e8bd997ea0785754a96d999648f 15356 
uhd_3.13.0.2-4_amd64.buildinfo
Files:
 73ff68e07ef76c46b02e9bc87c9a69bf 2795 science optional uhd_3.13.0.2-4.dsc
 a6899a2728e5491f03821f30b72fd2fc 674476 science optional 
uhd_3.13.0.2-4.debian.tar.xz
 c8552b5af29a880c668fae69361f69c3 15356 science optional 
uhd_3.13.0.2-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAlv0dBkACgkQUEHxiR9E
4JDKmA//Tp+FLMd7s+Jd+uEpMqc+GfKo2zGTpziY/ca5+PlB/W13xC3ETlNl3PGo
wMU2TSx7OgS2a8zUpkPzscQ2gbKFn2JNyK1msL12yuWwEEsKJ3l4xnZHhibqvNHf
mSJvKSX95IE4VYMPZoSLnYegIKTtu3Jhus6pGZnG6FLSJhrc7B7H29Y8t0wI/ErS
VqDWyAvd/EIsrGwKq8/kQK+V9mg3LBrbID3789m6FIPjbPd4fOrjj8nnacaSkYJ6
Lchi+9BEoyBmcWi4tMcVVoqkvdECB5Mj1dKWYOV1b1SVBxBZH6uBEqr7kAqwAHNF
+f2msr8wF3dPxGzAlzP6TkZt4IGVwHeBFJMOmeH+8qU4e7YsfazrzeEbX0c2yfY3
+sDWHNIBygQLDuykFCUXm8AiUhq0P7IraC8j+zkjXrpXO6dR7uItcvUUaOf4+8Hv
+0qWKEGtJvx7oO45PpkZx58dllEVCvsOrgm9E+wxU1EFY20NuZun1RM5Yhn9eUxj
l0L28nHAXws2CZ9wfe4FsPfWXIf3bZzRhnExz/412iNIBlmRLYa41dcvmh4u5Lhl
z5tymhorjmhSNkzf7bKGusekqfMl9XenQ+IP4I7kuUUcSQzeX/POG9xrnlYb4r41
lLo1dkiNMSsQ7/jW5n1AnfglHLytZ4O0L30IaopQgMVrq+Eu45A=
=XiZg
-END PGP SIGNATURE End Message ---

Processed: tagging 913404

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 913404 + fixed-upstream
Bug #913404 [src:ruby-curb] ruby-curb FTBFS with curl 7.62.0
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
913404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#899547: marked as done (ibus-sunpinyin: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Tue, 20 Nov 2018 21:20:18 +
with message-id 
and subject line Bug#899547: fixed in ibus-sunpinyin 2.0.3+git20181120-1
has caused the Debian Bug report #899547,
regarding ibus-sunpinyin: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
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.)


-- 
899547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ibus-sunpinyin
Version: 2.0.3-5
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of ibus-sunpinyin,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package ibus-sunpinyin since the list address
pkg-ime-de...@lists.alioth.debian.org used in the Maintainer: field was
not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  <https://wiki.debian.org/Alioth/MailingListContinuation>

* More options, even if imperfect, can be found at
  <https://wiki.debian.org/Salsa/AliothMigration#Import_mailing_list>


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-ime-de...@lists.alioth.debian.org is 68.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ibus-sunpinyin
Source-Version: 2.0.3+git20181120-1

We believe that the bug you reported is fixed in the latest version of
ibus-sunpinyin, 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 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated ibus-sunpinyin package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 20 Nov 2018 15:38:43 -0500
Source: ibus-sunpinyin
Binary: ibus-sunpinyin
Architecture: source
Version: 2.0.3+git20181120-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Description:
 ibus-sunpinyin - sunpinyin engine for ibus
Closes: 769560 883154 883309 885307 899547
Changes:
 ibus-sunpinyin (2.0.3+git20181120-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream git snapshot 20181120. (Closes: #883309)
 + Initially keep complete compatibility with python3 and
   gir1.2-ibus-1.0. (Closes: #769560)
   * debian: Apply "wrap-and-sort -abst".
   * debian/control:
 + Update maintainer and use Debian Input Method Team email address.
   (Closes: #899547)
 + Update uploaders' email addresses and use @debian.org ones.
 + Update Vcs-* fields and use git repo under Salsa Debian Input
   Method Team group.
 + Update homepage and use GitHub project.
 + Bump Standards-Version to 4.2.1.
 + Bump debhelper compat to v11.
 + Update dependencies and use the python3 toolchain.
   (Closes: #883154, #885307)
   * debian/rules:
 + Enable full hardenin

Bug#914245: h5py: FTBFS against hdf5 1.10.4 now in unstable

[Gilles Filippini]

Source: h5py
Version: 2.8.0-1
Severity: serious
Tags: patch
Justification: FTBFS

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

h5py FTBFS against hdf5 1.10.4 now transitioning into unstable:
==
ERROR: test_force_swmr_mode_on_raises 
(h5py.tests.hl.test_dataset_swmr.TestDatasetSwmrRead)
Verify when reading a file cannot be forcibly switched to swmr mode.
- --
Traceback (most recent call last):
  File "h5py/tests/hl/test_dataset_swmr.py", line 75, in 
test_force_swmr_mode_on_raises
self.f.swmr_mode = True
  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
  File "h5py/_hl/files.py", line 268, in swmr_mode
self.id.start_swmr_write()
  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
  File "h5py/h5f.pyx", line 510, in h5py.h5f.FileID.start_swmr_write
TypeError: Unable to convert file format (no write intent on file)

==
ERROR: test_exc (h5py.tests.old.test_group.TestLen)
len() on closed group gives ValueError
- --
Traceback (most recent call last):
  File "h5py/tests/old/test_group.py", line 302, in test_exc
len(self.f)
  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
  File "h5py/_hl/group.py", line 318, in __len__
return self.id.get_num_objs()
  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
  File "h5py/h5g.pyx", line 331, in h5py.h5g.GroupID.get_num_objs
TypeError: Not a location id (invalid object ID)

This is due to some changes introduced in hdf5 1.10.3. Please find attached
a patch backported from upstream repository.

Thanks,

_g.

- -- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAlv0eYsACgkQ7+hsbH/+
z4M1CQf/eNEpNVS++J7s9+9ydFCjv2PDDc7JOooChlJYhIfMFKe/aN6yUEWb6+qc
7bbk5Xx6oR+KU2OptDa9liUzSkvczzPB0KhGVpBOUSYKea3+g2ydCMf6m8KRJSPl
kecdlpOS+sOzzt9dxYqhzXIYk8qBduSu8eAjMx1iMYwr4HWELTm4zQ2YQXf1CGI3
bWzVI8K6iqOIQgfjpi+Jari3SWKtQ4vEHBAU50epHJsfnOibF4Fdlc5eqk76m6x7
43+LUAYJ4UAvbtXySh2g7lf/qEEcG4g3U+q0ARyJB6RwO1jXhRokoDPVYmVuiZox
7Oi9wDkmHDzhqmhg+QabZRXQZbrI4A==
=JQqV
-END PGP SIGNATURE-
diff -Nru h5py-2.8.0/debian/changelog h5py-2.8.0/debian/changelog
--- h5py-2.8.0/debian/changelog 2018-08-04 18:54:06.0 +0200
+++ h5py-2.8.0/debian/changelog 2018-10-14 22:52:25.0 +0200
@@ -1,3 +1,10 @@
+h5py (2.8.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * New patch hdf5-1.10.3-support.patch: fix FTBFS against HDF5 1.10.3
+
+ -- Gilles Filippini   Sun, 14 Oct 2018 22:52:25 +0200
+
 h5py (2.8.0-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru h5py-2.8.0/debian/patches/hdf5-1.10.3-support.patch 
h5py-2.8.0/debian/patches/hdf5-1.10.3-support.patch
--- h5py-2.8.0/debian/patches/hdf5-1.10.3-support.patch 1970-01-01 
01:00:00.0 +0100
+++ h5py-2.8.0/debian/patches/hdf5-1.10.3-support.patch 2018-10-14 
22:52:25.0 +0200
@@ -0,0 +1,32 @@
+Description: backport upstream patch to fix FTBFS against HDF5 1.10.3
+
+From 6653c65e8c8d024bbcf50315a1c5201487632322 Mon Sep 17 00:00:00 2001
+From: Thomas A Caswell 
+Date: Thu, 11 Oct 2018 23:39:29 -0400
+Subject: [PATCH] FIX: adjust mapping of hdf5 error codes -> python error codes
+
+This is to account for changes to hdf5 between 1.10.2 and 1.10.3.
+
+Closes #1088
+---
+ h5py/_errors.pyx | 7 +++
+ 1 file changed, 7 insertions(+)
+
+diff --git a/h5py/_errors.pyx b/h5py/_errors.pyx
+index 76801f4f..23849f49 100644
+--- a/h5py/_errors.pyx
 b/h5py/_errors.pyx
+@@ -73,6 +73,13 @@ _exact_table = {
+ (H5E_SYM, H5E_CANTINIT):ValueError, # Object already exists/1.8
+ (H5E_ARGS, H5E_BADTYPE):ValueError, # Invalid location in file
+ (H5E_REFERENCE, H5E_CANTINIT):  ValueError, # Dereferencing invalid ref
++
++# needed for 1.10.3 to maintain compatibility with 1.10.{0,1,2}
++
++# due to changes to H5Gdeprec.c:H5Gget_num_objs
++(H5E_SYM, H5E_BADTYPE): ValueError, # Invalid location in file
++# due to changes to H5F.c:H5Fstart_swmr_write
++(H5E_FILE, H5E_CANTCONVERT):ValueError, # Invalid file format
+   }
+ 
+ cdef struct 

Bug#913909: Bug #913909 in ceph marked as pending

[Gaudenz Steinlin]

Control: tag -1 pending

Hello,

Bug #913909 in ceph 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/ceph-team/ceph/commit/d34d35f1372dea2f8cc75fdb98e0357e2c52804c


Fix build on i386

d/p/0002-core-local-array-type-conversions.patch,
d/p/0003-Core-local-statistics.patch: Cherry pick rocksdb
commits to resolve compatibility with gcc-6 on i386.

Closes: #913909



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/913909

Processed: Bug #913909 in ceph marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #913909 [src:ceph] ceph: FTBFS on i386 and mipsel (regression)
Added tag(s) pending.

-- 
913909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913909
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#892340: dvdauthor: Please use 'pkg-config' to find FreeType 2

[Marc Leeman]

Thanks,

I was planning to combine this with an update from upstream.

On Tue, Nov 20, 2018, 15:57 Reiner Herrmann  wrote:

> Control: tags -1 + patch
>
> With the attached patch pkg-config is used for locating freetype2
> instead of the deprecated freetype-config.
>
> Regards,
>   Reiner
>

Bug#914167: marked as done (fatal error: KHR/khrplatform.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 20 Nov 2018 20:47:24 +
with message-id 
and subject line Bug#914167: fixed in mesa 18.2.5-2
has caused the Debian Bug report #914167,
regarding fatal error: KHR/khrplatform.h: No such file or directory
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.)


-- 
914167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mesa-common-dev
Version: 18.2.5-1
Severity: serious
Tags: ftbfs

OpenVDB fails to build from source because of:

In file included from /usr/include/GL/gl.h:2055,
 from viewer/Font.h:40,
 from viewer/Font.cc:31:
/usr/include/GL/glext.h:467:10: fatal error: KHR/khrplatform.h: No
such file or directory
 #include 
  ^~~
compilation terminated.

ref:
https://buildd.debian.org/status/fetch.php?pkg=openvdb=amd64=5.2.0-5=154226=0

It would be nice to fix this, upstream seems to have provided a patch:

https://bugs.freedesktop.org/show_bug.cgi?id=107511
--- End Message ---
--- Begin Message ---
Source: mesa
Source-Version: 18.2.5-2

We believe that the bug you reported is fixed in the latest version of
mesa, 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 914...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Boll  (supplier of updated mesa package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 20 Nov 2018 21:20:51 +0100
Source: mesa
Binary: libxatracker2 libxatracker-dev libd3dadapter9-mesa 
libd3dadapter9-mesa-dev libgbm1 libgbm-dev libegl-mesa0 libegl1-mesa 
libegl1-mesa-dev libwayland-egl1-mesa libgles2-mesa libgles2-mesa-dev 
libglapi-mesa libglx-mesa0 libgl1-mesa-glx libgl1-mesa-dri libgl1-mesa-dev 
mesa-common-dev libosmesa6 libosmesa6-dev mesa-va-drivers mesa-vdpau-drivers 
mesa-vulkan-drivers mesa-opencl-icd
Architecture: source
Version: 18.2.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Andreas Boll 
Description:
 libd3dadapter9-mesa - state-tracker for Direct3D9
 libd3dadapter9-mesa-dev - state-tracker for Direct3D9 -- development files
 libegl-mesa0 - free implementation of the EGL API -- Mesa vendor library
 libegl1-mesa - transitional dummy package
 libegl1-mesa-dev - free implementation of the EGL API -- development files
 libgbm-dev - generic buffer management API -- development files
 libgbm1- generic buffer management API -- runtime
 libgl1-mesa-dev - free implementation of the OpenGL API -- GLX development 
files
 libgl1-mesa-dri - free implementation of the OpenGL API -- DRI modules
 libgl1-mesa-glx - transitional dummy package
 libglapi-mesa - free implementation of the GL API -- shared library
 libgles2-mesa - transitional dummy package
 libgles2-mesa-dev - free implementation of the OpenGL|ES 2.x API -- 
development files
 libglx-mesa0 - free implementation of the OpenGL API -- GLX vendor library
 libosmesa6 - Mesa Off-screen rendering extension
 libosmesa6-dev - Mesa Off-screen rendering extension -- development files
 libwayland-egl1-mesa - transitional dummy package
 libxatracker-dev - X acceleration library -- development files
 libxatracker2 - X acceleration library -- runtime
 mesa-common-dev - Developer documentation for Mesa
 mesa-opencl-icd - free implementation of the OpenCL API -- ICD runtime
 mesa-va-drivers - Mesa VA-API video acceleration drivers
 mesa-vdpau-drivers - Mesa VDPAU video acceleration drivers
 mesa-vulkan-drivers - Mesa Vulkan graphics drivers
Closes: 914167
Changes:
 mesa (18.2.5-2) unstable; urgency=medium
 .
   * Move KHR/khrplatform.h from libegl1-mesa-dev to mesa-common-dev
 because GL/glcorearb.h and GL/glext.h started to depend on this
 header too (Closes: #914167).
Checksums-Sha1:
 5cdbcd4e0f55faa6b657030dcce90d421b05b443 5088 mesa_18.2.5-2.dsc
 be98b119968d5e2e796af0f3b791e1292a774419 100957 mesa_18.2.5-2.diff.gz
Checksums-Sha256:
 9bf93fcecabcf626b62b1ed1635a3b4c10ecef45a25694f4b21d43b9239d0f71 5088 
mesa_18.2.5-2.dsc
 43fe64b9881ab112d130fd80048906be91b992173bfb288bbdc7c8de01f84646 100957 
mesa_18.2.5-2.diff.gz
Files:
 

Bug#913371: gnat-gps fails to build on 32-bit kernels, address space exhaustion.

[Nicolas Boulenguez]

Package: src:gnat-gps
Followup-For: Bug #913371

Maybe we should restrict the architecture set for this binary package?
I doubt that anyone is using a graphical IDE like gnat-gps on
armel/mips/mipsel.

On the other hand, building on all architectures improves the quality,
so I would remove failing architectures instead of providing an
explicit list.

Any better idea?

Processed: affects src:grass & src:sfcgal

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 914167 src:grass src:sfcgal
Bug #914167 [mesa-common-dev] fatal error: KHR/khrplatform.h: No such file or 
directory
Added indication that 914167 affects src:grass and src:sfcgal
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
914167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#914221: marked as done (libwxgtk3.0-dev: Broken wx-config)

[Debian Bug Tracking System]

Your message dated Tue, 20 Nov 2018 19:49:57 +
with message-id 
and subject line Bug#914086: fixed in wxwidgets3.0 3.0.4+dfsg-6
has caused the Debian Bug report #914086,
regarding libwxgtk3.0-dev: Broken wx-config
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.)


-- 
914086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwxgtk3.0-dev
Version: 3.0.4+dfsg-5
Severity: grave
Justification: renders package unusable

Dear Maintainer,

wx-config is broken. I already posted a bug report here
https://trac.wxwidgets.org/ticket/18270 , as suggested, posting it here.

   * What led up to the situation?
Upgraded libwxgtk3.0-dev on 2018-11-19

   * What exactly did you do (or not do) that was effective (or ineffective)?
Copy/Pasting wx-config from a Sid system which has not been upgraded
solves the issues

   * What was the outcome of this action?
A working wx-config

   * What outcome did you expect instead?
wx-config included in package should work

Seems to be related to : https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=914086



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libwxgtk3.0-dev depends on:
ii  libgl1-mesa-dev [libgl-dev]  18.2.5-1
ii  libglu1-mesa-dev [xlibmesa-glu-dev]  9.0.0-2.1
ii  libwxbase3.0-dev 3.0.4+dfsg-5
ii  libwxgtk3.0-0v5  3.0.4+dfsg-5
ii  wx-common3.0.4+dfsg-5
ii  wx3.0-headers3.0.4+dfsg-5

libwxgtk3.0-dev recommends no packages.

Versions of packages libwxgtk3.0-dev suggests:
ii  gettext0.19.8.1-9
pn  wx3.0-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: wxwidgets3.0
Source-Version: 3.0.4+dfsg-6

We believe that the bug you reported is fixed in the latest version of
wxwidgets3.0, 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 914...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Olly Betts  (supplier of updated wxwidgets3.0 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 21 Nov 2018 07:54:05 +1300
Source: wxwidgets3.0
Binary: libwxbase3.0-0v5 libwxbase3.0-dev libwxgtk3.0-0v5 libwxgtk3.0-dev 
libwxgtk-media3.0-0v5 libwxgtk-media3.0-dev libwxgtk3.0-gtk3-0v5 
libwxgtk3.0-gtk3-dev libwxgtk-media3.0-gtk3-0v5 libwxgtk-media3.0-gtk3-dev 
libwxgtk-webview3.0-gtk3-0v5 libwxgtk-webview3.0-gtk3-dev wx-common 
wx3.0-headers wx3.0-i18n wx3.0-examples wx3.0-doc
Architecture: source
Version: 3.0.4+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: wxWidgets Maintainers 
Changed-By: Olly Betts 
Description:
 libwxbase3.0-0v5 - wxBase library (runtime) - non-GUI support classes of 
wxWidgets t
 libwxbase3.0-dev - wxBase library (development) - non-GUI support classes of 
wxWidge
 libwxgtk-media3.0-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ media 
library runt
 libwxgtk-media3.0-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ media 
library deve
 libwxgtk-media3.0-gtk3-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 3 
media library ru
 libwxgtk-media3.0-gtk3-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 3 
media library de
 libwxgtk-webview3.0-gtk3-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 
3 webview library
 libwxgtk-webview3.0-gtk3-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 
3 webview library
 libwxgtk3.0-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ runtime)
 libwxgtk3.0-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ development)
 libwxgtk3.0-gtk3-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 3 
runtime)
 libwxgtk3.0-gtk3-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 3 
development)
 

Bug#914086: marked as done (/usr/lib/*/wx/config/*: potentially broken if built on a merged-/usr system and run on a non-merged-/usr system)

[Debian Bug Tracking System]

Your message dated Tue, 20 Nov 2018 19:49:57 +
with message-id 
and subject line Bug#914086: fixed in wxwidgets3.0 3.0.4+dfsg-6
has caused the Debian Bug report #914086,
regarding /usr/lib/*/wx/config/*: potentially broken if built on a merged-/usr 
system and run on a non-merged-/usr system
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.)


-- 
914086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wxwidgets3.0
Version: 3.0.4+dfsg-4
Severity: normal
User: m...@linux.it
Usertags: usrmerge
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Steps to reproduce:

* Have two chroots, containers or complete systems, one with merged /usr
  and one not
* Build wxwidgets3.0 on the system with merged /usr
* Install and use wxwidgets3.0 on the system without merged /usr

Expected result:

* The package is functionally equivalent to the package you'd get if it
  had been built on a system without merged /usr
* The absolute paths of standard tools in /bin or /sbin do not appear in
  the package's content as paths in /usr/bin or /usr/sbin
* Everything works as intended

Actual result:

* /usr/lib/*/wx/config/* contain EGREP="/usr/bin/grep -E"
* If those scripts invoke ${EGREP} (I assume they do, but I haven't
  actually checked) it will not work on non-merged-/usr systems, where
  /bin/grep exists but /usr/bin/grep does not

A merged-/usr system can be obtained by installing with
debootstrap >= 1.0.102 or debootstrap --merged-usr, or by installing the
usrmerge package. A non-merged-/usr system can be obtained by installing
with debootstrap --no-merged-usr (or upgrading from an older release) and
not installing usrmerge.

Recent tests on tests.reproducible-builds.org use unmerged /usr for the
first build and merged /usr for the second, as a way to detect some
issues in this class.

This bug can probably be fixed by passing EGREP="/bin/grep -E" as an
additional command-line argument when invoking configure.

smcv
--- End Message ---
--- Begin Message ---
Source: wxwidgets3.0
Source-Version: 3.0.4+dfsg-6

We believe that the bug you reported is fixed in the latest version of
wxwidgets3.0, 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 914...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Olly Betts  (supplier of updated wxwidgets3.0 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 21 Nov 2018 07:54:05 +1300
Source: wxwidgets3.0
Binary: libwxbase3.0-0v5 libwxbase3.0-dev libwxgtk3.0-0v5 libwxgtk3.0-dev 
libwxgtk-media3.0-0v5 libwxgtk-media3.0-dev libwxgtk3.0-gtk3-0v5 
libwxgtk3.0-gtk3-dev libwxgtk-media3.0-gtk3-0v5 libwxgtk-media3.0-gtk3-dev 
libwxgtk-webview3.0-gtk3-0v5 libwxgtk-webview3.0-gtk3-dev wx-common 
wx3.0-headers wx3.0-i18n wx3.0-examples wx3.0-doc
Architecture: source
Version: 3.0.4+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: wxWidgets Maintainers 
Changed-By: Olly Betts 
Description:
 libwxbase3.0-0v5 - wxBase library (runtime) - non-GUI support classes of 
wxWidgets t
 libwxbase3.0-dev - wxBase library (development) - non-GUI support classes of 
wxWidge
 libwxgtk-media3.0-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ media 
library runt
 libwxgtk-media3.0-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ media 
library deve
 libwxgtk-media3.0-gtk3-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 3 
media library ru
 libwxgtk-media3.0-gtk3-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 3 
media library de
 libwxgtk-webview3.0-gtk3-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 
3 webview library
 libwxgtk-webview3.0-gtk3-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 
3 webview library
 libwxgtk3.0-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ runtime)
 libwxgtk3.0-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ development)
 libwxgtk3.0-gtk3-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 3 
runtime)
 libwxgtk3.0-gtk3-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 3 
development)
 wx-common  - wxWidgets Cross-platform C++ GUI toolkit (common support 

Bug#887720: marked as done (libgraphicsmagick1-dev: Detect freetype2 using pkg-config)

[Debian Bug Tracking System]

Your message dated Tue, 20 Nov 2018 19:49:29 +
with message-id 
and subject line Bug#887720: fixed in graphicsmagick 1.3.31-1
has caused the Debian Bug report #887720,
regarding libgraphicsmagick1-dev: Detect freetype2 using pkg-config
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.)


-- 
887720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgraphicsmagick1-dev
Version: 1.3.27-4
Severity: important

Dear Maintainer,

The next version of libfreetype6-dev will *not* ship
the 'freetype-config' script or freetype2.m4.

Please use pkg-config to detect the freetype2 headers
and libraries instead.

Thank you



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libgraphicsmagick1-dev depends on:
ii  libbz2-dev 1.0.6-8.1
ii  libc6-dev  2.26-4
ii  libexif-dev0.6.21-4
ii  libfreetype6-dev   2.8.1-1
ii  libgraphicsmagick-q16-31.3.27-4
ii  libice-dev 2:1.0.9-2
ii  libjbig-dev2.1-3.1+b2
ii  libjpeg-dev1:1.5.2-2
ii  libjpeg62-turbo-dev [libjpeg-dev]  1:1.5.2-2+b1
ii  liblcms2-dev   2.9-1
ii  libltdl-dev2.4.6-2
ii  libpng-dev 1.6.34-1
ii  libsm-dev  2:1.2.2-1+b3
ii  libtiff-dev4.0.9-3
ii  libwebp-dev0.6.0-4
ii  libwmf-dev 0.2.8.4-12
ii  libx11-dev 2:1.6.4-3
ii  libxext-dev2:1.3.3-1+b2
ii  libxml2-dev2.9.4+dfsg1-6.1
ii  x11proto-core-dev  7.0.31-1
ii  zlib1g-dev [libz-dev]  1:1.2.8.dfsg-5

libgraphicsmagick1-dev recommends no packages.

Versions of packages libgraphicsmagick1-dev suggests:
ii  graphicsmagick  1.3.27-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: graphicsmagick
Source-Version: 1.3.31-1

We believe that the bug you reported is fixed in the latest version of
graphicsmagick, 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 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated graphicsmagick 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 20 Nov 2018 17:16:37 +
Source: graphicsmagick
Binary: graphicsmagick libgraphicsmagick-q16-3 libgraphicsmagick1-dev 
libgraphicsmagick++-q16-12 libgraphicsmagick++1-dev libgraphics-magick-perl 
graphicsmagick-imagemagick-compat graphicsmagick-libmagick-dev-compat 
graphicsmagick-dbg
Architecture: source amd64 all
Version: 1.3.31-1
Distribution: unstable
Urgency: high
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 graphicsmagick - collection of image processing tools
 graphicsmagick-dbg - format-independent image processing - debugging symbols
 graphicsmagick-imagemagick-compat - image processing tools providing 
ImageMagick interface
 graphicsmagick-libmagick-dev-compat - image processing libraries providing 
ImageMagick interface
 libgraphics-magick-perl - format-independent image processing - perl interface
 libgraphicsmagick++-q16-12 - format-independent image processing - C++ shared 
library
 libgraphicsmagick++1-dev - format-independent image processing - C++ 
development files
 libgraphicsmagick-q16-3 - format-independent image processing - C shared 
library
 libgraphicsmagick1-dev - format-independent image processing - C development 
files
Closes: 887720
Changes:
 graphicsmagick (1.3.31-1) unstable; urgency=high
 .
   * New upstream 

Processed: affects 914167

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 914167 compiz-plugins-experimental
Bug #914167 [mesa-common-dev] fatal error: KHR/khrplatform.h: No such file or 
directory
Added indication that 914167 affects compiz-plugins-experimental
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
914167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 914221 to src:wxwidgets3.0, forcibly merging 914221 914086

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 914221 src:wxwidgets3.0
Bug #914221 [libwxgtk3.0-dev] libwxgtk3.0-dev: Broken wx-config
Bug reassigned from package 'libwxgtk3.0-dev' to 'src:wxwidgets3.0'.
No longer marked as found in versions wxwidgets3.0/3.0.4+dfsg-5.
Ignoring request to alter fixed versions of bug #914221 to the same values 
previously set
> forcemerge 914221 914086
Bug #914221 [src:wxwidgets3.0] libwxgtk3.0-dev: Broken wx-config
Bug #914086 [src:wxwidgets3.0] /usr/lib/*/wx/config/*: potentially broken if 
built on a merged-/usr system and run on a non-merged-/usr system
Severity set to 'grave' from 'normal'
Bug #914221 [src:wxwidgets3.0] libwxgtk3.0-dev: Broken wx-config
Marked as found in versions wxwidgets3.0/3.0.4+dfsg-4.
Added tag(s) pending.
Merged 914086 914221
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
914086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914086
914221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: affects 914167

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 914167 + src:survex
Bug #914167 [mesa-common-dev] fatal error: KHR/khrplatform.h: No such file or 
directory
Added indication that 914167 affects src:survex
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
914167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 1 error): forcibly merging 914221 914086, tagging 914086

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 914221 914086
Bug #914221 [libwxgtk3.0-dev] libwxgtk3.0-dev: Broken wx-config
Unable to merge bugs because:
package of #914086 is 'src:wxwidgets3.0' not 'libwxgtk3.0-dev'
Failed to forcibly merge 914221: Did not alter merged bugs.

> tags 914086 + pending
Bug #914086 [src:wxwidgets3.0] /usr/lib/*/wx/config/*: potentially broken if 
built on a merged-/usr system and run on a non-merged-/usr system
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
914086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914086
914221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#914223: solr-jetty: doesn't remove records from statoverride after purge

[sergio]

Package: solr-jetty
Version: 3.6.2+dfsg-10+deb9u2
Severity: serious
Justification: Policy 10.9

solr-jetty was installed and purged from host. I'm not able to
dist-upgrade more:

dpkg: unrecoverable fatal error, aborting:
 unknown user 'jetty' in statoverride file


% dpkg -l | grep solr
% dpkg -l | grep jett
%

Bug#914221: libwxgtk3.0-dev: Broken wx-config

[Geoffrey Merck]

Package: libwxgtk3.0-dev
Version: 3.0.4+dfsg-5
Severity: grave
Justification: renders package unusable

Dear Maintainer,

wx-config is broken. I already posted a bug report here
https://trac.wxwidgets.org/ticket/18270 , as suggested, posting it here.

   * What led up to the situation?
Upgraded libwxgtk3.0-dev on 2018-11-19

   * What exactly did you do (or not do) that was effective (or ineffective)?
Copy/Pasting wx-config from a Sid system which has not been upgraded
solves the issues

   * What was the outcome of this action?
A working wx-config

   * What outcome did you expect instead?
wx-config included in package should work

Seems to be related to : https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=914086



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libwxgtk3.0-dev depends on:
ii  libgl1-mesa-dev [libgl-dev]  18.2.5-1
ii  libglu1-mesa-dev [xlibmesa-glu-dev]  9.0.0-2.1
ii  libwxbase3.0-dev 3.0.4+dfsg-5
ii  libwxgtk3.0-0v5  3.0.4+dfsg-5
ii  wx-common3.0.4+dfsg-5
ii  wx3.0-headers3.0.4+dfsg-5

libwxgtk3.0-dev recommends no packages.

Versions of packages libwxgtk3.0-dev suggests:
ii  gettext0.19.8.1-9
pn  wx3.0-doc  

-- no debconf information

Processed (with 3 errors): mariadb-server sec-update (10.1.37-0+deb9u1) uninstalls

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> default-mysql-server, mysql-server, mariadb-server-10.1 &
Unknown command or malformed arguments to command.
> mariadb-client-10.1
Unknown command or malformed arguments to command.
> Reply-To: faus...@fala.red
Unknown command or malformed arguments to command.
> severity 914172 important
Bug #914172 [mariadb-server-10.1] mariadb-server-10.1: mariadb-server 
sec-update (10.1.37-0+deb9u1) uninstalls default-mysql-server, mysql-server, 
mariadb-server-10.1 & mariadb-client-10.1
Severity set to 'important' from 'grave'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
914172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#914172: [debian-mysql] Bug#914172: Bug#914172: mariadb-server-10.1: mariadb-server sec-update (10.1.37-0+deb9u1) uninstalls default-mysql-server, mysql-server, mariadb-server-10.1 & mariadb-client

[Faustin Lammler]

Hi Jeremy, thank you for your report.

To work on this, I need to be able to reproduce it.

Are you able to provide a step-by-step procedure?

If not, dpgk -l could help to understand what apt dependencies may be
problematic. And what happened when you reinstalled mariadb. Which
command did you used, what was the output?

Olaf's guess maybe true but there can be lot's of reason why APT decided
to remove mariadb-* packages.

Finally, do you at turnkeylinux set some non default apt preferences?

Faustin

Bug#911898: aarch64

[Alyssa Rosenzweig]

On 60.3 (buster's firefox-esr), I'm also consistently observing
segfaults on startup on an aarch64 machine.


signature.asc
Description: PGP signature

Bug#914204: marked as done (buildd.debian.org: buildd chroots should not have merged /usr for now)

[Debian Bug Tracking System]

Your message dated Tue, 20 Nov 2018 17:40:25 +0100
with message-id 
and subject line Re: Bug#914204: buildd.debian.org: buildd chroots should not 
have merged /usr for now
has caused the Debian Bug report #914204,
regarding buildd.debian.org: buildd chroots should not have merged /usr for now
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.)


-- 
914204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: buildd.debian.org
Severity: serious
Tags: patch
Justification: likely to cause grave bugs in built binary packages
X-Debbugs-Cc: debian-ad...@lists.debian.org

As discussed in  and the debian-devel
thread starting at 
,
buildd chroots should not be generated with merged /usr. However, this
is now the default in stretch-backports' debootstrap.

Avoiding merged /usr for buildds mitigates a frequently-seen class of
bugs in which packages end up with wrong executable paths hard-coded,
for example /usr/bin/bash or /bin/apt-get (which would both work fine
on a merged-/usr system, but not on an unmerged-/usr system).

I attach an untested patch for the script in dsa-puppet that I think is
currently responsible for generating buildd chroots.

Several bugs involving wrong paths when a package
is built on a merged-/usr system are tracked in
.

I'm also going to propose a patch for debootstrap to make --variant=buildd
disable merged /usr by default.

smcv
--- End Message ---
--- Begin Message ---
On 11/20/18 5:25 PM, Simon McVittie wrote:
> Package: buildd.debian.org
> Severity: serious
> Tags: patch
> Justification: likely to cause grave bugs in built binary packages
> X-Debbugs-Cc: debian-ad...@lists.debian.org
> 
> As discussed in  and the debian-devel
> thread starting at 
> ,
> buildd chroots should not be generated with merged /usr. However, this
> is now the default in stretch-backports' debootstrap.
> 
> Avoiding merged /usr for buildds mitigates a frequently-seen class of
> bugs in which packages end up with wrong executable paths hard-coded,
> for example /usr/bin/bash or /bin/apt-get (which would both work fine
> on a merged-/usr system, but not on an unmerged-/usr system).
> 
> I attach an untested patch for the script in dsa-puppet that I think is
> currently responsible for generating buildd chroots.
> 
> Several bugs involving wrong paths when a package
> is built on a merged-/usr system are tracked in
> .
> 
> I'm also going to propose a patch for debootstrap to make --variant=buildd
> disable merged /usr by default.
> 

https://salsa.debian.org/dsa-team/mirror/dsa-puppet/commit/b54f52d2899c5785923c804fdfbba0782c147da4

buildds will get new tarballs tomorrow.

Thanks,
Julien--- End Message ---

Bug#913645: Oldstable also affected

[Bastian Neuburger]

Hi,

I have however not yet tested what happens if you start thunderbird 
aftter the upgrade and close it right away (i.e. not trying to sign 
anything but also not entering the master password). I will try to test 
this later but now I need a working mail client.




I also tested this variant now:

1. Have berkeley DB based profile that works fine with thunderbird 52 in 
Jessie

2. Upgrade thunderbird
3. Start thunderbird
4. Close it without doing anything (I am not prompted for the master 
password)

5. Start thunderbird again

Expected results:
Either key3.db is still there or I am getting prompted for a master 
password during step 4.


Actual results:
Everything under "Your certificates" and "People" in the Certificate 
Manager gone, all saved passwords gone.


So the problem we encountered did not only wipe private keys, but also 
certificates of other people I already corresponded with AND stored 
passwords.


How should reporting with upstream be handled? Should I take care of it 
myself or would you like to forward it?


Kind regards,

Bastian

Bug#912098: marked as done (todoman FTBFS: sqlite3.InterfaceError: Error binding parameter 13 - probably unsupported type.)

[Debian Bug Tracking System]

Your message dated Tue, 20 Nov 2018 16:37:21 +
with message-id 
and subject line Bug#912098: fixed in todoman 3.5.0-1
has caused the Debian Bug report #912098,
regarding todoman FTBFS: sqlite3.InterfaceError: Error binding parameter 13 - 
probably unsupported type.
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.)


-- 
912098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: todoman
Version: 3.4.1-1
Severity: serious
Tags: ftbfs

Some recent change in unstable makes todoman FTBFS:

https://tests.reproducible-builds.org/debian/history/todoman.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/todoman.html

...
= test session starts ==
platform linux -- Python 3.7.1rc2, pytest-3.6.4, py-1.6.0, pluggy-0.6.0
hypothesis profile 'default' -> 
database=DirectoryBasedExampleDatabase('/build/1st/todoman-3.4.1/debian/hypothesis')
rootdir: /build/1st/todoman-3.4.1, inifile: setup.cfg
plugins: cov-2.5.1, hypothesis-3.71.11
collected 176 items

tests/test_backend.py .F...  [  5%]
tests/test_cli.py .x..s. [ 35%]
...  [ 42%]
tests/test_config.py ...xx.. [ 50%]
tests/test_filtering.py ..F..[ 55%]
tests/test_formatter.py ...  [ 64%]
tests/test_main.py . [ 64%]
tests/test_model.py ss..ss   [ 84%]
tests/test_porcelain.py  [ 88%]
tests/test_ui.py ... [ 94%]
tests/test_widgets.py .  [100%]

=== FAILURES ===
___ test_vtodo_serialization ___

todo_factory = .inner at 0x7f416d253730>

def test_vtodo_serialization(todo_factory):
"""Test VTODO serialization: one field of each type."""
description = 'A tea would be nice, thanks.'
todo = todo_factory(
categories=['tea', 'drinking', 'hot'],
description=description,
due=datetime(3000, 3, 21),
priority=7,
status='IN-PROCESS',
summary='Some tea',
>   rrule='FREQ=MONTHLY',
)

tests/test_backend.py:61: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
tests/conftest.py:92: in inner
default_database.save(todo)
todoman/model.py:972: in save
todo.id = self.cache.add_vtodo(vtodo, todo.path, todo.id)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 
todo = VTODO({'SUMMARY': vText('b'Some tea''), 'PRIORITY': 7, 'SEQUENCE': 1, 
'UID': vText('b'9d51c32e08184bd2a617dbc2f51f87ad...c92d30>, 'LAST-MODIFIED': 
, 'RRULE': vRecur({'FREQ': 
['MONTHLY']})})
file_path = 
'/tmp/pytest-of-pbuilder1/pytest-0/test_vtodo_serialization0/default/9d51c32e08184bd2a617dbc2f51f8...@profitbricks-build11-amd64.ics'
id = None

def add_vtodo(self, todo, file_path, id=None):
"""
Adds a todo into the cache.

:param icalendar.Todo todo: The icalendar component object on which
"""

sql = '''
INSERT INTO todos (
{}
file_path,
uid,
summary,
due,
start,
priority,
created_at,
completed_at,
percent_complete,
dtstamp,
status,
description,
location,
categories,
sequence,
last_modified,
rrule
) VALUES ({}?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
'''

due = self._serialize_datetime(todo, 'due')
start = self._serialize_datetime(todo, 'dtstart')

if start and due:
start = None if start >= due else start

params = (
file_path,
todo.get('uid'),
todo.get('summary'),
due,
   

Bug#914204: buildd.debian.org: buildd chroots should not have merged /usr for now

[Simon McVittie]

On Tue, 20 Nov 2018 at 16:25:28 +, Simon McVittie wrote:
> I attach an untested patch for the script in dsa-puppet that I think is
> currently responsible for generating buildd chroots.

Sorry, here's the promised patch.

smcv
>From f1fa9515d6bb7d6a57a60c582b6911fd30d5e1da Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Tue, 20 Nov 2018 16:18:50 +
Subject: [PATCH] setup-dchroot: Request unmerged /usr

Merged /usr is known to cause multiple packages to be misbuilt. As long
as we support unmerged /usr for user systems, we should mitigate
this class of bugs by using unmerged-/usr chroots on official buildds,
resulting in binary packages that work equally well on merged- or
unmerged-/usr user systems.

See:

https://bugs.debian.org/913229
https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=m...@linux.it=usrmerge
thread at https://lists.debian.org/debian-devel/2018/11/msg00299.html

Signed-off-by: Simon McVittie 
---
 modules/schroot/files/setup-dchroot | 1 +
 1 file changed, 1 insertion(+)

diff --git a/modules/schroot/files/setup-dchroot b/modules/schroot/files/setup-dchroot
index c3cc504c..8a6926b3 100755
--- a/modules/schroot/files/setup-dchroot
+++ b/modules/schroot/files/setup-dchroot
@@ -352,6 +352,7 @@ debootstrap \
 --include="$include" \
 --variant=buildd \
 --arch="$arch" \
+--no-merged-usr \
 "$suite_alias" "$rootdir" "$mirror" "$script"
 echo "$tuple" > "$rootdir/etc/debian_chroot"
 echo "force-unsafe-io" > "$rootdir/etc/dpkg/dpkg.cfg.d/force-unsafe-io"
-- 
2.19.1

Bug#914204: buildd.debian.org: buildd chroots should not have merged /usr for now

[Simon McVittie]

Package: buildd.debian.org
Severity: serious
Tags: patch
Justification: likely to cause grave bugs in built binary packages
X-Debbugs-Cc: debian-ad...@lists.debian.org

As discussed in  and the debian-devel
thread starting at 
,
buildd chroots should not be generated with merged /usr. However, this
is now the default in stretch-backports' debootstrap.

Avoiding merged /usr for buildds mitigates a frequently-seen class of
bugs in which packages end up with wrong executable paths hard-coded,
for example /usr/bin/bash or /bin/apt-get (which would both work fine
on a merged-/usr system, but not on an unmerged-/usr system).

I attach an untested patch for the script in dsa-puppet that I think is
currently responsible for generating buildd chroots.

Several bugs involving wrong paths when a package
is built on a merged-/usr system are tracked in
.

I'm also going to propose a patch for debootstrap to make --variant=buildd
disable merged /usr by default.

smcv

Bug#913540: "crypto: stream: repeat IV detected" after upgrading to newest version.

[Roger Shimizu]

On Tue, Nov 13, 2018 at 11:20 PM Roger Shimizu  wrote:
>
> On Mon, Nov 12, 2018 at 11:06 AM Gong S.  wrote:
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Package: shadowsocks-libev
> > Version: 3.2.1+ds-1
> >
> > After upgrading to the latest version, any connection attempts through the 
> > proxy would be closed with:
> >  2018-11-12 09:46:44 ERROR: invalid password or cipher
> >  2018-11-12 09:46:45 ERROR: crypto: stream: repeat IV detected
> > despite the passwords are correct.
> > If I downgrade to the previous version (3.2.0+ds-5) it works as normal.
> > Config files "/etc/shadowsocks-libev/config.json:
> > {
> > "server":[REDACTED],
> > "server_port":[REDACTED],
> > "local_port":1080,
> > "password":[REDACTED],
> > "timeout":4,
> > "method":"aes-256-cfb"
> > }
>
> Thanks for your report!
>
> I think maybe it's related upstream ticket:
> - https://github.com/shadowsocks/shadowsocks-libev/issues/2215
>
> I'll try to upload a version with the patch, so you can test.

I didn't upload because I find a similar issue on upstream ticket:
- https://github.com/shadowsocks/shadowsocks-libev/issues/2217

Can you tell me your client? If it's go version, please report this
ticket to that repository.

And I'm going to lower the level of this ticket. I don't think
blocking migration to testing is necessary.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Processed: Re: libdmtx-dev: copyright file missing after upgrade (policy 12.5)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #910220 [libdmtx-dev] libdmtx-dev: copyright file missing after upgrade 
(policy 12.5)
Added tag(s) patch.

-- 
910220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#910220: libdmtx-dev: copyright file missing after upgrade (policy 12.5)

[Reiner Herrmann]

Control: tags -1 + patch

In 0.7.5-1 /usr/share/doc/libdmtx-dev has been symlinked to libdmtx0a
with "dh_installdocs --link-doc=libdmtx0a".
But according to dh_installdocs(1) this requires a "dir to symlink"
migration. As this is missing, the directory still exists after an
upgrade, but is empty.
With the attached patch, dpkg-maintscript-helper(1) is used to perform
the migration on the next upgrade.

Please make sure that the version inside the file matches before
uploading.

Kind regards,
  Reiner
diff --git a/debian/libdmtx-dev.maintscript b/debian/libdmtx-dev.maintscript
new file mode 100644
index 000..6c27f30
--- /dev/null
+++ b/debian/libdmtx-dev.maintscript
@@ -0,0 +1 @@
+dir_to_symlink/usr/share/doc/libdmtx-devlibdmtx0a0.7.5-1.1~


signature.asc
Description: PGP signature

Bug#910258: marked as done (debmake-doc parallel FTBFS)

[Debian Bug Tracking System]

Your message dated Tue, 20 Nov 2018 15:49:36 +
with message-id 
and subject line Bug#910258: fixed in debmake-doc 1.12-1
has caused the Debian Bug report #910258,
regarding debmake-doc parallel FTBFS
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.)


-- 
910258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debmake-doc
Version: 1.11-1
Severity: serious
Tags: ftbfs

debmake-doc randomly fails to build from source when performing a
parallel build (difficult to trigger). The issue lies in test case
debhello-3.0. Its Makefile says:

| all: data/hello.desktop po/ja.mo
|
| data/hello.desktop po/ja.mo:
|   $(MAKE)  -C po all

My build log has this:

| make[1]: Entering directory 
'/<>/debhello-3.0-pkg1/test/debhello-3.0'
| 
| make  -C po all
| 
| make  -C po all
| 
| make[2]: Entering directory 
'/<>/debhello-3.0-pkg1/test/debhello-3.0/po'


So making all in debhello-3.0 causes two $(MAKE) -C po all to be spawned
simultaneously. Now the po Makefile runs xgettext to update
debhello.pot.  Running two xgettext at the same time on the same output
file causes bad things to happen and the later msgmerge calls notice
that:

| msgmerge -U ja.po debhello.pot
| 
| msgmerge -U ja.po debhello.pot
| 
| debhello.pot:37: duplicate message definition...
| 
| debhello.pot:23: ...this is the location of the first definition
| 
| debhello.pot:42: duplicate message definition...
| 
| debhello.pot:28: ...this is the location of the first definition
| 
| msgmerge: found 2 fatal errors
| 
| make[2]: *** [Makefile:10: ja.po] Error 1
| 
| make[2]: Leaving directory 
'/<>/debhello-3.0-pkg1/test/debhello-3.0/po'
| 
| make[1]: *** [Makefile:6: data/hello.desktop] Error 2
| 
| make[1]: *** Waiting for unfinished jobs
| 
| debhello.pot:37: duplicate message definition...
| 
| debhello.pot:23: ...this is the location of the first definition
| 
| debhello.pot:42: duplicate message definition...
| 
| debhello.pot:28: ...this is the location of the first definition
| 
| msgmerge: found 2 fatal errors
| 
| make[2]: *** [Makefile:10: ja.po] Error 1
| 
| make[2]: Leaving directory 
'/<>/debhello-3.0-pkg1/test/debhello-3.0/po'

Helmut
--- End Message ---
--- Begin Message ---
Source: debmake-doc
Source-Version: 1.12-1

We believe that the bug you reported is fixed in the latest version of
debmake-doc, 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 910...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Osamu Aoki  (supplier of updated debmake-doc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 20 Nov 2018 23:23:44 +0900
Source: debmake-doc
Binary: debmake-doc
Architecture: source all
Version: 1.12-1
Distribution: unstable
Urgency: high
Maintainer: Osamu Aoki 
Changed-By: Osamu Aoki 
Description:
 debmake-doc - Guide for Debian Maintainers
Closes: 910258
Changes:
 debmake-doc (1.12-1) unstable; urgency=high
 .
   * Update to match recent dpkg-source behavior.
   * Fix parallel FTBFS by fixing Makefile.  Closes: #910258
   * Bump policy to 4.2.1
Checksums-Sha1:
 af9332f85c8f77b91292ba4a3b21bb434e9f34dc 2474 debmake-doc_1.12-1.dsc
 c990b0883bb98d5a8a59130c1d8d06858ffb3a26 322392 debmake-doc_1.12.orig.tar.xz
 5bc368cc233e1b0cccf3172b98b058f6d99b22c9 4408 debmake-doc_1.12-1.debian.tar.xz
 1ba17749595b16329fdf6c50c1c42c2b5d4aea12 3902448 debmake-doc_1.12-1_all.deb
 9c3ad2963d14669d1d53f665383c5fc16eeb6f16 18598 
debmake-doc_1.12-1_amd64.buildinfo
Checksums-Sha256:
 ad58f150e55779d6377d000c39f36dad84b580993be018165b111e4658838c8c 2474 
debmake-doc_1.12-1.dsc
 fc23f94db43648435f2ff8bb1bebe5ccc74484b3b7fad1f69c7b80602ed21703 322392 
debmake-doc_1.12.orig.tar.xz
 72d69ea2e513716d859589d9b9bde7511f13911174439155ef2a1c002b1d3073 4408 
debmake-doc_1.12-1.debian.tar.xz
 090764ff1033e01618f890fea2df27790d5d426da187d5f2d4eddd521dc5e40f 3902448 
debmake-doc_1.12-1_all.deb
 5dd1d5c3fe824a4cb407772407da34d88997019f350b262d4bfaeddbcb59bb06 18598 
debmake-doc_1.12-1_amd64.buildinfo
Files:
 3c1f755b6f4d69756090ec950de15fca 2474 doc optional debmake-doc_1.12-1.dsc
 

Bug#914200: tortoisehg: uninstallable with mercurial 4.8

[Julien Cristau]

Package: tortoisehg
Version: 4.7-0.1
Severity: serious

Hi,

I just uploaded mercurial 4.8 to sid, tortoisehg will be uninstallable.

Cheers,
Julien

Bug#892340: dvdauthor: Please use 'pkg-config' to find FreeType 2

[Reiner Herrmann]

Control: tags -1 + patch

With the attached patch pkg-config is used for locating freetype2
instead of the deprecated freetype-config.

Regards,
  Reiner
diff --git a/debian/control b/debian/control
index 0077b31..813c284 100644
--- a/debian/control
+++ b/debian/control
@@ -14,6 +14,7 @@ Build-Depends: debhelper (>= 10),
 libmagick++-dev,
 libpng-dev,
 libxml2-dev,
+pkg-config,
 quilt
 Standards-Version: 3.9.8
 
diff --git a/debian/patches/freetype-config.patch b/debian/patches/freetype-config.patch
new file mode 100644
index 000..e62bf41
--- /dev/null
+++ b/debian/patches/freetype-config.patch
@@ -0,0 +1,26 @@
+Author: Reiner Herrmann 
+Description: Use pkg-config for finding freetype2
+Bug-Debian: https://bugs.debian.org/892340
+
+--- a/configure.ac
 b/configure.ac
+@@ -86,18 +86,7 @@
+ AC_SUBST(FRIBIDI_CFLAGS)
+ AC_SUBST(FRIBIDI_LIBS)
+ 
+-AC_CHECK_PROGS(FREETYPECONFIG, [freetype-config])
+-if test -n "$FREETYPECONFIG"; then
+-FREETYPE_CPPFLAGS="`$FREETYPECONFIG --cflags`"
+-FREETYPE_LIBS="`$FREETYPECONFIG --libs`"
+-AC_DEFINE(HAVE_FREETYPE, 1, [Whether FreeType is available])
+-
+-ac_save_CPPFLAGS="$CPPFLAGS"
+-CPPFLAGS="$CPPFLAGS $FREETYPE_CPPFLAGS"
+-AC_CHECK_HEADERS(ft2build.h)
+-CPPFLAGS="$ac_save_CPPFLAGS"
+-fi
+-
++PKG_CHECK_MODULES([FREETYPE], [freetype2], [AC_DEFINE(HAVE_FREETYPE, 1, [Whether FreeType is available])], [:])
+ AC_SUBST(FREETYPE_CPPFLAGS)
+ AC_SUBST(FREETYPE_LIBS)
+ 
diff --git a/debian/patches/series b/debian/patches/series
index 28d4391..57ac137 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -4,3 +4,4 @@ dvdauthor.manpage.diff
 link_libm.patch
 807657.patch
 libpng16.patch
+freetype-config.patch


signature.asc
Description: PGP signature

Processed: Re: dvdauthor: Please use 'pkg-config' to find FreeType 2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #892340 [src:dvdauthor] dvdauthor: Please use 'pkg-config' to find FreeType 
2
Added tag(s) patch.

-- 
892340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#885742: linsmith: GTK+ 3 / GooCanvas port may be available upstream

[Graham Inggs]

Hi Jeremy

On 2018/11/19 14:13, Jeremy Bicha wrote:

I don't know if you saw this bug and Yavor's response at
https://bugs.debian.org/885742


Yes, I forwarded this bug to John (upstream) by email on January 4.
I didn't get a reply, but as per the discussion on sourceforge, which 
Yavor linked, John seems to be be aware.



Are you interested in talking to upstream about getting access to the
gtk3 port of linsmith?


I did send John a reminder yesterday.


linsmith is one of the last packages using libgnome in Debian and the
Debian GNOME would really like to get libgnome removed.


Is there a RFA bug for libgnome?  Perhaps someone would like to adopt it 
in order to prevent the removal of working software from Debian.


Regards
Graham

Bug#912806: redmine: Could not find public_suffix error with current testing packages

[duck]

Control: severity -1 normal
Control: tags -1 + unreproducible


Quack,

I just created a testing environment and was able to install and run 
Redmine 3.4.6-1 without any problem.

Also debCI did not either catch such problem.

ruby-public-suffix is an indirect dependency of Redmine, and in my test 
environment I also had 3.0.3+ds-1 installed. Bundler did not complain.


So I'm sorry but I was not able to reproduce your problem. Did you have 
any plugins installed?


\_o<

--
Marc Dequènes

Processed: Re: redmine: Could not find public_suffix error with current testing packages

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #912806 [redmine] redmine: Could not find public_suffix error with current 
testing packages
Severity set to 'normal' from 'grave'
> tags -1 + unreproducible
Bug #912806 [redmine] redmine: Could not find public_suffix error with current 
testing packages
Added tag(s) unreproducible.

-- 
912806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912806
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#914183: marked as done (shutter: No way to install shutter in debian buster)

[Debian Bug Tracking System]

Your message dated Tue, 20 Nov 2018 08:48:37 -0500
with message-id 

and subject line Re: Bug#914183: shutter: No way to install shutter in debian 
buster
has caused the Debian Bug report #914183,
regarding shutter: No way to install shutter in debian buster
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.)


-- 
914183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: shutter
Version: 0.93.1-1.3
Severity: critical

I can't install shutter anymore in debian buster because some of lack of
some dependances.

Thanks.

Ludo



-- System Information:
Debian Release: buster/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (200, 'unstable'), 
(150, 'stable'), (100, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.18.0-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages shutter depends on:
ii  imagemagick8:6.9.10.14+dfsg-7
ii  imagemagick-6.q16 [imagemagick]8:6.9.10.14+dfsg-7
ii  libfile-basedir-perl   0.08-1
pn  libfile-copy-recursive-perl
ii  libfile-which-perl 1.22-1
ii  libglib-perl   3:1.328-1+b1
pn  libgnome2-canvas-perl  
pn  libgnome2-gconf-perl   
pn  libgnome2-perl 
pn  libgnome2-vfs-perl 
pn  libgnome2-wnck-perl
pn  libgtk2-imageview-perl 
ii  libgtk2-perl   2:1.24992-1+b2
pn  libgtk2-unique-perl
ii  libimage-magick-perl [perlmagick]  8:6.9.10.14+dfsg-7
ii  libjson-perl   2.97001-1
ii  libjson-xs-perl3.040-1+b1
ii  liblocale-gettext-perl 1.07-3+b4
ii  libnet-dbus-perl   1.1.0-5+b1
pn  libnet-dropbox-api-perl
ii  libpath-class-perl 0.37-1
pn  libproc-processtable-perl  
pn  libproc-simple-perl
ii  librsvg2-common2.44.8-3
ii  libsort-naturally-perl 1.03-2
ii  libwww-mechanize-perl  1.90-1
ii  libwww-perl6.36-1
ii  libx11-protocol-other-perl 30-1
ii  libx11-protocol-perl   0.56-7
ii  libxml-simple-perl 2.25-1
ii  perlmagick 8:6.9.10.14+dfsg-7
ii  procps 2:3.3.15-2
ii  xdg-utils  1.1.3-1

Versions of packages shutter recommends:
pn  libgoo-canvas-perl 
pn  libgtk2-appindicator-perl  

Versions of packages shutter suggests:
ii  gnome-web-photo 0.10.6-1+b1
ii  libimage-exiftool-perl  11.16-1
ii  libnet-dbus-glib-perl   0.33.0-3+b1
ii  nautilus-sendto 3.8.6-2
--- End Message ---
--- Begin Message ---
Control: severity -1 wishlist
Control: tag -1 + wontfix
X-Debbugs-CC: ludovic+deb...@heureux-cyclage.org

Hi Ludovic!

Ludovic CHEVALIER  于2018年11月20日周二 上午4:15写道：
>
> Package: shutter
> Version: 0.93.1-1.3
> Severity: critical
>
> I can't install shutter anymore in debian buster because some of lack of
> some dependances.

Unfortunately Debian has decided to remove shutter from next stable
release (Debian 10, Buster)
completely. Please check out the news page about such decision:

https://tracker.debian.org/news/994228/removed-094-1-from-unstable/

The reason was that shutter was using some extremely outdated perl
libraries with no security
support. We have already informed upstream about such decision months
ago when the removal
took place. Once shutter has migrated away from outdated perl
dependencies, developers in Debian
would be delighted to reintroduce shutter again later.

As a result, you will not be able to install shutter directly without
some degree of hacking (which
is still extremely discouraged since those dependency used are really
unmaintained). You are
recommended to migrate to some new screenshot tools with better
upstream support.

You are welcomed to contact us later when shutter has migrated away
from gnome2-perl library.

--
Thanks,
Boyuan Yang--- End Message ---

Bug#911696: marked as done (profitbricks-sdk-python FTBFS: flake8 fails)

[Debian Bug Tracking System]

Your message dated Tue, 20 Nov 2018 13:36:16 +
with message-id 
and subject line Bug#911696: fixed in profitbricks-sdk-python 4.1.3-2
has caused the Debian Bug report #911696,
regarding profitbricks-sdk-python FTBFS: flake8 fails
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.)


-- 
911696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: profitbricks-sdk-python
Version: 4.1.3-1
Severity: serious
Tags: ftbfs

profitbricks-sdk-python fails to build from source in unstable:

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/profitbricks-sdk-python_4.1.3-1.rbuild.log.gz

|debian/rules override_dh_auto_test
| make[1]: Entering directory '/build/1st/profitbricks-sdk-python-4.1.3'
| python3 -m flake8 --max-line-length=99 examples profitbricks tests setup.py
| profitbricks/client.py:69:12: W605 invalid escape sequence '\d'
| make[1]: *** [debian/rules:12: override_dh_auto_test] Error 1
| make[1]: Leaving directory '/build/1st/profitbricks-sdk-python-4.1.3'
| make: *** [debian/rules:7: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut
--- End Message ---
--- Begin Message ---
Source: profitbricks-sdk-python
Source-Version: 4.1.3-2

We believe that the bug you reported is fixed in the latest version of
profitbricks-sdk-python, 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 911...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated 
profitbricks-sdk-python package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 20 Nov 2018 13:13:28 +0100
Source: profitbricks-sdk-python
Binary: python-profitbricks python3-profitbricks profitbricks-api-tools
Architecture: source
Version: 4.1.3-2
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Drung 
Changed-By: Benjamin Drung 
Description:
 profitbricks-api-tools - command line tools that use the public API from 
ProfitBricks
 python-profitbricks - ProfitBricks REST API client library for Python 2
 python3-profitbricks - ProfitBricks REST API client library for Python 3
Closes: 911696
Changes:
 profitbricks-sdk-python (4.1.3-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Remove ancient X-Python-Version field
 .
   [ Benjamin Drung ]
   * Bump Standards-Version to 4.2.1 (no changes needed)
   * Fix anomalous backslash in string (Closes: #911696)
   * Update debhelper to version 11
Checksums-Sha1:
 a75d2a97a90fbe7139308e6ee9f0699ad07fcb74 2319 
profitbricks-sdk-python_4.1.3-2.dsc
 645d8800f435268d8e79366af71281aed86a7f79 3800 
profitbricks-sdk-python_4.1.3-2.debian.tar.xz
 76ba49be3ebf7c2632e573171a9d0ea54e97be0f 8862 
profitbricks-sdk-python_4.1.3-2_source.buildinfo
Checksums-Sha256:
 e424b1ce41d857b0f71f6093d681c2c950b6267bc6aa6d017d09230db5aa9720 2319 
profitbricks-sdk-python_4.1.3-2.dsc
 9b0dc3013164a3c352073cae209fecdd90acabeb2c3e13c3afd188020368ce69 3800 
profitbricks-sdk-python_4.1.3-2.debian.tar.xz
 ac1d02f7904e7025c81c1a68e1e9d7769539d22cefd487d410f3acf54834752c 8862 
profitbricks-sdk-python_4.1.3-2_source.buildinfo
Files:
 5bbc5748f1ff55e263035b79f1464fc2 2319 python optional 
profitbricks-sdk-python_4.1.3-2.dsc
 b330faabaa5ea66bdf17710ac2cec98a 3800 python optional 
profitbricks-sdk-python_4.1.3-2.debian.tar.xz
 c66019d27c72734d0a6bdc0849047147 8862 python optional 
profitbricks-sdk-python_4.1.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE5/q3CzlQJ15towl13YzVpd6MfnoFAlvz+z8ACgkQ3YzVpd6M
fnqh1w//XUJyXzVlAXzpOkVEtAi1SXLq4fFpImy9PFOGGYNUpGH7Hk1RC/RamDhZ
yq5+SKaP0iwM/akckl0calh0iOpp3ALzCG9Gb0nWJy2w+o25L9GMkRED6aPQKT0H
VJO7E4XyQKq7Iuww+Z8Vwc3dmAppXK3NZcQ0SfBhYJBM2T/xyPvmUWqhI/pAc/TA
jpaldWNsyABEfuyQe3WGiCpvafr22itXzENY/ynklHXvW48amZZZI1Udqsw7gEgm
aAJhyL3sK8ePXcT81xFNGQgryiEj9VcIYsPqBVvlkSXanJMCO5UhWVNEfejIMan3
jte6oLnC7LX2k8s1lq98i//Jtvxs2ABGFH4jUnvzQZAQu68wKT5hyKyL59xVbQiR
pqK5teSFRkYn4zhATwot1cGoKyJdi1sDJsaWuZDXwumYwkt9eYT8cCHWR5h7r2Dq
4oMKhLGogORoGIFiVz0glLssayhZOUgd/4ml3bhj9P+nNJ8WdRA7mrwm2e0XWe4M

Bug#912782: marked as done (s-tui package misses dependency on python3-pkg-resources)

[Debian Bug Tracking System]

Your message dated Tue, 20 Nov 2018 12:12:51 +
with message-id 
and subject line Bug#912782: fixed in s-tui 0.8.2-2
has caused the Debian Bug report #912782,
regarding s-tui package misses dependency on python3-pkg-resources
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.)


-- 
912782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912782
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: s-tui
Version: 0.8.2-1
Severity: important


Dear Maintainer,

$ s-tui
Traceback (most recent call last):
  File "/usr/bin/s-tui", line 6, in 
from pkg_resources import load_entry_point
ModuleNotFoundError: No module named 'pkg_resources'
$

Installing python3-pkg-resources (that accidently happened when I
installed reportbug!), made s-tui work.


Thanks.



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-2-amd64 (SMP w/32 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages s-tui depends on:
ii  python33.6.7-1
ii  python3-distutils  3.7.1-1
ii  python3-psutil 5.4.6-1+b1
ii  python3-urwid  2.0.1-2+b1

s-tui recommends no packages.

s-tui suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: s-tui
Source-Version: 0.8.2-2

We believe that the bug you reported is fixed in the latest version of
s-tui, 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 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonathan Carter  (supplier of updated s-tui package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 20 Nov 2018 13:36:36 +0200
Source: s-tui
Binary: s-tui
Architecture: source all
Version: 0.8.2-2
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Carter 
Changed-By: Jonathan Carter 
Description:
 s-tui  - terminal UI for monitoring your computer
Closes: 912782
Changes:
 s-tui (0.8.2-2) unstable; urgency=medium
 .
   * Add dependency: python3-pkg-resources (Closes: #912782)
   * Run wrap-and-sort
Checksums-Sha1:
 ec9a9b0f7c27cf8e47fc88b5109349e62bc32c80 1880 s-tui_0.8.2-2.dsc
 dff4ef373df931401f58be2cbf0e125bdfb9cfd3 2828 s-tui_0.8.2-2.debian.tar.xz
 d356c93671a7a4ab9c3db062dbf251bc54ab2931 32132 s-tui_0.8.2-2_all.deb
 8a5f030663b1d1a36a7888eb6b4c5905eadfc98d 5866 s-tui_0.8.2-2_amd64.buildinfo
Checksums-Sha256:
 fae7fc3b71bcf33a50f160ec3aeacee5c040dc5cc9c7fceacc06bd5e63a16522 1880 
s-tui_0.8.2-2.dsc
 2f9e863c82758a5ec2d168cb0c69fcc729efd1099a9d03f18251371630c2e50f 2828 
s-tui_0.8.2-2.debian.tar.xz
 6749b4b496140e51ebfaac1377e1bb3e2250f6db99825793a03bb799a31dde96 32132 
s-tui_0.8.2-2_all.deb
 af233409418c479f1a16f0d7bb1dcc2322d5dd6175297df38f6bda6fe490b771 5866 
s-tui_0.8.2-2_amd64.buildinfo
Files:
 37db4951646439c27f9cf91b4f0dc550 1880 utils optional s-tui_0.8.2-2.dsc
 0c4af4da3959957b95212bfb1c5b20ef 2828 utils optional 
s-tui_0.8.2-2.debian.tar.xz
 8686a12b0f422272d58235e11497ee81 32132 utils optional s-tui_0.8.2-2_all.deb
 eb34442a4c0d8d06d7265f1123032f45 5866 utils optional 
s-tui_0.8.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAlvz8rQPHGpjY0BkZWJp
YW4ub3JnAAoJELAdGnKsjcmhV14P/0JHaT15cWep2cqYraHTWO1GGwaSL7xGS+1t
JD7XJMmvqmcJSVqFFQl5KrUE0GqynYtlpSMvO9PGhbRQrUKPHrC04S8DQN6CQlNW
aNelScZfmSMzeD0J26I+AP12YeDEa69AB0z3jRWhVJsajUwjceKKpA2npSFmZsLb
t3U4yjaLmv40sndD+Tl0YaF65jL5/uAxsr1u+Sb9shFQpN4JVeJ2woF9+WfzNtsf
2DF5dWIhiwnqy8BoxDLbg7a6eSAN9g2woV75ROTy3RbgyiaKaNIiIFRce1RUNtL7
TwiH8l5qxIn9FBmKCBSIgNBSN7TalEYdFNUmKoPU+HgjQv3yIVihRAkWtqmwWEvL
BB/b8dDysJtxFc/tsH3X6wqcefaRU+6WSWDVhIrsqNRLAqkmaYdZ90ycmWQmDnas
9ODyhuSenl38VVhKp0Las0CtB/513rE0lsaEPwJTiyaIxtJi/xNBPZsLM3Fay8Tm
AlcGxJxh4bfg90Sm/izwwCbtrpeSsl072yrxLfKw2VlHpaigSQ4yEDm4OdKIYlow
zn7Xtw1yCDBxFmjiyXpFaUe1GAbUMFff2azXzfBB7OH/HLW78L7D8aN32yfbsLhz
N1it1WGe9yABl+yppwEAXyDVGZvKBu4gopPiP4rFsM6wyiq+atU001AMJgRdqVH+
di74j/rd

Processed: affects 914167

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 914167 src:gr-fosphor src:ember
Bug #914167 [mesa-common-dev] fatal error: KHR/khrplatform.h: No such file or 
directory
Added indication that 914167 affects src:gr-fosphor and src:ember
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
914167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#913814: marked as done (iptables fails to upgrade: ln: failed to create symbolic link '/sbin/iptables': File exists)

[Debian Bug Tracking System]

Your message dated Tue, 20 Nov 2018 10:37:08 +
with message-id 
and subject line Bug#913811: fixed in iptables 1.8.2-2
has caused the Debian Bug report #913811,
regarding iptables fails to upgrade: ln: failed to create symbolic link 
'/sbin/iptables': File exists
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.)


-- 
913811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iptables
Version: 1.8.2-1
Severity: serious

...
Preparing to unpack .../01-iptables_1.8.2-1_amd64.deb ...
Unpacking iptables (1.8.2-1) over (1.8.1-2) ...
...
ln: failed to create symbolic link '/sbin/iptables': File exists
dpkg: error processing package iptables (--configure):
 installed iptables package post-installation script subprocess returned error 
exit status 1


$ ls -la /sbin/iptables
lrwxrwxrwx 1 root root 18 Oct 26 00:47 /sbin/iptables -> /usr/sbin/iptables
$ 
--- End Message ---
--- Begin Message ---
Source: iptables
Source-Version: 1.8.2-2

We believe that the bug you reported is fixed in the latest version of
iptables, 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 913...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Arturo Borrero Gonzalez  (supplier of updated iptables 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 20 Nov 2018 10:54:37 +0100
Source: iptables
Binary: iptables iptables-dev libxtables12 libxtables-dev libiptc0 libiptc-dev 
libip4tc0 libip4tc-dev libip6tc0 libip6tc-dev
Architecture: source
Version: 1.8.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Netfilter Packaging Team 

Changed-By: Arturo Borrero Gonzalez 
Description:
 iptables   - administration tools for packet filtering and NAT
 iptables-dev - transitional dummy package
 libip4tc-dev - Development files for libip4tc
 libip4tc0  - netfilter libip4tc library
 libip6tc-dev - Development files for libip6tc
 libip6tc0  - netfilter libip6tc library
 libiptc-dev - Development files for libiptc
 libiptc0   - netfilter libiptc library
 libxtables-dev - netfilter xtables library -- development files
 libxtables12 - netfilter xtables library
Closes: 913811
Changes:
 iptables (1.8.2-2) unstable; urgency=medium
 .
   * [fb09c23] iptables: fixes for /sbin symlinks (Closes: #913811)
   * [60b3924] d/t/control: disable tests for ip[6]tables-restore-translate
   * [8f93912] iptables.prerm: change cleanup order
Checksums-Sha1:
 9eb3dddccb2a1aad82e07839b10ae4e367dd4962 2699 iptables_1.8.2-2.dsc
 b42b1a2fba17bc57f2aaed576bc410fa9f605437 64416 iptables_1.8.2-2.debian.tar.xz
 765cde48e1295e5e78f0c5cbdc9296e5f7789649 9034 iptables_1.8.2-2_amd64.buildinfo
Checksums-Sha256:
 bd3f2be471e2c01917e361eeef8f27773b08130928cacd4caea09dba9c83814c 2699 
iptables_1.8.2-2.dsc
 2c4815c2ad95652814420babed801cf3298409cfcd35e419b957f6e78764d2c5 64416 
iptables_1.8.2-2.debian.tar.xz
 bbf6364d91ad912bde5c0c4a8ef980a4eb24f6154e5255a366cc8e6c2b86ab49 9034 
iptables_1.8.2-2_amd64.buildinfo
Files:
 7c236501a7350942ad20015dfb57d87f 2699 net important iptables_1.8.2-2.dsc
 d0b419b74288936434a4be3af756ebce 64416 net important 
iptables_1.8.2-2.debian.tar.xz
 e325abc8462ce252784ae381d9ee4f7f 9034 net important 
iptables_1.8.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE3ZhhqyPcMzOJLgepaOcTmB0VFfgFAlvz2p4ACgkQaOcTmB0V
FfgWTQ//bDUEVfc9zSsyEe61M3swrocH1iS5BPHtxzkP0UGxoEPPzbBviaW7tMB8
rgZX7uQ7H0qhv2DJBnor38G9zGUZr9S9oNohcpF0Ko9h6qST2QpXU3tM9GIZwpCf
Q/YfVM9L4euR5gtmegerAilb773LqRWK5Emomur85UxzP5S8sGmEniQr/kQhdJat
YArk/4CZBsAf4NU7CdHelFt4yNprm5yhqziiilQ7nKJgKLGNklmhQvEl032Ty45+
AUw3xpCgkphwqVjHR3yVDLZbE1vn7rFA9MdnvST5FFSg/mq1Six8M9i6Kc7v7mBC
AQo5GC20PgwYedyDsl+WPjtgL4R/WKgLYP7R5XnmQpikY49gS2sD7rak38mJpUV1
nybLgDqwxhE+XJpv4LKQctq+XHTb6abPY2+r8F3cf6XQhj/CLXpwRvgQNW/TDprt
5HESrEYu2fB6v/ofhKyeDiWrf1IOHspi3Iws6GOdRn4lO8Gk5r2Xm/IhJXv3aUf4
fJg1qjfSnGCEMbi1uz0fWq8TK9NkEaOhVLXEoaWjEZ22vLcyIlYLzhZYNgdnP98e
8sUrM/gMqwQYRc2JZx5tL5oxwrmqjA6qqwlGBBxb3O77SDDrzDSOjiaK1XkSH4C1
Ap1c/YnXlYNrxlqcTAS7yANSEqiYRUjfuhLO7AWSJjONGzr+vmU=
=3XPE
-END PGP SIGNATURE End Message ---

Bug#913811: marked as done (iptables fails to upgrade from 1.8.1-2 to 1.8.2-1)

[Debian Bug Tracking System]

Your message dated Tue, 20 Nov 2018 10:37:08 +
with message-id 
and subject line Bug#913811: fixed in iptables 1.8.2-2
has caused the Debian Bug report #913811,
regarding iptables fails to upgrade from 1.8.1-2 to 1.8.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.)


-- 
913811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iptables
Version: 1.8.2-1
Severity: important

Dear Maintainer,

During an upgrade from 1.8.1-2 to 1.8.2-1 I got the following error:

Setting up iptables (1.8.2-1) ...
ln: failed to create symbolic link '/sbin/iptables': File exists
dpkg: error processing package iptables (--configure):
 installed iptables package post-installation script subprocess returned error 
exit status 1
Errors were encountered while processing:
 iptables
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

Downgrading the package back to 1.8.1-2 fixed it. Manually deleting the
files from /sbin also allows the 1.8.2-1 package to install.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-2-amd64 (SMP w/2 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: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages iptables depends on:
ii  libc62.27-8
ii  libip4tc01.8.2-1
ii  libip6tc01.8.2-1
ii  libiptc0 1.8.2-1
ii  libmnl0  1.0.4-2
ii  libnetfilter-conntrack3  1.0.7-1
ii  libnfnetlink01.0.1-3+b1
ii  libnftnl71.1.1-1
ii  libxtables12 1.8.2-1

iptables recommends no packages.

Versions of packages iptables suggests:
ii  kmod  25-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: iptables
Source-Version: 1.8.2-2

We believe that the bug you reported is fixed in the latest version of
iptables, 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 913...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Arturo Borrero Gonzalez  (supplier of updated iptables 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 20 Nov 2018 10:54:37 +0100
Source: iptables
Binary: iptables iptables-dev libxtables12 libxtables-dev libiptc0 libiptc-dev 
libip4tc0 libip4tc-dev libip6tc0 libip6tc-dev
Architecture: source
Version: 1.8.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Netfilter Packaging Team 

Changed-By: Arturo Borrero Gonzalez 
Description:
 iptables   - administration tools for packet filtering and NAT
 iptables-dev - transitional dummy package
 libip4tc-dev - Development files for libip4tc
 libip4tc0  - netfilter libip4tc library
 libip6tc-dev - Development files for libip6tc
 libip6tc0  - netfilter libip6tc library
 libiptc-dev - Development files for libiptc
 libiptc0   - netfilter libiptc library
 libxtables-dev - netfilter xtables library -- development files
 libxtables12 - netfilter xtables library
Closes: 913811
Changes:
 iptables (1.8.2-2) unstable; urgency=medium
 .
   * [fb09c23] iptables: fixes for /sbin symlinks (Closes: #913811)
   * [60b3924] d/t/control: disable tests for ip[6]tables-restore-translate
   * [8f93912] iptables.prerm: change cleanup order
Checksums-Sha1:
 9eb3dddccb2a1aad82e07839b10ae4e367dd4962 2699 iptables_1.8.2-2.dsc
 b42b1a2fba17bc57f2aaed576bc410fa9f605437 64416 iptables_1.8.2-2.debian.tar.xz
 765cde48e1295e5e78f0c5cbdc9296e5f7789649 9034 iptables_1.8.2-2_amd64.buildinfo
Checksums-Sha256:
 bd3f2be471e2c01917e361eeef8f27773b08130928cacd4caea09dba9c83814c 2699 
iptables_1.8.2-2.dsc
 2c4815c2ad95652814420babed801cf3298409cfcd35e419b957f6e78764d2c5 64416 
iptables_1.8.2-2.debian.tar.xz
 bbf6364d91ad912bde5c0c4a8ef980a4eb24f6154e5255a366cc8e6c2b86ab49 9034 
iptables_1.8.2-2_amd64.buildinfo
Files:
 7c236501a7350942ad20015dfb57d87f 2699 net important iptables_1.8.2-2.dsc
 

Bug#914143: Bug #914143 in soundscaperenderer marked as pending

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

Bug #914143 in soundscaperenderer reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/multimedia-team/soundscaperenderer/commit/69f27df56c9dce916019b5f934c535e36a64d53e


Don't build  Qt-packages on armel/armhf

Closes: #914143



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/914143

Processed: Bug #914143 in soundscaperenderer marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #914143 [src:soundscaperenderer] soundscaperenderer FTBFS on armel/armhf
Added tag(s) pending.

-- 
914143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#914189: postgresql-hll is not ready for 32bit systems

[Matthias Klose]

Package: src:postgresql-hll
Version: 2.12-1
Severity: serious
Tags: sid buster

According to https://github.com/citusdata/postgresql-hll/pull/57 the package is
not ready for 32bit systems. So maybe better limit the build to 64bit archs?

Unrelated issue: is the package working on big endian archs? Asking because of
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/s390x/p/postgresql-hll/20181112_020516_e6dfd@/log.gz

Processed: Re: Bug#913005: ruby-rack: CVE-2018-16471: Possible XSS vulnerability in Rack

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 913005 by 914184
Bug #913005 [src:ruby-rack] ruby-rack: CVE-2018-16471: Possible XSS 
vulnerability in Rack
913005 was not blocked by any bugs.
913005 was not blocking any bugs.
Added blocking bug(s) of 913005: 914184
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
913005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#913005: ruby-rack: CVE-2018-16471: Possible XSS vulnerability in Rack

[Chris Lamb]

block 913005 by 914184
thanks

Hi Salvatore,

> I think those will be no-dsa and can be adressed via a point release

Thanks, filed as: #914184.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#913005: Bug #913005 in ruby-rack marked as pending

[Chris Lamb]

Control: tag -1 pending

Hello,

Bug #913005 in ruby-rack reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/ruby-team/ruby-rack/commit/5a3262e2fd00cbc92a11f1a7a75fc63f97cf3a87


CVE-2018-16471: Prevent a possible XSS vulnerability where a malicious request 
could impact the HTTP/HTTPS scheme returned to the underlying application. 
(Closes: #913005)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/913005

Processed: Bug #913005 in ruby-rack marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #913005 [src:ruby-rack] ruby-rack: CVE-2018-16471: Possible XSS 
vulnerability in Rack
Added tag(s) pending.

-- 
913005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#914183: shutter: No way to install shutter in debian buster

[Ludovic CHEVALIER]

Package: shutter
Version: 0.93.1-1.3
Severity: critical

I can't install shutter anymore in debian buster because some of lack of
some dependances.

Thanks.

Ludo



-- System Information:
Debian Release: buster/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (200, 'unstable'), 
(150, 'stable'), (100, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.18.0-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages shutter depends on:
ii  imagemagick8:6.9.10.14+dfsg-7
ii  imagemagick-6.q16 [imagemagick]8:6.9.10.14+dfsg-7
ii  libfile-basedir-perl   0.08-1
pn  libfile-copy-recursive-perl
ii  libfile-which-perl 1.22-1
ii  libglib-perl   3:1.328-1+b1
pn  libgnome2-canvas-perl  
pn  libgnome2-gconf-perl   
pn  libgnome2-perl 
pn  libgnome2-vfs-perl 
pn  libgnome2-wnck-perl
pn  libgtk2-imageview-perl 
ii  libgtk2-perl   2:1.24992-1+b2
pn  libgtk2-unique-perl
ii  libimage-magick-perl [perlmagick]  8:6.9.10.14+dfsg-7
ii  libjson-perl   2.97001-1
ii  libjson-xs-perl3.040-1+b1
ii  liblocale-gettext-perl 1.07-3+b4
ii  libnet-dbus-perl   1.1.0-5+b1
pn  libnet-dropbox-api-perl
ii  libpath-class-perl 0.37-1
pn  libproc-processtable-perl  
pn  libproc-simple-perl
ii  librsvg2-common2.44.8-3
ii  libsort-naturally-perl 1.03-2
ii  libwww-mechanize-perl  1.90-1
ii  libwww-perl6.36-1
ii  libx11-protocol-other-perl 30-1
ii  libx11-protocol-perl   0.56-7
ii  libxml-simple-perl 2.25-1
ii  perlmagick 8:6.9.10.14+dfsg-7
ii  procps 2:3.3.15-2
ii  xdg-utils  1.1.3-1

Versions of packages shutter recommends:
pn  libgoo-canvas-perl 
pn  libgtk2-appindicator-perl  

Versions of packages shutter suggests:
ii  gnome-web-photo 0.10.6-1+b1
ii  libimage-exiftool-perl  11.16-1
ii  libnet-dbus-glib-perl   0.33.0-3+b1
ii  nautilus-sendto 3.8.6-2

Processed: severity of 907118 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 907118 important
Bug #907118 [bip] error:141a318a:ssl routines:tls_process_ske_dhe:dh key too 
small
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
907118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#907118: error:141a318a:ssl routines:tls_process_ske_dhe:dh key too small

[duck]

Control: -1 severity important


Quack,

This problem is solved in unstable and should not prevent this package 
from entering testing.


\_o<

--
Marc Dequènes

Bug#914140: pytango FTBFS with boost 1.67

[PICCA Frederic-Emmanuel]

Hello Adrian

If I look at the current boost1.67, I find this in the 
boost python package

https://packages.debian.org/sid/amd64/libboost-python1.67.0/filelist

and

https://packages.debian.org/sid/amd64/libboost-python1.67-dev/filelist

We can find these

/usr/lib/x86_64-linux-gnu/libboost_python3-py36.a
/usr/lib/x86_64-linux-gnu/libboost_python3-py36.so

but only for the python3.6 version and not for 2.7 and 3.7

previously we had for boost 1.62

https://packages.debian.org/sid/amd64/libboost-python1.62-dev/filelist

all python version  add these -pyXY.so files.

Is it an intended change in the new boost_python package, or a mistake ?

This logic -pyXY was  coded in the pytango setup.py, in order to deal with 
boost_python.

cheers

Fred

Processed: Bug #913600 in ceph marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #913600 [src:ceph] ceph: bd-uninst on several architectures: 
libboost-context1.67-dev not available
Ignoring request to alter tags of bug #913600 to the same tags previously set

-- 
913600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#913600: Bug #913600 in ceph marked as pending

[Gaudenz Steinlin]

Control: tag -1 pending

Hello,

Bug #913600 in ceph 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/ceph-team/ceph/commit/0a7cbd593bf5f246577197535c3febc1cea05259


Disable libboost-context on unsupported archs

Only a limited set of architectures supports libboost-context and
libboost-coroutine. This limits the use of these libraries to supported
architectures. Disabling libboost-context also disables the RADOS GW
Beast frontend.

Closes: #913600



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/913600

Bug#914167: fatal error: KHR/khrplatform.h: No such file or directory

[Sven Joachim]

On 2018-11-20 09:19 +0200, Timo Aaltonen wrote:

> On 20.11.2018 9.04, Mathieu Malaterre wrote:
>> Package: mesa-common-dev
>> Version: 18.2.5-1
>> Severity: serious
>> Tags: ftbfs
>> 
>> OpenVDB fails to build from source because of:
>> 
>> In file included from /usr/include/GL/gl.h:2055,
>>  from viewer/Font.h:40,
>>  from viewer/Font.cc:31:
>> /usr/include/GL/glext.h:467:10: fatal error: KHR/khrplatform.h: No
>> such file or directory
>>  #include 
>>   ^~~
>> compilation terminated.
>> 
>> ref:
>> https://buildd.debian.org/status/fetch.php?pkg=openvdb=amd64=5.2.0-5=154226=0
>> 
>> It would be nice to fix this, upstream seems to have provided a patch:
>> 
>> https://bugs.freedesktop.org/show_bug.cgi?id=107511
>
> That commit is in 18.2.5:
>
> commit 2645ea5817f4fd05905b8deda96c268cd69fa48c
> Author: Eric Engestrom 
> Date:   Tue Aug 7 12:56:25 2018 +0100
>
> configure: install KHR/khrplatform.h when needed
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107511
> Fixes: f7d42ee7d319256608ad "include: update GL & GLES headers (v2)"
> Signed-off-by: Eric Engestrom 
> Tested-by: Brad King 
> Reviewed-by: Emil Velikov 
> (cherry picked from commit 87c156183cd668f1341326cc7c88ab6686f27d8f)
>
> so something else is wrong.

KHR/khrplatform.h is installed, but into libegl1-mesa-dev, on which
mesa-common-dev does not currently depend.

Cheers,
   Sven

Bug#914177: libplexus-utils2-java: Provides: libplexus-utils-java must be versioned

[Adrian Bunk]

Package: libplexus-utils2-java
Version: 3.1.0-1
Severity: serious
Control: affects -1 src:maven-filtering

maven-filtering build depends on libplexus-utils-java (>= 1.5.15).

Please change the Provides to
  Provides: libplexus-utils-java (= 1:1.5.15-5)

Processed: libplexus-utils2-java: Provides: libplexus-utils-java must be versioned

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:maven-filtering
Bug #914177 [libplexus-utils2-java] libplexus-utils2-java: Provides: 
libplexus-utils-java must be versioned
Added indication that 914177 affects src:maven-filtering

-- 
914177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#914175: lightning is not installable after binNMUs

[Adrian Bunk]

Package: lightning
Version: 1:60.3.0-1
Severity: serious

 thunderbird : Breaks: lightning (< 1:60.3.0-1+b1) but 1:60.3.0-1 is to be 
installed

lightning is binary-all, ${source:Version} should be used
for Breaks and Recommends.