Bug#874843: RC bug ignored

[Eduard Bloch]

clone 874843 -1
reassign -1 cdcat
thanks

> As you reassigned the bug to wnpp cdcat lost it's RC bug. Do you mind if I 
> clone it and reassign the clone to cdcat?
>
> We are targetting at removing Qt4 from testing as a first step.

Right, I am sorry. I just applied what you suggested.

Regards, Eduard.

Bug#939813: tasksel: selected packages marked for removal on apt full-upgrade

[Jeremy Turnbull]

Package: tasksel
Version: 3.53
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

The real packages that are installed from the metapackages that tasksel uses
will be marked for automatic removal after the next full system upgrade because
neither the metapackages nor the real packages are marked as being manually
installed to apt, and the metapackages are not listed as dependent packages of
tasksel, which is the only one of these packages that is marked as being
manually installed.

After upgrading from Debian 9.9 to 10.1, I had over 300 packages marked to be
automatically removed. Looking through the list, some of them were what I would
consider as "core" packages to my desktop computing environment, packages like
LibreOffice, Firefox, and XFCE. I used 'apt install' to both mark some of these
packages as being manually installed and to ensure that I was not missing any
new, dependent packages. The problem was, I missed that the network-manager
package was also marked as automatically installed and set to be removed, so
after my next 'apt autoremove' and system reboot, my system had no network
connection and was missing a lot of the packages necessary to create one.

Luckily, I still had a Debian 9.5 installation thumb drive lying around and
was able to boot that into rescue mode and inject the network-manager package
into my root filesystem. However, actions such as this or knowing to scrutinize
the list of packages marked for automatic removal are not behaviors that should
be expected of normal users. The list of packages that automatically will be
removed should not break the system or remove core functionality.

If possible, probably the easiest fix would be to ensure that packages tasksel
marks for installation are also marked as being manually installed to apt.


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

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

Versions of packages tasksel depends on:
ii  apt 1.8.2
ii  debconf [debconf-2.0]   1.5.71
ii  liblocale-gettext-perl  1.07-3+b4
ii  perl-base   5.28.1-6
ii  tasksel-data3.53

tasksel recommends no packages.

tasksel suggests no packages.

-- debconf information:
  tasksel/title:
  tasksel/first: desktop, xfce-desktop, print-server, standard
* tasksel/desktop: xfce
  tasksel/tasks:

Bug#939768: gimp: After the last upgrade, GIMP crashes when creating a new image or opening an existing one.

[Asher Gordon]

Package: gimp
Version: 2.10.8-2+b1
Followup-For: Bug #939768

Hello,

I'm also using testing (bullseye) and I can confirm this bug too.

Here's what I think happened:

GIMP 2.10.8-2 was built on sid (which had GEGL 0.4.12 at the
time). Testing also had GEGL 0.4.12, so there was no version mismatch
and everything was fine. Then, GIMP 2.10.8-2+b1 was built on sid, which
now has GEGL 0.4.14. When GIMP 2.10.8-2+b1 (now built against GEGL
0.4.14) migrated to testing (which still has GEGL 0.4.12), the version
mismatch occurred causing the GIMP to crash.

Note that I am just guessing the versions of packages that sid and
testing had in the past, so it should be taken with a grain of salt.

If this is the case, there appears to be three obvious fixes:

1. Migrate GEGL 0.4.14 to testing.
2. Revert the testing GIMP package to 2.10.8-2.
3. Build the testing GIMP package against GEGL 0.4.12.

Since GEGL is 188 days old and should be migrated anyway, 1. seems to be
preferable. Looking at the package tracker [1], it appears that there
are some migration issues that need to be looked at, so perhaps 2. could
be a temporary fix. I'm not sure how 3. would be implemented, since the
sid GIMP package would still need to be built against GEGL 0.4.14.

In the future, care should be taken to avoid GEGL mismatches like this.

By the way, #939754 looks like the same bug.

Hope this helps,
Asher

P.S. I am neither a GIMP developer nor a Debian developer, just an
affected user trying to help.


[1] https://tracker.debian.org/pkg/gegl

-- 
By necessity, by proclivity, and by delight, we all quote.  In fact, it is as
difficult to appropriate the thoughts of others as it is to invent.
-- R. Emerson
-- Quoted from a fortune cookie program
(whose author claims, "Actually, stealing IS easier.")
[to which I reply, "You think it's easy for me to
misconstrue all these misquotations?!?"  Ed.]

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

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

Versions of packages gimp depends on:
ii  gimp-data2.10.8-2
ii  libaa1   1.4p5-46+b1
ii  libbabl-0.1-00.1.62-1
ii  libbz2-1.0   1.0.6-9.2
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libfontconfig1   2.13.1-2+b1
ii  libfreetype6 2.9.1-4
ii  libgcc1  1:9.2.1-4
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libgegl-0.4-00.4.12-2
ii  libgexiv2-2  0.10.9-1
ii  libgimp2.0   2.10.8-2+b1
ii  libglib2.0-0 2.60.6-2
ii  libgs9   9.27~dfsg-3.1
ii  libgtk2.0-0  2.24.32-3
ii  libgudev-1.0-0   232-2
ii  libharfbuzz0b2.6.1-2
ii  libheif1 1.5.1-1
ii  libilmbase24 2.3.0-6
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-3+b1
ii  liblzma5 5.2.4-1+b1
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.3-0 1.3.0-2.1+b1
ii  libopenexr24 2.3.0-6
ii  libopenjp2-7 2.3.0-2
ii  libpango-1.0-0   1.42.4-7
ii  libpangocairo-1.0-0  1.42.4-7
ii  libpangoft2-1.0-01.42.4-7
ii  libpng16-16  1.6.37-1
ii  libpoppler-glib8 0.71.0-5+b1
ii  librsvg2-2   2.44.14-1
ii  libstdc++6   9.2.1-4
ii  libtiff5 4.0.10+git190818-1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libwmf0.2-7  0.2.8.4-14
ii  libx11-6 2:1.6.7-1
ii  libxcursor1  1:1.2.0-2
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxmu6  2:1.1.2-2+b3
ii  libxpm4  1:3.5.12-1
ii  xdg-utils1.1.3-1
ii  zlib1g   1:1.2.11.dfsg-1+b1

Versions of packages gimp recommends:
ii  ghostscript  9.27~dfsg-3.1

Versions of packages gimp suggests:
pn  gimp-data-extras  
ii  gimp-help-en [gimp-help]  2.8.2-1
pn  gimp-python   
ii  gvfs-backends 1.38.1-5
ii  libasound21.1.8-1

-- no debconf information


signature.asc
Description: PGP signature

Bug#936552: marked as done (freecad: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 09 Sep 2019 01:04:54 +
with message-id 
and subject line Bug#936552: fixed in freecad 0.18.3+dfsg1-2
has caused the Debian Bug report #936552,
regarding freecad: Python2 removal in sid/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.)


-- 
936552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:freecad
Version: 0.18.3+dfsg1-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:freecad

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: freecad
Source-Version: 0.18.3+dfsg1-2

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

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

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

