Page 3 of 3 FirstFirst 123
Results 21 to 26 of 26

Thread: GCC version 7 to version 8

  1. #21
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    903

    Default Re: GCC version 7 to version 8

    Quote Originally Posted by amelcon View Post
    Thank very much for the explanation; now it makes sense.
    If you are concerned with stale information you may delete those packages and run zypper dup. This will pull them in from current repositories.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

  2. #22
    Join Date
    Dec 2014
    Location
    Cartagena, Spain
    Posts
    17

    Default Re: GCC version 7 to version 8

    Quote Originally Posted by karlmistelberger View Post
    If you are concerned with stale information you may delete those packages and run zypper dup. This will pull them in from current repositories.
    Thanks, this goes back to the previous version.

    A more manual way to revert to the previous version in the official repository is:

    Code:
    zypper install --oldpackage --from openSUSE-Leap-15.0-Oss <Name of package>
    where "openSUSE-Leap-15.0-Oss" must be the name you have for the official
    repository.

    So now all packages are back to normal.
    Thanks again.

  3. #23
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    903

    Default Re: GCC version 7 to version 8

    Quote Originally Posted by amelcon View Post
    So now all packages are back to normal.
    You may want to add zypper verify.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

  4. #24
    Join Date
    Dec 2014
    Location
    Cartagena, Spain
    Posts
    17

    Default Re: GCC version 7 to version 8

    Quote Originally Posted by karlmistelberger View Post
    You may want to add zypper verify.

    Nice one, thank you:

    Code:
    zypper verify
    The output:

    Retrieving repository 'Packman' metadata .................................[done]
    Building repository 'Packman' cache ......................................[done]
    Retrieving repository 'openSUSE-Leap-15.0-Update' metadata ...............[done]
    Building repository 'openSUSE-Leap-15.0-Update' cache ....................[done]
    Loading repository data...
    Reading installed packages...

    Dependencies of all installed packages are satisfied.
    Thanks.

  5. #25

    Default Re: GCC version 7 to version 8

    On 4/10/19 8:16 AM, dcurtisfra wrote:
    >
    > nrickert;2899418 Wrote:
    >> it tells me that it wants to downgrade those gcc7 related packages.

    > I've noticed just now that, YaST, when it marks packages with the colour
    > red, currently doesn't downgrade them – I seem to recall that, it used
    > to – possibly, only with a Repository change – for example from
    > Packman to openSUSE …
    >
    >


    It's my understanding that packages showing 'red' in YaST package
    management means that the package no longer belongs to any configured
    repo. Therefore it cannot be upgraded or downgraded, it needs to be
    replaced.

    --
    Ken
    unix since 1986
    S.u.S.E.-openSUSE since 1998


  6. #26
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    2,478

    Default Re: GCC version 7 to version 8

    Quote Originally Posted by kensch View Post
    It's my understanding that packages showing 'red' in YaST package management means that the package no longer belongs to any configured repo. Therefore it cannot be upgraded or downgraded, it needs to be replaced.
    Checked it a couple of minutes ago:
    • “blue”: update available – don't know if a patch is the same colour – it's the libtirpc update (openSUSE-2019-1188).
    • “red”: downgrade – from YaST software, forcibly update to apply the downgrade – it's some FFmpeg libraries from Packman which had their newest versions pulled from the repository …

Page 3 of 3 FirstFirst 123

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
  •