date:20191227

Your message dated Sat, 28 Dec 2019 07:21:27 +
with message-id 
and subject line Bug#943919: Removed package(s) from unstable
has caused the Debian Bug report #945668,
regarding monotone: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
945668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: monotone
Version: 1.1-9
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

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

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

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

  This is the least preferred option.

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

Dear submitter,

as the package monotone 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/943919

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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#889556: marked as done (monotone: (Build-)Depends on obsolete libbotan1.10-dev)

Your message dated Sat, 28 Dec 2019 07:21:27 +
with message-id 
and subject line Bug#943919: Removed package(s) from unstable
has caused the Debian Bug report #889556,
regarding monotone: (Build-)Depends on obsolete libbotan1.10-dev
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.)


-- 
889556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: monotone
Version: 1.1-9
Severity: serious

Dear Maintainer,

your package monotone (build-)depends on botan1.10, which itself is
obsolete. Upstream will end security support at the end of 2018, so it
must not be part of buster.

Please drop the libbotan1.10-dev build dependency.

Thanks,
Chris
--- End Message ---
--- Begin Message ---
Version: 1.1-9+rm

Dear submitter,

as the package monotone 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/943919

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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#941376: marked as done (Should monotone be removed?)

Your message dated Sat, 28 Dec 2019 07:21:27 +
with message-id 
and subject line Bug#943919: Removed package(s) from unstable
has caused the Debian Bug report #941376,
regarding Should monotone be removed?
to be marked as done.

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

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


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

Should monotone be removed? Dead upstream, last upload three years ago
and removed from testing since 1.5 years.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 1.1-9+rm

Dear submitter,

as the package monotone 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/943919

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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#888612: marked as done (monotone: FTBFS with debhelper/11.1 due to empty build target)

Your message dated Sat, 28 Dec 2019 07:21:27 +
with message-id 
and subject line Bug#943919: Removed package(s) from unstable
has caused the Debian Bug report #888612,
regarding monotone: FTBFS with debhelper/11.1 due to empty build target
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.)


-- 
888612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: monotone
Version: 1.1-9
Severity: serious
Tags: patch

Hi,

The monotone package FTBFS with debhelper/11.1 as it has an
empty build target.  This is caused by debhelper had a bug in its
handling of "explicitly defined rules targets" that has now been
fixed.

Previously, this happened to work because dpkg-buildpackage would
invoke "debian/rules build" (which would be a no-op) followed by
"fakeroot debian/rules binary".  During the binary target, dh's
suboptimal handling would run the build commands.


In the given case, monotone has an empty "build"-target to work around
rather old Debian practises.  Any supported version of Debian no
longer need these work arounds (as far as I remember), so I have
included a patch to remove said work arounds.


More details can be found in:
 * #886901 comment #35
 * #887688 comment #37
 * #880840

Apologies for the inconvenience.

Thanks,
~Niels
>From 58a8dd850ff9c294517677ce07487cc3f878b39d Mon Sep 17 00:00:00 2001
From: Niels Thykier 
Date: Sat, 27 Jan 2018 19:12:20 +
Subject: [PATCH] Remove dummy "build" target and now obsolete work arounds

Today, Debian buildds support build-arch and build-indep targets.
Remove the work arounds that assume that do not and also remove the
"magic" that attempts to undo "fakeroot" now that the build always
happens as a regular user.

Signed-off-by: Niels Thykier 
---
 debian/nofakeroot | 33 
 debian/rules  | 56 +++
 2 files changed, 3 insertions(+), 86 deletions(-)
 delete mode 100755 debian/nofakeroot

diff --git a/debian/nofakeroot b/debian/nofakeroot
deleted file mode 100755
index 18f0d02..000
--- a/debian/nofakeroot
+++ /dev/null
@@ -1,33 +0,0 @@
-#! /bin/sh
-
-# Usage:
-#   nofakeroot [command ...]
-#
-# Runs command after removing any trace of fakeroot from the environment it
-# receives.
-
-my_PRELOAD=
-for l in $LD_PRELOAD; do
-if ! echo $l | grep "libfakeroot[-a-z]*\\.so" > /dev/null; then
-   if [ -n "$my_PRELOAD" ]; then
-   my_PRELOAD="$my_PRELOAD $l"
-   else
-   my_PRELOAD="$l"
-   fi
-fi
-done
-
-was_IFS="$IFS" IFS=:
-my_LIBRARY_PATH=
-for p in $LD_LIBRARY_PATH; do
-if ! echo $p | grep "/libfakeroot\$" > /dev/null; then
-   if [ -n "$my_LIBRARY_PATH" ]; then
-   my_LIBRARY_PATH="${my_LIBRARY_PATH}:$p"
-   else
-   my_LIBRARY_PATH="$p"
-   fi
-fi
-done
-IFS="$was_IFS"
-
-LD_PRELOAD="$my_PRELOAD" LD_LIBRARY_PATH="$my_LIBRARY_PATH" eval "$@"
diff --git a/debian/rules b/debian/rules
index f3cabd8..ab54843 100755
--- a/debian/rules
+++ b/debian/rules
@@ -4,47 +4,6 @@
 # debian/rules for monotone, by Richard Levitte
 # based on the dh7 template provided by dh_make(1)
 
-# put this up top so it's the default rule.
-#
-# Policy (version 3.9.1.0, 2010-07-26, section 4.9) says that when
-# different binary packages are produced in different ways, it doesn't
-# make sense to have a build target that builds it all.  Quoted:
-#
-#   or some packages, notably ones where the same source tree is
-#   compiled in different ways to produce two binary packages, the
-#   build target does not make much sense. For these packages it is
-#   good enough to provide two (or more) targets (build-a and build-b
-#   or whatever) for each of the ways of building the package, and a
-#   build target that does nothing. The binary target will have to
-#   build the package in each of the possible ways and make the binary
-#   package out of each.
-#
-#   ...
-#
-#   When a package has a configuration and build routine which takes a
-#   long time, or when the makefiles are poorly designed, or when
-#   build needs to run clean first, it is a good idea to touch build
-#   when the build process is complete. This will ensure that if
-#   debian/rules build is run again it will not rebuild the whole
-#   program.
-#
-# We definitely have this situation, as we have -indep packages and
-# -arch packages, and we need to treat them separately, because the
-# buildds will build with -B after having installed only the Build-
-# Depends (for they are ignorant of B-D-I.

Bug#944628: marked as done (Drop build dep on monotone)

Your message dated Sat, 28 Dec 2019 06:43:10 +
with message-id 
and subject line Bug#947538: Removed package(s) from unstable
has caused the Debian Bug report #944628,
regarding Drop build dep on monotone
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.)


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

Hi Antoine,
monotone is getting removed from Debian, can you please drop the build dep
on monotone in bugs-everywhere?

(It seems unused anyway, as test_usage.sh doesn't cover it).

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 1.1.1-4+rm

Dear submitter,

as the package bugs-everywhere 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/947538

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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#821999: marked as done (kimwitu++: Build arch:all+arch:any but is missing build-{arch,indep} targets)

Your message dated Sat, 28 Dec 2019 06:42:39 +
with message-id 
and subject line Bug#947496: Removed package(s) from unstable
has caused the Debian Bug report #821999,
regarding kimwitu++: Build arch:all+arch:any but is missing build-{arch,indep} 
targets
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.)


-- 
821999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kimwitu++
Severity: normal
Usertags: arch-all-and-any-missing-targets

Hi,

The package kimwitu++ builds an architecture independent *and* an
architecture dependent package, but does not have the (now mandatory)
"build-arch" and "build-indep" targets in debian/rules.

We would like to phase out the hacks in dpkg, which are currently
needed to ensure that kimwitu++ builds despite its lack of these
targets.

 * Please add build-arch and build-indep targets to kimwitu++ at
   your earliest convenience.
   - This can also be solved by using e.g. the "dh"-style rules.

 * The work around will be removed in the first dpkg upload after
   the 1st of June.  After that upload, kimwitu++ will FTBFS if
   this bug has not been fixed before then.

Thanks,

See also: https://lists.debian.org/debian-devel/2016/04/msg00023.html
--- End Message ---
--- Begin Message ---
Version: 2.3.13-2+rm

Dear submitter,

as the package kimwitu++ 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/947496

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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#936249: marked as done (bugs-everywhere: Python2 removal in sid/bullseye)

Your message dated Sat, 28 Dec 2019 06:43:10 +
with message-id 
and subject line Bug#947538: Removed package(s) from unstable
has caused the Debian Bug report #936249,
regarding bugs-everywhere: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
936249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bugs-everywhere
Version: 1.1.1-4
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:bugs-everywhere

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

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

Dear submitter,

as the package bugs-everywhere 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/947538

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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#896456: marked as done (kimwitu++ FTBFS with fig2dev 3.2.7)

Your message dated Sat, 28 Dec 2019 06:42:39 +
with message-id 
and subject line Bug#947496: Removed package(s) from unstable
has caused the Debian Bug report #896456,
regarding kimwitu++ FTBFS with fig2dev 3.2.7
to be marked as done.

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

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


-- 
896456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kimwitu++
Version: 2.3.13-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kimwitu++.html

...
fig2dev -L pdftex -b1 figures/fprintdot.fig imagesgen/fprintdot.pdf
Invalid ellipse object at line 16.
make[1]: *** [Makefile:75: imagesgen/fprintdot.pdf] Error 1
--- End Message ---
--- Begin Message ---
Version: 2.3.13-2+rm

Dear submitter,

as the package kimwitu++ 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/947496

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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#902198: marked as done (octave-odepkg FTBFS with octave 4.4.0)

Your message dated Sat, 28 Dec 2019 06:38:38 +
with message-id 
and subject line Bug#932051: Removed package(s) from unstable
has caused the Debian Bug report #902198,
regarding octave-odepkg FTBFS with octave 4.4.0
to be marked as done.

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

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


-- 
902198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: octave-odepkg
Version: 0.8.5-5
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=octave-odepkg=sid

...
/usr/bin/mkoctfile --verbose -c odepkg_octsolver_mebdfdae.cc -o 
odepkg_octsolver_mebdfdae.o
g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/octave-4.4.0/octave/.. -I/usr/include/octave-4.4.0/octave  
-pthread -fopenmp -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security
odepkg_octsolver_mebdfdae.cc -o odepkg_octsolver_mebdfdae.o
odepkg_octsolver_mebdfdae.cc:42:10: fatal error: config.h: No such file or 
directory
 #include 
  ^~
compilation terminated.
make[1]: *** [Makefile:53: odepkg_octsolver_mebdfdae.o] Error 1
--- End Message ---
--- Begin Message ---
Version: 0.8.5-5+rm

Dear submitter,

as the package octave-odepkg 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/932051

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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#937174: marked as done (RM: nwsserver -- removal triggered by the Python2 removal)

Your message dated Sat, 28 Dec 2019 06:39:28 +
with message-id 
and subject line Bug#937174: Removed package(s) from unstable
has caused the Debian Bug report #937174,
regarding RM: nwsserver -- removal triggered by the Python2 removal
to be marked as done.

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

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


-- 
937174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nwsserver
Version: 2.0.0-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:nwsserver

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

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 nwsserver |2.0.0-2 | source
python-nwsserver |2.0.0-2 | all

--- Reason ---
removal triggered by the Python2 removal
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 937...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/937174

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

Bug#936217: marked as done (blinker: Python2 removal in sid/bullseye)

