fwupd_0.7.4-2+deb9u1 (was: "Re: Debian 9 (Stretch) LTS: archive side should be done")

2020-07-09 Thread Chris Lamb
Hi all, > In any case, please be careful with what you upload. There is a point release > planned for the 18th (the final point release for stretch) so uploads are > still > going there I loaded the release.debian@packages.debian.org "pu" usertag page on the BTS while triaging earlier today.

Re: [Git][security-tracker-team/security-tracker][master] data/dla-needed.txt: Claim gosa.

2020-07-09 Thread Emilio Pozuelo Monfort
Hi Chris, On 09/07/2020 11:54, Chris Lamb wrote: > Commits: > 389b61df by Chris Lamb at 2020-07-09T10:54:19+01:00 > data/dla-needed.txt: Claim gosa. Please note that there's a gosa package in opu for the upcoming point release. So it'd be good to wait with this until after the point release to av

Re: fwupd_0.7.4-2+deb9u1 (was: "Re: Debian 9 (Stretch) LTS: archive side should be done")

2020-07-09 Thread Moritz Muehlenhoff
On Thu, Jul 09, 2020 at 10:52:18AM +0100, Chris Lamb wrote: > However, as I understand it, this pu bug has not been confirmed yet > and this would actually update the version in oldstable to the > 0.8.x branch anyway, i.e. larger than my 0.7.4-2+deb9u1. I therefore > conclude that this is fine *thi

Re: [Git][security-tracker-team/security-tracker][master] data/dla-needed.txt: Claim gosa.

2020-07-09 Thread Adrian Bunk
On Thu, Jul 09, 2020 at 11:59:19AM +0200, Emilio Pozuelo Monfort wrote: >... > Please note that there's a gosa package in opu for the upcoming point release. > So it'd be good to wait with this until after the point release to avoid any > conflicts. I've just added notes about pending stretch-pu u

Re: [Git][security-tracker-team/security-tracker][master] data/dla-needed.txt: Claim gosa.

2020-07-09 Thread Sylvain Beucler
On 09/07/2020 12:35, Adrian Bunk wrote: > On Thu, Jul 09, 2020 at 11:59:19AM +0200, Emilio Pozuelo Monfort wrote: >> ... >> Please note that there's a gosa package in opu for the upcoming point >> release. >> So it'd be good to wait with this until after the point release to avoid any >> conflicts