Processed: tagging 933994, tagging 933993, tagging 933992, tagging 933684, tagging 933592, tagging 933666 ...

[Debian Bug Tracking System]

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

> tags 933994 + sid bullseye
Bug #933994 [src:ocaml-sqlexpr] ocaml-sqlexpr FTBFS because it depends on 
lwt.syntax
Added tag(s) sid and bullseye.
> tags 933993 + sid bullseye
Bug #933993 [src:ocaml-usb] ocaml-usb FTBFS because it depends on lwt.syntax
Added tag(s) sid and bullseye.
> tags 933992 + sid bullseye
Bug #933992 [src:obus] obus FTBFS because it depends on lwt.syntax
Added tag(s) bullseye and sid.
> tags 933684 + sid bullseye
Bug #933684 [src:python-httptools] python-httptools: Please adjust for 
http-parser 2.9
Added tag(s) bullseye and sid.
> tags 933592 + sid bullseye
Bug #933592 [node-node-forge,node-jsonld,node-rdf-canonize] Webpack 4 
transition: node-node-forge fail to build with webpack 4
Added tag(s) bullseye and sid.
> tags 933666 + sid bullseye
Bug #933666 [leaflet-image] leaflet-image: fails to build with webpack 4
Added tag(s) bullseye and sid.
> tags 933662 + sid bullseye
Bug #933662 [node-matrix-js-sdk] node-matrix-js-sdk: build with webpack 4 
failing
Added tag(s) sid and bullseye.
> tags 933932 + sid bullseye
Bug #933932 [src:strongwind] strongwind: State of the package, remove?
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
933592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933592
933662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933662
933666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933666
933684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933684
933932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933932
933992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933992
933993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933993
933994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: unarchiving 929618, unarchiving 929615

[Debian Bug Tracking System]

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

> unarchive 929618
Bug #929618 {Done: tony mancill } [src:t-digest] t-digest: 
latest-debian-changelog-entry-reuses-existing-version
Unarchived Bug 929618
> unarchive 929615
Bug #929615 {Done: gregor herrmann } 
[src:libconvert-units-perl] libconvert-units-perl: 
latest-debian-changelog-entry-reuses-existing-version
Unarchived Bug 929615
> thanks
Stopping processing here.

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

Bug#934108: icinga2-bin fails to install

[Daniel Baumann]

Package: icinga2
Version: 2.11.0~rc1-1~exp1
Severity: serious

Hi,

icinga2 fails to install due to a permission issue
(/etc/icinga2/features-* should be owned by nagios:nagions).

--snip--
Setting up icinga2-bin (2.11.0~rc1-1~exp1) ...
enabling default icinga2 features
Enabling feature checker. Make sure to restart Icinga 2 for these
changes to take effect.
critical/cli: Cannot enable feature 'checker'. Linking source
'../features-available/checker.conf' to target file
'/etc/icinga2/features-enabled/checker.conf' failed with error code 13,
"Permission denied".
Enabling feature notification. Make sure to restart Icinga 2 for these
changes to take effect.
critical/cli: Cannot enable feature 'notification'. Linking source
'../features-available/notification.conf' to target file
'/etc/icinga2/features-enabled/notification.conf' failed with error code
13, "Permission denied".
Enabling feature mainlog. Make sure to restart Icinga 2 for these
changes to take effect.
critical/cli: Cannot enable feature 'mainlog'. Linking source
'../features-available/mainlog.conf' to target file
'/etc/icinga2/features-enabled/mainlog.conf' failed with error code 13,
"Permission denied".
critical/cli: Cannot enable feature(s): checker notification mainlog
dpkg: error processing package icinga2-bin (--configure):
 installed icinga2-bin package post-installation script subprocess
returned error exit status 1
dpkg: dependency problems prevent configuration of icinga2:
 icinga2 depends on icinga2-bin (= 2.11.0~rc1-1~exp1); however:
  Package icinga2-bin is not configured yet.

dpkg: error processing package icinga2 (--configure):
 dependency problems - leaving unconfigured
Processing triggers for systemd (241-7) ...
Processing triggers for man-db (2.8.6-1) ...
Processing triggers for libc-bin (2.28-10) ...
Errors were encountered while processing:
 icinga2-bin
 icinga2
E: Sub-process /usr/bin/dpkg returned an error code (1)
--snap--

Regards,
Daniel

Bug#933914: python3-pytest: pytest v4 breaks existing tests

[Drew Parsons]

On 2019-08-07 03:41, Novy, Ondrej wrote:

Hi,

Drew Parsons píše v Út 06. 08. 2019 v 17:25 +0800:


e.g what to do about

...

"/usr/lib/python3/dist-packages/flaky/flaky_pytest_plugin.py", line
272,

in call_runtest_hook

INTERNALERROR> when=when,

INTERNALERROR> TypeError: __init__() missing 3 required positional

arguments: 'excinfo', 'start', and 'stop'


this fix looks related:
https://github.com/box/flaky/pull/140/commits/9f29ed0350391c821f04118fde3f019d970dc8b2




I see, coming from flaky.  Thanks Ondrej.

Drew

Processed: merge Sage FTBFS and GAP symbol issues

[Debian Bug Tracking System]

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

> severity 932367 serious
Bug #932367 [sagemath] sagemath: Sage does not start because of a missing 
symbol in GAP wrapper
Bug #933099 [sagemath] sagemath: sage command does not work due to it crashed
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> merge 932367 933667
Bug #932367 [sagemath] sagemath: Sage does not start because of a missing 
symbol in GAP wrapper
Bug #933099 [sagemath] sagemath: sage command does not work due to it crashed
Bug #933667 [sagemath] sagemath: FTBFS in sid
Marked as found in versions sagemath/8.6-6.
Marked as found in versions sagemath/8.6-6.
Bug #933099 [sagemath] sagemath: sage command does not work due to it crashed
Added tag(s) ftbfs.
Added tag(s) ftbfs.
Bug #933021 [sagemath] sagemath ftbfs in unstable (too many test failures)
Merged 932367 933021 933099 933667
> thanks
Stopping processing here.

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

Processed (with 2 errors): merge Sage FTBFS and GAP symbol issues

[Debian Bug Tracking System]

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

> # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933667#16
> severity 932367 serious # unusable + FTBFS
Unknown command or malformed arguments to command.
> reassign 933667 sagemath
Bug #933667 [src:sagemath] sagemath: FTBFS in sid
Bug #933021 [src:sagemath] sagemath ftbfs in unstable (too many test failures)
Bug reassigned from package 'src:sagemath' to 'sagemath'.
Bug reassigned from package 'src:sagemath' to 'sagemath'.
No longer marked as found in versions sagemath/8.6-6.
No longer marked as found in versions sagemath/8.6-6.
Ignoring request to alter fixed versions of bug #933667 to the same values 
previously set
Ignoring request to alter fixed versions of bug #933021 to the same values 
previously set
> merge 932367 933667
Bug #932367 [sagemath] sagemath: Sage does not start because of a missing 
symbol in GAP wrapper
Bug #933099 [sagemath] sagemath: sage command does not work due to it crashed
Unable to merge bugs because:
severity of #933667 is 'serious' not 'important'
severity of #933021 is 'serious' not 'important'
Failed to merge 932367: Did not alter merged bugs.

> thank you
Stopping processing here.

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

Bug#930057: marked as done (alot: FTBFS because of expired keys)

[Debian Bug Tracking System]

Your message dated Tue, 06 Aug 2019 23:08:03 +
with message-id 
and subject line Bug#930057: fixed in alot 0.8.1-2
has caused the Debian Bug report #930057,
regarding alot: FTBFS because of expired keys
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.)


-- 
930057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: alot
Version: 0.8.1-1
Severity: important

Hi,

alot will FTBFS in the future. For example, running with a clock in
2020 results in:

Traceback (most recent call last):
  File "/build/alot-0.8.1/2nd/tests/test_crypto.py", line 388, in test_decrypt
encrypted = crypto.encrypt(to_encrypt, keys=[crypto.get_key(FPR)])
  File "/build/alot-0.8.1/2nd/alot/crypto.py", line 170, in encrypt
always_trust=True)[0]
  File "/usr/lib/python3/dist-packages/gpg/core.py", line 315, in encrypt
results=results)
gpg.errors.InvalidRecipients: F74091D4133F87D56B5D343C1974EC55FBC2D660: All 
subkeys are expired or revoked

A full build log is attached.


Regards,

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


alot.txt.xz
Description: application/xz
--- End Message ---
--- Begin Message ---
Source: alot
Source-Version: 0.8.1-2

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

