Hi,
A) I can do both with my server, but I don't package a lot.
B) I agree with Andy here it should be automated.
When the automatic setup is realized, we should definitly consider to
support more architectures,
like aarch64 for the new showing up arm servers and Apple Macs.
greetings
tpowa
Am S
On 30/01/2022 12:59, Kristian Klausen via arch-dev-public wrote:
On 30.01.2022 12.08, Morten Linderud via arch-dev-public wrote:
I'm very happy to announce that debug packages in Arch Linux has been
deployed :)
This work began after FOSDEM 2020 and was announced in November 2020.
However
beca
Hi all,
given recent topics for build automation and work on internal projects I
would like to announce a code walkthrough for arch-repo-management [1].
I would like to give an overview of the scope of the project, its
current features and which features I would like to see implemented
(some of w
On 31/1/22 23:23, David Runge via arch-dev-public wrote:
Hi all,
given recent topics for build automation and work on internal projects I
would like to announce a code walkthrough for arch-repo-management [1].
I would like to give an overview of the scope of the project, its
current features an
On 2022-01-31 14:23:10 (+0100), David Runge via arch-dev-public wrote:
> The meeting will take place on Jitsi
> https://meet.jit.si/20220202-arch-repo-management
>
> on 2022-02-02 starting around 19:00 CET (UTC+01:00).
>
> Any changes to the date and/or location will be announced in this mail
> t
On Mon, Jan 31, 2022 at 11:55:07PM +1000, Allan McRae via arch-dev-public wrote:
> On 31/1/22 23:23, David Runge via arch-dev-public wrote:
> > Hi all,
> >
> > given recent topics for build automation and work on internal projects I
> > would like to announce a code walkthrough for arch-repo-manag
On 2022-01-31 23:55:07 (+1000), Allan McRae via arch-dev-public wrote:
> Any chance this can be recorded? It will be at 4am in my timezone?
I think that can certainly be arranged!
> I am interested in mainly what problem this is solving. From what I
> can tell, our current workflow is package->
On 1/2/22 00:36, David Runge wrote:
When looking at svn vs. git approaches the fundamental difference is,
that with svn we track both the package sources *and* their "location"
state in the repositories while repo-add/repo-remove is used to
add/remove things on the fly to the package repository
On Mon, Jan 31, 2022 at 10:20:35AM +0100, Jelle van der Waa via arch-dev-public
wrote:
> On 30/01/2022 12:59, Kristian Klausen via arch-dev-public wrote:
> >
> > We have three sponsored machines, which are used as package mirrors and
> > archive mirrors[1].
> > At the time of writing they have 14T
We’ve wanted automatic flagging packages out of date for a while and
currently every packager has to come up with it’s own solution. Let’s
solve this centralized by integrating nvchecker into archweb.
nvchecker is a program which can monitor versions upstreams, github,
pypi, haskell, crates.io
On 2022-01-31 23:55, Allan McRae via arch-dev-public wrote:
On 31/1/22 23:23, David Runge via arch-dev-public wrote:
Hi all,
given recent topics for build automation and work on internal projects I
would like to announce a code walkthrough for arch-repo-management [1].
I would like to give an
On 22-01-31 21:25, Jelle van der Waa via arch-dev-public wrote:
> We’ve wanted automatic flagging packages out of date for a while and
> currently every packager has to come up with it’s own solution. Let’s solve
> this centralized by integrating nvchecker into archweb.
>
> nvchecker is a program w
On Tue, Feb 01, 2022 at 03:55:44AM +, George Rawlinson via arch-dev-public
wrote:
>
> I have no objections to this, and happily support this endeavour.
>
> However, I currently track 8 packages via shell scripts (available via
> nvchecker's "cmd" source), all found here[0].
>
> Some of them
13 matches
Mail list logo
