Bug#946718: gbrowse: autopkgtest regression: Can't call method "features" on an undefined value

[gregor herrmann]

On Tue, 17 Dec 2019 08:35:40 +0100, Andreas Tille wrote:

> > https://ci.debian.net/data/autopkgtest/testing/amd64/g/gbrowse/3555081/log.gz
> > 
> > t/01.yeast.t ..
> > 1..7
> > not ok 1
> > # Failed test 1 in t/01.yeast.t at line 29
> > Can't call method "features" on an undefined value at t/01.yeast.t line 31.
> > Dubious, test returned 25 (wstat 6400, 0x1900)
> > Failed 7/7 subtests
> 
> The latest test log is:

> autopkgtest [15:25:16]: test autodep8-perl-recommends: 
> ---]
> autopkgtest [15:25:16]: test autodep8-perl-recommends:  - - - - - - - - - - 
> results - - - - - - - - - -
> autodep8-perl-recommends PASS (superficial)
> autopkgtest [15:25:16]:  summary
> autodep8-perl-build-deps FAIL non-zero exit status 1
> autodep8-perlPASS (superficial)
> autodep8-perl-recommends PASS (superficial)
> ...
> 
> 
> So the above issue seems to be solved.  However, the test is failing
> anyway - but I have no idea why?

Not sure which log you are referring to with "latest test log" as I
see the failure in all of them I found at ci.d.n. - Please note that
you are quoting only the last of the three test sections
(autodep8-perl-recommends), and the failure in the smoke test happens
in autodep8-perl-build-deps.

Anyway, looking at 
https://salsa.debian.org/med-team/gbrowse/blob/master/t/01.yeast.t#L26
my guess is that the tests need the sample_data directory; which is
there during build but not by default during autopkgtests because
there only t/ is copied to a new temporary directory.

What I would try (can't test right now) is:
- mkdir -p debian/tests/pkg-perl
- $EDITOR debian/tests/pkg-perl/smoke-files with:
  t/
  sample_data/

(Cf. https://perl-team.pages.debian.net/autopkgtest.html#smoke )


Hope this helps, happy to take a closer look in the evening.


Cheers,
gregor
  

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   BOFH excuse #352:  The cables are not the same length. 

Processed: Re: Bug#946718: gbrowse: autopkgtest regression: Can't call method "features" on an undefined value

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #946718 [src:gbrowse] gbrowse: autopkgtest regression: Can't call method 
"features" on an undefined value
Added tag(s) help.

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

Bug#946718: gbrowse: autopkgtest regression: Can't call method "features" on an undefined value

[Andreas Tille]

Control: tags -1 help


Hi,

On Sat, Dec 14, 2019 at 04:16:36PM +0100, Paul Gevers wrote:
> [1] https://qa.debian.org/excuses.php?package=gbrowse
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/g/gbrowse/3555081/log.gz
> 
> t/01.yeast.t ..
> 1..7
> not ok 1
> # Failed test 1 in t/01.yeast.t at line 29
> Can't call method "features" on an undefined value at t/01.yeast.t line 31.
> Dubious, test returned 25 (wstat 6400, 0x1900)
> Failed 7/7 subtests

The latest test log is:

...
autopkgtest [15:25:15]: test autodep8-perl-recommends: 
/usr/share/pkg-perl-autopkgtest/runner runtime-deps-and-recommends
autopkgtest [15:25:15]: test autodep8-perl-recommends: [---
/usr/share/pkg-perl-autopkgtest/runtime-deps-and-recommends.d/syntax.t .. 
1..12
ok 1 - Package gbrowse is known to dpkg
ok 2 - Got status information for package gbrowse
ok 3 # skip gbrowse has Suggestions and no explicit skip list
ok 4 # skip gbrowse has Suggestions and no explicit skip list
ok 5 - Package gbrowse-data is known to dpkg
ok 6 - Got status information for package gbrowse-data
ok 7 - Got file list for package gbrowse-data
ok 8 # skip no perl modules to test in gbrowse-data
ok 9 - Package gbrowse-calign is known to dpkg
ok 10 - Got status information for package gbrowse-calign
ok 11 - Got file list for package gbrowse-calign
# Subtest: all modules in gbrowse-calign pass the syntax check
1..1
ok 1 - /usr/bin/perl -wc 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Bio/Graphics/Browser2/CAlign.pm exited 
successfully
ok 12 - all modules in gbrowse-calign pass the syntax check
ok
All tests successful.
Files=1, Tests=12,  0 wallclock secs ( 0.02 usr  0.00 sys +  0.11 cusr  0.04 
csys =  0.17 CPU)
Result: PASS
autopkgtest [15:25:16]: test autodep8-perl-recommends: ---]
autopkgtest [15:25:16]: test autodep8-perl-recommends:  - - - - - - - - - - 
results - - - - - - - - - -
autodep8-perl-recommends PASS (superficial)
autopkgtest [15:25:16]:  summary
autodep8-perl-build-deps FAIL non-zero exit status 1
autodep8-perlPASS (superficial)
autodep8-perl-recommends PASS (superficial)
...


So the above issue seems to be solved.  However, the test is failing
anyway - but I have no idea why?

Any hint?

Kind regards

   Andreas.


-- 
http://fam-tille.de

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

[Debian Bug Tracking System]

Your message dated Tue, 17 Dec 2019 05:50:28 +
with message-id 
and subject line Bug#937643: fixed in python-characteristic 14.3.0-3
has caused the Debian Bug report #937643,
regarding python-characteristic: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-characteristic

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 16 Dec 2019 14:58:18 +
Source: python-characteristic
Architecture: source
Version: 14.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Dimitri John Ledkov 
Closes: 937643
Changes:
 python-characteristic (14.3.0-3) unstable; urgency=medium
 .
   * QA upload.
   * Drop python2 package. Closes: #937643
Checksums-Sha1:
 75f7594210024a11be5d7d9bba28aa0116b45d8d 1944 
python-characteristic_14.3.0-3.dsc
 9f2be82a7195934e41dff3f950f1c5289029e00e 2356 
python-characteristic_14.3.0-3.debian.tar.xz
 64a83909be3f4e1776ea34c0e469dbe4b420fa7a 7675 
python-characteristic_14.3.0-3_source.buildinfo
Checksums-Sha256:
 b19ca173ae146b94470daaf28d231895fd08856f483336636aeb80c9515126e0 1944 
python-characteristic_14.3.0-3.dsc
 556b0845508674584788384e74384c603e019591829acb08cc5f89693d41e564 2356 
python-characteristic_14.3.0-3.debian.tar.xz

Bug#937270: marked as done (pegasus-wms: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 17 Dec 2019 05:27:15 +
with message-id 
and subject line Bug#946849: Removed package(s) from unstable
has caused the Debian Bug report #937270,
regarding pegasus-wms: 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.)


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

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

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

Dear submitter,

as the package pegasus-wms 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/946849

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

[Debian Bug Tracking System]

Your message dated Tue, 17 Dec 2019 05:28:14 +
with message-id 
and subject line Bug#946867: Removed package(s) from unstable
has caused the Debian Bug report #942998,
regarding debpartial-mirror: 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.)


-- 
942998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debpartial-mirror
Version: 0.3.1+nmu1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

Dear submitter,

as the package debpartial-mirror 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/946867

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#944652: marked as done (cmark-gfm: FTBFS on s390x)

[Debian Bug Tracking System]

Your message dated Tue, 17 Dec 2019 05:04:10 +
with message-id 
and subject line Bug#944652: fixed in cmark-gfm 0.29.0.gfm.0-2
has caused the Debian Bug report #944652,
regarding cmark-gfm: FTBFS on s390x
to be marked as done.

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

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


-- 
944652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:cmark-gfm
version: 0.29.0.gfm.0-1
severity: serious
tags: ftbfs

Hi,

The latest upload of cmark-gfm to unstable fails on s390x:

https://buildd.debian.org/status/package.php?p=cmark-gfm

Also, if you upload a fix for this, please do a source-only upload to allow it
to migrate to testing.

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: cmark-gfm
Source-Version: 0.29.0.gfm.0-2

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

