Re: Porter roll call for Debian Bookworm
On 2021-10-02 11:57 +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: Oops, too slow! > * Which architectures are you committing to be an active porter for? arm64, amrhf, armel > * Please describe recent relevant porter contributions. Manage the arm buildds at ARM. Worked on packaging AI/ML stuff Worked with rust team on unbunging Help with give-backs Look at build issues brought to the attention of the debian-arm list > * Are you running/using Debian testing or sid on said port(s)? Largely only for building. I tend to run stable on boxes doing real work but switch to testing for half a release on development machines. I've never been a 'run sid on real machines' sort of person. > * Are you testing/patching d-i for the port(s)? Yes. I have a pretty good understanding of how it works, and sometimes test/fix things on new (to me) hardware, or when people ask about specific things. > 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 - test (most|all) packages on this architecture I have an arm64 desktop running stable and arm64/armhf/armel build machines I run an armhf home server (cubietruck) and an armel (Balloon) home controller I have various test hardware boards/machines > - run a Debian testing or unstable system on port that I use regularly - fix toolchain issues - triage arch-specific bugs (recent example is spurious neon instructions in init code: 982794, 998043, - fix arch-related bugs - test d-i sometimes - fix d-i bugs/issues - maintain buildds (@ARM Cambridge site - reboots, network moves, new hard-drives + fans, justifying functionality that we need to ARM corporate security who like to turn things off, assuring them that we have already (usually) dealt with this week's security scare) I plan to do an armhf-64-bit-timet rebuild soon, to provide info on breakage and help plan that transition I will probably be retiring from paid debian work at ARM within a year or so. Which probably means handing the buildd admin off to someone as it'll make access a lot easier. That won't change my debian-arm focus much, but it will probably change it a bit (away from AI, towards core arch activities and my personal packages). I'm not sure how much of my current test hardware I'll get to keep... I am a DD (since 2000) Wookey Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ signature.asc Description: PGP signature
Re: Porter roll call for Debian Bookworm
Sandro Tosi 于2022年1月14日周五 13:54写道： > > YunQiang, > > On Tue, Jan 4, 2022 at 9:48 AM PICCA Frederic-emmanuel > wrote: > > > > > > > > In case #1000435 (matplotlib crashes on mips64el) is not already on > > > > your radar, would you please take a look? > > > > > > > > > > Thank you. I will work on it right now. > > > > Hello, I just added some information about this problem on this bug > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001168#72 > > > > it seems to me that this is something related to gcc-11. If I build > > matplotlib with gcc-10 there is no more crash. > > did you have a chance to look at it yet? there's quite a substantial > number of packages depending on matplotlib that cant migrate to OK. I will have a look at this now. > testing until this issue is fixed, so we'd greatly appreciate it if > you can investigate it soon. > > Thanks, > -- > Sandro "morph" Tosi > My website: http://sandrotosi.me/ > Me at Debian: http://wiki.debian.org/SandroTosi > Twitter: https://twitter.com/sandrotosi -- YunQiang Su
Re: Porter roll call for Debian Bookworm
YunQiang, On Tue, Jan 4, 2022 at 9:48 AM PICCA Frederic-emmanuel wrote: > > > > > In case #1000435 (matplotlib crashes on mips64el) is not already on > > > your radar, would you please take a look? > > > > > > > Thank you. I will work on it right now. > > Hello, I just added some information about this problem on this bug > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001168#72 > > it seems to me that this is something related to gcc-11. If I build > matplotlib with gcc-10 there is no more crash. did you have a chance to look at it yet? there's quite a substantial number of packages depending on matplotlib that cant migrate to testing until this issue is fixed, so we'd greatly appreciate it if you can investigate it soon. Thanks, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Re: Porter roll call for Debian Bookworm
> > In case #1000435 (matplotlib crashes on mips64el) is not already on > > your radar, would you please take a look? > > > > Thank you. I will work on it right now. Hello, I just added some information about this problem on this bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001168#72 it seems to me that this is something related to gcc-11. If I build matplotlib with gcc-10 there is no more crash. I think that I reach my peter principe with this last effort :)) Cheers Frederic
Re: Porter roll call for Debian Bookworm
Hello, 2021-10-02 11:57 Graham Inggs: 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: [...] I have been working on the riscv64 port since 2015 or so, even if the successful and definitive initial bootstrap only happened in 2018. Some people joined from the start and more people joined lately, but I have a keen interest in pushing this port further :) Thus, I am an active porter for riscv64 and I intend to continue for the development cycle of Debian Bookworm (est. release mid-2023). In the last year or two the contributions were a bit diminished for a variety of issues (especially in the realm of attending bugs and looking at specific issues of packages and submitting patches), and will continue to be this way for a while, but I hope to pick-up pace again during this development cycle. For riscv64, I plan to: - maintain buildds --- I have set-up or was involved in getting hardware and necessary resources and setting up most of the buildds of the architecture so far, and I plan to continue doing this in the foreseeable future - maintain/provide hardware for (or assist with) automated tests on ci.d.n, jenkins.d.n (etc.) --- I though about doing do this in the past, I think that it's a good idea to do this if new suitable hardware becomes available, but there's been scarcity until now. - run a Debian testing or unstable system on port that I use regularly - test (most|all) packages on this architecture --- not sure if saying (most|all) is realistic with the current size of the archive, but I hope to use regularly the most important packages by using them on real systems. The following I will try to do as more time becomes available, and paying more attention if this port is considered to be supported for bookworm and becoming a more official architecture (but other people with interest in riscv64 are also working on these areas): - fix toolchain issues - triage arch-specific bugs - fix arch-related bugs - triage d-i bugs - test d-i regularly - fix d-i bugs/issues I am a DD. -- Manuel A. Fernandez Montecelo signature.asc Description: PGP signature
Re: Porter roll call for Debian Bookworm
Graham Inggs 于2021年12月26日周日 21:58写道： > > Hi YunQiang Su > > On Sun, 26 Dec 2021 at 11:17, YunQiang Su wrote: > > > > For mipsel and mips64el, I > > - test most 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.) > > > > I am a DD. > > Thanks for your response! > > In case #1000435 (matplotlib crashes on mips64el) is not already on > your radar, would you please take a look? > Thank you. I will work on it right now. > Regards > Graham -- YunQiang Su
Re: Porter roll call for Debian Bookworm
Hi YunQiang Su On Sun, 26 Dec 2021 at 11:17, YunQiang Su wrote: > > For mipsel and mips64el, I > - test most 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.) > > I am a DD. Thanks for your response! In case #1000435 (matplotlib crashes on mips64el) is not already on your radar, would you please take a look? Regards Graham
Re: Porter roll call for Debian Bookworm
For mipsel and mips64el, I - test most 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.) I am a DD. -- YunQiang Su
Re: Porter roll call for Debian Bookworm
Hi A friendly reminder about the porter roll call for bookworm. On Sat, 2 Oct 2021 at 11:57, Graham Inggs wrote: > 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: Please note we don't automatically assume that porters for previous releases will continue to do so. If you were a porter for a previous release, we'd like you to sign up again for bookworm. Please refer to the architecture requalification page [1] for the current status. Graham, on behalf of the release team [1] https://release.debian.org/bookworm/arch_qualify.html
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
Porter roll call for Debian Bookworm
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
