#57537 closed defect (fixed)
Move macports-legacy-support repository from cjones051073 user to macports organization
| Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | admin@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | server/hosting | Version: | |
| Keywords: | Cc: | cjones051073 (Chris Jones) | |
| Port: |
Description
It was mentioned in PR 2888 that the macports-legacy-support repository should be in the macports GitHub organization, rather than in the cjones051073 user account where it was created.
I think that's probably a good idea. The best way to do this is probably to transfer the repository using the repo's Settings screen on the GitHub web site. The person doing the transfer needs to have "create repo" privileges in the destination organization, which I do, so you could add me as an administrator of your repository and then I could do the transfer.
Change History (14)
comment:1 Changed 6 years ago by cjones051073 (Chris Jones)
comment:2 Changed 6 years ago by ryandesign (Ryan Carsten Schmidt)
I've accepted the invitation. I can't see the Settings tab yet. You may need to go in and adjust my privileges to give me access to that.
comment:3 Changed 6 years ago by cjones051073 (Chris Jones)
Where exactly do I need to go to do this ? I don't see it.
comment:4 Changed 6 years ago by cjones051073 (Chris Jones)
Unless I am completely overlooking it, the option to do what you suggest is not present.
Maybe the simplest approach is you fork the repo to your own area, then do the migration from there ?
comment:5 Changed 6 years ago by ryandesign (Ryan Carsten Schmidt)
I would rather not fork, because that leaves a mark on the GitHub web page for the forked repo that says it is a fork.
See if you can transfer the repository to the macports org. Go to the Settings page for the repo, scroll to the bottom, and click the Transfer button.
comment:7 Changed 6 years ago by cjones051073 (Chris Jones)
The port now needs updating to adapt....
comment:8 Changed 6 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | kencu added |
|---|
Ok great. And it looks like that preserved the relationship with kencu's existing fork of your repo; that's now marked as a fork of the moved repo. Though Ken may need to update his git remotes if he has that repo cloned anywhere; not sure.
I'll turn off the issue tracker for that repo, since I expect we'll want to use Trac for issues like we do for everything else, unless you object to that...
comment:9 follow-up: 11 Changed 6 years ago by cjones051073 (Chris Jones)
| Cc: | kencu removed |
|---|
No objections, of course...
port also now updated.
comment:10 Changed 6 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
There were a few more settings that we've used on other MacPorts repos, which I've made here as well: Disable issues, disable wiki, disable merge commits, prevent force pushes, allowed write access for all MacPorts developers.
comment:11 Changed 6 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to cjones051073:
port also now updated.
This unfortunately changes the distfile's checksums, because the repo owner is part of the root directory name in the tarball.
$ sudo port fetch --no-mirrors ---> Fetching distfiles for legacy-support ---> Attempting to fetch macports-legacy-support-0.5.tar.gz from https://github.com/macports/macports-legacy-support/tarball/v0.5 rschmidt@Untitled-Mac legacy-support $ sudo port checksum ---> Verifying checksums for legacy-support Error: Checksum (rmd160) mismatch for macports-legacy-support-0.5.tar.gz Error: Checksum (sha256) mismatch for macports-legacy-support-0.5.tar.gz Error: Checksum (size) mismatch for macports-legacy-support-0.5.tar.gz Error: Failed to checksum legacy-support: Unable to verify file checksums Error: See /opt/local/var/macports/logs/_Users_rschmidt_macports_macports-ports-svn-trunk-new_devel_legacy-support/legacy-support/main.log for details. Error: Follow https://guide.macports.org/#project.tickets to report a bug. Error: Processing of port legacy-support failed
comment:12 Changed 6 years ago by ryandesign (Ryan Carsten Schmidt)
No need to increase the port's revision since the code hasn't changed, just need to change the dist_subdir, until a new version is released.
Thanks. I've sent you a request to become a collaborator. Not sure though it this is enough for what you need ?