zypper dup warns: Make sure these repositories are compatible

OK so I do a:

zypper ref
zypper dup

The first thing the “zypper dup” said was:

[quote]Warning: You are about to do a distribution upgrade with all enabled repositories.
Make sure these repositories are compatible before you continue./quote

Amongst the things it said was:

The following packages are going to change vendor:
amarok                          openSUSE -> http://packman.links2linux.de
gstreamer-0_10                  openSUSE -> http://packman.links2linux.de
gstreamer-0_10-plugin-esd       openSUSE -> http://packman.links2linux.de
gstreamer-0_10-plugin-gnomevfs  openSUSE -> http://packman.links2linux.de
gstreamer-0_10-plugins-bad      http://packman.links2linux.de -> openSUSE
libgstapp-0_10-0                openSUSE -> http://packman.links2linux.de
libgstinterfaces-0_10-0         openSUSE -> http://packman.links2linux.de
libgstreamer-0_10-0             openSUSE -> http://packman.links2linux.de
libgstreamer-0_10-0-32bit       openSUSE -> http://packman.links2linux.de
libstrigi0                      openSUSE -> http://packman.links2linux.de
libxine2                        openSUSE -> http://packman.links2linux.de
moc                             openSUSE -> http://packman.links2linux.de
strigi                          openSUSE -> http://packman.links2linux.de
xine-ui                         openSUSE -> http://packman.links2linux.de

And incidently my configured repos are:

#  | Alias                     | Name                               | Enabled | Refresh
---+---------------------------+------------------------------------+---------+--------
1 | e17-12.2                  | Enlightenment Nightly 12.2         | Yes     | No
2 | libdvdcss                 | DVD Repository                     | Yes     | No
3 | packman                   | Packman repository (openSUSE_12.2) | Yes     | No
4 | repo-debug                | openSUSE-12.2-Debug                | No      | Yes
5 | repo-debug-update         | openSUSE-12.2-Update-Debug         | No      | Yes
6 | repo-debug-update-non-oss | openSUSE-12.2-Update-Debug-Non-Oss | No      | Yes
7 | repo-non-oss              | openSUSE-12.2-Non-Oss              | Yes     | Yes
8 | repo-oss                  | openSUSE-12.2-Oss                  | Yes     | Yes
9 | repo-source               | openSUSE-12.2-Source               | No      | Yes
10 | repo-update               | openSUSE-12.2-Update               | Yes     | Yes
11 | repo-update-non-oss       | openSUSE-12.2-Update-Non-Oss       | Yes     | Yes 

What I want to know is:

Do I need to worry about the packman repo???

If so, what happens to any installed packages without any other enabled
source if I disable packman for the zypper dup???

I sincerely hope I don’t have to worry about my e17 repo:

http://download.opensuse.org/repositories/X11:/Enlightenment:/Nightly/openSUSE_12.2

Since E17 is my desktop environment. But if I do then my 2nd question {above} would apply to
running “zypper dup” with that one disabled as well…{probably more so in fact}

Suggestions anyone?


JtWdyP

Exactly what are you attempting to do? As the warning reads, dup is a distribution upgrade, not an update. It can also be used to switch repositories. To update your system, use ‘zypper patch’ or ‘zypper update.’

You should enable and refresh packman, also e17

Then apply the switch on e17 then packman

from then on it’s just : zypper up

It would appear that on Oct 17, chief sealth did say:

> Exactly what are you attempting to do? As the warning reads, dup is a
> distribution upgrade, not an update. It can also be used to switch
> repositories. To update your system, use ‘zypper patch’ or ‘zypper
> update.’

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?

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

> You should enable and refresh packman, also e17

they ARE enabled. and I always run ‘zypper ref’ first so I don’t see a
problem with not having them set to auto-refresh…
>
> Then apply the switch on e17 then packman

What switch?


JtWdyP

Switching is done like this
https://dl.dropbox.com/u/10573557/Switcher%20Pics/11.4_packman_switch.png

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
This might be normal. Such is often seen, depending on how you have switched

On 2012-10-17 13:36, caf4926 wrote:
>
> Switching is done like this
> http://tinyurl.com/d47o3l6
>>
>> 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

