Can’t provide ./repodata/375458fadbd57d1c608cb04caa43ac14471e881a938f05598cd88f1d5aa7e0fe-deltainfo.xml.gz
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository ‘repo-sle-update’ because of the above error.
Some of the repositories have not been refreshed because of an error.
Loading repository data…
Reading installed packages…
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See ‘man zypper’ for more information about this command.
Computing distribution upgrade…
2 Problems:
Problem: nothing provides ‘postgresql12-server = 12.6-3.24.1’ needed by the to be installed postgresql12-llvmjit-12.6-3.24.1.x86_64
Problem: nothing provides ‘postgresql12-server = 12.6-3.24.1’ needed by the to be installed postgresql12-llvmjit-12.6-3.24.1.x86_64
Problem: nothing provides ‘postgresql12-server = 12.6-3.24.1’ needed by the to be installed postgresql12-llvmjit-12.6-3.24.1.x86_64
Solution 1: deinstallation of postgresql12-llvmjit-12.6-lp152.3.19.1.x86_64
Solution 2: keep obsolete postgresql12-llvmjit-12.6-lp152.3.19.1.x86_64
Solution 3: break postgresql12-llvmjit-12.6-3.24.1.x86_64 by ignoring some of its dependencies
But I suspect your systems particular ‘take’ on it is likely out-of-date. Try a:
zypper refresh
to update your local zyppers knowledge of what that repository contains. From the dates on the view of the repo itself, it was last updated on 16th Nov, so it may well have been updated while you were in the middle of this procedure. The refresh command should update all that and hopefully get you on-the-way again.
I’ve just done a successful zypper refresh on a system containing that repo here so I think that is what has happened in your case.
Incidentally, we hope to be writing a 15.3 to 15.4 howto variant soon: but we have first to do another testing rpm release before-hand as there are known issues that should be sorted very soon as it goes. These are expected to be addressed in Rockstor version 4.5.1-0, if all goes to plan.
I’ve had a successful upgrade and everything is as it should be. I think maybe the issue arose because of the repo update happening while I was accessing it. The next day I ran zypper dup --download-in-advance --allow-vendor-change --no-recommends successfully.
Now I’m running 4.5 is there any new features that I should be aware of?
@Tony_Cristiano Thanks for the update and chuffed your’ve now zypper dup’ed OK to 15.3.
All details are at least indexed in the new testing release thread here:
The long and short of it is that it’s almost all library/tools/lang/module/db updates. With the new postgresql dependency having been moved to version 13, at least for now. But we have also improved the automated testing somewhat (Thanks again to @Flox for helping to kick that one off) and have also slipped in an improvement in our ability to detect, and consequently work around, cli initiated balances. This is important for us to be able to more rapidly accommodate such things as the newer raid levels that can require (currently at least) some cli maintenance. At least until we write them in properly to the Web-UI. See for example: https://rockstor.com/docs/howtos/stable_kernel_backport.html
regarding these newer raid levels.
We have some clients who are itching to use such things as raid1c3 or say a mix of data btrfs-raid6 with metadata btrfs-raid1c4 (for large drive count, and/or sized, Pools). And that currently requires by-hand (read command line interface) intervention and so while we were working on improving the testing for balance detection I ended up hopefully improving our capabilities in that area. The same has yet to be done for scrubs but at least we have a model of what looks to be a working approach already in the balance. Plus we can use the same newer approach/structures for our yet to be written, and long awaited, disk-replace capability. All in good time however as we first have to get stuff moved up to being openSUSE Leap 15.4 compatible, which hopefully testing 5.4.1-0 will kick-off.