This bug was fixed in the package libtar - 1.2.20-3ubuntu0.1
---
libtar (1.2.20-3ubuntu0.1) trusty-proposed; urgency=high
[ Magnus Holmgren ]
* no_maxpathlen.patch: Half of the part of the patch modifying
compat/dirname.c was missing, causing libtar's dirname to always
ret
I tested the new package for the amd64 arch and it fixes the bug for me.
Thanks Brian, Collin.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to trusty-backports.
Matc
** Branch linked: lp:ubuntu/trusty-proposed/libtar
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to trusty-backports.
Matching subscriptions: ubuntu-backporters
https://bugs.launchpad.net/bugs/1315742
Title:
Segmentation fault on tar_
Hello TimJ, or anyone else affected,
Accepted libtar into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/libtar/1.2.20-3ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wik
I've uploaded the Utopic version of libtar to the Trusty proposed queue
for review by an SRU team member.
** Changed in: libtar (Ubuntu Trusty)
Status: Triaged => In Progress
** Changed in: libtar (Ubuntu Trusty)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Description ch
We successfully aplied the following patch to generate an own version
(1.2.20-4~osrf1) that fixes the problem.
** Patch added: "Backport of libtar_1.2.20-4 to trusty"
https://bugs.launchpad.net/ubuntu/+source/libtar/+bug/1315742/+attachment/4135049/+files/libtar-4_backport.debdiff
--
You rec
Thanks Brian, I've wrote a small testing case that should segfault with
current libtar 1.2.20-3 but should work with the patch 1.2.20-4
- Compile: gcc foo.c -ltar -o foo
- Run ./foo
It will uncompress the contents in the /tmp directory.
Let me know if you need anything else.
** Attachment add
As a part of the Stable Release Update process
(https://wiki.ubuntu.com/StableReleaseUpdates#Procedure) this bug will
need a test case so we can be verify that the bug is in fact fixed by
the new version of the package. Could someone please provide a test
case?
--
You received this bug notificat
** Also affects: libtar (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: libtar (Ubuntu Trusty)
Status: New => Triaged
** Changed in: libtar (Ubuntu Trusty)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
I've created a new bug to handle the process of backporting the fix:
https://bugs.launchpad.net/ubuntu/+source/libtar/+bug/1319809
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to trusty-backports.
Matching subscriptions: ubuntu-backport
As the current released version is crashing it does suggest it warrants
a release into the regular repos.
What's the correct way to reopen this for trusty since it looks like all
Affected elements are closed at the moment?
--
You received this bug notification because you are a member of Ubuntu
Seems like a good candidate for a stable release update, not for
backports.
** Changed in: trusty-backports
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to trusty-backports.
Matching subscriptions: ubuntu-
** Also affects: trusty-backports
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to trusty-backports.
Matching subscriptions: ubuntu-backporters
https://bugs.launchpad.net/bugs/1315742
Title:
13 matches
Mail list logo