> This might be normal. Such is often seen, depending on how you have
> switched

Another possibility is firing up yast package manager, select display
packman repo, choose updated installed packages from list if newer
version, see what is then selected to be updated, and if not happy,
click on the preferred version.


Cheers / Saludos,

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

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

> Switching is done like this
> http://tinyurl.com/d47o3l6

I thank you. But I’ve never done well extracting a sequence of actions from
a screen shot of a gui app. I don’t suppose you know how to do this with
zypper???

> > 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

> This might be normal. Such is often seen, depending on how you have switched

Which brings me back to the same underlying question as I started with…

If a package is available from more than one “vendor” how do I know which
one I need to “switch” to. (assuming I can figure switching out in the
first place…)
Seems to me that if the Packman repo is “compatible
for the above, then “zypper dup” would have done that “switching for me”

And since what I have is an E17system with a
few apps from kde, gnome, and xfce mixed in, on which most of the default
vendor selection for most packages were the defaults for a KDE system, I’m
not all that sure that “zypper dup” isn’t appropriate. I just don’t have a
clue if the packman repo is both “compatible” and “stable” enough to
warrant making it the vendor for several multimedia packages.

As far as how I’ve “switched” well I haven’t…

That is I installed from the dvd, which installed as a kde system with
whatever switching defaults that came with… Though I’ve no idea if they
would be appropriate for a system that Never runs either kde
nor gnome. (Though I do use a few applications from them)

I added and/or enabled a couple of repos to get E17 and the multi-media codecs etc…

At this point I’m thinking of mounting my OpenSuSE partition and my usb drive while
running any of the other three Linux distro’s. And then from a root shell:


cd /mnt/opensusepart
tar -czf /mnt/usbdrive/opensuse12_2.tgz --numeric-owner .

Then rebooting into OpenSuSE, and using the “zypper dup” {bigger hammer}

But thanks for the helpful info.


JtWdyP

For packman, based on your earlier list

zypper dup -r 3

> I’m not all that sure that “zypper dup” isn’t appropriate.

others have told you, now i’ll say this one time: ‘zypper dup’ i
wonderful if you are performing a Distribution UPgrade, like from 12.1
to 12.2, or from 12.2 to Tumbleweed, or from yesterday’s Tumbleweed to
today’s Tumbleweed…

