Bug#949274: pyresample autopkg tests regressed in unstable

[Matthias Klose]

Package: src:pyresample
Version: 1.14.0-2
Severity: serious
Tags: sid bullseye

https://ci.debian.net/data/autopkgtest/unstable/amd64/p/pyresample/4019144/log.gz

[...]
==
FAIL: test_get_area_def_from_raster_extracts_proj_id
(pyresample.test.test_utils.TestMisc)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pyresample/test/test_utils.py", line 477,
in test_get_area_def_from_raster_extracts_proj_id
self.assertEqual(area_def.proj_id, 'WGS 84 / Pseudo-Mercator')
AssertionError: 'WGS_1984_Web_Mercator_Auxiliary_Sphere' != 'WGS 84 /
Pseudo-Mercator'
- WGS_1984_Web_Mercator_Auxiliary_Sphere
+ WGS 84 / Pseudo-Mercator


--
Ran 271 tests in 193.325s

FAILED (failures=1, skipped=2)

Bug#949268: complexity FTBFS: missing Build-Depends: texinfo

[Helmut Grohne]

Source: complexity
Version: 1.10+dfsg-3
Severity: serious
Tags: ftbfs

complexity fails to build from source, because gnulib dropped its
dependency on texinfo and now complexity misses the makeinfo command
during build. Please add texinfo to Build-Depends.

Helmut

Bug#945738: marked as done (squid-deb-proxy: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jan 2020 01:47:31 -0500
with message-id 

and subject line Re: squid-deb-proxy: Python2 removal in sid/bullseye
has caused the Debian Bug report #945738,
regarding squid-deb-proxy: 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.)


-- 
945738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: squid-deb-proxy
Version: 0.8.14+nmu2
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: 0.8.15

On Wed, 27 Nov 2019 23:58:53 + Sandro Tosi  wrote:
> Source: squid-deb-proxy
> Version: 0.8.14+nmu2
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal

https://tracker.debian.org/news/1094859/accepted-squid-deb-proxy-0815-source-into-unstable/--- End Message ---

Processed: transition: netcdf

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://release.debian.org/transitions/html/auto-netcdf.html
Bug #949267 [release.debian.org] transition: netcdf
Set Bug forwarded-to-address to 
'https://release.debian.org/transitions/html/auto-netcdf.html'.
> block -1 by 949150 949157 908105 949132 949134
Bug #949267 [release.debian.org] transition: netcdf
949267 was not blocked by any bugs.
949267 was not blocking any bugs.
Added blocking bug(s) of 949267: 908105, 949134, 949132, 949157, and 949150

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

Bug#936669: marked as done (gr-radar: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jan 2020 01:37:33 -0500
with message-id 

and subject line Re: gr-radar: Python2 removal in sid/bullseye
has caused the Debian Bug report #936669,
regarding gr-radar: 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.)


-- 
936669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gr-radar
Version: 0.0.0.20180308-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:gr-radar

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: 0.0.0.20180308-2

On Fri, 30 Aug 2019 07:19:52 + Matthias Klose  wrote:
> Package: src:gr-radar
> Version: 0.0.0.20180308-1
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal

https://tracker.debian.org/news/1084881/accepted-gr-radar-00020180308-2-source-amd64-all-into-experimental-experimental/--- End Message ---

Bug#936463: marked as done (ecasound: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jan 2020 01:29:54 -0500
with message-id 

and subject line Re: Bug#936463: ecasound: Python2 removal in sid/bullseye - 
reopen 936463
has caused the Debian Bug report #936463,
regarding ecasound: 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.)


-- 
936463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ecasound
Version: 2.9.1-7
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:ecasound

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 ---
On Sun, Jan 19, 2020 at 1:05 AM Stuart Prescott  wrote:
>
> Sandro Tosi wrote:
>
> > Control: reopen -1
> >
> > This bug was closed, but the package has still some dependencies towards
> > Python2 packages, in details:
> >
> > (source:ecasound)Build-Depends->python-all
> > (source:ecasound)Build-Depends->python-docutils
> > (binary:ecatools)Depends->python:any
> > (binary:ecatools)Depends->python-ecasound
> > (binary:python-ecasound)Depends->python:any
> > (binary:python-ecasound)Depends->python:any
> >
> > Re-opening, so that they can be taken care of.
>
> That is not correct, the fixed package version was 2.9.3-1 and the
> dependencies you've quoted there are for 2.9.1-7.

this was uploaded only a few hours before this script ran, which means
the package wasnt available in my apt cache, while still the BTS had
the bug as done; closing it now again

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi--- End Message ---

Bug#938072: marked as done (python-pyknon: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jan 2020 01:31:08 -0500
with message-id 

and subject line Re: Bug#938072: python-pyknon: Python2 removal in sid/bullseye 
- reopen 938072
has caused the Debian Bug report #938072,
regarding python-pyknon: 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.)


-- 
938072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-pyknon
Version: 1.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:python-pyknon

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 ---
On Sun, Jan 19, 2020 at 1:10 AM Stuart Prescott  wrote:
>
> Sandro Tosi wrote:
>
> > Control: reopen -1
> >
> > This bug was closed, but the package has still some dependencies towards
> > Python2 packages, in details:
> >
> > (source:python-pyknon)Build-Depends->python-all-dev
> > (source:python-pyknon)Build-Depends->python-sphinx
> > (source:python-pyknon)Build-Depends->python-pytest
> > (binary:python-pyknon)Depends->python
> > (binary:python-pyknon)Depends->python
> > (binary:python-pyknon)Depends->python:any
> >
> > Re-opening, so that they can be taken care of.
>
> That is not correct. src:python-pyknon 1.2-2 in sid does not build the
> python-pyknon binary package at all and does not have the listed Build-
> Depends.

same thing here: the package hit the archive only few hours before the
script ran, so my apt mirror wasnt up to date yet. closing it again

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi--- End Message ---

Bug#925776: marked as done (mergelog: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jan 2020 06:20:52 +
with message-id 
and subject line Bug#925776: fixed in mergelog 4.5.1-10
has caused the Debian Bug report #925776,
regarding mergelog: ftbfs with GCC-9
to be marked as done.

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

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


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

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

[...]
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for unistd.h... (cached) yes
checking for size_t... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for working memcmp... yes
checking for mktime... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating man/Makefile
config.status: executing depfiles commands
configure: WARNING: unrecognized options: --disable-maintainer-mode
make[1]: Leaving directory '/<>'
   dh_auto_build -a
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
make -j1
make[1]: Entering directory '/<>'
Making all in src
make[2]: Entering directory '/<>/src'
gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DHAVE_LIBZ=1 
-DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 
-DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 
-DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_UNISTD_H=1 -DHAVE_MKTIME=1 -I. 
-g -O2 -lz  -DVERSION=\"4.5.1\" -Wall mergelog.c -o mergelog
gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DHAVE_LIBZ=1 
-DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 
-DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 
-DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_UNISTD_H=1 -DHAVE_MKTIME=1 -I. 
-g -O2 -lz  -DVERSION=\"4.5.1\" -Wall -DUSE_ZLIB mergelog.c -o zmergelog
mergelog.c: In function 'fast_gzgets':
mergelog.c:73:23: warning: passing argument 1 of 'gzread' from incompatible 
pointer type [-Wincompatible-pointer-types]
   73 |   f_end[i]=gzread(fp, f_buf[i], GZBUFFER_SIZE)+f_buf[i]-1;
  |   ^~
  |   |
  |   struct gzFile_s **
In file included from /usr/include/zlib.h:34,
 from mergelog.c:29:
/usr/include/zlib.h:1390:28: note: expected 'gzFile' {aka 'struct gzFile_s *'} 
but argument is of type 'struct gzFile_s **'
 1390 | ZEXTERN int ZEXPORT gzread OF((gzFile file, voidp buf, unsigned len));
  |^~
mergelog.c: In function 'main':
mergelog.c:135:18: warning

Bug#938072: python-pyknon: Python2 removal in sid/bullseye - reopen 938072

[Stuart Prescott]

Sandro Tosi wrote:

> Control: reopen -1
> 
> This bug was closed, but the package has still some dependencies towards
> Python2 packages, in details:
> 
> (source:python-pyknon)Build-Depends->python-all-dev
> (source:python-pyknon)Build-Depends->python-sphinx
> (source:python-pyknon)Build-Depends->python-pytest
> (binary:python-pyknon)Depends->python
> (binary:python-pyknon)Depends->python
> (binary:python-pyknon)Depends->python:any
> 
> Re-opening, so that they can be taken care of.

That is not correct. src:python-pyknon 1.2-2 in sid does not build the 
python-pyknon binary package at all and does not have the listed Build-
Depends.



-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Bug#936463: ecasound: Python2 removal in sid/bullseye - reopen 936463

[Stuart Prescott]

Sandro Tosi wrote:

> Control: reopen -1
> 
> This bug was closed, but the package has still some dependencies towards
> Python2 packages, in details:
> 
> (source:ecasound)Build-Depends->python-all
> (source:ecasound)Build-Depends->python-docutils
> (binary:ecatools)Depends->python:any
> (binary:ecatools)Depends->python-ecasound
> (binary:python-ecasound)Depends->python:any
> (binary:python-ecasound)Depends->python:any
> 
> Re-opening, so that they can be taken care of.

That is not correct, the fixed package version was 2.9.3-1 and the 
dependencies you've quoted there are for 2.9.1-7.

-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Bug#949264: nageru: FTBFS on arm/i386/mipsel architectures

[Boyuan Yang]

Package: nageru
Severity: serious
Version: 1.9.1-1.1

Recent source-only rebuild for nageru has mulitple FTBFS architectures on
buildd: https://buildd.debian.org/status/package.php?p=nageru

The tail log all reads like this:

/usr/bin/ld: libcore.a(nageru_timecode_renderer.cpp.o): in function
`TimecodeRenderer::TimecodeRenderer(movit::ResourcePool*, unsigned int,
unsigned int)':
./obj-mipsel-linux-gnu/../nageru/timecode_renderer.cpp:51: undefined reference
to `movit::generate_vbo(int, unsigned int, long, void const*)'
/usr/bin/ld: ./obj-mipsel-linux-gnu/../nageru/timecode_renderer.cpp:51:
undefined reference to `movit::generate_vbo(int, unsigned int, long, void
const*)'
/usr/bin/ld: libcore.a(nageru_chroma_subsampler.cpp.o): in function
`ChromaSubsampler::ChromaSubsampler(movit::ResourcePool*)':
./obj-mipsel-linux-gnu/../nageru/chroma_subsampler.cpp:121: undefined
reference to `movit::generate_vbo(int, unsigned int, long, void const*)'
/usr/bin/ld: ./obj-mipsel-linux-gnu/../nageru/chroma_subsampler.cpp:121:
undefined reference to `movit::generate_vbo(int, unsigned int, long, void
const*)'
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.

