Processed: severity of 953229 is normal

[Debian Bug Tracking System]

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

> severity 953229 normal
Bug #953229 [src:coq] coq: FTBFS test failures
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#952759: Fwd: Bug#952759: libsass-python 0.18.0 FTBFS with libsass 3.6.3, please upgrade to 0.19.4

[Anthony Fok]

(Oops, forgot to send to the bug report too, forwarding...)

-- Forwarded message -
From: Anthony Fok 
Date: Mon, Mar 9, 2020 at 7:28 PM
Subject: Re: Bug#952759: libsass-python 0.18.0 FTBFS with libsass
3.6.3, please upgrade to 0.19.4
To: Frédéric Bonnard 


Hi Fred,

On Mon, Mar 9, 2020 at 3:16 AM Frédéric Bonnard  wrote:
> March 9, 2020 8:30 AM, "Anthony Fok"  wrote:
> > [testing errors] which all go away with libsass-python 0.19.4.
> expected at some point :)
> I remember having checked in January the status of libsass which latest
> version was still in experimental.

Indeed.  It seems that Jonas (libsass's original maintainer) is quite
conservative with upgrading libsass, probably wary of breakage, though
it is understandable as it seems to be the time of Debian buster's
freeze and imminent release.  I am glad that Jonas did package 3.6.1
in experimental, as it does help my preparation of libsass 3.6.3 much
smoother.

And indeed, to this day, node-node-sass (node-sass upstream) is still
not compatible with libsass 3.6.3, and the upstream authors cite "it
is a volunteer project" as the reason for having no time line for the
upgrade... Thankfully, node-node-sass can be built with its embedded
copy of libsass 3.5.5 for the time being.

My impetus is to get the latest Hugo, which requires libsass 3.6.3,
into Debian (and Ubuntu).  And everyone seems to be saying that
libsass 3.6.3 solves some significant security issues, and we are in
relatively early stages of bullseye cycle, so I'd say, let's be bold
and upgrade and break things!  (and fix them)...

> > So, it would be great if you could upload libsass-python 0.19.4-1. :-)
> >
> > In case you are busy, since I have been fixing the ruby-sassc and
> > node-node-sass packages which also FTBFS due to the libsass 3.6.3
> > upgrade, I would be very happy to make an NMU upload of libsass-python
> > 0.19.4-0.1, which I have prepared at my fork at
> > https://salsa.debian.org/foka/libsass-python, and which I am happy to
> > upload any time, with your permission of course.
>
> It would be a shame to lose the work you've done already and that I didn't
> do, so feel free to NMU libsass-python.

You are very kind, thank you for your generosity!  I have done a "gbp
push" to your repository, and I will do a dput upload soon, like now.
:-)

> > Please let me know soon, especially because I would like to solve all
> > remaining libsass 3.6.3 upgrade issues, hopefully in time for Ubuntu
> > 20.04 LTS release.
>
> No worries, thanks a bunch for all the work and kind mail.

Thank you so much for your kind words and for maintaining the Python
binding for libsass!

Cheers,
Anthony

Bug#953235: vtkplotter: autopkgtest arm64 failure: No module named 'vtkIOFFMPEGPython'

[Drew Parsons]

Package: python3-vtkplotter
Followup-For: Bug #953235


Dodgy libgomp.so.  See https://github.com/pytorch/pytorch/issues/2575

Processed: retitle

[Debian Bug Tracking System]

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

> retitle 950177 "make check" fails non-deterministically
Bug #950177 [src:source-highlight] "make check" fails non-deterministically on 
arm64
Changed Bug title to '"make check" fails non-deterministically' from '"make 
check" fails non-deterministically on arm64'.
> thanks
Stopping processing here.

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

Bug#952759: marked as done (FTBFS with libsass 3.6.3, please upgrade to 0.19.4)

[Debian Bug Tracking System]

Your message dated Tue, 10 Mar 2020 01:34:32 +
with message-id 
and subject line Bug#952759: fixed in libsass-python 0.19.4-0.1
has caused the Debian Bug report #952759,
regarding FTBFS with libsass 3.6.3, please upgrade to 0.19.4
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.)


-- 
952759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsass-python
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

right now there is 0.19.4 available from upstream. Would you consider uploading
an updated package to the archive?

Cheers,
Michael


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

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

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAl5ZQfIRHGZsYWRpQGRl
Ymlhbi5vcmcACgkQ/9PIi5l90Wp0CAf/Qw7XsN1lXBnbsN3Bl0bFIT4HNWLlT3N2
PvZeW7wuZw7JZjfT+teu+X3HgUSRGj0V8+J+lSTDPFNRDsHCHCJIlnExE535b+sN
66/xOpW4KZ093AcuK45zlhachsz0dUH9U3manYWRj9PLNMRUSJD0QsvwoIKZNEqS
BuD2ZVuQQZfaLeaMSrpkx8IQJcM9nNYxjWlVhn7Ukmy912oAu+k7Fqs89lTgayeC
vJJn9Bi7P9olCCQ6ZFvlJqJEp3a3JWIre+/zTPALBMsf8Rk5h8VRqLlB8l+RCIqQ
z9cyR0agAOHu9GWg5IrcS9WlkcDNA53y3Dt93N3skWfh6PFt8IcOkg==
=A0zj
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libsass-python
Source-Version: 0.19.4-0.1
Done: Anthony Fok 

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

