Opened 10 months ago

Closed 10 months ago

Last modified 10 months ago

#69044 closed defect (duplicate)

pdal: port name wrong and live check fail on ports.macports.org after port name conversion to lowercase

Reported by: nilason (Nicklas Larsson) Owned by: Veence (Vincent)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: nilason (Nicklas Larsson)
Port: pdal

Description

After commit ad254d9 to rename the port PDAL to lowercase pdal, the name displayed on https://ports.macports.org/port/pdal is still PDAL and the live check is apparently not working (port livecheck pdal does work).

Change History (6)

comment:1 Changed 10 months ago by nilason (Nicklas Larsson)

Cc: nilason added

comment:2 Changed 10 months ago by jmroot (Joshua Root)

Owner: set to Veence
Status: newassigned

comment:3 Changed 10 months ago by jmroot (Joshua Root)

Component: websiteports
Resolution: duplicate
Status: assignedclosed

The case thing is https://github.com/macports/macports-webapp/issues/367. I don't see any livecheck failure on the web app currently. It runs periodically, not every time a change is made.

comment:4 in reply to:  3 Changed 10 months ago by nilason (Nicklas Larsson)

Replying to jmroot:

The case thing is https://github.com/macports/macports-webapp/issues/367. I don't see any livecheck failure on the web app currently. It runs periodically, not every time a change is made.

Oh, thanks. The live check doesn't fail per se, but doesn't detect actual updates (I missed an update from November because of this).

comment:5 Changed 10 months ago by jmroot (Joshua Root)

OK. If there's an issue with livecheck separate from the case sensitivity issues, please open another issue over on GitHub, as the web app's maintainers have decided to use GitHub issues instead of Trac for whatever reason.

comment:6 in reply to:  5 Changed 10 months ago by nilason (Nicklas Larsson)

Replying to jmroot:

OK. If there's an issue with livecheck separate from the case sensitivity issues, please open another issue over on GitHub, as the web app's maintainers have decided to use GitHub issues instead of Trac for whatever reason.

I guess the two things are related, added a comment on this there.

Note: See TracTickets for help on using tickets.