[MacPorts] #24717: Repeated "Portfile changed since last build; discarding previous state" when system clock is very wrong

MacPorts noreply at macports.org
Wed Apr 28 14:28:22 PDT 2010


#24717: Repeated "Portfile changed since last build; discarding previous state"
when system clock is very wrong
-------------------------------------+--------------------------------------
 Reporter:  ryandesign@…             |       Owner:  macports-tickets@…                   
     Type:  enhancement              |      Status:  new                                  
 Priority:  Normal                   |   Milestone:  MacPorts Future                      
Component:  base                     |     Version:  1.8.2                                
 Keywords:                           |        Port:                                       
-------------------------------------+--------------------------------------
 We have received several reports of this kind of problem:

 {{{
 Portfile changed since last build; discarding previous state.
 --->  Fetching libiconv
 Portfile changed since last build; discarding previous state.
 --->  Verifying checksum(s) for libiconv
 Portfile changed since last build; discarding previous state.
 --->  Extracting libiconv
 Portfile changed since last build; discarding previous state.
 }}}

 And then the next phase fails because the directory it expected to see
 doesn't exist.

 At this point Joshua replies that the user's system clock is set wrong.

 MacPorts should exit with a clear error message about this if the system
 clock is so wrong that it will trigger this confusing behavior.

-- 
Ticket URL: <http://trac.macports.org/ticket/24717>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list