Hey guys, So I think ABS is ready to move to rsync. The final piece, server-side ABS-tree generation, has been completed with help from Jason. I've just committed the svn2abs script to git - take a look at it to get the full details, but in short it does a checkout of the svn repo (or updates a pre-existing checkout), extracts the repo information into the expected format for an ABS tree and stores this in a tmp dir, then rsyncs /srv/abs to the tmp dir to update it. I've tested this a bit on gerolde, and ironed out a few of my initial bugs - the ABS tree currently sitting in /srv/abs was generated using that script. I've made packages (and src PKGBUILD) available at http://dev.archlinux.org/~travis/pkg/ if anyone wants to muck around. The [abs] rsync stanza is currently only set to allow my IP address, so you won't yet be able to sync with the new abs unless you get your IP added (or remove the restriction altogether). svn2abs is designed to be run as a cron-job, maybe once/twice a day or something along those lines to keep /srv/abs relatively fresh. I'm pretty confident in the state of ABS now, so I'm wondering how we'll go about integrating this onto Gerolde, then pushing it out to the users. Things we'll need to do to get this integrated and pushed out: 1) install abs-2.0 on gerolde 2) modify rsync stanza for [abs] in /etc/rsyncd.conf to allow anyone 3) add cronjob for svn2abs 4) push to users I'll need an enabler to handle 1-3, and once it's setup I can take it from there. Anyway, muck around, have fun, see if I missed anything. -- Travis
I am around most of today. Hit me up on jabber. On 4/12/08, Travis Willard <travis@archlinux.org> wrote:
Hey guys,
So I think ABS is ready to move to rsync.
The final piece, server-side ABS-tree generation, has been completed with help from Jason.
I've just committed the svn2abs script to git - take a look at it to get the full details, but in short it does a checkout of the svn repo (or updates a pre-existing checkout), extracts the repo information into the expected format for an ABS tree and stores this in a tmp dir, then rsyncs /srv/abs to the tmp dir to update it.
I've tested this a bit on gerolde, and ironed out a few of my initial bugs - the ABS tree currently sitting in /srv/abs was generated using that script.
I've made packages (and src PKGBUILD) available at http://dev.archlinux.org/~travis/pkg/ if anyone wants to muck around. The [abs] rsync stanza is currently only set to allow my IP address, so you won't yet be able to sync with the new abs unless you get your IP added (or remove the restriction altogether).
svn2abs is designed to be run as a cron-job, maybe once/twice a day or something along those lines to keep /srv/abs relatively fresh.
I'm pretty confident in the state of ABS now, so I'm wondering how we'll go about integrating this onto Gerolde, then pushing it out to the users. Things we'll need to do to get this integrated and pushed out: 1) install abs-2.0 on gerolde 2) modify rsync stanza for [abs] in /etc/rsyncd.conf to allow anyone 3) add cronjob for svn2abs 4) push to users
I'll need an enabler to handle 1-3, and once it's setup I can take it from there.
Anyway, muck around, have fun, see if I missed anything.
--
Travis
On Sat, Apr 12, 2008 at 12:18 PM, eliott <eliott@cactuswax.net> wrote:
I am around most of today. Hit me up on jabber.
Done and done - thanks to eliott, we've gotten the necessary infrastructure set up on gerolde. I'll be pushing a new ABS package to testing shortly. ;)
On 4/12/08, Travis Willard <travis@archlinux.org> wrote:
On Sat, Apr 12, 2008 at 12:18 PM, eliott <eliott@cactuswax.net> wrote:
I am around most of today. Hit me up on jabber.
Done and done - thanks to eliott, we've gotten the necessary infrastructure set up on gerolde. I'll be pushing a new ABS package to testing shortly. ;)
Hooray! One step closer to CVS choppy choppy.
2) modify rsync stanza for [abs] in /etc/rsyncd.conf to allow anyone
I think this might have a negative impact on our mirroring. We only allow 10 connections total for rsync mirrors and if any large number of those are used by ABS users, our mirrors will have problems syncing for sure. It looks like we can up the "max connections" option for just the abs module if we provide it a different "lock file". I have to leave now for a previous commitment but please let me know if this needs implemented. Dale
Good call dale. I will add the stanzas, and see how she handles. On 4/12/08, Dale Blount <dale@archlinux.org> wrote:
2) modify rsync stanza for [abs] in /etc/rsyncd.conf to allow anyone
I think this might have a negative impact on our mirroring. We only allow 10 connections total for rsync mirrors and if any large number of those are used by ABS users, our mirrors will have problems syncing for sure.
It looks like we can up the "max connections" option for just the abs module if we provide it a different "lock file".
I have to leave now for a previous commitment but please let me know if this needs implemented.
Dale
Am Samstag, 12. April 2008 17:16:41 schrieb Travis Willard:
Anyway, muck around, have fun, see if I missed anything.
This might not be important now, but it would be nice to checkout multiple arches. Think about the "any"-arch we'll have in future. -- Pierre Schmitz Clemens-August-Straße 76 53115 Bonn Telefon 0228 9716608 Mobil 0160 95269831 Jabber pierre@jabber.archlinux.de WWW http://www.archlinux.de
On Sun, Apr 13, 2008 at 12:07 PM, Pierre Schmitz <pierre@archlinux.de> wrote:
Am Samstag, 12. April 2008 17:16:41 schrieb Travis Willard:
Anyway, muck around, have fun, see if I missed anything.
This might not be important now, but it would be nice to checkout multiple arches. Think about the "any"-arch we'll have in future.
Hm. This is a good idea. I will add something in my TODO and ponder this
participants (4)
-
Dale Blount
-
eliott
-
Pierre Schmitz
-
Travis Willard