From owner-freebsd-x11@FreeBSD.ORG Thu Nov 17 22:52:30 2005 Return-Path: X-Original-To: freebsd-x11@freebsd.org Delivered-To: freebsd-x11@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E5D416A425 for ; Thu, 17 Nov 2005 22:52:30 +0000 (GMT) (envelope-from dejan.lesjak@ijs.si) Received: from mail.ijs.si (mail.ijs.si [193.2.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24C7343D45 for ; Thu, 17 Nov 2005 22:52:29 +0000 (GMT) (envelope-from dejan.lesjak@ijs.si) Received: from localhost (mail.ijs.si [193.2.4.66]) by patsy.ijs.si (Postfix) with ESMTP id 9639817B935; Thu, 17 Nov 2005 23:52:28 +0100 (CET) Received: from mail.ijs.si ([193.2.4.66]) by localhost (patsy.ijs.si [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 95735-06; Thu, 17 Nov 2005 23:52:25 +0100 (CET) Received: from radagast.ijs.si (radagast.ijs.si [193.2.4.168]) by patsy.ijs.si (Postfix) with ESMTP id 14A8817B92C; Thu, 17 Nov 2005 23:52:24 +0100 (CET) Received: from localhost.ijs.si (localhost.ijs.si [127.0.0.1]) by radagast.ijs.si (Postfix) with ESMTP id C288F1702E; Thu, 17 Nov 2005 23:52:24 +0100 (CET) From: Dejan Lesjak To: James Long Date: Thu, 17 Nov 2005 23:52:23 +0100 User-Agent: KMail/1.8.3 References: <200511172215.jAHMFNpI000954@ns.museum.rain.com> In-Reply-To: <200511172215.jAHMFNpI000954@ns.museum.rain.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511172352.24125.dejan.lesjak@ijs.si> X-Virus-Scanned: amavisd-new at ijs.si Cc: freebsd-x11@freebsd.org, Andy Fawcett Subject: Re: xorg-clients conflicts with xterm (patch) X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 22:52:30 -0000 On Thursday 17 of November 2005 23:15, James Long wrote: > > [snip] > > > > > ===> Installing for xorg-clients-6.8.2_1 > > > ===> xorg-clients-6.8.2_1 depends on package: xterm>0 - not found > > > ===> Verifying reinstall for xterm>0 in /usr/ports/x11/xterm > > > ===> Installing for xterm-206_1 > > > > > > ===> xterm-206_1 conflicts with installed package(s): > > > xorg-clients-6.8.2 > > > > And again, above is what confuses me - you don't have xorg-clients > > installed yet so why would installing xterm complain about installed > > conflicting xorg-clients. I wouldn't want to trouble you more but it > > would be interesting to know the contents of /var/db/pkg at that time. > > I would surmise the conflict is because numerous other packages depend > upon xorg-clients. So even though the package is temporarily missing, > there are entries to it in the pkgdb dependency tree. Possible, but then I have dependencies also and upgrade works... > Sorry, I don't have a snapshot of the /var/db/pkg/ directory at the time. > However, the pkgdb -F output may show you what I mean about the > dependencies. Yes, I see what you mean. > I don't mean to draw this out, I simply wanted to inquire about the > Makefile syntax, and the fact that -- perhaps coincidentally -- editing > out the ">0" and then doing a "make install" in xorg-clients made all > my problems go away. There is also the untested theory that only > portupgrade had a problem -- all my "conflict" messages come from > portupgrade. Toward the end of my episode, since portupgrade had already > build xorg-clients, but failed to install it, I went into > /usr/ports/x11/xorg-clients, edited out the ">0" and was able to do a > successful "make install" that installed xorg-clients and xterm. I > thought the Makefile edit was what did the trick for me. Perhaps it > was doing the manual "make install" that worked, and would have worked > even with the stock makefile. Who knows. > > If the patch has no value, so be it. I just wanted to share what I > had found that worked for me, again, perhaps just by coincidence. It works if you have installed xterm that installs xterm executable. It wouldn't work for previous versions of xterm which installed xterm-static binary. So your patch might still help someone that already has xterm-206_1 installed and bumps into similar problem. It just can't go into ports cvs - the upgrade described in UPDATING would fail with this dependency. Thanks for the help. Given Andy's mail, I do wonder if "make install" as opposed to portupgrade would work without making change to Makefile though. Dejan