openSUSE Forums > Archives > SF Archives > ARCHIVES - 64-bit » 10.2 Update From 10.1 Fails - And Workaround - And Fails Again

Go Back   openSUSE Forums > Archives > SF Archives > ARCHIVES - 64-bit
Forums FAQ Members List Search Today's Posts Mark Forums Read

ARCHIVES - 64-bit Questions specific to 64-bit systems running SUSE Linux
(Questions that apply to both 32-bit and 64-bit systems should be posted in the appropriate mixed architecture forums)

 
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 20-Dec-2006, 17:26
Cobra
Guest
 
Posts: n/a
Red face

I'm doing some updates from 10.1 to openSUSE 10.2 and ran across a problem on an AMD X2 system tonight. The install procedes normally until it presents the list of planned update actions. At that point, the package list tells me there is manual intervention required. On selecting it, I am told the pinentry package is in conflict (both the x86_64 and i586 packages are selected for install.)

I tried the update twice to resolve it with the installer.

First time, I told it to not install the i586 package. It immediately presented me the same conflict again. So I told it not to install the x86_64 package. At that point the installer bails back to text mode, I see a quick note that seems to indicate a core dump, then the start of the installation page returns... I just power off and start again.

The second time, I get to the same point. This time I get the same two presentations, but I tell it to ignore the package in both dialogs (the third option.) Same thing happens, install cores and dies.

I was able to work around this by booting in to the 10.1 installed system. I used Yast to remove the pinentry package, and all the packages that use it (about 6.)

I ran the 10.2 update again and it had no trouble with the package list.
  #2 (permalink)  
Old 20-Dec-2006, 18:07
Cobra
Guest
 
Posts: n/a
Default

But the installed system fails after the package install is complete...

I got a message that said
"An error occurred while switching to the installed system." Along with something like 'no recovery possible, would you like to run the automated debugger?' The debugger is kind of interesting, it verifies a bunch of system packages. No problems are shown, as all the rpm checks pass. Then the install continues, but initrd creation fails. Then the install dies.

I think I'm going to go do a clean install now.
 

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




 

Search Engine Friendly URLs by vBSEO 3.3.0 RC2