On 2016-01-30 12:54:50 + (+), Dave Walker wrote:
> Unless anyone else objects, I'd be really happy if you are willing to
> scp a handrolled tarball.
Since there have been no objections, I've generated the tarball and
wheel for ceilometer 2015.1.3 on a representative of the same host
types
Jeremy Stanley wrote:
I'm perfectly okay uploading a tarball I or someone else builds for
this, as long as it's acceptable to leadership from stable branch
management, Telemetry and the community at large. Our infrastructure
exists to make things more consistent and convenient, but it's there
to
On 30/01/2016 7:54 AM, Dave Walker wrote:
> On 29 January 2016 at 20:36, Jeremy Stanley wrote:
>> On 2016-01-29 19:34:01 + (+), gordon chung wrote:
>>> hmm.. that's unfortunate... anything we need to update so this doesn't
>>> happen again? or just a matter of lesson learned, let's keep
On 29 January 2016 at 20:36, Jeremy Stanley wrote:
> On 2016-01-29 19:34:01 + (+), gordon chung wrote:
>> hmm.. that's unfortunate... anything we need to update so this doesn't
>> happen again? or just a matter of lesson learned, let's keep an eye out
>> next time?
>
> Well, I backported t
On 29 January 2016 at 19:34, gordon chung wrote:
>
> hmm.. that's unfortunate... anything we need to update so this doesn't
> happen again? or just a matter of lesson learned, let's keep an eye out
> next time?
>
> i guess the question is can users wait (a month?) for next release? i'm
> willing
On 2016-01-29 19:34:01 + (+), gordon chung wrote:
> hmm.. that's unfortunate... anything we need to update so this doesn't
> happen again? or just a matter of lesson learned, let's keep an eye out
> next time?
Well, I backported the downloadcache removal to the stable/kilo
branch after dis
On 2016-01-29 18:27:18 + (+), Jeremy Stanley wrote:
[...]
> Due to unfortunate timing, the last commit on stable/liberty was
> tested with pip 7 and merged, but the 2015.1.2 tag for that commit
> was pushed after pip 8 was released and so tox was no longer able
> to work with the tagged com
On 29/01/2016 1:27 PM, Jeremy Stanley wrote:
> On 2016-01-29 14:14:48 + (+), gordon chung wrote:
>> trying to understand the situation here. isn't this all managed by
>> global-reqs? an incompatible pip and pbr were release so now we
>> can't build? were we the only project using download
On 2016-01-29 14:14:48 + (+), gordon chung wrote:
> trying to understand the situation here. isn't this all managed by
> global-reqs? an incompatible pip and pbr were release so now we
> can't build? were we the only project using downloadcache (i don't
> recall us doing anything unique in
On 28/01/2016 3:37 PM, Jeremy Stanley wrote:
> On 2016-01-28 19:40:20 + (+), Dave Walker wrote:
> [...]
>> However, pip 8 was released around the same time as the tarballs were
>> attempted to be generated. Most of the projects are OK with this, but
>> ceilometer declares pbr!=0.7,<1.0,>
On 2016-01-28 19:40:20 + (+), Dave Walker wrote:
[...]
> However, pip 8 was released around the same time as the tarballs were
> attempted to be generated. Most of the projects are OK with this, but
> ceilometer declares pbr!=0.7,<1.0,>=0.6 and then forces an update via
> tox.
[...]
More
Hi,
As many of you have probably seen, most of the projects targeted for
2015.1.3 release have been tagged and have tarballs ready for release.
However, pip 8 was released around the same time as the tarballs were
attempted to be generated. Most of the projects are OK with this, but
ceilometer d
12 matches
Mail list logo
