I am trying to submit a new build for the 'wicd' component, which I own, but CVS is telling me I don't have write permissions. I tried to clone the wicd component with fedpkg, but that even said I don't have read access.
All of the other components I own are working fine, so I don't know what's up with this one.
CVS is read only now. ;)
what does 'rpm -q fedora-packager' say? Make sure you have 0.5.0 or higher. If you cloned with an older one, update and clone again.
Paste the output/error here if you are still seeing one.
dcantrel@mitre ~$ rpm -q fedora-packager fedora-packager-0.4.2.3-1.fc13.noarch
Here's what happens when I try to clone wicd:
dcantrel@mitre ~$ fedpkg clone wicd Cloning into wicd... Use of uninitialized value in string eq at /usr/local/bin/gl-auth-command line 65. R access for wicd DENIED to dcantrel fatal: The remote end hung up unexpectedly Traceback (most recent call last): File "/usr/bin/fedpkg", line 903, in <module> args.command(args) File "/usr/bin/fedpkg", line 408, in clone pyfedpkg.clone(args.module[0], args.user, args.path, args.branch) File "/usr/lib/python2.6/site-packages/pyfedpkg/init.py", line 287, in clone _run_command(cmd) File "/usr/lib/python2.6/site-packages/pyfedpkg/init.py", line 112, in _run_command raise FedpkgError(e) pyfedpkg.FedpkgError: Command '['git', 'clone', 'ssh://dcantrel@pkgs.stg.fedoraproject.org/wicd']' returned non-zero exit status 128
But here's a package I own that works just fine:
dcantrel@mitre ~$ fedpkg clone clpbar Cloning into clpbar... Use of uninitialized value in string eq at /usr/local/bin/gl-auth-command line 65. remote: Counting objects: 29, done. remote: Compressing objects: 100% (17/17), done. remote: Total 29 (delta 8), reused 29 (delta 8) Receiving objects: 100% (29/29), 12.21 KiB, done. Resolving deltas: 100% (8/8), done.
Before we cut over to git, I was getting some acl issues with wicd under cvs. I could check things out, but could not commit anything. That was several weeks ago.
You have the old fedora-packager thats building against staging (see the 'stg' in there)?
So, all your older packages were over in the staging test instance and work. The new packages were added after the sync over to staging, so don't.
Update to the new fedora-packager so you are operating against the live production git repo.
Can the fedora-packager package in F-13 be updated to the latest version? I just installed mine via yum.
It's in updates-testing. It should go to stable on the next push:
https://admin.fedoraproject.org/updates/fedora-packager-0.5.1.0-1.fc13
Closing, I think this doesn't need to be tracked here. Please reopen if the new fedora-packager does not work for you.
Login to comment on this ticket.