Your message dated Sat, 28 Dec 2019 05:49:17 +
with message-id 
and subject line Bug#936217: fixed in blinker 1.4+dfsg1-0.3
has caused the Debian Bug report #936217,
regarding blinker: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:blinker

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

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

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated blinker package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 28 Dec 2019 00:30:49 -0500
Source: blinker
Architecture: source
Version: 1.4+dfsg1-0.3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 936217
Changes:
 blinker (1.4+dfsg1-0.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #936217
Checksums-Sha1:
 e8e887754782110028ad7f68facb3ff293a2e547 2092 blinker_1.4+dfsg1-0.3.dsc
 c75f2aa198695d09f0218111fe3f629d0270e50b 4016 
blinker_1.4+dfsg1-0.3.debian.tar.xz
 6395f6c6dd5a0016f4c178c86dff88e8b44e3156 6322 
blinker_1.4+dfsg1-0.3_source.buildinfo
Checksums-Sha256:
 5c82494dab39592882cdf86be738f3ce440b718f509332035c1f2013ba869cfa 2092 
blinker_1.4+dfsg1-0.3.dsc
 2b8eca537b6c36e9ad99121548d45225997c539f6c240d57d544faa1b8b214ac 4016 
blinker_1.4+dfsg1-0.3.debian.tar.xz
 f95c5acbaec341d1c92a095fec15ff20b35c652e9fc081c8924ad67228e6a38b 6322 
blinker_1.4+dfsg1-0.3_source.buildinfo
Files:

Bug#936217: blinker: diff for NMU version 1.4+dfsg1-0.3

2019-12-27 Thread Sandro Tosi

Control: tags 936217 + patch


Dear maintainer,

I've prepared an NMU for blinker (versioned as 1.4+dfsg1-0.3). The diff
is attached to this message.

Regards.

diff -Nru blinker-1.4+dfsg1/debian/changelog blinker-1.4+dfsg1/debian/changelog
--- blinker-1.4+dfsg1/debian/changelog	2018-08-04 02:51:55.0 -0400
+++ blinker-1.4+dfsg1/debian/changelog	2019-12-28 00:30:49.0 -0500
@@ -1,3 +1,10 @@
+blinker (1.4+dfsg1-0.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #936217
+
+ -- Sandro Tosi   Sat, 28 Dec 2019 00:30:49 -0500
+
 blinker (1.4+dfsg1-0.2) unstable; urgency=medium
 
   * Fix FTBFS (Closes: #903325)
diff -Nru blinker-1.4+dfsg1/debian/control blinker-1.4+dfsg1/debian/control
--- blinker-1.4+dfsg1/debian/control	2018-08-04 02:49:00.0 -0400
+++ blinker-1.4+dfsg1/debian/control	2019-12-28 00:30:24.0 -0500
@@ -3,25 +3,12 @@
 Uploaders: Ondřej Surý 
 Section: python
 Priority: optional
-Build-Depends: python-all (>= 2.6.6-3), python3-all, debhelper (>= 7), dh-python, python-nose
+Build-Depends: python3-all, debhelper (>= 7), dh-python, python3-nose
 Vcs-Svn: svn://anonscm.debian.org/python-modules/packages/blinker/trunk/
 Vcs-Browser: http://anonscm.debian.org/viewvc/python-modules/packages/blinker/trunk/
 Standards-Version: 3.9.5
 Homepage: http://pythonhosted.org/blinker/
 
-Package: python-blinker
-Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
-Suggests: python-blinker-doc
-Description: Fast, simple object-to-object and broadcast signaling library
- Blinker provides a fast dispatching system that allows any number of
- interested parties to subscribe to events, or "signals".
- .
- Signal receivers can subscribe to specific senders or receive signals
- sent by any sender.
- .
- This package contains the Python 2 version.
-
 Package: python3-blinker
 Architecture: all
 Depends: ${misc:Depends}, ${python3:Depends}
diff -Nru blinker-1.4+dfsg1/debian/python-blinker.install blinker-1.4+dfsg1/debian/python-blinker.install
--- blinker-1.4+dfsg1/debian/python-blinker.install	2014-08-02 13:49:39.0 -0400
+++ blinker-1.4+dfsg1/debian/python-blinker.install	1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-/usr/lib/python2.*
diff -Nru blinker-1.4+dfsg1/debian/rules blinker-1.4+dfsg1/debian/rules
--- blinker-1.4+dfsg1/debian/rules	2014-08-02 13:54:49.0 -0400
+++ blinker-1.4+dfsg1/debian/rules	2019-12-28 00:30:49.0 -0500
@@ -1,7 +1,4 @@
 #!/usr/bin/make -f
 
 %:
-	dh $@ --with python2,python3 --buildsystem=pybuild
-
-override_dh_auto_test:
-	nosetests
+	dh $@ --with python3 --buildsystem=pybuild

Processed: blinker: diff for NMU version 1.4+dfsg1-0.3

Processing control commands:

> tags 936217 + patch
Bug #936217 [src:blinker] blinker: Python2 removal in sid/bullseye
Added tag(s) patch.

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

Bug#936558: Ping

2019-12-27 Thread Bernhard Schmidt

On Tue, Dec 17, 2019 at 10:44:42PM +0100, Bernhard Schmidt wrote:

> Pinging this bug to delay testing removal, the fix is in unstable but
> migration is currently blocked by several RC bugs in libxcrypt.

And again. Hopefully this will be solved soon.

Bernhard

Bug#945989: marked as done (apngdis producing blank images)

Your message dated Sat, 28 Dec 2019 00:49:21 +
with message-id 
and subject line Bug#945989: fixed in apngdis 2.9-1
has caused the Debian Bug report #945989,
regarding apngdis producing blank images
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.)


-- 
945989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apngdis
Version: 2.5-2
Severity: grave
Tags: a11y
Justification: renders package unusable

Dear Maintainer,

apngdis is not working properly on Debian Buster.

It's producing a list of blang (black) images. It happened to any apng files I 
tested.

First I discovered this issue on production server, then repeated on freshly 
installed and updated minimal installation with only this package installed.

To reproduce the issue:
wget 
https://upload.wikimedia.org/wikipedia/commons/1/14/Animated_PNG_example_bouncing_beach_ball.png
apngdis Animated_PNG_example_bouncing_beach_ball.png

This command should generate seperate images for each animation frame.

On jessie it's working as expected, but on buster runs very quickly and 
generates a list of identical black images. There are no errors displayed.


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

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

Versions of packages apngdis depends on:
ii  libc6   2.28-10
ii  zlib1g  1:1.2.11.dfsg-1

apngdis recommends no packages.

Versions of packages apngdis suggests:
pn  apng2gif  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: apngdis
Source-Version: 2.9-1

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

Debian distribution maintenance software
pp.
Sudip Mukherjee  (supplier of updated apngdis 
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, 27 Dec 2019 21:05:32 +
Source: apngdis
Architecture: source
Version: 2.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Sudip Mukherjee 
Closes: 945989
Changes:
 apngdis (2.9-1) unstable; urgency=medium
 .
   * QA upload.
   * Update to upstream 2.9. (Closes: #945989)
   * Update Standards-Version to 4.4.1.
   * Update compat level to 12.
   * Add new dependency.
   * Push to salsa and update Vcs.
Checksums-Sha1:
 29b90ebc06b8c4232a6a0cffa979afec13ce5f5e 1851 apngdis_2.9-1.dsc
 2b85c81c4d44bc7c42dfb0ef1a9474ff68f533b9 4544 apngdis_2.9.orig.tar.xz
 454a1db81e56fa5a7f21edb22215c1daba0e8e46 6228 apngdis_2.9-1.debian.tar.xz
 772038efbe54ebe042150e63098243d42954df45 5770 apngdis_2.9-1_source.buildinfo
Checksums-Sha256:
 9d3b640402d01235c3265bdb24a4aed51983b2cf1e3c1db0a27df2eec9725683 1851 
apngdis_2.9-1.dsc
 8cf1a883a44775281aa473d9f6ff9c52ac9cc95fcd3bd9dd8cee4686583b0ec7 4544 
apngdis_2.9.orig.tar.xz
 c34e3cd87c4bcc99aadc6003cb8abe229abcfec9178db4e35029588b20ca91c1 6228 
apngdis_2.9-1.debian.tar.xz
 724789f6c6ee1d333fdd0c7b5e5d067888c85755bfd0a79654ac76e012c6ff17 5770 
apngdis_2.9-1_source.buildinfo
Files:
 92132a2c85af17695d95de8b32371d32 1851 graphics optional apngdis_2.9-1.dsc
 210812e5d5b9627b551b7d08850f4047 4544 graphics optional apngdis_2.9.orig.tar.xz
 ba5786e46f2dc9030fa12b28f382a7a2 6228 graphics optional 
apngdis_2.9-1.debian.tar.xz
 474a370ac00e018733ef3694596ca7e9 5770 graphics optional 
apngdis_2.9-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl4Go+4ACgkQweDZLphv
fH6dZxAA2VYsnAHz9sK9BqVdE3fZullCMG3jzSA8rc4KhEApOZsbZvMX3VRiUVSo
Hk9ZQcMdE6BY4jVJLxPsbsN2Yt12G5ranlLWvSBbtkRrk9QWVfT5QojP4WhyQ6ko
l57FrFEAVARV6IZ/6R3GqQbwYpk0C41PSVYI+dnqf4k1A5Md96yiEJNUBOwVH9LC
9ck+yfP29Sp3xDuUIGwmJKXVksE/OVX/Tpvc7ZVX0FlR6evXZRIhD56lnsc1anMq

Bug#946624: python-scipy: autopkgtest regularly times out

2019-12-27 Thread Drew Parsons

Package: python-scipy
Version: 1.2.2-11
Followup-For: Bug #946624
Control: tags -1 help

The rules for skipping the failing tests
(test_sparsetools.TestInt32Overflow) are already in place in
debian/tests/python2

It looks like something must have changed in pytest such that the skip
instructions are now being ignored.

Needs a pytest syntax expert to fix.

Processed: Re: python-scipy: autopkgtest regularly times out

Processing control commands:

> tags -1 help
Bug #946624 [src:python-scipy] python-scipy: autopkgtest regularly times out
Added tag(s) help.

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

Bug#947058: marked as done (pygalmesh: autopkgtest failure on arm64 (and ppc64el, s390x))

Your message dated Sat, 28 Dec 2019 00:34:37 +
with message-id 
and subject line Bug#947058: fixed in pygalmesh 0.5.0-2
has caused the Debian Bug report #947058,
regarding pygalmesh: autopkgtest failure on arm64 (and ppc64el, s390x)
to be marked as done.

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

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


-- 
947058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygalmesh
Version: 0.5.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: needs-update

Hi Maintainer

Pygalmesh 0.5.0-1 is failing its autopkgtests on arm64 [1], and on
ppc64el and s390x in Ubuntu [2], with the output below.

Regards
Graham


[1] https://ci.debian.net/packages/p/pygalmesh/testing/arm64/
[2] http://autopkgtest.ubuntu.com/packages/pygalmesh


___ test_inr ___

def test_inr():
this_dir = os.path.dirname(os.path.abspath(__file__))
mesh = pygalmesh.generate_from_inr(
os.path.join(this_dir, "meshes", "skull_2.9.inr"),
cell_size=5.0, verbose=False
)

tol = 1.0e-3
ref = [2.031053e02, 3.739508e01, 2.425594e02, 2.558910e01,
2.300883e02, 1.775010e00]
assert abs(max(mesh.points[:, 0]) - ref[0]) < tol * ref[0]
assert abs(min(mesh.points[:, 0]) - ref[1]) < tol * ref[1]
assert abs(max(mesh.points[:, 1]) - ref[2]) < tol * ref[2]
>   assert abs(min(mesh.points[:, 1]) - ref[3]) < tol * ref[3]
E   assert 0.035070535278318715 < (0.001 * 25.5891)
E+  where 0.035070535278318715 = abs((25.55403 - 25.5891))
E+where 25.55403 = min(array([124.876366, 124.18895 ,
119.206505, ...,  96.627495, 124.194954,\n   143.47313 ],
dtype=float32))

test/test_inr.py:18: AssertionError
--- End Message ---
--- Begin Message ---
Source: pygalmesh
Source-Version: 0.5.0-2

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated pygalmesh package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 28 Dec 2019 10:54:34 +1100
Source: pygalmesh
Architecture: source
Version: 0.5.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 947058
Changes:
 pygalmesh (0.5.0-2) unstable; urgency=medium
 .
   * debian patch relax_test_tolerance.patch relaxes tolerance in
 test_inr.py to allow successful tests on arm64. Closes: #947058.
   * Standards-Version: 4.4.1
Checksums-Sha1:
 c4cc1c16ecc5ee39310ca0c0547d3836b910518d 2172 pygalmesh_0.5.0-2.dsc
 33f76396f42a1cc3124c226e2bb0b0f666f4abff 4684 pygalmesh_0.5.0-2.debian.tar.xz
Checksums-Sha256:
 abff6533ee5d66bcc718dedcdee73c2f7e310ee6de93467dda4b5f581d5f73de 2172 
pygalmesh_0.5.0-2.dsc
 eb3cb183bb9b68be554892217a6b99fb5a3a24b846cc59a8eb83e47e5e29f148 4684 
pygalmesh_0.5.0-2.debian.tar.xz
Files:
 b443c5b68c491760685958f0fc30de81 2172 python optional pygalmesh_0.5.0-2.dsc
 8a49dbeb665857346ed0646a0055c863 4684 python optional 
pygalmesh_0.5.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAl4Gn4EACgkQVz7x5L1a
AfrFGBAAnGHVFIdRce775j4wjua8iOcjD0Q5s0v7axGHIFTUGcLreqAvz5PN+cMK
yGgyDVdWIQngy7gcOGW5sAvqRTdBpD/QH2G6Mv2NCGBagwit8uTELrzWFsDmzkps
Nh6QGmbdw/GOTUDZQQyqVUgpCo08VjzGworXLEMJgoJozn7n8gA+3ZkUBp/FJQdN
qs2isid7KrudavwIBZL8RMtembmbsmrH2YtHU6BOsw1ZImluxjwIf7E9srnhR3i0
gu/DL41aNy/6vbMIEswr2on9kR+BvqRtgmCTKiWUAXL2066wd0Dny4N5hmd2Lt6M
tiW6tkau5xyd4o3mafkaB1QWxcPxOpBKBYqDFX5v/vtUqde77Wz9WuoTFjCYWw6w
aiLJ+ugO/EjqJ6WBrH5uYZ90YDGPAfs8coR1ZZHdlKZHJ+re1QelE15yqwfPiXwf
Ilzbc8IteY7A474LaBThBx9IgmmWeELilpNImtBedIq2PCjjcX9QIjwqxnGH3pVl
51jsTdt6BrWGJEk8DanDhBGL6hgCQdal6zyhlwHTF/wKkg36DBDMkw6+Z4/vFC5o
fFKXM+ODiykzkwZxsn/dkn3sEfl71i9PVsYXQO6JL3z7breJfUzYNfrDhti6QbAh
V2rn880Ho0rXKrUgj4qjRy/AkDtDKlCSu2sWeu0MffkPRQyBMl4=
=2DgB
-END PGP SIGNATURE End Message ---

Processed: Re: scipy: autopkgtest regularly times out

Processing control commands:

> tags -1 help
Bug #946625 [src:scipy] scipy: autopkgtest regularly times out
Added tag(s) help.

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

Bug#946625: scipy: autopkgtest regularly times out

2019-12-27 Thread Drew Parsons

Source: scipy
Followup-For: Bug #946625
Control: tags -1 help

The rules for skipping the failing tests
(test_sparsetools.TestInt32Overflow) are already in place in
debian/tests/python3

It looks like something must have changed in pytest such that the skip
instructions are now being ignored.

Needs a pytest syntax expert to fix.

Processed: found 947338 in 0.37.6-1.1, retitle 917840 to nitroshare-nautilus: missing Depends: python-requests ...

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

> found 947338 0.37.6-1.1
Bug #947338 [src:cherrytree] cherrytree: should this package be removed?
Marked as found in versions cherrytree/0.37.6-1.1.
> retitle 917840 nitroshare-nautilus: missing Depends: python-requests
Bug #917840 [nitroshare-nautilus] nitroshare-nautilus expansion not working 
because of unmet python2 dependency
Changed Bug title to 'nitroshare-nautilus: missing Depends: python-requests' 
from 'nitroshare-nautilus expansion not working because of unmet python2 
dependency'.
> tags 947288 + sid bullseye
Bug #947288 [src:freshplayerplugin] freshplayerplugin: FTBFS: No package 
'libdrm' found
Added tag(s) bullseye and sid.
> found 947339 0.9-2
Bug #947339 [src:slingshot] slingshot: should this package be removed?
Marked as found in versions slingshot/0.9-2.
> tags 947339 + sid bullseye
Bug #947339 [src:slingshot] slingshot: should this package be removed?
Added tag(s) sid and bullseye.
> tags 936505 + experimental
Bug #936505 [src:faulthandler] faulthandler: Python2 removal in sid/bullseye
Added tag(s) experimental.
> tags 939362 + experimental
Bug #939362 {Done: Pino Toscano } [src:grantlee5] grantlee5: 
FTBFS with Qt 5.12.4 in experimental
Bug #947487 {Done: Pino Toscano } [src:grantlee5] FTBFS: 
various C++ errors
Added tag(s) experimental.
Added tag(s) experimental.
> tags 947326 + sid bullseye
Bug #947326 [src:antimony] FTBFS: unable to load addon python3: Can't locate
Added tag(s) bullseye and sid.
> tags 947479 + sid bullseye
Bug #947479 [antimony] antimony: fails to start due to broken library dependency
Added tag(s) bullseye and sid.
> retitle 947330 cb2bib: FTBFS: *** No rule to make target 'libc2b.a', needed 
> by '../bin/cb2bib'. Stop.
Bug #947330 [src:cb2bib] FTBFS: *** No rule to make target 'libc2b.a', needed 
by '../bin/cb2bib'.  Stop.
Changed Bug title to 'cb2bib: FTBFS: *** No rule to make target 'libc2b.a', 
needed by '../bin/cb2bib'. Stop.' from 'FTBFS: *** No rule to make target 
'libc2b.a', needed by '../bin/cb2bib'.  Stop.'.
> retitle 947329 bppphyview: FTBFS: 
> debian/bppphyview/usr/share/man/man1/phyview.1: No such file or directory
Bug #947329 [src:bppphyview] FTBFS: 
debian/bppphyview/usr/share/man/man1/phyview.1: No such file or directory
Changed Bug title to 'bppphyview: FTBFS: 
debian/bppphyview/usr/share/man/man1/phyview.1: No such file or directory' from 
'FTBFS: debian/bppphyview/usr/share/man/man1/phyview.1: No such file or 
directory'.
> retitle 947475 datovka: FTBFS: make[1]: *** No rule to make target 
> 'lowered_tree_view.h', needed by 'ui_datovka.h'. Stop.
Bug #947475 [src:datovka] FTBFS: make[1]: *** No rule to make target 
'lowered_tree_view.h', needed by 'ui_datovka.h'.  Stop.
Changed Bug title to 'datovka: FTBFS: make[1]: *** No rule to make target 
'lowered_tree_view.h', needed by 'ui_datovka.h'. Stop.' from 'FTBFS: make[1]: 
*** No rule to make target 'lowered_tree_view.h', needed by 'ui_datovka.h'.  
Stop.'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
917840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917840
936505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936505
939362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939362
947288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947288
947326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947326
947329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947329
947330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947330
947338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947338
947339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947339
947475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947475
947479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947479
947487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#937482: marked as done (pymongo: Python2 removal in sid/bullseye)

Your message dated Fri, 27 Dec 2019 23:37:28 +
with message-id 
and subject line Bug#937482: fixed in pymongo 3.10.0-1
has caused the Debian Bug report #937482,
regarding pymongo: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
937482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pymongo
Version: 3.7.1-1.1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:pymongo

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

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

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

Debian distribution maintenance software
pp.
Federico Ceratto  (supplier of updated pymongo 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, 27 Dec 2019 22:31:56 +
Source: pymongo
Architecture: source
Version: 3.10.0-1
Distribution: unstable
Urgency: medium
Maintainer: Federico Ceratto 
Changed-By: Federico Ceratto 
Closes: 924078 937482
Changes:
 pymongo (3.10.0-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Remove ancient X-Python-Version field
   * d/changelog: Remove trailing whitespaces
 .
   [ Federico Ceratto ]
   * New upstream release
   * Drop Python 2 (Closes: #937482)
   * Update homepage thanks to Chris Lamb (Closes: #924078)
Checksums-Sha1:
 dd059dd5697afdc79fa10dcc6b3b443821a65c81 2423 pymongo_3.10.0-1.dsc
 fff2922f124195a9ab5fdaafd3365849dc068857 714991 pymongo_3.10.0.orig.tar.gz
 32afc345cf47c7da08ff4b0ca83f5ff3b041efdb 5548 pymongo_3.10.0-1.debian.tar.xz
 f44819e22f7836ca1d1993d2134db1e2bf3f7be2 9488 pymongo_3.10.0-1_amd64.buildinfo
Checksums-Sha256:
 6fed60579ad9acc297de3561a59ed6c7e54110812a4523fd44e12b8cd6adb096 2423 
pymongo_3.10.0-1.dsc

Bug#947546: libtexttools: FTBFS during indep-only build: clean calls gprclean but gprbuild is in B-D-Arch

2019-12-27 Thread Andreas Beckmann

Source: libtexttools
Version: 2.1.0-14
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

libtexttools/experimental FTBFS during an indep-only build:

 debian/rules clean
dh clean
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/build/libtexttools-2.1.0'
dh_auto_clean -- ADAFLAGS="" CC="cc" CFLAGS="-g -O2 
-fdebug-prefix-map=/build/libtexttools-2.1.0=. -fstack-protector-strong 
-Wformat -Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" 
LDFLAGS="-Wl,-z,relro -Wl,-z,now -Wl,--no-undefined 
-Wl,--no-copy-dt-needed-entries -Wl,--no-allow-shlib-undefined" SOVERSION="10" 
GNATMAKE_OPTIONS=""
make -j3 clean ADAFLAGS= CC=cc "CFLAGS=-g -O2 
-fdebug-prefix-map=/build/libtexttools-2.1.0=. -fstack-protector-strong 
-Wformat -Werror=format-security" "CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2" 
"LDFLAGS=-Wl,-z,relro -Wl,-z,now -Wl,--no-undefined 
-Wl,--no-copy-dt-needed-entries -Wl,--no-allow-shlib-undefined" SOVERSION=10 
GNATMAKE_OPTIONS=
make[2]: Entering directory '/build/libtexttools-2.1.0'
Package ncurses was not found in the pkg-config search path.
Perhaps you should add the directory containing `ncurses.pc'
to the PKG_CONFIG_PATH environment variable
No package 'ncurses' found
rm -f build-obj-dynamic/* build-obj-static/* build-lib-dynamic/* 
build-lib-static/*
find -name "*~" -delete
sed ' s%ADAFLAGS%%;  s%CFLAGS%-g", "-O2", 
"-fdebug-prefix-map=/build/libtexttools-2.1.0=.", "-fstack-protector-strong", 
"-Wformat", "-Werror=format-security%;  s%LDFLAGS%-Wl,-z,relro", "-Wl,-z,now", 
"-Wl,--no-undefined", "-Wl,--no-copy-dt-needed-entries", 
"-Wl,--no-allow-shlib-undefined%;  s%LDLIBS%%;  s%SOVERSION%10%;' \
 examples/examples.gpr.sed > examples/examples.gpr
sed ' s%ADAFLAGS%%;  s%CFLAGS%-g", "-O2", 
"-fdebug-prefix-map=/build/libtexttools-2.1.0=.", "-fstack-protector-strong", 
"-Wformat", "-Werror=format-security%;  s%LDFLAGS%-Wl,-z,relro", "-Wl,-z,now", 
"-Wl,--no-undefined", "-Wl,--no-copy-dt-needed-entries", 
"-Wl,--no-allow-shlib-undefined%;  s%LDLIBS%%;  s%SOVERSION%10%;' \
 texttools.gpr.sed > texttools.gpr
gprclean examples/examples.gpr -XKIND=static
make[2]: gprclean: Command not found
make[2]: *** [Makefile:91: clean] Error 127
make[2]: Leaving directory '/build/libtexttools-2.1.0'
dh_auto_clean: make -j3 clean ADAFLAGS= CC=cc "CFLAGS=-g -O2 
-fdebug-prefix-map=/build/libtexttools-2.1.0=. -fstack-protector-strong 
-Wformat -Werror=format-security" "CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2" 
"LDFLAGS=-Wl,-z,relro -Wl,-z,now -Wl,--no-undefined 
-Wl,--no-copy-dt-needed-entries -Wl,--no-allow-shlib-undefined" SOVERSION=10 
GNATMAKE_OPTIONS= returned exit code 2
make[1]: *** [debian/rules:49: override_dh_auto_clean] Error 255
make[1]: Leaving directory '/build/libtexttools-2.1.0'
make: *** [debian/rules:39: clean] Error 2


gprbuild which ships gprclean has been moved to B-D-Arch which is not
installed for an indep-only build.

There is also a failure on most arch-only builds:
https://buildd.debian.org/status/package.php?p=libtexttools=experimental

dh_ada_library: error while loading shared libraries: libgpr.so.18: cannot open 
shared object file: No such file or directory


Cheers,

Andreas


libtexttools_2.1.0-14_indep.log.gz
Description: application/gzip

Processed: py2removal RC severity updates - 2019-12-27 23:36:51.544845+00:00

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # for more details on this severity bump
> # python-blinker is a module and has 0 external rdeps or not in testing
> severity 936217 serious
Bug #936217 [src:blinker] blinker: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-cinfony is a module and has 0 external rdeps or not in testing
> severity 936303 serious
Bug #936303 [src:cinfony] cinfony: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-indigo is a module and has 0 external rdeps or not in testing
> severity 936733 serious
Bug #936733 [src:indigo] indigo: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-itsdangerous is a module and has 0 external rdeps or not in testing
> severity 937848 serious
Bug #937848 [src:python-itsdangerous] python-itsdangerous: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> # python-netsyslog is a module and has 0 external rdeps or not in testing
> severity 937943 serious
Bug #937943 [src:python-netsyslog] python-netsyslog: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#921904: Bug#946951: Bug#921904: win-iconv: FTBFS (wine: chdir to /tmp/wine-I6miLw/server-29-3583b06 : No such file or directory)

2019-12-27 Thread Vincent Lefevre

On 2019-12-27 19:49:46 +, Joseph Nahmias wrote:
> On Fri, Dec 27, 2019 at 07:27:42PM +, Joseph Nahmias wrote:
> > The attached patch works around the issue until that is fixed.
> 
> Of course, I forgot this patch... Take 2.

Wouldn't the use of wildcards be a security issue?

+   ln -s /tmp/.wine-`id -u`/server* /tmp/wine-*/

i.e. could you end up creating wrong symbolic links?

In any case, this seems rather ugly to me.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#937544: marked as done (pyspread: Python2 removal in sid/bullseye)

Your message dated Fri, 27 Dec 2019 23:15:47 +
with message-id 
and subject line Bug#937544: fixed in pyspread 1.99.0.0-1
has caused the Debian Bug report #937544,
regarding pyspread: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
937544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyspread
Version: 1.1.3-4
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:pyspread

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

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

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

Debian distribution maintenance software
pp.
Andreas Noteng  (supplier of updated pyspread 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, 27 Dec 2019 23:39:18 +0100
Source: pyspread
Architecture: source
Version: 1.99.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Andreas Noteng 
Changed-By: Andreas Noteng 
Closes: 937544
Changes:
 pyspread (1.99.0.0-1) unstable; urgency=medium
 .
   * New upstream release
 - Switch to Python 3 (closes: #937544)
 - Switch to Qt5
 - Reenable tests
Checksums-Sha1:
 ae97058dd5bdb23cbbd598b23aee9cf980ffa1a4 2150 pyspread_1.99.0.0-1.dsc
 3f0756be3219b8358a7654d4d06d80d003250043 750380 pyspread_1.99.0.0.orig.tar.gz
 945de203e03a0d968241f4ced705aad58845efdc 9516 pyspread_1.99.0.0-1.debian.tar.xz
 98b24689d8398d22c0c0d0adcc430e86c1f84eb8 10023 
pyspread_1.99.0.0-1_amd64.buildinfo
Checksums-Sha256:
 474041c3baaf071c1db361676304496ab64f552488773c3e891fa4e510a74255 2150 
pyspread_1.99.0.0-1.dsc
 1e068e607a408d8fbea7988db6c571d434ec257a23151c2af8da8ff631b5acc3 750380 
pyspread_1.99.0.0.orig.tar.gz

Bug#936625: gnome-doc-utils is deprecated

On Wed, 20 Nov 2019 at 11:20:57 +0100, Andreas Henriksson wrote:
> The gnome-doc-utils package is deprecated since many years.
> It should be removed, rather than ported to python3.
> 
> Please see #889019 for futher deprecation info.
> 
> This packages however still has quite a large reverse build-dependency
> list

Some have been fixed already.

I've opened Severity: important bugs for the rest, to make sure
maintainers are alerted about this potentially becoming a RC issue in
future. They block this bug and #889019, and are usertagged as oldlibs[1]
and gnome-doc-utils[2].

[1] 
https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=pkg-gnome-maintainers%40lists.alioth.debian.org=oldlibs
[2] 
https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=pkg-gnome-maintainers%40lists.alioth.debian.org=gnome-doc-utils

Regards,
smcv

Processed: viking: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 947540 937181 947526 947532 947534 947525 945292 945294 
947527 947530 945141 947522 947536 947519 947524 947535 945138 947537 947520 
943108 947521 945293 947539 945523 947533 945137 947531 947529 947528 936865 
947523
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947541
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 947539 945137 947533 945523 947521 945293 936865 947528 
947529 947523 947531 945292 945141 947530 947527 945294 947532 947526 947540 
947525 947534 881889 945138 947520 947537 947519 947522 947536 947535 947524
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947541

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

Processed: xiphos: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 947523 947524 947533 947534 945293 945294 945141 947540 
947519 947541 947525 947535 947539 936865 947527 947526 947529 943108 947537 
947528 947536 947520 945137 947521 947522 945292 945523 947531 947532 937181 
947530 945138
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947542
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 947536 947537 947528 947529 947526 947527 936865 947539 
945138 947530 947532 947531 945523 945292 947522 947521 945137 947520 945141 
945293 881889 945294 947534 947533 947524 947523 947535 947525 947541 947519 
947540
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947542

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

Processed: stardict: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 947520 945523 945293 947533 947528 945137 936865 947529 
947537 947534 947532 947536 947525 947521 945141 945292 945294 947526 947535 
947531 937181 943108 945138 947539 947527 947519 947524 947522 947523 947530
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947540
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 945293 947520 945523 945137 881889 947528 947533 947532 
947534 947537 947529 936865 945294 945292 945141 947521 947525 947536 947531 
947535 947526 947522 947524 947527 947519 947539 945138 947523 947530
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947540

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

Processed: pitivi: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 947534 947527 947535 947536 947523 943108 947522 945523 
937181 947530 945138 947521 947531 945137 936865 947532 947520 945292 947529 
947528 947533 947524 947519 947526 947525
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947537
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 947529 945292 947528 947533 947524 947526 947519 947525 
947531 945137 947520 881889 947532 936865 947530 947522 945523 947521 945138 
947534 947527 947535 947536 947523
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947537

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

Processed: pdfmod: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 947531 936865 947527 947535 947529 947523 947530 945292 
947526 947532 947528 947519 947524 947521 937181 947525 945523 945138 947533 
943108 947520 947522 945137 947534
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947536
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 947523 945292 947530 947526 947532 881889 947524 947528 
947519 947531 936865 947527 947529 947535 947533 947520 947522 945137 947534 
947521 945138 945523 947525
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947536

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

Bug#936249: bugs-everywhere: Python2 removal in sid/bullseye

On Fri, Dec 27, 2019 at 02:34:42PM -0500, Antoine Beaupré wrote:
> On 2019-12-26 02:05:56, maxigas wrote:
> > On Wed, Dec 25 2019, Moritz Mühlenhoff wrote:
> >
> >> On Fri, Aug 30, 2019 at 07:12:24AM +, Matthias Klose wrote:
> >>> Package: src:bugs-everywhere
> >>> Version: 1.1.1-4
> >>> Severity: normal
> >>> Tags: sid bullseye
> >>> User: debian-pyt...@lists.debian.org
> >>> Usertags: py2removal
> >>> 
> >>> Python2 becomes end-of-live upstream, and Debian aims to remove
> >>> Python2 from the distribution, as discussed in
> >>> https://lists.debian.org/debian-python/2019/07/msg00080.html
> >>
> >> bugs-everywhere is dead upstream, the last commits are from 2013.
> >>
> >> Are you planning to port it to Python 3 yourself? Otherwise I'll
> >> request it's removal from the archive.
> >
> > Hm, i'm sorry but i don't think i will have the time to port it.
> 
> Same here, and there are alternatives. Just a quick list covering still
> active projects:

Ack! I'm filing a removal bug, then.

> https://distix.eu/
> https://github.com/MichaelMure/git-bug
> https://github.com/neithernut/git-dit
> https://sit.fyi/
> 
> maybe something for the release notes i guess...

That doesn't seem strictly needed, we're removing hundreds of packages each
release cycle :-)

Cheers,
Moritz

Processed: user pkg-gnome-maintain...@lists.alioth.debian.org, usertagging 945293, block 889019 with 945293 ...

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

> user pkg-gnome-maintain...@lists.alioth.debian.org
Setting user to pkg-gnome-maintain...@lists.alioth.debian.org (was 
s...@debian.org).
> usertags 945293 + oldlibs gnome-doc-utils
There were no usertags set.
Usertags are now: oldlibs gnome-doc-utils.
> block 889019 with 945293
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 947533 947534 947536 947520 881889 947527 945138 947537 
947530 945523 947528 945292 947526 945137 936865 947524 947519 947523 947531 
947525 947532 947529 947522 947535 947521
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 945293
> block 936625 with 945293
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 947534 947533 947536 937181 947520 945138 947527 947537 
947530 943108 947526 945137 947528 945292 945523 947523 947519 947524 936865 
947531 947525 947532 947529 947522 947535 947521
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 945293
> # likely to be escalated to serious during the bullseye cycle
> severity 945293 important
Bug #945293 [src:sensors-applet] sensors-applet: needlessly build-depends on 
deprecated gnome-doc-utils
Severity set to 'important' from 'normal'
> thanks
Stopping processing here.

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

Processed: user pkg-gnome-maintain...@lists.alioth.debian.org, usertagging 945294, block 889019 with 945294 ...

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

> user pkg-gnome-maintain...@lists.alioth.debian.org
Setting user to pkg-gnome-maintain...@lists.alioth.debian.org (was 
s...@debian.org).
> usertags 945294 + oldlibs gnome-doc-utils
There were no usertags set.
Usertags are now: oldlibs gnome-doc-utils.
> block 889019 with 945294
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 881889 945137 936865 947532 945138 947533 947524 947525 
945293 945292 947529 947520 947537 947521 947526 947523 947522 947534 947535 
945523 947527 947531 947519 947536 947530 945141 947528
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 945294
> block 936625 with 945294
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 947522 947523 937181 947535 947534 947527 945523 947519 
947536 947531 947528 945141 947530 945137 947533 945138 947532 936865 945292 
945293 947525 947524 943108 947520 947529 947537 947526 947521
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 945294
> # likely to be escalated to serious during the bullseye cycle
> severity 945294 important
Bug #945294 [src:shotwell] shotwell: needlessly build-depends on deprecated 
gnome-doc-utils
Severity set to 'important' from 'normal'
> thanks
Stopping processing here.

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

Processed: ocrfeeder: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 947532 936865 947529 947523 945523 937181 947526 947533 
945292 947522 947534 947519 947525 947524 947530 947527 947520 945137 947531 
943108 945138 947521 947528
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947535
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 947519 947528 947521 947524 947525 947534 947531 945138 
947533 947526 947522 945137 945292 947520 947530 947529 936865 947532 945523 
947527 947523 881889
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947535

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

Processed: solfege: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 945293 947527 947530 947532 943108 945137 947524 947525 
947529 945294 947531 936865 947523 947526 947520 945138 947537 947522 945141 
947528 947534 947521 947535 947519 945523 945292 937181 947536 947533
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947539
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 947519 947521 947535 881889 947536 947533 945523 945292 
947522 947520 947537 945138 947534 947528 945141 947525 947529 945294 947531 
947523 947526 936865 947532 945293 947527 947530 947524 945137
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947539

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

Processed: user pkg-gnome-maintain...@lists.alioth.debian.org, usertagging 945141, block 889019 with 945141 ...

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

> user pkg-gnome-maintain...@lists.alioth.debian.org
Setting user to pkg-gnome-maintain...@lists.alioth.debian.org (was 
s...@debian.org).
> usertags 945141 + oldlibs gnome-doc-utils
There were no usertags set.
Usertags are now: oldlibs gnome-doc-utils.
> block 889019 with 945141
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 881889 947527 945293 947519 947535 947533 945138 947521 
947531 947523 947525 947537 947524 945137 947530 947526 936865 947522 947528 
947532 945292 947536 947534 945523 947520 947529
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 945141
> block 936625 with 945141
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 947526 945137 947524 947530 947522 943108 947528 936865 
945292 947532 947529 947534 945523 947520 947536 947519 947533 947535 947527 
945293 947521 945138 947531 947537 937181 947525 947523
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 945141
> # likely to be escalated to serious during the bullseye cycle
> severity 945141 important
Bug #945141 [shotwell] needlessly build-depends on deprecated gnome-doc-utils
Severity set to 'important' from 'normal'
> thanks
Stopping processing here.

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

Bug#945993: marked as done (diffoscope: FAILED tests/test_source.py::test_code_is_black_clean - assert 228381 == 0)

Your message dated Fri, 27 Dec 2019 22:34:28 +
with message-id 
and subject line Bug#945993: fixed in diffoscope 134
has caused the Debian Bug report #945993,
regarding diffoscope: FAILED tests/test_source.py::test_code_is_black_clean - 
assert 228381 == 0
to be marked as done.

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

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


-- 
945993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: diffoscope
Severity: serious
Tags: bullseye sid
X-Debbugs-Cc: bl...@packages.debian.org

diffoscope autopkgtests fail with the current version of "black" in sid:
https://ci.debian.net/data/autopkgtest/unstable/amd64/d/diffoscope/3557636/log.gz

It seems to me the test is inherently extremely sensitive to the exact
version of black used, so it probably shouldn't be part of autopkgtests?

Cheers,
Julien
--- End Message ---
--- Begin Message ---
Source: diffoscope
Source-Version: 134

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated diffoscope 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, 27 Dec 2019 19:17:16 +
Source: diffoscope
Architecture: source
Version: 134
Distribution: unstable
Urgency: medium
Maintainer: Reproducible builds folks 

Changed-By: Chris Lamb 
Closes: 945993
Changes:
 diffoscope (134) unstable; urgency=medium
 .
   [ Chris Lamb ]
   * Ensure that autopkgtests are run with our pyproject.toml present for the
 correct "black" source code formatter settings. (Closes: #945993)
   * Tidy some unnecessary boolean logic in the ISO9660 tests.
   * Rename the "text_option_with_stdiout" to "text_option_with_stdout".
   * Include the libarchive file listing for ISO images to ensure that
 timestamps (not just dates) are visible in any difference.
 (Closes: reproducible-builds/diffoscope#81)
 .
   [ Eli Schwartz ]
   * Fix an exception in the progressbar handler.
 .
   [ Vagrant Cascadian ]
   * Add an external tool reference for zstd on GNU Guix.
Checksums-Sha1:
 dfd63811a853517bc775583b9e8310ec112b92a4 4717 diffoscope_134.dsc
 11df858a29b55e43555fdb99cb172c09a539e16d 974476 diffoscope_134.tar.xz
 3ac3b73ae7e0fe0559d3c86e292a1fe985a4257c 26300 diffoscope_134_amd64.buildinfo
Checksums-Sha256:
 89fef3182bab0119bcf2493158319f280b95ecbfb3600c143fc238c15b368ae8 4717 
diffoscope_134.dsc
 a025f1133a88d84b2139684d4d64ab65e4ae7214d6e154cc0b77369832469d79 974476 
diffoscope_134.tar.xz
 899f2bdb6c0c9a18e62b3df8e92ae11837b00d2b2d54a350e3e8222b785780cd 26300 
diffoscope_134_amd64.buildinfo
Files:
 7b85657920ef986dcb047d8837aa0b26 4717 devel optional diffoscope_134.dsc
 5a5002aea8c555d0e0fb50dced284684 974476 devel optional diffoscope_134.tar.xz
 8a6ad4d66d14283546bcf3995e031ad3 26300 devel optional 
diffoscope_134_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl4GhEIACgkQHpU+J9Qx
HliX9g/9HEZsl5vfI6PtgdEjHEhIvGGgXeXlqBcW8S1GIv51kYO2vF1blEZ9jbKC
O/bsMErKcm60QjaFLmiQlF9P1U9npE0TmMncr3vuWHu8LqMQ0ouSv8k21Ao/drQp
LLHsh+9mHtMeZZWESkHJDInmqave8FGLkV0WcZQIJj3oaVsfwI2fXdew06QYnxyC
p6dec5ZzQxg60xBXd0OMR9zDefpuJ9I2Qsmvc2COh1cEutoj4d0wzviunh8tL46m
xJPVkUViRTQm6VqTgKOHSFB+cK8GJB4/XDXTo115Fv9kQIyOClHfhQLEOWdJ0bbO
0cOpS6odHKUCJCg1v/oGiV5p2p2ma8Z36u7omf4rJR49H/CBdP0shqtddXPCwqz0
B0I1uzvOnUITJ9TYiatdBGMc37EOx+PjjdexY1c33g0f70MePIJultpuV+Py4DF7
V9BbRjMDQ0BAs8nDRkxVsc/3V9tjP2+grU8J+amjecBXtXzvesCvyM953rUGmrDg
oVL0RQ7xNcSn0hLlsb60ay6blEwN7RyVx9AWBkEHx/GgJs94POS67HPXz6YxOPPa
8Gl1KC2FCixap2ELHKG4HMmX/XTQzP9A0XiAwWghpCwP1bYXDS2b6nO4Ko8OOWf/
eHqpxfRQZWECme0cTLpvkmsqqdJ0cH9QSAi8FToMLVcTp6IQE/w=
=CNF+
-END PGP SIGNATURE End Message ---

Processed: user pkg-gnome-maintain...@lists.alioth.debian.org, usertagging 945523, block 889019 with 945523 ...

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

> user pkg-gnome-maintain...@lists.alioth.debian.org
Setting user to pkg-gnome-maintain...@lists.alioth.debian.org (was 
s...@debian.org).
> usertags 945523 + oldlibs gnome-doc-utils
There were no usertags set.
Usertags are now: oldlibs gnome-doc-utils.
> block 889019 with 945523
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 947525 947533 947523 947520 947526 881889 947530 936865 
947519 947531 947521 947534 945138 945137 947524 947528 947527 947529 945292 
947532 947522
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 945523
> block 936625 with 945523
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 943108 947533 947525 947523 947519 947531 947521 947520 
947526 947530 936865 947529 945137 947534 945138 947524 947527 947528 937181 
947532 947522 945292
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 945523
> # likely to be escalated to serious during the bullseye cycle
> severity 945523 important
Bug #945523 [src:muffin] muffin: please drop build-dependency on deprecated 
gnome-doc-utils
Severity set to 'important' from 'normal'
> thanks
Stopping processing here.

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

Processed: mp3splt: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 947520 947523 947529 947531 947532 947525 947521 937181 
947519 947530 945138 947527 947533 945292 936865 947528 947524 945137 947526 
947522 943108
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947534
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 947532 881889 947531 947529 947520 947523 947528 947526 
947522 945137 947524 945138 947530 936865 945292 947533 947527 947521 947525 
947519
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947534

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

Processed: user pkg-gnome-maintain...@lists.alioth.debian.org, usertagging 945292, block 889019 with 945292 ...

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

> user pkg-gnome-maintain...@lists.alioth.debian.org
Setting user to pkg-gnome-maintain...@lists.alioth.debian.org (was 
s...@debian.org).
> usertags 945292 + oldlibs gnome-doc-utils
There were no usertags set.
Usertags are now: oldlibs gnome-doc-utils.
> block 889019 with 945292
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 947532 947528 947529 945138 947531 947524 947521 947522 
947526 881889 947525 936865 947523 947519 947520 945137 947533 947530 947527
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 945292
> block 936625 with 945292
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 947520 947519 947526 947524 947522 947523 947528 945137 
947531 947527 936865 945138 947521 937181 943108 947532 947533 947530 947525 
947529
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 945292
> # likely to be escalated to serious during the bullseye cycle
> severity 945292 important
Bug #945292 [src:lightdm] lightdm: needlessly(?) build-depends on deprecated 
gnome-doc-utils
Severity set to 'important' from 'normal'
> thanks
Stopping processing here.

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

Processed: gparted: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 945138 943108 947530 947519 945137 947521 947524 947526 
947529 947523 947520 947525 947528 947522 937181 936865 947527
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947531
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 947519 947530 945138 945137 947521 947520 947529 947523 
947526 947524 881889 947528 947525 947522 947527
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947531
> fixed -1 1.0.0-0.1~exp
Bug #947531 [src:gparted] gparted: build-depends on deprecated gnome-doc-utils
Marked as fixed in versions gparted/1.0.0-0.1~exp.

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

Processed: gwaei: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 947524 947526 947529 943108 947530 947520 936865 947531 
947521 947522 945138 947525 945137 947523 937181 947528 947519 947527
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947532
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 947519 947528 947527 947523 881889 945138 945137 947525 
947522 947521 947531 947520 947530 947524 947529 947526
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947532

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

Processed: kupfer: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 937181 947530 945137 947527 945138 947528 947520 947526 
947532 947519 947525 947531 947522 947523 936865 947524 947529 943108 947521
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947533
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 881889 947528 945138 947520 947530 947527 945137 947523 
947524 947522 947529 947521 947519 947532 947526 947525 947531
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947533

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

Processed: gnome-system-tools: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 945137 947521 947529 936865 947527 947525 947523 947526 
947528 947522 947519 937181 947524 947520 943108 945138
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947530
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 947529 945137 947521 947527 947525 947523 947526 947522 
947528 881889 947519 947524 947520 945138
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947530

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

Processed: gmpc: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 937181 945138 947524 947527 947519 947520 947526 936865 
947522 945137 947525 947521 943108 947523
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947528
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 947521 947523 947527 947524 945138 947519 947520 881889 
945137 947522 947526 947525
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947528

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

Processed: gnome-chemistry-utils: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 937181 945137 947527 936865 947525 947524 943108 947521 
947526 947523 945138 947528 947522 947519 947520
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947529
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 947520 947523 947519 947522 947528 945138 881889 947526 
947521 947527 945137 947525 947524
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947529

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

Processed: glom: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 936865 945138 947519 943108 945137 947521 947520 937181 
947522 947524 947525 947523 947526
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947527
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 947525 947523 947526 947524 947520 947522 947521 945137 
947519 881889 945138
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947527

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

Processed: gconf-editor: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 947520 943108 936865 947521 947522 947519 937181 945138 
945137
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947523
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 947522 881889 947519 945137 945138 947520 947521
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947523

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

Processed: gimp-help: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 947520 947525 943108 936865 947521 945138 937181 947523 
947519 947524 947522 945137
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947526
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 947521 945138 947519 947523 947524 947522 945137 947520 
947525 881889
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947526

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

Processed: geeqie: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 947524 945138 943108 947521 947519 937181 947520 945137 
947522 936865 947523
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947525
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 947521 947519 945138 947524 881889 947523 945137 947522 
947520
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947525

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

Processed: geary: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 947523 947521 947522 936865 947520 947519 945137 937181 
945138 943108
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947524
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 947522 947521 947520 947519 881889 947523 945138 945137
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947524

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

Processed: gbrainy: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 947519 945137 947520 947521 943108 936865 945138 937181
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947522
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 945137 947521 947520 881889 947519 945138
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947522

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

Processed: dasher: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 943108 936865 937181
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947519
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 945138 881889 945137
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947519

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

Processed: block 936625 with 945138, block 936625 with 945137

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

> block 936625 with 945138
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 947520 936865 947519 937181 943108 947521
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 945138
> block 936625 with 945137
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 947520 947521 947519 943108 945138 937181 936865
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 945137
> thanks
Stopping processing here.

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

Processed: florence: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 947520 943108 936865 937181 947519
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947521
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 881889 947519 947520 945138 945137
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947521

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

Processed: filemanager-actions: build-depends on deprecated gnome-doc-utils

Processing control commands:

> block 936625 by -1
Bug #936625 [src:gnome-doc-utils] gnome-doc-utils: Python2 removal in 
sid/bullseye
936625 was blocked by: 937181 943108 936865 947519
936625 was blocking: 936941 937695
Added blocking bug(s) of 936625: 947520
> block 889019 by -1
Bug #889019 [gnome-doc-utils] gnome-doc-utils: is deprecated
889019 was blocked by: 945138 947519 881889 945137
889019 was not blocking any bugs.
Added blocking bug(s) of 889019: 947520

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

Bug#947518: casparcg-server: FTBFS: xf86vmode library not found - required for GLFW

2019-12-27 Thread Andreas Beckmann

Package: casparcg-server
Version: 2.2.0+dfsg-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

casparcg-server FTBFS in a current sid pbuilder environment:

CMake Error at CMakeModules/FindGLFW.cmake:150 (message):
  xf86vmode library not found - required for GLFW
Call Stack (most recent call first):
  CMakeModules/Bootstrap_Linux.cmake:44 (FIND_PACKAGE)
  CMakeLists.txt:18 (INCLUDE)


Andreas


casparcg-server_2.2.0+dfsg-2.log.gz
Description: application/gzip

Bug#927171: marked as done (boogie: build-dependencies not satisfiable in sid)

Your message dated Fri, 27 Dec 2019 22:04:27 +
with message-id 
and subject line Bug#927171: fixed in boogie 2.4.1+dfsg-0.1
has caused the Debian Bug report #927171,
regarding boogie: build-dependencies not satisfiable in sid
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.)


-- 
927171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: boogie
Version: 2.3.0.61016+dfsg+3.gbp1f2d6c1-1
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

the build-dependencies of boogie are not satisfiable on any architecture
in sid. This is the case since at least 2019-01-12.

On amd64, arm64, armel, armhf, i386, mipsel, ppc64el, s390x, the reason
is that it build-depends both on mono-devel (>= 2.4.2.3) and 
mono-reference-assemblies-4.0. However, mono-devel (5.18.0.240+dfsg-2) 
declares a Breaks with mono-reference-assemblies-4.0 (<< 5.0~).

-Ralf.
--- End Message ---
--- Begin Message ---
Source: boogie
Source-Version: 2.4.1+dfsg-0.1

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

Debian distribution maintenance software
pp.
Fabian Wolff  (supplier of updated boogie package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 16 Dec 2019 14:25:20 +0100
Source: boogie
Architecture: source
Version: 2.4.1+dfsg-0.1
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Barenblat 
Changed-By: Fabian Wolff 
Closes: 927171
Changes:
 boogie (2.4.1+dfsg-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release.
   * Update debian/watch file.
   * Update debian/copyright:
 - New upstream license.
 - Relicense debian/* to match new upstream license (Expat)
   (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944876#20).
 - Exclude prebuilt Windows binary from the source tree.
   * Update licenses in debian/{boogie,bvd}.1.
   * Change Priority to optional in debian/control.
   * Upgrade to debhelper compat level 12.
   * Update build dependencies (Closes: #927171).
   * Upgrade to Standards-Version 4.4.1.
   * Fix debian/rules to make the new version build.
   * Enable autopkgtest package testing, and add mccarthy-{91,92} tests.
   * Update Vcs-Git and Vcs-Browser fields in debian/control.
Checksums-Sha1:
 0b8465d1635ef149e2ed5a6c3d4a11e433128d6d 1989 boogie_2.4.1+dfsg-0.1.dsc
 4afce8c0fab76361d4cfc9086ca1a08a0e8db484 1165764 boogie_2.4.1+dfsg.orig.tar.xz
 d96b8aeb91ad583e7ebb15401fb12791b42fad5b 9080 
boogie_2.4.1+dfsg-0.1.debian.tar.xz
 8e34dfe536a796ca022988b3f5e8c65f880de794 15782 
boogie_2.4.1+dfsg-0.1_source.buildinfo
Checksums-Sha256:
 1d5b6e8701b81ca1b22259daaa1b16728de18d5b99c7122c434fbc0d7765853c 1989 
boogie_2.4.1+dfsg-0.1.dsc
 863dbb07fa71e2fdc117f87dac8193dc438ef8aaa9940379e21738ef86c9f077 1165764 
boogie_2.4.1+dfsg.orig.tar.xz
 3cd9c617d78183b42bacc3a3e40c1c6bbf1eb8ff37d07aa0f84466410b2a4ea9 9080 
boogie_2.4.1+dfsg-0.1.debian.tar.xz
 f288a0df8f7b8728d0121b4979f47d802289c73586eeb27e96d88b86d854f768 15782 
boogie_2.4.1+dfsg-0.1_source.buildinfo
Files:
 88261ab4e426dbe3e65e78e950493e47 1989 cli-mono optional 
boogie_2.4.1+dfsg-0.1.dsc
 48ad137c9193ba3359f734f4310d3ffe 1165764 cli-mono optional 
boogie_2.4.1+dfsg.orig.tar.xz
 71e7c99e1268de6fee4c02632c1c1032 9080 cli-mono optional 
boogie_2.4.1+dfsg-0.1.debian.tar.xz
 ad2064b922416099516a45414cfaf39e 15782 cli-mono optional 
boogie_2.4.1+dfsg-0.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEI3pUsQKHKL8A7zH00Ot2KGX8XjYFAl4GfBYACgkQ0Ot2KGX8
Xja1YQ//XRy4Ebr7ByY0iSN4U8Ng3QYJpxp3D8fWy6nWYL6iZMRAYhuIDNlJnyfv
NNlvht5mSsMeymlPjxphcYfoFxhYpiwIbT5lzqF+GuU4M3yb8tPlUfjn241+RNuh
lwVitify2WtV73XQhX27Z0qzW2oYWs//LchN/XWVEO86uGZG3EV0ioG6B6R8xmlg
zoBRf40YPnhOdoxvbeRjw3eVw68Gm4RyRarczIrgf6ITf06aOdwn6+vB16pkayro
uu3os1Oy6S/T+Jov66FcRYJRmKOl2eQc+f3J06D8Xn4ikIHhYqVUMtHyw1I3s7eH
s7gkzauVwgdb3xbE4nEEGs9+twVLeIAzDpHLVLPmSKNo5J6Cu0qfVECBNAByyOpf
Ln+/pg8Cowc+SkCN30du0HhkOAEg9Zq9+36rw80PObXz22kREv5Mp5JrpSqijhEg

Processed: transmission-remote-gtk: build-depends on obsolete libunique-dev

Processing control commands:

> block 895520 by -1
Bug #895520 [libunique-1.0-0] libunique-1.0-0: deprecated and unmaintained 
upstream
895520 was blocked by: 885814 885813 885815 947514 947513 947515 885810
895520 was not blocking any bugs.
Added blocking bug(s) of 895520: 947516

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

Bug#947516: transmission-remote-gtk: build-depends on obsolete libunique-dev

Source: transmission-remote-gtk
Version: 1.4.1-1
Severity: serious
Justification: inheriting severity from 895520
Control: block 895520 by -1

src:transmission-remote-gtk Build-Depends on libunique-dev, which is
obsolete and unmaintained upstream (see #895520 for more details). Its
Debian maintainers, the GNOME team, do not consider libunique to be
suitable for inclusion in the bullseye (Debian 11) stable release.

The transmission-remote-gtk binary package does not appear to have a
Depends on libunique-1.0-0, which suggests that the build-dependency is no
longer necessary. (Also, transmission-remote-gtk now depends on GTK 3, but
libunique is part of the older and incompatible GTK 2 stack, so I don't
think transmission-remote-gtk could be using libunique successfully.)

Please remove this build-dependency, so that the GNOME team can be a
step closer to removing libunique.

Thanks,
smcv

Bug#947515: quitcount: build-depends on obsolete libunique-dev

Source: quitcount
Version: 3.1.4-1
Severity: serious
Justification: inheriting severity from 895520
Control: block 895520 by -1

src:quitcount Build-Depends on libunique-dev, which is obsolete and
unmaintained upstream (see #895520 for more details). Its Debian
maintainers, the GNOME team, do not consider libunique to be suitable
for inclusion in the bullseye (Debian 11) stable release.

The quitcount binary package does not appear to have a Depends on
libunique-1.0-0, which suggests that the build-dependency is no longer
necessary. (Also, quitcount now depends on GTK 3, but libunique is part
of the older and incompatible GTK 2 stack, so I don't think quitcount
could be using libunique successfully.)

Please remove this build-dependency, so that the GNOME team can be a
step closer to removing libunique.

Thanks,
smcv

Processed: quitcount: build-depends on obsolete libunique-dev

Processing control commands:

> block 895520 by -1
Bug #895520 [libunique-1.0-0] libunique-1.0-0: deprecated and unmaintained 
upstream
895520 was blocked by: 885814 947513 885815 885813 947514 885810
895520 was not blocking any bugs.
Added blocking bug(s) of 895520: 947515

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

Bug#947514: midori: build-depends on obsolete libunique-dev

Source: midori
Version: 7.0-2
Severity: serious
Justification: inheriting severity from 895520
Control: block 895520 by -1

src:midori Build-Depends on libunique-dev, which is obsolete and
unmaintained upstream (see #895520 for more details). Its Debian
maintainers, the GNOME team, do not consider libunique to be suitable
for inclusion in the bullseye (Debian 11) stable release.

The midori binary package does not appear to have a Depends on
libunique-1.0-0, which suggests that the build-dependency is no longer
necessary. (Also, midori now depends on GTK 3, but libunique is part of
the older and incompatible GTK 2 stack, so I don't think midori could
be using libunique successfully.)

Please remove this build-dependency, so that the GNOME team can be a
step closer to removing libunique.

Thanks,
smcv

Processed: midori: build-depends on obsolete libunique-dev

Processing control commands:

> block 895520 by -1
Bug #895520 [libunique-1.0-0] libunique-1.0-0: deprecated and unmaintained 
upstream
895520 was blocked by: 885813 885815 885810 885814 947513
895520 was not blocking any bugs.
Added blocking bug(s) of 895520: 947514

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

Processed: Re: Bug#885815: fcitx-config-gtk2: Depends on libunique

Processing control commands:

> block 895520 by -1
Bug #895520 [libunique-1.0-0] libunique-1.0-0: deprecated and unmaintained 
upstream
895520 was blocked by: 885810 885814 947513 885813
895520 was not blocking any bugs.
Added blocking bug(s) of 895520: 885815
> severity -1 serious
Bug #885815 [fcitx-config-gtk2] fcitx-configtool-gtk2: Depends on libunique
Severity set to 'serious' from 'important'

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

Bug#947513: luakit: build-depends on obsolete libunique-dev

Source: luakit
Version: 1:2.1-1
Severity: serious
Justification: inheriting severity from 895520
Control: block 895520 by -1

src:luakit Build-Depends on libunique-dev, which is obsolete and
unmaintained upstream (see #895520 for more details). Its Debian
maintainers, the GNOME team, do not consider libunique to be suitable
for inclusion in the bullseye (Debian 11) stable release.

The luakit binary package does not appear to have a Depends on
libunique-1.0-0, which suggests that the build-dependency is no longer
necessary. (Also, luakit now depends on GTK 3, but libunique is part of
the older and incompatible GTK 2 stack, so I don't think luakit could
be using libunique successfully.)

Please remove this build-dependency, so that the GNOME team can be a
step closer to removing libunique.

Thanks,
smcv

Processed: luakit: build-depends on obsolete libunique-dev

Processing control commands:

> block 895520 by -1
Bug #895520 [libunique-1.0-0] libunique-1.0-0: deprecated and unmaintained 
upstream
895520 was blocked by: 885810 885813 885814
895520 was not blocking any bugs.
Added blocking bug(s) of 895520: 947513

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

Processed: python-jedi: NMU version 0.15.2-0.1 patch

Processing control commands:

> tags 937849 + patch
Bug #937849 [src:python-jedi] python-jedi: Python2 removal in sid/bullseye
Added tag(s) patch.

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

Bug#937849: python-jedi: NMU version 0.15.2-0.1 patch

2019-12-27 Thread Emmanuel Arias

Control: tags 937849 + patch

Dear maintainer,

I've prepared a NMU patch for the package (0.15.2-0.1) that I attach here.

That include a new upstream release.

Thanks!

Cheers,
Arias Emmanuel
@eamanu
http://eamanu.com
From 1c9ae21a282f4c5019e64563722b1660692a57df Mon Sep 17 00:00:00 2001
From: Emmanuel Arias 
Date: Fri, 27 Dec 2019 18:06:10 -0300
Subject: [PATCH] NMU

---
 debian/changelog |  9 +
 debian/control   | 21 ++---
 debian/rules |  2 +-
 3 files changed, 16 insertions(+), 16 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 8bb85c8..53c3caa 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+python-jedi (0.15.2-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * New upstream version 0.15.2
+  * Remove Python 2 Support (Closes: #937849)
+  * Bump Standards-Version to 4.4.1
+
+ -- Emmanuel Arias   Fri, 27 Dec 2019 17:36:40 -0300
+
 python-jedi (0.14.1-1) unstable; urgency=medium
 
   * New upstream release
diff --git a/debian/control b/debian/control
index 3a4ed95..ee9db39 100644
--- a/debian/control
+++ b/debian/control
@@ -3,23 +3,14 @@ Maintainer: Piotr Ożarowski 
 Section: python
 Priority: optional
 Build-Depends: debhelper (>= 10), dh-python,
- python-all, python3-all,
- python-setuptools, python3-setuptools,
- python-pytest, python3-pytest,
- python-unittest2, python3-unittest2,
- python-docopt, python3-docopt,
-Standards-Version: 4.3.0
+ python3-all,
+ python3-setuptools,
+ python3-pytest,
+ python3-unittest2,
+ python3-docopt,
+Standards-Version: 4.4.1
 Homepage: https://github.com/davidhalter/jedi
 
-Package: python-jedi
-Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}, python-parso (>= 0.3)
-Description: autocompletion tool for Python
- Jedi is an autocompletion tool for Python. It works. With and without syntax
- errors. Sometimes it sucks, but that's normal in dynamic languages. But it
- sucks less than other tools. It understands almost all of the basic Python
- syntax elements including many builtins.
-
 Package: python3-jedi
 Architecture: all
 Depends: ${python3:Depends}, ${misc:Depends}, python3-parso (>= 0.3)
diff --git a/debian/rules b/debian/rules
index 4bc2d8b..2bf88ca 100755
--- a/debian/rules
+++ b/debian/rules
@@ -3,7 +3,7 @@
 export PYBUILD_DISABLE=test
 
 %:
-	dh $@ --with python2,python3 --buildsystem=pybuild
+	dh $@ --with python3 --buildsystem=pybuild
 
 override_dh_installchangelogs:
 	dh_installchangelogs CHANGELOG.rst
-- 
2.20.1

Bug#875250: Intend to port to Qt 5

On Thu, Dec 05, 2019 at 11:50:53AM +0800, Benda Xu wrote:
> Hi Moritz,
> 
> I started to work on qt5 port of SCIM.  There is some remaining blocks.
> I will work on it for another 10 days.
> 
> I want to postpone to deadline to Dec 15, if that does not drag the QT5
> migration too much.
> 
> Thank you for your understanding!

scim is now the last package keeping Qt4 in testing, can we please go ahead
with the https://github.com/leggewie-DM/scim/pull/1 MR ? Qt5 support can
still be re-added later, there's ample time before the bullseye freeze.

Cheers,
Moritz

Bug#937071: marked as done (mopidy-beets: Python2 removal in sid/bullseye)

Your message dated Fri, 27 Dec 2019 20:45:17 +
with message-id 
and subject line Bug#937071: fixed in mopidy-beets 4.0.0~rc2-1
has caused the Debian Bug report #937071,
regarding mopidy-beets: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:mopidy-beets

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

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

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

Debian distribution maintenance software
pp.
Stein Magnus Jodal  (supplier of updated mopidy-beets 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, 27 Dec 2019 21:18:31 +0100
Source: mopidy-beets
Architecture: source
Version: 4.0.0~rc2-1
Distribution: unstable
Urgency: medium
Maintainer: Stein Magnus Jodal 
Changed-By: Stein Magnus Jodal 
Closes: 937071
Changes:
 mopidy-beets (4.0.0~rc2-1) unstable; urgency=medium
 .
   * New upstream release
   * Switch from Python 2 to 3 (Closes: #937071)
   * Disable tests because of pkg_resurces usage
   * Bump debhelper from 10 to 12
   * d/clean: Remove custom clean rules
   * d/control: Bump Standards-Version to 4.4.1, no changes
   * d/control: Require mopidy >= 3
   * d/control: Update Description
   * d/copyright: Update copyright years
   * d/copyright: Use HTTPS for the copyright spec
   * d/rules: Install changelog
Checksums-Sha1:
 215823f83c5179a830817af866092184aa9bef8a 1989 mopidy-beets_4.0.0~rc2-1.dsc
 2d1a26759505eb08bee93c5a148ab88c33ec2a9b 14309 
mopidy-beets_4.0.0~rc2.orig.tar.gz

Bug#947510: Asterisk won't response for a while after run the TTS for the first time.

2019-12-27 Thread Jörg Frings-Fürst

Package: asterisk-espeak
Version: 5.0~1-3
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

after install asterisk-easpeak and use via:

[quote]
exten => 888,1,NOOP(Call to 888);
 same => n,Answer();
 same => n,Wait(0.5);
 same => n,Espeak("Hallo. Test")
 same => n,Wait(5.0);
 same => n,Espeak("Hallo. Entschuldigung.");
 same => n,Wait(4.0);
 same => n,Espeak("Hallo. Test");
 same => n,Wait(15.0);
 same => n,Espeak("Test Test");
 same => n,Hangup();
[/quote]

Call Log:
[quote]
Using SIP RTP CoS mark 5
   > 0x7f29f000e010 -- Strict RTP learning after remote address set to:
192.168.1.221:49890
-- Executing [888@firma:1] NoOp("SIP/666-", "Call to 888") in new
stack
-- Executing [888@firma:2] Answer("SIP/666-", "") in new stack
-- Executing [888@firma:3] Wait("SIP/666-", "0.5") in new stack
   > 0x7f29f000e010 -- Strict RTP switching to RTP target address
192.168.1.221:49890 as source
-- Executing [888@firma:4] eSpeak("SIP/666-", ""Hallo. Test"") in
new stack
--  Playing '/tmp/espk_uWEBBn.slin' (language 'de')
-- Executing [888@firma:5] Wait("SIP/666-", "5.0") in new stack
   > 0x7f29f000e010 -- Strict RTP learning complete - Locking on source
address 192.168.1.221:49890
-- Executing [888@firma:6] eSpeak("SIP/666-", ""Hallo.
Entschuldigung."") in new stack
[/quote]

The text from :6 are not playing. After hangup the phone I get a lot of

WARNING[6996]: chan_sip.c:4337 __sip_autodestruct: Autodestruct on dialog
'313537373437393038343234373834-2sf0ko0cwh5y' with owner SIP/666- in
place (Method: BYE). Rescheduling destruction for 1 ms



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

Kernel: Linux 5.3.0-3-amd64 (SMP w/6 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled

Versions of packages asterisk-espeak depends on:
pn  asterisk   
pn  asterisk-1fb7f5c06d7a2052e38d021b3d8ca151  
ii  libc6  2.29-3
ii  libespeak-ng1  1.50+dfsg-4
ii  libsamplerate0 0.1.9-2

asterisk-espeak recommends no packages.

asterisk-espeak suggests no packages.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl4GbRcACgkQCfifPIyh
0l1lUg//R0u87Qk9LD1W55SOFo6LB4M15MOSxdMyKl5s8H+4HbhAp11TL8XWV5h3
+7s/rXp1a0TSO9yqpd7SfcEiGB9Uko65YqUJelmgZAFufQtPBvdLWuJ1T5hybhag
b4/WPgbnLWdJzPnjKnkl3tH4Ae8rGGcY6LnkWZycnBDeh197SK9aM0zYSyN4iRK1
M3flhQ61EKyiDgei0gGk9j9DCK6f4rIsl6xMFnCJnZBEWYjJ0+gii+K/hxC3qWFB
R9sX31+vuyEi7XWw3ILitEGfLQTzVntGBanUWPfZu3ZvLNw4FfhT1p879ue+sZZ0
LBMS336rPV/EBbOOn5VGKVdzRY0HC9je4KDNWTYtW23kQk3poByEfrzc7wdp283t
1VH0mvKHBUGaDXQmn++DTuphm5EUPTnd/KZFn9sXmirmmCwOhNgW9Yy5rjQSVpqM
9S0REe5s5BCC62604ahis59BpwkmXN3dXzF9yNhYk2blf8pjT/6mDOMN4bYFumPV
ohXZBsuX7WQCZqJpN6j+MnueIHRZvk/IKNnOKDprdL5fFUP4DQcG8d5v8Bavy9EP
l7FIazSwSgrNYsHWEEjAmsvQp+OlWl3MWHYLLVML4k35T9RTpyuMnnoJD1emLlG9
XEno9FUe7s7GAEqJuyIQT8DYBtbMlo8ntOdpVzFqCS4bMeNjnSA=
=xWpE
-END PGP SIGNATURE-

Bug#947508: mcomix: Upgrade to Python 3 fork deletes user bookmarks

2019-12-27 Thread Keshav Kini

Package: mcomix
Version: 1.2.1mcomix3+git20190616-1
Severity: critical
Tags: patch upstream
Justification: causes serious data loss

Dear Maintainer,

User bookmarks for the MComix application are stored in a pickle file at
~/.local/share/mcomix/bookmarks.pickle .  The Python 3 fork of MComix which
Debian has switched to is unable to read this file when it has been written by
the earlier, Python 2 version of the application.  When this happens, the
application prints an error message to the console (which most users will not
see since they won't be opening the application from a terminal), and then
proceeds to start up.  Since no bookmarks have been loaded, when the application
saves the current bookmarks back to the file, the contents of the file are reset
and the user's existing bookmark collection is destroyed.

I reported this problem to upstream, here:

  https://github.com/multiSnow/mcomix3/issues/98

I also wrote a pull request to fix the problem, here:

  https://github.com/multiSnow/mcomix3/pull/99

The patch from that PR is attached.  The behavior of the application after
patching is that now it will be able to read a user bookmarks file produced by
the Python 2 version of the applicaton, and if any error is encountered, it will
make a backup of the bookmarks pickle file before proceeding, in order to avoid
data loss.

Thanks,
Keshav

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

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

Versions of packages mcomix depends on:
ii  gir1.2-gtk-3.03.24.13-1
ii  python3   3.7.5-3
ii  python3-cairo 1.16.2-2
ii  python3-gi3.34.0-3
ii  python3-gi-cairo  3.34.0-3
ii  python3-pil   6.2.1-2+b1

Versions of packages mcomix recommends:
ii  python3-chardet  3.0.4-4

Versions of packages mcomix suggests:
pn  mupdf-tools  
ii  p7zip16.02+dfsg-7
ii  unrar1:5.6.6-2

-- no debconf information
>From 8a344788e18a31d34ae1681e1ebe75cd6a02f716 Mon Sep 17 00:00:00 2001
From: Keshav Kini 
Date: Thu, 26 Dec 2019 19:45:23 -0800
Subject: [PATCH] Try to read bookmarks pickled by Python 2

When a pickle file is saved by Python 2, it can be unreadable from Python 3 if
certain kinds of objects are stored in it, such as non-Unicode strings.  To
reliably unpickle these objects, a fallback string encoding must be supplied to
`pickle.load()`.

It turns out that `datetime` objects, which MComix saves as part of each
bookmark, are serialized as non-Unicode binary strings (using the pickle
format's opcode `SHORT_BINSTRING`).  According to the [Python
documentation][1],

> Using `encoding='latin1'` is required for unpickling NumPy arrays and
> instances of *datetime*, *date* and *time* pickled by Python 2.

This commit does as recommended by the above sentence from the documentation.

Furthermore, this commit makes it so that if MComix fails to unpickle the
bookmarks file, it will back up the existing file before proceeding (because
otherwise it will be overwritten with an empty set of bookmarks later).  If the
backup file cannot be saved, the program will crash to avoid destroying the
user's data.

[1]: https://docs.python.org/3/library/pickle.html#pickle.Unpickler "pickle"
---
 mcomix/mcomix/bookmark_backend.py | 12 ++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/mcomix/mcomix/bookmark_backend.py 
b/mcomix/mcomix/bookmark_backend.py
index 0492600..8293ee2 100644
--- a/mcomix/mcomix/bookmark_backend.py
+++ b/mcomix/mcomix/bookmark_backend.py
@@ -6,6 +6,7 @@ from gi.repository import Gtk
 import operator
 import datetime
 import time
+import shutil
 
 from mcomix import constants
 from mcomix import log
@@ -141,8 +142,8 @@ class __BookmarksStore(object):
 try:
 mtime = os.stat(path).st_mtime
 with open(path, 'rb') as fd:
-version = pickle.load(fd)
-packs = pickle.load(fd)
+version = pickle.load(fd, encoding='latin1')
+packs = pickle.load(fd, encoding='latin1')
 
 for pack in packs:
 # Handle old bookmarks without date_added attribute
@@ -155,6 +156,13 @@ class __BookmarksStore(object):
 
 except Exception:
 log.error(_('! Could not parse bookmarks file %s'), path)
+backup_path = path + '.bak'
+if not os.path.exists(backup_path):
+log.warning(_('! Backing up bookmarks file to %s'), 
backup_path)
+shutil.copyfile(path, backup_path)
+else:
+log.error(_('!

Bug#945920: Random Chromium crashes

2019-12-27 Thread Eloston

Hey all,

I highly suspect all of these crashes are due to disable/tracing.patch:
https://salsa.debian.org/chromium-team/chromium/blob/3bcbf4a32166e394c45caf66e1348127284f9094/debian/patches/disable/tracing.patch

Two reasons:

* It is the only patch that makes changes to memory_instrumentation.
* I am maintaining a fork of Debian's Chromium based on 79.0.3945.79 that does
not include disable/tracing.patch, and I don't have any of the segfaults
described in this issue. I've been running my fork daily for a little over a
week without problems.

I don't know why exactly the patch causes the segfault, but the safest solution
is to rebuild Chromium without the changes that disable tracing:

1. Download the debian/ directory from Salsa (above) or via "apt source
chromium". We don't want the orig tarball (we will need to re-generate it)
1. Remove disable/tracing.patch from debian/patches/series
2. Remove disable/perfetto.patch from debian/patches/series (not completely sure
this is necessary, but Catapult and Perfetto are both used in Chromium's
tracing)
3. Remove from debian/copyright's Files-Excluded section:
* Remove any path containing "tracing"
* Remove third_party/perfetto
* Remove third_party/catapult/*
4. Rebuild the browser with a new orig tarball:
a. Install dependencies: mk-build-deps -i debian/control
b. Make new orig tarball: ./debian/rules get-orig-source
c. Now just build normally, e.g. cd chromium-x.x.x.x && dpkg-buildpackage -b
-uc

NOTE: These changes will make the browser depend on minified javascript files
again, which was the original motivation for disabling tracing (as noted in the
header of disable/tracing.patch).

Hope that helps,
Eloston

Processed: your mail

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

> tags 947328 + fixed
Bug #947328 {Done: Thomas Ward } [src:xca] FTBFS: 
dh_installman: mv debian/xca/usr/share/man/man1/xca.1.dh-new: No such file or 
directory
Added tag(s) fixed.
>
End of message, stopping processing here.

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

Bug#921904: win-iconv: FTBFS (wine: chdir to /tmp/wine-I6miLw/server-29-3583b06 : No such file or directory)

2019-12-27 Thread Joseph Nahmias

On Fri, Dec 27, 2019 at 07:27:42PM +, Joseph Nahmias wrote:
> The attached patch works around the issue until that is fixed.

Of course, I forgot this patch... Take 2.
--Joe
diff -Nru win-iconv-0.0.8/debian/changelog win-iconv-0.0.8/debian/changelog
--- win-iconv-0.0.8/debian/changelog	2019-03-12 12:06:01.0 -0400
+++ win-iconv-0.0.8/debian/changelog	2019-12-27 14:04:56.0 -0500
@@ -1,3 +1,11 @@
+win-iconv (0.0.8-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Work around #946951 by initializing WINEPREFIX and adding a symlink,
+closes: #921904.
+
+ -- Joe Nahmias   Fri, 27 Dec 2019 14:04:56 -0500
+
 win-iconv (0.0.8-3) unstable; urgency=medium
 
   * wrap-and-sort -ast
diff -Nru win-iconv-0.0.8/debian/rules win-iconv-0.0.8/debian/rules
--- win-iconv-0.0.8/debian/rules	2019-03-12 11:29:02.0 -0400
+++ win-iconv-0.0.8/debian/rules	2019-12-27 14:04:56.0 -0500
@@ -33,6 +33,8 @@
 override_dh_auto_test:
 ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
 ifdef TESTARCH
+	-WINEPREFIX=$(CURDIR)/build-$(TESTARCH)/.wine wine64 wineboot -i
+	ln -s /tmp/.wine-`id -u`/server* /tmp/wine-*/
 	cd build-$(TESTARCH) && WINEPREFIX=$(shell pwd)/build-$(TESTARCH)/.wine $(MAKE) CC=$(TESTARCH)-gcc AR=$(TESTARCH)-ar RANLIB=$(TESTARCH)-ranlib DLLTOOL=$(TESTARCH)-dlltool test
 endif
 endif

Bug#921904: win-iconv: FTBFS (wine: chdir to /tmp/wine-I6miLw/server-29-3583b06 : No such file or directory)

2019-12-27 Thread Joseph Nahmias

package win-iconv
tags 921904 + patch
thanks

On Fri, Dec 27, 2019 at 06:19:41PM +, Joseph Nahmias wrote:
> Hello,
> 
> On Mon, Mar 18, 2019 at 10:12:55AM -0400, Daniel Kahn Gillmor wrote:
> > 
> > If anyone else needs win-iconv in debian, please speak up!
> > 
> > Otherwise i'll probably move forward with orphaning the package soon.
> > 
> >  --dkg
> 
> Yes, I'm interested in having win-iconv in Debian!
> Also, it seems like this FTBFS is no longer an issue, see the build(s)
> from 2019-11-30 at:
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/win-iconv.html

Spoke too soon, wine version 5.0~rc1-1 was uploaded to sid on 2019-12-18
which brought back this problem.

Upon further review, it seems this is the same as #946951. The attached
patch works around the issue until that is fixed. Not sure if we should
forcemerge this bug with 946951 and tag it affecting win-iconv, or if we
should use the workaround in the attached patch and close this bug... Any
thoughts?

Enjoy,
--Joe

Bug#947328: marked as done (FTBFS: dh_installman: mv debian/xca/usr/share/man/man1/xca.1.dh-new: No such file or directory)

Your message dated Fri, 27 Dec 2019 14:24:43 -0500
with message-id <1d1cbf1f-2541-85ee-1271-8b96ece1a...@ubuntu.com>
and subject line 
has caused the Debian Bug report #947328,
regarding FTBFS: dh_installman: mv debian/xca/usr/share/man/man1/xca.1.dh-new: 
No such file or directory
to be marked as done.

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

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


-- 
947328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xca
Version: 2.1.2-2
Severity: serious
Justification: FTBFS

Hi! During a rebuild your package FTBFS with the following error:

dh_installman: mv debian/xca/usr/share/man/man1/xca.1.dh-new 
debian/xca/usr/share/man/man1/xca.1: No such file or directory

Thanks for your work!

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

Kernel: Linux 5.3.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
DDs have given back the builds to the Buildd system, and the FTBFS 
issues are all resolving themselves thanks to the newer version of 
Debhelper being available with the fix that caused the core issue.


I am marking this bug as resolved and done, as well as having marked it 
as fixed in debhelper.



Thomas--- End Message ---

Bug#936249: bugs-everywhere: Python2 removal in sid/bullseye

2019-12-27 Thread Antoine Beaupré

On 2019-12-26 02:05:56, maxigas wrote:
> On Wed, Dec 25 2019, Moritz Mühlenhoff wrote:
>
>> On Fri, Aug 30, 2019 at 07:12:24AM +, Matthias Klose wrote:
>>> Package: src:bugs-everywhere
>>> Version: 1.1.1-4
>>> Severity: normal
>>> Tags: sid bullseye
>>> User: debian-pyt...@lists.debian.org
>>> Usertags: py2removal
>>> 
>>> Python2 becomes end-of-live upstream, and Debian aims to remove
>>> Python2 from the distribution, as discussed in
>>> https://lists.debian.org/debian-python/2019/07/msg00080.html
>>
>> bugs-everywhere is dead upstream, the last commits are from 2013.
>>
>> Are you planning to port it to Python 3 yourself? Otherwise I'll
>> request it's removal from the archive.
>
> Hm, i'm sorry but i don't think i will have the time to port it.

Same here, and there are alternatives. Just a quick list covering still
active projects:

https://distix.eu/
https://github.com/MichaelMure/git-bug
https://github.com/neithernut/git-dit
https://sit.fyi/

maybe something for the release notes i guess...

a.
-- 
Information is not knowledge. Knowledge is not wisdom.
Wisdom is not truth. Truth is not beauty.
Beauty is not love. Love is not music.
Music is the best.  - Frank Zappa

Processed: your mail

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

> tags 947328 - pending
Bug #947328 [src:xca] FTBFS: dh_installman: mv 
debian/xca/usr/share/man/man1/xca.1.dh-new: No such file or directory
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Processed: your mail

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

> fixed 947328 debhelper/12.7.2
Bug #947328 [src:xca] FTBFS: dh_installman: mv 
debian/xca/usr/share/man/man1/xca.1.dh-new: No such file or directory
Marked as fixed in versions debhelper/12.7.2.
>
End of message, stopping processing here.

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

Bug#945920: Random Chromium crashes

2019-12-27 Thread Michel Meyers


Hello,

Been running Chromium for the last 6 hours now, no crash since, so it 
looks like that last patch finally got it.


- Michel

Bug#945920: Random Chromium crashes

2019-12-27 Thread Stefan Bühler

Hi,

On Fri, 27 Dec 2019 15:31:13 +0100 Jaap Joris Vens  wrote:
> On Fri, Dec 27, 2019 at 01:29:13PM +0100, Stefan Bühler wrote:
> >Hi,
> >
> >yes, you are right, my patch only fixes the task manager crash.
> >
> >I now took a look at all backtraces, and all apart the first one
> >(probably older version?) seem to be the same "other" instance:
> >
> --- 8< ---
> 
> I am not quite following the intricacies of this crash anymore, but might
> this be something that we will need to report upstream?

Yes, that is how it looks to me (although I didn't take a look at the
debian patches and whether they have any impact on this). I don't quite
understand under which circumstances the MemoryInstrumentation
"singleton" instance is supposed to exist; but more importantly I
couldn't see any relation between the conditions when it gets created
and when it gets used.

Which imho means all uses need to check whether the instance actually
exists, or creating it automatically whenever it is requested.

Apart from that the singleton pointer is managed in a very dangerous
manner; the destructor will reset the singleton pointer, which makes it
look like that is supposed to do something meaningful, but in a
multi-threaded environment this simply can't go well imho; this probably
should use shared ownership and locking, or `call_once` and never
destroying it ever (and maybe calling abort in the destructor...).

cheers,
Stefan

Processed: fixed 914963 in python-pynvim/0.4.0-1, closing 914963, fixed 945605 in python-pynvim/0.4.0-1 ...

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

> fixed 914963 python-pynvim/0.4.0-1
Bug #914963 [python3-neovim] python3-neovim: Package renamed upstream to pynvim
Marked as fixed in versions python-pynvim/0.4.0-1.
> close 914963
Bug #914963 [python3-neovim] python3-neovim: Package renamed upstream to pynvim
Marked Bug as done
> fixed 945605 python-pynvim/0.4.0-1
Bug #945605 [src:python-neovim] python-neovim: autopkgtest needs update for new 
version of neovim: Invalid option name: 'listchars'
Marked as fixed in versions python-pynvim/0.4.0-1.
> close 945605
Bug #945605 [src:python-neovim] python-neovim: autopkgtest needs update for new 
version of neovim: Invalid option name: 'listchars'
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#945605: closing 914963, closing 945605

2019-12-27 Thread James McCoy

# These were fixed with upstream's 0.4.0 release, but I forgot to include the
# Closes entries in the changelog
#
#  * New upstream version 0.4.0
#- Fix FTBFS with neovim >= 0.4 (Closes: #945605)
#- Renamed to python-pynvim (Closes: #914963)
close 914963 python-pynvim/0.4.0-1
close 945605 python-pynvim/0.4.0-1
thanks
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#927136: src:zabbix-cli: Please update to python3

On Sun, Aug 25, 2019 at 01:21:29AM -0400, Scott Kitterman wrote:
> On Mon, 15 Apr 2019 08:56:40 -0400 Scott Kitterman  
> wrote:
> > Package: src:zabbix-cli
> > Version: 1.7.0-1
> > Severity: important
> > 
> > Python2.7 will go out of upstream security support during the Bullseye
> > development cycle.  It is not safe to assume it will be included in the
> > next release, so if you want to be sure zabbix-cli can stay in Debian, 
> please
> > update it to the python3 version available from upstream..
> > 
> > Personally, I want to remove some packages I maintain, particularly python-
> > ipaddr, which zabbix-cli depends on during the Bullseye cycle, regardless of
> > what happens to python2.7, so please update (python3 includes the ipaddress
> > module, which was developed from ipaddr, in the standard library).
> 
> Bumping to serious because python-ipaddr will be removed soon.  Upstream 
> support python3.  Please update to a new version or ack that you've lost 
> interest in the package and I'll ask to have it removed.

Current 2.1.x versions support Python 3, are there any plans to update the 
package?
Otherwise I'll file a removal bug.

Cheers,
Moritz

Bug#936172: autotrash: Python2 removal in sid/bullseye

On Fri, Aug 30, 2019 at 07:11:02AM +, Matthias Klose wrote:
> Package: src:autotrash
> Version: 0.1.5-1.1
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
> 
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2 from the distribution, as discussed in
> https://lists.debian.org/debian-python/2019/07/msg00080.html
> 
> Your package either build-depends, depends on Python2, or uses Python2
> in the autopkg tests.  Please stop using Python2, and fix this issue
> by one of the following actions.

Current upstream releases support Python 3, but the package hasn't seen
an upload since 2011. Are you still interested in the package, otherwise
I'll file a removal bug.

Cheers,
Moritz

Bug#945741: tcvt: Python2 removal in sid/bullseye

2019-12-27 Thread wferi

Helmut Grohne  writes:

> On Wed, Nov 27, 2019 at 11:58:53PM +, Sandro Tosi wrote:
>
>> - Convert your Package to Python3. This is the preferred option.
>
> Upstream here. While tcvt started on Python2, much of its development
> actually happend on Python3, so just changing the #! should work.

And I wanted to package it for Python3 in the first place.  I'm puzzled
that it uses Python2 despite dh --with python3 and the python3 build
dependency.  I'd be grateful for an explanation or some suggestions.
-- 
Thanks,
Feri

Bug#921904: win-iconv: FTBFS (wine: chdir to /tmp/wine-I6miLw/server-29-3583b06 : No such file or directory)

2019-12-27 Thread Joseph Nahmias

Hello,

On Mon, Mar 18, 2019 at 10:12:55AM -0400, Daniel Kahn Gillmor wrote:
> On Mon 2019-03-18 10:55:44 +0100, Tim Rühsen wrote:
> > Libiconv 1.15 itself from tarball.
> >
> > If you are interested in the details, have a look at our CI Dockerfile
> > where we build/install the dependencies needed for testing:
> >
> > https://gitlab.com/gnuwget/build-images/blob/master/docker-debian-mingw/Dockerfile
> 
> interesting, thanks!
> 
> If anyone else needs win-iconv in debian, please speak up!
> 
> Otherwise i'll probably move forward with orphaning the package soon.
> 
>  --dkg

Yes, I'm interested in having win-iconv in Debian!
Also, it seems like this FTBFS is no longer an issue, see the build(s)
from 2019-11-30 at:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/win-iconv.html

Thanks,
--Joe

Processed: Re: Bug#936165: autodocktools and mgltools-pmv are about to be removed from Debian

Processing control commands:

> clone 936165 -2 -3
Bug #936165 [ftp.debian.org] ROM: Please remove autodocktools which depends 
from to be removed mgltools-pmv
Bug 936165 cloned as bugs 947501-947502
936183 was blocked by: 945659 936165 945634
936183 was blocking: 937569 937695 938490 938656
Added blocking bug(s) of 936183: 947501
936183 was blocked by: 945634 947501 936165 945659
936183 was blocking: 937569 937695 938490 938656
Added blocking bug(s) of 936183: 947502
937020 was blocked by: 936165
937020 was blocking: 937039 937042 937238 937695 938219
Added blocking bug(s) of 937020: 947501
937020 was blocked by: 947501 936165
937020 was blocking: 937039 937042 937238 937695 938219
Added blocking bug(s) of 937020: 947502
937026 was blocked by: 937029 947294 936165 947301 937030
937026 was blocking: 937019 937021 937022 937031 937034 937262 937695 937960
Added blocking bug(s) of 937026: 947501
937026 was blocked by: 936165 947501 937029 937030 947301 947294
937026 was blocking: 937019 937021 937022 937031 937034 937262 937695 937960
Added blocking bug(s) of 937026: 947502
937029 was blocked by: 936165
937029 was blocking: 936165 937022 937023 937025 937026 937028 937033 937035 
937037 937038 937290 937695 938922
Added blocking bug(s) of 937029: 947501
937029 was blocked by: 936165 947501
937029 was blocking: 936165 937022 937023 937025 937026 937028 937033 937035 
937037 937038 937290 937695 938922
Added blocking bug(s) of 937029: 947502
937030 was blocked by: 936165 947294
937030 was blocking: 937026 937695 937960
Added blocking bug(s) of 937030: 947501
937030 was blocked by: 947294 947501 936165
937030 was blocking: 937026 937695 937960
Added blocking bug(s) of 937030: 947502
937035 was blocked by: 937029 947301 937039 947294 936165
937035 was blocking: 937695
Added blocking bug(s) of 937035: 947501
937035 was blocked by: 947501 937039 936165 947294 947301 937029
937035 was blocking: 937695
Added blocking bug(s) of 937035: 947502
937037 was blocked by: 947301 937029 936165 947294
937037 was blocking: 937695 937960
Added blocking bug(s) of 937037: 947501
937037 was blocked by: 947294 947301 937029 947501 936165
937037 was blocking: 937695 937960
Added blocking bug(s) of 937037: 947502
937038 was blocked by: 947294 936165 937029 947301
937038 was blocking: 937019 937569 937695
Added blocking bug(s) of 937038: 947501
937038 was blocked by: 936165 947501 937029 947294 947301
937038 was blocking: 937019 937569 937695
Added blocking bug(s) of 937038: 947502
937041 was blocked by: 947294 936165
937041 was blocking: 937695 937960
Added blocking bug(s) of 937041: 947501
937041 was blocked by: 947501 936165 947294
937041 was blocking: 937695 937960
Added blocking bug(s) of 937041: 947502
937042 was blocked by: 947294 936165 937020
937042 was blocking: 937695
Added blocking bug(s) of 937042: 947501
937042 was blocked by: 947501 937020 936165 947294
937042 was blocking: 937695
Added blocking bug(s) of 937042: 947502
937695 was blocked by: 937033 947231 936606 943027 945661 938366 936899 938890 
943049 936936 936557 936869 938860 938523 936447 937711 937251 937788 938420 
938209 937514 937083 937411 936158 938720 936729 943120 937488 936695 942995 
937244 938305 936665 937738 937307 936952 937993 936974 943288 936343 937417 
934870 936735 936741 936123 937176 936544 943217 936454 936485 938359 943148 
936875 936472 938157 938748 937184 938234 937703 936772 938448 936214 937500 
945667 936785 943021 937403 942979 936551 938043 938276 936832 945745 938670 
945731 937257 937717 938715 943203 938558 943115 938050 937259 937719 937334 
945699 936208 938428 943230 942977 943035 936505 943041 936891 936150 938357 
945704 937870 937480 937101 936566 937419 936524 936596 943280 936323 937730 
936721 943054 938753 938351 943466 943153 937296 937660 937224 936749 945675 
936358 937266 945682 943140 942942 936727 936283 945710 937000 939478 937508 
936449 938440 936867 938543 936427 938124 938196 938166 938058 936559 943047 
942971 936897 938222 937267 936805 936591 937773 936726 936794 938568 936910 
938295 945657 938598 937297 936561 938369 936609 938600 936464 926244 938167 
936939 943046 943273 937570 937078 936866 936702 936426 937658 942909 937473 
937883 937940 938279 936962 942976 936992 945644 942955 938614 938850 938375 
936859 938382 936634 937261 936904 937179 937377 938843 945651 942934 936312 
937808 937291 938463 938156 937814 938068 936569 938823 938560 938098 936599 
938590 936918 936857 937232 937379 936981 937177 938608 937256 938793 937643 
943193 945624 938391 937275 938763 943163 937578 936601 945666 937070 938361 
936945 936931 936398 938277 939104 945736 936190 943064 947302 938367 943026 
936844 936937 936556 938271 938683 938858 936532 939483 937269 937171 937800 
938402 936222 938591 937042 945623 937644 943194 943126 938069 938794 936919 
943164 938764 938099 937378 938464 937071 938360 936167 939111 943102 937579 
938866 938702 938390 936206 937077 942914 936161 938655 938684 936332 938270 
936279

Bug#855494: Suggested removal of mgltools from Debian (Was: SVN to Git migration status)

Control: reassign 855485 mgltools-pmv
Control: severity 855485 grave
Control: retitle 855485 mgltools-pmv: runPmv script does not work: TclError: 
cannot use geometry manager grid
Control: reassign 855494 mgltools-pmv
Control: retitle 855494 mgltools-pmv: runPmv script does not work: ImportError: 
No module named oldnumeric
Control: retitle 855701 RM: mgltools-pmv -- RoQA; RC bug with fix unlikely, low 
popcon, Python 2
Control: tags 855701 + moreinfo
Control: reassign 937029 mgltools-pmv
Control: retitle 937029 mgltools-pmv: Python2 removal in sid/bullseye

On Thu, 12 Dec 2019 at 09:38:30 +0100, Andreas Tille wrote:
> Control: reassign -1 ftp.debian.org
> Control: retitle -1 ROM: Please remove package mgltools-pmv

It's often clearer to leave RC bugs assigned to the package that has the
bug, and create a new RM: RoM or RM: RoQA bug against the ftp.debian.org
pseudo-package to represent the removal request. I'm repurposing #855701
for that, since that one seems to be a duplicate of #855485 already.

At the moment someone looking at the bug list of mgltools-pmv has no
indication that it is known to be broken, which doesn't seem to be ideal.

The ftp team can't remove mgltools-pmv until the packages that depend on
it have been removed (transcript below), so I'm tagging it moreinfo, and
will follow up by adding blockers. ftp team members processing removals
won't generally chase up the reverse-dependencies themselves, because only
a few people have ftp team powers, so they prefer to spend their limited
time doing tasks only ftp team members can do. As a result they rely on
QA team members[1] to present them with immediately-actionable bugs.

The bugs that are assigned to mgltools-pmv will be closed automatically
when mgltools-pmv is removed from the archive.

smcv

[1] i.e. anyone who happens to be looking at a bug

8<
smcv@coccia ~ % dak rm -R -n mgltools-pmv
Will remove the following packages from unstable:

mgltools-pmv |1.5.7-3 | source, all
mgltools-pmv-test |1.5.7-3 | all

Maintainer: Debian Med Packaging Team 

--- Reason ---

--

Checking reverse dependencies...
# Broken Depends:
autodocktools/non-free: autodocktools

Dependency problem found.

smcv@coccia ~ % dak rm -R -n autodocktools mgltools-pmv
Will remove the following packages from unstable:

autodocktools |1.5.7-4 | source, all
mgltools-pmv |1.5.7-3 | source, all
mgltools-pmv-test |1.5.7-3 | all

Maintainer: Debian Med Packaging Team 

--- Reason ---

--

Checking reverse dependencies...
# Broken Depends:
raccoon/contrib: raccoon

Dependency problem found.

8<

Processed: Re: Bug#855494: Suggested removal of mgltools from Debian (Was: SVN to Git migration status)

Processing control commands:

> reassign 855485 mgltools-pmv
Bug #855485 [mgltools-pmv] mgltools-pmv: runPmv script does not work: TclError: 
cannot use geometry manager grid
Ignoring request to reassign bug #855485 to the same package
> severity 855485 grave
Bug #855485 [mgltools-pmv] mgltools-pmv: runPmv script does not work: TclError: 
cannot use geometry manager grid
Ignoring request to change severity of Bug 855485 to the same value.
> retitle 855485 mgltools-pmv: runPmv script does not work: TclError: cannot 
> use geometry manager grid
Bug #855485 [mgltools-pmv] mgltools-pmv: runPmv script does not work: TclError: 
cannot use geometry manager grid
Ignoring request to change the title of bug#855485 to the same title
> reassign 855494 mgltools-pmv
Bug #855494 [mgltools-pmv] mgltools-pmv: runPmv script does not work: 
ImportError: No module named oldnumeric
Ignoring request to reassign bug #855494 to the same package
> retitle 855494 mgltools-pmv: runPmv script does not work: ImportError: No 
> module named oldnumeric
Bug #855494 [mgltools-pmv] mgltools-pmv: runPmv script does not work: 
ImportError: No module named oldnumeric
Ignoring request to change the title of bug#855494 to the same title
> retitle 855701 RM: mgltools-pmv -- RoQA; RC bug with fix unlikely, low 
> popcon, Python 2
Bug #855701 [ftp.debian.org] RM: mgltools-pmv -- RoQA; RC bug with fix 
unlikely, low popcon, Python 2
Ignoring request to change the title of bug#855701 to the same title
> tags 855701 + moreinfo
Bug #855701 [ftp.debian.org] RM: mgltools-pmv -- RoQA; RC bug with fix 
unlikely, low popcon, Python 2
Ignoring request to alter tags of bug #855701 to the same tags previously set
> reassign 937029 mgltools-pmv
Bug #937029 [mgltools-pmv] mgltools-pmv: Python2 removal in sid/bullseye
Ignoring request to reassign bug #937029 to the same package
> retitle 937029 mgltools-pmv: Python2 removal in sid/bullseye
Bug #937029 [mgltools-pmv] mgltools-pmv: Python2 removal in sid/bullseye
Ignoring request to change the title of bug#937029 to the same title

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

Processed: Re: Bug#855494: Suggested removal of mgltools from Debian (Was: SVN to Git migration status)

Processing control commands:

> reassign 855485 mgltools-pmv
Bug #855485 [mgltools-pmv] mgltools-pmv: runPmv script does not work: TclError: 
cannot use geometry manager grid
Ignoring request to reassign bug #855485 to the same package
> severity 855485 grave
Bug #855485 [mgltools-pmv] mgltools-pmv: runPmv script does not work: TclError: 
cannot use geometry manager grid
Ignoring request to change severity of Bug 855485 to the same value.
> retitle 855485 mgltools-pmv: runPmv script does not work: TclError: cannot 
> use geometry manager grid
Bug #855485 [mgltools-pmv] mgltools-pmv: runPmv script does not work: TclError: 
cannot use geometry manager grid
Ignoring request to change the title of bug#855485 to the same title
> reassign 855494 mgltools-pmv
Bug #855494 [mgltools-pmv] mgltools-pmv: runPmv script does not work: 
ImportError: No module named oldnumeric
Ignoring request to reassign bug #855494 to the same package
> retitle 855494 mgltools-pmv: runPmv script does not work: ImportError: No 
> module named oldnumeric
Bug #855494 [mgltools-pmv] mgltools-pmv: runPmv script does not work: 
ImportError: No module named oldnumeric
Ignoring request to change the title of bug#855494 to the same title
> retitle 855701 RM: mgltools-pmv -- RoQA; RC bug with fix unlikely, low 
> popcon, Python 2
Bug #855701 [ftp.debian.org] RM: mgltools-pmv -- RoQA; RC bug with fix 
unlikely, low popcon, Python 2
Ignoring request to change the title of bug#855701 to the same title
> tags 855701 + moreinfo
Bug #855701 [ftp.debian.org] RM: mgltools-pmv -- RoQA; RC bug with fix 
unlikely, low popcon, Python 2
Ignoring request to alter tags of bug #855701 to the same tags previously set
> reassign 937029 mgltools-pmv
Bug #937029 [mgltools-pmv] mgltools-pmv: Python2 removal in sid/bullseye
Ignoring request to reassign bug #937029 to the same package
> retitle 937029 mgltools-pmv: Python2 removal in sid/bullseye
Bug #937029 [mgltools-pmv] mgltools-pmv: Python2 removal in sid/bullseye
Ignoring request to change the title of bug#937029 to the same title

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

Processed: Re: Bug#855494: Suggested removal of mgltools from Debian (Was: SVN to Git migration status)

Processing control commands:

> reassign 855485 mgltools-pmv
Bug #855485 [mgltools-pmv] mgltools-pmv: runPmv script does not work: TclError: 
cannot use geometry manager grid
Ignoring request to reassign bug #855485 to the same package
> severity 855485 grave
Bug #855485 [mgltools-pmv] mgltools-pmv: runPmv script does not work: TclError: 
cannot use geometry manager grid
Ignoring request to change severity of Bug 855485 to the same value.
> retitle 855485 mgltools-pmv: runPmv script does not work: TclError: cannot 
> use geometry manager grid
Bug #855485 [mgltools-pmv] mgltools-pmv: runPmv script does not work: TclError: 
cannot use geometry manager grid
Ignoring request to change the title of bug#855485 to the same title
> reassign 855494 mgltools-pmv
Bug #855494 [mgltools-pmv] mgltools-pmv: runPmv script does not work: 
ImportError: No module named oldnumeric
Ignoring request to reassign bug #855494 to the same package
> retitle 855494 mgltools-pmv: runPmv script does not work: ImportError: No 
> module named oldnumeric
Bug #855494 [mgltools-pmv] mgltools-pmv: runPmv script does not work: 
ImportError: No module named oldnumeric
Ignoring request to change the title of bug#855494 to the same title
> retitle 855701 RM: mgltools-pmv -- RoQA; RC bug with fix unlikely, low 
> popcon, Python 2
Bug #855701 [ftp.debian.org] RM: mgltools-pmv -- RoQA; RC bug with fix 
unlikely, low popcon, Python 2
Ignoring request to change the title of bug#855701 to the same title
> tags 855701 + moreinfo
Bug #855701 [ftp.debian.org] RM: mgltools-pmv -- RoQA; RC bug with fix 
unlikely, low popcon, Python 2
Ignoring request to alter tags of bug #855701 to the same tags previously set
> reassign 937029 mgltools-pmv
Bug #937029 [mgltools-pmv] mgltools-pmv: Python2 removal in sid/bullseye
Ignoring request to reassign bug #937029 to the same package
> retitle 937029 mgltools-pmv: Python2 removal in sid/bullseye
Bug #937029 [mgltools-pmv] mgltools-pmv: Python2 removal in sid/bullseye
Ignoring request to change the title of bug#937029 to the same title

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

Processed: Re: Bug#855494: Suggested removal of mgltools from Debian (Was: SVN to Git migration status)

Processing control commands:

> reassign 855485 mgltools-pmv
Bug #855485 [ftp.debian.org] ROM: Please remove package mgltools-pmv
Bug reassigned from package 'ftp.debian.org' to 'mgltools-pmv'.
Ignoring request to alter found versions of bug #855485 to the same values 
previously set
Ignoring request to alter fixed versions of bug #855485 to the same values 
previously set
> severity 855485 grave
Bug #855485 [mgltools-pmv] ROM: Please remove package mgltools-pmv
Severity set to 'grave' from 'normal'
> retitle 855485 mgltools-pmv: runPmv script does not work: TclError: cannot 
> use geometry manager grid
Bug #855485 [mgltools-pmv] ROM: Please remove package mgltools-pmv
Changed Bug title to 'mgltools-pmv: runPmv script does not work: TclError: 
cannot use geometry manager grid' from 'ROM: Please remove package 
mgltools-pmv'.
> reassign 855494 mgltools-pmv
Bug #855494 [ftp.debian.org] ROM: Please remove package mgltools-pmv
Bug reassigned from package 'ftp.debian.org' to 'mgltools-pmv'.
Ignoring request to alter found versions of bug #855494 to the same values 
previously set
Ignoring request to alter fixed versions of bug #855494 to the same values 
previously set
> retitle 855494 mgltools-pmv: runPmv script does not work: ImportError: No 
> module named oldnumeric
Bug #855494 [mgltools-pmv] ROM: Please remove package mgltools-pmv
Changed Bug title to 'mgltools-pmv: runPmv script does not work: ImportError: 
No module named oldnumeric' from 'ROM: Please remove package mgltools-pmv'.
> retitle 855701 RM: mgltools-pmv -- RoQA; RC bug with fix unlikely, low 
> popcon, Python 2
Bug #855701 [ftp.debian.org] ROM: Please remove package mgltools-pmv
Changed Bug title to 'RM: mgltools-pmv -- RoQA; RC bug with fix unlikely, low 
popcon, Python 2' from 'ROM: Please remove package mgltools-pmv'.
> tags 855701 + moreinfo
Bug #855701 [ftp.debian.org] RM: mgltools-pmv -- RoQA; RC bug with fix 
unlikely, low popcon, Python 2
Added tag(s) moreinfo.
> reassign 937029 mgltools-pmv
Bug #937029 [ftp.debian.org] ROM: Please remove package mgltools-pmv
Bug reassigned from package 'ftp.debian.org' to 'mgltools-pmv'.
Ignoring request to alter found versions of bug #937029 to the same values 
previously set
Ignoring request to alter fixed versions of bug #937029 to the same values 
previously set
> retitle 937029 mgltools-pmv: Python2 removal in sid/bullseye
Bug #937029 [mgltools-pmv] ROM: Please remove package mgltools-pmv
Changed Bug title to 'mgltools-pmv: Python2 removal in sid/bullseye' from 'ROM: 
Please remove package mgltools-pmv'.

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

Processed: tagging 947468

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

> tags 947468 + pending
Bug #947468 [src:php-twig] php-twig: missing Build-Depends: php-symfony-string
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed (with 1 error): forcibly merging 936742 947297

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

> forcemerge 936742 947297
Bug #936742 [ipykernel-py2] ipykernel: Python2 removal in sid/bullseye
Unable to merge bugs because:
package of #947297 is 'src:ipykernel-py2' not 'ipykernel-py2'
Failed to forcibly merge 936742: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: caffe: depends on python3-leveldb whose removal has been requested