Bug 829352
| Summary: | [abrt] subversion-1.7.4-6.fc17: __GI_raise: Process /usr/bin/svn was killed by signal 6 (SIGABRT) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gabriele Svelto <gabriele.svelto> | ||||||||
| Component: | subversion | Assignee: | Joe Orton <jorton> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 17 | CC: | jorton, vanmeeuwen+fedora, ville.skytta | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i686 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:61f7db82948239bab164a17ff5d4ef4bfd8e0f29 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-08-01 01:26:28 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: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Gabriele Svelto
2012-06-06 14:27:38 UTC
Created attachment 589924 [details]
File: dso_list
Created attachment 589925 [details]
File: maps
Created attachment 589926 [details]
File: backtrace
Can you reproduce this with the 1.7.5 packages in updates-testing? I tested with a random old 1.6.x checkout with 1.7.5 installed and it worked fine. I updated to subversion-1.7.5-1.fc17.i686 and the problem is gone, now subversion only prints out a warning message and exits with error code 1 instead of crashing. There are certain cases which "svn upgrade" will not ever be able to handle. In this case it looks like the state of the subtree was already modifed from the original checkout (maybe an "svn mv" or "svn cp"?). Without the parent node the upgrade cannot be completed; I'd say you should try a new checkout. I didn't excpect 'svn upgrade' to succeed, the fact that I tried it on a directory that had been taken out of its original tree and had local modifications was an accident. Still I thought signaling the crash made sense as it shouldn't happen during normal operation, even if the checkout is incomplete. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |