Processed: tagging 994193, tagging 994194, tagging 994212, tagging 994214, tagging 994274, tagging 994285 ...
Processing commands for cont...@bugs.debian.org: > tags 994193 + sid bookworm Bug #994193 [src:iptstate] iptstate FTBFS: error: format not a string literal and no format arguments [-Werror=format-security] Added tag(s) sid and bookworm. > tags 994194 + sid bookworm Bug #994194 [src:hexcurse] hexcurse FTBFS: error: format not a string literal and no format arguments [-Werror=format-security] Added tag(s) sid and bookworm. > tags 994212 + sid bookworm Bug #994212 [r-cran-gprofiler] r-cran-gprofiler: Obsolete package, replaced with r-cran-gprofiler2 Added tag(s) sid and bookworm. > tags 994214 + sid bookworm Bug #994214 [src:nomad] nomad FTBFS in unstable Added tag(s) sid and bookworm. > tags 994274 + sid bookworm Bug #994274 [src:syslinux] syslinux: FTBFS with gnu-efi 3.0.13 Added tag(s) bookworm and sid. > tags 994285 + sid bookworm Bug #994285 [src:libseccomp] libseccomp: FTBFS on arm64, armhf, mips64el and mipsel Added tag(s) sid and bookworm. > tags 994424 + sid bookworm Bug #994424 [src:spice-vdagent] spice-vdagent FTBFS: error: ‘g_memdup’ is deprecated: Use 'g_memdup2' instead [-Werror=deprecated-declarations] Added tag(s) bookworm and sid. > tags 994443 + sid bookworm Bug #994443 [src:r-bioc-deseq2] r-bioc-deseq2: autopkgtest regression Added tag(s) sid and bookworm. > tags 994451 + sid bookworm Bug #994451 [golang-github-containers-common] golang-github-containers-common: secomp.json does not include newer syscall used by stable kernel/glibc on arm Added tag(s) bookworm and sid. > tags 994456 + sid bookworm Bug #994456 [src:ruby-stackprof] ruby-stackprof: flaky autopkgtests Added tag(s) bookworm. > tags 994480 + sid bookworm Bug #994480 [ball] ball: FTBFS following glibc change Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 994193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994193 994194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994194 994212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994212 994214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994214 994274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994274 994285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994285 994424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994424 994443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994443 994451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994451 994456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994456 994480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Upcoming stable point release (11.1)`
Hi, The first point release for "bullseye" (11.1) is scheduled for Saturday, October 9th. Processing of new uploads into bullseye- proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming oldstable point release (10.11)
Hi, The next point release for "buster" (10.11) is scheduled for Saturday, October 9th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Re: 11.1 and 10.11 planning]
Forwarding to the lists Andy forgot... - Forwarded message from Andy Simpkins - From: Andy Simpkins To: debian-cd@lists.debian.org Date: Wed, 15 Sep 2021 20:53:41 +0100 Subject: Re: 11.1 and 10.11 planning Message-ID: <717ba215-4bcc-08ab-b087-8f781f15c...@koipond.org.uk> On 14/09/2021 20:14, Steve McIntyre wrote: > On Tue, Sep 14, 2021 at 07:04:11PM +0100, Adam Barratt wrote: > > Hi, > > > > Thanks for the responses everyone. Mark indicated on IRC that he'd be > > happy to be ftpmaster-du-jour on any of the dates. > > > > On Mon, 2021-09-06 at 12:51 +0100, Adam D. Barratt wrote: > > > We've ended up being late with planning 10.11 due to the timing of > > > the bullseye release, and also need to look at getting 11.1 sorted. > > [...] > > > September 18th - not great; means freezing this coming weekend > > > September 25th - not great; I'm away during most of the week > > > beforehand, so will be unlikely to be able to deal with any issues, > > > make sure everything's ready, etc. > > > October 2nd - OK for me > > > > The conclusion seems to be that if we want to have all of the Images > > Team available then we're looking at: > > > > > October 9th - OK for me > > > October 16th - OK for me > > > > Images Team, what was the conclusion in terms of timing for the two > > point releases? Are you happy for the archive side for both to happen > > on the same day, with image testing for buster possibly being delayed, > > or would you prefer to try and separate the whole process? (In which > > case we would need all teams available for multiple dates.) > > I'm happy either way, I think Andy was less sure in the case that we > got him to do both? :-) > given that Steve will be around I am happy for both in one day :-) /Andy - End forwarded message - -- Steve McIntyre, Cambridge, UK.st...@einval.com < Aardvark> I dislike C++ to start with. C++11 just seems to be handing rope-creating factories for users to hang multiple instances of themselves.
