Bug 4355 - [wish] access to the latest SVN directory over RSYNC (or equivalent)
Summary: [wish] access to the latest SVN directory over RSYNC (or equivalent)
Status: RESOLVED OLD
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: Others (show other bugs)
Version: unspecified
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Sysadmin Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-31 01:41 CET by Kamil Rytarowski
Modified: 2014-05-08 18:07 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Kamil Rytarowski 2012-01-31 01:41:37 CET
Description of problem:
Please give access to the SVN repository ( http://svnweb.mageia.org/ ) over RSYNC (or equivalent) protocol.

It was proposed already in the sysadmin-mailinglist as a wish-feature initially for svn-searcher.
Comment 1 Nicolas Vigier 2012-01-31 01:52:30 CET
Why do you need to access it with rsync protocol ?

CC: (none) => boklm

Comment 2 Kamil Rytarowski 2012-01-31 02:06:43 CET
I wish I synchronized just the data I need - to keep only the revision I need... with RSYNC syncing ~10,000 SPEC files from the Cauldron directory-tree is very simple and not so abusive. And this is just ~30 MB!

Mirroring the whole SVN (using svnsync or equivalent) isn't a good solution (mainly the disk-space is a problem).

I need only the latest revision and the needed needed files (*.spec) in certain directories (current).

I haven't found any simple (and not abusive for a client and the server) way to do it with SVN.

I need the data for this http://kamil.mageia.org.pl/svnsearch.cgi (pre-alpha preview).
Comment 3 Michael Scherer 2012-02-07 22:39:21 CET
I doubt rsync will permit that, since this would mean access to the raw repository, and therefor, would sync everything.

CC: (none) => misc

Kamil Rytarowski 2012-10-21 15:55:17 CEST

Status: NEW => RESOLVED
Resolution: (none) => OLD

Nicolas Vigier 2014-05-08 18:07:16 CEST

CC: boklm => (none)


Note You need to log in before you can comment on or make changes to this bug.