RAD Game Tools License Concern - Immediate Action Required
Re: RAD Game Tools License Concern - Immediate Action Requir
Hoikas and I are happy with the results of CW's current script. Barring any issues found by others we'll push the results of that script to the H-uru master as soon as the simplified script exists for all our forks to use.
Re: RAD Game Tools License Concern - Immediate Action Requir
Different result here with Git 1.7.4 on Windows.
Expected result after updating to 1.8.0.
Thanks for all the work.
Expected result after updating to 1.8.0.
Thanks for all the work.
Re: RAD Game Tools License Concern - Immediate Action Requir
I just tried the git-only conversion script on a clone of the H-uru/Plasma repo. I got a message about "possible duplicates", but the HEAD SHA is b3976524ee406256655183fd25a49d984138dfb0, which matches the expected output according to binkbegone.sh. Looking at the logs those 'duplicates' might actually be correct (a closed PR and then a reopened one after a rebase).
It does look like github refuses to let me push up changes to the refs for PRs. I'll ask Hoikas to poke them about how to ensure the old history isn't accessible through closed pulls.
EDIT: the new history is presently live on H-uru/Plasma. I have a backup of the old one in case we decide more tweaks are needed.
EDIT2: I just converted the Gehn fork without getting the duplicates warning. It's quite possible that issue only affects H-uru repo, and if so I'm not going to worry about it.
It does look like github refuses to let me push up changes to the refs for PRs. I'll ask Hoikas to poke them about how to ensure the old history isn't accessible through closed pulls.
EDIT: the new history is presently live on H-uru/Plasma. I have a backup of the old one in case we decide more tweaks are needed.
EDIT2: I just converted the Gehn fork without getting the duplicates warning. It's quite possible that issue only affects H-uru repo, and if so I'm not going to worry about it.
Re: RAD Game Tools License Concern - Immediate Action Requir
Github support has been notified. They intend to make all unfiltered repositories private for us and pass along an explanation.
-
- Member
- Posts: 317
- Joined: Sat Dec 13, 2008 10:54 am
Re: RAD Game Tools License Concern - Immediate Action Requir
Trying this too (I hadn’t before – I used the GehnShard fork as a test case, which as you note causes no warnings), I can reproduce some duplicate warnings, and I concur that they are most likely harmless. They all have to do with pull requests in addition, so owners of repos that have no (incoming) pull requests should be fine.branan wrote:I just tried the git-only conversion script on a clone of the H-uru/Plasma repo. I got a message about "possible duplicates", but the HEAD SHA is b3976524ee406256655183fd25a49d984138dfb0, which matches the expected output according to binkbegone.sh. Looking at the logs those 'duplicates' might actually be correct (a closed PR and then a reopened one after a rebase).
In detail:
Code: Select all
commit b687ab3cc01a10c79bf25c661308e46f536ba277
Author: a'moaca' <none@none>
Date: Sun Mar 27 16:22:32 2011 -0700
Import modified jpeg-8c library. The library is modified to provide the
RGBA color space expected by plMipmap.
commit 4b7bb2f344cd06149907b665245d5295f7b81c5e
Author: a'moaca <none@none>
Date: Sun Mar 27 16:22:32 2011 -0700
Import modified jpeg-8c library. The library is modified to provide the
RGBA color space expected by plMipmap.
Code: Select all
commit be165f281b5025a691870440643f71415c7d1bf8
Merge: 86de0d4 5beda0a
Author: GitHub Merge Button <merge-button@github.com>
Date: Thu Apr 5 23:17:04 2012 -0700
Merge efeaaa60e6d9bb974b207273dafd5f29f4f0d6e7 into 4d56e49453ab94d4d4ade799a27b2353f0df0005
commit 49629b25d347a6203519672b652975a16094f299
Merge: 86de0d4 1fa981d
Author: GitHub Merge Button <merge-button@github.com>
Date: Thu Apr 5 23:17:04 2012 -0700
Merge b31f1fa72c4cdcdc9acefe8208e938d9139fd6f1 into 4d56e49453ab94d4d4ade799a27b2353f0df0005
Code: Select all
commit b219c3c3cc7f33cb9c5e33de33469647ad58a1dc
Author: Michael Hansen <zrax0111@gmail.com>
Date: Tue Nov 13 01:02:23 2012 -0800
Alright, this _TEMP_CONVERT_ stuff was a stupid idea
commit 230c43b143fed4f9d473e0fca6098edc24782e32
Author: Michael Hansen <zrax0111@gmail.com>
Date: Tue Nov 13 01:02:23 2012 -0800
Alright, this _TEMP_CONVERT_ stuff was a stupid idea
commit a3ba5c5bbe8c5c114d393be4febe7358ed1cb1bc
Author: Michael Hansen <zrax0111@gmail.com>
Date: Tue Nov 13 01:02:23 2012 -0800
Alright, this _TEMP_CONVERT_ stuff was a stupid idea
branan wrote:I'll ask Hoikas to poke them about how to ensure the old history isn't accessible through closed pulls.
Very good. If I read the network graph correctly, that would be AtlantisShard, TheEggman, NadnerbD, philippelatulippe, RPLawrence.Hoikas wrote:Github support has been notified. They intend to make all unfiltered repositories private for us and pass along an explanation.
I’m going to do some experiments to see if we can achieve the same thing (bring closed pull requests onto the new history) on Bitbucket. May require help from support as well.
Re: RAD Game Tools License Concern - Immediate Action Requir
Houston, we have a problem: https://github.com/Dhelayan/plLayerBink
Notice the addition of this comment:
Notice the addition of this comment:
Code: Select all
//Failure to remove this file could result in prosecution of Cyan Worlds by RAD Game Tools
//for releasing copyrighted code, which would be A Bad Thing(TM).
Lyrositor
Explorer #16601888
To D'ni, or not to D'ni. There is no question.
Explorer #16601888
To D'ni, or not to D'ni. There is no question.
Re: RAD Game Tools License Concern - Immediate Action Requir
Oh Dhelayan. What would we do without him. I think the best thing is just to notify Cyan and/or RAD and have them send a DMCA takedown request to github for that repo. It's just not worth anybody's time to bother talking to him.
Re: RAD Game Tools License Concern - Immediate Action Requir
I am working on the Bitbucket support side of things. Please contact me with any specifics.Christian Walther wrote:I’m going to do some experiments to see if we can achieve the same thing (bring closed pull requests onto the new history) on Bitbucket. May require help from support as well.
Perfect speed is being there.
Re: RAD Game Tools License Concern - Immediate Action Requir
I did send another email to github support about that one. That's all the attention I care to give to this trollface.branan wrote:Oh Dhelayan. What would we do without him. I think the best thing is just to notify Cyan and/or RAD and have them send a DMCA takedown request to github for that repo. It's just not worth anybody's time to bother talking to him.
-
- Member
- Posts: 317
- Joined: Sat Dec 13, 2008 10:54 am
Re: RAD Game Tools License Concern - Immediate Action Requir
OK, I haven’t found a way of doing it from our side so far. Here’s what I have found in my experiments – it’s all a little strange : Updating the destination repo to the new history (i.e. stripping the old and pushing the new), but leaving the source repos on the old history will mark all merged pull requests as open again. (This is halfways expected because the pull request head revisions now in fact are no longer merged into the destination, but is interesting because otherwise there is no way of reopening a pull request.) The pull requests will also become editable again, however the editability will only last as long as the source revision is still available in the source repository – as soon as I strip it from there and push the new history, the edit button disappears again. When I push the new history into the source repository without stripping the old one before, the pull request stays editable, but I still can’t seem to switch it to the new history – the source branch popup only has one entry for the branch (even though it now has two heads in the repository), and it seems to still refer to the old head.JWPlatt wrote:I am working on the Bitbucket support side of things. Please contact me with any specifics.Christian Walther wrote:I’m going to do some experiments to see if we can achieve the same thing (bring closed pull requests onto the new history) on Bitbucket. May require help from support as well.
So, the best course of action is probably to ask Bitbucket support what they suggest. If they can switch the PRs around for us without causing any reopening or other permanent changes, that would be best. I can easily compile a list of PR, old revision, new revision for them if that is desired. We’ll probably need exact instructions about what order to push the new history and strip the old one in the source and destination repos, since things seem to be sensitive to that. Fortunately the only source repos are Boq’s, Skoader’s, and mine, so we should manage to contact the owners.
I imagine that this isn’t the first time such a history rewriting has happened on Bitbucket, but I can’t find anything about it in its docs.