Date: Sun, 2 Jun 2013 09:00:53 -0400 From: Jerry <jerry@seibercom.net> To: freebsd-ports@freebsd.org Subject: Re: Can't build devel/qt4-corelib any more -- help? Message-ID: <20130602090053.14dfe6dc@scorpio> In-Reply-To: <20130602123138.GA1429@albert.catwhisker.org> References: <20130520015433.GD1291@albert.catwhisker.org> <86obbp1n8o.fsf@orwell.Elisa> <20130601223445.GJ1334@albert.catwhisker.org> <864ndgx38g.fsf@orwell.Elisa> <20130602123138.GA1429@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/yM2nU9kehJ4mGxN_=IscdJK Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sun, 2 Jun 2013 05:31:38 -0700 David Wolfskill articulated: > On Sun, Jun 02, 2013 at 12:37:35PM +0300, Raphael Kubo da Costa wrote: > > > /var/db/pkg > > > albert(9.1-S)[10] echo qt* > > > echo: No match. > > > albert(9.1-S)[11] > >=20 > > Can you also check that you don't have some stray q* headers in > > /usr/local/include? > > ... >=20 > Sorry; I erred: I was confused about which system was involved. The > above wasn't the "problem child" -- that ... honor ... was reserved > for my desktop at work. >=20 > And that one did have qt-3.3.8_14 installed. :-( >=20 > "pkg_delete qt-3.3.8_14" reported that: > pkg_delete: package 'qt-3.3.8_14' is required by these other packages > and may not be deinstalled: > pinentry-0.8.1_3 > gnupg-2.0.20 >=20 > So... fine; one "pkg_delete -f qt-3.3.8_14" later, and it was gone. >=20 > I then attempted "portmaster security/pinentry security/gnupg" (in > an attempt to ensure that they wouldn't wander off into the weeds > or something equally non-useful). That failed, claiming: >=20 > =3D=3D=3D>>> security/pinentry 1/2 >> x11-toolkits/qt33 (1/1) > 0;portmaster: security/pinentry 1/2 >> x11-toolkits/qt33 (1/1)^G > =3D=3D=3D>>> Port directory: /usr/ports/x11-toolkits/qt33 >=20 > =3D=3D=3D>>> This port is marked DEPRECATED > =3D=3D=3D>>> No upstream activity since 2008; unmaintained >=20 > =3D=3D=3D>>> If you are sure you can build it, remove the > DEPRECATED line in the Makefile and try again. >=20 > =3D=3D=3D>>> Update for x11-toolkits/qt33 failed > =3D=3D=3D>>> Aborting update >=20 >=20 > It *finally* occurred to me that maybe there was a (default?) option > set for security/pinentry that might be bringing in QT3. >=20 > So I tried "portmaster --force-config security/pinentry > security/gnupg"; sure enough, all of the options for pinentry -- > including one labelled "QT3 Qt3 frontend" -- were selected. I > de-selected that one, and that step then proceeded without further > incident. >=20 > After that, I was able to install devel/qt4-corelib. (I then ran > "portmaster --check-depends" -- just because I figured it couldn't > hurt.) >=20 >=20 > In my defense, I suspect that it had been a few years since I had > looked at the options for security/pinentry. And the port's > Makefile, at r317525, appears to specify QT3 as a default option. > (Or am I confused -- about that, I mean?) >=20 > IIRC, I only picked up security/pinentry as a port on which > security/gnupg depended -- it was pretty far from my focus at the time > (of initially installing gnupg -- probably a bit over 5 years ago). > And ports on which security/pinentry depended would be even further > from my focus: I'm not really a developer; I don't write Qt > applications. I merely wanted to be able to handle PGP-compatible > signing & encryption in mutt. >=20 > In any case: Thank you *very* much for your help. I doubt I would > have made the connection to Qt3 had it not been pointed out to me > rather explicitly. I reported the problem with the "security/pinentry" port several months ago. I was told then that the default configuration would be changed. Either someone forgot to do it, or changed their minds. To require by default a depreciate port seems rather short sighted. --=20 Jerry =E2=99=94 Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ --Sig_/yM2nU9kehJ4mGxN_=IscdJK Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBAgAGBQJRq0IPAAoJEF2rWD2do7dNOrAH/ibz+/SIWGD8+vFTY7zrn1iT VKbrOU7dNL2XsSjEhrxxnxbmPhwHIGmFC1TKRhVPSVa+qr5Rjonz2y14Ewkqfcid RcMbBTSq0BhoiSSEA1jLmygFsezRpFdVymEQvLSw8B3DpTl61SCXWv+Wv+wIyG1o E9vH8qWoNxM69MLe63QBeqS+3lavSs6JXW0UoXPkn66dxuAXtOGdUyqgEwtoxop+ g85i0q+GbaUC7dwQJnwOAcr9XMeMSQiVB9STJc48vNlQLvus/r50xXRy4uwiTXJ9 s2lYPiUTla0hVtG7EacWTUY18EO4WbT00ozaJpkDWTy2Vjt611MvFa+zOfRhaHc= =sjpk -----END PGP SIGNATURE----- --Sig_/yM2nU9kehJ4mGxN_=IscdJK--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130602090053.14dfe6dc>