I like Leap 15.4 . . . but I also like “new” . . . . I tried a bunch of googly searches to try to get to where 15.5 Alpha might be available for download . . . but only found the release timeline page.
According to that page it should have been available since 7/9/22 (American dating) . . . . Awhile back I had to post here to get a link to the 15.4 Alpha download and this time it doesn’t seem overt in providing ways of getting to 15.5??
But, my question relates to finding out if there is a similar way to upgrade SUSE as in Debian or Ubuntu flavors where editing the /etc/apt/sources.list to the flavor of choice will upgrade; i.e., like with getting to Sid from Bullseye install by changing “bullseye” to “unstable”???
Any way to do that to get my perfectly fine 15.4 install upgraded to 15.5 in my aging '09 MBP???
Hi, 15.5 isn’t there for now: and in case it was, in my opinion, it’s in a workplace. (openQA).
As soon as it is made available, even before the test versions, you can see its logs on video. comments, etc. even have an iso and a live type.
Although 15.4 is fine, there are still things to solve, better give time to time and when you least expect it, we have it in our teams.
As evidence you have the current ones, their live versions, Argon, Kripton Gnome next, etc.
Best regards .
Post Date: It would not hurt to experiment with containers, for me it is new, but perhaps it is a field to explore and open to many possibilities
Thanks for the helpful replies . . . . I saw the “request for help” from the MicroOS folks . . . if it’s possible to run it from a flashdrive as “live” I can do that. I wasn’t looking for a fresh install to do, since I have a bunch of OSs already, but if I can boot it as “live” I could do that. On their page it said “install” . . . ??
It’s not like I need to change 15.4 to something else, just upgrading it to 15.5 . . . without fresh install is what I was looking for here; as well as if and when 15.5 would be ready . . . ??
Seems like it’s not quite there ready for testing . . . .
Hi
AFAIK, it’s an install or run in a virtual machine, no ‘live’ option. I’m guessing you could install to a USB device, but just to be sure would pull any drives especially if a laptop…
Hmm . . . OK, thanks for that reply. I did read through the MicroOS & what Leap Micro download pages and it said something like, “set up for USB devices” . . . but yes it didn’t say “live” . . . although it is something like 3.8GB in size, which is around what the “live” iso files are . . . . I have yet to do a regular install to a USB drive, which I understand is a little different than “burning” a live iso . . . definitely don’t have time to pull drives to get that done safely, etc. Haven’t messed with VMs in some years now, all my installs are bare metal.
Since I have my hands very full with Life stuff these days . . . I’ll prolly wait for when 15.5 is available . . . to upgrade via console . . . that seems to happen around “beta” release time rather than Alpha???
The 15.5 repos do not seem to have been enabled yet:
# zypper ref
Warning: The /etc/products.d/baseproduct symlink is dangling or missing!
The link must point to your core products .prod file in /etc/products.d.
Retrieving repository 'NonOSS' metadata ......................................................................[error]
Repository 'NonOSS' is invalid.
[NonOSS|http://mirrorcache.opensuse.org/distribution/leap/15.5/repo/non-oss/] Valid metadata not found at specified URL
History:
- [NonOSS|http://mirrorcache.opensuse.org/distribution/leap/15.5/repo/non-oss/] Repository type can't be determined.
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'NonOSS' because of the above error.
Retrieving repository 'OSS' metadata .........................................................................[error]
Repository 'OSS' is invalid.
[OSS|http://mirrorcache.opensuse.org/distribution/leap/15.5/repo/oss/] Valid metadata not found at specified URL
History:
- [OSS|http://mirrorcache.opensuse.org/distribution/leap/15.5/repo/oss/] Repository type can't be determined.
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'OSS' because of the above error.
Some of the repositories have not been refreshed because of an error.
#
Thanks for checking . . . figured it would be a few more days until it would be ready. But, you must be temporarily editing something to get zypper ref to show you the response?
Where and how are you doing that?? Or do you have a basic 15.5 system already installed???
Same way I went from 12.1 to 12.2: ]clone partition]make unique UUID & LABEL on clone*]adjust bootloaders & fstabs appropriately*]disable optional repos and premature repos*]sed -i ‘s/12.1/12.2/g’ /etc/zypp/repos.d/repo]zypper clean*]zypper ref
Sorry, the translators play tricks on me.
The versions that are available, either in distribution or in openQA, is what we have for now, 15.5, which I know is not there, or at least I have not seen it.
For which I do not know how it will be, I suppose that it is better than the current ones.
When it comes out in OpenQA, you can see its development, videos, logs, and other things, but for now nothing.
Both. Cloning is part of my backup/restore system in the first place, so in practice a trivial process.
Like if I just wanted to change my 15.4 to 15.5 I could in theory just run
sed -i 's/15.4/15.5/g' /etc/zypp/repos.d/*repo
followed by #6 & #7 ???
Do it that way, and if something goes horribly wrong, you have to start with a fresh installation instead of duping a re-clone, unless your 15.4 has snapshots to fall back on. I only use EXTx, so can’t do that. The vast majority of mine don’t get a whole lot of space allocated, e.g. 6400MiB for / for the one several hours ago. One of my 32bit TWs is still up to date on a 4000MB /.
If you’ve converted from literal version to $releasever in all your .repo files then of course that sed wouldn’t accomplish anything. What dup --releasever=15.5 would do before 15.5 repos actually exist someone else can test for.
Alrighty . . . well, I also use ext4 for all of my linux installs . . . so from what you said, using that command to change the repos from 15.4 to 15.5 “will not work”???
SUSE doesn’t have the method that I mentioned that I have used in both ubuntu and debian to simply edit the sources.list data???
Or, going into Yast and editing the repos there to make the upgrade?? At whatever time that 15.5 is available???
Which command is “that” command? Where did your supposition come from? Of course my sed command will, if 15.5 repos exist, and your .repo files aren’t using $releasever instead of a number.
The “command” is the “command line” using text editor to change the name of the repo in the /etc/apt/sources.list to the next one, like in ubuntu changing “jammy” to “kinetic” and voila . . . new system. Been doing that with Lubuntu for years . . . easy-peasy upgrade, same in Debian.
I did look into Yast a few minutes ago in the Software Repositories . . . and some of the lines show “releasesever” and “leap” and others show “/15.4/” and another one shows “15_4_1”??? Seems like it might be possible to use the “edit partial” option to change the “15.4” to “15.5”???
Would that work without creating “total horror”??? I have “/” and “/home” in separate partitions, so I could always do a fresh install into “/” if I had to, but prefer to not if I don’t have to . . . .
Well since 15.5 repos are not active yet you can not do anything yet. Once they become active normal upgrading should work Note supplemental repos like packman will may not be fully available until release
sed -i 's/buster/bullseye/g' /etc/apt/sources.list
and
sed -i 's/15.4/15.5/g' /etc/zypp/repos.d/*repo
Each makes one substitution in a handful of lines. The main difference is those lines are in different files in openSUSE, because it uses one config file per repo, which permits configuring more than a single characteristic per individual repo, e.g., whether to retain downloaded files in cache after installation; whether enabled; or whether to auto-refresh.
I did look into Yast a few minutes ago in the Software Repositories . . . and some of the lines show “releasesever” and “leap” and others show “/15.4/” and another one shows “15_4_1”??? Seems like it might be possible to use the “edit partial” option to change the “15.4” to “15.5”???
You could have edited each .repo file manually 100 times each in the time you’ve spent in this thread rephrasing the same basic question over and over again. Spend 5 minutes or less in MC in /etc/zypp/repos.d/ and the setup’s done, over, finished.
Would that work without creating “total horror”??? I have “/” and “/home” in separate partitions, so I could always do a fresh install into “/” if I had to, but prefer to not if I don’t have to . . . .
Repo configuration has nothing to do with personal data or how you should partition drives. You must make your own decisions. I have hundreds of installations. I make new ones from scratch maybe 3-8 times in any given year, usually as a part of alpha/beta testing Leap, or putting a new disk in somebody else’s PC or laptop. The vast majority remaining turn into a next release, after a clone, using zypper dup, urpmi --auto-select, apt-get full-upgrade or dnf system-upgrade, in decreasing order of preference.