Closed totaam closed 3 years ago
There are many changes and I didn't have a chance to test them all. Some will have to be reverted i'm sure and some patches tweaked.
Right now I'm trying to solve the issue why it is ignoring my overriding of moduleset with
moduleset = "http://xpra.org/svn/Xpra/trunk/osx/jhbuild/modulesets-stable/gtk-osx.modules"
No matter what I do it seems to be ignoring it. I can't seem to figure this one out I will continue to try.
in .jhbuildrc-custom
libffi should be reverted to old version for 10.5 even left myself warning in there and missed it
<!-- anything higher than this fails on osx 10.5 -->
r13725 reverts this to older version once again
I believe I've discovered another issue. Openssl 1.1 doesn't seem to work properly with Python 2.7.12. Sometimes we can see errors like this
AttributeError: 'module' object has no attribute 'sha1'
because the hashlib module is broken
I am going to try and compile python before I install openssl and use the system openssl but this is probably not a good fix.
I've built python before doing openssl which seems to fix the issue for now. Not sure if python is built with openssl support or not at this point.
Maybe it never did build with openssl support in the first place?
new glib doesn't build on old system with this error
checking OSX version >= 10.9.0... no configure: error: OSX version is too old!
Will have to revert this change as well
problem with gobject-introspection
configure: error: Package requirements (glib-2.0 >= 2.48.0) were not met: Requested 'glib-2.0 >= 2.48.0' but version of GLib is 2.44.1
The python 2.7.x vs openssl 1.1 issue is tracked here: https://bugs.python.org/issue26470 This includes a fairly large patch which we may be able to use until python 2.7.13 comes out.
Everything builds once again for me.
*** success *** [119/119]
Still might be some issues with patches but these are probably from sources that redirect to https.
The process was something like this
jhbuild bootstrap jhbuild build python jhbuild build perl jhbuild -m ~/Source/jhbuild/modulesets/bootstrap.modules build perl-xml-simple --force jhbuild build curl export SSL_CERT_FILE="$HOME/gtk/inst/etc/ssl/cacert.pem" curl -o ${SSL_CERT_FILE} -k https://curl.haxx.se/ca/cacert.pem add to .jhbuildrc-custom so curl works for downloads os.environ["SSL_CERT_FILE"] = "/Users/osx/gtk/inst/etc/ssl/cacert.pem" jhbuild build
On older systems here where we can't update jhbuild anymore we probably need to overwrite ~/Sources/jhbuild/modulesets/bootstrap.modules with the one we have.
An update would do this normally its the only file you can't override in .jhbuildrc-custom
Maybe it would be simpler to hold on off new openssl for a bit is there some reason we need the latest?
Links to changesets: r13725 (libffi downgrade), r13726 (syntax typo), r13727 (removed python patch), r13728 (pixman revert), r13729 (gtk patch removed), r13730 (glib revert), r13731 (patch no longer applies?), r13732 (revert gobject-introspection)
Looks like comment:12 needs editing, shouldn't it be "jhbuild build python"?
We can go with openssl 1.0.2 until python 2.7.13 comes out.
r13786 changes openssl back to 1.0.2h until new python comes out.
Probably change this in the next release.
Going to do a full rebuild to make sure all is well then close this ticket.
Full rebuild worked no problem now I need to get pkg and dmg out to testing to see how it works.
Here are some changes beteween the stable-moduleset we use and the one from gtk-osx project
Some of these I don't remember so I will have to look into them. Others are because our build host is osx 10.5.x ||# xpra version||# gtk-osx version||# reason|| ||libjpeg-turbo-1.4.2.tar.gz||jpegsrc.v9a.tar.gz||better|| ||libxml2-2.9.2.tar.gz||libxml2-2.9.4.tar.gz||??|| ||orc-0.4.25.tar.xz||orc-0.4.22.tar.xz||newer|| ||gstreamer-1.8.3.tar.xz||gstreamer-1.4.3.tar.xz||newer|| ||gst-plugins-base-1.8.3.tar.xz||gst-plugins-base-1.4.3.tar.xz||newer|| ||gst-plugins-good-1.8.3.tar.xz||gst-plugins-good-1.4.3.tar.xz||newer|| ||gst-plugins-ugly-1.8.3.tar.xz||gst-plugins-ugly-1.4.3.tar.xz||newer|| ||gst-plugins-bad-1.8.3.tar.xz||gst-plugins-bad-1.4.3.tar.xz||newer|| ||glib-2.44.1.tar.xz||glib-2.48.tar.xz||compatibility|| ||libffi-3.0.13.tar.gz||libffi-3.2.1.tar.gz||compatibility|| ||gobject-introspection-1.44.0.tar.xz||gobject-introspection-1.48.0.tar.xz||compatibility|| ||pango-1.36.8.tar.xz||pango-1.38.1.tar.xz||??|| ||gdk-pixbuf-2.30.8.tar.xz||gdk-pixbuf-2.34.0.tar.xz||??|| ||gtk+-3.16.7.tar.xz||gtk+-3.20.3.tar.xz||newer|| ||pixman-0.32.6.tar.gz||pixman-0.34.0.tar.gz||??|| ||gtk-mac-integration-2.0.5.tar.xz||gtk-mac-integration-2.0.8.tar.xz||compatibility|| ||openssl-1.0.2h.tar.gz||openssl-1.0.2f.tar.gz||newer|| ||pygobject-3.16.2.tar.xz||pygobject-3.16.1.tar.xz||newer|| ||gmp-6.0.0.tar.bz2||gmp-5.0.5.tar.bz2||newer||
Please bump openssl: OpenSSL Fixes Over a Dozen Exploits, Including a High-Severity Vulnerability
Saw the openssl update: r13851 + r13852, added cryptography 1.5.1 in r13853.
For reference, I wanted up update and found some failures:
*** the following modules were not built *** [119/119]
pycairo-python2.6 pygtk gtk-mac-integration-python meta-gtk-osx-python
Why does it even try to build pycairo-python2.6?? It also rebuilt a lot of things I didn't think needed doing. Could this have been caused by a transient network failure to download our modules overrides? I've switched to https for the base moduleset URL since, and the problem seems to have gone away.
BTW, why are we still on 2.4.30? I see this bug has been fixed and looks relevant: improved fullscreen behaviouur: The attached patch improves the behaviour of fullscreen windows on El Capitan and perhaps other somewhat recent versions of OS X.
And again: openssl critical bug.
For 2.4 see Xpra-org/gtk-osx-build#2
Tracking the latest changes and recording why / how things work the way they do.
Related to Xpra-org/xpra#533 (original moduleset ticket), Xpra-org/gtk-osx-build#13 (64-bit), Xpra-org/xpra#641 (osx packaging) Recent osx tickets: Xpra-org/xpra#1271 (websocket client changes) Moduleset updates and build errors: Xpra-org/xpra#1007 and Xpra-org/xpra#544 (misc lib updates), Xpra-org/xpra#971 (build failures), r9116, .. Sound changes: Xpra-org/xpra#970 (switch to gstreamer 1.x) Xpra-org/xpra#1069 (gstreamer 1.6), Xpra-org/xpra#1168 (gstreamer 1.8)
Recent changes: r13715, r13714, r13713, r13712, r13711, r13710, r13709, r13708, r13707, r13706, r13705, r13704, r13703, r13702, r13701, r13700, r13699, r13698, r13697, r13696, r13695, r13694, r13693, r13692
Got some errors updating today:
(skipped)
Until we move to a clean 64-bit build env, we need this one to remain stable. (and we'll keep updating this one with minor stuff like ffmpeg and friends after then 1.0 release, and use trunk for the more bleeding edge stuff)