Mailinglist Archive: opensuse (2459 mails)

< Previous Next >
Re: [opensuse] [Fwd: What is the problem - and with whom?]
  • From: Basil Chupin <blchupin@xxxxxxxxxx>
  • Date: Sat, 22 Mar 2008 14:05:13 +1100
  • Message-id: <47E47769.1030807@xxxxxxxxxx>
Jeremy Baker wrote:
On March 20, 2008 04:28:52 am Basil Chupin wrote:
I've been using smart now since it was available for use in openSUSE.

At the moment I am using opeSUSE v10.3 (with all of its upgrades/updates
as of today).

I am also using both openSUSE's zypper and smart to upgrade the OS.

Everything was working just fine until a couple of days ago when
openSUSE's zypper did some upgrades - and it so happens that I saw that
python was one of the files being upgraded.

Since this upgrade, smart does not work.

While smart-updater goes away and checks for new upgrades and comes back
with the information that there are new upgrades available, trying to
download these new upgrades results with -- zilch.

Running smart itself produces nothing.

Running smart from a command line with, /usr/bin/smart --gui produces
the error message:

system has no support for gtk python interface

But python is installed (and it was upgraded as I mentioned above).

What do I need to do to get smart working again?


If you really want to know, you won't ask me.

I had this exact same behaviour. The culprit was the python-gtk 2.12.0-22.1 from the GNOME:Community repository. I downgraded to 2.10.6-25 from the standard opensuse repo, and now all is well. One other thing to note, smart isn't broken, just the gui. You can still run it from the command line.

I am getting a bad nagging feeling about the way openSUSE is being upgraded/updated by zypper- I can see some nasty things heading towards openSUSE.

Take this python-gtk business.

There are at least 3 versions (for 32- and 64-bit OSs) of python-gtk available via the zypper upgrade 'system' all with different version numbers: they are available from the Main Repository (OSS), but not being upgraded; the next 2 come from the openSUSE BuildService - GNOME:Community and openSUSEBuildService - GNOME:STABLE.

Now, if you have some Gnome bits installed - like mc [Midnight Commander] - you most probably won't get them upgraded unless you select either GNOME:Community or GNOME:STABLE, but if you do then you may get a different version of some file installed depending on whether you had selected Community or STABLE. (I had Community selected and received the "dud" python-gtk.)

In the case of python-gtk, Community has 2.12.0-22.1 (dated 17 March 1617 hours), which is the one causing smart not to function, while STABLE has 2.12.0-4.3 (dated24 Jan 1101 hours), and at the same time the normal SuSE update repository has 2.10.6-25 and which was never upgraded since I installed 10.3 until GNOME:Community repository kicked in on 18 March and installed the defective (for smart) 2.12.0-22.1.

In an earlier message I asked someone from where did he get 2.12.0-4.2 (dated 24 Jan 0227 hours) because he had to go back to it to have smart working again. Well, this version is a x64 version residing in the GNOME:STABLE directory.

In YaST2's List of Online Repositories both GNOME:Community and GNOME:STABLE are shown. Which one is to be selected for use - or should both be selected?

Another point about this is that I am using KDE so why should I have to go messing around with GNOME-related repositories? I am in the process of converting a friend of mine from XP to openSUSE and using KDE- trying to explain to him why he needs to select GNOME-related repositories is going to be very tricky business....


If you really want to know, you won't ask me.

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >