pkgdb2

Clone
Source Code
GIT

#47 issue when taken a package
Closed: Fixed None Opened 8 years ago by sergiomb.

Closed: Fixed
Reopen Issue

I was waiting for approve to be Package Administrator, later when I taken the package , my status still "waiting for approve to be Package Administrator".

To fix it on po4a package I give up of Package Administrator , I orphan the package and take it again , now I'm Package Administrator ...

But though that I should report since looks like a bug.

Thanks.

I don't understand what happened there.

When looking at the timeline for this package: https://admin.fedoraproject.org/pkgdb/package/po4a/timeline

  • you requested ACLs on a package that wasn't your and you were Awaiting Review for these
  • then you obsoleted all your requests
  • you orphaned the package (Note: there is no traces of you becoming PoC for the package, nor of this package being orphaned before)
  • you took the package that was orphaned and got all the ACLs granted as expected

So the question becomes: was the package orphaned? And if it was, how was it orphaned?

Chronological order

  • athimm was the POC
  • sharkcz request epel7 branch and approve me to el6 and epel7 (in timeline I had approveacls for epel7)
  • I request commit access and Package Administrator for fedora (which changed to Awaiting Review)
  • kevin orphan the package (user: kevin changed point of contact of package: po4a from: athimm to: orphan on branch: f21 )
  • I took the package, (user: sergiomb changed point of contact of package: po4a from: orphan to: sergiomb on branch: master ) but IIRC I haven't commit access .
    ah and this lines : user: sergiomb set for sergiomb acl: approveacls of package: po4a from: Awaiting Review to: Approved on branch: f22 , failed with: "you can't approve yourself" .
  • So after much struggle, I found the solution. I reset approveacls to obsolete and obsolete and took the package again. IIRC first I had done the same just for commit access around 2015-02-25 ...

Did you take the package using the web UI or pkgdb-cli? If the later, which command did you use?

only web UI

Hm, I have found a possible bug in the API endpoin that's used by pkgdb-cli but in the web UI, I can't reproduce it :/

Hello,

To be more precise, I may have tried to use the pkgdb-cli but only one or two times, I don't remember, by default I always used web UI .

Thanks for the reply.

I'm going to assume pkgdb-cli is the culprit here, otherwise I really don't see what could have happened :-/

PR merged

Login to comment on this ticket.

Metadata
None
None
None
None
Powered by Pagure 5.13.3
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.