Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: Updating Tumbleweed

  1. #1
    Join Date
    Feb 2009
    Location
    UK
    Posts
    1,085

    Default Updating Tumbleweed

    Hi folks, Yeasterday I read a long conversation on the mailing list about the correct way to update TW. It seems that even the top gurus of this parish have sort-of agreed to disagree on the topic, but that a consensus seems to favour:
    Code:
     #zypper dup --no-allow-vendor-change
    ??

    There was no mention in the conversation of the updater 'applet' which checks daily or whenever, and pops up in the taskbar.. Can someone tell me whether simply allowing the updater applet to do its thing is OK? And what "zypper commands" it is actually performing?
    My previous habit, on 13.2 and before was to notice the updater telling me that there was updates available and then to do
    Code:
    #zypper ref && zypper up
    I get a warning that this is not recommended now, and that I should:
    Code:
    #zypper dup
    But this also gives a warning.

    Is best practice
    Code:
     #zypper dup --no-allow-vendor-change
    ??

    Or something else?

    Tumbleweed/KDE/Ati Radeon R9 270/AMD FX-6300/8Gb DDR3

  2. #2
    Join Date
    Jun 2015
    Location
    Toulouse
    Posts
    133

    Default Re: Updating Tumbleweed

    Le 17/11/2017 à 11:46, wakou a écrit :

    > consensus seems to favour:
    >
    > Code:
    > --------------------
    > #zypper dup --no-allow-vendor-change
    > --------------------


    yes. I was also uncertain some month ago and this is what we should now
    think as official, and the option no-allow-vendor-change is now default
    so go for zypper dup :-)

    > me whether simply allowing the updater applet to do its thing is OK? And
    > what "zypper commands" it is actually performing?


    good question, I don't have an answer

    jdd

  3. #3
    Join Date
    Feb 2016
    Location
    Berlin
    Posts
    357

    Default Re: Updating Tumbleweed

    the updater app will NOT do the right thing. I have brought this up on the mailing list as misleading/dangerous and should be disabled but to no avail.

  4. #4
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    16,287

    Default Re: Updating Tumbleweed

    Updater is more like zypper up then zypper dup so should not be used on TW

  5. #5
    Join Date
    Feb 2009
    Location
    UK
    Posts
    1,085

    Default Re: Updating Tumbleweed

    Thank you! So I should:
    Code:
    #zypper dup --no-allow-vendor-change
    When the applet alerts me that updates are needed/available?

    Tumbleweed/KDE/Ati Radeon R9 270/AMD FX-6300/8Gb DDR3

  6. #6
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    2,033

    Default Re: Updating Tumbleweed

    Yes, "zypper dup --no-allow-vendor-change" from the command line is the only correct way to update TW

    "--no-allow-vendor-change" is now the default, so a simple "zypper dup" is sufficient, although there is no harm in still specifying it, indeed I still use it myself from habit.

    You could rely upon the updater to inform you.

    Other options would be to perform the update on a regular basis (weekly for example), or to follow the factory mailing list https://lists.opensuse.org/opensuse-factory/ for snapshot release announcements.
    Regards, Paul

  7. #7
    Join Date
    Oct 2014
    Location
    Italy
    Posts
    2,238

    Default Re: Updating Tumbleweed

    Quote Originally Posted by wakou View Post
    My previous habit, on 13.2 and before was to notice the updater telling me that there was updates available and then to do
    Code:
    #zypper ref && zypper up
    That was a good habit and still is for the "regular" Leap releases. Actually "zypper up" does also a "ref" if needed, so the "zypper ref" part is overkill.
    Basically, "zypper up" only upgrades packages to a higher version, while "zypper dup" also downgrades a package to a lower version if the repo carries a version lower than that installed in the system; this may occasionally happen on Tumbleweed when a troubled package is reverted to a previous version while the newer one gets fixed. When that happens, "zypper up", or the update applet, will leave you with a broken system on Tumbleweed.
    Hope this makes things clearer to you.
    Tumbleweed Gnome on i7 4720HQ + Geforce GTX960M
    testing Leap 15.3

  8. #8
    Join Date
    Feb 2009
    Location
    UK
    Posts
    1,085

    Default Re: Updating Tumbleweed

    "Hope this makes things clearer to you." It doesn't, but thank you!

    Tumbleweed/KDE/Ati Radeon R9 270/AMD FX-6300/8Gb DDR3

  9. #9

    Default Re: Updating Tumbleweed

    just to add to the confusion, I have this in my daily cron job:

    Code:
    zypper -n -q dup --no-recommends --auto-agree-with-licenses --replacefiles --allow-vendor-change
    It's been running like this for well over a year. There are a few things to note, though: packman is the only addon repo configured besides the regular tumbleweed repos. No nvidia, no KDE extras, no kernel, nothing. On the rare occasion when I need a package not in tumbleweed+packman, I download it from OBS repo and install it manually. The cronjob will not remove those. Oh, and I have plasma5-pk-updates uninstalled and on the lock list.

    I think all of this discussion about vendor change comes from addon repos. If you do not have a ton of addon repos, it is fairly safe to use allow-vendor-change as the worst that can happen is a short term switch from packman to tumbleweed and then back. In fact, I was somewhat put off at the change to making the "no" default. But then, nothing you cannot change with a very small shell script.

  10. #10
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,676
    Blog Entries
    3

    Default Re: Updating Tumbleweed

    Quote Originally Posted by markdd View Post
    Code:
    zypper -n -q dup --no-recommends --auto-agree-with-licenses --replacefiles --allow-vendor-change
    I also use "--allow-vendor-change", though I'm not doing it with a cron job.

    As in your case, my only repos are the standard ones plus packman. The standard repos have priority 99, while packman has priority 98. So allowing vendor change should sort things out correctly (prefer packman where there is a choice).

    As best I can tell (sometimes running with the "--allow-vendor-change") is that it will usually make the same vendor changes (if any) either way. But, with "--allow-vendor-change" it won't give me a conflict resolution dialog.
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •