On Tue, 25 Jun 2019 11:13:19 +0200 Martin Wilck <mwilck@suse.com> wrote:
On Mon, 2019-06-24 at 14:51 +0200, Michal Suchánek wrote:
It can and has been done but the very OBS team has rejected it. That's why we have a bot tracking patch changes when the package storage mechanism used by OBS should be able to do that. I mean the patch was checked into OBS and then later removed. Why can't OBS tell us when it happened, and what were the other package files at the time?
Some simple scripting around "osc log" and "osc rdiff" should provide the data in question. Or am I missing something?
Many package revisions cannot be 'expanded'. This whole thing is very unreliable. For Factory this should work more or less (unless somebody broke the package somewhere in its history which sometimes does happen). For release projects this is hopeless because packages are replaced in updates so getting the history out of OBS is challenging.
Something along the lines of
for x in $(seq 2 12); do echo === $x osc rdiff -r$((x-1)):$x openSUSE:Factory vdr | cat done | egrep '^=== |^[+-]Patch[0-9]*:'
It could arguably be made a easier and more reliable, but it can be done today.
And if it can be done why don't the mass-change scripts do it instead of parsing the changelogs? Because parsing changelogs is much faster and more reliable than querying OBS I suspect. Thanks Michal -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org