See the meta issue for background: #1076616: Projects should have "master" renamed to appropriate branch

In order for testbot to work, the dev release, 5.x-1.x-dev http://drupal.org/node/243803, needs to be based on a properly named development branch. The process to do that is documented at http://drupal.org/node/1127732

Comments

hass’s picture

Project: Link checker » The Great Git Migration
Version: 5.x-1.x-dev »
Component: Miscellaneous » Migration scripts

Are you trying to tell me that the suxxx git migration process failed again? Feel free to tell the git migration team to fix their outstanding migration bugs.

Josh The Geek’s picture

I'm not sure this should be leftovers, but at least part of the reason this didn't happen is the fact it was lost w/out any tags.

rfay’s picture

Project: The Great Git Migration » Link checker
Version: » 5.x-1.x-dev
Component: Migration scripts » Code
Status: Active » Fixed

Due to the hostile response, I've turned off automated testing on Link Checker. That resolves this issue.

All we were asking was for you to cut a reasonable branch. Geez.

hass’s picture

Project: Link checker » The Great Git Migration
Version: 5.x-1.x-dev »
Component: Code » Migration scripts
Category: task » bug
Status: Fixed » Active

It's not my job to fix the git migration team bugs. I have never maintained 5.x-1.x and i do not care about this branch. It could also get deleted at all.

Josh The Geek’s picture

Project: Git on Drupal.org » Link checker
Version: » 5.x-1.x-dev
Component: Tests » Code
Status: Needs work » Fixed

hass: This is not a bug. Testable projects now need to have a properly named branch instead of master. You can ignore now because rfay turned off testing. So, fixed.

hass’s picture

Status: Active » Needs work

The reason is - that git migration is buggy. This should have heen fixed with the migration if required. Enable testing in linkchecker! Nobody pleased you to disable it. Git migration team had all permissions. Otherwise they wouldn't have been able to remove files from my projects or alter all files to remove cvs tags as example. In this phase this should have been done, too.

Josh The Geek’s picture

Project: The Great Git Migration » Git on Drupal.org
Component: Migration scripts » Tests

I can't turn testing back on, but all you need to do is

git checkout master
git branch 5.x-1.x
git checkout 5.x-1.x
git push origin master

Correct me if I'm wrong, but then you can edit your release to point it at the 5.x-1.x branch. Testing should then work fine.

rfay’s picture

Project: Link checker » Git on Drupal.org
Version: 5.x-1.x-dev »
Component: Code » Tests
Status: Fixed » Needs work

Just so you know, if anything this is a bug in the PIFR testbot system.

The initial post explained exactly what to do. The instructions in #7 aren't quite right, but the original post gave the full info.

hass’s picture

I do not have git command line. Git migration team should have done this task for all maintainers. It's a migration bug. This was not required in past and this is why it need to be solved globally. There are no EGit docs available.

Otherwise... Delete the 1.x branch and releases for me. They are not maintained and i see no reason why i should do anything with it including tagging.

hass’s picture

Guys, I cannot use master as origin of 5.x-1.x. I have no clue who have destroyed this, but as said - I have NO git command on my windows box and additional to this - where the heck is the code gone that have been in 5.x-1.x-dev? If I would push master into 5.x-1.x branch I have D7 code in a D5 branch and all 5.x code is lost. Where is the 5.x-1.x-dev branch code gone? It was in CVS...

Where is a backup of these data?

hass’s picture

Shit on the lost data.

Re-enable patch testing for linkchecker module, please. The dead branch has been added and assigned.

rfay’s picture

@hass everybody can now turn on patch testing for their own projects (6.x+)

I don't really understand what you're after in #10 but you can turn on your own patch testing. Edit->Issues->Enable Automated testing.

hass’s picture

Category: bug » task
Status: Needs work » Fixed

Thx... This is what i searched for under automates testing... Usability issue.

Automatically closed -- issue fixed for 2 weeks with no activity.