Hey,
On 10/01/2023 16:05, David Runge wrote:
On 2023-01-08 12:13:36 (+0100), Jelle van der Waa wrote:
On 05/01/2023 23:15, Levente Polyak wrote:
# Introduction
[1] https://github.com/archlinux/archweb/issues/438
@jelle Maybe I misunderstand your last paragraph, but isn't this the
case currently already? I think dbscripts will prevent you from updating
the stable repository (e.g. extra), if any of the other stability layers
(staging or testing) would then have the package in a version lower than
the one you're trying to add.
It is always staging > testing > stable.
On IRC we have been writing a bit about how to make links to the
package sources on our GitLab available in archweb (we need to implement
the translation of version string to git tag string).
As repod will need similar functionality for source verification
purposes in the future, I sketched out the functionality in a small lib
here:
https://gitlab.archlinux.org/dvzrv/archlinux-version-tag-conversion/
Admittedly, it is not a lot of code and we could also consider having it
in each application directly, but maybe we'll find more functionality
for a shared library, that could go there.
The main takeaway of my question is that it's unclear how
gnome-unstable/kde-unstable are used in svn today to me and how this
would work in our Git packaging repository.
