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 Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Date Mon, 26 Nov 2012 08:28:03 GMT
#161: Install fails when trac-hacks is down
------------------------+-----------------------
  Reporter:  jdreimann  |      Owner:  gjm
      Type:  defect     |     Status:  closed
  Priority:  critical   |  Milestone:  Release 3
 Component:  installer  |    Version:
Resolution:  fixed      |   Keywords:
------------------------+-----------------------

Comment (by rjollos):

 Just a side-note to say that [trachacks:AccountManagerPlugin] 4.0 is very
 close to being released (pending license change from !BeerWare to 3-Clause
 BSD in [http://trac-hacks.org/ticket/10644 #10644]), and the new eggs
 should be uploaded to PyPI at that time. This had me thinking as to
 whether the older eggs would be retained on PyPI, and even if they aren't,
 setuptools will probably just go out and grab the latest version from
 PyPI, right? I wasn't sure if this had been given much thought already,
 and whether we might want more explicit control over the version being
 installed.

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

Mime
View raw message