Bug#960495: transition: gdal

2020-06-11 Thread Sebastiaan Couwenberg
On 6/11/20 10:07 PM, Sebastian Ramacher wrote:
> On 2020-06-11 20:37:58 +0200, Sebastiaan Couwenberg wrote:
>> On 6/11/20 6:46 AM, Sebastiaan Couwenberg wrote:
>>> On 6/10/20 9:46 PM, Sebastian Ramacher wrote:
 Please go ahead with the upload to unstable.
>>>
>>> Thanks, gdal (3.1.0+dfsg-1) was just uploaded to unstable.
>>
>> The rebuild are looking good so far
>>
>> Please also binNMU postgis in experimental.
> 
> Scheduled.

Thanks.

Some packages were (re)built with the old gdal:

 * octave-mapping on mips64el
 * libgdal-grass  on armel, mips64el & mipsel

These need another binNMU.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



signature.asc
Description: OpenPGP digital signature


Bug#962660: marked as done (nmu: ros-geometry2_0.6.6-2)

2020-06-11 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jun 2020 00:25:56 +0200
with message-id <20200611222556.gc3203...@ramacher.at>
and subject line Re: Bug#962660: nmu: ros-geometry2_0.6.6-2
has caused the Debian Bug report #962660,
regarding nmu: ros-geometry2_0.6.6-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.)


-- 
962660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Hi,

Due to a mistake, librostime0d was uploaded with a new ABI without
bumping the Soname. This is fixed in librostime0d 0.7.2-2, but
ros-geometry2 on the buildds was built against 0.7.2-1.

Please rebuild ros-geometry2 against librostime0d 0.7.2-2. As
librostime0d has not been built yet on mips64el and alpha, you may want
to consider adding a dep-wait.

nmu ros-geometry2_0.6.6-2 . ANY . unstable . -m "Rebuild against fixed ABI of 
librostime0d"
dw ros-geometry2_0.6.6-2 . mips64el alpha . -m 'librostime0d (>= 0.7.2-2)'

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

Kernel: Linux 5.6.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
On 2020-06-11 14:51:32 +0200, Jochen Sprickerhof wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> Hi,
> 
> Due to a mistake, librostime0d was uploaded with a new ABI without
> bumping the Soname. This is fixed in librostime0d 0.7.2-2, but
> ros-geometry2 on the buildds was built against 0.7.2-1.
> 
> Please rebuild ros-geometry2 against librostime0d 0.7.2-2. As
> librostime0d has not been built yet on mips64el and alpha, you may want
> to consider adding a dep-wait.
> 
> nmu ros-geometry2_0.6.6-2 . ANY . unstable . -m "Rebuild against fixed ABI of 
> librostime0d"
> dw ros-geometry2_0.6.6-2 . mips64el alpha . -m 'librostime0d (>= 0.7.2-2)'

Scheduled

Cheers
-- 
Sebastian Ramacher


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


Bug#962674: Bug#962672: buster-pu: package ca-certificates/20200611~deb10u1

2020-06-11 Thread Adrian Bunk
Control: tags 962669 moreinfo

