Bug#936095: sardana: Obsolete libs (Python 2) - Depends on to be removed packages

[Scott Kitterman]

Source: sardana
Version: 2.6.2+dfsg-1
Severity: serious
Justification: Policy 2.5

It appears that upstream supports python3 [1].  Please either upgrade
the package or have it removed.  This is, indirectly, one of the few
remaining packages blocking python-qt4 removal.  We are also removing
Qt4.  This is expected to be complete early in the buster release cycle,
so please upgrade soon if you intend to.

If you are no longer interested in the package, feel free to let me know
in the bug and I'll take care of filing the rm if you don't want to.

Scott K

[1] https://github.com/sardana-org/sardana

Bug#936092: gcc-9 patches apply even less

[Helmut Grohne]

Source: cross-gcc
Version: 231
Severity: serious
Tags: patch
Control: block -1 by 928035

On top of #928035, there is another change in gcc-9 that makes the gcc-9
patches no longer apply. The attached patch resolves the relevant hunk.
Please consider uploading a new version that works with the current
gcc-9.

Helmut
--- a/gcc-9/0004-added-multi-arch-specific-install-location-patch.patch
+++ b/gcc-9/0004-added-multi-arch-specific-install-location-patch.patch
@@ -368,9 +388,9 @@
 +  else
 +debian_patches += cross-install-location
 +  endif
- endif
- 
- ifeq ($(DEB_TARGET_ARCH_OS),hurd)
+   ifeq ($(with_m2),yes)
+ debian_patches += cross-install-location-gm2
+   endif
 -- 
 2.17.1

Processed: gcc-9 patches apply even less

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 928035
Bug #936092 [src:cross-gcc] gcc-9 patches apply even less
936092 was not blocked by any bugs.
936092 was not blocking any bugs.
Added blocking bug(s) of 936092: 928035

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

Processed: Re: Bug#927135: src:rekall: Please update to python3 version

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 936091
Bug #927135 [src:rekall] src:rekall: Please update to python3 version
927135 was not blocked by any bugs.
927135 was not blocking any bugs.
Added blocking bug(s) of 927135: 936091

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

Bug#927135: src:rekall: Please update to python3 version

[Sandro Tosi]

control: block -1 by 936091

On Mon, 26 Aug 2019 11:02:23 +0200 Raphael Hertzog  wrote:
> Hi,
>
> On Sun, 25 Aug 2019, Scott Kitterman wrote:
> > If you have lost interest in the package, please let me know so I can ask to
> > have it removed.
>
> Don't remove rekall please. There's a new upstream release with Python 3
> support. We will get to it eventually.

I started having a look at packaging the new upstream release of
rekall, to support python 3 (mostly because rekall is a r-dep of some
of the packages i maintain). For now it looks like the most immediate
need is to get aff4 ported to python3, as it's a strong dependency of
rekall, so i filed #936091

Regards,
Sandro

Bug#936091: aff4: please package new upstream release (needed by rekall), port to python3

[Sandro Tosi]

Source: aff4
Severity: serious

Hello,
please package the new upstream release for aff4; according to
https://github.com/google/aff4 the project has been split in the Python and C
parts separately.

aff4 (specificly `'pyaff4 >= 0.26, < 0.30'`) is required by the new upstream
release of rekall.  Additionally, since we're trying to port rekall to python 3,
aff4 will need to provide python 3 bindings too.  Since rekall is the only
reverse-dependency of pyhton-aff4, you can as well drop the python2 bindings at
the same time, since we're trying to remove python 2 from bullseye,
https://wiki.debian.org/Python/2Removal .

The severity is set to serious because rekall requires this package to be
packaged, and it's already RC-buggy.

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

Bug#933584: marked as done (BD on texlive-generic-extra which isn't build anymore and isn't in bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 03:14:41 +
with message-id 
and subject line Bug#936059: Removed package(s) from unstable
has caused the Debian Bug report #933584,
regarding BD on texlive-generic-extra which isn't build anymore and isn't in 
bullseye
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.)


-- 
933584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: breathe
Version: 4.11.1-1
Severity: serious
Tags: ftbfs sid bullseye

Recently the texlive-base package has stopped building the transitional
package texlive-generic-extra. This is an issue for your package as it
build-depends on it. Please update the building of your package to use
texlive-plain-generic instead.

Unfortunately the migration software doesn't detected this kind of
situation yet, so your package also FTBFS in bullseye since 2019-07-16.

Paul





signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 0.12.1-11+rm

Dear submitter,

as the package pyx 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/936059

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

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 03:16:16 +
with message-id 
and subject line Bug#936077: Removed package(s) from unstable
has caused the Debian Bug report #874891,
regarding [gns3] 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.)


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

Dear submitter,

as the package gns3 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/936077

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

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 03:15:50 +
with message-id 
and subject line Bug#936072: Removed package(s) from unstable
has caused the Debian Bug report #875240,
regarding [xflr5] 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.)


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

Dear submitter,

as the package xflr5 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/936072

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#784871: marked as done (gns3 version too old to be usable)

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 03:16:16 +
with message-id 
and subject line Bug#936077: Removed package(s) from unstable
has caused the Debian Bug report #784871,
regarding gns3 version too old to be usable
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.)


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

Package: apache-common
Version: 0.8.7-2
Severity: normal


hi,

the package is complete outdated. Current Version is 1.3.2. The Version
in Debian is from 2013. 

ruben

-- 
Ruben Herold 
ru...@insecure.pw


pgpsBJO3Cn58K.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.8.7-2+rm

Dear submitter,

as the package gns3 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/936077

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

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 03:16:43 +
with message-id 
and subject line Bug#936078: Removed package(s) from unstable
has caused the Debian Bug report #875234,
regarding [writetype] 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.)


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

Dear submitter,

as the package writetype 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/936078

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

Processed: Re: Bug#936088: Acknowledgement (libmurmurhash autopkg tests fail)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #936088 [src:libmurmurhash] libmurmurhash autopkg tests fail
Added tag(s) patch.

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

Bug#936088: Acknowledgement (libmurmurhash autopkg tests fail)

[Matthias Klose]

Control: tags -1 + patch

patch at
http://launchpadlibrarian.net/439524642/libmurmurhash_1.5-1_1.5-1ubuntu1.diff.gz

Bug#936088: libmurmurhash autopkg tests fail

[Matthias Klose]

Package: src:libmurmurhash
Version: 1.5-1
Severity: serious
Tags: sid bullseye

Apparently the package needs a rebuild at least, some tests don't work anymore.

autopkgtest [22:47:58]: test run-unit-test: [---
/usr/bin/ld: /tmp/ccNY3NFj.o: in function `main':
mmh.c:(.text.startup+0xe2): undefined reference to `lmmh_x86_32'
/usr/bin/ld: mmh.c:(.text.startup+0x11a): undefined reference to `lmmh_x86_128'
/usr/bin/ld: mmh.c:(.text.startup+0x159): undefined reference to `lmmh_x64_128'
collect2: error: ld returned 1 exit status

CFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2 -O2 -fstack-protector-strong -Wformat 
-Werror=format-security"

gcc ${CFLAGS} -o mmh -lmurmurhash mmh.c
gcc ${CFLAGS} -o mmh_old -lmurmurhash mmh_old.c

- libraries have to appear last on the command line

- it's questionable to hard code the hardening flags.
  you should ask dpkg-buildflags about that, and add
  dpkg-dev to the test dependencies.

Bug#913041: marked as done (python-memprof fails its autopkg tests with Python 3.7)

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 00:07:02 +
with message-id 
and subject line Bug#913035: fixed in python-memprof 0.3.6-1
has caused the Debian Bug report #913035,
regarding python-memprof fails its autopkg tests with Python 3.7
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.)


-- 
913035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-memprof
Version: 0.3.4-1
Severity: serious
Tags: sid buster

python-memprof fails its autopkg tests with Python 3.7.  The autopkg tests find
the memprof module in the source package, and are using that.  You should copy
the testsuite to a temporary directory, cd to it and run the tess from there.


autopkgtest [18:17:30]: test python3-testsuite: [---
/usr/lib/python3/dist-packages/matplotlib/__init__.py:107: DeprecationWarning:
Using or importing the ABCs from 'collections' instead of from 'collections.abc'
is deprecated, and in 3.8 it will stop working
  from collections import MutableMapping
/usr/lib/python3/dist-packages/matplotlib/rcsetup.py:20: DeprecationWarning:
Using or importing the ABCs from 'collections' instead of from 'collections.abc'
is deprecated, and in 3.8 it will stop working
  from collections import Iterable, Mapping
/usr/lib/python3/dist-packages/matplotlib/colors.py:53: DeprecationWarning:
Using or importing the ABCs from 'collections' instead of from 'collections.abc'
is deprecated, and in 3.8 it will stop working
  from collections import Sized
E
==
ERROR: test_demo (test1.Test)
--
Traceback (most recent call last):
  File "/tmp/autopkgtest.UUFbqF/build.kzG/src/testsuite/test1.py", line 28, in
test_demo
import demo
  File "/tmp/autopkgtest.UUFbqF/build.kzG/src/examples/demo.py", line 19, in

from memprof import *
  File "/tmp/autopkgtest.UUFbqF/build.kzG/src/memprof/__init__.py", line 17, in

from .memprof import *
  File "/tmp/autopkgtest.UUFbqF/build.kzG/src/memprof/memprof.py", line 25, in

from .getsize import getSize, isInteresting
ModuleNotFoundError: No module named 'memprof.getsize'

--
Ran 1 test in 0.793s

FAILED (errors=1)
autopkgtest [18:17:32]: test python3-testsuite: ---]
--- End Message ---
--- Begin Message ---
Source: python-memprof
Source-Version: 0.3.6-1

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-memprof package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 29 Aug 2019 19:37:00 -0400
Source: python-memprof
Architecture: source
Version: 0.3.6-1
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Sandro Tosi 
Closes: 913035
Changes:
 python-memprof (0.3.6-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Fixed VCS URL (https)
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/control: Deprecating priority extra as per policy 4.0.1
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
   * Use debhelper-compat instead of debian/compat.
 .
   [ Sandro Tosi ]
   * Team upload.
   * New upstream release; Closes: #913035
   * debian/control
 - move to PAPT
 - bump Standards-Version to 4.4.0 (no changes needed)
   * debian/patches
 - drop patches merged upstream
   * Drop python 2 support
Checksums-Sha1:
 9d144eebfa052249161ab3b3e0ed562cbd72 2142 python-memprof_0.3.6-1.dsc
 1cc821559f76866bed010eaad421ff441595c429 53984 python-memprof_0.3.6.orig.tar.xz
 568477b5822434d94f9ac6032ed60a597471f220 3708 
python-memprof_0.3.6-1.debian.tar.xz
 f3d40d4f0934e6a568ee5d83518cfb2ee9d6d83d 

Bug#913035: marked as done (python-memprof fails its autopkg tests with Pyhton 3.7)

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 00:07:02 +
with message-id 
and subject line Bug#913035: fixed in python-memprof 0.3.6-1
has caused the Debian Bug report #913035,
regarding python-memprof fails its autopkg tests with Pyhton 3.7
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.)


-- 
913035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-memprof
Version: 0.3.4-1
Severity: serious
Tags: sid buster

python-memprof fails its autopkg tests with Pyhton 3.7:

autopkgtest [18:17:30]: test python3-testsuite: [---
/usr/lib/python3/dist-packages/matplotlib/__init__.py:107: DeprecationWarning:
Using or importing the ABCs from 'collections' instead of from 'collections.abc'
is deprecated, and in 3.8 it will stop working
  from collections import MutableMapping
/usr/lib/python3/dist-packages/matplotlib/rcsetup.py:20: DeprecationWarning:
Using or importing the ABCs from 'collections' instead of from 'collections.abc'
is deprecated, and in 3.8 it will stop working
  from collections import Iterable, Mapping
/usr/lib/python3/dist-packages/matplotlib/colors.py:53: DeprecationWarning:
Using or importing the ABCs from 'collections' instead of from 'collections.abc'
is deprecated, and in 3.8 it will stop working
  from collections import Sized
E
==
ERROR: test_demo (test1.Test)
--
Traceback (most recent call last):
  File "/tmp/autopkgtest.UUFbqF/build.kzG/src/testsuite/test1.py", line 28, in
test_demo
import demo
  File "/tmp/autopkgtest.UUFbqF/build.kzG/src/examples/demo.py", line 19, in

from memprof import *
  File "/tmp/autopkgtest.UUFbqF/build.kzG/src/memprof/__init__.py", line 17, in

from .memprof import *
  File "/tmp/autopkgtest.UUFbqF/build.kzG/src/memprof/memprof.py", line 25, in

from .getsize import getSize, isInteresting
ModuleNotFoundError: No module named 'memprof.getsize'

--
Ran 1 test in 0.793s

FAILED (errors=1)
autopkgtest [18:17:32]: test python3-testsuite: ---]
--- End Message ---
--- Begin Message ---
Source: python-memprof
Source-Version: 0.3.6-1

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-memprof package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 29 Aug 2019 19:37:00 -0400
Source: python-memprof
Architecture: source
Version: 0.3.6-1
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Sandro Tosi 
Closes: 913035
Changes:
 python-memprof (0.3.6-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Fixed VCS URL (https)
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/control: Deprecating priority extra as per policy 4.0.1
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
   * Use debhelper-compat instead of debian/compat.
 .
   [ Sandro Tosi ]
   * Team upload.
   * New upstream release; Closes: #913035
   * debian/control
 - move to PAPT
 - bump Standards-Version to 4.4.0 (no changes needed)
   * debian/patches
 - drop patches merged upstream
   * Drop python 2 support
Checksums-Sha1:
 9d144eebfa052249161ab3b3e0ed562cbd72 2142 python-memprof_0.3.6-1.dsc
 1cc821559f76866bed010eaad421ff441595c429 53984 python-memprof_0.3.6.orig.tar.xz
 568477b5822434d94f9ac6032ed60a597471f220 3708 
python-memprof_0.3.6-1.debian.tar.xz
 f3d40d4f0934e6a568ee5d83518cfb2ee9d6d83d 6609 
python-memprof_0.3.6-1_source.buildinfo
Checksums-Sha256:
 d79fa24b872df9bc1652401b24f4c9ea18306978d1e99c1c4d34a7c790ae8053 2142 
python-memprof_0.3.6-1.dsc
 

Processed: bug 913035 is forwarded to https://github.com/jmdana/memprof/issues/12

[Debian Bug Tracking System]

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

> forwarded 913035 https://github.com/jmdana/memprof/issues/12
Bug #913035 [src:python-memprof] python-memprof fails its autopkg tests with 
Pyhton 3.7
Bug #913041 [src:python-memprof] python-memprof fails its autopkg tests with 
Python 3.7
Set Bug forwarded-to-address to 'https://github.com/jmdana/memprof/issues/12'.
Set Bug forwarded-to-address to 'https://github.com/jmdana/memprof/issues/12'.
> thanks
Stopping processing here.

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

Processed: severity of 934591 is normal

[Debian Bug Tracking System]

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

> severity 934591 normal
Bug #934591 [anki] Anki fails to start: ModuleNotFoundError: No module named 
'PyQt5.sip'
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Thu, 29 Aug 2019 22:19:24 +
with message-id 
and subject line Bug#935938: fixed in android-sdk-meta 25.0.0+12
has caused the Debian Bug report #935938,
regarding android-sdk-meta_25.0.0+11~deb10u1_all.changes REJECTED
to be marked as done.

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

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


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

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

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

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

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

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 29 Aug 2019 23:22:43 +0200
Source: android-sdk-meta
Architecture: source
Version: 25.0.0+12
Distribution: unstable
Urgency: medium
Maintainer: Android Tools Maintainers 

Changed-By: Hans-Christoph Steiner 
Closes: 924175 935938
Changes:
 android-sdk-meta (25.0.0+12) unstable; urgency=medium
 .
   * no need for JDK in Depends:, apksigner and dalvik-exchange
 already have it
   * Revert "remove broken screenshot2 symlink (Closes: #924175)
   * fix regex for adding Debian version to binary packages
 (Closes: #935938)
Checksums-Sha1:
 a9caf9f2ebadfd367b821bf6f410740cbd90eff5 2076 android-sdk-meta_25.0.0+12.dsc
 022644a7e3361917ec8bbb5c83ef3c36f920e857 10456 
android-sdk-meta_25.0.0+12.tar.xz
 fa6b074eda30d9baf33152bbbf3ceac11710d4fc 5097 
android-sdk-meta_25.0.0+12_source.buildinfo
Checksums-Sha256:
 d6be0689d2ce7c92a4de637eb429a597c39355c5b92d77668552d0054606aef1 2076 
android-sdk-meta_25.0.0+12.dsc
 5ad82865ed09c4e8fa6dcef62febcb4d4986d450579f84d0438b8f237eac10e1 10456 
android-sdk-meta_25.0.0+12.tar.xz
 acf211b4f0a33ca99220c65f37f8ede44cfadd9f99468400a2a7dc485abd628d 5097 
android-sdk-meta_25.0.0+12_source.buildinfo
Files:
 063b0bd2d57b8b7f8a0ba1d28bcd3d77 2076 metapackages optional 
android-sdk-meta_25.0.0+12.dsc
 e5c34f9c173918344cc15c3c6717e46b 10456 metapackages optional 
android-sdk-meta_25.0.0+12.tar.xz
 a5b7f99bdf6152b1328141816d62907f 5097 metapackages optional 
android-sdk-meta_25.0.0+12_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEElyI52+aGmfUmwGoFPhd4F7obm/oFAl1oQtQACgkQPhd4F7ob
m/o7Cgf+Mp4yVbVEEJhzQXy2q8qw4cjP2GA9U6R864Px/t6/08Y/pothBVfL1ypg
AOS5VJ1kgWUnOYg96zVY04kmzPm6bH3/VBCujDSZj5mnGKjvSGuyCsXfNFsjTIjz
Kc4YsrTy/ykLXB46/UbnQitwaCeR+HkaVs4sXXFHET/cYWoHAMQjtYgyDe0FbHHK
R7plEbPUcnA+uyPl6c1HOYGXKvC7+kovPjYleW40spSX2jB7mTr1BAd1R74ee+pX
3nrBZTBq/8dh+aXqWabD6SqaGZZeZozsia4MH1Z2MYOvCB9O1ntLtZDPw6i4JJ9s
d4oNadfSeeo2WjGaWGs6/W+vL2jN+Q==
=zSlj
-END PGP SIGNATURE End Message ---

Bug#928791: marked as done (congress: FTBFS twice in a row: File exists: 'congress/tests/etc/keys')

[Debian Bug Tracking System]

Your message dated Thu, 29 Aug 2019 22:19:37 +
with message-id 
and subject line Bug#928791: fixed in congress 9.0.0+dfsg1-4
has caused the Debian Bug report #928791,
regarding congress: FTBFS twice in a row: File exists: 'congress/tests/etc/keys'
to be marked as done.

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

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


-- 
928791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: congress
Version: 9.0.0+dfsg1-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

congress/experimental fails to build twice in a row:

Traceback (most recent call last):
  File 
"/build/congress-9.0.0+dfsg1/congress/tests/api/test_datasource_model.py", line 
45, in setUp
self.ds_manager.add_datasource(self.datasource)
  File "/build/congress-9.0.0+dfsg1/congress/dse2/datasource_manager.py", line 
71, in add_datasource
secret_config_fields=driver_info.get('secret', []))
  File "/usr/lib/python3/dist-packages/tenacity/__init__.py", line 241, in 
wrapped_f
return self.call(f, *args, **kw)
  File "/usr/lib/python3/dist-packages/tenacity/__init__.py", line 330, in call
start_time=start_time)
  File "/usr/lib/python3/dist-packages/tenacity/__init__.py", line 279, in iter
