Bug#931147: gdb depends on newer libbabeltrace

[Michael Jeanson]

On 2019-08-24 6:12 a.m., Andreas Beckmann wrote:
> Followup-For: Bug #931147
> 
> Hi,
> 
> I've just opened a PU request for babeltrace and a binNMU request
> for gdb etc. to get this fixed in buster, too.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935583
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935588
> 
> Andreas
> 

Thanks for doing this, I appreciate the help.

Michael

Processed: Re: [pkg-cryptsetup-devel] Bug#935702: Wrong DM device size due to integer truncation

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 DM device size ≥2³² 512-bits sectors is truncated on 32-bits 
> platforms
Bug #935702 [cryptsetup-bin] Wrong DM device size due to integer truncation
Changed Bug title to 'DM device size ≥2³² 512-bits sectors is truncated on 
32-bits platforms' from 'Wrong DM device size due to integer truncation'.
> tag -1 + upstream
Bug #935702 [cryptsetup-bin] DM device size ≥2³² 512-bits sectors is truncated 
on 32-bits platforms
Added tag(s) upstream.

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

Bug#935702: [pkg-cryptsetup-devel] Bug#935702: Wrong DM device size due to integer truncation

[Guilhem Moulin]

Control: retitle -1 DM device size ≥2³² 512-bits sectors is truncated on 
32-bits platforms
Control: tag -1 + upstream

Hi,

On Sun, 25 Aug 2019 at 12:43:26 +, n...@waifu.club wrote:
> 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.

Would you mind sharing your test vector, either here or the upstream bug
tracker at https://gitlab.com/cryptsetup/cryptsetup/issues ?  While it's
clear there is a bug, I was unable to reproduce your observations in the
arguably most common cases, namely block devices formatted as LUKS1 or
LUKS2 with the default parameters (and a payload size exceeding ≥2³²
512-bits sectors).  The only function of the dm_*_target_set() family
called is dm_crypt_target_set(), and always with 0 as segment offset and
size.

`cryptsetup plainOpen -b $LARGE_NUMBER` does yield a call to 
dm_crypt_target_set()
with a truncated dmd.size, but the proper size is used before opening
the device thanks to device_block_adjust().

Or does the bug only applies to integrity targets?  I'm indeed able to
reproduce for these targets:

$ uname -r
4.19.0-5-686
$ truncate -s3T /tmp/disk.img
$ losetup /dev/loop0 /tmp/disk.img

$ integritysetup format -s 512 --no-wipe -q /dev/loop0
$ integritysetup dump /dev/loop0 | grep provided_data_sectors
provided_data_sectors 6392379512
$ integritysetup open /dev/loop0 integrity_test
$ echo $?
0
$ dmsetup table integrity_test
0 2097412216 integrity …

syslog contains (checksum errors are due to no-wipe):
[…] device-mapper: integrity: Checksum failed at sector 0x7d03f780
[…] device-mapper: integrity: Checksum failed at sector 0x7d03f780
[…] Buffer I/O error on dev dm-2, logical block 262176496, async page read


## experimental --integrity extension
$ cryptsetup luksFormat -q --integrity hmac-sha256 --integrity-no-wipe \
--pbkdf-force-iterations 4 --pbkdf-memory 32 /dev/loop0 <<

signature.asc
Description: PGP signature

Bug#875165: Patch set to remove Qt 4 support

[Lisandro Damián Nicanor Pérez Meyer]

On Mon, 19 Aug 2019 15:28:53 -0300 
=?UTF-8?Q?Lisandro_Dami=C3=A1n_Nicanor_P=C3=A9rez_Meyer?= 
 wrote:
> This also adds proper .pc files back.
> 
> I also mailed qsapecng's maintainer in #875138. We are free to remove
> the package, so we can proceed with this.
> 
> I plan to NMU this package soon in order to get this fixed.

I have just uploaded the package to delayed/1, as tomorrow will be the seven
days recommened for NMUs of RC bugs without maintainr replies.

Please feel free to cancel it or ask me to do so.

Kinds regards, Lisandro.

Processed: Tag

[Debian Bug Tracking System]

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

> tag 875165 pending
Bug #875165 [src:qwt] [qwt] Future Qt4 removal from Buster
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#935615: marked as done (aptitude: FTBFS on amd64)

[Debian Bug Tracking System]

Your message dated Mon, 26 Aug 2019 00:19:34 +
with message-id 
and subject line Bug#935615: fixed in aptitude 0.8.12-1
has caused the Debian Bug report #935615,
regarding aptitude: 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.)


-- 
935615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:aptitude
version: 0.8.11-7
severity: serious
tags: ftbfs

Hi,

A binnmu of aptitude in unstable fails on amd64:

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

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: aptitude
Source-Version: 0.8.12-1

