Results 1 to 9 of 9

Thread: zypper dup default behavior changed: what is the difference to zypper up?

  1. #1
    Join Date
    Oct 2009
    Location
    Germany
    Posts
    518

    Default zypper dup default behavior changed: what is the difference to zypper up?

    Hi,
    in view of the recent change in the default behavior of zypper dup:

    what is the difference between:
    Code:
    zypper dup --no-allow-vendor-change
    and
    Code:
    zypper up
    ?

  2. #2
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,925
    Blog Entries
    14

    Default Re: zypper dup default behavior changed: what is the difference to zypper up?

    TW is rolling. The technique to do this is to release TW over and over again. Any updates go through openQA, when succesful a new TW is released. Hence 'zypper dup' ( the no-allow-vendor-change is default now ), and not zypper up. The latter would ignore downgrades f.e., where dup respects them.
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  3. #3
    Join Date
    Sep 2012
    Posts
    7,105

    Default Re: zypper dup default behavior changed: what is the difference to zypper up?

    "zypper dup" will automatically downgrade when needed; "zypper up" won't. Also "zypper dup" may delete packages which are marked for removal in global configuration; "zypper up" won't (it can remove packages as result of explicit Obsolete directive though).

  4. #4
    Join Date
    Oct 2011
    Location
    Germany (Ore Mountains)
    Posts
    459

    Default Re: zypper dup default behavior changed: what is the difference to zypper up?

    When the "new" zypper dup can solve a problem only with a vendor change, it asks instead of just doing it:
    Code:
    Loading repository data...
    Reading installed packages...
    Computing distribution upgrade...
    Force resolution: No
    Computing upgrade...
    4 Problems:
    Problem: problem with installed package libowncloudsync0-2.3.2-1.5.i586
    Problem: problem with installed package libqt5keychain1-0.7.0-9.13.i586
    Problem: problem with installed package owncloud-client-2.3.2-1.5.i586
    Problem: problem with installed package owncloud-client-l10n-2.3.2-1.5.i586
    
    Problem: problem with installed package libowncloudsync0-2.3.2-1.5.i586
     Solution 1: install libowncloudsync0-2.3.2-1.4.i586 (with vendor change)
      obs://build.opensuse.org/isv:ownCloud  -->  openSUSE
    
    Choose the above solution using '1' or skip, retry or cancel [1/s/r/c] (c):

  5. #5
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,811

    Default Re: zypper dup default behavior changed: what is the difference to zypper up?

    Please always copy/paste complete from your terminal window: the prompt, the command, the output and the next prompt. Now we have only the output. Thus we can not know for sure what you did.
    Henk van Velden

  6. #6
    Join Date
    Oct 2011
    Location
    Germany (Ore Mountains)
    Posts
    459

    Default Re: zypper dup default behavior changed: what is the difference to zypper up?

    Quote Originally Posted by hcvv View Post
    Please always copy/paste complete from your terminal window: the prompt, the command, the output and the next prompt. Now we have only the output. Thus we can not know for sure what you did.
    You are right.

    Code:
    schlepptop:/home/hendrik # LANG=en zypper -v dup
    Verbosity: 1
    Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
    Initializing Target
    Checking whether to refresh metadata for Packman
    Retrieving: repomd.xml ...........................................................................................................................[done]
    Checking whether to refresh metadata for home:hendwolt
    Retrieving: repomd.xml ...........................................................................................................................[done]
    Checking whether to refresh metadata for mozilla
    Retrieving: repomd.xml ...........................................................................................................................[done]
    Checking whether to refresh metadata for openSUSE-20170219-0
    Retrieving: content ..............................................................................................................................[done]
    Retrieving: media ................................................................................................................................[done]
    Checking whether to refresh metadata for openSUSE-Tumbleweed-Non-Oss
    Retrieving: content ..............................................................................................................................[done]
    Retrieving: media ................................................................................................................................[done]
    Checking whether to refresh metadata for openSUSE-Tumbleweed-Update
    Retrieving: repomd.xml .................................................................................................................[done (371 B/s)]
    Loading repository data...
    Reading installed packages...
    Computing distribution upgrade...
    Force resolution: No
    Computing upgrade...
    4 Problems:
    Problem: problem with installed package libowncloudsync0-2.3.2-1.5.i586
    Problem: problem with installed package libqt5keychain1-0.7.0-9.13.i586
    Problem: problem with installed package owncloud-client-2.3.2-1.5.i586
    Problem: problem with installed package owncloud-client-l10n-2.3.2-1.5.i586
    
    Problem: problem with installed package libowncloudsync0-2.3.2-1.5.i586
     Solution 1: install libowncloudsync0-2.3.2-1.4.i586 (with vendor change)
      obs://build.opensuse.org/isv:ownCloud  -->  openSUSE
    
    Choose the above solution using '1' or skip, retry or cancel [1/s/r/c] (c): 1
    FYI: There was problem with the original owncloud repository, I used to use in the past. I removed it now, causing this downgrade.

    My point was to illustrate the way, zypper handles such situations now, and not to ask for help.
    Sorry for the confusion.

    Hendrik

  7. #7
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,811

    Default Re: zypper dup default behavior changed: what is the difference to zypper up?

    Thanks for the full output.

    It may be that you do not ask for help (because you know how to handle this), but nevertheless in my opinion it is a good question.

    A possibility I see is that the change of the default for TW was introduced some time ago (one month, two months, maybe more?). As long as you do not have that update, it will still be the old situation.
    I assume you weren't that much behind in updating, but I see it as a possibility.
    Henk van Velden

  8. #8

    Default Re: zypper dup default behavior changed: what is the difference to zypper up?

    after years of using zypper , I came to conclusion that zypper up is safer and zypper dup is a NO to use unless no choice.

    some people said no different between zypper dup or zypper up which is wrong . the best example is when kernel update.

    zypper dup
    -kernel update will show up first in zypper dup
    -you may see only the kernel module show in list.


    zypper up
    - kernel update slow , when it come you will see accompany with huge list others packages update

    if you run zypper dup on kernel update, depend on luck some of services may not run . One of the cause maybe because not compatible with the newest kernel and you may need to recompile or you will have to wait the update pakages show up.


    after hit problem few times , I decide not using zypper dup .

  9. #9
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    32,339
    Blog Entries
    15

    Default Re: zypper dup default behavior changed: what is the difference tozypper up?

    On Mon 23 Oct 2017 02:16:01 AM CDT, kobolds1 wrote:

    after years of using zypper , I came to conclusion that zypper up is
    safer and zypper dup is a NO to use unless no choice.

    some people said no different between zypper dup or zypper up which is
    wrong . the best example is when kernel update.

    _zypper_dup
    _-kernel update will show up first in zypper dup
    -you may see only the kernel module show in list.


    _zypper_up
    _- kernel update slow , when it come you will see accompany with huge
    list others packages update

    if you run zypper dup on kernel update, depend on luck some of services
    may not run . One of the cause maybe because not compatible with the
    newest kernel and you may need to recompile or you will have to wait the
    update pakages show up.


    after hit problem few times , I decide not using zypper dup .


    Hi
    Be aware this thread is about Tumbleweed, the method to update is by
    using dup since it's a new snapshot. At this point it's your choice to
    update or not depending on your requirements. If your running out of
    kernel modules supplied by third parties, then your tied to their
    schedule.... Using zypper up will in the long term create more issues
    as well as not supported.

    --
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    openSUSE Leap 42.2|GNOME 3.20.2|4.4.87-18.29-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!


Posting Permissions

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