#5058 Unable to push into memtest86+/master
Closed: Will Not/Can Not fix 6 years ago Opened 8 years ago by jskarvad.

= bug description =
I cannot push into memtest86+/master (and maybe other branches, but I didn't test).

= bug analysis =
$ git clone 'ssh://jskarvad@pkgs.fedoraproject.org/memtest86+'
Cloning into 'memtest86+'...
WARNING: 'memtest86+' is an alias for 'rpms/memtest86+'
remote: Counting objects: 573, done.
remote: Compressing objects: 100% (342/342), done.
remote: Total 573 (delta 275), reused 458 (delta 207)
Receiving objects: 100% (573/573), 241.70 KiB | 0 bytes/s, done.
Resolving deltas: 100% (275/275), done.
Checking connectivity... done.

Then I updated SPEC file and tried to push the changes:

$ git push -v
ushing to ssh://jskarvad@pkgs.fedoraproject.org/memtest86+
WARNING: 'memtest86+' is an alias for 'rpms/memtest86+'
FATAL: W any memtest86+ jskarvad 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.


I tried to push into 'grep/master' and it worked. So It seems that only
the memtest86+ is broken for me. I apparently have the correct ACLs:

https://admin.fedoraproject.org/pkgdb/package/rpms/memtest86+/

It is really weird as I am proven packager so it shouldn't complain about ACLs.

Also the ugly warning:
WARNING: 'memtest86+' is an alias for 'rpms/memtest86+'

started to appear recently, but it seems to be harmless.

= fix recommendation =
None, please fix it :)


Ok so I looked a little into this and I fear the issue is in the alias we set so that memtest86+ points to rpms/memtest86+

One solution for now is to point to rpms/ directly.

So if you clone $ git clone '​ssh://jskarvad@pkgs.fedoraproject.org/rpms/memtest86+' or fedpkg clone rpms/memtest86+ or adjust the remote url of your clone, it should let you through.

I'll try to investigate further and also check if other packages are affected.

Thanks for your report.

Thanks for info, just changing the URL worked for me, I can now push, great.

FTR it seems to impact mysql++ as well (no report, just from my tests), I suspect all the packages with a '+' in their name are impacted

Partially out-of-topic but for further reference: Same for me and package gimp-separate+ .

Workaround in the form of fedpkg clone rpms/gimp-separate+ helped.

I also had this issue. Worked for me with fedpkg co rpms/coin-or-FlopC++

So, fedpkg should do the right thing here... not sure it's worth trying to fix further.

If anyone disagrees, please feel free to reopen or comment.

Thanks.

:heavy_plus_sign:

Metadata Update from @kevin:
- Issue close_status updated to: Will Not/Can Not fix
- Issue status updated to: Closed (was: Open)

6 years ago

Login to comment on this ticket.

Metadata