Archlinux Git migration #189
Labels
No Label
blocked upstream
bug
build-failure
duplicate
enhancement
help wanted
informational
invalid
invalid/corrupt package
packaging issue
priority: high
question
support
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: ALHP/ALHP.GO#189
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Asking, just to be on a safe side: Arch will merge [community] repository into [extra]
https://archlinux.org/news/git-migration-announcement/
What does it mean for Alhp users? Will also Alhp repos be merged at the same time?
That's the plan, correct. I'm not sure about the timeline, since changes to the arch infrastructure mean changes to ALHP as well, so I need to figure that out when the time comes. Expect ALHP to be shipping no new updates for at least the same duration as Archlinux does not ship any updates.
Since the packages are hopefully only getting moved without being pkgrel bumped, it should be rather painless to move them from [community] to [extra].
People should probably also remove the [community] entry in the future,
but since it will be empty there will be no harm done if it stays in their config anyways.I'll adjust README, configs and ALHP itself ideally at the same time as Arch does, but no guarantees on that one, we'll see how it goes.
Thank you for clarification here, adn thank you so much for all the effort you put in this project
Migration on ALHP side is done. Please report any problems you encounter here.
Is there possibility of a conflict after Git Arch repos migration?to Archlinux Git migrationNice!
I was getting:
So I removed:
from /etc/pacman.conf
as my understanding is, community will be now in extra, so it was already removed
Since the buildbot would have removed the community folders anyways, I decided to just rip off the bandage and remove them beforehand. It's just a minor edit in the
pacman.conf
and one would need to merge the new one anyways.So far so good, closing.