Processed: fixed 849832 in thunderbird/1:52.5.0-1

[Debian Bug Tracking System]

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

> fixed 849832 thunderbird/1:52.5.0-1
Bug #849832 [icedove] firefox: contains JSHint work under non-free licence
Marked as fixed in versions thunderbird/1:52.5.0-1.
> thanks
Stopping processing here.

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

Bug#880347: marked as done (bioperl-run: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Fri, 08 Dec 2017 07:19:26 +
with message-id 
and subject line Bug#880347: fixed in bioperl-run 1.7.2-2
has caused the Debian Bug report #880347,
regarding bioperl-run: FTBFS: Test failures
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.)


-- 
880347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bioperl-run
Version: 1.7.2-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20171030 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> ok 9 # skip Required executable for Bio::Tools::Run::tRNAscanSE is not present
> ok 10 # skip Required executable for Bio::Tools::Run::tRNAscanSE is not 
> present
> ok 11 # skip Required executable for Bio::Tools::Run::tRNAscanSE is not 
> present
> ok 12 # skip Required executable for Bio::Tools::Run::tRNAscanSE is not 
> present
> ok
> 
> Test Summary Report
> ---
> t/Bowtie.t  (Wstat: 512 Tests: 61 Failed: 2)
>   Failed tests:  43, 45
>   Non-zero exit status: 2
> Files=72, Tests=1690, 156 wallclock secs ( 0.24 usr  0.07 sys + 133.72 cusr  
> 6.41 csys = 140.44 CPU)
> Result: FAIL
> Failed 1/72 test programs. 2/1690 subtests failed.
> dh_auto_test: perl Build test --verbose 1 returned exit code 255
> debian/rules:32: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/10/30/bioperl-run_1.7.2-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: bioperl-run
Source-Version: 1.7.2-2

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

Debian distribution maintenance software
pp.
Alexandre Mestiashvili  (supplier of updated 
bioperl-run package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 07 Dec 2017 18:19:04 +0100
Source: bioperl-run
Binary: bioperl-run libbio-perl-run-perl
Architecture: source
Version: 1.7.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Alexandre Mestiashvili 
Description:
 bioperl-run - BioPerl wrappers: scripts
 libbio-perl-run-perl - BioPerl wrappers: modules
Closes: 880347
Changes:
 bioperl-run (1.7.2-2) unstable; urgency=medium
 .
   * Team upload
   * Add adjust_bowtie_tests.patch fixing failing tests for Bowtie
 Closes: #880347
   * Bump Standards-Version to 4.1.2, apply cme fix dpkg
Checksums-Sha1:
 c56c5afbc27c1b9d4b1bfb427791f310101840c1 2564 bioperl-run_1.7.2-2.dsc
 3949b1ebd6dc617c69244fe7b814c692440af721 14880 
bioperl-run_1.7.2-2.debian.tar.xz
 0d2b919ba6dd3b3f69a79bfb48d349d51494e991 10644 
bioperl-run_1.7.2-2_amd64.buildinfo
Checksums-Sha256:
 db21e187c2307789194d7975a7d366e784954a8b7ebe5cc4df9ca1f1bef6c7a0 2564 
bioperl-run_1.7.2-2.dsc
 1697075f16e6f40ec5551e428202598bdbf34c4806826e50d21d39e08a248a30 14880 
bioperl-run_1.7.2-2.debian.tar.xz
 28e9cb1e4a92fbef534c7d28ad146eaa65f8718441e28906c6feea6e23f8179a 10644 
bioperl-run_1.7.2-2_amd64.buildinfo
Files:
 4c40c2aca4891ac09dc33cd342f0b07e 2564 science optional bioperl-run_1.7.2-2.dsc
 4358cbfb04923a76d10e329ff5af98ce 14880 science optional 
bioperl-run_1.7.2-2.debian.tar.xz
 98bd301dd34ce21933b928765477318d 10644 science optional 
bioperl-run_1.7.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAloqOpcRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHxww/8C0l4NueLQlvGPh8ALGRzYwTKRM4CsXEe
GIqtVK8AGUyq9xBzFBs5LwpsZ2ftrCC4bU/ryOogtR7uvqbHQsb6K6G/UNfXonE2
YxC4v/TPq78au0FUw+gSZ9XRTKhraWVbF48yfVNG+BpeiBB4YlNfej1AxZVzHbNU
Rf3avMbz

Bug#883833: e17: FTBFS if $HOME is not writable

[Andreas Metzler]

Control: tags -1 patch

On 2017-12-08 Andreas Beckmann  wrote:
> Source: e17
> Version: 0.22.1-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)

> e17 FTBFS if $HOME is not existent (and therefore not writable) as
> enforced by current pbuilder.
> See also Policy 9.2.3.

> From the attached log:

> FATAL: Cannot create run dir '/nonexistent/.run' - errno=2

edje_cc seems to need a writeable ~/.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
>From 68546024af75578f47e42236077792ec33eb8646 Mon Sep 17 00:00:00 2001
From: Andreas Metzler 
Date: Fri, 8 Dec 2017 08:03:54 +0100
Subject: [PATCH] Fix FTBFS with HOME="/nonexistent".

Copy fake_home.sh from efl and run dh_auto_build under it. edje_cc needs a
writeable HOME. Closes: #883833
---
 debian/changelog|  7 +++
 debian/fake_home.sh | 15 +++
 debian/rules|  4 
 3 files changed, 26 insertions(+)
 create mode 100755 debian/fake_home.sh

diff --git a/debian/changelog b/debian/changelog
index 316806a9f..6f1bee871 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+e17 (0.22.1-2) UNRELEASED; urgency=medium
+
+  * Copy fake_home.sh from efl and run dh_auto_build under it. edje_cc needs a
+writeable HOME. Closes: #883833
+
+ -- Andreas Metzler   Fri, 08 Dec 2017 08:01:08 +0100
+
 e17 (0.22.1-1) experimental; urgency=medium
 
   * New upstream release
diff --git a/debian/fake_home.sh b/debian/fake_home.sh
new file mode 100755
index 0..2902878e1
--- /dev/null
+++ b/debian/fake_home.sh
@@ -0,0 +1,15 @@
+#!/bin/sh
+
+cleanup () {
+[ -n "$temp_HOME" ] && rm -r "$temp_HOME"
+[ -n "$temp_XDG_RUNTIME_DIR" ] && rm -r "$temp_XDG_RUNTIME_DIR"
+}
+
+trap cleanup EXIT
+
+temp_HOME=$(mktemp -d)
+temp_XDG_RUNTIME_DIR=$(mktemp -d)
+
+env HOME="$temp_HOME" \
+XDG_RUNTIME_DIR="$temp_XDG_RUNTIME_DIR" \
+$*
diff --git a/debian/rules b/debian/rules
index eafe076d0..de55ca691 100755
--- a/debian/rules
+++ b/debian/rules
@@ -11,6 +11,10 @@ ARCH_PATH=$(DEB_HOST_GNU_SYSTEM)-$(DEB_HOST_GNU_CPU)-$(RELEASE)
 override_dh_auto_configure:
 	dh_auto_configure --verbose
 
+override_dh_auto_build:
+	$(CURDIR)/debian/fake_home.sh \
+		dh_auto_build -O--buildsystem=meson --verbose
+
 override_dh_lintian:
 	sed -e "s/MULTIARCH/$(DEB_TARGET_MULTIARCH)/" \
 		-e "s/ARCH_PATH/$(ARCH_PATH)/" \
-- 
2.15.0

Processed: Re: Bug#883833: e17: FTBFS if $HOME is not writable

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #883833 [src:e17] e17: FTBFS if $HOME is not writable
Added tag(s) patch.

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

Processed: tagging 880842, found 880842 in 0.4.1-1, tagging 821577, found 880869 in 0.9.900-2 ...

[Debian Bug Tracking System]

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

> tags 880842 + experimental
Bug #880842 [src:gnome-twitch] gnome-twitch FTBFS with meson 0.43.0: Invalid 
kwargs for option "use-deprecated-webkit": "descritpion"
Added tag(s) experimental.
> found 880842 0.4.1-1
Bug #880842 [src:gnome-twitch] gnome-twitch FTBFS with meson 0.43.0: Invalid 
kwargs for option "use-deprecated-webkit": "descritpion"
Marked as found in versions gnome-twitch/0.4.1-1.
> tags 821577 + experimental
Bug #821577 [php-google-api-php-client] php-google-api-php-client: PHP 7.0 
Transition
Added tag(s) experimental.
> found 880869 0.9.900-2
Bug #880869 {Done: Stephen Kitt } [src:libratbag] libratbag 
FTBFS with meson 0.43.0: Invalid kwargs for option "udev-dir": "default"
Marked as found in versions libratbag/0.9.900-2 and reopened.
> found 882643 1:3.4.7-1
Bug #882643 [src:mongodb] mongodb FTBFS with glibc 2.25
Marked as found in versions mongodb/1:3.4.7-1.
> thanks
Stopping processing here.

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

Bug#883731: audacious: Debian packaging has incorrect license

[Nicholas D Steeves]

Dear Debian Legal Team,

I've CCed you for my reply to this bug, because I don't have the
experience to be able to tell if Debian implicitly relicensed
Audacious as GPL-3 from 2012-2016, how potentially falling out of
BSD-2-clause license compliance might have affected this, and also how
this should be resolved.  The Debian packaging is GPL-2+, so it's
possible to move to copyright-format/1.0 if that would simplify
things.  Also, please reply to point 2. OTTO "ancient plugins...under
different licenses.  I assume audacious-plugins will also need a
copyright review.  Please CC John and I, Bug #883731, and
debian-legal as appropriate.


Hi John,

On Thu, Dec 07, 2017 at 05:15:53PM -0500, John Lindgren wrote:
> Hi Nicholas,
> 
> > On this topic, would you please update contrib/audacious.appdata.xml
> > to reflect the current Audacious license (GPL3)? It claims the
> > project_license is BSD-2-Clause.
> 
> Sorry if my initial email was unclear.  The current Audacious license *is*
> BSD 2-clause, with some exceptions:

Oh, now I see.  Sorry I wasn't familiar with Audacious' upstream
relicensing, and thank you very much for confirming for the files I
asked about.

> 1. The embedded copy of libguess (which is an external project) is under
>a BSD 3-clause license, with a separate copyright.  I believe this is
>not a problem so long as the libguess license is also included with
>any distribution.
> 2. Some of the more ancient plugins are under different licenses, including
>GPLv2+ and GPLv3.  When we relicensed the main parts of Audacious to BSD
>around 2012, we thought it impractical to contact all of the original
>plugin authors since some of them go back to XMMS days (20 years ago now).
>The plugins are compiled as separate binaries, and Debian has them in a
>separate package (audacious-plugins).
> 
> Our upstream COPYING file makes note of these exceptions, which is one
> reason why it's important for it to be included verbatim, and not replaced
> with generic BSD 2-clause text as it is in the current Debian package.

Both BSD 3-clause and BSD 2-clause allow relicensing as GPL, thus so
long as the licensing terms are complied with correctly BSD code can
perpetually and unidirectionally flow to GPL projects.  So from what I
can tell it's 100% ok for the Debian package (both src and bin) to be
GPL-3 from 2012-to-2016, and both the Debian source packages and
binaries from this time period might actually be implicitly relicensed
as GPL-3.  If so, that's history that can't be changed.  Also, I'm not
sure what debian-legal and ftpmaster's view of #2 will be in light of
the relicensing (and possible implied relicensing back to GPL-3).

On 2016-04-06 06:55:52
(commit@124bf3bdccdac9d0eb78ce65b53c9a4ba128e052)
use-system-licenses.patch might have made Debian's implicit
relicensing invalid, not because of the deduplication patch per-se,
but because /usr/share/common-licenses/BSD is a 3-clause and not a
2-clause one like Audacious uses.  It's the same style, but is a
different license altogether...and yeah, I think one can go
BSD-2-clause to BSD-3-clause to GPL-3, but only if the original
BSD-2-clause bits aren't stripped.  I'm also unsure whether the patch
that changes the user-visible bits and the out-of-date
debian/copyright outweigh the 2-clause license that wasn't stripped
from the headers of various files.  eg: not implicitly relicensed, and
just out of date copyright plus non-compliance with 2-clause BSD.

> Regarding the plugins, I don't know the state of debian/copyright in the
> audacious-plugins package, but my main concern here is that the one in
> audacious is correct.
>
> > Conversely, what I found in debian/copyright was a project license of
> > GPL-3, with notable exceptions. eg: are really translations GPL-1+?
> 
> As I said, debian/copyright is out-of-date.  We relicensed the project
> from GPLv3 to BSD 2-clause back in 2012.  Possibly we didn't make an
> obvious enough announcement back then for Debian to take notice.

I haven't looked at audacious-plugins yet either.  Re: "is correct", I
agree, and I'm hoping the fix will be to simply synchronise with
upstream Audacious' BSD 2-clause.

> Translations are under the same license as the rest of Audacious.

Thank you for the confirmation.

> > To my eyes it looks like the upstream project license needs to be
> > clarified and disambiguated, debian/copyright needs work, and finally
> > that deduplication patch can be dropped.
> 
> Let me know if you think there are still clarifications needed upstream
> given the information I've provided here.  I'd be happy to adjust things
> as necessary.

Well, since the main Audacious project is in fact 2-clause-BSD this
is much clearer now!  Thanks again for the help.  I hope to work on
this Sunday, or after we hear back from debian-legal.

Sincerely,
Nicholas


signature.asc
Description: PGP signature

Bug#883615: Info received (CINDY,your recent order06053711)

[Cindy Fisher]

Hello,

I DID NOT order anything from you or this company and have no idea what
order you are referencing about Bug-tracking systems. Please confirm the
receipt of this email as well as the fact that I have No orders with your
company. Otherwise, I will report you for fraud!

Cindy Fisher

wyr...@gmail.com Email


Notice:
This message and any included attachments are intended only for the use of
the addressee, and may contain information that is privileged or
Confidential. If you are not the intended recipient, you are hereby
notified that any dissemination, distribution or copying of this
communication is strictly prohibited.


On Wed, Dec 6, 2017 at 11:00 AM, Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian NVIDIA Maintainers 
>
> If you wish to submit further information on this problem, please
> send it to 883...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 883615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883615
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#880231: marked as done (ubuntu-dev-tools: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Fri, 08 Dec 2017 03:09:36 +
with message-id 
and subject line Bug#868820: fixed in pylint 1.7.4-1
has caused the Debian Bug report #868820,
regarding ubuntu-dev-tools: FTBFS: dh_auto_test: pybuild --test -i 
python{version} -p 3.6 returned exit code 13
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
868820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ubuntu-dev-tools
Version: 0.161
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20171030 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2,python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.6 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools
> copying ubuntutools/subprocess.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools
> copying ubuntutools/rdepends.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools
> copying ubuntutools/question.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools
> copying ubuntutools/config.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools
> copying ubuntutools/misc.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools
> copying ubuntutools/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools
> copying ubuntutools/logger.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools
> copying ubuntutools/archive.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools
> copying ubuntutools/version.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools
> copying ubuntutools/update_maintainer.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools
> copying ubuntutools/builder.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools
> creating /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/lp
> copying ubuntutools/lp/udtexceptions.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/lp
> copying ubuntutools/lp/lpapicache.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/lp
> copying ubuntutools/lp/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/lp
> copying ubuntutools/lp/libsupport.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/lp
> creating /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/requestsync
> copying ubuntutools/requestsync/mail.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/requestsync
> copying ubuntutools/requestsync/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/requestsync
> copying ubuntutools/requestsync/lp.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/requestsync
> creating 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/sponsor_patch
> copying ubuntutools/sponsor_patch/patch.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/sponsor_patch
> copying ubuntutools/sponsor_patch/question.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/sponsor_patch
> copying ubuntutools/sponsor_patch/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/sponsor_patch
> copying ubuntutools/sponsor_patch/source_package.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/sponsor_patch
> copying ubuntutools/sponsor_patch/bugtask.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/sponsor_patch
> copying ubuntutools/sponsor_patch/sponsor_patch.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/sponsor_patch
> creating /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/test
> copying ubuntutools/test/test_help.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/test
> copying ubuntutools/test/test_archive.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/test
> copying ubuntutools/test/test_pylint.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/test
> copying ubuntutools/test/test_update_maintainer.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/test
> copying ubuntutools/test/test_config.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/test
> copying ubuntutools/test/example_package.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/test
> copying ubuntutools/test/test_flake8.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/ubuntutools/test
> copying ubuntutools/test

Bug#868820: marked as done (pylint: update to 1.7.2)

[Debian Bug Tracking System]

Your message dated Fri, 08 Dec 2017 03:09:36 +
with message-id 
and subject line Bug#868820: fixed in pylint 1.7.4-1
has caused the Debian Bug report #868820,
regarding pylint: update to 1.7.2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
868820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pylint
Severity: normal
Tags: patch
User: debian-pyt...@lists.debian.org
Usertags: python3.6

Dear Maintainer,