Looks like further investigations are needed.

-- 
Regards,
Boyuan Yang


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

Bug#936296: marked as done (cherrypy3: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jan 2020 05:34:27 +
with message-id 
and subject line Bug#936296: fixed in cherrypy3 8.9.1-6
has caused the Debian Bug report #936296,
regarding cherrypy3: 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.)


-- 
936296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cherrypy3
Version: 8.9.1-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:cherrypy3

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: cherrypy3
Source-Version: 8.9.1-6

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 19 Jan 2020 00:06:12 -0500
Source: cherrypy3
Architecture: source
Version: 8.9.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 936296 941135
Changes:
 cherrypy3 (8.9.1-6) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #936296, #941135
Checksums-Sha1:
 53eee43f8a0aba93dcc727c0ed98d1f462589e1f 2240 cherrypy3_8.9.1-6.dsc
 d4fe7d0902107d60b19df2c3ce4f6770f9186304 12376 cherrypy3_8.9.1-6.debian.tar.xz
 520da03cb5003c411c0bd8b52491b272d31bec2c 7696 
cherrypy3_8.9.1-6_source.buildinfo
Checksums-Sha256:
 1a6f2e515e8e8e84da3785d3fc6b65a30ad1540cfac05beeb0151f2c171a4e56 2240 
cherrypy3_8.9.1-6.dsc
 151ac42f04110a379e2a03f1bd9bec39df9aea66390ab1f572ef93737e0c142d 12376 
cherrypy3_8.9.1-6.debian.tar.xz
 4ead7255b5642d0108720048142386537224c8c65086590cbcbbaf858c8a69a5 7696 
cherrypy3_8.9.1-6_source.buildin

Bug#938890: marked as done (zinnia: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jan 2020 05:21:54 +
with message-id 
and subject line Bug#938890: fixed in zinnia 0.06-6
has caused the Debian Bug report #938890,
regarding zinnia: 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.)


-- 
938890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:zinnia
Version: 0.06-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:zinnia

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: zinnia
Source-Version: 0.06-6

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

