Bug 200873

Summary: can't complete update using rug
Product: [openSUSE] SUSE Linux 10.1 Reporter: Robert Harvey <bobharvey>
Component: ZenworksAssignee: Duncan Mac-Vicar <dmacvicar>
Status: RESOLVED WONTFIX QA Contact: Mauro Parra Miranda <mauro>
Severity: Normal    
Priority: P5 - None CC: andreas.hanke, kkaempf, suse-beta
Version: Final   
Target Milestone: ---   
Hardware: i586   
OS: SuSE Linux 10.1   
Whiteboard:
Found By: Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: contents of command window for rug update
log file as requested

Description Robert Harvey 2006-08-22 13:59:32 UTC 
I tried rug update, in an attempt to get round the problems of zen-updater, and got something much more understandable
------------------------------------------
rug update
Waking up ZMD...

Resolving Dependencies...

ERROR: Dependency resolution failed:
Updating yast2-ncurses-2.13.27-3.i586[System packages] to
yast2-ncurses-2.13.40-1.3.i586[SUSE-Linux-10.1-Updates]
Establishing atom:yast2-ncurses-2.13.40-1.3.i586[System packages]
libzypp-0.0.8-154.i586[System packages] provides libzypp.so.0, but is
scheduled to be uninstalled.
libzypp-0.0.8-154.i586[SUSE-Linux-10.1-PromoDVD-i386-10.1-0-20060819-200241]
provides libzypp.so.0, but another version of that
package is already installed.
Can't satisfy requirement libzypp.so.0 for
yast2-ncurses-2.13.27-3.i586[System packages]
Establishing atom:yast2-ncurses-2.13.36-1.2.i586[System packages]
Can't install yast2-ncurses-2.13.40-1.3.i586[20060821-194506], since
yast2-ncurses-2.13.40-1.3.i586[SUSE-Linux-10.1-Updates]
is already marked as needing to be installed
Marking this resolution attempt as invalid.
-----------------------------------------------------
Well, what does that mean?  Did anything else happen, or is this
entirely abortive.  I now have no idea what to do about the messages
above.  It seems I have 3 choices:
1.  Change something myself.  But if so, what?
2.  Tell someone.  But if so, who?  It does not seem appropriate for a
bugzilla report
3.  Wait and hope someone at suse notices, and the next mirror updates
leapfrog the problem. 

I have decided that this needs to go into bugzilla - it should not be possible for an automatic updater to get itself into this sort of tangle.  either the code itself, or the external data structures on the update servers, on which it depends is in some way invalid.  

From a user's point of view this is exactly what rug was supposed to prevent!
Comment 1 Robert Harvey 2006-08-22 18:27:52 UTC 
Next attempt.
In the end I left it a while and then tried again.

This time things were rather different.
The results are shown in the attached file rug_update.txt

So it has still not suceeded, but I don't think I will ever live long enough to see it end.

it took about an hour between typing "rug update" to getting the y/N prompt.  Most  of the time the screen was idle, a sudden rush of patch names just before the prompt was offered.

It was 70 minutes after I answered "y" that the thing popped up and asked me for the dvd.  Another period of dead screen, slightly longer than the first.

About 5 minutes after I put in the DVD it started drawing the progress bar, which took over an hour and a half to get to 97%, and then the error message.

I have a 512Mb broadband connection.  If I was on dial-up my Grandchildren would have died before this would have finished.

Oh, and it still has not succesfully updated.
Comment 2 Robert Harvey 2006-08-22 18:28:42 UTC 
Created attachment 96808 [details]
contents of command window for rug update
Comment 3 Robert Harvey 2006-08-23 19:22:03 UTC 
update:
when I ran rug update again the following morning it said that there were no updates available.  So what about the one it choked on?  Has it done it or not?

I tried rug pa 6bb52b75_d533_4255_9d11_affcfcc5f540/940132702_6.rem but it said it was not a valid catalog.  I tried it with rug search, rug history, rug bundle-history (you can see I was getting desperate).Nothing.

So, I don't know what it was trying to do at the end of attacment 96808, nor how to find out whether it has done it.  It says today that there is nothing to do, but last night it choked at 98% complete.  Which am I to believe?
Comment 4 Tambet Ingo 2006-09-08 09:04:41 UTC 
Looks like a resolver issue to me. Comment #3 is a different problem than the original bug report and all the other comments and has a couple of duplicates already open.
Comment 5 Stefan Schubert 2006-09-08 10:35:29 UTC 
The error should be reproduceable with YOU too:

Please start in a xterm:

export ZYPP_FULLLOG=1; yast2 online_update

And try to reproduce the error.

Please attach the logfile /var/log/YaST2/y2log to bugzilla.

Thanks !!!

BTW: This error occures very often if an update repro is not available anymore from which a patch has been installed sometimes ago.
Comment 6 Robert Harvey 2006-10-03 17:09:13 UTC 
Created attachment 100180 [details]
log file as requested

OK, trying that.  This morning I found:
harvey04:/home/bobh # rug update
Resolving Dependencies...

ERROR: Dependency resolution failed:
Resolvable id 325050 does not exist.

so I tried your trick.

I had to accept an invalid key from one of the repositories, probably pacman.  I have 11 unticked "red" updates, from flash-player to xmms-plugins, and a bunnch of others.  Accepted the flash and microsoft font licences.

Hmm..  YAST ended quite happily, and there was nothing on the command line to see
harvey04:/home/bobh # export ZYPP_FULLLOG=1; yast2 online_update

harvey04:/home/bobh #
Comment 7 Robert Harvey 2006-10-04 08:19:07 UTC 
Thinking about "BTW: This error occures very often if an update repro is not available anymore from which a patch has been installed sometimes ago."

Perhaps this condition could be explicitly detected, then, and an appropriate dialogue displayed - or just silently dealt with?
Comment 8 Federico Lucifredi 2006-10-12 00:12:12 UTC 
flagging it an enhacement request.
Comment 9 Stefan Schubert 2006-10-17 09:23:21 UTC 
"enhancement" is too low. 

Duncan, Michl, what happens if the requested source is not available anymore ?
Comment 10 Andreas Jaeger 2007-08-11 15:00:43 UTC 
We will not fix this bug anymore since ZENworks has been removed for 10.3.  Therefore closing as WONTFIX.
Comment 11 Robert Harvey 2007-08-11 15:22:14 UTC 
That's the best news for a long time.
Now we only need rt2500 support back and I can go back to using Suse,