| Summary: | svn crashes with Segmentation fault when checking out some repositories | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Stefan Puch <s.puch> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | luigiwalser, thierry.vignaud |
| Version: | 4 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | subversion-1.8.10-1.mga4.src.rpm | CVE: | |
| Status comment: | |||
| Attachments: |
cpuinfo Lenovo Thinkpad X201
Output from svn co with glibc-2.18-9.8.mga4 |
||
|
Description
Stefan Puch
2014-09-03 13:13:17 CEST
We recently updated both serf and subversion: https://bugs.mageia.org/show_bug.cgi?id=13914 https://bugs.mageia.org/show_bug.cgi?id=13838 Does reverting either of these updates fix the problem? In any case, please report the issue upstream to subversion. CC:
(none) =>
luigiwalser I tried without any success the following combinations from Mageia mirror: 1) libserf1-1.3.2-2.mga4.i586.rpm libsvn0-1.8.5-3.mga4.i586.rpm subversion-1.8.5-3.mga4.i586.rpm 2) libserf1-1.3.2-2.mga4.i586.rpm libsvn0-1.8.8-1.mga4.i586.rpm subversion-1.8.8-1.mga4.i586.rpm 3) libserf1-1.3.2-2.mga4.i586.rpm libsvn0-1.8.10-1.mga5.i586.rpm subversion-1.8.10-1.mga4.i586.rpm 4) libserf1-1.3.2-2.1.mga4.i586.rpm libsvn0-1.8.8-1.mga4.i586.rpm subversion-1.8.8-1.mga4.i586.rpm 5) with new version of libserf1 from Cauldron libserf1-1.3.7-1.mga5.i586.rpm libsvn0-1.8.10-1.mga4.i586.rpm subversion-1.8.10-1.mga4.i586.rpm ----------------------------------------------------------------------------- Debian stable and testing should working well (I've no debian system), here is the version output from a user: $ svn --version svn, version 1.8.10 (r1615264) compiled Aug 8 2014, 12:29:39 on x86_64-unknown-linux-gnu Copyright (C) 2014 The Apache Software Foundation. This software consists of contributions made by many people; see the NOTICE file for more information. Subversion is open source software, see http://subversion.apache.org/ The following repository access (RA) modules are available: * ra_svn : Module for accessing a repository using the svn network protocol. - with Cyrus SASL authentication - handles 'svn' scheme * ra_local : Module for accessing a repository on local disk. - handles 'file' scheme * ra_serf : Module for accessing a repository via WebDAV protocol using serf. - using serf 1.3.7 - handles 'http' scheme - handles 'https' scheme ----------------------------------------------------------------------------- @David > In any case, please report the issue upstream to subversion. Actually I've no login at subversion bugtracking system and it hard to report an issue there while other distros are working fine. Maybe this can be done by a user with some more development experience. Can you attach (not paste) your /proc/cpuinfo file? Keywords:
(none) =>
NEEDINFO Created attachment 5993 [details]
cpuinfo Lenovo Thinkpad X201
Thierry Vignaud
2015-03-05 11:49:33 CET
Attachment 5993 mime type:
application/octet-stream =>
text/plain What if you revert latest glibc update? ok, reverted back to glibc-2.18-9.8.mga4 and did the same procedure as described above. Problem still existing. svn version 1.8.11-1.mga4.i586. I add the output as attachment. Created attachment 5994 [details]
Output from svn co with glibc-2.18-9.8.mga4
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. 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 Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Status:
NEW =>
RESOLVED |