new cloudy world I am sure the paths will cross again. Till
> then, Sayo Nara, Take Care.
>
Sad to see you go, hope to see you around though. Good luck on your
journey. It was nice working with you.
--
Matthew Thode (prometheanfire)
On 18-10-09 11:12:30, Doug Hellmann wrote:
> Matthew Thode writes:
>
> > several projects have had problems with the new release, some have ways
> > of working around it, and some do not. I'm sending this just to raise
> > the issue and allow a place to discuss solu
somehow in further releases we may need
another solution.
https://review.openstack.org/#/c/608835/
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage
ing? I can't find it.
> > https://pypi.org/project/ceilometer/ certainly seems to be the right
> > project.
> >
> > The crux of the code issue is:
> > from ceilometer.network.statistics import driver
> >
> > in networking_odl/ceilometer/network/statistics/opend
On 18-09-06 13:33:12, Michel Peterson wrote:
> On Wed, Sep 5, 2018 at 6:03 PM, Matthew Thode
> wrote:
>
> > On 18-08-31 19:52:09, Matthew Thode wrote:
> > > The requirements project has a co-installability test for the various
> > > projects, networking-odl be
On 18-08-23 09:50:13, Matthew Thode wrote:
> This is your warning, if you have concerns please comment in
> https://review.openstack.org/589382 . cross tests pass, so that's a
> good sign... atm this is only for stein.
>
I pushed the big red button.
--
Matthew Thode (pr
>
> -Thomas
>
> [1] https://review.openstack.org/#/c/599422/
>
> On 05/09/2018 17:03, Matthew Thode wrote:
> > On 18-08-31 19:52:09, Matthew Thode wrote:
> > > The requirements project has a co-installability test for the various
> > > projects,
On 18-08-31 19:52:09, Matthew Thode wrote:
> The requirements project has a co-installability test for the various
> projects, networking-odl being included.
>
> Because of the way the dependancy on ceilometer is done it is blocking
> all reviews and updates to the requirements pro
On 18-09-05 07:04:12, Andreas Jaeger wrote:
> On 2018-09-05 05:20, Matthew Thode wrote:
> > With the move to per-project requirements (aka divergent requirements)
> > we started allowing projects to have differing exclusions and minimums.
> > As long as projects still
(not project-config) that you have
the check-requirements job as well.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
anymore.
As a side note, fungi noticed that when you branched you are still
installing ceilometer from master. Also, the ceilometer team
doesnt wish it to be used as a library either (like networking-odl
doesn't wish to be used as a library).
--
Matthew Thode (prometheanfire)
signature.asc
On 18-08-31 07:44:44, Jim Rollenhagen wrote:
> On Thu, Aug 30, 2018 at 11:10 PM, Matthew Thode
> wrote:
>
> > On 18-08-30 20:52:46, Matthew Thode wrote:
> > > On 18-08-23 09:50:13, Matthew Thode wrote:
> > > > This is your warning, if you have conc
On 18-08-30 20:52:46, Matthew Thode wrote:
> On 18-08-23 09:50:13, Matthew Thode wrote:
> > This is your warning, if you have concerns please comment in
> > https://review.openstack.org/589382 . cross tests pass, so that's a
> > good sign... atm this is only for stein.
> &
On 18-08-23 09:50:13, Matthew Thode wrote:
> This is your warning, if you have concerns please comment in
> https://review.openstack.org/589382 . cross tests pass, so that's a
> good sign... atm this is only for stein.
>
Consider yourself on notice, https://review.openstac
; 10x
> Yossi
>
> בתאריך יום ה׳, 30 באוג׳ 2018, 19:12, מאת Matthew Thode <
> prometheanf...@gentoo.org>:
>
> > On 18-08-30 17:54:24, Yossi Boaron wrote:
> > > Hi All,
> > >
> > > Kubernetes upper constraint was changed lately from 6.0.0 to 7.0.0
long til a version that supports >=7.0.0 comes out?
>
> Do you see any problem with this approach?
>
> Best regards
> Yossi
>
> [1] - https://review.openstack.org/#/c/594495/
> [2] - https://review.openstack.org/#/c/595569/
--
Matthew Thode
This is your warning, if you have concerns please comment in
https://review.openstack.org/589382 . cross tests pass, so that's a
good sign... atm this is only for stein.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
t; Ade
>
> On Tue, 2018-08-21 at 14:16 -0500, Matthew Thode wrote:
> > On 18-08-21 14:00:41, Ben Nemec wrote:
> > > Because castellan is in global-requirements, we need an FFE from
> > > requirements too. Can someone from the requirements team respond
> > >
; > > > > thread so
> > > > > > hopefully they can weigh in.
> > > > > >
> > > > >
> > > > > As far as releases go, this should be fine. If this doesn't affect
> > > > > any other
> > > &g
We've moved, please forward future correspondence to the following
location.
https://storyboard.openstack.org/#!/project/openstack/requirements
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
On 18-08-14 11:13:13, Matthew Thode wrote:
> This is to warn and call out all those projects that do not have a
> stable/rocky branch yet.
>
> If you are in the folloing list your project will need to realize that
> your master is testing against the requirements/constra
puppet-zaqar
python-tripleoclient
tripleo-common
tripleo-heat-templates
tripleo-image-elements
tripleo-puppet-elements
So please branch :D
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
On 18-08-14 13:56:28, Akihiro Motoki wrote:
> 2018年8月14日(火) 13:38 Matthew Thode :
> >
> > On 18-08-14 13:19:27, Akihiro Motoki wrote:
> > > Hi,
> > >
> > > I would like to request FFE for osc-lib 1.11.1 release.
> > >
> > > ht
t I am familiar whether we need
> to block it or not.
>
What libs (further down the dep tree) would need the exclusion? They'd
likely also need a FFE for at least a UC bump.
You have my (and requirements) ack for a UC only bump at least.
--
Matthew Thode (promethean
congress-devstack-api-mysql/c232d8a/job-output.txt.gz#_2018-08-13_11_46_28_441837
> [4] https://review.openstack.org/#/c/544025/
> [5]
> https://github.com/openstack/requirements/blob/stable/queens/upper-constraints.txt#L245
>
iirc, a UC bump is allowed if it fixes gating, so that's alri
t one instead.
>
> Release request:
> https://review.openstack.org/591485
>
Would this be a upper-constraint only bump?
If so reqs acks it
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
___
>
>
requirements FFE approved for UC only.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
for rocky yet. If one is not done by the final cycle-with-intermediary
> deadline, karbor will need to be excluded from the Rocky coordinated release.
> This would include service and clients.
>
requirements FFE approved for UC only.
--
Matthew Thode (prometheanfire)
es a U-C bump, and contains a few bug fixes from 2.9.0.
>
> Thanks,
>
> Graham
>
> 1 - https://review.openstack.org/590776
>
As discussed during the releases meeting, ack from reqs
--
Matthew Thode (promethean
On 18-08-08 18:00:35, Eric K wrote:
> Requesting the raised minimun just for openstack/congress.
> https://review.openstack.org/#/c/590021/
>
> No re-release required; it'll just take effect in RC1.
>
>
>
> On 8/8/18, 2:06 PM, "Matthew Thode" wrote:
>
On 18-08-08 18:00:14, Eric K wrote:
> Requesting the raised minimun just for openstack/congress.
> https://review.openstack.org/#/c/589995/
>
> No re-release required; it'll just take effect in RC1.
>
> On 8/8/18, 2:07 PM, "Matthew Thode" wrote:
>
> &
ng we can leave it as is.
>
> Thanks!
>
> https://review.openstack.org/#/c/589995/
>
Which project(s) will need the new minimum? Those projects would need
re-releases. Then my question then becomes if those projects need a
raised minumum too, and for which project(s). And so on.
--
s not
> disruptive to packaging [2]. If it is disruptive, we can just note it
> as a known issue.
Which project(s) will need the new minimum? Those projects would need
re-releases. Then my question then becomes if those projects need a
raised minumum too, and for which project(s). And s
On 18-08-08 17:57:32, Christophe Sauthier wrote:
>
>
> Le 2018-08-08 17:44, Matthew Thode a écrit :
> > On 18-08-08 16:49:51, Christophe Sauthier wrote:
> > > Hello all
> > >
> > > I'd like to ask for a FFE to release for python-cloudkittyclient
>
if I am not doing things right.
Will you require a bump to the minimum version required in requirements
files?
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List
d to "1.10", we need this release.
> > >
>
> XueFeng, do you just need upper-constraints raised for this, or also the
> minimum version? From that last sentence, I'm assuming you need to ensure only
> 1.8.0 is used for Rocky deployments.
>
OK, if it's JUST u
ing/decision if and when it comes down.)
>
Thanks for the update, if you are up to it, keeping us informed on this
would be nice, if only for the hilarity.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
should need a lower bounds bump - only the normal U-C bump.
>
ack'd
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
considering constraints is the minimum you can ask for an FFE for,
we'll go with that :P
FFE approved
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing Lis
On 18-08-06 21:37:12, Spyros Trigazis wrote:
> It is constraints only. There is no project
> that requires the new version.
>
> Spyros
>
> On Mon, 6 Aug 2018, 19:36 Matthew Thode, wrote:
>
> > On 18-08-06 18:34:42, Spyros Trigazis wrote:
> > > Hello,
&g
r if
there is some project that REQUIRES this new version to work (in which
case that project needs to update it's exclusions or minumum).
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack D
> that depend on the client, so we won't need a new release of any of the
> downstream consumers.
>
> We could add the exclusion to OSC on master, just for accuracy's sake.
>
Ya, it sounds like this is a valid FFE
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP
https://etherpad.openstack.org/p/stein-PTG-requirements
That is all
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
ic/tmp/requirements.txt | 64 |
glance-store==0.22.0 |
++--+--+-------+
--
Matthew Thode (prometheanfire)
m in networking-ansible,
but lgtm otherwise.
| networking-ansible | requirements.txt |5 | ansible-runner>=1.0.3 #
Apache-2.0 |
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
Ope
ey see the
> shiny new feature they might use it - and then be sad that it's half broken.
>
As long as it's only a UC bump you have my ack.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
_
--+
All these projects would need re-releases if you plan on raising the
minimum. They would also need reviews submitted individually for that.
A upper-constraint only fix would not need that, but would also still
allow consumers to encounter the bug, up to you to decide.
LGTM otherwise.
-
to smooth out the review process.
I look forward to continue working with you in this cycle, as your PTL or not.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List
s is your final warning. Starting
tomorrow you will have to make a FFE request to the list first.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for
idual projects and
not the requirements bot. It is recommended that you have a
lower-constraints.txt file and test with it to know when you need to
update. See the following example for how to run a basic tox LC job.
https://github.com/openstack/oslo.db/blob/master/tox.ini#L76-L81
--
Mat
dates from LP reflected in our SB story we could just leave the
> > bug tracker open on LP and run the migration tool "often".
> >
The feature we use most heavilly is the cross project tracking. I'm
just not sure how we'd deal with that when some projects are on LP an
Updated from global requirements
> |/
> * 8a9bcee 2018-01-18 03:35:02 + Updated from global requirements
> * 5d0fb11 2018-01-08 12:28:50 -0600 Follow the new PTI for document build
>
>
>
> [ Unreleased changes in openstack/sushy (master) ]
>
> Changes between 1
nion that we should decouple from distro supported python
versions and rely on what versions upstream python supports (longer
lifetimes than our releases iirc).
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
On 18-07-09 15:15:23, Matthew Thode wrote:
> We have a patch that looks good, can we get it merged?
>
> https://review.openstack.org/#/c/577833/
>
Anyone from taskflow around? Maybe it's better to just mail the ptl.
--
Matthew Thode (prometheanfire)
signature.asc
Description: P
We have a patch that looks good, can we get it merged?
https://review.openstack.org/#/c/577833/
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List
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
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
__
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 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
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
_
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
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
; 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
__
-+
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
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
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
.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-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
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
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
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
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-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 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
-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-04-06 09:41:07, Clark Boylan wrote:
> On Fri, Apr 6, 2018, at 9:34 AM, Matthew Thode wrote:
> > On 18-04-06 09:02:29, Jens Harbott wrote:
> > > 2018-04-05 19:26 GMT+00:00 Matthew Thode <prometheanf...@gentoo.org>:
> > > > On 18-04-05 20:11:04, Graham Hay
On 18-04-06 09:02:29, Jens Harbott wrote:
> 2018-04-05 19:26 GMT+00:00 Matthew Thode <prometheanf...@gentoo.org>:
> > On 18-04-05 20:11:04, Graham Hayes wrote:
> >> On 05/04/18 16:47, Matthew Thode wrote:
> >> > eventlet-0.22.1 has been out for a while now, we
On 18-04-05 20:11:04, Graham Hayes wrote:
> On 05/04/18 16:47, Matthew Thode wrote:
> > eventlet-0.22.1 has been out for a while now, we should try and use it.
> > Going to be fun times.
> >
> > I have a review projects can depend upon if they wish to test.
> > ht
eventlet-0.22.1 has been out for a while now, we should try and use it.
Going to be fun times.
I have a review projects can depend upon if they wish to test.
https://review.openstack.org/533021
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
enstack
ansible is doing in
https://github.com/openstack/openstack-ansible/blob/master/global-requirement-pins.txt
We could maintain it as a separate constraints file (or infra could
maintian it, doesn't mater). The file would only be used for the
initial get-pip install.
--
Matthew Thode (prometh
the fish.
--
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
://review.openstack.org/#/c/545182
solum: no open reviews
- looks like only a couple of functions need changing
trove: no open reviews
- mostly uses the random feature
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
t-api-vmware-tvd-t/logs/stack.sh.log.txt.gz#_2018-03-22_08_56_03_905
> Thanks
> Gary
It sounds like those versions need to be unpublished. This will likely
involve both infra and the releases team (not requirements). I've
tagged them to get their attention (and mentioned this in the releases
ir
gt;OpenStack with different versions of those dependencies is
> > >untested.
> > >
> >
> > As noted above I think that gathering the min versions/maskings from
> > openstack projects to be valuable (
t adjusting the
> version numbers once that dependency is in the global list will be
> easier.
>
Thanks for writing this up, I think it looks good in general, but like
you mentioned before, there is some discussion to be had about gathering
and creating a versionspec from all
ed to be adding it to the global-requirements.txt
> list. After that, it would depend on how picky we want to be. If the
> upper-constraints.txt list is successfully updated to avoid the release,
> we might not need anything in the project. If the project wants to
> provide detailed gui
and kubernetes
- to be co-installable with openstack libs (python-zunclient)
e. Raise the minimum acceptable version for kubernetes
raise the minimum version of websocket-client
- raise to above the versions kubernetes had problems with
--
Matthew Thode (prometheanfire)
signature.asc
ould do it like this.
1. add python-ldap-3.x to requirements (though it looks like that's still a beta
2. move existing pyldap to python-ldap
3. remove pyldap
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
on to rocky.
--
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
On 18-02-15 13:38:45, Matthew Thode wrote:
> On 18-02-15 09:31:19, Thomas Goirand wrote:
> > Hi,
> >
> > Since I'm getting some pressure from other DDs to actively remove Py2
> > support from my packages, I'm very much considering switching all of the
> > De
file-conflict so can not be coinstalled) I would like to ask for a
> FFE.
>
+2+W from requirements
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not
napi/dom0. Can we get those fixes? Here's my patch:
>
> https://review.openstack.org/544809
>
Gentoo has Openstack packaged for both python2.7 and python3.(5,6) for
pike. Queens will be the same for us at least, but I haven't had
problems with at least the core services running them
a FFE for it.
>
Requirements is fine with this, sorry for the delay.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
On 18-02-14 13:55:53, Sean McGinnis wrote:
> On Wed, Feb 14, 2018 at 10:09:47AM -0600, Matthew Thode wrote:
> > Development has stalled, (since 2014). It's been forked but now would
> > be a good time to move to a more actively maintained crypto library like
&
Development has stalled, (since 2014). It's been forked but now would
be a good time to move to a more actively maintained crypto library like
cryptography.
Requirements wishes to drop pycrypto. Let me know if there's anything
we can do to facilitate this.
--
Matthew Thode (prometheanfire
nt releases.
>
> From my side I can assure that the change is backwards compatible and very
> much wanted in stable/queens by many users.
>
> Hence we’re kindly asking to approve the release patch.
>
FFE approved from the requirements side.
--
Matthew Thode (prom
1 - 100 of 315 matches
Mail list logo
