Control: tag -1 + patch
On Mon, May 14, 2018 at 11:07:50AM -0700, Bdale Garbee wrote:
> Paul Eggert writes:
>
> > On 05/14/2018 07:56 AM, Antonio Terceiro wrote:
> >> I still need to study the > code a bit further to try to come up with a
> >> better suggestion.
> > Sorry, the only suggestion
Paul Eggert writes:
> On 05/14/2018 07:56 AM, Antonio Terceiro wrote:
>> I still need to study the > code a bit further to try to come up with a
>> better suggestion.
> Sorry, the only suggestion I can make is that you should just use the
> new GNU tar. The old one was obviously busted and it
On 05/14/2018 07:56 AM, Antonio Terceiro wrote:
I still need to study the > code a bit further to try to come up with a better
suggestion.
Sorry, the only suggestion I can make is that you should just use the
new GNU tar. The old one was obviously busted and it generated busted
tarballs.
Hello,
Paul: I hope you don't mind being involved in this. I would appreciate
any input that you are able to provide. Context is Debian bug #897653
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897653), but all the
important bits are already quoted below.
the general idea of pristine-tar is
Package: tar
Version: 1.30+dfsg-1
Severity: grave
Justification: causes non-serious data loss
Hi,
After tar 1.30 arrived in unstabled, pristine-tar can no longer
reproduce tarballs that it previously could. For example I just hit this
with bundler:
$ debcheckout -a bundler
declared git repositor
5 matches
Mail list logo
