Bug 4053 - in --help message, mgarepo putsrpm -m LOG is wrong, the correct is mgarepo putsrpm -l LOG
Summary: in --help message, mgarepo putsrpm -m LOG is wrong, the correct is mgarepo pu...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Dan Fandrich
QA Contact:
URL:
Whiteboard:
Keywords: PATCH, Triaged
Depends on:
Blocks:
 
Reported: 2012-01-07 14:51 CET by Florent Monnier
Modified: 2013-07-09 23:06 CEST (History)
3 users (show)

See Also:
Source RPM: mgarepo
CVE:
Status comment:

Attachments
patch to fix (498 bytes, patch)
2012-07-03 14:04 CEST, Barry Jackson 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Description Florent Monnier 2012-01-07 14:51:47 CET 
Description of problem:

$ mgarepo putsrpm --help | grep -- -m
    -m LOG  Log message used when commiting changes

$ mgarepo putsrpm -m "message" package.src.rpm
error: no such option: -m

The correct parameter is -l


Version-Release:
mgarepo version: 1.10.2
Comment 1 Manuel Hiebel 2012-01-07 17:21:00 CET 
Hi, thanks for reporting this bug.
Assigned to the package maintainer.

(Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged
Component: Others => RPM Packages
Version: unspecified => Cauldron
Assignee: sysadmin-bugs => bugsquad
Product: Infrastructure => Mageia
Source RPM: (none) => mgarepo

Manuel Hiebel 2012-01-07 17:21:29 CET

Assignee: bugsquad => boklm

Comment 2 Florent Monnier 2012-01-07 18:47:17 CET 
Maybe revision 2610 will solve this bug
Comment 3 Marja Van Waes 2012-05-26 13:02:58 CEST 
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 4 Barry Jackson 2012-07-03 14:04:38 CEST 
Created attachment 2520 [details]
patch to fix

Attached patch for this.
Barry Jackson 2012-07-03 14:06:12 CEST

CC: (none) => zen25000
Whiteboard: (none) => MGA2TOO

Manuel Hiebel 2012-07-03 22:22:04 CEST

Keywords: NEEDINFO => PATCH

Comment 5 Nicolas Vigier 2012-07-16 14:45:17 CEST 
It's fixed in cauldron (thanks to commit from blue_prawn).

Status: NEW => ASSIGNED
Version: Cauldron => 2
Whiteboard: MGA2TOO => (none)

Comment 6 Manuel Hiebel 2012-10-20 22:04:04 CEST 
boklm leave Mageia

Status: ASSIGNED => NEW
Assignee: boklm => bugsquad

Comment 7 Dan Fandrich 2013-07-06 00:23:28 CEST 
I have uploaded an updated package for Mageia 2. See bug #952 for details.

CC: (none) => dan
Assignee: bugsquad => qa-bugs

Comment 8 claire robinson 2013-07-06 09:53:48 CEST 
Please just assign one bug per update to QA Dan.

If the fix for this included it should be included in the advisory, which I see you did do. The reason for this is that when the update candidate is pushed as an update the bug assigned to us is closed, also as we complete testing we use the bug report to keep track of progress.

The exception to the rule would be if there were separate updates for mga2 and mga3 for different reasons. Then each should have it's own advisory etc and would be treated completely separately by QA.

Thanks

Assignee: qa-bugs => dan

Comment 9 Dan Fandrich 2013-07-06 12:06:09 CEST 
Thanks for the info. I've updated the wiki with the one-bug-to-qa rule.
Comment 10 Dan Fandrich 2013-07-09 23:06:38 CEST 
mga2 update pushed:
http://advisories.mageia.org/MGAA-2013-0052.html

See bug #952 for details.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.