Why put that version string in the PKGBUILD at all then, when you know it's going to be different with every checkout? (I could fix it, but it doesn't matter) the PKGBUILD doesn't know what sources it's building yet when it prints that version. No wonder the maintainer was admonished for this.Īnother thing that's a bit silly, this isn't going to be mesa-19.2.0_devel. This will also avoid the above problem I had with pacman -Syu and LLVM, next time that happens. I guess I'll remove that logic from the PKGBUILDs altogether and write normal makedepends and depends with the base package names instead of "8.0.0" which is retarded. => ERROR: Could not resolve all dependencies. it checks an environment variable to specify the LLVM version to use (numbers 1-4) and hard coding it later in the script with "case $MESA_WHICH_LLVM in", instead of just using what's on the system mesa-git]$ makepkg These PKGBUILDs I'm using are dumb as a rock in this regard too. Now I just have to rebuild my mesa-git packages (mesa 19.1.3 release tag) This is going to invalidate my cached shaders again (llvm this time probably).
#Xonotic forums scripting upgrade#
I guess I'll have to force those with -nodeps first, then finish the upgrade operation, then recompile my Mesa again just to fix package dependencies. :: installing llvm-libs (8.0.1-1) breaks dependency 'llvm-libs=8.0.0' required by mesa-git :: installing lib32-llvm-libs (8.0.1-1) breaks dependency 'lib32-llvm-libs=8.0.0' required by lib32-mesa-git that would be just fine, there's no need for this dumb logic.Įrror: failed to prepare transaction (could not satisfy dependencies) I don't have any packages showing up yet, but I'm ready for them, I already did a tarball snapshot today after upgrading my Mesa yesterday and testing some games (that sucks, because no matter how small, whether necessary or not, any change to Mesa invalidates cached shaders and I have to run my games and pan around)įucking stupid dependencies. So it warns every time packages get installed out of sequence. There might be more critical things, let's say you were upgrading an important service that gets restarted after the package install. Now, if you were doing that while getting updates, I would make fun of you. For example, if you were playing media with something that was using the phonon gstreamer backend, and you updated it out from under foot, and the phonon libraries were wrong.
It could crash something, under some circumstances I suppose, and that's the reason for the warning. You'll see that message often when it's sorting out a big run. That doesn't matter, as long as both packages are being installed in the same run.
0 kommentar(er)
