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

Thread: How to evaluate the damaged of doing "zypper up" a few times?

  1. #11
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    19,877
    Blog Entries
    1

    Default Re: How to evaluate the damaged of doing "zypper up" a few times?

    Quote Originally Posted by machadoprx View Post
    There is no package conflict or dependency issue, just the usual lock on nouveau package.

    So if there is nothing wrong in 'zypper dup' , my machine is fine?
    Yes, likely all is ok. For the most part zypper is good at resolving most inconsistencies, provided the appropriate repos configured.
    openSUSE Leap 15.0; KDE Plasma 5

  2. #12
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    11,998
    Blog Entries
    3

    Default Re: How to evaluate the damaged of doing "zypper up" a few times?

    Quote Originally Posted by machadoprx View Post
    So if i have no errors when running "zypper dup" my system is not corrupted?
    It is probably fine.

    However: I suggest Yast --> Software Manager

    Click "View" near the top left, and select "Package Groups".

    Scroll down to the line for "Orphaned packages". If there are any orphaned packages, consider removing them.

    An orphaned package is one that is not in any enabled repo. There might be some that are orphaned for reasons that you know. But others might be left over because you used "up" rather than "dup" at some time.

    You might get a conflict for some removals. Usually the conflict is with other orphaned packages. But you may have to sort that out, or just keep the ones that can't be removed because of a conflict.
    openSUSE Leap 15.1; KDE Plasma 5;

  3. #13
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    1,404

    Default Re: How to evaluate the damaged of doing "zypper up" a few times?

    Zypper up hurts nothing, creates no "damage". It simply leaves the upgrade incomplete. I do it nearly always, but I follow up with dup. That way the minor updates are distinguishable by being grouped separately from more significant upgrades when asked for confirmation. The latter I'm more likely to reject by aborting and locking. I might not notice any I'd wish to reject with minors and majors all mixed together by only doing dup.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,more on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,Oland,GT218&&&

  4. #14
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,601

    Default Re: How to evaluate the damaged of doing "zypper up" a few times?

    Quote Originally Posted by machadoprx View Post
    So if i have no errors when running "zypper dup" my system is not corrupted?
    That is correct. Doing zypper dup after you (may heve corruptes somtehing by) doing zypper up, it is now repaired.
    Henk van Velden

  5. #15

    Default Re: How to evaluate the damaged of doing "zypper up" a few times?

    As long as the system boots, and zypper runs, nothing should be broken. At worst, some packages simply need to be updated.

Page 2 of 2 FirstFirst 12

Posting Permissions

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