Bug#873615: Fails to detect changes in tarballs that share the same top-level directory

2019-09-04 Thread Carlos Maddela
On 2/9/19 1:21 am, Axel Beckert wrote: > > So I can't really reproduce this. > > Any idea what I might do different than you? Did you use any > additional commandline options when you ran into this? Without the -m option, tardiff only details the changes to the source tree (i.e. new or remove

Bug#873615: Fails to detect changes in tarballs that share the same top-level directory

2019-09-01 Thread Axel Beckert
Control: tag -1 + unreproducible moreinfo Hi Carlos, sorry for the late reply. Seems to have slipped through the cracks. Carlos Maddela wrote: > Perhaps I'm not using this utility in the way it was intended to be > used, but it falsely reports tarballs to be identical if the top-level > director

Bug#873615: Fails to detect changes in tarballs that share the same top-level directory

2017-08-29 Thread Carlos Maddela
Package: tardiff Version: 0.1-5 Followup-For: Bug #873615 Amended patch with correct indentation. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4

Bug#873615: Fails to detect changes in tarballs that share the same top-level directory

2017-08-29 Thread Carlos Maddela
Package: tardiff Version: 0.1-5 Severity: normal Tags: patch Hi, Perhaps I'm not using this utility in the way it was intended to be used, but it falsely reports tarballs to be identical if the top-level directories are identical. This is because the tarballs get extracted to the same location, a