Rev 33 | Rev 38 | Go to most recent revision | Show entire file | Ignore whitespace | Details | Blame | Last modification | View Log | RSS feed
| Rev 33 | Rev 36 | ||
|---|---|---|---|
| Line -... | Line 1... | ||
| - | 1 | libtar (1.2.20-4) unstable; urgency=high |
|
| - | 2 | ||
| - | 3 | * no_maxpathlen.patch: Half of the part of the patch modifying |
|
| - | 4 | compat/dirname.c was missing, causing libtar's dirname to always |
|
| - | 5 | return NULL (except in special circumstances). Actually make it work |
|
| - | 6 | (Closes: #745352). (The reason that libtar doesn't use libc's |
|
| - | 7 | dirname() and basename() on some or most platforms is that the code |
|
| - | 8 | doesn't work with destructive versions of these functions). |
|
| - | 9 | ||
| - | 10 | -- Magnus Holmgren <holmgren@debian.org> Sat, 03 May 2014 20:39:02 +0200 |
|
| - | 11 | ||
| 1 | libtar (1.2.20-3) unstable; urgency=low |
12 | libtar (1.2.20-3) unstable; urgency=low |
| 2 | 13 | ||
| 3 | * no_maxpathlen.patch: Fix two grave bugs in the patch. First, |
14 | * no_maxpathlen.patch: Fix two grave bugs in the patch. First, |
| 4 | th_get_pathname would only allocate as much memory as was needed for |
15 | th_get_pathname would only allocate as much memory as was needed for |
| 5 | the first filename encountered, causing heap corruption when/if |
16 | the first filename encountered, causing heap corruption when/if |