This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 60 days (the time period specified by
the administrator of this Tracker).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The 2.1.6 changelog says that this bug was fixed, but the actual fix is missing. The only modified files in CVS are configure.ac, NEWS and ChangeLog: http://sblim.cvs.sourceforge.net/sblim/gather/?sortby=date, reposdump.c is still at rev 1.1.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 60 days (the time period specified by
the administrator of this Tracker).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1198711
Originator: YES
Caused by an incorrect comparison, the attached patch fixes the problem.
Patch fixing reposdump segfault.
Logged In: YES
user_id=1198711
Originator: YES
File Added: gather-reposdump.patch
Logged In: YES
user_id=1198711
Originator: YES
Committed fix to CVS.
Logged In: YES
user_id=1312539
Originator: NO
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 60 days (the time period specified by
the administrator of this Tracker).
Logged In: YES
user_id=1496546
Originator: NO
The 2.1.6 changelog says that this bug was fixed, but the actual fix is missing. The only modified files in CVS are configure.ac, NEWS and ChangeLog: http://sblim.cvs.sourceforge.net/sblim/gather/?sortby=date, reposdump.c is still at rev 1.1.
The issue is still there... see previous comment from mmarek.
Committed patch to CVS Head.
This fix will be part of the 2.2.2 release.
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 60 days (the time period specified by
the administrator of this Tracker).