On Apr 26, 10 17:04:42 +0200, Adrian Schröter wrote:
The term 'unresolvable' makes sense to me because I know about dependency resolution, but with my newbie head on I would understand it as 'unfixable error' and start doing random useless things to fix it like deleting and recreating the package.
yes, the state codes are never full understandable by itself. We still will need the legend beside with an explanation like in the past.
I am not really concerned if the stat is called one way or the other. I now have a few packages in 'unresolvable', but no clue what to do. - how do I get more details about *what* was unresolvable? - it would also help the newbie if he could click on something and see, "ah, this depends on another package, which does not build..." thanks, JW- -- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw@suse.de back to ascii! __/ _---|____________\/ \ | 0911 74053-508 __/ (____/ /\ (/) | _____________________________/ _/ \_ vim:set sw=2 wm=8 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org