Opened 7 years ago

Closed 7 years ago

#54975 closed defect (fixed)

FreeRDP: new version is considered older than previous version

Reported by: mf2k (Frank Schima) Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.4.99
Keywords: Cc: l2dy (Zero King)
Port: FreeRDP

Description

The FreeRDP port just got updated, but for some reason, the latest version of base from GitHub is not seeing it.

$ port installed FreeRDP
The following ports are currently installed:
  FreeRDP @1.1.0-beta1-2015031201_3 (active)
$ port outdated 
No installed ports are outdated.
$ port -v outdated FreeRDP 
The following installed ports are outdated:
FreeRDP                        1.1.0-beta1-2015031201_3 > 1.1.0-beta1-20170727_0  !

Change History (5)

comment:2 Changed 7 years ago by kencu (Ken)

perhaps 20170727 should be 2017072701 ?

comment:3 Changed 7 years ago by mf2k (Frank Schima)

Good point. That makes sense that it thinks it is a smaller number because there are fewer digits. Maybe this is a bug in the FreeRDP port and it simply needs an epoch increase?

comment:4 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: l2dy added
Component: baseports
Port: FreeRDP added
Summary: Newer version not being detected by baseFreeRDP: new version is considered older than previous version

Yes, increasing the epoch is another solution.

comment:5 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: set to ryandesign
Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.