incubator-bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <bloodhound-...@incubator.apache.org>
Subject [Apache Bloodhound] #161: Install fails when trac-hacks is down
Date Thu, 16 Aug 2012 11:05:28 GMT
#161: Install fails when trac-hacks is down
-----------------------+--------------------
 Reporter:  jdreimann  |      Owner:  nobody
     Type:  defect     |     Status:  new
 Priority:  blocker    |  Milestone:
Component:  installer  |    Version:
 Keywords:             |
-----------------------+--------------------
 [http://mail-archives.apache.org/mod_mbox/incubator-bloodhound-
 dev/201208.mbox/%3Calpine.DEB.2.00.1208152337430.15473%40urchin.earth.li%3E
 Nick sent this to the mailing list]:

 I'm trying to follow the Bloodhound Install wiki page[1], against the
 latest version of Bloodhound from SVN. Against a fresh checkout, I
 followed the steps:

   cd bloodhound/installer
   virtualenv bloodhound
   source ./bloodhound/bin/activate
   pip install -r requirements-dev.txt

 Unforuanately, the pip step failed, the last few lines are:

 Checking out https://trac-hacks.org/svn/accountmanagerplugin/0.11 to
 ./bloodhound/src/tracaccountmanager
 svn: E160013: Unable to connect to a repository at URL 'https://trac-
 hacks.org/svn/accountmanagerplugin/0.11'
 svn: E160013: 'https://trac-hacks.org/svn/accountmanagerplugin/0.11' path
 not found
   Complete output from command /usr/bin/svn checkout -q https://trac-
 hacks.org/svn/accountmanagerplugin/0.11
 /data/issues/bloodhound/installer/bloodhound/src/tracaccountmanager:

 ----------------------------------------
 Command /usr/bin/svn checkout -q https://trac-
 hacks.org/svn/accountmanagerplugin/0.11
 /data/issues/bloodhound/installer/bloodhound/src/tracaccountmanager failed
 with error code 1 in None


 Is this a known problem? Should this really be a fatal problem, or could
 the installer instead skip over it if unavailable? Could either the
 installer or the docs provide some more help about what to do in the event
 of problems? And is there a workaround for now?

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/161>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker

Mime
View raw message