#7123 Please repair my package ownership permissions on lockdev package
Closed: Fixed 5 years ago Opened 5 years ago by skisela.

  • Describe what you need us to do:
    Fix package permissions(push permission) on lockdev package.

This has already happened with the following:
https://pagure.io/fedora-infrastructure/issue/6857

I guess the permissions are broken the same way as they were at the previous issue.

Please review also the following, which changed ownership from jpopelka to me:
arptables_jf
psutils
python-feedparser
python-lxml
recode

  • When do you need this? (YYYY/MM/DD)
    ASAP, but no hurry.
  • When is this no longer needed or useful? (YYYY/MM/DD)
    It always will.
  • If we cannot complete your request, what is the impact?
    You will be able to fix it. I trust you :)

Error message after push:

~/fedora/lockdev (master) $ fedpkg push
FATAL: W any rpms/lockdev skisela 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.
Could not execute push: Command '['git', 'push']' returned non-zero exit status 128

arptables_jf

There is no such package in Fedora

psutils

Fixed

python-feedparser

Refreshed but I'm not seeing you there

python-lxml

Refreshed but I'm not seeing you there

recode

Refreshed but I'm not seeing you there

Are you sure these errors are for Fedora's dist-git?

arptables_jf

There is no such package in Fedora

Actually there is, or rather there was: https://src.fedoraproject.org/rpms/arptables_jf it's been orphaned and retired (apparently for a while now)

I see you mention also 'lockdev' in your example... I fixed that one.

If you want to unretire arptables_jf, it will need a re-review then a releng ticket to unblock it and bring it back.

For the other packages, please contact the point of contact/admins and ask to have them add you.

Let us know if you need anything further.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata