mgarepo wrongly remembers last section When some packages in two sections (eg: core/release & tainted/release), mgarepo will upload by default into tainted/release instead of core/release. Eg: when uploading drakx-installer-images, it uploads it by default into non-free/release instead of core/release.
Source RPM: (none) => mgarepo
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) => TriagedAssignee: bugsquad => boklm
This is not a mgarepo bug, if you don't specify it will be detected by youri-submit on the server
CC: (none) => pterjan
Source RPM: mgarepo => mga-youri-submit
youri-submit wrongly submit the section. Whether last submitted section was core/release or non-free/release, the new submit will go into non-free/release (maybe due to ASCII sorting?)
Probably due to the order of medias in the config files, I'd need to read the code. Anyway the plan was to have it submit to both media but I did not finish coding it.
Trying to ping 41 bug reports in one move, because nothing has happened with them for more than 3 months, they still have the status NEW or REOPENED, there is no "OK" on the Whiteboard and severity and priority are "normal" or higher. Is this one still valid for Mageia 2 rc? If it is and you're the assignee, please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead. If it wasn't assigned correctly, please assign back to Bug Squad and explain.
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 => ASSIGNEDAssignee: boklm => sysadmin-bugs
No comments for ever. Obviously there is no need to keep open. Housekeeping wins.
Status: ASSIGNED => RESOLVEDCC: (none) => nicResolution: (none) => OLD