Hi Kaleb et al.,
Do you have any feel for whether or not getting the Wheezy package working will
be a quick fix? I was planning deploying the client to a number of our Wheezy
servers, but if it?s going to be a while I might look at setting up NFS-Ganesha
instead.
Thanks!
Ben
NPR | Benjamin Wilson | Sr. Systems Administrator | 202-513-4454 | bwilson at
npr.org
On 1/21/16, 7:06 AM, "gluster-users-bounces at gluster.org on behalf of
Ronny Adsetts" <gluster-users-bounces at gluster.org on behalf of
ronny.adsetts at amazinginternet.com> wrote:
>Kaleb Keithley wrote on 21/01/2016 11:51:
>>> From: "Atin Mukherjee" <amukherj at redhat.com>
>>>>
>>>> Wheezy has an old version of liburcu [1]. Gluster requires
>>>> at-least v0.7. I don't know how Wheezy packages even got
built
>>>> without the required version of liburcu being present.
>>> Probably Kaleb might be knowing it?
>>>>
>>>> [1]
>>>>
https://packages.debian.org/search?searchon=names&keywords=urcu
>>
>> Good question. The debian package build runs configure, so the build
>> _should_ have failed.
>>
>> We hadn't built 3.7.x up until 3.7.6 because of other dependencies
>> that were finally resolved in 3.7.6.
>>
>> Will have to investigate why the build did not fail on the incorrect
>> urcu.
>>
>> I'll pull the wheezy bits from d.g.o.
>
>Hi Kaleb,
>
>Is there a chance that the builds could be fixed to work with Wheezy?
>
>Thanks all for your quick responses.
>
>Ronny
>--
>Ronny Adsetts
>Technical Director
>Amazing Internet Ltd, London
>t: +44 20 8977 8943
>w: www.amazinginternet.com
>
>Registered office: 85 Waldegrave Park, Twickenham, TW1 4TJ
>Registered in England. Company No. 4042957
>
>