On 2015-04-29 18:45:56, Apollon Oikonomopoulos wrote: > Hi, > > On 16:37 Wed 29 Apr , Adam D. Barratt wrote: > > Unstable and stable currently have the same version of ganeti; as a > > rule of > > thumb, unless there's a really good reason then we always want fixes to have > > been proven in unstable before being backported to stable - that applies for > > small fixes, but certainly for a change of the size proposed. What's the > > plan for getting unstable updated? > > I originally intended to upload 2.12.3 to unstable today and then > prepare 2.12.3-1~deb8u1, precisely to get more testing. Unfortunately, > unstable moved on to GHC 7.8 right after the freeze ended, which > introduced some backwards-incompatible changes causing ganeti 2.12 to > FTBFS on sid. I know upstream is working on GHC 7.8 support, but it is > not yet clear how long it will take and whether the fix will target 2.12 > or a later stable release. Not the best possible situation I have to > admit. FYI, upstream seems to have fixed this on the 2.15 branch, and manually applying some of the changed done by Niklas (search on git.ganeti.org for "7.8", see especially commits b78a2c3013c16395c48e055de82c4f93d9b41c38, 083776b9dbd7e704357841e6a8a4fce6802199fc and 1ad14f38083d7d7702154f791070a92e241320e0) gets the build progressing quite far, until the lens 4.4 changes which removed defaultRules (see https://code.google.com/p/ganeti/issues/detail?id=981). Applying on top commits cfd9c8a82550df4e29ebeee2158f1d7fb864d531 and 14a85a6fa426e3088423923094cd6d574fe91d3f results in the build failing only due to -Werror, which can be patched out (and there are fixes for that as well in git). So the upstream git tree contains all changes needed, but spread around different branches. It should be easy for upstream to make a new 2.12 release, but it's even more simple for Debian to patch 2.12 in-place by cherry-picking these patches, they are rather trivial. I make my tests based on 2.12.0 source as retrieved by apt-get source. Not sure if 2.12.3 contains further fixes or changes that would make this more difficult. Just FYI :) regards, iustin
Attachment:
signature.asc
Description: Digital signature