Mailinglist Archive: opensuse (1959 mails)

["Mil T" <milt09672@xxxxxxxxx>]

Hi Dave,

> You must have at least one ConsoleKit package and at least one libxcrypt 
> because your system depends on them.

Well ok.  Kind of hoping then that the "system" would know what to DO
with them :-(

> I would recommend using Yast2 Online update to resolve the problem

According to this bug report
(http://lists.opensuse.org/opensuse-bugs/2007-06/msg00641.html) from
what I read "Yast2 Online" *uses* zypper by default, so shouldn't the
results be the same?

> but first use zypper clean
> next zypper ref
> and then post the output of zypper lr

zypper clean
All repositories have been cleaned up.

zypper ref
Repository 'OS11-update' is up to date.
Repository 'OS11-oss' is up to date.
Repository 'OS11-non-oss' is up to date.

zypper lr
#  | Alias            | Name             | Enabled | Refresh
---+------------------+------------------+---------+--------
1  | OS11-update      | OS11-update      | Yes     | Yes
2  | OS11-oss         | OS11-oss         | Yes     | Yes
3  | OS11-non-oss     | OS11-non-oss     | Yes     | Yes

yast2 online_update

Problems───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
    │
│      │patch:libxcrypt-109.noarch conflicts with
libxcrypt-32bit.x86_64 < 3.0-14.2 provided by
libxcrypt-32bit-3.0-14.1.x86_64
                │     │
│      │patch:ConsoleKit-132.noarch conflicts with
ConsoleKit-32bit.x86_64 < 0.2.10-14.2 provided by
ConsoleKit-32bit-0.2.10-14.1.x86_64

Possible 
Solutions─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
    │
│      │[ ] do not keep libxcrypt-32bit-3.0-14.1.x86_64 installed

                                         │     │
│      │[ ] do not install patch:libxcrypt-109.noarch


If I try to "resolve" by Check-ing

 [X] do not keep libxcrypt-32bit...

Then [OK -- Try Again]

etc etc, the results & offered solutions are EXACTLY the same as the
output from Zypper on the command line.

> Another question, which gui(s) do you have and which one are you using?

I originally installed KDE 35, and had this problem.

Someone told me that I should use Gnome.  So I reinstalled everything
with that installed.  I had the same problem.

Some posts have suggested that the GUI is the problem. So I
reinstalled a GUI-less system. And am trying everything at the
"Console GUI" (Do you call it ncurses, or something?), hoping that the
problem gets solved so then I can install the GUI on top of asystem
that works.

So far, the results are the same no matter which GUI I seem to use.

I was searching around and found this discussion,
https://bugzilla.novell.com/show_bug.cgi?id=336678

It's completely over my head, and I'm pretty sure it SHOULD be.  It
seems to be talking about some of this stuff.  It also looks like
"they" have know about this for a long time; since October of last
year?

The discussion ends with

------- Comment #83 From Ladislav Slezak 2008-06-04 05:13:43 MDT
-------I'll remove the yast workaround after 11.0 is out.-------

Comment #84 From Ladislav Slezak 2008-06-04 05:24:39 MDT -------The
workaround was removed in SVN trunk (for 11.1), later it will be
includedin yast2-packager-2.17.0.

Apparently the 11 version I have installed has
yast2-packager-2.16.53-3.1.  And the "Roadmap" for "11.1" says it will
take until Dec to be released.

So, what am I supposed to do in the meantime?  I just want to get up &
running on a system that works.  Should I replace this with a
different flavor of Linux?  Ubuntu's supposed to be "friendly" to
normal users.

--Mil