Bug#937095: marked as done (mwparserfromhell: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 14 Oct 2019 05:49:31 +
with message-id 
and subject line Bug#937095: fixed in mwparserfromhell 0.5.4-2
has caused the Debian Bug report #937095,
regarding mwparserfromhell: 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.)


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

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: mwparserfromhell
Source-Version: 0.5.4-2

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

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

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

Debian distribution maintenance software
pp.
Kunal Mehta  (supplier of updated mwparserfromhell 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, 13 Oct 2019 01:25:56 -0700
Source: mwparserfromhell
Architecture: source
Version: 0.5.4-2
Distribution: unstable
Urgency: medium
Maintainer: Kunal Mehta 
Changed-By: Kunal Mehta 
Closes: 937095
Changes:
 mwparserfromhell (0.5.4-2) unstable; urgency=medium
 .
   * Drop Python 2 support (Closes: #937095)
Checksums-Sha1:
 410853a9345f375d011605c14c1002d2e7cc1526 2030 mwparserfromhell_0.5.4-2.dsc
 ffd53d1c2fa3ba9726a61446bbac43df9bc0f17e 2564 
mwparserfromhell_0.5.4-2.debian.tar.xz
 eb1ba2fbc71d48b6a93e079fdd880dab0beb37ad 6559 
mwparserfromhell_0.5.4-2_amd64.buildinfo
Checksums-Sha256:
 12b35cda7cee0e457ed10490dc64a0b24de0d43399cc92425d894d28e3786949 2030 
mwparserfromhell_0.5.4-2.dsc
 b9909a67552d6d3ab907871a19fd1dba98690c3c87ef96b79d29dca65ed7d3ce 2564 
mwparserfromhell_0.5.4-2.debian.tar.xz
 2a98950926f4ed494b0854ef939252c0289b3c652fafafd8511aeefab5654313 6559 
mwparserfromhell_0.5.4-2_amd64.buildinfo

Bug#942229: marked as done (llvm-toolchain-9: Fails to compile on i386)

[Debian Bug Tracking System]

Your message dated Mon, 14 Oct 2019 07:43:28 +0200
with message-id <9215076f-27a1-37c5-00ab-9fef31bd2...@debian.org>
and subject line Re: llvm-toolchain-9: Fails to compile on i386
has caused the Debian Bug report #942229,
regarding llvm-toolchain-9: Fails to compile on i386
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.)


-- 
942229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-9
Version: 1:9-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Trying to build the i386 llvm-9 packages in a chroot by typing "debuild" fails 
with:

make[5]: Leaving directory 
'/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm'
make -f tools/clang/CMakeFiles/stage2.dir/build.make 
tools/clang/CMakeFiles/stage2.dir/build
make[5]: Entering directory 
'/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm'
[100%] Performing configure step for 'stage2'
cd 
/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm/tools/clang/stage2-bins 
&& /usr/bin/cmake -DCMAKE_INSTALL_PREFIX=/usr/lib/llvm-9 "-DCMAKE_CXX_FLAGS= 
-fuse-ld=gold -fPIC -Wno-unused-command-line-argument 
-Wno-unknown-warning-option" "-DCMAKE_C_FLAGS= -fuse-ld=gold -fPIC 
-Wno-unused-command-line-argument -Wno-unknown-warning-option" 
-DCMAKE_INSTALL_PREFIX=/usr/lib/llvm-9 -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=RelWithDebInfo "-DCMAKE_CXX_FLAGS_RELWITHDEBINFO=-O2 
-DNDEBUG -g1" -DLLVM_LINK_LLVM_DYLIB=ON -DLLVM_INSTALL_UTILS=ON 
-DLLVM_VERSION_SUFFIX= -DLLVM_ENABLE_SPHINX=ON -DSPHINX_WARNINGS_AS_ERRORS=OFF 
-DLLVM_BUILD_LLVM_DYLIB=ON -DLLVM_ENABLE_RTTI=ON -DLLVM_ENABLE_FFI=ON 
-DLIBCLANG_LIBRARY_VERSION=1 -DENABLE_LINKER_BUILD_ID=ON 
-DPOLLY_BUNDLED_JSONCPP=OFF -DLLVM_EXPERIMENTAL_TARGETS_TO_BUILD=AVR 
-DLLVM_USE_PERF=yes -DLLVM_ENABLE_ASSERTIONS=OFF 
-DLLVM_BINUTILS_INCDIR=/usr/include -DLLVM_HOST_TRIPLE=x86_64-pc-linux-gnu 
-DLLVM_COMPILER_CHECKED=ON -DCOMPILER_RT_BUILD_BUILTINS=ON 
-DLIBOMP_LIBFLAGS=-latomic "-DCMAKE_SHARED_LINKER_FLAGS=-latomic -Wl,-z,defs 
-Wl,-z,nodelete -flto=thin" -DPYTHON_EXECUTABLE=/usr/bin/python3 
-DPACKAGE_VERSION=9.0.0 -DLLVM_VERSION_MAJOR=9 -DLLVM_VERSION_MINOR=0 
-DLLVM_VERSION_PATCH=0 -DCLANG_VERSION_MAJOR=9 -DCLANG_VERSION_MINOR=0 
-DCLANG_VERSION_PATCHLEVEL=0 -DLLVM_VERSION_SUFFIX= 
-DLLVM_BINUTILS_INCDIR=/usr/include -DCLANG_REPOSITORY_STRING= 
-DCMAKE_MAKE_PROGRAM=/usr/bin/make -DLLVM_ENABLE_PROJECTS= -DCLANG_STAGE=stage2 
-DCMAKE_CXX_COMPILER=/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm/./bin/clang++
 
-DCMAKE_C_COMPILER=/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm/./bin/clang
 
-DCMAKE_ASM_COMPILER=/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm/./bin/clang
 -DCMAKE_ASM_COMPILER_ID=Clang -DCMAKE_VERBOSE_MAKEFILE=On 
-DCMAKE_AR=/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm/./bin/llvm-ar
 
-DCMAKE_RANLIB=/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm/./bin/llvm-ranlib
 "-GUnix Makefiles" /usr/local/src/test/stage/llvm-toolchain-9-9
Re-run cmake no build system arguments
-- Could NOT find Z3: Found unsuitable version "0.0.0", but required is at 
least "4.7.1" (found Z3_LIBRARIES-NOTFOUND)
CMake Error at cmake/config-ix.cmake:320 (message):
  libffi includes are not found.
Call Stack (most recent call first):
  CMakeLists.txt:618 (include)


-- Configuring incomplete, errors occurred!
See also 
"/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm/tools/clang/stage2-bins/CMakeFiles/CMakeOutput.log".
See also 
"/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm/tools/clang/stage2-bins/CMakeFiles/CMakeError.log".
make[5]: *** [tools/clang/CMakeFiles/stage2.dir/build.make:109: 
tools/clang/stage2-stamps/stage2-configure] Error 1
make[5]: Leaving directory 
'/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm'
make[4]: *** [CMakeFiles/Makefile2:46011: 
tools/clang/CMakeFiles/stage2.dir/all] Error 2
make[4]: Leaving directory 
'/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm'
make[3]: *** [CMakeFiles/Makefile2:46018: 
tools/clang/CMakeFiles/stage2.dir/rule] Error 2
make[3]: Leaving directory 
'/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm'
make[2]: *** [Makefile:14060: stage2] Error 2
make[2]: Leaving directory 
'/usr/local/src/test/stage/llvm-toolchain-9-9/build-llvm'
make[1]: *** [debian/rules:430: debian-full-build] Error 2
make[1]: Leaving directory '/usr/local/src/test/stage/llvm-toolchain-9-9'
make: *** [debian/rules:271: binary] Error 2
dpkg-buildpackage: error: debian/rules binary 

Bug#585221: marked as done (darcsweb: Python string exceptions no more allowed in Python 2.6)

[Debian Bug Tracking System]

Your message dated Mon, 14 Oct 2019 05:03:25 +
with message-id 
and subject line Bug#942271: Removed package(s) from unstable
has caused the Debian Bug report #585221,
regarding darcsweb: Python string exceptions no more allowed in Python 2.6
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.)


-- 
585221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: darcsweb
Version: 1.1-1
Severity: minor
User: debian-pyt...@lists.debian.org
Usertags: python2.6

Hello,
One of the changes brought by Python 2.6 is the removal of string
exceptions, so they won't work in Python 2.6 (just a side note: they
were also buggy before, since they were not guaranteed to work
reliable even in <2.6); as an example:

$ python2.5 -c "raise 'eggs'"
-c:1: DeprecationWarning: raising a string exception is deprecated
Traceback (most recent call last):
  File "", line 1, in 
eggs

$ python2.6 -c "raise 'eggs'"
Traceback (most recent call last):
  File "", line 1, in 
TypeError: exceptions must be old-style classes or derived from BaseException, 
not str

Since 2.6 is the planned default version for the upcoming new Debian
stable release, there are chances your package may be affected by this
change.

We are not sure your package is impacted, since the exception raise
can be in a dead or very rare branch of the code, and so simply never
being executed. We would like to leverage your package maintainer
status and the relationship with upstream authors to inspect more
deeply the issue and act accordingly (that includes: making this bug
release critical, closing it as irrelevant, tagging it 'wontfix', or
whatever is appropriate).

Jakub Wilk made the discovery of the problem and kindly prepared a
list [1] of all identified packages (downloaded on 2010-06-09) along
with files & lines that triggered the pattern search.

[1] http://people.debian.org/~morph/strexp/string-exceptions.lintian

This mass-bug filing was announced at 2010-06-06 on [2] (see the
thread and the references there).

[2] http://lists.debian.org/debian-devel/2010/06/msg00097.html

We do not consider the whole situation a stopper for the Python
transition to 2.6, except (of course) for those single bugs where
severity will be increased.

Thanks in advance for your attention,
Sandro on behalf of debian-python


--- End Message ---
--- Begin Message ---
Version: 1.1-3.2+rm

Dear submitter,

as the package darcsweb 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/942271

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

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

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

Bug#763607: marked as done (darcsweb: Newer version of darcsweb is available.)

[Debian Bug Tracking System]

Your message dated Mon, 14 Oct 2019 05:03:25 +
with message-id 
and subject line Bug#942271: Removed package(s) from unstable
has caused the Debian Bug report #763607,
regarding darcsweb: Newer version of darcsweb is available.
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.)


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

Darcsweb has been unchanged since 2010, but there are some useful patches at
  http://hub.darcs.net/simon/darcsweb

which get rid of obsolete python functions & make darcsweb more secure in the 
process.

cheers, Phil

-- System Information:
Debian Release: 7.6
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable')
Architecture: powerpc (ppc)

Kernel: Linux 3.16-2-powerpc
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages darcsweb depends on:
ii  darcs  2.8.1-1+b1
ii  debconf [debconf-2.0]  1.5.49
ii  python 2.7.8-1

Versions of packages darcsweb recommends:
ii  apache2 [httpd-cgi]  2.4.10-2
ii  apache2-mpm-prefork [httpd-cgi]  2.4.10-2

darcsweb suggests no packages.

-- Configuration Files:
/etc/apache2/conf.d/darcsweb.conf changed [not included]

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Version: 1.1-3.2+rm

Dear submitter,

as the package darcsweb 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/942271

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

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

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

Bug#942271: marked as done (RM: darcsweb -- RoQA; depends on Python 2, unmaintained, dead upstream)

[Debian Bug Tracking System]

Your message dated Mon, 14 Oct 2019 05:03:14 +
with message-id 
and subject line Bug#942271: Removed package(s) from unstable
has caused the Debian Bug report #942271,
regarding RM: darcsweb -- RoQA; depends on Python 2, unmaintained, dead upstream
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.)


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

Please remove darcsweb. It's dead upstream, unmaintained (last maintainer upload
in 2010) and depends on Python 2.

Cheers,
Moritz

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

  darcsweb |1.1-3.2 | source, all

--- Reason ---
RoQA; depends on Python 2, unmaintained, dead upstream
--

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

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

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#668735: marked as done (darcsweb: unowned files after purge (policy 6.8, 10.8): /etc/apache2/conf.d/darcsweb.conf)

[Debian Bug Tracking System]

Your message dated Mon, 14 Oct 2019 05:03:25 +
with message-id 
and subject line Bug#942271: Removed package(s) from unstable
has caused the Debian Bug report #668735,
regarding darcsweb: unowned files after purge (policy 6.8, 10.8): 
/etc/apache2/conf.d/darcsweb.conf
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.)


-- 
668735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: darcsweb
Version: 1.1-3.1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8 (or 10.8):

http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

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

0m26.9s ERROR: FAIL: Package purging left files on system:
  /etc/apache2   not owned
  /etc/apache2/conf.dnot owned
  /etc/apache2/conf.d/darcsweb.conf  not owned


cheers,

Andreas


darcsweb_1.1-3.1.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Version: 1.1-3.2+rm

Dear submitter,

as the package darcsweb 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/942271

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

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

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

Bug#440832: marked as done (darcsweb: Lighttpd config files)

[Debian Bug Tracking System]

Your message dated Mon, 14 Oct 2019 05:03:25 +
with message-id 
and subject line Bug#942271: Removed package(s) from unstable
has caused the Debian Bug report #440832,
regarding darcsweb: Lighttpd config files
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.)


-- 
440832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=440832
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: darcsweb
Version: 0.16-1
Severity: wishlist


It would be very helpful if config files for lighttpd could be included.

Thanks in advance

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-1-k7 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages darcsweb depends on:
ii  darcs 1.0.9-1an advanced revision control syste
ii  python2.4.4-6An interactive high-level object-o

Versions of packages darcsweb recommends:
ii  lighttpd [httpd]  1.4.16-5   A fast webserver with minimal memo

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 1.1-3.2+rm

Dear submitter,

as the package darcsweb 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/942271

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

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

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

Bug#578236: marked as done (darcsweb: stop shipping files in /etc/apache/)

[Debian Bug Tracking System]

Your message dated Mon, 14 Oct 2019 05:03:25 +
with message-id 
and subject line Bug#942271: Removed package(s) from unstable
has caused the Debian Bug report #578236,
regarding darcsweb: stop shipping files in /etc/apache/
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.)


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

Apache 1.x is long gone and so darcsweb should stop shipping anything in
/etc/apache/

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

Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are


--- End Message ---
--- Begin Message ---
Version: 1.1-3.2+rm

Dear submitter,

as the package darcsweb 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/942271

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

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

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

Bug#767254: marked as done (darcsweb: [INTL:nl] Dutch translation of debconf messages)

[Debian Bug Tracking System]

Your message dated Mon, 14 Oct 2019 05:03:25 +
with message-id 
and subject line Bug#942271: Removed package(s) from unstable
has caused the Debian Bug report #767254,
regarding darcsweb: [INTL:nl] Dutch translation of debconf messages
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.)


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


Package: darcsweb
Severity: wishlist
Tags: l10n patch 


Dear Maintainer,

==
Please find attached the Dutch translation of darcsweb debconf messages.
It has been submitted for review to the debian-l10n-dutch mailing list.
Please add it to your next package revision.
It should be put as debian/po/nl.po in your package build tree.
===

Groetjes,
Frans

===
www.frans-spiesschaert.homenet.org
home.base.be/vt6362833/


nl.po.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Version: 1.1-3.2+rm

Dear submitter,

as the package darcsweb 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/942271

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

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

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

Bug#444901: marked as done (darcsweb: please allow _darcs/prefs/motd as repository description)

[Debian Bug Tracking System]

Your message dated Mon, 14 Oct 2019 05:03:25 +
with message-id 
and subject line Bug#942271: Removed package(s) from unstable
has caused the Debian Bug report #444901,
regarding darcsweb: please allow _darcs/prefs/motd as repository description
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.)


-- 
444901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: darcs
Version: 1.0.9-1
Severity: wishlist

Hello,

darcsweb [1] can show a description for each repository.  ATM this is
internally handle by darcsweb, as darcsweb's config.py states:

  # if you want the descriptions to be picked up automatically from the
  # file named "_darcs/third_party/darcsweb/desc" (one line only), set
  # this to True. It defaults to False
  #autodesc = True

It could be useful to have an official file _darcs/description which
is a small phrase to describe the repository, created by `darcs init`
and retrieved when `darcs get`.  This can be used later by darcsweb as
well as by darcs-server.

Thx, bye,
Gismo / Luca

Footnotes: 
[1] http://auriga.wearlab.de/~alb/darcsweb/

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

Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages darcs depends on:
ii  libc6   2.6.1-5  GNU C Library: Shared libraries
ii  libcurl37.17.0-1 Multi-protocol file transfer libra
ii  libgmp3c2   2:4.2.2+dfsg-1   Multiprecision arithmetic library
ii  libkrb531.6.dfsg.1-7 MIT Kerberos runtime libraries
ii  libncurses5 5.6+20070908-1   Shared libraries for terminal hand
ii  zlib1g  1:1.2.3.3.dfsg-6 compression library - runtime

Versions of packages darcs recommends:
ii  postfix [mail-transport-agent 2.4.5-4High-performance mail transport ag

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 1.1-3.2+rm

Dear submitter,

as the package darcsweb 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/942271

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

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

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

Bug#438945: marked as done (please add more examples for examples/mkconfig.py usage)

[Debian Bug Tracking System]

Your message dated Mon, 14 Oct 2019 05:03:25 +
with message-id 
and subject line Bug#942271: Removed package(s) from unstable
has caused the Debian Bug report #438945,
regarding please add more examples for examples/mkconfig.py usage
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.)


-- 
438945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=438945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: darcsweb
Version: 0.16-1
Severity: minor

Hello,

README.Debian suggests to use $DOCS/examples/mkconfig.py to
automatically add configuration for many repositories.

First of all, examples/mkconfig.py in contains an error in the
instructions:
--8<---cut here---start->8---
--- mkconfig.py.ORG 2007-08-21 00:07:18.0 +0200
+++ mkconfig.py 2007-08-21 00:07:23.0 +0200
@@ -16,7 +16,7 @@
 directory. It outputs the configuration to stdout, so you can redirect it to
 config.py. For example:
 
-$ mkconf.py "http://example.com/darcs/NAME; "Repo for NAME" latin1 \\
+$ mkconfig.py "http://example.com/darcs/NAME; "Repo for NAME" latin1 \\
~/devel/repos/ >> config.py
 
 Remember that you still need to do the base configuration by hand. You can do
--8<---cut here---end--->8---

And anyway it doesn't work as exptected:
=
gismo:/home/luca# sh /usr/share/doc/darcsweb/examples/mkconfig.py \
 "http://localhost/darcs/stumpwm; "Debian StumpWM" \
 utf-8 /home/luca/var/lib/darcs/stumpwm
/usr/share/doc/darcsweb/examples/mkconfig.py: line 19:
A darcsweb configuration generator
--

This is a small utility that generates configuration files for darcsweb, in
case you're lazy and/or have many repositories.

It receives four parameters: the base URL for your repositories, the base
description, the encoding and the directory to get the repositories from.
It replaces the string NAME with the name of the directory that holds the
repository, so you can specify urls and descriptions with the name in them.

Then, it generates an appropiate configuration for each repository in the
directory. It outputs the configuration to stdout, so you can redirect it to
config.py. For example:

$ mkconf.py http://example.com/darcs/NAME Repo: No such file or directory
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

import: unable to open X server `:0.0'.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

import: unable to open X server `:0.0'.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

import: unable to open X server `:0.0'.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

import: unable to open X server `:0.0'.
/usr/share/doc/darcsweb/examples/mkconfig.py: line 33: syntax error near 
unexpected token `('
/usr/share/doc/darcsweb/examples/mkconfig.py: line 33: `def help():'
gismo:/home/luca#
=

Sorry, I'm not a Python expert and thus I cannot provide any help here
and I still don't understand why it tries to open the X server.
Enabling access to the X server for everyone gives a pointer, but
after clicking somewhere on the screen nothing happens.

Thx, bye,
Gismo / Luca

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

Kernel: Linux 2.6.22-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages darcsweb depends on:
ii  darcs 1.0.9-1an advanced revision control syste
ii  python2.4.4-6An interactive high-level object-o

Versions of packages darcsweb recommends:
ii  apache2-mpm-prefork [httpd]   2.2.4-3Traditional model for Apache HTTPD

-- debconf-show failed

--- End Message ---
--- Begin Message ---
Version: 1.1-3.2+rm

Dear submitter,

as the package darcsweb 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/942271

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

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

Debian distribution maintenance software
pp.

Bug#827063: marked as done (spek: segfault on first run)

[Debian Bug Tracking System]

Your message dated Mon, 14 Oct 2019 05:02:23 +
with message-id 
and subject line Bug#941338: Removed package(s) from unstable
has caused the Debian Bug report #827063,
regarding spek: segfault on first run
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.)


-- 
827063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: spek
Version: 0.8.2-3.2+b1
Severity: normal

Hi maintainer,

Right after being installed I run spek from a terminal, which resulted
on a worring dialog about some error. The error is also printed in
standard output (see below). The dialog allowed to continue, which I
choose. After that tried to open a file (File/Open) but it segfaulted:

$ spek

(spek:25021): GLib-CRITICAL **: Source ID 20 was not found when attempting to 
remove it

(spek:25021): GLib-WARNING **:
/build/glib2.0-y6934K/glib2.0-2.42.1/./glib/giounix.c:410Error while getting 
flags for FD: Bad file descriptor (9)

../src/unix/sockunix.cpp(200): assert "m_fd != INVALID_SOCKET" failed in 
OnWriteWaiting(): invalid socket ready for writing?
Segmentation fault
$

Unfortunately I've been not able to reproduce it, even after removing
~/.config/spek file.

Anyway if this happens often will make very bad first impressions for a
program which otherwise works nicely.

regards,

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

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

Versions of packages spek depends on:
ii  libavcodec566:11.6-1~deb8u1
ii  libavformat56   6:11.6-1~deb8u1
ii  libavutil54 6:11.6-1~deb8u1
ii  libc6   2.19-18+deb8u4
ii  libgcc1 1:4.9.2-10
ii  libstdc++6  4.9.2-10
ii  libwxbase3.0-0  3.0.2-1+b1
ii  libwxgtk3.0-0   3.0.2-1+b1

spek recommends no packages.

spek suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.8.2-4+rm

Dear submitter,

as the package spek 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/941338

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

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

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

Bug#933438: marked as done (spek: Please rebuild against wxWidgets GTK 3 package)

[Debian Bug Tracking System]

Your message dated Mon, 14 Oct 2019 05:02:23 +
with message-id 
and subject line Bug#941338: Removed package(s) from unstable
has caused the Debian Bug report #933438,
regarding spek: Please rebuild against wxWidgets GTK 3 package
to be marked as done.

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

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


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

Hi,

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

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

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

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

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

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

Dear submitter,

as the package spek 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/941338

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

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

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

Bug#935745: marked as done (RM: python-pushy -- RoQA; python2 only; dead upstream; low popcon; last upload in 2015)

[Debian Bug Tracking System]

Your message dated Mon, 14 Oct 2019 05:01:52 +
with message-id 
and subject line Bug#935745: Removed package(s) from unstable
has caused the Debian Bug report #935745,
regarding RM: python-pushy -- RoQA; python2 only; dead upstream; low popcon; 
last upload in 2015
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.)


-- 
935745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935745
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pushy
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Hello,
i'm looking at python-pushy as it depends on python-paramiko; one of bullseye
goals is to remove python2 and python-pushy

* is dead upstream
* last upload was in 2015, and NMU (one of the only 2 uploads)
* python2-only
* low popcon

If i dont hear anything back in 10 days, I'll file a RM bug for this package.

Regards,
Sandro


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

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

Versions of packages python-pushy depends on:
ii  python   2.7.16-1
ii  python-paramiko  2.6.0-1

python-pushy recommends no packages.

python-pushy suggests no packages.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-pushy |  0.5.1-1.1 | source
python-pushy | 0.5.1-1.1+b1 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x

--- Reason ---
RoQA; python2 only; dead upstream; low popcon; last upload in 2015
--

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

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

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#941338: marked as done (RM: spek -- RoQA; dead upstream; unmaintained; low popcon; RC-buggy)

[Debian Bug Tracking System]

Your message dated Mon, 14 Oct 2019 05:02:17 +
with message-id 
and subject line Bug#941338: Removed package(s) from unstable
has caused the Debian Bug report #941338,
regarding RM: spek -- RoQA; dead upstream; unmaintained; low popcon; RC-buggy
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.)


-- 
941338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spek
Version: 0.8.2-4
Severity: normal

I think it's time to remove the spek package:

* last upstream release was 6.5 years ago 
* last package update was 3.5 years ago
* has low popcon - inst:331 vote:57
* has no reverse dependencies (according to dak rm)
* 2 open bugs, neither with any maintainer response
* I had to NMU for the last wxWidgets transition 5 years ago, and
  it's now a blocker for the current wxwidgets3.0-gtk3 transition.

If there are no objections within two weeks, I'll turn this into an RM
bug.

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

  spek |0.8.2-4 | source
  spek | 0.8.2-4+b3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x

--- Reason ---
RoQA; dead upstream; unmaintained; low popcon; RC-buggy
--

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

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

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#942266: marked as done (pulseaudio: Please exclude user root when enable pulseaudio service.)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 22:36:24 -0300
with message-id 

and subject line Re: Bug#942266: pulseaudio: Please exclude user root when 
enable pulseaudio service.
has caused the Debian Bug report #942266,
regarding pulseaudio: Please exclude user root when enable pulseaudio service.
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.)


-- 
942266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pulseaudio
Version: 10.0-1+deb9u1
Severity: normal

Hi
Suppose to enable pulseaudio service
$systemctl --global enable pulseaudio.service, but systemd not know exception
in user 0
and create one instance of pulseaudio inspect
§systemctl --global status pulseaudio.service for more info.



-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


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

Kernel: Linux 5.0.0-rc6+ (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pulseaudio depends on:
ii  adduser  3.115
ii  libasound2   1.1.3-5
ii  libasound2-plugins   1.1.1-1
ii  libc62.24-11+deb9u4
ii  libcap2  1:2.25-1
ii  libdbus-1-3  1.10.28-0+deb9u1
ii  libgcc1  1:6.3.0-18+deb9u1
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-2
ii  liborc-0.4-0 1:0.4.26-2
ii  libpulse010.0-1+deb9u1
ii  libsm6   2:1.2.2-1+b3
ii  libsndfile1  1.0.27-3
ii  libsoxr0 0.1.2-2
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   6.3.0-18+deb9u1
ii  libsystemd0  232-25+deb9u12
ii  libtdb1  1.3.11-2
ii  libudev1 232-25+deb9u12
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.4-3+deb9u1
ii  libx11-xcb1  2:1.6.4-3+deb9u1
ii  libxcb1  1.12-1
ii  libxtst6 2:1.2.3-1
ii  lsb-base 9.20161125
ii  pulseaudio-utils 10.0-1+deb9u1

Versions of packages pulseaudio recommends:
ii  rtkit  0.11-4+deb9u1

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  3.0-3.1
pn  pavumeter
ii  udev 232-25+deb9u12

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See 

Bug#936747: marked as done (isbnlib: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 14 Oct 2019 00:49:58 +
with message-id 
and subject line Bug#936747: fixed in isbnlib 3.9.3-1.1
has caused the Debian Bug report #936747,
regarding isbnlib: 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.)


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

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: isbnlib
Source-Version: 3.9.3-1.1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 03 Oct 2019 19:46:17 -0400
Source: isbnlib
Architecture: source
Version: 3.9.3-1.1
Distribution: unstable
Urgency: medium
Maintainer: Aigars Mahinovs 
Changed-By: Sandro Tosi 
Closes: 936747
Changes:
 isbnlib (3.9.3-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * drop python2 support; Closes: #936747
Checksums-Sha1:
 3eec1a84abd1c736fb2ff769b27c5a53e5219fc8 1737 isbnlib_3.9.3-1.1.dsc
 28ddf387d39f32b0367971c174f6c835bda095ce 1756 isbnlib_3.9.3-1.1.debian.tar.xz
 4b9ea721085977f1646c43a359e50b2a6ec5 6171 
isbnlib_3.9.3-1.1_source.buildinfo
Checksums-Sha256:
 2e577942081d720cb9956164e7f981945b07e13e8ecd8f0f4e5a41933ce373d7 1737 
isbnlib_3.9.3-1.1.dsc
 a5531a11bd0fd59051327176db2617cf782007bbae91bd6f778d5dd05661338c 1756 
isbnlib_3.9.3-1.1.debian.tar.xz
 0f1ab8965bd80bb42772922264adedbffc5a235f410fa018a98c0dfa9a377b46 6171 
isbnlib_3.9.3-1.1_source.buildinfo
Files:
 4904c1aa5ace60e5c6f6645c97b79669 1737 python optional isbnlib_3.9.3-1.1.dsc
 

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

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 23:57:04 +
with message-id 
and subject line Bug#937741: fixed in python-exif 2.2.0-3
has caused the Debian Bug report #937741,
regarding python-exif: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-exif

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: python-exif
Source-Version: 2.2.0-3

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-exif 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, 13 Oct 2019 19:35:20 -0400
Source: python-exif
Architecture: source
Version: 2.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 937741
Changes:
 python-exif (2.2.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Drop python2 support; Closes: #937741
Checksums-Sha1:
 d10757181c7b195d425bdf95f0a3e3abdf89d244 2051 python-exif_2.2.0-3.dsc
 86907cfcfe5b4364bf7e7e113d37f149a55665f1 2896 python-exif_2.2.0-3.debian.tar.xz
 2e9007460c4392a9c8b337f8ac39110833ca3bf6 6149 
python-exif_2.2.0-3_source.buildinfo
Checksums-Sha256:
 49e29e05f820502dfc4dc00dae0216625dd1659b95d0dd650fe77d252c3a 2051 
python-exif_2.2.0-3.dsc
 748e5ea1bed5ff93172f0aa59ef273124e6b224bf548e5b1468aab284ef6a0e7 2896 
python-exif_2.2.0-3.debian.tar.xz
 fb2240f52349c4474b1bc912a93731791fd567a6a58d758c2879e7ed4e283510 6149 
python-exif_2.2.0-3_source.buildinfo
Files:
 024b25ede52a5284bd0a707dc6e63bd2 2051 

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

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 22:56:14 +
with message-id 
and subject line Bug#937828: fixed in python-ijson 2.3-2.1
has caused the Debian Bug report #937828,
regarding python-ijson: 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.)


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

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: python-ijson
Source-Version: 2.3-2.1

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-ijson 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, 06 Oct 2019 18:01:24 -0400
Source: python-ijson
Architecture: source
Version: 2.3-2.1
Distribution: unstable
Urgency: medium
Maintainer: Tomasz Buchert 
Changed-By: Sandro Tosi 
Closes: 937828
Changes:
 python-ijson (2.3-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #937828
Checksums-Sha1:
 1b0c84b77f89b601995cfb628b3158e0e7af6275 1920 python-ijson_2.3-2.1.dsc
 e9474ce16d64c51d414783ab22e6b917dec3a639 2236 
python-ijson_2.3-2.1.debian.tar.xz
 dc5980f09c812f1f3a367ce0267091ab4b2d5d5b 6128 
python-ijson_2.3-2.1_source.buildinfo
Checksums-Sha256:
 1cf6c5cc53271de3c761e4c37f49e4811d533d762487646dcef2618f2037444f 1920 
python-ijson_2.3-2.1.dsc
 b67133524069ff7d6c65a5bd54a0b3f192cfd8c56e1b468367420df4099cf462 2236 
python-ijson_2.3-2.1.debian.tar.xz
 883b7e2d7f20298d9c10b4da8d2ee9af7700f4556bec3289f8f0ff44fc89ca0d 6128 
python-ijson_2.3-2.1_source.buildinfo
Files:
 

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

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 22:27:38 +
with message-id 
and subject line Bug#937683: fixed in python-cymruwhois 1.6-3.2
has caused the Debian Bug report #937683,
regarding python-cymruwhois: 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.)


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

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: python-cymruwhois
Source-Version: 1.6-3.2

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-cymruwhois 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, 06 Oct 2019 17:12:33 -0400
Source: python-cymruwhois
Architecture: source
Version: 1.6-3.2
Distribution: unstable
Urgency: medium
Maintainer: Ana Custura 
Changed-By: Sandro Tosi 
Closes: 937683
Changes:
 python-cymruwhois (1.6-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #937683
Checksums-Sha1:
 4d90f855f344c3f969c908ede5b8e92466c55ea7 2086 python-cymruwhois_1.6-3.2.dsc
 884fa6f88c1d6740261a335c77f860f27f6cb1af 3536 
python-cymruwhois_1.6-3.2.debian.tar.xz
 9c6bc43e766d84b3b46582e24016dda72c1fa3e6 7116 
python-cymruwhois_1.6-3.2_source.buildinfo
Checksums-Sha256:
 a15cae93f1584bc0d37b5cf8083d7c92c0301126304e82dbaf6d33b60b332404 2086 
python-cymruwhois_1.6-3.2.dsc
 fb92b1b9a066960e80f46b5b8e555006330da47791a55f4b414f94c7f498b1fa 3536 
python-cymruwhois_1.6-3.2.debian.tar.xz
 6da3aea810bb88234d59ff7d45fd9316cab1f7c1830a4448258f84767a87896c 7116 

Bug#942278: marked as done (dpkg-www: Missing dependancy on perl module CGI.pm. At least when using lighttpd.)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 22:21:38 +
with message-id 
and subject line Bug#942278: fixed in dpkg-www 2.60
has caused the Debian Bug report #942278,
regarding dpkg-www: Missing dependancy on perl module CGI.pm. At least when 
using lighttpd.
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.)


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

Dear Maintainer,

I installed dpkg-www on a raspberry pi running raspian (based on Debian 10.1).
For the web server I chose lighttpd and enabled the cgi module.

When accessing the dpkg-www cgi via a web browser, anything clickable did not 
work.
It would just print the main page. Looking a bit further and setting the debug 
option
I noticed that the script did not receive the query string.

Looking at /usr/lib/cgi-bin/dpkg it tries to load a perl module that is not in 
the dependancies.

1261:perl -e "use CGI; my \$q = new CGI(\$_); print scalar 
\$q->param('$key')" "$1"

I installed libcgi-pm-perl to satisfy the dependancy and then the CGI worked as 
it should.

The system information below is not the same system where I encountered the 
problem.
I doubt that it makes much difference. 

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

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

Versions of packages dpkg-www depends on:
ii  apt   1.4.9
pn  dwww  
pn  info2www  
ii  perl  5.24.1-3+deb9u5

Versions of packages dpkg-www recommends:
pn  apache2 | httpd  

Versions of packages dpkg-www suggests:
ii  chromium [www-browser] 73.0.3683.75-1~deb9u1
ii  dctrl-tools [grep-dctrl]   2.24-2+b1
ii  dlocate1.07+nmu1
ii  firefox-esr [www-browser]  60.9.0esr-1~deb9u1
pn  man2html   
ii  tasksel3.39
--- End Message ---
--- Begin Message ---
Source: dpkg-www
Source-Version: 2.60

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

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

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated dpkg-www 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, 13 Oct 2019 23:41:18 +0200
Source: dpkg-www
Architecture: source
Version: 2.60
Distribution: unstable
Urgency: medium
Maintainer: Dpkg Developers 
Changed-By: Guillem Jover 
Closes: 942278
Changes:
 dpkg-www (2.60) unstable; urgency=medium
 .
   * Bump Standards-Version to 4.4.1 (no changes needed).
   * Switch from debian/compat to debhelper-compat in Build-Depends.
   * Switch to debhelper compatibility level 12.
   * Depend on libcgi-pm-perl, for the CGI module which got removed from
 perl core in 5.21.0. Thanks to Michael Gindonis .
 Closes: #942278
   * Remove obsolete conffile removal and renames.
   * Uppercase apache2 Require directives.
   * Lowercase web in README.Debian.
   * Remove copyright output in CGI HTML footer, as this information can get
 out of sync and duplicates what is already in the source header.
Checksums-Sha1:
 7185e784e7863e14b118c094cd8bca3295e9c89d 1574 dpkg-www_2.60.dsc
 37ecd8e2a0520c0bf4dd6532056a823a6101ae3f 27256 dpkg-www_2.60.tar.xz
 4300ce0b6719f2d91591cc738cb3b2c72e784dd7 5887 dpkg-www_2.60_amd64.buildinfo
Checksums-Sha256:
 dc391a4f830eb18544bb90819aba78e383d4ad4edd829dffe2d33921aa5ec6be 1574 
dpkg-www_2.60.dsc
 e6ba748c370542acfdf0eb8c1f7a1d9e13d6b8341cd24b4d8bb87addda4457c2 27256 
dpkg-www_2.60.tar.xz
 8fc695bc102496506f7e86bc1e1b8922a716086f6f450ef44b6cea89caea208e 5887 
dpkg-www_2.60_amd64.buildinfo
Files:
 1075bc3ef52b7792d1dcddf4dc3f281a 1574 doc optional dpkg-www_2.60.dsc
 50a6a6d88909a99a8d2bb4112a3d1bd8 27256 doc optional dpkg-www_2.60.tar.xz
 35259a5c349347bc950df4aacebb138c 

Bug#937524: marked as done (pyrlp: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 21:26:39 +
with message-id 
and subject line Bug#937524: fixed in pyrlp 0.5.1-1.1
has caused the Debian Bug report #937524,
regarding pyrlp: 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.)


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

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

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

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

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: pyrlp
Source-Version: 0.5.1-1.1

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated pyrlp 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, 06 Oct 2019 16:35:18 -0400
Source: pyrlp
Architecture: source
Version: 0.5.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Ben Finney 
Changed-By: Sandro Tosi 
Closes: 937524
Changes:
 pyrlp (0.5.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #937524
Checksums-Sha1:
 227dd94a14abd6fb38bdb14072f1eee83e8bb0c0 2092 pyrlp_0.5.1-1.1.dsc
 392d17007cc73dd1992d0d74f105efbdd7299d16 5256 pyrlp_0.5.1-1.1.debian.tar.xz
 042e57154dfeeead8a2058debd4fe37e23a94c6a 7361 pyrlp_0.5.1-1.1_source.buildinfo
Checksums-Sha256:
 b6fd918a332bc47f7b8a6ccff3e977a83b0b5c71c253f586f5e2a9b2a260cba9 2092 
pyrlp_0.5.1-1.1.dsc
 acf1fbf83f1e387eff33abfb46ea258fb18cf6f59f34274970633e239f9c730f 5256 
pyrlp_0.5.1-1.1.debian.tar.xz
 92f230c966d510163989c89d87590e44d8ddcc3c59d4bbe1736c1d8afae1a891 7361 
pyrlp_0.5.1-1.1_source.buildinfo
Files:
 cd9b19896485667ce7d4407a9f859b8c 2092 python optional pyrlp_0.5.1-1.1.dsc
 4de395d99d0ab41ba7f4f94e959f4b02 5256 

Bug#927513: marked as done (Updating the zipl-installer Uploaders list)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 21:11:46 +
with message-id 
and subject line Bug#927513: fixed in zipl-installer 0.0.40
has caused the Debian Bug report #927513,
regarding Updating the zipl-installer Uploaders list
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.)