Debian distribution maintenance software
pp.
Changwoo Ryu  (supplier of updated zinnia package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 19 Jan 2020 13:30:29 +0900
Source: zinnia
Architecture: source
Version: 0.06-6
Distribution: unstable
Urgency: high
Maintainer: Debian Input Method Team 
Changed-By: Changwoo Ryu 
Closes: 938890
Changes:
 zinnia (0.06-6) unstable; urgency=high
 .
   * Team upload.
   * Remove BD python-all-dev (Closes: #938890)
Checksums-Sha1:
 7d7b8ccd738725128bc9692cd731d17fa6f423e6 2066 zinnia_0.06-6.dsc
 3fd7223c29ffa484b3a120219623e6e9acc65d64 6084 zinnia_0.06-6.debian.tar.xz
 dbd02ec2fdc0dce5e68963d8eb229efc88c8d556 5410 zinnia_0.06-6_source.buildinfo
Checksums-Sha256:
 685eb465f8fbe05dca8a3b1a128266ae030a81cd2ae2346b57dfc330bd1b387d 2066 
zinnia_0.06-6.dsc
 6483d6c07a74f96a14615ce84d5cdb8d95c792726c49fd94b2bf6d39dfb4713c 6084 
zinnia_0.06-6.debian.tar.xz
 2f7da8c509d866bcb1a86084d6170963ecb29d6b7ea044cbee5c86a64b1c7557 5410 
zinnia_0.06-6_source.buildinfo
Files:
 1c638d56453d665daa7bc7b856871367 2066 libs optional zinnia_0.06-6.dsc
 c629c0e89a1d36c1b640d88264ce3de0 6084 libs optional zi

Processed: Bug#936296 marked as pending in cherrypy3

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #936296 [src:cherrypy3] cherrypy3: Python2 removal in sid/bullseye
Added tag(s) pending.

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

Bug#936296: marked as pending in cherrypy3

[Sandro Tosi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/cherrypy3/commit/2e9b43bbe89aa94f19c304dd1b7ae7d37196e303


Drop python2 support; Closes: #936296, #941135


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/936296

Processed: py2removal blocks updates - 2020-01-19 04:04:21.259590+00:00

[Debian Bug Tracking System]

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
> # adios
> block 936108 by 935927
Bug #936108 [src:adios] adios: Python2 removal in sid/bullseye
936108 was not blocked by any bugs.
936108 was not blocking any bugs.
Added blocking bug(s) of 936108: 935927
> # bkchem
> block 936212 by 935927
Bug #936212 [src:bkchem] bkchem: Python2 removal in sid/bullseye
936212 was blocked by: 945634
936212 was blocking: 937290 937397 937695 938036
Added blocking bug(s) of 936212: 935927
> # cherrypy3
> block 936296 by 937049 942938
Bug #936296 [src:cherrypy3] cherrypy3: Python2 removal in sid/bullseye
936296 was not blocked by any bugs.
936296 was not blocking any bugs.
Added blocking bug(s) of 936296: 942938 and 937049
> # geneagrapher
> block 936596 by 935927
Bug #936596 [src:geneagrapher] geneagrapher: Python2 removal in sid/bullseye
936596 was not blocked by any bugs.
936596 was blocking: 936196 936973 937695 938168
Added blocking bug(s) of 936596: 935927
> # gpsd
> block 936645 by 935927
Bug #936645 [src:gpsd] gpsd: Python2 removal in sid/bullseye
936645 was blocked by: 936318
936645 was blocking: 937695
Added blocking bug(s) of 936645: 935927
> # ipython-py2
> block 936743 by 935927
Bug #936743 [ipython-py2] ipython: Python2 removal in sid/bullseye
936743 was blocked by: 938613 947298 938582 937330 942973 943169 938261 936745 
936996 938444 936995 936772 937116 938581 938327 937117 936775 936739 947297 
936742 937144 937571 938428 939014 938348 937403 937942 938439 937250 938471 
936774 937177 937681 936661 937551 938859
936743 was blocking: 936744 936995 937156 937275 937286 937326 937446 937600 
937694 937695 938004 938168 938483 938716 947298 947302
Added blocking bug(s) of 936743: 935927
> # nautilus-python
> block 937115 by 938575
Bug #937115 [src:nautilus-python] nautilus-python: Python2 removal in 
sid/bullseye
937115 was blocked by: 942773 945651 938614 942775 943137 942771 942779 942781 
942778 936539 942777 948846 945718 937114 938327 945712 943234 942770 947300 
942776 942774 945706 942772 942769
937115 was blocking: 937448 937569 937695 943104
Added blocking bug(s) of 937115: 938575
> # nose
> block 937156 by 936296 938547 937396 936782
Bug #937156 [src:nose] nose: Python2 removal in sid/bullseye
937156 was blocked by: 936560 938407 937836 938283 938753 938618 938661 937950 
936870 936745 937236 937720 937253 936110 937293 938845 942973 937053 937426 
938249 937762 943199 938002 937182 938236 937657 937404 938202 938862 938336 
937415 938458 937250 936503 938625 936820 938244 937491 936744 937944 938370 
937675 937609 937252 938651 938523 937605 937617 936934 938848 937681 937263 
936474 937688 945714 937939 936120 936424 937710 937485 937082 938408 938810 
938310 937903 938022 937489 942992 943158 938863 936282 935450 937145 937952 
938209 937888 936821 938444 937291 936637 937914 937064 938009 938155 938719 
936304 936926 937998 936473 936219 937577 937851 937143 934852 938256 938871 
938663 938305 938166 937088 937758 936154 938177 937764 947730 936501 936398 
937256 936585 937159 938568 938116 937271 936561 937140 938278 936742 938648 
938307 938386 937516 942978 936217 947298 937168 937318 938716 938068 936774 
936285 936528 937224 938211 938727 937897 937446 936932 937119 938840 937768 
938229 942966 938515 934870 937558 938008 937787 947297 938653 936995 936569 
937725 938277 936743 938188 937117 937680 938301 937811 937439 936797 942943 
937232 937757 936806 936578 938261 937255 936196 936825 937114 936775 937808
937156 was blocking: 937665 937695 938168 938528
Added blocking bug(s) of 937156: 938547, 937396, 936296, and 936782
> # openvswitch
> block 937216 by 937051
Bug #937216 [src:openvswitch] openvswitch: Python2 removal in sid/bullseye
937216 was not blocked by any bugs.
937216 was not blocking any bugs.
Added blocking bug(s) of 937216: 937051
> # pdb2pqr
> block 937262 by 935927
Bug #937262 [src:pdb2pqr] pdb2pqr: Python2 removal in sid/bullseye
937262 was blocked by: 945659 937026
937262 was blocking: 932679 937569 937695 937944 937960
Added blocking bug(s) of 937262: 935927
> # pyasn1
> block 937386 by 937122
Bug #937386 [src:pyasn1] pyasn1: Python2 removal in sid/bullseye
937386 was blocked by: 938164 937880 938236 936730 938094 936790 938622 938731 
937238 938055
937386 was blocking: 937695 938168
Added blocking bug(s) of 937386: 937122
> # pygobject
> block 937448 by 943104 939102
Bug #937448 [src:pygobject] pygobject: Python2 removal in sid/bullseye
937448 was blocked by: 943291 943294 943230 926244 943110 937447 937688 943186 
937419 938584 936995 937703 937181 938623 936833 935358 938637 942988 937388 
943216 938329 938593 938582 939106 938590 943300 938293 936632 945863 936601 
938803 936531 937405 938604 945674 939112 938160 943252 943245 936265 945718 
943117 943108 938837 936173 

Processed: py2removal bugs severity updates - 2020-01-19 04:04:21.341230+00:00

[Debian Bug Tracking System]

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
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # not all bin pkgs are leaf for src:fs-uae, lower severity
> severity 936566 normal
Bug #936566 [src:fs-uae] fs-uae: Python2 removal in sid/bullseye
Severity set to 'normal' from 'serious'
> # not all bin pkgs are leaf for src:pygobject, lower severity
> severity 943104 normal
Bug #943104 [src:pygobject] lightdm-gtk-greeter-settings: Python2 removal in 
sid/bullseye
Severity set to 'normal' from 'serious'
> # science-engineering is an application, has low popcon (216 < 300), and has 
> 0 external rdeps or not in testing
> severity 935927 serious
Bug #935927 [src:debian-science] debian-science: migrate all python 
dependencies to their python3 variant
Severity set to 'serious' from 'important'
> # python-cherrypy3 is a module and has 0 external rdeps or not in testing
> severity 936296 serious
Bug #936296 [src:cherrypy3] cherrypy3: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-ecasound is a module and has 0 external rdeps or not in testing
> severity 936463 serious
Bug #936463 [src:ecasound] ecasound: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # kopano-utils is an application, has low popcon (28 < 300), and has 0 
> external rdeps or not in testing
> severity 936808 serious
Bug #936808 [src:kopanocore] kopanocore: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python3-ns3 is an application, has low popcon (2 < 300), and has 0 external 
> rdeps or not in testing
> severity 937163 serious
Bug #937163 [src:ns3] ns3: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # pwman3 is an application, has low popcon (53 < 300), and has 0 external 
> rdeps or not in testing
> severity 937381 serious
Bug #937381 [src:pwman3] pwman3: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-yubico is a module and has 0 external rdeps or not in testing
> # python-yubico-tools is a module and has 0 external rdeps or not in testing
> severity 938283 serious
Bug #938283 [src:python-yubico] python-yubico: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # subliminal-nautilus is an application, has low popcon (31 < 300), and has 0 
> external rdeps or not in testing
> severity 938575 serious
Bug #938575 [src:subliminal] subliminal: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # libufo-bin is an application, has low popcon (5 < 300), and has 0 external 
> rdeps or not in testing
> severity 938743 serious
Bug #938743 [src:ufo-core] ufo-core: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # cycle is an application, has low popcon (64 < 300), and has 0 external 
> rdeps or not in testing
> severity 939181 serious
Bug #939181 [src:cycle] cycle: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # pinot is an application, has low popcon (8 < 300), and has 0 external rdeps 
> or not in testing
> severity 945722 serious
Bug #945722 [src:pinot] pinot: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
935927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935927
936296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936296
936463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936463
936566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936566
936808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936808
937163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937163
937381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937381
938283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938283
938575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938575
938743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938743
939181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939181
943104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943104
945722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#937214: openturns: Python2 removal in sid/bullseye - reopen 937214

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(binary:openturns-examples)Depends->python

Re-opening, so that they can be taken care of.

Processed: openturns: Python2 removal in sid/bullseye - reopen 937214

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #937214 {Done: Sandro Tosi } [src:openturns] openturns: 
Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions openturns/1.14-1.

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

Bug#946648: marked as done (crashes within a few minutes)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jan 2020 03:11:28 +
with message-id 
and subject line Bug#945920: fixed in chromium 79.0.3945.130-1
has caused the Debian Bug report #945920,
regarding crashes within a few minutes
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.)


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

Too bad.
It was good while it lasted.
But this new version today... within a few minutes...

Received signal 11 SEGV_MAPERR 
#22 0x564ff676a0c6 
#23 0x564ff3c983e5 ChromeMain
#24 0x7f94706cfbbb __libc_start_main
#25 0x564ff3c9822a _start

Well this time I'll just sit back and hope somebody else will find the problem.
(Hard to reproduce, even if doing gdb stuff.)
Happened while browsing Facebook.
With the previous version I could browse Facebook for a whole month, no problem.
--- End Message ---
--- Begin Message ---
Source: chromium
Source-Version: 79.0.3945.130-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 18 Jan 2020 20:26:26 +
Source: chromium
Architecture: source
Version: 79.0.3945.130-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Chromium Team 
Changed-By: Michael Gilbert 
Closes: 945920
Changes:
 chromium (79.0.3945.130-1) unstable; urgency=medium
 .
   * New upstream security release.
 - CVE-2020-6377: Use after free in audio. Reported by Zhe Jin
 - CVE-2020-6378: Use-after-free in speech recognizer. Reported by Antti
   Levomäki and Christian Jalio
 - CVE-2020-6379: Use-after-free in speech recognizer. Reported by Guang
   Gong
 - CVE-2020-6380: Extension message verification error. Reported by Sergei
   Glazunov
 - CVE-2019-13767: Use after free in media picker. Reported by Sergei
   Glazunov
   * Fix memory instrumentation singleton initialization errors caused by
 tracing patch included in the previous upload (closes: #945920).
Checksums-Sha1:
 dd61c1104560c28b5cebb7d42c4ca6452fbbc014 4162 chromium_79.0.3945.130-1.dsc
 cab2484a4586d743ca9a6fd8507403cc710705d3 266756640 
chromium_79.0.3945.130.orig.tar.xz
 c450c2ad615334a3c77acc9fb519420f767b29f4 189208 
chromium_79.0.3945.130-1.debian.tar.xz
 2e5cf021e4798a9a2ac23ce589ef8e37d772efce 20666 
chromium_79.0.3945.130-1_source.buildinfo
Checksums-Sha256:
 f939b337d2aba54218ab7653d6e368104e93077b05ae3742422f5a7ca7029288 4162 
chromium_79.0.3945.130-1.dsc
 73d982161090d2c2af26f547cc6a8e1ef935a87d4d193789ced8c6ef07cf7a8d 266756640 
chromium_79.0.3945.130.orig.tar.xz
 59428d97e67764d6d874f6d2b7655918abf1c9e61d24b5a3389764f2956107d9 189208 
chromium_79.0.3945.130-1.debian.tar.xz
 b9e6d6c9e7bcbd62903965165c52e5dbd795ef8697a5ea92d401ae75dd7117d6 20666 
chromium_79.0.3945.130-1_source.buildinfo
Files:
 dfd9277f40854f207c64f7df0ac5b68a 4162 web optional chromium_79.0.3945.130-1.dsc
 b085e08af49bd9e9de7eef43e4d45886 266756640 web optional 
chromium_79.0.3945.130.orig.tar.xz
 97bd816b296f2eb1455a78a2b44d045d 189208 web optional 
chromium_79.0.3945.130-1.debian.tar.xz
 20461a76401001114c9dfddb03e4e47f 20666 web optional 
chromium_79.0.3945.130-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQQzBAEBCgAdFiEEIwTlZiOEpzUxIyp4mD40ZYkUaygFAl4jvjEACgkQmD40ZYkU
ayhn6h//T/0rN+debIvm6Livm6HxHzKROAEfadDc/gC2Ye5GxcSZ1LT6FCMn90m8
folcSFbLPVUQkOMv2qwHm6pfJ09nGMJEBx/gkmlX4jrYsZRb9z8NHtssevD7rZgz
pERpveYQnMVfz1xiijRNdy/iFGk2xEnJiBAQiOWCOP4JAL4okLZHkCxPwjlOXcQ0
g2q5bR7G1xcRMjE3wAs3LGT6Fx7eNfquo5uVjkyTe37pvG7zKr756xTn7i/07Goz
kOlfTmIbsCMh4vrim6i3rrj2I3eTCRFMJb8U/RiLThDRoZNkkL0uPAWmGMSR4voz
JowaTzDEAk19aZB295V9Z98U4/lyUpuoEyr+F8hr/myDygLe8ZOFqEU/x5//l9F3
LoDVCZFvC7+2UsmuzMGeBt7dAT7s9/WIKoGtA0HrTBa8ARrsur18sy0c6dqawVbE
y4EMnSLt1x0ubQuiF11sRc8hLyMKFooKPzpWnjvANYGLl0lwvchMSkWL0AAjWptt
686IdONzBEYxGbcdM2DchXxjJbzggUIuDKz5C2rNRV2WoKlUL5miax

Bug#945920: marked as done (Chromium randomly crashes in the latest version.)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jan 2020 03:11:28 +
with message-id 
and subject line Bug#945920: fixed in chromium 79.0.3945.130-1
has caused the Debian Bug report #945920,
regarding Chromium randomly crashes in the latest version.
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.)


-- 
945920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945920
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: chromium
Version: 79.0.3945.56-1
Severity: important

After updating to the latest version, Chromium randomly crashes after a while.
There are no error messages. It happens randomly and just abruptly quits.
There is no "dmesg" messages generated.
I used a temporary profile and it will still happen.

Stack trace:

Received signal 11 SEGV_MAPERR 
#0 0x5653d1480469 
#1 0x5653d13c9a76 
#2 0x5653d147ec63 
#3 0x5653d14803e6 
#4 0x7ffa7263b510 
#5 0x5653d27ed107 
#6 0x5653d0ffd850 
#7 0x5653d0ff5922 
#8 0x5653d1424b35 
#9 0x5653d143403b 
#10 0x5653d14359bc 
#11 0x5653d13e649a 
#12 0x7ffa7171bf3d g_main_context_dispatch
#13 0x7ffa7171c1c0 
#14 0x7ffa7171c24f g_main_context_iteration
#15 0x5653d13e67a0 
#16 0x5653d1435c79 
#17 0x5653d1411cca 
#18 0x5653d0f17cb7 
#19 0x5653cf23d046 
#20 0x5653cf23d1f5 
#21 0x5653cf213477 
#22 0x5653d0e9fba1 
#23 0x5653d0e9fdd8 
#24 0x5653d0ea0147 
#25 0x5653d0ed62a2 
#26 0x5653d0e9db66 
#27 0x5653ce3cc425 ChromeMain
#28 0x7ffa6bae __libc_start_main
#29 0x5653ce3cc26a _start
  r8: 5653dc28af00  r9: 0001 r10: 5653da8dd010 r11: 
7ffa6bc7ec40
 r12: 7ffcf239ae50 r13: 7ffcf239ae30 r14: 7ffcf239ae50 r15: 
5653dc3ae940
  di:   si: 7ffcf239ae30  bp: 7ffcf239adf0  bx: 

  dx: 7ffcf239ae50  ax: 7ff9dc002810  cx: 5653dc45bb20  sp: 
7ffcf239adb0
  ip: 5653d27ed107 efl: 00010202 cgf: 002b0033 erf: 
0004
 trp: 000e msk:  cr2: 
[end of stack trace]
Calling _exit(1). Core file will not be generated.
--
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBcBAEBCAAGBQJd4ySwAAoJENi1YDlFXXQfDFEH/1VzTV+JyJ7ody7FMorh
dSJ+l60HtPNxDrxRCgGydNzJzJHu47FPHqgiwetNeXgNJGEULiyr/XPk0JLQ
6bliAMCjdFJvIth0hBsINPRZK+Oh5f+gUiF1M1CDikwL7CGxc34zeCODscJ2
kTakc5ikZdFMlHg6UnizY+qX0VyETUGEtZb0FwoGUC9UOrJWJTUBHQnK6Umv
jweGFoypgZWyqp9UOsgLeAfWf3OEWMKYOGH1TtasjS7WSIbvd+OncxAYiC9+
0AY7e/TxRqD/h7GxK0DO5CLCWkG6ulvsHyG5hCohYetboluZehXy30aq4REF
tkc6gKGNto1EoWMdcvb1A2A=
=j/ZR
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: chromium
Source-Version: 79.0.3945.130-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 18 Jan 2020 20:26:26 +
Source: chromium
Architecture: source
Version: 79.0.3945.130-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Chromium Team 
Changed-By: Michael Gilbert 
Closes: 945920
Changes:
 chromium (79.0.3945.130-1) unstable; urgency=medium
 .
   * New upstream security release.
 - CVE-2020-6377: Use after free in audio. Reported by Zhe Jin
 - CVE-2020-6378: Use-after-free in speech recognizer. Reported by Antti
   Levomäki and Christian Jalio
 - CVE-2020-6379: Use-after-free in speech recognizer. Reported by Guang
   Gong
 - CVE-2020-6380: Extension message verification error. Reported by Sergei
   Glazunov
 - CVE-2019-13767: Use after free in media picker. Reported by Sergei
   Glazunov
   * Fix memory instrumentation singleton initialization errors caused by
 tracing patch included in the previous upload (

Bug#943259: vim-autopep8: Python2 removal in sid/bullseye - reopen 943259

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:vim-autopep8)Build-Depends->python-sphinx

Re-opening, so that they can be taken care of.

Processed: vim-autopep8: Python2 removal in sid/bullseye - reopen 943259

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #943259 {Done: Sylvestre Ledru } [src:vim-autopep8] 
vim-autopep8: Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions vim-autopep8/1.0.7-2.

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

Processed: python-pattern: Python2 removal in sid/bullseye - reopen 938006

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #938006 {Done: Miriam Ruiz } [src:python-pattern] 
python-pattern: Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions python-pattern/2.6+git20180818-1.

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

Bug#938890: zinnia: Python2 removal in sid/bullseye - reopen 938890

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:zinnia)Build-Depends->python-all-dev

Re-opening, so that they can be taken care of.

Bug#937169: nut: Python2 removal in sid/bullseye - reopen 937169

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:nut)Testsuite-Triggers->python

