Bug#947497: caffe: depends on python3-leveldb whose removal has been requested

[Simon McVittie]

Source: caffe
Version: 1.0.0+git20180821.99bd997-4
Severity: serious
Justification: uninstallable in testing
Control: block 945894 by -1

In #945894, the maintainer of src:python-leveldb writes:
> Please remove src:python-leveldb from unstable. Its upstream
> discontinued for a long time and there's already an other, maintained
> alternative in the archive.

Processed: block 935573 with 936580 938522 927134 938877 936216 945653 936724 927100 927132 935677 927136

[Debian Bug Tracking System]

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

> block 935573 with 936580 938522 927134 938877 936216 945653 936724 927100 
> 927132 935677 927136
Bug #935573 [ftp.debian.org] RM: python-ipaddr -- ROM; Obsolete libs (python2)
935573 was not blocked by any bugs.
935573 was not blocking any bugs.
Added blocking bug(s) of 935573: 936724, 935677, 927134, 938522, 938877, 
945653, 927136, 927100, 936216, 936580, and 927132
> thanks
Stopping processing here.

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

Bug#947338: cherrytree: should this package be removed?

[Simon McVittie]

On Tue, 24 Dec 2019 at 20:12:23 -0500, Sandro Tosi wrote:
> i believe there are several issues with cherrytree:
> 
> - python2-only application
> - depends on pygtk, deprecated
> - depends on gtksourceview, deprecated
> - upstream is rewriting it in C++, so there's no hope for a py3k port
> 
> i think it's time to remove it (and eventuall re-introduce it in Debian once 
> the
> C++ port is completed); if i dont hear back within a week with a good reason 
> to
> keep this package in Debian, i'll file for it's removal.

cherrytree is also the last thing keeping orphaned GNOME 2 package
src:pygtksourceview in Debian, so please ask for that package to be
removed (RoQA) at the same time.

Thanks,
smcv

Processed: Tagging

[Debian Bug Tracking System]

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

> tag 947490 ftbfs
Bug #947490 [src:kadu] FTBFS: CMake can't find X11
Added tag(s) ftbfs.
> tag 947492 ftbfs
Bug #947492 [src:kdiagram] FTBFS: on mips64el and mipsel: tests failing
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#936522: marked as done (flask: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 27 Dec 2019 17:05:06 +
with message-id 
and subject line Bug#936522: fixed in flask 1.1.1-2
has caused the Debian Bug report #936522,
regarding 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.)


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

We believe that the bug you reported is fixed in the latest version of
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.
Ondřej Nový  (supplier of updated 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: SHA512

Format: 1.8
Date: Fri, 27 Dec 2019 17:44:34 +0100
Source: flask
Architecture: source
Version: 1.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Piotr Ożarowski 
Changed-By: Ondřej Nový 
Closes: 936522
Changes:
 flask (1.1.1-2) unstable; urgency=medium
 .
   * Enable sphinx-issues extension.
   * Drop Python 2 support (Closes: #936522).
   * Fix tests in Python 3.8.
Checksums-Sha1:
 ca9a165ecd5862e35456a227ba6cba6151bca965 2320 flask_1.1.1-2.dsc
 bde6f02f364d05a6a32e0791377940e4df4af59d 6184 flask_1.1.1-2.debian.tar.xz
 c6253ed4bffab21dc396da5ec345f3a0f8457902 7872 flask_1.1.1-2_amd64.buildinfo
Checksums-Sha256:
 bb3f132b6989397019be858c185b56ea3c18797f89a8b2cf465b53b6ac998030 2320 
flask_1.1.1-2.dsc
 303d4f5e95d077dab81f840932138920def18ea53097938f8eba00f272a3c48e 6184 
flask_1.1.1-2.debian.tar.xz
 c6a7cb6aebd4fde6ae50193b984a74fe405b919e38bd85c7b6d36613ccb95bde 7872 
flask_1.1.1-2_amd64.buildinfo
Files:
 d27e2b074465f482e3913d300888c3b2 2320 python optional flask_1.1.1-2.dsc
 

Bug#875137: marked as done ([qjoypad] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Fri, 27 Dec 2019 17:00:22 +
with message-id 
and subject line Bug#875137: fixed in qjoypad 4.3.1-1
has caused the Debian Bug report #875137,
regarding [qjoypad] 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.)


-- 
875137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qjoypad
Version: 4.1.0-2.1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


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

[OpenSSL 1.1 support] 

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

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

= Porting =

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

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

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

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

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

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: qjoypad
Source-Version: 4.3.1-1

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

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

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated qjoypad 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, 22 Dec 2019 17:20:04 +0100
Source: qjoypad
Binary: qjoypad qjoypad-dbgsym
Architecture: source amd64
Version: 4.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Adam Borowski 
Changed-By: Adam Borowski 
Description:
 qjoypad- map gamepad/joystick events to mouse/keyboard event
Closes: 863132 870122 875137 947180
Changes:
 qjoypad (4.3.1-1) unstable; urgency=medium
 .
   * Reintroduce the package.  Closes: #947180.
   * New maintainer, thanks Jordan for your prior work!
   * Switch to a new upstream.  Closes: #870122.
   * QT 5.  Closes: #875137.
   * Set arch to linux-any.  Closes: #863132.
   * Drop the Debian menu, use upstream .desktop.
   * Generally modernize the package.
Checksums-Sha1:
 7233ebc9c5c3feb99a3ad29115a3c5e7ba7f6c5b 1924 qjoypad_4.3.1-1.dsc
 a96fdff90cdbc4eebecd97f51d41417e419f72eb 89122 qjoypad_4.3.1.orig.tar.gz
 57f1ab3b47d6092b31b56dcdd6c7f4e35073c9b0 2848 qjoypad_4.3.1-1.debian.tar.xz
 8cf2c7979fdb97fdc6960312bb25ec059de4dfe9 1812816 
qjoypad-dbgsym_4.3.1-1_amd64.deb
 778a8dd51ac9fc6b796c24603415bc5105ada2ed 11268 qjoypad_4.3.1-1_amd64.buildinfo
 8c10cdecef1de72902c74eecbf45e71b023dc231 84692 qjoypad_4.3.1-1_amd64.deb
Checksums-Sha256:
 daa91247c0cae6dfd36b979d620a37f771b403a856e372c8eaa9195151e1fd06 1924 
qjoypad_4.3.1-1.dsc
 0081974dc75b4a9804499f9340564a1aab7c5630c81503c0e624d5b3b6172b4f 89122 
qjoypad_4.3.1.orig.tar.gz
 

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

[Debian Bug Tracking System]

Your message dated Fri, 27 Dec 2019 17:00:20 +
with message-id 
and subject line Bug#937941: fixed in python-pynvim 0.4.0-1
has caused the Debian Bug report #937941,
regarding python-neovim: 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.)


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

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-pynvim
Source-Version: 0.4.0-1

We believe that the bug you reported is fixed in the latest version of
python-pynvim, 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.
James McCoy  (supplier of updated python-pynvim 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 Dec 2019 22:41:00 -0500
Source: python-pynvim
Binary: python3-pynvim
Architecture: source all
Version: 0.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: James McCoy 
Description:
 python3-pynvim - Python3 library for scripting Neovim processes through its 
msgpac
Closes: 937941
Changes:
 python-pynvim (0.4.0-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat.
   * Bump Standards-Version to 4.4.1.
 .
   [ Andrey Rahmatullin ]
   * Drop Python 2 support (Closes: #937941).
 .
   [ James McCoy ]
   * New upstream version 0.4.0
 - Renamed to python-pynvim
 - Add python3-pytest-runner to Build-Depends
   * Remove 0001-Add-missing-conftest.py-in-sdist.patch, applied upstream
   * Rename python3-neovim to python3-pynvim
   * Add myself to Uploaders
Checksums-Sha1:
 f3a821904b0b4233fc0ef5c1613c26919b3330e9 2404 

Processed: your mail

[Debian Bug Tracking System]

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

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

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

Bug#947328: (no subject)

[Thomas Ward]

https://bugs.debian.org/943705 has been reported as the core cause.

The builds are being give-backed now, as we are fairly sure that the 
issue reported in the FTBFS bug here was due to debhelper issues which 
were fixed on the 7th, five days after the autobuilds were triggered.


I'm going to mark this as tags: pending, as this is now waiting on the 
rebuilds on buildd.

Bug#937293: [Piuparts-devel] Bug#919170: Bug#919170: Please update dependency to python3-debianbts

[Holger Levsen]

hi,

Traceback (most recent call last):
  File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 
433, in 
main()
  File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 
423, in main
m = Master(sys.stdin, sys.stdout)
  File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 
154, in __init__
self._writeline("hello")
  File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 
111, in _writeline
self._output.flush()
BrokenPipeError: [Errno 32] Broken pipe
Exception ignored in: <_io.TextIOWrapper name='' mode='w' 
encoding='UTF-8'>
BrokenPipeError: [Errno 32] Broken pipe

not sure if this is something which should be fixed / excepted better?


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C



signature.asc
Description: PGP signature

Bug#947492: FTBFS: on mips64el and mipsel: tests failing

[Lisandro Damián Nicanor Pérez Meyer]

Source: kdiagram
Version: 2.6.1-1+b1
Severity: serious
Justification: FTBFS on mipsel and mips64el

Hi! Your package's tests are failing on mipsel andmips64el.

You can see the build logs at 
https://buildd.debian.org/status/package.php?p=kdiagram

Kinds regards, Lisandro.

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

Kernel: Linux 5.3.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#937293: [Piuparts-devel] Bug#919170: Bug#919170: Please update dependency to python3-debianbts

[Holger Levsen]

On Thu, Dec 26, 2019 at 11:26:31PM +0100, Nis Martensen wrote:
> On 26.12.2019 17.11, Holger Levsen wrote:
> > many thanks, merged and deployed, now this is left:
> 
> >   File 
> > "/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/__init__.py",
> >  line 58, in readline
> > empty = not self._refill()
> >   File 
> > "/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/__init__.py",
> >  line 49, in _refill
> > chunk = chunk.decode()
> > UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc3 in position 14159: 
> > unexpected end of data
> 
> This did not happen in my test setup, but I have a theory of what is
> causing this. Could you check if
> https://salsa.debian.org/debian/piuparts/merge_requests/18
> fixes it?

indeed, this fixes it, but things still dont work, but on master I only
see this:

Traceback (most recent call last):
  File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 
433, in 
main()
  File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 
425, in main
while m.do_transaction():
  File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 
268, in do_transaction
self._commands[command](command, args)
  File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 
323, in _reserve
self._init_db()
  File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 
202, in _init_db
self._load_package_database(self._section)
  File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 
219, in _load_package_database
self._load_package_database(dep)
  File "/srv/piuparts.debian.org/share/piuparts/piuparts-master-backend", line 
232, in _load_package_database
config.get_arch()))
  File 
"/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/packagesdb.py", 
line 455, in load_alternate_versions_from_packages_urls
pf2.load_packages_urls(urls)
  File 
"/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/packagesdb.py", 
line 181, in load_packages_urls
(url, stream) = piupartslib.open_packages_url(url)
  File 
"/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/__init__.py", 
line 96, in open_packages_url
socket = urllib.request.urlopen(url + ext)
  File "/usr/lib/python3.7/urllib/request.py", line 222, in urlopen
return opener.open(url, data, timeout)
  File "/usr/lib/python3.7/urllib/request.py", line 525, in open
response = self._open(req, data)
  File "/usr/lib/python3.7/urllib/request.py", line 543, in _open
'_open', req)
  File "/usr/lib/python3.7/urllib/request.py", line 503, in _call_chain
result = func(*args)
  File "/usr/lib/python3.7/urllib/request.py", line 1345, in http_open
return self.do_open(http.client.HTTPConnection, req)
  File "/usr/lib/python3.7/urllib/request.py", line 1320, in do_open
r = h.getresponse()
  File "/usr/lib/python3.7/http/client.py", line 1321, in getresponse
response.begin()
  File "/usr/lib/python3.7/http/client.py", line 296, in begin
version, status, reason = self._read_status()
  File "/usr/lib/python3.7/http/client.py", line 257, in _read_status
line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
  File "/usr/lib/python3.7/socket.py", line 589, in readinto
return self._sock.recv_into(b)
ConnectionResetError: [Errno 104] Connection reset by peer

and nothing really on the slave :/

so I dug depper on master and found that master was using mirror.bm.debian.org, 
which 
was shutdown recently and voila, it seems 0d44938b323e in develop branch was 
the last
bit to get piuparts working with python3 (hopefully, still needs more testing), 
and also the reason the (python2) stale branch broke recently.

So, piuparts.debian.org is running python3 code only now! At least for the 
piuparts service ;)

Thank you very much, Nis, for your help until here!

I do hope to do a final piuparts upload in 2019. We'll see if I manage during 
36c3 ;)

-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C



signature.asc
Description: PGP signature

Bug#947490: FTBFS: CMake can't find X11

[Lisandro Damián Nicanor Pérez Meyer]

Source: kadu
Version: 4.1-1.1
Severity: serious
Justification: FTBFS in various architectures

Hi! While binNMUing your package it FTBFS with the following error:

-- Looking for archive_write_set_compression_xz in 
/usr/lib/x86_64-linux-gnu/libarchive.so - found
CMake Error at 
/usr/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
  Could NOT find X11 (missing: X11)
Call Stack (most recent call first):
  /usr/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:378 
(_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake-3.15/Modules/FindX11.cmake:366 
(find_package_handle_standard_args)
  kadu-core/CMakeLists.txt:114 (find_package)

You can see the full build logs in 
https://buildd.debian.org/status/package.php?p=kadu

Thanks for your work, Lisandro.

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

Kernel: Linux 5.3.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Processed: Tag

[Debian Bug Tracking System]

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

> tag 947487 ftbfs
Bug #947487 {Done: Pino Toscano } [src:grantlee5] FTBFS: 
various C++ errors
Bug #939362 {Done: Pino Toscano } [src:grantlee5] grantlee5: 
FTBFS with Qt 5.12.4 in experimental
Added tag(s) ftbfs.
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: forcibly merging 939362 947487

[Debian Bug Tracking System]

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

> forcemerge 939362 947487
Bug #939362 {Done: Pino Toscano } [src:grantlee5] grantlee5: 
FTBFS with Qt 5.12.4 in experimental
Bug #947487 [src:grantlee5] FTBFS: various C++ errors
Marked Bug as done
Marked as fixed in versions grantlee5/5.2.0-1.
Added tag(s) sid and bullseye.
Merged 939362 947487
> thanks
Stopping processing here.

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

Bug#947487: FTBFS: various C++ errors

[Lisandro Damián Nicanor Pérez Meyer]

Source: grantlee5
Version: 5.1.0-2.1
Severity: serious
Justification: FTBFS in various architectures

Hi! While rebuilding your package due to a binNMU it failed to build from 
source:

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

The forst error I see is:

from 
/<>/obj-x86_64-linux-gnu/templates/tests/pluginpointertest/main_app_autogen/mocs_compilation.cpp:2:
/usr/include/c++/9/bits/c++0x_warning.h:32:2: error: #error This file requires 
compiler and library support for the ISO C++ 2011 standard. This support must 
be enabled with the -std=c++11 or -std=gnu++11 compiler options.
   32 | #error This file requires compiler and library support \
  |  ^

Thanks for your work, Lisandro.

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

Kernel: Linux 5.3.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Processed: FTBFS due to this?

[Debian Bug Tracking System]

Processing control commands:

> tag -1 ftbfs
Bug #936483 [src:enki-aseba] enki-aseba: Python2 removal in sid/bullseye
Added tag(s) ftbfs.

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

Bug#936483: FTBFS due to this?

[Lisandro Damián Nicanor Pérez Meyer]

Control: tag -1 ftbfs

Apparently this is also causing a FTBFS:

https://buildd.debian.org/status/package.php?p=enki-aseba

Bug#947486: golang-github-containers-image: FTBFS with test failures

[Andreas Beckmann]

Source: golang-github-containers-image
Version: 5.0.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

golang-github-containers-image/experimental FTBFS in an up-to-date
minimal sid+experimental pbuilder environment:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/golang-github-containers-image-5.0.0'
mkdir -v -p debian/tmp
mkdir: created directory 'debian/tmp'
XDG_RUNTIME_DIR=/build/golang-github-containers-image-5.0.0/debian/tmp \
dh_auto_test
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 3 
github.com/containers/image github.com/containers/image/copy 
github.com/containers/image/directory 
github.com/containers/image/directory/explicitfilepath 
github.com/containers/image/docker github.com/containers/image/docker/archive 
github.com/containers/image/docker/daemon 
github.com/containers/image/docker/policyconfiguration 
github.com/containers/image/docker/reference 
github.com/containers/image/docker/tarfile github.com/containers/image/image 
github.com/containers/image/internal/pkg/keyctl 
github.com/containers/image/internal/testing/explicitfilepath-tmpdir 
github.com/containers/image/internal/testing/mocks 
github.com/containers/image/internal/tmpdir 
github.com/containers/image/manifest github.com/containers/image/oci 
github.com/containers/image/oci/archive 
github.com/containers/image/oci/internal github.com/containers/image/oci/layout 
github.com/containers/image/pkg/blobinfocache 
github.com/containers/image/pkg/blobinfocache/boltdb 
github.com/containers/image/pkg/blobinfocache/internal/prioritize 
github.com/containers/image/pkg/blobinfocache/internal/test 
github.com/containers/image/pkg/blobinfocache/memory 
github.com/containers/image/pkg/blobinfocache/none 
github.com/containers/image/pkg/compression 
github.com/containers/image/pkg/compression/internal 
github.com/containers/image/pkg/compression/types 
github.com/containers/image/pkg/docker/config 
github.com/containers/image/pkg/strslice 
github.com/containers/image/pkg/sysregistriesv2 
github.com/containers/image/pkg/tlsclientconfig 
github.com/containers/image/signature github.com/containers/image/storage 
github.com/containers/image/tarball github.com/containers/image/transports 
github.com/containers/image/transports/alltransports 
github.com/containers/image/types github.com/containers/image/version
?   github.com/containers/image [no test files]
[...]
=== RUN   TestSessionKeyring
--- FAIL: TestSessionKeyring (0.00s)
keyring_test.go:19: key has been revoked
=== RUN   TestUserKeyring
--- PASS: TestUserKeyring (0.00s)
=== RUN   TestLink
--- FAIL: TestLink (0.00s)
keyring_test.go:85: key has been revoked
=== RUN   TestUnlink
--- FAIL: TestUnlink (0.00s)
keyring_test.go:129: key has been revoked
=== RUN   TestReadKeyring
--- PASS: TestReadKeyring (0.00s)
=== RUN   TestDescribe
--- PASS: TestDescribe (0.00s)
FAIL
FAILgithub.com/containers/image/internal/pkg/keyctl 0.003s
?   github.com/containers/image/internal/testing/explicitfilepath-tmpdir
[no test files]
?   github.com/containers/image/internal/testing/mocks  [no test files]
?   github.com/containers/image/internal/tmpdir [no test files]
[...]
ok  github.com/containers/image/transports/alltransports0.036s
?   github.com/containers/image/types   [no test files]
?   github.com/containers/image/version [no test files]
FAIL
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 3 
github.com/containers/image github.com/containers/image/copy 
github.com/containers/image/directory 
github.com/containers/image/directory/explicitfilepath 
github.com/containers/image/docker github.com/containers/image/docker/archive 
github.com/containers/image/docker/daemon 
github.com/containers/image/docker/policyconfiguration 
github.com/containers/image/docker/reference 
github.com/containers/image/docker/tarfile github.com/containers/image/image 
github.com/containers/image/internal/pkg/keyctl 
github.com/containers/image/internal/testing/explicitfilepath-tmpdir 
github.com/containers/image/internal/testing/mocks 
github.com/containers/image/internal/tmpdir 
github.com/containers/image/manifest github.com/containers/image/oci 
github.com/containers/image/oci/archive 
github.com/containers/image/oci/internal github.com/containers/image/oci/layout 
github.com/containers/image/pkg/blobinfocache 
github.com/containers/image/pkg/blobinfocache/boltdb 
github.com/containers/image/pkg/blobinfocache/internal/prioritize 
github.com/containers/image/pkg/blobinfocache/internal/test 
github.com/containers/image/pkg/blobinfocache/memory 
github.com/containers/image/pkg/blobinfocache/none 
github.com/containers/image/pkg/compression 
github.com/containers/image/pkg/compression/internal 
github.com/containers/image/pkg/compression/types 
github.com/containers/image/pkg/docker/config 
github.com/containers/image/pkg/strslice 

Processed: txt2tags: missing Depends: python3-pkg-resources

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:thunderbolt-tools
Bug #947482 [txt2tags] txt2tags: missing Depends: python3-pkg-resources
Added indication that 947482 affects src:thunderbolt-tools

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

Bug#947482: txt2tags: missing Depends: python3-pkg-resources

[Helmut Grohne]

Package: txt2tags
Version: 3.4-1
Severity: serious
Tags: ftbfs
Control: affects -1 + src:thunderbolt-tools

Running txt2tags fails:
$ txt2tags
Traceback (most recent call last):
  File "/usr/bin/txt2tags", line 6, in 
from pkg_resources import load_entry_point
ModuleNotFoundError: No module named 'pkg_resources'
$

This is due to a missing dependency on python3-pkg-resources. It happens
to make packages that use txt2tags during build (such as
thunderbolt-tools) ftbfs.

Helmut

Bug#947479: antimony: fails to start due to broken library dependency

[Damyan Ivanov]

Package: antimony
Version: 0.9.3-1+b1
Severity: grave
Justification: renders package unusable

Attempting to start antimony fails with:

$ antimony
antimony: error while loading shared libraries: libboost_python36.so.1.67.0: 
cannot open shared object file: No such file or directory


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

Versions of packages antimony depends on:
ii  libboost-python1.67.0  1.67.0-16
ii  libc6  2.29-6
ii  libgcc11:9.2.1-21
ii  libpng16-161.6.37-1
ii  libpython3.7   3.7.6-1
ii  libqt5concurrent5  5.12.5+dfsg-4
ii  libqt5core5a   5.12.5+dfsg-4
ii  libqt5gui5 5.12.5+dfsg-4
ii  libqt5network5 5.12.5+dfsg-4
ii  libqt5opengl5  5.12.5+dfsg-4
ii  libqt5widgets5 5.12.5+dfsg-4
ii  libstdc++6 9.2.1-21
ii  python33.7.5-3
ii  zlib1g 1:1.2.11.dfsg-1+b1

antimony recommends no packages.

antimony suggests no packages.

-- no debconf information

Bug#943943: marked as done (getfem++ ftbfs on s390x where it built before)

[Debian Bug Tracking System]

Your message dated Fri, 27 Dec 2019 14:43:50 +
with message-id 
and subject line Bug#943943: fixed in getfem++ 5.3+dfsg1-3
has caused the Debian Bug report #943943,
regarding getfem++ ftbfs on s390x where it built before
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.)


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

Package: src:getfem++
Version: 5.3+dfsg1-1
Severity: serious
Tags: sid bullseye

getfem++ ftbfs on s390x where it built before, test failures.

https://buildd.debian.org/status/package.php?p=getfem%2B%2B
shows that all other 64bit big endian targets also fail.
--- End Message ---
--- Begin Message ---
Source: getfem++
Source-Version: 5.3+dfsg1-3

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

