Ticket #821 (closed defect: fixed)
build chroots should use mirrors.mit.edu
| Reported by: | jdreed | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Precise Beta |
| Component: | -- | Keywords: | |
| Cc: | Fixed in version: | ||
| Upstream bug: |
Description
The build chroots are still using a variety of mirrors. This is causing us to lose, because ubuntu.media.mit.edu (used by the lucid chroot) is still trying to update from Feb 28, didn't get the 2.6.32-29 kernel, and thus the autodebathenificator couldn't build AFS modules, so every single machine around campus is upset that it can't update AFS.
I have used a sufficiently large hammer to get it working for now, however, I have no idea how to make this change permanently, since schroot tells me I'm not authorized to poke at the source chroot. Someone should document this process in the wiki.
Change History
comment:2 Changed 13 years ago by jdreed
Fixed for the Ubuntu chroots. Should we do the same for the Debian ones (which are still pointed at debian.lcs?
comment:3 Changed 13 years ago by jdreed
- Priority changed from blocker to normal
- Milestone changed from Natty Alpha to Fall 2011
I don't have a good answer to this. mirrors.mit.edu screwed us last month when it was experiencing network suckage. Approx made that worse by somehow refusing to even try and synchronize things. Approx has the benefit that we need only change our mirror in one place. Mirrors.mit.edu has the benefit that it's fast (and frankly, we'd rather know when it dies). And with dkms, we'll care less about having the mirror available ZOMG RIGHT NOW. So I still think we should do this, but it's lower priority.
comment:4 Changed 12 years ago by jdreed
- Status changed from new to closed
- Resolution set to fixed
When we switched to tar-based chroots, we created new chroots pointed at the approx cache. I just updated approx.conf on zulu to grab Debian from mirrors.mit.edu (it was pointed at debian.lcs) and ran approx-update. Approx was already looking at mirrors for Ubuntu. If Approx breaks, we can always quickly re-create the chroot with a new value for MIRRORHOST.
I noticed some oddness here too a while back. The canonical sources.list files all use approx (localhost:9999), as they're supposed to, and approx is pointed at the upstream primary archive sites. I'm not sure why the build chroots on disk are out-of-sync with that. Someone may have been working around approx trouble.
The trick with the source chroots is that you can only use them if you're logged in to root instead of the build account on the host. Since there's really no effective privilege separation, we can probably reconfigure schroot to let you get to the source chroots as not-root, but that's not the default behavior.