Re-opening, so that they can be taken care of.

Bug#943104: pygobject: Python2 removal in sid/bullseye - reopen 943104

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:pygobject)Build-Depends->python-all-dbg
(source:pygobject)Build-Depends->python-all-dev
(source:pygobject)Build-Depends->python-cairo-dbg
(source:pygobject)Build-Depends->python-cairo-dev
(source:pygobject)Build-Depends->python-pytest
(source:pygobject)Build-Depends->python-setuptools
(source:pygobject)Testsuite-Triggers->python2-dev
(binary:python-gi)Depends->python2
(binary:python-gi)Depends->python2
(binary:python-gi)Depends->python2:any
(binary:python-gi)Depends->python2:any
(binary:python-gi-cairo)Depends->python-cairo
(binary:python-gi-cairo)Depends->python-gi
(binary:python-gi-cairo)Depends->python2
(binary:python-gi-cairo)Depends->python2
(binary:python-gi-cairo)Depends->python2:any
(binary:python-gi-cairo)Depends->python2:any
(binary:python-gi-dbg)Depends->python-gi
(binary:python-gi-dbg)Depends->python2-dbg
(binary:python-gi-dbg)Depends->python2-dbg
(binary:python-gi-dbg)Depends->python2-dbg:any
(binary:python-gi-dbg)Depends->python2-dbg:any
(binary:python-gi-dev)Depends->python-gi

Re-opening, so that they can be taken care of.

Processed: libreoffice-dictionaries: Python2 removal in sid/bullseye - reopen 943096

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #943096 {Done: Rene Engelhard } 
[src:libreoffice-dictionaries] libreoffice-dictionaries: Python2 removal in 
sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libreoffice-dictionaries/1:6.3.3-1.

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

Processed: pygobject: Python2 removal in sid/bullseye - reopen 943104

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #943104 {Done: Andreas Henriksson } [src:pygobject] 
lightdm-gtk-greeter-settings: Python2 removal in sid/bullseye
Bug reopened
Ignoring request to alter fixed versions of bug #943104 to the same values 
previously set

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

Processed: nut: Python2 removal in sid/bullseye - reopen 937169

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #937169 {Done: Laurent Bigonville } [src:nut] nut: 
Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions nut/2.7.4-11.

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

Bug#938006: python-pattern: Python2 removal in sid/bullseye - reopen 938006

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:python-pattern)Build-Depends->python2-minimal

Re-opening, so that they can be taken care of.

Processed: zinnia: Python2 removal in sid/bullseye - reopen 938890

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #938890 {Done: Changwoo Ryu } [src:zinnia] zinnia: 
Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions zinnia/0.06-5.

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

Bug#943096: libreoffice-dictionaries: Python2 removal in sid/bullseye - reopen 943096

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(binary:libreoffice-lightproof-pt-br)Depends->python-uno

Re-opening, so that they can be taken care of.

Processed: decoratortools: Python2 removal in sid/bullseye - reopen 942943

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #942943 {Done: Debian FTP Masters } 
[src:decoratortools] decoratortools: Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.8-4+rm.

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

Bug#938459: seafile: Python2 removal in sid/bullseye - reopen 938459

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(binary:seafile-cli)Depends->python:any

Re-opening, so that they can be taken care of.

Processed: vim-autopep8: Python2 removal in sid/bullseye - unarchive 943259

[Debian Bug Tracking System]

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

> unarchive 943259
Bug #943259 {Done: Sylvestre Ledru } [src:vim-autopep8] 
vim-autopep8: Python2 removal in sid/bullseye
Unarchived Bug 943259
>
End of message, stopping processing here.

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

Processed: pygobject: Python2 removal in sid/bullseye - unarchive 943104

[Debian Bug Tracking System]

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

> unarchive 943104
Bug #943104 {Done: Andreas Henriksson } [src:pygobject] 
lightdm-gtk-greeter-settings: Python2 removal in sid/bullseye
Unarchived Bug 943104
>
End of message, stopping processing here.

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

Processed: python-socksipychain: Python2 removal in sid/bullseye - reopen 938184

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #938184 {Done: Federico Ceratto } 
[src:python-socksipychain] python-socksipychain: Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions python-socksipychain/2.1.0-1.

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

Processed: python-pyknon: Python2 removal in sid/bullseye - reopen 938072

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #938072 {Done: Stuart Prescott } [src:python-pyknon] 
python-pyknon: Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions python-pyknon/1.2-2.

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

Processed: libreoffice-dictionaries: Python2 removal in sid/bullseye - unarchive 943096

[Debian Bug Tracking System]

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

> unarchive 943096
Bug #943096 {Done: Rene Engelhard } 
[src:libreoffice-dictionaries] libreoffice-dictionaries: Python2 removal in 
sid/bullseye
Unarchived Bug 943096
>
End of message, stopping processing here.

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

Processed: python-pattern: Python2 removal in sid/bullseye - unarchive 938006

[Debian Bug Tracking System]

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

> unarchive 938006
Bug #938006 {Done: Miriam Ruiz } [src:python-pattern] 
python-pattern: Python2 removal in sid/bullseye
Unarchived Bug 938006
>
End of message, stopping processing here.

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

Bug#937941: python-neovim: Python2 removal in sid/bullseye - reopen 937941

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:python-neovim)Build-Depends->python-all
(source:python-neovim)Build-Depends->python-setuptools
(source:python-neovim)Build-Depends->python-msgpack
(source:python-neovim)Build-Depends->python-greenlet
(source:python-neovim)Build-Depends->cython
(source:python-neovim)Build-Depends->python-trollius
(source:python-neovim)Build-Depends->python-pytest
(source:python-neovim)Testsuite-Triggers->python-pytest
(binary:python-neovim)Depends->python-greenlet
(binary:python-neovim)Depends->python-msgpack
(binary:python-neovim)Depends->python-trollius
(binary:python-neovim)Depends->python:any
(binary:python-neovim)Depends->python:any

Re-opening, so that they can be taken care of.

Processed: nut: Python2 removal in sid/bullseye - unarchive 937169

[Debian Bug Tracking System]

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

> unarchive 937169
Bug #937169 {Done: Laurent Bigonville } [src:nut] nut: 
Python2 removal in sid/bullseye
Unarchived Bug 937169
>
End of message, stopping processing here.

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

Bug#936924: libsvm: Python2 removal in sid/bullseye - reopen 936924

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(binary:libsvm-tools)Depends->python:any

Re-opening, so that they can be taken care of.

Bug#938184: python-socksipychain: Python2 removal in sid/bullseye - reopen 938184

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:python-socksipychain)Testsuite-Triggers->python-all

Re-opening, so that they can be taken care of.

Bug#938072: python-pyknon: Python2 removal in sid/bullseye - reopen 938072

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:python-pyknon)Build-Depends->python-all-dev
(source:python-pyknon)Build-Depends->python-sphinx
(source:python-pyknon)Build-Depends->python-pytest
(binary:python-pyknon)Depends->python
(binary:python-pyknon)Depends->python
(binary:python-pyknon)Depends->python:any

Re-opening, so that they can be taken care of.

Bug#942943: decoratortools: Python2 removal in sid/bullseye - reopen 942943

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:decoratortools)Build-Depends->python-all
(source:decoratortools)Build-Depends->python-nose
(source:decoratortools)Build-Depends->python-setuptools
(binary:python-peak.util.decorators)Depends->python:any
(binary:python-peak.util.decorators)Depends->python:any

Re-opening, so that they can be taken care of.

Processed: zinnia: Python2 removal in sid/bullseye - unarchive 938890

[Debian Bug Tracking System]

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

> unarchive 938890
Bug #938890 {Done: Changwoo Ryu } [src:zinnia] zinnia: 
Python2 removal in sid/bullseye
Unarchived Bug 938890
>
End of message, stopping processing here.

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

Processed: seafile: Python2 removal in sid/bullseye - reopen 938459

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #938459 {Done: Moritz Schlarb } [src:seafile] 
seafile: Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 7.0.4-1.

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

Processed: fs-uae: Python2 removal in sid/bullseye - reopen 936566

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #936566 {Done: John Paul Adrian Glaubitz } 
[src:fs-uae] fs-uae: Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions fs-uae/3.0.2+dfsg-1.

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

Bug#936723: ifeffit: Python2 removal in sid/bullseye - reopen 936723

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:ifeffit)Build-Depends->python-all-dev
(binary:python-ifeffit)Depends->python
(binary:python-ifeffit)Depends->python
(binary:python-ifeffit)Depends->python:any
(binary:python-ifeffit)Depends->python-pmw
(binary:python-ifeffit)Depends->python-tk

Re-opening, so that they can be taken care of.

Processed: python-neovim: Python2 removal in sid/bullseye - reopen 937941

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #937941 {Done: James McCoy } [src:python-neovim] 
python-neovim: Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions python-pynvim/0.4.0-1.

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

Processed: ifeffit: Python2 removal in sid/bullseye - reopen 936723

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #936723 {Done: Debian FTP Masters } 
[src:ifeffit] ifeffit: Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 2:1.2.11d-10.2+rm.

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

Processed: ipe-tools: Python2 removal in sid/bullseye - reopen 936740

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #936740 {Done: s...@debian.org (Steve M. Robbins)} [src:ipe-tools] 
ipe-tools: Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions ipe-tools/1:7.2.7.2-2.

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

