NEW changes in oldstable-new

[Debian FTP Masters]

Processing changes file: linux_4.9.189-1_armhf.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: debian-edu-config_2.10.65+deb10u1_all.changes
  ACCEPT
Processing changes file: lacme_0.5-1+deb10u1_all.changes
  ACCEPT
Processing changes file: linux-latest_105+deb10u1_all.changes
  ACCEPT
Processing changes file: linux-latest_105+deb10u1_amd64.changes
  ACCEPT
Processing changes file: linux-latest_105+deb10u1_arm64.changes
  ACCEPT
Processing changes file: linux-latest_105+deb10u1_armel.changes
  ACCEPT
Processing changes file: linux-latest_105+deb10u1_armhf.changes
  ACCEPT
Processing changes file: linux-latest_105+deb10u1_i386.changes
  ACCEPT
Processing changes file: linux-latest_105+deb10u1_mips.changes
  ACCEPT
Processing changes file: linux-latest_105+deb10u1_mips64el.changes
  ACCEPT
Processing changes file: linux-latest_105+deb10u1_mipsel.changes
  ACCEPT
Processing changes file: linux-latest_105+deb10u1_ppc64el.changes
  ACCEPT
Processing changes file: linux-latest_105+deb10u1_s390x.changes
  ACCEPT

NEW changes in oldstable-new

[Debian FTP Masters]

Processing changes file: linux_4.9.189-1_i386.changes
  ACCEPT

NEW changes in oldstable-new

[Debian FTP Masters]

Processing changes file: linux_4.9.189-1_armel.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: sendmail_8.15.2-14~deb10u1_mips64el.changes
  ACCEPT
Processing changes file: sendmail_8.15.2-14~deb10u1_mipsel.changes
  ACCEPT
Processing changes file: slirp4netns_0.2.3-1_mips64el.changes
  ACCEPT
Processing changes file: slirp4netns_0.2.3-1_mipsel.changes
  ACCEPT

NEW changes in oldstable-new

[Debian FTP Masters]

Processing changes file: linux_4.9.189-1_amd64.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: clamav_0.101.4+dfsg-0+deb10u1_mips64el.changes
  ACCEPT
Processing changes file: clamav_0.101.4+dfsg-0+deb10u1_mipsel.changes
  ACCEPT
Processing changes file: cups_2.2.10-6+deb10u1_mips64el.changes
  ACCEPT
Processing changes file: cups_2.2.10-6+deb10u1_mipsel.changes
  ACCEPT

NEW changes in oldstable-new

[Debian FTP Masters]

Processing changes file: cups_2.2.1-8+deb9u4_mipsel.changes
  ACCEPT

NEW changes in oldstable-new

[Debian FTP Masters]

Processing changes file: clamav_0.101.4+dfsg-0+deb9u1_armel.changes
  ACCEPT
Processing changes file: clamav_0.101.4+dfsg-0+deb9u1_mips64el.changes
  ACCEPT
Processing changes file: clamav_0.101.4+dfsg-0+deb9u1_mipsel.changes
  ACCEPT
Processing changes file: cups_2.2.1-8+deb9u4_armel.changes
  ACCEPT
Processing changes file: cups_2.2.1-8+deb9u4_armhf.changes
  ACCEPT
Processing changes file: cups_2.2.1-8+deb9u4_mips.changes
  ACCEPT
Processing changes file: cups_2.2.1-8+deb9u4_mips64el.changes
  ACCEPT
Processing changes file: linux_4.9.189-1_arm64.changes
  ACCEPT
Processing changes file: linux_4.9.189-1_ppc64el.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: clamav_0.101.4+dfsg-0+deb10u1_armel.changes
  ACCEPT
Processing changes file: clamav_0.101.4+dfsg-0+deb10u1_i386.changes
  ACCEPT
Processing changes file: clamav_0.101.4+dfsg-0+deb10u1_mips.changes
  ACCEPT
Processing changes file: clamav_0.101.4+dfsg-0+deb10u1_ppc64el.changes
  ACCEPT
Processing changes file: cups_2.2.10-6+deb10u1_armel.changes
  ACCEPT
Processing changes file: cups_2.2.10-6+deb10u1_i386.changes
  ACCEPT
Processing changes file: cups_2.2.10-6+deb10u1_mips.changes
  ACCEPT
Processing changes file: cups_2.2.10-6+deb10u1_ppc64el.changes
  ACCEPT
Processing changes file: sendmail_8.15.2-14~deb10u1_amd64.changes
  ACCEPT
Processing changes file: sendmail_8.15.2-14~deb10u1_armel.changes
  ACCEPT
Processing changes file: sendmail_8.15.2-14~deb10u1_i386.changes
  ACCEPT
Processing changes file: sendmail_8.15.2-14~deb10u1_mips.changes
  ACCEPT
Processing changes file: sendmail_8.15.2-14~deb10u1_ppc64el.changes
  ACCEPT
Processing changes file: slirp4netns_0.2.3-1_amd64.changes
  ACCEPT
Processing changes file: slirp4netns_0.2.3-1_armel.changes
  ACCEPT
Processing changes file: slirp4netns_0.2.3-1_i386.changes
  ACCEPT
Processing changes file: slirp4netns_0.2.3-1_mips.changes
  ACCEPT
Processing changes file: slirp4netns_0.2.3-1_ppc64el.changes
  ACCEPT

Bug#935770: buster-pu: package ncbi-tools6/6.1.20170106+dfsg1-0+deb10u2

[Aaron M. Ucko]

"Adam D. Barratt"  writes:

> Please go ahead. Thanks for the fix.

Uploaded, thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

NEW changes in oldstable-new

[Debian FTP Masters]

Processing changes file: clamav_0.101.4+dfsg-0+deb9u1_all.changes
  ACCEPT
Processing changes file: clamav_0.101.4+dfsg-0+deb9u1_amd64.changes
  ACCEPT
Processing changes file: clamav_0.101.4+dfsg-0+deb9u1_arm64.changes
  ACCEPT
Processing changes file: clamav_0.101.4+dfsg-0+deb9u1_armhf.changes
  ACCEPT
Processing changes file: clamav_0.101.4+dfsg-0+deb9u1_i386.changes
  ACCEPT
Processing changes file: clamav_0.101.4+dfsg-0+deb9u1_mips.changes
  ACCEPT
Processing changes file: clamav_0.101.4+dfsg-0+deb9u1_ppc64el.changes
  ACCEPT
Processing changes file: clamav_0.101.4+dfsg-0+deb9u1_s390x.changes
  ACCEPT
Processing changes file: cups_2.2.1-8+deb9u4_all.changes
  ACCEPT
Processing changes file: cups_2.2.1-8+deb9u4_amd64.changes
  ACCEPT
Processing changes file: cups_2.2.1-8+deb9u4_arm64.changes
  ACCEPT
Processing changes file: cups_2.2.1-8+deb9u4_i386.changes
  ACCEPT
Processing changes file: cups_2.2.1-8+deb9u4_ppc64el.changes
  ACCEPT
Processing changes file: cups_2.2.1-8+deb9u4_s390x.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: clamav_0.101.4+dfsg-0+deb10u1_all.changes
  ACCEPT
Processing changes file: clamav_0.101.4+dfsg-0+deb10u1_amd64.changes
  ACCEPT
Processing changes file: clamav_0.101.4+dfsg-0+deb10u1_arm64.changes
  ACCEPT
Processing changes file: clamav_0.101.4+dfsg-0+deb10u1_armhf.changes
  ACCEPT
Processing changes file: clamav_0.101.4+dfsg-0+deb10u1_s390x.changes
  ACCEPT
Processing changes file: cups_2.2.10-6+deb10u1_all.changes
  ACCEPT
Processing changes file: cups_2.2.10-6+deb10u1_amd64.changes
  ACCEPT
Processing changes file: cups_2.2.10-6+deb10u1_arm64.changes
  ACCEPT
Processing changes file: cups_2.2.10-6+deb10u1_armhf.changes
  ACCEPT
Processing changes file: cups_2.2.10-6+deb10u1_s390x.changes
  ACCEPT
Processing changes file: sendmail_8.15.2-14~deb10u1_all.changes
  ACCEPT
Processing changes file: sendmail_8.15.2-14~deb10u1_arm64.changes
  ACCEPT
Processing changes file: sendmail_8.15.2-14~deb10u1_armhf.changes
  ACCEPT
Processing changes file: sendmail_8.15.2-14~deb10u1_s390x.changes
  ACCEPT
Processing changes file: slirp4netns_0.2.3-1_arm64.changes
  ACCEPT
Processing changes file: slirp4netns_0.2.3-1_armhf.changes
  ACCEPT
Processing changes file: slirp4netns_0.2.3-1_s390x.changes
  ACCEPT
Processing changes file: win32-loader_0.9.4+deb10u2_all.changes
  ACCEPT

Re: vacation 3.3.2 MIGRATED to testing

[Bastian Blank]

On Sun, Aug 25, 2019 at 11:49:31AM +0100, Ian Jackson wrote:
> Hi.  I think something went wrong with testing migration here.
> 3.3.2, which is now in testing, was *not* built on the buildds.
> Yesterday's excuses gave that as the reason for vacation not
> migrating.  So I did a source-only re-upload, 3.3.3.
> But it seems that britney has migrated 3.3.2.

Please state your problem more clearly.  Neither britney, nor the
migration notification can defy time.

So when britney saw 3.3.2 ready, it migrated it.  This check is AFAIK
done on the state from the last mirror run.  Some time later there is a
notification.  But it can't see that your upload of 3.3.3 is pending and
don't migrate 3.3.2 because it will be overriden.

Bastian

-- 
In the strict scientific sense we all feed on death -- even vegetarians.
-- Spock, "Wolf in the Fold", stardate 3615.4

Bug#935809: Re: buster-pu: package fdroidserver_1.1.4-1~deb10u1

[Hans-Christoph Steiner]

Adam D. Barratt:
> Control: tags -1 + moreinfo
> 
> Your report did not make it to debian-release due to the large size of
> the attachment. I had to download the mbox from the BTS is order to
> reply, which makes me quite surprised to see that you already decided
> to upload the package.
> 
> On Mon, 2019-08-26 at 14:54 +0200, Hans-Christoph Steiner wrote:
>> I have been working on polishing this package for buster since March,
>> but I didn't make the freeze cutoff.  I'm part of upstream, and we
>> did
>> our Debian/buster bug fix work in our stable 1.1.x branch, so the
>> changes are mostly in the upstream source tarball.
>>
>> The debdiff is long, but the actual code changes are quite short.
> 
> If the changes are short, why were they not made in time for buster?

They are mostly from compatibility bugs discovered since the final
buster freeze.  Some were fixed before the freeze, but we spent a lot of
time testing this package on buster, so we wanted until the tests were
complete before requesting an unblock.  This release is meant to be an
LTS for fdroidserver, and we'll be working to get it into other distros too.


>>   What
>> makes the debdiff long is the cruft that were removed upstream in the
>> source tarball due to a cleanup (see diffstat).
> 
> Are you really saying that what looks from the diff like dropping all
> localisation support is cruft cleanup? I feel like I may be missing
> something.

The localization was not removed.  The localization user-editable .po
files were removed while the .mo files are still there, which are what
are actually used to display the strings..  The .mo files can be
converted back to .po files as needed using msgunfmt, so they are also
"source".

> In any case, cleaning up cruft by removing 60K lines of files from your
> source package is generally not the sort of thing that would be
> expected in a stable update.

Yeah, this is annoying for sure. This cleanup was not triggered by me,
it came from creating the source tarball on buster, while v1.1.1 was
created on stretch.  The update to the standard Python tools that
generate source tarballs seems to be the cause.  I only noticed this
after the release was done and uploaded. Sorry.


>> The next largest block of changes is fixes to the test suite to work
>> properly on Debian/buster.
>>  The remaining changes are compatibility fixes related to:
>>
>> 929905: incompatible with upstream's data repository
> [...]
>> ### 1.1.4 (2019-08-15)
>>
>> * include bitcoin validation regex required by fdroiddata
> 
> As someone who knows nothing about fdroiddata, you may have to explain
> why this is actually a problem. This is the sort of information that
> should be in the request. To be honest, I'd have expected your upstream
> diff and changelog to have included more information than that one
> line.

fdroiddata is like the collection of *.debian.tar.gz files for all the
apps built by F-Droid.  It is the collection of metadata, build
instructions, and patches actually used to run the builds.  For anyone
who wants to contribute work related to apps in F-Droid, they need to
use fdroidserver.  These changes make buster's version work with all of
the files currently in the fdroiddata collection (its about 3000 apps
currently).

> Please provide a diff that only includes the non-"cruft" changes, so
> there's a chance of us knowing what you're actually changing.

I attached an excerpted debdiff without the aforementioned source
tarball removals. Here's the diff to show which files were removed in
this debdiff excerpt:

--- fdroidserver_1.1.1-1_1.1.4-1.debdiff
+++ fdroidserver_1.1.1-1_1.1.4-1~deb10u1_excerpt.debdiff
- .gitignore |   59
- .gitlab-ci.yml |  198 --
- .pylint-rcfile |   45
- .travis.yml|  109 -
  CHANGELOG.md   |   16
- MANIFEST.in|  550 ++
  PKG-INFO   |6
- buildserver/.gitignore |4
  completion/bash-completion |4
  debian/changelog   |   31
  debian/control |2
  fdroidserver.egg-info/PKG-INFO |6
  fdroidserver.egg-info/SOURCES.txt  |   38
  fdroidserver.egg-info/requires.txt |   20
  fdroidserver/index.py  |1
  fdroidserver/metadata.py   |2
  fdroidserver/nightly.py|8
  fdroidserver/publish.py|2
  fdroidserver/scanner.py|1
  fdroidserver/server.py |6
- hooks/install-hooks.sh |   30
- hooks/pre-commit   |  136 -
- jenkins-build-all  |  107 -
- jenkins-setup-build-environment|  119 -
- jenkins-test   |   78
- 

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: debian-edu-config_2.10.65+deb10u1_source.changes
  ACCEPT
Processing changes file: lacme_0.5-1+deb10u1_source.changes
  ACCEPT
Processing changes file: linux-latest_105+deb10u1_source.changes
  ACCEPT

Bug#917972: transition: openexr

[Matteo F. Vescovi]

Hi!

On 2019-08-25 at 14:15 (+01), Jonathan Wiltshire wrote:
> Is this transition ready to go?

I probably need to re-test some of the reverse dependencies.
Give me a bunch of days and I'll ping you back with the results.


-- 
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A


signature.asc
Description: PGP signature

Processed: lacme 0.5-1+deb10u1 flagged for acceptance

[Debian Bug Tracking System]

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

> package release.debian.org
Limiting to bugs with field 'package' containing at least one of 
'release.debian.org'
Limit currently set to 'package':'release.debian.org'

> tags 935370 = buster pending
Bug #935370 [release.debian.org] buster-pu: package lacme/0.5-1+deb10u1
Added tag(s) pending; removed tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#935776: debian-edu-config 2.10.65+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 935776 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: debian-edu-config
Version: 2.10.65+deb10u1

