From owner-freebsd-gnome Mon Jan 28 7:50:13 2002 Delivered-To: freebsd-gnome@freebsd.org Received: from mail.musha.org (daemon.musha.org [61.122.44.178]) by hub.freebsd.org (Postfix) with ESMTP id B5C3637B4A6; Mon, 28 Jan 2002 07:48:47 -0800 (PST) Received: from daemon.musha.org (daemon.local.idaemons.org [192.168.1.1]) by mail.musha.org (Postfix) with ESMTP id 2085F4D960; Tue, 29 Jan 2002 00:48:46 +0900 (JST) Date: Tue, 29 Jan 2002 00:48:46 +0900 Message-ID: <86u1t6cw81.wl@daemon.musha.org> From: "Akinori MUSHA" To: Maxim Sobolev Cc: John Merryweather Cooper , freebsd-gnome@FreeBSD.org Subject: Re: FOUND source of problem causing Nautilus Icons to be Barfed--misc/gnomemimedata In-Reply-To: <3C553357.517D04A2@FreeBSD.org> References: <20020126022936.A51353@johncoop.MSHOME> <3C553357.517D04A2@FreeBSD.org> User-Agent: Wanderlust/2.9.5 (Unchained Melody) SEMI/1.14.3 (Ushinoya) LIMIT/1.14.7 (Fujiidera) APEL/10.3 MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 081D 099C 1705 861D 4B70 B04A 920B EFC7 9FD9 E1EE MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-gnome@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At Mon, 28 Jan 2002 13:17:43 +0200, sobomax wrote: > John Merryweather Cooper wrote: > > > > I just figured out how to get the icons working again for Nautilus. > > misc/gnomemimedata is not actually getting built (except maybe on a new > > system). As a result, gnome-vfs.[keys|mime] files are not being > > installed. Forcing a reinstall of misc/gnomemimedata (which resulted > > in a tarball download and build) cured the problem. > > > > As a suggested fix, change the dependency file for ports that rely on > > misc/gnomemimedata to gnome-vfs.keys since this appears to be the > > "critical" file. > > Uhmm, no. The only people affected were those who used portupgrade, so > that I think the problem is with portupgrade, not with gnome ports. I'm not going to waste my time unleashing and messing with the "heavily-chained" beast when I don't use it, but I can give portupgrade users a couple of general hints: 1. When portupgrading something like GNOME components, ALWAYS specify the -R option (i.e. portupgrade -R gnome) to ensure that all the requisite packages have been upgraded before the dependent packages are built. If it still gets some dependent packages dysfunctional, then that will be the ports' problem. If a package Y stops working after upgrading one of its requisite packages called X, then the PORTREVISION of the package Y should have been bumped in the first place where the package X was upgraded, because the package Y needs rebuilding. 2. It's handier to use packages instead of ports (i.e. portupgrade -PP -R gnome) especially for something stubborn like GNOME, since the packages created on the package builders are all built in clean-room environments and they are thus built and supposed to work properly. Note: In this case, you must wait for up to a week long until the packages of the latest ports are built on bento and appear on FTP sites. -- / /__ __ Akinori.org / MUSHA.org / ) ) ) ) / FreeBSD.org / Ruby-lang.org Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp "Somewhere out of a memory.. of lighted streets on quiet nights.." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-gnome" in the body of the message