Re: source-only uploads for future point releases (Re: Bug#980962: buster-pu: package intel-microcode/3.20201118.1~deb10u1)
On Sat, 30 Jan 2021, Holger Levsen wrote: > On Fri, Jan 29, 2021 at 04:32:27PM -0300, Henrique de Moraes Holschuh wrote: > > > Please feel free to upload, bearing in mind that the window for 10.8 > > > closes during this weekend. > > Uploaded (source, i386, amd64). > > one can do source only uploads to stable(-security) and oldstable() too. Well, I tried that for *non-free* stretch-security. It didn't work. I don't think I forgot anything: "XS-Autobuild: true" has been in intel-microcode's control file since basically forever, and it does work properly in non-free unstable. Can someone please take a look? Alternatively, I will just upload the binaries to jessie-security. -- Henrique Holschuh
Re: Please allow pdns/4.4.1-1 into bullseye
Hi Paul, * Paul Gevers [210208 21:13]: > On 08-02-2021 09:32, Chris Hofstaedtler wrote: > > I've uploaded that yesterday, and that was "just too late"? > > What makes you think so? [..] > Required age reduced by 3 days because of autopkgtest > Not considered > > I don't see anything blocking it's migration tomorrow. As KiBi pointed out to me off-list, autopkgtest grants the 3 days age reduction. I was confused because earlier today the tests haven't passed yet, and then it just shows "5 days needed". So... sorry for the noise and thanks for checking! Best, Chris
Re: Please allow pdns/4.4.1-1 into bullseye
Hi Chris, On 08-02-2021 09:32, Chris Hofstaedtler wrote: > I've uploaded that yesterday, and that was "just too late"? What makes you think so? Migration status for pdns (4.4.0-3 to 4.4.1-1): Waiting for test results, another package or too young (no action required now - check later) Issues preventing migration: Too young, only 1 of 2 days old Additional info: Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdns.html Required age reduced by 3 days because of autopkgtest Not considered I don't see anything blocking it's migration tomorrow. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#982252: marked as done (nmu: rebuild on buildd after NEW)
Your message dated Mon, 8 Feb 2021 19:24:50 +0100 with message-id and subject line Re: Bug#982252: nmu: rebuild on buildd after NEW has caused the Debian Bug report #982252, regarding nmu: rebuild on buildd after NEW 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.) -- 982252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982252 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 nmu atitvout_0.4-13.1 . i386 . unstable . -m "rebuild on buildd" nmu gkrellmoon_0.6-6 . amd64 . unstable . -m "rebuild on buildd" nmu xserver-xorg-input-aiptek_to 1:1.4.1-3 . amd64 . unstable . -m "rebuild on buildd" nmu xserver-xorg-input-elographics_1:1.4.1-2 . amd64 . unstable . -m "rebuild on buildd" nmu xserver-xorg-input-mutouch_1:1.3.0-2 . amd64 . unstable . -m "rebuild on buildd" nmu xserver-xorg-video-mach64_6.9.6-2 . amd64 . unstable . -m "rebuild on buildd" nmu xserver-xorg-video-neomagic_1:1.3.0-2 . amd64 . unstable . -m "rebuild on buildd" nmu xserver-xorg-video-r128_6.12.0-2 . amd64 . unstable . -m "rebuild on buildd" nmu xserver-xorg-video-savage_1:2.3.9-3 . amd64 . unstable . -m "rebuild on buildd" nmu xserver-xorg-video-siliconmotion_1:1.7.9-3 . amd64 . unstable . -m "rebuild on buildd" nmu xserver-xorg-video-sisusb_1:0.9.7-2 . amd64 . unstable . -m "rebuild on buildd" nmu xserver-xorg-video-tdfx_1:1.5.0-3 . amd64 . unstable . -m "rebuild on buildd" nmu xserver-xorg-video-trident_1:1.3.8-2 . amd64 . unstable . -m "rebuild on buildd" # Multi-Arch: same nmu secsipidx_1.1.0-1 . ANY . unstable . -m "rebuild on buildd" # thanks --- End Message --- --- Begin Message --- On 2021-02-07 19:36:09 +0200, Adrian Bunk wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > nmu atitvout_0.4-13.1 . i386 . unstable . -m "rebuild on buildd" > nmu gkrellmoon_0.6-6 . amd64 . unstable . -m "rebuild on buildd" > nmu xserver-xorg-input-aiptek_to 1:1.4.1-3 . amd64 . unstable . -m "rebuild > on buildd" > nmu xserver-xorg-input-elographics_1:1.4.1-2 . amd64 . unstable . -m "rebuild > on buildd" > nmu xserver-xorg-input-mutouch_1:1.3.0-2 . amd64 . unstable . -m "rebuild on > buildd" > nmu xserver-xorg-video-mach64_6.9.6-2 . amd64 . unstable . -m "rebuild on > buildd" > nmu xserver-xorg-video-neomagic_1:1.3.0-2 . amd64 . unstable . -m "rebuild on > buildd" > nmu xserver-xorg-video-r128_6.12.0-2 . amd64 . unstable . -m "rebuild on > buildd" > nmu xserver-xorg-video-savage_1:2.3.9-3 . amd64 . unstable . -m "rebuild on > buildd" > nmu xserver-xorg-video-siliconmotion_1:1.7.9-3 . amd64 . unstable . -m > "rebuild on buildd" > nmu xserver-xorg-video-sisusb_1:0.9.7-2 . amd64 . unstable . -m "rebuild on > buildd" > nmu xserver-xorg-video-tdfx_1:1.5.0-3 . amd64 . unstable . -m "rebuild on > buildd" > nmu xserver-xorg-video-trident_1:1.3.8-2 . amd64 . unstable . -m "rebuild on > buildd" > > # Multi-Arch: same > nmu secsipidx_1.1.0-1 . ANY . unstable . -m "rebuild on buildd" Scheduled Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message ---
Bug#982311: buster-pu: package groff/1.22.4-3+deb10u1
Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu https://bugs.debian.org/982302 reports that groff/buster is built with references to ghostscript 9.26, despite 9.27 having been uploaded to buster in August 2020. I think the path of least resistance/risk would be to do a simple rebuild of groff against the new version. Would that be OK? diff -Nru groff-1.22.4/debian/changelog groff-1.22.4/debian/changelog --- groff-1.22.4/debian/changelog 2019-02-28 19:44:28.0 + +++ groff-1.22.4/debian/changelog 2021-02-08 15:55:48.0 + @@ -1,3 +1,9 @@ +groff (1.22.4-3+deb10u1) UNRELEASED; urgency=medium + + * Rebuild against ghostscript 9.27 (closes: #982302). + + -- Colin Watson Mon, 08 Feb 2021 15:55:48 + + groff (1.22.4-3) unstable; urgency=medium * Avoid Perl's unsafe "<>" operator (closes: #920269). Thanks, -- Colin Watson (he/him) [cjwat...@debian.org] signature.asc Description: PGP signature
firmware-nonfree 20210208-1 upload
Hello everyone, Just quick notice that newest upstream will be uploaded tomorrow to sid. It has relevant updates for Intel bluetooth && realtek. I plan to ask for a freeze exception to have the corresponding firmwares for current linux. best, -- maks signature.asc Description: PGP signature
Please allow pdns/4.4.1-1 into bullseye
Dear Release Team, I must have misunderstood the exact timing requirements for bullseye. However I persuaded upstream to maka a point release "for us", so I'd be great if pdns 4.4.1-1 could actually make it into bullseye. I've uploaded that yesterday, and that was "just too late"? Thanks, Chris
