[Bug 605294] New: Need to be able to add SLES 10 SP3 as a build target
http://bugzilla.novell.com/show_bug.cgi?id=605294 http://bugzilla.novell.com/show_bug.cgi?id=605294#c0 Summary: Need to be able to add SLES 10 SP3 as a build target Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: andavis@novell.com QAContact: adrian@novell.com Found By: --- Blocker: --- The OBS isv:microsoft project contains a kernel module package which needs to be built against SLES 10 SP3. I used to be able to add SLE10-SP3 as a target (as shown in my home:andavis:microsoft-hyper-v-3 project). But now when I try to add a build repository, my only choice is "SLES/SLED 10". Would you please let me know if there is a secret way to add SLES 10 SP3? In general, customers/partners who are building kernel modules will need the ability to add specific SLE SP versions as targets. Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=605294 http://bugzilla.novell.com/show_bug.cgi?id=605294#c yang xiaoyu <xyyang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyyang@novell.com AssignedTo|bnc-team-screening@forge.pr |adrian@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=605294 http://bugzilla.novell.com/show_bug.cgi?id=605294#c1 --- Comment #1 from Ann Davis <andavis@novell.com> 2010-05-13 17:29:52 UTC --- Note: Using "osc meta prj -e", I was able to add SLES 10 SP3 as a target for the isv:microsoft project (I got the SLE 10 SP3 repo name from my old home:andavis:microsoft-hyper-v-3 project metadata). So I don't need anything done immediately for this bug. But I still think we need to make sure that the GUI provides a way to add specific SLE service packs as build targets. Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=605294 http://bugzilla.novell.com/show_bug.cgi?id=605294#c2 Adrian Schröter <adrian@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mge@novell.com --- Comment #2 from Adrian Schröter <adrian@novell.com> 2010-05-14 06:09:15 UTC --- hm, we just built against the original version, because this should work also on later service packs (kernel is an exception of course). If I add all service packs, I fear the people will build against all of them without any need. Bad for our resources and I think also bad because people will think that we are highly incompatible between the SP releases. Has product management an opinion here ? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=605294 http://bugzilla.novell.com/show_bug.cgi?id=605294#c3 Matthias Eckermann <mge@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gp@novell.com, | |kukuk@novell.com, | |mge@novell.com, | |okir@novell.com --- Comment #3 from Matthias Eckermann <mge@novell.com> 2010-05-14 10:12:45 UTC --- (In reply to comment #2)
hm, we just built against the original version, because this should work also on later service packs
Yes.
(kernel is an exception of course).
Well, in this case (MSFT LICs) we are talking about Kernel, ...
If I add all service packs, I fear the people will build against all of them without any need. Bad for our resources and I think also bad because people will think that we are highly incompatible between the SP releases.
100% correct. See below for the "however"-part:-)
Has product management an opinion here ?
I indeed do, thanks for asking; adding Gerald in addition. 1. In general I agree that we should not add SLE service packs to the openSUSE BuildService (see Adrian's argument above). 2. As long as PLDP2 (which shall have it's own BuildService instance, as far as I understand) is not active, it makes sense though, to allow partners to build their kernel modules against specific SP states, thus we make their (and our) lifes easier -- and make them used to use the BuildService. In other words: don't make SLE 10 SPx generally available, but only to ISV related projects, where this is necessary on Ann's advice. Is this possible? 3. Now to SLE 11 SP 1. Here is indeed suggest to make it available in the openSUSE BuildService, publically, as soon as we officially have the GoldMaster (I expect: 2010-05-21). Argument: -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com