Opened 14 years ago

Closed 14 years ago

#23894 closed defect (invalid)

sudo port install zlib fails on Snow Leopard

Reported by: glmuelle@… Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 1.8.2
Keywords: Cc: landonf (Landon Fuller)
Port: zlib

Description (last modified by mf2k (Frank Schima))

Running "sudo port install zlib" on mac os 10.6.2 fails with the following error message:

Portfile changed since last build; discarding previous state.
--->  Computing dependencies for zlib
Portfile changed since last build; discarding previous state.
--->  Fetching zlib
Portfile changed since last build; discarding previous state.
--->  Verifying checksum(s) for zlib
Portfile changed since last build; discarding previous state.
--->  Extracting zlib
Portfile changed since last build; discarding previous state.
--->  Applying patches to zlib
Error: Target org.macports.patch returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_archivers_zlib/work/zlib-1.2.3" && /usr/bin/patch -p0 < '/opt/local/var/macports/sources/rsync.macports.org/release/ports/archivers/zlib/files/patch-Makefile-static.diff'" returned error 1
Command output: sh: line 0: cd: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_archivers_zlib/work/zlib-1.2.3: No such file or directory

Error: Status 1 encountered during processing.
Before reporting a bug, first run the command again with the -d flag to get complete output.

Change History (6)

comment:1 Changed 14 years ago by mf2k (Frank Schima)

Cc: landonf@… added
Description: modified (diff)
Keywords: zlib install removed
Owner: changed from macports-tickets@… to ryandesign@…
Priority: HighNormal

comment:2 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

I doubt this is zlib-specific. I suspect you'd get the same error for any port whose distfile is gzip-compressed. I suspect the gzip or possibly tar command on your OS is not functioning correctly. Please check, and if it's not working, you may need to replace it from your OS backups or reinstall your operating system.

comment:3 Changed 14 years ago by jmroot (Joshua Root)

Looks like your system clock is just set wrong.

comment:4 in reply to:  3 ; Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to jmr@…:

Looks like your system clock is just set wrong.

Interesting. What makes you suppose this?

comment:5 in reply to:  4 ; Changed 14 years ago by raimue (Rainer Müller)

Replying to ryandesign@…:

Replying to jmr@…:

Looks like your system clock is just set wrong.

Interesting. What makes you suppose this?

The message "Portfile changed since last build; discarding previous state." appears if the Portfile's modification time is newer than the state file. As this appears at every phase I guess the current system time is prior to the Portfile modification time, therefore always causing this message.

Correcting your system clock and sudo port selfupdate should help in this case, as that would reset the modification time on Portfiles.

comment:6 in reply to:  5 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: invalid
Status: newclosed

Replying to raimue@…:

The message "Portfile changed since last build; discarding previous state." appears [...] at every phase

Amazing how the brain edits out things it isn't expecting to see. :)

Note: See TracTickets for help on using tickets.