Debian distribution maintenance software
pp.
Konstantinos Poulios  (supplier of updated 
getfem++ package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 27 Dec 2019 13:51:29 +
Source: getfem++
Architecture: source
Version: 5.3+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Konstantinos Poulios 
Closes: 943943
Changes:
 getfem++ (5.3+dfsg1-3) unstable; urgency=medium
 .
   * Remove redundant dependencies on muparser and several boost packages.
   * Fix blas and lapack interface. Closes: #943943.
Checksums-Sha1:
 dbba1744b8335fbe5e0f116cca4decd68b01d29e 2375 getfem++_5.3+dfsg1-3.dsc
 9a3ce19fbf7e8c90e79ce6088decbbfe70c8ae47 20408 
getfem++_5.3+dfsg1-3.debian.tar.xz
Checksums-Sha256:
 e3d697d6e0a8d0a51dc4eecddf62b9686cd1be9387dd8e00b84825f02ee14972 2375 
getfem++_5.3+dfsg1-3.dsc
 39ce15be8dd86b729c753c45a5d4b5de3f51f5e7c2cf13af7d8932ae522e6cc9 20408 
getfem++_5.3+dfsg1-3.debian.tar.xz
Files:
 0eae971c3add605697ba75165355cd27 2375 libs optional getfem++_5.3+dfsg1-3.dsc
 9038de0b377a1231e4b311522d4f1b3e 20408 libs optional 
getfem++_5.3+dfsg1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl4GDPgACgkQr8/sjmac
4cLNYw//RMsh82Rj7ULVYs1fy9XtlW/Yx16uh4fR+RXU/Yaw7JFy4gf3BKdiHtYN
KE4CrS0yYSDDc6QqEYhAu5stGJiiKYEf3GAqdmM+c+JKj5CNomyBU0hgh4B4iF2y
xED4x16eWzUbuFwK+3m6IZlwB3Iu79BJw8RzjqO1qfvUn6CEqxz/MQBKWVuYYeMk
0YIDhvF+PG5mrkI2frFKx6JJpwEtrvv7UH16xPXqbR8ECORISz30JBuHn7AqeQD9
B2/B5sUpFDjlhznx4OzzKUSu8vOnmBFN6jUFFG8Spq/FvWY2uUPxrFcEIJR8ezll
b9FDOqvBAFs6V0HqsNTkAM0S9rQyRNd2yVSmkz9QX1pq15OadK3JHD5O65PXMl35
pIMj7Cv/WoqMs3YyEfHxdhE9hk6RCcZJlFwrfFaOxdDC9HLPyNmVjMTwK0338a17
g06YSo2Sr1GdF+ErYKxSY3c/RV3KLMIusXKUffVGxThfrd3wkx2fjXqM+v3EayVD
vkA3rwSQfXZFRR3TinIv4gX98q7R/yNLCCAqR2SgrdveTBkt5U+tUS+vL/tlnu7B
QkFtWAy6QXsJMXn97bc7JinPki9G4pMFKCvIq/yJSbREIaUFNEoa5PH/yxab5Xmp
tXsy2u4ePfyndKBg89KYD4c9DJOAF8Aex01qC2nF+5ViNdhzEg0=
=no+u
-END PGP SIGNATURE End Message ---

Bug#947476: slic3r-prusa: missing Build-Depends

[Andreas Beckmann]

Source: slic3r-prusa
Version: 1.41.3+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

slic3r-prusa/experimental FTBFS, probably due to some dependency changes
in other packages:

In file included from /usr/include/wx-3.0/wx/unix/glx11.h:13,
 from /usr/include/wx-3.0/wx/gtk/glcanvas.h:14,
 from /usr/include/wx-3.0/wx/glcanvas.h:195,
 from 
/build/slic3r-prusa-1.41.3+dfsg/xs/src/slic3r/GUI/GLCanvas3D.cpp:17:
/usr/include/GL/glx.h:30:10: fatal error: X11/Xlib.h: No such file or directory
   30 | #include 


Andreas


slic3r-prusa_1.41.3+dfsg-1.log.gz
Description: application/gzip

Bug#945920: Random Chromium crashes

[Jaap Joris Vens]

On Fri, Dec 27, 2019 at 01:29:13PM +0100, Stefan Bühler wrote:

Hi,

yes, you are right, my patch only fixes the task manager crash.

I now took a look at all backtraces, and all apart the first one
(probably older version?) seem to be the same "other" instance:


--- 8< ---

I am not quite following the intricacies of this crash anymore, but might
this be something that we will need to report upstream?

Greetings,
JJ

Processed: iFix tagging

[Debian Bug Tracking System]

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

> tag 947474 ftbfs
Bug #947474 [src:cloudcompare] FTBFS: various C++ related errors
Added tag(s) ftbfs.
> tag 947475 ftbfs
Bug #947475 [src:datovka] FTBFS: make[1]: *** No rule to make target 
'lowered_tree_view.h', needed by 'ui_datovka.h'.  Stop.
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#942735: (no subject)

[Håvard Flaget Aasen]

In the subject you are speaking of directories, but you do want the 
directories appended with an m?


Is it the files /usr/lib/python3/dist-packages/persistent/*38*.so you 
want changed to *38m*.so?

Bug#947475: FTBFS: make[1]: *** No rule to make target 'lowered_tree_view.h', needed by 'ui_datovka.h'. Stop.

[Lisandro Damián Nicanor Pérez Meyer]

Source: datovka
Version: 4.9.3-2
Severity: serious
Justification: FTBFS on all archs

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

make[1]: Entering directory '/<>'
make[1]: *** No rule to make target 'lowered_tree_view.h', needed by 
'ui_datovka.h'.  Stop.
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:20: build-arch] Error 255

You can see the build logs in 
https://buildd.debian.org/status/package.php?p=datovka

Thanks for your work, Lisandro.

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

Kernel: Linux 5.3.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Processed: Fix tags

[Debian Bug Tracking System]

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

> tag 947327 ftbfs
Bug #947327 [src:poppler] FTBFS: /usr/bin/env: ‘python’: No such file or 
directory
Added tag(s) ftbfs.
> tag 947328 ftbfs
Bug #947328 [src:xca] FTBFS: dh_installman: mv 
debian/xca/usr/share/man/man1/xca.1.dh-new: No such file or directory
Added tag(s) ftbfs.
> tag 947329 ftbfs
Bug #947329 [src:bppphyview] FTBFS: 
debian/bppphyview/usr/share/man/man1/phyview.1: No such file or directory
Added tag(s) ftbfs.
> tag 947330 ftbfs
Bug #947330 [src:cb2bib] FTBFS: *** No rule to make target 'libc2b.a', needed 
by '../bin/cb2bib'.  Stop.
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#947474: FTBFS: various C++ related errors

[Lisandro Damián Nicanor Pérez Meyer]

Source: cloudcompare
Version: 2.10.3-3
Severity: serious
Justification: FTBFS on amd64, arm64 and others

Hi! during a binNMU rebuild of your package it FTBFS with various C++ related 
errors.

You can see the build logs in 
https://buildd.debian.org/status/package.php?p=cloudcompare

Thanks, Lisandro.

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

Kernel: Linux 5.3.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Processed (with 1 error): Fixes

[Debian Bug Tracking System]

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

> retitle 947326 FTBFS: unable to load addon python3: Can't locate
Bug #947326 [src:antimony] dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC
Changed Bug title to 'FTBFS: unable to load addon python3: Can't locate' from 
'dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC'.
> Debian/Debhelper/Sequence/python3.pm in @INC
Unknown command or malformed arguments to command.
> tag 947326 ftbfs
Bug #947326 [src:antimony] FTBFS: unable to load addon python3: Can't locate
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#936566: marked as done (fs-uae: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 27 Dec 2019 13:49:26 +
with message-id 
and subject line Bug#936566: fixed in fs-uae 3.0.2+dfsg-1
has caused the Debian Bug report #936566,
regarding fs-uae: 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.)


-- 
936566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fs-uae
Version: 2.8.4+dfsg-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:fs-uae

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: fs-uae
Source-Version: 3.0.2+dfsg-1

We believe that the bug you reported is fixed in the latest version of
fs-uae, 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.
John Paul Adrian Glaubitz  (supplier of updated 
fs-uae package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 27 Dec 2019 13:47:35 +0100
Source: fs-uae
Architecture: source
Version: 3.0.2+dfsg-1
Distribution: sid
Urgency: medium
Maintainer: John Paul Adrian Glaubitz 
Changed-By: John Paul Adrian Glaubitz 
Closes: 886933 936566 944373
Changes:
 fs-uae (3.0.2+dfsg-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #886933, #944373)
   * Drop fs-uae-netplay-server package which is python2-only. (Closes: #936566)
 + Add note about removal in debian/README.source.
 + Delete debian/fs-uae-netplay-server.* files.
 + Drop python and python-setuptools from Build-Depends in debian/control.
 + Remove package description from debian/README.Debian.
 + Remove package build invocation from debian/rules.
 + Remove file pattern matching from debian/copyright.
 + Remove section from debian/control.
   * Drop debian/patches directory to start with a fresh patch-queue.
   * Re-add patch to define unknown CPUs as CPU_unknown:

Bug#947468: php-twig: missing Build-Depends: php-symfony-string

[Andreas Beckmann]

Source: php-twig
Version: 3.0.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

php-twig/experimental FTBFS due to failing to load some includes in the
tests:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/php-twig-3.0.0'
phpunit
PHP Warning:  require_once(Symfony/Component/String/autoload.php): failed to 
open stream: No such file or directory in 
/build/php-twig-3.0.0/extra/string-extra/src/autoload.php on line 2
PHP Fatal error:  require_once(): Failed opening required 
'Symfony/Component/String/autoload.php' (include_path='.:/usr/share/php') in 
/build/php-twig-3.0.0/extra/string-extra/src/autoload.php on line 2
make[1]: *** [debian/rules:78: override_dh_auto_test] Error 255
make[1]: Leaving directory '/build/php-twig-3.0.0'
make: *** [debian/rules:7: build] Error 2


Andreas


php-twig_3.0.0-2.log.gz
Description: application/gzip

Bug#947467: python-incremental, reccomends and build-depends on package that depends on obsolete package.

[peter green]

Package: python-incremental
Version: 16.10.1-3
Severity: serious
Tags: bullseye, sid, patch

python-incremental recommends, the incremental source package build-depends on 
and the incremental autopkgtests depend on python-click. Python-click in turn 
depends on the python-colorama binary package, which is no longer built by the 
python-colorama source package. It is still present in testing as a cruft 
package, but is completely gone from unstable.

The long-term solution to this would be to drop python2 support, however I do 
not think that is practical at this time. In particular python-twisted depends 
on python-incremental and the python-twisted python 2 removal bug still has a 
whole bunch of blockers.

From grepping the code it looks like python-incremental only uses python-click 
for the update script, not for the run-time stuff. So I have prepared a patch 
that eliminates them. This also involved disabling the testsuite/autopkgtest 
for python 2 (but keeping it enabled for python 3).

A debdiff is attached, if I get no objections I will probablly NMU this later.


diff -Nru incremental-16.10.1/debian/changelog 
incremental-16.10.1/debian/changelog
--- incremental-16.10.1/debian/changelog2016-11-03 20:27:56.0 
+
+++ incremental-16.10.1/debian/changelog2019-12-27 12:48:06.0 
+
@@ -1,3 +1,14 @@
+incremental (16.10.1-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove build-depends and reccomends on python-click (Closes: ??)
+  * Disable python 2 autopkgtests and remove associated test dependencies.
+  * Disable testsuite for python 2 (keep it enabled for python 3)
+  * Add note to package description about incremental.update functionality
+and python-click.
+
+ -- Peter Michael Green   Fri, 27 Dec 2019 12:48:06 +
+
 incremental (16.10.1-3) unstable; urgency=medium
 
   * Recommend python Twisted and Click, in order to use incremental.update
diff -Nru incremental-16.10.1/debian/control incremental-16.10.1/debian/control
--- incremental-16.10.1/debian/control  2016-11-03 20:27:56.0 +
+++ incremental-16.10.1/debian/control  2019-12-27 12:48:06.0 +
@@ -7,7 +7,6 @@
python-all (>= 2.6.6-3),
python-setuptools (>= 0.6b3),
python-twisted-core,
-   python-click,
python3-all,
python3-setuptools (>= 0.6b3),
python3-twisted,
@@ -20,12 +19,16 @@
 Package: python-incremental
 Architecture: all
 Depends: ${misc:Depends}, ${python:Depends}
-Recommends: python-click, python-twisted-core
+Recommends: python-twisted-core
 Provides: ${python:Provides}
 Description: Library for versioning Python projects.
  Incremental is a small library that versions your Python projects.
  .
  This package provides the Python 2.x module.
+ .
+ The incremental.update functionality requires the click module which is
+ no longer available for python 2 in Debian. If you require this functionality
+ we suggest using python 3.
 
 Package: python3-incremental
 Architecture: all
diff -Nru incremental-16.10.1/debian/rules incremental-16.10.1/debian/rules
--- incremental-16.10.1/debian/rules2016-11-03 17:40:25.0 +
+++ incremental-16.10.1/debian/rules2019-12-27 12:48:06.0 +
@@ -2,6 +2,10 @@
 
 export PYBUILD_NAME=incremental
 
+# Don't test python 2 because python-click is not available anymore.
+export PYBUILD_DISABLE_python2=test
+export PYBUILD_DISABLE_python2-dbg=test
+
 # XXX Unit tests seem to leave cruft around, for some reason
 export PYBUILD_AFTER_TEST=rm -rf {build_dir}/incremental.tests.*
 
diff -Nru incremental-16.10.1/debian/tests/control 
incremental-16.10.1/debian/tests/control
--- incremental-16.10.1/debian/tests/control2016-11-03 20:27:56.0 
+
+++ incremental-16.10.1/debian/tests/control2019-12-27 12:47:49.0 
+
@@ -1,7 +1,5 @@
-Tests: unit-tests-2 unit-tests-3
+Tests: unit-tests-3
 Restrictions: needs-root
 Depends: @,
- python-twisted-core,
- python-click,
  python3-twisted,
  python3-click

Bug#945692: marked as done (prometheus-postfix-exporter: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 27 Dec 2019 13:04:19 +
with message-id 
and subject line Bug#945692: fixed in prometheus-postfix-exporter 0.2.0-2
has caused the Debian Bug report #945692,
regarding prometheus-postfix-exporter: 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.)


-- 
945692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945692
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: prometheus-postfix-exporter
Version: 0.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 (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

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

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

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

  This is the least preferred option.

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

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

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

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

Debian distribution maintenance software
pp.
Martina Ferrari  (supplier of updated 
prometheus-postfix-exporter package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 27 Dec 2019 12:39:36 +
Source: prometheus-postfix-exporter
Architecture: source
Version: 0.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Martina Ferrari 
Closes: 945692
Changes:
 prometheus-postfix-exporter (0.2.0-2) unstable; urgency=medium
 .
   * Update chuser helper to python3, and fix bug in it. Closes: #945692.
   * Add myself to Uploaders.
   * Automated cme fixes.
Checksums-Sha1:
 2d468b84ea7bf5b0294f694b81445131c800419f 2450 
prometheus-postfix-exporter_0.2.0-2.dsc
 2d0f7ab181284cfa480b35be7179fe4cb02c6b81 6532 
prometheus-postfix-exporter_0.2.0-2.debian.tar.xz
 a1acff60d93bdb5e91bc4d8924a5938f2395e252 9327 
prometheus-postfix-exporter_0.2.0-2_amd64.buildinfo
Checksums-Sha256:
 ac66f55e58c5bb7523d9d6872915b34af18af59ee0e035713b806e0e3a778ea1 2450 
prometheus-postfix-exporter_0.2.0-2.dsc
 3e0e4985a67e242196effc31d36a23a6bbfc19b46ab47a00e2e0faac25497717 6532 
prometheus-postfix-exporter_0.2.0-2.debian.tar.xz
 

Bug#945920: Random Chromium crashes

[Stefan Bühler]

Hi,

yes, you are right, my patch only fixes the task manager crash.

I now took a look at all backtraces, and all apart the first one 
(probably older version?) seem to be the same "other" instance:

---
#0  0x5a77cee7 in 
memory_instrumentation::MemoryInstrumentation::RequestGlobalDump(std::vector, std::allocator >, 
std::allocator, 
std::allocator > > > const&, base::OnceCallback >)>) ()
#1  0x58f8ddb0 in 
ProcessMemoryMetricsEmitter::FetchAndEmitProcessMemoryMetrics() ()
#2  0x58f85e82 in (anonymous namespace)::RecordMemoryMetrics() ()
#3  0x593b5165 in base::TaskAnnotator::RunTask(char const*, 
base::PendingTask*) ()
---

The underlying issue is the same: it crashes when dereferencing `this` 
(as it is NULL).

It gets started in `RecordMemoryMetricsAfterDelay`:

https://github.com/chromium/chromium/blob/07653652c58cc019af7f833bd63eb0c2eceaab5e/chrome/browser/metrics/chrome_browser_main_extra_parts_metrics.cc#L72-L90

The "time to live" (until the first actual call) is determined in 
`GetDelayForNextMemoryLog`:

https://github.com/chromium/chromium/blob/07653652c58cc019af7f833bd63eb0c2eceaab5e/services/resource_coordinator/public/cpp/memory_instrumentation/browser_metrics.cc#L52-L61

And `FetchAndEmitProcessMemoryMetrics` doesn't check the `GetInstance()` 
result either:

https://github.com/chromium/chromium/blob/07653652c58cc019af7f833bd63eb0c2eceaab5e/chrome/browser/metrics/process_memory_metrics_emitter.cc#L636-L642

I'm not quite sure about the consequences, for now I tried skipping 
`RecordMemoryMetrics` completely - we'll see how that goes..

So as additional patch I replaced 0x55 (`push %rbp`) at offset 
0x03a31e50 (start of `RecordMemoryMetrics`) with 0xc3 (`retq`):

$ xxd -s 0x3a31e50 -l 16 /usr/lib/chromium/chromium
03a31e50: 55bf 4000  4889 e541 5453 e8cf dd49  u...@...h..ats...I
$ printf '03a31e50: c3\n' | xxd -r -  /usr/lib/chromium/chromium
$ sha1sum /usr/lib/chromium/chromium* 
fbfb255a77f38b629c19eabddff577a1b26f4395  /usr/lib/chromium/chromium
5056c781602f4bbd41f06b3bd1940b6edbd7dc8c  /usr/lib/chromium/chromium-pre-patch

cheers,
Stefan

Bug#939109: marked as done (pyhoca-gui: Python2 removal in sid/bullseye -- drop python-distutils-extra build dependency)

[Debian Bug Tracking System]

Your message dated Fri, 27 Dec 2019 11:51:25 +
with message-id 
and subject line Bug#939109: fixed in pyhoca-gui 0.6.1.0-1
has caused the Debian Bug report #939109,
regarding pyhoca-gui: Python2 removal in sid/bullseye -- drop 
python-distutils-extra build dependency
to be marked as done.

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

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


-- 
939109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyhoca-gui
Version: 0.5.0.8-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 build-depends on python-distutils-extra. Please convert the
package to Python 3, using python3-distutils-extra.

Thanks,

Martin
--- End Message ---
--- Begin Message ---
Source: pyhoca-gui
Source-Version: 0.6.1.0-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 27 Dec 2019 12:31:16 +0100
Source: pyhoca-gui
Architecture: source
Version: 0.6.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Remote Maintainers 
Changed-By: Mike Gabriel 
Closes: 937457 939109
Changes:
 pyhoca-gui (0.6.1.0-1) unstable; urgency=medium
 .
   * New upstream release.
 - Python3 port. Several known issues. Please report your findings.
   * debian/control:
 + Port B-Ds and Ds to Python3. (Closes: #937457, #939109).
   * debian/rules:
 + Switch to Python3 pybuild.
Checksums-Sha1:
 dd21ff8b83ef1538f9705827259d1252b8d0b9e1 2365 pyhoca-gui_0.6.1.0-1.dsc
 beccdda504d7d449f164949fdf52ffbd53d762da 2098973 pyhoca-gui_0.6.1.0.orig.tar.gz
 5660d1c6e3571da499c531c9dcaaecd2a50cbb87 488 pyhoca-gui_0.6.1.0.orig.tar.gz.asc
 f02ba5340e3508bbebe753e077fc82dd5d9a0406 25372 
pyhoca-gui_0.6.1.0-1.debian.tar.xz
 1fa8484a509ddf878d097b50de7bccd63d3a5c4a 9087 
pyhoca-gui_0.6.1.0-1_source.buildinfo
Checksums-Sha256:
 97160c5a31a661b68a5e0848308a96259c23fd4f6e480a321150c5f40be07056 2365 
pyhoca-gui_0.6.1.0-1.dsc
 b00f4c30dc504307b3536cedd403dd4f704516e70f81ac9ad2d501785beeeb1f 2098973 
pyhoca-gui_0.6.1.0.orig.tar.gz
 87984743acff14bcb004e7415cada9ba6e74a3d9a44669ada5407ebb974f2744 488 
pyhoca-gui_0.6.1.0.orig.tar.gz.asc
 4b42d1feb89331702a2259f4ef363daffb508e556a7c7c0184f97622f485ad60 25372 
pyhoca-gui_0.6.1.0-1.debian.tar.xz
 fb8caa9ed9ecaf9364601e42498be23b17a52173b822dd59a8f246ca2fbaa716 9087 
pyhoca-gui_0.6.1.0-1_source.buildinfo
Files:
 51c44fd373f64294bf82dad2b71e88d3 2365 x11 optional pyhoca-gui_0.6.1.0-1.dsc
 3d2c5e70d95324a07a08ebd0f785f338 2098973 x11 optional 
pyhoca-gui_0.6.1.0.orig.tar.gz
 450caf12be2dfdecca44c604173b7b4e 488 x11 optional 
pyhoca-gui_0.6.1.0.orig.tar.gz.asc
 e589c9c6be8dd9a3d63733b9ee12a5fc 25372 x11 optional 
pyhoca-gui_0.6.1.0-1.debian.tar.xz
 adae8683f3853df490bf785c6baddfe5 9087 x11 optional 
pyhoca-gui_0.6.1.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl4F7AkVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxYHgQAJCUQ+7DYEkJuNjrvQw5LFc8YuZ/
YadpSJkgPaURkQ3yUOoi/o2sRO83QCpwDIuqrd3k952jKbt22guVsweWeX3km0so
TJkT/DwMbjsqa8yWBufybTIP2BBmJd3x5sv7S2zCsQW86SMVJs1eQ7PmPfeDdevL
iG+aTcjKAERxG1AIATUnLEZ3DjlRfYOWrupRKZSCuFeHcHi7B8BHIpg6MRAfQ3pL
J/fKZ5lwKeSpWu7giAnnq1Ms1fWlpHNb3kZiIdQoPHrkHk3B54dCSMAVlhn1q/2A
t0r+syW0qRfxdJ0TakMIOZwk8Qs++vHHKpqsWqqoo0BISmO5reO66DnGXV9C77qB
iCZXR5weGX/qHD/vcYmreU0zeykoHg1dI6Vc66i4DLD+wxtdkyISV0VDeo8Lw2h9
AAOvMve6lCCF/M54R8psFCiTw7lyuLaN9csWP+sf9mbPaxe+MPR7Avos05D4v4/M
raN4bXWS+7JsHTIH/EQ5uWUI3q/nLo0A2ekAzKGRFqR/97yNJBOD7aDR1ZGhS/K5
6Y4reGOlklblmpHiFLzS4k367XzFJdVg/flz+efRQ2L/EOKrTTPnTVJmOUkAPOX8
CUDVnic9rPH0C4796hRO6u3HhCJ4OpoEnNdqCs6uPqsK8qgPftKLptltoseMtYBy
SPWYk560LNjGkvz4
=8Yxx
-END PGP SIGNATURE End Message ---

Bug#937457: marked as done (pyhoca-gui: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 27 Dec 2019 11:51:25 +
with message-id 
and subject line Bug#937457: fixed in pyhoca-gui 0.6.1.0-1
has caused the Debian Bug report #937457,
regarding pyhoca-gui: 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.)


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

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: pyhoca-gui
Source-Version: 0.6.1.0-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 27 Dec 2019 12:31:16 +0100
Source: pyhoca-gui
Architecture: source
Version: 0.6.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Remote Maintainers 
Changed-By: Mike Gabriel 
Closes: 937457 939109
Changes:
 pyhoca-gui (0.6.1.0-1) unstable; urgency=medium
 .
   * New upstream release.
 - Python3 port. Several known issues. Please report your findings.
   * debian/control:
 + Port B-Ds and Ds to Python3. (Closes: #937457, #939109).
   * debian/rules:
 + Switch to Python3 pybuild.
Checksums-Sha1:
 dd21ff8b83ef1538f9705827259d1252b8d0b9e1 2365 pyhoca-gui_0.6.1.0-1.dsc
 beccdda504d7d449f164949fdf52ffbd53d762da 2098973 pyhoca-gui_0.6.1.0.orig.tar.gz
 5660d1c6e3571da499c531c9dcaaecd2a50cbb87 488 pyhoca-gui_0.6.1.0.orig.tar.gz.asc
 f02ba5340e3508bbebe753e077fc82dd5d9a0406 25372 
pyhoca-gui_0.6.1.0-1.debian.tar.xz
 1fa8484a509ddf878d097b50de7bccd63d3a5c4a 9087 
pyhoca-gui_0.6.1.0-1_source.buildinfo
Checksums-Sha256:
 

Processed: Re: Bug#947319: missing directory

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #947319 [lightdm] lightdm: fails during startup (no invite)
Severity set to 'important' from 'grave'

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

Bug#947319: missing directory

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

control: severity -1 important

On Tue, 2019-12-24 at 16:16 +0100, Jérôme Bouat wrote:
> It seems a directory is missing :
> ---
> Could not enumerate user data directory /var/lib/lightdm/data: Error opening
> directory '/var/lib/lightdm/data': No such file or directory
> ---
> 
> I attached the last lines of my /var/log/syslog

Hi Jérơme,

that directory should be created created by lightdm (see 
https://sources.debian.org/src/lightdm/1.26.0-4/src/shared-data-manager.c/#L75
) so there's something fishy on your installation which doesn't happen
anywhere else.

Could you try to investigate why lightdm can't create it? Can you create it
yourself and see what happens?

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl4F4kgACgkQ3rYcyPpX
RFsanwf+NSyqUTTqSHSq63w+ogyRzgaR98n3reL2K7xvJGIr8dG2N5GA4siRwxW4
3EgSFW15bJ+t+R5T85J5lSWvXQcUzxMF9TI9xN63o3N0x8tEk1griFcfHCuY4I6E
vP5k4v+2bxed8wtLB23f1sA9XrFr/KFy50CVbflbQfNO4zyd2n/toZs/C//gXOSe
/mWfJi0c9fWLsALefJvx1QcZxD9+oHcPnXPRKy1dGqUma+6Ju4eVZOgHcmfL+pyH
0Ta7K5TjVlo5KTQNHWwjK3m2XeEkwIQ/mcR0g9OkPebf9fBmD1uNtOX4tfFHalY2
N7a/qwMJrIYncvYRK8NKkLWCxhwN9A==
=ER63
-END PGP SIGNATURE-

Processed: bio-tradis: autopkgtest regression: Use of uninitialized value $total_uis (and lots of mv: cannot stat '/tmp/aut.....)

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:samtools
Bug #947463 [src:bio-tradis] bio-tradis: autopkgtest regression: Use of 
uninitialized value $total_uis (and lots of mv: cannot stat '/tmp/aut.)
Added indication that 947463 affects src:samtools

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

Bug#947463: bio-tradis: autopkgtest regression: Use of uninitialized value $total_uis (and lots of mv: cannot stat '/tmp/aut.....)

[Paul Gevers]

Source: bio-tradis
Version: 1.4.5+dfsg-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Control: affects -1 src:samtools

Dear maintainers,

With a recent upload of bio-tradis the autopkgtest of bio-tradis fails
in testing when that autopkgtest is run with the binary packages of
bio-tradis from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
bio-tradis from testing1.4.5+dfsg-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

Additionally, looking at the failure mode in unstable, it seems some
package (samtools?) made your (test?) dependencies non-installable in
unstable. You probably need to fix that as well, or raise the issue with
the samtools maintainer.

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

Paul

[1] https://qa.debian.org/excuses.php?package=bio-tradis

https://ci.debian.net/data/autopkgtest/testing/amd64/b/bio-tradis/3765198/log.gz

t/Bio/Tradis/CommandLine/TradisAnalysis.t ..
ok 1 - use Bio::Tradis::CommandLine::TradisAnalysis;
ok 2 - creating object
Use of uninitialized value $total_uis in concatenation (.) or string at
/usr/share/perl5/Bio/Tradis/RunTradis.pm line 468.
Use of uninitialized value $total_uis in numeric gt (>) at
/usr/share/perl5/Bio/Tradis/RunTradis.pm line 470.
mv: cannot stat
'/tmp/autopkgtest-lxc.sfremfei/downtmp/autopkgtest_tmp/smokezkXJAM/tmp_TradisAnalysis_tests_lTLCo/tmp_run_tradis_MG155/test_1.out*':
No such file or directory
Use of uninitialized value $total_uis in concatenation (.) or string at
/usr/share/perl5/Bio/Tradis/RunTradis.pm line 468.
Use of uninitialized value $total_uis in numeric gt (>) at
/usr/share/perl5/Bio/Tradis/RunTradis.pm line 470.
mv: cannot stat
'/tmp/autopkgtest-lxc.sfremfei/downtmp/autopkgtest_tmp/smokezkXJAM/tmp_TradisAnalysis_tests_lTLCo/tmp_run_tradis_xXbiS/test_2.out*':
No such file or directory
ok 3 - testing run
ok 4 - both files have reads with tag
mv: cannot stat
'/tmp/autopkgtest-lxc.sfremfei/downtmp/autopkgtest_tmp/smokezkXJAM/tmp_TradisAnalysis_tests_K2kqu/tmp_run_tradis_AFhbT/test_2.out*':
No such file or directory
ok 5 - testing run with tag only found in one fastq
not ok 6 - one warning raised

#   Failed test 'one warning raised'
#   at t/Bio/Tradis/CommandLine/TradisAnalysis.t line 58.
#  got: '3'
# expected: '1'

[...]

Test Summary Report
---
t/Bio/Tradis/CommandLine/TradisAnalysis.t (Wstat: 256 Tests: 10 Failed: 1)
  Failed test:  6
  Non-zero exit status: 1
t/Bio/Tradis/Map.t   (Wstat: 1536 Tests: 21 Failed: 6)
  Failed tests:  11-15, 18
  Non-zero exit status: 6
t/Bio/Tradis/RunTradisBWA.t  (Wstat: 2304 Tests: 45 Failed: 9)
  Failed tests:  18, 27-28, 30-31, 34-35, 38, 41
  Non-zero exit status: 9
t/Bio/Tradis/RunTradisTaglessBwa.t   (Wstat: 1280 Tests: 22 Failed: 5)
  Failed tests:  5, 14-15, 17-18
  Non-zero exit status: 5
Files=16, Tests=310, 14 wallclock secs ( 1.33 usr  0.03 sys +  6.97 cusr
 1.19 csys =  9.52 CPU)
Result: FAIL



signature.asc
Description: OpenPGP digital signature

Bug#945251: marked as done (otrs2: CVE-2019-18179 CVE-2019-18180)

[Debian Bug Tracking System]

Your message dated Fri, 27 Dec 2019 10:26:45 +
with message-id 
and subject line Bug#945251: fixed in otrs2 6.0.24-1
has caused the Debian Bug report #945251,
regarding otrs2: CVE-2019-18179 CVE-2019-18180
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.)


-- 
945251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: otrs2
Version: 6.0.23-2
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

The following vulnerabilities were published for otrs2

CVE-2019-18179[0] and CVE-2019-18180[1].

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-18179
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18179

https://community.otrs.com/security-advisory-2019-14-security-update-for-otrs-framework/
[1] https://security-tracker.debian.org/tracker/CVE-2019-18180
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18180

https://community.otrs.com/security-advisory-2019-15-security-update-for-otrs-framework/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: otrs2
Source-Version: 6.0.24-1

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

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

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

Debian distribution maintenance software
pp.
Patrick Matthäi  (supplier of updated otrs2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 27 Dec 2019 10:51:52 +0100
Source: otrs2
Architecture: source
Version: 6.0.24-1
Distribution: unstable
Urgency: high
Maintainer: Patrick Matthäi 
Changed-By: Patrick Matthäi 
Closes: 945251
Changes:
 otrs2 (6.0.24-1) unstable; urgency=high
 .
   * New upstream release.
 - Fixes CVE-2019-18179, also known as OSA-2019-14: An attacker who is 
logged
   into OTRS as an agent is able to list tickets assigned to other agents,
   which are in the queue where attacker doesn’t have permissions.
 - Fixes CVE-2019-18180, also known as OSA-2019-15: OTRS can be put into an
   endless loop by providing filenames with overly long extensions. This
   applies to the PostMaster (sending in email) and also upload (attaching
   files to mails, for example).
   Closes: #945251
   * Add dependency on package libcpan-audit-perl.
   * Use the new debhelper-compat notation, and drop the d/compat file.
Checksums-Sha1:
 0895760238be4c5f6b7f4bacbe622ed8a73ed1d5 1817 otrs2_6.0.24-1.dsc
 ad90df5cec9ee59d3e6a32e542b7957f95adcaa9 25547206 otrs2_6.0.24.orig.tar.bz2
 797f243fcc63b66259da0b1965c5e3dfefb9343e 30372 otrs2_6.0.24-1.debian.tar.xz
 635df4d5673d7fd55b50ea0545582ba403fc09e6 5608 otrs2_6.0.24-1_source.buildinfo
Checksums-Sha256:
 6c53b95c209df8b21e9b466ee773f0cc2f84f5c42b5c29ece27cc2cb53776e6d 1817 
otrs2_6.0.24-1.dsc
 c5c1486fa3090b5fe4293f710cb4a19905b1b52f0eecb6de4063be6fac9012e2 25547206 
otrs2_6.0.24.orig.tar.bz2
 6e3ff079b620bd7e23d304165650e0c588da6e9fe05dac0c4cb6629b51ceb21f 30372 
otrs2_6.0.24-1.debian.tar.xz
 23b1bfa868683dcc4b0f1d01507b8fa63ba9fcdaa123c1d65214f3e0d71a2993 5608 
otrs2_6.0.24-1_source.buildinfo
Files:
 3e85cb3820609f57206e15d5d7e86e51 1817 non-free/web optional otrs2_6.0.24-1.dsc
 ca1e79f82db15889ff4ace75e56a9897 25547206 non-free/web optional 
otrs2_6.0.24.orig.tar.bz2
 fc0e843d6f18659d50591f9b350a34bb 30372 non-free/web optional 
otrs2_6.0.24-1.debian.tar.xz
 834afdc6f4d8b31998236a79b3bfd1c2 5608 non-free/web optional 
otrs2_6.0.24-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEWKA9xYJCWk3IuQ4TEtmwSpDL2OQFAl4F1TEACgkQEtmwSpDL
2OQiFg/9EWILVoJsHpFkmpVcH9P4UrjXthj297w2c+HGqNRSlC0HgYHqbVtvGTxl
6DZSHICS7HXpg1RBLmu2MfwCP70+2ob1gsq4g3zP0mGVIWVunU+xGbrjzGST+Osc
sKOu1++R1zRC9le6kLyabb6cTQNXuCxqGpWbITs7D8PUW0RsMqjvaVJq1yacNmk5
4OnRl09lkwhvc4VUvwI/Jf0TB0m184T5BFt4s0rLYRQiDLx6jJZiYbAIeXYnmbr0

Bug#947446: marked as done (libreoffice: ure split lacks proper versioned Breaks+Replaces)

[Debian Bug Tracking System]

Your message dated Fri, 27 Dec 2019 10:25:22 +
with message-id 
and subject line Bug#947446: fixed in libreoffice 1:6.4.0~rc1-3
has caused the Debian Bug report #947446,
regarding libreoffice: ure split lacks proper versioned Breaks+Replaces
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.)


-- 
947446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947446
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libreoffice
Version: 1:6.4.0~rc1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi Rene,

the ure package was split recently but this lacks proper versioned
Breaks+Replaces in the new packages. This allows for unwanted partial
upgrades mixing a pre-split ure package with post-split e.g.
libjuh-java which will leave a crippled ure package installed (but
apt/dpkg think everything is fine) if libjuh-java gets removed again.

Replaces should always be used with a matching Breaks. (Taking away a
file from a replaced package "Breaks" that version. Ownership has
changed, but the replaced package does not know about it.)
The Breaks+Replaces should be versioned unless the replaced package does
no longer exist. (The package version that no longer ships the moved
file does not need to get replaced)

There were some more package splits needeing proper B+R, too.
These packages seem to be affected (but I may have missed some),
versions according to changelog entries where I found them:

missing Breaks+Replaces: ure (<< 1:6.4.0~beta1-1)
* libjuh-java
* libjurt-java
* libridl-java
* libunoloader-java

missing Breaks+Replaces: libreoffice-java-common (<< 1:6.4.0~beta1-2)
* libreoffice-smoketest-data
missing Breaks+Replaces: libreoffice-java-common (<< ???)
* libunoil-java

missing Breaks+Replaces: libreoffice-officebean (<< ???)
* libofficebean-java


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 1:6.4.0~rc1-3

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 947...@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: Fri, 27 Dec 2019 10:51:35 +0100
Source: libreoffice
Architecture: source
Version: 1:6.4.0~rc1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Rene Engelhard 
Closes: 947446
Changes:
 libreoffice (1:6.4.0~rc1-3) unstable; urgency=medium
 .
   readd test fixes which somewow got lost in preparation of -2:
 .
   * debian/tests/control:
 - smoktest: add missing -nogui and add missing libreoffice-base-nogui
   to Depends:; but use calc and core since the test actually seems to want
   to use something from it
 - junit: use the "GUI" packages
   * debian/control*in:
 - add more Breaks:/Replaces: for the new split-out Java packages (and
   libreoffice-smoketest-data) (closes: #947446)
   * debian/libreoffice-common.doc-base: also add Files:
Checksums-Sha1:
 cda9280c823dd6abfce7210aa4b3a2d4e0df96a6 30385 libreoffice_6.4.0~rc1-3.dsc
 26a536fca5faf942329347199c0e5e1269c08d1e 10902940 
libreoffice_6.4.0~rc1-3.debian.tar.xz
 d1826ca936c42f553ce9b3f20fd84522dbfce4ea 39925 
libreoffice_6.4.0~rc1-3_source.buildinfo
Checksums-Sha256:
 2fb6cda51ba1e35e31ef3ef6df6a82133d5b8e5420f2705169526bbaca9d7d77 30385 
libreoffice_6.4.0~rc1-3.dsc
 220343254501fd2180018514072527c85db07c398b139f425543dca6d005db76 10902940 
libreoffice_6.4.0~rc1-3.debian.tar.xz
 7d863b7c4e3f791bbaa607743d6cae373404f3bf0c20d6ad4cd0e54727f97741 39925 
libreoffice_6.4.0~rc1-3_source.buildinfo
Files:
 d6b52173dc67f12e8f6e14f38df05bd3 30385 editors optional 
libreoffice_6.4.0~rc1-3.dsc
 a2495a8ee048ca0db0517a0c56ec3839 10902940 editors optional 
libreoffice_6.4.0~rc1-3.debian.tar.xz
 cbcb26e813b6c0039a28978c14ed21da 39925 editors optional 
libreoffice_6.4.0~rc1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE4S3qRnUGcM+pYIAdCqBFcdA+PnAFAl4F1i4QHHJlbmVAZGVi

Bug#922578: marked as done (FTBFS against opencv 4.0.1 (exp))

[Debian Bug Tracking System]

Your message dated Fri, 27 Dec 2019 10:15:36 +
with message-id <9b74847f-7872-948c-79ee-44777ec80...@p10link.net>
and subject line closing old eviacam ftbfs bugs.
has caused the Debian Bug report #922578,
regarding FTBFS against opencv 4.0.1 (exp)
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.)


-- 
922578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eviacam
Version: 2.1.3-4.1
Severity: important

Unfortunately the pkg-config file has been marked as deprecated by
upstream...


eviacam_2.1.3-4.1_ppc64el-2019-02-15T08:25:34Z.build.zst
Description: Binary data
--- End Message ---
--- Begin Message ---

Version: 2.1.4-1

Closing a couple of old eviacam ftbs bugs, the package now builds sucessfully 
in sid.--- End Message ---

Bug#947462: htslib: FTBFS on big-endian architectures

[Graham Inggs]

Source: htslib
Version: 1.10-1
Severity: serious
Tags: ftbfs

Hi Maintainer

Since the upload of htslib 1.10-1, it has FTBFS on all big-endian
architectures [1].

I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=htslib


cd test/tabix && ./test-tabix.sh tabix.tst
Testing tabix...
PASS : $tabix -f -p vcf vcf_file.tbi.tmp.vcf.gz
FAIL : $tabix vcf_file.tbi.tmp.vcf.gz 1:3000151-3000151
Got non-zero exit code
See FAIL-vcf_file.1.3000151.out.2.{out,err} for output
FAIL : $tabix vcf_file.tbi.tmp.vcf.gz 2:3199812-3199812
Got non-zero exit code
See FAIL-vcf_file.2.3199812.out.3.{out,err} for output
PASS : $tabix -f -C -p vcf vcf_file.csi.tmp.vcf.gz
PASS : $tabix vcf_file.csi.tmp.vcf.gz 1:3000151-3000151
PASS : $tabix vcf_file.csi.tmp.vcf.gz 2:3199812-3199812
PASS : $tabix -f -p vcf large_chr.tmp.vcf.gz (must exit non-zero)
PASS : $tabix -f -C -p vcf large_chr.tmp.vcf.gz
PASS : $tabix large_chr.tmp.vcf.gz chr20:1-2147483647
PASS : $tabix -f -p bed bed_file.tbi.tmp.bed.gz
FAIL : $tabix bed_file.tbi.tmp.bed.gz Y:100200-100200
Got non-zero exit code
See FAIL-bed_file.Y.100200.out.11.{out,err} for output
PASS : $tabix -f -p gff gff_file.tbi.tmp.gff.gz
FAIL : $tabix gff_file.tbi.tmp.gff.gz X:2934832-2935190
Got non-zero exit code
See FAIL-gff_file.X.2934832.2935190.out.13.{out,err} for output

Expected   passes:   9
Unexpected passes:   0
Expected   failures: 0
Unexpected failures: 4

Bug#938818: whatthepatch: diff for NMU version 0.0.5-2.1

[Reinhard Tartler]

Thanks for the upload, Sandro.

Happy holidays!
rt

On December 23, 2019 11:22:37 PM GMT+01:00, Sandro Tosi  
wrote:
>Control: tags 938818 + patch
>
>
>Dear maintainer,
>
>I've prepared an NMU for whatthepatch (versioned as 0.0.5-2.1). The
>diff
>is attached to this message.
>
>Regards.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.