On Fri, 2015-06-05 at 14:25 +0200, Till Maas wrote:
On Fri, Jun 05, 2015 at 10:34:19AM +0200, Dodji Seketeli wrote:
> When the "abipkgdiff" command line tool is ready , I guess the plan
> is
> to use it in a new Taskotron task that, when invoked on a given
> package,
> gets the stable version of that package as well as the debuginfo
> packages from koji, executes abipkgdiff to compare the package
> against
> it's stable version and emits the resulting report.
It would be nice if such reports could be generated earlier. For
example
when there is an upstream release, the-new-hotness builds a scratch
build automatically for monitored packages:
https://bugzilla.redhat.com/show_bug.cgi?id=1222017#c5
It would be awesome if your tool could report ABI changes afterwards,
so
the potential problem is known even before the new release is
actually
included into Fedora.
First off: I think this is actually already being worked on in rebase
-helper.
Second, I think these don't have to be mutually-exclusive (because the
updates-testing check will help us avoid accidentally introducing
incompatibilities via a downstream patch as well).