Explanation: use PXE option 'ipappend 2' for LTSP client boot; fix sudo-ldap 
configuration; fix loss of dynamically allocated v4 IP address; several fixes 
and improvements to debian-edu-config.fetch-ldap-cert

Bug#935370: lacme 0.5-1+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 935370 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: lacme
Version: 0.5-1+deb10u1

Explanation: update for removal of unauthenticated GET support from the Let's 
Encrypt ACMEv2 API

Processed: debian-edu-config 2.10.65+deb10u1 flagged for acceptance

[Debian Bug Tracking System]

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

> package release.debian.org
Limiting to bugs with field 'package' containing at least one of 
'release.debian.org'
Limit currently set to 'package':'release.debian.org'

> tags 935776 = buster pending
Bug #935776 [release.debian.org] buster-pu: [pre-upload approval of] package 
debian-edu-config/2.10.65+deb10u1
Added tag(s) pending; removed tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#935776: buster-pu: [pre-upload approval of] package debian-edu-config/2.10.65+deb10u1

[Mike Gabriel]

hi,

On  Mo 26 Aug 2019 19:35:20 CEST, Adam D. Barratt wrote:


Control: tags -1 -moreinfo +confirmed

On Mon, 2019-08-26 at 17:18 +, Mike Gabriel wrote:

Hi Adam,

On  Mo 26 Aug 2019 18:54:30 CEST, Adam D. Barratt wrote:

> Control: tags -1 +moreinfo
>
> On Mon, 2019-08-26 at 08:17 +0200, Mike Gabriel wrote:
> > for Debian Edu 10.1, we'd kindly ask to accept the below fixes
> > into
> > Debian 10.1:
> >
> > ### Common Bug Fixes
> >
> > +debian-edu-config (2.10.65+deb10u1) buster; urgency=medium
> >
>
> Have all of the changes already been applied to the package in
> unstable?

[...]

> Yes, all chanes are already in unstable.


OK, thanks. Please go ahead.

Regards,

Adam


Uploaded.

Mike
--

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

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



pgp7mzEZjgSxq.pgp
Description: Digitale PGP-Signatur

NEW changes in oldstable-new

[Debian FTP Masters]

Processing changes file: clamav_0.101.4+dfsg-0+deb9u1_source.changes
  ACCEPT
Processing changes file: cups_2.2.1-8+deb9u4_source.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: clamav_0.101.4+dfsg-0+deb10u1_source.changes
  ACCEPT
Processing changes file: cups_2.2.10-6+deb10u1_source.changes
  ACCEPT
Processing changes file: sendmail_8.15.2-14~deb10u1_source.changes
  ACCEPT
Processing changes file: slirp4netns_0.2.3-1_source.changes
  ACCEPT
Processing changes file: win32-loader_0.9.4+deb10u2_source.changes
  ACCEPT

Re: Status of libghc-shake-dev

[Joachim Breitner]

Hi,


Am Montag, den 26.08.2019, 16:36 + schrieb PICCA Frederic-Emmanuel:
> > I just scheduled the set of binNMUs seemingly required Haskell. I hope
> > this was the right thing to do at this time. Really someone more active
> > should take over that job.
> 
> Where is the documentation of this process ?


I thought I wrote it down somewhere, but I can’t find it… anyways, it’s
not much:

1. Get permissions from the wanna-build team.
2. Compile https://salsa.debian.org/haskell-team/tools/tree/master/binnmus
   for stable
   (My hack of doing so is this:
   
https://salsa.debian.org/haskell-team/tools/blob/master/deploy-binNMU-to-wuiet.sh)
3. On wuiet, run
   ./binNMUs --priority -100  --sql > binNMUs.txt
4. Inspect the file if it makes sense
   (I stopped doing that at some point, though.)
5. Run 
   wb < binNMUs.txt


The file
https://people.debian.org/~nomeata/binNMUs-haskell.txt
is created on paradis by the following line in my crontab:

13 */4 * * * ./binNMUs --priority -100 --arches amd64 -q > 
public_html/binNMUs-haskell-amd64.txt;  ./binNMUs --priority -100 -q > 
public_html/binNMUs-haskell.txt;  ./binNMUs --regex 
'lib(.*)-ocaml-(?:dev-)?([0-9a-z]{5})' -q --present-problems > 
public_html/binNMUs-ocaml.txt

If someone else takes over, then maybe this should also be moved from
my account.

Cheers,
Joachim

-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


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

Bug#935830: marked as done (nmu: libgit2_0.28.1+dfsg.1-0.1)

[Debian Bug Tracking System]

Your message dated Mon, 26 Aug 2019 21:06:35 +0200
with message-id <9bb2a7e6-b2ad-f1ea-8431-93cb35da2...@debian.org>
and subject line Re: Bug#935830: nmu: libgit2_0.28.1+dfsg.1-0.1
has caused the Debian Bug report #935830,
regarding nmu: libgit2_0.28.1+dfsg.1-0.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.)


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

libgit2 is uninstallable in experimental. Please queue:

nmu libgit2_0.28.1+dfsg.1-0.1 . ANY . experimental . -m "rebuild against 
http-parser 2.9"

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Hi Simon,

On 26-08-2019 20:01, Simon McVittie wrote:
> nmu libgit2_0.28.1+dfsg.1-0.1 . ANY . experimental . -m "rebuild against 
> http-parser 2.9"

Scheduled.

Paul



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#935708: clamav 0.101.4+dfsg-0+deb9u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 935708 = stretch pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: clamav
Version: 0.101.4+dfsg-0+deb9u1

Explanation: new upstream stable release with security fixes - add scan time 
limit to mitigate against zip-bombs [CVE-2019-12625]; fix out-of-bounds write 
within the NSIS bzip2 library [CVE-2019-12900]

Processed: tagging 935254

[Debian Bug Tracking System]

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

> tags 935254 + stretch
Bug #935254 [release.debian.org] stretch-pu: package cups/2.2.1-8+deb9u4
Ignoring request to alter tags of bug #935254 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#935254: cups 2.2.1-8+deb9u4 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 935254 = stretch pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: cups
Version: 2.2.1-8+deb9u4

Explanation: fix multiple security/disclosure issues - SNMP buffer overflows 
[CVE-2019-8696 CVE-2019-8675], IPP buffer overflow, Denial of Service and 
memory disclosure issues in the scheduler

Processed: cups 2.2.1-8+deb9u4 flagged for acceptance

[Debian Bug Tracking System]

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

> package release.debian.org
Limiting to bugs with field 'package' containing at least one of 
'release.debian.org'
Limit currently set to 'package':'release.debian.org'

> tags 935254 = stretch pending
Bug #935254 [release.debian.org] stretch-pu: package cups/2.2.1-8+deb9u4
Added tag(s) stretch and pending; removed tag(s) confirmed.
> thanks
Stopping processing here.

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

Processed: clamav 0.101.4+dfsg-0+deb9u1 flagged for acceptance

[Debian Bug Tracking System]

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

> package release.debian.org
Limiting to bugs with field 'package' containing at least one of 
'release.debian.org'
Limit currently set to 'package':'release.debian.org'

> tags 935708 = stretch pending
Bug #935708 [release.debian.org] stretch-pu: package 
clamav/0.101.4+dfsg-0+deb9u1
Added tag(s) pending; removed tag(s) confirmed.
> thanks
Stopping processing here.

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

Processed: cups 2.2.10-6+deb10u1 flagged for acceptance

[Debian Bug Tracking System]

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

> package release.debian.org
Limiting to bugs with field 'package' containing at least one of 
'release.debian.org'
Limit currently set to 'package':'release.debian.org'

> tags 935253 = buster pending
Bug #935253 [release.debian.org] buster-pu: package cups/2.2.10-6+deb10u1
Added tag(s) pending; removed tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#935704: sendmail 8.15.2-14~deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 935704 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: sendmail
Version: 8.15.2-14~deb10u1

Explanation: sendmail-bin.postinst, initscript: Let start-stop-daemon match on 
pidfile and executable; sendmail-bin.prerm: Stop sendmail before removing the 
alternatives

Processed: sendmail 8.15.2-14~deb10u1 flagged for acceptance

[Debian Bug Tracking System]

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

> package release.debian.org
Limiting to bugs with field 'package' containing at least one of 
'release.debian.org'
Limit currently set to 'package':'release.debian.org'

> tags 935704 = buster pending
Bug #935704 [release.debian.org] buster-pu: package sendmail/8.15.2-14~deb10u1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: slirp4netns 0.2.3-1 flagged for acceptance

[Debian Bug Tracking System]

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

> package release.debian.org
Limiting to bugs with field 'package' containing at least one of 
'release.debian.org'
Limit currently set to 'package':'release.debian.org'

> tags 935719 = buster pending
Bug #935719 [release.debian.org] buster-pu: package slirp4netns/0.2.3-1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: clamav 0.101.4+dfsg-0+deb10u1 flagged for acceptance

[Debian Bug Tracking System]

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

> package release.debian.org
Limiting to bugs with field 'package' containing at least one of 
'release.debian.org'
Limit currently set to 'package':'release.debian.org'

> tags 935707 = buster pending
Bug #935707 [release.debian.org] buster-pu: package 
clamav/0.101.4+dfsg-0+deb10u1
Added tag(s) pending; removed tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#935707: clamav 0.101.4+dfsg-0+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 935707 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: clamav
Version: 0.101.4+dfsg-0+deb10u1

Explanation: new upstream stable release with security fixes - add scan time 
limit to mitigate against zip-bombs [CVE-2019-12625]; fix out-of-bounds write 
within the NSIS bzip2 library [CVE-2019-12900]

Bug#935253: cups 2.2.10-6+deb10u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 935253 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: cups
Version: 2.2.10-6+deb10u1

Explanation: fix multiple security/disclosure issues - SNMP buffer overflows 
[CVE-2019-8696 CVE-2019-8675], IPP buffer overflow, Denial of Service and 
memory disclosure issues in the scheduler

Bug#935719: slirp4netns 0.2.3-1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 935719 = buster pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: slirp4netns
Version: 0.2.3-1

Explanation: new upstream stable release with security fixes - check sscanf 
result when emulating ident [CVE-2019-9824]; fixes heap overflow in included 
libslirp [CVE-2019-14378]

Bug#935830: nmu: libgit2_0.28.1+dfsg.1-0.1

[Simon McVittie]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

libgit2 is uninstallable in experimental. Please queue:

nmu libgit2_0.28.1+dfsg.1-0.1 . ANY . experimental . -m "rebuild against 
http-parser 2.9"

Thanks,
smcv

NEW changes in oldstable-new

[Debian FTP Masters]

Processing changes file: linux_4.9.189-1_multi.changes
  ACCEPT

Processed: Re: Bug#935827: buster-pu: package cryptsetup/2:2.1.0-5+deb10u2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + d-i confirmed
Bug #935827 [release.debian.org] buster-pu: package cryptsetup/2:2.1.0-5+deb10u2
Added tag(s) confirmed and d-i.

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

Bug#935827: buster-pu: package cryptsetup/2:2.1.0-5+deb10u2

[Adam D. Barratt]

Control: tags -1 + d-i confirmed

On Mon, 2019-08-26 at 19:18 +0200, Guilhem Moulin wrote:
> Another regression was found in cryptsetup :-/  Its scope is quite
> narrow as it only affects mapped device size ≥2TiB (2³² 512-bits
> sectors) on 32-bits platforms.  And AFAICT ‘crypt’ targets are not
> affected, only ‘integrity’ ones are; both standalone dm-integrity
> volumes set up with integritysetup(8), as well as volumes used for
> *experimental* authenticated disk encryption and set
> up with cryptsetup(8).
> 
> In these scenarios the size overflows (due to size_t being
> incorrectly used in place of uint64_t) and the device is mapped with
> a truncated size.  There is a risk of data loss if the user writes
> inside the container, for instance while trying to recover it, so
> that should IMHO be fixed via s-p-u.
> 
> This is an upstream regression from 2.1.0, so Stretch is not
> affected. 2:2.2.0-3 from Sid contains the cherry-picked upstream fix,
> but Buster's 2:2.1.0-5 (and 2:2.1.0-5+deb10u1) is affected.
[...]
> Given that Buster currently has 2:2.1.0-5, should the .changes
> include all
> changes since that version, or only since 2:2.1.0-5+deb10u1?

+deb10u1 is already in the archive, so this would be no different from
any other upload. (i.e. just since +deb10u1.)

Regards,

Adam

Processed: Re: Bug#935776: buster-pu: [pre-upload approval of] package debian-edu-config/2.10.65+deb10u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -moreinfo +confirmed
Bug #935776 [release.debian.org] buster-pu: [pre-upload approval of] package 
debian-edu-config/2.10.65+deb10u1
Removed tag(s) moreinfo.
Bug #935776 [release.debian.org] buster-pu: [pre-upload approval of] package 
debian-edu-config/2.10.65+deb10u1
Added tag(s) confirmed.

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

Bug#935776: buster-pu: [pre-upload approval of] package debian-edu-config/2.10.65+deb10u1

[Adam D. Barratt]

Control: tags -1 -moreinfo +confirmed

On Mon, 2019-08-26 at 17:18 +, Mike Gabriel wrote:
> Hi Adam,
> 
> On  Mo 26 Aug 2019 18:54:30 CEST, Adam D. Barratt wrote:
> 
> > Control: tags -1 +moreinfo
> > 
> > On Mon, 2019-08-26 at 08:17 +0200, Mike Gabriel wrote:
> > > for Debian Edu 10.1, we'd kindly ask to accept the below fixes
> > > into
> > > Debian 10.1:
> > > 
> > > ### Common Bug Fixes
> > > 
> > > +debian-edu-config (2.10.65+deb10u1) buster; urgency=medium
> > > 
> > 
> > Have all of the changes already been applied to the package in
> > unstable?
[...]
> > Yes, all chanes are already in unstable.

OK, thanks. Please go ahead.

Regards,

Adam

Bug#935776: buster-pu: [pre-upload approval of] package debian-edu-config/2.10.65+deb10u1

[Mike Gabriel]

Hi Adam,

On  Mo 26 Aug 2019 18:54:30 CEST, Adam D. Barratt wrote:


Control: tags -1 +moreinfo

On Mon, 2019-08-26 at 08:17 +0200, Mike Gabriel wrote:

for Debian Edu 10.1, we'd kindly ask to accept the below fixes into
Debian 10.1:

### Common Bug Fixes

+debian-edu-config (2.10.65+deb10u1) buster; urgency=medium



Have all of the changes already been applied to the package in
unstable?

Regards,

Adam


Yes, all chanes are already in unstable.

Mike
--

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

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



pgpXtwNGdxQlO.pgp
Description: Digitale PGP-Signatur

Bug#935827: buster-pu: package cryptsetup/2:2.1.0-5+deb10u2

[Guilhem Moulin]

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

Dear release team,

Another regression was found in cryptsetup :-/  Its scope is quite narrow as
it only affects mapped device size ≥2TiB (2³² 512-bits sectors) on 32-bits
platforms.  And AFAICT ‘crypt’ targets are not affected, only ‘integrity’ ones
are; both standalone dm-integrity volumes set up with integritysetup(8), as
well as volumes used for *experimental* authenticated disk encryption and set
up with cryptsetup(8).