return fut.result()
  File "/usr/lib/python3.7/concurrent/futures/_base.py", line 425, in result
return self.__get_result()
  File "/usr/lib/python3.7/concurrent/futures/_base.py", line 384, in 
__get_result
raise self._exception
  File "/usr/lib/python3/dist-packages/tenacity/__init__.py", line 333, in call
result = fn(*args, **kwargs)
  File "/build/congress-9.0.0+dfsg1/congress/db/utils.py", line 42, in decorate
return func(*args, **kw)
  File "/build/congress-9.0.0+dfsg1/congress/db/datasources.py", line 94, in 
add_datasource
_encrypt_secret_config_fields(datasource, secret_config_fields)
  File "/build/congress-9.0.0+dfsg1/congress/db/datasources.py", line 60, in 
_encrypt_secret_config_fields
config[field] = encryption.encrypt(config[field])
  File "/build/congress-9.0.0+dfsg1/congress/encryption.py", line 85, in encrypt
initialize_if_needed()
  File "/build/congress-9.0.0+dfsg1/congress/encryption.py", line 81, in 
initialize_if_needed
initialize_key()
  File "/build/congress-9.0.0+dfsg1/congress/encryption.py", line 72, in 
initialize_key
__key = create_new_key_file()
  File "/build/congress-9.0.0+dfsg1/congress/encryption.py", line 52, in 
create_new_key_file
os.makedirs(dir_path, mode=0o700)  # important: restrictive permissions
  File "/usr/lib/python3.7/os.py", line 221, in makedirs
mkdir(name, mode)
FileExistsError: [Errno 17] File exists: 'congress/tests/etc/keys'


--
Ran 832 tests in 75.262s

FAILED (failures=2, skipped=5)
make[1]: *** [debian/rules:41: override_dh_install] Error 1


Andreas


congress_9.0.0+dfsg1-2_twice.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: congress
Source-Version: 9.0.0+dfsg1-4

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 29 Aug 2019 23:07:03 +0200
Source: congress
Architecture: source
Version: 9.0.0+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 928791
Changes:
 congress (9.0.0+dfsg1-4) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat.
 .
   [ Thomas Goirand ]
   * Correctly clean-up builds (Closes: #928791).
Checksums-Sha1:
 7a4c1ac93ebd34e5c71ed6c9ed2d2b6b57820228 3479 congress_9.0.0+dfsg1-4.dsc
 515af0ff1896c562fbd7f13bf11387b78a3a9fcf 6600 
congress_9.0.0+dfsg1-4.debian.tar.xz
 879faa969da032f312249e50ac709b69c3da18a7 15938 
congress_9.0.0+dfsg1-4_amd64.buildinfo
Checksums-Sha256:
 

Bug#934591: Anki fails to start: ModuleNotFoundError: No module named 'PyQt5.sip'

[Julian Gilbey]

severity 931798 normal
thanks

On Wed, Aug 21, 2019 at 09:39:52PM +0100, Julian Gilbey wrote:
> On Wed, Aug 21, 2019 at 04:22:23PM +0200, Arnaldo Pirrone wrote:
> > Hi, i do have python3-sip.
> > Now the error is this:
> > $ anki
> > Traceback (most recent call last):
> >   File "/usr/bin/anki", line 6, in 
> >     import aqt
> >   File "/usr/share/anki/aqt/__init__.py", line 32, in 
> >     import aqt.forms
> >   File "/usr/share/anki/aqt/forms/__init__.py", line 44, in 
> >     from . import about
> >   File "/usr/share/anki/aqt/forms/about.py", line 42, in 
> >     from aqt.webview import AnkiWebView
> >   File "/usr/share/anki/aqt/webview.py", line 90, in 
> >     class AnkiWebView(QWebEngineView):
> > NameError: name 'QWebEngineView' is not defined
> 
> OK, something is very very wrong with your installation of something,
> or some other problem, but I'm quite stumped.  Anki imports the whole
> of PyQt5.Qt, and that includes QWebEngineView.
> 
> Are you getting the same error message every time you try starting
> Anki, or is it different each time?

Dear Arnaldo,

Since I can't reproduce this problem, and it seems to be related to
something else wrong on your system (as it gives different errors on
different occasions), I'm reducing the severity of this bug to
"normal".  If you are able to answer my question, we could try to get
to the bottom of this, otherwise we'll just have to leave it,
unfortunately.

Best wishes,

   Julian

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

[Christian T. Steigies]

On Thu, Aug 29, 2019 at 10:55:28PM +0200, Francesco Poli wrote:
> On Thu, 29 Aug 2019 22:14:04 +0200 Christian T. Steigies wrote:
> 
> > Hi,
> > On Fri, Aug 16, 2019 at 04:32:08PM +0100, Laurence Abbott via Glx-devel 
> > wrote:
> > > I _think_ I have the fix for seg faults that occur when QGLE is used with
> > > ghostscript 9.27 (the latest release).
> > 
> > I applied Laurence's patches and applied them to the Debian package, plus
> > some Debian related changes. It looks as if we have QGLE ported to Qt5!
> 
> Hey, I am glad to hear this!   :-)
> I am adding the Qt4-removal bug address to the list of recipient, since
> this is good news for Qt4-removal issue.
> 
> > 
> > I need to do some before this can go into Debian, but here are amd64 and
> > source packages for you to test:
> > 
> > https://people.debian.org/~cts/deb/
> > 
> > Please don't upload them, but test and send feedback back to the list.
> 
> Any specific reason to use a version number (4.2.5-7~exp1) which is
> actually considered lower than the one currently in Debian unstable
> (4.2.5-7+b1)?

Oh, I forgot about the binNMU. This is not the version that will be uploaded
to Debian, that will be -8. I just wanted to give you something to test,
before I upload, and it should have had a version between 7 and 8. Well, I
guess you can still test it, since you need to install the deb manually
anyway.

Christian

Bug#936016: meteo-qt crashes immediately

[Alf Gaida]

my bad, my first answer was wrong - should talk with the author


cheers Alf

Bug#875234: [writetype] Future Qt4 removal from Buster

[Miriam Ruiz]

Thanks!!!

Miry

El jue., 29 ago. 2019 a las 23:05, Moritz Mühlenhoff
() escribió:
>
> On Thu, Aug 29, 2019 at 10:58:03PM +0200, Miriam Ruiz wrote:
> > It's okay for me to remove it from the archive. I think it would be
> > the best. As you say, it seems to be dead upstream.
>
> Ack, I've just filed a removal bug.
>
> Cheers,
> Moritz

Bug#913756: marked as done (tootle: Tootle window opens and closes immediately)

[Debian Bug Tracking System]

Your message dated Thu, 29 Aug 2019 21:32:59 +
with message-id 
and subject line Bug#913756: fixed in granite 5.2.4-1
has caused the Debian Bug report #913756,
regarding tootle: Tootle window opens and closes immediately
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.)


-- 
913756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tootle
Version: 0.2.0-1
Severity: important

Dear Maintainer,


   After upgrade Tootle in 0.2.0-1 on Debian Sid, the window opens and closes
immediately.

Here is the return when launched via the terminal :
tootle
[INFO 21:35:59.596996] Application.vala:155: Tootle version: 0.2.0
[INFO 21:35:59.597255] Application.vala:157: Kernel version: 4.18.0-2-amd64
[FATAL 21:35:59.680194] [Json] json_object_get_int_member: assertion 'node !=
NULL' failed
[FATAL 21:35:59.680456] [Json] json_object_get_boolean_member: assertion 'node
!= NULL' failed
[FATAL 21:35:59.680653] [Json] json_object_get_array_member: assertion 'node !=
NULL' failed
[FATAL 21:35:59.680814] [Json] json_array_foreach_element: assertion 'array !=
NULL' failed
[INFO 21:35:59.681304] Notificator.vala:40: Starting:
/api/v1/streaming/?stream=user
[INFO 21:35:59.688757] Notificator.vala:40: Starting:
/api/v1/streaming/?stream=user
[INFO 21:35:59.701322] Notificator.vala:40: Starting:
/api/v1/streaming/?stream=public:local
[INFO 21:35:59.705691] Notificator.vala:40: Starting:
/api/v1/streaming/?stream=public
[INFO 21:36:00.595659] Watchlist.vala:23: Reloading
[INFO 21:36:00.595928] Watchlist.vala:34: Watching for 0 users and 0 hashtags
[ERROR 21:36:01.113720] [GLib-GIO] Settings schema
'io.elementary.desktop.wingpanel.datetime' is not installed
Trappe pour point d'arrêt et de trace


Thanks



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

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

Versions of packages tootle depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-1
ii  elementary-xfce-icon-theme   0.13.1-1
ii  libc62.27-8
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-6
ii  libgee-0.8-2 0.20.1-1
ii  libglib2.0-0 2.58.1-2
ii  libgranite5  5.2.1-1
ii  libgtk-3-0   3.24.1-2
ii  libjson-glib-1.0-0   1.4.4-1
ii  libsoup2.4-1 2.64.2-1

tootle recommends no packages.

tootle suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: granite
Source-Version: 5.2.4-1

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated granite package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 29 Aug 2019 16:18:30 -0400
Source: granite
Architecture: source
Version: 5.2.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Deepin Packaging Team 

Changed-By: Boyuan Yang 
Closes: 913756
Changes:
 granite (5.2.4-1) unstable; urgency=medium
 .
   * New upstream release 5.2.4.
 + Various fixes. (Closes: #913756)
   * debian/control: Bump Standards-Version to 4.4.0.
   * debian/copyright: Refresh information.
   * debian/symbols: Add new symbols.
Checksums-Sha1:
 348448734a185ea3f8d6677a4d08f130e74cdc50 2348 granite_5.2.4-1.dsc
 7e05ae1c9f54c149d2b5d04d11b3c8e4c7198339 390145 granite_5.2.4.orig.tar.gz
 347fb07bf2d94e5bdcdba9d4e4368e489d48fb1c 8452 granite_5.2.4-1.debian.tar.xz
 14d378fed485d6637fe91cf942a40230c6219978 16032 granite_5.2.4-1_amd64.buildinfo
Checksums-Sha256:
 

Bug#936016: meteo-qt crashes immediately

[Alf Gaida]

Nice finding, unfortunately you are right:


>From bfe9ae4d25b914d5c2622042303ba09fa8060e80 Mon Sep 17 00:00:00 2001
From: Dimitrios Glentadakis 
Date: Mon, 6 May 2019 19:34:58 +0200
Subject: [PATCH] Fix crash when 6 days forceast is not available

---
 meteo_qt/meteo_qt.py | 4 
 1 file changed, 4 insertions(+)

diff --git a/meteo_qt/meteo_qt.py b/meteo_qt/meteo_qt.py
index f6fca87..9774616 100644
--- a/meteo_qt/meteo_qt.py
+++ b/meteo_qt/meteo_qt.py
@@ -1861,6 +1861,10 @@ def run(self):
 'Fetching url for 6 days :' + self.forecast6_url
 + self.id_ + self.suffix + '=7'
 )
+reqforecast6 = (
+self.forecast6_url + self.id_
++ self.suffix + '=7'
+)
 try:
 reqforecast6 = urllib.request.urlopen(
 self.forecast6_url + self.id_


Applying this patch to 1.0.0 fixes the problem for me - next question is:

How to get this to stable, testing and sid have already 1.3.

Bug#933822: closed by Jan Dittberner (Bug#933822: fixed in virtualenvwrapper 4.8.4-1)

[Peter Green]

On 28/08/2019 09:12, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the virtualenvwrapper package:

#933822: virtualenvwrapper depends on cruft package python-stevedore

Is there a reason that the fix was only uploaded to experimental? and/or an ETA 
for getting the fix in unstable?

Bug#936079: python-ceilometerclient (build-)depends on cruft packages.

[peter green]

Package: python-ceilometerclient
Version: 2.9.0-2
Severity: serious
Tags: bullseye, sid

The python-ceilometerclient binary package depends on and the 
python-ceilometerclient binary package build-depends on a number of python 2 
binary packages that are no longer built by their corresponding source packages.

There don't seem to be any reverse-dependencies left, so presumablly it is time 
to drop python 2 support from this package.

Bug#929697: marked as done (pyglet: FTBFS randomly because of timing tests)

[Debian Bug Tracking System]

Your message dated Thu, 29 Aug 2019 21:36:44 +
with message-id 
and subject line Bug#929697: fixed in pyglet 1.4.1-3
has caused the Debian Bug report #929697,
regarding pyglet: FTBFS randomly because of timing tests
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
test -x debian/rules
mkdir -p "."
CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
mkdir -p debian/python-module-stampdir
cd . && python setup.py build --build-base="/<>/./build"
running build
running build_py
creating /<>/build
creating /<>/build/lib.linux-x86_64-2.7
creating /<>/build/lib.linux-x86_64-2.7/pyglet
copying pyglet/lib.py -> /<>/./build/lib.linux-x86_64-2.7/pyglet

[... snipped ...]

copying _build/lib.linux-x86_64-2.7/pyglet/app/xlib.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/app
copying _build/lib.linux-x86_64-2.7/pyglet/app/win32.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/app
copying _build/lib.linux-x86_64-2.7/pyglet/app/__init__.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/app
copying _build/lib.linux-x86_64-2.7/pyglet/info.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet
copying _build/lib.linux-x86_64-2.7/pyglet/compat.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet
creating 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/base.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/carbon.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/lib.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/lib_wgl.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/glext_nv.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/cocoa.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/glxext_arb.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/lib_glx.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/wglext_arb.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/glxext_nv.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/xlib.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/glx.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/wglext_nv.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/glx_info.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/glu.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/glext_arb.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/wgl.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/win32.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/__init__.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/glxext_mesa.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/gl.py -> 

Bug#935015: datalad: please drop python-datalad (python 2 removal effort)

[peter green]

Found 935015 0.11.2-2
Thanks

This bug also affects the version in testing.

Processed: re: datalad: please drop python-datalad (python 2 removal effort)

[Debian Bug Tracking System]

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

> Found 935015 0.11.2-2
Bug #935015 [src:datalad] datalad: please drop python-datalad (python 2 removal 
effort)
Marked as found in versions datalad/0.11.2-2.
> Thanks
Stopping processing here.

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

Bug#928791: marked as pending in congress

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/services/congress/commit/92cb080108bdfa87f21029adc87dcbca3515d587


