Watch out for this repo !

Michael Soibelman · External Since: May 10, 2007 Posts: 123

O.K. I figured this out. Once yesterday and once today I did a Yast
software update. Both times, after completing the update, I could no
longer get yast to start... Now I know what seems to be going on.

It seems that one of the updates was to libicu. The newer version in this
directory:

http://download.opensuse.org/repositories/GNOME:/UNSTABLE/openSUSE_10.2/

is libicu-3.6-3.1.i586.rpm . I had to uninstall this with the 'rpm -e
libicu' command and then re-install an older vrsion I got here:

http://rpm.pbone.net/index.php3/stat/4/idpl/3696393/com/libicu-3.4-34....6.rpm.h

Now yast works... Earlier, not being certain what caused Yast not to run, I
installed 'smart' to fix things.. After that was done (re-installed all
Yast proggies) and smart uninstalled quite a few others, Yast ran again..
Then a Yast software update of 'All Packages with newer versions' resulted
in Yast not working again... Looking at the warnings I got when trying to
launch Yast from a terminal gave this message:

mylinux:/home/mike # yast2
libicui18n.so.34 => not found
libicuuc.so.34 => not found
warning: the qt frontend is installed but does not work
Qt GUI wanted but not found, falling back to ncurses.
libicui18n.so.34 => not found
libicuuc.so.34 => not found
warning: the ncurses frontend is installed but does not work
You need to install yast2-ncurses to use the YaST2 text mode interface

It seems that Yast will not run with anything '>' greater than (newer)
libicu-3.4-34 . Perhaps an update of Yast in the immediate future will
solve this issue..

Just thought I'd give a heads up.

Barnacle Bill the Sailor · External Since: Jul 25, 2007 Posts: 13

Michael Soibelman wrote:
> O.K. I figured this out. Once yesterday and once today I did a Yast
> software update. Both times, after completing the update, I could no
> longer get yast to start... Now I know what seems to be going on.
>
> It seems that one of the updates was to libicu. The newer version in this
> directory:
>
> http://download.opensuse.org/repositories/GNOME:/UNSTABLE/openSUSE_10.2/
>
> is libicu-3.6-3.1.i586.rpm . I had to uninstall this with the 'rpm -e
> libicu' command and then re-install an older vrsion I got here:
>
> http://rpm.pbone.net/index.php3/stat/4/idpl/3696393/com/libicu-3.4-34....6.rpm.h
>
> Now yast works... Earlier, not being certain what caused Yast not to run, I
> installed 'smart' to fix things.. After that was done (re-installed all
> Yast proggies) and smart uninstalled quite a few others, Yast ran again..
> Then a Yast software update of 'All Packages with newer versions' resulted
> in Yast not working again... Looking at the warnings I got when trying to
> launch Yast from a terminal gave this message:
>
> mylinux:/home/mike # yast2
> libicui18n.so.34 => not found
> libicuuc.so.34 => not found
> warning: the qt frontend is installed but does not work
> Qt GUI wanted but not found, falling back to ncurses.
> libicui18n.so.34 => not found
> libicuuc.so.34 => not found
> warning: the ncurses frontend is installed but does not work
> You need to install yast2-ncurses to use the YaST2 text mode interface
>
>
> It seems that Yast will not run with anything '>' greater than (newer)
> libicu-3.4-34 . Perhaps an update of Yast in the immediate future will
> solve this issue..
>
> Just thought I'd give a heads up.

Well, 10.3 is what, still alpha? Maybe something will turn up there. I
haven't followed yast's development, so wonder myself if it will get any
changes soon.

Chris Maaskant · External Since: May 17, 2007 Posts: 44

Michael Soibelman schreef:

> O.K. I figured this out. Once yesterday and once today I did a Yast
> software update. Both times, after completing the update, I could no
> longer get yast to start... Now I know what seems to be going on.
>
> It seems that one of the updates was to libicu. The newer version in this
> directory:
>
> http://download.opensuse.org/repositories/GNOME:/UNSTABLE/openSUSE_10.2/
>

