[MacPorts] #35221: gconf @2.28.1 Failed to install

MacPorts noreply at macports.org
Tue Jul 17 03:26:44 PDT 2012


#35221: gconf @2.28.1 Failed to install
----------------------------------+-----------------------------------------
 Reporter:  ade_hall@…            |       Owner:  macports-tickets@…                   
     Type:  defect                |      Status:  new                                  
 Priority:  Normal                |   Milestone:                                       
Component:  ports                 |     Version:  2.1.1                                
 Keywords:                        |        Port:  gconf                                
----------------------------------+-----------------------------------------
Changes (by ryandesign@…):

 * cc: cal@… (added)


Comment:

 The terminal transcript you provided shows that MacPorts:

  * installed the pre-built gconf-2.28.1_3.darwin_10.x86_64.tbz2 package
 from our server
  * rev-upgrade ran, which detected that this gconf was in fact broken in
 some way
  * tried to build gconf from source on your system, which failed
  * rev-uprade determined gnome-vfs was broken
  * tried to rebuild gnome-vfs, but since it depends on gconf, tried again
 to build gconf, without cleaning it first, and it failed again
  * repeated the above step once more
  * exited

 We need to see the clean logs of the gconf build, but the above steps mean
 that MacPorts left you with an unclean log again. I'm Cc'ing Clemens, who
 wrote the rev-upgrade feature for us, because this behavior doesn't seem
 optimal.

 ahe_hall, please run "sudo port clean gconf", then run "sudo port -s
 install --no-rev-upgrade gconf". "-s" means build from source; don't use
 the binary from our server. "--no-rev-upgrade" means that even if MacPorts
 thinks things are broken after installation, it should not try to rebuild
 things to fix them. Presumably this build will fail and you can then
 attach that main.log to this ticket, which will hopefully contain enough
 information to help us diagnose the problem.

 We did already have [ticket:34994 one other report] of gconf failing to
 build. There I suggested we might need to update gconf to a newer version.
 So that's something we can try.

-- 
Ticket URL: <https://trac.macports.org/ticket/35221#comment:3>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list