Correctly clean-up builds (Closes: #928791).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/928791

Processed: Bug#928791 marked as pending in congress

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #928791 [src:congress] congress: FTBFS twice in a row: File exists: 
'congress/tests/etc/keys'
Added tag(s) pending.

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

Bug#875234: [writetype] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Thu, Aug 29, 2019 at 10:58:03PM +0200, Miriam Ruiz wrote:
> It's okay for me to remove it from the archive. I think it would be
> the best. As you say, it seems to be dead upstream.

Ack, I've just filed a removal bug.

Cheers,
Moritz

Bug#936076: python3-numba: numba segfaults when run with python 3.7.4 at numba/_dynfunc.c:52

[Diane Trout]

Package: python3-numba
Version: 0.42.0-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

Attempting to run any numba code immediately segfaults when running with python
3.7.4.

I found this upstream bug report.
https://github.com/numba/numba/pull/4328

"CPython 3.7.3->3.7.4 changed the size of PyGC_Head, the macro
_PyObject_GC_UNTRACK relied on calling sizeof() on that struct, as it is a
macro it got baked in at compile time and then segfaults happen across the
point version change as the struct size changed."

The simplist solution is to rebuild with python 3.7.4... though then it'll
crash with earlier versions.

Diane



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

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

Versions of packages python3-numba depends on:
ii  libc6   2.28-10
ii  libgcc1 1:9.2.1-4
ii  libgomp19.2.1-4
ii  libstdc++6  9.2.1-4
ii  libtbb2 2019~U8-1
ii  python3 3.7.3-1
ii  python3-llvmlite0.27.0-2
ii  python3-numpy [python3-numpy-abi9]  1:1.16.2-1+b1

Versions of packages python3-numba recommends:
ii  numba-doc  0.42.0-1

Versions of packages python3-numba suggests:
pn  nvidia-cuda-toolkit  

-- no debconf information

Bug#875234: [writetype] Future Qt4 removal from Buster

[Miriam Ruiz]

It's okay for me to remove it from the archive. I think it would be
the best. As you say, it seems to be dead upstream.

Greetings,
Miry

El jue., 29 ago. 2019 a las 22:42, Moritz Mühlenhoff
() escribió:
>
> On Sat, Sep 09, 2017 at 11:12:40PM +0200, Lisandro Damián Nicanor Pérez Meyer 
> wrote:
> > Source: writetype
> > Version: 1.3.163-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:
> >
> > 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
>
> Hi,
> writetype is dead upstream (the website vanished completely), are you
> planning to port it yourself or should we remove it from the archive?
>
> Cheers,
> Moritz

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

[Francesco Poli]

On Thu, 29 Aug 2019 22:14:04 +0200 Christian T. Steigies wrote:

> Hi,
> On Fri, Aug 16, 2019 at 04:32:08PM +0100, Laurence Abbott via Glx-devel wrote:
> > I _think_ I have the fix for seg faults that occur when QGLE is used with
> > ghostscript 9.27 (the latest release).
> 
> I applied Laurence's patches and applied them to the Debian package, plus
> some Debian related changes. It looks as if we have QGLE ported to Qt5!

Hey, I am glad to hear this!   :-)
I am adding the Qt4-removal bug address to the list of recipient, since
this is good news for Qt4-removal issue.

> 
> I need to do some before this can go into Debian, but here are amd64 and
> source packages for you to test:
> 
> https://people.debian.org/~cts/deb/
> 
> Please don't upload them, but test and send feedback back to the list.

Any specific reason to use a version number (4.2.5-7~exp1) which is
actually considered lower than the one currently in Debian unstable
(4.2.5-7+b1)?

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

Should it be 4.2.5-8~exp1, perhaps?


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


pgpqrA1KpSxXm.pgp
Description: PGP signature

Bug#875234: [writetype] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sat, Sep 09, 2017 at 11:12:40PM +0200, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Source: writetype
> Version: 1.3.163-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:
> 
> 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

Hi,
writetype is dead upstream (the website vanished completely), are you
planning to port it yourself or should we remove it from the archive?

Cheers,
Moritz

Bug#925862: xbindkeys-config: ftbfs with GCC-9

[Reiner Herrmann]

Control: tags -1 + patch

Dear maintainer,

the attached patch fixes the FTBFS by moving the linked
libraries to the end of the command line.

Regards,
  Reiner
--- xbindkeys-config-0.1.3.orig/debian/patches/gcc9.patch
+++ xbindkeys-config-0.1.3/debian/patches/gcc9.patch
@@ -0,0 +1,15 @@
+Author: Reiner Herrmann 
+Description: Fix FTBFS with gcc9 by moving libs to the end of the command line
+Bug-Debian: https://bugs.debian.org/925862
+
+--- a/Makefile
 b/Makefile
+@@ -15,7 +15,7 @@
+ all: main
+ 
+ main: $(OBJS)
+-	$(CC) $(GTK) $(OBJS) -o $(NOM)
++	$(CC) $(OBJS) -o $(NOM) $(GTK)
+ 
+ clean:
+ 	rm -f *.o */*.o */*~ core $(NOM) *~
only in patch2:
unchanged:
--- xbindkeys-config-0.1.3.orig/debian/patches/series
+++ xbindkeys-config-0.1.3/debian/patches/series
@@ -0,0 +1 @@
+gcc9.patch


signature.asc
Description: PGP signature

Processed: Re: xbindkeys-config: ftbfs with GCC-9

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #925862 [src:xbindkeys-config] xbindkeys-config: ftbfs with GCC-9
Added tag(s) patch.

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

Bug#875250: [scim] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sat, Sep 09, 2017 at 11:09:36PM +0200, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Source: scim
> 
> 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

Given upstream's comments on https://github.com/scim-im/scim/issues/21, let's
move forward by dropping the scim-qt-immodule binary package? It can still
be re-added if a Qt5 port appears at a later time.

Cheers,
Moritz

Bug#875219: [unixodbc-gui-qt] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sat, Sep 09, 2017 at 11:11:54PM +0200, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Source: unixodbc-gui-qt
> Version: 2.3.0-4
> Severity: wishlist
> User: debian-qt-...@lists.debian.org
> Usertags: qt4-removal
> 
> 
> Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> as [announced] in:
> 
> 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

The current SVN trunk on the SourceForge page supports Qt5.

Cheers,
Moritz

Bug#930363: faad2: fix build with gcc-9 [patch]

[Fabian Greffrath]

Am Donnerstag, den 29.08.2019, 09:54 -0400 schrieb Hugo Lefeuvre:
> Ack, I'll NMU then. Good luck with the baby :)

Thank you! \o/

 - Fabian



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

Bug#922767: marked as done (libemf : FTBFS - mv: cannot stat 'refman.pdf': No such file or directory -)

[Debian Bug Tracking System]

Your message dated Thu, 29 Aug 2019 21:54:39 +0200
with message-id <0ba8b1b9-8627-4306-d09d-17fec132c...@web.de>
and subject line Re: Processed (with 1 error): NIMBY
has caused the Debian Bug report #922767,
regarding libemf : FTBFS - mv: cannot stat 'refman.pdf': No such file or 
directory -
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.)


-- 
922767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libemf
Version: 1.0.11-2
Severity: important
Tags: sid buster

Current compilation fails with message