In these scenarios the size overflows (due to size_t being incorrectly used in
place of uint64_t) and the device is mapped with a truncated size.  There is a
risk of data loss if the user writes inside the container, for instance while
trying to recover it, so that should IMHO be fixed via s-p-u.

This is an upstream regression from 2.1.0, so Stretch is not affected.
2:2.2.0-3 from Sid contains the cherry-picked upstream fix, but Buster's
2:2.1.0-5 (and 2:2.1.0-5+deb10u1) is affected.  Changelog since 2:2.1.0-5 is
as follows, and debdiff against 2:2.1.0-5 and 2:2.1.0-5+deb10u1 attached.

--8<->8--

cryptsetup (2:2.1.0-5+deb10u2) buster; urgency=medium

  * Cherry pick upstream commit 8f8f0b32: Fix mapped segments overflow on
32bit architectures.  Regression since 2:2.1.0-1.  (Closes: #935702)

 -- Guilhem Moulin   Mon, 26 Aug 2019 14:54:10 +0200

cryptsetup (2:2.1.0-5+deb10u1) buster; urgency=high

  * Backport upstream commits c03e3fe8, 725720df and fe4e1de5 to fix support
for LUKS2 headers without any bound keyslot.  Adding a new key slot using
the volume key was failing, both via the crypt_keyslot_add_by_volume_key()
API call and with `luksAddKey --master-key`.  The former in particular
might yield data loss if, in order to change a passphrase, an application
destroys the keyslot before adding a new one (using the volume key), cf.
#928893.  Note that doing so is *unsafe*: applications should instead use
crypt_keyslot_change_by_passphrase() from libcryptsetup >=1.6.0.
Trying to open LUKS2 volume by supplying the volume key on the command
line was also failing if there were no bound keyslot on the header.
(Closes: #934715)

 -- Guilhem Moulin   Fri, 16 Aug 2019 19:18:10 +0200

--8<->8--

A s-p-u was previously filed (#934956) — and accepted — for 2:2.1.0-5+deb10u1.
The new commit cherry-picked from upstream also includes a unit test; like
most of the test suite it'll be ignored by the build daemons as it requires
root access, but I did verify that the entire test suite still passes on amd64
and i386 (and that indeed large devices no longer overflow).

Given that Buster currently has 2:2.1.0-5, should the .changes include all
changes since that version, or only since 2:2.1.0-5+deb10u1?

Thanks for considering its inclusion in Buster!  CC'ing KiBi for the d-i ack.
Cheers,
-- 
Guilhem.
diffstat for cryptsetup-2.1.0 cryptsetup-2.1.0

 changelog  |   23 +
 gbp.conf   |1 
 patches/Fix-getting-default-LUKS2-keyslot-encryption-paramet.patch |   56 +++
 patches/Fix-mapped-segments-overflow-on-32bit-architectures.patch  |  151 
++
 patches/Fix-volume-key-file-if-no-LUKS2-keyslots-are-present.patch |   86 +
 patches/Mention-limitation-of-crypt_get_volume_key_size.patch  |   20 +
 patches/series |4 
 7 files changed, 341 insertions(+)

diff -Nru cryptsetup-2.1.0/debian/changelog cryptsetup-2.1.0/debian/changelog
--- cryptsetup-2.1.0/debian/changelog   2019-06-10 14:51:15.0 +0200
+++ cryptsetup-2.1.0/debian/changelog   2019-08-26 14:54:10.0 +0200
@@ -1,3 +1,26 @@
+cryptsetup (2:2.1.0-5+deb10u2) buster; urgency=medium
+
+  * Cherry pick upstream commit 8f8f0b32: Fix mapped segments overflow on
+32bit architectures.  Regression since 2:2.1.0-1.  (Closes: #935702)
+
+ -- Guilhem Moulin   Mon, 26 Aug 2019 14:54:10 +0200
+
+cryptsetup (2:2.1.0-5+deb10u1) buster; urgency=high
+
+  * Backport upstream commits c03e3fe8, 725720df and fe4e1de5 to fix support
+for LUKS2 headers without any bound keyslot.  Adding a new key slot using
+the volume key was failing, both via the crypt_keyslot_add_by_volume_key()
+API call and with `luksAddKey --master-key`.  The former in particular
+might yield data loss if, in order to change a passphrase, an application
+destroys the keyslot before adding a new one (using the volume key), cf.
+#928893.  Note that doing so is *unsafe*: applications should instead use
+crypt_keyslot_change_by_passphrase() from libcryptsetup >=1.6.0.
+Trying to open LUKS2 volume by supplying the volume key on the command
+line was also failing if there were no 

Bug#874748: marked as done (stretch-pu: plasma-workspace/4:5.8.7-1+deb9u1)

[Debian Bug Tracking System]

Your message dated Mon, 26 Aug 2019 18:14:59 +0100
with message-id 
<3b65b33ac7d7b4639ca170429d980da7ab9d8da5.ca...@adam-barratt.org.uk>
and subject line Re: Bug#865537: stretch-pu: plasma 5.8.7 LTS pre-approval
has caused the Debian Bug report #874748,
regarding stretch-pu: plasma-workspace/4:5.8.7-1+deb9u1
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear release team,

KDE Plasma 5.8 is an LTS release that I consider fit to be updated in stretch.
I've updated the packages that contain fixes in the 5.8.7 plasma point release 
in unstable and I would like to upload them to stretch-pu.

The source packages that I would like to update in stretch are:

bluedevil/4:5.8.7-1+deb9u1
breeze-gtk/5.8.7-1+deb9u1
kde-cli-tools/4:5.8.7-1+deb9u1
kscreenlocker/5.8.7-1+deb9u1
libksysguard/4:5.8.7-1+deb9u1
plasma-pa/4:5.8.7-1+deb9u1
systemsettings/4:5.8.7-1+deb9u1
user-manager/4:5.8.7-1+deb9u1
kwin/4:5.8.7-1+deb9u1
plasma-workspace/4:5.8.7-1+deb9u1
plasma-desktop/4:5.8.7.1-1+deb9u1

The corresponding changes includes are:

bluedevil 4:5.8.4-1 currently in stretch to 4:5.8.7-1+deb9u1
#

bluedevil (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch.
  * Document how to run bluedevil in in other DEs (Closes: 781012)

 -- Maximiliano Curia   Sat, 17 Jun 2017 12:23:14 +0200

bluedevil (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7).
+ ReceiveFileJob: Don't cancel the request right after accepting it

  KNotification::closed is emitted also when one of the notification
  actions was triggered.

  KDE#376773

 -- Maximiliano Curia   Sun, 28 May 2017 18:35:52 +0200

bluedevil (4:5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:11 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_4:5.8.4-1_4:5.8.7-1+deb9u1.debian.diff

breeze-gtk 5.8.4-1 currently in stretch to 5.8.7-1+deb9u1
##

breeze-gtk (5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 08:55:23 +0200

breeze-gtk (5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Set no stepper button for GTK3 scrollbars on gtk >=3.20
   This is a workaround to mitigate broken (huge wide) scrollbars in
   mozilla/Gecko based applications for GTK3 >= 3.20 in versions 52
   onwards.
   Ref: https://bugs.kde.org/show_bug.cgi?id=377008 and
https://bugzilla.mozilla.org/show_bug.cgi?id=1343802
   The mozilla bug is now 'fixed' and landing in nightlies v55, but may
   continue to affect earlier releases if not brought forward upstream.
   Regardless of any other concern, applying this brings the appearance
   of newer breeze and breeze-gtk scrollars into closer accord.
   KDE#377008

 -- Maximiliano Curia   Tue, 06 Jun 2017 17:14:40 +0200

breeze-gtk (5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:12 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debian.diff

kde-cli-tools 4:5.8.4-2 currently in stretch to 4:5.8.7-1+deb9u1
#

kde-cli-tools (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 09:11:58 +0200

kde-cli-tools (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Fix query for available modules
   The old query was bad because two reasons:
* it didn't use the same query systemsettings uses
* it didn't use exist so if the first property did not exist the
   

Bug#874749: marked as done (stretch-pu: plasma-desktop/4:5.8.7.1-1+deb9u1)

[Debian Bug Tracking System]

Your message dated Mon, 26 Aug 2019 18:14:59 +0100
with message-id 
<3b65b33ac7d7b4639ca170429d980da7ab9d8da5.ca...@adam-barratt.org.uk>
and subject line Re: Bug#865537: stretch-pu: plasma 5.8.7 LTS pre-approval
has caused the Debian Bug report #874749,
regarding stretch-pu: plasma-desktop/4:5.8.7.1-1+deb9u1
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear release team,

KDE Plasma 5.8 is an LTS release that I consider fit to be updated in stretch.
I've updated the packages that contain fixes in the 5.8.7 plasma point release 
in unstable and I would like to upload them to stretch-pu.

The source packages that I would like to update in stretch are:

bluedevil/4:5.8.7-1+deb9u1
breeze-gtk/5.8.7-1+deb9u1
kde-cli-tools/4:5.8.7-1+deb9u1
kscreenlocker/5.8.7-1+deb9u1
libksysguard/4:5.8.7-1+deb9u1
plasma-pa/4:5.8.7-1+deb9u1
systemsettings/4:5.8.7-1+deb9u1
user-manager/4:5.8.7-1+deb9u1
kwin/4:5.8.7-1+deb9u1
plasma-workspace/4:5.8.7-1+deb9u1
plasma-desktop/4:5.8.7.1-1+deb9u1

The corresponding changes includes are:

bluedevil 4:5.8.4-1 currently in stretch to 4:5.8.7-1+deb9u1
#

bluedevil (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch.
  * Document how to run bluedevil in in other DEs (Closes: 781012)

 -- Maximiliano Curia   Sat, 17 Jun 2017 12:23:14 +0200

bluedevil (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7).
+ ReceiveFileJob: Don't cancel the request right after accepting it

  KNotification::closed is emitted also when one of the notification
  actions was triggered.

  KDE#376773

 -- Maximiliano Curia   Sun, 28 May 2017 18:35:52 +0200

bluedevil (4:5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:11 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_4:5.8.4-1_4:5.8.7-1+deb9u1.debian.diff

breeze-gtk 5.8.4-1 currently in stretch to 5.8.7-1+deb9u1
##

breeze-gtk (5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 08:55:23 +0200

breeze-gtk (5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Set no stepper button for GTK3 scrollbars on gtk >=3.20
   This is a workaround to mitigate broken (huge wide) scrollbars in
   mozilla/Gecko based applications for GTK3 >= 3.20 in versions 52
   onwards.
   Ref: https://bugs.kde.org/show_bug.cgi?id=377008 and
https://bugzilla.mozilla.org/show_bug.cgi?id=1343802
   The mozilla bug is now 'fixed' and landing in nightlies v55, but may
   continue to affect earlier releases if not brought forward upstream.
   Regardless of any other concern, applying this brings the appearance
   of newer breeze and breeze-gtk scrollars into closer accord.
   KDE#377008

 -- Maximiliano Curia   Tue, 06 Jun 2017 17:14:40 +0200

breeze-gtk (5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:12 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debian.diff

kde-cli-tools 4:5.8.4-2 currently in stretch to 4:5.8.7-1+deb9u1
#

kde-cli-tools (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 09:11:58 +0200

kde-cli-tools (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Fix query for available modules
   The old query was bad because two reasons:
* it didn't use the same query systemsettings uses
* it didn't use exist so if the first property did not exist the
   

Bug#874745: marked as done (stretch-pu: systemsettings/4:5.8.7-1+deb9u1)

[Debian Bug Tracking System]

Your message dated Mon, 26 Aug 2019 18:14:59 +0100
with message-id 
<3b65b33ac7d7b4639ca170429d980da7ab9d8da5.ca...@adam-barratt.org.uk>
and subject line Re: Bug#865537: stretch-pu: plasma 5.8.7 LTS pre-approval
has caused the Debian Bug report #874745,
regarding stretch-pu: systemsettings/4:5.8.7-1+deb9u1
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear release team,

KDE Plasma 5.8 is an LTS release that I consider fit to be updated in stretch.
I've updated the packages that contain fixes in the 5.8.7 plasma point release 
in unstable and I would like to upload them to stretch-pu.

The source packages that I would like to update in stretch are:

bluedevil/4:5.8.7-1+deb9u1
breeze-gtk/5.8.7-1+deb9u1
kde-cli-tools/4:5.8.7-1+deb9u1
kscreenlocker/5.8.7-1+deb9u1
libksysguard/4:5.8.7-1+deb9u1
plasma-pa/4:5.8.7-1+deb9u1
systemsettings/4:5.8.7-1+deb9u1
user-manager/4:5.8.7-1+deb9u1
kwin/4:5.8.7-1+deb9u1
plasma-workspace/4:5.8.7-1+deb9u1
plasma-desktop/4:5.8.7.1-1+deb9u1

The corresponding changes includes are:

bluedevil 4:5.8.4-1 currently in stretch to 4:5.8.7-1+deb9u1
#

bluedevil (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch.
  * Document how to run bluedevil in in other DEs (Closes: 781012)

 -- Maximiliano Curia   Sat, 17 Jun 2017 12:23:14 +0200

bluedevil (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7).
+ ReceiveFileJob: Don't cancel the request right after accepting it

  KNotification::closed is emitted also when one of the notification
  actions was triggered.

  KDE#376773

 -- Maximiliano Curia   Sun, 28 May 2017 18:35:52 +0200

bluedevil (4:5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:11 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_4:5.8.4-1_4:5.8.7-1+deb9u1.debian.diff

breeze-gtk 5.8.4-1 currently in stretch to 5.8.7-1+deb9u1
##

breeze-gtk (5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 08:55:23 +0200

breeze-gtk (5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Set no stepper button for GTK3 scrollbars on gtk >=3.20
   This is a workaround to mitigate broken (huge wide) scrollbars in
   mozilla/Gecko based applications for GTK3 >= 3.20 in versions 52
   onwards.
   Ref: https://bugs.kde.org/show_bug.cgi?id=377008 and
https://bugzilla.mozilla.org/show_bug.cgi?id=1343802
   The mozilla bug is now 'fixed' and landing in nightlies v55, but may
   continue to affect earlier releases if not brought forward upstream.
   Regardless of any other concern, applying this brings the appearance
   of newer breeze and breeze-gtk scrollars into closer accord.
   KDE#377008

 -- Maximiliano Curia   Tue, 06 Jun 2017 17:14:40 +0200

breeze-gtk (5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:12 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debian.diff

kde-cli-tools 4:5.8.4-2 currently in stretch to 4:5.8.7-1+deb9u1
#

kde-cli-tools (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 09:11:58 +0200

kde-cli-tools (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Fix query for available modules
   The old query was bad because two reasons:
* it didn't use the same query systemsettings uses
* it didn't use exist so if the first property did not exist the
 

Bug#874747: marked as done (stretch-pu: kwin/4:5.8.7-1+deb9u1)

[Debian Bug Tracking System]

Your message dated Mon, 26 Aug 2019 18:14:59 +0100
with message-id 
<3b65b33ac7d7b4639ca170429d980da7ab9d8da5.ca...@adam-barratt.org.uk>
and subject line Re: Bug#865537: stretch-pu: plasma 5.8.7 LTS pre-approval
has caused the Debian Bug report #874747,
regarding stretch-pu: kwin/4:5.8.7-1+deb9u1
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear release team,

KDE Plasma 5.8 is an LTS release that I consider fit to be updated in stretch.
I've updated the packages that contain fixes in the 5.8.7 plasma point release 
in unstable and I would like to upload them to stretch-pu.

The source packages that I would like to update in stretch are:

bluedevil/4:5.8.7-1+deb9u1
breeze-gtk/5.8.7-1+deb9u1
kde-cli-tools/4:5.8.7-1+deb9u1
kscreenlocker/5.8.7-1+deb9u1
libksysguard/4:5.8.7-1+deb9u1
plasma-pa/4:5.8.7-1+deb9u1
systemsettings/4:5.8.7-1+deb9u1
user-manager/4:5.8.7-1+deb9u1
kwin/4:5.8.7-1+deb9u1
plasma-workspace/4:5.8.7-1+deb9u1
plasma-desktop/4:5.8.7.1-1+deb9u1

The corresponding changes includes are:

bluedevil 4:5.8.4-1 currently in stretch to 4:5.8.7-1+deb9u1
#

bluedevil (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch.
  * Document how to run bluedevil in in other DEs (Closes: 781012)

 -- Maximiliano Curia   Sat, 17 Jun 2017 12:23:14 +0200

bluedevil (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7).
+ ReceiveFileJob: Don't cancel the request right after accepting it

  KNotification::closed is emitted also when one of the notification
  actions was triggered.

  KDE#376773

 -- Maximiliano Curia   Sun, 28 May 2017 18:35:52 +0200

bluedevil (4:5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:11 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_4:5.8.4-1_4:5.8.7-1+deb9u1.debian.diff

breeze-gtk 5.8.4-1 currently in stretch to 5.8.7-1+deb9u1
##

breeze-gtk (5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 08:55:23 +0200

breeze-gtk (5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Set no stepper button for GTK3 scrollbars on gtk >=3.20
   This is a workaround to mitigate broken (huge wide) scrollbars in
   mozilla/Gecko based applications for GTK3 >= 3.20 in versions 52
   onwards.
   Ref: https://bugs.kde.org/show_bug.cgi?id=377008 and
https://bugzilla.mozilla.org/show_bug.cgi?id=1343802
   The mozilla bug is now 'fixed' and landing in nightlies v55, but may
   continue to affect earlier releases if not brought forward upstream.
   Regardless of any other concern, applying this brings the appearance
   of newer breeze and breeze-gtk scrollars into closer accord.
   KDE#377008

 -- Maximiliano Curia   Tue, 06 Jun 2017 17:14:40 +0200

breeze-gtk (5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:12 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debian.diff

kde-cli-tools 4:5.8.4-2 currently in stretch to 4:5.8.7-1+deb9u1
#

kde-cli-tools (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 09:11:58 +0200

kde-cli-tools (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Fix query for available modules
   The old query was bad because two reasons:
* it didn't use the same query systemsettings uses
* it didn't use exist so if the first property did not exist the
  

Bug#874746: marked as done (stretch-pu: user-manager/4:5.8.7-1+deb9u1)

[Debian Bug Tracking System]

Your message dated Mon, 26 Aug 2019 18:14:59 +0100
with message-id 
<3b65b33ac7d7b4639ca170429d980da7ab9d8da5.ca...@adam-barratt.org.uk>
and subject line Re: Bug#865537: stretch-pu: plasma 5.8.7 LTS pre-approval
has caused the Debian Bug report #874746,
regarding stretch-pu: user-manager/4:5.8.7-1+deb9u1
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear release team,

KDE Plasma 5.8 is an LTS release that I consider fit to be updated in stretch.
I've updated the packages that contain fixes in the 5.8.7 plasma point release 
in unstable and I would like to upload them to stretch-pu.

The source packages that I would like to update in stretch are:

bluedevil/4:5.8.7-1+deb9u1
breeze-gtk/5.8.7-1+deb9u1
kde-cli-tools/4:5.8.7-1+deb9u1
kscreenlocker/5.8.7-1+deb9u1
libksysguard/4:5.8.7-1+deb9u1
plasma-pa/4:5.8.7-1+deb9u1
systemsettings/4:5.8.7-1+deb9u1
user-manager/4:5.8.7-1+deb9u1
kwin/4:5.8.7-1+deb9u1
plasma-workspace/4:5.8.7-1+deb9u1
plasma-desktop/4:5.8.7.1-1+deb9u1

The corresponding changes includes are:

bluedevil 4:5.8.4-1 currently in stretch to 4:5.8.7-1+deb9u1
#

bluedevil (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch.
  * Document how to run bluedevil in in other DEs (Closes: 781012)

 -- Maximiliano Curia   Sat, 17 Jun 2017 12:23:14 +0200

bluedevil (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7).
+ ReceiveFileJob: Don't cancel the request right after accepting it

  KNotification::closed is emitted also when one of the notification
  actions was triggered.

  KDE#376773

 -- Maximiliano Curia   Sun, 28 May 2017 18:35:52 +0200

bluedevil (4:5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:11 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_4:5.8.4-1_4:5.8.7-1+deb9u1.debian.diff

breeze-gtk 5.8.4-1 currently in stretch to 5.8.7-1+deb9u1
##

breeze-gtk (5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 08:55:23 +0200

breeze-gtk (5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Set no stepper button for GTK3 scrollbars on gtk >=3.20
   This is a workaround to mitigate broken (huge wide) scrollbars in
   mozilla/Gecko based applications for GTK3 >= 3.20 in versions 52
   onwards.
   Ref: https://bugs.kde.org/show_bug.cgi?id=377008 and
https://bugzilla.mozilla.org/show_bug.cgi?id=1343802
   The mozilla bug is now 'fixed' and landing in nightlies v55, but may
   continue to affect earlier releases if not brought forward upstream.
   Regardless of any other concern, applying this brings the appearance
   of newer breeze and breeze-gtk scrollars into closer accord.
   KDE#377008

 -- Maximiliano Curia   Tue, 06 Jun 2017 17:14:40 +0200

breeze-gtk (5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:12 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debian.diff

kde-cli-tools 4:5.8.4-2 currently in stretch to 4:5.8.7-1+deb9u1
#

kde-cli-tools (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 09:11:58 +0200

kde-cli-tools (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Fix query for available modules
   The old query was bad because two reasons:
* it didn't use the same query systemsettings uses
* it didn't use exist so if the first property did not exist the
   

Bug#874742: marked as done (stretch-pu: kscreenlocker/5.8.7-1+deb9u1)

[Debian Bug Tracking System]

Your message dated Mon, 26 Aug 2019 18:14:59 +0100
with message-id 
<3b65b33ac7d7b4639ca170429d980da7ab9d8da5.ca...@adam-barratt.org.uk>
and subject line Re: Bug#865537: stretch-pu: plasma 5.8.7 LTS pre-approval
has caused the Debian Bug report #874742,
regarding stretch-pu: kscreenlocker/5.8.7-1+deb9u1
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear release team,

KDE Plasma 5.8 is an LTS release that I consider fit to be updated in stretch.
I've updated the packages that contain fixes in the 5.8.7 plasma point release 
in unstable and I would like to upload them to stretch-pu.

The source packages that I would like to update in stretch are:

bluedevil/4:5.8.7-1+deb9u1
breeze-gtk/5.8.7-1+deb9u1
kde-cli-tools/4:5.8.7-1+deb9u1
kscreenlocker/5.8.7-1+deb9u1
libksysguard/4:5.8.7-1+deb9u1
plasma-pa/4:5.8.7-1+deb9u1
systemsettings/4:5.8.7-1+deb9u1
user-manager/4:5.8.7-1+deb9u1
kwin/4:5.8.7-1+deb9u1
plasma-workspace/4:5.8.7-1+deb9u1
plasma-desktop/4:5.8.7.1-1+deb9u1

The corresponding changes includes are:

bluedevil 4:5.8.4-1 currently in stretch to 4:5.8.7-1+deb9u1
#

bluedevil (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch.
  * Document how to run bluedevil in in other DEs (Closes: 781012)

 -- Maximiliano Curia   Sat, 17 Jun 2017 12:23:14 +0200

bluedevil (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7).
+ ReceiveFileJob: Don't cancel the request right after accepting it

  KNotification::closed is emitted also when one of the notification
  actions was triggered.

  KDE#376773

 -- Maximiliano Curia   Sun, 28 May 2017 18:35:52 +0200

bluedevil (4:5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:11 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_4:5.8.4-1_4:5.8.7-1+deb9u1.debian.diff

breeze-gtk 5.8.4-1 currently in stretch to 5.8.7-1+deb9u1
##

breeze-gtk (5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 08:55:23 +0200

breeze-gtk (5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Set no stepper button for GTK3 scrollbars on gtk >=3.20
   This is a workaround to mitigate broken (huge wide) scrollbars in
   mozilla/Gecko based applications for GTK3 >= 3.20 in versions 52
   onwards.
   Ref: https://bugs.kde.org/show_bug.cgi?id=377008 and
https://bugzilla.mozilla.org/show_bug.cgi?id=1343802
   The mozilla bug is now 'fixed' and landing in nightlies v55, but may
   continue to affect earlier releases if not brought forward upstream.
   Regardless of any other concern, applying this brings the appearance
   of newer breeze and breeze-gtk scrollars into closer accord.
   KDE#377008

 -- Maximiliano Curia   Tue, 06 Jun 2017 17:14:40 +0200

breeze-gtk (5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:12 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debian.diff

kde-cli-tools 4:5.8.4-2 currently in stretch to 4:5.8.7-1+deb9u1
#

kde-cli-tools (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 09:11:58 +0200

kde-cli-tools (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Fix query for available modules
   The old query was bad because two reasons:
* it didn't use the same query systemsettings uses
* it didn't use exist so if the first property did not exist the

Bug#874744: marked as done (stretch-pu: plasma-pa/4:5.8.7-1+deb9u1)

[Debian Bug Tracking System]

Your message dated Mon, 26 Aug 2019 18:14:59 +0100
with message-id 
<3b65b33ac7d7b4639ca170429d980da7ab9d8da5.ca...@adam-barratt.org.uk>
and subject line Re: Bug#865537: stretch-pu: plasma 5.8.7 LTS pre-approval
has caused the Debian Bug report #874744,
regarding stretch-pu: plasma-pa/4:5.8.7-1+deb9u1
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear release team,

KDE Plasma 5.8 is an LTS release that I consider fit to be updated in stretch.
I've updated the packages that contain fixes in the 5.8.7 plasma point release 
in unstable and I would like to upload them to stretch-pu.

The source packages that I would like to update in stretch are:

bluedevil/4:5.8.7-1+deb9u1
breeze-gtk/5.8.7-1+deb9u1
kde-cli-tools/4:5.8.7-1+deb9u1
kscreenlocker/5.8.7-1+deb9u1
libksysguard/4:5.8.7-1+deb9u1
plasma-pa/4:5.8.7-1+deb9u1
systemsettings/4:5.8.7-1+deb9u1
user-manager/4:5.8.7-1+deb9u1
kwin/4:5.8.7-1+deb9u1
plasma-workspace/4:5.8.7-1+deb9u1
plasma-desktop/4:5.8.7.1-1+deb9u1

The corresponding changes includes are:

bluedevil 4:5.8.4-1 currently in stretch to 4:5.8.7-1+deb9u1
#

bluedevil (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch.
  * Document how to run bluedevil in in other DEs (Closes: 781012)

 -- Maximiliano Curia   Sat, 17 Jun 2017 12:23:14 +0200

bluedevil (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7).
+ ReceiveFileJob: Don't cancel the request right after accepting it

  KNotification::closed is emitted also when one of the notification
  actions was triggered.

  KDE#376773

 -- Maximiliano Curia   Sun, 28 May 2017 18:35:52 +0200

bluedevil (4:5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:11 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_4:5.8.4-1_4:5.8.7-1+deb9u1.debian.diff

breeze-gtk 5.8.4-1 currently in stretch to 5.8.7-1+deb9u1
##

breeze-gtk (5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 08:55:23 +0200

breeze-gtk (5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Set no stepper button for GTK3 scrollbars on gtk >=3.20
   This is a workaround to mitigate broken (huge wide) scrollbars in
   mozilla/Gecko based applications for GTK3 >= 3.20 in versions 52
   onwards.
   Ref: https://bugs.kde.org/show_bug.cgi?id=377008 and
https://bugzilla.mozilla.org/show_bug.cgi?id=1343802
   The mozilla bug is now 'fixed' and landing in nightlies v55, but may
   continue to affect earlier releases if not brought forward upstream.
   Regardless of any other concern, applying this brings the appearance
   of newer breeze and breeze-gtk scrollars into closer accord.
   KDE#377008

 -- Maximiliano Curia   Tue, 06 Jun 2017 17:14:40 +0200

breeze-gtk (5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:12 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debian.diff

kde-cli-tools 4:5.8.4-2 currently in stretch to 4:5.8.7-1+deb9u1
#

kde-cli-tools (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 09:11:58 +0200

kde-cli-tools (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Fix query for available modules
   The old query was bad because two reasons:
* it didn't use the same query systemsettings uses
* it didn't use exist so if the first property did not exist the
  

Bug#874743: marked as done (stretch-pu: libksysguard/4:5.8.7-1+deb9u1)

[Debian Bug Tracking System]

Your message dated Mon, 26 Aug 2019 18:14:59 +0100
with message-id 
<3b65b33ac7d7b4639ca170429d980da7ab9d8da5.ca...@adam-barratt.org.uk>
and subject line Re: Bug#865537: stretch-pu: plasma 5.8.7 LTS pre-approval
has caused the Debian Bug report #874743,
regarding stretch-pu: libksysguard/4:5.8.7-1+deb9u1
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear release team,

KDE Plasma 5.8 is an LTS release that I consider fit to be updated in stretch.
I've updated the packages that contain fixes in the 5.8.7 plasma point release 
in unstable and I would like to upload them to stretch-pu.

The source packages that I would like to update in stretch are:

bluedevil/4:5.8.7-1+deb9u1
breeze-gtk/5.8.7-1+deb9u1
kde-cli-tools/4:5.8.7-1+deb9u1
kscreenlocker/5.8.7-1+deb9u1
libksysguard/4:5.8.7-1+deb9u1
plasma-pa/4:5.8.7-1+deb9u1
systemsettings/4:5.8.7-1+deb9u1
user-manager/4:5.8.7-1+deb9u1
kwin/4:5.8.7-1+deb9u1
plasma-workspace/4:5.8.7-1+deb9u1
plasma-desktop/4:5.8.7.1-1+deb9u1

The corresponding changes includes are:

bluedevil 4:5.8.4-1 currently in stretch to 4:5.8.7-1+deb9u1
#

bluedevil (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch.
  * Document how to run bluedevil in in other DEs (Closes: 781012)

 -- Maximiliano Curia   Sat, 17 Jun 2017 12:23:14 +0200

bluedevil (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7).
+ ReceiveFileJob: Don't cancel the request right after accepting it

  KNotification::closed is emitted also when one of the notification
  actions was triggered.

  KDE#376773

 -- Maximiliano Curia   Sun, 28 May 2017 18:35:52 +0200

bluedevil (4:5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:11 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_4:5.8.4-1_4:5.8.7-1+deb9u1.debian.diff

breeze-gtk 5.8.4-1 currently in stretch to 5.8.7-1+deb9u1
##

breeze-gtk (5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 08:55:23 +0200

breeze-gtk (5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Set no stepper button for GTK3 scrollbars on gtk >=3.20
   This is a workaround to mitigate broken (huge wide) scrollbars in
   mozilla/Gecko based applications for GTK3 >= 3.20 in versions 52
   onwards.
   Ref: https://bugs.kde.org/show_bug.cgi?id=377008 and
https://bugzilla.mozilla.org/show_bug.cgi?id=1343802
   The mozilla bug is now 'fixed' and landing in nightlies v55, but may
   continue to affect earlier releases if not brought forward upstream.
   Regardless of any other concern, applying this brings the appearance
   of newer breeze and breeze-gtk scrollars into closer accord.
   KDE#377008

 -- Maximiliano Curia   Tue, 06 Jun 2017 17:14:40 +0200

breeze-gtk (5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:12 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debian.diff

kde-cli-tools 4:5.8.4-2 currently in stretch to 4:5.8.7-1+deb9u1
#

kde-cli-tools (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 09:11:58 +0200

kde-cli-tools (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Fix query for available modules
   The old query was bad because two reasons:
* it didn't use the same query systemsettings uses
* it didn't use exist so if the first property did not exist the
   

Bug#874739: marked as done (stretch-pu: bluedevil/4:5.8.7-1+deb9u1)

[Debian Bug Tracking System]

Your message dated Mon, 26 Aug 2019 18:14:59 +0100
with message-id 
<3b65b33ac7d7b4639ca170429d980da7ab9d8da5.ca...@adam-barratt.org.uk>
and subject line Re: Bug#865537: stretch-pu: plasma 5.8.7 LTS pre-approval
has caused the Debian Bug report #874739,
regarding stretch-pu: bluedevil/4:5.8.7-1+deb9u1
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear release team,

KDE Plasma 5.8 is an LTS release that I consider fit to be updated in stretch.
I've updated the packages that contain fixes in the 5.8.7 plasma point release 
in unstable and I would like to upload them to stretch-pu.

The source packages that I would like to update in stretch are:

bluedevil/4:5.8.7-1+deb9u1
breeze-gtk/5.8.7-1+deb9u1
kde-cli-tools/4:5.8.7-1+deb9u1
kscreenlocker/5.8.7-1+deb9u1
libksysguard/4:5.8.7-1+deb9u1
plasma-pa/4:5.8.7-1+deb9u1
systemsettings/4:5.8.7-1+deb9u1
user-manager/4:5.8.7-1+deb9u1
kwin/4:5.8.7-1+deb9u1
plasma-workspace/4:5.8.7-1+deb9u1
plasma-desktop/4:5.8.7.1-1+deb9u1

The corresponding changes includes are:

bluedevil 4:5.8.4-1 currently in stretch to 4:5.8.7-1+deb9u1
#

bluedevil (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch.
  * Document how to run bluedevil in in other DEs (Closes: 781012)

 -- Maximiliano Curia   Sat, 17 Jun 2017 12:23:14 +0200

bluedevil (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7).
+ ReceiveFileJob: Don't cancel the request right after accepting it

  KNotification::closed is emitted also when one of the notification
  actions was triggered.

  KDE#376773

 -- Maximiliano Curia   Sun, 28 May 2017 18:35:52 +0200

bluedevil (4:5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:11 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_4:5.8.4-1_4:5.8.7-1+deb9u1.debian.diff

breeze-gtk 5.8.4-1 currently in stretch to 5.8.7-1+deb9u1
##

breeze-gtk (5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 08:55:23 +0200

breeze-gtk (5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Set no stepper button for GTK3 scrollbars on gtk >=3.20
   This is a workaround to mitigate broken (huge wide) scrollbars in
   mozilla/Gecko based applications for GTK3 >= 3.20 in versions 52
   onwards.
   Ref: https://bugs.kde.org/show_bug.cgi?id=377008 and
https://bugzilla.mozilla.org/show_bug.cgi?id=1343802
   The mozilla bug is now 'fixed' and landing in nightlies v55, but may
   continue to affect earlier releases if not brought forward upstream.
   Regardless of any other concern, applying this brings the appearance
   of newer breeze and breeze-gtk scrollars into closer accord.
   KDE#377008

 -- Maximiliano Curia   Tue, 06 Jun 2017 17:14:40 +0200

breeze-gtk (5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:12 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debian.diff

kde-cli-tools 4:5.8.4-2 currently in stretch to 4:5.8.7-1+deb9u1
#

kde-cli-tools (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 09:11:58 +0200

kde-cli-tools (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Fix query for available modules
   The old query was bad because two reasons:
* it didn't use the same query systemsettings uses
* it didn't use exist so if the first property did not exist the
  

Bug#865537: marked as done (stretch-pu: plasma 5.8.7 LTS pre-approval)

[Debian Bug Tracking System]

Your message dated Mon, 26 Aug 2019 18:14:59 +0100
with message-id 
<3b65b33ac7d7b4639ca170429d980da7ab9d8da5.ca...@adam-barratt.org.uk>
and subject line Re: Bug#865537: stretch-pu: plasma 5.8.7 LTS pre-approval
has caused the Debian Bug report #865537,
regarding stretch-pu: plasma 5.8.7 LTS pre-approval
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear release team,

KDE Plasma 5.8 is an LTS release that I consider fit to be updated in stretch.
I've updated the packages that contain fixes in the 5.8.7 plasma point release 
in unstable and I would like to upload them to stretch-pu.

The source packages that I would like to update in stretch are:

bluedevil/4:5.8.7-1+deb9u1
breeze-gtk/5.8.7-1+deb9u1
kde-cli-tools/4:5.8.7-1+deb9u1
kscreenlocker/5.8.7-1+deb9u1
libksysguard/4:5.8.7-1+deb9u1
plasma-pa/4:5.8.7-1+deb9u1
systemsettings/4:5.8.7-1+deb9u1
user-manager/4:5.8.7-1+deb9u1
kwin/4:5.8.7-1+deb9u1
plasma-workspace/4:5.8.7-1+deb9u1
plasma-desktop/4:5.8.7.1-1+deb9u1

The corresponding changes includes are:

bluedevil 4:5.8.4-1 currently in stretch to 4:5.8.7-1+deb9u1
#

bluedevil (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch.
  * Document how to run bluedevil in in other DEs (Closes: 781012)

 -- Maximiliano Curia   Sat, 17 Jun 2017 12:23:14 +0200

bluedevil (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7).
+ ReceiveFileJob: Don't cancel the request right after accepting it

  KNotification::closed is emitted also when one of the notification
  actions was triggered.

  KDE#376773

 -- Maximiliano Curia   Sun, 28 May 2017 18:35:52 +0200

bluedevil (4:5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:11 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_4:5.8.4-1_4:5.8.7-1+deb9u1.debian.diff

breeze-gtk 5.8.4-1 currently in stretch to 5.8.7-1+deb9u1
##

breeze-gtk (5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 08:55:23 +0200

breeze-gtk (5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Set no stepper button for GTK3 scrollbars on gtk >=3.20
   This is a workaround to mitigate broken (huge wide) scrollbars in
   mozilla/Gecko based applications for GTK3 >= 3.20 in versions 52
   onwards.
   Ref: https://bugs.kde.org/show_bug.cgi?id=377008 and
https://bugzilla.mozilla.org/show_bug.cgi?id=1343802
   The mozilla bug is now 'fixed' and landing in nightlies v55, but may
   continue to affect earlier releases if not brought forward upstream.
   Regardless of any other concern, applying this brings the appearance
   of newer breeze and breeze-gtk scrollars into closer accord.
   KDE#377008

 -- Maximiliano Curia   Tue, 06 Jun 2017 17:14:40 +0200

breeze-gtk (5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:12 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debian.diff

kde-cli-tools 4:5.8.4-2 currently in stretch to 4:5.8.7-1+deb9u1
#

kde-cli-tools (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 09:11:58 +0200

kde-cli-tools (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Fix query for available modules
   The old query was bad because two reasons:
* it didn't use the same query systemsettings uses
* it didn't use exist so if the first property did not exist the
   

Bug#874741: marked as done (stretch-pu: kde-cli-tools/4:5.8.7-1+deb9u1)

[Debian Bug Tracking System]

Your message dated Mon, 26 Aug 2019 18:14:59 +0100
with message-id 
<3b65b33ac7d7b4639ca170429d980da7ab9d8da5.ca...@adam-barratt.org.uk>
and subject line Re: Bug#865537: stretch-pu: plasma 5.8.7 LTS pre-approval
has caused the Debian Bug report #874741,
regarding stretch-pu: kde-cli-tools/4:5.8.7-1+deb9u1
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear release team,

KDE Plasma 5.8 is an LTS release that I consider fit to be updated in stretch.
I've updated the packages that contain fixes in the 5.8.7 plasma point release 
in unstable and I would like to upload them to stretch-pu.

The source packages that I would like to update in stretch are:

bluedevil/4:5.8.7-1+deb9u1
breeze-gtk/5.8.7-1+deb9u1
kde-cli-tools/4:5.8.7-1+deb9u1
kscreenlocker/5.8.7-1+deb9u1
libksysguard/4:5.8.7-1+deb9u1
plasma-pa/4:5.8.7-1+deb9u1
systemsettings/4:5.8.7-1+deb9u1
user-manager/4:5.8.7-1+deb9u1
kwin/4:5.8.7-1+deb9u1
plasma-workspace/4:5.8.7-1+deb9u1
plasma-desktop/4:5.8.7.1-1+deb9u1

The corresponding changes includes are:

bluedevil 4:5.8.4-1 currently in stretch to 4:5.8.7-1+deb9u1
#

bluedevil (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch.
  * Document how to run bluedevil in in other DEs (Closes: 781012)

 -- Maximiliano Curia   Sat, 17 Jun 2017 12:23:14 +0200

bluedevil (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7).
+ ReceiveFileJob: Don't cancel the request right after accepting it

  KNotification::closed is emitted also when one of the notification
  actions was triggered.

  KDE#376773

 -- Maximiliano Curia   Sun, 28 May 2017 18:35:52 +0200

bluedevil (4:5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:11 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_4:5.8.4-1_4:5.8.7-1+deb9u1.debian.diff

breeze-gtk 5.8.4-1 currently in stretch to 5.8.7-1+deb9u1
##

breeze-gtk (5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 08:55:23 +0200

breeze-gtk (5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Set no stepper button for GTK3 scrollbars on gtk >=3.20
   This is a workaround to mitigate broken (huge wide) scrollbars in
   mozilla/Gecko based applications for GTK3 >= 3.20 in versions 52
   onwards.
   Ref: https://bugs.kde.org/show_bug.cgi?id=377008 and
https://bugzilla.mozilla.org/show_bug.cgi?id=1343802
   The mozilla bug is now 'fixed' and landing in nightlies v55, but may
   continue to affect earlier releases if not brought forward upstream.
   Regardless of any other concern, applying this brings the appearance
   of newer breeze and breeze-gtk scrollars into closer accord.
   KDE#377008

 -- Maximiliano Curia   Tue, 06 Jun 2017 17:14:40 +0200

breeze-gtk (5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:12 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debian.diff

kde-cli-tools 4:5.8.4-2 currently in stretch to 4:5.8.7-1+deb9u1
#

kde-cli-tools (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 09:11:58 +0200

kde-cli-tools (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Fix query for available modules
   The old query was bad because two reasons:
* it didn't use the same query systemsettings uses
* it didn't use exist so if the first property did not exist the
  

Bug#874740: marked as done (stretch-pu: breeze-gtk/5.8.7-1+deb9u1)

[Debian Bug Tracking System]

Your message dated Mon, 26 Aug 2019 18:14:59 +0100
with message-id 
<3b65b33ac7d7b4639ca170429d980da7ab9d8da5.ca...@adam-barratt.org.uk>
and subject line Re: Bug#865537: stretch-pu: plasma 5.8.7 LTS pre-approval
has caused the Debian Bug report #874740,
regarding stretch-pu: breeze-gtk/5.8.7-1+deb9u1
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear release team,

KDE Plasma 5.8 is an LTS release that I consider fit to be updated in stretch.
I've updated the packages that contain fixes in the 5.8.7 plasma point release 
in unstable and I would like to upload them to stretch-pu.

The source packages that I would like to update in stretch are:

bluedevil/4:5.8.7-1+deb9u1
breeze-gtk/5.8.7-1+deb9u1
kde-cli-tools/4:5.8.7-1+deb9u1
kscreenlocker/5.8.7-1+deb9u1
libksysguard/4:5.8.7-1+deb9u1
plasma-pa/4:5.8.7-1+deb9u1
systemsettings/4:5.8.7-1+deb9u1
user-manager/4:5.8.7-1+deb9u1
kwin/4:5.8.7-1+deb9u1
plasma-workspace/4:5.8.7-1+deb9u1
plasma-desktop/4:5.8.7.1-1+deb9u1

The corresponding changes includes are:

bluedevil 4:5.8.4-1 currently in stretch to 4:5.8.7-1+deb9u1
#

bluedevil (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch.
  * Document how to run bluedevil in in other DEs (Closes: 781012)

 -- Maximiliano Curia   Sat, 17 Jun 2017 12:23:14 +0200

bluedevil (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7).
+ ReceiveFileJob: Don't cancel the request right after accepting it

  KNotification::closed is emitted also when one of the notification
  actions was triggered.

  KDE#376773

 -- Maximiliano Curia   Sun, 28 May 2017 18:35:52 +0200

bluedevil (4:5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:11 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_4:5.8.4-1_4:5.8.7-1+deb9u1.debian.diff

breeze-gtk 5.8.4-1 currently in stretch to 5.8.7-1+deb9u1
##

breeze-gtk (5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 08:55:23 +0200

breeze-gtk (5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Set no stepper button for GTK3 scrollbars on gtk >=3.20
   This is a workaround to mitigate broken (huge wide) scrollbars in
   mozilla/Gecko based applications for GTK3 >= 3.20 in versions 52
   onwards.
   Ref: https://bugs.kde.org/show_bug.cgi?id=377008 and
https://bugzilla.mozilla.org/show_bug.cgi?id=1343802
   The mozilla bug is now 'fixed' and landing in nightlies v55, but may
   continue to affect earlier releases if not brought forward upstream.
   Regardless of any other concern, applying this brings the appearance
   of newer breeze and breeze-gtk scrollars into closer accord.
   KDE#377008

 -- Maximiliano Curia   Tue, 06 Jun 2017 17:14:40 +0200

breeze-gtk (5.8.5-1) experimental; urgency=medium

  * New upstream release (5.8.5).

 -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:12 +0100

The full debdiff is available in 
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debian.diff

kde-cli-tools 4:5.8.4-2 currently in stretch to 4:5.8.7-1+deb9u1
#

kde-cli-tools (4:5.8.7-1+deb9u1) stretch; urgency=medium

  * Upload to stretch

 -- Maximiliano Curia   Mon, 19 Jun 2017 09:11:58 +0200

kde-cli-tools (4:5.8.7-1) unstable; urgency=medium

  * New upstream release (5.8.7)
 + Fix query for available modules
   The old query was bad because two reasons:
* it didn't use the same query systemsettings uses
* it didn't use exist so if the first property did not exist the
  

Bug#934356: stretch-pu: package mitmproxy/0.18.2-6

[Sébastien Delafond]

On 26/08 17:42, Adam D. Barratt wrote:
> Our tooling has highlighted a dependency issue. I've not had chance to
> check if it already existed in the earlier package, but:
> 
>   unsat-dependency: python-cryptography (< 1.6)
> 
> stretch has python-cryptography 1.7.1

This is a regression somewhere in the build process; 0.18.2-6 in stretch
currently has (sorted alphabetically for easier reading):

  Depends:
  python-backports.ssl-match-hostname,
  python-blinker (<< 1.5),
  python-brotli (>= 0.5.1),
  python-certifi,
  python-click,
  python-configargparse (>= 0.10),
  python-construct (>= 2.5.2),
  python-cryptography (>= 1.3),
  python-cssutils (<< 1.1),
  python-flask (>= 0.10.1),
  python-h2 (>= 2.4.1),
  python-hpack,
  python-html2text (>= 2016.1.8),
  python-hyperframe (<< 5),
  python-jsbeautifier (>= 1.6.3),
  python-lxml (>= 3.5.0),
  python-openssl (>= 16.0),
  python-passlib (>= 1.6.5),
  python-pil (>= 3.2),
  python-pyasn1 (>= 0.1.9),
  python-pyparsing (>= 2.1.3),
  python-pyperclip,
  python-requests (>= 2.9.1),
  python-six (>= 1.10),
  python-tornado (>= 4.3),
  python-typing
  python-urwid (>= 1.3.1),
  python-watchdog (>= 0.8.3),
  python:any (<< 2.8),
  python:any (>= 2.7.5-5~),

0.18.2-6+deb9u1 has:

  Depends:
  python-backports.ssl-match-hostname,
  python-blinker (<< 1.5),
  python-brotli (>= 0.5.1),
  python-certifi,
  python-click,
  python-configargparse (>= 0.10),
  python-construct (>= 2.5.2),
  python-cryptography (<< 1.6),
  python-cryptography (>= 1.3),
  python-cssutils (<< 1.1),
  python-flask (<< 0.12),
  python-flask (>= 0.10.1),
  python-h2 (>= 2.4.1),
  python-hpack,
  python-html2text (>= 2016.1.8),
  python-hyperframe (<< 5),
  python-jsbeautifier (>= 1.6.3),
  python-lxml (>= 3.5.0),
  python-openssl (>= 16.0),
  python-passlib (>= 1.6.5),
  python-pil (>= 3.2),
  python-pyasn1 (<< 0.2),
  python-pyasn1 (>= 0.1.9),
  python-pyparsing (>= 2.1.3),
  python-pyperclip,
  python-requests (>= 2.9.1),
  python-six (<< 1.11),
  python-six (>= 1.10),
  python-tornado (>= 4.3),
  python-typing
  python-urwid (>= 1.3.1),
  python-watchdog (>= 0.8.3),
  python:any (<< 2.8),
  python:any (>= 2.7.5-5~),

At this point I'm not sure what part of the build chain is adding back
all the "python foo (<< .n.m)" (obviously during the expansion of
${python:Depends}, and by looking at setup.py), even though python-foo
is already explicitly listed in debian/control's Depends field.

Even more confusing to me right now is that the whole point of 0.18.2-6
was indeed to *remove* all those upper-bound dependencies:

  - https://bugs.debian.org/848562
  - 
https://salsa.debian.org/debian/mitmproxy/commit/4c238cb3549b9bf5e7b01a9c287eb2428a7134d2

And obviously at the time it worked, because 0.18.6-2 is indeed
"correct".

Cheers,

-- 
Seb

Processed: Re: Bug#935746: buster-pu: package nss/2:3.42.1-1+deb10u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #935746 [release.debian.org] buster-pu: package nss/2:3.42.1-1+deb10u1
Added tag(s) confirmed.

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

Bug#935746: buster-pu: package nss/2:3.42.1-1+deb10u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sun, 2019-08-25 at 21:25 +0200, Moritz Muehlenhoff wrote:
> The NSS update below fixes a few non-severe security issues. I've
> been running this version with Firefox on Buster (which uses the
> system copy of NSS unlike Firefox in Stretch) without any issues.
[...]
> +  * Fixes for CVE-2019-11719, CVE-2019-11727 and CVE-2019-11729 (in
> unstable
> +these were addressed via the 2:3.45-1 upload to unstable)
> 

FWIW that stanza mentions unstable twice in the parentheses.

Please go ahead.

Regards,

Adam

Processed: Re: Bug#935370: buster-pu: package lacme/0.5-1+deb10u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #935370 [release.debian.org] buster-pu: package lacme/0.5-1+deb10u1
Added tag(s) confirmed.

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

Bug#935370: buster-pu: package lacme/0.5-1+deb10u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2019-08-22 at 00:54 +0200, Guilhem Moulin wrote:
> Per RFC 8555 sec 6.3 the Let's Encrypt folks are deprecating
> unauthenticated GETs from their v2 API.  Support for these requests
> will
> be removed on *Nov 01 2019* (so likely between Debian 10.1 and 10.2)
> [0].
> 
> lacme uses the v2 API by default since 0.5, and removing support for
> unauthenticated GETs means that applying for certificate issuance
> will
> stop working.  Replacing GETs with POST-as-GETs is trivial (debdiff
> attached), and I'd like to fix that in Buster via s-p-u.
> 

Please go ahead; thanks.

Regards,

Adam

Bug#935465: buster-pu: package jython/2.7.1+repack1-4~deb10u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2019-08-22 at 23:43 +0200, Andreas Beckmann wrote:
> jython/buster introduces a strictly versioned java dependency, which
> causes problems on some upgrade paths from stretch. (#924283,
> #934111)
> This problem originates from the dependency cycle (#929685) between
> ca-certificates-java,default-jre-headless,openjdk-11-jre-headless
> which has not been solved in sid, yet (and has been in several stable
> releases already).
> 
> The cycle gets broken in a way that jython gets configured
> successfully but jython-stilts gets configured subsequently and
> fails because the system is in a state where openjdk-8-jre-headless
> is still active (because openjdk-11-jre-headless is not yet
> configured), but default-jre-headless/buster is already configured.
> jython-stilts calls jython which fails because bytecode compiled for
> java-9+ is getting executed with java-8.
> 
> This problem does not show up in other packages, since none adds
> incompatibility with the java in stretch.
> 
> This was fixed in sid by building jython with backwards compatibility
> with the java in stretch, s.t. it does not matter which java version
> is
> run during the upgrade.
> 

Please go ahead; thanks.

[Note to anyone else reviewing this who has the same query - java7-
runtime-headless is provided by the -11 packages, so this is fine.]

Regards,

Adam

Processed: Re: Bug#935465: buster-pu: package jython/2.7.1+repack1-4~deb10u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #935465 [release.debian.org] buster-pu: package 
jython/2.7.1+repack1-4~deb10u1
Added tag(s) confirmed.

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

RE:Status of libghc-shake-dev

[PICCA Frederic-Emmanuel]

> I just scheduled the set of binNMUs seemingly required Haskell. I hope
> this was the right thing to do at this time. Really someone more active
> should take over that job.

Where is the documentation of this process ?

Cheers,
Frederic

Processed: Re: Bug#935776: buster-pu: [pre-upload approval of] package debian-edu-config/2.10.65+deb10u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +moreinfo
Bug #935776 [release.debian.org] buster-pu: [pre-upload approval of] package 
debian-edu-config/2.10.65+deb10u1
Added tag(s) moreinfo.

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

Bug#935776: buster-pu: [pre-upload approval of] package debian-edu-config/2.10.65+deb10u1

[Adam D. Barratt]

Control: tags -1 +moreinfo

On Mon, 2019-08-26 at 08:17 +0200, Mike Gabriel wrote:
> for Debian Edu 10.1, we'd kindly ask to accept the below fixes into
> Debian 10.1:
> 
> ### Common Bug Fixes
> 
> +debian-edu-config (2.10.65+deb10u1) buster; urgency=medium
> 

Have all of the changes already been applied to the package in
unstable?

Regards,

Adam

Bug#934356: stretch-pu: package mitmproxy/0.18.2-6

[Adam D. Barratt]

On Tue, 2019-08-20 at 23:03 +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Sat, 2019-08-10 at 09:27 +0200, Sebastien Delafond wrote:
> > Could 0.18.2-6+deb9u1 be included in stretch's next point release ?
> > It
> > closes #934033, which is an FTBFS on stretch, by blacklisting a
> > couple
> > #more things from the test suite.
> > 
> 
> Please go ahead.

Our tooling has highlighted a dependency issue. I've not had chance to
check if it already existed in the earlier package, but:

  unsat-dependency: python-cryptography (< 1.6)

stretch has python-cryptography 1.7.1

Regards,

Adam

Bug#935770: buster-pu: package ncbi-tools6/6.1.20170106+dfsg1-0+deb10u2

[Adam D. Barratt]

Control: tags -1 +confirmed

On Sun, 2019-08-25 at 21:27 -0400, Aaron M. Ucko wrote:
> As Adam noted in #934311 (and Paul Gevers reported in #935424), the
> removal of UniVec.* in my previous stable update introduced an
> autopkgtest regression, for which I hereby apologize.  I've prepared
> a
> proposed update that addresses this regression and gives ncbi-data a
> NEWS.Debian.gz file explaining the removal, which clearly turned out
> to have a bigger impact than anticipated.
> 

Please go ahead. Thanks for the fix.

Regards,

Adam

Processed: Re: Bug#935770: buster-pu: package ncbi-tools6/6.1.20170106+dfsg1-0+deb10u2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +confirmed
Bug #935770 [release.debian.org] buster-pu: package 
ncbi-tools6/6.1.20170106+dfsg1-0+deb10u2
Added tag(s) confirmed.

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

Bug#935308: buster-pu: package android-sdk-meta/25.0.0+11

[Adam D. Barratt]

Control: tags -1 + moreinfo

On Wed, 2019-08-21 at 15:44 +0200, Hans-Christoph Steiner wrote:
> I have been working on polishing this package for buster since March,
> but I didn't make the freeze cutoff.  This mostly adds new device IDs
> to
> the udev rules so that those devices will be recognized.  It also
> fixes
> debian/copyright and some minor usability bugs:

Again I have to ask why the changes took so long in that case,
particularly if they're mostly syncs from upstream.

> 924175: broken symlink: /usr/lib/android-sdk/tools/bin/screenshot2
> 923935: broken symlinks: proguardgui, proguardgui.jar
> 
> I uploaded this package to sid so that it runs the autopkgtest suite.

Well, and SRM policy requires the changes to be in unstable first in
any case.

> Here's the changelog since the current version in buster:
> 
>  android-sdk-meta (25.0.0+11) unstable; urgency=medium

The changes we're interested in, and what should be attached in your
request, are the changes between the current package in stable and the
package that you are proposing to upload to stable, as built and tested
on stable ready for upload.

As it is, you've uploaded a package using a version number that is
confusing when combined with your changelog (as we would have pointed
out if you had waited before uploading):

+android-sdk-meta (25.0.0+11~deb10u1) buster; urgency=medium

Such a version should include the changelog for the +11 upload to
unstable, and then have a short "rebuild for buster" or similar stanza
for ~deb10u1, in the same fashion as one would for backports. The style
that you've used is generally used for +10+deb10u1 versioning.
 .
>[ Jeff Muizelaar ]
>* Add some more Amazon devices
>  .
>[ Hans-Christoph Steiner ]
>* fix DEB_REVISION parsing to work with more than one digit
> 

I assume that's this change:

-DEB_REVISION = $(shell echo $(DEB_VERSION) | sed 's,.*\+\([0-9][0-9]*\).*,\1,')
+DEB_REVISION = $(shell echo $(DEB_VERSION) | sed 's,.*+\([0-9][0-9]*\).*,\1,')

However, I'm confused as to how this corresponds to the description. It
removes a match for a literal "+" symbol, but does nothing related to
the number of digits involved so far as I can tell.

>* remove broken screenshot2 symlink (Closes: #924175)
>* Suggests: proguard-gui for symlinks (Closes: #923935)
>* document udev rule for providing device access to the console
> user
>* update udev rules to latest upstream version (Closes: #931215)
>* sync new devices in 51-android.rules from upstream
>* Standards-Version 4.3.0 no changes
>* sync whitespace in 51-android.rules with upstream
>* sync comments in 51-android.rules with upstream
>* sync manufacturer order in 51-android.rules from upstream

Those last three changes sound like they could have made the diff a
fair bit smaller with no functional difference.

 debian/android-sdk.metainfo.xml  |  109 ++

+debian/android-sdk.metainfo.xml  usr/share/metainfo

Is that related to one of the items mentioned in the changelog?

On Mon, 2019-08-26 at 12:18 +0200, Hans-Christoph Steiner wrote:
> I forgot this important detail: LineageOS would recommend this as the
> official install method for these udev rules if this update was
> included in buster:

I'm afraid that's not really important in terms of whether the changes
are suitable for a stable update.

Regards,

Adam

Processed: Re: Bug#935308: buster-pu: package android-sdk-meta/25.0.0+11

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #935308 [release.debian.org] buster-pu: package 
android-sdk-meta/25.0.0+11~deb10u1
Added tag(s) moreinfo.

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

Processed: Bug#935809: Re: buster-pu: package fdroidserver_1.1.4-1~deb10u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #935809 [release.debian.org] buster-pu: package fdroidserver_1.1.4-1~deb10u1
Added tag(s) moreinfo.

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

Bug#935809: Re: buster-pu: package fdroidserver_1.1.4-1~deb10u1

[Adam D. Barratt]

Control: tags -1 + moreinfo

Your report did not make it to debian-release due to the large size of
the attachment. I had to download the mbox from the BTS is order to
reply, which makes me quite surprised to see that you already decided
to upload the package.

On Mon, 2019-08-26 at 14:54 +0200, Hans-Christoph Steiner wrote:
> I have been working on polishing this package for buster since March,
> but I didn't make the freeze cutoff.  I'm part of upstream, and we
> did
> our Debian/buster bug fix work in our stable 1.1.x branch, so the
> changes are mostly in the upstream source tarball.
> 
> The debdiff is long, but the actual code changes are quite short.

If the changes are short, why were they not made in time for buster?

>   What
> makes the debdiff long is the cruft that were removed upstream in the
> source tarball due to a cleanup (see diffstat).

Are you really saying that what looks from the diff like dropping all
localisation support is cruft cleanup? I feel like I may be missing
something.

In any case, cleaning up cruft by removing 60K lines of files from your
source package is generally not the sort of thing that would be
expected in a stable update.

> The next largest block of changes is fixes to the test suite to work
> properly on Debian/buster.
>  The remaining changes are compatibility fixes related to:
> 
> 929905: incompatible with upstream's data repository
[...]
> ### 1.1.4 (2019-08-15)
> 
> * include bitcoin validation regex required by fdroiddata

As someone who knows nothing about fdroiddata, you may have to explain
why this is actually a problem. This is the sort of information that
should be in the request. To be honest, I'd have expected your upstream
diff and changelog to have included more information than that one
line.

Please provide a diff that only includes the non-"cruft" changes, so
there's a chance of us knowing what you're actually changing.

Regards,

Adam

Processed: Re: Bug#935815: buster-pu: package gnome-bluetooth/3.28.2-4~deb10u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #935815 [release.debian.org] buster-pu: package 
gnome-bluetooth/3.28.2-4~deb10u1
Added tag(s) confirmed.

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

Bug#935815: buster-pu: package gnome-bluetooth/3.28.2-4~deb10u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2019-08-26 at 14:52 +0100, Simon McVittie wrote:
> Another in the ongoing series of "get fixes for buster's GNOME 3.30
> backported from unstable before GNOME 3.34 transitions start
> landing".
> 
> The only functional change in this one is to fix a use-after-free
> crash
> when a BluetoothClient is repeatedly allocated and freed. This is
> most
> problematic in practice when a GNOME Shell user installs
> gnome-shell-extension-bluetooth-quick-connect, either as a Debian
> package,
> from extensions.gnome.org or directly from its upstream source code.
> 

Please go ahead; thanks.

Regards,

Adam

Re: Status of libghc-shake-dev

[Joachim Breitner]

Hi,

Am Sonntag, den 25.08.2019, 16:07 + schrieb Dmitry Bogatov:
> Hi!
> 
> With GHC-8.6.5 is in unstable, many haskell libraries are no longer
> uninstallable. Right now I am interested in libghc-shake-dev, since it
> is needed for test suite of src:dh-runit[1].
> 
> So, what is the status? Are there any estimates on when transition will
> complete? Maybe I should start rebuilding and uploading?
> 
> [1] 
> https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dh-runit/2805329/log.gz

I just scheduled the set of binNMUs seemingly required Haskell. I hope
this was the right thing to do at this time. Really someone more active
should take over that job.

Cheers,
Joachim
-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


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

Processed: tagging 934996

[Debian Bug Tracking System]

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

> tags 934996 + pending
Bug #934996 [release.debian.org] transition: xfce4-panel
Added tag(s) pending.
> thanks
Stopping processing here.

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

Re: Bypassing the 2/3/4GB virtual memory space on 32-bit ports

[Mathieu Malaterre]

Aurélien,

Thanks for caring about 32bits arches !

On Thu, Aug 8, 2019 at 10:39 PM Aurelien Jarno  wrote:
[...]
> mips and mipsel are more affected by the issue as the virtual address
> space is limited to 2GB. Therefore on those architectures, this issue
> recently started to also affect core packages like ghc and rustc, and
> the usual tricks are not working anymore.
[...]

(maybe a bit naive) Another way to look at the issue is that ghc and
rustc are core packages on 32bits system. Would it make sense to start
having a separate core32 & core64 instead of a single one ?

Bug#935815: buster-pu: package gnome-bluetooth/3.28.2-4~deb10u1

[Simon McVittie]

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

Another in the ongoing series of "get fixes for buster's GNOME 3.30
backported from unstable before GNOME 3.34 transitions start landing".

The only functional change in this one is to fix a use-after-free crash
when a BluetoothClient is repeatedly allocated and freed. This is most
problematic in practice when a GNOME Shell user installs
gnome-shell-extension-bluetooth-quick-connect, either as a Debian package,
from extensions.gnome.org or directly from its upstream source code.

I haven't backported the whole upstream gnome-3-28 branch this time
because there are more commits there than I was hoping for, and I'd find
it hard to justify them all as minimal fixes.

Thanks,
smcv
diffstat for gnome-bluetooth-3.28.2 gnome-bluetooth-3.28.2

 changelog   |   21 +++
 gbp.conf|2 
 patches/client-Disconnect-all-signal-handlers-when-client-is-disp.patch |   70 ++
 patches/series  |1 
 4 files changed, 93 insertions(+), 1 deletion(-)

diff -Nru gnome-bluetooth-3.28.2/debian/changelog gnome-bluetooth-3.28.2/debian/changelog
--- gnome-bluetooth-3.28.2/debian/changelog	2018-12-23 14:46:03.0 +
+++ gnome-bluetooth-3.28.2/debian/changelog	2019-08-26 11:11:19.0 +0100
@@ -1,3 +1,24 @@
+gnome-bluetooth (3.28.2-4~deb10u1) buster; urgency=medium
+
+  * Team upload
+  * d/p/client-Disconnect-all-signal-handlers-when-client-is-disp.patch:
+Mark as applied upstream for 3.33.91
+  * d/gbp.conf: Set packaging branch to debian/buster
+  * Rebuild for buster
+
+ -- Simon McVittie   Mon, 26 Aug 2019 11:11:19 +0100
+
+gnome-bluetooth (3.28.2-4) unstable; urgency=medium
+
+  * Team upload
+  * d/p/client-Disconnect-all-signal-handlers-when-client-is-disp.patch:
+Add proposed patch to avoid GNOME Shell crashes when
+gnome-shell-extension-bluetooth-quick-connect is used
+(Closes: #932405)
+  * d/gbp.conf: Set Debian branch to debian/unstable
+
+ -- Simon McVittie   Sun, 18 Aug 2019 15:21:00 +0100
+
 gnome-bluetooth (3.28.2-3) unstable; urgency=medium
 
   * Restore -Wl,-O1 to our LDFLAGS
diff -Nru gnome-bluetooth-3.28.2/debian/gbp.conf gnome-bluetooth-3.28.2/debian/gbp.conf
--- gnome-bluetooth-3.28.2/debian/gbp.conf	2018-12-23 14:46:03.0 +
+++ gnome-bluetooth-3.28.2/debian/gbp.conf	2019-08-26 11:11:19.0 +0100
@@ -1,6 +1,6 @@
 [DEFAULT]
 pristine-tar = True
-debian-branch = debian/master
+debian-branch = debian/buster
 upstream-branch = upstream/latest
 
 [buildpackage]
diff -Nru gnome-bluetooth-3.28.2/debian/patches/client-Disconnect-all-signal-handlers-when-client-is-disp.patch gnome-bluetooth-3.28.2/debian/patches/client-Disconnect-all-signal-handlers-when-client-is-disp.patch
--- gnome-bluetooth-3.28.2/debian/patches/client-Disconnect-all-signal-handlers-when-client-is-disp.patch	1970-01-01 01:00:00.0 +0100
+++ gnome-bluetooth-3.28.2/debian/patches/client-Disconnect-all-signal-handlers-when-client-is-disp.patch	2019-08-26 11:11:19.0 +0100
@@ -0,0 +1,70 @@
+From: Simon McVittie 
+Date: Tue, 13 Aug 2019 15:53:49 +0100
+Subject: client: Disconnect all signal handlers when client is disposed
+
+I've encountered an intermittent GNOME Shell crash when needrestart[1]
+is allowed to restart system services that are using outdated shared
+libraries, which sometimes includes BlueZ. The crash seems to involve
+signals being delivered to a freed BluetoothClient, which can be avoided
+by using g_signal_connect_object(). I haven't encountered the crash
+since applying this change, although since it was always intermittent
+I cannot be sure that it is fully solved.
+
+This might be caused by using the Bluetooth Quick Connect shell
+extension[2], which will create and destroy a BluetoothClient when the
+extension is loaded and unloaded, which will in turn happen when the
+screen is locked (due to extensions being disabled in the lock screen).
+
+[1] https://github.com/liske/needrestart
+[2] https://extensions.gnome.org/extension/1401/bluetooth-quick-connect/
+
+Signed-off-by: Simon McVittie 
+Bug-Debian: https://bugs.debian.org/932405
+Forwarded: https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/17
+Applied-upstream: 3.33.91, commit:9c94e30c
+---
+ lib/bluetooth-client.c | 16 
+ 1 file changed, 8 insertions(+), 8 deletions(-)
+
+diff --git a/lib/bluetooth-client.c b/lib/bluetooth-client.c
+index 0be5089..2c039b3 100644
+--- a/lib/bluetooth-client.c
 b/lib/bluetooth-client.c
+@@ -392,8 +392,8 @@ device_added (GDBusObjectManager   *manager,
+ 	BluetoothType type;
+ 	GtkTreeIter iter, parent;
+ 
+-	g_signal_connect (G_OBJECT (device), "notify",
+-			  G_CALLBACK (device_notify_cb), client);
++	g_signal_connect_object (G_OBJECT (device), 

Re: Bypassing the 2/3/4GB virtual memory space on 32-bit ports

[Stefan Monnier]

> Your entire argument is built on the premis that it is actually
> desirable for these applications (compilers, linkers, etc) to work in
> 32-bit address spaces.

Why wouldn't it?

Of all my machines (2x BananaPi, 1x mac-mini, 1x T60, 1x T61, 1x X201s,
1x desktop PC) only 3 can take more than 3GB of memory and only 1 can
take more than 8GB (more specifically, it can take upto 16GB).

Am I supposed to throw away that hardware and go buy something new every
few years just because people can't be bothered to fix their
compilation-performance bugs?  Sounds like an ecological disaster to me.


Stefan


PS: The BananaPi's 1GB was sufficient to Git-clone and recompile Debian's
kernel last year, without any need to tweak options.
Why should other programs fare so much worse?
I'd simply consider it a bug if a program needs more than 2GB
to compile.

Processed: retitle

[Debian Bug Tracking System]

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

> retitle 935308 buster-pu: package android-sdk-meta/25.0.0+11~deb10u1
Bug #935308 [release.debian.org] buster-pu: package android-sdk-meta/25.0.0+11
Changed Bug title to 'buster-pu: package android-sdk-meta/25.0.0+11~deb10u1' 
from 'buster-pu: package android-sdk-meta/25.0.0+11'.
>
End of message, stopping processing here.

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

Bug#935370: buster-pu: package lacme/0.5-1+deb10u1

[Guilhem Moulin]

Hi KiBi,

On Mon, 26 Aug 2019 at 08:22:47 +0200, Cyril Brulebois wrote:
> I'll let someone else comment on that point, to ensure I'm not making
> you jump through hoops needlessly…

I vaguely recall seeing debdiffs without ‘Closes: #XXX’, but better safe
than sorry ^^  It makes sense to track the deprecation in our BTS anyway
(#935799).  New debdiff attached.

Thanks!
Cheers,
-- 
Guilhem.
diffstat for lacme-0.5 lacme-0.5

 changelog |   11 +
 gbp.conf  |2 
 patches/0002-Issue-GET-and-POST-as-GET-requests.patch |  121 ++
 patches/series|1 
 4 files changed, 134 insertions(+), 1 deletion(-)

diff -Nru lacme-0.5/debian/changelog lacme-0.5/debian/changelog
--- lacme-0.5/debian/changelog  2018-05-09 14:17:19.0 +0200
+++ lacme-0.5/debian/changelog  2019-08-22 00:14:42.0 +0200
@@ -1,3 +1,14 @@
+lacme (0.5-1+deb10u1) buster; urgency=medium
+
+  * Link to RFC 8555  instead of the
+ACME I-D URL.
+  * Issue GET and POST-as-GET requests (RFC 8555 sec. 6.3) for the
+authorizations, order and certificate URLs.   Let's Encrypt will remove
+support of unauthenticated GETs from the V2 API on 01 Nov 2019.
+Closes: #935799.
+
+ -- Guilhem Moulin   Thu, 22 Aug 2019 00:14:42 +0200
+
 lacme (0.5-1) unstable; urgency=medium
 
   * New upstream release, adding support for v2 ACME endpoints.
diff -Nru lacme-0.5/debian/gbp.conf lacme-0.5/debian/gbp.conf
--- lacme-0.5/debian/gbp.conf   2018-05-09 14:17:19.0 +0200
+++ lacme-0.5/debian/gbp.conf   2019-08-22 00:14:42.0 +0200
@@ -1,6 +1,6 @@
 [DEFAULT]
 upstream-branch = master
-debian-branch = debian
+debian-branch = debian-buster
 upstream-tag = upstream/%(version)s
 debian-tag = debian/%(version)s
 pristine-tar = False
diff -Nru 
lacme-0.5/debian/patches/0002-Issue-GET-and-POST-as-GET-requests.patch 
lacme-0.5/debian/patches/0002-Issue-GET-and-POST-as-GET-requests.patch
--- lacme-0.5/debian/patches/0002-Issue-GET-and-POST-as-GET-requests.patch  
1970-01-01 01:00:00.0 +0100
+++ lacme-0.5/debian/patches/0002-Issue-GET-and-POST-as-GET-requests.patch  
2019-08-22 00:14:42.0 +0200
@@ -0,0 +1,121 @@
+From f9d5e53cac1c002e5983efc18e42f5a21444b182 Mon Sep 17 00:00:00 2001
+From: Guilhem Moulin 
+Date: Wed, 21 Aug 2019 17:29:19 +0200
+Subject: Issue GET and POST-as-GET requests (RFC 8555 sec. 6.3)
+
+For the  authorizations, order and certificate URLs.
+See RFC 8555 sec. 7.1.
+---
+ client|   22 +++---
+ lacme-accountd.md |2 +-
+ lacme.md  |2 +-
+ 3 files changed, 13 insertions(+), 13 deletions(-)
+
+--- a/client
 b/client
+@@ -165,16 +165,16 @@ sub request_json_decode($;$$) {
+ #
+ # JSON-encode the hash reference $h and send it to the ACME server $uri
+ # encapsulated it in a JSON Web Signature (JWS).
+-# https://tools.ietf.org/html/draft-ietf-acme-acme-12
++# https://tools.ietf.org/html/rfc8555
+ #
+-sub acme($@) {
+-my $uri = shift;
++sub acme($;$) {
++my ($uri, $h) = @_;
+ die "Missing nonce\n" unless defined $NONCE;
+ 
+ # Produce the JSON Web Signature: RFC 7515 section 5
+ my %header = ( alg => 'RS256', nonce => $NONCE, url => $uri );
+ defined $KID ? ($header{kid} = $KID) : ($header{jwk} = $JWK);
+-my $payload = encode_base64url(json()->encode({ @_ }));
++my $payload = defined $h ? encode_base64url(json()->encode($h)) : "";
+ my $protected = encode_base64url(json()->encode(\%header));
+ my $data = $protected .'.'. $payload;
+ $S->printflush($data, "\r\n");
+@@ -204,7 +204,7 @@ sub acme_resource($%) {
+ request(HEAD => $RES{newNonce});
+ }
+ my $uri = $RES{$r} // die "Unknown resource '$r'\n";
+-acme($uri, @_);
++acme($uri, {@_});
+ }
+ 
+ # Set the key ID (registration URI)
+@@ -237,7 +237,7 @@ if ($COMMAND eq 'account') {
+ 
+ if ($r->is_success()) {
+ $KID = $r->header('Location');
+-$r = acme($KID, %h);
++$r = acme($KID, \%h);
+ request_json_decode($r, 1, \*STDOUT)
+ if $r->is_success() and $r->content_type() eq 'application/json';
+ }
+@@ -264,7 +264,7 @@ elsif ($COMMAND eq 'newOrder') {
+ my $order = request_json_decode($r);
+ 
+ foreach (@{$order->{authorizations}}) {
+-my $authz = request_json_decode(request(GET => $_));
++my $authz = request_json_decode(acme($_));
+ next unless $authz->{status} eq 'pending';
+ 
+ my $identifier = $authz->{identifier}->{value};
+@@ -288,7 +288,7 @@ elsif ($COMMAND eq 'newOrder') {
+ die "Can't open $challenge->{token}: $!";
+ }
+ 
+-$r = acme($challenge->{url});
++$r = acme($challenge->{url}, {});
+ 
+ # poll until the status become 'valid'
+ # XXX poll the 

Bug#935308: LineageOS

[Hans-Christoph Steiner]

I forgot this important detail: LineageOS would recommend this as the
official install method for these udev rules if this update was included
in buster:

https://review.lineageos.org/c/LineageOS/lineage_wiki/+/244577#message-39c50c8a9de8cd3fa4cc61322fd3f96b94ba36ef

Processed: tagging 931950

[Debian Bug Tracking System]

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

> tags 931950 + confirmed
Bug #931950 [release.debian.org] transition: libgeotiff
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#934995: transition: xfconf

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, 2019-08-25 at 19:46 +, Niels Thykier wrote:
> jmw already scheduled the binNMUs already so everything but
> xfce4-sntray-plugin has been rebuilt successfully by now (some of the
> builds are still pending uploads though).

Thanks for the schedule. We have few packages with sourceful uploads but it
doesn't really matter anyway.
> 
> I assume you have the ball on xfce4-sntray-plugin (either by filing an
> RC bug against it or/and uploading a fix).

sntray isn't under the xfce-team umbrella so honestly I don't know but we'll
try to get in touch with the maintainers.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl1jj/oACgkQ3rYcyPpX
RFsuXwgAtQ2zkpjQopRzoVPjuzObfazKYnOAMFdZ6xUoU1noy6PrbVerH8LKSHVD
hfZ1aH+MJjZGn9IGX8e5il7UPn0ZxGNwQ2PtE5631/ADMEdhe9NqVoHaURtjejQl
M4TGQX34Tj4nVauXSINTtCJOyc5pN13W15LAjXxLl2snp+OkDZX0Glzki9N8671y
5ArG/IKjiACSy6jufXpkyEEAf5S2eYhhQNwMP9spS6Ct6kWs+KGnuHWzXBMF8zLT
Ths+2MvZ+XrtQxe9GtbNca7CPo6fKmNK1tRDIUOjBGBoCFpN0BXslxV5zsWE2f2+
u17TRh/1cPfQMEfxKJHu1hV8dOsw9w==
=rDsL
-END PGP SIGNATURE-

Bug#934928: win32-loader FTBFS on stable - any idea ?

[Didier 'OdyX' Raboud]

Le dimanche, 25 août 2019, 12.20:16 h CEST Simon McVittie a écrit :
> On Sat, 24 Aug 2019 at 18:49:20 +0200, Didier 'OdyX' Raboud wrote:
> > The difference I finally found was that the buildds use LANG=C.UTF-8 and
> > LC_ALL=C.UTF-8 whereas mine was not enforcing these (and so I was building
> > with LC_ALL=POSIX).
> 
> This was a change in sbuild 0.78.0, so in practice a difference between
> buildds hosted on <= stretch (which used LC_ALL=POSIX) and buildds hosted
> on >= buster (which use LC_ALL=C.UTF-8).

Ah, thanks for the background.

> > +# A non-UTF-8 locale is needed for the NSIS build to convert some
> > language
> > strings
> > +LC_ALL := POSIX
> > +export LC_ALL
> 
> This is the first time I've encountered a package where changing the locale
> to C.UTF-8 *causes* FTBFS - normally the failure mode is that unit tests
> assume a UTF-8 (or at least legacy 8-bit) locale, and fail in LC_ALL=POSIX
> (or equivalently LC_ALL=C).

win32-loader is special™ :-)

> It would be interesting to know whether the Farsi locale *works* in the
> resulting build; but if it doesn't, then that probably isn't a regression,
> because version 0.9.4 in buster would probably be broken in the same way.

I have not tested win32-loader in non-Wine win32 environments recently, so 
we'd need someone with a Farsi Windows to test this.

But I see that Thomas is doing a lot of work on the experimental branch, and 
we should let this hit unstable soon!

Cheers,
OdyX

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

Bug#934928: win32-loader FTBFS on stable - any idea ?

[Didier 'OdyX' Raboud]

Le samedi, 24 août 2019, 20.26:37 h CEST Adam D. Barratt a écrit :
> On Sat, 2019-08-24 at 18:49 +0200, Didier 'OdyX' Raboud wrote:
> > @Adam: I assume I need to bump the version number and upload again,
> > right?
> 
> Yep.
> 
> (I assume the changelog etc still end up generated as UTF-8.)

Yep. So uploaded.

-- 
OdyX

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

Bug#935253: buster-pu: package cups/2.2.10-6+deb10u1

[Didier 'OdyX' Raboud]

Le dimanche, 25 août 2019, 17.37:47 h CEST Adam D. Barratt a écrit :
> Control: tags -1 -moreinfo +confirmed
> 
> On Wed, 2019-08-21 at 10:01 +0200, Didier 'OdyX' Raboud wrote:
> > This bug is about fixing the CVE-2019-8696, CVE-2019-8675 and other
> > security bugs fixed by CUPS upstream in [0] in buster.
> > 
> > The Security Team has declined fixing these in a security upload; so
> > here I come for a Stable update. The Stretch counterpart bug is
> > #935254.
> > 
> > The debdiff for Buster is attached. Can I (source-only) upload?
> 
> Yes, please go ahead.

Uploaded.

Thanks for your work!

OdyX

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

Bug#935370: buster-pu: package lacme/0.5-1+deb10u1

[Cyril Brulebois]

Hi Guilhem,

Guilhem Moulin  (2019-08-22):
> Package: release.debian.org
> Severity: normal
> Tags: buster
> User: release.debian@packages.debian.org
> Usertags: pu
> 
> Dear release team,
> 
> Per RFC 8555 sec 6.3 the Let's Encrypt folks are deprecating
> unauthenticated GETs from their v2 API.  Support for these requests will
> be removed on *Nov 01 2019* (so likely between Debian 10.1 and 10.2) [0].
> 
> lacme uses the v2 API by default since 0.5, and removing support for
> unauthenticated GETs means that applying for certificate issuance will
> stop working.  Replacing GETs with POST-as-GETs is trivial (debdiff
> attached), and I'd like to fix that in Buster via s-p-u.
> 
> (0.6 from Sid is not affected, and neither is 0.2 from Stretch as the
> latter supports only the v1 API.)

That seems like a welcome change indeed but I'm not entirely sure we're
accepting pu requests that have no matching bug reports against the
affected package; admittedly, it's been a while since I've last handled
pu requests, so I need to get my memory refreshed a little…

I'll let someone else comment on that point, to ensure I'm not making
you jump through hoops needlessly…


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#935776: buster-pu: [pre-upload approval of] package debian-edu-config/2.10.65+deb10u1

[Mike Gabriel]

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


Dear release team,

for Debian Edu 10.1, we'd kindly ask to accept the below fixes into Debian 10.1:

### Common Bug Fixes

+debian-edu-config (2.10.65+deb10u1) buster; urgency=medium
+
+  [ Wolfgang Schweer ]
+  * Adjust ltsp-build-client/Debian-custom/001-ltsp-setting. (Closes: #928756)
+- Use PXE option 'ipappend 2' for LTSP client boot. This option makes sure
+  that all DHCP server information is getting through to LTSP clients.
+  (LTSP used this option before, but switched to 'ipappend 3' during the
+  Buster development cycle to ease setups with ProxyDHCP.)

This resolves an issue on the LTSP client network of a Debian Edu LTSP
server. It was observed that the search domain did not get propagated to
the LTSP clients.

+  * Adjust share/debian-edu-config/sudo-ldap.conf. (Closes: #929964)
+- Fix sudo-ldap configuration. (The LDAP URI is needed on LDAP clients.)

Make sure LDAP configured sudo configuration is found by Debian Edu
client systems.

+  * Set environment variable to deal with Firefox profile. (Closes: #930122)
+This is a workaround for bug #930125, preventing firefox-esr startup issues
+if the mozilla profile is on an NFS share).
+- Ship share/debian-edu-config/edu-firefox-nfs with NSS_SDB_USE_CACHE="yes"
+  as content. Thanks to Mike Gabriel for spotting the issue and providing
+  this information.
+- Add instructions to cf3/cf.workarounds to link the 'edu-firefox-nfs' file
+  to appropriate files below '/etc/X11/Xsession.d' and '/etc/profile.d'.

It was observed that Firefox delays its start-up tremendously (by
serveral 10s of seconds), if the home directory is on NFS. On Debian Edu
networks, homes are mostly always on NFS shares. Such a delay of Firefox
startups in class rooms is unacceptable.

+  * Adjust cf3/cf.homes: Set correct LTSP chroot path. (Closes: #931680)
+- While the reported arch is i686, LTSP uses i386. Set arch accordingly.

If people happen to do i386 LTSP server installations, the above change
fixes the correct creation of /etc/exports (used for sharing the LTSP clients'
chroot over NFS).

+  * Adjust share/debian-edu-config/tools/kerberos-kdc-init. (Closes: #931366)
+- Remove outdated (and now wrong) logging section.

The [logging] section in krb5.conf needs to be removed to make Kerberos logging
work via systemd/journald.

+  * Fix loss of dynamically allocated v4 IP address. (Closes: #933580)
+- Drop etc/network/if-up.d/hostname. This script doesn't work anymore due
+  to changed behaviour of the ifupdown/dhclient/systemd combination and now
+  also causes the loss of a dynamically allocated ipv4 IP address after 20
+  to 30 minutes after booting.
+- Add code to d/debian-edu-config.postinstall to implement the intended
+  hostname update just after rebooting the system after a change.
+- Adjust Makefile.

It was observed that Debian Edu hosts using ifupdown for network setup lost 
their
network connection after 20 to 30 minutes. (Work-around was to replace ifupdown 
by
NetworkManager). The above changes resolve this problem (RC bug).

### Debian Edu PKI Re-Doings

The Debian Edu PKI had been entirely redone by Wolfgang Schweer between
Debian Edu 9 and Debian Edu 10. After Debian Edu 10 was released, I
migrated a huge school setup from Debian Edu 8 + 9 (mixed setup) to
Debian Edu 10 and finally found the time to post-release review those PKI
re-doings.

The below changes all tackle fixes, also slight concept changes, that the
Debian Edu team would love to see accepted into Debian (Edu) 10.1:

+  * Provide Debian Edu RootCA certificate for download. (Closes: #933183)
+- Adjust share/debian-edu-config/tools/create-debian-edu-certs to copy the
+  rootCA file to the web server directory at certificate generation time.
+- Adjust cf3/cf.finalize to care for the rootCA file as well.
+- Adjust cf3/cf.workarounds to copy the rootCA file to the web server
+  directory upon main server upgrade.

In Debian Edu 10.0, a crt bundle file got distributed via the main
server. This was implicitly handled by the init script fetch-ldap-cert.

The concept change for 10.1 is: distribute the CA file of the self-signed
Debian Edu PKI instead. The above changes modify the main server on
upgrades accordingly, so that the Debian-Edu_RootCA file is available for
download via http://www.intern/.

+  * Add LDAP server certificate to the initial LTSP NBD image. (Closes: 
#932828)
+- etc/ltsp/ltsp-build-client.conf: Don't create the image by default.
+- cf3/edu.cf: Define new class 'ltspimages'.
+- cf3/cf.finalize: Add code to include the LDAP server certificate for all
+  possible use cases, to generate the image and to adjust various rights.

This injects a certificate installation between chroot debootstrapping
and the creation of the SquashFS LTSP client 

Processed: Re: Bug#935392: buster-pu: package sogo/4.0.7-1+deb10u1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 confirmed
Bug #935392 [release.debian.org] buster-pu: package sogo/4.0.7-1+deb10u1
Added tag(s) confirmed.

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

Bug#935392: buster-pu: package sogo/4.0.7-1+deb10u1

[Cyril Brulebois]

Control: tag -1 confirmed

Hi Jordi,

Jordi Mallach  (2019-08-22):
> I'm requesting permission to upload sogo to stable-pu, to fix a high
> impact usability bug when dealing with S/MIME signed emails.

That looks good to me, please go ahead.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#935386: buster-pu: package raspi3-firmware/1.20190215-1+deb10u1

[Cyril Brulebois]

Hi,

Cyril Brulebois  (2019-08-22):
> I'll double check that my cherry-picks on top of the buster branch
> still do the trick, but it seems to me we should be able to move this
> pu request forward without blocking on the linux bits.

This resulted in this specific merge request, that was merged into
buster but still needs an upload:
  https://salsa.debian.org/kernel-team/linux/merge_requests/169

> The changelog reads:
> 
> ,---
> | raspi3-firmware (1.20190215-1+deb10u1) buster; urgency=medium
> | 
> |   * Add support for bcm2837-rpi-cm3-io3.dtb (as generated by the Linux
> | kernel build system) aka. bcm2710-rpi-cm3.dtb (as expected by the
> | bootloader), designed to work for:
> |  - Raspberry Pi Compute Module 3 (CM3);
> |  - Raspberry Pi Compute Module 3 Lite (CM3L);
> |  - Raspberry Pi Compute Module IO Board V3.
> | With many thanks to Charles Fendt for the tests (#932158).
 ^^^

A “Closes:” is missing in front of it…

> |   * The DTB addition in the linux source package is tracked in #932157.
> | 
> |  -- Cyril Brulebois   Thu, 22 Aug 2019 09:15:16 +0200
> `
> 
> and the full source debdiff is attached.
> 
> 
> (I've OK'd this pu request with Romain Perier, who is one of the
> maintainers; all of them are in X-D-Cc anyway.)

I had initially thought the unstable upload had reached the archive but
some GPG errors delayed its being processed. After a sponsored upload,
it reached the NEW queue (raspi3-firmware was renamed to raspi-firmware,
given the brand new Pi 4…), and was accepted from there. So the bugfix
I'd like to backport to buster is in unstable finally.


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/


signature.asc
Description: PGP signature