Debian distribution maintenance software
pp.
Anthony Fok  (supplier of updated libsass-python 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, 09 Mar 2020 00:31:31 -0600
Source: libsass-python
Architecture: source
Version: 0.19.4-0.1
Distribution: unstable
Urgency: medium
Maintainer: Frédéric Bonnard 
Changed-By: Anthony Fok 
Closes: 952759
Changes:
 libsass-python (0.19.4-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * New upstream release (Closes: #952759)
   * Link 0.19.4 with newer libsass 3.6.3
   * Bump Standards-Version to 4.5.0 (no change)
   * Add debian/gbp.conf to reflect the DEP-14 repository layout
Checksums-Sha1:
 b26b98377eff2cd24db7ff28d844fdccf909aa42 2111 libsass-python_0.19.4-0.1.dsc
 5c3dfee8fc8d358faaf60b48bfaab8c630cbe654 55934 
libsass-python_0.19.4.orig.tar.gz
 3d3166cd6272d35fb96b93037730a2bfea7eb16b 4152 
libsass-python_0.19.4-0.1.debian.tar.xz
 4381f9f1f327077d5a5987209fd0fdd816e164b4 8943 
libsass-python_0.19.4-0.1_amd64.buildinfo
Checksums-Sha256:
 15b33545f5cd6ab3176d114c603d328207ce2f6ebac2b022bcd2519ef6f4d332 2111 
libsass-python_0.19.4-0.1.dsc
 c8b8580c69457ebe593b7cc7905c7e601d2c899ff9011f9a4f7d1a7b75a22d8b 55934 
libsass-python_0.19.4.orig.tar.gz
 0caadac38565ca67f757c1db9fd7415c3069491a7e4f641b6efa53e8096cc6fa 4152 
libsass-python_0.19.4-0.1.debian.tar.xz
 600f893b63afd55bc24380ce454dd4fbf2dc3e290f37d303807bf118222c2a5e 8943 
libsass-python_0.19.4-0.1_amd64.buildinfo
Files:
 09c7246a133d175e62a3000e793f258d 2111 python optional 
libsass-python_0.19.4-0.1.dsc
 0015b37a683901fa5cb27c838b430e99 55934 python optional 
libsass-python_0.19.4.orig.tar.gz
 caa5ca1c0eb282031c6494f2f798650d 4152 python optional 
libsass-python_0.19.4-0.1.debian.tar.xz
 9441f0ef1fa3267ef00af82494aef4a8 8943 python optional 
libsass-python_0.19.4-0.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAl5mgJUACgkQ6iUAtBLF
ms8x3Q//brMGkRqK0uoAn3FFY2gwTjfR5kuB4ToRxQtmea5RBcFC64oLVG4b+agT
IJy00ZUvTbsB8ZQ3PK/t2egXnGvHa4eN2u+xN/MouwzmNfgMdVVp7JbLA7NNCF6Z
axTpKTUZ7jXW5FtKAwqNRreoofRol8LaqKLLmF3aP05vudvkzZN+sFnoxAeY6Ykm
OqNRyllp6vofmscEJAunnuww257tXTwO9SzEymIS0EmWeAIULoV4P9mV4JwbpS3S
AqyNNApfRLUsDo9Z6cWGIVyIFfMiARq

Bug#951842: marked as done (gringo needs a new upstream, and fixes for python3.8)

[Debian Bug Tracking System]

Your message dated Tue, 10 Mar 2020 01:22:33 +
with message-id 
and subject line Bug#951842: fixed in gringo 5.3.0-11
has caused the Debian Bug report #951842,
regarding gringo needs a new upstream, and fixes for python3.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.)


-- 
951842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gringo
Version: 5.3.0-10
Severity: important
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

gringo needs a new upstream, and fixes for python3.8. An example packaging can
be found at
https://launchpad.net/ubuntu/+source/gringo/5.4.0-0ubuntu1

Please note that I didn't address the GCC 8 -> GCC 9 move, which will also be
required for Debian.
--- End Message ---
--- Begin Message ---
Source: gringo
Source-Version: 5.3.0-11
Done: Thomas Krennwallner 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 09 Mar 2020 13:31:25 +0100
Source: gringo
Architecture: source
Version: 5.3.0-11
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Thomas Krennwallner 
Closes: 944178 951707 951842
Changes:
 gringo (5.3.0-11) experimental; urgency=medium
 .
   * add support for python3.8, thanks to Steve Langasek
   * compile with gcc-9 and g++-9
   * debian/control: bump Standards-Version to 4.5.0 (no changes required)
   * renamed debian/{NEWS,TODO}.Debian to debian/{NEWS,TODO}
 Lintian tag incorrect-packaging-filename
   * setup debhelper-compat 12.
 Lintian tag package-uses-old-debhelper-compat-version
   * debian/control: set Rules-Requires-Root to no
   * debian/symbols: fix symbols for g++-9 >= 9.2.0
   * Bug fix: "gringo needs a new upstream, and fixes for python3.8",
 thanks to Matthias Klose (Closes: #951842).
   * Bug fix: "gringo ftbfs with Python 3.8", thanks to Matthias Klose
 (Closes: #951707).
   * Bug fix: "non-standard gcc/g++ used for build (gcc-8)", thanks to
 Matthias Klose (Closes: #944178).
Checksums-Sha1:
 049d1e4e99c7f338491b6e826a5a6ae04f3a6a62 2149 gringo_5.3.0-11.dsc
 d226549353f88f58b74a82225fab1327cbab5355 19088 gringo_5.3.0-11.debian.tar.xz
 381933f70b79d2aa33f55f9dc97442095410699e 8299 gringo_5.3.0-11_amd64.buildinfo
Checksums-Sha256:
 356ad44f21cd4513e1264f18da8505ab50f0c26ba581e8b8c572a39aedfff347 2149 
gringo_5.3.0-11.dsc
 cc602a18480ae47fa2f7d704010c7df4912fa9e621163da80bfc875f6dca917d 19088 
gringo_5.3.0-11.debian.tar.xz
 a62ae7b03763ba01aaec02d15a72908b041ccbcb82e6e6c1a5b18e22088fbfe1 8299 
gringo_5.3.0-11_amd64.buildinfo
Files:
 6bb4605d56eeb3f02ba2c0dd6cb97950 2149 interpreters optional gringo_5.3.0-11.dsc
 b03752c3b8c15155ca09ae3200ed5041 19088 interpreters optional 
gringo_5.3.0-11.debian.tar.xz
 49fa00d68747adaa9f34e0e4fb72f0a7 8299 interpreters optional 
gringo_5.3.0-11_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEzH7vLECGZFUde0TKJ5ffdKZmmqkFAl5m5Y0ACgkQJ5ffdKZm
mqm5JQ/+LDN22urZQoiaNUmd/YPCQmb1HalTnr2ZMrLzpyGKmR2Uu7Ah5spn0RRD
s6WgDUUuUkHgFn4l4zUIeB3RzXic8GWrsgXSe04zw9PnoHz1tji0goeuzvGAJDgm
peLTg++fzUIIYFVW+i1/eWfnPiamW6Af/d9FmjvHtOafQjBTvEoquXS2fauDXOqU
VXZDE0JaGOONfkIHFZotxbK+7fzGNp5kWT/Kp89RwgGhfF6oUGYV3HK1+aQpcJBi
lsfQCRmNPXV0uYyVwaSrXOOWe5WWmCaFgOkUjaBCeba9FjB4k5MB0TN07HiHwtc3
SXULbbYUeIWh4WiqNVVJ1/XZtXvOehV9dDd5cmmvlUFTLz39xn9Ayg+FrAEC3hvd
apOWf+fB2w7AIFVf7w92VB29DYS7b1MHKmWPWN8Q0eCz89xII7ADslQV3SJoZpSO
xvlHxWFlqK1b2T0Sczi1xu+/yTn7jA0yC5ZwMR0ajum7MuM0s+vkFDOhotPIhZ2X
dsxW8EagHMkaM+m7FY0JRRBemqomhtmizEOvdQkXUoDcTT1ED/vGZz65eEBgp+8l
188bPr9scRNaJIc7U8B3CTHz7Z8a8XQU0by4604rhst0pJ6vFXFQi0fzH8d7FbSs
irw8n8XpstOyopFUHchQoCFZR24SxoXXlLbkIbClB7HhEF9nn+o=
=J+1p
-END PGP SIGNATURE End Message ---

Bug#951707: marked as done (gringo ftbfs with Python 3.8)

[Debian Bug Tracking System]

Your message dated Tue, 10 Mar 2020 01:22:33 +
with message-id 
and subject line Bug#951707: fixed in gringo 5.3.0-11
has caused the Debian Bug report #951707,
regarding gringo ftbfs 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.)


-- 
951707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gringo
Version: 5.3.0-10
Severity: important
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8

gringo ftbfs with Python 3.8:

[...]
packages/tmp/p/gringo-5.3.0/libclingo/clingo.hh:3871:32: warning: catching
polymorphic type ‘struct Clingo::Control::ground(Clingo::PartSpan,
Clingo::GroundCallback)Ret’ by
value [-Wcatch-value=]
 catch (Ret e) { return false; }
^
/packages/tmp/p/gringo-5.3.0/libpyclingo/pyclingo.cc: In instantiation of
‘PyTypeObject {anonymous}::ObjectBase<{anonymous}::Symbol>::type’:
/packages/tmp/p/gringo-5.3.0/libpyclingo/pyclingo.cc:1610:15:   required from 
here
/packages/tmp/p/gringo-5.3.0/libpyclingo/pyclingo.cc:1125:14: error: cannot
convert ‘std::nullptr_t’ to ‘Py_ssize_t’ {aka ‘long int’} in initialization
 PyTypeObject ObjectBase::type = {
  ^
/packages/tmp/p/gringo-5.3.0/libpyclingo/pyclingo.cc: In instantiation of
‘PyTypeObject {anonymous}::ObjectBase<{anonymous}::Flag>::type’:
/packages/tmp/p/gringo-5.3.0/libpyclingo/pyclingo.cc:7103:94:   required from 
here
/packages/tmp/p/gringo-5.3.0/libpyclingo/pyclingo.cc:1125:14: error: cannot
convert ‘std::nullptr_t’ to ‘Py_ssize_t’ {aka ‘long int’} in initialization
/packages/tmp/p/gringo-5.3.0/libpyclingo/pyclingo.cc: In instantiation of
‘PyTypeObject {anonymous}::ObjectBase<{anonymous}::TheoryTerm>::type’:
/packages/tmp/p/gringo-5.3.0/libpyclingo/pyclingo.cc:1065:21:   required from
‘static {anonymous}::SharedObject {anonymous}::ObjectBase::new_() [with T
= {anonymous}::TheoryTerm]’
/packages/tmp/p/gringo-5.3.0/libpyclingo/pyclingo.cc:1298:26:   required from 
here
/packages/tmp/p/gringo-5.3.0/libpyclingo/pyclingo.cc:1125:14: error: cannot
convert ‘std::nullptr_t’ to ‘Py_ssize_t’ {aka ‘long int’} in initialization
--- End Message ---
--- Begin Message ---
Source: gringo
Source-Version: 5.3.0-11
Done: Thomas Krennwallner 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 09 Mar 2020 13:31:25 +0100
Source: gringo
Architecture: source
Version: 5.3.0-11
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Thomas Krennwallner 
Closes: 944178 951707 951842
Changes:
 gringo (5.3.0-11) experimental; urgency=medium
 .
   * add support for python3.8, thanks to Steve Langasek
   * compile with gcc-9 and g++-9
   * debian/control: bump Standards-Version to 4.5.0 (no changes required)
   * renamed debian/{NEWS,TODO}.Debian to debian/{NEWS,TODO}
 Lintian tag incorrect-packaging-filename
   * setup debhelper-compat 12.
 Lintian tag package-uses-old-debhelper-compat-version
   * debian/control: set Rules-Requires-Root to no
   * debian/symbols: fix symbols for g++-9 >= 9.2.0
   * Bug fix: "gringo needs a new upstream, and fixes for python3.8",
 thanks to Matthias Klose (Closes: #951842).
   * Bug fix: "gringo ftbfs with Python 3.8", thanks to Matthias Klose
 (Closes: #951707).
   * Bug fix: "non-standard gcc/g++ used for build (gcc-8)", thanks to
 Matthias Klose (Closes: #944178).
Checksums-Sha1:
 049d1e4e99c7f338491b6e826a5a6ae04f3a6a62 2149 gringo_5.3.0-11.dsc
 d226549353f88f58b74a82225fab1327cbab5355 19088 gringo_5.3.0-11.debian.tar.xz
 381933f70b79d2aa33f55f9dc97442095410699e 8299 gringo_5.3.0-11_amd64.buildinfo
Checksums-Sha256:
 356ad44f21cd4513e1264f18da8505ab50f0c26ba581e8b8c572a39aedfff347 2149 
gringo_5.3.0-11.dsc
 cc602a18480ae47fa2f7d704010c7df4912fa9e621163

Bug#952475: marked as done (ats2-lang: Please make another source-only upload to allow testing migration)

[Debian Bug Tracking System]

Your message dated Tue, 10 Mar 2020 01:04:15 +
with message-id 
and subject line Bug#952475: fixed in ats2-lang 0.4.0-1
has caused the Debian Bug report #952475,
regarding ats2-lang: Please make another source-only upload to allow testing 
migration
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.)


-- 
952475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ats2-lang
Severity: serious
Version: 0.3.13-1
Justification: out-of-sync unstable-to-testing

Dear ats2-lang maintainer,

The latest upload of your package was not a source-only upload. As a result,
it did not migrate to 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 a Release Critical bug. Your package has been
out-of-sync for 67 days.

Please consider making another source-only upload to allow testing migration
according to https://wiki.debian.org/SourceOnlyUpload . Thanks!

-- 
Regards,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: ats2-lang
Source-Version: 0.4.0-1
Done: Matthew Danish 

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

Debian distribution maintenance software
pp.
Matthew Danish  (supplier of updated ats2-lang package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 10 Mar 2020 00:02:41 +
Source: ats2-lang
Architecture: source
Version: 0.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Matthew Danish 
Changed-By: Matthew Danish 
Closes: 952475
Changes:
 ats2-lang (0.4.0-1) unstable; urgency=medium
 .
   * New upstream release
   * Source only upload (Closes: #952475)
Checksums-Sha1:
 eb1942e4c035f626c31204c27af619f63071ddcd 1941 ats2-lang_0.4.0-1.dsc
 f9a734b6d7040633d16a11c73f06175afe04482f 4518542 ats2-lang_0.4.0.orig.tar.gz
 827162eb7227bf32358b50ab69c09b064cb3c937 9264 ats2-lang_0.4.0-1.debian.tar.xz
 e307e56ce4fa2ed09020aeb39396c585b198f001 11168 
ats2-lang_0.4.0-1_source.buildinfo
Checksums-Sha256:
 93f156fb593529c7315ce3ca4a9505b3ae9e8e9f7fc63eae185b4a256d403a95 1941 
ats2-lang_0.4.0-1.dsc
 a749b62d429eda45ec304075f1743e1a2638c4772d37b579839d7797470869c0 4518542 
ats2-lang_0.4.0.orig.tar.gz
 e528d6bc0b76306d95d76e7a56691d823250227a4c5c2bdb1537b502158025bb 9264 
ats2-lang_0.4.0-1.debian.tar.xz
 5138ef305c428184d0b8b0efa6e2d5886ba1b920289015ae7501bb1936cb4f6c 11168 
ats2-lang_0.4.0-1_source.buildinfo
Files:
 95315153e57767d5c841d0b0b24c2f12 1941 devel optional ats2-lang_0.4.0-1.dsc
 ed0a8212b23c8ce281b5512eb0dd130f 4518542 devel optional 
ats2-lang_0.4.0.orig.tar.gz
 cd124b5dc17dd63b8c84a2b22e4342d6 9264 devel optional 
ats2-lang_0.4.0-1.debian.tar.xz
 847c2b5749897e9fcc2200cca6dffcc5 11168 devel optional 
ats2-lang_0.4.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEvIUGUQ6c6R1J7CwLvBC9D3uL8IsFAl5m4iEPHG1yZEBkZWJp
YW4ub3JnAAoJELwQvQ97i/CLYPEQAIoIHvtEKknZLYxtXnA0LEm1gQr95+aQs4rL
84ujWJWc16wChAdsIhIwTH+JPIgk0+CbiQUqloB8BwhXB4pnvfWaze8sNOyaxQ19
t2z2E7UnKbd9odyQX8fEmtSICU764sr23dZgRv7m/47u9RpEuFO05W4B0G1y0y2E
CYbnALBmxeoUNSOW81xRSbPeIB31Ydw3vckItrvu2YnVQYYdZmtI65ZxLee4ySFD
v7i3RMWVkJRPf0G1W3BzjP25e3tQ6sPCUhVc6nqOTCP+cxYfPlydheAa0C1FS0PK
t/EUOoNPFWIFX4WbGpO4maEO6snhutbXUNcNZYErJ5a4u4qGiePF7Ce2goU8s0LF
qjRbW32E6YFu+/qOWOqtLfdIsnNbJFAsVFrOw27etr3lQNT4gzF84eGTTwgqjS0R
XH61yycfgRoua/Dy84PDTja3y6ZqS9STg2Xg0Sge2VpByuWZAxzDHXRPPgR/EdMB
zaQTNE95XgHiTsmJiuTweTznoVkfrIu0G9L1DMJ/+eilmUdUyTVZdmdCnC2U46Gv
cOlIO28Pc2VX34kxoX6YcTGSZFj1bx97VHDDCIwsZODjmUwAUSrZnJrSivsndv4Y
4/3orcGEG4+aRgr7vghwvf/GnRyMfgnbhEKc94jAc8VAIvhfOs4thwfeIrVz5tqo
CkR64CHm
=ADJP
-END PGP SIGNATURE End Message ---

Bug#938736: marked as done (txwinrm: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 10 Mar 2020 00:00:16 +
with message-id 
and subject line Bug#953482: Removed package(s) from unstable
has caused the Debian Bug report #938736,
regarding txwinrm: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:txwinrm

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.3.3-1+rm

Dear submitter,

as the package txwinrm 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/953482

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

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

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

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

Bug#946667: marked as done (mercurial-server: can't clone to or push repository to server (object has no attribute 'changectx'))

[Debian Bug Tracking System]

Your message dated Tue, 10 Mar 2020 00:00:43 +
with message-id 
and subject line Bug#953483: Removed package(s) from unstable
has caused the Debian Bug report #946667,
regarding mercurial-server: can't clone to or push repository to server (object 
has no attribute 'changectx')
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.)


-- 
946667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mercurial-server
Version: 1.2-2.2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

after upgrading my mercurial server from stretch to buster, I'm not
able to push or clone to this server from a buster client, the command
fails with:

...
remote:   File
"/usr/share/mercurial-server/mercurialserver/changes.py", line 6, in changes
remote: start = repo.changectx(node).rev()
remote: AttributeError:
'derivedrepo:/var/lib/mercurial-server/repos/projec' object has no
attribute 'changectx'
abort: stream ended unexpectedly (got 0 bytes, expected 4)

Only solution found is to disable access hook in
/etc/mercurial-server/remote-hgrc.d/access.rc but since it's removing
all access control security, this is not a real solution (and it also
raises another bug in the logging hook but at least repository is
cloned/pushed).

Clone from or pull are not affected (except for the logging hook bug).

Steps to reproduce:

sudo lxc-create hgserver -t debian --
--package=mercurial-server,openssh-server,sudo,reportbug -r buster
sudo lxc-start hgserver
sudo lxc-attach hgserver
apt update
apt dist-upgrade
cd
ssh-keygen
mkdir -p /etc/mercurial-server/keys/root
cp .ssh/id_rsa.pub /etc/mercurial-server/keys/root
sed -i 's/localhost/localhost hgserver/' /etc/hosts
sudo -u hg /usr/share/mercurial-server/refresh-auth
mkdir project
cd project
hg init
touch spam
hg add spam
hg commit -m 'add spam' -u root
hg clone . ssh://hg@127.0.0.1/project

Error trace:

searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
remote: error: pretxnchangegroup.access hook raised an exception:
'derivedrepo:/var/lib/mercurial-server/repos/projec' object has no
attribute 'changectx'
remote: transaction abort!
remote: rollback completed
remote: ** unknown exception encountered, please report by visiting
remote: ** https://mercurial-scm.org/wiki/BugTracker
remote: ** Python 2.7.16 (default, Oct 10 2019, 22:02:15) [GCC 8.3.0]
remote: ** Mercurial Distributed SCM (version 4.8.2)
remote: ** Extensions loaded:
remote: Traceback (most recent call last):
remote:   File "/usr/share/mercurial-server/hg-ssh", line 91, in

remote: dispatch.dispatch(request(['-R', repo, 'serve', '--stdio']))
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 220, in
dispatch
remote: ret = _runcatch(req) or 0
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 363, in
_runcatch
remote: return _callcatch(ui, _runcatchfunc)
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 371, in
_callcatch
remote: return scmutil.callcatch(ui, func)
remote:   File "/usr/lib/python2.7/dist-packages/mercurial/scmutil.py",
line 166, in callcatch
remote: return func()
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 354, in
_runcatchfunc
remote: return _dispatch(req)
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 994, in
_dispatch
remote: cmdpats, cmdoptions)
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 737, in
runcommand
remote: ret = _runcommand(ui, options, cmd, d)
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 1003, in
_runcommand
remote: return cmdfunc()
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 991, in

remote: d = lambda: util.checksignature(func)(ui, *args,
**strcmdopt)
remote:   File "/usr/lib/python2.7/dist-packages/mercurial/util.py",
line 1646, in check
remote: return func(*args, **kwargs)
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/commands.py", line 5207, in
serve
remote: s.serve_forever()
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/wireprotoserver.py",

Bug#937013: marked as done (mercurial-server: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 10 Mar 2020 00:00:43 +
with message-id 
and subject line Bug#953483: Removed package(s) from unstable
has caused the Debian Bug report #937013,
regarding mercurial-server: 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.)


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

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.2-2.2+rm

Dear submitter,

as the package mercurial-server 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/953483

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

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

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

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

Bug#936520: marked as done (flashbake: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 23:58:07 +
with message-id 
and subject line Bug#953434: Removed package(s) from unstable
has caused the Debian Bug report #936520,
regarding flashbake: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:flashbake

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.27.1-0.1+rm

Dear submitter,

as the package flashbake 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/953434

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

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

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

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

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

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 23:59:10 +
with message-id 
and subject line Bug#953475: Removed package(s) from unstable
has caused the Debian Bug report #937943,
regarding python-netsyslog: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-netsyslog

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.1.0+dp2-1+rm

Dear submitter,

as the package python-netsyslog 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/953475

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

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

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

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

Bug#936830: marked as done (ldaptor: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 23:58:30 +
with message-id 
and subject line Bug#953436: Removed package(s) from unstable
has caused the Debian Bug report #936830,
regarding ldaptor: 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.)


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

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.0.43+debian1-7.2+rm

Dear submitter,

as the package ldaptor 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/953436

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

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

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

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

Bug#937058: marked as done (moap: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 23:57:46 +
with message-id 
and subject line Bug#953433: Removed package(s) from unstable
has caused the Debian Bug report #937058,
regarding moap: 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.)


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

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.2.7-2.2+rm

Dear submitter,

as the package moap 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/953433

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

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

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

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

Bug#937508: marked as done (pyptlib: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 23:50:27 +
with message-id 
and subject line Bug#953429: Removed package(s) from unstable
has caused the Debian Bug report #937508,
regarding pyptlib: 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.)


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

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.0.6-2+rm

Dear submitter,

as the package pyptlib 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/953429

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

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

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

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

Bug#937277: NMU on the way

[Scott Kitterman]

On Fri, 6 Mar 2020 19:33:19 +0200 Adrian Bunk  wrote:
> On Fri, Aug 30, 2019 at 03:00:10PM +, Debian Bug Tracking System wrote:
> >...
> > Architecture: source all
> >...
> >* Switch to python3 (thanks to Sandro Tosi for the patch)
> >  (Closes: > #935476, #937277)
> 
> >...
> 
> Thanks for fixing this in unstable.
> 
> Could you make a source-only upload to allow testing migration?

This is now blocking psycopg2 migration to Testing, so I'm going to upload an 
NMU to get it to migrate.  Diff attached.

Scott Kdiff -Nru pg-activity-1.5.0/debian/changelog pg-activity-1.5.0/debian/changelog
--- pg-activity-1.5.0/debian/changelog	2019-08-29 04:04:54.0 -0400
+++ pg-activity-1.5.0/debian/changelog	2020-03-09 19:39:30.0 -0400
@@ -1,3 +1,10 @@
+pg-activity (1.5.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * No change source upload to allow fixes for #937277 to make it to Testing
+
+ -- Scott Kitterman   Mon, 09 Mar 2020 19:39:30 -0400
+
 pg-activity (1.5.0-1) unstable; urgency=medium
 
   * New upstream release


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

Bug#953398: marked as done (gnome-builder: uninstallable in unstable: gir1.2-glib-2.0 (>= 2.61.2) unavailable)

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 23:04:18 +
with message-id 
and subject line Bug#953398: fixed in gnome-builder 3.36.0-2
has caused the Debian Bug report #953398,
regarding gnome-builder: uninstallable in unstable: gir1.2-glib-2.0 (>= 2.61.2) 
unavailable
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.)


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

gnome-builder_3.36.0-1 Depends on gir1.2-glib-2.0 (>= 2.61.2), but that
version isn't available.

gir1.2-glib-2.0 is built by src:gobject-introspection, which has a version
number that doesn't match GLib's. If what you mean is "gir1.2-glib-2.0
corresponding to at least libglib2.0-0 (>= 2.61.2)", I think that's
probably version 1.62.0 or later.

smcv
--- End Message ---
--- Begin Message ---
Source: gnome-builder
Source-Version: 3.36.0-2
Done: Laurent Bigonville 

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated gnome-builder 
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, 09 Mar 2020 23:47:48 +0100
Source: gnome-builder
Architecture: source
Version: 3.36.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Laurent Bigonville 
Closes: 953398
Changes:
 gnome-builder (3.36.0-2) unstable; urgency=medium
 .
   * debian/control.in: Fix the version of gir1.2-glib-2.0 to make it
 installable again, oups (Closes: #953398)
Checksums-Sha1:
 7b7f905d32e94a72ef58a5a1f0718e72a26d9773 2783 gnome-builder_3.36.0-2.dsc
 8cd79f75971d66684b42b5a47798a4ff6106eeb2 17908 
gnome-builder_3.36.0-2.debian.tar.xz
 1ceb6f3b1fcc552fa73a3d9afe878cfcfaed6b48 13787 
gnome-builder_3.36.0-2_source.buildinfo
Checksums-Sha256:
 fc142729b0bad47b5f98a4d2da98b167e306809aaedeb812ec2f27e2ee4ba676 2783 
gnome-builder_3.36.0-2.dsc
 70d37b18a4f3be13051a47f70caceec06136eea24294ae064e1ed142e147fb95 17908 
gnome-builder_3.36.0-2.debian.tar.xz
 28051e80db0756f6c5976787137d5d16b0c1f8bffdbd6c1d090d918286360b1d 13787 
gnome-builder_3.36.0-2_source.buildinfo
Files:
 103d396760d735da9518e7a6602973cc 2783 editors optional 
gnome-builder_3.36.0-2.dsc
 e9419567d18f11a1d06c051ae0b191d2 17908 editors optional 
gnome-builder_3.36.0-2.debian.tar.xz
 f4aefe7cca62764a73de6265d6caf890 13787 editors optional 
gnome-builder_3.36.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAl5myFYRHGJpZ29uQGRl
Ymlhbi5vcmcACgkQH8WJHrqwQ9WtuggAijuEjFkKd7Oem0f0VU9MhcEUPfvdxqEs
zLnOOXvuNcmj6zeLRfZXFppT7LEZ8B9sOtYuGEky3R8kpA5zqSdIPT1hKdnTEBhR
VCW/PhYcC3RoaK0coywh7qKy9oxeTFOKkU8fMuo5WKU1cB21tGJYyJaRAoIqFK2C
VsogKpVEZzvM56rpo6wkdvhMd19eubSR0Mt/2at0tDcVACrE5pDdbbLeVLe6whKO
cbgLC3OHSi1rybLL8vNpexmVfKHmFkfnh9us6yl2UCmf7lLaJ2LIAXGCwjUoxvnh
z2ptaF5rLXuFGncRduYpyumHGl6diH32Vlpl5emBojt0GwAmO3dXtQ==
=C+EZ
-END PGP SIGNATURE End Message ---

Bug#953398: marked as pending in gnome-builder

[Laurent Bigonville]

Control: tag -1 pending

Hello,

Bug #953398 in gnome-builder 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/gnome-team/gnome-builder/-/commit/e159936a5ff37e3bde1ebceaf1406090bbc02b79


debian/control.in: Fix the version of gir1.2-glib-2.0 to make it installable 
again, oups (Closes: #953398)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/953398

Processed: Bug#953398 marked as pending in gnome-builder

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #953398 [gnome-builder] gnome-builder: uninstallable in unstable: 
gir1.2-glib-2.0 (>= 2.61.2) unavailable
Added tag(s) pending.

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

Bug#953486: xow: binaries for non-free not auto-built

[Samuel Henrique]

Hello Ivo,

> If the binaries can be auto-built, the package should be whitelisted, as
> described in
> https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd

This has been done already, I sent the email asking for the
whitelisting yesterday
and at this point I'm just waiting for it.

Regards,

--
Samuel Henrique 

Bug#953489: php-horde-text-filter-jsmin: binaries for non-free not auto-built

[Ivo De Decker]

package: src:php-horde-text-filter-jsmin
version: 1.0.2-6
severity: serious
tags: ftbfs

Hi,

The latest upload of php-horde-text-filter-jsmin to unstable has no binaries.
The buildds are not building it, because it is in non-free.

If the binaries can be auto-built, the package should be whitelisted, as
described in
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd

If not, a binary upload must be done (note that binary maintainer uploads for
sources in contrib and non-free are allowed to migrate to testing).

Cheers,

Ivo

Bug#953487: runescape: binaries for non-free not auto-built

[Ivo De Decker]

package: src:runescape
version: 0.6-2
severity: serious
tags: ftbfs

Hi,

The latest upload of runescape to unstable has no binaries.
The buildds are not building it, because it is in non-free.

If the binaries can be auto-built, the package should be whitelisted, as
described in
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd

If not, a binary upload must be done (note that binary maintainer uploads for
sources in contrib and non-free are allowed to migrate to testing).

Cheers,

Ivo

Bug#953488: powder: binaries for non-free not auto-built

[Ivo De Decker]

package: src:powder
version: 118+dfsg1-3
severity: serious
tags: ftbfs

Hi,

The latest upload of powder to unstable has no binaries.
The buildds are not building it, because it is in non-free.

If the binaries can be auto-built, the package should be whitelisted, as
described in
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd

If not, a binary upload must be done (note that binary maintainer uploads for
sources in contrib and non-free are allowed to migrate to testing).

Cheers,

Ivo

Bug#953486: xow: binaries for non-free not auto-built

[Ivo De Decker]

package: src:xow
version: 0.3-3
severity: serious
tags: ftbfs

Hi,

The latest upload of xow to unstable has no binaries.
The buildds are not building it, because it is in non-free.

If the binaries can be auto-built, the package should be whitelisted, as
described in
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd

If not, a binary upload must be done (note that binary maintainer uploads for
sources in contrib and non-free are allowed to migrate to testing).

Cheers,

Ivo

Bug#953485: amiwm: binaries for non-free not auto-built

[Ivo De Decker]

package: src:amiwm
version: 0.21pl2-2
severity: serious
tags: ftbfs

Hi,

The latest upload of amiwm to unstable has no binaries.
The buildds are not building it, because it is in non-free.

If the binaries can be auto-built, the package should be whitelisted, as
described in
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd

If not, a binary upload must be done (note that binary maintainer uploads for
sources in contrib and non-free are allowed to migrate to testing).

Cheers,

Ivo

Bug#938567: starpy: diff for NMU version 1.0.1.0.git.20151124-2.1

[Moritz Mühlenhoff]

Dear maintainer,
attached the debdiff for my NMU for starpy (versioned as 
1.0.1.0.git.20151124-2.1)

Cheers,
Moritz

diff -Nru starpy-1.0.1.0.git.20151124/debian/changelog starpy-1.0.1.0.git.20151124/debian/changelog
--- starpy-1.0.1.0.git.20151124/debian/changelog	2017-08-01 22:59:50.0 +0200
+++ starpy-1.0.1.0.git.20151124/debian/changelog	2020-03-09 22:40:05.0 +0100
@@ -1,3 +1,10 @@
+starpy (1.0.1.0.git.20151124-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Cherrypick upstream commit to fix Python 3 compat (Closes: #938567)
+
+ -- Moritz Muehlenhoff   Mon, 09 Mar 2020 22:40:05 +0100
+
 starpy (1.0.1.0.git.20151124-2) unstable; urgency=medium
 
   * Depend on python-setuptools (Closes: #867672)
diff -Nru starpy-1.0.1.0.git.20151124/debian/control starpy-1.0.1.0.git.20151124/debian/control
--- starpy-1.0.1.0.git.20151124/debian/control	2017-08-01 22:45:45.0 +0200
+++ starpy-1.0.1.0.git.20151124/debian/control	2020-03-09 22:40:05.0 +0100
@@ -5,19 +5,19 @@
 # Add Paul Belanger as an uploaded, for now.
 Uploaders: Tzafrir Cohen , Paul Belanger 
 Build-Depends: debhelper (>= 10),
- python,
+ python3,
  dh-python,
- python-setuptools,
- python-twisted-core
+ python3-setuptools,
+ python3-twisted
 X-Python-Version: >= 2.4
 Standards-Version: 3.9.8
 Homepage: https://github.com/asterisk/starpy
 Vcs-Git: https://anonscm.debian.org/cgit/pkg-voip/starpy.git
 Vcs-Browser: https://anonscm.debian.org/cgit/pkg-voip/starpy.git
 
-Package: python-starpy
+Package: python3-starpy
 Architecture: all
-Depends: python-twisted-core, ${misc:Depends}, ${python:Depends}
+Depends: python3-twisted, ${misc:Depends}, ${python3:Depends}
 Recommends: asterisk
 Description: Asterisk (AMI) protocols for Twisted Python
  A Twisted Python protocol that provides access to the Asterisk PBX's Manager
diff -Nru starpy-1.0.1.0.git.20151124/debian/patches/add-support-for-python-3.patch starpy-1.0.1.0.git.20151124/debian/patches/add-support-for-python-3.patch
--- starpy-1.0.1.0.git.20151124/debian/patches/add-support-for-python-3.patch	1970-01-01 01:00:00.0 +0100
+++ starpy-1.0.1.0.git.20151124/debian/patches/add-support-for-python-3.patch	2020-03-09 22:38:37.0 +0100
@@ -0,0 +1,267 @@
+From 7e43a8bafddd9e746dadf3ed4ec28fc79542dc25 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Rodrigo=20Ram=C3=ADrez=20Norambuena?= 
+Date: Sat, 1 Oct 2016 14:24:14 -0300
+Subject: [PATCH] Add support code for Python 3
+
+Change-Id: I9ccd5a15be6e4129a5e0ce0bf1a5a4ff26998bac
+---
+ starpy/fastagi.py | 19 ++-
+ starpy/manager.py | 44 +---
+ tox.ini   |  2 +-
+ 3 files changed, 40 insertions(+), 25 deletions(-)
+
+diff --git a/starpy/fastagi.py b/starpy/fastagi.py
+index 7a9b32e..7e26284 100644
+--- a/starpy/fastagi.py
 b/starpy/fastagi.py
+@@ -127,7 +127,7 @@ def lineReceived(self, line):
+ try:
+ key, value = line.split(':', 1)
+ value = value[1:].rstrip('\n').rstrip('\r')
+-except ValueError, err:
++except ValueError as err:
+ log.error("""Invalid variable line: %r""", line)
+ else:
+ self.variables[key.lower()] = value
+@@ -135,7 +135,7 @@ def lineReceived(self, line):
+ else:
+ try:
+ df = self.pendingMessages.pop(0)
+-except IndexError, err:
++except IndexError as err:
+ log.warn("Line received without pending deferred: %r", line)
+ else:
+ if line.startswith('200'):
+@@ -148,7 +148,7 @@ def lineReceived(self, line):
+ try:
+ errCode, line = line.split(' ', 1)
+ errCode = int(errCode)
+-except ValueError, err:
++except ValueError as err:
+ errCode = 500
+ df.errback(error.AGICommandFailure(errCode, line))
+ 
+@@ -166,7 +166,7 @@ def checkFailure(self, result, failure='-1'):
+ # result code may have trailing information...
+ try:
+ resultInt, line = result.split(' ', 1)
+-except ValueError, err:
++except ValueError as err:
+ resultInt = result
+ if resultInt.strip() == failure:
+ raise error.AGICommandFailure(FAILURE_CODE, result)
+@@ -176,7 +176,7 @@ def resultAsInt(self, result):
+ """(Internal) Convert result to an integer value"""
+ try:
+ return int(result.strip())
+-except ValueError, err:
++except ValueError as err:
+ raise error.AGICommandFailure(FAILURE_CODE, result)
+ 
+ def secondResultItem(self, result):
+@@ -188,7 +188,7 @@ def resultPlusTimeoutFlag(self, resultLine):
+ try:
+ digits, timeout = resultLine.split(' ', 1)
+ return digits.strip(), True
+-

Bug#952416: marked as done (glom: Use python3-embed pkg-config instead of python3)

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 21:37:01 +
with message-id 
and subject line Bug#952416: fixed in glom 1.30.4-6
has caused the Debian Bug report #952416,
regarding glom: Use python3-embed pkg-config instead of python3
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.)


-- 
952416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952416
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glom
Version: 1.30.4-5
Severity: serious
Tags: patch experimental
Justification: ftbfs
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

As of python3.8, the python3.pc file does not provide the library flags
necessary to link programs against an embedded python interpreter.  Instead,
packages need to use python3-embed, as in the attached patch.

Since python3-defaults is switching to python3.8 imminently (it's already in
experimental), I'm marking this as a serious bug.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru glom-1.30.4/debian/rules glom-1.30.4/debian/rules
--- glom-1.30.4/debian/rules2020-02-10 04:11:08.0 -0800
+++ glom-1.30.4/debian/rules2020-02-23 18:12:27.0 -0800
@@ -3,8 +3,8 @@
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,-O1 -Wl,--as-needed
 
-PYTHON_CPPFLAGS_PKGCONFIG := $(shell pkg-config --cflags python3)
-PYTHON_LIB_PKGCONFIG := $(shell pkg-config --libs python3)
+PYTHON_CPPFLAGS_PKGCONFIG := $(shell pkg-config --cflags python3-embed)
+PYTHON_LIB_PKGCONFIG := $(shell pkg-config --libs python3-embed)
 
 %:
dh $@ --with gnome,python3
--- End Message ---
--- Begin Message ---
Source: glom
Source-Version: 1.30.4-6
Done: Laurent Bigonville 

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated glom 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, 09 Mar 2020 22:12:58 +0100
Source: glom
Architecture: source
Version: 1.30.4-6
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Laurent Bigonville 
Closes: 952416
Changes:
 glom (1.30.4-6) unstable; urgency=medium
 .
   * debian/rules: Fix FTBFS with python3.8 (Closes: #952416)
   * debian/control.in: Bump Standards-Version to 4.5.0 (no further changes)
   * debian/glom.install: Install the appdata file
Checksums-Sha1:
 d6ac91efc7348ea3fee2a974e363dfed54f48961 2507 glom_1.30.4-6.dsc
 c6332f144e84497ae7566f60c2992bf3e8a98517 7132 glom_1.30.4-6.debian.tar.xz
 2ba60de1ade078917e1274076cc5bfa5142ec7bd 6708 glom_1.30.4-6_source.buildinfo
Checksums-Sha256:
 f019c80739b616b2762dedf3dc0c3af2095dee4e2f9b3ebe8c4bb1b490439442 2507 
glom_1.30.4-6.dsc
 1ac556298a227323406f3b10d84bf30aa3fe86f7b2902eec0ab7cc5316989e2e 7132 
glom_1.30.4-6.debian.tar.xz
 8c752f554d4bb586bbc16147bbf8adbc6a56227e5b203c70dc75375b56fc1352 6708 
glom_1.30.4-6_source.buildinfo
Files:
 527ca368b59c53321a5f646acc4a1454 2507 gnome optional glom_1.30.4-6.dsc
 2696d1ed69dce0e299508c67ba9c697e 7132 gnome optional 
glom_1.30.4-6.debian.tar.xz
 88af0965b97552805f7f99ff5e4bd261 6708 gnome optional 
glom_1.30.4-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAl5msYwRHGJpZ29uQGRl
Ymlhbi5vcmcACgkQH8WJHrqwQ9WsWQf+KGn8v1bcjBtw0+XOhrYavo6fffYkPkD2
odicDi/WwEmON7mcgQqcrjDDujgh0yRI667Ol8PDxfkmHgb+1oMHnrux/OvmuMRd
P/q3ECY7yG98yT1B9NhPgJw8sfFw10iwMhKS1+wTwU2UCyP+jGvLnG2MYqpBnVyL
rWYGF8OH22z0yZfOUZ+Mb4r/lxpoLivGRwPsKri+cMTxGfyN29pWjANZYQJAkoNm
ENq+Ie9YO5eNSXdMXYv00baCLeegiNgFOmj7/GVF0mXV5GBNoXb60MOBV9pJN1UV
AaO32xYa0hsUm+8jc59WUx3tqxV1cH+7JiiOl1fcl14aUTPHJpX64Q==
=1Gjj
-END PGP SIGNATURE End Message ---

Bug#938736: txwinrm: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

On Mon, Mar 09, 2020 at 09:02:29PM +, Christopher Hoskin wrote:
> Dear Moritz,
> 
> Yes - that seems sensible. There's no sign of an upstream Python 3 version.

Thanks, I've just filed a removal bug.

Cheers,
Moritz

Bug#953481: dmaths: Sources are no more available from upstream

[Pierre Gruet]

Source: dmaths
Severity: serious
Justification: Policy 2.3

Hello,

While visiting the upstream website [1], I saw a financial contribution has to 
be paid in order to be able to download dmaths. This violates 2.3 in the Debian 
policy.
No link for downloading the source can be found on the website.
I tried to reach upstream several weeks ago to confirm, but got no answer.

For those reasons, I think the package should be removed from Debian.

Best,
Pierre

[1] http://www.dmaths.org

Bug#952416: marked as pending in glom

[Laurent Bigonville]

Control: tag -1 pending

Hello,

Bug #952416 in glom 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/gnome-team/glom/-/commit/d4f05832f2cfd8f89685d559378272a872b06a9b


debian/rules: Fix FTBFS with python3.8 (Closes: #952416)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952416

Processed: Bug#952416 marked as pending in glom

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952416 [glom] glom: Use python3-embed pkg-config instead of python3
Added tag(s) pending.

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

Processed: Re: Bug#950177: source-highlight: FTBFS: make test fails

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #950177 [src:source-highlight] "make check" fails non-deterministically on 
arm64
Severity set to 'serious' from 'normal'
> tags -1 + patch
Bug #950177 [src:source-highlight] "make check" fails non-deterministically on 
arm64
Added tag(s) patch.

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

Bug#875243: marked as done ([yagf] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 21:04:48 +
with message-id 
and subject line Bug#875243: fixed in yagf 0.9.5+repack1-1
has caused the Debian Bug report #875243,
regarding [yagf] 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.)


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


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

[announced] 


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

[OpenSSL 1.1 support] 

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

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

= Porting =

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

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

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

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

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

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: yagf
Source-Version: 0.9.5+repack1-1
Done: Boris Pek 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 09 Mar 2020 23:39:56 +0300
Source: yagf
Architecture: source
Version: 0.9.5+repack1-1
Distribution: unstable
Urgency: medium
Maintainer: Boris Pek 
Changed-By: Boris Pek 
Closes: 746380 791400 859862 875243
Changes:
 yagf (0.9.5+repack1-1) unstable; urgency=medium
 .
   [ Jelmer Vernooij ]
   * Use secure URI in Vcs control header.
   * Use secure copyright file specification URI.
 .
   [ Boris Pek ]
   * New upstream release. (Closes: #791400)
   * Upstream tarball is repacked due to usage of incorrect end of lines.
   * Update debian/control:
 - bump Standards-Version to 4.5.0 (was 3.9.5)
 - replace build dependency from debhelper (>= 9) to debhelper-compat (= 12)
 - replace build dependency from libqt4-dev to qtbase5-dev, qttools5-dev and
   qttools5-dev-tools
 - add "Rules-Requires-Root: no"
 - update Homepage field
   * Update debian/rules:
 - delete --parallel option from dh
 - delete get-orig-source section and all related variables
 - enable all hardening flags
 - add option -Wl,--as-needed to LDFLAGS
 - add override_dh_installdocs target:
   remove deprecated file YAGF.appdata.xml from /usr/share/appdata
   * Update patch 01_fix-library-path-on-amd64-systems.
   * Add new patches:
 - 02_update-desktop-file.patch
 - 03_disable-cropping-of-loaded-images.patch:
   workaround for fixing of segmentation fault due to incorrect usage of
   smart

Bug#938736: txwinrm: Python2 removal in sid/bullseye

[Christopher Hoskin]

Dear Moritz,

Yes - that seems sensible. There's no sign of an upstream Python 3 version.

Thanks.

Christopher

On Mon, 9 Mar 2020 at 18:35, Moritz Mühlenhoff  wrote:
>
> On Fri, Aug 30, 2019 at 07:57:05AM +, Matthias Klose wrote:
> > Package: src:txwinrm
> > Version: 1.3.3-1
> > Severity: normal
> > Tags: sid bullseye
> > User: debian-pyt...@lists.debian.org
> > Usertags: py2removal
> >
> > Python2 becomes end-of-live upstream, and Debian aims to remove
> > Python2 from the distribution, as discussed in
> > https://lists.debian.org/debian-python/2019/07/msg00080.html
> >
> > Your package either build-depends, depends on Python2, or uses Python2
> > in the autopkg tests.  Please stop using Python2, and fix this issue
> > by one of the following actions.
>
> Hi Christopher,
> there was no followup from upstream on 
> https://github.com/zenoss/txwinrm/issues/191
> for > five months, shall we remove txwinrm?
>
> Cheers,
> Moritz

Bug#952126: emacs-bind-map: FTBFS caused by elpa-undo-tree 0.7.1

[Nicholas D Steeves]

Hi Lev,

Lev Lamberov  writes:

> Hi Nicholas and David,
>
> Пн 24 фев 2020 @ 12:27 Nicholas D Steeves :
>
>> Lev Lamberov  writes:
>>
>>> Hmmm, looks like the bug is caused by undo-tree, since when
>>> elpa-undo-tree 0.6.4-3 is installed tests are passed correctly.
>>> Moreover, when new upstream version of undo-tree is used (0.7.4, not
>>> currently in Debian) tests also are passed correctly.
>>
>> Lev, thank you for working to find, and finding the cause!  Sorry, I
>> share the blame for this regression because I sponsored the upload of
>> 0.7.1.  How urgently would you like a fix?  I'd like to give David some
>> time to prepare the new undo-tree release, but can prepare it myself if
>> too much time passes.  BTW, are undo-trees tests flaky or could you
>> enable autopkgtests for it at this time?
>
> In fact, this was not that urgent. Anyway, thank you both for your work
> and kindness! There's no one to blame simply because it is up to
> impossible to check a package against all possible regressions
> (especially given that dependency chain becomes way too long pretty
> quickly).
>

Thank you Lev, that's kind :-)  On the upside, autopkgtests give us an
edge over MELPA Stable!  Sorry for not noticing emacs-bind-map already
had them enabled.  IIRC the dep chain for this package is now covered,
so our early-warning system should be functional.  'wish we had
untruncated backtraces...

> Thanks again! I'm closing this bug (it also motivated me to update
> packaging of emacs-bind-map, which should have been done at some point).
>

Wonderful!  By the way, whenever I see a lot of packaging updates on our
mailing list it also motivates me to work on my packages :-D


Take care,
Nicholas


signature.asc
Description: PGP signature

Bug#925202: marked as done (Keep calypso out of testing/buster)

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 20:40:11 +
with message-id 
and subject line Bug#925202: fixed in calypso 2.0-2
has caused the Debian Bug report #925202,
regarding Keep calypso out of testing/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.)


-- 
925202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925202
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: calypso
Version: 1.5-5
Severity: grave

Calypso has not seen much attention recently so it's likely better to
not ship it in a stable release. It wasn't in stretch either so this
will not affect current users.
Cheers,
 -- Guido

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

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

Versions of packages calypso depends on:
ii  git  1:2.20.1-2
ii  python   2.7.15-4
ii  python-daemon2.2.3-1
ii  python-lockfile  1:0.12.2-2
ii  python-vobject   0.9.6.1-0.1

calypso recommends no packages.

calypso suggests no packages.
--- End Message ---
--- Begin Message ---
Source: calypso
Source-Version: 2.0-2
Done: Keith Packard 

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

Debian distribution maintenance software
pp.
Keith Packard  (supplier of updated calypso 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, 09 Mar 2020 12:44:19 -0700
Source: calypso
Architecture: source
Version: 2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Keith Packard 
Changed-By: Keith Packard 
Closes: 925202
Changes:
 calypso (2.0-2) unstable; urgency=medium
 .
   * New source upload to allow migration to testing
   * Use current debian conventions
   * New upstream version (Closes: #925202)
Checksums-Sha1:
 46be46261350b995b323399dcfc73fe5e5db7771 1792 calypso_2.0-2.dsc
 ead2891a02c0368f1b4baca309f2e35bacf92b18 2564 calypso_2.0-2.debian.tar.xz
 4da24807632d8f49396e605969dc418722a6c689 7185 calypso_2.0-2_amd64.buildinfo
Checksums-Sha256:
 f70835984f03e9819919d9e9cba61cadca30ab1a20d78a46ece423cc5dc4ef84 1792 
calypso_2.0-2.dsc
 64daa8b86e8ce3c7a055195b6c241fbe5806826b43e708ecb51f8a009b46b096 2564 
calypso_2.0-2.debian.tar.xz
 988c8e7d0fb94fbf52f9a53a1a8f92462e9a613d4a1f0c051e71bd105debe823 7185 
calypso_2.0-2_amd64.buildinfo
Files:
 5ea6850f1bb4bdfa1fed09d533fe5b56 1792 web optional calypso_2.0-2.dsc
 763c5dee266d7aa7d8ac8dcea2f91747 2564 web optional calypso_2.0-2.debian.tar.xz
 97332864eea132dcd4c0aa8101347705 7185 web optional 
calypso_2.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEw4O3eCVWE9/bQJ2R2yIaaQAAABEFAl5mno0ACgkQ2yIaaQAA
ABFrNQ//ZUjQA0XKGuDWHbgBmozzrw7eosq2fvj0cSkF5aOVlb70YQhU6lLCdVN0
RJcoKy/gEFIkXrN/XjvLOXW0HMHPgL9ywMYf4ZipwfpJIzt2SVnVmNr3Dfb9MctD
rP4qPKkH1w7Z+KSdT9cnorVj9qhXeqzP2dUltvGyDRIkdJr8fQsoWb1JzxuGAd1r
kTsM0mCTdI9PHGDgfF1mjyrkj3XCNP3qr1NeUScwq0Sd21l40OTjk6hED5aKHiIK
JW5HXwjh6rTWXeAMlTeSZJR9i8CKo8UgP3cbiYIJSuzLFFNx8pEH/aiBSmmm2qr5
MPldlhfisQh8U41wiU9qIcS+xhqX2XssllDx6O3GaqUAU83zVcI1e/ZB3448ftxl
24MEkg/C4G6Ej+J1E1rXuNk8moTvz6UqNPD8cSgguUscj8437iRonNKnesXvgfrc
YgXuQATBJQnmUXe4FJt5+kVGuAnF/4VY+epBu6hA0Ut0QqM3ILf5gm9lkweRognk
LqN6w+siJ1DUc6vDdkEULVjvMzbWpT8Imc7rNORBr5o4BH2ypD3wLR7ZnfWlao4H
+cLzABMLX02yX8WM23jX7IOS4eO7X98HiQHEYQMLQO1Mmfx5WHc508X+HD+uoDbQ
x2gfRBIFvLTcnO55XO9WikC0XdraFPvHu3Rk644rBCyM9ut0noM=
=Gag6
-END PGP SIGNATURE End Message ---

Bug#953348: marked as done (libpeas: FTBFS with Python 3.8)

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 20:42:10 +
with message-id 
and subject line Bug#953348: fixed in libpeas 1.26.0-1
has caused the Debian Bug report #953348,
regarding libpeas: FTBFS 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.)


-- 
953348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpeas
Version: 1.22.0-5
Severity: serious
Tags: ftbfs

Hi Maintainer

libpeas FTBFS when rebuilt with Python 3.8 [1].
There are several undefined references, similar to the following:

/usr/bin/ld: .libs/peas-plugin-loader-python.o: in function
`peas_plugin_loader_python_garbage_collect':
./loaders/python3/../../loaders/python/peas-plugin-loader-python.c:204:
undefined reference to `PyGILState_Ensure'
/usr/bin/ld: .libs/peas-plugin-loader-python.o: in function
`find_python_extension_type':
./loaders/python3/../../loaders/python/peas-plugin-loader-python.c:72:
undefined reference to `PyType_Type'
/usr/bin/ld: .libs/peas-plugin-loader-python.o: in function `_Py_DECREF':
/usr/include/python3.8/object.h:478: undefined reference to `_Py_Dealloc'

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=libpeas
--- End Message ---
--- Begin Message ---
Source: libpeas
Source-Version: 1.26.0-1
Done: Laurent Bigonville 

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated libpeas 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, 09 Mar 2020 21:16:07 +0100
Source: libpeas
Architecture: source
Version: 1.26.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Laurent Bigonville 
Closes: 936900 953348
Changes:
 libpeas (1.26.0-1) unstable; urgency=medium
 .
   [ Andreas Henriksson ]
   * Drop libpeas-1.0-python2loader (Closes: #936900)
 .
   [ Debian Janitor ]
   * Bump debhelper from old 11 to 12.
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields:
 - Bug-Database, Bug-Submit, Name, Repository, Repository-Browse.
 .
   [ Andreas Henriksson ]
   * Build-dep on dh-sequence-gir and dh-sequence-gnome
 .
   [ Laurent Bigonville ]
   * New upstream release (Closes: #953348)
   * debian/control.in: Add libglib2.0-doc, libgirepository1.0-doc and
 libgtk-3-doc so the links between documentation are properly resolved
   * debian/libpeas-1.0-0.symbols: Add newly exported symbols
   * debian/control.in: Bump Standards-Version to 4.5.0 (no further changes)
   * debian/contron.in: Mark libpeas-doc with Build-profiles: 
Checksums-Sha1:
 977caf0cb17d6ec5bfbcfb9828db0afc5cf236cf 2623 libpeas_1.26.0-1.dsc
 076daf5334f344a81b4c6e98751cbb61195eabc3 191708 libpeas_1.26.0.orig.tar.xz
 574c5e7f0bf246af2f8a8ebc71f6d6761af8933c 10328 libpeas_1.26.0-1.debian.tar.xz
 1e86aec196829cd7d5ac298867be8cc22feb5c6e 14782 
libpeas_1.26.0-1_source.buildinfo
Checksums-Sha256:
 f5aed9fcd8caddecb5f5a8244a1067727c9b248f77eab066e0ab1b8995bb8b06 2623 
libpeas_1.26.0-1.dsc
 a976d77e20496479a8e955e6a38fb0e5c5de89cf64d9f44e75c2213ee14f7376 191708 
libpeas_1.26.0.orig.tar.xz
 3311b4cbd2449352cf89be2e9680d23eb0ff171309bfc56fdbaad0f1591c5aaa 10328 
libpeas_1.26.0-1.debian.tar.xz
 f9b5c16e4cc62cc8138e8f50ca9c9fb1849377bf8c0047ee657aac816dadb8a4 14782 
libpeas_1.26.0-1_source.buildinfo
Files:
 94967f6c92494b72abcca112ca606bb9 2623 libs optional libpeas_1.26.0-1.dsc
 f7723bf8433b7984121157e1e9a629b5 191708 libs optional 
libpeas_1.26.0.orig.tar.xz
 b77bfa3569d828af3d937c241ed2592e 10328 libs optional 
libpeas_1.26.0-1.debian.tar.xz
 6d5b82bdfe08fc40581978d1293c6541 14782 libs optional 
libpeas_1.26.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAl5mpEkRHGJpZ29uQGRl
Ymlhbi5vcmcACgkQH8WJHrqwQ9XwFQf+JRpmDE33jOhPqTE5RlyuI0l9yiklfvpI
3R6FWyynYqOSESOb5ZrTnY+Ea83FZQxRSPYVbet0b3peVHwOxHsOKiNDNgVwM385
mJBsEMOBuHaRm4ggNHUex4MVVRmvicOlu6sEtyB1T2j/QZsMn0XecmwMEM7O7Sqc
tu4tPOcYu+BPd

Bug#874901: [GLE-devel] Probable fix for qgle seg faults with latest ghostscript versions

[Christian T. Steigies]

On Mon, Mar 02, 2020 at 08:18:21PM +0100, Moritz M?hlenhoff wrote:
> 
> I've now filed a removal bug for gle-graphics. It can be re-introduced when
> a stable Qt5 port is available, there's plenty of time until the next freeze.

Thanks, Moritz. I uploaded a version today which should fix everything, it
has to go trough NEW, so it will take a little longer.

The Qt5 part was already working fine, only the part loading the
ghostscript library had issues. The library is located in
/usr/lib/, for example /usr/lib/x86_64-linux-gnu/ on amd64.
The triarch part can be determined with:
ARCH = $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)

I tried to pass this directory with a define to the cpp code, where it would
be used to load the library. The define worked fine (some issues with
quotes) according to the logs, but during compilation this was changed to:
/usr/lib/x86_64-1-gnu (linux replace by 1), which I could not figure out how
to fix or even what happened there. 

So instead of using the define, I created a new header file during the
build, where a const with the correct path was defined.  The only change to
the upstream code is now to include this new header file and load the
library with the const as path.  That works fine (tested only on amd64, but
strace shows the correct path), and I expect it to work for all other arches
as well, as long as the dpkg-architecture call is correct.

This is the solution I have been looking for, even though it is debian
specific. But other distributions should be able to create the own fix based
on this. Now if I can get write access to the git repository on salsa, I
can push the new version there.

Christian

Bug#952105: marked as done (planetblupi: FTBFS: blupi.h:23:10: fatal error: SDL.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 19:50:59 +
with message-id 
and subject line Bug#952105: fixed in planetblupi 1.14.2-2
has caused the Debian Bug report #952105,
regarding planetblupi: FTBFS: blupi.h:23:10: fatal error: SDL.h: 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.)


-- 
952105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: planetblupi
Version: 1.14.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> /usr/bin/c++   -I/usr/include/SDL2 
> -I/<>/obj-x86_64-linux-gnu/include  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -std=c++11 
> -L/usr/lib   -std=gnu++11 -o CMakeFiles/planetblupi.dir/src/decblupi.cxx.o -c 
> /<>/src/decblupi.cxx
> In file included from /<>/src/action.h:23,
>  from /<>/src/action.cxx:24:
> /<>/src/blupi.h:23:10: fatal error: SDL.h: No such file or 
> directory
>23 | #include 
>   |  ^~~
> compilation terminated.
> make[4]: *** [CMakeFiles/planetblupi.dir/build.make:66: 
> CMakeFiles/planetblupi.dir/src/action.cxx.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/planetblupi_1.14.2-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: planetblupi
Source-Version: 1.14.2-2
Done: Didier Raboud 

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

Debian distribution maintenance software
pp.
Didier Raboud  (supplier of updated planetblupi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 09 Mar 2020 20:13:59 +0100
Source: planetblupi
Architecture: source
Version: 1.14.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Didier Raboud 
Closes: 952105
Changes:
 planetblupi (1.14.2-2) unstable; urgency=medium
 .
   [ Simon McVittie ]
   * d/p/Avoid-making-assumptions-about-location-of-SDL2-headers.patch:
 Don't assume that SDL2 headers are in /usr/include/SDL2
 (Closes: #952105)
 .
   [ Didier Raboud ]
   * lintian-brush: Set some upstream metadata fields
   * Bump Standards-Version to 4.5.0, cleanup versions
Checksums-Sha1:
 c0675606f056f06c2d6047f06fee6677f7401a72 2446 planetblupi_1.14.2-2.dsc
 1fe0a1f8f17e537fbdeba78b71454c0c326e14ef 5048 
planetblupi_1.14.2-2.debian.tar.xz
Checksums-Sha256:
 66ec867624a979c10efb23836bd07e8aaa1722de89f1784321d7547f63ffa45f 2446 
planetblupi_1.14.2-2.dsc
 b246fa415d435205afc20f68a2fa94466164ccf3c6963856c278a4a47a77bd48 5048 
planetblupi_1.14.2-2.debian.tar.xz
Files:
 4ba3fd9006e04cf74821824db5027ebb 2446 games optional planetblupi_1.14.2-2.dsc
 3b4e5bf128d3d89d5d9a397356783484 5048 games optional 
planetblupi_1.14.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJ3k7rA0YCplkx4gZqcb6xg1jAWkFAl5mmNsACgkQqcb6xg1j
AWlX0xAAgWWsk6w9Wsem/ptTUEWBJdknahO06M2utk35wLAFExXHopqOT858KDZf
KCk1I2mnEd2680mn1QxajNUaTy2DIKGohIvI8o7oDYEbA1eMdSpqiobPqhiENSg+
DcRvSJdR8Zye8jR9bpGih4QoBq3R+sYhWc+C7qvnd1pSFZcqsgsQD/EgjXB1nhiu
FWOanl2eo4OYxA9921ryMaJcQVgQZGZVjkXRzNqx5Om3s4Z0WIydrh/Mn5tmM7Rx
ElQPh3nsgHGBUXpBxpflF/cl4/ZCRzQFZXoc51uxUtHRfTppe8A/TNHrNJHzdAV7
+J3amLYPPRPAzuLI7TEPCCVaZJRsynn6jV99fqo5OEzMc6tbasiQe8tw7s/mOtLg
8ZFrwygGVadjp9ro7g/4t+kElg17QXrbQvOw/2r2CeShE4f2y6J6eriLlFNi4IWU
U/2dk+zPqNUtxu4WDgZytzckg0xmyRdJQPoPleaNvPdbLAlqJvP6fLzfuyCT8PLH
REOm0OHMYMTHdYy9zbt15YYI6wZE8Lbo5KfEQr8IlJZ+XXuW/sio9MFw0iKrPj2B
r1/4S2AwLnKOq7kF+gG4rR6n

Bug#952637: marked as done (ruby-asciidoctor-pdf: FTBFS: Could not find 'concurrent-ruby' (~> 1.0.5) - did find: [concurrent-ruby-1.1.6])

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 12:41:41 -0700
with message-id <874kuxz56y@keithp.org>
and subject line Close bug 952637
has caused the Debian Bug report #952637,
regarding ruby-asciidoctor-pdf: FTBFS: Could not find 'concurrent-ruby' (~> 
1.0.5) - did find: [concurrent-ruby-1.1.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.)


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

Package: ruby-asciidoctor-pdf
Version: 1.5.0~alpha.17.dev-6.1
Severity: serious
Control: tags -1 patch

With recent upload to ruby-concurrent to 1.1.6, ruby-asciidoctor-pdf 
started FTBFS because the dependency declared in gemspec is too strict.


┌──┐
│ Checking Rubygems dependency resolution on ruby2.5  
│

└──┘

GEM_PATH=/<>/debian/ruby-asciidoctor-pdf/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/ruby/gems/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0 
ruby2.5 -e gem\ \"asciidoctor-pdf\"
/usr/lib/ruby/2.5.0/rubygems/dependency.rb:312:in `to_specs': Could not 
find 'concurrent-ruby' (~> 1.0.5) - did find: [concurrent-ruby-1.1.6] 
(Gem::MissingSpecVersionError)


It can be fixed easily with  a patch,

commit 0a0cd710110b8445fc5ea5abeb809c97b40b0518
Author: Pirate Praveen 
Date:   Wed Feb 26 22:58:15 2020 +0530

   Relax dependencies of stable libraries

diff --git a/asciidoctor-pdf.gemspec b/asciidoctor-pdf.gemspec
index b66e4ba..8ec4524 100644
--- a/asciidoctor-pdf.gemspec
+++ b/asciidoctor-pdf.gemspec
@@ -47,9 +47,9 @@ An extension for Asciidoctor that converts AsciiDoc 
documents to PDF using the P
  # prawn-svg >= 0.22.1 requires Ruby >= 2.0.0, so we must cast a 
wider net to support Ruby 1.9.3

  s.add_runtime_dependency 'prawn-svg', '>= 0.28.0'
  s.add_runtime_dependency 'prawn-icon', '>= 1.4.0'
-  s.add_runtime_dependency 'safe_yaml', '~> 1.0.4'
+  s.add_runtime_dependency 'safe_yaml', '~> 1.0', '>= 1.0.4'
  s.add_runtime_dependency 'thread_safe', '~> 0.3.6'
-  s.add_runtime_dependency 'concurrent-ruby', '~> 1.0.5'
+  s.add_runtime_dependency 'concurrent-ruby', '~> 1.0', '>= 1.0.5'
  # For our usage, treetop 1.6.2 is slower than 1.5.3
  s.add_runtime_dependency 'treetop', '>= 1.5.3'
end

I have also sent a merge request 



--- End Message ---
--- Begin Message ---

Source: ruby-asciidoctor-pdf
Version: 1.5.3-1

Updated gemspec dependency on concurrent-ruby to ~> 1.1.0 which matches 1.1.6

-- 
-keith


signature.asc
Description: PGP signature
--- End Message ---

Bug#952105: marked as pending in planetblupi

[Didier 'OdyX' Raboud]

Control: tag -1 pending

Hello,

Bug #952105 in planetblupi 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/planetblupi/-/commit/d00242ce65cb608190a0eb61fe83a6f8d404c21a


Don't assume that SDL2 headers are in /usr/include/SDL2

Closes: #952105


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952105

Processed: Bug#952105 marked as pending in planetblupi

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952105 [src:planetblupi] planetblupi: FTBFS: blupi.h:23:10: fatal error: 
SDL.h: No such file or directory
Added tag(s) pending.

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

Bug#953205: Workaround

[Soren Stoutner]

As a workaround to this problem, commenting out line number 6 from

/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/core_ext/object/json.rb

allows the package to be configured.

# require "uri/generic"

I do not know enough about the internals of Ruby to know if doing this 
will cause other problems, but it did get my Redmine installation up and 
running while awaiting a more permanent fix.


--
Soren Stoutner
Small Business Tech Solutions
623-262-6169
so...@smallbusinesstech.net

Bug#938736: txwinrm: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

On Fri, Aug 30, 2019 at 07:57:05AM +, Matthias Klose wrote:
> Package: src:txwinrm
> Version: 1.3.3-1
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
> 
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2 from the distribution, as discussed in
> https://lists.debian.org/debian-python/2019/07/msg00080.html
> 
> Your package either build-depends, depends on Python2, or uses Python2
> in the autopkg tests.  Please stop using Python2, and fix this issue
> by one of the following actions.

Hi Christopher,
there was no followup from upstream on 
https://github.com/zenoss/txwinrm/issues/191
for > five months, shall we remove txwinrm?

Cheers,
Moritz

Processed: closing 951768

[Debian Bug Tracking System]

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

> close 951768 0.5.0-1
Bug #951768 [python3-sphinx-gallery] skimage documentation build fails with 
python 3.8
Marked as fixed in versions sphinx-gallery/0.5.0-1.
Bug #951768 [python3-sphinx-gallery] skimage documentation build fails with 
python 3.8
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: [bts-link] source package sphinx-gallery

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package sphinx-gallery
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #951768 (http://bugs.debian.org/951768)
> # Bug title: skimage documentation build fails with python 3.8
> #  * https://github.com/scikit-image/scikit-image/issues/4492
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 951768 + fixed-upstream
Bug #951768 [python3-sphinx-gallery] skimage documentation build fails with 
python 3.8
Added tag(s) fixed-upstream.
> usertags 951768 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: severity of 953289 is serious

[Debian Bug Tracking System]

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

> severity 953289 serious
Bug #953289 [libsoxr0] ABI change in libsoxr 0.1.3
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#953426: python-apt: Hasjes problem

[Julian Andres Klode]

Control: reassign -1 ftp.debian.org

On Mon, Mar 09, 2020 at 06:12:14PM +0100, Christian Marillat wrote:
> Package: python-apt
> Version: 1.9.10
> Severity: serious
> 
> Dear Maintainer,
> 
> Probably related that now apt use libgcrypt.
> 
> Output come from dak. Bug should be reassigned to ftp.debian.org is needed.
> 
> 
> dak process-upload -a -p -d 
> 
> dak_1.0.db122~20200307.git9dac010a-dmo1_amd64.changes
> 
> dak (1.0.db122~20200307.git9dac010a-dmo1) unstable; urgency=medium
>  .
>* New upstream release.
> 
> 
> 
> Reason:
> Processing raised an exception: 'apt_pkg.Hashes' object has no attribute 
> 'md5'.
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/daklib/archive.py", line 1019, in 
> check
> chk().check(self)
>   File "/usr/lib/python2.7/dist-packages/daklib/checks.py", line 146, in check
> self._check_hashes(upload, changes.filename, changes.files.itervalues())
>   File "/usr/lib/python2.7/dist-packages/daklib/checks.py", line 179, in 
> _check_hashes
> f.check(upload.directory)
>   File "/usr/lib/python2.7/dist-packages/daklib/upload.py", line 174, in check
> self.check_fh(fh)
>   File "/usr/lib/python2.7/dist-packages/daklib/upload.py", line 188, in 
> check_fh
> if hashes.md5 != self.md5sum:
> AttributeError: 'apt_pkg.Hashes' object has no attribute 'md5'

gotta uses hashes.hashes.find("MD5Sum") now.

API breaks in Python are messed up, given that there's no static
typing that would bring it up during a rebuild.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Processed: Re: Bug#953426: python-apt: Hasjes problem

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #953426 [python-apt] python-apt: Hasjes problem
Bug reassigned from package 'python-apt' to 'ftp.debian.org'.
No longer marked as found in versions python-apt/1.9.10.
Ignoring request to alter fixed versions of bug #953426 to the same values 
previously set

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

Bug#925797: marked as done (opensurgsim: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 17:19:13 +
with message-id 
and subject line Bug#925797: fixed in gpgme1.0 1.13.1-7
has caused the Debian Bug report #925797,
regarding opensurgsim: 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.)


-- 
925797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:opensurgsim
Version: 0.7.0-8
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/opensurgsim_0.7.0-8_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.

[...]
/<>/SurgSim/Physics/UnitTests/RigidCollisionRepresentationTest.cpp:138:85:
   required from here
/<>/SurgSim/Framework/Accessible-inl.h:49:2: warning: catching 
polymorphic type 'class boost::bad_any_cast' by value [-Wcatch-value=]
   49 |  catch (boost::bad_any_cast exception)
  |  ^
[ 98%] Building CXX object 
SurgSim/Physics/UnitTests/CMakeFiles/SurgSimPhysicsTest.dir/RigidConstraintFixedPointTests.cpp.o
cd /<>/obj-x86_64-linux-gnu/SurgSim/Physics/UnitTests && 
/usr/bin/c++  -DBOOST_ALL_DYN_LINK -D_POSIX_C_SOURCE=200809L -I/<> 
-I/<>/obj-x86_64-linux-gnu -I/usr/include/eigen3 
-I/usr/lib/x86_64-linux-gnu/cmake/yaml-cpp/../../../../../include -isystem 
/usr/src/googletest/googletest/include -isystem 
/usr/src/googletest/googlemock/include -isystem /usr/src/googletest/googlemock 
-isystem /usr/src/googletest/googletest  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall  -std=gnu++11   -DGTEST_HAS_PTHREAD=1 -o 
CMakeFiles/SurgSimPhysicsTest.dir/RigidConstraintFixedPointTests.cpp.o -c 
/<>/SurgSim/Physics/UnitTests/RigidConstraintFixedPointTests.cpp
[ 98%] Building CXX object 
SurgSim/Physics/UnitTests/CMakeFiles/SurgSimPhysicsTest.dir/RigidConstraintFixedRotationVectorTests.cpp.o
cd /<>/obj-x86_64-linux-gnu/SurgSim/Physics/UnitTests && 
/usr/bin/c++  -DBOOST_ALL_DYN_LINK -D_POSIX_C_SOURCE=200809L -I/<> 
-I/<>/obj-x86_64-linux-gnu -I/usr/include/eigen3 
-I/usr/lib/x86_64-linux-gnu/cmake/yaml-cpp/../../../../../include -isystem 
/usr/src/googletest/googletest/include -isystem 
/usr/src/googletest/googlemock/include -isystem /usr/src/googletest/googlemock 
-isystem /usr/src/googletest/googletest  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall  -std=gnu++11   -DGTEST_HAS_PTHREAD=1 -o 
CMakeFiles/SurgSimPhysicsTest.dir/RigidConstraintFixedRotationVectorTests.cpp.o 
-c 
/<>/SurgSim/Physics/UnitTests/RigidConstraintFixedRotationVectorTests.cpp
[ 98%] Building CXX object 
SurgSim/Physics/UnitTests/CMakeFiles/SurgSimPhysicsTest.dir/RigidConstraintFrictionlessContactTests.cpp.o
cd /<>/obj-x86_64-linux-gnu/SurgSim/Physics/UnitTests && 
/usr/bin/c++  -DBOOST_ALL_DYN_LINK -D_POSIX_C_SOURCE=200809L -I/<> 
-I/<>/obj-x86_64-linux-gnu -I/usr/include/eigen3 
-I/usr/lib/x86_64-linux-gnu/cmake/yaml-cpp/../../../../../include -isystem 
/usr/src/googletest/googletest/include -isystem 
/usr/src/googletest/googlemock/include -isystem /usr/src/googletest/googlemock 
-isystem /usr/src/googletest/googletest  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall  -std=gnu++11   -DGTEST_HAS_PTHREAD=1 -o 
CMakeFiles/SurgSimPhysicsTest.dir/RigidCo

Bug#875243: [yagf] Future Qt4 removal from Buster

[Boris Pek]

Hi everyone,

> Status update: Qt4 has now been droppped from testing, qt4 will be removed
> from unstable by end of February (along with the remaining rdeps (currently 
> 15)).

As I see yagf package is still in Debian repo.
And now I have enough free time for updating it...
So I am going to upload updated version ported to Qt5 today if no-one objects.

Best regards,
Boris

Bug#875243: [yagf] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Hi Boris! (sorry for the double mail)

On Mon, 9 Mar 2020 at 14:08, Boris Pek  wrote:
>
> Hi everyone,
>
> > Status update: Qt4 has now been droppped from testing, qt4 will be removed
> > from unstable by end of February (along with the remaining rdeps (currently 
> > 15)).
>
> As I see yagf package is still in Debian repo.
> And now I have enough free time for updating it...
> So I am going to upload updated version ported to Qt5 today if no-one objects.

Qt 4 has been removed form the archive last saturday, so the fastest the better.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Bug#953426: python-apt: Hasjes problem

[Christian Marillat]

Package: python-apt
Version: 1.9.10
Severity: serious

Dear Maintainer,

Probably related that now apt use libgcrypt.

Output come from dak. Bug should be reassigned to ftp.debian.org is needed.


dak process-upload -a -p -d 

dak_1.0.db122~20200307.git9dac010a-dmo1_amd64.changes

dak (1.0.db122~20200307.git9dac010a-dmo1) unstable; urgency=medium
 .
   * New upstream release.



Reason:
Processing raised an exception: 'apt_pkg.Hashes' object has no attribute 'md5'.
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/daklib/archive.py", line 1019, in check
chk().check(self)
  File "/usr/lib/python2.7/dist-packages/daklib/checks.py", line 146, in check
self._check_hashes(upload, changes.filename, changes.files.itervalues())
  File "/usr/lib/python2.7/dist-packages/daklib/checks.py", line 179, in 
_check_hashes
f.check(upload.directory)
  File "/usr/lib/python2.7/dist-packages/daklib/upload.py", line 174, in check
self.check_fh(fh)
  File "/usr/lib/python2.7/dist-packages/daklib/upload.py", line 188, in 
check_fh
if hashes.md5 != self.md5sum:
AttributeError: 'apt_pkg.Hashes' object has no attribute 'md5'


Christian

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

Kernel: Linux 4.19.108 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_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 python-apt depends on:
ii  dirmngr2.2.19-2
ii  gnupg  2.2.19-2
ii  libapt-pkg6.0  2.0.0
ii  libc6  2.29-10
ii  libgcc-s1  10-20200304-1
ii  libstdc++6 10-20200304-1
ii  python-apt-common  1.9.10
ii  python22.7.17-2

Versions of packages python-apt recommends:
ii  iso-codes4.4-1
ii  lsb-release  11.1.0
ii  xz-utils 5.2.4-1+b1

Versions of packages python-apt suggests:
ii  apt 2.0.0
pn  python-apt-dbg  
pn  python-apt-doc  

-- no debconf information

Bug#953199: marked as done (r10k: autopkgtest needs update for new version of ruby-puppet-forge: strict undeclared dependency)

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 15:50:57 +
with message-id 
and subject line Bug#953199: fixed in r10k 3.4.0-1
has caused the Debian Bug report #953199,
regarding r10k: autopkgtest needs update for new version of ruby-puppet-forge: 
strict undeclared dependency
to be marked as done.

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

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


-- 
953199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r10k
Version: 3.1.0-1
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:ruby-puppet-forge

[X-Debbugs-CC: debian...@lists.debian.org,
ruby-puppet-fo...@packages.debian.org]

Dear maintainers,

With a recent upload of ruby-puppet-forge the autopkgtest of r10k fails
in testing when that autopkgtest is run with the binary packages of
ruby-puppet-forge from unstable. It passes when run with only packages
from testing. In tabular form:
   passfail
ruby-puppet-forge  from testing2.3.2-1
r10k   from testing3.1.0-1
all others from testingfrom testing

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

Currently this regression is blocking the migration of ruby-puppet-forge
to testing [1]. Of course, ruby-puppet-forge shouldn't just break your
autopkgtest (or even worse, your package), but it seems to me that the
change in ruby-puppet-forge was intended and your package needs to
update to the new situation.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from ruby-puppet-forge should
really add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.

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

Paul

[1] https://qa.debian.org/excuses.php?package=ruby-puppet-forge

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r10k/4452690/log.gz

fatal: not a git repository (or any of the parent directories): .git
GEM_PATH= ruby2.5 -e gem\ \"r10k\"
/usr/lib/ruby/2.5.0/rubygems/dependency.rb:312:in `to_specs': Could not
find 'puppet_forge' (~> 2.2.8) - did find: [puppet_forge-2.3.2]
(Gem::MissingSpecVersionError)
Checked in
'GEM_PATH=/home/debci/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/ruby/gems/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0',
execute `gem env` for more information
from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1469:in `block in
activate_dependencies'
from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1458:in `each'
from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1458:in
`activate_dependencies'
from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1440:in `activate'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:68:in `block
in gem'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:67:in
`synchronize'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:67:in `gem'
from -e:1:in `'



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r10k
Source-Version: 3.4.0-1
Done: Georg Faerber 

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

Debian distribution maintenance software
pp.
Georg Faerber  (supplier of updated r10k 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, 09 Mar 2020 15:24:40 +
Source: r10k
Architecture: source
Version: 3.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers 

Changed-By: Georg Faerber 
Closes: 953199
Changes:
 r10k (3.4.0-1) unstable; urgency=medium
 .
   * New upstream version 3.4.0. (Closes: #953199)
 

Bug#953098: xscreensaver: Crashes with XIO: fatal IO error

[Jens Holzkämper]

So, I tried another self compiled version, this time without any of the 
Debian patches to see if the crashes happen with a pure upstream 
version: They do (see attached log), so I'll inform upstream of the 
problem as well.



> When using
> xscreensaver -nosplash -log /tmp/x.log -verbose &
> I did not see the XIO fatal IO error message.> > The crash was not 
accompanied by any useful information in the logfile.

> If someone can advise how to get more information in the logfile, I'll
> be happy to help investigate this bug.

Adding the parameter -no-capture-stderr is needed to capture error 
messages during a xscreensaver-crash acording to the man-page.


error 10 with 5.43-no-debian-patches.gz
Description: application/gzip

Processed: Re: Bug#953369: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #953369 [libpython3.8-minimal] RuntimeWarning: line buffering (buffering=1) 
isn't supported in binary mode, the default buffer size will be used
Severity set to 'serious' from 'normal'
> affects -1 codespell
Bug #953369 [libpython3.8-minimal] RuntimeWarning: line buffering (buffering=1) 
isn't supported in binary mode, the default buffer size will be used
Added indication that 953369 affects codespell

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

Processed: Re: Bug#953301: opensmtpd-extras: bad API version error while using the sqlite plugin

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 946834 -1
Bug #946834 [opensmtpd-extras] opensmtpd-extras: bad API version error while 
using the LDAP plugin
Bug #953301 [opensmtpd-extras] opensmtpd-extras: bad API version error while 
using the sqlite plugin
Severity set to 'important' from 'grave'
Merged 946834 953301
> retitle 946834 API version mismatch in Debian stable
Bug #946834 [opensmtpd-extras] opensmtpd-extras: bad API version error while 
using the LDAP plugin
Bug #953301 [opensmtpd-extras] opensmtpd-extras: bad API version error while 
using the sqlite plugin
Changed Bug title to 'API version mismatch in Debian stable' from 
'opensmtpd-extras: bad API version error while using the LDAP plugin'.
Changed Bug title to 'API version mismatch in Debian stable' from 
'opensmtpd-extras: bad API version error while using the sqlite plugin'.

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

Bug#953301: opensmtpd-extras: bad API version error while using the sqlite plugin

[Ryan Kavanagh]

Control: forcemerge 946834 -1
Control: retitle 946834 API version mismatch in Debian stable

Thanks for the bug report larzeni. Indeed, it appears that there is an
API mismatch between many (all?) of the opensmtpd-extras tables and the
version of opensmtpd in Debian stable.

Here's what happened. The opensmtpd-extras version in stable (5.7.1) was
released on 13-Jul-2015 and no other releases were made until
07-Nov-2018 (this version did not make it into Buster). Meanwhile, new
versions of opensmtpd continued to be released. For example, the version
of opensmtpd in stable (6.0.3p1) was released on 16-Jan-2018. At some
point, the new releases of opensmtpd stopped being compatible with the
existing opensmtpd-extras release. https://opensmtpd.org/archives/

At this point, it is too late to update the upstream version of
opensmtpd-extras in Buster. I'll prepare a new upload to Buster that
simply removes all of the broken tables.

If it helps, more recent versions of opensmtpd / opensmtpd-extras are
available from Debian backports: https://backports.debian.org/

Best,
Ryan

-- 
|)|/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac |  BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature

Bug#953318: marked as done (hplip: Failed to upgrade/install: dpkg-statoverride: warning: no override present)

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 14:48:19 +
with message-id 
and subject line Bug#953318: fixed in hplip 3.20.2+dfsg0-3
has caused the Debian Bug report #953318,
regarding hplip: Failed to upgrade/install:  dpkg-statoverride: warning: no 
override present
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.)


-- 
953318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hplip
Severity: grave
Version: 3.20.2+dfsg0-2
X-Debbugs-CC: d...@debian.org j...@debian.org m...@debian.org

Dear Debian hplip maintainers,

The latest version of hplip caused piuparts regression: 
https://piuparts.debian.org/sid/fail/hplip_3.20.2+dfsg0-2.log

It also failed to install and/or upgrade on my system:

[...]
Setting up hplip (3.20.2+dfsg0-2) ...
Creating/updating hplip user account...
dpkg-statoverride: warning: no override present
dpkg: error processing package hplip (--configure):
 installed hplip package post-installation script subprocess returned error
exit status 2
[...]

Please revise the changes made around dpkg-statoverride in the latest upload.
Thanks!

-- 
Regards,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: hplip
Source-Version: 3.20.2+dfsg0-3
Done: Didier Raboud 

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

Debian distribution maintenance software
pp.
Didier Raboud  (supplier of updated hplip package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 09 Mar 2020 14:15:39 +0100
Source: hplip
Architecture: source
Version: 3.20.2+dfsg0-3
Distribution: unstable
Urgency: high
Maintainer: Debian Printing Team 
Changed-By: Didier Raboud 
Closes: 953318
Changes:
 hplip (3.20.2+dfsg0-3) unstable; urgency=high
 .
   * Fix dpkg-statoverride calls (Closes: #953318)
   * Add patch to revert 3.20.2 change to io/hpmud/jd.c (hopefully fixing
 some print failures)
Checksums-Sha1:
 48201ad7394272e18485a90bcde138d93dcac6dd 3179 hplip_3.20.2+dfsg0-3.dsc
 17ea5641f099b289897632bbc6fa3a27d29b000b 134096 
hplip_3.20.2+dfsg0-3.debian.tar.xz
Checksums-Sha256:
 c948a10ed38eb232f3ebfb86686e8fb4eda289dfc9839e67f7dd909e079ace91 3179 
hplip_3.20.2+dfsg0-3.dsc
 359f92e2276944da5fc29e58ef8f1ab50ef17e62c0ae31a02ff740eb50cc26cf 134096 
hplip_3.20.2+dfsg0-3.debian.tar.xz
Files:
 2e928641f6a4b14c62aeec956bc642ff 3179 utils optional hplip_3.20.2+dfsg0-3.dsc
 4621e65953637f1cea49e6e743f417c0 134096 utils optional 
hplip_3.20.2+dfsg0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJ3k7rA0YCplkx4gZqcb6xg1jAWkFAl5mRrEACgkQqcb6xg1j
AWkEahAAwo7E9jXo2xQuJWy9TiK2vGOxV/J9rb2KJBizP5JDXmakryEg4Up98+pE
PJc1SgyZAbqE6pK1m/BiOhxsKch3Hl9X+LZok+RxxGxwyJW/8ox1y7zEvUcylgeZ
uKFcqspfjFNc1Fv14EjKkScHa2wELFG1HsEO7WTivOXT3Ln5uTtK+tiHZTC4p557
TGjPjzZqKHnUMbj1CF9p8dNwb2QXXq/Jjr/+DF2/F66KVwx8Dfmn0CMsWr53eYmL
PEH2ZAe6dqpRGen82G0W49HFNP04R4BrlZlDMioLedSftXH0SEtMfQcegBKBeX3A
hg7O9eF2OKbbwNiD53mE3qI6911Tot98JLEUls8L1oDQfiSkHDHxE3ybQ1b5uPzL
LRBNBsgKgNDNmn3iD4pgaIIf9IidBaRI1NJ62nRX+t3Et9MKi/c1GrrD8yPgYvBB
jCAaiOK5isrDsG+2yTIaz/lV+XHM60sMxo+43rNka7Ws7zLF7TQSQg78B9Xxy8Wk
IChgX6eMrLWqqCJ2gBeU1FDj2gXZv05Dijik0Ixji2RKCoor7vDDVUrzI4JKmkzv
z+tyEj6uvQS8Zq3dsRM6W8VyN+KpCLEyLrkkPzFlptXuS7gfePizq7QSLJ6btQOT
4UIMK1TIGrwLwjYq28vlpIzRG6++YbCDmq2bikvDAFRbp3H4lKU=
=KGHL
-END PGP SIGNATURE End Message ---

Bug#953331: marked as done (ldb: FTBFS with Python 3.8)

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 14:48:32 +
with message-id 
and subject line Bug#953331: fixed in ldb 2:2.0.8-2
has caused the Debian Bug report #953331,
regarding ldb: FTBFS 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.)


-- 
953331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ldb
Version: 2:2.0.8-1
Severity: serious
Tags: ftbfs patch

Hi Maintainer

ldb FTBFS on some architectures when rebuilt with Python 3.8 [1].

dpkg-gensymbols: error: new libraries appeared in the symbols file:
libpyldb-util.cpython-38-x86-64-linux-gnu.so.2
dpkg-gensymbols: error: some libraries disappeared in the symbols
file: libpyldb-util.cpython-37m-x86-64-linux-gnu.so.2

The attached patch fixed the problem in Ubuntu.

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=ldb&suite=unstable
diff -Nru ldb-2.0.8/debian/changelog ldb-2.0.8/debian/changelog
--- ldb-2.0.8/debian/changelog	2020-01-27 09:45:29.0 +
+++ ldb-2.0.8/debian/changelog	2020-01-27 18:12:42.0 +
@@ -1,3 +1,9 @@
+ldb (2:2.0.8-1ubuntu1) focal; urgency=medium
+
+  * d/python3-ldb.symbols*: update symbols for python 3.8
+
+ -- Andreas Hasenack   Mon, 27 Jan 2020 15:12:42 -0300
+
 ldb (2:2.0.8-1) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru ldb-2.0.8/debian/control ldb-2.0.8/debian/control
--- ldb-2.0.8/debian/control	2020-01-27 09:45:29.0 +
+++ ldb-2.0.8/debian/control	2020-01-27 18:12:42.0 +
@@ -1,7 +1,8 @@
 Source: ldb
 Section: devel
 Priority: optional
-Maintainer: Debian Samba Maintainers 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: Debian Samba Maintainers 
 Uploaders: Jelmer Vernooij ,
Mathieu Parent 
 Build-Depends: dh-exec,
diff -Nru ldb-2.0.8/debian/python3-ldb.symbols.amd64 ldb-2.0.8/debian/python3-ldb.symbols.amd64
--- ldb-2.0.8/debian/python3-ldb.symbols.amd64	2020-01-27 09:45:29.0 +
+++ ldb-2.0.8/debian/python3-ldb.symbols.amd64	2020-01-27 18:12:42.0 +
@@ -1,3 +1,3 @@
-libpyldb-util.cpython-37m-x86-64-linux-gnu.so.2 python3-ldb #MINVER#
- PYLDB_UTIL.CPYTHON_37M_X86_64_LINUX_GNU_2.0.8@PYLDB_UTIL.CPYTHON_37M_X86_64_LINUX_GNU_2.0.8 2:2.0.8
+libpyldb-util.cpython-38-x86-64-linux-gnu.so.2 python3-ldb #MINVER#
+ PYLDB_UTIL.CPYTHON_38_X86_64_LINUX_GNU_2.0.8@PYLDB_UTIL.CPYTHON_38_X86_64_LINUX_GNU_2.0.8 2:2.0.8
 #include "python3-ldb.symbols.common"
diff -Nru ldb-2.0.8/debian/python3-ldb.symbols.arm64 ldb-2.0.8/debian/python3-ldb.symbols.arm64
--- ldb-2.0.8/debian/python3-ldb.symbols.arm64	2020-01-27 09:45:29.0 +
+++ ldb-2.0.8/debian/python3-ldb.symbols.arm64	2020-01-27 18:12:42.0 +
@@ -1,3 +1,3 @@
-libpyldb-util.cpython-37m-aarch64-linux-gnu.so.2 python3-ldb #MINVER#
- PYLDB_UTIL.CPYTHON_37M_AARCH64_LINUX_GNU_2.0.8@PYLDB_UTIL.CPYTHON_37M_AARCH64_LINUX_GNU_2.0.8 2:2.0.8
+libpyldb-util.cpython-38-aarch64-linux-gnu.so.2 python3-ldb #MINVER#
+ PYLDB_UTIL.CPYTHON_38_AARCH64_LINUX_GNU_2.0.8@PYLDB_UTIL.CPYTHON_38_AARCH64_LINUX_GNU_2.0.8 2:2.0.8
 #include "python3-ldb.symbols.common"
diff -Nru ldb-2.0.8/debian/python3-ldb.symbols.armhf ldb-2.0.8/debian/python3-ldb.symbols.armhf
--- ldb-2.0.8/debian/python3-ldb.symbols.armhf	2020-01-27 09:45:29.0 +
+++ ldb-2.0.8/debian/python3-ldb.symbols.armhf	2020-01-27 18:12:42.0 +
@@ -1,3 +1,3 @@
-libpyldb-util.cpython-37m-arm-linux-gnueabihf.so.2 python3-ldb #MINVER#
- PYLDB_UTIL.CPYTHON_37M_ARM_LINUX_GNUEABIHF_2.0.8@PYLDB_UTIL.CPYTHON_37M_ARM_LINUX_GNUEABIHF_2.0.8 2:2.0.8
+libpyldb-util.cpython-38-arm-linux-gnueabihf.so.2 python3-ldb #MINVER#
+ PYLDB_UTIL.CPYTHON_38_ARM_LINUX_GNUEABIHF_2.0.8@PYLDB_UTIL.CPYTHON_38_ARM_LINUX_GNUEABIHF_2.0.8 2:2.0.8
 #include "python3-ldb.symbols.common"
diff -Nru ldb-2.0.8/debian/python3-ldb.symbols.i386 ldb-2.0.8/debian/python3-ldb.symbols.i386
--- ldb-2.0.8/debian/python3-ldb.symbols.i386	2020-01-27 09:45:29.0 +
+++ ldb-2.0.8/debian/python3-ldb.symbols.i386	2020-01-27 18:12:42.0 +
@@ -1,3 +1,3 @@
-libpyldb-util.cpython-37m-i386-linux-gnu.so.2 python3-ldb #MINVER#
- PYLDB_UTIL.CPYTHON_37M_I386_LINUX_GNU_2.0.8@PYLDB_UTIL.CPYTHON_37M_I386_LINUX_GNU_2.0.8 2:2.0.8
+libpyldb-util.cpython-38-i386-linux-gnu.so.2 python3-ldb #MINVER#
+ PYLDB_UTIL.CPYTHON_38_I386_LINUX_GNU_2.0.8@PYLDB_UTIL.CPYTHON_38_I386_LINUX_GNU_2.0.8 2:2.0.8
 #include "python3-ldb.symbols.common"
diff -Nru ldb-2.0.8/debian/python3-ldb.symbols.ppc64el ldb-2.0.8/debian/python3-ldb.symbols.ppc64el
--- ldb-2.0.8/debian/python3-ldb.symbols

Processed: Re: Bug#953357: dput-ng: sftp upload is broken: AttributeError: module 'os' has no attribute 'errno'

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #953357 [dput-ng] dput-ng: sftp upload is broken: AttributeError: module 
'os' has no attribute 'errno'
Severity set to 'important' from 'grave'
> retitle -1 dput-ng: crash on PermissionError
Bug #953357 [dput-ng] dput-ng: sftp upload is broken: AttributeError: module 
'os' has no attribute 'errno'
Changed Bug title to 'dput-ng: crash on PermissionError' from 'dput-ng: sftp 
upload is broken: AttributeError: module 'os' has no attribute 'errno''.

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

Bug#953357: dput-ng: sftp upload is broken: AttributeError: module 'os' has no attribute 'errno'

[Mattia Rizzolo]

Control: severity -1 important
Control: retitle -1 dput-ng: crash on PermissionError

On Sun, Mar 08, 2020 at 06:12:53PM +0530, Pirate Praveen wrote:
> $ dput ssh-upload ../node-clipboard_2.0.4+ds-2~bpo10+1_amd64.changes
…
>raise IOError(errno.EACCES, text)
> PermissionError: [Errno 13] Permission denied

This means that your likely trying to overwrite a file for which you
have no write permissions.


> During handling of the above exception, another exception occurred:
> 
> Traceback (most recent call last):
>  File "/usr/bin/dput", line 129, in 
>upload_package(changes, args)
>  File "/usr/lib/python3/dist-packages/dput/uploader.py", line 343, in
> invoke_dput
>obj.upload_file(path)
>  File "/usr/lib/python3/dist-packages/dput/uploaders/sftp.py", line 285, in
> upload_file
>if e.errno == os.errno.EACCES:
> AttributeError: module 'os' has no attribute 'errno'

This is the crash bit that will be fixed within dput-ng… it's just a
leftover from py2→py3, as errno is now its own library.

Imagine this warning coming out:

  logger.warning("""Upload permissions error

  You either don't have the rights to upload a file, or, if this is on
  ftp-master, you may have tried to overwrite a file already on the server.

  Continuing anyway in case you want to recover from an incomplete upload.
  No file was uploaded, however.""")

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#953351: marked as done (warzone2100: FTBFS in unstable: No package 'harfbuzz' found)

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 13:53:42 +
with message-id 
and subject line Bug#953351: fixed in warzone2100 3.3.0-2
has caused the Debian Bug report #953351,
regarding warzone2100: FTBFS in unstable: No package 'harfbuzz' 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.)


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


> checking for main in -lGL... yes
> checking for main in -lGLU... yes
> checking for FRIBIDI... yes
> checking for FREETYPE... yes
> checking for HARFBUZZ... configure: error: Package requirements (harfbuzz) 
> were not met:
>
> No package 'harfbuzz' found

Presumably one of its build-dependencies used to depend on libharfbuzz-dev
and no longer does.

It would be a good idea to check configure.ac for anything else that is
explicitly checked for, and add build-dependencies on those too, if any.

smcv
--- End Message ---
--- Begin Message ---
Source: warzone2100
Source-Version: 3.3.0-2
Done: Russell Coker 

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

Debian distribution maintenance software
pp.
Russell Coker  (supplier of updated warzone2100 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 10 Mar 2020 00:24:48 +1100
Source: warzone2100
Architecture: source
Version: 3.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Russell Coker 
Closes: 953351
Changes:
 warzone2100 (3.3.0-2) unstable; urgency=medium
 .
   * Build-depend on libharfbuzz-dev  Closes: #953351
   * Added myself to the uploaders.
   * NB wkhtmltopdf needs execmem access to run without SEGV.
Checksums-Sha1:
 36ba76cf772a5c960af8490e677ac9204e2d5cc5 2610 warzone2100_3.3.0-2.dsc
 810e437ee9ca5cc7041bbc0e4e7db49ae3592785 26400 
warzone2100_3.3.0-2.debian.tar.xz
 b28d4504b160982b7dc2b89e04f720b8c268b1fa 16352 
warzone2100_3.3.0-2_amd64.buildinfo
Checksums-Sha256:
 ab9814aa97160ee73386064fd13b08bb1b91ed0f2493903c21dd5a442a0757ce 2610 
warzone2100_3.3.0-2.dsc
 e3780b3dd99358b80d51d0e3239b2cf6c8e1c499117db8e08e496cae167495bc 26400 
warzone2100_3.3.0-2.debian.tar.xz
 b7b05589194c541f4b33424a322ef2ad10ff6f60bfbba9b2a352efc475409230 16352 
warzone2100_3.3.0-2_amd64.buildinfo
Files:
 ab356928479e22bde8b5bd8f0cbd760f 2610 games optional warzone2100_3.3.0-2.dsc
 64f26c63092d77741040ecc445acebb9 26400 games optional 
warzone2100_3.3.0-2.debian.tar.xz
 a44ef69a73255a0cc78bbd5fdc6a7fe5 16352 games optional 
warzone2100_3.3.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEn31hncwG9XwCqmbH0UHNMPxLj3kFAl5mRggACgkQ0UHNMPxL
j3lBkQ/9EaAhCtzeiVM8wbe+Bx4gWrwxmvFACN6Yb0PMsFHAcWn0cDUblsok8iqv
OWgdr0kiDJVG1H01g72S70m13Hifw0m5TTRzVocXbz27HP7VqHbvEIJV6c5TXl67
afWC9jQWKw98mvaxm0kyVIt6s1wT213pED2VSk8iQTOvtfO3nCucl3sQNbsIwgAs
CMj5heuHSFJMsqWCqPO0zL7E+dW3tuUCilYMRCkfjsLhuDcdrJsWqrSTDBsoIuXM
ieSCz3cVXglOI7YXoHC+oh/hoWy2k0e8eUR058j5Azm4yYQBjn553dr+W55xiNGn
u1jNXUiTG54x8RWLXUY5ks6g8AT6BlCqf9y55jZo9B1hYyPbsM9zPZcCZvlynx3w
WWZTYNYOljvXvIOrWX+0pFCd664kwM9I+0wMt2YT+nk7mr5/Om0ZkCZ4a/k9x0L6
/A8HemJsLFqvoOp8aoxzbYG/AGYV8D24Uh6IgDAf5c1ko1vhZjtBQxl/E3JbxIMN
dpVrBxI1BkSL9Lf2rtMF89btLFOTWoaDuRZ+YD7Ibw7yEdQ5G4X4NRRH5FBU9uNI
siO2f/uDmtXgWx7pd8p1buuE3/DtVd8wbWgwYaB6cnrXKoT7sFKBXkETINhlnGIA
dDz+alEtUXApt/cGFh7UxQtCFRsaZ4gZ1bKC04Vwq5Qbxuso/2w=
=FSeV
-END PGP SIGNATURE End Message ---

Bug#952610: fixed in meson 0.53.2-2

[Sebastien Bacher]

> Maybe the autopkg dependency lookup code gets confused by @builddeps@
somehow?

Right, that's an known limitation of the autopkgtest infrastructure at
the moment, builddepds resolve fine for installing packages in the test
environement but fail to register triggers. You can workaround by adding
manually the packages though which the patch is doing

Bug#953358: marked as done (python3-ball: missing (unversioned) Breaks+Replaces: python-ball)

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 12:04:21 +
with message-id 
and subject line Bug#953358: fixed in ball 1.5.0+git20180813.37fc53c-6
has caused the Debian Bug report #953358,
regarding python3-ball: missing (unversioned) Breaks+Replaces: python-ball
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.)


-- 
953358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953358
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-ball
Version: 1.5.0+git20180813.37fc53c-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Preparing to unpack .../python3-ball_1.5.0+git20180813.37fc53c-5_amd64.deb ...
  Unpacking python3-ball (1.5.0+git20180813.37fc53c-5) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-ball_1.5.0+git20180813.37fc53c-5_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/share/BALL-1.5/PYTHON/BALLView/add_hydrogens_BV.py', which is also in 
package python-ball 1.5.0+git20180813.37fc53c-4
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-ball_1.5.0+git20180813.37fc53c-5_amd64.deb

Since python-ball is gone in experimental, the B+R can be unversioned.


cheers,

Andreas


python-ball=1.5.0+git20180813.37fc53c-4_python3-ball=1.5.0+git20180813.37fc53c-5.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ball
Source-Version: 1.5.0+git20180813.37fc53c-6
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated ball 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, 09 Mar 2020 11:45:03 +0100
Source: ball
Architecture: source
Version: 1.5.0+git20180813.37fc53c-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 953358
Changes:
 ball (1.5.0+git20180813.37fc53c-6) unstable; urgency=medium
 .
   [ Steffen Möller ]
   * Update metadata - yamllint, BALL paper
 .
   [ Stuart Prescott ]
   * Add missing Breaks/Replaces for python3-ball
 Closes: #953358
 .
   [ Andreas Tille ]
   * Add debian/salsa-ci.yml
Checksums-Sha1:
 8d91791afe3ff0a6fb2e5f25762afacdb5392579 3054 
ball_1.5.0+git20180813.37fc53c-6.dsc
 0d9d0363609739ce5599495c30c89c15a1de951a 13676 
ball_1.5.0+git20180813.37fc53c-6.debian.tar.xz
 027ffed8331e8d8f339ec1eef60f7257019c2138 20878 
ball_1.5.0+git20180813.37fc53c-6_amd64.buildinfo
Checksums-Sha256:
 a0c9e04b7283764c83fefd44cd568be08c7c13a378feb3c4054dabef310c7978 3054 
ball_1.5.0+git20180813.37fc53c-6.dsc
 5dee63c16126e253621162f21b40ba7332e527882a675621b7ce2e5550b273ad 13676 
ball_1.5.0+git20180813.37fc53c-6.debian.tar.xz
 44b6f35cf7934a9b018bcdb425fd4d62f1678087dc873a613e61031b7f73521a 20878 
ball_1.5.0+git20180813.37fc53c-6_amd64.buildinfo
Files:
 dd81da752620194153345825ead88d7a 3054 science optional 
ball_1.5.0+git20180813.37fc53c-6.dsc
 6adc7947bf45b53e6024024a28c1768a 13676 science optional 
ball_1.5.0+git20180813.37fc53c-6.debian.tar.xz
 776e4fe523170ddf8e8e3109163853f0 20878 science optional 
ball_1.5.0+git20180813.37fc53c-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl5mLcsRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFU8A/8CQzsiV29s8BKjdjfyu8JMpwIMAOxYqY1
riiR70msT6ijzUgwfKcNVjHZVqDemPsPlICbQJLmLUAznJKs76JaETH1QMYUlMHQ
/+bCwNSUKExItQ1LDiyPUyK/GiDNnozr7HV8yZHobCK3JueLv9M2is8lP8Y3zryu
ZyCg+zsy9njgW+k87IdXQAIqPkhgQfU++vHoWB/X4Ujjr7vxhU1SHcv75jSRkRsX
A5nyunKOPZHBqFT63BN2GdvdSDM5HgcfUIhsWwnf/NBFEzwP7HJZ3eAnUklULjcI
38Nv/eZo2xWlxSz3gVwrT

Bug#951877: Patch: OpenSSL linking without license exception

[Bastian Germann]

This patch builds the package without OpenSSL.
>From 658cfaa87943e6423ee61fe078b93655b3f7fa70 Mon Sep 17 00:00:00 2001
From: Bastian Germann 
Date: Mon, 9 Mar 2020 12:32:07 +0100
Subject: [PATCH] Disable SSL (Closes: #951877)

---
 debian/control | 1 -
 debian/rules   | 2 +-
 2 files changed, 1 insertion(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index 0118f51..2e32fbd 100644
--- a/debian/control
+++ b/debian/control
@@ -5,7 +5,6 @@ Maintainer: Alexandre Viau 
 Build-Depends: debhelper (>= 9),
cmake,
libasio-dev,
-   libssl-dev,
libkashmir-dev
 Standards-Version: 3.9.8
 Homepage: https://github.com/Corvusoft/restbed
diff --git a/debian/rules b/debian/rules
index 68961b3..7153ea5 100755
--- a/debian/rules
+++ b/debian/rules
@@ -13,7 +13,7 @@ override_dh_auto_configure:
 	dh_auto_configure -- \
 	-DBUILD_TESTS=OFF \
 	-DBUILD_EXAMPLES=OFF \
-	-DBUILD_SSL=ON \
+	-DBUILD_SSL=OFF \
 	-DBUILD_SHARED=ON \
 	-DCMAKE_BUILD_TYPE=Release
 
-- 
2.20.1

Bug#950176: marked as done (source-highlight: FTBFS on all architectures other than amd64)

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 11:08:13 +
with message-id 
and subject line Bug#950176: fixed in source-highlight 3.1.9-1.1
has caused the Debian Bug report #950176,
regarding source-highlight: FTBFS on all architectures other than amd64
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.)


-- 
950176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950176
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: source-hightlight
Version: 3.1.9-1
Severity: grave
Tags: patch

Dear source-highlight maintainer,

There is an error currently lying in the debian/rules file that prevents the
package from being built successfully on all architectures other than amd64:

https://sources.debian.org/src/source-highlight/3.1.9-1/debian/rules/#L20

"rm $(DESTDIR)/usr/lib/x86_64-linux-gnu/libsource-highlight.la" We should
never hardcode "x86_64-linux-gnu" in the debian/rules file since this path
will be different on other platform.

The solution should be replacing the triplet string with * so that it may
match all possible directories. A further improvement could be using "rm -f"
instead of "rm" so that the build would not fail even if the file to be
removed is not found.

-- 
Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: source-highlight
Source-Version: 3.1.9-1.1
Done: =?utf-8?b?SMOpY3RvciBPcsOzbiBNYXJ0w61uZXo=?= 

We believe that the bug you reported is fixed in the latest version of
source-highlight, 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.
Héctor Orón Martínez  (supplier of updated source-highlight 
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, 02 Mar 2020 11:16:32 +0100
Source: source-highlight
Architecture: source
Version: 3.1.9-1.1
Distribution: unstable
Urgency: medium
Maintainer: Kartik Kulkarni 
Changed-By: Héctor Orón Martínez 
Closes: 950176
Changes:
 source-highlight (3.1.9-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix builds on non intel architectures. (Closes: #950176)
Checksums-Sha1:
 0510a8568a7ec4fae80daffa2ecdc0b3b88b35c0 2131 source-highlight_3.1.9-1.1.dsc
 47717501658516f8fabe92e0a89f56030f7905ce 5404 
source-highlight_3.1.9-1.1.debian.tar.xz
 893c7d147c161218d817382ee67558406a0dca82 6861 
source-highlight_3.1.9-1.1_source.buildinfo
Checksums-Sha256:
 946da6502e7d527990f60aa96d9b33fb70f175ea4af688127c12344d335c299e 2131 
source-highlight_3.1.9-1.1.dsc
 81a76396b2183efa0bb6925c2696a02bf2dd3ef1b618bee459d086777e60b1ae 5404 
source-highlight_3.1.9-1.1.debian.tar.xz
 5f2d5041d9fc75fa4151893ca00108913d7dada7006177ba388aeb1b35c75220 6861 
source-highlight_3.1.9-1.1_source.buildinfo
Files:
 a98cf62d2a6c7096b29df118bbc22ae9 2131 devel optional 
source-highlight_3.1.9-1.1.dsc
 50d164ed9c7e106f92885f94c385d96b 5404 devel optional 
source-highlight_3.1.9-1.1.debian.tar.xz
 94ca1f545ed52f0356dcd13dd93fca12 6861 devel optional 
source-highlight_3.1.9-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE6Q8IiVReeMgqnedOryKDqnbirHsFAl5c3xEACgkQryKDqnbi
rHv9qxAAmEaXIIJuhKC8H1RflQ//o5EqEzSGn/PXNdyfCxyRkegr1vlqKLH5HL2C
mZ/Gwh97Ze3vyX1zvWKnsv/X+GGJIq12sxkoiXKgUqk3JErcNXwFCCspkhEXq7gw
rbPGXsvA/THsRr8ToEpVkPH/P4X3lnozusaLdpF6kkw9STSx1PG1GfSPbtGKlUZN
l0+E9hq9j/jfiQ/rBFHzOCL4Msc0AFrYQhm0IAqlW6EKD1pSWRVx7HhkgJtMOW51
5orMjSGoVM8WsA1VtE62q78OjbGMgvsEvl5sh8qp7WU/cBBmbWhYenHdYMWcNaEJ
xSyOrPIXiuJRWltCDgP6cX8GeoS1Ir/WrwBjlnEo826ZCN0l/Cb/f9owNfm33CZs
otn9y25SjB3e38zz/8mEhpIGNjKqfusOYTpfYqlAUtI58DLiM0MNAfh4Pq7GrJw8
O/RMtwFnCe3VnY58os2lYbvCA+BDys/GIGm58LCu/FXFVU79zmkfZzirzX8Ofrc5
8UCcUINAr4EZ+Mj9lzuBAmSPzzepkutGaBsCPdcaNMcAPHcLNfWuHDbzRiaFiO/z
XgYfcFngw2/gOmGW+tU6mM2mjDldHqP5eQEZr04Vt43eV51gLavk1LE1d72nswGc
pSGLTKMK2628UwnmqDfiLh06QY7+v1SYi010YB5a40enj2ubCX0=
=FsCb
-END PGP SIGNATURE End Message ---

Bug#953416: php-horde-javascriptminify-jsmin: needs binary upload

[Ivo De Decker]

package: src:php-horde-javascriptminify-jsmin
version: 1.0.2-6
severity: serious
tags: ftbfs

Hi,

The latest upload of php-horde-javascriptminify-jsmin to unstable has no
binaries, because the buildds are not building it (it is non-free).

If the binaries can be auto-built, the package should be whitelisted, as
described in
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd

If not, a binary upload must be done (note that binary uploads for sources in
contrib and non-free are allowed to migrate to testing).

Cheers,

Ivo

Bug#953233: marked as done (r-cran-gnm: autopkgtest regression: cannot open *.R: No such file)

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 10:49:31 +
with message-id 
and subject line Bug#953233: fixed in r-cran-gnm 1.1-1-2
has caused the Debian Bug report #953233,
regarding r-cran-gnm: autopkgtest regression: cannot open *.R: No such file
to be marked as done.

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

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


-- 
953233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-gnm
Version: 1.1-1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

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

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

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

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

Paul

[1] https://qa.debian.org/excuses.php?package=r-cran-gnm

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-gnm/4468587/log.gz

autopkgtest [21:14:46]: test run-unit-test: [---
BEGIN TEST *.R
/tmp/autopkgtest-lxc.a3kw6be3/downtmp/build.azZ/src/debian/tests/run-unit-test:
15: cannot open *.R: No such file
autopkgtest [21:14:46]: test run-unit-test: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-cran-gnm
Source-Version: 1.1-1-2
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-cran-gnm 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: Sat, 07 Mar 2020 07:31:37 +0100
Source: r-cran-gnm
Architecture: source
Version: 1.1-1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 953233
Changes:
 r-cran-gnm (1.1-1-2) unstable; urgency=medium
 .
   * Add missing testthat.R ; Test-Depends: r-cran-testthat; fix run-unit-test
 Closes: #953233
   * Add salsa-ci file (routine-update)
   * Set upstream metadata fields: Archive, Bug-Database, Bug-Submit,
 Repository, Repository-Browse.
   * Fix permissions
Checksums-Sha1:
 7782db7eb27b5d21a676645a29cb2d4c5ee79034 2109 r-cran-gnm_1.1-1-2.dsc
 88d3e7c3ebe61c1518566fa4f0705979245a750d 3936 r-cran-gnm_1.1-1-2.debian.tar.xz
 ffa13c1b2eb8b8ced24933cc46c293fbb78f22e8 9023 
r-cran-gnm_1.1-1-2_amd64.buildinfo
Checksums-Sha256:
 a5dd023f1f88bfe9ec702e7e2b91b9bae86aeb4970c970c8659fbb377666d40b 2109 
r-cran-gnm_1.1-1-2.dsc
 50b2ee2584c35060addfdceb6b3ab8ec51e4fb1b2ddbc06a8e6662ace0f41842 3936 
r-cran-gnm_1.1-1-2.debian.tar.xz
 939318846dd5bfa3ca8a571efc903c4945cb232ceeb9ef6cd20bfdc456a38a02 9023 
r-cran-gnm_1.1-1-2_amd64.buildinfo
Files:
 5012fa1429cd085ce6e3a06100b78a91 2109 gnu-r optional r-cran-gnm_1.1-1-2.dsc
 de17697e0bc72ccb08877a14f5e6e2f2 3936 gnu-r optional 
r-cran-gnm_1.1-1-2.debian.tar.xz
 57728121c283c637815fcbfdbc9e4b90 9023 gnu-r optional 
r-cran-gnm_1.1-1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl5mGTgRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFHGQ/+Oa+9PLtaIlOSIIjjWOTbIQBKsExut53v
48Fn8zZAblG2hxFadBNAq+90Y5kPDPzq+/e0vDMo5Mfo1cKUVn4WRKNE5dR8dtco
D+lfH390LYmghR0odl4l9Z+m8fKpjgtk8Pw5v2cVdXb3Uo2S1Psairw6uL4eo019
He05PKyh6LchVFd/qbP5b/iMqpqUI/YIjoEDdbNA6lIphm75M1G8UK106AAeMg0m
CZ13gx1ZfcqazrzL6xdSkqyk+j/VR0wxrlKAtckIhVA280/xRU/QeOiiwz4GihdQ
dE+tN5gjolVRtk0HlQtW10pKj5Ea+xHVPb6u86MSbWbdGIduEy2OAe2yXc+lgolm
G3eFI9Q3V4s5IHKmE2chu111VTM2CotNi6mRFUolE9yJZ8nShLWNZ8niq83Ef9FL

debian-bugs-rc@lists.debian.org

[Dragos Jarca]

Package: gitlab
Version: 12.6.8-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When updating to 12.6.8.1 I have two problems:

1. Could not find gem 'deckar01-task_list (= 2.2.1)' in any of the gem 
sources listed in your Gemfile.

solved by editing Gemfile:
gem 'deckar01-task_list', '2.3.1'


2. Top-level selectors may not contain the parent selector "&"

[5/5] Building fresh packages...
$ node ./scripts/frontend/postinstall.js
success Dependency postinstall check passed.
Done in 33.53s.
I, [2020-03-09T10:22:03.456949 #2195262]  INFO -- : Writing 
/usr/share/gitlab/public/assets/emoji_sprites-6971486a811b8e0f3f4d35a546ad581196c3e9763237883df27970853d4adeb5.css
I, [2020-03-09T10:22:03.467003 #2195262]  INFO -- : Writing 
/usr/share/gitlab/public/assets/emoji_sprites-6971486a811b8e0f3f4d35a546ad581196c3e9763237883df27970853d4adeb5.css.gz
I, [2020-03-09T10:22:04.360900 #2195262]  INFO -- : Writing 
/usr/share/gitlab/public/assets/errors-5d74e774f61c743fb068f7aa706b4b34656aa68c0cd5818948f01d81b716b072.css
I, [2020-03-09T10:22:04.362359 #2195262]  INFO -- : Writing 
/usr/share/gitlab/public/assets/errors-5d74e774f61c743fb068f7aa706b4b34656aa68c0cd5818948f01d81b716b072.css.gz
I, [2020-03-09T10:22:17.199709 #2195262]  INFO -- : Writing 
/usr/share/gitlab/public/assets/auth_buttons/salesforce_64-3eb1feb32f86b99e2650dcf3bf280a4c74fc07aaad97c88d4435b697b31613ed.png
I, [2020-03-09T10:22:17.728510 #2195262]  INFO -- : Writing 
/usr/share/gitlab/public/assets/cluster_app_logos/crossplane-9ceca67b2b9a8740daeacc45d783c2ba73b23b307a04688fcbafca5452b6795d.png
I, [2020-03-09T10:22:38.859234 #2195262]  INFO -- : Writing 
/usr/share/gitlab/public/assets/favicon-blue-d8d16ee4d0d7e663e28aab8a282483671bfc0d00dffe4244944dd960620e2629.png
I, [2020-03-09T10:22:38.900424 #2195262]  INFO -- : Writing 
/usr/share/gitlab/public/assets/favicon-f34ef73e6504fe12db99198e77bc12fb1b4b616b2b186f0e5b5bf3265c327fce.png
I, [2020-03-09T10:22:39.272530 #2195262]  INFO -- : Writing 
/usr/share/gitlab/public/assets/none-scheme-preview-dbdbc404f98ec1239cd8f4861ab537a3675832adad096d9cfa67fd274987c602.png
I, [2020-03-09T10:22:41.478022 #2195262]  INFO -- : Writing 
/usr/share/gitlab/public/assets/error_tracking/components/error_details-5e51d4ecbf7371053e0f23db7f16e27022bdc211d558ef2eb218fa47ffde477a.vue
I, [2020-03-09T10:29:57.745243 #2195262]  INFO -- : Writing 
/usr/share/gitlab/public/assets/vue_merge_request_widget/components/states/mr_widget_rebase-ee896f4e5e1025eb3af5ec10abe30b4276ee024c2e1fff8e316cf2fb46768b12.vue

rake aborted!
SassC::SyntaxError: Error: Top-level selectors may not contain the 
parent selector "&".

    on line 6:9 of node_modules/@gitlab/ui/src/scss/components.scss
    from line 13:9 of node_modules/@gitlab/ui/src/scss/gitlab_ui.scss
    from line 5:9 of app/assets/stylesheets/framework.scss
    from line 19:9 of app/assets/stylesheets/application.scss
>>   &.gl-avatar-identicon-bg#{$i} {

   --^
/usr/share/gitlab/node_modules/@gitlab/ui/src/scss/../components/base/avatar/avatar.scss:82
/usr/share/rubygems-integration/all/gems/sassc-2.0.1/lib/sassc/engine.rb:49:in 
`render'

Tasks: TOP => assets:precompile
(See full trace by running task with --trace)
dpkg: error processing package gitlab (--configure):
 installed gitlab package post-installation script subprocess returned 
error exit status 1

Errors were encountered while processing:
 gitlab
E: Sub-process /usr/bin/dpkg returned an error code (1)

Please help me to solve upgrade.

And a proposal: use 12.8 in experimental and whatever version you want 
in unstable.


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (700, 
'experimental'), (500, 'oldstable')

Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to C.UTF-8), LANGUAGE=C.UTF-8 (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

Versions of packages gitlab depends on:
ii  asciidoctor 2.0.10-2
ii  bc 1.07.1-2+b2
ii  bundler 2.1.4-1
ii  bzip2   1.0.8-2
ii  dbconfig-pgsql  2.0.13
ii  debconf [debconf-2.0]   1.5.73
ii  gitlab-common   12.6.8-1
ii  gitlab-workhorse 8.18.0+debian-1
ii  libjs-bootstrap4 [node-bootstrap] 4.4.1+dfsg1-1
ii  libjs-pdf 1.5.188+dfsg-1
ii  libjs-popper.js [node-popper.js] 1.16.0+ds2-1
ii  libjs-uglify    2.8.29-6
ii  lsb-base    11.1.0
ii  nginx   1.16.1-3
ii  nginx-extras [nginx]

Bug#953395: marked as done (python-tinyalign: FTBFS due to various build dependency issues)

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 09:33:58 +
with message-id 
and subject line Bug#953395: fixed in python-tinyalign 0.2-2
has caused the Debian Bug report #953395,
regarding python-tinyalign: FTBFS due to various build dependency issues
to be marked as done.

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

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


-- 
953395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953395
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-tinyalign
Version: 0.2-1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

Hi,

python-tinyalign currently fails to build from source due to multiple
build dependency issues. It requires python3-setuptools-scm and cython3
for setup.py and needs python3-all-dev because its code includes
Python.h.

In Ubuntu, the attached patch was applied to achieve the following:

  * Adjust build dependencies to fix FTBFS:
- Build-depend on python3-setuptools-scm and cython3.
- Build-depend on python3-all-dev instead of python3-all.

Thanks for considering the patch.

Logan

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

Kernel: Linux 5.4.0-14-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru python-tinyalign-0.2/debian/control 
python-tinyalign-0.2/debian/control
--- python-tinyalign-0.2/debian/control 2020-02-02 15:33:44.0 -0500
+++ python-tinyalign-0.2/debian/control 2020-03-08 18:22:07.0 -0400
@@ -3,10 +3,12 @@
 Priority: optional
 Maintainer: Debian Med Packaging Team 

 Uploaders: Steffen Moeller 
-Build-Depends: debhelper-compat (= 12),
+Build-Depends: cython3,
+   debhelper-compat (= 12),
dh-python,
python3-setuptools,
-   python3-all
+   python3-setuptools-scm,
+   python3-all-dev
 Standards-Version: 4.5.0
 Homepage: https://github.com/marcelm/tinyalign
 Vcs-Browser: https://salsa.debian.org/med-team/tinyalign
--- End Message ---
--- Begin Message ---
Source: python-tinyalign
Source-Version: 0.2-2
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-tinyalign 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, 09 Mar 2020 09:51:15 +0100
Source: python-tinyalign
Architecture: source
Version: 0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 953395
Changes:
 python-tinyalign (0.2-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Logan Rosen ]
   * Fix Build-Depends issues
 Closes: #953395
 .
   [ Andreas Tille ]
   * Remove trailing whitespace in debian/changelog (routine-update)
   * Do not parse d/changelog (routine-update)
   * Add salsa-ci file (routine-update)
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Binary package: Section: python
   * Hardening
   * No fiddling around with _version.py since python3-setuptools-scm
 is used now
Checksums-Sha1:
 8f81e27ca1f60dde8b44cfee2051488ef294d2c1 2078 python-tinyalign_0.2-2.dsc
 7fbe15d37b2c10513a8be1bf83bfac5c3bade5f6 2520 
python-tinyalign_0.2-2.debian.tar.xz
 245935cc25df7e76387bdfea638706cd4011a882 6961 
python-tinyalign_0.2-2_amd64.buildinfo
Checksums-Sha256:
 e05cb1e45fa7b63bdce571dc6ac6389f5d89e12662633d0ae4b5659ff64ef585 2078 
python-tinyalign_0.2-2.dsc
 17939d4fc66bedf87eb0de6d127f806d2fc3d75d1fa700af9aa08eba3d29235b 2520 
python-tinyalign_0.2-2.debian.tar.xz
 06868d1c3a09b0863ec0ae6388862cd1fb8d81508e1ffa599bb49a83f82d64cd 

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> unarchive 916654
Bug #916654 {Done: Tobias Grimm } [vdr-plugin-epgsearch] 
vdr-plugin-epgsearch 2.2.0+git20170817-2
Unarchived Bug 916654
> severity 916654 grave
Bug #916654 {Done: Tobias Grimm } [vdr-plugin-epgsearch] 
vdr-plugin-epgsearch 2.2.0+git20170817-2
Severity set to 'grave' from 'normal'
> forcemerge 916654 951009
Bug #916654 {Done: Tobias Grimm } [vdr-plugin-epgsearch] 
vdr-plugin-epgsearch 2.2.0+git20170817-2
Bug #951009 [vdr-plugin-epgsearch] vdr-plugin-epgsearch: starting vdr with 
vdr-plugin-epgsearch installed gives a segfault
Marked Bug as done
Marked as fixed in versions vdr-plugin-epgsearch/2.4.0+git20190507-2.
Merged 916654 951009
> thanks
Stopping processing here.

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

Bug#953010: marked as done (glade: Upgrade to 3.22.2 ( to work with libglib2 >= 2.63.2 ))

[Debian Bug Tracking System]

Your message dated Mon, 09 Mar 2020 09:19:09 +
with message-id 
and subject line Bug#953010: fixed in glade 3.22.2-1
has caused the Debian Bug report #953010,
regarding glade: Upgrade to 3.22.2  ( to work with libglib2 >= 2.63.2 )
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.)


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

Dear Maintainer,

   * What led up to the situation?

https://gitlab.gnome.org/GNOME/glade/issues/407

caused by glib >= 2.63.2

This is not an issue yet in Debian unstable / sid as the libglib2.0-0 version
is only 2.62.5-1. But, in experimental it is already 2.64.0-1. glade 3.22.1
breaks 100% if glib >= 2.63.2. Thanks.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Full details in upstream bug. Please refer
https://gitlab.gnome.org/GNOME/glade/issues/407

   * What was the outcome of this action?

Full details in upstream bug. Please refer
https://gitlab.gnome.org/GNOME/glade/issues/407

   * What outcome did you expect instead?

Full details in upstream bug. Please refer
https://gitlab.gnome.org/GNOME/glade/issues/407



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

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

Versions of packages glade depends on:
ii  libc6   2.29-10
ii  libcairo2   1.16.0-4
ii  libgdk-pixbuf2.0-0  2.40.0+dfsg-2
ii  libgladeui-2-6  3.22.1-4
ii  libglib2.0-02.62.5-1
ii  libgtk-3-0  3.24.14-1
ii  libpango-1.0-0  1.42.4-8

Versions of packages glade recommends:
ii  devhelp   3.34.0-1
ii  libgtk-3-dev  3.24.14-1

glade suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: glade
Source-Version: 3.22.2-1
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glade 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, 09 Mar 2020 08:38:22 +
Source: glade
Architecture: source
Version: 3.22.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 953010
Changes:
 glade (3.22.2-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream release
 - Fixes a property name for compatibility with GLib >= 2.64
   (Closes: #953010)
   * Move to debhelper-compat 12
   * Enable gnome dh sequence via dh-sequence-gnome virtual package
   * d/rules: Don't run gtk-doc for Architecture: any builds
   * Remove Conflicts/Replaces on libraries older than Debian 8 (oldoldstable)
   * d/tests: Add superficial autopkgtests
   * Use dh-sequence-gir, fixing missing dependency on gir1.2-gtk-3.0.
 This was detected by the new autopkgtest.
   * Set Rules-Requires-Root to no
   * d/not-installed: List files we are deliberately not installing (*.la)
   * d/rules: Configure dh_missing to FTBFS on unpackaged files
   * Standards-Version: 4.5.0 (no changes required)
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse
Checksums-Sha1:
 a771c1e953930a1cb42df178d532ca0bffc59ed3 3091 glade_3.22.2-1.dsc
 66f34413fc7796cb2c205a943af2d766fc47b2e4 3550008 glade_3.22.2.orig.tar.xz
 d0c65820fa3542b546dc16549f5bef006be99aa6 23528 glade_3.22.2-1.debian.tar.xz
 fb5496c58ff7643fe99ee3dfbcdac9238d890b70 16950 glade_3.22.2-1_source.buildinfo
Checksums-Sha256:
 5213bd433b7004e66aaf50b69d2f5ff2b8ccb6343ed5709c0305

Bug#952759: libsass-python 0.18.0 FTBFS with libsass 3.6.3, please upgrade to 0.19.4

[Frédéric Bonnard]

Hi Anthony

March 9, 2020 8:30 AM, "Anthony Fok"  wrote:

> Control: severity -1 serious
> Control: tags -1 + ftbfs sid
> Control: found -1 0.18.0-1
> 
> On Fri, 28 Feb 2020 17:38:13 +0100 Michael Fladischer  
> wrote:
> 
>> Source: libsass-python
>> Severity: wishlist
>> 
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>> 
>> Dear Maintainer,
>> 
>> right now there is 0.19.4 available from upstream. Would you consider 
>> uploading
>> an updated package to the archive?
>> 
>> Cheers,
>> Michael
> 
> Dear Frédéric,
> 
> I understand that the reason you uploaded libsass-python 0.18.0-1 in
> January 2020, even though 0.19.4 was already released November 2019,
> was to match the existing libsass 3.5.5-4 in Debian.

true

> That changed about 10 days ago on 2020-02-28 when I uploaded libsass
> 3.6.3-1 to Debian sid, and indeed, libsass-python 0.18.0-1 FTBFS with
> libsass 3.6.3-1 with the following errors:
> 
> FAIL: test_importer_returns_wrong_tuple_size_too_big
> (sasstests.CompileTestCase)
> FAIL: test_importer_returns_wrong_tuple_size_zero (sasstests.CompileTestCase)
> FAIL: test_importers_raises_exception (sasstests.CompileTestCase)
> FAIL: test_error (sasstests.CustomFunctionsTest)
> FAIL: test_raises (sasstests.CustomFunctionsTest)
> FAIL: test_returns_unknown_object (sasstests.CustomFunctionsTest)
> FAIL: test_warning (sasstests.CustomFunctionsTest)
> 
> which all go away with libsass-python 0.19.4.

expected at some point :)
I remember having checked in January the status of libsass which latest
version was still in experimental.

> So, it would be great if you could upload libsass-python 0.19.4-1. :-)
> 
> In case you are busy, since I have been fixing the ruby-sassc and
> node-node-sass packages which also FTBFS due to the libsass 3.6.3
> upgrade, I would be very happy to make an NMU upload of libsass-python
> 0.19.4-0.1, which I have prepared at my fork at
> https://salsa.debian.org/foka/libsass-python, and which I am happy to
> upload any time, with your permission of course.

It would be a shame to lose the work you've done already and that I didn't
do, so feel free to NMU libsass-python.

> Please let me know soon, especially because I would like to solve all
> remaining libsass 3.6.3 upgrade issues, hopefully in time for Ubuntu
> 20.04 LTS release.

No worries, thanks a bunch for all the work and kind mail.

Fred

> Many thanks!
> 
> Yours truly,
> 
> Anthony Fok

Processed: your mail

[Debian Bug Tracking System]

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

> retitle 952759 FTBFS with libsass 3.6.3, please upgrade to 0.19.4
Bug #952759 [src:libsass-python] libsass-python: New upstream release available
Changed Bug title to 'FTBFS with libsass 3.6.3, please upgrade to 0.19.4' from 
'libsass-python: New upstream release available'.
> thanks
Stopping processing here.

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

Processed: Re: libsass-python 0.18.0 FTBFS with libsass 3.6.3, please upgrade to 0.19.4

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #952759 [src:libsass-python] libsass-python: New upstream release available
Severity set to 'serious' from 'wishlist'
> tags -1 + ftbfs sid
Bug #952759 [src:libsass-python] libsass-python: New upstream release available
Added tag(s) sid and ftbfs.
> found -1 0.18.0-1
Bug #952759 [src:libsass-python] libsass-python: New upstream release available
Marked as found in versions libsass-python/0.18.0-1.

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