Re: upcoming libtool rebase (2.4.2 ~> 2.4.3)

2015-01-09 Thread Pavel Raiskup
On Wednesday 29 of October 2014 15:20:31 Pavel Raiskup wrote: > Libtool upstream was able to cut the new release! > > I'll rebase the Rawhide package probably by the end of the next week or > so, if there are no objections. > > Upstream maintainer calls this update fearless :) and that it needs a

Re: upcoming libtool rebase (2.4.2 ~> 2.4.3)

2014-10-30 Thread Pavel Raiskup
On Wednesday 29 of October 2014 15:51:12 Kalev Lember wrote: > On 10/29/2014 03:20 PM, Pavel Raiskup wrote: > > Libtool upstream was able to cut the new release! > > Thanks Pavel for dealing with this! > > While you are at this, any chance you could try convincing upstream to > add /usr/lib64 to

Re: upcoming libtool rebase (2.4.2 ~> 2.4.3)

2014-10-30 Thread Pavel Raiskup
On Wednesday 29 of October 2014 15:03:32 Daniel P. Berrange wrote: > On Wed, Oct 29, 2014 at 03:20:31PM +0100, Pavel Raiskup wrote: > > Libtool upstream was able to cut the new release! > > > > I'll rebase the Rawhide package probably by the end of the next week or > > so, if there are no objectio

Re: upcoming libtool rebase (2.4.2 ~> 2.4.3)

2014-10-29 Thread Daniel P. Berrange
On Wed, Oct 29, 2014 at 03:20:31PM +0100, Pavel Raiskup wrote: > Libtool upstream was able to cut the new release! > > I'll rebase the Rawhide package probably by the end of the next week or > so, if there are no objections. > > Upstream maintainer calls this update fearless :) and that it needs

Re: upcoming libtool rebase (2.4.2 ~> 2.4.3)

2014-10-29 Thread Kalev Lember
On 10/29/2014 03:20 PM, Pavel Raiskup wrote: > Libtool upstream was able to cut the new release! Thanks Pavel for dealing with this! While you are at this, any chance you could try convincing upstream to add /usr/lib64 to the list of standard libdirs, to avoid madness like https://fedoraproject.o

upcoming libtool rebase (2.4.2 ~> 2.4.3)

2014-10-29 Thread Pavel Raiskup
Libtool upstream was able to cut the new release! I'll rebase the Rawhide package probably by the end of the next week or so, if there are no objections. Upstream maintainer calls this update fearless :) and that it needs a bit of luck [1] (asking for possible downstream cooperation); however af