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

Thread: I don't get why --allow-vendor-change didn't fully upgrade my system

  1. #1

    Question I don't get why --allow-vendor-change didn't fully upgrade my system

    Hi there !
    I am confused about the behaviour of "--allow-vendor-change".
    I thought it is used to resolve conflicts during update between packages from official repo and from packman, when the same package is available on both.
    But it affect the overall behaviour on dist-upgrade, what was unexpected and I appreciate some clarification on this.
    Follow me, please...
    I was in 20210114 release and today morning I decided to move to 20210121 release using tumbleweed cli, followed by a dist-upgrade with --allow-vendor-change flag
    Code:
    kimera:~ # tumbleweed switch 20210121  
    switching from 20210114 to 20210121? [y/n] (y): y
    kimera:~ # zypper dist-upgrade --from packman --allow-vendor-change
    ...
    
    
    21 packages to upgrade.
    Overall download size: 7.1 MiB. Already cached: 0 B. After the operation, additional 6.8 KiB will be used.
    Continue? [y/n/v/...? shows all options] (y): y
    For my surprise was there is only 21 packages to upgrade since 20210114. This can't be right...
    I repeat "zypper dist-upgrade --from packman --allow-vendor-change" and the message was "Nothing to do."
    Then, I decided to run dist-upgrade without the "--allow-vendor-change" flag and this time I got the expected number of packages to be update.

    Code:
    kimera:~ # zypper dist-upgrade
    Loading repository data...
    Reading installed packages...
    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.
    Computing distribution upgrade...
    
    
    ...
    The following product is going to be upgraded:
      openSUSE Tumbleweed  20210114-0 -> 20210121-0
    
    
    371 packages to upgrade, 155 new, 122 to remove.
    Overall download size: 874.6 MiB. Already cached: 0 B. After the operation, additional 80.2 MiB will be used.
    Continue? [y/n/v/...? shows all options] (y): y
    Then, this time, I notice that I got the message about the opensuse version change that I didn't get before: "openSUSE Tumbleweed 20210114-0 -> 20210121-0"

    Why there was so few packages to be updated when using "--allow-vendor-change" ?
    Why opensuse was not update from "20210114-0" to "20210121-0" when using "--allow-vendor-change" ?
    I guess the last question explain the first. With "--allow-vendor-change" opensuse was not updated to a new release (20210121) and staying on "20210114-0" there was just a few packages on that release to be updated anyway.

    So, looks like the main question is: Why "zypper dist-upgrade --allow-vendor-change" doesn't update the system to "20210121-0" ?
    This looks a bug for me...anyone ?

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,247

    Default Re: I don't get why --allow-vendor-change didn't fully upgrade my system

    When you do
    Code:
    zypper dist-upgrade --from packman --allow-vendor-change
    you restrict the action to the packages that can be found on the packman repository (assuming that the word "packman" here points to an URL of the (or a mirror of the) Packman repository, you did not show your list of repos).
    And I can imgine that 21 packages to update from the Packman repository is quite normal.
    And of course, doing that a second time will result in "nothing to do" because you just did it.

    The standard way of updating your Tumbleweed installation (probably triggered by the fact that here on the forums in the New and Announcements sub-section a new snapshot is announced) is
    Code:
    zypper dup
    Adding --allow-vendor-change is not needed anymore since a long time, because that is the default on Tumbleweed installations (though NOT on LEAP). But it does not hurt either.


    Edit: read the below posts for better information.
    Last edited by hcvv; 29-Jan-2021 at 05:59. Reason: Errors is the post
    Henk van Velden

  3. #3
    Join Date
    Sep 2012
    Posts
    6,842

    Default Re: I don't get why --allow-vendor-change didn't fully upgrade my system

    Quote Originally Posted by hcvv View Post
    Adding --allow-vendor-change is not needed anymore since a long time, because that is the default on Tumbleweed installations
    It is not. Default is to keep vendor.

  4. #4
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,247

    Default Re: I don't get why --allow-vendor-change didn't fully upgrade my system

    Sorry, I think I am very confused with the OP's description. He seems to find things strange that IMHO are quite normal

    To go to a new Tumbleweed snapshot one needs:
    Code:
    zypper dup --no-allow-vendor-change
    But since already some time --no-allow-vendor-change is the default in Tumbleweed installation, it can be left out.

    Another subject.
    To switch packages you may have from the standard OSS/non-OSS repos to the packages with the same name (and improved functionality) that reside on the Packman repo:
    Code:
    zyper dup --from <packman>
    (where <packman> is to be replaced by the #, alias or name of the Packman repo)
    No --allow-vendor-change needed, because that is implicit when you use the --from (else it would be useless).

    I hope this is better.
    Henk van Velden

  5. #5
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,480
    Blog Entries
    3

    Default Re: I don't get why --allow-vendor-change didn't fully upgrade my system

    Quote Originally Posted by marozsas View Post
    For my surprise was there is only 21 packages to upgrade since 20210114. This can't be right...
    I repeat "zypper dist-upgrade --from packman --allow-vendor-change" and the message was "Nothing to do."
    Then, I decided to run dist-upgrade without the "--allow-vendor-change" flag and this time I got the expected number of packages to be update.
    At this point, you should provide your list of repos.
    Code:
    zypper lr -d
    There is probably something that is inhibiting update.

    For example, if you still have the install DVD enabled as a repo, that can inhibit updating of packages from the version that is in the DVD repo.

    Just as a note: I normally use --allow-vendor-change (with a line in "/etc/zypp/zypp.conf"), but I am not seeing what you see.

    I'll add that I do not recommend others allow vendor change. It works for me, because I have carefully set the priorities of the repos to what I need, and I am very careful about which repos I enable.
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

  6. #6
    Join Date
    Feb 2018
    Location
    Romania
    Posts
    484

    Default Re: I don't get why --allow-vendor-change didn't fully upgrade my system

    Hello,

    With
    Code:
    zypper dup
    you will do a distro-upgrade only form "standard" repo (OSS/no-OSS).
    With
    Code:
    zypper dup --from packman --allow-vendor-change
    you will do a distro-upgrade ONLY form "packman" repo. The packages form "standard" repo will not be upgraded.
    Like @hcvv said,
    Code:
    zypper dup --from packman
    is enough. With
    Code:
    zypper dup --from repo
    you do not need "allow-vendor-change" (from what I know, with one exception, when you upgrade form kernel repository).

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

    Default Re: I don't get why --allow-vendor-change didn't fully upgrade my system

    Quote Originally Posted by another_roadrunner View Post
    Hello,

    With
    Code:
    zypper dup
    you will do a distro-upgrade only form "standard" repo (OSS/no-OSS).
    That us not true, You will do it from all enabled repos (in the normal case that includes e.g. Packman and that is what you want: OSS, non-OSS and Packman and maybe others). "Standard repos" is an expression for human consumption, zypper does understand any difference between "standard" and "non-standard" repos.

    That explains also why a
    Code:
    zypper dup
    is enough. It will update from all repos without switching vendors. Thus packages you have from Packman will again be from Packman. No need to do a new switch to Packman afterwards.
    Henk van Velden

  8. #8

    Default Re: I don't get why --allow-vendor-change didn't fully upgrade my system

    [QUOTE=nrickert;3000475]At this point, you should provide your list of repos.
    Code:
    zypper lr -d
    Here is the repos I am using
    Code:
    kimera:~ # zypper lr -d
    #  | Alias              | Name                                                   | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                           |
     Service
    ---+--------------------+--------------------------------------------------------+---------+-----------+---------+----------+--------+-------------------------------------------------------------------------------+
    --------
     1 | Education          | Applications for education users (openSUSE_Tumbleweed) | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | https://download.opensuse.org/repositories/Education/openSUSE_Tumbleweed/     |
      
     2 | Google-Chrome      | Google-Chrome                                          | Yes     | (r ) Yes  | No      |   99     | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64                           |
      
     3 | Tumbleweed-Non-OSS | Tumbleweed-Non-OSS                                     | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/history/20210121/tumbleweed/repo/non-oss/        |
      
     4 | Tumbleweed-OSS     | Tumbleweed-OSS                                         | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/history/20210121/tumbleweed/repo/oss/            |
      
     5 | Tumbleweed-update  | Tumbleweed-update                                      | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | https://download.opensuse.org/update/tumbleweed/                              |
      
     6 | packman            | Packman                                                | Yes     | (r ) Yes  | Yes     |   90     | rpm-md | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/          |
      
     7 | gh-cli             | packages for the GitHub CLI                            | Yes     | (r ) Yes  | No      |   99     | rpm-md | https://cli.github.com/packages/rpm                                           |
      
     8 | nvidia-tumbleweed  | nvidia-tumbleweed                                      | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | https://download.nvidia.com/opensuse/tumbleweed                               |
      
     9 | snappy             | snappy                                                 | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | https://download.opensuse.org/repositories/system:/snappy/openSUSE_Tumbleweed |
      
    10 | vscode             | vscode                                                 | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | https://packages.microsoft.com/yumrepos/vscode                                |
      
    kimera:~ #
    
    

  9. #9

    Default Re: I don't get why --allow-vendor-change didn't fully upgrade my system

    Quote Originally Posted by hcvv View Post
    Sorry, I think I am very confused with the OP's description. He seems to find things strange that IMHO are quite normal

    To go to a new Tumbleweed snapshot one needs:
    Code:
    zypper dup --no-allow-vendor-change
    But since already some time --no-allow-vendor-change is the default in Tumbleweed installation, it can be left out.
    Oh...This is new for me, I mean "To go to a new Tumbleweed snapshot one needs zypper dup --no-allow-vendor-change".
    So, this explain why I didn't get a new snapshot. I was using "--allow-vendor-change" and, according to you, I need to use "--no-allow-vendor-change" or don't use it at all, as I did later !
    Ok, good to know. Explained. Thanks !

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

    Default Re: I don't get why --allow-vendor-change didn't fully upgrade my system

    I'm looking at your repo list.

    It mostly looks okay, so I'm not sure why you are seeing this difference.

    When it next happens, do:
    Code:
    zypper dup --allow-vendor-change -D
    zypper dup -D
    and compare the changes between the two. Then check which repos those packages come from. If the packages that show differently are from "packman" then it probably means that there is a change in the main repo but the packman version has not yet been updated. Or maybe it is a package in that Education repo.

    If I were checking, I would probably use Yast and the "Versions" tab to see what version comes from which repo.
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

Page 1 of 2 12 LastLast

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
  •