Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1415486 - Import from SRPM upload fails with "insufficient permission for adding an object to repository database ./objects "
Summary: Import from SRPM upload fails with "insufficient permission for adding an obj...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Copr
Classification: Community
Component: backend
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: clime
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-22 14:15 UTC by Sandro Mani
Modified: 2017-01-23 14:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-23 14:49:51 UTC


Attachments (Terms of Use)
Import log (2.44 KB, text/plain)
2017-01-22 14:15 UTC, Sandro Mani
no flags Details

Description Sandro Mani 2017-01-22 14:15:22 UTC
Created attachment 1243356 [details]
Import log

I've got one particular SRPM [1] which constantly results in an import failure with the attached log. It somehow seems related to the SRPM as all other SRPMS I've uploaded imported fine. The failed build is [2]. I've tried multiple times and always got the same failure.

[1] https://smani.fedorapeople.org/mingw-osgearth-2.7-1.fc26.src.rpm
[2] https://copr.fedorainfracloud.org/coprs/smani/mingw-extras/build/502550/

Comment 1 clime 2017-01-23 12:21:47 UTC
One of the object dirs in the git repo for mingw-osgearth was missing group write permissions. Could you try again, please?

Comment 2 Sandro Mani 2017-01-23 12:41:32 UTC
Yep worked now, thanks for the quick reply! So was something actually wrong with the SRPM or was it an unlucky coincidence?

Comment 3 clime 2017-01-23 14:49:51 UTC
(In reply to Sandro Mani from comment #2)
> Yep worked now, thanks for the quick reply! So was something actually wrong
> with the SRPM or was it an unlucky coincidence?

SRPM is alright probly. Somehow permissions got messed up there but not exactly sure how. We will see if problem reoccurs.

Comment 4 Sandro Mani 2017-01-23 14:50:52 UTC
Okay thanks


Note You need to log in before you can comment on or make changes to this bug.