On Saturday 21 October 2006 21:17, Kris Kennaway wrote:
> On Sat, Oct 21, 2006 at 09:12:10PM +0300, Andy Fawcett wrote:
> > On Saturday 21 October 2006 21:07, Kris Kennaway wrote:
> > > On Sat, Oct 21, 2006 at 08:25:13PM +0300, Andy Fawcett wrote:
> > > > On Saturday 21 October 2006 19:40, Kris Kennaway wrote:
> > > > > On Sat, Oct 21, 2006 at 07:03:01PM +0300, Andy Fawcett wrote:
> > > > > > Hi Kris,
> > > > > >
> > > > > > This one isn't one of ours, it's az@'s
> > > > >
> > > > > Right, it was an example of one of the dozens of similar
> > > > > errors. See pointyhat for the full list.
> > > >
> > > > I'm there...
> > > >
> > > > > > But I'll take a look at the plist problems on kde@ ports
> > > > > > and see if I can work out what is wrong.
> > > > >
> > > > > Thanks - though I'd prefer a complete fix based on completing
> > > > > the commit that broke them all the other day. Drive-bys
> > > > > aren't supposed to happen during a ports freeze :-)
> > > >
> > > > Looking at portsmon:
> > > >
> > > > devel/tinyq: I suspect some 7-CURRENT fallout. I don't have a 7
> > > > box at the moment so I can't look at it. Nothing depends on
> > > > this port, and I'd even forgotten we had it.
> > > >
> > > > x11/kdelibs3-nocups: 6/i386: Oct 19th 07:59 UTC.
> > > > -> plist patch attached (untested, but matches the one made to
> > > > the master port and looks right to me), lofi missed this in his
> > > > commit of 2006-10-18 10:20:58 UTC
> > > >
> > > >
> > > > Other ones listed on that page are on ports that have been
> > > > since updated, either to newer versions or to fix these
> > > > problems.
> > > >
> > > > Let me know if I missed something here.
> > >
> > > You missed that it's the i386-6 build that is the one in question
> > > :)
> >
> > Eh?
> >
> > tinyq is showing a problem on 7-C only.
>
> Yep, so probably irrelevant to 6.2. Note that the previous 7.x build
> was with gcc 4.1.
Right. I'm a bit slow today, been on call all week...
> > kdelibs-nocups was fixed for all branches/architectures with the
> > patch I provided.
> >
> > Other problems listed against kde@ are already obsolete, as far as
> > I can make out.
>
> OK, so who is going to take responsibility for the ~50 other failures
> that began after the recent commit?
Can you point to them? Since they're not listed against kde@, I can't
guess which of the other 15000+ ports they are against? If they're
caused by lofi's last change I'll do my best to find solutions.
A.
--
Andy Fawcett | [EMAIL PROTECTED]
| [EMAIL PROTECTED]
"In an open world without walls and fences, | [EMAIL PROTECTED]
we wouldn't need Windows and Gates." -- anon | [EMAIL PROTECTED]
_______________________________________________
kde-freebsd mailing list
[email protected]
http://kf.liquidneon.com/mailman/listinfo/kde-freebsd
