Chum issues

[rinigus]

There are few issues in Chum:

• in SPEC, I would suggest to fix URL. Right now it points to https://github.com/harbour-sailfishos/sfos-hydrogen . With URL fixed, Chum GUI would be able to show opened issues, releases and other info

• is there a reason a file "release-sfos-0.4.1.zip" is bundled? All should be possible to pull via _service, or do I miss something?

• more serious issue preventing the build is "have choice for libKF5Archive.so.5()(64bit) needed by nemo-qml-plugin-filemanager: libKF5Archive5 libkf5archive". This looks to be caused by https://build.sailfishos.org/package/show/sailfishos:chum:testing/karchive - @piggz, does it interfere with SFOS provided package? In this case we should probably disable export of symbols or make one of them preferred one on repo level.

[piggz]

Yeah, ive seen the karchive issue before but never got around to fixing.... i imported karchive many years ago for amazfish, though i cant be sure which package came first, mine of Jollas .... in any case, maybe I should investigate using the jolla version and drop the one from chum

[nephros]

@rinigus do you have a recipe for a _service file which can pull from a GH action artifact?

We have tried and not succeeded to use the file download service.

[rinigus]

do you have a recipe for a _service file which can pull from a GH action artifact?

I didn't realize it is an artifact :( . no, I am not aware of it

[b100dian]

Sorry I'm late seeing this. For the artifact part I asked this maybe tar_git could use the fileserver URL. For the project URL: Thanks nephros for fixing it. For the libKF5Archive error, thanks piggz for fixing it!

[b100dian]

Just a note about the artifact: @rinigus this is the app I initially built nodejs on OBS for. To make the npm/yarn build run without network connection, it required a 200+MiB yarn.cache file as seen here. Having the build partially on github and using that output as a 5MiB artifact is no-brainer compared to that.

[rinigus]

Sounds reasonable to me. We have to make exceptions for a good cause and I think it is a great example of it.

[b100dian]

Sounds reasonable to me. We have to make exceptions for a good cause and I think it is a great example of it.

Thank you!

[b100dian]

This is slightly improved by using an actual URL of the artifact as shown here and adding <service name="download_files"/> after tar_git in _service. Ideally, something like this node modules _service would work better.

[b100dian]

Also, the node_modules service is not directly usable for yarn, as yarn has its own yaml lockfile and needs conversion to package-lock.json such as https://github.com/imsnif/synp. I am closing this for now, but please re-open if any other ideas come aboard..