Custom Query (1145 matches)
Results (13 - 15 of 1145)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1288 | fixed | additional packages for debathena-thirdparty | alexp | alexp |
| Description |
Please add to debathena-thirdparty: pan mesa-utils (Cambridge Structural Database won't work properly without this) iwidgets4 (previously requested for Espresso but it didn't get installed) Thanks,
|
|||
| #1551 | fixed | additional packages for debathena-thirdparty | alexp | alexp |
| Description |
I'm installing a TeX/LaTeX GUI editor, Texmaker, requested for Athena. It requires the following packages: libpoppler-qt4-4 asymptote Could these be installed in the release please?
|
|||
| #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. |
|||
