You are not logged in.
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.
Offline
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?
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline
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.
Offline
What about [community-testing]? Will it go to [extra-testing]?
Offline
What about [community-testing]? Will it go to [extra-testing]?
Yes.
Offline
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)?
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
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)
Offline
Details:
https://gitlab.archlinux.org/archlinux/ … -repos.rst
And the discussion during development of that RFC:
https://gitlab.archlinux.org/archlinux/ … equests/14
Offline
Sticking topic until after the migration.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
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)
Offline
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?
<49,17,III,I> Fama di loro il mondo esser non lassa;
<50,17,III,I> misericordia e giustizia li sdegna:
<51,17,III,I> non ragioniam di lor, ma guarda e passa.
Offline
Is this and the new pkgctl a step towards an automatic build farm?
Any timeline on that?
Offline
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)
Offline
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.
Offline
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
Offline
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).
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
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?
Offline
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?
Inofficial first vice president of the Rust Evangelism Strike Force
Online
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
Offline
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!
-----
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?
Good one :-D
Last edited by micronetic (2023-05-20 15:09:23)
Offline
The migration is complete.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
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"`
Offline
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?
Offline
Leave only /etc/pacman.conf.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
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)
Offline