You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <bl...@incubator.apache.org> on 2012/08/16 13:05:28 UTC
[Apache Bloodhound] #161: Install fails when trac-hacks is down
#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
Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#161: Install fails when trac-hacks is down
------------------------+----------------------
Reporter: jdreimann | Owner: gjm
Type: defect | Status: assigned
Priority: blocker | Milestone:
Component: installer | Version:
Resolution: | Keywords:
------------------------+----------------------
Comment (by gjm):
If we are allowed to we could serve a few pages out of our
issues.apache.org/bloodhound area that act as a python package index,
making use of the mod_rewrite to redirect for packages we don't know about
to pypi, something like this:
{{{
RewriteCond /var/www/pypi/$1 !-f
RewriteCond /var/www/pypi/$1 !-d
RewriteRule ^/bloodhound/pypi/(.*)$ http://pypi.python.org/pypi/$1
[P,L]
}}}
pages of this form would probably be good enough:
{{{
#!html
<html>
<body>
<h1>TracAccountManager Distributions</h1>
<ul>
<li><a
href="https://bitbucket.org/olemis/bloodhound-t-h.o/downloads/TracAccountManager-0.3.2.tar.gz">TracAccountManager-0.3.2.tar.gz</a>
</ul>
</body>
</html>
}}}
given a name like {{{/var/www/pypi/TracAccountManager/index.html}}}
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/161#comment:5>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#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:
------------------------+-----------------------
Changes (by gjm):
* status: review => closed
* resolution: => fixed
Comment:
That is fantastic.
r1412386 changes the TracAccountManager links to use pypi instead of trac-
hacks
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/161#comment:12>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#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 jdreimann):
Replying to [comment:14 rjollos]:
> Just a side-note [..]
As a comment on a closed ticket this is likely to be missed, it may be
worth raising this on the mailing list instead.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/161#comment:15>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#161: Install fails when trac-hacks is down
------------------------+----------------------
Reporter: jdreimann | Owner: olemis
Type: defect | Status: accepted
Priority: blocker | Milestone:
Component: installer | Version:
Resolution: | Keywords:
------------------------+----------------------
Changes (by olemis):
* status: new => accepted
* owner: nobody => olemis
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/161#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#161: Install fails when trac-hacks is down
------------------------+--------------------
Reporter: jdreimann | Owner: nobody
Type: defect | Status: new
Priority: blocker | Milestone:
Component: installer | Version:
Resolution: | Keywords:
------------------------+--------------------
Comment (by olemis):
==== For users #install
The following instructions are based on the assumption that you followed
[https://issues.apache.org/bloodhound/wiki/BloodhoundInstall#Installation
recommended installation steps].
If a similar failure happens to you , then download modified
[https://bitbucket.org/olemis/bloodhound-t-h.o/downloads/requirements.txt
requirements.txt] and
[https://bitbucket.org/olemis/bloodhound-t-h.o/downloads/requirements_dev.txt
requirements_dev.txt] files and replace the local copy created inside
`installer` folder. In a few words both files are aimed at downloading
from [https://bitbucket.org/olemis/bloodhound-t-h.o/ bitbucket hacks
mirror] the dependencies formerly found at [http://trac-hacks.org/ t-h.o]
.
After that remove everything in `installer/bloodhound` folder and follow
[https://issues.apache.org/bloodhound/wiki/BloodhoundInstall#Installation
recommended installation steps] but this time omitting initial svn
checkout as you should already have a local working copy.
Then you should see console output similar to this
[http://hudson.testrun.org/job/bh-tho-bb-test/3/console installation log].
'''PS''' In the next few days we shall be able to incorporate similar
steps in installer script so that you won't need to perform these
operations by hand. Sorry if this causes any trouble.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/161#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Posted by Ryan Ollos <ry...@wandisco.com>.
On Wed, Dec 5, 2012 at 8:04 AM, Olemis Lang <ol...@gmail.com> wrote:
> [...]
> > There seem to be two issues here:
> > 1. Specifying the version in requirements.txt, which appears to be
> > straightforward (4).
> > 2. Keeping the older packages available for all of the plugins we depend
> > on as newer versions of those packages are released, in order to give us
> > time to evaluate the new version and upgrade bloodhound in a controlled
> > manner.
> >
>
> +1
> all this is needed , yes .
>
>
I guess the thing to investigate next is whether we can host the packages
currently on PyPI elsewhere, and have pip search that location first. Once
I get that figured out (or if someone suggests a better way first), I'll
create a ticket for this issue and move forward.
Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Posted by Olemis Lang <ol...@gmail.com>.
On 12/5/12, Ryan Ollos <ry...@wandisco.com> wrote:
> On Tue, Nov 27, 2012 at 7:54 AM, Apache Bloodhound <
> bloodhound-dev@incubator.apache.org> wrote:
>
>> #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 olemis):
>>
>> jftr
>>
>> Replying to [comment:14 rjollos]:
>> [...]
>> > 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.
>>
>> Files uploaded to PyPI will remain there for a while ;) . There should
>> be
>> a way in requirements file to make pip install a particular version from
>> PyPI.
>
>
> That seems to depend on whether the developer chooses to leave the older
> packages on PyPI. TracAccountManager was released to version 0.4 last week,
> and the 0.3.2 package is no longer available on PyPI (1), as far as I can
> see.
>
You are absolutely right .
> I've just setup a new development environment following the instructions
> (2), and not surprisingly TracAccountManager 0.4 is now installed. I tend
> to think we should have more control over the upgrade of plugins, even for
> the development environment. There was an issue (3) discovered and resolved
> shortly after it's release that would likely have bit us.
>
:'(
> There seem to be two issues here:
> 1. Specifying the version in requirements.txt, which appears to be
> straightforward (4).
> 2. Keeping the older packages available for all of the plugins we depend
> on as newer versions of those packages are released, in order to give us
> time to evaluate the new version and upgrade bloodhound in a controlled
> manner.
>
+1
all this is needed , yes .
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Posted by Ryan Ollos <ry...@wandisco.com>.
On Tue, Nov 27, 2012 at 7:54 AM, Apache Bloodhound <
bloodhound-dev@incubator.apache.org> wrote:
> #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 olemis):
>
> jftr
>
> Replying to [comment:14 rjollos]:
> [...]
> > 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.
>
> Files uploaded to PyPI will remain there for a while ;) . There should be
> a way in requirements file to make pip install a particular version from
> PyPI.
That seems to depend on whether the developer chooses to leave the older
packages on PyPI. TracAccountManager was released to version 0.4 last week,
and the 0.3.2 package is no longer available on PyPI (1), as far as I can
see.
I've just setup a new development environment following the instructions
(2), and not surprisingly TracAccountManager 0.4 is now installed. I tend
to think we should have more control over the upgrade of plugins, even for
the development environment. There was an issue (3) discovered and resolved
shortly after it's release that would likely have bit us.
There seem to be two issues here:
1. Specifying the version in requirements.txt, which appears to be
straightforward (4).
2. Keeping the older packages available for all of the plugins we depend
on as newer versions of those packages are released, in order to give us
time to evaluate the new version and upgrade bloodhound in a controlled
manner.
The latter could be addressed by either contacting the plugin developers
and asking that they keep the older versions available on PyPI for a
certain period of time, or by capturing the packages ourselves in another
location. Relying on plugin developers to keep packages available for a
certain period of time does not seem robust solution, even if the
developers are reliable.
I guess this is just getting back to the old issue we've discussed as to
whether we can rely on plugins that are outside of our control. However, it
was a slightly different issue when we were pulling tagged versions of the
source code directly from trac-hacks (or elsewhere) rather than depending
on what is posted to PyPI. Relying on the tagged version, for the most part
we only have to be concerned about the server staying online since the
tagged version is unlikely to change or go away. The packages on PyPI seem
to be mroe volatile, but there might be a quick path to improving the
situation now, if we can find some way to easily capture the released
versions.
I'm interested to hear if others think this is a problem, and if so, how we
should address this.
(1) http://pypi.python.org/pypi/TracAccountManager
(2)
https://issues.apache.org/bloodhound/wiki/BloodhoundContributing#GettingTheSource
(3) https://trac-hacks.org/ticket/10669#comment:4
(4) http://www.pip-installer.org/en/latest/requirements.html
Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#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 olemis):
jftr
Replying to [comment:14 rjollos]:
[...]
> 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.
Files uploaded to PyPI will remain there for a while ;) . There should be
a way in requirements file to make pip install a particular version from
PyPI.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/161#comment:16>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#161: Install fails when trac-hacks is down
------------------------+----------------------
Reporter: jdreimann | Owner: gjm
Type: defect | Status: assigned
Priority: blocker | Milestone:
Component: installer | Version:
Resolution: | Keywords:
------------------------+----------------------
Changes (by gjm):
* owner: olemis => gjm
* status: accepted => assigned
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/161#comment:4>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#161: Install fails when trac-hacks is down
------------------------+-----------------------
Reporter: jdreimann | Owner: gjm
Type: defect | Status: assigned
Priority: blocker | Milestone: Release 2
Component: installer | Version:
Resolution: | Keywords:
------------------------+-----------------------
Changes (by gjm):
* milestone: => Release 2
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/161#comment:6>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#161: Install fails when trac-hacks is down
------------------------+-----------------------
Reporter: jdreimann | Owner: gjm
Type: defect | Status: assigned
Priority: blocker | Milestone: Release 3
Component: installer | Version:
Resolution: | Keywords:
------------------------+-----------------------
Comment (by gjm):
r1409747 updating requirements files so that we reduce the dependence on
trac-hacks to a single package
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/161#comment:7>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#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 olemis):
I have updated [pypi:TracThemeEngine] as well with sdists for version
2.1.0
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/161#comment:13>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Posted by Ryan Ollos <ry...@wandisco.com>.
On Thu, Nov 15, 2012 at 4:53 AM, Apache Bloodhound <
bloodhound-dev@incubator.apache.org> wrote:
> #161: Install fails when trac-hacks is down
> ------------------------+-----------------------
> Reporter: jdreimann | Owner: rjollos
> Type: defect | Status: assigned
> Priority: critical | Milestone: Release 3
> Component: installer | Version:
> Resolution: | Keywords:
> ------------------------+-----------------------
> Changes (by gjm):
>
> * owner: gjm => rjollos
> * priority: blocker => critical
>
>
> Comment:
>
> This may be about as far as we can go with improving the download
> locations until the accountmanager plugin is available on pypi. Even if we
> were to create a pypi like interface, I seem to remember there was a
> reluctance to recommend bitbucket as an alternative host.
>
> rjollos: hope you are OK with me assigning this to you. I am wondering if
> the accountmanager plugin is likely to get a new version on pypi.
>
Sure, no problem, this is a long standing item on my todo list. I've been
in touch with the original creator of the pypi page, so I'll get back in
touch with him and ask for control to change it.
Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#161: Install fails when trac-hacks is down
------------------------+-----------------------
Reporter: jdreimann | Owner: rjollos
Type: defect | Status: assigned
Priority: critical | Milestone: Release 3
Component: installer | Version:
Resolution: | Keywords:
------------------------+-----------------------
Changes (by gjm):
* owner: gjm => rjollos
* priority: blocker => critical
Comment:
This may be about as far as we can go with improving the download
locations until the accountmanager plugin is available on pypi. Even if we
were to create a pypi like interface, I seem to remember there was a
reluctance to recommend bitbucket as an alternative host.
rjollos: hope you are OK with me assigning this to you. I am wondering if
the accountmanager plugin is likely to get a new version on pypi.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/161#comment:8>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#161: Install fails when trac-hacks is down
------------------------+-----------------------
Reporter: jdreimann | Owner: gjm
Type: defect | Status: review
Priority: critical | Milestone: Release 3
Component: installer | Version:
Resolution: | Keywords:
------------------------+-----------------------
Changes (by rjollos):
* owner: rjollos => gjm
* status: accepted => review
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/161#comment:11>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#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
Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#161: Install fails when trac-hacks is down
------------------------+--------------------
Reporter: jdreimann | Owner: nobody
Type: defect | Status: new
Priority: blocker | Milestone:
Component: installer | Version:
Resolution: | Keywords:
------------------------+--------------------
Comment (by olemis):
Replying to [ticket:161 jdreimann]:
> [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]:
>
>
> Is this a known problem?
In any case , we should be prepared for situations like recent t-h.o
outage .
> Should this really be a fatal problem, or could the installer instead
skip over it if unavailable?
Not a fatal problem thanks to [https://bitbucket.org/hasienda/t-h.o_shadow
unofficial t-h.o mirror at Bitbucket].
> 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?
I'll document what I did in order to work around this particular problem,
at least as long as hacks site is down. Firstly I created
[https://bitbucket.org/olemis/bloodhound-t-h.o a clone] of aforementioned
repository and checked out source code for [http://trac-
hacks.org/wiki/AccountManagerPlugin AccountManagerPlugin] located at
[https://bitbucket.org/olemis/bloodhound-t-h.o/src/tip/accountmanagerplugin/0.11
accountmanagerplugin/0.11] subfolder. Then I had to add the following
''MANIFEST.in'' file ...
{{{
graft acct_mgr/htdocs
graft acct_mgr/locale
graft acct_mgr/templates
}}}
... in order to build correct source tarball by executing the following
command
{{{
#!sh
$ python setup.py sdist --formats=gztar
}}}
I followed similar steps for
[https://bitbucket.org/olemis/bloodhound-t-h.o/src/tip/themeengineplugin/0.11
themeengineplugin] and
[https://bitbucket.org/olemis/bloodhound-t-h.o/src/tip/permredirectplugin/0.11
permredirectplugin] subfolders (''MANIFEST.in'' file not needed in these
cases). The resulting ''sdist'' packages have been uploaded to
[https://bitbucket.org/olemis/bloodhound-t-h.o/downloads downloads area]
for that repository.
That's the philosophical explanation ...
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/161#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#161: Install fails when trac-hacks is down
------------------------+-----------------------
Reporter: jdreimann | Owner: rjollos
Type: defect | Status: accepted
Priority: critical | Milestone: Release 3
Component: installer | Version:
Resolution: | Keywords:
------------------------+-----------------------
Changes (by rjollos):
* status: assigned => accepted
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/161#comment:10>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#161: Install fails when trac-hacks is down
------------------------+-----------------------
Reporter: jdreimann | Owner: rjollos
Type: defect | Status: assigned
Priority: critical | Milestone: Release 3
Component: installer | Version:
Resolution: | Keywords:
------------------------+-----------------------
Comment (by rjollos):
This should be fixed now, thanks to help from trachacks:coderanger and
trachacks:hasienda. We also have requests out to add PyPI page ownership
for trachacks:PermRedirectPlugin to trachacks:ejucovy (current maintainer)
and trachacks:ThemeEnginePlugin to olemis (current maintainer).
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/161#comment:9>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker