Reboot to terminal prompt after updating repositories and running updates

Hi all,

A few months ago, after installing 12.1, I followed the documentation to upgrade to Tumbleweed and at first it seemed like everything worked fine until I realized it was been a long time I didn’t get any system updates. When I tried to run the updates in YAST, I had way to many conflicts so I figured there was something wrong with my repositories.

I updated my repositories to the only ones listed on the sticky post of this forum and I ran an update after manually resolving the conflicts, for which I was able to select an option to install a new version except for one where I had the choice to break dependencies or change the architecture, so I picked the latest option. It had many references in this conflict including Mozilla but I can’t post the exact name as I am now stuck to access the internet with my phone.

I would rather like to fix my setup rather than reinstalling everything as it takes me at least 2 full days to reinstall all my setup from scratch. Do you have any advice on how I can fix my mess or how can I rollback to a stable checkpoint?

Thanks a million!

It could be tricky, or at least require some careful answers to any package conflict prompts you encounter. It all depends on how incosistent the package state is (because of the enabled repos you had previously)

Anyway, try the following

zypper ve

You can exclude recommended packages initially with

zypper ve --no-recommends

That might cut down on some of the complexity.

You may also find some applications need to be un-installed as part of this package resolution process. Go with that, they can be added back in later as required. See how that goes.

On 09/25/2012 04:26 PM, JeromeQc wrote:
>
> Hi all,
>
> A few months ago, after installing 12.1, I followed the documentation
> to upgrade to Tumbleweed and at first it seemed like everything worked
> fine until I realized it was been a long time I didn’t get any system
> updates. When I tried to run the updates in YAST, I had way to many
> conflicts so I figured there was something wrong with my repositories.
>
> I updated my repositories to the only ones listed on the sticky post of
> this forum and I ran an update after manually resolving the conflicts,
> for which I was able to select an option to install a new version except
> for one where I had the choice to break dependencies or change the
> architecture, so I picked the latest option. It had many references in
> this conflict including Mozilla but I can’t post the exact name as I am
> now stuck to access the internet with my phone.
>
> I would rather like to fix my setup rather than reinstalling everything
> as it takes me at least 2 full days to reinstall all my setup from
> scratch. Do you have any advice on how I can fix my mess or how can I
> rollback to a stable checkpoint?
>
> Thanks a million!
>
>
If I still had Tumbleweed based on 12,2, I would put the openSUSE 12.2
DVD in my optical drive, attach the optical drive as a repo, and see
what happens when I ran “zypper dup -D”. The -D switch makes it a dummy
run. I tried this on my TW when 12.2 was released (just because I am
inquisitive) and I was presented with a beautiful, conflict-free schema
for taking the whole thing over to 12.2

Have a look at that, the -D swith will keep you safe and it might help
you get to a stable state (or it might not).


Regards
swerdna

That’s worth a crack too! :slight_smile:

Running these commands returned there was no conflicts but I was still stuck with the terminal prompt after rebooting.

I reinstalled 12.1 because I had no blank CD around and I still had the Live CD under the hand. I guess I exaggerated a little when saying it would take me 2 days to setup everything because it was only a matter of 2 hours. Since my /home is mounted on a separated partition I didn’t loose any settings at all…

I don’t know where I messed when upgrading to Tumbleweed but I guess I’ll have to do a bit more reading before to upgrade it again.

Thanks anyway!

Good result. I upgraded to 12.2 sooner than intended for similar reasons, after a KDE upgrade (from 4.8.5 to 4.9) didn’t go as well as expected. (I chose to do a live upgrade over the network.) :slight_smile: