[opensuse-buildservice] Corrupt diffcache?
When I run "osc rdiff -c 442 Base:System glibc" I get no output, but I'd expect to get the same diff that I get from "osc rq show -d 407107". Earlier revisions don't have this problem. Also, when issuing the api call with "expand=0" I get a correct diff. The corresponding expanded revisions are c60457ca347e1be482c43fab57813ee3 and 139d86ab44417129f81bbc53807137d0 and are clearly different. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "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 2016-08-02 23:46:39 +0200, Andreas Schwab wrote:
When I run "osc rdiff -c 442 Base:System glibc" I get no output, but I'd expect to get the same diff that I get from "osc rq show -d 407107".
Seeing no outpout when running "osc rdiff -c 442..." is "expected", because the link target/rev in 441 is not fixed. Hence, 441 is expanded against openSUSE:Factory glibc HEAD, which already contains the changes from 442. In order to get the expected diff, you need to to fix the link target/rev via the olinkrev parameter. For instance, curl -X POST -d '' \ 'https://api.opensuse.org/source/Base:System/glibc?cmd=diff&orev=441&olinkrev...' yields the same result as "osc rq show -d 407107".
Earlier revisions don't have this problem. Also, when issuing the api call with "expand=0" I get a correct diff. The corresponding expanded revisions are c60457ca347e1be482c43fab57813ee3 and 139d86ab44417129f81bbc53807137d0 and are clearly different.
Hmm how did you calculate these expanded revs? Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (2)
-
Andreas Schwab
-
Marcus Hüwe