Bug#951825: src:gambc: fails to migrate to testing for too long

[Paul Gevers]

Source: gambc
Version: 4.8.8-3.1
Severity: serious
Control: fixed -1 4.9.3-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:gambc in its
current version in unstable has been trying to migrate for 279 days.
Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have marked the version in unstable as fixing this bug, so if that
version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html




signature.asc
Description: OpenPGP digital signature

Processed: src:gambc: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 4.9.3-1
Bug #951825 [src:gambc] src:gambc: fails to migrate to testing for too long
Marked as fixed in versions gambc/4.9.3-1.

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

Bug#951824: stimfit needs a source only upload.

[peter green]

Package: stimfit
Version: 0.16.0-1
Severity: serious

The release team have decreed that non-buildd binaries can no longer migrate to 
testing. Please make a source-only upload so your package can migrate (and 
preferablly fix https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948020 at the 
same time).

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

[Sandro Tosi]

Control: reopen -1

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

(binary:svgtoipe)Recommends->python-pil

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

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

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #936740 {Done: Steve Robbins } [src:ipe-tools] ipe-tools: 
Python2 removal in sid/bullseye
Bug reopened
Ignoring request to alter fixed versions of bug #936740 to the same values 
previously set

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

Bug#937166: nuitka: Python2 removal in sid/bullseye - reopen 937166

[Sandro Tosi]

Control: reopen -1

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

(source:nuitka)Build-Depends->python
(source:nuitka)Build-Depends->python-all-dbg
(source:nuitka)Build-Depends->python-all-dev
(source:nuitka)Build-Depends->python-setuptools
(source:nuitka)Build-Depends->python-appdirs
(source:nuitka)Build-Depends->python-pil
(binary:nuitka)Depends->python-dev
(binary:nuitka)Recommends->python-lxml

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

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

[Debian Bug Tracking System]

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

> unarchive 936740
Bug #936740 {Done: Steve Robbins } [src:ipe-tools] ipe-tools: 
Python2 removal in sid/bullseye
Unarchived Bug 936740
>
End of message, stopping processing here.

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

Processed: nuitka: Python2 removal in sid/bullseye - reopen 937166

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#951821: gegl: FTBFS on arm*/mips* architectures; testing migration blocked

[Boyuan Yang]

Source: gegl
Version: 0.4.18-2
Severity: serious
Justification: out-of-sync unstable-to-testing
X-Debbugs-CC: jbi...@debian.org

Dear gegl maintainers,

The latest upload of package gegl was made on 2019-11-21 and it never migrated
to Debian Testing. According to 
https://lists.debian.org/debian-devel-announce/2020/02/msg5.html ,
packages that are out-of-sync between testing and unstable for more than 60
days are considered as having Release Critical bugs. This is blocking reverse-
dependencies like GIMP from migrating to Testing.

Looking into the current status, it fails to build on all ARM and MIPS
architectures. The reasons are mostly timeout in tests. Please make some
investigation and consider increasing the timeout limit or ignore test errors
during building.

-- 
Regards,
Boyuan Yang


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

Bug#947857: marked as done (golang-github-juju-testing: Remove depends/build-depends on src:mongodb)

[Debian Bug Tracking System]

Your message dated Sat, 22 Feb 2020 02:51:47 +
with message-id 
and subject line Bug#951791: Removed package(s) from unstable
has caused the Debian Bug report #947857,
regarding golang-github-juju-testing: Remove depends/build-depends on 
src:mongodb
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.)


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

Hello,
this package still depends/build-depends on a binary package from src:mongodb.
As mentioned in #947743, there are several issues with mongodb:

* rc-buggy
* un-upgreadable due to license issues
* not part of stable
* preventing some py2rm work

and so we're trying to remove it from Debian as it doesnt provide a good
enough solution nor provides an actual service to our users (who very likely
want to get a latest version of mongodb, which we cant provide).

Please remove the dependency (either binary of build-) from this package.

Regards,
Sandro
--- End Message ---
--- Begin Message ---
Version: 0.0~git20170608.2fe0e88-3+rm

Dear submitter,

as the package golang-github-juju-testing 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/951791

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#919089: marked as done (Please remove (build-)dependency on mongodb for buster)

[Debian Bug Tracking System]

Your message dated Sat, 22 Feb 2020 02:51:47 +
with message-id 
and subject line Bug#951791: Removed package(s) from unstable
has caused the Debian Bug report #919089,
regarding Please remove (build-)dependency on mongodb for buster
to be marked as done.

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

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


-- 
919089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mongodb
Version: 1:3.4.15-1
Severity: serious
Justification: Cannot be properly supported

MongoDB should not be part of (at least) Buster for the following 
reasons:

 - MongoDB 3.4 will be EOL by June 2019[1], which is way too soon for it 
   to be included in Buster.

 - MongoDB 3.6 and 4.0 will be supported longer, but upstream's switch 
   to SSPLv1 complicates matters. As discussed in #915537, we will not 
   be distributing any SSPL-licensed software, and keeping the last 
   AGPL-licensed version (3.6.8 or 4.0.3) without the ability to 
   cherry-pick upstream fixes is not a viable option. (I am currently 
   not considering distributing mongodb in non-free.)

I will not request removal immediately, to allow other packages time to 
adjust their dependencies, but eventually auto-removal will kick in.  

That said, MongoDB 3.4 will probably remain in sid for as long as it is 
AGPL-licensed and supported upstream.

Apollon

[1] https://www.mongodb.com/support-policy
--- End Message ---
--- Begin Message ---
Version: 0.0~git20170608.2fe0e88-3+rm

Dear submitter,

as the package golang-github-juju-testing 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/951791

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#947855: marked as done (php-php-mongodb: Remove depends/build-depends on src:mongodb)

[Debian Bug Tracking System]

Your message dated Sat, 22 Feb 2020 02:49:56 +
with message-id 
and subject line Bug#951795: Removed package(s) from unstable
has caused the Debian Bug report #947855,
regarding php-php-mongodb: Remove depends/build-depends on src:mongodb
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.)


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

Hello,
this package still depends/build-depends on a binary package from src:mongodb.
As mentioned in #947743, there are several issues with mongodb:

* rc-buggy
* un-upgreadable due to license issues
* not part of stable
* preventing some py2rm work

and so we're trying to remove it from Debian as it doesnt provide a good
enough solution nor provides an actual service to our users (who very likely
want to get a latest version of mongodb, which we cant provide).

Please remove the dependency (either binary of build-) from this package.

Regards,
Sandro
--- End Message ---
--- Begin Message ---
Version: 1.4.3-1+rm

Dear submitter,

as the package php-php-mongodb 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/951795

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#943045: marked as done (django-compat: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 22 Feb 2020 02:49:17 +
with message-id 
and subject line Bug#944051: Removed package(s) from unstable
has caused the Debian Bug report #943045,
regarding django-compat: 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.)


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

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

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

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

  This is the least preferred option.

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

Dear submitter,

as the package django-compat 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/944051

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#885299: marked as done (griffith: Depends on unmaintained pygtk)

[Debian Bug Tracking System]

Your message dated Sat, 22 Feb 2020 02:50:47 +
with message-id 
and subject line Bug#951792: Removed package(s) from unstable
has caused the Debian Bug report #885299,
regarding griffith: Depends on unmaintained pygtk
to be marked as done.

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

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


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

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

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

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

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

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

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

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 0.13+20140313-1+rm

Dear submitter,

as the package griffith 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/951792

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#936661: marked as done (griffith: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 22 Feb 2020 02:50:47 +
with message-id 
and subject line Bug#951792: Removed package(s) from unstable
has caused the Debian Bug report #936661,
regarding griffith: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:griffith

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

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

Dear submitter,

as the package griffith 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/951792

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#866429: marked as done (griffith: depends on obsolete python-imaging (replace with python3-pil or python-pil))

[Debian Bug Tracking System]

Your message dated Sat, 22 Feb 2020 02:50:47 +
with message-id 
and subject line Bug#951792: Removed package(s) from unstable
has caused the Debian Bug report #866429,
regarding griffith: depends on obsolete python-imaging (replace with 
python3-pil or python-pil)
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.)


-- 
866429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:griffith
Version: 0.13+20140313-1
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.
--- End Message ---
--- Begin Message ---
Version: 0.13+20140313-1+rm

Dear submitter,

as the package griffith 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/951792

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#936414: marked as done (django-compat: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 22 Feb 2020 02:49:17 +
with message-id 
and subject line Bug#944051: Removed package(s) from unstable
has caused the Debian Bug report #936414,
regarding django-compat: 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.)


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

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

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


--- End Message ---
--- Begin Message ---
Version: 1.0.15-2+rm

Dear submitter,

as the package django-compat 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/944051

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#932827: marked as done (django-compat: broken with Django 2.2, FTBFS, not ready)

[Debian Bug Tracking System]

Your message dated Sat, 22 Feb 2020 02:49:17 +
with message-id 
and subject line Bug#944051: Removed package(s) from unstable
has caused the Debian Bug report #932827,
regarding django-compat: broken with Django 2.2, FTBFS, not ready
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.)


-- 
932827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-compat
Version: 1.0.15-2
Severity: serious

Hi,

Django-compat is broken in may ways currently.

1/ It's using the loginview function instead of the LoginView class, as per
the deprecation in Django 1.11.
2/ The tests/settings.py is missing lots of declarations.
3/ Python 2 support has to be removed from this package.

I tried to work on this, but it doesn't look trivial.

Cheers,

Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
Version: 1.0.15-2+rm

Dear submitter,

as the package django-compat 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/944051

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#947856: marked as done (php-mongo-php-adapter: Remove depends/build-depends on src:mongodb)

[Debian Bug Tracking System]

Your message dated Sat, 22 Feb 2020 02:50:20 +
with message-id 
and subject line Bug#951793: Removed package(s) from unstable
has caused the Debian Bug report #947856,
regarding php-mongo-php-adapter: Remove depends/build-depends on src:mongodb
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.)


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

Hello,
this package still depends/build-depends on a binary package from src:mongodb.
As mentioned in #947743, there are several issues with mongodb:

* rc-buggy
* un-upgreadable due to license issues
* not part of stable
* preventing some py2rm work

and so we're trying to remove it from Debian as it doesnt provide a good
enough solution nor provides an actual service to our users (who very likely
want to get a latest version of mongodb, which we cant provide).

Please remove the dependency (either binary of build-) from this package.

Regards,
Sandro
--- End Message ---
--- Begin Message ---
Version: 1.1.11-1+rm

Dear submitter,

as the package php-mongo-php-adapter 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/951793

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#951281: marked as done (widelands FTBFS: SDL2 include dir not found)

[Debian Bug Tracking System]

Your message dated Sat, 22 Feb 2020 02:43:50 +
with message-id 
and subject line Bug#951281: fixed in widelands 1:20-2
has caused the Debian Bug report #951281,
regarding widelands FTBFS: SDL2 include dir not found
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.)


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

Source: widelands
Version: 1:20-1
Severity: serious
Justification: ftbfs
Tags: ftbfs

Dear Maintainer,

Widelands currently fails to build in Sid with the following error 
message:

...
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_893c8.dir/link.txt 
--verbose=1
/usr/bin/cc -g -O2 -fdebug-prefix-map=/build/widelands-20=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 
-DCHECK_FUNCTION_EXISTS=pthread_create  -Wl,-z,relro  -rdynamic 
CMakeFiles/cmTC_893c8.dir/CheckFunctionExists.c.o  -o cmTC_893c8  
-lpthreads

/usr/bin/ld: cannot find -lpthreads
collect2: error: ld returned 1 exit status
make[3]: *** [CMakeFiles/cmTC_893c8.dir/build.make:87: cmTC_893c8] Error 
1
make[3]: Leaving directory 
'/build/widelands-20/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'

make[2]: *** [Makefile:121: cmTC_893c8/fast] Error 2
make[2]: Leaving directory 
'/build/widelands-20/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'




dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake 
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DWL_INSTALL_BASEDIR=/usr/share/games/widelands 
-DWL_INSTALL_BINDIR=games 
-DWL_INSTALL_DATADIR=/usr/share/games/widelands/data 
-DWL_INSTALL_PREFIX=/usr -DOPTION_BUILD_WEBSITE_TOOLS=OFF 
-DCMAKE_BUILD_TYPE=Release .. returned exit code 1

make[1]: *** [debian/rules:14: override_dh_auto_configure] Error 25
make[1]: Leaving directory '/build/widelands-20'
make: *** [debian/rules:10: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
status 2




I suspect the important part is "/usr/bin/ld: cannot find -lpthreads", 
which I suppose
might be due to some underlying library change though I haven't figured 
it out. Saw the
same error message when the package was rebuilt in Ubuntu, and I guess 
other

packages using -lpthreads might suffer the same fate.

Tried rebuilding the current upstream development version to see if it 
had a fix,

but ran into a separate issue.

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

Kernel: Linux 5.4.0-3-amd64 (SMP w/3 CPU cores)
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)
LSM: AppArmor: enabled


--
mvh / best regards
Hans Joachim Desserud
http://desserud.org
--- End Message ---
--- Begin Message ---
Source: widelands
Source-Version: 1:20-2
Done: Markus Koschany 

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated widelands package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 22 Feb 2020 00:16:24 +0100
Source: widelands
Architecture: source
Version: 1:20-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Closes: 951281
Changes:
 widelands (1:20-2) unstable; urgency=medium
 .
   [ Juhani Numminen ]
   * Team upload.
   * Use SDL2 CMake integration. Fixes FTBFS caused by FindSDL2.cmake being out
 of sync with SDL2. (Closes: #951281)
 .
   [ Markus Koschany ]
   * Declare compliance with Debian Policy 4.5.0.
Checksums-Sha1:
 

Bug#951818: sslstrip: should this package be removed?

[Sandro Tosi]

Package: sslstrip
Severity: serious

Hello,
i think sslstrip should be removed from Debian:

* python2 only app
* low popcon
* only r-dep is websploit, recently removed from testing, and which doesnt use
  sslstrip anymore in the latest upstream release
* last upstream release and debian upload in 2011 (!)
* dead upstream, https://github.com/moxie0/sslstrip/issues/16 and render mostly
  obsolete

If i dont hear back within a week with a good reason to keep this package in
Debian, i'll file for its removal.

Regards,
Sandro

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

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

Versions of packages sslstrip depends on:
ii  python  2.7.16-1
pn  python-twisted-web  

sslstrip recommends no packages.

sslstrip suggests no packages.

Bug#951281: FTBFS: /usr/bin/ld: cannot find -lpthreads

[Markus Koschany]

On Wed, 19 Feb 2020 22:24:05 +0200 Juhani Numminen
 wrote:
> Markus Koschany kirjoitti 19.2.2020 klo 20.32:
> > Hello Juani,
> > 
> > Am 15.02.20 um 09:49 schrieb Juhani Numminen:
> > [...]
> >> Markus, you have made team uploads of widelands before. I wonder if you
> >> could make an upload that adds the patch?
> > 
> > Could you adjust the patch to use the same mechanism to find SDL2 as in
> > openjk?
> 
> I actually started to work on that after receiving Simon's message, and
> have now pushed the revised patch to a branch for your consideration.
> 
> https://salsa.debian.org/games-team/widelands/commit/e470cba2029c459d3ab1bb6c385bfd4746a9dd05
> 
> --
> Juhani

Thanks for the update! I have just uploaded a new revision to unstable.

Best,

Markus



signature.asc
Description: OpenPGP digital signature

Processed: Bug#951281 marked as pending in widelands

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #951281 [src:widelands] widelands FTBFS: SDL2 include dir not found
Ignoring request to alter tags of bug #951281 to the same tags previously set

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

Bug#951281: marked as pending in widelands

[Markus Koschany]

Control: tag -1 pending

Hello,

Bug #951281 in widelands 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/games-team/widelands/commit/e470cba2029c459d3ab1bb6c385bfd4746a9dd05


Use SDL2 CMake integration. Fixes FTBFS caused by FindSDL2.cmake being out of 
sync with SDL2.

Closes: #951281


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/951281

Bug#951691: marked as done (src:ruby-prawn-svg: fails to migrate to testing for too long)

[Debian Bug Tracking System]

Your message dated Sat, 22 Feb 2020 00:19:31 +
with message-id 
and subject line Bug#951691: fixed in ruby-prawn-svg 0.29.1-2
has caused the Debian Bug report #951691,
regarding src:ruby-prawn-svg: fails to migrate to testing for too long
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.)


-- 
951691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951691
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-prawn-svg
Version: 0.28.0-3
Severity: serious
Control: fixed -1 0.29.1-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package
src:ruby-prawn-svg in its current version in unstable has been trying to
migrate for 346 days. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have marked the version in unstable as fixing this bug, so if that
version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ruby-prawn-svg
Source-Version: 0.29.1-2
Done: Daniel Leidert 

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

Debian distribution maintenance software
pp.
Daniel Leidert  (supplier of updated ruby-prawn-svg 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 22 Feb 2020 00:49:54 +0100
Source: ruby-prawn-svg
Architecture: source
Version: 0.29.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Daniel Leidert 
Closes: 951691
Changes:
 ruby-prawn-svg (0.29.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Source upload to allow migration to testing (closes: #951691).
Checksums-Sha1:
 5c2b18004e2ab3704c9a7900bffdfc324ee577ed 2114 ruby-prawn-svg_0.29.1-2.dsc
 11c81fab2b23a841c40f697b5bec4710d4a1a29e 2260 
ruby-prawn-svg_0.29.1-2.debian.tar.xz
 d982e9e2df7eba2627d9f894183edefca4169330 9332 
ruby-prawn-svg_0.29.1-2_amd64.buildinfo
Checksums-Sha256:
 f3b64e8b333c4b91614d8af8f5ed36c0e9f44d1bc4f71c300583648603311ffe 2114 
ruby-prawn-svg_0.29.1-2.dsc
 03385454788fc8589ec04829df00ba1a197707ead9567a76ecdee86a7a2b7b40 2260 
ruby-prawn-svg_0.29.1-2.debian.tar.xz
 a3648d5b295cb1f3f5614633d1c76f49e990ae423783c528e11af7efee60cc2b 9332 
ruby-prawn-svg_0.29.1-2_amd64.buildinfo
Files:
 9d4dac7f6983459c94bea517db7c6009 2114 ruby optional ruby-prawn-svg_0.29.1-2.dsc
 c1ab888f9f32e4bb82840f77d4bb5cae 2260 ruby optional 
ruby-prawn-svg_0.29.1-2.debian.tar.xz
 aaf47c43bcc646b181d42ab34dfab82c 9332 ruby optional 
ruby-prawn-svg_0.29.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl5QbjUACgkQS80FZ8KW
0F18RxAAynK6IfrlfoFX9SJEPW7JA/3Am5LML1JLGi+c6cpY+EUmorlOwZsdyWw1
Ml+68I8oy7sxuh7Ws1wNYNqcFurX77UpN2p3VAzPD4P9yQD1seeBExDSj8eohxZb
lZLtCWHAiVkjSiHzaH+s7PQBS+wKn9A/VP8p8Kqe7LVvYM8H6QbYXkBtBqDk94lY
B+8q5aD8NWseoJ5ydXUl/SzqmGDtIcyPjl4F3/MAt4//pOFBRK8tAUcBVH+IymFQ

Processed: Fix for 949301 is pending

[Debian Bug Tracking System]

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

> tags 949301 pending
Bug #949301 [src:ufoai] ufoai: FTBFS: invalid use of incomplete type 
'mxml_node_t' {aka 'struct _mxml_node_s'}
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#936806: koji: Python2 removal in sid/bullseye

[Holger Levsen]

Hi,

On Fri, Feb 14, 2020 at 03:12:20AM +0100, Marek Marczykowski-Górecki wrote:
> > I mean, rpm is definitly still useful to have on Debian, but yum and 
> > friends???
> They are also useful in some cases. For example if you want to use
> Debian-based VM to download updates for your Qubes dom0...

hah, touche!

so for the record: while I can easily workaround the above problem by using a
Fedora based VM to download updates for my Qubes dom0, I'd be glad to help
people to get yum, dnf and rpm back into Debian, eg by sponsoring such uploads.


-- 
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: Re: Bug#951157: wireguard-dkms: DKMS make.log for wireguard-0.0.20200205 for kernel 5.3.9-sunxi (armv7l)

[Debian Bug Tracking System]

Processing control commands:

> severity 951157 normal
Bug #951157 [wireguard-dkms] wireguard-dkms: DKMS make.log for 
wireguard-0.0.20200205 for kernel 5.3.9-sunxi (armv7l)
Severity set to 'normal' from 'serious'
> tags 951157 + unreproducible moreinfo
Bug #951157 [wireguard-dkms] wireguard-dkms: DKMS make.log for 
wireguard-0.0.20200205 for kernel 5.3.9-sunxi (armv7l)
Added tag(s) moreinfo and unreproducible.

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

Bug#951157: wireguard-dkms: DKMS make.log for wireguard-0.0.20200205 for kernel 5.3.9-sunxi (armv7l)

[Daniel Kahn Gillmor]

Control: severity 951157 normal
Control: tags 951157 + unreproducible moreinfo

Hi Carlos--

On Thu 1970-01-01 00:00:00 +, carlosnewmusic wrote:
>* What led up to the situation?
> wireguard metapackage installation
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> install, install kernel headers, but it's useless
>* What was the outcome of this action?
> error 10 in the construction of the dkms package
>* What outcome did you expect instead?
> that the module and wireguard will be installed correctly

This sounds frustrating!  However, it doesn't look like you're using the
debian kernel, or the debian kernel header packages.

The kernel you're using:

> Kernel: Linux 5.3.9-sunxi (SMP w/4 CPU cores)

isn't in debian at all, afaict.

> DKMS make.log for wireguard-0.0.20191226 for kernel 5.3.9-sunxi (armv7l)
> lun ene 20 04:47:15 CET 2020
> make: se entra en el directorio '/usr/src/linux-headers-5.3.9-sunxi'
>   CC [M]  /var/lib/dkms/wireguard/0.0.20191226/build/main.o
>   CC [M]  /var/lib/dkms/wireguard/0.0.20191226/build/noise.o
>   CC [M]  /var/lib/dkms/wireguard/0.0.20191226/build/device.o
>   CC [M]  /var/lib/dkms/wireguard/0.0.20191226/build/peer.o
> /bin/sh: 1: ./scripts/recordmcount: not found

this error makes me think that you don't have the appropriate
linux-kbuild packages installed.  for example:
https://packages.debian.org/sid/armhf/linux-kbuild-5.4/filelist
shows that it contains the recordmcount script (you can find this by
searching the packages database:


https://packages.debian.org/search?suite=sid=armhf=filename=contents=recordmcount

So you might want to try installing some matching kbuild package and see
whether it works for you or not -- though i don't think that
linux-kbuild-5.3 is available anywhere except for snapshots:

   https://snapshot.debian.org/binary/linux-kbuild-5.3/

(see https://snapshot.debian.org/ on how to use the snapshots service)

Please report back and let me know if you run into the same problem when
you have linux-kbuild-5.3 installed!

--dkg


signature.asc
Description: PGP signature

Bug#947856: php-mongo-php-adapter: Remove depends/build-depends on src:mongodb

[David Prévot]

Le 21/02/2020 à 10:32, Moritz Mühlenhoff a écrit :
> On Thu, Feb 20, 2020 at 04:17:48PM -1000, David Prévot wrote:
>> Le 20/02/2020 à 12:43, Moritz Mühlenhoff a écrit :
>>
>>> let's remove this (and php-php-mongodb)? There are no rev deps in the 
>>> archive
>>
>> Sure, please proceed. […]

> Ack, I've just filed removal bugs.

Thanks Moritz!



signature.asc
Description: OpenPGP digital signature

Bug#947251: marked as done (mypaint: Please build-depend on python-gi in addition to python-gi-dev)

[Debian Bug Tracking System]

Your message dated Fri, 21 Feb 2020 23:09:37 +
with message-id 
and subject line Bug#947251: fixed in mypaint 2.0.0-1~exp1
has caused the Debian Bug report #947251,
regarding mypaint: Please build-depend on python-gi in addition to python-gi-dev
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.)


-- 
947251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mypaint
Version: 1.2.0-5
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: python-gi-dev-945022
Control: block 945022 by -1

Please see https://salsa.debian.org/gnome-team/pygobject/merge_requests/2
for the latest information on this transition.

python-gi-dev contains development files (pkg-config metadata and header
file) corresponding to both python-gi and python3-gi.

At the moment, python-gi-dev Depends on both python-gi and python3-gi.
The GNOME team would like to drop the python-gi dependency, to make the
status of Python 2 removal easier to track.

The package receiving this bug is one of a few packages that build-depend
on python-gi-dev and appear to build Python 2 bindings. With the proposed
changes to pygobject, mypaint fails to build from source:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
# Max-RSS: ~74000 kbytes
MPLCONFIGDIR=`mktemp -d` python tests/test_mypaintlib.py
Traceback (most recent call last):
  File "tests/test_mypaintlib.py", line 11, in 
from lib import mypaintlib, tiledsurface, brush, document, command, 
helpers
  File "../lib/tiledsurface.py", line 21, in 
from gettext import gettext as _
  File "../lib/gettext.py", line 30, in 
from gi.repository import GLib
ImportError: No module named gi.repository

If mypaint continues to use Python 2, please add python-gi to its
Build-Depends. Alternatively, if mypaint moves to Python 3 (#937099),
you can close this bug in that upload.

This bug's severity will be increased to serious if it is still open
when python-gi-dev's dependency on python-gi is removed in unstable.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: mypaint
Source-Version: 2.0.0-1~exp1
Done: Boyuan Yang 

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated mypaint package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 21 Feb 2020 16:36:17 -0500
Source: mypaint
Architecture: source
Version: 2.0.0-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Boyuan Yang 
Closes: 853938 897909 928075 932868 937099 947251 947570
Changes:
 mypaint (2.0.0-1~exp1) experimental; urgency=medium
 .
   * Team upload.
   * New upstream release 2.0.0. (Closes: #853938)
 + Migrate away from scons. (Closes: #947570)
 + Migrate away from python2. (Closes: #937099)
 + The conflict between libmypaint-common and mypaint-data is
   solved by upstream. (Closes: #897909, #932868)
   * debian/control:
 + Bump debhelper compat to v12.
 + Bump Standards-Version to 4.5.0.
 + Migrate to python3. (Closes: #947251)
 + Update homepage information. (Closes: #928075)
 + Add (build-)dependency on new libmypaint.
   * debian/patches: Dropped, all merged upstream.
   * debian/upstream/metadata: Add upstream information: Repository,
 Repository-Browse.
   * debian/rules: Rewrite to fit upstream's use of setup.py.
 .
   [ Sandro Tosi ]
   * debian/watch
 - recognize beta versions too
Checksums-Sha1:
 f2ad7514627939b6c797b3549697ba97339f2547 2436 mypaint_2.0.0-1~exp1.dsc
 334fa13893d20c80805092de665dbbcf03b92ece 7316680 mypaint_2.0.0.orig.tar.xz
 65edd222af7d3ca9ae212125044dd16fa8e5e1e3 20836 
mypaint_2.0.0-1~exp1.debian.tar.xz
 48eff9243f58699e9f5e23a7d0a14117950598ca 15776 
mypaint_2.0.0-1~exp1_amd64.buildinfo
Checksums-Sha256:
 

Bug#951743: marked as done (OpenSSL linking without license exception)

[Debian Bug Tracking System]

Your message dated Fri, 21 Feb 2020 22:35:00 +
with message-id 
and subject line Bug#951743: fixed in calibre 4.99.4+dfsg+really4.11.1-1
has caused the Debian Bug report #951743,
regarding OpenSSL linking without license exception
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.)


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

This package links to OpenSSL even though it does not have any license
exception for it. ftp-master considers this a serious issue. Please
build without the certgen extension or try to build with an OpenSSL API
compatible library like wolfssl.
--- End Message ---
--- Begin Message ---
Source: calibre
Source-Version: 4.99.4+dfsg+really4.11.1-1
Done: Norbert Preining 

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

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated calibre package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 21 Feb 2020 22:28:02 +0900
Source: calibre
Architecture: source
Version: 4.99.4+dfsg+really4.11.1-1
Distribution: unstable
Urgency: medium
Maintainer: Norbert Preining 
Changed-By: Norbert Preining 
Closes: 951743
Changes:
 calibre (4.99.4+dfsg+really4.11.1-1) unstable; urgency=medium
 .
   [ Norbert Preining ]
   * add change for 4.10.1 as patch
   * move Debian patches after Py3 patches
   * do not build/install certgen extension/module (Closes: #951743)
   * New upstream version 4.99.4+dfsg+really4.11.{0,1}
   * update py3 branch patches
   * fix patches that touch thumbpdf.py which is removed during orig.tar 
building
   * required patch for py3 branch
 .
   [ YOKOTA Hiroshi ]
   * Restore release version's watch line
   * Update version mangle line for "+really" style version number
   * Remove unused line
   * Apply Debian's compilation options to libheadless.so
   * New upstream version 4.99.4+dfsg+really4.10.1
   * Drop obsolete patch.
 This already patch applied in upstream
   * Remove unused patch
   * Refresh Debian patches
   * Move upstream "py3" branch to Quilt patch set
   * Refresh "py3" patches
   * Add ignored file list to dh_missing(1)
 "py3" branch already removed this file, but quilt(1) dose not handle
 deletion of blank file. And upstream install process installs some
 unwanted files.
   * Add "py3" branch document
   * Fix upstream version naming scheme
 "+py3" is not comes from upstream tarball.
 It comes from patch set.
   * Break lines
Checksums-Sha1:
 e6b991a11a2e5fe033cabe971eeb8f0909b7fe2f 2888 
calibre_4.99.4+dfsg+really4.11.1-1.dsc
 09479ccd2ae516769ff5b34cbcedf33b6d917341 38044096 
calibre_4.99.4+dfsg+really4.11.1.orig.tar.xz
 aa0226efa790e63548ddf0f1ca57f3b7d739a18e 316024 
calibre_4.99.4+dfsg+really4.11.1-1.debian.tar.xz
 9bf66173e59bbe4297306ffe64b90b817d40a881 19309 
calibre_4.99.4+dfsg+really4.11.1-1_source.buildinfo
Checksums-Sha256:
 029531af06e4ca30a15b9840649ae0af0582467ea8403e7dcc3906e1fdc85277 2888 
calibre_4.99.4+dfsg+really4.11.1-1.dsc
 6aa005c9622b9dcd39d98a6cb7946248447abb6d8ea30fd2829b1804954284ed 38044096 
calibre_4.99.4+dfsg+really4.11.1.orig.tar.xz
 f2cc2191b11b8bf3f6cc01510b870d36c9741d5ae4c250aa4a873b8a7890f3f5 316024 
calibre_4.99.4+dfsg+really4.11.1-1.debian.tar.xz
 d41504bf268dad5a7dc34dca40dc031ddfdce06a4388cde459d9f2d7355a1a65 19309 
calibre_4.99.4+dfsg+really4.11.1-1_source.buildinfo
Files:
 cbac84e89c8573fef606247beed73f59 2888 text optional 
calibre_4.99.4+dfsg+really4.11.1-1.dsc
 ebb364e2dad2715636d5dc4af6cf1c61 38044096 text optional 
calibre_4.99.4+dfsg+really4.11.1.orig.tar.xz
 4a114672de2952f5fd9710cefdcfc6a6 316024 text optional 
calibre_4.99.4+dfsg+really4.11.1-1.debian.tar.xz
 792e03623e3a3bb420100d492268d18a 19309 text optional 
calibre_4.99.4+dfsg+really4.11.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE68ws0vrA2voQX53I2A4JsIcUAGYFAl5QWEwACgkQ2A4JsIcU

Bug#951806: ruby-serverengine: FTBFS aginst Ruby2.5 and Ruby2.7

[Utkarsh Gupta]

Package: ruby-serverengine
Version: 2.2.0-1
Severity: critical
User pkg-ruby-extras-maintain...@lists.alioth.debian.org
Usertags: ruby2.7-transition

Dear Maintainer,

Whilst building ruby-serverengine against Ruby2.5 and Ruby2.7, I
noticed that all the tests are failing and at one point, the tests
freeze.

I've forwarded this upstream:
https://github.com/treasure-data/serverengine/issues/104

Just FTR, this package has no reverse-dependencies or
reverse-build-dependencies. Is it a good sign for it to be filed for
removal?


Best,
Utkarsh

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

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

Versions of packages ruby-serverengine depends on:
ii  ruby  1:2.5.2
ii  ruby-sigdump  0.2.4-4

ruby-serverengine recommends no packages.

ruby-serverengine suggests no packages.

-- no debconf information

Bug#950112: gplaycli: 502 Bad Gateway, does not work at all

[Andres Salomon]

Thanks for your bug reports!

So at this point, I'm wondering what to do with the current package,
now that I've uploaded a version that fixes the other bugs. The package
is still useful to me as a means to grab apks, even though it required
adding a google login/password. I see a few different options:

1) Assume the token dispenser is completely broken, and fix up the
package to clearly document the procedure to get it working with a
google account. This would probably be a good thing to do anyways, since
people might want to not use the token dispenser for various reasons.

2) Try and get the token dispenser working on Debian infrastructure.
This may or may not work (and I'm not sure whether Debian admins would
frown upon using my people.d.o space for this kind of thing), but if it
did work then it would allow people to continue using the package
without having a google account. That said, I don't particularly like
having a utility that requires calling out to a third party site in
other to get auth credentials, even if it's a Debian site.

3) Cross my fingers and hope Matlink gets the token dispenser working
on his end. That's the easiest option for me, obviously. ;)

Thoughts?

Bug#948639: marked as done (rust-log depends on non-existent librust-sval-0.4+fmt-dev )

[Debian Bug Tracking System]

Your message dated Fri, 21 Feb 2020 21:32:20 +
with message-id 
and subject line Bug#948639: fixed in rust-log 0.4.8-3
has caused the Debian Bug report #948639,
regarding rust-log depends on non-existent librust-sval-0.4+fmt-dev 
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.)


-- 
948639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-log
Version: 0.4.8-2
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

Hi Sylvestre,

The rust-log package in unstable is not able to migrate to testing because
it builds binary packages that depend on a non-existent rust-sval:

librust-log+kv-unstable-sval-dev/amd64 unsatisfiable Depends: 
librust-sval-0.4+fmt-dev (>= 0.4.2-~~)
librust-log+sval-dev/amd64 unsatisfiable Depends: librust-sval-0.4-dev (>= 
0.4.2-~~)

There is no rust-sval package in the Debian archive or in the NEW queue.

Please take care to make sure your packages' dependencies are met.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: rust-log
Source-Version: 0.4.8-3
Done: Daniel Kahn Gillmor 

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated rust-log 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 21 Feb 2020 15:42:22 -0500
Source: rust-log
Architecture: source
Version: 0.4.8-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Daniel Kahn Gillmor 
Closes: 948639
Changes:
 rust-log (0.4.8-3) unstable; urgency=medium
 .
   * Team upload.
   * drop sval-related features (Closes: #948639)
   * Package log 0.4.8 from crates.io using debcargo 2.4.2
Checksums-Sha1:
 e70fcc484ae322238a98665c3cc8880a89b75c70 1622 rust-log_0.4.8-3.dsc
 4c874a7ecaab2b3f58ec2f41bcc0d6ca43282908 3448 rust-log_0.4.8-3.debian.tar.xz
 fb0930c073136b3ea221859bd42807610e57d181 7174 rust-log_0.4.8-3_source.buildinfo
Checksums-Sha256:
 96b5f7059319e83c349248912dd38932f58f0c2b806f81545d54501af4927bad 1622 
rust-log_0.4.8-3.dsc
 d8ee5ef3ccc724a3d884262c23fe245e32b5a569ceefd3cddb111b25477e5daf 3448 
rust-log_0.4.8-3.debian.tar.xz
 56b915a502473312af25a8284c7e07758964f17fa51f25411880c13664ba3d5a 7174 
rust-log_0.4.8-3_source.buildinfo
Files:
 39abfeb0dd831719d645f654542b960d 1622 rust optional rust-log_0.4.8-3.dsc
 fe538ba7c554492506afd64909edc34a 3448 rust optional 
rust-log_0.4.8-3.debian.tar.xz
 ce32c921e65ec5e74b5cc50448346519 7174 rust optional 
rust-log_0.4.8-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQQsv6x2UaqQJzY+dXHEDyVUMvKBDwUCXlBAswAKCRDEDyVUMvKB
D96vAP9FduCXXlFF5+Cue1yFaVgLsK0mBdQJjMBvIKZuMLn1kAD/YwVnAK67qbzs
SkJAzZK9Q6U+HOZbuNXDtgZm2U0peAs=
=njNp
-END PGP SIGNATURE End Message ---

Processed: bug 951778 is forwarded to https://github.com/intel/libva/issues/373, tagging 951778

[Debian Bug Tracking System]

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

> forwarded 951778 https://github.com/intel/libva/issues/373
Bug #951778 [libva2] libva2: NULL vtable when querying nvidia render device
Set Bug forwarded-to-address to 'https://github.com/intel/libva/issues/373'.
> tags 951778 + upstream
Bug #951778 [libva2] libva2: NULL vtable when querying nvidia render device
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: Re: Bug#951771: linux-source-5.4: linux 5.4.0-4 does not boot on this pc

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux 5.4.19-1
Bug #951771 [linux-source-5.4] linux-source-5.4: linux 5.4.0-4 does not boot on 
this pc
Bug reassigned from package 'linux-source-5.4' to 'src:linux'.
Ignoring request to alter found versions of bug #951771 to the same values 
previously set
Ignoring request to alter fixed versions of bug #951771 to the same values 
previously set
Bug #951771 [src:linux] linux-source-5.4: linux 5.4.0-4 does not boot on this pc
Marked as found in versions linux/5.4.19-1.
> severity -1 important
Bug #951771 [src:linux] linux-source-5.4: linux 5.4.0-4 does not boot on this pc
Severity set to 'important' from 'serious'
> tag -1 moreinfo
Bug #951771 [src:linux] linux-source-5.4: linux 5.4.0-4 does not boot on this pc
Added tag(s) moreinfo.

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

Bug#951771: linux-source-5.4: linux 5.4.0-4 does not boot on this pc

[Ben Hutchings]

Control: reassign -1 src:linux 5.4.19-1
Control: severity -1 important
Control: tag -1 moreinfo

On Fri, 2020-02-21 at 15:39 +0100, TS wrote:
> Package: linux-source-5.4
> Version: linux 5.4.0-4
> Severity: serious
> Justification: 1
> 
> Hi
> 
> did upgrade to sid. linux 5.4.0-4 does not boot on this pc.
> Booting 4.19.0-8-amd64 instead brings up running system.
> 
> The boot prozess breaks after grub. Blank screen, nothing happens.
> With 4.19.0-8-amd64 system boots up as expected.

Are we supposed to guess what "this pc" is?

Run "reportbug kernel" and add the information that it gathers to this
bug report.

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett




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

Bug#951799: rng-tools: No longer supports some options

[Kurt Roeckx]

Package: rng-tools
Version: 5-1
Severity: serious

I tried to upgrade from 2-unofficial-mt.14-1+b2 to 5-1, but
installation failed because --feed-interval and --rng-entropy
are no longer supported. 

It's non-trivial to found out what the problem is, no error message
is logged or displayed on the screen, things like strace don't
actually get to see the invocation. All that you systemd shows is
that it exited with 1.

I really need the --rng-entropy option. My RNG does not provide
much entropy.


Kurt

Processed: src:neurodebian: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.39.0
Bug #951796 [src:neurodebian] src:neurodebian: fails to migrate to testing for 
too long
Marked as fixed in versions neurodebian/0.39.0.

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

Bug#951796: src:neurodebian: fails to migrate to testing for too long

[Paul Gevers]

Source: neurodebian
Version: 0.38.3
Severity: serious
Control: fixed -1 0.39.0
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:neurodebian
in its current version in unstable has been trying to migrate for 304
days. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have marked the version in unstable as fixing this bug, so if that
version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html




signature.asc
Description: OpenPGP digital signature

Bug#947856: php-mongo-php-adapter: Remove depends/build-depends on src:mongodb

[Moritz Mühlenhoff]

On Thu, Feb 20, 2020 at 04:17:48PM -1000, David Prévot wrote:
> Hi Moritz,
> 
> Le 20/02/2020 à 12:43, Moritz Mühlenhoff a écrit :
> 
> > let's remove this (and php-php-mongodb)? There are no rev deps in the 
> > archive
> 
> Sure, please proceed. I uploaded those in order to enable mongoDB tests
> in other packages (before being aware of the mongoDB state) so they are
> pretty useless.

Ack, I've just filed removal bugs.

Cheers,
Moritz

Bug#885299: bumping severity of pygtk bugs

[Moritz Mühlenhoff]

On Fri, Feb 21, 2020 at 10:09:39AM +0100, Piotr Ożarowski wrote:
> [Moritz Mühlenhoff, 2020-02-20]
> > On Sun, Oct 06, 2019 at 05:09:30PM -0400, Jeremy Bicha wrote:
> > > Control: severity -1 serious
> > > Control: tags -1 -buster
> > > 
> > > 
> > > As part of the Python2 removal, it is our intent that pygtk will be 
> > > removed from Testing before the release of Debian 11
> > > "Bullseye". Therefore, I am bumping the severity of this bug to Serious 
> > > to ensure that there is plenty of warning before
> > > the Debian 11 release and to make the eventual removal of pygtk as smooth 
> > > as possible.
> > 
> > Should griffith be removed? It's dropped from testing for two years now
> > and the upstream homepage vanished. Piotr, given that you're among the
> > upstream authors, is this still maintained?
> 
> unfortunately it should be removed from Debian. Maybe some day I will
> find time to update it to Python 3 and new GTK, but not anytime soon.

Ack, I've just filed a removal bug.

Cheers,
Moritz

Processed: src:scantool: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2.0-1
Bug #951794 [src:scantool] src:scantool: fails to migrate to testing for too 
long
Marked as fixed in versions scantool/2.0-1.

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

Bug#951794: src:scantool: fails to migrate to testing for too long

[Paul Gevers]

Source: scantool
Version: 1.21+dfsg-7
Severity: serious
Control: fixed -1 2.0-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:scantool in
its current version in unstable has been trying to migrate for 345 days.
Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have marked the version in unstable as fixing this bug, so if that
version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html




signature.asc
Description: OpenPGP digital signature

Bug#925646: marked as done (bombardier: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Fri, 21 Feb 2020 19:50:10 +
with message-id 
and subject line Bug#925646: fixed in bombardier 0.8.3+nmu2
has caused the Debian Bug report #925646,
regarding bombardier: ftbfs with GCC-9
to be marked as done.

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

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


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

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/bombardier_0.8.3+nmu1_unstable_gcc9.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

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

[...]
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:244: undefined 
reference to `stdscr'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:244: undefined 
reference to `wmove'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:244: undefined 
reference to `stdscr'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:244: undefined 
reference to `waddch'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:248: undefined 
reference to `stdscr'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:248: undefined 
reference to `wmove'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:261: undefined 
reference to `mvprintw'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:263: undefined 
reference to `stdscr'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:263: undefined 
reference to `wrefresh'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:239: undefined 
reference to `stdscr'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:239: undefined 
reference to `wmove'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:239: undefined 
reference to `stdscr'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:239: undefined 
reference to `waddch'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:243: undefined 
reference to `stdscr'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:243: undefined 
reference to `waddch'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:242: undefined 
reference to `stdscr'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:242: undefined 
reference to `wmove'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:242: undefined 
reference to `stdscr'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:242: undefined 
reference to `waddch'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:230: undefined 
reference to `mvprintw'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:229: undefined 
reference to `mvprintw'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:251: undefined 
reference to `stdscr'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:251: undefined 
reference to `wmove'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:251: undefined 
reference to `stdscr'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:251: undefined 
reference to `waddch'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:257: undefined 
reference to `stdscr'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:257: undefined 
reference to `wmove'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:257: undefined 
reference to `stdscr'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:257: undefined 
reference to `waddch'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:254: undefined 
reference to `stdscr'
/usr/bin/ld: /<>/bombardier-0.8.3+nmu1/display.c:254: undefined 
reference to `wmove'

Bug#950035: marked as done (bumpversion FTBFS with pytest 4.6)

[Debian Bug Tracking System]

Your message dated Fri, 21 Feb 2020 19:35:04 +
with message-id 
and subject line Bug#950035: fixed in bumpversion 1.0.0-1
has caused the Debian Bug report #950035,
regarding bumpversion FTBFS with pytest 4.6
to be marked as done.

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

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


-- 
950035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bumpversion
Version: 0.5.10-2
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bumpversion.html

...
= test session starts ==
platform linux -- Python 3.8.1, pytest-4.6.9, py-1.8.0, pluggy-0.13.0
rootdir: /build/1st/bumpversion-0.5.10, inifile: tox.ini
collected 37 items / 1 errors / 36 selected

 ERRORS 
 ERROR collecting .pybuild/cpython3_3.8/build/tests/test_cli.py 
/usr/lib/python3/dist-packages/pluggy/hooks.py:286: in __call__
return self._hookexec(self, self.get_hookimpls(), kwargs)
/usr/lib/python3/dist-packages/pluggy/manager.py:92: in _hookexec
return self._inner_hookexec(hook, methods, kwargs)
/usr/lib/python3/dist-packages/pluggy/manager.py:83: in 
self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
/usr/lib/python3/dist-packages/_pytest/python.py:234: in 
pytest_pycollect_makeitem
res = list(collector._genfunctions(name, obj))
/usr/lib/python3/dist-packages/_pytest/python.py:410: in _genfunctions
self.ihook.pytest_generate_tests(metafunc=metafunc)
/usr/lib/python3/dist-packages/pluggy/hooks.py:286: in __call__
return self._hookexec(self, self.get_hookimpls(), kwargs)
/usr/lib/python3/dist-packages/pluggy/manager.py:92: in _hookexec
return self._inner_hookexec(hook, methods, kwargs)
/usr/lib/python3/dist-packages/pluggy/manager.py:83: in 
self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
/usr/lib/python3/dist-packages/_pytest/python.py:137: in pytest_generate_tests
metafunc.parametrize(*marker.args, **marker.kwargs)
/usr/lib/python3/dist-packages/_pytest/python.py:999: in parametrize
argnames, parameters = ParameterSet._for_parametrize(
/usr/lib/python3/dist-packages/_pytest/mark/structures.py:131: in 
_for_parametrize
if len(param.values) != len(argnames):
E   TypeError: object of type 'MarkDecorator' has no len()
--- Captured stderr 
...
--- End Message ---
--- Begin Message ---
Source: bumpversion
Source-Version: 1.0.0-1
Done: Michael Fladischer 

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

Debian distribution maintenance software
pp.
Michael Fladischer  (supplier of updated bumpversion package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 21 Feb 2020 20:12:50 +0100
Source: bumpversion
Architecture: source
Version: 1.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Michael Fladischer 
Changed-By: Michael Fladischer 
Closes: 950035
Changes:
 bumpversion (1.0.0-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #950035).
   * Refresh patches.
   * Add python3-testfixtures to B-D as required by tests.
   * Add patch to skip tests correctly when hg/git is not installed.
   * Clean up pytest artifacts to allow two builds in a row.
   * Switch to debhelper-compat.
   * Bump Standards-Version to 4.5.0.
   * Set Rules-Requires-Root: no.
Checksums-Sha1:
 e651d63444fa8a56f17b7a60c6d5ec4a4c0b024c 1655 bumpversion_1.0.0-1.dsc
 f3e57475d357d2ab766431e5b7e9d544f730a42c 35037 bumpversion_1.0.0.orig.tar.gz
 cd5608dc9292698588594cbda83ab237b7a33c38 4160 bumpversion_1.0.0-1.debian.tar.xz
 284a25fb2de7747c21254ebebb0256661f6ab520 7492 
bumpversion_1.0.0-1_amd64.buildinfo
Checksums-Sha256:
 f65505fa8619669cd2a99115a30617b3c56964fe2edb42cb6ec422c3352a6c73 1655 
bumpversion_1.0.0-1.dsc
 06a7cb0fb7155b9283c4d10180e477f658754595b4dedb249f1e143e899d0e6c 35037 

Processed: forwarded uvloop issue

[Debian Bug Tracking System]

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

> forwarded 950165 https://github.com/MagicStack/uvloop/issues/318
Bug #950165 [src:uvloop] uvloop FTBFS: tests/test_sockets.py hangs
Set Bug forwarded-to-address to 
'https://github.com/MagicStack/uvloop/issues/318'.
> thanks
Stopping processing here.

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

Processed: Re: pitivi: missing libpython link?

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #951779 [src:pitivi] pitivi: missing libpython link?
Added tag(s) patch.

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

Bug#951779: pitivi: missing libpython link?

[Gianfranco Costamagna]

control: tags -1 patch

Hello, looks like two upstream commit (rebased on this version) helped

diff attached.

G.
diff -Nru pitivi-0.999/debian/changelog pitivi-0.999/debian/changelog
--- pitivi-0.999/debian/changelog   2020-02-07 19:01:06.0 +0100
+++ pitivi-0.999/debian/changelog   2020-02-21 18:59:53.0 +0100
@@ -1,3 +1,11 @@
+pitivi (0.999-1.2) unstable; urgency=medium
+
+  * Cherry-pick upstream fixes for python3.8 (Closes: #951779)
+  * debian/patches/9fc400ca6f3f59fd2b2abfb8e39f0cf7a4031e09.patch:
+  * debian/patches/0a3cc054a2c20b59f5a307de3c9af3c0d270.patch:
+
+ -- Gianfranco Costamagna   Fri, 21 Feb 2020 
18:59:53 +0100
+
 pitivi (0.999-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru 
pitivi-0.999/debian/patches/0a3cc054a2c20b59f5a307de3c9af3c0d270.patch 
pitivi-0.999/debian/patches/0a3cc054a2c20b59f5a307de3c9af3c0d270.patch
--- pitivi-0.999/debian/patches/0a3cc054a2c20b59f5a307de3c9af3c0d270.patch  
1970-01-01 01:00:00.0 +0100
+++ pitivi-0.999/debian/patches/0a3cc054a2c20b59f5a307de3c9af3c0d270.patch  
2020-02-21 18:59:53.0 +0100
@@ -0,0 +1,49 @@
+## Description: add some description
+## Origin/Author: add some origin or author
+## Bug: bug URL
+From 0a3cc054a2c20b59f5a307de3c9af3c0d270 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Alexandru=20B=C4=83lu=C8=9B?= 
+Date: Tue, 28 Jan 2020 22:34:40 +0100
+Subject: [PATCH] meson: Support Python 3.8
+
+To link to Python we need to use python-3.8-embed.
+---
+ meson.build   | 13 ++---
+ meson_options.txt |  3 ++-
+ 2 files changed, 12 insertions(+), 4 deletions(-)
+
+diff --git a/meson.build b/meson.build
+index 0885329f..060ab47a 100644
+--- a/meson.build
 b/meson.build
+@@ -1,11 +1,18 @@
+ project('pitivi', 'c', version : '0.999', meson_version : '>= 0.41.0')
+ 
+-python = find_program('python3')
++pymod = import('python')
++python = pymod.find_installation(get_option('python'))
++pythonver = python.language_version()
++# Workaround for https://github.com/mesonbuild/meson/issues/5629
++# https://gitlab.freedesktop.org/gstreamer/gst-python/issues/28
++python_dep = dependency('python-@0@-embed'.format(pythonver), version: '>= 
3.3', required: false)
++if not python_dep.found()
++  python_dep = python.dependency('python3', version: '>= 3.3')
++endif
+ intltool_merge = find_program('intltool-merge')
+ itstool = find_program('itstool')
+ msgfmt = find_program('msgfmt')
+ 
+-python_dep = dependency(version: '>= 3.3')
+ 
+ if get_option('build-gst')
+ subproject('gst-build', default_options: ['enable_python=true',
+ 'disable_gstreamer_sharp=true', 'disable_rtsp_server=true',
+diff --git a/meson_options.txt b/meson_options.txt
+index c6590dd1..7d6bad29 100644
+--- a/meson_options.txt
 b/meson_options.txt
+@@ -1,2 +1,3 @@
+-option('disable-help', type : 'boolean', value : false)
+ option('build-gst', type : 'boolean', value : false)
++option('disable-help', type : 'boolean', value : false)
++option('python', type : 'string', value : 'python3')
diff -Nru 
pitivi-0.999/debian/patches/9fc400ca6f3f59fd2b2abfb8e39f0cf7a4031e09.patch 
pitivi-0.999/debian/patches/9fc400ca6f3f59fd2b2abfb8e39f0cf7a4031e09.patch
--- pitivi-0.999/debian/patches/9fc400ca6f3f59fd2b2abfb8e39f0cf7a4031e09.patch  
1970-01-01 01:00:00.0 +0100
+++ pitivi-0.999/debian/patches/9fc400ca6f3f59fd2b2abfb8e39f0cf7a4031e09.patch  
2020-02-21 18:59:53.0 +0100
@@ -0,0 +1,27 @@
+From 9fc400ca6f3f59fd2b2abfb8e39f0cf7a4031e09 Mon Sep 17 00:00:00 2001
+From: Thibault Saunier 
+Date: Thu, 30 Jan 2020 12:34:41 -0300
+Subject: [PATCH] build: Fix build when python-embeded is not found
+
+Error message is:
+
+```
+meson.build:11:2: ERROR: Function does not take positional arguments.
+```
+---
+ meson.build | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+Index: pitivi-0.999/meson.build
+===
+--- pitivi-0.999.orig/meson.build
 pitivi-0.999/meson.build
+@@ -5,7 +5,7 @@
+ itstool = find_program('itstool')
+ msgfmt = find_program('msgfmt')
+ 
+-python_dep = dependency('python3', version : '>= 3.3')
++python_dep = dependency(version: '>= 3.3')
+ 
+ if get_option('build-gst')
+ subproject('gst-build', default_options: ['enable_python=true',
diff -Nru pitivi-0.999/debian/patches/series pitivi-0.999/debian/patches/series
--- pitivi-0.999/debian/patches/series  2018-09-07 16:01:24.0 +0200
+++ pitivi-0.999/debian/patches/series  2020-02-21 18:59:53.0 +0100
@@ -0,0 +1,2 @@
+9fc400ca6f3f59fd2b2abfb8e39f0cf7a4031e09.patch
+0a3cc054a2c20b59f5a307de3c9af3c0d270.patch

Bug#951780: OpenSSL linking without license exception

[Bastian Germann]

Package: eurephia
Severity: serious

This package links to OpenSSL even though it does not have any license
exception for it. ftp-master considers this a serious issue. Please
replace libssl with a GPL compatible library. I successfully compiled
with libwolfssl which has an OpenSSL API compatibility layer.

Bug#933334: Remove ugene from Buster (Was: ugene: FTBFS in buster (dpkg-shlibdeps error))

[Santiago Vila]

On Mon, 17 Feb 2020, Andreas Tille wrote:

> > reopen 94
> > found 94 1.31.1+dfsg-1
> > fixed 94 33.0+dfsg-1
> > thanks
> > 
> > Reopening because packages in stable must build in stable.
> 
> I wonder whether it might be the best solution to simply ask for removal
> of 1.31.1+dfsg-1 in buster and provide a backport of the latest version?
> In any case I've just uploaded a backport for now.

Seems ok to me. Just reassign this bug to ftp.debian.org and retitle
accordingly if you decide to follow that route.

(However, before doing that, please confirm that the package also
ftbfs for you in buster and this is not a misconfiguration in my
autobuilders).

Thanks.

Bug#951779: pitivi: missing libpython link?

[Gianfranco Costamagna]

Source: pitivi
Version: 0.999-1.1
Severity: serious

Hello, looks like your software FTBFS with python3.8.
The reason is that Python functions are used in c code but the library is not 
linked to it
grep PyList_Type . -R
./pitivi/coptimizations/renderer.c:  if (!PyArg_ParseTuple (args, "O!ii", 
_Type, , , ))


can you please add the link?
this patch does something similar, but we should change it to autodetect the 
current python library

http://launchpadlibrarian.net/465718636/pitivi_0.999-1.1_0.999-1.1ubuntu1.diff.gz

thanks

Gianfranco


[11/16] cc  -o renderer.so 'renderer@sha/pitivi_coptimizations_renderer.c.o' 
-Wl,--as-needed -Wl,--no-undefined -shared -fPIC -Wl,--start-group 
-Wl,-soname,renderer.so -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-Wl,-Bsymbolic-functions -Wl,-z,relro 
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so /usr/lib/x86_64-linux-gnu/libcairo.so 
-Wl,--end-group
FAILED: renderer.so 
cc  -o renderer.so 'renderer@sha/pitivi_coptimizations_renderer.c.o' 
-Wl,--as-needed -Wl,--no-undefined -shared -fPIC -Wl,--start-group 
-Wl,-soname,renderer.so -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-Wl,-Bsymbolic-functions -Wl,-z,relro 
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so /usr/lib/x86_64-linux-gnu/libcairo.so 
-Wl,--end-group
/usr/bin/ld: renderer@sha/pitivi_coptimizations_renderer.c.o: in function 
`py_fill_surface':
./deb-build/../pitivi/coptimizations/renderer.c:30: undefined reference to 
`PyList_Type'
/usr/bin/ld: ./deb-build/../pitivi/coptimizations/renderer.c:30: undefined 
reference to `PyArg_ParseTuple'
/usr/bin/ld: ./deb-build/../pitivi/coptimizations/renderer.c:33: undefined 
reference to `PyList_Size'
/usr/bin/ld: ./deb-build/../pitivi/coptimizations/renderer.c:50: undefined 
reference to `PyList_GetItem'
/usr/bin/ld: ./deb-build/../pitivi/coptimizations/renderer.c:51: undefined 
reference to `PyFloat_AsDouble'
/usr/bin/ld: ./deb-build/../pitivi/coptimizations/renderer.c:54: undefined 
reference to `PyErr_Occurred'
/usr/bin/ld: renderer@sha/pitivi_coptimizations_renderer.c.o: in function 
`_Py_DECREF':
/usr/include/python3.8/object.h:478: undefined reference to `_Py_Dealloc'
/usr/bin/ld: /usr/include/python3.8/object.h:478: undefined reference to 
`_Py_Dealloc'
/usr/bin/ld: renderer@sha/pitivi_coptimizations_renderer.c.o: in function 
`import_cairo':
/usr/include/pycairo/py3cairo.h:264: undefined reference to `PyCapsule_Import'
/usr/bin/ld: renderer@sha/pitivi_coptimizations_renderer.c.o: in function 
`PyInit_renderer':
./deb-build/../pitivi/coptimizations/renderer.c:134: undefined reference to 
`PyModule_Create2'
collect2: error: ld returned 1 exit status
[12/16] /usr/bin/intltool-merge --xml-style /<>/po 
../data/org.pitivi.Pitivi.appdata.xml.in data/org.pitivi.Pitivi.appdata.xml
Merging translations into data/org.pitivi.Pitivi.appdata.xml.
CREATED data/org.pitivi.Pitivi.appdata.xml
[13/16] /usr/bin/meson --internal symbolextractor 
subprojects/gst-transcoder/libgsttranscoder-1.0.so.0 
'subprojects/gst-transcoder/7016d90@@gsttranscoder-1.0@sha/libgsttranscoder-1.0.so.0.symbols'
 
[14/16] /usr/bin/g-ir-scanner -pthread -I/usr/include/gobject-introspection-1.0 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
--no-libtool --namespace=GstTranscoder --nsversion=1.0 --warn-all --output 
subprojects/gst-transcoder/GstTranscoder-1.0.gir '--add-init-section=extern 
gboolean gst_init(gint *argc, gchar **argv); gst_init(NULL,NULL);' 
-I/<>/subprojects/gst-transcoder 
-I/<>/deb-build/subprojects/gst-transcoder 
--filelist=/<>/deb-build/subprojects/gst-transcoder/7016d90@@gsttranscoder-1.0@sha/GstTranscoder_1.0_gir_filelist
 --include=GObject-2.0 --include=Gst-1.0 --include=GstPbutils-1.0 
--symbol-prefix=gst_ --identifier-prefix=Gst --cflags-begin 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/gstreamer-1.0 -I/usr/include/orc-0.4 -D_FORTIFY_SOURCE=2 
--cflags-end --add-include-path=/usr/share/gir-1.0 --library gsttranscoder-1.0 
-L/<>/deb-build/subprojects/gst-transcoder 
--extra-library=glib-2.0 --extra-library=gobject-2.0 
--extra-library=gstreamer-1.0 --extra-library=gstpbutils-1.0 
--extra-library=gstaudio-1.0 --extra-library=gstvideo-1.0 
--extra-library=gstbase-1.0 --sources-top-dirs 
/<>/subprojects/gst-transcoder --sources-top-dirs 
/<>/deb-build/subprojects/gst-transcoder
g-ir-scanner: link: x86_64-linux-gnu-gcc -pthread -o 
/<>/deb-build/tmp-introspectwznwxfiq/GstTranscoder-1.0 -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
/<>/deb-build/tmp-introspectwznwxfiq/GstTranscoder-1.0.o -L. 
-Wl,-rpath,. -Wl,--no-as-needed 
-L/<>/deb-build/subprojects/gst-transcoder 

Bug#951778: libva2: NULL vtable when querying nvidia render device

[Steinar H. Gunderson]

Package: libva2
Version: 2.6.1-1
Severity: grave

Hi,

It seems that after a recent full-upgrade, querying certain render nodes fails,
crashing my program; it is easily reproducible using vainfo:

  gruessi:~> vainfo --display drm --device /dev/dri/renderD129
  libva info: VA-API version 1.6.0
  vainfo: VA-API version: 1.6 (libva 2.6.0)
  vainfo: Driver version: 
  zsh: segmentation fault  vainfo --display drm --device /dev/dri/renderD129

The crash is in

  Program received signal SIGSEGV, Segmentation fault.
  0x77e254f2 in vaQueryConfigProfiles (dpy=0xd2d0, 
profile_list=0xdc10, 
  num_profiles=0x7fffe92c) at va.c:903
  903   va.c: Ingen slik fil eller filkatalog.
  (gdb) bt
  #0  0x77e254f2 in vaQueryConfigProfiles (dpy=0xd2d0, 
profile_list=0xdc10, 
  num_profiles=0x7fffe92c) at va.c:903
  #1  0x64e3 in ?? ()
  #2  0x77c73bbb in __libc_start_main (main=0x6370, argc=5, 
argv=0x7fffea48, 
  init=, fini=, rtld_fini=, 
stack_end=0x7fffea38)
  at ../csu/libc-start.c:308
  #3  0x68aa in ?? ()

It seems that somehow, the device is opened but gets a NULL vtable:

  (gdb) print *ctx
  $2 = {pDriverData = 0x0, vtable = 0x0, vtable_glx = 0x0, vtable_egl = 0x0, 
vtable_tpi = 0x0, 
native_dpy = 0x0, x11_screen = 0, version_major = 0, version_minor = 0, 
max_profiles = 0, 
max_entrypoints = 0, max_attributes = 0, max_image_formats = 0, 
max_subpic_formats = 0, 
max_display_attributes = 0, str_vendor = 0x0, handle = 0x0, drm_state = 
0xd2a0, glx = 0x0, 
display_type = 49, vtable_wayland = 0x0, vtable_vpp = 0x0, 
override_driver_name = 0x0, 
pDisplayContext = 0xd2d0, error_callback = 0x77e23540 
, 
info_callback = 0x77e23560 , reserved = {0 
}}

I can query renderD128, which corresponds to my Intel iGPU just fine.
renderD129 corresponds to my RTX 2070:

  gruessi:~> cat /sys/class/drm/renderD129/device/vendor
  0x10de
  gruessi:~> cat /sys/class/drm/renderD129/device/device
  0x1f02

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

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

Versions of packages libva2 depends on:
ii  libc6  2.29-10

Versions of packages libva2 recommends:
ii  i965-va-driver-shaders [va-driver]  2.4.0-1
ii  intel-media-va-driver-non-free [va-driver]  19.4.0+ds1-1
ii  mesa-va-drivers [va-driver] 19.3.3-1
ii  va-driver-all   2.6.1-1

libva2 suggests no packages.

-- no debconf information

Bug#935455: test failures with dask, python3.8

[Alastair McKinstry]

reassign 935455 dask

thanks

This is a problem that occurs with dask and python3.8. python3.7 passes
fine.

It appears to be fixed upstream:

https://github.com/dask/dask/pull/5852


Regards

Alastair

-- 
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered. 

Processed: test failures with dask, python3.8

[Debian Bug Tracking System]

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

> reassign 935455 dask
Bug #935455 [src:python-xarray] python-xarray: autopkgtest regression: 
test_dask fails
Bug reassigned from package 'src:python-xarray' to 'dask'.
No longer marked as found in versions python-xarray/0.12.3-1.
Ignoring request to alter fixed versions of bug #935455 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#950963: marked as done (FTBFS: Could not find gem 'sqlite3 (~> 1.3.8)' in any of the gem sources listed in your Gemfile)

[Debian Bug Tracking System]

Your message dated Fri, 21 Feb 2020 16:49:48 +
with message-id 
and subject line Bug#950963: fixed in ruby-joiner 0.4.2-2
has caused the Debian Bug report #950963,
regarding FTBFS: Could not find gem 'sqlite3 (~> 1.3.8)' in any of the gem 
sources listed in your Gemfile
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.)


-- 
950963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-joiner
Version: 0.4.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

ruby-sqlite3 was recently updated in unstable, and now ruby-joiner fails
to build with:

Could not find gem 'sqlite3 (~> 1.3.8)' in any of the gem sources listed in 
your Gemfile.

Note that ~> 1.3.8 is too strict a dependency. Please consider chancing
it to ~> 1.3, and possibly send a patch upstream.

See attached the full build log.

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

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


ruby-joiner_amd64.build.gz
Description: application/gzip


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-joiner
Source-Version: 0.4.2-2
Done: Lucas Kanashiro 

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

Debian distribution maintenance software
pp.
Lucas Kanashiro  (supplier of updated 
ruby-joiner package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 21 Feb 2020 12:55:49 -0300
Source: ruby-joiner
Architecture: source
Version: 0.4.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Lucas Kanashiro 
Closes: 950963
Changes:
 ruby-joiner (0.4.2-2) unstable; urgency=medium
 .
   * Team upload.
   * Add patch to relax version of some dependencies (Closes: #950963)
   * Bump debhelper compatibility level to 12
   * Declare compliance with Debian Policy 4.5.0
   * d/control: rules does not need root
   * Do not runtime depend on ruby interpreter
   * d/copyright: use secure url in Format field
Checksums-Sha1:
 bfd10658c47807a84351f6506f5f0c68c2ff6fae 2120 ruby-joiner_0.4.2-2.dsc
 92431075fa85318e8af18c986971b3baa6f43dbf 3204 ruby-joiner_0.4.2-2.debian.tar.xz
Checksums-Sha256:
 f0ea4ad1effa0c523ceb76c26f9e1e0b20f8b7644260cad5d541376d75d346df 2120 
ruby-joiner_0.4.2-2.dsc
 86b23f8bbf39575d9ee6b4f60b5981080fe6cc08d0b332e40c7a5b3c6652a76c 3204 
ruby-joiner_0.4.2-2.debian.tar.xz
Files:
 1820e7e11b357f17e1afb6a64f66e3d8 2120 ruby optional ruby-joiner_0.4.2-2.dsc
 7e51f193adf8547b30c9282a6ceb5bc7 3204 ruby optional 
ruby-joiner_0.4.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJSBAEBCAA8FiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAl5QBbYeHGx1Y2FzLmth
bmFzaGlyb0BjYW5vbmljYWwuY29tAAoJEPgjonKYg8l8uYMQAK2YsYZ1Rl1fFkKG
Lao4uRnhxNKfJWGX2dCA6IJpXfR0QZ7zsZE4KUGKs7ONgKewPm4hxOrefwzueUbB
JYd8P5Kg8w5H0IWiK8xBI3oxuzdupHcOx1NnFiCwqO5QV6sXPSjRpTSHgvMU2JX3
OZGlN08Ho3ZUR8ZccMhgucqkkPLQ7+2ukaKF7XsCoixs5yLYM27kmyDskIbdue6x
+jopC3TLlZONZcebDcTvnKlEsBxOB3hszHmToQ1p7RXabdQXXzsvHwLukRPm6bc4
GdIYLXGjXR845TJ+Q4bQ+d/8zJ6LYAO+fJEpLS6vlqoppvwh3FTcQ/HZRZVgbzVr
nL9qW+vBXUffY0cKoHia2miElH72540iXo/Bl+2MZfprj1J21kQvvZ10h9LWo0D0
4S4+MQZUNcD95MVDHvFs82AMNgwaDpYPh0vjMukwrTFaEIesmXIumdS1FDV3u6Z2
g1OZ8Ibpxzjay+WDtaKqMwepTrNB6dYwnohyeEyHa2R8m+W48PZnPb9G4ZijJ/65
d9gPLz2hKBEBZrctDQwC4Z+S4W5xa+JPJdIonPeuYL2McYzjoPpriHgW9YVZePfv
hyymFEjR5WMS8JNVnhxRYFCty3j9Ag4P+NPIHhzu/54jKVtUKlH0yeDZGEQBZLL1
+A+D0nGkzhrSEGQrEiu8IJKYI7Jc
=QeaJ
-END PGP SIGNATURE End Message ---

Bug#950684: Debian Bug #950684

[Johannes Schauer]

Hi,

Quoting Jörg Frings-Fürst (2020-02-19 10:29:44)
> Am Mittwoch, den 19.02.2020, 09:14 +0100 schrieb Johannes Schauer:
> > Quoting Jörg Frings-Fürst (2020-02-19 07:40:08)
> > > I set the severity to serious.
> > why?
> All packages with, direct or over an other package, a build depend
> systemd can't build.

please show me evidence of that.

Setting a bug severity to serious means that sbuild will be removed from
testing in March. You should have evidence before such a drastic measure is
taken.

Please show me how to reproduce the problem because I am unable to see it over
here.

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#951767: marked as done (python-cartopy test failures with Python 3.8)

[Debian Bug Tracking System]

Your message dated Fri, 21 Feb 2020 15:23:00 +
with message-id 
and subject line Bug#951767: fixed in python-cartopy 0.17.0+dfsg-9
has caused the Debian Bug report #951767,
regarding python-cartopy test failures with Python 3.8
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.)


-- 
951767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-cartopy
Version: 0.17.0+dfsg-8
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8

Seen with both versions in unstable and experimental, here on amd64:

=== FAILURES ===
_ test_transform_point _

def test_transform_point():
"""
Mostly tests the workaround for a specific problem.
Problem report in: https://github.com/SciTools/cartopy/issues/23
Fix covered in: https://github.com/SciTools/cartopy/pull/277
"""

# this way has always worked
result = _CRS_ROB.transform_point(35.0, 70.0, _CRS_PC)
>   assert_array_almost_equal(result, (2376187.27182751, 7275317.81573085),
  _TOL)
E   AssertionError:
E   Arrays are not almost equal to 7 decimals
E
E   Mismatch: 100%
E   Max absolute difference: 0.30056718
E   Max relative difference: 4.13132717e-08
Ex: array([2376187.2182271, 7275318.116298 ])
Ey: array([2376187.2718275, 7275317.8157309])

cartopy/tests/crs/test_robinson.py:126: AssertionError
 test_transform_points _

def test_transform_points():
"""
Mostly tests the workaround for a specific problem.
Problem report in: https://github.com/SciTools/cartopy/issues/23
Fix covered in: https://github.com/SciTools/cartopy/pull/277
"""

# these always worked
result = _CRS_ROB.transform_points(_CRS_PC,
   np.array([35.0]),
   np.array([70.0]))
>   assert_array_almost_equal(result,
  [[2376187.27182751, 7275317.81573085, 0]], 
_TOL)
E   AssertionError:
E   Arrays are not almost equal to 7 decimals
E
E   Mismatch: 66.7%
E   Max absolute difference: 0.30056718
E   Max relative difference: 4.13132717e-08
Ex: array([[2376187.2182271, 7275318.116298 ,   0.   ]])
Ey: array([[2376187.2718275, 7275317.8157309,   0.   ]])

cartopy/tests/crs/test_robinson.py:149: AssertionError
== 2 failed, 421 passed, 2 skipped, 111 deselected, 2 xfailed in 8.37 seconds ==
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=1: cd
'/packages/tmp/p/python-cartopy-0.18.0~b1+dfsg/.pybuild/cpython3_3.8_cartopy/build';
python3.8 -m pytest --pyargs -m "not network and not natural_earth"
--- End Message ---
--- Begin Message ---
Source: python-cartopy
Source-Version: 0.17.0+dfsg-9
Done: Bas Couwenberg 

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated python-cartopy 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 21 Feb 2020 15:50:38 +0100
Source: python-cartopy
Architecture: source
Version: 0.17.0+dfsg-9
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 951767
Changes:
 python-cartopy (0.17.0+dfsg-9) unstable; urgency=medium
 .
   * Team upload.
   * Add patch to fix FTBFS due to test failures.
 (closes: #951767)
Checksums-Sha1:
 75023934b32aac024e65b455c254d9734160ef3d 2531 python-cartopy_0.17.0+dfsg-9.dsc
 2e3bfb15961fb81b05fe168b438bfaa06529239c 12056 
python-cartopy_0.17.0+dfsg-9.debian.tar.xz
 498069e71226bb75388c37d3b5e895f83bc9d7c9 13702 
python-cartopy_0.17.0+dfsg-9_amd64.buildinfo
Checksums-Sha256:
 

Bug#951767: marked as done (python-cartopy test failures with Python 3.8)

[Debian Bug Tracking System]

Your message dated Fri, 21 Feb 2020 15:10:32 +
with message-id 
and subject line Bug#951767: fixed in python-cartopy 0.18.0~b1+dfsg-1~exp2
has caused the Debian Bug report #951767,
regarding python-cartopy test failures with Python 3.8
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.)


-- 
951767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-cartopy
Version: 0.17.0+dfsg-8
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8

Seen with both versions in unstable and experimental, here on amd64:

=== FAILURES ===
_ test_transform_point _

def test_transform_point():
"""
Mostly tests the workaround for a specific problem.
Problem report in: https://github.com/SciTools/cartopy/issues/23
Fix covered in: https://github.com/SciTools/cartopy/pull/277
"""

# this way has always worked
result = _CRS_ROB.transform_point(35.0, 70.0, _CRS_PC)
>   assert_array_almost_equal(result, (2376187.27182751, 7275317.81573085),
  _TOL)
E   AssertionError:
E   Arrays are not almost equal to 7 decimals
E
E   Mismatch: 100%
E   Max absolute difference: 0.30056718
E   Max relative difference: 4.13132717e-08
Ex: array([2376187.2182271, 7275318.116298 ])
Ey: array([2376187.2718275, 7275317.8157309])

cartopy/tests/crs/test_robinson.py:126: AssertionError
 test_transform_points _

def test_transform_points():
"""
Mostly tests the workaround for a specific problem.
Problem report in: https://github.com/SciTools/cartopy/issues/23
Fix covered in: https://github.com/SciTools/cartopy/pull/277
"""

# these always worked
result = _CRS_ROB.transform_points(_CRS_PC,
   np.array([35.0]),
   np.array([70.0]))
>   assert_array_almost_equal(result,
  [[2376187.27182751, 7275317.81573085, 0]], 
_TOL)
E   AssertionError:
E   Arrays are not almost equal to 7 decimals
E
E   Mismatch: 66.7%
E   Max absolute difference: 0.30056718
E   Max relative difference: 4.13132717e-08
Ex: array([[2376187.2182271, 7275318.116298 ,   0.   ]])
Ey: array([[2376187.2718275, 7275317.8157309,   0.   ]])

cartopy/tests/crs/test_robinson.py:149: AssertionError
== 2 failed, 421 passed, 2 skipped, 111 deselected, 2 xfailed in 8.37 seconds ==
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=1: cd
'/packages/tmp/p/python-cartopy-0.18.0~b1+dfsg/.pybuild/cpython3_3.8_cartopy/build';
python3.8 -m pytest --pyargs -m "not network and not natural_earth"
--- End Message ---
--- Begin Message ---
Source: python-cartopy
Source-Version: 0.18.0~b1+dfsg-1~exp2
Done: Bas Couwenberg 

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated python-cartopy 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 21 Feb 2020 15:27:07 +0100
Source: python-cartopy
Architecture: source
Version: 0.18.0~b1+dfsg-1~exp2
Distribution: experimental
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 951767
Changes:
 python-cartopy (0.18.0~b1+dfsg-1~exp2) experimental; urgency=medium
 .
   * Team upload.
   * Add patch to fix FTBFS due to test failures.
 (closes: #951767)
Checksums-Sha1:
 462e478a04b63acc207a3f2eb273d8a04304903a 2591 
python-cartopy_0.18.0~b1+dfsg-1~exp2.dsc
 674961e74e21c683e50e23f5dfe1a7ae93bfbe5e 10176 
python-cartopy_0.18.0~b1+dfsg-1~exp2.debian.tar.xz
 e15c78096b8f07cad2de2cf9b905d3674f398952 13812 

Bug#951771: linux-source-5.4: linux 5.4.0-4 does not boot on this pc

[TS]

Package: linux-source-5.4
Version: linux 5.4.0-4
Severity: serious
Justification: 1

Hi

did upgrade to sid. linux 5.4.0-4 does not boot on this pc.
Booting 4.19.0-8-amd64 instead brings up running system.

The boot prozess breaks after grub. Blank screen, nothing happens.
With 4.19.0-8-amd64 system boots up as expected.

regards,

T.Six


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

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

Bug#906144: marked as done (libmypaint-common: drop Conflicts: mypaint-data)

[Debian Bug Tracking System]

Your message dated Fri, 21 Feb 2020 15:00:17 +
with message-id 
and subject line Bug#906144: fixed in libmypaint 1.5.0-1~exp1
has caused the Debian Bug report #906144,
regarding libmypaint-common: drop Conflicts: mypaint-data
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.)


-- 
906144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmypaint-common
Version: 1.3.0-2
Severity: important
Control: affects -1 mypaint-data mypaint gimp

The Conflicts: mypaint-data should be dropped when the
file conflict is resolved, see #894757 for background.
--- End Message ---
--- Begin Message ---
Source: libmypaint
Source-Version: 1.5.0-1~exp1
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated libmypaint package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Feb 2020 16:32:17 -0500
Source: libmypaint
Binary: gir1.2-mypaint-1.5 libmypaint-1.5-1 libmypaint-1.5-1-dbgsym 
libmypaint-common libmypaint-dev libmypaint-doc
Architecture: source amd64 all
Version: 1.5.0-1~exp1
Distribution: experimental
Urgency: high
Maintainer: Debian Multimedia Maintainers 
Changed-By: Boyuan Yang 
Description:
 gir1.2-mypaint-1.5 - GObject introspection data for libmypaint
 libmypaint-1.5-1 - brush library for mypaint
 libmypaint-common - brush library for mypaint - common files
 libmypaint-dev - brush library for mypaint - development files
 libmypaint-doc - brush library for mypaint - documentation
Closes: 906144 951093
Changes:
 libmypaint (1.5.0-1~exp1) experimental; urgency=high
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat
 .
   [ Boyuan Yang ]
   * Acknowledge NMU.
   * New upstream version 1.5.0. (Closes: #951093)
   * debian/control:
 + Bump debhelper compat to v12.
 + Bump Standards-Version to 4.5.0.
 + Correctly set the upstream homepage for libmypaint.
 + Only use versioned conflict between libmypaint-common and
   mypaint-data. (Closes: #906144)
   * debian/: Rename library names from 1.3 to 1.5.
   * debian/symbols: Regenerate symbol list.
   * debian/patches: Refresh patches.
 + Add patch to force using python3 in configure process.
   * debian/upstream/metadata: Add metadata: Repository, Repository-Browse.
   * debian/copyright:
 + Refresh date.
 + Include upstream m4macros dir again.
 - use dh_clean to remove it prior to build instead.
Checksums-Sha1:
 c05b403c95359b3f3172fb2473c938ab44d57af9 2803 libmypaint_1.5.0-1~exp1.dsc
 1eef7a1d1bd1af85522fed9175ec0f32c43a71db 507232 libmypaint_1.5.0.orig.tar.xz
 622568806151f1850e4d1f0c1c6f13884b71ac65 958 libmypaint_1.5.0.orig.tar.xz.asc
 789388aa861ab163e648fb7d62753da233df9b44 5948 
libmypaint_1.5.0-1~exp1.debian.tar.xz
 c224b0f67c2f202636c7455ad371231116960828 7848 
gir1.2-mypaint-1.5_1.5.0-1~exp1_amd64.deb
 162ebfab6d1e6be856f02891a18ee45d2ca9ae9f 95076 
libmypaint-1.5-1-dbgsym_1.5.0-1~exp1_amd64.deb
 09ea76c8b290cbcffe6fb9a5c7d349f4c056894d 47860 
libmypaint-1.5-1_1.5.0-1~exp1_amd64.deb
 69aed23ff95966f1567ecdfc2898c0221a764e6d 136608 
libmypaint-common_1.5.0-1~exp1_all.deb
 e21b443775611df8252e4eaa5398eeed9a9920e7 18988 
libmypaint-dev_1.5.0-1~exp1_amd64.deb
 39da915c38f055beb20e405103af8a4270dee23b 68148 
libmypaint-doc_1.5.0-1~exp1_all.deb
 1e26701c36425c258abafc5ab1f86b9e475e7b6f 10569 
libmypaint_1.5.0-1~exp1_amd64.buildinfo
Checksums-Sha256:
 842f16b8abaa9bc37c950bec567dee3c0909b4a01e9a5d7472f914c07333c7a2 2803 
libmypaint_1.5.0-1~exp1.dsc
 aba6e0526f9e4bead4a89c7c82084971b90c5128b50da77b0ac0f5ef27772b57 507232 
libmypaint_1.5.0.orig.tar.xz
 cb1a9056efc95eac1b640a74390e5131fbe1f7347b5a17bf99fce39ae408c7e3 958 
libmypaint_1.5.0.orig.tar.xz.asc
 0730dd8ec747b8fbc16494756920960585980bd465386c29d53bf4fc5fa8e19f 5948 
libmypaint_1.5.0-1~exp1.debian.tar.xz
 3faa2b1f1703897f58d4ea08c4524ed0bf2bf11dfa0f949716dc13f17d0e4e26 7848 

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

[Debian Bug Tracking System]

Your message dated Fri, 21 Feb 2020 15:00:32 +
with message-id 
and subject line Bug#922600: fixed in visp 3.3.0-1
has caused the Debian Bug report #922600,
regarding FTBFS against opencv 4.0.1 (exp)
to be marked as done.

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

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


-- 
922600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: visp
Version: 3.1.0-2
Severity: important

maybe opencv4 broke it due to api change


visp_3.1.0-2_ppc64el-2019-02-15T12:00:30Z.build.zst
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: visp
Source-Version: 3.3.0-1
Done: Fabien Spindler 

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

Debian distribution maintenance software
pp.
Fabien Spindler  (supplier of updated visp 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, 17 Feb 2020 10:04:07 +0100
Source: visp
Binary: libvisp-ar-dev libvisp-ar3.3 libvisp-ar3.3-dbgsym libvisp-blob-dev 
libvisp-blob3.3 libvisp-blob3.3-dbgsym libvisp-core-dev libvisp-core3.3 
libvisp-core3.3-dbgsym libvisp-detection-dev libvisp-detection3.3 
libvisp-detection3.3-dbgsym libvisp-dev libvisp-doc libvisp-gui-dev 
libvisp-gui3.3 libvisp-gui3.3-dbgsym libvisp-imgproc-dev libvisp-imgproc3.3 
libvisp-imgproc3.3-dbgsym libvisp-io-dev libvisp-io3.3 libvisp-io3.3-dbgsym 
libvisp-klt-dev libvisp-klt3.3 libvisp-klt3.3-dbgsym libvisp-mbt-dev 
libvisp-mbt3.3 libvisp-mbt3.3-dbgsym libvisp-me-dev libvisp-me3.3 
libvisp-me3.3-dbgsym libvisp-robot-dev libvisp-robot3.3 libvisp-robot3.3-dbgsym 
libvisp-sensor-dev libvisp-sensor3.3 libvisp-sensor3.3-dbgsym libvisp-tt-dev 
libvisp-tt-mi-dev libvisp-tt-mi3.3 libvisp-tt-mi3.3-dbgsym libvisp-tt3.3 
libvisp-tt3.3-dbgsym libvisp-vision-dev libvisp-vision3.3 
libvisp-vision3.3-dbgsym libvisp-visual-features-dev libvisp-visual-features3.3 
libvisp-visual-features3.3-dbgsym libvisp-vs-dev
 libvisp-vs3.3
 libvisp-vs3.3-dbgsym
Architecture: source amd64 all
Version: 3.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Fabien Spindler 
Description:
 libvisp-ar-dev - development files for libvisp-ar
 libvisp-ar3.3 - visual servoing platform ar library
 libvisp-blob-dev - development files for libvisp-blob
 libvisp-blob3.3 - visual servoing platform blob tracking library
 libvisp-core-dev - development files for libvisp-core
 libvisp-core3.3 - visual servoing platform core library
 libvisp-detection-dev - development files for libvisp-detection
 libvisp-detection3.3 - visual servoing platform detection library
 libvisp-dev - development files for ViSP
 libvisp-doc - visual servoing library - documentation
 libvisp-gui-dev - development files for libvisp-gui
 libvisp-gui3.3 - visual servoing platform gui library
 libvisp-imgproc-dev - development files for libvisp-imgproc
 libvisp-imgproc3.3 - visual servoing platform imgproc library
 libvisp-io-dev - development files for libvisp-io
 libvisp-io3.3 - visual servoing platform io library
 libvisp-klt-dev - development files for libvisp-klt
 libvisp-klt3.3 - visual servoing platform klt tracking library
 libvisp-mbt-dev - development files for libvisp-mbt
 libvisp-mbt3.3 - visual servoing platform mbt library
 libvisp-me-dev - development files for libvisp-me
 libvisp-me3.3 - visual servoing platform me tracking library
 libvisp-robot-dev - development files for libvisp-robot
 libvisp-robot3.3 - visual servoing platform robot library
 libvisp-sensor-dev - development files for libvisp-sensor
 libvisp-sensor3.3 - visual servoing platform sensor library
 libvisp-tt-dev - development files for libvisp-tt
 libvisp-tt-mi-dev - development files for libvisp-tt-mi
 libvisp-tt-mi3.3 - visual servoing platform tt-mi library
 libvisp-tt3.3 - visual servoing platform tt library
 libvisp-vision-dev - development files for libvisp-vision
 libvisp-vision3.3 - visual servoing platform vision library
 libvisp-visual-features-dev - development files for libvisp-visual-features
 

Bug#947327: marked as done (FTBFS: /usr/bin/env: ‘python’: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 21 Feb 2020 15:00:19 +
with message-id 
and subject line Bug#947327: fixed in poppler 0.85.0-1
has caused the Debian Bug report #947327,
regarding FTBFS: /usr/bin/env: ‘python’: No such file or directory
to be marked as done.

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

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


-- 
947327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: poppler
Version: 0.71.0-6
Severity: serious
Justification: FTBFS

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

[ 58%] Generating glib-docs-build.stamp
cd /<>/obj-x86_64-linux-gnu/glib/reference && 
../../../make-glib-api-docs --src-dir=/<> 
--build-dir=/<>/obj-x86_64-linux-gnu
/usr/bin/env: ‘python’: No such file or directory
make[3]: *** [glib/reference/CMakeFiles/glib-docs.dir/build.make:64: 
glib/reference/glib-docs-build.stamp] Error 127
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:672: 
glib/reference/CMakeFiles/glib-docs.dir/all] Error 2

Thanks for your work, Lisandro.

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

Kernel: Linux 5.3.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: poppler
Source-Version: 0.85.0-1
Done: Emilio Pozuelo Monfort 

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

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

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

Debian distribution maintenance software
pp.
Emilio Pozuelo Monfort  (supplier of updated poppler package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 19 Feb 2020 18:50:58 +0100
Source: poppler
Binary: gir1.2-poppler-0.18 libpoppler-cpp-dev libpoppler-cpp0v5 
libpoppler-cpp0v5-dbgsym libpoppler-dev libpoppler-glib-dev libpoppler-glib-doc 
libpoppler-glib8 libpoppler-glib8-dbgsym libpoppler-private-dev 
libpoppler-qt5-1 libpoppler-qt5-1-dbgsym libpoppler-qt5-dev libpoppler95 
libpoppler95-dbgsym poppler-utils poppler-utils-dbgsym
Architecture: source amd64 all
Version: 0.85.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian freedesktop.org maintainers 

Changed-By: Emilio Pozuelo Monfort 
Description:
 gir1.2-poppler-0.18 - GObject introspection data for poppler-glib
 libpoppler-cpp-dev - PDF rendering library -- development files (CPP interface)
 libpoppler-cpp0v5 - PDF rendering library (CPP shared library)
 libpoppler-dev - PDF rendering library -- development files
 libpoppler-glib-dev - PDF rendering library -- development files (GLib 
interface)
 libpoppler-glib-doc - PDF rendering library -- documentation for the GLib 
interface
 libpoppler-glib8 - PDF rendering library (GLib-based shared library)
 libpoppler-private-dev - PDF rendering library -- private development files
 libpoppler-qt5-1 - PDF rendering library (Qt 5 based shared library)
 libpoppler-qt5-dev - PDF rendering library -- development files (Qt 5 
interface)
 libpoppler95 - PDF rendering library
 poppler-utils - PDF utilities (based on Poppler)
Closes: 947327
Changes:
 poppler (0.85.0-1) experimental; urgency=medium
 .
   [ Andreas Henriksson ]
   * New upstream release.
   * libpoppler91 -> libpoppler95
   * Revert "Silence deprecation warnings for GTime, fixing autopkgtest"
 - merged upstream, now part of upstream release.
   * Update symbols
 .
   [ Philip Withnall ]
   * Add python3:any to build deps as it’s used in `make-glib-api-docs` script.
 Closes: #947327.
 .
   [ Emilio Pozuelo Monfort ]
   * Replace ADTTMP variable with AUTOPKGTEST_TMP.
   * Update copyright holders.

Bug#945384: marked as done (visp: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Fri, 21 Feb 2020 15:00:32 +
with message-id 
and subject line Bug#945384: fixed in visp 3.3.0-1
has caused the Debian Bug report #945384,
regarding visp: autopkgtest regression
to be marked as done.

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

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


-- 
945384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: visp
Version: 3.2.0-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

Dear maintainers,

The autopkgtests for visp 3.2.0-1 have regressed vs prior versions of this
package, which means it will not migrate to testing.

The test failure happens to be different in Debian vs. Ubuntu.  In Debian
it appears to be failing due to uninstallability.  This uninstallability
doesn't affect Ubuntu (libvisp-detection-dev is installable in Ubuntu), but
once past this failure the test fails due to what looks like a missing
dependency of the -dev package:

autopkgtest [00:17:15]: test build: [---
g++: error: /usr/lib/x86_64-linux-gnu/libOpenGL.so: No such file or directory
g++: error: /usr/lib/x86_64-linux-gnu/libGLX.so: No such file or directory
g++: error: /usr/lib/x86_64-linux-gnu/libGLU.so: No such file or directory
g++: error: /usr/lib/x86_64-linux-gnu/libCoin.so: No such file or directory
g++: error: /usr/lib/x86_64-linux-gnu/libXi.so: No such file or directory
autopkgtest [00:17:16]: test build: ---]
[...]

  (http://autopkgtest.ubuntu.com/packages/v/visp/focal/amd64)

Looking at the autopkgtest in question, it appears that pkg-config for visp
is emitting libraries in its Libs: field that are provided by packages which
it does not depend on.  So this points to an actual bug in visp that needs
fixing. 

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: visp
Source-Version: 3.3.0-1
Done: Fabien Spindler 

We believe that the bug you reported is fixed in the latest version of
visp, 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.
Fabien Spindler  (supplier of updated visp 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, 17 Feb 2020 10:04:07 +0100
Source: visp
Binary: libvisp-ar-dev libvisp-ar3.3 libvisp-ar3.3-dbgsym libvisp-blob-dev 
libvisp-blob3.3 libvisp-blob3.3-dbgsym libvisp-core-dev libvisp-core3.3 
libvisp-core3.3-dbgsym libvisp-detection-dev libvisp-detection3.3 
libvisp-detection3.3-dbgsym libvisp-dev libvisp-doc libvisp-gui-dev 
libvisp-gui3.3 libvisp-gui3.3-dbgsym libvisp-imgproc-dev libvisp-imgproc3.3 
libvisp-imgproc3.3-dbgsym libvisp-io-dev libvisp-io3.3 libvisp-io3.3-dbgsym 
libvisp-klt-dev libvisp-klt3.3 libvisp-klt3.3-dbgsym libvisp-mbt-dev 
libvisp-mbt3.3 libvisp-mbt3.3-dbgsym libvisp-me-dev libvisp-me3.3 
libvisp-me3.3-dbgsym libvisp-robot-dev libvisp-robot3.3 libvisp-robot3.3-dbgsym 
libvisp-sensor-dev libvisp-sensor3.3 libvisp-sensor3.3-dbgsym libvisp-tt-dev 
libvisp-tt-mi-dev libvisp-tt-mi3.3 libvisp-tt-mi3.3-dbgsym libvisp-tt3.3 
libvisp-tt3.3-dbgsym libvisp-vision-dev libvisp-vision3.3 
libvisp-vision3.3-dbgsym libvisp-visual-features-dev libvisp-visual-features3.3 
libvisp-visual-features3.3-dbgsym libvisp-vs-dev
 libvisp-vs3.3
 libvisp-vs3.3-dbgsym
Architecture: source amd64 all
Version: 3.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Fabien Spindler 
Description:
 libvisp-ar-dev - development files for libvisp-ar
 libvisp-ar3.3 - visual servoing platform ar library
 libvisp-blob-dev - development files for libvisp-blob
 libvisp-blob3.3 - visual servoing platform blob tracking library
 libvisp-core-dev - development files for libvisp-core
 libvisp-core3.3 - visual servoing platform core library

Bug#951727: marked as done (qmelt: command not found)

[Debian Bug Tracking System]

Your message dated Fri, 21 Feb 2020 14:48:38 +
with message-id 
and subject line Bug#951727: fixed in shotcut 20.02.17-2
has caused the Debian Bug report #951727,
regarding qmelt: command not found
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.)


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

Dear Maintainer,

shotcut uses the program qmelt to export the videos. However, unless I'm
mistaken, this program is nowhere to be found in debian.

This has already been asked on the forum of shotcut and been discarded
as a packaging issue.
https://forum.shotcut.org/t/shotcut-export-not-working-usr-bin-nice-usr-bin-qmelt-not-found/8043


I tagged this bug as grave since the inability to export a video would
make the whole package pretty useless for most people.

It looks like this bug was already reported back in 2016 for a
non-official debian version.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818114

If anyone has already managed to use this package, I wonder where does
their qmelt program come from.

Best regards,
Celelibi


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

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

Versions of packages shotcut depends on:
ii  libc6  2.29-10
ii  libgcc-s1  10-20200211-1
ii  libjs-three111+dfsg1-1
ii  libmlt++3  6.20.0-1
ii  libmlt66.20.0-1
ii  libqt5core5a   5.12.5+dfsg-8
ii  libqt5gui5 5.12.5+dfsg-8
ii  libqt5multimedia5  5.12.5-1+b1
ii  libqt5network5 5.12.5+dfsg-8
ii  libqt5opengl5  5.12.5+dfsg-8
ii  libqt5qml5 5.12.5-5
ii  libqt5quick5   5.12.5-5
ii  libqt5quickwidgets55.12.5-5
ii  libqt5sql5 5.12.5+dfsg-8
ii  libqt5webkit5  5.212.0~alpha3-6
ii  libqt5websockets5  5.12.5-2+b1
ii  libqt5widgets5 5.12.5+dfsg-8
ii  libqt5xml5 5.12.5+dfsg-8
ii  libstdc++6 10-20200211-1
ii  qml-module-qtgraphicaleffects  5.12.5-2+b1
ii  qml-module-qtqml-models2   5.12.5-5
ii  qml-module-qtquick-controls5.12.5-1+b1
ii  qml-module-qtquick-controls2   5.12.5+dfsg-2+b1
ii  qml-module-qtquick-dialogs 5.12.5-1+b1
ii  qml-module-qtquick-extras  5.12.5-1+b1
ii  qml-module-qtquick-layouts 5.12.5-5
ii  qml-module-qtquick-window2 5.12.5-5
ii  qml-module-qtquick25.12.5-5

shotcut recommends no packages.

shotcut suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: shotcut
Source-Version: 20.02.17-2
Done: =?utf-8?q?G=C3=BCrkan_Myczko?= 

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

Debian distribution maintenance software
pp.
Gürkan Myczko  (supplier of updated shotcut package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 21 Feb 2020 09:04:34 +0100
Source: shotcut
Architecture: source
Version: 20.02.17-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Gürkan Myczko 
Closes: 951727
Changes:
 shotcut (20.02.17-2) unstable; urgency=medium
 .
   * d/control: add melt to Depends. (Closes: #951727)
Checksums-Sha1:
 9e14bd4e3f9a6649c405636d9a1cdf194d59630c 2263 shotcut_20.02.17-2.dsc
 f33cf84fe7217ce8974bb9a63f32d4964de2f0ac 9684 

Bug#948493: marked as done (the Python2 -dbg package should depend on python2-dbg)

[Debian Bug Tracking System]

Your message dated Fri, 21 Feb 2020 14:45:11 +
with message-id 
and subject line Bug#948493: fixed in libxml2 2.9.10+dfsg-2
has caused the Debian Bug report #948493,
regarding the Python2 -dbg package should depend on python2-dbg
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.)


-- 
948493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libxml2
Version: 2.9.4+dfsg1-8
Severity: serious
Tags: sid bullseye patch

the Python2 -dbg package should depend on python2-dbg, instead of python-dbg.

http://launchpadlibrarian.net/459845187/libxml2_2.9.4+dfsg1-8ubuntu1_2.9.4+dfsg1-8ubuntu2.diff.gz
--- End Message ---
--- Begin Message ---
Source: libxml2
Source-Version: 2.9.10+dfsg-2
Done: Mattia Rizzolo 

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated libxml2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 21 Feb 2020 14:45:03 +0100
Source: libxml2
Architecture: source
Version: 2.9.10+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian XML/SGML Group 
Changed-By: Mattia Rizzolo 
Closes: 948493
Changes:
 libxml2 (2.9.10+dfsg-2) unstable; urgency=medium
 .
   * Team upload
   * Re-instate Python2 support for now, the rev-deps are not ready.
 Re-opens: #936941
   * python-libxml2-dbg: Depend on python2-dbg instead of python-dbg.
 Closes: #948493
   * d/control: Bump Standards-Version 4.5.0, no changes needed.
   * Re-instnate the xml2-config script for now.
   * Upload to unstable.
Checksums-Sha1:
 2bcd579fc42f5502cdab9fe906d88ca9e1dff8bf 2908 libxml2_2.9.10+dfsg-2.dsc
 99f788c50578c2ba75b83f03bef86950872cf0e6 25248 
libxml2_2.9.10+dfsg-2.debian.tar.xz
 a6d402f3ef4c1074040a8874d292eb02970c5a90 10534 
libxml2_2.9.10+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 82d459277749cc5d14ad9efe4c550ec4cc3987f4cfece130b06c5cea35edda15 2908 
libxml2_2.9.10+dfsg-2.dsc
 7948f53a6e913b1665bfc529d98e72d36c3fe9863dcc6da6857bc05998c79cc8 25248 
libxml2_2.9.10+dfsg-2.debian.tar.xz
 5b86ee624bf3193c3281995587932ed55ccf46dcb0694e2c198360cb8934c314 10534 
libxml2_2.9.10+dfsg-2_amd64.buildinfo
Files:
 eb59590eb6995ee784e1e0bc4f841756 2908 libs optional libxml2_2.9.10+dfsg-2.dsc
 4d52b846ecf347a2b1270f24d1fee3d9 25248 libs optional 
libxml2_2.9.10+dfsg-2.debian.tar.xz
 28e21f582030efa81a9b18a1d84700a4 10534 libs optional 
libxml2_2.9.10+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAl5P36gACgkQCBa54Yx2
K60sog//SCmcGLLi4s98fOlGe1XLj9mGlWKTJ2HvxeN0lMBj/AAgrQEOnSTBj9cQ
gWJf9dLeuCbjQsKso12w7UhU3nuhmKQm0TSMqkdE616fJiML/frEw7j+hC3X2ZpU
ucrF+aadsGfF4vwc+a/J5rtGDtXjCyMjgN5MeSPlC1FSiwcI1Tfle0IRK2xUBCTb
w25qp891DAaEuw9a6GHrVFixkMEn6Qa1+yAIwukAjdumgL7NinLpyicQjRycUUFL
I4glAhJQ49JAk8wLGqF3zTSyBE9LRniKuz96245bmIKOsXrQT+QlOmX9fcpIbzyF
hDoHjb6ST+n1YjiTESBvIN8LMT/3y7QkE6dBCqyX0/YKH2nF7g4ywdy/9+Si+Sok
5NhNGKbgebLbOI023iixFlcRzLS6ozcLpnq+OM9zQdgPkOJTxmTVWebXJsNw3oQR
wKXLK3we+dVEIb5Jk1j4ai48jrHv3gPWPoqzd6Q3MsfSpgcoI4NdfaMUOi/Z/v4U
Sjc6EevQ5ZY5RGQr7YPWVU9qwkw+90U85IM0eMIRwTCCmI8sKm993KTBbxjtwTXy
AJTtHvzU6V+1tKI2CKB1+3FCzCrymmqVO+c+XGdNPkY+5ICtOg1bhjnep21GrKCc
UTEk74m2GiP96iN21IO53LYVk2X1Yj4fDJDVMmVDXPdIyq8XErA=
=4Ooz
-END PGP SIGNATURE End Message ---

Bug#875041: marked as done ([meshlab] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Fri, 21 Feb 2020 14:45:59 +
with message-id 
and subject line Bug#875041: fixed in meshlab 2020.02+git200217-1
has caused the Debian Bug report #875041,
regarding [meshlab] Future Qt4 removal from Buster
to be marked as done.

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

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


-- 
875041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: meshlab
Version: 1.3.2+dfsg1-4
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


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

[announced] 


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

[OpenSSL 1.1 support] 

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

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

= Porting =

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

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

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

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

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

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: meshlab
Source-Version: 2020.02+git200217-1
Done: =?utf-8?q?G=C3=BCrkan_Myczko?= 

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

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

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

Debian distribution maintenance software
pp.
Gürkan Myczko  (supplier of updated meshlab 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, 17 Feb 2020 14:52:55 +0100
Source: meshlab
Architecture: source
Version: 2020.02+git200217-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Gürkan Myczko 
Closes: 875041 910660 946685
Changes:
 meshlab (2020.02+git200217-1) unstable; urgency=medium
 .
   * Team upload.
   * Add myself to Uploaders.
   * New upstream version. (Closes: #910660, #946685, #875041)
   * debian/patches: lost+notfound.
   * Update Vcs fields.
   * Bump standards version to 4.5.0.
   * Bump debhelper version to 12.
Checksums-Sha1:
 1617092b308ecf941d4ed11f988afba23e73c0c8 2285 meshlab_2020.02+git200217-1.dsc
 20687671ff458d861d88de759d231655c3fa0d3d 50256752 
meshlab_2020.02+git200217.orig.tar.xz
 9a750dcf5ba957f2dfbccf88b56fadb1769c4617 9112 
meshlab_2020.02+git200217-1.debian.tar.xz
 e5f95258b6f35f43db4534030a0badec9acac3f6 10818 
meshlab_2020.02+git200217-1_source.buildinfo
Checksums-Sha256:
 106a187082ecdbda7cb08927d8a31774bc213ead3da029c5dc6370c138ed34a5 2285 
meshlab_2020.02+git200217-1.dsc
 a50836c9800ac1e0e7cefb55b838188c0ad6e8a891286b390cb9305611596979 50256752 
meshlab_2020.02+git200217.orig.tar.xz
 7075224ec4c144f7fe6964faa7d385f7743427957946ad48241ba3699ea35d86 9112 
meshlab_2020.02+git200217-1.debian.tar.xz
 8e7f7a05bb969ed2682bf57292a01d250dabdbf7c466ee837e81d55668c9de70 10818 
meshlab_2020.02+git200217-1_source.buildinfo

Bug#951770: libpam-radius-auth: do not release in bullseye without active maintainer

[Salvatore Bonaccorso]

Source: libpam-radius-auth
Version: 1.4.0-3
Severity: serious
Justification: should not be released in bullseye without active maintainer

libpam-radius-auth has been orphaned in Debian since several years and
QA maintained. It did had at least the CVE-2015-9542 security issue.

There are no packages blocking a potential removal, so the package
should get an active maintainer to be part of bullseye ideally.

Regards,
Salvatore

Processed: severity of 951396 is grave

[Debian Bug Tracking System]

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

> severity 951396 grave
Bug #951396 {Done: Utkarsh Gupta } [src:libpam-radius-auth] 
libpam-radius-auth: CVE-2015-9542
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Processed: raising to RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #949493 [src:ruby-libxml] ruby-libxml: FTBFS with libxml2 2.9.10
Severity set to 'serious' from 'important'

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

Processed: raising to RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #949099 [src:cairo-dock-plug-ins] cairo-dock-plug-ins: different build 
contents with libxml2 2.9.10+dfsg-1
Severity set to 'serious' from 'important'

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

Processed: raising to RC

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #949419 [src:nexus] nexus: FTBFS with libxml2 2.9.10
Severity set to 'serious' from 'important'

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

Processed: reassign 951698 to cryptsetup-initramfs, forcibly merging 950628 951698

[Debian Bug Tracking System]

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

> reassign 951698 cryptsetup-initramfs
Bug #951698 {Done: Bastian Blank } [linux-image-amd64] linux 
kernel 5.x does not work with disk encryption 4.19 works
Bug reassigned from package 'linux-image-amd64' to 'cryptsetup-initramfs'.
Ignoring request to alter found versions of bug #951698 to the same values 
previously set
Ignoring request to alter fixed versions of bug #951698 to the same values 
previously set
> forcemerge 950628 951698
Bug #950628 {Done: Debian FTP Masters } 
[cryptsetup-initramfs] cryptsetup-initramfs: can't unlock argon2 keyslots: 
incompatible with libgcc1 1:10-20200202-1
Bug #951698 {Done: Bastian Blank } [cryptsetup-initramfs] 
linux kernel 5.x does not work with disk encryption 4.19 works
Marked as fixed in versions cryptsetup/2:2.2.2-3.
Marked as found in versions cryptsetup/2:2.2.2-2.
Merged 950628 951698
> thanks
Stopping processing here.

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

Processed: closing 948494

[Debian Bug Tracking System]

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

> close 948494 1.1.34-1
Bug #948494 [src:libxslt] the Python2 -dbg package should depend on 
python2-dbg, instead of python-dbg
Marked as fixed in versions libxslt/1.1.34-1.
Bug #948494 [src:libxslt] the Python2 -dbg package should depend on 
python2-dbg, instead of python-dbg
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: notfound 936942 in 1.1.34-2, closing 936942

[Debian Bug Tracking System]

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

> notfound 936942 1.1.34-2
Bug #936942 [src:libxslt] libxslt: Python2 removal in sid/bullseye
The source 'libxslt' and version '1.1.34-2' do not appear to match any binary 
packages
No longer marked as found in versions libxslt/1.1.34-2.
> close 936942
Bug #936942 [src:libxslt] libxslt: Python2 removal in sid/bullseye
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#951767: python-cartopy test failures with Python 3.8

[Matthias Klose]

Package: src:python-cartopy
Version: 0.17.0+dfsg-8
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8

Seen with both versions in unstable and experimental, here on amd64:

=== FAILURES ===
_ test_transform_point _

def test_transform_point():
"""
Mostly tests the workaround for a specific problem.
Problem report in: https://github.com/SciTools/cartopy/issues/23
Fix covered in: https://github.com/SciTools/cartopy/pull/277
"""

# this way has always worked
result = _CRS_ROB.transform_point(35.0, 70.0, _CRS_PC)
>   assert_array_almost_equal(result, (2376187.27182751, 7275317.81573085),
  _TOL)
E   AssertionError:
E   Arrays are not almost equal to 7 decimals
E
E   Mismatch: 100%
E   Max absolute difference: 0.30056718
E   Max relative difference: 4.13132717e-08
Ex: array([2376187.2182271, 7275318.116298 ])
Ey: array([2376187.2718275, 7275317.8157309])

cartopy/tests/crs/test_robinson.py:126: AssertionError
 test_transform_points _

def test_transform_points():
"""
Mostly tests the workaround for a specific problem.
Problem report in: https://github.com/SciTools/cartopy/issues/23
Fix covered in: https://github.com/SciTools/cartopy/pull/277
"""

# these always worked
result = _CRS_ROB.transform_points(_CRS_PC,
   np.array([35.0]),
   np.array([70.0]))
>   assert_array_almost_equal(result,
  [[2376187.27182751, 7275317.81573085, 0]], 
_TOL)
E   AssertionError:
E   Arrays are not almost equal to 7 decimals
E
E   Mismatch: 66.7%
E   Max absolute difference: 0.30056718
E   Max relative difference: 4.13132717e-08
Ex: array([[2376187.2182271, 7275318.116298 ,   0.   ]])
Ey: array([[2376187.2718275, 7275317.8157309,   0.   ]])

cartopy/tests/crs/test_robinson.py:149: AssertionError
== 2 failed, 421 passed, 2 skipped, 111 deselected, 2 xfailed in 8.37 seconds ==
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=1: cd
'/packages/tmp/p/python-cartopy-0.18.0~b1+dfsg/.pybuild/cpython3_3.8_cartopy/build';
python3.8 -m pytest --pyargs -m "not network and not natural_earth"

Processed: Reassign to locales

[Debian Bug Tracking System]

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

> reassign 950840 locales
Bug #950840 [lxc-templates] English India selected during installation breaks 
locale in lxc
Bug reassigned from package 'lxc-templates' to 'locales'.
No longer marked as found in versions lxc-templates/3.0.3-1.
Ignoring request to alter fixed versions of bug #950840 to the same values 
previously set
> affects 950840 lxc-templates
Bug #950840 [locales] English India selected during installation breaks locale 
in lxc
Added indication that 950840 affects lxc-templates
> --
Stopping processing here.

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

Bug#951765: suricata: FTBFS on armel: atomic builtins clashing with Rust objects

[Sascha Steinbiss]

Source: suricata
Severity: serious
Tags: ftbfs help
Justification: fails to build from source (but built successfully in the past)

Suricata fails to build on armel at link time [1] due to duplicate objects 
between what
is built by the Rust compiler and what is built by gcc:

/usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/9/libgcc.a(linux-atomic.o): in 
function `__sync_fetch_and_add_4':
(.text+0x0): multiple definition of `__sync_fetch_and_add_4'; 
../rust/target/release/libsuricata.a(compiler_builtins-d2631cd9ed12b87c.compiler_builtins.k83988xm-cgu.1.rcgu.o):(.text.__sync_fetch_and_add_4+0x0):
 first defined here
/usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/9/libgcc.a(linux-atomic.o): in 
function `__sync_fetch_and_sub_4':
(.text+0x38): multiple definition of `__sync_fetch_and_sub_4'; 
../rust/target/release/libsuricata.a(compiler_builtins-d2631cd9ed12b87c.compiler_builtins.k83988xm-cgu.1.rcgu.o):(.text.__sync_fetch_and_sub_4+0x0):
 first defined here
/usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/9/libgcc.a(linux-atomic.o): in 
function `__sync_fetch_and_or_4':
(.text+0x70): multiple definition of `__sync_fetch_and_or_4'; 
../rust/target/release/libsuricata.a(compiler_builtins-d2631cd9ed12b87c.compiler_builtins.k83988xm-cgu.1.rcgu.o):(.text.__sync_fetch_and_or_4+0x0):
 first defined here
/usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/9/libgcc.a(linux-atomic.o): in 
function `__sync_fetch_and_and_4':
(.text+0xa8): multiple definition of `__sync_fetch_and_and_4'; 
../rust/target/release/libsuricata.a(compiler_builtins-d2631cd9ed12b87c.compiler_builtins.k83988xm-cgu.1.rcgu.o):(.text.__sync_fetch_and_and_4+0x0):
 first defined here
/usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/9/libgcc.a(linux-atomic.o): in 
function `__sync_fetch_and_xor_4':
(.text+0xe0): multiple definition of `__sync_fetch_and_xor_4'; 
../rust/target/release/libsuricata.a(compiler_builtins-d2631cd9ed12b87c.compiler_builtins.k83988xm-cgu.1.rcgu.o):(.text.__sync_fetch_and_xor_4+0x0):
 first defined here
/usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/9/libgcc.a(linux-atomic.o): in 
function `__sync_fetch_and_nand_4':
(.text+0x118): multiple definition of `__sync_fetch_and_nand_4'; 
../rust/target/release/libsuricata.a(compiler_builtins-d2631cd9ed12b87c.compiler_builtins.k83988xm-cgu.1.rcgu.o):(.text.__sync_fetch_and_nand_4+0x0):
 first defined here
/usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/9/libgcc.a(linux-atomic.o): in 
function `__sync_fetch_and_add_2':
(.text+0x154): multiple definition of `__sync_fetch_and_add_2'; 
../rust/target/release/libsuricata.a(compiler_builtins-d2631cd9ed12b87c.compiler_builtins.k83988xm-cgu.1.rcgu.o):(.text.__sync_fetch_and_add_2+0x0):
 first defined here
/usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/9/libgcc.a(linux-atomic.o): in 
function `__sync_fetch_and_sub_2':
(.text+0x1b4): multiple definition of `__sync_fetch_and_sub_2'; 
../rust/target/release/libsuricata.a(compiler_builtins-d2631cd9ed12b87c.compiler_builtins.k83988xm-cgu.1.rcgu.o):(.text.__sync_fetch_and_sub_2+0x0):
 first defined here
/usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/9/libgcc.a(linux-atomic.o): in 
function `__sync_fetch_and_or_2':
(.text+0x214): multiple definition of `__sync_fetch_and_or_2'; 
../rust/target/release/libsuricata.a(compiler_builtins-d2631cd9ed12b87c.compiler_builtins.k83988xm-cgu.1.rcgu.o):(.text.__sync_fetch_and_or_2+0x0):
 first defined here
/usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/9/libgcc.a(linux-atomic.o): in 
function `__sync_fetch_and_and_2':
(.text+0x274): multiple definition of `__sync_fetch_and_and_2'; 
../rust/target/release/libsuricata.a(compiler_builtins-d2631cd9ed12b87c.compiler_builtins.k83988xm-cgu.1.rcgu.o):(.text.__sync_fetch_and_and_2+0x0):
 first defined here
/usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/9/libgcc.a(linux-atomic.o): in 
function `__sync_fetch_and_xor_2':
(.text+0x2d4): multiple definition of `__sync_fetch_and_xor_2'; 
../rust/target/release/libsuricata.a(compiler_builtins-d2631cd9ed12b87c.compiler_builtins.k83988xm-cgu.1.rcgu.o):(.text.__sync_fetch_and_xor_2+0x0):
 first defined here
/usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/9/libgcc.a(linux-atomic.o): in 
function `__sync_fetch_and_nand_2':
(.text+0x334): multiple definition of `__sync_fetch_and_nand_2'; 
../rust/target/release/libsuricata.a(compiler_builtins-d2631cd9ed12b87c.compiler_builtins.k83988xm-cgu.1.rcgu.o):(.text.__sync_fetch_and_nand_2+0x0):
 first defined here
/usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/9/libgcc.a(linux-atomic.o): in 
function `__sync_fetch_and_add_1':
(.text+0x398): multiple definition of `__sync_fetch_and_add_1'; 
../rust/target/release/libsuricata.a(compiler_builtins-d2631cd9ed12b87c.compiler_builtins.k83988xm-cgu.1.rcgu.o):(.text.__sync_fetch_and_add_1+0x0):
 first defined here
/usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/9/libgcc.a(linux-atomic.o): in 
function `__sync_fetch_and_sub_1':
(.text+0x3f4): multiple definition of `__sync_fetch_and_sub_1'; 

Bug#951721: marked as done (autopkgtest suite flaky on arm64: command10 randomly fails)

[Debian Bug Tracking System]

Your message dated Fri, 21 Feb 2020 11:35:05 +
with message-id 
and subject line Bug#951721: fixed in suricata 1:5.0.2-1
has caused the Debian Bug report #951721,
regarding autopkgtest suite flaky on arm64: command10 randomly fails
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.)


-- 
951721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: suricata
Version: 1:4.1.5-2
Severity: serious
User: debian...@lists.debian.org

Hi,

the autopkgtest suite appears to be flaky on arm64. Sometimes it
succeeds, sometimes command10 fails.

This is problematic, as this (randomly) blocks other packages from
entering testing, a recent example is systemd which is currently blocked
because of

  autopkgtest for suricata/1:4.1.5-2: amd64: Pass, arm64: Regression

I asked on #debci, and they recommended to file this as RC bug.
If you think this is an issue of the debci arm64 infrastructure, please
get in touch with debian...@lists.debian.org.

Regards,
Michael
--- End Message ---
--- Begin Message ---
Source: suricata
Source-Version: 1:5.0.2-1
Done: Sascha Steinbiss 

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

Debian distribution maintenance software
pp.
Sascha Steinbiss  (supplier of updated suricata package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 20 Feb 2020 14:55:23 +0100
Source: suricata
Architecture: source
Version: 1:5.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Pierre Chifflier 
Changed-By: Sascha Steinbiss 
Closes: 951654 951721
Changes:
 suricata (1:5.0.2-1) unstable; urgency=medium
 .
   * New upstream release.
 Closes: #951654
   * Add patch from upstream to build without needing if_tunnel.h.
 This avoids a potentially foreign arch build-dep for eBPF builds.
 Thanks to Eric Leblond.
   * Drop patches applied upstream.
   * Use debhelper-compat.
   * Mark autopkgtests requiring a control socket as potentially flaky.
 We cannot always predict the timing on all archs and do not want to
 use them for CI gating.
 Closes: #951721
   * Bring d/copyright up to date with current code base.
Checksums-Sha1:
 08392a384246f71de438f30fc9fe06d315f62cb4 2921 suricata_5.0.2-1.dsc
 5e872e8ddd17d17b11488a2e1e045be21afc1a59 17604228 suricata_5.0.2.orig.tar.xz
 2b7735ec839498ec4333c9b2bd469b6ca24a78a3 29600 suricata_5.0.2-1.debian.tar.xz
 38ad28123c14162db2c403243fff68cac9aa9856 10703 suricata_5.0.2-1_amd64.buildinfo
Checksums-Sha256:
 318308d9fab4ac768b625c5ebc00e21bf29eb7e8acb33698f75f9fae8c9c7f0e 2921 
suricata_5.0.2-1.dsc
 09dc99aec24162b13d0028614255374a74068b1bca5fc78c4ccc6cc1a0d82e93 17604228 
suricata_5.0.2.orig.tar.xz
 9e94c436da2c7fea9a0a7bea117f068f1ed3924f5c21f0e5f35233a12a33e612 29600 
suricata_5.0.2-1.debian.tar.xz
 fbad670a4361d37f811fd9844a80ddc15e3c225c620699e4f3100f9a0eaaa33b 10703 
suricata_5.0.2-1_amd64.buildinfo
Files:
 412205e7b2fcffef0f289418db361eef 2921 net optional suricata_5.0.2-1.dsc
 10e692f46f75d2f6dd6c7cb7f59631aa 17604228 net optional 
suricata_5.0.2.orig.tar.xz
 19d35fbf2fbabee13605afb6ff178877 29600 net optional 
suricata_5.0.2-1.debian.tar.xz
 8f11835716430681c6801d35f6a8e7ec 10703 net optional 
suricata_5.0.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEWzS6WqtVB+kDQm6F6NN64vCfSHIFAl5PvUIACgkQ6NN64vCf
SHKEpA//WaxKCZGO9CJMkEz+bGqh90hRrK8+Uk4IvcAuG+ZocUuTVW4D1gWK1xal
27VKHSY/6FY/Rke96GEUjk65qkALQfci3X5d+/8dzw8d92GHj6whcnawso0Wmt3/
tVCk051J23ns9ZraEJ1zK1KaCRXEVv3oAcOIpVWOegkgs4FfqIMxbFaomHeJuB/u
1wVuoF2obTAJLwypCuEU/UHTN0FnX/X9hPztlIz2Bor8jcU7Z/lj10hgWkvKWWf/
i+Pn/Y0Qa/AMbtU0RCO1mU4N13vQTLL7u7C+lqfaxq74ZWIzJDdpHiDAFUPWEWEA
27YEssDFaE7eYMeRoRp/OfDCxrWhCj++Evht/9sutNOGA0k/APUfdY8A0gUpQo3h
rBV50lrRtAVHMp1pCcUpnGUuOJGwKRcOYej5OI4TBfmG6Wg8XlLpYfFFhTtVGOX9
Zut2CFmX2VNmGu8ojzFMzsPB84znJ8t5h9+moAZ3BxnzVUvAJ0AO4PiPpbZAgOta
J1na+Gg3OGoNkFch1/zj3o4IQkpcg0eD6/E1sPTXtVk7zPqMhYcnZ/lBAapedZF1
HHLW1R3u/hRh3HGvwA4nDZVK7JfkTtOxgoRRrxx0ZXHAtvaOQedqEjrrrwVwqnH0

Bug#855541: Update: actually it works

[Jean-Philippe MENGUAL]

Jean-Philippe MENGUAL

Le 21/02/2020 à 11:20, Alberto Garcia a écrit :

On Fri, Feb 21, 2020 at 04:05:51AM +0100, Jean-Philippe MENGUAL wrote:


Ok I have just built the git release, now it works. So to maintain
this package usable in Debian, you need to update it to the latest
git release, from December, 28. Do you want a specific bug to
request update? Without it, I think it is unusable now.


The Debian package is from the December 28 release (hence the version
number 0.0.0+git20191228-1). Which one are you trying?

Berto


oops sorry, should not have worked by night. The fact is that when I 
used the package, I go the error I mentioned. Then I removed it then 
installed the Git repo one building manually, and it worked. But now I 
re-installed the package and works too, and it is the same release indeed.


Well strange. So the package seems to work, thanks! Sorry for noise.

Best regards

Bug#855541: Update: actually it works

[Alberto Garcia]

On Fri, Feb 21, 2020 at 04:05:51AM +0100, Jean-Philippe MENGUAL wrote:

> Ok I have just built the git release, now it works. So to maintain
> this package usable in Debian, you need to update it to the latest
> git release, from December, 28. Do you want a specific bug to
> request update? Without it, I think it is unusable now.

The Debian package is from the December 28 release (hence the version
number 0.0.0+git20191228-1). Which one are you trying?

Berto

Bug#885299: bumping severity of pygtk bugs

[Piotr Ożarowski]

[Moritz Mühlenhoff, 2020-02-20]
> On Sun, Oct 06, 2019 at 05:09:30PM -0400, Jeremy Bicha wrote:
> > Control: severity -1 serious
> > Control: tags -1 -buster
> > 
> > 
> > As part of the Python2 removal, it is our intent that pygtk will be removed 
> > from Testing before the release of Debian 11
> > "Bullseye". Therefore, I am bumping the severity of this bug to Serious to 
> > ensure that there is plenty of warning before
> > the Debian 11 release and to make the eventual removal of pygtk as smooth 
> > as possible.
> 
> Should griffith be removed? It's dropped from testing for two years now
> and the upstream homepage vanished. Piotr, given that you're among the
> upstream authors, is this still maintained?

unfortunately it should be removed from Debian. Maybe some day I will
find time to update it to Python 3 and new GTK, but not anytime soon.

Bug#950207: python-crontab: diff for NMU version 1.9.3-3.1

[Håvard Flaget Aasen]

Version: 1.9.3-3
Tags: patch  pending

Dear maintainer,

I've prepared an NMU for python-crontab (versioned as 1.9.3-3.1) and
uploaded it to DELAYED/XX. Please feel free to tell me if I
should delay it longer.

Regards.
Håvard
diff -Nru python-crontab-1.9.3/debian/changelog 
python-crontab-1.9.3/debian/changelog
--- python-crontab-1.9.3/debian/changelog   2019-07-22 01:34:59.0 
+0200
+++ python-crontab-1.9.3/debian/changelog   2020-02-21 09:05:51.0 
+0100
@@ -1,3 +1,12 @@
+python-crontab (1.9.3-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove python as dependency from autopkgtest. closes: #937670, #950207
+  * Change from deprecated ADTTMP to AUTOPKGTEST_TMP in autopkgtest.
+  * Remove ancient X-python-version field in d/control
+
+ -- Håvard Flaget Aasen   Fri, 21 Feb 2020 09:05:51 
+0100
+
 python-crontab (1.9.3-3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru python-crontab-1.9.3/debian/control 
python-crontab-1.9.3/debian/control
--- python-crontab-1.9.3/debian/control 2019-07-22 01:34:59.0 +0200
+++ python-crontab-1.9.3/debian/control 2020-02-21 08:58:08.0 +0100
@@ -14,8 +14,6 @@
 Homepage: https://launchpad.net/python-crontab
 Vcs-Browser: https://github.com/jmetzmeier/python-crontab-debian
 Vcs-Git: https://github.com/jmetzmeier/python-crontab-debian.git
-X-Python3-Version: >= 3.3
-X-Python-Version: >= 2.7
 
 Package: python3-crontab
 Architecture: all
diff -Nru python-crontab-1.9.3/debian/tests/control 
python-crontab-1.9.3/debian/tests/control
--- python-crontab-1.9.3/debian/tests/control   2019-07-22 01:34:59.0 
+0200
+++ python-crontab-1.9.3/debian/tests/control   2020-02-21 08:53:17.0 
+0100
@@ -1,3 +1,3 @@
 Tests: python3-crontab
-Depends: python3-crontab, python, python3-pytest, python3-all
+Depends: python3-crontab, python3-pytest, python3-all
 Restrictions: allow-stderr
diff -Nru python-crontab-1.9.3/debian/tests/python3-crontab 
python-crontab-1.9.3/debian/tests/python3-crontab
--- python-crontab-1.9.3/debian/tests/python3-crontab   2019-07-22 
01:34:59.0 +0200
+++ python-crontab-1.9.3/debian/tests/python3-crontab   2020-02-21 
09:02:32.0 +0100
@@ -1,7 +1,7 @@
 #!/bin/sh
 set -e -u
-cp -a tests/ "$ADTTMP"
-cd "$ADTTMP/tests/"
+cp -a tests/ "$AUTOPKGTEST_TMP"
+cd "$AUTOPKGTEST_TMP/tests/"
 for py in $(py3versions -i); do
 LC_ALL=C.UTF-8 "$py" -m pytest
 done

Bug#946518: marked as done (gitlab: gitalb-unicorn not starting on 12.2.9-5)

[Debian Bug Tracking System]

Your message dated Fri, 21 Feb 2020 13:39:00 +0530
with message-id <369e2e66-5754-9bf9-b10b-77b47f5e6...@onenetbeyond.org>
and subject line Re: Bug#946518: gitlab: gitalb-unicorn not starting on 12.2.9-5
has caused the Debian Bug report #946518,
regarding gitlab: gitalb-unicorn not starting on 12.2.9-5
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.)


-- 
946518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 12.2.9-5
Severity: grave
Tags: a11y
Justification: renders package unusable

Dear Maintainer,

After update to 12.2.9-5 gitlab-unicorn cannot start.
We cannot use gitlab.
The error seems to be related to 
https://gitlab.com/gitlab-org/gitlab-foss/issues/62535 .
Thanks

/usr/lib/ruby/vendor_ruby/graphql/schema/member/build_type.rb:114:in 
`to_type_name': Unhandled to_type_name input:  (NilClass) (RuntimeError)
from /usr/lib/ruby/vendor_ruby/graphql/schema/field.rb:116:in 
`connection?'
from /usr/lib/ruby/vendor_ruby/graphql/schema/field.rb:135:in `scoped?'
from /usr/lib/ruby/vendor_ruby/graphql/schema/field.rb:260:in 
`initialize'
from 
/usr/lib/ruby/vendor_ruby/graphql/schema/member/accepts_definition.rb:142:in 
`initialize'
from /usr/share/gitlab/app/graphql/types/base_field.rb:14:in 
`initialize'
from /usr/lib/ruby/vendor_ruby/graphql/schema/field.rb:107:in `new'
from /usr/lib/ruby/vendor_ruby/graphql/schema/field.rb:107:in 
`from_options'
from 
/usr/lib/ruby/vendor_ruby/graphql/schema/member/has_fields.rb:13:in `field'
from /usr/share/gitlab/app/graphql/types/query_type.rb:27:in 
`'
from /usr/share/gitlab/app/graphql/types/query_type.rb:4:in 
`'
from /usr/share/gitlab/app/graphql/types/query_type.rb:3:in `'
from 
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in
 `require'
from 
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in
 `block in require'
from 
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in
 `load_dependency'
from 
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in
 `require'
from 
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:378:in
 `block in require_or_load'
from 
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:37:in
 `block in load_interlock'
from 
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies/interlock.rb:14:in
 `block in loading'
from 
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/concurrency/share_lock.rb:151:in
 `exclusive'
from 
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies/interlock.rb:13:in
 `loading'
from 
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:37:in
 `load_interlock'
from 
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:356:in
 `require_or_load'
from 
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:510:in
 `load_missing_constant'
from 
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:195:in
 `const_missing'
from /usr/share/gitlab/app/graphql/gitlab_schema.rb:26:in 
`'
from /usr/share/gitlab/app/graphql/gitlab_schema.rb:3:in `'
from 
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in
 `require'
from 
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in
 `block in require'
from 
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in
 `load_dependency'
from 
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in
 `require'
from 
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:378:in
 `block in require_or_load'
from 
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:37:in
 `block in load_interlock'
from 

Processed: Re: Bug#946518: gitlab: gitalb-unicorn not starting on 12.2.9-5

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 12.4.6-1
Bug #946518 [gitlab] gitlab: gitalb-unicorn not starting on 12.2.9-5
Marked as fixed in versions gitlab/12.4.6-1.

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

Bug#946518: gitlab: gitalb-unicorn not starting on 12.2.9-5

[Pirate Praveen]

Control: fixed -1 12.4.6-1

On Wed, 11 Dec 2019 07:34:06 +0530 Pirate Praveen
 wrote:
> 
> 
> On 2019, ഡിസംബർ 10 11:26:19 PM IST, Dragos Jarca 
>  wrote:
> >Thx
> >
> >Solved installing 
> >http://snapshot.debian.org/archive/debian-ports/20180917T212034Z/pool/main/r/ruby-graphql/ruby-graphql_1.8.4-1_all.deb
> >
> >Don't thinked at this solution.
> >
> >In my system this package is used only by gitlab.
> 
> This was updated for gitlab 12.3.8, but it is not yet ready to use. Since it 
> was a minor update, I was not expecting a breakage.

Closing this bug now.



signature.asc
Description: OpenPGP digital signature