Git migration announcement

Foxboron · 2023-05-16 10:25:47

This Friday morning (2023-05-19) the Git packaging migration will start until Sunday (2023-05-21). The Arch Linux packaging team will not be able to update packages in any of the repositories during this period.

Notification when the migration starts, and when it is completed, will be published on the [arch-dev-public] mailing list.

How does this impact Arch Linux users?
The [testing] repository will be split into [core-testing] and [extra-testing], the [staging] repository will be split into [core-staging] and [extra-staging]. The [community] repository will be merged into [extra] and will therefore be empty after the migration.

All affected repositories will be provided as empty repositories for a transition period after the migration. For regular users, this means that everything works as before.

Note: After the migration is done, users that have the testing repositories enabled need to include the new repositories ([core-testing] and [extra-testing] instead of [testing]) in their pacman.conf before updating their system.

Other changes:

SVN access is discontinued and will dissappear.
The svn2git mirror will no longer be updated.
asp, which relies on the svn2git mirror, will stop working. It is replaced by pkgctl repo clone.

How does this impact Arch Linux tier 1 mirrors?
During the migration rsync and HTTP access will be shut down. We will send an email notification to arch-mirrors once everything has been finished.

How does this impact Arch Linux packagers?
Packagers will not be able to patch and update their packages. The internal Tier 0 mirror is also going to be disabled for the duration of this migration.

kokoko3k · 2023-05-16 10:55:42

Thanks.

All affected repositories will be provided as empty repositories for a transition period after the migration. For regular users, this means that everything works as before.

What if one does not update his system from now till after the transition period?
If I have, say, community/package1, will pacman update it to extra/package1 automagically?

Allan · 2023-05-16 11:14:45

kokoko3k wrote:

If I have, say, community/package1, will pacman update it to extra/package1 automagically?

Pacman has no concept of what repository a package came from. So it will work fine.

Stefan Husmann · 2023-05-16 11:38:43

What about [community-testing]? Will it go to [extra-testing]?

Allan · 2023-05-16 11:56:56

Stefan Husmann wrote:

What about [community-testing]? Will it go to [extra-testing]?

Yes.

Trilby · 2023-05-16 12:04:34

Is there more information about how the scope of these repos is defined and / or who manages them? Specificially, the previous definitions of core, extra, and community no longer hold. What criteria are used to distinguish between the new core and extra? Will TUs now have all the same access as full developers? Or will TUs cease to have any main repo access (and only oversee the AUR)?

V1del · 2023-05-16 12:08:16

