Bug#942135: Сannot install Perl 5.30.0-6 without deleting the libgtk2-perl package

[intrigeri]

Hi,

Сергей Фёдоров:
> Tags: a11y

I've just noticed that you've set the a11y tag.

I would like to understand why: is there any important universal
access technology that still depends on libgtk2-perl?

If that's the case, then it matters to me and I'd like to take this
into account.

Cheers,
-- 
intrigeri

Processed: Re: Bug#942135: Сannot install Perl 5.30.0-6 without deleting the libgtk2-perl package

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://gitlab.gnome.org/GNOME/perl-gtk2/issues/3
Bug #942135 [src:libgtk2-perl] libgtk2-perl: FTBFS and not built against perl 
5.30
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/perl-gtk2/issues/3'.
> tag -1 + upstream
Bug #942135 [src:libgtk2-perl] libgtk2-perl: FTBFS and not built against perl 
5.30
Added tag(s) upstream.
> retitle -1 libgtk2-perl: FTBFS with gdk-pixbuf 2.39+ and not built against 
> perl 5.30
Bug #942135 [src:libgtk2-perl] libgtk2-perl: FTBFS and not built against perl 
5.30
Changed Bug title to 'libgtk2-perl: FTBFS with gdk-pixbuf 2.39+ and not built 
against perl 5.30' from 'libgtk2-perl: FTBFS and not built against perl 5.30'.
> severity -1 serious
Bug #942135 [src:libgtk2-perl] libgtk2-perl: FTBFS with gdk-pixbuf 2.39+ and 
not built against perl 5.30
Severity set to 'serious' from 'important'

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

Bug#942161: src:impacket: Substantial issues with debian/copyright

[Scott Kitterman]

Package: src:impacket
Version: 0.9.15-5
Severity: serious
Justification: Policy 2.5

This is at least in part a problem in the existing package, so I am not
going to reject the package for this, but it should definitely be fixed.
The following significant issues need review/update in debian/copyright:

Copyright 2018-2019 SecureAuth Corporation vice CORE Security Technologies for 
most, but not all code.

Missing license:
examples/kintercept.py:# Copyright (c) 2019 Isaac Boukris 
impacket/examples/remcomsvc.py:# Copyright (c) 2006 Talha Tariq [ 
talha.ta...@gmail.com ]
iimpacket/krb5/asn1.py:# Copyright (c) 2013, Marc Horowitz
impacket/krb5/types.py:# Copyright (c) 2013, Marc Horowitz
impacket/krb5/crypto.py:# Copyright (C) 2013 by the Massachusetts Institute of 
Technology.
impacket/smb.py:# Copyright (C) 2001 Michael Teo 
tests/htmlcov/jquery.hotkeys.js: * Copyright 2010, John Resig
tests/htmlcov/jquery.ba-throttle-debounce.min.js: * Copyright (c) 2010 "Cowboy" 
Ben Alman
tests/dot11/test_wps.py:# Copyright (c) 2003-2013 CORE Security Technologies

Missing copyright attribution
impacket/dcerpc/v5/even6.py:# Copyright (c) 2017 @MrAnde7son

Scott K

Bug#941638: docopt: diff for NMU version 0.6.2-2.1

[anarcat]

Control: tags 941638 + pending

Dear maintainer,

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

Regards.
diff -Nru docopt-0.6.2/debian/changelog docopt-0.6.2/debian/changelog
--- docopt-0.6.2/debian/changelog	2018-08-17 10:16:51.0 -0400
+++ docopt-0.6.2/debian/changelog	2019-10-11 00:57:20.0 -0400
@@ -1,3 +1,16 @@
+docopt (0.6.2-2.1) unstable; urgency=medium
+
+  [ Matthias Klose ]
+  * Don't run the Python2 autopkg tests. python-schema is gone.
+
+  [ Ondřej Nový ]
+  * d/copyright: Use https protocol in Format field
+
+  [ Antoine Beaupré ]
+  * Non-maintainer upload to ship Klose's patch (Closes: #941638)
+
+ -- Antoine Beaupré   Fri, 11 Oct 2019 00:57:20 -0400
+
 docopt (0.6.2-2) unstable; urgency=medium
 
   * [d/control] Remove obsolete X-Python-Version
diff -Nru docopt-0.6.2/debian/copyright docopt-0.6.2/debian/copyright
--- docopt-0.6.2/debian/copyright	2018-08-17 10:16:51.0 -0400
+++ docopt-0.6.2/debian/copyright	2019-10-11 00:57:20.0 -0400
@@ -1,4 +1,4 @@
-Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: docopt
 Upstream-Contact: Vladimir Keleshev 
 Source: https://github.com/docopt/docopt
diff -Nru docopt-0.6.2/debian/gitlab-ci.yml docopt-0.6.2/debian/gitlab-ci.yml
--- docopt-0.6.2/debian/gitlab-ci.yml	2018-08-17 10:16:51.0 -0400
+++ docopt-0.6.2/debian/gitlab-ci.yml	2019-10-11 00:57:20.0 -0400
@@ -1,71 +1,16 @@
-# Warning! This file is autogenerated by salsa pipeline bot. Any change made
-# over this document will be lost. Customization and changes must be made over
-# the template yaml.
-variables:
-  DEBFULLNAME: "Salsa Pipeline"
-  DEBEMAIL: ""
-  DEBIAN_FRONTEND: noninteractive
-  WORKING_DIR: ./debian/output
+include: https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml
 
-stages:
-  - build
-  - test
+build:
+extends: .build-unstable
 
-image: debian:unstable
+reprotest:
+extends: .test-reprotest
 
-build package:
-  stage: build
-  image: registry.salsa.debian.org/salsa-ci-team/images/gbp
-  artifacts:
-expire_in: 180 day
-name: "$CI_BUILD_NAME"
-paths:
-- ${WORKING_DIR}/
-  script:
-- apt-get update
-- eatmydata apt-get build-dep -y .
-- gbp pull --ignore-branch
-- gbp buildpackage --git-ignore-branch --git-export-dir=${WORKING_DIR} -us -uc
+lintian:
+extends: .test-lintian
 
