Processed: Re: Bug#990214: unblock: dovecot-fts-xapian/1.4.9a-1

2021-07-05 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 - moreinfo
Bug #990214 [release.debian.org] unblock: dovecot-fts-xapian/1.4.9a-1
Removed tag(s) moreinfo.

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

Bug#990214: unblock: dovecot-fts-xapian/1.4.9a-1

2021-07-05 Thread Joe Nahmias 
Control: tags -1 - moreinfo

Hello,

On Sun, Jul 04, 2021 at 10:17:31PM +0200, Sebastian Ramacher wrote:
> Control: tags -1 moreinfo confirmed
> 
> Assuming that the upload happens soon, please go ahead and remove the
> moreinfo tag once the new version is available in unstable.

Thanks for reviewing. I've added one additional patch cherry-picked from
upstream to fix a crash when reindexing, see attached. Uploaded to
unstable.

--Joe

Bug#990743: unblock: ncbi-entrez-direct/14.6.20210224+dfsg-4

2021-07-05 Thread Aaron M. Ucko 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

[ Introduction / Reason ]
I would like to issue a new ncbi-entrez-direct upload (patch attached)
adjusting two wrapper scripts to account fully for their wrappees'
repertoire of options, or at minimum acknowledging that NCBI's efetch
accepts -docsum as shorthand for -format docsum for the sake of
ncbi-blast+'s get_species_taxids script.
(https://bugs.debian.org/990741 has more details.)

[ Impact ]
Without this patch, on systems with ncbi-entrez-direct and acedb-other
both installed, some legitimate usage of efetch intended to pick up
NCBI's version will yield warnings; likewise for einfo with epub-utils
installed alongside ncbi-entrez-direct.  (In some corner cases, these
wrapper scripts might even wind up running the wrong efetch or einfo,
though they should at least warn about doing so.)

[ Tests ]
#990741 has an example of the current misbehavior; with this patch in
place, the only diagnostics should be the single WARNING: line from
NCBI's efetch itself, which is entirely safe to disregard.

[ Risks ]
AFAICT, this patch should not affect any command lines intended for
acedb-other's efetch or epub-utils's einfo, but if you want to be
extra cautious, I can limit it to adding -docsum for efetch for now.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
I am holding off on uploading anything pending feedback on whether to
go forward with the full patch or a scaled-down version that only adds
an acknowledgment of the -docsum shorthand.

Thanks!

unblock ncbi-entrez-direct/14.6.20210224+dfsg-4
diff --git a/debian/changelog b/debian/changelog
index f8b2667..5bb4c46 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+ncbi-entrez-direct (14.6.20210224+dfsg-4) UNRELEASED; urgency=medium
+
+  * debian/{efetch,einfo}: Refresh %ncbi_supported, taking care to include
+undocumented options.  (In particular, ncbi-blast+'s
+get_species_taxids uses efetch's undocumented -docsum shorthand.)
+(Closes: #990741.)
+
+ -- Aaron M. Ucko   Mon, 05 Jul 2021 22:12:10 -0400
+
 ncbi-entrez-direct (14.6.20210224+dfsg-3) unstable; urgency=medium
 
   * debian/man/eblast.1: Extend deprecation notice to eblast.
diff --git a/debian/efetch b/debian/efetch
index 603bdaa..79a2726 100755
--- a/debian/efetch
+++ b/debian/efetch
@@ -28,6 +28,7 @@ my %ncbi_supported = (
 'id'  => 's',
 'input'   => 's',
 'format'  => 's',
+'docsum'  => undef,
 'style'   => 's',
 'mode'=> 's',
 'seq_start'   => 'i',
@@ -38,10 +39,14 @@ my %ncbi_supported = (
 'complexity'  => 'i',
 'chr_start'   => 'i',
 'chr_stop'=> 'i',
+'showgi'  => undef,
 'extend'  => 'i',
 'extrafeat'   => 'i',
+'showgaps'=> undef,
+'show-gaps'   => undef,
 'start'   => 'i',
 'stop'=> 'i',
+'api_key' => 's',
 'raw' => undef,
 'json'=> undef,
 'nogi'=> undef,
@@ -49,14 +54,26 @@ my %ncbi_supported = (
 'tool'=> 's',
 'pipe'=> undef,
 'help'=> undef,
+'example' => undef,
+'examples'=> undef,
+'error'   => undef,
+'errors'  => undef,
 'silent'  => undef,
 'verbose' => undef,
 'debug'   => undef,
+'oldmode' => undef,
+'newmode' => undef,
 'log' => undef,
+'compact' => undef,
 'http'=> 's',
 'https'   => 's',
 'alias'   => 's',
-'base'=> 's');
+'base'=> 's',
+'web' => 's',
+'step'=> 'i',
+'label'   => 's',
+'timer'   => undef,
+'version' => undef);
 
 my %ncbi_abbrev = ();
 {
diff --git a/debian/einfo b/debian/einfo
index 570c088..a4d202a 100755
--- a/debian/einfo
+++ b/debian/einfo
@@ -26,19 +26,36 @@ my $epub_keys  = 't';
 my %ncbi_supported = (
 'db'  => 's',
 'dbs' => undef,
+'field'   => undef,
 'fields'  => undef,
+'link'=> undef,
 'links'   => undef,
+'test'=> undef,
+'tests'   => undef,
+'api_key' => undef,
 'email'   => 's',
 'tool'=> 's',
+'repeat'  => undef,
+'repeats' => undef,
+'error'   => undef,
+'errors'  => undef,
 'help'=> undef,
 'silent'  => undef,
 'verbose' => undef,
 'debug'   => undef,
+'oldmode' => undef,
+'newmode' => undef,
 'log' => undef,
+'compact' => undef,
 'http'=> 's',
 'https'   => 's',
 'alias'   => 's',
-'base'=> 's');
+'base'=> 's',
+'web' => 's',
+'step'=> 'i',
+'label'   => 's',
+'timer'   =>

Bug#990739: buster-pu: package iptables-netflow/2.3-5+deb10u1

2021-07-05 Thread Axel Beckert 
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: a...@debian.org, car...@debian.org

Hi,

an API change in the Linux kernel 4.19.194-1 uploaded with the Buster
10.10 stable minor update caused a regression in
iptables-netflow-dkms/2.3-5 built from the iptables-netflow source
package. The upstream API change happened in 4.19.191:

- modules: mark ref_module static

Relevant bug reports:

* Debian: https://bugs.debian.org/990123
* Upstream: https://github.com/aabc/ipt-netflow/issues/177

I would like to upload an updated package of iptables-netflow to
buster-proposed-updates which cherry-picks two upstream patches (see
below under [Changes] for details) which fix the issue initially and
then also for updated stable kernel lines like those in Buster.

[ Reason ]

Linux upstream has been backporting a change from kernel 5.9 to stable
kernel releases which makes sure that kernel modules which claim to be
GPL licensed and use _GPL exports, can no more depend on symbols from
non-GPL modules. This is has been solved by marking a function static,
i.e. no more being usable by kernel modules.

The Debian kernel team stated in  that it's unlikely that Linux kernel
upstream will revert the patches and they also stated that it's
unlikely that Debian's linux kernel will divert from upstream at this
point.

Context about this issue:

https://lore.kernel.org/lkml/20200730061027.29472-1-...@lst.de/
https://lore.kernel.org/stable/ymxnxqzcp0g1f...@kroah.com/

(Thanks to Salvatore Bonaccorso of the Debian kernel team for these
links and further reviews and suggestions on this issue!)

[ Impact ]

The package is currently no more working after a reboot into a current
Buster 10.10 kernel as the DKMS kernel module fails to build with
current kernel headers (see #990123). It is currently still usable
with kernels before 4.19.194-1.

It will also no more compile with non-debian kernels of the stable
kernel lines 4.14 (version 4.14.233 and above) and 5.4 (version 5.4.11
and above). (Compilation of kernels above 5.9rc1 never worked with the
version in Buster.)

[ Tests ]

The .deb as generated when applying the debdiff below runs in
production for about 1.5 weeks on two of my netflow generating
servers, first with kernel version 4.19.194-1, later with kernel
version 4.19.194-2, both with ABI 4.19.0-17-amd64.

I also tried installing it (aka compiling the DKMS module) on a box
which was still running linux-image-4.19.0-12-amd64 (package version
4.19.152-1 + headers) from October 2020. Since also further Debian
kernels were installed, I also successfully tested its compilation
against linux-{image,headers}-4.19.0-14-amd64 (package version
4.19.171-2).

No issues have been observed so far. Functionality is as expected.

[ Risks and Expected Regressions ]

The upstream patch https://github.com/aabc/ipt-netflow/commit/352cdb28
mostly removes CPP "#if LINUX_VERSION_CODE >= KERNEL_VERSION(…)"
blocks containing legacy code not needed for more modern kernels and
enables the modern code also for older releases.

As I read that upstream commit, now this kernel module will no more
compile with (vanilla) kernels before 2.6.35 which seems to have
introduced the functionality which is now used instead of the function
made static in 5.9.0, 4.19.191 and other recent stable kernel
releases. (I though didn't test any other kernels than those in Debian
Buster. For older kernels than 4.19.194-1 I just tested if the DKMS
module still compiles, not if it still works as before.)

Since upstream's approach also compiled against older stable kernels
than those affected by #990123 I took upstream's approach instead of
making those "#if LINUX_VERSION_CODE >= KERNEL_VERSION(…)" checks even
more complex by adding further constraints to list all the updated
stable kernels mentioned above.

[ Checklist ]
  [√] *all* changes are documented in the d/changelog
  [√] I reviewed all changes and I approve them
  [√] attach debdiff against the package in (old)stable
  [*] the issue is verified as fixed in unstable

Footnotes: * = Patch 1 (cherry-picked adfc6318) is already included in
   Debian Unstable and Bullseye as a cherry-picked patch
   from the currently most recent upstream 2.6 release. It
   fixes the same issue for kernels 5.9 and above since
   Debian package version 2.5.1-1, but its CPP
   conditionals were not prepared for that "mark
   ref_module static" change being backported to stable
   kernel lines.

   Patch 2 (cherry-picked 352cdb28) is not included in
   Debian Unstable and Bullseye as it is only necessary
   for kernels older than those in Unstable/Bullseye which
   got that change from 5.9 backported.

[ Changes ]

The proposed packages fixes #990123 by cherry-picking two upstream
commits in the same part of the code (I didn't want

Bug#990736: unblock: soapyosmo/0.2.5-4

2021-07-05 Thread tony mancill 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Dear Release Team,

Please consider an unblock for package soapyosmo.

[ Reason ]
This upload addresses an RC bug in the soapyosmo package:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990240 by configuring
it to build against boost::chrono.

[ Impact ]
#990240 will transitively impact 19 other packages via
autoremovals as per the mailing that went out on July 1st.

[ Tests ]
The updated soapyosmo was installed locally and confirmed to address
this error when starting sdrangelove:

> [ERROR] 
> SoapySDR::loadModule(/usr/lib/x86_64-linux-gnu/SoapySDR/modules0.7/librfspaceSupport.so)
>   dlopen() failed: 
> /usr/lib/x86_64-linux-gnu/SoapySDR/modules0.7/librfspaceSupport.so: undefined 
> symbol: _ZN5boost6chrono12steady_clock3nowEv

[ Risks ]
The fix is trivial.  It merely configures the build to make use of
libboost-chrono-dev.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
This unblock alone will not address the crash in sdrangelove initially
reported #990240; see the discussion in the bug report for more details
and discussion by the Debian Ham team.  However, it could address and
prevent other brokenness related to soapyosmo in Bullseye.  That is,
soapyosmo should depend upon 

Thank you for considering this unblock.

Cheers,
tony

unblock soapyosmo/0.2.5-4
diff -Nru soapyosmo-0.2.5/debian/changelog soapyosmo-0.2.5/debian/changelog
--- soapyosmo-0.2.5/debian/changelog2019-10-20 08:31:08.0 -0700
+++ soapyosmo-0.2.5/debian/changelog2021-07-03 09:31:09.0 -0700
@@ -1,3 +1,10 @@
+soapyosmo (0.2.5-4) unstable; urgency=medium
+
+  * Team upload.
+  * Add boost::chrono to build (Closes: #990240)
+
+ -- tony mancill   Sat, 03 Jul 2021 09:31:09 -0700
+
 soapyosmo (0.2.5-3) unstable; urgency=medium
 
   * Upload to unstable
diff -Nru soapyosmo-0.2.5/debian/control soapyosmo-0.2.5/debian/control
--- soapyosmo-0.2.5/debian/control  2019-10-20 08:29:52.0 -0700
+++ soapyosmo-0.2.5/debian/control  2021-07-03 09:31:09.0 -0700
@@ -7,6 +7,7 @@
 debhelper (>= 12),
 cmake,
 libboost-dev,
+libboost-chrono-dev,
 libboost-system-dev,
 libboost-thread-dev,
 libosmosdr-dev,
diff -Nru soapyosmo-0.2.5/debian/patches/boost_chrono.patch 
soapyosmo-0.2.5/debian/patches/boost_chrono.patch
--- soapyosmo-0.2.5/debian/patches/boost_chrono.patch   1969-12-31 
16:00:00.0 -0800
+++ soapyosmo-0.2.5/debian/patches/boost_chrono.patch   2021-07-03 
09:31:09.0 -0700
@@ -0,0 +1,10 @@
+--- a/CMakeLists.txt
 b/CMakeLists.txt
+@@ -102,6 +102,7 @@
+ SET(BOOST_REQUIRED_COMPONENTS
+ thread
+ system
++chrono
+ )
+ 
+ if(UNIX AND NOT BOOST_ROOT AND EXISTS "/usr/lib64")
diff -Nru soapyosmo-0.2.5/debian/patches/series 
soapyosmo-0.2.5/debian/patches/series
--- soapyosmo-0.2.5/debian/patches/series   2019-09-22 18:12:05.0 
-0700
+++ soapyosmo-0.2.5/debian/patches/series   2021-07-03 09:31:09.0 
-0700
@@ -1 +1,2 @@
 internal-common-library
+boost_chrono.patch
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in second .changes but not in first
-
-rw-r--r--  root/root   
/usr/lib/debug/.build-id/02/3648071dde21b174c4010728faa35a85d25c68.debug
-rw-r--r--  root/root   
/usr/lib/debug/.build-id/4c/6fdb3aa8aaf3fd6894d57bb164d12126fe4d87.debug
-rw-r--r--  root/root   
/usr/lib/debug/.build-id/d3/bb600eb81e7d8a5f97b54989a5a2f70df62f71.debug

Files in first .changes but not in second
-
-rw-r--r--  root/root   
/usr/lib/debug/.build-id/30/652528145c6ca4e902b0aaece5708b43cb256a.debug
-rw-r--r--  root/root   
/usr/lib/debug/.build-id/36/6254bfc9b5da96d62d80824e1a7deae0b8ec35.debug
-rw-r--r--  root/root   
/usr/lib/debug/.build-id/80/1a1744f1e2b0a3eb110ac0767ccd56e40f5618.debug

Control files of package soapyosmo-common0.7: lines which differ (wdiff format)
---
Version: [-0.2.5-3-] {+0.2.5-4+}

Control files of package soapyosmo-common0.7-dbgsym: lines which differ (wdiff 
format)
--
Depends: soapyosmo-common0.7 (= [-0.2.5-3)-] {+0.2.5-4)+}
Version: [-0.2.5-3-] {+0.2.5-4+}

Control files of package soapysdr-module-mirisdr: lines which differ (wdiff 
format)
---
Depends: soapysdr0.7-module-mirisdr, soapyosmo-common0.7 (= [-0.2.5-3)-] 
{+0.2.5-4)+}
Version: [-0.2.5-3-] {+0.2.5-4+}

Control files of package soapysdr-module-osmosdr: lines which differ (wdiff 
format)

Processed: Re: Bug#990696: unblock: netselect/0.3.ds1-29

2021-07-05 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 moreinfo confirmed
Bug #990696 [release.debian.org] unblock: netselect/0.3.ds1-29
Added tag(s) moreinfo and confirmed.

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

Bug#990696: unblock: netselect/0.3.ds1-29

2021-07-05 Thread Sebastian Ramacher 
Control: tags -1 moreinfo confirmed

On 2021-07-05 00:20:02 +0200, Javier Fernández-Sanguino Peña wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package netselect
> 
> [ Reason ]
> 
> Netselect-apt is not able to properly parse the URLs in the mirror list
> available in the Debian website. This version fixes the bug in parsing which
> makes it work again.
> 
> [ Impact ]
> If the unblock is not implemented users will not be able to use netselect-apt
> 
> [ Tests ]
> I have run manually tests in my unstable system to confi
> 
> [ Risks ]
> The change is very simple. This is a package which is used by a small number 
> of
> users. 
> 
> [ Checklist ]
>   [x] all changes are documented in the d/changelog
>   [x] I reviewed all changes and I approve them
>   [x] attach debdiff against the package in testing
> 
> unblock netselect/0.3.ds1-29

ACK, please remove the moreinfo tag once the package is available in
unstable.

Cheers

> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: i386 (i686)
> 
> Kernel: Linux 5.10.0-1-686-pae (SMP w/4 CPU threads)
> Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled

> diff -Nru netselect-0.3.ds1/debian/changelog 
> netselect-0.3.ds1/debian/changelog
> --- netselect-0.3.ds1/debian/changelog2021-07-05 00:14:53.0 
> +0200
> +++ netselect-0.3.ds1/debian/changelog2021-07-04 23:04:35.0 
> +0200
> @@ -1,3 +1,14 @@
> +netselect (0.3.ds1-29) unstable; urgency=high
> +
> +  * netselect-apt:
> +- Fix bug that makes it output some hosts with negative value (Closes: 
> 920907)
> +- Fix bug in the Pelr parsing which prevented it from processing properly
> +  the mirrors listed in the Debian website (Closes: 989674)
> +  * debian/control: Move curl to depends as it is required by netselect-apt
> +   (Closes: 788793)
> +
> + -- Javier Fernández-Sanguino Peña   Sun, 04 Jul 2021 
> 23:04:35 +0200
> +
>  netselect (0.3.ds1-28) unstable; urgency=medium
>  
>* Use debhelper files properly to relocation binaries and
> diff -Nru netselect-0.3.ds1/debian/control netselect-0.3.ds1/debian/control
> --- netselect-0.3.ds1/debian/control  2021-07-05 00:14:53.0 +0200
> +++ netselect-0.3.ds1/debian/control  2021-07-04 23:04:35.0 +0200
> @@ -22,8 +22,7 @@
>  
>  Package: netselect-apt
>  Architecture: all
> -Depends: wget, netselect (>= 0.3.ds1-17), ${misc:Depends}
> -Recommends: curl
> +Depends: wget, netselect (>= 0.3.ds1-17), curl, ${misc:Depends}
>  Enhances: apt
>  Suggests: dpkg-dev
>  Description: speed tester for choosing a fast Debian mirror
> diff -Nru netselect-0.3.ds1/netselect-apt netselect-0.3.ds1/netselect-apt
> --- netselect-0.3.ds1/netselect-apt   2021-07-05 00:14:53.0 +0200
> +++ netselect-0.3.ds1/netselect-apt   2021-07-04 23:04:35.0 +0200
> @@ -35,7 +35,7 @@
>  # Default distribution
>  distro="stable"
>  # Default protocol
> -protocol="HTTP"
> +protocol="http"
>  # Number of fastest hosts that will be validated
>  test_hosts="10"
>  # URL where the mirror list is retrieved from 
> @@ -120,7 +120,7 @@
>  
>  # Second test: do we have the test file we are looking for?
>  [ -n "$DEBUG" ] && log "DEBUG: Checking if the file '$test_file' is 
> available in site"
> -temp=`tempfile`
> +temp=`mktemp`
>  [ ! -e "$temp" ] && return 0 # Return without error if we cannot create
>   # a temporary file
>  curl -m 2 -q -s "$host/$test_file"  >$temp 2>&1
> @@ -156,12 +156,14 @@
>   SEARCH="$1"
>   PROTO="$2"
>  hosts=$(cat "$infile" \
> - | perl -n -e '
> +   | perl -n -e '
> +use warnings;
> +use strict;
>   $/="";
> -$country_name  = ".*";
> -$country_iso  = "..";
> -$country = "'"$country"'";
> -$my_country = 1;
> +my $country_name  = ".*";
> +my $country_iso  = "..";
> +my $country = "'"$country"'";
> +my $my_country = 1;
>  if ( $country ne "" ) {
>$my_country = 0;
>if ( $country =~ /^\w{2}$/ ) {
> @@ -184,7 +186,7 @@
>   next if $_ !~ /Site:/;
>   if( ( /Includes architectures:.+'"$arch"'.+/i ||
>   $_ !~ /Includes architectures:/ 
> ) &&
> - 
> m@'"$SEARCH"':.*@i && $my_country == 1
> +   
>

Bug#990530: marked as done (unblock: horizon/18.6.2-4 and all of its plugins)

2021-07-05 Thread Debian Bug Tracking System 
Your message dated Mon, 5 Jul 2021 23:50:26 +0200
with message-id 
and subject line Re: Bug#990530: unblock: horizon/18.6.2-4 and all of its 
plugins
has caused the Debian Bug report #990530,
regarding unblock: horizon/18.6.2-4 and all of its plugins
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.)


-- 
990530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990530
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: unblock

Dear release team,

As per the discussion at:
https://bugs.debian.org/988188

I have uploaded an update of Horizon and all of its plugins.
The debdiff for Horizon is attached.

Below, you'll find (inline) a debdiff for cloudkitty-dashboard showing
what I am updaging in a typical Horizon plugin. I don't think it's necessary
to provide a debdiff for each individual plugin, as they all look the
same. However, please note that for heat-dashboard, I also added this
patch (to warn users that this part of the plugin is broken on Chrome):

--- 
heat-dashboard-4.0.0.orig/heat_dashboard/content/template_generator/templates/template_generator/index.html
+++ 
heat-dashboard-4.0.0/heat_dashboard/content/template_generator/templates/template_generator/index.html
@@ -5,6 +5,7 @@
 {% block page_header %}
 
 {% trans "Template Generator" %}
+(Not compatible with Chrome based browsers)
 {% trans "Please drag and drop resource icons into center canvas to 
define resource for template." %}
 
 {% endblock %}

and also, for sahara-dashboard, I removed the Breaks+Replaces:
python-sahara-dashboard, as this is obsolete since the Python 2
version of this Horizon plugin doesn't exist in Buster (so the
transition is over). Otherwise, all plugins have recieved similar
updates.

Here's the list of unblocks:

unblock horizon/3:18.6.2-4
unblock cloudkitty-dashboard/11.0.0-2
designate-dashboard/11.0.0-2
freezer-web-ui/9.0.0-2
heat-dashboard/4.0.0-2
ironic-ui/4.2.0-3
magnum-ui/7.0.0-2
manila-ui/4.0.0-2
mistral-dashboard/11.0.0-2
murano-dashboard/1:10.0.0-2
neutron-vpnaas-dashboard/3.0.0-2
octavia-dashboard/6.0.0-2
sahara-dashboard/13.0.0-2
senlin-dashboard/2.0.0-2
trove-dashboard/15.0.0-2
vitrage-dashboard/3.2.0-3
watcher-dashboard/4.0.0-2
zaqar-ui/8.0.0-2

A typical plugin fix looks like this (here, cloudkitty-dashboard):

diff --git a/debian/changelog b/debian/changelog
index f08809f..adaf71e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+cloudkitty-dashboard (11.0.0-2) unstable; urgency=medium
+
+  * Fix installation of files in the enable folder.
+
+ -- Thomas Goirand   Wed, 30 Jun 2021 11:20:03 +0200
+
 cloudkitty-dashboard (11.0.0-1) unstable; urgency=medium
 
   * New upstream release.
diff --git a/debian/control b/debian/control
index 7525cc7..6295d6a 100644
--- a/debian/control
+++ b/debian/control
@@ -41,6 +41,8 @@ Depends:
  python3-xstatic-rickshaw,
  ${misc:Depends},
  ${python3:Depends},
+Breaks:
+ python3-django-horizon (<< 3:18.6.2-4~),
 Description: OpenStack data processing cluster as a service - dashboard plugin
  The Sahara project provides a simple means to provision a data-intensive
  application cluster (Hadoop or Spark) on top of OpenStack. It's the ex
diff --git a/debian/python3-cloudkitty-dashboard.install 
b/debian/python3-cloudkitty-dashboard.install
index 94ac7fd..9b4d16b 100644
--- a/debian/python3-cloudkitty-dashboard.install
+++ b/debian/python3-cloudkitty-dashboard.install
@@ -1,2 +1 @@
-/etc/openstack-dashboard/*
 /usr/*
diff --git a/debian/python3-cloudkitty-dashboard.maintscript 
b/debian/python3-cloudkitty-dashboard.maintscript
new file mode 100644
index 000..24bcd97
--- /dev/null
+++ b/debian/python3-cloudkitty-dashboard.maintscript
@@ -0,0 +1,9 @@
+rm_conffile /etc/openstack-dashboard/enable/_10_admin_group.py
+rm_conffile /etc/openstack-dashboard/enable/_10_project_group.py
+rm_conffile /etc/openstack-dashboard/enable/_11_admin_hashmap_panel.py
+rm_conffile /etc/openstack-dashboard/enable/_11_admin_rating_panel.py
+rm_conffile /etc/openstack-dashboard/enable/_11_admin_summary_panel.py
+rm_conffile /etc/openstack-dashboard/enable/_11_project_rating_panel.py
+rm_conffile /etc/openstack-dashboard/enable/_12_project_reporting_panel.py
+rm_conffile /etc/openstack-dashboard/enable/_13_admin_pyscripts_panel.py
+rm_conffile /etc/openstack-dashboard/enable/_31000_cloudkitty.py
diff --git a/debian/rules b/debian/rules
index 37b6a8d..b253002 100755
--- a/debian/rules
+++ b/debian/rules
@@ -23,11 +23,9 @@

Bug#990670: marked as done ([pre-approval] unblock: python-apt/2.2.1)

2021-07-05 Thread Debian Bug Tracking System 
Your message dated Mon, 05 Jul 2021 21:28:25 +
with message-id 
and subject line unblock python-apt
has caused the Debian Bug report #990670,
regarding [pre-approval] unblock: python-apt/2.2.1
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.)


-- 
990670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990670
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: unblock
X-Debbugs-Cc: j...@debian.org

Please unblock package python-apt

[ Reason ]

- Mark python-apt-common as Multi-Arch: common to unblock the
  crossgrader script (#968458). People have very varied understanding
  about severity of this; it's just a single line anyway.
- update the mirror lists.

[ Impact ]
People can't crossgrade and might see outdated mirror information
in mirror selection tools like software-properties

[ Tests ]
No code changed, just metadata. Unit tests are run at
build time and during autopkgtest.


[ Risks ]

It's just metadata changes, only risk is like regressions
in toolchain since last upload.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

unblock python-apt/2.2.1

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


python-apt_2.2.1.diff.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Unblocked.--- End Message ---

Bug#990697: marked as done (unblock: gnome-desktop3/3.38.5-3)

2021-07-05 Thread Debian Bug Tracking System 
Your message dated Mon, 05 Jul 2021 21:23:06 +
with message-id 
and subject line unblock gnome-desktop3
has caused the Debian Bug report #990697,
regarding unblock: gnome-desktop3/3.38.5-3
to be marked as done.

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

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


-- 
990697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990697
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: unblock
X-Debbugs-Cc: pkg-gnome-maintain...@lists.alioth.debian.org

Please unblock package gnome-desktop3.

[ Reason ]

Cherry picked upstream commit to fix segfault when adding input sources 
while show-all-sources is "true". The problem was reported in 
.


[ Impact ]

Without the fix, GNOME users can't make use of the so-called "exotic" 
XKB keyboard layouts. Let's not ship Debian 11 with that bug, even if 
only a minor portion of the users are affected.


[ Tests ]

Manually installed the binaries built by version 3.38.5-3 of the 
gnome-desktop3 source, and confirmed that the bug was fixed as expected.


[ Risks ]

The change is a targeted fix to address the issue at hand. It was 
committed upstream on April 22, and no reported regression.


[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

--
Cheers,
Gunnar Hjalmarsson
diff --git a/debian/changelog b/debian/changelog
index 80634e36..d39f84fc 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+gnome-desktop3 (3.38.5-3) unstable; urgency=medium
+
+  * Team upload
+  * d/p/xkbinfo-only-insert-new-layouts-skip-over-duplicate-ones.patch:
+Fix segfault when adding input sources while show-all-sources is
+"true" (closes: #989045).
+
+ -- Gunnar Hjalmarsson   Sun, 04 Jul 2021 15:40:52 +0200
+
 gnome-desktop3 (3.38.5-2) unstable; urgency=medium
 
   * Team upload
diff --git a/debian/patches/series b/debian/patches/series
index 6b64c79b..0630c1a8 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -4,3 +4,4 @@ xkbinfo-refactor-some-of-the-rules-parsing.patch
 test-convert-the-xkbinfo-test-to-produce-YAML.patch
 xkbinfo-use-libxkbregistry-to-parse-the-rules-files-for-u.patch
 xkbinfo-Update-iso639Ids-correctly-in-evdev.patch
+xkbinfo-only-insert-new-layouts-skip-over-duplicate-ones.patch
diff --git 
a/debian/patches/xkbinfo-only-insert-new-layouts-skip-over-duplicate-ones.patch 
b/debian/patches/xkbinfo-only-insert-new-layouts-skip-over-duplicate-ones.patch
new file mode 100644
index ..1274aae8
--- /dev/null
+++ 
b/debian/patches/xkbinfo-only-insert-new-layouts-skip-over-duplicate-ones.patch
@@ -0,0 +1,53 @@
+From: Peter Hutterer 
+Date: Thu, 22 Apr 2021 01:29:18 +
+Subject: xkbinfo: only insert new layouts, skip over duplicate ones
+
+This matches the behavior to the one in the old code path before
+libxkbregistry.
+
+This also fixes a use-after-free bug when a duplicate layout is present. The
+same layout struct is a member of multiple hashtables, specifically
+priv->layouts_table, priv->layouts_by_language and  priv->layouts_by_country.
+
+When the duplicate layout is added, add_layouts calls g_hash_table_replace
+(priv->layouts_table, l->id, l) which frees the original layout - but the
+layouts_by_{country|language} still have that now-freed layout.
+Immediately afterwards, add_layouts calls add_layout_to_locale_tables () which
+calls add_layout_to_table () which triggers a use-after-free.
+
+Avoid all this by simply skipping any duplicate layout.
+
+Reproducible with
+  gsettings set org.gnome.desktop.input-sources show-all-sources true
+  valgrind /usr/libexec/gnome-desktop-debug/test-xkb-info
+
+Requires xkeyboard-config <= 2.32, it has a duplicate cm(mmuock) entry
+(one is marked exotic, hence the need for show-all-sources).
+
+Origin: concatenation of:
+ https://gitlab.gnome.org/GNOME/gnome-desktop/-/commit/a39dd0d2
+ https://gitlab.gnome.org/GNOME/gnome-desktop/-/commit/81c6cd79
+Bug: https://gitlab.gnome.org/GNOME/gnome-desktop/-/issues/190
+Bug-Debian: https://bugs.debian.org/989045
+Bug-Ubuntu: https://launchpad.net/bugs/1933022
+---
+ libgnome-desktop/gnome-xkb-info.c | 6 ++
+ 1 file changed, 6 insertions(+)
+
+diff --git a/libgnome-desktop/gnome-xkb-info.c 
b/libgnome-desktop/gnome-xkb-info.c
+index b2eca699..f2a3214b 100644
+--- a/libgnome-desktop/gnome-xkb-info.c
 b/libgnome-desktop/gnome-xkb-info.c
+@@ -268,6 +268,12 @@ add_layouts (GnomeXkbInfo*self,
+

Bug#990695: marked as done (unblock: uif/1.1.9-5)

2021-07-05 Thread Debian Bug Tracking System 
Your message dated Mon, 05 Jul 2021 21:05:02 +
with message-id 
and subject line unblock uif
has caused the Debian Bug report #990695,
regarding unblock: uif/1.1.9-5
to be marked as done.

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

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


-- 
990695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990695
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: unblock

Please unblock package uif

[ Reason ]
I recently discovered that uif stopped setting up the kernel firewall
(via iptables-legacy still) on a Debian bullseye systems.

I only got around to investigating this today, so I came up with a patch
that replaces single quotes by double quotes when opening pipes.

[ Impact ]
People using uif will have a dysfunctional firewall.

[ Tests ]
Manual tests and debugging to come up with a patch.

[ Risks ]
None, uif is a leaf package.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
None.

unblock uif/1.1.9-5
diff -Nru uif-1.1.9/debian/changelog uif-1.1.9/debian/changelog
--- uif-1.1.9/debian/changelog  2021-03-26 21:09:26.0 +0100
+++ uif-1.1.9/debian/changelog  2021-07-04 22:59:36.0 +0200
@@ -1,3 +1,17 @@
+uif (1.1.9-5) unstable; urgency=medium
+
+  * debian/patches:
++ Add 1003_correctly-quote-when-opening-pipe.patch. Use double quotes in
+  open statement to properly evaluate variables. (Closes: #990692).
+
+ -- Mike Gabriel   Sun, 04 Jul 2021 22:59:36 +0200
+
+uif (1.1.9-4) unstable; urgency=medium
+
+  * debian/watch: Fix Github watch URL.
+
+ -- Mike Gabriel   Wed, 28 Apr 2021 22:27:57 +0200
+
 uif (1.1.9-3) unstable; urgency=medium
 
   * debian/control:
diff -Nru uif-1.1.9/debian/patches/1003_correctly-quote-when-opening-pipe.patch 
uif-1.1.9/debian/patches/1003_correctly-quote-when-opening-pipe.patch
--- uif-1.1.9/debian/patches/1003_correctly-quote-when-opening-pipe.patch   
1970-01-01 01:00:00.0 +0100
+++ uif-1.1.9/debian/patches/1003_correctly-quote-when-opening-pipe.patch   
2021-07-04 22:54:57.0 +0200
@@ -0,0 +1,32 @@
+Description: Use double quotes in open statement to properly evaluate 
variables.
+Author: Mike Gabriel 
+
+--- a/uif.pl
 b/uif.pl
+@@ -1490,7 +1490,7 @@
+ 
+   @$Listing=map { $_."\n" } @$Listing;
+ 
+-  open (IPT, '$iptables_save|');
++  open (IPT, "$iptables_save|");
+ 
+   @oldrules = ;
+   close (IPT);
+@@ -1500,7 +1500,7 @@
+   $SIG{'QUIT'} = 'signalCatcher';
+   $SIG{'TERM'} = 'signalCatcher';
+ 
+-  open (IPT, '|$iptables_restore');
++  open (IPT, "|$iptables_restore");
+ 
+   print IPT @$Listing;
+   close (IPT);
+@@ -1510,7 +1510,7 @@
+   sleep $timeout;
+   }
+   if ($timeout || $SignalCatched || $error) {
+-  open (IPT, '|$iptables_restore');
++  open (IPT, "|$iptables_restore");
+ 
+   print IPT @oldrules;
+   close (IPT);
diff -Nru uif-1.1.9/debian/patches/series uif-1.1.9/debian/patches/series
--- uif-1.1.9/debian/patches/series 2021-03-26 09:01:55.0 +0100
+++ uif-1.1.9/debian/patches/series 2021-07-04 22:50:02.0 +0200
@@ -1,2 +1,3 @@
 1001_use-iptables-legacy.patch
 1002_use-iptables-from-usr-sbin.patch
+1003_correctly-quote-when-opening-pipe.patch
diff -Nru uif-1.1.9/debian/watch uif-1.1.9/debian/watch
--- uif-1.1.9/debian/watch  2018-08-20 12:19:45.0 +0200
+++ uif-1.1.9/debian/watch  2021-04-28 22:27:41.0 +0200
@@ -1,4 +1,4 @@
 version=3
 opts=filenamemangle=s/.*\/v?([\d\.-]+)\.tar\.gz/uif-$1.tar.gz/ \
-https://github.com/cajus/uif/tags .*/archive/v?([\d\.]+).tar.gz
+https://github.com/cajus/uif/tags .*/archive/refs/tags/v?([\d\.]+).tar.gz
 
--- End Message ---
--- Begin Message ---
Unblocked.--- End Message ---

Bug#990651: marked as done (unblock: nx-libs/2:3.5.99.26-2)

2021-07-05 Thread Debian Bug Tracking System 
Your message dated Mon, 05 Jul 2021 21:06:17 +
with message-id 
and subject line unblock nx-libs
has caused the Debian Bug report #990651,
regarding unblock: nx-libs/2:3.5.99.26-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.)


-- 
990651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990651
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: unblock

Please unblock package nx-libs

[ Reason ]
Several important upstream issues have recently been resolved in nx-libs.
The fixes for those issues have been cherry-picked into this version of
Debian's nx-libs package.

+  * debian/patches:
++ Add 0001_Compext.c-fix-comparisons-of-16bit-sequence-numbers.patch.
+  Compext.c: fix comparisons of 16bit sequence numbers. (Closes:
+  #990647).

-> Fixes flawed 16 bit comparison. This resolves an "Xlib: unexpected async
reply (sequence 0x94b01439)!" and clipboard pasting being broken afterwards.

++ Add 0002_Forward-ClientMessages-to-nxproxy-side.patch.
+  Forward ClientMessages to nxproxy side. (Closes: #990649).

-> Resolve window control problems with client side decorated windows if
nxagent is used in rootless/seamless session mode.

++ Add 0003_randr-Do-not-update-ConnectionInfo-if-NULL.patch.
+  randr: Do not update ConnectionInfo if NULL (and avoid the nxagent
+  Xserver from crashing). (Closes: #990650).

-> Regression fix of unknown origin. Could be resolved by cherry-picking
a commit original from X.Org upstream. 

++ Add 0004_document-additional-options-only-nxagent-knows-about.patch.
+  Update man page and --help documentation of nxproxy/nxagent.

-> Recently, upstream added a documentation improvement that now
documents various session options that were undocumented before.

++ Adjust 0004_document-additional-options-only-nxagent-knows-about.patch.
+  Version 3.5.99.26 does not yet have the textclipboard= session
+  parameter.

-> The above patch added one option that is not yet available in 3.5.99.26,
So we removed this bit of documenation for nx-libs in Debian (bullseye).


[ Impact ]
The "connect to local X11 desktop" (shadow session support) would be broken, 

The clipboard between nxagent and the local Xserver might break in some 
situations.

There would be problems with client side decorated windows.

There would be undocumented options.

[ Tests ]
Manual tests.

[ Risks ]
X2Go sessions being busted if some of the above commits is flawed.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
None.

unblock nx-libs/2:3.5.99.26-2
--- End Message ---
--- Begin Message ---
Unblocked.--- End Message ---

Bug#990710: marked as done (unblock: jetty9/9.4.39-1)

2021-07-05 Thread Debian Bug Tracking System 
Your message dated Mon, 05 Jul 2021 21:03:28 +
with message-id 
and subject line unblock jetty9
has caused the Debian Bug report #990710,
regarding unblock: jetty9/9.4.39-1
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.)


-- 
990710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990710
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: unblock

Please unblock package jetty9

[ Reason ]

Fixing CVE-2021-28169 and CVE-2021-34428

[ Impact ]

Version of Jetty 9 in Debian 11 is vulnerable

[ Tests ]

Integrated tests pass successfully

[ Risks ]

None, since all tests pass.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing


unblock jetty9/9.4.39-1
diff -Nru jetty9-9.4.39/debian/changelog jetty9-9.4.39/debian/changelog
--- jetty9-9.4.39/debian/changelog  2021-04-12 00:11:03.0 +0200
+++ jetty9-9.4.39/debian/changelog  2021-07-03 19:09:58.0 +0200
@@ -1,3 +1,23 @@
+jetty9 (9.4.39-2) unstable; urgency=high
+
+  * Team upload.
+  * Fix CVE-2021-28169:
+It is possible for requests to the ConcatServlet with a doubly encoded path
+to access protected resources within the WEB-INF directory. For example a
+request to `/concat?/%2557EB-INF/web.xml` can retrieve the web.xml file.
+This can reveal sensitive information regarding the implementation of a web
+application.
+  * Fix CVE-2021-34428:
+If an exception is thrown from the SessionListener#sessionDestroyed()
+method, then the session ID is not invalidated in the session ID manager.
+On deployments with clustered sessions and multiple contexts this can
+result in a session not being invalidated. This can result in an
+application used on a shared computer being left logged in.
+
+Thanks to Salvatore Bonaccorso for the report. (Closes: #98, #990578)
+
+ -- Markus Koschany   Sat, 03 Jul 2021 19:09:58 +0200
+
 jetty9 (9.4.39-1) unstable; urgency=high
 
   * New upstream release
diff -Nru jetty9-9.4.39/debian/patches/CVE-2021-28169.patch 
jetty9-9.4.39/debian/patches/CVE-2021-28169.patch
--- jetty9-9.4.39/debian/patches/CVE-2021-28169.patch   1970-01-01 
01:00:00.0 +0100
+++ jetty9-9.4.39/debian/patches/CVE-2021-28169.patch   2021-07-03 
19:09:58.0 +0200
@@ -0,0 +1,520 @@
+From: Markus Koschany 
+Date: Sat, 3 Jul 2021 19:01:20 +0200
+Subject: CVE-2021-28169
+
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=98
+Origin: 
https://github.com/eclipse/jetty.project/commit/1c05b0bcb181c759e98b060bded0b9376976b055
+---
+ .../org/eclipse/jetty/server/ResourceService.java  |   4 +-
+ .../org/eclipse/jetty/servlets/ConcatServlet.java  |   4 +-
+ .../org/eclipse/jetty/servlets/WelcomeFilter.java  |   8 +-
+ .../eclipse/jetty/servlets/ConcatServletTest.java  |  83 
+ .../eclipse/jetty/servlets/WelcomeFilterTest.java  | 143 +
+ .../jetty/webapp/WebAppDefaultServletTest.java | 142 
+ 6 files changed, 353 insertions(+), 31 deletions(-)
+ create mode 100644 
jetty-servlets/src/test/java/org/eclipse/jetty/servlets/WelcomeFilterTest.java
+ create mode 100644 
jetty-webapp/src/test/java/org/eclipse/jetty/webapp/WebAppDefaultServletTest.java
+
+diff --git 
a/jetty-server/src/main/java/org/eclipse/jetty/server/ResourceService.java 
b/jetty-server/src/main/java/org/eclipse/jetty/server/ResourceService.java
+index 1edfd83..c908e8d 100644
+--- a/jetty-server/src/main/java/org/eclipse/jetty/server/ResourceService.java
 b/jetty-server/src/main/java/org/eclipse/jetty/server/ResourceService.java
+@@ -240,7 +240,7 @@ public class ResourceService
+ // Find the content
+ content = _contentFactory.getContent(pathInContext, 
response.getBufferSize());
+ if (LOG.isDebugEnabled())
+-LOG.info("content={}", content);
++LOG.debug("content={}", content);
+ 
+ // Not found?
+ if (content == null || !content.getResource().exists())
+@@ -430,7 +430,7 @@ public class ResourceService
+ return;
+ }
+ 
+-RequestDispatcher dispatcher = 
context.getRequestDispatcher(welcome);
++RequestDispatcher dispatcher = 
context.getRequestDispatcher(URIUtil.encodePath(welcome));
+ if (dispatcher != null)
+ {
+ // Forward to the index
+diff --git

Bug#990699: marked as done (release.debian.org: Sorting out bug 990059 in bullseye)

2021-07-05 Thread Debian Bug Tracking System 
Your message dated Mon, 5 Jul 2021 22:28:27 +0200
with message-id 
and subject line Re: Bug#990699: release.debian.org: Sorting out bug 990059 in 
bullseye
has caused the Debian Bug report #990699,
regarding release.debian.org: Sorting out bug 990059 in 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.)


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

Hi,

Recent versions of libnss3 had a backwards incompatible change that made
packages built with the newer versions fail to work properly with the older
version of the package that is in bullseye.

That wouldn't be a problem if 2 packages that use the problematic symbol
and are built with the newer version hadn't themselves made it to
bullseye. The packages are, namely, firefox-esr and curl (curl has only
become a problem this week).

I uploaded a version of nss (2:3.67-2) that works around the issue and
will make rebuilds of those packages work with the version of nss in
bullseye, meaning we'd need binNMUs of both curl and firefox-esr and
subsequent transitions.

However, firefox-esr is due for a security update next tuesday/wednesday,
so it will be rebuilt anyways. I guess we might as well wait.

Which leaves us with just curl.

 nmu curl_7.74.0-1.3 . ANY . -m 'Rebuild against newer libnss3-dev'

Mike
--- End Message ---
--- Begin Message ---
On 2021-07-05 09:33:40 +0900, Mike Hommey wrote:
> Package: release.debian.org
> Severity: important
> Usertags: binnmu transition
> 
> Hi,
> 
> Recent versions of libnss3 had a backwards incompatible change that made
> packages built with the newer versions fail to work properly with the older
> version of the package that is in bullseye.
> 
> That wouldn't be a problem if 2 packages that use the problematic symbol
> and are built with the newer version hadn't themselves made it to
> bullseye. The packages are, namely, firefox-esr and curl (curl has only
> become a problem this week).
> 
> I uploaded a version of nss (2:3.67-2) that works around the issue and
> will make rebuilds of those packages work with the version of nss in
> bullseye, meaning we'd need binNMUs of both curl and firefox-esr and
> subsequent transitions.
> 
> However, firefox-esr is due for a security update next tuesday/wednesday,
> so it will be rebuilt anyways. I guess we might as well wait.
> 
> Which leaves us with just curl.
> 
>  nmu curl_7.74.0-1.3 . ANY . -m 'Rebuild against newer libnss3-dev'

Thanks, scheduled.

> 
> Mike
> 

-- 
Sebastian Ramacher


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

Processed: Re: Bug#990500: unblock: lxml/4.6.3+dfsg-0.1

2021-07-05 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 - moreinfo
Bug #990500 [release.debian.org] unblock: lxml/4.6.3+dfsg-0.1
Removed tag(s) moreinfo.

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

Bug#990500: unblock: lxml/4.6.3+dfsg-0.1

2021-07-05 Thread Paul Gevers 
Control: tags -1 - moreinfo

Hi Sebastian,

On 04-07-2021 22:01, Sebastian Ramacher wrote:
>> diff -Nru lxml-4.6.3/debian/control lxml-4.6.3+dfsg/debian/control
>> --- lxml-4.6.3/debian/control2020-12-07 14:42:24.0 +0100
>> +++ lxml-4.6.3+dfsg/debian/control   2021-06-26 19:40:37.0 +0200
>> @@ -9,6 +9,7 @@
>>python3-setuptools (>= 0.6.29),
>>python3-bs4,
>>python3-html5lib,
>> +  python3-lxml ,
>>cython3, cython3-dbg,
>>python3-sphinx-autoapi,
>>  X-Python-Version: all
>> diff -Nru lxml-4.6.3/debian/rules lxml-4.6.3+dfsg/debian/rules
>> --- lxml-4.6.3/debian/rules  2020-07-17 11:16:59.0 +0200
>> +++ lxml-4.6.3+dfsg/debian/rules 2021-06-26 19:40:37.0 +0200
>> @@ -24,6 +24,9 @@
>>  touch $@
>>  build3-python%: prebuild
>>  python$* setup.py build
>> +ifeq (,$(filter nodoc,$(DEB_BUILD_OPTIONS)))
>> +python$* doc/mkhtml.py doc/html . $(UPSTREAMVER)
>> +endif
> 
> Shouldn't this use the just built version of lxml, e.g., by setting the
> appropriate PYTHONPATH, instead of the old packaged lxml in python3-lxml?

Oh, yes. But as I don't do Python packaging (just didn't happen, I don't
object), I didn't know how to do that and I didn't want to spend too
much time on it to figure it out (and potentially getting it wrong).

Paul




OpenPGP_signature
Description: OpenPGP digital signature

Bug#990731: unblock: virulencefinder/2.0.3+git20190809.dde157a-3

2021-07-05 Thread Nilesh Patra 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: nil...@debian.org, debian-med-packag...@lists.alioth.debian.org

Please unblock package virulencefinder

[ Reason ]
virulencefinder is an unusable package w/o having a Depends on
python3-distutils
It also fixes the corresponding RC bug #990728

[ Impact ]
The package will be unusable for bullseye users w/o explicitly
installing python3-distutils on their own

[ Tests ]
The package has autopkgtests which pass

[ Risks ]
No risks, resfinder is a leaf package

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

unblock virulencefinder/2.0.3+git20190809.dde157a-3

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

Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads)
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 not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru virulencefinder-2.0.3+git20190809.dde157a/debian/changelog 
virulencefinder-2.0.3+git20190809.dde157a/debian/changelog
--- virulencefinder-2.0.3+git20190809.dde157a/debian/changelog  2020-03-03 
11:39:54.0 +0530
+++ virulencefinder-2.0.3+git20190809.dde157a/debian/changelog  2021-07-06 
00:36:09.0 +0530
@@ -1,3 +1,11 @@
+virulencefinder (2.0.3+git20190809.dde157a-3) unstable; urgency=medium
+
+  * Team Upload.
+  * d/control: Add Missing Depends on python3-distutils
+(Closes: #990728)
+
+ -- Nilesh Patra   Tue, 06 Jul 2021 00:36:09 +0530
+
 virulencefinder (2.0.3+git20190809.dde157a-2) unstable; urgency=medium
 
   * Team Upload.
diff -Nru virulencefinder-2.0.3+git20190809.dde157a/debian/control 
virulencefinder-2.0.3+git20190809.dde157a/debian/control
--- virulencefinder-2.0.3+git20190809.dde157a/debian/control2020-03-03 
11:39:54.0 +0530
+++ virulencefinder-2.0.3+git20190809.dde157a/debian/control2021-07-06 
00:35:45.0 +0530
@@ -23,7 +23,8 @@
  python3-tabulate,
  python3-cgecore,
  ncbi-blast+,
- kma
+ kma,
+ python3-distutils
 Description: identify virulence genes in total or partial sequenced isolates 
of bacteria
  The VirulenceFinder service contains one Python script
  virulencefinder.py which is the script of the latest version of the
diff -Nru virulencefinder-2.0.3+git20190809.dde157a/debian/tests/control 
virulencefinder-2.0.3+git20190809.dde157a/debian/tests/control
--- virulencefinder-2.0.3+git20190809.dde157a/debian/tests/control  
2020-03-03 11:39:54.0 +0530
+++ virulencefinder-2.0.3+git20190809.dde157a/debian/tests/control  
2021-07-06 00:35:29.0 +0530
@@ -1,3 +1,3 @@
 Tests: run-unit-test
-Depends: @, python3-distutils
+Depends: @
 Restrictions: allow-stderr

Bug#990730: unblock: resfinder/3.2-3

2021-07-05 Thread Nilesh Patra 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: nil...@debian.org, debian-med-packag...@lists.alioth.debian.org

Please unblock package resfinder

[ Reason ]
resfinder is an unusable package w/o having a Depends on
python3-distutils
It also fixes the corresponding RC bug #990726

[ Impact ]
The package will be unusable for bullseye users w/o explicitly
installing python3-distutils on their own

[ Tests ]
The package has autopkgtests which pass

[ Risks ]
No risks, resfinder is a leaf package

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

unblock resfinder/3.2-3

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

Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads)
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 not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru resfinder-3.2/debian/changelog resfinder-3.2/debian/changelog
--- resfinder-3.2/debian/changelog  2020-03-03 11:12:37.0 +0530
+++ resfinder-3.2/debian/changelog  2021-07-06 00:05:05.0 +0530
@@ -1,3 +1,13 @@
+resfinder (3.2-3) unstable; urgency=medium
+
+  * Team Upload.
+  * d/control: Add Missing Depends on python3-distutils
+(Closes: #990726)
+  * d/p/fix_syntaxwarning.patch: Fix syntax warning for
+literal comparison
+
+ -- Nilesh Patra   Tue, 06 Jul 2021 00:05:05 +0530
+
 resfinder (3.2-2) unstable; urgency=medium
 
   [ Nilesh Patra ]
diff -Nru resfinder-3.2/debian/control resfinder-3.2/debian/control
--- resfinder-3.2/debian/control2020-03-03 11:12:37.0 +0530
+++ resfinder-3.2/debian/control2021-07-06 00:01:06.0 +0530
@@ -19,7 +19,8 @@
  resfinder-db,
  python3-cgecore,
  python3-tabulate,
- ncbi-blast+-legacy
+ ncbi-blast+-legacy,
+ python3-distutils
 Description: identify acquired antimicrobial resistance genes
  ResFinder identifies acquired antimicrobial resistance genes in total or
  partial sequenced isolates of bacteria.
diff -Nru resfinder-3.2/debian/patches/fix_syntaxwarning.patch 
resfinder-3.2/debian/patches/fix_syntaxwarning.patch
--- resfinder-3.2/debian/patches/fix_syntaxwarning.patch1970-01-01 
05:30:00.0 +0530
+++ resfinder-3.2/debian/patches/fix_syntaxwarning.patch2021-07-06 
00:04:19.0 +0530
@@ -0,0 +1,14 @@
+Description: Use == instead of is
+Author: Nilesh Patra 
+Last-Update: 2021-07-05
+--- a/resfinder.py
 b/resfinder.py
+@@ -364,7 +364,7 @@
+   """
+   """
+   # Check if databases and config file are correct/correponds
+-  if databases is '':
++  if databases == '':
+ sys.exit("Input Error: No database was specified!\n")
+   elif databases is None:
+  # Choose all available databases from the config file
diff -Nru resfinder-3.2/debian/patches/series 
resfinder-3.2/debian/patches/series
--- resfinder-3.2/debian/patches/series 1970-01-01 05:30:00.0 +0530
+++ resfinder-3.2/debian/patches/series 2021-07-06 00:03:19.0 +0530
@@ -0,0 +1 @@
+fix_syntaxwarning.patch
diff -Nru resfinder-3.2/debian/tests/control resfinder-3.2/debian/tests/control
--- resfinder-3.2/debian/tests/control  2020-03-03 11:12:37.0 +0530
+++ resfinder-3.2/debian/tests/control  2021-07-06 00:01:06.0 +0530
@@ -1,3 +1,3 @@
 Tests: run-unit-test
-Depends: @, python3-distutils
+Depends: @
 Restrictions: allow-stderr

Bug#990723: unblock: barman/2.12-2

2021-07-05 Thread Christoph Berg 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package barman

[ Reason ]
The existing package does not support PG13 and users will have a hard
time actually restoring backups from archive.

[ Tests ]
The upstream git repository does contain tests, but the shipped
tarball does not. I have no idea why they thought this is a good idea,
and I'm only fixing this since Marco seems unavailable.

The fix has been confirmed to work upstream and the diff looks sane.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

unblock barman/2.12-2

Thanks,
Christoph

No differences were encountered between the control files

diff -Nru barman-2.12/debian/changelog barman-2.12/debian/changelog
--- barman-2.12/debian/changelog	2020-11-04 10:39:52.0 +0100
+++ barman-2.12/debian/changelog	2021-07-05 17:59:18.0 +0200
@@ -1,3 +1,10 @@
+barman (2.12-2) unstable; urgency=medium
+
+  * Team upload.
+  * PG 13 expects wal_keep_size, not wal_keep_segments. (Closes: #990304)
+
+ -- Christoph Berg   Mon, 05 Jul 2021 17:59:18 +0200
+
 barman (2.12-1) unstable; urgency=medium
 
   * New upstream version 2.12
diff -Nru barman-2.12/debian/patches/pg13 barman-2.12/debian/patches/pg13
--- barman-2.12/debian/patches/pg13	1970-01-01 01:00:00.0 +0100
+++ barman-2.12/debian/patches/pg13	2021-07-05 17:59:14.0 +0200
@@ -0,0 +1,125 @@
+commit 45ccd9d2f315ec208eee778eba1333c0aa4a4460
+Author: Abhijit Menon-Sen 
+Date:   Wed Jan 20 19:47:37 2021 +0530
+
+Fetch wal_keep_size, not wal_keep_segments, from Postgres 13
+
+The `wal_keep_segments` parameter introduced in v9.0 was replaced with
+`wal_keep_size` in v13. Running Barman against Postgres 13 resulted in
+errors like the following being logged:
+
+barman ERROR:  unrecognized configuration parameter "wal_keep_segments"
+barman STATEMENT:  SHOW "wal_keep_segments"
+
+Here we change fetch_remote_status() to ask for wal_keep_size if the
+server version is >= 13. We didn't use this value anywhere, so we don't
+need any further changes to adapt to the different return value.
+
+Signed-off-by: Abhijit Menon-Sen 
+
+diff --git a/barman/postgres.py b/barman/postgres.py
+index 2414f77..6664620 100644
+--- a/barman/postgres.py
 b/barman/postgres.py
+@@ -827,7 +827,12 @@ class PostgreSQLConnection(PostgreSQL):
+ pg_settings.append('wal_level')
+ pg_settings.append('hot_standby')
+ pg_settings.append('max_wal_senders')
+-pg_settings.append('wal_keep_segments')
++# Retrieve wal_keep_segments from version 9.0 onwards, until
++# version 13.0, where it was renamed to wal_keep_size
++if self.server_version < 13:
++pg_settings.append('wal_keep_segments')
++else:
++pg_settings.append('wal_keep_size')
+ 
+ if self.server_version >= 90300:
+ pg_settings.append('data_checksums')
+diff --git a/doc/manual/42-server-commands.en.md b/doc/manual/42-server-commands.en.md
+index 90caea7..20e91d9 100644
+--- a/doc/manual/42-server-commands.en.md
 b/doc/manual/42-server-commands.en.md
+@@ -198,7 +198,8 @@ record of the transaction log. When the status file needs to be
+ cleaned, the `--reset` option can be used.
+ 
+ > **IMPORTANT:** If you are not using replication slots, you rely
+-> on the value of `wal_keep_segments`. Be aware that under high peeks
++> on the value of `wal_keep_segments` (or `wal_keep_size` from
++> PostgreSQL version 13.0 onwards). Be aware that under high peaks
+ > of workload on the database, the `receive-wal` process
+ > might fall behind and go out of sync. As a precautionary measure,
+ > Barman currently requires that users manually execute the command with the
+#diff --git a/tests/test_postgres.py b/tests/test_postgres.py
+#index 83c9f14..67636bb 100644
+#--- a/tests/test_postgres.py
+#+++ b/tests/test_postgres.py
+#@@ -822,6 +822,8 @@ class TestPostgres(object):
+#new_callable=PropertyMock)
+# @patch('barman.postgres.PostgreSQLConnection.is_in_recovery',
+#new_callable=PropertyMock)
+#+@patch('barman.postgres.PostgreSQLConnection.has_backup_privileges',
+#+   new_callable=PropertyMock)
+# @patch('barman.postgres.PostgreSQLConnection.is_superuser',
+#new_callable=PropertyMock)
+# @patch('barman.postgres.PostgreSQLConnection.server_txt_version',
+#@@ -847,6 +849,7 @@ class TestPostgres(object):
+#has_pgespresso_mock,
+#server_txt_version_mock,
+#is_superuser_mock,
+#+   has_backup_privileges_mock,
+#

Re: Six Bullseye packages that should be Priority: optional

2021-07-05 Thread Daniel Lewart 
Simon, et al,

Thank you for your excellent feedback!

On Mon, 5 Jul 2021 at 10:40:28 +0100, Simon McVittie wrote:

> On Mon, 05 Jul 2021 at 02:30:00 -0500, Daniel Lewart wrote:

> > Comparing important/required/standard packages between
> > Buster and Bullseye, I noticed some inconsistencies.

> We have been in hard freeze for almost 4 months, so I don't think
> now is necessarily the right time to be changing what is in a default
> installation of Debian (which is what the boundary between standard and
> optional means) without release team approval.

No worries.  The last thing I want to do is to add stress
to the Release Team.

> I've cc'd the release team to see what they think.

Very good.

> I agree with your reasoning for why these packages should be
> Priority: optional, and for any that cannot be changed in bullseye, the
> beginning of the Debian 12 'bookworm' release cycle would be an excellent
> time to make that change.

> > If so, should I file one or multiple bugs against:

> The ftp.debian.org pseudo-package is the right place to ask for priority
> changes ("override changes"): individual packages' maintainers cannot
> change this on their own. If you use reportbug, there's a template for
> an override change.

> It's probably best to Cc the package maintainer
> (name_of_pack...@packages.debian.org) using the X-Debbugs-Cc mechanism,
> because there is a suggested priority in the package's debian/control,
> which the ftp team use as a basis for setting the priority of new packages.
> (Yes, it's redundant, and there are probably better ways this could be
> controlled, but this is what we have at the moment.)

Excellent.  Of course, I will wait for Release Team feedback
before doing so.

> > 1) override: bind9-dnsutils:net/optional
> >   * Currently net/standard
> >   * Justification: Buster dnsutils is net/optional

> This is essentially asking: should the DNS utilities (dig, nslookup etc.)
> be installed by default even if nothing else depends on them? and changing
> the answer to that question seems a disruptive thing to be doing during
> hard freeze.

Agreed.

> These have relatively "heavy" dependencies, so they are probably the
> highest-impact in terms of reducing the size of a default installation;
> but they also seem like the highest-risk in terms of potentially exposing
> bugs where packages rely on these utilities without declaring a dependency.

> > 2) override: bind9-libs:libs/optional
> > 5) override: libreadline8:libs/optional
> >   * Justification: Debian Policy 2.5

> I agree that shared libraries should be Priority: optional. They will be
> pulled in by dependencies if they are needed.

> bind9-libs is pulled in by bind9-dnsutils, so there is no point in changing
> that priority unless bind9-dnsutils is also changed.

bind9-host (standard) Depends: bind9-libs,
so bind9-libs would be pulled in anyway.

> libreadline8 is quite small, so the impact of installing it unnecessarily
> is low.

python3-reportbug (standard) Depends: ... Depends: libreadline8,
so libreadline8 is installed by default.

> > 3) override: gcc-9-base:libs/optional
> > 4) override: gcc-10-base:libs/optional
> >   * Currently libs/required

> These are not *really* shared libraries, but the same reasoning applies,
> and I agree they should be Priority: optional.

> If I'm reading correctly, gcc-9-base is included in default installations
> of Debian 11, even though nothing else built by src:gcc-9 is, nicely
> demonstrating why Policy §2.5 changed to its current contents. This seems
> like it's obviously a bug (200K of licenses and documentation are installed
> unnecessarily), and unlike the other genuine bugs you've mentioned here,
> this one seems low-risk to fix, because gcc-9-base only contains
> documentation.

Yes, since "standard system utilities" are selected by default.

> In practice gcc-10-base will be installed anyway, as a result of libgcc-s1
> depending on it, so that change would have no practical effect right now;
> but moving it to Priority: optional would avoid having the same bug as for
> gcc-9-base when we upgrade to gcc-11 or later in a future Debian release.

Yes, since apt (required) Depends: libgcc-s1, libstdc++6 .

> > 6) override: mime-support:oldlibs/optional
> >   * Currently net/standard
> >   * Justification: Transitional package

> mime-support depends on mailcap (Priority: optional) and media-types
> (Priority: standard), so downgrading mime-support to optional would mean
> that mailcap (compose(1), edit(1), see(1), print(1)) would not be installed
> by default. That seems like it has a risk of exposing bugs where packages
> rely on those tools without declaring a dependency.

> I agree that this should be oldlibs/optional, but 4 months into hard freeze
> doesn't seem like the right time to change it.

Agreed.

Thank you again!
Dan
Urbana, Illinois

Bug#990719: unblock: tracker-miners/2.3.5-2.1

2021-07-05 Thread Guido Günther 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: pkg-gnome-maintain...@lists.alioth.debian.org

Please unblock package tracker-miners

[ Reason ]
The filesystem miner crashes repeatedly on (at least) arm64 and linux
5.11 or later kernels. See #983637.

Due to a missing syscall whitelist of the miner's sandbox the filesystem
tracker crashes repeatedly on startup.  This doesn't happen on bullseye
amd64 and linux 5.10 but can be reproduced on amd64 and (at least)
kernel 5.11 or later.

[ Impact ]
Makes the miner unusable but also drains the battery quickly since
systemd restarts the miner unconditionally and endlessly. This is
especially bad if core files are enabled since the writing of those
over and over drains battery even quicker.

[ Tests ]
Whether the service is up can be checked via

   systemctl start --user tracker-miner-fs.service

[ Risks ]
The proposed fix is a backport of an upstream fix so
the risk seems minimal. Theoretically allowing more
syscalls in the sandbox could open a security hole.

unblock tracker-miners/2.3.5-2.1
diff --git a/debian/changelog b/debian/changelog
index 353d69ddf..4fa33a6bd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+tracker-miners (2.3.5-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * libtracker-miners-common: Add newstatat/statat64 syscalls.
+Backport upstream commit b3fdbaf to avoid constant crashes every 2s.
+Thanks Julian Andres Klode for forwarding this initially.
+(Closes: #983637)
+
+ -- Guido Günther   Mon, 05 Jul 2021 12:40:50 +0200
+
 tracker-miners (2.3.5-2) unstable; urgency=medium
 
   * Make the 'audio' tests non-fatal on powerpc and sparc64 as well
diff --git a/debian/patches/libtracker-miners-common-Add-newstatat-statat64-syscalls.patch b/debian/patches/libtracker-miners-common-Add-newstatat-statat64-syscalls.patch
new file mode 100644
index 0..832386d2c
--- /dev/null
+++ b/debian/patches/libtracker-miners-common-Add-newstatat-statat64-syscalls.patch
@@ -0,0 +1,24 @@
+From: Carlos Garnacho 
+Date: Sun, 25 Oct 2020 15:37:13 +0100
+Subject: libtracker-miners-common: Add newstatat/statat64 syscalls
+
+These are done in recent glib versions, should be observed here.
+
+(cherry picked from commit b3fdbaf1ab23ce7191ace6db79575dfce5f90881)
+---
+ src/libtracker-miners-common/tracker-seccomp.c | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/src/libtracker-miners-common/tracker-seccomp.c b/src/libtracker-miners-common/tracker-seccomp.c
+index c0327eb..01887e8 100644
+--- a/src/libtracker-miners-common/tracker-seccomp.c
 b/src/libtracker-miners-common/tracker-seccomp.c
+@@ -91,6 +91,8 @@ tracker_seccomp_init (void)
+ 	/* Basic filesystem access */
+ 	ALLOW_RULE (fstat);
+ 	ALLOW_RULE (fstat64);
++	ALLOW_RULE (fstatat64);
++	ALLOW_RULE (newfstatat);
+ 	ALLOW_RULE (stat);
+ 	ALLOW_RULE (stat64);
+ 	ALLOW_RULE (statfs);
diff --git a/debian/patches/series b/debian/patches/series
index a9bd2953d..f56af3a1f 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -5,3 +5,4 @@ prefer_systemd_activation.patch
 dont_start_for_root.patch
 Don-t-immediately-restart-tracker-extract-on-SIGSYS.patch
 debian/Revert-build-Include-libdir-in-rpath.patch
+libtracker-miners-common-Add-newstatat-statat64-syscalls.patch

Processed: Re: unblock: kodi-pvr-waipu/2.8.4+ds1-1

2021-07-05 Thread Debian Bug Tracking System 
Processing control commands:

> close -1
Bug #988623 [release.debian.org] unblock: kodi-pvr-waipu/2.8.4+ds1-1
Marked Bug as done

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

Bug#988623: unblock: kodi-pvr-waipu/2.8.4+ds1-1

2021-07-05 Thread Vasyl Gello 
Control: close -1

Hi Sebastian!

After more thorough review of commits themselves I feel not sure about 
re-authentication issue. So I am closing the bug until some Waipu.tv user 
reopens it.
-- 
Vasyl Gello
==
Certified SolidWorks Expert

Mob.:+380 (98) 465 66 77

E-Mail: vasek.ge...@gmail.com

Skype: vasek.gello
==
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다

Bug#990711: unblock: debian-games/4

2021-07-05 Thread Markus Koschany 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: a...@debian.org

Please unblock package debian-games

[ Reason ]

debian-games is a metapackage that only recommends or suggests games.
This is an update to include the changes that occurred in the past
months during the freeze. Packages which were removed from Debian or
will not be part of Debian 11 have been either removed from the
list of recommended packages or downgraded to Suggests.

[ Impact ]

The list of recommended and suggested packages will be outdated.

[ Tests ]

There were no code changes. Only the list of recommended or suggested
packages was updated.

[ Risks ]

The change is trivial.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

unblock debian-games/4
diff -Nru debian-games-3.3/debian/changelog debian-games-4/debian/changelog
--- debian-games-3.3/debian/changelog   2021-02-19 01:29:47.0 +0100
+++ debian-games-4/debian/changelog 2021-07-04 08:50:03.0 +0200
@@ -1,3 +1,21 @@
+debian-games (4) unstable; urgency=medium
+
+  * Update the blacklist
+  * New games:
+- puzzle: chroma
+- console,toys: cbonsai
+  * Removed games or tools: (removed from Debian)
+- adanaxisgpl
+- aajm
+- jmdlx
+- fretsonfire
+- kiki-the-nano-bot
+- jerry
+- ninja-ide
+- python3-pyqt4.qtopengl
+
+ -- Markus Koschany   Sun, 04 Jul 2021 08:50:03 +0200
+
 debian-games (3.3) unstable; urgency=medium
 
   * arcade: Remove fofix from Suggests.
@@ -15,7 +33,7 @@
 - board: kgames
 - rpg: openmw
 - rpg: openmw-cs
-- arcarde: pinball-table-gnu
+- arcade: pinball-table-gnu
 - arcade: pinball-table-hurd
 - puzzle: puzzle-jigsaw
 - puzzle: sudoku-solver
diff -Nru debian-games-3.3/debian/control debian-games-4/debian/control
--- debian-games-3.3/debian/control 2021-02-19 01:29:47.0 +0100
+++ debian-games-4/debian/control   2021-07-04 08:50:03.0 +0200
@@ -495,6 +495,7 @@
 trader,
 vitetris
 Suggests: aajm,
+  cbonsai,
   termtris
 Description: Debian's console games
  This metapackage will install text console games designed to be used via a
@@ -872,6 +873,7 @@
 freesweep,
 gbrainy,
 gcompris,
+gfpoken,
 glpeces,
 gmult,
 gnome-mahjongg,
@@ -923,7 +925,7 @@
 xsok,
 xye,
 zaz
-Suggests: gfpoken,
+Suggests: chroma,
   gnome-games,
   gweled,
   kdegames,
@@ -1283,7 +1285,8 @@
 xplanet-images,
 xsnow,
 xteddy
-Suggests: fortunate.app
+Suggests: cbonsai,
+  fortunate.app
 Description: Debian's toy games
  This metapackage will install a collection of desktop toys and console
  programs that often modify the appearance of your computer and text in a
diff -Nru debian-games-3.3/src/blacklist debian-games-4/src/blacklist
--- debian-games-3.3/src/blacklist  2021-02-19 01:29:47.0 +0100
+++ debian-games-4/src/blacklist2021-07-04 08:50:03.0 +0200
@@ -679,3 +679,7 @@
 xscreensaver-screensaver-dizzy
 xye-data
 zaz-data
+openmw-data
+openmw-launcher
+pinball-table-gnu-data
+pinball-table-hurd-data
diff -Nru debian-games-3.3/tasks/arcade debian-games-4/tasks/arcade
--- debian-games-3.3/tasks/arcade   2021-02-19 01:29:47.0 +0100
+++ debian-games-4/tasks/arcade 2021-07-04 08:50:03.0 +0200
@@ -6,8 +6,6 @@
 
 Depends: abe
 
-Depends: adanaxisgpl
-
 Depends: airstrike
 
 Depends: alienblaster
@@ -62,8 +60,6 @@
 
 Depends: freegish
 
-Depends: fretsonfire
-
 Depends: funguloids
 
 Depends: funnyboat
@@ -94,8 +90,6 @@
 
 Depends: ii-esu
 
-Depends: jmdlx
-
 Depends: jumpnbump
 
 Depends: jumpnbump-levels
diff -Nru debian-games-3.3/tasks/chess debian-games-4/tasks/chess
--- debian-games-3.3/tasks/chess2021-02-19 01:29:47.0 +0100
+++ debian-games-4/tasks/chess  2021-07-04 08:50:03.0 +0200
@@ -36,8 +36,6 @@
 
 Depends: hoichess
 
-Depends: jerry
-
 Depends: pgn-extract
 
 Depends: pgn2web
diff -Nru debian-games-3.3/tasks/console debian-games-4/tasks/console
--- debian-games-3.3/tasks/console  2021-02-19 01:29:47.0 +0100
+++ debian-games-4/tasks/console2021-07-04 08:50:03.0 +0200
@@ -5,8 +5,6 @@
 
 Depends: 2048
 
-Depends: aajm
-
 Depends: an
 
 Depends: angband
@@ -23,6 +21,8 @@
 
 Depends: cavezofphear
 
+Depends: cbonsai
+
 Depends: colossal-cave-adventure
 
 Depends: crawl
diff -Nru debian-games-3.3/tasks/finest debian-games-4/tasks/finest
--- debian-games-3.3/tasks/finest   2021-02-19 01:29:47.0 +0100
+++ debian-games-4/tasks/finest 2021-07-04 08:50:03.0 +0200
@@ -82,8 +82,6 @@
 
 Depends: freeorion
 
-Depends: fretsonfire
-
 Depends: frozen-bubble

Bug#990710: unblock: jetty9/9.4.39-1

2021-07-05 Thread Markus Koschany 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package jetty9

[ Reason ]

Fixing CVE-2021-28169 and CVE-2021-34428

[ Impact ]

Version of Jetty 9 in Debian 11 is vulnerable

[ Tests ]

Integrated tests pass successfully

[ Risks ]

None, since all tests pass.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing


unblock jetty9/9.4.39-1
diff -Nru jetty9-9.4.39/debian/changelog jetty9-9.4.39/debian/changelog
--- jetty9-9.4.39/debian/changelog  2021-04-12 00:11:03.0 +0200
+++ jetty9-9.4.39/debian/changelog  2021-07-03 19:09:58.0 +0200
@@ -1,3 +1,23 @@
+jetty9 (9.4.39-2) unstable; urgency=high
+
+  * Team upload.
+  * Fix CVE-2021-28169:
+It is possible for requests to the ConcatServlet with a doubly encoded path
+to access protected resources within the WEB-INF directory. For example a
+request to `/concat?/%2557EB-INF/web.xml` can retrieve the web.xml file.
+This can reveal sensitive information regarding the implementation of a web
+application.
+  * Fix CVE-2021-34428:
+If an exception is thrown from the SessionListener#sessionDestroyed()
+method, then the session ID is not invalidated in the session ID manager.
+On deployments with clustered sessions and multiple contexts this can
+result in a session not being invalidated. This can result in an
+application used on a shared computer being left logged in.
+
+Thanks to Salvatore Bonaccorso for the report. (Closes: #98, #990578)
+
+ -- Markus Koschany   Sat, 03 Jul 2021 19:09:58 +0200
+
 jetty9 (9.4.39-1) unstable; urgency=high
 
   * New upstream release
diff -Nru jetty9-9.4.39/debian/patches/CVE-2021-28169.patch 
jetty9-9.4.39/debian/patches/CVE-2021-28169.patch
--- jetty9-9.4.39/debian/patches/CVE-2021-28169.patch   1970-01-01 
01:00:00.0 +0100
+++ jetty9-9.4.39/debian/patches/CVE-2021-28169.patch   2021-07-03 
19:09:58.0 +0200
@@ -0,0 +1,520 @@
+From: Markus Koschany 
+Date: Sat, 3 Jul 2021 19:01:20 +0200
+Subject: CVE-2021-28169
+
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=98
+Origin: 
https://github.com/eclipse/jetty.project/commit/1c05b0bcb181c759e98b060bded0b9376976b055
+---
+ .../org/eclipse/jetty/server/ResourceService.java  |   4 +-
+ .../org/eclipse/jetty/servlets/ConcatServlet.java  |   4 +-
+ .../org/eclipse/jetty/servlets/WelcomeFilter.java  |   8 +-
+ .../eclipse/jetty/servlets/ConcatServletTest.java  |  83 
+ .../eclipse/jetty/servlets/WelcomeFilterTest.java  | 143 +
+ .../jetty/webapp/WebAppDefaultServletTest.java | 142 
+ 6 files changed, 353 insertions(+), 31 deletions(-)
+ create mode 100644 
jetty-servlets/src/test/java/org/eclipse/jetty/servlets/WelcomeFilterTest.java
+ create mode 100644 
jetty-webapp/src/test/java/org/eclipse/jetty/webapp/WebAppDefaultServletTest.java
+
+diff --git 
a/jetty-server/src/main/java/org/eclipse/jetty/server/ResourceService.java 
b/jetty-server/src/main/java/org/eclipse/jetty/server/ResourceService.java
+index 1edfd83..c908e8d 100644
+--- a/jetty-server/src/main/java/org/eclipse/jetty/server/ResourceService.java
 b/jetty-server/src/main/java/org/eclipse/jetty/server/ResourceService.java
+@@ -240,7 +240,7 @@ public class ResourceService
+ // Find the content
+ content = _contentFactory.getContent(pathInContext, 
response.getBufferSize());
+ if (LOG.isDebugEnabled())
+-LOG.info("content={}", content);
++LOG.debug("content={}", content);
+ 
+ // Not found?
+ if (content == null || !content.getResource().exists())
+@@ -430,7 +430,7 @@ public class ResourceService
+ return;
+ }
+ 
+-RequestDispatcher dispatcher = 
context.getRequestDispatcher(welcome);
++RequestDispatcher dispatcher = 
context.getRequestDispatcher(URIUtil.encodePath(welcome));
+ if (dispatcher != null)
+ {
+ // Forward to the index
+diff --git 
a/jetty-servlets/src/main/java/org/eclipse/jetty/servlets/ConcatServlet.java 
b/jetty-servlets/src/main/java/org/eclipse/jetty/servlets/ConcatServlet.java
+index f6dde94..55700b4 100644
+--- 
a/jetty-servlets/src/main/java/org/eclipse/jetty/servlets/ConcatServlet.java
 
b/jetty-servlets/src/main/java/org/eclipse/jetty/servlets/ConcatServlet.java
+@@ -61,6 +61,7 @@ import org.eclipse.jetty.util.URIUtil;
+  * appropriate. This means that when not in development mode, the servlet 
must be
+  * restarted before changed content will be served.
+  */
++@Deprecated
+ public class ConcatServlet extends HttpServlet
+ {
+ private boolean _development;
+@@ -125,7 +126,8 @@ public class ConcatServlet extends HttpServlet
+ }
+ }
+ 
+-

Bug#990523: closed by Sebastian Ramacher (unblock expeyes)

2021-07-05 Thread Georges Khaznadar 
Thank you Sebastian :)

Debian Bug Tracking System a écrit :
> This is an automatic notification regarding your Bug report
> which was filed against the release.debian.org package:
> 
> #990523: unblock: expeyes/4.8.8+repack-2
> 
> It has been closed by Sebastian Ramacher .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Sebastian Ramacher 
>  by
> replying to this email.
> 
> 
> -- 
> 990523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990523
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> Date: Sun, 04 Jul 2021 19:31:40 +
> From: Sebastian Ramacher 
> Subject: unblock expeyes
> To: 990523-d...@bugs.debian.org
> X-Spam-Status: No, score=-7.7 required=4.0 tests=BAYES_00,DKIM_SIGNED,
>  DKIM_VALID,DKIM_VALID_AU,ONEWORDBODY,RCVD_IN_DNSWL_HI,SPF_HELO_NONE,
>  SPF_NONE,TVD_SPACE_RATIO,TXREP autolearn=ham autolearn_force=no
>  version=3.4.2-bugs.debian.org_2005_01_02
> Message-Id: 
> 
> Unblocked.

> Date: Thu, 01 Jul 2021 13:21:47 +0200
> From: Georges Khaznadar 
> Subject: unblock: expeyes/4.8.8+repack-2
> To: Debian Bug Tracking System 
> X-Spam-Status: No, score=-18.3 required=4.0 tests=BAYES_00,FOURLA,
>  FROMDEVELOPER,FVGT_m_MULTI_ODD,GMAIL,HAS_PACKAGE,MONEY,
>  RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,
>  SPF_NONE,STOCKLIKE,TXREP,WORD_WITHOUT_VOWELS,XMAILER_REPORTBUG
>  autolearn=ham autolearn_force=no version=3.4.2-bugs.debian.org_2005_01_02
> Message-ID: <162513850741.4160097.11420299565151753286.reportbug@localhost>
> X-Mailer: reportbug 7.10.3
> 
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package expeyes
> 
> [ Reason ]
> As Andreas Beckman reported, in bug #990489, this package did
> not allow a smooth upgrade from buster to bullseye. The reason was
> a declared conflict with package modemmanager.
> 
> Now this bug has been fixed.
> 
> [ Impact ]
> The binary package eyes17, built from expeyes, is used by
> a few thousands of students and teachers in Kerala (a southern
> Indian state), since the Eyes17 box has been officially endorsed
> by Kerala's academic authorities to teach experimental physics in
> high schools. Some people there update their system with Debian,
> most with Ubuntu. Having expeyes in Debian stable is useful for
> this community.
> 
> [ Tests ]
> Manual tests only:
> - the Eyes17 box communicates smoothly by the serial link, with
>   the package modemmanager installed, so expeyes software and
>   modemmanager are no longer conflicting.
> - installation/uninstallation of package eyes17 work as
>   expected.
> 
> [ Risks ]
> Expeyes software are leaf packages, so there is no reverse
> dependency.
> 
> [ Checklist ]
>   [x] all changes are documented in the d/changelog
>   [x] I reviewed all changes and I approve them
>   [x] attach debdiff against the package in testing
> 
> [ Other info ]
> Thank you in advance.
> 
> unblock expeyes/4.8.8+repack-2

> diff -Nru expeyes-4.8.7+repack/debian/changelog 
> expeyes-4.8.8+repack/debian/changelog
> --- expeyes-4.8.7+repack/debian/changelog 2020-12-10 16:45:11.0 
> +0100
> +++ expeyes-4.8.8+repack/debian/changelog 2021-07-01 10:50:55.0 
> +0200
> @@ -1,3 +1,30 @@
> +expeyes (4.8.8+repack-2) unstable; urgency=medium
> +
> +  * removed clauses conflicting with modemmanager. Closes: #990489
> +  * replaced calls to "service" by calls to "invoke-rc.d", thanks to
> +Andreas Beckman's hint.
> +
> + -- Georges Khaznadar   Thu, 01 Jul 2021 10:50:55 +0200
> +
> +expeyes (4.8.8+repack-1) unstable; urgency=medium
> +
> +  * new upstream changes
> +  * removed stale symlinks
> +  * restored documentation files in the upstream archive
> +  * made the clean target less agressive
> +
> + -- Georges Khaznadar   Mon, 26 Apr 2021 15:39:18 +0200
> +
> +expeyes (4.8.7+repack-5) unstable; urgency=medium
> +
> +  * included Camaleón's translation for po-debconf files, thanks!
> +Closes: #987479
> +  * added a command in d/rules to remove broken symlinks. Closes: #986480
> +  * removed python doctrees and .gitignore files from the package
> +(warned by lintian)
> +
> + -- Georges Khaznadar   Sun, 25 Apr 2021 18:41:30 +0200
> +
>  expeyes (4.8.7+repack-4) unstable; urgency=medium
>  
>* defined a conflict between packages eyes17 and older python-expeyes
> diff -Nru expeyes-4.8.7+repack/debian/control 
> expeyes-4.8.8+repack/debian/control
> --- expeyes-4.8.7+repack/debian/control   2020-12-10 16:45:11.0 
> +0100
> +++ expeyes-4.8.8+repack/debian/control   2021-07-01 10:50:55.0 
> +0200
> @@ -56,8 +56,7 @@
>   python3-serial
>  Recommends: fonts-lohit-mlym,
>   libreoffice
> -Conflicts: modemmanager,
> - python3-expeyes (<< 4.5.8+dfsg-2),
> +Conflicts: python3-expeyes (<< 4.5.8+dfsg-2),
>

Re: Six Bullseye packages that should be Priority: optional

2021-07-05 Thread Simon McVittie 
On Mon, 05 Jul 2021 at 02:30:00 -0500, Daniel Lewart wrote:
> Comparing important/required/standard packages between
> Buster and Bullseye, I noticed some inconsistencies.

We have been in hard freeze for almost 4 months[1], so I don't think
now is necessarily the right time to be changing what is in a default
installation of Debian (which is what the boundary between standard and
optional means) without release team approval.

I've cc'd the release team to see what they think.

I agree with your reasoning for why these packages should be
Priority: optional, and for any that cannot be changed in bullseye, the
beginning of the Debian 12 'bookworm' release cycle would be an excellent
time to make that change.

[1] https://release.debian.org/bullseye/freeze_policy.html

> If so, should I file one or multiple bugs against:

The ftp.debian.org pseudopackage is the right place to ask for priority
changes ("override changes"): individual packages' maintainers cannot
change this on their own. If you use reportbug, there's a template for
an override change.

It's probably best to Cc the package maintainer
(name_of_pack...@packages.debian.org) using the X-Debbugs-Cc mechanism,
because there is a suggested priority in the package's debian/control,
which the ftp team use as a basis for setting the priority of new packages.
(Yes, it's redundant, and there are probably better ways this could be
controlled, but this is what we have at the moment.)

> 1) override: bind9-dnsutils:net/optional
>   * Currently net/standard
>   * Justification: Buster dnsutils is net/optional

This is essentially asking: should the DNS utilities (dig, nslookup etc.)
be installed by default even if nothing else depends on them? and changing
the answer to that question seems a disruptive thing to be doing during
hard freeze.

These have relatively "heavy" dependencies, so they are probably the
highest-impact in terms of reducing the size of a default installation;
but they also seem like the highest-risk in terms of potentially exposing
bugs where packages rely on these utilities without declaring a dependency.

> 2) override: bind9-libs:libs/optional
> 5) override: libreadline8:libs/optional
>   * Justification: Debian Policy 2.5

I agree that shared libraries should be Priority: optional. They will be
pulled in by dependencies if they are needed.

bind9-libs is pulled in by bind9-dnsutils, so there is no point in changing
that priority unless bind9-dnsutils is also changed.

libreadline8 is quite small, so the impact of installing it unnecessarily
is low.

> 3) override: gcc-9-base:libs/optional
> 4) override: gcc-10-base:libs/optional
>   * Currently libs/required

