Closed
Bug 1225596
Opened 9 years ago
Closed 9 years ago
Mirror the Ubuntu precise-updates repo
Categories
(Infrastructure & Operations :: RelOps: General, task)
Infrastructure & Operations
RelOps: General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: coop, Assigned: rail)
References
Details
We're trying to upgrade some mesa libs in bug 1220658, but this particular ball of tar will require a laundry list of package updates from the precise-updates repo. This repo isn't currently mirrored.
Comment 1•9 years ago
|
||
Mirroring the entire repo is fairly easy (modulo disk space), but expect it to cause a lot of other mayhem as it will make new packages available that weren't previously available.
Better, I think, would be to figure out the particular packages that you require and mirror those to a custom repo.
Assignee | ||
Comment 2•9 years ago
|
||
Looks there is not too much of mayhem with this repo enabled (see the blocked bug). I don't mind to have the system updated. ;) In the worst case scenario we can revert and only then spend time cherry picking the packages. Last I looked the dependency chain wasn't short. :/
Comment 3•9 years ago
|
||
OK, well, mirroring a new repo isn't hard:
https://wiki.mozilla.org/ReleaseEngineering/PuppetAgain/Packages
and I expect that doing so will determine whether there is enough disk space :)
If you need more disk, let me know -- I think we're in a position where adding a few more tens of gigs is just a reboot and some LVM commands on all of the masters.
Assignee | ||
Comment 4•9 years ago
|
||
Hmmm, I'm getting
rsync: failed to connect to us.archive.ubuntu.com: Network is unreachable (101)
I wonder if we need to whitelist the rsync ports on releng-puppet2.srv.releng.scl3.mozilla.com or something like that...
Comment 5•9 years ago
|
||
Indeed - that seems to have been a change. It's not mentioned either way in the network flow tests.
Updated•9 years ago
|
Assignee: relops → rail
Assignee | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•