pylint needs an update in preparation for python 3.6. I don't have a potted
test case unfortunately (the closest I have is "make python 3.6 the default and
try to rebuild ubuntu-dev-tools"). The update is mostly straightforward but
some dependencies need to be added manually because dh-python does not (yet?)
parse environment-based conditional dependencies. I'm attaching the patch I put
on top of what git-dpm import-new-upstream --rebase ../pylint_1.7.2.orig.tar.gz
did by itself.

Cheers,
mwh


-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (400, 'xenial-proposed'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-83-generic (SMP w/4 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Index: debian/changelog
===
--- debian/changelog	(revision 14202)
+++ debian/changelog	(working copy)
@@ -1,3 +1,11 @@
+pylint (1.7.2-1) UNRELEASED; urgency=medium
+
+  * New upstream release.
+  * debian/control
+- Manually add dependencies missed by dh-python thanks to bug #834133
+
+ -- Michael Hudson-Doyle   Wed, 12 Jul 2017 09:44:37 +1200
+
 pylint (1.6.5-1) unstable; urgency=medium
 
   * New upstream release
Index: debian/control
===
--- debian/control	(revision 14202)
+++ debian/control	(working copy)
@@ -4,7 +4,7 @@
 Maintainer: Sandro Tosi 
 Uploaders: Python Applications Packaging Team 
 Build-Depends: debhelper (>= 9), python-all (>= 2.6.6-3~), python3-all, dh-python
-Build-Depends-Indep: python-astroid (>= 1.4.1), python3-astroid (>= 1.4.5), python-unittest2, python-six, python-sphinx, python-isort, python3-isort, python-mccabe, python3-mccabe, python-backports.functools-lru-cache
+Build-Depends-Indep: python-astroid (>= 1.4.1), python3-astroid (>= 1.4.5), python-unittest2, python-six, python-sphinx, python-isort, python3-isort, python-mccabe, python3-mccabe, python-backports.functools-lru-cache, python-configparser, python-singledispatch, python-setuptools, python3-setuptools
 Standards-Version: 3.9.8
 Homepage: http://www.pylint.org/
 Vcs-Svn: svn://anonscm.debian.org/python-apps/packages/pylint/trunk/
@@ -12,7 +12,7 @@
 
 Package: pylint
 Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}, python-astroid (>= 1.4.5), python-six, python-isort, python-backports.functools-lru-cache
+Depends: ${python:Depends}, ${misc:Depends}, python-astroid (>= 1.4.5), python-six, python-isort, python-backports.functools-lru-cache, python-configparser, python-singledispatch
 Recommends: python-tk
 Suggests: pylint-doc, python-mccabe
 Description: Python code static checker and UML diagram generator
--- End Message ---
--- Begin Message ---
Source: pylint
Source-Version: 1.7.4-1

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated pylint package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 07 Dec 2017 21:23:07 -0500
Source: pylint
Binary: pylint pylint-doc pylint3
Architecture: source all
Version: 1.7.4-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Description:
 pylint - Python code static checker and UML diagram generator
 pylint-doc 

Bug#883835: analitza: FTBFS Could not find a package configuration file provided by "Qt5LinguistTools"

[Andreas Beckmann]

Source: analitza
Version: 4:17.08.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

analitza/experimental recently started to FTBFS, probably related to
some changes in Qt5 in sid/experimental.

 debian/rules build
/usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.pl --with=kf5,pkgkde-symbolshelper 
dpkg-buildflags --export=make > debian/dhmk_env.mk
/usr/bin/make -f debian/rules dhmk_run_configure_commands 
DHMK_TARGET="configure"
make[1]: Entering directory '/build/analitza-17.08.0'
dh_testdir  
dh_auto_configure '--buildsystem=kf5' --parallel  
cd obj-x86_64-linux-gnu && cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACK
AGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DKDE_INSTALL_USE_QT_SYS_PATHS=ON
-- The C compiler identification is GNU 7.2.1
-- The CXX compiler identification is GNU 7.2.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Looking for __GLIBC__
-- Looking for __GLIBC__ - found
-- Performing Test _OFFT_IS_64BIT
-- Performing Test _OFFT_IS_64BIT - Success
-- Performing Test HAVE_DATE_TIME
-- Performing Test HAVE_DATE_TIME - Success
-- Could not set up the appstream test. appstreamcli is missing.
-- Found Eigen3: /usr/include/eigen3 (Required is at least version "2.91.0") 
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success
-- The following OPTIONAL packages have been found:

 * Eigen3

-- The following REQUIRED packages have been found:

 * ECM (required version >= 1.7.0)
 * Qt5Gui (required version >= 5.9.2)
 * Qt5Widgets
 * Qt5Xml
 * Qt5Svg
 * Qt5Test
 * Qt5Network (required version >= 5.9.2)
 * Qt5Qml
 * Qt5Quick
 * Qt5PrintSupport
 * Qt5 (required version >= 5.2)
 * Qt5Core

CMake Error at /usr/share/ECM/modules/ECMPoQmTools.cmake:144 (find_package):
  Could not find a package configuration file provided by "Qt5LinguistTools"
  with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.
Call Stack (most recent call first):
  /usr/share/ECM/modules/ECMPoQmTools.cmake:220 (ecm_process_po_files_as_qm)
  CMakeLists.txt:78 (ecm_install_po_files_as_qm)


-- Configuring incomplete, errors occurred!


Andreas


analitza_4%17.08.0-1.log.gz
Description: application/gzip

Bug#883834: kmetronome: FTBFS with latest Qt5: does not find Qt5LinguistToolsConfig.cmake

[Andreas Beckmann]

Source: kmetronome
Version: 1.0.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

kmetronome/experimental recently started to FTBFS with the current Qt5
in sid/experimental:

 debian/rules build
dh build 
   dh_update_autotools_config
   dh_auto_configure
cd obj-x86_64-linux-gnu && cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACK
AGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON
-- The C compiler identification is GNU 7.2.1
-- The CXX compiler identification is GNU 7.2.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Build configuration: None
CMake Error at CMakeLists.txt:40 (find_package):
  By not providing "FindQt5LinguistTools.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "Qt5LinguistTools", but CMake did not find one.

  Could not find a package configuration file provided by "Qt5LinguistTools"
  with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.


-- Configuring incomplete, errors occurred!


Andreas


kmetronome_1.0.0-1.log.gz
Description: application/gzip

Bug#883128: marked as done (sdpa: hard-coded dependency on scotch-5.1)

[Debian Bug Tracking System]

Your message dated Fri, 08 Dec 2017 01:34:44 +
with message-id 
and subject line Bug#883128: fixed in sdpa 7.3.11+dfsg-1
has caused the Debian Bug report #883128,
regarding sdpa: hard-coded dependency on scotch-5.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.)


-- 
883128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sdpa
Version: 7.3.10+dfsg-2
Severity: serious
Tags: patch
Justification: uninstallable
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Dear Makoto,

The sdpa package has a hard-coded dependency on libscotch-5.1, even though
it dynamically links against -lscotch at build time and gets the correct
dependency via ${shlibs:Depends}.

libscotch-5.1 has now been replaced with libscotch-6.0, which makes sdpa
uninstallable in Debian testing.

I have uploaded the attached patch to Ubuntu, which fixes this problem. 
Please consider applying it in Debian as well.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru sdpa-7.3.10+dfsg/debian/control sdpa-7.3.10+dfsg/debian/control
--- sdpa-7.3.10+dfsg/debian/control 2017-10-19 00:00:00.0 -0700
+++ sdpa-7.3.10+dfsg/debian/control 2017-11-29 16:26:27.0 -0800
@@ -11,7 +11,7 @@
 Package: sdpa
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends},
-   libopenblas-dev, libmumps-seq-5.1.1, libscotch-5.1
+   libopenblas-dev, libmumps-seq-5.1.1
 Description: High-performance package for SemiDefinite Programs
  The software SDPA (SemiDefinite Programming Algorithm) is one of the most
  efficient and stable  software packages for solving SDPs based on the
@@ -38,7 +38,7 @@
 Package: sdpam
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends},
-   libopenblas-dev, libmumps-seq-5.1.1, libscotch-5.1, 
+   libopenblas-dev, libmumps-seq-5.1.1,
octave, libsdpa-dev
 Description: Matlab/Octave interface of SDPA
  This package provides SDPA-M, Matlab/Octave interface 
--- End Message ---
--- Begin Message ---
Source: sdpa
Source-Version: 7.3.11+dfsg-1

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

Debian distribution maintenance software
pp.
Makoto Yamashita  (supplier of updated sdpa 
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: Wed, 06 Dec 2017 08:00:00 +0900
Source: sdpa
Binary: sdpa libsdpa-dev sdpam
Architecture: source amd64
Version: 7.3.11+dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Makoto Yamashita 
Changed-By: Makoto Yamashita 
Description:
 libsdpa-dev - Callable library and examples of SDPA
 sdpa   - High-performance package for SemiDefinite Programs
 sdpam  - Matlab/Octave interface of SDPA
Closes: 883128
Changes:
 sdpa (7.3.11+dfsg-1) unstable; urgency=low
 .
 * New upstream
   + Add SDPA::resetParameters() function (provided by Tristan Gally)
 * Fix debian/control (closes: #883128)
Checksums-Sha1:
 00312734e6639361ca7e5edf1c09b99116086b6e 1929 sdpa_7.3.11+dfsg-1.dsc
 5026c5ac377c16ed43d975495934d17e1149b212 237922 sdpa_7.3.11+dfsg.orig.tar.gz
 99b6a99ed2bcf55b4e35f00a58d51229aefd471e 4384 sdpa_7.3.11+dfsg-1.debian.tar.xz
 87fa42dee4e2c1586c44ff84969c06d69635b183 162040 
libsdpa-dev_7.3.11+dfsg-1_amd64.deb
 a444e609148976a838a6343aac7f1ed8aeb5bd22 658412 
sdpa-dbgsym_7.3.11+dfsg-1_amd64.deb
 f11420f3ccf92c1966e233a9144d42e24bf00a37 14376 
sdpa_7.3.11+dfsg-1_amd64.buildinfo
 93929913024d46087d091801783cc0a018bf7764 1553752 sdpa_7.3.11+dfsg-1_amd64.deb
 e619a973903ec8251a3c811027e78bae799e87cf 1337760 
sdpam-dbgsym_7.3.11+dfsg-1_amd64.deb
 75413e6c2a826d234a38e08cee25b7be6aac3638 3557332 sdpam_7.3.11+dfsg-1_amd64.deb
Checksums-Sha256:
 1a15258ac7cd736befe1752ba5698273eb558527c635b6af93a55c008e2bda65 1929 
sdpa_7.3.11+d

Bug#883833: e17: FTBFS if $HOME is not writable

[Andreas Beckmann]

Source: e17
Version: 0.22.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

e17 FTBFS if $HOME is not existent (and therefore not writable) as
enforced by current pbuilder.
See also Policy 9.2.3.

>From the attached log:

FATAL: Cannot create run dir '/nonexistent/.run' - errno=2


Andreas


e17_0.22.1-1.log.gz
Description: application/gzip

Processed: your mail

[Debian Bug Tracking System]

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

> tag 868820 + pending
Bug #868820 [src:pylint] pylint: update to 1.7.2
Bug #880231 [src:pylint] ubuntu-dev-tools: FTBFS: dh_auto_test: pybuild --test 
-i python{version} -p 3.6 returned exit code 13
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#883829: systemd: Fully qualified host names in fstab results in mounts failing

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #883829 [systemd] systemd: Fully qualified host names in fstab results in 
mounts failing
Added tag(s) moreinfo.
> severity -1 normal
Bug #883829 [systemd] systemd: Fully qualified host names in fstab results in 
mounts failing
Severity set to 'normal' from 'grave'

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

Bug#883829: systemd: Fully qualified host names in fstab results in mounts failing

[Michael Biebl]

Control: tags -1 moreinfo
Control: severity -1 normal

Am 08.12.2017 um 00:06 schrieb Duncan Hare:

> browne.danum.local:/nfsroot/b827eb/c23849/home /home   nfs defaults,rw
> 0 0 
> tmpfs/tmptmpfs   
> nodev,nosuid,size=1%,mode=1777 0 0
> 
> After the failed scenario when boot is complete, This fails after mounting 
> the home 
> directory by shell command:
> 
> sudo mkdir /abc
> sudo mount browne:/nfsroot/b827eb/c23849/home /abc
> 
> and normally this works:
>  
> sudo mkdir /abc
> sudo mount browne:/nfsroot/b827eb/c23849/home abc
> 
> and yes, my local domain suffix is .local, becuse it is a Microsoft domain.

How exactly do you configure your network (do you use ifupdown,
network-manager, something else)? Please share those exact configuration.

How exactly do you resolve those local names? Is that really a DNS or a
MDNS name? Do you have a local resolver running?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#883731: audacious: Debian packaging has incorrect license

[Debian Bug Tracking System]

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

> # License change happened in 3.3 (about 5 years ago)
> found 883731 3.3.1-1
Bug #883731 [audacious] audacious: Debian packaging has incorrect license
Marked as found in versions audacious/3.3.1-1.
> thanks
Stopping processing here.

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

Bug#882477: marked as done (python-karborclient FTBFS in C locale)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2017 22:19:04 +
with message-id 
and subject line Bug#882477: fixed in python-karborclient 0.6.0-3
has caused the Debian Bug report #882477,
regarding python-karborclient FTBFS in C locale
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.)


-- 
882477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-karborclient
Version: 0.6.0-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-karborclient.html

...
+ python3.6 setup.py install --install-layout=deb --root 
/build/1st/python-karborclient-0.6.0/debian/python3-karborclient
ERROR:root:Error parsing
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pbr/core.py", line 111, in pbr
attrs = util.cfg_to_args(path, dist.script_args)
  File "/usr/lib/python3/dist-packages/pbr/util.py", line 251, in cfg_to_args
kwargs = setup_cfg_to_setup_kwargs(config, script_args)
  File "/usr/lib/python3/dist-packages/pbr/util.py", line 315, in 
setup_cfg_to_setup_kwargs
value += description_file.read().strip() + '\n\n'
  File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 241: 
ordinal not in range(128)
error in setup command: Error parsing 
/build/1st/python-karborclient-0.6.0/setup.cfg: UnicodeDecodeError: 'ascii' 
codec can't decode byte 0xe2 in position 241: ordinal not in range(128)
debian/rules:10: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1
--- End Message ---
--- Begin Message ---
Source: python-karborclient
Source-Version: 0.6.0-3

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-karborclient 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 07 Dec 2017 22:44:22 +0100
Source: python-karborclient
Binary: python-karborclient python-karborclient-doc python3-karborclient
Architecture: source all
Version: 0.6.0-3
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-karborclient - karbor API client - Python 2.7
 python-karborclient-doc - karbor API client - doc
 python3-karborclient - Karbor API client - Python 3.x
Closes: 882477
Changes:
 python-karborclient (0.6.0-3) unstable; urgency=medium
 .
   * Fixed non-ascii in README.txt that was leading to FTBFS when running
 python setup.py install with LANG=C & Python 3.6 (Closes: 882477).
Checksums-Sha1:
 09197e79621e1357fb3257a34a78210ca95929a0 3252 python-karborclient_0.6.0-3.dsc
 b88a0e00caa542d9b2667b0c9be16064961db8e8 3752 
python-karborclient_0.6.0-3.debian.tar.xz
 7d15968da831c3aba213fbb63a4e1f0a79c6e2aa 915552 
python-karborclient-doc_0.6.0-3_all.deb
 0825a883b2ec9133e7b6779ea0576261385c3994 49872 
python-karborclient_0.6.0-3_all.deb
 d220a2c82bea7508b26fa53d9345adfd929a300e 15223 
python-karborclient_0.6.0-3_amd64.buildinfo
 1f2392294f01e5cfd9d9d49ad78d6b432d036ab0 49936 
python3-karborclient_0.6.0-3_all.deb
Checksums-Sha256:
 4a3fd84eba18b83907eeefcba61106cc47c755f2b8ba649f486cfb605bd9db1e 3252 
python-karborclient_0.6.0-3.dsc
 d4ada4dca5f21c310a814b7d5acacd5bbf4d79be807336839d0e767e49c22755 3752 
python-karborclient_0.6.0-3.debian.tar.xz
 0c2d321d6f63e54559091f0cba01d1495d960bc5758391a0ec74ec6814379031 915552 
python-karborclient-doc_0.6.0-3_all.deb
 ca6307b23f30aaeda10a4a9023a84d30f751054840dc9d04b7f16243c2950abc 49872 
python-karborclient_0.6.0-3_all.deb
 194837036a1900f44e10360c5e693028ea2c65cd1930f0a08343219f235e 15223 
python-karborclient_0.6.0-3_amd64.buildinfo
 61652c36744ce8d045910454c5d9dcb80203db47fcccd8c93466ae979ce1d07b 49936 
python3-karborclient_0.6.0-3_all.deb
Files:
 98af8f009997eee6f89ea39114eccf0b 3252 python optional 
python-karborclient_0.6.0-3.dsc
 1258f24f3d1d899

Bug#883731: audacious: Debian packaging has incorrect license

[John Lindgren]

Hi Nicholas,

> On this topic, would you please update contrib/audacious.appdata.xml
> to reflect the current Audacious license (GPL3)? It claims the
> project_license is BSD-2-Clause.

Sorry if my initial email was unclear.  The current Audacious license *is*
BSD 2-clause, with some exceptions:

1. The embedded copy of libguess (which is an external project) is under
   a BSD 3-clause license, with a separate copyright.  I believe this is
   not a problem so long as the libguess license is also included with
   any distribution.
2. Some of the more ancient plugins are under different licenses, including
   GPLv2+ and GPLv3.  When we relicensed the main parts of Audacious to BSD
   around 2012, we thought it impractical to contact all of the original
   plugin authors since some of them go back to XMMS days (20 years ago now).
   The plugins are compiled as separate binaries, and Debian has them in a
   separate package (audacious-plugins).

Our upstream COPYING file makes note of these exceptions, which is one
reason why it's important for it to be included verbatim, and not replaced
with generic BSD 2-clause text as it is in the current Debian package.

Regarding the plugins, I don't know the state of debian/copyright in the
audacious-plugins package, but my main concern here is that the one in
audacious is correct.

> However, shouldn't it say the following if Audacious' project license
> is GPL-3+ (drop the "any later version" clause for GPL-3 only) ?:

No, see above.

> Also, I found BSD-2-clause here: src/libaudcore/hook.cc,
> src/libaudcore/hook.h, src/libaudcore/output.cc, et al.

Those are correct.

> Conversely, what I found in debian/copyright was a project license of
> GPL-3, with notable exceptions. eg: are really translations GPL-1+?

As I said, debian/copyright is out-of-date.  We relicensed the project
from GPLv3 to BSD 2-clause back in 2012.  Possibly we didn't make an
obvious enough announcement back then for Debian to take notice.

Translations are under the same license as the rest of Audacious.

> To my eyes it looks like the upstream project license needs to be
> clarified and disambiguated, debian/copyright needs work, and finally
> that deduplication patch can be dropped.

Let me know if you think there are still clarifications needed upstream
given the information I've provided here.  I'd be happy to adjust things
as necessary.

Thank you,
John

Processed: tagging 854367

[Debian Bug Tracking System]

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

> tags 854367 - pending
Bug #854367 [apng2gif] apng2gif: CVE-2017-6960: Integer overflow resulting in 
heap buffer overflow
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Processed: user debian...@lists.debian.org, usertagging 853702, usertagging 883128, affects 883128 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 853702 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 883128 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 883128 + sdpam
Bug #883128 [sdpa] sdpa: hard-coded dependency on scotch-5.1
Added indication that 883128 affects sdpam
> found 820308 1.9.1+dfsg-2
Bug #820308 [qiime] qiime: many unsatisfiable dependencies
Marked as found in versions qiime/1.9.1+dfsg-2.
> found 847694 0.11.2-1
Bug #847694 [refind] refind: fails to install in chroot
Marked as found in versions refind/0.11.2-1.
> usertags 878937 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 878937 3.0.0-4
Bug #878937 [src:visp] visp: port baseline violation on i386+amd64 (also causes 
FTBFS on amd64)
Marked as found in versions visp/3.0.0-4.
> affects 878937 + libvisp-core3.0 libvisp-io3.0 libvisp-blob3.0 libvisp-me3.0 
> libvisp-visual-features3.0 libvisp-gui3.0 libvisp-vision3.0 libvisp-sensor3.0 
> libvisp-ar3.0 libvisp-klt3.0 libvisp-robot3.0 libvisp-tt3.0 
> libvisp-detection3.0 libvisp-mbt3.0 libvisp-tt-mi3.0 libvisp-vs3.0
Bug #878937 [src:visp] visp: port baseline violation on i386+amd64 (also causes 
FTBFS on amd64)
Added indication that 878937 affects libvisp-core3.0, libvisp-io3.0, 
libvisp-blob3.0, libvisp-me3.0, libvisp-visual-features3.0, libvisp-gui3.0, 
libvisp-vision3.0, libvisp-sensor3.0, libvisp-ar3.0, libvisp-klt3.0, 
libvisp-robot3.0, libvisp-tt3.0, libvisp-detection3.0, libvisp-mbt3.0, 
libvisp-tt-mi3.0, and libvisp-vs3.0
> affects 878469 + libjs-of-ocaml-dev
Bug #878469 [src:js-of-ocaml] js-of-ocaml FTBFS: ocamlbuild: Command not found
Added indication that 878469 affects libjs-of-ocaml-dev
> affects 883795 + dms-dr
Bug #883795 [dms-core] dms-core: dms-core.postrm removes /var/lib/bind9 on purge
Added indication that 883795 affects dms-dr
> found 874755 2.4.8-3
Bug #874755 [groovy] groovy: broken symlink: /usr/share/groovy/lib/testng.jar 
-> ../../java/testng.jar
Marked as found in versions groovy/2.4.8-3.
> found 857409 52.5.0esr-1
Bug #857409 [firefox-esr-dev] firefox-esr-dev: broken symlink: 
/usr/lib/firefox-esr-devel-45/sdk/bin/run-mozilla.sh -> 
../../../firefox-esr/run-mozilla.sh
Marked as found in versions firefox-esr/52.5.0esr-1.
> found 859149 0.19.1-2
Bug #859149 [python-sklearn-doc] python-sklearn-doc: broken symlink: 
/usr/share/doc/python-sklearn-doc/html/_static/underscore.js -> 
../../../../javascript/jquery/underscore.js
Marked as found in versions scikit-learn/0.19.1-2.
> found 877277 3.4.2-2
Bug #877277 [python-tables-doc] python-tables-doc: broken symlink: 
/usr/share/doc/python-tables-doc/html/_static/MathJax.js -> 
../../../../javascript/mathjax/MathJax.js
Marked as found in versions pytables/3.4.2-2.
> found 857820 1.15.0-1
Bug #857820 [simplesamlphp] simplesamlphp: broken symlink: 
/usr/share/simplesamlphp/vendor/openid/php-openid/Auth -> ../../../../php/Auth
Marked as found in versions simplesamlphp/1.15.0-1.
> found 857379 6.0.5-2
Bug #857379 [fusionforge-common] fusionforge-common: broken symlink: 
/usr/share/fusionforge/common/include/xhtml10t-rdfa10.dtd -> 
../../www/DTD/xhtml10t-rdfa10.dtd
Marked as found in versions fusionforge/6.0.5-2.
> found 857659 8.1.9+dfsg-6
Bug #857659 [gridengine-client] gridengine-client: broken symlink: 
/var/lib/gridengine/jobsbin -> /usr/lib/gridengine/jobsbin
Marked as found in versions gridengine/8.1.9+dfsg-6.
> found 857954 2:1.02.145-4.1
Bug #857954 [libdevmapper-dev] libdevmapper-dev: broken symlink: 
/usr/lib//libdevmapper-event-lvm2.so -> 
/lib//libdevmapper-event-lvm2.so.2.02
Marked as found in versions lvm2/2.02.176-4.1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
820308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820308
847694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847694
857379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857379
857409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857409
857659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857659
857820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857820
857954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857954
859149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859149
874755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874755
877277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877277
878469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878469
878937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878937
883128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883128
883795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

