Opened 6 years ago

Closed 6 years ago

#56858 closed defect (fixed)

p5-graveyard, py-graveyard don't accommodate epoch

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: larryv (Lawrence Velázquez)
Port: p5-graveyard, py-graveyard

Description

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 py26-webhelpers was made obsolete.

Change History (3)

comment:1 Changed 6 years ago by reneeotten (Renee Otten)

see ​this PR

comment:2 Changed 6 years ago by reneeotten <reneeotten@…>

In 47b16adaff6d20d1e6cdc1bd43e498d25161841b/macports-ports (master):

py-graveyard: add support for epoch

  • epoch values added by @ryandesign

See: #56858

comment:3 Changed 6 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: set to ryandesign
Resolution: → fixed
Status: new → closed

In 82629a84ae90e4da7d953695f7ac16c57de7bb28/macports-ports (master):

p5-graveyard: add support for epoch

  • add epoch values
  • update script to generate the list

Closes: #56858

Note: See TracTickets for help on using tickets.