Debian distribution maintenance software
pp.
Keith Packard  (supplier of updated cmark-gfm 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: Mon, 16 Dec 2019 20:37:41 -0800
Source: cmark-gfm
Architecture: source
Version: 0.29.0.gfm.0-2
Distribution: unstable
Urgency: medium
Maintainer: Keith Packard 
Changed-By: Keith Packard 
Closes: 944652
Changes:
 cmark-gfm (0.29.0.gfm.0-2) unstable; urgency=medium
 .
   * Merge upstream fix for tasklist on MSB machines (Closes: #944652)
Checksums-Sha1:
 75098d9b450a5e916886e8195aed3cbdde9cac26 2128 cmark-gfm_0.29.0.gfm.0-2.dsc
 93993e272ea1432ecfa1bcdd4203ae244f0bfe95 14464 
cmark-gfm_0.29.0.gfm.0-2.debian.tar.xz
 821b1e8879d5ab87828cf30122f9ee4b7a0e8575 9188 
cmark-gfm_0.29.0.gfm.0-2_amd64.buildinfo
Checksums-Sha256:
 2076046042ff1c22e17a9d210847b84990bc5a1992ebd0688630f06bbce81fc2 2128 
cmark-gfm_0.29.0.gfm.0-2.dsc
 6b9c9e5d71af73edec4d4a2047023492b6b2c68b3c5a50b89ef25c0ff5e65bad 14464 
cmark-gfm_0.29.0.gfm.0-2.debian.tar.xz
 2bae1f79c75172c95e02b6a5c6dec29e961eb82ecbb7a51ceaf049813a7c9f60 9188 
cmark-gfm_0.29.0.gfm.0-2_amd64.buildinfo
Files:
 d9bc1e36c151e561d8e32a3b92b2c4fc 2128 text optional 
cmark-gfm_0.29.0.gfm.0-2.dsc
 924bdeb2c0ba3c720c4f3ceba4aed46b 14464 text optional 
cmark-gfm_0.29.0.gfm.0-2.debian.tar.xz
 7f389b8595c782b0ba4a215580c38fa8 9188 text optional 
cmark-gfm_0.29.0.gfm.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEw4O3eCVWE9/bQJ2R2yIaaQAAABEFAl34XQ0ACgkQ2yIaaQAA
ABEiJQ//c2g0wsraEl/igRY8ikqjzQIJrqJE2RgNjz216q6Yk0FYVMhmnrwUXbTP
uhG01YkEEhgj7uUu3BJI4EDKkzLVQN8FflGm8Sc4k4sphrGcpZTzevLNCn2vQp4X
B249LN2NZQviB5tode5srSl3LA1t5t41NnSuKqoQZ4qEoJT3WfVjP5gDH1QTsNvO
eRQSQ7WhjNuv+WSw/9YXLQ4XhA8Ozhic69lykTUPHYsnyM6S31jhfQEkAuFaUMNE
ASnAL7gECGXWF8GzqYucRaT4xGP2lsquC3TaZnL5mlnsM/BTmbG/23MA/HA8/1oP
GSlRENiLp/OMeYvuZ9jN37iRqJc2ZFKsHMEXVad52cQYG9rO+35c0hmvXZ9Xsmvp
OoMXOndAAea3VkzAR9xN/Ip1jvpQWmgLMR3GlmFjUsu2cGOYl9kYLYEo3KlQpORw
8Dtu4ryCQapmnjnHb9auPgA8Ux7fX6SKR2x6kgF8PhDZCwgomGAdelscbimA8VQ+
Qk58OiOj/HfKx2wxoletNxG+sBZ0zQYQGQcujA7p8q61SM2DVqq63D+mz9nk9ZQZ
xQi7O4oFPAz7Wpu6dV6lex/qRHAHspDYvDIXvnqsL7p0KjIx+2PcQfSZO260krho
en24ws+s9uzQmWL/ejUC9MIvTzGXo8RD3FKf0YgmEWEfyGmwfeo=
=Q4cf
-END PGP SIGNATURE End Message ---

Bug#946858: marked as done (ruby-grib: Should this package be removed?)

[Debian Bug Tracking System]

Your message dated Tue, 17 Dec 2019 03:04:39 +
with message-id 
and subject line Bug#946858: fixed in ruby-grib 0.4.0-3
has caused the Debian Bug report #946858,
regarding ruby-grib: Should this package be removed?
to be marked as done.

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

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


-- 
946858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-grib
Severity: serious
Version: 0.4.0-2
X-Debbugs-CC: uwab...@gfd-dennou.org

Dear ruby-grib maintainers,

According to https://bugs.debian.org/932208 , one of the dependencies of ruby-
grib, grib-api, will be removed from Debian very soon. In this case, is the
package ruby-grib still relavent? Should we just have it removed from Debian?
Please evaluate the current status. If a removal is indeed necessary, please
consider filing a removal bug against FTP Masters.

Thanks and looking forward to your reply.

-- 
Regards,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: ruby-grib
Source-Version: 0.4.0-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 17 Dec 2019 10:58:13 +0900
Source: ruby-grib
Architecture: source
Version: 0.4.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Youhei SASAKI 
Closes: 946858
Changes:
 ruby-grib (0.4.0-3) unstable; urgency=medium
 .
   [ Utkarsh Gupta ]
   * Add salsa-ci.yml
   * Update d/ch
 .
   [ Youhei SASAKI ]
   * Use eccodes instead of grib_api (Closes: #946858)
   * d/control: update Vcs-{Git,Browser}. use salsa
   * d/control: Bump Standard Version 4.4.0
   * d/{control,compat}: Bump compat 12
   * d/watch: use gemwatch
   * d/copyright: fix insecure-copyright-format-uri
   * d/control: use debhelper-compat
Checksums-Sha1:
 515640e5c484489b9218db46b746953436488af7 2125 ruby-grib_0.4.0-3.dsc
 2f07dc4ec8d5af98a3fc7a6306cf322ec49d16cd 12164 ruby-grib_0.4.0-3.debian.tar.xz
 6c5489e7ffcf2aad0efadc3c3cdb02783133801a 10171 
ruby-grib_0.4.0-3_amd64.buildinfo
Checksums-Sha256:
 e0329204915126bd7c33325c89bd4376ea6ba4cc2c686d5d47a1a32387ca170b 2125 
ruby-grib_0.4.0-3.dsc
 4e1fb845d797d95b0fd8ec9b35d7f09ae4f1cfea030c3962c81a85e08016a2bf 12164 
ruby-grib_0.4.0-3.debian.tar.xz
 7e2cf1948a03e0c51bf70e05d596efa3c3897de9512ca9812efb11c08a39cc29 10171 
ruby-grib_0.4.0-3_amd64.buildinfo
Files:
 aa8e0a809f977604f38f37e838ff1eed 2125 ruby optional ruby-grib_0.4.0-3.dsc
 97997ee344a1163bc27d6a117f9c003f 12164 ruby optional 
ruby-grib_0.4.0-3.debian.tar.xz
 b217e18e6b55ff556d20b033bbe2451a 10171 ruby optional 
ruby-grib_0.4.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZqTqcE/iQFWNasLmk5TzVIkdfgcFAl34QJgACgkQk5TzVIkd
fgff6xAAo8XqUBQ6UjclQhsIC+2EgRalcdnshN5pagE0Kt+y45QRbdoYL3XKRhSU
c9a6dgOv4LelF4z7eKMaM9Jko4XE7ctijG1Va39f1W7qjs4zwwHjImvMsYrr03gP
7yEd8a2qUPpbcMofhdv3D9XbWmxX+wy9mN9VwsmaB85JaWws+2ZS3VzDrzafcR4j
Q3boeLG/+OqjskBb+GDIXYsw87k02q1BxWeVY7LmM8lNLsyREGB3g+d6gB2joYTX
bTG2CFKWkwayp3AbZfZ4afvnKzd59Ond8Qg916D3xUDvzwt6sEemdolentLA6n4P
Vpyuj54iPXS7IO5V1BWtXWhS0mJEHUzS0TexNAuRuICIlAum1+ZvTFiClFpiLAT0
6GhMwKdtzVELAoNpN4a5TlnKdgXxHTJhJJIpX6eSAGU4AVNGLDpg1Ekoyuwmw40H
7R0K8g1q0pzNNB/kfOcEkuu/ojXoiNyZDnjbqHk+y+V0Al06DSOMPvsFsVI32OEG
b2B6jgSER8TU73+t4lyIFEXIwqEFMRNAUtKI3Vuus4bgWdptvy1ZUU4Imzhz1N8A
WjAcuId4tkPxz99lKeNU6Fqwsu+BzSUckFvK7ECXusiqktSpDA/Xbs0NNrXJnlLm
fF8jdgEoButziRnIt7JQ5XOze0PdRt2xYvTroDnFAgvrkD7nNn8=
=rQih
-END PGP SIGNATURE End Message ---

Bug#941527: Bug #941527: marked as pending in matplotlib

[Sandro Tosi]

> It's marked for accept now.

many thanks!


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

Bug#945632: marked as done (debian-games: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 17 Dec 2019 01:49:09 +
with message-id 
and subject line Bug#945632: fixed in debian-games 3.1
has caused the Debian Bug report #945632,
regarding debian-games: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 17 Dec 2019 02:08:26 +0100
Source: debian-games
Architecture: source
Version: 3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Closes: 945632
Changes:
 debian-games (3.1) unstable; urgency=medium
 .
   * Drop python2-dev package because Python 2 will be removed from Debian.
 (Closes: #945632)
   * Declare compliance with Debian Policy 4.4.1.
   * Removed games: (Removed from Debian)
 - arcade/shootemup: balder2d
 - arcade: bubbros
 - arcade/shootemup: defendguin
 - puzzle/board: gnudoq
 - board: gpsshogi
 - card: holdingnuts
 - puzzle: magicor
 - card: pybridge
 - puzzle: pynagram
 - board: pyscrabble
 - typing: speedpad
 - board: tictactoe-ng
 - puzzle: xword
 - console: zivot
   * New games or engines:
 - chess: suggest crazywa
 - adventure: add glulxe
 - platform/arcade: add pekka-kana-2
 - simulation: suggest pmars
 - console/tetris: add termtris
 - toys: add tfortune and tfortunes
 - toys: add xsnow
Checksums-Sha1:
 cbc1497ef20b614118eea78c2f1b8d5cb8db3255 3832 

Bug#946882: blk-availability.service: may fail or unmount filesystems too soon

[Rob Leslie]

Package: lvm2
Version: 2.03.02-3
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

On systems upgraded from stretch and without the usrmerge package installed,
/sbin/blkdeactivate (ExecStop= of blk-availability.service) gives the
following error during system shutdown:

blkdeactivate[12003]: /sbin/blkdeactivate: line 345: /bin/sort: No such 
file or directory

Despite the error, I have not observed any adverse behavior.

However, on new installations or systems upgraded from stretch WITH the
usrmerge package installed, the error does not occur. Instead, filesystems
may be unmounted prematurely, for example those given as RequiresMountsFor=
in other units. I have observed data loss in this case where a required
mount was unmounted before the unit requiring it had properly saved its state
during shutdown.

I am not sure the best course of action to resolve this latter problem. Is it
necessary for blkdeactivate to be unmounting filesystems? Could the dependency
ordering be adjusted to avoid unmounting filesystems too soon?


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

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

Versions of packages lvm2 depends on:
ii  dmeventd  2:1.02.155-3
ii  dmsetup   2:1.02.155-3
ii  libaio1   0.3.112-3
ii  libblkid1 2.33.1-0.1
ii  libc6 2.28-10
ii  libdevmapper-event1.02.1  2:1.02.155-3
ii  libdevmapper1.02.12:1.02.155-3
ii  libreadline5  5.2+dfsg-3+b13
ii  libselinux1   2.8-1+b1
ii  libsystemd0   241-7~deb10u2
ii  libudev1  241-7~deb10u2
ii  lsb-base  10.2019051400

Versions of packages lvm2 recommends:
ii  thin-provisioning-tools  0.7.6-2.1

lvm2 suggests no packages.

-- Configuration Files:
/etc/lvm/lvm.conf changed [not included]

-- no debconf information

Bug#946837: vagrant: Does not work with virtualbox 6.1 from unstable

[Jeremy L. Gaddis]

A fix has been committed upstream:

  https://github.com/hashicorp/vagrant/commit/20ccf46

Bug#946881: translate-docformat: Please remove translate-docformat from Debian, package of questionable value

[Dimitri John Ledkov]

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.

Bug#946880: newt: Please switch from sgmtools-lite to docbook-utils

[Dimitri John Ledkov]

Source: newt
Version: 0.52.21-3
Severity: serious

Dear Maintainer,

sgmtools-lite is orphaned, abandoned upstream, python2 application to
be removed from Debian shortly. newt is one of the remaining packages
using it.

Please switch to docbook-utils and upload immediately to unstable.
Patch is attached.

Regards,

Dimitri.
diff -Nru newt-0.52.21/debian/changelog newt-0.52.21/debian/changelog
--- newt-0.52.21/debian/changelog   2019-09-01 16:59:14.0 +0100
+++ newt-0.52.21/debian/changelog   2019-12-17 00:39:20.0 +
@@ -1,3 +1,10 @@
+newt (0.52.21-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch from orphaned sgmltools-lite to docbook-utils.
+
+ -- Dimitri John Ledkov   Tue, 17 Dec 2019 00:39:20 +
+
 newt (0.52.21-3) unstable; urgency=medium
 
   * Move to Standards-Version: 4.4.0
diff -Nru newt-0.52.21/debian/control newt-0.52.21/debian/control
--- newt-0.52.21/debian/control 2019-09-01 16:59:14.0 +0100
+++ newt-0.52.21/debian/control 2019-12-17 00:39:09.0 +
@@ -7,7 +7,7 @@
 Standards-Version: 4.4.0
 Homepage: https://pagure.io/newt
 Build-Depends: debhelper-compat (= 12),
- sgmltools-lite, 
+ docbook-utils, 
  automake (>= 1.16),
  libslang2-dev  (>=2.0.4-2), 
  libpopt-dev,
diff -Nru newt-0.52.21/debian/libnewt-dev.doc-base 
newt-0.52.21/debian/libnewt-dev.doc-base
--- newt-0.52.21/debian/libnewt-dev.doc-base2019-09-01 16:59:14.0 
+0100
+++ newt-0.52.21/debian/libnewt-dev.doc-base2019-12-17 00:38:39.0 
+
@@ -1,4 +1,4 @@
-build-tree/*/tutorial/t1.html
+build-tree/*/tutorial/index.html
 build-tree/*/tutorial/x100.html
 build-tree/*/tutorial/x197.html  
 build-tree/*/tutorial/x223.html
diff -Nru newt-0.52.21/debian/rules newt-0.52.21/debian/rules
--- newt-0.52.21/debian/rules   2019-09-01 16:59:14.0 +0100
+++ newt-0.52.21/debian/rules   2019-12-17 00:37:24.0 +
@@ -53,7 +53,7 @@
 
 override_dh_auto_build:
dh_auto_build
-   sgmltools --backend html tutorial.sgml
+   docbook2html -o tutorial tutorial.sgml
ar cqv libnewt_pic.a shared/*.o
 
 override_dh_auto_install:

Bug#938554: spyne_2.13.11a0-0.1_source.changes REJECTED

[Russell Stuart]

On Mon, 2019-12-16 at 19:19 +0100, Bastian Germann wrote:
> Yes, I missed that. But maybe you have made up your mind now that
> spyne got auto-removed from testing.
> Isn't it better to have an alpha version in testing than no version
> at all?

As I said in my reply to the bug report, the "no version at all"
scenario seems unlikely to me even if Spyne for Python 3 doesn't get
released.  But it does seem like Spyne for Python 3 will be stable
before the bullseye deadlines hit. And I will upload it as soon as an I
am aware it has been released.

Regardless of what happens I use spyne in my day job, so I will
continue to package spyne for Debian.  Whether it ends up in Debian is
an open question, but I am a DD :)


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

Bug#935280: marked as done (gcc-h8300-hms: FTBFS on arm64)

[Debian Bug Tracking System]

Your message dated Mon, 16 Dec 2019 23:49:27 +
with message-id 
and subject line Bug#935280: fixed in gcc-h8300-hms 1:3.4.6+dfsg2-4.1
has caused the Debian Bug report #935280,
regarding gcc-h8300-hms: FTBFS on arm64
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.)


-- 
935280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:gcc-h8300-hms
version: 1:3.4.6+dfsg2-4
severity: serious
tags: ftbfs

Hi,

A binnmu of gcc-h8300-hms in unstable fails on arm64:

https://buildd.debian.org/status/package.php?p=gcc-h8300-hms

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: gcc-h8300-hms
Source-Version: 1:3.4.6+dfsg2-4.1

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

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

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

Debian distribution maintenance software
pp.
Dimitri John Ledkov  (supplier of updated gcc-h8300-hms 
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 23:36:24 +
Source: gcc-h8300-hms
Architecture: source
Version: 1:3.4.6+dfsg2-4.1
Distribution: unstable
Urgency: medium
Maintainer: Michael Tautschnig 
Changed-By: Dimitri John Ledkov 
Closes: 935280
Changes:
 gcc-h8300-hms (1:3.4.6+dfsg2-4.1) unstable; urgency=medium
 .
   [ Balint Reczey ]
   * Disable -fPIE on arm64 Closes: #935280
 .
   [ Matthias Klose ]
   * Fix build failure with -U_FORTIFY_SOURCE
 .
   [ Dimitri John Ledkov ]
   * Non-maintainer upload of Ubuntu delta.
Checksums-Sha1:
 3672de6bc67f18219e9edfc12f5e33741a239f0a 1861 gcc-h8300-hms_3.4.6+dfsg2-4.1.dsc
 e99f0f796b810565f8b2a78951cbaff0d303866b 58644 
gcc-h8300-hms_3.4.6+dfsg2-4.1.debian.tar.xz
 09488448b54ef84588339c359afd2627327525c3 6875 
gcc-h8300-hms_3.4.6+dfsg2-4.1_source.buildinfo
Checksums-Sha256:
 d5bfb33ece91922ae24c1fc37c46d9ea43f37733e8a07c079cfd3843be402e8c 1861 
gcc-h8300-hms_3.4.6+dfsg2-4.1.dsc
 8fd86c826cdc3d4b567d65a656ff799e73ee2f013c375fd590e1cf4482736f49 58644 
gcc-h8300-hms_3.4.6+dfsg2-4.1.debian.tar.xz
 2936b9ac9bd9036ef3ece4caed7696eeb7da0eaf33c9fbbd51a42f37a6c88a3b 6875 
gcc-h8300-hms_3.4.6+dfsg2-4.1_source.buildinfo
Files:
 78a48fae6c312ddb5af954d73dacf350 1861 devel extra 
gcc-h8300-hms_3.4.6+dfsg2-4.1.dsc
 c84560e27d1df0953187991e509abf5e 58644 devel extra 
gcc-h8300-hms_3.4.6+dfsg2-4.1.debian.tar.xz
 41a7f78697bef211809b9f3e9155a35e 6875 devel extra 
gcc-h8300-hms_3.4.6+dfsg2-4.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE7iQKBSojGtiSWEHXm47ISdXvcO0FAl34FX8ACgkQm47ISdXv
cO2eRQ/9GBcESfVi8fIIj8l8XGzy8YqhqDFp1s/3voxuWVl6d7rp2QA2g4YS9nzL
O+r/MYha35ht1B0XRU5KOx9FypNzOUropJ/aATQq9nB3VQHWbSyVN03hECxjCL/S
fB/mYN1yipMOuAZwF5ESC5Hb/Y+xTQNWV8WZOWshHhbE498kMgY9LRDO3EF7i5DP
BvArKeOmwFfxDs49oOENPuluCNn8vJoeI6kg63OI5+578tGr3lITmNC4wcd9HVHp
sLj4EvYHr3FaCvNAfuiefU/o4Aygi2EAbZTDfXRb55fInWhepsjhrFgdTKl/NJgU
BxFfGfADkfnsjOWoJGetJ1fxOAY/Sd6oR6UacbJ7GyTz684NErNiAvTKjyBOWy1B
neAkXoORfFhCG5aQ/ZQsbfUEwAyKpv5KX3qkko+ANKe+NJbFraCSVuYUqwD8Mdej
LNxWP5AnuaQjNN5wqRe4aoySxGDHuQgy32/EWiIcM3wAA70o9SoVTE8jH3BmXYO0
fXDSWKCtXfQYN0Jb3OsX//elspRVZl9DjSm+Wx12bbhXJkNiKpNjnDrw4cIr1HnQ
cKD99xgP1SxYy3txwmfTaAYCo6JXR+bOjYq7ZGcbgL14EgMIMen+Rk8cZJqOdHyR
SPAfW91rQGhplJl60B7G6v7nSH7QZvW4FZFvAgbC2OaMYYpcvyg=
=p653
-END PGP SIGNATURE End Message ---

Bug#943600: [Pkg-pascal-devel] Bug#943600: Bug#943600: Bug#943600: lazarus autopkgtest intermittedly fails due to EAccessViolation: Access violation

[Graham Inggs]

Hi Abou

2.0.6+dfsg-3, still fails intermittently on armhf in Ubuntu [1].
Did you try debugging on armhf in Debian?

Regards
Graham


[1] http://autopkgtest.ubuntu.com/packages/l/lazarus/focal/armhf

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

[Johann Glaser]

Hi Abou!

Am Montag, den 16.12.2019, 22:31 +0100 schrieb Abou Al Montacir:
> Hi Johann,
>
> Can you please provide the following information
>
> grep laz /var/lib/dpkg/diversions
>
> /var/lib/dpkg/info/lazarus-src-2.0.preinst
> /var/lib/dpkg/info/lazarus-src-2.0.postrm

Thanks for your help!

Please find three files attached.

> What package manager are you using (apt, aptitude, ...)?

I'm using "aptitude".

Bye
  Hansi

/usr/lib/lazarus/2.0.2/components/rtticontrols/runtimetypeinfocontrols.lpk
/usr/lib/lazarus/2.0.2/components/rtticontrols/runtimetypeinfocontrols.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/datetimectrls/datetimectrls.lpk
/usr/lib/lazarus/2.0.2/components/datetimectrls/datetimectrls.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/lazreport/source/addons/DialogControls/lr_dialogdesign.lpk
/usr/lib/lazarus/2.0.2/components/lazreport/source/addons/DialogControls/lr_dialogdesign.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/lazreport/source/addons/addfunction/lr_add_function.lpk
/usr/lib/lazarus/2.0.2/components/lazreport/source/addons/addfunction/lr_add_function.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/sparta/dockedformeditor/sparta_dockedformeditor.lpk
/usr/lib/lazarus/2.0.2/components/sparta/dockedformeditor/sparta_dockedformeditor.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/lazsvnpkg/lazsvnpkg.lpk
/usr/lib/lazarus/2.0.2/components/lazsvnpkg/lazsvnpkg.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/fpcunit/console/fpcunitconsolerunner.lpk
/usr/lib/lazarus/2.0.2/components/fpcunit/console/fpcunitconsolerunner.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/lcl/lclbase.lpk
/usr/lib/lazarus/2.0.2/lcl/lclbase.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/fpreport/design/lazfpreportdesign.lpk
/usr/lib/lazarus/2.0.2/components/fpreport/design/lazfpreportdesign.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/macfiles/macosfiles.lpk
/usr/lib/lazarus/2.0.2/components/macfiles/macosfiles.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/fpcunit/fpcunittestrunner.lpk
/usr/lib/lazarus/2.0.2/components/fpcunit/fpcunittestrunner.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/lazdebuggers/lazdebuggerfpgdbmi/lazdebuggerfpgdbmi.lpk
/usr/lib/lazarus/2.0.2/components/lazdebuggers/lazdebuggerfpgdbmi/lazdebuggerfpgdbmi.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/sqlite/sqlitelaz.lpk
/usr/lib/lazarus/2.0.2/components/sqlite/sqlitelaz.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/favorites/favorites.lpk
/usr/lib/lazarus/2.0.2/components/favorites/favorites.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/lazreport/source/lazreport.lpk
/usr/lib/lazarus/2.0.2/components/lazreport/source/lazreport.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/lazreport/source/addons/ZeosDB/lr_zeosdb.lpk
/usr/lib/lazarus/2.0.2/components/lazreport/source/addons/ZeosDB/lr_zeosdb.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/aggpas/lazarus/aggpaslcl.lpk
/usr/lib/lazarus/2.0.2/components/aggpas/lazarus/aggpaslcl.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/googleapis/lazgoogleapis.lpk
/usr/lib/lazarus/2.0.2/components/googleapis/lazgoogleapis.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/sqlite/sqlite3laz.lpk
/usr/lib/lazarus/2.0.2/components/sqlite/sqlite3laz.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/examples/dockmanager/package/easydockmgr.lpk
/usr/lib/lazarus/2.0.2/examples/dockmanager/package/easydockmgr.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/messagecomposer/messagecomposerpkg.lpk
/usr/lib/lazarus/2.0.2/components/messagecomposer/messagecomposerpkg.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/lazdebuggers/lazdebuggerlldb/lazdebuggerlldb.lpk
/usr/lib/lazarus/2.0.2/components/lazdebuggers/lazdebuggerlldb/lazdebuggerlldb.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/fpreport/lclfpreport.lpk
/usr/lib/lazarus/2.0.2/components/fpreport/lclfpreport.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/education/educationlaz.lpk
/usr/lib/lazarus/2.0.2/components/education/educationlaz.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/tachart/aggpas/tachartaggpas.lpk
/usr/lib/lazarus/2.0.2/components/tachart/aggpas/tachartaggpas.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/lazreport/source/addons/lrOfficeImport/lr_officeimport.lpk
/usr/lib/lazarus/2.0.2/components/lazreport/source/addons/lrOfficeImport/lr_officeimport.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/projecttemplates/projtemplates.lpk
/usr/lib/lazarus/2.0.2/components/projecttemplates/projtemplates.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/sparta/toolsapi/sparta_toolsapi.lpk
/usr/lib/lazarus/2.0.2/components/sparta/toolsapi/sparta_toolsapi.lpk.orig
lazarus-src-2.0
/usr/lib/lazarus/2.0.2/components/sparta/generics/sparta_generics.lpk

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

[Abou Al Montacir]

Hi Johann,
Can you please  provide the following information
grep laz /var/lib/dpkg/diversions
/var/lib/dpkg/info/lazarus-src-2.0.preinst/var/lib/dpkg/info/lazarus-src-
2.0.postrm
What package manager are you using (apt, aptitude, ...)?
On Mon, 2019-12-16 at 01:22 +0100, Johann Glaser wrote:
> Hi!
> The problem is still there for lazarus-src-2.0_2.0.6+dfsg-3_all.deb. Itwas
> actually also there for 2.0.6+dfsg-2 as well as 2.0.6+dfsg-1.
> The only thing which helps is forcing it, but it gives a huge load ofwarnings:
> # dpkg -i --force-all /var/cache/apt/archives/lazarus-src-2.0_2.0.6+dfsg-
> 3_all.deb(Reading database ... 528262 files and directories currently
> installed.)Preparing to unpack .../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) ...dpkg:
> warning: overriding problem because --force enabled:dpkg: warning: trying to
> overwrite '/usr/lib/lazarus/2.0.6/components/IdeInspector/ideinspector.lpk',
> which is also in package lcl-units-2.0 2.0.6+dfsg-3dpkg: warning: overriding
> problem because --force enabled:dpkg: warning: trying to overwrite
> '/usr/lib/lazarus/2.0.6/components/IdeLazLogger/idelazlogger.lpk', which is
> also in package lcl-units-2.0 2.0.6+dfsg-3dpkg: warning: overriding problem
> because --force enabled:dpkg: warning: trying to overwrite
> '/usr/lib/lazarus/2.0.6/components/PascalScript/Source/pascalscript.lpk',
> which is also in package lcl-units-2.0 2.0.6+dfsg-3dpkg: warning: overriding
> problem because --force enabled:dpkg: warning: trying to overwrite
> '/usr/lib/lazarus/2.0.6/components/PascalScript/Source/pascalscriptfcl.lpk',
> which is also in package lcl-units-2.0 2.0.6+dfsg-3dpkg: warning: overriding
> problem because --force enabled:dpkg: warning: trying to overwrite
> '/usr/lib/lazarus/2.0.6/components/aarre/src/aarrebase.lpk', which is also in
> package lcl-units-2.0 2.0.6+dfsg-3dpkg: warning: overriding problem because --
> force enabled:dpkg: warning: trying to overwrite
> '/usr/lib/lazarus/2.0.6/components/activex/LazActiveX.lpk', which is also in
> package lcl-units-2.0 2.0.6+dfsg-3dpkg: warning: overriding problem because --
> force enabled:dpkg: warning: trying to overwrite
> '/usr/lib/lazarus/2.0.6/components/aggpas/lazarus/aggpaslcl.lpk', which is
> also in package lcl-units-2.0 2.0.6+dfsg-3dpkg: warning: overriding problem
> because --force enabled:dpkg: warning: trying to overwrite
> '/usr/lib/lazarus/2.0.6/components/anchordocking/anchordocking.lpk', which is
> also in package lcl-units-2.0 2.0.6+dfsg-3dpkg: warning: overriding problem
> because --force enabled:dpkg: warning: trying to overwrite
> '/usr/lib/lazarus/2.0.6/components/anchordocking/design/anchordockingdsgn.lpk'
> , which is also in package lcl-units-2.0 2.0.6+dfsg-3dpkg: warning: overriding
> problem because --force enabled:dpkg: warning: trying to overwrite
> '/usr/lib/lazarus/2.0.6/components/cairocanvas/cairocanvas_pkg.lpk', which is
> also in package lcl-units-2.0 2.0.6+dfsg-3dpkg: warning: overriding problem
> because --force enabled:dpkg: warning: trying to overwrite
> '/usr/lib/lazarus/2.0.6/components/chmhelp/packages/help/lhelpcontrolpkg.lpk',
> which is also in package lcl-units-2.0 2.0.6+dfsg-3dpkg: warning: overriding
> problem because --force enabled:dpkg: warning: trying to overwrite
> '/usr/lib/lazarus/2.0.6/components/chmhelp/packages/idehelp/chmhelppkg.lpk',
> which is also in package lcl-units-2.0 2.0.6+dfsg-3dpkg: warning: overriding
> problem because --force enabled:dpkg: warning: trying to overwrite
> '/usr/lib/lazarus/2.0.6/components/codetools/codetools.lpk', which is also in
> package lcl-units-2.0 2.0.6+dfsg-3dpkg: warning: overriding problem because --
> force enabled:dpkg: warning: trying to overwrite
> '/usr/lib/lazarus/2.0.6/components/codetools/ide/cody.lpk', which is also in
> package lcl-units-2.0 2.0.6+dfsg-3dpkg: warning: overriding problem because --
> force enabled:dpkg: warning: trying to overwrite
> '/usr/lib/lazarus/2.0.6/components/compilers/c/lazc.lpk', which is also in
> package lcl-units-2.0 2.0.6+dfsg-3dpkg: warning: overriding problem because --
> force enabled:dpkg: warning: trying to overwrite
> '/usr/lib/lazarus/2.0.6/components/customdrawn/customdrawn.lpk', which is also
> in package lcl-units-2.0 2.0.6+dfsg-3dpkg: warning: overriding problem because
> --force enabled:dpkg: warning: trying to overwrite
> '/usr/lib/lazarus/2.0.6/components/customform/demo/appforms.lpk', which is
> also in package lcl-units-2.0 2.0.6+dfsg-3dpkg: warning: overriding problem
> because --force enabled:dpkg: warning: trying to overwrite
> '/usr/lib/lazarus/2.0.6/components/customform/lazcustforms.lpk', which is also
> in package lcl-units-2.0 2.0.6+dfsg-3dpkg: warning: overriding problem because
> --force enabled:dpkg: warning: trying to overwrite
> '/usr/lib/lazarus/2.0.6/components/daemon/lazdaemon.lpk', which is also in
> package lcl-units-2.0 2.0.6+dfsg-3dpkg: warning: overriding problem because --
> 

Bug#946862: marked as done (fluidsynth-dssi FTBFS after libfluidsynth update)

[Debian Bug Tracking System]

Your message dated Mon, 16 Dec 2019 21:19:10 +
with message-id 
and subject line Bug#946862: fixed in fluidsynth-dssi 1.0.0-7
has caused the Debian Bug report #946862,
regarding fluidsynth-dssi FTBFS after libfluidsynth update
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.)


-- 
946862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fluidsynth-dssi
Version: 1.0.0-6
Severity: serious
Tags: ftbfs
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

Your package is part of the libfluidsynth2 transition, so I scheduled
binNMU's. However, your package FTBFS on all architectures.

Please fix your package.

Paul

https://buildd.debian.org/status/package.php?p=fluidsynth-dssi

Tail of log for fluidsynth-dssi on amd64:

  870 | fluid_synth_nwrite_float(fsd_synth.fluid_synth, burst_size,
  | ^~~~
In file included from /usr/include/fluidsynth.h:97,
 from fluidsynth-dssi.c:43:
/usr/include/fluidsynth/synth.h:268:37: note: declared here
  268 | FLUID_DEPRECATED FLUIDSYNTH_API int 
fluid_synth_nwrite_float(fluid_synth_t *synth, int len,
  | ^~~~
make[3]: *** [Makefile:365: fluidsynth_dssi_la-fluidsynth-dssi.lo] Error 1
make[3]: Leaving directory '/<>/src'
make[2]: *** [Makefile:269: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:199: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:6: build-arch] Error 255


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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl332YwACgkQnFyZ6wW9
dQorXQgAwBT7pieOvEl0YgXqTuBtMSj/D5rtyQ3rUZf4d+35nQWQGlYlGRjyJY2o
BMDIU4xkB8GvVhVDRScTcPTpLIrrOLg6nh7pMGrfws/Mh2EvVYs/DH+qxjbjzDLL
Zl/5gmY+vz4CBs8+hvM/zro5t8v67PWd3S+rggPEEwQeJJil1TR51qLMo1vbfBkI
Eh4le8Dj088fp0DftQbrQtdQ44ZcMWTl1xTQkSTW/b7ZycQ10vMWyRPWNUHUKqLn
SpRS62gMdXNm5ysE7RYU/JeGzf9EZeJ4TydK/a8PvBJ7uQdryZ4Wl2bgKYia460y
my9r8U4Z7VJFJ4dXX/kcoHx4VPpOJA==
=ftxY
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: fluidsynth-dssi
Source-Version: 1.0.0-7

We believe that the bug you reported is fixed in the latest version of
fluidsynth-dssi, 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.
Sebastian Ramacher  (supplier of updated fluidsynth-dssi 
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 21:53:08 +0100
Source: fluidsynth-dssi
Architecture: source
Version: 1.0.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Closes: 946862
Changes:
 fluidsynth-dssi (1.0.0-7) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Team upload.
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Felipe Sateler ]
   * Change maintainer address to debian-multime...@lists.debian.org
 .
   [ Ondřej Nový ]
   * d/watch: Use https protocol
 .
   [ Olivier Humbert ]
   * Add icon
   * Update fluidsynth-dssi.desktop (add FR comment & icon)
   * Install icon & desktop files
   * Update copyright (add myself)
   * Update changelog (remove 1 empty line)
 .
   [ Sebastian Ramacher ]
   * debian/patches: Fix build with new version of fluidsynth (Closes: #946862)
   * debian/: Bump to debhelper compat 12
   * debian/control: Bump Standards-Version
   * debian/copyright:
 - Use versioned copyright format URI.
 - Update copyright file header to use current field names

Processed: Bug#946862 marked as pending in fluidsynth-dssi

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #946862 [src:fluidsynth-dssi] fluidsynth-dssi FTBFS after libfluidsynth 
update
Added tag(s) pending.

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

Bug#946862: marked as pending in fluidsynth-dssi

[Sebastian Ramacher]

Control: tag -1 pending

Hello,

Bug #946862 in fluidsynth-dssi 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/multimedia-team/fluidsynth-dssi/commit/e8c69f0ea84a2ceaf778d231cede2f4f1d9ad017


Fix build with new version of fluidsynth

Closes: #946862


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/946862

Processed: found 946797 in 1.929+deb9u3, found 946797 in 2.10.65+deb10u2, found 946797 in 2.11.9

[Debian Bug Tracking System]

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

> found 946797 1.929+deb9u3
Bug #946797 {Done: Holger Levsen } [debian-edu-config] 
debian-edu-config: kadm5.acl should set proper rights for users
Marked as found in versions debian-edu-config/1.929+deb9u3.
> found 946797 2.10.65+deb10u2
Bug #946797 {Done: Holger Levsen } [debian-edu-config] 
debian-edu-config: kadm5.acl should set proper rights for users
Marked as found in versions debian-edu-config/2.10.65+deb10u2.
> found 946797 2.11.9
Bug #946797 {Done: Holger Levsen } [debian-edu-config] 
debian-edu-config: kadm5.acl should set proper rights for users
Marked as found in versions debian-edu-config/2.11.9.
> thanks
Stopping processing here.

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

Bug#944743: marked as done (jupyter-notebook: systemd user unit enabled by default, despite per-system TCP port)

[Debian Bug Tracking System]

Your message dated Mon, 16 Dec 2019 20:35:03 +
with message-id 
and subject line Bug#944743: fixed in jupyter-notebook 6.0.0-2
has caused the Debian Bug report #944743,
regarding jupyter-notebook: systemd user unit enabled by default, despite 
per-system TCP port
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.)


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

The package now seems to enable the jupyter-notebook.service user unit
by default (I think this has changed?). Due to how Debian gdm3 is
packaged, this means also starting a server for the Debian-gdm user.

Since the service listens on a TCP port, the usefulness of this default
seems questionable at best. Only one server can use the default port,
and due to the GDM issue even machines with a single human user can
have two distinct user systemd sessions. If you can't rely on the port,
no static URL will work in a browser. If you add a method to query the
right port, you could just as well start the unit at that point.
--- End Message ---
--- Begin Message ---
Source: jupyter-notebook
Source-Version: 6.0.0-2

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

Debian distribution maintenance software
pp.
Gordon Ball  (supplier of updated jupyter-notebook 
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 19:56:28 +
Source: jupyter-notebook
Architecture: source
Version: 6.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Gordon Ball 
Closes: 944743
Changes:
 jupyter-notebook (6.0.0-2) unstable; urgency=medium
 .
   * Remove postinst and postrm logic for handling merged notebook JSON config
 like /etc/jupyter/nbconfig/notebook in favour of dropping files in eg,
 /etc/jupyter/nbconfig/notebook.d/, which should be simpler and more
 robust. Accordingly, add breaks against the last version of ipywidgets
 which used the old mechanism.
   * Update build paths for node-react and version dependency after install
 location was moved.
   * Don't automatically enable the systemd user unit (Closes: #944743);
 incorrectly enabled instances for non-interactive users can be disabled
 with `systemctl --user --global disable jupyter-notebook`
Checksums-Sha1:
 200ecea4789d54836497c7789c576e5b11e86d5f 3516 jupyter-notebook_6.0.0-2.dsc
 4067e5084b83c049b8052837337765732e0f92d3 58624 
jupyter-notebook_6.0.0-2.debian.tar.xz
 04953150bf122e360829ec5b58e3b4a0e8cc741e 19785 
jupyter-notebook_6.0.0-2_amd64.buildinfo
Checksums-Sha256:
 4ffc606e98eb8701c47ff14ba944d3642ad81b5cfd4997991eaffa637db24c10 3516 
jupyter-notebook_6.0.0-2.dsc
 e8411f0c6478ff012a840ffaee1951192fd061cd26657af56f9cb5f01b171b8a 58624 
jupyter-notebook_6.0.0-2.debian.tar.xz
 dc7c5626709e9d326f524bf2d000ab20853e07aa1935f6ba05fca4b2504c8c12 19785 
jupyter-notebook_6.0.0-2_amd64.buildinfo
Files:
 15b2721e64438fa6da9d6ff039c8ffbf 3516 python optional 
jupyter-notebook_6.0.0-2.dsc
 3b5574966c56662003117303c210569b 58624 python optional 
jupyter-notebook_6.0.0-2.debian.tar.xz
 ed2e99e923de22eea8278292f8e5bee3 19785 python optional 
jupyter-notebook_6.0.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE6PwpXIa418BJ+Xuno12v+60p6N4FAl335lMACgkQo12v+60p
6N4n+A//TZWhL4TLoPWLW+zctLysrKC/XnVQUb/Q9eBk6RC/X1MwVg3lGLGwR+Ng
k+R5cz17q4o1xnWFbVd29bdATnlwzXMHY1qIJ0QxRx8jHnNnlvwsbkeGkdY0CVM5
NkTT+a6nGxBkGltUSGviLel4qjMeDvXMf3WGW2B85ICUjEpA/cMaONVfA54noBDe
+kPzNSf7wi+am3pgsz3J9sm/NA6oDmzp7OQedO9X5/QTqzPqn4Bt6f8eswmdySNv
9+2R7t9Ku0nSO4JAmPAHZXLuIhneV1ZGXELVxp6AB6Mp6h1qM564aR9ISQLvm4g7
iMq7f5svjmu0PkF6z6iXMJYVgYmZlxV+uuFa861i4iDYX6jUdNscZBOlfo1QqZui
3jGw9BlcB6h5LNKItpyeQtUYaA+XC46W0fJYz/l1j7rSfD2YsFIYirVEetNoyn7p
lGXfBE9SdoU4r1Bq7bcceAVba67MM5yAmEpDxWf/3i/vkHY5spWjJDfRTG78K7sg
TFHYipdQaLdGAZRr2xM2ysGDCv3mvQWJOAys0ayM1Yia3B3viLhfSEvIcdGbMRBK

Bug#946865: libvncserver-dev: missing Depends on libsasl2-dev

[Sebastian Ramacher]

Package: libvncserver-dev
Version: 0.9.12+dfsg-4
Severity: serious

libvncserver-dev is missing a dependency on libsasl2-dev as can be seen
from the recent build of vlc:
| In file included from access/vnc.c:44:
| /usr/include/rfb/rfbclient.h:57:10: fatal error: sasl/sasl.h: No such file or 
directory
|57 | #include 
|   |  ^
| compilation terminated.

Cheers

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (650, 'unstable-debug'), (650, 'unstable'), (601, 'testing'), 
(600, 'experimental-debug'), (600, 'buildd-unstable'), (600, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages libvncserver-dev depends on:
ii  libgnutls28-dev3.6.11.1-2
ii  libjpeg-dev1:1.5.2-2
ii  libjpeg62-turbo-dev [libjpeg-dev]  1:1.5.2-2+b1
ii  libvncclient1  0.9.12+dfsg-4
ii  libvncserver1  0.9.12+dfsg-4
ii  zlib1g-dev 1:1.2.11.dfsg-1+b1

libvncserver-dev recommends no packages.

libvncserver-dev suggests no packages.

-- no debconf information

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#946863: freewheeling FTBFS after libfluidsynth update

[Paul Gevers]

Source: freewheeling
Version: 0.6.4-1
Severity: serious
Tags: ftbfs
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

Your package is part of the libfluidsynth2 transition, so I scheduled
binNMU's. However, your package FTBFS on all architecutes.

Please fix your package.

Paul

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

Tail of log for freewheeling on amd64:

  177 |   while (fluid_sfont_iteration_next(curfont, ))
  |  ^~
In file included from /usr/include/fluidsynth.h:95,
 from fweelin_fluidsynth.h:23,
 from fweelin_fluidsynth.cc:34:
/usr/include/fluidsynth/types.h:40:16: note: forward declaration of 
‘fluid_sfont_t’ {aka ‘struct _fluid_sfont_t’}
   40 | typedef struct _fluid_sfont_t fluid_sfont_t;/**< 
SoundFont */
  |^~
make[2]: *** [Makefile:464: fweelin_fluidsynth.o] Error 1
make[2]: *** Waiting for unfinished jobs
make[2]: Leaving directory '/<>/src'
make[1]: *** [Makefile:344: all-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make -j4 returned exit code 2
make: *** [debian/rules:9: build-arch] Error 255



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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl332jsACgkQnFyZ6wW9
dQoTbAgA0JAxUNuYYm5UE40iJL4eIGd31L5HJmhyMiIddZS4vF4QimWrBXmI6cul
Iy4qR9+os4h0DSt/t3l3hT97RJstqIuVwONggYrmrU+Qe2I5aotaOfv7FsX2n4LA
Q3Qh69ThD00pYcociuN2qBl2JeXsuagB6FEOSNWskdtW8ZLbGWakBjNEaHN1dxdg
JG+PxJmgP3uHFF7eG6nBeWaSppl0EfPOCwk6tMCx8UysrHvRFBosBO2r3+8N1q2A
GmRIm2o3jNwtWli630tO2KAH5wmOe0kszJ+J2RQCffQPURXlTL8H0tetfZKx3+gn
k2iIZJuzmF58RVgBMdiGVvRKuW9S0Q==
=aXr0
-END PGP SIGNATURE-

Bug#946862: fluidsynth-dssi FTBFS after libfluidsynth update

[Paul Gevers]

Source: fluidsynth-dssi
Version: 1.0.0-6
Severity: serious
Tags: ftbfs
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

Your package is part of the libfluidsynth2 transition, so I scheduled
binNMU's. However, your package FTBFS on all architectures.

Please fix your package.

Paul

https://buildd.debian.org/status/package.php?p=fluidsynth-dssi

Tail of log for fluidsynth-dssi on amd64:

  870 | fluid_synth_nwrite_float(fsd_synth.fluid_synth, burst_size,
  | ^~~~
In file included from /usr/include/fluidsynth.h:97,
 from fluidsynth-dssi.c:43:
/usr/include/fluidsynth/synth.h:268:37: note: declared here
  268 | FLUID_DEPRECATED FLUIDSYNTH_API int 
fluid_synth_nwrite_float(fluid_synth_t *synth, int len,
  | ^~~~
make[3]: *** [Makefile:365: fluidsynth_dssi_la-fluidsynth-dssi.lo] Error 1
make[3]: Leaving directory '/<>/src'
make[2]: *** [Makefile:269: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:199: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:6: build-arch] Error 255


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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl332YwACgkQnFyZ6wW9
dQorXQgAwBT7pieOvEl0YgXqTuBtMSj/D5rtyQ3rUZf4d+35nQWQGlYlGRjyJY2o
BMDIU4xkB8GvVhVDRScTcPTpLIrrOLg6nh7pMGrfws/Mh2EvVYs/DH+qxjbjzDLL
Zl/5gmY+vz4CBs8+hvM/zro5t8v67PWd3S+rggPEEwQeJJil1TR51qLMo1vbfBkI
Eh4le8Dj088fp0DftQbrQtdQ44ZcMWTl1xTQkSTW/b7ZycQ10vMWyRPWNUHUKqLn
SpRS62gMdXNm5ysE7RYU/JeGzf9EZeJ4TydK/a8PvBJ7uQdryZ4Wl2bgKYia460y
my9r8U4Z7VJFJ4dXX/kcoHx4VPpOJA==
=ftxY
-END PGP SIGNATURE-

Bug#946861: buzztrax FTBFS after libfluidsynth update

[Paul Gevers]

Source: buzztrax
Version: 0.10.2-6
Severity: serious
Tags: ftbfs
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

Your package is part of the libfluidsynth2 transition, so I scheduled
binNMU's. However, your package FTBFS on all architecutes.

Please fix your package.

Paul

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

Tail of log for buzztrax on amd64:

/usr/include/fluidsynth/settings.h:182:54: note: expected 
‘fluid_settings_foreach_t’ {aka ‘void (*)(void *, const char *, int)’} but 
argument is of type ‘void (*)(void *, char *, int)’
  182 | fluid_settings_foreach_t func);
  | ~^~~~
src/gst/fluidsynth/fluidsynth.c:877:11: error: ‘FLUID_CHORUS_DEFAULT_TYPE’ 
undeclared (first use in this function)
  877 |   FLUID_CHORUS_DEFAULT_TYPE,
  |   ^
src/gst/fluidsynth/fluidsynth.c:877:11: note: each undeclared identifier is 
reported only once for each function it appears in
make[3]: *** [Makefile:6261: 
src/gst/fluidsynth/libgstfluidsynth_la-fluidsynth.lo] Error 1
make[3]: Leaving directory '/<>'
make[2]: *** [Makefile:7283: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:3016: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:13: build-arch] Error 255



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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3314gACgkQnFyZ6wW9
dQoc3Qf8Cs6z53jnMcLCT6YJ+JX0OXjkdPCKwW97EovwR7EZLvwVyvVkIsuioHUC
9Loa2V5pIuqjYGPzpTIEWZsRO3GSxwkMq/amdIMsH7IlPaxv/jJtxEimJqjR5CS4
yvOCNPe9fzfDJ5+7su2dRuICApyBXdlGjnYT8G4kld5fvQHuxohgBJboc/Rutqqt
ucjWl5fvL2QytURwLE6ZaRaQQRekXI2enWea3xm/FR6ucrGbFX29YChexf5CNVPe
lcM89csPpaXWmOdMUIRK5tw3aOhulBPzcTUvZ2AUltnpjU0yP9Kx+K5G9HmTtA3b
TsBMvRW5LbQKuzSZYC26oIFmvthIiQ==
=1D4P
-END PGP SIGNATURE-

Bug#945827: marked as done (ssvnc: fix libvncclient bundle security issues)

[Debian Bug Tracking System]

Your message dated Mon, 16 Dec 2019 19:05:30 +
with message-id 
and subject line Bug#945827: fixed in ssvnc 1.0.29-5
has caused the Debian Bug report #945827,
regarding ssvnc: fix libvncclient bundle security issues
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.)


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

Package: ssvnc
Severity: grave
X-Debbugs-CC: t...@security.debian.org
Version: 1.0.29-4
Tags: security patch

The following vulnerabilites have recently been discovered in ssvnc's  
bundled (and rather old) version of libvncclient code:


CVE-2018-20020[0]:
| LibVNC before commit 7b1ef0ffc4815cab9a96c7278394152bdc89dc4d contains
| heap out-of-bound write vulnerability inside structure in VNC client
| code that can result remote code execution

CVE-2018-20021[1]:
| LibVNC before commit c3115350eb8bb635d0fdb4dbbb0d0541f38ed19c contains
| a CWE-835: Infinite loop vulnerability in VNC client code.
| Vulnerability allows attacker to consume excessive amount of resources
| like CPU and RAM

CVE-2018-20022[2]:
| LibVNC before 2f5b2ad1c6c99b1ac6482c95844a84d66bb52838 contains
| multiple weaknesses CWE-665: Improper Initialization vulnerability in
| VNC client code that allows attacker to read stack memory and can be
| abuse for information disclosure. Combined with another vulnerability,
| it can be used to leak stack memory layout and in bypassing ASLR

CVE-2018-20024[3]:
| LibVNC before commit 4a21bbd097ef7c44bb000c3bd0907f96a10e4ce7 contains
| null pointer dereference in VNC client code that can result DoS.

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

As I have worked on a fix for these issues for ssvnc in Debian jessie  
LTS (with my LTS team member hat on, that is), I have attached the  
proposed .debdiff (that applies against ssvnc 1.0.29-2) to this mail.  
It should be easy to forward-port the security fixes to ssvnc in  
stretch, buster and testing/unstable.


Regarding the upload to jessie LTS, please let me know, if I can  
proceed with the upload asap or if you want to take a closer look at  
the proposed changeset. Thanks.


Regards,

Mike

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-20020
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20020
[1] https://security-tracker.debian.org/tracker/CVE-2018-20021
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20021
[2] https://security-tracker.debian.org/tracker/CVE-2018-20022
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20022
[3] https://security-tracker.debian.org/tracker/CVE-2018-20024
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20024


--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

diff -Nru ssvnc-1.0.29/debian/changelog ssvnc-1.0.29/debian/changelog
--- ssvnc-1.0.29/debian/changelog   2011-11-11 08:11:09.0 +0100
+++ ssvnc-1.0.29/debian/changelog   2019-11-29 12:15:33.0 +0100
@@ -1,3 +1,15 @@
+ssvnc (1.0.29-2+deb8u1) jessie-security; urgency=medium
+
+  * Non-maintainer upload by the LTS team.
+  * Porting of libvncclient security patches:
+- CVE-2018-20020: heap out-of-bound write vulnerability inside structure
+  in VNC client code.
+- CVE-2018-20021: CWE-835: Infinite loop vulnerability in VNC client code.
+- CVE-2018-20022: CWE-665: Improper Initialization vulnerability.
+- CVE-2018-20024: null pointer dereference that can result DoS.
+
+ -- Mike Gabriel   Fri, 29 Nov 2019 12:15:33 +0100
+
 ssvnc (1.0.29-2) unstable; urgency=low
 
   * Also get CPPFLAGS from dpkg-buildflags. Pass it as EXTRA_DEFINES to
diff -Nru ssvnc-1.0.29/debian/patches/libvncclient_CVE-2018-20020.patch 
ssvnc-1.0.29/debian/patches/libvncclient_CVE-2018-20020.patch
--- ssvnc-1.0.29/debian/patches/libvncclient_CVE-2018-20020.patch   
1970-01-01 01:00:00.0 +0100
+++ ssvnc-1.0.29/debian/patches/libvncclient_CVE-2018-20020.patch   
2019-11-29 12:15:33.0 +0100
@@ -0,0 +1,22 @@
+Description: CVE-2018-20020
+ heap out-of-bound write vulnerability inside structure in VNC client code that
+ can result remote code execution
+---
+
+Author: Abhijith PA 
+Origin: 

Bug#938554: spyne_2.13.11a0-0.1_source.changes REJECTED

[Bastian Germann]

Am Sa., 7. Dez. 2019 um 02:45 Uhr schrieb Russell Stuart
:
> Perhaps you missed it as I only replied to the Debian bug, but I am not
> OK with an alpha version ending up in testing:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877783#30
>
> If you still want to do this upload the alpha version to experimental.
> If you do proceed any with uploading the alpha version to unstable I
> will replace it with the old version.

Yes, I missed that. But maybe you have made up your mind now that
spyne got auto-removed from testing.
Isn't it better to have an alpha version in testing than no version at all?

Bug#946856: Breaks d-i at runtime due to dependency loop with libc6-udeb

[Steve McIntyre]

On Mon, Dec 16, 2019 at 06:50:22PM +0100, Marco d'Itri wrote:
>On Dec 16, Steve McIntyre  wrote:
>
>> Some testing of this in a d-i environment would have been nice. :-(
>Is there a practical way to do this (i.e. without rebuilding half of 
>d-i)?
>The new package was discussed on debian-boot@.

You do a d-i build and test it. Builds are not difficult, and VM
testing is quite easy.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
  Mature Sporty Personal
  More Innovation More Adult
  A Man in Dandism
  Powered Midship Specialty

Bug#946858: ruby-grib: Should this package be removed?

[Boyuan Yang]

Source: ruby-grib
Severity: serious
Version: 0.4.0-2
X-Debbugs-CC: uwab...@gfd-dennou.org

Dear ruby-grib maintainers,

According to https://bugs.debian.org/932208 , one of the dependencies of ruby-
grib, grib-api, will be removed from Debian very soon. In this case, is the
package ruby-grib still relavent? Should we just have it removed from Debian?
Please evaluate the current status. If a removal is indeed necessary, please
consider filing a removal bug against FTP Masters.

Thanks and looking forward to your reply.

-- 
Regards,
Boyuan Yang


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

Bug#946856: Breaks d-i at runtime due to dependency loop with libc6-udeb

[Marco d'Itri]

On Dec 16, Steve McIntyre  wrote:

> Some testing of this in a d-i environment would have been nice. :-(
Is there a practical way to do this (i.e. without rebuilding half of 
d-i)?
The new package was discussed on debian-boot@.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#946857: pyfftw: FTBFS in unstable

[Graham Inggs]

Source: pyfftw
Version: 0.11.1-3
Severity: serious
Tags: ftbfs

Hi Maintainer

As can be seen on the reproducible builders [1], pyfftw currently
FTBFS in unstable.
This seems to be a combination of new versions of python3-defaults,
numpy and dask.

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

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/history/amd64/pyfftw.html


FAIL: test_objects_removed_after_keepalive
(test.test_pyfftw_interfaces_cache.CacheTest)
--
Traceback (most recent call last):
  File 
"/build/1st/pyfftw-0.11.1/.pybuild/cpython3_3.7_pyfftw/build/test/test_pyfftw_interfaces_cache.py",
line 328, in test_objects_removed_after_keepalive
self.assertRaises(KeyError, _cache.lookup, key)
AssertionError: KeyError not raised by lookup

Processed: Re: Breaks d-i at runtime due to dependency loop with libc6-udeb

[Debian Bug Tracking System]

Processing control commands:

> tag -1 +patch
Bug #946856 [libcrypt1-udeb] Breaks d-i at runtime due to dependency loop with 
libc6-udeb
Added tag(s) patch.

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

Bug#946856: Breaks d-i at runtime due to dependency loop with libc6-udeb

[Steve McIntyre]

Control: tag -1 +patch

On Mon, Dec 16, 2019 at 05:43:36PM +, Steve McIntyre wrote:
>Package: libcrypt1-udeb
>Version: 4.4.10-5
>Severity: critical
>Tags: d-i
>
>The addition of the libcrypt1-udeb has broken d-i at runtime. On a
>current d-i build, it fails immediately at boot when starting the
>main menu. In the log file:
>
>main-menu[247]: WARNING **: Deep recursion configuring package libc6-udeb (dep 
>loop?)
>main-menu[247]: WARNING **: Menu item 'localechooser' failed.
>
>If I try to save logs, that also fails and gives some more clue:
>
>main-menu[247]: WARNING **: Deep recursion configuring package libcrypt1-udeb 
>(dep loop?)
>main-menu[247]: WARNING **: Menu item 'save-logs' failed.
>
>The (dumb) resolver in the main menu is trying to configure both libc6-udeb
>and libcrypt1-udeb and can't, as they each depend on each other.
>
>Some testing of this in a d-i environment would have been nice. :-(
>
>As libcrypt1-udeb doesn't actually need any configuration, the a
>trivial patch (to simply not depend on libc6-udeb) makes things work
>again in d-i. I'll attach that in a mo once I get a bug# out of the
>BTS.

And here's the debdiff for what I've tested.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"I suspect most samba developers are already technically insane... Of
 course, since many of them are Australians, you can't tell." -- Linus Torvalds
diff -Nru libxcrypt-4.4.10/debian/changelog libxcrypt-4.4.10/debian/changelog
--- libxcrypt-4.4.10/debian/changelog   2019-12-06 11:00:54.0 +
+++ libxcrypt-4.4.10/debian/changelog   2019-12-16 17:48:24.0 +
@@ -1,3 +1,9 @@
+libxcrypt (1:4.4.10-5+nmu1) unstable; urgency=high
+
+  * Force libcrypt1-udeb to not depend on libc6-udeb. Closes: #946856
+
+ -- Steve McIntyre <93...@debian.org>  Mon, 16 Dec 2019 17:48:24 +
+
 libxcrypt (1:4.4.10-5) unstable; urgency=medium
 
   * Re-upload to unstable.
diff -Nru libxcrypt-4.4.10/debian/control libxcrypt-4.4.10/debian/control
--- libxcrypt-4.4.10/debian/control 2019-11-17 21:27:14.0 +
+++ libxcrypt-4.4.10/debian/control 2019-12-16 13:13:35.0 +
@@ -61,7 +61,7 @@
 Section: debian-installer
 Architecture: any
 Pre-Depends: ${misc:Pre-Depends}
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${misc:Depends}
 Description: libcrypt shared library
  This is a minimal version of libcrypt, only for use in the installation
  system.

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

[Debian Bug Tracking System]

Your message dated Mon, 16 Dec 2019 17:49:36 +
with message-id 
and subject line Bug#937731: fixed in python-escript 5.4-3
has caused the Debian Bug report #937731,
regarding python-escript: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-escript

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

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

We believe that the bug you reported is fixed in the latest version of
python-escript, 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.
Alastair McKinstry  (supplier of updated python-escript 
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: Mon, 16 Dec 2019 14:17:27 +
Source: python-escript
Architecture: source
Version: 5.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Closes: 917689 937731
Changes:
 python-escript (5.4-3) unstable; urgency=medium
 .
   * Drop python-numpy build-depends. Closes: #937731
   * Standards-Version now 4.4.1.0
   * Build-Depend on trilinos-dev for 64-bit archs
   * Build-depend on gmsh
   * Drop -Wno-maybe-uninitialized and use -Wno-unitialized instead because of
 warnings. Closes: #917689
Checksums-Sha1:
 adddc327837741a085aba8a00604f30534da23fe 2734 python-escript_5.4-3.dsc
 9ad30acf770f1a2c4ee0def23594d8a34c8c6b0d 13624 
python-escript_5.4-3.debian.tar.xz
Checksums-Sha256:
 dbc50b1ce4bf12cc8d509ac5e2b7a9b7bc35895cdefeaa5d87f2def7a006ee8b 2734 
python-escript_5.4-3.dsc
 e5ea9ad51c3b7c47ef9079fca2dca63a24d031289eae6fd4c6a6347f518e7ac7 13624 

Bug#946856: Breaks d-i at runtime due to dependency loop with libc6-udeb

[Steve McIntyre]

Package: libcrypt1-udeb
Version: 4.4.10-5
Severity: critical
Tags: d-i

The addition of the libcrypt1-udeb has broken d-i at runtime. On a
current d-i build, it fails immediately at boot when starting the
main menu. In the log file:

main-menu[247]: WARNING **: Deep recursion configuring package libc6-udeb (dep 
loop?)
main-menu[247]: WARNING **: Menu item 'localechooser' failed.

If I try to save logs, that also fails and gives some more clue:

main-menu[247]: WARNING **: Deep recursion configuring package libcrypt1-udeb 
(dep loop?)
main-menu[247]: WARNING **: Menu item 'save-logs' failed.

The (dumb) resolver in the main menu is trying to configure both libc6-udeb
and libcrypt1-udeb and can't, as they each depend on each other.

Some testing of this in a d-i environment would have been nice. :-(

As libcrypt1-udeb doesn't actually need any configuration, the a
trivial patch (to simply not depend on libc6-udeb) makes things work
again in d-i. I'll attach that in a mo once I get a bug# out of the
BTS.

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

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

Bug#944820: SimpleSAMLphp fails when consuming assertion

[Jørn Åne]

On 16/12/2019 14:23, Thijs Kinkhorst wrote:
> Hoi Jorn,
> 
>> When SimpleSAMLphp consumes an assertion, it will fail and log the
>> following:
> 
> Can you confirm that this update fixes the problem for you?
> 
> https://people.debian.org/~thijs/ssp/

It does, thank you!


-- 
Vennlig hilsen/Best regardsJørn Åne de Jong
Systemutvikler/Systems Developer
Uninett AS
jorn.dej...@uninett.no
+47 95 36 10 17
www.uninett.no
Abonner på vårt nyhetsbrev www.uninett.no/nyhetsbrev




signature.asc
Description: OpenPGP digital signature

Bug#946422: silx: autopkgtest regression: pocl error

[PICCA Frederic-Emmanuel]

not better

test cpp engine for medfilt2d ... ok
testOpenCLMedFilt2d (silx.image.test.test_medianfilter.TestMedianFilterEngines)
test cpp engine for medfilt2d ... 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.


The next step will be to ding in the code and find the culprite.

Processed: [bts-link] source package src:digikam

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:digikam
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #922574 (http://bugs.debian.org/922574)
> # Bug title: FTBFS against opencv 4.0.1 (exp)
> #  * http://bugs.kde.org/show_bug.cgi?id=401306
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 922574 + fixed-upstream
Bug #922574 [src:digikam] FTBFS against opencv 4.0.1 (exp)
Added tag(s) fixed-upstream.
> usertags 922574 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> thanks
Stopping processing here.

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

Bug#941544: NMU upload

[Gard Spreemann]

Hello all,

As part of my DD process I have been tasked with preparing an NMU for an
existing bug. I ended up preparing one for this bug, using Steve's
debdiff.

If I don't hear back from anyone within three days, my AM will upload
this NMU in DELAYED/7.

 Best,
 Gard


signature.asc
Description: PGP signature

Bug#946422: silx: autopkgtest regression: pocl error

[PICCA Frederic-Emmanuel]

It seems that this test does not PASS

@unittest.skipUnless(ocl, "PyOpenCl is missing")
def testOpenCLMedFilt2d(self):
"""test cpp engine for medfilt2d"""
res = medianfilter.medfilt2d(
image=TestMedianFilterEngines.IMG,
kernel_size=TestMedianFilterEngines.KERNEL,
engine='opencl')
self.assertTrue(numpy.array_equal(res, TestMedianFilterEngines.IMG))


testOpenCLMedFilt2d (silx.image.test.test_medianfilter.TestMedianFilterEngines)
test cpp engine for medfilt2d ... 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
E: pybuild pybuild:341: test: plugin custom failed with: exit code=134: env 
PYTHONPATH=/home/picca/silx-0.11.0+dfsg/.pybuild/cpython3_3.8_silx/build 
WITH_QT_TEST=False xvfb-run -a --server-args="-screen 0 1024x768x24" python3.8 
run_tests.py -vv --installed
dh_auto_test: pybuild --test -i python{version} -p "3.8 3.7" -s custom 
"--test-args=env PYTHONPATH={build_dir} WITH_QT_TEST=False xvfb-run -a 
--server-args=\"-screen 0 1024x768x24\" {interpreter} run_tests.py -vv 
--installed" returned exit code 13
make[1]: *** [debian/rules:70: override_dh_auto_test] Error 255
make[1]: Leaving directory '/home/picca/silx-0.11.0+dfsg'
make: *** [debian/rules:27: build] Error 2


the code of medfilt2d is there


def medfilt2d(image, kernel_size=3, engine='cpp'):
"""Apply a median filter on an image.

This median filter is using a 'nearest' padding for values
past the array edges. If you want more padding options or
functionalities for the median filter (conditional filter 
for example) please have a look at
:mod:`silx.math.medianfilter`.

:param numpy.ndarray image: the 2D array for which we want to apply
the median filter.
:param kernel_size: the dimension of the kernel.
Kernel size must be odd.
If a scalar is given, then it is used as the size in both dimension.
Default: (3, 3)
:type kernel_size: A int or a list of 2 int (kernel_height, kernel_width)
:param engine: the type of implementation to use.
Valid values are: 'cpp' (default) and 'opencl'

:returns: the array with the median value for each pixel.

.. note::  if the opencl implementation is requested but
is not present or fails, the cpp implementation is called.

"""
if engine not in MEDFILT_ENGINES:
err = 'silx doesn\'t have an implementation for the requested engine: '
err += '%s' % engine
raise ValueError(err)

if len(image.shape) is not 2:
raise ValueError('medfilt2d deals with arrays of dimension 2 only')

if engine == 'cpp':
return medianfilter_cpp.medfilt(data=image,
kernel_size=kernel_size,
conditional=False)
elif engine == 'opencl':
if medfilt_opencl is None:
wrn = 'opencl median filter not available. '
wrn += 'Launching cpp implementation.'
_logger.warning(wrn)
# instead call the cpp implementation
return medianfilter_cpp.medfilt(data=image,
kernel_size=kernel_size,
conditional=False)
else:
try:
medianfilter = medfilt_opencl.MedianFilter2D(image.shape,
 devicetype="gpu")
res = medianfilter.medfilt2d(image, kernel_size)
except(RuntimeError, MemoryError, ImportError):
wrn = 'Exception occured in opencl median filter. '
wrn += 'To get more information see debug log.'
wrn += 'Launching cpp implementation.'
_logger.warning(wrn)
_logger.debug("median filter - openCL implementation issue.",
  exc_info=True)
# instead call the cpp implementation
res = medianfilter_cpp.medfilt(data=image,
   kernel_size=kernel_size,
   conditional=False)

return res

in our case we have engine = 'opencl' and no warning message, so medfil_opencl  
should not be None.

it comes from here

from silx.opencl import medfilt as medfilt_opencl

In this code we have

:param devicetype: type of device, can be "CPU", "GPU", "ACC" or "ALL"
 
So let's do a first test by replacing gpu by cpu to see if it change something 
during the test.

Bug#945920: Chrome bug

[PPHome2]

"Override software rendering list"

It helped my machine but didn't really solve the problem, chrome worked
for 1-2 hours with this setup. Resetting it to default has been my
general operation for 20-30 minutes.

I'm sorry that I set this option as a workaround.
-- 
PP

Bug#946797: debian-edu-config: kadm5.acl should set proper rights for users

[Holger Levsen]

On Mon, Dec 16, 2019 at 04:58:32PM +0100, Dominik George wrote:
> > Wolfgang, many thanks for this bug report and the quick fix.
> > I'll upload to unstable right now and will coordinate with DSA and LTS
> > the fixes for buster, stretch and jessie.
> Are you aware that, as laid out on IRC, I am already doing that?

no. (best always to inform the bug if you are working on one.) (*)

also I've already uploaded to unstable as the fix needs to land there
first anyway.

Please also take my additional fix for postinst.


(*) my server had some connectivity issues and I wasnt on irc for 48h...
and then I just re-joined #-edu now.

-- 
cheers,
Holger

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



signature.asc
Description: PGP signature

Bug#946797: marked as done (debian-edu-config: kadm5.acl should set proper rights for users)

[Debian Bug Tracking System]

Your message dated Mon, 16 Dec 2019 16:19:31 +
with message-id 
and subject line Bug#946797: fixed in debian-edu-config 2.11.10
has caused the Debian Bug report #946797,
regarding debian-edu-config: kadm5.acl should set proper rights for users
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.)


-- 
946797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-edu-config
Version: 1.812+deb8u1
Severity: important

To improve security, settings in kadm5.acl should be adjusted.

The needed fix is minimal:

--- a/share/debian-edu-config/tools/kerberos-kdc-init
+++ b/share/debian-edu-config/tools/kerberos-kdc-init
@@ -187,7 +187,7 @@ EOF
 if [ ! -f /etc/krb5kdc/kadm5.acl ] ; then
cat > /etc/krb5kdc/kadm5.acl <

signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: debian-edu-config
Source-Version: 2.11.10

We believe that the bug you reported is fixed in the latest version of
debian-edu-config, 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.
Holger Levsen  (supplier of updated debian-edu-config 
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 16:56:24 +0100
Source: debian-edu-config
Architecture: source
Version: 2.11.10
Distribution: unstable
Urgency: medium
Maintainer: Debian Edu Developers 
Changed-By: Holger Levsen 
Closes: 946797
Changes:
 debian-edu-config (2.11.10) unstable; urgency=medium
 .
   [ Wolfgang Schweer ]
   * share/debian-edu-config/tools/kerberos-kdc-init:
 - Set proper rights for users in kadm5.acl file. (Closes: #946797)
   * Adjust debian/debian-edu-config.postinst to fix kadm5.acl upon upgrades.
   * Use secure URI in Homepage field.
   * Use canonical URL in Vcs-Git.
 .
   [ Holger Levsen ]
   * Improve debian/debian-edu-config.postinst fix to only run once on
 upgrades.
Checksums-Sha1:
 5b27f6077b87231c0d18c20a4c32147526e95c8c 1923 debian-edu-config_2.11.10.dsc
 e44bb8b240fb29ba916c959048ee620ad6d77950 340580 
debian-edu-config_2.11.10.tar.xz
 fdb9ddfea7b236e7f145a9cb24abc8de3dbd5652 5323 
debian-edu-config_2.11.10_source.buildinfo
Checksums-Sha256:
 c53a60a14694154a2598060735eaefe631d47b402d464e1d969d1b65873ed614 1923 
debian-edu-config_2.11.10.dsc
 285930972ed0ef9dc563064f42a3a75c159be2ba942e5d69ca7da64913dea8fb 340580 
debian-edu-config_2.11.10.tar.xz
 1fb2d212d9fc6a17c66ad51639cccf102d14b4a966138d26f0689750b9722a22 5323 
debian-edu-config_2.11.10_source.buildinfo
Files:
 93d8ea4c7578e37ee8927dafc0ed3209 1923 misc optional 
debian-edu-config_2.11.10.dsc
 c698786e25119d7380d25fde242adf7e 340580 misc optional 
debian-edu-config_2.11.10.tar.xz
 3c059ac522cada4d16cf63ffb1a8d015 5323 misc optional 
debian-edu-config_2.11.10_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAl33qaEACgkQCRq4Vgaa
qhy3dg/9GNR24sciJDRuKh2pq2ExE1/+flhfnPYcFJkRE+x667FKc0kJgGLkCV4R
CLXzHJafRPPMWt/uFjIX0QmhY1kXPyJlTtMCo/QJW8GhIVUSzkjdVn9L3VTr4tcT
J9QYI7oXl3CJ+oEbErX8bq4ufifLRKxHoTVKrbPi2JOSD6zoakW6uWRIHNBUWVDz
uPxpgeVeT4ePMNyqnVb1360v5Lr3dUm51dCxxIXxD5hCzaDA+Vl8dUWO65BTryRR
im5EbjnBwp+wsWNkSAiumhBKdJnoqafsF8bOY9Bb180hPljFeVCvrfdLtuRf5t1k
Ky7zZBrhV0z375VxSNj80IqE81A7vzBblngUTrCMzJmnu/GdZwqRBfawgAVronj6
oelLB9EOLn78BK6/84BqAghFDk+tZ8ysE+h6PGYAnTQVF5mfSQjHVcMbyr/YuJzn
JAmx0qWhOm1dwkOvd8Gg/9JC5dg5XhZgfnheWkvD5v6V6CxUGHSGKU7+iWppaGkr
wawx1K5D07YEeV8gv2xLbkExOeN5NTHDre9Vw2Kam/rpfetv2WHc62gCO9PYr/tE
STjag0vENNQhKWVw1wn19kI5TOlQrXFJ7VoMNob4dp6Yjag5YLJlGq1EAFksRCW2
4qgZjEqrG6+MVvno8Px596DsveGkKE3q54ep27zh5vTre8kV0dI=
=6zZo
-END PGP SIGNATURE End Message ---

Bug#946797: debian-edu-config: kadm5.acl should set proper rights for users

[Dominik George]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

> Wolfgang, many thanks for this bug report and the quick fix.
> I'll upload to unstable right now and will coordinate with DSA and LTS
> the fixes for buster, stretch and jessie.

Are you aware that, as laid out on IRC, I am already doing that?

- -nik
-BEGIN PGP SIGNATURE-

iQJlBAEBCgBPFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAl33qacxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYwAKCRC3mjwW
oMTylk1KEACs5v3i94+Hopt5NNSRc+nvQTC7I4AIUsbupHWj9EpV/avKXBH5ak2C
I+U8H6wtlAXQr1KkQwkKxUQYEyXwVN1swKrqJeb6cqW0jB62QizHxDMlzULh1qBw
per1HXYtlK5WcpytkarmOAauWC9Hrh0EIqfQwQxywZSKWbV2IwSj5+LdKW+sVj42
+z8MzO9A+b2UHYo8KWnwq/P48FfFp0bn9unrhiqkLB2OhFsDydF0w7IB8yqecj6x
QP177Po3B7Hf1ThDF4cfF/kqZQ0NenWvv7uRwNL/y4wJ7XQ0EtEsMY73iq3E/CXz
YRvqttqbnNSQO0xAy8CE9jKHY9vMoL7if4NdvFYlSsJYmg+/Tw5BLaehKQRINvZh
pMqDLB4kVi5gpO1Q6qGo/2+SU0+91QbPR6dwQCvcZRQ8v4KqN6GpS00mQX44DFhT
S1kOr60rCYYlRtmxeqmHhyv52GRoY8iGq5KuQUnwXAm8buqy4LmzWQhAVrQk30fi
oA290vBcXyTvhs8/yKGTvjnJcdmfE9V2QIZ8cA/5WbOBAEiEBtH1PoG87dUTejkD
SwEq20DAK8BhCGlWofanEnDygbnvFg/ouHsYQkt6RiP9ocqxXr+J2k5ACOUCWYmo
Carf26wfZ8IWPG7zUoaud68YAPSCfHi35rmRNFBt69DFeH66cLYg+Q==
=SBC3
-END PGP SIGNATURE-

Bug#946797: debian-edu-config: kadm5.acl should set proper rights for users

[Holger Levsen]

On Mon, Dec 16, 2019 at 12:26:57AM +0100, Wolfgang Schweer wrote:
> Also, /etc/krb5kdc/kadm5.acl should be fixed accordingly upon upgrades
> by adding something like this to debian-edu-config.postinst:
> 
> [configure case]
>  fi
> +
> +# Set proper rights for users.
> +if [ -f /etc/krb5kdc/kadm5.acl ] ; then
> +sed -i 's/cil/Cil/' /etc/krb5kdc/kadm5.acl
> +fi
>  ;;

I've made this conditional, so that this is only executed when upgrading
from 2.11.9 or before. (Also because the above changes also need a
krb5-admin-server service restart...)


-- 
cheers,
Holger

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



signature.asc
Description: PGP signature

Bug#946797: debian-edu-config: kadm5.acl should set proper rights for users

[Holger Levsen]

Hi,

Wolfgang, many thanks for this bug report and the quick fix.
I'll upload to unstable right now and will coordinate with DSA and LTS
the fixes for buster, stretch and jessie.

On Mon, Dec 16, 2019 at 11:05:33AM +0100, Dominik George wrote:
> > Severity: important
> I propose this bug to be set to severity critical and handled by DSA. 

DSA is very happy about maintainers - in coordination with DSA - taking care
of 'their' security fixes.

-- 
cheers,
Holger

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



signature.asc
Description: PGP signature

Processed: Bug#946797 marked as pending in debian-edu-config

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #946797 [debian-edu-config] debian-edu-config: kadm5.acl should set proper 
rights for users
Ignoring request to alter tags of bug #946797 to the same tags previously set

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

Bug#946797: marked as pending in debian-edu-config

[Dominik George]

Control: tag -1 pending

Hello,

Bug #946797 in debian-edu-config 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/debian-edu/debian-edu-config/commit/69dd3cf269eaa802f265cdd5b801f111d05731fe


share/debian-edu-config/tools/kerberos-kdc-init:
Set proper rights for users in kadm5.acl file. (Closes: #946797)

Adjust debian/debian-edu-config.postinst to fix kadm5.acl upon upgrades.

Signed-off-by: Wolfgang Schweer 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/946797

Processed: Re: Bug#946850: last-align ftbfs on non-x86 architectures

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #946850 [src:last-align] last-align ftbfs on non-x86 architectures
Added tag(s) upstream.
> forwarded -1 l...@cbrc.jp
Bug #946850 [src:last-align] last-align ftbfs on non-x86 architectures
Set Bug forwarded-to-address to 'l...@cbrc.jp'.

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

Bug#946850: last-align ftbfs on non-x86 architectures

[Andreas Tille]

Control: tags -1 upstream
Control: forwarded -1 l...@cbrc.jp


Hi,

the Debian packaged version of last has received the bug report you can
read below.  We are building last on several architectures which was not
a problem for previous versions.  Is there any restriction to run last
only on x86 architectures from your point of view?

Kind regards and thanks for providing last as free software

 Andreas.

On Mon, Dec 16, 2019 at 03:47:11PM +0100, Matthias Klose wrote:
> Package: src:last-align
> Version: 1021-2
> Severity: serious
> Tags: sid bullseye
> 
> last-align ftbfs on non-x86 architectures, and I really didn't check if it's
> doing the right thing on i386 with the intrinsics ...
> 
> 
> In file included from GappedXdropAligner.hh:49,
>  from GappedXdropAligner.cc:49:
> mcf_simd.hh:7:10: fatal error: immintrin.h: No such file or directory
> 7 | #include 
>   |  ^
> compilation terminated.
> make[3]: *** [makefile:105: GappedXdropAligner.o] Error 1
> make[3]: Leaving directory '/<>/src'
> make[2]: *** [makefile:3: all] Error 2
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging

-- 
http://fam-tille.de

Bug#946850: last-align ftbfs on non-x86 architectures

[Matthias Klose]

Package: src:last-align
Version: 1021-2
Severity: serious
Tags: sid bullseye

last-align ftbfs on non-x86 architectures, and I really didn't check if it's
doing the right thing on i386 with the intrinsics ...


In file included from GappedXdropAligner.hh:49,
 from GappedXdropAligner.cc:49:
mcf_simd.hh:7:10: fatal error: immintrin.h: No such file or directory
7 | #include 
  |  ^
compilation terminated.
make[3]: *** [makefile:105: GappedXdropAligner.o] Error 1
make[3]: Leaving directory '/<>/src'
make[2]: *** [makefile:3: all] Error 2

Processed (with 1 error): ruby-sigar FTBFS with glibc 2.28

[Debian Bug Tracking System]

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

> tags 916111 patch
Bug #916111 [src:ruby-sigar] ruby-sigar FTBFS with glibc 2.28
Added tag(s) patch.
> user 916111 ubuntu-de...@lists.ubuntu.com
Unknown command or malformed arguments to command.
> usertags 916111 origin-ubuntu focal ubuntu-patch
User is seb...@ubuntu.com
There were no usertags set.
Usertags are now: focal origin-ubuntu ubuntu-patch.
> thank you
Stopping processing here.

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

Bug#916111: ruby-sigar FTBFS with glibc 2.28

[Sebastien Bacher]

tags 916111 patch
user 916111 ubuntu-de...@lists.ubuntu.com
usertags 916111 origin-ubuntu focal ubuntu-patch

thank you

The attached patch fixes the issue


diff -Nru ruby-sigar-0.7.3/debian/changelog ruby-sigar-0.7.3/debian/changelog
--- ruby-sigar-0.7.3/debian/changelog	2015-09-09 17:59:41.0 +0200
+++ ruby-sigar-0.7.3/debian/changelog	2019-12-16 15:39:55.0 +0100
@@ -1,3 +1,11 @@
+ruby-sigar (0.7.3-2) UNRELEASED; urgency=medium
+
+  * debian/patches/github-glibc-buildfix.patch:
+- build fix for glibc 2.28, backported upstream proposed fix from
+  https://github.com/hyperic/sigar/pull/127 (Closes: #916111)
+
+ -- Sebastien Bacher   Mon, 16 Dec 2019 15:31:01 +0100
+
 ruby-sigar (0.7.3-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru ruby-sigar-0.7.3/debian/control ruby-sigar-0.7.3/debian/control
--- ruby-sigar-0.7.3/debian/control	2015-09-09 17:59:41.0 +0200
+++ ruby-sigar-0.7.3/debian/control	2018-03-01 10:36:16.0 +0100
@@ -1,7 +1,8 @@
 Source: ruby-sigar
 Section: ruby
 Priority: optional
-Maintainer: Debian Ruby Extras Maintainers 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: Debian Ruby Extras Maintainers 
 Uploaders: Pirate Praveen 
 Build-Depends: debhelper (>= 7.0.50~), gem2deb (>= 0.7.4~)
 Standards-Version: 3.9.6
diff -Nru ruby-sigar-0.7.3/debian/patches/github-glibc-buildfix.patch ruby-sigar-0.7.3/debian/patches/github-glibc-buildfix.patch
--- ruby-sigar-0.7.3/debian/patches/github-glibc-buildfix.patch	1970-01-01 01:00:00.0 +0100
+++ ruby-sigar-0.7.3/debian/patches/github-glibc-buildfix.patch	2019-12-16 15:30:29.0 +0100
@@ -0,0 +1,28 @@
+From b4e27b0b3167aac9a0f3f08dd2b2a0c0c9c4d797 Mon Sep 17 00:00:00 2001
+From: Logan Rosen 
+Date: Fri, 11 Jan 2019 22:52:21 -0500
+Subject: [PATCH] Fix build with glibc 2.28
+https://github.com/hyperic/sigar/pull/127
+---
+ src/os/linux/linux_sigar.c | 5 +
+ 1 file changed, 5 insertions(+)
+
+diff --git a/src/os/linux/linux_sigar.c b/src/os/linux/linux_sigar.c
+index a3fd2301..de9c960c 100644
+--- a/src/os/linux/linux_sigar.c
 b/src/os/linux/linux_sigar.c
+@@ -23,8 +23,13 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ 
++#ifdef __GNU_LIBRARY__
++#include 
++#endif
++
+ #include "sigar.h"
+ #include "sigar_private.h"
+ #include "sigar_util.h"
+
diff -Nru ruby-sigar-0.7.3/debian/patches/series ruby-sigar-0.7.3/debian/patches/series
--- ruby-sigar-0.7.3/debian/patches/series	2015-09-09 17:59:41.0 +0200
+++ ruby-sigar-0.7.3/debian/patches/series	2019-12-16 14:24:50.0 +0100
@@ -1,2 +1,3 @@
 mips-TIOCGETC-undeclared.patch
 gnu89-inline.diff
+github-glibc-buildfix.patch

Bug#946802: marked as done (python3-minieigen: missing Breaks+Replaces: python-minieigen)

[Debian Bug Tracking System]

Your message dated Mon, 16 Dec 2019 14:41:26 +
with message-id 
and subject line Bug#946802: fixed in minieigen 0.50.3+dfsg1-11
has caused the Debian Bug report #946802,
regarding python3-minieigen: missing Breaks+Replaces: python-minieigen
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.)


-- 
946802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-minieigen
Version: 0.50.3+dfsg1-10
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
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...):

  Preparing to unpack .../python3-minieigen_0.50.3+dfsg1-10_amd64.deb ...
  Unpacking python3-minieigen (0.50.3+dfsg1-10) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-minieigen_0.50.3+dfsg1-10_amd64.deb (--unpack):
   trying to overwrite '/usr/share/doc-base/python-minieigen', which is also in 
package python-minieigen 0.50.3+dfsg1-9
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-minieigen_0.50.3+dfsg1-10_amd64.deb


cheers,

Andreas


python-minieigen=0.50.3+dfsg1-9_python3-minieigen=0.50.3+dfsg1-10.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: minieigen
Source-Version: 0.50.3+dfsg1-11

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 16 Dec 2019 14:09:16 +
Source: minieigen
Architecture: source
Version: 0.50.3+dfsg1-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Dimitri John Ledkov 
Closes: 946802
Changes:
 minieigen (0.50.3+dfsg1-11) unstable; urgency=medium
 .
   * [74291a6] Correct doc-base document name, and paths. Closes: #946802
Checksums-Sha1:
 130f706822386b39b997b6579d98ecdb35445724 2196 minieigen_0.50.3+dfsg1-11.dsc
 6cfd6d1448b5406b8ee13387916631fa182af7bf 7180 
minieigen_0.50.3+dfsg1-11.debian.tar.xz
 1cc1bbac06fb4dca7724b7b2d6ae1c7183377db5 8814 
minieigen_0.50.3+dfsg1-11_source.buildinfo
Checksums-Sha256:
 f57419cdf663041ff78fdf968e45c7da502cb1daf50b7b52958604dc4f1df16d 2196 
minieigen_0.50.3+dfsg1-11.dsc
 655b27e9b89916f1548a69d0ff04028e690504b150681a66aae3429bd94ad619 7180 
minieigen_0.50.3+dfsg1-11.debian.tar.xz
 1a8d3386786f74876f2bdcda3c7a627e1dc9209012cbac1bb0d7dba785b38e1c 8814 
minieigen_0.50.3+dfsg1-11_source.buildinfo
Files:
 49734a9dfd0663494a0049f1e4a988bd 2196 libs optional 
minieigen_0.50.3+dfsg1-11.dsc
 15a8504a35b066860f51ed09dadee6fb 7180 libs optional 
minieigen_0.50.3+dfsg1-11.debian.tar.xz
 25c63755fa3d7a2e68911123351cddf2 8814 libs optional 
minieigen_0.50.3+dfsg1-11_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE7iQKBSojGtiSWEHXm47ISdXvcO0FAl33kGsACgkQm47ISdXv
cO0xpRAAkY0VN/JiJgUte5FT68ERekC17+tSN/3yRRGpUI0Rbc+Xbn+X9vUrHp0F
LQ4vVJCO1Q7GIvEljh+PDeGu79lFASdIscrTaFgCFh+ailArTJnNiynS9x33ey+Y
OCPXkB2EFJq6ISMicSLyk2dxbMcW3WN1+I4aEby9FDDi4eJFz04C9FLs1BJTJZAJ
4yekHvGadfng2ZBOa3GRLA74sthXR9aKhersLrNICVNdYrqoZ5tHTCIFSiBDLkZF
OTHm/luPbeO4KWKsT1Acr5Zz/8ShaT/FJK4T5pk8Cm24K72C8/MCm9mOc6knCxd7
7ogjODeoxT5u11K9dattAJpnrGNzhmtE2Fv24kWqEIIiEsKjCeTkKNuwqNBh+div
4hDVYufL32j3AgVuK+CxHABdC3kwbNzyt6sge8nJ8m6I/wZRP6MaReLvqqGqzYTr
FtOPOjyO6O0pUk8uH3s9UHBaAkJC1CIB4D40WCP7v+2mMCgPtdhVQjDVc+FDCqds
7o6Q3tXqJfuDlO4Ibs+Zi30LU2F5BPTXTM7Ry+aQXXmG9jYcUJTFiwDootANkURj
P394EnwHgaJY2tkVlF9/1Q038zFF1yIJ1F+mmygxHeTZtG7e2bOTLee+GG/YYPzP
MsRQUIeuZBHRQjBys6NqU/sI9m/AUAtSsOoo4nSQal+sLuU0m3k=
=PvYY
-END PGP SIGNATURE End Message ---

Bug#946568: marked as done (libbio-cluster-perl: missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3))

[Debian Bug Tracking System]

Your message dated Mon, 16 Dec 2019 14:41:17 +
with message-id 
and subject line Bug#946568: fixed in libbio-cluster-perl 1.7.3-3
has caused the Debian Bug report #946568,
regarding libbio-cluster-perl: missing Breaks+Replaces: libbio-perl-perl (<< 
1.7.3)
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.)


-- 
946568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbio-cluster-perl
Version: 1.7.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
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

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../libbio-cluster-perl_1.7.3-1_all.deb ...
  Unpacking libbio-cluster-perl (1.7.3-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libbio-cluster-perl_1.7.3-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/man/man3/Bio::Cluster::ClusterFactory.3pm.gz', which is also in 
package libbio-perl-perl 1.7.2-3
  Errors were encountered while processing:
   /var/cache/apt/archives/libbio-cluster-perl_1.7.3-1_all.deb


cheers,

Andreas


libbio-perl-perl=1.7.2-3_libbio-cluster-perl=1.7.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libbio-cluster-perl
Source-Version: 1.7.3-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 16 Dec 2019 14:58:36 +0100
Source: libbio-cluster-perl
Architecture: source
Version: 1.7.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 946568
Changes:
 libbio-cluster-perl (1.7.3-3) unstable; urgency=medium
 .
   * Whoops, try that again:
 Strengthen Breaks+Replaces: libbio-perl-perl (<< 1.7.3) (Closes: #946568)
Checksums-Sha1:
 49c5b5b10f057686739291194c9c25bf27d079d6 2156 libbio-cluster-perl_1.7.3-3.dsc
 cbbb5580d2dbf47bc824b25bc062272242ac39af 3748 
libbio-cluster-perl_1.7.3-3.debian.tar.xz
 a568018f5248027401de7831abb9a68088e9d8b1 7431 
libbio-cluster-perl_1.7.3-3_source.buildinfo
Checksums-Sha256:
 8de6ada47f676bbb2cbd3797266f7085f284e5654de5879de3a0cd12fa566d4c 2156 
libbio-cluster-perl_1.7.3-3.dsc
 1b416e359d45a401a312fcdabfd3ec2a914d3d76325f1cc95067636082d332fe 3748 
libbio-cluster-perl_1.7.3-3.debian.tar.xz
 54249da9683a9e39479cdf6c2ff288daf921464d05e4c0b6375a9b29698c0f00 7431 
libbio-cluster-perl_1.7.3-3_source.buildinfo
Files:
 723f0c2a4a11f534829ec15f46561e7f 2156 perl optional 
libbio-cluster-perl_1.7.3-3.dsc
 2a0ad8d9976c40bc2c724797ed10e7c8 3748 perl optional 
libbio-cluster-perl_1.7.3-3.debian.tar.xz
 388cfd7af88a6ae029b07b03aae68ad8 7431 perl optional 
libbio-cluster-perl_1.7.3-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl33jcIACgkQPCZ2P2xn
5uIspxAAu5fVkE0qLIY0qazRbqKv/QADXVbfjtgfSZ+Bx1hi4t0rBkPWbqlr3HpO
TO1NK5vJnd7MsQEVnAuhG6PkyG8idKQ9aBe54fhgunOPIucQrb9eCPNKm4ooDy/7
5aYTw49hMJE/rrmgpADxt1xINr3zpUHG+jUx1I1c+EeAAQ/O7xuYFPRMQonXD+iZ
2eQkaKtEBRt9oUy9kvZoGFt/gJpv3/E1fSamK3g+/KR8Y9LQFZNLkcCfs68E6fYp
ugNk+83HnegfM0sJhcdv8/mBYji01m/KheGErHY1Yk544MtkhhIT0gMszv2CNTin
wXkQ+4jeAtDeOWE3elJI5qURYMe5THklnj+PIVGBVyb4xI0ePlzs2xEmnAZ488Qn
V+8Ah7yhSaWNI3EBFMk2U0nEM/jFvv55Yk6sljaHkqZI6BgtJNW+KLSQQ+3+ayXO
u2lKy/MT0Ak6ZzE2lVHvk1Ytbh5+165E5NKIn1QP7h4SVmnK5iSILjHv/f32SvRZ

Processed: cloning 937270, severity of -1 is normal, retitle -1 to RM: pegasus-wms, orphaned, python2 ...

[Debian Bug Tracking System]

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

> clone 937270 -1
Bug #937270 [src:pegasus-wms] pegasus-wms: Python2 removal in sid/bullseye
Bug 937270 cloned as bug 946849
936323 was blocked by: 937270
936323 was blocking: 937695
Added blocking bug(s) of 936323: 946849
937617 was blocked by: 936189 937267 937931 937270
937617 was blocking: 937156 937695 937926 938168 938355 938492
Added blocking bug(s) of 937617: 946849
937695 was blocked by: 936875 936812 938682 942955 937883 943168 938268 936243 
943279 937900 936537 936520 936398 942912 942975 936745 936910 936855 936686 
938816 936949 936981 938150 937203 936842 936752 945682 937563 937387 936919 
938756 938846 938036 936772 937554 942942 936147 936529 937809 937463 938152 
936176 937474 938877 936819 938689 945680 942981 936840 936770 936942 945717 
938004 937454 938611 936881 937241 942940 945689 938680 936810 936955 936759 
938408 937738 935358 937800 937058 938373 937724 938364 942910 936522 937211 
938353 937078 939487 936294 937902 938641 936779 936561 936420 936437 945747 
936975 936912 936343 937728 938116 936155 937054 937102 945740 938859 936430 
936427 938710 945719 937074 936532 936298 937063 937287 936757 936847 938781 
936313 937458 938525 938850 938008 945710 936956 938719 936777 936685 937578 
936181 938157 937673 943257 942976 937664 943277 936539 938177 936119 936876 
938425 937558 938852 938742 943164 938273 943173 937389 938755 938436 938845 
938591 938712 938775 942112 937100 936917 945742 943153 936149 936527 936110 
937907 939482 938125 937874 943225 942929 938621 936440 938059 943068 945727 
938457 936829 938546 937007 849087 936481 936449 938808 938050 937262 938730 
939103 938727 937688 937221 937400 936132 937714 938516 936704 936820 938070 
936937 938669 938826 937500 937260 936920 938052 937402 937483 937331 936127 
943204 935209 938015 938072 938416 936736 936455 938695 937793 938384 936725 
938660 937269 935657 945732 936442 936929 936581 937295 945695 938835 939111 
938557 936735 938696 938016 938472 936939 938388 937083 937174 936120 937321 
938579 938445 936927 938046 937267 938836 937507 937296 945667 936832 936726 
938559 943208 938108 937231 937684 942930 938545 936932 938720 936665 938479 
936161 938737 938057 938459 936830 936708 936699 937009 937718 938729 938470 
945720 936447 943064 938515 943184 943235 938572 942939 938631 936556 937748 
936323 937000 936690 938450 936839 936857 937105 936172 936535 936611 938156 
942977 937694 943276 942957 938176 937448 936152 938840 938750 936689 938819 
936877 938027 936946 943194 938294 936641 938522 937044 937834 938437 938779 
936717 938420 936916 938759 938810 936680 937385 937418 936526 937806 938520 
938461 943217 936179 936816 938686 945715 938745 937124 938875 936426 937138 
943143 936159 936268 938243 936508 938772 938715 945745 936977 936756 937286 
938147 938529 943247 936170 936150 937643 943113 936776 937548 936957 938032 
938752 936177 942972 943240 942915 936852 936742 936425 938947 943281 938746 
938181 938856 938022 936815 936950 938685 945716 936872 937544 938061 936979 
938432 936712 936775 938301 942945 943210 938394 937783 936273 937938 945746 
937514 936845 936591 936959 938716 938427 936710 936945 936749 943033 936859 
938671 937700 937048 942979 937838 938532 943198 943275 938155 942959 937414 
936536 938651 936687 938029 945671 942970 936525 937709 937905 937271 937386 
938777 936915 936850 938439 936972 937593 936740 938020 936952 936870 938757 
938847 937444 936146 938313 937251 945651 942950 937005 942926 938861 937406 
938455 938736 938056 936695 936908 936191 936416 937534 937114 938076 938412 
936669 938127 943227 938549 943230 938130 938510 945736 937144 938581 938223 
936557 938540 942935 936577 938442 936660 938829 938666 936457 945704 938697 
937778 936546 936288 937758 937848 937038 936125 938542 937024 937193 936477 
938419 936935 936739 938440 943043 937428 938555 945666 937297 938837 937392 
937266 938047 936926 938704 938410 936727 938922 936730 943232 936459 945690 
942991 938040 938830 938708 938699 937290 938019 938827 936936 936126 937814 
943222 936891 938081 936804 936737 934852 936720 938665 938690 938049 945699 
936450 945708 938839 938010 937265 936729 937505 945665 936631 938556 937028 
936284 937844 937034 936572 937993 943133 938233 936550 937944 945726 943098 
938476 936825 938692 937148 936472 936667 938735 938055 937006 942925 937405 
936570 938129 936388 943229 936904 937538 937118 934870 937397 945692 937914 
936559 938517 936761 943237 936445 945735 936994 936843 937202 936753 937911 
937307 937562 936212 936901 936275 937521 936317 938379 943116 938216 938359 
942943 937989 937785 938588 938370 936242 937803 943008 937941 938683 936813 
937187 936606 938350 937495 937616 938315 937880 936240 938372 936219 938277 
937771 943026 938600 938488 937209 936634 936628 937841 937031 937751 936913 
936523 943157 937903 937421 937560 936249 937462 943253 938153 942994 937677 
937889 938345 938164 937657 943273 936894 

Processed: found 936951 in 5.5.1-6

[Debian Bug Tracking System]

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

> found 936951 5.5.1-6
Bug #936951 [src:link-grammar] link-grammar: Python2 removal in sid/bullseye
Marked as found in versions link-grammar/5.5.1-6.
> thanks
Stopping processing here.

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

Processed: bug 936753 is forwarded to https://bugs.launchpad.net/ispell-lt/+bug/1856108

[Debian Bug Tracking System]

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

> forwarded 936753 https://bugs.launchpad.net/ispell-lt/+bug/1856108
Bug #936753 [src:ispell-lt] ispell-lt: Python2 removal in sid/bullseye
Set Bug forwarded-to-address to 
'https://bugs.launchpad.net/ispell-lt/+bug/1856108'.
> thanks
Stopping processing here.

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

Bug#946568: libbio-cluster-perl: missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3)

[Andreas Beckmann]

Followup-For: Bug #946568
Control: found -1 1.7.3-2

Hi,

the Breaks+Replaces: libbio-perl-perl (<= 1.7.2) is not sufficient.
You need Breaks+Replaces: libbio-perl-perl (<< 1.7.3).

Andreas

Processed: Re: libbio-cluster-perl: missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3)

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.7.3-2
Bug #946568 {Done: michael.cru...@gmail.com (Michael R. Crusoe)} 
[libbio-cluster-perl] libbio-cluster-perl: missing Breaks+Replaces: 
libbio-perl-perl (<< 1.7.3)
Marked as found in versions libbio-cluster-perl/1.7.3-2; no longer marked as 
fixed in versions libbio-cluster-perl/1.7.3-2 and reopened.

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

Bug#939260: websploit: Python2 removal in sid/bullseye

[Raphael Hertzog]

Hello,

On Tue, 10 Dec 2019, 0X0Ptim0Us wrote:
> Got it, thank you. I will work on it

Great. Looking forward to it. Do you have any idea how much time you need
to complete this Python 3 port of websploit?

Regards,
-- 
  ⢀⣴⠾⠻⢶⣦⠀   Raphaël Hertzog 
  ⣾⠁⢠⠒⠀⣿⡁
  ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/
  ⠈⠳⣄   Debian Long Term Support: https://deb.li/LTS

Processed: severity of 944820 is serious

[Debian Bug Tracking System]

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

> severity 944820 serious
Bug #944820 [simplesamlphp] SimpleSAMLphp fails when consuming assertion
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#946797: debian-edu-config: kadm5.acl should set proper rights for users

[Wolfgang Schweer]

On Mon, Dec 16, 2019 at 01:09:53PM +0100, Dominik George wrote:
> Also, I'd propose to turn the sed command into:
> 
>   sed -i 's/\(\*@INTERN[[:space:]]*\)cil/\1CIl/' /etc/krb5kdc/kadm5.acl
> 
> This way, it will not destroy any legitimate additions a local admin made.
 
Good point. Thanks, committed.

Wolfgang


signature.asc
Description: PGP signature

Processed: #946797

[Debian Bug Tracking System]

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

> severity 946797 critical
Bug #946797 [debian-edu-config] debian-edu-config: kadm5.acl should set proper 
rights for users
Severity set to 'critical' from 'important'
> tags 946797 + patch security
Bug #946797 [debian-edu-config] debian-edu-config: kadm5.acl should set proper 
rights for users
Added tag(s) patch and security.
> thanks
Stopping processing here.

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

Bug#946837: vagrant: Does not work with virtualbox 6.1 from unstable

[Guillem Jover]

Package: vagrant
Version: 2.2.6+dfsg-1
Severity: serious

Hi!

The package does not work anymore since virtualbox 6.1 got upload to
unstable.

To get this working this just requires a couple of changes, which can
be easily applied as a local patch. Something like what is described
at .

Thanks,
Guillem

Processed: tagging 946719, tagging 946734, found 946769 in 1.7

[Debian Bug Tracking System]

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

> tags 946719 + sid bullseye
Bug #946719 {Done: Jonas Smedegaard } [src:konclude] konclude: 
FTBFS in sid
Added tag(s) sid and bullseye.
> tags 946734 + sid bullseye
Bug #946734 [src:rust-addr2line] rust-addr2line Build-Depends on 
librust-fallible-iterator-0.1+default-dev which isn't available
Added tag(s) bullseye and sid.
> found 946769 1.7
Bug #946769 [open-font-design-toolkit] Please remove dependency on fontypython 
(RC buggy, marked for removal)
Marked as found in versions open-font-design-toolkit/1.7.
> thanks
Stopping processing here.

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

Bug#945920: Chrome bug

[Alexander Chernaev]

Dear Maintainer,

I confirm experiencing the same crash with chromium version 79.0.3945.79-1 
installed from sid repos. It does happen very often on my system - after only 
5-15 minutes of watching videos.

Tried PPHome2's suggestion, but it did not help. The crash occurs within the 
same time period.

Bug#946040: marked as done (Build fails with the new pylint version)

[Debian Bug Tracking System]

Your message dated Mon, 16 Dec 2019 11:20:02 +
with message-id 
and subject line Bug#946040: fixed in pytest-pylint 0.14.1-3
has caused the Debian Bug report #946040,
regarding Build fails with the new pylint version
to be marked as done.

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

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


-- 
946040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pytest-pylint
Version: 0.14.1-2

The build is failing with pylint 2.4.4, log example from an Ubuntu build
https://launchpadlibrarian.net/454058807/buildlog_ubuntu-focal-amd64.pytest-pylint_0.14.1-2_BUILDING.txt.gz

I've reported the issue upstream
https://github.com/carsongee/pytest-pylint/issues/105

The debdiff attached should fix the issue

Cheers,

diff -Nru pytest-pylint-0.14.1/debian/changelog 
pytest-pylint-0.14.1/debian/changelog
--- pytest-pylint-0.14.1/debian/changelog   2019-11-19 08:01:18.0 
+0100
+++ pytest-pylint-0.14.1/debian/changelog   2019-12-03 11:06:41.0 
+0100
@@ -1,3 +1,10 @@
+pytest-pylint (0.14.1-3) unstable; urgency=medium
+
+  * debian/patches/import_warning_fix.patch:
+- reorder imports to fix pylint import-outside-toplevel warnings
+
+ -- Sebastien Bacher   Tue, 03 Dec 2019 10:58:36 +0100
+
 pytest-pylint (0.14.1-2) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru pytest-pylint-0.14.1/debian/patches/import_warning_fix.patch 
pytest-pylint-0.14.1/debian/patches/import_warning_fix.patch
--- pytest-pylint-0.14.1/debian/patches/import_warning_fix.patch
1970-01-01 01:00:00.0 +0100
+++ pytest-pylint-0.14.1/debian/patches/import_warning_fix.patch
2019-12-03 11:02:18.0 +0100
@@ -0,0 +1,39 @@
+# Description: build was failing on pylint import-outside-toplevel tests
+# Upstream: https://github.com/carsongee/pytest-pylint/issues/105
+#
+--- test-pytest/test_pytest_pylint.py  2019-01-15 14:10:38.0 +0100
 test-pytest/test_pytest_pylint.py.new  2019-12-03 10:57:27.668814673 
+0100
+@@ -3,7 +3,8 @@
+ Unit testing module for pytest-pylint plugin
+ """
+ import mock
+-
++from pytest_pylint import get_rel_path
++from pytest_pylint import include_file
+ 
+ pytest_plugins = ('pytester',)  # pylint: disable=invalid-name
+ 
+@@ -128,7 +129,6 @@
+ """
+ Verify our relative path function.
+ """
+-from pytest_pylint import get_rel_path
+ correct_rel_path = 'How/Are/You/blah.py'
+ path = '/Hi/How/Are/You/blah.py'
+ parent_path = '/Hi/'
+@@ -168,7 +168,6 @@
+ Files should only be included in the list if none of the directories on
+ it's path, of the filename, match an entry in the ignore list.
+ """
+-from pytest_pylint import include_file
+ ignore_list = [
+ "first", "second", "third", "part", "base.py"
+ ]
+@@ -191,7 +190,6 @@
+ 
+ def test_pylint_ignore_patterns():
+ """Test if the ignore-patterns is working"""
+-from pytest_pylint import include_file
+ ignore_patterns = [
+ "first.*",
+ ".*second",
diff -Nru pytest-pylint-0.14.1/debian/patches/series 
pytest-pylint-0.14.1/debian/patches/series
--- pytest-pylint-0.14.1/debian/patches/series  2019-07-25 14:03:35.0 
+0200
+++ pytest-pylint-0.14.1/debian/patches/series  2019-12-03 10:59:16.0 
+0100
@@ -1,2 +1,3 @@
 0001-Removed-PEP8-py.test-plugin.patch
 0002-Disable-abstract-method-pylint-check.patch
+import_warning_fix.patch
--- End Message ---
--- Begin Message ---
Source: pytest-pylint
Source-Version: 0.14.1-3

We believe that the bug you reported is fixed in the latest version of
pytest-pylint, 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.
Ondřej Nový  (supplier of updated pytest-pylint 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 11:54:52 +0100
Source: pytest-pylint
Architecture: source
Version: 0.14.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Closes: 946040
Changes:
 pytest-pylint (0.14.1-3) unstable; urgency=medium
 .
   [ 

Bug#946828: openblas: Fails to install during autopkgtests

[Dimitri John Ledkov]

Source: openblas
Version: 0.3.7+ds-6
Severity: serious

Dear Maintainer,

openblas appears to fails its autopackagetests with failure to install the 
librararies

Setting up libopenblas64-serial-dev:amd64 (0.3.7+ds-6) ...
update-alternatives: using 
/usr/lib/x86_64-linux-gnu/openblas64-serial/libblas64.so to provide 
/usr/lib/x86_64-linux-gnu/libblas64.so (libblas64.so-x86_64-linux-gnu) in auto 
mode
update-alternatives: error: error creating symbolic link 
'/usr/lib/x86_64-linux-gnu/pkgconfig/blas64.pc.dpkg-tmp': No such file or 
directory
dpkg: error processing package libopenblas64-serial-dev:amd64 (--configure):
 installed libopenblas64-serial-dev:amd64 package post-installation script 
subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of autopkgtest-satdep:
 autopkgtest-satdep depends on libopenblas64-serial-dev; however:
  Package libopenblas64-serial-dev:amd64 is not configured yet.


Something is wrong with pkgconfig files packaging / maintainer scripts?

Regards,

Dimitri.

Processed: your mail

[Debian Bug Tracking System]

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

> notfound #946816 archmage/1:0.3.1-4
Bug #946816 [archmage] archmage 1:0.4.0-1 is missing a dependency on 
python3-sgmllib3k
No longer marked as found in versions archmage/1:0.3.1-4.
>
End of message, stopping processing here.

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

Bug#946817: botch ftbfs, fails tests on 32bit archs

[Matthias Klose]

Package: src:botch
Version: 0.22-1
Severity: serious
Tags: sid bullseye

botch ftbfs, fails tests on all 32bit archs.

Processed: your mail

[Debian Bug Tracking System]

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

> found #946816 archmage/1:0.4.0-1
Bug #946816 [archmage] archmage 1:0.4.0-1 is missing a dependency on 
python3-sgmllib3k
Marked as found in versions archmage/1:0.4.0-1.
>
End of message, stopping processing here.

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

Bug#946816: archmage 1:0.4.0-1 is missing a dependency on python3-sgmllib3k

[Mikhail Gusarov]

Package: archmage
Version: 1:0.3.1-4
Severity: grave
Justification: renders package unusable

archmage 0.4 has introduced the dependency on sgmllib3k. This library has not 
yet
entered Debian archive (sitting in NEW), so archmage is broken.

This bug is filed to prevent archmage 0.4 from entering testing until sgmllib3k 
is
available and a new package release can be uploaded

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

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

Versions of packages archmage depends on:
ii  python 2.7.17-2
ii  python-bs4 4.8.0-2
ii  python-chm 0.8.4.1-3+b1
ii  python-lxml4.4.1-1+b1
ii  python-setuptools  41.4.0-1

archmage recommends no packages.

Versions of packages archmage suggests:
pn  elinks | links 
pn  htmldoc
pn  libapache2-mod-python  

-- no debconf information