Resolved on #ubuntu-mir... <mapreri> if you are fine with people uploading the package directly to the archive we can work it out, i.e. I upload a -2 as soon at 0.26.2-1 is uploaded, but then your next upload done through whatever CI should contain it. <alan_g> mapreri: that would work for me <mapreri> I have no idea how bileto (or whatever kind of CI/landing system) you are using work <mapreri> oh, great <mapreri> so, what would be the timing for 0.26.2 to land? :) <alan_g> mapreri: out of my hands, first QA need to approve and then someone needs to push to archive. But I'd guess the next day or two. <mapreri> that works just fine <mapreri> I'll arrange the -2 upload, will you please merge it in 0.26.3 in the meantime? <alan_g> AFAIK 0.26.3 doesn't exist (and likely won't). But I'll take care of it in that contingency.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675138 Title: Please transition to Boost 1.62 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1675138/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
