There are a few possibilities. One is that we try to force an update to 4.2 no matter when it's released, trying to push it into yakkety even after release-day. The rationale would be that the snapshot is anyway closer to 4.2 than anything, so it would be more like a 'bugfix' than a new feature-release. All features planned for 4.2 are already in so there should be no surprises here. We can of course also track the development of 4.2 and cherry-pick important fixes to our snapshot release, but I would really like to switch to 4.2 as soon as possible.
4.2 introduces no ABI breakages (at least not any obvious ones looking at the symbol files), so any step here should be relatively convenient as no rebuilds are needed (instead of zmqpp of course). It's backward compatible API-wise. Another possibility would be, of course, simply pushing a fork of zeromq3 to the archives that would be snapshot-based. This would mean we'd stay on 4.1.5 on yakkety for zeromq3 but some separate package, like, zeromq3-future (wrong name, but just an example) would provide the snapshot-based binaries instead. This way we would only have zmqpp as the consumer (and the only consumer of zmqpp is unity-scopes-api). This is much safer but very ugly from the archive perspective - but maybe this could be thought of as a better solution? It's also tough for me as this is the first situation like this we have to deal with. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1612240 Title: [FFe] Please upgrade zeromq3 and zmqpp to 4.1.2 git snapshot Status in zeromq3 package in Ubuntu: Incomplete Status in zmqpp package in Ubuntu: In Progress Bug description: Please update zmqpp to version 4.1.2 with the following patch that I proposed upstream (it got merged into their "develop" branch): https://github.com/zeromq/zmqpp/pull/167/files (alternatively, use master + my patch or develop branch of zmqpp). This will require the current git snapshot of the zmq library (which will be version 4.2 when it's released) - https://github.com/zeromq/libzmq All the above is needed to support the new USE_FD socket option, which will probably be critical for scopes as snaps. == Feature Freeze Exception details == These packages are required by the ongoing work of the unity scopes for snappy. Due to unrelated to zeromq issues (unity-scopes-api unit- test issues on arm64, possibly due to recent toolchain changes) we did not make it in time before Feature Freeze. The packages have been prepared and tested in: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-005/+packages?field.name_filter=&field.status_filter=published&field.series_filter=yakkety There is no ABI breakage in zeromq3 so no reverse-depends rebuilds are required. The zmqpp package does break ABI so a so bump and rebuild of rev-deps was needed, but the currently only consumer of the zmqpp packages is unity-scopes-api. The new release of zeromq3 is based on a git snapshot as a new stable release of this project is planned in the nearest future, so a bit too late for the current plans. Some reverse- depends of zeromq3 have been tested to work fine with the new package as is. We kindly request a FFe for this very particular case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1612240/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
