Bug#906131: CVE-2018-14722

[Nicholas D Steeves]

Dear Moritz and Sven,

On Tue, Aug 14, 2018 at 07:24:26PM +0200, Moritz Muehlenhoff wrote:
> Package: btrfsmaintenance
> Severity: grave
> Tags: security
> 
> Please see http://www.openwall.com/lists/oss-security/2018/08/14/7
> 
> Cheers,
> Moritz

Thank you for forwarding this report.  Unfortunately I do not yet have
DM for btrfsmaintenance so cannot upload.  I've CCed Sven in case he
wants to sponsor, but if he's on holidays would you be willing to
sponsor it?

I've uploaded to mentors

  https://mentors.debian.net/package/btrfsmaintenance
  dget 
https://mentors.debian.net/debian/pool/main/b/btrfsmaintenance/btrfsmaintenance_0.4.1-2.dsc

The package's repo can also be cloned:
  git clone https://salsa.debian.org/sten-guest/btrfsmaintenance.git

I don't use dgit, except to quickly download the latest
orig.tarball...  Maybe something like this would be fastest:
  dgit clone btrfsmaintenance
  cd btrfsmaintenace
  git remote add salsa https://salsa.debian.org/sten-guest/btrfsmaintenance.git
  git fetch salsa && git merge --allow-unrelated-histories -X theirs 
salsa/master

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#906152: libopenblas-base: version 0.3.2+ds-1 makes gimp hang indefinitely

[Rogério Brito]

Package: libopenblas-base
Version: 0.3.2+ds-1
Severity: serious
Justification: breaks unrelated software

Hi.

First of all, I selected serious instead of the more appropriate critical
severity because I don't want to severity inflation.

On the other hand, if you think that this is a severity too high, feel free
to set it to a more appropriate level (as long as we get everything fixed).

OK, now, to the actual report. With version 0.3.2 of openblas installed,
whenever I call gimp (I always start programs from the command line), it
just sits there and doesn't even show its splash screen.

If I interrupt the execution with Ctrl+C, then I get a "Segmentation fault"
message, which would lead me to think that the program would not even have
finished being linked to all the shared libraries that it needs.

If I run gimp under strace, I see that it hangs in a mutex call that never
proceeds.

I searched the web and I found the following discussion:
.

In it, it is suggested that the problem might have be with openblas and,
indeed, I removed libopenblas-base and voilá: with just atlas and the
reference blas installed, gimp fires up as expected on this machine.

This computer is, BTW, a notebook with a Core 2 Duo processor and, when I
start gimp now, I get the following message (that I used to get with
openblas before the upgrade to 0.3):

