Bug 1007157 - Allow bodhi command line options for fedpkg update
Allow bodhi command line options for fedpkg update
Status: CLOSED EOL
Product: Fedora
Classification: Fedora
Component: fedpkg (Show other bugs)
25
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: cqi
Fedora Extras Quality Assurance
: Reopened
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-11 23:14 EDT by Miro Hrončok
Modified: 2017-12-12 05:24 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-12-12 05:24:39 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Miro Hrončok 2013-09-11 23:14:36 EDT
tl;dr: When running fedpkg update, a template is always shown, that makes it hard when doing update for multiple releases at once. Bodhi offers several command line options that can be used to simplify the task. Allow that options to be used with fedpkg update. I can send patches.



I often do it with this (or similar) command:

$ for F in f20 f19 f18; do fedpkg switch-branch $F && fedpkg update; done

In that particular case I have to fill in the template three times and that's a pain. I have to copy and paste multiple values and basically I fill the form three times using the very same values. Deleting the line "Here is where you give an explanation of your update." three times also (BTW that line should not be there anyway, it should be in the comment ABOVE the notes= line).

Bodhi comes with lot of useful command line options [0], that would make this easier for me (and also others).

Look at this for example:

$ for F in f20 f19 f18; do fedpkg switch-branch $F && fedpkg update -t bugfix -N "Blah blah" -S 2 -U -2 -b 12345; done

When defining type and notes, everything else should be filled automatically without prompt (by prompt I mean showing the template in EDITOR). Bug number from changelog/git should be used when -b or --bugs is not used (the same way as it is pre-filled in the template). When type and/or notes are not defined, the template is shown as in present, with possible information from other switches present in the form.

$ fedpkg update -N "Blah blah" -S 2 -U -2 -b 12345

would prompt this:

=====

# bugfix, security, enhancement, newpackage (required)
type=

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=12345

# Description of your update
notes=Blah blah

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=2
unstable_karma=-2

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

======

But:

$ fedpkg update -t bugfix -N "Blah blah"

would simply use default values (as they are in the template now) and the only prompt necessary would be the password.

If you accept this behavior but don't want to code it, I'm free to take it, it seems like a relatively easy task. Just give me a blessing or comments.

[0] https://fedorahosted.org/bodhi/wiki/CLI
Comment 1 Miro Hrončok 2013-10-22 05:25:15 EDT
Please just let me know if I can patch it, so it works this way.
Comment 2 John Heidemann 2015-01-06 02:56:36 EST
Do you want to attach the patch?  This change would be a BIG help for exactly the reasons given in the bug report.
Comment 3 Miro Hrončok 2015-01-06 03:02:50 EST
I didn't write the patch. I was waiting for a reply first not to spend my time on something that would never be accepted. Still am.
Comment 4 Dennis Gilmore 2015-01-10 13:54:25 EST
Patches are always welcome. I am not sure why you are asking for permission or exactly what the options you are talking about are.  I personally change the disttag in the nvr at the top of the template and copy and paste the content when updating for multiple releases. having a easy way to specify multiple builds would be a welcome addition.
Comment 5 Jaroslav Reznik 2015-03-03 10:03:19 EST
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 6 Fedora End Of Life 2016-07-19 06:22:05 EDT
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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 7 Jan Kurik 2016-07-26 00:12:21 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.
Comment 8 Fedora Admin XMLRPC Client 2017-02-21 11:42:07 EST
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 9 cqi 2017-03-01 21:17:51 EST
Belongs to milestone 1.30[1]

[1] https://pagure.io/fedpkg/roadmap?status=Open&no_stones=&milestone=1.30
Comment 10 Fedora End Of Life 2017-12-12 05:24:39 EST
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.