Opened 16 years ago

Closed 15 years ago

#2087 closed defect (invalid)

port gets different version than what package expects

Reported by: alrescha@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: base Version: 1.0
Keywords: Cc:


I've seen this happen a few times now. I go to install package A, and it has a dependency on package B v 1.0.0. Port goes out and gets package B, but it's now v 1.0.1. The install fails with a message like this:

---> Fetching gtk2 ---> Attempting to fetch gtk+-2.4.4.tar.bz2 from GNOME/sources/gtk+/2.4 ---> Verifying checksum(s) for gtk2 ---> Extracting gtk2 ---> Configuring gtk2 ---> Building gtk2 with target all ---> Staging gtk2 into destroot ---> Installing gtk2 2.4.4_0 ---> Activating gtk2 2.4.4_0 Error: Target returned: Registry error: gtk2 2.4.0_0 not registered as installed.

In this case, package A was 'etherape'. Here's another instance with ethereal:

---> Fetching libpcap ---> Attempting to fetch libpcap-0.8.3.tar.gz from ---> Verifying checksum(s) for libpcap ---> Extracting libpcap ---> Applying patches to libpcap ---> Configuring libpcap ---> Building libpcap with target all ---> Staging libpcap into destroot ---> Installing libpcap 0.8.3_3 ---> Activating libpcap 0.8.3_3 Error: Target returned: Registry error: libpcap 0.8.3_0 not registered as installed. Error: The following dependencies failed to build: libpcap openssl zlib

Apologies if this is a known bug, I searched on 'dependency', 'dependencies', and 'registery error'.


Change History (2)

comment:1 Changed 15 years ago by blb@…

Since this is an old bug and many changes have been made to DP since, is this still an issue?

comment:2 Changed 15 years ago by blb@…

Resolution: invalid
Status: newclosed

Resolving, lack of response.

Note: See TracTickets for help on using tickets.