[Julien Aubin]

2017-12-07 22:11 GMT+01:00 Aurelien Jarno :

> On 2017-12-07 18:33, Julien Aubin wrote:
> > Hi,
> >
> > Ldd with file /etc/ld.so.nohwcap :
> > julien@pccorei7-4770:~$ ldd $(which glxgears)
> >linux-vdso.so.1 (0x7ffcc49c5000)
> >libGLEW.so.2.0 => /usr/lib/x86_64-linux-gnu/libGLEW.so.2.0
> > (0x7f9327cc6000)
> >libGLU.so.1 => /usr/lib/x86_64-linux-gnu/libGLU.so.1
> > (0x7f9327a57000)
> >libGL.so.1 => /usr/lib/x86_64-linux-gnu/libGL.so.1
> > (0x7f93277b3000)
> >libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f93274af000)
> >libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6
> > (0x7f932716f000)
> >libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6
> > (0x7f9326f5d000)
> >libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f9326bbe000)
> >libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> > (0x7f932683c000)
> >libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
> > (0x7f9326625000)
> >libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
> (0x7f9326421000)
> >libGLX.so.0 => /usr/lib/x86_64-linux-gnu/libGLX.so.0
> > (0x7f93261f1000)
> >libGLdispatch.so.0 => /usr/lib/x86_64-linux-gnu/
> libGLdispatch.so.0
> > (0x7f9325f23000)
> >/lib64/ld-linux-x86-64.so.2 (0x7f9328161000)
> >libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1
> > (0x7f9325cfb000)
> >libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6
> > (0x7f9325af7000)
> >libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6
> > (0x7f93258f1000)
> >libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0
> > (0x7f93256db000)
> >librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1
> (0x7f93254d3000)
> >libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> > (0x7f93252b6000)
> >
> > Ldd without file /etc/ld.so.nohwcap :
> > julien@pccorei7-4770:~$ ldd $(which glxgears)
> >linux-vdso.so.1 (0x7ffce55b)
> >libGLEW.so.2.0 => /usr/lib/x86_64-linux-gnu/libGLEW.so.2.0
> > (0x7f90c7a69000)
> >libGLU.so.1 => /usr/lib/x86_64-linux-gnu/libGLU.so.1
> > (0x7f90c77fa000)
> >libGL.so.1 => /usr/lib/x86_64-linux-gnu/libGL.so.1
> > (0x7f90c7556000)
> >libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f90c7252000)
> >libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6
> > (0x7f90c6f12000)
> >libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6
> > (0x7f90c6d0)
> >libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f90c6961000)
> >libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> > (0x7f90c65df000)
> >libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
> > (0x7f90c63c8000)
> >libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
> (0x7f90c61c4000)
> >libGLX.so.0 => /usr/lib/x86_64-linux-gnu/libGLX.so.0
> > (0x7f90c5f94000)
> >libGLdispatch.so.0 => /usr/lib/x86_64-linux-gnu/
> libGLdispatch.so.0
> > (0x7f90c5cc6000)
> >/lib64/ld-linux-x86-64.so.2 (0x7f90c7f04000)
> >libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1
> > (0x7f90c5a9e000)
> >libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6
> > (0x7f90c589a000)
> >libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6
> > (0x7f90c5694000)
> >libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0
> > (0x7f90c547e000)
> >librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1
> (0x7f90c5276000)
> >libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> > (0x7f90c5059000)
> >
> > I remark the addresses of libraries are not the same but it is probably
> due
> > to ASLR.
>
> It's normal that the addresses are not the same, that said, I was
> expecting the path to be different. The only thing that
> /etc/ld.so.nohwcap is supposed to change the libraries that are loaded.
> That said, there is are path for optimized libraries on amd64, so I am
> not really surprised. I still don't understand the bug...
>

@Andreas and/or Luca : could you please try as well the same thing as I
did, I mean :
1/ Create file /etc/ld.so.nohwcap
2/ Launch glxgears
3/ Remove the file
4/ Launch glxgears

And then communicate the results ?

>
> Aurelien
>
> --
> Aurelien Jarno  GPG: 4096R/1DDD8C9B
> aurel...@aurel32.net http://www.aurel32.net
>

Bug#859841: zurl: Please migrate to openssl1.1 in Buster

[Jan Niehusmann]

Just a small update to people following this issue:

The qt5 already updated to openssl 1.1, so the only remaining blocker
is curl. In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858398
there is some discussion about the right way to update curl, but I hope
some agreement will be reached, soon.

As soon as libcurl with openssl 1.1 is available, I'll upload an updated
package of zurl.

Jan

Bug#883817: libqhull-dev: missing Depends: libqhull-r7 (= ${binary:Version})

[Andreas Beckmann]

Package: libqhull-dev
Version: 2015.2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

1m17.9s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libqhull_r.so -> libqhull_r.so.7


cheers,

Andreas


libqhull-dev_2015.2-3.log.gz
Description: application/gzip

Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

[Aurelien Jarno]

On 2017-12-07 18:33, Julien Aubin wrote:
> Hi,
> 
> Ldd with file /etc/ld.so.nohwcap :
> julien@pccorei7-4770:~$ ldd $(which glxgears)
>linux-vdso.so.1 (0x7ffcc49c5000)
>libGLEW.so.2.0 => /usr/lib/x86_64-linux-gnu/libGLEW.so.2.0
> (0x7f9327cc6000)
>libGLU.so.1 => /usr/lib/x86_64-linux-gnu/libGLU.so.1
> (0x7f9327a57000)
>libGL.so.1 => /usr/lib/x86_64-linux-gnu/libGL.so.1
> (0x7f93277b3000)
>libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f93274af000)
>libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6
> (0x7f932716f000)
>libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6
> (0x7f9326f5d000)
>libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f9326bbe000)
>libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> (0x7f932683c000)
>libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
> (0x7f9326625000)
>libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f9326421000)
>libGLX.so.0 => /usr/lib/x86_64-linux-gnu/libGLX.so.0
> (0x7f93261f1000)
>libGLdispatch.so.0 => /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0
> (0x7f9325f23000)
>/lib64/ld-linux-x86-64.so.2 (0x7f9328161000)
>libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1
> (0x7f9325cfb000)
>libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6
> (0x7f9325af7000)
>libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6
> (0x7f93258f1000)
>libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0
> (0x7f93256db000)
>librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f93254d3000)
>libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> (0x7f93252b6000)
> 
> Ldd without file /etc/ld.so.nohwcap :
> julien@pccorei7-4770:~$ ldd $(which glxgears)
>linux-vdso.so.1 (0x7ffce55b)
>libGLEW.so.2.0 => /usr/lib/x86_64-linux-gnu/libGLEW.so.2.0
> (0x7f90c7a69000)
>libGLU.so.1 => /usr/lib/x86_64-linux-gnu/libGLU.so.1
> (0x7f90c77fa000)
>libGL.so.1 => /usr/lib/x86_64-linux-gnu/libGL.so.1
> (0x7f90c7556000)
>libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f90c7252000)
>libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6
> (0x7f90c6f12000)
>libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6
> (0x7f90c6d0)
>libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f90c6961000)
>libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> (0x7f90c65df000)
>libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
> (0x7f90c63c8000)
>libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f90c61c4000)
>libGLX.so.0 => /usr/lib/x86_64-linux-gnu/libGLX.so.0
> (0x7f90c5f94000)
>libGLdispatch.so.0 => /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0
> (0x7f90c5cc6000)
>/lib64/ld-linux-x86-64.so.2 (0x7f90c7f04000)
>libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1
> (0x7f90c5a9e000)
>libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6
> (0x7f90c589a000)
>libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6
> (0x7f90c5694000)
>libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0
> (0x7f90c547e000)
>librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f90c5276000)
>libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> (0x7f90c5059000)
> 
> I remark the addresses of libraries are not the same but it is probably due
> to ASLR.

It's normal that the addresses are not the same, that said, I was
expecting the path to be different. The only thing that
/etc/ld.so.nohwcap is supposed to change the libraries that are loaded.
That said, there is are path for optimized libraries on amd64, so I am
not really surprised. I still don't understand the bug...

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#882372: Processed: Bug fix for ohcount #882372

[Sylvestre Ledru]

I don't see the patch fixing the issue?!

Thanks

Le 07/12/2017 à 20:18, Debian Bug Tracking System a écrit :
> Processing commands for cont...@bugs.debian.org:
>
>> outlook 882372 This issue is fixed in the latest version of ohcount: 
>> https://github.com/blackducksoftware/ohcount/releases/tag/v3.1.0
> Outlook recorded from message bug 882372 message 
>> --
> Stopping processing here.
>
> Please contact me if you need assistance.

Bug#883731: audacious: Debian packaging has incorrect license

[Nicholas D Steeves]

Hi John,

On Wed, Dec 06, 2017 at 05:08:56PM -0500, John Lindgren wrote:
> 
> Per Debian policy 2.3:
> 
> "Every package must be accompanied by a verbatim copy of its copyright
> information and distribution license in the file 
> /usr/share/doc/package/copyright
> (see Copyright information for further details)."
> 
> The file /usr/share/doc/audacious/copyright shipped in the Debian package
> is out of date and does not match the current Audacious license (GPL3 vs.
> BSD 2-clause).
> 
> Worse, the Debian package patches out[1] the upstream license file which
> is normally installed under /usr/share/audacious/COPYING and visible in
> the "About" window when running Audacious.
> 
> You are currently distributing Audacious in violation both of our license
> and of Debian's own policy.  Please include the original upstream license,
> verbatim, in the Debian package, or stop distributing Audacious.
> 
> Thank you,
> 
> John Lindgren
> Audacious maintainer

I'm not the maintainer of Audacious' Debian package, but I am part of
the Multimedia team, so I took a look at the Debian and upstream
source, because I agree that license problems must be fixed asap.

On this topic, would you please update contrib/audacious.appdata.xml
to reflect the current Audacious license (GPL3)?  It claims the
project_license is BSD-2-Clause.

http://redmine.audacious-media-player.org/projects/audacious/repository/revisions/master/changes/contrib/audacious.appdata.xml

And when I looked up upstream audacious/COPYING here:
http://redmine.audacious-media-player.org/projects/audacious/repository/revisions/master/changes/COPYING

I found this, which also looks like BSD-2-Clause:

LICENSE

Copyright © 2001-2017 Audacious developers and others

(A list of the copyright holders is provided in the AUTHORS file.)

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice,
   this list of conditions, and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice,
   this list of conditions, and the following disclaimer in the
   documentation provided with the distribution.

This software is provided “as is” and without any warranty, express or
implied.  In no event shall the authors be liable for any damages arising
from the use of this software.
--
However, shouldn't it say the following if Audacious' project license
is GPL-3+ (drop the "any later version" clause for GPL-3 only) ?:

Audacious, an Advanced Audio Player
Copyright (C) 2001-2017 Audacious developers and others

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program.  If not, see .
--

Also, I found BSD-2-clause here: src/libaudcore/hook.cc,
src/libaudcore/hook.h, src/libaudcore/output.cc, et al.

Conversely, what I found in debian/copyright was a project license of
GPL-3, with notable exceptions. eg: are really translations GPL-1+?
Because the project license seems to be BSD-2-Clause, and the
translations have "This file is distributed under the same license as
the Audacious package" I wonder if they're actually BSD-2-Clause.
Would you please provide a citation for the upstream project's
relicensing to GPL-3?

