And will security issues remain unchanged when it comes to access by, say unauthorized persons?
Forgive me for such a silly question, but I just wanted to know if moving the project, could pose any dangers
I would argue it still works the same just removes one step in between. So it should be a bit safer.
1 Like
It’s coming alive already:
https://archlinux.org/packages/extra-testing/any/devtools/
it’s just a random package in the activity stream that I saw getting updated in the new repository and with the sourcecode on gitlab.
As the repo sync service has been disabled, no mirrors show those changes yet, so don’t edit your pacman.conf until the migration is done.
2 Likes
4 Likes
official confirmation that they are ahead of schedule:
https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/message/EOERNQY263J4JVE3DCYWLIQWUCLWZVBU/
2 Likes
Apparently it’s completed: https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/JL2OD7E73M5BMHG27KWV7MI3LBSXQNSS/
I have not been able to complete the following step though:
Update your system and merge the pacman pacnew
/etc/pacman.conf.pacnewfile. This is required as we have moved the[community]repository into[extra].$ pacman -Syu “pacman>=6.0.2-7”`
When I try to follow the above, I get the following error message: target not found: pacman>=6.0.2-7
1 Like
Same here.
Found this on arch forums:
I see on reddit that the repos are not necessarily done synching. I will wait a while.
So I will just do the same… 
1 Like
Just got mail:
https://archlinux.org/news/git-migration-completed/
For users
Update your system and merge the pacman pacnew /etc/pacman.conf.pacnew file. This is required as we have moved the [community] repository into [extra].
$ pacman -Syu "pacman>=6.0.2-7"
For users of the now deprecated asp tool, you will need to switch to pkgctl:
$ pacman -Syu "devtools>=1:1.0.0-1"
$ pkgctl repo clone linux
For some more detailed instructions on how to obtain PKGBUILDs see the corresponding wiki article.
but !!
Mirrors are syncing again, but it may take a bit of time until your mirror of choice has caught up.
3 Likes
When I try to follow the above, I get the following error message
error: target not found: pacman>=6.0.2-7
Is this because mirrors are syncing? For me it looks more like a file is missing.
1 Like
indeed no need to panic now… process is finished… but all the the mirrors now need to get in sync… this was the biggest change on the arch infrastructure for a long long time …
In addition to syncing everyone is now try to update and pulling huge load on all the mirrors… at the same time … so be pationed and wait…
5 Likes
The instuctions don’t seem clear to me. Is it pacman -Syu , merge the pacnew file then pacman -Syu "pacman>=6.0.2.7 OR just pacman -Syu "pacman>=6.0.2.7" then merge the pacnew file?
The latter.
Basically, pacman -Syu "pacman>=6.0.2.7" translates to “Update the system and install pacman if the version of pacman is at least 6.0.2.7”
It was probably published that way to avoid tons of people asking why they updated their system but didn’t get a pacnew file.
5 Likes
Understood. Thank you.
1 Like
looks like mirror providers didnt stop trying to sync, and they all synced 404-html pages instead of the packages:
https://bbs.archlinux.org/viewtopic.php?pid=2100770#p2100770
Might be that the mirrors need manual intervention to actually see that package change now - it looks like they think that they already have that file because they only check for existence by name or database entry and not if the file is actually correct (that osbeck mirror usually syncs every 5 minutes)
Edit: that osbeck mirror thinks that it synced correctly:
https://mirror.osbeck.com/archlinux/lastsync
1684682400 - which is one minute ago 17:20 CEST, unix timestamp converted to real time
Arch users at 21.05.2023
10 Likes
Patience guys. There is not even a single Tier1 fully synced yet.
My upstream is at letter “s” with pool/packages/
Couple more hours. 
5 Likes
according to this site:
https://archlinux.org/mirrors/status/tier/1/
almost all Tier 1’s are reporting 100% done. But checking one of them (https://archlinux.org/mirrors/f4st.host/755/) it also shows the 56byte pacman file 
lets see if that resolves anytime today
Edit: @moson I have now received several updated packages that were updated now (some hours after the migration finished), but packages that were updated during the migration are still broken …
This mirror worked for me just now:
Edit: This goes in /etc/pacman.d/mirrorlist
https://ftp.sh.cvut.cz/arch/$repo/os/$arch
This is the clickable link:
https://ftp.sh.cvut.cz/arch/core/os/x86_64/