So it seems arch is soon moving to git packaging.
This sure will be an interesting change. And also maybe worth a note in this forum, because some stuff won’t work for two days as it seems.
13 Likes
Thanks for the warning 
I have eos-update-notifier set to check daily, so presumably I will get error messages that weekend.
1 Like
Will this also impact the AUR? I know some packages there are infrequently rebuilt.
1 Like
That’s a good question. I’ll ask and let you know.
1 Like
Okay, if I understand it correctly, the AUR already uses git. The official repos do use SVN and convert that to git and save it to github. Now this step will be gone and the official repos will push directly to git and save everything on gitlab.
Soon after that the bug reporting will also happen on the gitlab page instead of using the current bug reporting system. Also people will be able to create pull requests.
At least that’s how I understand it. Please correct me if I’m wrong.
2 Likes
They just change the version control system for their build recipes (PKGBUILD’s).
That shouldn’t have effect on the resulting packages though.
The only thing an end user would notice is that there are a couple of days where you don’t get any updates. Mirrors will continue to serve whatever is there. So you shouldn’t get any errors messages or anything when syncing.
@Bryanpwo you can keep the sync services alive assuming you don’t sync directly from Arch Tier 0.
Actually, wait. Do you mirror arch packages at all?
edit Sorry, nevermind. I misread that other post. 
5 Likes
Thnx, I kind of figured that, but I just thought it was newsworthy in case someone posts over here that they think the mirrors are broken because of a lack of Arch updates during that time.
I also revised the post with your info in it as well.
1 Like
No, we don’t, we use the Arch services for that. Our mirror only mirrors our packages.
1 Like
Nope.
You mean updated I guess? The AUR does not deliver built packages. The building of a package happens on your machine
1 Like
Well, it delivers *-bin packages, but those are hosted somewhere else.
-bin just take pre-compiled binaries instead of building from source.
The packaging still happens on your machine
What the hell is git packaging?
1 Like
Answer I got from the internet
4 Likes
Git is a distributed version control system. In this type of VCS, a project contributor creates a local repository that is a full clone of a central repository. With a local clone of the central repository, each contributor is able to work on the project completely offline on their own computer. When changes are ready, contributors can push and merge them with the central repository.
Git has immense support from the open-source community. It has quickly become one of the most used version control systems for software development projects.
Versus the current SVN system:
Apache Subversion (SVN), is a centralized version control system. When working with this type of VCS, all project files exist on a central repository server. The central repository has a “trunk,” which contains the current, stable version of the project. When working on new features, contributors can make “branches” from the trunk. Each branch is stored in a sub-folder on the central repository. When changes are ready, a branch can be merged into the trunk.
SVN has a long and successful history and stands as a titan in the version control world. It has widespread usage for enterprise projects, with features like granular access control that make it excel in that context.
5 Likes
Oh jeez…They’ve used svn, that’s such a 
thing to do! 
Is this new system similar to Homebrew?
This is for Arch developers; it’s not going to directly affect users, i.e., you will still use pacman/yay to update. It’s just a different way for them to handle changes to packages.
5 Likes
The only thing the end user might notice is a lack of updates for two days, and after that, everything will be exactly the same.
4 Likes
for those not knowing what the change is about (@dbarronoss @I0F @keybreak @Lauri from the replies here in thread):
An example:
This shows the code base that Arch uses to build the kernel package (linux, linux-headers and linux-docs).
Those files are originally modified and stored on a SVN server and synced to the public github page (visible through the svntogit - part in the repository) After the change, those files will be modified and stored on the public Arch gitlab instance directly.
Thats everything that this change is about.
The only ones that will need to adapt are people like me, who sometimes rebuild repository-packages on their own because the repos are too slow with updates or want to add custom patches, because we then have to get our base-buildfiles from the gitlab - instance instead of github.
1 Like