Debian distribution maintenance software
pp.
Jordan Justen  (supplier of updated alot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 06 Aug 2019 15:34:16 -0700
Source: alot
Architecture: source
Version: 0.8.1-2
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Jordan Justen 
Closes: 930057
Changes:
 alot (0.8.1-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat.
   * Bump Standards-Version to 4.4.0.
 .
   [ Jordan Justen ]
   * d/patches: Cherry pick upstream 3446dc44f87d. Closes: #930057
Checksums-Sha1:
 9a972ea639aa258b947712dd2ebc72d50bd62c72 2585 alot_0.8.1-2.dsc
 fb9d4fc136838912ea2e5600c8486ccce4297da1 18232 alot_0.8.1-2.debian.tar.xz
 b0e06ac891376ee20cc5de75a7fc6a29eaca5e4f 11812 alot_0.8.1-2_source.buildinfo
Checksums-Sha256:
 14fa2ea78b788350cf3bdde962b55223e6a35788ea7d95d9c1d1b3d80b1bb04f 2585 
alot_0.8.1-2.dsc
 dcf6f6bae75eb7f8af6e53ef9051eca5de34926d7c51b23ea5e3b70b6779beb4 18232 
alot_0.8.1-2.debian.tar.xz
 63fb5c6e800bceb47feafeba644287f9641c385a39e8e6cbd066cd441e57e5cb 11812 
alot_0.8.1-2_source.buildinfo
Files:
 66df15195efde175b8675a084ee6fa32 2585 mail optional alot_0.8.1-2.dsc
 12bdf175444d7118432b021f2c13fea7 18232 mail optional alot_0.8.1-2.debian.tar.xz
 27950c23efe59041f905043c5e7b208d 11812 mail optional 
alot_0.8.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwnSFIXQUyd8CMWwuN/mfaMr5kusFAl1KATsACgkQN/mfaMr5
kusecRAAiMud/0kNIqbvZlfLrA79mYJgvivyvrgHsyvdQZJJ6ZTaQVyzJB8zZTct
SUsuNu6XhScNHMVR3cfWNlGhGxzOzVP8JLPw5Sm2PTsjtMmv2dJq3X9hn6zkrZWV
j+HW+RHHEJKWxog4Q5tsCib2yQiBzClZh1+AmFbP7ueQbBF1dbpNe8YaAoG2H1/A
09SqQfJA0Q/5rmfTpVfBrlZIXBt2fCOH4laR3lAFaJTNqEigv5jWRMdQ6rjUbXAl
zKql7eglzHNeZwSzDAk810Vfk2i1W9z0wLkwiPB6oE9SgwTSLHEa/zpYG2zgFy8L
XofU8pGvYDruR+JYAnJ72RSvkQG8VMoDnXwZdq2ztG9vzP3SAoCIAw86v6snbD1g
8QI7agqzEqg0hG4kzYZpU72ZLwQP6npYvx8yx7G4M2YCUSXmyOo+LYaatuJ9mZQB
ZCzPhqBohiMOds3MzqNQV9xyK+KLODXUWYxg65tX6WuG5ukvYv4Hs29BmTgc9d0R
hWkTuNMnqiwP/TL4CSNKXnGdsWJgq8gdu2guJfzjXn5xJWuCkQdF/PiMpjK29u8F
cM2paVBY64a2cUVDZfbEuhipuYcRW/+92BV8WFoerWFR3CGnGGqqjTjwDoUNi9N3
f+XU25/aOhEinuWBgzZmntse1wyV4FW1XAIf9vAfDWrwCbsfklw=
=lp1m
-END PGP SIGNATURE End Message ---

Bug#934095: python-os-testr (build-)depends on cruft package.

[peter green]

Package: python-os-testr
Version: 1.0.0-4
Severity: serious
Tags: bullseye, sid

The python-os-testr source package build-depends on the python-stestr binary 
package and the python-os-testdir binary package depends on it. The 
python-stestr binary package is no longer built by the python-stestr source 
package.

It's probably time to drop the python-os-testr binary package.

Processed: Bug#930057 marked as pending in alot

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #930057 [src:alot] alot: FTBFS because of expired keys
Added tag(s) pending.

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

Bug#930057: marked as pending in alot

[Jordan Justen]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/applications/alot/commit/c293c45a316eed20b11cd9bdc4a1b73e143e90f7


d/patches: Cherry pick upstream 3446dc44f87d. Closes: #930057

Signed-off-by: Jordan Justen 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/930057

Bug#828441: marked as done (moonshot-trust-router: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Tue, 06 Aug 2019 21:35:06 +
with message-id 
and subject line Bug#828441: fixed in moonshot-trust-router 3.5.0+1
has caused the Debian Bug report #828441,
regarding moonshot-trust-router: FTBFS with openssl 1.1.0
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.)


-- 
828441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: moonshot-trust-router
Version: 1.4.1-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/moonshot-trust-router_1.4.1-1_amd64-20160529-1451

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: moonshot-trust-router
Source-Version: 3.5.0+1

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

Debian distribution maintenance software
pp.
Sam Hartman  (supplier of updated moonshot-trust-router 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 06 Aug 2019 17:10:11 -0400
Source: moonshot-trust-router
Architecture: source
Version: 3.5.0+1
Distribution: unstable
Urgency: medium
Maintainer: Sam Hartman 
Changed-By: Sam Hartman 
Closes: 766298 770537 828441
Changes:
 moonshot-trust-router (3.5.0+1) unstable; urgency=medium
 .
   [ Jisc ]
   * Add support for IPv6
   * Allow tids to receive a list IP addresses to listen from
   * Allow constriants to contain multiple '*' and '?' wildcards anywhere
 .
   [ Sam Hartman ]
   * Standards version 4.4.0
   * debhelper compat 12
   * For now disable dh_dwz because I'm not sure how to get it to work with
 a dbg-pkg like moonshot-trust-router-dbg.  I don't think I want to get
 rid of moonshot-trust-router-dbg.
   * It's probably safe to allow this into testing, Closes: #766298
   * Uses openssl 1.1, Closes: #828441
   * Clean up /var/lib/trust_router on purge, Closes: #770537
 .
 moonshot-trust-router (3.4.10) unstable; urgency=medium
 .
   * Reorganise some of the "internal" configuration options into groups
   * Fix some issues found by the CLANG static analyser
   * Add a log message indicating that changes to hostname or ports require
 a restart to take effect.
 .
 moonshot-trust-router (3.4.9) unstable; urgency=medium
 .
   * Fix how default values are set for systemd units
 .
 moonshot-trust-router (3.4.8) unstable; urgency=medium
 .
   * Rework of tids command line arguments and init scripts
 .
 moonshot-trust-router (3.4.7) unstable; urgency=medium
 .
   * Update source URL
   * Allow realms to be case insensitive
   * Update "tids" so it accepts optional arguments and has sensible
 default values
 .
 moonshot-trust-router (3.4.6) unstable; urgency=medium
 .
   * Build source package
 .
 moonshot-trust-router (3.4.5-0) unstable; urgency=medium
 .
   * Include Build for Debian Buster
 .
 moonshot-trust-router (3.4.4-0) unstable; urgency=medium
 .
   * Improve tidc/tids/trmon command help
   * Support OpenSSL 1.1
 .
 moonshot-trust-router (3.4.3-0) unstable; urgency=medium
 .
   * Fix bug making trustrouter server not sending error responses.
   * Fix "internal error" caused not finding authorisations.
 .
 moonshot-trust-router (3.4.2-0) unstable; urgency=medium
 .
   * Add trust_router systemd unit
   * Fix tids systemd unit
 .
 moonshot-trust-router (3.4.1-0) unstable; urgency=medium
 .
   * Fix broken libtr_tid shared library
   * Link trust_router, tids, and tidc against 

Bug#766298: marked as done (ROM: Not Suitable for Inclusion in Jessie and Stretch)

[Debian Bug Tracking System]

Your message dated Tue, 06 Aug 2019 21:35:06 +
with message-id 
and subject line Bug#766298: fixed in moonshot-trust-router 3.5.0+1
has caused the Debian Bug report #766298,
regarding ROM: Not Suitable for Inclusion in Jessie and Stretch
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.)


-- 
766298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: moonshot-trust-router
severity: serious
justification: ROM
version: 1.4.1-1

Based on upstream discussion, the trust router without FreeRADIUS
integration does not provide sufficient value to expend the effort for
supporting for the length of the Jessie release.
Since we're not willing to commit resources to supporting
it--compatibility with the protocol, important bug fixes, etc--for that
length of time, trust router is not suitable for inclusion in Jessie.

we're willing to support ongoing evolution of the software; that's sort
of the point.  It's just we don't want to support version 1.4.1 for
three years or so.
so, trust-router will stay in unstable and will be included in Jessie+1.
It's likely I'll backport some then-current version of trust router to
Jessie after Jessie is released.

The Moonshot suite is useful without trust router: you can run clients
and servers without trust router.  Trust router is needed to run IDPs or
RP proxies.
--- End Message ---
--- Begin Message ---
Source: moonshot-trust-router
Source-Version: 3.5.0+1

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

Debian distribution maintenance software
pp.
Sam Hartman  (supplier of updated moonshot-trust-router 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 06 Aug 2019 17:10:11 -0400
Source: moonshot-trust-router
Architecture: source
Version: 3.5.0+1
Distribution: unstable
Urgency: medium
Maintainer: Sam Hartman 
Changed-By: Sam Hartman 
Closes: 766298 770537 828441
Changes:
 moonshot-trust-router (3.5.0+1) unstable; urgency=medium
 .
   [ Jisc ]
   * Add support for IPv6
   * Allow tids to receive a list IP addresses to listen from
   * Allow constriants to contain multiple '*' and '?' wildcards anywhere
 .
   [ Sam Hartman ]
   * Standards version 4.4.0
   * debhelper compat 12
   * For now disable dh_dwz because I'm not sure how to get it to work with
 a dbg-pkg like moonshot-trust-router-dbg.  I don't think I want to get
 rid of moonshot-trust-router-dbg.
   * It's probably safe to allow this into testing, Closes: #766298
   * Uses openssl 1.1, Closes: #828441
   * Clean up /var/lib/trust_router on purge, Closes: #770537
 .
 moonshot-trust-router (3.4.10) unstable; urgency=medium
 .
   * Reorganise some of the "internal" configuration options into groups
   * Fix some issues found by the CLANG static analyser
   * Add a log message indicating that changes to hostname or ports require
 a restart to take effect.
 .
 moonshot-trust-router (3.4.9) unstable; urgency=medium
 .
   * Fix how default values are set for systemd units
 .
 moonshot-trust-router (3.4.8) unstable; urgency=medium
 .
   * Rework of tids command line arguments and init scripts
 .
 moonshot-trust-router (3.4.7) unstable; urgency=medium
 .
   * Update source URL
   * Allow realms to be case insensitive
   * Update "tids" so it accepts optional arguments and has sensible
 default values
 .
 moonshot-trust-router (3.4.6) unstable; urgency=medium
 .
   * Build source package
 .
 moonshot-trust-router (3.4.5-0) unstable; urgency=medium
 .
   * Include Build for Debian Buster
 .
 moonshot-trust-router (3.4.4-0) unstable; urgency=medium
 .
   * Improve tidc/tids/trmon command help
   * Support OpenSSL 1.1
 .
 moonshot-trust-router (3.4.3-0) unstable; urgency=medium
 .
   * Fix bug making trustrouter server not sending error responses.
   * Fix "internal error" caused not finding authorisations.
 .
 moonshot-trust-router (3.4.2-0) unstable; urgency=medium
 .
   * Add trust_router systemd unit
   * Fix tids systemd unit
 .
 

Bug#933743: LibXSLT in Debian stable has three unpatched security vulnerabilities

[Daniel Richard G.]

On Tue, 2019 Aug  6 15:20-04:00, Salvatore Bonaccorso wrote:
> 
> No I was refering to the bugs filled in the BTS, they were #926895,
> #931321 and #931320. We then cross reference those to/from the
> security-tracker as well. I added your bug as well later on.

I think what may have happened was that these bugs were filed against
the source package, but I had (only) checked the bugs for libxslt1.1,
the runtime binary package.

I will make a note to additionally check the source package in this kind
of situation in the future.

> Done and it entered unstable today,
> https://tracker.debian.org/news/1052113/accepted-libxslt-1132-21-source-into-unstable/
> . Will look into prepare based on that as well a buster-pu update and
> possibly time permitting as well one back to stretch.

Greatly appreciate your work here, as will users running those releases.

Bug#934089: firehol fails to use iptables-restore

[Jean Louis]

Package: firehol
Version: 3.1.6+ds-8
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

   Upgrade to Debian 10
   
   * What exactly did you do (or not do) that was effective (or
 ineffective)?

   sudo firehol try
   
   * What was the outcome of this action?

sudo firehol try
FireHOL: Saving active firewall to a temporary file...  OK
FireHOL: Processing file '/etc/firehol/firehol.conf'...  OK  (281 iptables 
rules)

Your firewall is ready to be fast-activated...
If you don't continue, no changes will have been made to your firewall.
Activate the firewall? (just press enter to confirm or Control-C to stop) :

FireHOL: Fast activating new firewall...


ERROR   : # 1.
WHAT: A runtime command failed to execute (returned error CANNOT APPLY IN 
FAST MODE).
SOURCE  : FIN
COMMAND : /usr/sbin/iptables-legacy-restore 
\
ii  firehol-tools  3.1.6+ds-8
pn  ulogd2 

-- Configuration Files:
/etc/default/firehol changed [not included]
/etc/firehol/firehol.conf changed [not included]

-- no debconf information

Bug#933930: [Pkg-utopia-maintainers] Bug#933930: Bug#933930: network-manager: Ethernet connection no longer works

[Michael Biebl]

Am 06.08.19 um 15:49 schrieb Vincent Lefevre:
> On 2019-08-06 15:27:19 +0200, Vincent Lefevre wrote:
>> Now, I'll try to see if I can reproduce the failure with dhcp.conf.
> 
> I tried a dozen of times, but I couldn't.
> 

Ok, so the current state of affairs is:

dhcp=dhclient works always
dhcp=internal (the default) fails (sometimes)

?
-- 
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

Bug#933268: closed by Josue Ortega (Bug#933268: fixed in rpcbind 1.2.5-5)

[Michael Biebl]

Am 06.08.19 um 15:35 schrieb Felipe Sateler:>
>
> On Tue, Aug 6, 2019 at 3:15 AM Michael Biebl  # systemctl restart rpcbind.service rpcbind.socket
>
> Job for rpcbind.socket failed.
> See "systemctl status rpcbind.socket" and "journalctl -xe" for
details.
> A dependency job for rpcbind.service failed. See 'journalctl -xe' for
> details.
>
> This needs further investigation, where the underlying problem is.
> For the time being, I would suggest a different workaround, ie.
> restarting rpcbind.service and rpcbind.socket sequentially (or only
> rpcbind.service, I think that should be sufficient)
>
>
> So somehting like this:
> override_dh_installsystemd:
>    dh_installsystemd rpcbind.socket
> dh_installsystemd rpcbind.service
>
>
> I'm not yet sure if this is a bug in systemd itself, in rpcbind or
> debhelper for generating such a code sequence, so CCing all affected
> parties.
>
>
> The idea was to let systemctl/systemd order the jobs in whatever way it
> saw fit, according to the ordering requirements of the units. If there
> is a bug somewhere, it is either in systemd,  or in rpcbind where an
> ordering requirement is missing.

In other words I guess your point is, that this is a bug in
systemd/systemctl?

> Does the problem persist if you add After=rpcbind.socket to
rpcbind.service?
I think the After= ordering is implied for socket units, see man
systemd.socket

   Implicit Dependencies
   The following dependencies are implicitly added:

   •   Socket units automatically gain a Before= dependency on the
service units they activate.



-- 
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: alot: FTBFS because of expired keys

[Debian Bug Tracking System]

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

> severity 930057 serious
Bug #930057 [src:alot] alot: FTBFS in 2020
Severity set to 'serious' from 'important'
> retitle 930057 alot: FTBFS because of expired keys
Bug #930057 [src:alot] alot: FTBFS in 2020
Changed Bug title to 'alot: FTBFS because of expired keys' from 'alot: FTBFS in 
2020'.
> thanks
Stopping processing here.

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

Bug#933914: python3-pytest: pytest v4 breaks existing tests

[Novy, Ondrej]

Hi,

Drew Parsons píše v Út 06. 08. 2019 v 17:25 +0800:
> e.g what to do about..."/usr/lib/python3/dist-
> packages/flaky/flaky_pytest_plugin.py", line 272, in
> call_runtest_hookINTERNALERROR> when=when,INTERNALERROR>
> TypeError: __init__() missing 3 required positional arguments:
> 'excinfo', 'start', and 'stop'

this fix looks related:
https://github.com/box/flaky/pull/140/commits/9f29ed0350391c821f04118fde3f019d970dc8b2

-- 
Best regards Ondřej Nový



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

Bug#934079: 34079: FTBFS: still depends on node-unicode-11.0.0

[Daniel Baumann]

tag 934079 + patch
thanks

Hi,

jftr: for a local backport, I'm using the make it build
(s/12.0.0/12.1.0/ of course if the target is bullseye):

https://git.progress-linux.org/distributions/engywuck-backports/packages/acorn/commit/?id=2784f88405656a9e8e8c06109b94717f66e43def

Regards,
Daniel

Processed: Re: 34079: FTBFS: still depends on node-unicode-11.0.0

[Debian Bug Tracking System]

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

> tag 934079 + patch
Bug #934079 [acorn] FTBFS: still depends on node-unicode-11.0.0
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#934079: FTBFS: still depends on node-unicode-11.0.0

[Daniel Baumann]

Package: acorn
Version: 6.1.1+ds+~0.3.1+~4.0.0+~1.0.0+~5.0.1+ds+~1.6.2+ds-1
Severity: serious

Hi,

acorn build-depends on node-unicode-11.0.0 which is not available
anymore in the archive, as of buster it's node-unicode-12.0.0 (and
node-unicode-12.1.0 in current bullseye).

Regards,
Daniel

Processed: severity of 927418 is serious, retitle 927418 to sysdig-dkms: module does not compile with Kernel 5.x

[Debian Bug Tracking System]

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

> # Linux 5.2.6 now in unstable
> severity 927418 serious
Bug #927418 [sysdig-dkms] sysdig-dkms: Does not compile with Kernel 5.0 from 
Debian Experimental
Severity set to 'serious' from 'normal'
> retitle 927418 sysdig-dkms: module does not compile with Kernel 5.x
Bug #927418 [sysdig-dkms] sysdig-dkms: Does not compile with Kernel 5.0 from 
Debian Experimental
Changed Bug title to 'sysdig-dkms: module does not compile with Kernel 5.x' 
from 'sysdig-dkms: Does not compile with Kernel 5.0 from Debian Experimental'.
> thanks
Stopping processing here.

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

Bug#934035: ocrmypdf: FTBFS in stretch (failing tests)

[James R Barlow]

The issue here is that we have an old version of ocrmypdf (4.3.5) with a
backported version of Ghostscript (9.26) and the latter's behavior has
changed in a way that breaks the test.

I recommend disabling the test and documenting a caveat that certain
metadata may not be preserved in output files. This is arguably a fairly
minor loss of functionality.

On Tue, Aug 6, 2019 at 3:48 AM Santiago Vila  wrote:

> Package: src:ocrmypdf
> Version: 4.3.5-3
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> I tried to build this package in stretch but it failed:
>
>
> 
> [...]
>  debian/rules build-indep
> dh build-indep --with python3,sphinxdoc --buildsystem=pybuild
>dh_testdir -i -O--buildsystem=pybuild
>dh_update_autotools_config -i -O--buildsystem=pybuild
>dh_autoreconf -i -O--buildsystem=pybuild
>dh_auto_configure -i -O--buildsystem=pybuild
> I: pybuild base:184: python3.5 setup.py config
> Skipping external program tests because of --force
> running config
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> mkdir -p debian/.debhelper
> cp -R ocrmypdf debian/.debhelper
> sed -i debian/.debhelper/ocrmypdf/__init__.py -e \
> "s|^VERSION =.*|VERSION = \"4.3.5\"|"
> PYTHONPATH=debian/.debhelper sphinx-build docs html
> Running Sphinx v1.4.9
> making output directory...
> loading pickled environment... not yet created
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 7 source files that are out of date
> updating environment: 7 added, 0 changed, 0 removed
> reading sources... [ 14%] cookbook
> reading sources... [ 28%] errors
> reading sources... [ 42%] index
> reading sources... [ 57%] installation
> reading sources... [ 71%] introduction
> reading sources... [ 85%] languages
> reading sources... [100%] security
>
> /<>/docs/installation.rst:2: WARNING: Duplicate explicit
> target name: "docker".
> /<>/docs/installation.rst:2: WARNING: Duplicate explicit
> target name: "docker".
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... /<>/docs/installation.rst:: WARNING:
> document isn't included in any toctree
> done
> preparing documents... done
> writing output... [ 14%] cookbook
> writing output... [ 28%] errors
> writing output... [ 42%] index
> writing output... [ 57%] installation
> writing output... [ 71%] introduction
> writing output... [ 85%] languages
> writing output... [100%] security
>
> generating indices... genindex
> writing additional pages... search
> copying images... [100%] bitmap_vs_svg.svg
>
> copying static files... WARNING: html_static_path entry
> '/<>/docs/_static' does not exist
> done
> copying extra files... done
> dumping search index in English (code: en) ... done
> dumping object inventory... done
> build succeeded, 4 warnings.
> dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python3 setup.py build
> Skipping external program tests because of --force
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
> copying ocrmypdf/unpaper.py ->
> /<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
> copying ocrmypdf/hocrtransform.py ->
> /<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
> copying ocrmypdf/pdfa.py ->
> /<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
> copying ocrmypdf/ghostscript.py ->
> /<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
> copying ocrmypdf/leptonica.py ->
> /<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
> copying ocrmypdf/tesseract.py ->
> /<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
> copying ocrmypdf/main.py ->
> /<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
> copying ocrmypdf/__init__.py ->
> /<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
> copying ocrmypdf/qpdf.py ->
> /<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
> copying ocrmypdf/__main__.py ->
> /<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
> copying ocrmypdf/pageinfo.py ->
> /<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
> creating /<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf/data
> copying ocrmypdf/data/sRGB.icc ->
> /<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf/data
> generating cffi module
> '/<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf/lib/_leptonica.py'
> creating /<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf/lib
> make[1]: Leaving directory '/<>'
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/<>'
> python3 setup.py test
> Checking for tesseract >= 3.03...
> Found tesseract 3.04.01
> Checking for gs >= 9.15...
> Found gs 9.26
> Checking for unpaper >= 6.1...
> Found unpaper 6.1
> Checking for qpdf >= 5.0.0...
> Found qpdf 6.0.0
> running pytest
> running egg_info
> creating ocrmypdf.egg-info
> writing requirements to ocrmypdf.egg-info/requires.txt
> writing ocrmypdf.egg-info/PKG-INFO
> writing top-level names to ocrmypdf.egg-info/top_level.txt
> writing entry points to ocrmypdf.egg-info/entry_points.txt
> writing dependency_links to 

Bug#933536: marked as done (FTBFS: PYGAC_CONFIG_FILE is not a file or does not exist)

[Debian Bug Tracking System]

Your message dated Tue, 06 Aug 2019 19:24:17 +
with message-id 
and subject line Bug#933536: fixed in satpy 0.16.1-2
has caused the Debian Bug report #933536,
regarding FTBFS: PYGAC_CONFIG_FILE is not a file or does not exist
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.)


-- 
933536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: satpy
Version: 0.16.1-1
Severity: serious
Justification: FTBFS
Control: affects -1 src:python-scipy

satpy now FTBFS (and fails tests) because of the recent upgrade of
python3-pygac to 1.1.0-2.

test_basic_check_satpy (satpy.tests.test_config.TestCheckSatpy)
Test 'check_satpy' basic functionality. ... ERROR:pygac.gac_io:Environment 
variable PYGAC_CONFIG_FILE not set!
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pygac/gac_io.py", line 48, in 
CONFIG_FILE = os.environ['PYGAC_CONFIG_FILE']
  File "/usr/lib/python3.7/os.py", line 678, in __getitem__
raise KeyError(key) from None
KeyError: 'PYGAC_CONFIG_FILE'
ERROR
test_specific_check_satpy (satpy.tests.test_config.TestCheckSatpy)
Test 'check_satpy' with specific features provided. ... ok
test_areas_pyproj (satpy.tests.test_config.TestBuiltinAreas)
Test all areas have valid projections with pyproj. ... ok
test_areas_rasterio (satpy.tests.test_config.TestBuiltinAreas)
Test all areas have valid projections with rasterio. ... ok

==
ERROR: test_basic_check_satpy (satpy.tests.test_config.TestCheckSatpy)
Test 'check_satpy' basic functionality.
--


The failed tests prevent scipy from migrating to testing.

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: satpy
Source-Version: 0.16.1-2

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

