Opened 15 years ago
Closed 15 years ago
#24717 closed enhancement (fixed)
Repeated "Portfile changed since last build; discarding previous state" when system clock is very wrong
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | MacPorts 1.9.0 |
Component: | base | Version: | 1.8.2 |
Keywords: | Cc: | ||
Port: |
Description
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.
Change History (1)
comment:1 Changed 15 years ago by jmroot (Joshua Root)
Milestone: | MacPorts Future → MacPorts 1.9.0 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Already fixed, r65246.