Finally, from what I understand about combining licenses I think the
BSD-2-clause project license (please provide evidence that this isn't
the case), the src/libguess/* BSD-3-clause and the GPL bits can all be
used to produce a GPL-3 binary, so long as the BSD copyright notices
are preserved.

To my eyes it looks like the upstream project license needs to be
clarified and disambiguated, debian/copyright needs work, and finally
that deduplication patch can be dropped.

I'd be happy to take care of the Debian side of things over the
weekend.

Thank you,
Nicholas


signature.asc
Description: PGP signature

Bug#883809: os-autoinst: unsatisfiable Depends: tesseract-all - did you want tesseract-ocr-all?

[Andreas Beckmann]

Package: os-autoinst
Version: 4.4.1508936943.39adc5eb-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

The following packages have unmet dependencies:
 os-autoinst : Depends: tesseract-all but it is not installable
E: Unable to correct problems, you have held broken packages.

There is no package tesseract-all in the archive, but the similarily
named tesseract-ocr-all exists.


Cheers,

Andreas

Bug#880233: marked as done (openbsc: FTBFS: | ./openbsc/conftest.c:22: undefined reference to `dlopen')

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2017 19:59:23 +
with message-id 
and subject line Bug#880233: fixed in openbsc 0.15.0-3
has caused the Debian Bug report #880233,
regarding openbsc: FTBFS: | ./openbsc/conftest.c:22: undefined reference to 
`dlopen'
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.)


-- 
880233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openbsc
Version: 0.15.0-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20171030 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[6]: Entering directory '/<>/openbsc/tests'
> :;{ \
>echo '# Signature of the current package.' && \
>echo 'm4_define([AT_PACKAGE_NAME],' && \
>echo '  [openbsc])' && \
>echo 'm4_define([AT_PACKAGE_TARNAME],' && \
>echo '  [openbsc])' && \
>echo 'm4_define([AT_PACKAGE_VERSION],' && \
>echo '  [0.15.0])' && \
>echo 'm4_define([AT_PACKAGE_STRING],' && \
>echo '  [openbsc 0.15.0])' && \
>echo 'm4_define([AT_PACKAGE_BUGREPORT],' && \
>echo '  [open...@lists.osmocom.org])'; \
>echo 'm4_define([AT_PACKAGE_URL],' && \
>echo '  [])'; \
>  } >'./package.m4'
> /bin/bash ../missing --run autom4te --language=autotest -I '.' -o 
> testsuite.tmp testsuite.at
> mv testsuite.tmp testsuite
> /bin/bash './testsuite' 
> ## -- ##
> ## openbsc 0.15.0 test suite. ##
> ## -- ##
> 
> Regression tests.
> 
>   1: gsm0408 ok
>   2: subscr  ok
>   3: db  FAILED (testsuite.at:21)
>   4: channel ok
>   5: mgcpok
>   6: mgcp-trans  skipped (testsuite.at:38)
>   7: gprsok
>   8: bsc-nat ok
>   9: smppok
>  10: bsc-nat-trieok
>  11: abisok
>  12: bsc ok
>  13: gbproxy ok
>  14: trauok
>  15: sgsnok
> 
> ## - ##
> ## Test results. ##
> ## - ##
> 
> ERROR: 14 tests were run,
> 1 failed unexpectedly.
> 1 test was skipped.
> ## -- ##
> ## testsuite.log was created. ##
> ## -- ##
> 
> Please send `tests/testsuite.log' and all information you think might help:
> 
>To: 
>Subject: [openbsc 0.15.0] testsuite: 3 failed
> 
> You may investigate any problem if you feel able to do so, in which
> case the test suite provides a good starting point.  Its output may
> be found below `tests/testsuite.dir'.
> 
> Makefile:673: recipe for target 'check-local' failed
> make[6]: *** [check-local] Error 1
> make[6]: Leaving directory '/<>/openbsc/tests'
> Makefile:524: recipe for target 'check-am' failed
> make[5]: *** [check-am] Error 2
> make[5]: Leaving directory '/<>/openbsc/tests'
> Makefile:376: recipe for target 'check-recursive' failed
> make[4]: *** [check-recursive] Error 1
> make[4]: Leaving directory '/<>/openbsc/tests'
> Makefile:464: recipe for target 'check-recursive' failed
> make[3]: *** [check-recursive] Error 1
> make[3]: Leaving directory '/<>/openbsc'
> Makefile:755: recipe for target 'check' failed
> make[2]: *** [check] Error 2
> make[2]: Leaving directory '/<>/openbsc'
> dh_auto_test: cd openbsc && make -j1 check VERBOSE=1 returned exit code 2
> # -*- compilation -*-
> 3. testsuite.at:16: testing db ...
> ./testsuite.at:21: $abs_top_builddir/tests/db/db_test
> --- experr2017-10-30 15:38:35.099596935 +
> +++ /<>/openbsc/tests/testsuite.dir/at-groups/3/stderr   
> 2017-10-30 15:38:35.203594376 +
> @@ -1,2 +1,108 @@
>  Going to migrate from revision 3
> +DBI: -6: An invalid or out-of-range index was passed to libdbi
> +backtrace() returned 8 addresses
> +/<>/openbsc/tests/db/db_test(+0x8dca) 
> [0x5603b02cfdca]
> +[0;

Processed: tagging 854367

[Debian Bug Tracking System]

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

> tags 854367 + pending
Bug #854367 [apng2gif] apng2gif: CVE-2017-6960: Integer overflow resulting in 
heap buffer overflow
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: user debian...@lists.debian.org, usertagging 883795, found 883795 in 1.0.8-1.2, affects 883795

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 883795 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 883795 1.0.8-1.2
Bug #883795 [dms-core] dms-core: dms-core.postrm removes /var/lib/bind9 on purge
Marked as found in versions dms/1.0.8-1.2.
> affects 883795 + dms-wsgi
Bug #883795 [dms-core] dms-core: dms-core.postrm removes /var/lib/bind9 on purge
Added indication that 883795 affects dms-wsgi
> thanks
Stopping processing here.

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

Processed: Bug fix for ohcount #882372

[Debian Bug Tracking System]

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

> outlook 882372 This issue is fixed in the latest version of ohcount: 
> https://github.com/blackducksoftware/ohcount/releases/tag/v3.1.0
Outlook recorded from message bug 882372 message 
> --
Stopping processing here.

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

Bug#883615:

[Marie Lynette Reed]

What is this?

Processed (with 5 errors): Bug fix for ohcount #882372

[Debian Bug Tracking System]

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

> tags 882372 patch
Bug #882372 [ohcount] ohcount: CVE-2017-16926: Command injection through file 
names
Added tag(s) patch.
> Hi,
Unknown command or malformed arguments to command.
> We have released a new version of ohcount that fixes this vulnerability.
Unknown command or malformed arguments to command.
> https://github.com/blackducksoftware/ohcount/releases/tag/v3.1.0
Unknown command or malformed arguments to command.
> Regards,
Unknown command or malformed arguments to command.
> Alex
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

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

Bug#883801: grisbi: ships /usr/share/glib-2.0/schemas/gschemas.compiled

[Andreas Beckmann]

Package: grisbi
Version: 1.1.90-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package modifies a shipped
file. /usr/share/glib-2.0/schemas/gschemas.compiled is generated
automatically by triggers, it must not be shipped in any package.

0m41.5s ERROR: FAIL: debsums reports modifications inside the chroot:
  /usr/share/glib-2.0/schemas/gschemas.compiled


cheers,

Andreas

Bug#880347: bug squashing target: Probably bowtie 1.2.1.1 issue (Was: Bug#880347: bioperl-run: FTBFS: Test failures)

[Andreas Tille]

Hi Alex,

On Thu, Dec 07, 2017 at 06:12:05PM +0100, Alex Mestiashvili wrote:
> 
> That's a trivial one, s/reads processed: 1000/reads processed: 2000/
> I'll take care.

Cool!  Thanks a lot.

BTW, there are *lots* if easy ones - just in case this will keep
motivation of all team members higher. ;-)

Kind regards

 Andreas. 

-- 
http://fam-tille.de

Bug#876840: fseeko() on reference file: Invalid argument (Was: Bug#876840: staden-io-lib FTBFS on non-i386 32bit: FAIL: java)

[James Cowgill]

Hi,

On 07/12/17 15:28, Andreas Tille wrote:
> On Thu, Dec 07, 2017 at 02:40:36PM +, James Bonfield wrote:
>> On Tue, Dec 05, 2017 at 08:02:18AM +0100, Andreas Tille wrote:
>>> this is a kind ping since as I wrote below the issue seems not be solved.
>>
>> I'm not sure I can easily debug this as it only fails on systems I
>> have no access to; it's like trying to debug your grandmother's
>> windows desktop over the phone...
>>
>> I'm still convinced it's something to do with large file support not
>> working correctly, likely with off_t being the wrong size.  Especially
>> given the 64-bit mips build works while the 32-bit one does not.  I
>> assume everything else about these architectures are the same.
>>
>> We don't have any 32-bit build systems any more though.
>>
> Does adding that fix the fseeko call to start working again?

 Unfortunately not - see here the build logs:

 https://buildd.debian.org/status/package.php?p=staden-io-lib
>>
>> James
>> -- 
>> James Bonfield (j...@sanger.ac.uk) | Hora aderat briligi. Nunc et Slythia 
>> Tova
> 
> 
> I'm just forwarding this to debian-arm and debian-mips.  I see no other
> chance to deal with this bug rather than removing these architectures
> from the architectures field.
> 
> Do you have any better suggestion?

The bug is here:
https://sources.debian.org/src/staden-io-lib/1.14.9-3/io_lib/bgzip.c/#L47

Unlike most packages (although there are quite a few that do this),
staden-io-lib defines _FILE_OFFSET_BITS in a config header instead of
passing it as a -D argument to the compiler. Since this flag affects the
behavior of standard headers, you *must* include this header before any
others.

In the bgzip.c file above, stdio.h is included before the
io_lib_config.h header. This causes bgzip.c to have a different opinion
of what sizeof(off_t) compared to other files, so all external calls to
bzi_seek invoke undefined behavior.

To fix, move the "#ifdef HAVE_CONFIG_H...#endif" block above all the
other includes in that file.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#882534: marked as done (neutron-dynamic-routing FTBFS: test failure)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2017 17:34:51 +
with message-id 
and subject line Bug#882534: fixed in neutron-dynamic-routing 2:11.0.0-1
has caused the Debian Bug report #882534,
regarding neutron-dynamic-routing FTBFS: test failure
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.)


-- 
882534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: neutron-dynamic-routing
Version: 2:9.0.0-1.2
Severity: serious

Some recent change in unstable makes neutron-dynamic-routing FTBFS:

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

...
===> Testing with python2.7 (python2)
+ rm -rf .testrepository
+ testr-python2 init
+ mktemp -t
+ TEMP_REZ=/tmp/tmp.0ZJQpHYTu4
+ tee /tmp/tmp.0ZJQpHYTu4
+ PYTHONPATH=/build/1st/neutron-dynamic-routing-9.0.0 PYTHON=python2.7 
testr-python2 run --subunit neutron_dynamic_routing.tests.unit
+ subunit2pyunit
module pyroute2.ipdb.common is deprecated, use pyroute2.ipdb.exceptions instead
Non-zero exit code (2) from test listing.
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-60} \
OS_LOG_CAPTURE=1 \
${PYTHON:-python} -m subunit.run discover -t ./ \
${OS_TEST_PATH:-./neutron_dynamic_routing/tests/unit} \
--list 
--- import errors ---
Failed to import test module: 
neutron_dynamic_routing.tests.unit.api.rpc.agentnotifiers.test_bgp_dr_rpc_agent_api
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File 
"neutron_dynamic_routing/tests/unit/api/rpc/agentnotifiers/test_bgp_dr_rpc_agent_api.py",
 line 18, in 
from neutron import context
ImportError: cannot import name context

Failed to import test module: 
neutron_dynamic_routing.tests.unit.api.rpc.handlers.test_bgp_speaker_rpc
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File 
"neutron_dynamic_routing/tests/unit/api/rpc/handlers/test_bgp_speaker_rpc.py", 
line 20, in 
from neutron_dynamic_routing.api.rpc.handlers import bgp_speaker_rpc
  File "neutron_dynamic_routing/api/rpc/handlers/bgp_speaker_rpc.py", line 20, 
in 
from neutron_dynamic_routing.extensions import bgp as bgp_ext
  File "neutron_dynamic_routing/extensions/bgp.py", line 38, in 
'validate': {'type:string': attr.NAME_MAX_LEN},
AttributeError: 'module' object has no attribute 'NAME_MAX_LEN'

Failed to import test module: neutron_dynamic_routing.tests.unit.db.test_bgp_db
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "neutron_dynamic_routing/tests/unit/db/test_bgp_db.py", line 32, in 

from neutron_dynamic_routing.extensions import bgp
  File "neutron_dynamic_routing/extensions/bgp.py", line 38, in 
'validate': {'type:string': attr.NAME_MAX_LEN},
AttributeError: 'module' object has no attribute 'NAME_MAX_LEN'

Failed to import test module: 
neutron_dynamic_routing.tests.unit.db.test_bgp_dragentscheduler_db
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "neutron_dynamic_routing/tests/unit/db/test_bgp_dragentscheduler_db.py", 
line 19, in 
from neutron import context
ImportError: cannot import name context

Failed to import test module: 
neutron_dynamic_routing.tests.unit.services.bgp.agent.test_bgp_dragent
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__imp

Bug#880981: marked as done (jigdo FTBFS with glibc >= 2.25)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2017 17:34:40 +
with message-id 
and subject line Bug#880981: fixed in jigdo 0.7.3-5
has caused the Debian Bug report #880981,
regarding jigdo FTBFS with glibc >= 2.25
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.)


-- 
880981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880981
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jigdo
Version: 0.7.3-4
Severity: important
Tags: sid buster

fix build failure with glibc-2.26.

The package could benefit with a conversion to quilt package format too.
Index: b/src/mkimage.cc
===
--- a/src/mkimage.cc
+++ b/src/mkimage.cc
@@ -285,27 +285,27 @@ bostream& JigdoDescVec::put(bostream& fi
 //__
 
 namespace {
-  const int SIZE_WIDTH = 12;
+  const int J_SIZE_WIDTH = 12;
 }
 
 ostream& JigdoDesc::ImageInfo::put(ostream& s) const {
-  s << "image-info  " << setw(SIZE_WIDTH) << size() << "  "
+  s << "image-info  " << setw(J_SIZE_WIDTH) << size() << "  "
 << md5() << ' ' << blockLength() << '\n';
   return s;
 }
 ostream& JigdoDesc::UnmatchedData::put(ostream& s) const {
-  s << "in-template " << setw(SIZE_WIDTH) << offset() << ' '
-<< setw(SIZE_WIDTH) << size() << '\n';
+  s << "in-template " << setw(J_SIZE_WIDTH) << offset() << ' '
+<< setw(J_SIZE_WIDTH) << size() << '\n';
   return s;
 }
 ostream& JigdoDesc::MatchedFile::put(ostream& s) const {
-  s << "need-file   " << setw(SIZE_WIDTH) << offset() << ' '
-<< setw(SIZE_WIDTH) << size() << ' ' << md5() << ' ' << rsync() << '\n';
+  s << "need-file   " << setw(J_SIZE_WIDTH) << offset() << ' '
+<< setw(J_SIZE_WIDTH) << size() << ' ' << md5() << ' ' << rsync() << '\n';
   return s;
 }
 ostream& JigdoDesc::WrittenFile::put(ostream& s) const {
-  s << "have-file   " << setw(SIZE_WIDTH) << offset() << ' '
-<< setw(SIZE_WIDTH) << size() << ' ' << md5() << ' ' << rsync() << '\n';
+  s << "have-file   " << setw(J_SIZE_WIDTH) << offset() << ' '
+<< setw(J_SIZE_WIDTH) << size() << ' ' << md5() << ' ' << rsync() << '\n';
   return s;
 }
 
--- End Message ---
--- Begin Message ---
Source: jigdo
Source-Version: 0.7.3-5

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

Debian distribution maintenance software
pp.
Steve McIntyre <93...@debian.org> (supplier of updated jigdo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 07 Dec 2017 16:38:20 +
Source: jigdo
Binary: jigdo-file
Architecture: source
Version: 0.7.3-5
Distribution: unstable
Urgency: medium
Maintainer: Steve McIntyre <93...@debian.org>
Changed-By: Steve McIntyre <93...@debian.org>
Description:
 jigdo-file - Download Debian CD images from any Debian mirror
Closes: 578325 609816 767318 826781 864516 865864 880981
Changes:
 jigdo (0.7.3-5) unstable; urgency=medium
 .
   * Switch addresses from atterer.org to atterer.org in various places
 (Closes: #609816)
   * jigdo-lite: use tmpDir when creating images. Closes: #578325
 Thanks to Mateusz Poszwa for the patch.
   * jigdo-lite: Cope with https URLs. Closes: #865864.
 Thanks to s3v for the patch for inspiration.
   * jigdo-lite: Unset GREP_OPTIONS at the start. Closes: #767318
   * jigdo-lite: Read/store the filesPerFetch setting from the config
 file. Closes: #826781
   * jigdo-file: Fix building with glibc >= 2.25. Closes: #880981
 Thanks to Matthias Klose for the patch.
   * Various packaging changes:
 + Switch source format to 3.0 (quilt) and split up patches a little
 + Update to Standards-Version: 4.1.1
 + Switch Priority to optional
 + Improve cross-building. Closes: #864516. Thanks to Helmut Grohne for
   the patch
Checksums-Sha1:
 54578a0e5958adc718656aba47a53934e722d3c1 1708 jigdo_0.7.3-5.dsc
 21c0102fe9cd84f6074815e0c8aab6f67907931b 26460 jigdo_0.7.3-5.debian.tar.xz
 ce544e56fe4adecb44d4c5a2f1b1a96cb520f299 6739 jigdo_0.7.3-5_source.buildinfo
Ch

Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

[Julien Aubin]

Hi,

Ldd with file /etc/ld.so.nohwcap :
julien@pccorei7-4770:~$ ldd $(which glxgears)
   linux-vdso.so.1 (0x7ffcc49c5000)
   libGLEW.so.2.0 => /usr/lib/x86_64-linux-gnu/libGLEW.so.2.0
(0x7f9327cc6000)
   libGLU.so.1 => /usr/lib/x86_64-linux-gnu/libGLU.so.1
(0x7f9327a57000)
   libGL.so.1 => /usr/lib/x86_64-linux-gnu/libGL.so.1
(0x7f93277b3000)
   libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f93274af000)
   libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6
(0x7f932716f000)
   libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6
(0x7f9326f5d000)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f9326bbe000)
   libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x7f932683c000)
   libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x7f9326625000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f9326421000)
   libGLX.so.0 => /usr/lib/x86_64-linux-gnu/libGLX.so.0
(0x7f93261f1000)
   libGLdispatch.so.0 => /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0
(0x7f9325f23000)
   /lib64/ld-linux-x86-64.so.2 (0x7f9328161000)
   libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1
(0x7f9325cfb000)
   libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6
(0x7f9325af7000)
   libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6
(0x7f93258f1000)
   libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0
(0x7f93256db000)
   librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f93254d3000)
   libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f93252b6000)

Ldd without file /etc/ld.so.nohwcap :
julien@pccorei7-4770:~$ ldd $(which glxgears)
   linux-vdso.so.1 (0x7ffce55b)
   libGLEW.so.2.0 => /usr/lib/x86_64-linux-gnu/libGLEW.so.2.0
(0x7f90c7a69000)
   libGLU.so.1 => /usr/lib/x86_64-linux-gnu/libGLU.so.1
(0x7f90c77fa000)
   libGL.so.1 => /usr/lib/x86_64-linux-gnu/libGL.so.1
(0x7f90c7556000)
   libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f90c7252000)
   libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6
(0x7f90c6f12000)
   libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6
(0x7f90c6d0)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f90c6961000)
   libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x7f90c65df000)
   libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x7f90c63c8000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f90c61c4000)
   libGLX.so.0 => /usr/lib/x86_64-linux-gnu/libGLX.so.0
(0x7f90c5f94000)
   libGLdispatch.so.0 => /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0
(0x7f90c5cc6000)
   /lib64/ld-linux-x86-64.so.2 (0x7f90c7f04000)
   libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1
(0x7f90c5a9e000)
   libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6
(0x7f90c589a000)
   libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6
(0x7f90c5694000)
   libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0
(0x7f90c547e000)
   librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f90c5276000)
   libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f90c5059000)

I remark the addresses of libraries are not the same but it is probably due
to ASLR.

Another thing I was thinking of : if the issue is related to code paths,
maybe we should try on some other CPUs w/ the NVidia blob, because it might
be a Haswell hardware bug. What do you think of this ? We should try on
some Intel non-Haswell CPU w/ and w/o the file.

Rgds,

2017-12-07 10:06 GMT+01:00 Aurelien Jarno :

> control: reopen -1
> control: tag -1 - unreproducible
> control: retitle -1 nvidia-driver: crashes with /etc/ld.so.nohwcap
>
> On 2017-12-07 05:43, Julien Aubin wrote:
> > 2017-12-06 21:50 GMT+01:00 Aurelien Jarno :
> >
> > > On 2017-12-06 19:39, Julien Aubin wrote:
> > > > Weird... this time I re-upgraded libc6 and things work fine... looks
> like
> > > > something wrong went during the install. And I cannot reproduce the
> issue
> > > > anymore... :'( WTF ???
> > >
> > > Hmm, a bug has been introduced in libc6 version 2.24-11+deb9u2, which
> in
> > > some conditions leave the /etc/ld.so.nohwcap file instead of removing
> it
> > > just after the upgrade (see bug#883394). One of the condition is to
> have
> > > libc6-i686 installed (while it can be safely removed), which seems to
> be
> > > your case.
> > >
> > > I consider this bug harmless as it should not deactivate anything now
> > > that the default libc is already i686 optimized. Also I don't see how
> it
> > > could trigger the issue you described. Anyway better be safe than
> sorry,
> > > could you please try to create this file with "touch
> /etc/ld.so.nohwcap"
> > > as root and see if it makes the issue to reappear? Once the test is
> done
> > > you can then remove it.
> > >
> > > Thanks,
> > > Aurelien
> > >
> >
> >

Processed: reassign 883785 to libvirt-daemon

[Debian Bug Tracking System]

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

> reassign 883785 libvirt-daemon
Bug #883785 [libvirtd] libvirtd crashes when starting a vm with IDE cdrom
Warning: Unknown package 'libvirtd'
Bug reassigned from package 'libvirtd' to 'libvirt-daemon'.
Ignoring request to alter found versions of bug #883785 to the same values 
previously set
Ignoring request to alter fixed versions of bug #883785 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed (with 2 errors): Re: [Pkg-libvirt-maintainers] Bug#883785: libvirtd 3.10 segfault when starting a VM

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libvirtd
Bug #883785 [libvirt] libvirtd 3.10 segfault when starting a VM
Bug reassigned from package 'libvirt' to 'libvirtd'.
Warning: Unknown package 'libvirtd'
Warning: Unknown package 'libvirtd'
No longer marked as found in versions 3.10.0-1.
Warning: Unknown package 'libvirtd'
Warning: Unknown package 'libvirtd'
Ignoring request to alter fixed versions of bug #883785 to the same values 
previously set
Warning: Unknown package 'libvirtd'
> found 3.9.0-1
Unknown command or malformed arguments to command.

> retitle -1 libvirtd crashes when starting a vm with IDE cdrom
Bug #883785 [libvirtd] libvirtd 3.10 segfault when starting a VM
Warning: Unknown package 'libvirtd'
Changed Bug title to 'libvirtd crashes when starting a vm with IDE cdrom' from 
'libvirtd 3.10 segfault when starting a VM'.
Warning: Unknown package 'libvirtd'
> forcemerge -1 881293
Bug #883785 [libvirtd] libvirtd crashes when starting a vm with IDE cdrom
Warning: Unknown package 'libvirtd'
Unable to merge bugs because:
package of #881293 is 'libvirt-daemon' not 'libvirtd'
Warning: Unknown package 'libvirtd'
Failed to forcibly merge 883785: Did not alter merged bugs.


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

Bug#883785: [Pkg-libvirt-maintainers] Bug#883785: libvirtd 3.10 segfault when starting a VM

[Guido Günther]

control: reassign -1 libvirtd
control: found 3.9.0-1
control: retitle -1 libvirtd crashes when starting a vm with IDE cdrom
control: forcemerge -1 881293

Hi,
On Thu, Dec 07, 2017 at 03:38:24PM +0100, Pascal Obry wrote:
> 
> Package: libvirt
> Version: 3.10
> Severity: grave
> 
> With libvirt version 3.10 I cannot start a VM. Reverting to 3.0
> (Debian/stable) all is fine. This was initially found in GNOME-Boxes
> but I have been able to reproduce on the command line using virsh.
> 
> Note also that I had the same issue with 3.9.
> 
> On one console:
> 
> $ LIBVIRT_DEBUG=1 gdb /usr/sbin/libvirtd
> 
> On a second console, I tried to start the VM:
> 
> $ virsh start boxes-winxp
> 
> Then I got this exception from libvirtd:
> 
> Thread 5 "libvirtd" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7febad4a5700 (LWP 7867)]
> 0x7feb94b109c8 in virStorageFileReportBrokenChain ()
>from /usr/lib/libvirt/connection-driver/libvirt_driver_storage.so
> (gdb) bt
> #0  0x7feb94b109c8 in virStorageFileReportBrokenChain ()
>from /usr/lib/libvirt/connection-driver/libvirt_driver_storage.so
> #1  0x7feb7d266da3 in qemuDomainDetermineDiskChain ()
>from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
> #2  0x7feb7d28eec2 in qemuProcessPrepareHost ()
>from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
> #3  0x7feb7d294b71 in qemuProcessStart ()
>from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
> #4  0x7feb7d2f5201 in ?? ()
>from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
> #5  0x7feb7d2f58e6 in ?? ()
>from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
> #6  0x7febb9e5e077 in virDomainCreate (domain=0x7feb980008c0)
> at ../../../src/libvirt-domain.c:6531
> #7  0x56190ba2ed9c in ?? ()
> #8  0x7febb9ec697c in virNetServerProgramDispatchCall 
> (msg=0x56190d9e7590, 
> client=0x56190d9e6fb0, server=0x56190d9d00f0, prog=0x56190d9e4f40)
> at ../../../src/rpc/virnetserverprogram.c:437
> #9  virNetServerProgramDispatch (prog=0x56190d9e4f40, server=0x56190d9d00f0, 
> client=0x56190d9e6fb0, msg=0x56190d9e7590)
> at ../../../src/rpc/virnetserverprogram.c:307
> #10 0x56190ba3e988 in ?? ()
> #11 0x7febb9da1c01 in virThreadPoolWorker (
> opaque=opaque@entry=0x56190d9ce9f0)
> at ../../../src/util/virthreadpool.c:167
> #12 0x7febb9da0f78 in virThreadHelper (data=)
> at ../../../src/util/virthread.c:206
> #13 0x7febb68b0519 in start_thread (arg=0x7febad4a5700)
> at pthread_create.c:456
> #14 0x7febb65f2a5f in clone ()
> at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
> (gdb) 
> 
> I noticed that running with 3.0 I had a message saying that /dev/sr0 is
> not accessible. And indeed I do not have a CDROM on this machine. The
> .xml were migrated from a machine with a CDROM to this new one.
> 
> Removing:
> 
> 
>   
>   
>   
>   
>   
> 
> 
> Seems to fix the issue. Yet, libvirt should not crash on this. And the
> backtrace makes sense with this fix BTW.

Yept. Should not crash. Looks similar to another issue I did not get
around to look at.

Cheers,
 -- Guido

Bug#880347: bug squashing target: Probably bowtie 1.2.1.1 issue (Was: Bug#880347: bioperl-run: FTBFS: Test failures)

[Alex Mestiashvili]

> ...
> #   Failed test 'bowtie success'
> #   at t/Bowtie.t line 188.
> #   '# reads processed: 2000
> # # reads with at least one reported alignment: 2000 (100.00%)
> # # reads that failed to align: 0 (0.00%)
> # Reported 1000 paired-end alignments to 1 output stream(s)
> # '
> # doesn't match '(?^:reads processed: 1000)'
> 
> #   Failed test 'bowtie success'
> #   at t/Bowtie.t line 195.
> #   '# reads processed: 2000
> # # reads with at least one reported alignment: 2000 (100.00%)
> # # reads that failed to align: 0 (0.00%)
> # Reported 1000 paired-end alignments to 1 output stream(s)
> # '
> # doesn't match '(?^:reads processed: 1000)'
> # Looks like you failed 2 tests of 61.
> t/Bowtie.t .
> ...
> 
> 
> I suspect that some change between bowtie 1.2.0 and bowtie 1.2.1.1 is
> responsible for the issue in bioperl-run.  I wonder whether tracking
> down this issue sounds interesting for somebody who knows (and uses)
> bowtie a bit.
> 
> Kind regards
> 
>Andreas.
> 


Hi Andreas,

That's a trivial one, s/reads processed: 1000/reads processed: 2000/
I'll take care.

Best regards,
Alex

Processed: [bts-link] source package src:pupnp-1.8

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:pupnp-1.8
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #882377 (http://bugs.debian.org/882377)
> # Bug title: pupnp-1.8: version 1.8.3 breaks the ABI
> #  * https://github.com/mrjimenez/pupnp/issues/57
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 882377 + fixed-upstream
Bug #882377 [src:pupnp-1.8] pupnp-1.8: version 1.8.3 breaks the ABI
Added tag(s) fixed-upstream.
> usertags 882377 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 882377 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#880229: qbittorrent fills /tmp filesystem causing other programs to fail

[jim_p]

Package: qbittorrent
Followup-For: Bug #880229

I am using qbittorrent 3.3.15, I am having /tmp in ram (tmpfs) and what you
mention does not happen. I also have all my browsers' caches inside /tmp as
well (/tmp/cache) and I do keep at least one browser open all the time.

More specifically. This is what i have in my fstab for /tmp

tmpfs   /tmptmpfs   defaults0   0

This is what df -h reports for when downloading a 1GB torrent

- at the beggining of the download
tmpfs   2.0G   29M  2.0G   2% /tmp

- at ~25% of the download
tmpfs   2.0G   37M  1.9G   2% /tmp

- at ~50% of the download
tmpfs   2.0G   38M  1.9G   2% /tmp

- at ~100% of the download
tmpfs   2.0G   58M  1.9G   3% /tmp

Litterally NO difference at all, because all that space is allocated by
/tmp/cache

$ du -h /tmp/cache/
4.0K/tmp/cache/opera/Media Cache/index-dir
88K /tmp/cache/opera/Media Cache
40K /tmp/cache/opera/Cache/index-dir
58M /tmp/cache/opera/Cache
58M /tmp/cache/opera
58M /tmp/cache/

All qbittorrent writes in /tmp is an empty folder (/tmp/.qBittorrent) and 2
zero-sized files in /tmp named qtsingleapp-qBitto-something, nothing more.

p.s. Do you really have that problem in 3.3.7 or you just... assume it will be
a problem for someone who has /tmp in ram? Because many other executables write
in /tmp regularly, e.g. systemd, and not a single one has caused problems to
others due to low space. I have /tmp in ram for the last 6-7 years.



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

Kernel: Linux 4.13.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages qbittorrent depends on:
ii  geoip-database 20171107-1
ii  libboost-system1.62.0  1.62.0+dfsg-4+b2
ii  libc6  2.25-3
ii  libgcc11:7.2.0-16
ii  libqt5core5a   5.9.2+dfsg-4
ii  libqt5dbus55.9.2+dfsg-4
ii  libqt5gui5 5.9.2+dfsg-4
ii  libqt5network5 5.9.2+dfsg-4
ii  libqt5widgets5 5.9.2+dfsg-4
ii  libqt5xml5 5.9.2+dfsg-4
ii  libstdc++6 7.2.0-16
ii  libtorrent-rasterbar9  1.1.4-1
ii  python 2.7.14-1
ii  zlib1g 1:1.2.8.dfsg-5

qbittorrent recommends no packages.

Versions of packages qbittorrent suggests:
pn  qbittorrent-dbg  

-- no debconf information

Bug#882263: marked as done (libc6-dev-mips64el-cross breaks linking executables)

[Debian Bug Tracking System]

Your message dated Thu, 7 Dec 2017 17:32:00 +0100
with message-id <7b1f4a84-bfba-3118-de8b-dcb6b6c14...@debian.org>
and subject line Re: libc6-dev-mips64el-cross breaks linking executables
has caused the Debian Bug report #882263,
regarding libc6-dev-mips64el-cross breaks linking executables
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.)


-- 
882263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-dev-mips64el-cross
Version: 20
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

I was trying to use gcc-mips64el-linux-gnuabi64 to link a trivial
executable:

$ echo 'int main(){return 0;}' | mips64el-linux-gnuabi64-gcc -x c - -o /dev/null

With libc6-dev:mips64el installed, this just works. As soon as I install
libc6-dev-mips64el-cross, it fails though:

/usr/lib/gcc-cross/mips64el-linux-gnuabi64/7/../../../../mips64el-linux-gnuabi64/bin/ld:
 cannot find /usr/mips64el-linux-gnuabi64/lib/ld.so.1
collect2: error: ld returned 1 exit status

This renders libc6-dev-mips64el-cross pretty much useless.

Helmut
--- End Message ---
--- Begin Message ---
Version: 21--- End Message ---

Bug#883762: marked as done (pyscanfcs: Includes "freeze_pyinstaller/PyScanFCS.icns" listed in Files-Excluded header)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2017 16:12:11 +
with message-id 
and subject line Bug#883762: fixed in pyscanfcs 0.2.3+ds-1
has caused the Debian Bug report #883762,
regarding pyscanfcs: Includes "freeze_pyinstaller/PyScanFCS.icns" listed in 
Files-Excluded header
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.)


-- 
883762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyscanfcs
Version: 0.2.3-5
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

pyscanfcs lists "freeze_pyinstaller/PyScanFCS.icns" in the Files-Excluded
field in debian/copyright but the source tree contains
freeze_pyinstaller/PyScanFCS.icns

This is probably a DFSG violation, or at the upstream tarball was not
repacked as intended. Alternatively, the field is simply out of date.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: pyscanfcs
Source-Version: 0.2.3+ds-1

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

Debian distribution maintenance software
pp.
Alexandre Mestiashvili  (supplier of updated 
pyscanfcs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 07 Dec 2017 16:16:09 +0100
Source: pyscanfcs
Binary: pyscanfcs
Architecture: source amd64
Version: 0.2.3+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Alexandre Mestiashvili 
Description:
 pyscanfcs  - scientific tool for perpendicular line scanning FCS
Closes: 883762
Changes:
 pyscanfcs (0.2.3+ds-1) unstable; urgency=medium
 .
   * Update d/watch, due to stripped components repack with +ds suffix
   * New upstream version 0.2.3+ds, Closes: #883762
   * Refresh d/Use-Astropy-in-place-of-Pyfits.patch, don't patch removed files
   * Add lintian-overrides for typos in lib, reported to upstream
   * Bump Standards-Version to 4.1.2
Checksums-Sha1:
 e600240be58912f3503811c14fe0ad3923e1b9d0 2309 pyscanfcs_0.2.3+ds-1.dsc
 1f013f5af8d8443eedb70b2204e8606f2790baaa 481320 pyscanfcs_0.2.3+ds.orig.tar.xz
 adbcd8c956362601990fd7a1c26114aaed01fa30 4804 
pyscanfcs_0.2.3+ds-1.debian.tar.xz
 59a774725bbe2aa8a273f4570bd051be14dcbce6 145568 
pyscanfcs-dbgsym_0.2.3+ds-1_amd64.deb
 2f6c35bb9511ce4a1fdeb50295dc0fa5f61f69ec 14575 
pyscanfcs_0.2.3+ds-1_amd64.buildinfo
 f613dc43d4047948c6fc0c580f28bc6350696678 531792 pyscanfcs_0.2.3+ds-1_amd64.deb
Checksums-Sha256:
 abeb4cfbbf0cf9621bc60ae05f1cf744fd82fa5e2d76ccca03a0ea201a4d28a7 2309 
pyscanfcs_0.2.3+ds-1.dsc
 3282c251870a65ca15c2ae0a57675284f38ba512229b7a2b33437bfd6deae2e4 481320 
pyscanfcs_0.2.3+ds.orig.tar.xz
 7395ddf2901451bef60aedfb87279785c5cc68e51f7d049596846449ee2d8651 4804 
pyscanfcs_0.2.3+ds-1.debian.tar.xz
 46b954b7821e6a63d007b07d78aed4c5793de4969c9a56e5639b740d567daa9b 145568 
pyscanfcs-dbgsym_0.2.3+ds-1_amd64.deb
 8d1eaf4aeea0982e824e70ab6708be7b72b03d2f6a59b13451e2ef04bb1491da 14575 
pyscanfcs_0.2.3+ds-1_amd64.buildinfo
 842f9113723f9a8a075b714f8e3138779958f5e4494c04ef4a9df140634d11c3 531792 
pyscanfcs_0.2.3+ds-1_amd64.deb
Files:
 ec1d3c2082e4b9fb387ced07d1b3e6e7 2309 python optional pyscanfcs_0.2.3+ds-1.dsc
 bd95ed5fd8c4dc8c36b2db1e783ed6c2 481320 python optional 
pyscanfcs_0.2.3+ds.orig.tar.xz
 41a6fde8d05a5a03e45c654917dbf634 4804 python optional 
pyscanfcs_0.2.3+ds-1.debian.tar.xz
 f06f67a534302181ad2848602b22a3af 145568 debug optional 
pyscanfcs-dbgsym_0.2.3+ds-1_amd64.deb
 a956dbd3aaa4e62e9629e88d90602e06 14575 python optional 
pyscanfcs_0.2.3+ds-1_amd64.buildinfo
 9e7b2caed7df2ade1d15776b90f26d13 531792 python optional 
pyscanfcs_0.2.3+ds-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJaKWKSAAoJEBz3khEbUiiwW6cQALCrC5cijC50wQpznWp75WvV
J7YUZDyqJ/zvZ6+H8SvWHHnIUlhrFJ5slPzcGqhvDPkaojDCW7ZpjRPolr18o2ws
Wt/+aPJsZuBgBCOFUVql8Ctp0LnCgH8AZDl/drFXoK3u6XiyXjlFK9KeNfAz4kYR
QSrJjivTEdFweJUtMTDCrTSV+o6sFqtotgH7+WJYquIlJGF0xVNjubYuWrKN9ep1
7lofBfQYu9UXLUlE8iH0kWLIuaNaJlMO

Bug#883621: [PKG-Openstack-devel] Bug#883621: CVE-2017-17051 not fixed?

[Salvatore Bonaccorso]

Hi Thomas,

On Thu, Dec 07, 2017 at 09:45:01AM +0100, Thomas Goirand wrote:
> On 12/06/2017 09:34 PM, Salvatore Bonaccorso wrote:
> > Hi Thomas,
> > 
> > CVE-2017-17051 was not fixed afaics, only the regression which was
> > introduced by OSSA-2017-005.
> > 
> > See http://www.openwall.com/lists/oss-security/2017/12/05/5 for
> > CVE-2017-17051.
> > 
> > Could you relook?
> > 
> > Regards,
> > Salvatore
> 
> Hi Salvatore,
> 
> Indeed, I misunderstood how upstream fixed the problem, and failed to
> see that there was 2 patches, the announces were indeed a bit confusing.
> Thanks a lot for finding this out, and ensuring that I did the proper
> fix. I'll try to push upstream to make a new release of Nova, so that
> we've got better assurance all issues are addressed.
> 
> I've already applied upstream patch, the package is building, and I will
> upload it shortly to Sid.

Thank you! I have updated the security-tracker recording the fixed
version.

Regards,
Salvatore

Processed: Version fix

[Debian Bug Tracking System]

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

> notfound 883785 3.10
Bug #883785 [libvirt] libvirtd 3.10 segfault when starting a VM
There is no source info for the package 'libvirt' at version '3.10' with 
architecture ''
Unable to make a source version for version '3.10'
No longer marked as found in versions 3.10.
> found 883785 3.10.0-1
Bug #883785 [libvirt] libvirtd 3.10 segfault when starting a VM
There is no source info for the package 'libvirt' at version '3.10.0-1' with 
architecture ''
Unable to make a source version for version '3.10.0-1'
Marked as found in versions 3.10.0-1.
> thanks
Stopping processing here.

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

Bug#883758: marked as done (scamp: Includes "doc/scamp.pdf" listed in Files-Excluded header)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2017 15:51:51 +
with message-id 
and subject line Bug#883758: fixed in scamp 2.0.4+dfsg-1
has caused the Debian Bug report #883758,
regarding scamp: Includes "doc/scamp.pdf" listed in Files-Excluded header
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.)


-- 
883758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883758
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scamp
Version: 2.0.4-5
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

scamp lists "doc/scamp.pdf" in the Files-Excluded field in
debian/copyright but the source tree contains doc/scamp.pdf.

This is probably a DFSG violation, or at the upstream tarball was not
repacked as intended. Alternatively, the field is simply out of date.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: scamp
Source-Version: 2.0.4+dfsg-1

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated scamp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 07 Dec 2017 16:27:54 +0100
Source: scamp
Binary: scamp
Architecture: source
Version: 2.0.4+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Description:
 scamp  - Compute astrometric and photometric solutions
Closes: 883758
Changes:
 scamp (2.0.4+dfsg-1) unstable; urgency=medium
 .
   * Remove non-dfsg-free PDF from upstream tarball. Closes: #883758
Checksums-Sha1:
 d3bb5ee54e9d367ff5073a39c8a3c6ab2bd45509 2053 scamp_2.0.4+dfsg-1.dsc
 4e33a10090723e8b716278d808eb1f3106072ee2 663393 scamp_2.0.4+dfsg.orig.tar.gz
 c148935bb13d12c97999ca6d2007abbcefb8ac29 5796 scamp_2.0.4+dfsg-1.debian.tar.xz
Checksums-Sha256:
 afd828426694ed0e03fedac767e3fc38bfe3585c621ec03e81b372c7d02ddafd 2053 
scamp_2.0.4+dfsg-1.dsc
 63267121c5f70a4403ee36e1375ddab73b5062f34929bdc0bd781bc936310083 663393 
scamp_2.0.4+dfsg.orig.tar.gz
 43fc0d9391d9f99e92086d53be7f51c05e87b73b1829cad1dad7d2dacc4acc8d 5796 
scamp_2.0.4+dfsg-1.debian.tar.xz
Files:
 2560f367b29d39af6bcd6f78e8877bfc 2053 science optional scamp_2.0.4+dfsg-1.dsc
 123e7210381511b3899331391f4d9753 663393 science optional 
scamp_2.0.4+dfsg.orig.tar.gz
 5229dc05bb61f9f2560301c0db77c97d 5796 science optional 
scamp_2.0.4+dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAlopXtEACgkQcRWv0HcQ
3PchJQ//b3YdJoA4QbDvjYbEGQ7LYttSmCE+Ao7yxzDnctHTP+Q186UoN2VGajhu
fNyh9O9BOVlBgfuvD0bHrQ6RIE0nH0+JYId5ZoQpOHYRGY5sGwTJo/y5hpFLdwIy
+/qN1gh8FSWKoPJP/3OTBTyXOMDgTaRGyqPEf3ixJ+UVARpKbpiiOFjgMqTklRx4
0heTtjt3b9F5NnngzqAzrXdU8Peg+iPTYsr2GvqnBA8wmfFgtQOgbjrO7Sn6js+1
uy4euBYHjZ+ig0qU+cneq0mC7/HwcW/1uUfHwQT4v4+t2gpuoMN09rKuY7cUoBDz
0bRV3mPIKRq0t9l3v/7wCTCnydCV5K0K0+JJnAsof6EifDP1oR6er2Gdj1s9iKq9
cY/B2AoR7+plfTEE2qVcArt+gnqi7BiQFInHK8SgPmThx0GLWRena0Q4+oFkVcoI
IYVyDk6KqA8blwn2i0S5CDzGcZiKtSJK2F4uj0BCnT9HRS9eWLDHHjPHKkS9uHTv
GoGd2WfzS3Ud3CQCl2U8sLKz4lIrPd9FYLQ5m8jrNh+e57wObs+bk+C23Pyef97+
q6u88yDZJ1oIego0EPf4WQYGGgojFdVTZi50qKgUHC0ngZNCXdUsxXd3D0vYz2dO
dVdImju8LEtuHm1XSLRdZPFxpKgMhCefBDxBM0BGhCeM0pFPaaw=
=TVwl
-END PGP SIGNATURE End Message ---

Bug#883762: marked as done (pyscanfcs: Includes "freeze_pyinstaller/PyScanFCS.icns" listed in Files-Excluded header)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2017 15:50:43 +
with message-id 
and subject line Bug#883762: fixed in pyscanfcs 0.2.3+dfsg-1
has caused the Debian Bug report #883762,
regarding pyscanfcs: Includes "freeze_pyinstaller/PyScanFCS.icns" listed in 
Files-Excluded header
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.)


-- 
883762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyscanfcs
Version: 0.2.3-5
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

pyscanfcs lists "freeze_pyinstaller/PyScanFCS.icns" in the Files-Excluded
field in debian/copyright but the source tree contains
freeze_pyinstaller/PyScanFCS.icns

This is probably a DFSG violation, or at the upstream tarball was not
repacked as intended. Alternatively, the field is simply out of date.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: pyscanfcs
Source-Version: 0.2.3+dfsg-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated pyscanfcs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 07 Dec 2017 16:16:46 +0100
Source: pyscanfcs
Binary: pyscanfcs
Architecture: source
Version: 0.2.3+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 pyscanfcs  - scientific tool for perpendicular line scanning FCS
Closes: 883762
Changes:
 pyscanfcs (0.2.3+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * Repack upstream source + adapt quilt patch
 Closes: #883762
   * d/watch: version-mangle according to repackaging
Checksums-Sha1:
 d2ebfece37a6f1f76aafa0fce44bd06c112ced2b 2380 pyscanfcs_0.2.3+dfsg-1.dsc
 1f013f5af8d8443eedb70b2204e8606f2790baaa 481320 
pyscanfcs_0.2.3+dfsg.orig.tar.xz
 6ee97639e93276cefa22a66e6ef7371e25d48687 4568 
pyscanfcs_0.2.3+dfsg-1.debian.tar.xz
 c109bc39b3c3a968a8618dc07df0beb2de6389f1 13942 
pyscanfcs_0.2.3+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 74fab75e0d41a9a8985f3ba33635437a860ac086a0f512939f9673b666d74a76 2380 
pyscanfcs_0.2.3+dfsg-1.dsc
 3282c251870a65ca15c2ae0a57675284f38ba512229b7a2b33437bfd6deae2e4 481320 
pyscanfcs_0.2.3+dfsg.orig.tar.xz
 e9075a1005287a3feff2e8c7f315c4f75525340997f019c7520c759dee388e9f 4568 
pyscanfcs_0.2.3+dfsg-1.debian.tar.xz
 b46e0353c9f46a9e12270e1951aaa9e219ab190a08f913fa50042ad83b5e0939 13942 
pyscanfcs_0.2.3+dfsg-1_amd64.buildinfo
Files:
 800198e9c7c69d6ecad1d4341138ceeb 2380 python optional 
pyscanfcs_0.2.3+dfsg-1.dsc
 bd95ed5fd8c4dc8c36b2db1e783ed6c2 481320 python optional 
pyscanfcs_0.2.3+dfsg.orig.tar.xz
 f67edfa4fa23ba8a55f14bb907d68b83 4568 python optional 
pyscanfcs_0.2.3+dfsg-1.debian.tar.xz
 f5098800e62099d642f668d56539b96a 13942 python optional 
pyscanfcs_0.2.3+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlopYIsRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGshg/+NUcNzp8bbHpT/4swkpcN1IrMOFd4R+LH
cWKeytsWXdaXU0lnGzZNADEMeCDOMl7V3F/4YSqB7snQd41hVZ5oyBAjKNE/0MIU
gCjPFGefyYJe2J8m2lJ5jIcSiF9EA9NAI+xrkOKLfsKiHFVYdFjvvx/UEguoMrlo
WL0UnbuM0fLEhdNTY0XN6CRT4hLyabfuzTw8GOS2HSnjD2Xir78lkDyISMt+fzO0
QhiSi8ZFuh/vKkoG3dVgvOtGtBv/jVv218jpIfI6A68uzwsYdZw2ORXvfbgViAB1
sguS+/3S4sGzx95XXmxLQUAwGy/KQB6+lvt2mud2fvR2ffZ9qC/4MZaKODckzkR1
WLa4JzFnVcq4DnJ72AFQtjo/6xfcFrrpP9gvEauY5j2/S5KaS05CZqSb/y8pWM/J
fLur33g0m9AB95lCqsDZ1tpHr3CzP1E0BPiAwYixrtH8xXlklYVtvDQJvgk69q34
npKn1FNvQg8psJPTXyUJ3aZ4GVh6sMV6+4hUnWt8LA5oHMSQdmKjlOf0Ow4ge/xL
hQ7U2ivyP1bLbacboHTESCczFnhKlqy+i6pn2LayZb5luOfR6/GrNP928lQTPs4i
x0cb9itH1l07zkOiYJ+imNr8VdQjElB+1tt+JgB8hqHQACcAc6LRZ8dWpZvF4oE/
bN9EpeHqm84=
=vydy
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#883791: r-cran-scatterd3: Please clarify source of embedded D3 Lasso

[Debian Bug Tracking System]

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

> retitle 883791 r-cran-scatterd3: Please clarify source of embedded D3 Lasso
Bug #883791 [r-cran-scatterd3] r-cran-scatterd3: Does not include the source 
for D3 Lasso
Changed Bug title to 'r-cran-scatterd3: Please clarify source of embedded D3 
Lasso' from 'r-cran-scatterd3: Does not include the source for D3 Lasso'.
> severity 883791 wishlist
Bug #883791 [r-cran-scatterd3] r-cran-scatterd3: Please clarify source of 
embedded D3 Lasso
Severity set to 'wishlist' from 'serious'
> thanks
Stopping processing here.

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

Processed: Clone & reassign

[Debian Bug Tracking System]

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

> clone 882999 -1
Bug #882999 [bind9] bind9: fails to purge: rmdir: failed to remove 
'/var/lib/bind': No such file or directory
Bug 882999 cloned as bug 883795
> reassign -1 dms-core
Bug #883795 [bind9] bind9: fails to purge: rmdir: failed to remove 
'/var/lib/bind': No such file or directory
Bug reassigned from package 'bind9' to 'dms-core'.
No longer marked as found in versions bind9/1:9.10.6+dfsg-5.
Ignoring request to alter fixed versions of bug #883795 to the same values 
previously set
> severity -1 serious
Bug #883795 [dms-core] bind9: fails to purge: rmdir: failed to remove 
'/var/lib/bind': No such file or directory
Severity set to 'serious' from 'important'
> retitle -1 dms-core: dms-core.postrm removes /var/lib/bind9 on purge
Bug #883795 [dms-core] bind9: fails to purge: rmdir: failed to remove 
'/var/lib/bind': No such file or directory
Changed Bug title to 'dms-core: dms-core.postrm removes /var/lib/bind9 on 
purge' from 'bind9: fails to purge: rmdir: failed to remove '/var/lib/bind': No 
such file or directory'.
>
End of message, stopping processing here.

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

Bug#875688: libreoffice-report-builder: report builder inactive in 5.4

[Lionel Elie Mamane]

retitle 875688 report builder inactive; only legacy reports can be created and 
run
thanks

For clarity, there are two reporting systems in LibreOffice:

1) Report Design (entirely in C++), the "old legacy one".

2) Report Builder, which used to be an extension, then was a bundled
   extension, and then became an optional but integrated part of
   LibreOffice (installed by default, but optional).

The Debian package of 5.4 behaves as if the optional part of
LibreOffice "Report Builder" was not installed, although the packages
libreoffice-report-builder and libreoffice-report-builder-bin are
installed. I haven't diagnosed why.

The immediate cause is that in file
 dbaccess/source/ui/misc/linkeddocuments.cxx
 function OLinkedDocumentsAccess::open, the call to impl_open throws a
 css::io::WrongFormatException,
but what is the underlying reason for that? Probably the internal
LibreOffice registry doesn't have properly registered the optional
"Report Builder" part (could be an error in
/usr/lib/libreoffice/share/registry/reportbuilder.xcd or that file is
not loaded), or it fails to load for some reason.

Processed: Bug#875688: libreoffice-report-builder: report builder inactive in 5.4

[Debian Bug Tracking System]

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

> retitle 875688 report builder inactive; only legacy reports can be created 
> and run
Bug #875688 [libreoffice-report-builder] libreoffice-report-builder: Design 
view missing from libre office base. Existing reports won't run.
Changed Bug title to 'report builder inactive; only legacy reports can be 
created and run' from 'libreoffice-report-builder: Design view missing from 
libre office base. Existing reports won't run.'.
> thanks
Stopping processing here.

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

Bug#883791: r-cran-scatterd3: Does not include the source for D3 Lasso

[Andreas Tille]

Hi Chris,

On Thu, Dec 07, 2017 at 03:27:06PM +, Chris Lamb wrote:
> Package: r-cran-scatterd3
> Version: 0.8.1+dfsg-2
> Severity: serious
> 
> Hi (again!),
> 
> The debian/copyright of r-cran-scatterd3 includes the following line:
> 
>   Files: inst/htmlwidgets/lib/d3-lasso-plugin/*
>   Copyright: 2015-2016, Speros Kokenes
>   License: BSD-3-clause
>   Comment: Source is available at https://github.com/skokenes/D3-Lasso-Plugin
> 
> This unfortunately violates the DFSG "desert island" test. :)

Seems we are playing bug ping-pong around r-cran-scatterd3.  In how far
does the *Comment* violate anything?  The uncompressed source is inside
r-cran-scatterd3 source package.  I just wanted to drop a comment where
this JS can be found in case upstream might decide to replace it by a
compressed version.

I'm afraid this is also a false positive.

Kind regards and thanks for your QA checking in any case

  Andreas.

-- 
http://fam-tille.de

Bug#876840: fseeko() on reference file: Invalid argument (Was: Bug#876840: staden-io-lib FTBFS on non-i386 32bit: FAIL: java)

[Andreas Tille]

Hi,

On Thu, Dec 07, 2017 at 02:40:36PM +, James Bonfield wrote:
> On Tue, Dec 05, 2017 at 08:02:18AM +0100, Andreas Tille wrote:
> > this is a kind ping since as I wrote below the issue seems not be solved.
> 
> I'm not sure I can easily debug this as it only fails on systems I
> have no access to; it's like trying to debug your grandmother's
> windows desktop over the phone...
> 
> I'm still convinced it's something to do with large file support not
> working correctly, likely with off_t being the wrong size.  Especially
> given the 64-bit mips build works while the 32-bit one does not.  I
> assume everything else about these architectures are the same.
> 
> We don't have any 32-bit build systems any more though.
> 
> > > > Does adding that fix the fseeko call to start working again?
> > > 
> > > Unfortunately not - see here the build logs:
> > > 
> > > https://buildd.debian.org/status/package.php?p=staden-io-lib
> 
> James
> -- 
> James Bonfield (j...@sanger.ac.uk) | Hora aderat briligi. Nunc et Slythia Tova


I'm just forwarding this to debian-arm and debian-mips.  I see no other
chance to deal with this bug rather than removing these architectures
from the architectures field.

Do you have any better suggestion? 

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#883791: r-cran-scatterd3: Does not include the source for D3 Lasso

[Chris Lamb]

Package: r-cran-scatterd3
Version: 0.8.1+dfsg-2
Severity: serious

Hi (again!),

The debian/copyright of r-cran-scatterd3 includes the following line:

  Files: inst/htmlwidgets/lib/d3-lasso-plugin/*
  Copyright: 2015-2016, Speros Kokenes
  License: BSD-3-clause
  Comment: Source is available at https://github.com/skokenes/D3-Lasso-Plugin

This unfortunately violates the DFSG "desert island" test. :)


Regards,

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

Bug#883764: marked as done (r-cran-scatterd3: Includes files listed in Files-Excluded header)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2017 15:07:45 +
with message-id 
<1512659265.3072696.1197351064.0629c...@webmail.messagingengine.com>
and subject line Re: Bug#883764: r-cran-scatterd3: Includes files listed in 
Files-Excluded header
has caused the Debian Bug report #883764,
regarding r-cran-scatterd3: Includes files listed in Files-Excluded header
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.)


-- 
883764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-scatterd3
Version: 0.8.1+dfsg-2
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

r-cran-scatterd3 lists "*/d3*.min.js" in the Files-Excluded field in
debian/copyright but the source tree contains
inst/htmlwidgets/lib/d3-legend.min.js.

