On Sat, Jan 29, 2022 at 11:45:57AM +1000, Allan McRae via arch-dev-public wrote:
> On 29/1/22 11:28, Morten Linderud via arch-dev-public wrote:
> > On Sat, Jan 29, 2022 at 11:22:32AM +1000, Allan McRae via arch-dev-public
> > wrote:
> > > On 29/1/22 11:13, Morten Linderud via arch-dev-public wrote
On 29/1/22 22:11, Morten Linderud via arch-dev-public wrote:
On Sat, Jan 29, 2022 at 11:45:57AM +1000, Allan McRae via arch-dev-public wrote:
On 29/1/22 11:28, Morten Linderud via arch-dev-public wrote:
On Sat, Jan 29, 2022 at 11:22:32AM +1000, Allan McRae via arch-dev-public wrote:
On 29/1/22
On Sat, Jan 29, 2022 at 10:53:41PM +1000, Allan McRae via arch-dev-public wrote:
> On 29/1/22 22:11, Morten Linderud via arch-dev-public wrote:
> > On Sat, Jan 29, 2022 at 11:45:57AM +1000, Allan McRae via arch-dev-public
> > wrote:
> > > On 29/1/22 11:28, Morten Linderud via arch-dev-public wrote
On 29/1/22 23:02, Morten Linderud wrote:
On Sat, Jan 29, 2022 at 10:53:41PM +1000, Allan McRae via arch-dev-public wrote:
Exactly the same as it did in the i686/x86_64 days. Some packagers will
upload both variants, some will not. There was a webpage that showed the
package differences between
On Sat, Jan 29, 2022 at 2:49 PM Allan McRae via arch-dev-public
wrote:
> Assuming we need people to help the x86_64_v3 port, I would post a news
> item and have people apply. We have advertised developer positions in
> the past and received dozens of applications, and readily filled the
> availab
Shouldn't we rather recruit people to help with build automation, git
migration and the other topics that keep biting us whenever we try adopting
new stuff in a timely manner and/or with less manual stuff to do?
I fully agree with Morten on this one and we should definitely get our
infra and build
Hi all
The lack of package database signing was mentioned yet again and I think
it is time to get the "Signing enclave" project rolling.
A design was sketched two years ago[1], and based on that design I'm
proposing a new design, without a HSM, which should be implementable today.
The initi
On 2022-01-29 15:16, Pierre Schmitz via arch-dev-public wrote:
On Sat, Jan 29, 2022 at 2:49 PM Allan McRae via arch-dev-public
wrote:
Assuming we need people to help the x86_64_v3 port, I would post a news
item and have people apply. We have advertised developer positions in
the past and recei
On Sat, Jan 29, 2022 at 06:22:29PM +0100, Kristian Klausen via arch-dev-public
wrote:
> Signing:
> - SSHing to a restricted UNIX user with ForceCommand=signing-script
> - All signing operations are logged
> - Only signing requests from gemini's WireGuard IP address is allowed
Some general thought
On Sat, Jan 29, 2022 at 09:35:07AM -0800, Brett Cornwall via arch-dev-public
wrote:
> On 2022-01-29 15:16, Pierre Schmitz via arch-dev-public wrote:
> > On Sat, Jan 29, 2022 at 2:49 PM Allan McRae via arch-dev-public
> > wrote:
> > > Assuming we need people to help the x86_64_v3 port, I would pos
On 2022-01-29 13:11:05 (+0100), Morten Linderud via arch-dev-public wrote:
> * Signing enclave
> * Better rebuilding tools
> * Build automation
> * Git migration
>
> It would make discussions like these completely obsolete. Do we want
> v2, v3, v4, v5, v90001? Enable it in a setting and we'd have
On Sat, 29 Jan 2022 at 15:17, Pierre Schmitz via arch-dev-public <
arch-dev-public@lists.archlinux.org> wrote:
> On Sat, Jan 29, 2022 at 2:49 PM Allan McRae via arch-dev-public
> wrote:
> > Assuming we need people to help the x86_64_v3 port, I would post a news
> > item and have people apply. We
On 30/1/22 03:22, Kristian Klausen via arch-dev-public wrote:
Hi all
The lack of package database signing was mentioned yet again and I think
it is time to get the "Signing enclave" project rolling.
A design was sketched two years ago[1], and based on that design I'm
proposing a new design,
13 matches
Mail list logo
