| T42_ | <TheVancedGamer> oh no you don't (re @ššš ŠPŠ£ŠŠŠ_ŠHŠŠ0MCTV_18+: ) | 04:52 |
|---|---|---|
| piggz | rinigus: ping | 08:07 |
| rinigus | piggz: rather busy. what about pong tonight? | 08:19 |
| piggz | rinigus: its ok, i kinda figured t ot from your repos .. do i have to change inirtd if the volume is changed .... yes .... why the change? | 08:21 |
| rinigus | piggz: bg is https://forum.sailfishos.org/t/allow-to-decouple-luks-password-from-used-security-code | 08:56 |
| piggz | rinigus: ok, i understand ... one Q .. if using home_open as the volume, does the stock encryption still work? | 09:36 |
| rinigus | piggz: no, it doesn't | 09:44 |
| rinigus | have to choose the sides over this one :) | 09:45 |
| piggz | rinigus: is it ready to add to my build? | 09:46 |
| rinigus | piggz: I think you could test it. what works is wizard to set it up, unlocking on boot. settings app+service are in works. hwcrypt is not hooked to wizard and settings yet - so you have to use plain passwords. | 09:48 |
| rinigus | for that, add https://github.com/sailfishos-open/sailfish-device-encryption-community to config of device (used to be patterns) | 09:49 |
| piggz | rinigus: ok ... plan is, i'll build stock -devel, check ti works, promote to testing, then break devel! | 09:49 |
| rinigus | sure. sticky point is that users will have to reflash the device. its to get home->home_open as well as initialization of encryption | 09:50 |
| rinigus | but this inconvenience is something that will have to be taken. | 09:51 |
| piggz | yeah | 09:51 |
| rinigus | anyway, dependencies are all in devel for tama:aosp10 build. should be enough to copy packages from there. later we should probably move it to devel:common or similar | 09:52 |
| rinigus | same for fpd - parts that can be shared | 09:53 |
| poetaster | don't forget to let us opt out of LUKS altogether. | 09:56 |
| piggz | poetaster: are you ready to test volla build? | 09:57 |
| poetaster | sure. | 09:57 |
| T42_ | <eugenio_g7> wouldn't be good to rename the lvm LV only with open device encryption? Maybe the wizard could take that in account | 09:57 |
| rinigus | poetaster: opting out is there already | 10:46 |
| rinigus | but it still requires reformatting of home_open to make sure that you can switch between configs. | 10:47 |
| T42_ | <eugenio_g7> hmm why? Wouldn't renaming the LV, adding a new slot with the new passphrase and then killing the old pin-only slot be enough? | 10:56 |
| poetaster | rinigus: cool. | 11:00 |
| piggz | poetaster: https://gitlab.com/sailfishos-porters-ci/yggdrasil-ci/-/jobs/1579744269 | 11:54 |
| poetaster | piggz: downloading | 12:01 |
| piggz | poetaster: flash on v10 from fastboot mode using suppled script | 12:02 |
| poetaster | ah, easy peasy. | 12:02 |
| poetaster | piggz: ok! cool, install ran ... | 12:16 |
| piggz | question is, will it get to UI.... | 12:17 |
| poetaster | piggz: I'm setting up Jolla account ;) | 12:19 |
| piggz | gr8 | 12:19 |
| poetaster | It had a brief 'black' moment just before the wlan prompt came up. 6/7 seconds. | 12:19 |
| piggz | yeah, i noticed that too | 12:20 |
| poetaster | piggz: should I try the usual ? | 12:20 |
| piggz | poetaster: the usual? | 12:20 |
| piggz | im relatively confident everything is working | 12:20 |
| poetaster | run doom until the device crashes! | 12:20 |
| poetaster | ok, I'll just play doom, then. | 12:20 |
| piggz | sure, ive not had any crashes ... kernel seems way better than old port | 12:21 |
| poetaster | piggz: the old port is also, just fine. I mean, for my purposes. Just browser suckage. | 12:23 |
| poetaster | Ok, I'll screw about a bit.... | 12:24 |
| poetaster | looking good! | 12:24 |
| itex | what device are you porting? | 12:24 |
| poetaster | piggz has 4.2 running volla/gigaset GS290 | 12:24 |
| itex | i see | 12:25 |
| piggz | well, i currently flashed back to 4.1 to test the image ... but 4.2 installs ok on it | 12:25 |
| poetaster | Ah, ok. Sorry, this is a 4.1. | 12:26 |
| poetaster | Looking good! | 12:26 |
| itex | how hard is it to port sailfish to an android device, I am thinking of trying it out, but that pdf explaining how to do it is kinda scary | 12:27 |
| piggz | itex: trust the pdf :) | 12:40 |
| piggz | mal: should I add my BT bug to FSO? | 12:50 |
| itex | :))) alright | 13:07 |
| piggz | Keto: could you check if yggdrasil has store access pls | 13:27 |
| poetaster | piggz: you mean the 4.1 image? I've got store installs/open repos installs, and a bunch of work ahead. | 13:39 |
| poetaster | the pace is accelerating. | 13:41 |
| piggz | wdym | 13:41 |
| poetaster | piggz: 1, did you mean does your 4.1 ygg image, which I just installed have store access (sure does). | 14:02 |
| poetaster | piggz: 2. I have a lot of packaging work to do, and with 4.2 out the pressure is there to get clean builds for those users. all my stuff 'works' on 3.4 | 14:03 |
| poetaster | piggz: 2.b but somethings are bust on aarch | 14:03 |
| poetaster | and of course, chum causing me to reconsider all my builds with dependancies. | 14:04 |
| piggz | ok ... yeah, youre right, store access looks ok just double checking as i couldnt be sure if i ever requested it! | 14:05 |
| piggz | and yeah, use chum to simplify things ... considering moving amazfish to chum, instead of just its deps ... user asked me for a 3.4 version a few days ag | 14:06 |
| poetaster | heh:) sadly, showed me that a number of my packages need work there AND for chum :-( | 14:06 |
| poetaster | AND, I'd like to get Jolla to 1. put ffmpeg-tools back in (with 4.3) AND, I'd like to convince jolla to permit some stuff they already pkg. | 14:07 |
| poetaster | piggz: there is a quandry with Chum. For instance, if I build using BuildRequires python3-imaging that won't work for 3.4 | 14:13 |
| poetaster | piggz: I mean depending on the jolla pkgs. | 14:13 |
| mal | poetaster: what are you saying about ffmpeg-tools package? | 14:14 |
| poetaster | mal: it was 'installed' by default in 3.4. It is not as of 4.x | 14:15 |
| poetaster | mal: vige had advised I 'simply depend on it' and it went away. broke Audioworks/Videoworks. | 14:15 |
| poetaster | mal: Audioworks was actually in store. | 14:16 |
| piggz | poetaster: why does BuildRequires pythin3-imaging break? | 14:16 |
| poetaster | piggz: because it's not available in a usable version in 3.4. In 3.4 I'm shipping the library along. | 14:17 |
| mal | poetaster: wondering why it was installed before, I think nothing requires it by default and we usually don't install unneeded packages | 14:17 |
| piggz | poetaster: ok, what about something like https://github.com/piggz/harbour-amazfish/blob/master/rpm/harbour-amazfish.spec#L49 | 14:17 |
| poetaster | mal: vige mentioned the web browser at the time. | 14:17 |
| mal | ok | 14:19 |
| poetaster | piggz: I've got some good stuff from rinigus pure-maps, but I still need to rebuild all the pro files, split into subdir projects, etc. | 14:20 |
| poetaster | https://github.com/rinigus/pure-maps/blob/master/rpm/harbour-pure-maps.spec#L125 | 14:20 |
| poetaster | piggz: but %if 0%{?kf5calendarcore_found:1} is nice to know. thanks. | 14:21 |
| mal | does pure-maps have any gps logging support, I think couldn't find any | 14:21 |
| poetaster | mal: don't recall, sec. | 14:22 |
| poetaster | mal: doesn't look like it. | 14:23 |
| mal | ok, I have used another app for logging because it didn't have support | 14:27 |
| Keto | piggz: yes it does | 14:40 |
| Keto | re yggdrasil store configuration | 14:41 |
| rinigus | mal: I am avoiding adding gps tracking to pure maps as I consider it a feature creep. We have Kuri for logging and maybe even some more apps. | 14:53 |
| rinigus | Although, in corresponding issue, I agreed to accept PR with tracking if someone submits working code for it. | 14:57 |
| mal | rinigus: ok, I have used modrana for logging, need to check those others | 14:57 |
| rinigus | Kuri was designed for it | 14:58 |
| mal | ok, at least modrana has some annoying things in that so might look for different solution | 15:01 |
| piggz | Keto: thx | 15:24 |
| poetaster | all: this #%if "%{sailfishos_version}" < "40000" is frowned upon I would guess. | 15:57 |
| poetaster | shit. I'm just being too lazy. | 15:57 |
| piggz | poetaster: not really, thats why we added it, so that its like other distros | 16:01 |
| poetaster | piggz: ok, so it's not 'verboten'. ok. | 16:02 |
| poetaster | all: I'm sorta 'stuck' because I don't know whether to 'lean' on jolla. I'd 'like' to use https://github.com/sailfishos/python3-imaging/ | 16:05 |
| poetaster | all: under the assumption that it is there because jolla believes that particular version is 'viable' | 16:05 |
| poetaster | all: hence, I should do a subdirs build that uses 'that' repo to build PIL and then use copy in the spec to get it into application library context. | 16:06 |
| poetaster | all: and so make the build chum/openrepo and jolla store compatible. | 16:06 |
| poetaster | all: but, do i trust them? or just use my 'know usable build' copy the binaries. this chum will not like. because it's ubly. even if it works. | 16:07 |
| poetaster | 'known usable' build, meaning a simple 'copy' of python and c for all platforms that I 'know works'. | 16:08 |
| poetaster | ergh. sorry for the brain dump. | 16:15 |
| piggz | mal: a few packages in native-common still point to git.sailfishos.org ... will try to fix | 17:12 |
| mal | ok | 17:27 |
| poetaster | all: I also hesitate because the PIL repo is 144 mb in size. the product that I use is 7mb in size. save the whales. | 18:03 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!