hello Geert, Geert Stappers <stapp...@stappers.nl> writes: > On Sun, Aug 25, 2019 at 01:25:22PM +0000, PICCA Frederic-Emmanuel wrote: >> 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 use --delete ? > > > Added "mk-origtargz" to the Subject > > 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`. > > Karma bonus points for providing context.
https://salsa.debian.org/debian/devscripts/blob/master/lib/Devscripts/MkOrigtargz.pm#L262 The history is that in 2015, we discovered that when mk-origtargz runs tar's in-place deletion, it also deletes other files (random misbehavior which upstream does not intend to fix). So we replaced it with piping through tar --delete to an anonymous file (out-of-place, see source above): devscripts (2.15.9) unstable; urgency=medium [ Joachim Breitner ] * mk-origtargz: + Work around tar --delete not working unless piping. This should make the support for Excluded-Files more reliable. Thanks to Felix Natter for identifying the problem and solution. [...] Cheers and Best Regards, -- Felix Natter debian/rules!
