Le Mercredi 3 Octobre 2001 21:14, Peter Ruskin scribit : > OK, I found the reason. rpmdrake bales out as soon as it encounters a > corrupt RPM - I had quite a few on my 8.1 repository rsync'd from > uninett.no. I only became aware of this by running rpmdrake from the > command line. Someone really ought to look at improving the message output > from the gui - this _is_ the 21st century :-)
We had warned David concerning that and it seems to have put in his TODO list tyhe possibility to activate a log widows as in some CD recording programs. But you'd better always start rpmdrake from console. Re: [Cooker] Re: [CHRPM] rpmdrake-1.3-105mdk cache problem De : David Odin <[EMAIL PROTECTED]> � : Fabrice FACORAT <[EMAIL PROTECTED]> Date : Tue, 2 Oct 2001 13:34:55 +0200 On Tue, Oct 02, 2001 at 01:55:58AM +0200, Fabrice FACORAT wrote: > Le Mardi 2 Octobre 2001 01:30, Han scribit : > > Fabrice FACORAT (f.faberOnetcourrier.com) wrote: > > By the way I allways start rpmdrake from the console. Now I bet most > > newbies don't know this trick so wouldn't it be helpfull for them if > > they would see all that info? > > > > Suggestion: basic. Let rpmdrake allways start from an xterm or make a > > separate window for it. > > Good idea. what about a log window that you can activate in order to > see what happens ? Each time a user had a problem I had to advice him > to start rpmdrake form console ( what I always do ). > Good idea. Added to the todo. -- [EMAIL PROTECTED] -- http://perso.wanadoo.fr/linux_wizard/index.html - En guerre comme en amour, pour en finir il faut se voir de pr�s. Napoleon
