Bug#947043: cyrus-sasl2: CVE-2019-19906: Off by one in _sasl_add_string function

[Salvatore Bonaccorso]

Hi Roberto,

On Thu, Dec 19, 2019 at 08:06:19PM -0500, Roberto C. Sánchez wrote:
> On Thu, Dec 19, 2019 at 09:19:19PM +0100, Salvatore Bonaccorso wrote:
> > 
> > The following vulnerability was published for cyrus-sasl2.
> > 
> > CVE-2019-19906[0]:
> > Off by one in _sasl_add_string function
> > 
> > If you fix the vulnerability please also make sure to include the
> > CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> > 
> Hi Team,
> 
> Is anybody already working on this update?  If not, I can start on it
> possibly tomorrow or perhaps the day after.
> 
> Salvatore,
> 
> If I (or someone else on the team) prepares the upload, do we go ahead
> and make the upload then let the security team handle the DSA
> publication?

I already started yesterday, and have buster and stretch packages,
will likely release the DSA later today or tomorrow. So far tested
just lightly for stretch but will double check explicitly against
openldap.

unstable would need an update as well yet.

Can you later import then the changes in the packaging repository in
the appropriate branches?

Regards,
Salvatore

Bug#947060: resolvconf: dots stipped from dhcp search domain

[jfp]

Package: resolvconf
Version: 1.81
Severity: serious
Justification: unkown

Dear Maintainer,

dhcp supplies search domain as follows:

private BLAH.private BLAH.com

(Verified with packet capture)

resolv.conf is set to:

search private BLAHprivate BLAHcom

The domain gots are missing.

PS: Using iw rather than NetworkManager if it's relevant.



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

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

Versions of packages resolvconf depends on:
ii  debconf [debconf-2.0]  1.5.73
ii  lsb-base   11.1.0

resolvconf recommends no packages.

resolvconf suggests no packages.

-- debconf information:
  resolvconf/linkify-resolvconf: true
  resolvconf/downup-interfaces:
  resolvconf/reboot-recommended-after-removal:
  resolvconf/link-tail-to-original: false

Bug#946881: marked as done (translate-docformat: Please remove translate-docformat from Debian, package of questionable value)

[Debian Bug Tracking System]

Your message dated Fri, 20 Dec 2019 06:25:08 +
with message-id 
and subject line Bug#947026: Removed package(s) from unstable
has caused the Debian Bug report #946881,
regarding translate-docformat: Please remove translate-docformat from Debian, 
package of questionable value
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.)


-- 
946881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: translate-docformat
Version: 0.6-5
Severity: serious

Dear Maintainer,

This package is a trivial bash script, that mixes in together a
kitchensync of obsolete, bit-roted calls to web-browsers and various
xmlish/tex tools. It doesn't bring any additional value over using
existing tools directly, or better using their modern equivalents.

sgmltools-lite is orphaned and abandoned upstream and is to be removed
from Debian. And instead of porting this "app", I think it should go
as well.

No reverse dependencies, or build dependencies.

Regards,

Dimitri.
--- End Message ---
--- Begin Message ---
Version: 0.6-5+rm

Dear submitter,

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

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

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

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

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

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

Bug#945736: marked as done (seed-webkit2: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 20 Dec 2019 06:26:13 +
with message-id 
and subject line Bug#947033: Removed package(s) from unstable
has caused the Debian Bug report #945736,
regarding seed-webkit2: 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.)


-- 
945736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: seed-webkit2
Version: 4.0.0+20161014+6c77960+dfsg1-6
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

Dear submitter,

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

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

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

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

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

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

Bug#874843: marked as done (RFA: cdcat -- maintain disk media contents catalog)

[Debian Bug Tracking System]

Your message dated Fri, 20 Dec 2019 06:26:51 +
with message-id 
and subject line Bug#947037: Removed package(s) from unstable
has caused the Debian Bug report #874843,
regarding RFA: cdcat -- maintain disk media contents catalog
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.)


-- 
874843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cdcat
Version: 1.8-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 ---
Version: 1.8-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#939843: marked as done ([cdcat] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Fri, 20 Dec 2019 06:26:51 +
with message-id 
and subject line Bug#947037: Removed package(s) from unstable
has caused the Debian Bug report #939843,
regarding [cdcat] 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.)


-- 
939843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cdcat
Version: 1.8-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 ---
Version: 1.8-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#944995: marked as done (gtkimageview FTBFS: error: ‘GTypeDebugFlags’ is deprecated)

[Debian Bug Tracking System]

Your message dated Fri, 20 Dec 2019 06:24:07 +
with message-id 
and subject line Bug#946947: Removed package(s) from unstable
has caused the Debian Bug report #944995,
regarding gtkimageview FTBFS: error: ‘GTypeDebugFlags’ is deprecated
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.)


-- 
944995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtkimageview
Version: 1.6.4+dfsg-2
Severity: serious
Tags: ftbfs

gtkimageview fails to cross build from source in unstable. The crucial
bit is:

| /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is 
deprecated [-Werror=deprecated-declarations]
|   236 | voidgtk_type_init   (GTypeDebugFlagsdebug_flags);
|   | ^~~~

This is a problem, because gtkimageview builds with -Werror.

Reproducible by reproducible builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/gtkimageview_1.6.4+dfsg-2.rbuild.log.gz
Reproducible by crossqa:
http://crossqa.debian.net/build/gtkimageview_1.6.4+dfsg-2_ppc64el_20191014234854.log

As a first measure, dropping -Werror will likely make it build again,
then you likely need to fix #618962 and drop the gtk2 variant.

Helmut
--- End Message ---
--- Begin Message ---
Version: 1.6.4+dfsg-2+rm

Dear submitter,

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

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

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

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

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

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

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

[Graham Inggs]

Source: pygalmesh
Version: 0.5.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: needs-update

Hi Maintainer

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

Regards
Graham


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


___ test_inr ___

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

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

test/test_inr.py:18: AssertionError

Processed: Only in the version in experimental

[Debian Bug Tracking System]

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

> found 945742 0.10+r2052-1
Bug #945742 [src:urjtag] urjtag: Python2 removal in sid/bullseye
Marked as found in versions urjtag/0.10+r2052-1.
> notfound 945742 0.10+r2007-1.2
Bug #945742 [src:urjtag] urjtag: Python2 removal in sid/bullseye
No longer marked as found in versions urjtag/0.10+r2007-1.2.
> thanks
Stopping processing here.

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

Processed: severity of 947032 is serious

[Debian Bug Tracking System]

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

> severity 947032 serious
Bug #947032 [mnemosyne] from PIL import Image ModuleNotFoundError No module 
named PIL
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#945041: marked as done (openfoam: severe build time regression)

[Debian Bug Tracking System]

Your message dated Fri, 20 Dec 2019 05:05:11 +
with message-id 
and subject line Bug#945041: fixed in openfoam 1906.19+dfsg1-2
has caused the Debian Bug report #945041,
regarding openfoam: severe build time regression
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.)


-- 
945041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openfoam
Version: 1906+dfsg1-1
Severity: serious

Hi,

Looking at https://buildd.debian.org/status/logs.php?pkg=openfoam the
build time for your package increased unreasonably in this version.

Cheers,
Julien
--- End Message ---
--- Begin Message ---
Source: openfoam
Source-Version: 1906.19+dfsg1-2

