Feature changed by: Rémy Marquis (Spyhawk) Feature #305899, revision 3 - Title: Package Locking + Title: Build Service Package Locking Buildservice: Unconfirmed Priority Requester: Important Requested by: Will Stephenson (wstephenson) Description: * Lock a package * osc co -l checks out and locks * Anyone can unlock a package (to prevent deadlock) but it has to be explicit * https://build.opensuse.org/project/monitor to show locks and lock owners -- openSUSE Feature: https://features.opensuse.org/305899

Feature changed by: Pavol Rusnak (prusnak) Feature #305899, revision 5 Title: Build Service Package Locking Buildservice: Evaluation Priority Requester: Important Requested by: Will Stephenson (wstephenson) Description: * Lock a package * osc co -l checks out and locks * Anyone can unlock a package (to prevent deadlock) but it has to be explicit * https://build.opensuse.org/project/monitor to show locks and lock owners + Discussion: + #1: Pavol Rusnak (prusnak) (2009-07-10 14:13:48) + What exactly should lock do? Prevent someone else from checkout ? I + think we need better merging mechanism (e.g. replace source backend + with git), not locking. -- openSUSE Feature: https://features.opensuse.org/305899

Feature changed by: Pavol Rusnak (prusnak) Feature #305899, revision 7 Title: Build Service Package Locking Buildservice: Rejected by Adrian Schröter (adriansuse) reject date: 2009-07-10 15:04:40 reject reason: it blocks development for unknown timeframe, not wanted. Priority Requester: Important Requested by: Will Stephenson (wstephenson) Description: * Lock a package * osc co -l checks out and locks * Anyone can unlock a package (to prevent deadlock) but it has to be explicit * https://build.opensuse.org/project/monitor to show locks and lock owners Discussion: #1: Pavol Rusnak (prusnak) (2009-07-10 14:13:48) What exactly should lock do? Prevent someone else from checkout ? I think we need better merging mechanism (e.g. replace source backend with git), not locking. #2: Adrian Schröter (adriansuse) (2009-07-10 15:01:37) (reply to #1) How would git help here ? #3: Adrian Schröter (adriansuse) (2009-07-10 15:04:03) lock is IMHO the wrong approach. People should submit often, so that other people can follow and can build on top of their changes. No SCM supports locking afaik for good reasons, the first (accepted) submitter wins and others have to adapt. So from my point of view, I do not want this feature at all, it hinders more than it helps. + #4: Pavol Rusnak (prusnak) (2009-07-10 15:14:46) (reply to #3) + The problem is with "adapting" you mentioned. Current SCM in + buildservice has no merge support, one has to rebase the patches + manually, which is PITA. -- openSUSE Feature: https://features.opensuse.org/305899

Feature changed by: Will Stephenson (wstephenson) Feature #305899, revision 9 Title: Build Service Package Locking Buildservice: Rejected by Adrian Schröter (adriansuse) reject date: 2009-07-10 15:04:40 reject reason: it blocks development for unknown timeframe, not wanted. Priority Requester: Important Requested by: Will Stephenson (wstephenson) Description: * Lock a package * osc co -l checks out and locks * Anyone can unlock a package (to prevent deadlock) but it has to be explicit * https://build.opensuse.org/project/monitor to show locks and lock owners Discussion: #1: Pavol Rusnak (prusnak) (2009-07-10 14:13:48) What exactly should lock do? Prevent someone else from checkout ? I think we need better merging mechanism (e.g. replace source backend with git), not locking. #2: Adrian Schröter (adriansuse) (2009-07-10 15:01:37) (reply to #1) How would git help here ? #3: Adrian Schröter (adriansuse) (2009-07-10 15:04:03) lock is IMHO the wrong approach. People should submit often, so that other people can follow and can build on top of their changes. No SCM supports locking afaik for good reasons, the first (accepted) submitter wins and others have to adapt. So from my point of view, I do not want this feature at all, it hinders more than it helps. #4: Pavol Rusnak (prusnak) (2009-07-10 15:14:46) (reply to #3) The problem is with "adapting" you mentioned. Current SCM in buildservice has no merge support, one has to rebase the patches manually, which is PITA. #5: Adrian Schröter (adriansuse) (2009-07-10 16:31:16) (reply to #4) osc repairlink is doing a source merge for conflicting changes. You don't even have to do anything for non conflicting changes, if you use a source link. + #6: Will Stephenson (wstephenson) (2009-07-29 20:26:42) (reply to #3) + Ok consider this withdrawn and look at 305905 insetad.  that way I can + add an advisory note to a package before I fix a build failure so other + team members won't do the same work in parallel to me. -- openSUSE Feature: https://features.opensuse.org/305899