We believe that the bug you reported is fixed in the latest version of
aptitude, 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.
Manuel A. Fernandez Montecelo  (supplier of updated aptitude 
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 00:51:12 +0200
Source: aptitude
Architecture: source
Version: 0.8.12-1
Distribution: unstable
Urgency: medium
Maintainer: Aptitude Development Team 
Changed-By: Manuel A. Fernandez Montecelo 
Closes: 907436 935615
Changes:
 aptitude (0.8.12-1) unstable; urgency=medium
 .
   * New upstream release. Please see /usr/share/aptitude/NEWS for a change
 log with more details.
 .
 - New features:
   * Permit to retrieve changelogs of packages from Debian Ports
 repositories.
   * Adapt for changes in apt 1.9, like addressing deprecation and API
 changes.  Thanks to Julian Andres Klode.
 .
 - Bug fixes:
   * Adapt code to adapt to change of behaviour in Boost.MultiIndex
 library, and so we can start using Boost >= 1.66, 1.67 is about to
 become the default in Debian unstable.  Thanks to Julian Andres Klode.
   * Fix crashes when Label of a repository is empty (Closes: #907436)
   * Fix changelog downloads
   * Read the correct number of elements in
 pkg_item::pkg_columnizer::init_formatting() -- it was ignoring the last
 element, reading only 25 out of 26.
 .
 - Internal changes:
   * Misc. fixes about deprecation issues and minor compilation problems
 .
 .
   * Bump build-dependencies on cwidget to >= 0.5.18, that implies a
 library transition.  This ensures that aptitude is built against the
 latest cwidget ABI in the buildds.
   * d/patches, drop all patches because they are fixed in the upstream code:
 - changelogs-debian-ports.patch
 - fix-changelog-retrieval.patch
 - fix-crash-907436.patch
 - support-boost1.67.patch
   * Ensure that it builds in unstable with all the GCC compiler and
 library changes (Closes: #935615)
Checksums-Sha1:
 6eb6e8124ff763b6cac6c9943f58049812d9ea60 3030 aptitude_0.8.12-1.dsc
 c5671224be7efa88dc2a3831d0dbefdf0b3c3981 4723768 aptitude_0.8.12.orig.tar.xz
 fab21857ba59326d9d4a9a0f9b4b58583ce6eee5 56096 aptitude_0.8.12-1.debian.tar.xz
 a0154c451dced8202db3165d060861d1dffa4eeb 11657 
aptitude_0.8.12-1_amd64.buildinfo
Checksums-Sha256:
 b9a2a2ebae6e3fab5556d87167ceaa48b7faca8d7787455395b18882469a4a92 3030 
aptitude_0.8.12-1.dsc
 686af401ada97d3c94ca370164df9f5673962689e8efdb2a1d471d5dafd4b9a6 4723768 
aptitude_0.8.12.orig.tar.xz
 6b0b06cb4b8fd960f1b15768bd780d1805331f91b92691ee1d54c31fe050c940 56096 
aptitude_0.8.12-1.debian.tar.xz
 e0545d8c4fcf26458192fb343be4489ff3fa74041facbaf83dfa4ad66b742578 11657 
aptitude_0.8.12-1_amd64.buildinfo
Files:
 59e4fb7d21c72b56e462c25a44b46e51 3030 admin optional aptitude_0.8.12-1.dsc
 a115d84eff314906c52066f3881820b1 4723768 admin optional 
aptitude_0.8.12.orig.tar.xz
 f17065f3165e72c4ce988539d11aa243 56096 admin optional 
aptitude_0.8.12-1.debian.tar.xz
 334a6f8ca96408bb61e1edbb3bcaaf80 11657 admin optional 
aptitude_0.8.12-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEEKo6AUFxIYphDDdCTf3YGpEXcqA4FAl1jHOQQHG1hZm1AZGVi
aWFuLm9yZwAKCRB/dgakRdyoDm7iD/9+fDm8MQVzmbG8Apyh/yycZBaGIz/Lwgt4
LxBSNW5lLtshBRNNINl9loGixqN+qwFbM6H3oGxszr8qCbqek3tbSryg391worpm

Bug#935764: freeipmi: --link-doc between architecture all and not all packages breaks binNMUs

[Andreas Beckmann]

Source: freeipmi
Version: 1.6.3-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libfreeipmi17

The recent binNMU on amd64 rendered the freeipmi packages uninstallable
because of the --link-doc from an arch:any to an arch:all package.
The arch-dependent binary packages all got a dependency on
freeipmi-common (= 1.6.3-1.1+b1) which does not exist (as it is an
arch:all package, available at version 1.6.3-1.1 only).

Andreas

PS: don't forget to do source-only uploads to sid, otherwise the package
won't migrate to testing


libfreeipmi17_1.6.3-1.1+b1.log.gz
Description: application/gzip

Processed: freeipmi: --link-doc between architecture all and not all packages breaks binNMUs

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + libfreeipmi17
Bug #935764 [src:freeipmi] freeipmi: --link-doc between architecture all and 
not all packages breaks binNMUs
Added indication that 935764 affects libfreeipmi17

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

Processed: tagging 931944, tagging 931940, tagging 931935, tagging 931914, tagging 935698

[Debian Bug Tracking System]

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

> tags 931944 + sid bullseye
Bug #931944 [src:vtk7] vtk7: FTBFS with PROJ 6
Added tag(s) bullseye and sid.
> tags 931940 + sid bullseye
Bug #931940 [src:sumo] sumo: FTBFS with PROJ 6
Added tag(s) sid and bullseye.
> tags 931935 + sid bullseye
Bug #931935 [src:openorienteering-mapper] openorienteering-mapper: FTBFS with 
PROJ 6
Added tag(s) sid and bullseye.
> tags 931914 + sid bullseye
Bug #931914 {Done: Rafael Laboissiere } [src:octave-octproj] 
octave-octproj: FTBFS with PROJ 6
Added tag(s) bullseye and sid.
> tags 935698 + sid bullseye
Bug #935698 [amule-utils-gui] amule-utils-gui: amulegui crashing with current 
libwxgtk3.0-0v5 3.0.4+dfsg-9 and friends
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Bug#935713: marked as done (src:thrift: Incomplete debian/copyright)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 22:07:40 +
with message-id 
and subject line Bug#935713: fixed in thrift 0.11.0-6
has caused the Debian Bug report #935713,
regarding src:thrift: Incomplete debian/copyright
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.)


-- 
935713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:thrift
Version: 0.11.0-4
Severity: serious
Justification: Policy 2.3

While reviewing your package in New, I noticed omissions from debian/
copyright.  Since this problem also exists in the current package, I am
filing this bug rather than rejecting the package.

At a minimum, the following copyright/licenses are missing:

compile: GPL 2+

compiler/cpp/src/thrift/thrifty.hh: GPL 3+ + Bison exception
compiler/cpp/src/thrift/thrifty.cc

lib/php/src/ext/thrift_protocol/run-tests.php: PHP 3.01
Note: it references a LICENSE file that appears to be missing.

Please keep https://ftp-master.debian.org/php-license.html in mind when
you update your debian/copyright.

ylwrap: GPL 2+

build/cmake/FindGLIB.cmake: BSD 2 clause

Scott K
--- End Message ---
--- Begin Message ---
Source: thrift
Source-Version: 0.11.0-6

We believe that the bug you reported is fixed in the latest version of
thrift, 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.
Laszlo Boszormenyi (GCS)  (supplier of updated thrift 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, 25 Aug 2019 19:18:04 +
Source: thrift
Architecture: source
Version: 0.11.0-6
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 935713 935715
Changes:
 thrift (0.11.0-6) unstable; urgency=medium
 .
   * Update copyright file (closes: #935713).
   * Update Python packaging bits (closes: #935715).
Checksums-Sha1:
 569bc424a8d6fc172cfe3343682d1db590d0d635 3114 thrift_0.11.0-6.dsc
 037978b1a7b2d425f8083d3f2d7eeb9331abfda1 79000 thrift_0.11.0-6.debian.tar.xz
Checksums-Sha256:
 bcb8234c33817417c60242485d5c0b057ea6d8fcdd719cde6eff7bf39865229e 3114 
thrift_0.11.0-6.dsc
 3e8f2ae266c5a3c22afdb8cda0f635f67ac1e0f9c13153240c9ecca6b9b3be40 79000 
thrift_0.11.0-6.debian.tar.xz
Files:
 f8e034b5448265abaf44111088b6554d 3114 devel optional thrift_0.11.0-6.dsc
 896e1417320191b0a1444d40fee7db6a 79000 devel optional 
thrift_0.11.0-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl1jAdAACgkQ3OMQ54ZM
yL/s7g//SzIUm3emMYg/gOlALksXzGqb9NCePC4T9AX4nhPvArzSwe+eftJiu9hr
hULCZ1p6V3KmvpOVER6NV0nuqfauq1E6AnE766hBQcAasPYAbWjEnXTGq9OIFz+0
x5OryjW5QJ+Ko7Sdn5p7QdC/cHwnMAPqv8u+6rzSIpGb+44oAQzJiThbWRM+EjAm
pJbUdYUbP3L10gTBTljzl4X+eEwrQectqbamLZ8gCPQZB6/YGNpPM7AmYSs4gduS
4IwH6ECNWXASWF4UOxvAz7B3EGf5fXtolm6/GpicamHmKXANetbRZ2EJIEGzhqnF
43fZzsg7E/FDMdE65LyOgOuPci0bGAOG25tQV3jQmZRzi9VWXvbfdeQKCJ1uSda3
va7WKOAbHYL52T5kjOssZ+xpDn5QW/1IC2qUzuXdyoiz5/gIG0n1+wrDLL7SrGas
XKjfGO8uVwqNY+96b/+FaUyLn9xeLGEIO1zGhfjWUoa/YNkT4KFeWnw8X7pFLWWJ
PWA7jueJtgJPs9qjIt/FVewD7ZIPegEgiB3LdW3T261TiVMm4YDwrvxMjhgy+e1P
ranENk1kpI2DwFEUOrZQ/zM5M09ynC3CWWPwv/AXg5RkJ6IsAeWLQhHh18JILHLa
ABZDvVld5FCutyuvfzW965pTjX6dp2GUFvwrbOhOmjtTzsr3Ej0=
=XhYW
-END PGP SIGNATURE End Message ---

Bug#935620: thrift: FTBFS on amd64

[GCS]

On Sun, Aug 25, 2019 at 11:55 AM Ivo De Decker  wrote:
> If you add a new binary package, your upload will go to the NEW queue
> (and will have to include binaries).
 Sorry for the confusion, I meant which is better: upload it via
experimental and then do a Sid upload or do a Sid upload and do a
binNMU on buildds.

But I've done it via experimental and just uploaded to Sid.

Regards,
Laszlo/GCS

Bug#935759: postgresql-9.4: fails to purge: RET=10 postgresql-9.4/postrm_purge_data doesn't exist

[Andreas Beckmann]

Package: postgresql-9.4
Version: 9.4.24-0+deb8u1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to purge.
According to policy 7.2 you cannot rely on the depends being available
during purge, only the essential packages are available for sure.

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

  Removing postgresql-9.4 (9.4.24-0+deb8u1) ...
  Purging configuration files for postgresql-9.4 (9.4.24-0+deb8u1) ...
  + set -e
  + VERSION=9.4
  + [ purge = purge ]
  + [ -d /etc/postgresql/9.4 ]
  + ls /etc/postgresql/9.4
  + [ main ]
  + [ -e /usr/share/debconf/confmodule ]
  + . /usr/share/debconf/confmodule
  + [ !  ]
  + PERL_DL_NONLAZY=1
  + export PERL_DL_NONLAZY
  + [  ]
  + exec /usr/share/debconf/frontend /var/lib/dpkg/info/postgresql-9.4.postrm 
purge
  + set -e
  + VERSION=9.4
  + [ purge = purge ]
  + [ -d /etc/postgresql/9.4 ]
  + ls /etc/postgresql/9.4
  + [ main ]
  + [ -e /usr/share/debconf/confmodule ]
  + . /usr/share/debconf/confmodule
  + [ ! 1 ]
  + [ -z  ]
  + exec
  + [  ]
  + exec
  + DEBCONF_REDIR=1
  + export DEBCONF_REDIR
  + purge_package
  + [ -e /usr/share/debconf/confmodule ]
  + db_set postgresql-9.4/postrm_purge_data true
  + _db_cmd SET postgresql-9.4/postrm_purge_data true
  + _db_internal_IFS=

  + IFS=
  + printf %s\n SET postgresql-9.4/postrm_purge_data true
  + IFS=

  + IFS=
   read -r _db_internal_line
  + RET=10 postgresql-9.4/postrm_purge_data doesn't exist
  + return 10
  dpkg: error processing package postgresql-9.4 (--purge):
   subprocess installed post-removal script returned error exit status 10
  Errors were encountered while processing:
   postgresql-9.4

The template does not get registered because postinst does not load
/usr/share/debconf/confmodule.
In buster this is done by /usr/share/postgresql-common/maintscripts-functions
but in jessie the postinst has to do it manually

cheers,

Andreas


postgresql-9.4_9.4.24-0+deb8u1.log.gz
Description: application/gzip

Bug#932539: marked as done (qbittorrent: CVE-2019-13640)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 21:22:55 +
with message-id 
and subject line Bug#932539: fixed in qbittorrent 4.1.7-1
has caused the Debian Bug report #932539,
regarding qbittorrent: CVE-2019-13640
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.)


-- 
932539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qbittorrent
Version: 4.1.6-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/qbittorrent/qBittorrent/issues/10925
Control: found -1 4.1.5-1

Hi,

The following vulnerability was published for qbittorrent.

CVE-2019-13640[0]:
| In qBittorrent before 4.1.7, the function
| Application::runExternalProgram() located in app/application.cpp
| allows command injection via shell metacharacters in the torrent name
| parameter or current tracker parameter, as demonstrated by remote
| command execution via a crafted name within an RSS feed.


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-13640
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13640
[1] https://github.com/qbittorrent/qBittorrent/issues/10925

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: qbittorrent
Source-Version: 4.1.7-1

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

Debian distribution maintenance software
pp.
Andrew Starr-Bochicchio  (supplier of updated qbittorrent 
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, 25 Aug 2019 16:51:10 -0400
Source: qbittorrent
Binary: qbittorrent qbittorrent-dbg qbittorrent-nox
Architecture: source amd64
Version: 4.1.7-1
Distribution: unstable
Urgency: medium
Maintainer: Cristian Greco 
Changed-By: Andrew Starr-Bochicchio 
Description:
 qbittorrent - bittorrent client based on libtorrent-rasterbar with a Qt5 GUI
 qbittorrent-dbg - debug symbols for qbittorrent and qbittorrent-nox
 qbittorrent-nox - bittorrent client based on libtorrent-rasterbar (without X 
suppor
Closes: 932539 933889
Changes:
 qbittorrent (4.1.7-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #933889).
- Prevent command injection via "Run external program" function
  (Closes: #932539, CVE-2019-13640).
Checksums-Sha1:
 3b8a684d5869033ba9174626d1d98d37b60ab22e 2171 qbittorrent_4.1.7-1.dsc
 c62da06e4a5f1b1293d0c551f8b8432f1a9c2d71 4465352 qbittorrent_4.1.7.orig.tar.xz
 03ec763424f281ae78d46103040ab24188f17420 14 
qbittorrent_4.1.7-1.debian.tar.xz
 0a830866e45807c3075b9241a7d344cb763c375d 62045280 
qbittorrent-dbg_4.1.7-1_amd64.deb
 543500c411b17b5b3022d3719710cb7b76949d70 5075920 
qbittorrent-nox_4.1.7-1_amd64.deb
 f7b6c475c8bae02cf3141e8be6a45053992be4ed 11983 
qbittorrent_4.1.7-1_amd64.buildinfo
 5860a79fba0b48dc8ea37505bc00f237aa259007 5673324 qbittorrent_4.1.7-1_amd64.deb
Checksums-Sha256:
 84a326aa2f9d90d48c36301502f5cd8bd2f9a7b631276c7b764d111ac72c8665 2171 
qbittorrent_4.1.7-1.dsc
 1eef2cf930e167e7e1d2d338bf1efc0a4a38cba1211f909bc9741a7b5ff2b330 4465352 
qbittorrent_4.1.7.orig.tar.xz
 35d21b715e6ab294be7d46f4480b823d7c6b3b3521c5eb7f9617dd2cafae254a 14 
qbittorrent_4.1.7-1.debian.tar.xz
 d290747775cea0bc9810bf206fb9caae47bc93b58952fb81032ddb82ebcf16fa 62045280 
qbittorrent-dbg_4.1.7-1_amd64.deb
 538ad2312967edf0cd8aaa7e841d381cc831e8a9832b3fa42d8e246f5f13023a 5075920 
qbittorrent-nox_4.1.7-1_amd64.deb
 c9b78aab0b931983e71ab1460935e6fe2c4e5e6dc7abb6de55f737801225481d 11983 
qbittorrent_4.1.7-1_amd64.buildinfo
 7d52e3fa722416e3d108c37ea598e50260d8e53247e9b8ee7036de926e6dc1df 5673324 
qbittorrent_4.1.7-1_amd64.deb
Files:
 c2be1ecf970decb7e7eac85212ea1db1 2171 net optional qbittorrent_4.1.7-1.dsc
 d717e41ee7d0670f402c9c1f8e2c88fc 4465352 net optional 
qbittorrent_4.1.7.orig.tar.xz
 26c307b127fe0d8991dccca0addc0141 14 net optional 

Bug#935713: src:thrift: Incomplete debian/copyright

[GCS]

On Sun, Aug 25, 2019 at 4:06 PM Scott Kitterman  wrote:
> While reviewing your package in New, I noticed omissions from debian/
> copyright.  Since this problem also exists in the current package, I am
> filing this bug rather than rejecting the package.
[...]
> lib/php/src/ext/thrift_protocol/run-tests.php: PHP 3.01
> Note: it references a LICENSE file that appears to be missing.
>
> Please keep https://ftp-master.debian.org/php-license.html in mind when
> you update your debian/copyright.
 I've updated debian/copyright as there were other problems as well.
I'm just unsure if it will be auto rejected or not on upload. At least
Lintian is confused and from the following snipset
-- cut --
Files: lib/php/src/ext/thrift_protocol/run-tests.php
Copyright: Copyright (C) 1997-2017 The PHP Group
License: PHP-3.01
-- cut --
it thinks the whole source is under PHP license. At least it states:
E: thrift source: license-problem-php-license debian/copyright

Investigating how to resolve this. :-/

Cheers,
Laszlo/GCS

Bug#931914: marked as done (octave-octproj: FTBFS with PROJ 6)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 20:47:44 +
with message-id 
and subject line Bug#931914: fixed in octave-octproj 1.1.5-5
has caused the Debian Bug report #931914,
regarding octave-octproj: FTBFS with PROJ 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.)


-- 
931914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: octave-octproj
Version: 1.1.5-4
Severity: important
Tags: upstream patch
User: debian-...@lists.debian.org
Usertags: proj-6

Dear Maintainer,

Your package FTBFS with PROJ 6 from experimental.

The attached patch fixes the issue by defining 
ACCEPT_USE_OF_DEPRECATED_PROJ_API_H.

Note that this is only a temporary workaround, proj_api.h will be
removed in PROJ 7 scheduled for March 2020.

Upstream is aware of the issue, see:

 https://savannah.gnu.org/bugs/index.php?56039

Kind Regards,

Bas
diff -Nru octave-octproj-1.1.5/debian/patches/proj6.patch 
octave-octproj-1.1.5/debian/patches/proj6.patch
--- octave-octproj-1.1.5/debian/patches/proj6.patch 1970-01-01 
01:00:00.0 +0100
+++ octave-octproj-1.1.5/debian/patches/proj6.patch 2019-03-08 
15:16:34.0 +0100
@@ -0,0 +1,24 @@
+Description: Define ACCEPT_USE_OF_DEPRECATED_PROJ_API_H for PROJ 6.0.0 
compatibility
+Author: Bas Couwenberg 
+Bug: https://savannah.gnu.org/bugs/index.php?56039
+
+--- a/src/Makefile
 b/src/Makefile
+@@ -11,7 +11,7 @@ CFLAGS+=-Wstrict-prototypes -Wnested-ext
+ #Flags for C++
+ CXXFLAGS=$(FLAGSCOMW) $(FLAGSCOMO)
+ #Flags for the linker
+-LDFLAGS=-lproj
++LDFLAGS=-lproj -DACCEPT_USE_OF_DEPRECATED_PROJ_API_H
+ #Export flags for compilers and linker
+ export CFLAGS CXXFLAGS
+ 
+@@ -20,7 +20,7 @@ all: compile
+ 
+ .PHONY: compile
+ compile:
+-  $(MKOCTFILE) -c projwrap.c -o projwrap.o
++  $(MKOCTFILE) -c projwrap.c -o projwrap.o 
-DACCEPT_USE_OF_DEPRECATED_PROJ_API_H
+   $(MKOCTFILE) -g _op_transform.cc projwrap.o $(LDFLAGS)
+   $(MKOCTFILE) -g _op_fwd.cc projwrap.o $(LDFLAGS)
+   $(MKOCTFILE) -g _op_inv.cc projwrap.o $(LDFLAGS)
diff -Nru octave-octproj-1.1.5/debian/patches/series 
octave-octproj-1.1.5/debian/patches/series
--- octave-octproj-1.1.5/debian/patches/series  2018-12-30 22:01:14.0 
+0100
+++ octave-octproj-1.1.5/debian/patches/series  2019-03-08 15:16:34.0 
+0100
@@ -1 +1,2 @@
 do-not-strip-debugging-symbols.patch
+proj6.patch
--- End Message ---
--- Begin Message ---
Source: octave-octproj
Source-Version: 1.1.5-5

We believe that the bug you reported is fixed in the latest version of
octave-octproj, 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.
Rafael Laboissiere  (supplier of updated octave-octproj 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Aug 2019 15:39:00 -0300
Source: octave-octproj
Architecture: source
Version: 1.1.5-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Octave Group 
Changed-By: Rafael Laboissiere 
Closes: 931914
Changes:
 octave-octproj (1.1.5-5) unstable; urgency=medium
 .
   * d/control: Bump Standards-Version to 4.4.0 (no changes needed)
   * d/p/build-against-proj-6.patch: New patch (Closes: #931914)
Checksums-Sha1:
 a1684485b8a2440e894e9b68b826f2568a7608ed 2045 octave-octproj_1.1.5-5.dsc
 aa124aa107e52c62334b0b95943208885771fd93 3312 
octave-octproj_1.1.5-5.debian.tar.xz
 f0939604ea23dc5ea93be78e69464f86e360bbfc 16481 
octave-octproj_1.1.5-5_amd64.buildinfo
Checksums-Sha256:
 ff9a5987f12bab2bb2c16384f523947fa1846fa3f78d1a0ec5b08731a5cbacde 2045 
octave-octproj_1.1.5-5.dsc
 4fff835655ce1d35b55f459424a5d0327e0b732872157a5c3844072c0382c457 3312 
octave-octproj_1.1.5-5.debian.tar.xz
 bef1e5265a604aa5965173225fd01e8019ac7d0368a4016fc3558fd8df73558d 16481 
octave-octproj_1.1.5-5_amd64.buildinfo
Files:
 21b6868287fd4fbe255c5af91f90c1e6 2045 math optional octave-octproj_1.1.5-5.dsc
 8a1e330152128cf975461435c34fe09b 3312 math optional 
octave-octproj_1.1.5-5.debian.tar.xz
 f5036de84cbef10071399e14ce331024 16481 math optional 
octave-octproj_1.1.5-5_amd64.buildinfo

-BEGIN PGP 

Bug#935736: marked as done (Drop dependency on automoc)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 20:47:30 +
with message-id 
and subject line Bug#935736: fixed in meta-kde 5:103
has caused the Debian Bug report #935736,
regarding Drop dependency on automoc
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.)


-- 
935736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kde-sc-dev-latest
Severity: serious

All reverse dependencies of automoc have been dropped, but kde-sc-dev-latest 
still
depends on it, blocking it's removal.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: meta-kde
Source-Version: 5:103

We believe that the bug you reported is fixed in the latest version of
meta-kde, 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.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
meta-kde package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Aug 2019 16:10:42 -0300
Source: meta-kde
Architecture: source
Version: 5:103
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Closes: 935736
Changes:
 meta-kde (5:103) unstable; urgency=medium
 .
   * Team upload.
   * Drop kde-sc-dev-latest. It is no longer needed (no rdeps according to dak)
 and is currently stopping automoc's removal (Closes: #935736).
   * Bump Standards-Version to 4.4.0, no changes required.
   * Bump debhelper compatibility to 12.
Checksums-Sha1:
 349b0a061522d25b53eb6246818124cfcf731b4b 2600 meta-kde_103.dsc
 8a0b1259ee5d564dec8d03460996ab6c635bc1a4 15708 meta-kde_103.tar.xz
 e413b05bc88408eaafaac1cb5c76d8c16af8d1d9 6228 meta-kde_103_source.buildinfo
Checksums-Sha256:
 f4d761cabaaf5d525a5ad1cc248c887ddbbaefa9c2862cf1d1cd161c72086bdf 2600 
meta-kde_103.dsc
 6110d58077bd8d97fd94e0128b5415b99fb0cd61ec3bb8653fe7736f0db12af1 15708 
meta-kde_103.tar.xz
 6800f3ea809841b30edb831bfff05a15d42a9f99beb7637aace60f05b775084f 6228 
meta-kde_103_source.buildinfo
Files:
 ffe9831ac3f9158c430caf320aed9ce6 2600 metapackages optional meta-kde_103.dsc
 03afe1c6c63a013958136feb152d64eb 15708 metapackages optional 
meta-kde_103.tar.xz
 6dae36f7963195f79e5220d2f5552424 6228 metapackages optional 
meta-kde_103_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEEt36hKwjsrvwSzE8q2RfQGKGp9AFAl1i3ksUHGxpc2FuZHJv
QGRlYmlhbi5vcmcACgkQq2RfQGKGp9BxHQ//VN7xi4AFBmgYT5mBk0gi+aE52SoL
JX8QvCuqV1CeS0bHQJpGdvkiQ8JLNCD5uDDoISpB1dWRLfeSKmyF41lT7ohr0oOC
x4KEQkUjuhOEAPfaYGYH4Yo+pRhWbNykH1oMxWG6MK+KxLGGoYqftkQ9Zdz6kNFe
EpjGvxHV1kkMgMmFRLNfQkyYIFQyA1m5RM2s8Xvix9r6AwLFNUUO5MtuD7r45dHM
yHP8i922FqXDFdaHmtTOc+Adyu6ve7mNKubFGYes8mOHYMc1K8N7AXcaiU/c9TGh
FaJ/tk5r2zmmDLPMCJW5hdqwB91o2l1UJTLe/f673+aopl9GzK59hkii1R8jBmmx
VKVXdVTZtY/2iwV49WikEiZnYU9BT2fwZggkmS6aSATTzw23Jv4jUDxqDZz/HzXV
A0EkrU182G0ThJ8Agb8jyUxSfnIRi86CxrOwhJBE09t38CDN1YUSLssA6mmP82op
gHPcFFLRYONUgkvsBlWAcriaKaJt6mekcmF2w6YdWKq58HooxuTOOJHE9GBWMwgj
6/GEZHhfD/QcjqiGKopp+VkBDVHDWy9WC7Trkgj+2o+JIFIFHgVhtqFXuiKLLl/v
2LGptk5lHCdcBo0TIwveeC08mknwHu9PE763HyZJ2LSAXEUbEpw+73u4ScF/qZp4
TEoluXTWlKz9Z6Q=
=Wrlk
-END PGP SIGNATURE End Message ---

Bug#935733: marked as done (libbladerf-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc/libbladerf-dev/CONTRIBUTORS)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 20:39:30 +
with message-id 
and subject line Bug#935733: fixed in bladerf 0.2019.07-3
has caused the Debian Bug report #935733,
regarding libbladerf-doc: fails to upgrade from 'sid' - trying to overwrite 
/usr/share/doc/libbladerf-dev/CONTRIBUTORS
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.)


-- 
935733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbladerf-doc
Version: 0.2019.07-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 .../libbladerf-doc_0.2019.07-1_all.deb ...
  Unpacking libbladerf-doc (0.2019.07-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libbladerf-doc_0.2019.07-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/libbladerf-dev/CONTRIBUTORS', which is 
also in package libbladerf-dev:amd64 0.2017.12~rc1-2
  Errors were encountered while processing:
   /var/cache/apt/archives/libbladerf-doc_0.2019.07-1_all.deb


cheers,

Andreas


libbladerf-dev=0.2017.12~rc1-2_libbladerf-doc=0.2019.07-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: bladerf
Source-Version: 0.2019.07-3

We believe that the bug you reported is fixed in the latest version of
bladerf, 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.
A. Maitland Bottoms  (supplier of updated bladerf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Aug 2019 15:20:11 -0400
Source: bladerf
Architecture: source
Version: 0.2019.07-3
Distribution: unstable
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Closes: 935733
Changes:
 bladerf (0.2019.07-3) unstable; urgency=medium
 .
   * Handle upgrades with Breaks:/Replaces: (Closes: #935733)
Checksums-Sha1:
 24775199866cf1ec05ad210fb9c7fc4492e3bf36 3076 bladerf_0.2019.07-3.dsc
 2184fb81a0047027e04b8ed4fe8e310b0f6fe38a 68308 
bladerf_0.2019.07-3.debian.tar.xz
 12925a88dc42c60eec0c51c8531c67826ec241c6 12556 
bladerf_0.2019.07-3_amd64.buildinfo
Checksums-Sha256:
 242aec08e59a90904bf999220f23b46ac7577916ca0f83139bd16e5971af2917 3076 
bladerf_0.2019.07-3.dsc
 6fea1fb90f1a9e86c28a49a4cf898673ca82b6e33199837bcf90c543fc178309 68308 
bladerf_0.2019.07-3.debian.tar.xz
 8827eda0227c0cc92a9811ddc71c7a0cbca769bb5dbf59e97ff1558530244a21 12556 
bladerf_0.2019.07-3_amd64.buildinfo
Files:
 5898851ddbf64059330f3d5c850247dd 3076 comm optional bladerf_0.2019.07-3.dsc
 847d90312f064ff72ba3b1c483ab15f7 68308 comm optional 
bladerf_0.2019.07-3.debian.tar.xz
 55f5ff4956bb03ca04bdce879c0935f3 12556 comm optional 
bladerf_0.2019.07-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAl1i4OQACgkQUEHxiR9E
4JDkRQ//RGuC+owib92NclgGMbebbuzEwJI1CvHHlc8Tx+cXvHtKZe+dcWEElL3Y
yXkwAH+7+FJhD8mT4ODgQnqwBKLn7OIJILbn1kgYK0l5gDAA8XV2Uqk/K0jW7ouS
9pbEnhWkek+u2SVMsvn0hW/Qq5/ti7D3GMK+/vpneMoAhPe7K5xUmUTCZ4bWksgJ
0TsBhaDDKa9NW97NuDPa4657GsdC+AILoC9WaFcg9uQSx4VD2en8M9DNpHDlicia
WdLk/EoE2srswibd1mDss2WxCItrXT6Wkp0Jx3qmjPt4tBzr1yy831o5s6kvEoKm
y0LUjJbf/NMmz9ZkMnxhA9BJeyQF/9FU1QZCJJ3BrBrNFkqbcVnA8Cmh9dQB+5u6
klDVDZYOH9jdKfxC3w5o8AzwdL8IrzA4zCpJffuhUjUbtzbhMI8qTaTB9fB6rvlh
LC3l8WE/hCvaAtLdevsWK0G2BRN8jF4HahbwJdNFtOLMEPBaLIAuL+f1MvPR5kL0
32UnYg4vwWuPbqgHWTres8ojlxeJ0NG+Y2nEzoun4wzZgapqjzVY8olsSIObySSB
9CsScQ5Hf0y1roMwm9p39cpcnNUPJSxZx8GAs5HyUhd4IlYXhBdoXywO/d+97Uic
m4ARNs/OXp901/kW3176oYWp+G1RCjgw0fgcVXwiDzO76FdPato=
=a3kP
-END PGP SIGNATURE End Message ---

Bug#935592: marked as done (cogl: FTBFS on i386: tests hang indefinitely, possibly during test_pixel_buffer_set_data)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 20:40:54 +
with message-id 
and subject line Bug#935592: fixed in cogl 1.22.4-3
has caused the Debian Bug report #935592,
regarding cogl: FTBFS on i386: tests hang indefinitely, possibly during 
test_pixel_buffer_set_data
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.)


-- 
935592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cogl
Version: 1.22.4-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

On the i386 buildd:

> make[6]: Entering directory '/<>/tests/conform'
> Key:
> ok = Test passed
> n/a = Driver is missing a feature required for the test
> FAIL = Unexpected failure
> FIXME = Test failed, but it was an expected failure
> PASS! = Unexpected pass
> 
>Test  GL+FF GL+ARBFP GL+GLSL GL-NPTGL3
> ES2 ES2-NPT
>...
>   test_sub_texture: ok   ok  ok ok ok 
> ok  ok
>  test_pixel_buffer_map: ok   ok  ok ok ok 
> ok  ok
> E: Build killed with signal TERM after 150 minutes of inactivity

On amd64, for comparison:

>...
>   test_sub_texture: ok   ok  ok ok ok 
> ok  ok
>  test_pixel_buffer_map: ok   ok  ok ok ok 
> ok  ok
> test_pixel_buffer_set_data: ok   ok  ok ok ok 
> ok  ok
>   test_pixel_buffer_sub_region: ok   ok  ok ok ok 
> ok  ok
>...

I have not yet tried to reproduce this locally.

smcv
--- End Message ---
--- Begin Message ---
Source: cogl
Source-Version: 1.22.4-3

We believe that the bug you reported is fixed in the latest version of
cogl, 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.
Simon McVittie  (supplier of updated cogl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Aug 2019 18:07:05 +0100
Source: cogl
Architecture: source
Version: 1.22.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 935592
Changes:
 cogl (1.22.4-3) unstable; urgency=medium
 .
   * Team upload
   * d/p/Terminate-tests-with-SIGALRM-if-they-take-more-than-120-s.patch:
 Kill individual tests with SIGALRM if they take more than 120 seconds
 (arbitrary cutoff taken from the Meson build system in Mutter's fork
 of cogl). This avoids failing to build even though failures are ignored,
 and blocking a buildd for 150 minutes, if the test hangs.
 (Closes: #935592)
   * d/p/tests-Show-the-actual-output-from-tests-if-VERBOSE-is-set.patch:
 Show the output of each test. Writing it to a file is not much use
 on buildds, because the build directory is discarded after the build
 finishes anyway.
   * d/control.in: Add missing -dev dependency on libxrandr-dev
   * d/rules: Don't run xvfb-run under nocheck build option
   * d/p/test-premult-Don-t-free-texture-data-until-CoglBitmap-is-.patch:
 Fix a use-after-free in test code, which appears to fix one of the
 known test failures
   * d/p/Don-t-usually-run-tests-that-are-not-expected-to-succeed.patch:
 Don't run tests that are not expected to succeed, unless requested
 by setting $COGL_TEST_TRY_EVERYTHING
   * Canonicalize order of dependencies (wrap-and-sort -a)
   * Canonicalize order of installed file lists (wrap-and-sort -a)
   * Canonicalize Uploaders (wrap-and-sort -a)
Checksums-Sha1:
 83ffb5aeddd97cd669ebcbb43751ce0e6636fb8a 3586 cogl_1.22.4-3.dsc
 22f72afcea793ba912e6b255af10e511a5f32f42 18776 cogl_1.22.4-3.debian.tar.xz
 b8a339d8af141f5c3166283dde03e3d97450df63 13142 cogl_1.22.4-3_source.buildinfo
Checksums-Sha256:
 63c7370a4fbde5eb7764c41ee4e0d3b5d2fc281e4bed8f33dcb7b3716ddd2409 3586 
cogl_1.22.4-3.dsc
 74f64691276164cb3f474abb8856bb7551580f1718cd0bb037ecb0eb8978d03a 18776 
cogl_1.22.4-3.debian.tar.xz
 

Bug#935752: gcc-9-cross-mipsen: FTBFS (/usr/bin/python: bad interpreter: No such file or directory)

[Santiago Vila]

Package: src:gcc-9-cross-mipsen
Version: 1+c1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
gcc: 9.2.1-3 / 9.1.0-10cross1

old gcc version: 9.1.0-10 / 1

new gcc version: 9.2.1-3cross1
START stamp-dir/init-gcc
mkdir -p gcc
set -ex; \
cd gcc ; \
ln -sf /usr/src/gcc-9/gcc-9.2.0-dfsg.tar.xz gcc-9.2.0-dfsg.tar.xz ;\
cp -a  /usr/src/gcc-9/debian/ . ; \
if [ -n "$(grep -v '^\#' /<>/debian/patches/gcc-9/series)" ]; then 
\
  QUILT_PATCHES=/<>/debian/patches/gcc-9 quilt push --quiltrc 
/dev/null -a ; \
fi

[ ... ]

if [ xinfo = xinfo ]; then \
  rm -f doc/gfc-internals.info-*; \
  makeinfo --split-size=500 --split-size=500 -I 
../../src/gcc/doc/include -I ../../src/gcc/fortran \
-o doc/gfc-internals.info ../../src/gcc/fortran/gfc-internals.texi; \
else true; fi
../../src/gcc/fortran/gfc-internals.texi: warning: document without nodes
mkdir -p gm2/images
if [ -f ../../src/gcc/gm2/images/gnu.eps ] ; then \
   cp ../../src/gcc/gm2/images/gnu.eps 
/<>/gcc/build/gcc/gm2/images/gnu.eps ; \
else \
   pngtopnm ../../src/gcc/gm2/images/gnupng | pnmtops -noturn > 
/<>/gcc/build/gcc/gm2/images/gnu.eps ; \
fi
bash ../../src/gcc/gm2/tools-src/makeSystem -fpim \
 ../../src/gcc/gm2/gm2-libs/SYSTEM.def \
 ../../src/gcc/gm2/gm2-libs/SYSTEM.mod \
 -I../../src/gcc/gm2/gm2-libs \
 "/<>/gcc/build/./gcc/xgm2 
-B/<>/gcc/build/./gcc/" 
/<>/gcc/build/gcc/gm2/gm2-libs/SYSTEM.def
../../src/gcc/gm2/tools-src/def2texi.py -b/<>/gcc/build/gcc/gm2 
-f/<>/gcc/build/gcc/gm2/gm2-libs/SYSTEM.def > 
/<>/gcc/build/gcc/gm2/SYSTEM-pim.texi
/bin/bash: ../../src/gcc/gm2/tools-src/def2texi.py: /usr/bin/python: bad 
interpreter: No such file or directory
make[5]: *** [../../src/gcc/gm2/Make-lang.in:247: gm2/SYSTEM-pim.texi] Error 126
make[5]: Leaving directory '/<>/gcc/build/gcc'
make[4]: *** [Makefile:4368: all-gcc] Error 2
make[4]: Leaving directory '/<>/gcc/build'
make[3]: *** [Makefile:970: all] Error 2
make[3]: Leaving directory '/<>/gcc/build'
T Thu, 22 Aug 2019 13:25:38 +

[ ... ]

make[2]: *** [debian/rules2:1230: stamps/05-build-stamp] Error 1
make[2]: Leaving directory '/<>/gcc'
make[1]: *** [debian/rules:40: build] Error 2
make[1]: Leaving directory '/<>/gcc'
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
make: *** [debian/rules:410: stamp-dir/build-gcc.mips64] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A". I guess it 
will
happen 100% of the time when built in a clean chroot.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#935592: marked as pending in cogl

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #935592 in cogl 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/gnome-team/cogl/commit/4109d02652132524e44b2591892ca44422e4679b


Kill individual tests with SIGALRM if they take more than 120 seconds

This arbitrary cutoff was taken from the Meson build system in Mutter's
fork of cogl. This avoids failing to build even though failures
are ignored, and blocking a buildd for 150 minutes, if the test
hangs.

Closes: #935592


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/935592

Processed: Bug#935592 marked as pending in cogl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #935592 [src:cogl] cogl: FTBFS on i386: tests hang indefinitely, possibly 
during test_pixel_buffer_set_data
Added tag(s) pending.

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

Bug#875038: [lmms] Future Qt4 removal from Buster

[Boyuan Yang]

A stable lmms 1.2.0 with Qt5 support is already released several months ago.
Now it's about someone should be packaging it within Debian.

Thanks,
Boyuan Yang

在 2019-08-25日的 21:04 +0200，Moritz Mühlenhoff写道：
> On Sun, Oct 14, 2018 at 03:16:27AM +0200, Javier Serrano Polo wrote:
> > On Fri, 23 Mar 2018 18:23:51 +0800 Boyuan Yang <073p...@gmail.com>
> > wrote:
> > > lmms 1.2.0 is on its way.
> > 
> > I will not package a candidate version unless this bug becomes serious.
> > Efforts should be directed in helping upstream to release a stable
> > version.
> 
> This has now been bumped to serious last week. What's the plan here,
> ship an interim version supporting Qt5 or remove lmms and re-introduce
> it to Debian once a stable 2.0 release is out?
> 
> Cheers,
> Moritz
> 


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

Bug#917925: marked as done (Module fails to load on Linux 4.3 or later)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 19:13:45 +
with message-id 
and subject line Bug#935721: Removed package(s) from unstable
has caused the Debian Bug report #917925,
regarding Module fails to load on Linux 4.3 or later
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.)


-- 
917925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: device3dfx-source
Version: 2013.08.08-6
Severity: grave

devie3dfx-source can now build a module, but with these build-time
warnings:

  MODPOST 1 modules
WARNING: "mtrr_del" [/usr/src/modules/device3dfx/kbuild/3dfx.ko] undefined!
WARNING: "mtrr_add" [/usr/src/modules/device3dfx/kbuild/3dfx.ko] undefined!

The mtrr_{add,del}() functions are no longer exported since Linux 4.3,
which means it won't be possible to load the module.  Drivers should
use the higher-level functions arch_phys_wc_{add,del}() to mark memory
as write-combining.

Ben.

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

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

Versions of packages device3dfx-source depends on:
ii  debhelper 12
ii  make  4.2.1-1.2
ii  module-assistant  0.11.10

Versions of packages device3dfx-source recommends:
ii  kernel-package  13.018+nmu1

device3dfx-source suggests no packages.
--- End Message ---
--- Begin Message ---
Version: 2013.08.08-6+rm

Dear submitter,

as the package device3dfx 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/935721

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#875207: [tipp10] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Fri, Aug 23, 2019 at 09:16:57AM +0200, Christoph Martin wrote:
> Hi Moritz,
> 
> Am 22.08.19 um 21:47 schrieb Moritz Mühlenhoff:
> 
> > tipp10 seems to be dead upstream (not surprising given that it seems to be
> > based on an old diploma thesis)
> > 
> > Are you planning to port it to Qt5 yourself? Otherwise we should remove it
> > from the archive.
> 
> I'd like to try to port it to qt5. I also try to get some help from more
> experienced qt5 developpers or maintainers.

Sure, sounds good.

Cheers,
Moritz

Bug#874911: [hamfax] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sat, Sep 09, 2017 at 09:05:57PM +0200, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Source: hamfax
> 
> 
> Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> as [announced] in:
> 
> 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

We're now moving forward with the QT4 removal.

hamfax wasn't changed since 2011 and is dead upstream (last commit is from
2012). Does anyone of the Debian Hamradio Maintainers intend to port it to
Qt5 or should it be removed?

Cheers,
Moritz

Processed: severity of 910679 is serious

[Debian Bug Tracking System]

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

> severity 910679 serious
Bug #910679 [src:cegui-mk2] cegui-mk2 should build-depend on updated 
pyside-tools package
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: Bug#931914 marked as pending in octave-octproj

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #931914 [src:octave-octproj] octave-octproj: FTBFS with PROJ 6
Added tag(s) pending.

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

Bug#935733: libbladerf-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc/libbladerf-dev/CONTRIBUTORS

[A. Maitland Bottoms]

I got surprised by the result that adding a file to
debian/libbladerf-doc.docs resulted in a file being unpacked to
/usr/share/doc/libbladerf-dev/

Upload with Breaks:/Replaces: coming soon.
-Maitland

Bug#931914: marked as pending in octave-octproj

[Rafael Laboissiere]

Control: tag -1 pending

Hello,

Bug #931914 in octave-octproj 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/pkg-octave-team/octave-octproj/commit/a683eb8245a9dce25cfa7fbced9e1d3d3ff85f65


d/p/build-against-proj-6.patch: New patch

Closes: #931914


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/931914

Bug#935745: python-pushy: should this package be removed?

[Sandro Tosi]

Package: python-pushy
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Hello,
i'm looking at python-pushy as it depends on python-paramiko; one of bullseye
goals is to remove python2 and python-pushy

* is dead upstream
* last upload was in 2015, and NMU (one of the only 2 uploads)
* python2-only
* low popcon

If i dont hear anything back in 10 days, I'll file a RM bug for this package.

Regards,
Sandro


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

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

Versions of packages python-pushy depends on:
ii  python   2.7.16-1
ii  python-paramiko  2.6.0-1

python-pushy recommends no packages.

python-pushy suggests no packages.

Bug#874818: marked as done ([attica] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 19:14:24 +
with message-id 
and subject line Bug#935735: Removed package(s) from unstable
has caused the Debian Bug report #874818,
regarding [attica] 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.)


-- 
874818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: attica
Version: 0.4.2-2
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 ---
Version: 0.4.2-2+rm

Dear submitter,

as the package attica 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/935735

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#875038: [lmms] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sun, Oct 14, 2018 at 03:16:27AM +0200, Javier Serrano Polo wrote:
> On Fri, 23 Mar 2018 18:23:51 +0800 Boyuan Yang <073p...@gmail.com>
> wrote:
> > lmms 1.2.0 is on its way.
> 
> I will not package a candidate version unless this bug becomes serious.
> Efforts should be directed in helping upstream to release a stable
> version.

This has now been bumped to serious last week. What's the plan here,
ship an interim version supporting Qt5 or remove lmms and re-introduce
it to Debian once a stable 2.0 release is out?

Cheers,
Moritz

Bug#935738: python-webunit: please port to python 3

[Sandro Tosi]

Package: python-webunit
Severity: serious

Hello,
python-webunit is still python2-only, and one of the goals for Bullseye is to
remove python2.  python-webunit is a reverse-dependency of funkload, which will
also need to be ported to python3, but let's start with webunit.

An alternative would be to drop the whole stack from Debian: they dont appear to
be anylonger maintained upstream.

Regards,
Sandro

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

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

Versions of packages python-webunit depends on:
ii  python  2.7.16-1

python-webunit recommends no packages.

python-webunit suggests no packages.

Bug#933705: marked as done (aiscm: depend on correct libomp5 library)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 18:49:25 +
with message-id 
and subject line Bug#933705: fixed in aiscm 0.19.1-1
has caused the Debian Bug report #933705,
regarding aiscm: depend on correct libomp5 library
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.)


-- 
933705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aiscm
Version: 0.18.1-1
Severity: serious
Justification: breaks on update
tags: patch

Hello, if you need llvm-7, you should also use libomp-7-dev, because using the 
unversioned one will result in FTBFS once
llvm-defaults goes to 8.

Please see the following patch

diff -Nru aiscm-0.18.1/debian/control aiscm-0.18.1/debian/control
--- aiscm-0.18.1/debian/control 2018-11-06 21:57:33.0 +0100
+++ aiscm-0.18.1/debian/control 2019-08-02 09:29:41.0 +0200
@@ -4,7 +4,7 @@
 Priority: optional
 Homepage: http://wedesoft.github.io/aiscm/
 Standards-Version: 4.2.1
-Build-Depends: guile-2.2-dev, clang-7, llvm-7-dev, llvm-7, libomp-dev, 
linux-libc-dev, gettext, libmjpegtools-dev, imagemagick, libmagickcore-dev, 
libpulse-dev, libjpeg-dev, libx11-dev, libxext-dev, libxv-dev, libxmu-dev, 
libxi-dev, libxpm-dev, libglu1-mesa-dev, libgl1-mesa-dev, libswresample-dev, 
libswscale-dev, libavformat-dev, libavcodec-dev, libavutil-dev, pandoc, 
debhelper (>= 11)
+Build-Depends: guile-2.2-dev, clang-7, llvm-7-dev, llvm-7, libomp-7-dev, 
linux-libc-dev, gettext, libmjpegtools-dev, imagemagick, libmagickcore-dev, 
libpulse-dev, libjpeg-dev, libx11-dev, libxext-dev, libxv-dev, libxmu-dev, 
libxi-dev, libxpm-dev, libglu1-mesa-dev, libgl1-mesa-dev, libswresample-dev, 
libswscale-dev, libavformat-dev, libavcodec-dev, libavutil-dev, pandoc, 
debhelper (>= 11)
 
 Package: aiscm
 Architecture: amd64


thanks

Gianfranco
--- End Message ---
--- Begin Message ---
Source: aiscm
Source-Version: 0.19.1-1

We believe that the bug you reported is fixed in the latest version of
aiscm, 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 Wedekind  (supplier of updated aiscm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri,  2 Aug 2019 20:51:31 +0100
Source: aiscm
Architecture: source
Version: 0.19.1-1
Distribution: unstable
Urgency: low
Maintainer: Jan Wedekind 
Changed-By: Jan Wedekind 
Closes: 933705
Changes:
 aiscm (0.19.1-1) unstable; urgency=low
 .
   - New upstream release
   - Specify libomp-dev version (libomp-7-dev). Closes: #933705
   - Bumped Standards-Version to 4.4.0
   - Bumped compatibility level to 12.
   - do not run dwz on Guile object (*.go) files
   - remove library-not-linked-against-libc override
Checksums-Sha1:
 8fa7e4e23947040cff687bb164afd5f3710f7ab8 2311 aiscm_0.19.1-1.dsc
 1d073560875f47b5d70cb02302b93f1e2852acb5 3564056 aiscm_0.19.1.orig.tar.xz
 4ab0616b44d260a0de8b9505065b5fcae1557dff 833 aiscm_0.19.1.orig.tar.xz.asc
 6a2c60475f636ec1abdca6a33ecc75bf6c753125 5776 aiscm_0.19.1-1.debian.tar.xz
 073855ff0141eb6ec98ded3a6df6e71d30b95d30 15719 aiscm_0.19.1-1_amd64.buildinfo
Checksums-Sha256:
 55c44887dad5305284c803bdeabf51016d54851f59254d653df7a0073de23346 2311 
aiscm_0.19.1-1.dsc
 cea9ccd995c6f51249c063b6489dd13c8ba402829fe20565fd1482aac37e37d8 3564056 
aiscm_0.19.1.orig.tar.xz
 b225b25881501da97e52baefe5c448a85818f0326059922364a3dabc5cc693f9 833 
aiscm_0.19.1.orig.tar.xz.asc
 8ccdfcad565d989cf6ccff800ed61c31beb3312133275abd5a2d8078a4caef44 5776 
aiscm_0.19.1-1.debian.tar.xz
 e0bf13d7eadc1eaf6f270103f8d799d6965d1639763b4bcf08c8bd781ea0b378 15719 
aiscm_0.19.1-1_amd64.buildinfo
Files:
 c806ff8851eb2b8baa3e2ba68ff0bf8b 2311 lisp optional aiscm_0.19.1-1.dsc
 673214693053ff1ed33dba6c549fa1d6 3564056 lisp optional aiscm_0.19.1.orig.tar.xz
 8610c209404db6bcc4698c1ffab20377 833 lisp optional aiscm_0.19.1.orig.tar.xz.asc
 f6abde9a547f2c1c6796b4ab7bc5ac04 5776 lisp optional 
aiscm_0.19.1-1.debian.tar.xz
 aa66c8c0055c35095402d216a2df60b7 15719 lisp optional 
aiscm_0.19.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#935734: [workaround] Re: Bug#935734: error: Operation not supported: operation 'setCpusetMemoryMigrate' not supported

[Thorsten Glaser]

Dixi quod…

> tglase@tglase:~ $ virsh -c qemu:///system start MirBSD
> error: Failed to start domain MirBSD
> error: Operation not supported: operation 'setCpusetMemoryMigrate' not 
> supported

Looking around I found the (not very helpful to me)
https://bugzilla.redhat.com/show_bug.cgi?id=1688736
and after more research https://libvirt.org/cgroups.html
which led me to try something:

– sudoedit /etc/libvirt/qemu.conf
- add: cgroup_controllers = [ ]  (just removing cpuset from the
  default set is not enough)
- stop and start /etc/init.d/libvirtd

Voilà:

tglase@tglase:~ $ wirrsh start MirBSD
Domain MirBSD started

Make of that wht you will…

bye,
//mirabilos
-- 
15:41⎜ Somebody write a testsuite for helloworld :-)

Bug#935734: error: Operation not supported: operation 'setCpusetMemoryMigrate' not supported

[Thorsten Glaser]

On Sun, 25 Aug 2019, Thorsten Glaser wrote:

> Package: libvirt-daemon
> Version: 5.0.0-4.1

> After a recent upgrade in sid:

Hm, but it’s not libvirt, I think, whose upgrade broke things
(even if libvirt is unusable): looking at the logfiles under
/var/log/libvirt/qemu/ I see the last successful start was:

-BEGIN cutting here may damage your screen surface-
2019-08-16 17:19:22.042+: starting up libvirt version: 5.0.0, package: 4.1 
(Jonathan Wiltshire  Sat, 10 Aug 2019 13:31:18 +0100), qemu 
version: 3.1.0Debian 1:3.1+dfsg-8, kernel: 4.19.0-5-amd64, hostname: 
tglase.lan.tarent.de
LC_ALL=C \
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin \
HOME=/home/tglase \
USER=root \
LOGNAME=root \
QEMU_AUDIO_DRV=none \
/usr/local/bin/qemu-in-chroot \
-name guest=MirBSD,debug-threads=on \
-S \
-object 
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-MirBSD/master-key.aes
 \
-machine pc-i440fx-2.5,accel=kvm,usb=off,dump-guest-core=off \
-m 1024 \
-realtime mlock=off \
-smp 1,sockets=1,cores=1,threads=1 \
-uuid b0994f54-15e8-bb58-2f8f-1460fc81ec6b \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=26,server,nowait \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=utc \
-no-shutdown \
-boot strict=on \
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \
-drive 
file=/dev/vg-tglase/mirbsd,format=raw,if=none,id=drive-ide0-0-0,cache=none,aio=native
 \
-device 
ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1,write-cache=on
 \
-netdev tap,fd=29,id=hostnet0 \
-device e1000,netdev=hostnet0,id=net0,mac=52:54:00:49:f7:4f,bus=pci.0,addr=0x3 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-vnc 127.0.0.1:0 \
-device cirrus-vga,id=video0,bus=pci.0,addr=0x2 \
-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 \
-object rng-random,id=objrng0,filename=/dev/urandom \
-device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x5 \
-sandbox 
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
char device redirected to /dev/pts/7 (label charserial0)
-END cutting here may damage your screen surface-

The failing ones look like this:

-BEGIN cutting here may damage your screen surface-
2019-08-25 18:21:30.694+: starting up libvirt version: 5.0.0, package: 4.1 
(Jonathan Wiltshire  Sat, 10 Aug 2019 13:31:18 +0100), qemu 
version: 3.1.0Debian 1:3.1+dfsg-8, kernel: 5.2.0-2-amd64, hostname: 
tglase.lan.tarent.de
LC_ALL=C \
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin \
HOME=/ \
QEMU_AUDIO_DRV=none \
/usr/local/bin/qemu-in-chroot \
-name guest=MirBSD,debug-threads=on \
-S \
-object 
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-MirBSD/master-key.aes
 \
-machine pc-i440fx-2.5,accel=kvm,usb=off,dump-guest-core=off \
-m 1024 \
-realtime mlock=off \
-smp 1,sockets=1,cores=1,threads=1 \
-uuid b0994f54-15e8-bb58-2f8f-1460fc81ec6b \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=26,server,nowait \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=utc \
-no-shutdown \
-boot strict=on \
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \
-drive 
file=/dev/vg-tglase/mirbsd,format=raw,if=none,id=drive-ide0-0-0,cache=none,aio=native
 \
-device 
ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1,write-cache=on
 \
-netdev tap,fd=28,id=hostnet0 \
-device e1000,netdev=hostnet0,id=net0,mac=52:54:00:49:f7:4f,bus=pci.0,addr=0x3 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-vnc 127.0.0.1:0 \
-device cirrus-vga,id=video0,bus=pci.0,addr=0x2 \
-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 \
-object rng-random,id=objrng0,filename=/dev/urandom \
-device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x5 \
-sandbox 
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
libvirt:  error : libvirtd quit during handshake: Input/output error
2019-08-25 18:21:30.722+: shutting down, reason=failed
-END cutting here may damage your screen surface-

The diff is: HOME, USER, LOGNAME, fd argument for netdev, and kernel
4.19.0-5-amd64 (worked) vs 5.2.0-2-amd64 (fails).

bye,
//mirabilos
-- 
«MyISAM tables -will- get corrupted eventually. This is a fact of life. »
“mysql is about as much database as ms access” – “MSSQL at least descends
from a database” “it's a rebranded SyBase” “MySQL however was born from a
flatfile and went downhill from there” – “at least jetDB doesn’t claim to
be a database”  (#nosec)‣‣‣ Please let MySQL and MariaDB finally die!

Bug#935734: error: Operation not supported: operation 'setCpusetMemoryMigrate' not supported

[Thorsten Glaser]

> The diff is: HOME, USER, LOGNAME, fd argument for netdev, and kernel
> 4.19.0-5-amd64 (worked) vs 5.2.0-2-amd64 (fails).

Another difference might be that, in the meantime, I switched from
consolekit plus old policykit to elogind, which might have affected
some of the “modern desktop” things like cgroups.

bye,
//mirabilos
-- 
Sometimes they [people] care too much: pretty printers [and syntax highligh-
ting, d.A.] mechanically produce pretty output that accentuates irrelevant
detail in the program, which is as sensible as putting all the prepositions
in English text in bold font.   -- Rob Pike in "Notes on Programming in C"

Bug#935736: Drop dependency on automoc

[Moritz Muehlenhoff]

Package: kde-sc-dev-latest
Severity: serious

All reverse dependencies of automoc have been dropped, but kde-sc-dev-latest 
still
depends on it, blocking it's removal.

Cheers,
Moritz

Bug#935734: error: Operation not supported: operation 'setCpusetMemoryMigrate' not supported

[Thorsten Glaser]

Package: libvirt-daemon
Version: 5.0.0-4.1
Severity: grave
Justification: renders package unusable

After a recent upgrade in sid:

tglase@tglase:~ $ virsh -c qemu:///system start MirBSD
error: Failed to start domain MirBSD
error: Operation not supported: operation 'setCpusetMemoryMigrate' not supported


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

Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages libvirt-daemon depends on:
ii  libacl1 2.2.53-4
ii  libapparmor12.13.3-4
ii  libaudit1   1:2.8.5-2
ii  libavahi-client30.7-4+b1
ii  libavahi-common30.7-4+b1
ii  libblkid1   2.34-0.1
ii  libc6   2.28-10
ii  libcap-ng0  0.7.9-2+b1
ii  libcurl3-gnutls 7.65.3-1
ii  libdbus-1-3 1.12.16-1
ii  libdevmapper1.02.1  2:1.02.155-3
ii  libfuse22.9.9-1
ii  libgcc1 1:9.2.1-4
ii  libgnutls30 3.6.9-4
ii  libnetcf1   1:0.2.8-1+b2
ii  libnl-3-200 3.4.0-1
ii  libnl-route-3-200   3.4.0-1
ii  libparted2  3.2-25+b1
ii  libpcap0.8  1.9.0-2
ii  libpciaccess0   0.14-1
ii  libsasl2-2  2.1.27+dfsg-1
ii  libselinux1 2.9-2+b2
ii  libssh2-1   1.8.0-2.1
ii  libudev1242-4
ii  libvirt05.0.0-4.1
ii  libxml2 2.9.4+dfsg1-7+b3tarent1
ii  libyajl22.1.0-3

Versions of packages libvirt-daemon recommends:
ii  libxml2-utils   2.9.4+dfsg1-7+b3tarent1
ii  netcat-openbsd  1.203-1
ii  qemu1:2.12+dfsg-1+b1

Versions of packages libvirt-daemon suggests:
pn  libvirt-daemon-driver-storage-gluster  
pn  libvirt-daemon-driver-storage-rbd  
pn  libvirt-daemon-driver-storage-zfs  
ii  libvirt-daemon-system  5.0.0-4.1
pn  numad  

-- no debconf information

Bug#935733: libbladerf-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc/libbladerf-dev/CONTRIBUTORS

[Andreas Beckmann]

Package: libbladerf-doc
Version: 0.2019.07-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 .../libbladerf-doc_0.2019.07-1_all.deb ...
  Unpacking libbladerf-doc (0.2019.07-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libbladerf-doc_0.2019.07-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/libbladerf-dev/CONTRIBUTORS', which is 
also in package libbladerf-dev:amd64 0.2017.12~rc1-2
  Errors were encountered while processing:
   /var/cache/apt/archives/libbladerf-doc_0.2019.07-1_all.deb


cheers,

Andreas


libbladerf-dev=0.2017.12~rc1-2_libbladerf-doc=0.2019.07-1.log.gz
Description: application/gzip

Bug#935712: marked as done (FTBFS: dh-elpa error)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 18:07:41 +
with message-id 
and subject line Bug#935712: fixed in emacs-git-modes 1.2.8-3
has caused the Debian Bug report #935712,
regarding FTBFS: dh-elpa error
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.)


-- 
935712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emacs-git-modes
Version: 1.2.8-2
Severity: serious
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

during a no-change rebuild of this package I noticed that it fails to build 
from source

It looks like there is an incompatibility with the latest
dh-elpa.

,
| Generating git-modes-autoloads.el
| Installing...
| make[1]: Leaving directory '/<>'
|dh_elpa -i
| dh_elpa: emacs -batch -Q -l package --eval (add-to-list 
'package-directory-list "/usr/share/emacs/site-lisp/elpa") --eval (add-to-list 
'package-directory-list "/usr/share/emacs/site-lisp/elpa-src") -f 
package-initialize -l dh-elpa.el -f dhelpa-batch-install-file 
debian/elpa-git-modes//usr/share/emacs/site-lisp/elpa-src ./git-modes.el 
/<>/debian/.debhelper/elpa 1566734946 returned exit code 255
| E: The Debian version  cannot be used as an ELPA version.
| See dh_elpa(1) HINTS for how to deal with this.
| make: *** [debian/rules:4: binary-indep] Error 255
| dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2
`

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

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl1ikmgACgkQA0U5G1Wq
FSEbQw/+OXMkwDg7Pw5Cid5/x8GM8JRnWFKypsEBGeRDE0qdNHaGY0ep2uv67lLE
+1OwHCkuMMIkPNgb0qxX66iXejatKKtFefQ/YE6GwtIHaPlr1Fjdi+CeJpRF/PIP
06II9XCzcb8fIPHhQWgOnkO+8ZqQtI26l5piLYqrehfd3ztsoCmP0mlRPtkdYKUJ
0/Ia3t61yq0KYdn8KKNEZD3GPLAbz4c/9zr8FFp30u4qvX6KanYZ7G5Dix1H8sti
Y3fDOzLmjhyLOzVi2Vg7nb1ZzuPqEH0zAcQT+G0ONibuR+Ttfa/Z7StSLaF9Kf1p
W1SoM/TupjYxuDdwGEfnoDVHiBdrWRRkAHngp6vmX/N7odCB3pPGxuM05kOKJhch
duv4hWzMdu6iPoS9Qfm/3FSQe5mUN0bTqfAogRJjTLnXPNkufV1pTmCfE8sT2TJj
O12EUmhB0ELdPVEak6QS2kSXfV6y04iImOkS27lTiE+xtxrrt8RCxRGwZ06Z6lv6
ubdUG9yREAhDsLVFcCISF2YiwhCZ2Pv0wQuTQE+XJLhNyIa1D1v1sOeP02+z8A0o
hCRDB4Hv9H2PzDIY9eDEUOc3VJxk5y21Kj9BLaSAA6aVpbmHCQTjXlS2AdDIE/0j
tB4r5TrT+3mEsM2tt5rv/isPoIg5ZZt+Hbk+8rftdxOw/z9lhU4=
=N3Up
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: emacs-git-modes
Source-Version: 1.2.8-3

We believe that the bug you reported is fixed in the latest version of
emacs-git-modes, 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.
David Bremner  (supplier of updated emacs-git-modes package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Aug 2019 14:38:48 -0300
Source: emacs-git-modes
Architecture: source
Version: 1.2.8-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: David Bremner 
Closes: 935712
Changes:
 emacs-git-modes (1.2.8-3) unstable; urgency=medium
 .
   * Team upload.
   * Regenerate source package with quilt patches  (Closes: #935712).
Checksums-Sha1:
 c92ae19b47b3ac0b39e6f7ceb1c0536245968aa4 2309 emacs-git-modes_1.2.8-3.dsc
 03cc32a4b8e4d02597aab63975f0f4dfecd0554d 2760 
emacs-git-modes_1.2.8-3.debian.tar.xz
Checksums-Sha256:
 371a00d87be3b440d36d4dd113efc5061f9563d8df4daa3ea7cef2c886cee618 2309 
emacs-git-modes_1.2.8-3.dsc
 cb0317f6c106a6aea2df77300b7b94b8c82194f3c771e23656eedbf30628623f 2760 
emacs-git-modes_1.2.8-3.debian.tar.xz
Files:
 979fec0a575bd448c3883b3743f25360 2309 lisp optional emacs-git-modes_1.2.8-3.dsc
 9387652ffdf46ee3d2f0e59d8171fb04 2760 lisp optional 

Bug#935711: marked as done (FTBFS: looks for docker?)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 18:07:52 +
with message-id 
and subject line Bug#935711: fixed in emacs-pdf-tools 0.90-3
has caused the Debian Bug report #935711,
regarding FTBFS: looks for docker?
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.)


-- 
935711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emacs-pdf-tools
Version: 0.90-2
Severity: serious
Justification: ftbfs

During a no-change rebuild I noticed this packge does not build from source.
Apologies if this is caused by the way I created the source package:

%  dgit --quilt=auto push-source --overwrite

A sample build log is at

https://buildd.debian.org/status/fetch.php?pkg=emacs-pdf-tools=amd64=0.90-2=1566739129=log

I'm not sure what it wants docker for, but here is the relevant portion of logs:

Creating Dockerfile for target gentoo
Creating Dockerfile for target centos-7
cat docker/templates/gentoo.Dockerfile.in docker/templates/Dockerfile.in > 
docker/gentoo.Dockerfile
Creating Dockerfile for target fedora-25
cat docker/templates/centos-7.Dockerfile.in docker/templates/Dockerfile.in > 
docker/centos-7.Dockerfile
Creating Dockerfile for target arch
cat docker/templates/fedora-25.Dockerfile.in docker/templates/Dockerfile.in > 
docker/fedora-25.Dockerfile
cat docker/templates/arch.Dockerfile.in docker/templates/Dockerfile.in > 
docker/arch.Dockerfile
Creating Dockerfile for target ubuntu-16
cat docker/templates/ubuntu-16.Dockerfile.in docker/templates/Dockerfile.in > 
docker/ubuntu-16.Dockerfile
Creating Dockerfile for target fedora-24
Creating Dockerfile for target debian-9
cat docker/templates/fedora-24.Dockerfile.in docker/templates/Dockerfile.in > 
docker/fedora-24.Dockerfile
cat docker/templates/debian-9.Dockerfile.in docker/templates/Dockerfile.in > 
docker/debian-9.Dockerfile
Creating Dockerfile for target fedora-26
cat docker/templates/fedora-26.Dockerfile.in docker/templates/Dockerfile.in > 
docker/fedora-26.Dockerfile
Creating Dockerfile for target ubuntu-14
cat docker/templates/ubuntu-14.Dockerfile.in docker/templates/Dockerfile.in > 
docker/ubuntu-14.Dockerfile
Creating Dockerfile for target ubuntu-17
cat docker/templates/ubuntu-17.Dockerfile.in docker/templates/Dockerfile.in > 
docker/ubuntu-17.Dockerfile
Creating Dockerfile for target debian-8
cat docker/templates/debian-8.Dockerfile.in docker/templates/Dockerfile.in > 
docker/debian-8.Dockerfile
Building target gentoo
docker build -q -t epdfinfo/gentoo -f docker/gentoo.Dockerfile ../
Building target centos-7
make[3]: docker: Command not found
Building target fedora-25
docker build -q -t epdfinfo/centos-7 -f docker/centos-7.Dockerfile ../
make[3]: docker: Command not found
Building target arch
make[3]: *** [Makefile:30: docker/.gentoo.build] Error 127
make[3]: *** Waiting for unfinished jobs
make[3]: *** [Makefile:30: docker/.centos-7.build] Error 127
docker build -q -t epdfinfo/fedora-25 -f docker/fedora-25.Dockerfile ../
make[3]: docker: Command not found
make[3]: *** [Makefile:30: docker/.fedora-25.build] Error 127
docker build -q -t epdfinfo/arch -f docker/arch.Dockerfile ../
make[3]: docker: Command not found
make[3]: *** [Makefile:30: docker/.arch.build] Error 127
make[3]: Leaving directory '/<>/server/test'
make[2]: *** [Makefile:940: check-local] Error 2
make[2]: Leaving directory '/<>/server'
make[1]: *** [Makefile:801: check-am] Error 2
make[1]: Leaving directory '/<>/server'
dh_auto_test: cd server && make -j4 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:15: build-arch] Error 255
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Build finished at 2019-08-25T13:18:44Z

Finished




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

Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: emacs-pdf-tools
Source-Version: 0.90-3

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

A summary of the changes between this version and 

Bug#935710: marked as done (FTBFS: tests fail)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 18:07:59 +
with message-id 
and subject line Bug#935710: fixed in emacs-python-environment 0.0.2-5
has caused the Debian Bug report #935710,
regarding FTBFS: tests fail
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.)


-- 
935710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emacs-python-environment
Version: 0.0.2-4
Severity: serious
Justification: ftbfs

During a no-change rebuild, I noticed this package fails to build from source

Apparently the tests are failing

https://buildd.debian.org/status/fetch.php?pkg=emacs-python-environment=all=0.0.2-4=1566739692=log

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: emacs-python-environment
Source-Version: 0.0.2-5

We believe that the bug you reported is fixed in the latest version of
emacs-python-environment, 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.
David Bremner  (supplier of updated 
emacs-python-environment package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Aug 2019 14:50:31 -0300
Source: emacs-python-environment
Architecture: source
Version: 0.0.2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: David Bremner 
Closes: 935710
Changes:
 emacs-python-environment (0.0.2-5) unstable; urgency=medium
 .
   * Team upload.
   * Regenerate source package with quilt patches (Closes: #935710).
Checksums-Sha1:
 6af3ec75a7c6f7a5c12182257aeb5c8a381802de 2274 
emacs-python-environment_0.0.2-5.dsc
 64e2b00bef8c8a36777e5670d5623e0fd0a0efd9 3296 
emacs-python-environment_0.0.2-5.debian.tar.xz
Checksums-Sha256:
 11467c570c5399c98b36c36162b7d36467169f31b2463b5561ae23fcdfd84a38 2274 
emacs-python-environment_0.0.2-5.dsc
 159c6e92de6d3bf39eea067f2059067191fbf6d54bd69dd40ed8f91d37525415 3296 
emacs-python-environment_0.0.2-5.debian.tar.xz
Files:
 99e946cb54583b9bd37bd1b4603482d4 2274 lisp optional 
emacs-python-environment_0.0.2-5.dsc
 50ec49a2e1c61a4ccce724f027994f6e 3296 lisp optional 
emacs-python-environment_0.0.2-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl1iyvYACgkQA0U5G1Wq
FSEuQw/+J66BG+VIwq5ap+bPg+jhRDQwGhRtBJtsuuGxGnmBiVNqd/10WjgYbZLE
KD+DIsdlWtGglEJz9N+JySoSzyd4XFOedouuWAviF1KP5U/AB0so9RRH4lEz4PQN
Z2rvtwVyd2IV59J4BX98OSi+Q9EQrVz2H42Tv/0rT1rShbw9KnIpd7JXSK2tW0sH
lW+nFwb02QbcmnmA3TEaYnyN6mGmVu2972tZaT2vMWWx+ge44SOeabMMUs6I4kQm
QkhGkqBcoMdYkrNDwM3OQtK0LUBsf7ynVHFIUI8gmEDbfrBHnL1gf3Ty5eyyfLEB
B/ptcBO+BXEhc1aYLole1ajmUWii2Z69lWDsCoPfx0AoNyfSFOAzsPaurrQ0J8F1
n6FpMR4Gl0rNRUDcRCvtwRqxKOeO/tVo5jZ4ko8t9LQas9yF9CoDAJDbhfR/2CX0
YVHfP5/uoHIYmpQXx9lfG8p4ebdSDCH81iCjn4dd+6Xwdm82ZVYg0kJvSXwOaq5B
UisuzUDUTvUHMCL8tUEz6syJUXt8HcHlumLj7cG3Dcw6Brt1ADrT+FGrtOLhAqKa
q9XM8GJSfxYPy64SmatR/6Ua1RvSyVVxdfD/Tw7CaIJtWndcndN82N4q3cWqX4gf
k1qiIUvCSfbzaYTMFB9p/HjA0RS6YbQ5bB5SYhwyaoQlFes/5R0=
=S+UB
-END PGP SIGNATURE End Message ---

Bug#935731: comitup: port to python 3

[Sandro Tosi]

Package: comitup
Severity: serious

Hello,
comitup is one of the only rdeps of python-tabulate; Debian has a target of
dropping Python 2 from Bullseye, so please port comitup to python 3.

Regards,
Sandro

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

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

Versions of packages comitup depends on:
ii  dnsmasq-base [dnsmasq-base]  2.80-1
ii  iw   5.0.1-1
ii  python3  3.7.3-1
ii  python3-crypto   2.6.1-9+b1
ii  python3-flask1.0.2-3
ii  python3-gi   3.30.4-1
ii  python3-jinja2   2.10-2
pn  python3-networkmanager   
ii  python3-pkg-resources41.0.1-1
ii  systemd  241-5

comitup recommends no packages.

Versions of packages comitup suggests:
pn  python-tabulate  

Bug#935730: kamcli: port to python 3 (or remove from Debian?)

[Sandro Tosi]

Package: kamcli
Severity: serious

Hello,
kamcli is one of the only rdeps of python-tabulate; Debian has a target of
dropping Python 2 from Bullseye, so please port kamcli to python 3; an
alternative would be to drop kamcli entirely: it has a single popcon entry, so
i'm afraid it's not that populare of a package anyway.

Thanks,
Sandro

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

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

Versions of packages kamcli depends on:
ii  python  2.7.16-1
ii  python-click7.0-1
pn  python-pretty-yaml  
pn  python-sqlalchemy   
pn  python-tabulate 

kamcli recommends no packages.

kamcli suggests no packages.

Bug#875149: marked as done ([qtcurve] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 17:09:59 +
with message-id 
and subject line Bug#875149: fixed in qtcurve 1.9-4
has caused the Debian Bug report #875149,
regarding [qtcurve] 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.)


-- 
875149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtcurve
Version: 1.8.18+git20160320-3d8622c-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: qtcurve
Source-Version: 1.9-4

We believe that the bug you reported is fixed in the latest version of
qtcurve, 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.
Scott Kitterman  (supplier of updated qtcurve package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Aug 2019 12:23:45 -0400
Source: qtcurve
Architecture: source
Version: 1.9-4
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Scott Kitterman 
Closes: 875149
Changes:
 qtcurve (1.9-4) unstable; urgency=medium
 .
   * Team upload.
   * Drop Qt4 support (Closes: #875149)
Checksums-Sha1:
 b929765f8692044eb3e5396f8ab2099e0890 2758 qtcurve_1.9-4.dsc
 11e0bf110f4668aad03ebae333dc3c4e92c7fcac 12240 qtcurve_1.9-4.debian.tar.xz
 305af6ac2562bc8a18e86d9e9adbfe8fbcfbda26 10837 qtcurve_1.9-4_source.buildinfo
Checksums-Sha256:
 20f9d75cf54a5ed01847a8703813cb89bb8fb4ddc3f20ca1ec41143e64872ff1 2758 
qtcurve_1.9-4.dsc
 f54270af2405e91e8880d3f13013c01640fc844bc5e735f334ae9f7a05386983 12240 
qtcurve_1.9-4.debian.tar.xz
 cf277f2b7188913919441be04e2bc7dabfe4e2715ebe276c7ea7ede372f48efd 10837 
qtcurve_1.9-4_source.buildinfo
Files:
 6164ce6c236bc2f41e2752a0f572d73a 2758 kde optional qtcurve_1.9-4.dsc
 02aceec86a3916f02a46ecfbd87dce69 12240 kde optional qtcurve_1.9-4.debian.tar.xz
 79498cbbc6e65aff80828f42c7fdd651 10837 kde optional 
qtcurve_1.9-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE53Kb/76FQA/u7iOxeNfe+5rVmvEFAl1itmcACgkQeNfe+5rV
mvGAUQ/+PXhynOnUQcuGwSOBEOicw2HJlN6HXMMmvE9zCv2+8STqTlvqur0/JJFb
TYVaBxcQ3OsfFpIVJbAvudnG9PKBLMF2PkJnCwjaBl1QBimW37vcC1O6nLUAznHH
QIVOBVqccf3QGVLmEM614W6QLUGwWBFUO69yzXMpHsqW5DvjGOb3h18zA7EeBsJM

Processed: Tagging #935570 as pending

[Debian Bug Tracking System]

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

> tags 935570 + pending
Bug #935570 [src:pysph] src:pysph: License and Copyrights missing from 
debian/copyright
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#935615: [Aptitude-devel] Bug#935615: aptitude: FTBFS on amd64

[Manuel A. Fernandez Montecelo]

Hi,

Em dom, 25 de ago de 2019 às 16:27, Axel Beckert  escreveu:
>
> Hi Manuel,
>
> Ivo De Decker wrote:
> > A binnmu of aptitude in unstable fails on amd64:
> >
> > https://buildd.debian.org/status/package.php?p=aptitude
>
> Do you happen to know if any of your recent commits to the master
> branch already fixes this issue? I haven't found any which looks
> fitting on a first glance...
>
> If you can pinpoint one or more commits, I can cherry pick them and do
> a quick upload to fix this issue.

Actually the more direct cause to the build error it's commit
2591a1d9069eb2e75087737c25b41449b68bd248 in cwidget.  I worked on it
in May/June, along with other changes in cwidget, but then it took a
while in the NEW queue to get uploaded to experimental, so the window
of opportunity for me to work on it went away...

Maybe with that patch to cwdiget is enough, but maybe not; there are
more changes needed for Boost for example, not sure what's the default
version of boost now, but if not now the adaptation will be needed
soon.

More in general, what it needs to happen is to move cwidget 0.5.18-1
to unstable (as -2 or whatever), then rebuild aptitude against it
(would be a transition, but aptitude is the only package depending on
cwidget), and releases cwidget 0.5.19 and aptitude 0.8.12 as well --
it contains fixes for the upcoming apt 1.9 and other things.

Maybe I can start by moving cwidget to unstable and either binNMUing
or releasing the new aptitude version?


Cheers.
-- 
Manuel A. Fernandez Montecelo 

Bug#935698: amule-utils-gui: amulegui crashing with current libwxgtk3.0-0v5 3.0.4+dfsg-9 and friends

[Bernhard Übelacker]

Hello Martintxo,
I am just looking at crashes of some random packages and
found your backtrace. Thats already a good start.
As I it looks like you had installed the package
amule-utils-gui-dbgsym maybe you could also install these packages:

libwxbase3.0-0v5-dbgsym libwxgtk3.0-0v5-dbgsym libgtk2.0-0-dbgsym 
libglib2.0-0-dbgsym

That way the backtrace would contain line information not just
for the main executable but also for the .so files.
I guess it will point into wxWindow::DoClientToScreen [1] at
the top frames.

And yes, the duplicate lines are of no help, so ommiting most of them
is good, like you did.

And because it was not reproducible for me, you might add
which desktop environment you are using, and maybe note if
which theme is in use.

Kind regards,
Bernhard

[1] 
https://sources.debian.org/src/wxwidgets3.0/3.0.4+dfsg-9/src/gtk/window.cpp/#L3158

Bug#874833: marked as done ([boats] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 16:36:01 +
with message-id 
and subject line Bug#874833: fixed in boats 201908-1
has caused the Debian Bug report #874833,
regarding [boats] 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.)


-- 
874833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: boats
Version: 201307-1.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:

[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: boats
Source-Version: 201908-1

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

Debian distribution maintenance software
pp.
Thibaut Gridel  (supplier of updated boats package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Aug 2019 09:38:04 +0200
Source: boats
Architecture: source
Version: 201908-1
Distribution: unstable
Urgency: medium
Maintainer: Thibaut Gridel 
Changed-By: Thibaut Gridel 
Closes: 834409 874833
Changes:
 boats (201908-1) unstable; urgency=medium
 .
   * ACK'ing NMU. Thanks: Matthias Klose
   * New upstream release. Closes: #834409, #874833.
   * Updating debhelper.
   * Fixing debian/control: lintian problems and Vcs-changes.
   * Bumping Standards to 4.4.0(no change).
Checksums-Sha1:
 753cf821f5128379042470adc0f89c168f57439a 1837 boats_201908-1.dsc
 66c5f66e0d207e234a0acf76e6410e04bc0fb340 214350 boats_201908.orig.tar.gz
 982927445dbe83b88a1d735f371b98ac358e0dd3 2228 boats_201908-1.debian.tar.xz
 5a473f031fa13aab4a354ca6196b226a1c77a761 5237 boats_201908-1_source.buildinfo
Checksums-Sha256:
 8a489e3f077a233b0e1049425a5f83b04dcaf83782982eda68a02cd7540a9fd1 1837 
boats_201908-1.dsc
 439bcd4d87485bdc2b17437a4cae2808bb831dfd3608960c4b606c0d36d74c08 214350 
boats_201908.orig.tar.gz
 323c598ff71d30947e601ac1e469c33c749bf11d0643b65a459d1b4c8d8b9c2f 2228 
boats_201908-1.debian.tar.xz
 4b756f187f47d0820c234977408098f129ecb456d7ff52e7e0cf5a5a292bd402 5237 
boats_201908-1_source.buildinfo
Files:
 0ff64428f79ee64d3ad49b9a23d975e1 1837 x11 optional boats_201908-1.dsc
 62e68137f45b144ef21017685d5dd7bf 214350 x11 optional boats_201908.orig.tar.gz
 e95f1c87d9e599c5e235dc4c439c39d7 2228 x11 optional boats_201908-1.debian.tar.xz
 

Bug#875021: marked as done ([libdbusmenu-qt] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 16:36:45 +
with message-id 
and subject line Bug#875021: fixed in libdbusmenu-qt 0.9.3+16.04.20160218-2
has caused the Debian Bug report #875021,
regarding [libdbusmenu-qt] 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.)


-- 
875021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdbusmenu-qt
Version: 0.9.3+16.04.20160218-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:

[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: libdbusmenu-qt
Source-Version: 0.9.3+16.04.20160218-2

We believe that the bug you reported is fixed in the latest version of
libdbusmenu-qt, 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.
Scott Kitterman  (supplier of updated libdbusmenu-qt 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Aug 2019 12:07:44 -0400
Source: libdbusmenu-qt
Architecture: source
Version: 0.9.3+16.04.20160218-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Krap Maintainers 
Changed-By: Scott Kitterman 
Closes: 875021
Changes:
 libdbusmenu-qt (0.9.3+16.04.20160218-2) unstable; urgency=medium
 .
   * Team upload.
   * Drop Qt4 support (Closes: #875021)
   * Update Vcs-* to point to salsa
   * Update symbols files
Checksums-Sha1:
 d0b7622b158873892a71ba9c3875841d05612098 2359 
libdbusmenu-qt_0.9.3+16.04.20160218-2.dsc
 c93c2fc1271edb46377b287ea59e7cb9f114946b 5268 
libdbusmenu-qt_0.9.3+16.04.20160218-2.debian.tar.xz
 71a2641d19220192b465067cb29f4b0c1af075c3 10026 
libdbusmenu-qt_0.9.3+16.04.20160218-2_source.buildinfo
Checksums-Sha256:
 485ab4c4c624955571d8de5151ac2486edefcdeba7062f05546bff0b18cf43a7 2359 
libdbusmenu-qt_0.9.3+16.04.20160218-2.dsc
 a7bc4f85ab574005b277b56dd24a1ec9720ca98446adb185f8dd3c2ae064b9f5 5268 
libdbusmenu-qt_0.9.3+16.04.20160218-2.debian.tar.xz
 0407758c8d4251f24587cbc2ec50c8cfda2cde47d62efd34dbd1494ea32be9b2 10026 
libdbusmenu-qt_0.9.3+16.04.20160218-2_source.buildinfo
Files:
 85a0b65ab5786716816aabe554ed1d19 2359 libs optional 
libdbusmenu-qt_0.9.3+16.04.20160218-2.dsc
 4ecf4427202e276a63251e294254c5ac 5268 libs optional 
libdbusmenu-qt_0.9.3+16.04.20160218-2.debian.tar.xz
 

Bug#935717: marked as done (FTBFS: tests fail)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 16:05:35 +
with message-id 
and subject line Bug#935717: fixed in haskell-mode 16.1-8
has caused the Debian Bug report #935717,
regarding FTBFS: tests fail
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.)


-- 
935717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: haskell-mode
Version: 16.1-6
Severity: serious
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

during a no-change rebuild of haskell-mode I noticed the tests are failing.

failing tests:

,
| 4 unexpected results:
|FAILED  haskell-cabal-compute-checksum-1
|FAILED  haskell-cabal-compute-next-prev-section-1
|FAILED  haskell-cabal-enum-targets-1
|FAILED  haskell-cabal-get-field-1
`

full log:

https://buildd.debian.org/status/fetch.php?pkg=haskell-mode=all=16.1-7=1566743946=log

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

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

Versions of packages haskell-mode depends on:
ii  elpa-haskell-mode  16.1-6

haskell-mode recommends no packages.

haskell-mode suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl1io0EACgkQA0U5G1Wq
FSHJAw/9FhtGmX6sgT/fR/muGtTG+zUDoslYpjsBEnrReRRJhlIwxCIYK49Hl2ew
oZbSRxo4h5Ut9alewSB5pstt6h+4xZ3+hZ/B8OaPk116BMxsed3LMUWRDZXnjUnn
JaffmLeykgMtLFi2eLyeE/L+x8VyLnUby3jFAfUM0NsHLvMy+aMlyYa1hMi3Fe1t
/xGixtXMhLA7X7/4lEYd8yOFh+6Krqh4g/UoAPogS9V6fgQeIXIgnCLWHPv074Gv
uH36OIQgjTiQChwe4GBlgEvdwrNiU9XZ4QNd9fpR2azFlz/KgDDQf1JvD7Dncecy
q1fZy1iZkbUO5BwVez84Y2lfwF+rse9GU+8O5ykFg0x4KllJJe2deNW2nRXNex8B
0g7xFCwvIlDH84Pxicl3NMyCZ30d4Mp0qZ2c15CuYhLZ5QRKzj4Q1oVQSQdFzHZv
+CNWAnGokkRnCIPCadzuJpF8U+63P2l/k/qSIkPv57obCuRhiqmGhrIq/MkSDvtw
a6ZAQIEMiMARDUkAmieG6nKGfhBVeCR0jxqUzi1F1rr5XPYFabdb5V7PzUNNRynu
3N+EOkW+3QUFbnpatN/SuZ4pXtXa8Lqg0rtbKaJ3q4/WLL+xstr5pUL7wJHyW8Fr
th2DoEN9qT5AmTPHscZxfsG23InsnDizvhKswjHqRMMPoBV7+kw=
=nxBG
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: haskell-mode
Source-Version: 16.1-8

We believe that the bug you reported is fixed in the latest version of
haskell-mode, 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.
David Bremner  (supplier of updated haskell-mode package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Aug 2019 12:33:08 -0300
Source: haskell-mode
Architecture: source
Version: 16.1-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacs addons team 

Changed-By: David Bremner 
Closes: 935717
Changes:
 haskell-mode (16.1-8) unstable; urgency=medium
 .
   * Team upload
   * Try without single-debian-patch in debian/source/options (Closes:
 #935717).
   * don't use dgit --quilt=auto
Checksums-Sha1:
 1216427599daa496e65b2d1cd16938a0fd70f547 2280 haskell-mode_16.1-8.dsc
 cab2b80f64fa3ae9d3445bfda86fa0c422bebde3 6932 haskell-mode_16.1-8.debian.tar.xz
Checksums-Sha256:
 391282a05bb1fd6888e82b9f3e90baad983c9acb8e86822845b68d14763ae02f 2280 
haskell-mode_16.1-8.dsc
 cb9277d23b785900fe0e80d8bb5dbc60edf392806e118acb7c0283c8af687a08 6932 
haskell-mode_16.1-8.debian.tar.xz
Files:
 64151f588f2fc69a25d866002e275f05 2280 lisp optional haskell-mode_16.1-8.dsc
 6828b8b87a02fb42617c91b71f38fd9e 6932 lisp optional 
haskell-mode_16.1-8.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl1irI0ACgkQA0U5G1Wq
FSF++Q/6Al8XX078l8CGPqiXVeVrcNT0RNeBKNdtnq+0fJX+o/LR+to2VT0SfOLz
G/6Vh7afkV4yks7UjDlIiNC57Sbzr2cHgpqRHGiZDCaQAVS8nM17tO7hU9bfVjY3
o22vODPPAE9hXcUYPBRN9nRy4xktNMa+4tlGwXoMb3VwF1Cs9fEZHBCV5eDFV9JO

Bug#874808: marked as done ([akonadi4] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:45:47 +
with message-id 
and subject line Bug#935718: Removed package(s) from unstable
has caused the Debian Bug report #874808,
regarding [akonadi4] 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.)


-- 
874808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: akonadi4
Version: 1.13.0-11
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 ---
Version: 1.13.0-12+rm

Dear submitter,

as the package akonadi4 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/935718

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#925810: marked as done (qjson: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:44:18 +
with message-id 
and subject line Bug#935705: Removed package(s) from unstable
has caused the Debian Bug report #925810,
regarding qjson: ftbfs with GCC-9
to be marked as done.

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

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


-- 
925810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925810
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qjson
Version: 0.8.1-3
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/qjson_0.8.1-3_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
3/3 Test #3: testserializer ...***Failed0.01 sec
* Start testing of TestSerializer *
Config: Using QTest library 4.8.7, Qt 4.8.7
PASS   : TestSerializer::initTestCase()
PASS   : TestSerializer::testReadWriteEmptyDocument()
FAIL!  : TestSerializer::testReadWrite(basic array) Compared values are not the 
same
   Actual (result): QVariant(QVariantList,)
   Expected (writtenThenRead): QVariant(QVariantList,)
   Loc: [/<>/tests/serializer/testserializer.cpp(95)]
FAIL!  : TestSerializer::testReadWrite(int array) Compared values are not the 
same
   Actual (result): QVariant(QVariantList,)
   Expected (writtenThenRead): QVariant(QVariantList,)
   Loc: [/<>/tests/serializer/testserializer.cpp(95)]
FAIL!  : TestSerializer::testReadWrite(array of various numbers) Compared 
values are not the same
   Actual (result): QVariant(QVariantList,)
   Expected (writtenThenRead): QVariant(QVariantList,)
   Loc: [/<>/tests/serializer/testserializer.cpp(95)]
FAIL!  : TestSerializer::testReadWrite(complicated document) Compared values 
are not the same
   Actual (result): QVariant(QVariantMap,)
   Expected (writtenThenRead): QVariant(QVariantMap,)
   Loc: [/<>/tests/serializer/testserializer.cpp(95)]
FAIL!  : TestSerializer::testReadWrite(complicated array) Compared values are 
not the same
   Actual (result): QVariant(QVariantList,)
   Expected (writtenThenRead): QVariant(QVariantList,)
   Loc: [/<>/tests/serializer/testserializer.cpp(95)]
PASS   : TestSerializer::testValueNull()
PASS   : TestSerializer::testValueString()
FAIL!  : TestSerializer::testValueStringList(simple QStringList) 
'expected.exactMatch( serializedUnicode )' returned FALSE. (Expected regexp 
"\s*\[\s*"hello"\s*,\s*"world"\s*\]\s*" but got "[ "hello" ]".)
   Loc: [/<>/tests/serializer/testserializer.cpp(203)]
FAIL!  : TestSerializer::testValueStringList(simple QStringList) 
'expected.exactMatch( serializedUnicode )' returned FALSE. (Expected regexp 
"\s*\{\s*"value"\s*:\s*\[\s*"hello"\s*,\s*"world"\s*\]\s*\}\s*" but got "{ 
"value" : [ "hello" ] }".)
   Loc: [/<>/tests/serializer/testserializer.cpp(203)]
FAIL!  : TestSerializer::testValueHashMap() 'mIt != vmap.constEnd()' returned 
FALSE. ()
   Loc: [/<>/tests/serializer/testserializer.cpp(529)]
PASS   : TestSerializer::testValueInteger()
PASS   : TestSerializer::testValueDouble()
PASS   : TestSerializer::testSetDoublePrecision()
PASS   : TestSerializer::testValueFloat()
PASS   : TestSerializer::testValueBoolean()
PASS   : TestSerializer::testSpecialNumbers()
FAIL!  : TestSerializer::testIndentation(test indents) Compared values are not 
the same
   Actual (serialized): 7B 22 66 6F 6F 22 3A 30 7D
   Expected (expected_compact): 7B 22 66 6F 

Bug#875139: marked as done ([qjson] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:44:18 +
with message-id 
and subject line Bug#935705: Removed package(s) from unstable
has caused the Debian Bug report #875139,
regarding [qjson] 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.)


-- 
875139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qjson
Version: 0.8.1-3
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 ---
Version: 0.8.1-3+rm

Dear submitter,

as the package qjson 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/935705

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#935568: marked as done (sphinx-issuetracker: should this package be removed?)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:40:12 +
with message-id 
and subject line Bug#935700: Removed package(s) from unstable
has caused the Debian Bug report #935568,
regarding sphinx-issuetracker: should this package be removed?
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.)


-- 
935568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinx-issuetracker
Severity: serious

Hello,
sphinx-issuetracker is currently incompatible with python3.7:

Exception occurred:
  File 
"/build/sphinx-issuetracker-0.11/sphinxcontrib/issuetracker/__init__.py", line 
282, in connect_builtin_tracker
from sphinxcontrib.issuetracker.resolvers import BUILTIN_ISSUE_TRACKERS
  File 
"/build/sphinx-issuetracker-0.11/sphinxcontrib/issuetracker/resolvers.py", line 
138
except ImportError, e:
  ^
SyntaxError: invalid syntax


it has a very low popcon value

It has no reverse-dependencies and it's currently one of the few r-deps of
python-debianbts.

Should we just remove this package from Debian?

Thanks,
Sandro

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

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

Dear submitter,

as the package sphinx-issuetracker 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/935700

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#925718: marked as done (ioprocess: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:39:08 +
with message-id 
and subject line Bug#935693: Removed package(s) from unstable
has caused the Debian Bug report #925718,
regarding ioprocess: ftbfs with GCC-9
to be marked as done.

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

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


-- 
925718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925718
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ioprocess
Version: 0.15.1-3
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/ioprocess_0.15.1-3_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
./src/exported-functions.c:93: undefined reference to `g_propagate_error'
/usr/bin/ld: ioprocess-exported-functions.o: in function `exp_rename':
./src/exported-functions.c:112: undefined reference to `g_propagate_error'
/usr/bin/ld: ioprocess-exported-functions.o: in function `exp_memstat':
./src/exported-functions.c:141: undefined reference to 
`g_quark_from_static_string'
/usr/bin/ld: ./src/exported-functions.c:141: undefined reference to 
`g_set_error'
/usr/bin/ld: ./src/exported-functions.c:136: undefined reference to 
`g_quark_from_static_string'
/usr/bin/ld: ioprocess-exported-functions.o: in function `exp_echo':
./src/exported-functions.c:177: undefined reference to `g_propagate_error'
/usr/bin/ld: ioprocess-exported-functions.o: in function `exp_unlink':
./src/exported-functions.c:195: undefined reference to `g_propagate_error'
/usr/bin/ld: ioprocess-exported-functions.o: in function `exp_rmdir':
./src/exported-functions.c:208: undefined reference to `g_propagate_error'
/usr/bin/ld: ioprocess-exported-functions.o: in function `exp_mkdir':
./src/exported-functions.c:226: undefined reference to `g_propagate_error'
/usr/bin/ld: ioprocess-exported-functions.o: in function `exp_chmod':
./src/exported-functions.c:244: undefined reference to `g_propagate_error'
/usr/bin/ld: ioprocess-exported-functions.o:./src/exported-functions.c:261: 
more undefined references to `g_propagate_error' follow
/usr/bin/ld: ioprocess-exported-functions.o: in function `exp_fsyncPath':
./src/exported-functions.c:421: undefined reference to 
`g_quark_from_static_string'
/usr/bin/ld: ioprocess-exported-functions.o: in function `exp_symlink':
./src/exported-functions.c:442: undefined reference to `g_propagate_error'
/usr/bin/ld: ioprocess-exported-functions.o: in function `exp_listdir':
./src/exported-functions.c:462: undefined reference to `g_propagate_error'
/usr/bin/ld: ./src/exported-functions.c:468: undefined reference to 
`g_quark_from_static_string'
/usr/bin/ld: ioprocess-exported-functions.o: in function `exp_glob':
./src/exported-functions.c:506: undefined reference to `g_propagate_error'
/usr/bin/ld: ./src/exported-functions.c:515: undefined reference to 
`g_quark_from_static_string'
/usr/bin/ld: ./src/exported-functions.c:519: undefined reference to 
`g_quark_from_static_string'
/usr/bin/ld: ioprocess-exported-functions.o: in function `exp_writefile':
./src/exported-functions.c:560: undefined reference to `g_propagate_error'
/usr/bin/ld: ./src/exported-functions.c:573: undefined reference to 
`g_base64_decode'
/usr/bin/ld: ./src/exported-functions.c:609: undefined reference to 
`g_quark_from_static_string'
/usr/bin/ld: ./src/exported-functions.c:593: undefined reference 

Bug#876905: marked as done (qtwebkit should not be released with buster)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:35:34 +
with message-id 
and subject line Bug#935668: Removed package(s) from unstable
has caused the Debian Bug report #876905,
regarding qtwebkit should not be released 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.)


-- 
876905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876905
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtwebkit
Version: 2.3.4.dfsg-9.1
Severity: serious
Tags: buster sid

qtwebkit should not be release with buster
(RC bugs are already open against all r-deps).
--- End Message ---
--- Begin Message ---
Version: 2.3.4.dfsg-10+rm

Dear submitter,

as the package qtwebkit 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/935668

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#925662: marked as done (criu: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:36:02 +
with message-id 
and subject line Bug#935675: Removed package(s) from unstable
has caused the Debian Bug report #925662,
regarding criu: ftbfs with GCC-9
to be marked as done.

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

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


-- 
925662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:criu
Version: 3.8.1-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/criu_3.8.1-1_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
  DEP  images/timer.pb-c.d
  PBCC images/sa.pb-c.c
  DEP  images/pipe-data.pb-c.d
  PBCC images/mnt.pb-c.c
  DEP  images/sk-packet.pb-c.d
  PBCC images/tcp-stream.pb-c.c
  PBCC images/pipe.pb-c.c
  DEP  images/pstree.pb-c.d
  DEP  images/fs.pb-c.d
  PBCC images/signalfd.pb-c.c
  PBCC images/fh.pb-c.c
  DEP  images/eventpoll.pb-c.d
  DEP  images/eventfd.pb-c.d
  DEP  images/remap-file-path.pb-c.d
  DEP  images/fifo.pb-c.d
  PBCC images/ghost-file.pb-c.c
  PBCC images/regfile.pb-c.c
  DEP  images/ns.pb-c.d
  PBCC images/core-aarch64.pb-c.c
  PBCC images/core-arm.pb-c.c
  PBCC images/core-ppc64.pb-c.c
  PBCC images/core-s390.pb-c.c
  PBCC images/core-x86.pb-c.c
  DEP  images/cpuinfo.pb-c.d
  DEP  images/stats.pb-c.d
  PBCC images/sit.pb-c.c
  DEP  images/opts.pb-c.d
  DEP  images/ext-file.pb-c.d
  DEP  images/pagemap.pb-c.d
  DEP  images/tty.pb-c.d
  PBCC images/netdev.pb-c.c
  DEP  images/tun.pb-c.d
  DEP  images/vma.pb-c.d
  DEP  images/ipc-sem.pb-c.d
  DEP  images/ipc-msg.pb-c.d
  DEP  images/ipc-shm.pb-c.d
  DEP  images/packet-sock.pb-c.d
  DEP  images/sk-netlink.pb-c.d
  DEP  images/sk-inet.pb-c.d
  DEP  images/sk-unix.pb-c.d
  DEP  images/mm.pb-c.d
  DEP  images/timerfd.pb-c.d
  DEP  images/sa.pb-c.d
  DEP  images/mnt.pb-c.d
  DEP  images/tcp-stream.pb-c.d
  DEP  images/pipe.pb-c.d
  DEP  images/signalfd.pb-c.d
  PBCC images/fsnotify.pb-c.c
  DEP  images/fh.pb-c.d
  DEP  images/ghost-file.pb-c.d
  DEP  images/regfile.pb-c.d
  PBCC images/fdinfo.pb-c.c
  PBCC images/core.pb-c.c
  DEP  images/core-aarch64.pb-c.d
  DEP  images/core-arm.pb-c.d
  DEP  images/core-ppc64.pb-c.d
  DEP  images/core-s390.pb-c.d
  DEP  images/core-x86.pb-c.d
  DEP  images/sit.pb-c.d
  DEP  images/fsnotify.pb-c.d
  PBCC images/inventory.pb-c.c
  DEP  images/core.pb-c.d
  DEP  images/netdev.pb-c.d
  DEP  images/fdinfo.pb-c.d
  DEP  images/inventory.pb-c.d
make[2]: Nothing to be done for 'all'.
make[1]: Leaving directory '/<>'
dh_auto_build: make -j4 "INSTALL=install --strip-program=true" returned exit 
code 2
make: *** [debian/rules:9: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2
--- End Message ---
--- Begin Message ---
Version: 3.8.1-1+rm

Dear submitter,

as the package criu 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 

Bug#796536: marked as done (criu: package not yet ready for stable release / fast moving (blocking bug))

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:36:02 +
with message-id 
and subject line Bug#935675: Removed package(s) from unstable
has caused the Debian Bug report #796536,
regarding criu: package not yet ready for stable release / fast moving 
(blocking bug)
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.)


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

I'm filling this bug as blocking bug for criu for testing. Criu is by
now still a fast moving project and at this point it is not yet ready
to be effectively used in a stable release.
--- End Message ---
--- Begin Message ---
Version: 3.8.1-1+rm

Dear submitter,

as the package criu 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/935675

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#875159: marked as done ([qtwebkit] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:35:34 +
with message-id 
and subject line Bug#935668: Removed package(s) from unstable
has caused the Debian Bug report #875159,
regarding [qtwebkit] 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.)


-- 
875159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtwebkit
Version: 2.3.4.dfsg-9.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:

[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 ---
Version: 2.3.4.dfsg-10+rm

Dear submitter,

as the package qtwebkit 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/935668

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#875146: marked as done ([qt-at-spi] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:34:58 +
with message-id 
and subject line Bug#935662: Removed package(s) from unstable
has caused the Debian Bug report #875146,
regarding [qt-at-spi] 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.)


-- 
875146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qt-at-spi
Version: 0.4.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 ---
Version: 0.4.0-9+rm

Dear submitter,

as the package qt-at-spi 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/935662

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#934268: marked as done (kde4libs: CVE-2019-14744)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:34:27 +
with message-id 
and subject line Bug#935666: Removed package(s) from unstable
has caused the Debian Bug report #934268,
regarding kde4libs: CVE-2019-14744
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.)


-- 
934268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kconfig
Version: 5.54.0-1
Severity: grave
Tags: patch security upstream
Justification: user security hole
Control: found -1 5.28.0-2
Control: clone -1 -2
Control: reassign -2 src:kde4libs 4:4.14.38-3
Control: retitle -2 kde4libs: CVE-2019-14744
Control: found -2 4:4.14.26-2

Hi,

The following vulnerability was published for kconfig.

CVE-2019-14744[0]:
| In KDE Frameworks KConfig before 5.61.0, malicious desktop files and
| configuration files lead to code execution with minimal user
| interaction. This relates to libKF5ConfigCore.so, and the mishandling
| of .desktop and .directory files, as demonstrated by a shell command
| on an Icon line in a .desktop file.


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-14744
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14744
[1] https://kde.org/info/security/advisory-20190807-1.txt
[2] 
https://cgit.kde.org/kconfig.git/commit/?id=5d3e71b1d2ecd2cb2f910036e614ffdfc895aa22
[3] 
https://cgit.kde.org/kdelibs.git/commit/?id=2c3762feddf7e66cf6b64d9058f625a715694a00

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 4:4.14.38-4+rm

Dear submitter,

as the package kde4libs 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/935666

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#925724: marked as done (kde4libs: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:34:27 +
with message-id 
and subject line Bug#935666: Removed package(s) from unstable
has caused the Debian Bug report #925724,
regarding kde4libs: ftbfs with GCC-9
to be marked as done.

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

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


-- 
925724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kde4libs
Version: 4:4.14.38-3
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/kde4libs_4.14.38-3_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
In file included from /usr/include/qt4/QtDBus/qdbusabstractinterface.h:51,
 from /usr/include/qt4/QtDBus/QtDBus:5,
 from 
/<>/obj-x86_64-linux-gnu/kdeui/knotify_interface.h:21,
 from 
/<>/obj-x86_64-linux-gnu/kdeui/knotify_interface.cpp:12:
/usr/include/qt4/QtDBus/qdbusextratypes.h:93:25: note: because 
'QDBusObjectPath' has user-provided 'QDBusObjectPath& 
QDBusObjectPath::operator=(const QDBusObjectPath&)'
   93 | inline QDBusObjectPath ::operator=(const 
QDBusObjectPath &_path)
  | ^~~
In file included from /usr/include/qt4/QtCore/qobject.h:50,
 from /usr/include/qt4/QtCore/QObject:1,
 from 
/<>/obj-x86_64-linux-gnu/kdeui/knotify_interface.h:14,
 from 
/<>/obj-x86_64-linux-gnu/kdeui/knotify_interface.cpp:12:
/usr/include/qt4/QtCore/qlist.h:412:17: warning: implicitly-declared 
'QDBusObjectPath::QDBusObjectPath(const QDBusObjectPath&)' is deprecated 
[-Wdeprecated-copy]
  412 | new (current) T(*reinterpret_cast(src));
  | ^~~
In file included from /usr/include/qt4/QtDBus/qdbusabstractinterface.h:51,
 from /usr/include/qt4/QtDBus/QtDBus:5,
 from 
/<>/obj-x86_64-linux-gnu/kdeui/knotify_interface.h:21,
 from 
/<>/obj-x86_64-linux-gnu/kdeui/knotify_interface.cpp:12:
/usr/include/qt4/QtDBus/qdbusextratypes.h:93:25: note: because 
'QDBusObjectPath' has user-provided 'QDBusObjectPath& 
QDBusObjectPath::operator=(const QDBusObjectPath&)'
   93 | inline QDBusObjectPath ::operator=(const 
QDBusObjectPath &_path)
  | ^~~
In file included from /usr/include/qt4/QtCore/qobject.h:50,
 from /usr/include/qt4/QtCore/QObject:1,
 from 
/<>/obj-x86_64-linux-gnu/kdeui/knotify_interface.h:14,
 from 
/<>/obj-x86_64-linux-gnu/kdeui/knotify_interface.cpp:12:
/usr/include/qt4/QtCore/qlist.h: In instantiation of 'void 
QList::node_copy(QList::Node*, QList::Node*, QList::Node*) [with T 
= QDBusSignature]':
/usr/include/qt4/QtCore/qlist.h:711:9:   required from 'void 
QList::detach_helper(int) [with T = QDBusSignature]'
/usr/include/qt4/QtCore/qlist.h:725:5:   required from 'void 
QList::detach_helper() [with T = QDBusSignature]'
/usr/include/qt4/QtCore/qlist.h:122:80:   required from 'QList::QList(const 
QList&) [with T = QDBusSignature]'
/usr/include/qt4/QtCore/qmetatype.h:142:12:   required from 'void* 
qMetaTypeConstructHelper(const T*) [with T = QList]'
/usr/include/qt4/QtCore/qmetatype.h:196:18:   required from 'int 

Bug#874945: marked as done ([kde4libs] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:34:27 +
with message-id 
and subject line Bug#935666: Removed package(s) from unstable
has caused the Debian Bug report #874945,
regarding [kde4libs] 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.)


-- 
874945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kde4libs
Version: 4:4.14.35-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:

[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 ---
Version: 4:4.14.38-4+rm

Dear submitter,

as the package kde4libs 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/935666

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#784479: marked as done ([kde4libs] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:34:27 +
with message-id 
and subject line Bug#935666: Removed package(s) from unstable
has caused the Debian Bug report #784479,
regarding [kde4libs] Qt4's WebKit removal
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.)


-- 
784479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kde4libs
Version: 4:4.14.2-5
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal

Dear Debian Qt/KDE Maintainers ,

As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce].

[announce] 


Basically we are about to get the latest Qt4 point release and upstream is
migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream
support for maintaining Qt4's WebKit.

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library 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. In
order to ease the transition time we have provided Wheezy backports for Qt5.

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/packagingqtstuff.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

Ana,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 4:4.14.38-4+rm

Dear submitter,

as the package kde4libs 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/935666

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#875318: marked as done (QJson removal form Buster)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:30:26 +
with message-id 
and subject line Bug#935663: Removed package(s) from unstable
has caused the Debian Bug report #875318,
regarding QJson removal form 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.)


-- 
875318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kdepimlibs
Version: 4:4.14.10-7+b2
Severity: important
User: debian-qt-...@lists.debian.org
Usertags: qjson-removal

Hi! As you might know we the Qt/KDE team are preparing to remove Qt4.
This means that we need to remove QJson from the archive too.

In order to make this move, all packages directly or indirectly depending on
the QJson library 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.

Noreover porting from QJson to Qt5's QJson (part of the official API) tends to
be quite easy.

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


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

Kernel: Linux 4.12.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 4:4.14.10-11+rm

Dear submitter,

as the package kdepimlibs 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/935663

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#874937: marked as done ([kdepimlibs] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:30:26 +
with message-id 
and subject line Bug#935663: Removed package(s) from unstable
has caused the Debian Bug report #874937,
regarding [kdepimlibs] 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.)


-- 
874937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kdepimlibs
Version: 4:4.14.10-7
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 ---
Version: 4:4.14.10-11+rm

Dear submitter,

as the package kdepimlibs 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/935663

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#874944: marked as done ([kde-runtime] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:29:15 +
with message-id 
and subject line Bug#935664: Removed package(s) from unstable
has caused the Debian Bug report #874944,
regarding [kde-runtime] 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.)


-- 
874944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874944
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kde-runtime
Version: 4:16.08.3-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:

[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 ---
Version: 4:17.08.3-2.1+rm

Dear submitter,

as the package kde-runtime 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/935664

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#874932: marked as done ([kate4] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:29:50 +
with message-id 
and subject line Bug#935222: Removed package(s) from unstable
has caused the Debian Bug report #874932,
regarding [kate4] 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.)


-- 
874932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kate4
Version: 4:4.14.3-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 ---
Version: 4:4.14.3-5+rm

Dear submitter,

as the package kate4 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/935222

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#784477: marked as done ([kde-runtime] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:29:15 +
with message-id 
and subject line Bug#935664: Removed package(s) from unstable
has caused the Debian Bug report #784477,
regarding [kde-runtime] Qt4's WebKit removal
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.)


-- 
784477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kde-runtime
Version: 4:4.14.2-2
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal

Dear Debian Qt/KDE Maintainers ,

As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce].

[announce] 


Basically we are about to get the latest Qt4 point release and upstream is
migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream
support for maintaining Qt4's WebKit.

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library 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. In
order to ease the transition time we have provided Wheezy backports for Qt5.

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/packagingqtstuff.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

Ana,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 4:17.08.3-2.1+rm

Dear submitter,

as the package kde-runtime 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/935664

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#874925: marked as done ([kactivities] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:28:01 +
with message-id 
and subject line Bug#935219: Removed package(s) from unstable
has caused the Debian Bug report #874925,
regarding [kactivities] 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.)


-- 
874925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kactivities
Version: 4:4.13.3-2
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 ---
Version: 4:4.13.3-2+rm

Dear submitter,

as the package kactivities 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/935219

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#933130: marked as done (FTBFS, not Django 2.2 ready)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:23:16 +
with message-id 
and subject line Bug#933130: fixed in python-django-debug-toolbar 1:2.0-1
has caused the Debian Bug report #933130,
regarding FTBFS, not Django 2.2 ready
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.)


-- 
933130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-django-debug-toolbar
Version: 1:1.9.1-1
Severity: serious
Tags: patch

Hi,

Please find attached to this bug report, a patch to remove Python2 support in
your package.

Since Django 2.2 was uploaded to Sid (with Py2 removal), your package can't
build. After applying the attached patch, I get this, which shows missing Django
2.2 compatibility.

FYI, I know how to fix the MIDDLEWARE issue (I did fix similar issues in other
packages), but I don't know about the other errors.

dh_auto_test
I: pybuild base:217: PYTHONPATH=. DJANGO_SETTINGS_MODULE=tests.settings 
django-admin test tests
Creating test database for alias 'default'...
..s...EEEF......
==
ERROR: test_check_good_configuration 
(tests.test_integration.DebugToolbarSystemChecksTestCase)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/django/test/utils.py", line 373, in inner
return func(*args, **kwargs)
  File "/<>/tests/test_integration.py", line 339, in 
test_check_good_configuration
messages = run_checks()
  File "/usr/lib/python3/dist-packages/django/core/checks/registry.py", line 
72, in run_checks
new_errors = check(app_configs=app_configs)
  File "/usr/lib/python3/dist-packages/django/contrib/admin/checks.py", line 
111, in check_dependencies
if not 
_contains_subclass('django.contrib.auth.middleware.AuthenticationMiddleware', 
settings.MIDDLEWARE):
  File "/usr/lib/python3/dist-packages/django/contrib/admin/checks.py", line 
41, in _contains_subclass
for path in candidate_paths:
TypeError: 'NoneType' object is not iterable

==
ERROR: test_check_gzip_middleware_error 
(tests.test_integration.DebugToolbarSystemChecksTestCase)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/django/test/utils.py", line 373, in inner
return func(*args, **kwargs)
  File "/<>/tests/test_integration.py", line 365, in 
test_check_gzip_middleware_error
messages = run_checks()
  File "/usr/lib/python3/dist-packages/django/core/checks/registry.py", line 
72, in run_checks
new_errors = check(app_configs=app_configs)
  File "/usr/lib/python3/dist-packages/django/contrib/admin/checks.py", line 
111, in check_dependencies
if not 
_contains_subclass('django.contrib.auth.middleware.AuthenticationMiddleware', 
settings.MIDDLEWARE):
  File "/usr/lib/python3/dist-packages/django/contrib/admin/checks.py", line 
41, in _contains_subclass
for path in candidate_paths:
TypeError: 'NoneType' object is not iterable

==
ERROR: test_check_missing_middleware_error 
(tests.test_integration.DebugToolbarSystemChecksTestCase)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/django/test/utils.py", line 373, in inner
return func(*args, **kwargs)
  File "/<>/tests/test_integration.py", line 344, in 
test_check_missing_middleware_error
messages = run_checks()
  File "/usr/lib/python3/dist-packages/django/core/checks/registry.py", line 
72, in run_checks
new_errors = check(app_configs=app_configs)
  File "/usr/lib/python3/dist-packages/django/contrib/admin/checks.py", line 
111, in check_dependencies
if not 
_contains_subclass('django.contrib.auth.middleware.AuthenticationMiddleware', 
settings.MIDDLEWARE):
  File "/usr/lib/python3/dist-packages/django/contrib/admin/checks.py", line 
41, in _contains_subclass
for path in candidate_paths:
TypeError: 'NoneType' object is not iterable

==
FAIL: test_middleware_factory_functions_supported 
(tests.test_integration.DebugToolbarSystemChecksTestCase)
--
Traceback (most recent call last):
  File 

Bug#935699: gdm3: uninstallable on s390x

[Simon McVittie]

On Sun, 25 Aug 2019 at 12:52:08 +0200, Ivo De Decker wrote:
> On s390x, gdm3 isn't installable, because it needs gnome-shell, which FTBFS
> there. So either the dependency should be dropped or the binaries for gdm3 on
> s390x should be removed.

gdm3 genuinely does require gnome-shell at runtime: its GUI is gnome-shell
running in a special mode.

We thought we had addressed this by making gdm3 build-depend on gjs, but
unfortunately mozjs60 and gjs have now been partially fixed on s390x and
work sufficiently well for their own tests to pass, but not well enough
for gnome-shell to pass *its* tests and build successfully.

Is there anything better we can do to resolve this, short of either making
gdm3 build-depend on gnome-shell (which I'm a little reluctant to do
because it isn't actually necessary at build-time and the dependency chain
is extensive), or hard-coding a list of every (release?) architecture
except s390x in gnome-shell's d/control?

I'm going to assume that making gnome-shell tests pass on s390x is not
feasible, given that there has not been any s390x porter involvement
at any point in this saga. I suspect gnome-shell has no practical use
on s390x in any case, since $15K mainframes don't tend to have a GPU
or display.

smcv

Bug#925686: marked as done (fmtlib: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:17:38 +
with message-id 
and subject line Bug#925686: fixed in fmtlib 5.3.0+ds-1
has caused the Debian Bug report #925686,
regarding fmtlib: ftbfs with GCC-9
to be marked as done.

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

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


-- 
925686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fmtlib
Version: 5.2.1+ds-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/fmtlib_5.2.1+ds-2_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
-- Detecting CXX compile features - done
-- Version: 5.2.1
-- Build type: None
-- Looking for open
-- Looking for open - found
CMake Warning at /usr/src/googletest/googlemock/CMakeLists.txt:40 (project):
  VERSION keyword not followed by a value or was followed by a value that
  expanded to nothing.


CMake Warning at /usr/src/googletest/googletest/CMakeLists.txt:47 (project):
  VERSION keyword not followed by a value or was followed by a value that
  expanded to nothing.


-- Found PythonInterp: /usr/bin/python3.7 (found version "3.7.3") 
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Check if compiler accepts -pthread
-- Check if compiler accepts -pthread - yes
-- Found Threads: TRUE  
-- Performing Test HAVE_FNO_DELETE_NULL_POINTER_CHECKS
-- Performing Test HAVE_FNO_DELETE_NULL_POINTER_CHECKS - Success
-- FMT_PEDANTIC: on
-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

CMAKE_EXPORT_NO_PACKAGE_REGISTRY


-- Build files have been written to: 
/<>/fmtlib-5.2.1+ds/obj-x86_64-linux-gnu
make[1]: Leaving directory '/<>/fmtlib-5.2.1+ds'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/fmtlib-5.2.1+ds'
dh_auto_build
cd obj-x86_64-linux-gnu && make -j1
make[2]: Entering directory '/<>/fmtlib-5.2.1+ds/obj-x86_64-linux-gnu'
/usr/bin/cmake -S/<>/fmtlib-5.2.1+ds 
-B/<>/fmtlib-5.2.1+ds/obj-x86_64-linux-gnu --check-build-system 
CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start 
/<>/fmtlib-5.2.1+ds/obj-x86_64-linux-gnu/CMakeFiles 
/<>/fmtlib-5.2.1+ds/obj-x86_64-linux-gnu/CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make[3]: Entering directory '/<>/fmtlib-5.2.1+ds/obj-x86_64-linux-gnu'
make -f CMakeFiles/fmt.dir/build.make CMakeFiles/fmt.dir/depend
make[4]: Entering directory '/<>/fmtlib-5.2.1+ds/obj-x86_64-linux-gnu'
cd /<>/fmtlib-5.2.1+ds/obj-x86_64-linux-gnu && /usr/bin/cmake -E 
cmake_depends "Unix Makefiles" /<>/fmtlib-5.2.1+ds 
/<>/fmtlib-5.2.1+ds 
/<>/fmtlib-5.2.1+ds/obj-x86_64-linux-gnu 
/<>/fmtlib-5.2.1+ds/obj-x86_64-linux-gnu 
/<>/fmtlib-5.2.1+ds/obj-x86_64-linux-gnu/CMakeFiles/fmt.dir/DependInfo.cmake
 --color=
Scanning dependencies of target fmt
make[4]: Leaving directory '/<>/fmtlib-5.2.1+ds/obj-x86_64-linux-gnu'
make -f CMakeFiles/fmt.dir/build.make CMakeFiles/fmt.dir/build
make[4]: Entering directory '/<>/fmtlib-5.2.1+ds/obj-x86_64-linux-gnu'
[  2%] Building CXX object CMakeFiles/fmt.dir/src/format.cc.o
/usr/bin/c++   -I/<>/fmtlib-5.2.1+ds/include  -g -O2 
-fdebug-prefix-map=/<>/fmtlib-5.2.1+ds=. -fstack-protector-strong 
-Wformat 

Bug#935620: marked as done (thrift: FTBFS on amd64)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 15:10:11 +
with message-id 
and subject line Bug#935620: fixed in thrift 0.11.0-5
has caused the Debian Bug report #935620,
regarding thrift: 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.)


-- 
935620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:thrift
version: 0.11.0-4
severity: serious
tags: ftbfs

Hi,

A binnmu of thrift in unstable fails on amd64:

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

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: thrift
Source-Version: 0.11.0-5

We believe that the bug you reported is fixed in the latest version of
thrift, 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.
Laszlo Boszormenyi (GCS)  (supplier of updated thrift 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, 24 Aug 2019 15:47:34 +
Source: thrift
Binary: golang-thrift-dev libthrift-0.11.0 libthrift-0.11.0-dbgsym 
libthrift-c-glib-dev libthrift-c-glib0 libthrift-c-glib0-dbgsym libthrift-dev 
libthrift-perl php-thrift python-thrift python-thrift-dbg python3-thrift 
python3-thrift-dbg thrift-compiler thrift-compiler-dbgsym
Architecture: source amd64 all
Version: 0.11.0-5
Distribution: experimental
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 golang-thrift-dev - Go language support for Thrift
 libthrift-0.11.0 - Thrift C++ library
 libthrift-c-glib-dev - Thrift glib library (development headers)
 libthrift-c-glib0 - Thrift glib library
 libthrift-dev - Thrift C++ library (development headers)
 libthrift-perl - Perl language support for Thrift
 php-thrift - PHP language support for Thrift
 python-thrift - Python library for Thrift
 python-thrift-dbg - Python library for Thrift (debug symbols)
 python3-thrift - Python 3 library for Thrift
 python3-thrift-dbg - Python library for Thrift (debug symbols)
 thrift-compiler - code generator/compiler for Thrift definitions
Closes: 913724 935620
Changes:
 thrift (0.11.0-5) experimental; urgency=medium
 .
   * Fix Python 3 packaging.
   * Sync with Ubuntu.
   * Update Standards-Version to 4.4.0 .
 .
   [ Adam Cecile  ]
   * Build python3 package (closes: #913724).
 .
   [ Gianfranco Costamagna  ]
   * Export HOME to make the build happy (closes: #935620).
   * Fix another failure due to new go with upstream patch.
Checksums-Sha1:
 e20722b8170bc41acde0fa7a569f2b143a0cbdfe 3114 thrift_0.11.0-5.dsc
 a06d8127dc9e96750d76ee014c13b1f53bc0f465 77692 thrift_0.11.0-5.debian.tar.xz
 093226afdb21e54eab0aa3c958be87f7a6a5beca 105524 
golang-thrift-dev_0.11.0-5_amd64.deb
 520941f90d053933dc560808c41917c56bfca41e 6814936 
libthrift-0.11.0-dbgsym_0.11.0-5_amd64.deb
 35193df42ead0b67c5658aa4960665515aeb286f 441072 
libthrift-0.11.0_0.11.0-5_amd64.deb
 c72537ac6d01c3178fb8fad02dce2176cbb846fb 118496 
libthrift-c-glib-dev_0.11.0-5_amd64.deb
 6670a8452b33df2b95161545f18855c39bbe7548 194712 
libthrift-c-glib0-dbgsym_0.11.0-5_amd64.deb
 346f78edc5952ed5e53b37f7422502a724e0ac18 102660 
libthrift-c-glib0_0.11.0-5_amd64.deb
 168adf87298ff70afb82f885047d39532b914f26 609080 
libthrift-dev_0.11.0-5_amd64.deb
 af63d1ef1795f3760995ba95e6fc47392832173d 77872 libthrift-perl_0.11.0-5_all.deb
 827786774f61932c0ad2e2bcbe0a3928214958f0 93744 php-thrift_0.11.0-5_amd64.deb
 a6e3a7b0a159317d60ef2483aef5deae5be870f3 228444 
python-thrift-dbg_0.11.0-5_amd64.deb
 725826fb071c6bf3cb43dcbc3396f3dea8437041 116044 
python-thrift_0.11.0-5_amd64.deb
 b9ead63da6e79c4fe36d3d623cb5c832d6bc8824 284992 
python3-thrift-dbg_0.11.0-5_amd64.deb
 c76bc37befd4a8aaf34c32eb1e71296512eecab5 117260 
python3-thrift_0.11.0-5_amd64.deb
 e488332ed651b95fc92e6eb62b3527ee0b3e9590 30511064 
thrift-compiler-dbgsym_0.11.0-5_amd64.deb
 c93ae40da1ec4d8716d4bf60afac88cb03f3cedb 1473800 
thrift-compiler_0.11.0-5_amd64.deb
 4768aa607bcc2b92d596627bc119311d56c5d271 28978 thrift_0.11.0-5_amd64.buildinfo
Checksums-Sha256:
 

Bug#935717: FTBFS: tests fail

[David Bremner]

Package: haskell-mode
Version: 16.1-6
Severity: serious
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

during a no-change rebuild of haskell-mode I noticed the tests are failing.

failing tests:

,
| 4 unexpected results:
|FAILED  haskell-cabal-compute-checksum-1
|FAILED  haskell-cabal-compute-next-prev-section-1
|FAILED  haskell-cabal-enum-targets-1
|FAILED  haskell-cabal-get-field-1
`

full log:

https://buildd.debian.org/status/fetch.php?pkg=haskell-mode=all=16.1-7=1566743946=log

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

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

Versions of packages haskell-mode depends on:
ii  elpa-haskell-mode  16.1-6

haskell-mode recommends no packages.

haskell-mode suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl1io0EACgkQA0U5G1Wq
FSHJAw/9FhtGmX6sgT/fR/muGtTG+zUDoslYpjsBEnrReRRJhlIwxCIYK49Hl2ew
oZbSRxo4h5Ut9alewSB5pstt6h+4xZ3+hZ/B8OaPk116BMxsed3LMUWRDZXnjUnn
JaffmLeykgMtLFi2eLyeE/L+x8VyLnUby3jFAfUM0NsHLvMy+aMlyYa1hMi3Fe1t
/xGixtXMhLA7X7/4lEYd8yOFh+6Krqh4g/UoAPogS9V6fgQeIXIgnCLWHPv074Gv
uH36OIQgjTiQChwe4GBlgEvdwrNiU9XZ4QNd9fpR2azFlz/KgDDQf1JvD7Dncecy
q1fZy1iZkbUO5BwVez84Y2lfwF+rse9GU+8O5ykFg0x4KllJJe2deNW2nRXNex8B
0g7xFCwvIlDH84Pxicl3NMyCZ30d4Mp0qZ2c15CuYhLZ5QRKzj4Q1oVQSQdFzHZv
+CNWAnGokkRnCIPCadzuJpF8U+63P2l/k/qSIkPv57obCuRhiqmGhrIq/MkSDvtw
a6ZAQIEMiMARDUkAmieG6nKGfhBVeCR0jxqUzi1F1rr5XPYFabdb5V7PzUNNRynu
3N+EOkW+3QUFbnpatN/SuZ4pXtXa8Lqg0rtbKaJ3q4/WLL+xstr5pUL7wJHyW8Fr
th2DoEN9qT5AmTPHscZxfsG23InsnDizvhKswjHqRMMPoBV7+kw=
=nxBG
-END PGP SIGNATURE-

Bug#842892: marked as done (java.lang.UnsatisfiedLinkError: libz3java.so: undefined symbol: Z3_solver_get_model)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 14:28:17 +
with message-id 
and subject line Bug#842892: fixed in z3 4.4.1-1~deb9u1
has caused the Debian Bug report #842892,
regarding java.lang.UnsatisfiedLinkError: libz3java.so: undefined symbol: 
Z3_solver_get_model
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.)


-- 
842892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libz3-jni
Version: 4.4.1-0.3
Severity: important

Dear Maintainer,

The Java example program included with z3 [1] fails to run.

With the package in unstable, the error reported is:

Exception in thread "main" java.lang.UnsatisfiedLinkError: no libz3java in 
java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1867)
at java.lang.Runtime.loadLibrary0(Runtime.java:870)
at java.lang.System.loadLibrary(System.java:1122)
at com.microsoft.z3.Native.(Native.java:14)
at com.microsoft.z3.Global.ToggleWarningMessages(Global.java:86)
at JavaExample.main(JavaExample.java:2286)

This is a misleading error (the correct library to load is "z3java", not
"libz3java"), caused by hiding an earlier exception [2].

I applied the following patch locally:

--- a/scripts/update_api.py
+++ b/scripts/update_api.py
@@ -570,8 +570,9 @@
 java_native.write('  public static native void 
setInternalErrorHandler(long ctx);\n\n')

 java_native.write('  static {\n')
-java_native.write('try { System.loadLibrary("z3java"); }\n')
-java_native.write('catch (UnsatisfiedLinkError ex) { 
System.loadLibrary("libz3java"); }\n')
+java_native.write('System.loadLibrary("z3java");\n')
+#java_native.write('try { System.loadLibrary("z3java"); }\n')
+#java_native.write('catch (UnsatisfiedLinkError ex) { 
System.loadLibrary("libz3java"); }\n')
 java_native.write('  }\n')

 java_native.write('\n')

With the try-catch removed, the actual exception is revealed:

Exception in thread "main" java.lang.UnsatisfiedLinkError: 
/usr/lib/x86_64-linux-gnu/jni/libz3java.so: 
/usr/lib/x86_64-linux-gnu/jni/libz3java.so: undefined symbol: 
Z3_solver_get_model
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1941)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1857)
at java.lang.Runtime.loadLibrary0(Runtime.java:870)
at java.lang.System.loadLibrary(System.java:1122)
at com.microsoft.z3.Native.(Native.java:13)
at com.microsoft.z3.Global.ToggleWarningMessages(Global.java:86)
at JavaExample.main(JavaExample.java:2286)

I confirmed that libz3 does in fact export the symbol in question:

$ nm -gD /usr/lib/x86_64-linux-gnu/libz3.so | grep Z3_solver_get_model
000a6220 T Z3_solver_get_model

It looks like the JNI library is not actually linked against libz3?

$ ldd /usr/lib/x86_64-linux-gnu/jni/libz3java.so
linux-vdso.so.1 (0x7ffdc41e7000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fb61bcf5000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fb61b9f1000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fb61b7da000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fb61b43c000)
/lib64/ld-linux-x86-64.so.2 (0x55c3b7a27000)

[1] http://sources.debian.net/src/z3/4.4.1-0.3/examples/java/JavaExample.java/
[2] http://sources.debian.net/src/z3/4.4.1-0.3/scripts/update_api.py/#L574

thanks,
Ryan

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

Kernel: Linux 4.7.0-0.bpo.1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: z3
Source-Version: 4.4.1-1~deb9u1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated z3 package)

(This 

Bug#935615: [Aptitude-devel] Bug#935615: aptitude: FTBFS on amd64

[Axel Beckert]

Hi Manuel,

Ivo De Decker wrote:
> A binnmu of aptitude in unstable fails on amd64:
> 
> https://buildd.debian.org/status/package.php?p=aptitude

Do you happen to know if any of your recent commits to the master
branch already fixes this issue? I haven't found any which looks
fitting on a first glance...

If you can pinpoint one or more commits, I can cherry pick them and do
a quick upload to fix this issue.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#910577: marked as done (gdb-multiarch: libbabeltrace1 dependency not tight enough)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 14:27:32 +
with message-id 
and subject line Bug#931147: fixed in babeltrace 1.5.6-2+deb10u1
has caused the Debian Bug report #931147,
regarding gdb-multiarch: libbabeltrace1 dependency not tight enough
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.)


-- 
931147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gdb-multiarch
Version: 8.1-4
Severity: important

gdb-multiarch requires libbabeltrace-ctf1.

  --\ Versions of libbabeltrace-ctf1 (3)

p1.5.1-1
i1.5.6-1
i A  libbabeltrace1 1.5.6-1

Apparently the build process picks up the fact that libbabeltrace-1.5.6-1
contains the -ctf sub-library, but then doesn't depend on >=1.5.6.
Thus 1.5.1 ends up being installed, which doesn't contain the plugin.

Manually updating libbabeltrace1 to 1.5.6-1 fixes the problem.

-- System Information:
Debian Release: buster/sid
  APT prefers stable
  APT policy: (800, 'stable'), (750, 'testing'), (700, 'unstable'), (650, 
'oldstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages gdb-multiarch depends on:
ii  gdb 7.12-6+b2
pn  libbabeltrace-ctf1  
ii  libbabeltrace1  1.5.6-1
ii  libc6   2.27-3
ii  libexpat1   2.2.5-3
pn  libipt2 
ii  liblzma55.2.2-1.3
ii  libncurses5 6.1+20180714-1
ii  libncursesw66.1+20180210-4
ii  libpython2.72.7.15-1
pn  libpython3.5
ii  libpython3.63.6.6-1
ii  libreadline66.3-9
ii  libreadline77.0-5
ii  libtinfo5   6.1+20180714-1
ii  libtinfo6   6.1+20180210-4
ii  zlib1g  1:1.2.11.dfsg-1

gdb-multiarch recommends no packages.

gdb-multiarch suggests no packages.
--- End Message ---
--- Begin Message ---
Source: babeltrace
Source-Version: 1.5.6-2+deb10u1

We believe that the bug you reported is fixed in the latest version of
babeltrace, 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.
Andreas Beckmann  (supplier of updated babeltrace 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, 24 Aug 2019 12:10:28 +0200
Source: babeltrace
Architecture: source
Version: 1.5.6-2+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Jon Bernard 
Changed-By: Andreas Beckmann 
Closes: 931147
Changes:
 babeltrace (1.5.6-2+deb10u1) buster; urgency=medium
 .
   [ Andreas Beckmann ]
   * Non-maintainer upload.
   * Backport symbols fix from 1.5.7-1.
 .
   [ Michael Jeanson ]
   * Bump ctf symbols depends to post merge version (Closes: #931147)
Checksums-Sha1:
 30bb4fb1d372f10ae9c9ca0fb8eb383f603c9ba6 2698 babeltrace_1.5.6-2+deb10u1.dsc
 954c6f7554dcb85f80e1e7ea6a6fb62405ac23a5 11444 
babeltrace_1.5.6-2+deb10u1.debian.tar.xz
 ca762b672d875eb4e9716fadae091bbb0ae5ef2e 6577 
babeltrace_1.5.6-2+deb10u1_source.buildinfo
Checksums-Sha256:
 8ff1a25f9f98e406440e29d6dc3a8ffa3e8b7271abf344254f42178844617d3e 2698 
babeltrace_1.5.6-2+deb10u1.dsc
 3aa17dfd2e93fb86b1bb7cbc5796bbbcb7faf38a76e17ad63fcfe780a165c4c0 11444 
babeltrace_1.5.6-2+deb10u1.debian.tar.xz
 4ca63899163b97cd88e6c2f9a67d93bdc05efe71160445cbbe65c85164912d56 6577 
babeltrace_1.5.6-2+deb10u1_source.buildinfo
Files:
 68173e3f31e7554af8fd60860c447ab3 2698 libs optional 
babeltrace_1.5.6-2+deb10u1.dsc
 17bd995fa4bc84849c17baf1d129dbff 11444 libs optional 
babeltrace_1.5.6-2+deb10u1.debian.tar.xz
 fabd3ed19ef62b71ce139c8dc16086c1 6577 libs optional 
babeltrace_1.5.6-2+deb10u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAl1hDm0QHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCFt5EACGzmtLPVaDgdj1w8FXdGXQdjEL89HYcujR

Bug#842892: marked as done (java.lang.UnsatisfiedLinkError: libz3java.so: undefined symbol: Z3_solver_get_model)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 14:27:50 +
with message-id 
and subject line Bug#842892: fixed in z3 4.4.1-1~deb10u1
has caused the Debian Bug report #842892,
regarding java.lang.UnsatisfiedLinkError: libz3java.so: undefined symbol: 
Z3_solver_get_model
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.)


-- 
842892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libz3-jni
Version: 4.4.1-0.3
Severity: important

Dear Maintainer,

The Java example program included with z3 [1] fails to run.

With the package in unstable, the error reported is:

Exception in thread "main" java.lang.UnsatisfiedLinkError: no libz3java in 
java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1867)
at java.lang.Runtime.loadLibrary0(Runtime.java:870)
at java.lang.System.loadLibrary(System.java:1122)
at com.microsoft.z3.Native.(Native.java:14)
at com.microsoft.z3.Global.ToggleWarningMessages(Global.java:86)
at JavaExample.main(JavaExample.java:2286)

This is a misleading error (the correct library to load is "z3java", not
"libz3java"), caused by hiding an earlier exception [2].

I applied the following patch locally:

--- a/scripts/update_api.py
+++ b/scripts/update_api.py
@@ -570,8 +570,9 @@
 java_native.write('  public static native void 
setInternalErrorHandler(long ctx);\n\n')

 java_native.write('  static {\n')
-java_native.write('try { System.loadLibrary("z3java"); }\n')
-java_native.write('catch (UnsatisfiedLinkError ex) { 
System.loadLibrary("libz3java"); }\n')
+java_native.write('System.loadLibrary("z3java");\n')
+#java_native.write('try { System.loadLibrary("z3java"); }\n')
+#java_native.write('catch (UnsatisfiedLinkError ex) { 
System.loadLibrary("libz3java"); }\n')
 java_native.write('  }\n')

 java_native.write('\n')

With the try-catch removed, the actual exception is revealed:

Exception in thread "main" java.lang.UnsatisfiedLinkError: 
/usr/lib/x86_64-linux-gnu/jni/libz3java.so: 
/usr/lib/x86_64-linux-gnu/jni/libz3java.so: undefined symbol: 
Z3_solver_get_model
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1941)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1857)
at java.lang.Runtime.loadLibrary0(Runtime.java:870)
at java.lang.System.loadLibrary(System.java:1122)
at com.microsoft.z3.Native.(Native.java:13)
at com.microsoft.z3.Global.ToggleWarningMessages(Global.java:86)
at JavaExample.main(JavaExample.java:2286)

I confirmed that libz3 does in fact export the symbol in question:

$ nm -gD /usr/lib/x86_64-linux-gnu/libz3.so | grep Z3_solver_get_model
000a6220 T Z3_solver_get_model

It looks like the JNI library is not actually linked against libz3?

$ ldd /usr/lib/x86_64-linux-gnu/jni/libz3java.so
linux-vdso.so.1 (0x7ffdc41e7000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fb61bcf5000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fb61b9f1000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fb61b7da000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fb61b43c000)
/lib64/ld-linux-x86-64.so.2 (0x55c3b7a27000)

[1] http://sources.debian.net/src/z3/4.4.1-0.3/examples/java/JavaExample.java/
[2] http://sources.debian.net/src/z3/4.4.1-0.3/scripts/update_api.py/#L574

thanks,
Ryan

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

Kernel: Linux 4.7.0-0.bpo.1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: z3
Source-Version: 4.4.1-1~deb10u1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated z3 package)

(This 

Bug#931147: marked as done (gdb depends on newer libbabeltrace)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 14:27:32 +
with message-id 
and subject line Bug#931147: fixed in babeltrace 1.5.6-2+deb10u1
has caused the Debian Bug report #931147,
regarding gdb depends on newer libbabeltrace
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.)


-- 
931147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gdb
Version: 8.2.1-2
Severity: important

gdb fails to run when the buster package is installed, but libraries from 
stretch are still installed:

gdb: error while loading shared libraries: libbabeltrace-ctf.so.1: cannot open 
shared object file: No such file or directory

The package dependencies should require newer libraries.

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

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

Versions of packages gdb depends on:
ii  libbabeltrace1  1.5.1-1
ii  libc6   2.28-10
ii  libexpat1   2.2.0-2+deb9u1
ii  libipt2 2.0-2
ii  liblzma55.2.2-1.2+b1
ii  libncursesw66.1+20181013-2
ii  libpython3.73.7.3-2
ii  libreadline77.0-3
ii  libtinfo6   6.1+20181013-2
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages gdb recommends:
ii  libc6-dbg [libc-dbg]  2.28-10

Versions of packages gdb suggests:
pn  gdb-doc
pn  gdbserver  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: babeltrace
Source-Version: 1.5.6-2+deb10u1

We believe that the bug you reported is fixed in the latest version of
babeltrace, 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.
Andreas Beckmann  (supplier of updated babeltrace 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, 24 Aug 2019 12:10:28 +0200
Source: babeltrace
Architecture: source
Version: 1.5.6-2+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Jon Bernard 
Changed-By: Andreas Beckmann 
Closes: 931147
Changes:
 babeltrace (1.5.6-2+deb10u1) buster; urgency=medium
 .
   [ Andreas Beckmann ]
   * Non-maintainer upload.
   * Backport symbols fix from 1.5.7-1.
 .
   [ Michael Jeanson ]
   * Bump ctf symbols depends to post merge version (Closes: #931147)
Checksums-Sha1:
 30bb4fb1d372f10ae9c9ca0fb8eb383f603c9ba6 2698 babeltrace_1.5.6-2+deb10u1.dsc
 954c6f7554dcb85f80e1e7ea6a6fb62405ac23a5 11444 
babeltrace_1.5.6-2+deb10u1.debian.tar.xz
 ca762b672d875eb4e9716fadae091bbb0ae5ef2e 6577 
babeltrace_1.5.6-2+deb10u1_source.buildinfo
Checksums-Sha256:
 8ff1a25f9f98e406440e29d6dc3a8ffa3e8b7271abf344254f42178844617d3e 2698 
babeltrace_1.5.6-2+deb10u1.dsc
 3aa17dfd2e93fb86b1bb7cbc5796bbbcb7faf38a76e17ad63fcfe780a165c4c0 11444 
babeltrace_1.5.6-2+deb10u1.debian.tar.xz
 4ca63899163b97cd88e6c2f9a67d93bdc05efe71160445cbbe65c85164912d56 6577 
babeltrace_1.5.6-2+deb10u1_source.buildinfo
Files:
 68173e3f31e7554af8fd60860c447ab3 2698 libs optional 
babeltrace_1.5.6-2+deb10u1.dsc
 17bd995fa4bc84849c17baf1d129dbff 11444 libs optional 
babeltrace_1.5.6-2+deb10u1.debian.tar.xz
 fabd3ed19ef62b71ce139c8dc16086c1 6577 libs optional 
babeltrace_1.5.6-2+deb10u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAl1hDm0QHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCFt5EACGzmtLPVaDgdj1w8FXdGXQdjEL89HYcujR
3eoAZvzcMAMrshLe/GCW13vHNKVOsbSDpLwnoewlnNV0QO6F2/jFM/QIMbPLtVcc
6GIpkuTxdxyTICpcpL9tuUFUUf4r/RiJkDTDf5013IMDveFT8J+ThQNwmv5Nk96V
A8nHmpebIIvKb/8A/QqpeKuAGnCCksLsXbMH4OkhNOVObNxassBAOAKdF/JN7qdW
LjykpIwWq/5xvg2WgqNoFX8apCISpc44xSOra8soFyU4F75mEV5xBQ31bYAUdkFG
PgTLX5OowK/gAtxb0zuwZmT4gwfrG8GjITV+ok3TeumFi6NT8IfUy8TTorda7Cii
dbCPnVGpJo2W95w2+65K7NuZ9B8FJ1NrqYMKAqGbKhHn1nZQgxssQeCjAda+VTUf

Processed: tagging 935615

[Debian Bug Tracking System]

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

> tags 935615 + confirmed
Bug #935615 [src:aptitude] aptitude: FTBFS on amd64
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Processed: FTBFS with PROJ 6

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #931940 [src:sumo] sumo: FTBFS with PROJ 6
Severity set to 'serious' from 'important'

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

Processed: FTBFS with PROJ 6

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #931948 [src:r-cran-lwgeom] r-cran-lwgeom: FTBFS with PROJ 6
Severity set to 'serious' from 'important'

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

Processed: FTBFS with PROJ 6

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #931944 [src:vtk7] vtk7: FTBFS with PROJ 6
Severity set to 'serious' from 'important'

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

Processed: FTBFS with PROJ 6

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #931914 [src:octave-octproj] octave-octproj: FTBFS with PROJ 6
Severity set to 'serious' from 'important'

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

Processed: FTBFS with PROJ 6

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #931935 [src:openorienteering-mapper] openorienteering-mapper: FTBFS with 
PROJ 6
Severity set to 'serious' from 'important'

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

Processed: reassign 934600 to cufflinks, fixed 934600 in 2.2.1+dfsg.1-4, affects 934600

[Debian Bug Tracking System]

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

> reassign 934600 cufflinks 2.2.1+dfsg.1-3
Bug #934600 {Done: Alexandre Mestiashvili } 
[cufflinks,gffread] cufflinks,gffread: both ship /usr/bin/gffread
Bug reassigned from package 'cufflinks,gffread' to 'cufflinks'.
No longer marked as found in versions cufflinks/2.2.1+dfsg.1-3 and 
gffread/0.11.4-1.
No longer marked as fixed in versions cufflinks/2.2.1+dfsg.1-4.
Bug #934600 {Done: Alexandre Mestiashvili } [cufflinks] 
cufflinks,gffread: both ship /usr/bin/gffread
Marked as found in versions cufflinks/2.2.1+dfsg.1-3.
> fixed 934600 2.2.1+dfsg.1-4
Bug #934600 {Done: Alexandre Mestiashvili } [cufflinks] 
cufflinks,gffread: both ship /usr/bin/gffread
Marked as fixed in versions cufflinks/2.2.1+dfsg.1-4.
> affects 934600 + gffread
Bug #934600 {Done: Alexandre Mestiashvili } [cufflinks] 
cufflinks,gffread: both ship /usr/bin/gffread
Added indication that 934600 affects gffread
> thanks
Stopping processing here.

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

Bug#935713: src:thrift: Incomplete debian/copyright

[Scott Kitterman]

Package: src:thrift
Version: 0.11.0-4
Severity: serious
Justification: Policy 2.3

While reviewing your package in New, I noticed omissions from debian/
copyright.  Since this problem also exists in the current package, I am
filing this bug rather than rejecting the package.

At a minimum, the following copyright/licenses are missing:

compile: GPL 2+

compiler/cpp/src/thrift/thrifty.hh: GPL 3+ + Bison exception
compiler/cpp/src/thrift/thrifty.cc

lib/php/src/ext/thrift_protocol/run-tests.php: PHP 3.01
Note: it references a LICENSE file that appears to be missing.

Please keep https://ftp-master.debian.org/php-license.html in mind when
you update your debian/copyright.

ylwrap: GPL 2+

build/cmake/FindGLIB.cmake: BSD 2 clause

Scott K

Bug#935714: python-os-net-config (build-) depends on cruft package.

[Peter Michael Green]

Package: python-os-net-config
Version: 0.1.0-1
Severity: serious
Tags: bullseye, sid

python-os-net-config (build-)depends on the python-oslo.config binary 
package which is no longer built by the corresponding source package.


I see no reverse-depends, should this package simply be removed?

Bug#935712: FTBFS: dh-elpa error

[David Bremner]

Source: emacs-git-modes
Version: 1.2.8-2
Severity: serious
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

during a no-change rebuild of this package I noticed that it fails to build 
from source

It looks like there is an incompatibility with the latest
dh-elpa.

,
| Generating git-modes-autoloads.el
| Installing...
| make[1]: Leaving directory '/<>'
|dh_elpa -i
| dh_elpa: emacs -batch -Q -l package --eval (add-to-list 
'package-directory-list "/usr/share/emacs/site-lisp/elpa") --eval (add-to-list 
'package-directory-list "/usr/share/emacs/site-lisp/elpa-src") -f 
package-initialize -l dh-elpa.el -f dhelpa-batch-install-file 
debian/elpa-git-modes//usr/share/emacs/site-lisp/elpa-src ./git-modes.el 
/<>/debian/.debhelper/elpa 1566734946 returned exit code 255
| E: The Debian version  cannot be used as an ELPA version.
| See dh_elpa(1) HINTS for how to deal with this.
| make: *** [debian/rules:4: binary-indep] Error 255
| dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2
`

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

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl1ikmgACgkQA0U5G1Wq
FSEbQw/+OXMkwDg7Pw5Cid5/x8GM8JRnWFKypsEBGeRDE0qdNHaGY0ep2uv67lLE
+1OwHCkuMMIkPNgb0qxX66iXejatKKtFefQ/YE6GwtIHaPlr1Fjdi+CeJpRF/PIP
06II9XCzcb8fIPHhQWgOnkO+8ZqQtI26l5piLYqrehfd3ztsoCmP0mlRPtkdYKUJ
0/Ia3t61yq0KYdn8KKNEZD3GPLAbz4c/9zr8FFp30u4qvX6KanYZ7G5Dix1H8sti
Y3fDOzLmjhyLOzVi2Vg7nb1ZzuPqEH0zAcQT+G0ONibuR+Ttfa/Z7StSLaF9Kf1p
W1SoM/TupjYxuDdwGEfnoDVHiBdrWRRkAHngp6vmX/N7odCB3pPGxuM05kOKJhch
duv4hWzMdu6iPoS9Qfm/3FSQe5mUN0bTqfAogRJjTLnXPNkufV1pTmCfE8sT2TJj
O12EUmhB0ELdPVEak6QS2kSXfV6y04iImOkS27lTiE+xtxrrt8RCxRGwZ06Z6lv6
ubdUG9yREAhDsLVFcCISF2YiwhCZ2Pv0wQuTQE+XJLhNyIa1D1v1sOeP02+z8A0o
hCRDB4Hv9H2PzDIY9eDEUOc3VJxk5y21Kj9BLaSAA6aVpbmHCQTjXlS2AdDIE/0j
tB4r5TrT+3mEsM2tt5rv/isPoIg5ZZt+Hbk+8rftdxOw/z9lhU4=
=N3Up
-END PGP SIGNATURE-

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

[Francesco Poli]

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?


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


pgpnsuhEVyN3W.pgp
Description: PGP signature

Bug#866980: marked as done (biomaj-watcher: fails to upgrade from 'jessie': Exception in thread "main" java.lang.UnsupportedClassVersionError: WatcherConfigurator : Unsupported major.minor version 52.

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 13:47:29 +
with message-id 
and subject line Bug#866980: fixed in biomaj-watcher 1.2.2-4+deb9u1
has caused the Debian Bug report #866980,
regarding biomaj-watcher: fails to upgrade from 'jessie': Exception in thread 
"main" java.lang.UnsupportedClassVersionError: WatcherConfigurator : 
Unsupported major.minor version 52.0
to be marked as done.

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

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


-- 
866980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866980
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: biomaj-watcher
Version: 1.2.2-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' fails.

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

  Setting up biomaj-watcher (1.2.2-4) ...
  Exception in thread "main" java.lang.UnsupportedClassVersionError: 
WatcherConfigurator : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:803)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
  dpkg: error processing package biomaj-watcher (--configure):
   subprocess installed post-installation script returned error exit status 1


This was observed while doing two-stage upgrade tests:
  apt-get upgrade && apt-get dist-upgrade
during the apt-get upgrade phase.
A one-stage upgrade (only apt-get dist-upgrade) works fine.

There is probably an insufficiently versioned Depends (or Breaks) ...
but I have no idea which package could be meant with 
  Unsupported major.minor version 52.0


cheers,

Andreas


biomaj-watcher_1.2.2-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: biomaj-watcher
Source-Version: 1.2.2-4+deb9u1

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

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

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated biomaj-watcher 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, 23 Aug 2019 09:38:25 +0200
Source: biomaj-watcher
Binary: biomaj-watcher
Architecture: source
Version: 1.2.2-4+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Beckmann 
Description:
 biomaj-watcher - biological data-bank updater - web interface
Closes: 866980
Changes:
 biomaj-watcher (1.2.2-4+deb9u1) stretch; urgency=medium
 .
   * Bump (Build-)Depends to default-jdk (>= 2:1.8) (aka openjdk-8). Prevent
 partial upgrades from jessie (openjdk-7): biomaj-watcher needs to be run
 with the same jdk version that was used for building.  (Closes: #866980)
Checksums-Sha1:
 e9bd9cfff88b0c265464184164b716466594a3ef 2369 biomaj-watcher_1.2.2-4+deb9u1.dsc
 77b53f2a619d6126c8cf4a9cf39fc3c70398b69c 35472 
biomaj-watcher_1.2.2-4+deb9u1.debian.tar.xz
 b75fa3a5cfa9266733bcbe55e3b1256dae1bbaea 7122 
biomaj-watcher_1.2.2-4+deb9u1_source.buildinfo
Checksums-Sha256:
 b39be508f7db1722592517a21a42033e2d1b6d96e575e6a1440e4da06bf0205e 2369 
biomaj-watcher_1.2.2-4+deb9u1.dsc
 1c50b1a22c11e7d5fceba254591d41d0ba66d1cfbd2e826e6ad9cdc9ef5edc56 35472 
biomaj-watcher_1.2.2-4+deb9u1.debian.tar.xz
 

Bug#935711: FTBFS: looks for docker?

[David Bremner]

Source: emacs-pdf-tools
Version: 0.90-2
Severity: serious
Justification: ftbfs

During a no-change rebuild I noticed this packge does not build from source.
Apologies if this is caused by the way I created the source package:

%  dgit --quilt=auto push-source --overwrite

A sample build log is at

https://buildd.debian.org/status/fetch.php?pkg=emacs-pdf-tools=amd64=0.90-2=1566739129=log

I'm not sure what it wants docker for, but here is the relevant portion of logs:

Creating Dockerfile for target gentoo
Creating Dockerfile for target centos-7
cat docker/templates/gentoo.Dockerfile.in docker/templates/Dockerfile.in > 
docker/gentoo.Dockerfile
Creating Dockerfile for target fedora-25
cat docker/templates/centos-7.Dockerfile.in docker/templates/Dockerfile.in > 
docker/centos-7.Dockerfile
Creating Dockerfile for target arch
cat docker/templates/fedora-25.Dockerfile.in docker/templates/Dockerfile.in > 
docker/fedora-25.Dockerfile
cat docker/templates/arch.Dockerfile.in docker/templates/Dockerfile.in > 
docker/arch.Dockerfile
Creating Dockerfile for target ubuntu-16
cat docker/templates/ubuntu-16.Dockerfile.in docker/templates/Dockerfile.in > 
docker/ubuntu-16.Dockerfile
Creating Dockerfile for target fedora-24
Creating Dockerfile for target debian-9
cat docker/templates/fedora-24.Dockerfile.in docker/templates/Dockerfile.in > 
docker/fedora-24.Dockerfile
cat docker/templates/debian-9.Dockerfile.in docker/templates/Dockerfile.in > 
docker/debian-9.Dockerfile
Creating Dockerfile for target fedora-26
cat docker/templates/fedora-26.Dockerfile.in docker/templates/Dockerfile.in > 
docker/fedora-26.Dockerfile
Creating Dockerfile for target ubuntu-14
cat docker/templates/ubuntu-14.Dockerfile.in docker/templates/Dockerfile.in > 
docker/ubuntu-14.Dockerfile
Creating Dockerfile for target ubuntu-17
cat docker/templates/ubuntu-17.Dockerfile.in docker/templates/Dockerfile.in > 
docker/ubuntu-17.Dockerfile
Creating Dockerfile for target debian-8
cat docker/templates/debian-8.Dockerfile.in docker/templates/Dockerfile.in > 
docker/debian-8.Dockerfile
Building target gentoo
docker build -q -t epdfinfo/gentoo -f docker/gentoo.Dockerfile ../
Building target centos-7
make[3]: docker: Command not found
Building target fedora-25
docker build -q -t epdfinfo/centos-7 -f docker/centos-7.Dockerfile ../
make[3]: docker: Command not found
Building target arch
make[3]: *** [Makefile:30: docker/.gentoo.build] Error 127
make[3]: *** Waiting for unfinished jobs
make[3]: *** [Makefile:30: docker/.centos-7.build] Error 127
docker build -q -t epdfinfo/fedora-25 -f docker/fedora-25.Dockerfile ../
make[3]: docker: Command not found
make[3]: *** [Makefile:30: docker/.fedora-25.build] Error 127
docker build -q -t epdfinfo/arch -f docker/arch.Dockerfile ../
make[3]: docker: Command not found
make[3]: *** [Makefile:30: docker/.arch.build] Error 127
make[3]: Leaving directory '/<>/server/test'
make[2]: *** [Makefile:940: check-local] Error 2
make[2]: Leaving directory '/<>/server'
make[1]: *** [Makefile:801: check-am] Error 2
make[1]: Leaving directory '/<>/server'
dh_auto_test: cd server && make -j4 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:15: build-arch] Error 255
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Build finished at 2019-08-25T13:18:44Z

Finished




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

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

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

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 13:47:30 +
with message-id 
and subject line Bug#933743: fixed in libxslt 1.1.29-2.1+deb9u1
has caused the Debian Bug report #933743,
regarding LibXSLT in Debian stable has three unpatched security vulnerabilities
to be marked as done.

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

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Aug 2019 14:04:13 +0200
Source: libxslt
Architecture: source
Version: 1.1.29-2.1+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian XML/SGML Group 
Changed-By: Salvatore Bonaccorso 
Closes: 926895 931320 931321 933743
Changes:
 libxslt (1.1.29-2.1+deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * Fix security framework bypass (CVE-2019-11068) (Closes: #926895, #933743)
   * Fix uninitialized read of xsl:number token (CVE-2019-13117)
 (Closes: #931321, #933743)
   * Fix uninitialized read with UTF-8 grouping chars (CVE-2019-13118)
 (Closes: #931320, #933743)
Checksums-Sha1: 
 70e7c78198055d69973ac9b28354210e1f584886 2563 libxslt_1.1.29-2.1+deb9u1.dsc
 9963bba25c609012184ac5d815f6f6ab7b9b59b2 30436 
libxslt_1.1.29-2.1+deb9u1.debian.tar.xz
Checksums-Sha256: 
 a7b353c973bd0a66c85c2786c608d9059fafa7c4f58613e3ca5a47124f4c4bb6 2563 
libxslt_1.1.29-2.1+deb9u1.dsc
 1551bfcb01d176f629a4dbc9031617ecc35a8f1825fa470b4e9191115cb0f3dd 30436 
libxslt_1.1.29-2.1+deb9u1.debian.tar.xz
Files: 
 c8059916bf34e28bd0331b011459e2ff 2563 text optional 
libxslt_1.1.29-2.1+deb9u1.dsc
 1b6d060c87131f68cbd22b73edb59c17 30436 text optional 
libxslt_1.1.29-2.1+deb9u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl1hKpVfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89Ep3QP/2J21EvP7wvk8w5j/MEtLXO9MnrzdaAG
xuB5yALBpGpc1TzVOcXJQD1rMqqlGnPuUccUNgDUG82zL95WDGVO8jJcxkrTNVjm
GaNL+BMHxznlLudES62L49cMvV2IMRx416ZMJ8RSOrh8WB2DeXXicWBfXyS9/jpe
9GxM1lhlSBhPM9a4hlvj28D9NgsqdzJ7Us5T/Up/MV44mnQ0ZbeNX+Q3CSPScnd0
L11hgyc7P2OG2i2G/Fn6ueWreIjaj7VjCfw0tpl/JbczvXkrYomeKDKlyq8qX17d
eNIvHlePt8zCBwo4O7xM3J3l0w/uZKBKFIwaXq0eRGt/jI8hXnkJD6dtFtgqfddy
csXjwHr3TdlCFR25ROZDSDKrY3nf+K3ryWWgqWyYyp8FrmRbUSfaaHyG0sZM0TCJ
KTED6mAMoty6OyY8yLgG2zt76qs5P79iSKD6Ohz0EZxmqXu3yB6kta1gZed5xJ7E
VKjoAxm7EbJNpjuMrMtP7bRg0IZCx6EyiZMxjfOnf3AZfGB838wTEkJUgug+ZIg2
QVDl0X4j1uuwtNGeg53AA69D6tkY6YR1Nb4voKACj3t4OcVhm/UCZzYhM1B5/XtU
g/KLIpMv4Xfb/lLIxyD47dSpTCQtIcLl5SARcY3X0QWgUFEJwldjLFK2prDHi0wJ
ToSdTp969/Xe
=retl
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 13:47:31 +
with message-id 
and subject line Bug#934033: fixed in mitmproxy 0.18.2-6+deb9u1
has caused the Debian Bug report #934033,
regarding mitmproxy: FTBFS in stretch (failing tests, expired certificate)
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.)


-- 
934033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mitmproxy
Version: 0.18.2-6
Severity: serious
Tags: ftbfs

Dear maintainer:

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


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

Bug#933741: marked as done (qemu: CVE-2019-14378: heap buffer overflow during packet reassembly)

[Debian Bug Tracking System]

Your message dated Sun, 25 Aug 2019 13:47:32 +
with message-id 
and subject line Bug#933741: fixed in qemu 1:2.8+dfsg-6+deb9u8
has caused the Debian Bug report #933741,
regarding qemu: CVE-2019-14378: heap buffer overflow during packet reassembly
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.)


-- 
933741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qemu
Version: 1:3.1+dfsg-8
Severity: grave
Tags: security upstream
Control: clone -1 -2
Control: reassign -2 src:slirp4netns 0.3.1-1
Control: retitle -2 slirp4netns: CVE-2019-14459: heap buffer overflow during 
packet reassembly

Hi,

The following vulnerability was published for qemu (respective the
SLiRP networking implemenatation which is as well forked in
slirp4netns).

CVE-2019-14378[0]:
| ip_reass in ip_input.c in libslirp 4.0.0 has a heap-based buffer
| overflow via a large packet because it mishandles a case involving the
| first fragment.


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-14378
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14378
[1] 
https://gitlab.freedesktop.org/slirp/libslirp/commit/126c04acbabd7ad32c2b018fe10dfac2a3bc1210
[2] https://www.openwall.com/lists/oss-security/2019/08/01/2

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:2.8+dfsg-6+deb9u8

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

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

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

Debian distribution maintenance software
pp.
Michael Tokarev  (supplier of updated qemu 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, 09 Aug 2019 13:41:43 +0300
Source: qemu
Architecture: source
Version: 1:2.8+dfsg-6+deb9u8
Distribution: stretch-security
Urgency: medium
Maintainer: Debian QEMU Team 
Changed-By: Michael Tokarev 
Closes: 873012 931351 933741
Changes:
 qemu (1:2.8+dfsg-6+deb9u8) stretch-security; urgency=medium
 .
   [ Michal Arbet ]
   * Fix improper backport of CVE-2017-9524 fix that caused NBD
 connections to hang (Closes: #873012). Thanks to Geoffrey Thomas.
 - 
nbd-fully-initialize-client-in-case-of-failed-negotiation-CVE-2017-9524.patch:
   Don't move nbd_set_handlers before nbd_negotiate.
 - nbd-fix-regression-on-resiliency-to-port-scan-CVE-2017-9524.patch:
   Refresh.
 .
   [ Michael Tokarev ]
   * 
slirp-fix-heap-overflow-in-ip_reass-on-big-packet-input-CVE-2019-14378.patch
 bugfix in user-level networking
 Closes: #933741, CVE-2019-14378
   * qemu-bridge-helper-restrict-interface-name-to-IFNAMSIZ-CVE-2019-13164.patch
 Closes: #931351, CVE-2019-13164
   * integrate fix-md-clear-backport.patch into enable-md-clear.patch
 Thanks Moritz Mühlenhoff and Vincent Tondellier
   * device_tree-dont-use-load_image-CVE-2018-20815.patch
 fix unlikely overflow via saved image file size
 Closes: CVE-2018-20815
Checksums-Sha1:
 8fbeafc7c10912d1e137d6697b609f768b3232aa 5579 qemu_2.8+dfsg-6+deb9u8.dsc
 30ed9844cd7b60441d5532b4a7ff5bfcc04baebb 162212 
qemu_2.8+dfsg-6+deb9u8.debian.tar.xz
 351e1efe0fef0262cf2a2013aa0215679c2815af 7869 
qemu_2.8+dfsg-6+deb9u8_source.buildinfo
Checksums-Sha256:
 0a4987c1ba44baa25341ea25c3e3ac06358994abc662a7db5ed1545a191048c1 5579 
qemu_2.8+dfsg-6+deb9u8.dsc
 e3c0cd85409403824efe9ead0d5f110f2943c82986e460d5e3bb37bdb71d7fbb 162212 
qemu_2.8+dfsg-6+deb9u8.debian.tar.xz
 67b01392505ec7e5664968ba798324212027e9fca92f989e62f3580f9d1bc77c 7869 
qemu_2.8+dfsg-6+deb9u8_source.buildinfo
Files:
 0bf19074279779e05fe2bd9233a77409 5579 otherosfs optional 
qemu_2.8+dfsg-6+deb9u8.dsc
 15c10c07febb626168caff7f2e20f56e 162212 otherosfs optional 
qemu_2.8+dfsg-6+deb9u8.debian.tar.xz
 12fc5e4ac1ad9c7754054a5c4bee85a0 7869 otherosfs optional 
qemu_2.8+dfsg-6+deb9u8_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#935710: FTBFS: tests fail

[David Bremner]

Source: emacs-python-environment
Version: 0.0.2-4
Severity: serious
Justification: ftbfs

During a no-change rebuild, I noticed this package fails to build from source

Apparently the tests are failing

https://buildd.debian.org/status/fetch.php?pkg=emacs-python-environment=all=0.0.2-4=1566739692=log

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

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

Processed: tagging 927132, tagging 935660, tagging 935669, tagging 935677, tagging 935676, tagging 927136 ...

[Debian Bug Tracking System]

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

> tags 927132 + sid bullseye
Bug #927132 [src:hash-slinger] src:hash-slinger: Please port to python3
Added tag(s) bullseye and sid.
> tags 935660 + sid bullseye
Bug #935660 [src:tortoisehg] tortoisehg: Obsolete libs (python2) - depends 
python-pyqt5.qsci
Added tag(s) sid and bullseye.
> tags 935669 + sid bullseye
Bug #935669 [assaultcube-data] assaultcube-data: Outdated version makes 
assaultcube uninstallable
Added tag(s) bullseye and sid.
> tags 935677 + sid bullseye
Bug #935677 [ganeti-2.16] ganeti-2.16: Depends on to be removed packages 
(python2/python-ipaddr specifically)
Added tag(s) sid and bullseye.
> tags 935676 + sid bullseye
Bug #935676 [src:ganeti-2.15] ganeti-2.15: Depends on to be removed packages 
(python2/python-ipaddr specifically)
Added tag(s) sid and bullseye.
> tags 927136 + sid bullseye
Bug #927136 [src:zabbix-cli] src:zabbix-cli: Please update to python3
Added tag(s) bullseye and sid.
> tags 927135 + sid bullseye
Bug #927135 [src:rekall] src:rekall: Please update to python3 version
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
927132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927132
927135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927135
927136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927136
935660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935660
935669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935669
935676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935676
935677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems