On Monday 2015-03-09 08:01, Olaf Hering wrote:

On Mon, Mar 02, Olaf Hering wrote:

...

What has to be done to copy the pkg contents as is from source prj to destination prj via a submit request?

Anyone?

That implicit feature was removed sometime in 2.3 or so. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Mon, Mar 09, Adrian Schröter wrote:

On Montag, 9. März 2015, 08:01:03 wrote Olaf Hering:

...

On Mon, Mar 02, Olaf Hering wrote:

...

What has to be done to copy the pkg contents as is from source prj to destination prj via a submit request?

Anyone?

OBS is able to that since quite some time, but osc had no support for it yet.

In osc git master or soon in devel:tools:scm project you will find the

osc sr --update-link

option which is doing exactly what you need here. It does not merge but transfers everything including the _link file.

Does that require server side support? Using that knob with 'obs sr' from a prj in which the pkg contained nothing but a _link resulted in new pkg with expanded sources in the target prj. I had to remove the sources and restored the _link to OBS. Olaf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Mon, May 11, Adrian Schröter wrote:

On Donnerstag, 7. Mai 2015, 15:14:19 wrote Olaf Hering:

...

Using that knob with 'obs sr' from a prj in which the pkg contained nothing but a _link resulted in new pkg with expanded sources in the target prj. I had to remove the sources and restored the _link to OBS. can you give me the example package/request?

https://pmbs.links2linux.de/request/show/1883 Olaf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Mon, May 11, Adrian Schröter wrote:

If you can reproduce it in build.o.o I will have a look there.

olaf@bax:~/work/obs/home:olh:targetcli/build-compare $ obs sr --no-update --update-link -m http://lists.opensuse.org/opensuse-buildservice/2015-05/msg00041.html devel:languages:ocaml Warning: failed to fetch meta data for 'devel:languages:ocaml' package 'build-compare' (new package?) created request id 306417 olaf@bax:~/work/obs/home:olh:targetcli/build-compare $ cd ../../devel:languages:ocaml olaf@bax:~/work/obs/devel:languages:ocaml $ obs up -u ... checking out new package build-compare A build-compare A build-compare/COPYING A build-compare/build-compare.changes A build-compare/build-compare.spec A build-compare/functions.sh A build-compare/pkg-diff.sh A build-compare/same-build-result.sh A build-compare/srpm-check.sh At revision 1. olaf@bax:~/work/obs/devel:languages:ocaml $ I was expecting a _link in build-compare Olaf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

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. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

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. -- 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

Olaf Hering writes:

Why does sr use the sources from the linked prj instead of what was requested, the src prj?

You can submit a specific revision. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

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

On Dienstag, 12. Mai 2015, 10:05:23 wrote Olaf Hering:

On Tue, May 12, Adrian Schröter wrote:

...

On Dienstag, 12. Mai 2015, 09:06:33 wrote Olaf Hering:

...

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?

obs sr --no-update --update-link \ -m http://lists.opensuse.org/opensuse-buildservice/2015-05/msg00041.html \ devel:languages:ocaml

...

I suppose you have not specified any revision, but let the api create one via addrevision option?

yep, osc is using that option in this situation.

Yes, why would I want to specify a revision if I want to submit the state that is used for building a package? Thats cumbersome.

well, the state which is used to build *is* the expanded source. This is the case for all submissions. But in this situation you actually do not want this, but the opposite.

...

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.

I guess a better UI would to to have --use-expanded-sources and --use-unexpanded-sources to avoid all doubt. And to work per default with whatever the BS itself will use to build the pkg. If one really wants to submit something else --revision=N already exists.

Not sure if more options would not create more confusion here. However, as written before, OBS is actually using the expanded sources for building. So this was the default as you suggested. -- 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