On Wed, Jan 14, 2015 at 12:02:05PM +, Finucane, Stephen wrote:
> > On 01/14/2015 01:15 PM, Finucane, Stephen wrote:
> > >> Thanks for the followup. I hope that the Automake maintainers consider
> > >> the issue.
> > >
> > > No reply after > 1 week. How could we proceed here, as I'm still unabl
On 01/14/2015 03:53 PM, Finucane, Stephen wrote:
I dont remember the automake version I first encountered that, it was on
another project which had already been using ustar for several years but
then at some point during 2013 it started whining about large UIDs.
Assuming said project was open s
> I dont remember the automake version I first encountered that, it was on
> another project which had already been using ustar for several years but
> then at some point during 2013 it started whining about large UIDs.
Assuming said project was open source, how did they go about achieving this:
On 01/14/2015 02:02 PM, Finucane, Stephen wrote:
On 01/14/2015 01:15 PM, Finucane, Stephen wrote:
Thanks for the followup. I hope that the Automake maintainers consider
the issue.
No reply after > 1 week. How could we proceed here, as I'm still unable
to run 'make dist' (without manual patch
> On 01/14/2015 01:15 PM, Finucane, Stephen wrote:
> >> Thanks for the followup. I hope that the Automake maintainers consider
> >> the issue.
> >
> > No reply after > 1 week. How could we proceed here, as I'm still unable
> to run 'make dist' (without manual patching) in the interim? Based on my
On 01/14/2015 01:15 PM, Finucane, Stephen wrote:
Thanks for the followup. I hope that the Automake maintainers consider
the issue.
No reply after > 1 week. How could we proceed here, as I'm still unable to run
'make dist' (without manual patching) in the interim? Based on my conversation
wit
> Thanks for the followup. I hope that the Automake maintainers consider
> the issue.
No reply after > 1 week. How could we proceed here, as I'm still unable to run
'make dist' (without manual patching) in the interim? Based on my conversation
with Eric, it looks like this is something that cou
On Tue, Jan 06, 2015 at 09:14:51AM +, Finucane, Stephen wrote:
> > On Mon, Jan 05, 2015 at 08:57:48AM +, Finucane, Stephen wrote:
> > > > On Fri, Dec 19, 2014 at 10:19:10AM +, Stephen Finucane wrote:
> > > > > Automake defaults to the 'v7' legacy tar format in GNU tar, through
> > > > >
> On Mon, Jan 05, 2015 at 08:57:48AM +, Finucane, Stephen wrote:
> > > On Fri, Dec 19, 2014 at 10:19:10AM +, Stephen Finucane wrote:
> > > > Automake defaults to the 'v7' legacy tar format in GNU tar, through
> > > > passing of the '-o' parameter to GNU tar. Enabling this option
> results
>
On Mon, Jan 05, 2015 at 08:57:48AM +, Finucane, Stephen wrote:
> > On Fri, Dec 19, 2014 at 10:19:10AM +, Stephen Finucane wrote:
> > > Automake defaults to the 'v7' legacy tar format in GNU tar, through
> > > passing of the '-o' parameter to GNU tar. Enabling this option results
> > > in er
> On Fri, Dec 19, 2014 at 10:19:10AM +, Stephen Finucane wrote:
> > Automake defaults to the 'v7' legacy tar format in GNU tar, through
> > passing of the '-o' parameter to GNU tar. Enabling this option results
> > in errors for users with 32 bit UIDs:
> >
> > $ make dist
> > ...
> >
On Fri, Dec 19, 2014 at 10:19:10AM +, Stephen Finucane wrote:
> Automake defaults to the 'v7' legacy tar format in GNU tar, through
> passing of the '-o' parameter to GNU tar. Enabling this option results
> in errors for users with 32 bit UIDs:
>
> $ make dist
> ...
> tardir=openvs
12 matches
Mail list logo
