Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: System Updates only with 'zypper dup#

  1. #11
    Join Date
    Nov 2013
    Location
    Kamloops, BC, Canada
    Posts
    3,974

    Default Re: System Updates only with 'zypper dup#

    Quote Originally Posted by horizonbrave View Post
    according to this link it should be:

    Code:
    zypper dup --no-allow-vendor-change
    I wonder why everyone still spreading the "zypper dup" way of life on TW.

    If someone doesn't install codec/pacman would it be so bad to keep upgrading/updating with zypper dup --no-allow-vendor-change ??
    The --no-allow-vendor-change switch is, and has been for quite some time now, the default switch in zypper dup, already activated by default so there is no need to add the switch.

    Apparently, your googling appears to have missed the multitude of announcements mentioning that.

    That lwn link above is the first result of googling "how keep tumbleweed update"!!
    That is obviously an old, outdated link.

    Third result is from the official TW portal/webpage and still suggests zypper dup
    Which is the correct method, although actually adding the --no-allow-vendor-change will not hurt, since adding it has no effect, changes nothing.
    -Gerry Makaro
    Fraser-Bell Info Tech
    Solving Tech Mysteries since the Olden Days!
    ~~
    If I helped you, consider clicking the Star at the bottom left of my post.

  2. #12

    Default Re: System Updates only with 'zypper dup#

    Thanks for replies!

    Please another question: how bad is to update TW using a terminal emulator (like Gnome Terminal) rather than a new Virtual Session (the ones you open with CTRL+ ALT + Fx, sorry for wrong wording)?
    How many chances to bork the system because of running processes?

    Cheers

  3. #13
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    27,817
    Blog Entries
    15

    Default Re: System Updates only with 'zypper dup#

    On Mon 26 Nov 2018 08:16:03 AM CST, horizonbrave wrote:


    Thanks for replies!

    Please another question: how bad is to update TW using a terminal
    emulator (like Gnome Terminal) rather than a new Virtual Session (the
    ones you open with CTRL+ ALT + Fx, sorry for wrong wording)?
    How many chances to bork the system because of running processes?

    Cheers


    Hi
    Run the command screen, then do your update...

    --
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.25-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!


  4. #14
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    13,174
    Blog Entries
    3

    Default Re: System Updates only with 'zypper dup#

    Quote Originally Posted by malcolmlewis View Post
    Hi
    Run the command screen, then do your update...
    Yes, this is what I use.

    Sometimes an update will restart some process and crash the desktop. But screen keeps running.

    I normally use "screen -L" to run updates. That way the output is logged to a file. If the desktop crashes, then I use
    Code:
    tail screenlog.0
    to check the screen output. And it is sometimes still running. So I wait for everything to finish in the update before rebooting.

    If I forgot the "-L", then I instead use "ps" to see if "zypper" is still running somewhere. And I wait for that to finish.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  5. #15

    Default Re: System Updates only with 'zypper dup#

    On 11/26/18 3:16 AM, horizonbrave wrote:
    >
    > Thanks for replies!
    >
    > Please another question: how bad is to update TW using a terminal
    > emulator (like Gnome Terminal) rather than a new Virtual Session (the
    > ones you open with CTRL+ ALT + Fx, sorry for wrong wording)?
    > How many chances to bork the system because of running processes?
    >
    > Cheers
    >
    >


    I always use a konsole window for running

    ----------

    zypper dup

    ----------

    and never have any problems. just makw sure you logout/in or reboot
    after the update.

    --
    Ken
    unix since 1986
    S.u.S.E.-openSUSE since 1998

  6. #16

    Default Re: System Updates only with 'zypper dup#

    Quote Originally Posted by nrickert View Post
    [...] I normally use "screen -L" to run updates. That way the output is logged to a file. If the desktop crashes, then I use
    Code:
    tail screenlog.0
    to check the screen output. And it is sometimes still running. So I wait for everything to finish in the update before rebooting.
    If I forgot the "-L", then I instead use "ps" to see if "zypper" is still running somewhere. And I wait for that to finish.
    What do you think should the Tumbleweed wiki page provide the full "screen" command?
    I know I know Tumbleweed is not for noobs, but still.. improving instructions doesn't hurt, and noobs will keep doing things they shouldn't anyway.. you can't stop them and this way they'll steal valuable forum resources with their problems because of not fully detailed instructions. Just my 2 coins :)))

  7. #17
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    13,174
    Blog Entries
    3

    Default Re: System Updates only with 'zypper dup#

    Quote Originally Posted by horizonbrave View Post
    What do you think should the Tumbleweed wiki page provide the full "screen" command?
    That might be a good idea.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

Page 2 of 2 FirstFirst 12

Tags for this Thread

Posting Permissions

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