using it otherwise is VERY dangerous, and if you kill you system with it
you will be just as irresponsible as the other three or more new folks
who do so every day (afterwards they might say: oh! then why is “zypper
dup” NOT like “apt <something>” <:(

on switching: if you have installed something from somewhere and wish
you could replace it with an install from somewhere else, then you can
switch to the new somewhere by specifying it as the repo to pull from…

zypper up --repo <alias|name|#|URI> [packagename]

i think that is the way to do it with zypper–i almost always use
YaST…see man zypper, and decide for yourself…


dd http://tinyurl.com/DD-Caveat

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

> For packman, based on your earlier list
>
>
> Code:
> --------------------
> zypper dup -r 3
> --------------------

I thank you. Though I’m not so sure that’s quite what I’d want to do to “dup” if I
do ultimately decide to ignore all the strong advice against treating zypper “dup”
like debian’s dist-upgrade option… { yes I think dd is right about the source of
my confusion on it’s function }

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??

Even so, your above example gave me the key to understanding a syntax pattern from
both dd’s last responce and the man zypper doc that I can read when I’m actually
using the OpenSuSE, that is only one of 4 Linux I multiboot on my laptop…

Don’t ask me why the syntax of:


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”

Thanks!

It would appear that on Oct 17, dd did say:

I’m not all that sure that “zypper dup” isn’t appropriate.

others have told you, now i’ll say this one time: ‘zypper dup’ i wonderful if
you are performing a Distribution UPgrade, like from 12.1 to 12.2, or from
12.2 to Tumbleweed, or from yesterday’s Tumbleweed to today’s Tumbleweed…

using it otherwise is VERY dangerous, and if you kill you system with it you
will be just as irresponsible as the other three or more new folks who do so
every day (afterwards they might say: oh! then why is “zypper dup” NOT like
"apt " <:(

I believe you that it’s risky. That’s why I’d have made a tarball to restore from
if I actually did it.

on switching: if you have installed something from somewhere and wish you
could replace it with an install from somewhere else, then you can switch to
the new somewhere by specifying it as the repo to pull from…

zypper up --repo <alias|name|#|URI> [packagename]

i think that is the way to do it with zypper–i almost always use YaST…see
man zypper, and decide for yourself…

Yes! Now that caf4926’s example {above} gave me the key to breaking free of
the nearly terminal brain flatulence that prevented me from understanding that
part of the man document.

There is no doubt that your syntax is correct. And your logic too no doubt… :wink:

If I’m now understanding correctly, then given that:



The following packages are going to change vendor:
amarok                          openSUSE -> http://packman.links2linux.de
gstreamer-0_10                  openSUSE -> http://packman.links2linux.de
gstreamer-0_10-plugin-esd       openSUSE -> http://packman.links2linux.de
gstreamer-0_10-plugin-gnomevfs  openSUSE -> http://packman.links2linux.de
gstreamer-0_10-plugins-bad      http://packman.links2linux.de -> openSUSE
libgstapp-0_10-0                openSUSE -> http://packman.links2linux.de
libgstinterfaces-0_10-0         openSUSE -> http://packman.links2linux.de
libgstreamer-0_10-0             openSUSE -> http://packman.links2linux.de
libgstreamer-0_10-0-32bit       openSUSE -> http://packman.links2linux.de
libstrigi0                      openSUSE -> http://packman.links2linux.de
libxine2                        openSUSE -> http://packman.links2linux.de
moc                             openSUSE -> http://packman.links2linux.de
strigi                          openSUSE -> http://packman.links2linux.de
xine-ui                         openSUSE -> http://packman.links2linux.de

are the same packages that “zypper up” said wouldn’t be updated, would
this perhaps make sense:



zypper up -r packman amarok gstreamer-0_10 gstreamer-0_10-plugin-esd gstreamer-0_10-plugin-gnomevfs \
libgstapp-0_10-0 libgstinterfaces-0_10-0 libgstreamer-0_10-0 libgstreamer-0_10-0-32bit libstrigi0 \
libxine2 moc strigi xine-ui -r openSUSE gstreamer-0_10-plugins-bad 

I’m thinking this would accomplish the same vendor changes that “zypper dup” would
have. Only perhaps with less risk to my system…

If so I would then follow it with a generic “zypper up” to complete the system
update. ???!!!???

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



/home
UnderTree=-> zypper lr
#  | Alias                     | Name                               | Enabled | Refresh
---+---------------------------+------------------------------------+---------+--------
1 | e17-12.2                  | Enlightenment Nightly 12.2         | Yes     | No
2 | libdvdcss                 | DVD Repository                     | Yes     | No
3 | packman                   | Packman repository (openSUSE_12.2) | Yes     | No
4 | repo-debug                | openSUSE-12.2-Debug                | No      | Yes
5 | repo-debug-update         | openSUSE-12.2-Update-Debug         | No      | Yes
6 | repo-debug-update-non-oss | openSUSE-12.2-Update-Debug-Non-Oss | No      | Yes
7 | repo-non-oss              | openSUSE-12.2-Non-Oss              | Yes     | Yes
8 | repo-oss                  | openSUSE-12.2-Oss                  | Yes     | Yes
9 | repo-source               | openSUSE-12.2-Source               | No      | Yes
10 | repo-update               | openSUSE-12.2-Update               | Yes     | Yes
11 | repo-update-non-oss       | openSUSE-12.2-Update-Non-Oss       | Yes     | Yes
/home
UnderTree=-> 

Is “openSUSE” a valid argument to --repo that somehow refers to all 8 of the repos
here listed as # 4 through 11 ??? And if not, then how would I know which repo
“zypper dup” wanted to switch gstreamer-0_10-plugins-bad to???

BTW: Even if the above “zypper up” example is safer than “zypper dup”
I think that it only makes sense to make that tarball first…


JtWdyP

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:


> 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. :slight_smile:

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.


>
>  /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:


%{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)

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.

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.

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

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