mirror of
git://sourceware.org/git/libabigail.git
synced 2025-01-25 02:32:46 +00:00
The Git repository of the Libabigail Project
d9b5306224
The build libxcb-1.12-3.fc26 has been tagged for Fedora 27 (i.e, fc27). When we ask fedabipkgdiff to get the builds of libxcb for Fedora 27, it looks for builds which release string ends with 'fc27'. It thus fails to pick libxcb-1.12-3.fc26. This patch changes this behaviour by making Brew.get_package_latest_build to first try to get builds which release string match exactly the distro string we are looking at. But then if no build was found, the member function then tries to get builds for which the distro part of the release string is "less than" (in a lexicographic way) the distro string we are looking at. I haven't added any regression test specifically for this because we are planning to use the libabigail-selfcheck external tool to perform regression testing on tons of Fedora packages: https://pagure.io/libabigail-selfcheck. Fixing this issue is a pre-requisite for putting that regression test infrastructure in place. * tools/fedabipkgdiff (get_distro_from_string): Define new function. (Brew.get_package_latest_build): Also consider builds which distro property is less than the expected distro string that we were given. Signed-off-by: Dodji Seketeli <dodji@redhat.com> |
||
|---|---|---|
| autoconf-archive | ||
| bash-completion | ||
| doc | ||
| include | ||
| m4 | ||
| scripts | ||
| src | ||
| tests | ||
| tools | ||
| .gitignore | ||
| abigail.m4 | ||
| AUTHORS | ||
| ChangeLog | ||
| COMMIT-LOG-GUIDELINES | ||
| COMPILING | ||
| configure.ac | ||
| CONTRIBUTING | ||
| COPYING | ||
| COPYING-GPLV3 | ||
| COPYING-LGPLV2 | ||
| COPYING-LGPLV3 | ||
| default.abignore | ||
| gen-changelog.py | ||
| install-sh | ||
| libabigail.pc.in | ||
| ltmain.sh | ||
| Makefile.am | ||
| NEWS | ||
| README | ||
| release-text-template.txt | ||
| VISIBILITY | ||
This is the Application Binary Interface Generic Analysis and Instrumentation Library. It aims at constructing, manipulating, serializing and de-serializing ABI-relevant artifacts. The set of artifacts that we are intersted is made of quantities like types, variable, fonctions and declarations of a given library or program. For a given library or program this set of quantities is called an ABI corpus. This library aims at (among other things) providing a way to compare two ABI Corpora (apparently the plural of corpus is copora, heh, that's cool), provide detailed information about their differences, and help build tools to infer interesting conclusions about these differences. You are welcome to contribute to this project after reading the files CONTRIBUTING and COMMIT-LOG-GUIDELINES files in the source tree. Communicating with the maintainers of this project -- including sending patches to be include to the source code -- happens via email at libabigail@sourceware.org.