I think it would be easier if "mgarepo ci" checks in the changes for all directories (SPECS + SOURCES). That would make it different from SVN, but I noticed that none of the instructions currently mention that you should do the "svn ci" from the main directory. This resulted in me not committing changes properly. IMO the nicest fix is to make mgarepo ci behave nicely so people not using SVN or often using git do not have to care about the differences and can just rely on mgarepo doing whatever is required.
(In reply to comment #0) > I think it would be easier if "mgarepo ci" checks in the changes for all > directories (SPECS + SOURCES). That would make it different from SVN, but I > noticed that none of the instructions currently mention that you should do the > "svn ci" from the main directory. hum it does work like this here. The only things to handle in fact is the « source/patch updates » via a mgarepo sync -c (to commit immediatly) when we're adding/removing a binary, you can always add/remove a patch (or a text file in SOURCES folder) using svn add/del & after mgarepo ci should show all your changes. There's a bug regarding mgarepo ci when you did play with svn mv before (i did not try recently so i'm not sure it's fixed) )
CC: (none) => balcaen.john
pinging because this bug still has the NEW status and didn't show any activity in almost 4 months @ sysadmin 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.
CC: (none) => marja11
(In reply to comment #0) > > This resulted in me not committing changes properly. IMO the nicest fix is to > make mgarepo ci behave nicely so people not using SVN or often using git do not > have to care about the differences and can just rely on mgarepo doing whatever > is required. This could be confusing for people used to svn and not git, who could unexpectedly commit some changes from an other directory. I think the "mgarepo ci" command is not very useful, it's better to use svn ci directly (or later git if we switch to git).
Status: NEW => ASSIGNEDCC: (none) => boklm
Component: BuildSystem => RPM PackagesVersion: unspecified => CauldronAssignee: sysadmin-bugs => boklmProduct: Infrastructure => Mageia
CC: boklm => (none)
Assignee: boklm => bugsquad
CC: (none) => doktor5000
(In reply to Nicolas Vigier from comment #3) > (In reply to comment #0) > > > > This resulted in me not committing changes properly. IMO the nicest fix is to > > make mgarepo ci behave nicely so people not using SVN or often using git do not > > have to care about the differences and can just rely on mgarepo doing whatever > > is required. > > This could be confusing for people used to svn and not git, who could > unexpectedly commit some changes from an other directory. I think the > "mgarepo ci" command is not very useful, it's better to use svn ci directly > (or later git if we switch to git). Closing as wontfix, then
Status: ASSIGNED => RESOLVEDResolution: (none) => WONTFIX