Bug#936740: ipe-tools: Python2 removal in sid/bullseye - reopen 936740

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:ipe-tools)Build-Depends->python
(binary:svgtoipe)Depends->python
(binary:svgtoipe)Depends->python:any
(binary:svgtoipe)Recommends->python-pil

Re-opening, so that they can be taken care of.

Bug#936566: fs-uae: Python2 removal in sid/bullseye - reopen 936566

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(binary:fs-uae-arcade)Recommends->python-lhafile

Re-opening, so that they can be taken care of.

Processed: libsvm: Python2 removal in sid/bullseye - reopen 936924

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #936924 {Done: Christian Kastner } [src:libsvm] libsvm: 
Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libsvm/3.24+ds-1.

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

Processed: ffrenzy: Python2 removal in sid/bullseye - reopen 936513

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #936513 {Done: Debian FTP Masters } 
[src:ffrenzy] ffrenzy: Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.0.2~svn20150731-1+rm.

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

Bug#936513: ffrenzy: Python2 removal in sid/bullseye - reopen 936513

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:ffrenzy)Build-Depends->python
(binary:ffrenzy)Depends->python:any
(binary:ffrenzy)Depends->python-gtk2
(binary:ffrenzy)Depends->python-glade2
(binary:ffrenzy)Depends->python-pygame

Re-opening, so that they can be taken care of.

Processed: crudini: Python2 removal in sid/bullseye - reopen 942976

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #942976 {Done: Andrej Shadura } [src:crudini] crudini: 
Python2 removal in sid/bullseye
Bug #936346 {Done: Andrej Shadura } [src:crudini] crudini: 
Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions crudini/0.9.3-1.
No longer marked as fixed in versions crudini/0.9.3-1.

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

Bug#942976: crudini: Python2 removal in sid/bullseye - reopen 942976

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(binary:crudini)Depends->python:any

Re-opening, so that they can be taken care of.

Processed: citeproc-py: Python2 removal in sid/bullseye - reopen 936305

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #936305 {Done: Dimitri John Ledkov } [src:citeproc-py] 
citeproc-py: Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions citeproc-py/0.3.0-4.

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

Bug#936282: ceph: Python2 removal in sid/bullseye - reopen 936282

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:ceph)Build-Depends->cython

Re-opening, so that they can be taken care of.

Processed: claws-mail: Python2 removal in sid/bullseye - reopen 936307

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #936307 {Done: Ricardo Mones } [src:claws-mail] 
claws-mail: Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions claws-mail/3.17.4-2.

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

Processed: ceph: Python2 removal in sid/bullseye - reopen 936282

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #936282 {Done: Bernd Zeimetz } [src:ceph] ceph: Python2 
removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions ceph/14.2.4-1.

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

Bug#936305: citeproc-py: Python2 removal in sid/bullseye - reopen 936305

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:citeproc-py)Testsuite-Triggers->python-all
(source:citeproc-py)Testsuite-Triggers->python-lxml
(source:citeproc-py)Testsuite-Triggers->python-pytest

Re-opening, so that they can be taken care of.

Bug#942975: conque: Python2 removal in sid/bullseye - reopen 942975

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:conque)Build-Depends->python
(binary:vim-conque)Depends->python

Re-opening, so that they can be taken care of.

Bug#936307: claws-mail: Python2 removal in sid/bullseye - reopen 936307

[Sandro Tosi]

Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(binary:claws-mail-tools)Depends->python

Re-opening, so that they can be taken care of.

Processed: conque: Python2 removal in sid/bullseye - reopen 942975

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #942975 {Done: Debian FTP Masters } 
[src:conque] conque: Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 2.3-1+rm.

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

Bug#949257: xserver-xorg-core: Segmentation fault w/ 1.20.7

[Jamie Heilman]

Package: xserver-xorg-core
Version: 2:1.20.7-2
Severity: grave

Setup is a NVIDIA GF108GL [Quadro 600] driving two monitors in
portrait orientation.  Kernel 5.4.0-2-amd64 #1 SMP Debian 5.4.8-1 (2020-01-05)

xorg.conf is:
Section "Device"
 Identifier "GF108GL"
 Driver "nouveau"
 Option "Monitor-DVI-I-1" "Left Dell U2312HM"
 Option "Monitor-DP-1" "Right Dell U2312HM"
EndSection

Section "Monitor"
 Identifier "Left Dell U2312HM"
 Option "Rotate" "right"
EndSection

Section "Monitor"
 Identifier "Right Dell U2312HM"
 Option "RightOf" "Left Dell U2312HM"
 Option "Rotate" "right"
EndSection


Crash is consistent, and goes away once downgraded to 1.20.6, other
relevant package versions:

libdrm-nouveau2:amd64   2.4.100-4
xdm 1:1.1.11-3+b1
xserver-xorg-video-nouveau  1:1.0.16-1

Crash:

[   590.914] (II) NOUVEAU(0): NVEnterVT is called.
[   590.914] (EE) 
[   590.914] (EE) Backtrace:
[   590.914] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x138) [0x5618c21dfeb8]
[   590.915] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) 
[0x7f574e2d956f]
[   590.915] (EE) 2: /usr/lib/xorg/Xorg (DamageRegister+0x1d) [0x5618c2160abd]
[   590.915] (EE) 3: /usr/lib/xorg/Xorg (xf86RandR12PreInit+0x3c1) 
[0x5618c20fef31]
[   590.915] (EE) 4: /usr/lib/xorg/Xorg (xf86CrtcRotate+0x321) [0x5618c20ff5d1]
[   590.915] (EE) unw_get_proc_name failed: no unwind info found [-10]
[   590.915] (EE) 5: /usr/lib/xorg/modules/drivers/nouveau_drv.so (?+0x0) 
[0x7f574d8ccf30]
[   590.915] (EE) 6: /usr/lib/xorg/Xorg (xf86CrtcSetModeTransform+0x280) 
[0x5618c20f5330]
[   590.915] (EE) 7: /usr/lib/xorg/Xorg (xf86SetDesiredModes+0xea) 
[0x5618c20f587a]
[   590.915] (EE) unw_get_proc_name failed: no unwind info found [-10]
[   590.915] (EE) 8: /usr/lib/xorg/modules/drivers/nouveau_drv.so (?+0x0) 
[0x7f574d8b5f90]
[   590.916] (EE) unw_get_proc_name failed: no unwind info found [-10]
[   590.916] (EE) 9: /usr/lib/xorg/modules/drivers/nouveau_drv.so (?+0x0) 
[0x7f574d8b6370]
[   590.916] (EE) 10: /usr/lib/xorg/Xorg (InitExtensions+0x61e) [0x5618c20f0cee]
[   590.916] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x279) [0x5618c20867f9]
[   590.916] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) 
[0x7f574e12abbb]
[   590.916] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x5618c207074a]
[   590.916] (EE) 
[   590.916] (EE) Segmentation fault at address 0x10
[   590.916] (EE) 
Fatal server error:
[   590.916] (EE) Caught signal 11 (Segmentation fault). Server aborting
[   590.916] (EE) 

full Xorg and xdm logs attached; appears to die at the point when the
screen gets resized


-- 
Jamie Heilman http://audible.transient.net/~jamie/
[   590.560] 
X.Org X Server 1.20.7
X Protocol Version 11, Revision 0
[   590.560] Build Operating System: Linux 4.19.0-6-amd64 x86_64 Debian
[   590.560] Current Operating System: Linux jamiehe1 5.4.0-2-amd64 #1 SMP 
Debian 5.4.8-1 (2020-01-05) x86_64
[   590.560] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-2-amd64 
root=/dev/mapper/W-root ro cgroup_no_v1=all
[   590.560] Build Date: 14 January 2020  10:13:49AM
[   590.560] xorg-server 2:1.20.7-2 (https://www.debian.org/support) 
[   590.560] Current version of pixman: 0.36.0
[   590.560]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   590.560] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   590.560] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jan 18 23:24:40 
2020
[   590.560] (==) Using config file: "/etc/X11/xorg.conf"
[   590.560] (==) Using config directory: "/etc/X11/xorg.conf.d"
[   590.560] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   590.560] (==) No Layout section.  Using the first Screen section.
[   590.560] (==) No screen section available. Using defaults.
[   590.560] (**) |-->Screen "Default Screen Section" (0)
[   590.560] (**) |   |-->Monitor ""
[   590.560] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[   590.560] (**) |   |-->Device "GF108GL"
[   590.560] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   590.560] (==) Automatically adding devices
[   590.560] (==) Automatically enabling devices
[   590.560] (==) Automatically adding GPU devices
[   590.560] (==) Max clients allowed: 256, resource mask: 0x1f
[   590.560] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   590.560]Entry deleted from font path.
[   590.560] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fon

Bug#936723: marked as done (ifeffit: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 18 Jan 2020 23:53:12 +
with message-id 
and subject line Bug#949123: Removed package(s) from unstable
has caused the Debian Bug report #936723,
regarding ifeffit: 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.)


-- 
936723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ifeffit
Version: 2:1.2.11d-10.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:ifeffit

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: 2:1.2.11d-10.2+rm

Dear submitter,

as the package ifeffit 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/949123

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#948913: marked as done (FTBFS: No rule to make target 'QtWebKit/QWebView', needed by 'ui_report.h'. Stop)

[Debian Bug Tracking System]

Your message dated Sat, 18 Jan 2020 23:54:56 +
with message-id 
and subject line Bug#949200: Removed package(s) from unstable
has caused the Debian Bug report #948913,
regarding FTBFS: No rule to make target 'QtWebKit/QWebView', needed by 
'ui_report.h'.  Stop
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.)


-- 
948913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948913
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sleepyhead
Version: 1.0.0-beta-2+dfsg-7
Severity: serious
Justification: FTBFS: can not complete target

Hi! During a rebuild your package FTBFS:



The error seems to be:

/usr/lib/qt5/bin/uic ../../sleepyhead/mainwindow.ui -o ui_mainwindow.h
/usr/lib/qt5/bin/uic ../../sleepyhead/oximetry.ui -o ui_oximetry.h
/usr/lib/qt5/bin/uic ../../sleepyhead/preferencesdialog.ui -o 
ui_preferencesdialog.h
make[2]: *** No rule to make target 'QtWebKit/QWebView', needed by 
'ui_report.h'.  Stop.
make[2]: *** Waiting for unfinished jobs
make[2]: Leaving directory '/<>/_build/sleepyhead'
make[1]: *** [Makefile:47: sub-sleepyhead-make_first-ordered] Error 2
make[1]: Leaving directory '/<>/_build'
dh_auto_build: cd _build && make -j4 returned exit code 2
make: *** [debian/rules:17: build-arch] Error 255
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


Kinds regards, Lisandro.

-- 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.4.0-2-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 ---
Version: 1.0.0-beta-2+dfsg-7+rm

Dear submitter,

as the package sleepyhead 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/949200

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#947075: marked as done (conque: Should this package be removed?)