This is probably a DFSG violation, or at the upstream tarball was not
repacked as intended. Alternatively, the field is simply out of date.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Hi Andreas,

> I think that's a false positive:
> 
[…]
> $ apt-get source r-cran-scatterd3
> $ tar -taf r-cran-scatterd3_0.8.1+dfsg.orig.tar.xz | grep min\.js

Indeed; sorry. Fixed here:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=a088031654c5a419d5f3dad93a3907fac1e1d078

Closing bug...


Regards,

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

Bug#883342: marked as done (asterisk: CVE-2017-17090: DOS Vulnerability in Asterisk chan_skinny)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2017 15:04:08 +
with message-id 
and subject line Bug#883342: fixed in asterisk 1:13.18.3~dfsg-1
has caused the Debian Bug report #883342,
regarding asterisk: CVE-2017-17090: DOS Vulnerability in Asterisk chan_skinny
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.)


-- 
883342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asterisk
Version: 1:13.18.1~dfsg-1
X-Debbugs-CC: t...@security.debian.org 
secure-testing-t...@lists.alioth.debian.org
Severity: grave
Tags: security fixed-upstream upstream
Forwarded: https://issues.asterisk.org/jira/browse/ASTERISK-27452

Hi,

the following vulnerability was published for asterisk.

CVE-2017-17090[0]:
| An issue was discovered in chan_skinny.c in Asterisk Open Source
| 13.18.2 and older, 14.7.2 and older, and 15.1.2 and older, and
| Certified Asterisk 13.13-cert7 and older. If the chan_skinny (aka SCCP
| protocol) channel driver is flooded with certain requests, it can cause
| the asterisk process to use excessive amounts of virtual memory,
| eventually causing asterisk to stop processing requests of any kind.

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-2017-17090
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17090
[1] https://issues.asterisk.org/jira/browse/ASTERISK-27452
[2] http://downloads.asterisk.org/pub/security/AST-2017-013.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: asterisk
Source-Version: 1:13.18.3~dfsg-1

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

