[Systers-dev] steps to do after docu

[k roy]

Hello,

I finished installing Mailman and customised it according to Systers
configuration by getting the branch code. There were a few typos and missing
sudos which I corrected in the wiki after creating a new login. As the login
is not moderated so I believe this is allowed.
The installation guide says to check the GUI after the install is finished.
Can anyone please specify how I can do that?

Thanking you,
~kr0y.

On Thu, Apr 16, 2009 at 1:26 AM, Vidhu <vidhu2366 at gmail.com> wrote:

> >
> > Some how i succeded pulling the files
>
>
> The output of
>
>  sudo bzr checkout --lightweight lp:systers .
>
> was
>
> root at vidhoon-laptop:/usr/local/mailman# sudo bzr checkout --lightweight
> lp:systers .
> You have not informed bzr of your launchpad login. If you are attempting a
> write operation and it fails, run "bzr launchpad-login YOUR_ID" and try
> again.
> Format <RepositoryFormatKnit1> for
> http://bazaar.launchpad.net/%7Esysters/systers/devel/.bzr/ is deprecated -
> please use 'bzr upgrade' to get better performance
> Conflict adding file Mailman/Cgi/admindb.py.  Moved existing file to
> Mailman/Cgi/admindb.py.moved.
> Conflict adding file Mailman/Cgi/create.py.  Moved existing file to
> Mailman/Cgi/create.py.moved.
> Conflict adding file Mailman/Cgi/listinfo.py.  Moved existing file to
> Mailman/Cgi/listinfo.py.moved.
> Conflict adding file Mailman/Cgi/options.py.  Moved existing file to
> Mailman/Cgi/options.py.moved.
> Conflict adding file Mailman/Cgi/subscribe.py.  Moved existing file to
> Mailman/Cgi/subscribe.py.moved.
> Conflict adding file Mailman/Deliverer.py.  Moved existing file to
> Mailman/Deliverer.py.moved.
> Conflict adding file Mailman/HTMLFormatter.py.  Moved existing file to
> Mailman/HTMLFormatter.py.moved.
> Conflict adding file Mailman/Handlers/Decorate.py.  Moved existing file to
> Mailman/Handlers/Decorate.py.moved.
> Conflict adding file Mailman/Handlers/Moderate.py.  Moved existing file to
> Mailman/Handlers/Moderate.py.moved.
> Conflict adding file Mailman/ListAdmin.py.  Moved existing file to
> Mailman/ListAdmin.py.moved.
> Conflict adding file Mailman/MailList.py.  Moved existing file to
> Mailman/MailList.py.moved.
> Conflict adding file Mailman/OldStyleMemberships.py.  Moved existing file
> to
> Mailman/OldStyleMemberships.py.moved.
> Conflict adding file Mailman/Queue/CommandRunner.py.  Moved existing file
> to
> Mailman/Queue/CommandRunner.py.moved.
> Conflict adding file Mailman/SecurityManager.py.  Moved existing file to
> Mailman/SecurityManager.py.moved.
> Conflict adding file Mailman/mm_cfg.py.  Moved existing file to
> Mailman/mm_cfg.py.moved.
> Conflict adding file cron/checkdbs.  Moved existing file to
> cron/checkdbs.moved.
> Conflict adding file templates/en/options.html.  Moved existing file to
> templates/en/options.html.moved.
> Conflict adding file templates/en/subscribeack.txt.  Moved existing file to
> templates/en/subscribeack.txt.moved.
>
> Have I got the desired result. I believe that I have got.
>
> -
> Vidhoon V
>
>
> To unsubscribe from this conversation, send email to <
> systers-dev+steps+unsubscribe at systers.org<systers-dev%2Bsteps%2Bunsubscribe at systers.org>>
> or visit <
> http://systers.org/mailman/options/systers-dev?override=3&preference=0>
> To contribute to this conversation, use your mailer's reply-all or
> reply-group command or send your message to systers-dev+steps at systers.org<systers-dev%2Bsteps at systers.org>
> To start a new conversation, send email to <systers-dev+new at systers.org<systers-dev%2Bnew at systers.org>
> >
> To unsubscribe entirely from systers-dev, send email to <
> systers-dev-request at systers.org> with subject unsubscribe.
>



-- 
~ Once you have flown, you will walk the earth with your eyes turned
skyward, for there you have been, there you long to return --Da Vinci