From owner-freebsd-current@FreeBSD.ORG Wed Jul 24 19:07:27 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 63BC37F4; Wed, 24 Jul 2013 19:07:27 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C38632707; Wed, 24 Jul 2013 19:07:26 +0000 (UTC) Received: by mail-wg0-f41.google.com with SMTP id n11so807307wgh.2 for ; Wed, 24 Jul 2013 12:07:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=rOol6iXb2x2ZUcxTaZK2JjkKdqvpQC314K+sjOwvz88=; b=AC3duED94Z0Aq+VXzBs/efZgc5I1+jslCs/w/IpVHqkrGRTdFRTsfmrs6K0qsfq5r5 cjOkgb6BCliI42s5AyUijnOuMNQvK5Zrh9hq8tPyT3QBsvmcXwyDK7GABEiZV4WpyERq HN10rekVRB7LQ54UZ8+QHiEpgWK8rA3GRi/8ThLet2wSaQzHEk42RkGxyhFV7qf05wcK 8G/FulBLcmzVaS6iPxw1i42QoygBGWSxTzYv9NuJ5hQS3+Gu9GZmZ13dVokeJiSIB1Q6 GUbkK0l7YwcY6m4srKUsQzFrGH733ptHEWF0gHnIrjXBVIxd+TzMyokC20OrWbpCdueP LZMA== X-Received: by 10.180.126.10 with SMTP id mu10mr3656421wib.64.1374692844041; Wed, 24 Jul 2013 12:07:24 -0700 (PDT) Received: from ithaqua.etoilebsd.net (ithaqua.etoilebsd.net. [37.59.37.188]) by mx.google.com with ESMTPSA id r8sm7399654wiz.5.2013.07.24.12.07.23 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 24 Jul 2013 12:07:23 -0700 (PDT) Sender: Baptiste Daroussin Date: Wed, 24 Jul 2013 21:07:21 +0200 From: Baptiste Daroussin To: Pedro Giffuni Subject: Re: poudriere problems with fuse? Message-ID: <20130724190721.GB41432@ithaqua.etoilebsd.net> References: <20130724183435.GH63694@ithaqua.etoilebsd.net> <51F02319.40202@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Yylu36WmvOXNoKYn" Content-Disposition: inline In-Reply-To: <51F02319.40202@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Adrian Chadd , freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jul 2013 19:07:27 -0000 --Yylu36WmvOXNoKYn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 24, 2013 at 01:55:21PM -0500, Pedro Giffuni wrote: > On 24.07.2013 13:34, Baptiste Daroussin wrote: > > On Wed, Jul 24, 2013 at 11:22:57AM -0700, Adrian Chadd wrote: > >> Hi Pedro, > >> > >> Bapt tells me that there are FUSE issues in the most recent -HEAD and > >> it's stopping poudriere from running. > > Nah poudriere does not use yet fuse :) > >> What's the story here? > >> > > I was about to mail you :) > > > > It is broken since r248084 apparently the update on the fuse_kernel.h y= ou did is > > not in sync with fusefs-libs, resulting in no filesystem to properly wo= rk. > > > > Do you have any insight on the reason of the changes? and I should look= at? >=20 > The change came from upstream. Does it help to revert it all? >=20 > Another option could be to teach the port to use the kernel header > but it doesn't look like that would work either :(. Yes reverting will help r248084 is the last known working revision. Updating the header should be done with modification on the code itself to implement the missing bits. has some things has changed, I have seen some interesting things https://github.com/bfleischer/fuse-macosx I might probab= ly have a look at it later. Thank you for fast reply, regards, Bapt --Yylu36WmvOXNoKYn Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlHwJekACgkQ8kTtMUmk6ExXgwCfVEdnxTUFIwBNawyauzJzk6LF u7gAoJqOsEW4/g3ykUkBz2/sdDV2t9dk =yKje -----END PGP SIGNATURE----- --Yylu36WmvOXNoKYn--