zy. The original code is in fact:
return String(
u"%s(%s)" % (func_name, u", ".join(rendered_args)),
quotes=None)
So, could anyone help me fixing this? What's the way to make it always
work? I wouldn't like to just drop Python 3.x support because of
this happens?
Cheers,
Thomas Goirand (zigo)
Setting up openstack-dashboard (2014.2~b3-1) ...
RemovedInDjango18Warning: 'The `cycle` template tag is changing to
escape its arguments; the non-autoescaping version is deprecated. Load
it from the `future` tag library to start using the ne
le
names) and confusing (it's easy to forget them), and non-reversible, so
I'd like to avoid it if possible.
I'm sorry for the mess and added work.
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
list,
and believe that there's an aggressive, when in fact, the intention is
only to be convincing. Please assume good faith.
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
ing/vendoring) at the app level.
Since a few days, the Debian policy manual explicitly forbids static
linking. I fully agree with the decision to make it explicit.
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
opinions about his library, Cory and I take backwards
> compatibility and stability very seriously. This means anyone can
> upgrade to a newer version of requests without worrying that it will
> be backwards incompatible.
That's very good, thanks for taking care of this. Ho
Hi,
Please see this:
https://review.openstack.org/122993
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
of a problem for me (since I use
a git based workflow).
The 1.4.0.0a5 is confusing... :(
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
7;m well aware of this. As I wrote, I already had to deal with issues
like that, and I'm expecting even more in the future.
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
s with vendorizing,
even if it is my view that it's a really bad thing, is IMO not
interesting for the OpenStack project.
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
n’t be vendoring it’s
> dependencies since it is clear that the team has their reasons and
> does not want to switch to the dependency model again.
I'm sure they have tons of wrong reasons. If they don't want to change
anything, then we can only try to work around the issue, and never
#x27;t want to have to patch all of
OpenStack to do it there as well.
And no, there's no good excuse here...
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
security nightmare for distributions. It's
just a shame we didn't have it for Icehouse...
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
rything together.
Cheers,
Thomas Goirand (zigo)
Original Message
Subject: [PKG-Openstack-devel] Bug#755651: [openstack-dev] [horizon]
Support for Django 1.7: there's a bit of work, though it looks fixable
to me...
Resent-Date: Wed, 10 Sep 2014 20:45:23 +
Resent-From: Raph
nd the code is easier to understand., with more
extensive unit tests.
As for the issue with Redhat packaging, well, I'm sorry if that's a
problem for you, though really, pymemcache is a good choice, and I
support Julien on that one.
Cheers,
Thomas Goirand (zigo)
P.S: It's to
rvers recently too, as it became a way too
aggressive. I very much prefer to use my laptop to use git review than
having to bounce around servers. :(
Are their alternative IPs that I could use for review.openstack.org?
Cheers,
Thomas Goirand (zigo)
P.S: If a Chinese official read this, an easy w
So I was wondering if it was possible to keep compatibility with version
2.3.1.0 of compass-bootstrap-sass-plugin within Horizon.
Thoughts anyone?
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
ible. This creates more issues than it solves problems.
Any idea, comment or whatever that may help would be appreciated.
Cheers,
Thomas Goirand (zigo)
P.S: By the way, there's issues with python-oslo.utils with Python 3.4,
after solving the above problem...
__
ssaging, and pycadf. I
hope that's not an issue.
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
and need to adopt a way
more conservative attitude.
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 08/05/2014 04:06 PM, Julie Pichon wrote:
> On 05/08/14 08:11, Thomas Goirand wrote:
>> And there's also test_change_password_shows_message_on_login_page which
>> fails. Here's the end of the stack dump:
>>
>> File "/usr/lib/python2.7/dist-packages/r
s.py", line
375, in send
raise ConnectionError(e, request=request)
ConnectionError: HTTPConnectionPool(host='public.nova.example.com',
port=8774): Max retries exceeded with url: /v2/extensions (Caused by
: [Errno -2] Name or service not known)
Help fixing the above 2 remaining unit t
ot a Django expert, so I it'd be awesome to get help on this. Best
would be that:
1/ Support for Django 1.7 is added to Juno
2/ The changes are backported to Icehouse (even if this doesn't make it
into the stable branch because of "let's stay safe", I can add
On 07/28/2014 04:04 AM, Chris Dent wrote:
> On Mon, 28 Jul 2014, Thomas Goirand wrote:
>
>> That's exactly the version which I've been looking at. The thing is,
>> when I run the unit test with that version, it just bombs on me because
>> mechanize isn't
sing.
Please let me know if you can release a new version of wsgi-intercept
cleaned from any trace of mechanize, or if you think this can't be done.
If the former, then I'll just wait until you're done so that I can fix
#755315 (which is why I'm adding the Debian
On 07/27/2014 12:22 AM, Denis Makogon wrote:
> суббота, 26 июля 2014 г. пользователь Thomas Goirand написал:
> At this point, I gave-up with mechanize. But then, this makes me wonder:
> can we continue to use wsgi-intercept if it depends on such a bad Python
> module.
&g
stick to an older version of wsgi-intercept (which I do not
recommend, for maintainability reasons), could someone help me to fix
the Python 3.4 issue I'm having with wsgi-intercept? Removing Python 3
support would be sad... :(
Your thoughts?
s/1.7/#python-compatibility
Having the gate putting a cap on Django < 1.7 doesn't mean that nobody
can write patches to support it. Just that it's going to be more
difficult to test.
Thomas Goirand (zigo)
___
OpenStack-dev mailing lis
with an extensive Django experience needs to work on this.
So, I NEED HELP HERE! :)
Thoughts, comments, or whatever else is welcome! [1]
Cheers,
Thomas Goirand (zigo)
[1] but discussing how upgrading to Django 1.7 would be difficult isn't:
that's counter pro
all* projects could switch to that, and not
just Neutron, otherwise, we'd be just adding a new dependency, which
isn't great.
Also, about eventlet, there's been long threads about switching to
something else like asyncio. Wouldn't it be tim
On 07/09/2014 05:31 PM, Julien Danjou wrote:
> On Wed, Jul 09 2014, Thomas Goirand wrote:
>
>> The thing is, having a lack of Python 3 support in python-memcached
>> prevents from having python-keystoneclient to support Python 3, and as a
>> consequence, about ever
ystoneclient to support Python 3, and as a
consequence, about everything else in OpenStack.
I don't have the necessary expertise/skills in Python 3 myself. Could
anyone volunteer to do the work? I'd integrate the patch within the
Debian package, of course, even if it's not released
On 06/30/2014 10:43 PM, Jeremy Stanley wrote:
> On 2014-06-30 22:11:30 +0800 (+0800), Thomas Goirand wrote:
>> It'd be nice to fix the fact that oslosphinx & hacking are
>> build-depending on each other. How can we fix this?
>
> They're only build-depending
go ahead and gate with Python 3.3, but please also consider
adding support for Python 3.4 at least, and Python 3.2 if you can.
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi,
It'd be nice to fix the fact that oslosphinx & hacking are
build-depending on each other. How can we fix this?
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bi
On 06/14/2014 07:26 PM, Thomas Goirand wrote:
> Hi,
>
> I've been thinking for a long time on how to fix dnsmasq unix rights
> issue in Neutron. Namely (from syslog):
>
> /var/lib/neutron/dhcp/{id}/host : Permission denied
>
> One way to fix it is to do:
> chmod
adduser" and add the nobody user in the
neutron group, but I'm discarding that option as the least safe.
I don't want to introduce a Debian specific security hole in my Neutron
package, and I am therefore seeking for advices in this list. What's the
safest way to fix that prob
On 06/13/2014 06:53 AM, Morgan Fainberg wrote:
> Hi Thomas,
>
> I felt a couple sentences here were reasonable to add (more than “don’t
> care” from before).
>
> I understand your concerns here, and I totally get what you’re driving
> at, but in the packaging world wouldn’t this make sense to ca
if upstream cared...
Also, it's truth bash8 is a very poor name, which can be very confusing
for our users. Something like bash-tidy or bashtidy would have been much
better (even with an 8 at the end...).
Thomas Goirand (zigo)
___
OpenStack-d
Hi,
It's looking like bash8 isn't great. It's too much python-centric. At
least that's the view of multiple Debian Developers (not really mine, I
honestly don't care that much...).
Could we think about a better name?
Cheers,
Thomas Goirand (zigo)
Original
On 05/30/2014 03:22 PM, Chmouel Boudjnah wrote:
>
> On Thu, May 29, 2014 at 11:25 AM, Thomas Goirand <mailto:z...@debian.org>> wrote:
>
> So I'm wondering: are we being careful enough when selecting
> dependencies? In this case, I think we haven't, a
On 05/29/2014 05:25 PM, Thomas Goirand wrote:
> Hi everyone,
>
> Recently, wrapt was added as a dependency. The Python module suffers
> from obvious design issues, like for example:
> - Lack of Python 3.4 support
> - Broken with Python 3.2
> - Upstream sources in "src&q
to its own use cases.
In a more general case, I would vouch for avoiding *any* Python package
which is embedding a copy of another one. This should IMO be solved
before the Python module reaches our global-requirements.txt.
Thoughts anyone?
Cheers,
Thomas Goirand (zigo)
__
On 05/07/2014 01:26 AM, Jeremy Stanley wrote:
> Given that's Sean's session before the break (assuming it doesn't
> get reshuffled) and he's signed up for the key signing too, he could
> probably be persuaded to end on time and allow us to quickly free up
> the room for that. If we go this route we
On 05/06/2014 12:00 AM, Hochmuth, Roland M wrote:
> for Monitoring as a Service (MaaS)
Great care with MaaS, as it also means Metal as a Service.
Just my 2 cents.
Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.op
ult configuration file, and let me play with horrible
tox hack to generate one myself (and manually add it to my package).
Please continue to store a default configuration file in the Git!!!
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
iguration files like
for other projects instead (on a single or multiple configuration files:
I don't care since I have the logic already implemented...).
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 05/02/2014 05:17 AM, Alexandre Viau wrote:
> Hello Everyone!
>
> My name is Alexandre Viau from Savoir-Faire Linux.
>
> We have submited a Monitoring as a Service blueprint and need feedback.
>
> Problem to solve: Ceilometer's purpose is to track and *measure/meter* usage
> information colle
tionError: False is not true
if running with Python 3.4.
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 04/29/2014 06:42 AM, Jeremy Stanley wrote:
> On 2014-04-26 17:05:41 -0700 (-0700), Clint Byrum wrote:
>> Just a friendly reminder to add yourself to this list if you are
>> interested in participating in the key signing in Atlanta:
>>
>> https://wiki.openstack.org/wiki/OpenPGP_Web_of_Trust/Juno_
On 04/11/2014 10:52 PM, Collins, Sean wrote:
> Many of those patches are stale - please join us in the subteam IRC
> meeting if you wish to coordinate development of IPv6 features, so that
> we can focus on updating them and getting them merged. At this point
> simply applying them to the Icehouse
On 04/11/2014 06:05 PM, Jaromir Coufal wrote:
> On 2014/11/04 10:27, Thomas Goirand wrote:
>> On 04/10/2014 04:32 PM, Jaromir Coufal wrote:
>>> Dear Stackers,
>>>
>>> I am happy to announce that yesterday Tuskar UI (TripleO UI) has tagged
>>> branch
) would be more than welcome,
as I had no time to test it myself! Of course, the plan is to have it
updated again "soon".
Cheers,
Thomas Goirand (zigo)
[1]
http://qa.debian.org/developer.php?login=openstack-de...@lists.alioth.debian.org
___
O
eviewing it and
evaluating it, then rewrite the patch header, and finally send me a
patchset to apply on top of Icehouse. It's much better that it is them,
rather than me, that works on that, as they are specialists of Neutron,
while I'm a specia
ting TripleO, Tuskar, and so on, on Debian
Wheezy (backports) and in Debian Sid [1]. Currently all of TripleO but
tripleo-image-elements is uploaded to Debian Experimental. I also have
Trusty packages (it's part of my build process).
If all, I need feedback. I'm quick to fix things if r
penStack packaging team in
alioth.debian.org, and contribute to it at least for this IPv6 support,
that'd be just great! I'm available if you need my help.
Could you please point to me to the list of needed patches? I would need
to
On 04/02/2014 06:38 PM, Salvatore Orlando wrote:
> Hi Thomas,
>
> it probably won't be a bad idea if you can share the patches you're
> applying to the default configuration files.
> I think all distros are patching them anyway, so this might allow us to
> provide mostly ready to use config files.
On 04/02/2014 11:01 PM, Solly Ross wrote:
> IMHO, having "Example:" on a separate line from the actual option is a lot
> easier for humans:
> you just delete a single character or use your editor-of-choice's uncomment
> macro to activate
> a line.
Please re-read what I wrote. There's things like
st one
(and example) from the 2nd one (a commented out directive). Could we
instead use something like this instead?
-# Example:
-# connection = mysql://root:pass@127.0.0.1:3306/neutron
+# Example: connection = mysql://root:pass@127.0.0.1:3306/neutron
It'd be nice if these changes could
On 04/01/2014 04:03 AM, Jeremy Stanley wrote:
> On 2014-03-31 10:55:06 +0200 (+0200), Thierry Carrez wrote:
>> No miracle here... All slots are pretty full as expected. I think our
>> best bet is still the 30-min morning break on Wednesday or Thursday at
>> 10:30am.
>
> Would finding an available
https://wiki.openstack.org/wiki/OpenPGP_Web_of_Trust/Juno_Summit
Please add yourself. We'll see if I can make it to Atlanta, and organize
something later on.
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openst
On 03/29/2014 01:07 AM, Sean Dague wrote:
> On 03/28/2014 12:50 PM, Thierry Carrez wrote:
>> Thierry Carrez wrote:
>>> Julien Danjou wrote:
>>>> On Thu, Mar 27 2014, Thomas Goirand wrote:
>>>>
>>>>> -happybase>=0.4,<=0.6
>>>
ze
exception in this case? If yes (please, everyone, agree! :) ), then
would >=0.8 or >=0.4,!=0.6,!=0.7 be better?
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
ree. Therefore, I just created a patch for the
stable/havana branch over here:
https://review.openstack.org/82298
I'd really like to have it included in the next stable release of
Horizon. I don't think this one is hard to deal with, and I hope it will
go through even with the lack of ti
On 03/22/2014 12:58 AM, Joe Gordon wrote:
>
> So it sounds like we need:
>
> * Hacking 0.8.1 to fix the oslo.sphinx oslosphinx issue for Icehouse.
> Since we cap hacking versions at 0.9 [1] this will get used in icehouse.
> * Hacking 0.9 to release all the new hacking goodness. This will be
> t
Hi,
The current version of python-hacking wants python-oslo.sphinx, but
we're moving to python-oslosphinx. In Debian, I made python-oslo.sphinx
as a transition empty package that only depends on python-oslosphinx. As
a consequence, python-hacking needs to be updated to use
python-oslosphinx, other
or that following assumption, so
> the test failures aren't particularly helpful.
Oh, ok, thanks!
I've added python-memcache *AND* memcached as build-dependency, then
everything is back to working! :)
Thanks again for the above help,
27;m worried that this is the symptoms of a problem with some backends.
Can someone confirm if there's a real problem or if I should just
declare a build-conflict?
Cheers,
Thomas Goirand (zigo)
=
On 03/19/2014 09:25 PM, victor stinner wrote:
> Hi,
>
> According to the following table, paste is blocking many OpenStack servers to
> be ported to Python 3:
>
>https://wiki.openstack.org/wiki/Python3
I had a look to this, and found it weird that ironicclient is marked as
supporting Python
On 03/19/2014 02:42 AM, Nikhil Manchanda wrote:
>
> Thomas Goirand writes:
>
>> On 03/18/2014 06:12 PM, Thierry Carrez wrote:
>>> Thomas Goirand wrote:
> [...]
>>> Trove turned out to not be participating in global requirements, and
>>> has 3 items
On 03/18/2014 06:12 PM, Thierry Carrez wrote:
> Thomas Goirand wrote:
>> We're now 1 month away from the scheduled release date. It is my strong
>> opinion (as the main Debian OpenStack package maintainer) that for the
>> last Havana release, the freeze of dependenc
On 03/18/2014 02:51 PM, Andreas Jaeger wrote:
> On 03/18/2014 07:14 AM, Thomas Goirand wrote:
>> Hi,
>>
>> We're now 1 month away from the scheduled release date. It is my strong
>> opinion (as the main Debian OpenStack package maintainer) that for the
>&
sters
NEW queue in time for new packages.
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 03/14/2014 09:11 PM, Julie Pichon wrote:
> On 14/03/14 11:31, Thomas Goirand wrote:
>> Hi,
>>
>> A few months ago, I raised the fact that Selenium *CANNOT* be a hard
>> test-requirements.txt build-dependency of Horizon, because it is
>> non-free (because of b
again, and I get some unit
tests errors (see below).
Guys, could we stop having this kind of regressions, and make Selenium
tests not mandatory? They aren't runnable in Debian.
Cheers,
Thomas Goirand (zigo)
==
ERRO
On 03/14/2014 02:06 AM, Sean Dague wrote:
> On 03/13/2014 12:31 PM, Thomas Goirand wrote:
>> On 03/12/2014 07:07 PM, Sean Dague wrote:
>>> Because of where we are in the freeze, I think this should wait until
>>> Juno opens to fix. Icehouse will only be compatible with
On 03/14/2014 05:20 AM, John Dennis wrote:
> On 03/13/2014 12:31 AM, Thomas Goirand wrote:
>> Hi,
>>
>> Since Havana, I've been ignoring the 5 unit test failures that I always
>> get. Though I think it'd be nice to have them fixed. The log file is
>> avai
On 03/12/2014 07:07 PM, Sean Dague wrote:
> Because of where we are in the freeze, I think this should wait until
> Juno opens to fix. Icehouse will only be compatible with SQLA 0.8, which
> I think is fine. I expect the rest of the issues can be addressed during
> Juno 1.
>
> -Sean
Sean,
d be nice if I could solve these.
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi,
I just tried this:
https://review.openstack.org/#/c/79129/
and it seems everything works. \o/
Shall we lift the SQLA cap right away?
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
On 03/04/2014 06:13 PM, Julien Danjou wrote:
> On Tue, Mar 04 2014, James E. Blair wrote:
>
>> If there aren't objections to this plan, I think we can propose a motion
>> to the TC with a date and move forward with it fairly soon.
>
> That plan LGTM, and +1 for OFTC. :)
Same over here, +1 for OF
On 03/03/2014 11:17 PM, David Ripton wrote:
> On 03/02/2014 03:12 AM, Thomas Goirand wrote:
>> On 03/02/2014 12:03 PM, Thomas Goirand wrote:
>
>>> I hope to get support from core reviewers here, so that we can fix-up
>>> the SQLA 0.9.x compat ASAP, preferably b
On 03/03/2014 01:14 PM, Thomas Goirand wrote:
> On 03/03/2014 11:24 AM, Thomas Goirand wrote:
>> It looks like my patch fixes the first unit test failure. Though we
>> still need a fix for the 2nd problem:
>> AttributeError: 'module' object has no attribute 'A
On 03/03/2014 11:24 AM, Thomas Goirand wrote:
> It looks like my patch fixes the first unit test failure. Though we
> still need a fix for the 2nd problem:
> AttributeError: 'module' object has no attribute 'AbstractType'
Replying to myself...
It looks like AbstractT
uot;git rebase -i" and a "git review" change the order of the
paches? I don't dare trying, fearing to break something.
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 03/02/2014 12:03 PM, Thomas Goirand wrote:
> Hi,
>
> About a week ago, the maintainer of SQLAlchemy uploaded version 0.9.3 in
> Debian Sid. This of course broke a lot of OpenStack packages, including
> python-migrate.
>
> I do not intend to let this continue on for 7 mo
nst it as well.
Thoughts welcome,
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 02/28/2014 03:10 PM, Thomas Goirand wrote:
> On 02/28/2014 01:18 PM, Thomas Goirand wrote:
>> Hi,
>>
>> It's been now more than 40 days that this patch needs review:
>> https://review.openstack.org/#/c/67096/
>>
>> Could some core reviewers have a loo
On 02/28/2014 01:18 PM, Thomas Goirand wrote:
> Hi,
>
> It's been now more than 40 days that this patch needs review:
> https://review.openstack.org/#/c/67096/
>
> Could some core reviewers have a look, and eventually approve the patch?
> It's very important to
Hi,
It's been now more than 40 days that this patch needs review:
https://review.openstack.org/#/c/67096/
Could some core reviewers have a look, and eventually approve the patch?
It's very important to me, since Horizon is currently considered
non-free in Debian, due to the minified javascript fi
On 02/21/2014 06:13 AM, Vincent Untz wrote:
>Le jeudi 20 février 2014, à 12:02 -0800, Armando M. a écrit :
>> No action on a negative review means automatic expiration, if you lose
>> interest in something you care about whose fault is that?
>
> I beg to disagree. If we let patches go to automatic
reviewers have a *serious* look at this patch, and explain
why it's not ok for it to be approved? If nobody says why, then could
this be approved, so we can move on?
Cheers,
Thomas Goirand (zigo)
[1]
http://anonscm.debian.org/gitweb/?p=openstack/neutron.git;a=blob;f=debian/patches/fix-alembic
hich isn't in Debian,
I wouldn't be able because of the lack of the XenAPI python module.
Again, I'm unhappy about this situation, and hope it can be solved. I
warmly welcome Citrix to work with me (again) to fix this quickly.
Cheers,
Thomas Goirand (zigo)
__
will work on Debian support in xenserver-core.
Cheers,
Thomas Goirand (zigo)
For reference, see http://bugs.debian.org/738322 and
https://bugs.launchpad.net/bugs/1278352
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
On 02/03/2014 11:31 PM, Doug Hellmann wrote:
>
>
>
> On Mon, Feb 3, 2014 at 7:31 AM, Monty Taylor <mailto:mord...@inaugust.com>> wrote:
>
> On 02/03/2014 11:45 AM, Thomas Goirand wrote:
>
> Hi,
>
> Sorry if this has bee
ing version 1.3? I haven't seen issues building (most of not all)
core packages using WebOb 1.3. Did I miss the obvious?
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org
On 01/13/2014 10:38 PM, Sean Dague wrote:
> I know we've been here before, but I want to raise this again while
> there is still time left in icehouse.
>
> I would like to propose that the Nova v3 API removes the XML payload
> entirely. It adds complexity to the Nova code, and it requires
> duplic
On 01/08/2014 07:43 PM, Daniel P. Berrange wrote:
> On Wed, Jan 01, 2014 at 02:33:09PM +0800, Thomas Goirand wrote:
>> Hi,
>>
>> I was wondering if it would be possible for NoVNC to switch from
>> websockify to sockjs-client, which is available here:
>>
>>
On 01/05/2014 12:12 AM, Joshua Harlow wrote:
> it won't
> be the last time a library that is used in various projects
> causes dependency issues
Please, tell me the opposite thing. Please tell me that this is the last
time we're having a discussion about problems with SQLA 0.8. Please tell
me that
On 01/04/2014 07:53 AM, Joshua Harlow wrote:
> So another idea that was talked about on IRC.
>
> Taskflow exposes entrypoints for these storage backends (like your storage
> callback/interface idea).
>
> It currently provides 3 such 'default' backends [sqlalchemy, file/dir
> based, in-memory <-->
501 - 600 of 696 matches
Mail list logo
