Page 2 of 2 FirstFirst 12
Results 11 to 15 of 15

Thread: zypper dup warns: Make sure these repositories are compatible

  1. #11
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: zypper dup warns: Make sure these repositories are compatible

    On 2012-10-17 23:42, JtWdyP wrote:

    > But whereas "zypper dup" wanted to change vendor on only 14 packages {and only 13
    > of them changing to packman, wouldn't "zypper dup -r 3" try to
    > change vendor on ALL packages??


    I think so, yes.

    > Don't ask me why the syntax of:
    Code:
    > zypper up --repo <alias|name|#|URI> [packagename]
    >
    confused me. But it wasn't until I saw your example that I figured out
    > that the "<alias|name|#|URI>" actually 4 different ways of specifying "which repo"


    Ah, yes, that's typical Linux man parlance. :-)

    But I think that's the optimal way to change packages vendor with
    zypper. Me, I use YaST, less work.

    > One thing bothers me with the above, the "zypper dup" list refers to a vendor as
    > "openSUSE" Yet considering :


    "Vendor" can not be related directly to a repo name or alias. I find it
    with an rpm query.


    Code:
    
    >
    >  /home
    > UnderTree=-> zypper lr
    > #  | Alias                     | Name                               | Enabled | Refresh
    > ---+---------------------------+------------------------------------+---------+--------
    >  1 | e17-12.2                  | Enlightenment Nightly 12.2         | Yes     | No
    >  2 | libdvdcss                 | DVD Repository                     | Yes     | No
    For example, the vendor for package "libdvdcss2" is shown here:

    Code:
    %{VENDOR};%{PACKAGER};%{DISTRIBUTION};%{DISTTAG}
    http://packman.links2linux.de;
    packman@links2linux.de;
    Essentials / Factory;
    (none)
    It might be an rpm field, not a repository token.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 12.1 x86_64 "Asparagus" at Telcontar)

  2. #12

    Default Re: zypper dup warns: Make sure these repositories are compatible

    jtwdyp@no-mx.forums.opensuse.org wrote:
    > That's where I started... but when I run 'zypper up' I get this:
    >
    > The following package updates will NOT be installed:
    > amarok gstreamer-0_10 gstreamer-0_10-plugin-esd gstreamer-0_10-plugin-gnomevfs gstreamer-0_10-plugins-base
    > gstreamer-0_10-plugins-good k3b libgstapp-0_10-0 libgstinterfaces-0_10-0 libgstreamer-0_10-0
    > libgstreamer-0_10-0-32bit libstrigi0 libxine2 libxine2-pulse moc strigi xine-ui
    >
    > So if I'm supposed toavoid 'zypper dup', how do I get those to update?


    You can try to run 'zypper in' on the packages that are not installing.
    For example, I get the same amarok will NOT be installed. If I run:

    zypper in amarok

    I get:
    ---------------------
    There is an update candidate for 'amarok', but it is from different
    vendor. Use 'zypper install amarok-2.6.0-175.2.x86_64' to install this
    candidate.
    ---------------------
    If I then run:

    zypper install amarok-2.6.0-175.2.x86_64

    I get:
    ---------------------
    The following package is going to be upgraded:
    amarok

    The following package is going to change vendor:
    amarok http://packman.links2linux.de -> obs://build.opensuse.org/KDE


    1 package to upgrade, 1 to change vendor.
    Overall download size: 15.7 MiB. After the operation, 1.1 MiB will be freed.
    ---------------------

    You can try with several at a time and it also works.


  3. #13
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,733
    Blog Entries
    20

    Default Re: zypper dup warns: Make sure these repositories are compatible

    Repos 1, 2, 3 are non-standard (but repo 2 can be pretty much ignored once you have installed libdvdcss)

    So, typically, when you add a repo for a collective installation, rather than for an individual package. It should be switched to.
    So in your case, you should switch to e17 and lastly to packman
    Once this is done, updates are simply: zypper up

    *repos might be added at times to supply an individual package, for point of example, lets say 'dropbox', and so we would add the repo, install dropbox, then disable the repo, especially if the repo contains other packages that might be yet another example of those we already have.
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

  4. #14

    Default Re: zypper dup warns: Make sure these repositories are compatible


    It would appear that on Oct 18, caf4926 did say:

    > Repos 1, 2, 3 are non-standard (but repo 2 can be pretty much ignored
    > once you have installed libdvdcss)
    >
    > So, typically, when you add a repo for a collective installation,
    > rather than for an individual package. It should be switched to.
    > So in your case, you should switch to e17 and lastly to packman
    > Once this is done, updates are simply: zypper up


    So then If I understand. When you say "switched to" you are talking about
    changing the vendor of all the packages in a repo to the vendor associated
    with said repo... The way you would do this is to select the software
    management tool in yast2. Set the view to repos. set the secondary view to
    "all packages" then click on the vendor change tool. And assuming no
    errors, you would then accept the changes... Right?

    And you are suggesting That I should consider switching the vendor of the
    packages in the e17 repo to that repo's vendor. Then repeat the process
    with packman {which sequence should, I think, result in any package found
    in both the e17 AND packman repos ultimately having it's vendor switched to
    packman...} How am I doing so far?


    > *repos might be added at times to supply an individual package, for
    > point of example, lets say 'dropbox', and so we would add the repo,
    > install dropbox, then disable the repo, especially if the repo contains
    > other packages that might be yet another example of those we already
    > have.


    So you think I should disable repo # 2 ???

    --
    JtWdyP


  5. #15
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,733
    Blog Entries
    20

    Default Re: zypper dup warns: Make sure these repositories are compatible

    Yes
    Yes
    No. It only contains libdvdcss so once installed that's fine, no other repos provide it (well VideoLan does, but we recommend NOT using that), so no switching is needed. But it's not really necessary to keep it on, just check it from time to time or if you have trouble with dvds
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

Page 2 of 2 FirstFirst 12

Posting Permissions

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