Bug#934183: buster-pu: package open-vm-tools/2:10.3.10-1+deb10u1

2019-08-18 Thread Bernd Zeimetz
On 8/18/19 4:35 PM, Adam D. Barratt wrote: > On Wed, 2019-08-07 at 21:44 +0200, Bernd Zeimetz wrote: >> I'd like to upload a fix for open-vm-tools to proposed-updates which >> actually allows to recognize buster. >> >> `lsb_release -sd` currently prints >>    Debian GNU/Linux 10 (buster) >> but

Bug#934368: transition: x265

2019-08-18 Thread Sebastian Ramacher
On 2019-08-18 17:58:59, Jonathan Wiltshire wrote: > > As usual, libx265 bumped its SONAME. All reverse dependencies build fine > > against the new version. Please let me know once it's a good time to > > upload the new version from experimental to unstable. > > Please go ahead. Thanks, uploaded.

Bug#933125: buster-pu: package systemd/241-5+deb10u1

2019-08-18 Thread Michael Biebl
Hi Adam Am 16.08.19 um 22:08 schrieb Adam D. Barratt: > Control: tags -1 + confirmed > > On Fri, 2019-07-26 at 21:43 +0200, Michael Biebl wrote: >> I'd like to make a stable upload for systemd, fixing the following >> issues: > [...] >> 241-5+deb10u1 is identical to 241-7 which has been uploaded

Bug#934368: transition: x265

2019-08-18 Thread Jonathan Wiltshire
Control: tag -1 confirmed On Sat, Aug 10, 2019 at 10:47:03AM +0200, Sebastian Ramacher wrote: > As usual, libx265 bumped its SONAME. All reverse dependencies build fine > against the new version. Please let me know once it's a good time to > upload the new version from experimental to unstable.

Processed: Re: Bug#934368: transition: x265

2019-08-18 Thread Debian Bug Tracking System
Processing control commands: > tag -1 confirmed Bug #934368 [release.debian.org] transition: x265 Added tag(s) confirmed. -- 934368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: closing 934112

2019-08-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 934112 Bug #934112 [release.debian.org] transition: poco Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 934112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934112 Debian Bug

Bug#931551: transition: llvm-defaults to 8

2019-08-18 Thread Jonathan Wiltshire
Control: tag -1 confirmed On Sun, Jul 07, 2019 at 04:29:31PM +0200, Sylvestre Ledru wrote: > Now that we release buster, I would like to move llvm-defaults to > llvm-toolchain-8. Ok, let's go! Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer

Processed: Re: Bug#931551: transition: llvm-defaults to 8

2019-08-18 Thread Debian Bug Tracking System
Processing control commands: > tag -1 confirmed Bug #931551 [release.debian.org] transition: llvm-defaults to 8 Added tag(s) confirmed. -- 931551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931551 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Re: Bits from the Release Team: ride like the wind, Bullseye!

2019-08-18 Thread Mattia Rizzolo
On Sun, Aug 18, 2019 at 08:54:21AM +0100, Ian Jackson wrote: > > On 19/08/08 09:46, Paul Gevers wrote: > > > I think we should also try to improve the visibility towards reverse > > > dependencies that their autopkgtest is blocking other packages. I would > > > love tracker (and the old pts) to

Re: Bug#933002: docker.io: CVE-2019-13139

