From owner-freebsd-stable@FreeBSD.ORG Sat Jan 14 19:05:35 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79216106566B for ; Sat, 14 Jan 2012 19:05:35 +0000 (UTC) (envelope-from andre@drenet.info) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2DDC18FC0A for ; Sat, 14 Jan 2012 19:05:34 +0000 (UTC) Received: by vbbfp1 with SMTP id fp1so3223988vbb.13 for ; Sat, 14 Jan 2012 11:05:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=drenet.info; s=google; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=pgdXCkjLLXP6TRW3FBWd70Ck6dMheHmso5k2Mdko3P8=; b=XgnxFQVv9U3vvMFet9EqGJyu51dOPWHpO+zodP9TNPrSKkgEuMjyATpdVoglvbIFZl Q2mX7AxuKmO4GikUsTPz6etHxz29kEKAaL9DHy7laxN4ddsy1bO7dwiNVJfSXNOaE21N ZX9cet8qKI8ML0dJxhnmdbrGy72nfIl4pW6q4= MIME-Version: 1.0 Received: by 10.52.29.7 with SMTP id f7mr2750920vdh.130.1326567934334; Sat, 14 Jan 2012 11:05:34 -0800 (PST) Received: by 10.220.18.204 with HTTP; Sat, 14 Jan 2012 11:05:34 -0800 (PST) X-Originating-IP: [98.199.43.85] In-Reply-To: References: <4F11558E.6010806@restart.be> Date: Sat, 14 Jan 2012 13:05:34 -0600 Message-ID: From: Andre Goree To: Chris Rees Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: libutempter X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2012 19:05:35 -0000 On Sat, Jan 14, 2012 at 12:34 PM, Chris Rees wrote: > > On 14 Jan 2012 18:26, "Andre Goree" wrote: > > > > On Sat, 14 Jan 2012 04:14:38 -0600, Henri Hennebert > wrote: > > > >> On 01/14/2012 09:47, Andre Goree wrote: > >>> > >>> On Tue, 10 Jan 2012 19:58:13 -0600, Andre Goree > wrote: > >>> > >>>> I recently csup'd 9-STABLE and was able to get it working along with > my > >>>> custom kernel. I'm now in the process of rebuilding all my ports, and > >>>> I've > >>>> come across something when running 'portmaster -af' that I can't seem > to > >>>> find any information on. > >>>> > >>>> ===>>> Launching child to reinstall libutempter-1.1.5_1 > >>>> > >>>> ===>>> Port directory: /usr/ports/sysutils/libutempter > >>>> > >>>> ===>>> This port is marked IGNORE > >>>> ===>>> is now contained in the base system > >>>> > >>>> > >>>> ===>>> If you are sure you can build it, remove the > >>>> IGNORE line in the Makefile and try again. > >>>> > >>>> ===>>> Update for libutempter-1.1.5_1 failed > >>>> ===>>> Aborting update > >>>> > >>>> Terminated > >>>> > >>>> > >>>> I figure, "ok I'll just delete the package and move on." However, > there > >>>> are many packages I have installed that depend on libutemper. I would > >>>> still just proceed with the removal given that the functionality is > >>>> provided in base now, however I don't want to break all these ports > and > >>>> have to deal with the mess when I portmaster -af again. > >>>> > >>>> What is the recommended action here? Should I just force exclude that > >>>> port > >>>> from the upgrade? That's probably the easiest way but I'd have to > deal > >>>> with this at some point. > >>>> > >>>> Thanks in advance for any advice > >>>> > >>>> -- > >>>> Andre Goree > >>>> andre@drenetinfo > >>> > >>> > >>> So I've rebuilt everything that I could, but when I get to the ports > >>> that depend on libutempter, I get an error that they could not be > >>> reinstalled due to a failure with libutempter :/ > >>> > >>> ---> Skipping 'www/opera' (opera-11.60) because a requisite package > >>> 'libutempter-1.1.5_1' (sysutils/libutempter) failed (specify -k to > force) > >>> ---> Skipping 'www/opera-linuxplugins' (opera-linuxplugins-11.60) > >>> because a requisite package 'opera-11.60' (www/opera) failed (specify > -k > >>> to force) > >>> ---> Skipping 'deskutils/kdeplasma-addons' (kdeplasma-addons-4.7.3) > >>> because a requisite package 'kdepimlibs-4.7.3' (deskutils/kdepimlibs4) > >>> failed (specify -k to force) > >>> ---> Skipping 'graphics/libkdcraw-kde4' (libkdcraw-4.7.3) because a > >>> requisite package 'libutempter-1.1.5_1' (sysutils/libutempter) failed > >>> (specify -k to force) > >>> > >>> > >>> I installed misc/compat8x, however it informed my that I'd need to add > >>> "" to the kernel conf. When I try to do that, I'm met with this error: > >>> > >>> /usr/src/sys/amd64/conf/DESKTOPKERN9: unknown option "COMPAT_FREEBSD8" > >>> *** Error code 1 > >>> Stop in /usr/src. > >>> > >>> > >>> Which is weird, because: > >>> > >>> [root@desktop src]# uname -r > >>> 9.0-STABLE > >>> > >>> > >>> Meaning I'm certainly running 9.0-STABLE. So what gives re: that error > >>> above about "unknown option"? I even tried to csup source and > >>> buildworld again, but to no avail -- the error remains. > >>> > >>> > >> I upgrade my ports with portupgrade. > >> After removing libutempter I just run `pkgdb -Fu' and then > >> I can proceed with the update of depending ports. > >> I don't need compat8x. > >> > >> Henri > >> _______________________________________________ > >> freebsd-stable@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable > >> To unsubscribe, send any mail to " > freebsd-stable-unsubscribe@freebsd.org" > > > > > > > > Thanks, yeah upon further research last night I discovered that > "COMPAT_FREEBSD8" is not kernel option and that compat8x doesn't play a > role at all in my situation. > > > > Also thanks for the suggestion, that worked perfectly! :) > > > > > > > >> > >> Just pkg_delete -f it. > >> > >> Since it's in base, its absence won't cause a problem. > >> > >> Chris > > > > > > > > Yeah I was mored concerned (erroneously, it would seem) with dependency > hell rather than missing libs :p After just removing it then doing a > pkgdb -Fu, I'm good to go. I've done this before in the past with pkg's > I've removed, so kinda disheartening that I overlooked it for so long, heh. > I guess I don't fully grasp the relationship between ports and pkgs which > lead to all this confusion. > > > > In any case, it's resolved now, thanks everyone who replied :) > > Woah, whatever you do, don't switch TO portupgrade! It does nothing that > other tools can't, is unmaintained and is unlikely to work with Ruby 1.9, > and unless that is fixed it's going to die fairly soon. > > Chris > Thanks, but I'm not switching TO anything, it's what I've been using and what I'm comfortable with. What gave the impression that I hadn't already been using portupgrade?