[Debian Bug Tracking System]

Your message dated Sat, 18 Jan 2020 23:54:20 +
with message-id 
and subject line Bug#949170: Removed package(s) from unstable
has caused the Debian Bug report #947075,
regarding conque: Should this package be removed?
to be marked as done.

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

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


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

Dear conque maintainer,

The package conque you maintain in Debian is currently affected by
Debian's python2 removal. Since conque seems to be a python2-only
packages, is it reasonable to have it removed from Debian archive?

If you have any thoughts, please let me know ASAP. If there's no
response, I plan to convert this bug report to a removal request to
have this package removed from Debian.

-- 
Regards,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Version: 2.3-1+rm

Dear submitter,

as the package conque 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/949170

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#885279: marked as done (ffrenzy: Depends on unmaintained pygtk)

[Debian Bug Tracking System]

Your message dated Sat, 18 Jan 2020 23:55:29 +
with message-id 
and subject line Bug#949220: Removed package(s) from unstable
has caused the Debian Bug report #885279,
regarding ffrenzy: Depends on unmaintained pygtk
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.)


-- 
885279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885279
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ffrenzy
Version: 1.0.2~svn20150731-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 1.0.2~svn20150731-1+rm

Dear submitter,

as the package ffrenzy 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/949220

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

[Debian Bug Tracking System]

Your message dated Sat, 18 Jan 2020 23:54:20 +
with message-id 
and subject line Bug#949170: Removed package(s) from unstable
has caused the Debian Bug report #942975,
regarding conque: 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.)


-- 
942975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: conque
Version: 2.3-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 (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.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: 2.3-1+rm

Dear submitter,

as the package conque 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/949170

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

[Debian Bug Tracking System]

Your message dated Sat, 18 Jan 2020 23:55:29 +
with message-id 
and subject line Bug#949220: Removed package(s) from unstable
has caused the Debian Bug report #936513,
regarding ffrenzy: 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.)


-- 
936513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ffrenzy
Version: 1.0.2~svn20150731-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:ffrenzy

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.0.2~svn20150731-1+rm

Dear submitter,

as the package ffrenzy 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/949220

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#948555: python-soappy: should this package be removed?

[Scott Kitterman]

On Fri, 10 Jan 2020 00:14:59 -0500 Sandro Tosi  wrote:
> Package: python-soappy
> Version: 0.12.22-1
> Severity: serious
> 
> Hello,
> i believe we should remove python-soappy from Debian:
> 
> * python2-only code base
> * leaf package
> * even upstream suggests to use `suds` instead of this project
> * the relatively high popcon is because reportbug used to depend on this
>   package, but it has migrated to simplesoap/debianbts a long ago.
> 
> if i dont hear back within a week with a good reason to keep this package
> around, i'll file for its removal.

DAK thinks there's an rdepend that needs to be addressed first:

Checking reverse dependencies...
# Broken Depends:
dtc-xen: dtc-xen

Dependency problem found.

Please remove the moreinfo tag once that's been addressed.

Scott K


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

Processed: tagging 948555

[Debian Bug Tracking System]

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

> tags 948555 + moreinfo
Bug #948555 [ftp.debian.org] RM: python-soappy -- RoQA; python2-only; leaf 
package; upstream suggests to use 'suds'; better alternatives exist
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#938269: marked as done (RM: python-wxmpl -- RoQA; dead upstream; unmaintained; low popcon; blocking py2 removal)

[Debian Bug Tracking System]

Your message dated Sat, 18 Jan 2020 23:47:49 +
with message-id 
and subject line Bug#938269: Removed package(s) from unstable
has caused the Debian Bug report #938269,
regarding RM: python-wxmpl -- RoQA; dead upstream; unmaintained; low popcon; 
blocking py2 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.)


-- 
938269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-wxmpl
Version: 2.0.0-2.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:python-wxmpl

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:

python-wxmpl |  2.0.0-2.1 | source, all

--- Reason ---
RoQA; dead upstream; unmaintained; low popcon; blocking py2 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 938...@bugs.debian.org.

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

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 (

Bug#896239: marked as done (python-wxmpl: wxmpl fails to import)

[Debian Bug Tracking System]

Your message dated Sat, 18 Jan 2020 23:47:54 +
with message-id 
and subject line Bug#938269: Removed package(s) from unstable
has caused the Debian Bug report #896239,
regarding python-wxmpl: wxmpl fails to import
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.)


-- 
896239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-wxmpl
Version: 2.0.0-2.1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-wxmpl importing the module wxmpl
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/wxmpl.py", line 25, in 
from matplotlib.axes import _process_plot_var_args
ImportError: cannot import name _process_plot_var_args

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Version: 2.0.0-2.1+rm

Dear submitter,

as the package python-wxmpl 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/938269

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

Processed: tagging 936344

[Debian Bug Tracking System]

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

> tags 936344 + upstream
Bug #936344 [src:crossfire] crossfire: Python2 removal in sid/bullseye
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#942943: marked as done (decoratortools: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 18 Jan 2020 23:49:08 +
with message-id 
and subject line Bug#948541: Removed package(s) from unstable
has caused the Debian Bug report #942943,
regarding decoratortools: 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.)


-- 
942943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942943
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: decoratortools
Version: 1.8-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 (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.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.8-4+rm

Dear submitter,

as the package decoratortools 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/948541

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#938421: marked as done (RM: rurple-ng -- RoQA; dead upstream; unmaintained; low popcon; blocking py2 removal)

[Debian Bug Tracking System]

Your message dated Sat, 18 Jan 2020 23:48:25 +
with message-id 
and subject line Bug#938421: Removed package(s) from unstable
has caused the Debian Bug report #938421,
regarding RM: rurple-ng -- RoQA; dead upstream; unmaintained; low popcon; 
blocking py2 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.)


-- 
938421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rurple-ng
Version: 0.5+16-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:rurple-ng

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:

 rurple-ng |   0.5+16-2 | source, all

--- Reason ---
RoQA; dead upstream; unmaintained; low popcon; blocking py2 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 938...@bugs.debian.org.

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

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 ftpmaste

Bug#948541: marked as done (RM: decoratortools -- RoQA; python2-only; last release in 2010; no upstream development since; leaf pkg)

[Debian Bug Tracking System]

Your message dated Sat, 18 Jan 2020 23:49:03 +
with message-id 
and subject line Bug#948541: Removed package(s) from unstable
has caused the Debian Bug report #948541,
regarding RM: decoratortools -- RoQA; python2-only; last release in 2010; no 
upstream development since; leaf pkg
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.)


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

Hello,
recently python-peak.util was removed, and i believe decoratortools should see
the same destiny: it's a python2-only project with the latest release in 2010
and no upstream development.

If i dont hear back within a week with a good reason to keep it around, i'll
file for its removal.

Regards,
Sandro

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

decoratortools |  1.8-4 | source
python-peak.util.decorators |  1.8-4 | all

--- Reason ---
RoQA; python2-only; last release in 2010; no upstream development since; leaf 
pkg
--

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 948...@bugs.debian.org.

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

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#949140: ffmpeg: FTBFS: ERROR: tesseract not found using pkg-config

[James Cowgill]

Control: reassign -1 libtesseract-dev 4.1.1-1
Control: retitle -1 libtesseract-dev: missing dependency on libarchive-dev
Control: affects -1 src:ffmpeg

Hi,

On 17/01/2020 11:51, Mattia Rizzolo wrote:
> Source: ffmpeg
> Version: 4.2.1-2
> Severity: serious
> Tags: ftbfs
> 
> Dear maintainer,
> 
> your package failed to rebuild in a standard sid/amd64 chroot.
> Attached is the full build log, hopefully relevant excerpt follows:
> 
> ERROR: tesseract not found using pkg-config
> make[1]: *** [debian/rules:225: override_dh_auto_configure] Error 1
> make[1]: Leaving directory '/build/ffmpeg-4.2.1'
> make: *** [debian/rules:220: binary] Error 2
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
> 2

And the few lines before that error are:
> gcc [omitted] -ltesseract -larchive
> /usr/bin/ld: cannot find -larchive
> collect2: error: ld returned 1 exit status
> ERROR: tesseract not found using pkg-config
> make[1]: *** [debian/rules:225: override_dh_auto_configure] Error 1

If I install libtesseract-dev and nothing else, building something
against the libraries in the pkg-config file give the same error:
> $ echo 'int main(void) {}' | gcc -x c - $(pkg-config --cflags --libs 
> tesseract) 
> /usr/bin/ld: cannot find -larchive
> collect2: error: ld returned 1 exit status

So I think this is a bug in tesseract.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#949140: ffmpeg: FTBFS: ERROR: tesseract not found using pkg-config

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libtesseract-dev 4.1.1-1
Bug #949140 [src:ffmpeg] ffmpeg: FTBFS: ERROR: tesseract not found using 
pkg-config
Bug reassigned from package 'src:ffmpeg' to 'libtesseract-dev'.
No longer marked as found in versions ffmpeg/7:4.2.1-2.
Ignoring request to alter fixed versions of bug #949140 to the same values 
previously set
Bug #949140 [libtesseract-dev] ffmpeg: FTBFS: ERROR: tesseract not found using 
pkg-config
Marked as found in versions tesseract/4.1.1-1.
> retitle -1 libtesseract-dev: missing dependency on libarchive-dev
Bug #949140 [libtesseract-dev] ffmpeg: FTBFS: ERROR: tesseract not found using 
pkg-config
Changed Bug title to 'libtesseract-dev: missing dependency on libarchive-dev' 
from 'ffmpeg: FTBFS: ERROR: tesseract not found using pkg-config'.
> affects -1 src:ffmpeg
Bug #949140 [libtesseract-dev] libtesseract-dev: missing dependency on 
libarchive-dev
Added indication that 949140 affects src:ffmpeg

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

Processed: tagging 947111

[Debian Bug Tracking System]

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

> tags 947111 + fixed-upstream
Bug #947111 [src:python-thinc] python-thinc: FTBFS with Python 3.8
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: libolecf: diff for NMU version 20181231-1.1

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#936897: libolecf: diff for NMU version 20181231-1.1

[Adrian Bunk]

Control: tags 936897 + patch
Control: tags 936897 + pending

Dear maintainer,

