This bug was fixed in the package bolt - 0.5-0ubuntu0.18.04.1
---
bolt (0.5-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream version (lp: #1798014)
* debian/control:
- update the meson requirement according to the upstream changes
* debian/rules:
- drop use of the
I've tested the SRU on bionic and authorized a device successfully.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Hello Mario, or anyone else affected,
Accepted bolt into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/bolt/0.5-0ubuntu0.18.04.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
@Robie, I've reuploaded without the -Ddb-path use, could you have
another look?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798014
Title:
[sru] backport 0.5 release to bionic
To manage notificat
@Robie, right, sorry I ment to drop that option and even listed that as a
change in the changelog
"+- drop use of the -Ddb-path option which is deprecated now"
I've built the new version locally and in a ppa and verified that the
path is still the same so that option isn't needed/doesn't need
Thanks.
Reviewing Sebastien's, I don't see the use of -Ddb-path updated, but
upstream states that it is deprecated in
https://gitlab.freedesktop.org/bolt/bolt/merge_requests/113/diffs.
Deprecation rather than removal might be OK, but the upstream diff
suggests to me that -Ddb-path is now ignored e
Upstream release notes including notes for packagers are at:
https://gitlab.freedesktop.org/bolt/bolt/tags - it seems that there are
a number of things to consider and might be especially important for an
SRU backport.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Sebastien's. He took out a few of the "unnecessary" changes in doing the
backport.
On Wed, Oct 31, 2018 at 12:01 PM Robie Basak <1798...@bugs.launchpad.net>
wrote:
> Here's the diff between the two versions in the queue:
> http://paste.ubuntu.com/p/tKRSR5Yq7s/
>
> --
> You received this bug noti
It looks like Mario and Sebastien have different competing updates in
the queue. Which one do you want?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798014
Title:
[sru] backport 0.5 release to bio
Here's the diff between the two versions in the queue:
http://paste.ubuntu.com/p/tKRSR5Yq7s/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798014
Title:
[sru] backport 0.5 release to bionic
To man
** Description changed:
[Impact]
- * The bolt 0.4 release introduced support for Thunderbolt force power, but
it has been reported that this conflicts with the fwupd force power support.
This is a regression as a result of 0.4 being backported to bionic.
- * Bolt 0.5 will work together with
I reproduced a failure in fwupd 1.0.6 as well caused by bolt 0.4. it's
because bolt didn't know fwupd was performing an update and turned off
thunderbolt during the update.
In 1.0.9 they work together to prevent this.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: bolt (Ubuntu Bionic)
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798014
Title:
[sru] backport 0.5 release to bionic
To manage notifications about t
Does it really lead to a regression-update? In
https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1795864/comments/7
you wrote "this can cause problems in bionic too if on fwupd 1.0.9 or
later" or currently bionic/bionic-updates have fwupd 1.0.6, so there is
no regression until 1.0.9 lands (which
Since backporting 0.4 lead to a regression, adding regression-update to
this bug (Although it's a little confusing since this bug "resolves"
that regression).
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Since the backport of bolt 0.4 (with force power support that conflicted
with fwupd) is what introduced the need for this SRU adjusting the
importance.
** Changed in: bolt (Ubuntu Bionic)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubunt
The fwupd 1.0.9 SRU bug is here: #1791999
SRU team:
Ideally, please process these at the same time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798014
Title:
[sru] backport 0.5 release to bionic
** Changed in: bolt (Ubuntu)
Status: New => In Progress
** Tags added: bionic
** Changed in: bolt (Ubuntu)
Status: In Progress => Fix Released
** Also affects: bolt (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: bolt (Ubuntu Bionic)
Status: New =
18 matches
Mail list logo