-- 
927513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zipl-installer
Version: 0.0.39
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the zipl-installer package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.
--- End Message ---
--- Begin Message ---
Source: zipl-installer
Source-Version: 0.0.40

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

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

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

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated zipl-installer 
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, 13 Oct 2019 22:24:05 +0200
Source: zipl-installer
Architecture: source
Version: 0.0.40
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 927513
Changes:
 zipl-installer (0.0.40) unstable; urgency=medium
 .
   * Team upload
 .
   [ Cyril Brulebois ]
   * Remove Christian Perrier from Uploaders, with many thanks for all
 his contributions over the years! (Closes: #927513)
 .
   [ Holger Wansing ]
   * Add comment for translators, to keep main menu entry below a 55 columns
 limit. This updates all po|pot files.
 .
   [ Updated translations ]
   * Croatian (hr.po) by gogogogi
Checksums-Sha1:
 5434c70df95d779a0b0990714390207a05b1d21b 1700 zipl-installer_0.0.40.dsc
 f59e9d7522a44bd070b9224fb05fc2579dc8f4d3 23144 zipl-installer_0.0.40.tar.xz
 2f69212c283d6399db9cbb5046cd83ad2dff6275 5511 
zipl-installer_0.0.40_s390x.buildinfo
Checksums-Sha256:
 8aab3b44d64f6c90f6ccb47b9bd2ab142a399e24f62b6cb550d6ba589f848fb8 1700 
zipl-installer_0.0.40.dsc
 291bac3dee3ca6d03b54d1da0d7c8b3e619e214928e92ee26ad214128618f219 23144 
zipl-installer_0.0.40.tar.xz
 ebf54719f5c868539fd535fc63ae6fa01917d4fa1c15aa2ce7d43295007f65a1 5511 
zipl-installer_0.0.40_s390x.buildinfo
Files:
 1edcc75a0488cfc292a38c5c9b88a870 1700 debian-installer standard 
zipl-installer_0.0.40.dsc
 7306c295b13e6935d46ea6e9a8329cb6 23144 debian-installer standard 
zipl-installer_0.0.40.tar.xz
 12a28453569cc560bca2aece109475c9 5511 debian-installer standard 
zipl-installer_0.0.40_s390x.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAl2jiX8VHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB23YEQALgwqxcQwEMbSMTqyDupX4WEgne2
ZMA6zDxar5COdN3WAP/I7cTjvD4OYWywOPoPKRW2UzSeMv0YZmP6B3A/0ig7lPgm
qsVUNRgynl79qz6dSSISTsM9xEr2Nqtw6zwlv0Nyq7HpDjkKJx+AOx9sP5qm2JOS
RoqVxwWZ1Dti+HavCDSiHmfKEvTmTn40WPiOWUCAq4pHATKoMZyS92Axw+TtLxPt
Rgh0NhoyAF1MXgcTOHNHzUvgdPq8HpSvm7gYYp1h2bzu/OiaFr13zbZ51YwesfaJ
qzd1GA3kILr5N7vsVWG3ovgrvPlJ1IXcwbDlFM3thk8s4T0CiqkUH2Ec9kbksdsX
kWueEnt3mhs6meB68USSql52P5DAj74rc517yDeaIsCYiQxUJUU7dvdETTgNjqm/
GLIVhRx8LpHZClmVGxpOJQ4bl4Rv4qEYJu/6DyV0Kf5tR5cYebSTEBaq18m8Hrzh
3oZjH9bSVVBoKrutvzidKacUSHOknm3UPP9nJll4kvLoDOqGTh8oAKMY6tt3/znZ
SKnIY6M4IexVXxFAntotCGT5NeTD2DzUiyOKhJ77CH17jRrFlJF4+MYR3faR7Oo3
puN5h9RkzmaxcC38gmvTqqCfIGlL/m9kmKJBWxITRIfnUk7FpheRVnglPLiWjn9O
wDV59rfHz8q/90a7
=UHu/
-END PGP SIGNATURE End Message ---

Bug#937112: marked as done (natsort: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 20:52:19 +
with message-id 
and subject line Bug#937112: fixed in natsort 6.0.0-1.1
has caused the Debian Bug report #937112,
regarding natsort: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:natsort

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: natsort
Source-Version: 6.0.0-1.1

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated natsort 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, 06 Oct 2019 16:00:20 -0400
Source: natsort
Architecture: source
Version: 6.0.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Agustin Henze 
Changed-By: Sandro Tosi 
Closes: 937112
Changes:
 natsort (6.0.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #937112
Checksums-Sha1:
 0ae636ab74522a97a55f86e3c2d949691549211e 2103 natsort_6.0.0-1.1.dsc
 a830fc9ea874ed7003cedcafad8dc00a215f6c47 3940 natsort_6.0.0-1.1.debian.tar.xz
 e0986be6c8efe83e68115a1d3423cd0b8167b7c9 7113 
natsort_6.0.0-1.1_source.buildinfo
Checksums-Sha256:
 642fbd743212731c1a29a894d41b310af4186d39b4fa5dc0e49f863ec738c93e 2103 
natsort_6.0.0-1.1.dsc
 2607300032bd4bdfdc433935a9db83b319f7c0b1e51d6091fab5f6d19d0a753b 3940 
natsort_6.0.0-1.1.debian.tar.xz
 3b48f25ed72ac14c6125b73977160a9e04d43c6a6370cc68cc798ba059060ed3 7113 
natsort_6.0.0-1.1_source.buildinfo
Files:
 e7204c66b0902a97d7f354a145110dec 2103 python optional natsort_6.0.0-1.1.dsc
 

Bug#927514: marked as done (Updating the partman-base Uploaders list)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 20:53:58 +
with message-id 
and subject line Bug#927514: fixed in partman-base 209
has caused the Debian Bug report #927514,
regarding Updating the partman-base Uploaders list
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.)


-- 
927514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: partman-base
Version: 208
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the partman-base package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.
--- End Message ---
--- Begin Message ---
Source: partman-base
Source-Version: 209

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

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

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

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated partman-base 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, 13 Oct 2019 21:57:14 +0200
Source: partman-base
Architecture: source
Version: 209
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 927514
Changes:
 partman-base (209) unstable; urgency=medium
 .
   * Team upload
 .
   [ Cyril Brulebois ]
   * Remove Christian Perrier from Uploaders, with many thanks for all
 his contributions over the years! (Closes: #927514)
 .
   [ Holger Wansing ]
   * Add comment for translators, to keep main menu entry below a 55 columns
 limit. This updates all po|pot files.
 .
   [ Updated translations ]
   * Croatian (hr.po) by gogogogi
Checksums-Sha1:
 2d00dc50cdcd8b005e00223618b2ffd39d7c3040 1891 partman-base_209.dsc
 cfd086ddcb3d466d6d45b2f96292becdd128a92f 174684 partman-base_209.tar.xz
 deea44382e0e919f8c0db855c63f1f9c372f06c1 6297 partman-base_209_amd64.buildinfo
Checksums-Sha256:
 437ea082ec2b1a4ed478671dfb2ff92c59272a796189ef952cb09cdbf746ccaf 1891 
partman-base_209.dsc
 ccc9dad4ed4ec057e90a5d10875f8fa740588c8d3b3b1fa2b57d8c3641fc39e1 174684 
partman-base_209.tar.xz
 398b75420d8ead368378d795a0866f61214c0f927f62e0f353db7312e35a1c2d 6297 
partman-base_209_amd64.buildinfo
Files:
 68aa00814860966a028a4255b2d6197e 1891 debian-installer standard 
partman-base_209.dsc
 f37095ff61d745a8c7cd9261cef5e92b 174684 debian-installer standard 
partman-base_209.tar.xz
 ef243a644bf963c4bb75547e080d6da9 6297 debian-installer standard 
partman-base_209_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAl2jgyoVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2eCMP/1eE++JwoTw5Iasj/Gk7A2EjXEwy
hTGpNSxX8wGg5124ZcNSu2hNlLoCDT2dNzSx4mrQXIHb1NP7AyRAsDXywbA7HHcE
LiDRuIx2XDppqxWlCicOzRY6OrdlQdmMcBC1XT9Ch9D+115rjxn2XgQxmJ21HeBT
YKM+zkfceEZOp7Hx6raCzXpD3X5+gZPEwYR/0ml6vc+P16hAR1nObVWJeD+t8l4r
i419TsYW2mMHKIrje6NbwO802ACmwRg5K/ZWtVc4GBkLQelc1W6aj3ohzZ7jcbUq
i1F8XcEsaDTQx45hBNJGZOC5PkzlwtLoaIaVFiTsVLMQJYk90pKMk3q74rmLBIJ8
Fg2mPl/ViIDFMBb/jIAl+8PGFkuHRG+Ye4rzGVmCRuH1F2RFRCXHM2dqU0/k2wkq
EkYko1WPGsdS2gAd782HU1DEyDcRhYkjKekZflH0Woe0nnEGaCyPMVr/JLVYous5
X+y05kr7voibRWwpSTz5KX3a7UQca0/RjHoCpmzvjKmExxSwCTr/5i1XaNLTbGQr
WXIImJz3IDSHIshP/kRC3KFYLj717+WTIlDeDidQ4FnJB14E12QWYmhnPJXeWCxz
uecU/9fyxLvc0NrceTjKJHdXP+ytNhmO4AvLf/fG9NObo8/9mYyNiLM9gz7fWtJx
jbHFfTgwBiXhO4XP
=3NmB
-END PGP SIGNATURE End Message ---

Bug#927506: marked as done (Updating the s390-netdevice Uploaders list)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 20:54:34 +
with message-id 
and subject line Bug#927506: fixed in s390-netdevice 0.0.69
has caused the Debian Bug report #927506,
regarding Updating the s390-netdevice Uploaders list
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.)


-- 
927506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: s390-netdevice
Version: 0.0.68
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the s390-netdevice package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.
--- End Message ---
--- Begin Message ---
Source: s390-netdevice
Source-Version: 0.0.69

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

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

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

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated s390-netdevice 
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, 13 Oct 2019 22:14:27 +0200
Source: s390-netdevice
Architecture: source
Version: 0.0.69
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 927506
Changes:
 s390-netdevice (0.0.69) unstable; urgency=medium
 .
   * Team upload
 .
   [ Cyril Brulebois ]
   * Remove Christian Perrier from Uploaders, with many thanks for all
 his contributions over the years! (Closes: #927506)
 .
   [ Holger Wansing ]
   * Add comment for translators, to keep main menu entry below a 55 columns
 limit. This updates all po|pot files.
 .
   [ Updated translations ]
   * Croatian (hr.po) by gogogogi
Checksums-Sha1:
 af60bc2f49a7fb12fb8319809e9cfdbe379c2449 1795 s390-netdevice_0.0.69.dsc
 45eddb4f1849ad658bf320c96dbec17cf7d9bddf 96292 s390-netdevice_0.0.69.tar.xz
 b96f9d7ad52a06c1a0ccf9a3e4c4f1e06114fc3e 5722 
s390-netdevice_0.0.69_s390x.buildinfo
Checksums-Sha256:
 f1ae89c2b85f5b5caf251c8316685187e99e9647c78c0edc6f90c16efe366714 1795 
s390-netdevice_0.0.69.dsc
 eed104b7742594addfc520e5a699f508f6080cd93bac3f5bdf6557e0f1e7f99c 96292 
s390-netdevice_0.0.69.tar.xz
 28251b08612cc94e73d9e56c5ac391e8309619b83ba436dfa606d76a4b20b3ae 5722 
s390-netdevice_0.0.69_s390x.buildinfo
Files:
 3cde3b210168c28b88dc70700385b16b 1795 debian-installer standard 
s390-netdevice_0.0.69.dsc
 49af6f6af80b8dc30aafc757b53e74e0 96292 debian-installer standard 
s390-netdevice_0.0.69.tar.xz
 24b5423672129ae78f00250885360b81 5722 debian-installer standard 
s390-netdevice_0.0.69_s390x.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAl2jh1MVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2uicP/2/B43J7KH+EoeXDGZGwL31lywUC
XQRWtC9nw9uozdN4KJQ8NVxz5byerOmge011XyJ23uJV9wAZvp1aUxuLZDB6wRU5
YdXojHaknHnF6XvgVpG8DfYXYm6KbmNNubPrfj1QTvA045B+9iAsvR/eKkPYIF2u
4UtRzs1FPRKWFMQjy4j5MC7DqtdIDps+ltLn/FE05u1t6SiS/VKPVbxDNCllg0Ju
Tw7XwIZLwR5JYemBc9nusfGGVIoNIsNh2FWClrb3LuR59ORHFSUiHuibzNMbka6q
UInwo4b/UzOK2hG2occ2xxgMok/Df5rpKPHgCUYr+mftiSmZJd17LRJY+VOj2yIf
acaE8JsX8embBDQxWF+rqjC4btpCNArtVl00nlhg1FB+XwQmIvY00/JHRIWUcfZ8
YMLfCa6J3nbgZficIVVvycYE8btn7MG0ZlK2yYQ+mWIcRB3UghzquHh+O2iXHAPe
dCiXFzt0hfIzLrUhcW5cwnQTRPPY9S1QYKETSxugETzOGLXOED5VFMQNlXyKgaqy
qP8cnpFnSvqRyqesyKM/ZOD02lNmD9//fQi6IlxgaUyTqtZazb3S+jduiKS8NZtV
oFJ+4N7yctHiagMe/jL4SDT07YLj2aZREyc0FDzRKvIejflv+eU838XwYSrVpzY+
3K19BfVOALmUsscu
=6GZb
-END PGP SIGNATURE End Message ---

Bug#927536: marked as done (Updating the rescue Uploaders list)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 20:54:04 +
with message-id 
and subject line Bug#927536: fixed in rescue 1.77
has caused the Debian Bug report #927536,
regarding Updating the rescue Uploaders list
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.)


-- 
927536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rescue
Version: 1.67 1.75 1.76
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the rescue package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.
--- End Message ---
--- Begin Message ---
Source: rescue
Source-Version: 1.77

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

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

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

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated rescue 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, 13 Oct 2019 22:07:29 +0200
Source: rescue
Architecture: source
Version: 1.77
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 927536
Changes:
 rescue (1.77) unstable; urgency=medium
 .
   * Team upload
 .
   [ Cyril Brulebois ]
   * Remove Christian Perrier from Uploaders, with many thanks for all
 his contributions over the years! (Closes: #927536)
 .
   [ Updated translations ]
   * Croatian (hr.po) by gogogogi
   * Icelandic (is.po) by Sveinn í Felli
   * Portuguese (pt.po) by Miguel Figueiredo
Checksums-Sha1:
 32c5bfba271c96e911f2a824d2fbbd398bafc36f 1671 rescue_1.77.dsc
 8dad7fe42fa5d44847539aa0960cadccf1aa724a 140096 rescue_1.77.tar.xz
 96e07138588dc503affb96697823a7b3c3c2c336 5691 rescue_1.77_amd64.buildinfo
Checksums-Sha256:
 86f290c126424ef36e386dc9f6d2a21489d510c22acdaf0f93f7faa573f5e8b8 1671 
rescue_1.77.dsc
 1b18a687064e22aa5dd6cfc1af395e65f6e4a94421d1785b6db34a452131a3c6 140096 
rescue_1.77.tar.xz
 dc4994093aa91ac3f5a1e216e631eb432a2b3ed4f6039cc965c862e8bb46932a 5691 
rescue_1.77_amd64.buildinfo
Files:
 60a79866bbe3aebd7c8b0b9636a33319 1671 debian-installer optional rescue_1.77.dsc
 fe1f35ee4410b9fdc4182e19e81b32e5 140096 debian-installer optional 
rescue_1.77.tar.xz
 32c0e88039dd382e2729c70dcabcdfcd 5691 debian-installer optional 
rescue_1.77_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAl2jhTMVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2PZUP/A9JXWTFYA+KQiZ7bJOgUHgB1Lfk
kPpB4gGDw9ngUmgHuUxFpURi3RUnth/Ch3nXZdkbe3el4XqJY+tPh91J5sSUMtRa
LGlRy9DRq+qX+WfcZBpUuUdpPxfFcbl9qpZABvcthgeQGh820RQH96qjlrcGUzS6
nayMbhu2aLKZ0ZofxhRGhYHCPVf2CSG9sLQT+huOytUYnQARW33aLbd8wTFaE/8+
F3ZpGM1un6te9CLpFERaY9FEeSEqv4pWq+Bz44e9t4I6fVnYLZjV1+F0sFRRmyPF
GdoDDBdDi+Qxa4VuZ+JXDe+DqcGUSqk3pAXmoRyxwogOXVwzFRBvG6grqR6j4gkq
QWWDEpqj7qq7w2Wf6hF/cvEaJhAIyy2//3k+HfzouhvKPOVPWDtAZ0rxa7Db9chQ
5Y3eE6IEcBgBUnXLCdcOgF+xcEyXpva6b7rNrIhvhGL5t1pN2fd5Nz484vupMPqz
aQKw3j5UvhdW2nu7GT4+1+UU0Da7OpCNeauqPgn4dgU9h5fxhWBLsL30yX4KzggN
OcR4ROz7e+JXpRI92HNe29qjhXcgH3DNzeIOlX6c0XuaT8YZZCGWLmBQH7JEjCsN
DLKq94vY2ryJIqNBm9UNGozReKoLCRuFbF5SAWZZGZbUa8f1wUrQDjh+8KUMluIF
EkWEV96yYiun3YT2
=aGcK
-END PGP SIGNATURE End Message ---

Bug#927508: marked as done (Updating the nobootloader Uploaders list)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 20:52:25 +
with message-id 
and subject line Bug#927508: fixed in nobootloader 1.57
has caused the Debian Bug report #927508,
regarding Updating the nobootloader Uploaders list
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.)


-- 
927508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nobootloader
Version: 1.56
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the nobootloader package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.
--- End Message ---
--- Begin Message ---
Source: nobootloader
Source-Version: 1.57

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

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

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

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated nobootloader 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, 13 Oct 2019 21:50:03 +0200
Source: nobootloader
Architecture: source
Version: 1.57
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 927508
Changes:
 nobootloader (1.57) unstable; urgency=medium
 .
   * Team upload
 .
   [ Cyril Brulebois ]
   * Remove Christian Perrier from Uploaders, with many thanks for all
 his contributions over the years! (Closes: #927508)
 .
   [ Holger Wansing ]
   * Add comment for translators, to keep main menu entry below a 55 columns
 limit. This updates all po|pot files.
 .
   [ Updated translations ]
   * Croatian (hr.po) by gogogogi
   * Portuguese (pt.po) by Miguel Figueiredo
Checksums-Sha1:
 6bb34cbadb3aba8e72db2ee99fc4f692a4ada366 1637 nobootloader_1.57.dsc
 00ad83d34bc926fdf6410f7b9e2694108927599e 79872 nobootloader_1.57.tar.xz
 f2e71011cdbbe24616e3f817ad267ada6627344e 5462 nobootloader_1.57_amd64.buildinfo
Checksums-Sha256:
 f73eaff3056ab9de741a658dd0cdea7a5e9bdafc8bcda46c3e7a4b63aacc55c2 1637 
nobootloader_1.57.dsc
 f45e55a6ce7fd339bbd665d90b45091344bd98f47badd8fb6699db2b73860122 79872 
nobootloader_1.57.tar.xz
 4a4487252e86a8413966dc0710990ef8485a65a437ccd827049019d25b4543d8 5462 
nobootloader_1.57_amd64.buildinfo
Files:
 6a96f15b07bd8c391b2f100f13f51809 1637 debian-installer standard 
nobootloader_1.57.dsc
 56344dd08df667960f54b8115ac563f0 79872 debian-installer standard 
nobootloader_1.57.tar.xz
 7dd0cbe57fb64ab5e3248d38ef491218 5462 debian-installer standard 
nobootloader_1.57_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAl2jgTAVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2kYwQAIOaNTVkNBCBfRmoPPh6LDAiKRnq
DJ8Wev3lo/DAWx4Qy57tKso7rJc2jnQ4wdDDS3tFWLgzWoiXlF/S98SDZPtDsk98
y6N3E6R8bF8Kne0F1lmH3Bn8m+dTnJoHh9NuogwCreYUvP/FW3rcMeb1/Nkqtn2d
TDwqs2PCZBq/NU7+w0l1li0HfoPQKlWj0Vhswd2EtCqgYWlc5VcOtqX4GFi3iKAv
fsXS5Ob2a55mhVVwr5JcDAf4hJQM4wt0uAVIgtDqG/sysNLh9/vJmxO3wb4/utQG
jZP9VeNJYomy7u6ikzVRJ5s+bp5mC4CPYBEYMpoJWlCDrGQmts5EXMY1r1OFBS22
ynIfqqLKsAHzIAkrFAhhAJwInNuuBKMFV6NIsb2yZ3bvgRxoIfchtpahPmwHO0tn
Ape8iQBMi17tpCCP7pRUlvs3d1QB+I5XHHysM+PKff6LAI8eVBMHLMBb4vaMO+TY
GLCbiFqbEOtd5K5MRVkX9VYpfJcKedakU6IUjX+FftVVKYb+dlwmJK1/REZpgJjX
Lw8Qja+OkneI9jM3TWPF8/5ZUQu1v+wFV4Xaedpou0Z5zGYCMvvRphgzjEO4Rs8R
FCcaigsduTTQgiLnmkg3msERlteaH/2yJBytl9YCysjndsjX9G0jw9cwA9aoEi0P
G3abiblaUC16m+N1
=1D+d
-END PGP SIGNATURE End Message ---

Bug#927524: marked as done (Updating the mdcfg Uploaders list)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 20:52:12 +
with message-id 
and subject line Bug#927524: fixed in mdcfg 1.64
has caused the Debian Bug report #927524,
regarding Updating the mdcfg Uploaders list
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.)


-- 
927524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mdcfg
Version: 1.63
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the mdcfg package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.
--- End Message ---
--- Begin Message ---
Source: mdcfg
Source-Version: 1.64

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

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

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

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated mdcfg 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, 13 Oct 2019 21:39:05 +0200
Source: mdcfg
Architecture: source
Version: 1.64
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 927524
Changes:
 mdcfg (1.64) unstable; urgency=medium
 .
   * Team upload
 .
   [ Cyril Brulebois ]
   * Remove Christian Perrier from Uploaders, with many thanks for all
 his contributions over the years! (Closes: #927524)
 .
   [ Holger Wansing ]
   * Add comment for translators, to keep main menu entry below a 55 columns
 limit. This updates all po|pot files.
   * Remove trailing whitespace from control file, to fix lintian tag.
 .
   [ Updated translations ]
   * Croatian (hr.po) by gogogogi
   * Icelandic (is.po) by Sveinn í Felli
   * Portuguese (pt.po) by Miguel Figueiredo
Checksums-Sha1:
 1c2660578e903e536065967bc199e0a97be9f6a9 1641 mdcfg_1.64.dsc
 06e63a73610798db6b80c3b2640c569c7830bafc 145996 mdcfg_1.64.tar.xz
 055dbe9868c47977128c43a0bd6154bc95106403 5642 mdcfg_1.64_amd64.buildinfo
Checksums-Sha256:
 9b951b9e237c592ed50b6f056cc1f0ab0e632cc8de0d8e03665eca3c1710e883 1641 
mdcfg_1.64.dsc
 27dd4f1113a71a9c9976b061752d1890c42c1748a18913e00382fb2ba79a031f 145996 
mdcfg_1.64.tar.xz
 8c8812f4781c95427bc835ec6298dbb1f195888785bf26ff7cb98e4ccb16 5642 
mdcfg_1.64_amd64.buildinfo
Files:
 9234e028b2c6d8b5ee078e3a72cfc68e 1641 debian-installer optional mdcfg_1.64.dsc
 c7d109d97f196c728e46d4670a7d2be2 145996 debian-installer optional 
mdcfg_1.64.tar.xz
 e042113fa1bb7a15d8fd761238fefa97 5642 debian-installer optional 
mdcfg_1.64_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAl2jf2AVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB23SoQALKB/BeiBWh0tipWVvdLpzYtgKVf
1Iw5/ekJLRaGYr7gbvQ8dbgUrPWtHPEc9KnOpqt5ebkhpzoW0N7hN+h0NKlKWA/W
cVZe20rgybID74AgC12dyntibIwcm7vJqMLmCVkxRaeWYAZhkZa00fJOD8YI3lSS
A9jUdmlUkSZ5IobJJNhjRfuCNHUETrtuxG5t5KtFuCP2eTgvEKvNwuQM0rbPMZfn
jSP3RdYUqNpThYC2aHw90hyMSvqzLJWwAX5aysbhdOdgkKNAj30iGMRqtLYJTP1G
3Ur1JGJ6GVfgOwmCAMyVMOvY6JqI7tCbC/NirqMrIacLoVlmTffJGO79pBv9WmLc
UO0AxqQ6Ck80OrbXvvm2TVHKVMDiMThbl0Pg5pMBdtXhIpFZVUA0JABuHtwIILmz
qshiX5KcWKooGffhRn9zPt38bAGNcXGqtgX8q9ntpfviioLQg9agt1+fgd1DY+yM
sQF5x77gF8zNyeFtlnHjqI3kSfbd2ADMDHa5pI5cPvpCQBKgkUly260Oovcvqq9T
AlkL/IDIgubYt4r3GHISqSIWwDPyJVXOlNmroSBR6+uKn3iUP0g0XQ/Nd5LskQ9b
Fn2kyXL1k0Vrysy7lToE+3Oe1QECsGUk0elOrKhJXjVZFqHJfG0w4DRBu8ZBY4me
fUHm0HUVaGDppamc
=CE46
-END PGP SIGNATURE End Message ---

Bug#936563: marked as done (frozen-flask: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 20:44:52 +
with message-id 
and subject line Bug#936563: fixed in frozen-flask 0.11-3.1
has caused the Debian Bug report #936563,
regarding frozen-flask: 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.)


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

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: frozen-flask
Source-Version: 0.11-3.1

We believe that the bug you reported is fixed in the latest version of
frozen-flask, 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 frozen-flask 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, 06 Oct 2019 15:43:03 -0400
Source: frozen-flask
Architecture: source
Version: 0.11-3.1
Distribution: unstable
Urgency: medium
Maintainer: Orestis Ioannou 
Changed-By: Sandro Tosi 
Closes: 936563
Changes:
 frozen-flask (0.11-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #936563
Checksums-Sha1:
 084c8e031968714687328ddcbe2f62b3df57eda8 1947 frozen-flask_0.11-3.1.dsc
 26670a708296c2fc47badcb1bd80f6edf94cb87a 2460 
frozen-flask_0.11-3.1.debian.tar.xz
 e81a65e78a4c21b56a9bb978bd27c01dc04c579a 6421 
frozen-flask_0.11-3.1_source.buildinfo
Checksums-Sha256:
 8ddfdfa5ce7a2871456a241a2aef2572fd5a68da30c8a2c08d094ed96c81c95b 1947 
frozen-flask_0.11-3.1.dsc
 b0fa69e3d0b3f4fdf18fca6aad54212661996ba83f3bed50ebef30c7e0b4 2460 
frozen-flask_0.11-3.1.debian.tar.xz
 a7ec3ebe61aa57bebdd1e120b5bf1348e7be12cd0567c94164a0dd21e62cfeff 6421 
frozen-flask_0.11-3.1_source.buildinfo
Files:
 

Bug#936331: marked as done (construct.legacy: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 20:40:15 +
with message-id 
and subject line Bug#936331: fixed in construct.legacy 2.5.3-2.1
has caused the Debian Bug report #936331,
regarding construct.legacy: 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.)


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

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: construct.legacy
Source-Version: 2.5.3-2.1

We believe that the bug you reported is fixed in the latest version of
construct.legacy, 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 construct.legacy 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, 06 Oct 2019 14:38:10 -0400
Source: construct.legacy
Architecture: source
Version: 2.5.3-2.1
Distribution: unstable
Urgency: medium
Maintainer: Hilko Bengen 
Changed-By: Sandro Tosi 
Closes: 936331
Changes:
 construct.legacy (2.5.3-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #936331
Checksums-Sha1:
 a6a4f901e6a2ce71e1b15574e15dffe5785e04de 2021 construct.legacy_2.5.3-2.1.dsc
 15d4db39ed5b4f556ce57fcf288eebb80c56c063 2240 
construct.legacy_2.5.3-2.1.debian.tar.xz
 b46434db57a65527444a411bcc73dc05982de16d 6216 
construct.legacy_2.5.3-2.1_source.buildinfo
Checksums-Sha256:
 116091812c7770805b72a0f91ecb309f31419149380b3bf4418f4fb3647c0daf 2021 
construct.legacy_2.5.3-2.1.dsc
 a6671611cea3803c1dd44a25d3c4eb58c61eaea8ebb9ed883374ebdb3d04de6f 2240 
construct.legacy_2.5.3-2.1.debian.tar.xz
 5f8f4cbe9b74a3a8eee3116e09203f4fa336f3d996bd382c3038a8e14fbd6e05 6216 

Bug#927502: marked as done (Updating the lvmcfg Uploaders list)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:50:14 +
with message-id 
and subject line Bug#927502: fixed in lvmcfg 1.51
has caused the Debian Bug report #927502,
regarding Updating the lvmcfg Uploaders list
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.)


-- 
927502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lvmcfg
Version: 1.50
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the lvmcfg package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.
--- End Message ---
--- Begin Message ---
Source: lvmcfg
Source-Version: 1.51

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

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

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

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated lvmcfg 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, 13 Oct 2019 21:26:08 +0200
Source: lvmcfg
Architecture: source
Version: 1.51
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 927502
Changes:
 lvmcfg (1.51) unstable; urgency=medium
 .
   * Team upload
 .
   [ Cyril Brulebois ]
   * Remove Christian Perrier from Uploaders, with many thanks for all
 his contributions over the years! (Closes: #927502)
 .
   [ Holger Wansing ]
   * Add comment for translators, to keep main menu entry below a 55 columns
 limit. This updates all po|pot files.
   * Update URL to package source from ftp to http, to fix lintian tag.
 .
   [ Updated translations ]
   * Croatian (hr.po) by gogogogi
   * Portuguese (pt.po) by Miguel Figueiredo
Checksums-Sha1:
 6bc80badfd1da828a1bc9f3a23d643f5ecaaa31d 1676 lvmcfg_1.51.dsc
 df71406a704fa5136933afd1a6322856cee2b241 156584 lvmcfg_1.51.tar.xz
 bbbdf17a0e300ca0d3b0cfa040803f77358e7965 5656 lvmcfg_1.51_amd64.buildinfo
Checksums-Sha256:
 b718f9c7391832484da7688269b65284046371269ee1d7e2db62f380b7752985 1676 
lvmcfg_1.51.dsc
 6436a55aca0aca12266f2dda5833e45115cc2290e5f8377be1437b8b63b22516 156584 
lvmcfg_1.51.tar.xz
 1f73920ba85d1fd9a74be4eab00c4a76952d983e179bcc36b676fcadf1d0ec48 5656 
lvmcfg_1.51_amd64.buildinfo
Files:
 0536218b58873d480ec854d87d8c5f89 1676 debian-installer optional lvmcfg_1.51.dsc
 4318d68b2448d8b6cce93f2f177a68a6 156584 debian-installer optional 
lvmcfg_1.51.tar.xz
 63b24b5d0eb310155c0c161adde519ce 5656 debian-installer optional 
lvmcfg_1.51_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAl2jfDYVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2mOUP/jVoW6PsaDT+wDigK3naW+t+8f3F
F8D8l2mY21BVz25tOFYbkSlMjnRp0PqnjLdBD024ubOnKySXYwEAbdqLMvv5B00j
UzRHpgdsBkw5XiVXAZXSlCstZNBpu4OlNk7/AhxIQBJfSprYdahXcAUNONRP7CIz
FgMv4OJzuXHk9lQAGUb5x+ZI+Mr/qhuYNU1oyyBM3Ktv7j6hfJyEPwYiP2U9LMhh
3eN/uetQfxD7mt9GjIPD2Y5UwK2iNg0nq86cXQgMAlBsXJWkE2a9NQgbruP6KmCk
6gKRLAhcsO606qsORrO/p39yzHRXQGJzLCY4sH5slkWeyD4+a9nwpEi/tQER49QN
3PEqdK52g8Y3nX2cgnwv7Cmh4DhWBsUPCZsBF7TiG3KCQvuSoEAm35K2Fid4F2+d
eZhbroARyLRT+pXYhbVWCFgItmRYsTK30DrvHvGybtbwbx+e36OEhW66E+2Wq3Af
hdDhOL+6Xv90cqcJhFQioQL+j5Sem2iF4FDyYSn91xV+WxJSFyTLSTXDpj21T+N1
naIMh/C4x0VelKIe2no38AIuz8bcKOXuFcIxn4vzxXa4YVUA0jaLzfgNv0QmQu2F
MmFiR99fq6bsBIBEer0gduMlaIGtROalsgr5F7XUWM4TNpl9TpZ9vl42V356fSdc
FbLE3iLpdMOF0t38
=zWjT
-END PGP SIGNATURE End Message ---

Bug#934519: marked as done (fence-agents: FTBFS in stretch/buster/sid (ImportError: No module named pywsman))

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:47:32 +
with message-id 
and subject line Bug#934519: fixed in fence-agents 4.0.25-1+deb9u2
has caused the Debian Bug report #934519,
regarding fence-agents: FTBFS in stretch/buster/sid (ImportError: No module 
named pywsman)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --with python2 --with autoreconf
   dh_testdir -a
   dh_update_autotools_config -a
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf ./autogen.sh
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal -I make -I m4
configure.ac:70: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2601: _AC_COMPILE_IFELSE is expanded from...
../../lib/autoconf/general.m4:2617: AC_COMPILE_IFELSE is expanded from...

[... snipped ...]

xsltproc ../../fence/agents/lib/fence2wiki.xsl apc_snmp/.fence_apc_snmp.8.tmp | 
grep -v ' apc_snmp/fence_apc_snmp.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python ifmib/fence_ifmib -o metadata > 
ifmib/.fence_ifmib.8.tmp && \
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
ifmib/.fence_ifmib.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl ifmib/.fence_ifmib.8.tmp > 
ifmib/fence_ifmib.8
ifmib/.fence_ifmib.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl ifmib/.fence_ifmib.8.tmp | grep 
-v ' ifmib/fence_ifmib.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python ibmblade/fence_ibmblade -o metadata > 
ibmblade/.fence_ibmblade.8.tmp && \
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
ibmblade/.fence_ibmblade.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl ibmblade/.fence_ibmblade.8.tmp > 
ibmblade/fence_ibmblade.8
ibmblade/.fence_ibmblade.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl ibmblade/.fence_ibmblade.8.tmp | 
grep -v ' ibmblade/fence_ibmblade.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python bladecenter/fence_bladecenter -o metadata > 
bladecenter/.fence_bladecenter.8.tmp && \
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
bladecenter/.fence_bladecenter.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl 
bladecenter/.fence_bladecenter.8.tmp > bladecenter/fence_bladecenter.8
bladecenter/.fence_bladecenter.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl 
bladecenter/.fence_bladecenter.8.tmp | grep -v ' 
bladecenter/fence_bladecenter.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python rhevm/fence_rhevm -o metadata > 
rhevm/.fence_rhevm.8.tmp && \
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
rhevm/.fence_rhevm.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl rhevm/.fence_rhevm.8.tmp > 
rhevm/fence_rhevm.8
rhevm/.fence_rhevm.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl rhevm/.fence_rhevm.8.tmp | grep 
-v ' rhevm/fence_rhevm.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python ilo/fence_ilo -o metadata > ilo/.fence_ilo.8.tmp && \
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
ilo/.fence_ilo.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl ilo/.fence_ilo.8.tmp > 
ilo/fence_ilo.8
ilo/.fence_ilo.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl ilo/.fence_ilo.8.tmp | grep -v 
' ilo/fence_ilo.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python alom/fence_alom -o metadata > alom/.fence_alom.8.tmp && 
\
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
alom/.fence_alom.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl alom/.fence_alom.8.tmp > 
alom/fence_alom.8
alom/.fence_alom.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl alom/.fence_alom.8.tmp | 

Bug#940547: marked as done (python-cryptography: Testsuite fails with OpenSSL 1.1.1d)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:47:34 +
with message-id 
and subject line Bug#940547: fixed in python-cryptography 1.7.1-3+deb9u2
has caused the Debian Bug report #940547,
regarding python-cryptography: Testsuite fails with OpenSSL 1.1.1d
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.)


-- 
940547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-cryptography
Version: 2.6.1-3
Severity: serious

The upload of latest openssl 1.1.1d triggert three testsuite failures in
python-cryptography [0]

- _ test_buffer_protocol_alternate_modes[mode5] 
__

|mode = 
|backend = 
|
|@pytest.mark.parametrize(
|"mode",
|[
|modes.CBC(bytearray(b"\x00" * 16)),
|modes.CTR(bytearray(b"\x00" * 16)),
|modes.OFB(bytearray(b"\x00" * 16)),
|modes.CFB(bytearray(b"\x00" * 16)),
|modes.CFB8(bytearray(b"\x00" * 16)),
|modes.XTS(bytearray(b"\x00" * 16)),
|]
|)
|@pytest.mark.requires_backend_interface(interface=CipherBackend)
|def test_buffer_protocol_alternate_modes(mode, backend):
|data = bytearray(b"sixteen_byte_msg")
|cipher = base.Cipher(
|algorithms.AES(bytearray(b"\x00" * 32)), mode, backend
|)
|>   enc = cipher.encryptor()
|
|tests/hazmat/primitives/test_aes.py:495: 
|_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
|/usr/lib/python2.7/dist-packages/cryptography/hazmat/primitives/ciphers/base.py:121:
 in encryptor
|self.algorithm, self.mode
|/usr/lib/python2.7/dist-packages/cryptography/hazmat/backends/openssl/backend.py:295:
 in create_symmetric_encryption_ctx
|return _CipherContext(self, cipher, mode, _CipherContext._ENCRYPT)
|/usr/lib/python2.7/dist-packages/cryptography/hazmat/backends/openssl/ciphers.py:116:
 in __init__
|self._backend.openssl_assert(res != 0)
|/usr/lib/python2.7/dist-packages/cryptography/hazmat/backends/openssl/backend.py:125:
 in openssl_assert
|return binding._openssl_assert(self._lib, ok)

This is due to commit 2a5f63c9a61be ("Allow AES XTS decryption using duplicate
keys.").
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2a5f63c9a61be

- _ TestDH.test_dh_parameters_supported 
__

|self = 
|backend = 
|
|def test_dh_parameters_supported(self, backend):
|assert backend.dh_parameters_supported(23, 5)
|>   assert not backend.dh_parameters_supported(23, 18)
|E   assert not True
|E+  where True = >(23, 18)
|E+where > = .dh_parameters_supported
|
|tests/hazmat/primitives/test_dh.py:161: AssertionError

This is due to commit ddd16c2fe988e ("Change DH parameters to generate the
order q subgroup instead of 2q").
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=ddd16c2fe988e

- _ TestECDSACertificate.test_load_ecdsa_no_named_curve 
__

|self = 
|backend = 
|
|def test_load_ecdsa_no_named_curve(self, backend):
|_skip_curve_unsupported(backend, ec.SECP256R1())
|cert = _load_cert(
|os.path.join("x509", "custom", "ec_no_named_curve.pem"),
|x509.load_pem_x509_certificate,
|backend
|)
|with pytest.raises(NotImplementedError):
|>   cert.public_key()
|E   Failed: DID NOT RAISE 
|
|tests/x509/test_x509.py:3722: Failed

This is due to commit 9a43a733801bd ("[ec] Match built-in curves on
EC_GROUP_new_from_ecparameters").
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9a43a733801bd


The first two changes in OpenSSL have been made on purporse and I'm not
sure about the last one.
Could someone please comment?

[0] 
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-cryptography/2969575/log.gz

Sebastian
--- End Message ---
--- Begin Message ---
Source: python-cryptography
Source-Version: 1.7.1-3+deb9u2

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

Debian distribution maintenance software
pp.
Sebastian Andrzej Siewior  (supplier of updated 
python-cryptography package)

(This message was 

Bug#936589: marked as done (gconf: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:34:47 +
with message-id 
and subject line Bug#936589: fixed in gconf 3.2.6-6
has caused the Debian Bug report #936589,
regarding gconf: 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.)


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

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: gconf
Source-Version: 3.2.6-6

We believe that the bug you reported is fixed in the latest version of
gconf, 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.
Adrian Bunk  (supplier of updated gconf 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, 13 Oct 2019 21:41:05 +0300
Source: gconf
Architecture: source
Version: 3.2.6-6
Distribution: unstable
Urgency: medium
Maintainer: Adrian Bunk 
Changed-By: Adrian Bunk 
Closes: 935801 936589 941487
Changes:
 gconf (3.2.6-6) unstable; urgency=medium
 .
   * Add patch from Iain Lane for GLib 2.62 deprecations
 in gconf-value.h. (Closes: #935801, #941487)
   * Add Python 3 changes from Ubuntu. (Closes: #936589)
   * Add patch from Chow Loong Jin to initialize dbus threads before
 doing anything. This fixes crashes in multithreaded applications
 that don't use libdbus directly. (LP: #1048341)
Checksums-Sha1:
 66d3cb20ffd9acf1c55c2a2a50d1f9586c4928f2 2641 gconf_3.2.6-6.dsc
 1531a460d43f6396ef9a15833c98d456d257f207 30276 gconf_3.2.6-6.debian.tar.xz
Checksums-Sha256:
 692527c66299e07d408321cb01c847cfc09ebc736f90bcd30c0b92e16be416b0 2641 
gconf_3.2.6-6.dsc
 45e0b6452f7c84b96af978f3f89be49a894e7557ba69dc3f8987d78212527354 30276 
gconf_3.2.6-6.debian.tar.xz
Files:
 

Bug#941487: marked as done (gconf: autopkgtest fails with libglib2.0-0 (>= 2.62))

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:34:47 +
with message-id 
and subject line Bug#941487: fixed in gconf 3.2.6-6
has caused the Debian Bug report #941487,
regarding gconf: autopkgtest fails with libglib2.0-0 (>= 2.62)
to be marked as done.

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

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


-- 
941487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gconf
Version: 3.2.6-5
Severity: serious
Justification: https://release.debian.org/bullseye/rc_policy.txt §6a
Tags: patch
Forwarded: https://gitlab.gnome.org/Archive/gconf/merge_requests/1

With the recent upload of GLib 2.62 to unstable, gconf's autopkgtest has
started failing:

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gconf/3045304/log.gz
> /usr/include/gconf/2/gconf/gconf-value.h:139:3: error: ‘GTime’ is deprecated: 
> Use 'GDateTime' instead [-Werror=deprecated-declarations]
>   139 |   GTime  mod_time; /* time of the modification */
>   |   ^
> /usr/include/gconf/2/gconf/gconf-value.h:144:1: error: ‘GTime’ is deprecated: 
> Use 'GDateTime' instead [-Werror=deprecated-declarations]
>   144 | GTime   gconf_meta_info_mod_time (GConfMetaInfo *gcmi);
>   | ^
> /usr/include/gconf/2/gconf/gconf-value.h:153:46: error: ‘GTime’ is 
> deprecated: Use 'GDateTime' instead [-Werror=deprecated-declarations]
>   153 |  GTime  mod_time);
>   |  ^
> cc1: all warnings being treated as errors

GTime is a gint32 (not a time_t, although it happens to be equivalent on
older 32-bit architectures) counting seconds since the beginning of 1970.
As such it is not Y2038-safe.

The deprecation warnings can be disabled for code that depends on
gconf by wrapping a block with the G_GNUC_BEGIN_IGNORE_DEPRECATIONS
and G_GNUC_END_IGNORE_DEPRECATIONS macros, as was done in Ubuntu patch
3.2.6-5ubuntu3: https://gitlab.gnome.org/Archive/gconf/merge_requests/1

Regards,
smcv
--- End Message ---
--- Begin Message ---
Source: gconf
Source-Version: 3.2.6-6

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated gconf 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, 13 Oct 2019 21:41:05 +0300
Source: gconf
Architecture: source
Version: 3.2.6-6
Distribution: unstable
Urgency: medium
Maintainer: Adrian Bunk 
Changed-By: Adrian Bunk 
Closes: 935801 936589 941487
Changes:
 gconf (3.2.6-6) unstable; urgency=medium
 .
   * Add patch from Iain Lane for GLib 2.62 deprecations
 in gconf-value.h. (Closes: #935801, #941487)
   * Add Python 3 changes from Ubuntu. (Closes: #936589)
   * Add patch from Chow Loong Jin to initialize dbus threads before
 doing anything. This fixes crashes in multithreaded applications
 that don't use libdbus directly. (LP: #1048341)
Checksums-Sha1:
 66d3cb20ffd9acf1c55c2a2a50d1f9586c4928f2 2641 gconf_3.2.6-6.dsc
 1531a460d43f6396ef9a15833c98d456d257f207 30276 gconf_3.2.6-6.debian.tar.xz
Checksums-Sha256:
 692527c66299e07d408321cb01c847cfc09ebc736f90bcd30c0b92e16be416b0 2641 
gconf_3.2.6-6.dsc
 45e0b6452f7c84b96af978f3f89be49a894e7557ba69dc3f8987d78212527354 30276 
gconf_3.2.6-6.debian.tar.xz
Files:
 22caa60dbcf00eec83188d9e971ddb74 2641 libs optional gconf_3.2.6-6.dsc
 4dac0dc8c4b5daae327edc84075c2406 30276 libs optional 
gconf_3.2.6-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl2jdxoACgkQiNJCh6LY
mLGD8hAAsLqcMmS0YjsJEurLOvRaGxAnjjvxUiXGRRZKJubioGXg3sY2K/RLTCKD
2ahEcxZf7IxYsfAnpsLjRbEuTeUSpuX8Zk7SQlgM6YzwuCr4pbkVBKyUh/3Y+4zt
xlEZKTEwKzkKfMJkzMBcsuuMI4WKBFvgeAcTHtHUELvXFRi1akIKSqwRcpg6SLGx
+m9PpVxcGq+7gARhv8t29zdBlYoUL6e95zH5eCckLVElCWxLGQwo7v9h3afQqKO/
Zg8iO4GuLXt+Xw3hRJfgvxYD70AeDOfMD6g5ptPvh+JIXIyHHSOq8X7wXT2sttms
SlSe72g2vLhleYVtPxlnHxYnRC68cIUejvOxjj2KRH1lsF7QttX7Ejahn9b7O90c
Qki6RLxehm/hzQhzXCL0u0S+6Y1NFbZ52ajK8xsCvPjOjIEUnZbm7zAiLxN6fHnj

Bug#935801: marked as done (Deprecated types in exported API as of GLib 2.62)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:34:47 +
with message-id 
and subject line Bug#935801: fixed in gconf 3.2.6-6
has caused the Debian Bug report #935801,
regarding Deprecated types in exported API as of GLib 2.62
to be marked as done.

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

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


-- 
935801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgconf2-dev
Version: 3.2.6-5ubuntu1
Severity: normal
Tags: patch upstream
Control: forwarded -1 https://gitlab.gnome.org/Archive/gconf/merge_requests/1

Hi there,

gconf's headers contains functions which refer to types that are
deprecated in GLib 2.62. For example, gconf's autopkgtest starts failing
due to this:

autopkgtest [13:41:39]: test build: [---
In file included from /usr/include/gconf/2/gconf/gconf-schema.h:26,
 from /usr/include/gconf/2/gconf/gconf.h:27,
 from /usr/include/gconf/2/gconf/gconf-client.h:25,
 from build_test.c:1:
/usr/include/gconf/2/gconf/gconf-value.h:139:3: error: ‘GTime’ is deprecated: 
Use 'GDateTime' instead [-Werror=deprecated-declarations]
  139 |   GTime  mod_time; /* time of the modification */
  |   ^
/usr/include/gconf/2/gconf/gconf-value.h:144:1: error: ‘GTime’ is deprecated: 
Use 'GDateTime' instead [-Werror=deprecated-declarations]
  144 | GTime   gconf_meta_info_mod_time (GConfMetaInfo *gcmi);
  | ^
/usr/include/gconf/2/gconf/gconf-value.h:153:46: error: ‘GTime’ is deprecated: 
Use 'GDateTime' instead [-Werror=deprecated-declarations]
  153 |  GTime  mod_time);
  |  ^
cc1: all warnings being treated as errors
autopkgtest [13:41:40]: test build: ---]
autopkgtest [13:41:40]: test build:  - - - - - - - - - - results - - - - - - - 
- - -
buildFAIL non-zero exit status 1

(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/arm64/g/gconf/20190825_134153_ffcc3@/log.gz)

I wrote a patch to turn off these warnings - since it's not really
possible to fix as that would be an API break - and forwarded it
upstream. I was about to upload to Debian and then I noticed that gconf
isn't pkg-gnome any more.

  
https://gitlab.gnome.org/iainl/gconf/commit/6b97432b90c595ed799dce681101748568ae7f20

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]
--- End Message ---
--- Begin Message ---
Source: gconf
Source-Version: 3.2.6-6

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated gconf 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, 13 Oct 2019 21:41:05 +0300
Source: gconf
Architecture: source
Version: 3.2.6-6
Distribution: unstable
Urgency: medium
Maintainer: Adrian Bunk 
Changed-By: Adrian Bunk 
Closes: 935801 936589 941487
Changes:
 gconf (3.2.6-6) unstable; urgency=medium
 .
   * Add patch from Iain Lane for GLib 2.62 deprecations
 in gconf-value.h. (Closes: #935801, #941487)
   * Add Python 3 changes from Ubuntu. (Closes: #936589)
   * Add patch from Chow Loong Jin to initialize dbus threads before
 doing anything. This fixes crashes in multithreaded applications
 that don't use libdbus directly. (LP: #1048341)
Checksums-Sha1:
 66d3cb20ffd9acf1c55c2a2a50d1f9586c4928f2 2641 gconf_3.2.6-6.dsc
 1531a460d43f6396ef9a15833c98d456d257f207 30276 gconf_3.2.6-6.debian.tar.xz
Checksums-Sha256:
 692527c66299e07d408321cb01c847cfc09ebc736f90bcd30c0b92e16be416b0 2641 
gconf_3.2.6-6.dsc
 45e0b6452f7c84b96af978f3f89be49a894e7557ba69dc3f8987d78212527354 30276 
gconf_3.2.6-6.debian.tar.xz
Files:
 22caa60dbcf00eec83188d9e971ddb74 2641 libs optional 

Bug#941411: marked as done (shelldap: sometimes falls back to simple auth when it should do sasl)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:36:09 +
with message-id 
and subject line Bug#941411: fixed in shelldap 1.5.1-1
has caused the Debian Bug report #941411,
regarding shelldap: sometimes falls back to simple auth when it should do sasl
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.)


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

Hello,

when calling shelldap repeatedly it sometimes fails for me and sometimes
succeeds in entering the shell:

user@host:~# shelldap
LDAP bind error: No password, did you mean noauth or anonymous ?
user@host:~# shelldap
~ >

The problem is that in /usr/share/perl5/Net/LDAP.pm in the bind() method
the iteration through %ptype happens in different orderings. If

password => simple

is hit first it dies with the above error message. If however 

sasl => sasl

is tried first, it succeeds.

The following patch makes it work for me:

diff --git a/shelldap b/shelldap
index 68dde20cc8de..5a18f23799f0 100755
--- a/shelldap
+++ b/shelldap
@@ -770,7 +770,6 @@ You may try connecting insecurely, or install the module 
and try again.\n} if $@
#
if ( $sasl_conn ) {
$rv = $ldap->bind( $conf->{'binddn'},
-   password => $conf->{'bindpass'},
sasl => $sasl_conn
);
}

I *think* you never need a password when using sasl, but I'm not 100%
confident, so I'm not tagging with "patch". I didn't try with shelldap
1.5.0-2 from sid, but there also both sasl and password are passed, so I
expect the problem to still exist there.

Best regards
Uwe

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

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

Versions of packages shelldap depends on:
ii  libalgorithm-diff-perl 1.19.03-2
ii  libnet-ldap-perl   1:0.6500+dfsg-1
ii  libterm-readkey-perl   2.38-1
ii  libterm-readline-gnu-perl  1.36-1
ii  libterm-shell-perl 0.10-1
ii  libyaml-syck-perl  1.31-1+b1
ii  perl   5.28.1-6

Versions of packages shelldap recommends:
pn  libio-socket-ssl-perl  

Versions of packages shelldap suggests:
ii  libauthen-sasl-perl  2.1600-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: shelldap
Source-Version: 1.5.1-1

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

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

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated shelldap 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, 13 Oct 2019 21:20:43 +0200
Source: shelldap
Architecture: source
Version: 1.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Salvatore Bonaccorso 
Changed-By: Salvatore Bonaccorso 
Closes: 941411
Changes:
 shelldap (1.5.1-1) unstable; urgency=medium
 .
   * debian/watch: Switch to fetch releases from github
   * New upstream version 1.5.1
 - Repair SASL authentications, add a 'sasluser' option (Closes: #941411)
   * Declare compliance with Debian policy 4.4.1
Checksums-Sha1: 
 5c652a12af9072a6513074567952484a1360fb85 2031 shelldap_1.5.1-1.dsc
 4028da788c01a669ae4a65ed016fada8438635b2 23996 shelldap_1.5.1.orig.tar.xz
 299c415d10e4c3f0c4a07bb82b20e85abb782781 5124 shelldap_1.5.1-1.debian.tar.xz
Checksums-Sha256: 
 f1266cfe42c605bb82ef7c44fc12151293072d7fbb488e5617407ffd7c0f969e 2031 
shelldap_1.5.1-1.dsc
 57d2a58119a4f1c2086d6e90060ef8e51e9ba6703b9689629e7f050fa4341d05 23996 
shelldap_1.5.1.orig.tar.xz
 206fa4c63497fcd54793c8560b08a3487af8b14029579386c37e1840600c194d 5124 
shelldap_1.5.1-1.debian.tar.xz
Files: 
 

Bug#927541: marked as done (Updating the lilo-installer Uploaders list)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:35:52 +
with message-id 
and subject line Bug#927541: fixed in lilo-installer 1.61
has caused the Debian Bug report #927541,
regarding Updating the lilo-installer Uploaders list
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.)


-- 
927541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lilo-installer
Version: 1.60
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Christian Perrier  has retired, so can't work on
the lilo-installer package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.
--- End Message ---
--- Begin Message ---
Source: lilo-installer
Source-Version: 1.61

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

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

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

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated lilo-installer 
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, 13 Oct 2019 21:01:01 +0200
Source: lilo-installer
Architecture: source
Version: 1.61
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 927541
Changes:
 lilo-installer (1.61) unstable; urgency=medium
 .
   [ Cyril Brulebois ]
   * Remove Christian Perrier from Uploaders, with many thanks for all
 his contributions over the years! (Closes: #927541)
 .
   [ Holger Wansing ]
   * Add comment for translators, to keep main menu entry below a 55 columns
 limit. This updates all po|pot files.
 .
   [ Updated translations ]
   * Croatian (hr.po) by gogogogi
Checksums-Sha1:
 71c3648e85828d147013608f882b2e293a6c40bc 1686 lilo-installer_1.61.dsc
 c9b863980c75b59dd369fd6ecbd0f37effaf1077 101684 lilo-installer_1.61.tar.xz
 fe3d258241b6de74b1bb944ea9a5432ec32e8667 5490 
lilo-installer_1.61_amd64.buildinfo
Checksums-Sha256:
 73d49139ec994a080b599c388054937432cd15803f7d47b753c411760c96a56d 1686 
lilo-installer_1.61.dsc
 91d873ba6eb46ed7b44328f15a559b71a5a42226efa078bac82c1c85f86d2336 101684 
lilo-installer_1.61.tar.xz
 086ff2977d1fccd68184fa961700a990fed66b0bcc8eee5eee370ddbc4f3adc2 5490 
lilo-installer_1.61_amd64.buildinfo
Files:
 0bd24b03b98c203bdf542a93b7d410de 1686 debian-installer standard 
lilo-installer_1.61.dsc
 0179267df41860f096a4d05dbd6c8553 101684 debian-installer standard 
lilo-installer_1.61.tar.xz
 2ce087b1015a7b370a1519771b8a9823 5490 debian-installer standard 
lilo-installer_1.61_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAl2jeGAVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2IPEQALIKxb7CBbjiieCPalbP9UJK0fZV
kzS8HnWAKaIPtCv+HVhpIuY+viOenABVqWnn4qQyB3ZQchFiSN1H66PZoPyWsj7X
A8YY28rX+8snTrtBtbtwIsZZ2Hs/u7AcIquBVE+mwF3ZmzJDHj9M6E1gTiQJpLRC
2jcc7hMwRsacXK4XNQjCB/Tw5P8zw84iQwunF+BwPEGTW++fIlCwIv0U8E2zC3IL
cmFAsF2t11wBQtcU4ThNqrHI2bHq0dlRtynFeFS2h/6h0tW8TP0PWB2IAMoc7Hdy
A3D+hcw0AI0qUXue0sIeEO+DIpLZH0sFy/ybWC5DX8XSZVHVYIWdW+JJ4R4qecUp
F8xe2lDF8FdK+e6IVFXXCRGonfYjIcEi4mt9dcy9cDb4ECUL7lxfPSfJ/h6Kufk+
EcySoQg80zmLqiNI9eEr8PJDQZbBunLWxSTeild6m+4DP0v6sIcX0Rqhh8duViDB
1Jicm+TWc6BAWL18ZKmZvgVHOcYGx5xn2RVqEvbX4OVNBYG+N6wSuG6KYlI8uKu+
c5Wugj2MmwuH83L4f9lbQFQ29hAoS4JbQ38rpl9aH2gH7jjr9kgw2resfxNmJTDz
JsbzlSoTyYXjt5NdUDYNJna7uTYAEMz4DjzRwstmbIZs0FE1lYVHxGfRjfcRghoy
gd62jEAACscCysi2
=UgEM
-END PGP SIGNATURE End Message ---

Bug#921278: marked as done (bibtex2html: Lacks several math-related translations)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:34:36 +
with message-id 
and subject line Bug#921278: fixed in bibtex2html 1.99-3
has caused the Debian Bug report #921278,
regarding bibtex2html: Lacks several math-related translations
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.)


-- 
921278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921278
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bibtex2html
Version: 1.99-2.1
Severity: wishlist
Tags: patch

Dear Maintainer,


I maintain several large bibtex files, including one devoted to
numerical analysis papers, with abstracts that use a lot of math
notation.  I have collected some of the required translations
into a latex macro file that I can load with the -m switch.
However, it would be more convenient to have those translations
built into bibtex2html tool.

I'm proposing four kinds of additions:

 - bibtex2html already had a translation for \log.  I've added
   translations for all 32 of the math functions on p. 162 of the
   TeXbook.

 - I added single-character translations for \lbrace, \rbrace,
   and \over.

 - There were already translations for \sum, \int, and \prod that
   used HTML entities.  I've added translations using
   Unicode.  (Note that there were already translations for "--"
   and "---" to both HTML entities and Unicode, presumably for
   situations where one was acceptable but the other was not, so
   I'm following the same convention.)

 - I added both Unicode and HTML translations for \ell, \ll,
   \gg,\langle, and \rangle.

I'm attaching a patch to make those additions for Debian.  It
would be even better to get them accepted upstream.

 - Jim Van Zandt


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

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

Versions of packages bibtex2html depends on:
ii  ocaml-base-nox [ocaml-base-nox-4.05.0]  4.05.0-11
ii  perl5.28.1-3
ii  texlive-base2018.20190131-1

bibtex2html recommends no packages.

Versions of packages bibtex2html suggests:
pn  hlins  


more-translations
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: bibtex2html
Source-Version: 1.99-3

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

Debian distribution maintenance software
pp.
Ralf Treinen  (supplier of updated bibtex2html 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, 13 Oct 2019 12:14:52 +0200
Source: bibtex2html
Architecture: source
Version: 1.99-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Ralf Treinen 
Closes: 921278 921593
Changes:
 bibtex2html (1.99-3) unstable; urgency=medium
 .
   * Make this an architecture-dependent package:
 - set Architecture=any
 - fix patch charset, to use the unix module also for compilation to
   native code.
 - debian/rules: auto_build override conditional on whether this is an
   ocaml native architecture or not
 - debian/rules: auto_test override conditional on whether this is an
   ocaml native architecture or not
 - Depends: add {shlibs:Depends}
   * debian/ruies : drop override of dh_auto_install: we don't need it anymore
 since the upstream Makefile does the right thing for native and bytecode
 architectures.
   * debian/rules: drop override of dh_strip which is no longer needed.
   * Apply patch by James Van Zandt that adds many translations of
 math-related symbols. Thanks a lot for the patch! (closes: #921278)
   * Apply patch by James Van Zandt that adds translations of
 accentuated characters. Thanks a 

Bug#921593: marked as done (bibtex2html should transate math characters with overhead accents)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:34:36 +
with message-id 
and subject line Bug#921593: fixed in bibtex2html 1.99-3
has caused the Debian Bug report #921593,
regarding bibtex2html should transate math characters with overhead accents
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.)


-- 
921593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bibtex2html
Version: 1.99-2.1
Severity: wishlist
Tags: upstream

Dear Maintainer,

I wish bibtex2html could translate math characters that have accents.

In my .bib collection, I have a few abstracts with math characters
that have accents.  One such document is at
http://arxiv.org/pdf/1508.04874v1.pdf.  Here's a sample .bib entry for
it, with an abridged abstract:

@Misc{   lee-sidford-wong15cutting,
  author = {Yin Tat Lee and Aaron Sidford and Sam Chiu-wai Wong},
  title = {A Faster Cutting Plane Method and its Implications
  for Combinatorial and Convex Optimization},
  eprinttype =   {arxiv},
  eprint =   {1508.04874v1},
  url =  {http://arxiv.org/pdf/1508.04874v1.pdf},
  month = aug,
  year = 2015,
  abstract = {We obtain a running time of $\tilde O ( n ( n^2 +
  m^\omega + S ))$, improving upon the previous best
  of $\tilde O ( n ( n^\omega + m^\omega + S ))$ for
  the regime $S$ is small.},
  pdf =   {lee-sidford-wong15cutting.pdf}
}

Unicode can add bars and such over characters, using characters with
combining class "above".  In TeX, the accent macro precedes the base
character, while the Unicode combining character must follow the base
character.  I think these TeX macro definitions should accomplish the
exchange:

\def\overleftarrow#1{#1⃖}  % over left arrow  U+20d6
\def\overrightarrow#1{#1⃗} % over right arrow U+20d7
\def\bar#1{#1̅}% overbar accent   U+0305
\def\tilde#1{#1̃}  % tilde accent U+0303

However none of these actually work because ``bibtex2html does not
handle macros arguments; arguments are simply discarded.''

I think the translations could be done with ocaml, but I'm not even
sure how to spell that.

Please ask the upstream author(s) to consider implementing translations for
accented math characters.

  - Jim Van Zandt


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

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

Versions of packages bibtex2html depends on:
ii  ocaml-base-nox [ocaml-base-nox-4.05.0]  4.05.0-11
ii  perl5.28.1-4
ii  texlive-base2018.20190131-1

bibtex2html recommends no packages.

Versions of packages bibtex2html suggests:
pn  hlins  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: bibtex2html
Source-Version: 1.99-3

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

Debian distribution maintenance software
pp.
Ralf Treinen  (supplier of updated bibtex2html 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, 13 Oct 2019 12:14:52 +0200
Source: bibtex2html
Architecture: source
Version: 1.99-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Ralf Treinen 
Closes: 921278 921593
Changes:
 bibtex2html (1.99-3) unstable; urgency=medium
 .
   * Make this an architecture-dependent package:
 - set Architecture=any
 - fix patch charset, to use the unix module also for compilation to
   native code.
 - debian/rules: auto_build override conditional on whether this is an
   ocaml native architecture or 

Bug#919891: marked as done (navit: Crash when starting for the first time due to XML)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 21:34:04 +0200
with message-id 
and subject line Re: navit: Crash when starting for the first time due to XML
has caused the Debian Bug report #919891,
regarding navit: Crash when starting for the first time due to XML
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.)


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

Package: navit
Version: 0.5.3+dfsg.1-1
Severity: normal
Tags: upstream

Dear Maintainer,

I try navit for the first time.  I copied the XML file from 
http://wiki.navit-project.org/index.php/Configuration and put it in 
.navit/navit.xml:


  
  





  


I start navit and have a crash:

Reading symbols from navit...(no debugging symbols found)...done.
Attaching to program: /usr/bin/navit, process 5561
Reading symbols from /lib/x86_64-linux-gnu/libpthread.so.0...Reading 
symbols from 
/usr/lib/debug/.build-id/a7/0e1c821fa0b9649d341d929fe875c574a5324b.debug...done.

done.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Reading symbols from /lib/x86_64-linux-gnu/libglib-2.0.so.0...(no 
debugging symbols found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libgmodule-2.0.so.0...(no 
debugging symbols found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libz.so.1...(no debugging 
symbols found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libpng16.so.16...(no 
debugging symbols found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libdl.so.2...Reading symbols 
from 
/usr/lib/debug/.build-id/5f/5bc3aba9c2600e38002c8471fb24e6005fd7c8.debug...done.

done.
Reading symbols from /lib/x86_64-linux-gnu/libm.so.6...Reading symbols 
from 
/usr/lib/debug/.build-id/84/aff20c33f05386e02c8a9d2629b9aa27fce0e8.debug...done.

done.
Reading symbols from /lib/x86_64-linux-gnu/libc.so.6...Reading symbols 
from 
/usr/lib/debug/.build-id/dd/2b8c469f69d0866039fcc75889451baca4e0f1.debug...done.

done.
Reading symbols from /lib64/ld-linux-x86-64.so.2...Reading symbols from 
/usr/lib/debug/.build-id/f6/8476632fe338d209f9536ad0ebe7cfde5b5f28.debug...done.

done.
Reading symbols from /lib/x86_64-linux-gnu/libpcre.so.3...(no debugging 
symbols found)...done.
0x7f6609499757 in __GI___waitpid (pid=5562, 
stat_loc=stat_loc@entry=0x7ffeeaac04c8,

options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:30
30  ../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory.
#0  0x7f6609499757 in __GI___waitpid (pid=5562, 
stat_loc=stat_loc@entry=0x7ffeeaac04c8,

options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:30
#1  0x7f660941781f in do_system (line=) at 
../sysdeps/posix/system.c:149

#2  0x55bcb6897ba0 in ?? ()
#3  
#4  0x55bcb688b3d4 in ?? ()
#5  0x55bcb688b94f in ?? ()
#6  0x55bcb688c3ba in ?? ()
#7  0x7f66099cc5f2 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f66099cd716 in g_markup_parse_context_parse () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0

#9  0x55bcb688bd86 in ?? ()
#10 0x55bcb688df5f in config_load ()
#11 0x55bcb6886016 in main_real ()
#12 0x7f66093f709b in __libc_start_main (main=0x55bcb6885ca0 , 
argc=1,
--Type  for more, q to quit, c to continue without 
paging--argv=0x7ffeeaac21f8, Quit

Detaching from program: /usr/bin/navit, process 5561

Cheers,
Eugen Dedu


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

Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)

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


Versions of packages navit depends on:
ii  libc6   2.28-5
ii  libdbus-1-3 1.12.12-1
ii  libdbus-glib-1-20.110-3
ii  libfontconfig1  2.13.1-2
ii  libfreetype62.9.1-3
ii  libfribidi0 1.0.5-3.1
ii  libgarmin0  0~svn320-6
ii  libglib2.0-02.58.2-4
ii  libgps233.17-5+b1
ii  libpng16-16 1.6.36-3
ii  libspeechd2 0.8.8-9
ii  navit-data  0.5.3+dfsg.1-1
ii  navit-gui-internal  0.5.3+dfsg.1-1
ii  zlib1g  1:1.2.11.dfsg-1

Versions of packages navit recommends:
ii  gpsd  3.17-5+b1

Versions of packages navit suggests:
pn  maptool  

-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, 20 Jan 2019 15:55:58 +0100 Eugen Dedu
 wrote:
> Package: navit
> Version: 

Bug#935210: marked as done (python-nbxmpp: Please port to Python 3 and/or drop Python 2 package)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:20:10 +
with message-id 
and subject line Bug#935210: fixed in python-nbxmpp 0.6.10-1.1
has caused the Debian Bug report #935210,
regarding python-nbxmpp: Please port to Python 3 and/or drop Python 2 package
to be marked as done.

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

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


-- 
935210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-nbxmpp
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Hello, please port python-nbxmpp to Python3 and/or drop the python 2
package. This will help the goal of removing Python 2 from Debian,
and would also (more immediately) allow to remove packages currently
dependencies of this one.

More info at: https://wiki.debian.org/Python/2Removal

Thanks, Sandro 
--- End Message ---
--- Begin Message ---
Source: python-nbxmpp
Source-Version: 0.6.10-1.1

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-nbxmpp 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, 06 Oct 2019 14:33:39 -0400
Source: python-nbxmpp
Architecture: source
Version: 0.6.10-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian XMPP Maintainers 
Changed-By: Sandro Tosi 
Closes: 935210
Changes:
 python-nbxmpp (0.6.10-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #935210
Checksums-Sha1:
 4d2a10a0238a66aa37f4d27418d48befd33ccc2d 2127 python-nbxmpp_0.6.10-1.1.dsc
 fc141309184f0173e7a06ec668f2f5cb936e6fac 5780 
python-nbxmpp_0.6.10-1.1.debian.tar.xz
 0f3d6d64f92aac0e3687bcb5d324a3f413b08461 6212 
python-nbxmpp_0.6.10-1.1_source.buildinfo
Checksums-Sha256:
 900e6cc4521931b7932b898a7147a723bacb86e227124d82374eeef2f52f1792 2127 
python-nbxmpp_0.6.10-1.1.dsc
 72e8c95c19501b1f3b6872076beaec3dc895336d0555ad786eb42ba244bfe1de 5780 
python-nbxmpp_0.6.10-1.1.debian.tar.xz
 fd279d450723200b76d02514dd9673c9194e7a17d6282614e1874e8c706fe1bc 6212 
python-nbxmpp_0.6.10-1.1_source.buildinfo
Files:
 9ae2a4fccf5d0681e55b8035128683ed 2127 python optional 
python-nbxmpp_0.6.10-1.1.dsc
 38e8489d08c6b601e054f8285c9d1a2a 5780 python optional 
python-nbxmpp_0.6.10-1.1.debian.tar.xz
 33b835b7388687ad670be7b8a6fdba0d 6212 python optional 
python-nbxmpp_0.6.10-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl2aM/4ACgkQh588mTgB
qU9JyRAAh4uKFlUmS1X6vqcQOilMuTt5qgaxJZJgtZFAPWzTtCxXIIf8OYr2rwt0
iPpTleigv1qsELzNEe748bqBe6uYluV0ySiuGHcj341ZP64uogE3IYY0GLWUti6E
T+6TmTqSqKf/izutxdqLB/xdQntmKSm6RhA7D7wk+EC2CKqowkUDRToTibcHKADi
zVUaBPHQGeG/ysJ9JJK2Rovs+T3n1ZHaiwG0ACRM+2DugsfqTBjam92D26g0RPDq
iD6VfSPRUhtIWMPEP3r9C85w82/0hmA0EuBuwZrlHUKEIs6q6SdAyTCnRd5y2KE1
M3XtA3siRK70FDhjM3Y3PbBTsJWaNYoVFEts45IhoBBmmgsUylOA+pFcumM6wtux
SR7roErcSqFqBsRfnz9L7BE2ytemenIK5la5gEzdYpJ5UhI3aWWftxOcgBkfHG4L
Az6QoPPUzMYsM+WibGfIYfk5VY7itxvcmZlrGNoN2BaA2Oj/S5O4FUYfVnWD2s/W
l5BZ0+8Ky9ZJG/NamGhxNc4JH8h0LbCGEhfty6OpkFYOs+5n2OCVVCekJIfbfvqD
cKIiQkycmCFGtaN4DO2moRD11g0zDsAe79vP2t7h5R2Q++6/3G5M8CVb46ubs9vS
+F03l/V1l/GEjqRWzyVsc3XA4dFEv4qWqTSm1m649mrybTmy0Rg=
=gMVm
-END PGP SIGNATURE End Message ---

Bug#935492: marked as done (rpcbind: Broadcast requests broken)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:17:23 +
with message-id 
and subject line Bug#939877: fixed in rpcbind 1.2.5-0.3+deb10u1
has caused the Debian Bug report #939877,
regarding rpcbind: Broadcast requests broken
to be marked as done.

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

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


-- 
939877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rpcbind
Version: 1.2.5-0.3
Severity: important

I upgraded my NIS server to buster and found that it stopped
answering requests to NIS clients.  It turns out that rpcbind
no longer responds to broadcast requests coming in on port 111.

This is due to an upstream change:

https://sourceforge.net/p/libtirpc/mailman/message/36377522/

Fortunately it is easy to fix it by enabling it at build time
with --enable-rmtcalls.

Could you please do that and also inform upstream that people
do use this feature?

Thanks,
--
Email: Herbert Xu 
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--- End Message ---
--- Begin Message ---
Source: rpcbind
Source-Version: 1.2.5-0.3+deb10u1

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

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

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

Debian distribution maintenance software
pp.
Josue Ortega  (supplier of updated rpcbind package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 09 Sep 2019 12:19:21 -0600
Source: rpcbind
Architecture: source
Version: 1.2.5-0.3+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Josue Ortega 
Changed-By: Josue Ortega 
Closes: 939877
Changes:
 rpcbind (1.2.5-0.3+deb10u1) buster; urgency=medium
 .
   * Add 00-rmt-calls.patch (Closes: #939877):
 + Add command line option to enable remote calls at runtime
 + Refresh debian/patches
   * debian/control: Update maintainer information
   * Add debian/README.debian explaining remote calls activation for
 Debian systems
   * Add debian/NEWS
Checksums-Sha1:
 e854744d050d76f3f8fbdd74eb92a251d8265995 1851 rpcbind_1.2.5-0.3+deb10u1.dsc
 99e7676ac0df6befdf4408f6bac2b029e355c970 11240 
rpcbind_1.2.5-0.3+deb10u1.debian.tar.xz
 dedc3c21829083670a1f47b6381b23b82c41f8b7 6062 
rpcbind_1.2.5-0.3+deb10u1_amd64.buildinfo
Checksums-Sha256:
 c881586a2b2e56c4985fe1f9a33f17271e43360e2ef8dc5def3f6e725432cf82 1851 
rpcbind_1.2.5-0.3+deb10u1.dsc
 daa8e74c875a6caa3824fe90e7bcfa8472f1aae65dfe073789a681e15eb82487 11240 
rpcbind_1.2.5-0.3+deb10u1.debian.tar.xz
 41e382be8e6bbf4215f5081b4af13bb68bd96c62bd4de4faf5af0bfdc83832cc 6062 
rpcbind_1.2.5-0.3+deb10u1_amd64.buildinfo
Files:
 254f5874fbcb8304ac7de7302e97c303 1851 net optional 
rpcbind_1.2.5-0.3+deb10u1.dsc
 bf1e40e72af2954b09596f3979480d6f 11240 net optional 
rpcbind_1.2.5-0.3+deb10u1.debian.tar.xz
 5578d189d15034b7198127677dddebda 6062 net optional 
rpcbind_1.2.5-0.3+deb10u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAl2h6OURHGpvc3VlQGRl
Ymlhbi5vcmcACgkQAVCdXKtK/T+BDQ/8C/AN6tfzuIqOuuy1986R1qRtBn0lg3j+
jzreJ31qIZLyCBuNrEhAXJAB4hZBzbg4N7YlgOobQP6RxTjVMOHbrokMdwXjxH+t
rWfigfu5hYJMtak7QMLgFHH6xJjxTKMDrvFlEkMtYg5jvuaQTNyKm4IOkkeIzbRc
0cJoTFZP++C2A1s5rFJ86XGf0FjZe8ijGeVMKU12xqPBr/j6bBDgJ1inYsCbozNZ
Vwa5xoyh/Jb5SEJfnIsJY02srfF9646J5uiO9em44j4eyI9dXYY4nay9Mt0XxFtG
dh/cgIxu045TVRgZSfgkg9f1U/QfHGZaoOSk4YgrMFqW/vQDE6H81OusxuHFA85r
L1hDK87dczOQNyPcU6i0b9dnGoF8lhYhJePwe9xFzHafqzd8oHyDx1xMSjhwspuq
uEBmGujQhimzq6zGfe8AgeGMaCdAxXn9mwd/flMI0UuA7SdyhMn8RLaECS8qM8dz
kaaJ1zxyZFO2eas19jSBakRy6vOmvhC0yYnpInIpsX4Nl4AyxQb42tRpAwKZ7YkW
rPcepBjQEiZjnASzT3dQeSjvQHlR3sZoSIFQ7xV3oYUY+zQCY4TfFucJLRL2FS47
R/dyq+OW/GzWbw7RyHo/MiuW9lBsfoJDT7ymJat3lYEDrygU3t6rFTgzKWuUw+rj
iNuDZlzwVbk=
=xlGy
-END PGP SIGNATURE End Message ---

Bug#941955: marked as done (memory leaks in open-vm-tools)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:17:11 +
with message-id 
and subject line Bug#941955: fixed in open-vm-tools 2:10.3.10-1+deb10u2
has caused the Debian Bug report #941955,
regarding memory leaks in open-vm-tools
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.)


-- 
941955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941955
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: open-vm-tools
Version: 10.3.10-1

We have discovered a few memory leaks in open-vm-tools, related to the vix 
plugin. We have created a branch for 10.3.10 on github that includes fixes: 
https://github.com/vmware/open-vm-tools/tree/stable-10.3.10-vix-memory-leaks

Thanks,
Oliver



--- End Message ---
--- Begin Message ---
Source: open-vm-tools
Source-Version: 2:10.3.10-1+deb10u2

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

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

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

Debian distribution maintenance software
pp.
Bernd Zeimetz  (supplier of updated open-vm-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 09 Oct 2019 14:18:48 +0200
Source: open-vm-tools
Architecture: source
Version: 2:10.3.10-1+deb10u2
Distribution: buster
Urgency: medium
Maintainer: Bernd Zeimetz 
Changed-By: Bernd Zeimetz 
Closes: 941955
Changes:
 open-vm-tools (2:10.3.10-1+deb10u2) buster; urgency=medium
 .
   * [d512626] Fix memory leaks and error handling.
 From the upstream stable-10.3.10-vix-memory-leaks branch:
 commit 26b9edbeb79d1c67b9ae73a0c97c48999c1fb503
 Fix leaks in ListAliases and ListMappedAliases
 commit 7b874f37f970aab2adddb063a8363594f47abf70
 End VGAuth impersonation in the case of error.
 commit 015db4c06a8be65eb96cf62421e8b5366993452f
 Fix memory leaks in 'vix' tools plugin.
 Thanks to Oliver Kurth (Closes: #941955)
Checksums-Sha1:
 127afba950e69bab13f666c629a0e3113830e230 2358 
open-vm-tools_10.3.10-1+deb10u2.dsc
 3582f48a5e94a7256863ff68e418ef6c070f868a 30036 
open-vm-tools_10.3.10-1+deb10u2.debian.tar.xz
 64f3f695c8618e35ff64d1f72501865fb29eb781 16418 
open-vm-tools_10.3.10-1+deb10u2_source.buildinfo
Checksums-Sha256:
 b0de338a12bd51cc883447df9f21ac81abe84b13e74f453a606c5102b27b0cac 2358 
open-vm-tools_10.3.10-1+deb10u2.dsc
 088e3a8505e56f051dfb61c28754bbb3a7f335e6fc647195900f3e30f8948d82 30036 
open-vm-tools_10.3.10-1+deb10u2.debian.tar.xz
 91bedc37768d1cf1748a23070ec3f9068402452257d69ef63f43d623adde2592 16418 
open-vm-tools_10.3.10-1+deb10u2_source.buildinfo
Files:
 9121cdb8d5cba0eaa78e791dc372555f 2358 admin extra 
open-vm-tools_10.3.10-1+deb10u2.dsc
 8116615cd2a06d75730846c7a73fa915 30036 admin extra 
open-vm-tools_10.3.10-1+deb10u2.debian.tar.xz
 ab0173c62641400457bb9925ebe77d8f 16418 admin extra 
open-vm-tools_10.3.10-1+deb10u2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE7KHj8o4RJDLUhd2V6zYXGm/5Q18FAl2iLgwACgkQ6zYXGm/5
Q1/lWg/+MDLyDxMSqSjZKnKIKwW9OWYhdFTyNojoKA1upB45YfBOSLypECB+Y4OB
zcCbtUI6Q/TY8kUPjvIW3tCy4quRG5Tbvpp5KvG/THHVp1ezM94hDZBjH2v1RxF3
MHN0BFrMZOF5/jj3b4YcKdgD59RFoBGkiry0tPPseUr9hWFStC2aUrftiB8l3WQu
ItDsAC9TEE6Wabyy4ytyx5PjRC9Oc23PZgncnzUReUK81hDsLIRFCCZXiErEO6o8
i52Pk93MLjB9lm1bm3eRlovbhXux0megQDE2oPt/K7m8goAjkRZJj6kjAWFm7W1V
Ihxqo6VGSaNxNo/BQpZEWFkTAIlQxm7eKwc7AmaNS8pnQRV8jr/L2rxkYqA0JkuR
qxg8zqMANF5wbH2xoMXdmBjSWKEgCBwWZxzDOW7s34trzzQQ0SCFkEexaeq+0CN+
+LyeLSGK8zxDnzVRu6DrO1t+8qpx2AjOSKH9dOzjdUSmjesA7E1QNTjgBcQx5UGG
lkwDS8BF6NhiYTR0uk85gScZ2MrK+sllmGNJexWF2hFxlf7eGx4vASfL2yachZq9
QGF9kmikYQ8YKUD50+vwYy/Q1GKgzMJVCEE8v1NgAo0ABtcMdzIlmXaNTYPKk+og
NzK/2xrccgDzO0Gre2zF69TGtZ3GLFpp/9wcrUhNJkFtoXpuCc8=
=FFSf
-END PGP SIGNATURE End Message ---

Bug#941987: marked as done (libssl1.1: Ciphers AES-*-CBC-HMAC-* are missing in libssl 1.1.1d, but available in 1.1.1c)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:17:11 +
with message-id 
and subject line Bug#941987: fixed in openssl 1.1.1d-0+deb10u2
has caused the Debian Bug report #941987,
regarding libssl1.1: Ciphers AES-*-CBC-HMAC-* are missing in libssl 1.1.1d, but 
available in 1.1.1c
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.)


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

Package: libssl1.1
Version: 1.1.1c-1+0~20190710.13+debian10~1.gbp359e02
Severity: normal

Dear Maintainer,

   * What led up to the situation?
   Upgraded package libssl1.1 from 1.1.1c to 1.1.1d

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   Downgraded to 1.1.1c

   * What was the outcome of this action?
   4 more ciphers were back



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

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

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

Versions of packages libssl1.1 depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  libc6  2.28-10

libssl1.1 recommends no packages.

libssl1.1 suggests no packages.

-- debconf information excluded


Signature email
--- End Message ---
--- Begin Message ---
Source: openssl
Source-Version: 1.1.1d-0+deb10u2

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

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

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

Debian distribution maintenance software
pp.
Sebastian Andrzej Siewior  (supplier of updated 
openssl 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, 12 Oct 2019 21:56:43 +0200
Source: openssl
Architecture: source
Version: 1.1.1d-0+deb10u2
Distribution: buster-security
Urgency: medium
Maintainer: Debian OpenSSL Team 
Changed-By: Sebastian Andrzej Siewior 
Closes: 941987
Changes:
 openssl (1.1.1d-0+deb10u2) buster-security; urgency=medium
 .
   * Reenable AES-CBC-HMAC-SHA ciphers (Closes: #941987).
Checksums-Sha1:
 e80eadde9a37c9e1e30bf2ff1059f372521c7ff3 2472 openssl_1.1.1d-0+deb10u2.dsc
 bce8a3b76ae1561329362edd4de721e21224d639 84848 
openssl_1.1.1d-0+deb10u2.debian.tar.xz
Checksums-Sha256:
 cfeb4085016d29b14c2e0b1c204fd95a6fe20be3c12b669b8b0d6553eb2108a9 2472 
openssl_1.1.1d-0+deb10u2.dsc
 418f08b2182c54bad5f049d8b17433055e146c84c793794ebca3d74231b53389 84848 
openssl_1.1.1d-0+deb10u2.debian.tar.xz
Files:
 fd22615df0ab72a605e9c6af4d98e346 2472 utils optional 
openssl_1.1.1d-0+deb10u2.dsc
 0beb92d26e33b46c2b2ee7f8d359f3b6 84848 utils optional 
openssl_1.1.1d-0+deb10u2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEV4kucFIzBRM39v3RBWQfF1cS+lsFAl2iM0YACgkQBWQfF1cS
+luUkgv/XPrDTDGnCEhwNDUdRlTqHm1Sn2yre879VgG90Tblon2yNVwAgIYuw1Tf
GOkBdMB6YCp0XaqS/NXrF1Xh9x71ZA+GsoVaac/ram/CalzVn6uFaSJZp+TtSvSN
w+2oiBx3sG223hUeTxsM2SF7Uf5cn8EINKcQZfn2jp///qqGEEwAL7TBEJ7C7g7e
Jf91HFWGz7zDvrGCsn3BmWynn1p9XydVx9wOSmpnjgpRdOs5FmAEjHtbXDfNTiOj
K8udRHzX3HQ4NODdn4z/SzVpXEUmtmFfi34gMBqMYWoDf91DOaKPnqpWYVOGq71g
kDNb1Y8GwVgLBVsnxR1eIy9LgxvK/FZ6POkRI8DEk4PoBaibbxQgByNyMWyRsTK4
ZtIJasIPSTSL0gjbS+3Ug/c0qGI7Xm3SDF9AxBVorkYkhjLMKkrRrB9R8EqA+j7o
WhmMeJS1/6MKfwylZzWBXl9hQ8BD3Jc4eG2VgzgSPBs4L5HAmjhmeMPCZbQ8TRiM
7EOSwop1
=tBxR
-END PGP SIGNATURE End Message ---

Bug#935724: marked as done (aegisub: Aegisub crashes immediately after opening the context menu)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:17:08 +
with message-id 
and subject line Bug#935724: fixed in aegisub 3.2.2+dfsg-4+deb10u1
has caused the Debian Bug report #935724,
regarding aegisub: Aegisub crashes immediately after opening the context menu
to be marked as done.

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

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


-- 
935724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aegisub
Version: 3.2.2+dfsg-4
Severity: important

I hit a similar problem in another distribution. I believe that this is related
to the spell checking code (list available languages).
The same error occurs in Ubuntu 19.04. It should be mention that this bug
doesn't affect Aegisub in Ubuntu 16.04 LTS.

Steps to reproduce:
1. Run aegisub-3.2
2. Disable update checker if needed (first run only)
3. Press the context menu key

I suspect these components as the cause of the error:
a. libstdc++: It may be a problem with Dual ABI.
However, it should also affect package in Ubuntu 16.04 LTS, but it doesn't.
https://wiki.debian.org/GCC5
https://gcc.gnu.org/onlinedocs/gcc-5.2.0/libstdc++/manual/manual/using_dual_abi.html

b. GCC: Maybe this is caused by aggressive GCC 8 optimizations.
Maybe this is about some hardening flags (-D_GLIBCXX_ASSERTIONS)?

c. Boost:
Aegisub may be not 100% compatible with the latest Boost. TUV doesn't even
support Boost 1.69 OOTB. I believe that they are still using Boost 1.58.

gdb output:
> Thread 1 "aegisub-3.2" received signal SIGSEGV, Segmentation fault.
> 0x55981c6b in SubsTextEditCtrl::OnContextMenu (this=0x5643f400,
> event=...) at /usr/include/c++/8/bits/unique_ptr.h:342
> warning: Source file is more recent than executable.
> 342 get() const noexcept

I don't use Debian on a daily basis. I used LiveDVD (debian-
live-10.0.0-amd64-mate.iso).



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

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

Versions of packages aegisub depends on:
ii  libasound2 1.1.8-1
ii  libass91:0.14.0-2
ii  libboost-chrono1.67.0  1.67.0-13
ii  libboost-filesystem1.67.0  1.67.0-13
ii  libboost-locale1.67.0  1.67.0-13
ii  libboost-regex1.67.0   1.67.0-13
ii  libboost-system1.67.0  1.67.0-13
ii  libboost-thread1.67.0  1.67.0-13
ii  libc6  2.28-10
ii  libffms2-4 2.23-4
ii  libfontconfig1 2.13.1-2
ii  libgcc11:8.3.0-6
ii  libgl1 1.1.0-1
ii  libicu63   63.1-6
ii  libluajit-5.1-22.1.0~beta3+dfsg-5.1
ii  libstdc++6 8.3.0-6
ii  libwxbase3.0-0v5   3.0.4+dfsg-8
ii  libwxgtk3.0-0v53.0.4+dfsg-8
ii  zlib1g 1:1.2.11.dfsg-1

aegisub recommends no packages.

Versions of packages aegisub suggests:
pn  aegisub-l10n  

-- no debconf information
Oops, Aegisub has crashed!

An attempt has been made to save a copy of your file to:

/home/user/.aegisub/recovered/Untitled.2019-08-25-16-05-16.ass

Aegisub will now close.
--- End Message ---
--- Begin Message ---
Source: aegisub
Source-Version: 3.2.2+dfsg-4+deb10u1

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

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

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

Debian distribution maintenance software
pp.
Aniol Marti  (supplier of updated aegisub package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 02 Oct 2019 09:29:42 +
Source: aegisub
Architecture: source
Version: 3.2.2+dfsg-4+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Aniol Marti 
Changed-By: Aniol Marti 
Closes: 935724
Changes:
 aegisub (3.2.2+dfsg-4+deb10u1) buster; urgency=medium
 .
   * Add libhunspell-dev to 

Bug#910901: marked as done (plasma-applet-redshift-control: Mouse wheel only reduces color temperature, in either direction)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:17:21 +
with message-id 
and subject line Bug#910901: fixed in plasma-applet-redshift-control 
1.0.18-2+deb10u1
has caused the Debian Bug report #910901,
regarding plasma-applet-redshift-control: Mouse wheel only reduces color 
temperature, in either direction
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.)


-- 
910901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: plasma-applet-redshift-control
Version: 1.0.18-2
Severity: normal
Tags: patch

Since redshift 1.12, the interface for one-shot changes was modified, causing
all mouse wheel operations to only lower the color temperature and gamma.  The
fix is simply to add the new "-P" command line option.

Other reports, with one-liner patches:
https://bugs.kde.org/show_bug.cgi?id=395641
https://bugs.archlinux.org/task/59084



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

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

Versions of packages plasma-applet-redshift-control depends on:
ii  fonts-font-awesome  5.0.10+really4.7.0~dfsg-1
ii  redshift1.12-2

plasma-applet-redshift-control recommends no packages.

plasma-applet-redshift-control suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: plasma-applet-redshift-control
Source-Version: 1.0.18-2+deb10u1

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

Debian distribution maintenance software
pp.
Didier Raboud  (supplier of updated 
plasma-applet-redshift-control package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 01 Oct 2019 09:26:56 +0200
Source: plasma-applet-redshift-control
Architecture: source
Version: 1.0.18-2+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Didier Raboud 
Closes: 910901
Changes:
 plasma-applet-redshift-control (1.0.18-2+deb10u1) buster; urgency=medium
 .
   * Import upstream-submitted patch to fix manual mode for redshift
 >= 1.12 (Closes: #910901)
Checksums-Sha1:
 33a8d2a1415594bf7c91272536d176bb4819aecd 2281 
plasma-applet-redshift-control_1.0.18-2+deb10u1.dsc
 10d873519f6d926253bc6cba26bde361f319e13b 4732 
plasma-applet-redshift-control_1.0.18-2+deb10u1.debian.tar.xz
Checksums-Sha256:
 9371b73a77a819d5f428c7c3aa4cef1fd93bf03736bde68e1bef0042325ab1f4 2281 
plasma-applet-redshift-control_1.0.18-2+deb10u1.dsc
 ba11fd132c06fc285e7e1a5e04160bf1a44cdbdc22dc7c862789f632186d4a9b 4732 
plasma-applet-redshift-control_1.0.18-2+deb10u1.debian.tar.xz
Files:
 d0a08c8e6cd1dc9fbe18c257006fe726 2281 kde optional 
plasma-applet-redshift-control_1.0.18-2+deb10u1.dsc
 f262b2c71e323b86a8edffcdc652142b 4732 kde optional 
plasma-applet-redshift-control_1.0.18-2+deb10u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEe+WPIRpjNw1/GSB7i8+nHsoWNFUFAl2UR7cACgkQi8+nHsoW
NFVHpQv+IivKpzfk5bQZmZD2xIsGyOEUNmIsZD8CBWDbtkvgibtEh5K9drAOAFhP
rDvusZB0HrIo63ZO7Z0u4qR/Pz0D5kffj9jzYXiJddcUbnnbQJZXpNrt0XmozVY7
j6a3Ua8ZKg5yCMYRpAyaJ9V7Lm0d2sB731+bt8JLJObpCITyF4GroWA4udyVys5j
yys7EST7OwzP94xMl0pwa942BzQ6ngtVV7aIKLZhdkAzIEb5SZNhb7sVeAN4yt6o
dcs/XYEZ5PvDfC/V/F1Nf9glX+0VWELZUb7fni5h9wuvcyKOnH0dvUFRWMVgmjUx
k1A1mLQjYkXv4q6jQxzwPFl72SOme18c/Zeyf+IyferEXyQ1BGDmefMu4mFGGPK0
xsvS7UKxUxdgb6xHqnBAntOsf3FYZWFECuhRbWaY7Yz8eRTpLLGP5NdjLsayTdyZ
8M6BxM9KKeH2TwGVwT/Pyoi/pR1jtdBE4Em0XLut98YB/+dF16qwAcJHJdGDDhm7
aXxI4wks
=eZ6P
-END PGP SIGNATURE End Message ---

Bug#941189: marked as done (node-set-value: CVE-2019-10747)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:17:10 +
with message-id 
and subject line Bug#941189: fixed in node-set-value 0.4.0-1+deb10u1
has caused the Debian Bug report #941189,
regarding node-set-value: CVE-2019-10747
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.)


-- 
941189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-set-value
Version: 0.4.0-1
Severity: important
Tags: security upstream
Control: found -1 3.0.0-1

Hi,

The following vulnerability was published for node-set-value.

CVE-2019-10747[0]:
| set-value is vulnerable to Prototype Pollution in versions lower than
| 3.0.1. The function mixin-deep could be tricked into adding or
| modifying properties of Object.prototype using any of the constructor,
| prototype and _proto_ payloads.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-10747
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10747
[1] https://snyk.io/vuln/SNYK-JS-SETVALUE-450213

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: node-set-value
Source-Version: 0.4.0-1+deb10u1

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

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

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-set-value package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 26 Sep 2019 07:27:54 +0200
Source: node-set-value
Architecture: source
Version: 0.4.0-1+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 941189
Changes:
 node-set-value (0.4.0-1+deb10u1) buster; urgency=medium
 .
   * Team upload
   * Fix prototype pollution (Closes: #941189, CVE-2019-10747)
   * Add test for CVE-2019-10747
Checksums-Sha1: 
 9d2c5bf927437989e824bf1aef7a67098cb30ff5 2220 
node-set-value_0.4.0-1+deb10u1.dsc
 f4dfe860088e6ccb8f374ec2610b07473e97ebe5 5619 node-set-value_0.4.0.orig.tar.gz
 40aea7e0635627fa13053405a7698ca08a026f8b 2796 
node-set-value_0.4.0-1+deb10u1.debian.tar.xz
Checksums-Sha256: 
 24bad46a0536b10e4166b98b7d76c629fbed2fb726616f0343cff52abd3cdb82 2220 
node-set-value_0.4.0-1+deb10u1.dsc
 70f52e5305e17f2a374efd3aa6eadb2d5ce4cb283350a80c334c7ec493c89466 5619 
node-set-value_0.4.0.orig.tar.gz
 51aafcc4261fc892d1b705926b062e96a0636b9f747002aa84a138977a1cd34e 2796 
node-set-value_0.4.0-1+deb10u1.debian.tar.xz
Files: 
 93eebe8ab3d7e59f7d25cd13ecba3c8f 2220 web optional 
node-set-value_0.4.0-1+deb10u1.dsc
 e7cfaa9e1b8eb02025fd56059c1cd10f 5619 web optional 
node-set-value_0.4.0.orig.tar.gz
 801b65977507fe45370098a75d4324f7 2796 web optional 
node-set-value_0.4.0-1+deb10u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl2UKw8ACgkQ9tdMp8mZ
7un86Q/6AovThGKnOujpba5AEvT4qd3Wy4OcC/fXcerWW4uswE3tbe/BZyArh6Zn
G8eSHpqmRQod5R0QrmEX/VljqD8tUQULtCWs1bPISb5vd+sSq1gJ6Jy4JNcokgpa
9+1RV7nmavUq+sEzyy6PzVCWfSHhCGoix5UOpeSNG4aZclM4GTPDiE4GZTUp9D9q
xYSzz8am9y2Rpq1ykulnyxUnJ++30EhxntmGMKau0YP5zFAT9KzbWdWfd1RXvLgW
xDdFmWEKAKn2aH9B449ygnIEhPKbF75YNUYjDd92jfml3Jig+Lgk2JtPJ8O4FmyY
rgO9yQ3P7onsE36V8gkNKddFNdf6b9unMZwB+9c2G5EYsp/7lhuQcRQJ1TOY4sPX
C6/Mz55/omVqTjXv7XrnDlRnNjzp5alO02Vc7FqWhUuLXpgRyvbqp9V5rpHjmOI/
7JGL2wCFK1Unao+97NXv+H/+xyrRyZ3ZPwO6oN8qnX/tck2aQHqzD0/KkXWgBZxH
RPgYOeanf4CNRVLHtrLTqCNVgvCO2Qad1f8HdHsvCspD6PsffZOuprp/bLa7fTYC
aHbNGdEcn/O5S1gzRN/q3JJVvZysHxAZqiIcU6fmhy+wD/sjbbVipqRysAPvXTyQ
AhnkldhGf16l1nhM5BXeZC/PCHq04uxiKm+qtze7eVpw6jkO9p0=
=5WVs
-END PGP SIGNATURE End Message ---

Bug#931855: marked as done (rpc.rquotad takes 100% CPU)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:17:22 +
with message-id 
and subject line Bug#931855: fixed in quota 4.04-2+deb10u1
has caused the Debian Bug report #931855,
regarding rpc.rquotad takes 100% CPU
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.)


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

Dear Maintainer,


after upgrading to Buster rcp.rquotad takes 100% CPU.

It's probably the bug reported below:
https://sourceforge.net/p/linuxquota/feature-requests/16/
https://bugs.launchpad.net/ubuntu/+source/quota/+bug/1774431
https://bugzilla.redhat.com/show_bug.cgi?id=1575956

Upgrading to quota 4.05-1 (from SID) fixes the problem.


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

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

Versions of packages quota depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  libc6  2.28-10
ii  libcom-err21.44.5-1
ii  libdbus-1-31.12.16-1
ii  libext2fs2 1.44.5-1
ii  libldap-2.4-2  2.4.47+dfsg-3
ii  libnl-3-2003.4.0-1
ii  libnl-genl-3-200   3.4.0-1
ii  libtirpc3  1.1.4-0.4
ii  libwrap0   7.6.q-28
ii  lsb-base   10.2019051400

quota recommends no packages.

Versions of packages quota suggests:
pn  libnet-ldap-perl
ii  postfix [mail-transport-agent]  3.4.5-1
ii  rpcbind 1.2.5-0.3

-- Configuration Files:
/etc/default/quota changed:
run_warnquota=
RPCRQUOTADOPTS="-p 32769"


-- debconf information:
  quota/cc_before:
  quota/group_message:
  quota/subject:
  quota/supportphone:
  quota/charset:
  quota/rquota_setquota:
* quota/run_warnquota: false
  quota/signature:
  quota/mailfrom:
  quota/group_signature:
  quota/message:
  quota/supportemail:
  quota/cc:
--- End Message ---
--- Begin Message ---
Source: quota
Source-Version: 4.04-2+deb10u1

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

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

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

Debian distribution maintenance software
pp.
Mark Hymers  (supplier of updated quota package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 11 Sep 2019 20:07:07 +0100
Source: quota
Architecture: source
Version: 4.04-2+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Michael Meskes 
Changed-By: Mark Hymers 
Closes: 931855
Changes:
 quota (4.04-2+deb10u1) buster; urgency=medium
 .
   * With permission of maintainer, backport fix to stable to prevent
 rpc.rquotad spinning at 100% CPU.  Closes: #931855.
Checksums-Sha1:
 bf8a9a5474b9d4bcd2155d9b13131d6f8a451a2d 1871 quota_4.04-2+deb10u1.dsc
 a92302db8b0cc23aa0337e61410b24714f38d019 40452 
quota_4.04-2+deb10u1.debian.tar.xz
 507ce82ad921a9d4835b9fbd05c8cf30577582ee 7134 
quota_4.04-2+deb10u1_source.buildinfo
Checksums-Sha256:
 525a06d641c9ab27ae95d05d116ace5056ca78bf0e5018f6ab6962c0763331b0 1871 
quota_4.04-2+deb10u1.dsc
 508098f991901dbac4ff105c50f5837391ecbba4666b526bc9a370d72b0d49c3 40452 
quota_4.04-2+deb10u1.debian.tar.xz
 36b0e541bd61dc18e3a458e87486517e56312b6bed2a3e4b14eafb687321075c 7134 
quota_4.04-2+deb10u1_source.buildinfo
Files:
 e070fa3febdd2810243dcae9febdc391 1871 admin optional quota_4.04-2+deb10u1.dsc
 4073cfd8aeb002ea8dbec39b72de7de3 40452 admin optional 
quota_4.04-2+deb10u1.debian.tar.xz
 af2fcb74759ac13154600d3f465892e4 7134 admin optional 
quota_4.04-2+deb10u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEMJkRvqlm0GEwUwRXEbTl/xWw/YIFAl2hvAAACgkQEbTl/xWw
/YKEiBAAgDoMZCkxcxb0r3+kH48fCPy8HIGeX/bYv1FX9aMYQDG+3EmzITGFsifT
Uav/CnCAcw1r9/NB1brTEFCMiOAHmEWwJ9YeC8ez1vO97lxe+uqb2gqHc3VLFIM8
HfTZp56yTBbSVNUc8i/IfZ7EvunQ7JJJz/FGtUGNT9gMgfWO3c/dW2aa0w4fQfhZ

Bug#933163: marked as done (cyrus-imapd: Data loss possible when upgrading to buster)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:17:08 +
with message-id 
and subject line Bug#933163: fixed in cyrus-imapd 3.0.8-6+deb10u1
has caused the Debian Bug report #933163,
regarding cyrus-imapd: Data loss possible when upgrading to buster
to be marked as done.

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

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


-- 
933163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933163
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cyrus-imapd
Version: 3.0.8-6
Severity: grave
Tags: upstream

Dear Maintainer,

After upgrading a cyrus-imapd system from 2.4.17 (jessie-era) to 3.0.8 (buster),
I discovered many missing messages.  It appears that index records with MODSEQ 
set
to zero (e.g., records for messages which predated the addition of the MODSEQ 
field)
are being ignored.  The data is still there, but not served to IMAP clients.
Unfortunately, if the 3.0.8 cyrus "reconstruct" is executed to naively try to 
fix
the missing messages, those index records (and the metadata they contain, e.g.,
seen flags) are lost for good!  I tagged this report as "grave" because of the
potential for irreversible data loss.

There may be a one-line fix for this; I have filed an upstream bug report with 
more
details:

https://github.com/cyrusimap/cyrus-imapd/issues/2839

Fortunately, I have backups of the original cyrus.index files and didn't 
permanently
lose any state, but I don't know of any way to safely upgrade to v3.x.x until 
this
issue is fixed.

-m

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

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

Versions of packages cyrus-imapd depends on:
ii  cyrus-common  3.0.8-6
ii  dpkg  1.19.7
ii  libc6 2.28-10
ii  libcom-err2   1.44.5-1
ii  libsasl2-22.1.27+dfsg-1
ii  libssl1.1 1.1.1c-1
ii  libwrap0  7.6.q-28
ii  zlib1g1:1.2.11.dfsg-1

cyrus-imapd recommends no packages.

cyrus-imapd suggests no packages.

-- Configuration Files:
/etc/pam.d/imap changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: cyrus-imapd
Source-Version: 3.0.8-6+deb10u1

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

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

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated cyrus-imapd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 09 Oct 2019 22:38:07 +0200
Source: cyrus-imapd
Architecture: source
Version: 3.0.8-6+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Debian Cyrus Team 
Changed-By: Xavier Guimard 
Closes: 933163
Changes:
 cyrus-imapd (3.0.8-6+deb10u1) buster; urgency=medium
 .
   * Add patch to fix data loss on upgrade from versions ≤ 3.0.0
 (Closes: #933163)
Checksums-Sha1: 
 eee2d59d23825ee71f1477a15222e2d6bcab8c82 3157 cyrus-imapd_3.0.8-6+deb10u1.dsc
 8840295493f852b67b5a43b55c6ddbae5c9e4394 92656 
cyrus-imapd_3.0.8-6+deb10u1.debian.tar.xz
Checksums-Sha256: 
 721162a79c90c30c83cf47b2b9b3108e90d26b7cc615c37bcc5fcf36da8679f3 3157 
cyrus-imapd_3.0.8-6+deb10u1.dsc
 22b2d09a61d6b3094cd88d69154c01054ca93989f5fda3f21240207fa8fc0d12 92656 
cyrus-imapd_3.0.8-6+deb10u1.debian.tar.xz
Files: 
 ac66f5f95ec2c76cf0dd131ee39215d7 3157 mail optional 
cyrus-imapd_3.0.8-6+deb10u1.dsc
 b789355c52e3c74e2212f827b44d696e 92656 mail optional 
cyrus-imapd_3.0.8-6+deb10u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIyBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl2hed8ACgkQ9tdMp8mZ
7umKmQ/2PuCXjT84Dk67hkPqxzQRh9hC8KJ/DC64Pp3l91A54baRMOV8eE/AaNvv
XRloTd/eEaQtGqG9a82huuGioBU1Qi+7ZoEFTfv9QCuXHCicBQiABjJHQzHyGB4J
hbRosB/BNdOcIi+78B8ZqHBm0TYdEpCQka1xBmN04gvF5uqDasCTxOU8OVa9iE6H
KdBdiS/QJ9GJjo1zDScH9WOS8Nhhy3XblahXrjoD6ii25kOYt2d+UwuWJd8+ET9v
MvspBray1z1IUWQDxHZR84bY92hmj8n6ZM2+U3zPCZzOrsmXZgUbhXgJjgQJLnJI

Bug#934519: marked as done (fence-agents: FTBFS in stretch/buster/sid (ImportError: No module named pywsman))

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:17:09 +
with message-id 
and subject line Bug#934519: fixed in fence-agents 4.3.3-2+deb10u1
has caused the Debian Bug report #934519,
regarding fence-agents: FTBFS in stretch/buster/sid (ImportError: No module 
named pywsman)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --with python2 --with autoreconf
   dh_testdir -a
   dh_update_autotools_config -a
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf ./autogen.sh
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal -I make -I m4
configure.ac:70: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2601: _AC_COMPILE_IFELSE is expanded from...
../../lib/autoconf/general.m4:2617: AC_COMPILE_IFELSE is expanded from...

[... snipped ...]

xsltproc ../../fence/agents/lib/fence2wiki.xsl apc_snmp/.fence_apc_snmp.8.tmp | 
grep -v ' apc_snmp/fence_apc_snmp.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python ifmib/fence_ifmib -o metadata > 
ifmib/.fence_ifmib.8.tmp && \
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
ifmib/.fence_ifmib.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl ifmib/.fence_ifmib.8.tmp > 
ifmib/fence_ifmib.8
ifmib/.fence_ifmib.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl ifmib/.fence_ifmib.8.tmp | grep 
-v ' ifmib/fence_ifmib.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python ibmblade/fence_ibmblade -o metadata > 
ibmblade/.fence_ibmblade.8.tmp && \
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
ibmblade/.fence_ibmblade.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl ibmblade/.fence_ibmblade.8.tmp > 
ibmblade/fence_ibmblade.8
ibmblade/.fence_ibmblade.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl ibmblade/.fence_ibmblade.8.tmp | 
grep -v ' ibmblade/fence_ibmblade.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python bladecenter/fence_bladecenter -o metadata > 
bladecenter/.fence_bladecenter.8.tmp && \
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
bladecenter/.fence_bladecenter.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl 
bladecenter/.fence_bladecenter.8.tmp > bladecenter/fence_bladecenter.8
bladecenter/.fence_bladecenter.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl 
bladecenter/.fence_bladecenter.8.tmp | grep -v ' 
bladecenter/fence_bladecenter.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python rhevm/fence_rhevm -o metadata > 
rhevm/.fence_rhevm.8.tmp && \
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
rhevm/.fence_rhevm.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl rhevm/.fence_rhevm.8.tmp > 
rhevm/fence_rhevm.8
rhevm/.fence_rhevm.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl rhevm/.fence_rhevm.8.tmp | grep 
-v ' rhevm/fence_rhevm.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python ilo/fence_ilo -o metadata > ilo/.fence_ilo.8.tmp && \
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
ilo/.fence_ilo.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl ilo/.fence_ilo.8.tmp > 
ilo/fence_ilo.8
ilo/.fence_ilo.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl ilo/.fence_ilo.8.tmp | grep -v 
' ilo/fence_ilo.wiki
set -e && \
PYTHONPATH=/<>/fence/agents/lib:/<>/fence/agents/../lib:/<>/fence/agents/lib
 \
/usr/bin/python alom/fence_alom -o metadata > alom/.fence_alom.8.tmp && 
\
xmllint --noout --relaxng /<>/fence/agents/lib/metadata.rng 
alom/.fence_alom.8.tmp && \
xsltproc ../../fence/agents/lib/fence2man.xsl alom/.fence_alom.8.tmp > 
alom/fence_alom.8
alom/.fence_alom.8.tmp validates
xsltproc ../../fence/agents/lib/fence2wiki.xsl alom/.fence_alom.8.tmp | 

Bug#939877: marked as done (rpcbind: Does not receive any broadcast queries resulting in complete breakage of NIS)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:17:23 +
with message-id 
and subject line Bug#939877: fixed in rpcbind 1.2.5-0.3+deb10u1
has caused the Debian Bug report #939877,
regarding rpcbind: Does not receive any broadcast queries resulting in complete 
breakage of NIS
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.)


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

Dear Maintainer,

After an upgrade to buster rpcbind no longer receives any broadcast queries. 
Unicast works.

This is verified via strace - it has occasional netlink messages, but any of 
the broadcast
traffic to port 111 never hit it.

As a result clients can no longer find a nis server which has been upgraded to 
buster. 

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

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

Versions of packages rpcbind depends on:
ii  adduser  3.118
ii  libc62.28-10
ii  libsystemd0  241-7~deb10u1
ii  libtirpc31.1.4-0.4
ii  libwrap0 7.6.q-28
ii  lsb-base 10.2019051400

rpcbind recommends no packages.

rpcbind suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: rpcbind
Source-Version: 1.2.5-0.3+deb10u1

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

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

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

Debian distribution maintenance software
pp.
Josue Ortega  (supplier of updated rpcbind package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 09 Sep 2019 12:19:21 -0600
Source: rpcbind
Architecture: source
Version: 1.2.5-0.3+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Josue Ortega 
Changed-By: Josue Ortega 
Closes: 939877
Changes:
 rpcbind (1.2.5-0.3+deb10u1) buster; urgency=medium
 .
   * Add 00-rmt-calls.patch (Closes: #939877):
 + Add command line option to enable remote calls at runtime
 + Refresh debian/patches
   * debian/control: Update maintainer information
   * Add debian/README.debian explaining remote calls activation for
 Debian systems
   * Add debian/NEWS
Checksums-Sha1:
 e854744d050d76f3f8fbdd74eb92a251d8265995 1851 rpcbind_1.2.5-0.3+deb10u1.dsc
 99e7676ac0df6befdf4408f6bac2b029e355c970 11240 
rpcbind_1.2.5-0.3+deb10u1.debian.tar.xz
 dedc3c21829083670a1f47b6381b23b82c41f8b7 6062 
rpcbind_1.2.5-0.3+deb10u1_amd64.buildinfo
Checksums-Sha256:
 c881586a2b2e56c4985fe1f9a33f17271e43360e2ef8dc5def3f6e725432cf82 1851 
rpcbind_1.2.5-0.3+deb10u1.dsc
 daa8e74c875a6caa3824fe90e7bcfa8472f1aae65dfe073789a681e15eb82487 11240 
rpcbind_1.2.5-0.3+deb10u1.debian.tar.xz
 41e382be8e6bbf4215f5081b4af13bb68bd96c62bd4de4faf5af0bfdc83832cc 6062 
rpcbind_1.2.5-0.3+deb10u1_amd64.buildinfo
Files:
 254f5874fbcb8304ac7de7302e97c303 1851 net optional 
rpcbind_1.2.5-0.3+deb10u1.dsc
 bf1e40e72af2954b09596f3979480d6f 11240 net optional 
rpcbind_1.2.5-0.3+deb10u1.debian.tar.xz
 5578d189d15034b7198127677dddebda 6062 net optional 
rpcbind_1.2.5-0.3+deb10u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAl2h6OURHGpvc3VlQGRl
Ymlhbi5vcmcACgkQAVCdXKtK/T+BDQ/8C/AN6tfzuIqOuuy1986R1qRtBn0lg3j+
jzreJ31qIZLyCBuNrEhAXJAB4hZBzbg4N7YlgOobQP6RxTjVMOHbrokMdwXjxH+t
rWfigfu5hYJMtak7QMLgFHH6xJjxTKMDrvFlEkMtYg5jvuaQTNyKm4IOkkeIzbRc
0cJoTFZP++C2A1s5rFJ86XGf0FjZe8ijGeVMKU12xqPBr/j6bBDgJ1inYsCbozNZ
Vwa5xoyh/Jb5SEJfnIsJY02srfF9646J5uiO9em44j4eyI9dXYY4nay9Mt0XxFtG
dh/cgIxu045TVRgZSfgkg9f1U/QfHGZaoOSk4YgrMFqW/vQDE6H81OusxuHFA85r
L1hDK87dczOQNyPcU6i0b9dnGoF8lhYhJePwe9xFzHafqzd8oHyDx1xMSjhwspuq
uEBmGujQhimzq6zGfe8AgeGMaCdAxXn9mwd/flMI0UuA7SdyhMn8RLaECS8qM8dz

Bug#941464: marked as done (picard: Crash when using Spanish locale)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:17:21 +
with message-id 
and subject line Bug#941464: fixed in picard 2.1.2-1+deb10u1
has caused the Debian Bug report #941464,
regarding picard: Crash when using Spanish locale
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.)


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

Version: 2.2.1-1

Picard 2.2.1 in Buster crashes when using the Spanish locale and
opening options. This is a bug that we have fixed upstream [1] in the
2.1.3 release.

I think this package should actually be updated to the 2.1.3 release
(which is a bugfix release only not introducing new functionality) or
if this is not possible at the very minimum include the patch that
fixed the translations [2]


[1] https://tickets.metabrainz.org/browse/PICARD-1461
[2] 
https://github.com/metabrainz/picard/commit/5b7b29df2ae9dd5b860326fc5260e73fde74d0a5
--- End Message ---
--- Begin Message ---
Source: picard
Source-Version: 2.1.2-1+deb10u1

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

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

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated picard 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, 13 Oct 2019 10:02:04 +0200
Source: picard
Architecture: source
Version: 2.1.2-1+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Closes: 941464
Changes:
 picard (2.1.2-1+deb10u1) buster; urgency=medium
 .
   * debian/gbp.conf: Work in buster branch
   * debian/patches: Update translations to fix crash with Spanish locale 
(Closes: #941464)
Checksums-Sha1:
 695fb5c8b28bd5b3a26842d0ded8b1292a30f192 2036 picard_2.1.2-1+deb10u1.dsc
 e765603b9a0c5964ff8ea10cdbd5063debb35cf6 15680 
picard_2.1.2-1+deb10u1.debian.tar.xz
Checksums-Sha256:
 5e53bea28f6a42f7aad0f11dd59600a819e0f3f92e9e168a10cad2fb3ad31b2a 2036 
picard_2.1.2-1+deb10u1.dsc
 61aea85acb00451c5ef9a16021d4d46c68772d196fdacdea2692bcfc9c2380d4 15680 
picard_2.1.2-1+deb10u1.debian.tar.xz
Files:
 940d15553f1633c2f284514b373e4a72 2036 sound optional picard_2.1.2-1+deb10u1.dsc
 ad7cc2bd42c0d76e9917e25db9a10b3d 15680 sound optional 
picard_2.1.2-1+deb10u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl2i3sQACgkQafL8UW6n
GZOCoQ//U31Mloa1KlaaJ7paqo+ewOjN6Mt7PCeD319YvSvsDMcit2KfAC2Nu2qo
hzDJYNEyvoP5fqt3+ZDJDnT6m5HJDQS2LPxs8/F7MlqU9A5gGb9nlBxiGy5jjAL6
XdikO6rR9hySZ7sbmgtOssecs2sVhZxDlgbU1m1Vge0OMeeRvFgCypjCmJ/tbD9y
g4sYsXttxJjWf4n0gmN9MXAU4UmeBFjJKK9RidPnVs0WDbuaI3Dqnl8pbP0aJIDg
xCcGjRYHrJFlfuBAMB0kbXJctJ8YUjblS7HNuJ54BArda47qWozggoY2idzhiRok
ET8Ji1s9x6xPyc6QnywxTZOkV6v/NyWoJiGi1Xs+fhpyvO7umia87AMcxsR3PAZ+
fpcyoNCl8yylhWZEgc0rQixqPUmEtdBcnOfDD+HbMBC86gzCcmYbzKmZAASFmWPr
3fx1CreoLCtTMnrX+ZF5rM4uN410Ie/RmbaQPA+KbcTuI8JQVLGsHZ2cVTKgAfjx
igcxqWa/6b21XnJJpSA6lDWKqdnE3QEawHj8qMqtk9kGqAYYpkF49izd55J4yxAj
4soUBrzvttqzwV0da/eadWkyInvvmoRYf2nj2TMaHz0m3HfPQMQ8qupr/hLHdCNQ
3BfkWdqVTbD830o2Pje4ONvJk0Ar0fPW4e2M6Ac2aucoBdszuEw=
=8X09
-END PGP SIGNATURE End Message ---

Bug#939119: marked as done (gnustep-base-runtime: Upgrading to Debian 10 causes gdomap network service to become enabled)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:17:09 +
with message-id 
and subject line Bug#939119: fixed in gnustep-base 1.26.0-4+deb10u1
has caused the Debian Bug report #939119,
regarding gnustep-base-runtime: Upgrading to Debian 10 causes gdomap network 
service to become enabled
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.)


-- 
939119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939119
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnustep-base-runtime
Version: 1.26.0-4
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

I had "gnustep-base-runtime" installed on my system, probably as a
dependency of "unar".

When I upgrade from Debian 9 to Debian 10 (and reboot), there is a
network server "gdomap".  I did not see this server on Debian 9.
"gdomap" is not wanted.  It is supposed to be disabled by default
since 2013, i.e. in Debian 8.[1]

[1] #717773 "/usr/bin/gdomap: please split out gdomap or disable it by default"
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717773

The problem is due to this code change:

"Disable gdomap via defaults-disabled as per Policy 9.3.3.1."
https://salsa.debian.org/gnustep-team/gnustep-base/commit/e0da63fa9e341a38a9a493a615c2c36b8f9d418f

Salvatore Bonaccorso analyzed this for me:

> Install a fresh stretch installation and install gnustep-base-runtime
> in it. gdomap is not started by default, because gdomap init honours
> the ENABLED=no setting in /etc/default/gdomap. Now update the host to
> buster.
>
> During this update /etc/default/gdomap is updated according to the
> above. Unless the admin has modified it, where then it will be
> noticed and admin asked for a decision. As formerly the init was
> enabled, and the code to handle the ENABLED setting is removed this
> might be the problem. The postinst calls update-rc.d gdomap
> defaults-disabled [...]

"update-rc.d" does not do anything in this case.  The man page says

> If any files named /etc/rcrunlevel.d/[SK]??name already exist then
> update-rc.d does nothing.  The program was written this way so that
> it will never change an existing configuration, which may have been
> customized by the system administrator.  The program will only  
> install links if none are present, i.e., if it appears that the 
> service has never been installed before.

It is unfortunate that "Policy 9.3.3.1" does not have an explicit
warning about this potential security problem.

So this is a problem with upgrades.  It does not happen on a fresh
install of Debian 10.

Salvatore also suggested

> I think it's best handled though in a bugreport accordngly, and once
> fixed in unstable, to schedule a fix as well via a buster point
> release.

$ sudo netstat -l -p
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address   Foreign Address State   
PID/Program name
...
udp0  0 0.0.0.0:gdomap  0.0.0.0:*   
57/gdomap

$ ps aux | grep gdomap
nobody  57  0.0  0.0   2736  2052 ?Ss   11:16   0:00 
/usr/bin/gdomap -I /var/run/gdomap.pid -p -j /var/run/gdomap

$ dpkg-query -S gdomap
gnustep-base-runtime: /usr/share/man/man8/gdomap.8.gz
gnustep-base-runtime: /etc/default/gdomap
gnustep-base-runtime: /usr/bin/gdomap
gnustep-base-runtime: /etc/init.d/gdomap


[Report sent from a systemd-nspawn container, which I used to reproduce the 
issue]

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

Kernel: Linux 5.2.9-200.fc30.x86_64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnustep-base-runtime depends on:
ii  gnustep-base-common  1.26.0-4
ii  init-system-helpers  1.56+nmu1
ii  libc62.28-10
ii  libgcc1  1:8.3.0-6
ii  libgnustep-base1.26  1.26.0-4
ii  libobjc4 8.3.0-6
ii  lsb-base 10.2019051400

gnustep-base-runtime recommends no packages.

gnustep-base-runtime suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gnustep-base
Source-Version: 1.26.0-4+deb10u1

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

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

Bug#940547: marked as done (python-cryptography: Testsuite fails with OpenSSL 1.1.1d)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:17:22 +
with message-id 
and subject line Bug#940547: fixed in python-cryptography 2.6.1-3+deb10u1
has caused the Debian Bug report #940547,
regarding python-cryptography: Testsuite fails with OpenSSL 1.1.1d
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.)


-- 
940547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-cryptography
Version: 2.6.1-3
Severity: serious

The upload of latest openssl 1.1.1d triggert three testsuite failures in
python-cryptography [0]

- _ test_buffer_protocol_alternate_modes[mode5] 
__

|mode = 
|backend = 
|
|@pytest.mark.parametrize(
|"mode",
|[
|modes.CBC(bytearray(b"\x00" * 16)),
|modes.CTR(bytearray(b"\x00" * 16)),
|modes.OFB(bytearray(b"\x00" * 16)),
|modes.CFB(bytearray(b"\x00" * 16)),
|modes.CFB8(bytearray(b"\x00" * 16)),
|modes.XTS(bytearray(b"\x00" * 16)),
|]
|)
|@pytest.mark.requires_backend_interface(interface=CipherBackend)
|def test_buffer_protocol_alternate_modes(mode, backend):
|data = bytearray(b"sixteen_byte_msg")
|cipher = base.Cipher(
|algorithms.AES(bytearray(b"\x00" * 32)), mode, backend
|)
|>   enc = cipher.encryptor()
|
|tests/hazmat/primitives/test_aes.py:495: 
|_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
|/usr/lib/python2.7/dist-packages/cryptography/hazmat/primitives/ciphers/base.py:121:
 in encryptor
|self.algorithm, self.mode
|/usr/lib/python2.7/dist-packages/cryptography/hazmat/backends/openssl/backend.py:295:
 in create_symmetric_encryption_ctx
|return _CipherContext(self, cipher, mode, _CipherContext._ENCRYPT)
|/usr/lib/python2.7/dist-packages/cryptography/hazmat/backends/openssl/ciphers.py:116:
 in __init__
|self._backend.openssl_assert(res != 0)
|/usr/lib/python2.7/dist-packages/cryptography/hazmat/backends/openssl/backend.py:125:
 in openssl_assert
|return binding._openssl_assert(self._lib, ok)

This is due to commit 2a5f63c9a61be ("Allow AES XTS decryption using duplicate
keys.").
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2a5f63c9a61be

- _ TestDH.test_dh_parameters_supported 
__

|self = 
|backend = 
|
|def test_dh_parameters_supported(self, backend):
|assert backend.dh_parameters_supported(23, 5)
|>   assert not backend.dh_parameters_supported(23, 18)
|E   assert not True
|E+  where True = >(23, 18)
|E+where > = .dh_parameters_supported
|
|tests/hazmat/primitives/test_dh.py:161: AssertionError

This is due to commit ddd16c2fe988e ("Change DH parameters to generate the
order q subgroup instead of 2q").
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=ddd16c2fe988e

- _ TestECDSACertificate.test_load_ecdsa_no_named_curve 
__

|self = 
|backend = 
|
|def test_load_ecdsa_no_named_curve(self, backend):
|_skip_curve_unsupported(backend, ec.SECP256R1())
|cert = _load_cert(
|os.path.join("x509", "custom", "ec_no_named_curve.pem"),
|x509.load_pem_x509_certificate,
|backend
|)
|with pytest.raises(NotImplementedError):
|>   cert.public_key()
|E   Failed: DID NOT RAISE 
|
|tests/x509/test_x509.py:3722: Failed

This is due to commit 9a43a733801bd ("[ec] Match built-in curves on
EC_GROUP_new_from_ecparameters").
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9a43a733801bd


The first two changes in OpenSSL have been made on purporse and I'm not
sure about the last one.
Could someone please comment?

[0] 
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-cryptography/2969575/log.gz

Sebastian
--- End Message ---
--- Begin Message ---
Source: python-cryptography
Source-Version: 2.6.1-3+deb10u1

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

Debian distribution maintenance software
pp.
Sebastian Andrzej Siewior  (supplier of updated 
python-cryptography package)

(This message 

Bug#940069: marked as done (gr-limesdr: FTBFS in unstable)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:04:22 +
with message-id 
and subject line Bug#940069: fixed in gr-limesdr 2.0.0-27-gca01a64-2
has caused the Debian Bug report #940069,
regarding gr-limesdr: FTBFS in unstable
to be marked as done.

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

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


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

Package: gr-limesdr
Version: 0.9~beta-1+b2
Severity: serious
Tags: bullseye, sid

gr-limesdr failed to build with the following errors when an attempt was made 
to binnmu it for the new gnuradio.


-- Could NOT find MPIR (missing: MPIRXX_LIBRARY MPIR_LIBRARY MPIR_INCLUDE_DIR)
CMake Error at 
/usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
   Could NOT find MPLIB (missing: MPLIBXX_LIBRARY MPLIB_LIBRARY
   MPLIB_INCLUDE_DIR)
Call Stack (most recent call first):
   /usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:378 
(_FPHSA_FAILURE_MESSAGE)
   /usr/lib/x86_64-linux-gnu/cmake/gnuradio/FindMPLIB.cmake:26 
(find_package_handle_standard_args)
   /usr/share/cmake-3.13/Modules/CMakeFindDependencyMacro.cmake:48 
(find_package)
   /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GnuradioConfig.cmake:26 
(find_dependency)
   CMakeLists.txt:130 (find_package)


--- End Message ---
--- Begin Message ---
Source: gr-limesdr
Source-Version: 2.0.0-27-gca01a64-2

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated gr-limesdr 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, 13 Oct 2019 20:51:15 +0200
Source: gr-limesdr
Architecture: source
Version: 2.0.0-27-gca01a64-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Christoph Berg 
Closes: 915597 936662 940069
Changes:
 gr-limesdr (2.0.0-27-gca01a64-2) experimental; urgency=medium
 .
   * Add B-D python3-six, the doxygen docs need it.
 .
 gr-limesdr (2.0.0-27-gca01a64-1) experimental; urgency=medium
 .
   [ A. Maitland Bottoms ]
   * New upstream tag v2.0.0
   * Update homepage (Closes: #915597)
 .
   [ Christoph Berg ]
   * New upstream version 2.0.0-27-gca01a64 with support for gnuradio 3.8.
   * Set package name to libgnuradio-limesdr3.0.0.
   * Add liborc-0.4-dev and libgmp-dev build-dependencies. (Closes: #940069)
   * Add debian/gitlab-ci.yml.
   * Move to Section: hamradio.
   * Add ${python3:Depends} dependency. (Closes: #936662)
   * Update copyright after upstream source was restructured.
Checksums-Sha1:
 1ffae1063c98e5ecc5933172f105c9354a095bd8 2342 
gr-limesdr_2.0.0-27-gca01a64-2.dsc
 16c3c9ba846ac664c1bd73812d7287e487c852ed 3664 
gr-limesdr_2.0.0-27-gca01a64-2.debian.tar.xz
Checksums-Sha256:
 06270c3994f78ebb49760b1052e28e333d987f7529d5dcc6a2fa0114fbe3e100 2342 
gr-limesdr_2.0.0-27-gca01a64-2.dsc
 bab77b043c3b8a1e18de74bf916b54f0b033784c815bd3e106aa8645bf74b60b 3664 
gr-limesdr_2.0.0-27-gca01a64-2.debian.tar.xz
Files:
 9ecf1a24517af05f70236127f96ebbc8 2342 hamradio optional 
gr-limesdr_2.0.0-27-gca01a64-2.dsc
 82877935459cf4b8af1fa894464d3495 3664 hamradio optional 
gr-limesdr_2.0.0-27-gca01a64-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl2jct0ACgkQTFprqxLS
p64tIg//QJw0UmxWI84aGLTTEndnKnNO9uWtxnClzlmkbsRn5OV2eOdxk35aNg0g
YnKdgMR6puRkV/GwXvtCtMGfjLuaRthC5G1k2boIz3jvL9PvdSKgujuz2HnQ92zP
fRiH/H4i+LUj7QiQLOrphYbm2i1r8hS27bPn2WqJWHyFA/EAKVW02umHwzHS7w5n
MB5LxLjOTqR9jBOyFJ8kRtyP5OBPLz4vzryi7zN1jibyurvYUd5iIsMMAQEss2r0
AT2kF0s9LHO1jYW3Ks+oUY2F+oCPjIEKs50uGByk5MACi0/9P4G1EpZNaS1sGUI7
8GfGWFZYn2MQFfmsJLf5zWSTdZPUcuaylH3KwDzkG80G0jmN4wibCK3NedIExA1P
Lp7LCntHr0C1f9X0e2ofzwN/1nObtV2QaRJ/lrjyHG7AQXiDiF4xg13bIsKm8Dzg
yTd8TS3jW70WMMFSt4HwrITLKFq1v1ySnS1dPLF3BQECTxRI0E+o/GePe3spLRNr
a5yIaz3Oowv+meOYCA12B0jSWJ2rW6cLj/Aal1BRlk5ikFWAlnOE0f2pw01TTxwH
O5iQCaLavSH6wbdOtUtbvnayTZIQnj/FpDte8vLgU9C1OJSdTzLTnnNHxI2akTTW
myBjkvEd4+voLqHCDrO0z9ETJGTzimKxVW5J4tToS+MgdZjLvy8=
=fjLq
-END PGP 

Bug#938833: marked as done (wsgicors: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:04:41 +
with message-id 
and subject line Bug#938833: fixed in wsgicors 0.4.1-1.1
has caused the Debian Bug report #938833,
regarding wsgicors: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:wsgicors

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: wsgicors
Source-Version: 0.4.1-1.1

We believe that the bug you reported is fixed in the latest version of
wsgicors, 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.
Sandro Tosi  (supplier of updated wsgicors 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, 06 Oct 2019 14:25:37 -0400
Source: wsgicors
Architecture: source
Version: 0.4.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: David Douard 
Changed-By: Sandro Tosi 
Closes: 938833
Changes:
 wsgicors (0.4.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #938833
Checksums-Sha1:
 dad7161ec1437d4880f24cb2b08d63bf93be4cc9 1889 wsgicors_0.4.1-1.1.dsc
 10d4efb677c55a3166d3a6c07d35cd9ce1612e25 1416 wsgicors_0.4.1-1.1.debian.tar.xz
 4da6544a8f49df95dc52ba027c12799f2796e946 6149 
wsgicors_0.4.1-1.1_source.buildinfo
Checksums-Sha256:
 1bae0f4cdee6b8a09bf93b658ac2b07e3aa6f4d2caeb95af72410108b844a883 1889 
wsgicors_0.4.1-1.1.dsc
 92aae6d1b3455ffb00dd76fe58dc5f4395a706467b7f4ec66db0cc8e22cd31ed 1416 
wsgicors_0.4.1-1.1.debian.tar.xz
 568adc4dff662ae26478bd9960f90ba68a7521d36c1ba90f363055ca2e584e41 6149 
wsgicors_0.4.1-1.1_source.buildinfo
Files:
 a8ad88d3c1ef13d435209762c40b7e75 1889 python optional 

Bug#912196: marked as done (abgate FTCBFS: multiple reasons)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:04:03 +
with message-id 
and subject line Bug#912196: fixed in abgate 1.1.9-2
has caused the Debian Bug report #912196,
regarding abgate FTCBFS: multiple reasons
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.)


-- 
912196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: abgate
Version: 1.1.9-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

abgate fails to cross build from source for multiple reasons:

 * The upstream Makefile hard codes build architecture tools such as g++
   or pkg-config.
 * The upstream Makefile directly runs qmake, which lacks cross flags as
   well.

The attached patch fixes that. In part, the Makefile is fixed. For qt,
it is simply sidestepped. After doing so, abgate cross builds
successfully. Please consider applying it.

Helmut
diff --minimal -Nru abgate-1.1.9/debian/changelog abgate-1.1.9/debian/changelog
--- abgate-1.1.9/debian/changelog   2017-11-01 12:38:10.0 +0100
+++ abgate-1.1.9/debian/changelog   2018-10-29 06:15:39.0 +0100
@@ -1,3 +1,12 @@
+abgate (1.1.9-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Build abGateQt directly via dh_auto_* before the Makefile can do it.
++ cross.patch: Honour cross tools.
+
+ -- Helmut Grohne   Mon, 29 Oct 2018 06:15:39 +0100
+
 abgate (1.1.9-1) unstable; urgency=medium
 
   * New upstream version 1.1.9
diff --minimal -Nru abgate-1.1.9/debian/patches/cross.patch 
abgate-1.1.9/debian/patches/cross.patch
--- abgate-1.1.9/debian/patches/cross.patch 1970-01-01 01:00:00.0 
+0100
+++ abgate-1.1.9/debian/patches/cross.patch 2018-10-29 06:15:35.0 
+0100
@@ -0,0 +1,23 @@
+--- abgate-1.1.9.orig/Makefile
 abgate-1.1.9/Makefile
+@@ -3,6 +3,7 @@
+ BUNDLE = abGate.lv2
+ PREFIX = /usr
+ INSTALL_DIR = $(DESTDIR)$(PREFIX)/lib/lv2
++PKG_CONFIG ?= pkg-config
+ 
+ $(BUNDLE): manifest.ttl gate.ttl gate.so gate_gui.so bypass_on.png 
bypass_off.png knob.png background.png abGateQt/libabGateQt.so
+   rm -rf $(BUNDLE)
+@@ -13,10 +14,10 @@
+   cd abGateQt; qmake; make
+ 
+ gate.so: gate.cpp
+-  g++ $(LDFLAGS) $(CPPFLAGS) $(CFLAGS) -g -O3 -shared -fPIC -DPIC 
-Wl,--as-needed gate.cpp `pkg-config --cflags --libs lv2` -o gate.so
++  $(CXX) $(LDFLAGS) $(CPPFLAGS) $(CFLAGS) -g -O3 -shared -fPIC -DPIC 
-Wl,--as-needed gate.cpp `$(PKG_CONFIG) --cflags --libs lv2` -o gate.so
+ 
+ gate_gui.so: gate_gui.cpp main_window.cpp main_window.h knob.cpp knob.h 
toggle.cpp toggle.h preset_widget.cpp preset_widget.h presets.cpp presets.h 
preset.cpp preset.h gate_const.h plugin_configuration.h
+-  g++ $(LDFLAGS) $(CPPFLAGS) $(CFLAGS) -g -O3 -shared -fPIC -DPIC 
-Wl,--as-needed gate_gui.cpp main_window.cpp knob.cpp toggle.cpp 
preset_widget.cpp presets.cpp preset.cpp `pkg-config --cflags gtkmm-2.4 --libs 
lv2 gthread-2.0` -o gate_gui.so
++  $(CXX) $(LDFLAGS) $(CPPFLAGS) $(CFLAGS) -g -O3 -shared -fPIC -DPIC 
-Wl,--as-needed gate_gui.cpp main_window.cpp knob.cpp toggle.cpp 
preset_widget.cpp presets.cpp preset.cpp `$(PKG_CONFIG) --cflags gtkmm-2.4 
--libs lv2 gthread-2.0` -o gate_gui.so
+ 
+ all: $(BUNDLE)
+ 
diff --minimal -Nru abgate-1.1.9/debian/patches/series 
abgate-1.1.9/debian/patches/series
--- abgate-1.1.9/debian/patches/series  2017-10-11 16:19:02.0 +0200
+++ abgate-1.1.9/debian/patches/series  2018-10-29 06:14:55.0 +0100
@@ -1 +1,2 @@
 0002-flags.patch
+cross.patch
diff --minimal -Nru abgate-1.1.9/debian/rules abgate-1.1.9/debian/rules
--- abgate-1.1.9/debian/rules   2017-11-01 12:25:19.0 +0100
+++ abgate-1.1.9/debian/rules   2018-10-29 06:15:39.0 +0100
@@ -8,3 +8,10 @@
 
 %:
dh $@
+
+override_dh_auto_configure:
+   dh_auto_configure --sourcedirectory=abGateQt
+
+override_dh_auto_build:
+   dh_auto_build --sourcedirectory=abGateQt
+   dh_auto_build
--- End Message ---
--- Begin Message ---
Source: abgate
Source-Version: 1.1.9-2

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated abgate package)

(This message was 

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

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:04:22 +
with message-id 
and subject line Bug#936662: fixed in gr-limesdr 2.0.0-27-gca01a64-2
has caused the Debian Bug report #936662,
regarding gr-limesdr: 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.)


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

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: gr-limesdr
Source-Version: 2.0.0-27-gca01a64-2

We believe that the bug you reported is fixed in the latest version of
gr-limesdr, 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.
Christoph Berg  (supplier of updated gr-limesdr 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, 13 Oct 2019 20:51:15 +0200
Source: gr-limesdr
Architecture: source
Version: 2.0.0-27-gca01a64-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Christoph Berg 
Closes: 915597 936662 940069
Changes:
 gr-limesdr (2.0.0-27-gca01a64-2) experimental; urgency=medium
 .
   * Add B-D python3-six, the doxygen docs need it.
 .
 gr-limesdr (2.0.0-27-gca01a64-1) experimental; urgency=medium
 .
   [ A. Maitland Bottoms ]
   * New upstream tag v2.0.0
   * Update homepage (Closes: #915597)
 .
   [ Christoph Berg ]
   * New upstream version 2.0.0-27-gca01a64 with support for gnuradio 3.8.
   * Set package name to libgnuradio-limesdr3.0.0.
   * Add liborc-0.4-dev and libgmp-dev build-dependencies. (Closes: #940069)
   * Add debian/gitlab-ci.yml.
   * Move to Section: hamradio.
   * Add ${python3:Depends} dependency. (Closes: #936662)
   * Update copyright after upstream source was 

Bug#915597: marked as done (gr-limesdr: Homepage: points to dead page)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:04:22 +
with message-id 
and subject line Bug#915597: fixed in gr-limesdr 2.0.0-27-gca01a64-2
has caused the Debian Bug report #915597,
regarding gr-limesdr: Homepage: points to dead page
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.)


-- 
915597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gr-limesdr
Version: 0.9~beta-1
Severity: minor

The actual homepage seems to be
  https://tracker.debian.org/media/packages/g/gr-limesdr
--- End Message ---
--- Begin Message ---
Source: gr-limesdr
Source-Version: 2.0.0-27-gca01a64-2

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated gr-limesdr 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, 13 Oct 2019 20:51:15 +0200
Source: gr-limesdr
Architecture: source
Version: 2.0.0-27-gca01a64-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Christoph Berg 
Closes: 915597 936662 940069
Changes:
 gr-limesdr (2.0.0-27-gca01a64-2) experimental; urgency=medium
 .
   * Add B-D python3-six, the doxygen docs need it.
 .
 gr-limesdr (2.0.0-27-gca01a64-1) experimental; urgency=medium
 .
   [ A. Maitland Bottoms ]
   * New upstream tag v2.0.0
   * Update homepage (Closes: #915597)
 .
   [ Christoph Berg ]
   * New upstream version 2.0.0-27-gca01a64 with support for gnuradio 3.8.
   * Set package name to libgnuradio-limesdr3.0.0.
   * Add liborc-0.4-dev and libgmp-dev build-dependencies. (Closes: #940069)
   * Add debian/gitlab-ci.yml.
   * Move to Section: hamradio.
   * Add ${python3:Depends} dependency. (Closes: #936662)
   * Update copyright after upstream source was restructured.
Checksums-Sha1:
 1ffae1063c98e5ecc5933172f105c9354a095bd8 2342 
gr-limesdr_2.0.0-27-gca01a64-2.dsc
 16c3c9ba846ac664c1bd73812d7287e487c852ed 3664 
gr-limesdr_2.0.0-27-gca01a64-2.debian.tar.xz
Checksums-Sha256:
 06270c3994f78ebb49760b1052e28e333d987f7529d5dcc6a2fa0114fbe3e100 2342 
gr-limesdr_2.0.0-27-gca01a64-2.dsc
 bab77b043c3b8a1e18de74bf916b54f0b033784c815bd3e106aa8645bf74b60b 3664 
gr-limesdr_2.0.0-27-gca01a64-2.debian.tar.xz
Files:
 9ecf1a24517af05f70236127f96ebbc8 2342 hamradio optional 
gr-limesdr_2.0.0-27-gca01a64-2.dsc
 82877935459cf4b8af1fa894464d3495 3664 hamradio optional 
gr-limesdr_2.0.0-27-gca01a64-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl2jct0ACgkQTFprqxLS
p64tIg//QJw0UmxWI84aGLTTEndnKnNO9uWtxnClzlmkbsRn5OV2eOdxk35aNg0g
YnKdgMR6puRkV/GwXvtCtMGfjLuaRthC5G1k2boIz3jvL9PvdSKgujuz2HnQ92zP
fRiH/H4i+LUj7QiQLOrphYbm2i1r8hS27bPn2WqJWHyFA/EAKVW02umHwzHS7w5n
MB5LxLjOTqR9jBOyFJ8kRtyP5OBPLz4vzryi7zN1jibyurvYUd5iIsMMAQEss2r0
AT2kF0s9LHO1jYW3Ks+oUY2F+oCPjIEKs50uGByk5MACi0/9P4G1EpZNaS1sGUI7
8GfGWFZYn2MQFfmsJLf5zWSTdZPUcuaylH3KwDzkG80G0jmN4wibCK3NedIExA1P
Lp7LCntHr0C1f9X0e2ofzwN/1nObtV2QaRJ/lrjyHG7AQXiDiF4xg13bIsKm8Dzg
yTd8TS3jW70WMMFSt4HwrITLKFq1v1ySnS1dPLF3BQECTxRI0E+o/GePe3spLRNr
a5yIaz3Oowv+meOYCA12B0jSWJ2rW6cLj/Aal1BRlk5ikFWAlnOE0f2pw01TTxwH
O5iQCaLavSH6wbdOtUtbvnayTZIQnj/FpDte8vLgU9C1OJSdTzLTnnNHxI2akTTW
myBjkvEd4+voLqHCDrO0z9ETJGTzimKxVW5J4tToS+MgdZjLvy8=
=fjLq
-END PGP SIGNATURE End Message ---

Bug#935737: marked as done (transition: perl)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 21:05:19 +0200
with message-id <1553faab-0f1d-8f33-8c70-f52df130c...@debian.org>
and subject line Re: Bug#935737: transition: perl
has caused the Debian Bug report #935737,
regarding transition: perl
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.)


-- 
935737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hi, perl 5.30 has been in experimental since May and I think it is
ready for sid/bullseye now.

Our test rebuilds caught unusually few failures and those are
all fixed now.

The build system has been revamped: it's now based on debhelper/dh
and supports building the three perl variants (static, shared, debug)
in parallel via symlink farms in separate build directories. Other
packaging changes are minimal.

The symlink farm part broke builds under qemu-user (due to its
special/buggy $0 implementation), but that doesn't concern release
architectures. See #931641. I believe only the sh4 buildds are currently
affected.

As usual the bugs are at
 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.30-transition;users=debian-p...@lists.debian.org

Please let us know when we might get a transition slot.  Both of us
are currently rather taken by real life stuff, so would appreciate an
advance warning if possible.

Many thanks for your work on the release.

Ben file:

title = "perl";
is_affected = .depends ~ "libperl5.28|perlapi-5.28" | .depends ~ 
"libperl5.30|perlapi-5.30";
is_good = .depends ~ "libperl5.30|perlapi-5.30";
is_bad = .depends ~ "libperl5.28|perlapi-5.28";


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

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

On 05-10-2019 12:06, Paul Gevers wrote:
> On 03-10-2019 21:32, Dominic Hargreaves wrote:
>> Yes, I am able to cut a release and upload on Saturday (morning Europe
>> time).
> 
> Ok, let's go this going.

And all done now. Thanks for the cooperation.

Paul



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

Bug#938474: marked as done (sgp4: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:04:35 +
with message-id 
and subject line Bug#938474: fixed in sgp4 1.4-1.1
has caused the Debian Bug report #938474,
regarding sgp4: 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.)


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

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: sgp4
Source-Version: 1.4-1.1

We believe that the bug you reported is fixed in the latest version of
sgp4, 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.
Sandro Tosi  (supplier of updated sgp4 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, 06 Oct 2019 14:19:56 -0400
Source: sgp4
Architecture: source
Version: 1.4-1.1
Distribution: unstable
Urgency: medium
Maintainer: Ulises Vitulli 
Changed-By: Sandro Tosi 
Closes: 938474
Changes:
 sgp4 (1.4-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #938474
Checksums-Sha1:
 1043d2ab114b37688c000d765636face1a00c8a9 1735 sgp4_1.4-1.1.dsc
 b4fa19854e17ed5107bbbdbc0820a96a772c1221 2372 sgp4_1.4-1.1.debian.tar.xz
 6c5a476a8af883fab126fbe20b4b5f301baffc7e 6121 sgp4_1.4-1.1_source.buildinfo
Checksums-Sha256:
 709caf8d7e07fe38f8e6c0a440338be5258631874ef57f86f316aefad88d5ec6 1735 
sgp4_1.4-1.1.dsc
 2e59b043f3252fcbb514c3cafe53fdcc19de7d38783f4c07f7e7af18d363bc65 2372 
sgp4_1.4-1.1.debian.tar.xz
 698e444293e9e6a1563065a7d98dd2a8838b078cc4d271d131e25faa5e6454b0 6121 
sgp4_1.4-1.1_source.buildinfo
Files:
 5524f62393545ae9c96640c7e6d61e6c 1735 python optional sgp4_1.4-1.1.dsc
 1ffa0185eb475bdfe7817c9a10b914bc 2372 python optional 

Bug#941083: marked as done (ITP: stream-lib -- library for summarizing data in streams)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 19:00:10 +
with message-id 
and subject line Bug#941083: fixed in stream-lib 2.9.8-1
has caused the Debian Bug report #941083,
regarding ITP: stream-lib -- library for summarizing data in streams
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.)


-- 
941083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Owner: Andrius Merkys 
Severity: wishlist
Control: block 585905 by -1

* Package name    : stream-lib
  Version : 2.9.8
  Upstream Author : Matt Abrams 
* URL : https://github.com/addthis/stream-lib
* License : Apache-2.0
  Programming Lang: Java
  Description : library for summarizing data in streams
 A Java library for summarizing data in streams for which it is
infeasible to
 store all events. More specifically, there are classes for estimating:
 cardinality (i.e. counting things); set membership; top-k elements and
 frequency. One particularly useful feature is that cardinality
estimators with
 compatible configurations may be safely merged.

This package is a dependency of apache-cassandra.

Remark: This package is to be maintained with Debian Java Maintainers at
   https://salsa.debian.org/java-team/stream-lib
--- End Message ---
--- Begin Message ---
Source: stream-lib
Source-Version: 2.9.8-1

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

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

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

Debian distribution maintenance software
pp.
Andrius Merkys  (supplier of updated stream-lib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 24 Sep 2019 01:27:19 -0400
Source: stream-lib
Binary: libstream-java
Architecture: source all
Version: 2.9.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Andrius Merkys 
Description:
 libstream-java - library for summarizing data in streams
Closes: 941083
Changes:
 stream-lib (2.9.8-1) unstable; urgency=medium
 .
   * Initial release (Closes: #941083)
Checksums-Sha1:
 7a7033fc9c0110766a5a626086c20d805c11fc66 2160 stream-lib_2.9.8-1.dsc
 6f949d26827e95ad74870004da31bb401fc670a3 919812 stream-lib_2.9.8.orig.tar.gz
 d0c6f519949973d6124c2d9dca83eea3b34e1925 10628 stream-lib_2.9.8-1.debian.tar.xz
 a3bfd94f83933b52d95119cf72778c80ca2358e0 158908 libstream-java_2.9.8-1_all.deb
 a0da45419fe063f324d1cc9518052ed2e1264c71 13177 
stream-lib_2.9.8-1_amd64.buildinfo
Checksums-Sha256:
 2ab7b05a6bec2298081e3b791914eaa4a40539b88ae7184b650cb392d9c85daf 2160 
stream-lib_2.9.8-1.dsc
 b2a48d89f150545eed41ca4cdfcc1ec4730a107b67b61ddede6bdf6ae4417d1e 919812 
stream-lib_2.9.8.orig.tar.gz
 e87f7eeebdd5813c932f0abffa487523bcdaba257f456b626fb9f580e30d8805 10628 
stream-lib_2.9.8-1.debian.tar.xz
 437b64662553d665b79f1293b7bd0d6a0f77abeacdb3af38663ba9ee63f8e244 158908 
libstream-java_2.9.8-1_all.deb
 50b2ff0c74ee6cdabcbde7c332eaa8ae8dd4d5f858ac90e47e5902cec4f1e8df 13177 
stream-lib_2.9.8-1_amd64.buildinfo
Files:
 6a15c4ed04d0e463666a4f150c19d2d1 2160 java optional stream-lib_2.9.8-1.dsc
 03d7ff980782da9bb97764c8d6fb8080 919812 java optional 
stream-lib_2.9.8.orig.tar.gz
 76c680ff4e6ea5d054617c6b72b3a8c8 10628 java optional 
stream-lib_2.9.8-1.debian.tar.xz
 2adae2733c11fe902533526ae3a4a291 158908 java optional 
libstream-java_2.9.8-1_all.deb
 ca49d02e8c1bf352c9014571fc07b453 13177 java optional 
stream-lib_2.9.8-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAl2K+gISHG1lcmt5c0Bk
ZWJpYW4ub3JnAAoJEOX0P5wnNPKH7W0P/1IsQ5ey2M2odbCriGyuqz0x7vM5+8s+
olBetjUyyvEKhBtDiBBZusCkqT1r9RD0wxHtjbuuAxpifYLPdZua0IJirwAsBOoD
9okN2TPYV4el0VKWvJJQUn2CqeYWthbKKBzrLbWWcE+w7LL3xEgXgh+fVhbbaKiU
dhD/R2s58PYD6dCABZFVOLoT9lwSxmaMPpdh5cIUjZUr+hUGmsHKFvi0XyZrTlHK
CnZzXh34RR/elHI8KV1WoSat44DeoCYHRqNo3S5HH3YwytTO7hcNUpHv1Kd2G5os
/LCVjyLWUDu+Pe2wziaSa7l5VO5/arMy8BSsXQtbBfgT7xCZbx0RaU88mTI7yj9l
OlRAduyArXTMrypL/RvGg334uGoiC/hsSQGJ+QtfF0/HeGf7cBs8eQ7q1oePVvWI
RyS4ccvfAtjHiC//VRmpLusuX9sYRyzMQwPJgqXH964UBgHxKKyHC/FLwuM/wyWO

Bug#941963: marked as done (ITP: opentest4j -- Open Test Alliance for the JVM)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 18:00:18 +
with message-id 
and subject line Bug#941963: fixed in opentest4j 1.2.0-1
has caused the Debian Bug report #941963,
regarding ITP: opentest4j -- Open Test Alliance for the JVM
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.)


-- 
941963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Emmanuel Bourg 

* Package name: opentest4j
  Version : 1.2.0
  Upstream Author : Marc Philipp, Sam Brannen
* URL : https://github.com/ota4j-team/opentest4j
* License : Apache-2.0
  Programming Lang: Java
  Description : Open Test Alliance for the JVM

OpenTest4Jj provides a minimal common foundation for testing libraries
on the JVM. The primary goal of the project is to enable testing
frameworks like JUnit, TestNG, Spock, etc. and third-party assertion
libraries like Hamcrest, AssertJ, etc. to use a common set of
exceptions that IDEs and build tools can support in a consistent manner
across all testing scenarios -- for example, for consistent handling of
failed assertions and failed assumptions as well as visualization of
test execution in IDEs and reports.

This package this a dependency of JUnit 5. It'll be maintained
by the Java Team.
--- End Message ---
--- Begin Message ---
Source: opentest4j
Source-Version: 1.2.0-1

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

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

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated opentest4j package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Oct 2019 10:13:32 +0200
Source: opentest4j
Binary: libopentest4j-java
Architecture: source all
Version: 1.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libopentest4j-java - Open Test Alliance API
Closes: 941963
Changes:
 opentest4j (1.2.0-1) unstable; urgency=medium
 .
   * Initial release (Closes: #941963)
Checksums-Sha1:
 06bd776ec4382b56d82d9478118ce33e654f4e27 2005 opentest4j_1.2.0-1.dsc
 df077755577c90cc843b89a8a22e611f3f11c1e1 20664 opentest4j_1.2.0.orig.tar.xz
 71228fd47828f85f7cdd8a8c4ba7bbf06c5fe944 2700 opentest4j_1.2.0-1.debian.tar.xz
 59588f5307c288b7e040ad53c36c5c65fd7f9e4e 9044 
libopentest4j-java_1.2.0-1_all.deb
 c271feb78a8a3fcfe95c23e24b66ea64db5b838b 12131 
opentest4j_1.2.0-1_amd64.buildinfo
Checksums-Sha256:
 276e24ae0839cfc3ed9563858a119a8b82cc5dbca3dde95d4d1e887508e40e98 2005 
opentest4j_1.2.0-1.dsc
 77d9b1fcf0cd6edb7db14dc43bb4ae1cc11d7914e580814aaf76a1f86de223ed 20664 
opentest4j_1.2.0.orig.tar.xz
 de355d62638f8a5793282bece86548be51a6ea90a44e0074d8d67f8089f1e1b9 2700 
opentest4j_1.2.0-1.debian.tar.xz
 29cabd39a1b7acb15053f7368c349b5b30f49f519853096998b70d328404babd 9044 
libopentest4j-java_1.2.0-1_all.deb
 12286f1d4d69bb21fe24bf2725c73caecd0c5abc4256844b1d1f45e2bfbae2de 12131 
opentest4j_1.2.0-1_amd64.buildinfo
Files:
 200af69e9e3fb9b8eff01598ad08c3a6 2005 java optional opentest4j_1.2.0-1.dsc
 b1b639e4639b4948391c327e1836db0f 20664 java optional 
opentest4j_1.2.0.orig.tar.xz
 e1b205f2e492e7f63d5604c8f49f5714 2700 java optional 
opentest4j_1.2.0-1.debian.tar.xz
 ef8ed38d7f2be64b5218611aa1a70572 9044 java optional 
libopentest4j-java_1.2.0-1_all.deb
 9a387438d67f10dae78eeb0f53bf2f26 12131 java optional 
opentest4j_1.2.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAl2cR4AACgkQ9RPEGeS5
0KyL+g/+PH8+X/5ywdH730KaOo9QALRW9ZFi7k2jGybwIFdr133sAW2oODXUhmr9
R8OqX8fYHquUXmqhzwRa8rDBaRIl+2o0SmxfrDOw82LKaTTGPsu51jO5pMmaHOZB
WKGudyoPqmbcp7goYlwzaO+iDANRgEVvMCI+lFDSC0iUA5dRc5n7CFwm+w/yDoRU
bnZrsDWgErFbH5iKwqo/QIq/pCiJDfwwFn6JMqVB5e6gkyu3/qsbJSBdStvLfC48
A96mJBiY5jkPdCpOwKsseYYwZDq9exwQfbRwNcIdsBagAH3NQN7CC8rneQN3UbLa
bucUSI4bEBd5xPA5sq2F1VOhMvdrvxYkwfDqswWWqP3S4DC3loE2Ic2D1ZZy8lgs
fTEKId+ACiPmuDBcrP+QOALIkcMg+YlerY68JRSDqA+Bf1jLeiahFFEmbas+8V79

Bug#941965: marked as done (ITP: univocity-parsers -- Parsers for CSV, TSV and fixed width files)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 18:00:19 +
with message-id 
and subject line Bug#941965: fixed in univocity-parsers 2.8.3-1
has caused the Debian Bug report #941965,
regarding ITP: univocity-parsers -- Parsers for CSV, TSV and fixed width files
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.)


-- 
941965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Emmanuel Bourg 

* Package name: univocity-parsers
  Version : 2.8.3
  Upstream Author : Univocity Software Pty Ltd
* URL : https://www.univocity.com/pages/about-parsers
* License : Apache-2.0
  Programming Lang: Java
  Description : Parsers for CSV, TSV and fixed width files

univocity-parsers is a collection of extremely fast and reliable parsers
for Java. It provides a consistent interface for handling different file
formats, and a solid framework for the development of new parsers.

This package this a dependency of JUnit 5. It'll be maintained
by the Java Team.
--- End Message ---
--- Begin Message ---
Source: univocity-parsers
Source-Version: 2.8.3-1

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

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

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated univocity-parsers 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Oct 2019 10:39:49 +0200
Source: univocity-parsers
Binary: libunivocity-parsers-java
Architecture: source all
Version: 2.8.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libunivocity-parsers-java - Parsers for CSV, TSV and fixed width files
Closes: 941965
Changes:
 univocity-parsers (2.8.3-1) unstable; urgency=medium
 .
   * Initial release (Closes: #941965)
Checksums-Sha1:
 bcaa1b6ffcce9d73acb408aa67187c34b89aec9c 2099 univocity-parsers_2.8.3-1.dsc
 64ce73c00db2868af2969d951b2f311570d60584 362912 
univocity-parsers_2.8.3.orig.tar.xz
 a5d821dc44f741efec8a5cba0e4da224047e031c 2292 
univocity-parsers_2.8.3-1.debian.tar.xz
 3f815c3ddbeb5ff7e4efc9449b505bb32d882e32 392816 
libunivocity-parsers-java_2.8.3-1_all.deb
 fb505dc226c3f07cc6515a1b2c362076b7a2a2ef 13266 
univocity-parsers_2.8.3-1_amd64.buildinfo
Checksums-Sha256:
 90dd4b542ff97cb6f16b45379d76693bab20ad1d2f5c1924ba2b80fab0c8dc74 2099 
univocity-parsers_2.8.3-1.dsc
 1949150afe8227c8f9c690152edf5a8d857e9c27f86a663c54c9d1b2026b9898 362912 
univocity-parsers_2.8.3.orig.tar.xz
 77c142ff2282c4e7562d06d9ab1e16f7c95e34107ae367c369200cebf79a0105 2292 
univocity-parsers_2.8.3-1.debian.tar.xz
 61aa2eb2d19265288b4159d621e35352d093c09dbcb675ecdf6e5a6fbaceef18 392816 
libunivocity-parsers-java_2.8.3-1_all.deb
 7512f65918962aa5f1f18d35fd57a9ece88266c9d0b19b3b3cab0aad74614713 13266 
univocity-parsers_2.8.3-1_amd64.buildinfo
Files:
 cd8ef6c2038f1bbbd2860a8f44c9c046 2099 java optional 
univocity-parsers_2.8.3-1.dsc
 9802f07ea15325d4a486810f8dff60d0 362912 java optional 
univocity-parsers_2.8.3.orig.tar.xz
 33427617def3185fac479d68049e2583 2292 java optional 
univocity-parsers_2.8.3-1.debian.tar.xz
 a17ff879b21442f7a012e17c7c3f3916 392816 java optional 
libunivocity-parsers-java_2.8.3-1_all.deb
 576280596d3ec1de367c71f35798b126 13266 java optional 
univocity-parsers_2.8.3-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAl2cTWAACgkQ9RPEGeS5
0KzHHBAAp718KMgsmAeJyiEmvc5cCz0mdmF98yZrroOQUsCeRGyTvc+JEYslxvpn
xdtfDC8znsOkb/26jLHnXF1w5zY030ez/eUcfseAofYV5MuEDtJpDfXfeSy+TmzX
kgrk1+fBicE5rdVV0tw1aYr+WDumw8M4F2vaBIT5t24ia2DGfHBMb4pVrVGi6/z2
HTOiCMCHWq2zzCfMXJZFsbxS2TkZaC1hx/Lltvt3qGMByUlbrHnKt41de5pwhKG3
/9trN0XmVmejagWqeQi0eJWHGbF4Xk8nIvlVK1M6Am3bAZd1KOrIqCUtxdI6bbkF
ifDOPujzB/rSztOSanN6/TpBtFzD45b4xdnwi8WkodtSCgXhbTxUiLq5KDX46Uig
uYXbuO1NgGYl/FeIwrGGHJGqFz/p9hjvYSK99q+u7WvbNH5u92/zEL20Hdh1fxmv
/D0ukxrJxRaPoMl5Gm6VxV0p1zXP8JqPJc0uRtb1tKjv/NcRCLJop7RAfCVzM9YV

Bug#933350: marked as done (ITP: ceph-iscsi -- common logic and CLI tools for creating and managing LIO gateways for Ceph)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 18:00:13 +
with message-id 
and subject line Bug#933350: fixed in ceph-iscsi 3.2-1
has caused the Debian Bug report #933350,
regarding ITP: ceph-iscsi -- common logic and CLI tools for creating and 
managing LIO gateways for Ceph
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.)


-- 
933350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Sebastien Delafond 

* Package name: ceph-iscsi
  Version : 3.2
  Upstream Author : The Ceph iSCSI Project Developers
* URL : https://github.com/ceph/ceph-iscsi
* License : GPL-3
  Programming Lang: Python
  Description : common logic and CLI tools for creating and managing LIO 
gateways for Ceph

It includes the rbd-target-api daemon which is responsible for
restoring the state of LIO following a gateway reboot/outage and
exporting a REST API to configure the system using tools like
gwcli. It replaces the existing 'target' service.

There is also a second daemon rbd-target-gw which exports a REST API
to gather statistics.

It also includes the CLI tool gwcli which can be used to configure
and manage the Ceph iSCSI gateway, which replaces the existing
targetcli CLI tool. This CLI tool utilizes the rbd-target-api server
daemon to configure multiple gateways concurrently.
--- End Message ---
--- Begin Message ---
Source: ceph-iscsi
Source-Version: 3.2-1

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

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

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

Debian distribution maintenance software
pp.
Sebastien Delafond  (supplier of updated ceph-iscsi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Sep 2019 08:46:44 +0200
Source: ceph-iscsi
Binary: ceph-iscsi
Architecture: source all
Version: 3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Freexian Packaging Team 
Changed-By: Sebastien Delafond 
Description:
 ceph-iscsi - common logic and CLI tools for creating and managing LIO gateways
Closes: 933350
Changes:
 ceph-iscsi (3.2-1) unstable; urgency=medium
 .
   [ Mathieu Parent ]
   * Add debian/gbp.conf
   * Add debian/watch
   * Rename package ceph-iscsi
   * Install gwcli manpage
   * Add "Debian pipeline for Developers"
   * piuparts fails because tcmu-runner is not yet in sid
   * Add init.d services
   * Replace /etc/sysconfig/ceph by /etc/default/ceph in service files
   * Fix skip-systemd-native-flag-missing-pre-depends
 .
   [ Sébastien Delafond ]
   * Remove piuparts override now that tcmu-runner is in sid
   * First release (Closes: #933350)
Checksums-Sha1:
 0f7175ec636e4331e5649d41c15a58834f051c93 1610 ceph-iscsi_3.2-1.dsc
 e670b2d2f7149159bef259f1e2da940adebd1d22 100088 ceph-iscsi_3.2.orig.tar.xz
 63ff2f51648e9ec47565699e395af1585abaf82b 2668 ceph-iscsi_3.2-1.debian.tar.xz
 bc415d447506e3dd9db015276b979a26c30a8851 90412 ceph-iscsi_3.2-1_all.deb
 b9dcde56609264ce1dcb0b896978ad620e8a76bf 5856 ceph-iscsi_3.2-1_amd64.buildinfo
Checksums-Sha256:
 71d8127c8795e958cc9fb043df334ecc1820e4cc0f15e225b27d9054af9382f9 1610 
ceph-iscsi_3.2-1.dsc
 6469aaad7835734e3891a82efb7b7549f2e546b3a6d0b28e3faa906ffdeae4cf 100088 
ceph-iscsi_3.2.orig.tar.xz
 bcb89ec8afcf2571c5426a8c829a1ec21e0226ff795e62ab5217652eabf74b66 2668 
ceph-iscsi_3.2-1.debian.tar.xz
 50071c912bdcae36922794ee66e1db9d97c7ecd15776c8eca64ce828c7615bd8 90412 
ceph-iscsi_3.2-1_all.deb
 7b0b0b030d6d1496dfe9b2ede945253bc8a939d7472ac2bacabd2f15c4a8e9f1 5856 
ceph-iscsi_3.2-1_amd64.buildinfo
Files:
 b2432020dacb32d8ec8f2d7a7eb0a215 1610 python optional ceph-iscsi_3.2-1.dsc
 e1b431c95d20ca505d552e81a3e115bc 100088 python optional 
ceph-iscsi_3.2.orig.tar.xz
 8d0a0ef63c521347825c15510e4dba19 2668 python optional 
ceph-iscsi_3.2-1.debian.tar.xz
 3142cb9d7e47fbd30fd5e6b8e5929e7a 90412 python optional ceph-iscsi_3.2-1_all.deb
 aa8f54f967ea5bf555beed92b369a3e0 5856 python optional 
ceph-iscsi_3.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#930979: marked as done (ITP: membernator -- Tool to scan membership cards to establish if they are valid)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 18:00:17 +
with message-id 
and subject line Bug#930979: fixed in membernator 1.0.1-1
has caused the Debian Bug report #930979,
regarding ITP: membernator -- Tool to scan membership cards to establish if 
they are valid
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.)


-- 
930979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930979
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Louis-Philippe Véronneau 


Package name: membernator
Version : 1.0.1
URL : https://gitlab.com/baldurmen/membernator
License : ISC
Programming Lang: Python
Description : Tool to scan membership cards to establish if they are
  valid

membernator is a tool that can be used to scan membership cards and
establish if they're valid or not against a CSV database. It relies on a
graphical user interface and can be used by typing IDs manually or using
a barcode scanner.

My packaging efforts can be found at:
https://salsa.debian.org/python-team/applications/membernator

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: membernator
Source-Version: 1.0.1-1

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

Debian distribution maintenance software
pp.
Louis-Philippe Véronneau  (supplier of updated membernator 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Aug 2019 15:24:09 -0400
Source: membernator
Binary: membernator
Architecture: source all
Version: 1.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Louis-Philippe Véronneau 
Description:
 membernator - Tool to scan membership cards to establish if they are valid
Closes: 930979
Changes:
 membernator (1.0.1-1) unstable; urgency=medium
 .
   * Initial release (Closes: #930979)
Checksums-Sha1:
 2a9f7791635fd8ffe6093134f98ce6b6cd6f9eaa 2105 membernator_1.0.1-1.dsc
 4e82e75e20d5e12cdc7bb058b31c7570b8c17048 6560 membernator_1.0.1.orig.tar.xz
 fde8652cbcaf868a332e1225a2fd48342b633662 8172 membernator_1.0.1-1.debian.tar.xz
 80d6e6e78e51c4c6aec0d592834e8d27a07eaa20 7712 membernator_1.0.1-1_all.deb
 614151f57e711c7b73046f17d6521023f07368d0 8308 
membernator_1.0.1-1_amd64.buildinfo
Checksums-Sha256:
 5f3384e0017693caff8b678a3de795814bee08d8fb3685a8c036d27b68314e4e 2105 
membernator_1.0.1-1.dsc
 13b75597ef97c2ade0b80ad99ab06b97c1c7a5f477ee464bce01aad1dbaef1d4 6560 
membernator_1.0.1.orig.tar.xz
 4e047b30a39f085fd7b7fb168829d1290f15ed89624c68216c4b5614b784f2ef 8172 
membernator_1.0.1-1.debian.tar.xz
 bcd1560198856c947f69ee28e872ceb3c340d0afb2e5e21429ed7b8661a58abd 7712 
membernator_1.0.1-1_all.deb
 2452ba26fe0ed54d6c4bcb46cb9a18512a8170437f500126d9d6e459e0c075a2 8308 
membernator_1.0.1-1_amd64.buildinfo
Files:
 7715412cfbe62fe2a483f099792256a6 2105 misc optional membernator_1.0.1-1.dsc
 ff4a9ec5e602867fe10bffe6ef2a5b30 6560 misc optional 
membernator_1.0.1.orig.tar.xz
 712aa9b6ce49a97875b4f3855fa4d8ed 8172 misc optional 
membernator_1.0.1-1.debian.tar.xz
 b880773decba2267ec847ba5b108 7712 misc optional membernator_1.0.1-1_all.deb
 601184f0db583fa1929b7837ca5796ff 8308 misc optional 
membernator_1.0.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAl1/hpUPHGpjY0BkZWJp
YW4ub3JnAAoJELAdGnKsjcmhXDcP/2TXYLn+RdRUotBm+xQGIo9q4zMhZ8h8a3w4
lUwmLRItyQcs7m6M9J+UftgGLSyl2iDv86TTx9r0kyUtX90B7WEvOY1cmLWZNUI6
RL65rxX46SJgI3I5M6k5HYGPVrhflw/Ptwi4ai2vKt/IiFXj6cqOo3vwxzwwxVi/
OeC/SffYTvnMjlFzfHd9OgcEdF2UyonJoOALebLT7yFt0W2iGMpROYYK+5YD/KL3
4HBg9u4EdoMWFYHoQmN4ABAMBUu/DbOJj+4RXdE6pwWuSsXP4eF5UWboSEfosjFk
EE9VjZDGBzLLLvvTkiFdRcDmRN0VEeGcC3Cb0/2BjBv0MlFRQsKYXJrlK6argu/q
dfvJMUdChTGz01rJMrCuBiV+tkpb52zk46S9d51gaYN+q5ev5a8M6LjXbEBpt0oD
imYCvX9rhVbn9tvbe61ITu+2UM29z+OVIE9bCUwxMGejjhFoJBd8l5Fug7RzRS4B

Bug#941976: marked as done (ITP: apiguardian -- Level of stability annotation for frameworks or applications)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 18:00:12 +
with message-id 
and subject line Bug#941976: fixed in apiguardian 1.1.0-1
has caused the Debian Bug report #941976,
regarding ITP: apiguardian -- Level of stability annotation for frameworks or 
applications
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.)


-- 
941976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Emmanuel Bourg 

* Package name: apiguardian
  Version : 1.1.0
  Upstream Author : Marc Philipp, Sam Brannen
* URL : https://github.com/apiguardian-team/apiguardian
* License : Apache-2.0
  Programming Lang: Java
  Description : Level of stability annotation for frameworks or applications

API Guardian provides the @API annotation that is used to annotate public
types, methods, constructors, and fields within a framework or application
in order to publish their status and level of stability and to indicate
how they are intended to be used by consumers of the API.

This package this a dependency of JUnit 5. It'll be maintained
by the Java Team.
--- End Message ---
--- Begin Message ---
Source: apiguardian
Source-Version: 1.1.0-1

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

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

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated apiguardian package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Oct 2019 12:27:26 +0200
Source: apiguardian
Binary: libapiguardian-java
Architecture: source all
Version: 1.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libapiguardian-java - Level of stability annotation for frameworks or 
applications
Closes: 941976
Changes:
 apiguardian (1.1.0-1) unstable; urgency=medium
 .
   * Initial release (Closes: #941976)
Checksums-Sha1:
 8a0e917b99c88f800d1281b33c5ff2b3aefa264b 2020 apiguardian_1.1.0-1.dsc
 98da86bc8d89731a4ada277f62d005503c86bb1b 9788 apiguardian_1.1.0.orig.tar.xz
 27502a787e7ac5cbe5fc21ed4d2497475f1cf846 1960 apiguardian_1.1.0-1.debian.tar.xz
 15cbaa493d4ecd620db130851a73c4d01025462c 12141 
apiguardian_1.1.0-1_amd64.buildinfo
 e4623f212f0fdff4438f10af5ce06aae9fc532f8 3940 
libapiguardian-java_1.1.0-1_all.deb
Checksums-Sha256:
 4219ef0d66008cf689d59970b4e2191a6845fb6e1af53289681929bd37a62a83 2020 
apiguardian_1.1.0-1.dsc
 c3cb62b6c844785f455da77fd59940aeb4065afe5e487772b9c2267f0717ec5e 9788 
apiguardian_1.1.0.orig.tar.xz
 aaa284ba00ed14333c8211e3ba13fc20157c32fef2bd2f285673f405451e08b2 1960 
apiguardian_1.1.0-1.debian.tar.xz
 0ded90cd3e1a0ff7ebc16e2de4521473c4584b4869a4ffce76fabcdc7e331e7c 12141 
apiguardian_1.1.0-1_amd64.buildinfo
 1cdc1c1ff609167ad0b21801bbedecf3b38b3a03b79088cc60de634fe50db834 3940 
libapiguardian-java_1.1.0-1_all.deb
Files:
 6309cfffa1a6597942c210c8a153abe3 2020 java optional apiguardian_1.1.0-1.dsc
 00739de61878d11d2413c84504e547d9 9788 java optional 
apiguardian_1.1.0.orig.tar.xz
 fef52f323a4b395c1aaa7e4322b62abd 1960 java optional 
apiguardian_1.1.0-1.debian.tar.xz
 cdcc3612348f7c698b978bd911210b6a 12141 java optional 
apiguardian_1.1.0-1_amd64.buildinfo
 b8d5285ef903c4cfb80365ac7f782e80 3940 java optional 
libapiguardian-java_1.1.0-1_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAl2cZUsACgkQ9RPEGeS5
0KzLuQ/+KJsZXNnIVD7sWeGqbA/Av8mwIwZLaVmNER750KoYdD8YBFXwBOPZQH3F
a4xb+l7GfTSA12LZnLOonFbJjR9CMTbTH9sGYn8yNW42crUoJbWpEhFt/Xig40WM
jRZv7TzxhrTxjRfmHnx0jCeczkFv+rndUkPrIrAokFJ72K5Ko+ALTG5HDqoTMgHr
boSTuYiJgoETw52IFg2i2kalfVuZXoJAQlw4D5wdfUFewK0W0STM463jKNR9Uari
WbkSV1cwUW4F/HxtTdOYSMoMfjxPIOQT27V8V35sxmAveLZa5eztOSzgMJUK52A2
jn5KOAH9oZbbPbizcF4gzIojNy8hHCKXODMsHknHeMnM3fVgBKKRuvs1kgZkp7zz
5VQPbQeUcQozVyP4M0Z1MMioRDcd3+V6k1rTje8zIdhSc85uq7+sqoFev9D+c1/k
KYS/k2YJis2BJNdCN0EppHqEV1Q3X3bmLjr3wfqNutI4SV2gZHl9PfpGvTGKmSeO
a8rrun0UeEGH4QTMDeb7qfhURJJkAW1LC8+sezSetjrQ0BHCjueRIRsI2flBld90

Bug#935785: marked as done (ITP: eckit -- C++ toolkit for ECMWF tools and Applications)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 18:00:14 +
with message-id 
and subject line Bug#935785: fixed in eckit 1.1.1-1
has caused the Debian Bug report #935785,
regarding ITP: eckit -- C++ toolkit for ECMWF tools and Applications
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.)


-- 
935785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Alastair McKinstry 

* Package name: eckit
  Version : 1.1.1
  Upstream Author : European Centre for Medium-Range Forecasts 

* URL : http://github.com/ecmwf/eckit
* License : Apache 2
  Programming Lang: C++
  Description : C++ toolkit for ECMWF tools and Applications

ecKit is a cross-platform c++ toolkit that supports development of tools and 
applications at ECMWF. It is based on code developed over the last 20 years 
within the MARS software and was re-factored out to be reused by other 
applications. It provides a an abstraction layer on top of the operating 
system, so it is easier to port code to new architectures. It is developed 
taking into account the robustness requirements of running production systems 
at ECMWF. The main focus is UNIX/POSIX systems, and it has been thoroughly 
tested on AIX, Linux and Mac OSX. Historically, the code base pre-dates and in 
some way can be seen as a leaner substitute for some 'Boost' libraries.

It features facilities to easily handle, in a cross-platform way:

multi-threading
json and yaml parsing
object serialization and persistence
configuration of user options and resources
file-system abstraction
regular expressions
socket networking
http protocol
type-to-type conversions
asynchronous IO
asynchronous processing
exception handling and stack dumping
MPI object-oriented wrapper
linear algebra abstraction with multiple backends (BLAS, MKL, Armadillo, 
Eigen3)
advanced container classes
space partition trees
file-mapped arrays


libeckit is currently already used in several ECMWF packages on Debian 
(metview, odb-api) and provided in odb-api.
This will refactor it out as a shared library.
--- End Message ---
--- Begin Message ---
Source: eckit
Source-Version: 1.1.1-1

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

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

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated eckit 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: Tue, 01 Oct 2019 16:10:53 +0100
Source: eckit
Binary: libeckit-dev libeckit-utils libeckit-utils-dbgsym libeckit0d 
libeckit0d-dbgsym
Architecture: source amd64
Version: 1.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libeckit-dev - Fortran toolkit for interoperating Fortran with C/C++
 libeckit-utils - Library Fortran toolkit for interoperating Fortran with C/C++
 libeckit0d - Library Fortran toolkit for interoperating Fortran with C/C++
Closes: 935785
Changes:
 eckit (1.1.1-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #935785)
Checksums-Sha1:
 bde0d3026a42765ee930697c2f07efe067fed55a 1982 eckit_1.1.1-1.dsc
 b124e0d9118477e38d595b0ae984e06cb3622f81 636671 eckit_1.1.1.orig.tar.gz
 d1b59a81dd9a456b235f559d82a8306f0c7547d6 3088 eckit_1.1.1-1.debian.tar.xz
 d8a3d4009ed4edd1cc1ea50b36d91155d75a6b2e 8395 eckit_1.1.1-1_amd64.buildinfo
 7ead110673aba9181b9e45f32f22913ca4e0d32a 168920 libeckit-dev_1.1.1-1_amd64.deb
 547c839cba105f0c0462e5fe2e65a8d74fd3e899 31308 
libeckit-utils-dbgsym_1.1.1-1_amd64.deb
 2af6971b8e3181c67f07c185372ffad38ef48004 6968 libeckit-utils_1.1.1-1_amd64.deb
 79e913e3ee633e8918c0ea0aafb9bab4f2feb03b 7422316 
libeckit0d-dbgsym_1.1.1-1_amd64.deb
 70a08a6a36fb5760095a35df073088231f5d8917 781288 libeckit0d_1.1.1-1_amd64.deb
Checksums-Sha256:
 46f03e91c792228d12b1090ee48e1fd99f95cb132d46da2928088c943e847c43 1982 
eckit_1.1.1-1.dsc
 

Bug#940094: marked as done (ITP: mmtf-java -- Java API for macromolecular transmission format encoder/decoder)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 18:00:18 +
with message-id 
and subject line Bug#940094: fixed in mmtf-java 1.0.9-1
has caused the Debian Bug report #940094,
regarding ITP: mmtf-java -- Java API for macromolecular transmission format 
encoder/decoder
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.)


-- 
940094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940094
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Owner: Andrius Merkys 
Severity: wishlist

* Package name    : mmtf-java
  Version : 1.0.9
  Upstream Author : RCSB PDB
* URL : https://github.com/rcsb
* License : Apache-2.0
  Programming Lang: (C, C++, C#, Perl, Python, etc.)
  Description : Java API for macromolecular transmission format
encoder/decoder
 The Macromolecular Transmission Format (MMTF) is a compact binary format to
 transmit and store biomolecular structures for fast 3D visualization and
 analysis.

mmtf-java is a dependency of DataWarrior which I intend to package.

Remark: This package is to be maintained with Debichem Team at
   https://salsa.debian.org/debichem-team/mmtf-java
--- End Message ---
--- Begin Message ---
Source: mmtf-java
Source-Version: 1.0.9-1

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

Debian distribution maintenance software
pp.
Andrius Merkys  (supplier of updated mmtf-java package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 08 Aug 2019 01:54:07 -0400
Source: mmtf-java
Binary: libmmtf-java
Architecture: source all
Version: 1.0.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Andrius Merkys 
Description:
 libmmtf-java - Java API for macromolecular transmission format encoder/decoder
Closes: 940094
Changes:
 mmtf-java (1.0.9-1) unstable; urgency=medium
 .
   * Initial release (Closes: #940094)
Checksums-Sha1:
 5d0200b84fe86981d432afe3948c49730a4f415c 2132 mmtf-java_1.0.9-1.dsc
 34a4979dc88ca6a5c86af3f7a83e10b1043740a4 6422256 mmtf-java_1.0.9.orig.tar.xz
 257e254f2e955a8908304f9d0fc0a252ee8823c3 5772 mmtf-java_1.0.9-1.debian.tar.xz
 9a7cd4cfe16fbfc18833ddfe7c98fdce5fe68d40 186536 libmmtf-java_1.0.9-1_all.deb
 c05810666e081154247eff36da8a925a05475e49 13251 
mmtf-java_1.0.9-1_amd64.buildinfo
Checksums-Sha256:
 2c5c68066ca9a47c25f99dc011b574355494a25e5f54c3f9e060a91356792bef 2132 
mmtf-java_1.0.9-1.dsc
 86911b9650aa5da1561ee4b6f135cd6f1e1dda45231d3a91d0a5d21259f3238b 6422256 
mmtf-java_1.0.9.orig.tar.xz
 3ee7fd1eb5c5f5883913fb867e8c65bdba7484b8748a76169fbf0e1878e920f6 5772 
mmtf-java_1.0.9-1.debian.tar.xz
 4f1f959bd94d7a2d485da0469e7c7bac12a3ff45e93e6a4f2bfcff1bc623f811 186536 
libmmtf-java_1.0.9-1_all.deb
 654a71831b084ab3c89d17aa1e65de2cfdd837b12af5a01a4238a685c5a28f9b 13251 
mmtf-java_1.0.9-1_amd64.buildinfo
Files:
 326c124d10abce9f2f2d3167d1428c11 2132 science optional mmtf-java_1.0.9-1.dsc
 0d9a08fc7bdc63d5b95143b74fd0320a 6422256 science optional 
mmtf-java_1.0.9.orig.tar.xz
 a3c350efd32aec2f3dd8ea80b1fa8f7a 5772 science optional 
mmtf-java_1.0.9-1.debian.tar.xz
 dedcef786db25aaf9abd2f6ca56e7fa9 186536 java optional 
libmmtf-java_1.0.9-1_all.deb
 61935451b5f46800fb0d1699111ff022 13251 science optional 
mmtf-java_1.0.9-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAl16HPQSHG1lcmt5c0Bk
ZWJpYW4ub3JnAAoJEOX0P5wnNPKHKjkQAIGmN5ir9ybt0E6JcO+xEJ3UkkKsk5gU
kUIUrxcD7mc+DDfAomITrXE2FebsB4tQkTniWimOn8AZ+mltdw6k6/S2vvIfi5Fk
qNXN7rFjPcEG2Ix5GLw/0/VR4MBaC2Ncl8e9h9qZi+jHyD88vTnKlF8j9fqqxxT+
Fr2rC5JZNCqXQlHjH8ytmCEJQGwH/roPPVCeuBX/esglmMmWFbSnADNLnKKdtwG/
5Jct4Z7v3b+CR3dEWUQ++tjTyZ8v5nppJuzxKw6LbLGAlFe8I0jpeacpRbp7lMx3
Xy1wlFCs5BzGuG+er56kUir0A/hvCvvPj+zPjtwyVt9L19tOf6K8aYWcdoeVuXAu
jUSLQVr7nqQy3xp/+ua1lDWQDGh//llyyrgtZQbvIt6SdP5yYaqV2tsXM6LPLiNP
Ayqc+QY9ZuGIEuNtpu0lVNQHGWjGSuc3lhAR9LF9tcZoF2QI8LigonyuyjzS1AZD
kTcwBVwLrt+ucxiaYMgJMAm8FTwwDGJRieKcL/IfN5WX7DmCU/OxNwpgNjil4Fcy
ax1zBYtubU7MFFNEzgfNUq9fmz4QSaJ7hzc59B/LDLawkMr35WY9tU4LWTogsGPy

Bug#934964: marked as done (ITP: afl++ -- security related binary fuzzer (fork of american Fuzzy Lop))

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 18:00:12 +
with message-id 
and subject line Bug#934964: fixed in aflplusplus 2.53c-1
has caused the Debian Bug report #934964,
regarding ITP: afl++ -- security related binary fuzzer (fork of american Fuzzy 
Lop)
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.)


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

* Package name: afl++
  Version : 2.53c
  Upstream Author : Marc Heuse 
* URL : https://github.com/vanhauser-thc/AFLplusplus
* License : Apache-2.0
  Programming Lang: C
  Description : security related binary fuzzer (fork of American Fuzzy Lop)

This is a fork of American Fuzzy Lop [1], which isn't actively further developed
anymore [2]. The latest release of AFL++ includes a lot new features, fixes and
improvements.

Packaging this would replace AFL in the Debian archive [3], which doesn't build 
with
LLVM >= 7 [4], and therefore is going to be removed so that LLVM 6 could be 
finally
dropped.

Thanks,
Daniel Stender

[1] https://github.com/google/afl

[2] https://twitter.com/Dor3s/status/1154737061787660288

[3] https://tracker.debian.org/pkg/afl

[4] https://bugs.debian.org/912785
--- End Message ---
--- Begin Message ---
Source: aflplusplus
Source-Version: 2.53c-1

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

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated aflplusplus package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 17 Sep 2019 10:52:07 +0200
Source: aflplusplus
Binary: afl++ afl++-clang afl++-clang-dbgsym afl++-dbgsym afl++-doc
Architecture: source amd64 all
Version: 2.53c-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Raphaël Hertzog 
Description:
 afl++  - instrumentation-driven fuzzer for binary formats
 afl++-clang - instrumentation-driven fuzzer for binary formats - clang support
 afl++-doc  - instrumentation-driven fuzzer for binary formats - documentation
Closes: 934964
Changes:
 aflplusplus (2.53c-1) unstable; urgency=medium
 .
   [ Raphaël Hertzog ]
   * Team upload.
   * Fix Vcs-Git and Vcs-Browser URLs.
   * Note for ftpmasters: the source package contains a number of binary-only
 files in the "testcases" and "docs/vuln_samples/" subdirectories. We
 believe that they are their own sources as they have been manually crafted
 to meet specific requirements. Those files were already part of the former
 "afl" package that recently got removed. Thank you.
 .
   [ Sophie Brun ]
   * Initial releases (Closes: #934964)
   * Add more info in patches
Checksums-Sha1:
 a1462ea38628628a37eb9f33003d9b42b672fb97 1857 aflplusplus_2.53c-1.dsc
 786b4ae0e6767b77ef5c3df5a1b4269420c85816 934915 aflplusplus_2.53c.orig.tar.gz
 94cac39b7432d291d079c77cc7f018144bc0537a 7852 aflplusplus_2.53c-1.debian.tar.xz
 388bd314329b6fe57b8a479d0b22a096ac080aea 313540 
afl++-clang-dbgsym_2.53c-1_amd64.deb
 8375d5a61124cb3cd46c3ce535f1b547d9ec5e8a 61872 afl++-clang_2.53c-1_amd64.deb
 d7d74fa4b83b523931b84d9db11c5a695d1b1c53 355228 afl++-dbgsym_2.53c-1_amd64.deb
 efb6699048c8f2900a13af6a9745c10eb2f6e5e6 127996 afl++-doc_2.53c-1_all.deb
 43d20ee5751737f56b95b23cdde1d4ec199e4cc6 162820 afl++_2.53c-1_amd64.deb
 2cb30e6772686712bc75112306aea4f30b5cfba7 6927 
aflplusplus_2.53c-1_amd64.buildinfo
Checksums-Sha256:
 a9624b181df03d63b46aa17f180b2a58ed66ebf67e2a2a6336219ad0a558040c 1857 
aflplusplus_2.53c-1.dsc
 3147d44f01378b46c4234090781e5cb13c9721a72701c28ed4f18b7256d452e7 934915 
aflplusplus_2.53c.orig.tar.gz
 404816cb19f151e1f7c141ef89585cfabbcbc864d98f3750c46b07d005f33b08 7852 
aflplusplus_2.53c-1.debian.tar.xz
 91c0b4a690764ab1660fc8528703b9a2d01e8717fcd3e5c40b2b477f2b264f42 313540 
afl++-clang-dbgsym_2.53c-1_amd64.deb
 58f72d92b7c03877a8f92190fad1037a2c757939615070afafe75004753f89a8 61872 
afl++-clang_2.53c-1_amd64.deb
 

Bug#934142: marked as done (ITP: python-in-toto -- software supply chain security framework)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 18:00:16 +
with message-id 
and subject line Bug#934142: fixed in in-toto 0.4.0-1
has caused the Debian Bug report #934142,
regarding ITP: python-in-toto -- software supply chain security framework
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.)


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

Please see corresponding RFS ticket for details (description, license, URLs):
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931013

-- 
lukas.puehrin...@nyu.edu
PGP fingerprint: 8BA6 9B87 D43B E294 F23E  8120 89A2 AD3C 07D9 62E8



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: in-toto
Source-Version: 0.4.0-1

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

Debian distribution maintenance software
pp.
Lukas Puehringer  (supplier of updated in-toto 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 11 Sep 2019 14:52:01 +0100
Source: in-toto
Binary: in-toto
Architecture: source all
Version: 0.4.0-1
Distribution: unstable
Urgency: low
Maintainer: in-toto developers 
Changed-By: Lukas Puehringer 
Description:
 in-toto- software supply chain security framework
Closes: 934142
Changes:
 in-toto (0.4.0-1) unstable; urgency=low
 .
   * Initial Debian release. (Closes: #934142)
Checksums-Sha1:
 773570d44e59bf3af07c8090c9930ea31b9998dd 2450 in-toto_0.4.0-1.dsc
 dafed4ecad63137c36c232c60260dc222dae66f6 169677 in-toto_0.4.0.orig.tar.gz
 7579e84480e0f5a59049f55c64a606e221da3e30 874 in-toto_0.4.0.orig.tar.gz.asc
 936cfcf5058b60431f627ae190840222540fd42b 8660 in-toto_0.4.0-1.debian.tar.xz
 743d8b945bf49e887eac59b374d5e30fb419acdb 65384 in-toto_0.4.0-1_all.deb
 b652a9cedc7cef107365b2141dfc26eed00ca9e3 7586 in-toto_0.4.0-1_amd64.buildinfo
Checksums-Sha256:
 5c52e1283e245cddc5ffda6337aa213355287c217fff1b093510350dcbeea6b9 2450 
in-toto_0.4.0-1.dsc
 cf400aa0eb637df919c908902e06b1c41bb46d8c085ddaa4d95ae83f5ca6def4 169677 
in-toto_0.4.0.orig.tar.gz
 24f31238bee364714240840532776ad998597461990f3209f25a25e3283b612f 874 
in-toto_0.4.0.orig.tar.gz.asc
 0705c7331173680b27dce0f544fa43b1c007451f98841855b2c1c88e13944945 8660 
in-toto_0.4.0-1.debian.tar.xz
 0b9ab829b0a7be94d878325c875ed7b2d7ad8628c0a0f0a1ba1623825a497d0b 65384 
in-toto_0.4.0-1_all.deb
 4edf0e72034f62b66f0965581701eaa88aac745e70075a425e435238938f92cf 7586 
in-toto_0.4.0-1_amd64.buildinfo
Files:
 76a0dd614759dd6ff4286f6ef062244e 2450 utils optional in-toto_0.4.0-1.dsc
 892d0462e770a997b770b68df1f71726 169677 utils optional 
in-toto_0.4.0.orig.tar.gz
 bd84b068c7c7a57d9a0cb7f7bcb35349 874 utils optional 
in-toto_0.4.0.orig.tar.gz.asc
 bf44de822564b29cf7bfdb4d43922bf0 8660 utils optional 
in-toto_0.4.0-1.debian.tar.xz
 d5ff51c9c4cf203a99e681c2dfd37252 65384 utils optional in-toto_0.4.0-1_all.deb
 0ebb3fd696f92ac9893c9805c02aa643 7586 utils optional 
in-toto_0.4.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAl2Thk0ACgkQCRq4Vgaa
qhwK8A/+JOmu179sajNxfHGwXTcICB3KOun2Tk+BMatWUgDJdvQH2wLply3VRddX
h8sS4Gk5hwEw+Hu+UK0M441lNfi39VMRJ+2nN/KdYhuMsfwAZA3rWl42lQFcCIzH
Yu80l4WVBAoFi52uL18tZqmm+A5gcv9HpqDxviOmrZlFgiWYx7Ri7a7IRD2bnYSn
vGB33mEnUmuCAOgXg03iU8DZjWItCSi5z6qzXId3AutJJbntIYvNgDF5pU84YKbD
LV9YPs1B1b4thGS8HewaaU1ssIOGQkD4bbhmqwEf/afZm1OC7L1gi2K5TZUUwE4r
FXEgf9oUhCxmHYs1hAkJ0mnWYWTtbou2+DxT0774MDxS/OS0Rua9dDIJ6Jb5pTG3
ueuvpkHRSraLXs4WxOBFlvARO53FrRKH/ecNroQIPnaPIhxZokqGH007usjTQ/ZZ
Qn9ofczuePZa93UNv6sWpGK47o9O/UexcDgtjOhFBlIIMProBS0UCK/yMiij6R81
IurTgqE0fQw3KrfuSTSwfl+FuUwfvriFO+W/Rsmxor1uc8Kz955nySujg7EnRVEB
JJYP/TBOMcYCjR3KZ1VSM13xt9bODAvPfxuOPcBuR+6ReX8gWbALkcOsSW6lnm8I
Wh+idq19029Qg8Xtga5lPHAKGzy2HPn41PQQTus73/2i56I9ysQ=
=6vbE
-END PGP SIGNATURE End Message ---

Bug#940049: marked as done (ITP: pd.build-cmake-module -- Pure Data CMake Module)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 18:00:19 +
with message-id 
and subject line Bug#940049: fixed in pd.build-cmake-module 0.1.0~ds1-1
has caused the Debian Bug report #940049,
regarding ITP: pd.build-cmake-module -- Pure Data CMake Module
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.)


-- 
940049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: IOhannes m zmölnig (Debian/GNU) 

* Package name: pd.build-cmake-module
  Version : 0.1
  Upstream Author : Pierre Guillot
* URL : https://github.com/pierreguillot/pd.build
* License : GPL-3
  Programming Lang: CMake
  Description : Pure Data CMake Module

 Pure Data (also known as Pd) is a real-time graphical programming environment
 for audio and graphics processing.
 It can be easily extended with so called 'externals'
 .
 This package contains a CMake Module for building such externals.

This package is part of the ongoing attempt to package the Pure Data microcosm
for Debian (and a prerequisite of the update of the src:jsusfx package).
I intend to maintain the package under the multimedia-team umbrella.
--- End Message ---
--- Begin Message ---
Source: pd.build-cmake-module
Source-Version: 0.1.0~ds1-1

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
pd.build-cmake-module package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 13 Sep 2019 11:16:28 +0200
Source: pd.build-cmake-module
Binary: pd.build-cmake-module
Architecture: source all
Version: 0.1.0~ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Description:
 pd.build-cmake-module - Pure Data CMake Module
Closes: 940049
Changes:
 pd.build-cmake-module (0.1.0~ds1-1) unstable; urgency=medium
 .
   * Initial release (Closes: #940049)
Checksums-Sha1:
 a73a31b21855aa355c4238625a37b16074c52ea9 2122 
pd.build-cmake-module_0.1.0~ds1-1.dsc
 0652f00bed85b17bcd82612792444005f96e8403 35139 
pd.build-cmake-module_0.1.0~ds1.orig.tar.gz
 f5c763232ae1aac163dc7d1fc5bd9fdd676c7a2f 1764 
pd.build-cmake-module_0.1.0~ds1-1.debian.tar.xz
 9f4d39f06ce3e2becbb94f796a51d3575319e433 5952 
pd.build-cmake-module_0.1.0~ds1-1_all.deb
 61be06d1e1de6b15b7d21ce089400145e53af6f4 5588 
pd.build-cmake-module_0.1.0~ds1-1_amd64.buildinfo
Checksums-Sha256:
 62992b25b411789028d75ff37336626e668f52a57b52f9a485eeec5d25e303be 2122 
pd.build-cmake-module_0.1.0~ds1-1.dsc
 0f149001b14d2857f661870797cf77ae896ca23d8ddd8bdd36e5927bdf1ad488 35139 
pd.build-cmake-module_0.1.0~ds1.orig.tar.gz
 b314801c7e78bf01f64968c3b0ba8223881563f805acaece0101eea6358c7100 1764 
pd.build-cmake-module_0.1.0~ds1-1.debian.tar.xz
 8b15de64302d677dc6925e61063c46d3a16a650e613b3013de7740f74194c305 5952 
pd.build-cmake-module_0.1.0~ds1-1_all.deb
 a88607109872eb9ba4979859a04f964c5da5c775b0fb25a95a99d702b0fb18ef 5588 
pd.build-cmake-module_0.1.0~ds1-1_amd64.buildinfo
Files:
 1ec36434934a67f976956d588286b54d 2122 devel optional 
pd.build-cmake-module_0.1.0~ds1-1.dsc
 55a822a42beecd3588d15961ce7c49da 35139 devel optional 
pd.build-cmake-module_0.1.0~ds1.orig.tar.gz
 5783509889a5173f337c525d99d5bcd2 1764 devel optional 
pd.build-cmake-module_0.1.0~ds1-1.debian.tar.xz
 249e12800db9c57313cae3f43068a633 5952 devel optional 
pd.build-cmake-module_0.1.0~ds1-1_all.deb
 216a7cf14aff9dbc805f4c357ca41f15 5588 devel optional 
pd.build-cmake-module_0.1.0~ds1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAl17X1gACgkQtlAZxH96
Nvh/Sg//ZlL0ZTo6vwmfuEmU0BnhHHQUvXtWcV0nzUgDf12Puqe1Zl5SeTbCBDAo
Drlk09zIU0c7mcwnQV4G7JWbxIHJh1XaHS8MyDbaJybsvj5z7De8T2+FsVazmtQw
g7th402r7mIQBj24GovCI7IuYoOQwPAuE266fE6i3hYrknY0HssZmlvCva426djJ
r2UDr3S0tLLv/Cb2Fq5+3JWFUlMtKXQxRTjp/EdbPFvZ0BogLQi304GimXC0BaGc

Bug#934700: marked as done (ITP: lz4-java -- LZ4 compression for Java)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 18:00:17 +
with message-id 
and subject line Bug#934700: fixed in lz4-java 1.5.1-1
has caused the Debian Bug report #934700,
regarding ITP: lz4-java -- LZ4 compression for Java
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.)


-- 
934700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Owner: Saif Abdul Cassim 
Severity: wishlist

* Package name: liblz4-java
  Version : 1.3.0
* URL : https://github.com/lz4/lz4-java

* License : Apache-2.0
  Programming Lang: Java, C
  Description : LZ4 compression for Java

LZ4 compression for Java, based on Yann Collet's work available at
http://code.google.com/p/lz4/.

This library provides access to two compression methods that both generate
a valid LZ4 stream:

   - fast scan (LZ4):
  - low memory footprint (~ 16 KB),
  - very fast (fast scan with skipping heuristics in case the input
  looks incompressible),
  - reasonable compression ratio (depending on the redundancy of the
  input).
   - high compression (LZ4 HC):
  - medium memory footprint (~ 256 KB),
  - rather slow (~ 10 times slower than LZ4),
  - good compression ratio (depending on the size and the redundancy of
  the input).

The streams produced by those 2 compression algorithms use the same
compression format, are very fast to decompress and can be decompressed by
the same decompressor instance.
This is used for kotlin.
I plan on maintaining this along with debian-java team.
--- End Message ---
--- Begin Message ---
Source: lz4-java
Source-Version: 1.5.1-1

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

Debian distribution maintenance software
pp.
Saif Abdul Cassim  (supplier of updated lz4-java 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, 21 Sep 2019 09:43:31 +0200
Source: lz4-java
Binary: liblz4-java liblz4-jni liblz4-jni-dbgsym
Architecture: source all amd64
Version: 1.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Saif Abdul Cassim 
Description:
 liblz4-java - LZ4 compression for Java
 liblz4-jni - LZ4 compression for Java (JNI library)
Closes: 934700
Changes:
 lz4-java (1.5.1-1) unstable; urgency=medium
 .
   * Initial release (Closes: #934700)
Checksums-Sha1:
 9ed8f1f8e966ec4cdf731ef25c78a7c8e13b76e3 2196 lz4-java_1.5.1-1.dsc
 e2b6d9e388ff7a24c597e63b6fcdd918f39f1ddc 406604 lz4-java_1.5.1.orig.tar.xz
 132682125925fcce4a369abe3a106c232746cb0a 6380 lz4-java_1.5.1-1.debian.tar.xz
 0ff51807af75e3894ccdfdf419027a15f0e1ad5c 110128 liblz4-java_1.5.1-1_all.deb
 c3648c294cc087b4f22ad5887d7f6b8b18e9c5da 16280 
liblz4-jni-dbgsym_1.5.1-1_amd64.deb
 d99c3db416012018f17a61ee0a4f770c4e62da2b 8012 liblz4-jni_1.5.1-1_amd64.deb
 8bcf4117342e014de2135dc7ac0dc9660f1d536a 10058 lz4-java_1.5.1-1_amd64.buildinfo
Checksums-Sha256:
 069370427bdace637ffd5a8116163d0df117d704edf44ec592cd1df35e83d5d3 2196 
lz4-java_1.5.1-1.dsc
 027fe2756bf0845072bae78d4af413f035b50fd485e42a3b1e6ec71c9c426a44 406604 
lz4-java_1.5.1.orig.tar.xz
 12748cb8251f950f9c077b5c6f8b51fdd0ce0ea63b01f0c3345dd13e16755439 6380 
lz4-java_1.5.1-1.debian.tar.xz
 a5a20dd662dfb0375a443c4fdb36bdae25e139ec8cf5495091094881ceaebe6d 110128 
liblz4-java_1.5.1-1_all.deb
 84a98a773fbea795dce1babc5791e5495407b993f37cdd5f87dac99c5c05ca4b 16280 
liblz4-jni-dbgsym_1.5.1-1_amd64.deb
 320a174cce468963433b831b7f7f68dd115673cbde4ce782f5b91bf15dc22953 8012 
liblz4-jni_1.5.1-1_amd64.deb
 d9365146071269b7b11f4fcfb2198849cf97f19d7814de80e76abc44527802ad 10058 
lz4-java_1.5.1-1_amd64.buildinfo
Files:
 1e846dc4f539135dd80292ff231f2bb0 2196 java optional lz4-java_1.5.1-1.dsc
 844159e5f9efbb76af34ccc43e2ec59d 406604 java optional 
lz4-java_1.5.1.orig.tar.xz
 c92b84e12ce6c5e25b8d679976c740d4 6380 java optional 
lz4-java_1.5.1-1.debian.tar.xz
 b7e44af1fc28859712a36bb67bd5bcda 110128 java optional 

Bug#941938: marked as done (ITP: guava-mini -- utilities from Guava)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 18:00:15 +
with message-id 
and subject line Bug#941938: fixed in guava-mini 0.1.2-1~exp1
has caused the Debian Bug report #941938,
regarding ITP: guava-mini -- utilities from Guava
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.)


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

* Package name: libguava-mini-java
  Version : 0.1.2
  Upstream Author : David Moten
* URL : https://github.com/davidmoten/guava-mini
* License : Apache License 2.0
  Programming Lang: Java
  Description : utilities from Guava

Some popular utilities from Guava repackaged (with different package
names but same class names and method names) into a little jar (11K)
available on Maven Central.



It is a dependency of jax-maven-plugin which is a dependency of Jollyday
(ITP #939617


It should be maintained in the java-team

-- 
Mechtilde Stehmann
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: guava-mini
Source-Version: 0.1.2-1~exp1

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

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

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

Debian distribution maintenance software
pp.
Mechtilde Stehmann  (supplier of updated guava-mini 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 07 Oct 2019 21:16:23 +0200
Source: guava-mini
Binary: libguava-mini-java
Architecture: source all
Version: 0.1.2-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Mechtilde Stehmann 
Description:
 libguava-mini-java - utilities from Guava
Closes: 941938
Changes:
 guava-mini (0.1.2-1~exp1) experimental; urgency=medium
 .
   [ Mechtilde Stehmann ]
   * [2fc4050] Initial release (Closes: #941938)
   * [67bc9c7] New upstream version 0.1.2
Checksums-Sha1:
 d52b96aaeb91c992a124510f73cf0e522dd33b49 2014 guava-mini_0.1.2-1~exp1.dsc
 6a2523cccbb9bb12925e15dc5ed9eabb51d6971b 10820 guava-mini_0.1.2.orig.tar.gz
 e3c4f1e9028cfefcdd08aab65e28526c7e549931 2524 
guava-mini_0.1.2-1~exp1.debian.tar.xz
 12421f349d465dfb9880043a3107682b734bbda4 11948 
guava-mini_0.1.2-1~exp1_amd64.buildinfo
 27f643890fa52aabf5351e7ef9688e6389b86dc3 10832 
libguava-mini-java_0.1.2-1~exp1_all.deb
Checksums-Sha256:
 b0098999d5c3e8e33d3a1a94b352249fa61c5420acf0ce85200e8eb25a9d3997 2014 
guava-mini_0.1.2-1~exp1.dsc
 9df6aa9424d6ba86507c92dc7ce03e681cf195bc357153e0cc911982f3265401 10820 
guava-mini_0.1.2.orig.tar.gz
 f4c56daccbbb4d1a15007b44c03e56adb188db4583f1d423c0059a98432d151d 2524 
guava-mini_0.1.2-1~exp1.debian.tar.xz
 b3fe7e39b2e05e5ecbd7bdec9fccfe63dd79642c93a01ce57df97148920295ce 11948 
guava-mini_0.1.2-1~exp1_amd64.buildinfo
 dd053d9df670ad7df49c83e02881bec07d84a91590744519841b82105c773edf 10832 
libguava-mini-java_0.1.2-1~exp1_all.deb
Files:
 7c41e596aa2ea0fd2d116f288e69ecba 2014 java optional guava-mini_0.1.2-1~exp1.dsc
 1a256534af07ce56fa2ce4edc949cc54 10820 java optional 
guava-mini_0.1.2.orig.tar.gz
 9c9e50dc4da409d1b75d1ac74c9554ad 2524 java optional 
guava-mini_0.1.2-1~exp1.debian.tar.xz
 39fbbe4d4448bf0d6f170b18d662418a 11948 java optional 
guava-mini_0.1.2-1~exp1_amd64.buildinfo
 b79689c42b344021d91d7e273b0e5175 10832 java optional 
libguava-mini-java_0.1.2-1~exp1_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE8ON/Pch6SZgomTnn8od7uhQarX8FAl2bkpoACgkQ8od7uhQa
rX+f1g//Y1nT+v1qIQfcKtc8K+ZRUaG3gHMeU8t6pBudS2//FKaKvfO+VFS8NUa9
wckwy+kef+GkXD5E6VAP3bZ1rE8ttW4T9qLZO4BzmBf+5kjmJketX2GsXiHGsa6G
H77z9QeLhDN3IoaeP7/hulwn1SWifTRtpUNHTx5PnZ6sucH/YNWEVV9me5czAvts
N4KDPz9BSxv5gK29cIOSPtBCgDLTJO143mSjNr7SkcwAaldgovqPLhqx2t6Ccor3
xyyQQs0zJn+rk0q7e+Q1nhNo4VCw1qSSLbTKme/nK4/F3V6BcuD5n0kjJNTIYZy3
0epmlmd0AUfP/kNJmlagyl/PdSvWxLO4dFk/o0ZhgWyeIrrRosq15GaKuiBzqb6G
pwB9psAOyRmgU6U/YUVc07HKpNM1i86ktsZcYh6Wt/Y/BuVuHUO5Utwik14i56n0

Bug#941944: marked as done (ITP: zt-exec -- ZT Process Executor)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 18:00:20 +
with message-id 
and subject line Bug#941944: fixed in zt-exec 1.11-1~exp1
has caused the Debian Bug report #941944,
regarding ITP: zt-exec -- ZT Process Executor
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.)


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

* Package name: libzt-exec-java
  Version : 1.11
  Upstream Author : 
* URL : 
* License : Apache License 2.0
  Programming Lang: Java
  Description : ZT Process Executor

A lightweight library to execute external processes from Java



It is a deppendency of jax-maven-plugin which is a dependency of
jollyday (ITP: #939617)


It should be maintained in the java-team

Kind regards

-- 
Mechtilde Stehmann
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: zt-exec
Source-Version: 1.11-1~exp1

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

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

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

Debian distribution maintenance software
pp.
Mechtilde Stehmann  (supplier of updated zt-exec package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Oct 2019 19:00:30 +0200
Source: zt-exec
Binary: libzt-exec-java
Architecture: source all
Version: 1.11-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Mechtilde Stehmann 
Description:
 libzt-exec-java - ZT Process Executor
Closes: 941944
Changes:
 zt-exec (1.11-1~exp1) experimental; urgency=medium
 .
   [ Mechtilde Stehmann ]
   * [e390777] Initial release (Closes: #941944)
   * [42f59e4] New upstream version 1.11
Checksums-Sha1:
 1930beea4551636354326de2a79383a829305914 2028 zt-exec_1.11-1~exp1.dsc
 35a4ff20222cdc07b03762e1629b9893aab70bd6 91760 zt-exec_1.11.orig.tar.gz
 7e02e740b23adf97feafd0615517cdcc33c8bc17 2444 zt-exec_1.11-1~exp1.debian.tar.xz
 557d43a7e1ce390c1abcf88dcdcd57d8b20701e0 52544 
libzt-exec-java_1.11-1~exp1_all.deb
 565c8234062a56fbe66fe0ab40a8c74f61f04cf1 11913 
zt-exec_1.11-1~exp1_amd64.buildinfo
Checksums-Sha256:
 b0fe8cb71bac79703b5bc52ba26ad8b06d9eabd27e5dac9a0f78d1c0dd644998 2028 
zt-exec_1.11-1~exp1.dsc
 485668849ba169897781b4063c2ac47454139b8de6637868c10369902f2d0af1 91760 
zt-exec_1.11.orig.tar.gz
 df99b2bfeee36565a47fb05df505369694188f1bebfd4b1e421812f8254c6066 2444 
zt-exec_1.11-1~exp1.debian.tar.xz
 e543fc5ef21fe58bcef6e07d05f6b73a83672d6476d34e5f0132ffbbfe21e998 52544 
libzt-exec-java_1.11-1~exp1_all.deb
 c7fcf0314812f2d2776e111fa39cfc81aa96d7c37201f8f5a8971f1d2cc54c95 11913 
zt-exec_1.11-1~exp1_amd64.buildinfo
Files:
 c079b3268871c02081c89574bfdd7e3b 2028 java optional zt-exec_1.11-1~exp1.dsc
 b337b2fd6e2c7732137f0d9fdbd2da4e 91760 java optional zt-exec_1.11.orig.tar.gz
 2bf04abb438195b74b2dcc27c83117fc 2444 java optional 
zt-exec_1.11-1~exp1.debian.tar.xz
 6999c0cd5736d77730e68699d8afa8e8 52544 java optional 
libzt-exec-java_1.11-1~exp1_all.deb
 7dd97f4c0a5080bf8074373fbce22331 11913 java optional 
zt-exec_1.11-1~exp1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE8ON/Pch6SZgomTnn8od7uhQarX8FAl2cwbcACgkQ8od7uhQa
rX9qRRAAtBfSpe0Etikwv7HDuNw5MWdoN0J2HBD+oJA3mpxWcgnoczc6FwwqFfxS
swrOqNa0Z957+KlAkpTrXaWZONj6YNK10GyHlFupAkQdFpE39cpjP8JXkGRdRqaZ
7jwnUQX+KmTEHMU07zGqjjN9Q2cvQ/am/HTkaXHvT+eHbDbYcTJyaPRTQ+U0+VLm
Fs6ckxklRqi3psP2Qi0TsOTEx2+X9z25SLBnI3XH5R/jvqQFsr1GkHnML4b+u7pJ
QEiuQc07u/kR7f/LHf6raKl8ZoV1tJzlBl72EciuPcZDJZlkq6piv507zG0MVuNV
mJflRUo8+fRzatJ2GX8y1A6nozUuIQd8Kp3nRUnvCVcxirm93DDsTkxaznq7cGld
XdzvL6t6v2PGBj6qJ8PDUc5oxeueDyvDZLU9wjH4C0ifU5oT75svj8t4vbpQn/CA
+D/ceBzM+zV8xUJDXU17NAyDuXROg7ocFI3R0w4aaJcmQFuI0j3NsgG+xmPtmu/a
KMQ8Bw3yOc8yo6/2uNiZTeGl1NclFEo+KycJJwpYWNqCt6Vr0B19ruOzKZissTXw
OkH/RGqWuqMNJYYEg2xG/fNiGyIE42WD6QPtnHsMykvu3w52Rq2TQy1CMUf3KNpV
4lhjPk+PX7EWB8tpUrUdCrpVSdhyOROYXpTA8xjT8bEdvZ9v5Vc=
=6VFd
-END PGP 

Bug#941439: marked as done (Ships obsolete mimelnk directory)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 17:10:02 +
with message-id 
and subject line Bug#941439: fixed in libreoffice 1:6.3.3~rc1-1
has caused the Debian Bug report #941439,
regarding Ships obsolete mimelnk directory
to be marked as done.

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

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


-- 
941439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice-common
Version: 1:6.3.2-1
Severity: minor

Hi,

libreoffice-common ships an unused, obsolete
/usr/share/mimelnk directory.

Those were used in KDE3 days which is long gone.
This directory can be dropped safely from the package.

Regards,
Michael

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

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

Versions of packages libreoffice-common depends on:
ii  libnumbertext-data 1.0.5-3
ii  libreoffice-style-colibre  1:6.3.2-1
ii  libreoffice-style-tango1:6.3.2-1
ii  ure6.3.2-1

Versions of packages libreoffice-common recommends:
ii  apparmor2.13.3-5
ii  fonts-liberation2   2.00.5-2
ii  libexttextcat-data  3.4.5-1
ii  python3-uno 1:6.3.2-1
ii  xdg-utils   1.1.3-1

Versions of packages libreoffice-common suggests:
ii  libreoffice-style-colibre [libreoffice-style] 1:6.3.2-1
ii  libreoffice-style-elementary [libreoffice-style]  1:6.3.2-1
ii  libreoffice-style-tango [libreoffice-style]   1:6.3.2-1

Versions of packages python3-uno depends on:
ii  libc6 2.29-2
ii  libgcc1   1:9.2.1-8
ii  libpython3.7  3.7.4-4
ii  libreoffice-core  1:6.3.2-1
ii  libstdc++69.2.1-8
ii  python3   3.7.3-1
ii  python3.7 3.7.4-4
ii  uno-libs3 6.3.2-1
ii  ure   6.3.2-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 1:6.3.3~rc1-1

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

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

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

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated libreoffice 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, 13 Oct 2019 16:39:08 +
Source: libreoffice
Architecture: source
Version: 1:6.3.3~rc1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Rene Engelhard 
Closes: 941439 941655
Changes:
 libreoffice (1:6.3.3~rc1-1) unstable; urgency=medium
 .
   * New upstream release candidate
 - fixes images getting black in some circumstances
   (closes: #941655)
 .
   * debian/scripts/gid2pkgdirs.sh:
 - stop installing /usr/share/mimelnk (closes: #941439)
Checksums-Sha1:
 537c98bb54b867cf82a766c5dfbccf2568baaf6c 27068 libreoffice_6.3.3~rc1-1.dsc
 4a19c774750dfd656a7c39912fc8198ac2e10151 12588924 
libreoffice_6.3.3~rc1.orig-helpcontent2.tar.xz
 5271fc8078018594d1f5c99369936c94a959798a 146759852 
libreoffice_6.3.3~rc1.orig-translations.tar.xz
 d238a37bb44a805395cff40fc10746d211b44850 224937884 
libreoffice_6.3.3~rc1.orig.tar.xz
 989b18d25e089aa5c8cd5a1ab85762cfa71b1591 833 
libreoffice_6.3.3~rc1.orig.tar.xz.asc
 f98d72cafabf80bb2c28e1c2f7e243b4ef223508 10691628 
libreoffice_6.3.3~rc1-1.debian.tar.xz
 512e321ec38f3b60bc7bd7a18c63442c0cd44cfd 40179 
libreoffice_6.3.3~rc1-1_source.buildinfo
Checksums-Sha256:
 6ff3836875fbc51c22b805b6cdc7ac389c4ef3579d5532062685b7563c17fb6c 27068 
libreoffice_6.3.3~rc1-1.dsc
 e39e114337aab52733711f4eabc602059c965d823320361ad016c29cfc3f808d 12588924 
libreoffice_6.3.3~rc1.orig-helpcontent2.tar.xz
 24a1cbfb41ec4664ab81ae70b2b16edfabf66b2abe58997645a8afc74c5788bb 146759852 
libreoffice_6.3.3~rc1.orig-translations.tar.xz
 4e39753489049eb2c6a698862b7d465aa98cf53b1d6c32571368d97bc144277a 

Bug#941655: marked as done (libreoffice-impress: Exported html pages have black backgrounds)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 17:10:02 +
with message-id 
and subject line Bug#941655: fixed in libreoffice 1:6.3.3~rc1-1
has caused the Debian Bug report #941655,
regarding libreoffice-impress: Exported html pages have black backgrounds
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.)


-- 
941655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice-impress
Version: 1:6.3.2-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Exporting html pages of a libreoffice-impress document

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

For the purpose of this bugreport I created a small .odp file of two slides
Then alt-File, Export, and then pressed Export in the Export window.

   * What was the outcome of this action?

The html versions were saved, but all slides shown in the html files have a
black background 

   * What outcome did you expect instead?

The same background as in the presentation slides. In previous versions 
(version 1:6.1.5-3+deb10u4, the current stable version and before) exporting
html pages of the presentation went flawlessly. 

For your information: the demo slides and exported html pages are available in
https://www.icce.rug.nl/tmp/impress.tgz

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

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

Versions of packages libreoffice-impress depends on:
ii  libc62.29-2
ii  libepoxy01.5.3-0.1
ii  libetonyek-0.1-1 0.1.9-1
ii  libgcc1  1:9.2.1-8
ii  libmwaw-0.3-30.3.15-2
ii  libodfgen-0.1-1  0.1.7-1
ii  libreoffice-core 1:6.3.2-1
ii  libreoffice-draw 1:6.3.2-1
ii  librevenge-0.0-0 0.0.4-6+b1
ii  libstaroffice-0.0-0  0.0.6-1
ii  libstdc++6   9.2.1-8
ii  uno-libs36.3.2-1
ii  ure  6.3.2-1

libreoffice-impress recommends no packages.

Versions of packages libreoffice-impress suggests:
pn  bluez  

Versions of packages libreoffice-core depends on:
ii  fontconfig  2.13.1-2+b1
ii  fonts-opensymbol2:102.11+LibO6.3.2-1
ii  libboost-locale1.67.0   1.67.0-13
ii  libc6   2.29-2
ii  libcairo2   1.16.0-4
ii  libclucene-contribs1v5  2.3.3.4+dfsg-1+b1
ii  libclucene-core1v5  2.3.3.4+dfsg-1+b1
ii  libcmis-0.5-5v5 0.5.2-1
ii  libcups22.3.0-3
ii  libcurl3-gnutls 7.66.0-1
ii  libdbus-1-3 1.12.16-1
ii  libdconf1   0.34.0-1
ii  libeot0 0.01-5+b1
ii  libepoxy0   1.5.3-0.1
ii  libexpat1   2.2.7-2
ii  libexttextcat-2.0-0 3.4.5-1
ii  libfontconfig1  2.13.1-2+b1
ii  libfreetype62.9.1-4
ii  libgcc1 1:9.2.1-8
ii  libglib2.0-02.60.6-2
ii  libgpgmepp6 1.13.1-1
ii  libgraphite2-3  1.3.13-8
ii  libgstreamer-plugins-base1.0-0  1.14.4-2
ii  libgstreamer1.0-0   1.16.1-1
ii  libharfbuzz-icu02.6.1-3
ii  libharfbuzz0b   2.6.1-3
ii  libhunspell-1.7-0   1.7.0-2+b1
ii  libhyphen0  2.8.8-7
ii  libice6 2:1.0.9-2
ii  libicu6363.2-2
ii  libjpeg62-turbo 1:1.5.2-2+b1
ii  liblcms2-2  2.9-3+b1
ii  libldap-2.4-2   2.4.48+dfsg-1
ii  libmythes-1.2-0 2:1.2.4-3+b1
ii  libneon27-gnutls0.30.2-3
ii  libnspr42:4.21-2
ii  libnss3 2:3.45-1
ii  libnumbertext-1.0-0 1.0.5-3
ii  liborcus-0.14-0 0.14.1-6
ii  libpng16-16 1.6.37-1
ii  libpoppler820.71.0-5+b1
ii  librdf0 1.0.17-1.1+b1
ii  libreoffice-common  1:6.3.2-1
ii  librevenge-0.0-00.0.4-6+b1
ii  libsm6  2:1.2.3-1
ii  libstdc++6  9.2.1-8
ii  libx11-62:1.6.8-1
ii  libxext6

Bug#936104: marked as done (a2jmidid: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 17:04:21 +
with message-id 
and subject line Bug#936104: fixed in a2jmidid 9-2
has caused the Debian Bug report #936104,
regarding a2jmidid: 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.)


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

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: a2jmidid
Source-Version: 9-2

We believe that the bug you reported is fixed in the latest version of
a2jmidid, 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.
Sebastian Ramacher  (supplier of updated a2jmidid 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, 13 Oct 2019 18:36:50 +0200
Source: a2jmidid
Architecture: source
Version: 9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Closes: 936104 941167
Changes:
 a2jmidid (9-2) unstable; urgency=medium
 .
   * Team upload
   * Brown paper bag release
 - Include proper changelog
 .
 a2jmidid (9-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Felipe Sateler ]
   * Change maintainer address to debian-multime...@lists.debian.org
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat
 .
   [ Sebastian Ramacher ]
   * New upstream release (Closes: #941167)
 - Port to Python 3 (Closes: #936104)
   * debian/control:
 - Bump debhelper compat to 12
 - Bump Standards-Version
   * debian/:
 - Point to new upstream
 - Use meson build system and Python 3
Checksums-Sha1:
 

Bug#941167: marked as done (a2jmidid: new upstream and new upstream version)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 17:04:21 +
with message-id 
and subject line Bug#941167: fixed in a2jmidid 9-2
has caused the Debian Bug report #941167,
regarding a2jmidid: new upstream and new upstream 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.)


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

Package: a2jmidid

Dear debian maintainers,

there is a new upstream source point for a2jmidid: 
https://github.com/linuxaudio/a2jmidid/

and this upstream just released a new version ("9") 2 days ago.

Hope that helps.
Olivier

--
Site web : https://librazik.tuxfamily.org/
Donation : https://liberapay.com/LibraZiK/
Diaspora : 
https://framasphere.org/people/8c184af0c9450134f6682a053625

Mastodon : https://mastodon.xyz/@LibraZiK
--- End Message ---
--- Begin Message ---
Source: a2jmidid
Source-Version: 9-2

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

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

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated a2jmidid 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, 13 Oct 2019 18:36:50 +0200
Source: a2jmidid
Architecture: source
Version: 9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Closes: 936104 941167
Changes:
 a2jmidid (9-2) unstable; urgency=medium
 .
   * Team upload
   * Brown paper bag release
 - Include proper changelog
 .
 a2jmidid (9-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Felipe Sateler ]
   * Change maintainer address to debian-multime...@lists.debian.org
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat
 .
   [ Sebastian Ramacher ]
   * New upstream release (Closes: #941167)
 - Port to Python 3 (Closes: #936104)
   * debian/control:
 - Bump debhelper compat to 12
 - Bump Standards-Version
   * debian/:
 - Point to new upstream
 - Use meson build system and Python 3
Checksums-Sha1:
 1f0c9be3adb28a7b4078c7ca8644760433dc17a8 2006 a2jmidid_9-2.dsc
 3760a4fc84647059cb3a915572b93c1fc18fa7c7 4316 a2jmidid_9-2.debian.tar.xz
Checksums-Sha256:
 fcb84e16832ae5193589a6e229455fef3069fc43ab9463f93530c4e4b85a7eb1 2006 
a2jmidid_9-2.dsc
 3215be4a77d3efe59d27ecb4da39dcf46abb323a14ee936b6290f69db5aea6de 4316 
a2jmidid_9-2.debian.tar.xz
Files:
 23b5b8681acee6c77f65493eab9ed6c5 2006 sound optional a2jmidid_9-2.dsc
 6532c7de04252b0f9d38cf804e55e827 4316 sound optional a2jmidid_9-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl2jU2IACgkQafL8UW6n
GZMinRAAnDeNuHcyyyhrGQbEwDkL6Zny/W2nXFTiUGdlzjq3yTP47HE88jOOFJ8J
UKAo3Q+La+BpRWKpc8TiuuGkI53PLG1LIvgTyFl8VwRWh0qs9+jlm3zqhZkYBqPa
VKvxIuIqrXg3QsP80G0mBSQ9i+BTryhqd2ElNkjcwG01MNyIyfQ2P60lLARLof2c
y9ll0sniGegxmveMMhpEb2mfgficVlitHWDuMPToJNB8i/SKdGY4atq0jNrDMH3K
b8ytt3TSlbOkVYoIR0EIB33/JTa6MljH4fTV3rgsfGPSioj3ZTSGV9+yNYTIC7bV
Rwu4JmYz3N1ZslG7BZkJ2udX0EqvejEf9Rt53Tmp2lY+253Mrw9gxa+HWdDp6pDt
E2BbAT6HL3vMPnIVmx3dMK0+t/foXzUsnExaO81apzRmcFvSYGw3j2+fudUNsGLq
tJSnFwL058zEEd3Wpg1X/1nt4m6kP8MWTu8KwWBCG0Wj9U00BAPDLAC1lcej+mng
NmocLMnP1XsqoleMumWxWAV+rJMYyTgenpvmoae1vwsgRHhyOFhu0GVvvtZlmx2m
wMhZxpyF9lUnT49AqH9mKUOv3+NnbSWHr4ZWNWLpw4oE3DRNSibWaZi3AtX89R7/
zMJ6ikw41lsXDbQBnekVkJadoqRVtvhZcEJFP8EqInilTsUTrDU=
=eiFO
-END PGP SIGNATURE End Message ---

Bug#938504: marked as done (smbmap: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 16:35:44 +
with message-id 
and subject line Bug#938504: fixed in smbmap 1.1.0+git20191013-1
has caused the Debian Bug report #938504,
regarding smbmap: 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.)


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

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: smbmap
Source-Version: 1.1.0+git20191013-1

We believe that the bug you reported is fixed in the latest version of
smbmap, 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.
Samuel Henrique  (supplier of updated smbmap 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, 13 Oct 2019 17:13:58 +0100
Source: smbmap
Architecture: source
Version: 1.1.0+git20191013-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Samuel Henrique 
Closes: 938504
Changes:
 smbmap (1.1.0+git20191013-1) unstable; urgency=medium
 .
   * New upstream version 1.1.0+git20191013
   * Bump Debhelper to 12
   * Bump Standards-Version to 4.4.1
   * Build with python3 (closes: #938504)
   * Add salsa-ci.yml
   * d/patches: Update patch and remove one applied upstream
Checksums-Sha1:
 1870f4ed3460dd39931bf057f58ccf8214cd4f3b 2029 smbmap_1.1.0+git20191013-1.dsc
 485843011bc0a84c348dcfa43bf9849b262ae545 27553 
smbmap_1.1.0+git20191013.orig.tar.gz
 1a297b6a6d4dd36354562e59827182584e825c7f 4152 
smbmap_1.1.0+git20191013-1.debian.tar.xz
 a6c19c8d4a90a5bd1404155cda3a2115c1ee4982 6231 
smbmap_1.1.0+git20191013-1_amd64.buildinfo
Checksums-Sha256:
 

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

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:49:45 +
with message-id 
and subject line Bug#938245: fixed in python-urlobject 2.4.3-1
has caused the Debian Bug report #938245,
regarding python-urlobject: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-urlobject

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: python-urlobject
Source-Version: 2.4.3-1

We believe that the bug you reported is fixed in the latest version of
python-urlobject, 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.
Andrej Shadura  (supplier of updated python-urlobject 
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, 13 Oct 2019 17:34:49 +0200
Source: python-urlobject
Architecture: source
Version: 2.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andrej Shadura 
Closes: 938245
Changes:
 python-urlobject (2.4.3-1) unstable; urgency=medium
 .
   [ Sandro Tosi ]
   * Non-maintainer upload.
   * Drop python2 support; Closes: #938245.
 .
   [ Andrej Shadura ]
   * New upstream version.
   * Refresh the patch.
   * Maintain in the team.
   * Run wrap-and-sort -bask.
   * d/copyright: Use https protocol in Format field.
   * Use debhelper-compat instead of debian/compat.
   * Use secure URI in Homepage field.
   * Bump debhelper from old 9 to 12.
Checksums-Sha1:
 bf4f258031517507f1e9fb37cf3a0a225960c01f 1866 python-urlobject_2.4.3-1.dsc
 f7d41684ec6a232c111d72135e080a8f42e67354 23204 
python-urlobject_2.4.3.orig.tar.xz
 f557bafa193b61b0701b51594d1437ad93f9a440 3112 

Bug#595986: marked as done (loggerhead: Instructions to get branch give bad location.)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:32:52 +
with message-id <20191013153252.ga...@jelmer.uk>
and subject line Done
has caused the Debian Bug report #595986,
regarding loggerhead: Instructions to get branch give bad location.
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.)


-- 
595986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: loggerhead
Version: 1.17+bzr424-1
Severity: normal

When viewing a branch in loggerhead on bzr.debian.org, the instructions to get
the branch give a bad location. For instance, viewing
 you
see:

To get this branch, use:
bzr branch /scm/loggerhead/pkg-bazaar/loggerhead/unstable

That will obviously not work.



-- System Information:
Debian Release: squeeze/sid
  APT prefers maverick-updates
  APT policy: (500, 'maverick-updates'), (500, 'maverick-security'), (500, 
'maverick-backports'), (500, 'maverick')
Architecture: i386 (i686)

Kernel: Linux 2.6.35-19-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


--- End Message ---
--- Begin Message ---
This was fixed in upstream Loggerhead.--- End Message ---

Bug#942039: marked as done (loggerhead: not co-installable with loggerhead-breezy)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:32:28 +
with message-id <20191013153228.ga...@jelmer.uk>
and subject line Resolved
has caused the Debian Bug report #942039,
regarding loggerhead: not co-installable with loggerhead-breezy
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.)


-- 
942039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: loggerhead
Version: 1.19~bzr494-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Selecting previously unselected package loggerhead-breezy.
  Preparing to unpack .../loggerhead-breezy_1.20~bzr551+dfsg-1_all.deb ...
  Unpacking loggerhead-breezy (1.20~bzr551+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/loggerhead-breezy_1.20~bzr551+dfsg-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/loggerhead-serve', which is also in package 
loggerhead 1.19~bzr494-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/loggerhead-breezy_1.20~bzr551+dfsg-1_all.deb

loggerhead is the newer package, uploaded a few days ago, while the last
loggerhead-breezy upload was nearly a year ago.

cheers,

Andreas


loggerhead=1.19~bzr494-1_loggerhead-breezy=1.20~bzr551+dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
loggerhead-breezy has been removed from Debian, resolving this bug.--- End Message ---

Bug#942186: marked as done (RM: sandboxgamemaker -- RoQA; inactive upstream; NIT; broken; orphaned; RC-buggy; low popcon)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:16:34 +
with message-id 
and subject line Bug#942186: Removed package(s) from unstable
has caused the Debian Bug report #942186,
regarding RM: sandboxgamemaker -- RoQA; inactive upstream; NIT; broken; 
orphaned; RC-buggy; low popcon
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.)


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

* Last upstream release was 2013
* Not in testing
* Doesn't work at all without manually downloading a tarball from
  upstream, pulling out various files, and installing by hand (#764896)
* Orphaned
* Very low popcon (Inst: 58 Vote: 5)
* No rdeps according to: `dak rm -Rn sandboxgamemaker`

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

sandboxgamemaker | 2.8.2+dfsg-1 | source
sandboxgamemaker | 2.8.2+dfsg-1+b3 | amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el, s390x

--- Reason ---
RoQA; inactive upstream; NIT; broken; orphaned; RC-buggy; low popcon
--

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

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

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#879121: marked as done (unixodbc-gui-qt FTCBFS: uses AC_CHECK_FILE for /usr/include)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:18:08 +
with message-id 
and subject line Bug#942264: Removed package(s) from unstable
has caused the Debian Bug report #879121,
regarding unixodbc-gui-qt FTCBFS: uses AC_CHECK_FILE for /usr/include
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.)


-- 
879121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unixodbc-gui-qt
Version: 2.3.0-4
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

unixodbc-gui-qt fails to cross build from source, because it searches
for headers with AC_CHECK_FILES. The latter macro is supposed to search
the host system, but we need the headers on the build system. Just
trying "test -e ..." is good here. After doing so, unixodbc-gui-qt cross
builds successfully. Please consider applying the attached patch.

Helmut
diff -u unixodbc-gui-qt-2.3.0/qt.m4 unixodbc-gui-qt-2.3.0/qt.m4
--- unixodbc-gui-qt-2.3.0/qt.m4
+++ unixodbc-gui-qt-2.3.0/qt.m4
@@ -111,8 +111,8 @@
   # qt_dir_lib="$qt_dir"/lib
   # qt_dir_bin="$qt_dir"/bin
 
-  AC_CHECK_FILE([$qt_dir_include/QtGui/QWizard], [have_qtwizard=yes], [have_qtwizard=no])
-  AC_CHECK_FILE([$qt_dir_include/QtGui/QMdiArea], [have_qtmdiarea=yes], [have_qtmdiarea=no])
+  if test -e "$qt_dir_include/QtGui/QWizard"; then have_qtwizard=yes; else have_qtwizard=no; fi
+  if test -e "$qt_dir_include/QtGui/QMdiArea"; then have_qtmdiarea=yes; else have_qtmdiarea=no; fi
 
   MOC="$qt_dir_bin"/moc
   UIC="$qt_dir_bin"/uic
--- End Message ---
--- Begin Message ---
Version: 2.3.0-4+rm

Dear submitter,

as the package unixodbc-gui-qt 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/942264

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

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

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

Bug#920554: marked as done (unixodbc-bin: Binaries listed in description don't match binaries provided)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:18:08 +
with message-id 
and subject line Bug#942264: Removed package(s) from unstable
has caused the Debian Bug report #920554,
regarding unixodbc-bin: Binaries listed in description don't match binaries 
provided
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.)


-- 
920554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unixodbc-bin
Version: 2.3.0-4+b1
Severity: important

Dear Maintainer,

First of all, THANK YOU, for maintaining this package!

Now, the problem:

The package description lists three binaries that are to be included with the
package, ODBCConfig, DataManager, and odbctest.  However, none of these
binaries are actually included.

Also, the package does provide binaries ODBCCreateDataSourceQ4, and
ODBCManageDataSourcesQ4.  However, these are not mentioned in the package
description.

Please provide the ODBCConfig, DataManager and odbctest binaries in this
package; and, please update the description to indicate that the package also
provides ODBCCreateDataSourceQ4 and ODBCManageDataSourcesQ4.

Thanks again!
Gene



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

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

Versions of packages unixodbc-bin depends on:
ii  libc6  2.24-11+deb9u3
ii  libgcc11:6.3.0-18+deb9u1
ii  libodbc1   2.3.4-1
ii  libodbcinstq4-12.3.0-4+b1
ii  libqt4-network 4:4.8.7+dfsg-11
ii  libqtassistantclient4  4.6.3-7+b1
ii  libqtcore4 4:4.8.7+dfsg-11
ii  libqtgui4  4:4.8.7+dfsg-11
ii  libstdc++6 6.3.0-18+deb9u1
ii  odbcinst1debian2   2.3.4-1

unixodbc-bin recommends no packages.

unixodbc-bin suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.3.0-4+rm

Dear submitter,

as the package unixodbc-gui-qt 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/942264

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

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

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

Bug#875172: marked as done ([rlplot] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:17:21 +
with message-id 
and subject line Bug#942263: Removed package(s) from unstable
has caused the Debian Bug report #875172,
regarding [rlplot] Future Qt4 removal from Buster
to be marked as done.

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

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


-- 
875172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rlplot
Version: 1.5-3
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


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

[OpenSSL 1.1 support] 

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

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

= Porting =

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

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

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

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

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

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 1.5-4+rm

Dear submitter,

as the package rlplot 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/942263

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

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

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

Bug#941180: marked as done (RM: usbprog -- RoQA; dead upstream; unmaintained; low popcon; RC-buggy)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:15:31 +
with message-id 
and subject line Bug#941180: Removed package(s) from unstable
has caused the Debian Bug report #941180,
regarding RM: usbprog -- RoQA; dead upstream; unmaintained; low popcon; RC-buggy
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.)


-- 
941180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: usbprog
Version: 0.2.0-2.2
Severity: normal

I think it's time to remove the usbprog package:

* upstream website gives 500 error
* last upstream release packaged was ~8.5 years ago
* has low popcon - inst:231 vote:180
* has no reverse dependencies (according to dak rm)
* last maintainer upload was over 7.5 years ago
* 4 open bugs with no maintainer response to any of them
* I had to NMU for the last wxWidgets transition 5 years ago, and
  it's now a blocker for the current wxwidgets3.0-gtk3 transition.

If there are no objections within two weeks, I'll turn this into an RM
bug.

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

libusbprog-dev | 0.2.0-2.2+b3 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
libusbprog0v5 | 0.2.0-2.2+b3 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
   usbprog |  0.2.0-2.2 | source
   usbprog | 0.2.0-2.2+b3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
usbprog-gui | 0.2.0-2.2+b3 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x

--- Reason ---
RoQA; dead upstream; unmaintained; low popcon; RC-buggy
--

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

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

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#941179: marked as done (O: sandboxgamemaker -- 3D game maker and 3D game design program)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:16:42 +
with message-id 
and subject line Bug#942186: Removed package(s) from unstable
has caused the Debian Bug report #941179,
regarding O: sandboxgamemaker -- 3D game maker and 3D game design program
to be marked as done.

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

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


-- 
941179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: normal
--- End Message ---
--- Begin Message ---
Version: 2.8.2+dfsg-1+rm

Dear submitter,

as the package sandboxgamemaker 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/942186

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

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

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

Bug#933408: marked as done (usbprog: Please rebuild against wxWidgets GTK 3 package)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:15:38 +
with message-id 
and subject line Bug#941180: Removed package(s) from unstable
has caused the Debian Bug report #933408,
regarding usbprog: Please rebuild against wxWidgets GTK 3 package
to be marked as done.

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

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


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

Hi,

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

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

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

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

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

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

Dear submitter,

as the package usbprog 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/941180

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

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

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

Bug#933445: marked as done (sandboxgamemaker: Please rebuild against wxWidgets GTK 3 package)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:16:42 +
with message-id 
and subject line Bug#942186: Removed package(s) from unstable
has caused the Debian Bug report #933445,
regarding sandboxgamemaker: Please rebuild against wxWidgets GTK 3 package
to be marked as done.

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

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


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

Hi,

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

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

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

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

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

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

Dear submitter,

as the package sandboxgamemaker 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/942186

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

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

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

Bug#941153: marked as done (RM: manpages-es -- RoQA; totally outdated manpages, unmaintained)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:15:01 +
with message-id 
and subject line Bug#941153: Removed package(s) from unstable
has caused the Debian Bug report #941153,
regarding RM: manpages-es -- RoQA; totally outdated manpages, unmaintained
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.)


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

Please see #934248: The manpages are completely outdated, the
last release of manpages-es was in 2005 and the last upload in 2011.

Cheers,
Moritz



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

manpages-es |1.55-10 | source, all

--- Reason ---
RoQA; totally outdated manpages, unmaintained
--

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

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

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

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:15:09 +
with message-id 
and subject line Bug#941153: Removed package(s) from unstable
has caused the Debian Bug report #934248,
regarding 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.)


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

The last release of manpages-es was in 2005 and the last upload in 2011.

As already pointed out in #860177, the translations are consequentially
very outdated, I did some random sampling and e.g

- For a basic command like mkdir(1) in Spanish only documents three of
the current seven options in the English manpages

- proc(5) documents the state of Linux 2.4.17

>From my PoV such extremely outdated documentation probably does more harm
than good?

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 1.55-10+rm

Dear submitter,

as the package manpages-es 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/941153

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

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

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

Bug#933411: marked as done (fwknop-gui: Please rebuild against wxWidgets GTK 3 package)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:16:13 +
with message-id 
and subject line Bug#941240: Removed package(s) from unstable
has caused the Debian Bug report #933411,
regarding fwknop-gui: Please rebuild against wxWidgets GTK 3 package
to be marked as done.

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

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


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

Hi,

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

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

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

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

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

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

Dear submitter,

as the package fwknop-gui 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/941240

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

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

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

Bug#941240: marked as done (RM: fwknop-gui -- RoQA; dead upstream; unmaintained; low popcon; RC-buggy)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:16:08 +
with message-id 
and subject line Bug#941240: Removed package(s) from unstable
has caused the Debian Bug report #941240,
regarding RM: fwknop-gui -- RoQA; dead upstream; unmaintained; low popcon; 
RC-buggy
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.)


-- 
941240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fwknop-gui
Version: 1.3+dfsg-1
Severity: normal

I think it's time to remove the fwknop-gui package:

* upstream is inactive (last upstream commit over 3 years ago)
* package has only ever been uploaded once, over 3 years ago
* extremely low popcon - inst:11 vote:1
* blocker for the current wxwidgets3.0-gtk3 transition
* maintainer seems unresponsive

If there are no objections within two weeks, I'll turn this into an RM
bug.

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

fwknop-gui | 1.3+dfsg-1 | source
fwknop-gui | 1.3+dfsg-1+b2 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x

--- Reason ---
RoQA; dead upstream; unmaintained; low popcon; RC-buggy
--

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

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

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#942264: marked as done (RM: unixodbc-gui-qt -- RoQA; Depends on Qt4)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:18:02 +
with message-id 
and subject line Bug#942264: Removed package(s) from unstable
has caused the Debian Bug report #942264,
regarding RM: unixodbc-gui-qt -- RoQA; Depends on Qt4
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.)


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

Please remove unixodbc-gui-qt, it depends on Qt4 which is being
removed and hasn't seen an upload since 5.5 years.

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

libodbcinstq4-1 | 2.3.0-4+b1 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
unixodbc-bin | 2.3.0-4+b1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
unixodbc-gui-qt |2.3.0-4 | source

--- Reason ---
RoQA; Depends on Qt4
--

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

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

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#875219: marked as done ([unixodbc-gui-qt] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:18:08 +
with message-id 
and subject line Bug#942264: Removed package(s) from unstable
has caused the Debian Bug report #875219,
regarding [unixodbc-gui-qt] Future Qt4 removal from Buster
to be marked as done.

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

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


-- 
875219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unixodbc-gui-qt
Version: 2.3.0-4
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


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

[OpenSSL 1.1 support] 

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

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

= Porting =

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

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

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

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

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

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 2.3.0-4+rm

Dear submitter,

as the package unixodbc-gui-qt 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/942264

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

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

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

Bug#942247: marked as done (RM: geary [s390x] -- ROM; ANAIS)

[Debian Bug Tracking System]

Your message dated Sun, 13 Oct 2019 15:16:54 +
with message-id 
and subject line Bug#942247: Removed package(s) from unstable
has caused the Debian Bug report #942247,
regarding RM: geary [s390x] -- ROM; ANAIS
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.)


-- 
942247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
X-Debbugs-CC: ge...@packages.debian.org, m...@vee.net

geary no longer builds on s390x because it has critical failures in
its build tests. Those failures indicate that geary probably does not
work on s390x.

We are unaware of anyone working on supporting geary on s390x and
would prefer not to ignore test failures in order to publish broken
binary packages.

Therefore, please remove geary on s390x from Debian Unstable.

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 geary |   0.12.4-4 | s390x

--- Reason ---
ROM; ANAIS
--

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.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

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

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

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

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