Le Fri, 28 Nov 2014 15:37:06 +0100, Zygmunt Krynicki <[email protected]> a écrit :
> Thanks for reporting this issue. > > We'll have a look at all the bluetooth related APIs and see what kind > of changes we can make quickly. > The goal of the package is to be a data source for "plainbox" and > "checkbox-ng" packages. Though I must admit we haven't been releasing > them to Debian quite that often recently. > > I'd like to understand how to address this bug in Debian better. > 1) Should we try to synchronize this package to the latest upstream > release (bringing in many additional fixes), I guess that may not be > allowed because of the freeze > 2) Should we try to disable/remove that particular test? > 3) Should we try something different? What? I see several issues here: 1) we are in freeze 2) 0.4-1 will not be part of the next release because it didn't migrate in time, so the fix should be applied for 0.3 and not 0.4, see: https://packages.qa.debian.org/p/plainbox-provider-checkbox.html I guess disabling the check (and removing the obexd-client dependency) could do it. But again that should be done against the 0.3 package. Otherwise fixing everything in 0.4 and removing 0.3 from testing could also be a solution (you need to set this bug as RC then) > > In addition, what is the timeline for any potential fixes? Days / > weeks? Deep freeze starts 5/12 (next monday) :/ > Thanks > ZK -- Mailing list: https://launchpad.net/~checkbox-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~checkbox-dev More help : https://help.launchpad.net/ListHelp
