bugGNU tar - Bugs: bug #55111, GNU tar cannot properly parse...


bug #55111: GNU tar cannot properly parse .gitignore entries containing a leading slash

Submitter:  None
Submitted:  Tue 27 Nov 2018 09:17:24 AM UTC
Category:  None Severity:  3 - Normal
Item Group:  None Status:  In Progress
Privacy:  Public Assigned to:  gray
Open/Closed:  Open
* Mandatory Fields

Add a New Comment Rich Markup

Fri 03 May 2019 10:04:33 AM UTC, comment #1: 

Thanks for reporting. This is related to bug #54408. I'll let you know when it is fixed.

Sergey Poznyakoff <gray>
Group administrator
Tue 27 Nov 2018 09:17:24 AM UTC, original submission:  

I first ran into this when discovering that --exclude-vcs-ignores would probably help out my backup scripts a whole lot, considering  each thing I build has gigabytes of build artefacts. Unfortunately, it didn't seem to work all the time. I eventually narrowed it down to the fact that Rust by default adds a `/target/` entry to .gitignore instead of just `target/`. The latter works fine, while the former is incorrectly recognised by GNU tar.

I think fixing this would just mean stripping leading slashes from .gitignore files whenever tar reads them.



(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by gray (Posted a comment)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.


    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-05-03 gray StatusNone In Progress
        Assigned toNone gray

    Back to the top

    Powered by Savane 3.13-599c.
    Corresponding source code