Anybody else had the above? Should I just go ahead and resolve the dependency issues manually in Yast (which involves downgrading one or two components), or ignore the update altogether (it’s 11.2 time soon anyway…)?
Bump, can’t believe no one else had this…
Why don’t you list your repositories (zypper lr -u).
gminnerup wrote:
> Bump, can’t believe no one else had this…
maybe i’m dumb one, but your subject line doesn’t give me enough
hints to know where to begin…
what is the “1130.noarch” package you are trying/wanting/needing to
install?? and, from which repo?
i’m forced to ask because, for example, a google returns
<quote> Results 1 - 2 of 2 for “1130.noarch”.<end quote>
both of which gives ZERO new info since both point to your thread…
i am sure you intended your question to be complete, and i’m sure it
is easy for you to understand–but for the more simple minded around
you might read and think on: http://is.gd/2BfI3
–
platinum
Sorry, you’re right of course: I asked a fuller version a week or so ago and there were no takers, but that doesn’t excuse this one.
It concerns a Yast2 upgrade, from the Update repo, that I was offered a week or so ago, and the error message in the title appears when I try to install it. This is openSUSE 11.1, KDE 4.3.1.
Voila:
# | Alias | Name | Enabled | Refresh | URI
---+----------------------+---------------------------------------+---------+---------+---------------------------------------------------------------------------------------------------
1 | 20090729-225941 | 20090729-225941 | Yes | Yes | http://download.opensuse.org/repositories/server%3a/php%3a/applications/openSUSE_11.1/
2 | KDE4_Factory | KDE4 Factory | Yes | Yes | http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openSUSE_11.1/
3 | KDE4_Factory_Desktop | KDE4 Factory Desktop | Yes | Yes | http://download.opensuse.org/repositories/KDE:/KDE4:/Community/openSUSE_11.1_KDE4_Factory_Desktop/
4 | OpenOffice | OpenOffice | Yes | Yes | http://download.opensuse.org/repositories/OpenOffice.org:/STABLE/openSUSE_11.1/
5 | YaST_autoclose_fix | YaST autoclose fix | No | No | http://download.opensuse.org/repositories/home://lslezak/openSUSE_11.1/
6 | multimedia:photo | multimedia:photo | Yes | Yes | http://download.opensuse.org/repositories/multimedia:/photo/openSUSE_11.1/
7 | repo | openSUSE Education | Yes | Yes | http://www.opensuse-education.org/download/repo/1.0/11.1
8 | repo-non-oss | openSUSE-11.1-Non-Oss | Yes | Yes | http://download.opensuse.org/distribution/11.1/repo/non-oss/
9 | repo-oss | openSUSE-11.1-Oss | Yes | Yes | http://download.opensuse.org/distribution/11.1/repo/oss/
10 | repo-update | openSUSE-11.1-Update | Yes | Yes | http://download.opensuse.org/update/11.1/
11 | repo_15 | openSUSE BuildService - Mozilla | Yes | Yes | http://download.opensuse.org/repositories/mozilla/openSUSE_11.1/
12 | repo_21 | Packman Repository | Yes | Yes | http://ftp.skynet.be/pub/packman/suse/11.1/
13 | repo_6 | openSUSE BuildService - KDE:Community | Yes | Yes | http://download.opensuse.org/repositories/KDE:/Community/openSUSE_11.1/
i’ve just looked at your results from the “zypper lr -u” and kindly
direct your attention to the numerous places on opensuse.org in which
it clearly states that you should generally restrict enabled repos to
a specific four only…to do otherwise is a huge and open invitation
to a broken system…
here is one many wiki or forum discussions on that subject:
many more can be found using the forum search page…
i believe if you disable all but the four recommended repos the
‘problem’ you seek to resolve in this thread will go away…
–
platinum
There’s no point arguing about beliefs. But beliefs don’t explain the conflict between the two versions of Yast2…
As to the repos: They all have a purpose, mainly to do with newer versions of KDE4 and OpenOffice.
What’s this “YaST_autoclose_fix?” It’s disabled now, but it appears at some point you’ve updated Yast through the OBS. Is this right?
Well for one, how are you getting a Yast2-noarch package in the first place? All I can get are all i586 packages. Go into Yast Software manager and search for Yast. Find the Yast2 that you currently have installed and see where you have it installed from. If it is from that Autoclose fix repository then that’s why you’re getting the error message. Obviously you can’t have two versions of Yast2 installed at the same time so it’s asking you which version you want, the updated Yast2 i586 version or the one you currently have installed (the noarch version).
I would highly advise using the i586 version as this version comes from the update repository, an officially supported repository.
Take Care,
Ian
> There’s no point arguing about beliefs. But beliefs don’t explain the
> conflict between the two versions of Yast2…
have it your way…but, if you update YaST from two different sources
then there will, of course, be conflicts…
–
platinum
Yup, it was the autoclose fix thing (which never worked anyway). All updated to latest i586 Yast and sorted now. Thanks everyone.
am happy you got it sorted…
–
platinum
Cough
Most of the packages for YaST are “noarch” (and it’s not only translation stuff).
compared to
Me too
And I am aware of the risks of too many repos, learnt that lesson some time ago. But those I still have do serve a purpose - for example, running properly functioning versions of KDE4 rather than the one that originally came with 11.1 - so I don’t think you can say never more than the standard OSS ones. None of this, of course, excuses the oversight re the Yast fix…
gminnerup wrote:
> so I don’t think you can say never more
> than the standard OSS ones.
you are correct…on the other hand are you certain you want
everything introduced into all those other repos before you have had
the chance to see if it breaks other folks’ systems?
i prefer stability and predictability over bleeding edge…
ymmv
–
platinum
Right, that’s all nice and good but the actual Yast2 package?
http://www.fileden.com/files/2007/7/24/1293578/Yast2_thumb.png](http://www.fileden.com/files/2007/7/24/1293578/Yast2.png)
That’s what I meant by all I can get are all i586 packages.
Take Care,
Ian