On Dienstag, 12. Mai 2015, 09:06:33 wrote Olaf Hering:
On Tue, May 12, Adrian Schröter wrote:
On Dienstag, 12. Mai 2015, 08:53:53 wrote Andreas Schwab:
Adrian Schröter
writes: All what updatelink is doing is transfering the sources in an unexpanded form to the target.
If that's all it's doing, then the example should work.
No, because:
osc ls home:olh:targetcli build-compare -R41da7d729e7b110b4c628025433976c8
contains no _link. A submit request using revision 612c8dee23a5e6d2ef4a6b5217c6b96e would work.
How can that be? There is just a single revision in that pkg, the _link existed right from the start.
You can always specify the md5sum of an expanded or an un-expanded source. Also for a single commit.
Why does sr use the sources from the linked prj instead of what was requested, the src prj?
How exactly did you create the request? I suppose you have not specified any revision, but let the api create one via addrevision option? I have change the api code now, that it checks in this situation now for the updatelink option. Only when it is not set it is using the expanded revision. Just in git, not yet deployed. -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org