I just did a fresh install of 11.1 with KDE. The first thing I tried after the virgin install was to upgrade KDE to 4.2.4. I used the 1-click install. I got two dependency errors saying that the dependent file wasn’t available and I got 3 options to either downgrade a bunch of other files, ingnore the dependency or not to install the file. I know that this is a bit of an open question but generally what is the best approach? to downgrade or ignore. I assume by not installing the file you’ll break the installation of the app you were trying to install.
I seem to get this quite often when installing apps generally.
suse tpx60s adjusted his/her AFDB on Wednesday 10 Jun 2009 17:36 to write:
>
> I just did a fresh install of 11.1 with KDE. The first thing I tried
> after the virgin install was to upgrade KDE to 4.2.4. I used the 1-click
> install. I got two dependency errors saying that the dependent file
> wasn’t available and I got 3 options to either downgrade a bunch of
> other files, ingnore the dependency or not to install the file. I know
> that this is a bit of an open question but generally what is the best
> approach? to downgrade or ignore. I assume by not installing the file
> you’ll break the installation of the app you were trying to install.
>
> I seem to get this quite often when installing apps generally.
>
>
This is the big question…
It depends on loads of things like which file you are updating, what the dep
is, and the versions of the files you have on the system.
One of the common probs is that the app you are updating has a dep in it for
only say lib-blah.3.2 and your installed one might be lib-blah.3.2.1 now
because the app states ONLY 3.2 and not version greater than it will throw
an error and say that deps are not met.
The choice there is do you upgrade and find it works fine ( ignore the dep )
which will work 90 odd % of the time.
The other thing to take into account is what does the file do?
Now if it was a major system file you would need to investigate more as it
could take the whole system down ( very unlikely but it could )
So you need a bit of judgement, experience and sometimes just a good guess
at what to do.
Dont forget that you can always get the old version back using YaST, or the commandline version of YaST if a GUI dont start because of the update.
But if it breaks YaST then it gets a lot more “Interesting” ™
If you need help at what to do then post the output from the update so we
can see which will be the best thing.
HTH
–
Mark
Nullus in verba
Nil illegitimi carborundum
Thanks. As an inexperienced user I have no clue what the file actually is or would do. To me lib-blah doesn’t mean anything so it would be a pure pot luck decision on my part on what to do.
What I can’t figure is I tried to do the KDE4.2.4 update from the Suse repository on a virgin install of Suse KDE4.1 so I would have expected there to be no dependency issues. Hasn’t everyone else upgrading come across the same problem?
Nest time I 'll post the files and ask for help.
suse tpx60s adjusted his/her AFDB on Wednesday 10 Jun 2009 20:46 to write:
>
> Thanks. As an inexperienced user I have no clue what the file actually
> is or would do. To me lib-blah doesn’t mean anything so it would be a
> pure pot luck decision on my part on what to do.
>
> What I can’t figure is I tried to do the KDE4.2.4 update from the Suse
> repository on a virgin install of Suse KDE4.1 so I would have expected
> there to be no dependency issues. Hasn’t everyone else upgrading come
> across the same problem?
I do not use one-click so no expert there but I have just updated using the
repo`s and YaST ( I use Yast because zypper will not select some apps due to
deps ) there were a few deps that where not met but by looking at the
messages I could see that the reason was that some apps needed a specific
version number of which I had newer versions so I just ignored them by using
the ignore option.
Had no probs “yet”*
>
> Nest time I 'll post the files and ask for help.
>
>
Yep just holler someone will help.
–
Mark
Nullus in verba
Nil illegitimi carborundum