Bug#934293: marked as done (fuse3.postinst fails)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sun, 01 Sep 2019 06:49:36 +
with message-id 
and subject line Bug#934293: fixed in fuse3 3.6.2-1
has caused the Debian Bug report #934293,
regarding fuse3.postinst fails
to be marked as done.

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

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


-- 
934293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fuse3
Version: 3.4.1-1
Severity: normal

root@nuc8:/home/roderich# apt install fuse3
...
Setting up fuse3 (3.4.1-1) ...
dpkg: error processing package fuse3 (--configure):
 installed fuse3 package post-installation script subprocess returned error
exit status 1
Errors were encountered while processing:
 fuse3
E: Sub-process /usr/bin/dpkg returned an error code (1)


The problem is line 34 of fuse3.postint, running it by hand gives

root@nuc8:/home/roderich# udevadm test --action -p  $(udevadm info -q path -n
/dev/fuse)
Invalid action '-p'


Cheers, Roderich




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

Kernel: Linux 5.2.7 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fuse3 depends on:
ii  adduser 3.118
ii  libc6   2.28-10
ii  libfuse3-3  3.4.1-1
ii  lsb-base10.2019051400
ii  mount   2.34-0.1
ii  sed 4.7-1

fuse3 recommends no packages.

fuse3 suggests no packages.

-- Configuration Files:
/etc/fuse.conf [Errno 2] No such file or directory: '/etc/fuse.conf'

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fuse3
Source-Version: 3.6.2-1

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 01 Sep 2019 06:15:20 +
Source: fuse3
Architecture: source
Version: 3.6.2-1
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 934293
Changes:
 fuse3 (3.6.2-1) unstable; urgency=medium
 .
   * New upstream release.
   * Drop outdated udevadm commands from postinst (closes: #934293).
   * Remove dh_makeshlibs override.
   * Update Standards-Version to 4.4.0 .
Checksums-Sha1:
 6d5f7f030e85a03265357b054e6eb533bf9b04ee 2327 fuse3_3.6.2-1.dsc
 2bdef7a3f1f9e63fed87559c6e77d27e5f2c2e0c 126 fuse3_3.6.2.orig.tar.xz
 32dff1bd03d43226eb833be6a7897cce00e6aa2f 1012 fuse3_3.6.2.orig.tar.xz.asc
 1761c11fce6ba2ccbfdab8332cfc8fe62d4c8534 16552 fuse3_3.6.2-1.debian.tar.xz
Checksums-Sha256:
 e5b48112d6874035f71a94fa6525b2098987d162e0cfec2916bbc19782fe3269 2327 
fuse3_3.6.2-1.dsc
 f45869427575e1e59ab743a67deb57addbf2cb8f9ce431199dbd40ddab71f281 126 
fuse3_3.6.2.orig.tar.xz
 f4f7d6139ef2ba5de395c34aee50ab1c9eb5b27b77c13155fff5da6db32f9edf 1012 
fuse3_3.6.2.orig.tar.xz.asc
 61db31529bf2e6c10398c8e047a3d322a8cd4545dd15b8ec4c76915398d0cf07 16552 
fuse3_3.6.2-1.debian.tar.xz
Files:
 2a1177ebf29c4ac0989fb8837c7e491b 2327 utils optional fuse3_3.6.2-1.dsc
 1798945aa69434286723ba141c7a 126 utils optional fuse3_3.6.2.orig.tar.xz
 b86f354336e6231029d8939adf9fd91d 1012 utils optional 
fuse3_3.6.2.orig.tar.xz.asc
 c2a1a400e8dd37544e0b6f955ec50c56 16552 utils optional 
fuse3_3.6.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl1rZe0ACgkQ3OMQ54ZM
yL+N5BAAlOmtcc7fp8Kwovqy/IrJ81FK089RgsyxtxHCCCGyOQKre3if+iB4i782
3SmUj/piLsyAolXe1TjWeBtKQi3b0NwR65C7jDyLjpLXsFB9pYs3OHSex7kPQNQk
KFTZfFrqSPw2lDU0tNFbhOz9hABxl7k1flkbdhQXwZCtjB861/4BA4VpImQOQPco
RD6yp3GceY8dgoKpJTZdkmvc0LZgyOgQcU/nEEA5jWpeJJaQ+HGbEccOv+pmFgPZ
evJPYEXC1T2B4D5jYXgeP1U2HNPvJaash3bOIEGG08Oog6TW6eMWwXYTgtOw48uq
ssvpZvbfWAbXdyQ/k3xTpllWFv04NObd0a4SHdrIt6HgFFMm6EIg+zl2BlKs

Processed: reassign 939022

2019-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 939022 pyresample
Bug #939022 [basemap] pyresample: autopkgtest failure with PROJ 6 (epsg data 
file removed)
Bug reassigned from package 'basemap' to 'pyresample'.
Ignoring request to alter found versions of bug #939022 to the same values 
previously set
Ignoring request to alter fixed versions of bug #939022 to the same values 
previously set
> thanks
Stopping processing here.

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



Bug#932197: Please switch to Python 3

2019-08-31 Thread Scott Kitterman
On Tue, 16 Jul 2019 16:07:38 +0200 Thomas Goirand  wrote:
> Source: nipype
> Version: 1.1.9-1
> Severity: important
> 
> Hi,
> 
> I'd like to switch python-xvfbwrapper to Python 3 only, and noticed that
> nipype only has Python 2 support. Python 2 is going to be removed from
> Sid/Testing.

Python3 is supported upstream.

Scott K



Bug#903201: marked as done (cinnamon: CVE-2018-13054: privilege escalation in cinnamon-settings-users.py GUI)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sun, 1 Sep 2019 13:00:08 +0900
with message-id <20190901040008.coxo57fmkbz6k...@bulldog.preining.info>
and subject line CVE-2018-13054: privilege escalation in 
cinnamon-settings-users.py GUI
has caused the Debian Bug report #903201,
regarding cinnamon: CVE-2018-13054: privilege escalation in 
cinnamon-settings-users.py GUI
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.)


-- 
903201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cinnamon
Version: 3.2.7-4
Severity: grave
Tags: patch security upstream
Forwarded: https://github.com/linuxmint/Cinnamon/pull/7683

Hi,

The following vulnerability was published for cinnamon.

CVE-2018-13054[0]:
| An issue was discovered in Cinnamon 1.9.2 through 3.8.6. The
| cinnamon-settings-users.py GUI runs as root and allows configuration of
| (for example) other users' icon files in
| _on_face_browse_menuitem_activated and _on_face_menuitem_activated.
| These icon files are written to the respective user's $HOME/.face
| location. If an unprivileged user prepares a symlink pointing to an
| arbitrary location, then this location will be overwritten with the
| icon content.

It requires admin intervention though, but still filling it as RC
severity.

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-13054
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-13054
[1] https://github.com/linuxmint/Cinnamon/pull/7683
[2] https://bugzilla.suse.com/show_bug.cgi?id=1083067

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
fixed 903201 3.8.8-1
thanks

Hi all,

there is still 
#903201 cinnamon: CVE-2018-13054: privilege escalation in 
cinnamon-settings-users.py GUI
open, but it is already fixed in 3.8.8, so I am closing this bug now and
mark it as fixed in 3.8.8-1 in buster.

There is a fix to remove the root owned .face file that is not
incorporated, we could add that later on. For the time being I create a
buster branch that incorporates that fix. We will see if we upload it to
a point release.

Best

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13--- End Message ---


Processed: CVE-2018-13054: privilege escalation in cinnamon-settings-users.py GUI

2019-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 903201 3.8.8-1
Bug #903201 [src:cinnamon] cinnamon: CVE-2018-13054: privilege escalation in 
cinnamon-settings-users.py GUI
Ignoring request to alter fixed versions of bug #903201 to the same values 
previously set
> thanks
Stopping processing here.

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



Bug#939078: bro: unfulfilled (build) dependencies libbroker-dev and libbroker0

2019-08-31 Thread Matthias Klose

Package: src:bro
Version: 2.6.1+ds1-1
Severity: serious
Tags: sid bullseye

according to https://tracker.debian.org/pkg/bro, it references a nn-existing 
libbroker0, and doesn't build on any other architecture because of a missing 
libbroker-dev package.




Bug#935702: marked as done (Mapped devices of size ≥2TiB are truncated on 32-bits platforms)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 23:17:09 +
with message-id 
and subject line Bug#935702: fixed in cryptsetup 2:2.1.0-5+deb10u2
has caused the Debian Bug report #935702,
regarding Mapped devices of size ≥2TiB are truncated on 32-bits platforms
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.)


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

Package: cryptsetup-bin
Version: 2:2.1.0-5
Severity: serious

Dear Maintainer,

cryptsetup in Stable contains multiple severe integer handling issues.
Created DM device's size is set incorrectly due to integer truncation.

Not only the access to protected data is lost, the integritysetup's 
"open" operation actually succeeds. All reads on the incorrectly created 
DM device will of course fail with I/O errors due to bad integrity tags, 
but all writes will happily write wrong tags at wrong places! This makes 
it very easy for the administrator to destroy the data while trying to 
recover with --integrity-recovery-mode.


The issue is caused by a new set of functions "dm_*_target_set", 
introduced with cryptsetup 2:2.1.0, whose arguments use haphazardly 
chosen integer types, even though the actual types are easy to find.


For example, "uint64_t size" is temporarily stored in a size_t variable.
1) stored in lib/utils_dm.h: struct crypt_dm_active_device { uint64_t 
size, ... }
2) passed to lib/libdevmapper.c dm_*_target_set(..., (size_t)dmd.size, 
...

3) stored in lib/utils_dm.h: struct dm_target { uint64_t size, ... }

Seeing such carelessness in a core crypto software makes me very uneasy.


Best,
n.b.f.

-- Notes:
64-bit systems, whose size_t is 64bit, are safe from this bug.
Partitions smaller than 2TiB (2^32 * 512) are safe from this bug.
Severity: grave may be appropriate due to the potential for data loss.
--- End Message ---
--- Begin Message ---
Source: cryptsetup
Source-Version: 2:2.1.0-5+deb10u2

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