These are not *really* shared libraries, but the same reasoning applies,
and I agree they should be Priority: optional.

If I'm reading correctly, gcc-9-base is included in default installations
of Debian 11, even though nothing else built by src:gcc-9 is, nicely
demonstrating why Policy §2.5 changed to its current contents. This seems
like it's obviously a bug (200K of licenses and documentation are installed
unnecessarily), and unlike the other genuine bugs you've mentioned here,
this one seems low-risk to fix, because gcc-9-base only contains
documentation.

In practice gcc-10-base will be installed anyway, as a result of libgcc-s1
depending on it, so that change would have no practical effect right now;
but moving it to Priority: optional would avoid having the same bug as for
gcc-9-base when we upgrade to gcc-11 or later in a future Debian release.

> 6) override: mime-support:oldlibs/optional
>   * Currently net/standard
>   * Justificatino: Transtional package

mime-support depends on mailcap (Priority: optional) and media-types
(Priority: standard), so downgrading mime-support to optional would mean
that mailcap (compose(1), edit(1), see(1), print(1)) would not be installed
by default. That seems like it has a risk of exposing bugs where packages
rely on those tools without declaring a dependency.

I agree that this should be oldlibs/optional, but 4 months into hard freeze
doesn't seem like the right time to change it.

smcv

