Custom Query (196 matches)
Results (64 - 66 of 196)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #131 | fixed | Better package management for eggs, gems, and other vaguely spherical-shaped objects | andersk | |
| Description |
We currently install a bunch of Perl CPAN modules, Python eggs, and Ruby gems behind RPM’s back. But we have no plan in place for upgrading them, making sure they don’t conflict with RPMs, or making sure they get superseded by new Fedora packages when they become available. This is a disaster waiting to discovered. Everything should be an RPM. There are tools for automatically converting these creatures into RPMs, such as cpanspec, setup.py bdist_rpm, and gem2rpm. We should start using them and get rid of all the unpackaged modules lying around. |
|||
| #140 | fixed | Pony: Stop telling people to decide between CNAME and A records | andersk | |
| Description |
“You can request a non-MIT hostname, but you'll have to register the hostname yourself and configure it's DNS with a CNAME record for "scripts-vhosts.mit.edu." or an A record for scripts-vhosts.mit.edu's IP address, 18.181.0.46.” This isn’t useful to the typical user; the choice between CNAME and A is just confusing. Also, there are too many caveats associated with CNAMEs (canonicalization will kill most of your incoming mail, and you can’t use them at the top of a zone). We should just tell all users to use A records. If for some reason we want to document that CNAMEs are supported even though they’re strictly inferior, we can put that information in an FAQ somewhere, but it shouldn’t be on the Pony form. |
|||
| #162 | fixed | Upgrade scripts servers to Fedora 13 | andersk | |
| Description |
Fedora 11 reached end of life on June 25 and is no longer receiving security support. We’ve been backporting some security updates manually. We should actually upgrade to Fedora 13. (Not that we didn’t know, just that we didn’t have a ticket. See also the Fedora 13 milestone.) |
|||
