Custom Query (1145 matches)
Results (151 - 153 of 1145)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #161 | wontfix | Make texlive install more quickly. | wdc | |
| Description |
The install of texlive performs activities such as
as every package is installed rather than setting a trigger to perform them once at the end of all package installs. This causes the texlive install to take far longer than it ideally should. It would be nice if we could help the upstream debian integrator of texlive to produce a more efficient install. Broder has also cooked up a hack to do some triggerizing: /mit/broder/Public/debathena-triggerize-texlive_1.0.tar.gz Consensus is that we'd prefer to work with upstream rather than having our own local hack. |
|||
| #163 | fixed | debathena-auto-update should know about apt-release clusterinfo | geofft | broder |
| Description |
Soon, hopefully, machines in various Moira clusters around campus will have "production", "proposed", and/or "development" values for the "apt-release" key in clusterinfo. debathena-auto-update should know about that key, and adjust /etc/apt/sources.list.d/debathena.list accordingly when it runs. This allows us to configure cluster machines (and other workstations) to take updates from -proposed and -development without having to ever physically manipulate the machines. |
|||
| #164 | fixed | installer should know about apt-release clusterinfo | amb | broder |
| Description |
Soon, hopefully, machines in various Moira clusters around campus will have "production", "proposed", and/or "development" values for the "apt-release" key in clusterinfo. The Debathena installer script should somehow know about this field, and should use it to frob /etc/apt/sources.list.d/debathena.list appropriately at install time. This allows us to test how a system handles being installed with the packages in -proposed (or -development). This one is a little trickier than #163 because we don't have debathena-clusterinfo or debathena-getcluster installed when /etc/apt/sources.list.d/debathena.list is written. It may be that we want to install debathena-getcluster, find out the clusterinfo, and then re-generate /etc/apt/sources.list.d/debathena.list, but even this seems slightly non-ideal, as for a small period packages will only be pulled from production. |
|||