Afaik TUs can now push to extra as if it was community (so there's no extra restriction on "extra" anymore) and core still locked to developers. Which is also one of the reasons why the forum title of Trusted User switched to Package Maintainer.

Last edited by V1del (2023-05-16 12:09:01)

Allan · 2023-05-16 12:13:10

Details:
https://gitlab.archlinux.org/archlinux/ … -repos.rst

And the discussion during development of that RFC:
https://gitlab.archlinux.org/archlinux/ … equests/14

ewaller · 2023-05-16 14:57:42

Sticking topic until after the migration.

icar · 2023-05-16 15:51:13

Will this have any implication for the users of the devtools package? Specifically the build scripts.

Last edited by icar (2023-05-16 15:51:35)

d.ALT · 2023-05-19 06:12:46

Foxboron wrote:

The [community] repository will be merged into [extra] and will therefore be empty after the migration.
[...]
For regular users, this means that everything works as before.

Sorry guys, I don't understand. I was thinking that this merge would imply removing [community] declaration from pacman.conf. What am I missing?

johnzeuler · 2023-05-19 07:44:28

Is this and the new pkgctl a step towards an automatic build farm?
Any timeline on that?

moson · 2023-05-19 07:58:55

d.ALT wrote:

Sorry guys, I don't understand. I was thinking that this merge would imply removing [community] declaration from pacman.conf. What am I missing?

Afaik, the (empty) community repo stays there for a while to give users the chance to adopt their config and remove [community] from it.
Then after some time I'd expect that [community] is being removed completely.

Last edited by moson (2023-05-19 08:01:09)

Fuxino · 2023-05-19 08:41:59

d.ALT wrote:

Sorry guys, I don't understand. I was thinking that this merge would imply removing [community] declaration from pacman.conf. What am I missing?

There will probably be a new default pacman.conf without [community] repo, I would guess.

Enrico1989 · 2023-05-20 06:18:00

How do I know if I need to take any action, now or after the migration?

Surely this suggests I have to do nothing

For regular users, this means that everything works as before.

but at the same time I read that

The [community] repository will be merged into [extra] and will therefore be empty after the migration. All affected repositories will be provided as empty repositories for a transition period after the migration.

so I wonder if I'll need to remove the following lines from my /etc/pacman.conf

[community]
Include = /etc/pacman.d/mirrorlist

WorMzy · 2023-05-20 08:55:27

You can remove it if you want, nothing will break if you do, and nothing will break if you don't. It'll probably be removed from the packaged version of pacman.conf at a later date (which will result in a .pacnew file for most people).

micronetic · 2023-05-20 10:14:11

Foxboron wrote:

How does this impact Arch Linux packagers?
Packagers will not be able to patch and update their packages. The internal Tier 0 mirror is also going to be disabled for the duration of this migration.

Maybe I am misunderstanding something here but why are there updated packages from today (20.5.2023) when the packagers aren't able to patch and update their packages?

schard · 2023-05-20 10:40:02

micronetic wrote:

Foxboron wrote:
How does this impact Arch Linux packagers?
Packagers will not be able to patch and update their packages. The internal Tier 0 mirror is also going to be disabled for the duration of this migration.
Maybe I am misunderstanding something here but why are there updated packages from today (20.5.2023) when the packagers aren't able to patch and update their packages?

Foxboron · 2023-05-20 12:02:04

micronetic wrote:

Foxboron wrote:
How does this impact Arch Linux packagers?
Packagers will not be able to patch and update their packages. The internal Tier 0 mirror is also going to be disabled for the duration of this migration.
Maybe I am misunderstanding something here but why are there updated packages from today (20.5.2023) when the packagers aren't able to patch and update their packages?

We need to validate that the new setup works. So a restricted set of packagers get access early to limit any issues if we forgot something.

There is a complete runbook available: https://md.archlinux.org/utjjQ-bQTsipIKntPrpf8g?both

micronetic · 2023-05-20 15:08:56

Foxboron wrote:

micronetic wrote:
Foxboron wrote:
How does this impact Arch Linux packagers?
Packagers will not be able to patch and update their packages. The internal Tier 0 mirror is also going to be disabled for the duration of this migration.
Maybe I am misunderstanding something here but why are there updated packages from today (20.5.2023) when the packagers aren't able to patch and update their packages?
We need to validate that the new setup works. So a restricted set of packagers get access early to limit any issues if we forgot something.

There is a complete runbook available: https://md.archlinux.org/utjjQ-bQTsipIKntPrpf8g?both

Thank you very much for the explanation!

-----

schard wrote:

micronetic wrote:
Foxboron wrote:
How does this impact Arch Linux packagers?
Packagers will not be able to patch and update their packages. The internal Tier 0 mirror is also going to be disabled for the duration of this migration.
Maybe I am misunderstanding something here but why are there updated packages from today (20.5.2023) when the packagers aren't able to patch and update their packages?
https://i.gifer.com/2Gb.gif

Good one :-D

Last edited by micronetic (2023-05-20 15:09:23)

ewaller · 2023-05-21 15:42:07

The migration is complete.

https://archlinux.org/news/git-migration-completed/

harcher · 2023-05-22 10:42:20

This is probably not a big deal but the arch announcement I got via email didn't hae a properly formatted quotes in the instructions.
It looks like this:

$ pacman -Syu "pacman>=6.0.2-7"`

Enrico1989 · 2023-05-22 18:32:51

Update your system and merge the pacman pacnew /etc/pacman.conf.pacnew file.

I guess that the merging is manual, in the sense that I need to update the old one (e.g. [community] -> [extra]) an presumably keep my personal edits to it (e.g. ILoveCandy).

Anyway, which of the two files shluld we merge into? As in, after the merge, am I supposed to have only /etc/pacman.conf.pacnew or only /etc/pacman.conf?

ewaller · 2023-05-22 18:35:07

Leave only /etc/pacman.conf.

arnuld · 2023-05-23 04:14:31

This does not seem to work:

[arnuld@arch64 ~ ]$ sudo pacman -Syu "pacman>=6.0.2-7"
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
error: target not found: pacman>=6.0.2-7

[arnuld@arch64 ~ ]$ pacman -Q pacman
pacman 6.0.2-6

Last edited by arnuld (2023-05-23 04:15:00)

Arch Linux

#1 2023-05-16 10:25:47

Git migration announcement

#2 2023-05-16 10:55:42

Re: Git migration announcement

#3 2023-05-16 11:14:45

Re: Git migration announcement

#4 2023-05-16 11:38:43

Re: Git migration announcement

#5 2023-05-16 11:56:56

Re: Git migration announcement

#6 2023-05-16 12:04:34

Re: Git migration announcement

#7 2023-05-16 12:08:16

Re: Git migration announcement

#8 2023-05-16 12:13:10

Re: Git migration announcement

#9 2023-05-16 14:57:42

Re: Git migration announcement

#10 2023-05-16 15:51:13

Re: Git migration announcement

#11 2023-05-19 06:12:46

Re: Git migration announcement

#12 2023-05-19 07:44:28

Re: Git migration announcement

#13 2023-05-19 07:58:55

Re: Git migration announcement

#14 2023-05-19 08:41:59

Re: Git migration announcement

#15 2023-05-20 06:18:00

Re: Git migration announcement

#16 2023-05-20 08:55:27

Re: Git migration announcement

#17 2023-05-20 10:14:11

Re: Git migration announcement

#18 2023-05-20 10:40:02

Re: Git migration announcement

#19 2023-05-20 12:02:04

Re: Git migration announcement

#20 2023-05-20 15:08:56

Re: Git migration announcement

#21 2023-05-21 15:42:07

Re: Git migration announcement

#22 2023-05-22 10:42:20

Re: Git migration announcement

#23 2023-05-22 18:32:51

Re: Git migration announcement

#24 2023-05-22 18:35:07

Re: Git migration announcement

#25 2023-05-23 04:14:31

Re: Git migration announcement

Board footer