Current approach is an error prone, because Debian repos may contain
metadata that doesn't fit our pinning template. Yes, in some cases
our template will work (and it does with upstream Ubuntu and Fuel),
but we want to be flexible and cover all cases.
In order to set corrent pinning, we have to use repo's metadata and
that means download repo's Release file, parse it and create pinning
based on it. In that case we'll use all available pinning rules, so
all possible issues will be up to repo maintainer and not because
we're using error prone approach.
Reviewed: https:/ /review. openstack. org/175358 /git.openstack. org/cgit/ stackforge/ fuel-web/ commit/ ?id=46cd6a8d8e9 43669e4cb755755 1a3e4eeae0019c
Committed: https:/
Submitter: Jenkins
Branch: master
commit 46cd6a8d8e94366 9e4cb7557551a3e 4eeae0019c
Author: Igor Kalnitsky <email address hidden>
Date: Wed Apr 15 18:05:45 2015 +0300
Implement advanced apt pinning
Current approach is an error prone, because Debian repos may contain
metadata that doesn't fit our pinning template. Yes, in some cases
our template will work (and it does with upstream Ubuntu and Fuel),
but we want to be flexible and cover all cases.
In order to set corrent pinning, we have to use repo's metadata and
that means download repo's Release file, parse it and create pinning
based on it. In that case we'll use all available pinning rules, so
all possible issues will be up to repo maintainer and not because
we're using error prone approach.
Related-Bug: #1435892
Related-Bug: #1438783
Closes-Bug: #1446686
Change-Id: I5279b7f414f831 503fd993109dd5c 91bef51a9ef
Signed-off-by: Igor Kalnitsky <email address hidden>