We believe that the bug you reported is fixed in the latest version of
openfoam, 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.
Kurt Kremitzki  (supplier of updated openfoam 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, 19 Dec 2019 22:41:17 -0600
Source: openfoam
Architecture: source
Version: 1906.19+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Kurt Kremitzki 
Closes: 945041
Changes:
 openfoam (1906.19+dfsg1-2) unstable; urgency=medium
 .
   * [d64a732] Update d/watch url
   * [e72cfcf] Unset MAKEFLAGS to fix parallel builds (Closes: #945041)
Checksums-Sha1:
 ed616615f59e7cc0b4815aef3d5c6885da2f2c50 2352 openfoam_1906.19+dfsg1-2.dsc
 2f2c564ae309f0835154d5b8c838ad3eba99bd82 6104 
openfoam_1906.19+dfsg1-2.debian.tar.xz
 360b2f8c6621cb453703dfdd47bb656e04b74e76 10111 
openfoam_1906.19+dfsg1-2_source.buildinfo
Checksums-Sha256:
 57339c110e452286f526d7a115fa0858e594123321ca2a996b6430eeeced950d 2352 
openfoam_1906.19+dfsg1-2.dsc
 aa47b8f40bf3417f4a4c245d0bf9817b05e33ca0bffeab6368ebe4c1b4cfe5bf 6104 
openfoam_1906.19+dfsg1-2.debian.tar.xz
 0acceb42ceef8e3802ce2369be95a9016c4c04b6ef5f601e24e7d54d19c53434 10111 
openfoam_1906.19+dfsg1-2_source.buildinfo
Files:
 17c870227c1a49bea6308977d74fb1d6 2352 science optional 
openfoam_1906.19+dfsg1-2.dsc
 3e2134d839f121cec2a1a197381eb4f9 6104 science optional 
openfoam_1906.19+dfsg1-2.debian.tar.xz
 4f14830ae07c0f90a4dce4cff2045f7d 10111 science optional 
openfoam_1906.19+dfsg1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEh8RU7HmiYTD5HEfrKUghB0bfc8AFAl38UdcRHGt1cnRAa3dr
LnN5c3RlbXMACgkQKUghB0bfc8ASVw//Vlddl42DKbSL0fzYz6x9D3WQxBatAS+d
9NdkVfYccZmcauAPk8eFLeA5pDvqizRFfB+HuodFbDEFx/lKwQspypniFrN/MJRp
xY+PIkkdSUF174FuYpiB8RDrW0IoEMEvB+UGM7JBReTZO2SRKhTCBX4fjrBeEv8U
FVzyfcU6fmhM2YfRiqSgwR5i5Ac0+r3jcunzjbR4VQ5ORrJqMidmbmgaZosyHDXY
/eXBOr5DHeJmZibwNaGfu6WNEuOwXqHKuc/teA3xslK/xi97evGQjAgglrTq9t51
o15tN6A9iFPpDy1EO4cFQfuj6ZbmLMbxDMuoBzcZhfK+waQiVYCVEnPhbbp5otYu
oKR/+tiewjVSe68zAyPd7TU4GF29NUsY8586xFUpdPLlvWo3KPSJYLSeLI0ea+lT
34gwZZtvvNsFGH7UMOqwwcuVP1xpsCqPTXWzN49HpxPxxybuaWNrsHOHaHpua3Bo
o1YqbIiaX7fl/1MYppvG2N3AFhFyLtiLUsRs2mxxflTAxGdudbrauQsBWKdXXcSl
qGdVG1zyUYcsbeak+B8LlPoJ+jz2PNWutOO/De/wipIsyyom6B9AsGoe4dW/Eiqa
E43o+Jwd5ohI7v505GfqPpJzBbg5KtwDVfVxOM44aeuA8GJqYEf8KMrTF6Uz0f/G
kfu1AEfBIBg=
=cwM1
-END PGP SIGNATURE End Message ---

Bug#921571: afnix FTBFS on armhf when built on arm64 hardware

[Adrian Bunk]

Control: severity -1 important

On Wed, Feb 06, 2019 at 10:38:35PM +0200, Adrian Bunk wrote:
> Source: afnix
> Version: 2.9.2-1
> Severity: serious
> Tags: ftbfs
> 
> https://buildd.debian.org/status/fetch.php?pkg=afnix=armhf=2.9.2-1=1548047247=0
> 
> ...
> running: SEC0003.als
> exception : assert-error
> in file   : SEC0003.als at or around line 113
> afnix-aexec: failure SEC0003.als
> make[6]: *** [../../../../cnf/mak/afnix-rule.mak:270: SEC0003.als] Error 1
> 
> 
> This is likely an unaligned access problem.

I can reproduce it with gcc 8, but it seems to work with gcc 9.

Still FTBFS on sparc64, likely the problem is just hidden with gcc 9
on armhf.

cu
Adrian

Processed: Re: Bug#921571: afnix FTBFS on armhf when built on arm64 hardware

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #921571 [src:afnix] afnix FTBFS on armhf when built on arm64 hardware
Severity set to 'important' from 'serious'

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

Processed: py2removal RC severity updates - 2019-12-20 03:37:11.274621+00:00

[Debian Bug Tracking System]

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # for more details on this severity bump
> # sat-xmpp-core is an application, has low popcon (21 < 300), and has 0 
> external rdeps or not in testing
> severity 935358 serious
Bug #935358 [salutatoi] salutatoi: Please port to Python 3 and/or drop Python 2 
package (rdep of python-progressbar)
Severity set to 'serious' from 'normal'
> # sat-xmpp-primitivus is an application, has low popcon (16 < 300), and has 0 
> external rdeps or not in testing
> severity 935358 serious
Bug #935358 [salutatoi] salutatoi: Please port to Python 3 and/or drop Python 2 
package (rdep of python-progressbar)
Ignoring request to change severity of Bug 935358 to the same value.
> # python-aff4 is a module and has 0 external rdeps or not in testing
> severity 936110 serious
Bug #936110 [src:aff4] aff4: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # autokey-gtk is an application, has low popcon (280 < 300), and has 0 
> external rdeps or not in testing
> severity 936166 serious
Bug #936166 [src:autokey] autokey: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-backports.ssl-match-hostname is a module and has 0 external rdeps or 
> not in testing
> severity 936180 serious
Bug #936180 [src:backports.ssl-match-hostname] backports.ssl-match-hostname: 
Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # libball1.5 is an application, has low popcon (47 < 300), and has 0 external 
> rdeps or not in testing
> severity 936183 serious
Bug #936183 [src:ball] ball: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # libballview1.5 is an application, has low popcon (46 < 300), and has 0 
> external rdeps or not in testing
> severity 936183 serious
Bug #936183 [src:ball] ball: Python2 removal in sid/bullseye
Ignoring request to change severity of Bug 936183 to the same value.
> # python-ball is a module and has 0 external rdeps or not in testing
> severity 936183 serious
Bug #936183 [src:ball] ball: Python2 removal in sid/bullseye
Ignoring request to change severity of Bug 936183 to the same value.
> # python-broccoli is a module and has 0 external rdeps or not in testing
> severity 936240 serious
Bug #936240 [src:broccoli-python] broccoli-python: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> # python-calabash is a module and has 0 external rdeps or not in testing
> severity 936267 serious
Bug #936267 [src:calabash] calabash: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-capstone is a module and has 0 external rdeps or not in testing
> severity 936273 serious
Bug #936273 [src:capstone] capstone: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # crossfire-server is an application, has low popcon (44 < 300), and has 0 
> external rdeps or not in testing
> severity 936344 serious
Bug #936344 [src:crossfire] crossfire: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-drmaa is a module and has 0 external rdeps or not in testing
> severity 936444 serious
Bug #936444 [src:drmaa] drmaa: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-dulwich is a module and has 0 external rdeps or not in testing
> severity 936454 serious
Bug #936454 [src:dulwich] dulwich: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-editobj is a module and has 0 external rdeps or not in testing
> severity 936467 serious
Bug #936467 [src:editobj] editobj: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-egenix-mxbeebase is a module and has 0 external rdeps or not in 
> testing
> severity 936472 serious
Bug #936472 [src:egenix-mx-base] egenix-mx-base: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-egenix-mxproxy is a module and has 0 external rdeps or not in testing
> severity 936472 serious
Bug #936472 [src:egenix-mx-base] egenix-mx-base: Python2 removal in sid/bullseye
Ignoring request to change severity of Bug 936472 to the same value.
> # python-egenix-mxqueue is a module and has 0 external rdeps or not in testing
> severity 936472 serious
Bug #936472 [src:egenix-mx-base] egenix-mx-base: Python2 removal in sid/bullseye
Ignoring request to change severity of Bug 936472 to the same value.
> # python-egenix-mxstack is a module and has 0 external rdeps or not in testing
> severity 936472 serious
Bug #936472 [src:egenix-mx-base] egenix-mx-base: Python2 removal in sid/bullseye
Ignoring request to change severity of Bug 936472 to the same value.
> # python-egenix-mxtexttools is a module and 

Processed: tagging 942678

[Debian Bug Tracking System]

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

> tags 942678 + fixed-upstream
Bug #942678 [src:subvertpy] subvertpy ftbfs with python 3.8 (tests)
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: tagging 938262

[Debian Bug Tracking System]

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

> tags 938262 + fixed
Bug #938262 {Done: Georges Khaznadar } 
[src:python-whiteboard] python-whiteboard: Python2 removal in sid/bullseye
Added tag(s) fixed.
> thanks
Stopping processing here.

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

Bug#947053: pep8 uses python instead of python2 in the autopkg tests

[Matthias Klose]

Package: src:pep8
Version: 1.7.1-7
Severity: serious
Tags: sid bullseye

pep8 uses python instead of python2 in the autopkg tests:

autopkgtest [23:57:13]: test command1: cd "$AUTOPKGTEST_TMP" ; python -c "import
pep8; print pep8.__version__"
autopkgtest [23:57:13]: test command1: [---
bash: python: command not found
autopkgtest [23:57:13]: test command1: ---]
autopkgtest [23:57:13]: test command1:  - - - - - - - - - - results - - - - - -
- - - -
command1 FAIL non-zero exit status 127
autopkgtest [23:57:14]: test command1:  - - - - - - - - - - stderr - - - - - - -
- - -
bash: python: command not found

Bug#945041: openfoam: severe build time regression

[Adrian Bunk]

On Thu, Dec 19, 2019 at 12:31:09AM -0600, Kurt Kremitzki wrote:
> On Thursday, December 19, 2019 12:11:33 AM CST Adrian Bunk wrote:
> > On Mon, Nov 18, 2019 at 10:17:10PM +0100, Julien Cristau wrote:
> > > Source: openfoam
> > > Version: 1906+dfsg1-1
> > > Severity: serious
> > > 
> > > Hi,
> > > 
> > > Looking at https://buildd.debian.org/status/logs.php?pkg=openfoam the
> > > build time for your package increased unreasonably in this version.
> > >...
> > 
> > Something seems to be going wrong around parallel building,
> > when trying locally only one core gets used now.
> 
> Indeed, although the build logs state e.g. 'Compiling enabled on 4 cores', 
> only 1 core is ever used. However exporting the variables defined in debian/
> rules and following the same build steps in a shell results in a build which 
> does actually use the number of cores it reports, so I wasn't sure where to 
> proceed with troubleshooting it beyond that. I mentioned the issue to my 
> upstream contact as well who wasn't sure either given that it behaves as 
> expected in a shell but not in the build environment.

wmake/wmake:
...
if [ -n "$WM_NCOMPPROCS" ]
then
parOpt="-j $WM_NCOMPPROCS"

if [ "$WM_NCOMPPROCS" -gt 1 -a -z "$MAKEFLAGS" ]
then
make="$make --no-print-directory $parOpt"
fi
fi
...


The problem is that MAKEFLAGS is set to "w",
as fix/workaround add in debian/rules:
  unexport MAKEFLAGS

cu
Adrian

Processed: block 938859 with 946984

[Debian Bug Tracking System]

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

> block 938859 with 946984
Bug #938859 {Done: Anton Gladky } [src:yade] yade: Python2 
removal in sid/bullseye
938859 was not blocked by any bugs.
938859 was blocking: 936227 936743 936995 937050 937290 937455 937513 937569 
937603 937695 937960 938198 938275 938490 938528 938655 938656 943172
Added blocking bug(s) of 938859: 946984
> thanks
Stopping processing here.

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

Processed: block 946223 with 946984

[Debian Bug Tracking System]

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

> block 946223 with 946984
Bug #946223 {Done: Anton Gladky } [src:yade] [NMU] FTFBS with 
CGAL 5.0
946223 was not blocked by any bugs.
946223 was blocking: 944417
Added blocking bug(s) of 946223: 946984
> thanks
Stopping processing here.

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

Bug#947043: cyrus-sasl2: CVE-2019-19906: Off by one in _sasl_add_string function

[Roberto C . Sánchez]

On Thu, Dec 19, 2019 at 09:19:19PM +0100, Salvatore Bonaccorso wrote:
> 
> The following vulnerability was published for cyrus-sasl2.
> 
> CVE-2019-19906[0]:
> Off by one in _sasl_add_string function
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> 
Hi Team,

Is anybody already working on this update?  If not, I can start on it
possibly tomorrow or perhaps the day after.

Salvatore,

If I (or someone else on the team) prepares the upload, do we go ahead
and make the upload then let the security team handle the DSA
publication?

Regards,

-Roberto

-- 
Roberto C. Sánchez

Processed: re: muse FTBFS after libfluidsynth update

[Debian Bug Tracking System]

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

> tags 946917 +patch
Bug #946917 [src:muse] muse FTBFS after libfluidsynth update
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#946917: muse FTBFS after libfluidsynth update

[Peter Green]

tags 946917 +patch
thanks

I whipped up a patch that makes this build, I have not tested it beyond that. 
There were two main fixes, the first is that delete_fluid_synth no longer 
returns an error code, the second is a few structures are now opaque and have 
to be accessed through accessors.

I also found I had to add a build-dependency on libegl-dev to make the 
configure script complete successfully. It seems that 
/usr/lib/x86_64-linux-gnu/libEGL.so has moved from libglvnd-dev to libegl-dev

The debdiff is attached, I don't have any immediate plans to NMU, but I may do 
so later, especially if I get positive feedback about the patch from users.

diff -Nru muse-3.0.2+ds1/debian/changelog muse-3.0.2+ds1/debian/changelog
--- muse-3.0.2+ds1/debian/changelog 2018-12-16 13:37:01.0 +
+++ muse-3.0.2+ds1/debian/changelog 2019-12-19 17:49:59.0 +
@@ -1,3 +1,13 @@
+muse (3.0.2+ds1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix build with fluidsynth 2.
+  * Bump fluidsynth build-dependency since patch will make the code 
incompatible
+   with fluidsynth 1.
+  * Add build-depends on libegl-dev
+
+ -- Peter Michael Green   Thu, 19 Dec 2019 17:49:59 +
+
 muse (3.0.2+ds1-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru muse-3.0.2+ds1/debian/control muse-3.0.2+ds1/debian/control
--- muse-3.0.2+ds1/debian/control   2018-12-16 13:37:01.0 +
+++ muse-3.0.2+ds1/debian/control   2019-12-19 17:49:59.0 +
@@ -11,7 +11,7 @@
  dssi-dev,
  libasound2-dev,
  libdssialsacompat-dev [!linux-any],
- libfluidsynth-dev,
+ libfluidsynth-dev (>= 2),
  libjack-dev,
  liblilv-dev (>= 0.22),
  liblo-dev,
@@ -21,7 +21,8 @@
  libsord-dev (>= 0.14),
  lv2-dev (>= 1.12),
  qtbase5-dev,
- qttools5-dev
+ qttools5-dev,
+ libegl-dev
 Standards-Version: 4.2.1
 Homepage: http://www.muse-sequencer.org/
 Vcs-Git: https://salsa.debian.org/multimedia-team/muse.git
diff -Nru muse-3.0.2+ds1/debian/patches/0005-fluidsynth2.patch 
muse-3.0.2+ds1/debian/patches/0005-fluidsynth2.patch
--- muse-3.0.2+ds1/debian/patches/0005-fluidsynth2.patch1970-01-01 
00:00:00.0 +
+++ muse-3.0.2+ds1/debian/patches/0005-fluidsynth2.patch2019-12-19 
17:49:59.0 +
@@ -0,0 +1,112 @@
+Description: Fix build with fluidsynth 2.
+ The changes consist of some adjustments for the fact that some structures are
+ nowopaque and the removal of error handling for delete_fluid_synth which no
+ longer returns an error value.
+Author: Peter Michael Green 
+
+---
+The information above should follow the Patch Tagging Guidelines, please
+checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
+are templates for supplementary fields that you might want to add:
+
+Origin: , 
+Bug: 
+Bug-Debian: https://bugs.debian.org/
+Bug-Ubuntu: https://launchpad.net/bugs/
+Forwarded: 
+Reviewed-By: 
+Last-Update: 2019-12-19
+
+Index: muse-3.0.2+ds1/synti/fluidsynth/fluidsynti.cpp
+===
+--- muse-3.0.2+ds1.orig/synti/fluidsynth/fluidsynti.cpp
 muse-3.0.2+ds1/synti/fluidsynth/fluidsynti.cpp
+@@ -155,16 +155,12 @@ FluidSynth::~FluidSynth()
+   std::cerr << DEBUG_ARGS << "Error unloading soundfont!" << 
fluid_synth_error(fluidsynth) << std::endl;
+   }
+ 
+-  int err = delete_fluid_synth (fluidsynth);
++  delete_fluid_synth (fluidsynth);
+   if(gui)
+ delete gui;
+ 
+   if (initBuffer)
+ delete [] initBuffer;
+-  if (err == -1) {
+-std::cerr << DEBUG_ARGS << "error while destroying synth: " << 
fluid_synth_error(fluidsynth) << std::endl;
+-return;
+-}
+   }
+ 
+ bool FluidSynth::init(const char* name)
+@@ -1368,7 +1364,7 @@ const char* FluidSynth::getPatchName(int
+   else {
+ fluid_preset_t *preset = 
fluid_synth_get_channel_preset(fluidsynth, i);
+ if (!preset) return "";
+-return preset->get_name(preset);
++return fluid_preset_get_name(preset);
+ }
+   }
+ //-
+@@ -1414,12 +1410,12 @@ const MidiPatch* FluidSynth::getFirstPat
+   if (!channels[channel].drumchannel) {
+ for (unsigned bank = 0; bank < 128; ++bank) {
+   for (unsigned patch = 0; patch < 128; ++patch) {
+-preset = sfont->get_preset (sfont, bank, patch);
++preset = fluid_sfont_get_preset (sfont, bank, patch);
+ if (preset) {
+   midiPatch.hbank = bank;
+   midiPatch.lbank = 0xff;  // Off
+   midiPatch.prog = patch;
+-  midiPatch.name = preset->get_name (preset);
++  midiPatch.name = fluid_preset_get_name (preset);
+   return 
+   

Bug#926795: marked as done (di-netboot-assistant: Unable to install Debian Buster amd64 from d-i n-a at 2019-04-10 generated boot-file)

[Debian Bug Tracking System]

Your message dated Thu, 19 Dec 2019 23:19:12 +
with message-id 
and subject line Bug#749991: fixed in anna 1.73
has caused the Debian Bug report #749991,
regarding di-netboot-assistant: Unable to install Debian Buster amd64 from d-i 
n-a at 2019-04-10 generated boot-file
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.)


-- 
749991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: di-netboot-assistant
Version: 0.60
Severity: normal

Dear Maintainer,

the "Debian testing (amd64) image 20190410", generated by

di-netboot-assistant install stable testing

shows after answering a few installer querstions the following dialog:

"[!!] Download installer components

No kernel modules were found. This probably is due to a mismatch between
the kernel used by this version of the Installer and the kernel version
available in the archive.

If you 're Installing from a mirror, you can work around this problem
by choosing to Install a different version of Debian. The Install will
probably fail to work if you continue without kernel modules.

Continue the Install without loading kernel modules?

  "

No matter what I select, the installer will fail.

Seems kernel and mirror are out of sycn...

Thanks for any hint

Ralf


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

Kernel: Linux 4.19.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: anna
Source-Version: 1.73

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

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated anna 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, 19 Dec 2019 23:44:26 +0100
Source: anna
Architecture: source
Version: 1.73
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 367515 749991
Changes:
 anna (1.73) unstable; urgency=medium
 .
   * Team upload
 .
   [ Holger Wansing ]
   * Change template, to give a senseful message to the user, when no kernel
 modules can be found.
 Also, turn that from a question into an error message, since continuing
 isn't possible without kernel modules anyway.
 Includes updating all po|pot files.
 Closes: #749991, #367515.
 .
   [ Stefanos Chaliasos ]
   * Fix missing input of util.h in Makefile.
 .
   [ Updated translations ]
   * German (de.po) by Holger Wansing
   * French (fr.po) by Baptiste Jammet
   * Hebrew (he.po) by Yaron Shahrabani
   * Indonesian (id.po) by Andika Triwidada
   * Icelandic (is.po) by Sveinn í Felli
   * Norwegian Bokmal (nb.po) by Deleted User
   * Dutch (nl.po) by Frans Spiesschaert
   * Punjabi (Gurmukhi) (pa.po) by Aman ALam
   * Portuguese (pt.po) by Miguel Figueiredo
   * Serbian (sr.po) by Filipovic Dragan
   * Swedish (sv.po) by Mattias Münster
Checksums-Sha1:
 9303cfcc2c91470d40ee3c51e1f0070ef4ce3b6b 1657 anna_1.73.dsc
 a83d97f69295e14737944923588636696506ecb9 86528 anna_1.73.tar.xz
 21de9e487060ee4e5d3a4a01c6e531c897d68bab 5580 anna_1.73_amd64.buildinfo
Checksums-Sha256:
 39a1e2b876f2d463cbece6c2fa99850511cd36bdb563291a799d3a6ab03af3c9 1657 
anna_1.73.dsc
 0339d7ec220a9da7ea9e5f669a3989ba625e7504234f3f06f68cc33740c54ef3 86528 
anna_1.73.tar.xz
 45117a6a32b86c5e00501410255aee803e6a990d6cc35232fd6afd744e2ad73e 5580 
anna_1.73_amd64.buildinfo
Files:
 fd5e473c9c66797a4dd299626c9a1614 1657 debian-installer standard anna_1.73.dsc
 02c80229275588246792edea9e8e159c 86528 debian-installer standard 
anna_1.73.tar.xz
 c29d4fcbaf21b033032a0a4bab4404ad 5580 debian-installer standard 
anna_1.73_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAl38AisVHGh3YW5zaW5n

Bug#749991: marked as done (debian-installer: Wrong kernel in debian-installer package)

[Debian Bug Tracking System]

Your message dated Thu, 19 Dec 2019 23:19:12 +
with message-id 
and subject line Bug#749991: fixed in anna 1.73
has caused the Debian Bug report #749991,
regarding debian-installer: Wrong kernel in debian-installer package
to be marked as done.

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

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


-- 
749991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: testing
Severity: important
Tags: d-i

When trying to install debian-testign from netboot image the instalation fails 
due wrong kernel modules. The installer reports on tty4 http error 403. I used 
multiple mirrors and combinations of versions. Last time that i tried to 
install jessie version the version of netboot was SID.

Thank You

Have a nice day
ewew


-- System Information:
Debian Release: 7.5
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: anna
Source-Version: 1.73

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

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated anna 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, 19 Dec 2019 23:44:26 +0100
Source: anna
Architecture: source
Version: 1.73
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 367515 749991
Changes:
 anna (1.73) unstable; urgency=medium
 .
   * Team upload
 .
   [ Holger Wansing ]
   * Change template, to give a senseful message to the user, when no kernel
 modules can be found.
 Also, turn that from a question into an error message, since continuing
 isn't possible without kernel modules anyway.
 Includes updating all po|pot files.
 Closes: #749991, #367515.
 .
   [ Stefanos Chaliasos ]
   * Fix missing input of util.h in Makefile.
 .
   [ Updated translations ]
   * German (de.po) by Holger Wansing
   * French (fr.po) by Baptiste Jammet
   * Hebrew (he.po) by Yaron Shahrabani
   * Indonesian (id.po) by Andika Triwidada
   * Icelandic (is.po) by Sveinn í Felli
   * Norwegian Bokmal (nb.po) by Deleted User
   * Dutch (nl.po) by Frans Spiesschaert
   * Punjabi (Gurmukhi) (pa.po) by Aman ALam
   * Portuguese (pt.po) by Miguel Figueiredo
   * Serbian (sr.po) by Filipovic Dragan
   * Swedish (sv.po) by Mattias Münster
Checksums-Sha1:
 9303cfcc2c91470d40ee3c51e1f0070ef4ce3b6b 1657 anna_1.73.dsc
 a83d97f69295e14737944923588636696506ecb9 86528 anna_1.73.tar.xz
 21de9e487060ee4e5d3a4a01c6e531c897d68bab 5580 anna_1.73_amd64.buildinfo
Checksums-Sha256:
 39a1e2b876f2d463cbece6c2fa99850511cd36bdb563291a799d3a6ab03af3c9 1657 
anna_1.73.dsc
 0339d7ec220a9da7ea9e5f669a3989ba625e7504234f3f06f68cc33740c54ef3 86528 
anna_1.73.tar.xz
 45117a6a32b86c5e00501410255aee803e6a990d6cc35232fd6afd744e2ad73e 5580 
anna_1.73_amd64.buildinfo
Files:
 fd5e473c9c66797a4dd299626c9a1614 1657 debian-installer standard anna_1.73.dsc
 02c80229275588246792edea9e8e159c 86528 debian-installer standard 
anna_1.73.tar.xz
 c29d4fcbaf21b033032a0a4bab4404ad 5580 debian-installer standard 
anna_1.73_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAl38AisVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2cXUQAKu/zJdA7esPUg3/1QT09r6BPvQM
FubSOI3zluMFWPRwpB6+SG1io8o6pBZ15vHt/8Xg7vWL6b35IRNqbt03FKexcMtc
5p16OEJXF0buyqPdv+Xv/M9mVt5R8DSYZKm8NpmKw8dDG/Vl2E//Llqza3YhOctL
bxVaq7YLmNiYckLMxRrTDKezGXPbr5QgmEEIRHvXOlw8XS0rl7bq/KwlSXl33/lm
rZ5KKX1DkrAxi4CfIXG9B3SQvdhJdIHaYAGHJAJEcM3qwPwBqGIozJH+1+ApqTbp
+NgsuyB8ejy3LDY2ZfZR0weQKHCl2Q+6KZAHFB77hqU6ndkNwOgH8PwKsmYcMYqv
s8KRYS0yEttfDzv9iimutd2Idjj/aIf4EC55kEAsY7Z8hVKW4HBS0exS+mh/TJvy
tOMdVzq6NxHey67Cwf81p17unMqaODYSgqbbhTo6KDVu4K04dH1ze27PjIuMXu5L
XHLLsrTsFf8uN590r48X85+2JKK1hKYbwJY0Qcs/V9fubbNx6bx/RScc37s54GNf

Bug#944277: actually a bug in camlp5

[Christopher Cramer]

This is probably caused by a bug in camlp5, caught by a stricter dynamic
linker in OCaml 4.08. It is fixed in camlp5 7.10.

See https://github.com/camlp5/camlp5/pull/46

Processed: tagging 936336

[Debian Bug Tracking System]

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

> tags 936336 + fixed-upstream
Bug #936336 [src:coz-profiler] coz-profiler: Python2 removal in sid/bullseye
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#947043: cyrus-sasl2: CVE-2019-19906: Off by one in _sasl_add_string function

[Salvatore Bonaccorso]

Control: tags -1 + patch

Hi,

On Thu, Dec 19, 2019 at 09:19:19PM +0100, Salvatore Bonaccorso wrote:
> Source: cyrus-sasl2
> Version: 2.1.27+dfsg-1
> Severity: grave
> Tags: security upstream
> Forwarded: https://github.com/cyrusimap/cyrus-sasl/issues/587
> Control: found -1 2.1.27~101-g0780600+dfsg-3
> 
> Hi,
> 
> The following vulnerability was published for cyrus-sasl2.
> 
> CVE-2019-19906[0]:
> Off by one in _sasl_add_string function
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> 
> For further information see:
> 
> [0] https://security-tracker.debian.org/tracker/CVE-2019-19906
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19906
> [1] https://github.com/cyrusimap/cyrus-sasl/issues/587

Attached patch for this issue.

Regards,
Salvatore
Description: CVE-2019-19906: Off-by-one in _sasl_add_string function
Origin: vendor
Bug: https://github.com/cyrusimap/cyrus-sasl/issues/587
Bug-Debian: https://bugs.debian.org/947043
Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2019-19906
Author: Stephan Zeisberg 
Reviewed-by: Salvatore Bonaccorso 
Last-Update: 2019-12-19

--- a/lib/common.c
+++ b/lib/common.c
@@ -190,7 +190,7 @@ int _sasl_add_string(char **out, size_t
 
   if (add==NULL) add = "(null)";
 
-  addlen=strlen(add); /* only compute once */
+  addlen=strlen(add)+1; /* only compute once */
   if (_buf_alloc(out, alloclen, (*outlen)+addlen)!=SASL_OK)
 return SASL_NOMEM;
 

Processed: Re: Bug#947043: cyrus-sasl2: CVE-2019-19906: Off by one in _sasl_add_string function

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #947043 [src:cyrus-sasl2] cyrus-sasl2: CVE-2019-19906: Off-by-one in 
_sasl_add_string function
Added tag(s) patch.

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

Processed: retitle 947043 to cyrus-sasl2: CVE-2019-19906: Off-by-one in _sasl_add_string function

[Debian Bug Tracking System]

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

> retitle 947043 cyrus-sasl2: CVE-2019-19906: Off-by-one in _sasl_add_string 
> function
Bug #947043 [src:cyrus-sasl2] cyrus-sasl2: CVE-2019-19906: Off by one in 
_sasl_add_string function
Changed Bug title to 'cyrus-sasl2: CVE-2019-19906: Off-by-one in 
_sasl_add_string function' from 'cyrus-sasl2: CVE-2019-19906: Off by one in 
_sasl_add_string function'.
> thanks
Stopping processing here.

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

Processed: bug 936206 is forwarded to https://github.com/google/binplist/issues/6

[Debian Bug Tracking System]

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

> forwarded 936206 https://github.com/google/binplist/issues/6
Bug #936206 [src:binplist] binplist: Python2 removal in sid/bullseye
Set Bug forwarded-to-address to 'https://github.com/google/binplist/issues/6'.
> thanks
Stopping processing here.

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

Processed: tagging 936172

[Debian Bug Tracking System]

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

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

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

Processed: add patch tag to bug

[Debian Bug Tracking System]

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

> tags 922692 patch
Bug #922692 [src:galax] galax: FTBFS - ERROR: unable to find 
camomileLibrary.cmi in /usr/lib/ocaml/camomile
Added tag(s) patch.
> quit
Stopping processing here.

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

Processed: cyrus-sasl2: CVE-2019-19906: Off by one in _sasl_add_string function

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.1.27~101-g0780600+dfsg-3
Bug #947043 [src:cyrus-sasl2] cyrus-sasl2: CVE-2019-19906: Off by one in 
_sasl_add_string function
Marked as found in versions cyrus-sasl2/2.1.27~101-g0780600+dfsg-3.

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

Bug#910945: fontcustom: diff for NMU version 2.0.0+ds4-5.1

[Paul Gevers]

Control: tags 910945 + patch
Control: tags 910945 + pending
Control: tags 936537 + pending

Dear maintainer,

I've prepared an NMU for fontcustom (versioned as 2.0.0+ds4-5.1) and
uploaded it with dgit to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.
Paul

diff -Nru fontcustom-2.0.0+ds4/debian/changelog
fontcustom-2.0.0+ds4/debian/changelog
--- fontcustom-2.0.0+ds4/debian/changelog   2018-10-05 18:39:21.0
+0200
+++ fontcustom-2.0.0+ds4/debian/changelog   2019-12-19 20:02:14.0
+0100
@@ -1,3 +1,14 @@
+fontcustom (2.0.0+ds4-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Convert to Python 3, thanks to Graham Inggs (Closes: #936537)
+  * gemspec: update json to 2.0, thanks to Alexandre Viau (Closes:
+#910945)
+  * Drop "Testsuite: autopkgtest-pkg-ruby" as it isn't testing anything
+and requires more non-trivial work to get it working
+
+ -- Paul Gevers   Thu, 19 Dec 2019 20:02:14 +0100
+
 fontcustom (2.0.0+ds4-5) unstable; urgency=medium

   * Depend on python.
diff -Nru fontcustom-2.0.0+ds4/debian/control
fontcustom-2.0.0+ds4/debian/control
--- fontcustom-2.0.0+ds4/debian/control 2018-10-05 18:39:21.0 +0200
+++ fontcustom-2.0.0+ds4/debian/control 2019-12-19 20:02:14.0 +0100
@@ -8,14 +8,13 @@
 Vcs-Git: https://salsa.debian.org/debian/fontcustom.git
 Vcs-Browser: https://salsa.debian.org/debian/fontcustom
 Homepage: https://github.com/FontCustom/fontcustom
-Testsuite: autopkgtest-pkg-ruby
 XS-Ruby-Versions: all

 Package: fontcustom
 Architecture: all
 XB-Ruby-Versions: ${ruby:Versions}
 Depends: ruby | ruby-interpreter,
- python,
+ python3,
  ruby-thor,
  ruby-json,
  ruby-listen,
diff -Nru fontcustom-2.0.0+ds4/debian/patches/convert-to-python3.patch
fontcustom-2.0.0+ds4/debian/patches/convert-to-python3.patch
--- fontcustom-2.0.0+ds4/debian/patches/convert-to-python3.patch
1970-01-01 01:00:00.0 +0100
+++ fontcustom-2.0.0+ds4/debian/patches/convert-to-python3.patch
2019-12-19 20:02:14.0 +0100
@@ -0,0 +1,18 @@
+From: Paul Gevers 
+Date: Thu, 19 Dec 2019 13:12:58 +0100
+X-Dgit-Generated: 2.0.0+ds4-5.1 8e1f57ecec8429b302c888d4f393248d4d863b41
+Subject: Convert to Python3
+
+Thanks to Graham Inggs
+Closes: #936537
+
+---
+
+--- fontcustom-2.0.0+ds4.orig/lib/fontcustom/scripts/eotlitetool.py
 fontcustom-2.0.0+ds4/lib/fontcustom/scripts/eotlitetool.py
+@@ -1,4 +1,4 @@
+-#!/usr/bin/env python
++#!/usr/bin/python3
+ # * BEGIN LICENSE BLOCK *
+ # Version: MPL 1.1/GPL 2.0/LGPL 2.1
+ #
diff -Nru
fontcustom-2.0.0+ds4/debian/patches/gemspec-update-json-to-2.0.patch
fontcustom-2.0.0+ds4/debian/patches/gemspec-update-json-to-2.0.patch
--- fontcustom-2.0.0+ds4/debian/patches/gemspec-update-json-to-2.0.patch
1970-01-01 01:00:00.0 +0100
+++ fontcustom-2.0.0+ds4/debian/patches/gemspec-update-json-to-2.0.patch
2019-12-19 20:02:14.0 +0100
@@ -0,0 +1,21 @@
+From: Paul Gevers 
+Date: Thu, 19 Dec 2019 13:16:29 +0100
+X-Dgit-Generated: 2.0.0+ds4-5.1 499a669af6b81a987e6b5f2568f765cd87adf100
+Subject: gemspec: update json to 2.0
+
+Thanks to Alexandre Viau
+Closes: #910945
+
+---
+
+--- fontcustom-2.0.0+ds4.orig/fontcustom.gemspec
 fontcustom-2.0.0+ds4/fontcustom.gemspec
+@@ -18,7 +18,7 @@ Gem::Specification.new do |gem|
+   gem.test_files= gem.files.grep(%r{^(test|spec|features)/})
+   gem.require_paths = ["lib"]
+
+-  gem.add_dependency "json", "~>1.4"
++  gem.add_dependency "json", "~>2.0"
+   gem.add_dependency "thor", "~>0.14"
+   gem.add_dependency "listen", ">=1.0","<4.0"
+
diff -Nru
fontcustom-2.0.0+ds4/debian/patches/generate.py-support-python.patch
fontcustom-2.0.0+ds4/debian/patches/generate.py-support-python.patch
--- fontcustom-2.0.0+ds4/debian/patches/generate.py-support-python.patch
1970-01-01 01:00:00.0 +0100
+++ fontcustom-2.0.0+ds4/debian/patches/generate.py-support-python.patch
2019-12-19 20:02:14.0 +0100
@@ -0,0 +1,19 @@
+From: Paul Gevers 
+Date: Thu, 19 Dec 2019 20:55:27 +0100
+X-Dgit-Generated: 2.0.0+ds4-5.1 c6b34e17e6d2a9e517bfec3bd20c2e4f8e229a1e
+Subject: generate.py support python
+
+
+---
+
+--- fontcustom-2.0.0+ds4.orig/lib/fontcustom/scripts/generate.py
 fontcustom-2.0.0+ds4/lib/fontcustom/scripts/generate.py
+@@ -126,7 +126,7 @@ try:
+ manifest['fonts'].append(fontfile + '.woff')
+
+ # Convert EOT for IE7
+-subprocess.call('python ' + scriptPath + '/eotlitetool.py ' +
fontfile + '.ttf -o ' + fontfile + '.eot', shell=True)
++subprocess.call('python3 ' + scriptPath + '/eotlitetool.py ' +
fontfile + '.ttf -o ' + fontfile + '.eot', shell=True)
+ # check if windows
+ if os.name == 'nt':
+ subprocess.call('move ' + fontfile + '.eotlite ' + fontfile +
'.eot', shell=True)
diff -Nru fontcustom-2.0.0+ds4/debian/patches/series
fontcustom-2.0.0+ds4/debian/patches/series
--- fontcustom-2.0.0+ds4/debian/patches/series  2018-10-05
18:39:21.0 +0200
+++ 

Processed: fontcustom: diff for NMU version 2.0.0+ds4-5.1

[Debian Bug Tracking System]

Processing control commands:

> tags 910945 + patch
Bug #910945 [src:fontcustom] fontcustom: autopkgtest fails
Ignoring request to alter tags of bug #910945 to the same tags previously set
> tags 910945 + pending
Bug #910945 [src:fontcustom] fontcustom: autopkgtest fails
Ignoring request to alter tags of bug #910945 to the same tags previously set
> tags 936537 + pending
Bug #936537 [src:fontcustom] fontcustom: Python2 removal in sid/bullseye
Ignoring request to alter tags of bug #936537 to the same tags previously set

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

Processed: Re: Bug#946359: Info received (Bug#946359: pg-snakeoil: Selftest apears to be broken)

[Debian Bug Tracking System]

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

> forwarded 946359 https://bugzilla.clamav.net/show_bug.cgi?id=12440
Bug #946359 {Done: Christoph Berg } [pg-snakeoil] pg-snakeoil: 
Selftest apears to be broken
Set Bug forwarded-to-address to 
'https://bugzilla.clamav.net/show_bug.cgi?id=12440'.
>
End of message, stopping processing here.

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

Processed: fontcustom: diff for NMU version 2.0.0+ds4-5.1

[Debian Bug Tracking System]

Processing control commands:

> tags 910945 + patch
Bug #910945 [src:fontcustom] fontcustom: autopkgtest fails
Added tag(s) patch.
> tags 910945 + pending
Bug #910945 [src:fontcustom] fontcustom: autopkgtest fails
Added tag(s) pending.
> tags 936537 + pending
Bug #936537 [src:fontcustom] fontcustom: Python2 removal in sid/bullseye
Added tag(s) pending.

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

Bug#947043: cyrus-sasl2: CVE-2019-19906: Off by one in _sasl_add_string function

[Salvatore Bonaccorso]

Source: cyrus-sasl2
Version: 2.1.27+dfsg-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/cyrusimap/cyrus-sasl/issues/587
Control: found -1 2.1.27~101-g0780600+dfsg-3

Hi,

The following vulnerability was published for cyrus-sasl2.

CVE-2019-19906[0]:
Off by one in _sasl_add_string function

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-19906
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19906
[1] https://github.com/cyrusimap/cyrus-sasl/issues/587

Regards,
Salvatore

Bug#937900: [pkg-lxc-devel] Bug#937900: python-lxc: Python2 removal in sid/bullseye

[Evgeni Golov]

Hi Moritz,

yeah, that sounds reasonable.

PEB, terceiro, any objections?

Evgeni

On December 19, 2019 7:43:30 PM UTC, "Moritz Mühlenhoff"  
wrote:
>On Fri, Aug 30, 2019 at 07:41:57AM +, Matthias Klose wrote:
>> Package: src:python-lxc
>> Version: 0.1-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
>
>Hi Evgeni,
>there are no remaining rdeps for python-lxc and Python 3 support is
>available via the separate python3-lxc source package, let's remove?
>
>Cheers,
>Moritz
>
>___
>Pkg-lxc-devel mailing list
>pkg-lxc-de...@alioth-lists.debian.net
>https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-lxc-devel

Bug#937900: python-lxc: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

On Fri, Aug 30, 2019 at 07:41:57AM +, Matthias Klose wrote:
> Package: src:python-lxc
> Version: 0.1-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

Hi Evgeni,
there are no remaining rdeps for python-lxc and Python 3 support is
available via the separate python3-lxc source package, let's remove?

Cheers,
Moritz

Bug#947039: libapache2-mod-auth-pgsql: AuthType Basic configured without corresponding module

[Bernd Zeimetz]

Package: libapache2-mod-auth-pgsql
Version: 2.0.3-6.1
Severity: serious

As far as I can see one of the issues from #666814 has reincarnated the 
package since Stretch. I could not get the auth module to work at all due to


AH01796: AuthType Basic configured without corresponding module

Due to the low popcon and auth_dbd being available, I'd assume nobody 
noticed this at all.



--
Bernd Zeimetz
Senior Systems Engineer
Debian Developer, Palo Alto ACE, RHCE, RHCS-PaaS

conova communications GmbH
Zentrale Salzburg
Karolingerstraße 36a
5020 Salzburg, Austria

T +43 662/22 00-313
M +43 676/830 50 313
b.zeim...@conova.com
www.conova.com

Gesetzliche Pflichtangaben:
www.conova.com/impressum
www.conova.com/datenschutz


smime.p7s
Description: S/MIME cryptographic signature

Bug#947005: nethack: buffer overflow when parsing config files

[Salvatore Bonaccorso]

Control: retitle -1 nethack: CVE-2019-19905: buffer overflow when parsing 
config files

On Thu, Dec 19, 2019 at 11:57:42AM +0100, Reiner Herrmann wrote:
> Source: nethack
> Version: 3.6.0-1
> Severity: grave
> Tags: security
> X-Debbugs-Cc: t...@security.debian.org
> 
> Hi,
> 
> a new version of NetHack has been released that fixes a privilege
> escalation issue introduced in 3.6.0 [0] [1]:
> 
> > A buffer overflow issue exists when reading very long lines from a
> > NetHack configuration file (usually named .nethackrc).
> > 
> > This vulnerability affects systems that have NetHack installed suid/sgid
> > and shared systems that allow users to upload their own configuration
> > files.
> > 
> > All users are urged to upgrade to NetHack 3.6.4 as soon as possible. 
> 
> As the Debian packages ship setgid binaries, I think they are affected by it.
> 
> At least these two commits look related:
>  https://github.com/NetHack/NetHack/commit/f4a840a
>  https://github.com/NetHack/NetHack/commit/f001de7

This issue has been assigned CVE-2019-19905 by MITRE.

Regards,
Salvatore

Bug#946359: pg-snakeoil: Selftest apears to be broken

[Sebastian Andrzej Siewior]

On 2019-12-19 10:04:48 [+0100], Christoph Berg wrote:
> Re: Sebastian Andrzej Siewior 2019-12-18 
> <20191218225837.qttuxpwrbo5ukpr3@flow>
> > > $ sudo -u clamav freshclam --verbose
> > 
> > what happens if you strip the sudo part? One of the first thing is to
> > change to the clamav user (well so is my memory and the /var/…/clamav is
> > owned by clamav so…)? However after I install sudo in my chroot and try
> > this it still works :/
> 
> Now it just works, both with "sudo freshclam --verbose" and "sudo -u
> clamav freshclam --verbose":

I meant without sudo but here you go.

> Thu Dec 19 10:00:36 2019 -> *updatedb: Running g_cb_download_complete 
> callback...

and now out of the sudden it is no longer outdated.

> > > Time: 2.4s, ETA; 0.0s [===>] 
> > > 52.81MiB/52.81MiB   
> > > * Connection #0 to host database.clamav.net left intact
> > > Wed Dec 18 11:56:13 2019 -> ^Mirror https://database.clamav.net is not 
> > > synchronized.
> > 
> > So I don't have this. And for that to happen you need an out-dated
> > database. And somehow you have that and the ci host. Reproducible.
> 
> Maybe there was one bad server in the mirror list...

right. And the same server is used ci.debian.net. For days.
The database server sits behind cloudflare's CDN [0]. Which means
something would bad with the CDN. But then it appears to work with the
old freshclam while new one throws the problem. So it might be a problem
somewhere else.

[0] https://blog.clamav.net/2018/09/want-to-improve-your-clamav-experience.html

> > If the `sudo' part makes no difference, can you stash me your chroot or
> > the other way around? There must be something that is different.
> 
> One bit that could have been relevant is that I'm running on schroot
> with tmpfs on an overlay fs.

But that part is transparent. I would expect a transparent proxy,
dns-preload library or an odd package which somehow influeces
curl/freshclam.

> Christoph

Sebastian

Processed: Re: Bug#947005: nethack: buffer overflow when parsing config files

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 nethack: CVE-2019-19905: buffer overflow when parsing config files
Bug #947005 [src:nethack] nethack: buffer overflow when parsing config files
Changed Bug title to 'nethack: CVE-2019-19905: buffer overflow when parsing 
config files' from 'nethack: buffer overflow when parsing config files'.

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

Bug#874843: [cdcat] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Mon, Aug 26, 2019 at 09:30:48AM +0200, Eduard Bloch wrote:
> reassign 874843 wnpp
> retitle 874843 RFA: cdcat - maintain disk media contents catalog
> thanks
> 
> Hallo Moritz,
> * Moritz Mühlenhoff [Thu, Aug 22 2019, 11:16:12PM]:
> > On Sat, Sep 09, 2017 at 09:03:03PM +0200, Lisandro Damián Nicanor Pérez 
> > Meyer wrote:
> > > Source: cdcat
> > >
> > > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> > > as [announced] in:
> > >
> > > [announced] 
> > > 
> > >
> > > 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
> >
> > Eduard,
> > cdcat is dead upstream, are you planning to port it to Qt5 yourself or 
> > should
> > it be removed from the archive?
> 
> IMHO, unless some wants to contribute here, it can go for good.
> 
> TBH it was not just porting to Qt5 but also architectural issues in later
> versions which I refused to package the way they were designed
> (depending on build-time config and weird 3rd party libs). And I don't
> have time nor much interest to continue here.
> 
> Thanks for pushing, I am making this request RFA for now and it can
> become RoM by the time you are RoMing qt4.

We're now wrapping up the remaining rev deps of Qt4 and noone adopted it
since then so I just filed a removal bug.

Cheers,
Moritz

Bug#938525: spectacle: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

On Fri, Aug 30, 2019 at 07:53:18AM +, Matthias Klose wrote:
> Package: src:spectacle
> Version: 0.25-1
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal

Hi Philippe,
Spectacle seems dead upstream, let's remove it from the archive?

Cheers,
Moritz

Bug#947024: ipxe-qemu: grub2 tests fail after upgrade to 1.0.0+git-20190125.36a4c85-2

[Bastian Blank]

Control: tags -1 pending

Hi Colin

On Thu, Dec 19, 2019 at 05:14:11PM +, Colin Watson wrote:
> OK, I bisected this to this commit:
>   
> https://salsa.debian.org/waldi/ipxe/commit/56212b3037321d709184c5aed48b91b0a1bbd06e
> Happy to try further tests if you have any suggestions.

I feared it would be something like that.  And after re-reading the
change, the cause is found:

qemu loads rom files, which are supposed to include roms for all
environments, currently efi-x86_64 and pcbios.  By accident they now
only contain efi-x86_64.  So booting with OVMF works, but seabios does
not.

Regards,
Bastian

-- 
Dammit Jim, I'm an actor, not a doctor.

Processed: Re: Bug#947024: ipxe-qemu: grub2 tests fail after upgrade to 1.0.0+git-20190125.36a4c85-2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #947024 [ipxe-qemu] ipxe-qemu: grub2 tests fail after upgrade to 
1.0.0+git-20190125.36a4c85-2
Added tag(s) pending.

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

Bug#934119: [Pkg-privacy-maintainers] Bug#934119: torbrowser-launcher: Erroneously manages /etc/apparmor.d/local/torbrowser.* as conffiles

[Roger Shimizu]

Dear Intrigeri,

Thanks for your report, and sorry I just had time to look at this issue.

On Wed, Aug 7, 2019 at 5:21 PM  wrote:
>
> Package: torbrowser-launcher
> Version: 0.3.2-1
> Severity: normal
>
> With this version, /etc/apparmor.d/local/torbrowser.Browser.firefox
> and /etc/apparmor.d/local/torbrowser.Tor.tor are managed as conffiles
> again, while they should not: they're supposed to be created/deleted
> as needed by bits of maintainer scripts generated by dh_apparmor.

So you mean we should revert 9fdce2a576782bb0790416bcf739b31ceb869c6b?

> A problematic consequence is that if I have local tweaks in those
> files (which is their actual intended purpose), I'm asked on upgrade
> to resolve the conflict between my configuration and the empty one
> shipped by the package.
>
> I believe we've had the same bug in the past, that got fixed in
> d0deb2f923edbaf3c2801c46d74b7925c5605593. I'm not sure what
> exact rm_conffile call would be suitable here (depends on which
> upgrade paths we shall support).

d0deb2f923edbaf3c2801c46d74b7925c5605593 was just add entries of
rm_conffile line.
I'm not sure why we should remove rm_conffile here.
Please provide more info if possible. Thank you!

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Processed: Fwd: Processed: py2removal RC severity updates - 2019-12-19 17:37:03.473537+00:00

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #943234 [src:sparkleshare] sparkleshare: Python2 removal in sid/bullseye
Severity set to 'normal' from 'serious'

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

Bug#943234: Fwd: Processed: py2removal RC severity updates - 2019-12-19 17:37:03.473537+00:00

[Andrej Shadura]

Control: severity -1 normal

Sandro, can you please stop this?

Let me quote my previous message, which I understand you missed:

> Python 2 dependency in SparkleShare is not part of the core
> functionality, thus this bug is only severity normal.
>
> I plan to update it but it is not an RC bug.
>
> Thanks for not raising it again. I will fix it when I have time,
> juggling the severity will not me spend more time on it or work faster.

On Thu, 19 Dec 2019 at 18:39, Debian Bug Tracking System
 wrote:
>
> Processing commands for cont...@bugs.debian.org:
>
> > # Part of the effort for the removal of python from bullseye
> > #  * https://wiki.debian.org/Python/2Removal
> > #  * http://sandrotosi.me/debian/py2removal/index.html
> > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> > # for more details on this severity bump
> > # sparkleshare is an application, has low popcon (99 < 300), and has 0 
> > external rdeps or not in testing
> > severity 943234 serious
> Bug #943234 [src:sparkleshare] sparkleshare: Python2 removal in sid/bullseye
> Severity set to 'serious' from 'normal'
> >
> End of message, stopping processing here.
>
> Please contact me if you need assistance.
> --
> 943234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943234
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>


--
Cheers,
  Andrej


-- 
Cheers,
  Andrej

Processed: py2removal RC severity updates - 2019-12-19 17:37:03.473537+00:00

[Debian Bug Tracking System]

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

> # Part of the effort for the removal of python from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # for more details on this severity bump
> # sparkleshare is an application, has low popcon (99 < 300), and has 0 
> external rdeps or not in testing
> severity 943234 serious
Bug #943234 [src:sparkleshare] sparkleshare: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#947024: ipxe-qemu: grub2 tests fail after upgrade to 1.0.0+git-20190125.36a4c85-2

[Colin Watson]

On Thu, Dec 19, 2019 at 04:32:32PM +, Colin Watson wrote:
> On Thu, Dec 19, 2019 at 04:15:55PM +, Colin Watson wrote:
> > With ipxe-qemu 1.0.0+git-20190125.36a4c85-1, it runs for a few seconds
> > then exits 0.  With 1.0.0+git-20190125.36a4c85-2, it hangs apparently
> > forever (grub2's test suite kills it after a minute, but I've left it
> > running for rather longer than that and it doesn't seem to make a
> > difference).  Any hints welcome.
> 
> I rebuilt ipxe-qemu 1.0.0+git-20190125.36a4c85-1 against current
> unstable and it works fine, so I think that rules out changes in ipxe's
> build-dependencies.

OK, I bisected this to this commit:

  
https://salsa.debian.org/waldi/ipxe/commit/56212b3037321d709184c5aed48b91b0a1bbd06e

Happy to try further tests if you have any suggestions.

-- 
Colin Watson   [cjwat...@debian.org]

Processed: severity of 938758 is serious

[Debian Bug Tracking System]

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

> severity 938758 serious
Bug #938758 [src:urlgrabber] urlgrabber: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#937337: marked as done (pugl: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 19 Dec 2019 17:04:14 +
with message-id 
and subject line Bug#937337: fixed in pugl 0~svn32+dfsg0-3
has caused the Debian Bug report #937337,
regarding pugl: 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.)


-- 
937337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pugl
Version: 0~svn32+dfsg0-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:pugl

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: pugl
Source-Version: 0~svn32+dfsg0-3

We believe that the bug you reported is fixed in the latest version of
pugl, 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.
Dimitri John Ledkov  (supplier of updated pugl 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, 19 Dec 2019 16:04:40 +
Source: pugl
Architecture: source
Version: 0~svn32+dfsg0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Dimitri John Ledkov 
Closes: 937337
Changes:
 pugl (0~svn32+dfsg0-3) unstable; urgency=medium
 .
   * QA upload.
   * Switch to python3 waf, and twiddle wscript. Closes: #937337
   * Add libgl-dev build-dep.
Checksums-Sha1:
 e59b4dfa09066c4c93414b23c40532d6442586e6 1923 pugl_0~svn32+dfsg0-3.dsc
 87ca5ed0ce0535eb370d7e068c22dc62582c815e 125108 
pugl_0~svn32+dfsg0-3.debian.tar.xz
 a8cd70ca55acce08e7a1ae53f24bc037f8b9429c 9743 
pugl_0~svn32+dfsg0-3_source.buildinfo
Checksums-Sha256:
 b1886cb0240a707948b71ff4bdb40833de0f9efa00d2b77f637ffb7eb9cd7c0e 1923 
pugl_0~svn32+dfsg0-3.dsc
 851677409df7f9f5dddca5812369cda3feaa8afbad4b141a6ba8f753eae6db67 125108 
pugl_0~svn32+dfsg0-3.debian.tar.xz
 d1b501050af6a1e69ac6ea2281717f28ced57243ebe74efd1ee2f333bc92a6e2 9743 
pugl_0~svn32+dfsg0-3_source.buildinfo

Processed: cloning 938473, severity of -1 is normal ..., reassign -1 to ftp.debian.org

[Debian Bug Tracking System]

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

> clone 938473 -1
Bug #938473 [src:sgmltools-lite] sgmltools-lite: Python2 removal in sid/bullseye
Bug 938473 cloned as bug 947027
937695 was blocked by: 943196 936344 936721 943282 937639 937084 936189 936881 
943098 938195 938020 938372 937696 937627 938574 936111 937174 945710 936159 
936241 938651 937054 937939 936819 945732 936473 937996 937927 937415 945671 
936531 937022 936317 936854 945717 937598 937413 937171 936114 936507 937461 
937019 938654 937051 936332 938272 938622 939491 937377 936165 937418 936310 
937593 943120 936884 943095 936341 936724 936709 937081 938684 938027 938096 
936752 936217 936147 938198 937620 937270 938438 938922 945744 938150 936610 
938070 938810 942915 937549 936632 937677 937296 938322 938509 937182 943057 
938354 937714 937580 936941 942964 936932 937320 938180 936428 937830 937072 
943274 938707 936910 937406 938251 936641 938582 938219 938734 937124 938384 
937550 938841 938222 938672 943049 937970 937740 937837 936425 945624 936872 
936917 938700 938844 937557 937339 938731 938381 942918 938157 938521 938742 
937768 936944 943050 945682 937587 937759 938351 937711 936774 938513 938305 
938498 937260 937728 936447 937888 936706 938036 937883 938099 942921 943035 
938518 936465 945664 937118 938262 937016 937471 937161 937869 937538 937243 
936591 938616 936816 942982 937245 936468 945661 937115 937936 936463 936173 
936459 937474 937164 937885 937636 938564 937267 938362 936440 943033 935208 
938308 849087 937725 942909 942924 943038 938515 936489 943136 937943 937773 
942971 937660 937778 938457 936803 937421 943046 937643 943218 943148 936125 
938608 935450 937005 943143 936862 937826 937897 937648 943213 883173 937960 
938487 937336 938043 937003 936123 943145 938794 937452 938216 937062 937890 
936805 938605 936128 937645 938480 936992 942974 936761 943167 937236 937482 
937667 937945 936718 938892 938450 937295 938177 938682 938467 943281 938057 
937779 945742 943070 938924 938909 945731 937405 938445 936852 937680 937398 
936242 938087 936307 937950 937021 936101 937577 936532 937393 945672 943180 
936809 937052 936426 937687 937462 943254 945734 937408 938448 937570 938443 
945707 937403 936821 937009 937024 938271 938621 943222 938049 936207 939259 
937082 936544 937657 938460 938050 938921 937293 936751 943157 938572 938374 
937181 938744 936631 938499 934870 938831 937889 943195 936485 937250 945684 
938098 936942 936772 938436 938127 938196 937737 937387 937249 937151 937071 
937527 938674 937596 938224 938209 937119 937811 936931 945654 936455 938581 
937539 936900 938252 937814 936934 937993 937074 938671 936179 938382 938584 
937287 937998 936166 945651 938710 938834 943198 936483 937184 938522 938309 
935209 936634 937701 943096 943027 937257 937712 938554 943039 938807 943193 
938095 937847 937730 938364 938562 936294 943067 937233 937548 942954 938315 
938503 937238 938160 938470 938261 937103 943045 937560 937785 937162 937825 
938046 936437 936126 937006 943048 942981 937783 937333 937823 937338 936806 
937788 936190 937105 943043 936430 938313 943060 938505 942951 938361 937769 
938167 937776 937946 937758 938420 937638 942972 943133 936188 938306 943036 
937484 943138 936183 938618 943203 936158 936176 937938 936818 937875 937422 
938792 936169 936813 937064 938661 943262 937454 936994 936153 943208 938613 
937116 937599 936815 937246 938615 936155 943205 936864 937013 937061 937536 
937419 937451 937726 938427 936762 943303 937635 936708 936185 943135 938439 
936691 938516 945665 937079 936464 937241 937159 937851 936939 936595 937500 
937819 937473 938540 938230 936996 936927 937168 937066 938589 938212 937102 
938757 937456 937317 938131 943007 937189 938502 938329 938568 945647 938839 
937210 938100 937140 938827 938511 936627 943034 937232 942928 938559 938337 
943000 938565 937884 937724 937709 938301 945640 935212 937217 938107 943031 
942925 938330 945689 938780 937507 938204 937114 945668 943042 938229 937244 
936920 938666 938237 937534 936377 945663 937822 937475 936418 936866 938750 
936593 937932 936812 942986 937428 936977 943141 936830 938612 937037 937910 
936152 938044 937029 937004 938601 936124 937423 936550 938793 943268 945727 
938877 936765 937610 938366 942978 936227 938379 936714 937771 942973 943240 
937941 936580 936702 938032 942975 937617 936768 938010 936670 937944 936759 
943247 943302 943144 937012 943214 938637 936740 937425 938795 937030 936804 
936829 943265 936339 936789 936557 937644 938041 938279 945720 937001 938604 
937055 936876 937465 937175 936118 945673 938676 938226 936858 937392 936853 
945678 938669 937414 936161 936113 936869 938653 936538 943225 936243 938688 
938390 937085 936345 936728 938746 937447 943091 945743 936888 938407 945748 
936883 936723 938683 938326 937186 936267 936885 937440 938573 938685 938836 
937088 938400 936725 936343 938578 937083 945745 938556 937489 938431 936699 
937402 937156 938442 937076 936855 937058 943223 938655 

Processed: cloning 946881, severity of -1 is normal ..., reassign -1 to ftp.debian.org

[Debian Bug Tracking System]

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

> clone 946881 -1
Bug #946881 [translate-docformat] translate-docformat: Please remove 
translate-docformat from Debian, package of questionable value
Bug 946881 cloned as bug 947026
> severity -1 normal
Bug #947026 [translate-docformat] translate-docformat: Please remove 
translate-docformat from Debian, package of questionable value
Severity set to 'normal' from 'serious'
> retitle -1 RM: RoQA: translate-docformat, buggy, unused, kitchen-sync script
Bug #947026 [translate-docformat] translate-docformat: Please remove 
translate-docformat from Debian, package of questionable value
Changed Bug title to 'RM: RoQA: translate-docformat, buggy, unused, 
kitchen-sync script' from 'translate-docformat: Please remove 
translate-docformat from Debian, package of questionable value'.
> reassign -1 ftp.debian.org
Bug #947026 [translate-docformat] RM: RoQA: translate-docformat, buggy, unused, 
kitchen-sync script
Bug reassigned from package 'translate-docformat' to 'ftp.debian.org'.
No longer marked as found in versions translate-docformat/0.6-5.
Ignoring request to alter fixed versions of bug #947026 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#946422: Fw: pocl and silx

[Jerome Kieffer]

Thanks Fred for the time spent on this. It looks like it is a very deep problem 
!

Concerning the code:
This medfilt code never properly worked on POCL CPU-thread version
while it works as expected on CUDA (POCL+CUDA) or other drivers. 
There is a huge amount of shared memory involved which may be the root of the 
problem (?)

But about the interference I mainly see specfile (the C-library) which is our 
"first" guess inside "silx.io".
This legacy code is far from our current standards ...

Other point, pyopencl.array.zeros_like() is calling the opencl enfillBuffer 
function which caused me also issues 
in (POCL+CUDA). Creating a work-around on the silx side is an option as it has 
been done many times.

I opened a bug on our side:
https://github.com/silx-kit/silx/issues/2848

Cheers

Begin forwarded message:

Date: Thu, 19 Dec 2019 10:08:49 +
From: PICCA Frederic-Emmanuel 
To: "kief...@esrf.fr" 
Subject: pocl and silx


Salut Jerome, on est en train d'essayer de demerder le problème avec pocl.

On a mis les info la

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946422


est-ce que cela te dis quelque choses.

C'est vrai que si l'on import silxs.io avant silxs.opencl  dans le petit 
snipset de test, ca change fondamentalement la done...

Amicalement

Fred

-- 
Jérôme Kieffer
tel +33 476 882 445

Bug#947024: ipxe-qemu: grub2 tests fail after upgrade to 1.0.0+git-20190125.36a4c85-2

[Colin Watson]

On Thu, Dec 19, 2019 at 04:15:55PM +, Colin Watson wrote:
> With ipxe-qemu 1.0.0+git-20190125.36a4c85-1, it runs for a few seconds
> then exits 0.  With 1.0.0+git-20190125.36a4c85-2, it hangs apparently
> forever (grub2's test suite kills it after a minute, but I've left it
> running for rather longer than that and it doesn't seem to make a
> difference).  Any hints welcome.

I rebuilt ipxe-qemu 1.0.0+git-20190125.36a4c85-1 against current
unstable and it works fine, so I think that rules out changes in ipxe's
build-dependencies.

-- 
Colin Watson   [cjwat...@debian.org]

Bug#946422: silx: autopkgtest regression: pocl error

[Andreas Beckmann]

On 19/12/2019 14.33, Graham Inggs wrote:
> On Thu, 19 Dec 2019 at 15:17, Andreas Beckmann  wrote:
>> I'm suspecting openmpi (that gets loaded by the io import) somehow messes up 
>> some state,
>> causing the lt_*() failures.
> 
> I wonder if this is related to #946986 ?

Downgrading to python3-h5py from buster makes the problem go away. But
it also removes mpi from the loop.

Selecting previously unselected package libhdf5-103:amd64.
(Reading database ... 32183 files and directories currently installed.)
Preparing to unpack .../libhdf5-103_1.10.4+repack-10_amd64.deb ...
Unpacking libhdf5-103:amd64 (1.10.4+repack-10) ...
(Reading database ... 32197 files and directories currently installed.)
Removing python3-mpi4py (3.0.3-1) ...
Removing mpi-default-bin (1.13) ...
Removing openmpi-bin (4.0.2-4+b1) ...
Removing libhdf5-openmpi-103:amd64 (1.10.4+repack-10) ...
Removing libopenmpi3:amd64 (4.0.2-4+b1) ...
Removing libpmix2:amd64 (3.1.4-1+b1) ...
Removing libevent-2.1-7:amd64 (2.1.11-stable-1) ...
Removing libevent-pthreads-2.1-7:amd64 (2.1.11-stable-1) ...
Removing libevent-core-2.1-7:amd64 (2.1.11-stable-1) ...
Removing libfabric1 (1.6.2-3+b1) ...
Removing librdmacm1:amd64 (26.0-2) ...
Removing libibverbs1:amd64 (26.0-2) ...
Removing libnl-route-3-200:amd64 (3.4.0-1+b1) ...
Removing libnl-3-200:amd64 (3.4.0-1+b1) ...
Removing libpsm2-2 (11.2.86-1) ...
Removing libnuma1:amd64 (2.0.12-1+b1) ...
Removing libpsm-infinipath1 (3.3+20.604758e7-6+b1) ...
update-alternatives: warning: alternative
/usr/lib/libpsm1/libpsm_infinipath.so.1.16 (part of link group
libpsm_infinipath.so.1) doesn't exist; removing from list of alternatives
update-alternatives: warning: /etc/alternatives/libpsm_infinipath.so.1
is dangling; it will be updated with best choice
Removing openmpi-common (4.0.2-4) ...
Setting up libhdf5-103:amd64 (1.10.4+repack-10) ...
Setting up python3-h5py (2.8.0-3) ...
Processing triggers for libc-bin (2.29-6) ...

I can reproduce the original problem if I take some OpenCL hello world
program (e.g. https://gist.github.com/ddemidov/2925717 with s/GPU/CPU/)
and insert MPI_Init(,  - no python needed

Andreas

Processed: ipxe-qemu: grub2 tests fail after upgrade to 1.0.0+git-20190125.36a4c85-2

[Debian Bug Tracking System]

Processing control commands:

> affects -1 grub2
Bug #947024 [ipxe-qemu] ipxe-qemu: grub2 tests fail after upgrade to 
1.0.0+git-20190125.36a4c85-2
Added indication that 947024 affects grub2

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

Bug#944426: [Pkg-pascal-devel] Bug#944426: Bug#944426: Still not able to update

[Abou Al Montacir]

Hi Johann

As far as I can see everything is OK.
You were updating from 2.0.6-2 to 2.0.6-3 and this was tested here as you can
see below.

What I can assume is that even your 2.0.6-2 installation was broken and thus the
diversion was not done.
However this does not explain that your diversions file is OK.

Unfortunately, you did force the installation, but if you can reproduce the
issue (an other machine, or reinstall -2 then -3) then I'll be happy to
reproduce and fix.

# aptitude upgrade Resolving dependencies...The following
packages will be upgraded:  lazarus lazarus-2.0 lazarus-doc-2.0 lazarus-ide
lazarus-ide-2.0 lazarus-ide-gtk2-2.0 lazarus-src-2.0 lcl-2.0   lcl-gtk2-2.0 lcl-
nogui-2.0 lcl-units-2.0 lcl-utils-2.0 12 packages upgraded, 0 newly installed, 0
to remove and 2 not upgraded.Need to get 0 B/83.8 MB of archives. After
unpacking 115 kB will be freed.Do you want to continue? [Y/n/?] ...Reading
changelogs... Donegelogs... 7%Preconfiguring packages ...(Reading database ...
545578 files and directories currently installed.)Preparing to unpack .../00-
lazarus-2.0_2.0.6+dfsg-3_all.deb ...Unpacking lazarus-2.0 (2.0.6+dfsg-3) over
(2.0.6+dfsg-2) ...Preparing to unpack .../01-lazarus-ide-2.0_2.0.6+dfsg-
3_amd64.deb ...Unpacking lazarus-ide-2.0 (2.0.6+dfsg-3) over (2.0.6+dfsg-2)
...Preparing to unpack .../02-lazarus-ide-gtk2-2.0_2.0.6+dfsg-3_amd64.deb
...Unpacking lazarus-ide-gtk2-2.0 (2.0.6+dfsg-3) over (2.0.6+dfsg-2)
...Preparing to unpack .../03-lazarus-ide_2.0.6+dfsg-3_all.deb ...Unpacking
lazarus-ide (2.0.6+dfsg-3) over (2.0.6+dfsg-2) ...Preparing to unpack .../04-
lazarus-src-2.0_2.0.6+dfsg-3_all.deb ...Unpacking lazarus-src-2.0 
(2.0.6+dfsg-3) 
over (2.0.6+dfsg-2) ...Preparing to unpack .../05-lcl-nogui-2.0_2.0.6+dfsg-
3_amd64.deb ...Unpacking lcl-nogui-2.0 (2.0.6+dfsg-3) over (2.0.6+dfsg-2)
...Preparing to unpack .../06-lcl-units-2.0_2.0.6+dfsg-3_amd64.deb ...Unpacking
lcl-units-2.0 (2.0.6+dfsg-3) over (2.0.6+dfsg-2) ...Preparing to unpack .../07-
lcl-gtk2-2.0_2.0.6+dfsg-3_amd64.deb ...Unpacking lcl-gtk2-2.0 (2.0.6+dfsg-3)
over (2.0.6+dfsg-2) ...Preparing to unpack .../08-lcl-utils-2.0_2.0.6+dfsg-
3_amd64.deb ...Unpacking lcl-utils-2.0 (2.0.6+dfsg-3) over (2.0.6+dfsg-2)
...Preparing to unpack .../09-lcl-2.0_2.0.6+dfsg-3_amd64.deb ...Unpacking lcl-
2.0:amd64 (2.0.6+dfsg-3) over (2.0.6+dfsg-2) ...Preparing to unpack .../10-
lazarus_2.0.6+dfsg-3_all.deb ...Unpacking lazarus (2.0.6+dfsg-3) over
(2.0.6+dfsg-2) ...Preparing to unpack .../11-lazarus-doc-2.0_2.0.6+dfsg-
3_all.deb ...Unpacking lazarus-doc-2.0 (2.0.6+dfsg-3) over (2.0.6+dfsg-2)
...Setting up lazarus-doc-2.0 (2.0.6+dfsg-3) ...Setting up lazarus-src-2.0
(2.0.6+dfsg-3) ...Setting up lazarus-ide-2.0 (2.0.6+dfsg-3) ...update-
alternatives: using /usr/lib/lazarus/2.0.6/startlazarus to provide
/usr/bin/lazarus-ide (lazarus-ide) in auto modeSetting up lcl-utils-2.0
(2.0.6+dfsg-3) ...update-alternatives: using /usr/lib/lazarus/2.0.6 to provide
/usr/lib/lazarus/default (lazarus) in auto modeSetting up lcl-nogui-2.0
(2.0.6+dfsg-3) ...Setting up lazarus-ide-gtk2-2.0 (2.0.6+dfsg-3) ...update-
alternatives: using /usr/lib/lazarus/2.0.6/lazarus-gtk2 to provide
/usr/lib/lazarus/2.0.6/lazarus (lazarus-2.0.6) in auto modeSetting up lazarus-
ide (2.0.6+dfsg-3) ...Setting up lcl-gtk2-2.0 (2.0.6+dfsg-3) ...Setting up lcl-
units-2.0 (2.0.6+dfsg-3) ...Setting up lcl-2.0:amd64 (2.0.6+dfsg-3) ...Setting
up lazarus-2.0 (2.0.6+dfsg-3) ...Setting up lazarus (2.0.6+dfsg-3) ...Processing
triggers for mime-support (3.62) ...Processing triggers for hicolor-icon-theme
(0.17-2) ...Processing triggers for gnome-menus (3.31.4-3) ...Processing
triggers for man-db (2.8.5-2) ...Processing triggers for desktop-file-utils
(0.23-4) ... Current status: 2 (-12)
upgradable.-- 
Cheers,
Abou Al Montacir


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

Processed: severity of 943234 is normal

[Debian Bug Tracking System]

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

> severity 943234 normal
Bug #943234 [src:sparkleshare] sparkleshare: Python2 removal in sid/bullseye
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: py2removal RC severity updates - 2019-12-19 15:36:44.839837+00:00

[Debian Bug Tracking System]

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

> # Part of the effort for the removal of python from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # for more details on this severity bump
> # sparkleshare is an application, has low popcon (99 < 300), and has 0 
> external rdeps or not in testing
> severity 943234 serious
Bug #943234 [src:sparkleshare] sparkleshare: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#940491: python3-meep-Script blocks apt-get installation operations in upgraded experimental debian

[Claus Fütterer]

Package: python3-meep
Version: 1.12.0-2
Followup-For: Bug #940491

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
installation of meep and python3-meep

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I installed the named packages with synaptic and later with apt
   * What was the outcome of this action?

synaptic:
E: python3-meep: »installiertes python3-meep-Skript des Paketes post-
installation«-Unterprozess gab den Fehlerwert 1 zurück
English: installed python3-meep-script of package post-installation sup-process
returned error 1

now I cannot install or remove any software but get instead this error message

Further:

root@kugel:~# apt-get upgrade
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr
benötigt:
  freecad-runtime libfuse3-3 python3-pyside2.qtsvg python3-pyside2.qtuitools
python3-pyside2.qtxml python3-pyside2uic
Verwenden Sie »apt autoremove«, um sie zu entfernen.
Die folgenden Pakete sind zurückgehalten worden: (English: The following
packages are hold back)
  freecad gnome-dictionary libequinox-osgi-java libllvm9 libllvm9:i386 phonon-
backend-gstreamer-common python-sip quota sshfs
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 9 nicht aktualisiert.
1 nicht vollständig installiert oder entfernt.
Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n]
python3-meep (1.12.0-2) wird eingerichtet ...
dpkg-query: Paket »python-meep« ist nicht installiert  (English: ...is not
installed)
Verwenden Sie dpkg --contents (= dpkg-deb --contents) zum Auflisten von
Archivinhalten.
Traceback (most recent call last):
  File "/usr/bin/pycompile", line 289, in 
main()
  File "/usr/bin/pycompile", line 262, in main
options.force, options.optimize, e_patterns)
  File "/usr/bin/pycompile", line 154, in compile
for fn, versions_to_compile in filter_files(files, e_patterns, versions):
  File "/usr/bin/pycompile", line 109, in filter_files
for fn in files:
  File "/usr/share/python/debpython/files.py", line 77, in filter_out_ext
for fn in files:
  File "/usr/share/python/debpython/namespace.py", line 77, in
add_namespace_files
for fn in files:
  File "/usr/share/python/debpython/files.py", line 69, in filter_public
for fn in files:
  File "/usr/share/python/debpython/files.py", line 53, in from_package
raise Exception("cannot get content of %s" % package_name)
Exception: cannot get content of python-meep
dpkg: Fehler beim Bearbeiten des Paketes python3-meep (--configure):
 »installiertes python3-meep-Skript des Paketes post-installation«-Unterprozess
gab den Fehlerwert 1 zurück
Trigger für libc-bin (2.29-6) werden verarbeitet ...
Fehler traten auf beim Bearbeiten von:
 python3-meep
E: Sub-process /usr/bin/dpkg returned an error code (1)


   * What outcome did you expect instead?
no errors when installing or removing

*** End of the template - remove these template lines ***



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

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

Versions of packages python3-meep depends on:
ii  libatlas3-base [liblapack.so.3]3.10.3-9
ii  libblas3 [libblas.so.3]3.9.0-1
ii  libc6  2.29-6
ii  libctl74.4.0-3
ii  libfftw3-double3   3.3.8-2
ii  libgcc11:9.2.1-21
ii  liblapack3 [liblapack.so.3]3.9.0-1
pn  libmeep17  
ii  libopenblas0-pthread [liblapack.so.3]  0.3.7+ds-7
ii  libstdc++6 9.2.1-21
ii  python33.7.5-3
ii  python3-numpy  1:1.17.4-4

python3-meep recommends no packages.

python3-meep suggests no packages.

-- no debconf information

Processed: severity of 936700 is normal

[Debian Bug Tracking System]

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

> severity 936700 normal
Bug #936700 [src:hgsubversion] hgsubversion: Python2 removal in sid/bullseye
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: severity of 937012 is important, severity of 937011 is important

[Debian Bug Tracking System]

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

> severity 937012 important
Bug #937012 [src:mercurial-keyring] mercurial-keyring: Python2 removal in 
sid/bullseye
Severity set to 'important' from 'serious'
> severity 937011 important
Bug #937011 [src:mercurial-extension-utils] mercurial-extension-utils: Python2 
removal in sid/bullseye
Severity set to 'important' from 'normal'
> thanks
Stopping processing here.

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

Bug#946609: marked as done (resolvconf: broken init script: "/run/resolvconf is neither a directory nor a symbolic link")

[Debian Bug Tracking System]

Your message dated Thu, 19 Dec 2019 14:39:22 +
with message-id 
and subject line Bug#946609: fixed in resolvconf 1.81
has caused the Debian Bug report #946609,
regarding resolvconf: broken init script: "/run/resolvconf is neither a 
directory nor a symbolic link"
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.)


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

Package: resolvconf
Version: 1.80
Tags: patch

The create_runtime_directories() function in the resolvconf init script 
worked under assumption that $RUN_DIR is a symlink (either broken or 
pointing to a directory). Now that $RUN_DIR is just /run/resolvconf, 
resolvconf no longer starts on boot:


  Setting up resolvconf...failed (/run/resolvconf is neither a directory nor a 
symbolic link).


-- System Information:
Architecture: i386

Versions of packages resolvconf depends on:
ii  lsb-base 11.1.0
ii  debconf  1.5.73

--
Jakub Wilk
--- /etc/init.d/resolvconf	2019-12-10 16:45:20.0 +0100
+++ /etc/init.d/resolvconf	2019-12-11 20:30:41.564651091 +0100
@@ -54,11 +54,8 @@
 {
 	umask 022
 	if [ ! -d "$RUN_DIR" ] ; then
-		[ -L "$RUN_DIR" ] || log_action_end_msg_and_exit 1 "$RUN_DIR is neither a directory nor a symbolic link"
-		# It's a symlink. Its target is not a dir.
-		{ RUN_CANONICALDIR="$(readlink -f "$RUN_DIR")" && [ "$RUN_CANONICALDIR" ] ; } || log_action_end_msg_and_exit 1 "Canonical path of the run directory could not be determined"
 		# Create directory at the target
-		mkdir "$RUN_CANONICALDIR" || log_action_end_msg_and_exit 1 "Error creating directory $RUN_CANONICALDIR"
+		mkdir "$RUN_DIR" || log_action_end_msg_and_exit 1 "Error creating directory $RUN_DIR"
 	fi
 	# The resolvconf run directory now exists.
 	if [ ! -d "${RUN_DIR}/interface" ] ; then
--- End Message ---
--- Begin Message ---
Source: resolvconf
Source-Version: 1.81

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated resolvconf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 19 Dec 2019 15:19:16 +0100
Source: resolvconf
Architecture: source
Version: 1.81
Distribution: unstable
Urgency: medium
Maintainer: resolvconf team 
Changed-By: Andrej Shadura 
Closes: 850783 946609
Changes:
 resolvconf (1.81) unstable; urgency=medium
 .
   [ Russell Coker ]
   * Set correct SE Linux context on created directories and files
 (Closes: #850783).
 .
   [ Jakub Wilk ]
   * Drop symlink resolving logic from the init script (Closes: #946609).
Checksums-Sha1:
 7765917b0be729dfaa4d867b3b480e8cff9bb735 1483 resolvconf_1.81.dsc
 a05a36af2f8cba3d00339bc02ea52ccd5e4b687d 72900 resolvconf_1.81.tar.xz
Checksums-Sha256:
 7e2bb5f62686b94715657fd6e3f87bfde6a4a5afdb3706dba2e61692fc0246ce 1483 
resolvconf_1.81.dsc
 68c0700befb473355d353ce5ea20d44b62e0a7b01a0ac5e214e33ea692934d3e 72900 
resolvconf_1.81.tar.xz
Files:
 20e58ff37fcddfdae9564f7bf5318c07 1483 net optional resolvconf_1.81.dsc
 016294998dafc3b28b1c8c418c2040c5 72900 net optional resolvconf_1.81.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl37hw0ACgkQXkCM2RzY
OdL3HQf/cph4Uq6yIi83+uGycy1HXQs8eNUd0XkMBEx/KUp3pyyrQWvhEnV77CiK
MZ7Rt3grB/AVxICRJmX5Zeb/uqiozpajsSz4zmsb1EqPnR+JEy9f/cu/pqisA7mj
D7pEkMzx1lupbz2PO1fvGVM5FBOQ/D9p/w1D6V3MFrofJyRmKuLPqHjR0+V+Frbf
7hbhrweHB1CEb13gi0ol9UE23xVVmtsCm3m73G5a7AXN6m8b01no7HPGM2Q92ujM
cOAA1n9DEUNZbtt0keWTDhdFz+EM7fGoj9RhjQnWci2Aguo2/jzyyXXFNgUU3IF1
S9K+zIk4qMNMaa6JbxrSbgYRUN8UuQ==
=7sOC
-END PGP SIGNATURE End Message ---

Bug#945134: marked as done (pep8 fails the python2 autopkg tests, calling python instead of python2)

[Debian Bug Tracking System]

Your message dated Thu, 19 Dec 2019 14:37:52 +
with message-id 
and subject line Bug#945134: fixed in pep8 1.7.1-7
has caused the Debian Bug report #945134,
regarding pep8 fails the python2 autopkg tests, calling python instead of 
python2
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.)


-- 
945134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pep8
Version: 1.7.1-6
Severity: serious
Tags: sid bullseye

pep8 fails the two python2 autopkg tests, calling python instead of python2.
Currently blocking the migration of python-defaults to testing.
--- End Message ---
--- Begin Message ---
Source: pep8
Source-Version: 1.7.1-7

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 19 Dec 2019 15:17:11 +0100
Source: pep8
Architecture: source
Version: 1.7.1-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andrej Shadura 
Closes: 945134
Changes:
 pep8 (1.7.1-7) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Name.
   * Fix day-of-week for changelog entries 1.4.6-1.1, 0.5.0-1.
 .
   [ Andrej Shadura ]
   * Call python2 in autopkgtest, not python (Closes: #945134).
Checksums-Sha1:
 6793361387b7ef9cfe7f75961694fe3d3f851474 1914 pep8_1.7.1-7.dsc
 98c4c1bf19d430449e30a51b177f07e75f8cd3c7 5992 pep8_1.7.1-7.debian.tar.xz
Checksums-Sha256:
 8dd736a8446f194376c9055bebe73e85b6edacd7b88955a81f2c142961890786 1914 
pep8_1.7.1-7.dsc
 05be67f41c7460c2e32dfc8689a3d2eaa619b24170f4f93bfe1422f48533ee21 5992 
pep8_1.7.1-7.debian.tar.xz
Files:
 b29a5ce984e928700d1bea490e3bb915 1914 python optional pep8_1.7.1-7.dsc
 6f0a66db9dc7e9ebbab8cf4088fa3dbe 5992 python optional 
pep8_1.7.1-7.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl37hpkACgkQXkCM2RzY
OdI+6Qf/fel+RHbohoODeyu1heKKDOwcvs++NLyim72kA59IE/YRC5nFdZ7SXV+M
hzImR5aaPGWTW+qd/y0xRNvTioUR/fjyA25QqR0yHpep47Hv9F19HPcycdt7vlSr
LBVv/6FLJbf8jArNQ5vlk6jeN6WkxTNh6JSPLwJT+gVeg2IliAEpfsxM625s9a5Z
CUw8QCIEsIlHK3xX7rtJRPdi80EbX+Tcl5zQYPwZnsYF41B1JkHtITqwP2RA6MZH
iQAfwzZtojo42GEgeFduVPAbLZkX1JUTPEoxL2qpiEC1D3TmCs4g8TNKreq9jycw
cPfgTZLBEwUdnC/r2fIaN6fnz50Lxw==
=H4+y
-END PGP SIGNATURE End Message ---

Processed: Bug#945134 marked as pending in pep8

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #945134 [src:pep8] pep8 fails the python2 autopkg tests, calling python 
instead of python2
Added tag(s) pending.

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

Bug#945134: marked as pending in pep8

[Andrej Shadura]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/pep8/commit/3e23cf1c066489a9a3712cdb0934791a585684fa


Call python2 in autopkgtest, not python

Closes: #945134


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/945134

Bug#936450: marked as done (duecredit: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 19 Dec 2019 13:49:10 +
with message-id 
and subject line Bug#936450: fixed in duecredit 0.7.0-3
has caused the Debian Bug report #936450,
regarding duecredit: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:duecredit

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: duecredit
Source-Version: 0.7.0-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 18 Dec 2019 22:21:04 -0500
Source: duecredit
Architecture: source
Version: 0.7.0-3
Distribution: unstable
Urgency: medium
Maintainer: Yaroslav Halchenko 
Changed-By: Yaroslav Halchenko 
Closes: 936450
Changes:
 duecredit (0.7.0-3) unstable; urgency=medium
 .
   * Completely remove mentioining of python2 in debian/rules
 (Closes: #936450)
Checksums-Sha1:
 2e9dd7a5a39fcfe3bff0328392f13fce608a6db3 1890 duecredit_0.7.0-3.dsc
 c8623610a946a546570c223a532d47b528116d2f 3820 duecredit_0.7.0-3.debian.tar.xz
 8022751a932041c01f9b0cb392c3e0465ff0 6597 
duecredit_0.7.0-3_source.buildinfo
Checksums-Sha256:
 baadf6cc9a942c013a1dd85951eb787acb8aaebe54ee7f20b01474796872234a 1890 
duecredit_0.7.0-3.dsc
 6f279ec706a68c20d090c57c95adc3bad88bacb0c52e508624410edf7e63acce 3820 
duecredit_0.7.0-3.debian.tar.xz
 60a597534b0997b2ccf26745c636bfc4716c6805edb930a6ebdebd0af5debd2d 6597 
duecredit_0.7.0-3_source.buildinfo
Files:
 2c6eabd0346da0a238528bbaf65de4b6 1890 

Bug#946422: silx: autopkgtest regression: pocl error

[Graham Inggs]

On Thu, 19 Dec 2019 at 15:17, Andreas Beckmann  wrote:
> I'm suspecting openmpi (that gets loaded by the io import) somehow messes up 
> some state,
> causing the lt_*() failures.

I wonder if this is related to #946986 ?

Processed: Re: Bug#946984: yade: Ships python3.8 scripts, without any python3 or python3.8 deps

[Debian Bug Tracking System]

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

> tag 946984 pending
Bug #946984 [yade] yade: Ships python3.8 scripts, without any python3 or 
python3.8 deps
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#946984: yade: Ships python3.8 scripts, without any python3 or python3.8 deps

[Dimitri John Ledkov]

tag 946984 pending
thanks

On Thu, 19 Dec 2019 07:33:52 +0100 Anton Gladky  wrote:
> Hi,
>
> it is already done and will be uploaded tonight.

Great! Thanks.

> The problem is that it should go through NEW-queue.
>

Indeed it will must do that =/ I guess we can live without yade in
testing for a little while

Bug#946422: silx: autopkgtest regression: pocl error

[Andreas Beckmann]

On 19/12/2019 11.59, PICCA Frederic-Emmanuel wrote:
> I found that commenting this line 
> 
> # self.d_array_5 = pyopencl.array.zeros_like(self.d_array_img) - 5
> 
> remove the pocl issue.

I think that's a red herring. Without that line I get python errors because 
d_array_5 is missing.

That's the backtrace I get in gdb for the original failure:

(gdb) bt
#0  0x77e41081 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x77e2c535 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x7fffe67c46d1 in pocl_check_kernel_dlhandle_cache 
(cmd=cmd@entry=0x13e1bb0, initial_refcount=initial_refcount@entry=1) at 
./lib/CL/devices/common.c:1097
#3  0x7fffe67ca327 in pocl_pthread_prepare_kernel (cmd=0x13e1bb0, 
data=0x1335df0) at ./lib/CL/devices/pthread/pthread_scheduler.c:413
#4  pocl_pthread_exec_command (td=0x133cb80, cmd=0x13e1bb0) at 
./lib/CL/devices/pthread/pthread_scheduler.c:450
#5  pocl_pthread_driver_thread (p=) at 
./lib/CL/devices/pthread/pthread_scheduler.c:496
#6  0x77deefb7 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#7  0x77f012df in clone () from /lib/x86_64-linux-gnu/libc.so.6

we are failing in pocl_check_kernel_dlhandle_cache() here:

if (ci->dlhandle == NULL || ci->wg == NULL || dl_error != NULL)
  { 
POCL_ABORT (
"pocl error: lt_dlopen(\"%s\") or lt_dlsym() failed with '%s'.\n"
"note: missing symbols in the kernel binary might be"
" reported as 'file not found' errors.\n",
module_fn, dl_error);
  }

(gdb) print *ci
$11 = {hash = "p\374|\271.\364b0\217\036\361?\271\327~\372", local_wgs = {32, 
1, 1}, wg = 0x0, dlhandle = 0x7fff890010f0, next = 0x0, prev = 0x0, ref_count = 
1}
(gdb) print dl_error
$15 = 0x753433e0 "can't close resident module"

I'm suspecting openmpi (that gets loaded by the io import) somehow messes up 
some state,
causing the lt_*() failures.

Andreas

Processed: tagging 946894

[Debian Bug Tracking System]

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

> tags 946894 + sid bullseye
Bug #946894 {Done: Federico Ceratto } [runsnakerun] 
runsnake cannot open python3 profiling information
Ignoring request to alter tags of bug #946894 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#945393: marked as done (skimage: autopkgtest failures)

[Debian Bug Tracking System]

Your message dated Thu, 19 Dec 2019 12:35:55 +
with message-id 
and subject line Bug#945393: fixed in skimage 0.16.2-1
has caused the Debian Bug report #945393,
regarding skimage: autopkgtest failures
to be marked as done.

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

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


-- 
945393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: skimage
Version: 0.14.2-3
Severity: serious
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

The autopkgtest for your package are failing, which prevent the testing 
migration of networkx.

The logging shows many exceptions like this:

 AttributeError: 'RAG' object has no attribute 'node'

See:

 https://ci.debian.net/data/autopkgtest/testing/amd64/s/skimage/3494472/log.gz

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: skimage
Source-Version: 0.16.2-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 18 Dec 2019 15:41:34 +0100
Source: skimage
Architecture: source
Version: 0.16.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ole Streicher 
Closes: 945389 945393
Changes:
 skimage (0.16.2-1) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Team upload.
   * New upstream version. Closes: #945389, #945393
   * Standards-Version: 4.4.1
   * More default d/rules
   * Drop Stefan van der Walt from Uploaders since he confirmed not to
 do packaging work any more (thanks for your previous work Stefan)
 .
   [ Ole Streicher ]
   * Fix manual adjustment for build time tests
   * Add imageio and sphinx-copybutton build dependencies
   * Disable failures on warnings
   * Wrap and sort -a
   * Disable test that requires local server
   * Rediff patches and adjust patch names to the Subject line
   * Disable -j option use for sphinx
   * Update search.html to new way of generating Sphinx search box
Checksums-Sha1:
 a1b50c2a4b7b5ac024f3c264ce3d297484205b8d 2690 skimage_0.16.2-1.dsc
 f601313df228832ebc8818b464492ae54df8a537 22662669 skimage_0.16.2.orig.tar.gz
 fffdd06c7b7a70192a24cd34efa289d41c9f8c14 23564 skimage_0.16.2-1.debian.tar.xz
Checksums-Sha256:
 018780c767b22c2316dd9c666e6025faea29e913f7138c516b605c12806453eb 2690 
skimage_0.16.2-1.dsc
 6ca8de67321322298aa1a700715dca0b7a3ab59d710d1bd8d1dd82b477e607e8 22662669 
skimage_0.16.2.orig.tar.gz
 7e9c1e8188159595ef64be20ae1e99b7f6242da20c069903c7f94ddb88e20a1b 23564 
skimage_0.16.2-1.debian.tar.xz
Files:
 1323e94c34aea30431980caf0f2e102e 2690 python optional skimage_0.16.2-1.dsc
 5334acddcafff70832781b51c78fef1f 22662669 python optional 
skimage_0.16.2.orig.tar.gz
 12ac5d2de69e8c89a91243ea6b9ddec3 23564 python optional 
skimage_0.16.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAl37aKsACgkQcRWv0HcQ
3PfZMA/8CokGYg2uYvLV9hc/+n7vjTK7xzfk5SLVmmvmlz/ehTUo8ByY01xpJpD8
1oYlKNGK1EY92ex/peE8JRIZOeFBjlBRQTYe/ojGMHiLBDw0G1pSsyoN3ewrKBD9
4wf+1ve2p577NjpMiMJV37bFk0/ArZXDw61DCq5XyToYJwDQq2fdxc+5FO60+9fN
BnnMVzZZXtG0kC8tHLopASFU7Czj6s/IbK3r3l7ocIhiHHCmd1o0hzgQy8ElfKqe
cSfGOMvpmUL2T7H26+sR9Wr2OyK6DwtATTgGBWCQ6AoxYJwyjoC0dQ1f+BxDd0f0
JhhrCpNnPPg6lQiiosGJMyTIJkQpCjXAldQDwL8/dqTPgxDMCbTuVoQGCoKD2V/8
rTBVQ4hfCf00bwy07mbkaP/zN5jSvFgPuapGyKLe+gUZsZNNOXKQYjvDihD5xOc6
Q+1AlmgpQED3dUWasG3x897fIH9ia5FrAk68yeCPI7rR66ma4bZSGx2iFjxCafj+
ZiOvRaO+ZkrfAxou41S5VgBnxPHnTJQ2hrNRxDxuCPv5Pxl3r3/E1vokJ9AuZYOa
AMV9YvYXLWAs4so38zOQpnHy4C2u74xQYqdiAyZbcWkzXZa3WlPo7zl5XjO1PrXC
Uf99e2YR1nId3J4+Ijal5Vz0hNSCzz6WyENwOrDu1iVcOYsN0Ag=
=/PG/
-END PGP SIGNATURE End Message ---

Bug#945389: marked as done (skimage: FTBFS with python3.8 (test failures))

[Debian Bug Tracking System]

Your message dated Thu, 19 Dec 2019 12:35:55 +
with message-id 
and subject line Bug#945389: fixed in skimage 0.16.2-1
has caused the Debian Bug report #945389,
regarding skimage: FTBFS with python3.8 (test failures)
to be marked as done.

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

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


-- 
945389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: skimage
Version: 0.14.2-3
Severity: serious
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

Your package FTBFS as part of the python3.8 transition, see:

 
https://buildd.debian.org/status/fetch.php?pkg=skimage=amd64=0.14.2-3%2Bb1=1574494998=0
 https://buildd.debian.org/status/package.php?p=skimage

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: skimage
Source-Version: 0.16.2-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 18 Dec 2019 15:41:34 +0100
Source: skimage
Architecture: source
Version: 0.16.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ole Streicher 
Closes: 945389 945393
Changes:
 skimage (0.16.2-1) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Team upload.
   * New upstream version. Closes: #945389, #945393
   * Standards-Version: 4.4.1
   * More default d/rules
   * Drop Stefan van der Walt from Uploaders since he confirmed not to
 do packaging work any more (thanks for your previous work Stefan)
 .
   [ Ole Streicher ]
   * Fix manual adjustment for build time tests
   * Add imageio and sphinx-copybutton build dependencies
   * Disable failures on warnings
   * Wrap and sort -a
   * Disable test that requires local server
   * Rediff patches and adjust patch names to the Subject line
   * Disable -j option use for sphinx
   * Update search.html to new way of generating Sphinx search box
Checksums-Sha1:
 a1b50c2a4b7b5ac024f3c264ce3d297484205b8d 2690 skimage_0.16.2-1.dsc
 f601313df228832ebc8818b464492ae54df8a537 22662669 skimage_0.16.2.orig.tar.gz
 fffdd06c7b7a70192a24cd34efa289d41c9f8c14 23564 skimage_0.16.2-1.debian.tar.xz
Checksums-Sha256:
 018780c767b22c2316dd9c666e6025faea29e913f7138c516b605c12806453eb 2690 
skimage_0.16.2-1.dsc
 6ca8de67321322298aa1a700715dca0b7a3ab59d710d1bd8d1dd82b477e607e8 22662669 
skimage_0.16.2.orig.tar.gz
 7e9c1e8188159595ef64be20ae1e99b7f6242da20c069903c7f94ddb88e20a1b 23564 
skimage_0.16.2-1.debian.tar.xz
Files:
 1323e94c34aea30431980caf0f2e102e 2690 python optional skimage_0.16.2-1.dsc
 5334acddcafff70832781b51c78fef1f 22662669 python optional 
skimage_0.16.2.orig.tar.gz
 12ac5d2de69e8c89a91243ea6b9ddec3 23564 python optional 
skimage_0.16.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAl37aKsACgkQcRWv0HcQ
3PfZMA/8CokGYg2uYvLV9hc/+n7vjTK7xzfk5SLVmmvmlz/ehTUo8ByY01xpJpD8
1oYlKNGK1EY92ex/peE8JRIZOeFBjlBRQTYe/ojGMHiLBDw0G1pSsyoN3ewrKBD9
4wf+1ve2p577NjpMiMJV37bFk0/ArZXDw61DCq5XyToYJwDQq2fdxc+5FO60+9fN
BnnMVzZZXtG0kC8tHLopASFU7Czj6s/IbK3r3l7ocIhiHHCmd1o0hzgQy8ElfKqe
cSfGOMvpmUL2T7H26+sR9Wr2OyK6DwtATTgGBWCQ6AoxYJwyjoC0dQ1f+BxDd0f0
JhhrCpNnPPg6lQiiosGJMyTIJkQpCjXAldQDwL8/dqTPgxDMCbTuVoQGCoKD2V/8
rTBVQ4hfCf00bwy07mbkaP/zN5jSvFgPuapGyKLe+gUZsZNNOXKQYjvDihD5xOc6
Q+1AlmgpQED3dUWasG3x897fIH9ia5FrAk68yeCPI7rR66ma4bZSGx2iFjxCafj+
ZiOvRaO+ZkrfAxou41S5VgBnxPHnTJQ2hrNRxDxuCPv5Pxl3r3/E1vokJ9AuZYOa
AMV9YvYXLWAs4so38zOQpnHy4C2u74xQYqdiAyZbcWkzXZa3WlPo7zl5XjO1PrXC
Uf99e2YR1nId3J4+Ijal5Vz0hNSCzz6WyENwOrDu1iVcOYsN0Ag=
=/PG/
-END PGP SIGNATURE End Message ---

Bug#947006: libvirt: autopkgtest always fails and now started to time out regularly

[Paul Gevers]

Source: libvirt
Version: 5.6.0-3
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: timeout flaky

Dear maintainers,

Your package has an autopkgtest, great. However, I noticed that it
always fails, which nowadays is considered RC. However, on top of that,
with version 5.6.0-3 your package started to time out regularly on
ci.debian.net (after 2:50 h).

I wonder if the smoke-lxc test is suitable to test *inside* an lxc as
your using virsh. I am not enough into this, but it smells a bit like
you want an "isolation-machine" restriction for that test.

Can you please investigate the situation? Don't hesitate to ask for help
from the Debian CI team (in X-Debbugs-CC) if you need help solving this
issue.

To avoid wasting lots of time on the ci.debian.net infrastructure, I
have blacklisted your package. If needed, please ping me to try any
uploads you make that should fix the issue if you are unsure and don't
want to close this bug until verified.

Paul

https://ci.debian.net/data/autopkgtest/unstable/amd64/libv/libvirt/3677408/log.gz

autopkgtest [18:02:42]: test smoke-lxc: [---
+ virt-host-validate lxc
   LXC: Checking for Linux >= 2.6.26
 : PASS
   LXC: Checking for namespace ipc
 : PASS
   LXC: Checking for namespace mnt
 : PASS
   LXC: Checking for namespace pid
 : PASS
   LXC: Checking for namespace uts
 : PASS
   LXC: Checking for namespace net
 : PASS
   LXC: Checking for namespace user
 : PASS
   LXC: Checking for cgroup 'cpu' controller support
 : PASS
   LXC: Checking for cgroup 'cpuacct' controller support
 : PASS
   LXC: Checking for cgroup 'cpuset' controller support
 : PASS
   LXC: Checking for cgroup 'memory' controller support
 : PASS
   LXC: Checking for cgroup 'devices' controller support
 : PASS
   LXC: Checking for cgroup 'freezer' controller support
 : PASS
   LXC: Checking for cgroup 'blkio' controller support
 : PASS
   LXC: Checking if device /sys/fs/fuse/connections exists
 : PASS
+ virsh capabilities
autopkgtest [20:49:22]: ERROR: timed out on command "su -s /bin/bash
root -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 ||
true;  . ~/.profile >/dev/null 2>&1 || true;
buildtree="/tmp/autopkgtest-lxc.g55a6fi0/downtmp/build.mXC/src"; mkdir
-p -m 1777 --
"/tmp/autopkgtest-lxc.g55a6fi0/downtmp/smoke-lxc-artifacts"; export
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.g55a6fi0/downtmp/smoke-lxc-artifacts";
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755
"/tmp/autopkgtest-lxc.g55a6fi0/downtmp/autopkgtest_tmp"; export
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.g55a6fi0/downtmp/autopkgtest_tmp";
export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive;
export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=2; unset LANGUAGE
LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES
LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT
LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo
$$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f
/tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; export
AUTOPKGTEST_NORMAL_USER=debci; export ADT_NORMAL_USER=debci; chmod +x
/tmp/autopkgtest-lxc.g55a6fi0/downtmp/build.mXC/src/debian/tests/smoke-lxc;
touch /tmp/autopkgtest-lxc.g55a6fi0/downtmp/smoke-lxc-stdout
/tmp/autopkgtest-lxc.g55a6fi0/downtmp/smoke-lxc-stderr;
/tmp/autopkgtest-lxc.g55a6fi0/downtmp/build.mXC/src/debian/tests/smoke-lxc
2> >(tee -a /tmp/autopkgtest-lxc.g55a6fi0/downtmp/smoke-lxc-stderr >&2)
> >(tee -a /tmp/autopkgtest-lxc.g55a6fi0/downtmp/smoke-lxc-stdout);"
(kind: test)
autopkgtest [20:49:22]: test smoke-lxc: ---]



signature.asc
Description: OpenPGP digital signature

Bug#946422: silx: autopkgtest regression: pocl error

[PICCA Frederic-Emmanuel]

looking in picca@sixs7:~/Debian/silx/silx/silx/opencl/test/test_addition.py

def setUp(self):
if ocl is None:
return
self.shape = 4096
self.data = numpy.random.random(self.shape).astype(numpy.float32)
self.d_array_img = pyopencl.array.to_device(self.queue, self.data)
self.d_array_5 = pyopencl.array.zeros_like(self.d_array_img) - 5
self.program = pyopencl.Program(self.ctx, 
get_opencl_code("addition")).build()

I found that commenting this line 

# self.d_array_5 = pyopencl.array.zeros_like(self.d_array_img) - 5

remove the pocl issue.


I remove everythings from the unit test.

@unittest.skipUnless(ocl, "pyopencl is missing")
def test_add(self):
self.assetTrue(True)


that means, only ther setUp and the tearDown are done.

with the line uncomment

(sid_amd64-dchroot)picca@barriere:~$ PYOPENCL_COMPILER_OUTPUT=1 
PYTHONPATH=silx-0.11.0+dfsg/.pybuild/cpython3_3.7_silx/build python3 test.py -v
pocl error: lt_dlopen("(null)") or lt_dlsym() failed with 'can't close resident 
module'.
note: missing symbols in the kernel binary might be reported as 'file not 
found' errors.
Aborted

with the line commented

(sid_amd64-dchroot)picca@barriere:~$ PYOPENCL_COMPILER_OUTPUT=1 
PYTHONPATH=silx-0.11.0+dfsg/.pybuild/cpython3_3.7_silx/build python3 test.py -v
.Maximum valid workgroup size 0 on device 

--
Ran 1 test in 0.013s

OK
Test suite succeeded


If now I do not import silx.io before there is no issue with or without the 
commented line

(sid_amd64-dchroot)picca@barriere:~$ PYOPENCL_COMPILER_OUTPUT=1 
PYTHONPATH=silx-0.11.0+dfsg/.pybuild/cpython3_3.7_silx/build python3 test.py -v
.Maximum valid workgroup size 0 on device 

--
Ran 1 test in 0.021s

OK
Test suite succeeded



So what is going on when executing this line ???


self.d_array_5 = pyopencl.array.zeros_like(self.d_array_img) - 5

Bug#947005: nethack: buffer overflow when parsing config files

[Reiner Herrmann]

Source: nethack
Version: 3.6.0-1
Severity: grave
Tags: security
X-Debbugs-Cc: t...@security.debian.org

Hi,

a new version of NetHack has been released that fixes a privilege
escalation issue introduced in 3.6.0 [0] [1]:

> A buffer overflow issue exists when reading very long lines from a
> NetHack configuration file (usually named .nethackrc).
> 
> This vulnerability affects systems that have NetHack installed suid/sgid
> and shared systems that allow users to upload their own configuration
> files.
> 
> All users are urged to upgrade to NetHack 3.6.4 as soon as possible. 

As the Debian packages ship setgid binaries, I think they are affected by it.

At least these two commits look related:
 https://github.com/NetHack/NetHack/commit/f4a840a
 https://github.com/NetHack/NetHack/commit/f001de7

Regards,
  Reiner

[0] https://nethack.org/security/index.html
[1] https://nethack.org/v364/release.html


signature.asc
Description: PGP signature

Bug#946422: silx: autopkgtest regression: pocl error

[PICCA Frederic-Emmanuel]

I decided to concentrate myself on one opencl test (addition)
So I deactivated all other test by commenting the test in 
silx/opencl/__init__.py

If I do not import silxs.io, this test works

(sid_amd64-dchroot)picca@barriere:~$ PYOPENCL_COMPILER_OUTPUT=1 
PYTHONPATH=silx-0.11.0+dfsg/.pybuild/cpython3_3.7_silx/build python3 test.py -v
.Maximum valid workgroup size 2048 on device 

--
Ran 1 test in 0.030s

OK


If I add silxs.io, it fails

(sid_amd64-dchroot)picca@barriere:~$ PYOPENCL_COMPILER_OUTPUT=1 
PYTHONPATH=silx-0.11.0+dfsg/.pybuild/cpython3_3.7_silx/build python3 test.py -v
pocl error: lt_dlopen("(null)") or lt_dlsym() failed with 'can't close resident 
module'.
note: missing symbols in the kernel binary might be reported as 'file not 
found' errors.
Aborted


so this test is ok in order to investigate this issue.

Bug#945931: haskell-crypto: Removal notice: broken and unmaintained

[Ilias Tsitsimpis]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: haskell-crypto -- ROM; broken and unmaintained
Control: severity -1 normal

Hi,

Please remove haskell-crypto from Debian. It is unmaintained and doesn't
work with the latest version of GHC.

Thanks,

-- 
Ilias

Processed: Re: Bug#945931: haskell-crypto: Removal notice: broken and unmaintained

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #945931 [src:haskell-crypto] haskell-crypto: Removal notice: broken and 
unmaintained
Bug reassigned from package 'src:haskell-crypto' to 'ftp.debian.org'.
No longer marked as found in versions haskell-crypto/4.2.5.1-9.
Ignoring request to alter fixed versions of bug #945931 to the same values 
previously set
> retitle -1 RM: haskell-crypto -- ROM; broken and unmaintained
Bug #945931 [ftp.debian.org] haskell-crypto: Removal notice: broken and 
unmaintained
Changed Bug title to 'RM: haskell-crypto -- ROM; broken and unmaintained' from 
'haskell-crypto: Removal notice: broken and unmaintained'.
> severity -1 normal
Bug #945931 [ftp.debian.org] RM: haskell-crypto -- ROM; broken and unmaintained
Severity set to 'normal' from 'grave'

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

Bug#946422: silx: autopkgtest regression: pocl error

[PICCA Frederic-Emmanuel]

With the silx.io import I have this

(sid_amd64-dchroot)picca@barriere:~$ 
PYTHONPATH=silx-0.11.0+dfsg/.pybuild/cpython3_3.7_silx/build python3 test.py 
pocl error: lt_dlopen("(null)") or lt_dlsym() failed with 'can't close resident 
module'.
note: missing symbols in the kernel binary might be reported as 'file not 
found' errors.

without, I have this

(sid_amd64-dchroot)picca@barriere:~$ 
PYTHONPATH=silx-0.11.0+dfsg/.pybuild/cpython3_3.7_silx/build python3 test.py -v
.Maximum valid workgroup size 2048 on device 
FThe gpyfft module was not found. The Fourier transforms will be done on CPU. 
For more performances, it is advised to install gpyfft.
.The gpyfft module was not found. The Fourier transforms will be done on CPU. 
For more performances, it is advised to install gpyfft.
The gpyfft module was not found. The Fourier transforms will be done on CPU. 
For more performances, it is advised to install gpyfft.
The gpyfft module was not found. The Fourier transforms will be done on CPU. 
For more performances, it is advised to install gpyfft.
The gpyfft module was not found. The Fourier transforms will be done on CPU. 
For more performances, it is advised to install gpyfft.
The gpyfft module was not found. The Fourier transforms will be done on CPU. 
For more performances, it is advised to install gpyfft.
The gpyfft module was not found. The Fourier transforms will be done on CPU. 
For more performances, it is advised to install gpyfft.
.The gpyfft module was not found. The Fourier transforms will be done on CPU. 
For more performances, it is advised to install gpyfft.
The gpyfft module was not found. The Fourier transforms will be done on CPU. 
For more performances, it is advised to install gpyfft.
../home/picca/silx-0.11.0+dfsg/.pybuild/cpython3_3.7_silx/build/silx/opencl/test/test_linalg.py:69:
 FutureWarning: Using a non-tuple sequence for multidimensional indexing is 
deprecated; use `arr[tuple(seq)]` instead of `arr[seq]`. In the future this 
will be interpreted as an array index, `arr[np.array(seq)]`, which will result 
either in an error or a different result.
  gradient[slice_all] = np.diff(img, axis=d)
4096
...7 warnings generated.
/usr/lib/python3/dist-packages/pyopencl/__init__.py:235: CompilerWarning: 
Non-empty compiler output encountered. Set the environment variable 
PYOPENCL_COMPILER_OUTPUT=1 to see more.
  "to see more.", CompilerWarning)
..7 warnings generated.
..
==
FAIL: test_medfilt (silx.opencl.test.test_medfilt.TestMedianFilter)
--
Traceback (most recent call last):
  File 
"/home/picca/silx-0.11.0+dfsg/.pybuild/cpython3_3.7_silx/build/silx/opencl/test/test_medfilt.py",
 line 115, in test_medfilt
self.assertEqual(r.error, 0, 'Results are correct')
AssertionError: 3.4028235e+38 != 0 : Results are correct

--
Ran 217 tests in 175.525s

FAILED (failures=1, skipped=48)


I will run it with the PYOPENCL_COMPILEr_OUTPUT=1 to check that compiler warning


(sid_amd64-dchroot)picca@barriere:~$ PYOPENCL_COMPILER_OUTPUT=1 
PYTHONPATH=silx-0.11.0+dfsg/.pybuild/cpython3_3.7_silx/build python3 test.py -v
.Maximum valid workgroup size 2048 on device 
FThe gpyfft module was not found. The Fourier transforms will be done on CPU. 
For more performances, it is advised to install gpyfft.
.The gpyfft module was not found. The Fourier transforms will be done on CPU. 
For more performances, it is advised to install gpyfft.
The gpyfft module was not found. The Fourier transforms will be done on CPU. 
For more performances, it is advised to install gpyfft.
The gpyfft module was not found. The Fourier transforms will be done on CPU. 
For more performances, it is advised to install gpyfft.
The gpyfft module was not found. The Fourier transforms will be done on CPU. 
For more performances, it is advised to install gpyfft.
The gpyfft module was not found. The Fourier transforms will be done on CPU. 
For more performances, it is advised to install gpyfft.
The gpyfft module was not found. The Fourier transforms will be done on CPU. 
For more performances, it is advised to install gpyfft.
.The gpyfft module was not found. The Fourier transforms will be done on CPU. 
For more performances, it is advised to install gpyfft.
The gpyfft module was not found. The Fourier transforms will be done on CPU. 
For more performances, it is advised to install gpyfft.
../home/picca/silx-0.11.0+dfsg/.pybuild/cpython3_3.7_silx/build/silx/opencl/test/test_linalg.py:69:
 FutureWarning: Using a non-tuple sequence for multidimensional indexing is 
deprecated; use `arr[tuple(seq)]` instead of `arr[seq]`. In the future this 
will be 

Bug#943943: getfem++ ftbfs

[Konstantinos Poulios]

the latest ftbfs on all architectures seems more like a python2to3
transition issue

/usr/bin/env: ‘python’: No such file or directory

Processed: unarchiving 635457

[Debian Bug Tracking System]

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

> unarchive 635457
Bug #635457 {Done: Emilio Pozuelo Monfort } [gvfs] 
gvfsd-metadata: gvfsd-metadata creates a large amount of NFS network I/O on 
NFS-mounted user home directory
Bug #624507 {Done: Emilio Pozuelo Monfort } [gvfs] Started 
looping and continuously rewriting metadata file
Unarchived Bug 635457
Unarchived Bug 624507
> thanks
Stopping processing here.

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

Processed: archiving 635457

[Debian Bug Tracking System]

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

> archive 635457
Bug #635457 {Done: Emilio Pozuelo Monfort } [gvfs] 
gvfsd-metadata: gvfsd-metadata creates a large amount of NFS network I/O on 
NFS-mounted user home directory
Bug #624507 {Done: Emilio Pozuelo Monfort } [gvfs] Started 
looping and continuously rewriting metadata file
archived 635457 to archive/57 (from 635457)
archived 624507 to archive/07 (from 635457)
> thanks
Stopping processing here.

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

Bug#940985: dnsmasq: diff for NMU version 2.80-1.1

[Paul Gevers]

Control: tags 940985 + pending

Dear maintainer,

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

Regards.

diff -u dnsmasq-2.80/debian/changelog dnsmasq-2.80/debian/changelog
--- dnsmasq-2.80/debian/changelog
+++ dnsmasq-2.80/debian/changelog
@@ -1,3 +1,12 @@
+dnsmasq (2.80-1.1) unstable; urgency=medium
+
+  [ Andreas Metzler ]
+  * Non-maintainer upload.
+  * Apply ab73a746a0d6fcac2e682c5548eeb87fb9c9c82e from upstream GIT to fix
+build error against nettle 3.5. Closes: #940985
+
+ -- Paul Gevers   Wed, 18 Dec 2019 21:23:49 +0100
+
 dnsmasq (2.80-1) unstable; urgency=low

* New upstream. (closes: #837602) (closes: #794640) (closes: #794636)
only in patch2:
unchanged:
--- dnsmasq-2.80.orig/src/crypto.c
+++ dnsmasq-2.80/src/crypto.c
@@ -275,6 +275,10 @@
   static struct ecc_point *key_256 = NULL, *key_384 = NULL;
   static mpz_t x, y;
   static struct dsa_signature *sig_struct;
+#if NETTLE_VERSION_MAJOR == 3 && NETTLE_VERSION_MINOR < 4
+#define nettle_get_secp_256r1() (_secp_256r1)
+#define nettle_get_secp_384r1() (_secp_384r1)
+#endif

   if (!sig_struct)
 {
@@ -294,7 +298,7 @@
  if (!(key_256 = whine_malloc(sizeof(struct ecc_point
return 0;

- nettle_ecc_point_init(key_256, _secp_256r1);
+ nettle_ecc_point_init(key_256, nettle_get_secp_256r1());
}

   key = key_256;
@@ -307,7 +311,7 @@
  if (!(key_384 = whine_malloc(sizeof(struct ecc_point
return 0;

- nettle_ecc_point_init(key_384, _secp_384r1);
+ nettle_ecc_point_init(key_384, nettle_get_secp_384r1());
}

   key = key_384;



signature.asc
Description: OpenPGP digital signature

Processed: dnsmasq: diff for NMU version 2.80-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 940985 + pending
Bug #940985 [src:dnsmasq] dnsmasq WFTBFS: Accesses ECC curves directly
Added tag(s) pending.

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

Bug#946359: pg-snakeoil: Selftest apears to be broken

[Christoph Berg]

Re: Sebastian Andrzej Siewior 2019-12-18 <20191218225837.qttuxpwrbo5ukpr3@flow>
> > $ sudo -u clamav freshclam --verbose
> 
> what happens if you strip the sudo part? One of the first thing is to
> change to the clamav user (well so is my memory and the /var/…/clamav is
> owned by clamav so…)? However after I install sudo in my chroot and try
> this it still works :/

Now it just works, both with "sudo freshclam --verbose" and "sudo -u
clamav freshclam --verbose":

$ sudo freshclam --verbose
Thu Dec 19 10:00:32 2019 -> ClamAV update process started at Thu Dec 19 
10:00:32 2019
Thu Dec 19 10:00:32 2019 -> *Current working dir is /var/lib/clamav/
Thu Dec 19 10:00:32 2019 -> *Querying current.cvd.clamav.net
Thu Dec 19 10:00:32 2019 -> *TTL: 539
Thu Dec 19 10:00:32 2019 -> *fc_dns_query_update_info: Software version from 
DNS: 0.102.1
Thu Dec 19 10:00:32 2019 -> *Current working dir is /var/lib/clamav/
Thu Dec 19 10:00:32 2019 -> *check_for_new_database_version: No local copy of 
"daily" database.
Thu Dec 19 10:00:32 2019 -> *query_remote_database_version: daily.cvd version 
from DNS: 25667
Thu Dec 19 10:00:32 2019 -> daily database available for download (remote 
version: 25667)
Thu Dec 19 10:00:32 2019 -> *Retrieving https://database.clamav.net/daily.cvd
Thu Dec 19 10:00:32 2019 -> *downloadFile: Download source:  
https://database.clamav.net/daily.cvd
Thu Dec 19 10:00:32 2019 -> *downloadFile: Download destination: 
/var/lib/clamav/tmp/clamav-a0eebaf13c63bb204c5e5a77e26f717c.tmp
*   Trying 2606:4700::6810:db54:443...
* TCP_NODELAY set
* Connected to database.clamav.net (2606:4700::6810:db54) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: none
  CApath: /etc/ssl/certs
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: OU=Domain Control Validated; OU=PositiveSSL Multi-Domain; 
CN=ssl392509.cloudflaressl.com
*  start date: Aug 24 00:00:00 2019 GMT
*  expire date: Mar  1 23:59:59 2020 GMT
*  subjectAltName: host "database.clamav.net" matched cert's "*.clamav.net"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=COMODO CA Limited; 
CN=COMODO ECC Domain Validation Secure Server CA 2
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x55c822a6d790)
> GET /daily.cvd HTTP/2
Host: database.clamav.net
user-agent: ClamAV/0.102.1 (OS: linux-gnu, ARCH: x86_64, CPU: x86_64)
accept: */*
connection: close

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 256)!
< HTTP/2 200 
< date: Thu, 19 Dec 2019 09:00:33 GMT
< content-type: application/octet-stream
< content-length: 55429776
< set-cookie: __cfduid=d808352f8029efc872822e310079600b81576746033; 
expires=Sat, 18-Jan-20 09:00:33 GMT; path=/; domain=.clamav.net; HttpOnly; 
SameSite=Lax
< last-modified: Wed, 18 Dec 2019 09:53:00 GMT
< etag: "5df9f6fc-34dca90"
< expires: Thu, 19 Dec 2019 13:00:33 GMT
< cache-control: public, max-age=14400
< cf-cache-status: HIT
< age: 3383
< accept-ranges: bytes
< strict-transport-security: max-age=15552000
< x-content-type-options: nosniff
< expect-ct: max-age=604800, 
report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct;
< server: cloudflare
< cf-ray: 54782fd3fa8ed45b-HAM
< 
Time: 3.5s, ETA; 0.0s [===>] 
52.86MiB/52.86MiB
* Connection #0 to host database.clamav.net left intact
Thu Dec 19 10:00:36 2019 -> *updatedb: Running g_cb_download_complete 
callback...
Thu Dec 19 10:00:36 2019 -> *download_complete_callback: Download complete for 
database : 
/var/lib/clamav/tmp/clamav-a0eebaf13c63bb204c5e5a77e26f717c.tmp-daily.cvd
Thu Dec 19 10:00:36 2019 -> *download_complete_callback:   
fc_context->bTestDatabases   : 1
Thu Dec 19 10:00:36 2019 -> *download_complete_callback:   
fc_context->bBytecodeEnabled : 1
Thu Dec 19 10:00:36 2019 -> Testing database: 
'/var/lib/clamav/tmp/clamav-a0eebaf13c63bb204c5e5a77e26f717c.tmp-daily.cvd' ...
Thu Dec 19 10:00:36 2019 -> *Loading signatures from 
/var/lib/clamav/tmp/clamav-a0eebaf13c63bb204c5e5a77e26f717c.tmp-daily.cvd
Thu Dec 19 10:00:40 2019 -> *Properly loaded 2061162 signatures from 
/var/lib/clamav/tmp/clamav-a0eebaf13c63bb204c5e5a77e26f717c.tmp-daily.cvd
Thu Dec 19 10:00:41 2019 -> Database test passed.
Thu Dec 19 10:00:41 2019 -> daily.cvd updated (version: 25667, sigs: 2061162, 
f-level: 63, builder: raynman)
Thu Dec 19 10:00:41 2019 -> *fc_update_database: daily.cvd updated.
Thu Dec 19 10:00:41 2019 -> *Current working dir is /var/lib/clamav/
Thu Dec 19 10:00:41 2019 -> *check_for_new_database_version: No local copy of 
"main" database.
Thu Dec 19 10:00:41 2019 -> *query_remote_database_version: main.cvd version 
from DNS: 59
Thu Dec 19 10:00:41 2019 -> main database 

Bug#941544: marked as done (proofgeneral: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)

[Debian Bug Tracking System]

Your message dated Thu, 19 Dec 2019 08:41:52 +
with message-id 
and subject line Bug#941544: fixed in proofgeneral 4.4.1~pre170114-1.2
has caused the Debian Bug report #941544,
regarding proofgeneral: build-depend on texlive-plain-generic, not obsolete 
texlive-generic-recommended
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.)


-- 
941544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: proofgeneral
Version: 4.4.1~pre170114-1.1
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

Hi Hendrik,

The texlive-generic-recommended transitional package has been dropped from
texlive-base in sid.  Please update your build-dependency to
texlive-plain-generic instead.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru proofgeneral-4.4.1~pre170114/debian/control 
proofgeneral-4.4.1~pre170114/debian/control
--- proofgeneral-4.4.1~pre170114/debian/control 2019-07-25 01:15:04.0 
-0700
+++ proofgeneral-4.4.1~pre170114/debian/control 2019-10-01 14:38:55.0 
-0700
@@ -2,7 +2,7 @@
 Section: editors
 Priority: optional
 Maintainer: Hendrik Tews 
-Build-Depends: debhelper (>= 9), texinfo, texlive-latex-recommended, 
texlive-generic-recommended, texlive-fonts-recommended, emacs-gtk
+Build-Depends: debhelper (>= 9), texinfo, texlive-latex-recommended, 
texlive-plain-generic, texlive-fonts-recommended, emacs-gtk
 Standards-Version: 3.9.8
 Homepage: https://proofgeneral.github.io/
 
--- End Message ---
--- Begin Message ---
Source: proofgeneral
Source-Version: 4.4.1~pre170114-1.2

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

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

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

Debian distribution maintenance software
pp.
Gard Spreemann  (supplier of updated proofgeneral package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 16 Dec 2019 17:50:59 +0100
Source: proofgeneral
Architecture: source
Version: 4.4.1~pre170114-1.2
Distribution: unstable
Urgency: medium
Maintainer: Hendrik Tews 
Changed-By: Gard Spreemann 
Closes: 941544
Changes:
 proofgeneral (4.4.1~pre170114-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build-depend on texlive-plain-generic instead of
 texlive-generic-recommended. Thanks to Steve Langasek for
 patch. (Closes: #941544)
Checksums-Sha1:
 ef3552e140ca2fc5c396d930ab1f5fc9a549ec79 1983 
proofgeneral_4.4.1~pre170114-1.2.dsc
 ebb27ec63fa5f6bb89725df5fdd3ee86c9ef9a28 19908 
proofgeneral_4.4.1~pre170114-1.2.debian.tar.xz
 41752a7b34c7c95663457c7d908aead7183f0b7d 10964 
proofgeneral_4.4.1~pre170114-1.2_source.buildinfo
Checksums-Sha256:
 c466855c5f38e46b3b8eed4cd8e83817ce16de4a6330c8d2fc8503d7f8a4d05a 1983 
proofgeneral_4.4.1~pre170114-1.2.dsc
 184d07cc7aaa1dc58928b30639668d87d996c64c1e508f4f7259613acc298cd5 19908 
proofgeneral_4.4.1~pre170114-1.2.debian.tar.xz
 9c1a69d8828fd853e69adc4b02cb0f92de4274a09ef3c2d58843d2e940bfa946 10964 
proofgeneral_4.4.1~pre170114-1.2_source.buildinfo
Files:
 21b7565fce5cb4e7ac1144322e733d49 1983 editors optional 
proofgeneral_4.4.1~pre170114-1.2.dsc
 f93803a132978a784df69075beb0b89a 19908 editors optional 
proofgeneral_4.4.1~pre170114-1.2.debian.tar.xz
 458b06b53393cada191f8cfc4d7313e2 10964 editors optional 
proofgeneral_4.4.1~pre170114-1.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEESYqTBWsFJgT6y8ijKb+g0HkpCsoFAl37LXoACgkQKb+g0Hkp
CsorpxAAuJLzsfBADr2NicLyQjRmH47lOdSK96oXtfUH+IpAFfWJInBFhMcWNBGZ
LrOI6X5odQwhT/tVSuhF/Hr9XsSo99Av/x2rya6TvUxGGix4BYPHRqC57E3OhE5E
/8040d0g83WjE5oG/vGdvOS3weCEovHu9mUz/FdGH1NdbAjxRsMHM0n4p3kp3G90
0ByKz1Iq4JyOP0zxiOgnrzq0iCayEkM6F1GrAFwB8ixTHsndEBZZvaRq2PwY4pzQ
dtEEtxmW8+C7gIMIs6/DNbh4eIg+KbedzPIsCmf5Gi6+WfmOh3OrMIbj0Wwwh+4t

Bug#946800: marked as done (python3-pbcommand: missing Breaks+Replaces: python-pbcommand (<< 1.1.1+git20191122.ec024c3))

[Debian Bug Tracking System]

Your message dated Thu, 19 Dec 2019 08:42:03 +
with message-id 
and subject line Bug#946800: fixed in python-pbcommand 
1.1.1+git20191122.ec024c3-3
has caused the Debian Bug report #946800,
regarding python3-pbcommand: missing Breaks+Replaces: python-pbcommand (<< 
1.1.1+git20191122.ec024c3)
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.)


-- 
946800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pbcommand
Version: 1.1.1+git20191122.ec024c3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package python3-pbcommand.
  Preparing to unpack 
.../16-python3-pbcommand_1.1.1+git20191122.ec024c3-1_all.deb ...
  Unpacking python3-pbcommand (1.1.1+git20191122.ec024c3-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-vOkgKo/16-python3-pbcommand_1.1.1+git20191122.ec024c3-1_all.deb
 (--unpack):
   trying to overwrite '/usr/share/man/man1/pbservice.1.gz', which is also in 
package python-pbcommand 1.1.1-1
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-vOkgKo/16-python3-pbcommand_1.1.1+git20191122.ec024c3-1_all.deb


cheers,

Andreas


python-pbcommand=1.1.1-1_python3-pbcommand=1.1.1+git20191122.ec024c3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-pbcommand
Source-Version: 1.1.1+git20191122.ec024c3-3

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-pbcommand package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 19 Dec 2019 09:10:31 +0100
Source: python-pbcommand
Architecture: source
Version: 1.1.1+git20191122.ec024c3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 946800
Changes:
 python-pbcommand (1.1.1+git20191122.ec024c3-3) unstable; urgency=medium
 .
   * Really Breaks+Provides+Replaces: python-pbcommand
 Closes: #946800
Checksums-Sha1:
 0f1fbcbd7146cdbfef0edfd93658507195b83bf7 2537 
python-pbcommand_1.1.1+git20191122.ec024c3-3.dsc
 5a5434c0d21084aa96895d6a498cf7f083ca4b36 5108 
python-pbcommand_1.1.1+git20191122.ec024c3-3.debian.tar.xz
 cc5a237761f6f637ef87ffdd5fff42ea2e51d16e 8906 
python-pbcommand_1.1.1+git20191122.ec024c3-3_amd64.buildinfo
Checksums-Sha256:
 cbcb4ce4e4daa53d24f2141bf96fc0f0c3c18b03b97b36ec616511a601605f8d 2537 
python-pbcommand_1.1.1+git20191122.ec024c3-3.dsc
 c07d2cd064eccef38a31e2fbe5b92fd69fb6d0dc242ea2da1eba19275dda544d 5108 
python-pbcommand_1.1.1+git20191122.ec024c3-3.debian.tar.xz
 f2e525c64f2e7b8f6c5ebe732f7cefb014e3a871b5650f7a5b81df3c25e4fe6d 8906 
python-pbcommand_1.1.1+git20191122.ec024c3-3_amd64.buildinfo
Files:
 0631d74e634faf07a7f1d391c5ed22b6 2537 python optional 
python-pbcommand_1.1.1+git20191122.ec024c3-3.dsc
 79bd7f00d15c1d4d8dc3f12c43b09313 5108 python optional 
python-pbcommand_1.1.1+git20191122.ec024c3-3.debian.tar.xz
 f241d7ddd4174e213f53cdd8c4353f8d 8906 python optional 
python-pbcommand_1.1.1+git20191122.ec024c3-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl37MtYRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFXshAAjYArWF62bNFgBbVxLtYYBmWfhXO0eEF7
HccUt217YUI3R2QwGtR2C1ATeXom5UaTT8v8kR4nSA8mH93woA92E0YhmZWo2ZrA
88DMKlJTDunmz8tJCYcUVCwXNpGC7qmES71/+fHbuIWKP256yfPBaauLPJ4VdsBW
GlApAiqIvlzR/q4F8IwT93CBoXe6GWMdwq1OgzP0K9BIdJN3Ez399d718lbX9OVn
SvtYBEwrtMK8uiAxHzUDxptWaKBL2fNsvn3ORudXx5APoqlvV94fRGZvZaHZqMyx
xyVopgCAEM/ewD4roQagAp7UKGvp7rapyrbL29+dI62fJKysGBQfyGeK3EbvA1Uj

Processed: Re: Bug#939506: unanimity ftbfs in unstable

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #939506 [src:unanimity] unanimity ftbfs in unstable
Added tag(s) help.

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

Bug#939506: unanimity ftbfs in unstable

[Andreas Tille]

Control: tags -1 help

Hi,

On Thu, Sep 05, 2019 at 06:39:33PM +0200, Matthias Klose wrote:
> cd /build/1st/unanimity-3.3.0+dfsg/build/src && /usr/bin/cmake -E
> cmake_link_script CMakeFiles/gcpp.dir/link.txt --verbose=1
> /build/1st/unanimity-3.3.0+dfsg/src/main/ccs.cpp: In function ‘int
> Runner(const PacBio::CLI::Results&)’:
> /build/1st/unanimity-3.3.0+dfsg/src/main/ccs.cpp:570:38: error: ‘move’ was
> not declared in this scope
>   570 | read.Sequence(), move(ipd), move(pw),
> read.LocalContextFlags(),
>   |  ^~~~

I have pushed the latest upstream version to Git[1].  The whole error message
is now:


...
cd /build/unanimity-3.4.1+git20180307.02aa264+dfsg/build/src && /usr/bin/c++   
-I/build/unanimity-3.4.1+git20180307.02aa264+dfsg/include 
-I/build/unanimity-3.4.1+git20180307.02aa264+dfsg/build/generated 
-I/build/unanimity-3.4.1+git20180307.02aa264+dfsg/src  -g -O2 
-fdebug-prefix-map=/build/unanimity-3.4.1+git20180307.02aa264+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time - 
  D_FORTIFY_SOURCE=2 -Wall -Wextra -Wno-unused-parameter 
-Wno-unused-variable -Wno-unused-local-typedefs   -fPIC -std=c++14 -o 
CMakeFiles/ccs.dir/main/ccs.cpp.o -c 
/build/unanimity-3.4.1+git20180307.02aa264+dfsg/  src/main/ccs.cpp
/build/unanimity-3.4.1+git20180307.02aa264+dfsg/src/main/ccs.cpp:63:12: error: 
‘std::setprecision’ has not been declared
   63 | using std::setprecision;
  |^~~~
/build/unanimity-3.4.1+git20180307.02aa264+dfsg/src/main/ccs.cpp: In function 
‘void WriteResultsReport(std::ostream&, const Results&)’:
/build/unanimity-3.4.1+git20180307.02aa264+dfsg/src/main/ccs.cpp:273:24: error: 
‘setprecision’ was not declared in this scope
  273 | report << fixed << setprecision(2);
  |^~~~
/build/unanimity-3.4.1+git20180307.02aa264+dfsg/src/main/ccs.cpp: In function 
‘int Runner(const PacBio::CLI::Results&)’:
/build/unanimity-3.4.1+git20180307.02aa264+dfsg/src/main/ccs.cpp:570:38: error: 
‘move’ was not declared in this scope
  570 | read.Sequence(), move(ipd), move(pw), 
read.LocalContextFlags(),
  |  ^~~~
/build/unanimity-3.4.1+git20180307.02aa264+dfsg/src/main/ccs.cpp:570:38: note: 
suggested alternatives:
In file included from /usr/include/c++/9/deque:67,
 from /usr/include/boost/detail/container_fwd.hpp:91,
 from /usr/include/boost/container_hash/extensions.hpp:22,
 from /usr/include/boost/container_hash/hash.hpp:760,
 from /usr/include/boost/type_index/stl_type_index.hpp:43,
 from /usr/include/boost/type_index.hpp:29,
 from /usr/include/boost/function/function_base.hpp:21,
 from /usr/include/boost/function/detail/prologue.hpp:17,
 from /usr/include/boost/function.hpp:30,
 from 
/usr/include/boost/algorithm/string/detail/find_iterator.hpp:18,
 from /usr/include/boost/algorithm/string/find_iterator.hpp:24,
 from /usr/include/boost/algorithm/string/iter_find.hpp:27,
 from /usr/include/boost/algorithm/string/split.hpp:16,
 from /usr/include/boost/algorithm/string.hpp:23,
 from 
/build/unanimity-3.4.1+git20180307.02aa264+dfsg/src/main/ccs.cpp:14:
/usr/include/c++/9/bits/stl_deque.h:443:5: note:   ‘std::move’
  443 | move(_Deque_iterator<_Tp, _Tp&, _Tp*> __first,
  | ^~~~
In file included from /usr/include/boost/move/algorithm.hpp:29,
 from /usr/include/boost/move/move.hpp:32,
 from /usr/include/boost/variant/detail/move.hpp:28,
 from /usr/include/boost/variant/detail/initializer.hpp:23,
 from /usr/include/boost/variant/variant.hpp:30,
 from /usr/include/boost/variant.hpp:17,
 from /usr/include/pbbam/Tag.h:10,
 from /usr/include/pbbam/TagCollection.h:13,
 from /usr/include/pbbam/BamRecordImpl.h:21,
 from /usr/include/pbbam/BamRecord.h:19,
 from /usr/include/pbbam/BamWriter.h:15,
 from 
/build/unanimity-3.4.1+git20180307.02aa264+dfsg/src/main/ccs.cpp:22:
/usr/include/boost/move/algo/move.hpp:53:6: note:   ‘boost::move’
   53 |O move(I f, I l, O result)
  |  ^~~~
In file included from /usr/include/boost/function/function_template.hpp:32,
 from /usr/include/boost/function/detail/maybe_include.hpp:15,
 from 
/usr/include/boost/function/detail/function_iterate.hpp:14,
 from 
/usr/include/boost/preprocessor/iteration/detail/iter/forward1.hpp:48,
 from /usr/include/boost/function.hpp:71,
 from 
/usr/include/boost/algorithm/string/detail/find_iterator.hpp:18,
 from 

Processed: block 946817 with 946980

[Debian Bug Tracking System]

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

> block 946817 with 946980
Bug #946817 [src:botch] botch ftbfs, fails tests on 32bit archs
946817 was not blocked by any bugs.
946817 was not blocking any bugs.
Added blocking bug(s) of 946817: 946980
> thanks
Stopping processing here.

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