/This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live
2019/dev/Debian) (preloaded format=pdflatex) restricted \write18
enabled. entering extended mode (./refman.tex LaTeX2e <2018-12-01> mv:
cannot stat 'refman.pdf': No such file or directory make[2]: ***
[Makefile:870: doxygen-doc/libemf.pdf] Error 1 make[2]: Leaving
directory '/<>' dh_auto_build: make -j4 all doxygen-doc
doxygen-pdf returned exit code 2 make[1]: *** [debian/rules:13:
override_dh_auto_build] Error 2/

The command pdflatext refman.tex fails according to refman.log
! Misplaced \cr.
 \cr 

l.46 \end{DoxyParams}
 
I can't figure out why you would want to use a tab mark
or \cr or \span just now. If something like a right brace
up above has ended a previous alignment prematurely,
you're probably due for more error messages, and you
might try typing `S' now just to see what is salvageable.

! Missing \cr inserted.
 
\cr 
l.46 \end{DoxyParams}
 
*(That makes 100 errors; please try again.) *
Here is how much of TeX's memory you used:
 14925 strings out of 494561
 215545 string characters out of 6177454
 324426 words of memory out of 500
 18282 multiletter control sequences out of 15000+60
 43322 words of font info for 66 fonts, out of 800 for 9000
 14 hyphenation exceptions out of 8191
 53i,11n,92p,307b,565s stack positions out of 5000i,500n,1p,20b,8s

!  ==> Fatal error occurred, no output PDF file produced!

--- End Message ---
--- Begin Message ---
Version: 2019.20190506-1

Am 29.08.2019 um 18:21 teilte Debian Bug Tracking System mit:

>> reassign 922767 texlive-latex-extra
> Bug #922767 [libemf] libemf : FTBFS - mv: cannot stat 'refman.pdf': No such 
> file or directory -
> Bug reassigned from package 'libemf' to 'texlive-latex-extra'.
> No longer marked as found in versions 1.0.11-2.
> Ignoring request to alter fixed versions of bug #922767 to the same values 
> previously set
>> forcemerge 920621 922767
> Failed to forcibly merge 920621: Not altering archived bugs; see unarchive.
> 


-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Processed: [bts-link] source package kamoso

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package kamoso
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #914441 (http://bugs.debian.org/914441)
> # Bug title: kamoso: no user interface is shown: qrc:/qml/Main.qml:7 module 
> "org.kde.kirigami" is not installed
> #  * https://salsa.debian.org/qt-kde-team/kde/kamoso/merge_requests/1
> #  * remote status changed: (?) -> merged
> #  * closed upstream
> tags 914441 + fixed-upstream
Bug #914441 [kamoso] kamoso: no user interface is shown: qrc:/qml/Main.qml:7 
module "org.kde.kirigami" is not installed
Added tag(s) fixed-upstream.
> usertags 914441 + status-merged
There were no usertags set.
Usertags are now: status-merged.
> thanks
Stopping processing here.

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

Bug#934959: marked as done (python-mock breaks sunpy autopkgtest)

[Debian Bug Tracking System]

Your message dated Thu, 29 Aug 2019 19:10:59 +
with message-id 
and subject line Bug#934959: fixed in sunpy 1.0.3-1
has caused the Debian Bug report #934959,
regarding python-mock breaks sunpy autopkgtest
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.)


-- 
934959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-mock, sunpy
Control: found -1 python-mock/3.0.5-1
Control: found -1 sunpy/0.9.6-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent (one month old) upload of python-mock the autopkgtest of
sunpy fails in testing when that autopkgtest is run with the binary
packages of python-mock from unstable. It passes when run with only
packages from testing. In tabular form:
   passfail
python-mockfrom testing3.0.5-1
sunpy  from testing0.9.6-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. (On top of
that, there are *loads* of deprecation warnings, the maintainer of sunpy
probably wants to look into that).

Currently this regression is blocking the migration of python-mock to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package? If needed, please change the
bug's severity.

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

Paul

[1] https://qa.debian.org/excuses.php?package=python-mock

https://ci.debian.net/data/autopkgtest/testing/amd64/s/sunpy/2748790/log.gz

=== FAILURES
===
 test_parse_obssumm_dbase_file
_

def test_parse_obssumm_dbase_file():
"""
Ensure that all required data are extracted from the RHESSI
observing summary database file mocked in `hessi_data()`
"""
mock_file = mock.mock_open()
mock_file.return_value.__iter__.return_value = hessi_data()

dbase_data = {}
with mock.patch('sunpy.instr.rhessi.open', mock_file, create=True):
>   dbase_data = rhessi.parse_obssumm_dbase_file(None)

/usr/lib/python3/dist-packages/sunpy/instr/tests/test_rhessi.py:206:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _

filename = None

def parse_obssumm_dbase_file(filename):
"""
Parse the RHESSI observing summary database file. This file
lists the
name of observing summary files for specific time ranges along
with other
info

Parameters
--
filename : `str`
The filename of the obssumm dbase file.

Returns
---
out : `dict`
Return a `dict` containing the parsed data in the dbase file.

Examples

>>> import sunpy.instr.rhessi as rhessi
>>> fname, _ = rhessi.get_obssumm_dbase_file(('2011/04/04',
'2011/04/05'))   # doctest: +REMOTE_DATA
>>> file_names = rhessi.parse_obssumm_dbase_file(fname)   #
doctest: +REMOTE_DATA
>>> file_names['filename'][::5]   # doctest: +REMOTE_DATA
['hsi_obssumm_20110401_043.fit', 'hsi_obssumm_20110406_041.fit',
'hsi_obssumm_20110411_024.fit', 'hsi_obssumm_20110416_016.fit',
'hsi_obssumm_20110421_025.fit', 'hsi_obssumm_20110426_022.fit']

References
--
|
https://hesperia.gsfc.nasa.gov/ssw/hessi/doc/guides/hessi_data_access.htm#Observing%20Summary%20Data

.. note::
This API is currently limited to providing data from whole
days only.

"""
# An example dbase file can be found at:
#
https://hesperia.gsfc.nasa.gov/hessidata/dbase/hsi_obssumm_filedb_200311.txt

with open(filename) as fd:
reader = csv.reader(fd, delimiter=' ', skipinitialspace=True)
>   _ = next(reader)  # skip 'HESSI Filedb File:' row
E   StopIteration

/usr/lib/python3/dist-packages/sunpy/instr/rhessi.py:145: StopIteration



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: sunpy
Source-Version: 1.0.3-1

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

Bug#925625: abr2gbr: ftbfs with GCC-9

[Reiner Herrmann]

Control: tags -1 + patch

Dear maintainer,

the attached patch fixes the FTBFS by moving the libs
to the end of the command line.

Regards,
  Reiner
diff -Nru abr2gbr-1.0.2/debian/patches/gcc9.patch abr2gbr-1.0.2/debian/patches/gcc9.patch
--- abr2gbr-1.0.2/debian/patches/gcc9.patch	1970-01-01 01:00:00.0 +0100
+++ abr2gbr-1.0.2/debian/patches/gcc9.patch	2010-08-24 10:01:53.0 +0200
@@ -0,0 +1,15 @@
+Author: Reiner Herrmann 
+Description: Fix FTBTS with gcc9 by moving libs to the end of the command line
+Bug-Debian: https://bugs.debian.org/925625
+
+--- a/Makefile
 b/Makefile
+@@ -44,7 +44,7 @@
+ 	$(CC) -o $@ $(CFLAGS) -c $<
+ 
+ $(OBJDIR)/$(BIN): $(DESTS)
+-	$(CC) -o $@ $(CFLAGS) $(LIBS) $(DESTS)
++	$(CC) -o $@ $(CFLAGS) $(DESTS) $(LIBS)
+ 	if [ ! -L $(BIN) ]; then \
+ 		ln -s $(OBJDIR)/$(BIN) .; \
+ 		ln -s $(OBJDIR)/$(BIN) jbr2gbr; \
diff -Nru abr2gbr-1.0.2/debian/patches/series abr2gbr-1.0.2/debian/patches/series
--- abr2gbr-1.0.2/debian/patches/series	2010-08-27 21:37:09.0 +0200
+++ abr2gbr-1.0.2/debian/patches/series	2010-08-24 10:01:53.0 +0200
@@ -1 +1,2 @@
 fix_compile_flags-1:1.0.2-2
+gcc9.patch


signature.asc
Description: PGP signature

Processed: Re: abr2gbr: ftbfs with GCC-9

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #925625 [src:abr2gbr] abr2gbr: ftbfs with GCC-9
Added tag(s) patch.

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

Bug#875029: [lightdm] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Thu, Sep 21, 2017 at 03:36:38PM +0200, Yves-Alexis Perez wrote:
> On Thu, 2017-09-21 at 00:09 +0800, Boyuan Yang wrote:
> > I noticed that you are planning to remove Qt components of lightdm from 
> > Debian's lightdm. In fact, pkg-deepin team has a planned package that needs 
> > Qt5-based liblightdm-qt as (build-)dependency. See bug #871840 [1]. In case 
> > you might be curious, we have a dependency graph too. [3]
> 
> Hi,
> 
> I'm a not at all interested in Qt (4 or 5) components, so honestly I'm all
> inclined to just disable Qt4 and stay like this.

Attached is a patch which drops Qt4 support. It's only used by src:razorqt,
which is already RC-buggy anyway and which will be removed soon along with
Qt4.

Cheers,
Moritz
diff -Naur lightdm-1.26.0.orig/debian/control lightdm-1.26.0/debian/control
--- lightdm-1.26.0.orig/debian/control	2019-07-10 22:34:59.0 +0200
+++ lightdm-1.26.0/debian/control	2019-08-29 20:25:12.718749257 +0200
@@ -16,7 +16,6 @@
libglib2.0-dev,
libgtk-3-dev,
libpam-dev,
-   libqt4-dev,
libxcb1-dev,
libxdmcp-dev,
libxklavier-dev,
@@ -72,15 +71,6 @@
  This package contains the GObject library for lightdm, used by the GTK+
  greeter.
 
-Package: liblightdm-qt-3-0
-Section: libs
-Architecture: any
-Multi-Arch: same
-Pre-depends: ${misc:Pre-Depends}
-Depends: ${misc:Depends}, ${shlibs:Depends}
-Description: simple display manager (Qt library)
- This package contains the Qt library for lightdm.
-
 Package: liblightdm-qt5-3-0
 Section: libs
 Architecture: any
@@ -107,17 +97,6 @@
  This package contains the development files for lightdm.
  They can be used to build new greeters applications GTK+ based.
 
-Package: liblightdm-qt-dev
-Section: libdevel
-Architecture: any
-Multi-Arch: same
-Depends: liblightdm-qt-3-0 (= ${binary:Version}),
- ${misc:Depends},
- ${shlibs:Depends}
-Description: simple display manager (Qt development files)
- This package contains the development files for lightdm.
- They can be used to build new greeters applications Qt based.
-
 Package: liblightdm-qt5-3-dev
 Section: libdevel
 Architecture: any
diff -Naur lightdm-1.26.0.orig/debian/liblightdm-qt-3-0.install lightdm-1.26.0/debian/liblightdm-qt-3-0.install
--- lightdm-1.26.0.orig/debian/liblightdm-qt-3-0.install	2019-07-10 22:34:59.0 +0200
+++ lightdm-1.26.0/debian/liblightdm-qt-3-0.install	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-usr/lib/*/liblightdm-qt-*.so.*
diff -Naur lightdm-1.26.0.orig/debian/liblightdm-qt-3-0.lintian-overrides lightdm-1.26.0/debian/liblightdm-qt-3-0.lintian-overrides
--- lightdm-1.26.0.orig/debian/liblightdm-qt-3-0.lintian-overrides	2019-07-10 22:34:59.0 +0200
+++ lightdm-1.26.0/debian/liblightdm-qt-3-0.lintian-overrides	1970-01-01 01:00:00.0 +0100
@@ -1,2 +0,0 @@
-# we do use -fstack-protector
-liblightdm-qt-3-0: hardening-no-stackprotector usr/lib/x86_64-linux-gnu/liblightdm-qt-3.so.0.0.0
diff -Naur lightdm-1.26.0.orig/debian/liblightdm-qt-3-0.symbols lightdm-1.26.0/debian/liblightdm-qt-3-0.symbols
--- lightdm-1.26.0.orig/debian/liblightdm-qt-3-0.symbols	2019-07-10 22:34:59.0 +0200
+++ lightdm-1.26.0/debian/liblightdm-qt-3-0.symbols	1970-01-01 01:00:00.0 +0100
@@ -1,72 +0,0 @@
-liblightdm-qt-3.so.0 liblightdm-qt-3-0 #MINVER#
- (c++|regex)"^.*::qt_metacall\(QMetaObject::Call, int, void[*][*]\)@Base$" 1.8.7
- (c++|regex)"^.*::qt_metacast\(char const[*]\)@Base$" 1.8.7
- (c++|regex)"^.*::staticMetaObject@Base$" 1.8.7
- (c++|regex)"^.*::metaObject\(\) const@Base$" 1.8.7
- (c++|regex)"^typeinfo for .*@Base$" 1.8.7
- (c++|regex)"^typeinfo name for .*@Base$" 1.8.7
- (c++|regex)"^vtable for .*@Base$" 1.8.7
- (c++)"QLightDM::UsersModel::UsersModel(QObject*)@Base" 1.8.7
- (c++)"QLightDM::UsersModel::~UsersModel()@Base" 1.8.7
- (c++)"QLightDM::SessionsModel::SessionsModel(QLightDM::SessionsModel::SessionType, QObject*)@Base" 1.8.7
- (c++)"QLightDM::SessionsModel::SessionsModel(QObject*)@Base" 1.8.7
- (c++)"QLightDM::SessionsModel::~SessionsModel()@Base" 1.8.7
- (c++)"QLightDM::PowerInterface::canRestart()@Base" 1.8.7
- (c++)"QLightDM::PowerInterface::canSuspend()@Base" 1.8.7
- (c++)"QLightDM::PowerInterface::canShutdown()@Base" 1.8.7
- (c++)"QLightDM::PowerInterface::canHibernate()@Base" 1.8.7
- (c++)"QLightDM::PowerInterface::PowerInterfacePrivate::PowerInterfacePrivate()@Base" 1.8.7
- (c++)"QLightDM::PowerInterface::restart()@Base" 1.8.7
- (c++)"QLightDM::PowerInterface::suspend()@Base" 1.8.7
- (c++)"QLightDM::PowerInterface::shutdown()@Base" 1.8.7
- (c++)"QLightDM::PowerInterface::hibernate()@Base" 1.8.7
- (c++)"QLightDM::PowerInterface::PowerInterface(QObject*)@Base" 1.8.7
- (c++)"QLightDM::PowerInterface::~PowerInterface()@Base" 1.8.7
- (c++)"QLightDM::Greeter::showPrompt(QString, QLightDM::Greeter::PromptType)@Base" 1.8.7
- (c++)"QLightDM::Greeter::connectSync()@Base" 1.8.7
- 

Bug#875087: [phonon-backend-gstreamer] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sat, Sep 09, 2017 at 10:18:38PM +0200, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Source: phonon-backend-gstreamer
> Version: 4:4.9.0-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:

With the removal of src:kde4libs, there are no reverse deps of the Qt4
packages of phonon-backend-gstreamer, patch attached to drop them.

Cheers,
Moritz
diff -Naur phonon-backend-gstreamer-4.9.1.orig/debian/control phonon-backend-gstreamer-4.9.1/debian/control
--- phonon-backend-gstreamer-4.9.1.orig/debian/control	2019-07-30 07:26:24.0 +0200
+++ phonon-backend-gstreamer-4.9.1/debian/control	2019-08-29 20:18:01.483076445 +0200
@@ -13,12 +13,8 @@
libglib2.0-dev,
libgstreamer-plugins-base1.0-dev,
libgstreamer1.0-dev,
-   libphonon-dev (>= 4:4.7.1~),
libphonon4qt5-dev (>= 4:4.7.1~),
libphonon4qt5experimental-dev (>= 4:4.7.1~),
-   libphononexperimental-dev (>= 4:4.7.1~),
-   libqt4-dev (>= 4:4.8.1),
-   libqt4-opengl-dev (>= 4:4.8.1),
libqt5opengl5-dev,
libqt5x11extras5-dev (>= 5.2.0~),
libxml2-dev,
@@ -47,29 +43,6 @@
  .
  This package contains icons used by Phonon and Phonon4Qt5 backends.
 
-Package: phonon-backend-gstreamer
-Architecture: any
-Multi-Arch: same
-Provides: phonon-backend
-Pre-Depends: ${misc:Pre-Depends}
-Depends: gstreamer1.0-alsa [linux-any] | gstreamer1.0-audiosink,
- gstreamer1.0-plugins-base,
- gstreamer1.0-pulseaudio,
- phonon-backend-gstreamer-common (= ${binary:Version}),
- ${misc:Depends},
- ${shlibs:Depends}
-Recommends: gstreamer1.0-plugins-good
-Suggests: gstreamer1.0-plugins-ugly
-Description: Phonon GStreamer 1.0 backend
- This package contains GStreamer 1.0 backend for Phonon multimedia
- framework. It transparently adapts and reroutes all requests from Phonon
- applications to the GStreamer framework which in turn performs requested
- audio/video decoding/capture tasks.
- .
- You should install gstreamer1.0-plugins-good to get support for playing
- popular free multimedia formats and gstreamer1.0-plugins-ugly to get support
- for popular MPEG audio formats like MP3.
-
 Package: phonon4qt5-backend-gstreamer
 Architecture: any
 Multi-Arch: same
diff -Naur phonon-backend-gstreamer-4.9.1.orig/debian/phonon-backend-gstreamer.install phonon-backend-gstreamer-4.9.1/debian/phonon-backend-gstreamer.install
--- phonon-backend-gstreamer-4.9.1.orig/debian/phonon-backend-gstreamer.install	2016-06-06 21:29:58.0 +0200
+++ phonon-backend-gstreamer-4.9.1/debian/phonon-backend-gstreamer.install	1970-01-01 01:00:00.0 +0100
@@ -1,2 +0,0 @@
-usr/lib/*/qt4/plugins/phonon_backend/phonon_gstreamer.so
-usr/share/kde4/services/phononbackends/gstreamer.desktop
diff -Naur phonon-backend-gstreamer-4.9.1.orig/debian/rules phonon-backend-gstreamer-4.9.1/debian/rules
--- phonon-backend-gstreamer-4.9.1.orig/debian/rules	2016-06-06 21:29:58.0 +0200
+++ phonon-backend-gstreamer-4.9.1/debian/rules	2019-08-29 20:14:51.963932199 +0200
@@ -5,33 +5,27 @@
 include /usr/share/pkg-kde-tools/qt-kde-team/2/debian-qt-kde.mk
 
 override_dh_auto_configure:
-	$(overridden_command) -B obj-qt4 -- -DPLUGIN_INSTALL_DIR=/usr/lib/$(DEB_HOST_MULTIARCH)/qt4/
 	$(overridden_command) -B obj-qt5 -- \
 	  -DPLUGIN_INSTALL_DIR=/usr/lib/$(DEB_HOST_MULTIARCH)/qt5/ \
 	  -DPHONON_BUILD_PHONON4QT5=ON
 
 override_dh_auto_build:
-	$(overridden_command) -B obj-qt4
 	$(overridden_command) -B obj-qt5
 
 override_dh_auto_install:
-	$(overridden_command) -B obj-qt4
 	$(overridden_command) -B obj-qt5
 
 override_dh_install:
 	$(overridden_command) --fail-missing
 
 override_dh_auto_clean:
-	$(overridden_command) -B obj-qt4
 	$(overridden_command) -B obj-qt5
 
 override_dh_shlibdeps:
 	$(overridden_command) -- -xphonon
 
 override_dh_auto_test:
-	$(overridden_command) -B obj-qt4
 	$(overridden_command) -B obj-qt5
 
 override_dh_strip:
-	$(overridden_command) -pphonon-backend-gstreamer --dbgsym-migration='phonon-backend-gstreamer-dbg (<= 4:4.9.0-1~~)'
 	$(overridden_command) -pphonon4qt5-backend-gstreamer --dbgsym-migration='phonon4qt5-backend-gstreamer-dbg (<= 4:4.9.0-1~~)'

Bug#934457: installation in chroot failing with Unknown device "/dev/fuse": No such device

[Tyler Weldon]

Hello,

The issue is in the command:

udevadm test --action -p  $(udevadm info -q path -n /dev/fuse)

the -p flag is being seen as a parameter to the --action flag, which is not
a valid action.

Per the udevadm man page:

*-c*, *--action=**ACTION*
Type of event to be triggered. Possible actions are "add", "remove",
"change", "move", "online", "offline", "bind", and "unbind". The default
value is "change".

Hope this helps.

Tyler Weldon
tylerweldo...@gmail.com
(609)-661-9396

Processed: Re: Bug#932108: nextcloud-desktop-cmd: Missing nextcloud-desktop-common leads to error "Cannot load system exclude list[...]"

[Debian Bug Tracking System]

Processing control commands:

> Severity -1 important
Bug #932108 [nextcloud-desktop-cmd] nextcloud-desktop-cmd: Missing 
nextcloud-desktop-common leads to error "Cannot load system exclude list[...]"
Severity set to 'important' from 'grave'

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

Bug#932108: nextcloud-desktop-cmd: Missing nextcloud-desktop-common leads to error "Cannot load system exclude list[...]"

[Sandro Knauß]

Control: Severity -1 important

It does not fit the grave severity, that's why I lower the severity. Never the 
less I'll prepare an update for Buster.

hefee


On Samstag, 10. August 2019 18:59:07 CEST Calogero Lo Leggio wrote:
> Hi,
> 
> I think it's sufficient to add 'nextcloud-desktop-common' in the
> nextcloud-desktop-cmd dependencies
> 
> 
> $ diff -u control.old control
> 
> --- control.old2019-05-17 04:35:50.0 +0200
> +++ control2019-08-10 18:58:11.490413351 +0200
> @@ -122,6 +122,7 @@
>  Architecture: any
>  Depends: libnextcloudsync0 (= ${binary:Version}),
>   libqt5sql5-sqlite,
> + nextcloud-desktop-common,
>   nextcloud-desktop-l10n,
>   ${misc:Depends},
>   ${shlibs:Depends}




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

Bug#936035: marked as done (xfwm4: fails to load due to missing libxfconf-0.so.2)

[Debian Bug Tracking System]

Your message dated Thu, 29 Aug 2019 19:08:11 +0200
with message-id <18ccdd14c3a84d8ce121067c7f1610c4b6271467.ca...@debian.org>
and subject line Re: Bug#936035: xfwm4: fails to load due to missing 
libxfconf-0.so.2
has caused the Debian Bug report #936035,
regarding xfwm4: fails to load due to missing libxfconf-0.so.2
to be marked as done.

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

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


-- 
936035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfwm4
Version: 4.14.0-1
Severity: serious
Justification: Policy 3.5

Dear Maintainer,

xfwm4 fails to start:

$ xfwm4
xfwm4: error while loading shared libraries: libxfconf-0.so.2: cannot
open shared object file: No such file or directory
$ ldd /usr/bin/xfwm4 | grep libxfconf
libxfconf-0.so.3 => /usr/lib/x86_64-linux-gnu/libxfconf-0.so.3
(0x7f74ba2f5000)
libxfconf-0.so.2 => not found
$

Fortunately, installing libxfconf-0-2 does make it load successfully,
but it's not listed as a dependency.

Actually, this bug can be grave (rendering the package unusable)
when libxfconf-0-2 is faded out.

Regards,
-- 
Theppitak Karoonboonyanan
http://linux.thai.net/~thep/

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

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

Versions of packages xfwm4 depends on:
ii  libc6 2.28-10
ii  libcairo2 1.16.0-4
ii  libepoxy0 1.5.3-0.1
ii  libgdk-pixbuf2.0-02.38.1+dfsg-1
ii  libglib2.0-0  2.60.6-2
ii  libgtk-3-03.24.10-1
ii  libpango-1.0-01.42.4-7
ii  libpangocairo-1.0-0   1.42.4-7
ii  libstartup-notification0  0.12-6
ii  libwnck-3-0   3.32.0-1
ii  libx11-6  2:1.6.7-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.5-1
ii  libxext6  2:1.3.3-1+b2
ii  libxfce4ui-2-04.14.1-1+b1
ii  libxfce4util7 4.14.0-1
ii  libxfconf-0-3 4.14.1-1
ii  libxfixes31:5.0.3-1
ii  libxi62:1.7.9-1
ii  libxinerama1  2:1.1.4-2
ii  libxpresent1  1.0.0-2+b10
ii  libxrandr22:1.5.1-1
ii  libxrender1   1:0.9.10-1

Versions of packages xfwm4 recommends:
ii  librsvg2-common  2.44.14-1

Versions of packages xfwm4 suggests:
ii  xfce4  4.14

-- no debconf information
--- End Message ---
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Thu, 2019-08-29 at 23:37 +0700, Theppitak Karoonboonyanan wrote:
> Thanks to your test command suggestion, I find my report was a false alarm.
> And I'm terribly sorry for that.
> 
> The one that drags libxfconf-0.so.2 in is libxfce4kbd-private-3.so.0,
> which appears to be from /usr/local/lib, not from an installed deb!
> I can't recall when I built and installed the local version.
> The file date says some time in 2018.

That was my gut feeling as well :) Thanks for the confirmation, I'm closing
the bug.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl1oBnsACgkQ3rYcyPpX
RFuWyAgA6J/pxAdJxPQBu4lmZR6X7rtxhV/PJ7ujYDcszC5kuJlmmuOMxUsMDBtz
iQU6MXIFylr66V8HJT9bekekjvfYc7PNtuGmQ0s2m4VSGjP0rrodGF2lgUlcGfBC
VX3QOsj7ymctk2o/zmaprLFHLUy3TLYGbDWrVIPFHBr5/aYVe9IaiUnRPXqhsDY2
NpudNPqGy92sF8FJL3rfI6FZyT7Oj0FdNW3Psm8XbKXAVexyhBruVV4r3neJsSl/
cIR72UoPjJJEhr5/J70VsIrDFaYTaktfJFjOYgVIR0SWX6/kS+OhcL6EXeEueOhF
6bgyH5uOs4/MECXkVYTX9kO+2BWG4g==
=48aG
-END PGP SIGNATURE End Message ---

Bug#933922: marked as done (src:salt: Unsafe use of yaml.load())

[Debian Bug Tracking System]

Your message dated Thu, 29 Aug 2019 17:08:29 +
with message-id 
and subject line Bug#933922: fixed in salt 2018.3.4+dfsg1-7
has caused the Debian Bug report #933922,
regarding src:salt: Unsafe use of yaml.load()
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.)


-- 
933922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:salt
Version: 2018.3.4+dfsg1-6
Severity: grave
Tags: security
Justification: user security hole

The new version of pyyaml no longer allows use of yaml.load() without a
loader being specifed.  This raises a deprecation warning which has
caused and autopkgtest failure on this package.  These are generally
trivial to fix, see the upstream guidance [1].

Scott K

[1] https://github.com/yaml/pyyaml/wiki/PyYAML-yaml.load(input)-Deprecation
--- End Message ---
--- Begin Message ---
Source: salt
Source-Version: 2018.3.4+dfsg1-7

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 29 Aug 2019 18:26:56 +0200
Source: salt
Architecture: source
Version: 2018.3.4+dfsg1-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Salt Team 
Changed-By: Benjamin Drung 
Closes: 933922
Changes:
 salt (2018.3.4+dfsg1-7) unstable; urgency=medium
 .
   * doc: Set script type explicitly to text/javascript
   * Use jquery.js from sphinx
   * Symlink vendor JavaScript files before building
   * Use dh_sphinxdoc
   * Fix various spelling mistakes
   * Fix salt to work with python3-yaml 5.1.2-1 (Closes: #933922):
 - Set default_flow_style=None in yaml.dump calls
 - Fix yamldumper test for both py2/py3
   * Bump Standards-Version to 4.4.0 (no changes needed)
   * Switch to debhelper 12
   * Add missing Pre-Depends on ${misc:Pre-Depends}
Checksums-Sha1:
 5c2a59a119bcb00a65e4955a6a38966f55e586e3 4066 salt_2018.3.4+dfsg1-7.dsc
 0d106e97e0a0cf10e5c6ffe4621d59b21a1efff7 103404 
salt_2018.3.4+dfsg1-7.debian.tar.xz
 dc2d3526e585dce88a9ab9dbaa23bc6b0ed4dee3 13302 
salt_2018.3.4+dfsg1-7_source.buildinfo
Checksums-Sha256:
 49201b11cf7f433d9e7c89f5d2e9ba7233c8c5b475611ecc047ca4ea1fb6e8d2 4066 
salt_2018.3.4+dfsg1-7.dsc
 82c97432f0e17a7acc7b6ee9b0dc5a5e598699c19581934d615a0e3659317792 103404 
salt_2018.3.4+dfsg1-7.debian.tar.xz
 f453ebfe10573bf1f28d563ce9f1ae43b242a60fcdc506b3fd6940d97d006223 13302 
salt_2018.3.4+dfsg1-7_source.buildinfo
Files:
 3cefbe274509639efa66bbf3ad1b4323 4066 admin optional salt_2018.3.4+dfsg1-7.dsc
 c8bd45e3d96836ab2de75092cd0912ce 103404 admin optional 
salt_2018.3.4+dfsg1-7.debian.tar.xz
 2856bc378c29e8f3e72220e4d08c05e7 13302 admin optional 
salt_2018.3.4+dfsg1-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE5/q3CzlQJ15towl13YzVpd6MfnoFAl1n/pQACgkQ3YzVpd6M
fnoKTQ/8Cmi5AnOHpfhAQdwQ05JMVCvQHm3fPvP0WoJ2kn4/L22Fz2wudbddIWev
dKobiRUcxv+qdGFvWNCBUDjQoQ+ox/fqaTzG5/LaYWwQICPtkEUgPOFThFD+JUGh
ax0p1UCk8tLarLn/Fji5mWUD+1iqcDcIgQZyR4htnkWCA4R2F8vYlm1/7u2f0uqG
QLxilScQdTt4wB4FhCOZAb5Q1s6bF5cEFUvhckqy2leeNdzzAQcxPnelcDY0YnP2
JNXJfmGqP4QrcOCctHQJaIh8OOgPRUXoszHN3EATXE1Z55tDydxhdHpx+klsMEX4
HFXXPsLXtNTYtKm2T4Cxl6nrlLpYGxWijVoVq4bhZ+wdxOdhVDRa7yyoHDixn8aI
7tvjug7Bzuejk7lWoERRAGZTvdl3bq63k9Ec/mcjvwiiTEBKZnoFANLcDUXOGoQ5
lCUlQQjoyr4WVr76c2E5MYgo90CQyjVaGEjRPA2jJiJbiupQZPckuqdFX+ORpwbP
8adqX5Jh+K/5uLkkFRgTAeu1jBH+oLpEbEgLc99+E5RQD5PdVN552FdwQCu9CJKq
PkK2N7R8fYCVnwJCJQAhdwk2FNLba8BEw1vGMmGqJfQ9yvD4giz1mgqfuO3yAiFG
spIcTV3iOP0y1ktVQq927xdG/wgO/o7grChMLwC91CcTQU0jjyI=
=j53j
-END PGP SIGNATURE End Message ---

Bug#933922: marked as pending in salt

[Benjamin Drung]

Control: tag -1 pending

Hello,

Bug #933922 in salt 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/salt-team/salt/commit/307770ff7b23e520a59bb03d2bea18f554648918


Fix yamldumper test for both py2/py3

Fix salt to work with python3-yaml 5.1.2-1.

Closes: #933922
Signed-off-by: Benjamin Drung 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/933922

Processed: Bug#933922 marked as pending in salt

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #933922 [src:salt] src:salt: Unsafe use of yaml.load()
Added tag(s) pending.

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

Bug#933922: marked as pending in salt

[Benjamin Drung]

Control: tag -1 pending

Hello,

Bug #933922 in salt 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/salt-team/salt/commit/ab64448c27bfa82502980204b570d1d8f1a6dce3


Set default_flow_style=None in yaml.dump calls

Fix salt to work with python3-yaml 5.1.2-1.

Closes: #933922
Signed-off-by: Benjamin Drung 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/933922

Bug#936035: xfwm4: fails to load due to missing libxfconf-0.so.2

[Theppitak Karoonboonyanan]

On Thu, Aug 29, 2019 at 6:25 PM Yves-Alexis Perez  wrote:

> xfwm4 4.14.0-1 (in sid and unstable) is only linked against libxfconf-0.3, not
> libxfconf-0.2, so it's definitely not where the problem lies. Xfce 4.14 just
> migrated to testing so that could explain your issue (which is likely
> transient), but it shouldn't have happened anyway.
>
> Can you install the pax-utils package (and only that package, please try not
> to upgrade anything else) and give us the output of lddtree (so we have an
> idea from where exactly the link comes from).

Thanks to your test command suggestion, I find my report was a false alarm.
And I'm terribly sorry for that.

The one that drags libxfconf-0.so.2 in is libxfce4kbd-private-3.so.0,
which appears to be from /usr/local/lib, not from an installed deb!
I can't recall when I built and installed the local version.
The file date says some time in 2018.

Here's the full output:

$ lddtree /usr/bin/xfwm4
xfwm4 => /usr/bin/xfwm4 (interpreter => /lib64/ld-linux-x86-64.so.2)
libXcomposite.so.1 => /usr/lib/x86_64-linux-gnu/libXcomposite.so.1
libXdamage.so.1 => /usr/lib/x86_64-linux-gnu/libXdamage.so.1
libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3
libepoxy.so.0 => /usr/lib/x86_64-linux-gnu/libepoxy.so.0
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2
libstartup-notification-1.so.0 =>
/usr/lib/x86_64-linux-gnu/libstartup-notification-1.so.0
libxcb-util.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-util.so.0
libX11-xcb.so.1 => /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1
libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6
libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6
libbsd.so.0 => /usr/lib/x86_64-linux-gnu/libbsd.so.0
libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6
libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6
libxfce4kbd-private-3.so.0 => /usr/local/lib/libxfce4kbd-private-3.so.0
libatk-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0
libcairo-gobject.so.2 => /usr/lib/x86_64-linux-gnu/libcairo-gobject.so.2
libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1
libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1
libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1
libpcre2-8.so.0 => /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2
libSM.so.6 => /usr/lib/x86_64-linux-gnu/libSM.so.6
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1
libICE.so.6 => /usr/lib/x86_64-linux-gnu/libICE.so.6
libxfconf-0.so.2 => /usr/lib/x86_64-linux-gnu/libxfconf-0.so.2
libgthread-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgthread-2.0.so.0
libdbus-glib-1.so.2 => /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0
libxfce4ui-2.so.0 => /usr/local/lib/libxfce4ui-2.so.0
libgtk-3.so.0 => /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
libatk-bridge-2.0.so.0 =>
/usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
libatspi.so.0 => /usr/lib/x86_64-linux-gnu/libatspi.so.0
libxkbcommon.so.0 => /usr/lib/x86_64-linux-gnu/libxkbcommon.so.0
libwayland-cursor.so.0 =>
/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0
libwayland-egl.so.1 => /usr/lib/x86_64-linux-gnu/libwayland-egl.so.1
libwayland-client.so.0 =>
/usr/lib/x86_64-linux-gnu/libwayland-client.so.0
libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6
libfribidi.so.0 => /usr/lib/x86_64-linux-gnu/libfribidi.so.0
libharfbuzz.so.0 => /usr/lib/x86_64-linux-gnu/libharfbuzz.so.0
libgraphite2.so.3 => /usr/lib/x86_64-linux-gnu/libgraphite2.so.3
libpangoft2-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0
libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1
libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6
libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16
libgdk-3.so.0 => /usr/lib/x86_64-linux-gnu/libgdk-3.so.0

Processed: Bug#933922 marked as pending in salt

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #933922 [src:salt] src:salt: Unsafe use of yaml.load()
Ignoring request to alter tags of bug #933922 to the same tags previously set

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

Bug#928791: congress: FTBFS twice in a row: File exists: 'congress/tests/etc/keys'

[Sven Eckelmann]

Control: tag -1 + patch

Hi,

On Sat, 11 May 2019 11:34:23 +0200 Andreas Beckmann  wrote:
[...]
> congress/experimental fails to build twice in a row:
> 
> Traceback (most recent call last):
>   File 
> "/build/congress-9.0.0+dfsg1/congress/tests/api/test_datasource_model.py", 
> line 45, in setUp
> self.ds_manager.add_datasource(self.datasource)
>   File "/build/congress-9.0.0+dfsg1/congress/dse2/datasource_manager.py", 
> line 71, in add_datasource
> secret_config_fields=driver_info.get('secret', []))
>   File "/usr/lib/python3/dist-packages/tenacity/__init__.py", line 241, in 
> wrapped_f
> return self.call(f, *args, **kw)
[...]
> FileExistsError: [Errno 17] File exists: 'congress/tests/etc/keys'

Seems like the package (or the pkg utilities) currently doesn't clean up in 
the clean target. Interestingly, even dpkg-source currently fails after a 
build finished. This is caused by following extra files/directories

* Congress.tokens
* build
* */__pycache__/
* congress/tests/etc/keys

The dpkg-source configuration of this package (debian/source/options) 
currently ignores a lot of debian specific files. It would maybe make sense to 
also to ignore __pycache__ this way.

build and Congress.tokens are part of the build and can just be cleaned using 
dh_clean's debian/clean

congress/tests/etc/keys is slightly more interesting. It is part of the files 
generated by the test suite. So congress/tests/api/test_datasource_model.py's 
setUp() method could be changed to take care of this. But I am not familiar 
with this package. But to fix the FTBS "twice in a row" problem, it is enough 
to also delete the test artifact during clean.

Even when this patch is currently formatted like a NMU, it is not part of an 
actual NMU.

Kind regards,
Svendiff -Nru congress-9.0.0+dfsg1/debian/changelog congress-9.0.0+dfsg1/debian/changelog
--- congress-9.0.0+dfsg1/debian/changelog	2019-07-17 15:31:05.0 +0200
+++ congress-9.0.0+dfsg1/debian/changelog	2019-08-28 21:53:11.0 +0200
@@ -1,3 +1,12 @@
+congress (9.0.0+dfsg1-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS twice in a row (Closes: #928791).
+- Ignore __pycache__ artifacts during dpkg-source.
+- Clean build and test artifacts.
+
+ -- Sven Eckelmann   Wed, 29 Aug 2019 18:00:41 +0200
+
 congress (9.0.0+dfsg1-3) unstable; urgency=medium
 
   * Uploading to unstable.
diff -Nru congress-9.0.0+dfsg1/debian/clean congress-9.0.0+dfsg1/debian/clean
--- congress-9.0.0+dfsg1/debian/clean	1970-01-01 01:00:00.0 +0100
+++ congress-9.0.0+dfsg1/debian/clean	2019-08-28 21:38:13.0 +0200
@@ -0,0 +1,3 @@
+Congress.tokens
+build/
+congress/tests/etc/keys/
diff -Nru congress-9.0.0+dfsg1/debian/source/options congress-9.0.0+dfsg1/debian/source/options
--- congress-9.0.0+dfsg1/debian/source/options	2019-07-17 15:31:05.0 +0200
+++ congress-9.0.0+dfsg1/debian/source/options	2019-08-28 21:40:12.0 +0200
@@ -1,3 +1,4 @@
 extend-diff-ignore = "^[^/]*[.]egg-info/"
 extend-diff-ignore = "^congress/datalog/CongressParser.py"
 extend-diff-ignore = "^congress/datalog/CongressLexer.py"
+extend-diff-ignore = "/__pycache__/"


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

Processed: Re: congress: FTBFS twice in a row: File exists: 'congress/tests/etc/keys'

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #928791 [src:congress] congress: FTBFS twice in a row: File exists: 
'congress/tests/etc/keys'
Added tag(s) patch.

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

Processed (with 1 error): NIMBY

[Debian Bug Tracking System]

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

> reassign 922767 texlive-latex-extra
Bug #922767 [libemf] libemf : FTBFS - mv: cannot stat 'refman.pdf': No such 
file or directory -
Bug reassigned from package 'libemf' to 'texlive-latex-extra'.
No longer marked as found in versions 1.0.11-2.
Ignoring request to alter fixed versions of bug #922767 to the same values 
previously set
> forcemerge 920621 922767
Failed to forcibly merge 920621: Not altering archived bugs; see unarchive.

> affects 922767 src:libemf
Bug #922767 [texlive-latex-extra] libemf : FTBFS - mv: cannot stat 
'refman.pdf': No such file or directory -
Added indication that 922767 affects src:libemf
> thanks
Stopping processing here.

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

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

[Andreas Beckmann]

Package: virtualenvwrapper-doc
Version: 4.8.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

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


cheers,

Andreas


virtualenvwrapper=4.3.1-2_virtualenvwrapper-doc=4.8.4-1.log.gz
Description: application/gzip

Bug#936068: python3-gnuplot: missing Breaks+Replaces: python-gnuplot

[Andreas Beckmann]

Package: python3-gnuplot
Version: 1.8-7
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 .../python3-gnuplot_1.8-7_all.deb ...
  Unpacking python3-gnuplot (1.8-7) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-gnuplot_1.8-7_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/python-gnuplot/html/ANNOUNCE.html', 
which is also in package python-gnuplot 1.8-6
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-gnuplot_1.8-7_all.deb


cheers,

Andreas


python-gnuplot=1.8-6_python3-gnuplot=1.8-7.log.gz
Description: application/gzip

Bug#933185: marked as done (fai-server: /etc/fai/apt/sources.list should not contain trusted=yes to skip GPG verification)

[Debian Bug Tracking System]

Your message dated Thu, 29 Aug 2019 15:52:39 +
with message-id 
and subject line Bug#933185: fixed in fai 5.8.5
has caused the Debian Bug report #933185,
regarding fai-server: /etc/fai/apt/sources.list should not contain trusted=yes 
to skip GPG verification
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.)


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

Package: fai-server
Version: 5.8.4
Severity: grave
Tags: security, buster

Dear Maintainer,

fai-server installs /etc/fai/apt/sources.list with the following entry
by default:

deb [trusted=yes] http://fai-project.org/download buster koeln

This is problematic, as the [trusted=yes] part will tell APT to
completely skip cryptographic verification of the repository when
creating the nfsroot. This is extremely bad because the repository is
accessed via unencrypted HTTP, which makes a man-in-the-middle attack
absolutely trivial. True, this only occurs if the NFSROOT is created
and/or updated, but at least updating with make-fai-nfsroot -k should
be a semi-regular thing on well-managed systems.

You should make sure that your APT signing key is added to the
NFSROOT so that APT may check it:

 - Export your GPG signing key in binary (NOT -a!) format:
   gpg --export 2BF8D9FE074BCDE4 > fai-project.gpg

 - Create a directory /etc/fai/apt/trusted.gpg.d

 - Copy the file to the appropriate directory
   cp fai-project.gpg /etc/fai/apt/trusted.gpg.d/

 - Remove the [trusted=yes] part of that line

I've tested this with a pristine FAI install on Debian 10 and during
fai-make-nfsroot the repository is correctly added to the NFSROOT and
the integrity of the signatures is properly checked.

For Debian 9 I don't think this is a critical issue (as the default
configuration does not include the repository, the line is commented
out entirely), but even suggestions in configuration files should
follow established security practices, so I would recommend also
removing the [trusted=yes] comment from the package in Debian 9 (and
also including the key there, or maybe just a comment on how to add
the key), so that inexperienced administrators may avoid the trap that
enabling this repository leads to a security issue.



Best regards,
Christian

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fai-server depends on:
ii  debootstrap  1.0.114
ii  e2fsprogs1.44.5-1
ii  fai-client   5.8.4
ii  xz-utils 5.2.4-1

Versions of packages fai-server recommends:
pn  isc-dhcp-server   
pn  libproc-daemon-perl   
pn  nfs-kernel-server 
ii  openbsd-inetd [inet-superserver]  0.20160825-4
ii  openssh-client1:7.9p1-10
ii  openssh-server1:7.9p1-10
pn  tftpd-hpa | atftpd

Versions of packages fai-server suggests:
ii  binutils   2.31.1-16
pn  debmirror  
pn  fai-setup-storage  
pn  grub2  
pn  perl-tk
ii  qemu-utils 1:3.1+dfsg-8~deb10u1
pn  reprepro   
ii  squashfs-tools 1:4.3-12
ii  xorriso1.5.0-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fai
Source-Version: 5.8.5

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 29 Aug 2019 17:08:49 +0200
Source: fai
Architecture: source
Version: 5.8.5
Distribution: unstable
Urgency: high
Maintainer: Thomas Lange 
Changed-By: Thomas Lange 

Bug#932578: marked as done (Cinnamon Settings fail to start)

[Debian Bug Tracking System]

Your message dated Thu, 29 Aug 2019 15:49:42 +
with message-id 
and subject line Bug#932578: fixed in cinnamon 4.0.10-1
has caused the Debian Bug report #932578,
regarding Cinnamon Settings fail to start
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.)


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

Dear Maintainer,

after dist-upgrading a current sid system cinnamon-settings fail to start. If 
started
from terminal the following backtrace comes up:

/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py:220: 
DeprecationWarning: Gtk.Widget.set_margin_right is deprecated
  self.stack_switcher.set_margin_right(n)
/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py:233: 
DeprecationWarning: Gtk.Window.set_has_resize_grip is deprecated
  self.window.set_has_resize_grip(False)
Traceback (most recent call last):
  File "/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py", line 608, 
in 
window = MainWindow()
  File "/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py", line 244, 
in __init__
for module in modules:
  File "/usr/share/cinnamon/cinnamon-settings/modules/cs_backgrounds.py", line 
5, in 
import imtools
  File "/usr/share/cinnamon/cinnamon-settings/bin/imtools.py", line 623, in 

if Image.VERSION == '1.1.7':
AttributeError: module 'PIL.Image' has no attribute 'VERSION'

Reason is the uncoordinated upload of pillow in ver. 6.1.0-1. Downgrading 
python3-pil "solve" the problem for now.

Cheers Alf

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

Kernel: Linux 5.1.18-towo.1-siduction-amd64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cinnamon depends on:
ii  cinnamon-common  3.8.8-1
ii  cinnamon-control-center  3.8.1-1
ii  cinnamon-desktop-data3.8.1-2
ii  cinnamon-screensaver 3.8.2-1
ii  cinnamon-session 3.8.2-1
ii  cinnamon-settings-daemon 3.8.4-2
ii  cjs  3.8.0-5
ii  cups-pk-helper   0.2.6-1+b1
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  gir1.2-accountsservice-1.0   0.6.45-2
ii  gir1.2-caribou-1.0   0.4.21-7
ii  gir1.2-clutter-1.0   1.26.2+dfsg-10
ii  gir1.2-cmenu-3.0 3.8.2-1
ii  gir1.2-cogl-1.0  1.22.2-6
ii  gir1.2-cvc-1.0   3.8.1-2
ii  gir1.2-gdkpixbuf-2.0 2.38.1+dfsg-1
ii  gir1.2-gkbd-3.0  3.26.1-1
ii  gir1.2-glib-2.0  1.58.3-2
ii  gir1.2-gnomedesktop-3.0  3.30.2.1-2
ii  gir1.2-gtk-3.0   3.24.10-1
ii  gir1.2-gtkclutter-1.01.8.4-4
ii  gir1.2-keybinder-3.0 0.3.2-1
ii  gir1.2-meta-muffin-0.0   3.8.2-1
ii  gir1.2-nm-1.01.18.0-3
ii  gir1.2-nma-1.0   1.8.22-2
ii  gir1.2-notify-0.70.7.7-4
ii  gir1.2-pango-1.0 1.42.4-6
ii  gir1.2-polkit-1.00.105-25
ii  gir1.2-soup-2.4  2.64.2-2
ii  gir1.2-upowerglib-1.00.99.10-1
ii  gir1.2-xapp-1.0  1.2.2-1
ii  gkbd-capplet 3.26.1-1
ii  gnome-backgrounds3.30.0-1
ii  gnome-themes-extra   3.28-1
ii  gsettings-desktop-schemas3.28.1-1
ii  iso-flags-png-320x2401.0.2-1
ii  libatk-bridge2.0-0   2.30.0-5
ii  libatk1.0-0  2.30.0-2
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libcinnamon-desktop4 3.8.1-2
ii  libcinnamon-menu-3-0 3.8.2-1
ii  libcjs0  3.8.0-5
ii  libclutter-1.0-0

Bug#931777: marked as done (cinnamon-settings does not start due incompatibility with python3-pil >= 6.0)

[Debian Bug Tracking System]

Your message dated Thu, 29 Aug 2019 15:49:42 +
with message-id 
and subject line Bug#931777: fixed in cinnamon 4.0.10-1
has caused the Debian Bug report #931777,
regarding cinnamon-settings does not start due incompatibility with python3-pil 
>= 6.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.)


-- 
931777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cinnamon
Version: 3.8.8-1
Severity: important

After upgrade python3-pip from 5.4.1-2 to 6.1.0-1, cinnamon-settings does
not start anymore. Here is the trace:

 $ cinnamon-settings
/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py:220:
DeprecationWarning: Gtk.Widget.set_margin_right is deprecated
  self.stack_switcher.set_margin_right(n)
/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py:233:
DeprecationWarning: Gtk.Window.set_has_resize_grip is deprecated
  self.window.set_has_resize_grip(False)
Traceback (most recent call last):
  File "/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py", line
608, in 
window = MainWindow()
  File "/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py", line
244, in __init__
for module in modules:
  File "/usr/share/cinnamon/cinnamon-settings/modules/cs_backgrounds.py",
line 5, in 
import imtools
  File "/usr/share/cinnamon/cinnamon-settings/bin/imtools.py", line 623, in

if Image.VERSION == '1.1.7':
AttributeError: module 'PIL.Image' has no attribute 'VERSION'

This is already fixed upstream by cinnamon

https://github.com/linuxmint/cinnamon/issues/8495

but a backport should be made in order to run cinnamon-settings in testing
and sid.
--- End Message ---
--- Begin Message ---
Source: cinnamon
Source-Version: 4.0.10-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 29 Aug 2019 12:04:52 -0300
Source: cinnamon
Architecture: source
Version: 4.0.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Cinnamon Team 
Changed-By: Maximiliano Curia 
Closes: 877738 931777 932578
Changes:
 cinnamon (4.0.10-1) unstable; urgency=medium
 .
   [ Maximiliano Curia ]
   * New revision
   * Replace gvfs-bin calls with gio calls.
 Thanks to Simon McVittie for the heads up (Closes: 877738)
   * Salsa CI automatic initialization by Tuco
   * Add a basic gbp.conf
   * Add lintian-override for muffin rpath
   * Release to unstable
 .
   [ Norbert Preining ]
   * Fix disappearing systray indicators (upstream fix)
   * New upstream releases (4.0.5, 4.0.10)
   * Fix cinnamon-settings for PIL >= 6.0.0 (VERSION was removed)
 (Closes: #931777, #932578)
Checksums-Sha1:
 b641ba41640823f300474f4db658b81305522035 2842 cinnamon_4.0.10-1.dsc
 feebef840e3d186c7e2607667cf3ede0792da509 2328500 cinnamon_4.0.10.orig.tar.gz
 5e3cb43aded191eadfdc7e19c771a7628f56808f 106720 cinnamon_4.0.10-1.debian.tar.xz
 c007d1031e33f0706d69584dfb17a885d45f7d31 9032 
cinnamon_4.0.10-1_source.buildinfo
Checksums-Sha256:
 b8be07f9725432d739f08769b441196f3c4f7775908c83b92c1bf36b48a24c32 2842 
cinnamon_4.0.10-1.dsc
 50e07fa014eeecb380e840a3be0f09c8af0ad368c64c6b8ce6c30b1f78a2bf66 2328500 
cinnamon_4.0.10.orig.tar.gz
 51634557902c547e187722afeff3e229ac58179cdf587cca417e981541c9ad5c 106720 
cinnamon_4.0.10-1.debian.tar.xz
 afc2e4214833a9bbbe1666d295f4ec80d744cf70a727ecaf648a513de6f77de6 9032 
cinnamon_4.0.10-1_source.buildinfo
Files:
 d8f086047d020b49501525ff250abccb 2842 x11 optional cinnamon_4.0.10-1.dsc
 6e849f005485664f527acbdf0e0c68bf 2328500 x11 optional 
cinnamon_4.0.10.orig.tar.gz
 030f8dc3da3dbec00b1533e70f92102c 106720 x11 optional 
cinnamon_4.0.10-1.debian.tar.xz
 4bd1fda782b3e84b65b71da6f7efe400 9032 x11 optional 
cinnamon_4.0.10-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE+JIdOnQEyG4RNSIVxxl2mbKbIyoFAl1n7w8ACgkQxxl2mbKb

Bug#922767: libemf : FTBFS - mv: cannot stat 'refman.pdf': No such file or directory -

[Sven Eckelmann]

On Wed, 20 Feb 2019 13:51:13 +0100 "Thierry fa...@linux.ibm.com" 
 wrote:
[...]
> Current compilation fails with message
> 
> /This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live
> 2019/dev/Debian) (preloaded format=pdflatex) restricted \write18
> enabled. entering extended mode (./refman.tex LaTeX2e <2018-12-01> mv:
> cannot stat 'refman.pdf': No such file or directory make[2]: ***
> [Makefile:870: doxygen-doc/libemf.pdf] Error 1 make[2]: Leaving
> directory '/<>' dh_auto_build: make -j4 all doxygen-doc
> doxygen-pdf returned exit code 2 make[1]: *** [debian/rules:13:
> override_dh_auto_build] Error 2/
> 
> The command pdflatext refman.tex fails according to refman.log
> ! Misplaced \cr.
>  \cr 
> 
> l.46 \end{DoxyParams}
[...]

I wanted to check this problem and cannot reproduce this problem. A quick 
search revealed that this is most likely related to #920621. This also seems 
to be reflected in the FTBFS reports from the reproducible-builds [1]. They 
failed after the 2019-01-30 but started to work again after the upload of 
texlive-extra 2018.20190227-1. 

Can you please check again. I would assume this can be reassigned after 
confirmation to texlive-latex-extra:

   reassign 922767 texlive-latex-extra 
   forcemerge 920621 922767
   affects 922767 src:libemf
   thanks

Kind regards,
Sven

[1] https://tests.reproducible-builds.org/debian/history/libemf.html

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

Bug#931609: Update release names after the Buster release.

[Andreas Beckmann]

On 28/08/2019 19.40, Sandro Tosi wrote:
> please cancel the NMU, i'll update reportbug with this patch today. I

Thanks!

Unfortunately you didn't re-enable oldstable_pu in reportbug/debbugs.py,
so there is no stretch-pu support any more :-(

> will not take care of stables uploads tho

OK, I'll take care of these.

Andreas

Bug#918595: marked as pending in ruby-seed-fu

[Jongmin Kim]

Control: tag -1 pending

Hello,

Bug #918595 in ruby-seed-fu 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/ruby-team/ruby-seed-fu/commit/4c72d7a203deb6b6ca8728003658b28510648b06


Patch for fixing the API mismatch from ActiveRecord 5.1

(Closes: #918595)

Signed-off-by: Jongmin Kim 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/918595

Processed: Bug#918595 marked as pending in ruby-seed-fu

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #918595 [src:ruby-seed-fu] ruby-seed-fu FTBFS with rails 5.2
Added tag(s) pending.

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

Processed: Re: Bug#913756: tootle: Tootle window opens and closes immediately

[Debian Bug Tracking System]

Processing control commands:

> reassign 913756 libgranite5,tootle
Bug #913756 [tootle] tootle: Tootle window opens and closes immediately
Bug reassigned from package 'tootle' to 'libgranite5,tootle'.
No longer marked as found in versions tootle/0.2.0-1.
Ignoring request to alter fixed versions of bug #913756 to the same values 
previously set
> found -1 tootle/0.2.0-1
Bug #913756 [libgranite5,tootle] tootle: Tootle window opens and closes 
immediately
Marked as found in versions tootle/0.2.0-1.
> found -1 granite/5.2.3-1
Bug #913756 [libgranite5,tootle] tootle: Tootle window opens and closes 
immediately
Marked as found in versions granite/5.2.3-1.
> tag 913756 + fixed-upstream
Bug #913756 [libgranite5,tootle] tootle: Tootle window opens and closes 
immediately
Added tag(s) fixed-upstream.

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

Bug#913756: tootle: Tootle window opens and closes immediately

[Axel Beckert]

Control: reassign 913756 libgranite5,tootle
Control: found -1 tootle/0.2.0-1
Control: found -1 granite/5.2.3-1
Control: tag 913756 + fixed-upstream

Hi,

context for the granite maintainers: Since the switch to granite 5.2,
tootle crashes upon startup with "[GLib-GIO] Settings schema
'io.elementary.desktop.wingpanel.datetime' is not installed".

Federico Ceratto wrote:
> Temporary workaround: download the package for your architecture from
> https://snapshot.debian.org/package/granite/5.1.0-2/\#libgranite5_5.1.0-2
> and install it with sudo dpkg -i 

This is because of a change in granite 5.2.x up to 5.2.3 (which is
currently in Buster, Bullseye and Sid).

According to
https://github.com/bleakgrey/tootle/issues/107#issuecomment-510074740
granite upstream has reverted that controversial change in granite
5.2.4, so the issue is now actually more or less in granite — but only
(or mostly) seems to affect tootle.

Hence reassigning this issue to both, granite and tootle as a fix in
any of them could solve this issue.

It though should be fixed in granite by uploading 5.2.4 to Debian
Unstable. (Hence the "fixed-upstream" tag which refers to granite
upstream. :-)

It might also help to have tootle depend on "libgranite5 (<< 5.2) |
libgranite5 (>= 5.2.4)" in the future to avoid this issue popping up
again during upgrades or when backporting.

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#933922: [Pkg-salt-team] Bug#933922: src:salt: Unsafe use of yaml.load()

[Benjamin Drung]

Am Montag, den 05.08.2019, 01:41 -0400 schrieb Scott Kitterman:
> Package: src:salt
> Version: 2018.3.4+dfsg1-6
> Severity: grave
> Tags: security
> Justification: user security hole
> 
> The new version of pyyaml no longer allows use of yaml.load() without
> a
> loader being specifed.  This raises a deprecation warning which has
> caused and autopkgtest failure on this package.  These are generally
> trivial to fix, see the upstream guidance [1].

This was already reported to upstream in 
https://github.com/saltstack/salt/issues/39531 and was fixed by pull
request https://github.com/saltstack/salt/pull/40751

I will cherry-pick these changes.

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

1&1 IONOS Cloud GmbH | Greifswalder Str. 207 | 10405 Berlin | Germany
E-mail: benjamin.dr...@cloud.ionos.com | Web: www.ionos.de

Head Office: Berlin, Germany
District Court Berlin Charlottenburg, Registration number: HRB 125506 B
Executive Management: Christoph Steffens, Matthias Steinberg, Achim
Weiss

Member of United Internet

Bug#930363: faad2: fix build with gcc-9 [patch]

[Hugo Lefeuvre]

Hi Fabian,

> Am Donnerstag, den 29.08.2019, 08:04 -0400 schrieb Hugo Lefeuvre:
> > Fabian (faad2 maintainer and upstream), do you want to handle this?
> > Otherwise I can NMU a second time with this patch.
> 
> please go ahead with a second NMU. I am a bit short on time currently
> (home alone with the 10mo baby...).

Ack, I'll NMU then. Good luck with the baby :)

cheers,
Hugo

-- 
Hugo Lefeuvre (hle)|www.owl.eu.com
RSA4096_ 360B 03B3 BF27 4F4D 7A3F D5E8 14AA 1EB8 A247 3DFD
ed25519_ 37B2 6D38 0B25 B8A2 6B9F 3A65 A36F 5357 5F2D DC4C


signature.asc
Description: PGP signature

Bug#936049: metview: missing libopenmpi-dev dependency?

[Alastair McKinstry]

odb-api includes mpi-default-dev, which defaults to libopenmpi-dev.

This may be failing if another mpi (mpich-dev) is installed instead. I 
agree hard-coding including libopenmpi-dev is needed for the moment.


The CMake code in the ECMWF stack (eccodes, magics++, metview, ...) is 
brittle, and leaks dependencies. Adding a dependency lower down the 
chain (eg odb-api)  breaks packages up the chain (metview) unless they 
include all dev libraries, etc. which in turn is bad for transitions.


I've recently packaged the underlying build cmake code (ecbuild, 
currently bundled into the ECMWF tarballs), and will start patching it 
to fix this brittleness; if eg libodb-api.so is built with libssl.so, 
libssl-dev should not be needed for metview to build.


Secondly, i'm refactoring some of the components. eckit, fckit, atlas 
are available independently at github so I'm packaging them separately 
from odb-api.


regards

Alastair


On 29/08/2019 13:35, Gianfranco Costamagna wrote:

Source: odb-api
Version: 0.18.1-6
Severity: serious
tags: patch

Hello, looks like for some reasons eckit in Ubuntu fails to see the include 
directory for openmpi, because it simply doesn't exist

adding libopenmpi-dev dependency to odb-api should fix the issue, bringing the 
directory back when cmake tries to find header files
/usr/lib/x86_64-linux-gnu/pkgconfig/odb.pc:ODB_CC=/usr/bin/cc -pthread 
-I/usr/lib/x86_64-linux-gnu/openmpi/include 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -Wdate-time 
-D_FORTIFY_SOURCE=2 -pipe -fopenmp -fPIC -I${prefix}/include
/usr/lib/x86_64-linux-gnu/cmake/odb/odb-import.cmake:set(ODB_ENVIRONMENT 
"ODB_ROOT=/usr;ODB_SYSPATH=/usr/include;ODB_BINPATH=/usr/bin;ODB_BEBINPATH=/usr/bin;ODB_FEBINPATH=/usr/bin;ODB_LIBPATH=/usr/lib;ODB_RTABLE_PATH=/usr/share/odb;ODB_SYSDBPATH=/usr/share/odb;ODB_CC=/usr/bin/cc
 -pthread -I/usr/lib/x86_64-linux-gnu/openmpi/include 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -Wdate-time -D_FORTIFY_SOURCE=2 -pipe 
-fopenmp -fPIC -I/usr/include;ODB_F90=/usr/bin/gfortran -g -O2 
-fdebug-prefix-map=/build/odb-api=. -fstack-protector-strong -fopenmp -fPIC 
-ffree-line-length-none -I/usr/include -I/usr/module 
-I/usr/odb/module;ODB_COMPILER=/usr/bin/odb98.x -V 
-O3;ODB_COMPILER_FLAGS=/usr/share/odb/odb98.flags;ODB_STATIC_LINKING=1;ODB_LD_SHARED=none;ODB_LD_SHARED_SFX=.so;ODB_IOASSIGN_MAXPROC=32;ODB_IOASSIGN_PARAMS=-r
 1m -w 
1m;ODB_AR=/usr/bin/ar;ODB_GZIP=/bin/gzip;ODB_GUNZIP=/bin/gunzip;ODB_SETUP_SHELL=/bin/sh")

it looks like used and needed


snip of the failing log:

-- The following OPTIONAL packages have not been found:

  * Git
  * fckit (required version >= 0.6.2)
  * transi (required version >= 0.4.4)
  * CGAL
  * gridtools_storage

-- ENABLE_EXPOSE_SUBPACKAGES is On:
-- All packages in the bundle will be installed at the same level into:
--   /usr
-- Configuring done
CMake Error in atlas/src/atlas/CMakeLists.txt:
   Imported target "eckit_mpi" includes non-existent path

 "/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi"

   in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

   * The path was deleted, renamed, or moved to another location.

   * An install or uninstall procedure did not complete successfully.

   * The installation package was faulty and references files it does not
   provide.



CMake Error in atlas/src/atlas/CMakeLists.txt:
   Imported target "eckit_mpi" includes non-existent path

 "/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi"

   in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

   * The path was deleted, renamed, or moved to another location.

   * An install or uninstall procedure did not complete successfully.

   * The installation package was faulty and references files it does not
   provide.


trivial patch here:
https://launchpad.net/ubuntu/+source/odb-api/0.18.1-6ubuntu1

Gianfranco


--
Alastair McKinstry, email: alast...@sceal.ie, matrix: @alastair:sceal.ie, 
phone: 087-6847928
Green Party Councillor, Galway County Council

Bug#931255: Update in stable?

[Mathieu Parent]

Le jeu. 29 août 2019 à 15:39, Christoph Haas  a écrit :
>
> I would like to see this simple fix in Buster. Without it the package is 
> nearly unusable in my opinion. Do you think the release team would agree?

Yes, the release team will agree.

Unfortunately, I won't work on this soon.

Regards
-- 
Mathieu Parent

Bug#931255: Update in stable?

[Christoph Haas]

I would like to see this simple fix in Buster. Without it the package
is nearly unusable in my opinion. Do you think the release team would
agree?

…Christoph

Bug#930363: faad2: fix build with gcc-9 [patch]

[Fabian Greffrath]

Dear Hugo,

Am Donnerstag, den 29.08.2019, 08:04 -0400 schrieb Hugo Lefeuvre:
> Fabian (faad2 maintainer and upstream), do you want to handle this?
> Otherwise I can NMU a second time with this patch.

please go ahead with a second NMU. I am a bit short on time currently
(home alone with the 10mo baby...).

Thanks!

 - Fabian



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

Processed: severity of 935527 is serious

[Debian Bug Tracking System]

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

> severity 935527 serious
Bug #935527 [scantool] scantool: FTBFS due to undefined reference to symbol 
'ceilf@@GLIBC_2.4'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#936049: metview: missing libopenmpi-dev dependency?

[Gianfranco Costamagna]

Source: odb-api
Version: 0.18.1-6
Severity: serious
tags: patch

Hello, looks like for some reasons eckit in Ubuntu fails to see the include 
directory for openmpi, because it simply doesn't exist

adding libopenmpi-dev dependency to odb-api should fix the issue, bringing the 
directory back when cmake tries to find header files
/usr/lib/x86_64-linux-gnu/pkgconfig/odb.pc:ODB_CC=/usr/bin/cc -pthread 
-I/usr/lib/x86_64-linux-gnu/openmpi/include 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -Wdate-time 
-D_FORTIFY_SOURCE=2 -pipe -fopenmp -fPIC -I${prefix}/include
/usr/lib/x86_64-linux-gnu/cmake/odb/odb-import.cmake:set(ODB_ENVIRONMENT 
"ODB_ROOT=/usr;ODB_SYSPATH=/usr/include;ODB_BINPATH=/usr/bin;ODB_BEBINPATH=/usr/bin;ODB_FEBINPATH=/usr/bin;ODB_LIBPATH=/usr/lib;ODB_RTABLE_PATH=/usr/share/odb;ODB_SYSDBPATH=/usr/share/odb;ODB_CC=/usr/bin/cc
 -pthread -I/usr/lib/x86_64-linux-gnu/openmpi/include 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -Wdate-time 
-D_FORTIFY_SOURCE=2 -pipe -fopenmp -fPIC 
-I/usr/include;ODB_F90=/usr/bin/gfortran -g -O2 
-fdebug-prefix-map=/build/odb-api=. -fstack-protector-strong -fopenmp -fPIC 
-ffree-line-length-none -I/usr/include -I/usr/module 
-I/usr/odb/module;ODB_COMPILER=/usr/bin/odb98.x -V 
-O3;ODB_COMPILER_FLAGS=/usr/share/odb/odb98.flags;ODB_STATIC_LINKING=1;ODB_LD_SHARED=none;ODB_LD_SHARED_SFX=.so;ODB_IOASSIGN_MAXPROC=32;ODB_IOASSIGN_PARAMS=-r
 1m -w 
1m;ODB_AR=/usr/bin/ar;ODB_GZIP=/bin/gzip;ODB_GUNZIP=/bin/gunzip;ODB_SETUP_SHELL=/bin/sh")

it looks like used and needed


snip of the failing log:

-- The following OPTIONAL packages have not been found:

 * Git
 * fckit (required version >= 0.6.2)
 * transi (required version >= 0.4.4)
 * CGAL
 * gridtools_storage

-- ENABLE_EXPOSE_SUBPACKAGES is On:
-- All packages in the bundle will be installed at the same level into:
--   /usr
-- Configuring done
CMake Error in atlas/src/atlas/CMakeLists.txt:
  Imported target "eckit_mpi" includes non-existent path

"/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.



CMake Error in atlas/src/atlas/CMakeLists.txt:
  Imported target "eckit_mpi" includes non-existent path

"/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.


trivial patch here:
https://launchpad.net/ubuntu/+source/odb-api/0.18.1-6ubuntu1

Gianfranco

Bug#933666: marked as done (leaflet-image: fails to build with webpack 4)

[Debian Bug Tracking System]

Your message dated Thu, 29 Aug 2019 12:20:16 +
with message-id 
and subject line Bug#933666: fixed in leaflet-image 0.4.0~dfsg-2
has caused the Debian Bug report #933666,
regarding leaflet-image: fails to build with webpack 4
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.)


-- 
933666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: leaflet-image
Version: 0.4.0~dfsg-1
Severity: important
Control: tags -1 patch

When building with webpack 4, this package fails with error,

mkdir --parents debian/js   uglifyjs --compress --mangle \  
--in-source-map leaflet-image.js.map \  
--source-map debian/js/leaflet-image.min.js.map \   
--output debian/js/leaflet-image.min.js -- leaflet-image.js 
fs.js:115   
throw err;  ^   
Error: ENOENT: no 
such file or directory, open 'leaflet-image.js.map'

Now webpack creates output files relative to dist directory.

This commit -> 
https://salsa.debian.org/js-team/leaflet-image/commit/c177c223f86facce929bab19f891675d4e511eb0
 in webpack4 branch of salsa fixes it.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.--- End Message ---
--- Begin Message ---
Source: leaflet-image
Source-Version: 0.4.0~dfsg-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 29 Aug 2019 13:01:52 +0200
Source: leaflet-image
Architecture: source
Version: 0.4.0~dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Closes: 933666
Changes:
 leaflet-image (0.4.0~dfsg-2) unstable; urgency=medium
 .
   * Fix clean generated documentation.
   * Fix set leafletImage (not leaflet-image) as window global,
 to match upstream build routines.
   * Fix have webpack look for modules below /usr/share
 (not only /usr/lib).
   * Fix explicitly set webpack output.path, (mandatory since Webpack 4).
 Closes: Bug#933666. Thanks to Pirate Praveen.
   * Fix browser library source-map reference, by having webpack uglify.
 Stop build-depend on node-source-map node-uglify.
   * Declare compliance with Debian Policy 4.4.0.
   * Mark autopkgtest as superficial.
   * Install nodejs code under /usr/share (not /usr/lib).
Checksums-Sha1:
 aaaedf18af76784257a8d292d380b060771f45cb 2168 leaflet-image_0.4.0~dfsg-2.dsc
 3926ddb24c0a65ee986208272d67f9d08330d99f 4840 
leaflet-image_0.4.0~dfsg-2.debian.tar.xz
 fd9f6c436175c57f1c6115b7bf8640626ed57188 14885 
leaflet-image_0.4.0~dfsg-2_amd64.buildinfo
Checksums-Sha256:
 236049e373fbd567e45e3566590831524612cd80e13fccbb0c52ceeaa50fe71b 2168 
leaflet-image_0.4.0~dfsg-2.dsc
 ea73c3c80c920bce10bd3e9560ea773e3c35aafaf079ccffe1a395a980f897a6 4840 
leaflet-image_0.4.0~dfsg-2.debian.tar.xz
 8434c1382730fa0bdb59fcf0dfd974a68b9a3165c1ae68437e0fa232fc6e6662 14885 
leaflet-image_0.4.0~dfsg-2_amd64.buildinfo
Files:
 2dfb15653d0ae0fffb472823f1117ea9 2168 javascript optional 
leaflet-image_0.4.0~dfsg-2.dsc
 8fbc1ae8f38f233b5d772ba97c3de4ba 4840 javascript optional 
leaflet-image_0.4.0~dfsg-2.debian.tar.xz
 a8870867e163ce36b8078a7936bee6ef 14885 javascript optional 
leaflet-image_0.4.0~dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl1nt/oACgkQLHwxRsGg
ASGjgQ//QJG3D4CnxSQkZOFoKV0e/r2LrYToOWVIV242weLxXinV+rJLA8YTnVL7
22+fj37NpcoCzOAhyNSwnl5kyUTzZYhL8de53j33+lST33x0lvENM4BWtKXTqtaB
4MfzdVo6GUkSI9xfZ2Ny5WAoHbuNYApIu/PaAtvp8RqxK1iHeYO4h6w5XhRbPEU9
gOb3lP25KRFDhTUakSTdMsgWnw9LRiX+Y/TzJRqJN4pe7yrQo34mMp90MmLhlMFa

Bug#930363: faad2: fix build with gcc-9 [patch]

[Hugo Lefeuvre]

Hi Gianfranco,

On Thu, Aug 29, 2019 at 07:43:15AM +0200, Gianfranco Costamagna wrote:
> control: severity -1 serious
> On Tue, 11 Jun 2019 15:06:01 +0200 Gianfranco Costamagna 
>  wrote:
> > Source: faad2
> > Version: 2.8.8-3
> > Severity: normal
> > tags: patch
> > 
> > Hello, looks like gcc-9 is adding wl,asneeded flag in compilation, so libs
> > passed as CFLAGS are not correctly used by gcc anymore, because only LIBS
> > is added at the end of the compilation line.
> > 
> > The following patch fixes the issue, and starts then using again the glib
> > implementation of the library.  (without the patch, the bundled version is
> > used everywhere, and the build fails only on i386 because of an
> > implementation mismatch of a long/int data type)
> > 
> > I reported the patch already upstream
> > https://sourceforge.net/p/faac/bugs/242/
> > patch: 
> > http://launchpadlibrarian.net/427773869/faad2_2.8.8-3_2.8.8-3ubuntu1.diff.gz
> 
> Now this bug is RC, and preventing CVE fixes from Migration.
> Hugo, can you please reupload with the Ubuntu patch?
> https://launchpad.net/ubuntu/+source/faad2/2.8.8-3.1ubuntu1
> I rebased it with the upstream version

Fabian (faad2 maintainer and upstream), do you want to handle this?

Otherwise I can NMU a second time with this patch.

cheers,
Hugo

-- 
Hugo Lefeuvre (hle)|www.owl.eu.com
RSA4096_ 360B 03B3 BF27 4F4D 7A3F D5E8 14AA 1EB8 A247 3DFD
ed25519_ 37B2 6D38 0B25 B8A2 6B9F 3A65 A36F 5357 5F2D DC4C


signature.asc
Description: PGP signature

Processed: Bug#933666 marked as pending in leaflet-image

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #933666 [leaflet-image] leaflet-image: fails to build with webpack 4
Added tag(s) pending.

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

Bug#933666: marked as pending in leaflet-image

[Jonas Smedegaard]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/leaflet-image/commit/27116f225295b2741e62a54822b64e9d28a7bb0c


Fix explicitly set webpack output.path, (mandatory since Webpack 4). Closes: 
Bug#933666. Thanks to Pirate Praveen.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/933666

Bug#936035: xfwm4: fails to load due to missing libxfconf-0.so.2

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Thu, 2019-08-29 at 17:31 +0700, Theppitak Karoonboonyanan wrote:
> Package: xfwm4
> Version: 4.14.0-1
> Severity: serious
> Justification: Policy 3.5
> 
> Dear Maintainer,
> 
> xfwm4 fails to start:
> 
> $ xfwm4
> xfwm4: error while loading shared libraries: libxfconf-0.so.2: cannot
> open shared object file: No such file or directory
> $ ldd /usr/bin/xfwm4 | grep libxfconf
> libxfconf-0.so.3 => /usr/lib/x86_64-linux-gnu/libxfconf-0.so.3
> (0x7f74ba2f5000)
> libxfconf-0.so.2 => not found
> $
> 
> Fortunately, installing libxfconf-0-2 does make it load successfully,
> but it's not listed as a dependency.
> 
> Actually, this bug can be grave (rendering the package unusable)
> when libxfconf-0-2 is faded out.

Hi,

xfwm4 4.14.0-1 (in sid and unstable) is only linked against libxfconf-0.3, not
libxfconf-0.2, so it's definitely not where the problem lies. Xfce 4.14 just
migrated to testing so that could explain your issue (which is likely
transient), but it shouldn't have happened anyway.

Can you install the pax-utils package (and only that package, please try not
to upgrade anything else) and give us the output of lddtree (so we have an
idea from where exactly the link comes from). My guess would be libxfce4ui, so
if you could give us the output of dpkg -l |grep libxfce4ui in the same reply
it'd be nice.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl1nthwACgkQ3rYcyPpX
RFtJdggAwHZABAc+x8sq0L8u6uihUu74OJZkJkqZMNbImDBrpc/e8hrvDFwJBOrN
uU/o83cFnsG+gUzyZCGJEuID8QbY+GsTmHCPzTGBScK2sSV7igpJgkBDH7JR7GQd
SOGloR8ui4tkWXAxYHVs640FGMmnc6wDmuLfewWtF85unSUJKY/hILEO3S4Ew32o
g5E2fsyPeJ3Rxbv01IQmDg3OwMW/MkdWOOaCZxWSbfTD7BGHayFXVdZacGJrSMVW
ao3qC6XoGHjR9rc0thHRTNORcEidcnHP8fjWa+AVnCDPv2WX2EomiCPTqy1pBoRk
eE47hTHBrZEjujPBwWJJZFvJxfRhZg==
=xCEb
-END PGP SIGNATURE-

Bug#936040: isc-kea: CVE-2019-6472 CVE-2019-6473 CVE-2019-6474

[Salvatore Bonaccorso]

Source: isc-kea
Version: 1.5.0-2
Severity: grave
Tags: security upstream

Hi,

The following vulnerabilities were published for isc-kea.

CVE-2019-6472[0]:
|A packet containing a malformed DUID can cause the kea-dhcp6 server to
|terminate

CVE-2019-6473[1]:
|An invalid hostname option can cause the kea-dhcp4 server to terminate

CVE-2019-6474[2]:
|An oversight when validating incoming client requests can lead to a
|situation where the Kea server will exit when trying to restart

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-6472
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6472
[1] https://security-tracker.debian.org/tracker/CVE-2019-6473
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6473
[2] https://security-tracker.debian.org/tracker/CVE-2019-6474
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6474

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#924548: marked as done (gnome-core: does not actually install a desktop environment on s390x)

[Debian Bug Tracking System]

Your message dated Thu, 29 Aug 2019 10:50:19 +
with message-id 
and subject line Bug#924548: fixed in meta-gnome3 1:3.30+2
has caused the Debian Bug report #924548,
regarding gnome-core: does not actually install a desktop environment on s390x
to be marked as done.

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

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


-- 
924548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-core
Version: 1:3.30+1
Severity: serious
Justification: we should make a decision one way or another before release

I recently changed gnome-core to install gnome-flashback instead of
GNOME Shell on s390x, because: GNOME Shell is uninstallable on s390x, due
to mozjs60 not being functional there; testing migration requires task
packages to be installable; and the release team were not willing to waive
that requirement for s390x, because d-i maintainers were concerned that
d-i might do the wrong thing if asked to install an uninstallable task.

However, the observant will realise that gnome-flashback is
not the package I meant. I should have added a dependency on
gnome-session-flashback (a complete GNOME-2-derived desktop with a
panel and a window manager), not on gnome-flashback (a helper for
gnome-session-flashback that doesn't do anything particularly useful
on its own). (I only found this out because I happened to have tried
installing GNOME Flashback on a test VM while trying to reproduce an
unrelated bug.)

It gets worse: gnome-session-flashback requires gnome-panel, which is
unbuildable on s390x, because it build-depends on gdm. This can be worked
around with a sufficiently horrible hack (see below), but I can't help
questioning whether we should.

Note that I can't actually test any of this, because (real or virtual)
s390x machines normally don't have any displays, and after spending
a significant amount of time setting up a s390x qemu virtual machine
I was unable to get XDMCP forwarding to work. If there are people who
care about graphics on s390x machines, perhaps they can explain how?

By this point I feel as though I have already put orders of magnitude
more time and effort into GNOME on s390x than it deserves: GNOME is a
desktop environment, designed to be run on desktops and laptops, not
on $15K mainframes with no displays. In particular, I cannot justify
putting time and effort into fixing the remaining failing tests in mozjs60
(although s390x porters and JavaScript enthusiasts are of course welcome
to do so, and I'm happy to point people in the right directions to avoid
duplicate work).

Options are:

* Deliberately stop trying to install a full desktop environment on s390x:
  make gnome-core stop depending on lightdm, gnome-session, gnome-shell
  or gnome-shell-extensions on s390x, with no replacement. This
  would effectively mean that gnome-core means "the core GNOME apps,
  but no desktop environment" on s390x, and "the core GNOME desktop"
  everywhere else.

* Hack gnome-panel to build successfully on s390x, for example with
  ,
  and apply s/gnome-flashback/gnome-session-flashback/ to the gnome-core
  dependencies. This might need extra work if gnome-panel is not the only
  missing package.

* Close this bug and leave gnome-core as-is. I suspect that no end user
  will report a bug about its current broken state on s390x for the entire
  lifetime of buster, at which point we can use this as evidence that
  nobody actually wants desktop tasks on mainframes. (I am not entirely
  serious about this being an option, but not entirely joking either.)

Does anyone have any input on this?

smcv
--- End Message ---
--- Begin Message ---
Source: meta-gnome3
Source-Version: 1:3.30+2

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated meta-gnome3 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 29 Aug 2019 11:24:18 +0100

Bug#935692: marked as done (cpufreqd: FTBFS on ppc64el)

[Debian Bug Tracking System]

Your message dated Thu, 29 Aug 2019 10:49:38 +
with message-id 
and subject line Bug#935692: fixed in cpufreqd 2.4.2-2.2
has caused the Debian Bug report #935692,
regarding cpufreqd: FTBFS on ppc64el
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.)


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

Hi,

A binnmu of cpufreqd in unstable fails on ppc64el:

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

This might be related to changes in libcpupower in the latest linux upload.

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: cpufreqd
Source-Version: 2.4.2-2.2

We believe that the bug you reported is fixed in the latest version of
cpufreqd, 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.
Frédéric Bonnard  (supplier of updated cpufreqd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 29 Aug 2019 12:30:53 +0200
Binary: cpufreqd cpufreqd-dbgsym
Source: cpufreqd
Architecture: ppc64el source
Version: 2.4.2-2.2
Distribution: unstable
Urgency: medium
Maintainer: Mattia Dongili 
Changed-By: Frédéric Bonnard 
Closes: 935692
Description: 
 cpufreqd   - fully configurable daemon for dynamic frequency and voltage scali
Changes:
 cpufreqd (2.4.2-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix build on power* since linux 5.1 introduced backward incompatilities in
 libcpupower (Closes: #935692)
Checksums-Sha1: 
 578898687d0da459ecacdd2d95cb3f37f9508ae2 2020 cpufreqd_2.4.2-2.2.dsc
 6d045017e0b87a2c0163b53c2ab9c857dd45fa4b 11604 cpufreqd_2.4.2-2.2.debian.tar.xz
 5159eb6da847809fe085d9c654ed757926ca7028 141292 
cpufreqd-dbgsym_2.4.2-2.2_ppc64el.deb
 25117e8bfd9fb11ff557ba9de84028a69591ffc6 5810 
cpufreqd_2.4.2-2.2_ppc64el.buildinfo
 910280082058ece338b72770a66cbe1658ff2ed6 79508 cpufreqd_2.4.2-2.2_ppc64el.deb
Checksums-Sha256: 
 981af9697b9fbadcd9f5f921c196722cc15355578ecdcd786b3e2d75a4e0b208 2020 
cpufreqd_2.4.2-2.2.dsc
 994ff2374a320a6334eeeb10f86fe292f1553fd1ba45d1cf39c4b0dd32875901 11604 
cpufreqd_2.4.2-2.2.debian.tar.xz
 f646eee6763ac761ea3cb62f85da3e5b3d7b50cc4bbf362b9e2217f50b9d9158 141292 
cpufreqd-dbgsym_2.4.2-2.2_ppc64el.deb
 c77067334c7ea78ca77e0e8ce1c8fcd79d875589e9698eeefc795e534fb618d5 5810 
cpufreqd_2.4.2-2.2_ppc64el.buildinfo
 5eaee835caf81260c70ebb81e749c808f90d824e3898dec353dfa39a21fd51e6 79508 
cpufreqd_2.4.2-2.2_ppc64el.deb
Files: 
 e82a88b42de59b532a69979d61b0b874 2020 admin optional cpufreqd_2.4.2-2.2.dsc
 a8a6c12c2f36547207cbde6bc91f39bf 11604 admin optional 
cpufreqd_2.4.2-2.2.debian.tar.xz
 fdbbbaf4d6cf049db876d268a18d87e3 141292 debug optional 
cpufreqd-dbgsym_2.4.2-2.2_ppc64el.deb
 093ceb4353305ead854fb177373a9d77 5810 admin optional 
cpufreqd_2.4.2-2.2_ppc64el.buildinfo
 3f6f4b4e86ce94473d96300d045affb8 79508 admin optional 
cpufreqd_2.4.2-2.2_ppc64el.deb

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEh9vVdWFVIC7DiF6Ta3SY/LmzWKwFAl1nqwYSHGZyZWRpekBk
ZWJpYW4ub3JnAAoJEGt0mPy5s1is4ooQAIvGaXeRMU0WyHgU/8kbsr3rNgBI7cfw
xq9BFCJ2I1bD4WlQwNbBzQG3WDDv5BQV3qnVszl5AdKgZr8ovXwYNQV1yhWEwzyf
kBbZSDoGqBiCCRMSsVQAPxPGqXaXmykT4bUv8syKrp7RdJzsaJk9Tx/fWb5Hze4W
MxP1wCy1MzlVPCaW5Njs4AXla47OtApfFJektb/7oTFrVA/2rfRRmtKytz6lZU/7
QCMPur2ua4lC1k99zVQyyO62Maqqiugcno35Dryokz1TeSd1D71arHdOvwfgTXhB
LTH9pSIzOcndeOzhX0l16IVNs5ru+5c027aL/KxGFbGnGCz35DqglhheFgwOwerZ
CybEqgR7UhH3dDXOnM1eLC6yHT5MFQpbLcui+pytbEI6x67ANwzAEoYSTGb/g9b0
4EiyO9Y3IXzqO6B1UYmyAAAdUeMsEGs7cxChTu0S6oKf5mHeEDpEuzfZBffcDE2N
tevipf4guGw5lB5s7XzohYwce4wTGm9JKdrlF6BXq0Blw3rbXpdxXK1ABhfprdeA
AlLxcASbF2wsyCaXjrvJqGCez/xvPEdxUUG50FoAjxMCFOtQPWWmhYA0niZrs1bo
qCAM4CMvc10B+Xz4+OPn2uwXdiWgCxIP0PeGQ+60IXGc2h2otZdGmdfkTc9jqCGI
w8WbAeEEOEdw
=yzWR
-END PGP SIGNATURE End Message ---

Bug#935699: marked as done (gdm3: uninstallable on s390x)

[Debian Bug Tracking System]

Your message dated Thu, 29 Aug 2019 10:50:07 +
with message-id 
and subject line Bug#935699: fixed in gdm3 3.30.2-4
has caused the Debian Bug report #935699,
regarding gdm3: uninstallable on s390x
to be marked as done.

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

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


-- 
935699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: gdm3
version: 3.30.2-3
severity: serious

Hi,

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.

Please note that this blocks the s390x binaries from some other packages (like
gnome-panel and gnome-applets) to migrate to testing. This also blocks new
source uploads for the packages depending on libgdm1.

Ivo
--- End Message ---
--- Begin Message ---
Source: gdm3
Source-Version: 3.30.2-4

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 29 Aug 2019 11:08:50 +0100
Source: gdm3
Architecture: source
Version: 3.30.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 935699
Changes:
 gdm3 (3.30.2-4) unstable; urgency=medium
 .
   * Team upload
   * d/gbp.conf: Use debian/unstable, upstream/3.30.x branches
   * Skip building the gdm3 binary package on s390x.
 GDM requires GNOME Shell, which provides its GUI, but GNOME Shell
 is unavailable on s390x.
 Our previous attempt to avoid building an uninstallable gdm3 package
 on s390x involved a spurious build-dependency on gjs, but mozjs60 and
 gjs now work well enough on s390x to pass most of their own tests.
 However, GNOME Shell still fails tests on s390x, and in any case is
 not appropriate for mainframe-class machines that do not normally have
 a GPU or a local display.
 Continuing to build libgdm binaries for s390x, as opposed to forcing the
 entire source package to FTBFS on s390x, means we can continue to build
 gnome-panel without special hacks, allowing s390x users to install the
 GNOME 2-based GNOME Flashback environment if they particularly want a
 GNOME-based desktop on their mainframes. (Closes: #935699)
   * d/control.in: Add versioned Recommends on desktop-base (>= 10.0.0)
 In a previous version this was added to d/control, but d/control is
 regenerated from d/control.in during clean.
   * Remove spurious gjs build-dependency.
 This is less help than we had anticipated in making gdm3 unavailable on
 architectures where gnome-shell is unavailable, because gjs mostly works
 on s390x but gnome-shell does not. It is also desirable to build libgdm
 on even the architectures that do not have a working gdm, so that they
 can use gnome-panel and hence gnome-flashback.
Checksums-Sha1:
 507b366640a942544e653c58a63890815cc47d02 3153 gdm3_3.30.2-4.dsc
 206aba0f277e74fda5341cc88c24a6c5cbb56e4d 92136 gdm3_3.30.2-4.debian.tar.xz
 eb420c5bf1f310cc115c155d2900f705bef52bb4 17388 gdm3_3.30.2-4_source.buildinfo
Checksums-Sha256:
 8f6a007cb8bda2091c38df06738ef0fefb46256f73ac25c7e4256bbb4641bbed 3153 
gdm3_3.30.2-4.dsc
 1b4dd2a009c7c970cff667604d93b0603bc8bb7655dee3bdb9279bedc40afaa3 92136 
gdm3_3.30.2-4.debian.tar.xz
 ae2957b5bff3388b180e27db835c9da61efc585e9361036c4fb747cffa0c5055 17388 
gdm3_3.30.2-4_source.buildinfo
Files:
 6d6e1618238f68b1818e915342726fb3 3153 gnome optional gdm3_3.30.2-4.dsc
 962006e2770ced953c50ec3715ca26e6 92136 gnome optional 
gdm3_3.30.2-4.debian.tar.xz
 2584aff044788531bd0166520231cacf 17388 gnome optional 
gdm3_3.30.2-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl1nqoAQHHNtY3ZAZGVi
aWFuLm9yZwAKCRDgWuFHj4FMT/+YD/9gUx2sgRchY9yOJDQFZ/9zYuAfpNxW1QCj
wUerXX8dpgYYnZipsjQrc5d7OmQVlk4SSBmfFJrpvqKETwMl6y1NO/L8xVnI++Hm

Bug#936014: dovecot: CVE-2019-11500

[Salvatore Bonaccorso]

Hi Apollon,

On Thu, Aug 29, 2019 at 12:55:57PM +0300, Apollon Oikonomopoulos wrote:
> Source: dovecot
> Version: 1:2.3.7.2-1
> 
> Hi,
> 
> This was fixed in unstable in 1:2.3.7.2-1. Closing this manually as I 
> stripped the Closes: tag from d/changelog during a rebase ;)

Thank you!

Regards,
Salvatore

Processed: Bug#935699 marked as pending in gdm3

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #935699 [gdm3] gdm3: uninstallable on s390x
Ignoring request to alter tags of bug #935699 to the same tags previously set

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

Processed: Bug#924548 marked as pending in meta-gnome3

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #924548 [gnome-core] gnome-core: does not actually install a desktop 
environment on s390x
Added tag(s) pending.

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

Bug#935699: marked as pending in gdm3

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #935699 in gdm3 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/gdm/commit/faeef5efcc7ae1334cf4ef5b047d9a4c363826a6


Skip building the gdm3 binary package on s390x

GDM requires GNOME Shell, which provides its GUI, but GNOME Shell
is unavailable on s390x.

Our previous attempt to avoid building an uninstallable gdm3 package
on s390x involved a spurious build-dependency on gjs, but mozjs60 and
gjs now work well enough on s390x to pass most of their own tests.
However, GNOME Shell still fails tests on s390x, and in any case is
not appropriate for mainframe-class machines that do not normally have
a GPU or a local display.

Continuing to build libgdm binaries for s390x, as opposed to forcing the
entire source package to FTBFS on s390x, means we can continue to build
gnome-panel without special hacks, allowing s390x users to install the
GNOME 2-based GNOME Flashback environment if they particularly want a
GNOME-based desktop on their mainframes.

Closes: #935699


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/935699

Bug#924548: marked as pending in meta-gnome3

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #924548 in meta-gnome3 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/meta-gnome3/commit/654f70f5448f57eb69830315a5a1afe60a537134


Reapply "On s390x, install gnome-session-flashback, not gnome-flashback"

This reverts commit dddaeb1f0e2c51062685edccc67f6ca48aa6248f.
gnome-panel is now buildable on s390x, so gnome-session-flashback should
be installable (of course whether it *works* is anyone's guess).

Closes: #924548


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/924548

Bug#936035: xfwm4: fails to load due to missing libxfconf-0.so.2

[Theppitak Karoonboonyanan]

Package: xfwm4
Version: 4.14.0-1
Severity: serious
Justification: Policy 3.5

Dear Maintainer,

xfwm4 fails to start:

$ xfwm4
xfwm4: error while loading shared libraries: libxfconf-0.so.2: cannot
open shared object file: No such file or directory
$ ldd /usr/bin/xfwm4 | grep libxfconf
libxfconf-0.so.3 => /usr/lib/x86_64-linux-gnu/libxfconf-0.so.3
(0x7f74ba2f5000)
libxfconf-0.so.2 => not found
$

Fortunately, installing libxfconf-0-2 does make it load successfully,
but it's not listed as a dependency.

Actually, this bug can be grave (rendering the package unusable)
when libxfconf-0-2 is faded out.

Regards,
-- 
Theppitak Karoonboonyanan
http://linux.thai.net/~thep/

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

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

Versions of packages xfwm4 depends on:
ii  libc6 2.28-10
ii  libcairo2 1.16.0-4
ii  libepoxy0 1.5.3-0.1
ii  libgdk-pixbuf2.0-02.38.1+dfsg-1
ii  libglib2.0-0  2.60.6-2
ii  libgtk-3-03.24.10-1
ii  libpango-1.0-01.42.4-7
ii  libpangocairo-1.0-0   1.42.4-7
ii  libstartup-notification0  0.12-6
ii  libwnck-3-0   3.32.0-1
ii  libx11-6  2:1.6.7-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.5-1
ii  libxext6  2:1.3.3-1+b2
ii  libxfce4ui-2-04.14.1-1+b1
ii  libxfce4util7 4.14.0-1
ii  libxfconf-0-3 4.14.1-1
ii  libxfixes31:5.0.3-1
ii  libxi62:1.7.9-1
ii  libxinerama1  2:1.1.4-2
ii  libxpresent1  1.0.0-2+b10
ii  libxrandr22:1.5.1-1
ii  libxrender1   1:0.9.10-1

Versions of packages xfwm4 recommends:
ii  librsvg2-common  2.44.14-1

Versions of packages xfwm4 suggests:
ii  xfce4  4.14

-- no debconf information

Bug#935699: marked as pending in gdm3

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #935699 in gdm3 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/gdm/commit/faeef5efcc7ae1334cf4ef5b047d9a4c363826a6


Skip building the gdm3 binary package on s390x

GDM requires GNOME Shell, which provides its GUI, but GNOME Shell
is unavailable on s390x.

Our previous attempt to avoid building an uninstallable gdm3 package
on s390x involved a spurious build-dependency on gjs, but mozjs60 and
gjs now work well enough on s390x to pass most of their own tests.
However, GNOME Shell still fails tests on s390x, and in any case is
not appropriate for mainframe-class machines that do not normally have
a GPU or a local display.

Continuing to build libgdm binaries for s390x, as opposed to forcing the
entire source package to FTBFS on s390x, means we can continue to build
gnome-panel without special hacks, allowing s390x users to install the
GNOME 2-based GNOME Flashback environment if they particularly want a
GNOME-based desktop on their mainframes.

Closes: #935699


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/935699

Processed: Bug#935699 marked as pending in gdm3

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #935699 [gdm3] gdm3: uninstallable on s390x
Added tag(s) pending.

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

Bug#936014: marked as done (dovecot: CVE-2019-11500)

[Debian Bug Tracking System]

Your message dated Thu, 29 Aug 2019 12:55:57 +0300
with message-id <20190829095556.ga14...@marvin.dmesg.gr>
and subject line Re: Bug#936014: dovecot: CVE-2019-11500
has caused the Debian Bug report #936014,
regarding dovecot: CVE-2019-11500
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.)


-- 
936014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dovecot
Version: 1:2.3.4.1-5
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 1:2.2.27-3+deb9u4
Control: found -1 1:2.2.27-3
Control: fixed -1 1:2.2.27-3+deb9u5
Control: fixed -1 1:2.3.4.1-5+deb10u1

Hi,

The following vulnerability was published for dovecot.

CVE-2019-11500[0]:
| Nick Roessler and Rafi Rubin discovered that the IMAP and ManageSieve
| protocol parsers in the Dovecot email server do not properly validate
| input (both pre- and post-login). A remote attacker can take advantage
| of this flaw to trigger out of bounds heap memory writes, leading to
| information leaks or potentially the execution of arbitrary code.

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-11500
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11500
[1] https://dovecot.org/pipermail/dovecot-news/2019-August/000418.html

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: dovecot
Version: 1:2.3.7.2-1

Hi,

This was fixed in unstable in 1:2.3.7.2-1. Closing this manually as I 
stripped the Closes: tag from d/changelog during a rebase ;)

Regards,
Apollon


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