[MacPorts] #56858: p5-graveyard, py-graveyard don't accommodate epoch
MacPorts
noreply at macports.org
Tue Jul 24 17:57:04 UTC 2018
#56858: p5-graveyard, py-graveyard don't accommodate epoch
------------------------+----------------------------------------
Reporter: ryandesign | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Keywords: | Port: p5-graveyard, py-graveyard
------------------------+----------------------------------------
The p5-graveyard and py-graveyard ports accommodate each obsolete subport
specifying a `version` and `revision` but not an `epoch`. The consequence
of this is that if a port that had previously specified an `epoch` greater
than `0` is added to the graveyard, the replacement does not actually
work, because as far as MacPorts can see, the port's `epoch` has
decreased. This happened for example when
[changeset:aa1d608282a2a58b3b9d3c4396a361832879448d/macports-ports
py26-webhelpers was made obsolete].
--
Ticket URL: <https://trac.macports.org/ticket/56858>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list