Wishes for new subversion repositories should be added to this bug. There are three types: (a) brand new repositories (b) convert cvs-modules to svn repositories (c) import repositories from somewhere else (e.g. berlios) Please add some information about the repository. name: type: access:
and please add where to fetch the external dumps from (in case of an repository import)
name: hardened type: This would be a clean repository, but I do have a couple projects I'd like to see imported to this repository. The projects are currently in svn on my own server. access: hardened (for when ACL is implemented I guess?)
(In reply to comment #2) > name: hardened created. > type: This would be a clean repository, but I do have a couple projects I'd like to see imported to this > repository. The projects are currently in svn on my own server. If you need help in importing without losing the history, you should contact trapni, who can assist. > access: hardened (for when ACL is implemented I guess?) Sure. So I don't have to ask a second time.
name: keychain type: b, from gentoo-src/keychain access: open
(In reply to comment #3) > (In reply to comment #2) > > name: hardened > > created. > > > type: This would be a clean repository, but I do have a couple projects I'd > like to see imported to this > > repository. The projects are currently in svn on my own server. > > If you need help in importing without losing the history, you should contact > trapni, who can assist. > > > access: hardened (for when ACL is implemented I guess?) > > Sure. So I don't have to ask a second time. Thanks
name: gentoolkit type: b, entire gentoolkit repository (it's a top-level like gentoo-src) access: open
name: baselayout type: b, from gentoo-src/rc-scripts access: open
name: votify type: b, from gentoo-src/votify access: open
(In reply to comment #4) > name: keychain done
(In reply to comment #6) > name: gentoolkit done
(In reply to comment #7) > name: baselayout done
(In reply to comment #8) > name: votify done
name: gentoo-syntax type: a, from svn://svn.berlios.de/gentoo-syntax/trunk access: open ciaran considers this a deadend, but I'll fork it and continue development
(In reply to comment #13) > name: gentoo-syntax I created an empty repository. Now you can simply svn add the trunk from svn://svn.berlios.de/gentoo-syntax/trunk
name: tenshi type: c (will supply an svn db) access: open
(In reply to comment #15) > name: tenshi created > type: c (will supply an svn db) imported
name: glsr type: A access: myself, hadfield@g.o and allanonjl@g.o This repo is for the second generation (rewrite) of the glsr (a.k.a GLEP 15)
name: sandbox type: b, from gentoo-src/sandbox access: azarah, ferringb, genone, vapier
(In reply to comment #17) > name: glsr done
(In reply to comment #18) > name: sandbox That one must be renamed to something else, as an overall 'sandbox' for testing svn etc. already exists. Proposals: gentoo-sandbox, portage-sandbox, etc. Please pick one.
(In reply to comment #20) > (In reply to comment #18) > > name: sandbox > > That one must be renamed to something else, as an overall 'sandbox' for testing > svn etc. already exists. Proposals: gentoo-sandbox, portage-sandbox, etc. > Please pick one. hmm, k. Make it path-sandbox then. also, scratch the access list, it can be open.
(In reply to comment #21) > hmm, k. Make it path-sandbox then. also, scratch the access list, it can be open. done
Name: gentoo-perl Type: new is fine access: open. if we discover perl trolls we can revisit this with a box of cookies in hand :)
(In reply to comment #23) > Name: gentoo-perl done
name: linux-patches type: brand new access: dsd, gregkh, spock, eradicator, johnm, plasmaroo
(In reply to comment #25) > name: linux-patches done.
Since about yesterday path-sandbox have been busted (second time after second time I actually committed more than one thing in a few hours) with: ---- svn: Berkeley DB error while opening 'copies' table for filesystem /var/svnroot/path-sandbox/db: Cannot allocate memory svn: bdb: Lock table is out of available locker entries ---- Can we please: 1) Get it fixed, and the backend changed to fsfs (pretty please not berkdb anymore) 2) Get it removed totally if 1) is not possible. Either one will do, just please let me know which. Thanks.
name: gentoo-bashcomp type: c (will supply dump from berlios as soon as I figure out how) access: open
(In reply to comment #28) > name: gentoo-bashcomp > type: c (will supply dump from berlios as soon as I figure out how) > access: open Just now saw comment #27. If possible please use fsfs for this repo as well. I used fsfs in GLEP 36 for exactly this reason. Unfortunately that happens with a db filesystem quite often. Not only is that annoying to the developer, but I imagine it'd get quite old for the admin having to 'svnadmin recover' it.
(In reply to comment #29) > Just now saw comment #27. If possible please use fsfs for this repo as well. I > used fsfs in GLEP 36 for exactly this reason. Unfortunately that happens with a > db filesystem quite often. Not only is that annoying to the developer, but I > imagine it'd get quite old for the admin having to 'svnadmin recover' it. I must admit, I'm a noob in administrating svn and trapni isn't available currently. But I'm all for kicking that stupid berkdb and using something more stable. Is it okay to delay your requests for some days until we changed over to fsfs completely?
(In reply to comment #30) > I must admit, I'm a noob in administrating svn and trapni isn't available > currently. But I'm all for kicking that stupid berkdb and using something more > stable. It's actually pretty easy to migrate existing db repos to fsfs. Not too different from loading a repo dump (just a few added steps). Just dump the repo to a file, move the repo directory out of the way, create a new repository of the same name with '--fs-type fsfs' and then svnadmin load the dump file. Those procedures aren't specific with fs migration, but pretty much anything requiring "migration". > Is it okay to delay your requests for some days until we changed over to fsfs > completely? Certainly.
I can wait as well. Hopefully I did not come off as harsh or ungrateful, but having to whine every day or two about a broken repo is not fun for me, and I assume even less for Infra :-) Like I said - if there is some problems with fsfs (from what I heard it works very good, but you never know), then I will understand, but rather go back to cvs. If not, then great, and another day or two waiting is fine (just please no berkdb ;p). Thanks guys.
(In reply to comment #31) > It's actually pretty easy to migrate existing db repos to fsfs. Not too > different from loading a repo dump (just a few added steps). Thanks, I found it out myself during this evening svn hacking session :-) See my summary at -core. You may provide me now an svn-dump of your repository, so that I can install in.
name: php type: brand new access: php, apache herds Ta, Stu
(In reply to comment #34) > name: php > type: brand new > access: php, apache herds new group created, repository done.
name: bugday type: brand new access: kloeri,gurligebis,tannewt Repository will be used for the bugday.g.o code.
(In reply to comment #36) > name: bugday > type: brand new > access: kloeri,gurligebis,tannewt Done
name: portage type: new repo access: genone, jstubbs, ferringb, vapier
(In reply to comment #38) > name: portage Done.
name: gentoo-vdr type: brand new repository access: zzam (more people coming soon)
(In reply to comment #40) > name: gentoo-vdr > type: brand new repository > access: zzam (more people coming soon) Repository created, but currently without access-restriction. Do you really need it? If you want to quickly involve more devs, it would be easier for everybody not to restrict access.
name: harmonious type: new access: myself and hadfield
(In reply to comment #42) > name: harmonious > type: new > access: myself and hadfield Created, without access restriction after talking to port001 and hadfield.
(In reply to comment #41) > (In reply to comment #40) > > name: gentoo-vdr > > type: brand new repository > > access: zzam (more people coming soon) > > Repository created, but currently without access-restriction. Do you really > need it? If you want to quickly involve more devs, it would be easier for > everybody not to restrict access. Thanks. Free access is okay, restrictions are not necessary at the moment. But: When commiting something I get:
(In reply to comment #41) > (In reply to comment #40) > > name: gentoo-vdr > > type: brand new repository > > access: zzam (more people coming soon) > > Repository created, but currently without access-restriction. Do you really > need it? If you want to quickly involve more devs, it would be easier for > everybody not to restrict access. Thanks. Free access is okay, restrictions are not necessary at the moment. But: When commiting something I get: Übertrage Daten .......................svn: Übertragen fehlgeschlagen (Details folgen): svn: Can't create directory '/var/svnroot/gentoo-vdr/db/transactions/0-1.txn': Permission denied
(In reply to comment #44) > But: When commiting something I get: > Permission denied Well, recruiters forgot to add you to the svn-group. This is fixed now.
name: gentoo-alt type: b (gentoo-projects/bsd/fbsd/overlay -> gentoo-alt/trunk/overlay) access: unrestricted For merged gentoo/alt working overlay.
(In reply to comment #46) > name: gentoo-alt done. > type: b (gentoo-projects/bsd/fbsd/overlay -> gentoo-alt/trunk/overlay) moved into the overlay
Gnome herd would like a svn repo to work on development releases and prepare them for the official tree. Name:gnome Type:Brand New Access:allanonjl, dang, foser, joem, leonardop, obz, spider
(In reply to comment #48) > Name:gnome Sorry for the delay. Finally created.
(In reply to comment #15) > name: tenshi > type: c (will supply an svn db) > access: open This is no longer needed. Could you please remove it? thx
name: dietlibc type: import from svn+ssh://dev.gentoo.org/home/phreak/repos/dietlibc access: open
Can I get cardoe and compenerd added to the access list for the gnome repo?
(In reply to comment #50) > (In reply to comment #15) > > name: tenshi > This is no longer needed. Could you please remove it? thx Removed.
(In reply to comment #51) > name: dietlibc > type: import from svn+ssh://dev.gentoo.org/home/phreak/repos/dietlibc > access: open created. You should be able to import yourself or provide a dump (svnadmin dump $path_to_repository | bzip2 --best --stdout > dietlibc-dump.bz2 )
(In reply to comment #52) > Can I get cardoe and compenerd added to the access list for the gnome repo? They have been added to the group some time ago.
FOr the kbase project I'm requesting a repo as well where developers can develop the kbase, both content before the technology is found, as well as technology. name: kbase type: a (brand new repo) access: limited to developers (any dev may use it as far as I'm concerned, but surely the kbase devs) tia
(In reply to comment #56) > name: kbase created.
"I wish for a subversion repository": name: python type: for the python team to maintain the growing list of patches for the gentoo python package. access: liquidx, kloeri, marienz, pythonhead Thanks!
*** Bug 144139 has been marked as a duplicate of this bug. ***
(In reply to comment #58) > name: python Created, but I named it 'gentoo-python', like 'gentoo-perl' we already have.
thanks pylon
I have a few. name: catalyst type: b, gentoo/src/catalyst access: rocket, wolf31o2, agaffney name: genkernel type; b, gentoo/src/genkernel_bradmssw access: rocket, wolf31o2, agaffney name: livecd-tools type: b, gentoo/src/livecd-tools access: rocket, wolf31o2, agaffney name: hwdata type: b, gentoo/src/hwdata access: rocket, wolf31o2, agaffney I think that's it for now.
(In reply to comment #62) > I have a few. > > name: catalyst > type: b, gentoo/src/catalyst > access: rocket, wolf31o2, agaffney Done. > name: genkernel > type; b, gentoo/src/genkernel_bradmssw > access: rocket, wolf31o2, agaffney Done. Name is 'genkernel' as requested. > name: livecd-tools > type: b, gentoo/src/livecd-tools > access: rocket, wolf31o2, agaffney Done. Group is 'svnlivecdtool' > name: hwdata > type: b, gentoo/src/hwdata > access: rocket, wolf31o2, agaffney Done.
I've got a CVS->SVN convert request. name: gli type: b, gentoo/src/installer access: just make it open, and we'll personally beat anyone who does Bad Things(TM) Please make gentoo/src/installer read-only or remove it once the svn repo is up and running. Thanks.
(In reply to comment #64) > I've got a CVS->SVN convert request. > > name: gli > type: b, gentoo/src/installer > access: just make it open, and we'll personally beat anyone who does Bad > Things(TM) Andrew and i spoke about this on IRC. Allowed commiteers are him, wolf31o2, mdisney and codeman. > Please make gentoo/src/installer read-only or remove it once the svn repo is up > and running. Thanks. done.
Thanks
Hey, It would be nice to get a new svn repository. Name: brutalis Type: a brand new repository Access: spb and eroyf It's going to be for some scripts to do automatic QA scans of the whole portage tree. Regards, Alex
Just forget about my request. I have found a solution :) Best regards, Alex
name: autoepatch type: a access: open on the "I'll kill misbehaving" rule :)
(In reply to comment #69) > name: autoepatch > type: a > access: open on the "I'll kill misbehaving" rule :) done.
*** Bug 148085 has been marked as a duplicate of this bug. ***
from bug 148085: > name: kde > type: brand new > access: open to all devs presently. all created.
News repository for GLEP 42 Initial data = None Read/Write = All Gentoo Devs Belongs on s.g.o as well.
*** Bug 161946 has been marked as a duplicate of this bug. ***
From bug 161946: > News repository for GLEP 42 > Initial data = None > Read/Write = All Gentoo Devs > Belongs on s.g.o as well. Name = gentoo-news. Created now, needs to go on sources.g.o still.
name: gentoo-dev-summary type: a access: araujo, jokey
* name: adopt-a-dev * type: a * access: Adopt-a-dev project members (diox, christel, tsunam) -> motivation: Adopt-a-dev information is sensitive. That's why i'd like this information to be restricted. If this is not possible, the restriction to devs only would be fine too. Tough i'd prefer the first.
gentoo-dev-summary: created. why do you want to lock it down to just two developers, I don't see any privacy requirements in material from gentoo-dev? I've left it open to all developers for now. should it be replicated to anonsvn/sources.g.o? adopt-a-dev: created and locked down per request (RW to those 3 users, and no access to anybody else). If you end up putting only code in here, ensure that you do not have any passwords, and then let's open up the codebase instead.
pybugz SVN Code for PyBugz goes here. RW access to all devs, s.g.o would be nice too No existing repo (that I can find) I'll just import the current code and work on it. -Alec
(In reply to comment #80) > pybugz Created. And my apologies for the really long delay.
*** Bug 182271 has been marked as a duplicate of this bug. ***
Update product
Could you please convert gentoo/src/releng to a new releng SVN repo? Access would need to be: wolf31o2, armin76, angelos, kingtaco, phreak, dertobi123, ranger, agaffney, redhatter, kumba, vapier Thanks
gentoo/src/releng converted to SVN repo named 'releng'.
name: qmail type: a access: qmail herd
Since you converted catalyst/hwdata/livecd-tools/genkernel to git, you can probably remove the SVN versions of them from both the server and sources.gentoo.org...
pybugz repository can be removed. It hasn't been used for a couple of years and it lives now in http://code.google.com/p/pybugz/
brand new repository for media Screenshots from the 2009 Screenshot contest Gentoo related audio and video files name: media type: svn access: pr
idlor, do we have any svn left or can we close this? -A
There are still some repos but I don't have enough time to work on it atm.
SVN service has been discontinued.