On Tue, 25 May 2010 01:24:18 +0200 (CEST) "Carlos E. R." wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Monday, 2010-05-24 at 15:45 -0300, Marco Calistri wrote:

...

1) Reverting from G:S:2.28 to update repo and ran a zypper dup

Sigh...

A "dup" is intended to update from a version of the distro to the next. Otherwise it can break things. It will upgrade or downgrade everything to mimic the repo state. - -- Cheers, Carlos E. R.

-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkv7CqsACgkQtTMYHG2NR9VFjACfVMxWc/6Iq1amJ6GEeyPlUouU TiQAn3pCxVGyQMCGVyFJPj8Qld7vNceQ =iWx4 -----END PGP SIGNATURE-----

In other words, you should do a zypper up, not a zypper dup. Also, be sure the repo you use is the same one you used originally. -- Tom Taylor - retired penguin openSuSE 11.3-M7 x86_64 KDE 4.4.3, FF 3.6.4 claws-mail 3.7.6 linxt-AT-comcast.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

In order to find a solution to my gdm, which refuses to start, I'am seriously thinking about uninstalling Gnome and all related pkgs from my system (openSUSE 11.2 x86_64). But before doing such boring and perhaps dangerous thing, I wonder collect some list-members suggestions. Foreword: Problems raised up after I enabled Gnome:Stable:2.28 and ran a zypper dup. Actually gnome-greeter does not appears anymore and Gnome desktop stuck on the spinning ball screen undlessly. gconfd-2 eats a lot of CPU/MEM. Workaround: I simply changed /etc/sysconfig/displaymanager replacing "gdm" to "kdm" and with this remedy I can login to Gnome desktop, but I have to insert the security wallet passphrase in order to authorize network applet and also if I want to restart the system then window back to kde greeter instead to proceed directly to reboot. Solution: Can I have the hope to solve my problems by uninstalling completely Gnome from my system? And then re-install all back? And how could I do it safely? It seems that through Yast2 it is not possible since I tried to unmark the labels Gnome Desktop on the left of the window without success. Many Thanks for your attention. BR, Marco -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Ken Schneider - openSUSE ha scritto:

On 05/25/2010 01:08 PM, Marco Calistri pecked at the keyboard and wrote:

...

In order to find a solution to my gdm, which refuses to start, I'am seriously thinking about uninstalling Gnome and all related pkgs from my system (openSUSE 11.2 x86_64).

But before doing such boring and perhaps dangerous thing, I wonder collect some list-members suggestions.

Foreword:

Problems raised up after I enabled Gnome:Stable:2.28 and ran a zypper dup.

Remove the Gnome:Stable repo that you added, then do zypper ref and zypper dup to revert back to what you had before adding Gnome:Stable.

Hi Ken, Thanks, I lack to mention into my "Foreword" that I disabled G:S:2.28 and zypper dup, but reverting doesn't sorted out the expected result and gdm refuses to start. Cheers, Marco -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2010-05-25 at 09:35 -0300, Marco Calistri wrote:

...

...

...

...

1) Reverting from G:S:2.28 to update repo and ran a zypper dup

Sigh...

A "dup" is intended to update from a version of the distro to the next. Otherwise it can break things. It will upgrade or downgrade everything to mimic the repo state.

...

In other words, you should do a zypper up, not a zypper dup. Also, be sure the repo you use is the same one you used originally.

So what about this: http://en.opensuse.org/GNOME/2.26

If the operation I ran is dangerous, why openSUSE put such instructions to be publicly usable?

I have no idea. If the only repo you have is oss, nonoss, update, and the gnome repo, a dup might work. Might. Otherwise, dunno. The page recomends using "YaST or zypper to upgrade to the latest version", but YaST behaves quite different, it doesn't do a full dup. What I know for sure is that a dup, unless really indicated, is dangerous. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkv8UkUACgkQtTMYHG2NR9XTfgCfa+lXIhACMmH5Orr071wnVsYZ BAMAnR+nbgYMTEycqWx81cDTBRf5nyan =Knxs -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2010-05-25 at 18:47 -0400, Patrick Shanahan wrote:

* Carlos E. R. <> [05-25-10 18:45]:

...

What I know for sure is that a dup, unless really indicated, is dangerous.

Highly dependent on the enabled repos :^).

Very much so... I suppose the defined priorities have great influence, too. how exactly... I don't have it clear at all. Anyway, for what is worth, I've never sucessfully upgraded gnome in any SuSE/openSUSE distro. Always had to revert. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkv8VlIACgkQtTMYHG2NR9VRDQCghiV1faOmAenNlJrGeInvyIFm i+0AoJgKlImmYVZzLhONeUNbZVtgeE1P =eqZX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2010-05-24 at 23:13 -0400, Ken Schneider - openSUSE wrote:

...

...

1) Reverting from G:S:2.28 to update repo and ran a zypper dup

Sigh...