Debian distribution maintenance software
pp.
Bernhard Schmidt  (supplier of updated asterisk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 07 Dec 2017 15:20:29 +0100
Source: asterisk
Binary: asterisk asterisk-modules asterisk-dahdi asterisk-vpb 
asterisk-voicemail asterisk-voicemail-imapstorage 
asterisk-voicemail-odbcstorage asterisk-ooh323 asterisk-mp3 asterisk-mysql 
asterisk-mobile asterisk-tests asterisk-doc asterisk-dev asterisk-config
Architecture: source
Version: 1:13.18.3~dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Bernhard Schmidt 
Description:
 asterisk   - Open Source Private Branch Exchange (PBX)
 asterisk-config - Configuration files for Asterisk
 asterisk-dahdi - DAHDI devices support for the Asterisk PBX
 asterisk-dev - Development files for Asterisk
 asterisk-doc - Source code documentation for Asterisk
 asterisk-mobile - Bluetooth phone support for the Asterisk PBX
 asterisk-modules - loadable modules for the Asterisk PBX
 asterisk-mp3 - MP3 playback support for the Asterisk PBX
 asterisk-mysql - MySQL database protocol support for the Asterisk PBX
 asterisk-ooh323 - H.323 protocol support for the Asterisk PBX - ooH323c
 asterisk-tests - internal test modules of the Asterisk PBX
 asterisk-voicemail - simple voicemail support for the Asterisk PBX
 asterisk-voicemail-imapstorage - IMAP voicemail storage support for the 
Asterisk PBX
 asterisk-voicemail-odbcstorage - ODBC voicemail storage support for the 
Asterisk PBX
 asterisk-vpb - VoiceTronix devices support for the Asterisk PBX
Closes: 883342
Changes:
 asterisk (1:13.18.3~dfsg-1) unstable; urgency=medium
 .
   * New upstream version 13.18.3~dfsg
 - CVE-2017-17090 / AST-2017-013
   DOS Vulnerability in Asterisk chan_skinny (Closes: #883342)
   * Drop duplicate filter line from d/gbp.conf
Checksums-Sha1:
 8206f7a44506678906afab0e69876fffc132fcc0 4243 asterisk_13.18.3~dfsg-1.dsc
 e0b838e5478dfcdac0c20840ec9a77af021b7bf7 6274896 
asterisk_13.18.3~dfsg.orig.tar.xz
 6711dddc4e56c7d9504e0be511e051988f3d73c8 168724 
asterisk_13.18.3~dfsg-1.debian.tar.xz
 5bd0248bfe0bfc6758153afa3efe1300e03b3556 27544 
asterisk_13.18.3~

Bug#876840: fseeko() on reference file: Invalid argument (Was: Bug#876840: staden-io-lib FTBFS on non-i386 32bit: FAIL: java)

[James Bonfield]

On Tue, Dec 05, 2017 at 08:02:18AM +0100, Andreas Tille wrote:
> this is a kind ping since as I wrote below the issue seems not be solved.

I'm not sure I can easily debug this as it only fails on systems I
have no access to; it's like trying to debug your grandmother's
windows desktop over the phone...

I'm still convinced it's something to do with large file support not
working correctly, likely with off_t being the wrong size.  Especially
given the 64-bit mips build works while the 32-bit one does not.  I
assume everything else about these architectures are the same.

We don't have any 32-bit build systems any more though.

> > > Does adding that fix the fseeko call to start working again?
> > 
> > Unfortunately not - see here the build logs:
> > 
> > https://buildd.debian.org/status/package.php?p=staden-io-lib

James
-- 
James Bonfield (j...@sanger.ac.uk) | Hora aderat briligi. Nunc et Slythia Tova
  | Plurima gyrabant gymbolitare vabo;
  A Staden Package developer: | Et Borogovorum mimzebant undique formae,
https://sf.net/projects/staden/   | Momiferique omnes exgrabure Rathi. 


-- 
 The Wellcome Trust Sanger Institute is operated by Genome Research 
 Limited, a charity registered in England with number 1021457 and a 
 company registered in England with number 2742969, whose registered 
 office is 215 Euston Road, London, NW1 2BE. 

Bug#883764: r-cran-scatterd3: Includes files listed in Files-Excluded header

[Andreas Tille]

Hi Chris,

On Thu, Dec 07, 2017 at 10:22:15AM +, Chris Lamb wrote:
> 
> r-cran-scatterd3 lists "*/d3*.min.js" in the Files-Excluded field in
> debian/copyright but the source tree contains
> inst/htmlwidgets/lib/d3-legend.min.js.

I think that's a false positive:


$ apt-get source r-cran-scatterd3
$ tar -taf r-cran-scatterd3_0.8.1+dfsg.orig.tar.xz | grep min\.js
$

Am I missing something?

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#883787: ntopng: Error "Missing CSRF parameter" in "Manage users" and "Preferences"

[Daniel Aubry]

Package: ntopng
Version: 2.4+dfsg1-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

This is fixed in ntopng/2.4+dfsg1-4 which is not available on debian stretch.

Please see bug #856048 for more details.

It is not possible to access the "Manage users" and "Preferences" links on
the web interface. Both will display an error message:

 Script "/lua/admin/users.lua" returned an error:
 Missing CSRF parameter

 Script "/lua/admin/prefs.lua" returned an error:
 Missing CSRF parameter


This is the important changelog entry of version 2.4+dfsg1-4

  * Update Check-for-presence-of-crsf-in-admin-scripts.patch to avoid the
'Missing CSRF parameter' error (Closes: #856048).


Best Reards
Daniel

-- System Information:
Debian Release: 9.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages ntopng depends on:
ii  init-system-helpers  1.48
ii  libc62.24-11+deb9u1
ii  libcurl3-gnutls  7.52.1-5+deb9u3
ii  libgcc1  1:6.3.0-18
ii  libgeoip11.6.9-4
ii  libhiredis0.13   0.13.3-2
ii  libjson-c3   0.12.1-1.1
ii  libluajit-5.1-2  2.0.4+dfsg-1+b1
ii  libmariadbclient18   10.1.26-0+deb9u1
ii  libndpi4 1.8-1
ii  libpcap0.8   1.8.1-3
ii  librrd8  1.6.0-1+b2
ii  libsqlite3-0 3.16.2-5
ii  libstdc++6   6.3.0-18
ii  libzmq5  4.2.1-4
ii  lsb-base 9.20161125
ii  ntopng-data  2.4+dfsg1-3
ii  redis-server 3:3.2.6-1
ii  zlib1g   1:1.2.8.dfsg-5

ntopng recommends no packages.

Versions of packages ntopng suggests:
pn  geoip-database-contrib  

-- no debconf information

Bug#883785: libvirtd 3.10 segfault when starting a VM

[Pascal Obry]

Package: libvirt
Version: 3.10
Severity: grave

With libvirt version 3.10 I cannot start a VM. Reverting to 3.0
(Debian/stable) all is fine. This was initially found in GNOME-Boxes
but I have been able to reproduce on the command line using virsh.

Note also that I had the same issue with 3.9.

On one console:

$ LIBVIRT_DEBUG=1 gdb /usr/sbin/libvirtd

On a second console, I tried to start the VM:

$ virsh start boxes-winxp

Then I got this exception from libvirtd:

Thread 5 "libvirtd" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7febad4a5700 (LWP 7867)]
0x7feb94b109c8 in virStorageFileReportBrokenChain ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_storage.so
(gdb) bt
#0  0x7feb94b109c8 in virStorageFileReportBrokenChain ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_storage.so
#1  0x7feb7d266da3 in qemuDomainDetermineDiskChain ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
#2  0x7feb7d28eec2 in qemuProcessPrepareHost ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
#3  0x7feb7d294b71 in qemuProcessStart ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
#4  0x7feb7d2f5201 in ?? ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
#5  0x7feb7d2f58e6 in ?? ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
#6  0x7febb9e5e077 in virDomainCreate (domain=0x7feb980008c0)
at ../../../src/libvirt-domain.c:6531
#7  0x56190ba2ed9c in ?? ()
#8  0x7febb9ec697c in virNetServerProgramDispatchCall (msg=0x56190d9e7590, 
client=0x56190d9e6fb0, server=0x56190d9d00f0, prog=0x56190d9e4f40)
at ../../../src/rpc/virnetserverprogram.c:437
#9  virNetServerProgramDispatch (prog=0x56190d9e4f40, server=0x56190d9d00f0, 
client=0x56190d9e6fb0, msg=0x56190d9e7590)
at ../../../src/rpc/virnetserverprogram.c:307
#10 0x56190ba3e988 in ?? ()
#11 0x7febb9da1c01 in virThreadPoolWorker (
opaque=opaque@entry=0x56190d9ce9f0)
at ../../../src/util/virthreadpool.c:167
#12 0x7febb9da0f78 in virThreadHelper (data=)
at ../../../src/util/virthread.c:206
#13 0x7febb68b0519 in start_thread (arg=0x7febad4a5700)
at pthread_create.c:456
#14 0x7febb65f2a5f in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
(gdb) 

I noticed that running with 3.0 I had a message saying that /dev/sr0 is
not accessible. And indeed I do not have a CDROM on this machine. The
.xml were migrated from a machine with a CDROM to this new one.

Removing:


  
  
  
  
  


Seems to fix the issue. Yet, libvirt should not crash on this. And the
backtrace makes sense with this fix BTW.

Please let me know if you need additional information.

Thanks,

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B

Bug#883778: problems building guile-2.0 on armel

[Steve McIntyre]

Package: guile-2.0
Version: 2.0.13+1-5
Severity: serious

Hi.

Putting this information into the BTS for posterity...

Trying to build guile-2.0/armel is currently crashing our buildds and
porter box. See

  https://buildd.debian.org/status/package.php?p=guile-2.0&suite=sid

at the moment - hartmann tried to build the package, but
crashed. Adrian Bunk says he's tried to build it on abel too, and that
caused the same issue. I've just tried a local rebuild here on the
same hardware as the buildds (Marvell Armada XP) and I see the same
issue. Unfortunately, there's no diagnostic output I can share. The
machine simply died overnight without even any kernel messages to show
for it.

I was also running top and displaying CPU temperature in a loop during
the build, with no problems shown at the point of failure.

Interestingly, in armhf mode the package builds just fine on the same
type of hardware (built ok on hoiby). Wondering what on earth is going
on...


-- System Information:
Debian Release: 9.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages guile-2.0 depends on:
ii  guile-2.0-libs  2.0.13+1-4

guile-2.0 recommends no packages.

Versions of packages guile-2.0 suggests:
pn  guile-2.0-doc  

-- no debconf information

Processed: fixed 883774 in 6.0.2-1

[Debian Bug Tracking System]

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

> fixed 883774 6.0.2-1
Bug #883774 [src:otrs2] otrs2: CVE-2017-16921: Remote code execution
Marked as fixed in versions otrs2/6.0.2-1.
> thanks
Stopping processing here.

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

Processed: otrs2: CVE-2017-16921: Remote code execution

[Debian Bug Tracking System]

Processing control commands:

> found -1 3.3.9-3
Bug #883774 [src:otrs2] otrs2: CVE-2017-16921: Remote code execution
Marked as found in versions otrs2/3.3.9-3.

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

Bug#883774: otrs2: CVE-2017-16921: Remote code execution

[Salvatore Bonaccorso]

Source: otrs2
Version: 5.0.16-1
Severity: grave
Tags: patch security upstream
Control: found -1 3.3.9-3

Hi,

the following vulnerability was published for otrs2.

The issue is related to improper handling of PGP parameters, as such I
think the issue is as well present back in the 3.3.x series (they are
not mentioned in the advisories since the 3.3.x series are not
supported anymore upstream).

CVE-2017-16921[0]:
OSA-2017-09: Remote code execution

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-2017-16921
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16921
[1] 
https://www.otrs.com/security-advisory-2017-09-security-update-otrs-framework/

Regards,
Salvatore

Bug#882680: marked as done (networking-ovn FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2017 13:37:43 +
with message-id 
and subject line Bug#882680: fixed in networking-ovn 3.0.0-1
has caused the Debian Bug report #882680,
regarding networking-ovn FTBFS: test failures
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.)


-- 
882680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: networking-ovn
Version: 1.0.0-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes networking-ovn FTBFS:

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/networking-ovn-1.0.0'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
ostestr
/usr/lib/python2.7/dist-packages/os_testr/ostestr.py:120: UserWarning: No 
.stestr.conf file found in the CWD. Please create one to to replace the 
.testr.conf. You can find a script to do this in the stestr git repository.
  warnings.warn(msg)

=
Failures during discovery
=
--- import errors ---
Failed to import test module: networking_ovn.tests.unit.common.test_acl
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "networking_ovn/tests/unit/common/test_acl.py", line 20, in 
from networking_ovn.common import acl as ovn_acl
  File "networking_ovn/common/acl.py", line 21, in 
from networking_ovn.common import config
  File "networking_ovn/common/config.py", line 65, in 
default=portbindings.VIF_TYPE_OVS,
AttributeError: 'module' object has no attribute 'VIF_TYPE_OVS'

Failed to import test module: networking_ovn.tests.unit.l3.test_l3_ovn
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "networking_ovn/tests/unit/l3/test_l3_ovn.py", line 25, in 
from networking_ovn.ovsdb import impl_idl_ovn
  File "networking_ovn/ovsdb/impl_idl_ovn.py", line 24, in 
from networking_ovn.common import config as cfg
  File "networking_ovn/common/config.py", line 65, in 
default=portbindings.VIF_TYPE_OVS,
AttributeError: 'module' object has no attribute 'VIF_TYPE_OVS'

Failed to import test module: networking_ovn.tests.unit.l3.test_l3_ovn_scheduler
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "networking_ovn/tests/unit/l3/test_l3_ovn_scheduler.py", line 21, in 

from networking_ovn.common import constants as ovn_const
  File "networking_ovn/common/constants.py", line 24, in 
OVN_PORT_BINDING_PROFILE = portbindings.PROFILE
AttributeError: 'module' object has no attribute 'PROFILE'

Failed to import test module: networking_ovn.tests.unit.ml2.test_mech_driver
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "networking_ovn/tests/unit/ml2/test_mech_driver.py", line 34, in 
from networking_ovn.common import acl as ovn_acl
  File "networking_ovn/common/acl.py", line 21, in 
from networking_ovn.common import config
  File "networking_ovn/common/config.py", line 65, in 
default=portbindings.VIF_TYPE_OVS,
AttributeError: 'module' object has no attribute 'VIF_TYPE_OVS'

Failed to import test module: networking_ovn.tests.unit.ml2.test_qos_driver
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/

Bug#882535: marked as done (glare requires internet access during the build)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2017 13:37:20 +
with message-id 
and subject line Bug#882535: fixed in glare 0.4.1-3
has caused the Debian Bug report #882535,
regarding glare requires internet access during the build
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.)


-- 
882535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882535
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glare
Version: 0.4.1-2
Severity: serious

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

...
==
FAIL: glare.tests.unit.test_store_api.TestStoreAPI.test_read_data
glare.tests.unit.test_store_api.TestStoreAPI.test_read_data
--
_StringException: Traceback (most recent call last):
  File "glare/tests/unit/test_store_api.py", line 66, in test_read_data
self.req.context
  File "glare/common/utils.py", line 449, in new_function
raise map_record['raise'](str(e))
glare.common.exception.BadRequest: Remote server where the image is present is 
unavailable.


--
Ran 251 tests in 72.988s

FAILED (failures=1, skipped=2)
debian/rules:25: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: glare
Source-Version: 0.4.1-3

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated glare package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 07 Dec 2017 13:19:38 +
Source: glare
Binary: glare-api glare-common python-glare
Architecture: source all
Version: 0.4.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 glare-api  - OpenStack Artifact Repository - API server
 glare-common - OpenStack Artifact Repository - common files
 python-glare - OpenStack Artifact Repository - Python 2.7 library
