Description of problem: Currently shortrpm does not accept "--clean" only option. ---------------------------------------------- [tasaka1@localhost SPECS]$ env LANG=C shortrpm --clean jd.spec RPM version 4.7.1 Copyright (C) 1998-2002 - Red Hat, Inc. This program may be freely redistributed under the terms of the GNU GPL Usage: shortrpm [-v?] [-bp] [-bc] [-bi] [-bl] [-ba] [-bb] [-bs] [-tp] [-tc] ... ... ---------------------------------------------- However rpmbuild accepts this: ---------------------------------------------- [tasaka1@localhost SPECS]$ env LANG=C /usr/bin/rpmbuild --clean jd.spec Executing(--clean): /bin/sh -e /home/tasaka1/rpmbuild/INSTROOT/rpm-tmp.7uMZZ5 + umask 022 + cd /home/tasaka1/rpmbuild/BUILD + rm -rf jd-2.5.0-beta091103 + exit 0 ---------------------------------------------- It is preferable that shortrpm accepts "--clean" only option. Version-Release number of selected component (if applicable): shortrpm-1.2-1.fc12.i686 How reproducible: 100% Steps to Reproduce: 1. See above 2. 3. Additional info: shortrpm accepts "--clean --rmsource --rmspec", for example, however does not accept "--clean" (only).
This is not exactly a RFE, rather a regular bug. I attempted to fix it in shortrpm-1.2-2 package, could you please try it? http://koji.fedoraproject.org/koji/taskinfo?taskID=1785384 If it works, I'll submit an update for F-12.
(In reply to comment #1) > http://koji.fedoraproject.org/koji/taskinfo?taskID=1785384 This works, thank you!
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
By the way are there any plans that the fixed shortpm will be pushed into F-11/12 stable repositories?
shortrpm-1.2-2.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/shortrpm-1.2-2.fc12
shortrpm-1.2-2.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.