Date: Sun, 7 Jul 2013 15:17:33 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Marco Steinbach <coco@executive-computing.de> Cc: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: make config: doesn't work - reports ===> Options unchanged : no options menu popping up Message-ID: <20130707151733.23f5e735@thor.walstatt.dyndns.org> In-Reply-To: <51D960D5.5060503@executive-computing.de> References: <20130707122551.0a6bca03@thor.walstatt.dyndns.org> <51D960D5.5060503@executive-computing.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/pfkwwx4j9hsKOukZB4IPN2p Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sun, 07 Jul 2013 14:36:37 +0200 Marco Steinbach <coco@executive-computing.de> wrote: > O. Hartmann wrote on 07.07.2013 12:25: > >=20 > > On boxes running recent /usr/ports and recent soutces( FreeBSD > > 10.0-CURRENT #0 r252885: Sat Jul 6 16:09:09 CEST 2013) I'm unable > > to configure some ports, for instance www/firefox: > >=20 > > /usr/ports/www/firefox # make config > > =3D=3D=3D> Options unchanged > >=20 > > Even performing "make rmconfig" and repeating above procedure > > doesn't change anything. I can not change options anymore! > >=20 > > Please CC me, I'm not subsrcribing the list. >=20 > [...] >=20 > I've seen this kind of behaviour with dialog4ports in various=20 > situations, but since dialog4ports-0.1.1 or so, I've never > encountered this again. >=20 > Here's a few shots in the dark: >=20 > - Maybe you're running an outdated version of dialog4ports. Remove=20 > dialog4ports, then make config in www/firefox again. This will > trigger installation of whatever the most recent version of > dialog4ports is in your ports tree. > - Check your environment. Unset DIALOG4PORTS or DIALOG, if they're > set, then try make config again. >=20 > MfG CoCo Thanks for the hint.=20 rebuilding dialog4ports made the problem go away. It is strange. I usually have up to date ports, even dialog4ports. But since this happens on CURRENT (I didn't see this on 9.1-STBALE yet) I guess it is due to CURRENT is a moving target ... Regards, Oliver --Sig_/pfkwwx4j9hsKOukZB4IPN2p Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBAgAGBQJR2WpzAAoJEOgBcD7A/5N8JX4IAKxAn5DPzzjlrVgCS1+0U+AU 2OhhyHpPOLTKw0Q4YtMdfp0vjUwvfVDEAbTYDMNIuMwQm1KBN3ya2NvWKePRcaX2 hH43hjXMtwJ4ZGdsCFqNhPolPMVcjeo2Vnlj439Yp1xl15QhcsRS+FjMR8s2iqEM Mxqzg2WYhcYLUU+pEKwUXrwNNZggn/+J8ljFonkIWXX5FghUI5Ym8QOOV/CYLbhT 4MJNoaOvMt3JGfsQXWn0YUc+43pbOXXsN9IF3C3WDrwSqJDGe5UJdU0qCcZZxoQ8 ZuA+1SC5RJ2n0x6TSqsNPQv3fFnZf0fJJ0fScdTJ7w/J+QoysT+JJekScHox77s= =g4XQ -----END PGP SIGNATURE----- --Sig_/pfkwwx4j9hsKOukZB4IPN2p--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130707151733.23f5e735>