gogs: 500 on creating repository for Organisation

The same issue for me.

• Gogs version (or commit ref): 0.9.100.1119
• Git version: 2.1.4
• Operating system: Debian Jessie (armhf): kernel 4.4.26
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • SQLite
• Can you reproduce the bug at https://try.gogs.io:
  • Yes (provide example URL)
  • No
  • Not relevant
• Log gist: 2016/11/24 20:32:23 [...routers/repo/repo.go:101 handleCreateError()] [E] MigratePost: addRepository: getMembers: get team-users: no such column: team_id

Description

Steps to reproduce this issue:

1. Create new organisation
2. Try to create new repository within this organisation
3. Get 500 Internal Server Error

BR, Piotr

Please don’t start a discussion about another tool, this thread is already flooded with irrelevant comments enough.

Isnt this considered a serious issue? no work around and unable to create a repo in a organization? why taking so long to fix?

If someone has already reported the issue with the same configuration you’re running, there’s no point littering the thread with redundant answers.

same here, It makes no difference if I create the repository for the Organization or transfer ownership.

creating repositories for my user however works fine.

Pushed another patch try to fix this problem, Docker image should be ready in few minutes.

Gitea fixed this issue!

@Unknwon Are you aware that this is a serious issue for mostly everyone right now? Some acknowledgement at least would be great 👍

This works for me.

Let me know if you need me to test other stuff to get rid of the dirty hack 😉

same here, 0.9.100.1119 with postgres

I am seeing the same issue on trying to create a repository under an Organization:

2016/11/25 04:08:04 [...routers/repo/repo.go:101 handleCreateError()] [E] CreatePost: addRepository: getMembers: get team-users: pq: column "team_id" does not exist

P.S. This was a fresh install that I just made today, first action taken.

Gogs version (or commit ref): 0.9.100.1119

Using Docker and SQLite, just pull the latest tag and recreate your containers, it does solve the problem. Thanks @Unknwon.

It worked!

Now I can create repos in our company group.

Thank you!

@lunny i’ll try it, this is sad

master branch isnt the release version? what’s the point of develop branch 😐 All the guides for linux suggest installing from github master src