Closed Bug 1022790 Opened 12 years ago Closed 11 years ago

Specify OpenSSL version in mock builds

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: dustin, Unassigned)

Details

With http://lists.centos.org/pipermail/centos-announce/2014-June/020344.html, we need to upgrade the version of OpenSSL used everywhere. This includes in mock builds. However, mock doesn't pin the versions of openssl required, and thus takes whatever is "latest" in the repository. This doesn't present a stable build platform as you might expect from a mock environment. Ideally, it seems that the version of *every* package should be pinned, a la requirements.txt for Python or shrinkwrap for node. For the moment, though, pinning OpenSSL should help to enable a controlled upgrade to fixed versions of OpenSSL.
docker will solve this!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.