Tuesday, 2021-07-20

T42<b100dian> However the number of packages I have to add to OBS is getting out of hand, I might have added something that pulled the whole world:-S00:00
T42<b100dian> So I don't know if the script creates an image in the end00:03
T42<b100dian> So I wasn't using the nemo:devel:hw:common - I added it but still got unresolvable for ofono-ril-binder-plugin (needs libgbinder-radio>1.4.1), so I may still need to build a bunch of these myself00:56
T42<adampigg> set version to 1.2.3 instead of HEAD for ofono-ril-binder-plugin (re @b100dian: So I wasn't using th...)06:42
T42<edp_17> Hi all! I am upgrading my treltexx (Galexy Note4) port to 4.1 and following the new HADK.07:31
T42<edp_17> I've downloaded the ubuntu chroot that provides the older OpenJDK but cannot enter into it. I get this error: https://paste.ubuntu.com/p/w9KQDSgRgr/07:33
T42<edp_17> (When I downloaded the newer ubuntu chroot, that worked, but I was not sure that would be correct for my old device, so downloaded the older chroot.)07:34
T42<edp_17> Can I use the newer ubuntu tarball? If not, how can I fix the error?07:35
T42<b100dian> Thanks piggz - do you also happen to know about "nothing provides libncicore.so.1()(64bit) needed by nfcd-binder-plugin-1.1.8-1.7.4.jolla.aarch64" ?08:43
T42<b100dian> @edp_17 use sudo?08:43
piggz@b100dian not sure about that one, 1.1.8 builds here https://build.merproject.org/package/show/nemo:devel:hw:fxtec:t5/nfcd-binder-plugin08:45
T42<edp_17> @b100dian : The HADK doesn't say that and I never used sudo to enter into the HABUILD.08:46
T42<b100dian> @edp_17 you're right, I don't use either, sorry for the noise08:50
T42<edp_17> No worries. :)08:50
T42<edp_17> I've decided to give a try for the newer chroot.09:30
T42<edp_17> Now, I'd like to install some packages in there and getting this: sudo: account validation failure, is your account locked?09:32
T42<edp_17> I've seen somebody reported this issue but there was no solution. Any idea?12:59
T42<edp_17> I've downloaded the older ubuntu tarball and still cannot enter. It says "Unknown ubuntu version".13:05
T42<shouaccount> you need to add your user account to /etc/shadow (re @edp_17: I've seen somebody r...)13:05
rinigus@edp_17: you can alter sudo config in the chroot env if you do it outside of it. I think I had to do that for the same reason13:05
T42<edp_17> I've checked the ubu-vhroot script and seen that it is checking for version squeeze and wheezy|bullseye however I have jessie/sid in /etc/debian_version13:06
T42<edp_17> Are these new things and changed for building from 4.1? None of them were required for older builds.13:07
T42<edp_17> *ubu-chroot script13:08
T42<edp_17> On my host? (re @shouaccount: you need to add your...)13:08
T42<shouaccount> chroot (re @edp_17: On my host?)13:10
T42<edp_17> Ok13:17
T42<edp_17> Okay, I know now why couldn't enter into older chroot.13:23
T42<elros34> I guess you can't chroot to legacy ubuntu sdk because you use sed command from HADK13:23
T42<edp_17> Yep. Exactly.13:24
T42<edp_17> Now I went back to the newer chroot but I am not sure that is fine for my device.13:24
T42<edp_17> And trying to add the user into /etc/shadow as Shou recommended.13:25
T42<elros34> you can have some issues when compiling old kernel with never compiler form ubuntu 20.0413:26
T42<edp_17> So, do you recommend to use the older chroot?13:29
T42<elros34> sure but if you already use 20.04 then why not try, maybe I am wrong and kernel will be compiled by compiler from android tree and everything will work13:31
T42<edp_17> Okay, I try now.13:43
T42<edp_17> As you mentioned, the compilation errored: https://paste.ubuntu.com/p/xQvmYDns4n/13:55
T42<elros34> line62: I guess python2/3 issue, I had something similar recently in osc devel -> testing copy script. print r statement changed to print(r) function14:06
T42<edp_17> So, I need to go back to the older version of chroot I guess. (At least now I know what to fix to be able to enter into 😊)14:22
T42<edp_17> Yeah, using the older chroot, the hybris-hal has built without error. 👍15:06
T42<edp_17> ... and I got the first error when building pulseaudio-modules-droid: https://paste.ubuntu.com/p/y7zzPnF5gc/15:24
T42<edp_17> Should I upgrade pulseaudio-modules-droid?15:24
deathmisthey, is it worth it to upgrade a working aarch64/hybris-16.0 SFOS 4.1 port to hybris-17.1 still? 10 is the last Android version my OEM supported so it would make installation a bit easier too15:28
rinigusdeathmist: if hybris-16 is working fine, I wouldn't do that and would have spent time on something more productive. assuming that los16.0 is available15:42
deathmistwell, 16.0 builds are not available anymore from https://download.lineageos.org/cheeseburger at least since 18.1 is the default so I've archived some older zips, but the situation is kind of the same on 17.1 as well if I were to upgrade15:47
rinigusdeathmist: that is a problem, indeed. and will be the same with 17.1, unfortunately.which seems to be a major issue with any LOS based port15:49
rinigusdo you distribute los 16 yourself somehow?15:51
deathmistrinigus: yes, I've got the last 16.0 signed official OP5/5T builds archived on my MEGA drive: https://mega.nz/folder/2gt1GI5B#GFQWf8_YTxK6y9oPp5w-QQ16:01
deathmistI believe I also "hoarded" the last 17.1 zips already for the same possible reason locally16:03
rinigusdeathmist: way to go, I think. in this respect, should be almost as good as for LOS17 (I presume users need to downgrade stock first). but yeah, there isn't much anything better on AOSP10.16:03
rinigusactually, you maybe the ONLY port (aarch64 and LOS16) that has a chance of HW acceleration in flatpak. I couldn't make it work for AOSP1016:04
rinigusbut LOS16/aarch64 might work. which would allow you to use current flatpak KDE platform16:05
rinigusarm32 is phased out already16:05
rinigusdeathmist: ^16:05
deathmistrinigus: neat, I might check it out. I'd also like to play around with https://github.com/Anbox-halium/anbox-halium to see if I can get it to boot and perhaps even usable in SFOS userspace, it's a really promising project16:08
rinigusdeathmist: good luck with it!16:08
deathmistthanks, I hope I at least get to see the LOS boot animation of it and get an ADB shell :)16:10
deathmistoh yeah is there anything I should know about the new OBS? I'd like to get stuff migrated and updated so (XDA) users aren't stuck on 3.416:16
deathmistgetting OP5/5T projects merged would also be nice since maintaining the 5T one is kind of a pain and mostly is duplication of work16:19
deathmistI don't think an upgrade path from armv7 userspace to aarch64 is possible either, so messing with the project structure(s) shouldn't be a big deal16:22
T42<elros34> @edp_17 Did you update submodules?16:29
T42<edp_17> Yes I did.16:44
T42<elros34> even droid-hal? Did you build it also?16:48
T42<b100dian> deathmist: thanks for your help;)16:49
deathmist@b100dian np, I already dealt with a bunch of the issues I saw you had piled up on your tracker16:51
T42<edp_17> I have updated all three submodules but didn't build droid-hal. I only built hybris-hal then ran the mic to build all packages. (re @elros34: even droid-hal? Did ...)16:51
T42<elros34> so what was to point to update submodules for droid-config/hal if you didn't built them?16:52
T42<elros34> mic do not built single package only pull all from your local repo or obs/jolla repo and create sfos image16:53
T42<edp_17> I thought mic would do that.16:53
T42<edp_17> Okay, I'll build droid-hal and retry.16:54
T42<edp_17> Thanks.16:56
rinigusdeathmist: OBS is up and running. if you want to switch to aarch64 with you should be fine already and its possible to do so17:01
rinigusas for 5/5t merging - could choose one of them and make it  a base?17:02
deathmistrinigus: yeah, I'd make cheeseburger the base and add 5T droid-config etc. on top I'd assume?17:10
rinigusdeathmist: almost. see https://build.merproject.org/project/show/nemo:testing:hw:sony:tama:aosp10 for example17:11
rinigusyou would need to choose few packages as preferred ones (see project config for tama)17:12
rinigusthere some configs, hal were preferred17:13
maldeathmist: so a bit similar how we have the sony xperia device variants, just some config differences17:13
deathmistmal: pretty much, and thanks rinigus I'll look into it17:19
maltama was done the same way, mostly17:20
deathmistbtw I'd like to ask: is armv7 upgrade to aarch64 userspace possible for existing users without reinstall? if not that's ok17:20
malI think that is not supported17:21
deathmistyeah I figured, at least it makes the OBS repo merging process a bit more seamless I suppose17:21
malbecause it would have a partially arm and partially aarch64 at some point and that most likely breaks everything17:21
T42<b100dian> anyone know how to debug mic error "running command: "/sbin/losetup -d /dev/loop10" \ "Error <repo>[07/20 10:54:21] : Could not run transaction."17:25
T42<b100dian> (ok, it's probably the last package that installation was triggered for)18:22
piggzmal: at some point was there a generic package providing pulseaudio-modules-droid?18:50
malpiggz: hmm, which part do you mean?18:53
malpiggz: what are you trying to do?18:53
piggzmal: dhv build fails on pine https://build.sailfishos.org/package/show/nemo:devel:hw:pine:dontbeevil:pinephone/droid-hal-version-pinephone18:54
piggzbut, it used to work18:54
piggzso, somewhere, a package has gone missing18:54
malpiggz: I'm quite sure talked about that and for native devices you would only require the keepalive plugin, wasn't that all you need19:09
piggzit is19:10
piggzi wonder if i need to tweak dhv19:10
piggzor, does the keep alive package "provide" pulseaudio-modules-droid ?19:10
malit doesn't because it co-exists with droid module19:13
malpiggz: make a PR to dhv submodule to fix that requirement19:14
piggzmal: this was all seeming very familiar....19:19
piggzbut i was thinking about dhc19:19
piggzshould i wrap dhv in if native ?19:19
maljust wrap that with %if 0%{!?native_build:1} and else for the droid case19:23
piggzah, native_build is already in there19:24
malit just had a bug :)19:24
* piggz checks git blame19:24
piggzah, yes, it was me that added that!19:24
malI think you did that before the split of keepalive from droid module19:25
malyep, some months earlier19:25
T42<b100dian> ok, so I think my mic image creation is because i have tooling/target 4.0.1 and I want to build 4.1.0 from obs. Do I need to upgrade both?20:12
T42<b100dian> also - it is not clear to me, I've installed the 4.1.0 tooling side-by-side but the sfossdk is still entering a chroot where os-version is
T42<b100dian> I'd like to keep the 4.0.1 'workflow' working at least till the OBS + 4.1.0 is flashed successfully and I know it works..20:15
malyou can add separate toolings for different releases if you want20:20
T42<b100dian> I did, but I can't 1. add targets named the same $VENDOR-$DEVICE-$PORT_ARCH20:21
T42<b100dian> 2. don't know what sfossdk choses as tooling (still 4.0.1)20:21
T42<b100dian> and I've changed RELEASE in ~/.hadk.env20:22
T42<b100dian> oh - there's another layer - sdks:) so I need to install a separate sdk first?20:26
T42<b100dian> mal: I'm doing guesswork here. The question I have is what do I need to successfully run mic on a ks file generated by OBS for
T42<elros34> it shouldn't really matter but you can upgrade to latest sdk. ks file is probably the same20:32
T42<b100dian> but given a ks file, would mic command fail because sdk or tooling or target is not 4.1.0 but 4.0.1?20:44
T42<elros34> mic doesn't care at all about target and tooling and unlikely about sdk version. Target version is only important to generate correct ks file but if you downloaded it from obsand run mic manually then that is no issue20:46
T42<b100dian> thanks @elros34 for restoring sanity20:47
T42<b100dian> Where should I look up next for the Error <repo> Could not run transaction?20:48
T42<b100dian> That happens right after "installing package glibc-debugsource-2.30.." which is the last part of local build too20:48
T42<elros34> show full log, mic --help also have more verbose build options. You do not need that glibc but I guess you have valgrind in patterns added indirectly20:50
*** Daanct12 is now known as Danct1220:50
T42<b100dian> Here is the script https://github.com/sailfishos-on-tucana/Readme/blob/main/create-image.sh#L67 and the output with —verbose —debug added https://pastebin.ubuntu.com/p/fbH3q3zQSx/20:53
piggzmal: no sure why dhv explicitly required p-m-d when its already required by dhc ?20:54
T42<b100dian> I am looking at mic right now, zypppkgmgr.py at for e in errors:\n    msger.warning(e[0]) doesn't output anything. I've tried repr(e) to no avail20:55
T42<elros34> are you sure  you want loops image or you just copy it from rinigus? His adaptation is not the best for unexperienced porter because his port is not done regular HADK way20:59
T42<b100dian> Yes I copied from rinigus:) Let me chack what build_packages.sh does, it didn't cross my mind that was different21:00
T42<b100dian> if Requires: droid-hal-...-kernel-modules21:02
malpiggz: not quite sure really, at least after we got rid of patterns, before that it made sense21:03
T42<b100dian> @elros34  already with fs the output looks like the familiar build_packages —mic21:05
T42<b100dian> well, to be fair, rinigus tried to help and enlightened me that I could download the ks and run mic myself, my bad that I haven't checked the build scripts for the 'usual' way this is done. Thank you @elros34 and rinigus - I now have a tar,gz file ;)21:09

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!