-run autopkgtest:
-  stage: test
-  image: registry.salsa.debian.org/salsa-ci-team/images/autopkgtest
-  script:
-- eatmydata autopkgtest -U ${WORKING_DIR}/*.deb -- null
+autopkgtest:
+extends: .test-autopkgtest
 
-run lintian:
-  stage: test
-  image: registry.salsa.debian.org/salsa-ci-team/images/lintian
-  script:
-- lintian -iI ${WORKING_DIR}/*.changes
-
-run reprotest:
-  stage: test
-  image: registry.salsa.debian.org/salsa-ci-team/images/reprotest
-  artifacts:
-name: "$CI_BUILD_NAME"
-expire_in: 180 day
-paths:
-  - ./reprotest.log
-when: always
-  script:
-- apt-get update
-- eatmydata apt-get build-dep -y .
-- export DEB_BUILD_OPTIONS=nocheck
-- eatmydata reprotest . -- null &> reprotest.log
-
-run piuparts:
-  stage: test
-  image: registry.salsa.debian.org/salsa-ci-team/images/piuparts
-  services:
-- docker:dind
-  script:
-- CHROOT_PATH=/tmp/debian-unstable
-- CONTAINER_ID=$(docker run --rm -d debian:unstable sleep infinity)
-- docker exec ${CONTAINER_ID} bash -c "apt-get update && apt-get install eatmydata -y"
-- mkdir -p ${CHROOT_PATH}
-- docker export ${CONTAINER_ID} | tar -C ${CHROOT_PATH} -xf -
-- mknod -m 666 ${CHROOT_PATH}/dev/urandom c 1 9
-- piuparts --hard-link -e ${CHROOT_PATH} ${WORKING_DIR}/*.deb
-# End of include
- Below starts the local customization ###
+piuparts:
+extends: .test-piuparts
diff -Nru docopt-0.6.2/debian/gitlab-ci.yml.tpl docopt-0.6.2/debian/gitlab-ci.yml.tpl
--- docopt-0.6.2/debian/gitlab-ci.yml.tpl	2018-08-17 10:16:51.0 -0400
+++ docopt-0.6.2/debian/gitlab-ci.yml.tpl	1969-12-31 19:00:00.0 -0500
@@ -1,3 +0,0 @@
-include: https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml
-
-# end of salsa pipeline bot parser
diff -Nru docopt-0.6.2/debian/tests/control docopt-0.6.2/debian/tests/control
--- docopt-0.6.2/debian/tests/control	2018-08-17 10:16:51.0 -0400
+++ docopt-0.6.2/debian/tests/control	2019-10-11 00:57:20.0 -0400
@@ -2,5 +2,3 @@
 Depends: @,
  python3-pytest,
  python3-schema,
- python-pytest,
- python-schema,
diff -Nru docopt-0.6.2/debian/tests/run_examples docopt-0.6.2/debian/tests/run_examples
--- docopt-0.6.2/debian/tests/run_examples	2018-08-17 10:16:51.0 -0400
+++ docopt-0.6.2/debian/tests/run_examples	2019-10-11 00:57:20.

Processed: docopt: diff for NMU version 0.6.2-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 941638 + pending
Bug #941638 [src:docopt] autopkg tests still rely on removed python-schema
Added tag(s) pending.

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

Bug#912894: marked as done (odot: Depends on libgtk2-perl, that won't be part of Bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 11 Oct 2019 05:07:14 +
with message-id 
and subject line Bug#942153: Removed package(s) from unstable
has caused the Debian Bug report #912894,
regarding odot: Depends on libgtk2-perl, that won't be part of 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.)


-- 
912894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912894
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: odot
Severity: normal
User: debian-p...@lists.debian.org
Usertags: gtk2-removal

Hi!

This package depends on libgtk2-perl, that I intend to remove
from testing soon after the Buster release, and then from sid at
some later point during the Bullseye development cycle:

   https://bugs.debian.org/912860

Please get in touch with the upstream project and suggest they
port this application to libgtk3-perl. I've personally ported
a couple Perl GTK+ apps from 2.x to 3.x and it's rather
straightforward. Upstream for the GTK+ 3 and GObject
Introspection Perl bindings is responsive and happy to add
missing bits to the bindings.

This being said, the package was orphaned last year and the current
"votes" count on popcon is 2. So I think should remove it from the
archive if/once it's clear that it won't be ported to GTK+ 3.

Cheers!
-- 
intrigeri
--- End Message ---
--- Begin Message ---
Version: 1.3.0-0.1+rm

Dear submitter,

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

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

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

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

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

Bug#894858: marked as done (gui-apt-key: Missing package relation with menu)

[Debian Bug Tracking System]

Your message dated Fri, 11 Oct 2019 05:07:42 +
with message-id 
and subject line Bug#942156: Removed package(s) from unstable
has caused the Debian Bug report #894858,
regarding gui-apt-key: Missing package relation with menu
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.)


-- 
894858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gui-apt-key
Version: 0.4-2.2
Severity: important
Tags: newcomer

Package should Depend on the menu package as it calls `su-to-root`, which that
package provides. Attempting to run the program without that binary in place
causes it to fail with an error.



-- System Information:
Debian Release: stretch/sid
  APT prefers artful-updates
  APT policy: (500, 'artful-updates'), (500, 'artful-security'), (500, 
'artful'), (100, 'artful-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages gui-apt-key depends on:
ii  libgtk2-perl2:1.24992-1build1
ii  liblocale-gettext-perl  1.07-3build2

gui-apt-key recommends no packages.

gui-apt-key suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.4-2.2+rm

Dear submitter,

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

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

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

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

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

Bug#912890: marked as done (pidgin-openpgp: Depends on libgtk2-perl, that won't be part of Bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 11 Oct 2019 05:06:46 +
with message-id 
and subject line Bug#942152: Removed package(s) from unstable
has caused the Debian Bug report #912890,
regarding pidgin-openpgp: Depends on libgtk2-perl, that won't be part of 
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.)


-- 
912890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pidgin-openpgp
Severity: normal
User: debian-p...@lists.debian.org
Usertags: gtk2-removal

Hi!

This package depends on libgtk2-perl, that I intend to remove
from testing soon after the Buster release, and then from sid at
some later point during the Bullseye development cycle:

   https://bugs.debian.org/912860

Please get in touch with the upstream project and suggest they
port this application to libgtk3-perl. I've personally ported
a couple Perl GTK+ apps from 2.x to 3.x and it's rather
straightforward. Upstream for the GTK+ 3 and GObject
Introspection Perl bindings is responsive and happy to add
missing bits to the bindings.

Additionally, I notice that:

 - This package was orphaned back in 2012.

 - Upstream seems to be… a code dump in a Pidgin upstream ticket
   comment: https://developer.pidgin.im/ticket/288
   So perhaps my suggestion to contact upstream is kind of moot :/

 - There are other options for this use case nowadays, such as OTR,
   which are probably better for most use cases.

So perhaps it would be best to remove this package from Debian.

Cheers!
-- 
intrigeri
--- End Message ---
--- Begin Message ---
Version: 0.1-2+rm

Dear submitter,

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

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

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

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

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

Bug#912877: marked as done (gui-apt-key: Depends on libgtk2-perl, that won't be part of Bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 11 Oct 2019 05:07:42 +
with message-id 
and subject line Bug#942156: Removed package(s) from unstable
has caused the Debian Bug report #912877,
regarding gui-apt-key: Depends on libgtk2-perl, that won't be part of 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.)


-- 
912877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gui-apt-key
Severity: normal
X-Debbugs-Cc: Axel Beckert 
User: debian-p...@lists.debian.org
Usertags: gtk2-removal

Hi!

This package depends on libgtk2-perl, that I intend to remove
from testing soon after the Buster release, and then from sid at
some later point during the Bullseye development cycle:

   https://bugs.debian.org/912860

Please get in touch with the upstream project and suggest they
port this application to libgtk3-perl. I've personally ported
a couple Perl GTK+ apps from 2.x to 3.x and it's rather
straightforward. Upstream for the GTK+ 3 and GObject
Introspection Perl bindings is responsive and happy to add
missing bits to the bindings.

This being said, I notice that this package is RC-buggy, not in
testing currently, and the last maintainer upload was 10 years ago.
So Cc'ing Axel, who did the last upload, in case he's interested to
take the lead here :) Otherwise, I think the best course of action
will be to remove this package from the archive.

Cheers!
-- 
intrigeri
--- End Message ---
--- Begin Message ---
Version: 0.4-2.2+rm

Dear submitter,

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

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

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

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

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

Bug#933476: marked as done (stx-btree: Please rebuild against wxWidgets GTK 3 package)

[Debian Bug Tracking System]

Your message dated Fri, 11 Oct 2019 05:04:40 +
with message-id 
and subject line Bug#941177: Removed package(s) from unstable
has caused the Debian Bug report #933476,
regarding stx-btree: Please rebuild against wxWidgets GTK 3 package
to be marked as done.

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

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


-- 
933476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933476
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: stx-btree
Severity: normal

Hi,

Your package appears to be using the wxWidgets GTK 2 implementation.  In 
Debian, we have had a GTK 3 implementation of wxWidgets for some time.  
For the bullseye release, the wxWidgets package maintainers plan to 
remove the GTK 2 version, so we kindly request that you switch your 
package to use the GTK 3 version.  We have a transition tracker [1] 
setup to track progress.

Switching to the GTK 3 version may be as simple as:
1) Update your Build-Depends
   libwxgtk3.0-dev -> libwxgtk3.0-gtk3-dev
   libwxgtk-media3.0-dev -> libwxgtk-media3.0-gtk3-dev
2) Rebuild
3) Test

If everything seems to be working fine, that's probably all you need to do.

There are a couple of known issues:
1) If your package uses wxGLCanvas, this doesn't currently work when running
under Wayland.  As a workaround, you can force use of X.  See bug: [2]
2) If your package uses graphics contexts, it may encounter a problem with
coordinate overflow.  See bug: [3]

If you have any questions, or need assistance with the conversion, please
contact the wxWidgets team, team...@tracker.debian.org.

[1] https://release.debian.org/transitions/html/wxwidgets3.0-gtk3.html
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900678
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906060
--- End Message ---
--- Begin Message ---
Version: 0.9-2+rm

Dear submitter,

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

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

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

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

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

Bug#933466: marked as done (rapidsvn: Please rebuild against wxWidgets GTK 3 package)

[Debian Bug Tracking System]

Your message dated Fri, 11 Oct 2019 05:05:08 +
with message-id 
and subject line Bug#941178: Removed package(s) from unstable
has caused the Debian Bug report #933466,
regarding rapidsvn: Please rebuild against wxWidgets GTK 3 package
to be marked as done.

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

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


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

Hi,

Your package appears to be using the wxWidgets GTK 2 implementation.  In 
Debian, we have had a GTK 3 implementation of wxWidgets for some time.  
For the bullseye release, the wxWidgets package maintainers plan to 
remove the GTK 2 version, so we kindly request that you switch your 
package to use the GTK 3 version.  We have a transition tracker [1] 
setup to track progress.

Switching to the GTK 3 version may be as simple as:
1) Update your Build-Depends
   libwxgtk3.0-dev -> libwxgtk3.0-gtk3-dev
   libwxgtk-media3.0-dev -> libwxgtk-media3.0-gtk3-dev
2) Rebuild
3) Test

If everything seems to be working fine, that's probably all you need to do.

There are a couple of known issues:
1) If your package uses wxGLCanvas, this doesn't currently work when running
under Wayland.  As a workaround, you can force use of X.  See bug: [2]
2) If your package uses graphics contexts, it may encounter a problem with
coordinate overflow.  See bug: [3]

If you have any questions, or need assistance with the conversion, please
contact the wxWidgets team, team...@tracker.debian.org.

[1] https://release.debian.org/transitions/html/wxwidgets3.0-gtk3.html
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900678
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906060
--- End Message ---
--- Begin Message ---
Version: 0.12.1dfsg-3.1+rm

Dear submitter,

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

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

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

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

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

Bug#886835: marked as done (RM: sitplus -- RoM; very low popcon; broken)

[Debian Bug Tracking System]

Your message dated Fri, 11 Oct 2019 05:04:11 +
with message-id 
and subject line Bug#886835: Removed package(s) from unstable
has caused the Debian Bug report #886835,
regarding RM: sitplus -- RoM; very low popcon; broken
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.)


-- 
886835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886835
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sitplus
Version: 1.0.3-5.1+b3
Severity: grave
Justification: renders package unusable

Hi,

running sitplus results in:

$ sitplus

(sitplus:4537): Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and 
GTK+ 3 in the same process is not supported
fish: 'sitplus' terminated by signal SIGTRAP (Trace or breakpoint trap)

which seems to be correct:

$ ldd /usr/bin/sitplus  | grep gtk
libwx_gtk2u_core-3.0.so.0 => 
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0 (0x7f735596c000)
libwx_gtk2u_html-3.0.so.0 => 
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_html-3.0.so.0 (0x7f73551f9000)
libgtk-3.so.0 => /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7f7351d74000)
libgtk-x11-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 
(0x7f734ece1000)

this makes the package unusable, hence the severity.

Cheers Jochen

P.S.: I'm not really using the software, just found this during tests of
a security upload of libpoco. Installing from wheezy works.

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

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

Versions of packages sitplus depends on:
ii  libbluetooth3   5.47-1+b1
ii  libboost-filesystem1.62.0   1.62.0+dfsg-5
ii  libboost-program-options1.62.0  1.62.0+dfsg-5
ii  libboost-system1.62.0   1.62.0+dfsg-5
ii  libboost-thread1.62.0   1.62.0+dfsg-5
ii  libc6   2.26-2
ii  libconfig9  1.5-0.4
ii  libgcc1 1:7.2.0-19
ii  libopencv-calib3d3.23.2.0+dfsg-4+b3
ii  libopencv-contrib3.23.2.0+dfsg-4+b3
ii  libopencv-core3.2   3.2.0+dfsg-4+b3
ii  libopencv-features2d3.2 3.2.0+dfsg-4+b3
ii  libopencv-flann3.2  3.2.0+dfsg-4+b3
ii  libopencv-highgui3.23.2.0+dfsg-4+b3
ii  libopencv-imgcodecs3.2  3.2.0+dfsg-4+b3
ii  libopencv-imgproc3.23.2.0+dfsg-4+b3
ii  libopencv-ml3.2 3.2.0+dfsg-4+b3
ii  libopencv-objdetect3.2  3.2.0+dfsg-4+b3
ii  libopencv-photo3.2  3.2.0+dfsg-4+b3
ii  libopencv-shape3.2  3.2.0+dfsg-4+b3
ii  libopencv-stitching3.2  3.2.0+dfsg-4+b3
ii  libopencv-superres3.2   3.2.0+dfsg-4+b3
ii  libopencv-video3.2  3.2.0+dfsg-4+b3
ii  libopencv-videoio3.23.2.0+dfsg-4+b3
ii  libopencv-videostab3.2  3.2.0+dfsg-4+b3
ii  libopencv-viz3.23.2.0+dfsg-4+b3
ii  libpocofoundation50 1.8.0.1-1
ii  libpocoxml501.8.0.1-1
ii  libportmidi01:217-6
ii  libsdl-gfx1.2-5 2.0.25-9
ii  libsdl-image1.2 1.2.12-7
ii  libsdl1.2debian 1.2.15+dfsg2-0.1
ii  libstdc++6  7.2.0-19
ii  libv4l-01.14.1-1
ii  libwxbase3.0-0v53.0.3.1+dfsg2-1
ii  libwxgtk3.0-0v5 3.0.3.1+dfsg2-1
ii  libx11-62:1.6.4-3
ii  libxtst62:1.2.3-1
ii  pd-cyclone  0.2~beta3-2
ii  pd-freeverb 1.2-3
ii  pd-iemnet   0.2.1-1
ii  pd-libdir   1.11-1
ii  pd-list-abs 0.1-2
ii  puredata0.48.1-1
ii  sitplus-data1.0.3-5.1

sitplus recommends no packages.

sitplus suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   sitplus |  1.0.3-5.1 | source
   sitplus | 1.0.3-5.1+b7 | amd64, arm64, armel, armhf, i386, mipsel, ppc64el, 
s390x
   sitplus | 1.0.3-5.1+b8 | mips64el
sitplus-data |  1.0.3-5.1 | all

--- Reason ---
RoM; very low popcon; broken

Bug#933424: marked as done (sitplus: Please rebuild against wxWidgets GTK 3 package)

[Debian Bug Tracking System]

Your message dated Fri, 11 Oct 2019 05:04:18 +
with message-id 
and subject line Bug#886835: Removed package(s) from unstable
has caused the Debian Bug report #933424,
regarding sitplus: Please rebuild against wxWidgets GTK 3 package
to be marked as done.

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

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


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

Hi,

Your package appears to be using the wxWidgets GTK 2 implementation.  In 
Debian, we have had a GTK 3 implementation of wxWidgets for some time.  
For the bullseye release, the wxWidgets package maintainers plan to 
remove the GTK 2 version, so we kindly request that you switch your 
package to use the GTK 3 version.  We have a transition tracker [1] 
setup to track progress.

Switching to the GTK 3 version may be as simple as:
1) Update your Build-Depends
   libwxgtk3.0-dev -> libwxgtk3.0-gtk3-dev
   libwxgtk-media3.0-dev -> libwxgtk-media3.0-gtk3-dev
2) Rebuild
3) Test

If everything seems to be working fine, that's probably all you need to do.

There are a couple of known issues:
1) If your package uses wxGLCanvas, this doesn't currently work when running
under Wayland.  As a workaround, you can force use of X.  See bug: [2]
2) If your package uses graphics contexts, it may encounter a problem with
coordinate overflow.  See bug: [3]

If you have any questions, or need assistance with the conversion, please
contact the wxWidgets team, team...@tracker.debian.org.

[1] https://release.debian.org/transitions/html/wxwidgets3.0-gtk3.html
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900678
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906060
--- End Message ---
--- Begin Message ---
Version: 1.0.3-5.1+rm

Dear submitter,

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

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

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

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

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

Bug#940973: libarchive-zip-perl breaks strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember

[tony mancill]

On Thu, Oct 10, 2019 at 05:53:57PM +0200, gregor herrmann wrote:
> On Thu, 10 Oct 2019 06:30:52 -0700, tony mancill wrote:
> > >jh_classpath
> > > error: No member named $memberName 
> > >  at /usr/share/perl5/Archive/Zip/Archive.pm line 411.
> > >   
> > > Archive::Zip::Archive::contents(Archive::Zip::Archive=HASH(0x55bbbdadedd0),
> > >  "META-INF/MANIFEST.MF") called at /usr/bin/jh_manifest line 297
> > >   main::update_jar("/<>/debian/li"..., undef) called at 
> > > /usr/bin/jh_manifest line 147
> > > Could not read manifest from 
> > > /<>/debian/libquartz2-java/usr/share/java/quartz2-2.3.0.jar 
> > > (2):  at /usr/bin/jh_manifest line 298.
> > > jh_classpath: jh_manifest -plibquartz2-java 
> > > --classpath=/usr/share/java/slf4j-api.jar 
> > > debian/libquartz2-java/usr/share/java/quartz2.jar returned exit code 255
> > > make: *** [debian/rules:4: binary] Error 255
> > 
> > I don't know if this is the same issue but wanted to mention it here,
> > since it seems potentially related.  I'd be glad to provide more
> > debugging information or testing if that would help.  libquartz2-java is
> > an example of a source package that exhibits this issue.
> 
> Salvatore has uploaded libarchive-zip-perl 1.67-1 right now. Could
> you try and check with this version? If there's still a problem I'm
> happy to debug this together and forward it upstream.

Hi Gregor,

The behavior is the same with 1.67-1.  I'll have some time to look into
it in more detail this weekend.

Thanks,
tony


signature.asc
Description: PGP signature

Bug#942118: marked as done (SysV: fails to restart during upgrade, breaks dpkg)

[Debian Bug Tracking System]

Your message dated Fri, 11 Oct 2019 03:34:22 +
with message-id 
and subject line Bug#942118: fixed in smartmontools 7.0-2
has caused the Debian Bug report #942118,
regarding SysV: fails to restart during upgrade, breaks dpkg
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.)


-- 
942118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: smartmontools
Version: 7.0-1
Severity: grave
Justification: renders package unusable

[…]
(Reading database ... 302786 files and directories currently installed.)
Preparing to unpack .../00-smartmontools_7.0-1_amd64.deb ...
Unpacking smartmontools (7.0-1) over (6.6-1+b1) ...
[…]
Setting up smartmontools (7.0-1) ...
Installing new version of config file /etc/default/smartmontools ...
Installing new version of config file /etc/init.d/smartmontools ...
Installing new version of config file /etc/smartd.conf ...
Removing obsolete conffile /etc/smartmontools/run.d/10powersave-notify ...
insserv: warning: current stop runlevel(s) (1) of script `smartmontools' 
overrides LSB defaults (0 1 6).
Restarting S.M.A.R.T. daemon: smartd failed!
invoke-rc.d: initscript smartmontools, action "restart" failed.
dpkg: error processing package smartmontools (--configure):
 installed smartmontools package post-installation script subprocess returned 
error exit status 1
[…]
Errors were encountered while processing:
 smartmontools
E: Sub-process /usr/bin/dpkg returned an error code (1)
100|root@ci-busyapps:~ # dpkg -a --configure
Setting up smartmontools (7.0-1) ...
insserv: warning: current stop runlevel(s) (1) of script `smartmontools' 
overrides LSB defaults (0 1 6).
Restarting S.M.A.R.T. daemon: smartd failed!
invoke-rc.d: initscript smartmontools, action "restart" failed.
dpkg: error processing package smartmontools (--configure):
 installed smartmontools package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 smartmontools



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

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

Versions of packages smartmontools depends on:
ii  debianutils  4.9
ii  init-system-helpers  1.57
ii  libc62.29-2
ii  libcap-ng0   0.7.9-2+b1
ii  libgcc1  1:9.2.1-9
ii  libselinux1  2.9-2+b2
ii  libstdc++6   9.2.1-9
ii  libsystemd0  242-7
ii  lsb-base 11.1.0

smartmontools recommends no packages.

Versions of packages smartmontools suggests:
ii  bsd-mailx [mailx]  8.1.2-0.20180807cvs-1+b1
ii  curl   7.66.0-1
ii  gpg2.2.17-3
pn  gsmartcontrol  
ii  lynx   2.9.0dev.4-1
pn  smart-notifier 
ii  wget   1.20.3-1+b1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: smartmontools
Source-Version: 7.0-2

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated smartmontools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 Oct 2019 14:05:51 +1100
Source: smartmontools
Architecture: source
Version: 7.0-2
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Closes: 942118
Changes:
 smartmontools (7.0-2) unstable; urgency=medium
 .
   * SysV: don't (re)start daemon during upgrade (Closes: #942118).
   * rules/configure: detect systemd automatically.
   * Build-Depends:
 = libsystemd-dev [!kfreebsd-any]
Checksums-Sha1:
 db575c6f432d988540cd59dbdc57d226c1701b02 2188 smartmontools_7.0-2.dsc
 215f6fd1b602a92edea1b83760fb43c692ef3cbe 35948 
smartmontools_7.0-2.debian.tar.xz
 783334f0047682f0c369c01965b4a8c6723ac553 6135 
smartmontools_7.0-2_amd64.

Bug#942118: marked as pending in smartmontools

[Dmitry Smirnov]

Control: tag -1 pending

Hello,

Bug #942118 in smartmontools 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/debian/smartmontools/commit/1ca63ecf8f2d47ca6043850bee1605645d35fd7e


SysV: don't (re)start daemon during upgrade (Closes: #942118).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/942118

Processed: Bug#942118 marked as pending in smartmontools

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #942118 [smartmontools] SysV: fails to restart during upgrade, breaks dpkg
Added tag(s) pending.

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

Processed: retitle 942118 to SysV: fails to restart during upgrade, breaks dpkg

[Debian Bug Tracking System]

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

> retitle 942118 SysV: fails to restart during upgrade, breaks dpkg
Bug #942118 [smartmontools] smartmontools: fails to restart during upgrade, 
breaks dpkg
Changed Bug title to 'SysV: fails to restart during upgrade, breaks dpkg' from 
'smartmontools: fails to restart during upgrade, breaks dpkg'.
> thanks
Stopping processing here.

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

Bug#941756: marked as done (python3-git: trying to overwrite '/usr/share/doc/python-git/_static/jquery.js', which is also in package python-git 2.1.11-1)

[Debian Bug Tracking System]

Your message dated Fri, 11 Oct 2019 03:04:01 +
with message-id 
and subject line Bug#941756: fixed in python-git 3.0.3-3
has caused the Debian Bug report #941756,
regarding python3-git: trying to overwrite 
'/usr/share/doc/python-git/_static/jquery.js', which is also in package 
python-git 2.1.11-1
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.)


-- 
941756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-git
Version: 3.0.1-1
Severity: serious
Control: found -1 3.0.3-1

Hi,

upgrading python3-git from 2.1.11-1 to 3.0.1-1 or 3.0.3-1 fails as
follows if python-git is still installed:

Unpacking python3-git (3.0.3-1) over (2.1.11-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/python3-git_3.0.3-1_all.deb (--unpack):
 trying to overwrite '/usr/share/doc/python-git/_static/jquery.js', which is 
also in package python-git 2.1.11-1

There seem to be either according Breaks and Replaces headers missing or
that file has been included in python3-git by accident.

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

Kernel: Linux 5.3.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages python3-git depends on:
ii  git [git-core]  1:2.23.0-1
ii  python3 3.7.5-1
ii  python3-gitdb   2.0.6-1

python3-git recommends no packages.

Versions of packages python3-git suggests:
pn  python-git-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python-git
Source-Version: 3.0.3-3

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

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

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

Debian distribution maintenance software
pp.
TANIGUCHI Takaki  (supplier of updated python-git package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 Oct 2019 11:52:29 +0900
Source: python-git
Architecture: source
Version: 3.0.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: TANIGUCHI Takaki 
Closes: 941756
Changes:
 python-git (3.0.3-3) unstable; urgency=medium
 .
   * Add python-git to Breaks and Replaces to fix file conflict (Closes: 
#941756)
Checksums-Sha1:
 3c57a2f15261fe3be810fe5a482593c0abd7e9e4 2353 python-git_3.0.3-3.dsc
 ffc544cb14546084b0b4478d5d473006fb4337ab 6388 python-git_3.0.3-3.debian.tar.xz
 5eb1ab0cb1644ab6e7ee5dcdb975b1b348432eac 8695 
python-git_3.0.3-3_source.buildinfo
Checksums-Sha256:
 e73829e091f0fbd9a27181a3cb432fec5ed7767bc215ca0f8b0bcd89eda84a2c 2353 
python-git_3.0.3-3.dsc
 cce5ca68f43d1bdd2cba0a55b594e7faadd976a5c6dd2e011ef0f051d17fbaa1 6388 
python-git_3.0.3-3.debian.tar.xz
 fea51fb4f7e99d9ba24adb196df22f833eb224703a4bebc658d73795ccb46731 8695 
python-git_3.0.3-3_source.buildinfo
Files:
 7f4b91f0a838575fce106b8038bfe116 2353 python optional python-git_3.0.3-3.dsc
 6581d46186af7d0155c8f10ae3e314c4 6388 python optional 
python-git_3.0.3-3.debian.tar.xz
 a3e3ec8dce19a49756d0b5b5a58adba3 8695 python optional 
python-git_3.0.3-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEE0kq/0SfNJVahPGx5zBSfbCil4lcFAl2f7rUSHHRha2FraUBk
ZWJpYW4ub3JnAAoJEMwUn2wopeJXGtUP/R0UNfqn6sUi1A/hARl5oVobcw2Bz+wm
ApKWkSdozMFjA+bWNlMr3kDKnpkpZ4HDY5VkOT/pJYD3scgRvxE0jcbN532KNCF1
LiBQ5DYo5r1ra181vkTd40/zqcRvgub7nOtjPPhKj4vwB+wWo/Ibd4XD2dxxSv1s
kRFbi/HXNYaBKCg9QJ1eOjATOWePywrwbiPBDO3QL9+dbI1RmHRdIvew07iZKqq2
NKCaahYQlCEy0dZUoxsBPcM4/ODJYj8ypLtiUwwrzZEdqLjY38ySf/gjb46CdJAK
LF7ozDmHNxQMsAZaOkk7vu3enIoaJP0VLFCVKSs/zfjpV0QK6Yp1bePj1MlRd98v
WHYPRlA2ZSadce5Jtt1rY1Ed1ixgFUNcoBsBJTrENr/aVB8CKKP40k9Ea/jakSIT
DlwHVEviRmOjNIICUpY2nFmNkgRz+QzS8zdMJyRAkvWijftr2egYlY2RJYRvoeol
ey1WTOlavyhJ/Db5OfArQ1IbFj65TPigsco1OQvK2dSHq3

Processed: tagging 942118

[Debian Bug Tracking System]

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

> tags 942118 - help
Bug #942118 [smartmontools] smartmontools: fails to restart during upgrade, 
breaks dpkg
Removed tag(s) help.
> thanks
Stopping processing here.

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

Bug#941756: marked as pending in python-git

[TANIGUCHI Takaki]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/python-git/commit/d60c3694e60c356916f654fc46c5a9044bb345b2


Fix file conflict

Closes: #941756


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/941756

Processed: Bug#941756 marked as pending in python-git

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #941756 [python3-git] python3-git: trying to overwrite 
'/usr/share/doc/python-git/_static/jquery.js', which is also in package 
python-git 2.1.11-1
Added tag(s) pending.

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

Bug#903213: fixed in datalad 0.10.2-1

[Yaroslav Halchenko]

On Tue, 06 Aug 2019, Santiago Vila wrote:

> reopen 903213
> found 903213 0.4.1-1
> fixed 903213 0.10.2-1
> thanks

> Hi. Could we please fix this in stretch?
> (Packages in stretch must be buildable in stretch).

...
FAILED (SKIP=65, errors=63, failures=15)

I will unlikely embark on that endeavor until I retire and get really
bored! ;-)  (well -- the "fix" could be just disabling testing).

those failures cheeped in  with some new then release of git or
git-annex most likely.

stretch is now a very oldstable, and 0.4.1 of datalad is even more so --
we are aiming to release 0.12 soon.

if anything -- feel welcome to remove datalad from stretch


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

Processed: tagging 942118

[Debian Bug Tracking System]

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

> tags 942118 + help
Bug #942118 [smartmontools] smartmontools: fails to restart during upgrade, 
breaks dpkg
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#935341: marked as done (backintime-qt4: Qt4 removal from Bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 11 Oct 2019 01:00:11 +
with message-id 
and subject line Bug#935341: fixed in backintime 1.2.1-1
has caused the Debian Bug report #935341,
regarding backintime-qt4: Qt4 removal from 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.)


-- 
935341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: backintime
Version: 1.1.24-0.1
Severity: important
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal

Hi!

As you might know, we the Qt/KDE team are going to remove Qt 4 in Bullseye
cycle, as announced in [1].

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.

Your package still uses Qt 4, via the Python bindings (PyQt4).

Therefore, please take the time and:

- contact your upstream (if existing) and ask about the state of a Qt 5 /
  PyQt5 port of your application;
- if there are no activities regarding porting, investigate whether there are
  suitable alternatives for your users;
- if there is a Qt 5 port that is not yet packaged, consider packaging it;
- if both the Qt 4 and the Qt 5 versions already coexist in the Debian
  archives, consider removing the Qt 4 version.

Porting from Qt 4 to 5 is much easier than it was to port from Qt 3 to 4.
Please see [2] for the general porting instructions, and [3] for some
Python-specific differences.

The removal is being tracked in [4]. My intention is to bump the severity
of this bug to RC soon, like it is already the case with other Qt 4 removal
bugs.

[1]: https://lists.debian.org/debian-devel-announce/2017/08/msg6.html
[2]: https://doc.qt.io/qt-5/sourcebreaks.html
[3]: https://www.riverbankcomputing.com/static/Docs/PyQt5/pyqt4_differences.html
[4]: https://wiki.debian.org/Qt4Removal

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: backintime
Source-Version: 1.2.1-1

We believe that the bug you reported is fixed in the latest version of
backintime, 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.
Jonathan Wiltshire  (supplier of updated backintime 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, 15 Sep 2019 15:02:51 +0100
Source: backintime
Binary: backintime-common backintime-qt backintime-qt4
Architecture: source all
Version: 1.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Wiltshire 
Changed-By: Jonathan Wiltshire 
Description:
 backintime-common - simple backup/snapshot system (common files)
 backintime-qt - simple backup/snapshot system (graphical interface)
 backintime-qt4 - Qt 4 front-end for backintime (transitional package)
Closes: 879611 930589 935341 939139 939140
Changes:
 backintime (1.2.1-1) unstable; urgency=medium
 .
   [ Fabian Wolff ]
   * Add myself as co-maintainer in debian/control.
   * New upstream release (Closes: #930589, #935341, #879611).
   * Upgrade to Standards-Version 4.4.0 (no changes).
   * Upgrade to debhelper compat level 12.
   * Remove debian/patches (all fixed upstream).
   * Introduce new backintime-qt package, because upstream moved from
 Qt 4 to Qt 5. Make backintime-qt4 a transitional package.
   * Drop the transitional backintime-{gnome,kde} packages
 (Closes: #939139, #939140).
 .
   [ Jonathan Wiltshire ]
   * Team upload.
   * Add a debian/NEWS entry regarding possible change to repository
 permissions
Checksums-Sha1:
 a405d88b0cd0447d7fafa0753175f5521749dbb4 2052 backintime_1.2.1-1.dsc
 ed05ad6ec1347764bcf5207564f5c45c1aac7099 713853 backintime_1.2.1.orig.tar.gz
 b313b5ac2f545aacda6752d681f8ed78ef3d81d9 5944 backintime_1.2.1-1.debian.tar.xz
 f23f645ed80533bb01b9d3b24e6f6715bb447a98 260068 
backintime-common_1.2.1-1_all.deb
 9c988c92e50634c17446708f3bfe433306553a6b 20136 backintime-qt4_1.2.1-1_all.deb
 d41df7f299413b95d7c28c284940ca3b9ad2ca29 72164 backintime-qt_1.2.1-1_all.deb
 a01a78feff6eec161022fa7dae20626250d575bf 6558 

Bug#942155: backintime: Incomplete debian/copyright, etc.

[Chris Lamb]

Source: backintime
Version: 1.2.1-1
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: Jonathan Wiltshire , ftpmas...@debian.org, 
Fabian Wolff , spwhit...@spwhitton.name

Hi,

I just ACCEPTed backintime from NEW but the FTP team noticed:

 *  qt/docbook/en/* seem to be GFDL not GPL. (bug already filed; not a
regression from unstable)

 *  `Files: *` is missing copyright years and holders as given in
README.md.  And `Files: debian/*` stanza out-of-date.  (bug should not
be filed until after ACCEPT as it only applies to version in NEW)

 *  New binary package name is sane as it ships /usr/bin/backintime-qt

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload. :)


Regards,

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

Bug#942154: z3: Incomplete debian/copyright?

[Chris Lamb]

Source: z3
Version: 4.8.6-1
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: Fabian Wolff , ftpmas...@debian.org

Hi,

I just ACCEPTed z3 from NEW but noticed it was missing attribution in 
debian/copyright for at least Arie Gurfinkel and Saint-Petersburg State
University.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

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

Processed: Re: Bug#924757: anjuta: clean after build deletes libanjuta/interfaces/Makefile.am.gir which is not regenerated

[Debian Bug Tracking System]

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

> severity 924757 important
Bug #924757 [src:anjuta] anjuta: clean after build deletes 
libanjuta/interfaces/Makefile.am.gir which is not regenerated
Severity set to 'important' from 'serious'
>
End of message, stopping processing here.

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

Bug#941917: Ping? nginx and the perl transition

[Dominic Hargreaves]

Hello nginx maintainers.

Please would you be able to look at this bug soon? I believe It's
currently the main thing preventing the perl transition from completing.

If not, I can try and look at it, but it might not be before the weekend
and it would be good if the transition was completed by then.

Thanks!
Dominic

Bug#942148: ndiswrapper-dkms: ndiswrapper 1.60 module fails to compile for kernel 5.3

[Lothar Brendel]

Package: ndiswrapper-dkms
Version: 1.60-8
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

   kernel upgrade to linux-image-5.3.2


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

   Effective was building the module for linux-image-4.20.17, ineffective was 
building for linux-image-5.3.2 and linux-image-5.3.5.


   * What was the outcome of this action?

   4.20.17: module ndiswrapper works flawlessly.
   5.3.*: make: *** [Makefile:1639: 
_module_/var/lib/dkms/ndiswrapper/1.60/build] Error 2

   Reason: In file linux/sched.h, the member "cpus_allowed" of struct 
task_struct has been renamed to "cpus_mask" in kernel 5.3.


   * What outcome did you expect instead?

   successfuil build
   
Kind regards
 LB


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

Kernel: Linux 4.20.17-towo.1-siduction-amd64 (SMP w/2 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ndiswrapper-dkms depends on:
ii  dkms  2.7.1-4

ndiswrapper-dkms recommends no packages.

ndiswrapper-dkms suggests no packages.

-- no debconf information

Bug#942147: marked as done (info: removal of info makes files disappear from texinfo-doc-nonfree)

[Debian Bug Tracking System]

Your message dated Thu, 10 Oct 2019 22:34:43 +
with message-id 
and subject line Bug#942147: fixed in texinfo 6.7.0.dfsg.2-4
has caused the Debian Bug report #942147,
regarding info: removal of info makes files disappear from texinfo-doc-nonfree
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.)


-- 
942147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: info
Version: 6.7.0.dfsg.2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

The installation sequence to reproduce this problem is

  apt-get install texinfo-doc-nonfree
  # (1)
  apt-get install info
  apt-get remove info
  # (2)

The list of installed files at points (1) and (2) should be identical,
but the following files have disappeared:

  /usr/share/info/info-stnd.info.gz

This is a serious bug violating policy 7.6, see
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
and also see the footnote that describes this incorrect behavior:
https://www.debian.org/doc/debian-policy/ch-relationships.html#id13

The info package has the following relationships with texinfo-doc-nonfree:

  Conflicts: n/a
  Breaks:n/a
  Replaces:  texinfo-doc-nonfree

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

0m31.5s DEBUG: Modified(user, group, mode, size, target): 
/var/lib/dpkg/info/texinfo-doc-nonfree.list expected(root, root, - 100644, 
25866, None) != found(root, root, - 100644, 25832, None)
0m31.5s ERROR: FAIL: After purging files have disappeared:
  /usr/share/info/info-stnd.info.gz  owned by: info

0m31.5s ERROR: FAIL: After purging files have been modified:
  /var/lib/dpkg/info/texinfo-doc-nonfree.listnot owned


cheers,

Andreas


texinfo-doc-nonfree=6.5.0-1_info=6.7.0.dfsg.2-3+b1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: texinfo
Source-Version: 6.7.0.dfsg.2-4

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

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texinfo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 11 Oct 2019 07:20:29 +0900
Source: texinfo
Architecture: source
Version: 6.7.0.dfsg.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX maintainers 
Changed-By: Norbert Preining 
Closes: 942147
Changes:
 texinfo (6.7.0.dfsg.2-4) unstable; urgency=medium
 .
   * info needs to break against ti-doc-nonfree (Closes: #942147)
   * change texinfo/ti-doc-nofree from conflicts to breaks
Checksums-Sha1:
 a41674a13ae5d63e25c3ee8017501fa348c20f4b 1875 texinfo_6.7.0.dfsg.2-4.dsc
 f62f45ee8c2bbf52faaa2c7cc8baf4d8e6d7729b 27168 
texinfo_6.7.0.dfsg.2-4.debian.tar.xz
 d09ba064346e9990ba078894c6ed6252c2eb53a8 6098 
texinfo_6.7.0.dfsg.2-4_source.buildinfo
Checksums-Sha256:
 1254af5c0040688477a0a728bca77496c8bb063bc1442f04653d23b2252cdd36 1875 
texinfo_6.7.0.dfsg.2-4.dsc
 7e2db6eec2a5343f417d9b71021adae7e5832cabf6efec041aa934561d063efa 27168 
texinfo_6.7.0.dfsg.2-4.debian.tar.xz
 ab02f33f0306ac924dd0765e1532cbe9c923b72212b9c4d0543cff6a1608b631 6098 
texinfo_6.7.0.dfsg.2-4_source.buildinfo
Files:
 7ba6dd793d82dfd4a0a518f396c1cdfb 1875 doc standard texinfo_6.7.0.dfsg.2-4.dsc
 3303143b5fca4ae3c51862100fd156de 27168 doc standard 
texinfo_6.7.0.dfsg.2-4.debian.tar.xz
 c496c6dec83781efbd3d576414ba3678 6098 doc standard 
texinfo_6.7.0.dfsg.2-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE68ws0vrA2voQX53I2A4JsIcUAGYFAl2fr24ACgkQ2A4JsIcU
AGYgnAf/T/xCYA1VLAhlgdxDTBIeLlnX8vVpD9pRBxaXI1EbVuDVOhIp4HOH90vt
LattGK6SqKdeqbz5JUeW3ZJ37MSzyV0Tp2io8SSr9wizuKrjExUADg4ISLqxYZc4
6r0TmNvasA7vHEIntLrjyXBBJfsTiQMzvt1sh2KIAxNm0QdHV9dviOfZqamDPZyi
yTby2r6fqgUNeSWjdpdbap2/pxxhtF4FWy0vdBHyAkAclkSn5YeaYeX7na

Processed: flowcanvas: diff for NMU version 0.7.1+dfsg0-0.5

[Debian Bug Tracking System]

Processing control commands:

> tags 932531 + patch
Bug #932531 [src:flowcanvas] flowcanvas: Uses manual dh sequence operations 
that are going to be removed
Added tag(s) patch.
> tags 932531 + pending
Bug #932531 [src:flowcanvas] flowcanvas: Uses manual dh sequence operations 
that are going to be removed
Added tag(s) pending.

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

Bug#932531: flowcanvas: diff for NMU version 0.7.1+dfsg0-0.5

[Sebastian Ramacher]

Control: tags 932531 + patch
Control: tags 932531 + pending

Dear maintainer,

I've prepared an NMU for flowcanvas (versioned as 0.7.1+dfsg0-0.5) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru flowcanvas-0.7.1+dfsg0/debian/changelog flowcanvas-0.7.1+dfsg0/debian/changelog
--- flowcanvas-0.7.1+dfsg0/debian/changelog	2015-09-05 18:29:21.0 +0200
+++ flowcanvas-0.7.1+dfsg0/debian/changelog	2019-10-11 00:10:55.0 +0200
@@ -1,3 +1,10 @@
+flowcanvas (0.7.1+dfsg0-0.5) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Remove use of --before and --after (Closes: #932531)
+
+ -- Sebastian Ramacher   Fri, 11 Oct 2019 00:10:55 +0200
+
 flowcanvas (0.7.1+dfsg0-0.4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru flowcanvas-0.7.1+dfsg0/debian/rules flowcanvas-0.7.1+dfsg0/debian/rules
--- flowcanvas-0.7.1+dfsg0/debian/rules	2012-01-09 19:52:46.0 +0100
+++ flowcanvas-0.7.1+dfsg0/debian/rules	2019-10-11 00:10:18.0 +0200
@@ -11,17 +11,11 @@
 	./waf configure --prefix /usr
 
 override_dh_auto_build:
-	dh build --before dh_auto_build
 	./waf build
-	dh build --after dh_auto_build
 
 override_dh_auto_install:
-	dh install --before dh_auto_install
 	./waf install --destdir $(CURDIR)/debian/tmp
-	dh install --after dh_auto_install
 
 override_dh_auto_clean:
-	dh clean --before dh_auto_clean
 	./waf clean || true
 	find -name "*.pyc" -delete
-	dh clean --after dh_auto_clean


signature.asc
Description: PGP signature

Bug#925662: closing 925662

[Salvatore Bonaccorso]

close 925662 3.12-1
thanks

Processed: closing 925662

[Debian Bug Tracking System]

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

> close 925662 3.12-1
Bug #925662 [src:criu] criu: ftbfs with GCC-9
Marked as fixed in versions criu/3.12-1.
Bug #925662 [src:criu] criu: ftbfs with GCC-9
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#941105: marked as done (FTBFS: relocation R_X86_64_TPOFF32 against `tls_serialization_float_format' can not be used when making a shared object)

[Debian Bug Tracking System]

Your message dated Thu, 10 Oct 2019 23:58:49 +0200
with message-id <2f02e6c1-f7a1-c071-1a08-1fe70104c...@debian.org>
and subject line Re: FTBFS: relocation R_X86_64_TPOFF32 against 
`tls_serialization_float_format' can not be used when making a shared object
has caused the Debian Bug report #941105,
regarding FTBFS: relocation R_X86_64_TPOFF32 against 
`tls_serialization_float_format' can not be used when making a shared object
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.)


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

While rebuilding packages depending on nettle, libstorj failed with the 
following error:

/bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pedantic -O3 -Wall -Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed -o libstorj.la -rpath /usr/lib storj.lo utils.lo http.lo 
uploader.lo downloader.lo bip39.lo crypto.lo rs.lo -lcurl -lnettle -ljson-c 
-luv -lm 
libtool: link: gcc -shared  -fPIC -DPIC  .libs/storj.o .libs/utils.o 
.libs/http.o .libs/uploader.o .libs/downloader.o .libs/bip39.o .libs/crypto.o 
.libs/rs.o   /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so -lnettle -ljson-c -luv 
-lm  -g -O2 -fstack-protector-strong -O3 -Wl,-z -Wl,relro -Wl,-z -Wl,now 
-Wl,--as-needed   -pthread -Wl,-soname -Wl,libstorj.so.0 -o 
.libs/libstorj.so.0.0.0
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libjson-c.a(json_object.o):
 relocation R_X86_64_TPOFF32 against `tls_serialization_float_format' can not 
be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: nonrepresentable section on output
collect2: error: ld returned 1 exit status

Not sure what's happening there since -fPIC is indeed used.

The full build log is attached.

-- 
Magnus Holmgrenholmg...@debian.org
Debian Developer sbuild (Debian sbuild) 0.78.1 (09 February 2019) on johansson.kibibyte.se

+==+
| libstorj (amd64) Tue, 24 Sep 2019 20:03:59 + |
+==+

Package: libstorj
Distribution: sid
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/sid-amd64-sbuild-2fc154fe-2db6-43fd-b47b-c98ab8b5fc71' 
with '<>'
I: NOTICE: Log filtering will replace 'build/libstorj-wu1kZk/resolver-e6BMLW' 
with '<>'

+--+
| Update chroot|
+--+

Get:1 http://ftp.se.debian.org/debian sid InRelease [139 kB]
Get:2 http://ftp.se.debian.org/debian sid/main Sources.diff/Index [27.9 kB]
Get:3 http://ftp.se.debian.org/debian sid/main amd64 Packages.diff/Index [27.9 
kB]
Get:4 http://ftp.se.debian.org/debian sid/main Sources 2019-09-24-0215.17.pdiff 
[20.1 kB]
Get:5 http://ftp.se.debian.org/debian sid/main Sources 2019-09-24-0813.11.pdiff 
[5362 B]
Get:6 http://ftp.se.debian.org/debian sid/main Sources 2019-09-24-1416.36.pdiff 
[10.1 kB]
Get:7 http://ftp.se.debian.org/debian sid/main amd64 Packages 
2019-09-24-0215.17.pdiff [22.8 kB]
Get:8 http://ftp.se.debian.org/debian sid/main amd64 Packages 
2019-09-24-0813.11.pdiff [4835 B]
Get:9 http://ftp.se.debian.org/debian sid/main amd64 Packages 
2019-09-24-1416.36.pdiff [8123 B]
Get:6 http://ftp.se.debian.org/debian sid/main Sources 2019-09-24-1416.36.pdiff 
[10.1 kB]
Get:9 http://ftp.se.debian.org/debian sid/main amd64 Packages 
2019-09-24-1416.36.pdiff [8123 B]
Fetched 266 kB in 7s (36.2 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
  apt e2fsprogs libapt-pkg5.0 libarchive-zip-perl libattr1 libc-bin
  libc-dev-bin libc6 libc6-dev libcom-err2 libext2fs2 libss2 logsave
13 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 10.1 MB of archives.
After this operation, 100 kB of additional disk space will be used.
Get:1 http://ftp.se.debian.org/debian sid/main amd64 libc6-dev amd64 2.29-2 
[2651 kB]
Get:2 http://ftp.se.debian.org/debian sid/main amd64 libc-dev-bin amd64 2.29-2 
[277 kB]
Get:3 http:

Processed: notfixed 942088 in 5.02-1, tagging 941267, found 942123 in 1.7.0-1, tagging 942123

[Debian Bug Tracking System]

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

> notfixed 942088 5.02-1
Bug #942088 {Done: "Dr. Tobias Quathamer" } [manpages-dev] 
manpages-dev: crypt(3) is not installed
No longer marked as fixed in versions 5.02-1.
> tags 941267 - moreinfo
Bug #941267 [ukwm] ukwm can't start, dmesg has segfault error info 
libukwm-cogl-1.so [b5b4c000+68000]
Removed tag(s) moreinfo.
> found 942123 1.7.0-1
Bug #942123 [transmission-remote-cli] transmission-remote-cli: should this 
package be removed?
Marked as found in versions transmission-remote-cli/1.7.0-1.
> tags 942123 + sid bullseye
Bug #942123 [transmission-remote-cli] transmission-remote-cli: should this 
package be removed?
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Bug#941917: nginx: FTBFS on several architectures: luajit.h: No such file or directory

[gregor herrmann]

On Tue, 08 Oct 2019 01:07:04 +0900, Hideki Yamane wrote:

>  In debian/control, Build-Depends: libluajit-5.1-dev [i386 amd64 
> kfreebsd-i386 armel armhf powerpc powerpcspe mips mipsel]
>  is wrong, as https://buildd.debian.org/status/package.php?p=luajit&suite=sid 
> says below archs are built.
[..] 
>  So, it should be libluajit-5.1-dev [amd64 arm64 armel armhf i386 mips64el 
> mipsel ppc64el hurd-i386 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64] and so 
> on.
>  And it seems that it should check whether its arch has libluajit-5.1-dev or 
> not.

Any news here? This is the last blocker for the perl 5.30 transition.

Do I understand this correctly that changing the architecture list
should fix the bug short-term and then the failing luajit detection
should be fixed as well? At least the first part would be quite easy.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Dave Brubeck: Unsquare Dance


signature.asc
Description: Digital Signature

Processed: Re: Bug#886835: Should sitplus package be droped from Debian (Was: Bug#886835: sitplus fails to start because GTK+ 2.x and GTK+ 3 in the same process is not supported)

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #886835 [sitplus] sitplus fails to start because GTK+ 2.x and GTK+ 3 in the 
same process is not supported
Bug reassigned from package 'sitplus' to 'ftp.debian.org'.
No longer marked as found in versions sitplus/1.0.3-5.1.
Ignoring request to alter fixed versions of bug #886835 to the same values 
previously set
> retitle -1 RM: sitplus -- RoM; very low popcon; broken
Bug #886835 [ftp.debian.org] sitplus fails to start because GTK+ 2.x and GTK+ 3 
in the same process is not supported
Changed Bug title to 'RM: sitplus -- RoM; very low popcon; broken' from 
'sitplus fails to start because GTK+ 2.x and GTK+ 3 in the same process is not 
supported'.

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

Bug#886835: Should sitplus package be droped from Debian (Was: Bug#886835: sitplus fails to start because GTK+ 2.x and GTK+ 3 in the same process is not supported)

[Olly Betts]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: sitplus -- RoM; very low popcon; broken

On Thu, Oct 10, 2019 at 10:18:51PM +0200, Andreas Tille wrote:
> On Fri, Oct 11, 2019 at 09:07:38AM +1300, Olly Betts wrote:
> > 
> > It's more than a year later - has anyone shown interest in updating
> > sitplus?
> > 
> > If not, I propose to reassign this bug as an RM with ftpmaster.  The
> > package can be updated and reintroduced should somebody step forward
> > to do the work (and a new library package means it would need a trip
> > through NEW either way).
> > 
> > I realise letting go of a package is often not easy, but having a broken
> > package in unstable doesn't benefit anyone, wastes the time of unstable
> > users who try to install it only to discover it doesn't even run, and
> > incurs a cost to people managing transitions - e.g. #915592, #922597,
> > #933424.
>
> Just go for it.  Kind regards, Andreas.

Thanks for the quick confirmation - given that I've marked it as "RoM".

Cheers,
Olly

Bug#942147: info: removal of info makes files disappear from texinfo-doc-nonfree

[Andreas Beckmann]

Package: info
Version: 6.7.0.dfsg.2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

The installation sequence to reproduce this problem is

  apt-get install texinfo-doc-nonfree
  # (1)
  apt-get install info
  apt-get remove info
  # (2)

The list of installed files at points (1) and (2) should be identical,
but the following files have disappeared:

  /usr/share/info/info-stnd.info.gz

This is a serious bug violating policy 7.6, see
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
and also see the footnote that describes this incorrect behavior:
https://www.debian.org/doc/debian-policy/ch-relationships.html#id13

The info package has the following relationships with texinfo-doc-nonfree:

  Conflicts: n/a
  Breaks:n/a
  Replaces:  texinfo-doc-nonfree

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

0m31.5s DEBUG: Modified(user, group, mode, size, target): 
/var/lib/dpkg/info/texinfo-doc-nonfree.list expected(root, root, - 100644, 
25866, None) != found(root, root, - 100644, 25832, None)
0m31.5s ERROR: FAIL: After purging files have disappeared:
  /usr/share/info/info-stnd.info.gz  owned by: info

0m31.5s ERROR: FAIL: After purging files have been modified:
  /var/lib/dpkg/info/texinfo-doc-nonfree.listnot owned


cheers,

Andreas


texinfo-doc-nonfree=6.5.0-1_info=6.7.0.dfsg.2-3+b1.log.gz
Description: application/gzip

Bug#942077: marked as done (/usr/bin/budgie-desktop: Update to GNOME 3.34 breaks Budgie)

[Debian Bug Tracking System]

Your message dated Thu, 10 Oct 2019 21:04:19 +
with message-id 
and subject line Bug#942077: fixed in budgie-desktop 10.5-4
has caused the Debian Bug report #942077,
regarding /usr/bin/budgie-desktop: Update to GNOME 3.34 breaks Budgie
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.)


-- 
942077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: budgie-core
Version: 10.5-3
Severity: grave
File: /usr/bin/budgie-desktop
Tags: patch
Justification: renders package unusable

Dear Maintainer,

After upgrading GNOME to 3.34, starting Budgie invariably ends with
GNOME's error screen (“Oops, something went wrong”). This seems to be
due to the fact that gnome-session uses systemd as a session manager
nowadays, resulting in gnome-shell to be started indiscriminately. This
can be resolved by using gnome-session's builtin session manager. I've
attached a patch (originally from Arch Linux) to do just that.

Kind regards,

Willem Mulder

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

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

Versions of packages budgie-core depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.34.0-1
ii  gnome-screensaver3.6.1-10+b1
ii  gnome-session-bin3.34.0-3
ii  gnome-session-common 3.34.0-3
ii  gnome-settings-daemon3.34.0-3
ii  libasound2   1.1.8-1
ii  libbudgie-plugin010.5-3
ii  libbudgie-private0   10.5-3
ii  libbudgietheme0  10.5-3
ii  libc62.29-2
ii  libcairo21.16.0-4
ii  libgdk-pixbuf2.0-0   2.38.2+dfsg-1
ii  libgirepository-1.0-11.62.0-2
ii  libgles2 1.1.0-1+b1
ii  libglib2.0-0 2.62.0-3
ii  libgnome-bluetooth13 3.34.0-1
ii  libgnome-desktop-3-183.34.0-2
ii  libgnome-menu-3-03.32.0-1
ii  libgtk-3-0   3.24.12-1
ii  libibus-1.0-51.5.19-4+b1
ii  libmutter-5-03.34.0-4
ii  libnotify4   0.7.8-1
ii  libpeas-1.0-01.22.0-4
ii  libpolkit-agent-1-0  0.105-26
ii  libpolkit-gobject-1-00.105-26
ii  libpulse-mainloop-glib0  13.0-2
ii  libpulse013.0-2
ii  libraven010.5-3
ii  libupower-glib3  0.99.11-1
ii  libuuid1 2.34-0.1
ii  libwnck-3-0  3.32.0-1
ii  libx11-6 2:1.6.8-1

budgie-core recommends no packages.

budgie-core suggests no packages.

-- no debconf information
diff -Nru budgie-desktop-10.5/debian/changelog 
budgie-desktop-10.5/debian/changelog
--- budgie-desktop-10.5/debian/changelog2019-09-30 19:59:27.0 
+0200
+++ budgie-desktop-10.5/debian/changelog2019-10-09 23:33:24.0 
+0200
@@ -1,3 +1,10 @@
+budgie-desktop (10.5-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Use gnome-session's builtin session manager (Closes: #nn)
+
+ -- Willem Mulder   Wed, 09 Oct 2019 23:33:24 
+0200
+
 budgie-desktop (10.5-3) unstable; urgency=medium
 
   * Upload experimental package to unstable
diff -Nru budgie-desktop-10.5/debian/patches/series 
budgie-desktop-10.5/debian/patches/series
--- budgie-desktop-10.5/debian/patches/series   2019-09-14 20:09:47.0 
+0200
+++ budgie-desktop-10.5/debian/patches/series   2019-10-09 23:26:13.0 
+0200
@@ -15,3 +15,4 @@
 wnck-shutdown.patch
 Use-panel-orientation-for-spacer-sizing.patch
 gsd334.patch
+use-builtin-session-manager.patch
diff -Nru budgie-desktop-10.5/debian/patches/use-builtin-session-manager.patch 
budgie-desktop-10.5/debian/patches/use-builtin-session-manager.pa

Bug#942146: koji: CVE-2019-17109

[Salvatore Bonaccorso]

Source: koji
Version: 1.16.2-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://pagure.io/koji/issue/1634

Hi,

The following vulnerability was published for koji.

CVE-2019-17109[0]:
| Koji through 1.18.0 allows remote Directory Traversal, with resultant
| Privilege Escalation.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-17109
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17109
[1] https://pagure.io/koji/issue/1634
[2] https://docs.pagure.org/koji/CVE-2019-17109/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#886835: Should sitplus package be droped from Debian (Was: Bug#886835: sitplus fails to start because GTK+ 2.x and GTK+ 3 in the same process is not supported)

[Olly Betts]

On Wed, Aug 01, 2018 at 04:26:18PM +1200, Olly Betts wrote:
> On Wed, Jan 10, 2018 at 04:47:48PM +0100, Luis Rivas wrote:
> > On 10 January 2018 at 13:46, Andreas Tille  wrote:
> > > just a note for sitplus:  This package definitely needs more love.
> > > Upstream has released a new version a long time ago but it has split a
> > > separate library which needs to be packaged separately.
> > >
> > > I'm personally lacking the time resources to care for this package.
> > >
> > > Any volunteer or is it possibly better to drop the package at all
> > > if it is not running?
> > 
> > I'm afraid I don't have the time for taking care of this package. So,
> > unless someone else volunteers, probably it's for the better to drop
> > the package for now.
> 
> I suspect this particular issue would be fixed by updating the wxWidgets
> build-dependency from libwxgtk3.0-dev to libwxgtk3.0-gtk3-dev (the
> former uses GTK+ 2.x, the latter GTK+ 3.x), though if nobody's able to
> look after the package properly, perhaps it's better to drop it.

It's more than a year later - has anyone shown interest in updating
sitplus?

If not, I propose to reassign this bug as an RM with ftpmaster.  The
package can be updated and reintroduced should somebody step forward
to do the work (and a new library package means it would need a trip
through NEW either way).

I realise letting go of a package is often not easy, but having a broken
package in unstable doesn't benefit anyone, wastes the time of unstable
users who try to install it only to discover it doesn't even run, and
incurs a cost to people managing transitions - e.g. #915592, #922597,
#933424.

Cheers,
Olly

Bug#942138: apt: installation of glade destroys system

[Adam Schrey]

Package: apt
Version: 1.8.2
Severity: critical
Justification: breaks the whole system

Dear Maintainer,


This report comes from a different (not broken) system. When I was asked for
the apt-files by the bugreport program, I moved the old ones to the system I am
using now (hope this worked).

I tried to install "glade" on my system. This removed a lot of packages. This
destroyed my system. I could have prevented this problem by checking the
packages that will be removed, but I do not always do that.
My desktop environment was XFCE4 and the system used the Vesa driver. The
display manager was lightdm and Gnome was not installed (only some Gnome apps).

I tried to use the rescue mode on a debian DVD and the rescue mode that was
available in GRUB.
But I had to reinstall my system (rescue mode was not working).

I think this information will have the most value for you
(/var/log/apt/history.log):

Start-Date: 2019-10-02  20:45:38
Commandline: apt-get install glade
Install: libpython3.7-minimal:amd64 (3.7.3-2, automatic), libx265-165:amd64
(2.9-4, automatic), libgpgmepp6:amd64 (1.12.0-6, automatic), libgupnp-
igd-1.0-4:amd64 (0.2.5-3, automatic), node-normalize.css:amd64 (8.0.1-3,
automatic), startpar:amd64 (0.61-1, automatic), libmbedtls12:amd64 (2.16.0-1,
automatic), gir1.2-gtksource-4:amd64 (4.0.3-2, automatic), libvulkan1:amd64
(1.1.97-2, automatic), libwayland-egl1:amd64 (1.16.0-1, automatic),
python3-distutils:amd64 (3.7.3-1, automatic), libgtksourceview-4-common:amd64
(4.0.3-2, automatic), libvkd3d1:amd64 (1.1-3, automatic), libobjc-8-dev:amd64
(8.3.0-6, automatic), libegl1:amd64 (1.1.0-1, automatic), libllvm7:amd64
(1:7.0.1-8, automatic), libmbedcrypto3:amd64 (2.16.0-1, automatic),
valac-0.42-vapi:amd64 (0.42.5-1, automatic), libegl-mesa0:amd64 (18.3.6-2,
automatic), libswresample3:amd64 (7:4.1.4-1~deb10u1, automatic),
libqt5sensors5:amd64 (5.11.3-2, automatic), libnumbertext-data:amd64 (1.0.5-1,
automatic), libbrotli1:amd64 (1.0.7-2, automatic), libmtdev-dev:amd64
(1.1.5-1+b1, automatic), libsndio7.0:amd64 (1.5.0-3, automatic),
libnice10:amd64 (0.1.14-1, automatic), libsrtp2-1:amd64 (2.2.0-1, automatic),
libgl1:amd64 (1.1.0-1, automatic), gcc-8-base:amd64 (8.3.0-6, automatic),
gcc-8-base:i386 (8.3.0-6, automatic), gcc-8-base:armhf (8.3.0-6, automatic),
libcrypt-openssl-random-perl:amd64 (0.15-1+b1, automatic), clang-7:amd64
(1:7.0.1-8, automatic), libwoff1:amd64 (1.0.2-1, automatic), libzmf-0.0-0:amd64
(0.0.2-1+b2, automatic), libvala-0.42-0:amd64 (0.42.5-1, automatic),
libjsonrpc-glib-1.0-1:amd64 (3.30.1-2, automatic), libgupnp-1.0-4:amd64
(1.0.3-3, automatic), perl-modules-5.28:amd64 (5.28.1-6, automatic),
libncurses6:amd64 (6.1+20181013-2+deb10u1, automatic), gir1.2-ggit-1.0:amd64
(0.27.7-1, automatic), insserv:amd64 (1.18.0-2, automatic), libpython3.7:amd64
(3.7.3-2, automatic), libimagequant0:amd64 (2.12.2-1.1, automatic),
python3.7:amd64 (3.7.3-2, automatic), gir1.2-template-1.0:amd64 (3.30.0-2,
automatic), libselinux1-dev:amd64 (2.8-1+b1, automatic), libfribidi-dev:amd64
(1.0.5-3.1, automatic), python3.7-dev:amd64 (3.7.3-2, automatic),
libasan5:amd64 (8.3.0-6, automatic), libgles2:amd64 (1.1.0-1, automatic),
libdazzle-1.0-0:amd64 (3.30.2-2, automatic), libwacom-dev:amd64 (0.32-1,
automatic), libclang-common-7-dev:amd64 (1:7.0.1-8, automatic),
libpython3.7-stdlib:amd64 (3.7.3-2, automatic), libclang1-6.0:amd64
(1:6.0.1-10, automatic), python3.7-minimal:amd64 (3.7.3-2, automatic), libyaml-
cpp0.6:amd64 (0.6.2-4, automatic), libaom0:amd64 (1.0.0-3, automatic),
libxmlsec1-nss:amd64 (1.2.27-2, automatic), libmount-dev:amd64 (2.33.1-0.1,
automatic), libqxp-0.0-0:amd64 (0.0.2-1, automatic), libperl5.28:amd64
(5.28.1-6, automatic), pango1.0-tools:amd64 (1.42.4-7~deb10u1, automatic),
libxnvctrl0:amd64 (418.74-1, automatic), libnumbertext-1.0-0:amd64 (1.0.5-1,
automatic), libgcc-8-dev:amd64 (8.3.0-6, automatic), libunbound8:amd64
(1.9.0-2, automatic), libglib2.0-dev-bin:amd64 (2.58.3-2+deb10u1, automatic),
libva2:amd64 (2.4.0-1, automatic), libllvm6.0:amd64 (1:6.0.1-10, automatic),
libx264-155:amd64 (2:0.155.2917+git0a84d98-2, automatic), libubsan1:amd64
(8.3.0-6, automatic), libass9:amd64 (1:0.14.0-2, automatic),
gir1.2-vte-2.91:amd64 (0.54.2-2, automatic), libqt5webchannel5:amd64 (5.11.3-2,
automatic), libboost-iostreams1.67.0:amd64 (1.67.0-13, automatic), libboost-
chrono1.67.0:amd64 (1.67.0-13, automatic), libilmbase23:amd64 (2.2.1-2,
automatic), libreoffice-help-common:amd64 (1:6.1.5-3+deb10u4, automatic),
libhttp-parser2.8:amd64 (2.8.1-1, automatic), libgstreamer-gl1.0-0:amd64
(1.14.4-2, automatic), idle-python3.7:amd64 (3.7.3-2, automatic),
qt5-assistant:amd64 (5.11.3-4, automatic), libdevhelp-3-6:amd64 (3.30.1-1,
automatic), libgdbm6:amd64 (1.18.1-4, automatic), libreoffice-style-
colibre:amd64 (1:6.1.5-3+deb10u4, automatic), libavcodec58:amd64
(7:4.1.4-1~deb10u1, automatic), liborcus-0.14-0:amd64 (0.14.1-6, automatic),
libmbedx509-0:amd64 (2.16.0-1, automatic), libpython3.7-dev:amd64 (3.7.3-2,
au

Processed: [bts-link] source package src:ruby-gnome

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:ruby-gnome
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #941795 (http://bugs.debian.org/941795)
> # Bug title: ruby-gnome: gio2 autopkgtest fails with gobject-introspection 
> 1.62
> #  * https://github.com/ruby-gnome/ruby-gnome/issues/1296
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 941795 + fixed-upstream
Bug #941795 {Done: Utkarsh Gupta } [src:ruby-gnome] 
ruby-gnome: gio2 autopkgtest fails with gobject-introspection 1.62
Added tag(s) fixed-upstream.
> usertags 941795 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#935086: marked as done (insighttoolkit4: FTBFS with GCC-9: use of undeclared identifier '__builtin_is_constant_evaluated')

[Debian Bug Tracking System]

Your message dated Thu, 10 Oct 2019 18:50:06 +
with message-id 
and subject line Bug#935086: fixed in insighttoolkit4 4.12.2-dfsg1-4.1
has caused the Debian Bug report #935086,
regarding insighttoolkit4: FTBFS with GCC-9: use of undeclared identifier 
'__builtin_is_constant_evaluated'
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.)


-- 
935086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: insighttoolkit4
Version: 4.12.2-dfsg1-4
Severity: serious
Justification: FTBFS

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

Insighttoolkit4 FTBFS with:
In file included from /<>/BUILD/Wrapping/itkFixedArray.cxx:1:
In file included from 
/<>/Modules/Core/Common/include/itkCommand.h:21:
In file included from 
/<>/Modules/Core/Common/include/itkObject.h:31:
In file included from 
/<>/Modules/Core/Common/include/itkLightObject.h:21:
In file included from 
/<>/Modules/Core/Common/include/itkMacro.h:47:
In file included from /usr/include/c++/9/string:48:
/usr/include/c++/9/bits/stl_function.h:418:6: error: use of undeclared 
identifier '__builtin_is_constant_evaluated'
if (__builtin_is_constant_evaluated())
^
- -- Found object: 
"/<>/data/.ExternalData/MD5/7665397f59eaeb65c578e8712be70e79"
/usr/include/c++/9/bits/stl_function.h:437:6: error: use of undeclared 
identifier '__builtin_is_constant_evaluated'
if (__builtin_is_constant_evaluated())
^
/usr/include/c++/9/bits/stl_function.h:456:6: error: use of undeclared 
identifier '__builtin_is_constant_evaluated'
if (__builtin_is_constant_evaluated())
^
/usr/include/c++/9/bits/stl_function.h:475:6: error: use of undeclared 
identifier '__builtin_is_constant_evaluated'
if (__builtin_is_constant_evaluated())
^
This seems related to GCC-9.
Full buildlog available on demand.

Thanks,

_g.

- -- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAl1ahPMACgkQ7+hsbH/+
z4NlqAf/YXeuCAqgyr66wanyke1aJJOn8YQr/eV/jPVc9LU0lhqwJyuH0KqGbfPG
3e/S7cwLRPtGfGDdiHHNIjLTxtbScWGEEQ8BYfOqosQ0tteP8H2BLzXp79gnNnUR
J4Boq3W+6BRKuUoa53YEoxCJIrz3fwlZR5oJWowfVhQ/XSWIFmoS/ZdQEuoAR5c/
CjidFWwk5DUAOT2x9NHpEeJCPkX1aYibYigQsMySfGB4zznoRbBe9Y/ttH1zyYPE
nwajwmd8dK7t1YGpkRucwCr6t5+nlKPKxlchwz4jY/isWfi2UpTP16tv8jAmPPCJ
VuUsplljecyl97yZu8hUKHe2fIMI8g==
=uac6
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: insighttoolkit4
Source-Version: 4.12.2-dfsg1-4.1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Oct 2019 19:47:04 +0200
Source: insighttoolkit4
Architecture: source
Version: 4.12.2-dfsg1-4.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Gilles Filippini 
Closes: 935086
Changes:
 insighttoolkit4 (4.12.2-dfsg1-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Force -std=c++11 to fix FTBFS with GCC-9 (closes: #935086)
Checksums-Sha1:
 600aab84e081439f9b0fff24a7a0efd5e8965d1a 2671 
insighttoolkit4_4.12.2-dfsg1-4.1.dsc
 32d95171be964fe0561ab11a92a462f44dfee6b2 26188 
insighttoolkit4_4.12.2-dfsg1-4.1.debian.tar.xz
 ca27306bb2833776b62561ed224dbe0bc96609d3 9001 
insighttoolkit4_4.12.2-dfsg1-4.1_source.buildinfo
Checksums-Sha256:
 bf7f63a0052f7faa90be7b772f9f44a5983afe7655905a1d6f46fd66baa56528 2671 
insighttoolkit4_4.12.2-dfsg1-4.1.dsc
 2857c6a5e92931d500353a0c9018be6b80d2c36db90aade7b71fcbfe0daf8532 26188 
insighttoo

Bug#942119: libproxy: depends on mono for build-arch; mono not universally present

[Simon McVittie]

On Thu, 10 Oct 2019 at 19:15:33 +0200, Thorsten Glaser wrote:
> On Thu, 10 Oct 2019, Simon McVittie wrote:
> 
> >   * dh: Support running addons in "arch-only" or "indep-only" mode by
> > adding "dh-sequence-ADDON" in Build-Depends-Arch or
> 
> Ah, so dh-sequence-* is not a package, just a shorthand for --with * ?

It's a virtual package with two functions:

* Its only provider is the package that implements the ADDON sequence,
  so build-depending on dh-sequence-ADDON is enough to get it installed

* Mentioning it in your Build-Depends{,-Arch,-Indep} tells debhelper to
  activate the relevant sequence during {all,arch-dep,arch-indep} builds,
  the same as "dh --with ADDON", without having to repeat yourself

smcv

Bug#941795: marked as done (ruby-gnome: gio2 autopkgtest fails with gobject-introspection 1.62)

[Debian Bug Tracking System]

Your message dated Thu, 10 Oct 2019 18:20:42 +
with message-id 
and subject line Bug#941795: fixed in ruby-gnome 3.4.0-1
has caused the Debian Bug report #941795,
regarding ruby-gnome: gio2 autopkgtest fails with gobject-introspection 1.62
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.)


-- 
941795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-gnome
Version: 3.3.8-2
Severity: normal
Control: forwarded -1 https://github.com/ruby-gnome/ruby-gnome/issues/1296
Control: tags -1 + upstream

Dear Maintainer,

Please note that since the upload of gobject-introspection 1.62 to
unstable the ruby-gnome autopkgtests fails the gio2 test.

See https://tracker.debian.org/pkg/gobject-introspection

Log available at:
https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-gnome/3078476/log.gz

Upstream seems to be aware of the issue and is working on a solution,
but it said that it will take time.

Other distributions (ubuntu, fedora) seems to have removed ruby-gnome
for the time being.

This issue is blocking gobject-introspection from entering testing,
which in turn blocks the entire gnome 3.34 transition which is currently
ongoing. Given that processing transitions is a very scarce resource
please treat this with urgency to get gobject-introspection/transition
unblocked.

Regards,
Andreas Henriksson
--- End Message ---
--- Begin Message ---
Source: ruby-gnome
Source-Version: 3.4.0-1

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

Debian distribution maintenance software
pp.
Utkarsh Gupta  (supplier of updated ruby-gnome 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 10 Oct 2019 23:30:54 +0530
Source: ruby-gnome
Architecture: source
Version: 3.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Utkarsh Gupta 
Closes: 941795
Changes:
 ruby-gnome (3.4.0-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream version 3.4.0 (Closes: #941795)
   * Bump Standards-Version to 4.4.1
   * Refresh d/patches
Checksums-Sha1:
 588ac620068ecd5a0980149c5c76fdbe4b5607d7 3769 ruby-gnome_3.4.0-1.dsc
 ed9ecf9263290851d0e61eb059fc3954605e7904 3135649 ruby-gnome_3.4.0.orig.tar.gz
 4de510767e759be2a0ddd213df1e05e1040e0921 19572 ruby-gnome_3.4.0-1.debian.tar.xz
 0fae1e0863a150d22f04def995e0d35c241b90ed 19271 
ruby-gnome_3.4.0-1_source.buildinfo
Checksums-Sha256:
 c8cec81d74286a0e2318d35f640a4bb3b762f810ec145bf061f49904af015b55 3769 
ruby-gnome_3.4.0-1.dsc
 34bbbfc9c5d1b0684269e879cbf0375c52b12057aafb1210cc3711981b239c8e 3135649 
ruby-gnome_3.4.0.orig.tar.gz
 733a5dbba519f2d7662dc2e896810b16cff69a964ea50223ff94fb3a66ee7b3c 19572 
ruby-gnome_3.4.0-1.debian.tar.xz
 491827d7ed91ae20929f0ad8c842ded14a0d077762351a9d149c77a44f99b5c9 19271 
ruby-gnome_3.4.0-1_source.buildinfo
Files:
 cf6917a23abd58e02f6f59a44bd9492e 3769 ruby optional ruby-gnome_3.4.0-1.dsc
 eee3f4bdd6d344a28acd4b344b153957 3135649 ruby optional 
ruby-gnome_3.4.0.orig.tar.gz
 397e3c976400e6ade3b7f1ef9b7e53c0 19572 ruby optional 
ruby-gnome_3.4.0-1.debian.tar.xz
 6a984dd3a140c92082b37e3305f592d7 19271 ruby optional 
ruby-gnome_3.4.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJPBAEBCAA5FiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAl2fc58bHGd1cHRhdXRr
YXJzaDIxMDJAZ21haWwuY29tAAoJEII+lnYGw0uWIsQQALwNt2XFSAejKULyC6FP
RHkMO7BuF3GX8cpE/kIRZ4PsRM/ah0/etM0Y3B/zzCPY2rQWgCUC5i549xfm0/BE
AZBpcQ2pK6cpO+a3ud75bY/2Xe6qBBOgMk4iLfjCH7G6SIsfgxFVK414VdJdD66f
oB596kXSW6tfx2b2IQMIT3IGzFBoVxxM+CYwXRYjlwsCxmFXRIsQXxK1DhTtfszm
LXgloFmDtySu9K2NH8vdj8pEYfjrp8HTtnhinIrcWoaOLLb/ySmaZcdbccNaEMVS
ayyCATQuW+Zb766pJ5k7hTsYqx5Z1b5upDX7hQgcxTn6XmnZlQ2dYLKGeodiEU9u
KGbuUWG/+lT0pzbLb+dXyF2REfalQVXnAYR4aXBpaLmekE0NGxsS3nOO9uHTpadY
PbUMpAi0bmBlgZI2PloamLPISBYOwotbREb+eUYdBTtfXNzscs6qqFkLX9jzAsWk
fKjkmaA704BVFCtwc1ZOVFUFGis/93kVCcYlwAdIyJzrQjnwEaMQ9Uq6Ys2vc94w
usuxm9RWfNd+sf8m1Qo5orHZluCIm7iPAi5hm5p7VwFz5j0i+Sg7uLgf7RCsN5pz
dnlJvPfZjwrwJKNIRYGVGb1oL0tJ0ic/42RSqDaANivgtD6zUKg5RUrsB

Bug#942056: marked as done (openvswitch: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Thu, 10 Oct 2019 18:00:13 +
with message-id 
and subject line Bug#942056: fixed in openvswitch 
2.11.0+2019.06.25+git.9ebe795035+ds1-2
has caused the Debian Bug report #942056,
regarding openvswitch: Incomplete debian/copyright?
to be marked as done.

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

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


-- 
942056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openvswitch
Version: 2.11.0+2019.06.25+git.9ebe795035+ds1-1
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: Thomas Goirand , ftpmas...@debian.org

Hi,

I just ACCEPTed openvswitch from NEW but noticed it was missing 
attribution in debian/copyright for at least Ericsson.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: openvswitch
Source-Version: 2.11.0+2019.06.25+git.9ebe795035+ds1-2

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 10 Oct 2019 09:13:37 +0200
Source: openvswitch
Binary: openvswitch-common openvswitch-dbg openvswitch-dev openvswitch-ipsec 
openvswitch-pki openvswitch-switch openvswitch-switch-dpdk 
openvswitch-testcontroller openvswitch-vtep ovn-central ovn-controller-vtep 
ovn-host python3-openvswitch
Architecture: source amd64 all
Version: 2.11.0+2019.06.25+git.9ebe795035+ds1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 openvswitch-common - Open vSwitch common components
 openvswitch-dbg - Debug symbols for Open vSwitch packages
 openvswitch-dev - Open vSwitch development package
 openvswitch-ipsec - Open vSwitch IPsec tunneling support
 openvswitch-pki - Open vSwitch public key infrastructure dependency package
 openvswitch-switch - Open vSwitch switch implementations
 openvswitch-switch-dpdk - DPDK enabled Open vSwitch switch implementation
 openvswitch-testcontroller - Simple controller for testing OpenFlow setups
 openvswitch-vtep - Open vSwitch VTEP utilities
 ovn-central - OVN central components
 ovn-controller-vtep - OVN vtep controller
 ovn-host   - OVN host components
 python3-openvswitch - Python 3 bindings for Open vSwitch
Closes: 942056
Changes:
 openvswitch (2.11.0+2019.06.25+git.9ebe795035+ds1-2) unstable; urgency=medium
 .
   [ Jakub Safarik ]
   * Reintroduce the openvswitch-ipsec package.
   * Fix lintian errors:
 - openvswitch-switch: init.d-script-not-included-in-package.
 - openvswitch source: python-depends-but-no-python-helper.
 - openvswitch source: missing-notice-file-for-apache-license.
 .
   [ Thomas Goirand ]
   * Fixed d/copyright (Closes: #942056).
Checksums-Sha1:
 87aa36bcbb5fed627b07a78a83d3c95216182a2d 3543 
openvswitch_2.11.0+2019.06.25+git.9ebe795035+ds1-2.dsc
 d3ed1e3eb5b422e95c6397665948642859b2c43a 66768 
openvswitch_2.11.0+2019.06.25+git.9ebe795035+ds1-2.debian.tar.xz
 ca321457b07f37150a6ab7fbdfff8ca577739b2d 2066352 
openvswitch-common_2.11.0+2019.06.25+git.9ebe795035+ds1-2_amd64.deb
 f32a117d7d424bc0cb4bd303137dc2e76ec3c751 7164436 
openvswitch-dbg_2.11.0+2019.06.25+git.9ebe795035+ds1-2_amd64.deb
 3b378e41cd99a6f827d3e13be17b215b9c48da9e 1480720 
openvswitch-dev_2.11.0+2019.06.25+git.9ebe795035+ds1-2_amd64.deb
 c7131a090168b29dbbe64de4337fb446c4666d1f 37836 
openvswitch-ipsec_2.11.0+2019.06.25+git.9ebe795035+ds1-2_amd64.deb
 c9a6557d6335f385d686028c572a24a23c806bfa 36408 
openvswitch-pki_2.11.0+2019.06.25+git.9ebe795035+ds1-2_all.deb
 e603231fc80d256710b664b7da53e94605ca4c16 38588 
openvswitch-switch-dpdk_2.11.0+2019.06.25+git.9ebe795035+ds1-2_amd64.deb
 d5ab17c26a1ba16e175f4da5999b0364f3252d17 51972 
openvswitch-switch_2.11.0+2019.06.25+git.9ebe795035+ds1-2_amd6

Bug#941729: marked as done (gpaste: Please upload 3.34 to unstable)

[Debian Bug Tracking System]

Your message dated Thu, 10 Oct 2019 17:34:37 +
with message-id 
and subject line Bug#941729: fixed in gpaste 3.34.1-1
has caused the Debian Bug report #941729,
regarding gpaste: Please upload 3.34 to unstable
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.)


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

The Debian GNOME team has uploaded gnome-shell 3.34 to Unstable.
Please upload gpaste 3.34 to Unstable now too.

I am filing this as serious because the current version of gpaste in
Unstable fails to build from source because it build-depends on a
version of mutter that was never in Unstable.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: gpaste
Source-Version: 3.34.1-1

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

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated gpaste package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Oct 2019 19:22:20 +0200
Source: gpaste
Architecture: source
Version: 3.34.1-1
Distribution: unstable
Urgency: medium
Maintainer: Jérémy Lal 
Changed-By: Jérémy Lal 
Closes: 941729
Changes:
 gpaste (3.34.1-1) unstable; urgency=medium
 .
   [ Jérémy Lal ]
   * New upstream version 3.34.1 (Closes: #941729)
 .
   [ Jeremy Bicha ]
   * Set $XDG_RUNTIME_DIR to clean up some build log noise
Checksums-Sha1:
 2641d58e311f5de9e7af325d29b6b0c4fcc3ff4a 2617 gpaste_3.34.1-1.dsc
 22f9f00a60b043d8dfe3576cee123618767d3c31 184922 gpaste_3.34.1.orig.tar.gz
 fcf42010a7d4c466680ba2fa2c0e05c8deccc81c 7300 gpaste_3.34.1-1.debian.tar.xz
 a0213727e5ea98d78790df403b1c035c33bf1b36 18410 gpaste_3.34.1-1_source.buildinfo
Checksums-Sha256:
 21387fb57c0ccbb0b27d412118d8c3a74bd631cf70942e6b987d8a8a19e5522a 2617 
gpaste_3.34.1-1.dsc
 ba2dbdaecd1dd04c95b44c87078c104d266bfa264b926669cfd2f9684f0e0aef 184922 
gpaste_3.34.1.orig.tar.gz
 2344b5a7eef04387c42a3037095060e426928c1ced31216c795518799fe51f53 7300 
gpaste_3.34.1-1.debian.tar.xz
 9bcc5bc993e4670b4d498229d494b49d308456ac81807e61416a9d24efe1709c 18410 
gpaste_3.34.1-1_source.buildinfo
Files:
 9049f4c6a6c2b1a8678b922516ee924a 2617 gnome optional gpaste_3.34.1-1.dsc
 6c778717fd4577e53b4efccf7bca857c 184922 gnome optional 
gpaste_3.34.1.orig.tar.gz
 2309bbc1c1a85c6c7d17c44735d15695 7300 gnome optional 
gpaste_3.34.1-1.debian.tar.xz
 0c367326d5888963ce634d5c0b7b8250 18410 gnome optional 
gpaste_3.34.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAl2faPYSHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN0hlYP/1nT0jeMHkQ4dyMTvYDT7Uu8Ls0CXd9t
xHyklKWw2uSvMWG406xiIQbYR+gA6+JDC2ZqMFpqbsZqIFpdVR3SOO+lbM3av2NL
NGU8L39AJC34q5KvZTiENsc85/6ZIkyoLVxxfo7ZNOF5D32D3clMnXsNyhOCTxSB
RyRg4DGvQjlL6oEVqGhc/lOis9uYXukgKLZLGLhhGQjC4HVElmueIUYBOSeZE6Zw
KPsO1H7UDLUs+xBlFfPDNTzpqM7dLMVVlC1DROxxN1JfXEQjG9OvcwIqwoP9Jvda
slsMhQdL/yM1RF+EhCYlMwyUopMv/iK5Ai7bx2LGYutjbIqZGaKmf0EAAb6kZtQS
zcR0w9aSjBevjMp30ygxtbxS/lHNZoUowU2PzkNYfJc2xYDhY+BNM2MwFniKpLTP
8gCFjAwxWpscsUkyUYASN+7TJgRt+jeJDB1agY6SgFWjMhyjb63w2N3LtyP1FAxR
R0Ljv59fZ4PRCdf8vbcoUsALujkNmvHL00s8qkyUK4y31u3GrAih/O18+tTNAMzt
Mob/Ada+NX9/i6psFi0BzZ2sfm2AFsasUU/y+7+X3EFGEbmwf3a3IvOJHeLCAfOu
pnu76586qm+bkQsqX8870bYv1iDx3abmfM2BlQGA4fHtpoMLgZHm0vRo4eRvU3XZ
xJ83WtMsqlPH
=ig9I
-END PGP SIGNATURE End Message ---

Bug#941731: marked as done (appstream-util: unable to create directory '/sbuild-nonexistent/.cache/dconf')

[Debian Bug Tracking System]

Your message dated Thu, 10 Oct 2019 19:18:09 +0200
with message-id 

and subject line Re: appstream-util: unable to create directory 
'/sbuild-nonexistent/.cache/dconf'
has caused the Debian Bug report #941731,
regarding appstream-util: unable to create directory 
'/sbuild-nonexistent/.cache/dconf'
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.)


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

Hi,

when building gpaste, the log shows

/usr/bin/msgfmt --xml --template 
data/appstream/org.gnome.GPaste.Ui.appdata.xml.in -o 
data/appstream/org.gnome.GPaste.Ui.appdata.xml -d ./po/
if test -f "data/appstream/org.gnome.GPaste.Ui.appdata.xml"; then d=; else 
d="./"; fi; \
if test -n "/usr/bin/appstream-util"; \
then /usr/bin/appstream-util --nonet validate 
${d}data/appstream/org.gnome.GPaste.Ui.appdata.xml; fi \
&& touch data/appstream/org.gnome.GPaste.Ui.appdata.valid
data/appstream/org.gnome.GPaste.Ui.appdata.xml: 
(appstream-util:6465): dconf-CRITICAL **: 11:45:26.968: unable to create 
directory '/sbuild-nonexistent/.cache/dconf': Permission denied.  dconf will 
not work properly.

This is new and i think it is a regression from 0.7.14.

Jérémy

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

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

Versions of packages appstream-util depends on:
ii  libappstream-glib8  0.7.16-1
ii  libc6   2.29-2
ii  libgdk-pixbuf2.0-0  2.39.2-3
ii  libglib2.0-02.62.0-3
ii  libsoup2.4-12.68.1-2

appstream-util recommends no packages.

appstream-util suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Le dim. 6 oct. 2019 à 21:37, Jeremy Bicha  a écrit :

> Jérémy, I think the actual error is this:
>
> FAILED:
> • tag-missing   :  required [use
> https://odrs.gnome.org/oars]
> • tag-missing   :  required
> Validation of files failed
>
> appstream-glib 0.7.16 made the validation requirements stricter.
> Therefore, I believe this isn't an appstream-glib bug and this bug
> report should be closed.
>
> The warnings you see about the directory permission denied were also
> present in your last experimental upload. I am attaching a patch you
> can apply if you don't want to see those warnings in your build log.
> Applying the patch would have made it a lot easier for you to see
> where the failure was in this case.
>

Yes, thanks a lot for that.

I applied the patch to gpaste, and got the right error.
It'd be nicer to not need that patch, but i guess it's a feature request,
not a bug.

Hence closing it.
--- End Message ---

Bug#942119: libproxy: depends on mono for build-arch; mono not universally present

[Thorsten Glaser]

On Thu, 10 Oct 2019, Simon McVittie wrote:

>   * dh: Support running addons in "arch-only" or "indep-only" mode by
> adding "dh-sequence-ADDON" in Build-Depends-Arch or

Ah, so dh-sequence-* is not a package, just a shorthand for --with * ?

> DH_ADDONS += --with cli
[…]
> %:
>   dh $@ $(DH_ADDONS)

That looks even better, then.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**

Bug#942119: libproxy: depends on mono for build-arch; mono not universally present

[Simon McVittie]

On Thu, 10 Oct 2019 at 12:46:22 -0400, Jeremy Bicha wrote:
> On Thu, Oct 10, 2019 at 12:09 PM Thorsten Glaser  wrote:
> > src:libproxy recently gained a B-D-Arch on dh-sequence-cli
...
> > Please use mono only in B-D-Indep.
> 
> dh-sequence-cli doesn't work in B-D-Indep as I found when I built 0.4.15-6 :
> 
> https://buildd.debian.org/status/logs.php?pkg=libproxy&arch=arm64
> 
> Is it a debhelper bug that it doesn't look like dh-sequence-* packages
> work in B-D-Indep?

debhelper's changelog says

  * dh: Support running addons in "arch-only" or "indep-only" mode by
adding "dh-sequence-ADDON" in Build-Depends-Arch or
Build-Depends-Indep (respectively).  Not all addons support this and
will trigger an error at load time.

So... maybe it's a debhelper bug, or maybe it's a dh-sequence-cli bug?

In this case I would personally suggest going back to explicitly using
"--with cli" if and only if the C# parts are being built, instead of
implicitly via dh-sequence-cli.

d/rules:
> ifneq (,$(wildcard /usr/share/perl5/Debian/Debhelper/Sequence/cli.pm))
> ifeq (,$(filter stage1,$(DEB_BUILD_PROFILES)))

This sort of thing is usually better written in terms of what packages
we want to build, like in this case

DH_ADDONS =
ifneq ($(filter libproxy0.4-cil,$(DO_PACKAGES)),)
WITH_DOTNET = -DWITH_DOTNET=ON
DH_ADDONS += --with cli
else
WITH_DOTNET = -DWITH_DOTNET=OFF
endif

%:
dh $@ $(DH_ADDONS)

We can still use dh-sequence-ADDON for the rest.

smcv

Bug#942056: openvswitch: Incomplete debian/copyright?

[Chris Lamb]

Hi Thomas,

> My last upload, which fixes it, goes again through NEW, as we (re-)added
> the support for ipsec.

This was just ACCEPTED.


Regards,

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

Bug#942119: libproxy: depends on mono for build-arch; mono not universally present

[Thorsten Glaser]

Hi Jeremy,

> Maybe you'd be interested in helping me by digging deeper into this issue?

I can try, but I don’t have experience with Mono either.

> dh-sequence-cli doesn't work in B-D-Indep as I found when I built 0.4.15-6 :

Ouch. Looking at it…

> https://buildd.debian.org/status/logs.php?pkg=libproxy&arch=arm64

… this seems weird. But…

> Is it a debhelper bug that it doesn't look like dh-sequence-* packages
> work in B-D-Indep?

… this is the “clean” target, which is invoked the same no matter
whether building arch, indep or both.

I’d definitely bring this up with the dh7-style debhelper developers.
It appears to auto-detect the sequences used from B-D-*?

One thing you could try is:

ifneq (,$(wildcard /usr/share/perl5/Debian/Debhelper/Sequence/cli.pm))
# … stage1 … endif
# you already have the above lines, new is:
else
DH_ARGS += --without cli
# and the endif you already have
endif

And then:

%:
dh ${DH_ARGS} $@

> (There are definitely a few other ways to work around this issue if
> debhelper won't be changed soon.)

Yeah… the trick is probably finding the right ones and keeping
them working…

Note: you can get a chroot with just the B-D installed on a porterbox,
so you can test this even without uploading.

If you wish, I can also try around on my x32 box (main desktop at work).

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**

Bug#941601: marked as done (rollup 0.56 transition: Add node-rollup-plugin-json to build depends and fix 'format is now output.format' error)

[Debian Bug Tracking System]

Your message dated Thu, 10 Oct 2019 16:49:31 +
with message-id 
and subject line Bug#941601: fixed in leaflet-markercluster 1.4.1~dfsg-7
has caused the Debian Bug report #941601,
regarding rollup 0.56 transition: Add node-rollup-plugin-json to build depends 
and fix 'format is now output.format' error
to be marked as done.

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

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


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

Package: leaflet-markercluster
Version: 1.4.1~dfsg-6
Severity: important
Control: tags -1 patch

It needs the following changes,

diff --git a/debian/control b/debian/control
index 341cd23..09dc90e 100644
--- a/debian/control
+++ b/debian/control
@@ -12,6 +12,7 @@ Build-Depends:
 pigz,
 rename,
 rollup,
+ node-rollup-plugin-json,
 sassc,
 uglifyjs (>= 3),
Standards-Version: 4.3.0

and it still fails,

NODE_ENV=release rollup --config build/rollup-config.js
(!) Some options have been renamed
https://gist.github.com/Rich-Harris/d472c50732dab03efeb37472b08a3f32
entry is now input
moduleName is now output.name
sourceMap is now output.sourcemap
format is now output.format
banner is now output.banner
dest is now output.file

src/index.js → dist/leaflet.markercluster-src.js...
[!] Error: You must specify options.format, which can be one of 'amd', 
'cjs', 'system', 'es', 'iife' or 'umd'

https://rollupjs.org/#format-f-output-format-
Error: You must specify options.format, which can be one of 'amd', 
'cjs', 'system', 'es', 'iife' or 'umd'
   at Object.error [as default] 
(/usr/share/nodejs/rollup/src/utils/error.js:10:15)
   at checkOutputOptions 
(/usr/share/nodejs/rollup/src/rollup/index.js:37:24)
   at normalizeOptions 
(/usr/share/nodejs/rollup/src/rollup/index.js:95:21)

   at generate (/usr/share/nodejs/rollup/src/rollup/index.js:99:41)
   at Object.write 
(/usr/share/nodejs/rollup/src/rollup/index.js:131:32)

   at /usr/share/nodejs/rollup/bin/src/run/build.js:49:27
   at next (/usr/share/nodejs/rollup/src/utils/promise.js:7:32)
   at /usr/share/nodejs/rollup/src/utils/promise.js:10:53
   at process._tickCallback (internal/process/next_tick.js:68:7)
   at Function.Module.runMain (internal/modules/cjs/loader.js:834:11)

After rollup configuration if fixed, I get an error with uglifyjs

uglifyjs --compress --mangle \
--source-map 
"base='/<>/debian/js',content='dist/leaflet.markercluster-src.js.map',url='leaflet.markercluster.min.js.map'" 
\

--output debian/js/leaflet.markercluster.min.js \
-- dist/leaflet.markercluster-src.js
ERROR: No element indexed by 0
   at ArraySet_at [as at] 
(/usr/share/nodejs/source-map/lib/array-set.js:109:9)
   at BasicSourceMapConsumer.SourceMapConsumer_originalPositionFor [as 
originalPositionFor] 
(/usr/share/nodejs/source-map/lib/source-map-consumer.js:673:30)
   at Object.add (eval at  
(/usr/lib/nodejs/uglify-js/tools/node.js:20:1), :12216:32)
   at eval (eval at  
(/usr/lib/nodejs/uglify-js/tools/node.js:20:1), :3921:32)

   at Array.forEach ()
   at OutputStream.flush_mappings (eval at  
(/usr/lib/nodejs/uglify-js/tools/node.js:20:1), :3920:18)
   at Object.print (eval at  
(/usr/lib/nodejs/uglify-js/tools/node.js:20:1), :4025:29)
   at eval (eval at  
(/usr/lib/nodejs/uglify-js/tools/node.js:20:1), :4847:16)
   at doit (eval at  
(/usr/lib/nodejs/uglify-js/tools/node.js:20:1), :4356:13)
   at AST_Var.eval (eval at  
(/usr/lib/nodejs/uglify-js/tools/node.js:20:1), :4363:13)


This was fixed by switching to uglifyjs.terser.

Entire change is here 
https://salsa.debian.org/js-team/leaflet-markercluster/merge_requests/1


--- End Message ---
--- Begin Message ---
Source: leaflet-markercluster
Source-Version: 1.4.1~dfsg-7

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated leaflet-markercluster 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Oct 2019 18:33:51 +0200
Source: leaflet-markercluster
Architecture: sour

Bug#942123: transmission-remote-cli: should this package be removed?

[Sandro Tosi]

Package: transmission-remote-cli
Severity: serious

Hello,
upstream declared, at https://github.com/fagga/transmission-remote-cli that

  transmission-remote-cli is no longer maintained.

  Alternative Transmission TUI clients are tremc (a fork of this project) and 
stig.

so, should we remove this package from Debian? it's python2 only, and it did not
received any upstream maintenance (at least at the current repo) in 3 years,
last Debian upload was in 2014.

If i dont receive a valid reason to keep this package around within a week, i'll
file for its removal.

Regards,
Sandro


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

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

Versions of packages transmission-remote-cli depends on:
ii  python  2.7.16-1

Versions of packages transmission-remote-cli recommends:
pn  python-adns   
pn  python-geoip  
pn  python-ipy
ii  transmission-cli  2.94-2

transmission-remote-cli suggests no packages.

Bug#942119: libproxy: depends on mono for build-arch; mono not universally present

[Jeremy Bicha]

On Thu, Oct 10, 2019 at 12:09 PM Thorsten Glaser  wrote:
> src:libproxy recently gained a B-D-Arch on dh-sequence-cli which
> depends on mono-utils, which isn’t available for the architectures
> mips64el (release), alpha, hppa, hurd-i386, ia64, kfreebsd-amd64,
> kfreebsd-i386, m68k, riscv64, sh4, sparc64, x32, and any new ones.
>
> Please use mono only in B-D-Indep.

Maybe you'd be interested in helping me by digging deeper into this issue?

dh-sequence-cli doesn't work in B-D-Indep as I found when I built 0.4.15-6 :

https://buildd.debian.org/status/logs.php?pkg=libproxy&arch=arm64

Is it a debhelper bug that it doesn't look like dh-sequence-* packages
work in B-D-Indep?

(There are definitely a few other ways to work around this issue if
debhelper won't be changed soon.)

Thanks,
Jeremy

Bug#935753: marked as done (FATAL:memory_linux.cc Out of memory)

[Debian Bug Tracking System]

Your message dated Thu, 10 Oct 2019 18:37:38 +0200
with message-id <87imowy2st.fsf...@turtle.gmx.de>
and subject line Bug fixed in mesa 19.2.1
has caused the Debian Bug report #935753,
regarding FATAL:memory_linux.cc  Out of memory
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.)


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

# Env:
# LD_LIBRARY_PATH=
#PATH=/home/jidanni/bin:/usr/bin:/bin:/usr/local/bin
#GTK_PATH=
#  CHROMIUM_FLAGS= --show-component-extension-options 
--enable-gpu-rasterization --no-default-browser-check --disable-pings 
--media-router=0 --enable-remote-extensions --load-extension=
/usr/bin/gdb /usr/lib/chromium/chromium -x /tmp/chromiumargs.8R4spW
GNU gdb (Debian 8.3-1) 8.3
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/chromium/chromium...
Reading symbols from 
/usr/lib/debug/.build-id/c5/b565ee488296ba155602dafc4904ee021d24ef.debug...
(gdb) handle SIG33 pass nostop noprint
SignalStop  Print   Pass to program Description
SIG33 NoNo  Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/lib/chromium/chromium --show-component-extension-options 
--enable-gpu-rasterization --no-default-browser-check --disable-pings 
--media-router=0 --enable-remote-extensions --load-extension= --single-process 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffec6be700 (LWP 10778)]
[Detaching after fork from child process 10779]
[New Thread 0x7fffebebd700 (LWP 10783)]
[New Thread 0x7fffea3fd700 (LWP 10784)]
[New Thread 0x7fffe9bfc700 (LWP 10785)]
[New Thread 0x7fffe93fb700 (LWP 10786)]
[New Thread 0x7fffe8bfa700 (LWP 10787)]
[New Thread 0x7fffdb7fe700 (LWP 10789)]
[New Thread 0x7fffdbfff700 (LWP 10788)]
[New Thread 0x7fffdaffd700 (LWP 10790)]
[New Thread 0x7fffda7fc700 (LWP 10791)]
[New Thread 0x7fffd9ffb700 (LWP 10792)]
[New Thread 0x7fffe828e700 (LWP 10793)]
[New Thread 0x7fffd8ff9700 (LWP 10795)]
[New Thread 0x7fffb3fff700 (LWP 10796)]
[New Thread 0x7fffd97fa700 (LWP 10794)]
[New Thread 0x7fffb2ffd700 (LWP 10797)]
[New Thread 0x7fffb27fc700 (LWP 10798)]
[New Thread 0x7fffb37fe700 (LWP 10799)]
[New Thread 0x7fffb1ffb700 (LWP 10800)]
[New Thread 0x7fffb17fa700 (LWP 10801)]
[New Thread 0x7fffb0ff9700 (LWP 10802)]
[New Thread 0x7fffabfff700 (LWP 10803)]
[New Thread 0x7fffab7fe700 (LWP 10804)]
[10774:10774:0826/042928.466062:ERROR:system_network_context_manager.cc(670)] 
Cannot use V8 Proxy resolver in single process mode.
[Detaching after fork from child process 10805]
[10774:10802:0826/042928.694828:FATAL:memory_linux.cc(42)] Out of memory.

Thread 22 "Chrome_InProcGp" received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffb0ff9700 (LWP 10802)]
0x713c1081 in raise () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) backtrace
#0  0x713c1081 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x713ac535 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x58edd435 in base::debug::BreakDebugger() ()
#3  0x58e43e98 in logging::LogMessage::~LogMessage() ()
#4  0x58e64e4d in base::(anonymous namespace)::OnNoMemorySize(unsigned 
long) [clone .constprop.237] ()
#5  0x58ef0c85 in calloc ()
#6  0x7fffaa96c7e9 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#7  0x7fffaa45f4b9 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#8  0x7fffaa4cd4b4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#9  0x7fffd87ca1b5 in ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
#10 0x7fffd87b6ec9 in ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
#11 0x7fffd87b2a64 in ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
#12 0x7fffd87b2f

Bug#942119: libproxy: depends on mono for build-arch; mono not universally present

[Thorsten Glaser]

Source: libproxy
Version: 0.4.15-7
Severity: serious
Justification: FTBFS on release architecture

src:libproxy recently gained a B-D-Arch on dh-sequence-cli which
depends on mono-utils, which isn’t available for the architectures
mips64el (release), alpha, hppa, hurd-i386, ia64, kfreebsd-amd64,
kfreebsd-i386, m68k, riscv64, sh4, sparc64, x32, and any new ones.

Please use mono only in B-D-Indep.

Thanks,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**

Processed: bug 942114 is forwarded to https://github.com/ganeti/instance-debootstrap/pull/6

[Debian Bug Tracking System]

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

> forwarded 942114 https://github.com/ganeti/instance-debootstrap/pull/6
Bug #942114 [ganeti-instance-debootstrap] cache fails to store capabilities 
correctly
Set Bug forwarded-to-address to 
'https://github.com/ganeti/instance-debootstrap/pull/6'.
> thanks
Stopping processing here.

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

Bug#940973: libarchive-zip-perl breaks strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember

[gregor herrmann]

On Thu, 10 Oct 2019 06:30:52 -0700, tony mancill wrote:

> I have recently started observing build failures for packages that use
> jh_manifest (which is part of Debian's javahelper).  All of the failures
> I have seen so far have the same symptom, namely that the manifest
> cannot be extracted from the JAR, which is actually a Zip archive.  

Ouch.
Thanks for mentioning this issue.

> >jh_classpath
> > error: No member named $memberName 
> >  at /usr/share/perl5/Archive/Zip/Archive.pm line 411.
> > 
> > Archive::Zip::Archive::contents(Archive::Zip::Archive=HASH(0x55bbbdadedd0), 
> > "META-INF/MANIFEST.MF") called at /usr/bin/jh_manifest line 297
> > main::update_jar("/<>/debian/li"..., undef) called at 
> > /usr/bin/jh_manifest line 147
> > Could not read manifest from 
> > /<>/debian/libquartz2-java/usr/share/java/quartz2-2.3.0.jar 
> > (2):  at /usr/bin/jh_manifest line 298.
> > jh_classpath: jh_manifest -plibquartz2-java 
> > --classpath=/usr/share/java/slf4j-api.jar 
> > debian/libquartz2-java/usr/share/java/quartz2.jar returned exit code 255
> > make: *** [debian/rules:4: binary] Error 255
> 
> I don't know if this is the same issue but wanted to mention it here,
> since it seems potentially related.  I'd be glad to provide more
> debugging information or testing if that would help.  libquartz2-java is
> an example of a source package that exhibits this issue.

Salvatore has uploaded libarchive-zip-perl 1.67-1 right now. Could
you try and check with this version? If there's still a problem I'm
happy to debug this together and forward it upstream.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#942118: smartmontools: fails to restart during upgrade, breaks dpkg

[Thorsten Glaser]

Package: smartmontools
Version: 7.0-1
Severity: grave
Justification: renders package unusable

[…]
(Reading database ... 302786 files and directories currently installed.)
Preparing to unpack .../00-smartmontools_7.0-1_amd64.deb ...
Unpacking smartmontools (7.0-1) over (6.6-1+b1) ...
[…]
Setting up smartmontools (7.0-1) ...
Installing new version of config file /etc/default/smartmontools ...
Installing new version of config file /etc/init.d/smartmontools ...
Installing new version of config file /etc/smartd.conf ...
Removing obsolete conffile /etc/smartmontools/run.d/10powersave-notify ...
insserv: warning: current stop runlevel(s) (1) of script `smartmontools' 
overrides LSB defaults (0 1 6).
Restarting S.M.A.R.T. daemon: smartd failed!
invoke-rc.d: initscript smartmontools, action "restart" failed.
dpkg: error processing package smartmontools (--configure):
 installed smartmontools package post-installation script subprocess returned 
error exit status 1
[…]
Errors were encountered while processing:
 smartmontools
E: Sub-process /usr/bin/dpkg returned an error code (1)
100|root@ci-busyapps:~ # dpkg -a --configure
Setting up smartmontools (7.0-1) ...
insserv: warning: current stop runlevel(s) (1) of script `smartmontools' 
overrides LSB defaults (0 1 6).
Restarting S.M.A.R.T. daemon: smartd failed!
invoke-rc.d: initscript smartmontools, action "restart" failed.
dpkg: error processing package smartmontools (--configure):
 installed smartmontools package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 smartmontools



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

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

Versions of packages smartmontools depends on:
ii  debianutils  4.9
ii  init-system-helpers  1.57
ii  libc62.29-2
ii  libcap-ng0   0.7.9-2+b1
ii  libgcc1  1:9.2.1-9
ii  libselinux1  2.9-2+b2
ii  libstdc++6   9.2.1-9
ii  libsystemd0  242-7
ii  lsb-base 11.1.0

smartmontools recommends no packages.

Versions of packages smartmontools suggests:
ii  bsd-mailx [mailx]  8.1.2-0.20180807cvs-1+b1
ii  curl   7.66.0-1
ii  gpg2.2.17-3
pn  gsmartcontrol  
ii  lynx   2.9.0dev.4-1
pn  smart-notifier 
ii  wget   1.20.3-1+b1

-- no debconf information

Bug#942114: cache fails to store capabilities correctly

[Antoine Beaupré]

Control: tags -1 +patch

Here's a patch to fix this, also available in:

https://salsa.debian.org/ganeti-team/ganeti-instance-debootstrap/merge_requests/1

-- 
You are absolutely deluded, if not stupid, if you think that a
worldwide collection of software engineers who can't write operating
systems or applications without security holes, can then turn around
and suddenly write virtualization layers without security holes.
- Theo de Raadt
>From cd34bcc48a2af92f484535b81fba2d46dad1dbb6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= 
Date: Thu, 10 Oct 2019 11:07:51 -0400
Subject: [PATCH] respect Linux capabilities(7) in cache

The default GNU tar configuration does not carry fancy extended
attributes and that is where, among other things, stuff like Linux
capabilities(7) are stored. This is kind of important because that's
how ping(8) works for regular users.

We shove --selinux and --acls in there while we're at it, because why
not. We never know what the future might bring, and it seems
silly *not* to create a complete archive.

Note that --xattrs-include='*' is important because, by default, GNU
tar will not include capabilities /even/ if --xattrs is specified on
the commandline, see this bug report for details:

https://bugzilla.redhat.com/show_bug.cgi?id=771927
---
 create | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/create b/create
index 607bab2..7526e71 100755
--- a/create
+++ b/create
@@ -83,7 +83,7 @@ if [ "$CLEAN_CACHE" -a -d "$CACHE_DIR" ]; then
 fi
 
 if [ -f "$CACHE_FILE" ]; then
-  tar xf "$CACHE_FILE" -C $TMPDIR
+  tar --acls --selinux --xattrs --xattrs-include='*' -x -f "$CACHE_FILE" -C $TMPDIR
 else
   if [ "$PROXY" ]; then
 export http_proxy="$PROXY"
@@ -109,7 +109,7 @@ else
 
   if [ "$GENERATE_CACHE" = "yes" ]; then
 TMP_CACHE=`mktemp "${CACHE_FILE}.XX"`
-tar cf "$TMP_CACHE" -C $TMPDIR .
+tar --acls --selinux --xattrs --xattrs-include='*' -c -f "$TMP_CACHE" -C $TMPDIR .
 mv -f "$TMP_CACHE" "$CACHE_FILE"
   fi
 fi
-- 
2.20.1

Processed: Re: Bug#942114 cache fails to store capabilities correctly

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #942114 [ganeti-instance-debootstrap] cache fails to store capabilities 
correctly
Added tag(s) patch.

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

Bug#942114: cache fails to store capabilities correctly

[Antoine Beaupre]

Package: ganeti-instance-debootstrap
Version: 0.16-6
Severity: grave

It seems that ganeti-instance-deboostrap fails to properly cache the
filesystem after the first creation. This leads to stuff like
`/usr/bin/ping` having the wrong permissions. On a healthy system,
installed without caching, it looks like this:

root@test01:~# getcap /usr/bin/ping
/usr/bin/ping = cap_net_raw+ep
root@test01:~#

But if that instance is removed and recreated, it then looks like this:

root@test01:~# getcap /usr/bin/ping
root@test01:~#

This is "grave" because capabilities are a serious issue. There could
be suid files that are restricted by capabilities (or the
opposite). We just don't quite know and this looks really wrong. At
best it makes ping unusable by regular users, and that's still a
serious issue.

Inspection of the cache file confirms the capabilities are not stored
correctly:

root@fsn-node-02:~# tar fx 
/var/cache/ganeti-instance-debootstrap/cache-buster-amd64.tar ./usr/bin/ping
root@fsn-node-02:~# getcap ./usr/bin/ping
root@fsn-node-02:~# 

A.

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

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_CA.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 ganeti-instance-debootstrap depends on:
ii  debootstrap  1.0.114
ii  dump 0.4b46-5
ii  e2fsprogs1.44.5-1+deb10u2
ii  fdisk2.33.1-0.1
ii  kpartx   0.7.9-3
ii  util-linux   2.33.1-0.1

ganeti-instance-debootstrap recommends no packages.

ganeti-instance-debootstrap suggests no packages.

-- debconf-show failed

Bug#916195: marked as done (python3-qwt: make optional the python3-pyqt4 dependency)

[Debian Bug Tracking System]

Your message dated Thu, 10 Oct 2019 14:27:04 +
with message-id 

and subject line 
has caused the Debian Bug report #916195,
regarding python3-qwt: make optional the python3-pyqt4 dependency
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.)


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

Dear Maintainer,

When installing python3-qwt from Debian stretch (using apt-get install), 
python3-pyqt4 is also installed, even if python3-pyqt5 is available.

After testing python3-qwt with python3-pyqt5 and a dummy/mock package of 
python3-pyqt4 
(allowing to bypass the dependency on it), the impression is that python3-qwt 
is working well with python3-pyqt5.

The dependency on python3-pyqt4 should be made optional. 
If python3-pyqt5 is already installed in the system, python3-pyqt4 should not 
be installed.


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

Kernel: Linux 4.9.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=locale: Cannot set LC_ALL to default 
locale: No such file or directory
ANSI_X3.4-1968), LANGUAGE=en_US (charmap=locale: Cannot set LC_ALL to default 
locale: No such file or directory
ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages python3-qwt depends on:
ii  python33.5.3-1
ii  python3-numpy  1:1.12.1-3
ii  python3-pyqt4  4.11.4+dfsg-2+b1

python3-qwt recommends no packages.

python3-qwt suggests no packages.

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US",
LC_ALL = (unset),
LC_MEASUREMENT = "ca_ES.UTF-8",
LC_MONETARY = "ca_ES.UTF-8",
LC_COLLATE = "ca_ES.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_ALL to default locale: No such file or directory
--- End Message ---
--- Begin Message ---
This package does not pull qt4 by himself--- End Message ---

Bug#940973: libarchive-zip-perl breaks strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember

[tony mancill]

On Tue, Oct 08, 2019 at 11:15:38PM +0200, gregor herrmann wrote:
> Control: tag -1 - fixed-upstream
> COntrol: notforwarded -1
> 
> On Tue, 08 Oct 2019 14:10:19 -0700, Chris Lamb wrote:
> 
> > This has apparently been fixed (again) upstream in version 1.67:
> > 
> >   
> > https://github.com/redhotpenguin/perl-Archive-Zip/issues/51#issuecomment-539679696
> 
> Thanks for the notice but I'm afraid this is a different issue, and
> "our" problem is not yet fixed.
> (I tried with some of the merge requests earlier, and Salvatore tried
> today with the 1.67 release.)
> 
> I guess now that 1.67 is out we should open a separate issue upstream
> …

Hi Gregor,

I have recently started observing build failures for packages that use
jh_manifest (which is part of Debian's javahelper).  All of the failures
I have seen so far have the same symptom, namely that the manifest
cannot be extracted from the JAR, which is actually a Zip archive.  An
example build error:

>jh_classpath
> error: No member named $memberName 
>  at /usr/share/perl5/Archive/Zip/Archive.pm line 411.
>   
> Archive::Zip::Archive::contents(Archive::Zip::Archive=HASH(0x55bbbdadedd0), 
> "META-INF/MANIFEST.MF") called at /usr/bin/jh_manifest line 297
>   main::update_jar("/<>/debian/li"..., undef) called at 
> /usr/bin/jh_manifest line 147
> Could not read manifest from 
> /<>/debian/libquartz2-java/usr/share/java/quartz2-2.3.0.jar (2): 
>  at /usr/bin/jh_manifest line 298.
> jh_classpath: jh_manifest -plibquartz2-java 
> --classpath=/usr/share/java/slf4j-api.jar 
> debian/libquartz2-java/usr/share/java/quartz2.jar returned exit code 255
> make: *** [debian/rules:4: binary] Error 255

I don't know if this is the same issue but wanted to mention it here,
since it seems potentially related.  I'd be glad to provide more
debugging information or testing if that would help.  libquartz2-java is
an example of a source package that exhibits this issue.

Cheers,
tony


signature.asc
Description: PGP signature

Bug#931944: vtk7: FTBFS with PROJ 6

[peter green]

Disabling the PROJ support was not an option as it was for vtk6. You may
want to reinstate the embedded copy and use that instead.

It looks like a commit doing this was made on salsa on august 6th 
https://salsa.debian.org/science-team/vtk7/commit/19d6e5e2e02cbd10404dd96e750370546feaa82b

Is there something blocking an upload?

Bug#942105: Can not active fcitx after Debian testing upgraded today

[gulfstream]

Package: fcitx
Version: 1:4.2.9.6-6
Severity: grave


I upgrade my Debian testing just now, and I found that the fcitx can not be 
used. When I press ctrl+Space, the Chinese input UI can not be actived.

Hope this problem can be resolve soon.


Best regards,
Gulfstream



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), 
LANGUAGE=zh_CN.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 fcitx depends on:
ii  fcitx-bin  1:4.2.9.6-6
ii  fcitx-data 1:4.2.9.6-6
ii  fcitx-modules  1:4.2.9.6-6

Versions of packages fcitx recommends:
ii  fcitx-config-gtk0.4.10-2
ii  fcitx-frontend-all  1:4.2.9.6-6
ii  fcitx-ui-classic1:4.2.9.6-6
ii  im-config   0.43-1

Versions of packages fcitx suggests:
pn  fcitx-m17n   
pn  fcitx-tools  

-- no debconf information

Bug#942101: python-msrest build accesses the network during the build

[Matthias Klose]

Package: src:python-msrest
Version: 0.6.1-1
Severity: serious
Tags: sid bullseye

according to
https://launchpadlibrarian.net/441507516/buildlog_ubuntu-eoan-amd64.python-msrest_0.6.1-1_BUILDING.txt.gz

the tests access some infrastructure.  The build must not rely on the network, 
the autopkg tests can.  Usually the Debian buildds don't check for network access.

Bug#942077: /usr/bin/budgie-desktop: Update to GNOME 3.34 breaks Budgie

[Willem Mulder]

On Wed, 9 Oct 2019 23:41:37 +0100 David Mohammed
 wrote:
> many thanks for the suggested changes.
>
> Please can you let me know a bit more about your setup to clarify why
> the patch is required.
>

> Have you got both gnome-shell and budgie-desktop as sessions?

I do, and I suspect that's the reason why it breaks. gnome-session now
starts components through systemd, one of which is
/usr/lib/systemd/user/gnome-shell-x11.service. This unit starts
gnome-shell regardless of whether org.gnome.Shell is specified in the
session file (/usr/share/gnome-session/sessions/). Ultimately this is a
bug in GNOME (and I should probably report it as such), but this is a
quick workaround without much impact, while the bug in GNOME is not easy
to fix and probably requires upstream involvement.

> Are you using GDM3 for your login manager or lightdm login manager?

I've tested this with lightdm, but any display manager should exhibit
this behaviour, since it concerns /usr/bin/budgie-desktop, which is
specified in the session file (/usr/share/xsessions/budgie-desktop.desktop).

> thanks
>
> On Wed, 9 Oct 2019 at 23:24, Willem Mulder
 wrote:
> [...]

Bug#942056: openvswitch: Incomplete debian/copyright?

[Thomas Goirand]

On 10/9/19 6:32 PM, Chris Lamb wrote:
> Source: openvswitch
> Version: 2.11.0+2019.06.25+git.9ebe795035+ds1-1
> Severity: serious
> Justication: Policy §12.5
> X-Debbugs-CC: Thomas Goirand , ftpmas...@debian.org
> 
> Hi,
> 
> I just ACCEPTed openvswitch from NEW but noticed it was missing 
> attribution in debian/copyright for at least Ericsson.
> 
> This is in no way exhaustive so please check over the entire package 
> carefully and address these on your next upload.

Hi,

Thanks again.

My last upload, which fixes it, goes again through NEW, as we (re-)added
the support for ipsec.

Cheers,

Thomas Goirand (zigo)

Bug#941267: ukwm can't start, dmesg has segfault error info libukwm-cogl-1.so [b5b4c000+68000]

[Faris Xiao]

Thanks for you feedback!

在 2019/10/10 上午3:38, Andreas Beckmann 写道:

> testing and sid now have 1.1.11-1+b2 - does the crash still happen with
> these versions that were rebuilt against newer libraries? (Don't forget
> to upgrade the libukwm-1-0 package, too.)

After I upgrade to the newer versions in testing,the crash still happen.

[四 10月 10 15:40:06 2019] ukwm[4221]: segfault at 38 ip b5baf084 sp
bfaba2dc error 4 in libukwm-cogl-1.so[b5b71000+68000]
[四 10月 10 15:40:06 2019] Code: 00 8d 74 26 00 90 8b 44 24 04 8b 40 4c 8b
40 48 85 c0 74 02 ff e0 31 c0 c3 8d b4 26 00 00 00 00 8d b6 00 00 00 00
8b 44 24 04 <8b> 40 38 c3 8d b4 26 00 00 00 00 90 8b 44 24 04 8b 40 3c
c3 8d b4
[四 10月 10 15:42:15 2019] ukwm[4330]: segfault at 38 ip b5bc4084 sp
bfc38b6c error 4 in libukwm-cogl-1.so[b5b86000+68000]
[四 10月 10 15:42:15 2019] Code: 00 8d 74 26 00 90 8b 44 24 04 8b 40 4c 8b
40 48 85 c0 74 02 ff e0 31 c0 c3 8d b4 26 00 00 00 00 8d b6 00 00 00 00
8b 44 24 04 <8b> 40 38 c3 8d b4 26 00 00 00 00 90 8b 44 24 04 8b 40 3c
c3 8d b4


My packages version is following:

apt search ukwm
Sorting... Done
Full Text Search... Done
gir1.2-ukwm-1/testing,now 1.1.11-1+b2 i386 [installed]
  GObject introspection data for Ukwm

libukwm-1-0/testing,now 1.1.11-1+b2 i386 [installed]
  window manager library from the Ukwm window manager

libukwm-1-dev/testing 1.1.11-1+b2 i386
  Development files for the Ukwm window manager

ukwm/testing,now 1.1.11-1+b2 i386 [installed,automatic]
  lightweight GTK+ window manager

ukwm-common/stable,testing,now 1.1.11-1 all [installed]
  shared files for the Ukwm window manager

>
>

> Can you reproduce the segfault in a clean stable environment?

Yes.The segfault can reproduce in a clean stable environment.Infact,I
find this bug in stable at first.

[  286.489542] show_signal_msg: 2 callbacks suppressed
[  286.489552] ukwm[925]: segfault at 38 ip b5b73084 sp bfe25b8c error 4
in libukwm-cogl-1.so[b5b35000+68000]
[  286.489577] Code: 00 8d 74 26 00 90 8b 44 24 04 8b 40 4c 8b 40 48 85
c0 74 02 ff e0 31 c0 c3 8d b4 26 00 00 00 00 8d b6 00 00 00 00 8b 44 24
04 <8b> 40 38 c3 8d b4 26 00 00 00 00 90 8b 44 24 04 8b 40 3c c3 8d b4
[  412.498816] fcitx-dbus-watc[902]: segfault at 70725 ip b7e906b7 sp
bfdd11a0 error 4 in libdbus-1.so.3.19.11[b7e6c000+31000]
[  412.498842] Code: fd ff 83 c4 10 5b 5e 5f c3 8d b4 26 00 00 00 00 8d
76 00 53 e8 da d6 fd ff 81 c3 ca f1 02 00 83 ec 08 8b 44 24 10 85 c0 74
11 <0f> b6 40 20 83 e0 01 83 c4 08 5b c3 8d 74 26 00 90 8d 83 0b 2d fe
[  853.126075] e100 :02:08.0 enp2s8: NIC Link is Up 100 Mbps Full Duplex
[  853.126224] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s8: link becomes ready
[ 1412.900840] ukwm[2667]: segfault at 38 ip b5b5e9f4 sp bfafd97c error
4 in libukwm-cogl-1.so[b5b2+68000]
[ 1412.900869] Code: 00 8d 74 26 00 90 8b 44 24 04 8b 40 4c 8b 40 48 85
c0 74 02 ff e0 31 c0 c3 8d b4 26 00 00 00 00 8d b6 00 00 00 00 8b 44 24
04 <8b> 40 38 c3 8d b4 26 00 00 00 00 90 8b 44 24 04 8b 40 3c c3 8d b4

The following is my clean stable environment about ukwm packages version
info:

apt search ukwm
Sorting... Done
Full Text Search... Done
gir1.2-ukwm-1/stable 1.1.11-1 i386
  GObject introspection data for Ukwm

libukwm-1-0/stable,now 1.1.11-1 i386 [installed,automatic]
  window manager library from the Ukwm window manager

libukwm-1-dev/stable 1.1.11-1 i386
  Development files for the Ukwm window manager

ukwm/stable,now 1.1.11-1 i386 [installed]
  lightweight GTK+ window manager

ukwm-common/stable,now 1.1.11-1 all [installed,automatic]
  shared files for the Ukwm window manager

Is there possible  about hardware issue,or kernel driver bug,or gl bug?

>
>
> Andreas

-- 
肖盛文  Faris Xiao
Debian 中文套件一键安装 https://gitee.com/atzlinux/debian-cn




signature.asc
Description: OpenPGP digital signature

Bug#939838: marked as done (nftables: please apply upstream commits to fix firewalld testsuite failures)

[Debian Bug Tracking System]

Your message dated Thu, 10 Oct 2019 10:50:07 +0200
with message-id <7aac7045-e382-3443-ee86-066cf4dd8...@debian.org>
and subject line Bug#939838: fixed in nftables 0.9.2-2
has caused the Debian Bug report #939838,
regarding nftables: please apply upstream commits to fix firewalld testsuite 
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.)


-- 
939838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nftables
Version: 0.9.2-1
Severity: serious
Justification: breaks another package from working correctly

Hello, according to firewalld upstream devs, we need 2 commits to fixup their 
test failures.
I also cherry-picked another hotfix, because it seemed important to me
(note, I just uploaded them in Ubuntu, I didn't run the tests yet)
commit ids:
- 2e57d4ff79fa166f2dea3686ca4fe051b656a8d2
- 03478af1bea03eafd43df94334cb001ed26145a3
- 1e2aae7d73ce733650d78da452d45d6c5498cc33

patch here:

http://launchpadlibrarian.net/441272565/nftables_0.9.2-1_0.9.2-1ubuntu1.diff.gz


thanks

Gianfranco
--- End Message ---
--- Begin Message ---
Control: fixed -1 nftables/0.9.2-2

I made a mistake when creating the changelog for nftables and closed another
bug, but #939838 is the bug this upload is really closing.

sorry for the noise.

On Wed, 09 Oct 2019 18:04:35 + Arturo Borrero Gonzalez 
wrote:
> Source: nftables
> Source-Version: 0.9.2-2
> 
> We believe that the bug you reported is fixed in the latest version of
> nftables, 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.
> Arturo Borrero Gonzalez  (supplier of updated nftables 
> 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: Wed, 09 Oct 2019 19:40:31 +0200
> Source: nftables
> Architecture: source
> Version: 0.9.2-2
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Netfilter Packaging Team 
> 
> Changed-By: Arturo Borrero Gonzalez 
> Closes: 939838
> Changes:
>  nftables (0.9.2-2) unstable; urgency=medium
>  .
>[ Konstantin Demin ]
>* [9c626fc] d/rules: build less verbose if requested
>  .
>[ Arturo Borrero Gonzalez ]
>* [ba5d4d0] nftables: add Suggests: firewalld
>* [f8bea94] nftables: add upstream patches to address firewalld testsuite
>  failures (Closes: #939838)
>* [35f35af] src:nftables: bump std-version to 4.4.1
> Checksums-Sha1:
>  69a45bb393f0bdab61b3a1be473872343b100e2a 2706 nftables_0.9.2-2.dsc
>  830124abc930537bcd897e2ad58a43d72eab6d2c 21112 nftables_0.9.2-2.debian.tar.xz
>  1d79c4eff3c74548dde645804560a356c0e0307d 7886 
> nftables_0.9.2-2_amd64.buildinfo
> Checksums-Sha256:
>  1b2c1bde15711e499f15dcda97d286e10c744a03702c98a966a482914280ea2b 2706 
> nftables_0.9.2-2.dsc
>  bc53658d3426dcc243507b0213bdf348a05b3057b1a5da93111356b868e43564 21112 
> nftables_0.9.2-2.debian.tar.xz
>  91d1462c6fd1243782467153e79e2c8a0f668d9ba4f7d91381834047753c46b6 7886 
> nftables_0.9.2-2_amd64.buildinfo
> Files:
>  d78f006e6d56c3f93d1e9f1a7cfe9899 2706 net important nftables_0.9.2-2.dsc
>  4336636e266af563f4406a90915aa4fe 21112 net important 
> nftables_0.9.2-2.debian.tar.xz
>  7243b58c29320398b3f81d185bdca1a0 7886 net important 
> nftables_0.9.2-2_amd64.buildinfo
> 
> -BEGIN PGP SIGNATURE End Message ---

Bug#942070: marked as done (gnome-shell-extension-workspaces-to-dock: Must be updated to work with GNOME 3.34)

[Debian Bug Tracking System]

Your message dated Thu, 10 Oct 2019 08:40:05 +
with message-id 
and subject line Bug#942070: fixed in gnome-shell-extension-workspaces-to-dock 
52-1
has caused the Debian Bug report #942070,
regarding gnome-shell-extension-workspaces-to-dock: Must be updated to work 
with GNOME 3.34
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.)


-- 
942070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-workspaces-to-dock
Version: 51-1
Severity: grave
Tags: upstream
Justification: renders package unusable
User: de...@kali.org
Usertags: origin-kali

Please package version 52 that is documented to work with GNOME Shell
3.34.

The current version can be installed and loaded but it entirely breaks the
activities overview.

Thank you.

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

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

Versions of packages gnome-shell-extension-workspaces-to-dock depends on:
ii  gnome-shell  3.34.0-2

gnome-shell-extension-workspaces-to-dock recommends no packages.

gnome-shell-extension-workspaces-to-dock suggests no packages.
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-workspaces-to-dock
Source-Version: 52-1

We believe that the bug you reported is fixed in the latest version of
gnome-shell-extension-workspaces-to-dock, 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 942...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated 
gnome-shell-extension-workspaces-to-dock package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Oct 2019 09:28:44 +0200
Source: gnome-shell-extension-workspaces-to-dock
Architecture: source
Version: 52-1
Distribution: unstable
Urgency: high
Maintainer: Debian GNOME Maintainers 

Changed-By: Raphaël Hertzog 
Closes: 942070
Changes:
 gnome-shell-extension-workspaces-to-dock (52-1) unstable; urgency=high
 .
   * Team upload
   * New upstream release
   * Update for gnome-shell 3.34 (Closes: #942070)
   * Bump Standards-Version to 4.4.1
Checksums-Sha1:
 9f4e4e5afa6f709388736cc438350b785eb1ec0f 2004 
gnome-shell-extension-workspaces-to-dock_52-1.dsc
 adc97f728e86539f3d0499c67dd6c154b3e718bf 5293381 
gnome-shell-extension-workspaces-to-dock_52.orig.tar.gz
 09dc451aca48307df244dbe2eac15ff9b271c513 2372 
gnome-shell-extension-workspaces-to-dock_52-1.debian.tar.xz
 c7f78c19e22e6c28cb9543ef31138646fd5c9257 6050 
gnome-shell-extension-workspaces-to-dock_52-1_source.buildinfo
Checksums-Sha256:
 660dea9124a0cd4cfe39c15a16935dab5934b5259c8df0fc19638982f7b77f9e 2004 
gnome-shell-extension-workspaces-to-dock_52-1.dsc
 cda2690138b28d0cee579b84d68dab4e82dc0ab656a9e2ae79e82976af1a3c3d 5293381 
gnome-shell-extension-workspaces-to-dock_52.orig.tar.gz
 68092a70de46cebb71bfb13460a574ced2d6d5c9c14afd6cc2671a00cfefdaf6 2372 
gnome-shell-extension-workspaces-to-dock_52-1.debian.tar.xz
 fe7acdc391537ef316589099051e99cf13d40dc85e51c9c2586b67fd44a29cbf 6050 
gnome-shell-extension-workspaces-to-dock_52-1_source.buildinfo
Files:
 2b219be5458310b3e5ad36f105936423 2004 gnome optional 
gnome-shell-extension-workspaces-to-dock_52-1.dsc
 f9d125c1a95dbc4465d40a9549c29044 5293381 gnome optional 
gnome-shell-extension-workspaces-to-dock_52.orig.tar.gz
 d23dfb31422564a5a6fb87bd1bf0bcb1 2372 gnome optional 
gnome-shell-extension-workspaces-to-dock_52-1.debian.tar.xz
 a2ccda713836ec8aa3c98e3254ed8854 6050 gnome optional 
gnome-shell-extension-workspaces-to-dock_52-1_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Signed by Raphael Hertzog

iQEzBAEBCgAdFiEE1823g1EQnhJ

Bug#942093: libdbd-mysql-perl: flaky autopkgtest: Out of memory!

[Paul Gevers]

Source: libdbd-mysql-perl
Version: 4.050-2
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear Perl team,

With a recent upload of perl the autopkgtest of libdbd-mysql-perl failed
in testing when that autopkgtest was run with the binary packages of
perl from unstable. However, when the test was retried, the test passed.
I looked into the history of your autopkgtest and it fails very regularly.

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests. Please either fix the test to be more robust, or check if the
required memory is available and exit with code 77 and mark you test as
skippable, or use the "flaky" restriction for the offending test until a
solution has been found.

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

I'll have the migration software ignore the results of your autopkgtest
until this bug is fixed.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/libd/libdbd-mysql-perl/3127805/log.gz

t/40server_prepare.t 
1..31
ok 1 - connecting
ok 2 - making slate clean
ok 3 - creating table
ok 4 - loading data
ok 5
ok 6
ok 7 - binding parameter
ok 8 - fetching data
ok 9
ok 10
ok 11 - cleaning up
ok 12 - making slate clean
ok 13 - creating test table
ok 14
ok 15 - binding int
ok 16 - binding smallint
ok 17 - binding tinyint
ok 18 - binding bigint
ok 19 - inserting data
ok 20
ok 21 - cleaning up
ok 22 - making slate clean
ok 23 - creating test table
ok 24
ok 25 - insert t3
Out of memory!
Out of memory!



signature.asc
Description: OpenPGP digital signature

Bug#942059: gcc-9-cross: uses “long” as “time_t” leading to failure on most new 32-bit architectures

[Matthias Klose]

Control: severity -1 important
Control: reassign -1 src:gcc-9-cross-ports

As always, I appreciate your detailed analysis, level of detail (including the 
gcc-9-source version number), and thoroughly written bug report.  No, most 32bit 
archs build fine, it's just x32 having that issue.


On 09.10.19 19:13, Thorsten Glaser wrote:

Source: gcc-9-cross
Version: 12
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)


x86_64-linux-gnux32-g++-9 -fno-PIE -c -g -I-I../../src/gcc/gm2 -Igm2 
-I../../src/gcc/gm2/gm2-gcc -Igm2/gm2-gcc   -g -O2 -DIN_GCC  
-DCROSS_DIRECTORY_STRUCTURE   -fno-exceptions -fno-rtti 
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings 
-Wcast-qual-DHAVE_CONFIG_H -I. -Igm2 -I../../src/gcc -I../../src/gcc/gm2 
-I../../src/gcc/../include -I../../src/gcc/../libcpp/include  
-I../../src/gcc/../libdecnumber -I../../src/gcc/../libdecnumber/bid 
-I../libdecnumber -I../../src/gcc/../libbacktrace   -I. -Igm2 -I../../src/gcc 
-I../../src/gcc/gm2 -I../../src/gcc/../include 
-I../../src/gcc/../libcpp/include  -I../../src/gcc/../libdecnumber 
-I../../src/gcc/../libdecnumber/bid -I../libdecnumber 
-I../../src/gcc/../libbacktrace  ../../src/gcc/gm2/gm2-lang.c -o gm2/gm2-lang.o
../../src/gcc/gm2/m2.flex: In function 'void handleDate()':
../../src/gcc/gm2/m2.flex:354:24: error: cannot convert 'long int*' to 
'time_t*' {aka 'long long int*'}
   354 |   time_t  clock = time((long *)0);
   |^
   ||
   |long int*
In file included from ../../src/gcc/system.h:337,
  from ../../src/gcc/gm2/gm2-gcc/gcc-consolidation.h:23,
  from ../../src/gcc/gm2/m2.flex:22:
/usr/include/time.h:75:29: note:   initializing argument 1 of 'time_t 
time(time_t*)'
75 | extern time_t time (time_t *__timer) __THROW;
   | ^~~
make[5]: *** [../../src/gcc/gm2/Make-lang.in:1124: 
gm2/gm2-compiler-boot/m2flex.o] Error 1

Processed: Re: Bug#942059: gcc-9-cross: uses “long” as “time_t” leading to failure on most new 32-bit architectures

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #942059 [src:gcc-9-cross] gcc-9-cross: uses “long” as “time_t” leading to 
failure on most new 32-bit architectures
Severity set to 'important' from 'serious'
> reassign -1 src:gcc-9-cross-ports
Bug #942059 [src:gcc-9-cross] gcc-9-cross: uses “long” as “time_t” leading to 
failure on most new 32-bit architectures
Bug reassigned from package 'src:gcc-9-cross' to 'src:gcc-9-cross-ports'.
No longer marked as found in versions gcc-9-cross/12.
Ignoring request to alter fixed versions of bug #942059 to the same values 
previously set

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

Bug#941674: marked as done (gnome-shell-extension-dashtodock: Not working)

[Debian Bug Tracking System]

Your message dated Thu, 10 Oct 2019 07:34:11 +
with message-id 
and subject line Bug#941674: fixed in gnome-shell-extension-dashtodock 67-1
has caused the Debian Bug report #941674,
regarding gnome-shell-extension-dashtodock: Not working
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.)


-- 
941674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-dashtodock
Version: 66-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

Latest upgrade to Gnome 3.34

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

//

   * What was the outcome of this action?

Dashtodock is not working and https://extensions.gnome.org/local/ report an
error.

Maybe due to this error, at every error all extensions are disabled and I am
forced to activate them by hand by Gnome Tweak Tool.

I don't know how to debug this issue, but, if necessary, tell me how to do it
and I will do, if possible.

   * What outcome did you expect instead?

Dashtodock working. ;-)

Thank you very much in advance,
Domenico



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=it_IT.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-shell-extension-dashtodock depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.34.0-1
ii  gir1.2-clutter-1.0   1.26.2+dfsg-12
ii  gnome-shell  3.34.0-2

gnome-shell-extension-dashtodock recommends no packages.

gnome-shell-extension-dashtodock suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-dashtodock
Source-Version: 67-1

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

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated 
gnome-shell-extension-dashtodock package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Oct 2019 08:56:56 +0200
Source: gnome-shell-extension-dashtodock
Architecture: source
Version: 67-1
Distribution: unstable
Urgency: high
Maintainer: Debian GNOME Maintainers 

Changed-By: Raphaël Hertzog 
Closes: 941674
Changes:
 gnome-shell-extension-dashtodock (67-1) unstable; urgency=high
 .
   * Team upload
   * New upstream release
   * Update for GNOME Shell 3.34 (Closes: #941674)
   * Drop Testsuite field as there is no debian/tests/control
   * Update Standards-Version to 4.4.1
Checksums-Sha1:
 e125a82e86c1ed74dc12a534333d5c53665dd864 1902 
gnome-shell-extension-dashtodock_67-1.dsc
 62f87bed8229b17bf29fb1ca71a0837c597ba3af 309712 
gnome-shell-extension-dashtodock_67.orig.tar.gz
 0b1b22f01850d3a694bee2142e810a81757a8456 3712 
gnome-shell-extension-dashtodock_67-1.debian.tar.xz
 c5c8a770f17f47b8c509a6849cae654622ef7064 6010 
gnome-shell-extension-dashtodock_67-1_source.buildinfo
Checksums-Sha256:
 f261c80d585050f1b7398365944c3e85f0d552cbb8af316554954fba726ef163 1902 
gnome-shell-extension-dashtodock_67-1.dsc
 55fc9a4e27b912cfc64bf5f491fc616c7088df2b5fd3706664a86eead3cb8c64 309712 
gnome-shell-extension-dashtodock_67.orig.tar.gz
 d720568202ab1fe16453cdcc3063a6fc3e9909a7481fb3c66ecb2c858ebc0aa3 3712 
gnome-shell-extension-dashtodock_67-1.debian.tar.xz
 16383d8f371aa7c5fa3a7fd2346873cdfe8d6128a8d6c0b3c52195679368ced3 6010 
gnome-shell-extension-dashtodock_67-1_source.buildinfo
Files:
 bb522d6420db5a42ce8ec9f9daed547a 1902 gnome optional 
gnome-shell-extension-dashtodock_67-1.dsc
 5585929d64364f5fc2936004fbe69586 309712 gnome optional 
gnome-shell-extension-dashtodock_67.orig.tar.gz
 147cbbab970152f82a4e8d629ae873d9 3712 gn

Bug#942056: marked as pending in openvswitch

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/third-party/openvswitch/commit/8879acc9c2223940cb30f530213eec32c2572540


Fixed d/copyright (Closes: #942056).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/942056

Processed: Bug#942056 marked as pending in openvswitch

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #942056 [src:openvswitch] openvswitch: Incomplete debian/copyright?
Added tag(s) pending.

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