#31 build blockerbugs for el7
Closed: Fixed None Opened 9 years ago by tflink.

Infra wants us to move production blockerbugs to a new el7 vm controlled by ansible.

Most of the work is already done but we do need to rebuild the package with appropriate deps for epel7 and make sure it works


Waiting on epel7 builds for python-flask-assets, python-flask-sqlalchemy and python-cssmin:
* [[https://bugzilla.redhat.com/show_bug.cgi?id=1163987|python-cssmin]]
* [[https://bugzilla.redhat.com/show_bug.cgi?id=1163974|python-flask-assets]]

I'm a co-maintainer for python-flask-sqlalchemy and am taking care of the missing epel7 build there

That was fun, forgot that uglify-js is required to make a blockerbugs bundle. That should really be in the docs somewhere unless I just missed it

whee! more package updates required - python-flask-wtf in el7 is too old to work with python-wtforms in el7

I have acls on that package already and did the upgrade in fedora, will do a new build for el7

Found yet another missing build in the depchain: python-flask-babel. There's currently no el7 build for that and [[https://bugzilla.redhat.com/show_bug.cgi?id=1175391 | I've requested a build ]].

I've also hit some problems with python-flask-assets but one way or another (patch build or downgrade), it's fixable.

I'm finally getting almost done with this. I've submitted patches to make python-flask-assets work with the webassets build in epel7 (thanks to @dcallagh for the help and backporting there), a new python-flask-babel has been built (waiting push to epel-testing) and I've done a new build of python-flask-sqlalchemy for epel7.

I had to make some code and packaging changes in blockerbugs to make all this work, will be submitting a review shortly.

Once all the builds we need make it to epel7-stable and my changes to blockerbugs are reviewed, we should be good to go on a el7 build for blockerbugs and can proceed with the migration.

Closed by commit rBLKR4868a4916d4d.

Login to comment on this ticket.

Metadata