Bug 9188

Summary: [meta-swupd] Remove hard-coded paths from swupd-client
Product: [Build System, Metadata & Runtime] Other YP Layers Reporter: Joshua Lock <joshuagloe>
Component: meta-swupdAssignee: Patrick Ohly <patrick.ohly>
Status: RESOLVED OBSOLETE QA Contact:
Severity: normal    
Priority: Undecided CC: igor.stoppa, patrick.ohly, poky.bs.watcher, poky.watcher, richard.purdie
Version: 2.1   
Target Milestone: Future   
Hardware: x86   
OS: Multiple   
URL: https://github.com/clearlinux/swupd-client/issues/208
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Joshua Lock 2016-03-01 09:28:48 UTC
swupd assumes Clear Linux as a host OS and hard-codes several paths to directories, programs and configuration files on Clear.

Create patches to make these paths configurable and submit them upstream.
Comment 1 Igor Stoppa 2016-05-11 11:11:30 UTC
Shouldn't this be a bug against swupd?
It's not clear to me if it intentionally assumes CL, but I think it shouldn't.
Comment 2 Joshua Lock 2016-05-11 18:42:24 UTC
(In reply to comment #1)
> Shouldn't this be a bug against swupd?
> It's not clear to me if it intentionally assumes CL, but I think it
> shouldn't.

Yes, it should. IIRC there wasn't a public bug tracker at the time so this seemed a good place to keep track.

Upstream bug filed: https://github.com/clearlinux/swupd-client/issues/67
Comment 3 Joshua Lock 2016-05-16 10:16:13 UTC
Patch submitted upstream:

https://github.com/clearlinux/swupd-client/pull/71
Comment 4 Ross Burton 2017-07-05 10:52:41 UTC
Waiting For Upstream status is being removed, changing to Accepted.
Comment 5 Patrick Ohly 2017-09-21 07:11:10 UTC
This was partly addressed. Upstream is tracking the rest at https://github.com/clearlinux/swupd-client/issues/208
Comment 6 Richard Purdie 2018-10-11 15:23:34 UTC
Upstream swupd has changed a lot and integration with the Yocto Project would be tricky and need rework to the layer. Closing this as obsolete since any new integration would need rework and have its own issues.