Re: youtube-dl: needs version update to 2021.05.16 to continue working with youtube

2021-07-05 Thread Holger Levsen 
Hi Andreas,

[diclaimer: i'm not a release team member.]

On Fri, Jul 02, 2021 at 05:31:48AM +0200, Andreas Tille wrote:
> Hi release team,
[...]
> I do not want to do an upload to unstable without your agreement and I
> hope you can come up with some good advise what to do.
[...]

a.) since about 10 years or so the release team asks for bugs to be filed for 
such
requests, as debian-release is a too busy mailing list so things are likely to
fall under the carpet if not.

b.) if *you* think the changes are suitable for bullseye, you can upload to 
unstable.

c.) if you are unsure, you can always upload to experimental.

d.) if no diff is provided, either here in a bug or via an upload, how should 
the
release team evaluate your request? So, please either upload or attach the diff
here^win a bug against release.debian.org which is yet to be filed.

> PS: Please be so kind to CC me in your replies.

done.


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

In Europe there are people prosecuted by courts because they saved other people
from drowning in the  Mediterranean Sea.  That is almost as absurd  as if there
were people being prosecuted because they save humans from drowning in the sea.


signature.asc
Description: PGP signature

Processed: Re: Bug#990670: [pre-approval] unblock: python-apt/2.2.1

