From owner-freebsd-gnome@FreeBSD.ORG Sat Jan 5 12:36:04 2008 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0AF0A16A4BF; Sat, 5 Jan 2008 12:36:04 +0000 (UTC) (envelope-from rehsack@web.de) Received: from fmmailgate02.web.de (fmmailgate02.web.de [217.72.192.227]) by mx1.freebsd.org (Postfix) with ESMTP id AD8A413C458; Sat, 5 Jan 2008 12:36:03 +0000 (UTC) (envelope-from rehsack@web.de) Received: from smtp05.web.de (fmsmtp05.dlan.cinetic.de [172.20.4.166]) by fmmailgate02.web.de (Postfix) with ESMTP id A7CF0C4492F1; Sat, 5 Jan 2008 13:36:01 +0100 (CET) Received: from [80.134.66.109] (helo=waldorf.muppets.liwing.de) by smtp05.web.de with esmtp (TLSv1:AES256-SHA:256) (WEB.DE 4.108 #208) id 1JB8Ft-00061O-00; Sat, 05 Jan 2008 13:36:01 +0100 Message-ID: <477F79AE.4020403@web.de> Date: Sat, 05 Jan 2008 12:35:58 +0000 From: Jens Rehsack User-Agent: Thunderbird 2.0.0.9 (X11/20080104) MIME-Version: 1.0 To: araujo@FreeBSD.org References: <477EA66C.6060300@web.de> <477ED631.1060905@FreeBSD.org> In-Reply-To: <477ED631.1060905@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: rehsack@web.de X-Sender: rehsack@web.de X-Provags-ID: V01U2FsdGVkX1/EXalZVmObBq4Np2Xr8XxiUXYAJG4B+/P+zNHG 4ZqFCCToMuxTmrX1FePprDuwDvlejSYwNWPWXzWLbyavJEsm9t FZlkEsDYQ= Cc: FreeBSD GNOME Users , Hardy Schumacher Subject: Re: Port x11-fm/gnome-commander2 marked as broken? X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jan 2008 12:36:04 -0000 Marcelo Araujo wrote: > Jens Rehsack wrote: >> Hi Marcelo, >> >> I've seen you've marked port x11-fm/gnome-commander2 as broken for >> OSVERSION < 700000. >> If I understood pr ports/118840 correctly, it doesn't run on OSVERSION >>> 700000 - please >> correct me, when I'm wrong. >> >> I'm unsure 'bout the PR, because there is nothing referenced what the >> submitter had >> tested. Maybe it's the same bug (which noone reports to FreeBSD, >> because it's a >> gnome-commander bug) as http://bugzilla.gnome.org/show_bug.cgi?id=468685. >> >> Would be great if the patch in above named bug is tested to be a fix >> for submitted >> problem. For my system (FreeBSD waldorf.muppets.liwing.de >> 6.3-PRERELEASE FreeBSD >> 6.3-PRERELEASE #0: Sat Dec 15 12:14:20 UTC 2007 >> root@waldorf.muppets.liwing.de:/usr/obj/usr/src/sys/WALDORF amd64) I >> can affirm, that >> currently built (10 minutes ago) gnome-commander2 runs like a clockwork. >> >> Best regards, >> Jens >> > Hi dear Jens. Hi Marcelo, > You are right! > The problem occurs only with the 7.X and 8-Current. > Before the commit, many users made a test and reported the problem for > me. The last user is nox@(via IRC)! > You have a 7.X or 8-Current on AMD64? Not yet. For the moment my AMD64-machine runs with 6.3-RC2. I work on a portupgrade feature to build parallel - and I want to finish it before updating to 7.0. > You can make a test with new patch? > Diff: http://people.freebsd.org/~araujo/logs/gnome-commander2.diff Not yet, but maybe Hardy can do? After all he submitted the problem :) > I put this port to build inside 5.X, 6.X, 7.X and 8-CURRENT on AMD64, > but I only make a build I can't run this, although the package build > fine, I'm not sure about the bug is fixed. > I need another couple eyes to check it also. I think, in 1-2 weeks I can give you an answer on my own. But then, 6.x test machine on amd64 is gone ;) > NOTE: If this patch don't solve the problem, I change the BROKEN message > and fix the OSVERSION check. Seems, there're not so many FreeBSD/amd64 Gnome-Commander users outside, so you have time :) > Thanks a lot by report > Best Regards. Best regards, Jens