,
| Missing fast-path babl conversion detected, Implementing missing babl fast 
paths
| accelerates GEGL, GIMP and other software using babl, warnings are printed on
| first occurance of formats used where a conversion has to be synthesized
| programmatically by babl based on format description
| 
| *WARNING* missing babl fast path(s): "R'G'B' double" to "CIE Lab double"
`

If any further information is needed, please let me know.


Thanks,

Rogério Brito.

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

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

Versions of packages libopenblas-base depends on:
ii  libc6 2.27-5
ii  libgfortran5  8.2.0-3

libopenblas-base recommends no packages.

libopenblas-base suggests no packages.

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br

Bug#906003: Keep plowshare-modules out of Debian releases

[Carl Suster]

It probably shouldn't have been in stretch, but as long as it does not
cause trouble, you can let it rot there :-)


Agreed that it shouldn't have been released in stretch; at the time I 
had the idea of supporting it through backports. Given the relatively 
low popcon statistics and activity in bts, I think I prefer to just 
leave the package in stretch alone for now. If anyone is caught out by 
the situation later I can proceed with the patching and removing as 
outline above.


Carl

Bug#906128: libykpiv1 impacted by CVE-2018-14779 and CVE-2018-14780

[Nicolas Braud-Santoni]

Hi Salvatore,

On Tue, Aug 14, 2018 at 09:55:39PM +0200, Salvatore Bonaccorso wrote:
> On Tue, Aug 14, 2018 at 08:36:10PM +0200, Nicolas Braud-Santoni wrote:
> > Hi,
> > 
> > Gunnar Wolf sponsored the upload to sid (thanks!) and I just prepared an
> > upload for stretch-security.  It is available in the branch debian/stretch 
> > on:
> > 
> >   https://salsa.debian.org/auth-team/yubico-piv-tool.git
> > 
> > If the security team finds it suitable, please upload directly.
> 
> The issue does not warrant a DSA (was marked no-dsa in the tracker
> already). Can you though propose a fix to be included in the next
> stretch point release?

Yes, jcristau pointed out on IRC that there was a race condition between my mail
and the update of the security-tracker; I updated the changelog for an upload
to stretch-p-u, and jcc@ said he will look at it tomorrow.

Thanks for the swift reply  :)


Best,

  nicoo


signature.asc
Description: PGP signature

Bug#906147: python-smoke-zephyr ftbfs (failing tests)

[Matthias Klose]

Package: src:python-smoke-zephyr
Version: 1.2.0-1
Severity: serious
Tags: sid buster

python-smoke-zephyr ftbfs (failing tests). Please also make it clear which
Python version is used during the tests.


   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:217: cd
/<>/.pybuild/cpython2_2.7_smoke-zephyr/build; python2.7 -m unittest
discover -v -s /<>/tests -p "[a-z]*.py"
test_job_add (job.JobManagerTests) ... ok
test_job_delete (job.JobManagerTests) ... ok
test_job_disable (job.JobManagerTests) ... ok
test_job_init (job.JobManagerTests) ... ok
test_job_request_delete (job.JobManagerTests) ... ok
test_job_run (job.JobManagerTests) ... ok
test_cache (utilities.UtilitiesCacheTests) ... ok
test_cache_cache_clear (utilities.UtilitiesCacheTests) ... ok
test_cache_flatten_args (utilities.UtilitiesCacheTests) ... ok
test_attribute_dict (utilities.UtilitiesTests) ... ok
test_escape_single_quote (utilities.UtilitiesTests) ... ok
test_is_valid_email_address (utilities.UtilitiesTests) ... ok
test_parse_case_camel_to_snake (utilities.UtilitiesTests) ... ok
test_parse_case_snake_to_camel (utilities.UtilitiesTests) ... ok
test_parse_server (utilities.UtilitiesTests) ... ok
test_parse_timespan (utilities.UtilitiesTests) ... ok
test_parse_to_slug (utilities.UtilitiesTests) ... ok
test_selection_collision (utilities.UtilitiesTests) ... ok
test_unescape_single_quote (utilities.UtilitiesTests) ... ok
test_bin_b64_type (argparse_types.ArgparseTypeTests) ... ok
test_bin_hex_type (argparse_types.ArgparseTypeTests) ... ok
test_dir_type (argparse_types.ArgparseTypeTests) ... ok
test_log_level_type (argparse_types.ArgparseTypeTests) ... ok
test_port_type (argparse_types.ArgparseTypeTests) ... ok
test_timespan_type (argparse_types.ArgparseTypeTests) ... ok

--
Ran 25 tests in 14.038s

OK
I: pybuild base:217: cd
/<>/.pybuild/cpython3_3.7_smoke-zephyr/build; python3.7 -m unittest
discover -v -s /<>/tests -p "[a-z]*.py"
test_bin_b64_type (argparse_types.ArgparseTypeTests) ... ok
test_bin_hex_type (argparse_types.ArgparseTypeTests) ... ok
test_dir_type (argparse_types.ArgparseTypeTests) ... ok
test_log_level_type (argparse_types.ArgparseTypeTests) ... ok
test_port_type (argparse_types.ArgparseTypeTests) ... ok
test_timespan_type (argparse_types.ArgparseTypeTests) ... ok
test_job_add (job.JobManagerTests) ... ok
test_job_delete (job.JobManagerTests) ... ok
test_job_disable (job.JobManagerTests) ... ok
test_job_init (job.JobManagerTests) ... ok
test_job_request_delete (job.JobManagerTests) ... FAIL
test_job_run (job.JobManagerTests) ... ok
test_cache (utilities.UtilitiesCacheTests) ...
/<>/.pybuild/cpython3_3.7_smoke-zephyr/build/smoke_zephyr/utilities.py:135:
DeprecationWarning: inspect.getargspec() is deprecated, use inspect.signature()
or inspect.getfullargspec()
  arg_spec = inspect.getargspec(target_function)  # pylint: disable=W1505
/<>/.pybuild/cpython3_3.7_smoke-zephyr/build/smoke_zephyr/utilities.py:144:
DeprecationWarning: Using or importing the ABCs from 'collections' instead of
from 'collections.abc' is deprecated, and in 3.8 it will stop working
  if not isinstance(args, collections.Hashable):
ok
test_cache_cache_clear (utilities.UtilitiesCacheTests) ... ok
test_cache_flatten_args (utilities.UtilitiesCacheTests) ... ok
test_attribute_dict (utilities.UtilitiesTests) ... ok
test_escape_single_quote (utilities.UtilitiesTests) ... ok
test_is_valid_email_address (utilities.UtilitiesTests) ... ok
test_parse_case_camel_to_snake (utilities.UtilitiesTests) ... ok
test_parse_case_snake_to_camel (utilities.UtilitiesTests) ... ok
test_parse_server (utilities.UtilitiesTests) ... ok
test_parse_timespan (utilities.UtilitiesTests) ... ok
test_parse_to_slug (utilities.UtilitiesTests) ... ok
test_selection_collision (utilities.UtilitiesTests) ... ok
test_unescape_single_quote (utilities.UtilitiesTests) ... ok

==
FAIL: test_job_request_delete (job.JobManagerTests)
--
Traceback (most recent call last):
  File "/<>/tests/job.py", line 97, in test_job_request_delete
self.assertFalse(self.jm.job_exists(jid))
AssertionError: True is not false

--
Ran 25 tests in 16.037s

FAILED (failures=1)
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.7_smoke-zephyr/build; python3.7 -m unittest
discover -v -s {dir}/tests -p "[a-z]*.py"
dh_auto_test: pybuild --test -i python{version} -p "3.7 3.6" returned exit code 
13

Bug#898520: u-boot-rockchip: firefly-rk3288 hangs on: Loading Environment from MMC

[Vagrant Cascadian]

On 2018-08-14, Vagrant Cascadian wrote:
>> Also just tried with v2018.09-rc2, same problem.

With some debugging in mmc enabled (#define DEBUG at the top of dw_mmc.c
mmc-uclass.c mmc.c rockchip_dw_mmc.c) and CONFIG_MMC_TRACE=y, it gives a
little more information:

U-Boot SPL 2018.09-rc2+dfsg-1~20180814~6 (Aug 14 2018 - 21:58:09 +)
Returning to boot ROM...
mmc_bind: alias ret=0, devnum=1


U-Boot 2018.09-rc2+dfsg-1~20180814~6 (Aug 14 2018 - 21:58:09 +)

Model: Firefly-RK3288
DRAM:  2 GiB
mmc_bind: alias ret=0, devnum=1
mmc_bind: alias ret=0, devnum=0
MMC:   dwmmc@ff0c: 1, dwmmc@ff0f: 0
Loading Environment from MMC... clock is disabled (0Hz)

Buswidth = 0, clock: 0


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#906138: [Pkg-auth-maintainers] Bug#906138: libykneomgr: out of bounds read/writes

[Salvatore Bonaccorso]

Hi Simon,

On Tue, Aug 14, 2018 at 10:35:26PM +0200, Simon Josefsson wrote:
> Yes, removing the package from testing seems reasonable to me.

Can you fill a separate bug to ftp.debian.org to request a removal from
unstable (and so buster/testing)? Having this RC bug will at least
though ensure it will be removed at some point from testing.

I just checked, there should be no conflict in doing so:

> $ dak rm --suite=sid -n -R libykneomgr
> Will remove the following packages from sid:
> 
> libykneomgr |  0.1.8-2.2 | source
> libykneomgr-dev |  0.1.8-2.2 | amd64, arm64, armel, armhf, hurd-i386, i386, 
> kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, ppc64el, s390x
> libykneomgr0 |  0.1.8-2.2 | amd64, arm64, armel, armhf, hurd-i386, i386, 
> kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, ppc64el, s390x
>   ykneomgr |  0.1.8-2.2 | amd64, arm64, armel, armhf, hurd-i386, i386, 
> kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, ppc64el, s390x
> 
> Maintainer: Debian Authentication Maintainers 
> 
> 
> --- Reason ---
> 
> --
> 
> Checking reverse dependencies...
> No dependency problem found.

Regards,
Salvatore

Bug#898520: u-boot-rockchip: firefly-rk3288 hangs on: Loading Environment from MMC

[Vagrant Cascadian]

On 2018-08-14, Vagrant Cascadian wrote:
> On 2018-06-05, Vagrant Cascadian wrote:
>> On 2018-05-21, Vagrant Cascadian wrote:
>>> On 2018-05-12, Vagrant Cascadian wrote:
 On 2018-05-12, Vagrant Cascadian wrote:
> Booting firefly-rk3288 seems to hang looking for environment:
>
>   U-Boot 2018.05+dfsg-1 (May 10 2018 - 20:24:57 +)
>   
>   Model: Firefly-RK3288
>   DRAM:  2 GiB
>   MMC:   dwmmc@ff0c: 1, dwmmc@ff0f: 0
>   Loading Environment from MMC...
>
> And just hangs there.
>>
>> Still happening with v2018.07-rc1, too.
>
> Also just tried with v2018.09-rc2, same problem.

Adding Philipp Tomsich to CC.

The not very detailed log of the Debian bug report is at:

  https://bugs.debian.org/898520

v2018.01 works, v2018.03 doesn't, the closest I got to bisecting the
issue:

>>> I tried to bisect this, and got:
>>>
>>> commit 04a2ea248f58b3b6216d0cd0a6b8698df8b14355
>>> Author: Jean-Jacques Hiblot 
>>> Date:   Thu Sep 21 16:30:08 2017 +0200
>>>
>>> mmc: disable UHS modes if Vcc cannot be switched on and off
>>>
>>>
>>> But it fails in a slightly different way:
>>>
>>>   U-Boot 2018.01-00026-g04a2ea248f (May 21 2018 - 21:46:18 +)
>>>
>>>   Model: Firefly-RK3288
>>>   DRAM:  2 GiB
>>>   MMC:   dwmmc@ff0c: 1, dwmmc@ff0f: 0
>>>
>>> And just hangs without the "Loading Environment from MMC..."
>>> part...
>>>
>>>
>>> It is not a trivial revert on top of 2018.05, so I haven't been able to
>>> do that simple test.

Any further suggestions would be appreciated.

Thanks!


live well,
  vagrant


signature.asc
Description: PGP signature

Processed: reassign 888573 to gnome-shell-extensions

[Debian Bug Tracking System]

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

> reassign 888573 gnome-shell-extensions
Bug #888573 [gnome-desktop] gnome-desktop: insertion & removal of USB thumb 
drive causes user to be logged out
Bug reassigned from package 'gnome-desktop' to 'gnome-shell-extensions'.
No longer marked as found in versions gnome3.
Ignoring request to alter fixed versions of bug #888573 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: closing 888573

[Debian Bug Tracking System]

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

> close 888573
Bug #888573 [gnome-shell-extensions] gnome-desktop: insertion & removal of USB 
thumb drive causes user to be logged out
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: notfound 888573 in gnome3

[Debian Bug Tracking System]

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

> notfound 888573 gnome3
Bug #888573 [gnome-shell-extensions] gnome-desktop: insertion & removal of USB 
thumb drive causes user to be logged out
There is no source info for the package 'gnome-shell-extensions' at version 
'gnome3' with architecture ''
Unable to make a source version for version 'gnome3'
Ignoring request to alter found versions of bug #888573 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#898520: u-boot-rockchip: firefly-rk3288 hangs on: Loading Environment from MMC

[Vagrant Cascadian]

On 2018-06-05, Vagrant Cascadian wrote:
> On 2018-05-21, Vagrant Cascadian wrote:
>> On 2018-05-12, Vagrant Cascadian wrote:
>>> On 2018-05-12, Vagrant Cascadian wrote:
 Booting firefly-rk3288 seems to hang looking for environment:

   U-Boot 2018.05+dfsg-1 (May 10 2018 - 20:24:57 +)
   
   Model: Firefly-RK3288
   DRAM:  2 GiB
   MMC:   dwmmc@ff0c: 1, dwmmc@ff0f: 0
   Loading Environment from MMC...

 And just hangs there.
>
> Still happening with v2018.07-rc1, too.

Also just tried with v2018.09-rc2, same problem.

live well,
  vagrant

>> I tried to bisect this, and got:
>>
>> commit 04a2ea248f58b3b6216d0cd0a6b8698df8b14355
>> Author: Jean-Jacques Hiblot 
>> Date:   Thu Sep 21 16:30:08 2017 +0200
>>
>> mmc: disable UHS modes if Vcc cannot be switched on and off
>>
>>
>> But it fails in a slightly different way:
>>
>>   U-Boot 2018.01-00026-g04a2ea248f (May 21 2018 - 21:46:18 +)
>>
>>   Model: Firefly-RK3288
>>   DRAM:  2 GiB
>>   MMC:   dwmmc@ff0c: 1, dwmmc@ff0f: 0
>>
>> And just hangs without the "Loading Environment from MMC..."
>> part...
>>
>>
>> It is not a trivial revert on top of 2018.05, so I haven't been able to
>> do that simple test.


signature.asc
Description: PGP signature

Bug#905146: marked as done (libpqxx-6.2: missing Breaks+Replaces: libpqxx6 (>= 6.2))

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 20:51:37 +
with message-id 
and subject line Bug#905146: fixed in libpqxx 6.2.4-4
has caused the Debian Bug report #905146,
regarding libpqxx-6.2: missing Breaks+Replaces: libpqxx6 (>= 6.2)
to be marked as done.

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

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


-- 
905146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpqxx-6.2
Version: 6.2.4-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
the previous version in sid,
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/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libpqxx-6.2.
  Preparing to unpack .../libpqxx-6.2_6.2.4-3_amd64.deb ...
  Unpacking libpqxx-6.2 (6.2.4-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libpqxx-6.2_6.2.4-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libpqxx-6.2.so', which is 
also in package libpqxx6 6.2.4-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libpqxx-6.2_6.2.4-3_amd64.deb


The suggested versioning "(>= 6.2)" is unusual, but intended,
since libpqxx-6.2 is co-installable with libpqxx6 (6.1.0-1) in testing.


cheers,

Andreas


libpqxx6=6.2.4-2_libpqxx-6.2=6.2.4-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libpqxx
Source-Version: 6.2.4-4

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

Debian distribution maintenance software
pp.
Marcin Kulisz  (supplier of updated libpqxx 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, 14 Aug 2018 20:50:39 +0100
Source: libpqxx
Binary: libpqxx-dev libpqxx-doc libpqxx-6.2
Architecture: source
Version: 6.2.4-4
Distribution: unstable
Urgency: medium
Maintainer: Marcin Kulisz 
Changed-By: Marcin Kulisz 
Description:
 libpqxx-6.2 - C++ library to connect to PostgreSQL
 libpqxx-dev - C++ library to connect to PostgreSQL (development files)
 libpqxx-doc - C++ library to connect to PostgreSQL (documentation)
Closes: 905146
Changes:
 libpqxx (6.2.4-4) unstable; urgency=medium
 .
   * Added Breaks+Replaces to fix upgrades from libpqxx6 to libpqxx-6.2
 (Closes: 905146)
Checksums-Sha1:
 1017503b4e4adfab314ec6a1d456c8466435bc7c 2128 libpqxx_6.2.4-4.dsc
 54151ffe94c37d182bab280365a27d61246511f9 682802 libpqxx_6.2.4.orig.tar.gz
 7d451d0f286795e7f2628574cece47f4046f311f 18464 libpqxx_6.2.4-4.debian.tar.xz
 40fb5406e895fd70dc283c07e85ac026c36cb3ef 6867 libpqxx_6.2.4-4_source.buildinfo
Checksums-Sha256:
 cde175bbaf76704e20e428d5114106f13afeb272c94e56a16b51d2bca3aabae5 2128 
libpqxx_6.2.4-4.dsc
 b2abc384a146edf5a32b65316eb80965a0f58ba0de2cd21bbb4bcb1b068d680f 682802 
libpqxx_6.2.4.orig.tar.gz
 1548565cb4eacc4d70eeefa57ca07e18d7df699c6b81ddd13025407e9973504b 18464 
libpqxx_6.2.4-4.debian.tar.xz
 4fcb18ad8c7d81d4e0eec926da3c6221a3ff42e8fa05f95f287c67c74aa8f4f8 6867 
libpqxx_6.2.4-4_source.buildinfo
Files:
 5d68949ae381a6afeefd2df29d149daa 2128 libs optional libpqxx_6.2.4-4.dsc
 c18cc2840e3651a9244d9d313c05165e 682802 libs optional libpqxx_6.2.4.orig.tar.gz
 d31d53fc3dd4919cc180eacb4760060e 18464 libs optional 
libpqxx_6.2.4-4.debian.tar.xz
 3d8f4b93fc288ae40dc37e13b8d2ed0f 6867 libs optional 
libpqxx_6.2.4-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEPfGk38cyRog4vPEhaGkw3VjDOLMFAltzOGQSHGRlYmlhbkBr
dWxpc3oubmV0AAoJEGhpMN1YwzizFiQQAKKrs6gOZoX1O0Nr3l5Xym/qeIerfGU2
hvuGBJIDu4fIkJqu/vAqLyT7yqsXkaO2kiY/vImmIWX3epoTSyDCYvZm58zu+u5X
GK5/lMjzcBajUrAFyDC3IqRq6N/4kKM9sepZj2gMpM+kDeaT46/Qaxp5Qisy/hqa
DsXIooW3pdCP52hRrJcgzaYwXFmAs8qnO/ejMRVhKBxVIVqr8+tKNMTp8XrdO67z
Yar7FlOZXMOvCNf9OsSbjInSDNu2UfdwSqXL6o9yTOFReZvZzls0WPPpDC+

Bug#906138: [Pkg-auth-maintainers] Bug#906138: libykneomgr: out of bounds read/writes

[Simon Josefsson]

Yes, removing the package from testing seems reasonable to me.

/Simon

> 14 aug. 2018 kl. 20:39 skrev Salvatore Bonaccorso :
> 
> Source: libykneomgr
> Version: 0.1.8-1
> Severity: grave
> Tags: security upstream
> 
> Hi
> 
> See https://www.x41-dsec.de/lab/advisories/x41-2018-004-libykneomgr/
> for details. Upstream will  not issue a patch for it as vendor does
> not support the library anymore.
> 
> Should we consider removing libykneomgr from Debian?
> 
> Regards,
> Salvatore
> 
> ___
> Pkg-auth-maintainers mailing list
> pkg-auth-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-auth-maintainers

Bug#878775: marked as done (remake FTBFS on s390x: test failure)

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 23:16:51 +0300
with message-id <20180814201651.GA28052@localhost>
and subject line Re: Bug#878775: remake FTBFS on s390x: test failure
has caused the Debian Bug report #878775,
regarding remake FTBFS on s390x: test failure
to be marked as done.

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

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


-- 
878775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: remake
Version: 4.1+dbg1.3~dfsg.1-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=remake&arch=s390x&ver=4.1%2Bdbg1.3~dfsg.1-1&stamp=1508104983&raw=0

...
make  check-local
make[3]: Entering directory '/<>/remake-4.1+dbg1.3~dfsg.1'
cd tests && perl -I . ./run_make_tests.pl -srcdir 
/<>/remake-4.1+dbg1.3~dfsg.1 -make ../make 
--
   Running tests for GNU make on Linux zandonai 4.9.0-4-s390x s390x
 GNU Make 4.1+dbg1.3
--

Finding tests...

features/archives ... N/A
features/comments ... ok (1 passed)
features/conditionals ... ok (4 passed)
features/default_names .. ok (3 passed)
features/double_colon ... 
Test timed out after 5 seconds
Error running /<>/remake-4.1+dbg1.3~dfsg.1/tests/../make (expected 0; 
got 14): /<>/remake-4.1+dbg1.3~dfsg.1/tests/../make -f 
work/features/double_colon.mk bar

Caught signal 14!
FAILED (10/11 passed)
features/echoing  ok (4 passed)
features/errors . ok (2 passed)
features/escape . ok (8 passed)
features/export . ok (12 passed)
features/include  ok (10 passed)
features/jobserver .. ok (2 passed)
features/load ... ok (5 passed)
features/loadapi  ok (3 passed)
features/mult_rules . ok (2 passed)
features/mult_targets ... ok (2 passed)
features/order_only . ok (10 passed)
features/output-sync  ok (14 passed)
features/override ... ok (4 passed)
features/parallelism  ok (9 passed)
features/patspecific_vars ... ok (10 passed)
features/patternrules ... ok (10 passed)
features/quoting  ok (1 passed)
features/recursion .. ok (2 passed)
features/reinvoke ... ok (5 passed)
features/rule_glob .. ok (3 passed)
features/se_explicit  ok (10 passed)
features/se_implicit  ok (11 passed)
features/se_statpat . ok (4 passed)
features/shell_assignment ... ok (4 passed)
features/statipattrules . ok (8 passed)
features/targetvars . ok (25 passed)
features/utf8 ... ok (1 passed)
features/varnesting . ok (2 passed)
features/vpath .. ok (2 passed)
features/vpath2 . ok (1 passed)
features/vpath3 . ok (1 passed)
features/vpathgpath . ok (1 passed)
features/vpathplus .. ok (4 passed)
functions/abspath ... ok (1 passed)
functions/addprefix . ok (1 passed)
functions/addsuffix . ok (2 passed)
functions/andor . ok (2 passed)
functions/basename .. ok (1 passed)
functions/call 

Bug#906112: closed by Niels Thykier (Bug#906112: fixed in libcdio-paranoia 10.2+0.94+2-4)

[Andreas Beckmann]

On 2018-08-14 21:27, Debian Bug Tracking System wrote:
>* Remove cd-paranoia package again; the binary is also provided by
>  libcdio-utils.  (Reopens: #889803, Closes: #906112)

Nope, it is no longer provided by libcdio-utils >= 0.92

This was an issue upgrading from stretch.


Andreas

Bug#906128: libykpiv1 impacted by CVE-2018-14779 and CVE-2018-14780

[Salvatore Bonaccorso]

Hi Nicolas,

On Tue, Aug 14, 2018 at 08:36:10PM +0200, Nicolas Braud-Santoni wrote:
> Hi,
> 
> Gunnar Wolf sponsored the upload to sid (thanks!) and I just prepared an
> upload for stretch-security.  It is available in the branch debian/stretch on:
> 
>   https://salsa.debian.org/auth-team/yubico-piv-tool.git
> 
> If the security team finds it suitable, please upload directly.

The issue does not warrant a DSA (was marked no-dsa in the tracker
already). Can you though propose a fix to be included in the next
stretch point release?

Regards,
Salvatore

Bug#906112: marked as done (cd-paranoia: missing Breaks+Replaces: libcdio-utils (<< 0.92))

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 19:24:07 +
with message-id 
and subject line Bug#906112: fixed in libcdio-paranoia 10.2+0.94+2-4
has caused the Debian Bug report #906112,
regarding cd-paranoia: missing Breaks+Replaces: libcdio-utils (<< 0.92)
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.)


-- 
906112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cd-paranoia
Version: 10.2+0.94+2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../cd-paranoia_10.2+0.94+2-3_amd64.deb ...
  Unpacking cd-paranoia (10.2+0.94+2-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/cd-paranoia_10.2+0.94+2-3_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/cd-paranoia', which is also in package 
libcdio-utils 0.83-4.3+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/cd-paranoia_10.2+0.94+2-3_amd64.deb


BTW, libcdio-utils still mentions cd-paranoia in its long description.


cheers,

Andreas


libcdio-utils=0.83-4.3+b1_cd-paranoia=10.2+0.94+2-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libcdio-paranoia
Source-Version: 10.2+0.94+2-4

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated libcdio-paranoia 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, 14 Aug 2018 18:58:20 +
Source: libcdio-paranoia
Binary: libcdio-cdda-dev libcdio-cdda2 libcdio-paranoia-dev libcdio-paranoia2
Architecture: source
Version: 10.2+0.94+2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Niels Thykier 
Description:
 libcdio-cdda-dev - library to read and control digital audio CDs (development 
files)
 libcdio-cdda2 - library to read and control digital audio CDs
 libcdio-paranoia-dev - library to read digital audio CDs with error correction 
(developm
 libcdio-paranoia2 - library to read digital audio CDs with error correction
Closes: 906112
Changes:
 libcdio-paranoia (10.2+0.94+2-4) unstable; urgency=medium
 .
   * QA upload.
   * Remove cd-paranoia package again; the binary is also provided by
 libcdio-utils.  (Reopens: #889803, Closes: #906112)
Checksums-Sha1:
 e1da2cda6f276b82cfad0cb842e1e3a022e8aa30 2167 
libcdio-paranoia_10.2+0.94+2-4.dsc
 706fb7f46f3ad8bf8e972e3e1c9f041e165a48a4 7948 
libcdio-paranoia_10.2+0.94+2-4.debian.tar.xz
 e3060f50a621a0ed78bd8c5ba98b515a3e39dc20 5634 
libcdio-paranoia_10.2+0.94+2-4_source.buildinfo
Checksums-Sha256:
 65c0b89f6919d6ce6306278d2c32f23bd4ab51a960d14474b624814dbdf9091e 2167 
libcdio-paranoia_10.2+0.94+2-4.dsc
 e27d5075f97016ee0aaf0b5c29c0573614c9e4d4db65d217650bab5fe6081934 7948 
libcdio-paranoia_10.2+0.94+2-4.debian.tar.xz
 678d4cb1295c18e42becdbdbffd1fce73018a82a2de0189a7d68a0e60177c13f 5634 
libcdio-paranoia_10.2+0.94+2-4_source.buildinfo
Files:
 47a2ca4261e840bbb27b0082d79a863a 2167 libs optional 
libcdio-paranoia_10.2+0.94+2-4.dsc
 3babfe96b3826c65a52614a4e7aaba53 7948 libs optional 
libcdio-paranoia_10.2+0.94+2-4.debian.tar.xz
 4cc916aa58341b89a3bd88dea25fd23a 5634 libs optional 
libcdio-paranoia_10.2+0.94+2-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEsxMaRR2/33ygW0GXBUu7n32AZEIFAltzKCUACgkQBUu7n32A
ZELTmQ/+MR3L1E1y4tnF6gJ1CXgmaKwlzPK+YysWvS12ksSMPJm8cv1eAml6ZWDj
dGwSBiVZQlQbYF4gKEHOqIvF06g3oCEr2R9I3SYtlOqygAkntWpbfsdN1LDbi

Processed: Re: Bug#897767: closed by Mo Zhou (Bug#897767: fixed in highwayhash 0~20180209-g14dedec-5)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #897767 [src:highwayhash] non-x86 symbols out of date
Severity set to 'serious' from 'normal'

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

Bug#903177: marked as done (libcdio-paranoia: FTBFS in buster/sid (dh_installdocs: Cannot find "README"))

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 18:50:00 +
with message-id <351920f8-7ab3-16b0-5f3f-939c6c212...@thykier.net>
and subject line Re: libcdio-paranoia: FTBFS in buster/sid (dh_installdocs: 
Cannot find "README")
has caused the Debian Bug report #903177,
regarding libcdio-paranoia: FTBFS in buster/sid (dh_installdocs: Cannot find 
"README")
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.)


-- 
903177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libcdio-paranoia
Version: 10.2+0.94+2-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh_testdir
dh_autoreconf
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:80: installing './compile'
configure.ac:28: installing './missing'
example/C++/Makefile.am: installing './depcomp'

[... snipped ...]

Making install in test
make[2]: Entering directory '/<>/libcdio-paranoia-10.2+0.94+2/test'
Making install in cdda_interface
make[3]: Entering directory 
'/<>/libcdio-paranoia-10.2+0.94+2/test/cdda_interface'
make[4]: Entering directory 
'/<>/libcdio-paranoia-10.2+0.94+2/test/cdda_interface'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory 
'/<>/libcdio-paranoia-10.2+0.94+2/test/cdda_interface'
make[3]: Leaving directory 
'/<>/libcdio-paranoia-10.2+0.94+2/test/cdda_interface'
Making install in data
make[3]: Entering directory 
'/<>/libcdio-paranoia-10.2+0.94+2/test/data'
make[4]: Entering directory 
'/<>/libcdio-paranoia-10.2+0.94+2/test/data'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory 
'/<>/libcdio-paranoia-10.2+0.94+2/test/data'
make[3]: Leaving directory 
'/<>/libcdio-paranoia-10.2+0.94+2/test/data'
make[3]: Entering directory '/<>/libcdio-paranoia-10.2+0.94+2/test'
make[4]: Entering directory '/<>/libcdio-paranoia-10.2+0.94+2/test'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/libcdio-paranoia-10.2+0.94+2/test'
make[3]: Leaving directory '/<>/libcdio-paranoia-10.2+0.94+2/test'
make[2]: Leaving directory '/<>/libcdio-paranoia-10.2+0.94+2/test'
Making install in example
make[2]: Entering directory '/<>/libcdio-paranoia-10.2+0.94+2/example'
make[3]: Entering directory '/<>/libcdio-paranoia-10.2+0.94+2/example'
make[4]: Entering directory '/<>/libcdio-paranoia-10.2+0.94+2/example'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/libcdio-paranoia-10.2+0.94+2/example'
make[3]: Leaving directory '/<>/libcdio-paranoia-10.2+0.94+2/example'
make[2]: Leaving directory '/<>/libcdio-paranoia-10.2+0.94+2/example'
make[2]: Entering directory '/<>/libcdio-paranoia-10.2+0.94+2'
make[3]: Entering directory '/<>/libcdio-paranoia-10.2+0.94+2'
make[3]: Nothing to be done for 'install-exec-am'.
 /bin/mkdir -p 
'/<>/libcdio-paranoia-10.2+0.94+2/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
 /usr/bin/install -c -m 644 libcdio_paranoia.pc libcdio_cdda.pc 
'/<>/libcdio-paranoia-10.2+0.94+2/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
make[3]: Leaving directory '/<>/libcdio-paranoia-10.2+0.94+2'
make[2]: Leaving directory '/<>/libcdio-paranoia-10.2+0.94+2'
make[1]: Leaving directory '/<>/libcdio-paranoia-10.2+0.94+2'
dh_testdir
dh_testroot
dh_installchangelogs ChangeLog
dh_installdocs
dh_installdocs: Cannot find (any matches for) "README" (tried in .)

debian/rules:83: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder
but it also fails in reproducible builds:

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

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is

Bug#906128: libykpiv1 impacted by CVE-2018-14779 and CVE-2018-14780

[Nicolas Braud-Santoni]

Hi,

Gunnar Wolf sponsored the upload to sid (thanks!) and I just prepared an
upload for stretch-security.  It is available in the branch debian/stretch on:

  https://salsa.debian.org/auth-team/yubico-piv-tool.git

If the security team finds it suitable, please upload directly.


Best,

  nicoo

PS: In case I need to be reached swiftly, IRC might be the most effective medium
(nicoo on irc.oftc.net/#debian-security)

On Tue, Aug 14, 2018 at 06:39:43PM +0200, Nicolas Braud-Santoni wrote:
> Package: libykpiv1
> Severity: serious
> Tags: security pending stretch buster sid
> Justification: security
> 
> libykpiv1 versions below 1.6.0 are affected by a buffer overflow, exploitable 
> by
> malicious USB devices, that can lead to arbitrary code execution.
> 
> I will upload the fixed upstream version later today, and coordinate with
> the security team to get fixed in stretch and jessie-backports
> 
> 
> Best,
> 
>   nicoo
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: 
> LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: 
> LC_ALL set to en_US.UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages libykpiv1 depends on:
> ii  libc6 2.27-5
> ii  libpcsclite1  1.8.23-3
> ii  libssl1.1 1.1.0h-4
> 
> Versions of packages libykpiv1 recommends:
> ii  pcscd  1.8.23-3
> 
> libykpiv1 suggests no packages.
> 


signature.asc
Description: PGP signature

Bug#906138: libykneomgr: out of bounds read/writes

[Salvatore Bonaccorso]

Source: libykneomgr
Version: 0.1.8-1
Severity: grave
Tags: security upstream

Hi

See https://www.x41-dsec.de/lab/advisories/x41-2018-004-libykneomgr/
for details. Upstream will  not issue a patch for it as vendor does
not support the library anymore.

Should we consider removing libykneomgr from Debian?

Regards,
Salvatore

Bug#902594: marked as done (python3-setuptools-git should depend on python3-setuptools)

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 18:36:42 +
with message-id 
and subject line Bug#902594: fixed in python-setuptools-git 1.2-2
has caused the Debian Bug report #902594,
regarding python3-setuptools-git should depend on python3-setuptools
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.)


-- 
902594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-setuptools-git
Version: 1.1-1

The python3-setuptools-git package currently depends on the python-
setuptools package (i.e. the Python2 variant), not python3-setuptools.
This applies to all current Debian releases (jessie - sid).

# apt-cache show python3-setuptools-git
Package: python3-setuptools-git
Priority: optional
Section: python
Installed-Size: 29
Maintainer: Laszlo Boszormenyi (GCS) 
Architecture: all
Source: python-setuptools-git
Version: 1.1-1
Depends: python3:any (>= 3.3.2-2~), python-setuptools, git
Filename: pool/main/p/python-setuptools-git/python3-setuptools-git_1.1-
1_all.deb
Size: 10582
MD5sum: ceb090d47507b7c16ef5e500295b2823
SHA1: 6dbcd34fcc4fb47ea47d32bf9f145f7a74624d47
SHA256:
aef04c8130beca6853c3b6faafca627e8326438054f5f77f94990c5baf0c990a
SHA512:
e7d1acb4a0bbb071b8b826146dbf7ffb03893328af9f4fbb703946b6b1060a2702577ce
89bcf36f5a017e0320db83c6a1c8998e66d016ef8cf9c3a02a7225adc
Description: plugin for setuptools that enables git integration
Description-md5: 5fd071b89a9d204990c56242f591cc64
Homepage: https://github.com/wichert/setuptools-git

Thanks,
Marc Schmitzer


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: python-setuptools-git
Source-Version: 1.2-2

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

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

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated 
python-setuptools-git 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, 14 Aug 2018 16:18:48 +
Source: python-setuptools-git
Binary: python-setuptools-git python3-setuptools-git
Architecture: source all
Version: 1.2-2
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 python-setuptools-git - plugin for setuptools that enables git integration
 python3-setuptools-git - plugin for setuptools that enables git integration
Closes: 902594
Changes:
 python-setuptools-git (1.2-2) unstable; urgency=medium
 .
   * Correct python-setuptools dependency of Python 3 variant
 (closes: #902594).
   * Add python3-docutils and python3-pygments to build dependency for
 rst2man .
   * Update debhelper level to 11 .
   * Update Standards-Version to 4.1.5 .
Checksums-Sha1:
 60005d3d0ebc6a310b31c80cec7f2ef06ed5c911 2042 python-setuptools-git_1.2-2.dsc
 cb282ac5b32c76e9a74991f47155afb4e0ece84e 3364 
python-setuptools-git_1.2-2.debian.tar.xz
 bd47006c390c7924c13022cb47b29faf2b5d0256 13680 
python-setuptools-git_1.2-2_all.deb
 1c68f2c5bd40ddb65152c1932a64942fe3402506 8954 
python-setuptools-git_1.2-2_amd64.buildinfo
 d2662c236ca901655fa4d174fc8e318bb93180a9 13756 
python3-setuptools-git_1.2-2_all.deb
Checksums-Sha256:
 adae1f5205d8a827906d707cf7c814d2f0622cb08c673d7c807004db0fbbef86 2042 
python-setuptools-git_1.2-2.dsc
 432b35068f6dfca781fc2f57480d87d11a8288dc161b146e9b205d54f722be2d 3364 
python-setuptools-git_1.2-2.debian.tar.xz
 1e1617f710bcfb5f5d4f8249aeab9e047e75e702ef0f640c9de92ab0386f36d5 13680 
python-setuptools-git_1.2-2_all.deb
 dd3444a82f4fd899603197d7939be024bb9c534959961e16ede0d7f1db55d54e 8954 
python-setuptools-git_1.2-2_amd64.buildinfo
 b43f26f5a509bebc77f63a5acef0c1852ba959c7c37da4a20a682313ee4e2910 13756 
python3-setuptools-git_1.2-2_all.deb
Files:
 1edc6685a180111f7cd6a066da092ad7 2042 python optional 
python-setuptools-git_1.2-2.dsc
 b6ddd5af7e4544eb856030b6cacd43b0 3364 python optional 
python-setuptools-git_1.2-2.debian.tar.xz
 9c293c1c65a382e18b5041212466b87a 13680 python optional 
python-setuptools-git_1.2-2_

Processed: found 906131 in 0.4.1-1

[Debian Bug Tracking System]

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

> found 906131 0.4.1-1
Bug #906131 [btrfsmaintenance] CVE-2018-14722
Marked as found in versions btrfsmaintenance/0.4.1-1.
> thanks
Stopping processing here.

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

Processed: found 906128 in 1.4.2-2

[Debian Bug Tracking System]

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

> found 906128 1.4.2-2
Bug #906128 [libykpiv1] libykpiv1 impacted by CVE-2018-14779 and CVE-2018-14780
Marked as found in versions yubico-piv-tool/1.4.2-2.
> thanks
Stopping processing here.

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

Bug#891063:

[Chris Waters]

Vincent Lefevre  writes:

> But in any case, the bug needs to be fixed.

Yeah, I don't believe this can reasonably be called a bug. Emacs, like
a lot of big complex apps, can and does write to various parts of the
filesystem when used. There's a good chance that if you check your
home directory, you'll find more files owned by root. Files like
.emacs.d/recentf or .emacs.d/auto-save-list/* or .emacs-places.

At least, those are some of the files that Emacs has silently modified
recently on *my* system. It may depend on which emacs features you
have enabled, but that's something you shouldn't have to worry about.

Typing "su emacs [filename]" is simply not something you can
reasonably expect to do safely. Which is why emacs has features to
work around that. Like typing "emacs /su::[filename]" instead. Or
using "C-x C-f /su::[filename]" from within emacs. (Or, better yet,
"emacs /sudo::[filename]" or "C-x C-f /sudo::[filename]".)

If it *really* bothers you to type the pathname, you can make an alias
like: "eroot='emacs /sudo::$(pwd)/$1'". Or even "su -l emacs $(pwd)/$1".

However, turning off dbus access for emacs, which is something some of
us actually *use*, just to support a non-standard and unnecessary
workflow, is *not* a good option.

Bug#874421: marked as done (python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz)

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 17:44:00 +
with message-id <8d110c7a-0a99-5a17-c999-b7057b281...@thykier.net>
and subject line Re: Bug#874421: python3-cliapp: fails to upgrade from 
'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz
has caused the Debian Bug report #874421,
regarding python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite 
/usr/share/man/man5/cliapp.5.gz
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.)


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

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' 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#s-replaces

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

  Selecting previously unselected package python3-cliapp.
  Preparing to unpack .../python3-cliapp_1.20170827-1_all.deb ...
  Unpacking python3-cliapp (1.20170827-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-cliapp_1.20170827-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man5/cliapp.5.gz', which is also in 
package python-cliapp 1.20160724-2
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-cliapp_1.20170827-1_all.deb


cheers,

Andreas


python-cliapp=1.20160724-2_python3-cliapp=1.20170827-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source-Version: 1.20180812.1-1

On Sun, 12 Aug 2018 16:03:16 +0300 Lars Wirzenius  wrote:
> I've uploaded a version that should fix this.
> 
> [...]

This was closed in the 1.20180812.1-1 version:

> python-cliapp (1.20180812.1-1) unstable; urgency=medium
> 
>   * New upstream version.
>   * Add build-dep on dh-python.
> 
>  -- Lars Wirzenius   Sun, 12 Aug 2018 15:22:03 +0300
> 
> python-cliapp (1.20180812-1) unstable; urgency=medium
> 
>   * New upstream version.
>   * Add Breaks and Replaces on the python-cliapp version prior to
> buster to python3-cliapp, because the python3-cliapp package
> now has the cliapp(5) manpage. It used to be in python-cliapp.
> Having the manpage at all was probably a mistake, since it seems
> no-one in the history of the world has read it without being
> forced to. (Closes: #874421)
> 
>  -- Lars Wirzenius   Sun, 12 Aug 2018 10:22:12 +0300

Thanks,
~Niels--- End Message ---

Bug#906131: CVE-2018-14722

[Moritz Muehlenhoff]

Package: btrfsmaintenance
Severity: grave
Tags: security

Please see http://www.openwall.com/lists/oss-security/2018/08/14/7

Cheers,
Moritz

Bug#905183: marked as done (openstack-dashboard: dependency problems upgrading from stretch to buster)

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 17:04:07 +
with message-id 
and subject line Bug#905183: fixed in horizon 3:13.0.1-2
has caused the Debian Bug report #905183,
regarding openstack-dashboard: dependency problems upgrading from stretch to 
buster
to be marked as done.

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

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


-- 
905183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openstack-dashboard
Version: 3:13.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
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails.

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

  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) python3-django-horizon:amd64 < none -> 3:13.0.1-1 @un uN Ib 
>
  Broken python3-django-horizon:amd64 Conflicts on 
python-django-openstack-auth:amd64 < 2.4.1-2 -> 3.5.0-2 @ii umU >
Considering python-django-openstack-auth:amd64 0 as a solution to 
python3-django-horizon:amd64 0
Holding Back python3-django-horizon:amd64 rather than change 
python-django-openstack-auth:amd64
  Investigating (1) openstack-dashboard:amd64 < 3:10.0.1-1 -> 3:13.0.1-1 @ii 
umU Ib >
  Broken openstack-dashboard:amd64 Depends on python3-django-horizon:amd64 < 
none | 3:13.0.1-1 @un uH > (= 3:13.0.1-1)
Considering python3-django-horizon:amd64 0 as a solution to 
openstack-dashboard:amd64 0
Holding Back openstack-dashboard:amd64 rather than change 
python3-django-horizon:amd64
  Investigating (2) python-django:amd64 < 1:1.10.7-2+deb9u1 -> 1:1.11.14-1 @ii 
umU Ib >
  Broken python-django:amd64 Breaks on openstack-dashboard:amd64 < 3:10.0.1-1 | 
3:13.0.1-1 @ii umH > (< 3:12)
Considering openstack-dashboard:amd64 0 as a solution to 
python-django:amd64 11
Upgrading openstack-dashboard:amd64 due to Breaks field in 
python-django:amd64
  Investigating (2) openstack-dashboard:amd64 < 3:10.0.1-1 -> 3:13.0.1-1 @ii 
umU Ib >
  Broken openstack-dashboard:amd64 Depends on python3-django-horizon:amd64 < 
none | 3:13.0.1-1 @un uH > (= 3:13.0.1-1)
Considering python3-django-horizon:amd64 0 as a solution to 
openstack-dashboard:amd64 0
Holding Back openstack-dashboard:amd64 rather than change 
python3-django-horizon:amd64
  Investigating (3) python-django:amd64 < 1:1.10.7-2+deb9u1 -> 1:1.11.14-1 @ii 
umU Ib >
  Broken python-django:amd64 Breaks on openstack-dashboard:amd64 < 3:10.0.1-1 | 
3:13.0.1-1 @ii umH > (< 3:12)
Considering openstack-dashboard:amd64 0 as a solution to 
python-django:amd64 11
Upgrading openstack-dashboard:amd64 due to Breaks field in 
python-django:amd64
  Investigating (3) openstack-dashboard:amd64 < 3:10.0.1-1 -> 3:13.0.1-1 @ii 
umU Ib >
  Broken openstack-dashboard:amd64 Depends on python3-django-horizon:amd64 < 
none | 3:13.0.1-1 @un uH > (= 3:13.0.1-1)
Considering python3-django-horizon:amd64 0 as a solution to 
openstack-dashboard:amd64 0
Holding Back openstack-dashboard:amd64 rather than change 
python3-django-horizon:amd64
...
  Investigating (9) python-django:amd64 < 1:1.10.7-2+deb9u1 -> 1:1.11.14-1 @ii 
umU Ib >
  Broken python-django:amd64 Breaks on openstack-dashboard:amd64 < 3:10.0.1-1 | 
3:13.0.1-1 @ii umH > (< 3:12)
Considering openstack-dashboard:amd64 0 as a solution to 
python-django:amd64 11
Upgrading openstack-dashboard:amd64 due to Breaks field in 
python-django:amd64
  Investigating (9) openstack-dashboard:amd64 < 3:10.0.1-1 -> 3:13.0.1-1 @ii 
umU Ib >
  Broken openstack-dashboard:amd64 Depends on python3-django-horizon:amd64 < 
none | 3:13.0.1-1 @un uH > (= 3:13.0.1-1)
Considering python3-django-horizon:amd64 0 as a solution to 
openstack-dashboard:amd64 0
Holding Back openstack-dashboard:amd64 rather than change 
python3-django-horizon:amd64
  Done
  
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   fonts-roboto-fontface : Breaks: openstack-dashboard (< 3:12) but 3:10.0.1-1 
is to be installed
   python-django : Breaks: openstack-dashboard (< 3:12) but 3:10.0.1-1 is to be 
installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.


The problem seems to come from the conf

Processed: Bug #905183 in horizon marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #905183 [openstack-dashboard] openstack-dashboard: dependency problems 
upgrading from stretch to buster
Added tag(s) pending.

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

Bug#905183: Bug #905183 in horizon marked as pending

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #905183 in horizon 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/openstack-team/services/horizon/commit/c9ae91e3192a0084b99955f4e47da2993aa4270e


  * Add Conflicts: python-django-horizon to give hints to apt to ease upgrade
from Stretch as per Andreas Beckmann report (Closes: #905183).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/905183

Bug#906128: libykpiv1 impacted by CVE-2018-14779 and CVE-2018-14780

[Nicolas Braud-Santoni]

Package: libykpiv1
Severity: serious
Tags: security pending stretch buster sid
Justification: security

libykpiv1 versions below 1.6.0 are affected by a buffer overflow, exploitable by
malicious USB devices, that can lead to arbitrary code execution.

I will upload the fixed upstream version later today, and coordinate with
the security team to get fixed in stretch and jessie-backports


Best,

  nicoo

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

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

Versions of packages libykpiv1 depends on:
ii  libc6 2.27-5
ii  libpcsclite1  1.8.23-3
ii  libssl1.1 1.1.0h-4

Versions of packages libykpiv1 recommends:
ii  pcscd  1.8.23-3

libykpiv1 suggests no packages.

Processed: Re: xul-ext-noscript: new upstream version (WebExtensions)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #882287 [xul-ext-noscript] xul-ext-noscript: new upstream version 
(WebExtensions)
Severity set to 'grave' from 'wishlist'

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

Processed: Re: xul-ext-foxyproxy-standard: new upstream version (with WebExtensions support)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #881970 [xul-ext-foxyproxy-standard] xul-ext-foxyproxy-standard: new 
upstream version (with WebExtensions support)
Severity set to 'grave' from 'wishlist'

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

Bug#903206: marked as done (python-httpsig: FTBFS in sid (error: Could not find suitable distribution for Requirement.parse('six')))

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 16:21:32 +
with message-id 
and subject line Bug#903206: fixed in python-httpsig 1.2.0-2
has caused the Debian Bug report #903206,
regarding python-httpsig: FTBFS in sid (error: Could not find suitable 
distribution for Requirement.parse('six'))
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.)


-- 
903206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-httpsig
Version: 1.2.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python3 --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:217: python3.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3.7 setup.py build 
running build
running build_py

[... snipped ...]

writing top-level names to httpsig.egg-info/top_level.txt
writing manifest file 'httpsig.egg-info/SOURCES.txt'
reading manifest file 'httpsig.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'httpsig.egg-info/SOURCES.txt'
copying httpsig/tests/rsa_private.pem -> 
/<>/.pybuild/cpython3_3.7/build/httpsig/tests
copying httpsig/tests/rsa_public.pem -> 
/<>/.pybuild/cpython3_3.7/build/httpsig/tests
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython3_3.6/build/httpsig
copying httpsig/__init__.py -> 
/<>/.pybuild/cpython3_3.6/build/httpsig
copying httpsig/verify.py -> 
/<>/.pybuild/cpython3_3.6/build/httpsig
copying httpsig/sign.py -> /<>/.pybuild/cpython3_3.6/build/httpsig
copying httpsig/utils.py -> /<>/.pybuild/cpython3_3.6/build/httpsig
copying httpsig/requests_auth.py -> 
/<>/.pybuild/cpython3_3.6/build/httpsig
creating /<>/.pybuild/cpython3_3.6/build/httpsig/tests
copying httpsig/tests/test_utils.py -> 
/<>/.pybuild/cpython3_3.6/build/httpsig/tests
copying httpsig/tests/__init__.py -> 
/<>/.pybuild/cpython3_3.6/build/httpsig/tests
copying httpsig/tests/test_verify.py -> 
/<>/.pybuild/cpython3_3.6/build/httpsig/tests
copying httpsig/tests/test_signature.py -> 
/<>/.pybuild/cpython3_3.6/build/httpsig/tests
running egg_info
writing httpsig.egg-info/PKG-INFO
writing dependency_links to httpsig.egg-info/dependency_links.txt
writing requirements to httpsig.egg-info/requires.txt
writing top-level names to httpsig.egg-info/top_level.txt
reading manifest file 'httpsig.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'httpsig.egg-info/SOURCES.txt'
copying httpsig/tests/rsa_private.pem -> 
/<>/.pybuild/cpython3_3.6/build/httpsig/tests
copying httpsig/tests/rsa_public.pem -> 
/<>/.pybuild/cpython3_3.6/build/httpsig/tests
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py test 
running test
Searching for six

Note: Bypassing https://pypi.org/simple/six/ (disallowed host; see 
http://bit.ly/2hrImnY for details).

Couldn't find index page for 'six' (maybe misspelled?)
Scanning index of all packages (this may take a while)

Note: Bypassing https://pypi.org/simple/ (disallowed host; see 
http://bit.ly/2hrImnY for details).

No local packages or working download links found for six
error: Could not find suitable distribution for Requirement.parse('six')
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: 
python3.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p "3.7 3.6" returned exit code 
13
make: *** [debian/rules:4: build-indep] Error 13
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder
but it also fails in reproducible builds:

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: python-httpsig
Source-Version: 1.2.0-2

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

A summary of the changes between this version and the previous on

Processed: xul-ext-tabmixplus: add WebExtensions version

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #890804 [xul-ext-tabmixplus] xul-ext-tabmixplus: add WebExtensions version
Severity set to 'grave' from 'wishlist'

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

Bug#905708: marked as done (gcc-6: FTBFS with isl 0.20)

[Debian Bug Tracking System]

brary)
 libgnat-6-dbg - runtime for applications compiled with GNAT (debugging symbols)
 libgnatprj6 - GNU Ada compiler Project Manager (shared library)
 libgnatprj6-dbg - GNU Ada compiler Project Manager (debugging symbols)
 libgnatprj6-dev - GNU Ada compiler Project Manager (development files)
 libgnatvsn6 - GNU Ada compiler selected components (shared library)
 libgnatvsn6-dbg - GNU Ada compiler selected components (debugging symbols)
 libgnatvsn6-dev - GNU Ada compiler selected components (development files)
 libgo9 - Runtime library for GNU Go applications
 libgo9-dbg - Runtime library for GNU Go applications (debug symbols)
 libgphobos-6-dev - Phobos D standard library
 libgphobos68 - Phobos D standard library (runtime library)
 libgphobos68-dbg - Phobos D standard library (debug symbols)
 libmpx2- Intel memory protection extensions (runtime)
 libmpx2-dbg - Intel memory protection extensions (debug symbols)
 libn32gcc-6-dev - GCC support library (n32 development files)
 libn32gfortran-6-dev - Runtime library for GNU Fortran applications (n32 
development fil
 libn32gfortran3 - Runtime library for GNU Fortran applications (n32)
 libn32gfortran3-dbg - Runtime library for GNU Fortran applications (n32 debug 
symbols)
 libn32go9  - Runtime library for GNU Go applications (n32)
 libn32go9-dbg - Runtime library for GNU Go applications (n32 debug symbols)
 libn32objc-6-dev - Runtime library for GNU Objective-C applications (n32 
development
 libn32stdc++-6-dev - GNU Standard C++ Library v3 (development files)
 libn32stdc++6-6-dbg - GNU Standard C++ Library v3 (debugging files)
 libobjc-6-dev - Runtime library for GNU Objective-C applications (development 
fil
 libstdc++-6-dev - GNU Standard C++ Library v3 (development files)
 libstdc++-6-doc - GNU Standard C++ Library v3 (documentation files)
 libstdc++-6-pic - GNU Standard C++ Library v3 (shared library subset kit)
 libstdc++6-6-dbg - GNU Standard C++ Library v3 (debugging files)
 libx32asan3 - AddressSanitizer -- a fast memory error detector (x32)
 libx32asan3-dbg - AddressSanitizer -- a fast memory error detector (x32 debug 
symbo
 libx32gcc-6-dev - GCC support library (x32 development files)
 libx32gfortran-6-dev - Runtime library for GNU Fortran applications (x32 
development fil
 libx32gfortran3 - Runtime library for GNU Fortran applications (x32)
 libx32gfortran3-dbg - Runtime library for GNU Fortran applications (x32 debug 
symbols)
 libx32go9  - Runtime library for GNU Go applications (x32)
 libx32go9-dbg - Runtime library for GNU Go applications (x32 debug symbols)
 libx32gphobos-6-dev - Phobos D standard library (x32 development files)
 libx32gphobos68 - Phobos D standard library (runtime library)
 libx32gphobos68-dbg - Phobos D standard library (debug symbols)
 libx32objc-6-dev - Runtime library for GNU Objective-C applications (x32 
development
 libx32stdc++-6-dev - GNU Standard C++ Library v3 (development files)
 libx32stdc++6-6-dbg - GNU Standard C++ Library v3 (debugging files)
Closes: 905708 905714
Changes:
 gcc-6 (6.4.0-20) unstable; urgency=medium
 .
   * Update to SVN 20180814 (r263539) from the gcc-6-branch.
 - Fix PR libstdc++/83982, PR libstdc++/80893, PR libstdc++/80893,
   PR libstdc++/68519, PR libstdc++/86292, PR libstdc++/60555,
   PR libstdc++/86734, PR libstdc++/66145, PR libstdc++/85222,
   PR target/86197 (PPC).
 - Fix PR bootstrap/86724. Closes: #905708.
   * Backport r235876 from the trunk (PPC). LP: #1783252.
   * Add some basic autopkg tests for Ada, C, C++, Go, OpenMP and Fortran.
   * Update the src_libgo_Makefile.in patch (Svante Signell). Closes: #905714.
Checksums-Sha1:
 dc917da926dd9428fc1969ec6dd1c093026b6372 24192 gcc-6_6.4.0-20.dsc
 4217c316e760c31a647f73b9e4847c3a419b737d 1958337 gcc-6_6.4.0-20.diff.gz
 d7e7f74726f0c7c3c719b5d00655f8e84c93463e 10234 gcc-6_6.4.0-20_source.buildinfo
Checksums-Sha256:
 ec78e61298a65a937f1a48ee42214743fa54d3a4002a2267d9a5e65cb7dba9be 24192 
gcc-6_6.4.0-20.dsc
 952092aafe4ca753fa1df3c8fec4bcf6817d1f68003c8411b738823a170d0184 1958337 
gcc-6_6.4.0-20.diff.gz
 da5e93433dc9f16271d31d30aed1f60e41685d701ae1258b3386347c56f22b85 10234 
gcc-6_6.4.0-20_source.buildinfo
Files:
 2c17f7805d35e1ec1de77f9bb58cf809 24192 devel optional gcc-6_6.4.0-20.dsc
 b1865ebf1b57d2b9c54807868ef670bf 1958337 devel optional gcc-6_6.4.0-20.diff.gz
 6433b598bb32bfead32b0638aa3b888b 10234 devel optional 
gcc-6_6.4.0-20_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlty+swQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9W0aD/wLBwbG6lY+EeebPrIgtcsHSFRJ4ik6weWd
0EPNBGhfb/YOby81i1CDbq1Ekft0bd+z1A0Qr8F0vD0TXtaVkCiUyYjlnWMRfJja
kj0GEMgNdRs9GaGMS9IHOVF5p5F/bIWDxdMxBnuMEK7wfJ5YHcGePHvBA23twFxp
Yknf5C9DU+uT+5xFN+ZL9STIoyroTxjGsDgxlf6iJkWFWTi8kmwUIyJlFL8tey1u
7+vxvUVNe4spGd1BdF/cxd9vjDJoioSizOHNFFeMNk3bsmBUMCmiJ/gllwwutdNF
fgE2c76mF+D63/1ABWvOU4NAiR7QXPjLaC1goi1UO66nC3uK1pgtlHge1CUP/316
TkXdUyHsnu9cC42zzBqBknvHYwqrqyyjc5lWpqVDSqY6mTpkZk1avNSl77ds1PhR
ZAFdghB7febUl

Processed: Re: Bug#904506: pcre3: FTBFS on most architectures: more STL symbols disappear

[Debian Bug Tracking System]

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

> severity 904506 important
Bug #904506 [src:pcre3] pcre3: FTBFS on most architectures: more STL symbols 
disappear
Severity set to 'important' from 'serious'
> quit
Stopping processing here.

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

Bug#904506: pcre3: FTBFS on most architectures: more STL symbols disappear

[Matthew Vernon]

severity 904506 important
quit

So this has now built successfully (I think version skew between gcc :-/
), so I think the severity is now important. Probably still worth making
more symbols optional.

Regards,

Matthew

Processed: limit source to zapping, tagging 886188

[Debian Bug Tracking System]

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

> limit source zapping
Limiting to bugs with field 'source' containing at least one of 'zapping'
Limit currently set to 'source':'zapping'

> tags 886188 + pending
Bug #886188 [src:zapping] zapping: Depends on gconf
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#903533: yapf FTBFS with Python 3.7 as supported version

[Ana C. Custura]

Ah, I missed this - thank you.

Ana

On Tue, Aug 14, 2018, at 3:05 PM, Matthias Klose wrote:
>* debian/rules:
>- prevents some Python3 tests from running (Closes: #903533)
> 
> this doesn't address the failures in the autopkg tests.

Bug#903801: marked as done (python-pika,python-pika-doc: both ship /usr/share/doc/python-pika/README.rst)

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 14:51:30 +
with message-id 
and subject line Bug#903801: fixed in python-pika 0.11.0-4
has caused the Debian Bug report #903801,
regarding python-pika,python-pika-doc: both ship 
/usr/share/doc/python-pika/README.rst
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.)


-- 
903801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pika,python-pika-doc
Version: 0.11.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

This is probably caused by a behavioral change of dh_installdocs in
debhelper compat level 11.

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

  Selecting previously unselected package python-pika-doc.
  Preparing to unpack .../python-pika-doc_0.11.0-2_all.deb ...
  Unpacking python-pika-doc (0.11.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-pika-doc_0.11.0-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/python-pika/README.rst', which is also 
in package python-pika 0.11.0-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python-pika-doc_0.11.0-2_all.deb

cheers,

Andreas


python-pika=0.11.0-2_python-pika-doc=0.11.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-pika
Source-Version: 0.11.0-4

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-pika 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, 14 Aug 2018 14:02:28 +
Source: python-pika
Binary: python-pika python-pika-doc python3-pika
Architecture: source all
Version: 0.11.0-4
Distribution: unstable
Urgency: medium
Maintainer: Jan Dittberner 
Changed-By: Thomas Goirand 
Description:
 python-pika - AMQP client library for Python 2
 python-pika-doc - AMQP client library documentation
 python3-pika - AMQP client library for Python 3
Closes: 903801
Changes:
 python-pika (0.11.0-4) unstable; urgency=medium
 .
   * Team upload.
   * Add breaks+replaces python-pika (<< 0.11.0-3~). (Closes: #903801)
Checksums-Sha1:
 55fe26c85a1dbc58021cfff0b94bf3643c6f11ae 2390 python-pika_0.11.0-4.dsc
 a8d32d7475d719e904df2caa489dc8a3ad938579 4664 
python-pika_0.11.0-4.debian.tar.xz
 14ce69a4f46335c46578f155b639a53b09af3fcf 137768 
python-pika-doc_0.11.0-4_all.deb
 fdd189aefcbdf0eb6cc66e46aa44b511523b08af 94344 python-pika_0.11.0-4_all.deb
 87af21408709a54a67d515941ced84596765c58a 9691 
python-pika_0.11.0-4_amd64.buildinfo
 b9f0c34c40e9ed7f045fb4e89c8baff653514bad 94380 python3-pika_0.11.0-4_all.deb
Checksums-Sha256:
 d3be9a4616ed6e014827b265374e291b8cac221b320ca414c8d4ac70bd017666 2390 
python-pika_0.11.0-4.dsc
 bd41d2ecba7bc9ebf170344151612bb65df1c527f84cdc0698386585013ab600 4664 
python-pika_0.11.0-4.debian.tar.xz
 c314163f326c71642b5140e738c2589840e1df8533b3de9949f6e3cd838bd146 137768 
python-pika-doc_0.11.0-4_all.deb
 c2da1351caca29db1fdc42ab46b59ba8f8d3729e5c52b657145e66e431c97e2b 94344 
python-pika_0.11.0-4_all.deb
 4c434ef93d79ada608f695e009121db148d95bbb03a21787aad953890a9c37dc 9691 
python-pika_0.11.0-4_amd64.buildinfo
 5e79a78466c3e350996f1354dcfe5e746027e3c38ca320b602fa62fb20767a5a 94380 
python3-pika_0.11.0-4_all.deb
Files:
 e25ac7c8fe388c84e4852088b77ec95d 2390 python optional python-pika_0.11.0-4.dsc
 2981025d6d7f30eed40ee2adcade1055 4664 python optional 
python-pika_0.11.0-4.debian.tar.xz
 22948c1296f834b97da6b18c637a12c5 137768 doc optional 
python-pika-doc_0.11.0-4_all.deb
 3f94a7457d438742197fd43a7e57ec64 94344 python optional 
python-pika_0.11.0-4_all.deb
 eff6118fa42edde916eeefd4b7e1e08c 9691 python optional 
python-pika_0.11.0-4_amd64.buildinfo
 76c88b8f98f6d75a2322e9ab861ba2c8 94380 python optional 
python3-pika_0

Bug#905356: marked as done (python3-gnocchiclient: missing Depends: python3-distutils)

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 14:51:19 +
with message-id 
and subject line Bug#905356: fixed in python-gnocchiclient 7.0.1-5
has caused the Debian Bug report #905356,
regarding python3-gnocchiclient: missing Depends: python3-distutils
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.)


-- 
905356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-gnocchiclient
Version: 7.0.1-4
Severity: serious

$ python3-gnocchi
Traceback (most recent call last):
  File "/usr/bin/python3-gnocchi", line 6, in 
from gnocchiclient.shell import main
  File "/usr/lib/python3/dist-packages/gnocchiclient/shell.py", line 36, in 

from gnocchiclient.v1 import resource_cli
  File "/usr/lib/python3/dist-packages/gnocchiclient/v1/resource_cli.py", line 
14, in 
import distutils.util
ModuleNotFoundError: No module named 'distutils.util'


Andreas
--- End Message ---
--- Begin Message ---
Source: python-gnocchiclient
Source-Version: 7.0.1-5

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-gnocchiclient 
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, 14 Aug 2018 14:14:00 +
Source: python-gnocchiclient
Binary: python-gnocchiclient python-gnocchiclient-doc python3-gnocchiclient
Architecture: source all
Version: 7.0.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-gnocchiclient - bindings to the OpenStack Gnocchi API - Python 2.7
 python-gnocchiclient-doc - bindings to the OpenStack Gnocchi API - doc
 python3-gnocchiclient - bindings to the OpenStack Gnocchi API - Python 3.x
Closes: 905356
Changes:
 python-gnocchiclient (7.0.1-5) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Use team+openst...@tracker.debian.org as maintainer
 .
   [ Thomas Goirand ]
   * Add (build-)depends on python3-distutils (Closes: #905356).
Checksums-Sha1:
 541bc24340a352922100db72842beddace49fa0f 3209 python-gnocchiclient_7.0.1-5.dsc
 f4c21e1523497f5209f64402024303f47998c32e 4176 
python-gnocchiclient_7.0.1-5.debian.tar.xz
 117e568907ca5a2252e6d488914caa6b0966c603 140072 
python-gnocchiclient-doc_7.0.1-5_all.deb
 140fa9927f4e645c46cfe920e70375c711c2a1f8 31708 
python-gnocchiclient_7.0.1-5_all.deb
 3c0dce3592c2daece2f9c262513e67d6c5958004 17728 
python-gnocchiclient_7.0.1-5_amd64.buildinfo
 18eab776bef8ceb10a491becc060bcd20df07605 31780 
python3-gnocchiclient_7.0.1-5_all.deb
Checksums-Sha256:
 deff41db654fa5455858e40d56ca6354526fa35f7bdd651519c28b3ab47b7d55 3209 
python-gnocchiclient_7.0.1-5.dsc
 3cb948a6a69aa329aa44897bbb04c908bba3dc1a4f40d5327e5c3843f7a37c9e 4176 
python-gnocchiclient_7.0.1-5.debian.tar.xz
 e1af8e4a98b27c9ab1d2b3a26623618428a2bfe3864c03fd9c5867997786091d 140072 
python-gnocchiclient-doc_7.0.1-5_all.deb
 33b18eb3c43897686705c98cf16e16943b2dc20a7aba884f92e5c0862164fe1d 31708 
python-gnocchiclient_7.0.1-5_all.deb
 1dca8f1af4404a97fc3bed5418e5c57c76904985d68b4ffbd3e88570ed975d31 17728 
python-gnocchiclient_7.0.1-5_amd64.buildinfo
 a658474d92016b697e9ae05b682df0c9a5ee8be765829bcc3cc231adaa510a60 31780 
python3-gnocchiclient_7.0.1-5_all.deb
Files:
 d499ff53a61c71677b2e135a3776c1e7 3209 python optional 
python-gnocchiclient_7.0.1-5.dsc
 1cadafb19fe65febef2b2374e969f090 4176 python optional 
python-gnocchiclient_7.0.1-5.debian.tar.xz
 78910315e8a48622b8059471449de699 140072 doc optional 
python-gnocchiclient-doc_7.0.1-5_all.deb
 e9fc6dac860a59550cf541ae589b25e3 31708 python optional 
python-gnocchiclient_7.0.1-5_all.deb
 f7830e712586ae21b09bf92d6fb4e4fa 17728 python optional 
python-gnocchiclient_7.0.1-5_amd64.buildinfo
 ea2fcb9db504599c8d8d6f3c537d9180 31780 python optional 
python3-gnocchiclient_7.0.1-5_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtKCq/KhshgVdBnYUq1PlA1hod6YFAlty5NwACgkQq1PlA1ho
d6Z5kg//fXpcAQsTNtRM/cLeOQc/Q6eQvSBQu3jV6WfCH++ZuJ+2yB4jA8U8nKQ

Bug#905615: healpy: FTBFS with python 3.7

[Ole Streicher]

Control: tags -1 patch

The following patch fixes the FTBFS.

Cheers

Ole
>From 86111629ba3b99df2aacdc9dd4e777cc9ed9f76c Mon Sep 17 00:00:00 2001
From: Ole Streicher 
Date: Tue, 14 Aug 2018 16:36:03 +0200
Subject: [PATCH] Rebuild C++ files from Cython sources

This is required for Python 3.7 since the API changed a bit.

Closes: #905615
---
 debian/clean   | 3 +++
 debian/control | 2 ++
 2 files changed, 5 insertions(+)

diff --git a/debian/clean b/debian/clean
index fdc9787..c418c17 100644
--- a/debian/clean
+++ b/debian/clean
@@ -1 +1,4 @@
 matplotlibrc
+healpy/src/_pixelfunc.cpp
+healpy/src/_query_disc.cpp
+healpy/src/_sphtools.cpp
diff --git a/debian/control b/debian/control
index 79076e7..4b38474 100644
--- a/debian/control
+++ b/debian/control
@@ -5,6 +5,8 @@ Uploaders: Leo Singer 
 Homepage: http://healpy.readthedocs.org
 Section: python
 Build-Depends:
+ cython,
+ cython3,
  python-setuptools (>= 0.6.14),
  python-all-dev (>= 2.7),
  python-matplotlib,
-- 
2.18.0

Processed: Re: healpy: FTBFS with python 3.7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #905615 [src:healpy] healpy: FTBFS with python 3.7
Added tag(s) patch.

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

Processed: Bug #905356 in python-gnocchiclient marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #905356 [python3-gnocchiclient] python3-gnocchiclient: missing Depends: 
python3-distutils
Added tag(s) pending.

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

Bug#905356: Bug #905356 in python-gnocchiclient marked as pending

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #905356 in python-gnocchiclient 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/openstack-team/clients/python-gnocchiclient/commit/184f730e638f6663c0171b41675a34b5dc1ad195


Add (build-)depends on python3-distutils (Closes: #905356).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/905356

Bug#903801: Bug #903801 in python-pika marked as pending

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #903801 in python-pika 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-pika/commit/f9f9ed6772d6e67cd343305517c22bd3ba16df70


Add breaks+replaces python-pika (<< 0.11.0-3~). (Closes: #903801)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/903801

Processed: Bug #903801 in python-pika marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #903801 [python-pika,python-pika-doc] python-pika,python-pika-doc: both 
ship /usr/share/doc/python-pika/README.rst
Added tag(s) pending.

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

Processed: reopen 903533, autopkg tests not fixed

[Debian Bug Tracking System]

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

> reopen 903533
Bug #903533 {Done: Ana Custura } [src:yapf] yapf FTBFS 
with Python 3.7 as supported version
'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 yapf/0.22.0-2.
> thanks
Stopping processing here.

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

Processed: severity of 905444 is normal

[Debian Bug Tracking System]

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

> severity 905444 normal
Bug #905444 [ftp.debian.org] RM: cipux-rpc-client -- RoQA; dead upstream and 
unused
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#906116: marked as done (Jansson can not always parse QEMU's JSON)

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 13:49:18 +
with message-id 
and subject line Bug#906116: fixed in libvirt 4.6.0-2
has caused the Debian Bug report #906116,
regarding Jansson can not always parse QEMU's JSON
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.)


-- 
906116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libvirt
Version: 4.6.0-1
Severity: grave

Error looks somewhat like

   error: internal error: failed to parse JSON 1:59: too big integer near 
'18446744073709551615'

See https://bugzilla.redhat.com/show_bug.cgi?id=1614569
Cheers,
 -- Guido

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

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: libvirt
Source-Version: 4.6.0-2

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

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated libvirt 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, 14 Aug 2018 15:09:14 +0200
Source: libvirt
Binary: libvirt-clients libvirt-daemon libvirt-daemon-driver-storage-gluster 
libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-sheepdog 
libvirt-daemon-driver-storage-zfs libvirt-daemon-system libvirt0 libvirt-doc 
libvirt-dev libvirt-sanlock libnss-libvirt libvirt-wireshark
Architecture: source
Version: 4.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Libvirt Maintainers 

Changed-By: Guido Günther 
Description:
 libnss-libvirt - nss plugin providing IP address resolution for virtual 
machines
 libvirt-clients - Programs for the libvirt library
 libvirt-daemon - Virtualization daemon
 libvirt-daemon-driver-storage-gluster - Virtualization daemon glusterfs 
storage driver
 libvirt-daemon-driver-storage-rbd - Virtualization daemon RBD storage driver
 libvirt-daemon-driver-storage-sheepdog - Virtualization daemon Sheedog storage 
driver
 libvirt-daemon-driver-storage-zfs - Virtualization daemon ZFS storage driver
 libvirt-daemon-system - Libvirt daemon configuration files
 libvirt-dev - development files for the libvirt library
 libvirt-doc - documentation for the libvirt library
 libvirt-sanlock - Sanlock plugin for virtlockd
 libvirt-wireshark - Wireshark dissector for the libvirt protocol
 libvirt0   - library for interfacing with different virtualization systems
Closes: 905700 906116
Changes:
 libvirt (4.6.0-2) unstable; urgency=medium
 .
   * [c33faee] Drop dwarves dependency.
 Unmaintained and only used in the test suite. (Closes: #905700)
   * [43da5ad] Don't use jansson for JSON encoding.
 It has borken integer parsing. This adds new patches:
 Revert-m4-Introduce-STABLE_ORDERING_JANSSON.patch
 Revert-Remove-virJSONValueNewStringLen.patch
 Revert-build-undef-WITH_JANSSON-for-SETUID_RPC_CLIENT.patch
 Revert-tests-qemucapsprobe-Fix-output-after-switching-to-.patch
 Revert-build-require-Jansson-if-QEMU-driver-is-enabled.patch
 Revert-util-jsoncompat-Stub-out-virJSONInitialize-when-co.patch
 Revert-Switch-from-yajl-to-Jansson.patch
 Revert-remote-daemon-Make-sure-that-JSON-symbols-are-prop.patch
 Revert-build-remove-references-to-WITH_YAJL-for-SETUID_RP.patch
 Revert-build-add-with-jansson.patch
 Revert-Remove-functions-using-yajl.patch
 Revert-build-switch-with-qemu-default-from-yes-to-check.patch
 Revert-tests-also-skip-qemuagenttest-with-old-jansson.patch
 Revert-util-avoid-symbol-clash-bet

Bug#906119: Gratuitous sexual references

[Ian Jackson]

Package: weboob
Version: 1.3-1
Severity: serious

Hi.

As has been extensively discussed elsewhere (eg [1]), this package has
some unfortunate sexual references.  These problems include:
 * Command names which contain sexual references
 * Sexually suggestive icons etc.
There are, I suspect, other problems.  The sexualised content is both
gratuitous and unambiguous.

IMO this is in conflict with with Debian's values, in particular those
underlying the Diversity Statement.  gregor herrmann explained very
well why this is unacceptable here [0].  As you know, the matter has
been discussed with upstream.  It appears that upstream are,
unfortunately, not willing to change this. [2]

This situation is very unfortunate.  As I understand it the package
itself is very useful for some otherwise difficult situations.
However, IMO the problems are sufficiently serious that the package as
it is is not suitable for Debian, no matter how useful it is.

So, given that upstream have rejected requests for change, IMO the
available responses for the Debian project are to bowdlerise the
package (that is, to rename the commands, review the documentation,
change the icons, and so on), or to remove the package.

It seems to me from reading the thread on -devel that a substantial
majority of the Debian contributors there agree with that conclusion.
Accordingly I have marked this bug as "serious".


I think I need to make some points about the right process for
handling this disagreement:

Of course these postings to -devel may not represent a real view of
the project's consensus.  Mailing list traffic is not a particularly
good way of judging these matters.  A better guide is the Diversity
Statement GR, perhaps: although it is not directly on point, the
majority in favour was overwhelming.  Nevertheless there is probably
some room for differing assessments of the project's overall view.

While there is no requirement for a package maintainer to abide by the
project consensus, whether a package is suitable for the release is
ultimately a matter for the Release Team.  On a matter like this I
would expect the Release Team to follow what they see as the project's
rough consensus.

I had hoped that this matter could be brought to a satisfactory
resolution amicably.  However that does not now appear to be possible.
The discussion on -devel is becoming a distraction.  IMO we need to
bring it to a close.

I consider this matter important, and I am convinced that the project
consensus is with me.  Under the circumstances it would be quite wrong
to just drop it, and accept the unacceptable status quo.

So that is why I am filing this bug now.  If you as maintainer
disagree with my assessment, then we should refer the dispute about
the bug severity to the Release Team, in accordance with usual
practice.

For the avoidance of doubt: if the Release Team feel the project's
consensus is not sufficiently clear; or that a removal decision by the
Release Team would lack legitimacy, I would quite understand.
In that case the right next step would be a General Resolution.  If
necessary I will propose and/or sponsor a GR to definitively establish
Debian's view that this package is unacceptable.

With regret,
Ian.

[0] https://lists.debian.org/debian-devel/2018/07/msg00428.html
[1] https://lists.debian.org/debian-devel/2018/07/msg00263.html
[2] See for example:
  https://lists.debian.org/debian-devel/2018/07/msg00386.html

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Processed: Bug #906116 in libvirt marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #906116 [src:libvirt] Jansson can not always parse QEMU's JSON
Added tag(s) pending.

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

Bug#906116: Bug #906116 in libvirt marked as pending

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #906116 in libvirt 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/libvirt-team/libvirt/commit/43da5addedee0bfd2b62b3ea565c0f06c4c0d715


Don't use jansson for JSON encoding.

It has borken integer parsing

New patches:
Revert-m4-Introduce-STABLE_ORDERING_JANSSON.patch
Revert-Remove-virJSONValueNewStringLen.patch
Revert-build-undef-WITH_JANSSON-for-SETUID_RPC_CLIENT.patch
Revert-tests-qemucapsprobe-Fix-output-after-switching-to-.patch
Revert-build-require-Jansson-if-QEMU-driver-is-enabled.patch
Revert-util-jsoncompat-Stub-out-virJSONInitialize-when-co.patch
Revert-Switch-from-yajl-to-Jansson.patch
Revert-remote-daemon-Make-sure-that-JSON-symbols-are-prop.patch
Revert-build-remove-references-to-WITH_YAJL-for-SETUID_RP.patch
Revert-build-add-with-jansson.patch
Revert-Remove-functions-using-yajl.patch
Revert-build-switch-with-qemu-default-from-yes-to-check.patch
Revert-tests-also-skip-qemuagenttest-with-old-jansson.patch
Revert-util-avoid-symbol-clash-between-json-libraries.patch

Revert "Depend on libjansson4"

This reverts commit 42d718c778de95cb61431d0aa49cb9c055ecde7c.

Revert "Use jansson instead of yajl"

This reverts commit d53b4b1dc792673476d98b21e3aff284a875cabc.

Closes: #906116



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/906116

Bug#906110: freecad-{common,python2},libfreecad-python2-0.17: missing Breaks+Replaces: freecad (<< 0.17)

[Andreas Beckmann]

On 2018-08-14 12:43, Kurt Kremitzki wrote:
> Thanks for letting me know about this! I'll get at it right away.

Please also take a look at the FTBFS during the binary-arch builds:

https://buildd.debian.org/status/package.php?p=freecad&suite=experimental

--fail-missing chokes upon a few files that anre not needed
for the arch:any packages.


Andreas

Bug#906118: openmpi: some builds and autopkgtests time out on i386, armhf

[Graham Inggs]

Source: openmpi
Version: 3.1.1.real-6
Severity: serious

Hi Alastair

We noticed in Ubuntu, builds and autopkgtests of a couple of 
openmpi-related packages time out on i386 and armhf.  At least some of 
these have been successful with previous versions of libopenmpi3.


I have been able to reproduce some of the build failures in Debian 
[1][2][3].  Unfortunately, Debian do not run autopkgtests on i386, but 
in Ubuntu there are failed logs of esys-particle [4], liggghts [5], 
yorick [6].


Regards
Graham


[1] 
https://tests.reproducible-builds.org/debian/history/i386/med-fichier.html
[2] 
https://tests.reproducible-builds.org/debian/history/armhf/med-fichier.html

[3] https://tests.reproducible-builds.org/debian/history/armhf/slepc.html

[4] http://autopkgtest.ubuntu.com/packages/e/esys-particle/cosmic/i386
[5] http://autopkgtest.ubuntu.com/packages/l/liggghts/cosmic/i386
[6] http://autopkgtest.ubuntu.com/packages/y/yorick/cosmic/i386

Bug#906117: openjdk-7-jre-headless: FTBFS in Debian Experimental

[Boyuan Yang]

Package: openjdk-7-jre-headless
Version: 7u181-2.6.13-1
Severity: serious
X-Debbugs-CC: d...@debian.org

Dear Maintainer (Hi doko!),

TL;DR: openjdk-7 currently FTBFS in Debian experimental, please 
consider fixing it.

I fully understand that openjdk-7 will never enter Debian unstable / 
testing again but the last two builds in experimental all failed to 
build on every architectures. The leftover in experimental repository 
blocks the fix for Debian Bug #887858 [1] currently.

I have no idea if versions in experimental is needed to be able to 
push into oldstable repository. Now that oldstable has entered the 
LTS state, I assume that is not necessary anymore.

Could you please consider fixing the FTBFS or simply removing the 
unnecessary cruft from experimental repository?

Thanks!

--
Regards,
Boyuan Yang


[1] https://bugs.debian.org/887858

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

Bug#906116: Jansson can not always parse QEMU's JSON

[Guido Günther]

Source: libvirt
Version: 4.6.0-1
Severity: grave

Error looks somewhat like

   error: internal error: failed to parse JSON 1:59: too big integer near 
'18446744073709551615'

See https://bugzilla.redhat.com/show_bug.cgi?id=1614569
Cheers,
 -- Guido

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

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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)
LSM: AppArmor: enabled

Processed: Re: python3-websockets: fails to install with Python 3.7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #904650 [python3-websockets] python3-websockets: fails to install with 
Python 3.7
Added tag(s) patch.

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

Bug#904650: python3-websockets: fails to install with Python 3.7

[Matthias Klose]

Control: tags -1 + patch

updated package available at
https://launchpad.net/ubuntu/+source/python-websockets/6.0-0ubuntu1

Bug#893184: marked as done (artemis FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 12:19:08 +
with message-id 
and subject line Bug#893184: fixed in artemis 17.0.1+dfsg-1
has caused the Debian Bug report #893184,
regarding artemis FTBFS with openjdk-9
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.)


-- 
893184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: artemis
Version: 16.0.17+dfsg-3
Severity: serious

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

...
/usr/bin/make jar
make[2]: Entering directory '/build/1st/artemis-16.0.17+dfsg'
idlj -Icorba corba/types.idl
idlj -Icorba corba/nsdb.idl
idlj -Icorba corba/nsdb_write.idl
idlj -Icorba corba/seqdb.idl
CLASSPATH=/usr/share/java/biojava.jar:/usr/share/java/j2ssh-core.jar:/usr/share/java/ibatis.jar:/usr/share/java/log4j-1.2.jar:/usr/share/java/postgresql-jdbc3.jar:/usr/share/java/picard.jar:/usr/share/java/htsjdk.jar:/usr/share/java/commons-net.jar:/usr/share/java/commons-lang3.jar:/usr/share/java/batik-all.jar:/usr/share/java/batik-awt-util.jar:/usr/share/java/batik-dom.jar:/usr/share/java/batik-ext.jar:/usr/share/java/batik-svggen.jar:/usr/share/java/batik-util.jar:/usr/share/java/batik-xml.jar:/usr/share/EMBOSS/jemboss/lib/jemboss.jar:/build/1st/artemis-16.0.17+dfsg
 javac -source 1.5 -target 1.5   
uk/ac/sanger/artemis/MegaBlastComparisonData.java
warning: [options] bootstrap class path not set in conjunction with -source 1.5
error: Source option 1.5 is no longer supported. Use 1.6 or later.
error: Target option 1.5 is no longer supported. Use 1.6 or later.
make[2]: *** [Makefile:48: uk/ac/sanger/artemis/MegaBlastComparisonData.class] 
Error 2
--- End Message ---
--- Begin Message ---
Source: artemis
Source-Version: 17.0.1+dfsg-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated artemis 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, 14 Aug 2018 13:59:24 +0200
Source: artemis
Binary: artemis
Architecture: source
Version: 17.0.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 artemis- genome browser and annotation tool
Closes: 893184
Changes:
 artemis (17.0.1+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
 Closes: #893184
   * debhelper 11
   * Point Vcs fields to salsa.debian.org
   * Standards-Version: 4.2.0
   * Class FTPSeekableStream should not be excluded
   * Update patch that prevents copying of non-existing files
   * d/rules: Use dh_auto_build instead of $(MAKE)
   * All JAR files named lower case according to Java policy
   * d/watch: use xz compression
Checksums-Sha1:
 0672c686df102af61aa5580f4c74ce9cd2d7425b 2268 artemis_17.0.1+dfsg-1.dsc
 d0e5dd8b331ef8f11d79bd7a17d9c20f0c985243 53870400 
artemis_17.0.1+dfsg.orig.tar.xz
 14e508b45084d5abb24c1d774fc0f58034072f92 22904 
artemis_17.0.1+dfsg-1.debian.tar.xz
Checksums-Sha256:
 bc368e095623e1629e255cc743417f625311db60b2794f064dec0e479705b7e1 2268 
artemis_17.0.1+dfsg-1.dsc
 a958e93be8be4dee0a5fc5e4165aa92267e406f8655735b754b852aeb2a0716b 53870400 
artemis_17.0.1+dfsg.orig.tar.xz
 e37dc4d1a36fd2bdb06fd4d99ab79f9da09a5bd267ec4fd58089811332d46adc 22904 
artemis_17.0.1+dfsg-1.debian.tar.xz
Files:
 5585c252348d723411a52ed4535b2ecb 2268 science optional 
artemis_17.0.1+dfsg-1.dsc
 46eee23910e9015bddc171cc2862294e 53870400 science optional 
artemis_17.0.1+dfsg.orig.tar.xz
 849231a4d2186fc1aa07ead61de2008e 22904 science optional 
artemis_17.0.1+dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAltyxkcRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEVCg/9FWVzDfni42aHuVCsynxcVF2fmWXSISbR
EIjuCMmgDMUfab+j0FFDVYmpqvrLJ/rP/FHBLvkB5kN8pmnouehca4x9vViNlZ8P
ECUNMB3DU8SUop7jExKSwZoO3BQom2USVq3wEC0OV/hTh0SnxeDRwoB7FuxQovZD
ARry7hQ8U2qXih89K9ZJkhYBfOjDczRwmLa5pFq0GmQ2ZuE4nFoDjgrhjFa8jWPg
ylwpT/1Ga1BBj9L07ROlQ3HWnQ0RGW5lgWS

Bug#905539: marked as done (gcc-7 FTBFS with isl 0.20)

[Debian Bug Tracking System]

)
 libgomp-plugin-nvptx1 - GCC OpenMP v4.5 plugin for offloading to NVPTX
 libgomp1   - GCC OpenMP (GOMP) support library
 libgomp1-dbg - GCC OpenMP (GOMP) support library (debug symbols)
 libgphobos-7-dev - Phobos D standard library
 libgphobos71 - Phobos D standard library (runtime library)
 libgphobos71-dbg - Phobos D standard library (debug symbols)
 libhsail-rt-7-dev - HSAIL runtime library (development files)
 libn32gcc-7-dev - GCC support library (n32 development files)
 libn32gfortran-7-dev - Runtime library for GNU Fortran applications (n32 
development fil
 libn32gfortran4 - Runtime library for GNU Fortran applications (n32)
 libn32gfortran4-dbg - Runtime library for GNU Fortran applications (n32 debug 
symbols)
 libn32go11 - Runtime library for GNU Go applications (n32)
 libn32go11-dbg - Runtime library for GNU Go applications (n32 debug symbols)
 libn32gomp1 - GCC OpenMP (GOMP) support library (n32)
 libn32gomp1-dbg - GCC OpenMP (GOMP) support library (n32 debug symbols)
 libn32objc-7-dev - Runtime library for GNU Objective-C applications (n32 
development
 libn32stdc++-7-dev - GNU Standard C++ Library v3 (development files)
 libn32stdc++6-7-dbg - GNU Standard C++ Library v3 (debugging files)
 libobjc-7-dev - Runtime library for GNU Objective-C applications (development 
fil
 libstdc++-7-dev - GNU Standard C++ Library v3 (development files)
 libstdc++-7-doc - GNU Standard C++ Library v3 (documentation files)
 libstdc++-7-pic - GNU Standard C++ Library v3 (shared library subset kit)
 libstdc++6-7-dbg - GNU Standard C++ Library v3 (debugging files)
 libubsan0  - UBSan -- undefined behaviour sanitizer (runtime)
 libubsan0-dbg - UBSan -- undefined behaviour sanitizer (debug symbols)
 libx32asan4 - AddressSanitizer -- a fast memory error detector (x32)
 libx32asan4-dbg - AddressSanitizer -- a fast memory error detector (x32 debug 
symbo
 libx32cilkrts5 - Intel Cilk Plus language extensions (x32)
 libx32cilkrts5-dbg - Intel Cilk Plus language extensions (x32 debug symbols)
 libx32gcc-7-dev - GCC support library (x32 development files)
 libx32gfortran-7-dev - Runtime library for GNU Fortran applications (x32 
development fil
 libx32gfortran4 - Runtime library for GNU Fortran applications (x32)
 libx32gfortran4-dbg - Runtime library for GNU Fortran applications (x32 debug 
symbols)
 libx32go11 - Runtime library for GNU Go applications (x32)
 libx32go11-dbg - Runtime library for GNU Go applications (x32 debug symbols)
 libx32gphobos-7-dev - Phobos D standard library (x32 development files)
 libx32gphobos71 - Phobos D standard library (runtime library)
 libx32gphobos71-dbg - Phobos D standard library (debug symbols)
 libx32objc-7-dev - Runtime library for GNU Objective-C applications (x32 
development
 libx32stdc++-7-dev - GNU Standard C++ Library v3 (development files)
 libx32stdc++6-7-dbg - GNU Standard C++ Library v3 (debugging files)
 libx32ubsan0 - UBSan -- undefined behaviour sanitizer (x32)
 libx32ubsan0-dbg - UBSan -- undefined behaviour sanitizer (x32 debug symbols)
Closes: 905539
Changes:
 gcc-7 (7.3.0-28) unstable; urgency=medium
 .
   * Update to SVN 20180814 (r264534) from the gcc-7-branch.
 - Fix PR libstdc++/86138, PR libstdc++/85672, PR libstdc++/84654,
   PR libstdc++/80893, PR libstdc++/80893, PR libstdc++/68519,
   PR libstdc++/86292, PR libstdc++/60555, PR libstdc++/86861,
   PR libstdc++/86734, PR rtl-optimization/85645, PR rtl-optimization/85645,
   PR target/86197 (PPC), PR middle-end/86705, PR c++/86728.
 - Fix PR bootstrap/86724. Closes: #905539.
 .
   [ Matthias Klose ]
   * Add some basic autopkg tests for Ada, C, C++, Go, OpenMP and Fortran.
   * Build again using gnat-7.
 .
   [ Nicolas Boulenguez ]
   * gnat: Improve the ada-gcc-name patch.
Checksums-Sha1:
 d7e83f6c2bdf1a739f09eb22e8350ebdf41b4216 25652 gcc-7_7.3.0-28.dsc
 bc83d9c9b311bd85c3988ed47b7e64a92772e329 1160362 gcc-7_7.3.0-28.diff.gz
 443322d09798b81d739e3c3e03dc8e763cc13505 10300 gcc-7_7.3.0-28_source.buildinfo
Checksums-Sha256:
 9f842401af8be67b477bdfed00e6c939d40ea9e5a6d2ba9fc6202caed48dbb06 25652 
gcc-7_7.3.0-28.dsc
 9a0b439d19ac641d7c364dcc21d6eb3a3033aa1bf58ba86b7586b20c5855385d 1160362 
gcc-7_7.3.0-28.diff.gz
 93e3594540cdc858d9e265c5e67d8de0d17c98813f3fe479bbb4f7a51e068d5d 10300 
gcc-7_7.3.0-28_source.buildinfo
Files:
 da027018b1fccd298de6865a5b50e141 25652 devel optional gcc-7_7.3.0-28.dsc
 c735d4beb83bdd096106c75b0c83b049 1160362 devel optional gcc-7_7.3.0-28.diff.gz
 6aac684bd243271402792d7d8629e8b1 10300 devel optional 
gcc-7_7.3.0-28_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAltywhcQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9UTcD/0bMePyVm0UsbkrUpbF41NalNODfszO8j4J
yBBCHG2u6UUCeeyuPF0h4wX+U28GMN4Hba61lE/lGGUSRKnW9rZyHno2Kk9PTYkw
L2oKW8R4YDY2DrfQj8M9FAYzW5uYdV1VmUMlG9ZEhyja62eob1yGaaCZVfCUI/bI
kDlwP0ky/c63gdrjyAnHc8pZQVEIXClrWfbymNlHtFZ7WMPDCCu/S6noYuKBj93h
SvRa67+R0FpN5U7H0Pv3zBa2CaN+djuS6u0sqA009xdsa

Bug#905198: marked as done (python-ldap-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 12:05:03 +
with message-id 
and subject line Bug#905198: fixed in python-ldap 3.1.0-2
has caused the Debian Bug report #905198,
regarding python-ldap-dbg: unhandled symlink to directory conversion: 
/usr/share/doc/PACKAGE
to be marked as done.

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

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


-- 
905198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-ldap-dbg
Version: 3.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  stretch -> buster

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m38.4s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/python-ldap-dbg/changelog.Debian.amd64.gz (python-ldap-dbg) != 
/usr/share/doc/python-ldap/changelog.Debian.amd64.gz (python-ldap:amd64)
/usr/share/doc/python-ldap-dbg -> python-ldap
  /usr/share/doc/python-ldap-dbg/changelog.Debian.gz (python-ldap-dbg) != 
/usr/share/doc/python-ldap/changelog.Debian.gz (python-ldap:amd64)
/usr/share/doc/python-ldap-dbg -> python-ldap
  /usr/share/doc/python-ldap-dbg/changelog.gz (python-ldap-dbg) != 
/usr/share/doc/python-ldap/changelog.gz (python-ldap:amd64)
/usr/share/doc/python-ldap-dbg -> python-ldap
  /usr/share/doc/python-ldap-dbg/copyright (python-ldap-dbg) != 
/usr/share/doc/python-ldap/copyright (python-ldap:amd64)
/usr/share/doc/python-ldap-dbg -> python-ldap


cheers,

Andreas


python-ldap-dbg_3.1.0-1+b1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-ldap
Source-Version: 3.1.0-2

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

Debian distribution maintenance software
pp.
Pierre-Elliott Bécue  (supplier of updated python-ldap 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: Fri, 10 Aug 2018 22:58:26 +0200
Source: python-ldap
Binary: python-ldap python3-ldap python-ldap-dbg python3-ldap-dbg python-pyldap 
python3-pyldap
Architecture: source amd64
Version: 3.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Pierre-Elliott Bécue 
Description:
 python-ldap - LDAP interface module for Python
 python-ldap-dbg - LDAP interface module for Python (debug extension)
 python-pyldap - LDAP interface module for Python 2.7 - transition package
 python3-ldap - LDAP interface module for Python3
 python3-ldap-dbg - LDAP interface module for Python3 (debug extension)
 python3-pyldap - LDAP interface module for Python 3.x - transition

Bug#905382: marked as done (cgit: CVE-2018-14912: directory traversal vulnerability)

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 11:34:35 +
with message-id 
and subject line Bug#905382: fixed in cgit 1.1+git2.10.2-3.1
has caused the Debian Bug report #905382,
regarding cgit: CVE-2018-14912: directory traversal vulnerability
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.)


-- 
905382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cgit
Version: 1.1+git2.10.2-3
Severity: grave
Tags: patch security upstream

Hi,

The following vulnerability was published for cgit.

CVE-2018-14912[0]:
| cgit_clone_objects in CGit before 1.2.1 has a directory traversal
| vulnerability when `enable-http-clone=1` is not turned off, as
| demonstrated by a cgit/cgit.cgi/git/objects/?path=../ request.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-14912
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14912
[1] https://bugs.chromium.org/p/project-zero/issues/detail?id=1627
[2] https://lists.zx2c4.com/pipermail/cgit/2018-August/004176.html
[3] 
https://git.zx2c4.com/cgit/commit/?id=53efaf30b50f095cad8c160488c74bba3e3b2680

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: cgit
Source-Version: 1.1+git2.10.2-3.1

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 04 Aug 2018 12:27:48 +0200
Source: cgit
Binary: cgit
Architecture: source
Version: 1.1+git2.10.2-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Cgit Packaging Team 
Changed-By: Salvatore Bonaccorso 
Description:
 cgit   - hyperfast web frontend for git repositories written in C
Closes: 905382
Changes:
 cgit (1.1+git2.10.2-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * clone: fix directory traversal (CVE-2018-14912) (Closes: #905382)
Checksums-Sha1:
 4f859fedc6715dda0bb537006c71df17eb0b5987 2289 cgit_1.1+git2.10.2-3.1.dsc
 37d74a9266a995c4fc53bd78a5affdf8d214e174 6118627 cgit_1.1+git2.10.2.orig.tar.gz
 916bf4c72cd1f89ff3c6f74b2bb7e68ca2d1a9a7 11472 
cgit_1.1+git2.10.2-3.1.debian.tar.xz
 08d8be6cbfbdd7a14469cfc2ae84dbadd72d3208 6316 
cgit_1.1+git2.10.2-3.1_source.buildinfo
Checksums-Sha256:
 d59d1e04f36b9a2dd4d0e50aecf3ae3a2dd90567e2445097d8054c7a8ceb501d 2289 
cgit_1.1+git2.10.2-3.1.dsc
 ca271d2cd188bd8a1d9a103c3d5e889ac67169bd2b9b554fbdaa98cf76e8a2bb 6118627 
cgit_1.1+git2.10.2.orig.tar.gz
 2963cce53544303897b42944c2cad2462ca7ef8a313f59b37c006a0cfa345e64 11472 
cgit_1.1+git2.10.2-3.1.debian.tar.xz
 67cc72acb6b9d165d7e95107f697bc45e562a795527b9070301104ef947b1fb2 6316 
cgit_1.1+git2.10.2-3.1_source.buildinfo
Files:
 6ba726e2571ab4b71e8e0456173edf05 2289 net extra cgit_1.1+git2.10.2-3.1.dsc
 ed3b45ecf5b8bc4afe92ace523548b26 6118627 net extra 
cgit_1.1+git2.10.2.orig.tar.gz
 5fa39b44d688687d94354e37b99c4bdc 11472 net extra 
cgit_1.1+git2.10.2-3.1.debian.tar.xz
 c89205fb4031b1024e6147428918a5f8 6316 net extra 
cgit_1.1+git2.10.2-3.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAltlgrZfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E3ngP/0/5P+7cGLEhfN28Uz9mH3ClyKTKPn2l
/xt0cKsNpV2QpXaznk9aXhzrNLJsy23snomNnhkWg5yi6B4Nt42eUwxrh37WYrge
kdGIFqovdCAJGHAip0PLqPK5qxmLXtBTgNFDOasQ/RSaugZhzXa8p3Sns+cM12WA
GTfFdYdCujHm3Q4zRks3wYD3ollFjF8HJO7LYoG+ZFBw7SzAvIIlmRmTf+I5qMAQ
vZPaqquY+pMh337eTaWdReJ5k65cDoA5XVQTGN088HwtgXvS+fo/eioB+qh1SLn9
Mem6YS1q04Py87abr2j/Khc33RjCNrrpptW7BVnRp37syKtrzv+rSaAwWNCSmRH8
HpuNcNUezI4Z2BTEFWztw+x2r6h+hboq20OdLYlH95okILs87PK9pXDfT3Fxg5ky
TuFxICl1PTngPJp1XPu7DkHCm8MOncvFTxFMsARsRw91MtuoyKnjaZY4L2dT8Edm
8rEq8K8650q8KRu9ZAmojyBT8MQExybqVD5hAFiMv8kXTg+

Bug#901771: marked as done ([d-shlibs] Include override of libfribidi0-dev to libfribidi-dev)

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 11:34:41 +
with message-id 
and subject line Bug#901771: fixed in d-shlibs 0.82+nmu1
has caused the Debian Bug report #901771,
regarding [d-shlibs] Include override of libfribidi0-dev to libfribidi-dev
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.)


-- 
901771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901771
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: d-shlibs
Version: 0.82
Severity: normal
X-Debbugs-CC: debian-ri...@lists.debian.org
User: debian-ri...@lists.debian.org
Usertags: riscv64

As the title says. Package fontforge is FTBFS on riscv64 and is
requesting to be reported:


https://buildd.debian.org/status/fetch.php?pkg=fontforge&arch=riscv64&ver=1%3A20170731%7Edfsg-1&stamp=1525574665&raw=0

BTW, the failure is not related to riscv64. The other architectures do
not fail because they were built a long time ago, when libpango1.0-dev
did not depend on libfribidi-dev. Still marking with riscv64 usertag, so
that nobody will spend additional time on that.

Thanks, Gio.
-- 
Giovanni Mascellani 
Postdoc researcher - Université Libre de Bruxelles



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: d-shlibs
Source-Version: 0.82+nmu1

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated d-shlibs 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, 07 Aug 2018 11:01:54 +
Source: d-shlibs
Binary: d-shlibs
Architecture: source
Version: 0.82+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Niels Thykier 
Description:
 d-shlibs   - Debian shared library package building helper scripts
Closes: 897539 901771
Changes:
 d-shlibs (0.82+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Alexander Volkov ]
   * Make shellcheck build-dependency optional as it is a test-only
 build-dependency.  Furthermore, ensure that tests are not run
 under "DEB_BUILD_OPTIONS=nocheck".
 .
   [ Simon McVittie ]
   * Add quirk for libfribidi-dev.  (Closes: #901771)
   * Fix parsing of "--".
   * Fix shell-check warnings.  (Closes: #897539)
 .
   [ Niels Thykier ]
   * Set Rules-Requires-Root to no as d-shlibs do not need (fake)root
 for building .debs.
Checksums-Sha1:
 e429e05ef4948d15a6635c7dced3a4cf32cb70ba 1667 d-shlibs_0.82+nmu1.dsc
 53f5e429b8d60affb940f52c8685e4d19f9b87ca 24196 d-shlibs_0.82+nmu1.tar.xz
 96feb0e3afe65a078cadcf210cfe036ca263 5360 
d-shlibs_0.82+nmu1_source.buildinfo
Checksums-Sha256:
 9a57c9692a0f935c831c1827f33963f2706d0d13631fd7bbaf995534132acbb0 1667 
d-shlibs_0.82+nmu1.dsc
 0c54a8a90d78453bcb310af27e2d3d8257214dc098e2592fd2f2684dfa4d2718 24196 
d-shlibs_0.82+nmu1.tar.xz
 c2e90659ffb622367fca68a47a10a7c64508e2cde8b602cb2ce7808a81974b90 5360 
d-shlibs_0.82+nmu1_source.buildinfo
Files:
 735b8d58887b220246b39b3c9fd4ef6e 1667 utils optional d-shlibs_0.82+nmu1.dsc
 b5466905fd746e78a1b13137f82034ef 24196 utils optional d-shlibs_0.82+nmu1.tar.xz
 b196bba4c31e37328a5a543129ee209a 5360 utils optional 
d-shlibs_0.82+nmu1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEsxMaRR2/33ygW0GXBUu7n32AZEIFAltpfaQACgkQBUu7n32A
ZEI1nxAAnTDYMuvcy7K7RL5vq0WMH57SjCc7i4vVZHN0UoiVHmadecjVZ1f1++dp
DeXqnif5PuOuNlnvba7qMvqv66c4mvVcOGIHBzfBh+i1arUuDqNXUcWmIIjYpmso
hcA7vcZNkrf9fnby6F2tcDmyrj4V7mSlmw7jupFLSQSZRQ/gZ7y/Gf/iBwBh9Lio
xk+EapYzUTB4/cTYYzr7guQQj/zlG7v1mbMwCDp49UWlGJQN0gKIsqSDzjuf5rmO
M/3jxngDETavRKE6vCUGixV6Ik2cJsuJcdh60QTPf5ph0Xjivo2M2asEdr3C615e
EiuNnypaTqwnXsmPPuOGgE6ImwaIGG2unwyxwAiciPG1DMgKO/kTP0DIHRgPxTYZ
4KF9afzF/Tez3rcYW1kYaVLnv0jlVVH+bAWbQetVFc7WTJnFqHPxPZhnXJm8kUnZ
wFyT4IlW27R9U77+TDvJyrlSb5pdJKLi4swPThSg5L+8Tts9c5G9D2ZjUMdFaYrB
zt91g7hJh7tQPAHj/TNFrD8G5bOrazTpYy7PN+8zGA3nP8+Hz8bPvaFnbPcom/Az
+94Npv9A+KDgyDr7VFTPubPvmnY2o/yHsaroZmg1Iz6NurktUHThyQoouWFqlR56
J7wqNvRUKzc0J2UTrNrzxEzLZVwKdeyTpf2Cg0F18PdtEP7kf+c=
=HjH3
-END PGP SIGNATURE End Me

Bug#897539: marked as done (d-shlibs: FTBFS: shellcheck errors)

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 11:34:41 +
with message-id 
and subject line Bug#897539: fixed in d-shlibs 0.82+nmu1
has caused the Debian Bug report #897539,
regarding d-shlibs: FTBFS: shellcheck errors
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> bash -n d-shlibmove
> bash -n d-devlibdeps
> shellcheck d-shlibmove
> 
> In d-shlibmove line 243:
>   sed -i -e "/^.*\.la usr\/lib || true$/d" "$INSTALLFILE_DEVPKG"
>^-- SC1117: Backslash is literal in "\.". Prefer 
> explicit escaping: "\\.".
>^-- SC1117: Backslash is literal in "\/". 
> Prefer explicit escaping: "\\/".
> 
> 
> In d-shlibmove line 251:
>   sed -i -e "s/usr\/lib\( || true\)\?$/usr\/lib\/$DEB_HOST_MULTIARCH\1/" 
> "$execscript"
> ^-- SC1117: Backslash is literal in "\/". Prefer 
> explicit escaping: "\\/".
>  ^-- SC1117: Backslash is literal in "\(". Prefer 
> explicit escaping: "\\(".
>^-- SC1117: Backslash is literal in 
> "\)". Prefer explicit escaping: "\\)".
>  ^-- SC1117: Backslash is literal in 
> "\?". Prefer explicit escaping: "\\?".
> ^-- SC1117: Backslash is 
> literal in "\/". Prefer explicit escaping: "\\/".
>  ^-- SC1117: Backslash is 
> literal in "\/". Prefer explicit escaping: "\\/".
>   ^-- 
> SC1117: Backslash is literal in "\1". Prefer explicit escaping: "\\1".
> 
> 
> In d-shlibmove line 270:
> check_line "$PKGDEV" "Section: \(devel\|libdevel\)"
>^-- SC1117: Backslash is literal in "\(". 
> Prefer explicit escaping: "\\(".
>   ^-- SC1117: Backslash is literal in 
> "\|". Prefer explicit escaping: "\\|".
> ^-- SC1117: Backslash is 
> literal in "\)". Prefer explicit escaping: "\\)".
> 
> make[1]: *** [Makefile:10: check] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2018/05/02/d-shlibs_0.82_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated d-shlibs 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, 07 Aug 2018 11:01:54 +
Source: d-shlibs
Binary: d-shlibs
Architecture: source
Version: 0.82+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Niels Thykier 
Description:
 d-shlibs   - Debian shared library package building helper scripts
Closes: 897539 901771
Changes:
 d-shlibs (0.82+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Alexander Volkov ]
   * Make shellcheck build-dependency optional as it is a test-only
 build-dependency.  Furthermore, ensure that tests are not run
 under "DEB_BUILD_OPTIONS=nocheck".
 .
   [ Simon McVittie ]
   * Add quirk for libfribidi-dev.  (Closes: #901771)
   * F

Bug#902787: marked as done (h2database: Add support for JTS 1.15)

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 11:19:25 +
with message-id 
and subject line Bug#902787: fixed in h2database 1.4.197-1
has caused the Debian Bug report #902787,
regarding h2database: Add support for JTS 1.15
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.)


-- 
902787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: h2database
Version: 1.4.196-2
Severity: important
Tags: patch
User: debian-...@lists.debian.org
Usertags: jts-1.15

Dear Maintainer,

Your packages FTBFS with JTS 1.15 available in expermental.

The attached patch fixes the build failure.

To quote the MIGRATION documentation:

"
 JTS Upgrade Guide
 =

 The JTS Topology Suite has a long history, and in 2016/2017,
 [Vivid Solutions](http://www.vividsolutions.com/) brought the project
 to the LocationTech working group of the Eclipse Foundation.

 During that transition, the Java package names and Maven GAVs have
 changed.  For package names (typically used in imports), the change is
 reflected below:

 |   | **JTS 1.14.0 and before** | **JTS 1.15.0 and later**|
 |---|:--|:|
 | Maven GroupId | com.vividsolutions| org.locationtech.jts|
 | Package names | com.vividsolutions.jts.*  | org.locationtech.jts.*  |

 To upgrade a Maven project (or another build tool using Maven dependency
 management), one can do a find and replace on ```pom.xml``` files (or
 similiar build files).  In the source code, one could do a find and
 replace on the package names.  As a concrete example, one could use
 these two commands to handle most of the migration.

 ```
 git grep -l com.vividsolutions | grep pom.xml | xargs sed -i 
