Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#4 closed defect (fixed)

cgit not showing non-master branches.

Reported by: mbooth Owned by: mbooth
Priority: major Milestone: Ansible Migration Leftovers
Component: service: git Keywords:

Description (last modified by mbooth)

If you look at the darkpeak services repo [1] you can see that only the master branch is shown.

But there is definitely another branch called "ansible" that is not showing up in the cgit repo browser.

Need to figure out why this is.


Change History (6)

comment:1 Changed 2 years ago by mbooth

Milestone: Ansible Migration Leftovers

comment:2 Changed 2 years ago by mbooth

Owner: changed from somebody to mbooth
Status: newassigned

I took a quick a look at this, and there is something wierd going on.

Here is my testing repo that was migrated from the old setup:

I made two commits to two branches, but you can plainly see that cgit still shows "the repo seems to be empty."

So, I created a new user so that I can try new repositories created from scratch. I checked out the testing repo for the new user and then I merged in all the commits from my old testing repo -- the two repos now have identical histories:

Wait a minute, why the hell does that work?

comment:3 Changed 2 years ago by mbooth

Okay, I think it's because there is a different UMASK in the new setup. Let me try fixing it.

comment:4 Changed 2 years ago by mbooth

Resolution: fixed
Status: assignedclosed

Looks fixed now:

I ran a one-time script to fix an incorrect .gitolite.rc symlink in everyone's migrated home dirs and fix the permissions of new commits that got written to disk with the incorrect umask.

All migrated repos should work fine now and gitolite will do The Right Thing™ going forward for new repos.

Last edited 2 years ago by mbooth (previous) (diff)

comment:5 Changed 2 years ago by mbooth

Component: miscgit

comment:6 Changed 2 years ago by mbooth

Description: modified (diff)
Note: See TracTickets for help on using tickets.