Re: Porter roll call for Debian Bookworm
On 2021-10-02, Graham Inggs wrote: > * Which architectures are you committing to be an active porter for? armhf, arm64 > * Please describe recent relevant porter contributions. Maintaining u-boot (bootloader used on many arm64 and armhf plaforms), arm-trusted-firmware (arm64 firmware), and occasional debian-installer, linux and initramfs-tools contributions for specific hardware. > 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 armhf and arm64, I: > - test (most|all) packages on this architecture I maintain the armhf build machines for tests.reproducible-builds.org which currently runs package builds for the whole archive in sid, experimental, bookworm and bullseye chroots. The build machines are a mix of arm64 and armhf capable machines. > - run a Debian testing or unstable system on port that I use regularly I run mobian on arm64, which is currently bookworm based, working towards complete inclusion in debian. I may start using an arm64 laptop (pinebook pro) regularly, probably running bookworm. > - triage arch-specific bugs > - fix arch-related bugs > - triage d-i bugs > - test d-i regularly > - fix d-i bugs/issues Not systematically or regularly, but occasionally as the need arises. I am a DD. live well, vagrant signature.asc Description: PGP signature
Re: Porter roll call for Debian Bullseye
On 2020-11-20, Graham Inggs wrote: > A friendly reminder about the porter roll call for bullseye. > > On Mon, 2 Nov 2020 at 22:23, Graham Inggs wrote: >> We are doing a roll call for porters of all release architectures. If >> you are an active porter behind one of the release architectures [1] >> for the entire lifetime of Debian Bullseye (est. end of 2024), please >> respond with a signed email containing the following before Friday, >> November 27: > > 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 bullseye. I know I'm a bit late to the party now... I do run both arm64 and armhf on numerous machines, mostly as part of the reproducible builds zoo. We mostly stick to stable for the main OS, but do run unstable and testing in chroots. I also sometimes run testing or individual packages from unstable on various other armhf and arm64 machines I use and make efforts to report and ideally fix bugs when encountered. I maintain u-boot and arm-trusted-firmware, used primarily on armhf and arm64. I do occasional debian-installer work and linux related work for both arm64 and armhf. I can most likely continue doing the above for the forseeable future. Not likely to fix deeply complicated toolchain issues. If all that qualifies for a porter hat, ok, if not, also ok. :) live well, vagrant signature.asc Description: PGP signature
