Greetings . Since i am new to the Suse community after installing my Tumbleweed with EXT4 FS today and applying the updates i overcame the MESA problem that appeared today by deleting some cache files.
After logging in and doing sudo zypper up from terminal i am getting :
Loading repository data...
Reading installed packages...
The following package update will NOT be installed:
kernel-default
Nothing to do.
Can someone tell me why is keeping back this update ? Is it something i have to look more about it or it is normal ?
While you are waiting for a reply, you have not done any damage using “up”. But since this is a rolling distribution there is no reason not to use “dup”.
It is the nature of a rolling distribution, like Tumbleweed, that there will be many updates.
The problem is that when i installed the KDE, machine checked for updates and i installed them through the graphical applet at the taskbar .
Usually no harm done. But you will be left with a few obsolete packages. A “zypper dup” will fix that.
Shall i reinstall fresh and just ignore the notification about the update from the applet ?
No need to reinstall.
You can ignore the update applet. Or you can treat it as a notifier that it is time to do another “zypper dup”. Or just turn it off. Right click on the tray, select “System Tray Settings”, and uncheck the updater box.
Simply run ‘zypper dup’ . And disable / uninstall the update applet. It is not aware that you’re running TW. TW is released over and over again ( last week 6 times ) and needs zypper dup
That’s like saying never or always when you cannot in fact know. Dup is the official update method, but it doesn’t make up useless. Doing up first, followed by dup, segregates generally less significant changes from generally more significant changes, the latter of which may (without using the g key before y or n) fit onscreen for examination before proceeding, while a whole -v dup list easily may not for those who do their updates infrequently.
On 02/07/2018 03:16 PM, mrmazda wrote:
>
> doscott;2854447 Wrote:
>> there is no reason not to use “dup”.
> That’s like saying never or always when you cannot in fact know. Dup is
> the official update method, but it doesn’t make up useless. Doing up
> first, followed by dup, segregates generally less significant changes
> from generally more significant changes, the latter of which may
> (without using the g key before y or n) fit onscreen for examination
> before proceeding, while a whole -v dup list easily may not for those
> who do their updates infrequently.
>
>
But we in fact do know. For TW the only accepted option is ‘zypper dup’
because each new release of TW is a DistributionUPgrade. Notice it
says ‘Distribution’. If you changed from LEAP42.2 to LEAP42.3 by
updating the version in the repo files would you use ‘zypper up’ or
‘zypper dup’. Do you get the picture now. You are not simply updating a
few packages but making significant system changes.
–
Ken
linux since 1984
S.u.S.E./openSUSE since 1996
That’s like saying never or always when you cannot in fact know. Dup is
the official update method, but it doesn’t make up useless. Doing up
first, followed by dup, segregates generally less significant changes
from generally more significant changes, the latter of which may
(without using the g key before y or n) fit onscreen for examination
before proceeding, while a whole -v dup list easily may not for those
who do their updates infrequently.[/quote]But we in fact do know.[/quote]That ignores the entire point of my post, which is that there is at least one reason for (non-exclusively) using up, the one I stated, and have been routinely using since before TW replaced Factory.
For TW the only accepted option is ‘zypper dup’
because each new release of TW is a DistributionUPgrade.
It’s the only accepted method of completing the task. A non-linear path to completion can serve a useful purpose, not the least of which is discovering imminence of undesirable changes and taking steps to block them while still utilizing the others, intentionally leaving the task incomplete.
You are not simply updating a few packages but making significant system changes.
Exactly my reason for preceeding dup with up!
I must say that the replies i got are more than satisfactory in using -dup and since i am new to OpenSuse i took a nice look at the zypper commands with this chance given .
Appreciate your help and i am happy that i tried and now using Tumbleweed. Great community.
It stresses to use --no-allow-vendor-change, which is since already some time the default on Tumbleweed (though not on Leap). So, apart from learning about the underlying principles, there is no need anymore to point to this option. Just use
