=> Bootstrap dependency digest>=20010302: found digest-20121220 WARNING: [bsd.prefs.mk] The package majordomo-devel-20060817 is missing DESTDIR support. WARNING: [license.mk] Every package should define a LICENSE. => Checksum SHA1 OK for majordomo-20060817.tar.gz => Checksum RMD160 OK for majordomo-20060817.tar.gz ===> Installing dependencies for majordomo-devel-20060817 => Tool dependency checkperms>=1.1: found checkperms-1.11 => Full dependency p5-MailTools>=1.67: found p5-MailTools-2.12nb1 => Full dependency p5-IO-stringy>=2.108: found p5-IO-stringy-2.110nb5 => Full dependency p5-MIME-tools>=4.119: found p5-MIME-tools-5.504nb1 => Full dependency p5-Date-Manip>=5.10: found p5-Date-Manip-6.34nb1 => Full dependency p5-Digest-SHA1-[0-9]*: found p5-Digest-SHA1-2.13nb5 => Full dependency p5-TimeDate>=1.15: found p5-TimeDate-1.20nb4 => Full dependency p5-HTML-Format-[0-9]*: found p5-HTML-Format-2.10nb2 => Full dependency p5-HTML-Tree-[0-9]*: found p5-HTML-Tree-5.03nb1 => Full dependency p5-Term-ReadLine-[0-9]*: found p5-Term-ReadLine-1.20nb4 => Full dependency p5-Text-Reflow>=1.04: found p5-Text-Reflow-1.09nb4 => Full dependency perl>=5.0: found perl-5.18.0 ===> Overriding tools for majordomo-devel-20060817 ===> Extracting for majordomo-devel-20060817 /bin/cat /usr/pkgsrc/wip/majordomo-devel/files/mj_config.common /usr/pkgsrc/wip/majordomo-devel/files/mj_config.postfix > /scratch/wip/majordomo-devel/work/majordomo/.mj_config ===> Patching for majordomo-devel-20060817 => Applying pkgsrc patches for majordomo-devel-20060817 => Verifying /usr/pkgsrc/wip/majordomo-devel/patches/patch-aa => Applying pkgsrc patch /usr/pkgsrc/wip/majordomo-devel/patches/patch-aa Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD$ | |--- installbin.orig 2002-01-22 08:09:18.000000000 +0100 |+++ installbin -------------------------- Patching file installbin using Plan A... Hunk #1 succeeded at 5. done => Verifying /usr/pkgsrc/wip/majordomo-devel/patches/patch-ab => Applying pkgsrc patch /usr/pkgsrc/wip/majordomo-devel/patches/patch-ab Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD$ | |--- bin/mj_confirm.orig 2004-10-03 22:03:41.000000000 +0200 |+++ bin/mj_confirm -------------------------- Patching file bin/mj_confirm using Plan A... Hunk #1 succeeded at 6. done => Verifying /usr/pkgsrc/wip/majordomo-devel/patches/patch-ac => Applying pkgsrc patch /usr/pkgsrc/wip/majordomo-devel/patches/patch-ac Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD$ | |--- bin/mj_shell.orig 2004-01-15 00:20:06.000000000 +0100 |+++ bin/mj_shell -------------------------- Patching file bin/mj_shell using Plan A... Hunk #1 succeeded at 7. done => Verifying /usr/pkgsrc/wip/majordomo-devel/patches/patch-ad => Applying pkgsrc patch /usr/pkgsrc/wip/majordomo-devel/patches/patch-ad Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD$ | |--- bin/mj_shutdown.orig 2002-04-20 21:09:52.000000000 +0200 |+++ bin/mj_shutdown -------------------------- Patching file bin/mj_shutdown using Plan A... Hunk #1 succeeded at 8. done => Verifying /usr/pkgsrc/wip/majordomo-devel/patches/patch-ae => Applying pkgsrc patch /usr/pkgsrc/wip/majordomo-devel/patches/patch-ae Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD$ | |--- bin/mj_wwwadm.orig 2006-07-02 10:00:04.000000000 +0200 |+++ bin/mj_wwwadm -------------------------- Patching file bin/mj_wwwadm using Plan A... Hunk #1 succeeded at 6. done => Verifying /usr/pkgsrc/wip/majordomo-devel/patches/patch-af => Applying pkgsrc patch /usr/pkgsrc/wip/majordomo-devel/patches/patch-af Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD$ | |--- bin/mj_wwwusr.orig 2004-10-13 02:56:32.000000000 +0200 |+++ bin/mj_wwwusr -------------------------- Patching file bin/mj_wwwusr using Plan A... Hunk #1 succeeded at 6. done => Verifying /usr/pkgsrc/wip/majordomo-devel/patches/patch-ag => Applying pkgsrc patch /usr/pkgsrc/wip/majordomo-devel/patches/patch-ag Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD$ | |--- bin/mj_email.orig 2004-09-30 07:04:19.000000000 +0200 |+++ bin/mj_email -------------------------- Patching file bin/mj_email using Plan A... Hunk #1 succeeded at 6. done => Verifying /usr/pkgsrc/wip/majordomo-devel/patches/patch-ah => Applying pkgsrc patch /usr/pkgsrc/wip/majordomo-devel/patches/patch-ah Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD$ | |--- bin/mj_enqueue.orig 2004-10-30 16:51:54.000000000 +0200 |+++ bin/mj_enqueue -------------------------- Patching file bin/mj_enqueue using Plan A... Hunk #1 succeeded at 9. done => Verifying /usr/pkgsrc/wip/majordomo-devel/patches/patch-ai => Applying pkgsrc patch /usr/pkgsrc/wip/majordomo-devel/patches/patch-ai Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD$ | |--- bin/mj_queuerun.orig 2004-10-03 22:01:30.000000000 +0200 |+++ bin/mj_queuerun -------------------------- Patching file bin/mj_queuerun using Plan A... Hunk #1 succeeded at 6. done => Verifying /usr/pkgsrc/wip/majordomo-devel/patches/patch-aj => Applying pkgsrc patch /usr/pkgsrc/wip/majordomo-devel/patches/patch-aj Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD$ | |--- bin/mj_queueserv.orig 2005-07-11 17:55:41.000000000 +0200 |+++ bin/mj_queueserv -------------------------- Patching file bin/mj_queueserv using Plan A... Hunk #1 succeeded at 4. done => Verifying /usr/pkgsrc/wip/majordomo-devel/patches/patch-ak => Applying pkgsrc patch /usr/pkgsrc/wip/majordomo-devel/patches/patch-ak Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD$ | |--- bin/mj_setup.orig 2004-09-30 07:04:19.000000000 +0200 |+++ bin/mj_setup -------------------------- Patching file bin/mj_setup using Plan A... Hunk #1 succeeded at 3. done => Verifying /usr/pkgsrc/wip/majordomo-devel/patches/patch-al => Applying pkgsrc patch /usr/pkgsrc/wip/majordomo-devel/patches/patch-al Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD$ | |--- bin/mj_trigger.orig 2005-06-19 19:04:30.000000000 +0200 |+++ bin/mj_trigger -------------------------- Patching file bin/mj_trigger using Plan A... Hunk #1 succeeded at 6. done ===> Creating toolchain wrappers for majordomo-devel-20060817 ===> Configuring for majordomo-devel-20060817 => Setting values in .mj_config => Replacing Perl interpreter in convertdb.pl convertlist.pl. => Checking for portability problems in extracted files cd /scratch/wip/majordomo-devel/work/majordomo && { echo;echo;echo;echo; } | /usr/pkg/bin/perl Makefile.PL ---------------------------------------------------------------------------- Language Enter "en" if you prefer to answer questions in English. Entrez "fr" si vous préférez répondre aux questions en Français. [en] -> ---------------------------------------------------------------------------- Majordomo 2 relies on a number of Perl modules. If some of the required modules are not installed on your system, the configuration process will stop, and you will be given instructions for installing the missing modules. Press the enter key to begin checking for modules. -> Checking for Mail::Internet (v1.3) ok: found v2.12 Checking for Mail::Header (v1.1) ok: found v2.12 Checking for MIME::Base64 (v2) ok: found v3.13 Checking for IO::Wrap (v1.101) ok: found v2.110 Checking for MIME::Tools (v4.119) ok: found v5.504 Checking for Data::Dumper (v2.07) ok: found v2.145 Checking for Date::Manip (v5.1) ok: found v6.34 Checking for CGI (v2.36) ok: found v3.63 Checking for Digest::SHA1 (any) ok: found v2.13 Checking for Socket (any) ok: found v2.009 Checking for IO::File (any) ok: found v1.16 Checking for IO::Handle (any) ok: found v1.34 Checking for Date::Format (v2.2) ok: found v2.24 Checking for Date::Parse (any) ok: found v2.30 Checking for DirHandle (any) ok: found v1.04 Checking for Safe (any) ok: found v2.35 Checking for POSIX (any) ok: found v1.32 Checking for Net::Domain (any) ok: found v2.20 Checking for File::Basename (any) ok: found v2.84 Checking for File::Copy (any) ok: found v2.26 Checking for Fcntl (any) ok: found v1.11 Checking for Carp (any) ok: found v1.29 Checking for Time::Local (any) ok: found v1.2300 Checking for HTML::FormatText (any) ok: found v2.10 Checking for HTML::TreeBuilder (any) ok: found v5.03 Checking for Text::Reflow (v1.04) ok: found v1.09 Checking for Time::HiRes (any) ok: found v1.9725 Checking for DB_File (v1.63) ok: found v1.827 Checking for DBI (v1.28) not found Checking for DBD::Pg (v1.13) not found Checking for DBD::mysql (v2.101) not found Checking for Sys::Syslog and headers ok Checking for Net::Config done, status not checked Checking for .mj_config ---------------------------------------------------------------------------- All of the required modules are available on your system. Next, the software must be configured. Press the enter key to continue. -> The .mj_config file contains the following configuration values: cgi_bin => database_backend => db domain => ... domains => gid => mjdomo2 ignore_case => 1 install_dir => /usr/pkg/majordomo lists_dir => /usr/pkg/majordomo/lists lockdir => /var/majordomo/tmp/locks maintain_mtaconfig => 0 majordomocf => /usr/pkg/etc/majordomo/majordomo.cf mta => postfix mta_separator => + queue_chld_ignore => 1 queue_concurrency => 3 queue_mode => 1 queue_timeout => 120 save_passwords => 0 sendmail_maintain_vut => 0 sepclear => 0 startperl => /usr/pkg/bin/perl tmpdir => /var/majordomo/tmp uid => mjdomo2 umask => 077 version => 13 wrappers => 1 wtmpdir => /tmp ---------------------------------------------------------------------------- The table that was just displayed contains the answers you gave when you configured Majordomo 2 on a previous occasion. Do you want to change any of your previous answers? [no] -> Building the wrapper programs...ok. Checking if your kit is complete... Looks good Writing Makefile for Majordomo Writing MYMETA.yml and MYMETA.json Majordomo 2 can always be installed by the root user. It may be possible for the majordomo user (mjdomo2) to install the software. Any barriers to this are listed here: Use of uninitialized value $u in numeric eq (==) at Makefile.PL line 214. * There is no password entry for the user "mjdomo2". Now you should run the following shell commands: make (expect several warnings about truncation to 8 characters) make test (report any problems to mj2-dev@lists.mj2.org) make install (usually as root, answering any questions that appear) After the software has been installed, save a copy of .mj_config, which contains your answers to the configuration questions. Finally, read the help file for domain administrators with this command: /usr/pkg/majordomo/bin/mj_shell -P help admin_domain