Re: Porter roll call for Debian Bookworm
Hi, I am an active porter for the following architecture and I intend to continue for the development cycle of Debian Bookworm (est. release mid-2023): For ppc64el, I - test most packages on this architecture - run a Debian testing or unstable system that I use regularly - fix ppc64el-related bugs, especially by following https://udd.debian.org/cgi-bin/ftbfs.cgi - test d-i on a daily basis with OpenQA (sid netboot/testing netinst/bookworm alphas) installer (vm and PowerVM on P8, P9, P10) - fix d-i bugs/issues I am a DD Frédéric Bonnard On Sat, 02 Oct 2021 11:57:07 +0200 Graham Inggs wrote: > Hi > > We are doing a roll call for porters of all prospective release > architectures. If you are an active porter behind one of these > architectures [1] and intend to continue for the development cycle of > Debian Bookworm (est. release mid-2023), please respond with a signed > email containing the following before Saturday, January 1, 2022: > > * Which architectures are you committing to be an active porter for? > * Please describe recent relevant porter contributions. > * Are you running/using Debian testing or sid on said port(s)? > * Are you testing/patching d-i for the port(s)? > > Please note that no response is required for amd64 because our > toolchain maintainers are happy to support amd64 as-is. > > Feel free to use the following template as your reply: > > """ > Hi, > > I am an active porter for the following architectures and I intend to > continue for the development cycle of Debian Bookworm > (est. release mid-2023): > > For , I > [delete/modify as appropriate] > - test (most|all) packages on this architecture > - run a Debian testing or unstable system on port that I use regularly > - fix toolchain issues > - triage arch-specific bugs > - fix arch-related bugs > - triage d-i bugs > - test d-i regularly > - fix d-i bugs/issues > - maintain buildds > - maintain/provide hardware for (or assist with) automated tests on ci.d.n, > jenkins.d.n (etc.) > - run other automated tests outside the Debian QA services (Please describe > these) > - ... > > > > > """ > > Graham, on behalf of the release team > > > [1] https://release.debian.org/bookworm/arch_qualify.html > signature.asc Description: PGP signature
Bug#996094: marked as done (transition: libgphobos)
Your message dated Thu, 14 Oct 2021 13:01:13 +0200 with message-id and subject line Re: Bug#996094: transition: libgphobos has caused the Debian Bug report #996094, regarding transition: libgphobos 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.) -- 996094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996094 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: transition please binNMU packages for the (non-blocking) libgphobos transition, triggered by the GCC defaults change (dub and cheesecutter are ftbfs, bug reports are already filed): Reverse Depends: Depends: val-and-rick (>= 10.1) Depends: tumiki-fighters (>= 10.1) Depends: torus-trooper (>= 10.1) Depends: titanion (>= 10.1) Depends: tatan (>= 10.1) Depends: projectl (>= 10.1) Depends: parsec47 (>= 10.1) Depends: mu-cade (>= 10.1) Depends: ii-esu (>= 10.1) Depends: gunroar (>= 10.1) Depends: a7xpg (>= 10.1) Depends: dustmite (>= 10.1) Depends: dub (>= 10.1) Depends: cheesecutter (>= 10.1) --- End Message --- --- Begin Message --- On Mon, 11 Oct 2021 at 08:18, Matthias Klose wrote: > please binNMU packages for the (non-blocking) libgphobos transition, triggered > by the GCC defaults change (dub and cheesecutter are ftbfs, bug reports are > already filed): > > Reverse Depends: > Depends: val-and-rick (>= 10.1) > Depends: tumiki-fighters (>= 10.1) > Depends: torus-trooper (>= 10.1) > Depends: titanion (>= 10.1) > Depends: tatan (>= 10.1) > Depends: projectl (>= 10.1) > Depends: parsec47 (>= 10.1) > Depends: mu-cade (>= 10.1) > Depends: ii-esu (>= 10.1) > Depends: gunroar (>= 10.1) > Depends: a7xpg (>= 10.1) > Depends: dustmite (>= 10.1) Scheduled, thanks.--- End Message ---
Re: Debian 11 images for AWS m6i instances
Hi Giambattista, On Thu, Oct 14, 2021 at 10:32:50AM +0100, Giambattista Piranesi wrote: >I've noticed there are no official Debian 11 (Bullseye) images on AWS >compatible with m6i instances. > >Any chance to generate a m6-ready Debian 11 AMI? What does it depend? The best place to ask about this is the debian-cloud list (in CC). -- Steve McIntyre, Cambridge, UK.st...@einval.com "When C++ is your hammer, everything looks like a thumb." -- Steven M. Haflich
Debian 11 images for AWS m6i instances
I've noticed there are no official Debian 11 (Bullseye) images on AWS compatible with m6i instances. Any chance to generate a m6-ready Debian 11 AMI? What does it depend?
