> Can you reproduce the problem with:
> $ cat tango-9.3.3-rc2.tar | tar --delete > \
> tango-9.3.3-rc2-excluded.tar
> ?
here
:~/Debian/tango$ cat tango-9.3.3-rc2.tar | tar --delete
tango-9.3.3/lib/java/RestServer-1.14.jar > tango-9.3.3-rc2-excluded.tar
tar: tango-9.3.3/lib/java/RestServer-1.14
> Please confirm that
> > LANG=C tar --delete $(tar tf tango-9.3.3-rc2.tar | grep "lib/java/R.*jar")
> > < tango-9.3.3-rc2.tar > tango.tar
> is inspired by `mk-origtargz`.
not at all, I found this in #869087, which is a tar bug with --delete.
It is not clear to me what is the cmd executed by mk-
I tryed to reproduce the issue like this
LANG=C tar --delete $(tar tf tango-9.3.3-rc2.tar | grep "lib/java/R.*jar") <
tango-9.3.3-rc2.tar > tango.tar
tar: tango-9.3.3/lib/java/RestServer-1.14.jar: Not found in archive
tar: Exiting with failure status due to previous errors
Is it the right way to
> mk-origtargz just calls tar --delete < file > newfile and as you can
> easily check this indeed gives the same error message.
the listed files are the right files as extracted by tar from the upstream
tar.gz, so
this is an issue with tar ?
Is it possible to display the exact tar command line
looking at the directroy, I find this
drwxr-xr-x 11 picca picca 4096 août 20 17:23 tango-9.3.3
-rw-r--r-- 1 picca picca 282982400 août 25 08:37
tango_9.3.3~rc2+dfsg1.orig.tar
-rw-r--r-- 1 picca picca 232776497 août 25 08:36 tango-9.3.3-rc2.tar.gz
what is strange it that the extracted di
Hello
> Found jar deletion instruction
> at https://salsa.debian.org/science-team/tango/blob/master/debian/copyright#L5
yes I use
Files-Excluded: lib/java/*.jar
from DEP-5 (it was find until now)
> I assume that upstream has stopped shipping jars in there .tar.gz
> If so, then it is a good thin
6 matches
Mail list logo
