| rinigus | morning! I have managed now to build the port packages and make an image out of them using tbuilder. | 06:27 |
|---|---|---|
| rinigus | announcement at https://forum.sailfishos.org/t/automated-build-system-to-handle-multiple-packages/5828/11 | 06:28 |
| rinigus | anyone wishing to try? piggz or someone else? | 06:28 |
| piggz | rinigus: what should i try ... a build for pro1? | 07:10 |
| piggz | spiiroin: lets talk about mce :) | 07:11 |
| rinigus | piggz: could be good. for start just one-two packages and see if it works. for example, libhybris and having droid-hal packages used for it | 07:12 |
| rinigus | but I guess it will become more interesting if you work on something not supported by OBS | 07:12 |
| rinigus | as building something for aarch64 | 07:13 |
| piggz | rinigus: maybe in the future, if i get a pro1x to port ... but i dont ahve that ... and that will be 64 from start | 07:13 |
| piggz | havnt dont a 64bit pro1 tho | 07:13 |
| rinigus | piggz: Amazfish for aarch64? | 07:14 |
| rinigus | but indeed, it is most interesting to try when you actually need it | 07:15 |
| piggz | rinigus: ah, not only ports .. apps too? | 07:15 |
| rinigus | piggz: anything that needs multiple packages. I have now maps for aarch64 built that way | 07:16 |
| piggz | rinigus: for the KF5 packages i build on OBS ... i use the release tarballs from KDE + a spec uploaded to OBS ... can i do the same? | 08:32 |
| rinigus | piggz: yes, you can. just unpack tarball and add spec under `rpm` subfolder of it. | 08:33 |
| rinigus | next, add symlink to that spec in spec subfolder. | 08:34 |
| rinigus | this positioning is needed for tbuilder to figure out where are your sources and how to compile them | 08:34 |
| rinigus | sources are expected to be in the folder that is a level above the location where spec/abc.spec symlink points | 08:35 |
| rinigus | if you look into tama project then you will see how the symlinks are organized against sorces. note that sources can be almost anywhere on PC, as long as SDK can get there | 08:36 |
| rinigus | piggz: ^ | 08:36 |
| piggz | thx | 08:41 |
| T42 | <A_T_R> HABUILD_SDK [x00td] atr@atr-DL-G41MXE:~/hadk$ repo init -u git://github.com/mer-hybris/android.git -b hybris-17.1 | 09:57 |
| T42 | <A_T_R> bash: repo: command not found | 09:57 |
| T42 | <A_T_R> @A_T_R [HABUILD_SDK [x00td] atr@atr-DL-G41MXE:~/hadk$ …], what is the fix for this ..( i forgot how i was built hybris-16.0 before ) | 09:59 |
| rinigus | install repo | 10:00 |
| T42 | <A_T_R> sudo apt install repo | 10:01 |
| T42 | <A_T_R> Reading package lists... Done | 10:01 |
| T42 | <A_T_R> Building dependency tree | 10:01 |
| T42 | <A_T_R> Reading state information... Done | 10:01 |
| T42 | <A_T_R> E: Unable to locate package repo | 10:01 |
| T42 | <A_T_R> or i should initialise repo on host machine ? | 10:03 |
| rinigus | You can do it on the host or in SDK. I'm sure it was documented in porters guide | 10:09 |
| T42 | <zinstack625> Repo uses python3, you can either find an old version for python2 and use that anywhere you like, or do everything repo-related on host | 10:27 |
| T42 | <zinstack625> I prefer the latter, personally | 10:28 |
| T42 | <A_T_R> okey i will do it my host (focal ) | 10:31 |
| rinigus | I have an issue with droid-hal-xxx-img-boot building. it is summarized at https://github.com/sailfishos-sony-tama/tbuilder-project#issues-with-droid-hal-xxx-img-boot | 18:20 |
| rinigus | any ideas on how to work around it? so far, considering just removing old RPM before building new. | 18:20 |
| rinigus | or maybe should lock kernel-modules package using zypper? | 18:22 |
| rinigus | hmm, locking will not help as then droid-hal-version will need to have it removed. | 18:33 |
| deathmist_ | mal: have you experienced sensorfwd hanging the shutdown process as it doesn't listed to SIGTERM? I for example decided to add https://github.com/sailfishos-oneplus5/droid-config-cheeseburger/commit/3622495 to my port to avoid this extra wait | 19:29 |
| deathmist_ | s/listed/listen/ | 19:29 |
| mal | deathmist_: I don't remember seeing that but I haven't checked shutdown timings much | 19:29 |
| mal | deathmist_: I think I have seen on some devices at least that shutdown does take quite a long time but never checked why it happens | 19:31 |
| mal | deathmist_: sensorfw should be listening to SIGTERM https://git.sailfishos.org/mer-core/sensorfw/blob/master/sensord/main.cpp | 19:34 |
| T42 | <elros34> only on 4.0.1? Is there any chance you use busybox ash instead gnu-bash? I was reporting long time ago at #sailfishos some strange error that busybox caused qprocess hang (there was no finished signal). Maybe this is similar | 19:44 |
| deathmist_ | @elros34 I indeed noticed bash was completely absent from userspace | 20:22 |
| T42 | <elros34> since 4.0.1 busybox bash/ash, ps, pidof maybe more are installed by default | 20:23 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!