These are chat archives for abranson/rockpool

19th
May 2017
Andrew Branson
@abranson
May 19 2017 06:59 UTC
about the Jolla 1 and Bluez5 - there are a couple of showstoppers. The kernel's too old - patches exist but it's huge and would need a lot of testing. Then they'd have to pay to get the phone recertified. That's crazy for a phone that hasn't been sold for over a year.
https://git.merproject.org/mer-core/obexd master is the latest. The RPM spec Version tag is overwritten with the git tag name by OBS during build. Most of them contain zeroes, but if there's a dependency check in another package, it'll often be set to at least that so that local builds will satisfy them
ruff
@rufferson
May 19 2017 07:47 UTC
Ah, ok, I just did local build to test first modifications. Will then update version tag as well to avoid rpm conflicts
Andrew Branson
@abranson
May 19 2017 08:06 UTC
yep. or just use --force
that's quite handy if you want version --dup to revert everything when you're done
ruff
@rufferson
May 19 2017 08:12 UTC
yea, mainly I need to be sure what I built corresponds to what was on the phone so that I won't break package compatibility (api/abi). First trying to backport latest obex profiles from bluez5 and then will see what misses. That should allow easier forward-porting then
Andrew Branson
@abranson
May 19 2017 08:14 UTC
The tricky part is knowing if the git is much further ahead than the release version. Compare the last tag to the version in the repo for that.
Sailfish is usually a couple of versions ahead in the devel branch.
but some packages don't change for a long time
ruff
@rufferson
May 19 2017 08:15 UTC
yes, noticed that for telepathy packages. But obex looks quite steady. Was jsut surprised when attempted to install freshly built rpm :)
Andrew Branson
@abranson
May 19 2017 08:16 UTC
Yes, I'm surprised at that as the bluez5 isn't quite done yet. maybe that part is...