2021-07-05 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 - moreinfo
Bug #990670 [release.debian.org] [pre-approval] unblock: python-apt/2.2.1
Removed tag(s) moreinfo.

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

Bug#990670: [pre-approval] unblock: python-apt/2.2.1

2021-07-05 Thread Julian Andres Klode 
Control: tags -1 - moreinfo

On Sun, Jul 04, 2021 at 09:27:35PM +0200, Sebastian Ramacher wrote:
> Control: tags -1 confirmed moreinfo
> 
> On 2021-07-04 14:25:00 +0200, Julian Andres Klode wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: unblock
> > X-Debbugs-Cc: j...@debian.org
> > 
> > Please unblock package python-apt
> > 
> > [ Reason ]
> > 
> > - Mark python-apt-common as Multi-Arch: common to unblock the
> >   crossgrader script (#968458). People have very varied understanding
> >   about severity of this; it's just a single line anyway.
> > - update the mirror lists.
> > 
> > [ Impact ]
> > People can't crossgrade and might see outdated mirror information
> > in mirror selection tools like software-properties
> > 
> > [ Tests ]
> > No code changed, just metadata. Unit tests are run at
> > build time and during autopkgtest.
> > 
> > 
> > [ Risks ]
> > 
> > It's just metadata changes, only risk is like regressions
> > in toolchain since last upload.
> > 
> > [ Checklist ]
> >   [x] all changes are documented in the d/changelog
> >   [x] I reviewed all changes and I approve them
> >   [x] attach debdiff against the package in testing
> > 
> > unblock python-apt/2.2.1
> 
> ACK, please remove the moreinfo tag once the ne wversion is available in
> unstable.

It landed

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


signature.asc
Description: PGP signature

Bug#990530: unblock: horizon/18.6.2-4 and all of its plugins

2021-07-05 Thread Thomas Goirand 
On 7/4/21 8:21 PM, Thomas Goirand wrote:
> On 7/1/21 10:48 PM, Sebastian Ramacher wrote:
>>> magnum-ui/7.0.0-2
>>
>> This seems to be missing an upload.
> 
> magnum-ui uploaded.

unblock: magnum-ui/7.0.0-2

>>> sahara-dashboard/13.0.0-2
>>
>> This introduces piuparts regressions.

It has a wrong Breaks: version, this is fixed:

unblock: sahara-dashboard/13.0.0-2

>>
>>> vitrage-dashboard/3.2.0-3
>>
>> This only seems to have a changelog entry.

Indeed. Fixed:
unblock: vitrage-dashboard/2.0.0-4

Cheers,

Thomas Goirand (zigo)