[opensuse-buildservice] Re: [opensuse-svn] r3494 - trunk/buildservice/src/build
Hi, On Tue, Mar 11, 2008 at 06:21:45AM -0600, Novell Forge SVN wrote:
Author: lnussel Date: 2008-03-11 06:21:40 -0600 (Tue, 11 Mar 2008) New Revision: 3494
Modified: trunk/buildservice/src/build/build trunk/buildservice/src/build/init_buildsystem Log: qemu and uml support
Intended to be used as regular user. User must be allowed to mount the disk image file via /etc/fstab for that to work.
I saw this commit and the others that Ludwig recently did. How about releasing a new build package once in a while? Right now, build.rpm in openSUSE:Tools was last updated in September last year. So I assume most people still use that old version. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
On Tuesday 11 March 2008 13:25:58 wrote Dr. Peter Poeml:
Hi,
On Tue, Mar 11, 2008 at 06:21:45AM -0600, Novell Forge SVN wrote:
Author: lnussel Date: 2008-03-11 06:21:40 -0600 (Tue, 11 Mar 2008) New Revision: 3494
Modified: trunk/buildservice/src/build/build trunk/buildservice/src/build/init_buildsystem Log: qemu and uml support
Intended to be used as regular user. User must be allowed to mount the disk image file via /etc/fstab for that to work.
I saw this commit and the others that Ludwig recently did.
How about releasing a new build package once in a while? Right now, build.rpm in openSUSE:Tools was last updated in September last year. So I assume most people still use that old version.
openSUSE:Tools is intended to be kept stable. However we could create new versions for testing in openSUSE:Tools:Unstable first and later merging back. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2008-03-11 15:22:23 +0100, Adrian Schröter wrote:
openSUSE:Tools is intended to be kept stable. However we could create new versions for testing in openSUSE:Tools:Unstable first and later merging back.
why do you think that the current codebase of "build" is unstable? can you prove that with facts? darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Marcus Rueckert wrote:
On 2008-03-11 15:22:23 +0100, Adrian Schröter wrote:
openSUSE:Tools is intended to be kept stable. However we could create new versions for testing in openSUSE:Tools:Unstable first and later merging back.
why do you think that the current codebase of "build" is unstable? can you prove that with facts?
Weird question. I made quite some changes so the concern that the build script might contain more bugs now is valid. It's not intentionally broken either of course. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Ludwig Nussel escribió:
Weird question. I made quite some changes so the concern that the build script might contain more bugs now is valid.
Sure, but if the users dont get it installed, there is no way to discover bugs, report and fix them. -- "Morality is merely an interpretation of certain phenomena — more precisely, a misinterpretation." - Friedrich Nietzsche Cristian Rodríguez R. Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, Mar 11, 2008 at 03:22:23 +0100, Adrian Schröter wrote:
How about releasing a new build package once in a while? Right now, build.rpm in openSUSE:Tools was last updated in September last year. So I assume most people still use that old version.
openSUSE:Tools is intended to be kept stable. However we could create new versions for testing in openSUSE:Tools:Unstable first and later merging back.
bye adrian
A lag of half a year sounds like a bit of a too strong safety belt to me. There is no "openSUSE:Tools:Unstable" that I can see either. (It's sheer existence wouldn't actually mean that anyone tests it anyway.) I propose to surface changes much earlier, release early and often, you know, to keep breakage small and revertible. We can also test the svn version, I suppose, can't we? I would be happy to do that. What is needed? osc has a config setting 'build-cmd'. Is it possible to point that to the svn working copy? Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
Hi, Dr. Peter Poeml wrote:
On Tue, Mar 11, 2008 at 03:22:23 +0100, Adrian Schröter wrote:
How about releasing a new build package once in a while? Right now, build.rpm in openSUSE:Tools was last updated in September last year. So I assume most people still use that old version.
openSUSE:Tools is intended to be kept stable. However we could create new versions for testing in openSUSE:Tools:Unstable first and later merging back.
bye adrian
A lag of half a year sounds like a bit of a too strong safety belt to me.
There is no "openSUSE:Tools:Unstable" that I can see either. (It's sheer existence wouldn't actually mean that anyone tests it anyway.)
I propose to surface changes much earlier, release early and often, you know, to keep breakage small and revertible.
We can also test the svn version, I suppose, can't we?
I do that regularily with a "larger setup" and also some big projects mirrored from build.o.o, and testing this also :-) I build and install: - osc - build - obs-server - rails 2.0 stuff completly from svn trunc, from one source code version. I currently use -r 3408 (that was when abauer fixed the errors with https://bugzilla.novell.com/show_bug.cgi?id=366405) I intend to update to current revision, especially after the new build features and the osc merge. I had already asked to put a copy into openSUSE:Tools:Unstable, but have no permission, to get openSUSE:Tools:Unstable lets say every week or so, or when some new features are to be tested. Where should the rails 2.0 copy (e.g. from darix) go? Also into openSUSE:Tools:Unstable? Cheers, Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi Martin, On Tue, Mar 11, 2008 at 06:57:30 +0100, Martin Mohring wrote:
A lag of half a year sounds like a bit of a too strong safety belt to me.
There is no "openSUSE:Tools:Unstable" that I can see either. (It's sheer existence wouldn't actually mean that anyone tests it anyway.)
I propose to surface changes much earlier, release early and often, you know, to keep breakage small and revertible.
We can also test the svn version, I suppose, can't we?
I do that regularily with a "larger setup" and also some big projects mirrored from build.o.o, and testing this also :-)
That's good to know. My concern is that if we don't have anybody who updates the stable build package, we will much less have anyone who additinally updates an unstable package.
I had already asked to put a copy into openSUSE:Tools:Unstable, but have no permission, to get openSUSE:Tools:Unstable lets say every week or so, or when some new features are to be tested.
Knowing that you would like to work in this area, it should be no problem at all to get you the required permissions. Adrian?
Where should the rails 2.0 copy (e.g. from darix) go? Also into openSUSE:Tools:Unstable?
Cheers, Martin
Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
participants (6)
-
Adrian Schröter -
Cristian Rodríguez -
Dr. Peter Poeml -
Ludwig Nussel -
Marcus Rueckert -
Martin Mohring