On Wed, Mar 20, 2013 at 19:27 -0700, Christian Theune wrote:
On 2013-03-20 23:59:21 +, Christian Theune said:
I'm currently re-initializing my own mirror. This basically can be
run in-place by just removing the existing state data and calling
my sync script (bsn-mirror) instead of
On 20 March 2013 19:27, Christian Theune c...@gocept.com wrote:
On 2013-03-20 23:59:21 +, Christian Theune said:
I'm currently re-initializing my own mirror. This basically can be run
in-place by just removing the existing state data and calling my sync script
(bsn-mirror) instead of
On Mar 21, 2013, at 3:28 AM, holger krekel hol...@merlinux.eu wrote:
On Wed, Mar 20, 2013 at 19:27 -0700, Christian Theune wrote:
On 2013-03-20 23:59:21 +, Christian Theune said:
I'm currently re-initializing my own mirror. This basically can be
run in-place by just removing the
Hi,
I'm slowly wrapping up my sprint. Here's what happened today:
- fixed some errors reported by users
- allow running a non-deleting mirror (with the hint that official ones
must not do this)
- add config file handling to avoid complicated command lines including
some documentation how to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Theune wrote:
Hi,
I'm slowly wrapping up my sprint. Here's what happened today:
- fixed some errors reported by users - allow running a non-deleting
mirror (with the hint that official ones must not do this) - add
config file
Hi,
as you might be aware, I've done my share on bitching about my mirror
(f.pypi.python.org) breaking.
I have picked pep381client apart yesterday and rebuilt it - mostly from
ground up.
You can find a working version here:
https://bitbucket.org/ctheune/bandersnatch
The focus has been on
On 2013-03-20 23:59:21 +, Christian Theune said:
I'm currently re-initializing my own mirror. This basically can be run
in-place by just removing the existing state data and calling my sync
script (bsn-mirror) instead of pep381run with the same parameters.
This worked nicely for me -
