Re: Releasability of the kFreeBSD ports
On 05/08/10 at 22:41 +0200, Peter Palfrader wrote:
> On Wed, 04 Aug 2010, Aurelien Jarno wrote:
> > > So, what do you think is still missing? What would we need to communicate
> > > as a disclaimer to the users if releasing kFreeBSD in this state?
> > From the server point of view, I think we reached something close to
> > other debian-ports, with even some added features like ZFS. On the other
> > hand I have to agree that on the desktop point of view, there are still
> > problems, which may break the expectations users have from a stable
> > release. The desktop is usable though.
> With my DSA hat on I have to say that I'm not entirely happy with what
> we have so far.
> The biggest pain for us currently is that puppet just does not work
> reliably on kfreebsd (both i386 and amd64). This may be a ruby bug, but
> it's still really, really annoying.
Which version of ruby are you using? Is it >= 126.96.36.199-4 ?
ruby1.8 (188.8.131.52-4) unstable; urgency=low
[ Lucas Nussbaum ]
* Update debian/patches/100312_timeout-fix.dpatch after discussion with
Petr Salinger. Treat FreeBSD the same as Linux. Closes: #580464
ruby1.8 (184.108.40.206-2) unstable; urgency=low
* Add 100312_timeout-fix.dpatch: Backport upstream change to fix
problem with threads and timeouts. Closes: #539987
(That bug was triggered by puppet)