| Summary: | tar: New version is killed by kernel when using --no-overwrite-dir option | ||
|---|---|---|---|
| Product: | IPFire | Reporter: | Michael Tremer <michael.tremer> |
| Component: | --- | Assignee: | Matthias Fischer <matthias.fischer> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | Crash | ||
| Priority: | Will affect all users | CC: | arne.fitzenreiter |
| Version: | 2 | ||
| Hardware: | unspecified | ||
| OS: | Unspecified | ||
| Attachments: | Trace of crash | ||
OUCH! I tested 1.31, but not with Pakfire... Duh! Nevertheless, I tried to file a bug report and it worked. => http://savannah.gnu.org/bugs/index.php?55413 Best, Matthias Ah cool. Keep us updated when they respond please... Hi, I got a really fast reaction. See: https://savannah.gnu.org/bugs/?55413 Devel is running... Best, Matthias Hi, Patch was sent and tested, see: https://patchwork.ipfire.org/patch/2031/ Please confirm... Best, Matthias Merged. We will see... Shipped with Core 127. Best, Matthias |
Created attachment 650 [details] Trace of crash When pakfire installs a package, we don't overwrite any existing directories. To achieve that we unpack all tar archives with --no-overwrite-dir. That doesn't work any more. tar just crashes. I will revert the update for now. We probably need to file a bug report upstream and wait for a new release. See the attached trace. Works fine without the option.