Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 533810 - Access denied to proj/qt after gitolite upgrade
Summary: Access denied to proj/qt after gitolite upgrade
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Infrastructure
Classification: Unclassified
Component: Gentoo Overlays (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Overlays Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-28 14:31 UTC by Davide Pesavento
Modified: 2014-12-31 01:26 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Davide Pesavento (RETIRED) gentoo-dev 2014-12-28 14:31:22 UTC 
$ git push

FATAL -- ACCESS DENIED
Repo            proj/qt
User            pesa@gentoo.org
Stage           Before git was called
Operation       Repo write

FATAL: W any proj/qt pesa@gentoo.org DENIED by fallthru
(or you mis-spelled the reponame)
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

===

This started to happen last night after the gitolite upgrade was completed. Not sure if other qt team members are affected.
Comment 1 Michael Palimaka (kensington) gentoo-dev 2014-12-30 16:44:26 UTC 
I was able to push successfully, but my remote is proj/qt.git instead of proj/qt in case that makes any difference for some reason.
Comment 2 Davide Pesavento (RETIRED) gentoo-dev 2014-12-31 01:24:59 UTC 
(In reply to Michael Palimaka (kensington) from comment #1)
> I was able to push successfully, but my remote is proj/qt.git instead of
> proj/qt in case that makes any difference for some reason.

It's qt.git here too, according to git remote

  Push  URL: git+ssh://git@git.overlays.gentoo.org/proj/qt.git
Comment 3 Davide Pesavento (RETIRED) gentoo-dev 2014-12-31 01:26:37 UTC 
Well I don't know why but it works now, I didn't touch anything...