Tested:
xenial: 0.26.3+16.04.20170605-0ubuntu1
yakkety: 0.26.3+16.10.20170605-0ubuntu1
zesty: 0.26.3+17.04.20170605-0ubuntu1
All is fine.
** Tags removed: verification-needed
** Tags added: verification-done
** Summary changed:
- Please transition to Boost 1.62
+ Please transition to latest Boo
Hello Balint, or anyone else affected,
Accepted mir into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mir/0.26.3+17.04.20170605-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
Hello Balint, or anyone else affected,
Accepted mir into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mir/0.26.3+16.04.20170605-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
h
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783
--
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
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2791
--
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 tra
** Changed in: mir/0.26
Status: Fix Committed => Fix Released
--
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
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-artful-2778
--
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
The package does not actually transition to Boost 1.62 in Xenial because
this Boost version is not present there, but mirtest-dev properly
depends on unversioned Boost development libraries.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notificati
Fixed in xenial-proposed, verified in 0.26.3+16.04.20170510-0ubuntu1.
--
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
Hello Balint, or anyone else affected,
Accepted mir into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mir/0.26.3+16.04.20170510-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
h
** Also affects: mir (Ubuntu Xenial)
Importance: Undecided
Status: New
--
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
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2735
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736
--
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 transi
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2683
--
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 t
Only problem now is that zesty contains different code to what's in
lp:mir/ubuntu. We may need to deal with minor conflicts at the next Mir
release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/167513
** Branch linked: lp:mir/0.26
--
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/m
Fix committed to lp:mir/0.26 at revision 4051, scheduled for release in
Mir 0.26.3 (if that gets released at all)
** Changed in: mir/0.26
Status: New => Fix Committed
** Changed in: mir/0.26
Assignee: (unassigned) => Mattia Rizzolo (mapreri)
** Changed in: mir/0.26
Importance: Und
This bug was fixed in the package mir - 0.26.2+17.04.20170322.1-0ubuntu2
---
mir (0.26.2+17.04.20170322.1-0ubuntu2) zesty; urgency=medium
[ Mattia Rizzolo ]
* Patch the code to use unversioned runtime boost libraries (LP: #1675138).
-- Gianfranco Costamagna Fri, 24 Mar 2017
22
Cool. That was the plan. I just didn't know where it was.
--
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:
FWIW, the fix for this bug in the -2 upload, waiting in the unapproved
queue, until somebody from the release team approves it… (and it's been
there for nearly 3 days already…).
** Changed in: mir (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you
Ignore comment #16 as it's not relevant to this bug. The fix for this
bug is NOT in Mir 0.26 or Ubuntu branches.
--
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 Boo
** Changed in: mir (Ubuntu)
Status: Fix Committed => Triaged
** Changed in: mir (Ubuntu)
Assignee: Mattia Rizzolo (mapreri) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16
** Changed in: mir (Ubuntu)
Status: Triaged => Fix Committed
--
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 b
Mir 0.26.2 has passed QA and should be landing soon (as soon as I can
find someone to publish it).
--
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 ma
** Tags added: packaging
--
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/+b
Resolved on #ubuntu-mir...
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.
mapreri: that would work for me
I have no idea how
@Mattia: From the linked bug it seems reverse build dependencies needed those
libs listed. I haven't tried changing those to unversioned depends, because IMO
at this stage a safe fix like this one is more appropriate.
The fix for both other transitioning packages are on their way, no need to
rem
I'd really appreciate if it could be scheduled for 0.26.2, actually.
It's a packaging-only change, making progress on a transition. I'm not
involved in this boost transition myself, but I know I hate any kind of
delay. Besides, to me it looks like mir is the last actionable package
on the list be
That's on trunk right now so we're looking at next cycle: 1.0
If it's safe enough for zesty however we could try scheduling it for 0.26.3
which does not have a timeframe right now. We are working on releasing 0.26.2
at present.
** Also affects: mir/0.26
Importance: Undecided
Status: Ne
Thank you for merging!
What is the expected time frame for the next upload to the archive,
containing this change?
--
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
** Changed in: mir
Importance: Medium => High
--
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://b
Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0
** Changed in: mir
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Also affects: mir
Importance: Undecided
Status: New
** Changed in: mir
Assignee: (unassigned) => Mattia Rizzolo (mapreri)
** Changed in: mir
Milestone: None => 1.0.0
** Changed in: mir (Ubuntu)
Importance: Undecided => High
** Changed in: mir
Importance: Undecided =>
** Branch linked: lp:~mapreri/mir/1675138-boost-dep
--
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:
ok, that doesn't explain why it can't be unversioned.
Then I noticed that it depends on the library package instead of the
-dev package (i.e. it's not explicitly pulling in the package containing
the relevant .so file), so it seems even more broken to me.
Really that should be 'libboost-filesyste
Let me try once more: LP: #1633537
--
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.
The link will work: https://bugs.launchpad.net/mir/+bug/1633537 :-)
--
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 b
Those were added in #1633537
--
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/ub
in LP:#1633537
--
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/ubuntu/+source/m
why can't mir depend on unversioned boost?
--
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.la
The attachment "debdiff performing the transition" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patc
fixed my email address in the patch
** Patch added: "debdiff performing the transition"
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1675138/+attachment/4842635/+files/mir_0.26.1+17.04.20170209.1-0ubuntu2.patch
--
You received this bug notification because you are a member of Ubuntu
Bu
41 matches
Mail list logo