I've prepared an NMU for libolecf (versioned as 20181231-1.1) and 
uploaded it to DELAYED/15. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru libolecf-20181231/debian/changelog libolecf-20181231/debian/changelog
--- libolecf-20181231/debian/changelog	2019-01-14 03:08:37.0 +0200
+++ libolecf-20181231/debian/changelog	2020-01-19 01:31:09.0 +0200
@@ -1,3 +1,10 @@
+libolecf (20181231-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Remove the Python 2 bindings. (Closes: #936897)
+
+ -- Adrian Bunk   Sun, 19 Jan 2020 01:31:09 +0200
+
 libolecf (20181231-1) unstable; urgency=medium
 
   [ Raphaël Hertzog ]
diff -Nru libolecf-20181231/debian/control libolecf-20181231/debian/control
--- libolecf-20181231/debian/control	2019-01-14 03:03:50.0 +0200
+++ libolecf-20181231/debian/control	2020-01-19 01:31:09.0 +0200
@@ -3,7 +3,7 @@
 Maintainer: Debian Security Tools 
 Uploaders: Hilko Bengen 
 Build-Depends: debhelper (>= 11),
- pkg-config, python-dev, python3-dev, libbfio-dev, libfuse-dev,
+ pkg-config, dh-python, python3-dev, libbfio-dev, libfuse-dev,
 Standards-Version: 4.3.0
 Section: libs
 Homepage: https://github.com/libyal/libolecf
@@ -44,15 +44,6 @@
  This package contains tools to access data stored in OLECF files:
  olecfexport, olecfinfo, lecfmount.
 
-Package: python-libolecf
-Section: python
-Architecture: any
-Depends: libolecf1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}
-Description: OLE2 Compound File format access library -- Python 2 bindings
- libolecf is a library to access the OLE 2 Compound File (OLECF) format.
- .
- This package contains Python 2 bindings for libolecf.
-
 Package: python3-libolecf
 Section: python
 Architecture: any
diff -Nru libolecf-20181231/debian/python-libolecf.install libolecf-20181231/debian/python-libolecf.install
--- libolecf-20181231/debian/python-libolecf.install	2016-08-02 12:13:50.0 +0300
+++ libolecf-20181231/debian/python-libolecf.install	1970-01-01 02:00:00.0 +0200
@@ -1 +0,0 @@
-/usr/lib/python2*
diff -Nru libolecf-20181231/debian/rules libolecf-20181231/debian/rules
--- libolecf-20181231/debian/rules	2019-01-14 03:04:07.0 +0200
+++ libolecf-20181231/debian/rules	2020-01-19 01:31:09.0 +0200
@@ -10,10 +10,10 @@
 export SKIP_PYTHON_TESTS=1
 
 %:
-	dh $@ --with python2,python3
+	dh $@ --with python3 --buildsystem=autoconf
 
 override_dh_auto_configure:
-	dh_auto_configure -- --enable-python2 --enable-python3
+	dh_auto_configure -- --disable-python2 --enable-python3
 
 override_dh_missing:
 	dh_missing -X.la -X/pyolecf.a --fail-missing

Processed: libscca: diff for NMU version 20181227-1.1

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#936915: libscca: diff for NMU version 20181227-1.1

[Adrian Bunk]

Control: tags 936915 + patch
Control: tags 936915 + pending

Dear maintainer,

I've prepared an NMU for libscca (versioned as 20181227-1.1) and 
uploaded it to DELAYED/15. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru libscca-20181227/debian/changelog libscca-20181227/debian/changelog
--- libscca-20181227/debian/changelog	2019-01-14 03:26:38.0 +0200
+++ libscca-20181227/debian/changelog	2020-01-19 01:35:22.0 +0200
@@ -1,3 +1,10 @@
+libscca (20181227-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Remove the Python 2 bindings. (Closes: #936915)
+
+ -- Adrian Bunk   Sun, 19 Jan 2020 01:35:22 +0200
+
 libscca (20181227-1) unstable; urgency=medium
 
   [ Raphaël Hertzog ]
diff -Nru libscca-20181227/debian/control libscca-20181227/debian/control
--- libscca-20181227/debian/control	2019-01-14 03:21:39.0 +0200
+++ libscca-20181227/debian/control	2020-01-19 01:35:22.0 +0200
@@ -5,7 +5,7 @@
 Build-Depends: debhelper (>= 11),
  dh-python,
  pkg-config,
- python-dev, python3-dev, libbfio-dev,
+ python3-dev, libbfio-dev,
 Standards-Version: 4.3.0
 Section: libs
 Homepage: https://github.com/libyal/libscca
@@ -48,16 +48,6 @@
  .
  This package contains a tool to display information about a PF file.
 
-Package: python-libscca
-Section: python
-Architecture: any
-Depends: libscca1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}
-Description: Windows Prefetch File access library -- Python 2 bindings
- libscca is a library to access the Windows Prefetch File (SCCA)
- format.
- .
- This package contains Python 2 bindings for libscca.
-
 Package: python3-libscca
 Section: python
 Architecture: any
diff -Nru libscca-20181227/debian/python-libscca.install libscca-20181227/debian/python-libscca.install
--- libscca-20181227/debian/python-libscca.install	2016-08-30 00:09:46.0 +0300
+++ libscca-20181227/debian/python-libscca.install	1970-01-01 02:00:00.0 +0200
@@ -1 +0,0 @@
-/usr/lib/python2*
diff -Nru libscca-20181227/debian/rules libscca-20181227/debian/rules
--- libscca-20181227/debian/rules	2019-01-14 03:21:54.0 +0200
+++ libscca-20181227/debian/rules	2020-01-19 01:35:22.0 +0200
@@ -10,10 +10,10 @@
 export SKIP_PYTHON_TESTS=1
 
 %:
-	dh $@ --with python2,python3
+	dh $@ --with python3 --buildsystem=autoconf
 
 override_dh_auto_configure:
-	dh_auto_configure -- --enable-python2 --enable-python3
+	dh_auto_configure -- --disable-python2 --enable-python3
 
 override_dh_missing:
 	dh_missing -X.la -X/pyscca.a --fail-missing

Processed: libmsiecf: diff for NMU version 20181227-1.1

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#936895: libmsiecf: diff for NMU version 20181227-1.1

[Adrian Bunk]

Control: tags 936895 + patch
Control: tags 936895 + pending

Dear maintainer,

I've prepared an NMU for libmsiecf (versioned as 20181227-1.1) and 
uploaded it to DELAYED/15. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru libmsiecf-20181227/debian/changelog libmsiecf-20181227/debian/changelog
--- libmsiecf-20181227/debian/changelog	2019-01-14 03:00:33.0 +0200
+++ libmsiecf-20181227/debian/changelog	2020-01-19 01:27:06.0 +0200
@@ -1,3 +1,10 @@
+libmsiecf (20181227-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Remove the Python 2 bindings. (Closes: #936895)
+
+ -- Adrian Bunk   Sun, 19 Jan 2020 01:27:06 +0200
+
 libmsiecf (20181227-1) unstable; urgency=medium
 
   [ Raphaël Hertzog ]
diff -Nru libmsiecf-20181227/debian/control libmsiecf-20181227/debian/control
--- libmsiecf-20181227/debian/control	2019-01-14 02:55:30.0 +0200
+++ libmsiecf-20181227/debian/control	2020-01-19 01:27:06.0 +0200
@@ -3,7 +3,7 @@
 Maintainer: Debian Security Tools 
 Uploaders: Hilko Bengen 
 Build-Depends: debhelper (>= 11),
- pkg-config, python-dev, python3-dev, libbfio-dev,
+ pkg-config, dh-python, python3-dev, libbfio-dev,
 Standards-Version: 4.3.0
 Section: libs
 Homepage: https://github.com/libyal/libmsiecf
@@ -47,16 +47,6 @@
  This package contains tools to access data stored in index.dat files:
  msiecfexport, msiecfinfo.
 
-Package: python-libmsiecf
-Section: python
-Architecture: any
-Depends: libmsiecf1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}
-Description: Microsoft Internet Explorer Cache File access library -- Python 2 bindings
- libmsiecf is a library to access the Microsoft Internet Explorer
- (MSIE) Cache File (index.dat) files.
- .
- This package contains Python 2 bindings for libmsiecf.
-
 Package: python3-libmsiecf
 Section: python
 Architecture: any
diff -Nru libmsiecf-20181227/debian/python-libmsiecf.install libmsiecf-20181227/debian/python-libmsiecf.install
--- libmsiecf-20181227/debian/python-libmsiecf.install	2016-08-02 12:13:47.0 +0300
+++ libmsiecf-20181227/debian/python-libmsiecf.install	1970-01-01 02:00:00.0 +0200
@@ -1 +0,0 @@
-/usr/lib/python2*
diff -Nru libmsiecf-20181227/debian/rules libmsiecf-20181227/debian/rules
--- libmsiecf-20181227/debian/rules	2019-01-14 02:55:49.0 +0200
+++ libmsiecf-20181227/debian/rules	2020-01-19 01:27:06.0 +0200
@@ -10,10 +10,10 @@
 export SKIP_PYTHON_TESTS=1
 
 %:
-	dh $@ --with python2,python3
+	dh $@ --with python3 --buildsystem=autoconf
 
 override_dh_auto_configure:
-	dh_auto_configure -- --enable-python2 --enable-python3
+	dh_auto_configure -- --disable-python2 --enable-python3
 
 override_dh_missing:
 	dh_missing -X.la -X/pymsiecf.a --fail-missing

Processed: liblnk: diff for NMU version 20181227-1.1

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#936890: liblnk: diff for NMU version 20181227-1.1

[Adrian Bunk]

Control: tags 936890 + patch
Control: tags 936890 + pending

Dear maintainer,

I've prepared an NMU for liblnk (versioned as 20181227-1.1) and uploaded 
it to DELAYED/15. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru liblnk-20181227/debian/changelog liblnk-20181227/debian/changelog
--- liblnk-20181227/debian/changelog	2019-01-14 02:49:18.0 +0200
+++ liblnk-20181227/debian/changelog	2020-01-19 01:23:58.0 +0200
@@ -1,3 +1,10 @@
+liblnk (20181227-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Remove the Python 2 bindings. (Closes: #936890)
+
+ -- Adrian Bunk   Sun, 19 Jan 2020 01:23:58 +0200
+
 liblnk (20181227-1) unstable; urgency=medium
 
   * New upstream version 20181227
diff -Nru liblnk-20181227/debian/control liblnk-20181227/debian/control
--- liblnk-20181227/debian/control	2019-01-14 02:49:09.0 +0200
+++ liblnk-20181227/debian/control	2020-01-19 01:23:58.0 +0200
@@ -3,7 +3,7 @@
 Maintainer: Debian Security Tools 
 Uploaders: Hilko Bengen 
 Build-Depends: debhelper (>= 11),
- pkg-config, python-dev, python3-dev, libbfio-dev,
+ pkg-config, dh-python, python3-dev, libbfio-dev,
 Standards-Version: 4.3.0
 Section: libs
 Homepage: https://github.com/libyal/liblnk
@@ -44,15 +44,6 @@
  This package contains lnkinfo, a tool to determine information about
  a Windows Shortcut File.
 
-Package: python-liblnk
-Section: python
-Architecture: any
-Depends: liblnk1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}
-Description: Windows Shortcut File format access library -- Python 2 bindings
- liblnk is a library to access the Windows Shortcut File (LNK) format.
- .
- This package contains Python 2 bindings for liblnk.
-
 Package: python3-liblnk
 Section: python
 Architecture: any
diff -Nru liblnk-20181227/debian/python-liblnk.install liblnk-20181227/debian/python-liblnk.install
--- liblnk-20181227/debian/python-liblnk.install	2016-08-02 12:13:45.0 +0300
+++ liblnk-20181227/debian/python-liblnk.install	1970-01-01 02:00:00.0 +0200
@@ -1 +0,0 @@
-/usr/lib/python2*
diff -Nru liblnk-20181227/debian/rules liblnk-20181227/debian/rules
--- liblnk-20181227/debian/rules	2019-01-14 02:49:09.0 +0200
+++ liblnk-20181227/debian/rules	2020-01-19 01:23:58.0 +0200
@@ -7,10 +7,10 @@
 export SKIP_PYTHON_TESTS=1
 
 %:
-	dh $@ --with python2,python3
+	dh $@ --with python3 --buildsystem=autoconf
 
 override_dh_auto_configure:
-	dh_auto_configure -- --enable-python2 --enable-python3 CFLAGS="-g"
+	dh_auto_configure -- --disable-python2 --enable-python3 CFLAGS="-g"
 
 override_dh_missing:
 	dh_missing -X.la -X/pylnk.a --fail-missing

Processed: libfwsi: diff for NMU version 20181227-1.1

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#936864: libfwsi: diff for NMU version 20181227-1.1

[Adrian Bunk]

Control: tags 936864 + patch
Control: tags 936864 + pending

Dear maintainer,

I've prepared an NMU for libfwsi (versioned as 20181227-1.1) and 
uploaded it to DELAYED/15. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru libfwsi-20181227/debian/changelog libfwsi-20181227/debian/changelog
--- libfwsi-20181227/debian/changelog	2019-01-14 02:41:21.0 +0200
+++ libfwsi-20181227/debian/changelog	2020-01-19 01:20:00.0 +0200
@@ -1,3 +1,10 @@
+libfwsi (20181227-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Remove the Python 2 bindings. (Closes: #936864)
+
+ -- Adrian Bunk   Sun, 19 Jan 2020 01:20:00 +0200
+
 libfwsi (20181227-1) unstable; urgency=medium
 
   * New upstream version 20181227
diff -Nru libfwsi-20181227/debian/control libfwsi-20181227/debian/control
--- libfwsi-20181227/debian/control	2019-01-14 02:41:11.0 +0200
+++ libfwsi-20181227/debian/control	2020-01-19 01:20:00.0 +0200
@@ -4,7 +4,7 @@
 Uploaders: Hilko Bengen 
 Build-Depends: debhelper (>= 11),
  pkg-config,
- python-dev, python3-dev,
+ dh-python, python3-dev,
 Standards-Version: 4.3.0
 Section: libs
 Homepage: https://github.com/libyal/libfwsi
@@ -33,16 +33,6 @@
  .
  This package contains the shared library.
 
-Package: python-libfwsi
-Section: python
-Architecture: any
-Depends: libfwsi1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
- ${python:Depends}
-Description: Windows Shell Item format access library -- Python 2 bindings
- libfwsi is a library to access the Windows Shell Item format.
- .
- This package contains Python bindings for libfwsi.
-
 Package: python3-libfwsi
 Section: python
 Architecture: any
diff -Nru libfwsi-20181227/debian/python-libfwsi.install libfwsi-20181227/debian/python-libfwsi.install
--- libfwsi-20181227/debian/python-libfwsi.install	2017-11-12 15:37:43.0 +0200
+++ libfwsi-20181227/debian/python-libfwsi.install	1970-01-01 02:00:00.0 +0200
@@ -1 +0,0 @@
-/usr/lib/python2*
diff -Nru libfwsi-20181227/debian/rules libfwsi-20181227/debian/rules
--- libfwsi-20181227/debian/rules	2019-01-14 02:41:11.0 +0200
+++ libfwsi-20181227/debian/rules	2020-01-19 01:20:00.0 +0200
@@ -10,10 +10,10 @@
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
 
 %:
-	dh $@ --with python2,python3
+	dh $@ --with python3 --buildsystem=autoconf
 
 override_dh_auto_configure:
-	dh_auto_configure -- --enable-python2 --enable-python3
+	dh_auto_configure -- --disable-python2 --enable-python3
 
 override_dh_missing:
 	dh_missing -X.la -X/pyfwsi.a --fail-missing

Bug#936853: libevtx: diff for NMU version 20181227-1.1

[Adrian Bunk]

Control: tags 936853 + pending

Dear maintainer,

I've prepared an NMU for libevtx (versioned as 20181227-1.1) and 
uploaded it to DELAYED/15. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru libevtx-20181227/debian/changelog libevtx-20181227/debian/changelog
--- libevtx-20181227/debian/changelog	2019-01-14 01:44:32.0 +0200
+++ libevtx-20181227/debian/changelog	2020-01-19 01:15:51.0 +0200
@@ -1,3 +1,10 @@
+libevtx (20181227-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Remove the Python 2 bindings. (Closes: #936853)
+
+ -- Adrian Bunk   Sun, 19 Jan 2020 01:15:51 +0200
+
 libevtx (20181227-1) unstable; urgency=medium
 
   [ Raphaël Hertzog ]
diff -Nru libevtx-20181227/debian/control libevtx-20181227/debian/control
--- libevtx-20181227/debian/control	2019-01-14 01:36:29.0 +0200
+++ libevtx-20181227/debian/control	2020-01-19 01:15:51.0 +0200
@@ -3,7 +3,7 @@
 Maintainer: Debian Security Tools 
 Uploaders: Hilko Bengen 
 Build-Depends: debhelper (>= 11),
- pkg-config, python-dev, python3-dev, libbfio-dev,
+ pkg-config, dh-python, python3-dev, libbfio-dev,
 Standards-Version: 4.3.0
 Section: libs
 Homepage: https://github.com/libyal/libevtx
@@ -44,15 +44,6 @@
  This package contains tools to access data stored in EVT log files:
  evtxexport, evtxinfo.
 
-Package: python-libevtx
-Section: python
-Architecture: any
-Depends: libevtx1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}
-Description: Windows XML Event Log format access library -- Python 2 bindings
- libevtx is a library to access the Windows XML Event Log (EVTX) format.
- .
- This package contains Python 2 bindings for libevtx.
-
 Package: python3-libevtx
 Section: python
 Architecture: any
diff -Nru libevtx-20181227/debian/python-libevtx.install libevtx-20181227/debian/python-libevtx.install
--- libevtx-20181227/debian/python-libevtx.install	2016-08-02 12:13:37.0 +0300
+++ libevtx-20181227/debian/python-libevtx.install	1970-01-01 02:00:00.0 +0200
@@ -1 +0,0 @@
-/usr/lib/python2*
diff -Nru libevtx-20181227/debian/rules libevtx-20181227/debian/rules
--- libevtx-20181227/debian/rules	2019-01-14 01:36:29.0 +0200
+++ libevtx-20181227/debian/rules	2020-01-19 01:15:51.0 +0200
@@ -10,10 +10,10 @@
 export SKIP_PYTHON_TESTS=1
 
 %:
-	dh $@ --with python2,python3
+	dh $@ --with python3 --buildsystem=autoconf
 
 override_dh_auto_configure:
-	dh_auto_configure -- --enable-python2 --enable-python3
+	dh_auto_configure -- --disable-python2 --enable-python3
 
 override_dh_missing:
 	dh_missing -X.la -X/pyevtx.a --fail-missing

Processed: libevtx: diff for NMU version 20181227-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 936853 + pending
Bug #936853 [src:libevtx] libevtx: Python2 removal in sid/bullseye
Added tag(s) pending.

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

Bug#936852: libevt: diff for NMU version 20181227-1.1

[Adrian Bunk]

Control: tags 936852 + patch
Control: tags 936852 + pending

Dear maintainer,

I've prepared an NMU for libevt (versioned as 20181227-1.1) and uploaded 
it to DELAYED/15. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru libevt-20181227/debian/changelog libevt-20181227/debian/changelog
--- libevt-20181227/debian/changelog	2019-01-14 00:40:33.0 +0200
+++ libevt-20181227/debian/changelog	2020-01-19 01:11:31.0 +0200
@@ -1,3 +1,10 @@
+libevt (20181227-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Remove the Python 2 bindings. (Closes: #936852)
+
+ -- Adrian Bunk   Sun, 19 Jan 2020 01:11:31 +0200
+
 libevt (20181227-1) unstable; urgency=medium
 
   * New upstream version 20181227
diff -Nru libevt-20181227/debian/control libevt-20181227/debian/control
--- libevt-20181227/debian/control	2019-01-14 00:35:37.0 +0200
+++ libevt-20181227/debian/control	2020-01-19 01:11:31.0 +0200
@@ -3,7 +3,7 @@
 Maintainer: Debian Security Tools 
 Uploaders: Hilko Bengen 
 Build-Depends: debhelper (>= 11),
- pkg-config, python-dev, python3-dev, libbfio-dev,
+ pkg-config, dh-python, python3-dev, libbfio-dev,
 Standards-Version: 4.3.0
 Section: libs
 Homepage: https://github.com/libyal/libevt
@@ -44,15 +44,6 @@
  This package contains tools to access data stored in EVT log files:
  evtexport, evtinfo.
 
-Package: python-libevt
-Section: python
-Architecture: any
-Depends: libevt1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}
-Description: Windows Event Log (EVT) format access library -- Python 2 bindings
- libevt is a library to access the Windows Event Log (EVT) format.
- .
- This package contains Python 2 bindings for libevt.
-
 Package: python3-libevt
 Section: python
 Architecture: any
diff -Nru libevt-20181227/debian/python-libevt.install libevt-20181227/debian/python-libevt.install
--- libevt-20181227/debian/python-libevt.install	2019-01-14 00:33:57.0 +0200
+++ libevt-20181227/debian/python-libevt.install	1970-01-01 02:00:00.0 +0200
@@ -1 +0,0 @@
-/usr/lib/python2*
diff -Nru libevt-20181227/debian/rules libevt-20181227/debian/rules
--- libevt-20181227/debian/rules	2019-01-14 00:35:58.0 +0200
+++ libevt-20181227/debian/rules	2020-01-19 01:11:31.0 +0200
@@ -10,10 +10,10 @@
 export SKIP_PYTHON_TESTS=1
 
 %:
-	dh $@ --with python2,python3
+	dh $@ --with python3 --buildsystem=autoconf
 
 override_dh_auto_configure:
-	dh_auto_configure -- --enable-python2 --enable-python3 CFLAGS="-g"
+	dh_auto_configure -- --disable-python2 --enable-python3 CFLAGS="-g"
 
 override_dh_missing:
 	dh_missing -X.la -X/pyevt.a --fail-missing