On 3/2/22 03:42, Leonidas Spyropoulos via arch-dev-public wrote:
On 02/02/2022 17:32, Evangelos Foutras via arch-dev-public wrote:
I'm not fond of the hidden all-caps filename for editable sources
(whereas it's fine for .BUILDINFO and friends). More importantly
though, has integration with [1] b
On 2/1/22 22:54, George Rawlinson via arch-dev-public wrote:
On 22-02-01 08:21, Morten Linderud via arch-dev-public wrote:
At this stage, the following [community] packages that I maintain
require massaging of HTML sources:
* html-xml-utils
* oil
* parallel
* libmilter (bundled with sendmail sou
On 2/2/22 19:59, Anatol Pomozov via arch-dev-public wrote:
And here is one more tool to check if package version is of out-of-date
https://github.com/anatol/pkgoutofdate
It is a pretty simple tool that does not require any modification to Arch
repo. It simply tries to guess what is the next poss
Hi
On Wed, Feb 2, 2022 at 9:32 AM Evangelos Foutras via arch-dev-public <
arch-dev-public@lists.archlinux.org> wrote:
> On Mon, 31 Jan 2022 at 22:27, Jelle van der Waa via arch-dev-public
> wrote:
> >
> > The question is if anyone object to checking these small .NVCHECKER
> > files into our svn
On 02/02/2022 17:32, Evangelos Foutras via arch-dev-public wrote:
I'm not fond of the hidden all-caps filename for editable sources
(whereas it's fine for .BUILDINFO and friends). More importantly
though, has integration with [1] been considered? The best way to
implement automatic version checki
On 2/2/22 18:32, Evangelos Foutras via arch-dev-public wrote:
On Mon, 31 Jan 2022 at 22:27, Jelle van der Waa via arch-dev-public
wrote:
The question is if anyone object to checking these small .NVCHECKER
files into our svn repository. If there are no real objections, I'll
start implementing t
On Mon, 31 Jan 2022 at 22:27, Jelle van der Waa via arch-dev-public
wrote:
>
> The question is if anyone object to checking these small .NVCHECKER
> files into our svn repository. If there are no real objections, I'll
> start implementing this functionality into archweb in two weeks.
I'm not fond
On 01/02/2022 21:54, George Rawlinson via arch-dev-public wrote:
On 22-02-01 08:21, Morten Linderud via arch-dev-public wrote:
These require running arbitrary scripts on archweb so they should probably
remain
unsupported. Is there no better options?
At this stage, the following [community] pa
Hi,
This is an updated news entry for the debug package announcement. We have been
working on the system and provided a few repositories for the debug repositories
as well.
I'll post this when we have an updated "Getting traces" article ready :)
# Debug packages and debuginfod
We are very happy
On 2022-02-02 12:40:56 (+0100), Morten Linderud via arch-dev-public wrote:
> # Signed SHIM
>
> First of we need to have a signing solution for this. My idea has been to
> piggy-back on the existing work on the signing-enclave. However it's current
> focus is GnuPG and I need something which can su
On Wed, Feb 02, 2022 at 12:20:19PM +0100, Tobias Powalowski via arch-dev-public
wrote:
> Hi guys,
> next topic to step up: Secure Boot support
> I wanted to bring this up to the mailing list to collect all info about the
> status of SB support.
> There are different approaches on how to implement
Hi guys,
next topic to step up: Secure Boot support
I wanted to bring this up to the mailing list to collect all info about the
status of SB support.
There are different approaches on how to implement SB.
My question first: Do we want a signed shim for Arch Linux?
If yes, how to achieve this? We sh
12 matches
Mail list logo