A "dup" is intended to update from a version of the distro to the next. Otherwise it can break things. It will upgrade or downgrade everything to mimic the repo state.

It is also used to install updated packages that are in a different repo. The caveat, use at your own risk. YMMV

AFAIK, it will not limit itself to only "dup" the packages in one repo. It will do all of the active repos. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkv8UvoACgkQtTMYHG2NR9W+vgCfY+JZQ6BLEt6Fz6GQ8Y8mM//b AoYAn1TY6lhQbWeT/a9MtOelgnJknja5 =oVuM -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2010-05-25 at 19:13 -0400, Ken Schneider - openSUSE wrote:

On 05/25/2010 06:45 PM, Carlos E. R. pecked at the keyboard and wrote:

...

AFAIK, it will not limit itself to only "dup" the packages in one repo. It will do all of the active repos.

That is correct *but*, the only updates performed will be to newer packages which will NEVER be in the OSS and non-OSS repos.

How do you define "newer"? By date? By version? Notice that if you have, say, version 2 of something, one of the repos with a higher priority has version 1, and you run a dup, it will _downgrade_ your something to version 1. This is intentional.

And the repo with the updates has to have a higher priority in order to be considered by dup. Using zypper dup is _not_ dangerous if you know what you are doing.

So, if you only have the OSS, non-OSS and update repos configured you will revert back to only the packages in those repos. dup gives preferential treatment to the repos with the higher priority.

Yes, that's true and that's what I said. But the moment you put extra repos, like gnome and who knows what, things get really complicated to predict - except if you know zypper internals, which I don't. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkv8XDkACgkQtTMYHG2NR9VA0ACfffwHBEqaeK5rIViHMc9rreNI boMAn0L7edYoOulpzjn3ySwO22QN7jyH =KHIX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2010-05-26 at 18:52 -0300, Marco Calistri wrote:

Latest attempts included:

1) zypper ref -f -b

This does nothing to the system. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkv9roMACgkQtTMYHG2NR9V+FgCdGdDdd1wFcEIUDN/5wFAJSBY5 OMgAoI+KN3YOnFf+3F5sBEB1FXwYxBl3 =Nkv1 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2010-05-27 at 09:07 -0300, Marco Calistri wrote:

Carlos E. R. ha scritto:

...

...

Latest attempts included:

...

1) zypper ref -f -b

This does nothing to the system.

Somebody, somewhere, argued about that a not synced metaDB could drive into problems, when sitting in front of similar issues as mine, for this reason I issued the above command, which force a rebuild of repos metadatas.

Ah, yes, but later you have to tell yast or zypper to reinstall or update things. That's only the database, not the packages. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkv+3BoACgkQtTMYHG2NR9UaIgCdFASYfnjS6RRAkJ61difQVE5n zM8An03Txs9IBYqjG6gUMYjbCY9OP/CW =YfFC -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Marco Calistri ha scritto:

Carlos E. R. ha scritto:

...

On Thursday, 2010-05-27 at 09:07 -0300, Marco Calistri wrote:

...

Carlos E. R. ha scritto:

...

...

...

Latest attempts included:

...

1) zypper ref -f -b

This does nothing to the system.

Somebody, somewhere, argued about that a not synced metaDB could drive into problems, when sitting in front of similar issues as mine, for this reason I issued the above command, which force a rebuild of repos metadatas.

Ah, yes, but later you have to tell yast or zypper to reinstall or update things. That's only the database, not the packages.

-- Cheers, Carlos E. R.

Of course that is implied.

Regards,

Marco

I finally overcome the issue by adopting a drastic but apparently unique measure: I reinstalled 11.2, preserving /home and /data1 dirs where I have my configurations and archives. I took profit of the case and decided to format the / file-system into ext4, instead of the former ext3. Now gdm starts regularly and I am an happy man :) -- Marco Calistri <amdturion> The honourable gentleman is never fortuitous in the coincidence of his facts with truth. -- Winston Churchill -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2010-05-25 at 09:32 -0300, Marco Calistri wrote:

Carlos E. R. ha scritto:

...

On Monday, 2010-05-24 at 15:45 -0300, Marco Calistri wrote:

...

1) Reverting from G:S:2.28 to update repo and ran a zypper dup

Sigh...

A "dup" is intended to update from a version of the distro to the next. Otherwise it can break things. It will upgrade or downgrade everything to mimic the repo state.

Ok, but the "damage" gravity IMHO should be proportional to the enabled repos...

Or not?

Dunno.

Having just G:S:2.28 and nothing Factory enabled, I believe (may be wrongly) that the process would be quiet and mostly reversible.

I really don't know what a zypper dup does when there are several repos. I prefer to use YaST and manually check what version each package is going to get and where from. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkv8U+gACgkQtTMYHG2NR9UEJQCfQlq5f4mUZrvKRhjaYONBsTdV Zi8An2TTMDLbev631Sd2TnXbGReWAYWz =Xzf5 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org