Description of problem: 'mgarepo changed' gives error: invalid arguments Version-Release number of selected component (if applicable): mgarepo-1.10.2-1.mga2.noarch How reproducible: always Steps to Reproduce: 1. mgarepo changed 2. 3.
Assignee: bugsquad => boklm
Seems that this command requires an argument (presumeably the package name) to work. I figured, similar is true for 'mgarepo rpmlog', and I think it would be nice if it would detect the package name like the other related commands (ci, co, submit) do ...
CC: (none) => herbert
Severity: major => normal
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
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
Status: NEW => ASSIGNED
boklm leave Mageia
Status: ASSIGNED => NEWAssignee: boklm => bugsquad
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D [reply] [-] Comment 4
CC: (none) => r.wobben
@ Herbert Re-reading, I don't think this is a bug. Closing it as old, anyway, because it was filed against mgarepo-1.10.2-1.mga2.src.rpm and we're on mgarepo-1.10.5-3.mga5.src.rpm now in cauldron. If you want to reopen it, then please change it to Severity: "enhancement request" There is no maintainer for mgarepo now, btw.
Keywords: NEEDINFO => (none)Status: NEW => RESOLVEDCC: (none) => marja11Resolution: (none) => OLD