Custom Query (1145 matches)
Results (136 - 138 of 1145)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#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. |
|||
#167 | wontfix | debathena-lert-server binds only to localhost | broder | |
Description |
debathena-lert-server uses gethostbyname(uname().nodename) as the address to bind to. Unfortunately, on most Ubuntu systems, this works out to being 127.0.1.1 instead of the actual IP address, thanks to Ubuntu's /etc/hosts hacks. More fun, the krb4 code needs the destination address of incoming packets for the encryption of the reply, so we can't simply switch to listening on INADDR_ANY with no other changes. I see two options:
|
|||
#169 | fixed | Live CD adjustments for debathena-login-graphical | xavid | broder |
Description |
I assume that the Live CD wants to run debathena-login-graphical, but install debathena-workstation. This is just to track that that gets dealt with. |