[Bug 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories

2019-09-03 Thread Launchpad Bug Tracker
This bug was fixed in the package libarchive - 3.2.2-3.1ubuntu0.4 --- libarchive (3.2.2-3.1ubuntu0.4) bionic; urgency=medium * debian/patches/git_zip_directories.patch: - backport a fix for an issue where files are created instead of directories (lp: #1830629) --

[Bug 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories

2019-08-06 Thread Sebastien Bacher
** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830629 Title: Errors when

[Bug 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories

2019-08-06 Thread Alejandro Claro
Good morning Murray, we performed some test and everything looks fine. Thank you very much. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830629 Title: Errors when extracting ZIP files. It can

[Bug 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories

2019-08-05 Thread Alejandro Claro
Thank you Brian, We are going to be testing it during this week. I will let you know the results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830629 Title: Errors when extracting ZIP files. It

[Bug 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories

2019-07-30 Thread Brian Murray
Hello Alejandro, or anyone else affected, Accepted libarchive into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libarchive/3.2.2-3.1ubuntu0.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package.

[Bug 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories

2019-06-28 Thread Sebastien Bacher
Thank you for your bug report, marking the bug as fixed since the issue is resolved in the current version. We are doing a SRU backport to Bionic as well (the corresponding line will be added to the report) ** Changed in: libarchive (Ubuntu) Importance: Undecided => High ** Changed in:

[Bug 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories

2019-06-04 Thread Alejandro Claro
One important note here, The defect is only present in version 3.2.2 (Bionic official version now). Previous and next version do work properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830629

[Bug 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories

2019-06-04 Thread Alejandro Claro
HI Sebastien, Sure. Here is a zip file that it's very easy to use to reproduce the defect. The defect s not in the bsdtar, it's in libarchive. However, since bsdtar depends on libarchive, this can be used to demonstrate the problem as someone reports in the GitHub issue report:

[Bug 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories

2019-05-30 Thread Sebastien Bacher
The commit seems reasonable for a SRU. Could you maybe add an example/testcase to the bug that could be used for the SRU process? (we need to be able to verify the problem and the solution) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories

2019-05-30 Thread Alex Murray
Thanks for reporting this issue - this would appear to have potential security implications, however as it is already public I see no reason to keep this private - if a CVE were to be assigned then this could be fixed via a security update by the security team, otherwise this would be fixed via