Custom Query (1145 matches)
Results (202 - 204 of 1145)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#272 | fixed | debathena-tellme: tellme has no manpage | jdreed | geofft |
Description |
The tellme command in the debathena-tellme package has no manpage. |
|||
#273 | fixed | debathena-moira-clients: userreg has a manpage but does not exist | broder | geofft |
Description |
The debathena-moira-clients package installs a manpage for a command called userreg, but that command does not exist. There's an empty third/moira/clients/userreg/ directory in the sources, so perhaps this client used to exist and was deleted. |
|||
#274 | fixed | New debathena-discuss-server breaks mail feeds and local access | mitchb | mitchb |
Description |
This morning, I caught the following in a DSN:
This is due to a reversion in the recently updated debathena-discuss-server package. It results in dsmail being completely unable to work, but not via a bug in dsmail itself. Ordinarily, if root@ATHENA.MIT.EDU has bits on a meeting, then user 'root' on that server is granted those bits. This means that to set up a mail feed to a discuss archive, you figure out what user your MTA will exec dsmail as, and adjust the ACL of the meeting to grant bits to that username@ATHENA.MIT.EDU. With the revised debathena-discuss-server package, if you run discuss as some user on the local server and try to so much as add a non-public meeting, you get the "Connection reset by peer" error. Downgrading only debathena-discuss from 10.0.8-0debathena1 to 10.0.7-0debathena3 does not fix the problem. Downgrading only debathena-discuss-server does fix the problem. |