[opensuse-packaging] OBS package state "unresolvable"
Hello, JFYI, we decided to rename the "expansion error" package state to "unresolvable". The meaning is still the same, it still means that a package can't get built since build dependencies are missing. We hope that this new name is better understandable. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Monday 26 April 2010 13:58:47 Adrian Schröter wrote:
JFYI, we decided to rename the "expansion error" package state to "unresolvable".
The meaning is still the same, it still means that a package can't get built since build dependencies are missing.
We hope that this new name is better understandable.
If this is at all open to discussion, how will this appear in the clients? 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. 'Packages required for build not found' seems clearer to me. Perhaps this is too long to read well in a table, in which case 'reqtsnotfound' with a tooltip containing the longer text. Will -- Will Stephenson, KDE Developer, openSUSE Boosters Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Mon, 2010-04-26 at 08:13 -0500, Will Stephenson wrote:
On Monday 26 April 2010 13:58:47 Adrian Schröter wrote:
JFYI, we decided to rename the "expansion error" package state to "unresolvable".
The meaning is still the same, it still means that a package can't get built since build dependencies are missing.
We hope that this new name is better understandable.
If this is at all open to discussion, how will this appear in the clients? 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.
'Packages required for build not found' seems clearer to me. Perhaps this is too long to read well in a table, in which case 'reqtsnotfound' with a tooltip containing the longer text.
Sentences were rules out on the opensuse-buildservice list. I suggested icons with tooltips, but compact names with tooltips was not brought up. That could be a very good compromise.
Will
-- Will Stephenson, KDE Developer, openSUSE Boosters Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 04/26/2010 10:15 AM, Luke Imhoff wrote:
On Mon, 2010-04-26 at 08:13 -0500, Will Stephenson wrote:
On Monday 26 April 2010 13:58:47 Adrian Schröter wrote:
JFYI, we decided to rename the "expansion error" package state to "unresolvable".
The meaning is still the same, it still means that a package can't get built since build dependencies are missing.
We hope that this new name is better understandable.
If this is at all open to discussion, how will this appear in the clients? 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.
'Packages required for build not found' seems clearer to me. Perhaps this is too long to read well in a table, in which case 'reqtsnotfound' with a tooltip containing the longer text.
Sentences were rules out on the opensuse-buildservice list. I suggested icons with tooltips, but compact names with tooltips was not brought up. That could be a very good compromise.
Then lets have tooltip on a real word and not some arbitrary abbreviation. Robert
Will
-- Will Stephenson, KDE Developer, openSUSE Boosters Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex
-- Robert Schweikert MAY THE SOURCE BE WITH YOU Software Engineer Consultant LINUX rschweikert@novell.com 781-464-8147 Novell Making IT Work As One -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Montag, 26. April 2010 15:13:24 schrieb Will Stephenson:
On Monday 26 April 2010 13:58:47 Adrian Schröter wrote:
JFYI, we decided to rename the "expansion error" package state to "unresolvable".
The meaning is still the same, it still means that a package can't get built since build dependencies are missing.
We hope that this new name is better understandable.
If this is at all open to discussion, how will this appear in the clients?
Discussion happened before on opensuse-buildservice ml ;)
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.
'Packages required for build not found' seems clearer to me. Perhaps this is too long to read well in a table, in which case 'reqtsnotfound' with a tooltip containing the longer text.
Yes, but this is no state anymore. Imaging how your monitor would look alike if every state would be this extensive -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
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
On Monday 26 of April 2010, Adrian Schröter wrote:
Hello,
JFYI, we decided to rename the "expansion error" package state to "unresolvable".
The meaning is still the same, it still means that a package can't get built since build dependencies are missing.
We hope that this new name is better understandable.
Could you please give it back a color (in the monitor) that made it obvious it was an error? The current grey makes it look a lot like 'disabled'. -- Lubos Lunak openSUSE Boosters team, KDE developer l.lunak@suse.cz , l.lunak@kde.org -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (6)
-
Adrian Schröter -
Juergen Weigert -
Lubos Lunak -
Luke Imhoff -
Robert Schweikert -
Will Stephenson