Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 598545 - PostgreSQL Project Repos: Move, archives, and additions
Summary: PostgreSQL Project Repos: Move, archives, and additions
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Infrastructure
Classification: Unclassified
Component: Git (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Infrastructure
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-30 15:46 UTC by Aaron W. Swenson
Modified: 2018-01-15 04:06 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron W. Swenson gentoo-dev 2016-10-30 15:46:13 UTC
It looks like there are currently 3 repositories that belong to the PostgreSQL project.

 * proj/pgsql-patches.git
 * proj/postgresql/experimental.git
 * proj/postgresql/testing.git

I'd like for proj/pgsql-patches.git to be moved to proj/postgresql/pgsql-patches.git.

And then, have all 3 of those marked read-only, if there is such a way to do so.

I'd like for 2 new repos to be created:

 * proj/postgresql/eclass.git
 * proj/postgresql/eselect.git

I intend to copy the eselect branch from pgsql-patches into the new repo, and copy the eclass branch from my overlay on github.

Of course, I'm open to suggestions.
Comment 1 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2016-10-30 15:53:28 UTC
We don't support magical renames, so I'll just create a new repo for you so that you can push over the contents.

I'll start by creating the three new repositories, then I'll start altering old ones once you confirm that you've altered them any way you needed.

What ACLs should I set on the new repositories? Do you want me to alter existing ACLs? You don't seem to be on them. The current ones are:

repo proj/postgresql/experimental
	RW+ = dastergon@gentoo.org dev-zero@gentoo.org

repo proj/postgresql/testing
	RW+ = dastergon@gentoo.org dev-zero@gentoo.org

repo proj/pgsql-patches
	RW+	= @devs
Comment 2 Aaron W. Swenson gentoo-dev 2016-10-30 17:24:22 UTC
(In reply to Michał Górny from comment #1)
> We don't support magical renames, so I'll just create a new repo for you so
> that you can push over the contents.

OK.

> I'll start by creating the three new repositories, then I'll start altering
> old ones once you confirm that you've altered them any way you needed.

OK.

> What ACLs should I set on the new repositories? Do you want me to alter
> existing ACLs? You don't seem to be on them. The current ones are:
> 
> repo proj/postgresql/experimental
> 	RW+ = dastergon@gentoo.org dev-zero@gentoo.org
> 
> repo proj/postgresql/testing
> 	RW+ = dastergon@gentoo.org dev-zero@gentoo.org
> 
> repo proj/pgsql-patches
> 	RW+	= @devs

I can't think of any reason to restrict permissions any more than @devs for any of them.
Comment 3 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2016-10-30 18:23:12 UTC
remote: Initialized empty Git repository in /var/gitroot/proj/postgresql/eclass.git/
remote: Initialized empty Git repository in /var/gitroot/proj/postgresql/eselect.git/
remote: Initialized empty Git repository in /var/gitroot/proj/postgresql/patches.git/

Please let me know when I should restrict write accesses.
Comment 4 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2017-12-22 13:39:56 UTC
Ping. Anything else to be done here?
Comment 5 Aaron W. Swenson gentoo-dev 2018-01-14 21:00:56 UTC
Sorry for the delay. I think I have everything moved.
Comment 6 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2018-01-14 22:07:43 UTC
I've removed the old pgsql-patches repo and restricted experimental/testing to read-only. Is this all or do you want also the new proj/postgresql/patches to be read-only?
Comment 7 Aaron W. Swenson gentoo-dev 2018-01-15 02:49:14 UTC
(In reply to Michał Górny from comment #6)
> I've removed the old pgsql-patches repo and restricted experimental/testing
> to read-only. Is this all or do you want also the new
> proj/postgresql/patches to be read-only?

Let's keep proj/postgresql/patches writeable in case we need to move our patches back outside of gentoo.git.
Comment 8 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2018-01-15 04:06:30 UTC
Done then.