After a short delay for reasons Openstack is now up to date on Gentoo.
Just `emerge =sys-cluster/openstack-meta-2017.1.` with your desired
use flags to pull in the head of the services stable branches and their
dependencies.
--
Matthew Thode (prometheanfire)
signature.asc
Description
quirements) know when it's released
so we can make a feature freeze exception (and email the list with
[requirements][FFE] in the title).
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
minor than something more serious (not JUST
breaking testing).
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions
to stable/newton) so this is
easier to merge.
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev
e minimal supported version from
> 4.10.0+ to 4.13.3+ (when the later is even released; we are still at the
> stage of backport).
>
> Ihar
>
Ya that makes sense, the patch can be altered to just block 4.13.1,2
(assuming 4.13.3 really does fix it)
--
-- Ma
___
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
Are you fine with the knock on effects that a gr update would cause
(not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
I think the backport/release and mask of the bad oslo.db should be enough.
--
-- Matthew Thode (prometheanfire)
sign
penstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
I don't think this will impact and cause a rerelease for any project so
I'm fine with this.
--
-- Matthew Tho
n python 3
>> (through uwsgi).
>
> Is there a gate job to back that up?
>
> Doug
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-d
stack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
I think / thought keystone was supported on python 3 (maybe not all
features in mitaka though). I'm currently run
age questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
It looks like this has limited impact so I'm ok with this. It (and the
keystonemiddleware ffe) are kinda late in the cycle though...
--
--
: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
Nothing in codesearch popped out at me so this looks fine.
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signa
..@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
Both of these are bumps to upper-constraints, which is good. Also, I
don't see a problem with downstream projects (as found via codesearch).
--
-- Matth
it impacts this late in the cycle. Is there ANY way we can
not merge this?
just some of the things that would need to be re-released
networking-ovn (just had their rc1)
os-net-config
os-vif
oslo.config
oslo.serialization
oslo.utils
oslo.versionedobjects
oslo.vmware
python-neutronclient
wsme
--
m with this anyway as
they are using newer netaddr anyway (0.7.18 for both debian and gentoo
at least).
In short, if the releases and requirements teams are both fine with
this, ok :D (and tonyb is on both...)
--
-- Matthew Thode (prometheanfire)
signature.asc
De
On 09/09/2016 04:24 PM, gordon chung wrote:
>
>
> On 09/09/16 03:45 PM, Matthew Thode wrote:
>> Does this mean that the minimum (GR needs raising as well)?
>
> iiuc, just the max or upper-constraints.
>
> cheers,
>
k, I already +2'd it as I think this is fi
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
Does this mean that the minimum (GR needs raising as well)?
--
-
://bugs.launchpad.net/nova/+bug/1630448
At the moment I think the first bug is likely the cause of the second
bug, but don't have enough info to verify or fix it.
--
Matthew Thode (prometheanfire)
__
OpenStack Development
enStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Awesome :D
Gentoo packages have been done for a few days with upgrades tested from
mit
for that?
This would basically require a re-release (RC2) for all the projects at
this point.
http://codesearch.openstack.org/?q=swiftclient=nope=requirements.txt=
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: Open
t for tony's feedback.
http://codesearch.openstack.org/?q=kuryr=nope=requirements.txt=
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for us
16-User-Survey-Report.pdf
>
I don't know about nova, but at least in keystone when I was testing
upgrades I found an error that had to be fixed before release of Mitaka.
Guess I'm part of the 4% :(
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
___
On 08/18/2016 01:50 PM, Matt Riedemann wrote:
> On 8/18/2016 1:18 PM, Matthew Thode wrote:
>> Perhaps a better option would be to get oslo.db to run cross-project
>> checks like we do in requirements. That way the right team is covering
>> the usage of postgres and we stil
we're really using the python module and not
> the binaries.
>
> --Adam
Is there a reason you are not using pecan?
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStac
we're stuck with Octavia not being
> packageable in downstream distros.
That's not quite true for but is certainly true for most :P
* www-servers/gunicorn
Available versions: 19.1.1 ~19.3.0 ~19.4.5 {doc examples test
PYTHON_TARGETS="pypy python2_7 python3_3 python3_4 python3
tions 1 or 2.
>
> --Adam
Personally I'm happy with it being in gr, it's not the perfect place
though. (bindep would probably be better I feel, it's packaged on my
distro)
Do you need a specific version (bindep can't handle versions)?
As a packager I'd rather not force the type of server on my us
for something like this for
audits the requirements team wishes to do to ensure no duplicate /
unmaintained libraries are used.
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
On 11/23/2016 04:57 AM, Tony Breeds wrote:
> On Wed, Nov 23, 2016 at 04:39:30AM -0600, Matthew Thode wrote:
>> Does Openstack (infra) have a centralized calendar that teams could used
>> for reoccurring tasks/bugs? Something like this would be useful for
>> things r
necessitate a 4.0.2.1 release
* tag was removed, can hopefully be recovered for checkout/branch
Here's the upstream bug to browse at your leisure :)
https://github.com/rohe/pysaml2/issues/366
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
evconf.cz in a few weeks on this too. I hope to return
> with
> some additional feedback on using DIB for building container things.
>
I'd be interested in extending this to Gentoo at least. Need to reduce
the stage size somewhat. I wonder if stage2 is small enough...
--
Ma
docs will be worse without you. I do hope
you will be going on to greater things.
--
-- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not fo
cific timeframe?
>
> Thanks for surfacing it Matthew.
>
> -amrith
Heh, thanks, I suspect a few things are fairly cross project for
requirements. Moving to new webob / eventlet / sqlalchemy for instance.
Is there a specific process we go through to do these?
--
Matthew Thode (prome
owner:dims-v
>
> Thanks,
> Dims
>
> On Wed, Mar 8, 2017 at 2:03 PM, Matthew Thode <prometheanf...@gentoo.org>
> wrote:
>> So, pycrypto upstream is dead and has been for a while, we should look
>> at moving off of it for both bugfix and security reasons.
>>
&
it's done perfectly. If
it's not done perfectly we have to deal with untangling the requirements
for a security update (or the like).
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital
Keep diskimage-builder under tripleo (EmilienM PTL).
> We don't want to carry this one anymore for the reasons mentioned in
> that thread.
>
As a sometimes contributor to DIB for Gentoo stuff I'm fine with moving
it out into it's own project under the big tent, with a PTL and all.
--
Matt
stack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> --
> Davanum Srinivas :: https://twitter.com/dims
>
> ______
> OpenStack Development Mailing List (not for usage question
..@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
This is fine with me, it's not used anywhere at the moment so doesn't
look to have any knockon effects.
http://codesearch.openstack.org/?
,
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
> Please release this and take the new version in for requirements repo,
>
> https://review.openstack.org/490001
>
> Andreas
Looks fine here, are you looking for just a UC bump?
--
Matthew Thode (prometheanfire)
signatu
g that worries me.
>
> From a requirements POV I'm +2 on a u-c bump -2 on a g-r bump.
>
> Yours Tony.
Agreed, the amount of projects that'd be impacted by a GR bump is too
high, but a UC bump is fine.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
___
not for usage questions)
> > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > >
> >
>
ber of projects, so the risk is fairly small.
>
> I assume you've done enough testing to feel comfortable that 4.5.2 will
> work better than 4.5.0 and 4.5.1?
>
> Doug
>
> __
> OpenStack Development Mail
added to the core group in a few days.
>
> --
> Best,
> Samuel Cassiba
>
I haven't worked with him in an openstack chef way, but I've worked with
him through the OSUOSL. He's always been great to work with. IIRC the
OSUOSL also uses chef to deploy openstack, so hopefully that hel
nfo/openstack-dev
The current plan is to thaw requirements on Monday. If that happens
you'll need to be very careful in reviewing any bot updates from our
master (queens) to your master (pike).
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
_
ing on OpenStack
> projects and their deliverables.
>
> A huge improvement from where PTLs in Mitaka and prior were manually
> tagging and signing deliverables, handling the release note process, and
> all other sorts of minutia that required extreme care and focus.
>
> A fine exa
e good to be in sync. The
same could be said to many of the bumps that go through the requirements
project. One of the things we've been working on is divergent
requirements, where the goal is to keep making sure all projects test
against one set of upper-constraints, but allow each projec
s)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
It sounds like you will need a requirements update as well, both UC and
maybe GR. GR would suck at this VERY late point. The cur
On 17-08-08 08:03:42, Matthew Thode wrote:
> On 17-08-08 16:11:53, Renat Akhmerov wrote:
> > Hi,
> >
> > We recently sent a patch [1] to release the version 3.1.2 of
> > python-mistralclient out of Pike branch. It was done after the date of
> > final cli
.
If you have questions, feel free to reach out to me on irc
(prometheanfire on freenode, #openstack-requirements for the channel) or
email.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
___
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Matthew Thode (prometheanfire)
signature.asc
Descr
https://review.openstack.org/#/q/project:openstack/requirements+status:open+NOT+branch:master
We currently do not have anyone able to review/workflow these items and
it'd be nice if we could get some eyes on these reviews.
Thanks,
--
Matthew Thode (prometheanfire)
signature.asc
Description
.
mistral
os-apply-config
os-collect-config
os-refresh-config
os-vif
If these projects could make a release (something fetchable by pypi) off
of master that's all that's needed. They all have updated their
requirements in master, just no consumable release.
--
Matthew Thode (prometheanfire
On 05/30/2017 04:08 PM, Emilien Macchi wrote:
> On Tue, May 30, 2017 at 8:36 PM, Matthew Thode
> <prometheanf...@gentoo.org> wrote:
>> We have a problem in requirements that projects that don't have the
>> cycle-with-intermediary release model (most of the cycle-with-milest
ew criteria to the requirements list that
> projects using the cycle-with-milestone model are not added to the list
> to avoid this issue in the future.
>
> Doug
>
> __________
> OpenStack Development Mailing List (not
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
gt; upstream can't (or won't) do.
>
> Chris
Us distro folks don't like it either :P
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Developme
in the #openstack-requirements channel.
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
> > UPPER_CONSTRAINTS changes
> > ACTIONS: Make sure master publishes {rocky,master}.txt
> > (optionally add the S release at this point,
> > it doesn't hurt)
>
> We could add new "future" series names as soon a
hose constraints files would never be removed but they'd stop getting
> updated when we EOL the requirements branch.
>
> How does that sound?
>
> Yours Tony.
That's correct, I haven't had time this week to create the jobs quite
yet, but hope to do so either this weekend or next w
raints are updated as soon as the git
> cache is updated.
>
> I think we should publish using a post-merge job. The job isn't
> expensive, right? It's just copying some files out of git onto the
> web server?
>
> Do we really land 20-30 changes to the constraints list on an av
post
* upper-constraints are available via published location immediately
* sets good precident for end users/devs to use it
cons - post
* both breaks and fixes quick
* more load on infra to publish (20-30 times a day)
--
Matthew Thod
n that we'll need to document and
> > possible check for somewhere in our tools.
> >
> > Yours Tony.
> >
> > [1] This just occurred to me
>
> __
> OpenStack Development Mailing List (not f
n EOL'd and now unbranched project. We could create a
temporary branch from the commit and retag, but as a rule we should not
use the same tag twice (removing the pointer that existed and reusing it
to point to a diferent
channel.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
stack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
We use it downstream to build ironic images using the process kevin
documented here.
https://cloudnull.io/2016/11/osic-building-baremetal-ironic-images/
It can probably be updated but it'd b
k.org/cgi-bin/mailman/listinfo/openstack-dev
I think we have three options here.
1. Unpublish. This is probably the simplest, but generally goes against
the policy of pypi to never unpublish things (it is not a hard and fast
rule though).
2. Rename. A bunch of work for downstreams but technicall
On 17-08-29 15:58:55, Jeremy Stanley wrote:
> On 2017-08-29 10:30:42 -0500 (-0500), Matthew Thode wrote:
> [...]
> > 3. reversion. Start new versions at 3000 or something, kinda
> > dirty imo.
>
> And sort of a 3.1 option is to prepend a PEP 440 version epoch:
>
>
s widely used, even as an implementation detail, is the
> strongest arguement i have for shared version control of it.
>
So what happens when someone wants to use gunicorn or add another wsgi server
to be tracked by the requirements repo? One
___
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
>
> __
; OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Meant to reply from this address, but below is my original response.
The first
OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
The first question I have is if ALL
hat'd need to be updated.
http://codesearch.openstack.org/?q=networkx=nope=.*requirements.*=
I'm open to uncapping networkx if these projects have buyin.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
Open
-L185
https://bugs.launchpad.net/ironic/+bug/1747384
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
On 18-05-09 13:42:02, Jim Rollenhagen wrote:
> On Wed, May 9, 2018 at 11:22 AM, Matthew Thode <prometheanf...@gentoo.org>
> wrote:
>
> > python-swiftclient prior to 3.2.0 seemed to incidentally support radosgw
> > tempurls. That is, there was no official s
On 18-05-09 12:24:32, Clay Gerrard wrote:
> On Wed, May 9, 2018 at 12:08 PM, Matthew Thode <prometheanf...@gentoo.org>
> wrote:
>
> >
> > * Proper fix would be to make ceph support the account field
> >
>
> Is the 'rgw_swift_account_in_url' option n
On 18-05-09 15:14:37, Matthew Thode wrote:
> On 18-05-09 12:24:32, Clay Gerrard wrote:
> > On Wed, May 9, 2018 at 12:08 PM, Matthew Thode <prometheanf...@gentoo.org>
> > wrote:
> >
> > >
> > > * Proper fix wo
On 18-05-10 11:09:41, Jim Rollenhagen wrote:
> On Thu, May 10, 2018 at 11:05 AM, Matthew Thode <prometheanf...@gentoo.org>
> wrote:
>
> > On 18-05-09 15:14:37, Matthew Thode wrote:
> > > On 18-05-09 12:24:32, Clay Gerrard wrote:
> > > > On W
47 | pycrypto>=2.6 # Public Domain
|
++-+--+-----------+
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: op
Please review your particular uncaping patch (all but rpm-packaging are
passing gate it looks like). We'd like to move on to a newer eventlet
for rocky.
https://review.openstack.org/#/q/topic:uncap-eventlet+status:open
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP
Please unblock webob-1.8.1, you are the only library holding it back at
this point. I don't see a way to submit code to the project so I cc'd
the project in launchpad.
https://bugs.launchpad.net/openstack-requirements/+bug/1765748
--
Matthew Thode (prometheanfire)
signature.asc
Description
On 18-05-15 12:25:04, Zane Bitter wrote:
> On 13/05/18 13:22, Matthew Thode wrote:
> > This is a reminder to the projects called out that they are using old,
> > unmaintained and probably insecure libraries (it's been dead since
> > 2014). Please migrate off to use the crypto
.get_router_for_floatingip:8:Field
list ends without a blank line; unexpected unindent.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questio
like to keep on 1.7.4 and have the affected projects fix the error
so we can move on, but the revert has been proposed (and approved to get
gate unbroken for them). https://review.openstack.org/568248 Any
advice from the community is welcome.
--
Matthew Thode (prometheanfire)
signature.asc
On 18-05-17 13:51:06, Tony Breeds wrote:
> On Wed, May 16, 2018 at 04:14:36PM -0500, Matthew Thode wrote:
> > On 18-05-16 17:07:09, Doug Hellmann wrote:
> > > Excerpts from Matthew Thode's message of 2018-05-16 15:59:47 -0500:
> > > > Sphinx has breaking changes (ye
-+
Reverse order this time :D
trove has https://review.openstack.org/#/c/573070 which is making good
progress
The rest (tatu, fuel, freezer, daisycloud-core) I don't see any reviews,
starting to wonder if they watch the list.
--
Matthew Thode (prometheanfire)
signature.asc
Description
; Feel free to reach out to me directly with any questions, looking forward to
> seeing everyone in Denver!
>
What if we want that train experience. I feel like there will be
something missing without it.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
ks anyone who helps us on this improments and looks forward to have more
> contributors joining us in OpenStack/Trove !
>
>
> Best wishes.
> Fan Zhang
>
> Original Message
> Sender: Matthew Thode
> Recipient:
> openstack-dev@lists.openstack.org
> Date: Wedn
n the openstack
domain an alias may not make as much sense, it'd have to be a full
account forward. It's useful for centralized spam filtering.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
_
On 18-06-15 15:29:07, Jeremy Stanley wrote:
> On 2018-06-15 10:23:36 -0500 (-0500), Matthew Thode wrote:
> [...]
> > Not sure it'd help but one option we do is to create aliases based
> > on the title. Though since the PTLs don't have addresses on the
> > openstack doma
Sphinx is being updated from 1.6.7 to 1.7.5. You may need to update
your docs/templates to work with it.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List
On 18-06-04 14:06:24, Matthew Thode wrote:
> On 18-05-13 12:22:06, Matthew Thode wrote:
> > This is a reminder to the projects called out that they are using old,
> > unmaintained and probably insecure libraries (it's been dead since
> > 2014). Please migrate off to use the
On 18-05-13 12:22:06, Matthew Thode wrote:
> This is a reminder to the projects called out that they are using old,
> unmaintained and probably insecure libraries (it's been dead since
> 2014). Please migrate off to use the cryptography library. We'd like
> to drop pycrypto from
t is actually being used in the various
> distros?
>
For Gentoo it's 0.20.1 right now, but that's mainly because I haven't
updated it myself (because Openstack).
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
at seem
> right?
>
> If we can make that happen before we start the zuul configuration
> porting work that we're going to do as part of the python3-first
> goal, then we can take advantage of those patches to trigger doc
> rebuilds in all of the projects.
>
Yep, talked about this
yboard story for projects that have already migrated.
>
Ya, I'm not sure what to do there. Requirements hasn't migrated because
other projects haven't migrated (we really need to be on both systems
unfortunately). Is it possible to half migrate?
--
Matthew Thode (prometheanfire)
signature.a
The short of it is that we are currently using eventlet 0.20.0. The bot
proposes 0.22.1 which fails updates, I think we need to start bugging
projects that fail the cross test jobs. What do you think?
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
On 17-12-20 10:56:50, Matthew Thode wrote:
> On 17-12-20 15:51:17, Afek, Ifat (Nokia - IL/Kfar Sava) wrote:
> > Hi,
> >
> > There is an open bug in launchpad about the new release of Networkx 2.0,
> > that is backward incompatible with versions 1.x [1].
> > Is th
On 18-01-13 00:41:28, Matthew Thode wrote:
> https://review.openstack.org/531788 is the review we are seeing it in,
> but 2.22.0 failed as well.
>
> I'm guessing it was introduced in either
>
> https://github.com/openstack/oslo.serialization/commit/c1a7079c26d27a2e46cca2
discuss "hot" last-minute cross-project issues -- if you have ideas
> of topics that we need to discuss in-person, please let us know.
>
As one of the teams in orange, what specific steps, if any, do we need to
tak
On 18-01-16 19:12:16, ChangBo Guo wrote:
> What's the issue for Glance, any bug link ?
>
> 2018-01-16 0:12 GMT+08:00 Matthew Thode <prometheanf...@gentoo.org>:
>
> > On 18-01-13 00:41:28, Matthew Thode wrote:
> > > https://review.openstack.org/5
101 - 200 of 315 matches
Mail list logo
