I'd like to propose new candidates for RPM packaging core reviewers:
Alan Pevec
Jakub Ruzicka
Both are involved in downstream RDO project and this group creation.
Alan is part of the stable release team and Jakub has been working on
our tooling since the beginning.
Having them onboard as core revi
Hi,
as a packager, I spend a lot of time to scrutinize the requirements
repo, and I find it easier to read if specifiers are ordered.
So in a quick glance, you can check which is the min version required
and max one without trying to search them among other specifiers.
I scripted a basic linter to
2016-06-22 7:23 GMT+02:00 Tony Breeds :
>
> I'm fine with doign something like this. I wrote [1] some time ago but didn't
> push on it as I needed to verify that this wouldn't create a "storm" of
> pointless updates that just reorder things in every projects
> *requirements.txt.
>
> I think the f
Yes, RDO faced the very same issue:
https://github.com/rdo-packages/neutron-fwaas-distgit/blob/rpm-master/openstack-neutron-fwaas.spec#L115
My understanding was that neutron folks were looking for a solution,
but we ship this workaround for now a month.
Regards,
H
___
2016-06-24 4:02 GMT+02:00 Tony Breeds :
>
> I think we need to pause on these 'normalizing' changes in g-r. They're
> genertaing whitspace only reviews in many, (possibly all) projects that have
> managed requirements.
>
> We need to do more testing and possibly make the bot smarter befoer we look
2016-06-28 17:53 GMT+02:00 Steven Dake (stdake) :
> The mitaka branch of Kolla requires 3.7 or later.
>
> Git checkout stable/mitaka
>
> Master may require 3.10, but that happens via the global requirements update
> process, of which RDO will surely address in the future.
>
> Regards
> -steve
>
Ye
My opinion as one of RDO release wranglers is not to support Fedora
for anything else that isn't trunk.
It's proven really hard to maintain all dependencies in a good state,
and when we managed to do that,
an update could break things at any time (like python-pymongo update
who was removed because
2016-06-30 14:07 GMT+02:00 Steven Dake (stdake) :
> What really cratered our implementation of fedora was the introduction of
> DNF. Prior to that, we led with Fedora. I switched my focus to something
> slower moving (CentOS) so I could focus on a properly working RDO rather
> then working around
2016-07-02 20:42 GMT+02:00 jason :
> Pip Package Name Supported By Centos CentOS Name Repo
> Name
> ==
> ansible yes
> ansible1.9.noarch
Hi,
the RDO community has packages available for Mitaka Stable in its
testing repositories.
Official RDO release will be announced after we validate this release
with our CI.
Regards,
H.
__
OpenStack Development Mailing List
Well, I'm more in favor having it as a sub-team of release mgmt team.
H,
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.
Started on removing some entries, I guess I have big cleanup to do RDO side.
H.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http:/
All Kolla requirements are packaged in RDO either in Fedora or CentOS
Cloud SIG repositories.
Kolla relies on RDO packages for RPM packages, but there's also a RPM
upstream packaging project.
Regards,
H.
__
OpenStack Developm
2015-05-27 23:26 GMT+02:00 Derek Higgins :
> On 27/05/15 09:14, Thomas Goirand wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> Hi all,
>>
>> tl;dr:
>> - - We'd like to push distribution packaging of OpenStack on upstream
>> gerrit with reviews.
>> - - The intention is to bette
2015-05-28 21:58 GMT+02:00 Paul Belanger :
>
> Personally, I'm a fan of mock. Is there plan to add support for it? Also,
> currently containers are not being used in -infra. Not saying it is a show
> stopper, but could see some initial planning that is required for it.
>
>
Nothing prevents us to
2015-05-28 10:40 GMT+02:00 Thomas Goirand :
>
> I don't know delorean at all, but what should be kept in mind is that,
> for Debian and Ubuntu, we *must* use sbuild, which is what is used on
> the buildd networks.
>
> I also started working on openstack-pkg-tools to provide such sbuild
> based buil
2015-05-29 15:41 GMT+02:00 Thierry Carrez :
> Hi everyone,
>
> TL;DR:
> - We propose to stop tagging coordinated point releases (like 2015.1.1)
> - We continue maintaining stable branches as a trusted source of stable
> updates for all projects though
>
Hi,
I'm one of the main maintainer of the p
2015-05-29 21:23 GMT+02:00 Ian Cordasco :
>
>
> On 5/29/15, 12:14, "Haïkel" wrote:
>
>>2015-05-29 15:41 GMT+02:00 Thierry Carrez :
>>> Hi everyone,
>>>
>>> TL;DR:
>>> - We propose to stop tagging coordinated point releases (like 2015
2015-05-29 21:36 GMT+02:00 Dave Walker :
> Responses inline.
>
> On 29 May 2015 6:15 pm, "Haïkel" wrote:
>>
>> 2015-05-29 15:41 GMT+02:00 Thierry Carrez :
>> > Hi everyone,
>> >
>> > TL;DR:
>> > - We propose to stop tagging coordi
2015-06-01 17:32 GMT+02:00 Alan Pevec :
>> *Plan C* would be to just let projects tag stable point releases from
>> time to time. That would solve all the original stated problems. And
>> that would solve objections 2 and 3, which I think are the most valid ones.
>
> and *Plan D* would be to start
Hi Neil,
We're already having this discussion on the downstream list.
RDO is currently moving packages publication for RHEL/CentOS over CentOS
mirrors. That's just a matter of time and finish the tooling
automating the publication
process for source packages.
In the mean time, you can find source
2015-06-03 12:59 GMT+02:00 Neil Jerram :
> Many thanks, Haïkel, that looks like the information that my team needed.
>
> Neil
>
Feel free to ask or join us on our downstream irc channel (#rdo @ freenode) if
you have further questions.
We also hold weekly public irc me
2015-06-03 17:23 GMT+02:00 Thomas Goirand :
> i
> On 06/03/2015 12:41 AM, James E. Blair wrote:
>> Hi,
>>
>> This came up at the TC meeting today, and I volunteered to provide an
>> update from the discussion.
>
> I've just read the IRC logs. And there's one thing I would like to make
> super clear
2015-06-03 23:41 GMT+02:00 Allison Randal :
>
> TBH, I don't think pip or distro packaging are ever going to be the
> right answer for fully configuring an OpenStack cloud. Because, there is
> no "one true cloud", there are a variety of different configurations and
> combinations depending on wheth
2016-02-12 21:57 GMT+01:00 Corey Bryant :
> Are any projects using sqlalchemy-utils?
>
> taskflow started using it recently, however it's only needed for a single
> type in taskflow (JSONType). I'm wondering if it's worth the effort of
> maintaining it and it's dependencies in Ubuntu main or if pe
2016-02-14 23:16 GMT+01:00 Davanum Srinivas :
> Hi,
>
> Short Story:
> pycryptodome if installed inadvertently will break several projects:
> Example : https://review.openstack.org/#/c/279926/
>
> Long Story:
> There's a new kid in town pycryptodome:
> https://github.com/Legrandin/pycryptodome
>
>
+1 it fuels the confusion that RDO Manager has downstream-only patches
which is not the case anymore.
And I'll bite anyone who will try to sneak downstream-only patches in
RDO package of tripleO.
Regards,
H.
__
OpenStack Dev
2017-08-10 9:52 GMT+02:00 Venkata R Edara :
> Hello All,
>
> we are from Red Hat and we have product called Gluster which is distributed
> file system. we have integrated Gluster with openstack-swift , the product
> is called
>
> gluster-swift . gluster-swift allows users to have SWIFT/S3 APIs with
2016-09-02 12:45 GMT+02:00 Dirk Müller :
> Hi,
>
> I would like to suggest Javier Peña as an additional core reviewer for
> the packaging-rpm core group. He's been an extremely valueable
+1
Javier has done a good job as a reviewer, and is key contributor to
add RDO 3rd CI.
Good job!
H.
> con
2016-09-08 19:33 GMT+02:00 Mehdi Abaakouk :
>
>
> Le 2016-09-08 16:21, Matthew Thode a écrit :
>>>
>>> Once it’s in, we’ll trigger another oslo.db release.
>
>
> The release change is ready: https://review.openstack.org/#/c/367482/
>
> I have tested it against Gnocchi we don't have any issue anymor
2018-02-13 23:53 GMT+01:00 Ben Nemec :
>
>
> On 02/13/2018 01:57 PM, Tom Barron wrote:
>>
>> Since python 2.7 will not be maintained past 2020 [1] it is a reasonable
>> conjecture that downstream distributions
>> will drop support for python 2 between now and then, perhaps as early as
>> next year.
2018-02-14 17:05 GMT+01:00 Ben Nemec :
>
>
> On 02/13/2018 05:30 PM, David Moreau Simard wrote:
>>
>> On Tue, Feb 13, 2018 at 5:53 PM, Ben Nemec wrote:
>>>
>>>
>>> I guess if RDO has chosen this path then we don't have much choice.
>>
>>
>> This makes it sound like we had a choice to begin with.
>
2018-02-14 22:53 GMT+01:00 Tom Barron :
> On 13/02/18 16:53 -0600, Ben Nemec wrote:
>>
>>
>>
>> On 02/13/2018 01:57 PM, Tom Barron wrote:
>>>
>>> Since python 2.7 will not be maintained past 2020 [1] it is a reasonable
>>> conjecture that downstream distributions
>>> will drop support for python 2
2018-02-15 11:25 GMT+01:00 Bob Ball :
> Hi Thomas,
>
> As noted on the patch, XenServer only has python 2 (and some versions of
> XenServer even has Python 2.4) in domain0. This is code that will not run in
> Debian (only in XenServer's dom0) and therefore can be ignored or removed
> from the D
2017-02-15 13:42 GMT+01:00 Thomas Goirand :
> Hi there,
>
> It's been a while since I planed on writing this message. I couldn't
> write it because the situation makes me really sad. At this point, it
> starts to be urgent to post it.
>
> As for many other folks, Mirantis decided to end its contrac
2017-02-16 15:43 GMT+01:00 Igor Yozhikov :
> Hello team.
> I want to announce the following changes to Packaging-RPM core team:
> I’d like to nominate Alberto Planas Dominguez known as aplanas on irc for
> Packaging-RPM core.
> Alberto done a lot of reviews for as for project modules [1],[2] as for
Hi,
I haven't seen this but I'd like to point that Redis moved to an open
core licensing model.
https://redislabs.com/community/commons-clause/
In short:
* base engine remains under BSD license
* modules move to ASL 2.0 + commons clause which is non-free
(prohibits sales of derived products)
IMH
2016-09-12 21:10 GMT+02:00 Thomas Goirand :
> I am writing to submit my candidacy for re-election as the PTL for the
> packaging-deb project.
>
> The idea sparked in Vancouver (spring 2015). The project joined the
> big-tent about a year ago (in August 2015, it was approved by the TC)
> But it then
Fellow RPM packagers,
I announce my candidacy for PTL of the Packaging Rpm project.
During the Newton cycle, we reached the point where we provide enough
artefacts to build OpenStack clients usable on all supported platforms.
As a PTL, my primary focus would be on:
* 3rd party CI: increase covera
2016-09-19 19:40 GMT+02:00 Jeffrey Zhang :
> Kolla core reviewer team,
>
> Kolla supports multiple Linux distros now, including
>
> * Ubuntu
> * CentOS
> * RHEL
> * Fedora
> * Debian
> * OracleLinux
>
> But only Ubuntu, CentOS, and OracleLinux are widely used and we have
> robust gate to ensure the
2016-09-21 16:34 GMT+02:00 Steven Dake (stdake) :
>
>
>
> On 9/20/16, 11:18 AM, "Haïkel" wrote:
>
> 2016-09-19 19:40 GMT+02:00 Jeffrey Zhang :
> > Kolla core reviewer team,
> >
> > Kolla supports multiple Linux distros now, inclu
Hi,
following our discussions about 3rd party gates in RPM packaging project,
I suggest that we vote in order to promote the following gates as voting:
- MOS CI
- SUSE CI
After promotion, all patchsets submitted will have to validate these gates
in order to get merged. And gates maintainers shoul
2016-09-26 16:05 GMT+02:00 Anita Kuno :
> On 16-09-26 07:48 AM, Haïkel wrote:
>>
>> Hi,
>>
>> following our discussions about 3rd party gates in RPM packaging project,
>> I suggest that we vote in order to promote the following gates as voting:
>> - MOS CI
RDO Newton GA was ready for more than an hour ago, builds are currently running.
Formal publication should happen soon.
Good job to all projects and release mgmt team!
Regards,
H.
__
OpenStack Development Mailing List (not f
could fix that up, it would be grand J
>
>
Sorry for the delay, it got in the wrong folder, I'll look into adding this
package.
H.
>
> Thanks
>
> -steve
>
>
>
>
>>
>> From: Haïkel
>> Reply-To: "OpenStack Development Mailing List (not for
45 matches
Mail list logo
