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

Thread: zypper dup with automatic conflict resolution

  1. #1
    Join Date
    Apr 2016
    Location
    North America
    Posts
    525

    Default zypper dup with automatic conflict resolution

    My latest attempt to run 'zypper dup' results in many conflict resolution options.
    Is there a way to run zypper dup with automatic conflict resolution (i.e. it will complete by itself)?

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,982

    Default Re: zypper dup with automatic conflict resolution

    Quote Originally Posted by ravas View Post
    My latest attempt to run 'zypper dup' results in many conflict resolution options.
    Is there a way to run zypper dup with automatic conflict resolution (i.e. it will complete by itself)?
    IMHO zypper does ask for human intervention because it does not "know" what to do. What then should the "automatics" you ask for do?

    However, if you have read the man page, you have found the -n --non-interactive global otion. What the result will be when zypper has to answer a question about breaking your system yes, no, maybe, I don;t know.

    I think a better question would be: "Why do I get so many conflicts"?
    Henk van Velden

  3. #3
    Join Date
    Apr 2016
    Location
    North America
    Posts
    525

    Default Re: zypper dup with automatic conflict resolution

    Thanks :-]

    I assume your question requires more thought than this,
    but I would have the automatic method upgrade anything it can
    which will not result in conflict / breaking anything.

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

    Default Re: zypper dup with automatic conflict resolution

    Quote Originally Posted by ravas View Post
    Thanks :-]

    I assume your question requires more thought than this,
    but I would have the automatic method upgrade anything it can
    which will not result in conflict / breaking anything.
    It is not just an upgrade (in zypper terms), but a distribution upgrade.

    The first is done very regulary (some do it daily) by many users of the non-Tumbleweed versions of openSUSE without any problems. And thus often automaticaly.

    You chose for Tumbleweed. And that requires a bit more knowledge about how to manage repos and what a distribution update might run into.

    Again, I invite you to ask for help with your conflicts. E.g. by posting at least one or two of them, completing that with your repo list. Then people can start studying it. At the moment there is nothing.
    Henk van Velden

  5. #5
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,267
    Blog Entries
    1

    Default Re: zypper dup with automatic conflict resolution

    Along with Henk's advice, you should probably show us your configured repo list
    Code:
    zypper lr -d

  6. #6
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,267
    Blog Entries
    1

    Default Re: zypper dup with automatic conflict resolution

    Quote Originally Posted by hcvv View Post
    Again, I invite you to ask for help with your conflicts. E.g. by posting at least one or two of them, completing that with your repo list. Then people can start studying it. At the moment there is nothing.
    Sorry Henk, missed this request. Yes, the OP needs to provide the relevant info in order to help progress this.

  7. #7
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    19,768
    Blog Entries
    14

    Default Re: zypper dup with automatic conflict resolution

    Quote Originally Posted by ravas View Post
    My latest attempt to run 'zypper dup' results in many conflict resolution options.
    Is there a way to run zypper dup with automatic conflict resolution (i.e. it will complete by itself)?
    Assuming you use the Packman repo as well ( or any other than the tumbleweed repos ), use
    Code:
    zypper dup --no-allow-vendor-change
    This advice was given on the factory ML.
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  8. #8
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,486
    Blog Entries
    3

    Default Re: zypper dup with automatic conflict resolution

    As others have suggested, first check whether you have some strange repos.

    If you only have standard repos, then:

    Yast --> Software Management.

    Select the "Package Groups" view.

    Click on "orphaned packages". (Maybe also look at "unneeded packages").

    In my experience, conflicts often involve orphaned packages that probably should be removed. But you might also get conflicts when you try to remove orphaned packages. Some cleanup of old packages usually helps.

    I should add that an "orphaned package" is a package that is not found in any enabled repo. There might be some of those that you still want. But some of them are just outdated packages that are no longer supported or needed.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  9. #9
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,982

    Default Re: zypper dup with automatic conflict resolution

    Quote Originally Posted by Knurpht View Post
    Code:
    zypper dup --no-allow-vendor-change
    Just curious.

    I can not find this option in my 13.1 man zypper (but it may be in newer openSUSE versions), thus I am unable to read the exact details. But what is the difference between the above and a
    Code:
    zypper up
    I always had the idea that the main difference between "up" and "dup" is the Vendor change. So what is the idea of having "dup" without Vendor change instead of "up"?
    Henk van Velden

  10. #10

    Default Re: zypper dup with automatic conflict resolution

    Quote Originally Posted by hcvv View Post
    I always had the idea that the main difference between "up" and "dup" is the Vendor change. So what is the idea of having "dup" without Vendor change instead of "up"?
    The main differences (other than vendor change) I know of:
    - dup will also downgrade packages, it will always install the latest version available in the repo(s), even if it is a lower version
    - it will remove packages dropped from the distribution automatically
    - it tries harder to solve conflicts automatically I think

    And yes, that --no-allow-vendor-change option has only been added a few months ago, it is probably not available in 13.1 (an update that contains it has been released for 13.2, but I don't know about 13.1).
    The man page just says this:
    Code:
               --[no-]allow-vendor-change
                   Whether to allow changing the vendor of installed resolvables
                   [yes]. Setting this to no might be useful if you do not want
                   packages from foreign repos being dup’ed to the distributions
                   version (or vice versa ).
    Last edited by wolfi323; 05-Sep-2016 at 08:17.

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
  •