T42_ | <elros34> @b100dian looks like submodule sparse is empty and files are not copied thus build fails, maybe because of updated rpm or something related in sfos 4.6.x | 13:12 |
---|---|---|
mal | something odd is happening | 13:29 |
T42_ | <elros34> maybe _obs_build_project is false | 13:32 |
mal | testing | 13:37 |
mal | @elros34 that indeed fixed it | 13:40 |
T42_ | <elros34> where it is defined? I have no clue where to search for it | 13:41 |
mal | it's in project config, I added it to the global 4.6 project config now, testing again | 13:42 |
T42_ | <b100dian> You folks rock, I just re-triggered services and all went well apparently | 13:44 |
mal | works fine now | 13:44 |
mal | @elros34 thanks for figuring that out | 13:44 |
T42_ | <b100dian> +1 | 13:45 |
T42_ | <b100dian> now, between "have choice for profiled-settings needed by profiled: `profiled-settings-default` `sailfish-content-profiled-settings-default`" which one should I add to Prefers? | 13:46 |
T42_ | <elros34> maybe still missing some macros | 13:47 |
T42_ | <elros34> both packages are mentioned in 4.5 https://build.sailfishos.org/project/prjconf/sailfishos:4.5.0.18 | 13:48 |
mal | just a moment | 13:48 |
T42_ | <elros34> but not on 4.6 | 13:48 |
mal | fixing things | 13:48 |
mal | now those build | 13:49 |
mal | there was a bit too much project config cleanup done for 4.6 when adding it to community obs so some things got lost | 13:50 |
T42_ | <b100dian> Cleanup is good | 13:52 |
T42_ | <elros34> mal: do change latest to 4.6 in EA stage or only after full release is out? Currently it's prbably 4.5 that is why @b100dian had this issue only in testing build | 13:56 |
mal | latest will change to 4.6 only after full release is done | 13:58 |
mal | that is how it has always been | 13:58 |
T42_ | <b100dian> so I've jumped in too "Early". But it is good to know, a testing EA release should be possible | 14:00 |
mal | the main reason for the ea target on obs was to get chum build so there would be fewer update issue hopefully | 14:02 |
T42_ | <b100dian> I know, that's why I jumped to the conclusion I can update the port too | 14:05 |
T42_ | <adampigg> If anyone is doing any native port work, ive set up an org/project for managing all the projects, feel free to get involved https://github.com/sailfishos-native | 14:38 |
T42_ | <abranson> the face on that | 14:45 |
T42_ | <b100dian> both this and sailfishos-open need logos. A sailfish and a pinguin, a sailfish and a gnu head... | 14:55 |
T42_ | <b100dian> mal: next up is mic complaining that https://repo.sailfishos.org/obs/nemo:/testing:/hw:/common/sailfishos_4.6.0.11_aarch64/repodata/repomd.xml does not exist. Should the new RELEASE export be only 4.6? | 14:57 |
mal | I haven't added that repo yet | 14:58 |
mal | usually development testing is supposed to happen in devel project not testing :) | 14:59 |
T42_ | <b100dian> haha ok | 14:59 |
mal | we haven't actually though yet how to handle the community-adaptation package for 4.6 | 15:00 |
mal | I added that target now, but still usually we don't add ea targets to testing | 15:02 |
T42_ | <b100dian> no worries, I;ll keep an eye on what's announced when the time comes. | 15:02 |
T42_ | <b100dian> That's very kind. Let's hope there are no multiple EA releases | 15:03 |
T42_ | <adampigg> i forked one of your repos into there :) (re @abranson: the face on that) | 15:26 |
T42_ | <adampigg> mal: hows new kernel-headers? | 15:26 |
mal | @adampigg it's in obs already | 15:30 |
T42_ | <adampigg> mal: looks like 3.18 .. need newer for ell/ofono https://build.sailfishos.org/package/show/nemo:devel:hw:native-common/kernel-headers | 15:31 |
mal | it's not tagged | 15:32 |
mal | it's really 5.4.276 | 15:32 |
mal | maybe we should have that in that native project so we can tag it | 15:32 |
T42_ | <adampigg> feel free | 15:45 |
T42_ | <adampigg> mal: gst plugins with v4l need re-done to point to new monorepo | 16:07 |
mal | yeah | 16:10 |
mal | @adampigg simple rebase worked conflicts, triggered build now | 16:15 |
mal | *without conflicts | 16:16 |
T42_ | <b100dian> So, the reason I tried to re-make the image for tucana is because the devicelock does not work in testing. I have backtracked this to an error like "encpartition[1562]: Device /dev/sailfish/home does not exist or access denied" | 19:28 |
T42_ | <b100dian> and comparing to the devel build and the sake build(s), there is "pluginName=/usr/lib64/qt5/plugins/devicelock/encpartition" inside /usr/share/lipstick/devicelock/devicelock.conf (whereas otherwise it's encsfa[-fpd] | 19:29 |
T42_ | <b100dian> I discovered that some years ago I commented out Requires: jolla-devicelock-daemon-encsfa from adaptation in tucana | 19:30 |
T42_ | <b100dian> Without a proper comment, something like "fixing boot" | 19:30 |
T42_ | <b100dian> However, if I put it back I cannot install the adaptation package, "The following package update will NOT be installed" | 19:32 |
T42_ | <b100dian> And even mic complains: requires 'patterns-sailfish-device-adaptation-tucana', but this requirement cannot be provided | 19:33 |
T42_ | <b100dian> Build link https://github.com/sailfishos-on-tucana/Readme/actions/runs/9236974196/job/25414741738#step:4:177 | 19:33 |
T42_ | <b100dian> I do not understand how this works for sake, how this presumably works on devel for tucana (it has encsfa-fpd binary plugin). | 19:35 |
T42_ | <b100dian> Anyone rpm-experienced what to query? | 19:35 |
T42_ | <b100dian> Hmm maybe rinigus explains in this commit, it should be commented out if you're using fpd, let me check https://github.com/sailfishos-sony-tama/droid-config-sony-tama-pie/commit/c65ec781ab4adf0deca51375d8abd336cbfe8e68 | 20:11 |
mal | yes, jolla-devicelock-daemon-encsfa is used when there is no fingerpring support | 20:29 |
T42_ | <b100dian> Yes, the mic build worked after something similar | 20:39 |
T42_ | <b100dian> It was a tad more complicated to update, but I assume a version —dup will not pose the same questions | 20:40 |
T42_ | <b100dian> The only problem now is that it offers to set up fingerprint sensor at initial setup | 20:40 |
T42_ | <b100dian> and that doesn't work for under display. Too bad the new community phone doesn't have one, there would have been light circles in there, wherever dconf says ;) | 20:41 |
mal | @b100dian about display cutouts, add file /dconf/db/vendor.d/silica-cutouts.txt with content | 22:05 |
mal | [desktop/sailfish/silica] | 22:05 |
mal | cutouts = [[x, y, w, h]] | 22:05 |
mal | add suitable numbers to that last line | 22:06 |
T42_ | <b100dian> wow, dconf update and magic happens. Thank you! | 22:17 |
T42_ | <b100dian> That is an interesting design around cutouts | 22:17 |
mal | the whole idea of cutouts on devices is so stupid :) | 22:20 |
mal | only makes things complicated with no real benefits | 22:21 |
mal | same with the recent trend of not adding notification led on devices | 22:22 |
T42_ | <b100dian> I know:( | 22:23 |
mal | same with rounded corners in viewable display area | 22:23 |
T42_ | <b100dian> yeah, let's cram that top bar even more, we don't need them pixels | 22:24 |
T42_ | <b100dian> there are already notched laptops | 22:25 |
mal | if they would just have small amount of non-display area at the top and bottom then camera, led and other stuff would fix just fine, and device would still look fine | 22:25 |
mal | really? even on laptops? that's even more stupid | 22:25 |
T42_ | <b100dian> wondering when they'll get rounded corners :)) | 22:25 |
mal | hehe | 22:25 |
T42_ | <b100dian> There are even under-display cameras today, if you really want to show off your thin bezels. | 22:27 |
T42_ | <b100dian> You don't have to leave with a whole in the display the whole time, only when "needed". | 22:27 |
mal | yeah. but why are thin bezels so important for some people? never understood that, like a phone is a phone, quite irrelevant how it looks :) | 22:28 |
T42_ | <b100dian> It's akin to people wanting small cars, but spacious | 22:42 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!