Debian distribution maintenance software
pp.
Antonio Valentino  (supplier of updated satpy 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 06 Aug 2019 17:30:35 +
Source: satpy
Architecture: source
Version: 0.16.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Antonio Valentino 
Closes: 933536
Changes:
 satpy (0.16.1-2) unstable; urgency=medium
 .
   * Use debhelper-compat instead of debian/compat.
   * Set upstream metadata fields: Contact.
   * debian/patches:
 - new 0005-Fix-test_gaclacfile.patch (Closes: #933536)
Checksums-Sha1:
 fee73f27aa6b7bdfd910d0cca5e1c34c6ec82659 2705 satpy_0.16.1-2.dsc
 c3e4e754f9a724779137a2c1d9a93b677b9bd88d 7360 satpy_0.16.1-2.debian.tar.xz
 261c6aec309bd1ec23b9cd42867fd2935e8ce5f9 13033 satpy_0.16.1-2_amd64.buildinfo
Checksums-Sha256:
 db36181bc0cc7c964ec364ae017255237581108c6dc4b9984cc72fb80aff86b0 2705 
satpy_0.16.1-2.dsc
 95ef7a59fcfb8a476b31567ec2d82f988762df484fb5077d7287d8c42c50f424 7360 
satpy_0.16.1-2.debian.tar.xz
 e9418f6ca86e0e9a64d3c88c290fc16358f9464321026e3f668f3397043bce9e 13033 
satpy_0.16.1-2_amd64.buildinfo
Files:
 f8268a249b33024c4d19d022a303728d 2705 python optional satpy_0.16.1-2.dsc
 176539a4d072f26c91f3a5e95f138e1e 7360 python optional 
satpy_0.16.1-2.debian.tar.xz
 d7a786c5343f13f653330a9ac3b168b1 13033 python optional 
satpy_0.16.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAl1J0AUACgkQZ1DxCuiN
SvExuhAAroc3YvuRYkFZwn/buubtxj53Dy/n6zN3nR4OS1d7HBQi4156z4BORMrC
gm7Ln5eJY11oZ+2korOgzrGpukiU1drBXBwxYLbhAuva+D/o3519+4VG+8l4XkvQ

Bug#933743: LibXSLT in Debian stable has three unpatched security vulnerabilities

[Salvatore Bonaccorso]

Hi!

On Sun, Aug 04, 2019 at 08:26:04PM -0400, Daniel Richard G. wrote:
> On Sun, 2019 Aug  4 03:20-04:00, Salvatore Bonaccorso wrote:
> >
> > Sure it might have been overlooked, but pinging the existing bug would
> > have been less overhead to now as well start tracking this one as well
> > adjusting metadata etc. But no worries.
> 
> Just so that I understand, there was an existing bug? I checked the open
> bugs before filing this one, but didn't see anything relating to those
> CVEs. Do you mean something with the security tracker?

No I was refering to the bugs filled in the BTS, they were #926895,
#931321 and #931320. We then cross reference those to/from the
security-tracker as well. I added your bug as well later on.
> 
> > CVSS severity scores are really very dependent and who assess it. I
> > guess you are refering to the ones as assessed by NVD. Agreed though
> > that Felix Wilhelm has provided a nice exploiting vector example in
> > the upstream issue for local file access depending on context of how
> > libxslt would be used.
> 
> And I figure LibXSLT is used in a number of ways that may result in
> security exposure, not just within Debian itself, but also user
> applications built on top of it.
> 
> > Anyway I prepared a non-maintainer upload for libxslt adressing all
> > three CVEs in unstable and uploaded it to DELAYED/2 and create a merge
> > request on salsa.
> 
> Thank you, I will watch for it in sid :)

Done and it entered unstable today,
https://tracker.debian.org/news/1052113/accepted-libxslt-1132-21-source-into-unstable/
. Will look into prepare based on that as well a buster-pu update and
possibly time permitting as well one back to stretch.

Regards,
Salvatore

Bug#933784: Patch rev 2

[Stewart Ferguson]

I realized that d/patches/* wasn't enough.  I also had to update d/control. 
Please see corrected patch attached.
From dc7147723a6297410cf56a451ba8a20b177e396b Mon Sep 17 00:00:00 2001
From: Stewart Ferguson 
Date: Tue, 6 Aug 2019 19:01:57 +0200
Subject: [PATCH] Updating rouge dependency to 3.7.0 (Closes: #933784)

---
 debian/control |  4 ++--
 debian/patches/rouge_3_7.patch | 26 ++
 debian/patches/series  |  1 +
 3 files changed, 29 insertions(+), 2 deletions(-)
 create mode 100644 debian/patches/rouge_3_7.patch

diff --git a/debian/control b/debian/control
index 6174cf5..2ade209 100644
--- a/debian/control
+++ b/debian/control
@@ -32,7 +32,7 @@ Build-Depends: dbconfig-common,
ruby-rmagick (>= 2.14.0~),
ruby-roadie (>= 3.2.2~),
ruby-roadie-rails (>= 1.3.0~),
-   ruby-rouge (>= 3.3.0~)
+   ruby-rouge (>= 3.7.0~)
 Build-Depends-Indep: po-debconf
 Standards-Version: 4.3.0
 Vcs-Browser: https://salsa.debian.org/ruby-team/redmine
@@ -71,7 +71,7 @@ Depends: dbconfig-common,
  ruby-rmagick (>= 2.14.0~),
  ruby-roadie (>= 3.2.2~),
  ruby-roadie-rails (>= 1.3.0~),
- ruby-rouge (>= 3.3.0~),
+ ruby-rouge (>= 3.7.0~),
  libjs-jquery,
  libjs-jquery-ui,
  libjs-raphael,
diff --git a/debian/patches/rouge_3_7.patch b/debian/patches/rouge_3_7.patch
new file mode 100644
index 000..a6a6a5a
--- /dev/null
+++ b/debian/patches/rouge_3_7.patch
@@ -0,0 +1,26 @@
+Description: Updating rouge dependency to 3.7.0
+ Debian provides ruby-rouge 3.7.0 while redmine 4.0.4 requires ~>3.3.0.
+ Shortly after releasing 4.0.4 upstream updated rouge dependency to 3.7.0
+ with no further changes to the sources. Therefore it is safe to do the same
+ in Debian's release of 4.0.4.
+ .
+ This change is already applied in redmine release 4.1.0. This patch should be
+ removed when importing that version or higher.
+Author: Stewart Ferguson 
+Bug: http://www.redmine.org/issues/31556
+Forwarded: not-needed
+Applied-Upstream: 4.1.0
+Last-Update: 2019-08-06
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/Gemfile
 b/Gemfile
+@@ -3,7 +3,7 @@ source 'https://rubygems.org'
+ gem "bundler", ">= 1.5.0"
+ 
+ gem "rails", "~> 5.2.2"
+-gem "rouge", "~> 3.3.0"
++gem "rouge", "~> 3.7.0"
+ gem "request_store", "~> 1.1"
+ gem "mini_mime", "~> 1.0.1"
+ gem "actionpack-xml_parser"
diff --git a/debian/patches/series b/debian/patches/series
index 8178d32..a740184 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -4,3 +4,4 @@
 0004-Add-multi-tenancy-support.patch
 0005-Assume-default-instance.patch
 use_system_jquery_libs.patch
+rouge_3_7.patch
-- 
2.23.0.rc1



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

Bug#933784: Patch for bug

[Stewart Ferguson]

tags 933784 + patch
thank you

I've attached a simple patch to address this issue.  Simply bumps the 
ruby-rouge 
revision. The change has already been made upstream[1], requiring only the
dependency version bump and targeting release 4.1.0 (at which time this patch
should be removed).

I was able to install this package properly on my unstable installation after
building with this patch.

[1] http://www.redmine.org/issues/31556

Stewart Ferguson
From 341b1f9b04199c20e64ed5c65fe30bba8af2ffaa Mon Sep 17 00:00:00 2001
From: Stewart Ferguson 
Date: Tue, 6 Aug 2019 19:01:57 +0200
Subject: [PATCH] Updating rouge dependency to 3.7.0 (Closes: #933784)

---
 debian/patches/rouge_3_7.patch | 26 ++
 debian/patches/series  |  1 +
 2 files changed, 27 insertions(+)
 create mode 100644 debian/patches/rouge_3_7.patch

diff --git a/debian/patches/rouge_3_7.patch b/debian/patches/rouge_3_7.patch
new file mode 100644
index 000..a6a6a5a
--- /dev/null
+++ b/debian/patches/rouge_3_7.patch
@@ -0,0 +1,26 @@
+Description: Updating rouge dependency to 3.7.0
+ Debian provides ruby-rouge 3.7.0 while redmine 4.0.4 requires ~>3.3.0.
+ Shortly after releasing 4.0.4 upstream updated rouge dependency to 3.7.0
+ with no further changes to the sources. Therefore it is safe to do the same
+ in Debian's release of 4.0.4.
+ .
+ This change is already applied in redmine release 4.1.0. This patch should be
+ removed when importing that version or higher.
+Author: Stewart Ferguson 
+Bug: http://www.redmine.org/issues/31556
+Forwarded: not-needed
+Applied-Upstream: 4.1.0
+Last-Update: 2019-08-06
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/Gemfile
 b/Gemfile
+@@ -3,7 +3,7 @@ source 'https://rubygems.org'
+ gem "bundler", ">= 1.5.0"
+ 
+ gem "rails", "~> 5.2.2"
+-gem "rouge", "~> 3.3.0"
++gem "rouge", "~> 3.7.0"
+ gem "request_store", "~> 1.1"
+ gem "mini_mime", "~> 1.0.1"
+ gem "actionpack-xml_parser"
diff --git a/debian/patches/series b/debian/patches/series
index 8178d32..a740184 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -4,3 +4,4 @@
 0004-Add-multi-tenancy-support.patch
 0005-Assume-default-instance.patch
 use_system_jquery_libs.patch
+rouge_3_7.patch
-- 
2.23.0.rc1



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

Bug#933536: FTBFS: PYGAC_CONFIG_FILE is not a file or does not exist

[Antonio Valentino]

Hi Graham,

On Tue, 6 Aug 2019 17:02:35 +0200 Graham Inggs  wrote:
> Control: reopen -1
> 
> This does not appear to be fixed, see reproducible builds [1] and 
> autokpkgtest [2] failures.
> 
> 
> [1] https://tests.reproducible-builds.org/debian/history/amd64/satpy.html
> [2] https://ci.debian.net/packages/s/satpy/unstable/amd64/


thanks for reporting.
Despite of the very similar log messages, this seems to me a different
issue.
This one

AssertionError:  is not 

seems to be actually a bug in the satpy test code.
I'm already working on it.

The old one

OSError: /etc/pygac.cfg pointed to by the environment variable
PYGAC_CONFIG_FILE is not a file or does not exist!

affects another package, pygac, and has been already fixed.


regards

-- 
Antonio Valentino

Processed: Patch for bug

[Debian Bug Tracking System]

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

> tags 933784 + patch
Bug #933784 [redmine] redmine: fails to install: Could not find gem 'rouge (~> 
3.3.0)'
Added tag(s) patch.
> thank you
Stopping processing here.

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

Bug#933029: marked as done (argus-clients ftbfs in unstable)

[Debian Bug Tracking System]

Your message dated Tue, 06 Aug 2019 15:49:55 +
with message-id 
and subject line Bug#933029: fixed in argus-clients 1:3.0.8.2-4
has caused the Debian Bug report #933029,
regarding argus-clients ftbfs in unstable
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.)


-- 
933029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:argus-clients
Version: 1:3.0.8.2-3
Severity: serious
Tags: sid bullseye

seen on all architectures.

[...]
   debian/rules override_dh_systemd_enable
make[1]: Entering directory '/<>'
# Do not enable the file by default on purpose.
# The user should enable it only after making sure the configuration is
# appropriate for his/her computer.
make[1]: Leaving directory '/<>'
   debian/rules override_dh_installinit
make[1]: Entering directory '/<>'
dh_installinit --noscripts --name=rasplit
dh_installinit: --name=rasplit option specified, but init script not found
make[1]: *** [debian/rules:19: override_dh_installinit] Error 255
make[1]: Leaving directory '/<>'
make: *** [debian/rules:9: binary-arch] Error 2
--- End Message ---
--- Begin Message ---
Source: argus-clients
Source-Version: 1:3.0.8.2-4

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

Debian distribution maintenance software
pp.
Michael Stone  (supplier of updated argus-clients package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 06 Aug 2019 10:33:16 -0400
Source: argus-clients
Binary: argus-client argus-client-dbgsym
Architecture: source amd64
Version: 1:3.0.8.2-4
Distribution: unstable
Urgency: low
Maintainer: Michael Stone 
Changed-By: Michael Stone 
Description:
 argus-client - IP network transaction auditing tool
Closes: 932984 933029
Changes:
 argus-clients (1:3.0.8.2-4) unstable; urgency=low
 .
   * updated debhelper systemd boilerplate (Closes: #933029)
   * fix hardcoded path to rabins (Closes: #932984)
   * Update standards-version to 4.4.0
Checksums-Sha1:
 6b5ff70290139aafaff0709a3eeb75554748d691 1941 argus-clients_3.0.8.2-4.dsc
 808df65ab7c90ea74a8215fcd77d6b8d46ccb4e2 22956 
argus-clients_3.0.8.2-4.debian.tar.xz
 3d6ebee3414db0e76e07a2f7c1251ce6595ff7c6 26949660 
argus-client-dbgsym_3.0.8.2-4_amd64.deb
 31056cf10770e56ff7d52dcefa9b04235838fb91 3422644 
argus-client_3.0.8.2-4_amd64.deb
 578c381e5e5075313ba594592164f7b9f5108c41 7643 
argus-clients_3.0.8.2-4_amd64.buildinfo
Checksums-Sha256:
 6dbb65d21fd00d9fc2dc091f818c19af70eb9e53593088fbad1c8b1eac6f2032 1941 
argus-clients_3.0.8.2-4.dsc
 9dc07a78ec46078702f8dcd7a65edff4731fec54bb64e61dd6c4473f6f47105f 22956 
argus-clients_3.0.8.2-4.debian.tar.xz
 0c8060f54c5cf20646595f5444e9e2b618f4417e2100576d4d21caead1655e8c 26949660 
argus-client-dbgsym_3.0.8.2-4_amd64.deb
 967cce3870ea4380de0e2cba67e212d2d5cbafc46c8bd9c976474f65112d511b 3422644 
argus-client_3.0.8.2-4_amd64.deb
 c25c5296dc006855ffd64e4b1f5c272c007830a035256fc1bf41278f15da7502 7643 
argus-clients_3.0.8.2-4_amd64.buildinfo
Files:
 8d1253ce8a2dc23971d5789426699c4f 1941 utils optional 
argus-clients_3.0.8.2-4.dsc
 9ba07da9b6a4bee3618b2847258b2449 22956 utils optional 
argus-clients_3.0.8.2-4.debian.tar.xz
 6d4a9b6ffc9310856c74ed4b27abaa93 26949660 debug optional 
argus-client-dbgsym_3.0.8.2-4_amd64.deb
 62c1b12f11734679d9b669d70313c7e4 3422644 utils optional 
argus-client_3.0.8.2-4_amd64.deb
 fafd048d3c4622093acc66f6715a3b28 7643 utils optional 
argus-clients_3.0.8.2-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAtUxX/EfDh4C9hqs3PoR/94FAl1JlsAACgkQ9hqs3PoR
/97IRQ//cn0kRKq67Pof9SIWQut95nhWB1XrCwzQcPQ16x3ds2c27QqtcSZNTghI
DHfS2SJY+l+KIlZrYxPicOP9f7SyG5i3UKZ1if0+ffTZAshbLkXNvDp8fEmEqlis
q2+od4apFpWu2flfyjO1W486cgtD9YEgm5IOGHYJqXrAlJk/PslejQIgmmFz5Kj0
/ViuL+a2o+dSCPK74An+zV8NTfbJl8S+GyUbLBuk59dd6Qev22NIkIKVnsnLxSkE
hh+AeuiBuv98k2/RqEe34CqJ7mKTqI5y+fZySbmeHjOE9SZ4Or+E6OyqNFxPK+cD
Gv0vzc9TAmbT/He2oYJA5HC5ITwEAt+Zbc27PQLPHjznyFQiY0LucYF9QVI9Rb4A
5JOCxLzGeZb6etpZBvavuPBUWtr4NPrgY/L1sA63lhs/hddGoizhCxFETJlftt5P

Bug#933865: adb crashes on startup with SIGBUS

[Bernhard Übelacker]

Dear Maintainer,
I tried to get some more information to this crash and
could reproduce it on a Raspberry 3 running a Debian Buster armhf
image created by following script (with "arch: armhf" and linux-image-armmp):

https://salsa.debian.org/raspi-team/image-specs


The crash seems to happen at least on the initial key creation,
therefore is maybe just visible with an empty ~/.android.


"dmesg" shows following after the crash has happened:

[  339.344841] Alignment trap: not handling instruction ecd6cb04 at 
[]
[  339.345111] Unhandled fault: alignment exception (0x001) at 0xb6c58ba1
[  339.345328] pgd = 72cfb493
[  339.345426] [b6c58ba1] *pgd=33fe8835


The backtrace from "coredumpctl gdb ..." just shows the last two frames:
(gdb) bt
#0  _bsaes_key_convert () at linux-arm/crypto/fipsmodule/bsaes-armv7.S:1037
#1  0xb6c5960e in bsaes_ctr32_encrypt_blocks () at 
linux-arm/crypto/fipsmodule/bsaes-armv7.S:1371
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

When running in an debugger short before the crash the backtrace shows this:
(gdb) bt
#0  bsaes_ctr32_encrypt_blocks () at 
linux-arm/crypto/fipsmodule/bsaes-armv7.S:1351
#1  0xb6c476ba in CTR_DRBG_generate (drbg=0x436570, out=, 
out_len=, additional_data=0xbeffd67c 
"\321,(L\262[\270\344\242\353Zp<\234\372\266\200U:\354\314\237\220r\033\252\002[P\vUban\216\024.J\020\305#g\r\345w\243q-Z\305\201\b~\245U\324\005^\310j\223\221H\370t\356\301\352\323ze\267\063\211\006\332\004\017\320\217w",
 additional_data_len=32) at src/crypto/fipsmodule/rand/ctrdrbg.c:169
#2  0xb6c47832 in RAND_bytes_with_additional_data (out=0x4364e8 "", 
out_len=out_len@entry=128, 
user_additional_data=user_additional_data@entry=0xb6c80dc8 
 "") at src/crypto/fipsmodule/rand/rand.c:330
#3  0xb6c479f6 in RAND_bytes_with_additional_data 
(user_additional_data=0xb6c80dc8  "", out_len=128, 
out=0x4364e8 "") at src/crypto/fipsmodule/bn/random.c:143
#4  bn_rand_with_additional_data (rnd=0x436460, bits=1024, top=0, bottom=1, 
additional_data=0xb6c80dc8  "") at 
src/crypto/fipsmodule/bn/random.c:162
#5  0xb6c47a8e in BN_rand (rnd=rnd@entry=0x436460, bits=bits@entry=1024, 
top=top@entry=0, bottom=bottom@entry=1) at src/crypto/fipsmodule/bn/random.c:199
#6  0xb6c4be42 in generate_prime (out=0x436460, bits=bits@entry=1024, 
e=0x436448, p=p@entry=0x0, ctx=ctx@entry=0x436a18, cb=cb@entry=0x0) at 
src/crypto/fipsmodule/rsa/rsa_impl.c:837
#7  0xb6c4c132 in RSA_generate_key_ex (rsa=0x4361a8, bits=2048, 
e_value=, cb=0x0) at src/crypto/fipsmodule/rsa/rsa_impl.c:964
#8  0xb6f947ac in ?? () from 
/usr/lib/arm-linux-gnueabihf/android/libadb.so.0
#9  0xb6f95d80 in adb_auth_init() () from 
/usr/lib/arm-linux-gnueabihf/android/libadb.so.0
#10 0x00408608 in adb_server_main (is_daemon=is_daemon@entry=1, 
socket_spec="tcp:5037", ack_reply_fd=ack_reply_fd@entry=4) at 
adb/client/main.cpp:130
#11 0x0040bd10 in adb_commandline (argc=, argv=0xbefffdd0) 
at /usr/include/c++/8/bits/basic_string.h:252
#12 0xb6cc2524 in __libc_start_main (main=0x404e11 , 
argc=7, argv=0xbefffdb4, init=, fini=0x41812d <__libc_csu_fini>, 
rtld_fini=0xb6fe16c5 <_dl_fini>, stack_end=0xbefffdb4) at libc-start.c:308
#13 0x00404e80 in _start () at adb/client/main.cpp:186


The causing instruction seems to be following (complete debug session attached):
(gdb) 
1034vldmia  r6, {q14}   @ .LM0
1: x/i $pc
=> 0xb6c6f278 <_bsaes_key_convert+40>:  vldmia  r6, {d28-d29}
(gdb) info reg
...
r6 0xb6c6eba1  3066489761
...
(gdb) stepi

Thread 1 "adb" received signal SIGBUS, Bus error.
_bsaes_key_convert () at linux-arm/crypto/fipsmodule/bsaes-armv7.S:1037
1037vrev32.8q7,  q7
1: x/i $pc
=> 0xb6c6f27c <_bsaes_key_convert+44>:  vrev32.8q7, q7
(gdb) 


Upstream appears to have an patch integrated that touches _bsaes_key_convert: 
[1] [2]

A package android-libboringssl build with that patch applied could successfuly
create the keys and did no crash on "adb devices" (just tested without a device 
connected).

Kind regards,
Bernhard

[1] 
https://android.googlesource.com/platform/external/boringssl/+/ab8b888152733533e60c1ebbe8438594a3a2e3d7%5E%21/linux-arm/crypto/fipsmodule/bsaes-armv7.S
[2] 
https://boringssl.googlesource.com/boringssl/+/672f6fc2486745d0cabc3aaeb4e0a3cd13b37b12%5E%21/crypto/fipsmodule/aes/asm/bsaes-armv7.pl



# Buster/stable armhf Raspberry Pi 3, 2019-08-06

apt update
apt dist-ugprade




apt install systemd-coredump gdb fakeroot adb adb-dbgsym 
android-libboringssl-dbgsym
apt build-dep android-libboringssl


The following NEW packages will be installed:
adb android-libadb android-libbase android-libboringssl android-libcrypto-utils 
android-libcutils android-liblog android-sdk-platform-tools-common libatomic1 
libusb-1.0-0 gdb libbabeltrace1 libc6-dbg libglib2.0-0 libglib2.0-data libicu63 

Bug#934013: marked as done (boost-defaults: Boost license file is not found)

[Debian Bug Tracking System]

Your message dated Tue, 06 Aug 2019 15:10:48 +
with message-id 
and subject line Bug#934013: fixed in boost-defaults 1.67.0.2
has caused the Debian Bug report #934013,
regarding boost-defaults: Boost license file is not found
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.)


-- 
934013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934013
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: boost-defaults
Version: 1.67.0.1
Severity: serious
Justification: Policy 4.5

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

Every boost packages, libboost*, contains debian/copyright file
which says:

```
copyright & license for Boost-Defaults for Debian.
The license for Boost itself may be found in file
/usr/share/doc/libboost-doc/HTML/LICENSE_1_0.txt
```

However, even if I installed libboost-doc package, the above path does
not exist at all. I cannot find the license for Boost itself.

I believe that the license for Boost itself should
also be available when only one e.g. libboost-test1.67 package is
installed.

P.S. I know that The license for the original Boost is the same as the
license for Boost-Defaults for Debian so that editing the wording might
be enough.

Best regards,
- -- 
Ryo IGARASHI, Ph.D.
rigar...@gmail.com

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

Kernel: Linux 4.4.0-17763-Microsoft
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), 
LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

-BEGIN PGP SIGNATURE-

iIkEARYKADEWIQSQVQWnJ6dEuIxNmESAtgFFC/hXNwUCXUj3WBMccmlnYXJhc2hA
Z21haWwuY29tAAoJEIC2AUUL+Fc35goA/1QXwA5BjOmWINst3Izx7Gv7k4KcTB/6
hR5Kqd3SiIS4AP9UjY3TWHdGVXZmDdk/5ZvD0s/kLMrdLBvvuolyxe44Dg==
=7nMT
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: boost-defaults
Source-Version: 1.67.0.2

We believe that the bug you reported is fixed in the latest version of
boost-defaults, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 934...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Giovanni Mascellani  (supplier of updated boost-defaults 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 06 Aug 2019 16:38:06 +0200
Source: boost-defaults
Architecture: source
Version: 1.67.0.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Boost Team 
Changed-By: Giovanni Mascellani 
Closes: 933276 934013
Changes:
 boost-defaults (1.67.0.2) unstable; urgency=medium
 .
   [ Dimitri John Ledkov ]
   * Remove myself from uploaders.
 .
   [ Giovanni Mascellani ]
   * Convert debian/copyright to the machine-readable format and make it clear
 that it is not about the actual Boost license (closes: #934013).
   * Explicitly list Intel-based architectures in dependencies, in order to
 avoid depending on x32 when it is not supported (closes: #933276).
Checksums-Sha1:
 5e230b1efb7ffec9cdf2d96489c495e39f014d8d 4037 boost-defaults_1.67.0.2.dsc
 632fa264b9305224e6c0490faced9ffbf29abfbf 12767 boost-defaults_1.67.0.2.tar.gz
 d9653ff44094ebb1e4e0e108a69a110f07045fdc 7362 
boost-defaults_1.67.0.2_source.buildinfo
Checksums-Sha256:
 62d1d5a005eab2338efca7d9a796cf91b4f7ea073e52ae169a8f89964d9024ba 4037 
boost-defaults_1.67.0.2.dsc
 da6254edfb1d456a70ebad6744bf655967b1b0b2271c0580e5a6b65d10d85a7e 12767 
boost-defaults_1.67.0.2.tar.gz
 dba00d54f74833d02b4e3a26e35b2ab6d2a8e2c92390a74f2ff007989f755170 7362 
boost-defaults_1.67.0.2_source.buildinfo
Files:
 1f371fe11a74fba96e2225578d6ca15b 4037 libs optional boost-defaults_1.67.0.2.dsc
 23649d4294e469b5bade732d6ad8a10f 12767 libs optional 
boost-defaults_1.67.0.2.tar.gz
 b84460f24fb50156cbe23e46243ca69e 7362 libs optional 
boost-defaults_1.67.0.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQSiBF6hBvCQNcghJEaNr8EMz954SQUCXUmQ6AAKCRCNr8EMz954
ScOnAP0QbXRsS4wICdzTZ5MNq+z16tfnRkBE/zGPraQZxh3FcgD/Z51pMUTM3Vrv
0jijpooMts7Pe8cxyyqDrYCbywrkIAw=
=/vVz
-END PGP SIGNATURE End Message ---

Processed: FTBFS: PYGAC_CONFIG_FILE is not a file or does not exist

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #933536 {Done: Antonio Valentino } 
[src:pygac] FTBFS: PYGAC_CONFIG_FILE is not a file or does not exist
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions pygac/1.1.0-3.

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

Bug#933536: FTBFS: PYGAC_CONFIG_FILE is not a file or does not exist

[Graham Inggs]

Control: reopen -1

This does not appear to be fixed, see reproducible builds [1] and 
autokpkgtest [2] failures.



[1] https://tests.reproducible-builds.org/debian/history/amd64/satpy.html
[2] https://ci.debian.net/packages/s/satpy/unstable/amd64/

Bug#933268: closed by Josue Ortega (Bug#933268: fixed in rpcbind 1.2.5-5)

[Josue Ortega]

On Tue, Aug 06, 2019 at 09:35:28AM -0400, Felipe Sateler wrote:

> The idea was to let systemctl/systemd order the jobs in whatever way it saw
> fit, according to the ordering requirements of the units. If there is a bug
> somewhere, it is either in systemd,  or in rpcbind where an ordering
> requirement is missing.
> 
> Does the problem persist if you add After=rpcbind.socket to rpcbind.service?
>

Yes, the problem persists. This was one of my first aproaches to fix this.

Cheers,

--
Josue

signature.asc
Description: PGP signature

Bug#933268: closed by Josue Ortega

[Josue Ortega]

Hi Michael,

First, thanks for your help and heads up with this issue. 

On Tue, Aug 06, 2019 at 09:15:04AM +0200, Michael Biebl wrote:

> I don't think this is a proper fix. After all, you typically want a
> daemon to be restarted after upgrades so (security) fixes are applied.

I agree with you, actually I'm not very happy with the solution either. From my 
perspective (by now)
I'd rather to keep the service running and then the user could restart it under 
supervision after
the upgrade is done than let it keeping failing under the upgrade where maybe 
the final user
would not notice it after something is on fire.
I'm looking forward to find a better solution for this.
 
 > I also notice, that the above commit contains other (unrelated) changes
> which are not mentioned in the changelog.

 It's not a good idea try several fixes and (ab)use `git commit --amend` I lost 
control of
 some changes (related with the fix). Totally my bad, Sorry about this! I'll 
fix it in the next revision. 

> For the time being, I would suggest a different workaround, ie.
> restarting rpcbind.service and rpcbind.socket sequentially (or only
> rpcbind.service, I think that should be sufficient)

> So somehting like this:
> override_dh_installsystemd:
>  dh_installsystemd rpcbind.socket
>   dh_installsystemd rpcbind.service

I have tried this however rpcbind keeps failing at upgrade after the workaround 

> I'm not yet sure if this is a bug in systemd itself, in rpcbind or
> debhelper for generating such a code sequence, so CCing all affected
> parties.

Similar bug was filed two years ago upgrading to stretch:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865617

--
Josue


signature.asc
Description: PGP signature

Bug#933930: [Pkg-utopia-maintainers] Bug#933930: network-manager: Ethernet connection no longer works

[Vincent Lefevre]

On 2019-08-06 15:27:19 +0200, Vincent Lefevre wrote:
> Now, I'll try to see if I can reproduce the failure with dhcp.conf.

I tried a dozen of times, but I couldn't.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#933268: closed by Josue Ortega (Bug#933268: fixed in rpcbind 1.2.5-5)

[Felipe Sateler]

On Tue, Aug 6, 2019 at 3:15 AM Michael Biebl  wrote:

> Am 06.08.19 um 04:48 schrieb Debian Bug Tracking System:
> >  rpcbind (1.2.5-5) unstable; urgency=medium
> >  .
> >* debian/rules: Add --no-restart-after-upgrade option to
> >  dh_installsystemd to avoid race condition at rpcbind.socket
> >  initialization (Closes: #933268)
>
>
> https://salsa.debian.org/debian/rpcbind/commit/6bdd9256f811ed312173eeb9e9ca7f600720769b
>
> I don't think this is a proper fix. After all, you typically want a
> daemon to be restarted after upgrades so (security) fixes are applied.
> I also notice, that the above commit contains other (unrelated) changes
> which are not mentioned in the changelog.
>
>
> A quick test shows, that debhelper creates the following code and
> executing that manually triggers the same error:
>
> # systemctl restart rpcbind.service rpcbind.socket
>
> Job for rpcbind.socket failed.
> See "systemctl status rpcbind.socket" and "journalctl -xe" for details.
> A dependency job for rpcbind.service failed. See 'journalctl -xe' for
> details.
>
> This needs further investigation, where the underlying problem is.
> For the time being, I would suggest a different workaround, ie.
> restarting rpcbind.service and rpcbind.socket sequentially (or only
> rpcbind.service, I think that should be sufficient)
>
>
> So somehting like this:
> override_dh_installsystemd:
>    dh_installsystemd rpcbind.socket
> dh_installsystemd rpcbind.service
>
>
> I'm not yet sure if this is a bug in systemd itself, in rpcbind or
> debhelper for generating such a code sequence, so CCing all affected
> parties.
>

The idea was to let systemctl/systemd order the jobs in whatever way it saw
fit, according to the ordering requirements of the units. If there is a bug
somewhere, it is either in systemd,  or in rpcbind where an ordering
requirement is missing.

Does the problem persist if you add After=rpcbind.socket to rpcbind.service?

-- 

Saludos,
Felipe Sateler

Bug#933930: [Pkg-utopia-maintainers] Bug#933930: network-manager: Ethernet connection no longer works

[Vincent Lefevre]

On 2019-08-06 10:38:19 +0200, Michael Biebl wrote:
> Can you try and switch to dhclient instead of the internal one.
> 
> $ cat /etc/NetworkManager/conf.d/dhcp.conf
> [main]
> dhcp=dhclient

I upgraded to 1.19.90-2 again, and I did that, and rebooted,
and it worked.

Then, to be sure, I removed dhcp.conf and rebooted, and...
it worked!

Then I rebooted again, and I got a failure.

So, this is not always reproducible.

FYI, a diff of the logs for 1.19.90-2 (with date-information removed
for the diff) between working connection and failure.

--- Logs begin at Tue 2016-04-19 07:35:01 CEST, end at Tue 2019-08-06 15:01:18 
CEST. --
+-- Logs begin at Tue 2016-04-19 07:35:01 CEST, end at Tue 2019-08-06 15:13:18 
CEST. --
 cventin kernel: e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
 cventin kernel: e1000e :00:19.0 eth0: Intel(R) PRO/1000 Network Connection
 cventin ifup: /bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d
 cventin ifup: run-parts: executing /etc/network/if-pre-up.d/ethtool
 cventin ifup: run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
 cventin ifup: /bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d
 cventin ifup: run-parts: executing /etc/network/if-pre-up.d/ethtool
 cventin ifup: run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
 cventin ifup: /bin/run-parts --exit-on-error --verbose /etc/network/if-up.d
 cventin ifup: run-parts: executing /etc/network/if-up.d/avahi-daemon
 cventin ifup: run-parts: executing /etc/network/if-up.d/ethtool
 cventin ifup: run-parts: executing /etc/network/if-up.d/mountnfs
 cventin ifup: run-parts: executing /etc/network/if-up.d/wpasupplicant
 cventin ifup: /bin/run-parts --exit-on-error --verbose /etc/network/if-up.d
 cventin ifup: run-parts: executing /etc/network/if-up.d/avahi-daemon
 cventin ifup: run-parts: executing /etc/network/if-up.d/ethtool
 cventin ifup: run-parts: executing /etc/network/if-up.d/mountnfs
 cventin ifup: run-parts: executing /etc/network/if-up.d/wpasupplicant
 cventin systemd: Starting Network Time Synchronization...
 cventin systemd: Started Network Time Synchronization.
 cventin systemd: Starting Network Manager...
 cventin NetworkManager:   NetworkManager (version 1.19.90) is 
starting... (for the first time)
 cventin NetworkManager:   Read config: 
/etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)
 cventin NetworkManager:   config: unknown key 'wifi.cloned-mac-address' 
in section [device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
 cventin NetworkManager:   config: unknown key 
'ethernet.cloned-mac-address' in section [device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
 cventin NetworkManager:   bus-manager: acquired D-Bus service 
"org.freedesktop.NetworkManager"
 cventin NetworkManager:   monitoring ifupdown state file 
'/run/network/ifstate'.
-cventin dbus-daemon: Activating systemd to hand-off: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' 
requested by ':1.5' (uid=0 pid=766 comm="/usr/sbin/NetworkManager --no-daemon ")
+cventin dbus-daemon: Activating systemd to hand-off: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' 
requested by ':1.7' (uid=0 pid=807 comm="/usr/sbin/NetworkManager --no-daemon ")
 cventin avahi-daemon: Network interface enumeration completed.
 cventin systemd: Started Network Manager.
 cventin systemd: Starting Network Manager Wait Online...
 cventin systemd: Reached target Network.
 cventin NetworkManager:   Loaded device plugin: NMWifiFactory 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.19.90/libnm-device-plugin-wifi.so)
 cventin NetworkManager:   Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.19.90/libnm-device-plugin-bluetooth.so)
 cventin NetworkManager:   Loaded device plugin: NMWwanFactory 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.19.90/libnm-device-plugin-wwan.so)
 cventin NetworkManager:   Loaded device plugin: NMTeamFactory 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.19.90/libnm-device-plugin-team.so)
 cventin NetworkManager:   Loaded device plugin: NMAtmManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.19.90/libnm-device-plugin-adsl.so)
 cventin NetworkManager:   manager: Networking is enabled by state file
-cventin dbus-daemon: Activating via systemd: service 
name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.5' (uid=0 
pid=766 comm="/usr/sbin/NetworkManager --no-daemon ")
+cventin dbus-daemon: Activating via systemd: service 
name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.7' (uid=0 
pid=807 comm="/usr/sbin/NetworkManager --no-daemon ")
 cventin NetworkManager:   settings: Loaded settings plugin: ifupdown 
("/usr/lib/x86_64-linux-gnu/NetworkManager/1.19.90/libnm-settings-plugin-ifupdown.so")

Bug#934032: libjaxen-java: FTBFS in stretch (failing tests, IllegalArgumentException)

[Santiago Vila]

On Tue, Aug 06, 2019 at 02:01:27PM +0200, Emmanuel Bourg wrote:
> Le 06/08/2019 à 12:45, Santiago Vila a écrit :
> 
> > Dear maintainer:
> > 
> > I tried to build this package in stretch but it failed:
> 
> Hi Santiago,
> 
> I'm not sure to understand why you are reporting a test failure in
> oldstable. This is a duplicate of #909216 which was fixed in buster.
> Personally I don't think it's important enough to fix it in stretch.

In a general sense, the DFSG requires that packages build in the same
distribution as they are present, so we can't fix a FTBFS in stretch
(still a supported distribution) by fixing the bug only in buster.

Release Policy says that packages in stretch must build in stretch and
without failure. Because the tests are part of the build, their failure
counts as a build failure.

Do you think I should ask Release Managers before reporting more bugs
like this one? (I only found a handful of them)

Thanks.

Processed: tagging 934036

[Debian Bug Tracking System]

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

> tags 934036 + confirmed
Bug #934036 [src:sketch] sketch: FTBFS in stretch (LaTeX error)
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Processed: fixed 934036 in 1:0.3.7-10

[Debian Bug Tracking System]

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

> fixed 934036 1:0.3.7-10
Bug #934036 [src:sketch] sketch: FTBFS in stretch (LaTeX error)
Marked as fixed in versions sketch/1:0.3.7-10.
> thanks
Stopping processing here.

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

Processed: fixed 934036 in 1:0.3.7-11

[Debian Bug Tracking System]

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

> fixed 934036 1:0.3.7-11
Bug #934036 [src:sketch] sketch: FTBFS in stretch (LaTeX error)
Marked as fixed in versions sketch/1:0.3.7-11.
> thanks
Stopping processing here.

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

Bug#934032: libjaxen-java: FTBFS in stretch (failing tests, IllegalArgumentException)

[Emmanuel Bourg]

Le 06/08/2019 à 12:45, Santiago Vila a écrit :

> Dear maintainer:
> 
> I tried to build this package in stretch but it failed:

Hi Santiago,

I'm not sure to understand why you are reporting a test failure in
oldstable. This is a duplicate of #909216 which was fixed in buster.
Personally I don't think it's important enough to fix it in stretch.

Emmanuel Bourg

Bug#934036: sketch: FTBFS in stretch (LaTeX error)

[David Bremner]

Santiago Vila  writes:
> ./sketch.texi:257: Emergency stop.
>  @epsfxsize 
>
> @epsfspecial #1->@epsftmp =10@epsfxsize 
> @divide @epsftmp by @pspoints 
> @ifnum...
>
> @epsfsetgraph ... to @epsfxsize {@epsfspecial {#1}
>   @hfil }@else @vfil @hbox 
> t...
>
> @imagexxx ...ysize =#3@relax @fi @epsfbox {#1.eps}
>   @else @doxeteximage 
> {#1}{#...
>
> @image ...true @fi @else @imagexxx #1,@finish 
>   @fi 
>  @hfil @ignorespaces @image {ex000}
>  @unskip @hfil 
> ...
> l.257 @center @image{ex000}

That looks very similar to

 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916150

Although the timing is a bit confusing, since supposedly 916150 was
caused by a change to unstable in December of 2018

If someone wants to test, the fix for the previous incarnation was

iff --git a/Doc/make.pl b/Doc/make.pl
index 2259f74..d1c9868 100644
--- a/Doc/make.pl
+++ b/Doc/make.pl
@@ -32,10 +32,10 @@ sub make_example {
 print STDERR "latex example '$ex-tmp.tex':\n";
 system("sed -e s/TEXFILE/$ex/ makeex-tmp.tex > $ex-tmp.tex") == 0 or die 
"$!";
 system("latex $LATEX_OPTS $ex-tmp.tex") == 0 or die "$!";
-system("dvips -E $ex-tmp -o tmp.eps") == 0 or die "$!";
+system("dvips -E $ex-tmp -o $ex.eps") == 0 or die "$!";^M
 # fix up bounding box (originally this was not necessary; something was 
"improved")
-system("epstool --copy --bbox tmp.eps $ex.eps") == 0 or die "$!";
-unlink "tmp.eps";
+#system("epstool --copy --bbox tmp.eps $ex.eps") == 0 or die "$!";^M
+#unlink "tmp.eps";^M
 local *F;
 open(F, "> $ex.txt") or die "$!";
 print F "Image $ex omitted in text version of this document.";

Bug#934043: segfaults with use-after-free when using KrbServiceName Any

[Steinar H. Gunderson]

Package: libapache2-mod-auth-kerb
Version: 5.4-2.3
Severity: grave
Tags: patch upstream

Hi,

After upgrading to buster, mod_auth_kerb keeps on crashing Apache (thus the
grave severity), after printing

  double free or corruption (out)

This is indeed a use-after-free; verify_krb5_user gets in a keytab as a
parameter, and chooses to deallocate it even though the parent expects to keep
using it. I don't know why this didn't trigger as often in stretch,
although we've certainly seen mod_auth_kerb segfaults there as well
(especially with outdated keytabs).

The patch is trivial and can be found in upstream's bug tracker; just don't
deallocate the keytab in verify_krb5_user():

  https://sourceforge.net/p/modauthkerb/bugs/61/

This is not a leak, since the parent closes it inself, in all paths. I've 
verified
that it applies in Debian (just some changed line numbers) and fixes the issue.

Please consider for a buster point release, in addition to unstable.
It makes mod_auth_kerb borderline unusable.

-- System Information:
Debian Release: 10.0
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'proposed-updates'), (500, 
'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.1.11 (SMP w/40 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NO:en_US:en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libapache2-mod-auth-kerb depends on:
ii  apache2-bin [apache2-api-20120211]  2.4.38-3
ii  krb5-config 2.6
ii  libc6   2.28-10
pn  libcomerr2  
ii  libgssapi-krb5-21.17-3
ii  libk5crypto31.17-3
ii  libkrb5-3   1.17-3

libapache2-mod-auth-kerb recommends no packages.

libapache2-mod-auth-kerb suggests no packages.

Bug#934031: heimdal: FTBFS in stretch (failing tests)

[Santiago Vila]

Package: src:heimdal
Version: 7.1.0+dfsg-13+deb9u2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in stretch but it failed:


[...]
 debian/rules build-indep
dh build-indep --with autoreconf --parallel
   dh_testdir -i -O--parallel
   dh_update_autotools_config -i -O--parallel
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf --as-needed
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:18: installing './compile'
configure.ac:20: installing './missing'
src/Makefile.am: installing './depcomp'
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'cf'.
libtoolize: copying file 'cf/libtool.m4'
libtoolize: copying file 'cf/ltoptions.m4'
libtoolize: copying file 'cf/ltsugar.m4'
libtoolize: copying file 'cf/ltversion.m4'
libtoolize: copying file 'cf/lt~obsolete.m4'
configure.ac:14: installing './compile'
configure.ac:10: installing './missing'
admin/Makefile.am: installing './depcomp'
patching file ./ltmain.sh
patching file ./lib/libedit/ltmain.sh
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
./configure CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" 
CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" CXXFLAGS="-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" FCFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong" FFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong" GCJFLAGS="-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong" 
LDFLAGS="-Wl,-z,relro" OBJCFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" OBJCXXFLAGS="-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security"  \
  --libexecdir="\${prefix}/sbin" \
  --enable-shared \
  --prefix=/usr \
  --includedir="\${prefix}/include" \
  --with-openldap=/usr \
  --with-sqlite3=/usr \
  --with-libedit=/usr \
  --enable-kcm \
  --with-hdbdir=/var/lib/heimdal-kdc \
  --without-openssl \
  --infodir="\${prefix}/share/info" \
  --datarootdir="\${prefix}/share" \
  --libdir="\${prefix}/lib/x86_64-linux-gnu" \
  --without-krb4
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu 
format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... 
func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /bin/dd
checking how to truncate binary pipes... 

Bug#934037: sorl-thumbnail: FTBFS in stretch (RuntimeError: Magick: Unable to deduce image format)

[Santiago Vila]

Package: src:sorl-thumbnail
Version: 12.3+git20160928-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in stretch but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_2.7/build/sorl
copying sorl/__init__.py -> /<>/.pybuild/pythonX.Y_2.7/build/sorl
creating /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
copying sorl/thumbnail/compat.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
copying sorl/thumbnail/models.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
copying sorl/thumbnail/parsers.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
copying sorl/thumbnail/default.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
copying sorl/thumbnail/log.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
copying sorl/thumbnail/base.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
copying sorl/thumbnail/helpers.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
copying sorl/thumbnail/shortcuts.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
copying sorl/thumbnail/images.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
copying sorl/thumbnail/fields.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
copying sorl/thumbnail/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail
creating 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/templatetags
copying sorl/thumbnail/templatetags/thumbnail.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/templatetags
copying sorl/thumbnail/templatetags/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/templatetags
creating /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/admin
copying sorl/thumbnail/admin/current.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/admin
copying sorl/thumbnail/admin/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/admin
creating /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/kvstores
copying sorl/thumbnail/kvstores/dynamodb_kvstore.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/kvstores
copying sorl/thumbnail/kvstores/redis_kvstore.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/kvstores
copying sorl/thumbnail/kvstores/dbm_kvstore.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/kvstores
copying sorl/thumbnail/kvstores/base.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/kvstores
copying sorl/thumbnail/kvstores/cached_db_kvstore.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/kvstores
copying sorl/thumbnail/kvstores/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/kvstores
creating /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/migrations
copying sorl/thumbnail/migrations/0001_initial.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/migrations
copying sorl/thumbnail/migrations/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/migrations
creating /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/conf
copying sorl/thumbnail/conf/defaults.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/conf
copying sorl/thumbnail/conf/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/conf
creating /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/management
copying sorl/thumbnail/management/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/management
creating /<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/engines
copying sorl/thumbnail/engines/wand_engine.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/engines
copying sorl/thumbnail/engines/convert_engine.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/engines
copying sorl/thumbnail/engines/vipsthumbnail_engine.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/engines
copying sorl/thumbnail/engines/base.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/engines
copying sorl/thumbnail/engines/pil_engine.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/engines
copying sorl/thumbnail/engines/pgmagick_engine.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/engines
copying sorl/thumbnail/engines/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/sorl/thumbnail/engines
creating 

Bug#934032: libjaxen-java: FTBFS in stretch (failing tests, IllegalArgumentException)

[Santiago Vila]

Package: src:libjaxen-java
Version: 1.1.6-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in stretch but it failed:


[...]
 debian/rules build-indep
test -x debian/rules
mkdir -p "."
/usr/share/maven-debian-helper/copy-repo.sh /<>/debian
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibjaxen-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo 
touch debian/stamp-poms-patched
# before-build target may be used to unpatch the pom files, so we need to check 
if
# patching the pom files is needed here, normally not
if [ ! -f pom.xml.save ]; then \
/usr/bin/make -f debian/rules patch-poms; \
fi
cd . && /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
  -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Dmaven.repo.local=/<>/debian/maven-repo  package -DskipTests
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building jaxen 1.1.6
[INFO] 
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ jaxen ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /<>/src/main/resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @ jaxen ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 197 source files to /<>/target/classes
[WARNING] bootstrap class path not set in conjunction with -source 1.3
[WARNING] source value 1.3 is obsolete and will be removed in a future release
[WARNING] target value 1.2 is obsolete and will be removed in a future release
[WARNING] To suppress warnings about obsolete options, use -Xlint:-options.
[WARNING] 
/<>/src/java/main/org/jaxen/pattern/PatternParser.java:[57,22] 
org.jaxen.expr.DefaultAllNodeStep in org.jaxen.expr has been deprecated
[WARNING] 
/<>/src/java/main/org/jaxen/pattern/PatternParser.java:[58,22] 
org.jaxen.expr.DefaultCommentNodeStep in org.jaxen.expr has been deprecated
[WARNING] 
/<>/src/java/main/org/jaxen/pattern/PatternParser.java:[59,22] 
org.jaxen.expr.DefaultFilterExpr in org.jaxen.expr has been deprecated
[WARNING] 
/<>/src/java/main/org/jaxen/pattern/PatternParser.java:[60,22] 
org.jaxen.expr.DefaultNameStep in org.jaxen.expr has been deprecated
[WARNING] 
/<>/src/java/main/org/jaxen/pattern/PatternParser.java:[61,22] 
org.jaxen.expr.DefaultProcessingInstructionNodeStep in org.jaxen.expr has been 
deprecated
[WARNING] 
/<>/src/java/main/org/jaxen/pattern/PatternParser.java:[62,22] 
org.jaxen.expr.DefaultStep in org.jaxen.expr has been deprecated
[WARNING] 
/<>/src/java/main/org/jaxen/pattern/PatternParser.java:[63,22] 
org.jaxen.expr.DefaultTextNodeStep in org.jaxen.expr has been deprecated
[WARNING] 
/<>/src/java/main/org/jaxen/expr/DefaultBinaryExpr.java:[52,42] 
org.jaxen.expr.DefaultExpr in org.jaxen.expr has been deprecated
[WARNING] 
/<>/src/java/main/org/jaxen/expr/DefaultLocationPath.java:[60,44] 
org.jaxen.expr.DefaultExpr in org.jaxen.expr has been deprecated
[WARNING] 
/<>/src/java/main/org/jaxen/expr/DefaultUnaryExpr.java:[56,32] 
org.jaxen.expr.DefaultExpr in org.jaxen.expr has been deprecated
[WARNING] 
/<>/src/java/main/org/jaxen/expr/DefaultVariableReferenceExpr.java:[53,44]
 org.jaxen.expr.DefaultExpr in org.jaxen.expr has been deprecated
[WARNING] 
/<>/src/java/main/org/jaxen/expr/DefaultNumberExpr.java:[55,33] 
org.jaxen.expr.DefaultExpr in org.jaxen.expr has been deprecated
[WARNING] 
/<>/src/java/main/org/jaxen/pattern/PatternParser.java:[140,35] 
org.jaxen.expr.DefaultFilterExpr in org.jaxen.expr has been deprecated
[WARNING] 
/<>/src/java/main/org/jaxen/pattern/PatternParser.java:[192,30] 
org.jaxen.expr.DefaultAllNodeStep in org.jaxen.expr has been deprecated
[WARNING] 
/<>/src/java/main/org/jaxen/pattern/PatternParser.java:[204,35] 
org.jaxen.expr.DefaultCommentNodeStep in org.jaxen.expr has been deprecated
[WARNING] 
/<>/src/java/main/org/jaxen/pattern/PatternParser.java:[208,35] 
org.jaxen.expr.DefaultProcessingInstructionNodeStep in org.jaxen.expr has been 
deprecated
[WARNING] 
/<>/src/java/main/org/jaxen/pattern/PatternParser.java:[212,35] 
org.jaxen.expr.DefaultTextNodeStep in org.jaxen.expr has been deprecated
[WARNING] 

Bug#934033: mitmproxy: FTBFS in stretch (failing tests, expired certificate)

[Santiago Vila]

Package: src:mitmproxy
Version: 0.18.2-6
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in stretch but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2 --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
   dh_auto_build -i -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/netlib
copying netlib/certutils.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib
copying netlib/basetypes.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib
copying netlib/wsgi.py -> /<>/.pybuild/pythonX.Y_2.7/build/netlib
copying netlib/tutils.py -> /<>/.pybuild/pythonX.Y_2.7/build/netlib
copying netlib/version_check.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib
copying netlib/debug.py -> /<>/.pybuild/pythonX.Y_2.7/build/netlib
copying netlib/version.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib
copying netlib/tcp.py -> /<>/.pybuild/pythonX.Y_2.7/build/netlib
copying netlib/human.py -> /<>/.pybuild/pythonX.Y_2.7/build/netlib
copying netlib/strutils.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib
copying netlib/utils.py -> /<>/.pybuild/pythonX.Y_2.7/build/netlib
copying netlib/exceptions.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib
copying netlib/multidict.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib
copying netlib/basethread.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib
copying netlib/socks.py -> /<>/.pybuild/pythonX.Y_2.7/build/netlib
copying netlib/encoding.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib
copying netlib/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib
creating /<>/.pybuild/pythonX.Y_2.7/build/mitmproxy
copying mitmproxy/options.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/mitmproxy
copying mitmproxy/ctx.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/mitmproxy
copying mitmproxy/controller.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/mitmproxy
copying mitmproxy/contentviews.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/mitmproxy
copying mitmproxy/optmanager.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/mitmproxy
copying mitmproxy/addons.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/mitmproxy
copying mitmproxy/main.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/mitmproxy
copying mitmproxy/flowfilter.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/mitmproxy
copying mitmproxy/dump.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/mitmproxy
copying mitmproxy/cmdline.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/mitmproxy
copying mitmproxy/utils.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/mitmproxy
copying mitmproxy/exceptions.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/mitmproxy
copying mitmproxy/stateobject.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/mitmproxy
copying mitmproxy/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/mitmproxy
creating /<>/.pybuild/pythonX.Y_2.7/build/pathod
copying pathod/pathoc_cmdline.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/pathod
copying pathod/test.py -> /<>/.pybuild/pythonX.Y_2.7/build/pathod
copying pathod/pathoc.py -> /<>/.pybuild/pythonX.Y_2.7/build/pathod
copying pathod/log.py -> /<>/.pybuild/pythonX.Y_2.7/build/pathod
copying pathod/utils.py -> /<>/.pybuild/pythonX.Y_2.7/build/pathod
copying pathod/pathod_cmdline.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/pathod
copying pathod/pathod.py -> /<>/.pybuild/pythonX.Y_2.7/build/pathod
copying pathod/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/pathod
creating /<>/.pybuild/pythonX.Y_2.7/build/netlib/websockets
copying netlib/websockets/utils.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib/websockets
copying netlib/websockets/frame.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib/websockets
copying netlib/websockets/masker.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib/websockets
copying netlib/websockets/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib/websockets
creating /<>/.pybuild/pythonX.Y_2.7/build/netlib/http
copying netlib/http/url.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib/http
copying netlib/http/request.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib/http
copying netlib/http/authentication.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib/http
copying netlib/http/message.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib/http
copying netlib/http/cookies.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib/http
copying netlib/http/status_codes.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib/http
copying netlib/http/multipart.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib/http
copying netlib/http/response.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib/http
copying netlib/http/headers.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib/http
copying netlib/http/user_agents.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib/http
copying netlib/http/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/netlib/http

Bug#934035: ocrmypdf: FTBFS in stretch (failing tests)

[Santiago Vila]

Package: src:ocrmypdf
Version: 4.3.5-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in stretch but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python3,sphinxdoc --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python3.5 setup.py config 
Skipping external program tests because of --force
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
mkdir -p debian/.debhelper
cp -R ocrmypdf debian/.debhelper
sed -i debian/.debhelper/ocrmypdf/__init__.py -e \
"s|^VERSION =.*|VERSION = \"4.3.5\"|"
PYTHONPATH=debian/.debhelper sphinx-build docs html
Running Sphinx v1.4.9
making output directory...
loading pickled environment... not yet created
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 7 source files that are out of date
updating environment: 7 added, 0 changed, 0 removed
reading sources... [ 14%] cookbook
reading sources... [ 28%] errors
reading sources... [ 42%] index
reading sources... [ 57%] installation
reading sources... [ 71%] introduction
reading sources... [ 85%] languages
reading sources... [100%] security

/<>/docs/installation.rst:2: WARNING: Duplicate explicit target 
name: "docker".
/<>/docs/installation.rst:2: WARNING: Duplicate explicit target 
name: "docker".
looking for now-outdated files... none found
pickling environment... done
checking consistency... /<>/docs/installation.rst:: WARNING: 
document isn't included in any toctree
done
preparing documents... done
writing output... [ 14%] cookbook
writing output... [ 28%] errors
writing output... [ 42%] index
writing output... [ 57%] installation
writing output... [ 71%] introduction
writing output... [ 85%] languages
writing output... [100%] security

generating indices... genindex
writing additional pages... search
copying images... [100%] bitmap_vs_svg.svg

copying static files... WARNING: html_static_path entry 
'/<>/docs/_static' does not exist
done
copying extra files... done
dumping search index in English (code: en) ... done
dumping object inventory... done
build succeeded, 4 warnings.
dh_auto_build -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python3 setup.py build 
Skipping external program tests because of --force
running build
running build_py
creating /<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
copying ocrmypdf/unpaper.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
copying ocrmypdf/hocrtransform.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
copying ocrmypdf/pdfa.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
copying ocrmypdf/ghostscript.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
copying ocrmypdf/leptonica.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
copying ocrmypdf/tesseract.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
copying ocrmypdf/main.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
copying ocrmypdf/__init__.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
copying ocrmypdf/qpdf.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
copying ocrmypdf/__main__.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
copying ocrmypdf/pageinfo.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf
creating /<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf/data
copying ocrmypdf/data/sRGB.icc -> 
/<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf/data
generating cffi module 
'/<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf/lib/_leptonica.py'
creating /<>/.pybuild/pythonX.Y_3.5/build/ocrmypdf/lib
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
python3 setup.py test
Checking for tesseract >= 3.03...
Found tesseract 3.04.01
Checking for gs >= 9.15...
Found gs 9.26
Checking for unpaper >= 6.1...
Found unpaper 6.1
Checking for qpdf >= 5.0.0...
Found qpdf 6.0.0
running pytest
running egg_info
creating ocrmypdf.egg-info
writing requirements to ocrmypdf.egg-info/requires.txt
writing ocrmypdf.egg-info/PKG-INFO
writing top-level names to ocrmypdf.egg-info/top_level.txt
writing entry points to ocrmypdf.egg-info/entry_points.txt
writing dependency_links to ocrmypdf.egg-info/dependency_links.txt
writing manifest file 'ocrmypdf.egg-info/SOURCES.txt'
reading manifest file 'ocrmypdf.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '*' found under directory 
'tests/output'
warning: no previously-included files matching '*' found under directory 
'tests/output_pageinfo'
warning: no previously-included files matching '*' found under directory 
'tests/resources/private'
warning: no previously-included files matching '*' found under directory 
'tests/cache'
warning: no previously-included files matching '*' found under directory 
'.github'
warning: no 

Bug#934034: monkeysphere: FTBFS in stretch (failing tests)

[Santiago Vila]

Package: src:monkeysphere
Version: 0.41-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in stretch but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   dh_auto_build -i
make -j1
make[1]: Entering directory '/<>'
gcc -o src/agent-transfer/agent-transfer -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security   --pedantic -Wall -Werror -std=c99 -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now src/agent-transfer/main.c -lassuan 
-L/usr/lib/x86_64-linux-gnu -lgpg-error -lgcrypt
mkdir -p replaced/src/
sed < src/monkeysphere > replaced/src/monkeysphere \
-e 's:__SYSSHAREDIR_PREFIX__:/usr:' \
-e 's:__SYSCONFDIR_PREFIX__::' \
-e 's:__SYSDATADIR_PREFIX__:/var/lib:'
mkdir -p replaced/src/
sed < src/monkeysphere-host > replaced/src/monkeysphere-host \
-e 's:__SYSSHAREDIR_PREFIX__:/usr:' \
-e 's:__SYSCONFDIR_PREFIX__::' \
-e 's:__SYSDATADIR_PREFIX__:/var/lib:'
mkdir -p replaced/src/
sed < src/monkeysphere-authentication > 
replaced/src/monkeysphere-authentication \
-e 's:__SYSSHAREDIR_PREFIX__:/usr:' \
-e 's:__SYSCONFDIR_PREFIX__::' \
-e 's:__SYSDATADIR_PREFIX__:/var/lib:'
mkdir -p replaced/src/share/
sed < src/share/defaultenv > replaced/src/share/defaultenv \
-e 's:__SYSSHAREDIR_PREFIX__:/usr:' \
-e 's:__SYSCONFDIR_PREFIX__::' \
-e 's:__SYSDATADIR_PREFIX__:/var/lib:'
mkdir -p replaced/src/transitions/
sed < src/transitions/0.23 > replaced/src/transitions/0.23 \
-e 's:__SYSSHAREDIR_PREFIX__:/usr:' \
-e 's:__SYSCONFDIR_PREFIX__::' \
-e 's:__SYSDATADIR_PREFIX__:/var/lib:'
mkdir -p replaced/src/transitions/
sed < src/transitions/0.28 > replaced/src/transitions/0.28 \
-e 's:__SYSSHAREDIR_PREFIX__:/usr:' \
-e 's:__SYSCONFDIR_PREFIX__::' \
-e 's:__SYSDATADIR_PREFIX__:/var/lib:'
mkdir -p replaced/src/transitions/
sed < src/transitions/README.txt > replaced/src/transitions/README.txt \
-e 's:__SYSSHAREDIR_PREFIX__:/usr:' \
-e 's:__SYSCONFDIR_PREFIX__::' \
-e 's:__SYSDATADIR_PREFIX__:/var/lib:'
mkdir -p replaced/man/man1/
sed < man/man1/monkeysphere.1 > replaced/man/man1/monkeysphere.1 \
-e 's:__SYSSHAREDIR_PREFIX__:/usr:' \
-e 's:__SYSCONFDIR_PREFIX__::' \
-e 's:__SYSDATADIR_PREFIX__:/var/lib:'
gzip -n replaced/man/man1/monkeysphere.1
mkdir -p replaced/man/man1/
sed < man/man1/agent-transfer.1 > replaced/man/man1/agent-transfer.1 \
-e 's:__SYSSHAREDIR_PREFIX__:/usr:' \
-e 's:__SYSCONFDIR_PREFIX__::' \
-e 's:__SYSDATADIR_PREFIX__:/var/lib:'
gzip -n replaced/man/man1/agent-transfer.1
mkdir -p replaced/man/man1/
sed < man/man1/openpgp2ssh.1 > replaced/man/man1/openpgp2ssh.1 \
-e 's:__SYSSHAREDIR_PREFIX__:/usr:' \
-e 's:__SYSCONFDIR_PREFIX__::' \
-e 's:__SYSDATADIR_PREFIX__:/var/lib:'
gzip -n replaced/man/man1/openpgp2ssh.1
mkdir -p replaced/man/man1/
sed < man/man1/pem2openpgp.1 > replaced/man/man1/pem2openpgp.1 \
-e 's:__SYSSHAREDIR_PREFIX__:/usr:' \
-e 's:__SYSCONFDIR_PREFIX__::' \
-e 's:__SYSDATADIR_PREFIX__:/var/lib:'
gzip -n replaced/man/man1/pem2openpgp.1
mkdir -p replaced/man/man8/
sed < man/man8/monkeysphere-authentication.8 > 
replaced/man/man8/monkeysphere-authentication.8 \
-e 's:__SYSSHAREDIR_PREFIX__:/usr:' \
-e 's:__SYSCONFDIR_PREFIX__::' \
-e 's:__SYSDATADIR_PREFIX__:/var/lib:'
gzip -n replaced/man/man8/monkeysphere-authentication.8
mkdir -p replaced/man/man8/
sed < man/man8/monkeysphere-host.8 > replaced/man/man8/monkeysphere-host.8 \
-e 's:__SYSSHAREDIR_PREFIX__:/usr:' \
-e 's:__SYSCONFDIR_PREFIX__::' \
-e 's:__SYSDATADIR_PREFIX__:/var/lib:'
gzip -n replaced/man/man8/monkeysphere-host.8
mkdir -p replaced/man/man7/
sed < man/man7/monkeysphere.7 > replaced/man/man7/monkeysphere.7 \
-e 's:__SYSSHAREDIR_PREFIX__:/usr:' \
-e 's:__SYSCONFDIR_PREFIX__::' \
-e 's:__SYSDATADIR_PREFIX__:/var/lib:'
gzip -n replaced/man/man7/monkeysphere.7
make[1]: Leaving directory '/<>'
   dh_auto_test -i
make -j1 test
make[1]: Entering directory '/<>'
MONKEYSPHERE_TEST_NO_EXAMINE=true ./tests/keytrans
##
### generating openpgp key...
gpg: keybox '/<>/tests/tmp/ms.5MW/pubring.kbx' created
gpg: /<>/tests/tmp/ms.5MW/trustdb.gpg: trustdb created
gpg: key A28F4C7A72BA3ACE marked as ultimately trusted
gpg: directory '/<>/tests/tmp/ms.5MW/openpgp-revocs.d' created
gpg: revocation certificate stored as 
'/<>/tests/tmp/ms.5MW/openpgp-revocs.d/110B0A0392E152A667CDA1E5A28F4C7A72BA3ACE.rev'
gpg: done
##
### retrieving key timestamp...
gpg: checking the trustdb
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
##
### exporting key to ssh file...
##
### reconvert key, and compare to key in gpg 

Processed: found 934026 in 2:2.2.3-5

[Debian Bug Tracking System]

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

> found 934026 2:2.2.3-5
Bug #934026 {Done: Chris Lamb } [python-django] 
python-django: CVE-2019-14232 CVE-2019-14233 CVE-2019-14234 CVE-2019-14235
There is no source info for the package 'python-django' at version '2:2.2.3-5' 
with architecture ''
Unable to make a source version for version '2:2.2.3-5'
Marked as found in versions 2:2.2.3-5.
> thanks
Stopping processing here.

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

Bug#903213: fixed in datalad 0.10.2-1

[Santiago Vila]

reopen 903213
found 903213 0.4.1-1
fixed 903213 0.10.2-1
thanks

Hi. Could we please fix this in stretch?
(Packages in stretch must be buildable in stretch).

Thanks.

Processed: Re: Bug#903213: fixed in datalad 0.10.2-1

[Debian Bug Tracking System]

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

> reopen 903213
Bug #903213 {Done: Yaroslav Halchenko } [src:datalad] 
datalad: FTBFS in stretch/buster/sid
Bug #903233 {Done: Yaroslav Halchenko } [src:datalad] 
datalad: FTBFS in stretch/buster/sid
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions datalad/0.10.2-1.
No longer marked as fixed in versions datalad/0.10.2-1.
> found 903213 0.4.1-1
Bug #903213 [src:datalad] datalad: FTBFS in stretch/buster/sid
Bug #903233 [src:datalad] datalad: FTBFS in stretch/buster/sid
Ignoring request to alter found versions of bug #903213 to the same values 
previously set
Ignoring request to alter found versions of bug #903233 to the same values 
previously set
> fixed 903213 0.10.2-1
Bug #903213 [src:datalad] datalad: FTBFS in stretch/buster/sid
Bug #903233 [src:datalad] datalad: FTBFS in stretch/buster/sid
Marked as fixed in versions datalad/0.10.2-1.
Marked as fixed in versions datalad/0.10.2-1.
> thanks
Stopping processing here.

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

Processed: unarchive

[Debian Bug Tracking System]

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

> unarchive 903213
Bug #903213 {Done: Yaroslav Halchenko } [src:datalad] 
datalad: FTBFS in stretch/buster/sid
Bug #903233 {Done: Yaroslav Halchenko } [src:datalad] 
datalad: FTBFS in stretch/buster/sid
Unarchived Bug 903213
Unarchived Bug 903233
>
End of message, stopping processing here.

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

Bug#933848: marked as done (FTBFS if cmake is installed or if built twice in a row)

[Debian Bug Tracking System]

Your message dated Tue, 06 Aug 2019 09:37:14 +
with message-id 
and subject line Bug#933848: fixed in pygalmesh 0.3.6-2
has caused the Debian Bug report #933848,
regarding FTBFS if cmake is installed or if built twice in a row
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.)


-- 
933848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygalmesh
Version: 0.3.6-1
Severity: serious

1) pygalmesh FTBFS if cmake is installed. Actually the build succeeds, but the
resulting binary package is almost empty.

With cmake installed:

 fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: dh_auto_clean --buildsystem=cmake
   dh_autoreconf_clean -O--buildsystem=pybuild
   dh_clean -O--buildsystem=pybuild
[...]
 fakeroot debian/rules binary
dh binary --with python3 --buildsystem=pybuild
   dh_testroot -O--buildsystem=pybuild
   dh_prep -O--buildsystem=pybuild
   dh_auto_install -O--buildsystem=pybuild
I: pybuild base:217: dh_auto_install --buildsystem=cmake 
--builddirectory="/mnt/debian/packages/pygalmesh/pygalmesh-0.3.6/.pybuild/cpython3_3.7_pygalmesh/build"
 
--destdir="/mnt/debian/packages/pygalmesh/pygalmesh-0.3.6/debian/python3-pygalmesh"
 -- 
   dh_installdocs -O--buildsystem=pybuild

Without cmake installed:

 fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py clean 
running clean
removing '/build/pygalmesh-0.3.6/.pybuild/cpython3_3.7_pygalmesh/build' (and 
everything under it)
'build/bdist.linux-amd64' does not exist -- can't clean it
'build/scripts-3.7' does not exist -- can't clean it
[...]
 fakeroot debian/rules binary
dh binary --with python3 --buildsystem=pybuild
   dh_testroot -O--buildsystem=pybuild
   dh_prep -O--buildsystem=pybuild
   dh_auto_install -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3 setup.py install --root 
/build/pygalmesh-0.3.6/debian/python3-pygalmesh 
running install
[... many more lines following ...]
   dh_installdocs -O--buildsystem=pybuild

I don't understand why the bare existence of cmake causes the build process to
behave differently. At least, the package should declare a Build-Conflicts: on
cmake.


2) pygalmesh FTBFS when built twice in a row. This can be fixed by putting

pygalmesh-from-inr.1
pygalmesh-volume-from-surface.1

in debian/clean.


Best regards,
  Joachim


-- System Information:
Debian Release: 10.0
  APT prefers stable-debug
  APT policy: (800, 'stable-debug'), (800, 'stable'), (700, 'testing-debug'), 
(700, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: pygalmesh
Source-Version: 0.3.6-2

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated pygalmesh package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 06 Aug 2019 16:53:03 +0800
Source: pygalmesh
Architecture: source
Version: 0.3.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 933848 933986
Changes:
 pygalmesh (0.3.6-2) unstable; urgency=medium
 .
   * debian/clean: delete pygalmesh-from-inr.1 and
 pygalmesh-volume-from-surface.1, generated in
 override_dh_auto_build. Thanks Joachim Reichel.
 Closes: #933848, #933986.
Checksums-Sha1:
 2fd53bb4702aa1f5a0ca3ac7e38741d401769364 2169 pygalmesh_0.3.6-2.dsc
 a8bec4fa979dc3be9b02851a3c7b66eb7d2d9df1 4168 pygalmesh_0.3.6-2.debian.tar.xz
Checksums-Sha256:
 

Bug#896953: marked as done (python-biom-format: autopkgtest fails with new version while succeeded in the past; autodep8 not ready yet)

[Debian Bug Tracking System]

Your message dated Tue, 06 Aug 2019 09:37:25 +
with message-id 
and subject line Bug#896953: fixed in python-biom-format 2.1.7+dfsg-3
has caused the Debian Bug report #896953,
regarding python-biom-format: autopkgtest fails with new version while 
succeeded in the past; autodep8 not ready yet
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.)


-- 
896953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-biom-format
Version: 2.1.6+dfsg-1
Severity: normal
User: debian...@lists.debian.org
Usertags: regression

With the upload of version 2.1.6+dfsg-1 of python-biom-format, the
autopkgtest¹ started to fail with the error copied below. These test
commands come from autodep8, but autodep8 isn't ready yet for the name
of your module vs the package name. Until autodep8 is ready (patches
welcome), please revert the change to use autodep8 for this package.

Paul

¹ https://ci.debian.net/packages/p/python-biom-format/unstable/amd64/

autopkgtest [20:01:22]: test command1: [---
Testing with python2.7:
Traceback (most recent call last):
  File "", line 1, in 
ImportError: No module named biom_format
autopkgtest [20:01:23]: test command1: ---]


autopkgtest [20:02:01]: test command2: [---
Testing with python3.6:
Traceback (most recent call last):
  File "", line 1, in 
ModuleNotFoundError: No module named 'biom_format'
autopkgtest [20:02:01]: test command2: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-biom-format
Source-Version: 2.1.7+dfsg-3

We believe that the bug you reported is fixed in the latest version of
python-biom-format, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 896...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-biom-format 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 06 Aug 2019 10:11:48 +0200
Source: python-biom-format
Binary: python-biom-format python3-biom-format python-biom-format-doc
Architecture: source
Version: 2.1.7+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 python-biom-format - Biological Observation Matrix (BIOM) format (Python 2)
 python-biom-format-doc - documentation for BIOM format
 python3-biom-format - Biological Observation Matrix (BIOM) format (Python 3)
Closes: 896953 919586
Changes:
 python-biom-format (2.1.7+dfsg-3) unstable; urgency=medium
 .
   * debhelper-compat 12
   * Standards-Version: 4.4.0
   * executable /usr/bin/biom in Python3 package
   * Examples in Python3 package to support testing
   * Do not copy build time tests to doc directory
 Closes: #919586
   * Drop biom-format-tools package - wrapper script is in Python3 package
   * Provide valid autopkgtest for Python3 module based on upstreams CI test
 Closes: #896953
Checksums-Sha1:
 271b2a8b02ec8643a6ecea249acdd9f9cae3b927 2832 
python-biom-format_2.1.7+dfsg-3.dsc
 5ee28e79a08f9ff45c9b0653a4d7e8244eb286ab 9096 
python-biom-format_2.1.7+dfsg-3.debian.tar.xz
Checksums-Sha256:
 fdc8a64ef1e98d4271a868a598b8d0b626c7380e3420fcb037fcd245de5a0f89 2832 
python-biom-format_2.1.7+dfsg-3.dsc
 ab25e2d1fc0e5185f2fa3cb0e49237cbb15b1177da2f513a021471f30f3f4dba 9096 
python-biom-format_2.1.7+dfsg-3.debian.tar.xz
Files:
 19dc036a5c4255942078809c5370dbaa 2832 python optional 
python-biom-format_2.1.7+dfsg-3.dsc
 71225f3bc12264a8117d93648a4ef3fa 9096 python optional 
python-biom-format_2.1.7+dfsg-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl1JPNQRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGXLQ//XDHgvfWnm3izup979/Fv5ZXK+qQUhC/V
KV3xJqcdXfmRglKLj6F2wjr8Cv1SLzgx577aw6ocJ/iv141BJUVnzsRlL76xXIT/
M0jc2QP1L/3AXMISPrsZNR3V5zwkVV7BdXBhuWonjlIiSy6sdOvLbwDp6Cr6eV40
0NEcM6C5lpuandS1TOjv1qOhekVd4WGxOrtzaz7A3qySvsalSJBgk9tWGGJu1r+j
gr0HgkYj5BTl0qBTv8aZMVNiYzuurovCrqRALKtkqzJ3sRIfRDk4Wt8IEBDiTnyv

Bug#934026: marked as done (python-django: CVE-2019-14232 CVE-2019-14233 CVE-2019-14234 CVE-2019-14235)

[Debian Bug Tracking System]

Your message dated Tue, 06 Aug 2019 09:37:44 +
with message-id 
and subject line Bug#934026: fixed in python-django 2:2.2.4-1
has caused the Debian Bug report #934026,
regarding python-django: CVE-2019-14232 CVE-2019-14233 CVE-2019-14234 
CVE-2019-14235
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.)


-- 
934026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-django
Version: 1.7.11-1+deb8u6
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for python-django.

CVE-2019-14232[0]:
| An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before
| 2.1.11, and 2.2.x before 2.2.4. If django.utils.text.Truncator's
| chars() and words() methods were passed the html=True argument, they
| were extremely slow to evaluate certain inputs due to a catastrophic
| backtracking vulnerability in a regular expression. The chars() and
| words() methods are used to implement the truncatechars_html and
| truncatewords_html template filters, which were thus vulnerable.


CVE-2019-14233[1]:
| An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before
| 2.1.11, and 2.2.x before 2.2.4. Due to the behaviour of the underlying
| HTMLParser, django.utils.html.strip_tags would be extremely slow to
| evaluate certain inputs containing large sequences of nested
| incomplete HTML entities.


CVE-2019-14234[2]:
SQL injection possibility in key and index lookups for JSONField/HStoreField

CVE-2019-14235[3]:
| An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before
| 2.1.11, and 2.2.x before 2.2.4. If passed certain inputs,
| django.utils.encoding.uri_to_iri could lead to significant memory
| usage due to a recursion when repercent-encoding invalid UTF-8 octet
| sequences.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-14232
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14232
[1] https://security-tracker.debian.org/tracker/CVE-2019-14233
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14233
[2] https://security-tracker.debian.org/tracker/CVE-2019-14234
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14234
[3] https://security-tracker.debian.org/tracker/CVE-2019-14235
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14235


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: python-django
Source-Version: 2:2.2.4-1

We believe that the bug you reported is fixed in the latest version of
python-django, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 934...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated python-django package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 06 Aug 2019 10:08:25 +0100
Source: python-django
Built-For-Profiles: nocheck
Architecture: source
Version: 2:2.2.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Chris Lamb 
Closes: 934026
Changes:
 python-django (2:2.2.4-1) unstable; urgency=medium
 .
   * New upstream security release. (Closes: #934026)
 
Checksums-Sha1:
 9d6966a16c1c7dfaee35ad53e2c693304a07c65f 2741 python-django_2.2.4-1.dsc
 42640e8381bbf041bb2e09400251cd53694902a8 8856979 
python-django_2.2.4.orig.tar.gz
 8839c49662e6b91d054c73fb4d1e1d5a06946c02 25712 
python-django_2.2.4-1.debian.tar.xz
 f7d7d7e65236881ccefd11b3935b9c48e1d80e5b 7292 
python-django_2.2.4-1_amd64.buildinfo
Checksums-Sha256:
 50b20c5bdf006bfb0b0a9d952b63c7f0db55d0b2c03089d7a75dadb0636e0018 2741 
python-django_2.2.4-1.dsc
 16a5d54411599780ac9dfe3b9b38f90f785c51259a584e0b24b6f14a7f69aae8 8856979 
python-django_2.2.4.orig.tar.gz
 

Bug#933914: python3-pytest: pytest v4 breaks existing tests

[Drew Parsons]

On 2019-08-05 16:37, Novy, Ondrej wrote:

Tags: wontfix

On Mon, 05 Aug 2019 11:43:39 +0800 Drew Parsons 
 wrote:


This upgrade should be treated as a Transition, uploading the

package to

experimental first.


We are not using Transitions for Python upgrades because almost every
module upgrade breaks something. It's too much overhead for us. Last
time I uploaded pytest to experimental first and send information to
ML, nothing happened [1].



There seem to be regularities in the pytest4 error message, i.e. the 
same errors are reported in the different packages.


It would be helpful to have an indication of the common patches that 
will be needed to address them.


e.g what to do about

INTERNALERROR> Traceback (most recent call last):
INTERNALERROR>   File "/usr/lib/python3/dist-packages/_pytest/main.py", 
line 206, in wrap_session

INTERNALERROR> session.exitstatus = doit(config, session) or 0
INTERNALERROR>   File "/usr/lib/python3/dist-packages/_pytest/main.py", 
line 250, in _main

INTERNALERROR> config.hook.pytest_runtestloop(session=session)
INTERNALERROR>   File "/usr/lib/python3/dist-packages/pluggy/hooks.py", 
line 289, in __call__
INTERNALERROR> return self._hookexec(self, self.get_hookimpls(), 
kwargs)
INTERNALERROR>   File 
"/usr/lib/python3/dist-packages/pluggy/manager.py", line 87, in 
_hookexec

INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR>   File 
"/usr/lib/python3/dist-packages/pluggy/manager.py", line 81, in 
INTERNALERROR> firstresult=hook.spec.opts.get("firstresult") if 
hook.spec else False,
INTERNALERROR>   File 
"/usr/lib/python3/dist-packages/pluggy/callers.py", line 208, in 
_multicall

INTERNALERROR> return outcome.get_result()
INTERNALERROR>   File 
"/usr/lib/python3/dist-packages/pluggy/callers.py", line 80, in 
get_result

INTERNALERROR> raise ex[1].with_traceback(ex[2])
INTERNALERROR>   File 
"/usr/lib/python3/dist-packages/pluggy/callers.py", line 187, in 
_multicall

INTERNALERROR> res = hook_impl.function(*args)
INTERNALERROR>   File "/usr/lib/python3/dist-packages/_pytest/main.py", 
line 271, in pytest_runtestloop
INTERNALERROR> item.config.hook.pytest_runtest_protocol(item=item, 
nextitem=nextitem)
INTERNALERROR>   File "/usr/lib/python3/dist-packages/pluggy/hooks.py", 
line 289, in __call__
INTERNALERROR> return self._hookexec(self, self.get_hookimpls(), 
kwargs)
INTERNALERROR>   File 
"/usr/lib/python3/dist-packages/pluggy/manager.py", line 87, in 
_hookexec

INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR>   File 
"/usr/lib/python3/dist-packages/pluggy/manager.py", line 81, in 
INTERNALERROR> firstresult=hook.spec.opts.get("firstresult") if 
hook.spec else False,
INTERNALERROR>   File 
"/usr/lib/python3/dist-packages/pluggy/callers.py", line 208, in 
_multicall

INTERNALERROR> return outcome.get_result()
INTERNALERROR>   File 
"/usr/lib/python3/dist-packages/pluggy/callers.py", line 80, in 
get_result

INTERNALERROR> raise ex[1].with_traceback(ex[2])
INTERNALERROR>   File 
"/usr/lib/python3/dist-packages/pluggy/callers.py", line 187, in 
_multicall

INTERNALERROR> res = hook_impl.function(*args)
INTERNALERROR>   File 
"/usr/lib/python3/dist-packages/flaky/flaky_pytest_plugin.py", line 81, 
in pytest_runtest_protocol

INTERNALERROR> self.runner.pytest_runtest_protocol(item, nextitem)
INTERNALERROR>   File 
"/usr/lib/python3/dist-packages/_pytest/runner.py", line 78, in 
pytest_runtest_protocol

INTERNALERROR> runtestprotocol(item, nextitem=nextitem)
INTERNALERROR>   File 
"/usr/lib/python3/dist-packages/_pytest/runner.py", line 87, in 
runtestprotocol

INTERNALERROR> rep = call_and_report(item, "setup", log)
INTERNALERROR>   File 
"/usr/lib/python3/dist-packages/flaky/flaky_pytest_plugin.py", line 118, 
in call_and_report

INTERNALERROR> call = self.call_runtest_hook(item, when, **kwds)
INTERNALERROR>   File 
"/usr/lib/python3/dist-packages/flaky/flaky_pytest_plugin.py", line 272, 
in call_runtest_hook

INTERNALERROR> when=when,
INTERNALERROR> TypeError: __init__() missing 3 required positional 
arguments: 'excinfo', 'start', and 'stop'

Bug#902162: closed by Petter Reinholdtsen (Re: fixed 902162 in 2.2.5-2)

[Santiago Vila]

reopen 902162
found 902162 2.0.0-1
fixed 902162 2.3.1-3
thanks

Hi.

Could we please fix this in stretch?
(Packages in stretch must be buildable in stretch)

Thanks.

Bug#934026: python-django: CVE-2019-14232 CVE-2019-14233 CVE-2019-14234 CVE-2019-14235

[Chris Lamb]

[Adding t...@security.debian.org to CC]

Chris Lamb wrote:

> The following vulnerabilities were published for python-django.
> 
> CVE-2019-14232[0]:
> CVE-2019-14233[1]:
> CVE-2019-14234[2]:
> CVE-2019-14235[3]:

I have just fixed this in sid and will fix this in jessie LTS shortly.

Security team (added to CC), would you be interested in uploads for
buster (currently 1:1.11.22-1~deb10u1) and stretch (currently
1:1.10.7-2+deb9u5)?


Regards,

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

Bug#934026: marked as pending in python-django

[Chris Lamb]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/python-django/commit/0aa461b77c83d4f417fd59f9f7c467b87f429040


New upstream security release. 
 (Closes: 
#934026)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/934026

Processed: Bug#934026 marked as pending in python-django

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #934026 [python-django] python-django: CVE-2019-14232 CVE-2019-14233 
CVE-2019-14234 CVE-2019-14235
Added tag(s) pending.

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

Processed: tagging 934026

[Debian Bug Tracking System]

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

> tags 934026 + upstream fixed-upstream
Bug #934026 [python-django] python-django: CVE-2019-14232 CVE-2019-14233 
CVE-2019-14234 CVE-2019-14235
Added tag(s) fixed-upstream and upstream.
> thanks
Stopping processing here.

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

Processed: Re: Bug#902162 closed by Petter Reinholdtsen (Re: fixed 902162 in 2.2.5-2)

[Debian Bug Tracking System]

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

> reopen 902162
Bug #902162 {Done: Petter Reinholdtsen } 
[src:translate-toolkit] translate-toolkit: FTBFS in stretch (broken by change 
in Africa/Windhoek timezone)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions translate-toolkit/2.2.5-2 and 2.2.5-2.
> found 902162 2.0.0-1
Bug #902162 [src:translate-toolkit] translate-toolkit: FTBFS in stretch (broken 
by change in Africa/Windhoek timezone)
Ignoring request to alter found versions of bug #902162 to the same values 
previously set
> fixed 902162 2.3.1-3
Bug #902162 [src:translate-toolkit] translate-toolkit: FTBFS in stretch (broken 
by change in Africa/Windhoek timezone)
Marked as fixed in versions translate-toolkit/2.3.1-3.
> thanks
Stopping processing here.

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

Processed: Unarchive

[Debian Bug Tracking System]

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

> unarchive 902162
Bug #902162 {Done: Petter Reinholdtsen } 
[src:translate-toolkit] translate-toolkit: FTBFS in stretch (broken by change 
in Africa/Windhoek timezone)
Unarchived Bug 902162
>
End of message, stopping processing here.

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

Bug#934026: python-django: CVE-2019-14232 CVE-2019-14233 CVE-2019-14234 CVE-2019-14235

[Chris Lamb]

Package: python-django
Version: 1.7.11-1+deb8u6
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for python-django.

CVE-2019-14232[0]:
| An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before
| 2.1.11, and 2.2.x before 2.2.4. If django.utils.text.Truncator's
| chars() and words() methods were passed the html=True argument, they
| were extremely slow to evaluate certain inputs due to a catastrophic
| backtracking vulnerability in a regular expression. The chars() and
| words() methods are used to implement the truncatechars_html and
| truncatewords_html template filters, which were thus vulnerable.


CVE-2019-14233[1]:
| An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before
| 2.1.11, and 2.2.x before 2.2.4. Due to the behaviour of the underlying
| HTMLParser, django.utils.html.strip_tags would be extremely slow to
| evaluate certain inputs containing large sequences of nested
| incomplete HTML entities.


CVE-2019-14234[2]:
SQL injection possibility in key and index lookups for JSONField/HStoreField

CVE-2019-14235[3]:
| An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before
| 2.1.11, and 2.2.x before 2.2.4. If passed certain inputs,
| django.utils.encoding.uri_to_iri could lead to significant memory
| usage due to a recursion when repercent-encoding invalid UTF-8 octet
| sequences.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-14232
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14232
[1] https://security-tracker.debian.org/tracker/CVE-2019-14233
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14233
[2] https://security-tracker.debian.org/tracker/CVE-2019-14234
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14234
[3] https://security-tracker.debian.org/tracker/CVE-2019-14235
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14235


Regards,

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

Bug#934016: marked as done (clangd-8: missing Breaks+Replaces: clang-tools-8 (<< 1:8.0.1))

[Debian Bug Tracking System]

Your message dated Tue, 06 Aug 2019 08:59:36 +
with message-id 
and subject line Bug#934016: fixed in llvm-toolchain-8 1:8.0.1-2
has caused the Debian Bug report #934016,
regarding clangd-8: missing Breaks+Replaces: clang-tools-8 (<< 1:8.0.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.)


-- 
934016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clangd-8
Version: 1:8.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../clangd-8_1%3a8.0.1-1_amd64.deb ...
  Unpacking clangd-8 (1:8.0.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/clangd-8_1%3a8.0.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/llvm-8/bin/clangd', which is also in package 
clang-tools-8 1:8.0.1~+rc4-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/clangd-8_1%3a8.0.1-1_amd64.deb


cheers,

Andreas


clang-tools-8=1:8.0.1~+rc4-1_clangd-8=1:8.0.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-8
Source-Version: 1:8.0.1-2

We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-8, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 934...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
llvm-toolchain-8 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 06 Aug 2019 09:36:11 +0200
Source: llvm-toolchain-8
Binary: clang-8 clang-tools-8 clang-format-8 clang-tidy-8 clangd-8 clang-8-doc 
libclang1-8 libclang-8-dev libclang-common-8-dev libfuzzer-8-dev python-clang-8 
clang-8-examples libllvm8 llvm-8 llvm-8-runtime llvm-8-dev llvm-8-tools 
libllvm-8-ocaml-dev llvm-8-doc llvm-8-examples lld-8 liblld-8 liblld-8-dev 
lldb-8 liblldb-8 python-lldb-8 python3-lldb-8 liblldb-8-dev libomp-8-dev 
libomp5-8 libomp-8-doc libc++1-8 libc++-8-dev libc++abi1-8 libc++abi-8-dev
Architecture: source
Version: 1:8.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Gianfranco Costamagna 
Description:
 clang-8- C, C++ and Objective-C compiler
 clang-8-doc - C, C++ and Objective-C compiler - Documentation
 clang-8-examples - Clang examples
 clang-format-8 - Tool to format C/C++/Obj-C code
 clang-tidy-8 - clang-based C++ linter tool
 clang-tools-8 - clang-based tools for C/C++ developments
 clangd-8   - Language server that provides IDE-like features to editors
 libc++-8-dev - LLVM C++ Standard library (development files)
 libc++1-8  - LLVM C++ Standard library
 libc++abi-8-dev - LLVM low level support for a standard C++ library 
(development fi
 libc++abi1-8 - LLVM low level support for a standard C++ library
 libclang-8-dev - Clang library - Development package
 libclang-common-8-dev - Clang library - Common development package
 libclang1-8 - C interface to the Clang library
 libfuzzer-8-dev - Library for coverage-guided fuzz testing
 liblld-8   - LLVM-based linker, library
 liblld-8-dev - LLVM-based linker, header files
 liblldb-8  - Next generation, high-performance debugger, library
 liblldb-8-dev - Next generation, high-performance debugger, header files
 libllvm-8-ocaml-dev - Modular compiler and toolchain technologies, OCaml 
bindings
 libllvm8   - Modular compiler and toolchain technologies, runtime library
 libomp-8-dev - LLVM OpenMP runtime - dev package
 libomp-8-doc - LLVM OpenMP runtime - Documentation
 libomp5-8  - LLVM OpenMP runtime
 lld-8  - LLVM-based linker
 lldb-8 - Next generation, high-performance 

Bug#933930: [Pkg-utopia-maintainers] Bug#933930: network-manager: Ethernet connection no longer works

[Michael Biebl]

Control: tags -1 + moreinfo

Can you try and switch to dhclient instead of the internal one.


$ cat /etc/NetworkManager/conf.d/dhcp.conf
[main]
dhcp=dhclient


-- 
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: [Pkg-utopia-maintainers] Bug#933930: network-manager: Ethernet connection no longer works

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #933930 [network-manager] network-manager: Ethernet connection no longer 
works
Added tag(s) moreinfo.

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

Bug#857653: marked as done (liblld-4.0: missing liblld-4.0.so.1)

[Debian Bug Tracking System]

Your message dated Tue, 06 Aug 2019 08:54:44 +
with message-id 
and subject line Bug#857653: fixed in llvm-toolchain-7 1:7.0.1-9
has caused the Debian Bug report #857653,
regarding liblld-4.0: missing liblld-4.0.so.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.)


-- 
857653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblld-4.0
Version: missing liblld-4.0.so.1
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...):

0m24.5s ERROR: FAIL: Broken symlinks:
  /usr/lib/llvm-4.0/lib/liblld.so.1 -> ../../x86_64-linux-gnu/liblld-4.0.so.1
  /usr/lib/x86_64-linux-gnu/liblld-4.0.so -> liblld-4.0.so.1
  /usr/lib/python2.7/dist-packages/lld-4.0/_lld.so -> 
../../../x86_64-linux-gnu/liblld-4.0.so

liblld-4.0.so.1 does not seem to exist anywhere, I could only find
  /usr/lib/llvm-4.0/lib/liblld.so.1

liblld-5.0 has the same problems.


cheers,

Andreas


liblld-4.0_1:4.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-7
Source-Version: 1:7.0.1-9

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
llvm-toolchain-7 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 21 Apr 2019 22:55:47 +0200
Source: llvm-toolchain-7
Binary: clang-7 clang-tools-7 clang-format-7 clang-tidy-7 clang-7-doc 
libclang1-7 libclang-7-dev libclang-common-7-dev libfuzzer-7-dev python-clang-7 
clang-7-examples libllvm7 llvm-7 llvm-7-runtime llvm-7-dev llvm-7-tools 
libllvm-7-ocaml-dev llvm-7-doc llvm-7-examples lld-7 liblld-7 liblld-7-dev 
lldb-7 liblldb-7 python-lldb-7 liblldb-7-dev libomp-7-dev libomp5-7 
libomp-7-doc libc++1-7 libc++-7-dev libc++abi1-7 libc++abi-7-dev
Architecture: source
Version: 1:7.0.1-9
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Gianfranco Costamagna 
Description:
 clang-7- C, C++ and Objective-C compiler
 clang-7-doc - C, C++ and Objective-C compiler - Documentation
 clang-7-examples - Clang examples
 clang-format-7 - Tool to format C/C++/Obj-C code
 clang-tidy-7 - clang-based C++ linter tool
 clang-tools-7 - clang-based tools for C/C++ developments
 libc++-7-dev - LLVM C++ Standard library (development files)
 libc++1-7  - LLVM C++ Standard library
 libc++abi-7-dev - LLVM low level support for a standard C++ library 
(development fi
 libc++abi1-7 - LLVM low level support for a standard C++ library
 libclang-7-dev - Clang library - Development package
 libclang-common-7-dev - Clang library - Common development package
 libclang1-7 - C interface to the Clang library
 libfuzzer-7-dev - Library for coverage-guided fuzz testing
 liblld-7   - LLVM-based linker, library
 liblld-7-dev - LLVM-based linker, header files
 liblldb-7  - Next generation, high-performance debugger, library
 liblldb-7-dev - Next generation, high-performance debugger, header files
 libllvm-7-ocaml-dev - Modular compiler and toolchain technologies, OCaml 
bindings
 libllvm7   - Modular compiler and toolchain technologies, runtime library
 libomp-7-dev - LLVM OpenMP runtime - dev package
 libomp-7-doc - LLVM OpenMP runtime - Documentation
 libomp5-7  - LLVM OpenMP runtime
 lld-7  - LLVM-based linker
 lldb-7 - Next generation, high-performance debugger
 llvm-7 - Modular compiler and toolchain technologies
 llvm-7-dev - Modular compiler and toolchain technologies, libraries and header
 llvm-7-doc - Modular compiler and toolchain technologies, documentation
 llvm-7-examples - Modular compiler and toolchain technologies, examples
 llvm-7-runtime - Modular compiler and toolchain technologies, IR interpreter
 llvm-7-tools - Modular compiler and toolchain technologies, tools
 python-clang-7 - Clang Python Bindings
 python-lldb-7 - 

Bug#933268: closed by Josue Ortega (Bug#933268: fixed in rpcbind 1.2.5-5)

[Michael Biebl]

Am 06.08.19 um 09:15 schrieb Michael Biebl:
> Am 06.08.19 um 04:48 schrieb Debian Bug Tracking System:
>>  rpcbind (1.2.5-5) unstable; urgency=medium
>>  .
>>* debian/rules: Add --no-restart-after-upgrade option to
>>  dh_installsystemd to avoid race condition at rpcbind.socket
>>  initialization (Closes: #933268)
> 
> https://salsa.debian.org/debian/rpcbind/commit/6bdd9256f811ed312173eeb9e9ca7f600720769b
> 
> I don't think this is a proper fix. After all, you typically want a
> daemon to be restarted after upgrades so (security) fixes are applied.
> I also notice, that the above commit contains other (unrelated) changes
> which are not mentioned in the changelog.
> 
> 
> A quick test shows, that debhelper creates the following code and
> executing that manually triggers the same error:
> 
> # systemctl restart rpcbind.service rpcbind.socket
> 
> Job for rpcbind.socket failed.
> See "systemctl status rpcbind.socket" and "journalctl -xe" for details.
> A dependency job for rpcbind.service failed. See 'journalctl -xe' for
> details.
> 
> This needs further investigation, where the underlying problem is.
> For the time being, I would suggest a different workaround, ie.
> restarting rpcbind.service and rpcbind.socket sequentially (or only
> rpcbind.service, I think that should be sufficient)
> 
> 
> So somehting like this:
> override_dh_installsystemd:
>  dh_installsystemd rpcbind.socket
>   dh_installsystemd rpcbind.service
> 
> 
> I'm not yet sure if this is a bug in systemd itself, in rpcbind or
> debhelper for generating such a code sequence, so CCing all affected
> parties.
> 

I've filed https://github.com/systemd/systemd/issues/13271 in the mean
time, asking for input from systemd upstream.

-- 
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

Bug#902241: fixed in python-proliantutils 2.6.0-2

[Santiago Vila]

reopen 902241
found 902241 2.1.11-2
fixed 902241 2.6.0-2
thanks

Hi.

Could we please fix this in stretch? After all, this is what I
reported initially (packages in stretch must be buildable in stretch).

Thanks.

Processed: Re: Bug#902241: fixed in python-proliantutils 2.6.0-2

[Debian Bug Tracking System]

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

> reopen 902241
Bug #902241 {Done: Thomas Goirand } [src:python-proliantutils] 
python-proliantutils: FTBFS in stretch (AssertionError: IloConnectionError not 
raised)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions python-proliantutils/2.5.0-3 and 
python-proliantutils/2.6.0-2.
> found 902241 2.1.11-2
Bug #902241 [src:python-proliantutils] python-proliantutils: FTBFS in stretch 
(AssertionError: IloConnectionError not raised)
Ignoring request to alter found versions of bug #902241 to the same values 
previously set
> fixed 902241 2.6.0-2
Bug #902241 [src:python-proliantutils] python-proliantutils: FTBFS in stretch 
(AssertionError: IloConnectionError not raised)
Marked as fixed in versions python-proliantutils/2.6.0-2.
> thanks
Stopping processing here.

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

Bug#933921: src:python-tablib: Unsafe use of yaml.load()

[Thomas Goirand]

On 8/6/19 1:58 AM, Joseph Herlant wrote:
> Hi,
> 
> Thanks Scott for the report.
> Tomas: the repository in Openstack was archived long ago because it
> was ported to https://salsa.debian.org/python-team/modules/python-tablib
> The module is used by other packages than openstack (like
> django-tables if I remember correctly), so could you please hold off
> the removal request please?
> If the repo in the openstack group bother you, you can drop it but
> please don't drop tablib (at least not the python3 version).
> 
> Thanks,
> Joseph
> 

Indeed, it has a single reverse build-depends. Closing the RM bug then.
I'd still advise upstream against using this library which is of lower
code quality.

Cheers,

Thomas Goirand (zigo)

Processed: Unarchive

[Debian Bug Tracking System]

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

> unarchive 902241
Bug #902241 {Done: Thomas Goirand } [src:python-proliantutils] 
python-proliantutils: FTBFS in stretch (AssertionError: IloConnectionError not 
raised)
Unarchived Bug 902241
> thanks
Stopping processing here.

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

Bug#933743: marked as done (LibXSLT in Debian stable has three unpatched security vulnerabilities)

[Debian Bug Tracking System]

Your message dated Tue, 06 Aug 2019 07:36:22 +
with message-id 
and subject line Bug#933743: fixed in libxslt 1.1.32-2.1
has caused the Debian Bug report #933743,
regarding LibXSLT in Debian stable has three unpatched security vulnerabilities
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.)


-- 
933743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libxslt1.1
Version: 1.1.32-2
Severity: grave

The upstream version of LibXSLT shipped in Debian stable (1.1.32) has
the following three CVEs reported against it:

https://nvd.nist.gov/vuln/detail/CVE-2019-11068
https://nvd.nist.gov/vuln/detail/CVE-2019-13117
https://nvd.nist.gov/vuln/detail/CVE-2019-13118

Debian has taken notice of these, but has only patched them in jessie
(a.k.a. oldoldstable):

https://lists.debian.org/debian-lts-announce/2019/04/msg00016.html
https://lists.debian.org/debian-lts-announce/2019/07/msg00020.html

The current jessie package version of LibXSLT (1.1.28-2+deb8u5) contains
the following patch files:

CVE-2019-11068.patch
CVE-2019-13117.patch
CVE-2019-13118.patch

These are not present in 1.1.32-2, and so these vulnerabilities appear
to be exploitable in Debian stable, testing, and sid.

The current upstream release of LibXSLT is 1.1.33, which unfortunately
still has the above three CVEs. However, they appear to have been
patched in Git.
--- End Message ---
--- Begin Message ---
Source: libxslt
Source-Version: 1.1.32-2.1

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated libxslt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 04 Aug 2019 08:14:05 +0200
Source: libxslt
Architecture: source
Version: 1.1.32-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian XML/SGML Group 
Changed-By: Salvatore Bonaccorso 
Closes: 926895 931320 931321 933743
Changes:
 libxslt (1.1.32-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix security framework bypass (CVE-2019-11068) (Closes: #926895, #933743)
   * Fix uninitialized read of xsl:number token (CVE-2019-13117)
 (Closes: #931321, #933743)
   * Fix uninitialized read with UTF-8 grouping chars (CVE-2019-13118)
 (Closes: #931320, #933743)
Checksums-Sha1: 
 9edb1b30d9652d632d49a7667201b4ad51e3f15c 2502 libxslt_1.1.32-2.1.dsc
 253481a7c31a78d1c9ace6da37af3e50934fe016 33792 libxslt_1.1.32-2.1.debian.tar.xz
Checksums-Sha256: 
 bc9454624f5127960244d433676a654c96790ed3c3e5c01b416188953a0f3421 2502 
libxslt_1.1.32-2.1.dsc
 68a20c62f69574822af5f01e807228fbaf5ab23868df3a2b57d4915d0f799dd7 33792 
libxslt_1.1.32-2.1.debian.tar.xz
Files: 
 6e2048b8d013183e16ce2d39d418f7bc 2502 text optional libxslt_1.1.32-2.1.dsc
 b586dca5cf29e1dc6e02dc4473d66509 33792 text optional 
libxslt_1.1.32-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl1GhE5fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E4LUP/RxDTCzHKUltsGsmEF13WU+CUaVSRdFQ
K+6oxKLcQY4+HZ3MRemmk/ugVapyyvNnTyQt9OHpM7ZRmL8+y5DOZysVpjR3ofOE
F0EaxDQcLOQl7FX7WFns33K81D5i9qkZkrsSQJmu0SVPlN2+0KcuUQBoIDuDQixP
qaMJqk5ymk5A+MYbFfDGVmSpWGBHpYwlUudkoz0wfBDk9CpkbCXaCi/LNGQ1Ug/n
UwOqKtgfhaysrABW3OrbvwhJfqWsOiA+jskuwmq9wtGuTEhPIOVfqO3NZZFJ6qNH
JDIgCO/8YVKYK2bsk8kaXYRl2DPELyYsbB/K5+B5PRYHQ5Dk2hESNZw9bL0XuBK4
0khk83pD9BN3rlWFpCGJA+C/Jv5pEylok5U0AfIx8ex0d/u993e+ElKa7+JMpgfE
l5UkDEApj7+3AA4f/sDcCDn0vUfXbXhHoZP1cff33RdceyQz08D/SckwKA1UC6v7
00vNiovK7FGXHD+u8KelAWwAdckn8lIuqJRrHCnQMlTD0vcIibhuh4rOaeujTG7J
2DFDRu7tJ4DFj69br1wCrMVIRgcIv34WJ+U894b0YySVrKU0xF1vCN1eaN8CMo+t
315K1Dyu7u2xuFuE8Y6mjA8OPv0u+EiYOYz9O/vc2LLxlcdSAG7v7z6X62eY8mVe
RxInCDFuWQtl
=Fm9U
-END PGP SIGNATURE End Message ---

Bug#933268: closed by Josue Ortega (Bug#933268: fixed in rpcbind 1.2.5-5)

[Michael Biebl]

Am 06.08.19 um 04:48 schrieb Debian Bug Tracking System:
>  rpcbind (1.2.5-5) unstable; urgency=medium
>  .
>* debian/rules: Add --no-restart-after-upgrade option to
>  dh_installsystemd to avoid race condition at rpcbind.socket
>  initialization (Closes: #933268)

https://salsa.debian.org/debian/rpcbind/commit/6bdd9256f811ed312173eeb9e9ca7f600720769b

I don't think this is a proper fix. After all, you typically want a
daemon to be restarted after upgrades so (security) fixes are applied.
I also notice, that the above commit contains other (unrelated) changes
which are not mentioned in the changelog.


A quick test shows, that debhelper creates the following code and
executing that manually triggers the same error:

# systemctl restart rpcbind.service rpcbind.socket

Job for rpcbind.socket failed.
See "systemctl status rpcbind.socket" and "journalctl -xe" for details.
A dependency job for rpcbind.service failed. See 'journalctl -xe' for
details.

This needs further investigation, where the underlying problem is.
For the time being, I would suggest a different workaround, ie.
restarting rpcbind.service and rpcbind.socket sequentially (or only
rpcbind.service, I think that should be sufficient)


So somehting like this:
override_dh_installsystemd:
   dh_installsystemd rpcbind.socket
dh_installsystemd rpcbind.service


I'm not yet sure if this is a bug in systemd itself, in rpcbind or
debhelper for generating such a code sequence, so CCing all affected
parties.
-- 
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

Bug#934021: libsidplayfp5: missing Breaks+Replaces: libsidplayfp4

[Andreas Beckmann]

Package: libsidplayfp5
Version: 2.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../libsidplayfp5_2.0.0-1_amd64.deb ...
  Unpacking libsidplayfp5:amd64 (2.0.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libsidplayfp5_2.0.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libstilview.so.0', which is 
also in package libsidplayfp4:amd64 1.8.8-1
  Errors were encountered while processing:
   /var/cache/apt/archives/libsidplayfp5_2.0.0-1_amd64.deb


Mixing shared libraries with uncorrelated SOVERSIONS in one binary
package is not recommended, since it requires strict Breaks+Replaces,
preventing co-installability and smooth upgrades.


cheers,

Andreas


libsidplayfp4=1.8.8-1_libsidplayfp5=2.0.0-1.log.gz
Description: application/gzip

Bug#933731: marked as done (audacity: FTBFS on 32-bit arches (except i386))

[Debian Bug Tracking System]

Your message dated Tue, 06 Aug 2019 06:34:43 +
with message-id 
and subject line Bug#933731: fixed in audacity 2.3.2-2
has caused the Debian Bug report #933731,
regarding audacity: FTBFS on 32-bit arches (except i386)
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.)


-- 
933731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: audacity
Version: 2.3.2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

audacity 2.3.2-1 appears to FTBFS on 32-bit arches (except for i386):

/usr/include/c++/8/atomic:250: undefined reference to `__atomic_load_8'
/usr/bin/ld: /usr/include/c++/8/atomic:250: undefined reference to 
`__atomic_load_8'
/usr/bin/ld: audacity-AudioIO.o: in function 
`std::atomic::store(double, std::memory_order)':
/usr/include/c++/8/atomic:239: undefined reference to `__atomic_store_8'
/usr/bin/ld: audacity-AudioIO.o: in function 
`std::atomic::load(std::memory_order) const':
/usr/include/c++/8/atomic:250: undefined reference to `__atomic_load_8'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:2800: audacity] Error 1
make[3]: Leaving directory '/<>/src'
make[2]: *** [Makefile:1989: all] Error 2
make[2]: Leaving directory '/<>/src'
make[1]: *** [Makefile:820: all-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make -j4 returned exit code 2
make: *** [debian/rules:37: build-arch] Error 255

Could you please take a look?
--- End Message ---
--- Begin Message ---
Source: audacity
Source-Version: 2.3.2-2

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

Debian distribution maintenance software
pp.
Unit193  (supplier of updated audacity 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: SHA384

Format: 1.8
Date: Tue, 06 Aug 2019 02:01:08 -0400
Source: audacity
Binary: audacity audacity-data
Architecture: source
Version: 2.3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Unit193 
Description:
 audacity   - fast, cross-platform audio editor
 audacity-data - fast, cross-platform audio editor (data)
Closes: 933731
Changes:
 audacity (2.3.2-2) unstable; urgency=medium
 .
   * Team upload.
   * d/p/0006-Link-atomic-if-needed.patch: Link atomic if needed.
 (Closes: #933731)
Checksums-Sha1:
 3f2f851d2ba7ab88dc6e609c105e963cc7a5b91e 2983 audacity_2.3.2-2.dsc
 b91b88aa68521a03fa5cc7dacaf5eb39f92e3b6f 61972597 audacity_2.3.2.orig.tar.gz
 5a6784a739353a99af1f8b0f0d1bd131b5703fde 40336 audacity_2.3.2-2.debian.tar.xz
 a215d3952b3c4e2411aaf91f287289a2eadf2b5d 6453 audacity_2.3.2-2_source.buildinfo
Checksums-Sha256:
 2b91c90c0b997f36cfc3bee169995d343c2bacd69b9f1aa2e5b73ae079d158d4 2983 
audacity_2.3.2-2.dsc
 cc477a71ff5571c72887a7a155365b07a1a50bcea1abf490a4de7b884376c731 61972597 
audacity_2.3.2.orig.tar.gz
 123e236db7c744d391099125033f6a0a018cb0f2bf1c9ad7cbb7d87a60548e92 40336 
audacity_2.3.2-2.debian.tar.xz
 560e59843a61567a2d12a6d4112c409cce3a9e964348e52c6a27b378d198f225 6453 
audacity_2.3.2-2_source.buildinfo
Files:
 9dcb3af590f2fe12e6e105e993387876 2983 sound optional audacity_2.3.2-2.dsc
 ca1b5b5258e7a8839ca72bb20093b31b 61972597 sound optional 
audacity_2.3.2.orig.tar.gz
 2244722c6a6b65b8b64c5dfead6687a6 40336 sound optional 
audacity_2.3.2-2.debian.tar.xz
 d140378cb777ac32bb3b5b1a9af3fd76 6453 sound optional 
audacity_2.3.2-2_source.buildinfo
Checksums-Sha512:
 
0da619aa3bc1e7aeb6f5f4cf5b95894aee3e50c587e5f0e7418c5e06505b88c0570e689da6ff98e534eeb8336aa79b7efb66c12e2f04b55480318c4a82114c78
 2983 audacity_2.3.2-2.dsc
 
a59d6e9e974d5f78f5ca561e3bea31fc1b3e88f9ea60b2df7ce8bcec264d886f3fdc8f20030e11a86daff8ffeb735850b5e5f73c45fbef0bfcc58692423e7cd0
 61972597 audacity_2.3.2.orig.tar.gz
 
f60ac0e1c197c6ed3cfc3d45ad78a94a868d2bb7db0114eddbc172397beab89e61a1b81ede8ba6e22335f69baec21087419dd8a8b15373fb940c3a3c8cb34bda
 40336 audacity_2.3.2-2.debian.tar.xz
 

Bug#908678: Update on the security-tracker git discussion

[Salvatore Bonaccorso]

Hi Bastian,

Thanks for keeping track and following up.

On Tue, Aug 06, 2019 at 08:05:11AM +0200, Bastian Blank wrote:
> Moin
> 
> On Tue, Jul 02, 2019 at 01:38:10PM +0200, Moritz Muehlenhoff wrote:
> > On Tue, Jul 02, 2019 at 01:25:43PM +0200, Salvatore Bonaccorso wrote:
> > > p.s.: Question is if we should do a split as well for the other types of
> > >   files which are supported (DSA, TDSA, ...) while at it.
> > We can axe out DTSA/* while we're at it.
> > For DSA/list (and DLA/list) we can initially keep it as a single file, it 
> > can
> > still be split later on if necessary.
> 
> Following up to 
> 
> | Please provide a plan how and when to fix this before 2019-06-30.
> 
> We have now one month later.  Please provide the plan.

The items in
https://salsa.debian.org/security-tracker-team/security-tracker-service/issues/1
needs further detailed and then sorted/prioritized. Later actual
implementation work on making the split possible on tracker and other
tooling side needs to happen. We cannot depend on a non-functional
instance for the day to day work, so all of the above basically will
need to be ported in some sensible way.

Progress is slow due to other time limitations in day to day tasks.

Still if it is going to be too much burden for salsa admin and needs
to be fast, then I only see that we temporarily switch away from salsa
to gitlab or another hosting (github will not work) and then move back
once the split has finally happened.

Regards,
Salvatore

Bug#933731: marked as pending in audacity

[Unit 193]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/audacity/commit/600d50b2ee5f0c0b31aa72c456b8bde4259776dd


d/p/0006-Link-atomic-if-needed.patch: Link atomic if needed.

Closes: #933731


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/933731

Processed: Bug#933731 marked as pending in audacity

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #933731 [audacity] audacity: FTBFS on 32-bit arches (except i386)
Added tag(s) pending.

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

Bug#908678: Update on the security-tracker git discussion

[Bastian Blank]

Moin

On Tue, Jul 02, 2019 at 01:38:10PM +0200, Moritz Muehlenhoff wrote:
> On Tue, Jul 02, 2019 at 01:25:43PM +0200, Salvatore Bonaccorso wrote:
> > p.s.: Question is if we should do a split as well for the other types of
> >   files which are supported (DSA, TDSA, ...) while at it.
> We can axe out DTSA/* while we're at it.
> For DSA/list (and DLA/list) we can initially keep it as a single file, it can
> still be split later on if necessary.

Following up to 

| Please provide a plan how and when to fix this before 2019-06-30.

We have now one month later.  Please provide the plan.

Bastian

-- 
We do not colonize.  We conquer.  We rule.  There is no other way for us.
-- Rojan, "By Any Other Name", stardate 4657.5

Bug#934016: clangd-8: missing Breaks+Replaces: clang-tools-8 (<< 1:8.0.1)

[Andreas Beckmann]

Package: clangd-8
Version: 1:8.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../clangd-8_1%3a8.0.1-1_amd64.deb ...
  Unpacking clangd-8 (1:8.0.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/clangd-8_1%3a8.0.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/llvm-8/bin/clangd', which is also in package 
clang-tools-8 1:8.0.1~+rc4-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/clangd-8_1%3a8.0.1-1_amd64.deb


cheers,

Andreas


clang-tools-8=1:8.0.1~+rc4-1_clangd-8=1:8.0.1-1.log.gz
Description: application/gzip

Bug#866371: marked as done (FP register corruption on ppc64el with lock elision)

[Debian Bug Tracking System]

Your message dated Tue, 06 Aug 2019 06:00:12 +
with message-id 
and subject line Bug#866122: fixed in linux 5.2.6-1
has caused the Debian Bug report #866122,
regarding FP register corruption on ppc64el with lock elision
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.)


-- 
866122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openldap
Version: 2.4.44+dfsg-6
Severity: serious

https://buildd.debian.org/status/logs.php?pkg=openldap=ppc64el
https://buildd.debian.org/status/logs.php?pkg=openldap=ppc64

...
> Starting test060-mt-hot for bdb...
running defines.sh
Running slapadd to build slapd database...
Running slapindex to index slapd database...
Starting slapd on TCP/IP port 9011...
/<>/openldap-2.4.44+dfsg/debian/build/tests/../servers/slapd/slapd 
-s0 -f 
/<>/openldap-2.4.44+dfsg/debian/build/tests/testrun/slapd.1.conf -h 
ldap://localhost:9011/ -d stats
Testing basic monitor search...
Monitor searches
Testing basic mt-hot search: 1 threads (1 x 5) loops...
./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com 
-w secret -e cn=Monitor -m 1 -L 1 -l 5
Testing basic mt-hot search: 5 threads (1 x 1) loops...
./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com 
-w secret -e cn=Monitor -m 5 -L 1 -l 1
Testing basic mt-hot search: 100 threads (5 x 100) loops...
./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com 
-w secret -e cn=Monitor -m 100 -L 5 -l 100
Random searches
Testing random mt-hot search: 1 threads (1 x 5) loops...
./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com 
-w secret -e dc=example,dc=com -f (objectclass=*) -m 1 -L 1 -l 5
Testing random mt-hot search: 5 threads (1 x 1) loops...
./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com 
-w secret -e dc=example,dc=com -f (objectclass=*) -m 5 -L 1 -l 1
slapd-mtread failed (139)!
> test060-mt-hot failed for bdb
(exit 139)
Makefile:296: recipe for target 'bdb-mod' failed
make[3]: *** [bdb-mod] Error 139
make[3]: Leaving directory 
'/<>/openldap-2.4.44+dfsg/debian/build/tests'
Makefile:282: recipe for target 'test' failed
make[2]: *** [test] Error 2
make[2]: Leaving directory 
'/<>/openldap-2.4.44+dfsg/debian/build/tests'
Makefile:294: recipe for target 'test' failed
make[1]: *** [test] Error 2
make[1]: Leaving directory '/<>/openldap-2.4.44+dfsg/debian/build'
dh_auto_test: make -j8 test VERBOSE=1 returned exit code 2
debian/rules:68: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.2.6-1

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 05 Aug 2019 02:27:14 +0100
Binary: linux-doc-5.2 linux-headers-5.2.0-1-common 
linux-headers-5.2.0-1-common-rt linux-source-5.2 linux-support-5.2.0-1
Source: linux
Architecture: all source
Version: 5.2.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 866122 872069 914511 920651 921019 927791 928451 929938 929968 931247 
931374 931752 932722 933228 933603
Description: 
 linux-doc-5.2 - Linux kernel specific documentation for version 5.2
 linux-headers-5.2.0-1-common - Common header files for Linux 5.2.0-1
 linux-headers-5.2.0-1-common-rt - Common header files for Linux 5.2.0-1-rt
 linux-source-5.2 - Linux kernel source for version 5.2 with Debian patches
 linux-support-5.2.0-1 - Support files for Linux 5.2
Changes:
 linux (5.2.6-1) unstable; urgency=medium
 .
   * New upstream release:
 https://kernelnewbies.org/Linux_5.1
 https://kernelnewbies.org/Linux_5.2
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.1
 

Bug#866122: marked as done (FP register corruption on ppc64el with lock elision)

[Debian Bug Tracking System]

Your message dated Tue, 06 Aug 2019 06:00:12 +
with message-id 
and subject line Bug#866122: fixed in linux 5.2.6-1
has caused the Debian Bug report #866122,
regarding FP register corruption on ppc64el with lock elision
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.)


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

Source: openldap
Version: 2.4.44+dfsg-6
Severity: important

test060-mt-hot for bdb failed twice in a row on the ppc64el buildd
(ppc64el-osuosl-01), however a binary-only upload (presumably on a 
porterbox) built successfully.



Starting test060-mt-hot for bdb...

running defines.sh
Running slapadd to build slapd database...
Running slapindex to index slapd database...
Starting slapd on TCP/IP port 9011...
/<>/openldap-2.4.44+dfsg/debian/build/tests/../servers/slapd/slapd -s0 -f 
/<>/openldap-2.4.44+dfsg/debian/build/tests/testrun/slapd.1.conf -h 
ldap://localhost:9011/ -d stats
Testing basic monitor search...
Monitor searches
Testing basic mt-hot search: 1 threads (1 x 5) loops...
./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com 
-w secret -e cn=Monitor -m 1 -L 1 -l 5
Testing basic mt-hot search: 5 threads (1 x 1) loops...
./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com 
-w secret -e cn=Monitor -m 5 -L 1 -l 1
Testing basic mt-hot search: 100 threads (5 x 100) loops...
./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com 
-w secret -e cn=Monitor -m 100 -L 5 -l 100
Random searches
Testing random mt-hot search: 1 threads (1 x 5) loops...
./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com 
-w secret -e dc=example,dc=com -f (objectclass=*) -m 1 -L 1 -l 5
Testing random mt-hot search: 5 threads (1 x 1) loops...
./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com 
-w secret -e dc=example,dc=com -f (objectclass=*) -m 5 -L 1 -l 1
slapd-mtread failed (139)!

test060-mt-hot failed for bdb

(exit 139)
Makefile:296: recipe for target 'bdb-mod' failed
make[3]: *** [bdb-mod] Error 139
make[3]: Leaving directory 
'/<>/openldap-2.4.44+dfsg/debian/build/tests'
Makefile:282: recipe for target 'test' failed
make[2]: *** [test] Error 2
make[2]: Leaving directory 
'/<>/openldap-2.4.44+dfsg/debian/build/tests'
Makefile:294: recipe for target 'test' failed
make[1]: *** [test] Error 2
make[1]: Leaving directory '/<>/openldap-2.4.44+dfsg/debian/build'
dh_auto_test: make -j4 test VERBOSE=1 returned exit code 2
debian/rules:68: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.2.6-1

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 05 Aug 2019 02:27:14 +0100
Binary: linux-doc-5.2 linux-headers-5.2.0-1-common 
linux-headers-5.2.0-1-common-rt linux-source-5.2 linux-support-5.2.0-1
Source: linux
Architecture: all source
Version: 5.2.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 866122 872069 914511 920651 921019 927791 928451 929938 929968 931247 
931374 931752 932722 933228 933603
Description: 
 linux-doc-5.2 - Linux kernel specific documentation for version 5.2
 linux-headers-5.2.0-1-common - Common header files for Linux 5.2.0-1
 linux-headers-5.2.0-1-common-rt - Common header files for Linux 5.2.0-1-rt
 linux-source-5.2 - Linux kernel source for version 5.2 with Debian patches
 linux-support-5.2.0-1 - Support files for Linux 5.2
Changes:
 linux (5.2.6-1) unstable; urgency=medium
 .
   * New upstream release:
 https://kernelnewbies.org/Linux_5.1
 https://kernelnewbies.org/Linux_5.2
 .
   * New upstream stable