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

Thread: 2000+ packages update

  1. #1

    Question 2000+ packages update

    Hi.
    Since weeks I have a huge update with more than 2000 packages and yast2 makes me questions I dont know how to answer or decide.
    I dont know what to do, maybe a fresh install?. Please give me some advice about this.
    Thanks in advance.

  2. #2
    Join Date
    May 2015
    Location
    Italy
    Posts
    234

    Default Re: 2000+ packages update

    Hi tech_bot,
    how can we help you if you don't show us the questions that you don't know how to answer?

    Cris
    Desktop: OpenSUSE Tumbleweed (x86_64) - AMD FX-8350 Eight-Core Processor, 8Gb RAM, 120GB Samsung Evo 840 SSD
    Laptop: OpenSUSE Tumbleweed (x86_64) - Thinkpad T440 - Intel i5-4210U, 12Gb RAM, 250GB Samsung EVO 750 SSD

  3. #3
    Join Date
    Mar 2015
    Location
    Viçosa, Brasil
    Posts
    138

    Default Re: 2000+ packages update

    I not using tumbleweed anymore but as far as I remember usually have these huge updates. You don't need to do a fresh install.
    --
    openSUSE | EcoLab Spin
    https://github.com/ViniciusBRodrigues/openSUSE-EcoLab

  4. #4

    Default Re: 2000+ packages update

    Quote Originally Posted by tech_bot View Post
    Hi.
    Since weeks I have a huge update with more than 2000 packages and yast2 makes me questions I dont know how to answer or decide.
    I dont know what to do, maybe a fresh install?. Please give me some advice about this.
    Run "zypper dup --no-allow-vendor-change", that's the recommended and preferred way to update Tumbleweed.
    If that still asks you questions you cannot answer, feel free to post them for further help.

    Regarding the "huge update": the distribution was/had to be completely rebuilt recently because the default compiler was switched to GCC7.
    That's life with Tumbleweed (or any rolling distribution)...

  5. #5

    Default Re: 2000+ packages update

    Thanks to all for the quick responses.
    Maybe that switch to GCC7 is the reason but after, maybe, 5 months is the first time it happens to me.
    I did the question that way cause I thought it happened to more users. What is missing? The yast's questions are like choose between several options about install that or this package, not to install this and yes that other... etc; but to much questions to be writen here because until I dont answer one I dont get the next .
    Il'l try when return home that update with zypper.
    Many thanks again.

  6. #6
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    21,433

    Default Re: 2000+ packages update

    Quote Originally Posted by tech_bot View Post
    Thanks to all for the quick responses.
    Maybe that switch to GCC7 is the reason but after, maybe, 5 months is the first time it happens to me.
    I did the question that way cause I thought it happened to more users. What is missing? The yast's questions are like choose between several options about install that or this package, not to install this and yes that other... etc; but to much questions to be writen here because until I dont answer one I dont get the next .
    Il'l try when return home that update with zypper.
    Many thanks again.
    As there is no simple equivalent with YaST for
    Code:
    zypper dup --no-allow-vendor-change
    I do not think people here are interested in what YaST said, whatever you were doing with it (you did not even explain that). But as said, when you get errors with the zypper statement shown, please post. And when it still is a long list, please post at least the first 20-30 lines or so. We can not help on "story telling" alone. We need computer facts.
    Henk van Velden

  7. #7
    Join Date
    Jan 2016
    Location
    Manchester, UK
    Posts
    208

    Default Re: 2000+ packages update

    Hi, tech_bot,

    You're right about the reason of the huge number of packages to be updated. 2000+ is normal. It's because of GCC7. And you could read more on this in this thread of mailing list: https://lists.opensuse.org/opensuse-.../msg00015.html

    As for the selections, if you don't know for sure, you could run the command,
    Code:
    sudo zypper dup --no-allow-vendor-change
    as suggested previously by @wolfi323 and @hcvv, in command line such as in Konsole under KDE environment, so that you can easily copy the output here for further help. For example,

    Code:
    cnzhx@a:~> sudo zypper dup --no-allow-vendor-change
    [sudo] password for root: 
    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.
    Retrieving repository 'M17N_Fonts' metadata ..........................................................[done]
    Building repository 'M17N_Fonts' cache ...............................................................[done]
    Retrieving repository 'packman' metadata .............................................................[done]
    Building repository 'packman' cache ..................................................................[done]
    Retrieving repository 'openSUSE-Tumbleweed-Non-Oss' metadata .........................................[done]
    Building repository 'openSUSE-Tumbleweed-Non-Oss' cache ..............................................[done]
    Retrieving repository 'openSUSE-Tumbleweed-Oss' metadata .............................................[done]
    Building repository 'openSUSE-Tumbleweed-Oss' cache ..................................................[done]
    Retrieving repository 'openSUSE-Tumbleweed-Update' metadata ..........................................[done]
    Building repository 'openSUSE-Tumbleweed-Update' cache ...............................................[done]
    Loading repository data...
    Reading installed packages...
    Computing distribution upgrade...
    2 Problems:
    Problem: problem with installed package dkms-2.3-4.1.noarch
    Problem: problem with installed package liba52-0-0.7.5+svn613-1.27.x86_64
    
    Problem: problem with installed package dkms-2.3-4.1.noarch
     Solution 1: install dkms-2.3-1.1.noarch (with vendor change)
      http://packman.links2linux.de  -->  openSUSE
    
    Choose the above solution using '1' or skip, retry or cancel [1/s/r/c] (c):
    I am sure you could get specific help on this issue by presenting it like this.

    IF I choose option "1" for the first problem, I get,
    Code:
    Choose the above solution using '1' or skip, retry or cancel [1/s/r/c] (c): 1
    
    Problem: problem with installed package liba52-0-0.7.5+svn613-1.27.x86_64
     Solution 1: install liba52-0-0.7.5+svn613-1.2.x86_64 (with vendor change)
      http://packman.links2linux.de  -->  openSUSE
    This is because liba52 is now in the default repositories of openSUSE Tumbleweed instead of packman repo. (Yes, I have delayed my updates for several days for testing purpose and then I have this for this post.)

    Regards,
    CnZhx
    Last edited by cnzhx; 07-Jun-2017 at 09:50. Reason: Use full commands and outputs.
    openSUSE Tumbleweed (usually the latest snapshot) w/ KDE Plasma 5

  8. #8

    Default Re: 2000+ packages update

    Quick question. I'm showing vendor switch for liba52 and libmpg123 from packman to opensuse. Is this going to break encode or decode for media or is this simply a reflection of the mp3 license thing from a few weeks ago? I googled around for some info, but I'm kind of new to suse... I've only been doing "zypper up" for my updates until I saw this thread.

  9. #9
    Join Date
    Nov 2009
    Location
    West Virginia Sector 9
    Posts
    14,166

    Default Re: 2000+ packages update

    No the mp3 codec patents have expired and now can legally be included as open source so can now be included in openSUSE

  10. #10
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    15,716
    Blog Entries
    1

    Default Re: 2000+ packages update

    Quote Originally Posted by exdevnull View Post
    Quick question. I'm showing vendor switch for liba52 and libmpg123 from packman to opensuse. Is this going to break encode or decode for media or is this simply a reflection of the mp3 license thing from a few weeks ago?
    Yes to the latter.

    I googled around for some info, but I'm kind of new to suse... I've only been doing "zypper up" for my updates until I saw this thread.
    Accept the changes. It's already been mentioned here...

    https://forums.opensuse.org/showthre...50#post2824750

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
  •