As of a day or two ago I’m unable to update my computer. I haven’t changed anything regards to package management, so is there an issue with the update servers?
I usually update using the software updates widget in KDE, but periodically it just says that there’s a problem connecting to a software origin…
Any thoughts?
Many thanks in advance
Ross
probobly a mirror issue try doing
zypper up
anyway you should consider updating as 42.1 will be dead soon (6 months after 42.2 came out) I think that will be april or may
What’s the best way to update? I’m always apprehensive about doing a complete fresh install and potentially messing up my dual boot!! Is it download the DVD and choose the update option?
here’s the output of zypper up:
File ‘/repodata/repomd.xml’ not found on medium ‘http://download.opensuse.org/repositories/home:/deadpoint/openSUSE_Leap_42.1/’
Thanks again
On looking at that, it just looks like a repo for a package I installed ages ago has gone. I’ve deleted it, and it’s updating fine now.
Would like your opinion on the best way to update to 42.2 without the risk of messing up with the boot loader, and losing all my settings etc 
Many thanks!!
I recently updated one of my laptops from Leap 42.1 to 42.2 with the appropriate repo changes and ‘zypper dup’ (there are a couple of extra steps if using btrfs to be aware of). It can also be done via install media if preferred.
Live upgrade steps outlined here
https://en.opensuse.org/SDB:System_upgrade
Some additional accounts of the process…
Thanks, I’ll have a look either tomorrow or Wednesday.
Cheers!
that’s a user repo and the user decided not to build for 42.1
http://download.opensuse.org/repositories/home:/deadpoint/
only has SLE12, 42.2 and TW repo’s (and 13.2 lol)
you should remove that repo and redo an update
packages from that repo will not be changed
tell us your repo list
zypper lr -d
for me the easiest way to do an upgrade is live with zypper dup
see this
https://en.opensuse.org/SDB:System_upgrade#Running_the_Upgrade
in a nutshell you change your repo’s to point to 42.2 insead of 42.1 (change a number) and then run zypper dup
take noite that you should disable any 3rd party repo and remove any extra 3rd party driver (I remove nvidia rpm’s before doing an upgrade)
also it’s best to run the upgrade in run level 3 ie with no graphical server running
but that’s a different issue
That’s my issue, I’m concerned something will go wrong with my Nvidia drivers, like before. I may just download the latest DVD and see what happens! It’s always a good idea to have the OS on a disc anyway, just in case. If I do it this way, will it be likely my Nvidia drivers will screw up? I had all sorts of issues to start with!
Thanks
Updated to 42.2. Had a bit of a nightmare because my root partition ran out of space (!!!) so it had to abort the update…and upon trying to log in, it wouldn’t work, so I had to do a fresh install. Luckily this went very smoothly indeed, I kept my old user data…my dual boot bootloader still works fine. I’ve just spent 30mins, if that, installing various bits of software and codecs etc and all seems to be working well.
Not sure if I’ll notice a great deal of difference between the systems. I didn’t think Leap 42.1 was that old, so I’m surprised if what you’re saying is true about it being discontinued (in terms of update support) so soon. I thought they usually run 3 versions at once then when a 4th comes out, the 1st gets discontinued?
Cheers
is that a bumblebee rig?
I have a desktop with nvidia 240 and I did live upgrades from 13.2 to 42.1 then to 42.2
I had no problems, I did remove the nvidia driver and the nvidia repo before doing an upgrade
I only had the OSS, non-OSS, the update-OSS and update-non-OSS repo’s active
after the upgrade I re-added the nvidia repo and installed the driver
I had zero issues the upgrade took about half an hour it depends on your local mirror speed and how many packages you have installed
Have a read of the following…
https://en.opensuse.org/Lifetime
Maintained Regular distributions The following distributions are expected to receive updates until the specified date:
That’s very useful, thank you for that! Looks like 42.2 will be supported for quite a while at least.
Bit concerning my root partition was so full. After the fresh install it’s now got over 13gb free. Short of periodically deleting the tmp directory, and disabling snapper, is there any other way to ensure that it doesn’t get full?
Cheers
Don’t put things in it LOL
But it all depends on your usage.
Snapper just does not do well with root partitions significantly under 40 gig.
I never purposefully put anything in temp, I always try to save stuff to /home or a USB hard drive, and yet, over time, the root partition still got full…?
With snapper on or off??
Snapper does use space and if you have less then the minimum recommended then it may use most of the available thus reducing available space
/tmp is cleaned out on boot I think
On 03/09/2017 08:46 AM, gogalthorp wrote:
>
> With snapper on or off??
>
> Snapper does use space and if you have less then the minimum recommended
> then it may use most of the available thus reducing available space
>
> /tmp is cleaned out on boot I think
>
>
I don’t remember where zypper cache is located, perhaps that is using
space as well.
zypper clean
can be used to clear the cache directory.
You might want to allocate 100G to / next time to at least give you time
to monitor disk usage.
–
Ken
linux since 1994
S.u.S.E./openSUSE since 1996
Thanks everyone. I’m half contemplating using something like gparted to shrink my /home by 20gb or so, and increase the root partition, though obviously it’s a fairly risky business doing so.
Snapper was disabled, yes
Hi
So if it’s using btrfs, then you still need to look at running btrfs-balance which should recover space before looking at adjust partition sizes…
btrfs fi usage /
Are the btrfs maintenance tools installed?
zypper in btrfsmaintenance
/etc/cron.weekly/btrfs-balance
Hi,
thanks for your help thus far. Here’s an output for you…
ross@linux-p7rj:~> su
Password:
linux-p7rj:/home/ross # btrfs fi usage /
Overall:
Device size: 20.00GiB
Device allocated: 8.13GiB
Device unallocated: 11.87GiB
Device missing: 0.00B
Used: 6.18GiB
Free (estimated): 13.21GiB (min: 7.28GiB)
Data ratio: 1.00
Metadata ratio: 2.00
Global reserve: 96.00MiB (used: 0.00B)
Data,single: Size:7.01GiB, Used:5.67GiB
/dev/sdb4 7.01GiB
Metadata,DUP: Size:512.00MiB, Used:264.84MiB
/dev/sdb4 1.00GiB
System,DUP: Size:64.00MiB, Used:16.00KiB
/dev/sdb4 128.00MiB
Unallocated:
/dev/sdb4 11.87GiB
linux-p7rj:/home/ross #
Does that mean anything for you?
Thanks!
Bare in mind this is my clean install.
Sorry, for this is a long one…btrfs balance already installed…
linux-p7rj:/home/ross # /etc/cron.weekly/btrfs-balance
Before balance of /
Data, single: total=7.01GiB, used=5.67GiB
System, DUP: total=64.00MiB, used=16.00KiB
Metadata, DUP: total=512.00MiB, used=264.89MiB
GlobalReserve, single: total=96.00MiB, used=0.00B
Filesystem Size Used Avail Use% Mounted on
/dev/sdb4 22G 6.8G 15G 33% /
Done, had to relocate 1 out of 14 chunks
Dumping filters: flags 0x1, state 0x0, force is off
DATA (flags 0x2): balancing, usage=1
Done, had to relocate 1 out of 14 chunks
Dumping filters: flags 0x1, state 0x0, force is off
DATA (flags 0x2): balancing, usage=5
Done, had to relocate 1 out of 14 chunks
Dumping filters: flags 0x1, state 0x0, force is off
DATA (flags 0x2): balancing, usage=10
Done, had to relocate 1 out of 14 chunks
Dumping filters: flags 0x1, state 0x0, force is off
DATA (flags 0x2): balancing, usage=20
Done, had to relocate 1 out of 14 chunks
Dumping filters: flags 0x1, state 0x0, force is off
DATA (flags 0x2): balancing, usage=30
Done, had to relocate 1 out of 14 chunks
Dumping filters: flags 0x1, state 0x0, force is off
DATA (flags 0x2): balancing, usage=40
Done, had to relocate 1 out of 14 chunks
Dumping filters: flags 0x1, state 0x0, force is off
DATA (flags 0x2): balancing, usage=50
Done, had to relocate 1 out of 14 chunks
Done, had to relocate 2 out of 14 chunks
Dumping filters: flags 0x6, state 0x0, force is off
METADATA (flags 0x2): balancing, usage=1
SYSTEM (flags 0x2): balancing, usage=1
Done, had to relocate 1 out of 12 chunks
Dumping filters: flags 0x6, state 0x0, force is off
METADATA (flags 0x2): balancing, usage=5
SYSTEM (flags 0x2): balancing, usage=5
Done, had to relocate 1 out of 12 chunks
Dumping filters: flags 0x6, state 0x0, force is off
METADATA (flags 0x2): balancing, usage=10
SYSTEM (flags 0x2): balancing, usage=10
Done, had to relocate 1 out of 12 chunks
Dumping filters: flags 0x6, state 0x0, force is off
METADATA (flags 0x2): balancing, usage=20
SYSTEM (flags 0x2): balancing, usage=20
Done, had to relocate 1 out of 12 chunks
Is this a command I should run regularly then?