Hi Nick,

We seem to have two things going on here:

motd.innd is to be renamed to motd.nnrpd (by a means yet to be agreed);

Do you mean motd.news (used by INN <= 2.5.2) is to be renamed to motd.nnrpd (used by INN >= 2.5.3)?

motd.innd does not exist in INN 2.5.2.


Under the name motd.nnrpd it is no longer a conffile in the new package
(as it is no longer shipped but it is used if present).

motd.nnrpd is still shipped in INN 2.5.3.

If I have a look at the list of files installed by Debian packages, I see:

INN 2.5.2:

/etc/news/motd.news
/usr/share/doc/inn2/examples/active
/usr/share/doc/inn2/examples/innreport.css
/usr/share/doc/inn2/examples/newsgroups


INN 2.5.3:

/usr/share/doc/inn2/examples/active
/usr/share/doc/inn2/examples/innreport.css
/usr/share/doc/inn2/examples/motd.innd
/usr/share/doc/inn2/examples/motd.nnrpd
/usr/share/doc/inn2/examples/newsgroups


I believe something should be done in the 2.5.3 Debian package: motd.innd and motd.nnrpd should be installed in the /etc/news directory!


Incidentally Russ Alberry reckons that the feature which requires this
file is almost never used anyway:
http://www.eyrie.org/~eagle/software/inn/docs/motd.news.html

Yep, that's true.  This feature is not wide-spread.


In Wheezy we will (all being well) then either have no file at all (if
it proclaimed "This is a sample MOTD file" under squeeze) or else have
a non-conffile that has been user created.

I think it would be best to have both motd.innd and motd.nnrpd because they are already shipped in the package. They should be installed in the right /etc/news directory.


I think this is the best for anyone who does use this file.  I'll try
coding it up but can anyone see any holes in this idea in the meantime ?

I hope the above comments will be of help.

--
Julien ÉLIE

« La perfection est atteinte non pas lorsqu'il n'y a plus rien à
  ajouter, mais lorsqu'il n'y a plus rien à retirer. » (Saint-
  Exupéry)


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to