Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MRAN date based on build day #57

Open
ck37 opened this issue Jul 24, 2015 · 2 comments
Open

MRAN date based on build day #57

ck37 opened this issue Jul 24, 2015 · 2 comments

Comments

@ck37
Copy link
Contributor

ck37 commented Jul 24, 2015

Should the MRAN repo be based on the current day that the build is being created, rather than being hardcoded? Or find the most recent MRAN archive to use? http://mran.revolutionanalytics.com/

It seems kind of unfortunate to have to update the URL whenever building or otherwise having packages potentially worth upgrading immediately after the build is created. E.g. right now the MRAN is 2.5 months old.

@ryanlovett
Copy link
Contributor

It should be set to a particular day for reproducability. The day of the
build would work.

Ryan

On Thu, Jul 23, 2015 at 10:03 PM, Chris Kennedy notifications@github.com
wrote:

Should the MRAN repo be based on the current day that the build is being
created, rather than being hardcoded? Or find the most recent MRAN archive
to use? http://mran.revolutionanalytics.com/

It seems kind of unfortunate to have to update the URL whenever building
or otherwise having packages potentially worth upgrading immediately after
the build is created. E.g. right now the MRAN is 2.5 months old.


Reply to this email directly or view it on GitHub
#57.

@ck37
Copy link
Contributor Author

ck37 commented Jul 24, 2015

Right, for the "most recent MRAN" option it would still be hardcoded in the actual AMI, but it would handle the contingency that there may not be an MRAN folder for the day of the build for whatever random reason.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants