pkgsrc-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: pkg/25165
Am 20.04.2005 um 20:53 Uhr +0000 schrieb bouyer%netbsd.org@localhost:
Synopsis: The mailman 2.1.4 package in incomplete in various places
the maillan package was since updated to 2.1.5. Does the current package still
have problems ?
Well, let's see...
Am 13.04.2004 um 16:17 Uhr +0200 schrieb Hauke Fath:
The mailman 2.1.4 package installs an incomplete setup that
has to be manually fixed up in several places. Apart from the
file permissions problem discussed in PR pkg/24041,
That was fixed in Feb 05, AFAICS.
I have come across:
(1) The conversion of a 2.0 database is far from trivial. See
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.032.htp
for details. The MESSAGE should note this if a /var/spool/mailman
direcory is present and populated.
Still no hint in MESSAGE for updates from 2.0. While pkgsrc is
generally weak in that area ("Shoot^WDeinstall first, ask questions
later"), that upgrade is exceptionally messy. At least, MESSAGE
should point to the Mailman FAQ entry.
(2) Mailman 2.1.4 wants a /usr/pkg/lib/mailman/bin/qrunner process
active for queuing list mail - see /usr/pkg/share/doc/mailman/INSTALL,
ch.4. The package does not come with a rc.d mailman script.
Fixed, from looking at files/mailman.sh.
(3) The sample crontab for user mailman should probably go to
PKGBASE/share/examples/mailman (EGDIR).
You put the sample crontab into ${EXECDIR}/cron -- why? Do we keep
fstab.sample in /sbin?
I'll update our mailman installation next week and report my experience.
hauke
--
/~\ The ASCII Ribbon Campaign Hauke Fath
\ / No HTML/RTF in email Institut für Nachrichtentechnik
X No Word docs in email TU Darmstadt
/ \ Respect for open standards Ruf +49-6151-16-3281
Home |
Main Index |
Thread Index |
Old Index