On 2/18/23 15:36, Jelle van der Waa wrote:
On 02/02/2023 01:45, Morten Linderud wrote:
Hi everyone!
Levente and I have been busy preparing a test environment for the new git package workflow, which is going to replace the svn repository.
To test the new git package setup install `devtools-git-poc` from the [community] repository and use the new `pkgctl` utility. Please check each time if there is a new upgrade before playing around.
The goal of the testing is to figure out UX issues, bugs and larger issues that would need to be dealt with before a git migration can happen. It's therefor very important that people sit down and play around with the tools :)
While working on the archweb side of things I noticed that we now have extra, extra-testing, extra-staging. Is this change intentional?
This would require some manual intervention as the default is to use testing/staging. On the PoC there is some curious difference between testing and extra-testing
https://repos.sandbox.archlinux.org/extra-testing/os/x86_64/ https://repos.sandbox.archlinux.org/testing/os/x86_64/
Many tools/integrations probably depend on testing, so this surely will break.
Greetings,
Jelle
Hi there, Yes, we were required to change things in dbscripts and devtools anyway. Considering that all secondary tooling needs adjustments to reflect the [core-testing] layout, we have decided to just go simple and remove special casing any stability layers. It was best to break secondary tooling once (which was the case either way), instead of multiple times. So now we ended with a simple and easy to code stability layer layout without special cases: ${repo} ${repo}-staging ${repo}-testing Sincerely, Levente