I noticed that upload and I'm curious about the motivation. It's really
early in the cycle and we will get bluez updates and time for archive
rebuilds later on so I guess the aim is not to get packages built with a
new LTO by release time. Did we have a buggy LTO version in the archive
and are we rebuilding things with a fixed version? Which packages do
need a rebuild and do we need to organize the rebuilds with the owning
teams?
Cheers,
Sebastien Bacher
Le 13/05/2022 à 21:56, Brian Murray a écrit :
> bluez (5.64-0ubuntu2) kinetic; urgency=medium
>
> * No change rebuild to pickup a new version of LTO.
>
> Date: Fri, 13 May 2022 12:36:19 -0700
> Changed-By: Brian Murray <brian@ubuntu.com>
> Maintainer: Ubuntu Bluetooth team <ubuntu-bluetooth@lists.ubuntu.com>
> https://launchpad.net/ubuntu/+source/bluez/5.64-0ubuntu2
>
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
