https://bugzilla.novell.com/show_bug.cgi?id=439191 User odabrunz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439191#c1 --- Comment #1 from Olaf Dabrunz 2008-10-27 09:04:05 MDT --- 16:00 < jdelvare>|orafu: it doesn't work on SLES10 SP1 either... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439191 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |poeml@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439191 User odabrunz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439191#c3 Olaf Dabrunz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | --- Comment #3 from Olaf Dabrunz 2008-10-29 08:26:45 MDT --- Assigning to maintenance then. The alternatives I see here are: 1) - tell every internal and external developer to - read the openSUSE Wiki (I guess the info about openSUSE:Tools is in there) - gather what specific setup is needed to be able to do basic OS development - track that setup - offer no "basic things are easy and work out of the box" solution 2) - offer updates to OS via maintenance updates Solution 1) means every developer has to follow and track our instructions to get basic things to work. Solution 2) means we do the work to offer maintenance updates. We clearly should have solution 2), if we want people (internal and external) to work with openSUSE. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439191 User hmuelle@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439191#c4 Harald Mueller-Ney changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maint-coord@suse.de AssignedTo|hmuelle@novell.com |adrian@novell.com --- Comment #4 from Harald Mueller-Ney 2008-10-29 09:22:14 MDT --- I do not really see a complete solution - assigning to Adrian driving openSUSE Build service. With the information in the bug I do not see how getpac impacts external people. For internal use: this looks like an immanent problem to me due to the fast development of openSUSE build service. People using build service are more skilled than the average should be able to solve this issue if we give them a good documentation at hand. Adrian could have a look at it. If you see issues which might need updates going to released products, ask maintenance team for help to workout a concept. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=439191 User odabrunz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439191#c6 Olaf Dabrunz changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WORKSFORME |WONTFIX --- Comment #6 from Olaf Dabrunz 2008-10-30 06:59:14 MDT ---

Right, the development speed makes it hard to deliver fixes and requested features in time via maintenance channels.

It should not break when getpac uses it. That's all. This bug is not about other features and fixes. But you have no time to provide customers with needed updates. I see your problem. Anyhow, then this is a WONTFIX rather than a WORKSFORME.

So please use the osc build for your plattform (openSUSE:Tools in external OBS or SUSE:Tools in internal IBS).

I guess this is a temporary workaround. Otherwise I miss this repository in the list of community repositories. (How would I know I need this repository other than to go asking people?)

Lars implemented osc support in getpac to allow "osc build" calls in the checked out sources. He could maybe implement fallback mechanisms there.

Using a fallback when osc exits with a failure code could be helpful for a limited time.

On the other hand, you need anyway a working osc on your workstation or you can't cooperate with the community.

Yes. This is another reason why an update via maintenance channels is so important.

Given the current Beta stress all around here, I suggest you install the new packages to get a fast solution.

This bug is not about me. It is about maintenance channels not working for basic tools. (For me this problem has been solved before I opened the bug, as I simply built osc from STABLE for 10.3. This was just another problem I and others had to solve during our Beta stress...) osc is part of our distribution and an integral part of our openSUSE offering. And now it also is an integral part of our internal work environment. It should not break, and making it work again should not require a special setup that is not part of our offering. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.