Processed: tagging 1010196, tagging 1010197

Processing commands for cont...@bugs.debian.org: > tags 1010196 + bullseye Bug #1010196 [release.debian.org] RM: elog/3.1.3-1-1 (from bullseye) Added tag(s) bullseye. > tags 1010197 + buster Bug #1010197 [release.debian.org] RM: elog/3.1.3-1-1 (from buster) Added tag(s) buster. > thanks Stopping p

Bug#1009726: bullseye-pu: package samba/2:4.13.13+dfsg-1+deb11u4

Hi, On Fri, Apr 15, 2022 at 05:12:38PM +0300, Michael Tokarev wrote: > * switch from weird ~deb11uN to the usual +deb11uN release numbering scheme > since a more recent upstream version is available in testing now > > It is not really a change per se, just an indication that the versioning

Bug#1008823: transition: thrift

Hi On 2022-04-19 14:12:33, Sebastian Ramacher wrote: > Control: tags -1 confirmed > Control: forwarded -1 > https://release.debian.org/transitions/html/auto-thrift.html > > On 2022-04-02 11:48:40, László Böszörményi wrote: > > Package: release.debian.org > > Severity: normal > > User: release.de

Bug#1010203: bullseye-pu: package bind9/1:9.16.28-1~deb11u1

Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 [ Reason ] New upstream version update, the upstream CHANGES are: --- 9.16.28 released --- 5856. [bug] The "

Bug#1009726: bullseye-pu: package samba/2:4.13.13+dfsg-1+deb11u4

26.04.2022 10:37, Salvatore Bonaccorso wrote: Hi, On Fri, Apr 15, 2022 at 05:12:38PM +0300, Michael Tokarev wrote: * switch from weird ~deb11uN to the usual +deb11uN release numbering scheme since a more recent upstream version is available in testing now It is not really a change per

Bug#1009726: bullseye-pu: package samba/2:4.13.13+dfsg-1+deb11u4

So, is there anything else needed on my side to help this? I can re-send the debdiff (the change against the previous one was the removal of closing of #1002059 from d/changelog which slipped there by mistake, and going from -1+deb11u4 to -1~deb11u4 per carnil@ suggestion. Thanks, /mjt

Processed: retitle 1009726 to bullseye-pu: package samba/2:4.13.13+dfsg-1~deb11u4

Processing commands for cont...@bugs.debian.org: > retitle 1009726 bullseye-pu: package samba/2:4.13.13+dfsg-1~deb11u4 Bug #1009726 [release.debian.org] bullseye-pu: package samba/2:4.13.13+dfsg-1+deb11u4 Changed Bug title to 'bullseye-pu: package samba/2:4.13.13+dfsg-1~deb11u4' from 'bullseye-p

Bug#1010211: bullseye-pu: package grunt/1.3.0-1+deb11u1

Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu [ Reason ] grunt is vulnerable to path traversal [ Impact ] Medium security issue [ Tests ] Test passed, including new test [ Risks ] low risk, patch is trivial [ Checklist ]

Bug#1009726: broken build of samba_4.13.13+dfsg-1~deb11u3 on i386

Hi On Sat, Apr 23, 2022 at 10:55:28AM +0300, Michael Tokarev wrote: > Hello! > > It turned out the security-uploaded build of samba on i386 is broken. > There were several reports about smbd segfaulting at startup or other > weirdness. This is specific to i386 build, the x64 build is fine (and >

Bug#1009865: marked as done (transition: octave)

Your message dated Tue, 26 Apr 2022 22:43:47 +0200 with message-id and subject line Re: Bug#1009865: transition: octave has caused the Debian Bug report #1009865, regarding transition: octave to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Re: security updates of Golang packages

Hi Paul, On Tue, 26 Apr 2022, Paul Gevers wrote: But if you have the tooling to create such versioned dependencies (and you'd need those to get everything right), than we could use the same tools to add Depwait on the binNMUs and the build order would be correct again. hmm, Depwaits are new t