From owner-freebsd-current@FreeBSD.ORG Fri Sep 6 15:35:30 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CEE5AE6A; Fri, 6 Sep 2013 15:35:30 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from winston.madpilot.net (winston.madpilot.net [78.47.75.155]) by mx1.freebsd.org (Postfix) with ESMTP id 61E0028A5; Fri, 6 Sep 2013 15:35:30 +0000 (UTC) Received: from winston.madpilot.net (localhost [127.0.0.1]) by winston.madpilot.net (Postfix) with ESMTP id 3cWjX15Fq6zFTGl; Fri, 6 Sep 2013 17:35:29 +0200 (CEST) X-Virus-Scanned: amavisd-new at madpilot.net Received: from winston.madpilot.net ([127.0.0.1]) by winston.madpilot.net (winston.madpilot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1PcF4VtcSEwb; Fri, 6 Sep 2013 17:35:27 +0200 (CEST) Received: from vwg82.hq.ignesti.it (unknown [77.246.14.163]) by winston.madpilot.net (Postfix) with ESMTPSA; Fri, 6 Sep 2013 17:35:27 +0200 (CEST) Message-ID: <5229F63F.7070704@FreeBSD.org> Date: Fri, 06 Sep 2013 17:35:27 +0200 From: Guido Falsi User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130904 Thunderbird/17.0.8 MIME-Version: 1.0 To: "O. Hartmann" Subject: Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv References: <522985C7.2010303@passap.ru> <20130906170449.64439c27@munin.geoinf.fu-berlin.de> In-Reply-To: <20130906170449.64439c27@munin.geoinf.fu-berlin.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Baptiste Daroussin , AN , Boris Samorodov , FreeBSD ports list , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Sep 2013 15:35:31 -0000 On 09/06/13 17:04, O. Hartmann wrote: > Using portmaster, I'm higly adviced to use option -f, otherwise every > second port I try to update gets interrupted due to missing > libiconv.so.3. It is impossible to update a system unattended and this > is a mess with 200 or even 680 ports to be updated. A waste of time. > > Some ports still rely on methusalem gcc 4.6. But gcc 4.6.3 relies on > some gnuish tools in the port and the compilation fails if those > prerequisits aren't updated first. The description I found > in /usr/ports/UPDATING is quick and dirty - too dirty for being > useful, in my opinion. Did the maintainer ever tried this command > sequence on a "used" machine and not in a clean vbox environment? I have tested it on my two machines at home. Both "lived" ones. On one I had problems, but I did not follow that procedure exactly. On the laptop everything went definitely smoother. > There must be a description of a fallback in UPDATING! I took the > whole day to update on one machine less than the half of the installed > ports and huge ports like libreoffice are still dropping out of the > build and I restart after fixed the missing port that relies on being > recompiled. I hope that reinstalling converters/libiconv will give me > X11 back on my boxes! I can not stay with them 48 hours non stop until > they have completed the messy update. The first backup things that comes to mind is, one can always reinstall libiconv (removing IGNORE), that should allow old binaries to run. I don't suggest updating the other ports while libiconv is installed though, since the include files will conflict and ports could link to the por5ts libiconv instead of the base one. As I told AN, preserving libiconv.so in /usr/local/lib/compat/pkg and then removing the package could help, by allowing the machine to work in a "mixed world". Can you try that? The biggest problem is usually libtool, pulling in old .la files still referencing the non existing libiconv.la file. I don't know of any solution to that. I had to resort to manually listing offending la files and recompiling the owning package. Not optimal :( I am willing to add further information to the UPDATING entry, but I need people with different scenarios to test and report the success of the strategies. Obviously the last resort strategy is deinstalling all ports and reinstalling them, which I agree is terrible. -- Guido Falsi