Are the SLE-11 SP2 repositories available for building against yet? We
have a local instance OBS server, with projects configured as
...
<repository name="SLE_11_SP1">
<path project="openSUSE.org:SUSE:SLE-11:SP1:Update"
repository="standard"/>
<path project="openSUSE.org:SUSE:SLE-11:SP1"
repository="standard"/>
<arch>i586</arch>
<arch>x86_64</arch>
</repository>
<repository name="SLE_11_SP2">
<path project="openSUSE.org:SUSE:SLE-11:SP2"
repository="standard"/>
<arch>i586</arch>
<arch>x86_64</arch>
</repository>
...
The SLE_11_SP1 repository builds are OK, but as yet there is nothing
happening in the SLE_11_SP2 repo. It doesn't even appear on the
overview/build status page.
Incidentally, how are the SLE repositories configured? The
SUSE:SLE-11:SP1 project contains no packages -- so how do they get "used
for build"?
Regards
Magnus Lewis-Smith
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
present: lnussel, bbrunner, meissner, dirk, rommel, mls, saschpe, adrian
Rollout plan
============
* switch openSUSE maintenance to OBS mechanics and new model
in two steps.
8th March: switch openSUSE:11.4 to new mechanism
================================================
- define openSUSE:11.4:Update as update project
- disable update project syncing from euklid
- disable openSUSE in SWAMP
- reimport all released updates
- convert running updates into incidents
15th March: new maintenance workflow for packagers
================================================
- send mail describing the change and pointing to
documentation some days ago
- find and update wiki pages about maintenance and
point to:
- Update OBS maintenance documentation:
http://doc.opensuse.org/products/draft/OBS/obs-reference-
guide_draft/cha.obs.maintenance_setup.html
Blocking wishes
===============
* openSUSE Maintenance issues
- update feeder must work
AI: dirk
- update test channel generation must work
(should be fixed with new deployment)
* open incident ordering
- no patchinfo exists
- patchinfo rating
- ready to release, but no release request
- release request creation date
AI: saschpe
* Handle project wide requests better in webui like
maintenance requests for entire projects.
AI: adrian/sascha, clarify how to solve it either
during request creation or in webui.
* patchinfo issue listing needs option
documented=false
Done in api/backend, webui needs to take care on
incident overview page.
Optional wishes for 2.3
=======================
* osc jobhistory should contain delta jobs
AI: mls
* special page for maintenance_incendent accept:
- show existing incidents which contains added issues
- offer to merge into incident
* Even more speedup of incident overview page
AI: saschpe
* osc rq watch command to wait for changing results
* implement osc prjres --watch
* enhance createrepo for delta downloads
AI: sascha
* Show binaries in release requests view
* Show issue descriptions in request view
* mbranch api return value shall list all packages
Implemented requests
====================
* webui incident overview
=> show patchinfo summary instead of project summary
=> show package names of incident
=> show all incidents
=> show declined release requests
AI: saschpe
* Add support to fetch CVE descriptions from upstream
AI: adrian
* patchinfo build result must be broken without package
-> openSUSE:Maintenance:288
AI: mls
* broken flag to document to define "stopped" with a text
comment => build result must be broken
AI: adrian
* reimport issues from bugzillas to fix URL's
AI: adrian
--
Adrian Schroeter
SUSE Linux Products GmbH
email: adrian(a)suse.de
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi
There would be some way to make spec files without the BuildRoot tag
and using the %make_install macro build against Evergreen_11.1? I have
been playing with the prjconf but I was unable to define the macro
only for pre-11.2 distros (no %if's after "Macros:"?)
Thanks.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org