Opened 10 months ago

Closed 10 months ago

Last modified 10 months ago

#68740 closed defect (fixed)

Update from luajit 2.1.1699520727_0 to 2.1.1699524327_0 doesn't seem to do anything

Reported by: breun (Nils Breunese) Owned by: l2dy (Zero King)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: casr (Chris Rawnsley), l2dy (Zero King)
Port: luajit

Description

I have luajit 2.1.1699520727_0 installed and MacPorts tells me that an update to 2.1.1699524327_0 is available:

~ ❯ port outdated
The following installed ports are outdated:
luajit                         2.1.1699520727_0 < 2.1.1699524327_0

I try upgrading:

~ ❯ sudo port upgrade luajit
--->  Scanning binaries for linking errors
--->  No broken files found.
--->  No broken ports found.

Hm, was the upgrade actually performed? Let's see:

~ ❯ port outdated              
The following installed ports are outdated:
luajit                         2.1.1699520727_0 < 2.1.1699524327_0

I don't get an error message, but it seems the upgrade doesn't do anything.

Change History (4)

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

The way the version is set in this port is far too clever for its own good. I assume the date is being parsed according to the local timezone, so the PortIndex generated on the server has a different version than the Portfile does when it's parsed locally.

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

Cc: casr l2dy added

comment:3 Changed 10 months ago by l2dy (Zero King)

Owner: set to l2dy
Resolution: fixed
Status: newclosed

In dc5a406dc4c62c63588e7fcac92abc67d0806d13/macports-ports (master):

luajit: update to 2.1.1700008891

  • Fix version difference on systems with different time zones.

Closes: #68740

comment:4 in reply to:  1 Changed 10 months ago by casr (Chris Rawnsley)

Replying to jmroot:

The way the version is set in this port is far too clever for its own good.

Fair challenge. I was optimising the port livecheck side of things to make it a little more convenient to upgrade since LuaJIT moved to a 'rolling release' schedule based on timestamps. Open to suggestions if there are better ways to this. I think upstream is pretty resistant to doing things differently in terms of versioning though.

Note: See TracTickets for help on using tickets.