Bug 752655 - Publishing to docs-stage Fails Due to Fedora Apparently Failing to Read CVS Config Setting in /etc/profile.d/cvs.sh
Summary: Publishing to docs-stage Fails Due to Fedora Apparently Failing to Read CVS C...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: publican
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ruediger Landmann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-10 03:34 UTC by David Le Sage
Modified: 2012-03-13 00:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-13 00:11:35 UTC
Type: ---


Attachments (Terms of Use)

Description David Le Sage 2011-11-10 03:34:16 UTC
Description of problem:
If the user attempts to publish a book to the Red Hat docs-stage with a fresh installation of Fedora 16, he or she will encounter the following error:

cvs.devel.redhat.com: Connection refused

This seems to be because Fedora is not recognising/reading the contents of the /etc/profile.d/cvs.sh file. (The contents of that file seem to be correct.)

Version-Release number of selected component (if applicable):
Fedora 16 (fresh installation)
publican-2.7-1.fc16.noarch

How reproducible:
Every time.

Steps to Reproduce:
1. Run publican package --lang en-US --cvs on a book that is tagged correctly and would publish successfully under Fedora 15.
  
Actual results:
cvs.devel.redhat.com: Connection refused

Expected results:
Book should be sent to staging server.

Additional info:
For a workaround, users should add the following lines to .bash_profile:

export CVS_RSH
export PATH

Save the file, then run

source .bash_profile to export the settings.  You should then be able to publish your book to the server.

Comment 1 Ruediger Landmann 2012-03-13 00:11:35 UTC
Closing this because the mechanism is now obsolete anyway...


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