Re: Porter roll call for Debian Bullseye

Vagrant Cascadian <[email protected]> Mon, 30 Nov 2020 17:07:26 -0800

Newsgroups	gmane.linux.debian.ports.bsd
Message-ID	<87v9dmmj01.fsf__12144.2151068308$1606785439$gmane$org@yucca>

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 <[email protected]> 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 (application/pgp-signature, 227 B)