2019-08-18 Thread Adam D. Barratt
On Sun, 2019-08-18 at 16:56 +0200, Arnaud Rebillout wrote: > * The bug you want to fix in stable must be fixed in unstable >   already (and not waiting in NEW or the delayed queue) > > My issue with this particular bug (#933002) is that for now, > docker.io  doesn't build in unstable. It

Re: Bug#933002: docker.io: CVE-2019-13139

2019-08-18 Thread Arnaud Rebillout
  Dear Release Team, I'm new to the process of uploading to stable, I need your guidance on that one. From the buster announce:    * The bug you want to fix in stable must be fixed in unstable  already (and not waiting in NEW or the delayed queue) My issue with this particular bug

Bug#933793: stretch-pu: package usbutils/1:007-4+deb9u1

2019-08-18 Thread Aurelien Jarno
On 2019-08-18 15:27, Adam D. Barratt wrote: > On Sat, 2019-08-03 at 16:42 +0200, Aurelien Jarno wrote: > > I would like to update usbutils in stretch to update the usb.ids > > database. There is no code change, the changes only adds a few > > hundred of USB devices to the database. There are a lot

Processed: Re: Bug#934163: buster-pu: package ncurses/6.1+20181013-2+deb10u1

2019-08-18 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + confirmed d-i Bug #934163 [release.debian.org] buster-pu: package ncurses/6.1+20181013-2+deb10u1 Added tag(s) confirmed. -- 934163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934163 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#934206: buster-pu: package golang-github-docker-docker-credential-helpers/0.6.1-2+deb10u1

2019-08-18 Thread Arnaud Rebillout
On 8/16/19 9:35 PM, Adam D. Barratt wrote: So is the conclusion there that docker.io is or is not actually affected? Yes docker.io is affected as well.

Bug#934163: buster-pu: package ncurses/6.1+20181013-2+deb10u1

2019-08-18 Thread Adam D. Barratt
Control: tags -1 + confirmed d-i On Wed, 2019-08-07 at 18:01 +0200, Sven Joachim wrote: > I have just uploaded ncurses 6.1+20181013-2+deb10u1 to Buster which > contains a one-line fix for bug #933053[1], the same as in version > 6.1+20190713-2 which is now in testing. > > Some background: for

Bug#934183: buster-pu: package open-vm-tools/2:10.3.10-1+deb10u1

2019-08-18 Thread Adam D. Barratt
On Wed, 2019-08-07 at 21:44 +0200, Bernd Zeimetz wrote: > I'd like to upload a fix for open-vm-tools to proposed-updates which > actually allows to recognize buster. > > `lsb_release -sd` currently prints >    Debian GNU/Linux 10 (buster) > but the current implementation in open-vm-tools expects

Bug#934952: stretch-pu: package icu/57.1-6+deb9u3

2019-08-18 Thread Adam D. Barratt
Control: tags -1 + confirmed On Sat, 2019-08-17 at 10:20 +0200, László Böszörményi wrote: > There's a crash in Stretch with ICU, there's a missing NULL check in > the LocalArray class. It crashes ICU with certain options / use > case[1]. Upstream fixed it[2] and now I would like to make it to >

Processed: Re: Bug#934952: stretch-pu: package icu/57.1-6+deb9u3

2019-08-18 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + confirmed Bug #934952 [release.debian.org] stretch-pu: package icu/57.1-6+deb9u3 Added tag(s) confirmed. -- 934952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#934956: buster-pu: package cryptsetup/2:2.1.0-5+deb10u1

2019-08-18 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + confirmed d-i Bug #934956 [release.debian.org] buster-pu: package cryptsetup/2:2.1.0-5+deb10u1 Added tag(s) d-i and confirmed. -- 934956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934956 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#934956: buster-pu: package cryptsetup/2:2.1.0-5+deb10u1

2019-08-18 Thread Adam D. Barratt
Control: tags -1 + confirmed d-i On Sat, 2019-08-17 at 11:03 +0200, Guilhem Moulin wrote: > Buster's cryptsetup (2:2.1.0-5) doesn't cope well with LUKS2 headers > without any bound keyslot: adding a new key slot to such a header > fails, both via the crypt_keyslot_add_by_volume_key() API call and

Bug#933793: stretch-pu: package usbutils/1:007-4+deb9u1

2019-08-18 Thread Adam D. Barratt
On Sat, 2019-08-03 at 16:42 +0200, Aurelien Jarno wrote: > I would like to update usbutils in stretch to update the usb.ids > database. There is no code change, the changes only adds a few > hundred of USB devices to the database. There are a lot of new > entries as this hasn't been updated for

Bug#934872: marked as done (RM: ocaml-usb/1.3.0-4 ocaml-sqlexpr/0.5.5-3 zeroinstall-injector/2.12.3-2 obus/1.1.5-6)

2019-08-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Aug 2019 15:26:14 +0200 with message-id <54380ddc-3434-49e3-12af-0a72393e0...@debian.org> and subject line Re: Bug#934872: RM: ocaml-usb/1.3.0-4 ocaml-sqlexpr/0.5.5-3 zeroinstall-injector/2.12.3-2 obus/1.1.5-6 has caused the Debian Bug report #934872, regarding RM:

Bug#935028: marked as done (nmu: lutok_0.4+dfsg-1)

2019-08-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Aug 2019 12:18:40 +0100 with message-id <1566127120.5665.11.ca...@adam-barratt.org.uk> and subject line Re: Bug#935028: nmu: lutok_0.4+dfsg-1 has caused the Debian Bug report #935028, regarding nmu: lutok_0.4+dfsg-1 to be marked as done. This means that you claim that

Bug#933764: buster-pu: package e2fsprogs/1.44.5-1+deb10u1

2019-08-18 Thread Nicolas Braud-Santoni
Control: tag -1 - d-i Hi Jonathan, On Sun, Aug 04, 2019 at 02:37:25PM +0100, Jonathan Wiltshire wrote: > As there's a udeb involved I will just check with the d-i release managers > that this isn't an issue, though I can't see that fixing a crash would be > all that controversial. I can confirm

Processed: Re: Bug#933764: buster-pu: package e2fsprogs/1.44.5-1+deb10u1

2019-08-18 Thread Debian Bug Tracking System
Processing control commands: > tag -1 - d-i Bug #933764 [release.debian.org] buster-pu: package e2fsprogs/1.44.5-1+deb10u1 Removed tag(s) d-i. -- 933764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#935028: nmu: lutok_0.4+dfsg-1

2019-08-18 Thread Nicolas Braud-Santoni
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 nmu lutok_0.4+dfsg-1 . all amd64 . unstable . -m "Rebuild on buildd for transition to bullseye" - -- System Information: Debian Release:

Re: Bits from the Release Team: ride like the wind, Bullseye!

2019-08-18 Thread Ian Jackson
Lisandro Damián Nicanor Pérez Meyer writes ("Re: Bits from the Release Team: ride like the wind, Bullseye!"): > My personal point of view (and because of this it might be biased) > is that the maintainers of the packages that ship autopkgtest should > be the reponsibles for any breackage it might