>
> This works with tar 1.13.25
>
> tar cvjf test.tbz2 --exclude=
Hmm, I agree that the behavior has changed, but am not yet sure
it is a bug. I'll ask upstream if the change in behavior was intentional,
or whether it should be construed as a bug.
>
> In 1.15.1 it mucks up parsing of --exclu
On Thu, 27 Oct 2005, Alan Hourihane wrote:
>
> Moving --exclude= to this...
>
> tar --exclude= -cvjf test.tbz2
>
> makes it work.
I remember...
I hit those some time ago too. tar is now more strict where options
can be put on the command line.
bye
ago
--
[EMAIL PROTECTED]
http:
On Thu, 2005-10-27 at 06:27 -0600, Eric Blake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> According to Alan Hourihane on 10/27/2005 3:30 AM:
> > Now, having upgraded everything to the latest releases things started to
> > go wrong with the packaging scripts.
> >
> > tar started t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Alan Hourihane on 10/27/2005 3:30 AM:
> Now, having upgraded everything to the latest releases things started to
> go wrong with the packaging scripts.
>
> tar started to bleat with "Cannot stat: No such file or directory" for
> lots of d
This is probably just for Eric Blake, but I thought I'd let others know.
I'm currently packaging a new xorg release for cygwin. I only ever build
directly on my WinXP box for this too.
Now, having upgraded everything to the latest releases things started to
go wrong with the packaging scripts.
t
5 matches
Mail list logo