Red Hat Bugzilla – Bug 1260986
dnf reposync lists repo as wrong argument
Last modified: 2016-07-21 10:37:02 EDT
Description of problem:
reposync help lists --repo as argument for the repository id, but this generates an error "Befehlszeilenfehler: argument --repofrompath: bad format: f22-updates"
If --repoid is used as argument the reposync works. So I guess it's an error in the reposync help output.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. dnf reposync -p fedora --repo /mnt/somewhere
error about bad format of argument
download of repo to /mnt/somewhere
This is a know issue, unfortunately. Actually, the cause is the introduction of the --repofrompath option and the problematic design of our argument parser. We are currently working on improving the argument parsing part.
FTR, the issue was first reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1193851#c7 I don't know how to handle this situation. I mean whether to close this as a duplicate or track the issue here.
*** Bug 1265025 has been marked as a duplicate of this bug. ***
Ping ... what is the --repoid status please?
yeah, we should finish it but there were issue with Python3.
*** Bug 1299261 has been marked as a duplicate of this bug. ***
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see email@example.com with any questions
*** Bug 1328050 has been marked as a duplicate of this bug. ***
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.
--repo parameter still does not work :/
It likely won't until DNF2 arrives - just anecdotally it seems like that's the direction the project went as I observed most bugs in Github had a similar reply from the authors. So I think they're not bothering to fix menial bugs like this in favor of the complete DNF2 rewrite.
Granted, I agree with keeping actual bugs open, since it's still broken.
Fixed as part of DNF 2.0 which will be available at some point soon.