Date: Sun, 24 Jun 2012 20:45:56 +0200 From: Koop Mast <kwm@rainbow-runner.nl> To: Mark Linimon <linimon@lonesome.com> Cc: kwm@FreeBSD.org, freebsd-ports@freebsd.org Subject: Re: FreeBSD ports which are currently scheduled for deletion Message-ID: <1340563556.1577.33.camel@crashalot.rainbow-runner.nl> In-Reply-To: <20120622025904.GC2608@lonesome.com> References: <201206210829.q5L8Tn8t084934@portsmonj.FreeBSD.org> <4FE30487.3040002@freebsd.org> <20120622025904.GC2608@lonesome.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2012-06-21 at 21:59 -0500, Mark Linimon wrote: > On Thu, Jun 21, 2012 at 01:24:55PM +0200, Stefan Esser wrote: > > Am 21.06.2012 10:29, schrieb linimon@FreeBSD.org: > > > portname: audio/gstreamer-plugins-flite > > > description: Gstreamer flite run-time speech synthesis engine > > > plugin > > > maintainer: multimedia@FreeBSD.org > > > status: BROKEN > > > deprecated because: BROKEN for more than 6 month > > > expiration date: 2012-05-10 > > > build errors: none. > > > overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gstreamer-plugins-flite > > > > I just tried building this port and it built and packaged without any > > problems. Is the compile log still available that lead to this port > > being marked broken? > > There's not a quick way to do it. See the following wiki page for > the how-to: > > http://wiki.freebsd.org/WhenDidThatPortBreak > > But by walking through this, I did not find a last build log. However, > the CVSweb entry shows the following: > > http://www.freebsd.org/cgi/cvsweb.cgi/ports/audio/gstreamer-plugins-flite/Makefile.diff?r1=1.1;r2=1.2;f=h > > Update Gstreamer (core) to 0.10.33 > Update Gstreamer-plugins(-base) to 0.10.33 > Update Gstreamer-plugins-good to 0.10.29 > Update Gstreamer-plugins-bad to 0.10.22 > Update Gstreamer-plugins-ugly to 0.10.18 > > So it doesn't really say. > > kwm, you were the committer, do you remember what the issue was? > > mcl Thanks for bringing this to my attention, I complete forgot about this issue. This is/was a runtime issue, unresolved symbols. I recently picked up work again on a Gstreamer update which will contain a workaround to fix this problem. But since I forgot about it the flite plugin would still be marked broken after the Gstreamer update. -Koop
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1340563556.1577.33.camel>