| Thaodan | The device sparse can override the changes from sparse-$android_version_major or you can delete the file with delete_files | 01:12 |
|---|---|---|
| T42 | <zinstack625> mal: so hybris 17 builds have both sparse and sparse-10, as it seems | 06:11 |
| korppi | mal: Did your fp2 reboot after starting lipstick when in 4.0.1.48 ? | 06:36 |
| korppi | mal: for my port it was missing firmware line on udev rules. So i added SUBSYSTEM=="firmware", ACTION=="add", RUN="/usr/bin/droid/droid-load-firmware.sh" to the rules | 06:36 |
| rinigus | korppi: you mean after OTA? | 07:03 |
| rinigus | .. reboot after finishing OTA | 07:03 |
| korppi | rinigus: Yes after OTA, udev rule file for firmware was gone. | 07:10 |
| korppi | rinigus: I checked xa2 and that line was added there to one of those 999-* rule files | 07:13 |
| rinigus | korppi: for me all worked after reboot. but I have that rule provided in droid-config rpm via 998-droid-system.rules file. maybe config is old and not updated? | 07:16 |
| korppi | rinigus: Yes this is an ancient port so many things have changed, but if i remember correctly mal had similar problems than me with fp2 so this was heads up for all the old ports | 07:21 |
| korppi | rinigus: kernel could not find adsp firmware and lipstick tried to use graphics and result was reboot | 07:24 |
| mal | korppi: I haven't been able to boot fp2 with 4.0.1.48 | 08:45 |
| korppi | mal: At all or reboot before ui ? In my scorpion_windy port had that firmware line missing from udev rules, OTA removed firmware-rule file and result was reboot. | 08:55 |
| korppi | mal: kernel needed some patches too to it, but those patches have been mentioned here before. Kernel version is 3.4.0. | 09:01 |
| mal | korppi: not sure when it stops booting, at least kernel had issues which I need to fix | 09:04 |
| mal | there is one different kernel build for fp2 I have tested which reboots after starting UI, I haven't found why it fails | 09:05 |
| mal | I think there is some issue with systemd not working correctly on fp2 | 09:11 |
| korppi | mal: I had logs saying it can't load some adsp firmware, turned out it could not find it allthought it was in same place. | 09:19 |
| korppi | *although | 09:20 |
| mal | ok, I can have a look on my device | 09:21 |
| T42 | <edp_17> mal: I have some problems on OBS. On my treltexx the gts-droid failed. I don't know what's the missing dependency. Can you help me out with this, please? https://build.sailfishos.org/project/monitor/nemo:devel:hw:samsung:treltexx | 10:35 |
| T42 | <edp_17> Plus my n7000 and hammerhead builds are a disaster: https://build.sailfishos.org/project/monitor/home:edp17:n7000 | 10:39 |
| T42 | <edp_17> https://build.sailfishos.org/project/monitor/home:edp17 | 10:39 |
| T42 | <elros34> build older gst-droid. Btw you should not build all releases at once (3.4.0 and 4.0.1 at the same time). Disable all repositories but one that you want to build then set revision in _service file and let it build otherwise expect issues on older release . For sure you had situations that you had to downgrade packages when you have bui | 10:45 |
| T42 | ld packages locally | 10:45 |
| rinigus | @edp_17: you have used too new gst-droid. compare with https://build.sailfishos.org/package/show/nemo:devel:hw:sony:tama/gst-droid | 10:45 |
| rinigus | and "devel" repo is expected to have ONLY "latest", no fixed SFOS version | 10:46 |
| rinigus | @edp_17: comments ^ similar to the ones by @elros34 | 10:47 |
| rinigus | n7000 fail as hal package failed. which is probably due to droidmedia-0.20200424.0 20 gd0d14dd-1.armv7hl.rpm package name (check it for some odd html symbols) | 10:49 |
| T42 | <elros34> when using web interface instead osc packages names are changed (IIRC + symbol, maybe others too) | 10:51 |
| T42 | <edp_17> Thanks guys! I also wanted to ask how to disable a release to build. | 10:54 |
| T42 | <edp_17> Oh, and how can I set up the _service file in droid-config-$DEVICE if I need a different branch for older sfos version? Should I build the old version first, then once that is built, disable it, update the _service for the newer one and build the newer version? | 10:57 |
| T42 | <elros34> Repositories tab -> Build Flag -> choose release -> Explicitly disable or manually in meta tab | 10:58 |
| T42 | <edp_17> Thanks. | 10:58 |
| T42 | <elros34> _service: branch: git branch, revision: HEAD or some commit hash | 11:01 |
| T42 | <edp_17> Yes, but this _service file is for all sfos versions and I need a different branch for 3.3 or 4.0. I guess there is no way to set in the _service file that use this brach for building sfos 3.3 but use that branch for building sfous 4.0. Right? How I understand the only way to do it, if I update the _service file for 3.3 and building it | 11:04 |
| T42 | , then disabling that 3.3 to avoid re-buil, and update _service file for 4.4 and buid 4.0. Right? | 11:04 |
| T42 | <elros34> yes | 11:05 |
| mal | @edp_17 like I said on this channel before, latest gst-droid cannot be used now, please use version 0.20201104.0 | 11:05 |
| T42 | <edp_17> Thanks for confirming! | 11:05 |
| T42 | <edp_17> mal: Now, I remember. Just forgot to set in the _service file. I think, need to review all _service files in all ports and then build each versions one by one. | 11:08 |
| mal | everything else can probably be latest for 4.0.1.48 | 11:10 |
| T42 | <edp_17> Thank you! | 11:11 |
| T42 | <edp_17> I've disabled 3.4 and tried to update the _service file in gts-droid to build 4.0 but I cannot save the changes in _service. I am doing something wrong, but don't know what. https://build.sailfishos.org/project/show/nemo:devel:hw:samsung:i9100 | 11:14 |
| T42 | <edp_17> I got it! Needed to remove the / from the <param name="revision"/>. Thanks! | 11:16 |
| T42 | <elros34> I think you should/need to disable only Build Flag | 11:17 |
| T42 | <edp_17> Yeah, I thought required to disable the others too, then I spotted that I needed to remove that /. 😃 | 11:18 |
| T42 | <edp_17> For my n7000 port, I had to amend external/droidmedia/env.mk. Therefore I uploaded the custom droidmedia*.rpm and droidmedia-devel-*.rpm into droid-hal-n7000 on OBS. As A result, building gts-droid failed because didn't find the droidmedia-devel package. How can solve this? How can I use custom droidmedia on OBS? Thanks in advance. | 12:05 |
| T42 | <edp_17> In github, I've forked the orginal droidmedia and upload my changes into the n7000 branch. | 12:10 |
| T42 | <elros34> @edp_17 https://irclogs.sailfishos.org/logs/%23sailfishos-porters/%23sailfishos-porters.2021-03-15.log.html#t2021-03-15T10:51:10. Try changing rpm name before upload or use osc | 12:55 |
| mal | hmm, where did those extra things come to the filename | 12:58 |
| T42 | <edp_17> Thanks @elros34. To be honest, until now, I missed rinigus' comment about the failing hal package. | 13:50 |
| T42 | <edp_17> I've seen somebody already fixed the package names in there. Thank you for that! | 13:50 |
| T42 | <edp_17> @elr | 13:51 |
| T42 | <edp_17> @edp_17 [I've seen somebody already fixed the package n …], Ops, I mixed up the n7000 repo with the hammerhead one where I don't have those weird strings in the name. | 13:52 |
| T42 | <elros34> basically commandline way to manage obs: 'osc checkout home:edp17:n7000' to clone (like github) then make changes to local packages or_service files. Then 'osc addremove' to add/remove new files, osc status, and 'osc checkin' to upload your changes | 13:56 |
| T42 | <edp_17> I see, thanks. | 13:59 |
| T42 | <edp_17> @elros34 : I have another question. When I OTA to a newer release, that will refreshes/reinstalls the hybris-boot too. (Correct me if I am wrong.) In some of my devices I cannot use hybris-boot and always need to flash the kernel file from the out/target/product/$DEVICE/ folder. In those devices, how the OTA will work? Once I did the O | 14:14 |
| T42 | TA should I flash the kernel in TWRP before first boot? | 14:14 |
| T42 | <elros34> if you followed the faq about OTA then you should have flash-bootimg.sh triggered if you have enable_kernel_update in droid-hal-device.spec script which flash hybris-boot to boot partition. Maybe you could change it a little so it flash your zImage or whatever format you use | 14:23 |
| T42 | <edp_17> I see. and how the file named kernel will go into he /boot/ instead of the hybris-boot.img? | 14:35 |
| mal | @edp_17 you need something like this in your project configs on OBS https://build.sailfishos.org/project/prjconf/nemo:testing:hw:fairphone:fp2-sibon | 14:38 |
| mal | adapt device codename in those of course | 14:39 |
| T42 | <edp_17> Thanks! I added and it started/continued to build for the hammerhead. 😃 | 14:41 |
| T42 | <edp_17> And the n7000 too. 😃 | 14:42 |
| T42 | <elros34> @edp_17 hmm I guess kernel is already packaged in droid-hal-device-kernel.rpm but flash script is executed when you install img-boot rpm. Probably you would have to add: https://github.com/mer-hybris/droid-hal-device/blob/master/droid-hal-device.inc#L888-L895 to your droid-hal-device.spec but for kernel package instead img-boot. Maybe | 14:43 |
| T42 | there is some better way to do this | 14:43 |
| T42 | <edp_17> Thanks @elros34, I'll try this. | 14:50 |
| T42 | <edp_17> The hammerhead build fo r4.0.1.48 has completed. If I want to try to OTA to this release I should add the url from the relevant repo under the 'Publish Falg' in 'Repositories'. Right? Like: http://repo.merproject.org/obs/home:/edp17/sailfishos_4.0.1.48_latest_armv7hl/ | 14:54 |
| T42 | <zinstack625> Any idea what provides android.frameworks.sensorservice@1.0::ISensorManager/default? sensors@1.0-service is running. Here's a full logcat, can't see anything interesting myself: https://pastebin.com/n0Uk8Ys3 | 14:54 |
| T42 | <elros34> @edp_17 little confusing because your repo doesn't contain device name but yes url looks correct | 14:58 |
| T42 | <edp_17> @elros34 : I didn't want to mess up the other hammerhead repo, so I've created and built one as a 'Subproject' under my 'Home Project'. | 15:00 |
| T42 | <elros34> the point is you didn't use subproject for hammerhead | 15:01 |
| T42 | <elros34> https://build.merproject.org/project/subprojects/home:edp17 | 15:02 |
| T42 | <edp_17> Oh, yes, because I used the 'Home Project' directly for my cm12.1 hammerhead build. Although, I think you are right. To avoid confusion, I will create a 'Subproject' for hammerhead too and move all stuff there. | 15:04 |
| T42 | <edp_17> @elros34 : Is it possible to OTA from 3.3.0.16 to 4.0.1.48 or I need to OTA to 3.4.0.24 first? (I've seen a website where all releases, major and smaller updates, were listed but can't find it.) | 15:22 |
| T42 | <elros34> "Stop Releases" https://jolla.zendesk.com/hc/en-us/articles/201836347 | 15:24 |
| T42 | <edp_17> Yep, this is the one. Its seems from 3.3 I cannot go to 4.0 directly. First I need to go to 3.4 firthe then to 4.0. | 15:31 |
| T42 | <edp_17> Thanks. | 15:32 |
| T42 | <edp_17> Hm, I've added: ssu ar adaptation-community-treltexx http://repo.merproject.org/obs/nemo:/devel:/hw:/samsung:/treltexx/sailfishos_3.4.0.24/ | 15:47 |
| T42 | <edp_17> but when I do a version --dup, I get: Error: nothing provides patterns-sailfish-device-adaptation-treltexx needed by pattern:jolla-configuration-treltexx-0.0.25-10.30.4.jolla.noarch | 15:47 |
| T42 | <edp_17> These are the repos: https://paste.ubuntu.com/p/stpVQdXDzP/ | 15:49 |
| T42 | <edp_17> Where from should I get 'patterns-sailfish-device-adaptation-treltexx'? | 15:52 |
| T42 | <elros34> from new enough droid-config | 15:56 |
| T42 | <mintphin> Hi. I'm following the HADK and I'm stuck at "Configure Mountpoint Information". | 16:01 |
| T42 | <zinstack625> Anyone? About my problem just above, it can't seem to find sensorservice, but it is located in /system/lib64/ as a .so. Perhaps aarch64 builds were not yet told to look there? | 16:01 |
| T42 | <mintphin> The guide goes too briefly on it and skips many details. | 16:01 |
| T42 | <mintphin> So I don't know exactly what to do. | 16:02 |
| T42 | <mintphin> Should I just copy the output of ls and paste it on a file? Or what? | 16:02 |
| T42 | <zinstack625> @mintphin do an "ls -l /dev/block/bootdevice/by-name" on your device and make an entry for your device with each of those links in hybris/hybris-boot/fixup-mountpoints | 16:02 |
| T42 | <mintphin> ah ok thanks | 16:03 |
| T42 | <elros34> no. You always take by-name path from your device's fstab. | 16:04 |
| T42 | <zinstack625> Those usually are /dev/block/bootdevice/by-name, unless your device is ufs afaik | 16:05 |
| T42 | <elros34> it doesn't have to be block/bootdevice/by-name, it can be platform/msm_sdcc.1/by-name, block/platform/hi_mci.0/by-name (examples from fixup-mountpoints file) and even there was device recently with different paths for different partitions | 16:06 |
| T42 | <mintphin> @zinstack625 [Those usually are /dev/block/bootdevice/by-nam …], yeah ik i found them | 16:06 |
| T42 | <mintphin> (Document) https://irc.thaodan.de/.imgstore/wSsnHXgUy4.png | 16:07 |
| T42 | <mintphin> so uh how can i add an entry | 16:08 |
| T42 | <zinstack625> @mintphin please don't use screenshots and direct replies, those are ugly on irc side | 16:08 |
| T42 | <mintphin> ah ok | 16:08 |
| T42 | <mintphin> sorry | 16:08 |
| T42 | <mintphin> i always forget that | 16:08 |
| T42 | <mintphin> ok found where they start and where they end | 16:09 |
| T42 | <mintphin> so i guess now it's just time to fix the mountpoints | 16:09 |
| T42 | <zinstack625> a single line there is a single partition on your device. this script replaces udev names in fstab android can use with direct (is that the right term) names like /dev/mmcblk0pX | 16:11 |
| T42 | <mintphin> if i'm working on a system-as-root device, should i put both slots in the mountpoints, or just a single slot? | 16:11 |
| T42 | <edp_17> @elros34 [from new enough droid-config], 'New enough' droid config? Think I know now, what happened. I didn't build 3.4 locally, only 3.3 and then 4.0. I uploaded all .rpms to droid-hal-treltexx from my 4.0 local build. So, the 4.0 build on OBS is correct, however, the 3.4 is not as that used the same .rpms that I uploaded from my | 16:12 |
| T42 | 4.0 local build. | 16:12 |
| T42 | <zinstack625> I did system_a and vendor_a, not sure if it's possible to make sfos work with a/b just like android | 16:12 |
| T42 | <mintphin> ok | 16:12 |
| T42 | <zinstack625> But as those are just system and vendor in fstab, you have to include use just system and vendor, not system_a and vendor_a | 16:13 |
| T42 | <elros34> @mint usually active slot without _a/_b suffix but that also you need to check in fstab | 16:13 |
| T42 | <mintphin> wait, walleye has both a and b mountpoints | 16:15 |
| T42 | <mintphin> guess i'll try to replicate them here | 16:15 |
| T42 | <zinstack625> In fstab? How's that? | 16:15 |
| T42 | <mintphin> i'm just looking at fixup-mountpoints and stumbled upon walleye's mountpoints | 16:15 |
| T42 | <zinstack625> If there are walleye's mountpoints there, obviously, you don't need to modify fixup-mountpoints | 16:16 |
| T42 | <mintphin> my device is laurel_sprout | 16:17 |
| T42 | <mintphin> not walleye | 16:17 |
| T42 | <zinstack625> Ah, gotcha | 16:17 |
| T42 | <mintphin> i'm just saying the laurel_sprout mountpoints and walleye mountpoints are very similar | 16:17 |
| T42 | <zinstack625> That's weird, there are no system_a entries in walleye's fstab, or maybe it's some google magic | 16:21 |
| T42 | <edp_17> Hi all, I was trying to build packages for OBS (i9100 sfos4.0) and got this error: https://paste.ubuntu.com/p/wTv5Yh5Zxr/ | 16:43 |
| T42 | <edp_17> Do you have idea what it is and how to fix? Thanks. | 16:43 |
| T42 | <edp_17> Prior this, I've re-created sdk, targets, toolings, updated all submodules and mer-kernel-check, then rebuilt hybris-hal and migrated patterns to meta-packages. | 16:46 |
| mal | @edp_17 wasn't your device hybris-16.0, that new ports don't use pulseaudio-modules-droid-glue | 16:53 |
| mal | you should have pulseaudio-modules-droid-hidl in patterns probably | 16:53 |
| T42 | <zinstack625> Oh, hey mal, how's fp3 hybris17? | 16:54 |
| mal | @zinstack625 most things work, some hacks for camera, I had some call audio issues but could be some small thing missing after doing a rebuild, only broken feature is fingerprint | 16:55 |
| T42 | <zinstack625> My device is sdm632 too, and it has problems with android.frameworks.sensorservice, any ideas? | 16:56 |
| T42 | <edp_17> mal: No, my devices use cm12.1 and cm14.1 | 16:56 |
| mal | hmm, have you built audioflinger glue for those? | 17:01 |
| mal | @edp_17 looks like I need to fix that | 17:02 |
| T42 | <elros34> didn't you forget to build droid-hal? | 17:03 |
| mal | @elros34 that is unrelated, it's a missing fix for droid-devel header move | 17:04 |
| T42 | <elros34> ok | 17:05 |
| T42 | <zinstack625> Someone mind looking at my logcat? Specifically "qti_file_open():Could not open device file" https://pastebin.com/n0Uk8Ys3 | 17:06 |
| T42 | <zinstack625> Dmesg gets spammed like this: https://pastebin.com/Bht29HiZ | 17:07 |
| T42 | <zinstack625> android.frameworks.sensorservice@1.0.so is in /system/lib64 and /system/lib, build is aarch64 | 17:09 |
| T42 | <zinstack625> Setting LD_LIBRARY_PATH=/system/lib64/ in /usr/bin/droid/droid-hal-startup.sh did not help | 17:13 |
| T42 | <edp_17> mal: Okay. Does it mean I need to wait for you to fix? | 17:16 |
| T42 | <mintphin> how can i make breakfast use local manifests instead of trying to fetch from lineage? | 17:16 |
| mal | @edp_17 do you have some different droid-hal packages on OBS? | 17:17 |
| mal | @edp_17 could you try branch jb51449 from https://github.com/mlehtima/pulseaudio-modules-droid-glue and see if that build | 17:18 |
| T42 | <zinstack625> @mintphin after making up local_manifests, run "repo sync —fetch-submodules" and only then do breakfast | 17:21 |
| T42 | <mintphin> ah ok | 17:21 |
| T42 | <edp_17> mal: Will do but later. Thanks! | 17:33 |
| T42 | <mintphin> for some reason it's still showing this error after fetching submodules | 17:54 |
| T42 | <mintphin> (Document) https://irc.thaodan.de/.imgstore/TJxGppaBQV.png | 17:54 |
| T42 | <mintphin> wait | 17:54 |
| T42 | <mintphin> i'll send this as a pastebin | 17:54 |
| mal | do you have that repo in local manifest? | 17:54 |
| T42 | <mintphin> I have it in .repo/local_manifest/laurel_sprout.xml | 17:55 |
| T42 | <mintphin> https://pastebin.com/x12ZC8ra | 17:55 |
| mal | show the local manifest | 17:55 |
| T42 | <mintphin> ok | 17:55 |
| T42 | <mintphin> (Document) https://irc.thaodan.de/.imgstore/wZNO096kVV.xml | 17:56 |
| mal | so you don't have the repo there | 17:56 |
| T42 | <mintphin> which repo? i implemented the respective vendor, kernel, and device repos. | 17:57 |
| mal | it should have device/xiaomi/sm6125-common which comes from there https://github.com/LineageOS/android_device_xiaomi_sm6125-common | 17:57 |
| T42 | <mintphin> ah yeah i saw that being mentioned before | 17:57 |
| T42 | <mintphin> ok i'll have to add it | 17:57 |
| mal | or if you use some custom repo then take it from there | 17:58 |
| mal | looks like that custom github project also has it | 17:58 |
| T42 | <mintphin> yeah true | 17:59 |
| T42 | <mintphin> where should it go? | 17:59 |
| T42 | <mintphin> like what path? | 17:59 |
| mal | you have all the information already | 18:00 |
| mal | the path is mention in the error message, I also said it once | 18:00 |
| T42 | <mintphin> ah ok | 18:00 |
| T42 | <zinstack625> it says it right there in the error message, device/xiaomi/sm6125-common | 18:00 |
| T42 | <mintphin> ah ok thank you | 18:01 |
| T42 | <edp_17> @edp_17 [Hm, I've added: ssu ar adaptation-community-tr …], Guys, I don't get it what I am doing wrong. Locally I rebuilt packages for 3.4 (-c, -d, -v, -g). Pushed all changes to github, uploaded all packages to obs, edited the .spec file with the right .rpm name, disabled building 4.0, and enabled building 3.4. Once building has c | 18:30 |
| T42 | ompleted tried to OTA to 3.4 and got the same error message. | 18:30 |
| T42 | <mintphin> now it's asking me for the sm6125 vendor | 19:03 |
| T42 | <mintphin> i can't seem to track a lineage-17.1 version of it | 19:03 |
| T42 | <mintphin> found it | 19:14 |
| T42 | <mintphin> ok new error `error: device/xiaomi/laurel_sprout/fod/Android.bp:16:1: "vendor.lineage.biometrics.fingerprint.inscreen@1.0-service.xiaomi_laurel_sprout" depends on undefined module "//hardware/xiaomi:vendor.xiaomi.hardware.fingerprintextension@1.0"` | 19:19 |
| T42 | <mintphin> how can i safely remove fod references? | 19:19 |
| T42 | <mintphin> ok i just removed the conflicting lines | 19:40 |
| T42 | <mintphin> it seems to beworking fine | 19:41 |
| mal | @mintphin wait | 19:42 |
| T42 | <mintphin> *be working | 19:42 |
| mal | https://github.com/HarukeyUA/android_device_xiaomi_laurel_sprout/blob/lineage-18.1/lineage.dependencies#L7 | 19:42 |
| mal | you should check the dependencies files | 19:42 |
| T42 | <mintphin> those are the lineage 18.1 dependencies though | 19:42 |
| T42 | <mintphin> i'm on 17.1 | 19:42 |
| mal | well change the branch | 19:42 |
| mal | the same line is in 17.1 | 19:42 |
| T42 | <mintphin> oh yup same dependency, i'll add and sync | 19:43 |
| T42 | <mintphin> wait then i could get fod working | 19:43 |
| T42 | <mintphin> that repo doesn't exist anymore so yeah | 20:27 |
| mal | what do you mean? | 20:39 |
| mal | the repo is at least in lineageos github | 20:39 |
| T42 | <mintphin> not on harukey's repos tho | 20:40 |
| T42 | <mintphin> maybe i could sync it here though | 20:40 |
| T42 | <mintphin> ok lemme try that | 20:40 |
| mal | you can takes repos from different sources if needed | 20:40 |
| T42 | <mintphin> qh ok | 20:52 |
| T42 | <mintphin> oh sorry | 20:53 |
| Mister_Magister | mal: could you help me out with GPS? | 21:38 |
| mal | what is the problem? | 21:51 |
| Mister_Magister | mal: emm i sent logs and stuff… after making 3.4 update it stopped working, hal seems to work but like test_gps and other sfotware can't connect to it it seems, there's no flashing gps symbol either | 21:55 |
| mal | Mister_Magister: I probably don't have the logs anymore | 22:00 |
| Mister_Magister | yeah, will get you those tomorrow! | 22:00 |
| mal | ok | 22:00 |
| poetaster | g'night guys. hackernews app is in beta | 22:26 |
| T42 | <edp_17> @elros34 [from new enough droid-config], I have found three /rpm files in the droid-local-repo/treltexx/droid-configs/. Should I uplod these into which package droid-config-treltexx or droid-hal-treltexx? | 22:44 |
| T42 | <edp_17> I meant three patterns-sailfish-device-*.rpm | 22:45 |
| T42 | <edp_17> On my treltexx repo, now I have that 'patterns-sailfish-device-adaptation-treltexx' so that error is gone. Although, got a new one: "Error: nothing provides pulseaudio >= 12.2+git9 needed by pulseaudio-modules-droid-14.2.88-1.1.3.jolla.armv7hl" | 22:55 |
| T42 | <edp_17> I've checked my local repo and there is no pulseaudio rpm. | 22:56 |
| mal | @edp_17 what are you talking about uploading those, you only upload droid-hal (and droidmedia etc) to droid-hal repo on OBS, everything else is built on OBS | 23:13 |
| T42 | <edp_17> mal: Hi. I have realised that all those pattern*.rpm were generated on treltexx because I uploaded submodules to my github. Therefore, I repeated the same with the hammerhead. Hopefully it will generate those pattern*.rpm files there too. | 23:15 |
| mal | I don't understand what you are talking about | 23:17 |
| T42 | <edp_17> First I though those were missing because I forgot to upload something. | 23:17 |
| mal | what is that earlier error about | 23:18 |
| T42 | <edp_17> Then, I realised that I needed to upload my local changes to github (droid-config, droid-hal, and droid-hal-version), then I needed to trigget OBS to rebuild packages. | 23:18 |
| T42 | <edp_17> Once I refreshed my github repos with the latest sfos 4 related changes, OBS has generated those pattern*.rpm files. | 23:19 |
| T42 | <edp_17> This is for the treltexx. | 23:19 |
| T42 | <edp_17> Then, I tried to OTA my hammerhead to sfos 4 and got the same error. And realised that I also needed to upload all changes from my local repo to github. | 23:20 |
| mal | my last question was about the pulseaudio error | 23:20 |
| T42 | <edp_17> Sorry, I thought about the others. | 23:21 |
| T42 | <edp_17> Regarding that pulseaudio error. When OBS re-built all packages and I've seen those pattern*.rpm in the treltexx repo, I tried to OTA the device to 4.0 and got that error. | 23:22 |
| T42 | <edp_17> This is all I know. | 23:22 |
| mal | what do you see if you search for pulseaudio on the device using pkcon search pulseaudio | 23:23 |
| T42 | <edp_17> mal: Got this: https://paste.ubuntu.com/p/mfwVrWdmyf/ | 23:25 |
| mal | what did you use for ssu re | 23:26 |
| T42 | <edp_17> mal: ssu re says: 'Device release is currently: 3.4.0.24' | 23:27 |
| T42 | <edp_17> Because I issued ssu release 3.4.0.24, then pkcon refresh, then version --dup | 23:28 |
| T42 | <edp_17> as root. | 23:28 |
| mal | so you are trying to update to 4.0.1 without actually changing the version? | 23:28 |
| mal | or were you trying to update to 3.4.0? | 23:29 |
| T42 | <edp_17> Yes. | 23:29 |
| mal | yes to which question? | 23:30 |
| T42 | <edp_17> Sorry, yes I was trying to upgrade to 3.4. | 23:30 |
| T42 | <edp_17> Didn't see the first part of your question. 😊 | 23:31 |
| mal | does ssu lr look ok? | 23:31 |
| T42 | <edp_17> Yes, it looks ok: https://paste.ubuntu.com/p/PqkbVHSFg3/ | 23:32 |
| T42 | <edp_17> Well, no, actually it is not ok! | 23:33 |
| mal | @edp_17 why do you think it looks ok | 23:33 |
| T42 | <edp_17> It is not ok, because I left 4.0 repo in there instead of 3.4! | 23:33 |
| T42 | <edp_17> Oh my! Sorry, it is my fault. | 23:34 |
| T42 | <edp_17> As I pasted into ubuntu, now I saw. | 23:34 |
| T42 | <edp_17> I remember why, because first I thought could go from 3.3 to 4.0, then elros sent me the stop releases list and saw I needed to got to 3.4 first but I forgot to set it as I was upgrading the hammerhead from 3.4 to 4.0 at the same time and I mixed up the terminal sessions. | 23:36 |
| T42 | <edp_17> Okay, I'll try again. The good part, I have the pattern*.rpm files for the 4.0 version. So, once I got to 3.4, the upgrade to 4.0 should be okay. | 23:38 |
| T42 | <edp_17> mal: Sorry for wasting your time! | 23:38 |
| T42 | <edp_17> mal: I have a question. I disabled 3.4 repo, and let 4.0 enabled. Then I changed something in droid-hal-treltexx and I've see that buildig droid-hal-treltexx for the disabled 3.4 repo also started. I didn't expect that. Do you know why? | 23:40 |
| mal | and you were sure it was disabled? | 23:44 |
| T42 | <edp_17> Yes 100% | 23:45 |
| T42 | <edp_17> Only the droid-hal-treltexx started to build for that repo, nothing else. On the enabled one, all other packages were started to build (scheduled, waiting or unresolved or something). | 23:47 |
| T42 | <edp_17> mal: I've tried to build branch jb51449 pulseaudio-modules-droid-glue from mlehtima repo and it worked. | 23:48 |
| T42 | <edp_17> mal: this is for the s2 (i9100) | 23:48 |
| mal | I just checked some of my old project on OBS and those still have the old droid-hal packages in the old targets | 23:50 |
| T42 | <edp_17> I don't know what happened but that popped up in the 'Monitor' tab. I though it was normal, so I asked. If this will cause issue, I'll come back to this later. | 23:53 |
| T42 | <edp_17> mal: regarding the pulseaudio-modules-droid-glue. DO you know why I didn't need that jb51449 branch when I built sfos 4.0 for treltexx, hammerhead and n7000? Why was it required only for the i9100? | 23:55 |
| mal | you probably had older dhd submodule | 23:59 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
