[opensuse-buildservice] Build Team Meeting
present: cwh, mls, tschmidt, adrian, freitag Topics: * Status round * expansion error -> dependency error * 1.7.3 release * MeeGo meeting * OBS Downtime Status round ============ cwh: * kiwi implementation for driver update disk is complete, waiting for validation by Scott. * has quite some ideas to improve current kiwi product code, need testsuite before to work on that. mls: * Supporting kiwi image builds for repos without kiwi. => will be part of 1.7.3 release tschmidt: * added "branch" functionality to webui, similar look at * rewrote "Add repository" page - "simple page" gets the list from the api now * Lots of bugfixing together with coolo * Improved project status page again * layout and icon changes Please test build.opensuse.org/stage and give feedback! adrian: * prepare 1.7.3 release * try to get source service working within lxc for build.o.o => minimal goal is to support file download * Real Names get updated now based on iChain data * added "signing" state for packages, helpfull when signing service has trouble. freitag: * removing accounts from Hermes with invalid account names. * Thinking about how to handle user database of hermes together with OBS. expansion error -> dependency error =================================== Discussion about to rename "expansion error" to "dependency error". We think that this would be a better understandable name. Any opinions ? 1.7.3 release ============= Current 1.7 branch is rolled in openSUSE:Tools project. Will be published this week. MeeGo meeting ============= LinuxFoundation, Intel, Nokia and SUSE/Novell had OBS developer meeting in Nuernberg. Details were sent around earlier: http://lists.opensuse.org/opensuse-buildservice/2010-04/msg00170.html OBS Downtime ============ SAN connection failure lead to downtime 12hours ago. We still have broken on disk data due lack of data journaling, which we are currently repairing. Everything is working, except scheduling might take longer. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 04/20/2010 05:52 AM, Adrian Schröter wrote:
<snip>
expansion error -> dependency error ===================================
Discussion about to rename "expansion error" to "dependency error". We think that this would be a better understandable name.
Any opinions ?
It should be "dependency resolution error", one has to presume the the dependency specification is correct. Therefore, it is technically not a "dependency error". The problem is that the dependency cannot be satisfied/resolved for one reason or another, not that the dependency is incorrect. My $0.02 Robert -- 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-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag, 20. April 2010 13:46:49 schrieb Robert Schweikert:
On 04/20/2010 05:52 AM, Adrian Schröter wrote:
<snip>
expansion error -> dependency error ===================================
Discussion about to rename "expansion error" to "dependency error". We think that this would be a better understandable name.
Any opinions ?
It should be "dependency resolution error", one has to presume the the dependency specification is correct. Therefore, it is technically not a "dependency error". The problem is that the dependency cannot be satisfied/resolved for one reason or another, not that the dependency is incorrect.
technically correct, but it will cause problems on monitor pages. This already way longer than "broken", "succeeded", "failed" for example and an entire sentence would mess up the output of webui and osc even more. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tuesday 20 April 2010 15:35:18 Adrian Schröter wrote:
It should be "dependency resolution error", one has to presume the the dependency specification is correct. Therefore, it is technically not a "dependency error". The problem is that the dependency cannot be satisfied/resolved for one reason or another, not that the dependency is incorrect.
technically correct, but it will cause problems on monitor pages. This already way longer than "broken", "succeeded", "failed" for example and an entire sentence would mess up the output of webui and osc even more.
Maybe "unresolvable"? Andreas -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
If you're worried about length, why not use icons in the webui and have the mouseover tooltip display the status phrase? Won't help osc unless it adopts a symbol based status in the table with a key at the bottom. On Tue, 2010-04-20 at 08:35 -0500, Andreas Gruenbacher wrote:
On Tuesday 20 April 2010 15:35:18 Adrian Schröter wrote:
It should be "dependency resolution error", one has to presume the the dependency specification is correct. Therefore, it is technically not a "dependency error". The problem is that the dependency cannot be satisfied/resolved for one reason or another, not that the dependency is incorrect.
technically correct, but it will cause problems on monitor pages. This already way longer than "broken", "succeeded", "failed" for example and an entire sentence would mess up the output of webui and osc even more.
Maybe "unresolvable"?
Andreas
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag 20 April 2010 schrieb Luke Imhoff:
If you're worried about length, why not use icons in the webui and have the mouseover tooltip display the status phrase? Won't help osc unless it adopts a symbol based status in the table with a key at the bottom.
I don't think you can express the problem in icons well enough. There are too many states. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 04/20/2010 09:35 AM, Andreas Gruenbacher wrote:
On Tuesday 20 April 2010 15:35:18 Adrian Schröter wrote:
It should be "dependency resolution error", one has to presume the the dependency specification is correct. Therefore, it is technically not a "dependency error". The problem is that the dependency cannot be satisfied/resolved for one reason or another, not that the dependency is incorrect.
technically correct, but it will cause problems on monitor pages. This already way longer than "broken", "succeeded", "failed" for example and an entire sentence would mess up the output of webui and osc even more.
That's somewhat a sad state of affairs. While I can see issues with a long sentence or a paragraph, it strikes me as odd that we cannot handle 3 words.
Maybe "unresolvable"?
Sounds reasonable to me. Robert
Andreas
-- 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-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag, 20. April 2010 15:35:57 schrieb Andreas Gruenbacher:
On Tuesday 20 April 2010 15:35:18 Adrian Schröter wrote:
It should be "dependency resolution error", one has to presume the the dependency specification is correct. Therefore, it is technically not a "dependency error". The problem is that the dependency cannot be satisfied/resolved for one reason or another, not that the dependency is incorrect.
technically correct, but it will cause problems on monitor pages. This already way longer than "broken", "succeeded", "failed" for example and an entire sentence would mess up the output of webui and osc even more.
Maybe "unresolvable"?
Sounds good to me, and it is a state and just one word. Any objections against to the switch from "expansion error" to "unresolvable" ? bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (5)
-
Adrian Schröter -
Andreas Gruenbacher -
Luke Imhoff -
Robert Schweikert -
Stephan Kulow