Debian distribution maintenance software
pp.
Guilhem Moulin  (supplier of updated cryptsetup 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, 26 Aug 2019 14:54:10 +0200
Source: cryptsetup
Architecture: source
Version: 2:2.1.0-5+deb10u2
Distribution: buster
Urgency: medium
Maintainer: Debian Cryptsetup Team 

Changed-By: Guilhem Moulin 
Closes: 935702
Changes:
 cryptsetup (2:2.1.0-5+deb10u2) buster; urgency=medium
 .
   * Cherry pick upstream commit 8f8f0b32: Fix mapped segments overflow on
 32bit architectures.  Regression since 2:2.1.0-1.  (Closes: #935702)
Checksums-Sha1:
 fde100155d525dd034556a44391067022d622383 2842 cryptsetup_2.1.0-5+deb10u2.dsc
 2c4559ec0b077016ab39e4b5019774786386c67b 112312 
cryptsetup_2.1.0-5+deb10u2.debian.tar.xz
 16cf0cd7a1faf9952c0296769e1a36a6a6005061 9337 
cryptsetup_2.1.0-5+deb10u2_amd64.buildinfo
Checksums-Sha256:
 be8654f3862a7271cb313a31a862729697c92e28c4dff94d7b575d98e98d9e1a 2842 
cryptsetup_2.1.0-5+deb10u2.dsc
 f775f41955845c849659b83e324514e3b14dbf7a63a7331b9ccbcf3c77252ab0 112312 
cryptsetup_2.1.0-5+deb10u2.debian.tar.xz
 d6c88fbe8cb9bfa549ad7e7ffaa7bc39a466cda9c1c6423db1925cd2d7a34d70 9337 
cryptsetup_2.1.0-5+deb10u2_amd64.buildinfo
Files:
 447dbeb9f41865c7ceabe72f9a768c27 2842 admin optional 
cryptsetup_2.1.0-5+deb10u2.dsc
 0b06ca7e75f6faef108858ca8a1eb4e9 112312 admin optional 
cryptsetup_2.1.0-5+deb10u2.debian.tar.xz
 767e007596382b54eddeab0e58e2daf1 9337 admin optional 
cryptsetup_2.1.0-5+deb10u2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJnDwhpVIFAl1lKDUACgkQ05pJnDwh
pVJ94Q//XIAMsnVtbBE9BytPil+neehdrGkb2/4cX7YRYVgsGHzDhGFbPEoM1ONS
0UeP9xK+tj46/gDnq5bSICwQBdm49ntHh+ABcxaXtFv9d6nf2drxtQsHRzSWFyX4
fU5BD7bnB7+NrOzNRLmV7u+arcycezQoJF/nr2X8YsbMI7kkZHLMf70BZ3lyuNMN
aA7GMSp1qj+muzZxBl4cs3dWatFW/oHR9gMjoi6H2kDVlHnPQSMaDIK8CQj0FKMH
TOAlpQ6MXu2laIOoTFLZYeDT5YSUIyIHekwEg2USf01OszaRL/KMFA7YtMbS56s6
EHgkITB/YfH11Tkb80ewIVlUXAHQTm7VT4j15hLwZXA9l3wwoPeEtCVbZjIHV3sw
cgWRw

Bug#925702: closing 925702

2019-08-31 Thread Steve M . Robbins
close 925702 1.9.0.20190831-1
thanks

Fixed with upload of new upstream 1.9.0.



Processed: closing 925702

2019-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 925702 1.9.0.20190831-1
Bug #925702 [src:googletest] googletest: ftbfs with GCC-9
Ignoring request to alter fixed versions of bug #925702 to the same values 
previously set
Bug #925702 [src:googletest] googletest: ftbfs with GCC-9
Marked Bug as done
> thanks
Stopping processing here.

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



Bug#922978: marked as done (auralquiz: Auralquiz depends on Qt4-based Phonon backends instead of Qt5 counterparts)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 22:20:18 +
with message-id 
and subject line Bug#922978: fixed in auralquiz 1.0.0-2
has caused the Debian Bug report #922978,
regarding auralquiz: Auralquiz depends on Qt4-based Phonon backends instead of 
Qt5 counterparts
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.)


-- 
922978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922978
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: auralquiz
Version: 1.0.0-1.1
Severity: normal

Dear Maintainer,

auralquiz is currently built with Qt5, but since the program
uses Phonon to play sound, and Phonon requires at least one
backend, this package depends on either of 3 possible backends.

The only problem is that the packages for the backends are
the Qt4 versions, not the Qt5 equivalents:

dep: phonon-backend-vlc
or phonon-backend-xine
or phonon-backend-gstreamer


it should depend on:

phonon4qt5-backend-vlc
or phonon4qt5-backend-gstreamer
(the one for Xine has been dead for years)


The current package *can* be used happily if the user installs one
of those manually, or has them for any reason, but auralquiz
has to be removed to remove Qt4.


Thank you for your time! Cheers! o/



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

Kernel: Linux 4.19.0-3-686-pae (SMP w/1 CPU core)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages auralquiz depends on:
ii  libc6   2.28-7
ii  libgcc1 1:8.2.0-21
ii  libgl1  1.1.0-1
ii  libphonon4qt5-4 4:4.10.2-1
ii  libqt5core5a5.11.3+dfsg-5
ii  libqt5gui5  5.11.3+dfsg-5
ii  libqt5widgets5  5.11.3+dfsg-5
ii  libstdc++6  8.2.0-21
ii  libtag1v5   1.11.1+dfsg.1-0.3
ii  phonon-backend-vlc  0.10.2-1
ii  phonon4qt5  4:4.10.2-1

auralquiz recommends no packages.

auralquiz suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: auralquiz
Source-Version: 1.0.0-2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated auralquiz 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, 31 Aug 2019 23:54:35 +0200
Source: auralquiz
Architecture: source
Version: 1.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Closes: 922978
Changes:
 auralquiz (1.0.0-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Scarlett Clark ]
   * Update VCS entries to salsa.
   * Update runtime phonon dependencies to phonon4qt5 and
 remove unmaintained xine. (Closes: #922978)
 .
   [ Reiner Herrmann ]
   * Team upload.
   * d/watch: fix upstream version detection
 .
   [ Markus Koschany ]
   * Declare compliance with Debian Policy 4.4.0.
   * Switch to debhelper-compat = 12.
Checksums-Sha1:
 de07268db07cffa204d6afcf54621198483e2473 2142 auralquiz_1.0.0-2.dsc
 d43db076ebca9449d96f61a19bb8d2032cfb4320 2748 auralquiz_1.0.0-2.debian.tar.xz
 a09f3eece1eed8ba9f2760b83eddde9251e49af9 12034 
auralquiz_1.0.0-2_amd64.buildinfo
Checksums-Sha256:
 a52005f9616e1d09ff627bd567ed5a541aa33cc56c5e9567c5779024871b 2142 
auralquiz_1.0.0-2.dsc
 737895ee80b7edfbcc8bbaca1aff1e911e3b8cb8a853ff066a6d47984c068feb 2748 
auralquiz_1.0.0-2.debian.tar.xz
 b7bd31615c2c391b42087ca4d4fdeb07722f6de65edb03c47a69bb52adf6c3b6 12034 
auralquiz_1.0.0-2_amd64.buildinfo
Files:
 9d62714b2201743147f1f01659cffae2 2142 games optional auralquiz_1.0.0-2.dsc
 14b08dcfabc4eb1764ce4c6601baa49f 2748 games optional 
auralquiz_1.0.0-2.debian.tar.xz
 06ac0ee2e1adb952adf3df20525906ed 12034 games optional 
auralquiz_1.0.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl1q7vdfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuL

Processed: severity of 938993 is important, severity of 938996 is important

2019-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 938993 important
Bug #938993 [clisp] clisp crashes under slime when doing tab-completion
Severity set to 'important' from 'grave'
> severity 938996 important
Bug #938996 [cl-swank] cl-swank: starting clisp under SLIME explodes with: 
FUNCALL: undefined function SWANK::MAKE-OUTPUT-STREAM-FOR-TARGET
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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



Bug#939072: src:python-raven: Should this package be removed

2019-08-31 Thread Scott Kitterman
Package: src:python-raven
Version: 6.3.0-2
Severity: serious
Justification: Policy 2.5

This package is not in Testing, has no rdepends, is RC buggy for quite
some time, and used python2, which we are trying to remove.  It's
currently blocking removal of at least python-celery which blocks quite
a number of other packages.

I think it would be better just to remove this package.

Scott K



Bug#935938: marked as done (android-sdk-meta_25.0.0+11~deb10u1_all.changes REJECTED)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 19:59:44 +
with message-id 
and subject line Bug#935938: fixed in android-sdk-meta 25.0.0+11~deb10u2
has caused the Debian Bug report #935938,
regarding android-sdk-meta_25.0.0+11~deb10u1_all.changes REJECTED
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.)


-- 
935938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: android-sdk-meta
Severity: serious
Version: 25.0.0+11~deb10u1

On 2019-08-28 03:19, Debian FTP Masters wrote:
> android-sdk-build-tools-common_27.0.1+11_all.deb: Does not match file already 
> existing in the pool.
> 
> 
> Mapping buster to stable.
> Mapping stable to proposed-updates.
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
> 
>
>

Despite the source version being 25.0.0+11~deb10u1, the binary packages
that are built are in version 25.0.0+11, hence the reject. See the build
log:

https://buildd.debian.org/status/fetch.php?pkg=android-sdk-meta&arch=all&ver=25.0.0%2B11%7Edeb10u1&stamp=1566961497&raw=0

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
--- End Message ---
--- Begin Message ---
Source: android-sdk-meta
Source-Version: 25.0.0+11~deb10u2

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

Debian distribution maintenance software
pp.
Hans-Christoph Steiner  (supplier of updated android-sdk-meta 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 29 Aug 2019 22:15:45 +0200
Source: android-sdk-meta
Architecture: source
Version: 25.0.0+11~deb10u2
Distribution: buster
Urgency: medium
Maintainer: Android Tools Maintainers 

Changed-By: Hans-Christoph Steiner 
Closes: 935938
Changes:
 android-sdk-meta (25.0.0+11~deb10u2) buster; urgency=medium
 .
   * fix regex for adding Debian version to binary packages (Closes: #935938)
Checksums-Sha1:
 ae9d0dface925afc40245f7825b33ac6789cdb6a 2108 
android-sdk-meta_25.0.0+11~deb10u2.dsc
 51bd2328f61a84d624ffc7b5d3cc17cd68327b76 10468 
android-sdk-meta_25.0.0+11~deb10u2.tar.xz
 b2292e618d21a1d4eaddcc326031527557e34352 5129 
android-sdk-meta_25.0.0+11~deb10u2_source.buildinfo
Checksums-Sha256:
 cb68b2a0b1464369ef1cf93eb58f2557265f1d17149e91b991dfcd1170da48f8 2108 
android-sdk-meta_25.0.0+11~deb10u2.dsc
 34779ed7d68a711b739dd7ddc821584a48606cee92d5f8b422c3d6773a4640a4 10468 
android-sdk-meta_25.0.0+11~deb10u2.tar.xz
 75a3271b2301273a23f26441b10a424c4895bdfc91c63a97816b1de5bf23e7ea 5129 
android-sdk-meta_25.0.0+11~deb10u2_source.buildinfo
Files:
 258e1afe031d986342080e62d89e771a 2108 metapackages optional 
android-sdk-meta_25.0.0+11~deb10u2.dsc
 ff3e7d59b7b087714d00d1924d142709 10468 metapackages optional 
android-sdk-meta_25.0.0+11~deb10u2.tar.xz
 e1879a3010097a882c56a80f6891bd4a 5129 metapackages optional 
android-sdk-meta_25.0.0+11~deb10u2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEElyI52+aGmfUmwGoFPhd4F7obm/oFAl1oOh8ACgkQPhd4F7ob
m/ovQgf9HXGB1YXlfRkKjF7oyhpEKJ8OgNM/bNuZgnzY0N7wbYdS+xWpR7pVSHaW
Ef7M8IFQgTQsw/O1xc/cb2Ms8RzWl0NOnivwQtXzdu75K1d5+gaNBmFj+a/NtsAl
imFsh6H79tf3/YMiNLQaKGjApcHt9lTy3LQfkJ3yZbF56o7dMwrEYIumtjp6VGqS
3EboTP/J8Jus0vUGTLMHreVHgPnqheL0hdymZ435T8LNi1dp3WZ1Oc+uVttOouga
NY61m6jUwOpkPDlXPgkjzJJtIJKaYdJW1uEjeI30I+zc+zJSYBbM1jlkjd7i7X6u
5GnQBdq6f9p6gB9xMBDTjfgePyZf8w==
=8cQh
-END PGP SIGNATURE End Message ---


Bug#875092: marked as done ([polkit-qt-1] Future Qt4 removal from Buster)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 19:53:58 +
with message-id 
and subject line Bug#875092: fixed in polkit-qt-1 0.112.0-7
has caused the Debian Bug report #875092,
regarding [polkit-qt-1] Future Qt4 removal from 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.)


-- 
875092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875092
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: polkit-qt-1
Version: 0.112.0-5
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: polkit-qt-1
Source-Version: 0.112.0-7

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

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
polkit-qt-1 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 31 Aug 2019 16:24:32 -0300
Source: polkit-qt-1
Architecture: source
Version: 0.112.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Closes: 875092
Changes:
 polkit-qt-1 (0.112.0-7) unstable; urgency=medium
 .
   * Teamp upload.
   * Drop Qt 4 support (Closes: #875092). Work heavily based in Moritz
 Mühlenhoff's patch.
   * Bump debhelper compatibility to 12.
 - Pass --list-missing to dh_missing.
   * Bump Standards-Version to 4.4.0, no changes required.
Checksums-Sha1:
 e51ed9bff63ce3f5c331a6deb8d527a3e48485b8 2337 polkit-qt-1_0.112.0-7.dsc
 354ba4830770a399134b276c1b96167ce4e4f023 9124 
polkit-qt-1_0.112.0-7.debian.tar.xz
 9e448b294dbb56c7a84fe16efb053e908805decc 10666 
polkit-qt-1_0.112.0-7_source.buildinfo
Checksums-Sha256:
 bd7643999b38f28af5ef664106ec6f374023bcc5d9b82d70571687ab6556c13c 2337 
polkit-qt-1_0.112.0-7.dsc
 0508e2b4f550b0d82fe7433be888f5bf7b6ab368b59cf029886de94346efa559 9124 
polkit-qt-1_0.112.0-7.debian.tar.xz
 f43259dbc5e62e55ca90ef0e31e6366b344e9335db95cd055e1e0e1857d444bf 10666 
polkit-qt-1_0.112.0-7_source.buildinfo
Files:
 959f5a5995883812d7709ffea1a60cf6 2337 libs optional polkit-qt-1_0.112.0-7.dsc
 94e540ca7191a7af0eab2b57520eb6c8 9124 libs optional 
polkit-qt-1_0.112.0-7.debian.tar.xz
 45a14f3bdf708ad68134c1def7816811 10666 libs optional 
polkit-qt-1_0.11

Bug#931825: marked as done (Dub executable does not run)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 19:51:14 +
with message-id 
and subject line Bug#931825: fixed in dub 1.16.0-1
has caused the Debian Bug report #931825,
regarding Dub executable does not run
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.)


-- 
931825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931825
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dub
Version: 1.12.1-1

Installing dub on Debian unstable (tested on x86 and x64) and then
running "dub" errors out immediately with the following error message:

dub: symbol lookup error: dub: undefined symbol: _Dstd5stdio_.
--- End Message ---
--- Begin Message ---
Source: dub
Source-Version: 1.16.0-1

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

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated dub package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 31 Aug 2019 20:54:34 +0200
Source: dub
Architecture: source
Version: 1.16.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian D Language Group 
Changed-By: Matthias Klumpp 
Closes: 931825
Changes:
 dub (1.16.0-1) unstable; urgency=medium
 .
   * New upstream version: 1.16.0
   * Rebuild dub and add very simple autopkgtest
 so we catch issues early next time (Closes: #931825)
   * Bump dependency on GDC
   * Bump dh compat level and standards version: No changes needed
   * Simplify d/watch
Checksums-Sha1:
 2d143e6369d43942639bd003a7cf9f3fbb52c017 1937 dub_1.16.0-1.dsc
 9801f369ef26febc302a22f1a8da4a58a6d30dae 1280184 dub_1.16.0.orig.tar.gz
 e85c13abd3b674880b3c8fbd1d72f7c0bd198605 4168 dub_1.16.0-1.debian.tar.xz
 a08957c8e576260743d499a05ddbfd2ee819 6970 dub_1.16.0-1_source.buildinfo
Checksums-Sha256:
 d74489bf44f73549fe4cab2d117a02c82f63bfc6af102b1f8bd8f9f30d03d4d4 1937 
dub_1.16.0-1.dsc
 e63a4df707535aefad33e9d49cfa38df61d1b2ae76c9ba6b29fd336c2dd4f89b 1280184 
dub_1.16.0.orig.tar.gz
 f3efa96c5fdf758ea775168e8d5a6e0b6f2ab312166726932f5e8ca9e769f16d 4168 
dub_1.16.0-1.debian.tar.xz
 ee79d15fc9eec79d49da2ef4471d6671570250530a1199417f7fe3142abeb79c 6970 
dub_1.16.0-1_source.buildinfo
Files:
 2973b0879036e9d445eb8caba4147f4c 1937 devel optional dub_1.16.0-1.dsc
 450cc576052b56dfff5de70f0bc8a9e4 1280184 devel optional dub_1.16.0.orig.tar.gz
 01bd1df93593975901b020f38b770a82 4168 devel optional dub_1.16.0-1.debian.tar.xz
 463ccd11bb2addf4eae41805f55df7c4 6970 devel optional 
dub_1.16.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEE0zo/DKFrCsxRpgc4SUyKX79N7OsFAl1qx1cPHG1ha0BkZWJp
YW4ub3JnAAoJEElMil+/Tezr1X4P/2Bjk4UAzVRkEfpwyM/iU9B6Bkmt+OyxYavK
ixVLcd3r3ypEEyDu6viONKKrKb8/nFHtZ3YvyGjn3V4y807A8fwjP6/t+dDHpUhl
0zIv0kMZDTPHk8pIqfNyo4JX6ZnVFKnNFSq7/NITHJE9oHEYJqSm9ZEOKJJPY5Qc
AJWNEf0Kqiu9G+oL/r57GBfTpjPLyVP2svMEGIi0hK4+E1vjz+W4flLdWb1VFzbT
jNxQcKpTuZMhsecpsh/LeFg4aV0DopNmT5hfd0sNGKW1sO0nhLHYdRxSepSE1Xr5
IK1MEaRzFVCKGuIFJcnYNQLoebbYn3z2WYOXjRLUD8ZuRyzl7hR2fFBaTolY4Dvk
EUni1MOm6LSqRKwV7hDKwWfqelm69J8nBw/YpSJgnJwbHqHSIQKN0fhYw8JzqgIy
eNfmwWGYOILclWFeCcuqx7DRQ+hBPfqhp9hGputB0r1sSDnspGfuymX3/91WyOi7
VJqmhkcB+ABzDCx1Kp+LSWpoRhKKGyt8+FLT3OhIpIXk6W4b4fRt0bvcs+FH99u/
0D4l3E8wkfPYrmx+2DxLSOLHbAjCqamYMwX+Q5VxwRxgVgFeOuf9JqU3LZz/svE6
41k+Zr8KzxB6ucyFF5PNHMP26RebymOjvvEPaNwifcp1SXKFlmxj4LZ4bvKeM0JI
rn+Lprhq
=kXI2
-END PGP SIGNATURE End Message ---


Bug#935288: marked as done (python-cmarkgfm: FTBFS on amd64)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 15:28:27 -0400
with message-id <3442998.WREg5s2EAQ@l5580>
and subject line Re: python-cmarkgfm: FTBFS on amd64
has caused the Debian Bug report #935288,
regarding python-cmarkgfm: FTBFS on amd64
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.)


-- 
935288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:python-cmarkgfm
version: 0.4.2-1
severity: serious
tags: ftbfs

Hi,

A binnmu of python-cmarkgfm in unstable fails on amd64:

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

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
On Wed, 21 Aug 2019 11:08:10 + Ivo De Decker  wrote:
> package: src:python-cmarkgfm
> version: 0.4.2-1
> severity: serious
> tags: ftbfs
> 
> Hi,
> 
> A binnmu of python-cmarkgfm in unstable fails on amd64:
> 
> https://buildd.debian.org/status/package.php?p=python-cmarkgfm

I was unable to reproduce the failure and it succeded on the buildd when given 
back, so closing.

Scott K--- End Message ---


Processed: fixed 925702 in 1.9.0.20190831-1

2019-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 925702 1.9.0.20190831-1
Bug #925702 [src:googletest] googletest: ftbfs with GCC-9
Marked as fixed in versions googletest/1.9.0.20190831-1.
> thanks
Stopping processing here.

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



Bug#910422: marked as done (grr-server: broken symlinks: /usr/share/grr-server/grr/artifacts/* -> debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/*)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 19:16:30 +
with message-id 
and subject line Bug#938972: Removed package(s) from unstable
has caused the Debian Bug report #910422,
regarding grr-server: broken symlinks: /usr/share/grr-server/grr/artifacts/* -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/*
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.)


-- 
910422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grr-server
Version: 3.1.0.2+dfsg-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

2m42.8s ERROR: FAIL: Broken symlinks:
  /usr/share/grr-server/grr/artifacts/wmi.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/wmi.yaml 
(grr-server)
  /usr/share/grr-server/grr/artifacts/windows_dll_hijacking.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/windows_dll_hijacking.yaml
 (grr-server)
  /usr/share/grr-server/grr/artifacts/windows.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/windows.yaml 
(grr-server)
  /usr/share/grr-server/grr/artifacts/webbrowser.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/webbrowser.yaml 
(grr-server)
  /usr/share/grr-server/grr/artifacts/unix_common.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/unix_common.yaml
 (grr-server)
  /usr/share/grr-server/grr/artifacts/ntfs.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/ntfs.yaml 
(grr-server)
  /usr/share/grr-server/grr/artifacts/macos.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/macos.yaml 
(grr-server)
  /usr/share/grr-server/grr/artifacts/linux_proc.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/linux_proc.yaml 
(grr-server)
  /usr/share/grr-server/grr/artifacts/linux.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/linux.yaml 
(grr-server)
  /usr/share/grr-server/grr/artifacts/legacy.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/legacy.yaml 
(grr-server)
  /usr/share/grr-server/grr/artifacts/kaspersky_careto.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/kaspersky_careto.yaml
 (grr-server)
  /usr/share/grr-server/grr/artifacts/java.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/java.yaml 
(grr-server)
  /usr/share/grr-server/grr/artifacts/installed_modules.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/installed_modules.yaml
 (grr-server)
  /usr/share/grr-server/grr/artifacts/config_files.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/config_files.yaml
 (grr-server)
  /usr/share/grr-server/grr/artifacts/cloud_services.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/cloud_services.yaml
 (grr-server)
  /usr/share/grr-server/grr/artifacts/applications.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/applications.yaml
 (grr-server)
  /usr/share/grr-server/grr/artifacts/antivirus.yaml -> 
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts/antivirus.yaml 
(grr-server)


The targets contain build-time paths.


cheers,

andreas


grr-server_3.1.0.2+dfsg-6.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 3.1.0.2+dfsg-6+rm

Dear submitter,

as the package grr has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/938972

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---


Bug#921871: marked as done (grr: Prevent entering testing)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 19:16:30 +
with message-id 
and subject line Bug#938972: Removed package(s) from unstable
has caused the Debian Bug report #921871,
regarding grr: Prevent entering testing
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.)


-- 
921871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921871
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: grr
Version: 3.1.0.2+dfsg-6
Severity: grave

The Buster release should not contain GRR.

The version in unstable (3.1.0.2) is outdated and effectively unsuppoted
by upstream. Current upstream versions require many thus far unpackaged
build-dependencies for building the web-based UI, including two dozen
NodeJS modules and a newer version of the Java/Maven-based
clojure-compiler. We won't be able to get this situation fixed in time.

Cheers,
-Hilko
--- End Message ---
--- Begin Message ---
Version: 3.1.0.2+dfsg-6+rm

Dear submitter,

as the package grr has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/938972

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---


Bug#927131: marked as done (src:grr: Please port to python3)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 19:16:30 +
with message-id 
and subject line Bug#938972: Removed package(s) from unstable
has caused the Debian Bug report #927131,
regarding src:grr: Please port to python3
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.)


-- 
927131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927131
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:grr
Version: 3.1.0.2+dfsg-6
Severity: important

Python2.7 will go out of upstream security support during the Bullseye
development cycle.  It is not safe to assume it will be included in the
next release, so if you want to be sure grr can stay in Debian, please port
it to python3 (I see there are upstream commits for a python3 port, but no
release yet).

Personally, I want to remove some packages I maintain, particularly python-
ipaddr, which grr depends on during the Bullseye cycle, regardless of what
happens to python2.7, so please update (python3 includes the ipaddress module,
which was developed from ipaddr, in the standard library).

I'm aware there are complications in updating to a newer release.  I figure
early notice is better than late.
--- End Message ---
--- Begin Message ---
Version: 3.1.0.2+dfsg-6+rm

Dear submitter,

as the package grr has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/938972

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---


Bug#935275: marked as done (dustmite: FTBFS on amd64)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 20:57:47 +0200
with message-id 

and subject line Re: Bug#931825: Dub executable does not run
has caused the Debian Bug report #933675,
regarding dustmite: FTBFS on amd64
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.)


-- 
933675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:dustmite
version: 0~20170126.e95dff8-3
severity: serious
tags: ftbfs

Hi,

A binnmu of dustmite in unstable fails on amd64:

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

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
This issue is indeed mysteriously gone now, with GDC 8 and 9.
I can't reproduce it anymore, so the only thing left to do is fix up
the affected packages by simply rebuilding them.

Cheers,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/--- End Message ---


Bug#933675: marked as done (gdc-8: Unable to link D applications against runtime/stdlib)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 20:57:47 +0200
with message-id 

and subject line Re: Bug#931825: Dub executable does not run
has caused the Debian Bug report #933675,
regarding gdc-8: Unable to link D applications against runtime/stdlib
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.)


-- 
933675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dub
Version: 1.12.1-1

Installing dub on Debian unstable (tested on x86 and x64) and then
running "dub" errors out immediately with the following error message:

dub: symbol lookup error: dub: undefined symbol: _Dstd5stdio_.
--- End Message ---
--- Begin Message ---
This issue is indeed mysteriously gone now, with GDC 8 and 9.
I can't reproduce it anymore, so the only thing left to do is fix up
the affected packages by simply rebuilding them.

Cheers,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/--- End Message ---


Bug#939065: BD on python-rdkit which isn't build anymore and isn't in bullseye

2019-08-31 Thread Paul Gevers
Source: cinfony
Version: 1.2-3
Severity: serious
Tags: ftbfs sid bullseye
Control: found -1 1.2-4

Recently the rdkit package has stopped building the python-rdkit
package. This is an issue for your package as it build-depends on it.

Unfortunately the migration software doesn't detected this kind of
situation yet, so your package also FTBFS in bullseye since 2019-08-15.
The package is still available in unstable as cruft.

Paul



signature.asc
Description: OpenPGP digital signature


Bug#939066: libodsstream-qt5-dev: depends on dropped libquazip-dev

2019-08-31 Thread Jonathan Wiltshire
Package: libodsstream-qt5-dev
Version: 0.7.0-2
Severity: serious
Tags: bullseye sid
Justification: will become uninstallable

Hi,

libodsstream-qt5-dev depends on the dropped package libquazip-dev, which
will be removed soon as part of the libquazip transition. Binary
packages cannot be cleaned up in testing until libodsstream's
dependencies are updated, presumably to libquazip5-dev.

Thanks,

-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 
'oldstable-updates'), (500, 'unstable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libodsstream-qt5-dev depends on:
pn  libodsstream-qt5-0  
pn  libquazip-dev   

libodsstream-qt5-dev recommends no packages.

libodsstream-qt5-dev suggests no packages.



Processed: BD on python-rdkit which isn't build anymore and isn't in bullseye

2019-08-31 Thread Debian Bug Tracking System
Processing control commands:

> found -1 1.2-4
Bug #939065 [src:cinfony] BD on python-rdkit which isn't build anymore and 
isn't in bullseye
Marked as found in versions cinfony/1.2-4.

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



Bug#875051: [netanim] Future Qt4 removal from Buster

2019-08-31 Thread Moritz Mühlenhoff
On Sat, Sep 09, 2017 at 10:12:23PM +0200, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Source: netanim
> Version: 3.100-1
> Severity: wishlist
> User: debian-qt-...@lists.debian.org
> Usertags: qt4-removal
> 
> Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> as [announced] in:

Hi YinQiang,
3.108 supports Qt5, are you planning to upload that version? Otherwise I'll
file a removal bug.

Cheers,
Moritz



Bug#933077: marked as done (/usr/lib/nodejs/tslib vs /usr/share/nodejs/tslib breaking node-rollup-plugin-typescript)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 18:21:36 +
with message-id 
and subject line Bug#933077: fixed in node-typescript 3.6.2-1
has caused the Debian Bug report #933077,
regarding /usr/lib/nodejs/tslib vs /usr/share/nodejs/tslib breaking 
node-rollup-plugin-typescript
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.)


-- 
933077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-tslib, node-typescript, node-rollup-plugin-typescript
Severity: serious
Justification: breaks node-rollup-plugin-typescript

In last upload of node-tslib, location was changed from /usr/lib/nodejs to 
/usr/share/nodejs. This broke node-rollup-plugin-typescript as it was trying to 
load 'tslib/tslib.es6.js'

While running rollup from node-sourcemap-codec it failed

praveen@mahishasura:~/forge/node-sourcemap-codec$ rollup -c 
[!] Error: Cannot find module 'tslib/tslib.es6.js' from 
'/usr/lib/nodejs/rollup-plugin-typescript/dist' 
Error: Cannot find module 'tslib/tslib.es6.js' from 
'/usr/lib/nodejs/rollup-plugin-typescript/dist' 
at Function.module.exports [as sync] 
(/usr/lib/nodejs/resolve/lib/sync.js:40:15)at typescript 
(/usr/lib/nodejs/rollup-plugin-typescript/dist/rollup-plugin-typescript.cjs.js:109:29)
at Object. 
(/home/praveen/forge/node-sourcemap-codec/rollup.config.js:13:3)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.require.extensions..js (/usr/lib/nodejs/rollup/bin/rollup:582:7)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:22:18)

It worked after adding a symlink to /usr/share/nodejs/tslib from 
/usr/lib/nodejs/rollup-plugin-typescript/node_modules.

I'm not sure if that is the right fix. Ideas?

Shouldn't node-typescript also move tslib to /usr/share/nodejs? 
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.--- End Message ---
--- Begin Message ---
Source: node-typescript
Source-Version: 3.6.2-1

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

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

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated node-typescript 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, 31 Aug 2019 19:03:10 +0200
Source: node-typescript
Architecture: source
Version: 3.6.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Julien Puydt 
Closes: 933077
Changes:
 node-typescript (3.6.2-1) unstable; urgency=medium
 .
   * Move tslib to /usr/share (Closes: #933077).
   * New upstream release.
   * Move everything to /usr/share according to new policy.
   * Update overrides
Checksums-Sha1:
 d83a3628fc4d1bc25bea45830d66a9002207d8a9 2059 node-typescript_3.6.2-1.dsc
 cfa3c23b9a4a69f2dc0179d81e42a3f9742ca5b0 26640477 
node-typescript_3.6.2.orig.tar.gz
 28da7c05c88d2e47ae835595f3954d98e251b6b5 6100 
node-typescript_3.6.2-1.debian.tar.xz
 ec7350e9f709047c3bc33512051ac69c1e0cc0e6 5947 
node-typescript_3.6.2-1_source.buildinfo
Checksums-Sha256:
 308fb03c674f93e612a4a1b52ac7f363c3ecb3b0c28a79f0a3e60f25377cc27e 2059 
node-typescript_3.6.2-1.dsc
 107c842c573dea02a4f40d6d54952f056818455d205ec9ec672c45a8fc5d85b6 26640477 
node-typescript_3.6.2.orig.tar.gz
 a6fb25defc5a0f23abfeb1ef7b3c5e080a2791b6ade44231e18667c552b3f408 6100 
node-typescript_3.6.2-1.debian.tar.xz
 d0114e75bf215de1bd13879bd969776096054803f7557a9bed62a3a019129af0 5947 
node-typescript_3.6.2-1_source.buildinfo
Files:
 665bd7537e4a2acb77b357724a9f6ac8 2059 javascript optional 
node-typescript_3.6.2-1.dsc
 24e6b6e0401bd90c095550cc3a68ae64 26640477 javascript optional 
node-typescript_3.6.2.orig.tar.gz
 31084f840

Processed: affects 938221

2019-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> affects 938221 python-turbogears2
Bug #938221 [src:python-toscawidgets] python-toscawidgets: Python2 removal in 
sid/bullseye
Added indication that 938221 affects python-turbogears2
> thanks
Stopping processing here.

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



Processed: severity of 938221 is serious

2019-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 938221 serious
Bug #938221 [src:python-toscawidgets] python-toscawidgets: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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



Bug#933077: marked as pending in node-typescript

2019-08-31 Thread Julien Puydt
Control: tag -1 pending

Hello,

Bug #933077 in node-typescript 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/js-team/node-typescript/commit/6ec246a02e7c1009d6056c9e6bc364d99b51bbe7


Move tslib to /usr/share (Closes: #933077)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/933077



Processed: Bug#933077 marked as pending in node-typescript

2019-08-31 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #933077 [node-tslib, node-typescript, node-rollup-plugin-typescript] 
/usr/lib/nodejs/tslib vs /usr/share/nodejs/tslib breaking 
node-rollup-plugin-typescript
Added tag(s) pending.

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



Processed: Raising severity

2019-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 922978 serious
Bug #922978 [auralquiz] auralquiz: Auralquiz depends on Qt4-based Phonon 
backends instead of Qt5 counterparts
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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



Bug#939022: [#939022] Re: pyresample: autopkgtest failure with PROJ 6 (epsg data file removed)

2019-08-31 Thread Sebastiaan Couwenberg
On 8/31/19 6:58 PM, Antonio Valentino wrote:
> it seems to me that the issue is in basemap rather then pyresample.

basemap most likely also needs to be updated to support PROJ 6
correctly, as pretty much everything using PROJ should.

> As far as I can understand it has been already fixed [1,2] in the latest
> version of basemap (1.2.1) which is still not in debian.
> 
> The problem seems to be related to the recent proj/pyproj updates and
> the location of EPSG data. In particular it seems that the "epsg" data
> file used by basemap was provided by proj-data v5.2.0 but is no longer
> in the new version. Is it correct?

The init files like epsg are not longer provided in PROJ 6, this data
moved to the proj.db SQLite database.

Now you shouldn't specify the init file when doing a transformation.

An example from the proj-rdnap test suite, for PROJ <= 5 it does:

 cs2cs -r +init=epsg:4258 +to +init=rdnap:rdnap -f %.4f

For PROJ 6 it does:

 cs2cs EPSG:4937 +to EPSG:7415 -f %.4f

Note that EPSG:4937 is the 3D equivalent of EPSG:4258. The epsg & rdnap
init files are no longer used, instead the projection database is used.

> I'm going to reassign.

That doesn't seem appropriate, pyresample needs to be updated too. It
does things like this:

 pyresample/test/test_geometry.py:
projections = {'+init=epsg:3006': 'init: epsg:3006'}

Note the explicit use of init files, this is not going to work correctly
with PROJ 6.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



Bug#875095: marked as done ([phonon] Future Qt4 removal from Buster)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 17:10:52 +
with message-id 
and subject line Bug#875095: fixed in phonon 4:4.10.3-3
has caused the Debian Bug report #875095,
regarding [phonon] Future Qt4 removal from 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.)


-- 
875095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: phonon
Version: 4:4.9.0-4
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: phonon
Source-Version: 4:4.10.3-3

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

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
phonon package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 31 Aug 2019 13:35:27 -0300
Source: phonon
Architecture: source
Version: 4:4.10.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Closes: 875095
Changes:
 phonon (4:4.10.3-3) unstable; urgency=medium
 .
   * Drop Qt 4 support (Closes: #875095).
   * Bump debhelper compat to 12.
 - Pass --fail-missing to dh_missing instead of dh_install.
   * Drop debconf translations for phonon-backend-null and set up translations
 for phonon4qt5-backend-null.
Checksums-Sha1:
 59671cdc80d27aab72b181ac15d87656e0f32145 2626 phonon_4.10.3-3.dsc
 c9c5d7511b8a2ba1ce1320f5ae32e7b80a76d523 27248 phonon_4.10.3-3.debian.tar.xz
 95a7c4316d1a7acdc0493aa9628c01df281a0b53 12590 phonon_4.10.3-3_source.buildinfo
Checksums-Sha256:
 6ef5478c0057e27d25f32ba2baeac824d320f0b859dce7171deff19f2e0784b9 2626 
phonon_4.10.3-3.dsc
 d871abd8d87514fe736381ff20c293cbe795e9a18465e9956bac64ca2a8489a9 27248 
phonon_4.10.3-3.debian.tar.xz
 0fade95f4228f12d2e96602f847101ca2d8b1c7180ac24da6d1fe66cc969b65a 12590 
phonon_4.10.3-3_source.buildinfo
Files:
 6e34db843be070072b9d85dd66dbaa13 2626 sound optional phonon_4.10.3-3.dsc
 6934586078f49bbeea2a6467a006da18 27248 sound optional 
phonon_4.10.3-3.debian.tar.xz
 8f8004ecd945a79abf18eb335fe962c7 12590 sound optional 
phonon_4.10.3-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEEt36hKwjsrvwSzE8q2R

Bug#939022: [#939022] Re: pyresample: autopkgtest failure with PROJ 6 (epsg data file removed)

2019-08-31 Thread Antonio Valentino
Dear Bas,
it seems to me that the issue is in basemap rather then pyresample.
As far as I can understand it has been already fixed [1,2] in the latest
version of basemap (1.2.1) which is still not in debian.

The problem seems to be related to the recent proj/pyproj updates and
the location of EPSG data. In particular it seems that the "epsg" data
file used by basemap was provided by proj-data v5.2.0 but is no longer
in the new version. Is it correct?

I'm going to reassign.

@sandro probably you are busy with other packages in this period so, if
it is OK for you, I could take in charge of updating the basemap package
on salsa (not sure I have push permissions anyway). You should only take
care of reviewing/upload since I'm not a DD/DM.


[1] https://github.com/matplotlib/basemap/pull/454
[2] https://github.com/matplotlib/basemap/issues/458


kind regards
antonio

On Sat, 31 Aug 2019 11:52:33 +0200 Bas Couwenberg 
wrote:
> Source: pyresample
> Version: 1.12.3-5
> Severity: serious
> Justification: makes the package in question unusable or mostly so
> Control: block 931949 by -1
> 
> Dear Maintainer,
> 
> Since the upgrade to proj (6.1.1-1) the autopkgtest of your package
> fails:
> 
>  https://ci.debian.net/packages/p/pyresample/unstable/amd64/
> 
> The log show that basemap tries to use the epsg data file which was
> removed in PROJ 6:
> 
>  autopkgtest [12:38:14]: test python3: [---
>  === python3.7 ===
>  Traceback (most recent call last):
>File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main
>  "__main__", mod_spec)
>File "/usr/lib/python3.7/runpy.py", line 85, in _run_code
>  exec(code, run_globals)
>File "/usr/lib/python3.7/unittest/__main__.py", line 18, in 
>  main(module=None)
>File "/usr/lib/python3.7/unittest/main.py", line 100, in __init__
>  self.parseArgs(argv)
>File "/usr/lib/python3.7/unittest/main.py", line 147, in parseArgs
>  self.createTests()
>File "/usr/lib/python3.7/unittest/main.py", line 159, in createTests
>  self.module)
>File "/usr/lib/python3.7/unittest/loader.py", line 220, in 
> loadTestsFromNames
>  suites = [self.loadTestsFromName(name, module) for name in names]
>File "/usr/lib/python3.7/unittest/loader.py", line 220, in 
>  suites = [self.loadTestsFromName(name, module) for name in names]
>File "/usr/lib/python3.7/unittest/loader.py", line 154, in 
> loadTestsFromName
>  module = __import__(module_name)
>File "/usr/lib/python3/dist-packages/pyresample/test/__init__.py", line 
> 26, in 
>  from pyresample.test import (
>File "/usr/lib/python3/dist-packages/pyresample/test/test_plot.py", line 
> 31, in 
>  from mpl_toolkits.basemap import Basemap
>File "/usr/lib/python3/dist-packages/mpl_toolkits/basemap/__init__.py", 
> line 152, in 
>  epsgf = open(os.path.join(pyproj.pyproj_datadir,'epsg'))
>  AttributeError: module 'pyproj' has no attribute 'pyproj_datadir'
>  autopkgtest [12:38:16]: test python3: ---]
>  autopkgtest [12:38:16]: test python3:  - - - - - - - - - - results - - - - - 
> - - - - -
>  python3  FAIL non-zero exit status 1
> 
> Please fix or remove the autopkgtest in your package.
> 
> Kind Regards,
> 
> Bas
> 
> 

-- 
Antonio Valentino



Processed: Reassign #939022

2019-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 939022 basemap
Bug #939022 [src:pyresample] pyresample: autopkgtest failure with PROJ 6 (epsg 
data file removed)
Bug reassigned from package 'src:pyresample' to 'basemap'.
No longer marked as found in versions pyresample/1.12.3-5.
Ignoring request to alter fixed versions of bug #939022 to the same values 
previously set
> affects 939022 + pyresample
Bug #939022 [basemap] pyresample: autopkgtest failure with PROJ 6 (epsg data 
file removed)
Added indication that 939022 affects pyresample
> thanks
Stopping processing here.

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



Processed: severity of 938258 is serious

2019-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 938258 serious
Bug #938258 [src:python-webflash] python-webflash: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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



Bug#935496: Fails to install: Invalid action '-p'

2019-08-31 Thread GCS
Hi,

On Fri, Aug 30, 2019 at 12:03 PM Simon McVittie  wrote:
> On Fri, 23 Aug 2019 at 10:04:28 +0200, Michael Biebl wrote:
> > Setting up fuse (2.9.9-1) ...
> > dpkg: error processing package fuse (--configure):
> >  installed fuse package post-installation script subprocess returned error 
> > exit status 1
> ...
> > # udevadm test --action -p /devices/virtual/misc/fuse
> > Invalid action '-p'
 Ouch, it's a leftover (outdated lines) from the time when fuse
installed its udev rules. Now it should be something like this:
"udevadm test --action=change /devices/virtual/misc/fuse".
But now as udev ships its fuse rules (in 50-udev-default.rules and
99-systemd.rules) this is not needed anymore.

> Similar to the equivalent fuse3 bug #934293, this seems to be a regression
> since buster: the same binary package installs OK on buster. Maybe
> udevadm became more strict about its parameter parsing?
 As mentioned elsewhere, this seems to be the case. About the the
transition, it is expected but I would like to get more information on
it.

> Similar to fuse3, it would be helpful if the maintainer script had less
> "> /dev/null 2>&1" so that error messages would appear.
 Well, the expected output (on my Buster system) is 131 lines long.
These are not relevant for normal users / usage.

> > I'm not exactly sure what this code is supposed to achieve.
> > Since fuse no longer ships its own udev rules, maybe it can be dropped
> > altogether?
 Trigger an udev rules change after the package installed its udev rule.

> Or if the postinst is still necessary, maybe fuse3 could take over the
> fuse binary package name for bullseye (with a transitional package) so that
> bugs like this one don't need to be fixed in both places?
 For the time I will fix it independently. I can't promise when the
actual transition will take place.
But if you can, please check the proposed package update[1].

Thanks,
Laszlo/GCS
[1] dget -x http://www.barcikacomp.hu/gcs/fuse_2.9.9-2.dsc



Processed: affects 938258

2019-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> affects 938258 python-turbogears2
Bug #938258 [src:python-webflash] python-webflash: Python2 removal in 
sid/bullseye
Added indication that 938258 affects python-turbogears2
> thanks
Stopping processing here.

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



Processed: forcibly merging 935447 938121, user debian-pyt...@lists.debian.org, usertagging 935447

2019-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forcemerge 935447 938121
Bug #935447 [src:python-raven] Please drop the Python 2 subpackage
Bug #935447 [src:python-raven] Please drop the Python 2 subpackage
Added tag(s) sid and bullseye.
Bug #938121 [src:python-raven] python-raven: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
938103 was blocked by: 938121 938255
938103 was not blocking any bugs.
Removed blocking bug(s) of 938103: 938121
Removed indication that 938121 affects src:pytest-xdist
Merged 935447 938121
> user debian-pyt...@lists.debian.org
Setting user to debian-pyt...@lists.debian.org (was w...@debian.org).
> usertags 935447 py2removal py2leaf py3available
There were no usertags set.
Usertags are now: py3available py2removal py2leaf.
> thanks
Stopping processing here.

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



Processed: forcibly merging 935438 936291, user debian-pyt...@lists.debian.org, usertagging 935438

2019-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forcemerge 935438 936291
Bug #935438 [src:chaussette] Please update to Python 3 or remove
Bug #936291 [src:chaussette] chaussette: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
Bug #935438 [src:chaussette] Please update to Python 3 or remove
Added tag(s) bullseye and sid.
Merged 935438 936291
> user debian-pyt...@lists.debian.org
Setting user to debian-pyt...@lists.debian.org (was w...@debian.org).
> usertags 935438 py2removal py2leaf py2rm
There were no usertags set.
Usertags are now: py2leaf py2rm py2removal.
> thanks
Stopping processing here.

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



Bug#935300: rsyslog: FTBFS on s390x

2019-08-31 Thread Michael Biebl
Am 31.08.19 um 16:43 schrieb Michael Biebl:
> So instead I tried reverting the following commit which was in the vicinity:
> 
> commit 7ad178cea388dd1ffc9ac17ae2fecae32c8443b3
> Author: Rainer Gerhards 
> Date:   Wed Jul 31 11:36:27 2019 +0200
> 
> omfile bugfix: race file when async writing is enabled
> 
> This seems to be a long-standing bug, introduced around 7 years ago.
> It became more visible by properly closing files during HUP, which
> was done in 8.1905.0 (and was another bugfix).
> 
> closes https://github.com/rsyslog/rsyslog/issues/3772
> 
> And tada, with that one reverted, asynwr_deadlock2 passes again on the
> s390x porterbox.

Bad news is, with that commit reverted, now the following two tests fail
(at least on the s390x porter machine)

gzipwr_hup_multi_file
gzipwr_hup_single_file



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



signature.asc
Description: OpenPGP digital signature


Processed: fixed 924966 in 4.2.0-1

2019-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 924966 4.2.0-1
Bug #924966 {Done: Christian Hofstaedtler } [src:pdns] pdns: 
CVE-2019-3871: Insufficient validation in the HTTP remote backend
Marked as fixed in versions pdns/4.2.0-1.
> thanks
Stopping processing here.

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



Bug#935300: rsyslog: FTBFS on s390x

2019-08-31 Thread Michael Biebl
On Wed, 21 Aug 2019 19:27:34 +0200 Rainer Gerhards
 wrote:
> I had a look but to me it seems we actually run out file handles. No
> failure indication.
>   
> Is this run in parallel? If so, how many tasks?
> 

I'm running the test-suite with the --no-parallel option, so no parallel
tests.
It seems to be the asynwr_deadlock2 test which fails.

I can reproduce this issue on a s390x porter machine by simply executing
the test

git bisect points at the following as the first faulty commit:

967b7eac17b601c773ee46017eed03cedf14be8d is the first bad commit
commit 967b7eac17b601c773ee46017eed03cedf14be8d
Merge: 2a33b2877 0b2477a9f
Author: Rainer Gerhards 
Date:   Wed Jul 31 11:35:48 2019 +0200

Merge pull request #3780 from rgerhards/i3760

imrelp bugfix: hang after HUP

 plugins/imrelp/imrelp.c | 7 +--
 runtime/glbl.c  | 2 +-
 runtime/glbl.h  | 1 +
 3 files changed, 7 insertions(+), 3 deletions(-)

That doesn't look related immediately so I was wondering if git bisect
got a bit confused by the merge history.

So instead I tried reverting the following commit which was in the vicinity:

commit 7ad178cea388dd1ffc9ac17ae2fecae32c8443b3
Author: Rainer Gerhards 
Date:   Wed Jul 31 11:36:27 2019 +0200

omfile bugfix: race file when async writing is enabled

This seems to be a long-standing bug, introduced around 7 years ago.
It became more visible by properly closing files during HUP, which
was done in 8.1905.0 (and was another bugfix).

closes https://github.com/rsyslog/rsyslog/issues/3772

And tada, with that one reverted, asynwr_deadlock2 passes again on the
s390x porterbox.

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



signature.asc
Description: OpenPGP digital signature


Bug#930363: marked as done (faad2: fix build with gcc-9 [patch])

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 14:39:08 +
with message-id 
and subject line Bug#930363: fixed in faad2 2.8.8-3.2
has caused the Debian Bug report #930363,
regarding faad2: fix build with gcc-9 [patch]
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.)


-- 
930363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: faad2
Version: 2.8.8-3
Severity: normal
tags: patch

Hello, looks like gcc-9 is adding wl,asneeded flag in compilation, so libs 
passed as CFLAGS are not correctly
used by gcc anymore, because only LIBS is added at the end of the compilation 
line.

The following patch fixes the issue, and starts then using again the glib 
implementation of the library.
(without the patch, the bundled version is used everywhere, and the build fails 
only on i386 because of an implementation mismatch of a long/int data type)

I reported the patch already upstream
https://sourceforge.net/p/faac/bugs/242/


patch: 
http://launchpadlibrarian.net/427773869/faad2_2.8.8-3_2.8.8-3ubuntu1.diff.gz


please apply if possible, thanks!

Gianfranco
>From b9e6b9bf906c8c2c6fabf7255bcf9eceff96023b Mon Sep 17 00:00:00 2001
From: Gianfranco Costamagna 
Date: Tue, 11 Jun 2019 14:54:38 +0200
Subject: [PATCH] Add patch to fix a gcc-9 build failure on i386 and to
 correctly use lprintf from glibc

---
 debian/changelog   |  6 ++
 debian/patches/gcc-9.patch | 26 ++
 debian/patches/series  |  1 +
 3 files changed, 33 insertions(+)
 create mode 100644 debian/patches/gcc-9.patch

diff --git a/debian/changelog b/debian/changelog
index dfa8217..c1267f4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+faad2 (2.8.8-4) UNRELEASED; urgency=medium
+
+  * Fix build with gcc-9 and asneeded flag on i386.
+
+ -- Gianfranco Costamagna   Tue, 11 Jun 2019 14:41:09 +0200
+
 faad2 (2.8.8-3) unstable; urgency=high
 
   * Team upload.
diff --git a/debian/patches/gcc-9.patch b/debian/patches/gcc-9.patch
new file mode 100644
index 000..e17a3a3
--- /dev/null
+++ b/debian/patches/gcc-9.patch
@@ -0,0 +1,26 @@
+Description: Fix link failure with gcc-9 and wl,asneeded flags
+Author: Gianfranco Costamagna 
+Last-Update: 2019-06-11
+
+--- faad2-2.8.8.orig/configure.ac
 faad2-2.8.8/configure.ac
+@@ -91,8 +91,8 @@ AC_DEFUN([AC_C99_FUNC_LRINTF],
+ [AC_CACHE_CHECK(for lrintf,
+   ac_cv_c99_lrintf,
+ [
+-lrintf_save_CFLAGS=$CFLAGS
+-CFLAGS="-O -lm"
++lrintf_save_LIBS=$LIBS
++LIBS="-O -lm"
+ AC_TRY_LINK([
+ #define _ISOC9X_SOURCE  1
+ #define _ISOC99_SOURCE  1
+@@ -102,7 +102,7 @@ AC_TRY_LINK([
+ #include 
+ ], if (!lrintf(3.14159)) lrintf(2.7183);, ac_cv_c99_lrintf=yes, ac_cv_c99_lrintf=no)
+ 
+-CFLAGS=$lrintf_save_CFLAGS
++LIBS=$lrintf_save_LIBS
+ 
+ ])
+ 
diff --git a/debian/patches/series b/debian/patches/series
index 6d4062f..f35c884 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -2,3 +2,4 @@ reproducible-build.patch
 0009-syntax.c-check-for-syntax-element-inconsistencies.patch
 0010-sbr_hfadj-sanitize-frequency-band-borders.patch
 0004-Fix-a-couple-buffer-overflows.patch
+gcc-9.patch
-- 
2.17.1

--- End Message ---
--- Begin Message ---
Source: faad2
Source-Version: 2.8.8-3.2

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

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

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

Debian distribution maintenance software
pp.
Hugo Lefeuvre  (supplier of updated faad2 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, 31 Aug 2019 09:11:54 -0400
Source: faad2
Architecture: source
Version: 2.8.8-3.2
Distribution: unstable
Urgency: high
Maintainer: Debian Multimedia Maintainers 
Changed-By: Hugo Lefeuvre 
Closes: 930363
Changes:
 faad2 (2.8.8-3.2) unstable; urgency=high
 .
   * Non-maintainer upload with maintainer's permission.
   * debian/patches/gcc-9.patch: Fix build with GCC-9 (thanks Gianfranco
 Costamagna for the patch) (Closes: #930363).
Checksums-Sha1:
 17a42b0b015655b6ee5a7409f593c5647db7cf70 1928 faad2_2.8.8-3.2.dsc
 529fade97c2d2d0960b5725c73fe18

Bug#938931: marked as done (python-cpuset: missing Breaks+Replaces: cpuset (<< 1.6))

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 14:37:17 +
with message-id 
and subject line Bug#938931: fixed in cpuset 1.6-2
has caused the Debian Bug report #938931,
regarding python-cpuset: missing Breaks+Replaces: cpuset (<< 1.6)
to be marked as done.

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

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


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

Hi,

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

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

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

  Preparing to unpack .../python-cpuset_1.6-1_all.deb ...
  Unpacking python-cpuset (1.6-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-cpuset_1.6-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/python2.7/dist-packages/cpuset/__init__.py', 
which is also in package cpuset 1.5.6-5.1
  Errors were encountered while processing:
   /var/cache/apt/archives/python-cpuset_1.6-1_all.deb


cheers,

Andreas


cpuset=1.5.6-5.1_python-cpuset=1.6-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: cpuset
Source-Version: 1.6-2

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

Debian distribution maintenance software
pp.
Roberto C. Sanchez  (supplier of updated cpuset 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, 31 Aug 2019 10:17:35 -0400
Source: cpuset
Architecture: source
Version: 1.6-2
Distribution: unstable
Urgency: medium
Maintainer: Roberto C. Sanchez 
Changed-By: Roberto C. Sanchez 
Closes: 938931
Changes:
 cpuset (1.6-2) unstable; urgency=medium
 .
   * Add Replaces/Breaks to fix upgrades from earlier version (Closes: #938931)
Checksums-Sha1:
 e3da3c3a38a8088eb99586c307e51a350b0c4dd6 1862 cpuset_1.6-2.dsc
 7d35bef70401ed75b6e6e916b84cc31584d1743c 3536 cpuset_1.6-2.debian.tar.xz
 87ba6e305bda63c8f579cf2cafcd6444feb21e57 7244 cpuset_1.6-2_amd64.buildinfo
Checksums-Sha256:
 d49c261b4df3c44b95ba3e0f91eb8ef21e6c0187ebbba2b9b97569cf8cd7a64b 1862 
cpuset_1.6-2.dsc
 1475735cce4cc088571b0bf32f4d0acf3f33fb7a552b7464dff026204735220d 3536 
cpuset_1.6-2.debian.tar.xz
 9d8b6f2081143952a0c56bf46fc8ec911d7f00c078549c11d4352beeebc0357c 7244 
cpuset_1.6-2_amd64.buildinfo
Files:
 60cfd51d6842c05e9ff7ef813391fc64 1862 utils optional cpuset_1.6-2.dsc
 b746286cfa74ac3890729aa51d709d95 3536 utils optional cpuset_1.6-2.debian.tar.xz
 ebdf5aba5b5c895cc0aaee3331c0cbd1 7244 utils optional 
cpuset_1.6-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEz9ERzDttUsU/BH8iLNd4Xt2nsg8FAl1qgogACgkQLNd4Xt2n
sg9JgQ/+LB1qOXAicxZOnSoyIpXTD7JGYhc3/Mz2xCjP+V49x4vp5RxZrvyy0lKn
Z8JmvkKihelaDaZ//xAtWv1hHrx6e+Jy6WJcnCL5Fsr7xWeaNsv82KfQozM7K+AR
TQ/hBfaB6PrraKG01iy0+Mt60B5SuDxC6a1lpXjrRtAYtB5XYY9Jo3/w3RZCRrTe
uCNkR5sQP0cd3pacEitvNLEg/gyMnJ+gvudaXhPxrVFICqbVJfsDGhIRq0RiFQfX
ibttUJ90HHz/pIh2MOyHrguNFQhbYLxvpxzCCNKPXgnurItn1n7osgw/gO+MFzvz
K1zVeHvQvk0v/SZnPhiCmVctG7Ui6OBE48rQ/stB8JGP2TtV6yhX2qnLax2e6Mse
fHcBsekVRt0bmWR/niPtQcEBNY5Hna5XrVCDEMbxvlENHjc9C+YGSPSNtpZKnxSu
CRSmSyu4oRsZ3CiehVRZw1DcDeOfZ/1nHTmc3e+2TkOIfBdtzfRK1BrOjxr50wi1
w9VNqj8t8tUf0XMVgX5JGjxz7RWc7RjLpQOitNC1by0S9EcXbO25D1Sul9GV4o+r
AlG4XkeTx+JXCXDB47/O4d/UD/OWulN0qEThsRWBmlQX+hjGoUzjO4CRsBt/p939
E0tkolSXNFJKQQd/ZEqawaeHHt6uPCVp5nZi1eAKugZqD+YWurc=
=WqBT
-END PGP SIGNATURE End Message ---


Bug#939044: ocrmypdf: autopkgtest not compatible with new pikepdf, ghostscript and/or pytest

2019-08-31 Thread Jonas Smedegaard
Thanks, Paul,

Quoting Paul Gevers (2019-08-31 15:25:04)
> With a recent upload of pikepdf and with a recent upload of 
> ghostscript and with a recent upload of pytest (althought that pulls 
> in the others) the autopkgtest of ocrmypdf fails in testing when that 
> autopkgtest is run with the binary packages of those packages from 
> unstable. It passes when run with only packages from testing. In 
> tabular form, e.g.:
>passfail
> pikepdffrom testing1.6.1+dfsg-1
> ocrmypdf   from testing8.0.1+dfsg-1
> all others from testingfrom testing
> 
> I copied some of the output at the bottom of this report.

Possibly some of the other tools uses undocumented insecure ghostscript 
calls which was recently removed.

To investigate that further, someone needs to extract the actual input 
(probably Postscript or PDF) and the exact command used to call 
ghostscript.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


Bug#939045: mypy: autopkgtest needs update for new version of lxml

2019-08-31 Thread Paul Gevers
Source: mypy
Version: 0.720-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, l...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:lxml

Dear maintainers,

With a recent upload of lxml the autopkgtest of mypy fails in testing
when that autopkgtest is run with the binary packages of lxml from
unstable. It passes when run with only packages from testing. In tabular
form:
   passfail
lxml   from testing4.4.1-1
mypy   from testing0.720-2
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of lxml to testing
[1]. Of course, lxml shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in lxml was
intended and your package needs to update to the new situation. Please
reassign to lxml when I judged this wrong.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=lxml

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mypy/2854351/log.gz

=== FAILURES
===
___ CoberturaReportSuite.test_as_xml
___
[gw1] linux -- Python 3.7.4 /usr/bin/python3

self = 

def test_as_xml(self) -> None:
cobertura_package = CoberturaPackage('foobar')
cobertura_package.covered_lines = 21
cobertura_package.total_lines = 42

child_package = CoberturaPackage('raz')
child_package.covered_lines = 10
child_package.total_lines = 10
child_package.classes['class'] = etree.Element('class')

cobertura_package.packages['raz'] = child_package

expected_output = textwrap.dedent('''\

  
  

  

  

  

''').encode('ascii')
assert_equal(expected_output,
>etree.tostring(cobertura_package.as_xml(),
pretty_print=True))

/usr/lib/python3/dist-packages/mypy/test/testreports.py:40:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _

a = b'\n  \n  \n\n  \n\n
\n\n  \n\n'
b = b'\n  \n  \n\n  \n\n
\n\n  \n\n'
fmt = '{} != {}'

def assert_equal(a: object, b: object, fmt: str = '{} != {}') -> None:
if a != b:
>   raise AssertionError(fmt.format(good_repr(a), good_repr(b)))
E   AssertionError: b'\n  \n  \n
\n  \n\n
\n\n  \n\n' != b'\n
\n  \n\n  \n\n
 \n\n  \n\n'

/usr/lib/python3/dist-packages/mypy/test/helpers.py:349: AssertionError




signature.asc
Description: OpenPGP digital signature


Processed: mypy: autopkgtest needs update for new version of lxml

2019-08-31 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 src:lxml
Bug #939045 [src:mypy] mypy: autopkgtest needs update for new version of lxml
Added indication that 939045 affects src:lxml

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



Processed: ocrmypdf: autopkgtest not compatible with new pikepdf, ghostscript and/or pytest

2019-08-31 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 src:pikepdf
Bug #939044 [src:ocrmypdf] ocrmypdf: autopkgtest not compatible with new 
pikepdf, ghostscript and/or pytest
Added indication that 939044 affects src:pikepdf
> affects -1 src:ghostscript
Bug #939044 [src:ocrmypdf] ocrmypdf: autopkgtest not compatible with new 
pikepdf, ghostscript and/or pytest
Added indication that 939044 affects src:ghostscript
> affects -1 src:pytest
Bug #939044 [src:ocrmypdf] ocrmypdf: autopkgtest not compatible with new 
pikepdf, ghostscript and/or pytest
Added indication that 939044 affects src:pytest

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



Bug#939044: ocrmypdf: autopkgtest not compatible with new pikepdf, ghostscript and/or pytest

2019-08-31 Thread Paul Gevers
Source: ocrmypdf
Version: 8.0.1+dfsg-1
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:pikepdf
Control: affects -1 src:ghostscript
Control: affects -1 src:pytest

[X-Debbugs-CC: debian...@lists.debian.org, pike...@packages.debian.org,
ghostscr...@packages.debian.org, pyt...@packages.debian.org]

Dear maintainers,

With a recent upload of pikepdf and with a recent upload of ghostscript
and with a recent upload of pytest (althought that pulls in the others)
the autopkgtest of ocrmypdf fails in testing when that autopkgtest is
run with the binary packages of those packages from unstable. It passes
when run with only packages from testing. In tabular form, e.g.:
   passfail
pikepdffrom testing1.6.1+dfsg-1
ocrmypdf   from testing8.0.1+dfsg-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of pikepdf,
ghostscript and pytest to testing [1]. Because failure is triggered by
two packages separately, I filed the bug against ocrmypdf, please
reassign (and clone) if that wasn't correct.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=pikepdf

https://ci.debian.net/data/autopkgtest/testing/amd64/o/ocrmypdf/2854254/log.gz

=== FAILURES
===
___ test_non_square_resolution[hocr]
___

renderer = 'hocr'
spoof_tesseract_cache = {'ADTTMP':
'/tmp/autopkgtest-lxc._q0vjo65/downtmp/autopkgtest_tmp',
'ADT_ARTIFACTS':
'/tmp/autopkgtest-lxc._q0vjo65/do...q0vjo65/downtmp/test-suite-artifacts',
'AUTOPKGTEST_TMP':
'/tmp/autopkgtest-lxc._q0vjo65/downtmp/autopkgtest_tmp', ...}
resources =
PosixPath('/tmp/autopkgtest-lxc._q0vjo65/downtmp/build.Oxe/src/tests/resources')
outpdf =
'/tmp/pytest-of-debci/pytest-0/test_non_square_resolution_hoc0/out.pdf'

@pytest.mark.parametrize('renderer', RENDERERS)
def test_non_square_resolution(renderer, spoof_tesseract_cache,
resources, outpdf):
# Confirm input image is non-square resolution
in_pageinfo = PdfInfo(resources / 'aspect.pdf')
assert in_pageinfo[0].xres != in_pageinfo[0].yres

check_ocrmypdf(
resources / 'aspect.pdf',
outpdf,
'--pdf-renderer',
renderer,
>   env=spoof_tesseract_cache,
)

tests/test_main.py:481:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _

input_file =
PosixPath('/tmp/autopkgtest-lxc._q0vjo65/downtmp/build.Oxe/src/tests/resources/aspect.pdf')
output_file =
'/tmp/pytest-of-debci/pytest-0/test_non_square_resolution_hoc0/out.pdf'
env = {'ADTTMP':
'/tmp/autopkgtest-lxc._q0vjo65/downtmp/autopkgtest_tmp',
'ADT_ARTIFACTS':
'/tmp/autopkgtest-lxc._q0vjo65/do...q0vjo65/downtmp/test-suite-artifacts',
'AUTOPKGTEST_TMP':
'/tmp/autopkgtest-lxc._q0vjo65/downtmp/autopkgtest_tmp', ...}
args = ('--pdf-renderer', 'hocr')
p = , out = ''

@pytest.helpers.register
def check_ocrmypdf(input_file, output_file, *args, env=None):
"Run ocrmypdf and confirmed that a valid file was created"

p, out, err = run_ocrmypdf(input_file, output_file, *args, env=env)
# ensure py.test collects the output, use -s to view
print(err, file=sys.stderr)
>   assert p.returncode == 0
E   assert 15 == 0
E+  where 15 = .returncode

tests/conftest.py:155: AssertionError
- Captured stderr call
-
   INFO -1: [tesseract] Tesseract cache folder
/tmp/autopkgtest-lxc._q0vjo65/downtmp/build.Oxe/src/tests/cache/aspect/__-l__eng__01.ocr.png__01__hocr__txt
- HIT
  ERROR - Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/ruffus/task.py", line 712, in
run_pooled_job_without_exceptions
register_cleanup, touch_files_only)
  File "/usr/lib/python3/dist-packages/ruffus/task.py", line 544, in
job_wrapper_io_files
ret_val = user_defined_work_func(*params)
  File "/usr/lib/python3/dist-packages/ocrmypdf/_pipeline.py", line 827,
in convert_to_pdfa
pdf_layers_file.save(layers_file)
ValueError: Cannot overwrite input file


_ test_non_square_resolution[sandwich]
_

renderer = 'sandwich'
spoof_tesseract_cache = {'ADTTMP':
'/tmp/autopkgtest-lxc._q0vjo65/downtmp/autopkgtest_tmp',
'ADT_ARTIFACTS':
'/tmp/autopkgtest-lxc._q0vjo65/do...q0vjo65/downtmp/test-suite-artifacts',
'AUTOPKGTEST_TMP':
'/tmp/autopkgtest-lxc._q0vjo65/downtmp/autopkgtest_tmp', ...}
resources =
PosixPath('/tmp/autopkgtest-lxc._q0vjo65/downtmp/build.Oxe/src/tests/resources')
outpdf =
'/tmp/pytest-of-debci/pytest-0/test_non_square_resolution_san0/out.pd

Bug#924712: crypt() not available _XOPEN_SOURCE is defined

2019-08-31 Thread Francesco Poli
On Sat, 31 Aug 2019 15:04:06 +0200 Aurelien Jarno wrote:

> On 2019-08-25 15:51, Francesco Poli wrote:
> > On Sun, 25 Aug 2019 13:46:36 +0200 Florian Weimer wrote:
> > 
> > > * Francesco Poli:
> > > 
> > > > Hello everyone,
> > > > I am sorry to ask, but... I cannot understand what's the status of
> > > > [this bug report].
> > > >
> > > > [this bug report]: 
> > > >
> > > > A serious bug for libc6-dev without any apparent activity since last
> > > > March?  Sure there must have been some hidden progress that I cannot
> > > > see.
> > > 
> > > We provided a solution acceptable to the reporter.  I do not think
> > > further action is needed on the glibc side.  The manual page needs to
> > > be updated to reflect the change, but that's not part of glibc.
> > 
> > OK, good.
> > Thanks for your prompt reply!
> > 
> > Why is the bug report being kept open, though?
> > Should it be reassigned to package manpages-dev and fixed there?
> 
> manpages-dev doesn't provide the manpage for crypt(3) anymore.

Oops, I hadn't noticed that.
Thanks a lot for clarifying!

> It is now
> provided by libcrypt2-dev. The crypt functions are getting removed from
> the glibc and will be provided by this external library. I guess we'll
> do the transition after getting glibc 2.29 into unstable.
> 
> As the version provided by libcrypt2-dev doesn't have the reported
> issue, I am closing the bug.

Good, thanks for stepping in!

Bye.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpU_s0RH54Qx.pgp
Description: PGP signature


Bug#935496: Fails to install: Invalid action '-p'

2019-08-31 Thread Michael Biebl
On Fri, 30 Aug 2019 18:57:11 +0200 Michael Biebl  wrote:
> Am 30.08.19 um 11:04 schrieb Simon McVittie:
> > Control: tags -1 + bullseye sid
> > 
> > On Fri, 23 Aug 2019 at 10:04:28 +0200, Michael Biebl wrote:
> >> Setting up fuse (2.9.9-1) ...
> >> dpkg: error processing package fuse (--configure):
> >>  installed fuse package post-installation script subprocess returned error 
> >> exit status 1
> > ...
> >> # udevadm test --action -p /devices/virtual/misc/fuse
> >> Invalid action '-p'
> > 
> > Similar to the equivalent fuse3 bug #934293, this seems to be a regression
> > since buster: the same binary package installs OK on buster. Maybe
> > udevadm became more strict about its parameter parsing?
> 
> I'm currently investigating, whether this is a regression in udevadm or not

Quoting upstream
https://github.com/systemd/systemd/issues/13442#issuecomment-526688796

> I do not think it is an our bug, but the bug in the script used in the 
> install script of fuse. udevadm test does not support -p, and --action option 
> requires argument. Also, of course, -p is not a valid action.



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



signature.asc
Description: OpenPGP digital signature


Bug#936069: marked as done (virtualenvwrapper-doc: missing Breaks+Replaces: virtualenvwrapper (<< 4.8))

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 13:10:50 +
with message-id 
and subject line Bug#936069: fixed in virtualenvwrapper 4.8.4-3
has caused the Debian Bug report #936069,
regarding virtualenvwrapper-doc: missing Breaks+Replaces: virtualenvwrapper (<< 
4.8)
to be marked as done.

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

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


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

Hi,

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

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

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

  Preparing to unpack .../virtualenvwrapper-doc_4.8.4-1_all.deb ...
  Unpacking virtualenvwrapper-doc (4.8.4-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/virtualenvwrapper-doc_4.8.4-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/doc/virtualenvwrapper/html/_static/ajax-loader.gif', which is also 
in package virtualenvwrapper 4.3.1-2
  Errors were encountered while processing:
   /var/cache/apt/archives/virtualenvwrapper-doc_4.8.4-1_all.deb


cheers,

Andreas


virtualenvwrapper=4.3.1-2_virtualenvwrapper-doc=4.8.4-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: virtualenvwrapper
Source-Version: 4.8.4-3

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

Debian distribution maintenance software
pp.
Jan Dittberner  (supplier of updated virtualenvwrapper 
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, 31 Aug 2019 14:17:10 +0200
Source: virtualenvwrapper
Architecture: source
Version: 4.8.4-3
Distribution: unstable
Urgency: medium
Maintainer: Jan Dittberner 
Changed-By: Jan Dittberner 
Closes: 729306 760080 805877 933822 936069 938786
Changes:
 virtualenvwrapper (4.8.4-3) unstable; urgency=medium
 .
   * Re-upload to unstable
 .
 virtualenvwrapper (4.8.4-2) experimental; urgency=medium
 .
   * add Breaks/Replaces virtualenvwrapper (<< 4.8) to virtualenvwrapper-doc
 and python3-virtualenvwrapper (Closes: #936069)
   * upload to unstable without Python2 support (Closes: #938786)
 .
 virtualenvwrapper (4.8.4-1) experimental; urgency=medium
 .
   [ Joel Cross ]
   * Add Python 3 support by splitting into multiple packages (Closes: #760080)
   * Bump Debhelper and standards version
   * Build using pybuild
   * Update Vcs-Git/Vcs-Browser fields in d/control
   * Patches: Correctly decode bytestring in fix-python3-sphinx-build.patch
   * Patches: Actually remove shebang in
 remove-virtualenvwrapper_lazy-shebang.patch
 .
   [ Ondřej Nový ]
   * d/copyright: Change Format URL to correct one
   * Use 'python3 -m sphinx' instead of sphinx-build for building docs
 .
   [ Nicholas D Steeves ]
   * d/control: Drop python-virtualenvwrapper, the Python 2 variant of this
 package which depends on cruft package python-stevedore (Closes: #933822)
   * d/rules: Drop operations on non-existent python-virtualenvwrapper.
   * d/control: Drop python2 dependencies.
   * d/rules: No longer build "--with python2".
   * d/README.Debian: Debian's virtualenv package now supports Python 3, so
 drop misleading info that says otherwise.
   * Add 0004-Use-Python-3-everywhere.patch; Fixes ftbfs caused by the py2 drop.
 .
   [ Jan Dittberner ]
   * New upstream version (Closes: #729306, #805877)
   * fix previous changelog entry's bug number
   * refresh patches
   * Install wrapper scripts via dh_install
   * Adapt debian/watch to new pypi.org
   * remove unusable upstream signing key
   * use macros from /usr/share/dpkg/pkg-info.mk instead of parsing dpkg-
 parsechan

Bug#933822: marked as done (virtualenvwrapper depends on cruft package python-stevedore)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 13:10:50 +
with message-id 
and subject line Bug#933822: fixed in virtualenvwrapper 4.8.4-3
has caused the Debian Bug report #933822,
regarding virtualenvwrapper depends on cruft package python-stevedore
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.)


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

Package: virtualenvwrapper
Severity: serious
Version: 4.3.1-2
Tags: bullseye, sid

virtualenvwapper depends on python-stevedore which is no longer built by 
the stevedore source package.
--- End Message ---
--- Begin Message ---
Source: virtualenvwrapper
Source-Version: 4.8.4-3

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

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

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

Debian distribution maintenance software
pp.
Jan Dittberner  (supplier of updated virtualenvwrapper 
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, 31 Aug 2019 14:17:10 +0200
Source: virtualenvwrapper
Architecture: source
Version: 4.8.4-3
Distribution: unstable
Urgency: medium
Maintainer: Jan Dittberner 
Changed-By: Jan Dittberner 
Closes: 729306 760080 805877 933822 936069 938786
Changes:
 virtualenvwrapper (4.8.4-3) unstable; urgency=medium
 .
   * Re-upload to unstable
 .
 virtualenvwrapper (4.8.4-2) experimental; urgency=medium
 .
   * add Breaks/Replaces virtualenvwrapper (<< 4.8) to virtualenvwrapper-doc
 and python3-virtualenvwrapper (Closes: #936069)
   * upload to unstable without Python2 support (Closes: #938786)
 .
 virtualenvwrapper (4.8.4-1) experimental; urgency=medium
 .
   [ Joel Cross ]
   * Add Python 3 support by splitting into multiple packages (Closes: #760080)
   * Bump Debhelper and standards version
   * Build using pybuild
   * Update Vcs-Git/Vcs-Browser fields in d/control
   * Patches: Correctly decode bytestring in fix-python3-sphinx-build.patch
   * Patches: Actually remove shebang in
 remove-virtualenvwrapper_lazy-shebang.patch
 .
   [ Ondřej Nový ]
   * d/copyright: Change Format URL to correct one
   * Use 'python3 -m sphinx' instead of sphinx-build for building docs
 .
   [ Nicholas D Steeves ]
   * d/control: Drop python-virtualenvwrapper, the Python 2 variant of this
 package which depends on cruft package python-stevedore (Closes: #933822)
   * d/rules: Drop operations on non-existent python-virtualenvwrapper.
   * d/control: Drop python2 dependencies.
   * d/rules: No longer build "--with python2".
   * d/README.Debian: Debian's virtualenv package now supports Python 3, so
 drop misleading info that says otherwise.
   * Add 0004-Use-Python-3-everywhere.patch; Fixes ftbfs caused by the py2 drop.
 .
   [ Jan Dittberner ]
   * New upstream version (Closes: #729306, #805877)
   * fix previous changelog entry's bug number
   * refresh patches
   * Install wrapper scripts via dh_install
   * Adapt debian/watch to new pypi.org
   * remove unusable upstream signing key
   * use macros from /usr/share/dpkg/pkg-info.mk instead of parsing dpkg-
 parsechangelog output
   * Update debian/control and debian/copyright
   * d/control: run wrap-and-sort
   * Switch to debhelper 12 compatibility
   * d/control: bump Standards-Version to 4.4.0 (no changes)
   * Refresh patches, drop d/patches/fix-python3-sphinx-build.patch
   * update d/patches/0004-Use-Python-3-everywhere.patch to use Python 3
 in virtualenvwrapper.sh
Checksums-Sha1:
 a86f7f5d366ce635e0edd856103378c7a642 1944 virtualenvwrapper_4.8.4-3.dsc
 43a8ac97858cfcbdc394b24cb6dde2ad0ccb2324 8300 
virtualenvwrapper_4.8.4-3.debian.tar.xz
 34498eab0af980991ddea65bcf461e6d013fafab 5474 
virtualenvwrapper_4.8.4-3_source.buildinfo
Checksums-Sha256:
 e030afce64f2835a75406fb50a84a2bae6870b3c6a30371738a8daf43581a977 1944 
virtualenvwrapper_4.8.4-3.dsc
 3edd154fd15783b68720e7e7fa8c950adc99ddfc37f12d5342e4da614f64d336 8300 
virtualenvwrapper_4.8.4-3.debian.tar.xz
 918160ad2f53983ff3d3e03a1a8544aeb1c52abd10ccfe0bceae8813492a 5474 
virtualenvwrapper_4.8.4-3_source.buildinfo
F

Bug#924712: marked as done (crypt() not available _XOPEN_SOURCE is defined)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 15:04:06 +0200
with message-id <20190831130406.ga31...@aurel32.net>
and subject line Re: Bug#924712: crypt() not available _XOPEN_SOURCE is defined
has caused the Debian Bug report #924712,
regarding crypt() not available _XOPEN_SOURCE is defined
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.)


-- 
924712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-dev
Version: 2.28-8
Severity: serious

Hi,

The crypt.3 manpage, state that _XOPEN_SOURCE should be define for
crypt() to be available.

But it looks that it's currently the opposite, if _XOPEN_SOURCE is
defined, the function cannot be found.

This actually looks like a regression compared to stretch.

Regards,
Laurent Bigonville

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

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

Versions of packages manpages-dev depends on:
ii  manpages  4.16-1

manpages-dev recommends no packages.

Versions of packages manpages-dev suggests:
ii  man-db [man-browser]  2.8.5-2

-- no debconf information
--- End Message ---
--- Begin Message ---
On 2019-08-25 15:51, Francesco Poli wrote:
> On Sun, 25 Aug 2019 13:46:36 +0200 Florian Weimer wrote:
> 
> > * Francesco Poli:
> > 
> > > Hello everyone,
> > > I am sorry to ask, but... I cannot understand what's the status of
> > > [this bug report].
> > >
> > > [this bug report]: 
> > >
> > > A serious bug for libc6-dev without any apparent activity since last
> > > March?  Sure there must have been some hidden progress that I cannot
> > > see.
> > 
> > We provided a solution acceptable to the reporter.  I do not think
> > further action is needed on the glibc side.  The manual page needs to
> > be updated to reflect the change, but that's not part of glibc.
> 
> OK, good.
> Thanks for your prompt reply!
> 
> Why is the bug report being kept open, though?
> Should it be reassigned to package manpages-dev and fixed there?

manpages-dev doesn't provide the manpage for crypt(3) anymore. It is now
provided by libcrypt2-dev. The crypt functions are getting removed from
the glibc and will be provided by this external library. I guess we'll
do the transition after getting glibc 2.29 into unstable.

As the version provided by libcrypt2-dev doesn't have the reported
issue, I am closing the bug.

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


signature.asc
Description: PGP signature
--- End Message ---


Processed: reopening 796536, reopening 925662, reopening 918229, reopening 927104, reopening 929754 ...

2019-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reopen 796536
Bug #796536 {Done: Debian FTP Masters } 
[src:criu] criu: package not yet ready for stable release / fast moving 
(blocking bug)
'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 3.8.1-1+rm.
> reopen 925662
Bug #925662 {Done: Debian FTP Masters } 
[src:criu] criu: ftbfs with GCC-9
'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 3.8.1-1+rm.
> reopen 918229
Bug #918229 {Done: Debian FTP Masters } 
[src:criu] criu: FTBFS building for armhf on arm64
'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 3.8.1-1+rm.
> reopen 927104
Bug #927104 {Done: Debian FTP Masters } [criu] 
criu: Please update to python3
'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 3.8.1-1+rm.
> reopen 929754
Bug #929754 {Done: Debian FTP Masters } [criu] 
Restoration failures due to PID increment rates.
'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 3.8.1-1+rm.
> reopen 782007
Bug #782007 {Done: Debian FTP Masters } 
[src:criu] criu: Split up binary packages
'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 3.8.1-1+rm.
> reopen 844290
Bug #844290 {Done: Debian FTP Masters } [criu] 
criu FTBFS if source directory has a tilde in it
'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 3.8.1-1+rm.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
782007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782007
796536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796536
844290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844290
918229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918229
925662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925662
927104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927104
929754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929754
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#939040: srt: CVE-2019-15784

2019-08-31 Thread Salvatore Bonaccorso
Source: srt
Version: 1.3.2-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/Haivision/srt/pull/811

Hi,

The following vulnerability was published for srt.

CVE-2019-15784[0]:
| Secure Reliable Transport (SRT) through 1.3.4 has a CSndUList array
| overflow if there are many SRT connections.


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-2019-15784
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15784
[1] https://github.com/Haivision/srt/pull/811

Regards,
Salvatore



Processed: merging 939038 939039

2019-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> merge 939038 939039
Bug #939038 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS 
with libvpx6
Bug #939039 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS 
with libvpx6
Bug #939039 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS 
with libvpx6
Merged 939038 939039
> thanks
Stopping processing here.

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



Bug#935794: xfce4-sntray-plugin FTBFS

2019-08-31 Thread Jonathan Wiltshire
On Fri, Aug 30, 2019 at 06:14:10AM +, mike.gabr...@das-netzwerkteam.de 
wrote:
> Hi,
> 
> Am Donnerstag, 29. August 2019 schrieb peter green:
> > It looks like that class was dropped from vala-panel in 
> > https://gitlab.com/vala-panel-project/vala-panel/commit/87493a6dfab9868f77b7b19b57fca40a06fe80af
> > 
> > Unfortunately the commit message doesn't give any clues to what if-anything 
> > it should be replaced with.
> > 
> > If a proper fix cannot be found then one option would be to drop the 
> > vala-panel support from this package. The popcon figures for the vala-panel 
> > variant are the lowest of any of the variants. 
> > https://qa.debian.org/popcon.php?package=xfce4-sntray-plugin . I decided to 
> > go ahead and do that in raspbian for the moment to complete the transition 
> > there.
> > 
> > A debdiff should appear soon at 
> > https://debdiffs.raspbian.org/main/x/xfce4-sntray-plugin . No intent to NMU 
> > in Debian.
> > 
> > There does seem to be some upstream activity on xfce4-sntray-plugin at 
> > https://github.com/rilian-la-te/xfce4-sntray-plugin but I can't find 
> > anything relavent to this issue.
> > 
> 
> I hope that upstream makes a new release soon, see
> https://gitlab.com/vala-panel-project/xfce4-sntray-plugin/issues/34
> 
> In the past, Konstantin has been really quick with such requests.

Seems to be fixed in 
https://gitlab.com/vala-panel-project/xfce4-sntray-plugin/-/tags/0.4.12

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



Processed: Merge 939038 939039

2019-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> merge 939038 939039
Bug #939038 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS 
with libvpx6
Bug #939039 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS 
with libvpx6
Merged 939038 939039
> thanks
Stopping processing here.

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



Processed: bug 935794 is forwarded to https://gitlab.com/vala-panel-project/xfce4-sntray-plugin/issues/34 ...

2019-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 935794 
> https://gitlab.com/vala-panel-project/xfce4-sntray-plugin/issues/34
Bug #935794 [src:xfce4-sntray-plugin] xfce4-sntray-plugin FTBFS
Set Bug forwarded-to-address to 
'https://gitlab.com/vala-panel-project/xfce4-sntray-plugin/issues/34'.
> tags 935794 + fixed-upstream
Bug #935794 [src:xfce4-sntray-plugin] xfce4-sntray-plugin FTBFS
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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



Bug#933822: marked as done (virtualenvwrapper depends on cruft package python-stevedore)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 12:25:08 +
with message-id 
and subject line Bug#933822: fixed in virtualenvwrapper 4.8.4-2
has caused the Debian Bug report #933822,
regarding virtualenvwrapper depends on cruft package python-stevedore
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.)


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

Package: virtualenvwrapper
Severity: serious
Version: 4.3.1-2
Tags: bullseye, sid

virtualenvwapper depends on python-stevedore which is no longer built by 
the stevedore source package.
--- End Message ---
--- Begin Message ---
Source: virtualenvwrapper
Source-Version: 4.8.4-2

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

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

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

Debian distribution maintenance software
pp.
Jan Dittberner  (supplier of updated virtualenvwrapper 
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, 31 Aug 2019 13:55:48 +0200
Source: virtualenvwrapper
Architecture: source
Version: 4.8.4-2
Distribution: experimental
Urgency: medium
Maintainer: Jan Dittberner 
Changed-By: Jan Dittberner 
Closes: 729306 760080 805877 933822 936069 938786
Changes:
 virtualenvwrapper (4.8.4-2) experimental; urgency=medium
 .
   * add Breaks/Replaces virtualenvwrapper (<< 4.8) to virtualenvwrapper-doc
 and python3-virtualenvwrapper (Closes: #936069)
   * upload to unstable without Python2 support (Closes: #938786)
 .
 virtualenvwrapper (4.8.4-1) experimental; urgency=medium
 .
   [ Joel Cross ]
   * Add Python 3 support by splitting into multiple packages (Closes: #760080)
   * Bump Debhelper and standards version
   * Build using pybuild
   * Update Vcs-Git/Vcs-Browser fields in d/control
   * Patches: Correctly decode bytestring in fix-python3-sphinx-build.patch
   * Patches: Actually remove shebang in
 remove-virtualenvwrapper_lazy-shebang.patch
 .
   [ Ondřej Nový ]
   * d/copyright: Change Format URL to correct one
   * Use 'python3 -m sphinx' instead of sphinx-build for building docs
 .
   [ Nicholas D Steeves ]
   * d/control: Drop python-virtualenvwrapper, the Python 2 variant of this
 package which depends on cruft package python-stevedore (Closes: #933822)
   * d/rules: Drop operations on non-existent python-virtualenvwrapper.
   * d/control: Drop python2 dependencies.
   * d/rules: No longer build "--with python2".
   * d/README.Debian: Debian's virtualenv package now supports Python 3, so
 drop misleading info that says otherwise.
   * Add 0004-Use-Python-3-everywhere.patch; Fixes ftbfs caused by the py2 drop.
 .
   [ Jan Dittberner ]
   * New upstream version (Closes: #729306, #805877)
   * fix previous changelog entry's bug number
   * refresh patches
   * Install wrapper scripts via dh_install
   * Adapt debian/watch to new pypi.org
   * remove unusable upstream signing key
   * use macros from /usr/share/dpkg/pkg-info.mk instead of parsing dpkg-
 parsechangelog output
   * Update debian/control and debian/copyright
   * d/control: run wrap-and-sort
   * Switch to debhelper 12 compatibility
   * d/control: bump Standards-Version to 4.4.0 (no changes)
   * Refresh patches, drop d/patches/fix-python3-sphinx-build.patch
   * update d/patches/0004-Use-Python-3-everywhere.patch to use Python 3
 in virtualenvwrapper.sh
Checksums-Sha1:
 a7f4afcc11a491234a9b134c57fdd43090202296 1944 virtualenvwrapper_4.8.4-2.dsc
 691508b5f5bb1dbb6ba7085b2f481cde310f7905 8272 
virtualenvwrapper_4.8.4-2.debian.tar.xz
 8224d6d006e57a4bbb710af6f8d8e6470110edd1 5474 
virtualenvwrapper_4.8.4-2_source.buildinfo
Checksums-Sha256:
 69f68ca09c6fd93e4f569a03cc085aa07767f2ca20567678bc65506713872d12 1944 
virtualenvwrapper_4.8.4-2.dsc
 dc193f00cf0c113f0858b6d9ddfa27249c5abbfb30f3c74ba2b854b68d5ef722 8272 
virtualenvwrapper_4.8.4-2.debian.tar.xz
 6467ad3bbfbfa943fc8452dc2e0820ad212456c3439ef27ca9e2b1fe564e4e30 5474 
virtualenvwrapper_4.8.4-2_source.buildinfo
Files:
 5888562605023aeeeb54e63b8568e5ca 1944 python optional 
virtualenvwrapper_4.8

Bug#935563: marked as done (astropy 3.2.1 breaks sunpy)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 14:24:37 +0200
with message-id <34321db2-05aa-31e0-c1ce-423245d0d...@debian.org>
and subject line astropy 3.2.1 breaks sunpy
has caused the Debian Bug report #935563,
regarding astropy 3.2.1 breaks sunpy
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.)


-- 
935563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: astropy
Version: 3.2.1-1
Severity: serious
Justification: autopkgtest regressions block migration
Affects: sunpy/0.9.6-2
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan autopkgtest

Hi Ole,

The sunpy autopkgtests fail with new astropy 3.2.1-1, and considering the
failing autopkgtest is one specifically intended to test an error-prone
astropy transformation (according to the comments), this looks to me like it
may be a genuine regression in astropy that's caught by sunpy:

[...]
=== FAILURES ===
 test_hgs_hcrs _

def test_hgs_hcrs():
# This test checks the HGS->HCRS transformation by transforming from 
HGS to
# HeliocentricTrueEcliptic (HTE).  It will fail if there are errors in 
Astropy's
# HCRS->ICRS or ICRS->HTE transformations.

# Use published HGS coordinates in the Astronomical Almanac (2013), 
pages C6-C7
obstime = Time('2013-01-28')
earth_hgs = SkyCoord(0*u.deg, -5.73*u.deg, 0.9848139*u.AU, 
frame=HeliographicStonyhurst,
 obstime=obstime)

# Transform to HTE at observation-time equinox
earth_hte = 
earth_hgs.transform_to(HeliocentricTrueEcliptic(equinox=obstime))

# Validate against published values from the Astronomical Almanac 
(2013), page C6 per page E2
# The dominant source of inaccuracy is the limited precision of the 
published B0 used above
>   assert quantity_allclose(earth_hte.lon, Angle('308d13m30.51s') - 
> 180*u.deg, atol=5*u.arcsec)
E   assert False
E+  where False = quantity_allclose(, 
( - (180 * Unit("deg"))), atol=(5 * Unit("arcsec")))
E+where  = .lon
E+and= Angle('308d13m30.51s')
E+and   Unit("deg") = u.deg
E+and   Unit("arcsec") = u.arcsec

/usr/lib/python3/dist-packages/sunpy/coordinates/tests/test_transformations.py:146:
 AssertionError
[...]

(https://ci.debian.net/data/autopkgtest/testing/amd64/s/sunpy/2801123/log.gz)

Opening a bug so that this is documented in the BTS (and so it can be
reassigned if I'm wrong about which package is to blame).

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.0.3-1

This problem is fixed in the new upstream version of sunpy
(but was not marked in d/changelog).



Format: 1.8
Date: Thu, 29 Aug 2019 20:28:30 +0200
Source: sunpy
Architecture: source
Version: 1.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Ole Streicher 
Closes: 934959
Changes:
 sunpy (1.0.3-1) unstable; urgency=medium
 .
   * New upstream version 1.0.3. Rediff patches. Closes: #934959
   * Update dependencies
   * Push Standards-Version to 4.4.0. No changes required
   * Push compat to 12. Remove d/compat
   * Remove unused paragraph from d/copyright
Checksums-Sha1:
 716efc289568a457af6149e5c598b990144bb285 2628 sunpy_1.0.3-1.dsc
 f382359b7e9b5353b5cd366afcdae2d4305a09af 6615391 sunpy_1.0.3.orig.tar.gz
 3d76edbffd259b1b69dab5ed686800b22f44f5f9 5856 sunpy_1.0.3-1.debian.tar.xz
Checksums-Sha256:
 3c508cadbaf53e364ed476433ec442ee15ffe42ab31122345ad73da71761289b 2628 
sunpy_1.0.3-1.dsc
 0fd75a8ee4d6527f990beb2424be4ac97aad1f166cae449d9ac9fb00179db0a0 6615391 
sunpy_1.0.3.orig.tar.gz
 c24af2a9e19481e4d84d2a9129c2ff51a356816114953aa9344ca547abe3730b 5856 
sunpy_1.0.3-1.debian.tar.xz
Files:
 094b83423583c1424eae661055accace 2628 python optional sunpy_1.0.3-1.dsc
 5e11306c64faac3492f4f0941ff6fab1 6615391 python optional 
sunpy_1.0.3.orig.tar.gz
 0948c89163b3aafe44a2fb0e7edff75b 5856 python optional 
sunpy_1.0.3-1.debian.tar.xz--- End Message ---


Bug#936069: marked as done (virtualenvwrapper-doc: missing Breaks+Replaces: virtualenvwrapper (<< 4.8))

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 12:25:08 +
with message-id 
and subject line Bug#936069: fixed in virtualenvwrapper 4.8.4-2
has caused the Debian Bug report #936069,
regarding virtualenvwrapper-doc: missing Breaks+Replaces: virtualenvwrapper (<< 
4.8)
to be marked as done.

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

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


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

Hi,

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

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

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

  Preparing to unpack .../virtualenvwrapper-doc_4.8.4-1_all.deb ...
  Unpacking virtualenvwrapper-doc (4.8.4-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/virtualenvwrapper-doc_4.8.4-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/doc/virtualenvwrapper/html/_static/ajax-loader.gif', which is also 
in package virtualenvwrapper 4.3.1-2
  Errors were encountered while processing:
   /var/cache/apt/archives/virtualenvwrapper-doc_4.8.4-1_all.deb


cheers,

Andreas


virtualenvwrapper=4.3.1-2_virtualenvwrapper-doc=4.8.4-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: virtualenvwrapper
Source-Version: 4.8.4-2

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

Debian distribution maintenance software
pp.
Jan Dittberner  (supplier of updated virtualenvwrapper 
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, 31 Aug 2019 13:55:48 +0200
Source: virtualenvwrapper
Architecture: source
Version: 4.8.4-2
Distribution: experimental
Urgency: medium
Maintainer: Jan Dittberner 
Changed-By: Jan Dittberner 
Closes: 729306 760080 805877 933822 936069 938786
Changes:
 virtualenvwrapper (4.8.4-2) experimental; urgency=medium
 .
   * add Breaks/Replaces virtualenvwrapper (<< 4.8) to virtualenvwrapper-doc
 and python3-virtualenvwrapper (Closes: #936069)
   * upload to unstable without Python2 support (Closes: #938786)
 .
 virtualenvwrapper (4.8.4-1) experimental; urgency=medium
 .
   [ Joel Cross ]
   * Add Python 3 support by splitting into multiple packages (Closes: #760080)
   * Bump Debhelper and standards version
   * Build using pybuild
   * Update Vcs-Git/Vcs-Browser fields in d/control
   * Patches: Correctly decode bytestring in fix-python3-sphinx-build.patch
   * Patches: Actually remove shebang in
 remove-virtualenvwrapper_lazy-shebang.patch
 .
   [ Ondřej Nový ]
   * d/copyright: Change Format URL to correct one
   * Use 'python3 -m sphinx' instead of sphinx-build for building docs
 .
   [ Nicholas D Steeves ]
   * d/control: Drop python-virtualenvwrapper, the Python 2 variant of this
 package which depends on cruft package python-stevedore (Closes: #933822)
   * d/rules: Drop operations on non-existent python-virtualenvwrapper.
   * d/control: Drop python2 dependencies.
   * d/rules: No longer build "--with python2".
   * d/README.Debian: Debian's virtualenv package now supports Python 3, so
 drop misleading info that says otherwise.
   * Add 0004-Use-Python-3-everywhere.patch; Fixes ftbfs caused by the py2 drop.
 .
   [ Jan Dittberner ]
   * New upstream version (Closes: #729306, #805877)
   * fix previous changelog entry's bug number
   * refresh patches
   * Install wrapper scripts via dh_install
   * Adapt debian/watch to new pypi.org
   * remove unusable upstream signing key
   * use macros from /usr/share/dpkg/pkg-info.mk instead of parsing dpkg-
 parsechangelog output
   * Update debian/control and debian/copyright
   * d/control: run wr

Bug#935883: marked as done (Socket activation disabled and daemon timing out after 120s)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 12:22:49 +
with message-id 
and subject line Bug#935883: fixed in libvirt 5.6.0-2
has caused the Debian Bug report #935883,
regarding Socket activation disabled and daemon timing out after 120s
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.)


-- 
935883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvirt-daemon-system
Version: 5.6.0-1
Severity: serious

Hello,

So apparently libvirtd socket activation has been disabled in this
release because it's "broken upstream" but the daemon is still started
with "--timeout 120" meaning that after 2 min the daemon become
unreachable without anything automatically restarting it.

So either the socket activation must be fixed or the timeout should be
temporarily removed until it's fixed

Kind regards,

Laurent Bigonville

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

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

Versions of packages libvirt-daemon-system depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.73
ii  firewalld  0.7.1-1
ii  gettext-base   0.19.8.1-9
ii  init-system-helpers1.57
ii  iptables   1.8.3-2
ii  libc6  2.28-10
ii  libvirt-clients5.6.0-1
ii  libvirt-daemon 5.6.0-1
ii  libvirt0   5.6.0-1
ii  libxml22.9.4+dfsg1-7+b3
ii  logrotate  3.14.0-4
ii  lsb-base   11.1.0
ii  policykit-10.105-26

Versions of packages libvirt-daemon-system recommends:
ii  dmidecode3.2-2
ii  dnsmasq-base [dnsmasq-base]  2.80-1+b1
ii  iproute2 5.2.0-1
ii  parted   3.2-25+b1

Versions of packages libvirt-daemon-system suggests:
ii  apparmor2.13.3-4
ii  auditd  1:2.8.5-2
pn  nfs-common  
pn  open-iscsi  
pn  pm-utils
pn  radvd   
ii  systemd 242-4
pn  systemtap   
pn  zfsutils

-- Configuration Files:
/etc/default/libvirt-guests changed [not included]
/etc/libvirt/nwfilter/allow-arp.xml [Errno 13] Permission non accordée: 
'/etc/libvirt/nwfilter/allow-arp.xml'
/etc/libvirt/nwfilter/allow-dhcp-server.xml [Errno 13] Permission non accordée: 
'/etc/libvirt/nwfilter/allow-dhcp-server.xml'
/etc/libvirt/nwfilter/allow-dhcp.xml [Errno 13] Permission non accordée: 
'/etc/libvirt/nwfilter/allow-dhcp.xml'
/etc/libvirt/nwfilter/allow-incoming-ipv4.xml [Errno 13] Permission non 
accordée: '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'
/etc/libvirt/nwfilter/allow-ipv4.xml [Errno 13] Permission non accordée: 
'/etc/libvirt/nwfilter/allow-ipv4.xml'
/etc/libvirt/nwfilter/clean-traffic-gateway.xml [Errno 13] Permission non 
accordée: '/etc/libvirt/nwfilter/clean-traffic-gateway.xml'
/etc/libvirt/nwfilter/clean-traffic.xml [Errno 13] Permission non accordée: 
'/etc/libvirt/nwfilter/clean-traffic.xml'
/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml [Errno 13] Permission non 
accordée: '/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml'
/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml [Errno 13] Permission non 
accordée: '/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml'
/etc/libvirt/nwfilter/no-arp-spoofing.xml [Errno 13] Permission non accordée: 
'/etc/libvirt/nwfilter/no-arp-spoofing.xml'
/etc/libvirt/nwfilter/no-ip-multicast.xml [Errno 13] Permission non accordée: 
'/etc/libvirt/nwfilter/no-ip-multicast.xml'
/etc/libvirt/nwfilter/no-ip-spoofing.xml [Errno 13] Permission non accordée: 
'/etc/libvirt/nwfilter/no-ip-spoofing.xml'
/etc/libvirt/nwfilter/no-mac-broadcast.xml [Errno 13] Permission non accordée: 
'/etc/libvirt/nwfilter/no-mac-broadcast.xml'
/etc/libvirt/nwfilter/no-mac-spoofing.xml [Errno 13] Permission non accordée: 
'/etc/libvirt/nwfilter/no-mac-spoofing.xml'
/etc/libvirt/nwfilter/no-other-l2-traffic.xml [Errno 13] Permission non 
accordée: '/etc/libvirt/nwfilter/no-other-l2-traffic.xml'
/etc/libvirt/nwfilter/no-other-rarp-traffic.xml [Errno 13] Permission non 
accordée: '/etc/libvirt/nwfilter/no-other-rarp-traffic.xml'
/etc/libvirt/nwfilter/qemu-announce-self-rarp.xml [Errno 13] Permission non 
accordée: '/etc/libvirt/nwfilter/qemu-announce-self-rarp.xml'
/etc/libvirt/nwfilte

Processed: astropy 3.2.1 breaks sunpy

2019-08-31 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 python3-sunpy 0.9.6-2
Bug #935563 [src:astropy] astropy 3.2.1 breaks sunpy
Bug reassigned from package 'src:astropy' to 'python3-sunpy'.
No longer marked as found in versions astropy/3.2.1-1.
Ignoring request to alter fixed versions of bug #935563 to the same values 
previously set
Bug #935563 [python3-sunpy] astropy 3.2.1 breaks sunpy
Marked as found in versions sunpy/0.9.6-2.

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



Bug#935563: astropy 3.2.1 breaks sunpy

2019-08-31 Thread Ole Streicher
Control: reassign -1 python3-sunpy 0.9.6-2

That is rather an inaccuracy in sunpy, which is fixed with the latest
version.

Cheers

Ole



Bug#939038: qtwebengine-opensource-src: FTBFS with libvpx6

2019-08-31 Thread Jonathan Wiltshire
Source: qtwebengine-opensource-src
Version: 5.11.3+dfsg-2
Severity: serious
Tags: ftbfs bullseye sid
Justification: ftbfs

Hi,

During a rebuild for the libvpx6 transition qtwebengine-opensource-src
failed to build from source. The tail of the log is:

| [6055/15332] /usr/bin/g++ -MMD -MF 
obj/third_party/webrtc/modules/video_coding/webrtc_vp9/vp9_impl.o.d 
-DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 
-DUSE_NSS_CERTS=1 -DUSE_X11=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING 
-DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD 
-DFIELDTRIAL_TESTING_ENABLED -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS 
-D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 
-DWEBRTC_ENABLE_PROTOBUF=1 -DWEBRTC_RESTRICT_LOGGING -DHAVE_SCTP 
-DENABLE_EXTERNAL_AUTH -DHAVE_WEBRTC_VIDEO -DHAVE_WEBRTC_VOICE 
-DLOGGING_INSIDE_WEBRTC -DUSE_WEBRTC_DEV_BRANCH 
-DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 -DFEATURE_ENABLE_VOICEMAIL 
-DGTEST_RELATIVE_PATH -DWEBRTC_CHROMIUM_BUILD -DWEBRTC_POSIX -DWEBRTC_LINUX 
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32 
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -DNO_MAIN_THREAD_WRAPPING -Igen 
-I../../3rdparty/chromium 
-I../../3rdparty/chromium/third_party/webrtc_overrides 
-I../../3rdparty/chromium/third_party/webrtc -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Igen -Igen 
-I../../3rdparty/chromium/third_party/libyuv/include -Igen 
-I../../3rdparty/chromium/third_party/webrtc/common_video/include 
-fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector 
-Wno-builtin-macro-redefined -D__DATE__= -D__TIME__= -D__TIMESTAMP__= 
-funwind-tables -fPIC -pipe -pthread -m64 -Wall -U_FORTIFY_SOURCE 
-D_FORTIFY_SOURCE=2 -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-deprecated-declarations -fno-delete-null-pointer-checks 
-Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident 
-fdata-sections -ffunction-sections -fno-omit-frame-pointer -g0 
-fvisibility=hidden -std=gnu++14 -fno-delete-null-pointer-checks -Wno-narrowing 
-fno-exceptions -fno-rtti -fvisibility-inlines-hidden -c 
../../3rdparty/chromium/third_party/webrtc/modules/video_coding/codecs/vp9/vp9_impl.cc
 -o obj/third_party/webrtc/modules/video_coding/webrtc_vp9/vp9_impl.o
| FAILED: obj/third_party/webrtc/modules/video_coding/webrtc_vp9/vp9_impl.o 
| /usr/bin/g++ -MMD -MF 
obj/third_party/webrtc/modules/video_coding/webrtc_vp9/vp9_impl.o.d 
-DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 
-DUSE_NSS_CERTS=1 -DUSE_X11=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING 
-DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD 
-DFIELDTRIAL_TESTING_ENABLED -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS 
-D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 
-DWEBRTC_ENABLE_PROTOBUF=1 -DWEBRTC_RESTRICT_LOGGING -DHAVE_SCTP 
-DENABLE_EXTERNAL_AUTH -DHAVE_WEBRTC_VIDEO -DHAVE_WEBRTC_VOICE 
-DLOGGING_INSIDE_WEBRTC -DUSE_WEBRTC_DEV_BRANCH 
-DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 -DFEATURE_ENABLE_VOICEMAIL 
-DGTEST_RELATIVE_PATH -DWEBRTC_CHROMIUM_BUILD -DWEBRTC_POSIX -DWEBRTC_LINUX 
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32 
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -DNO_MAIN_THREAD_WRAPPING -Igen 
-I../../3rdparty/chromium 
-I../../3rdparty/chromium/third_party/webrtc_overrides 
-I../../3rdparty/chromium/third_party/webrtc -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Igen -Igen 
-I../../3rdparty/chromium/third_party/libyuv/include -Igen 
-I../../3rdparty/chromium/third_party/webrtc/common_video/include 
-fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector 
-Wno-builtin-macro-redefined -D__DATE__= -D__TIME__= -D__TIMESTAMP__= 
-funwind-tables -fPIC -pipe -pthread -m64 -Wall -U_FORTIFY_SOURCE 
-D_FORTIFY_SOURCE=2 -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-deprecated-declarations -fno-delete-null-pointer-checks 
-Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident 
-fdata-sections -ffunction-sections -fno-omit-frame-pointer -g0 
-fvisibility=hidden -std=gnu++14 -fno-delete-null-pointer-checks -Wno-narrowing 
-fno-exceptions -fno-rtti -fvisibility-inlines-hidden -c 
../../3rdparty/chromium/third_party/webrtc/modules/video_coding/codecs/vp9/vp9_impl.cc
 -o obj/third_party/webrtc/modules/video_coding/webrtc_vp9/vp9_impl.o
| 
../../3rdparty/chromium/third_party/webrtc/modules/video_coding/codecs/vp9/vp9_impl.cc:
 In constructor ‘webrtc::VP9EncoderImpl::VP9EncoderImpl()’:
| 
../../3rdparty/chromium/third_party/webrtc/modules/video_coding/codecs/vp9/vp9_impl.cc:84:36:
 warning: ‘void* memset(void*, int, size_t)’ clearing an object of non-trivial 
type ‘class webrtc::VideoCodec’; use assignment or value-initialization instead 
[-Wclass-memaccess]
|memset(&codec_, 0, sizeof(codec_));
| ^
| In file included from 
../..

Bug#935883: marked as pending in libvirt

2019-08-31 Thread Guido Günther
Control: tag -1 pending

Hello,

Bug #935883 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/4dcbe933607f0ef228d3f89be7eb024857213fb2


Revert "Disable libvirtd socket activation" (Closes: #935883)

Turns out socket activation for libvirtd actually works fine, and
furthermore not having it enabled along with the default timeout
for libvirtd now being 120 seconds results in clients no longer
being able to use libvirt two short minutes after boot.

This reverts commit b8e92da4ff0af742f5de055ace97503c778a8484.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/935883



Processed: fixed 938454 in 1.9.7-0.1~exp1

2019-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 938454 1.9.7-0.1~exp1
Bug #938454 [src:sdaps] sdaps: Python2 removal in sid/bullseye
Marked as fixed in versions sdaps/1.9.7-0.1~exp1.
> thanks
Stopping processing here.

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



Processed: Bug#935883 marked as pending in libvirt

2019-08-31 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #935883 [libvirt-daemon-system] Socket activation disabled and daemon 
timing out after 120s
Added tag(s) pending.

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



Processed: Re: Bug#938454: sdaps: Python2 removal in sid/bullseye

2019-08-31 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #938454 [src:sdaps] sdaps: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> tag -1 bullseye sid ftbfs
Bug #938454 [src:sdaps] sdaps: Python2 removal in sid/bullseye
Added tag(s) ftbfs.

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



Bug#939022: pyresample: autopkgtest failure with PROJ 6 (epsg data file removed)

2019-08-31 Thread Bas Couwenberg
Source: pyresample
Version: 1.12.3-5
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: block 931949 by -1

Dear Maintainer,

Since the upgrade to proj (6.1.1-1) the autopkgtest of your package
fails:

 https://ci.debian.net/packages/p/pyresample/unstable/amd64/

The log show that basemap tries to use the epsg data file which was
removed in PROJ 6:

 autopkgtest [12:38:14]: test python3: [---
 === python3.7 ===
 Traceback (most recent call last):
   File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main
 "__main__", mod_spec)
   File "/usr/lib/python3.7/runpy.py", line 85, in _run_code
 exec(code, run_globals)
   File "/usr/lib/python3.7/unittest/__main__.py", line 18, in 
 main(module=None)
   File "/usr/lib/python3.7/unittest/main.py", line 100, in __init__
 self.parseArgs(argv)
   File "/usr/lib/python3.7/unittest/main.py", line 147, in parseArgs
 self.createTests()
   File "/usr/lib/python3.7/unittest/main.py", line 159, in createTests
 self.module)
   File "/usr/lib/python3.7/unittest/loader.py", line 220, in loadTestsFromNames
 suites = [self.loadTestsFromName(name, module) for name in names]
   File "/usr/lib/python3.7/unittest/loader.py", line 220, in 
 suites = [self.loadTestsFromName(name, module) for name in names]
   File "/usr/lib/python3.7/unittest/loader.py", line 154, in loadTestsFromName
 module = __import__(module_name)
   File "/usr/lib/python3/dist-packages/pyresample/test/__init__.py", line 26, 
in 
 from pyresample.test import (
   File "/usr/lib/python3/dist-packages/pyresample/test/test_plot.py", line 31, 
in 
 from mpl_toolkits.basemap import Basemap
   File "/usr/lib/python3/dist-packages/mpl_toolkits/basemap/__init__.py", line 
152, in 
 epsgf = open(os.path.join(pyproj.pyproj_datadir,'epsg'))
 AttributeError: module 'pyproj' has no attribute 'pyproj_datadir'
 autopkgtest [12:38:16]: test python3: ---]
 autopkgtest [12:38:16]: test python3:  - - - - - - - - - - results - - - - - - 
- - - -
 python3  FAIL non-zero exit status 1

Please fix or remove the autopkgtest in your package.

Kind Regards,

Bas



Processed: pyresample: autopkgtest failure with PROJ 6 (epsg data file removed)

2019-08-31 Thread Debian Bug Tracking System
Processing control commands:

> block 931949 by -1
Bug #931949 [release.debian.org] transition: proj
931949 was blocked by: 931935 931914 931872 931940 939002 931922 931944 931904 
931943 931931 931941 931908 931948 936017 931945
931949 was blocking: 931950
Added blocking bug(s) of 931949: 939022

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



Bug#934838: marked as done (range-v3: FTBFS in sid (error: assignment from temporary initializer_list does not extend the lifetime of the underlying array))

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 09:36:10 +
with message-id 
and subject line Bug#934838: fixed in range-v3 0.9.0-1~exp1
has caused the Debian Bug report #934838,
regarding range-v3: FTBFS in sid (error: assignment from temporary 
initializer_list does not extend the lifetime of the underlying array)
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.)


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

Dear maintainer:

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


[...]
 debian/rules binary-indep
dh binary-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON -DRANGES_NATIVE=OFF 
-DRANGES_VERBOSE_BUILD=ON
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON -DRANGES_NATIVE=OFF 
-DRANGES_VERBOSE_BUILD=ON ..
-- The CXX compiler identification is GNU 9.2.1
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features

[... snipped ...]

cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/test/action 
/<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/test/action 
/<>/obj-x86_64-linux-gnu/test/action/CMakeFiles/act.remove_if.dir/DependInfo.cmake
 --color=
Scanning dependencies of target act.remove_if
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f test/action/CMakeFiles/act.remove_if.dir/build.make 
test/action/CMakeFiles/act.remove_if.dir/build
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 59%] Building CXX object 
test/action/CMakeFiles/act.remove_if.dir/remove_if.cpp.o
cd /<>/obj-x86_64-linux-gnu/test/action && /usr/bin/c++   
-I/<>/include  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-Wno-error=maybe-uninitialized -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG   
-std=c++11 -Wall -Wextra -Werror -fdiagnostics-show-template-tree 
-ftemplate-backtrace-limit=0 -fomit-frame-pointer -Ofast -fstrict-aliasing 
-ffast-math -fsized-deallocation -DRANGES_CXX_ALIGNED_NEW=0 -pedantic 
-pedantic-errors -Wno-padded -Wno-old-style-cast -Wno-shadow -Wno-noexcept-type 
-o CMakeFiles/act.remove_if.dir/remove_if.cpp.o -c 
/<>/test/action/remove_if.cpp
[ 59%] Linking CXX executable act.remove_if
cd /<>/obj-x86_64-linux-gnu/test/action && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/act.remove_if.dir/link.txt --verbose=1
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-Wno-error=maybe-uninitialized -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG  
-Wl,-z,relro CMakeFiles/act.remove_if.dir/remove_if.cpp.o  -o act.remove_if 
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
[ 59%] Built target act.remove_if
make -f test/action/CMakeFiles/act.unstable_remove_if.dir/build.make 
test/action/CMakeFiles/act.unstable_remove_if.dir/depend
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/test/action 
/<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/test/action 
/<>/obj-x86_64-linux-gnu/test/action/CMakeFiles/act.unstable_remove_if.dir/DependInfo.cmake
 --color=
Scanning dependencies of target act.unstable_remove_if
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f test/action/CMakeFiles/act.unstable_remove_if.dir/build.make 
test/action/CMakeFiles/act.unstable_remove_if.dir/build
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 59%] Building CXX object 
test/action/CMakeFiles/act.unstable_remove_if.dir/unstable_remove_if.cpp.o
cd /<>/obj-x86_64-linux-gnu/test/action && /usr/bin/c++   
-I/<>/include  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-Wno-error=maybe-uninitialized -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG   
-std=c+

Bug#874901: [GLE-devel] Probable fix for qgle seg faults with latest ghostscript versions

2019-08-31 Thread Francesco Poli
On Fri, 30 Aug 2019 00:19:08 +0200 Christian T. Steigies wrote:

> On Thu, Aug 29, 2019 at 10:55:28PM +0200, Francesco Poli wrote:
[...]
> > Any specific reason to use a version number (4.2.5-7~exp1) which is
> > actually considered lower than the one currently in Debian unstable
> > (4.2.5-7+b1)?
> 
> Oh, I forgot about the binNMU.

Well, actually, even without the binNMU, the chosen version number
would be considered as a downgrade (because of the tilde):

  $ if dpkg --compare-versions 4.2.5-7 lt 4.2.5-7~exp1 ; then echo yes ; else 
echo no ; fi
  no

> This is not the version that will be uploaded
> to Debian, that will be -8.

Sure!

> I just wanted to give you something to test,
> before I upload, and it should have had a version between 7 and 8. Well, I
> guess you can still test it, since you need to install the deb manually
> anyway.

I grabbed
https://people.debian.org/~cts/deb/gle-graphics_4.2.5-7~exp1.dsc
https://people.debian.org/~cts/deb/gle-graphics_4.2.5-7~exp1.debian.tar.xz
and, after taking a look at the differences with respect to the package
currently in Debian unstable, I fixed the version string and rebuilt
the binary package.

I tested the resulting package: it seems to fix the [dependency on obsolete 
Qt4] bug, the [libgs search] bug, and also the [GUI segfault] bug!

[dependency on obsolete Qt4]: 
[libgs search]: 
[GUI segfault]: 

Please prepare a new Debian revision (4.2.5-8) with these patches and
with appropriate Closes directives in the changelog, and upload it to
unstable!

Of course, I would also like to recommend the upstream developers to
incorporate the (non Debian-specific) patches into the next official
version of GLE.

Thanks for taking care of the package.
Bye!


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpCdc5Ak7yfV.pgp
Description: PGP signature


Processed: bug 935290 is forwarded to https://github.com/rakudo/rakudo/issues/3090

2019-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 935290 https://github.com/rakudo/rakudo/issues/3090
Bug #935290 [src:rakudo] rakudo: FTBFS on amd64
Set Bug forwarded-to-address to 'https://github.com/rakudo/rakudo/issues/3090'.
> thanks
Stopping processing here.

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



Bug#939016: rust-debcargo_2.4.0-1_mipsel.changes REJECTED

2019-08-31 Thread Aurelien Jarno
Package: rust-debcargo
Version: 2.4.0-1
Severity: serious

On 2019-08-29 01:23, Debian FTP Masters wrote:
> debcargo_2.4.0-1_mipsel.deb: Built-Using refers to non-existing source 
> package rust-sized-chunks (= 0.3.1-1+b1)
> 
> 
> Mapping sid to unstable.
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
> 
> 

The Built-Using field is not correct, it should point to the version of
the source package, not the binary one (so no +b1).

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



Bug#935792: libglx-mesa0: error creating symbolic link (missing dependency?)

2019-08-31 Thread Sven Joachim
Control: severity -1 normal
Control: tags -1 unreproducible moreinfo

On 2019-08-26 11:10 +0200, P.H. wrote:

> Package: libglx-mesa0
> Version: 18.3.6-2
> Severity: serious
> Justification: Policy 3.5
>
> Dear Maintainer,
>
> the update from Stretch to Buster failed with
>
>Unpacking libglx-mesa0:amd64 (18.3.6-2) ...
>dpkg: error processing archive 
> /var/cache/apt/archives/libglx-mesa0_18.3.6-2_amd64.deb (--unpack):
> error creating symbolic link 
> './usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0': No such file or directory

That's rather strange, but the diversions below show how it could
happen.

> $ env LANG=C dpkg -S /usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0
> diversion by glx-diversions from: 
> /usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0
> diversion by glx-diversions to: 
> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLX_indirect.so.0
>
> and after installing the 'glx-diversions' package, 'libglx-mesa0' is happy 
> again.

The question is in what state the glx-diversions was before that.
Apparently it was installed due to the reported diversion, but maybe it
was broken.  In particular, apparently there was no
/usr/lib/mesa-diverted/x86_64-linux-gnu directory, that's why dpkg
failed to create the symlink there.  However, that directory is shipped
in the glx-diversions package.

> I am not sure what exactly happened, as my other computers upgraded
> smoothly and while they do have 'libglx-mesa0' installed, they do not
> need the 'glx-diversions' package. I guess the different graphic card
> drivers are to thank for...
>
>
> Anyway, this might only happen in strange environments but since my
> system seems sound, it is definitely a problem.

I don't think your system had been sound when you encountered the
unpacking error.  Installing/upgrading glx-diversions appears to have
fixed it, though.

I tried to reproduce your problem by installing glx-diversions from
stretch in a chroot, then installing libglx-mesa0 from buster.  This
worked just fine, so unless you can give additional information, there's
not much we can do.

Cheers,
   Sven



Bug#935015: Thank you!

2019-08-31 Thread Yaroslav Halchenko
Dear Sandro, Steve, and Peter

Thank you for all the modernization of DataLad package.  Feel welcome to
upload to shorter NMU if desired/needed.  Some of those changes are now
addressed upstream and I will include/ack your NMUs with the next
release of datalad package.

Cheers,
-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik



Processed: Re: Bug#935792: libglx-mesa0: error creating symbolic link (missing dependency?)

2019-08-31 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 normal
Bug #935792 [libglx-mesa0] libglx-mesa0: error creating symbolic link (missing 
dependency?)
Severity set to 'normal' from 'serious'
> tags -1 unreproducible moreinfo
Bug #935792 [libglx-mesa0] libglx-mesa0: error creating symbolic link (missing 
dependency?)
Added tag(s) moreinfo and unreproducible.

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



Bug#935283: marked as done (lua-sec: FTBFS on arm64, armel, armhf, mips64el, mipsel, s390x)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 07:04:54 +
with message-id 
and subject line Bug#935283: fixed in lua-sec 0.8-2
has caused the Debian Bug report #935283,
regarding lua-sec: FTBFS on arm64, armel, armhf, mips64el, mipsel, s390x
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.)


-- 
935283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935283
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:lua-sec
version: 0.8-1
severity: serious
tags: ftbfs

Hi,

A binnmu of lua-sec in unstable fails on arm64, armel, armhf, mips64el, mipsel, 
s390x:

https://buildd.debian.org/status/package.php?p=lua-sec

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: lua-sec
Source-Version: 0.8-2

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

Debian distribution maintenance software
pp.
Sergei Golovan  (supplier of updated lua-sec 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: Fri, 30 Aug 2019 12:30:50 +0300
Source: lua-sec
Architecture: source
Version: 0.8-2
Distribution: unstable
Urgency: medium
Maintainer: Enrico Tassi 
Changed-By: Sergei Golovan 
Closes: 935283
Changes:
 lua-sec (0.8-2) unstable; urgency=medium
 .
   * Team upload
   * Fix cleanup after a test run (closes: #935283)
   * Run test code using the correct Lua interpreter, and not the default one
Checksums-Sha1:
 64658883291aa4c61c61d051aa6cc6dddf0c26a4 2044 lua-sec_0.8-2.dsc
 85f679cc6d15e3774b699d67a0576a6c1851308d 4832 lua-sec_0.8-2.debian.tar.xz
 f977fd54d4d4af63eb8b5831301827982e6d 6657 lua-sec_0.8-2_amd64.buildinfo
Checksums-Sha256:
 152611e3946131daf5a86c0c725a762ce484507232dcbdfa98b1fc77e3424fa5 2044 
lua-sec_0.8-2.dsc
 a03a5c2e53a382b927583c0d396a1bb56bb65f01b194f674c500439db67637bd 4832 
lua-sec_0.8-2.debian.tar.xz
 b1d3ceb016f571258854625a6abeb54e6dacb94748b5818e5f455093fb1149da 6657 
lua-sec_0.8-2_amd64.buildinfo
Files:
 80d624ff1244c03e9a996aa06a5f6cf2 2044 interpreters optional lua-sec_0.8-2.dsc
 7231edf3847dc1e04de4857d60e01596 4832 interpreters optional 
lua-sec_0.8-2.debian.tar.xz
 fb1a4fb7955f439e942db419b9b76fe8 6657 interpreters optional 
lua-sec_0.8-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/SYPsyDB+ShSnvc4Tyrk60tj54cFAl1qGE8ACgkQTyrk60tj
54eGNw//XZ58tHDkAmsuA+708QL8EeRyXDwJcrad5ihq24xszhUUOEWtDynq/KDz
qj6UGoJXWs1k2xeXd3/Q0Q5Vh1EppC0U3B3h9IUCwj3tDvuBW8SIKCQ+Fjlumab2
Pwep1aPMO0Ib3ryv1PHjS0zJr1eJv22a+BiXqVCwBF/8LKp7xMms4tQOvLcxPH5V
6+bNWuZ3r5M4Ulhg9ABPMQu4EF0B9wOphkkmMaWpHfNE2W9k+/47i5cG3kMDy3wa
2lsDeRsXFI3k57FlOv4vQYbRKJIp4BaB7NP+VkyPluF0+a+M7wbunJQeTzBDU6JN
VZB6OE3B9QIP4m2IJIt4J8MPhmvbVHO9lxhwlmLio129apPCUz/SuNGXWMRSQWFR
xLg/f4YPDnEhoZVdWSKrYPif9SUiDsGkecwz2zXJi/mfsvCKmBvi/9ADJuF3pnK+
xNxSS5jqhX1v4p9fuVLyZRli/sA4V1ZT5AszMTRhizgiIbVRLBz1xEammcf5WDfr
FptV5pCJ30tCrSZ8XyREYGamyIi0ryzl2DWSNWknFfeaVakJNzOXhPkL4Ad5Sv6K
CZ+8yVqSxkyefKSjE//DAeNQ78UC6gQ5VmRph35h7OCQhTgYJqoJWNdga37OsWDd
maGxJftM9g9lR59deQ8U0kIqosNWu+qKMCvQEXENCEx6oD9HEC4=
=kmdw
-END PGP SIGNATURE End Message ---


Bug#771615: marked as done (python-lamson: non-functioning email address for Maintainer)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 07:00:47 +
with message-id 
and subject line Bug#939009: Removed package(s) from unstable
has caused the Debian Bug report #771615,
regarding python-lamson: non-functioning email address for Maintainer
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.)


-- 
771615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-lamson
Version: 1.0pre11-1
Severity: important

Dear Maintainer,

The “Maintainer” field in ‘debian/control’ has the value:

David Watson 

Email sent to that address encounters permanent delivery failures,
resulting in unnecessary difficulty reaching the package maintainer.

Please put a functioning email address for the package maintainer in
the Maintainer field, and make a new release of this package to
publish it to automated systems.

-- 
 \“Read not to contradict and confute, nor to believe and take |
  `\  for granted … but to weigh and consider.” —Francis Bacon |
_o__)  |
Ben Finney 


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 1.0pre11-1.3+rm

Dear submitter,

as the package python-lamson has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/939009

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---


Bug#684743: marked as done (python-lamson: missing dependency on python-pkg-resources)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 07:00:47 +
with message-id 
and subject line Bug#939009: Removed package(s) from unstable
has caused the Debian Bug report #684743,
regarding python-lamson: missing dependency on python-pkg-resources
to be marked as done.

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

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


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

Package: python-lamson
Version: 1.0pre11-1
Severity: important

In a minimal chroot:

$ /usr/bin/lamson --help
Traceback (most recent call last):
  File "/usr/bin/lamson", line 3, in 
from lamson import args, commands
  File "/usr/lib/pymodules/python2.7/lamson/commands.py", line 29, in 
from pkg_resources import resource_stream
ImportError: No module named pkg_resources


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-lamson depends on:
ii  python   2.7.3-2
ii  python-chardet   2.0.1-2
ii  python-daemon1.5.5-1
ii  python-dns   2.3.6-1
ii  python-lockfile  1:0.8-2
ii  python-mock  0.8.0-2
ii  python-support   1.0.15

--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Version: 1.0pre11-1.3+rm

Dear submitter,

as the package python-lamson has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/939009

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---


Bug#927066: marked as done (python-gdata: Should not ship with Buster)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 06:59:08 +
with message-id 
and subject line Bug#938971: Removed package(s) from unstable
has caused the Debian Bug report #927066,
regarding python-gdata: Should not ship with 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.)


-- 
927066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-gdata
Version: 2.0.18+dfsg1-2
Severity: serious
Tags: buster sid

I am uploader of python-gdata and my intention is that it should not be
part of Debian Buster release.

There are two main reasons for it:

1) It does not actually work anymore: Google has shut down most of gdata
API backends [1]. Some of them like the YouTube data API continue to work
as per deprecation policy, but will most likely be shutdown during Buster
lifetime.

2) It is insecure: it bundles an ancient version of tlslite, which
has known vulnerabilities: at least CVE-2014-3566, CVE-2013-0169 and
CVE-2011-3389. Newer version of tlslite has been removed from Debian
in 2014, so I cannot even unbundle it.

I have filed bugs for all reverse dependencies in May 2018. At the moment
of writing this all reverse dependencies have been removed from Buster.

I am also going to get it removed from Sid later.

[1]: https://developers.google.com/gdata/docs/directory

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 2.0.18+dfsg1-2+rm

Dear submitter,

as the package python-gdata has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/938971

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---