[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100716203750.GD17993@openwall.com>
Date: Sat, 17 Jul 2010 00:37:50 +0400
From: Anatoly Pugachev <mator@...nwall.com>
To: owl-users@...ts.openwall.com
Subject: Re: update from cvs
On Sun, Aug 09, 2009 at 10:57:44AM +0400, Solar Designer wrote:
> On Wed, Aug 05, 2009 at 11:41:33AM +0400, Anatoly Pugachev wrote:
> > How do i update my /usr/src/world from the cvs tree ?
>
> Owl/doc/DOWNLOAD, also available via the web at:
>
> http://www.openwall.com/Owl/DOWNLOAD.shtml
>
> gives some basic information for accessing our FTP mirrors and anoncvs.
>
> As it relates to your specific question - namely, updating an existing
> local copy of the Owl CVS tree - you may do it as follows:
>
> su - build
> CVSROOT=:pserver:anoncvs:anoncvs@...ncvs.owl.openwall.com:/cvs make checkout
>
> or maybe:
>
> su - build
> export CVS_RSH=ssh CVSROOT=anoncvs@...ncvs.owl.openwall.com:/cvs
> cd native/Owl
> cvs -z3 up -P
> anoncvs@...ncvs.owl.openwall.com's password: <type anoncvs here>
>
> Lots of other variations are possible as well.
>
> Our "native" tree is quite small - just 2 MB gzipped - so if you're on a
> fast link, you may as well re-download native.tar.gz from one of the FTP
> mirrors. And you do in fact have to access an FTP mirror in order to
> update the "sources" tree as well (which contains mostly the original
> tarballs of software that we use in Owl). You may do it like this:
>
> su - build
> lftp ftp://ftp.fr.openwall.com/pub/Owl/current/
> mirror -Lev sources
>
> If you do not intend to rebuild Owl from source, you will need to get
> and keep up-to-date the RPMS directory for your architecture instead of
> the "sources" tree, like this:
>
> su - build
> lftp ftp://ftp.fr.openwall.com/pub/Owl/current/i386/
> mirror -ev RPMS
well, docs (at http://openwall.com/Owl/BUILD.shtml) and your
instructions suggest to use 'build' user, but my freshly owl openvz
install (from owl-current-20100323-x86_64.tar.gz template) have
sources:sources as owner for /usr/src (and below), so 'build' username
can't create any files in it's $HOME directory. And even giving a group
access as 'chmod g+w /usr/src/world' would not help (make will complain
of not ownership of a current directory). So I'm rebuilding as 'sources'
username now... Do we need to change docs so they will tell to use
'sources' username instead of 'build' now?
Thanks.
--
Anatoly Pugachev
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
