https://bugzilla.novell.com/show_bug.cgi?id=419589 Summary: osc meta prj alters order of tags Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: luke@cray.com QAContact: adrian@novell.com Found By: Community User This is for osc 0.107 and a local instance of OBS 0.9.99, but may apply to ealier osc versons. Inside the repository tag in the prj meta the path tag order matters because it determines the order of paths to check for a given rpm. If both paths supply a given rpm when the first list path wins. Now, the server records the tag order as given by the user: less /srv/obs/projects/XT:2.2.xml: <project name="XT:2.2"> <title>The 2.2 release stream of XT</title> <description></description> <person role="maintainer" userid="luke" /> <build> <disable arch="i586" repository="SLE_10" /> </build> <publish> <disable arch="i586" repository="SLE_10" /> </publish> <repository name="SLE_10"> <path project="kernel:1.2" repository="SLE_10" /> <path project="SUSE:SLE-10:SDK" repository="standard" /> <arch>x86_64</arch> </repository> </project> The order of kernel:1.2 and SUSE:SLE-10:SDK is correct since we want our kernel-source and kernel-syms from kernel:1.2 to be used over the ones in SLES 10. However, osc prj meta shows the wrong order (SUSE:SLE-10:SDK before kernel:1.2), which disagrees with the server stored copy: osc meta prj XT:2.2: <project name="XT:2.2"> <title>The 2.2 release stream of XT</title> <description></description> <person userid="luke" role="maintainer"/> <build> <disable repository='SLE_10' arch='i586'/> </build> <publish> <disable repository='SLE_10' arch='i586'/> </publish> <repository name="SLE_10"> <path repository="standard" project="SUSE:SLE-10:SDK"/> <path repository="SLE_10" project="kernel:1.2"/> <arch>x86_64</arch> </repository> </project> If I were to check in the prj meta in the order osc meta prj displays (e.g after editing the description) it would break the build since our kernels are needed for special headers, etc, but the SLES 10 kernel-source would be found first and used instead The workaround is to always check the order, but if anyone tries to edit the prj meta with osc and doesn't know what the path order should be then they can break the build. -- 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.