Well i gues that's why they call it UNSTABLE Wink

--
Chris Maaskant

houghi · External Since: Apr 25, 2004 Posts: 3249

Michael Soibelman wrote:
> O.K. I figured this out. Once yesterday and once today I did a Yast
> software update. Both times, after completing the update, I could no
> longer get yast to start... Now I know what seems to be going on.

IIABDFI. Wink

> It seems that one of the updates was to libicu. The newer version in this
> directory:
>
> http://download.opensuse.org/repositories/GNOME:/UNSTABLE/openSUSE_10.2/
<snip>
> Just thought I'd give a heads up.

So you use an UNSTABLE repo and then warn us that it s unstable.
Interesting.

houghi
--
houghi http://houghi.org http://www.plainfaqs.org/linux/
http://www.netmeister.org/news/learn2quote.html
>
> Today I went outside. My pupils have never been tinier...

Michael Soibelman · External Since: May 10, 2007 Posts: 123

-----------------------------------snip----------------------------
> Well i gues that's why they call it UNSTABLE Wink

O.K. I absolutely agree ! My subject line should have just been
something like 'gnome-unstable is.. unstable' LOL Wink

That way it would be obvious to anyone. I just didn't take the time to
think that through. Seriously though, just meant it to be a heads up for
anyone in the same situation.

In reference to a follow up post to an earlier post of mine regarding this
same situation...yes you're right Houghi. I should probably toggle off
numerous 'development' repo's for the most part. However, only once in a
while does something negative happen. I suppose stability in a desktop IS
a good thing...

Also, I in no way meant to disparage any software developers who may or may
not have unknowingly produced an 'incompatibility' with existing stable
software. Any fault was my own !!

Anyway, I've got to go back to........compiling some more stuff.

Wink

Have a nice day.

Rikishi 42 · External Since: Oct 27, 2005 Posts: 177

On 2007-08-01, houghi <houghi.DeleteThis@houghi.org.invalid> wrote:

>> http://download.opensuse.org/repositories/GNOME:/UNSTABLE/openSUSE_10.2/
><snip>
>> Just thought I'd give a heads up.
>
> So you use an UNSTABLE repo and then warn us that it s unstable.
> Interesting.

Indeed.

<pointy ear mode>
Fascinating logic, quiet fascinating.
</pointy ear mode>

--
There is an art, it says, or rather, a knack to flying.
The knack lies in learning how to throw yourself at the ground and miss.
Douglas Adams

houghi · External Since: Apr 25, 2004 Posts: 3249

Michael Soibelman wrote:
> In reference to a follow up post to an earlier post of mine regarding this
> same situation...yes you're right Houghi. I should probably toggle off
> numerous 'development' repo's for the most part. However, only once in a
> while does something negative happen. I suppose stability in a desktop IS
> a good thing...

There are moments when stability is important. That would be with
servers and desktops in a working enviroment. Other times that is just
boring and breaking things is much more fun. It all depends on what you
try to achieve. The important thing is to keep them seperated.

In this group my first intuition is alwayd to go for stability

> Also, I in no way meant to disparage any software developers who may or may
> not have unknowingly produced an 'incompatibility' with existing stable
> software. Any fault was my own !!
>
> Anyway, I've got to go back to........compiling some more stuff.

If you do compile a lot of stuff and are interested in repo's, which ypu
obviously are, otherwise you would not have so many, why not join the
build service (and mailing list) http://build.opensuse.org/ and
http://en.opensuse.org/Build_Service

That way you can either (help to) repair the issues, add software that
is not yet available for openSUSE or jmake your own repo. Nothing more
fun then learning AND helping at the same time.

houghi
--
houghi http://houghi.org http://www.plainfaqs.org/linux/
http://www.netmeister.org/news/learn2quote.html
>
> Today I went outside. My pupils have never been tinier...