Closes: 882535
Changes:
 glare (0.4.1-3) unstable; urgency=medium
 .
   * Fixed requires internet access during the build (Closes: #882535).
Checksums-Sha1:
 7cd620bf7d7740eac4415947039b7d6861b53a7f 3588 glare_0.4.1-3.dsc
 6982534fec4ab1347319ef327ca5e92cbc2cd199 23664 glare_0.4.1-3.debian.tar.xz
 bff19fc78c29e10534c6a0730a4bfff0bbd6a056 19240 glare-api_0.4.1-3_all.deb
 e969384e37941dd953533ede5838ef00f27da3a8 41460 glare-common_0.4.1-3_all.deb
 8a6e511a6def51a92e3ef7b0b64d21941b2b2d65 15353 glare_0.4.1-3_amd64.buildinfo
 2b41e5f82161563f05ccf5c79f4c324fa61f7276 125132 python-glare_0.4.1-3_all.deb
Checksums-Sha256:
 38aced5e00e435605f5b7c41dd39854d36ea307b78322d95fe8f92a5e4ba875f 3588 
glare_0.4.1-3.dsc
 191077f5b8b136338b0e12b5c8db75ebb1902a53ef61b6cbd9ed36ac1c44ae28 23664 
glare_0.4.1-3.debian.tar.xz
 9b84757fa65a15d134c402dfed163e73b62df6fa2c2436d82e640cb0a5f5a33d 19240 
glare-api_0.4.1-3_all.deb
 a07c0160899b11dab3914ecf5dd967f242ab1aabd8aa4b8eacf7a969c91aba29 41460 
glare-common_0.4.1-3_all.deb
 be595ad67e79ffc97916f12ff64f64b419489764dfd6b106bd744c0aa47b80ff 15353 
glare_0.4.1-3_amd64.buildinfo
 77c23f641e12c74364014a3bf340f68f80bf84858d504e49c19c24ece9d70bb9 125132 
python-glare_0.4.1-3_all.deb
Files:
 ce7beeb04f15bb1f5b3efd099a2da728 3588 net optional glare_0.4.1-3.dsc
 50d744f89637ea366533bbade28ebad7 23664 net optional glare_0.4.1-3.debian.tar.xz
 2aebac9d89c9e00950f814a0398dc7d4 19240 net optional glare-api_0.4.1-3_all.deb
 4492202e8fad3ea341e3ccc509b1736b 41460 net optional 
glare-common_0.4.1-3_all.deb
 ca53999c7dc2f56dbb038d80d8be729c 15353 net optional 
glare_0.4.1-3_amd64.buildinfo
 7187c37741fbdfa0e3c979dc1a620d7d 125132 python optional 
python-glare_0.4.1-3_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAlopQNUACgkQ1BatFaxr
Q/4SSA/+PuLKvHVLAAATXcrVaL2qJVPNTs43yV70Gy05g6HGt6KH3bLNrjz/O9Qe
btqIMJlpE6XNFQ8c3sGvfxnwr5SSap6gRqUxvtuvXafTJ3TwJEta+pX

Processed: Bug#882535 marked as pending

[Debian Bug Tracking System]

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

> tag 882535 pending
Bug #882535 [src:glare] glare requires internet access during the build
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#882535: marked as pending

[Thomas Goirand]

tag 882535 pending
thanks

Hello,

Bug #882535 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/openstack/services/glare.git/commit/?id=da8e9ab

---
commit da8e9ab929fc456da222df479737b8b419a67d56
Author: Thomas Goirand 
Date:   Thu Dec 7 13:21:04 2017 +

Fixed requires internet access during the build (Closes: #882535).

diff --git a/debian/changelog b/debian/changelog
index a7ec627..5de125e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+glare (0.4.1-3) unstable; urgency=medium
+
+  * Fixed requires internet access during the build (Closes: #882535).
+
+ -- Thomas Goirand   Thu, 07 Dec 2017 13:19:38 +
+
 glare (0.4.1-2) unstable; urgency=medium
 
   * Uploading to unstable.

Bug#872305: diaspora: Package fails to install

[Joseph Nuthalapati]

Tried a lot to reproduce this bug but it is not reproducible.
I don't see any permissions issues in the debian installation scripts
either.

Closing this.

Regards,
Joseph Nuthalapati




signature.asc
Description: OpenPGP digital signature

Processed: Bug#883732 marked as pending

[Debian Bug Tracking System]

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

> tag 883732 pending
Bug #883732 [src:flask-migrate] flask-migrate FTBFS: test failures
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#883732: marked as pending

[Christoph Berg]

tag 883732 pending
thanks

Hello,

Bug #883732 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/python-modules/packages/flask-migrate.git/commit/?id=da8c6cf

---
commit da8c6cf5e012d77820134f03ead3cf10a69ed76b
Author: Christoph Berg 
Date:   Thu Dec 7 13:26:40 2017 +0100

debian/rules: Set LC_ALL=C.UTF-8 to make "Click" happy under python3.

RuntimeError: Click will abort further execution because Python 3 was 
configured to use ASCII as encoding for the environment.  Consult 
http://click.pocoo.org/python3/for mitigation steps.\n\nThis system supports 
the C.UTF-8 locale which is recommended.\nYou might be able to resolve your 
issue by exporting the\nfollowing environment variables:\n\nexport 
LC_ALL=C.UTF-8\nexport LANG=C.UTF-8\n'

Closes: #883732

diff --git a/debian/changelog b/debian/changelog
index 5d3af16..bc4c287 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+flask-migrate (2.1.1-2) unstable; urgency=medium
+
+  * Team upload.
+  * debian/rules: Set LC_ALL=C.UTF-8 to make "Click" happy under python3.
+(Closes: #883732)
+
+ -- Christoph Berg   Thu, 07 Dec 2017 13:23:17 
+0100
+
 flask-migrate (2.1.1-1) unstable; urgency=medium
 
   * Team upload.

Bug#853599: opensurgsim: ftbfs with GCC-7

[Andreas Tille]

Pushed, sorry for not doing earlier, Andreas.

On Thu, Dec 07, 2017 at 12:38:09PM +0100, Fabian Klötzl wrote:
> Hi Andreas,
> 
> While I am fixing this bug, could you please push your changes? There is
> a 0.7.0-5 in the archives but not in the git repo.
> 
> See also https://qa.debian.org/cgi-bin/vcswatch?package=opensurgsim
> 
> Best,
> Fabian
> 
> 

-- 
http://fam-tille.de

Bug#853599: Bug#853599: opensurgsim: ftbfs with GCC-7

[Fabian Klötzl]

Hi Andreas,

While I am fixing this bug, could you please push your changes? There is
a 0.7.0-5 in the archives but not in the git repo.

See also https://qa.debian.org/cgi-bin/vcswatch?package=opensurgsim

Best,
Fabian

Bug#882720: marked as done (src:fossil: Contains generated file autosetup/jimsh0.c)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2017 11:04:44 +
with message-id 
and subject line Bug#882720: fixed in fossil 1:2.4-1
has caused the Debian Bug report #882720,
regarding src:fossil: Contains generated file autosetup/jimsh0.c
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.)


-- 
882720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fossil
Severity: serious

jimsh0.c is a generated bootstrap version of jimtcl. Please
repackage the tarball to remove it, and build-depend on jimtcl
instead (for example).

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en
--- End Message ---
--- Begin Message ---
Source: fossil
Source-Version: 1:2.4-1

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

Debian distribution maintenance software
pp.
Barak A. Pearlmutter  (supplier of updated fossil package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 07 Dec 2017 10:41:26 +
Source: fossil
Binary: fossil
Architecture: source amd64
Version: 1:2.4-1
Distribution: unstable
Urgency: medium
Maintainer: Barak A. Pearlmutter 
Changed-By: Barak A. Pearlmutter 
Description:
 fossil - DSCM with built-in wiki, http interface and server, tickets datab
Closes: 882720
Changes:
 fossil (1:2.4-1) unstable; urgency=medium
 .
   * New upstream version
   * Bump debian standards version
   * Use https URL for upstream pull in README.Debian
   * Repack upstream tarball to remove autosetup/jimsh0.c (closes: #882720)
   * ./configure --with-tcl-private-stubs or it won't compile dunno why
   * Correct some minor spelling errors
   * Repack upstream tarball to remove *.chm file
   * Remove redundant-in-dh10 autotools-dev materials
Checksums-Sha1:
 d8163435905dae3b64d7ba7657c3a5fbc979b9dd 1803 fossil_2.4-1.dsc
 800aaf8d628565cbb0b7695c9d1803289f1b311e 4794139 fossil_2.4.orig.tar.gz
 64940be6e2df29cae58892385c02b33d7fe963fc 23832 fossil_2.4-1.debian.tar.xz
 4b244bb979852106ceb933b80ddd2455974a4b42 3304292 fossil-dbgsym_2.4-1_amd64.deb
 50724d4eaea1a56a9847a2b21c99bbe5a803fd1f 6316 fossil_2.4-1_amd64.buildinfo
 a3528c69b460a9b241f14c7ad6d9a26f47766fa1 775056 fossil_2.4-1_amd64.deb
Checksums-Sha256:
 4dbfd3a7eec4ab802bdc50cc6c853c82ad548b01e98736be477b66e07b5ecda8 1803 
fossil_2.4-1.dsc
 5ba46062f408b82ad048cd6e31dc3424ee8f8bd4b1e85ca43b8c41afbedebe14 4794139 
fossil_2.4.orig.tar.gz
 e7c14ac58aa6c187522729e45e886afe61d76f4c4cca976ffe0c21958da14560 23832 
fossil_2.4-1.debian.tar.xz
 d3eab1f1a61d283b741f17f5aea8eaa90c60ce6b630ee524486cd76fbaa2dde3 3304292 
fossil-dbgsym_2.4-1_amd64.deb
 8ac31f9ea72aad8c04e4b25cbfc57bd5e2c6e18173729d8fbc2d51d40cd96e79 6316 
fossil_2.4-1_amd64.buildinfo
 13a0706e55d9c9f7ec8e51e4ccb9ee52d7710759a26c115e3a4a4cc5b30cba75 775056 
fossil_2.4-1_amd64.deb
Files:
 710a4c24df28ad904273fa13a33a0f66 1803 vcs optional fossil_2.4-1.dsc
 9131005aa858e9ea6c4a4620b2232aa4 4794139 vcs optional fossil_2.4.orig.tar.gz
 61dd1459a40208f7bf4fa02d08c8f722 23832 vcs optional fossil_2.4-1.debian.tar.xz
 1e387fb3cc5f4adc1ce610f59c186c00 3304292 debug optional 
fossil-dbgsym_2.4-1_amd64.deb
 f365c6e1e806959cc9435bee10c964c0 6316 vcs optional fossil_2.4-1_amd64.buildinfo
 66fc8026957ed27e84f1020ef0538a6c 775056 vcs optional fossil_2.4-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZPQp426hHMLZZlRvEltXR14ZDRgFAlopHNIACgkQEltXR14Z
DRgh9Q/9Gw2xWi2PeE3oTB4kMzLBgqfshwLfUjCvYx89o1D3hQs56I+Y3J2

Bug#883764: r-cran-scatterd3: Includes files listed in Files-Excluded header

[Chris Lamb]

Source: r-cran-scatterd3
Version: 0.8.1+dfsg-2
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

r-cran-scatterd3 lists "*/d3*.min.js" in the Files-Excluded field in
debian/copyright but the source tree contains
inst/htmlwidgets/lib/d3-legend.min.js.

This is probably a DFSG violation, or at the upstream tarball was not
repacked as intended. Alternatively, the field is simply out of date.


Regards,

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

Bug#883758: scamp: Includes "doc/scamp.pdf" listed in Files-Excluded header

[Chris Lamb]

Source: scamp
Version: 2.0.4-5
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

scamp lists "doc/scamp.pdf" in the Files-Excluded field in
debian/copyright but the source tree contains doc/scamp.pdf.

This is probably a DFSG violation, or at the upstream tarball was not
repacked as intended. Alternatively, the field is simply out of date.


Regards,

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

Bug#883763: python-social-auth: Includes "site/css/site.css" listed in Files-Excluded header

[Chris Lamb]

Source: python-social-auth
Version: 1:0.2.21+dfsg-1
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

python-social-auth lists "site/*" in the Files-Excluded field in
debian/copyright but the source tree containns site/css/site.css.

This is probably a DFSG violation, or at the upstream tarball was not
repacked as intended. Alternatively, the field is simply out of date.


Regards,

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

Bug#883759: kashmir: Includes "gui/ios/Model/UUIDModel.h" listed in Files-Excluded header

[Chris Lamb]

Source: kashmir
Version: 0.0~git20150805.0.2f3913f+dfsg1-3
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

kashmir lists "gui/*" in the Files-Excluded field in debian/copyright
but the source tree contains gui/ios/Model/UUIDModel.h.

This is probably a DFSG violation, or at the upstream tarball was not
repacked as intended. Alternatively, the field is simply out of date.


Regards,

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

Bug#883760: libgd2: Includes "VMS/CONFIGURE.COM" and "test/gdtest.gd2" listed in Files-Excluded header

[Chris Lamb]

Source: libgd2
Version: 2.2.5-4
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

libgd2 lists "VMS/* and test/*" in the Files-Excluded field in
debian/copyright but the source tree contains VMS/CONFIGURE.COM and
test/gdtest.gd2

This is probably a DFSG violation, or at the upstream tarball was not
repacked as intended. Alternatively, the field is simply out of date.


Regards,

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

Bug#883761: libgdamm5.0: Includes "docs/reference/html/jquery.js" listed in Files-Excluded header

[Chris Lamb]

Source: libgdamm5.0
Version: 4.99.11-1
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

libgdamm5.0 lists "docs/reference/html/jquery.js" in the Files-Excluded field in
debian/copyright but the source tree contain docs/reference/html/jquery.js.

This is probably a DFSG violation, or at the upstream tarball was not
repacked as intended. Alternatively, the field is simply out of date.


Regards,

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

Bug#883757: ignition-transport: Includes "test/gtest/cmake/internal_utils.cmake" listed in Files-Excluded header

[Chris Lamb]

Source: ignition-transport
Version: 1.3.0-5
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

ignition-transport lists "test/gtest" in the Files-Excluded field in
debian/copyright but the source tree contains
test/gtest/cmake/internal_utils.cmake.

This is probably a DFSG violation, or at the upstream tarball was not
repacked as intended. Alternatively, the field is simply out of date.


Regards,

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

Bug#883762: pyscanfcs: Includes "freeze_pyinstaller/PyScanFCS.icns" listed in Files-Excluded header

[Chris Lamb]

Source: pyscanfcs
Version: 0.2.3-5
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

pyscanfcs lists "freeze_pyinstaller/PyScanFCS.icns" in the Files-Excluded
field in debian/copyright but the source tree contains
freeze_pyinstaller/PyScanFCS.icns

This is probably a DFSG violation, or at the upstream tarball was not
repacked as intended. Alternatively, the field is simply out of date.


Regards,

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

Bug#881496: [Pkg-privacy-maintainers] Bug#881496: onioncircuits: python3/testing and apparmor/testing breaks onioncircuits

[intrigeri]

Control: tag -1 + moreinfo

Hi Mykola,

Sascha Steinbiss:
> ah, this sheds some light on the situation. However:

>> audit[3722]: AVC apparmor="DENIED" operation="file_mmap"
>> profile="/usr/bin/onioncircuits"
>> name="/usr/lib/python3.6/lib-dynload/_ctypes.cpython-36m-x86_64-linux-gnu.so"
>> pid=3722 comm="onioncircuits" requested_mask="m" denied_mask="m" fsuid=1000 
>> ouid=0

> This is interesting, since the corresponding line in the python AppArmor
> abstractions [1] (which are imported by the onioncircuits profile [2]) is:

>   /usr/lib{,32,64}/python3.[0-6]/lib-dynload/*.somr,

> which indeed already has the mmap flag set. It's been in testing for
> some while now (since bzr revision #1671, which was the initial update
> to upstream's 2.11.1).
> I also can't see it being overridden anywhere. So I am not sure why this
> permission should be denied...

Can you please share the content of your
/etc/apparmor.d/abstractions/python file?

Cheers,
-- 
intrigeri

Processed: Re: Bug#881496: [Pkg-privacy-maintainers] Bug#881496: onioncircuits: python3/testing and apparmor/testing breaks onioncircuits

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + moreinfo
Bug #881496 [onioncircuits] onioncircuits: current python3/testing breaks 
onioncircuits
Added tag(s) moreinfo.

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

Bug#883755: alt-ergo: Includes "non-free/Non-Commercial-License.pdf" listed in Files-Excluded header

[Chris Lamb]

Source: alt-ergo
Version: 1.30-1
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

alt-ergo lists "non-free" in the Files-Excluded field in
debian/copyright but the source tree contains:

  non-free/Non-Commercial-License.pdf

This is almost certainly a DFSG violation or at the upstream tarball was
not repacked as intended. Alternatively, the field is merely out of date.


Regards,

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

Bug#876870: marked as done (apertium-en-es FTBFS with apertium 3.4.2~r68466-2: test failure)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2017 09:33:51 +
with message-id 
and subject line Bug#876870: fixed in apertium-en-es 0.8.0~r57502-3
has caused the Debian Bug report #876870,
regarding apertium-en-es FTBFS with apertium 3.4.2~r68466-2: test failure
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.)


-- 
876870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apertium-en-es
Version: 0.8.0~r57502-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-en-es.html

...
   dh_auto_test -O--fail-missing
make -j1 test VERBOSE=1
make[1]: Entering directory '/build/1st/apertium-en-es-0.8.0~r57502'
echo  "Fue un malentendido."  | apertium -d . es-en | tee .test-mt
It went a misunderstanding.
1c1
< It was a misunderstanding.
---
> It went a misunderstanding.
Makefile:784: recipe for target 'test' failed
make[1]: *** [test] Error 1
--- End Message ---
--- Begin Message ---
Source: apertium-en-es
Source-Version: 0.8.0~r57502-3

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated apertium-en-es package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 07 Dec 2017 14:07:11 +0530
Source: apertium-en-es
Binary: apertium-en-es
Architecture: source all
Version: 0.8.0~r57502-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Kartik Mistry 
Description:
 apertium-en-es - Apertium translation data for the English-Spanish pair
Closes: 876870
Changes:
 apertium-en-es (0.8.0~r57502-3) unstable; urgency=medium
 .
   * Added patch to fix FTBFS in test suites. Thanks to Andreas Moog.
 (Closes: #876870)
   * debian/control:
 + Updated Standards-Version to 4.1.2
Checksums-Sha1:
 8d52905e3d63e3f09da5f0fedcae911fd5eab066 2174 apertium-en-es_0.8.0~r57502-3.dsc
 98f22a2d1868929ba621fd22927d356e54fc04af 2852 
apertium-en-es_0.8.0~r57502-3.debian.tar.xz
 71a404b458fd5a7a3fd86b402c49995da0a9fd66 2137020 
apertium-en-es_0.8.0~r57502-3_all.deb
 180b570aa40a4838bdc913d0c37cb2e85676e800 6201 
apertium-en-es_0.8.0~r57502-3_amd64.buildinfo
Checksums-Sha256:
 e4535d57fad681cd871fb040c29d35b63f4fcad35bceebd9ff6e19fa6968 2174 
apertium-en-es_0.8.0~r57502-3.dsc
 7393313337b10cc9e26c6a79fbf04954b7a713f71067406845f8967c62755fb3 2852 
apertium-en-es_0.8.0~r57502-3.debian.tar.xz
 0fb97da03f0eeda3cf939071063ba3376f7d6f78ef45c16ae5dd6a89f5d79ca1 2137020 
apertium-en-es_0.8.0~r57502-3_all.deb
 5aeef6e3dee8e9fdfe654b396071fe50f93e308d6387498da6c318eff8e5c5c0 6201 
apertium-en-es_0.8.0~r57502-3_amd64.buildinfo
Files:
 4833e194674f553944fe57102e576a33 2174 science optional 
apertium-en-es_0.8.0~r57502-3.dsc
 1585d8fe8e994f94c421ed6b638ab221 2852 science optional 
apertium-en-es_0.8.0~r57502-3.debian.tar.xz
 9c46142ff6bf45d7e7a3cd8f6085d439 2137020 science optional 
apertium-en-es_0.8.0~r57502-3_all.deb
 3d0a63db32cb001119713e2c6fc7f9e1 6201 science optional 
apertium-en-es_0.8.0~r57502-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEa2MbXvVUr2sRlmKSAsHT8ng6pN4FAlopBG0ACgkQAsHT8ng6
pN7q6xAAqH0bgKdvf5et4QOExT41iWcV9ke81LWyKynuNqpx7f6JnHo+z3bPXA/Y
ixKbCQFwYx+9oan6dzPdBxEiI4wO/AlaiW8Sj5CLermqnaJKLQGf0/426RY79Vw8
217LNMgN9YuCfqdYHjVSDb8k7V96z/Bz8fWrUFplF7bfbFT4DFBPFSecYHq8s9m3
lIP+TqQ3r4ui4tfpYOltGpzE1ruv0h+Ix71WGUNeH+Pw0XdtCIMBILFG+pSraJT2
5+pUOzICLdPQo2O5c7mHvXC/wmHUtv9PKXMjop0SowVV8BX2EAXxDyfpg+tNt03r
pOKirca9kszfmuR3BK1aDg4GhFlyc4eEAZpKY5MkxzIuY0KNquC0aP0BpUS9iqEY
KKm+xWZ3M00Mya1w3vrNH1+pRpLFDYSv66Q6Kj1qcaS5iLpjLhb01X5+ZU2+miLo
rA0G7+URAZ3QvyNTAXIm0yFx3pl9r5M4y4Paw6mQFMKjn0k/3N6NkmkLz7uKgKqU
46vRAYJ2bihi3JrHE8CFpEWrU2IVgqAZ2vOtSfi3pLWmsy5/P4tX6awWGReZr9xL
yI4yB0GPZUlwV02bv0mPqk/AH2aumwIN5KVHDp+iEXIe8F0HQu8BRcZvycgM4lzx
nvCEBoTYptaJIr9lPfF8xKf2qLMBW9LYaOpgmKKOFwo+TcypY38=
=VaOe
-END PGP SIGNATURE End Message ---

Processed: tagging 882808

[Debian Bug Tracking System]

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

> tags 882808 + pending
Bug #882808 [src:construct] construct 2.8 incompatible with 2.5, should add 
versioned Breaks
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#883621: marked as done (nova: CVE-2017-17051: Nova FilterScheduler doubles resource allocations during rebuild with new image)

[Debian Bug Tracking System]

Your message dated Thu, 07 Dec 2017 09:19:22 +
with message-id 
and subject line Bug#883621: fixed in nova 2:16.0.3-6
has caused the Debian Bug report #883621,
regarding nova: CVE-2017-17051: Nova FilterScheduler doubles resource 
allocations during rebuild with new image
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.)


-- 
883621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nova
Version: 2:16.0.3-1
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for nova.

CVE-2017-17051[0]:
| An issue was discovered in the default FilterScheduler in OpenStack
| Nova 16.0.3. By repeatedly rebuilding an instance with new images, an
| authenticated user may consume untracked resources on a hypervisor host
| leading to a denial of service, aka doubled resource allocations. This
| regression was introduced with the fix for OSSA-2017-005
| (CVE-2017-16239); however, only Nova stable/pike or later deployments
| with that fix applied and relying on the default FilterScheduler are
| affected.

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-2017-17051
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17051
[1] http://www.openwall.com/lists/oss-security/2017/12/05/5

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: nova
Source-Version: 2:16.0.3-6

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated nova package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 07 Dec 2017 09:29:15 +0100
Source: nova
Binary: nova-api nova-cells nova-common nova-compute nova-compute-ironic 
nova-compute-kvm nova-compute-lxc nova-compute-qemu nova-conductor nova-console 
nova-consoleauth nova-consoleproxy nova-doc nova-placement-api nova-scheduler 
nova-volume python-nova
Architecture: source all
Version: 2:16.0.3-6
Distribution: unstable
Urgency: high
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 nova-api   - OpenStack Compute - compute API frontend
 nova-cells - Openstack Compute - cells
 nova-common - OpenStack Compute - common files
 nova-compute - OpenStack Compute - compute node
 nova-compute-ironic - OpenStack Compute - compute node (Ironic)
 nova-compute-kvm - OpenStack Compute - compute node (KVM)
 nova-compute-lxc - OpenStack Compute - compute node (LXC)
 nova-compute-qemu - OpenStack Compute - compute node (QEmu)
 nova-conductor - OpenStack Compute - conductor service
 nova-console - OpenStack Compute - console
 nova-consoleauth - OpenStack Compute - Console Authenticator
 nova-consoleproxy - OpenStack Compute - NoVNC proxy
 nova-doc   - OpenStack Compute - documentation
 nova-placement-api - OpenStack compute - placement API
 nova-scheduler - OpenStack Compute - virtual machine scheduler
 nova-volume - OpenStack Compute - storage metapackage
 python-nova - OpenStack Compute - libraries
Closes: 883621
Changes:
 nova (2:16.0.3-6) unstable; urgency=high
 .
   * CVE-2017-17051 / OSSA-2017-006: Nova FilterScheduler doubles resource
 allocations during rebuild with new image. Applied upstream patch: Fix
 doubling allocations on rebuild (Closes: 883621).
 Note: previous upload was in fact only refining the patch for addressing
 CVE-2017-16239, not CVE-2017-17051. This upload really fixes the bug for
 CVE-2017-17051.
Checksums-Sha1:
 948543088b83d44870a7cbe884a8c94e3c187023 5406 nova_16.0.3-6.dsc
 6d8b2dbe01cbc83c57cf7631b1c298d8eac5d267 74168 nova_16.0.3-6.debian.tar.xz
 85b319333ee5082cfa366bed395856a0a99dabb2 38612 nova-api_16.0.3-6_all.deb
 d916034cb3b638eba44a774a27bd9b24b799ab65 21992 nova-cells_16.0.3-6_all.deb
 1f9096b8c4f493d721d6743d42972f824c4045d8 127140 nova-common_16.0.3-6_all.deb
 828662b9e6a375524b1d5168b0bdd6a57

Processed: Re: Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #883615 {Done: Andreas Beckmann } [nvidia-driver] 
[CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org
Bug reopened
Ignoring request to alter fixed versions of bug #883615 to the same values 
previously set
> tag -1 - unreproducible
Bug #883615 [nvidia-driver] [CRITICAL] Stretch p-u 9.3 breaks NVidia driver and 
X.org
Removed tag(s) unreproducible.
> retitle -1 nvidia-driver: crashes with /etc/ld.so.nohwcap
Bug #883615 [nvidia-driver] [CRITICAL] Stretch p-u 9.3 breaks NVidia driver and 
X.org
Changed Bug title to 'nvidia-driver: crashes with /etc/ld.so.nohwcap' from 
'[CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org'.

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

Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

[Aurelien Jarno]

control: reopen -1
control: tag -1 - unreproducible
control: retitle -1 nvidia-driver: crashes with /etc/ld.so.nohwcap

On 2017-12-07 05:43, Julien Aubin wrote:
> 2017-12-06 21:50 GMT+01:00 Aurelien Jarno :
> 
> > On 2017-12-06 19:39, Julien Aubin wrote:
> > > Weird... this time I re-upgraded libc6 and things work fine... looks like
> > > something wrong went during the install. And I cannot reproduce the issue
> > > anymore... :'( WTF ???
> >
> > Hmm, a bug has been introduced in libc6 version 2.24-11+deb9u2, which in
> > some conditions leave the /etc/ld.so.nohwcap file instead of removing it
> > just after the upgrade (see bug#883394). One of the condition is to have
> > libc6-i686 installed (while it can be safely removed), which seems to be
> > your case.
> >
> > I consider this bug harmless as it should not deactivate anything now
> > that the default libc is already i686 optimized. Also I don't see how it
> > could trigger the issue you described. Anyway better be safe than sorry,
> > could you please try to create this file with "touch /etc/ld.so.nohwcap"
> > as root and see if it makes the issue to reappear? Once the test is done
> > you can then remove it.
> >
> > Thanks,
> > Aurelien
> >
> 
> 
> Bingo ! It was exactly this !
> 
> If I re-create the file for example it crashes glxgears. When I remove it
> glxgears works fine.
> 
> With GDB, the stack trace for when I run glxgears :
> 
> 0  0x76b311a4 in pthread_mutex_lock (mutex=0x7604e8c0) at
> forward.c:192
> #1  0x75de1308 in __glDispatchNewVendorID () from
> /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0
> #2  0x760793c2 in ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
> #3  0x7607a1ac in ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
> #4  0x76073170 in glXChooseVisual () from
> /usr/lib/x86_64-linux-gnu/libGLX.so.0
> #5  0x779f in ?? ()
> #6  0x5ae7 in ?? ()
> #7  0x76a5c2e1 in __libc_start_main (main=0x5970, argc=1,
> argv=0x7fffe638, init=,
>fini=, rtld_fini=,
> stack_end=0x7fffe628) at ../csu/libc-start.c:291
> #8  0x646a in ?? ()
> 

The libc6 package version 2.24-11+deb9u2 won't be in the next point
release so this issue won't trigger. That said there is clearly an
issue on the nvidia package, it should behave the same with and
without /etc/ld.so.nohwcap. I am therefore reopening this bug.

One of the first step to debug this issue would be to run ldd
/usr/bin/glxgears with and without /etc/ld.so.nohwcap and compare the
difference.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#883621: [PKG-Openstack-devel] Bug#883621: CVE-2017-17051 not fixed?

[Thomas Goirand]

On 12/06/2017 09:34 PM, Salvatore Bonaccorso wrote:
> Hi Thomas,
> 
> CVE-2017-17051 was not fixed afaics, only the regression which was
> introduced by OSSA-2017-005.
> 
> See http://www.openwall.com/lists/oss-security/2017/12/05/5 for
> CVE-2017-17051.
> 
> Could you relook?
> 
> Regards,
> Salvatore

Hi Salvatore,

Indeed, I misunderstood how upstream fixed the problem, and failed to
see that there was 2 patches, the announces were indeed a bit confusing.
Thanks a lot for finding this out, and ensuring that I did the proper
fix. I'll try to push upstream to make a new release of Nova, so that
we've got better assurance all issues are addressed.

I've already applied upstream patch, the package is building, and I will
upload it shortly to Sid.

Cheers,

Thomas Goirand (zigo)

Processed: Bug#883621 marked as pending

[Debian Bug Tracking System]

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

> tag 883621 pending
Bug #883621 [src:nova] nova: CVE-2017-17051: Nova FilterScheduler doubles 
resource allocations during rebuild with new image
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#883621: marked as pending

[Thomas Goirand]

tag 883621 pending
thanks

Hello,

Bug #883621 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/openstack/services/nova.git/commit/?id=4b5a4fd

---
commit 4b5a4fd9e6bbcd28457ec4154d596a1070a51971
Author: Thomas Goirand 
Date:   Thu Dec 7 09:35:50 2017 +0100

  * CVE-2017-17051 / OSSA-2017-006: Nova FilterScheduler doubles resource
allocations during rebuild with new image. Applied upstream patch: Fix
doubling allocations on rebuild (Closes: 883621).
Note: previous upload was in fact only refining the patch for addressing
CVE-2017-16239, not CVE-2017-17051. This upload really fixes the bug for
CVE-2017-17051.

diff --git a/debian/changelog b/debian/changelog
index 7df7e57..34a4984 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,17 @@
+nova (2:16.0.3-6) unstable; urgency=high
+
+  * CVE-2017-17051 / OSSA-2017-006: Nova FilterScheduler doubles resource
+allocations during rebuild with new image. Applied upstream patch: Fix
+doubling allocations on rebuild (Closes: 883621).
+Note: previous upload was in fact only refining the patch for addressing
+CVE-2017-16239, not CVE-2017-17051. This upload really fixes the bug for
+CVE-2017-17051.
+
+ -- Thomas Goirand   Thu, 07 Dec 2017 09:29:15 +0100
+
 nova (2:16.0.3-5) unstable; urgency=high
 
-  * CVE-2017-17051/OSSA-2017-005.1 (errata for CVE-2017-16239/OSSA-2017-005):
+  * CVE-2017-16239/OSSA-2017-005.1 (errata for CVE-2017-16239/OSSA-2017-005):
 Nova Filter Scheduler bypass through rebuild action. Apply upstream patch:
 Refined fix for validating image on rebuild (Closes: #883621).
 

Processed: tagging 883705

[Debian Bug Tracking System]

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

> tags 883705 - unreproducible
Bug #883705 [libc6] libc6: keep /etc/ld.so.nohwcap after upgrade, breaking 
Nvidia GLX
Bug #883394 [libc6] libc6: keep /etc/ld.so.nohwcap after upgrade, breaking 
Nvidia GLX
Removed tag(s) unreproducible.
Removed tag(s) unreproducible.
> thanks
Stopping processing here.

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

Processed: Re: Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

[Debian Bug Tracking System]

Processing control commands:

> reopen 883705
Bug #883705 {Done: Andreas Beckmann } [libc6] libc6: 
2.24-11+deb9u2 breaks Nvidia's GLX X module on Pascal GPU
Bug reopened
Ignoring request to alter fixed versions of bug #883705 to the same values 
previously set
> forcemerge 883705 883394
Bug #883705 [libc6] libc6: 2.24-11+deb9u2 breaks Nvidia's GLX X module on 
Pascal GPU
Bug #883394 [libc6] libc6: does not remove /etc/ld.so.nohwloc after all libc6-* 
packages are upgraded
Severity set to 'critical' from 'important'
Added tag(s) unreproducible.
Bug #883705 [libc6] libc6: 2.24-11+deb9u2 breaks Nvidia's GLX X module on 
Pascal GPU
Added tag(s) pending.
Merged 883394 883705
> retitle 883705 libc6: keep /etc/ld.so.nohwcap after upgrade, breaking Nvidia 
> GLX
Bug #883705 [libc6] libc6: 2.24-11+deb9u2 breaks Nvidia's GLX X module on 
Pascal GPU
Bug #883394 [libc6] libc6: does not remove /etc/ld.so.nohwloc after all libc6-* 
packages are upgraded
Changed Bug title to 'libc6: keep /etc/ld.so.nohwcap after upgrade, breaking 
Nvidia GLX' from 'libc6: 2.24-11+deb9u2 breaks Nvidia's GLX X module on Pascal 
GPU'.
Changed Bug title to 'libc6: keep /etc/ld.so.nohwcap after upgrade, breaking 
Nvidia GLX' from 'libc6: does not remove /etc/ld.so.nohwloc after all libc6-* 
packages are upgraded'.

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