Bug 441694 - cvs assertion failure
cvs assertion failure
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: cvs (Show other bugs)
All Linux
high Severity medium
: rc
: ---
Assigned To: Jiri Moskovcak
Depends On:
Blocks: 391511
  Show dependency treegraph
Reported: 2008-04-09 11:03 EDT by Adam Stokes
Modified: 2015-02-01 17:48 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 769298 (view as bug list)
Last Closed: 2009-05-18 16:12:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
mimics upstream fix to remove assert statement (319 bytes, patch)
2008-04-09 11:03 EDT, Adam Stokes
no flags Details | Diff

  None (edit)
Description Adam Stokes 2008-04-09 11:03:26 EDT
Description of problem:
CVS fails with assertion error

Version-Release number of selected component (if applicable):
cvs 1.11.17

How reproducible:

Steps to Reproduce:
1. use cvs rtag
Actual results:
cvs: recurse.c:642: do_recursion: Assertion `strstr (repository, "/./") ==
((void *)0)' failed.
cvs [rtag aborted]: received abort signal

Expected results:
No error.

Additional info:
Comment 1 Adam Stokes 2008-04-09 11:03:26 EDT
Created attachment 301822 [details]
mimics upstream fix to remove assert statement
Comment 4 RHEL Product and Program Management 2008-09-05 13:13:47 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
Comment 9 Jan Ščotka 2009-01-08 06:32:29 EST
testcase created in 196259 -  cvs lacks LFS support
Comment 12 errata-xmlrpc 2009-05-18 16:12:10 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.