Taken care of.
3 Likes
Perhaps a better way to deal with the versions is use the method in the PKGBUILDs for the -git packages in the AUR:
pkgver() {
cd ${pkgbase%-git}
_ver="$(grep -m1 'set(PROJECT_VERSION' CMakeLists.txt | cut -d '"' -f2 | tr - .)"
echo "${_ver}_r$(git rev-list --count HEAD).g$(git rev-parse --short HEAD)"
}
This gives versions like 5.81.80_r1215.gfce6cf5, which identifies the alpha release.
Humm actually some cmake files doesn’t have PROJECT_VERSION… So maybe git describe --long --tags --abbrev=7 | sed 's/\([^-]*-g\)/r\1/;s/-/./g;s/^v//' is a more robust approach…
1 Like
sorry been all day away from computer.
working on it! also checked that arch kde-unstable did a lot of updates.
Gonna try to include updates and also with new version scheme!
3 Likes
well… uploaded to github updated packages in new branch: new_pkgver
built some packages with new pkgver (packages that had new commits).
its necessary to do a pacman -Syuu
NOTE: (big notice) → To update to NEWER packages, one needs to do “pacman -Syuu” !!! it will seem a downgrade for pacman, because of the version change, but it is not!!
3 Likes
Just added the repo and trying to install the apps from kf6, extra, plasma file, getting this error:
error: failed retrieving file 'kidletime-9999.r415.cd5739c4.1-1-x86_64.pkg.tar.zst.sig' from r2.garudalinux.org : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
error: failed retrieving file 'plymouth-kcm-5.27.80.r6.g0f384e165-1-x86_64.pkg.tar.zst.sig' from r2.garudalinux.org : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
warning: failed to retrieve some files
error: failed to commit transaction (download library error)
Errors occurred, no packages were upgraded.
EDIT: Sorry if this is a universal error, because someone has filed same issue for garuda-update
EDIT: FIXED
It seems like a mirror network issue. Glad that its fixed 
2 Likes
Would it be possible to manually trigger a rebuild of everything just for the version change? That way we only need to “downgrade” once and stick with normal upgrades afterwards.
sure, its possible.
didn’t do it, because was expecting that it would happen faster, and there is an issue, dunno why, may be chaotic only, the pkgrel doesnt apply! (that was why I had pkgrel directly in the pkgver)
1 Like
I am not sure I understand what you mean by that. Looking at the repo, it seems that all the packages have the “-1” at the end, which is the pkgrel.
Also when I use makepkg to compile the PKGBUILDs, I also get the “-1” at the end.
1 Like
yes, but if you notice, there are lots of PKGBUILDs which pkgrel != 1 !!!
2 Likes
All the PKGBUILDS in the pkg_* folders have pkgrel=1. Which ones should I be looking at?
for example, sddm is at pkgrel=3
I also tested it on the server, changing pkgrel=2 to every package. Anyway, I am rebuilding everything, and will look at issues (some conflicts appears, have to check it)
3 Likes
By the way the versions of plasma-framework, kactivities-stats, kactivities, and kwayland need special treatment, in case you haven’t noticed. Otherwise they conflict with the 5 version of the packages. Sorry for not catching that sooner!
please ignore downgrade for kio-extras to 22.* version. it was a mistake 
yeah… and there is a plasma-activities-stats now too:
probably from the move of activities, from kf6 framework to plasma
2 Likes
Yeah this is mentioned here. See also this and this for other packaging guidelines. But hopefully we could just follow whatever upstream is doing.
2 Likes
Nearly all the packages are on the new version system!
The github repo was such a life saver! It made fixing broken packages very straight forward. (Yeah, they still get broken some times, because when a package is updated, packages that depend on it may need to be rebuilt… l can’t think of a simple solution to this off the top of my head though. Not only do some packages have to be rebuilt, the user also needs to be notified of the need to update. Not sure what should be done in this case. Having versioned dependencies, or bumping the pkgrel might work, but both seem complicated and not robust.
1 Like
glad the github repo helped wish things were at a better stage, but … such is life!
About the rebuild thing, yeah, the word simple in “simple solution” is the issue. For now… making a way to build package in proper order would be excellent.
3 Likes
plasma 6 beta 1 will be released today! Hope everything goes smoothly.