Date: Sun, 28 Aug 2011 21:49:33 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Chris Rees <crees@freebsd.org> Cc: dinoex@freebsd.org, freebsd-ports@freebsd.org Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken Message-ID: <20110828184933.GY17489@deviant.kiev.zoral.com.ua> In-Reply-To: <CADLo839RYem1ngPsxbO%2BxtW6QXpR5jhEDfvMjssGAS8_4V3jAQ@mail.gmail.com> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <BLU0-SMTP182102B9C96837517ECB6BB93150@phx.gbl> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <CADLo839RYem1ngPsxbO%2BxtW6QXpR5jhEDfvMjssGAS8_4V3jAQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Hwc0ilm0gE8kvSWy
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sun, Aug 28, 2011 at 07:41:20PM +0100, Chris Rees wrote:
> On 28 August 2011 19:33, Kostik Belousov <kostikbel@gmail.com> wrote:
> > On Sun, Aug 28, 2011 at 02:13:59PM -0400, Sahil Tandon wrote:
> >> On Sun, 2011-08-28 at 20:30:59 +0300, Kostik Belousov wrote:
> >>
> >> > On Sun, Aug 28, 2011 at 01:26:51PM -0400, Sahil Tandon wrote:
> >> > > On Sun, 2011-08-28 at 11:30:27 -0400, Carmel wrote:
> >> > >
> >> > > > My question is what changed? It worked before updating "libnotif=
y". Is
> >> > > > "libnotify" the culprit or "GNUTLS" or something else and why di=
dn't
> >> > > > anyone catch this problem sooner?
> >> > >
> >> > > The chain of dependencies during the libnotify update prompted the
> >> > > upgrade of cups. =9AThe latter's OpenSSL interfaces are explicitly
> >> > > thread-safe, which GNU TLS is not.
> >> > >
> >> > > > There appears to be a lot of material released lately that is ei=
ther
> >> > > > broken or requiring a considerable amount of manual intervention.
> >> > > > Perhaps a moratorium (port freeze) should be considered until al=
l of
> >> > > > the outstanding problems have been corrected.
> >> > >
> >> > > We are sorry for the inconvenience which is surely frustrating, but
> >> > > freezing the tree because of this does not seem appropriate.
> >> >
> >> > Might be, completely ignoring the option 'use gnutls' in cups ports,
> >> > until it can be made working, will change everybody life to be easie=
r.
> >>
> >> What "might be"?
> >>
> >> As already noted, the GNUTLS option now defaults to OFF and users are
> >> warned (via the BROKEN construct) if it is selected.
> >
> > Apparently, this have to be written explicitely. Users, who upgrade
> > their ports, are not presented with the configuration dialog. Using
> > automated tool like portupgrade, all you get is a list of the failed
> > ports. After that, user needs to start investigation, spending his
> > own time and possibly time of the people on list.
> >
> > Ignoring or removing the option makes the ports upgrade without user
> > intervention.
> >
> > I am willing to spend some more time describing unobvious points of
> > this consideration.
>=20
> Alright, how about this?
>=20
> RCS file: /home/pcvs/ports/print/cups-base/Makefile,v
> retrieving revision 1.162
> diff -u -r1.162 Makefile
> --- Makefile 25 Aug 2011 14:54:39 -0000 1.162
> +++ Makefile 28 Aug 2011 18:40:24 -0000
> @@ -124,7 +124,7 @@
> .endif
>=20
> .if defined(WITH_GNUTLS)
> -BROKEN=3D gnutls does not support threads yet
> +BROKEN=3D gnutls does not support threads yet; disable the GNUTLS
> option to build
> CONFIGURE_ARGS+=3D --disable-openssl --enable-gnutls
> CONFIGURE_ENV+=3D PKGCONFIG=3D"${LOCALBASE}/bin/pkg-config"
> LIB_DEPENDS+=3D gnutls-openssl.27:${PORTSDIR}/security/gnutls
>=20
> Dirk, do you have any objections if I were to commit that?
It still requires manual intervention into the process which can be automat=
ed.
--Hwc0ilm0gE8kvSWy
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)
iEYEARECAAYFAk5ajb0ACgkQC3+MBN1Mb4hfCwCg0rlis1wktFbBOChcr+Iwy5/U
qusAmweBxxai/LPllx0nIGhRQNk29JBv
=MK2z
-----END PGP SIGNATURE-----
--Hwc0ilm0gE8kvSWy--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110828184933.GY17489>