Bug 164573

Summary: tla seg faults creating repo
Product: [Fedora] Fedora Reporter: James Antill <james.antill>
Component: tlaAssignee: Shahms E. King <shahms>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: extras-qa, scop
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 1.3.3-3.fc4 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-16 17:07:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 158655    
Bug Blocks:    

Description James Antill 2005-07-28 20:13:10 UTC
Description of problem:
 tla will die via. SEGV/glibc-double-free when trying to create a pristine tree Ie.

tla get james/vstr--main--1

...but I found it when it complained about my {arch}/++prinstine-tree/ and I
deleted that and it couldn't create a new one

Version-Release number of selected component (if applicable):
FC4 GA
Version: 1.3.1
Release: 4.fix.1


How reproducible:
always

Additional info:
 I'm now using tla(0:1.3.2-5).i386 from FC3, and that works fine.

Comment 1 Shahms E. King 2005-07-28 20:53:49 UTC
Yes, this problem and many more are fixed in 1.3.2/1.3.3.  Sadly, tla doesn't
pass make check on PPC (meaning the build fails) and Extras won't push updates
if the build fails on any of the supported architectures (i386, x86_64, PPC).

Upstream has been less than responsive to this problem as most of the tla
developers are focused on "revc" (GNU Arch 2.0) or baz (bazaar).  I have not had
time to track down and patch the PPC problems myself so tla sits without
bugfixes for the platforms that work ...

I'm glad you've managed to work around the problem; hopefully I'll be able to
grab my friends PowerBook and investigate the PPC build problems which should
solve this problem as well.

Comment 2 Ville Skyttä 2006-02-01 22:39:35 UTC
I hope this was fixed in 1.3.3-3.fc4.  Could you verify?

Comment 3 Shahms E. King 2006-02-16 17:07:43 UTC
I'm closing this bug as the problem should be fixed by the current release and
there has been no response to Ville's request for more information.