From owner-freebsd-gnome@FreeBSD.ORG Sat Mar 15 18:40:02 2014 Return-Path: Delivered-To: gnome@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 01093D6D for ; Sat, 15 Mar 2014 18:40:02 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E312B8BC for ; Sat, 15 Mar 2014 18:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s2FIe12Z063345 for ; Sat, 15 Mar 2014 18:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s2FIe1Yc063344; Sat, 15 Mar 2014 18:40:01 GMT (envelope-from gnats) Date: Sat, 15 Mar 2014 18:40:01 GMT Message-Id: <201403151840.s2FIe1Yc063344@freefall.freebsd.org> To: gnome@FreeBSD.org From: John Hein Subject: Re: ports/185252: x11-toolkits/pango can't find fonts X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: John Hein List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Mar 2014 18:40:02 -0000 The following reply was made to PR ports/185252; it has been noted by GNATS. From: John Hein To: miwi@FreeBSD.org Cc: paulbeard@gmail.com, gnome@FreeBSD.org, bug-followup@FreeBSD.org Subject: Re: ports/185252: x11-toolkits/pango can't find fonts Date: Sat, 15 Mar 2014 12:30:33 -0600 miwi@FreeBSD.org wrote at 15:50 GMT on Mar 15, 2014: > hi, could u please check if the problem still exist with the current > portstree? I noticed the problem with r348052 (~ March 13). This was after the change to make pango support staging. I just updated to r348357 which changed the pango-querymodules invocation in pkg-plist to use --update-cache (and put the module list in lib/pango/1.8.0/modules.cache). That fixes the problem I reported. Thanks. It's probably wise to use pango-querymodules --update-cache --system (to avoid possible pollution due to pango config in the install user's home directory), but that's apple polishing. I'd also use %%PREFIX%% instead of %%LOCALBASE%% (or just leave the absolute path off altogether) for the pango-querymodules invocation in pkg-plist. Also apple polishing unrelated to the bug.