Hi,
I am excited by Leap 15.1 arrival.
However, zypper dup says “nothing to do”.
Any suggestions?
Thanks for your help.
Here’s what I did:
Step 1: I changed all of the repos to the 15.1 version. I did this by editing the files in “/etc/zypp/repo.d” and changing “15.0” to “15.1”.
Step 2: Disable any other repos (with no “15.0” string). I did that with Yast Software Repositories.
Step 3: I used CTRL-ALT-F1 to get to a terminal screen (virtual console).
Step 4: I shutdown the graphic interface with
telinit 3
Step 5: I ran
zypper dup --allow-vendor-change
And it all went very smoothly. It took a while, but there were no problems. I then did:
shutdown -r now
to reboot, and I had Leap 15.1 running.
I am stuck at Step 1:
SUDO_EDITOR=kwrite sudoedit /etc/zypp/repo.d
THIS IS POTENTIALLY INSECURE!
To edit files as root please use:
SUDO_EDITOR=kwrite sudoedit <file>
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
sudoedit: /etc/zypp/repo.d unchanged
Screen shows a blank page for new file.
“/etc/zypp/repos.d” is a directory, not a file.
Use “ls” to list the contents
ls /etc/zypp/repos.d
The individual files will be named in the form of “‘repository name’.repo”
You will need to edit them individually.
It’s /etc/zypp/**repos.d **-- a directory as tannington says.
The advice was to change the files “**in **”/etc/zypp/repo.d" (which is short for file names in /etc/zypp/repo.d.
CLI people would go there
cd /etc/zypp.d
and then do mv statements.
But when you are a bit afraid of using the CLI, you can use YaST > Software > Repository Management also for this. Select them one by one and Edit changing their URLs.
Tried nrickerts approach on 2 machines with 15.0, worked quite well!
Due to some write errors (“Failed writing body”) after 1600 packages being downloaded out of 2519 packages, possibly due to disk getting close to being full, I ended up having to install 15.1 via a DVD.
It’s working now!
Cheers!
That’s the important part.
Yes, you do need space for those packages.
Those whose disk space is limited can disable downloading all rpms in advance of installation with a zypper option or via zypp.conf modification. This has been my method for many years. Though risk from interruption doing this is warned against, it has never caused a system reboot failure here. Such failures may be avoided because I use a miniscript to update the package management system and a bit of the system foundation before proceeding with a dup:
zypper -v in --download-in-advance zypper libzypp libsolv-tools rpm openSUSE-release
zypper -v in --download-in-advance device-mapper dmraid glibc lvm2 multipath-tools mdadm systemd udev
Maybe I should comment on this.
I actually put the package cache on an NFS server, so that I can share it between several systems. And I had lots of space on that NFS server.
When I switched the repos to 15.1, I also switched the package cache directories to those for 15.1 (by changing a few symbolic links).
I’m pretty sure it would have worked without that. My root partition had room to spare.
Yes, you do need space for those packages.
My root partition had room to spare.
What space would be required on root and elsewhere to do the upgrade from 15.0 to 15.1?
I am interested in trying an upgrade instead of a fresh install, following the steps you suggested in #2 of this thread.
If you do “zypper dup -D” (dry-run) instead of just “zypper dup”, zypper will report whether the process should succeed (adequate freespace).
The main issue will be for the root partition (or, really, the partition containing “/var/cache/zypp”) since that is where the packages are downloaded.
My rough guess would be that the root partition should be no more than 2/3 full. The downloaded packages are compressed, so roughly half the size of what will be installed. So with 2/3 full, you would have half of that 2/3 (i.e. 1/3) for downloading. Once installing starts, space gets freed up. The older 15.0 software is removed, the new package is installed, then that downloaded package is removed.
I like the suggestion of mrmazda to start with a dry run to find out.
Although slightly OT: Is there a how-to available for setting this up Additional question: As I 'm currently setting up a new linux file server (as usual with samba), NFS is still not available natively in Win7, or? As the most important clients for the NAS are some Win 7 64bit machines…
Hey guys,
If you want to save yourself a lot of work and possible mistakes modifying repo files, don’t do it manually.
Follow the instructions in
https://en.opensuse.org/SDB:System_upgrade
which provides the following command which modifies all your repo configurations from 15.0 to 15.1.
If you are upgrading from a different openSUSE version, you can substitute your version for “15.0” in the script
sed -i 's/15.0/15.1/g' /etc/zypp/repos.d/*
TSU
I blogged about it at the time I set this up:
Sharing updates with opensuse
Ignore the problems that I mentioned with NetworkManager – that has been fixed.
Additional question: As I 'm currently setting up a new linux file server (as usual with samba), NFS is still not available natively in Win7, or? As the most important clients for the NAS are some Win 7 64bit machines…
I don’t think NFS is available in Windows. I’m using one of my linux systems as NFS server.
There is apparently a way to install the win 8 NFS client on Win 7, but I never tried it…
Did you run SMB / NFS performance test back-to-back? Is NFS significantly faster?
I never tested that. I just setup SMB for Windows clients and NFS for linux clients. And both worked, so I didn’t worry about performance. However, NFS of WiFi is not the best, so I use ethernet.
For anyone who has the time and motivation, I decided to do a little looking around regarding NFS on Windows…
First, what is officially supported…
NFS only on currently supported MSWindows Servers, functionality supports setting up both NFS Server and/or client, and only NFS v3.
https://docs.microsoft.com/en-us/windows-server/storage/nfs/nfs-overview
Regarding MSWindows Desktop versions, there are various articles that describe “Services for Unix” available in any MSWindows “Pro” version or better, (starting with Windows 7)
https://graspingtech.com/mount-nfs-share-windows-10/
But, NFSv3 is old, and what if you have Windows Home machines?
I found the following project creating a cross-platform, fully featured library which appears to be actively maintained (most recent significant contributions less than 3 months ago)
https://github.com/sahlberg/libnfs
At the end of the above project, it describes two other projects which implement the NFS library as a FUSE file system supporting NFS mounts.
Of the following two, I recommend trying the first since it appears to be actively maintained, while the other may work… I don’t know though if the 2 year old wrapper will work fine with the updated libraries (there might not be any problems)
FUSE NFS Crossbuild scripts
Instructions
https://github.com/Daniel-Abrecht/fuse-nfs-crossbuild-scripts
Downloads
https://github.com/Daniel-Abrecht/fuse-nfs-crossbuild-scripts/releases
NFS-Win
https://github.com/billziss-gh/nfs-win
This requires building (make) on Windows, I don’t know what is recommended. Maybe asking the author what he recommends is in order (submit github “issue”). I assume then you only need to clone this project to your machine and download WinFsp as described is required then build.
If anyone wants to explore this, good luck and report back!
TSU