From owner-freebsd-ports@FreeBSD.ORG Mon May 14 12:29:49 2007 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F211C16A406 for ; Mon, 14 May 2007 12:29:48 +0000 (UTC) (envelope-from boris@brooknet.com.au) Received: from pecan.exetel.com.au (pecan.exetel.com.au [220.233.0.17]) by mx1.freebsd.org (Postfix) with ESMTP id 8B5B013C480 for ; Mon, 14 May 2007 12:29:43 +0000 (UTC) (envelope-from boris@brooknet.com.au) Received: from 28.201.233.220.exetel.com.au ([220.233.201.28] helo=[192.168.100.148]) by pecan.exetel.com.au with esmtp (Exim 4.63) (envelope-from ) id 1HnZgH-0002vq-UB; Mon, 14 May 2007 22:29:38 +1000 In-Reply-To: <20070513072616.GA34743@xor.obsecurity.org> References: <20070510212817.GA67897@xor.obsecurity.org> <20070511202905.GO826@turion.vk2pj.dyndns.org> <20070511205243.GI1066@k7.mavetju> <200705120235.01113.danny@ricin.com> <20070512011248.GA39007@xor.obsecurity.org> <20070513071312.GA34544@xor.obsecurity.org> <2A6AA96C-4526-4A72-B30F-973B0C165EF1@brooknet.com.au> <20070513072616.GA34743@xor.obsecurity.org> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Sam Lawrance Date: Mon, 14 May 2007 22:29:30 +1000 To: Kris Kennaway X-Mailer: Apple Mail (2.752.3) Cc: Danny Pansters , freebsd-ports@freebsd.org Subject: Re: first? patch [ HEADS UP: xorg 7.2 ready for testing ] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 May 2007 12:29:49 -0000 On 13/05/2007, at 5:26 PM, Kris Kennaway wrote: > On Sun, May 13, 2007 at 05:20:53PM +1000, Sam Lawrance wrote: >> >> On 13/05/2007, at 5:13 PM, Kris Kennaway wrote: >> >>> On Sun, May 13, 2007 at 05:04:29PM +1000, Sam Lawrance wrote: >>>> >>>> On 12/05/2007, at 11:12 AM, Kris Kennaway wrote: >>>> >>>>> On Sat, May 12, 2007 at 02:35:00AM +0200, Danny Pansters wrote: >>>>> >>>>>> I ran into a little problem with the gstreamer-plugins, to be >>>>>> exact with >>>>>> the 'bad' plugin. What's in a name. Attached patch to gstreamer- >>>>>> plugins which >>>>>> eliminates X11BASE from configure args fixes it. >>>>> >>>>> This actually seems to indicate that something you have installed >>>>> references /usr/X11R6 in a .la file. I actually built this >>>>> successfully myself during the upgrade tests, so I guess something >>>>> went wrong with the upgrade on your machine. Can you please >>>>> provide >>>>> the full log, as well as the result of >>>>> >>>>> find /usr/local/lib -name \*.la | xargs grep /usr/X11R6/lib/ >>>>> libfontconfig.la >>>> >>>> Just a quick "me too". Last night I installed 6.2-RELEASE with >>>> gnome >>>> and goffice from the release packageset, then proceeded to >>>> follow the >>>> xorg upgrade instructions. The two errors I got are listed >>>> below. I >>>> will try to investigate tonight. >>> >>> OK, still waiting for the log from Danny, so maybe you'll get in >>> first >>> with yours. >> >> I hope there's a nice prize, or showgirls springing out of big cakes. >> >> http://people.freebsd.org/~lawrance/xorg-upgrade.bz2 I think I have figured this out. In short: portupgrade does not include new, previously not installed, dependencies in its list of tasks when updating. In this particular case, gstreamer-plugins-bad was built before one of its dependencies was updated, and we end up with a crufty old reference to X11R6. Less short: Before the xorg upgrade, gstreamer-plugins-bad was not installed on my system. It was installed during the upgrade as part of running "portupgrade -a". Upon further inspection of the xorg-upgrade log above I noticed that there were two build attempts for gstreamer-plugins-bad, and neither was directly performed by portupgrade (ie. the ports framework did it). The first attempt was as a dependency of gstreamer-plugins- dts. The second (and successful) attempt was as a dependency of gstreamer-plugins-xvid. I reverted the system to its original state and ran "portupgrade -an" to show the order of updates that portupgrade would perform. gstreamer-plugins-bad was not in the list. I think this means is that if a port being upgraded has a new dependency, that dependency will _not_ be included in the list portupgrade uses to determine which packages to update and at what point. Using portupgrade with the flags -aRn made no difference. A few people have reported their systems updating correctly after a several attempts with "portupgrade -a"; this is possibly one of the reasons. It seems like an effective workaround for the moment. The only issue I can think of is if an out of order build succeeds, and the later update of a dependency breaks something at runtime.