We need to extend mgarepo to handle the backports branch as it does with the updates branch. There are at least two things that mgarepo should be able to do: - Checkout a backports branch using a simple syntax, i.e. mgarepo co backports/4/pkgname - If the branch does not exist, create the actual backports branch for the given package, following this scheme: o Branch off the updates/4/pkgname branch to backports/4/pkgname o If pkgname is new, branch off cauldron/pkgname to backports/4/pkgname For the first point, I've done a patch (arguably not the best implementation though) that mimics the behaviour of mgarepo co 4/pkgname and extends it to support backports. I've tested it locally and it works fine. Reproducible: Steps to Reproduce:
Created attachment 5878 [details] Implement support for mgarepo co backports/4/pkgname if branch exists
CC'ing sysadmin team.
CC: (none) => sysadmin-bugs
Keywords: (none) => PATCHSeverity: normal => enhancement
i just added this feature in mgarepo ( http://gitweb.mageia.org/software/build-system/mgarepo/commit/?id=4521eb9e1425919f6e6a87011098c2a3490295c4 ) the switch is -k ( or --backports ) mgarepo co packagename -k 5
Status: NEW => RESOLVEDCC: (none) => mageiaResolution: (none) => FIXED
Summary: Implement backports handling in mgarepo => Implement backports checkout in mgarepo
Assignee: bugsquad => mageia