[MacPorts] #19935: incorrect locking policy with deactivate
#19935: incorrect locking policy with deactivate ---------------------------------+------------------------------------------ Reporter: vinc17@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 1.7.1 Keywords: | Port: ---------------------------------+------------------------------------------ I've tried to upgrade two ports A and B at the same time with: {{{ $ sudo port -v upgrade A $ sudo port -v upgrade B }}} in two different shell sessions. Port B depends on A. As expected, the upgrade of port B waited for a lock while the new version of port A was being built. But the following problem occurred: both occurrences of the port command tried to deactivate port A at the same time, so that one of the deactivate operations failed. -- Ticket URL: <http://trac.macports.org/ticket/19935> MacPorts <http://www.macports.org/> Ports system for Mac OS
#19935: incorrect locking policy with deactivate ---------------------------------+------------------------------------------ Reporter: vinc17@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts Future Component: base | Version: 1.7.1 Keywords: lock | Port: ---------------------------------+------------------------------------------ Changes (by blb@…): * keywords: => lock * milestone: => MacPorts Future -- Ticket URL: <http://trac.macports.org/ticket/19935#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#19935: need per-port locking, not just per-target ---------------------------------+------------------------------------------ Reporter: vinc17@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts Future Component: base | Version: 1.7.1 Keywords: lock | Port: ---------------------------------+------------------------------------------ -- Ticket URL: <http://trac.macports.org/ticket/19935#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#19935: need per-port locking, not just per-target ---------------------------------+------------------------------------------ Reporter: vinc17@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts Future Component: base | Version: 1.7.1 Keywords: lock | Port: ---------------------------------+------------------------------------------ Changes (by ryandesign@…): * cc: ryandesign@… (added) Comment: Has duplicate #24858. -- Ticket URL: <http://trac.macports.org/ticket/19935#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#19935: need per-port locking, not just per-target ----------------------------------+----------------------------------------- Reporter: vinc17@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: MacPorts 1.9.2 Component: base | Version: 1.7.1 Resolution: fixed | Keywords: lock Port: | ----------------------------------+----------------------------------------- Changes (by jmr@…): * status: new => closed * resolution: => fixed * milestone: MacPorts Future => MacPorts 1.9.2 Comment: Should be OK as of r70174/r70175. I went for the simpler approach of having one exclusive lock for all actions that modify the registry. -- Ticket URL: <http://trac.macports.org/ticket/19935#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts