Opened 3 months ago

Closed 3 months ago

Last modified 2 weeks ago

#70517 closed defect (fixed)

MacPorts 2.10.0 release missing package for 10.4 Tiger on GitHub, broken link on MacPorts website

Reported by: aprfx Owned by: jmroot (Joshua Root)
Priority: Normal Milestone:
Component: base Version: 2.10.0
Keywords: tiger Cc: aprfx, jmroot (Joshua Root)
Port:

Description

The latest MacPorts 2.10.0 release on GitHub is missing a package for 10.4 Tiger in Assets.

The link https://github.com/macports/macports-base/releases/download/v2.10.0/MacPorts-2.10.0-10.4-Tiger.dmg on the MacPorts website (www.macports.org/install.php#installing) leads to a 404 error on GitHub.

The previous full release, MacPorts 2.9.3, has a package for Tiger in its GitHub entry. There was no mention of dropping support for 10.4 Tiger in any changelogs, so I am sure it is just an oversight.

Change History (7)

comment:1 Changed 3 months ago by aprfx

Cc: aprfx added

comment:2 Changed 3 months ago by ryandesign (Ryan Carsten Schmidt)

Cc: jmroot added
Component: websitebase
Keywords: missing package installer 10.4 removed
Priority: Not setNormal

Josh didn't produce installers for Mac OS X 10.4 for MacPorts 2.10.0 beta 1, beta 2, rc 1, nor final.

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

As far as I know support for 10.4 has not been dropped; you should still be able to selfupdate to it or build it from source as usual. If that's failing let us know.

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

Owner: set to jmroot
Resolution: fixed
Status: newclosed

In 309921ce960c3b1a5c8c71411fdc94687e10cfb4/macports-www (master):

Remove links to nonexistent Tiger dmg

Closes: #70517

comment:5 Changed 3 months ago by ryandesign (Ryan Carsten Schmidt)

Is there a problem with creating the 10.4 installer dmg?

comment:6 Changed 3 months ago by barracuda156

This should probably be reopened. Deleting a reference does not fix the issue.

comment:7 Changed 2 weeks ago by ryandesign (Ryan Carsten Schmidt)

What Josh seems to be telling us is that he intentionally no longer produces the Tiger installer; reopening the ticket won't necessarily change Josh's intention.

What I'd like to understand is why the Tiger installer is no longer produced. Josh, did your 10.4 VM or machine die and it's too much trouble to fix? Or is there now an error when producing this installer? If so, what's the error? Maybe I can help fix it.

I have Tiger machines I could use but I'm not sure how our release process would change if all of the assets are not being made by one person.

Note: See TracTickets for help on using tickets.