On Thu, Jun 11, 2020 at 08:18:38PM +0100, Adam D. Barratt wrote:
> On Thu, 2020-06-11 at 13:48 -0500, Michael Shuler wrote:
> > On 6/11/20 1:33 PM, Adam D. Barratt wrote:
> > > Just to confirm - will the certificates be automatically re-added
> > > (assuming that users have either the automatically trust or prompt
> > > options enabled)?
> > 
> > (stretch-pu report cc'ed, since same applies)
> > 
> > Excellent question. I believe we're going to hit #743339 "Previously 
> > removed certificates not added again". I had not found a reasonable
> > fix for that case in general, to preserve a user's selections. Maybe
> > a "good enough" fix will have to do for the specific ones added back.
> 
> OK.
> 
> In that case, how does this seem as an SUA text?
> 
> 
> The ca-certificates update described in SUA 182-1 removed some
> certificates issued by Symantec (under various brand names).
> Unfortunately, this removal led to a number of reported regressions.
> The affected certificates have therefore been reintroduced.
> 
> If you have already installed the package from SUA 182-1, and need to
> use the affected certificates, you may need to manually enable them by
> running "dpkg-reconfigure ca-certificates" as root.
> 

This does not work in various embedded scenarios.

Would it work to force-enable them in /etc/ca-certificates.conf
from the preinst when upgrading from old-version matching 20200601* ?

Unrelated to that, please keep the Python 2 -> 3 build dependency
change out of this emergency update.

> Regards,
> 
> Adam

cu
Adrian



Bug#960495: transition: gdal

2020-06-11 Thread Sebastian Ramacher
On 2020-06-11 20:37:58 +0200, Sebastiaan Couwenberg wrote:
> On 6/11/20 6:46 AM, Sebastiaan Couwenberg wrote:
> > On 6/10/20 9:46 PM, Sebastian Ramacher wrote:
> >> Please go ahead with the upload to unstable.
> > 
> > Thanks, gdal (3.1.0+dfsg-1) was just uploaded to unstable.
> 
> The rebuild are looking good so far
> 
> Please also binNMU postgis in experimental.

Scheduled.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature


Processed: Re: Bug#962674: stretch-pu: package ca-certificates/20200611~deb9u1

2020-06-11 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + confirmed
Bug #962674 [release.debian.org] stretch-pu: package 
ca-certificates/20200611~deb9u1
Added tag(s) confirmed.

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



Bug#962672: buster-pu: package ca-certificates/20200611~deb10u1

2020-06-11 Thread Adam D. Barratt
On Thu, 2020-06-11 at 13:48 -0500, Michael Shuler wrote:
> On 6/11/20 1:33 PM, Adam D. Barratt wrote:
> > Just to confirm - will the certificates be automatically re-added
> > (assuming that users have either the automatically trust or prompt
> > options enabled)?
> 
> (stretch-pu report cc'ed, since same applies)
> 
> Excellent question. I believe we're going to hit #743339 "Previously 
> removed certificates not added again". I had not found a reasonable
> fix for that case in general, to preserve a user's selections. Maybe
> a "good enough" fix will have to do for the specific ones added back.

OK.

In that case, how does this seem as an SUA text?


The ca-certificates update described in SUA 182-1 removed some
certificates issued by Symantec (under various brand names).
Unfortunately, this removal led to a number of reported regressions.
The affected certificates have therefore been reintroduced.

If you have already installed the package from SUA 182-1, and need to
use the affected certificates, you may need to manually enable them by
running "dpkg-reconfigure ca-certificates" as root.


Regards,

Adam



Bug#962674: stretch-pu: package ca-certificates/20200611~deb9u1

2020-06-11 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Thu, 2020-06-11 at 13:33 -0500, Michael Shuler wrote:
> #911289 resulted in a regression, and the explicitly blacklisted
> roots  have been reverted. One in particular, "GeoTrust Global CA",
> has caused  serious issues noted in #962596. The other reverted roots
> also remain in  the Mozilla CA bundle[0], so #911289 will require
> additional research  and be re-opened when uploaded.

As with the buster update, please go ahead; thanks.

Regards,

Adam



Bug#962672: buster-pu: package ca-certificates/20200611~deb10u1

2020-06-11 Thread Michael Shuler

On 6/11/20 1:33 PM, Adam D. Barratt wrote:

Just to confirm - will the certificates be automatically re-added
(assuming that users have either the automatically trust or prompt
options enabled)?


(stretch-pu report cc'ed, since same applies)

Excellent question. I believe we're going to hit #743339 "Previously 
removed certificates not added again". I had not found a reasonable fix 
for that case in general, to preserve a user's selections. Maybe a "good 
enough" fix will have to do for the specific ones added back.


Thanks for the question, patch ideas welcomed.

Michael



Bug#960495: transition: gdal

2020-06-11 Thread Sebastiaan Couwenberg
On 6/11/20 6:46 AM, Sebastiaan Couwenberg wrote:
> On 6/10/20 9:46 PM, Sebastian Ramacher wrote:
>> Please go ahead with the upload to unstable.
> 
> Thanks, gdal (3.1.0+dfsg-1) was just uploaded to unstable.

The rebuild are looking good so far

Please also binNMU postgis in experimental.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



signature.asc
Description: OpenPGP digital signature


Processed: Re: Bug#962672: buster-pu: package ca-certificates/20200611~deb10u1

2020-06-11 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + confirmed
Bug #962672 [release.debian.org] buster-pu: package 
ca-certificates/20200611~deb10u1
Added tag(s) confirmed.

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



Bug#962672: buster-pu: package ca-certificates/20200611~deb10u1

2020-06-11 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Thu, 2020-06-11 at 13:25 -0500, Michael Shuler wrote:
> #911289 resulted in a regression, and the explicitly blacklisted
> roots  have been reverted. One in particular, "GeoTrust Global CA",
> has caused  serious issues noted in #962596. The other reverted roots
> also remain in  the Mozilla CA bundle[0], so #911289 will require
> additional research  and be re-opened when uploaded.

Please feel free to get the new version uploaded. (It will need to be
in unstable before we push it to -updates, but they could be uploaded
at the same time.)

Just to confirm - will the certificates be automatically re-added
(assuming that users have either the automatically trust or prompt
options enabled)?

Regards,

Adam



Bug#962674: stretch-pu: package ca-certificates/20200611~deb9u1

2020-06-11 Thread Michael Shuler

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Hi release team,

#911289 resulted in a regression, and the explicitly blacklisted roots 
have been reverted. One in particular, "GeoTrust Global CA", has caused 
serious issues noted in #962596. The other reverted roots also remain in 
the Mozilla CA bundle[0], so #911289 will require additional research 
and be re-opened when uploaded.


stretch-proposed-updates and stretch-updates both got the previous upload.

I would like to upload ca-certificates_20200611~deb9u1 with the 
following changes:



ca-certificates (20200611~deb9u1) stretch; urgency=medium

   * Rebuild for stretch.
   * This oldstable release Closes: #962596, #942915

  -- Michael Shuler   Thu, 11 Jun 2020 09:11:56 
-0500


ca-certificates (20200611) unstable; urgency=medium

   * mozilla/blacklist:
 Revert Symantec CA blacklist (#911289). Closes: #962596
 The following root certificates were added back (+):
 + "GeoTrust Global CA"
 + "GeoTrust Primary Certification Authority"
 + "GeoTrust Primary Certification Authority - G2"
 + "GeoTrust Primary Certification Authority - G3"
 + "GeoTrust Universal CA"
 + "thawte Primary Root CA"
 + "thawte Primary Root CA - G2"
 + "thawte Primary Root CA - G3"
 + "VeriSign Class 3 Public Primary Certification Authority - G4"
 + "VeriSign Class 3 Public Primary Certification Authority - G5"
 + "VeriSign Universal Root Certification Authority"

   [ Gianfranco Costamagna ]
   * debian/{rules,control}:
 Merge Ubuntu patch from Matthias Klose to use Python3 during build.
 Closes: #942915

  -- Michael Shuler   Thu, 11 Jun 2020 08:38:00 
-0500



Source debdiff attached.

ca-certificates_20200611~deb9u1 uploaded to mentors[1], RFS will be 
submitted pending pu approval. Source can be fetched from mentors or the 
`debian-stretch` git branch, commit 
c151326dda72f703f7001f655e331b548eb1e411.


Binary debdiff files list matches unstable upload for 20200611 currently 
on mentors - RFS: #962669.


[0] 
https://ccadb-public.secure.force.com/mozilla/IncludedCACertificateReport

[1] https://mentors.debian.net/package/ca-certificates

Kind regards,
Michael

diffstat for ca-certificates-20200601~deb9u1 ca-certificates-20200611~deb9u1

 debian/changelog|   37 +++--
 debian/control  |8 
 mozilla/Makefile|2 +-
 mozilla/blacklist.txt   |   23 ---
 mozilla/certdata2pem.py |2 +-
 5 files changed, 33 insertions(+), 39 deletions(-)

diff -Nru ca-certificates-20200601~deb9u1/debian/changelog 
ca-certificates-20200611~deb9u1/debian/changelog
--- ca-certificates-20200601~deb9u1/debian/changelog2020-06-05 
11:52:50.0 -0500
+++ ca-certificates-20200611~deb9u1/debian/changelog2020-06-11 
09:11:56.0 -0500
@@ -1,16 +1,33 @@
-ca-certificates (20200601~deb9u1) stretch; urgency=medium
+ca-certificates (20200611~deb9u1) stretch; urgency=medium
 
   * Rebuild for stretch.
-  * Merge changes from 20200601
-- d/control
-  * This release updates the Mozilla CA bundle to 2.40, blacklists
-distrusted Symantec roots, and blacklists expired "AddTrust External
-Root". Closes: #956411, #955038, #911289, #961907
-  * Fix permissions on /usr/local/share/ca-certificates when using symlinks.
-Closes: #916833
-  * Remove email-only roots from mozilla trust store. Closes: #721976
+  * This oldstable release Closes: #962596, #942915
 
- -- Michael Shuler   Fri, 05 Jun 2020 11:52:50 -0500
+ -- Michael Shuler   Thu, 11 Jun 2020 09:11:56 -0500
+
+ca-certificates (20200611) unstable; urgency=medium
+
+  * mozilla/blacklist:
+Revert Symantec CA blacklist (#911289). Closes: #962596
+The following root certificates were added back (+):
++ "GeoTrust Global CA"
++ "GeoTrust Primary Certification Authority"
++ "GeoTrust Primary Certification Authority - G2"
++ "GeoTrust Primary Certification Authority - G3"
++ "GeoTrust Universal CA"
++ "thawte Primary Root CA"
++ "thawte Primary Root CA - G2"
++ "thawte Primary Root CA - G3"
++ "VeriSign Class 3 Public Primary Certification Authority - G4"
++ "VeriSign Class 3 Public Primary Certification Authority - G5"
++ "VeriSign Universal Root Certification Authority"
+
+  [ Gianfranco Costamagna ]
+  * debian/{rules,control}:
+Merge Ubuntu patch from Matthias Klose to use Python3 during build.
+Closes: #942915
+
+ -- Michael Shuler   Thu, 11 Jun 2020 08:38:00 -0500
 
 ca-certificates (20200601) unstable; urgency=medium
 
diff -Nru ca-certificates-20200601~deb9u1/debian/control 
ca-certificates-20200611~deb9u

Bug#962672: buster-pu: package ca-certificates/20200611~deb10u1

2020-06-11 Thread Michael Shuler

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

Hi release team,

#911289 resulted in a regression, and the explicitly blacklisted roots 
have been reverted. One in particular, "GeoTrust Global CA", has caused 
serious issues noted in #962596. The other reverted roots also remain in 
the Mozilla CA bundle[0], so #911289 will require additional research 
and be re-opened when uploaded.


buster-proposed-updates and buster-updates both got the previous upload.

I would like to upload ca-certificates_20200611~deb10u1 with the 
following changes:



ca-certificates (20200611~deb10u1) buster; urgency=medium

  * Rebuild for buster.
  * This stable release Closes: #962596, #942915

 -- Michael Shuler   Thu, 11 Jun 2020 09:07:27 
-0500


ca-certificates (20200611) unstable; urgency=medium

  * mozilla/blacklist:
Revert Symantec CA blacklist (#911289). Closes: #962596
The following root certificates were added back (+):
+ "GeoTrust Global CA"
+ "GeoTrust Primary Certification Authority"
+ "GeoTrust Primary Certification Authority - G2"
+ "GeoTrust Primary Certification Authority - G3"
+ "GeoTrust Universal CA"
+ "thawte Primary Root CA"
+ "thawte Primary Root CA - G2"
+ "thawte Primary Root CA - G3"
+ "VeriSign Class 3 Public Primary Certification Authority - G4"
+ "VeriSign Class 3 Public Primary Certification Authority - G5"
+ "VeriSign Universal Root Certification Authority"

  [ Gianfranco Costamagna ]
  * debian/{rules,control}:
Merge Ubuntu patch from Matthias Klose to use Python3 during build.
Closes: #942915

 -- Michael Shuler   Thu, 11 Jun 2020 08:38:00 
-0500



Source debdiff attached.

ca-certificates_20200611~deb10u1 uploaded to mentors[1], RFS will be 
submitted pending pu approval. Source can be fetched from mentors or the 
`debian-buster` git branch, commit 442fd47f4831483b72329e0df1f6260e4a91ab36.


Binary debdiff files list matches unstable upload for 20200611 currently 
on mentors - RFS: #962669.


[0] 
https://ccadb-public.secure.force.com/mozilla/IncludedCACertificateReport

[1] https://mentors.debian.net/package/ca-certificates

Kind regards,
Michael
diffstat for ca-certificates-20200601~deb10u1 ca-certificates-20200611~deb10u1

 debian/changelog|   34 +++---
 debian/control  |2 +-
 mozilla/Makefile|2 +-
 mozilla/blacklist.txt   |   23 ---
 mozilla/certdata2pem.py |2 +-
 5 files changed, 30 insertions(+), 33 deletions(-)

diff -Nru ca-certificates-20200601~deb10u1/debian/changelog 
ca-certificates-20200611~deb10u1/debian/changelog
--- ca-certificates-20200601~deb10u1/debian/changelog   2020-06-03 
13:09:34.0 -0500
+++ ca-certificates-20200611~deb10u1/debian/changelog   2020-06-11 
09:07:27.0 -0500
@@ -1,13 +1,33 @@
-ca-certificates (20200601~deb10u1) buster; urgency=medium
+ca-certificates (20200611~deb10u1) buster; urgency=medium
 
   * Rebuild for buster.
-  * Merge changes from 20200601
-- d/control; set d/gbp.conf branch to debian-buster
-  * This release updates the Mozilla CA bundle to 2.40, blacklists
-distrusted Symantec roots, and blacklists expired "AddTrust External
-Root". Closes: #956411, #955038, #911289, #961907
+  * This stable release Closes: #962596, #942915
 
- -- Michael Shuler   Wed, 03 Jun 2020 13:09:34 -0500
+ -- Michael Shuler   Thu, 11 Jun 2020 09:07:27 -0500
+
+ca-certificates (20200611) unstable; urgency=medium
+
+  * mozilla/blacklist:
+Revert Symantec CA blacklist (#911289). Closes: #962596
+The following root certificates were added back (+):
++ "GeoTrust Global CA"
++ "GeoTrust Primary Certification Authority"
++ "GeoTrust Primary Certification Authority - G2"
++ "GeoTrust Primary Certification Authority - G3"
++ "GeoTrust Universal CA"
++ "thawte Primary Root CA"
++ "thawte Primary Root CA - G2"
++ "thawte Primary Root CA - G3"
++ "VeriSign Class 3 Public Primary Certification Authority - G4"
++ "VeriSign Class 3 Public Primary Certification Authority - G5"
++ "VeriSign Universal Root Certification Authority"
+
+  [ Gianfranco Costamagna ]
+  * debian/{rules,control}:
+Merge Ubuntu patch from Matthias Klose to use Python3 during build.
+Closes: #942915
+
+ -- Michael Shuler   Thu, 11 Jun 2020 08:38:00 -0500
 
 ca-certificates (20200601) unstable; urgency=medium
 
diff -Nru ca-certificates-20200601~deb10u1/debian/control 
ca-certificates-20200611~deb10u1/debian/control
--- ca-certificates-20200601~deb10u1/debian/control 2020-06-03 
13:09:34.0 -0500
+++ ca-certificates-20200611~deb10u1/debian/control 2

Bug#961979: transition: libwebsockets

2020-06-11 Thread GCS
On Thu, Jun 11, 2020 at 4:10 PM Paul Gevers  wrote:
> On 11-06-2020 13:46, László Böszörményi (GCS) wrote:
> > Basically the transition is over.
>
> Only when everything is in testing.
 Indeed, that's what I meant it's (only) basically over. The migration
of packages (when this transition can be closed) only depends on time
now.

Sorry for the confusion,
Laszlo/GCS



Bug#961979: transition: libwebsockets

2020-06-11 Thread Paul Gevers
Hi László,

On 11-06-2020 13:46, László Böszörményi (GCS) wrote:
> Basically the transition is over.

Only when everything is in testing.

Paul



signature.asc
Description: OpenPGP digital signature


Bug#962660: nmu: ros-geometry2_0.6.6-2

2020-06-11 Thread Jochen Sprickerhof
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Hi,

Due to a mistake, librostime0d was uploaded with a new ABI without
bumping the Soname. This is fixed in librostime0d 0.7.2-2, but
ros-geometry2 on the buildds was built against 0.7.2-1.

Please rebuild ros-geometry2 against librostime0d 0.7.2-2. As
librostime0d has not been built yet on mips64el and alpha, you may want
to consider adding a dep-wait.

nmu ros-geometry2_0.6.6-2 . ANY . unstable . -m "Rebuild against fixed ABI of 
librostime0d"
dw ros-geometry2_0.6.6-2 . mips64el alpha . -m 'librostime0d (>= 0.7.2-2)'

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

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



Bug#962659: transition: xmltooling

2020-06-11 Thread Ferenc Wágner
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Dear Release Team,

The 3.1 release of the Shibboleth software stack changed the ABI and API
of all the components.  It's pretty self-contained in Debian, though.
The affected packages (xmltooling, opensaml, shibboleth-sp and
shibboleth-resolver) are all in experimental now, and moonshot-gss-eap
will only need a binnmu to complete the transition.

We're ready to upload to unstable if you agree.

Ben file:

title = "shibboleth31";
is_affected = .depends ~ "libxmltooling8" | .depends ~ "libsaml10" | .depends ~ 
"libshibsp8" | .depends ~ "libshibresolver2" | .depends ~ "libxmltooling9" | 
.depends ~ "libsaml11" | .depends ~ "libshibsp9" | .depends ~ 
"libshibresolver3";
is_good = .depends ~ "libxmltooling9" | .depends ~ "libsaml11" | .depends ~ 
"libshibsp9" | .depends ~ "libshibresolver3";
is_bad = .depends ~ "libxmltooling8" | .depends ~ "libsaml10" | .depends ~ 
"libshibsp8" | .depends ~ "libshibresolver2";

Thanks,
the Shibboleth packaging team.



Processed: block 960495 with 949027

2020-06-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 960495 with 949027
Bug #960495 [release.debian.org] transition: gdal
960495 was blocked by: 960369 953138 962641
960495 was not blocking any bugs.
Added blocking bug(s) of 960495: 949027
> thanks
Stopping processing here.

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



Bug#961979: transition: libwebsockets

2020-06-11 Thread GCS
On Thu, Jun 11, 2020 at 9:02 AM László Böszörményi (GCS)  
wrote:
> On Wed, Jun 10, 2020 at 9:51 PM Sebastian Ramacher  
> wrote:
> > Please go ahead with the upload to unstable.
>  Thanks, 4.0.15-2 was uploaded, built and installed on most architectures.
 Then all reverse dependencies are (re-)built and installed on all
primary architectures.
Basically the transition is over.

Thanks,
Laszlo/GCS



Bug#960193: ICU rebuilds

2020-06-11 Thread Paul Gevers
Hi Peter,

On 10-06-2020 21:54, Peter wrote:
> Will there be a full rebuild of the archive for Bullseye anyway?

No, we only do rebuilds to reduce the number of copies of source
packages that are needed due to Built-Using. All other rebuilds come
from source uploads or regular binNMU's for transitions. One reason why
we can't do this is because the infrastructure doesn't handle binNMU's
of arch:all correctly.

Paul



signature.asc
Description: OpenPGP digital signature


Bug#961979: transition: libwebsockets

2020-06-11 Thread GCS
On Wed, Jun 10, 2020 at 9:51 PM Sebastian Ramacher  wrote:
> > Small transition with four affected packages: driftnet, forked-daapd,
> > janus and mosquitto.
> > All build fine with the libwebsockets 4.0.13 version in experimental.
>
> Please go ahead with the upload to unstable.
 Thanks, 4.0.15-2 was uploaded, built and installed on most architectures.

Cheers,
Laszlo/GCS