"s/com.vividsolutions/org.locationtech.jts/g"
 git grep -l com.vividsolutions | xargs sed -i 
"s/com.vividsolutions/org.locationtech/g"
 ```

 ## Using JTS with Maven

 To include JTS in a Maven project, add a dependency block like the following:

 ```xml
 
 org.locationtech.jts
 jts-core
 ${jts.version}
 
 ```

 Where ${jts.version} is the released version of JTS one chooses to use.
 See the [releases](https://github.com/locationtech/jts/releases) page
 for options.
"

https://salsa.debian.org/debian-gis-team/jts/blob/upstream/1.15.1+ds/MIGRATION.md

The severity of this issue will be raised when the jts package is moved
from experimental to unstable.

Please note that JTS is up for adoption (#884537), as it should be better
to maintain the package as part of the Java team where its reverse
dependencies are maintained as well.

Kind Regards,

Bas
diff -Nru h2database-1.4.196/debian/changelog 
h2database-1.4.196/debian/changelog
--- h2database-1.4.196/debian/changelog 2017-11-24 12:53:48.0 +0100
+++ h2database-1.4.196/debian/changelog 2018-06-30 21:59:29.0 +0200
@@ -1,3 +1,10 @@
+h2database (1.4.196-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch for JTS 1.15.
+
+ -- Bas Couwenberg   Sat, 30 Jun 2018 21:59:29 +0200
+
 h2database (1.4.196-2) unstable; urgency=medium
 
   * Fixed the build failure when maven-debian-helper is installed
diff -Nru h2database-1.4.196/debian/patches/01-use-jar-files-from-debian.patch 
h2database-1.4.196/debian/patches/01-use-jar-files-from-debian.patch
--- h2database-1.4.196/debian/patches/01-use-jar-files-from-debian.patch
2017-06-20 09:48:22.0 +0200
+++ h2database-1.4.196/debian/patches/01-use-jar-files-from-debian.patch
2018-06-30 21:59:29.0 +0200
@@ -6,7 +6,7 @@
 Last-Update: 2011-07-13
 --- a/src/tools/org/h2/build/Build.java
 +++ b/src/tools/org/h2/build/Build.java
-@@ -202,14 +202,13 @@
+@@ -202,14 +202,13 @@ public class Build extends BuildBase {
  switchSource(debugInfo);
  clean();
  mkdir("temp");
@@ -23,7 +23,7 @@
 +File.pathSeparator + "/usr/share/java/slf4j-api.jar" +
 +File.pathSeparator + "/usr/share/java/org.eclipse.osgi.jar" +
 +File.pathSeparator + "/usr/share/java/osgi.compendium.jar" +
-+File.pathSeparator + "/usr/share/java/jts.jar" +
++File.pathSeparator + "/usr/share/java/jts-core.jar" +
  File.pathSeparator + javaToolsJar;
  FileList files;
  if (clientOnly) {
diff -Nru h2database-1.4.196/debian/patches/jts-1.15.patch 
h2database-1.4.196/debian/patches/jts-1.15.patch
--- h2database-1.4.196/debian/patches/jts-1.15.patch1970-01-01 
01:00:00.0 +0100
+++ h2database-1

Bug#906003: Keep plowshare-modules out of Debian releases

[Andreas Beckmann]

On 2018-08-14 03:18, Carl Suster wrote:
> Does that sound reasonable? The alternative is just to leave the package
> in stretch alone and accept that it will degrade in functionality over
> time. Users are already able to use the plowmod script and ignore the
> plowshare-modules package there if they need more recent modules.

That would work. It's your call. Probably depends on the number of bugs
you get against the package in stable.

It probably shouldn't have been in stretch, but as long as it does not
cause trouble, you can let it rot there :-)


Andreas

Bug#903527: marked as done (python3-motor fails to install with Python 3.7 as suported version)

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 10:53:30 +
with message-id 
and subject line Bug#903527: fixed in python-motor 1.2.3-1.1
has caused the Debian Bug report #903527,
regarding python3-motor fails to install with Python 3.7 as suported version
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.)


-- 
903527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-motor
Version: 1.2.3-1
Severity: grave
Control: block 902788 by -1

Setting up python3-motor (1.2.3-1) ...
  File "/usr/lib/python3/dist-packages/motor/frameworks/asyncio/__init__.py", 
line 32
from asyncio import async as ensure_future
^
SyntaxError: invalid syntax

dpkg: error processing package python3-motor (--configure):
 installed python3-motor package post-installation script subprocess returned 
error exit status 1
--- End Message ---
--- Begin Message ---
Source: python-motor
Source-Version: 1.2.3-1.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated python-motor 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: Fri, 10 Aug 2018 23:31:48 +0300
Source: python-motor
Binary: python-motor python3-motor
Architecture: source
Version: 1.2.3-1.1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team 

Changed-By: Adrian Bunk 
Description:
 python-motor - full-featured, non-blocking MongoDB driver - Python 2.x
 python3-motor - full-featured, non-blocking MongoDB driver - Python 3.x
Closes: 903527
Changes:
 python-motor (1.2.3-1.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Add upstream fix for compatibility with Python 3.7.
 (Closes: #903527)
Checksums-Sha1:
 951ac8543f7dcb627c7092711842847e5e765fd6 2145 python-motor_1.2.3-1.1.dsc
 e678845b15bac0fc273f8b7c5a9baa2672e70c3a 3992 
python-motor_1.2.3-1.1.debian.tar.xz
Checksums-Sha256:
 2221b8da9e465933f714b1dffb6a581cfdc257538d868820133279701dfff871 2145 
python-motor_1.2.3-1.1.dsc
 af95cdd57d1f329f2937f4414ad9d037aa411f456a3ba7e2cc05a84d49ea4ffa 3992 
python-motor_1.2.3-1.1.debian.tar.xz
Files:
 3d7322c05422039f2554c761b02cb031 2145 python optional 
python-motor_1.2.3-1.1.dsc
 6ef5dd932e50393d8ddadda0aadf3d12 3992 python optional 
python-motor_1.2.3-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAltt9uIACgkQiNJCh6LY
mLEwxBAAy0a/KJQxPMDeLCg1s/AwuraSeseHv5IAutJpQVUwAWvJkxA90jNahEAe
4Z92VREMx72XLzcYo1Ug/G9CMlMOWtcUnXsDt4DwgxxLJsdHGPvJTdFG32HraGb4
0qUbJx1EjaOs1hetbgly7pFOVfFo51B6V2dk09X/VsZL3I5c8j1F8lw1Cq8njH34
2ngbfClc1dZZBYs4BWzIfiE4VGGALQtC4mQ2cgtufv4eQoI75E4MVBkUp49Ippue
4lYqpAAGrh6oVb0q7zHf0GH1gRZUoq3z0r0v3AcUfGczFcJw+CmY32y6JjA16QOR
Vegzdcz31ZaKx+a1BhF6L3ORjnbXnSmmKAksIc58yxsWiTrIfRP8ULa6/ZO/li4u
vJL+O28NF87QbcbVYA/KPn2fEdaOjivoyvg1/mAJ4b/YH1vzuun6nCFCiHk+DACX
dph85tL4qGECpwqFFlJi7zEL1Q94svTZ+8H80gcY8dAmdgHFDEbuOxAlYQRViOKl
ccuvcLknA7h2Wp3VVBNQLPvzJVRQdYClzvyY4Ds0FWD69oC3ZoRNlDpke07UfDAG
f6WvIASm+i9Ga/J8hTFJgsJw2N2tNGq73MGCZXXXkhGzdi7DUY3co3Zm9L41dpl4
332XAVjX1UxK7Fhak+ybPJ/Nbu0NL3StPZYno/t3gSgfWlVEo7A=
=xfQH
-END PGP SIGNATURE End Message ---

Bug#906112: cd-paranoia: missing Breaks+Replaces: libcdio-utils (<< 0.92)

[Andreas Beckmann]

Package: cd-paranoia
Version: 10.2+0.94+2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../cd-paranoia_10.2+0.94+2-3_amd64.deb ...
  Unpacking cd-paranoia (10.2+0.94+2-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/cd-paranoia_10.2+0.94+2-3_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/cd-paranoia', which is also in package 
libcdio-utils 0.83-4.3+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/cd-paranoia_10.2+0.94+2-3_amd64.deb


BTW, libcdio-utils still mentions cd-paranoia in its long description.


cheers,

Andreas


libcdio-utils=0.83-4.3+b1_cd-paranoia=10.2+0.94+2-3.log.gz
Description: application/gzip

Bug#906110: freecad-{common,python2},libfreecad-python2-0.17: missing Breaks+Replaces: freecad (<< 0.17)

[Kurt Kremitzki]

Hello Andreas,

On 08/14/2018 05:17 AM, Andreas Beckmann wrote:
> Package: freecad-common,freecad-python2,libfreecad-python2-0.17
> Version: 0.17+dfsg1-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/#overwriting-files-and-replacing-packages-replaces
> 
> From the attached log (scroll to the bottom...):
-snip-
> cheers,
> 
> Andreas
> 

Thanks for letting me know about this! I'll get at it right away.

Bug#904995: xserver-common: black screen with mouse on screen rotate.

[Michel Dänzer]

On 2018-08-14 11:34 AM, Simon Polack wrote:
> Package: xserver-common
> Version: 2:1.20.0-3
> Followup-For: Bug #904995
> 
> Dear Maintainer,
> 
> please upgrade to current upstream bugfix release 1.20.1. Thank you a
> lot.

It probably won't make a difference for this particular bug, though, as
it's an xf86-video-ati bug.


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer

Bug#899223: marked as done (sparkleshare: fails to start without any error message)

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 10:28:51 +
with message-id 
and subject line Bug#899223: fixed in sparkleshare 3.28-1
has caused the Debian Bug report #899223,
regarding sparkleshare: fails to start without any error message
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.)


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

After the recent update, sparkleshare fails to start without any kind of
useful error message on multiple machines.

First, it hits a mono bug that's triggered by the new libncurses, which
can either be worked around with «TERM=xterm sparkleshare start» or
patched by
https://github.com/mono/mono/commit/2c1f45f3791f274855e0f5fd2fb0af71c9a756f7
(thanks to Jo Shields for that link).

It then runs like:
$ TERM=dumb sparkleshare start
06.47.09 Environment | SparkleShare 2.0.1
06.47.09 Environment | Git LFS 
06.47.09 Environment | Git 2.17.0
06.47.09 Environment | GNOME (Unix 4.16.0.1)
06.47.09 Cmd |  | gvfs-set-attribute "/home/tfheen/SparkleShare" 
metadata::custom-icon-name org.sparkleshare.SparkleShare

and then just exits.  strace does not really shed any light on what's
going on.

I'm happy to help out with debugging this issue if you can't reproduce
it.

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

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

Versions of packages sparkleshare depends on:
ii  git 1:2.17.0-1
ii  gnome-icon-theme3.12.0-3
ii  gvfs1.36.1-1
ii  libappindicator3-0.1-cil12.10.0+git20151221-5
ii  libgdk3.0-cil   2.99.3-2+b1
ii  libgio3.0-cil   2.99.3-2+b1
ii  libglib3.0-cil  2.99.3-2+b1
ii  libgtk3.0-cil   2.99.3-2+b1
ii  libjs-jquery3.2.1-1
ii  libmono-corlib4.5-cil   4.6.2.7+dfsg-1
ii  libmono-posix4.0-cil4.6.2.7+dfsg-1
ii  libmono-system-core4.0-cil  4.6.2.7+dfsg-1
ii  libmono-system-xml4.0-cil   4.6.2.7+dfsg-1
ii  libmono-system4.0-cil   4.6.2.7+dfsg-1
ii  libnotify3.0-cil3.0.3-3
ii  libpango3.0-cil 2.99.3-2+b1
ii  libwebkit2-sharp-4.0-cil2.10.9+git20160917-1.1
ii  mono-runtime4.6.2.7+dfsg-1

Versions of packages sparkleshare recommends:
ii  python   2.7.15~rc1-1
ii  python-nautilus  1.1-6

sparkleshare suggests no packages.

-- no debconf information

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
--- End Message ---
--- Begin Message ---
Source: sparkleshare
Source-Version: 3.28-1

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

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

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated sparkleshare 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, 14 Aug 2018 12:01:10 +0200
Source: sparkleshare
Binary: sparkleshare
Architecture: source
Version: 3.28-1
Distribution: unstable
Urgency: medium
Maintainer: Debian CLI Applications Team 

Changed-By: Andrej Shadura 
Description:
 sparkleshare - distributed collaboration and sharing tool
Closes: 899223
Changes:
 sparkleshare (3.28-1) unstable; urgency=medium
 .
   [ Maxime “pep” Buquet ]
   * New upstream release.
   * Change buildsystem to meson.
   * Remove the start/stop patch that has never been upstreamed.
   * Patch meson.build to remove a post-install script.
   * Update debian/copyright.
 .
   [ Andrej Shadura ]
   * Install RELEASE_NOTES.txt as a changelog.
   * Depend on git-lfs (Closes: #899223).
   * Make sure appdate gets installed into /usr/share/metainfo only.
   * Fix permissions on shipped HTML f

Bug#903801: python-pika,python-pika-doc: both ship /usr/share/doc/python-pika/README.rst

[Andreas Beckmann]

Followup-For: Bug #903801
Control: found -1 0.11.0-3

Hi,

now you are still missing

  Package: python-pika-doc
  Breaks: python-pika (<< 0.11.0-3~)
  Replaces: python-pika (<< 0.11.0-3~)

since that file has moved to python-pika-doc.

  Preparing to unpack .../python-pika-doc_0.11.0-3_all.deb ...
  Unpacking python-pika-doc (0.11.0-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-pika-doc_0.11.0-3_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/python-pika/README.rst', which is also 
in package python-pika 0.11.0-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python-pika-doc_0.11.0-3_all.deb


Andreas

Processed: Re: python-pika,python-pika-doc: both ship /usr/share/doc/python-pika/README.rst

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.11.0-3
Bug #903801 {Done: Jan Dittberner } 
[python-pika,python-pika-doc] python-pika,python-pika-doc: both ship 
/usr/share/doc/python-pika/README.rst
Marked as found in versions python-pika/0.11.0-3; no longer marked as fixed in 
versions python-pika/0.11.0-3 and reopened.

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

Bug#878896: marked as done (liquidsoap: FTBFS with OCaml 4.05.0)

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 10:20:31 +
with message-id 
and subject line Bug#878896: fixed in liquidsoap 1.3.3-1
has caused the Debian Bug report #878896,
regarding liquidsoap: FTBFS with OCaml 4.05.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.)


-- 
878896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878896
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liquidsoap
Version: 1.1.1-7.2
Severity: serious
Tags: buster sid

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

...
OCAMLOPT -c stream/generator.mli
OCAMLOPT -c stream/generator.ml
OCAMLOPT -c stream/aFrame.mli
OCAMLOPT -c stream/aFrame.ml
OCAMLOPT -c decoder/decoder.mli
OCAMLOPT -c request.mli
OCAMLOPT -c source.mli
OCAMLOPT -c stream/vFrame.mli
OCAMLOPT -c stream/vFrame.ml
OCAMLOPT -c stream/mFrame.mli
OCAMLOPT -c stream/mFrame.ml
OCAMLOPT -c decoder/decoder.ml
File "decoder/decoder.ml", line 280, characters 10-14:
Error: Multiple definition of the extension constructor name Exit.
   Names must be unique in a given structure or signature.
../Makefile.rules:192: recipe for target 'decoder/decoder.cmx' failed
make[3]: *** [decoder/decoder.cmx] Error 2
--- End Message ---
--- Begin Message ---
Source: liquidsoap
Source-Version: 1.3.3-1

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

Debian distribution maintenance software
pp.
Kyle Robbertze  (supplier of updated liquidsoap 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, 06 Aug 2018 15:29:41 +0200
Source: liquidsoap
Binary: liquidsoap liquidsoap-mode
Architecture: source amd64 all
Version: 1.3.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Kyle Robbertze 
Description:
 liquidsoap - audio streaming language
 liquidsoap-mode - Emacs mode for editing Liquidsoap code
Closes: 721639 827218 841871 878896
Changes:
 liquidsoap (1.3.3-1) unstable; urgency=medium
 .
   * New upstream release (closes: #878896, #841871, LP: #378151)
   * Remove outdated note about MP3 encoding (closes: #721639)
   * Make copyright machine readable
   * Drop unmaintained liguidsoap binary package
   * Drop unsupported dynamic plugins for static ones
   * Bump compat to 10 (no change)
   * Bump standards version to 4.2.0 (fix user management)
   * Add user to audio group (closes: #827218)
   * Convert to use dh
   * Add new uploader
Checksums-Sha1:
 6e0d4003d028a32096e6dac61db7c4d17f35a556 3401 liquidsoap_1.3.3-1.dsc
 a190853e1a4654a71972408081722afd537cd4cb 704003 liquidsoap_1.3.3.orig.tar.bz2
 3322376d30b265b39b7a314fc022f637543d4e4e 10008 liquidsoap_1.3.3-1.debian.tar.xz
 cf915de0b8ff2287dc4a5ee66dfe4ad9f986b019 562820 
liquidsoap-dbgsym_1.3.3-1_amd64.deb
 1d5f19f84fcc2c380affd09e1e5a8899e211a4e4 28372 liquidsoap-mode_1.3.3-1_all.deb
 e8bde3565e745c7c626b48259738f60d57e8b6d0 23467 
liquidsoap_1.3.3-1_amd64.buildinfo
 0d101900818a6a8d71a8fb92746bd2d46972f77f 2654968 liquidsoap_1.3.3-1_amd64.deb
Checksums-Sha256:
 7148b6b8f76143dcefe7865e4f14c5f89c62c3b0d12eb25837a412c7f54f6567 3401 
liquidsoap_1.3.3-1.dsc
 f6d849e6f0dc03f8f9e88cc18b9436d17301226c793f6ab5f9174fd544d27498 704003 
liquidsoap_1.3.3.orig.tar.bz2
 f2f95c5ca9c4813eb8bcbaa725d3e7b66ece2e2a8c29c176a520447d5f41ba6d 10008 
liquidsoap_1.3.3-1.debian.tar.xz
 122ef25c5f52cd07dcdc09b861d3367a054137e638f457a0ae521892c7b02f9a 562820 
liquidsoap-dbgsym_1.3.3-1_amd64.deb
 a5fa05f6ddb3d639173605b027860f5014a5201d4441f7521ad0af12b2eeb5ff 28372 
liquidsoap-mode_1.3.3-1_all.deb
 10132939d76f485a66f4b462fee2d8016a589c312b839444298aedec5ff27784 23467 
liquidsoap_1.3.3-1_amd64.buildinfo
 f401250d8c7d51e3142e300ab24e24fa9d0081dd42f50bf3ddbe3df13eae21a0 2654968 
liquidsoap_1.3.3-1_amd64.deb
Files:
 31322da93657c7a2c8ea8291da7c7fae 3401 sound optional liquidsoap_1.3.3-1.dsc
 a0283885f3c41753a4ce29b4d69ce2e9 704003 sound optional 
liquidsoap_1.3.3.orig.tar.bz2
 3a3fc8b56f06d959c9a51dd8152f392b 10008 sound optional 
liquidsoap_1.3.3-1.debian.tar.xz
 f341b0bcba23aa27cd50c1f66196c5e4 562820 deb

Bug#842815: Help needed for change of build system to gradle of package libsis-jhdf5-java

[olivier sallou]

Le mar. 14 août 2018 à 11:32, Andreas Tille  a écrit :

> Hi,
>
> upstream of libsis-jhdf5-java[1] has switched to gradle in its new
> version that is compatible with HDF5 1.10.  I tried to adapt debian/rules
> from previous manual build to buildsystem=gradle but got:
>
> ...
> Parallel execution is an incubating feature.
> Evaluating root project 'libsis-jhdf5-java' using build file
> '/build/libsis-jhdf5-java-18.08~pre+git20180805.da55947+dfsg/build.gradle'.
> Compiling build file
> '/build/libsis-jhdf5-java-18.08~pre+git20180805.da55947+dfsg/build.gradle'
> using SubsetScriptTransformer.
> Compiling build file
> '/build/libsis-jhdf5-java-18.08~pre+git20180805.da55947+dfsg/build.gradle'
> using BuildScriptTransformer.
> Compiling script
> '/build/libsis-jhdf5-java-18.08~pre+git20180805.da55947+dfsg/javaproject.gradle'
> using SubsetScriptTransformer.
> Compiling script
> '/build/libsis-jhdf5-java-18.08~pre+git20180805.da55947+dfsg/repository.gradle'
> using SubsetScriptTransformer.
> Compiling script
> '/build/libsis-jhdf5-java-18.08~pre+git20180805.da55947+dfsg/repository.gradle'
> using BuildScriptTransformer.
> Creating new cache for metadata-2.23/module-versions, path
> /build/libsis-jhdf5-java-18.08~pre+git20180805.da55947+dfsg/.gradle/caches/modules-2/metadata-2.23/module-versions.bin,
> access org.gradle.cache.internal.DefaultCacheAccess@350dec85
>
> FAILURE: Build failed with an exception.
>
> * Where:
> Build file
> '/build/libsis-jhdf5-java-18.08~pre+git20180805.da55947+dfsg/build.gradle'
> line: 1
>
> * What went wrong:
> A problem occurred evaluating root project 'libsis-jhdf5-java'.
> > Could not resolve all dependencies for configuration 'classpath'.
>> Could not resolve cisd:cisd-ant-tasks:+.
>  Required by:
>  unspecified:unspecified:unspecified
>   > No cached version listing for cisd:cisd-ant-tasks:+ available for
> offline mode.
>
> * Try:
> Run with --debug option to get more log output.
>
> * Exception is:
> org.gradle.api.GradleScriptException: A problem occurred evaluating root
> project 'libsis-jhdf5-java'.
> at
> org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:92)
> ...
> at
> org.gradle.api.internal.artifacts.ivyservice.ivyresolve.DynamicVersionResolver.resolve(DynamicVersionResolver.java:67)
> ... 104 more
>
>
> BUILD FAILED
>
> Total time: 5.829 secs
> Received result Failure[value=org.gradle.initialization.ReportedException:
> org.gradle.internal.exceptions.LocationAwareException: Build file
> '/build/libsis-jhdf5-java-18.08~pre+git20180805.da55947+dfsg/build.
>  gradle' line: 1
> A problem occurred evaluating root project 'libsis-jhdf5-java'.] from
> daemon DaemonInfo{pid=26176, address=[01070135-56e1-461a-92ea-35d94d1e1ee5
> port:41021, addresses:[/0:0:0:0:0:0:0:1, /127.0.0.1]],
> state=Busy, lastBusy=1534230750655,
> context=DefaultDaemonContext[uid=37bdd18f-143d-4071-ab24-f17f8d67fb44,javaHome=/usr/lib/jvm/java-10-openjdk-amd64,daemonRegistryDir=/build/libsis-jhdf5-java-18.08~pre+
>
> git20180805.da55947+dfsg/.gradle/daemon,pid=26176,idleTimeout=12,daemonOpts=-XX:+HeapDumpOnOutOfMemoryError,-Xmx1024m,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]}
> (build   should be done).
>
>
>
> Since I had no idea how to fix this I simply tried to remove this
> dependency definition (ant is installed as Build-Dependency anyway) and
> thus I tried the following quilt patch:
>
>
> $ git diff
> diff --git a/debian/patches/fix_build_dir.patch
> b/debian/patches/fix_build_dir.patch
> index 1d652b2..163553c 100644
> --- a/debian/patches/fix_build_dir.patch
> +++ b/debian/patches/fix_build_dir.patch
> @@ -4,7 +4,7 @@ Description: Do not make wrong assumptions about directory
> name
>
>  --- a/javaproject.gradle
>  +++ b/javaproject.gradle
> -@@ -50,7 +50,7 @@ sourceSets {
> +@@ -50,13 +50,9 @@ sourceSets {
>   buildDir = 'targets/gradle'
>
>   buildscript {
> @@ -12,4 +12,10 @@ Description: Do not make wrong assumptions about
> directory name
>  +apply from: 'repository.gradle'
>
>   repositories repositoryConfig
> -
> +-
> +-dependencies {
> +-classpath 'cisd:cisd-ant-tasks:+'
> +-}
> + }
> +
> + repositories repositoryConfig
>
>
> This leads to:
>
>
> ...
> FAILURE: Build failed with an exception.
>
> * Where:
> Build file
> '/build/libsis-jhdf5-java-18.08~pre+git20180805.da55947+dfsg/build.gradle'
> line: 40
>
> * What went wrong:
> A problem occurred evaluating root project 'libsis-jhdf5-java'.
> > Could not resolve all dependencies for configuration ':runtime'.
>> Could not resolve cisd:cisd-args4j:+.
>  Required by:
>  project :
>   > No cached version listing for cisd:cisd-args4j:+ available for
> offline mode.
>> Could not resolve cisd:cisd-base:+.
>  Required by:
>  project :
>   > No cached version listing for cisd:cisd-base:+ available for
> offline mode.
>> Co

Bug#906110: freecad-{common,python2},libfreecad-python2-0.17: missing Breaks+Replaces: freecad (<< 0.17)

[Andreas Beckmann]

Package: freecad-common,freecad-python2,libfreecad-python2-0.17
Version: 0.17+dfsg1-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/#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../freecad-common_0.17+dfsg1-1_all.deb ...
  Unpacking freecad-common (0.17+dfsg1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/freecad-common_0.17+dfsg1-1_all.deb (--unpack):
   trying to overwrite '/usr/share/icons/hicolor/16x16/apps/freecad.png', which 
is also in package freecad 0.16.6712+dfsg1-3
  Errors were encountered while processing:
   /var/cache/apt/archives/freecad-common_0.17+dfsg1-1_all.deb

  Preparing to unpack .../freecad-python2_0.17+dfsg1-1_amd64.deb ...
  Unpacking freecad-python2 (0.17+dfsg1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/freecad-python2_0.17+dfsg1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/freecad/bin/FreeCAD', which is also in package 
freecad 0.16.6712+dfsg1-3
  Errors were encountered while processing:
   /var/cache/apt/archives/freecad-python2_0.17+dfsg1-1_amd64.deb

  Preparing to unpack .../libfreecad-python2-0.17_0.17+dfsg1-1_amd64.deb ...
  Unpacking libfreecad-python2-0.17 (0.17+dfsg1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libfreecad-python2-0.17_0.17+dfsg1-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/freecad/lib/DraftUtils.so', which is also in 
package freecad 0.16.6712+dfsg1-3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libfreecad-python2-0.17_0.17+dfsg1-1_amd64.deb


cheers,

Andreas


freecad=0.16.6712+dfsg1-3_freecad-common=0.17+dfsg1-1.log.gz
Description: application/gzip

Processed: your mail

[Debian Bug Tracking System]

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

> # bugs with submitter de...@blough.us
> submitter 801727 !
Bug #801727 [src:pugixml] pugixml: Please package pugixml variant with wchar 
enabled
Changed Bug submitter to 'Bill Blough ' from 'William 
Blough '.
> submitter 884037 !
Bug #884037 [xalan] xalan: Xalan does not support building on hurd arch
Changed Bug submitter to 'Bill Blough ' from 'William 
Blough '.
> submitter 881026 !
Bug #881026 [src:openms] openms: Transition to xerces-c3.2
Changed Bug submitter to 'Bill Blough ' from 'William 
Blough '.
> submitter 881127 !
Bug #881127 [release.debian.org] transition: xerces-c
Changed Bug submitter to 'Bill Blough ' from 'William 
Blough '.
> # bugs with owner de...@blough.us
> thanks
Stopping processing here.

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

Bug#904995: xserver-common: black screen with mouse on screen rotate.

[Simon Polack]

Package: xserver-common
Version: 2:1.20.0-3
Followup-For: Bug #904995

Dear Maintainer,

please upgrade to current upstream bugfix release 1.20.1. Thank you a
lot.

Best
Simon


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

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

Versions of packages xserver-common depends on:
ii  x11-common 1:7.7+19
ii  x11-xkb-utils  7.7+4
ii  xkb-data   2.23.1-1

Versions of packages xserver-common recommends:
ii  xauth1:1.0.10-1
ii  xfonts-base  1:1.0.4+nmu1

xserver-common suggests no packages.

-- no debconf information

Bug#842815: Help needed for change of build system to gradle of package libsis-jhdf5-java

[Andreas Tille]

Hi,

upstream of libsis-jhdf5-java[1] has switched to gradle in its new
version that is compatible with HDF5 1.10.  I tried to adapt debian/rules
from previous manual build to buildsystem=gradle but got:

...
Parallel execution is an incubating feature.
Evaluating root project 'libsis-jhdf5-java' using build file 
'/build/libsis-jhdf5-java-18.08~pre+git20180805.da55947+dfsg/build.gradle'.
Compiling build file 
'/build/libsis-jhdf5-java-18.08~pre+git20180805.da55947+dfsg/build.gradle' 
using SubsetScriptTransformer.
Compiling build file 
'/build/libsis-jhdf5-java-18.08~pre+git20180805.da55947+dfsg/build.gradle' 
using BuildScriptTransformer.
Compiling script 
'/build/libsis-jhdf5-java-18.08~pre+git20180805.da55947+dfsg/javaproject.gradle'
 using SubsetScriptTransformer.
Compiling script 
'/build/libsis-jhdf5-java-18.08~pre+git20180805.da55947+dfsg/repository.gradle' 
using SubsetScriptTransformer.
Compiling script 
'/build/libsis-jhdf5-java-18.08~pre+git20180805.da55947+dfsg/repository.gradle' 
using BuildScriptTransformer.
Creating new cache for metadata-2.23/module-versions, path 
/build/libsis-jhdf5-java-18.08~pre+git20180805.da55947+dfsg/.gradle/caches/modules-2/metadata-2.23/module-versions.bin,
 access org.gradle.cache.internal.DefaultCacheAccess@350dec85

FAILURE: Build failed with an exception.

* Where:
Build file 
'/build/libsis-jhdf5-java-18.08~pre+git20180805.da55947+dfsg/build.gradle' 
line: 1

* What went wrong:
A problem occurred evaluating root project 'libsis-jhdf5-java'.
> Could not resolve all dependencies for configuration 'classpath'.
   > Could not resolve cisd:cisd-ant-tasks:+.
 Required by:
 unspecified:unspecified:unspecified
  > No cached version listing for cisd:cisd-ant-tasks:+ available for 
offline mode.

* Try:
Run with --debug option to get more log output.

* Exception is:
org.gradle.api.GradleScriptException: A problem occurred evaluating root 
project 'libsis-jhdf5-java'.
at 
org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:92)
...
at 
org.gradle.api.internal.artifacts.ivyservice.ivyresolve.DynamicVersionResolver.resolve(DynamicVersionResolver.java:67)
... 104 more


BUILD FAILED

Total time: 5.829 secs
Received result Failure[value=org.gradle.initialization.ReportedException: 
org.gradle.internal.exceptions.LocationAwareException: Build file 
'/build/libsis-jhdf5-java-18.08~pre+git20180805.da55947+dfsg/build.   gradle' 
line: 1
A problem occurred evaluating root project 'libsis-jhdf5-java'.] from daemon 
DaemonInfo{pid=26176, address=[01070135-56e1-461a-92ea-35d94d1e1ee5 port:41021, 
addresses:[/0:0:0:0:0:0:0:1, /127.0.0.1]],state=Busy, 
lastBusy=1534230750655, 
context=DefaultDaemonContext[uid=37bdd18f-143d-4071-ab24-f17f8d67fb44,javaHome=/usr/lib/jvm/java-10-openjdk-amd64,daemonRegistryDir=/build/libsis-jhdf5-java-18.08~pre+

git20180805.da55947+dfsg/.gradle/daemon,pid=26176,idleTimeout=12,daemonOpts=-XX:+HeapDumpOnOutOfMemoryError,-Xmx1024m,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]}
 (build   should be done).



Since I had no idea how to fix this I simply tried to remove this
dependency definition (ant is installed as Build-Dependency anyway) and
thus I tried the following quilt patch:


$ git diff
diff --git a/debian/patches/fix_build_dir.patch 
b/debian/patches/fix_build_dir.patch
index 1d652b2..163553c 100644
--- a/debian/patches/fix_build_dir.patch
+++ b/debian/patches/fix_build_dir.patch
@@ -4,7 +4,7 @@ Description: Do not make wrong assumptions about directory name
 
 --- a/javaproject.gradle
 +++ b/javaproject.gradle
-@@ -50,7 +50,7 @@ sourceSets {
+@@ -50,13 +50,9 @@ sourceSets {
  buildDir = 'targets/gradle'
  
  buildscript {
@@ -12,4 +12,10 @@ Description: Do not make wrong assumptions about directory 
name
 +apply from: 'repository.gradle'
  
  repositories repositoryConfig
- 
+-
+-dependencies {
+-classpath 'cisd:cisd-ant-tasks:+'
+-}
+ }
+ 
+ repositories repositoryConfig


This leads to:


...
FAILURE: Build failed with an exception.

* Where:
Build file 
'/build/libsis-jhdf5-java-18.08~pre+git20180805.da55947+dfsg/build.gradle' 
line: 40

* What went wrong:
A problem occurred evaluating root project 'libsis-jhdf5-java'.
> Could not resolve all dependencies for configuration ':runtime'.
   > Could not resolve cisd:cisd-args4j:+.
 Required by:
 project :
  > No cached version listing for cisd:cisd-args4j:+ available for offline 
mode.
   > Could not resolve cisd:cisd-base:+.
 Required by:
 project :
  > No cached version listing for cisd:cisd-base:+ available for offline 
mode.
   > Could not resolve rinn:restrictions:+.
 Required by:
 project :
  > No cached version listing for rinn:restrictions:+ available for offline 
mode.

* Try:
Run with --debug option to get more log output.



I wonder how I 

Bug#893184: artemis FTBFS with openjdk-9

[Markus Koschany]

Hi,

Am 13.08.2018 um 13:23 schrieb Andreas Tille:
[...]
> I tried hard to add junit4.jar to the classpath but my attempts failed.
> It should be done in the latest quilt patch in test/build-test.xml but
> I have no idea how to use it properly (I actually think all *.jar in
> /usr/share/java are in classpath but it just does not work),
> 
> Any help would be welcome
> 
>   Andreas.

I pushed some changes and the tests build now. You might want to
investigate some of the test failures though, they could be related to
the missing libjacoco-java.

Strangely the fix-tests.patch was missing although it was referenced in
the series file. I updated the test-classpath.patch and set src.lib.dir
to /usr/share/java everywhere and I also disabled three tests that were
failing since we use OpenJDK 10 and not 8 as upstream expects it.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#906049: marked as done (Broken Version: in pkg-config file)

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 08:39:41 +
with message-id 
and subject line Bug#906049: fixed in libssh 0.8.1-1
has caused the Debian Bug report #906049,
regarding Broken Version: in pkg-config file
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.)


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

The new libssh's pkg-config file is broken, it has an empty version:

| $ pkg-config --modversion libssh
| $ grep Version /usr/lib/x86_64-linux-gnu/pkgconfig/libssh.pc
| Version: 

The previous version, still in testing, is correct:

| $ pkg-config --modversion libssh
| 0.7.5
| $

RC bug as this causes depending packages to FTBFS, e. g. cockpit:

| checking for LIBSSH... no
| configure: error: Package requirements (libssh >= 0.6.0) were not met:
| 
| Requested 'libssh >= 0.6.0' but version of libssh is

Thanks,

Martin
--- End Message ---
--- Begin Message ---
Source: libssh
Source-Version: 0.8.1-1

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated libssh 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, 14 Aug 2018 09:43:56 +0200
Source: libssh
Binary: libssh-4 libssh-gcrypt-4 libssh-dev libssh-gcrypt-dev libssh-doc
Architecture: source amd64 all
Version: 0.8.1-1
Distribution: unstable
Urgency: medium
Maintainer: Laurent Bigonville 
Changed-By: Laurent Bigonville 
Description:
 libssh-4   - tiny C SSH library (OpenSSL flavor)
 libssh-dev - tiny C SSH library. Development files (OpenSSL flavor)
 libssh-doc - tiny C SSH library. Documentation files
 libssh-gcrypt-4 - tiny C SSH library (gcrypt flavor)
 libssh-gcrypt-dev - tiny C SSH library. Development files (gcrypt flavor)
Closes: 906049
Changes:
 libssh (0.8.1-1) unstable; urgency=medium
 .
   * New upstream version 0.8.1
 - Fix Version field in pkg-config file (Closes: #906049)
   * debian/*-dev.install: Install the libssh-config.cmake file
   * debian/libssh-gcrypt-4.lintian-overrides: Adjust soname of the library
Checksums-Sha1:
 62eb36692c4003dd30f78c07c05876a779ec402a 2173 libssh_0.8.1-1.dsc
 c556abb2c0edf4c2db4ac1873aaf248b081f8978 409572 libssh_0.8.1.orig.tar.xz
 93469d94799307fbc5f9fc8a17bd293167ee3857 833 libssh_0.8.1.orig.tar.xz.asc
 358da0b406a2b940420192d2b043ea247be9a936 18040 libssh_0.8.1-1.debian.tar.xz
 2f5ca9313af06d836e3e632c0c5ab27686433d23 554472 
libssh-4-dbgsym_0.8.1-1_amd64.deb
 b07089c52cdba635e9835901a2e4f2276af20f98 186976 libssh-4_0.8.1-1_amd64.deb
 f299ad86c185507e6c2d421a08e6ee0d757e2093 230380 libssh-dev_0.8.1-1_amd64.deb
 77867e0fc74cf5b09dd210dd7af155df030452a4 299000 libssh-doc_0.8.1-1_all.deb
 6dfe746ddba0ea120bd4ce1885db98860146a330 560876 
libssh-gcrypt-4-dbgsym_0.8.1-1_amd64.deb
 571c4a795982a91093fb708d0dcc8c1c25a3cb58 190024 
libssh-gcrypt-4_0.8.1-1_amd64.deb
 b64f562a83598b4fd04f94c26ed35e52e964eefe 230388 
libssh-gcrypt-dev_0.8.1-1_amd64.deb
 f749f72a66862869d438032eeb8eceee1803658b 8899 libssh_0.8.1-1_amd64.buildinfo
Checksums-Sha256:
 eae483d35d77485efdf8fd24abd10cbee556bc17b5424245bdd199ff918f530d 2173 
libssh_0.8.1-1.dsc
 d17f1267b4a5e46c0fbe66d39a3e702b8cefe788928f2eb6e339a18bb00b1924 409572 
libssh_0.8.1.orig.tar.xz
 b49ab9f322bb9012a0d0995e1817edeaa791b15f09553c50ef6d2b476ca4d8fa 833 
libssh_0.8.1.orig.tar.xz.asc
 db5fc0b1dc190dbfb05c25bbd55b05ee8c539eedf1753d2297190accd6324e85 18040 
libssh_0.8.1-1.debian.tar.xz
 adfa30e2f666ac8c5dd2cade848b223fb9604466af8371bc583eaee6463f12ca 554472 
libssh-4-dbgsym_0.8.1-1_amd64.deb
 1758215ea1d2c3cf3e0eec14c1a5c0db849fc87409c295b1faf34e58fd99dc3a 186976 
libssh-4_0.8.1-1_amd64.deb
 750678737be9d94248511ae05669d345c8af72545230db17f87f4ccde4dfb3c9 230380 
libssh-dev_0.8.1-1_amd64.deb
 0259dccc9bd11f553d57cbc1b7de7433ad209a4fa6f2d2cfa5f6ddc101875f04 299000 
libssh-doc_0.8.1-1_all.deb
 a5627798063a28ef51de1ff226d417b3554be9ca736d13a893ee6c491eed7bb7 560876 
libssh-gc

Processed: Missing/Broken dependencies are RC

[Debian Bug Tracking System]

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

> severity 902594 serious
Bug #902594 [python3-setuptools-git] python3-setuptools-git should depend on 
python3-setuptools
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#906100: python3-pygpu-dbg should depend on python3 packages, not python2 packages

[Adrian Bunk]

Package: python3-pygpu-dbg
Version: 0.6.9-2
Severity: serious
Tags: patch

Fix:

--- debian/control.old  2018-08-12 21:15:24.235132664 +
+++ debian/control  2018-08-12 21:15:37.911132533 +
@@ -151,7 +151,7 @@
 Section: debug
 Priority: extra
 Depends: ${misc:Depends},
- ${python:Depends},
+ ${python3:Depends},
  ${shlibs:Depends},
  python3-numpy-dbg,
  python3-pygpu (= ${binary:Version})

Bug#906101: python3-sendfile-dbg should depend on python3-sendfile, not python-sendfile

[Adrian Bunk]

Package: python3-sendfile-dbg
Version: 2.0.1-1
Severity: serious
Tags: patch

Fix:

--- debian/control.old  2018-08-14 08:22:19.330237985 +
+++ debian/control  2018-08-14 08:22:37.738237810 +
@@ -58,7 +58,7 @@
 Priority: extra
 Section: debug
 Architecture: any
-Depends: python-sendfile (= ${binary:Version}), ${shlibs:Depends}, 
${misc:Depends},
+Depends: python3-sendfile (= ${binary:Version}), ${shlibs:Depends}, 
${misc:Depends},
  ${python3:Depends}
 Recommends: python3-dbg
 Provides: ${python3:Provides}

Processed: Bug #904615 in rpyc marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #904615 [python3-rpyc] python3-rpyc: fails to install with Python 3.7
Added tag(s) pending.

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

Bug#904615: Bug #904615 in rpyc marked as pending

[Carl Suster]

Control: tag -1 pending

Hello,

Bug #904615 in rpyc 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/rpyc/commit/aa118d2156a761be1f53f4f510b62e9a09531477


New upstream release (Closes: #904615).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/904615

Bug#902573: closed by Jeremy Bicha (Re: firefox-esr: firefox 60.1.0esr requires nss >= 3.36.4)

[Adrian Bunk]

Control: reopen -1

On Tue, Aug 14, 2018 at 01:09:06AM +, Debian Bug Tracking System wrote:
>...
> Date: Mon, 13 Aug 2018 21:05:28 -0400
> From: Jeremy Bicha 
> To: 902573-d...@bugs.debian.org
> Subject: Re: firefox-esr: firefox 60.1.0esr requires nss >= 3.36.4
> 
> It is not guaranteed for you to be able to build a package that you
> found in experimental (now in unstable) on a machine running Debian
> stable.
>...

This is actually supposed to work, and also required for usecases like
the official Debian backports[1].

We do not have automated testing setup for testing this,
but when such insufficient version constraints in build
dependencies are found they do get fixed.

> Thanks,
> Jeremy Bicha

cu
Adrian

[1] backports are not relevant for the exceptional case of firefox-esr

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: Re: Bug#902573 closed by Jeremy Bicha (Re: firefox-esr: firefox 60.1.0esr requires nss >= 3.36.4)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #902573 {Done: Jeremy Bicha } [firefox-esr] firefox-esr: 
firefox 60.1.0esr requires nss >= 3.36.4
Bug reopened
Ignoring request to alter fixed versions of bug #902573 to the same values 
previously set

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

Bug#903325: marked as done (blinker: FTBFS in buster/sid (dh_installdocs: Cannot find "README"))

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 07:33:51 +
with message-id 
and subject line Bug#903325: fixed in blinker 1.4+dfsg1-0.2
has caused the Debian Bug report #903325,
regarding blinker: FTBFS in buster/sid (dh_installdocs: Cannot find "README")
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.)


-- 
903325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:blinker
Version: 1.4+dfsg1-0.1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   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:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
I: pybuild base:217: /usr/bin/python setup.py build 
running build

[... snipped ...]

dh_auto_install: Compatibility levels before 9 are deprecated (level 7 in use)
I: pybuild base:217: /usr/bin/python setup.py install --root 
/<>/blinker-1.4+dfsg1/debian/tmp 
running install
running build
running build_py
running install_lib
creating /<>/blinker-1.4+dfsg1/debian/tmp
creating /<>/blinker-1.4+dfsg1/debian/tmp/usr
creating /<>/blinker-1.4+dfsg1/debian/tmp/usr/lib
creating /<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7
creating 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages
creating 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/blinker
copying 
/<>/blinker-1.4+dfsg1/.pybuild/cpython2_2.7/build/blinker/_utilities.py
 -> 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/blinker
copying 
/<>/blinker-1.4+dfsg1/.pybuild/cpython2_2.7/build/blinker/__init__.py 
-> 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/blinker
copying 
/<>/blinker-1.4+dfsg1/.pybuild/cpython2_2.7/build/blinker/_saferef.py 
-> 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/blinker
copying 
/<>/blinker-1.4+dfsg1/.pybuild/cpython2_2.7/build/blinker/base.py -> 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/blinker
byte-compiling 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/blinker/_utilities.py
 to _utilities.pyc
byte-compiling 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/blinker/__init__.py
 to __init__.pyc
byte-compiling 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/blinker/_saferef.py
 to _saferef.pyc
byte-compiling 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/blinker/base.py
 to base.pyc
running install_egg_info
Writing 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/blinker-1.4.egg-info
I: pybuild base:217: /usr/bin/python3 setup.py install --root 
/<>/blinker-1.4+dfsg1/debian/tmp 
running install
running build
running build_py
running install_lib
creating /<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6
creating 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6/dist-packages
creating 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6/dist-packages/blinker
copying 
/<>/blinker-1.4+dfsg1/.pybuild/cpython3_3.6/build/blinker/_utilities.py
 -> 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6/dist-packages/blinker
copying 
/<>/blinker-1.4+dfsg1/.pybuild/cpython3_3.6/build/blinker/__init__.py 
-> 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6/dist-packages/blinker
copying 
/<>/blinker-1.4+dfsg1/.pybuild/cpython3_3.6/build/blinker/_saferef.py 
-> 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6/dist-packages/blinker
copying 
/<>/blinker-1.4+dfsg1/.pybuild/cpython3_3.6/build/blinker/base.py -> 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6/dist-packages/blinker
byte-compiling 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6/dist-packages/blinker/_utilities.py
 to _utilities.cpython-36.pyc
byte-compiling 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6/dist-packages/blinker/__init__.py
 to __init__.cpython-36.pyc
byte-compiling 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6/dist-packages/blinker/_saferef.py
 to _saferef.cpython-36.pyc
byte-compiling 
/<>/blinker-1.4+dfsg1/debian

Bug#906084: marked as done (python3-pyds9 should depend on python3-six, not python-six)

[Debian Bug Tracking System]

Your message dated Tue, 14 Aug 2018 09:28:38 +0200
with message-id 
and subject line Fwd: Accepted python-pyds9 1.8.1-2 (source) into unstable
has caused the Debian Bug report #906084,
regarding python3-pyds9 should depend on python3-six, not python-six
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.)


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

python3-pyds9 should depend on python3-six, not python-six.
--- End Message ---
--- Begin Message ---
Source: python-pyds9
Source-Version: 1.8.1-2

This is fixed with the latest upload. Thank you very much for reporting!

Cheers

Ole


 Forwarded Message 
Subject: Accepted python-pyds9 1.8.1-2 (source) into unstable
Date: Tue, 14 Aug 2018 07:19:27 +
From: Ole Streicher 
To: debian-devel-chan...@lists.debian.org

Format: 1.8
Date: Tue, 14 Aug 2018 08:55:21 +0200
Source: python-pyds9
Binary: python-pyds9 python3-pyds9
Architecture: source
Version: 1.8.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers

Changed-By: Ole Streicher 
Description:
 python-pyds9 - Communication with the ds9 image display program (Python-2)
 python3-pyds9 - Communication with the ds9 image display program (Python-3)
Changes:
 python-pyds9 (1.8.1-2) unstable; urgency=medium
 .
   * Add Bug-Db and Repository to d/u/metadata
   * Update VCS fields to use salsa.d.o
   * Push Standards-Version to 4.2.0. Change URLs to https
   * Push compat to 11
   * Depend python3-pyds9 on python3-six, not python-six
Checksums-Sha1:
 bf295cd6e565187286af6c2d80b9a6b4e9b37dff 2231 python-pyds9_1.8.1-2.dsc
 33188341e307f54c347ce37abe4afc1390a69917 3492
python-pyds9_1.8.1-2.debian.tar.xz
Checksums-Sha256:
 4db249e838f289d2fc3b351262e952c8a146257e2defcf2e7eedfc3700cbf6cc 2231
python-pyds9_1.8.1-2.dsc
 92874ad988396527ef8a2649d25274ec763af09c6c784ecec543478ff3ee5109 3492
python-pyds9_1.8.1-2.debian.tar.xz
Files:
 a879714c505b23b813db67a4605d1978 2231 python optional
python-pyds9_1.8.1-2.dsc
 31306597fbcb2d2883bfb8a1202042ff 3492 python optional
python-pyds9_1.8.1-2.debian.tar.xz--- End Message ---

Bug#906094: psi4: missing dependency on python3

[Adrian Bunk]

Package: psi4
Version: 1:1.1-5
Severity: serious
Tags: patch

psi4 needs a dependency on python3 for /usr/bin/psi4:

--- debian/control.old  2018-08-13 21:58:29.746594942 +
+++ debian/control  2018-08-14 00:15:45.898516395 +
@@ -21,6 +21,7 @@
   libhdf5-dev,
   libint-dev (>= 1.2.0-1),
liblapack-dev,
+   dh-python,
   python3-dev,
python3-numpy,
python3-pybind11,
@@ -34,7 +35,7 @@
 
 Package: psi4
 Architecture: any
-Depends: psi4-data (= ${source:Version}), ${misc:Depends}, ${shlibs:Depends}
+Depends: psi4-data (= ${source:Version}), ${misc:Depends}, ${shlibs:Depends}, 
${python3:Depends}
 Description: Quantum Chemical Program Suite
  PSI4 is an ab-initio quantum chemistry program.  It is especially designed to
  accurately compute properties of small to medium molecules using highly
--- debian/rules.old2018-08-13 21:58:26.866594969 +
+++ debian/rules2018-08-13 21:58:41.678594828 +
@@ -8,7 +8,7 @@
 export OMPI_MCA_orte_rsh_agent=/bin/false
 
 %: 
-   dh $@ --parallel --builddirectory=builddir
+   dh $@ --parallel --builddirectory=builddir --with python3
 
 override_dh_auto_clean:
dh_auto_clean --builddirectory=builddir