From owner-freebsd-ports@freebsd.org Tue Aug 4 00:15:47 2015 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7406D9B2A4D for ; Tue, 4 Aug 2015 00:15:47 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3AB82C09 for ; Tue, 4 Aug 2015 00:15:47 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by oihn130 with SMTP id n130so11175004oih.2 for ; Mon, 03 Aug 2015 17:15:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=5vD5uVmnPck3+dVNGAd2jKbPoZUYgBAswUm7DnOWLJ0=; b=j6K5sk99U0OsaisN/brlWTvpM7hw4VFxV0KYbt1M2AaEMVKzrLrh03fww1zruwoPeo obxuEYGNqVTR/Fs7mSAl98eaqOCZvr79WDvYKOMpqrwO3ltVzCi6IdYlqomXt/emmIWZ +Wg0l0Q2a56xkrSNTUsWJL3Nb10Vzf5DDacgKicZ/bL5wjisMEnWlakM8sSsuR9P8eiO XvgC3Igdf3Py8hEKxhZGaoCHP5nMrmOlkQ1NMoFOpllErwK/E4yyRSKGilJFYaitg8j7 v/PgdzjiPAygemU263MZEtWNNaU1uLkJPY3+QXTM4NtylThEDh2o77IVyypvj8T6Bg9v +UqQ== MIME-Version: 1.0 X-Received: by 10.202.87.22 with SMTP id l22mr572798oib.91.1438647346510; Mon, 03 Aug 2015 17:15:46 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.202.221.69 with HTTP; Mon, 3 Aug 2015 17:15:46 -0700 (PDT) In-Reply-To: <20150803230330.1769f862@kirk.drpetervoigt.private> References: <20150803230330.1769f862@kirk.drpetervoigt.private> Date: Mon, 3 Aug 2015 17:15:46 -0700 X-Google-Sender-Auth: 1zpjMXGu6UDwKRP-RYwmu9W4fFU Message-ID: Subject: Re: Problems with update to print/tex-luatex From: Kevin Oberman To: "Dr. Peter Voigt" Cc: Koop Mast , FreeBSD Ports ML Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2015 00:15:47 -0000 On Mon, Aug 3, 2015 at 2:03 PM, Dr. Peter Voigt wrote: > On Mon, 3 Aug 2015 13:04:19 -0700 > Kevin Oberman wrote: > > > When I tried updating print/tex-luatex today, the install phase > > failed with a number of missing files. The log showed that the port > > uses luatex in the install phase but fails due to a missing .so, > > poppler.so.49. This has been superseded by libpoppler.so.53, but the > > install was defaulting to the previously built binary, not the newly > > built one. > > > > I was able to get the port installed by deleting the existing port > > (pkg delete tex-luatex) and > > deleting work/.stage_done.luatex._usr_local and re-running stage and > > install. > > > > I think a note to that effect should be in UPDATING. Obviously this > > does impact new installs or poudriere build and probably not package > > installs, but it does hit upgrades. > > Kevin Oberman, Network Engineer, Retired > > E-mail: rkoberman@gmail.com > > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > _______________________________________________ > > freebsd-ports@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to > > "freebsd-ports-unsubscribe@freebsd.org" > > Well, I can confirm this behavior from my today experiences with > print/tex-luatex. As a result of my upgrade attempt my old > print/tex-luatex packages was deleted. > > I just upgraded all remaining TeXLive packages and tried a fresh > installation of print/tex-luatex: This time it installed just fine. > > I am far from understanding these miracles but I have learned my ports > lesson: Some package refuse to upgrade while being installed - the > error messages, however are quite different. > > Peter > This is annoyingly common and seldom caught because the standard test method is a virgin install. It can involve using the wrong header files, the wrong shareable, or the wrong executable. As the errors can be be triggered in a variety of ways, they can look quite different. Usually the log can point out the issue as it did in this case. This was an issue with libchamplain for years, but was finally fixed. -- Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683