Debian distribution maintenance software
pp.
Kurt Kremitzki  (supplier of updated freecad package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 08 Sep 2019 17:35:08 -0500
Source: freecad
Architecture: source
Version: 0.18.3+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Kurt Kremitzki 
Closes: 936552
Changes:
 freecad (0.18.3+dfsg1-2) unstable; urgency=medium
 .
   * [898fd80] Migrate to Python 3 only, Netgen-enabled build (Closes:
 #936552)
   * [2c077ab] Bump compat level to 12
   * [276a12e] Bump Standards-Version to 4.4.0 (no changes needed)
Checksums-Sha1:
 6ef2cb69c2bda7affd5ef3ba7b8bdda4da690ae4 3360 freecad_0.18.3+dfsg1-2.dsc
 993ae09f010f9b31aa3c475e353ad6be0696bb23 29952 
freecad_0.18.3+dfsg1-2.debian.tar.xz
 03422face816d15860bf1aa9d5228b8344f7e696 30165 
freecad_0.18.3+dfsg1-2_source.buildinfo
Checksums-Sha256:
 cec09875e450abd28574372536a978c0961558878441eb65f76c2bd573df2c00 3360 
freecad_0.18.3+dfsg1-2.dsc
 e886af322ba0dbfd2a81e90e1549555a13f83a1a22e49e7fb229a958e1ddea89 29952 
freecad_0.18.3+dfsg1-2.debian.tar.xz
 

Bug#939807: sbcl build-depends on package that is cruft in unstable and gone in testing.

[peter green]

Package: sbcl
Version: 2:1.5.6-1
Severity: serious

sbcl build-depends on texlive-generic-recommended which is no longer built by 
texlive-base. The old texlive-generic-recommended is still present in unstable 
as a cruft package, but is completely gone from testing.

Please update your build-dependency to texlive-plain-generic.

Bug#939768: gimp: After the last upgrade, GIMP crashes when creating a new image or opening an existing one.

[japers]

Package: gimp
Version: 2.10.8-2+b1
Followup-For: Bug #939768

Dear Maintainer,

   * What led up to the situation?
Any attempt to open or create an image file results in segmentation
fault and exit from the software.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
No attempt to open any kind of image on my system resulted in anything
but segmentation fault and exit from the software.




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

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.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 gimp depends on:
ii  gimp-data2.10.8-2
ii  libaa1   1.4p5-46+b1
ii  libbabl-0.1-00.1.62-1
ii  libbz2-1.0   1.0.6-9.2
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libfontconfig1   2.13.1-2+b1
ii  libfreetype6 2.9.1-4
ii  libgcc1  1:9.2.1-4
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libgegl-0.4-00.4.12-2
ii  libgexiv2-2  0.10.9-1
ii  libgimp2.0   2.10.8-2+b1
ii  libglib2.0-0 2.60.6-2
ii  libgs9   9.27~dfsg-3.1
ii  libgtk2.0-0  2.24.32-3
ii  libgudev-1.0-0   232-2
ii  libharfbuzz0b2.6.1-2
ii  libheif1 1.5.1-1
ii  libilmbase24 2.3.0-6
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-3+b1
ii  liblzma5 5.2.4-1+b1
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.3-0 1.3.0-2.1+b1
ii  libopenexr24 2.3.0-6
ii  libopenjp2-7 2.3.0-2
ii  libpango-1.0-0   1.42.4-7
ii  libpangocairo-1.0-0  1.42.4-7
ii  libpangoft2-1.0-01.42.4-7
ii  libpng16-16  1.6.37-1
ii  libpoppler-glib8 0.71.0-5+b1
ii  librsvg2-2   2.44.14-1
ii  libstdc++6   9.2.1-4
ii  libtiff5 4.0.10+git190818-1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libwmf0.2-7  0.2.8.4-14
ii  libx11-6 2:1.6.7-1
ii  libxcursor1  1:1.2.0-2
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxmu6  2:1.1.2-2+b3
ii  libxpm4  1:3.5.12-1
ii  xdg-utils1.1.3-1
ii  zlib1g   1:1.2.11.dfsg-1+b1

Versions of packages gimp recommends:
ii  ghostscript  9.27~dfsg-3.1

Versions of packages gimp suggests:
ii  gimp-data-extras  1:2.0.2-1
ii  gimp-help-en [gimp-help]  2.8.2-1
ii  gimp-python   2.10.8-2+b1
ii  gvfs-backends 1.38.1-5
ii  libasound21.1.8-1

-- no debconf information

Bug#935578: [Pkg-rust-maintainers] Bug#935578: bat: bacula-console-qt already ships /usr/sbin/bat (and /usr/share/man/man1/bat.1.gz)

[Paride Legovini]

Andreas Beckmann wrote on 24/08/2019:
> Package: bat
> Version: 0.11.0-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package failed to install
> because it tries to overwrite other packages files.
> 
> Since /usr/sbin/bat is already provided by another package, you can't
> ship a different binary as /usr/bin/bat.
> I noticed this by the clash on the manpage.
> 
> From the attached log (scroll to the bottom...):
> 
>   Selecting previously unselected package bat.
>   Preparing to unpack .../11-bat_0.11.0-2_amd64.deb ...
>   Unpacking bat (0.11.0-2) ...
>   dpkg: error processing archive 
> /tmp/apt-dpkg-install-xqEwrF/11-bat_0.11.0-2_amd64.deb (--unpack):
>trying to overwrite '/usr/share/man/man1/bat.1.gz', which is also in 
> package bacula-console-qt 9.4.4-2+b1
>   Errors were encountered while processing:
>/tmp/apt-dpkg-install-xqEwrF/11-bat_0.11.0-2_amd64.deb

:(

Thanks Andreas for the heads-up, I missed this name clash. I knew tat
the 'bat' binary name and manpage were taken by the bareos-bat package
up to Buster. That package has now been dropped, and I happily packaged
'bat' without renames, as I didn't know that bacula-console-qt was
installing those files too; bareos-bat had a Conflits/Replaces on
bacula-console-qt, so there was no name clash in that case.

I guess I'll have to rename some files here. This isn't obvious at the
moment as the build dependencies for rust-bat are not satisfied in unstable.

Paride

Bug#939740: marked as done (libwxgtk3.0-gtk3-0v5: -10 is not compatible with -9 [symbol _ZNK8wxWindow21GetContentScaleFactorEv version WXU_3.0 not defined in file libwx_gtk3u_core-3.0.so.0 with link t

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 22:29:41 +
with message-id 
and subject line Bug#939740: fixed in wxwidgets3.0 3.0.4+dfsg-11
has caused the Debian Bug report #939740,
regarding libwxgtk3.0-gtk3-0v5: -10 is not compatible with -9 [symbol 
_ZNK8wxWindow21GetContentScaleFactorEv version WXU_3.0 not defined in file 
libwx_gtk3u_core-3.0.so.0 with link time reference]
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.)


-- 
939740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwxgtk3.0-gtk3-0v5
Version: 3.0.4+dfsg-10
Severity: serious

Rebuilding hugin on current sid with libwxgtk 3.0.4+dfsg-10 creates a
package that according to its dependencies [libwxgtk3.0-gtk3-0v5 (>=
3.0.4+dfsg)] is installable on testing but fails to run there (with
libwxgtk3.0-gtk3-0v5:amd64 3.0.4+dfsg-9).

ametzler@argenau:/tmp/HUGIN$ ldd -r /usr/bin/hugin > /dev/null
symbol _ZNK8wxWindow21GetContentScaleFactorEv version WXU_3.0 not defined in 
file libwx_gtk3u_core-3.0.so.0 with link time reference
(/usr/lib/hugin/libhuginbasewx.so.0.0)
symbol _ZNK8wxWindow21GetContentScaleFactorEv version WXU_3.0 not defined in 
file libwx_gtk3u_core-3.0.so.0 with link time reference
(/usr/lib/hugin/libicpfindlib.so.0.0)
symbol _ZNK8wxWindow21GetContentScaleFactorEv version WXU_3.0 not defined in 
file libwx_gtk3u_core-3.0.so.0 with link time reference(/usr/bin/hugin)

cu Andreas
--- End Message ---
--- Begin Message ---
Source: wxwidgets3.0
Source-Version: 3.0.4+dfsg-11

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

Debian distribution maintenance software
pp.
Olly Betts  (supplier of updated wxwidgets3.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 09 Sep 2019 08:19:11 +1200
Source: wxwidgets3.0
Architecture: source
Version: 3.0.4+dfsg-11
Distribution: unstable
Urgency: medium
Maintainer: wxWidgets Maintainers 
Changed-By: Olly Betts 
Closes: 939740
Changes:
 wxwidgets3.0 (3.0.4+dfsg-11) unstable; urgency=medium
 .
   * debian/patches/upstream-changes-since-3.0.4.patch: Add lost entry for
 new wxWindow::GetContentScaleFactor() function. (Closes: #939740)
Checksums-Sha1:
 f7d01bbfdbb07f9fe77f6f7b1d31c595c8d1e9fd 3499 wxwidgets3.0_3.0.4+dfsg-11.dsc
 76ff30140a84180804ab7dd09e40dab0b67b817b 67784 
wxwidgets3.0_3.0.4+dfsg-11.debian.tar.xz
 d5a6ea97fa1fd665d08e7a37098bb302dd2654a8 24032 
wxwidgets3.0_3.0.4+dfsg-11_amd64.buildinfo
Checksums-Sha256:
 9584f191d1d7423f5ca42bafcfa3159bd19cda722c0109a995402605d1d92896 3499 
wxwidgets3.0_3.0.4+dfsg-11.dsc
 13eabd6e4123c26ab87413f94c5709bc5d35d5977f24bc2680221b610e00e216 67784 
wxwidgets3.0_3.0.4+dfsg-11.debian.tar.xz
 41924b964a5ce1fd4962b53097b7f426cc19edaa80719ff786554923977b07ae 24032 
wxwidgets3.0_3.0.4+dfsg-11_amd64.buildinfo
Files:
 005f4c4c8259b0de7f5f9264f0b3b278 3499 libs optional 
wxwidgets3.0_3.0.4+dfsg-11.dsc
 8103a71baaca534859ac7c45ececaf29 67784 libs optional 
wxwidgets3.0_3.0.4+dfsg-11.debian.tar.xz
 70dcd605ebb30d4538e0d7ff545c38ae 24032 libs optional 
wxwidgets3.0_3.0.4+dfsg-11_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEECOJAD/f+j+3jrLUoGBR7BzutKwcFAl11ceUACgkQGBR7Bzut
KwdjmQ//cVifhXdul5DAf7OKYPLO3orUGduWoLiiDyt0s1AFuuG2okHuW00SuUky
owqCMV2k6+9hqUMBWTpiaDf220aFdu7L1NmpXy0Wt2Jb+D/tWtfbMPLrIaLY+SFZ
3eYELb8gMz8ZeJdkm5Zj/pQk1Wsj7RdbshkeHfDxjykG5yApk8mFUWAW3on0R6jF
dcCV2nugqIy49YHzjaGVAPsDZI3kQIp4lCB38g1D9x2QavYittG+taGUqbUqHsoB
+lruhniLb4JxAr41ft8EcRdslZBg3QyeT/X7sAGmhwVVsh0uqE+AfqoEERAJ43ct
QLrii3IuaVhs31bKlYGXi0rylfYNEs8v1dp+El9IceYugaJBAyhSosFnPGjsmMSa
qXhKfu2nkf1VsM0H4xAS2a1e/3xSqxwYb6gNaKOvX29uWNH1AwNtpR4YC/e3ffov
CQQy/ump4ohh5mMfc5CdBD/bFFLRhyQx7IFEDS+u6+/rI4GV/5Hy7cLDBdGEx+ic
BeYuyN3gHLDiMYwJp80Zvv5ophrPeFlaidpXzbeu841BzMPrBttV2NHDUBO36FCT
yiecMVumvFXi8rl7uJaVxbrwIlNCCdHfxGdHBWBSG1kJfPftIBRuhMdR8/J1WtKD
eNCFXD8RUzFm9BrRWkhmEjEgc2Q6n9DkNiVnbawu8ppANJ5p5gQ=
=pfc4
-END PGP SIGNATURE End Message ---

Bug#930774: buster-pu: package guile-2.2/2.2.4+1-2

[Rob Browning]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

This should fix the FTBFS that's already been fixed in sid.

diff -Nru guile-2.2-2.2.4+1/debian/changelog guile-2.2-2.2.4+1/debian/changelog
--- guile-2.2-2.2.4+1/debian/changelog	2019-06-02 11:17:15.0 -0500
+++ guile-2.2-2.2.4+1/debian/changelog	2019-09-08 15:22:44.0 -0500
@@ -1,3 +1,10 @@
+guile-2.2 (2.2.4+1-2+deb10u1) buster; urgency=medium
+
+  * Switch to dh_missing and ignore guile-X.Y for binary-indep.  Thanks to
+Santiago Vila for reporting the problem. (Closes: 930774)
+
+ -- Rob Browning   Sun, 08 Sep 2019 15:22:44 -0500
+
 guile-2.2 (2.2.4+1-2) unstable; urgency=medium
 
   * Backport upstream fix for after-gc-hook test failures.  Replace
diff -Nru guile-2.2-2.2.4+1/debian/rules guile-2.2-2.2.4+1/debian/rules
--- guile-2.2-2.2.4+1/debian/rules	2019-06-02 11:17:15.0 -0500
+++ guile-2.2-2.2.4+1/debian/rules	2019-09-08 15:22:01.0 -0500
@@ -231,7 +231,8 @@
 
 override_dh_install-arch: $(autogen_install_files)
 	cd debian/tmp/usr/bin && mv -i guile-$(deb_src_eff_ver) guile
-	dh_install -a --fail-missing \
+	dh_install -a
+	dh_missing -a --fail-missing \
 	  -Xusr/lib/$(march)guile/$(deb_src_eff_ver)/extensions/guile-readline.a \
 	  -Xusr/lib/$(march)guile/$(deb_src_eff_ver)/extensions/guile-readline.la
 	test -e $(gdb_ext)
@@ -242,7 +243,9 @@
 # Glob should match the one in debian/guile-doc.install
 	test "$(sort $(expected_info))" = \
 	  "$(sort $(shell cd debian/tmp/usr/share/info && ls guile.info*))"
-	dh_install -i --fail-missing \
+	dh_install -i
+	dh_missing -i --fail-missing \
+	  -Xusr/bin/guile-$(deb_src_eff_ver) \
 	  -Xusr/share/info/dir \
 	  -Xusr/share/info/r5rs.info \
 	  -Xusr/lib/$(march)guile/$(deb_src_eff_ver)/extensions/guile-readline.a \

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#939801: xtables-addons-source: xtables-addons-2.12.0 fails to compile (kernel 5.2.0-0.bpo.2-amd64)

[Olaf Martens]

Package: xtables-addons-source
Version: 2.12-0.1
Severity: serious
Justification: Policy 4.15

Dear maintainer,

whenever attempting to compile xtables-addons-dkms, the following occurs
reproducibly:

root@h2182426:/var/lib/dkms/xtables-addons/2.12/build# make
make  all-recursive
make[1]: Verzeichnis „/var/lib/dkms/xtables-addons/2.12/build“ wird betreten
Making all in extensions
make[2]: Verzeichnis „/var/lib/dkms/xtables-addons/2.12/build/extensions“ wird 
betreten
Xtables-addons 2.12 - Linux 5.2.9
if [ -n "/lib/modules/5.2.0-0.bpo.2-amd64/build" ]; then make -C 
/lib/modules/5.2.0-0.bpo.2-amd64/build 
M=/var/lib/dkms/xtables-addons/2.12/build/extensions modules; fi;
make[3]: Verzeichnis „/usr/src/linux-headers-5.2.0-0.bpo.2-amd64“ wird betreten
  CC [M]  /var/lib/dkms/xtables-addons/2.12/build/extensions/pknock/xt_pknock.o
/var/lib/dkms/xtables-addons/2.12/build/extensions/pknock/xt_pknock.c: In 
function ‘add_rule’:
/var/lib/dkms/xtables-addons/2.12/build/extensions/pknock/xt_pknock.c:472:2: 
error: implicit declaration of function ‘init_timer’; did you mean 
‘init_timers’? [-Werror=implicit-function-declaration]
  init_timer(&rule->timer);
  ^~
  init_timers
/var/lib/dkms/xtables-addons/2.12/build/extensions/pknock/xt_pknock.c:473:23: 
error: assignment to ‘void (*)(struct timer_list *)’ from incompatible pointer 
type ‘void (*)(long unsigned int)’ [-Werror=incompatible-pointer-types]
  rule->timer.function = peer_gc;
   ^
/var/lib/dkms/xtables-addons/2.12/build/extensions/pknock/xt_pknock.c:474:13: 
error: ‘struct timer_list’ has no member named ‘data’
  rule->timer.data = (unsigned long)rule;
 ^
/var/lib/dkms/xtables-addons/2.12/build/extensions/pknock/xt_pknock.c: In 
function ‘xt_pknock_mt_init’:
/var/lib/dkms/xtables-addons/2.12/build/extensions/pknock/xt_pknock.c:1138:13: 
error: ‘struct shash_desc’ has no member named ‘flags’
  crypto.desc.flags = 0;
 ^
cc1: some warnings being treated as errors
make[7]: *** 
[/usr/src/linux-headers-5.2.0-0.bpo.2-common/scripts/Makefile.build:290: 
/var/lib/dkms/xtables-addons/2.12/build/extensions/pknock/xt_pknock.o] Fehler 1
make[6]: *** 
[/usr/src/linux-headers-5.2.0-0.bpo.2-common/scripts/Makefile.build:494: 
/var/lib/dkms/xtables-addons/2.12/build/extensions/pknock] Fehler 2
make[5]: *** [/usr/src/linux-headers-5.2.0-0.bpo.2-common/Makefile:1610: 
_module_/var/lib/dkms/xtables-addons/2.12/build/extensions] Fehler 2
make[4]: *** [Makefile:179: sub-make] Fehler 2
make[3]: *** [Makefile:8: all] Fehler 2
make[3]: Verzeichnis „/usr/src/linux-headers-5.2.0-0.bpo.2-amd64“ wird verlassen
make[2]: *** [Makefile:463: modules] Fehler 2
make[2]: Verzeichnis „/var/lib/dkms/xtables-addons/2.12/build/extensions“ wird 
verlassen
make[1]: *** [Makefile:496: all-recursive] Fehler 1
make[1]: Verzeichnis „/var/lib/dkms/xtables-addons/2.12/build“ wird verlassen
make: *** [Makefile:381: all] Fehler 2

Kind regards,

Olaf Martens

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

Kernel: Linux 5.2.0-0.bpo.2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.utf8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) (ignored: LC_ALL set to 
de_DE.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: default

Versions of packages xtables-addons-source depends on:
ii  bzip2 1.0.6-9.2~deb10u1
ii  debhelper 12.1.1
ii  iptables-dev  1.8.3-2~bpo10+1
ii  make  4.2.1-1.2
ii  pkg-config0.29-6

Versions of packages xtables-addons-source recommends:
ii  module-assistant  0.11.10

xtables-addons-source suggests no packages.

-- no debconf information

Bug#939420: marked as done (stdx-allocator: FTBFS, test failures.)

[Debian Bug Tracking System]

Your message dated Sun, 8 Sep 2019 23:19:27 +0200
with message-id 

and subject line Re: Bug#939420: stdx-allocator: FTBFS, test failures.
has caused the Debian Bug report #939420,
regarding stdx-allocator: FTBFS, test failures.
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.)


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

Package: stdx-allocator
Version: 3.0.1-2
Tags: bullseye, sid

stdx-allocator failed to build when binnmu'd for the ldc transition.


dh_auto_test -a
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test
[0/1] Running all tests.
1/1 stdx-allocator-test FAIL 0.12 s (exit status 1)

Ok:0
Expected Fail: 0
Fail:  1
Unexpected Pass:   0
Skipped:   0
Timeout:   0


The output from the failed tests:

1/1 stdx-allocator-test FAIL 0.12 s (exit status 1)

--- command ---
/<>/obj-x86_64-linux-gnu/stdx-allocator-test
--- stderr ---
core.exception.AssertError@../source/stdx/allocator/gc_allocator.d(161): 
Assertion failure

??:? _d_assert [0x7fd6ea38763c]
gc_allocator.d:161 [0x55b4ecb75f74]
gc_allocator.d:0 [0x55b4ecb75fb5]
??:? int core.runtime.runModuleUnitTests().__foreachbody2(object.ModuleInfo*) 
[0x7fd6ea38e13b]
??:? int rt.minfo.moduleinfos_apply(scope int 
delegate(immutable(object.ModuleInfo*))).__foreachbody2(ref 
rt.sections_elf_shared.DSO) [0x7fd6ea3bada1]
??:? int rt.sections_elf_shared.DSO.opApply(scope int delegate(ref 
rt.sections_elf_shared.DSO)) [0x7fd6ea3bc109]
??:? int rt.minfo.moduleinfos_apply(scope int 
delegate(immutable(object.ModuleInfo*))) [0x7fd6ea3bad4b]
??:? int object.ModuleInfo.opApply(scope int delegate(object.ModuleInfo*)) 
[0x7fd6ea3a501e]
??:? runModuleUnitTests [0x7fd6ea38df54]
??:? void rt.dmain2._d_run_main(int, char**, extern (C) int 
function(char[][])*).runAll() [0x7fd6ea3b18ca]
??:? _d_run_main [0x7fd6ea3b1717]
??:? __libc_start_main [0x7fd6ea11e09a]
??:? [0x55b4ecb102b9]
1/22 unittests FAILED
---

Full log written to /<>/obj-x86_64-linux-gnu/meson-logs/testlog.txt
--- End Message ---
--- Begin Message ---
Am Mi., 4. Sept. 2019 um 21:24 Uhr schrieb Peter Michael Green
:
>
> Package: stdx-allocator
> Version: 3.0.1-2
> Tags: bullseye, sid
>
> stdx-allocator failed to build when binnmu'd for the ldc transition.
>
> > dh_auto_test -a
> >   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja 
> > test
> > [0/1] Running all tests.
> > 1/1 stdx-allocator-test FAIL 0.12 s (exit status 1)
> >
> > Ok:0
> > Expected Fail: 0
> > Fail:  1
> > Unexpected Pass:   0
> > Skipped:   0
> > Timeout:   0
> >
> > [...]

This is fixed in version 3.1.0~beta.2-1 now, thank you for reporting the issue!

Cheers,
Matthias

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

Bug#939800: librtlsdr-dev: Incomplete pkg-config file

[Jonas Eymann]

Package: librtlsdr-dev
Version: 0.6-1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)

Hello Maitland,

while trying to build tfrec (https://github.com/baycom/tfrec) I came across the
problem that pkg-config does not provide the correct linker flags for
librtlsdr:

~$ pkg-config --libs librtlsdr
-L -lrtlsdr

(empty path after -L). Looking at librtlsdr.pc shows that the first four lines
do not have any values defined:

prefix=
exec_prefix=
libdir=
includedir=

Name: RTL-SDR Library
Description: C Utility Library
Version: 0.6.0
Cflags: -I${includedir}/
Libs: -L${libdir} -lrtlsdr
Libs.private:  -lusb-1.0

To me, the upstream librtlsdr.pc.in seems to look fine, so it might a problem
introduced during packaging, but I'm not an expert on pkg-config...

Best regards,
Jonas



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

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

Versions of packages librtlsdr-dev depends on:
ii  librtlsdr00.6-1
ii  libusb-1.0-0-dev  2:1.0.22-2

librtlsdr-dev recommends no packages.

librtlsdr-dev suggests no packages.

-- no debconf information

Bug#875070: marked as done ([opencsg] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 21:04:44 +
with message-id 
and subject line Bug#875070: fixed in opencsg 1.4.2-2
has caused the Debian Bug report #875070,
regarding [opencsg] 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.)


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

[announced] 


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

[OpenSSL 1.1 support] 

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

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

= Porting =

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

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

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

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

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

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: opencsg
Source-Version: 1.4.2-2

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

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

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

Debian distribution maintenance software
pp.
Kristian Nielsen  (supplier of updated opencsg 
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: Wed, 04 Sep 2019 20:14:28 +0200
Source: opencsg
Architecture: source
Version: 1.4.2-2
Distribution: unstable
Urgency: medium
Maintainer: John Paul Adrian Glaubitz 
Changed-By: Kristian Nielsen 
Closes: 875070
Changes:
 opencsg (1.4.2-2) unstable; urgency=medium
 .
   * Switch from qt4-qmake to qt5-qmake dependency (Closes: #875070)
Checksums-Sha1:
 046cdf8035687ad2fbe0eff2dc805b0da4a43983 2160 opencsg_1.4.2-2.dsc
 c73dca0912f05918de06fcfd0eded3f72237b6ec 7748 opencsg_1.4.2-2.debian.tar.xz
 ffe09b948b6a6e639807918092ed20928aa5bddb 11232 opencsg_1.4.2-2_amd64.buildinfo
Checksums-Sha256:
 c84032be50182156648ee45f4ae76db72d262d30cb94e31df5f1fc8dc8119b1a 2160 
opencsg_1.4.2-2.dsc
 85bb1ea7fd8ed43251e3ebd48e6402756cb5ad0587792810ca884fcdc64d6144 7748 
opencsg_1.4.2-2.debian.tar.xz
 2c962c51de943cb87aa8d9db686cba411acb110bf955072203a8648b4e0ff38a 11232 
opencsg_1.4.2-2_amd64.buildinfo
Files:
 d96adbefe331e2da8366bf98e6c58e96 2160 libs optional opencsg_1.4.2-2.dsc
 3723b4605beff32d45d7c5108bb59848 7748 libs optional 
opencsg_1.4.2-2.debian.tar.xz
 552f845739cf6f39ae47bb7c7acd29e8 11232 libs optional 
opencsg_1.4.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAl11ZL0ACgkQdCY7N/W1
+RNa9w//XGQLD1BoOXcRQMGzQLfKntINQ8WgMIF40N6oQ2HN9dk6r113N0AD4sUF
9RPL2FYGSjTmdw0UPu7RgDZEaMfyaywh0P4oH/9vUDjkuye8mJcaeIvgOEd2VLiS
1FUVHxl3QkUiidM1afJpbzlrsf/YCHMiwzfyx4X88XhMZk/7d+rFqgXddWYgUjFs
SUxAWP2JFTov

Bug#939375: marked as done (dub depends on unavailable default-d-compiler)

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 21:03:59 +
with message-id 
and subject line Bug#939375: fixed in dh-dlang 0.6.3
has caused the Debian Bug report #939375,
regarding dub depends on unavailable default-d-compiler
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.)


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

Package: dub
Version: 1.16.0-1
Severity: serious
Tags: sid bullseye

dub depends on the unavailable package default-d-compiler. Maybe that one should 
be built from the dh-dlang source. If you touch that package, please add the 
package for all the mips* targets as well, now built by gcc-9/gdc-9.
--- End Message ---
--- Begin Message ---
Source: dh-dlang
Source-Version: 0.6.3

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

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated dh-dlang package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 08 Sep 2019 22:46:42 +0200
Source: dh-dlang
Architecture: source
Version: 0.6.3
Distribution: unstable
Urgency: medium
Maintainer: Debian D Language Group 
Changed-By: Matthias Klumpp 
Closes: 939375
Changes:
 dh-dlang (0.6.3) unstable; urgency=medium
 .
   * Bump standards version: No changes needed
   * Update list of default compilers for
 supported architectures (Closes: #939375)
Checksums-Sha1:
 63045e686026bb35504069ad488914da45ff16de 1759 dh-dlang_0.6.3.dsc
 ebc1e40cb5e45636a6f62fd9ecc6f06aa24384c2 4084 dh-dlang_0.6.3.tar.xz
 992d2de606883958f4ba1227471948d648f24416 6837 dh-dlang_0.6.3_source.buildinfo
Checksums-Sha256:
 792baaf833e2d0ef0a147e475a3139034bdca3114f8493382ddf14f43e91a9d4 1759 
dh-dlang_0.6.3.dsc
 534591ca9442babc6ddf340c42b3d9e2f06860571f10202d63e5bc57d6fb61ed 4084 
dh-dlang_0.6.3.tar.xz
 94b33edb79a0c350234af1f866f72d7bd70baa956580a7fc9542f030f24bbb5e 6837 
dh-dlang_0.6.3_source.buildinfo
Files:
 98bec365fa497bd61e83ca20b4a83366 1759 devel optional dh-dlang_0.6.3.dsc
 cac1dfedd46d0ddc1f78e2c3ec453168 4084 devel optional dh-dlang_0.6.3.tar.xz
 d8a8b68764a61e0655cb9eb369d892ed 6837 devel optional 
dh-dlang_0.6.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEE0zo/DKFrCsxRpgc4SUyKX79N7OsFAl11afcPHG1ha0BkZWJp
YW4ub3JnAAoJEElMil+/TezrEyIQAJiO7yJrPQkBc8yudn0J+8h+xYWCBO6RqQLF
YvKmGKmxEmQhpGy6sQ2BLohvsN50HDoGKTRgchcNC+bwNlkCJTrouidWUFJYdUr1
bMQh1iGY9QxEzPWddfaettiSadDUclUr8iZHbiOyl3CLViu4KB/hUUwP6GsSsvoe
S1jQYN8teTBlq6p5Sj07/yKfGLhQL3omp4/R9zYEsJUJXRkUQJzDiQibdgNd18/T
klnIFRFevotxXauLtOiX5SeMYN+gmsM2EBShu2vw3xwsJd3gvRxcG1WRAYF6bD9t
fWlM0WLAnWBAeTib6hwKtujUUnSUy8PE8Nm/DfoIY4uUE0T3pgyrW1GWrAJZDslN
Idv9UxrLE8zG12acC4b6RQOd+CqnO7EI065DaoMZ/XA5th8iQfjfmdAtZ1Zxa6Xb
knshlP26Bfv2E8khHhFsTGl4teg+T466RlZscI/pDtS5PkqjSKqOc2ZOvHajwm2H
hMjaY6iJsxTy/CIEiJhcuUrsjdgZIVHqW7Awwdkt2Zn7K7stdO5amhYpF5vBSBhi
UVvp582b8Rl2I1Z6uaVj6Mk8hTdw2Bewpd/Jei7Xhl8Zx/3wqrqBDLxvrGZScyBy
qFXFSGhqDFbe1SYGiXKtsji6OFh/0ubwukYKNtma3/xUZJtEtp1C3lb3UwTVpOfQ
bYJ5KwEg
=F5zw
-END PGP SIGNATURE End Message ---

Bug#875184: [sofa-framework] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Sun, Sep 08, 2019 at 08:41:40AM +0200, Andreas Tille wrote:
> On Sat, Sep 07, 2019 at 10:43:53PM +0200, Moritz Mühlenhoff wrote:
> > 
> > The current releases on https://github.com/sofa-framework claim to be Qt5
> > compatible. Is anyone working on updating the package or should it be 
> > removed?
> > 
> > sofa-framework is one of the three remaining reverse dependencies of
> > libqwt5-qt4-dev at this point.
> 
> I tried to upgrade sofa-framework but had severe issues with new cmake
> configuration.  I'll have a look next week.

If you're stuck, feel free to ping #debian-qt-kde.

Cheers,
Moritz

Bug#939375: dub depends on unavailable default-d-compiler

[Matthias Klumpp]

Hi!

Am Mi., 4. Sept. 2019 um 11:17 Uhr schrieb Matthias Klose :
>
> Package: dub
> Version: 1.16.0-1
> Severity: serious
> Tags: sid bullseye
>
> dub depends on the unavailable package default-d-compiler. Maybe that one 
> should
> be built from the dh-dlang source. If you touch that package, please add the
> package for all the mips* targets as well, now built by gcc-9/gdc-9.

I add the respective architectures to the default-d-compiler
metapackage dependent on whether there is a working D compiler on the
respective architecture. "Working" in this case means "can build and
run dub". This is the case for risc64 now, surprisingly, but
unfortunately not yet for mips*, apparently builds on that
architecture succeed, but running the simple manual page generator
fails with a segmentation fault.
Once that issue is fixed, I'll add mips* as well.
As for the other architectures, with the latest dh-dlang upload dub
should be installable on all architectures where it actually builds.

Cheers,
Matthias

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

Processed: Re: Bug#939740: libwxgtk3.0-gtk3-0v5: -10 is not compatible with -9 [symbol _ZNK8wxWindow21GetContentScaleFactorEv version WXU_3.0 not defined in file libwx_gtk3u_core-3.0.so.0 with link ti

[Debian Bug Tracking System]

Processing control commands:

> tag -1 +pending
Bug #939740 [libwxgtk3.0-gtk3-0v5] libwxgtk3.0-gtk3-0v5: -10 is not compatible 
with -9 [symbol _ZNK8wxWindow21GetContentScaleFactorEv version WXU_3.0 not 
defined in file libwx_gtk3u_core-3.0.so.0 with link time reference]
Added tag(s) pending.

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

Bug#939740: libwxgtk3.0-gtk3-0v5: -10 is not compatible with -9 [symbol _ZNK8wxWindow21GetContentScaleFactorEv version WXU_3.0 not defined in file libwx_gtk3u_core-3.0.so.0 with link time reference]

[Olly Betts]

Control: tag -1 +pending

On Sun, Sep 08, 2019 at 12:00:57PM +0200, Andreas Metzler wrote:
> ametzler@argenau:/tmp/HUGIN$ ldd -r /usr/bin/hugin > /dev/null
> symbol _ZNK8wxWindow21GetContentScaleFactorEv version WXU_3.0 not defined in 
> file libwx_gtk3u_core-3.0.so.0 with link time reference  
> (/usr/lib/hugin/libhuginbasewx.so.0.0)
> symbol _ZNK8wxWindow21GetContentScaleFactorEv version WXU_3.0 not defined in 
> file libwx_gtk3u_core-3.0.so.0 with link time reference  
> (/usr/lib/hugin/libicpfindlib.so.0.0)
> symbol _ZNK8wxWindow21GetContentScaleFactorEv version WXU_3.0 not defined in 
> file libwx_gtk3u_core-3.0.so.0 with link time reference  (/usr/bin/hugin)

There's a new entry in the upstream linker version script for this, but
this is the only new symbol since the last upstream release which our
package has cherry-picked the patch for and it looks like I failed to
merge the version-script change for it appropriately.

Thanks for catching this.  I'll make a new upload shortly.

Cheers,
Olly

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

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 20:40:10 +
with message-id 
and subject line Bug#939267: fixed in llvm-defaults 0.48.2
has caused the Debian Bug report #939267,
regarding clangd: missing Breaks+Replaces: clang-tools (<< 1:8)
to be marked as done.

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

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


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

Hi,

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

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

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

  Preparing to unpack .../clangd_1%3a8.0-48_amd64.deb ...
  Unpacking clangd (1:8.0-48) ...
  dpkg: error processing archive 
/var/cache/apt/archives/clangd_1%3a8.0-48_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/clangd', which is also in package clang-tools 
1:7.0-47.1
  Errors were encountered while processing:
   /var/cache/apt/archives/clangd_1%3a8.0-48_amd64.deb


cheers,

Andreas


clang-tools=1:7.0-47.1_clangd=1:8.0-48.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: llvm-defaults
Source-Version: 0.48.2

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

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

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-defaults 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 08 Sep 2019 21:25:12 +0200
Source: llvm-defaults
Architecture: source
Version: 0.48.2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Closes: 939267
Changes:
 llvm-defaults (0.48.2) unstable; urgency=medium
 .
   * Fix breaks/replaces for clangd (Closes: #939267)
Checksums-Sha1:
 830f2c6612cb2e704ae09095c117d855c2a1645b 2892 llvm-defaults_0.48.2.dsc
 9b45ddd94e07ac451e1ff64be3790f8d5fe7b1dc 11592 llvm-defaults_0.48.2.tar.xz
 79ec395c95ba1b21a16db795d078254fad5bbae7 11378 
llvm-defaults_0.48.2_amd64.buildinfo
Checksums-Sha256:
 e77075b7ecce609b49885b42cb462308377f4097de4abc7173c36f7e1ef1c5d4 2892 
llvm-defaults_0.48.2.dsc
 a9d3089d709953000880fba5d108dc77431bf33232387b5766a0f44353ba3418 11592 
llvm-defaults_0.48.2.tar.xz
 5d7716c369b9a63d3e2e219330dea5ec69ed5c332f2f26cde050f3bd06102cee 11378 
llvm-defaults_0.48.2_amd64.buildinfo
Files:
 bc7937ad7a6d2d46933da867ae9312e9 2892 devel optional llvm-defaults_0.48.2.dsc
 5b7d88b79c23a216d7438bc8b9fafcbc 11592 devel optional 
llvm-defaults_0.48.2.tar.xz
 d15476649813d600df790dc8b7f5393a 11378 devel optional 
llvm-defaults_0.48.2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAl11X+kACgkQfmUo2nUv
G+ExBw//T/ete39v9M2D2DknNzztr2K1N2Wrjm9ONe6fVemc0hlLD8li18H8jBov
IePlKrfEFtDUwnX4oMbZuaUYFJFSDrsOrjIXufdfi79tEDyAmsPKQfy8mtQ7tbDE
mn6ZUiIQVAlbf1Z5mOrcCbUGnU8yu9AUF17b4UajY98n6+k7A8tS7b3VRRL/AI+y
SRYDUUkUbuKfnygr6g4JA9InS0CWBrkhFnrmgVnfHwi4bbcpqWJZjKgvMCiwVvsC
VENq9B+S6zlgOP3LDkuF6/iMkfFSe7r26+5GuRiguoYevIebdoP2NPFYxIDAeqkq
uv95tZ1sEtRa2chBVkOWSPCPfncKg1CKkwwugLbOWBEBJsCS+US2k3I0N9KHeru0
H5Kb33mT6xTG9LQxcpnQSZlc1YfS0uci0hEGVyQW2iwMvKfvrOOQZYO4lnpE5EHR
gq8NPMV+kamNyzLb7dNxdd/Lw2h+RGebgwLXyDMnTfW0oykaVlXVO1RnvCCFC/D5
WrWzO6mHu3tRZ4Ib7YltyY0c9Ty3gvaKlx7z2ntG944Jb/9svFydPK1sGi0HYi+R
eOWPtW4eTKPf6e09LSxgR/WfxxZP1lppyle7pJOu8MW71v/UYJVkV2WbrXOIpv/7
PLgXDlHyzbY73T47yFlvjPJqM6D++8L/MUZSZ1vevZ5zjA8WGLo=
=pvgs
-END PGP SIGNATURE End Message ---

Bug#939750: marked as done (package unusable (missing/wrong dependencies))

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 20:40:16 +
with message-id 
and subject line Bug#939750: fixed in lollypop 1.1.4.16-2
has caused the Debian Bug report #939750,
regarding package unusable (missing/wrong dependencies)
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.)


-- 
939750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lollypop
Version: 1.1.4.16-1
Severity: grave
Tags: patch

without python3-gi installed:

$ lollypop
Traceback (most recent call last):
  File "/usr/bin/lollypop", line 14, in 
from gi.repository import Gio
ModuleNotFoundError: No module named 'gi.repository'

IOW: the package needs python3-gi to run.
OTOH gobject-introspection is *not* required.

There are a several more wrong more dependencies and build-dependencies:
- all the lib*-dev packages are *not* required
  (meson.build is wrong, there's nothing to compile here)
- instead several gir1.2-* packages are required
  (the contain the *.typelib files required for using gobject introspection
  with the correspnding libraries)
- libglib2.0-dev-bin is required for the build
  (it provides glib-compile-resources required to compile resource files)
- python-sqlite is totally wrong: it contains a Python binding to the
  obsolete SQLite2 library (and is python2 only); lollypop uses

 import sqlite3

  which is a Python binding for the SQLite3 library provided
  by package libpython3-stdlib which is already covered
  as a dependency of package python3


Patch (for meson.build and debian/control) attached.

Cheers, Roderich




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

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

-- no debconf information
--- a/debian/control
+++ b/debian/control
@@ -7,17 +7,15 @@
python3,
dh-python,
meson,
-   libglib2.0-dev,
-   libgirepository1.0-dev,
-   libgtk-3-dev,
-   gnome-common,
gir1.2-gstreamer-1.0,
-   libappstream-glib-dev,
-   python3-cairo,
-   python3-pil,
+   gir1.2-secret-1,
+   gir1.2-totemplparser-1.0,
+   libglib2.0-dev-bin,
+   python3,
python3-bs4,
+   python3-gi,
+   python3-pil,
python3-pylast,
-   libtotem-plparser-dev,
appstream-util,
 Standards-Version: 4.4.0
 Homepage: https://wiki.gnome.org/Apps/Lollypop
@@ -28,14 +26,14 @@
 Architecture: all
 Depends: ${python3:Depends},
  ${misc:Depends},
- gir1.2-totemplparser-1.0,
- gobject-introspection,
- python3-pylast,
+ gir1.2-gstreamer-1.0,
  gir1.2-secret-1,
+ gir1.2-totemplparser-1.0,
  python3,
- python3-pil,
  python3-bs4,
- python-sqlite
+ python3-gi,
+ python3-pil,
+ python3-pylast,
 Description: modern music player
  A Music player for GNOME featuring intuitive browsing of your music
  collection. Supports downloading of lyrics and cover art, syncing music
--- a/meson.build
+++ b/meson.build
@@ -13,9 +13,6 @@
 else
 message('Found python3 binary')
 endif
-dependency('glib-2.0')
-dependency('gobject-introspection-1.0', version: '>=1.35.9')
-dependency('gtk+-3.0', version :'>=3.20')
 
 python_dir = join_paths(get_option('prefix'), python.sysconfig_path('purelib'))
 LIBEXEC_DIR = join_paths(get_option('prefix'), get_option('libexecdir'))
--- End Message ---
--- Begin Message ---
Source: lollypop
Source-Version: 1.1.4.16-2

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

Debian distribution maintenance software
pp.
Andreas Rönnquist  (supplier of updated lollypop package)

(This message was generated automatically at their request; if you
believe that there is a problem with

Bug#874834: [Help] [avogadro] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Wed, Dec 13, 2017 at 02:54:07PM +0100, Andreas Tille wrote:
> control: tags -1 help
> 
> Hi,
> 
> I've moved avogadro packaging from SVN to Git.  I also had a look into
> the Qt5 migration.  The Git repository[1] contains a branch qt5.  I
> tried my best to adapt cmake to finalise the configuration step.

https://github.com/cryos/avogadro/issues/891 was tagged wontfix,
so let's remove it from the archive? We're closing in on the Qt4 removal
now.

It mentions an avogadro2, that can still be uploaded before bullseye
release when ready.

Cheers,
Moritz

Bug#849308: state of wireguard mainline inclusion?

[Daniel Kahn Gillmor]

Version: 0.0.20190905-1

Over in 849...@bugs.debian.org, Daniel Kahn Gillmor wrote:
> I do plan for putting wireguard into buster-backports, since i expect
> the upstream inclusion issues to be resolved one way or another by the
> time of bullseye release.  If anyone wants to help out by adding it to
> stretch-backports-sloppy, i would welcome that.

Following up on this, and after some discussion with Jason (upstream), i
think it's time to let wireguard migrate into debian testing.

So i'm closing #849308 with this e-mail, and once wireguard migrates
into testing, i'll look into putting it into buster-backports.

I welcome anyone who wants to contribute to the debian packaging to
offer maintenance help too!

  --dkg


signature.asc
Description: PGP signature

Bug#939768: gimp: It's the gegl mismatch...

[Manuel Bilderbeek]

Package: gimp
Version: 2.10.8-2+b1
Followup-For: Bug #939768

Dear Maintainer,

Some discussion on the GIMP IRC channel:

 what's your gegl version? (you can see with $ gimp -v)
 using GEGL version 0.4.12 (compiled against version 0.4.14)
 is that mismatch relevant?
 in this case, probably not
 Ell: do you think it's something gegl related?
 it could be
 Ell: is it worth to try with matching gegl?
 oh, wait. i see what it is :) it's absolutely the 0.4.12/14 mismatch
 Quibus: yes, a matching gegl will fix it

So, looks like the dependencies to gegl are not OK?

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

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

Versions of packages gimp depends on:
ii  gimp-data2.10.8-2
ii  libaa1   1.4p5-46+b1
ii  libbabl-0.1-00.1.62-1
ii  libbz2-1.0   1.0.6-9.2
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libfontconfig1   2.13.1-2+b1
ii  libfreetype6 2.9.1-4
ii  libgcc1  1:9.2.1-4
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libgegl-0.4-00.4.12-2
ii  libgexiv2-2  0.10.9-1
ii  libgimp2.0   2.10.8-2+b1
ii  libglib2.0-0 2.60.6-2
ii  libgs9   9.27~dfsg-3.1
ii  libgtk2.0-0  2.24.32-3
ii  libgudev-1.0-0   232-2
ii  libharfbuzz0b2.6.1-2
ii  libheif1 1.5.1-1
ii  libilmbase24 2.3.0-6
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-3+b1
ii  liblzma5 5.2.4-1+b1
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.3-0 1.3.0-2.1+b1
ii  libopenexr24 2.3.0-6
ii  libopenjp2-7 2.3.0-2
ii  libpango-1.0-0   1.42.4-7
ii  libpangocairo-1.0-0  1.42.4-7
ii  libpangoft2-1.0-01.42.4-7
ii  libpng16-16  1.6.37-1
ii  libpoppler-glib8 0.71.0-5+b1
ii  librsvg2-2   2.44.14-1
ii  libstdc++6   9.2.1-4
ii  libtiff5 4.0.10+git190818-1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libwmf0.2-7  0.2.8.4-14
ii  libx11-6 2:1.6.7-1
ii  libxcursor1  1:1.2.0-2
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxmu6  2:1.1.2-2+b3
ii  libxpm4  1:3.5.12-1
ii  xdg-utils1.1.3-1
ii  zlib1g   1:1.2.11.dfsg-1+b1

Versions of packages gimp recommends:
ii  ghostscript  9.27~dfsg-3.1

Versions of packages gimp suggests:
pn  gimp-data-extras  
pn  gimp-help-en | gimp-help  
pn  gimp-python   
ii  gvfs-backends 1.38.1-5
ii  libasound21.1.8-1

-- no debconf information

Bug#849308: marked as done (wireguard: Wireguard should not transition to stable yet)

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 16:28:52 -0400
with message-id <87y2yy5y7v@fifthhorseman.net>
and subject line Re: Bug#849308: state of wireguard mainline inclusion?
has caused the Debian Bug report #849308,
regarding wireguard: Wireguard should not transition to stable yet
to be marked as done.

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

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


-- 
849308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wireguard
Version: 0.0.20161223-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Wireguard appears to be stable and reliable enough to distribute in
debian unstable, to get more widespread testing than would arise from
distribution in experimental alone.

However, the on-wire format might still change, leading to potential
interop issues, and upstream isn't yet willing to maintain a stable
branch in the face of security issues (which is understandable given
the age of the project.

So this bug report is a placeholder to keep it from migration.  Feel
free to comment here!

   --dkg

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

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 0.0.20190905-1

Over in 849...@bugs.debian.org, Daniel Kahn Gillmor wrote:
> I do plan for putting wireguard into buster-backports, since i expect
> the upstream inclusion issues to be resolved one way or another by the
> time of bullseye release.  If anyone wants to help out by adding it to
> stretch-backports-sloppy, i would welcome that.

Following up on this, and after some discussion with Jason (upstream), i
think it's time to let wireguard migrate into debian testing.

So i'm closing #849308 with this e-mail, and once wireguard migrates
into testing, i'll look into putting it into buster-backports.

I welcome anyone who wants to contribute to the debian packaging to
offer maintenance help too!

  --dkg


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

Bug#875144: [qscintilla2] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

Hi,

On Sat, Sep 09, 2017 at 11:07:32PM +0200, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Source: qscintilla2
> Version: 2.9.3+dfsg-4
> Severity: wishlist
> User: debian-qt-...@lists.debian.org
> Usertags: qt4-removal
> 
> 
> Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> as [announced] in:
> 
> [announced] 
> 
> 
> Currently Qt4 has been dead upstream and we are starting to have problems
> maintaining it, like for example in the [OpenSSL 1.1 support] case.
> 
> [OpenSSL 1.1 support] 
> 
> 
> In order to make this move, all packages directly or indirectly depending on
> the Qt4 libraries have to either get ported to Qt5 or eventually get
> removed from the Debian repositories.
> 
> Therefore, please take the time and:
> - contact your upstream (if existing) and ask about the state of a Qt5
> port of your application
> - if there are no activities regarding porting, investigate whether there are
> suitable alternatives for your users
> - if there is a Qt5 port that is not yet packaged, consider packaging it
> - if both the Qt4 and the Qt5 versions already coexist in the Debian
> archives, consider removing the Qt4 version

All the reverse dependencies of libqscintilla2-qt4-dev and pyqt4.qsci-dev
have now been removed or fixed, so support for Qt4 can simply be dropped.

Cheers,
Moritz

Bug#939793: marked as done (plplot breaks coyote autopkgtest: times out)

[Debian Bug Tracking System]

Your message dated Sun, 8 Sep 2019 22:09:58 +0200
with message-id 
and subject line Re: plplot breaks coyote autopkgtest: times out
has caused the Debian Bug report #939793,
regarding plplot breaks coyote autopkgtest: times out
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.)


-- 
939793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plplot, coyote
Control: found -1 plplot/5.15.0+dfsg-3
Control: found -1 coyote/2019.02.25-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update timeout

Dear maintainers,

With a recent upload of plplot the autopkgtest of coyote fails in
testing when that autopkgtest is run with the binary packages of plplot
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
plplot from testing5.15.0+dfsg-3
coyote from testing2019.02.25-1
all others from testingfrom testing

I copied some of the output at the bottom of this report, but the
problem may be an infinite loop as the test times out now in the
autopkgtest framework after 2:27 hours, where it used to run under one
minute.

Currently this regression is blocking the migration of plplot 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?

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

https://ci.debian.net/data/autopkgtest/testing/amd64/c/coyote/2906835/log.gz




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi,

Hm, obviously I didn't meant coyote from unstable, as that is arch:all
and can't be nmu-ed, but I triggered it with gnudatalanguage and that's
fine.

So, closing as the issue is with britney, the migration software, that
doesn't trigger with the binNMU-ed packages from unstable yet.

Sorry for the noise.

Paul
PS: I don't know what to make of the gnudatalanguage failure yet though.



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

Processed: ghostscript breaks fig2dev autopkgtest: compare arrow tips with template failed unexpectedly

[Debian Bug Tracking System]

Processing control commands:

> found -1 ghostscript/9.28~~rc2~dfsg-1
Bug #939794 [src:ghostscript, src:fig2dev] ghostscript breaks fig2dev 
autopkgtest: compare arrow tips with template failed unexpectedly
Marked as found in versions ghostscript/9.28~~rc2~dfsg-1.
> found -1 fig2dev/1:3.2.7a-7
Bug #939794 [src:ghostscript, src:fig2dev] ghostscript breaks fig2dev 
autopkgtest: compare arrow tips with template failed unexpectedly
Marked as found in versions fig2dev/1:3.2.7a-7.

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

Bug#939794: ghostscript breaks fig2dev autopkgtest: compare arrow tips with template failed unexpectedly

[Paul Gevers]

Source: ghostscript, fig2dev
Control: found -1 ghostscript/9.28~~rc2~dfsg-1
Control: found -1 fig2dev/1:3.2.7a-7
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of ghostscript the autopkgtest of fig2dev fails in
testing when that autopkgtest is run with the binary packages of
ghostscript from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
ghostscriptfrom testing9.28~~rc2~dfsg-1
fig2devfrom testing1:3.2.7a-7
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report. (The output is
rather dense. I would love a more verbose output, so that others like me
have something to look at.)

Currently this regression is blocking the migration of ghostscript 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?

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

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
ghostscript/9.28~~rc2~dfsg-1. I.e. due to versioned dependencies or
breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=ghostscript

https://ci.debian.net/data/autopkgtest/testing/amd64/f/fig2dev/2909339/log.gz
Test PostScript output language.

 28: compare arrow tips with templateFAILED (output.at:41)



signature.asc
Description: OpenPGP digital signature

Bug#939791: [Debian-ha-maintainers] Bug#939791: crmsh: autopkgtest needs update for new version of lxml

[Valentin Vidić]

On Sun, Sep 08, 2019 at 09:53:34PM +0200, Paul Gevers wrote:
> Thanks for letting us know. I'll trigger a test run with lxml and crmsh
> from unstable. If that succeeds as expected, than please close this bug
> with the version of crmsh that fixed the issue.

Will do, thanks. Did not know about the versioned depends in tests,
hope I remember next time :)

-- 
Valentin

Bug#934384: libvma: FTBFS: some symbols or patterns disappeared

[Tzafrir Cohen]

On 10/08/2019 17:46, Niko Tyni wrote:
> Source: libvma
> Version: 8.8.1.really.8.7.7-1
> Severity: serious
> Tags: ftbfs
> 
> This package fails to build on current sid/amd64.
> 
>>From my build log:
> 
>   dpkg-gensymbols: warning: some new symbols appeared in the symbols file: 
> see diff output below
>   dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
>   dpkg-gensymbols: warning: debian/libvma8/DEBIAN/symbols doesn't match 
> completely debian/libvma8.symbols
>   --- debian/libvma8.symbols (libvma8_8.8.1.really.8.7.7-1_amd64)
>   +++ dpkg-gensymbolsBhlY4G   2019-08-10 14:41:41.948238949 +
>   @@ -542,7 +542,7 @@
> _ZN12sockinfo_tcp2rxE9rx_call_tP5ioveclPiP8sockaddrPjP6msghdr@Base 
> 8.8.1.really.8.7.7
> _ZN12sockinfo_tcp2txE9tx_call_tPK5iovecliPK8sockaddrj@Base 
> 8.8.1.really.8.7.7
> 
> _ZN12sockinfo_tcp30create_flow_tuple_key_from_pcbER10flow_tupleP7tcp_pcb@Base 
> 8.8.1.really.8.7.7
>   - _ZN12sockinfo_tcp30return_reuse_buffers_postponedEv@Base 
> 8.8.1.really.8.7.7
>   +#MISSING: 8.8.1.really.8.7.7-1# 
> _ZN12sockinfo_tcp30return_reuse_buffers_postponedEv@Base 8.8.1.really.8.7.7
> _ZN12sockinfo_tcp4bindEPK8sockaddrj@Base 8.8.1.really.8.7.7
> _ZN12sockinfo_tcp5fcntlEim@Base 8.8.1.really.8.7.7
> _ZN12sockinfo_tcp5ioctlEmm@Base 8.8.1.really.8.7.7
>   [...]
>   dh_makeshlibs: failing due to earlier errors
>   make: *** [debian/rules:15: binary] Error 255
>   dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
> status 2
> 

Sorry for the delay. Working on this and will have a fix this week.

-- Tzafrir

Bug#939791: [Debian-ha-maintainers] Bug#939791: crmsh: autopkgtest needs update for new version of lxml

[Paul Gevers]

Hi Valentin,

On 08-09-2019 21:47, Valentin Vidić wrote:
> Indeed, I updated crmsh to 4.1.0-3 in unstable to fix this problem
> and autopkgtest is passing for unstable now.

Thanks, I failed to spot that.

> The only problem is
> that it now needs the same version of lxml in testing to pass there.

So, the test should have had a *versioned* depends on lxml.

> In other words I think that lxml and crmsh should migrate to testing
> together now?

Yes. Next time, please make sure that the dependency resolution will
also know how to find the right combination.

> The new version of lxml does not break the package itself, it's just
> that one of the tests checks the XML output and the ordering of
> attributes has changed with the new version of lxml.

Thanks for letting us know. I'll trigger a test run with lxml and crmsh
from unstable. If that succeeds as expected, than please close this bug
with the version of crmsh that fixed the issue.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#939791: [Debian-ha-maintainers] Bug#939791: crmsh: autopkgtest needs update for new version of lxml

[Valentin Vidić]

On Sun, Sep 08, 2019 at 09:25:48PM +0200, Paul Gevers wrote:
> Source: crmsh
> Version: 4.1.0-2
> Severity: serious
> X-Debbugs-CC: debian...@lists.debian.org, l...@packages.debian.org
> Tags: sid bullseye
> User: debian...@lists.debian.org
> Usertags: needs-update
> Control: affects -1 src:lxml
> 
> Dear maintainers,
> 
> With a recent upload of lxml the autopkgtest of crmsh fails in testing
> when that autopkgtest is run with the binary packages of lxml from
> unstable. It passes when run with only packages from testing. In tabular
> form:
>passfail
> lxml   from testing4.4.1-1
> crmsh  from testing4.1.0-2
> versioned deps [0] from testingfrom unstable
> all others from testingfrom testing
> 
> I copied some of the output at the bottom of this report.

Indeed, I updated crmsh to 4.1.0-3 in unstable to fix this problem
and autopkgtest is passing for unstable now. The only problem is
that it now needs the same version of lxml in testing to pass there.
In other words I think that lxml and crmsh should migrate to testing
together now?

The new version of lxml does not break the package itself, it's just
that one of the tests checks the XML output and the ordering of
attributes has changed with the new version of lxml.

-- 
Valentin

Bug#939793: plplot breaks coyote autopkgtest: times out

[Paul Gevers]

Grr, I forgot the attachment, and I forgot that there is a transition
involved. Let me run the test with coyote from unstable as the test
passes there.

Paul

On 08-09-2019 21:34, Paul Gevers wrote:
> I copied some of the output at the bottom of this report

Openbox-Message: Unable to find a valid menu file
"/var/lib/openbox/debian-menu.xml"
% WARNING: your version of the GraphicsMagick library will truncate
images to 16 bits per pixel
% Compiled module: TEST_COYOTE.
% Compiled module: CGDEMODATA.
% Compiled module: CGSCALEVECTOR.
% Compiled module: FPUFIX.
% Compiled module: CGDISPLAY.
% Compiled module: CGQUERY.
% Compiled module: CGERRORMSG.

%CGDISPLAY: PLplot installation lacks the requested driver: xwin

Traceback Report from CGDISPLAY:

 PLplot installation lacks the requested driver: xwin
% Compiled module: CGPLOT.
% Compiled module: CGSETCOLORSTATE.
% Compiled module: CGGETCOLORSTATE.
% CGGETCOLORSTATE: PLplot installation lacks the requested driver: xwin
% Error occurred at: CGGETCOLORSTATE150
/usr/share/gnudatalanguage/coyote/cggetcolorstate.pro
%CGSETCOLORSTATE150
/usr/share/gnudatalanguage/coyote/cgsetcolorstate.pro
%CGPLOT 699
/usr/share/gnudatalanguage/coyote/cgplot.pro
%BASIC_LINE_PLOT  9
/tmp/autopkgtest-lxc.ru1iwmn9/downtmp/build.8eN/src/debian/tests/test_coyote.pro
%TEST_COYOTE302
/tmp/autopkgtest-lxc.ru1iwmn9/downtmp/build.8eN/src/debian/tests/test_coyote.pro
%$MAIN$

%CGPLOT: PLplot installation lacks the requested driver: xwin

Traceback Report from CGPLOT:

 PLplot installation lacks the requested driver: xwin
% CGGETCOLORSTATE: PLplot installation lacks the requested driver: xwin
% Error occurred at: CGGETCOLORSTATE150
/usr/share/gnudatalanguage/coyote/cggetcolorstate.pro
%CGSETCOLORSTATE150
/usr/share/gnudatalanguage/coyote/cgsetcolorstate.pro
%CGPLOT 699
/usr/share/gnudatalanguage/coyote/cgplot.pro
%PLOT_WITH_LEGEND36
/tmp/autopkgtest-lxc.ru1iwmn9/downtmp/build.8eN/src/debian/tests/test_coyote.pro
%TEST_COYOTE303
/tmp/autopkgtest-lxc.ru1iwmn9/downtmp/build.8eN/src/debian/tests/test_coyote.pro
%$MAIN$

%CGPLOT: PLplot installation lacks the requested driver: xwin

Traceback Report from CGPLOT:

 PLplot installation lacks the requested driver: xwin
% CGGETCOLORSTATE: PLplot installation lacks the requested driver: xwin
% Error occurred at: CGGETCOLORSTATE150
/usr/share/gnudatalanguage/coyote/cggetcolorstate.pro
%CGSETCOLORSTATE150
/usr/share/gnudatalanguage/coyote/cgsetcolorstate.pro
%CGPLOT 699
/usr/share/gnudatalanguage/coyote/cgplot.pro
%PLOT_WITH_LEGEND38
/tmp/autopkgtest-lxc.ru1iwmn9/downtmp/build.8eN/src/debian/tests/test_coyote.pro
%TEST_COYOTE303
/tmp/autopkgtest-lxc.ru1iwmn9/downtmp/build.8eN/src/debian/tests/test_coyote.pro
%$MAIN$

%CGPLOT: PLplot installation lacks the requested driver: xwin

Traceback Report from CGPLOT:

 PLplot installation lacks the requested driver: xwin
% Compiled module: CGLEGEND.
% Compiled module: CGLEGENDITEM__DEFINE.
% Compiled module: SETDEFAULTVALUE.
% Compiled module: CGDEFCHARSIZE.
% CGGETCOLORSTATE: PLplot installation lacks the requested driver: xwin
% Error occurred at: CGGETCOLORSTATE150
/usr/share/gnudatalanguage/coyote/cggetcolorstate.pro
%CGSETCOLORSTATE150
/usr/share/gnudatalanguage/coyote/cgsetcolorstate.pro
%CGLEGENDITEM::DRAW   637
/usr/share/gnudatalanguage/coyote/cglegenditem__define.pro
%CGLEGENDITEM::INIT   382
/usr/share/gnudatalanguage/coyote/cglegenditem__define.pro
%CGLEGEND   208
/usr/share/gnudatalanguage/coyote/cglegend.pro
%PLOT_WITH_LEGEND44
/tmp/autopkgtest-lxc.ru1iwmn9/downtmp/build.8eN/src/debian/tests/test_coyote.pro
%TEST_COYOTE303
/tmp/autopkgtest-lxc.ru1iwmn9/downtmp/build.8eN/src/debian/tests/test_coyote.pro
%$MAIN$

%CGLEGENDITEM::DRAW: PLplot installation lacks the requested driver: xwin

Traceback Report from CGLEGENDITEM::DRAW:

 PLplot installation lacks the requested driver: xwin

%CGDISPLAY: PLplot installation lacks the requested driver: xwin

Traceback Report from CGDISPLAY:

 PLplot installation lacks the requested driver: xwin
% CGGETCOLORSTATE: PLplot installation lacks the requested driver: xwin
% Error occurred at: CGGETCOLORSTATE150
/usr/share/gnudatalanguage/coyote/cggetcolorstate.pro
%CGSETCOLORSTATE150
/usr/share/gnudatalanguage/coyote/cgsetcolorstate.pro
%CGPLOT 699
/usr/share/gnudatalanguage/coyote/cgplot.pro
%ADDITIONAL_AXES_PLOT   

Processed: plplot breaks coyote autopkgtest: times out

[Debian Bug Tracking System]

Processing control commands:

> found -1 plplot/5.15.0+dfsg-3
Bug #939793 [src:plplot, src:coyote] plplot breaks coyote autopkgtest: times out
Marked as found in versions plplot/5.15.0+dfsg-3.
> found -1 coyote/2019.02.25-1
Bug #939793 [src:plplot, src:coyote] plplot breaks coyote autopkgtest: times out
Marked as found in versions coyote/2019.02.25-1.

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

Bug#939793: plplot breaks coyote autopkgtest: times out

[Paul Gevers]

Source: plplot, coyote
Control: found -1 plplot/5.15.0+dfsg-3
Control: found -1 coyote/2019.02.25-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update timeout

Dear maintainers,

With a recent upload of plplot the autopkgtest of coyote fails in
testing when that autopkgtest is run with the binary packages of plplot
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
plplot from testing5.15.0+dfsg-3
coyote from testing2019.02.25-1
all others from testingfrom testing

I copied some of the output at the bottom of this report, but the
problem may be an infinite loop as the test times out now in the
autopkgtest framework after 2:27 hours, where it used to run under one
minute.

Currently this regression is blocking the migration of plplot 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?

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

https://ci.debian.net/data/autopkgtest/testing/amd64/c/coyote/2906835/log.gz




signature.asc
Description: OpenPGP digital signature

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

[Debian Bug Tracking System]

Processing control commands:

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

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

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

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#939791: crmsh: autopkgtest needs update for new version of lxml

[Paul Gevers]

Source: crmsh
Version: 4.1.0-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, l...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:lxml

Dear maintainers,

With a recent upload of lxml the autopkgtest of crmsh fails in testing
when that autopkgtest is run with the binary packages of lxml from
unstable. It passes when run with only packages from testing. In tabular
form:
   passfail
lxml   from testing4.4.1-1
crmsh  from testing4.1.0-2
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

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

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

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from lxml should really add a
versioned Breaks on the unfixed version of (one of your) package(s).

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/c/crmsh/2911559/log.gz

==
FAIL: test_configs (unittests.test_parse.TestCliParser)
--
Traceback (most recent call last):
  File "/usr/share/crmsh/tests/unittests/test_parse.py", line 725, in
test_configs
self.assertEqual(expected, result)
AssertionError: '
?
 ---
+ 
?
   +++

 >> begin captured stdout << -
ERROR: Reference not found: d1-ops
ERROR: Reference not found: d1
ERROR: Reference not found: l2-rule1
ERROR: Reference not found: l2

- >> end captured stdout << --

==
FAIL: test_fencing (unittests.test_parse.TestCliParser)
--
Traceback (most recent call last):
  File "/usr/share/crmsh/tests/unittests/test_parse.py", line 460, in
test_fencing
self.assertEqual(expect, xml_tostring(out))
AssertionError: '' != ''
- 
+ 


--



signature.asc
Description: OpenPGP digital signature

Bug#939338: marked as done (/usr/include/gpsim/pic-processor.h references non-existent ../config.h)

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 19:07:23 +
with message-id 
and subject line Bug#939338: fixed in gpsim 0.31.0-2
has caused the Debian Bug report #939338,
regarding /usr/include/gpsim/pic-processor.h references non-existent ../config.h
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.)


-- 
939338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gpsim-dev
Version: 0.31.0-1
Severity: serious
Justification: simulide FTBFS
Tags: ftbfs
Control: affects -1 + src:simulide
File: /usr/include/gpsim/pic-processor.h

simulide fails to build from source. A build on amd64 ends with:

| g++ -c -pipe -g -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -O3 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC 
-DMAINMODULE_EXPORT= -DAPP_VERSION=\"0.1.7\" -DQT_NO_DEBUG -DQT_SVG_LIB 
-DQT_WIDGETS_LIB -DQT_MULTIMEDIA_LIB -DQT_GUI_LIB -DQT_XML_LIB 
-DQT_CONCURRENT_LIB -DQT_SERIALPORT_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. 
-I../src -I../src/gui -I../src/gui/circuitwidget 
-I../src/gui/circuitwidget/components -I../src/gui/circuitwidget/components/mcu 
-I../src/gui/oscopewidget -I../src/gui/plotterwidget 
-I../src/gui/terminalwidget -I../src/gui/QPropertyEditor 
-I../src/gui/componentselector -I../src/gui/filebrowser 
-I../src/gui/editorwidget -I../src/gui/editorwidget/findreplacedialog 
-I../src/gui/serialporwidget -I../src/simulator -I../src/simulator/elements 
-I../src/simulator/elements/processors -I../src/misc -I../src/simavr 
-I../src/simavr/sim -I../src/simavr/sim/avr -I../src/simavr/cores -isystem 
/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSerialPort -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I. -isystem /usr/include/libdrm 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o itemlibrary.o 
../src/gui/circuitwidget/itemlibrary.cpp
| In file included from /usr/include/gpsim/pic-processor.h:30,
|  from ../src/simulator/elements/processors/picprocessor.h:26,
|  from 
../src/gui/circuitwidget/components/mcu/piccomponent.h:24,
|  from ../src/gui/circuitwidget/itemlibrary.cpp:62:
| /usr/include/gpsim/breakpoints.h:25:10: fatal error: ../config.h: No such 
file or directory
|25 | #include "../config.h"
|   |  ^
| compilation terminated.
| make[1]: *** [Makefile:3380: itemlibrary.o] Error 1
| make[1]: Leaving directory '/<>/build_XX'
| dh_auto_build: cd build_XX && make -j1 returned exit code 2
| make: *** [debian/rules:17: build] Error 255
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

The file /usr/include/gpsim/pic-processor.h from the gpsim-dev package
references ../config.h, which does not exist. Including
 is bound to fail.

Helmut
--- End Message ---
--- Begin Message ---
Source: gpsim
Source-Version: 0.31.0-2

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated gpsim package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 08 Sep 2019 20:12:59 +0200
Source: gpsim
Architecture: source
Version: 0.31.0-2
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Closes: 939338
Changes:
 gpsim (0.31.0-2) unstable; urgency=medium
 .
   * adopted Slávek Banko's patch, thanks! Closes: #939338
Checksums-Sha1:
 84bd56ca965dcdbc9fdd5765c85131cb5c24101f 2026 gpsim_0.31.0-2.dsc
 a74a51d9f703a56a20e

Bug#939754: gimp: Crashes when I try to open an image or create a new one

[MKL]

Package: gimp
Version: 2.10.8-2+b1
Followup-For: Bug #939754

Dear Maintainer,

Here is what the console tells me when I open a new file:
gimp: fatal error: Segmentation fault
26  ../sysdeps/unix/sysv/linux/read.c: No such file or directory.

Thanks,

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

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

Versions of packages gimp depends on:
ii  gimp-data2.10.8-2
ii  libaa1   1.4p5-46+b1
ii  libbabl-0.1-00.1.62-1
ii  libbz2-1.0   1.0.6-9.2
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libfontconfig1   2.13.1-2+b1
ii  libfreetype6 2.9.1-4
ii  libgcc1  1:9.2.1-4
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libgegl-0.4-00.4.12-2
ii  libgexiv2-2  0.10.9-1
ii  libgimp2.0   2.10.8-2+b1
ii  libglib2.0-0 2.60.6-2
ii  libgs9   9.27~dfsg-3.1
ii  libgtk2.0-0  2.24.32-3
ii  libgudev-1.0-0   232-2
ii  libharfbuzz0b2.6.1-2
ii  libheif1 1.5.1-1
ii  libilmbase24 2.3.0-6
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-3+b1
ii  liblzma5 5.2.4-1+b1
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.3-0 1.3.0-2.1+b1
ii  libopenexr24 2.3.0-6
ii  libopenjp2-7 2.3.0-2
ii  libpango-1.0-0   1.42.4-7
ii  libpangocairo-1.0-0  1.42.4-7
ii  libpangoft2-1.0-01.42.4-7
ii  libpng16-16  1.6.37-1
ii  libpoppler-glib8 0.71.0-5+b1
ii  librsvg2-2   2.44.14-1
ii  libstdc++6   9.2.1-4
ii  libtiff5 4.0.10+git190818-1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libwmf0.2-7  0.2.8.4-14
ii  libx11-6 2:1.6.7-1
ii  libxcursor1  1:1.2.0-2
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxmu6  2:1.1.2-2+b3
ii  libxpm4  1:3.5.12-1
ii  xdg-utils1.1.3-1
ii  zlib1g   1:1.2.11.dfsg-1+b1

Versions of packages gimp recommends:
ii  ghostscript  9.27~dfsg-3.1

Versions of packages gimp suggests:
pn  gimp-data-extras  
pn  gimp-help-en | gimp-help  
pn  gimp-python   
pn  gvfs-backends 
ii  libasound21.1.8-1

-- no debconf information

Processed: retitle 939702 to imapfilter: CVE-2016-10937: does not validate hostname

[Debian Bug Tracking System]

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

> retitle 939702 imapfilter: CVE-2016-10937: does not validate hostname
Bug #939702 [imapfilter] imapfilter: does not validate hostname
Changed Bug title to 'imapfilter: CVE-2016-10937: does not validate hostname' 
from 'imapfilter: does not validate hostname'.
> thanks
Stopping processing here.

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

Processed: limit source to gigedit, tagging 915329

[Debian Bug Tracking System]

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

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

> tags 915329 + pending
Bug #915329 [src:gigedit] gigedit FTBFS with libgtkmm-3.0-dev 3.24.0-1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Handle Python2 removal bugs

[Debian Bug Tracking System]

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

> affects 936630 + src:python-pyqrcode
Bug #936630 [src:gnumed-client] gnumed-client: Python2 removal in sid/bullseye
Added indication that 936630 affects src:python-pyqrcode
> affects 937590 + src:python-pyqrcode
Bug #937590 [src:python-autobahn] python-autobahn: Python2 removal in 
sid/bullseye
Added indication that 937590 affects src:python-pyqrcode
> affects 935730 + src:python-pretty-yaml
Bug #935730 [kamcli] kamcli: port to python 3 (or remove from Debian?)
Added indication that 935730 affects src:python-pretty-yaml
> affects 938087 + src:pypng
Bug #938087 [src:python-pyqrcode] python-pyqrcode: Python2 removal in 
sid/bullseye
Added indication that 938087 affects src:pypng
> affects 937445 + src:pypng
Bug #937445 [src:pyglet] pyglet: Python2 removal in sid/bullseye
Added indication that 937445 affects src:pypng
> # Adjusted src:python-portpicker to no longer build python2 binary package
> # python-portpicker has no rdepends in unstable, RM
> retitle 938037 remove ‘python-portpicker' binary package from sid
Bug #938037 [src:python-portpicker] python-portpicker: Python2 removal in 
sid/bullseye
Changed Bug title to 'remove ‘python-portpicker' binary package from sid' from 
'python-portpicker: Python2 removal in sid/bullseye'.
> reassign 938037 ftp.debian.org
Bug #938037 [src:python-portpicker] remove ‘python-portpicker' binary package 
from sid
Bug reassigned from package 'src:python-portpicker' to 'ftp.debian.org'.
No longer marked as found in versions python-portpicker/1.3.1-2.
Ignoring request to alter fixed versions of bug #938037 to the same values 
previously set
> # Adjusted src:python-filelock to no longer build python2 binary package
> # python-filelock has no rdepends in unstable, RM
> retitle 937753 remove ‘python-filelock' binary package from sid
Bug #937753 [src:python-filelock] python-filelock: Python2 removal in 
sid/bullseye
Changed Bug title to 'remove ‘python-filelock' binary package from sid' from 
'python-filelock: Python2 removal in sid/bullseye'.
> reassign 937753 ftp.debian.org
Bug #937753 [src:python-filelock] remove ‘python-filelock' binary package from 
sid
Bug reassigned from package 'src:python-filelock' to 'ftp.debian.org'.
No longer marked as found in versions python-filelock/3.0.12-1.
Ignoring request to alter fixed versions of bug #937753 to the same values 
previously set
> # Adjusted src:python-fusepy to no longer build python2 binary package
> # python-fusepy has no rdepends in unstable, RM
> retitle 937772 remove ‘python-fusepy' binary package from sid
Bug #937772 [src:python-fusepy] python-fusepy: Python2 removal in sid/bullseye
Changed Bug title to 'remove ‘python-fusepy' binary package from sid' from 
'python-fusepy: Python2 removal in sid/bullseye'.
> reassign 937772 ftp.debian.org
Bug #937772 [src:python-fusepy] remove ‘python-fusepy' binary package from sid
Bug reassigned from package 'src:python-fusepy' to 'ftp.debian.org'.
No longer marked as found in versions python-fusepy/3.0.1-1.
Ignoring request to alter fixed versions of bug #937772 to the same values 
previously set
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
935730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935730
936630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936630
937445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937445
937590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937590
937753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937753
937772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937772
938037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938037
938087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#939779: kmod FTBFS: dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared libraries but --add-udeb=libkmod2-udeb was passed!?

[Sven Joachim]

Am 08.09.2019 um 20:10 schrieb Helmut Grohne:

> Source: kmod
> Version: 26-1
> Severity: serious
> Tags: ftbfs
>
> kmod fails to build from source in unstable:
>
> | dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4
> | dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared libraries 
> but --add-udeb=libkmod2-udeb was passed!?
> | make: *** [debian/rules:115: .stamp-binary] Error 255
> | dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
> status 2
>
> Is this a debhelper regression?

Not really, it was certainly a bug that earlier dh_makeshlibs versions
did not complain here.  Using --add-udeb when the udeb does not actually
contain a shared library is IMO a serious bug.  It is currently possible
to build a udeb with a program that links to libkmod.so.2 and have its
dependencies fulfilled, but such a program will fail at runtime in the
installer because the library is not there.

Cheers,
   Sven

Processed: libtcd: diff for NMU version 2.2.2-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 897675 + patch
Bug #897675 [src:libtcd] libtcd: not binNMU safe
Added tag(s) patch.
> tags 897675 + pending
Bug #897675 [src:libtcd] libtcd: not binNMU safe
Added tag(s) pending.

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

Bug#939401:

[Patrice Duroux]

Hi,

Looking at the following message and the next ones, I was also facing a trouble
and try to find a way to solve it on my system:
https://alioth-lists.debian.net/pipermail/pkg-nvidia-devel/2019-August/017339.html

Just to say that the legacy-390xx driver is not working here. Finally holding 
the version to 418.88-1 using https://snapshot.debian.org/ is fine. ;-)

Thanks,
Patrice

Bug#939687: clazy: FTBFS on armel: undefined reference to symbol '__atomic_load_4@@LIBATOMIC_1.0'

[Lisandro Damián Nicanor Pérez Meyer]

Hi! Thanks for filing the bug. And sorry for the duplicate, I don't
know why the bug report wasn't CCed.

On Sat, 7 Sep 2019 at 16:03, Paul Gevers  wrote:
>
> Source: clazy
> Version: 1.5-1
> Severity: serious
> Tags: ftbfs
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Dear maintainer,
>
> During a binNMU of clazy during the llvm-defaults transition, you package 
> FTBFS
> on armel. Can you please check and fix the situation?
>
> The last part of the log message as currently shown on
> https://buildd.debian.org/status/fetch.php?pkg=clazy&arch=armel&ver=1.5-1%2Bb1&stamp=1567623182&raw=0
>  reads:
>
> [100%] Linking CXX executable bin/clazy-standalone
> /usr/bin/cmake -E cmake_link_script CMakeFiles/clazy-standalone.dir/link.txt 
> --verbose=1
> /usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -Wno-class-memaccess -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -fno-common 
> -Woverloaded-virtual -Wcast-qual -fno-strict-aliasing -pedantic 
> -Wno-long-long -Wall -W -Wno-unused-parameter -Wwrite-strings -fno-exceptions 
> -fno-rtti -fPIC  -Wl,-z,relro -Wl,-z,now -latomic -rdynamic 
> CMakeFiles/clazy-standalone.dir/src/ClazyStandaloneMain.cpp.o  -o 
> bin/clazy-standalone  -L/usr/lib/llvm-8/lib 
> -Wl,-rpath,/usr/lib/llvm-8/lib:/<>/obj-arm-linux-gnueabi/lib: 
> lib/ClazyPlugin.so /usr/lib/llvm-8/lib/libclangFrontend.a 
> /usr/lib/llvm-8/lib/libclangDriver.a /usr/lib/llvm-8/lib/libclangCodeGen.a 
> /usr/lib/llvm-8/lib/libclangSema.a /usr/lib/llvm-8/lib/libclangAnalysis.a 
> /usr/lib/llvm-8/lib/libclangRewriteFrontend.a 
> /usr/lib/llvm-8/lib/libclangRewrite.a /usr/lib/llvm-8/lib/libclangAST.a 
> /usr/lib/llvm-8/lib/libclangASTMatchers.a /usr/lib/llvm-8/lib/libclangParse.a 
> /usr/lib/llvm-8/lib/libclangLex.a /usr/lib/llvm-8/lib/libclangBasic.a 
> /usr/lib/llvm-8/lib/libclangARCMigrate.a /usr/lib/llvm-8/lib/libclangEdit.a 
> /usr/lib/llvm-8/lib/libclangFrontendTool.a 
> /usr/lib/llvm-8/lib/libclangRewrite.a 
> /usr/lib/llvm-8/lib/libclangSerialization.a 
> /usr/lib/llvm-8/lib/libclangTooling.a 
> /usr/lib/llvm-8/lib/libclangStaticAnalyzerCheckers.a 
> /usr/lib/llvm-8/lib/libclangStaticAnalyzerCore.a 
> /usr/lib/llvm-8/lib/libclangStaticAnalyzerFrontend.a 
> /usr/lib/llvm-8/lib/libclangSema.a /usr/lib/llvm-8/lib/libLLVM-8.so 
> /usr/lib/llvm-8/lib/libclangAnalysis.a 
> /usr/lib/llvm-8/lib/libclangRewriteFrontend.a 
> /usr/lib/llvm-8/lib/libclangRewrite.a /usr/lib/llvm-8/lib/libclangAST.a 
> /usr/lib/llvm-8/lib/libclangASTMatchers.a /usr/lib/llvm-8/lib/libclangParse.a 
> /usr/lib/llvm-8/lib/libclangLex.a /usr/lib/llvm-8/lib/libclangBasic.a 
> /usr/lib/llvm-8/lib/libclangARCMigrate.a /usr/lib/llvm-8/lib/libclangEdit.a 
> /usr/lib/llvm-8/lib/libclangFrontendTool.a 
> /usr/lib/llvm-8/lib/libclangSerialization.a 
> /usr/lib/llvm-8/lib/libclangTooling.a 
> /usr/lib/llvm-8/lib/libclangStaticAnalyzerCheckers.a 
> /usr/lib/llvm-8/lib/libclangStaticAnalyzerCore.a 
> /usr/lib/llvm-8/lib/libclangStaticAnalyzerFrontend.a 
> /usr/lib/llvm-8/lib/libLLVM-8.so
> /usr/bin/ld: lib/ClazyPlugin.so: undefined reference to symbol 
> '__atomic_load_4@@LIBATOMIC_1.0'
> /usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/9/libatomic.so: error adding 
> symbols: DSO missing from command line
> collect2: error: ld returned 1 exit status
> make[3]: *** [CMakeFiles/clazy-standalone.dir/build.make:128: 
> bin/clazy-standalone] Error 1
> make[3]: Leaving directory '/<>/obj-arm-linux-gnueabi'
> make[2]: *** [CMakeFiles/Makefile2:76: CMakeFiles/clazy-standalone.dir/all] 
> Error 2
> make[2]: Leaving directory '/<>/obj-arm-linux-gnueabi'
> make[1]: *** [Makefile:155: all] Error 2
> make[1]: Leaving directory '/<>/obj-arm-linux-gnueabi'
> dh_auto_build: cd obj-arm-linux-gnueabi && make -j4 "INSTALL=install 
> --strip-program=true" returned exit code 2
> make: *** [debian/rules:19: build-arch] Error 255

According to the web this seems to be lacking an -latomic flag to the
linker, but I do wonder why it happens *now* and only on armel :-/
Has clang changed anything wrt armel?

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Processed: Split up report into two

[Debian Bug Tracking System]

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

> severity 939750 grave
Bug #939750 [src:lollypop] package unusable (missing/wrong dependencies)
Ignoring request to change severity of Bug 939750 to the same value.
> severity 939783 normal
Bug #939783 [src:lollypop] package unusable (missing/wrong dependencies)
Severity set to 'normal' from 'grave'
> notforwarded 939750
Bug #939750 [src:lollypop] package unusable (missing/wrong dependencies)
Unset Bug forwarded-to-address
> retitle 939783 meson.build dependencies unnecessary
Bug #939783 [src:lollypop] package unusable (missing/wrong dependencies)
Changed Bug title to 'meson.build dependencies unnecessary' from 'package 
unusable (missing/wrong dependencies)'.
> thanks
Stopping processing here.

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

Bug#939687: clazy: FTBFS on armel: undefined reference to symbol '__atomic_load_4@@LIBATOMIC_1.0'

[Lisandro Damián Nicanor Pérez Meyer]

Hi! Thanks for filing the bug.

On Sat, 7 Sep 2019 at 16:03, Paul Gevers  wrote:
>
> Source: clazy
> Version: 1.5-1
> Severity: serious
> Tags: ftbfs
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Dear maintainer,
>
> During a binNMU of clazy during the llvm-defaults transition, you package 
> FTBFS
> on armel. Can you please check and fix the situation?
>
> The last part of the log message as currently shown on
> https://buildd.debian.org/status/fetch.php?pkg=clazy&arch=armel&ver=1.5-1%2Bb1&stamp=1567623182&raw=0
>  reads:
>
> [100%] Linking CXX executable bin/clazy-standalone
> /usr/bin/cmake -E cmake_link_script CMakeFiles/clazy-standalone.dir/link.txt 
> --verbose=1
> /usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -Wno-class-memaccess -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -fno-common 
> -Woverloaded-virtual -Wcast-qual -fno-strict-aliasing -pedantic 
> -Wno-long-long -Wall -W -Wno-unused-parameter -Wwrite-strings -fno-exceptions 
> -fno-rtti -fPIC  -Wl,-z,relro -Wl,-z,now -latomic -rdynamic 
> CMakeFiles/clazy-standalone.dir/src/ClazyStandaloneMain.cpp.o  -o 
> bin/clazy-standalone  -L/usr/lib/llvm-8/lib 
> -Wl,-rpath,/usr/lib/llvm-8/lib:/<>/obj-arm-linux-gnueabi/lib: 
> lib/ClazyPlugin.so /usr/lib/llvm-8/lib/libclangFrontend.a 
> /usr/lib/llvm-8/lib/libclangDriver.a /usr/lib/llvm-8/lib/libclangCodeGen.a 
> /usr/lib/llvm-8/lib/libclangSema.a /usr/lib/llvm-8/lib/libclangAnalysis.a 
> /usr/lib/llvm-8/lib/libclangRewriteFrontend.a 
> /usr/lib/llvm-8/lib/libclangRewrite.a /usr/lib/llvm-8/lib/libclangAST.a 
> /usr/lib/llvm-8/lib/libclangASTMatchers.a /usr/lib/llvm-8/lib/libclangParse.a 
> /usr/lib/llvm-8/lib/libclangLex.a /usr/lib/llvm-8/lib/libclangBasic.a 
> /usr/lib/llvm-8/lib/libclangARCMigrate.a /usr/lib/llvm-8/lib/libclangEdit.a 
> /usr/lib/llvm-8/lib/libclangFrontendTool.a 
> /usr/lib/llvm-8/lib/libclangRewrite.a 
> /usr/lib/llvm-8/lib/libclangSerialization.a 
> /usr/lib/llvm-8/lib/libclangTooling.a 
> /usr/lib/llvm-8/lib/libclangStaticAnalyzerCheckers.a 
> /usr/lib/llvm-8/lib/libclangStaticAnalyzerCore.a 
> /usr/lib/llvm-8/lib/libclangStaticAnalyzerFrontend.a 
> /usr/lib/llvm-8/lib/libclangSema.a /usr/lib/llvm-8/lib/libLLVM-8.so 
> /usr/lib/llvm-8/lib/libclangAnalysis.a 
> /usr/lib/llvm-8/lib/libclangRewriteFrontend.a 
> /usr/lib/llvm-8/lib/libclangRewrite.a /usr/lib/llvm-8/lib/libclangAST.a 
> /usr/lib/llvm-8/lib/libclangASTMatchers.a /usr/lib/llvm-8/lib/libclangParse.a 
> /usr/lib/llvm-8/lib/libclangLex.a /usr/lib/llvm-8/lib/libclangBasic.a 
> /usr/lib/llvm-8/lib/libclangARCMigrate.a /usr/lib/llvm-8/lib/libclangEdit.a 
> /usr/lib/llvm-8/lib/libclangFrontendTool.a 
> /usr/lib/llvm-8/lib/libclangSerialization.a 
> /usr/lib/llvm-8/lib/libclangTooling.a 
> /usr/lib/llvm-8/lib/libclangStaticAnalyzerCheckers.a 
> /usr/lib/llvm-8/lib/libclangStaticAnalyzerCore.a 
> /usr/lib/llvm-8/lib/libclangStaticAnalyzerFrontend.a 
> /usr/lib/llvm-8/lib/libLLVM-8.so
> /usr/bin/ld: lib/ClazyPlugin.so: undefined reference to symbol 
> '__atomic_load_4@@LIBATOMIC_1.0'
> /usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/9/libatomic.so: error adding 
> symbols: DSO missing from command line
> collect2: error: ld returned 1 exit status
> make[3]: *** [CMakeFiles/clazy-standalone.dir/build.make:128: 
> bin/clazy-standalone] Error 1
> make[3]: Leaving directory '/<>/obj-arm-linux-gnueabi'
> make[2]: *** [CMakeFiles/Makefile2:76: CMakeFiles/clazy-standalone.dir/all] 
> Error 2
> make[2]: Leaving directory '/<>/obj-arm-linux-gnueabi'
> make[1]: *** [Makefile:155: all] Error 2
> make[1]: Leaving directory '/<>/obj-arm-linux-gnueabi'
> dh_auto_build: cd obj-arm-linux-gnueabi && make -j4 "INSTALL=install 
> --strip-program=true" returned exit code 2
> make: *** [debian/rules:19: build-arch] Error 255

According to the web this seems to be lacking an -latomic flag to the
linker, but I do wonder why it happens *now* and only on armel :-/
Has clang changed anything wrt armel?

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Bug#939750: Split up report into two

[Andreas Ronnquist]

severity 939750 grave
severity 939783 normal
notforwarded 939750
retitle 939783 meson.build dependencies unnecessary
thanks

Splitting up this into two reports - One for the Debian dependencies
[939750], and one for the meson build stuff [939783].

I'll fix the Debian dependencies bug in an upload soon.

Thanks
-- Andreas Rönnquist
gus...@debian.org

Bug#897675: libtcd: diff for NMU version 2.2.2-2.1

[Boyuan Yang]

Control: tags 897675 + patch
Control: tags 897675 + pending

Dear maintainer,

I've prepared an NMU for libtcd (versioned as 2.2.2-2.1) and
uploaded it to DELAYED/15. Please feel free to tell me if I
should delay it longer.

Regards,
Boyuan Yang

diff -u libtcd-2.2.2/debian/changelog libtcd-2.2.2/debian/changelog
--- libtcd-2.2.2/debian/changelog
+++ libtcd-2.2.2/debian/changelog
@@ -1,3 +1,24 @@
+libtcd (2.2.2-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Make libtcd-dev dependency to be using
+${binary:Version} instead of ${source:Version}.
+(Closes: #897675)
+  * debian/control:
++ Let libtcd-dev depends on ${misc:Depends}.
++ Replace Priority: extra with Priority: optional.
+  * debian/*.ex: Removed, useless. (lintian warning)
+  * debian/dirs: Removed, useless.
+  * debian/postinst,postrm: Empty scripts, removed.
+  * debian/libtcd0.dirs: Removed, useless.
+  * debian/rules:
++ Replace deprecated dh_clean -k with dh_prep.
++ Add missing recommended target build-arch and build-indep.
+  * debian/source/format: Explicitly use "1.0" format.
+  * debian/libtcd-dev.install: Do not install .la file.
+
+ -- Boyuan Yang   Sun, 08 Sep 2019 14:24:19 -0400
+
 libtcd (2.2.2-2) unstable; urgency=medium
 
   * debian/compat from 5 to 9
diff -u libtcd-2.2.2/debian/control libtcd-2.2.2/debian/control
--- libtcd-2.2.2/debian/control
+++ libtcd-2.2.2/debian/control
@@ -1,5 +1,5 @@
 Source: libtcd
-Priority: extra
+Priority: optional
 Maintainer: Peter S Galbraith 
 Build-Depends: debhelper (>= 5), dh-autoreconf
 Standards-Version: 3.9.8
@@ -8,7 +8,7 @@
 Package: libtcd-dev
 Section: libdevel
 Architecture: any
-Depends: libtcd0 (= ${source:Version})
+Depends: libtcd0 (= ${binary:Version}), ${misc:Depends}
 Description: Tide Constituent Database (TCD) library (header file)
  libtcd provides a software API for reading and writing Tide Constituent
  Database (TCD) files.
reverted:
--- libtcd-2.2.2/debian/dirs
+++ libtcd-2.2.2.orig/debian/dirs
@@ -1,2 +0,0 @@
-usr/bin
-usr/sbin
reverted:
--- libtcd-2.2.2/debian/libtcd-default.ex
+++ libtcd-2.2.2.orig/debian/libtcd-default.ex
@@ -1,10 +0,0 @@
-# Defaults for libtcd initscript
-# sourced by /etc/init.d/libtcd
-# installed at /etc/default/libtcd by the maintainer scripts
-
-#
-# This is a POSIX shell fragment
-#
-
-# Additional options that are passed to the Daemon.
-DAEMON_OPTS=""
diff -u libtcd-2.2.2/debian/libtcd-dev.install libtcd-2.2.2/debian/libtcd-
dev.install
--- libtcd-2.2.2/debian/libtcd-dev.install
+++ libtcd-2.2.2/debian/libtcd-dev.install
@@ -4 +3,0 @@
-debian/tmp/usr/lib/*.la
reverted:
--- libtcd-2.2.2/debian/libtcd.doc-base.EX
+++ libtcd-2.2.2.orig/debian/libtcd.doc-base.EX
@@ -1,22 +0,0 @@
-Document: libtcd
-Title: Debian libtcd Manual
-Author: 
-Abstract: This manual describes what libtcd is
- and how it can be used to
- manage online manuals on Debian systems.
-Section: unknown
-
-Format: debiandoc-sgml
-Files: /usr/share/doc/libtcd/libtcd.sgml.gz
-
-Format: postscript
-Files: /usr/share/doc/libtcd/libtcd.ps.gz
-
-Format: text
-Files: /usr/share/doc/libtcd/libtcd.text.gz
-
-Format: HTML
-Index: /usr/share/doc/libtcd/html/index.html
-Files: /usr/share/doc/libtcd/html/*.html
-
-  
reverted:
--- libtcd-2.2.2/debian/libtcd0.dirs
+++ libtcd-2.2.2.orig/debian/libtcd0.dirs
@@ -1 +0,0 @@
-usr/lib
reverted:
--- libtcd-2.2.2/debian/postinst
+++ libtcd-2.2.2.orig/debian/postinst
@@ -1,41 +0,0 @@
-#!/bin/sh
-# postinst script for libtcd
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-#*  `configure' 
-#*  `abort-upgrade' 
-#*  `abort-remove' `in-favour' 
-#  
-#*  `abort-remove'
-#*  `abort-deconfigure' `in-favour'
-#`removing'
-#   
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-
-case "$1" in
-configure)
-;;
-
-abort-upgrade|abort-remove|abort-deconfigure)
-;;
-
-*)
-echo "postinst called with unknown argument \`$1'" >&2
-exit 1
-;;
-esac
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0
-
-
reverted:
--- libtcd-2.2.2/debian/postrm
+++ libtcd-2.2.2.orig/debian/postrm
@@ -1,39 +0,0 @@
-#!/bin/sh
-# postrm script for libtcd
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-#*  `remove'
-#*  `purge'
-#*  `upgrade' 
-#*  `failed-upgrade' 
-#*  `abort-install'
-#*  `abort-install' 
-#*  `abort-upgrade' 
-#*  `disappear' 
-#  
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-
-case "$1" in
-purge|remove|upgrade|failed-upgrade|abort-install|abort-
upgrade|disappear)
-;;
-
-*)
-echo "postrm called with unknown argument \`$1'" >&2
-exit 1
-;;
-esac
-
-# dh_instal

Bug#931003: [Pkg-rust-maintainers] Bug#931003: Removed package(s) from unstable

[Ximin Luo]

Santiago Vila:
> reopen 931003
> found 931003 0.2.4-1
> fixed 931003 0.2.4-1+rm
> thanks
> 
> Hi.
> 
> This was automatically closed by ftpmaster because the package was
> removed from unstable, but this still does not fix the FTBFS problem
> in stable.
> 
> Thanks.
> 

Please be aware that the Debian Rust team today *does not make any effort* 
towards bugs affecting Debian Stable. If you want these bugs fixed, you will 
need to do it yourself.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Processed: cloning 939750

[Debian Bug Tracking System]

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

> clone 939750 -1
Bug #939750 [src:lollypop] package unusable (missing/wrong dependencies)
Bug 939750 cloned as bug 939783
> thanks
Stopping processing here.

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

Bug#939779: kmod FTBFS: dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared libraries but --add-udeb=libkmod2-udeb was passed!?

[Helmut Grohne]

Source: kmod
Version: 26-1
Severity: serious
Tags: ftbfs

kmod fails to build from source in unstable:

| dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4
| dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared libraries 
but --add-udeb=libkmod2-udeb was passed!?
| make: *** [debian/rules:115: .stamp-binary] Error 255
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

Is this a debhelper regression?

Helmut

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 925833 https://github.com/a2o/snoopy/issues/148
Bug #925833 [src:snoopy] snoopy: ftbfs with GCC-9
Set Bug forwarded-to-address to 'https://github.com/a2o/snoopy/issues/148'.
> thanks
Stopping processing here.

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

Bug#938952: marked as done ([debian Buster] [arm64 pinebook] [sysvinit-core] libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not going to be installed)

[Debian Bug Tracking System]

Your message dated Sun, 8 Sep 2019 19:11:56 +0200 (CEST)
with message-id 
and subject line Re: Bug#938952: [debian Buster] [arm64 pinebook] 
[sysvinit-core] libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is 
not going to be installed
has caused the Debian Bug report #938952,
regarding [debian Buster] [arm64 pinebook] [sysvinit-core] libsoup2.4-1 : 
Depends: glib-networking (>= 2.32.0) but it is not going to be installed
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.)


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

Package: sysvinit
Version: 2.93-8
Severity: grave

Dear maintainers,

It seems there is a dependency issue when installing sysvinit-core as 
indicated in following trace



ansible@pinebook:~$ LC_ALL=C LANG=C LANGUAGE=C sudo apt install 
sysvinit-core

Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 dconf-service : Depends: default-dbus-session-bus or
  dbus-session-bus
 libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not 
going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be 
caused by held packages.


My configuration is  :
ansible@pinebook:~$ cat /etc/debian_version
10.0

ansible@pinebook:~$ uname -a
Linux pinebook 5.2.5-sunxi64 #5.92 SMP Fri Aug 2 07:51:38 CEST 2019 
aarch64 GNU/Linux



ansible@pinebook:~$ grep deb /etc/apt/sources.list.d/* |grep -v "#"
/etc/apt/sources.list.d/debian_apt_v_10_buster_backports.list:deb 
http://ftp.fr.debian.org/debian buster-backports main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_current.list:deb 
http://ftp.debian.org/debian/ buster main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_previous.list:deb 
http://ftp.debian.org/debian/ stretch main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_update_security.list:deb 
http://security.debian.org buster/updates main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_updates.list:deb 
http://ftp.fr.debian.org/debian buster-updates main contrib non-free



ansible@pinebook:~$ cat 
/etc/apt/preferences.d/preferences_debian_v_10_buster* |grep -v "#" 
|grep -v "^$"

Package: dhcpcd5
Pin: release *
Pin-Priority: -1
Package: *systemd*
Pin: release *
Pin-Priority: -1


Package: *
Pin: release o=Debian,l=Debian,n=buster-update
Pin-Priority: 901
Package: *
Pin: release o=Debian,l=Debian,n=buster
Pin-Priority: 900
Package: *
Pin: release o=Debian,l=Debian,n=buster-backports
Pin-Priority: -1
Package: *
Pin: release o=Debian,l=Debian,n=stretch
Pin-Priority: 400
Package: *
Pin: release o=Debian,l=Debian,n=testing
Pin-Priority: -1
Package: *
Pin: release o=Debian,l=Debian,n=unstable
Pin-Priority: -1

ansible@pinebook:~$ dpkg -l |grep -v ii
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| 
État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements

|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
||/ Nom Version 
Architecture Description

+++-===---===


Thanks in advance for your help
Best regards
--- End Message ---
--- Begin Message ---
On Sun, 8 Sep 2019, Jean-Marc LACROIX wrote:

> ii  systemd 241-5
> arm64system and service manager

And:

> ansible@pinebook:~$ cat
> /etc/apt/preferences.d/preferences_debian_v_10_buster_no_systemd.pref |grep -v
> "#"
> 
> Package: systemd
> Pin: release *
> Pin-Priority: -1

Your package database is in an inconsistent state: you have
pinned systemd to be removed, but it is currently installed.

Fix either that first (remove systemd) or temporarily comment
out the pinning, then do the installation, removing systemd,
then restore the pinning if necessary. (The latter has a
higher chance of success.)

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49

Bug#939750: package unusable (missing/wrong dependencies)

[Andreas Ronnquist]

On Sun, 08 Sep 2019 14:26:31 +0200 Roderich Schupp
> 
> There are a several more wrong more dependencies and
> build-dependencies:
> - all the lib*-dev packages are *not* required
>   (meson.build is wrong, there's nothing to compile here)
> - instead several gir1.2-* packages are required
>   (the contain the *.typelib files required for using gobject
> introspection with the correspnding libraries)
> - libglib2.0-dev-bin is required for the build
>   (it provides glib-compile-resources required to compile resource
> files)
> - python-sqlite is totally wrong: it contains a Python binding to the
>   obsolete SQLite2 library (and is python2 only); lollypop uses
> 
>  import sqlite3
> 
>   which is a Python binding for the SQLite3 library provided
>   by package libpython3-stdlib which is already covered
>   as a dependency of package python3
> 
> 


Roderich, as you can see on 

https://gitlab.gnome.org/World/lollypop/merge_requests/1358

there is some discussion on if the meson.build should be changed.
I will of course follow what upstream does, but if you would like to
post comments for your point of view, that would be the place to do
it. 

I will of course apply your changes in Debian package dependencies to
the package. 

best regards and thanks for your help
/Andreas Rönnquist
gus...@debian.org

Bug#939750: package unusable (missing/wrong dependencies)

[Andreas Ronnquist]

On Sun, 08 Sep 2019 14:26:31 +0200 Roderich Schupp
 wrote:
> There are a several more wrong more dependencies and
> build-dependencies:
> - all the lib*-dev packages are *not* required
>   (meson.build is wrong, there's nothing to compile here)
> - instead several gir1.2-* packages are required
>   (the contain the *.typelib files required for using gobject
> introspection with the correspnding libraries)
> - libglib2.0-dev-bin is required for the build
>   (it provides glib-compile-resources required to compile resource
> files)
> - python-sqlite is totally wrong: it contains a Python binding to the
>   obsolete SQLite2 library (and is python2 only); lollypop uses
> 
>  import sqlite3
> 
>   which is a Python binding for the SQLite3 library provided
>   by package libpython3-stdlib which is already covered
>   as a dependency of package python3
> 
> 
> Patch (for meson.build and debian/control) attached.

Thanks - I have forwarded the changes to meson.build upstream [1], and I
will apply the dependencies changes to the Debian package.

1: https://gitlab.gnome.org/World/lollypop/merge_requests/1358

Thanks!
/Andreas Rönnquist
gus...@debian.org

Processed: bug 939750 is forwarded to https://gitlab.gnome.org/World/lollypop/merge_requests/1358

[Debian Bug Tracking System]

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

> forwarded 939750 https://gitlab.gnome.org/World/lollypop/merge_requests/1358
Bug #939750 [src:lollypop] package unusable (missing/wrong dependencies)
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/World/lollypop/merge_requests/1358'.
> thanks
Stopping processing here.

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

Bug#939755: marked as done (darktable: FTBFS with gcc-9)

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 15:49:15 +
with message-id 
and subject line Bug#939755: fixed in darktable 2.6.2-2
has caused the Debian Bug report #939755,
regarding darktable: FTBFS with gcc-9
to be marked as done.

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

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


-- 
939755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: darktable
Version: 2.6.2-1
Severity: serious
Tags: upstream
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

darktable in unstable and experimental fails to build with gcc-9, due
to openmp related changes.

This is known, and fixed upstream in git master.  It will probably be
at least another month or so before a release. There is more than one
merge request upstream that would have to be backported to do this
nicely.

Currently the options seem to be

- - force the build to use gcc-8

- - package a git snapshot, and (presumably) keep it out of testing

- - take on faith a 5k line patch opensuse is using; that patch only
  mentions one pull request, so I don't know if it is a complete
  solution.

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

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

Versions of packages darktable depends on:
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libcolord-gtk1   0.1.26-2
ii  libcolord2   1.4.3-4
ii  libcups2 2.3.0-3
ii  libcurl3-gnutls  7.65.3-1
ii  libexiv2-14  0.25-4
ii  libflickcurl01.26-4+b1
ii  libgcc1  1:9.2.1-4
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.60.6-2
ii  libgomp1 9.2.1-4
ii  libgphoto2-6 2.5.22-3
ii  libgphoto2-port122.5.22-3
ii  libgraphicsmagick-q16-3  1.4+really1.3.33-1
ii  libgtk-3-0   3.24.11-1
ii  libilmbase23 2.2.1-2+b1
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libjs-prototype  1.7.1-3
ii  libjs-scriptaculous  1.9.0-2
ii  libjson-glib-1.0-0   1.4.4-2
ii  liblcms2-2   2.9-3+b1
ii  liblensfun1  0.3.2-4
ii  liblua5.3-0  5.3.3-1.1+b1
ii  libopenexr23 2.2.1-4.1+b1
ii  libopenjp2-7 2.3.0-2
ii  libosmgpsmap-1.0-1   1.1.0-6
ii  libpango-1.0-0   1.42.4-7
ii  libpangocairo-1.0-0  1.42.4-7
ii  libpng16-16  1.6.37-1
ii  libpugixml1v51.9-3
ii  librsvg2-2   2.44.14-1
ii  libsecret-1-00.18.7-1
ii  libsoup2.4-1 2.64.2-2
ii  libsqlite3-0 3.29.0-2
ii  libstdc++6   9.2.1-4
ii  libtiff5 4.0.10+git190818-1
ii  libwebp6 0.6.1-2+b1
ii  libx11-6 2:1.6.7-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  libxrandr2   2:1.5.1-1
ii  zlib1g   1:1.2.11.dfsg-1+b1

darktable recommends no packages.

darktable suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl10/GAACgkQA0U5G1Wq
FSFWDA//UL9/NKzuYqDuMzS3TSJaROUb3YzWRtrQVcjd0F3+hYZ7/iXwfKSfndNw
Bs3jHQI0at1MOIv+eCWVhZAfen9fRJ0I184QCYqfUuN+zCZ1p6vDFj/6Bzem+eBK
/WPhEvqTjQpIC37ODX1tPsoM5D8cmD/O344y69Sp2bbIUoP3lM7IZa4oGS9Jkamf
itMXjGqHvcQwUh2kDqBaaRG4qMOtQOAwpFVYBhFPdIARiAW8JQK6kAXEyLLIB3pB
vc7wqNbp5SMrclKlNP2cOrlddUVi7VAnDh69/mjUfipt7uxKxp+BKDvg6BxZYZze
zCwoqi25p+aKvb66AgUUsmm1n+2QEutDNu1Ah009e1fzTZyZF+kcteB/midEShDz
lCPsHwJ+JUOSLKehjsLjviWtk+SRIeshsnhmtqNvMkdSZPjcYQbPXaQ35mjROSv1
VKu7CYO6EVJCvBTTKRmQmBgDTn6SjFPLEa5bRohwb1EBkzOI2H9ntGWRhEhfFIgi
P6LCm1wda3coyxEXn5gbFnbE1gsPG5m9uBFGsIOZ0+VcFnF0ohbDKL1X/xnf5VOn
y/RJT1qTVlyEHhBZvpmOs9IH7bP755kIoWJkW5WunbjaaSTz4zxRuwn2WsBzhg89
EEfQl2DXmpW63Mxk9HOW2jAoLlt4nrXVC4Intmd0FyIvEpnD5Tk=
=Q60t
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: darktable
Source-Version: 2.6.2-2

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

Bug#938952: [debian Buster] [arm64 pinebook] [sysvinit-core] libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not going to be installed

[Jean-Marc LACROIX]

Dimitry,
Thank for your reply.

> Please:
>
>   * Try installing something else, like `tor'. I expect you will get
> similar error (`tor' depends on libsystemd0, sigh)

ansible@pinebook:~$ sudo apt install tor
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  mixmaster torbrowser-launcher socat tor-arm apparmor-utils obfs4proxy
Recommended packages:
  tor-geoipdb torsocks
The following NEW packages will be installed:
  tor
0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded.
Need to get 1706 kB of archives.
After this operation, 4872 kB of additional disk space will be used.
Get:1 http://ftp.debian.org/debian buster/main arm64 tor arm64 0.3.5.8-1 
[1706 kB]

Fetched 1706 kB in 1s (2008 kB/s)
Selecting previously unselected package tor.
(Reading database ... 102649 files and directories currently installed.)
Preparing to unpack .../tor_0.3.5.8-1_arm64.deb ...
Unpacking tor (0.3.5.8-1) ...
Setting up tor (0.3.5.8-1) ...
Something or somebody made /var/lib/tor disappear.
Creating one for you again.
Something or somebody made /var/log/tor disappear.
Creating one for you again.
Created symlink /etc/systemd/system/multi-user.target.wants/tor.service 
→ /lib/systemd/system/tor.service.

Processing triggers for man-db (2.8.5-2) ...
Processing triggers for systemd (241-5) ...
ansible@pinebook:~$

ansible@pinebook:~$ dpkg -l |grep -v ii
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion 
Architecture Description

+++-===---===
ansible@pinebook:~$ dpkg -l |grep systemd
ii  dbus-user-session 
1.12.16-1arm64simple interprocess messaging 
system (systemd --user integration)
ii  libpam-systemd:arm64241-5 
arm64system and service manager - PAM module
ii  libsystemd0:arm64   241-5 
arm64systemd utility library
ii  syslog-ng-mod-journal   3.19.1-5 
arm64Enhanced system logging daemon 
(systemd journal plugin)
ii  systemd 241-5 
arm64system and service manager
ii  systemd-sysv241-5 
arm64system and service manager - SysV links



> Please:
>   * Replace `*systemd*' with `systemd' (without wildcard) in your
> apt-pinnings and try installing sysvinit-core again.
>

ansible@pinebook:~$ cat 
/etc/apt/preferences.d/preferences_debian_v_10_buster_no_systemd.pref 
|grep -v "#"


Package: systemd
Pin: release *
Pin-Priority: -1

then update/upgrade

ansible@pinebook:~$ sudo apt update && sudo apt upgrade
Get:1 http://ftp.fr.debian.org/debian buster-backports InRelease [46.7 kB]
Hit:2 http://security.debian.org buster/updates InRelease 

Hit:3 http://ftp.debian.org/debian buster InRelease 

Get:4 http://ftp.fr.debian.org/debian buster-updates InRelease [49.3 kB] 


Ign:5 http://ftp.debian.org/debian stretch InRelease
Hit:6 http://ftp.debian.org/debian stretch Release
Fetched 96.0 kB in 3s (36.8 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
3 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  libpam-systemd libsystemd0
The following packages will be upgraded:
  systemd-sysv
1 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Need to get 98.8 kB of archives.
After this operation, 1024 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.debian.org/debian buster/main arm64 systemd-sysv arm64 
241-7~deb10u1 [98.8 kB]

Fetched 98.8 kB in 0s (626 kB/s)
(Reading database ... 102692 files and directories currently installed.)
Preparing to unpack .../systemd-sysv_241-7~deb10u1_arm64.deb ...
Unpacking systemd-sysv (241-7~deb10u1) over (241-5) ...
Setting up systemd-sysv (241-7~deb10u1) ...
Processing triggers for man-db (2.8.5-2) ...
ansible@pinebook:~$

ansible@pinebook:~$ cat /etc/debian_version
10.1

...and of course without any errors ...

ansible@pinebook:~$ dpkg -l |grep -v ii
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameV

Bug#939768: gimp: After the last upgrade, GIMP crashes when creating a new image or opening an existing one.

[Diego Caraffini]

Package: gimp
Version: 2.10.8-2+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I currently use testing (bullseye), amd since the last upgrade, GIMP
keeps crashing whwnever I open am image or even create new one.

The images in question were edited minutes before the upgrade, so they
should adhere to the latest format specification.

The issue was noticed while using gimp-console and python-fu to convert
the images to pdf as part of the compilation of a latex document, and
later veriied to happen within the GUI.

This makes GIMP unusable.

The debug information is after the System information

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

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

Versions of packages gimp depends on:
ii  gimp-data2.10.8-2
ii  libaa1   1.4p5-46+b1
ii  libbabl-0.1-00.1.62-1
ii  libbz2-1.0   1.0.6-9.2
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libfontconfig1   2.13.1-2+b1
ii  libfreetype6 2.9.1-4
ii  libgcc1  1:9.2.1-4
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libgegl-0.4-00.4.12-2
ii  libgexiv2-2  0.10.9-1
ii  libgimp2.0   2.10.8-2+b1
ii  libglib2.0-0 2.60.6-2
ii  libgs9   9.27~dfsg-3.1
ii  libgtk2.0-0  2.24.32-3
ii  libgudev-1.0-0   232-2
ii  libharfbuzz0b2.6.1-2
ii  libheif1 1.5.1-1
ii  libilmbase24 2.3.0-6
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-3+b1
ii  liblzma5 5.2.4-1+b1
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.3-0 1.3.0-2.1+b1
ii  libopenexr24 2.3.0-6
ii  libopenjp2-7 2.3.0-2
ii  libpango-1.0-0   1.42.4-7
ii  libpangocairo-1.0-0  1.42.4-7
ii  libpangoft2-1.0-01.42.4-7
ii  libpng16-16  1.6.37-1
ii  libpoppler-glib8 0.71.0-5+b1
ii  librsvg2-2   2.44.14-1
ii  libstdc++6   9.2.1-4
ii  libtiff5 4.0.10+git190818-1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libwmf0.2-7  0.2.8.4-14
ii  libx11-6 2:1.6.7-1
ii  libxcursor1  1:1.2.0-2
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxmu6  2:1.1.2-2+b3
ii  libxpm4  1:3.5.12-1
ii  xdg-utils1.1.3-1
ii  zlib1g   1:1.2.11.dfsg-1+b1

Versions of packages gimp recommends:
ii  ghostscript  9.27~dfsg-3.1

Versions of packages gimp suggests:
pn  gimp-data-extras  
pn  gimp-help-en | gimp-help  
ii  gimp-python   2.10.8-2+b1
ii  gvfs-backends 1.38.1-5
ii  libasound21.1.8-1

-- no debconf information


-- Debug information:
```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-6' 
--with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-9 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib 
--with-target-system-zlib=auto --enable-multiarch --disable-werror 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa 
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 9.2.1 20190827 (Debian 9.2.1-6) 

using GEGL version 0.4.12 (compiled against version 0.4.14)
using GLib version 2.60.6 (compiled against version 2.60.6)
using GdkPixbuf version 2.38.1 (compiled against version 2.38.1)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo versio

Bug#830726: xtrlock: CVE-2016-10894: xtrlock does not block multitouch events

[Chris Lamb]

Hi Antoine,

> As this is getting a bit open-ended, though, do you think it could be
> worth it to release one of these patches soon

I agree, but I will first write to the xinput2 maintainers and leave a
little time to get a response there. However, I will set myself a
rough timeout of 3/4 days from right now so that we fallback to a
previous iteration as you outline regardless of whether I get around
to this or they fruitfully reply.


Regards,

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

Bug#939338: Remove the config.h header which is generated from breakpoints.h

[Slávek Banko]

tags 939338 + patch

I noticed the same problem during building ktechlab-trinity.

The attached patch removes the config.h header, which is generated and 
valid during build from the source code, from the breakpoints.h header 
that is part of the public API.

Cheers
-- 
Slávek
From c39da3038d9456663b17faa1606e87c5b16711ca Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Sl=C3=A1vek=20Banko?= 
Date: Sun, 8 Sep 2019 16:38:35 +0200
Subject: [PATCH] Remove the config.h header, which is generated and valid
 during build from the source code, from the breakpoints.h header that is part
 of the public API.
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

This resolves Debian Bug #939338.

Signed-off-by: Slávek Banko 
---
 cli/cmd_break.cc   | 1 +
 cli/socket.cc  | 1 +
 src/14bit-registers.cc | 2 ++
 src/breakpoints.h  | 2 --
 src/trigger.cc | 1 +
 5 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/cli/cmd_break.cc b/cli/cmd_break.cc
index 8cd8a48..40ec32f 100644
--- a/cli/cmd_break.cc
+++ b/cli/cmd_break.cc
@@ -26,6 +26,7 @@ Boston, MA 02111-1307, USA.  */
 #include "misc.h"
 #include "cmd_break.h"
 
+#include "../config.h"
 #include "../src/breakpoints.h"
 #include "../src/expr.h"
 #include "../src/gpsim_object.h"
diff --git a/cli/socket.cc b/cli/socket.cc
index 81c5663..5594376 100644
--- a/cli/socket.cc
+++ b/cli/socket.cc
@@ -32,6 +32,7 @@ Boston, MA 02111-1307, USA.  */
 #include 
 #include 
 
+#include "../config.h"
 //#include "../src/processor.h"
 #include "../src/symbol.h"
 #include "../src/protocol.h"
diff --git a/src/14bit-registers.cc b/src/14bit-registers.cc
index e967425..2b09e9c 100644
--- a/src/14bit-registers.cc
+++ b/src/14bit-registers.cc
@@ -26,6 +26,8 @@ License along with this library; if not, see
 #include 
 #include 
 
+#include "../config.h"
+
 #include "14bit-processors.h"
 #include "14bit-registers.h"
 #include "14bit-tmrs.h"
diff --git a/src/breakpoints.h b/src/breakpoints.h
index f784fc4..93d1172 100644
--- a/src/breakpoints.h
+++ b/src/breakpoints.h
@@ -22,8 +22,6 @@ License along with this library; if not, see
 #ifndef  SRC_BREAKPOINTS_H_
 #define  SRC_BREAKPOINTS_H_
 
-#include "../config.h"
-
 #include 
 #include 
 #include "exports.h"
diff --git a/src/trigger.cc b/src/trigger.cc
index a5eb8a1..0d7ed0e 100644
--- a/src/trigger.cc
+++ b/src/trigger.cc
@@ -19,6 +19,7 @@ License along with this library; if not, see
 */
 
 
+#include "../config.h"
 #include "trigger.h"
 #include "value.h"
 #include "expr.h"
-- 
2.11.0

Bug#932389: marked as done (gnome-sound-recorder crashes when trying to play back a recording)

[Debian Bug Tracking System]

Your message dated Sun, 8 Sep 2019 15:03:31 +0100
with message-id <20190908140331.ga10...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#932076: gnome-sound-recorder: Starting 
gnome-sound-recorder and then trying to play back a (previous) recording 
results in crash program.
has caused the Debian Bug report #932389,
regarding gnome-sound-recorder crashes when trying to play back a recording
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.)


-- 
932389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-sound-recorder
Version: 3.28.2-1
Severity: important

Crashes with:
** (org.gnome.SoundRecorder:12342): CRITICAL **: 19:04:35.810: 
g_object_info_get_n_fields: assertion 'info != NULL' failed
**
Gjs:ERROR:gi/object.cpp:481:bool ObjectInstance::field_getter_impl(JSContext*, 
JS::HandleObject, JS::HandleString, JS::MutableHandleValue): assertion failed: 
(field)

Playing back a recording is not possible. Pretty embarrassing for a program 
which has two functions and a default workflow which involves these two 
functions...

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

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

Versions of packages gnome-sound-recorder depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  gir1.2-gdkpixbuf-2.0 2.38.1+dfsg-1
ii  gir1.2-glib-2.0  1.58.3-2
ii  gir1.2-gst-plugins-base-1.0  1.14.4-2
ii  gir1.2-gstreamer-1.0 1.14.4-1
ii  gir1.2-gtk-3.0   3.24.5-1
ii  gir1.2-pango-1.0 1.42.4-6
ii  gjs  1.54.3-1
ii  gstreamer1.0-plugins-base1.14.4-2
ii  gstreamer1.0-plugins-good1.14.4-1
ii  gstreamer1.0-pulseaudio  1.14.4-1

gnome-sound-recorder recommends no packages.

gnome-sound-recorder suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.31.90-1

On Sun, 14 Jul 2019 at 21:30:06 +0300, Jury Mazurov wrote:
> The error is old. There are fixes.
> https://gitlab.gnome.org/GNOME/gjs/issues/223

I've uploaded a fixed version to unstable.

This change was already included in the newer upstream version in
experimental, so I'm closing the bug for the experimental branch with
this email.

> But the error is in a stable release. When will it get to buster?

The same as any other patch being applied to a stable release: in the
next stable point release after the release team approves its inclusion.
In this case, most likely Debian 10.2.

smcv--- End Message ---

Bug#932076: marked as done (gnome-sound-recorder: Starting gnome-sound-recorder and then trying to play back a (previous) recording results in crash program.)

[Debian Bug Tracking System]

Your message dated Sun, 8 Sep 2019 15:03:31 +0100
with message-id <20190908140331.ga10...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#932076: gnome-sound-recorder: Starting 
gnome-sound-recorder and then trying to play back a (previous) recording 
results in crash program.
has caused the Debian Bug report #932076,
regarding gnome-sound-recorder: Starting gnome-sound-recorder and then trying 
to play back a (previous) recording results in crash program.
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.)


-- 
932076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-sound-recorder
Version: 3.28.2-1
Severity: normal

Dear Maintainer,

The error is old. There are fixes.
https://gitlab.gnome.org/GNOME/gjs/issues/223

But the error is in a stable release. When will it get to buster?

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

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

Versions of packages gnome-sound-recorder depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  gir1.2-gdkpixbuf-2.0 2.38.1+dfsg-1
ii  gir1.2-glib-2.0  1.58.3-2
ii  gir1.2-gst-plugins-base-1.0  1.14.4-2
ii  gir1.2-gstreamer-1.0 1.14.4-1
ii  gir1.2-gtk-3.0   3.24.5-1
ii  gir1.2-pango-1.0 1.42.4-6
ii  gjs  1.54.3-1
ii  gstreamer1.0-plugins-base1.14.4-2
ii  gstreamer1.0-plugins-good1.14.4-1
ii  gstreamer1.0-pulseaudio  1.14.4-1

gnome-sound-recorder recommends no packages.

gnome-sound-recorder suggests no packages.

-- no debconf information

(org.gnome.SoundRecorder:6732): Gjs-WARNING **: 18:30:29.547: Some code 
accessed the property 'Application' on the module 'application'. That property 
was defined with 'let' or 'const' inside the module. This was previously 
supported, but is not correct according to the ES6 standard. Any symbols to be 
exported from a module must be defined with 'var'. The property access will 
work as previously for the time being, but please fix your code anyway.

(org.gnome.SoundRecorder:6732): Gtk-WARNING **: 18:30:29.548: Locale not 
supported by C library.
Using the fallback 'C' locale.
Gjs-Message: 18:30:29.652: JS LOG: Sound Recorder started
Gjs-Message: 18:30:29.653: JS WARNING: 
[resource:///org/gnome/SoundRecorder/js/application.js 84]: Too many arguments 
to function Gst.init: expected 1, got 2

(org.gnome.SoundRecorder:6732): Gjs-WARNING **: 18:30:29.682: Some code 
accessed the property 'MainWindow' on the module 'mainWindow'. That property 
was defined with 'let' or 'const' inside the module. This was previously 
supported, but is not correct according to the ES6 standard. Any symbols to be 
exported from a module must be defined with 'var'. The property access will 
work as previously for the time being, but please fix your code anyway.

(org.gnome.SoundRecorder:6732): Gjs-WARNING **: 18:30:29.683: Some code 
accessed the property 'AudioProfile' on the module 'audioProfile'. That 
property was defined with 'let' or 'const' inside the module. This was 
previously supported, but is not correct according to the ES6 standard. Any 
symbols to be exported from a module must be defined with 'var'. The property 
access will work as previously for the time being, but please fix your code 
anyway.

(org.gnome.SoundRecorder:6732): Gjs-WARNING **: 18:30:29.683: Some code 
accessed the property 'OffsetController' on the module 'fileUtil'. That 
property was defined with 'let' or 'const' inside the module. This was 
previously supported, but is not correct according to the ES6 standard. Any 
symbols to be exported from a module must be defined with 'var'. The property 
access will work as previously for the time being, but please fix your code 
anyway.

(org.gnome.SoundRecorder:6732): Gjs-WARNING **: 18:30:29.683: Some code 
accessed the property 'DisplayTime' on the module 'fileUtil'. That property was 
defined with 'let' or 'const' inside the module. This was previously supported, 
but is not correct according to the ES6 standard. Any symbols to be exported 
from a module must be

Bug#933035: marked as done (dmtcp: Should this package be removed?)

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 09:16:45 -0400
with message-id <08a9c7b9-4991-466b-9e06-5d189d6e4...@dartmouth.edu>
and subject line Re: Your Debian package(s) will not migrate to testing
has caused the Debian Bug report #933035,
regarding dmtcp: Should this package be removed?
to be marked as done.

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

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


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

The last upload was in 2014 and it's RC-buggy for a long time, it missed two
stable releases already.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 2.6.0-1

IMHO 933035 was a logistic report about bad state of the package and it was 
resolved by the last upload, this closing it here. 
I can do source only upload, but to say the truth, I didn't know that it is the 
requirement now. What needs to be addressed for migration is failing builds. 
Gene and Paul,  you can access logs from 
https://buildd.debian.org/status/package.php?p=dmtcp to see what fixed for i386 
and armhf

On September 8, 2019 4:23:08 AM EDT, "j...@debian.org"  wrote:
>On Sat, Sep 07, 2019 at 09:54:24AM +, Cooperman, Gene wrote:
>> Hi Julian,
>> Thank you for the courtesy message about the DMTCP
>> package in sid (included below).
>> Paul Grosu and I had submitted the package for dmtcp-2.6.0-1 .
>> Yaroslav (cc'ed here) is the downstream Debian maintainer.
>> 
>> Since Paul and I are unfamiliar with all the rules of Debian, could
>> you help us with further details about why dmtcp-2.6.0-1 is stuck
>> in sid?
>> 
>> We looked at:  https://tracker.debian.org/pkg/dmtcp
>> It seems that the reasons there apply only to the old dmtcp-2.3.1-6
>> and not to our current submission:  dmtcp-2.6.0-1
>> [...]
>
>Hi Gene,
>
>I ran (from the devscripts package) "grep-excuses dmtcp" and was told:
>
>dmtcp (- to 2.6.0-1)
>Maintainer: Paul Grosu
>19 days old (needed 10 days)
>Migration status for dmtcp (- to 2.6.0-1): BLOCKED:
>Rejected/violates migration policy/introduces a regression
>Issues preventing migration:
>Updating dmtcp introduces new bugs: #933035
>Not built on buildd: arch amd64 binaries uploaded by yoh
>missing build on armhf
>missing build on i386
>Additional info:
>Piuparts tested OK -
>https://piuparts.debian.org/sid/source/d/dmtcp.html
>19 days old (needed 10 days)
>
>So this was not a source-only upload.
>
>This wiki page explains how to do a source-only upload using several
>different approaches:
>https://wiki.debian.org/SourceOnlyUpload
>
>So you'll need to do one of these when you upload version 2.6.0-2 (or
>later), and then it will be able to migrate to testing (at least once
>bug#933035 is also addressed).
>
>I hope this helps!
>
>Best wishes,
>
>   Julian--- End Message ---

Processed: found 939755 in 2.6.0-1, tagging 939755

[Debian Bug Tracking System]

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

> found 939755 2.6.0-1
Bug #939755 [darktable] darktable: FTBFS with gcc-9
Marked as found in versions darktable/2.6.0-1.
> tags 939755 + bullseye sid experimental
Bug #939755 [darktable] darktable: FTBFS with gcc-9
Added tag(s) experimental, sid, and bullseye.
> thanks
Stopping processing here.

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

Bug#939755: darktable: FTBFS with gcc-9

[David Bremner]

Package: darktable
Version: 2.6.2-1
Severity: serious
Tags: upstream
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

darktable in unstable and experimental fails to build with gcc-9, due
to openmp related changes.

This is known, and fixed upstream in git master.  It will probably be
at least another month or so before a release. There is more than one
merge request upstream that would have to be backported to do this
nicely.

Currently the options seem to be

- - force the build to use gcc-8

- - package a git snapshot, and (presumably) keep it out of testing

- - take on faith a 5k line patch opensuse is using; that patch only
  mentions one pull request, so I don't know if it is a complete
  solution.

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

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

Versions of packages darktable depends on:
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libcolord-gtk1   0.1.26-2
ii  libcolord2   1.4.3-4
ii  libcups2 2.3.0-3
ii  libcurl3-gnutls  7.65.3-1
ii  libexiv2-14  0.25-4
ii  libflickcurl01.26-4+b1
ii  libgcc1  1:9.2.1-4
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.60.6-2
ii  libgomp1 9.2.1-4
ii  libgphoto2-6 2.5.22-3
ii  libgphoto2-port122.5.22-3
ii  libgraphicsmagick-q16-3  1.4+really1.3.33-1
ii  libgtk-3-0   3.24.11-1
ii  libilmbase23 2.2.1-2+b1
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libjs-prototype  1.7.1-3
ii  libjs-scriptaculous  1.9.0-2
ii  libjson-glib-1.0-0   1.4.4-2
ii  liblcms2-2   2.9-3+b1
ii  liblensfun1  0.3.2-4
ii  liblua5.3-0  5.3.3-1.1+b1
ii  libopenexr23 2.2.1-4.1+b1
ii  libopenjp2-7 2.3.0-2
ii  libosmgpsmap-1.0-1   1.1.0-6
ii  libpango-1.0-0   1.42.4-7
ii  libpangocairo-1.0-0  1.42.4-7
ii  libpng16-16  1.6.37-1
ii  libpugixml1v51.9-3
ii  librsvg2-2   2.44.14-1
ii  libsecret-1-00.18.7-1
ii  libsoup2.4-1 2.64.2-2
ii  libsqlite3-0 3.29.0-2
ii  libstdc++6   9.2.1-4
ii  libtiff5 4.0.10+git190818-1
ii  libwebp6 0.6.1-2+b1
ii  libx11-6 2:1.6.7-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  libxrandr2   2:1.5.1-1
ii  zlib1g   1:1.2.11.dfsg-1+b1

darktable recommends no packages.

darktable suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl10/GAACgkQA0U5G1Wq
FSFWDA//UL9/NKzuYqDuMzS3TSJaROUb3YzWRtrQVcjd0F3+hYZ7/iXwfKSfndNw
Bs3jHQI0at1MOIv+eCWVhZAfen9fRJ0I184QCYqfUuN+zCZ1p6vDFj/6Bzem+eBK
/WPhEvqTjQpIC37ODX1tPsoM5D8cmD/O344y69Sp2bbIUoP3lM7IZa4oGS9Jkamf
itMXjGqHvcQwUh2kDqBaaRG4qMOtQOAwpFVYBhFPdIARiAW8JQK6kAXEyLLIB3pB
vc7wqNbp5SMrclKlNP2cOrlddUVi7VAnDh69/mjUfipt7uxKxp+BKDvg6BxZYZze
zCwoqi25p+aKvb66AgUUsmm1n+2QEutDNu1Ah009e1fzTZyZF+kcteB/midEShDz
lCPsHwJ+JUOSLKehjsLjviWtk+SRIeshsnhmtqNvMkdSZPjcYQbPXaQ35mjROSv1
VKu7CYO6EVJCvBTTKRmQmBgDTn6SjFPLEa5bRohwb1EBkzOI2H9ntGWRhEhfFIgi
P6LCm1wda3coyxEXn5gbFnbE1gsPG5m9uBFGsIOZ0+VcFnF0ohbDKL1X/xnf5VOn
y/RJT1qTVlyEHhBZvpmOs9IH7bP755kIoWJkW5WunbjaaSTz4zxRuwn2WsBzhg89
EEfQl2DXmpW63Mxk9HOW2jAoLlt4nrXVC4Intmd0FyIvEpnD5Tk=
=Q60t
-END PGP SIGNATURE-

Bug#939754: gimp: Crashes when I try to open an image or create a new one

[Alexander]

Package: gimp
Version: 2.10.8-2+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

Starting GIMP and either creating an image using File->New, File->Create
Screenshot, File->Create from Clipboard or starting GIMP from a terminal with
an existing image file as only argument.

File->Open, File->Open as layers crashes GIMP as soon as I click on an image to
get a preview.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I installed updates etc., I also installed dbsym-packages for every library
shown by apt-cache depends gimp.

Here is the backtrace from the "GIMP Crash Debug" window:

```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-6'
--with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-
languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-
gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu-
--enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-
included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls
--enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-
libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib
--with-target-system-zlib=auto --enable-multiarch --disable-werror --with-
arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib
--with-tune=generic --enable-offload-targets=nvptx-none,hsa --without-cuda-
driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-
gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 9.2.1 20190827 (Debian 9.2.1-6)

using GEGL version 0.4.12 (compiled against version 0.4.14)
using GLib version 2.60.6 (compiled against version 2.60.6)
using GdkPixbuf version 2.38.1 (compiled against version 2.38.1)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 31639 - Thread 31639 #

[New LWP 31655]
[New LWP 31656]
[New LWP 31672]
[New LWP 31673]
[New LWP 31674]
[New LWP 31675]
[New LWP 31676]
[New LWP 31677]
[New LWP 31678]
[New LWP 31679]
[New LWP 31680]
[New LWP 31681]
[New LWP 31682]
[New LWP 31683]
[New LWP 31684]
[New LWP 31685]
[New LWP 31686]
[New LWP 31687]
[New LWP 31688]
[New LWP 31702]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7ffd1dd929d0, fd=16) at
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id   Frame
* 1Thread 0x7f6635957e00 (LWP 31639) "gimp"__libc_read (nbytes=256,
buf=0x7ffd1dd929d0, fd=16) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7f660e594700 (LWP 31655) "gmain"   0x7f66376b2819 in
__GI___poll (fds=0x5564f4db91f0, nfds=2, timeout=2999) at
../sysdeps/unix/sysv/linux/poll.c:29
  3Thread 0x7f6610d95700 (LWP 31656) "gdbus"   0x7f66376b2819 in
__GI___poll (fds=0x5564f4dd0a20, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
  4Thread 0x7f65f9d8f700 (LWP 31672) "async"   syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7f65f958e700 (LWP 31673) "worker"  syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7f65f8d8d700 (LWP 31674) "worker"  syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x7f65f858c700 (LWP 31675) "worker"  syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7f65f7d8b700 (LWP 31676) "worker"  syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7f65f758a700 (LWP 31677) "worker"  syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7f65f6d89700 (LWP 31678) "worker"  syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7f65f6588700 (LWP 31679) "worker"  syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7f65f5d87700 (LWP 31680) "worker"  syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  13   Thread 0x7f65f5586700 (LWP 31681) "worker"  syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  14   Thread 0x7f65f4d85700 (LWP 31682) "worker"  syscall () at
../sys

Bug#939750: package unusable (missing/wrong dependencies)

[Roderich Schupp]

Source: lollypop
Version: 1.1.4.16-1
Severity: grave
Tags: patch

without python3-gi installed:

$ lollypop
Traceback (most recent call last):
  File "/usr/bin/lollypop", line 14, in 
from gi.repository import Gio
ModuleNotFoundError: No module named 'gi.repository'

IOW: the package needs python3-gi to run.
OTOH gobject-introspection is *not* required.

There are a several more wrong more dependencies and build-dependencies:
- all the lib*-dev packages are *not* required
  (meson.build is wrong, there's nothing to compile here)
- instead several gir1.2-* packages are required
  (the contain the *.typelib files required for using gobject introspection
  with the correspnding libraries)
- libglib2.0-dev-bin is required for the build
  (it provides glib-compile-resources required to compile resource files)
- python-sqlite is totally wrong: it contains a Python binding to the
  obsolete SQLite2 library (and is python2 only); lollypop uses

 import sqlite3

  which is a Python binding for the SQLite3 library provided
  by package libpython3-stdlib which is already covered
  as a dependency of package python3


Patch (for meson.build and debian/control) attached.

Cheers, Roderich




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

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

-- no debconf information
--- a/debian/control
+++ b/debian/control
@@ -7,17 +7,15 @@
python3,
dh-python,
meson,
-   libglib2.0-dev,
-   libgirepository1.0-dev,
-   libgtk-3-dev,
-   gnome-common,
gir1.2-gstreamer-1.0,
-   libappstream-glib-dev,
-   python3-cairo,
-   python3-pil,
+   gir1.2-secret-1,
+   gir1.2-totemplparser-1.0,
+   libglib2.0-dev-bin,
+   python3,
python3-bs4,
+   python3-gi,
+   python3-pil,
python3-pylast,
-   libtotem-plparser-dev,
appstream-util,
 Standards-Version: 4.4.0
 Homepage: https://wiki.gnome.org/Apps/Lollypop
@@ -28,14 +26,14 @@
 Architecture: all
 Depends: ${python3:Depends},
  ${misc:Depends},
- gir1.2-totemplparser-1.0,
- gobject-introspection,
- python3-pylast,
+ gir1.2-gstreamer-1.0,
  gir1.2-secret-1,
+ gir1.2-totemplparser-1.0,
  python3,
- python3-pil,
  python3-bs4,
- python-sqlite
+ python3-gi,
+ python3-pil,
+ python3-pylast,
 Description: modern music player
  A Music player for GNOME featuring intuitive browsing of your music
  collection. Supports downloading of lyrics and cover art, syncing music
--- a/meson.build
+++ b/meson.build
@@ -13,9 +13,6 @@
 else
 message('Found python3 binary')
 endif
-dependency('glib-2.0')
-dependency('gobject-introspection-1.0', version: '>=1.35.9')
-dependency('gtk+-3.0', version :'>=3.20')
 
 python_dir = join_paths(get_option('prefix'), python.sysconfig_path('purelib'))
 LIBEXEC_DIR = join_paths(get_option('prefix'), get_option('libexecdir'))

Bug#935346: work in progress upstream?

[Sandro Tosi]

On Sat, Sep 7, 2019 at 10:03 AM David Bremner  wrote:
>
>
> It looks like the pyqt5 branch discussed in
>
>https://github.com/keithgg/puddletag/issues/418
>
> has been merged to master, but I didn't manage to make it work with
> PyQt5. It looks like the source still hardcodes pyqt5, so I don't know
> what's going on there.

yes, upstream is working on it, no it's not ready yet :) we'll need to
wait for them to release a new version, hopefully soon
I'm monitoring the situation as currently puddletag is python2-only
and i dont want it to get removed from the distro

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#931003: Removed package(s) from unstable

[Santiago Vila]

reopen 931003
found 931003 0.2.4-1
fixed 931003 0.2.4-1+rm
thanks

Hi.

This was automatically closed by ftpmaster because the package was
removed from unstable, but this still does not fix the FTBFS problem
in stable.

Thanks.

Bug#931002: Removed package(s) from unstable

[Santiago Vila]

reopen 931002
found 931002 0.1.2-1
fixed 931002 0.1.2-1+rm
thanks

Hi.

This was automatically closed by ftpmaster because the package was
removed from unstable, but this still does not fix the FTBFS problem
in stable.

Thanks.

Processed: retitle 872801 to RFP: RTS2 -- open source observatory manager ...

[Debian Bug Tracking System]

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

> #fix some WNPP bugs titles
> retitle 872801 RFP: RTS2 -- open source observatory manager
Bug #872801 [wnpp] RFP: RTS2 - open source observatory manager
Changed Bug title to 'RFP: RTS2 -- open source observatory manager' from 'RFP: 
RTS2 - open source observatory manager'.
> retitle 889225 O: golang-github-mrjones-oauth -- OAuth 1.0 Library for Go
Bug #889225 [wnpp] O: golang-github-mrjones-oauth - OAuth 1.0 Library for Go
Changed Bug title to 'O: golang-github-mrjones-oauth -- OAuth 1.0 Library for 
Go' from 'O: golang-github-mrjones-oauth - OAuth 1.0 Library for Go'.
> retitle 889235 O: golang-github-issue9-identicon -- generate an icon from 
> identity information
Bug #889235 [wnpp] O: golang-github-issue9-identicon - generate an icon from 
identity information
Changed Bug title to 'O: golang-github-issue9-identicon -- generate an icon 
from identity information' from 'O: golang-github-issue9-identicon - generate 
an icon from identity information'.
> retitle 831981 RFP: mkusb -- Tool to make boot drives.
Bug #831981 [wnpp] RFP: mkusb - Tool to make boot drives.
Changed Bug title to 'RFP: mkusb -- Tool to make boot drives.' from 'RFP: mkusb 
- Tool to make boot drives.'.
> retitle 864808 RFP: php-openid -- OpenID library for PHP
Bug #864808 [wnpp] RFP: php-openid - OpenID library for PHP
Changed Bug title to 'RFP: php-openid -- OpenID library for PHP' from 'RFP: 
php-openid - OpenID library for PHP'.
> retitle 889200 O: golang-github-unknwon-cae -- PHP-like Compression and 
> Archive Extensions in Go
Bug #889200 [wnpp] O: golang-github-unknwon-cae - PHP-like Compression and 
Archive Extensions in Go
Changed Bug title to 'O: golang-github-unknwon-cae -- PHP-like Compression and 
Archive Extensions in Go' from 'O: golang-github-unknwon-cae - PHP-like 
Compression and Archive Extensions in Go'.
> retitle 877796 ITP: libpherkin-extension-weasel-perl -- Pherkin extension for 
> web-testing
Bug #877796 [wnpp] ITP: libpherkin-extension-weasel-perl - Pherkin extension 
for web-testing
Changed Bug title to 'ITP: libpherkin-extension-weasel-perl -- Pherkin 
extension for web-testing' from 'ITP: libpherkin-extension-weasel-perl - 
Pherkin extension for web-testing'.
> retitle 878152 RFP: Atomsk -- A tool for manipulating and converting atomic 
> data files
Bug #878152 [wnpp] RFP: Atomsk - A tool for manipulating and converting atomic 
data files
Changed Bug title to 'RFP: Atomsk -- A tool for manipulating and converting 
atomic data files' from 'RFP: Atomsk - A tool for manipulating and converting 
atomic data files'.
> retitle 889248 O: golang-github-gogits-cron -- Gogs cron library in Go
Bug #889248 [wnpp] O: golang-github-gogits-cron - Gogs cron library in Go
Changed Bug title to 'O: golang-github-gogits-cron -- Gogs cron library in Go' 
from 'O: golang-github-gogits-cron - Gogs cron library in Go'.
> retitle 889257 O: golang-github-edsrzf-mmap-go -- portable mmap package for Go
Bug #889257 [wnpp] O: golang-github-edsrzf-mmap-go - portable mmap package for 
Go
Changed Bug title to 'O: golang-github-edsrzf-mmap-go -- portable mmap package 
for Go' from 'O: golang-github-edsrzf-mmap-go - portable mmap package for Go'.
> retitle 889478 O: golang-github-blevesearch-bleve -- modern text indexing 
> library for go
Bug #889478 [wnpp] O: golang-github-blevesearch-bleve - modern text indexing 
library for go
Changed Bug title to 'O: golang-github-blevesearch-bleve -- modern text 
indexing library for go' from 'O: golang-github-blevesearch-bleve - modern text 
indexing library for go'.
> retitle 907641 ITP: phosh -- GTK+ based pure Wayland shell for mobile devices
Bug #907641 [wnpp] ITP: phosh - GTK+ based pure Wayland shell for mobile devices
Changed Bug title to 'ITP: phosh -- GTK+ based pure Wayland shell for mobile 
devices' from 'ITP: phosh - GTK+ based pure Wayland shell for mobile devices'.
> retitle 916553 RFP: xgl -- translates Vulkan API commands into PAL commands
Bug #916553 [wnpp] RFP: xgl - translates Vulkan API commands into PAL commands
Changed Bug title to 'RFP: xgl -- translates Vulkan API commands into PAL 
commands' from 'RFP: xgl - translates Vulkan API commands into PAL commands'.
> retitle 924588 ITP: node-sjcl -- Standford Javascript Crypto Library
Bug #924588 [wnpp] ITP: Standford Javascript Crypto Library - sjcl
Changed Bug title to 'ITP: node-sjcl -- Standford Javascript Crypto Library' 
from 'ITP: Standford Javascript Crypto Library - sjcl'.
> retitle 931973 O: libapache2-mod-qos -- quality of service module for the 
> apache2
Bug #931973 [wnpp] O: libapache2-mod-qos - quality of service module for the 
apache2
Changed Bug title to 'O: libapache2-mod-qos -- quality of service module for 
the apache2' from 'O: libapache2-mod-qos - quality of service module for the 
apache2'.
> retitle 736370 ITP: clear-sans -- sharp on-screen sans-serif font
Bug #736370 {Done: Adam Borowski } [wnpp] ITP: clear-sans 
- sharp on-screen sans-serif font
Changed Bug 

Processed: Removed package(s) from unstable

[Debian Bug Tracking System]

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

> reopen 931002
Bug #931002 {Done: Debian FTP Masters } 
[src:rust-coresimd] rust-coresimd: FTBFS (unrecognized platform-specific 
intrinsic function: `x86_rdrand16_step`unrecognized platform-specific intrinsic 
function: `x86_rdrand16_step`)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.1.2-1+rm.
> found 931002 0.1.2-1
Bug #931002 [src:rust-coresimd] rust-coresimd: FTBFS (unrecognized 
platform-specific intrinsic function: `x86_rdrand16_step`unrecognized 
platform-specific intrinsic function: `x86_rdrand16_step`)
Ignoring request to alter found versions of bug #931002 to the same values 
previously set
> fixed 931002 0.1.2-1+rm
Bug #931002 [src:rust-coresimd] rust-coresimd: FTBFS (unrecognized 
platform-specific intrinsic function: `x86_rdrand16_step`unrecognized 
platform-specific intrinsic function: `x86_rdrand16_step`)
The source 'rust-coresimd' and version '0.1.2-1+rm' do not appear to match any 
binary packages
Marked as fixed in versions rust-coresimd/0.1.2-1+rm.
> thanks
Stopping processing here.

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

Processed: Removed package(s) from unstable

[Debian Bug Tracking System]

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

> reopen 931003
Bug #931003 {Done: Debian FTP Masters } 
[src:rust-simd] rust-simd: FTBFS (unrecognized platform-specific intrinsic 
function: `x86_mm_movemask_ps`unrecognized platform-specific intrinsic 
function: `x86_mm_movemask_ps`)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.2.4-1+rm.
> found 931003 0.2.4-1
Bug #931003 [src:rust-simd] rust-simd: FTBFS (unrecognized platform-specific 
intrinsic function: `x86_mm_movemask_ps`unrecognized platform-specific 
intrinsic function: `x86_mm_movemask_ps`)
Ignoring request to alter found versions of bug #931003 to the same values 
previously set
> fixed 931003 0.2.4-1+rm
Bug #931003 [src:rust-simd] rust-simd: FTBFS (unrecognized platform-specific 
intrinsic function: `x86_mm_movemask_ps`unrecognized platform-specific 
intrinsic function: `x86_mm_movemask_ps`)
The source 'rust-simd' and version '0.2.4-1+rm' do not appear to match any 
binary packages
Marked as fixed in versions rust-simd/0.2.4-1+rm.
> thanks
Stopping processing here.

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

Bug#930774: fixed in guile-2.2 2.2.4+1-3

[Santiago Vila]

found 930774 2.2.4+1-2
fixed 930774 2.2.4+1-3
thanks

Bug#934519: fixed in fence-agents 4.4.0-2

[Santiago Vila]

reopen 934519
found 934519 4.0.25-1
fixed 934519 4.4.0-2
thanks

Hi.

Could we please fix this in buster as well?
(for some future point release)

I'm still doing QA on stretch and buster and it's a real pain to find
packages which FTBFS. Please let me know if you need/require/welcome
help for this.

Thanks.

Bug#930774: fixed in guile-2.2 2.2.4+1-3

[Santiago Vila]

reopen 930774
found 2.2.4+1-2
fixed 2.2.4+1-3
thanks

Hi.

Could we please fix this in buster as well?
(for some future point release)

I'm still doing QA on buster and it's a real pain to find packages
which FTBFS. Please let me know if you need/require/welcome help
for this.

Thanks.

Bug#930057: fixed in alot 0.8.1-2

[Santiago Vila]

found 930057 0.8.1-1
fixed 930057 0.8.1-2
thanks

Processed: Re: Bug#930057: fixed in alot 0.8.1-2

[Debian Bug Tracking System]

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

> found 930057 0.8.1-1
Bug #930057 [src:alot] alot: FTBFS because of expired keys
Ignoring request to alter found versions of bug #930057 to the same values 
previously set
> fixed 930057 0.8.1-2
Bug #930057 [src:alot] alot: FTBFS because of expired keys
Marked as fixed in versions alot/0.8.1-2.
> thanks
Stopping processing here.

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

Processed: Re: Bug#930774: fixed in guile-2.2 2.2.4+1-3

[Debian Bug Tracking System]

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

> found 930774 2.2.4+1-2
Bug #930774 [src:guile-2.2] guile-2.2: FTBFS when built with dpkg-buildpackage 
-A
Ignoring request to alter found versions of bug #930774 to the same values 
previously set
> fixed 930774 2.2.4+1-3
Bug #930774 [src:guile-2.2] guile-2.2: FTBFS when built with dpkg-buildpackage 
-A
Marked as fixed in versions guile-2.2/2.2.4+1-3.
> thanks
Stopping processing here.

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

Bug#930057: fixed in alot 0.8.1-2

[Santiago Vila]

reopen 930057
found 0.8.1-1
fixed 0.8.1-2
thanks

Hi.

Could we please fix this in buster as well?
(for some future point release)

I'm still doing QA on buster and it's a real pain to find packages
which FTBFS. Please let me know if you need/require/welcome help
for this.

Thanks.

Processed (with 2 errors): Re: Bug#930774: fixed in guile-2.2 2.2.4+1-3

[Debian Bug Tracking System]

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

> reopen 930774
Bug #930774 {Done: Rob Browning } [src:guile-2.2] 
guile-2.2: FTBFS when built with dpkg-buildpackage -A
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions guile-2.2/2.2.4+1-3.
> found 2.2.4+1-2
Unknown command or malformed arguments to command.
> fixed 2.2.4+1-3
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Processed: Re: Bug#934519: fixed in fence-agents 4.4.0-2

[Debian Bug Tracking System]

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

> reopen 934519
Bug #934519 {Done: Valentin Vidic } [src:fence-agents] 
fence-agents: FTBFS in stretch/buster/sid (ImportError: No module named pywsman)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions fence-agents/4.4.0-2.
> found 934519 4.0.25-1
Bug #934519 [src:fence-agents] fence-agents: FTBFS in stretch/buster/sid 
(ImportError: No module named pywsman)
Ignoring request to alter found versions of bug #934519 to the same values 
previously set
> fixed 934519 4.4.0-2
Bug #934519 [src:fence-agents] fence-agents: FTBFS in stretch/buster/sid 
(ImportError: No module named pywsman)
Marked as fixed in versions fence-agents/4.4.0-2.
> thanks
Stopping processing here.

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

Processed (with 2 errors): Re: Bug#930057: fixed in alot 0.8.1-2

[Debian Bug Tracking System]

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

> reopen 930057
Bug #930057 {Done: Jordan Justen } [src:alot] alot: 
FTBFS because of expired keys
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions alot/0.8.1-2.
> found 0.8.1-1
Unknown command or malformed arguments to command.
> fixed 0.8.1-2
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Processed: Re: Bug#925337: webext-ublock-origin: deactivated with Firefox 66

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #925337 {Done: Markus Koschany } [webext-ublock-origin] 
webext-ublock-origin: deactivated with Firefox 66
Severity set to 'grave' from 'normal'

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

Bug#932076: marked as done (gnome-sound-recorder: Starting gnome-sound-recorder and then trying to play back a (previous) recording results in crash program.)

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 11:03:18 +
with message-id 
and subject line Bug#932076: fixed in gnome-sound-recorder 3.28.2-2
has caused the Debian Bug report #932076,
regarding gnome-sound-recorder: Starting gnome-sound-recorder and then trying 
to play back a (previous) recording results in crash program.
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.)


-- 
932076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-sound-recorder
Version: 3.28.2-1
Severity: normal

Dear Maintainer,

The error is old. There are fixes.
https://gitlab.gnome.org/GNOME/gjs/issues/223

But the error is in a stable release. When will it get to buster?

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

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

Versions of packages gnome-sound-recorder depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  gir1.2-gdkpixbuf-2.0 2.38.1+dfsg-1
ii  gir1.2-glib-2.0  1.58.3-2
ii  gir1.2-gst-plugins-base-1.0  1.14.4-2
ii  gir1.2-gstreamer-1.0 1.14.4-1
ii  gir1.2-gtk-3.0   3.24.5-1
ii  gir1.2-pango-1.0 1.42.4-6
ii  gjs  1.54.3-1
ii  gstreamer1.0-plugins-base1.14.4-2
ii  gstreamer1.0-plugins-good1.14.4-1
ii  gstreamer1.0-pulseaudio  1.14.4-1

gnome-sound-recorder recommends no packages.

gnome-sound-recorder suggests no packages.

-- no debconf information

(org.gnome.SoundRecorder:6732): Gjs-WARNING **: 18:30:29.547: Some code 
accessed the property 'Application' on the module 'application'. That property 
was defined with 'let' or 'const' inside the module. This was previously 
supported, but is not correct according to the ES6 standard. Any symbols to be 
exported from a module must be defined with 'var'. The property access will 
work as previously for the time being, but please fix your code anyway.

(org.gnome.SoundRecorder:6732): Gtk-WARNING **: 18:30:29.548: Locale not 
supported by C library.
Using the fallback 'C' locale.
Gjs-Message: 18:30:29.652: JS LOG: Sound Recorder started
Gjs-Message: 18:30:29.653: JS WARNING: 
[resource:///org/gnome/SoundRecorder/js/application.js 84]: Too many arguments 
to function Gst.init: expected 1, got 2

(org.gnome.SoundRecorder:6732): Gjs-WARNING **: 18:30:29.682: Some code 
accessed the property 'MainWindow' on the module 'mainWindow'. That property 
was defined with 'let' or 'const' inside the module. This was previously 
supported, but is not correct according to the ES6 standard. Any symbols to be 
exported from a module must be defined with 'var'. The property access will 
work as previously for the time being, but please fix your code anyway.

(org.gnome.SoundRecorder:6732): Gjs-WARNING **: 18:30:29.683: Some code 
accessed the property 'AudioProfile' on the module 'audioProfile'. That 
property was defined with 'let' or 'const' inside the module. This was 
previously supported, but is not correct according to the ES6 standard. Any 
symbols to be exported from a module must be defined with 'var'. The property 
access will work as previously for the time being, but please fix your code 
anyway.

(org.gnome.SoundRecorder:6732): Gjs-WARNING **: 18:30:29.683: Some code 
accessed the property 'OffsetController' on the module 'fileUtil'. That 
property was defined with 'let' or 'const' inside the module. This was 
previously supported, but is not correct according to the ES6 standard. Any 
symbols to be exported from a module must be defined with 'var'. The property 
access will work as previously for the time being, but please fix your code 
anyway.

(org.gnome.SoundRecorder:6732): Gjs-WARNING **: 18:30:29.683: Some code 
accessed the property 'DisplayTime' on the module 'fileUtil'. That property was 
defined with 'let' or 'const' inside the module. This was previously supported, 
but is not correct according to the ES6 standard. Any symbols to be exported 
from a module must be defined with 'var'. The property access will work as 
previously for the time being, but please fix your code anyway.

(org.gnome.SoundRecorder:673

Bug#932389: marked as done (gnome-sound-recorder crashes when trying to play back a recording)

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 11:03:18 +
with message-id 
and subject line Bug#932389: fixed in gnome-sound-recorder 3.28.2-2
has caused the Debian Bug report #932389,
regarding gnome-sound-recorder crashes when trying to play back a recording
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.)


-- 
932389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-sound-recorder
Version: 3.28.2-1
Severity: important

Crashes with:
** (org.gnome.SoundRecorder:12342): CRITICAL **: 19:04:35.810: 
g_object_info_get_n_fields: assertion 'info != NULL' failed
**
Gjs:ERROR:gi/object.cpp:481:bool ObjectInstance::field_getter_impl(JSContext*, 
JS::HandleObject, JS::HandleString, JS::MutableHandleValue): assertion failed: 
(field)

Playing back a recording is not possible. Pretty embarrassing for a program 
which has two functions and a default workflow which involves these two 
functions...

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

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

Versions of packages gnome-sound-recorder depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  gir1.2-gdkpixbuf-2.0 2.38.1+dfsg-1
ii  gir1.2-glib-2.0  1.58.3-2
ii  gir1.2-gst-plugins-base-1.0  1.14.4-2
ii  gir1.2-gstreamer-1.0 1.14.4-1
ii  gir1.2-gtk-3.0   3.24.5-1
ii  gir1.2-pango-1.0 1.42.4-6
ii  gjs  1.54.3-1
ii  gstreamer1.0-plugins-base1.14.4-2
ii  gstreamer1.0-plugins-good1.14.4-1
ii  gstreamer1.0-pulseaudio  1.14.4-1

gnome-sound-recorder recommends no packages.

gnome-sound-recorder suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gnome-sound-recorder
Source-Version: 3.28.2-2

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

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gnome-sound-recorder 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 08 Sep 2019 11:15:17 +0100
Source: gnome-sound-recorder
Architecture: source
Version: 3.28.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 932076 932389
Changes:
 gnome-sound-recorder (3.28.2-2) unstable; urgency=medium
 .
   * Team upload
   * d/p/Fix-crashes-when-selecting-a-recording.patch:
 Add upstream patch fixing crashes with versions of gjs that expose
 GtkContainer.widget (Closes: #932076, #932389)
   * d/gbp.conf: Set packaging branch to debian/unstable and upstream
 branch to upstream/3.28.x. The debian/master and upstream/latest
 branches are already in use for versions >= 3.32 in experimental.
Checksums-Sha1:
 962e5da965f1b4c58519edd6768bea1359547c03 2584 gnome-sound-recorder_3.28.2-2.dsc
 6bebe3fa3bd981f42142567d5f2e766b5613aeba 5044 
gnome-sound-recorder_3.28.2-2.debian.tar.xz
 1d31e4ee76e988ff5df3fbcb1358c3f46199decd 15969 
gnome-sound-recorder_3.28.2-2_source.buildinfo
Checksums-Sha256:
 763d75c0892659a8968f3d7d651d42ae968385b83249029655b1a1605d9c5b47 2584 
gnome-sound-recorder_3.28.2-2.dsc
 2322e57bbd1c3c390c6a569fdd8932e7dc7230a446a6ca78dfda4d6c7b70be7b 5044 
gnome-sound-recorder_3.28.2-2.debian.tar.xz
 2f58ad32c4b26cccf0d250a92e8c9b45297fa9b2592a284de3e51d512aab1987 15969 
gnome-sound-recorder_3.28.2-2_source.buildinfo
Files:
 31b94ced576ce0adf5a142c17114f40f 2584 gnome optional 
gnome-sound-recorder_3.28.2-2.dsc
 ac9850eb67e288a181b4e88ac203425d 5044 gno

Bug#939745: python-nameparser: needs a source-only upload

[Esa Peuha]

Source: python-nameparser
Version: 1.0.4-1
Severity: serious

According to the Release Team, maintainer-uploaded binary packages
are no longer allowed to enter testing. Since it's not possible to
binNMU arch:all packages, a source-only upload is needed to get
python3-nameparser built on a buildd.

Bug#939401: nvidia-driver: Xorg crashing in an endless loop after upgrade to version 430

[Luca Boccassi]

On Sat, 2019-09-07 at 14:52 +0100, Luca Boccassi wrote:
> On Wed, 4 Sep 2019 17:20:06 +0200 Andreas Beckmann <
> a...@debian.org
> > wrote:
> > On 04/09/2019 17.15, Niklas Schmidt wrote:
> > >   I tried rebooting with an older kernel to reinstall the
> driver, which did not work. I also tried unplugging my second monitor
> and deleting the xorg.conf file. This didn't help either. I have
> resorted to using the legacy 390 driver for now.
> > Could you try 435.xx from experimental?
> > 
> > Andreas
> 
> Unfortunately I cannot reproduce this on my buster desktop (780gtx).

Ok scratch that, I can reproduce - it's because of the non-glvnd
libraries. With the glvnd one there's no issue, and that's why 435
works - non-glvnd was removed.

Users with optimus/bumblebee should switch to 390xx, and users without
should switch to glvnd with:

sudo apt install nvidia-driver-libs nvidia-driver-libs:i386

Andreas, I think the time has come to force primus-libs to use legacy
drivers only. What do you think?

-- 
Kind regards,
Luca Boccassi


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

Bug#939651: meteo-qt/buster crashes immediately because of changed openweathermap data structure

[Alf Gaida]

Description: Fixes crash after changes of the received data (xml structure)
 * backported from current upstream
 * some minor string changes
 * reflect changed openweathermap datastructure
 * fix crash when wind direction is not available
 * shows UV when available
 * handle download errors and missing values
 * fix logging handling
 * fix crash when 6 days forcast is not available
 * fix crash if applying settings and start minimized
 * catch unhandled exceptions and write them into log file
 * fix crash when UV index has two decimals

Author: Alf Gaida 

---
Bug-Debian: https://bugs.debian.org/939651
Forwarded: not-needed
Last-Update: 2019-09-07

--- meteo-qt-1.0.0.orig/CHANGELOG
+++ meteo-qt-1.0.0/CHANGELOG
@@ -1,3 +1,11 @@
+1.1
+- Option to show the window at start-up
+- Fixes for crashes
+- Show wind info when Bft unit option is unchecked
+- Use unicode arrows for hPa and T° trend
+- Wrap weather information of the day on panel
+- Update translations [German, Slovak, Czech]
+
 1.0.0
 - Automatic detection of the geolocation
 - Reenable UV Ozone in weather information
--- meteo-qt-1.0.0.orig/meteo_qt/about_dlg.py
+++ meteo-qt-1.0.0/meteo_qt/about_dlg.py
@@ -102,7 +102,8 @@ class AboutDialog(QDialog):
 '',
 'werthad '
 'wert...@gmail.com'
-' [hu] Hungarian translation', ''
+' [hu] Hungarian translation',
+''
 )
 + QCoreApplication.translate(
 '',
@@ -129,27 +130,44 @@ class AboutDialog(QDialog):
 'rw4...@yandex.ru'
 'Alexey Zakaldaev '
 'nelex...@gmail.com'
-'Liliya Panova [ru] Russian translation', ''
+'Liliya Panova [ru] Russian translation',
+''
+)
++ QCoreApplication.translate(
+'',
+'jose1711 '
+''
+'jose1...@gmail.com'
+' [sk] Slovak translation, Project',
+''
 )
 + QCoreApplication.translate(
 '',
 'Atilla Öntaş '
 ''
 'tarakbu...@gmail.com'
-' [tr] Turkish translation', ''
+' [tr] Turkish translation',
+''
 )
 + QCoreApplication.translate(
 '',
 'Yuri Chornoivan '
 'yurc...@ukr.net'
-' [uk] Ukrainian translation', ''
+' [uk] Ukrainian translation',
+''
 )
 + QCoreApplication.translate(
 '',
 'You-Cheng Hsieh '
 ''
 'yochenhs...@gmail.com'
-' [zh_TW] Chinese (Taiwan) translation', ''
+' [zh_TW] Chinese (Taiwan) translation',
+''
+)
++ QCoreApplication.translate(
+'',
+'pmav99 Project',
+''
 )
-+ QCoreApplication.translate('', 'pmav99 Project', ''))
+)
 return contributors
--- meteo-qt-1.0.0.orig/meteo_qt/citylistdlg.py
+++ meteo-qt-1.0.0/meteo_qt/citylistdlg.py
@@ -127,7 +127,7 @@ class CityListDlg(QDialog):
 QCoreApplication.translate(
 'Message when trying to remove the'
 'last and unique city in the list',
-'This is the default city !',
+'This is the default city!',
 'Cities list dialogue'
 )
 )
--- meteo-qt-1.0.0.orig/meteo_qt/meteo_qt.py
+++ meteo-qt-1.0.0/meteo_qt/meteo_qt.py
@@ -17,6 +17,9 @@ from lxml import etree
 import json
 import time
 import datetime
+import traceback
+from io import StringIO
+import gc
 
 from PyQt5.QtCore import (
 PYQT_VERSION_STR, QT_VERSION_STR, QCoreApplication, QByteArray,
@@ -143,17 +146,6 @@ class SystemTrayIcon(QMainWindow):
 # The traycolor has to be initialized here for the case when we cannot
 # reach the tray method (case: set the color at first time usage)
 self.traycolor = ''
-self.refresh()
-
-def overviewcity(self):
-temp_trend = ''
-if self.temp_trend == " ↗":
-temp_trend = " "
-elif self.temp_trend == " ↘":
-temp_trend = ""
-
-self.overviewcitydlg = QDialog()
-self.setCentralWidget(self.overviewcitydlg)
 self.days_dico = {'0': self.tr('Mon'),
   '1': self.tr('Tue'),
   '2': self.tr('Wed'),
@@ -169,14 +161,21 @@ class SystemTrayIcon(QMainWindow):
 self.hpa_indications = self.cond.pressure
 self.uv_risk = self.cond.uv_risk
 self.uv_recommend = self.cond.uv_recommend
+
+self.refresh()
+
+def overviewcity(self):
+self.overviewcitydlg = QDialog()
+self.setCent

Bug#935096: marked as done (install-keymap(8) binary not included although package description tells so)

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 10:34:19 +
with message-id 
and subject line Bug#935096: fixed in console-common 0.7.91
has caused the Debian Bug report #935096,
regarding install-keymap(8) binary not included although package description 
tells so
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.)


-- 
935096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: console-common
Version: 0.7.90
Severity: grave
Tags: patch

The "Cleanup d/rules using dh" in the latest version of this package
accidently causes intall-keymap and several other files
(e.g. getkmapchoice.pl) to be left out of the binary package. The
fact, that the console-common package states it installs
install-keymap but does not is the smaller issue. Much more important
is the fact that using kbd-config or more precise 'dpkg-reconfigure
console-data' to configure a console keymap will silently do nothing
instead. That is because console-data checks for existance of
getkmapchoice.pl to check if console-common is installed and simply
skips configuration if not WITHOUT A WARNING.

This patch for the package will fix the issue:

diff -Naur console-common-0.7.90/debian/console-common.files 
console-common-0.7.90+mpi1/debian/console-common.files
--- console-common-0.7.90/debian/console-common.files   2009-07-26 
15:19:59.0 +0200
+++ console-common-0.7.90+mpi1/debian/console-common.files  1970-01-01 
01:00:00.0 +0100
@@ -1,3 +0,0 @@
-usr/sbin
-usr/share/man/man8
-usr/share/console
diff -Naur console-common-0.7.90/debian/console-common.install 
console-common-0.7.90+mpi1/debian/console-common.install
--- console-common-0.7.90/debian/console-common.install 2009-07-26 
15:19:59.0 +0200
+++ console-common-0.7.90+mpi1/debian/console-common.install2019-07-11 
15:43:53.0 +0200
@@ -1 +1,4 @@
 debian/lintian/console-common  usr/share/lintian/overrides
+usr/sbin
+usr/share/man/man8
+usr/share/console


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

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

Versions of packages console-common depends on:
ii  console-data   2:1.12-6
ii  debconf [debconf-2.0]  1.5.71
ii  debianutils4.8.6.1
ii  kbd2.0.4-4
ii  lsb-base   10.2019051400

console-common recommends no packages.

console-common suggests no packages.

-- debconf information excluded
diff -Naur console-common-0.7.90/debian/console-common.files 
console-common-0.7.90+mpi1/debian/console-common.files
--- console-common-0.7.90/debian/console-common.files   2009-07-26 
15:19:59.0 +0200
+++ console-common-0.7.90+mpi1/debian/console-common.files  1970-01-01 
01:00:00.0 +0100
@@ -1,3 +0,0 @@
-usr/sbin
-usr/share/man/man8
-usr/share/console
diff -Naur console-common-0.7.90/debian/console-common.install 
console-common-0.7.90+mpi1/debian/console-common.install
--- console-common-0.7.90/debian/console-common.install 2009-07-26 
15:19:59.0 +0200
+++ console-common-0.7.90+mpi1/debian/console-common.install2019-07-11 
15:43:53.0 +0200
@@ -1 +1,4 @@
 debian/lintian/console-common  usr/share/lintian/overrides
+usr/sbin
+usr/share/man/man8
+usr/share/console
--- End Message ---
--- Begin Message ---
Source: console-common
Source-Version: 0.7.91

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 08 Sep 2019 11:00:28 +0100
Source: console-common
Architecture: source
Version: 0.7.91
Distribution: unstable
Urge

Bug#932389: marked as pending in gnome-sound-recorder

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #932389 in gnome-sound-recorder 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/gnome-sound-recorder/commit/b1bcfb2e5b0b0e6a49cad117d7f539a7bb205f95


Add upstream patch fixing crashes with some versions of gjs

Specifically, this affects versions of gjs that expose GtkContainer.widget.

Closes: #932076
Closes: #932389


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/932389

Processed: Bug#932076 marked as pending in gnome-sound-recorder

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #932076 [gnome-sound-recorder] gnome-sound-recorder: Starting 
gnome-sound-recorder and then trying to play back a (previous) recording 
results in crash program.
Added tag(s) pending.

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

Bug#932076: marked as pending in gnome-sound-recorder

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #932076 in gnome-sound-recorder 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/gnome-sound-recorder/commit/b1bcfb2e5b0b0e6a49cad117d7f539a7bb205f95


Add upstream patch fixing crashes with some versions of gjs

Specifically, this affects versions of gjs that expose GtkContainer.widget.

Closes: #932076
Closes: #932389


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/932076

Processed: Bug#932389 marked as pending in gnome-sound-recorder

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #932389 [gnome-sound-recorder] gnome-sound-recorder crashes when trying to 
play back a recording
Added tag(s) pending.

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

Processed: severity of 932389 is serious, severity of 932076 is serious

[Debian Bug Tracking System]

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

> severity 932389 serious
Bug #932389 [gnome-sound-recorder] gnome-sound-recorder crashes when trying to 
play back a recording
Severity set to 'serious' from 'important'
> severity 932076 serious
Bug #932076 [gnome-sound-recorder] gnome-sound-recorder: Starting 
gnome-sound-recorder and then trying to play back a (previous) recording 
results in crash program.
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#935289: marked as done (qd: FTBFS on ppc64el)

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2019 10:19:44 +
with message-id 
and subject line Bug#935289: fixed in qd 2.3.22+dfsg.1-3
has caused the Debian Bug report #935289,
regarding qd: 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.)


-- 
935289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:qd
version: 2.3.22+dfsg.1-2
severity: serious
tags: ftbfs

Hi,

A binnmu of qd in unstable fails on ppc64el:

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

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: qd
Source-Version: 2.3.22+dfsg.1-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 08 Sep 2019 10:49:51 +0100
Source: qd
Architecture: source
Version: 2.3.22+dfsg.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Closes: 935289
Changes:
 qd (2.3.22+dfsg.1-3) unstable; urgency=medium
 .
   * Standards-Version: 4.4.0
   * Use debhelper-compat (= 12)
   * Build-Depend on gfortran | fortran-compiler, for flang.
   * When compiling with flang, set -fPIC in d/rules
   * Patch from  Frédéric Bonnard for FTBFS on ppc64el.
 Closes: #935289
Checksums-Sha1:
 fa4cefe546008397bf408075cfe8047475821d70 2129 qd_2.3.22+dfsg.1-3.dsc
 501b3495ee354460beb4ff606db92006d64fed76 52060 qd_2.3.22+dfsg.1-3.debian.tar.xz
Checksums-Sha256:
 0369392355f2a57900d6747a59a34c07dc2fde81c607a9a66d63edbd2f633fef 2129 
qd_2.3.22+dfsg.1-3.dsc
 8bb4bc4928180da9f2936799c3baf122fa519dc3f65d0052f26a585a233c46c6 52060 
qd_2.3.22+dfsg.1-3.debian.tar.xz
Files:
 ca05b664e3dbe0ba7fdb97756dfda630 2129 libs optional qd_2.3.22+dfsg.1-3.dsc
 95adf0aa39b7c8e2535ec130dc077b44 52060 libs optional 
qd_2.3.22+dfsg.1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl100FcACgkQy+a7Tl2a
06WAdhAAmW/yoS6WGs9GEqhKDqVkO3U/iOm0wEBwrgUjx+NJWhelk0SLturiVNlK
I2Ry190xOoZA0SoVb8KTQdOHjF3QVnh7NaHxp90BkGKEtRl4h0Nh6tlivWqT+bzk
54CiVx4qMKbQlK3MzxsjJyT0NsFnx5erzvEZOYGCTCYiYIMhqOSS8El+J2z4E5BF
qIMtnsghqedSj/htLHIW5KY5EENoQAc/96kFvJuDFyeXIWBWmKcGUTVbUSH7gyls
V1641Yw5LR6gmGMIN0BbgsexG6l90EHSSaSKYaOzZESBONCBwTkdUw3I5Z633I7K
M+iUHLJbGRrMiKPTLolQPV4EGxkCRvUP1hvavTaAGZ4/w40RUL4eQa6RECHwOwCF
JVP46iAI4GRROB51FcXaFBqbEeGk1GySpUiHXELn36Q+Lk9b+11OW1//kDp05W41
3GJt8mvvuTuQF3GM6bUl9nNRW8OjzW+wYeDbQPVVQnAaarl+3HTO79Zwz28FqsK2
mAYSd9XvLFYZbQsOTl0dSBl70Ko2FA0+DHqMKrwZoYknDIcHd8ZCF15Lv22dTAoN
bu+EFt0EXMrYiZLXv8c3qjOinFDgtdyvMJz85JxOPBypY8aUM/VRg4OqPPsuAeF4
TzheBKnp8yNBQKd+YOqWuL6VBlEZqoSCByJwTq74avpbkAIGccw=
=Hwsi
-END PGP SIGNATURE End Message ---