| xyb | hello,does anyone know the SSH password of the sailfish os emulator? | 05:09 |
|---|---|---|
| mahrain | Hi all, given Apple’s recent moves I’m pondering a switch to Sailfish on a Sony device. I have two questions. | 07:02 |
| mahrain | Our company only gives access to Exchange resources after accepting MDM via Microsoft Intune portal, would that work with Sailfish’s Exchange implementation? | 07:03 |
| mahrain | secondly, how actively should I look for 64-bit support, do you see android apps requiring this at this point? | 07:03 |
| *** gmc is now known as Guest5797 | 07:35 | |
| Guest5797 | mahrain: i don't know the answer to your questions, and while there are some knowledgable folks on this channel, I would also post your questions on the forum if I were you | 07:38 |
| *** Guest5797 is now known as gmc_ | 07:38 | |
| *** gmc_ is now known as gmc | 07:39 | |
| ender | IMHO, if a company wants me to have company e-mail (and all the control that this implies) on my phone, the company should provide the phone | 10:37 |
| Renaud[m] | rinigus: it seems you imported ecl into chum a bit too early… builds on 3.1.0.12_armv7hl and 3.2.1.20_armv7hl have been stuck for 4 hours. I recall having some issues with qemu and ecl before and I had to make the package directly on device | 13:03 |
| rinigus | Renaud: I was sure it will be fine. sounds like I will have to disable those builds then | 13:07 |
| rinigus | Renaud: disabled in chum and chum:testing | 13:08 |
| rinigus | thanks for keeping an eye | 13:09 |
| Renaud[m] | thanks, I have another package coming soon that depends on it, I'll do the same preemptively | 13:10 |
| rinigus | Renaud: I don't think you can - as meta is not propagated through submission. but you could try | 13:14 |
| Renaud[m] | okay, I'll write a reminder in the request then | 13:15 |
| rinigus | thanks! | 13:18 |
| poetaster | rinigus: so videoworks does build on chum. BUT, it includes both libs and bins that you probably don't want in chum (ffmpeg-static costum build, fre0r plugins for same). | 15:01 |
| poetaster | rinigus: it's obviously going to remain in openrepos but I'm not sure if I should just remove it from obs again:https://build.sailfishos.org/package/show/home:poetaster:videoworks/harbour-clipper | 15:02 |
| rinigus | poetaster: but why not to build them as separate dependencies and request as such? there is no need to put binary blobs into sources... | 15:05 |
| poetaster | rinigus: you mean, create a project for ffmpeg and for the plugins and maintain those in github and on chum? | 15:07 |
| poetaster | rinigus: the value proposition is declining. chum already makes me jump through hoops with releases. It's becomming more work that jolla store. | 15:07 |
| rinigus | poetaster: yes, assuming that ffmpeg is not available in official repos | 15:08 |
| rinigus | But it is there, at least I can get it through zypper | 15:09 |
| poetaster | rinigus: yes, it's even more complicated. | 15:09 |
| poetaster | rinigus: I'm already in the process of branching all the repos (it's 'only' 3 where it's of consequence). | 15:10 |
| poetaster | rinigus: now it's looking like feature set branches (for instance, sharing with Transferengine), and build limits | 15:11 |
| poetaster | I simply won't have enough time. | 15:12 |
| poetaster | rinigus: what I'm looking at now is 3 branches, one feature reduced to the jolla ruleset, one chum, and the full extent openrepos. | 15:15 |
| rinigus | poetaster: it is puzzling that you make branches for it. it should be simple %if in RPM SPEC that could differentiate between chum+openrepos vs store | 15:18 |
| rinigus | it is also not clear why you have different builds for chum and openrepos | 15:19 |
| rinigus | if you request ffmpeg as dependency, this would work (assuming that I understand your problem) for chum+openrepos. if you add it as build dependency, you could pull it into jolla store build | 15:20 |
| poetaster | rinigus: frankly, I just don't grok the rpm spec nonsense. But I also have legary .pro file bits, (ie. python libs installed in the .pro file,not the spec). | 15:20 |
| poetaster | rinigus: I'm sure I could find the right approach with conditionals in spec files. but I'm not sure I care. | 15:21 |
| poetaster | well, obviously I care. | 15:21 |
| poetaster | how many 'aliases' exist for %{buildroot}%{_datadir}/ | 15:21 |
| rinigus | poetaster: it could be easier maybe to explain using some of your projects as an example. which one is tricky for you to fix? | 15:22 |
| poetaster | https://github.com/poetaster/harbour-clipper/blob/main/harbour-clipper.pro + | 15:22 |
| poetaster | https://github.com/poetaster/harbour-clipper/blob/main/rpm/harbour-clipper.spec | 15:22 |
| poetaster | rinigus: in this case, I've already considered just removing the plugins for ffmpeg and reducing the app to what can be done with ffmpeg-tools | 15:23 |
| rinigus | poetaster: ok, do you have sources for frei0r? | 15:23 |
| poetaster | rinigus: yes. | 15:23 |
| rinigus | poetaster: is frei0r packaged somewhere? | 15:24 |
| poetaster | rinigus: all over the place. but building stuff built by Fabrice Bellard, always costs time. | 15:26 |
| poetaster | unless you're fabrice. | 15:26 |
| rinigus | poetaster: is it this: https://src.fedoraproject.org/rpms/frei0r-plugins ? | 15:27 |
| poetaster | ah, shit. how cool. | 15:27 |
| poetaster | sorry, I just realized a friend is maintaining the source. https://github.com/dyne/frei0r | 15:27 |
| poetaster | rinigus: it's a bit older but would probably work. | 15:29 |
| rinigus | poetaster: we could also pull it from your friend's repo - just would need to be sure it is easy to build | 15:30 |
| poetaster | rinigus: that's my point, wasn't that easy to build. well, ffmpeg-static was the real pita. for aarch | 15:31 |
| rinigus | poetaster: wait a sec - frei0r for start. let's keep on a same package | 15:32 |
| poetaster | rinigus: fri0r is plugins for ffmpeg. so ffmpeg first. but, don't wast your time. | 15:33 |
| poetaster | rinigus. I have to go back to basics and see whether I can: 1. get rid of static ffmpeg without losing too much functionality. 2. see if I care enough about the plugins. | 15:33 |
| rinigus | poetaster: ok ffmpeg. we have ffmpeg itself, -tools and -devel. so those seem to be packaged for SFOS already, right? | 15:33 |
| poetaster | rinigus: yes. | 15:34 |
| poetaster | rinigus: but we don't know for how much longer. until 4.x they were installed by default (apparently to support the web browser). | 15:34 |
| rinigus | poetaster: among that what is already packaged, do you miss some other plugins except fri0r? | 15:34 |
| poetaster | rinius: no, it's just not clear which parts of the app will work with SFOS ffmpeg and which (IF any) require the static build I had. | 15:35 |
| poetaster | rinigus: this is 'history' I'll just have to test. the problem is, it'll all be moot in three weeks when I have to test everything with 4.1 and aarch64. | 15:36 |
| rinigus | poetaster: see how it is packaged at https://github.com/sailfishos/ffmpeg | 15:36 |
| rinigus | and what is there / what is missing. I don't think it will disappear from sfos | 15:37 |
| poetaster | rinigus: yeah, I need to learn how to build with submodules. this would also be 'the way' for PIL (which 2 other apps use)... python-imaging. | 15:37 |
| rinigus | poetaster: look at ffmpeg as example. that way you could also package fri0r and then suddenly pieces will fall together :) . | 15:38 |
| poetaster | rinigus: but frankly, I don't know how to use this in the SDK context. Ok, I can clone it, get the submodules with git, but after that, packaging it seems pita. | 15:38 |
| poetaster | rinigus: I get it 'in the abstract'. Just have no idea how to use this in a qt context | 15:39 |
| poetaster | rinigus: I assume that I could also go: https://github.com/sailfishos/python3-imaging/ | 15:40 |
| poetaster | rinigus: but can I just USE those SFOS repos? I don't think so?! | 15:40 |
| rinigus | poetaster: it works as any other lib or dependency. you build it and install into your SDK. or, build at OBS, add your repo to sdk and it will pull that dependency in on building of your package | 15:41 |
| rinigus | poetaster: yes, you can use it. `sb2 -t .... ssu ar ...` | 15:41 |
| poetaster | rinigus: Ummm. I have no idea how to do any of that. I do not understand how submodule stuff is done 'properly'. I mean, I can read the code, but don't know where to begin. And frankly, would rather work on code. | 15:43 |
| rinigus | poetaster: ok, no problem. let's work on code and maybe we can solve it in future. in principle, you just need to package missing plugins as a separate RPM and then you can use it for your builds. | 15:45 |
| rinigus | submodule is just convenient way of doing the packaging | 15:45 |
| poetaster | ok. at some point I'll have to learn how to do that. | 15:45 |
| poetaster | yes, I know, I just don't know how to use them. And I hate git. with a passion :) | 15:46 |
| poetaster | I'm a darcs/fossil (svn, and even older) guy. | 15:46 |
| poetaster | rinigus: so I just create .gitmodules in my app git context and fill it with | 15:47 |
| poetaster | [submodule "Pillow"] | 15:47 |
| poetaster | path = Pillow | 15:47 |
| poetaster | url = https://github.com/python-imaging/Pillow.git | 15:47 |
| rinigus | poetaster: used to use svn and so on - so had to do transition myself. possible and, after bit of time, learn to use these new tools | 15:48 |
| rinigus | poetaster: no, you search on web "git submodules" and get lots of help | 15:48 |
| rinigus | you don't fill that file manually, use cmd tool for it | 15:49 |
| rinigus | poetaster: with Pillow - I would suggest to start with some other non-python code. some simple lib | 15:49 |
| poetaster | rinigus: yes, sorry, I was just being cheeky. I use 3 different systems as it is.... | 15:49 |
| rinigus | example: https://github.com/sailfishos-chum/libargon2 | 15:49 |
| rinigus | ok, I am off to code a bit :) | 15:50 |
| poetaster | rinigus: https://github.com/poetaster/harbour-simplesynth | 15:50 |
| poetaster | rinigus: ok, thanks and till then. | 15:50 |
| rinigus | poetaster: quick feedback - yes, it would make sense to have https://github.com/poetaster/harbour-simplesynth/tree/main/libsynth as submodule | 15:51 |
| poetaster | rinigus: ok, I'll do some reading. | 15:51 |
| poetaster | thanks. | 15:51 |
| rinigus | you're welcome | 15:52 |
| gatherer | Regarding org.sailfishos.secrets: How to administratively delete a collection using "secrets-tool --delete-collection org.sailfishos.secrets.plugin.encryptedstorage.sqlcipher XXXX" ? Error: Sailfish::Secrets::Result::ErrorCode(PermissionsError) "Collection XXXX is owned by a different application" | 16:57 |
| rinigus | poetaster: unless you want to spin-off libsynth, there is probably no point in having submodules in your example. (just a short not). | 16:59 |
| rinigus | assuming that the lab was developed for that app only | 17:00 |
| poetaster | rinigus: yeah, that's my quandry. sometimes it's not worth it. Also, using submodules is brittle. | 18:08 |
| poetaster | rinigus: libsynth is an odd example. i have to communicate with the author. it's a thing i really like and have two use cases for, but think won't get much traction. | 18:09 |
| poetaster | rinigus: so, it's probably ok 'as it is' as a static lib in a qt project. | 18:09 |
| poetaster | rinigus: my big problem is figuring out what i have to do in .pro (like target.path=/usr/share/harbour-simplesynth/lib) and what I can offload to the spec. | 18:12 |
| rinigus | poetaster: to pile problems - you should also look when to package libs as separate rpms and not try to bundle them into one mega-project. frei0r is a good example of something that should have been packaged separately from the start | 18:19 |
| rinigus | such package splitting would work really well on OBS | 18:20 |
| rinigus | as for PRO vs RPM - it is partially style. | 18:20 |
| rinigus | just imagine your software being used in some other Linux distro. then PRO would have to be "smart" part in the equation allowing to easily package in some other format. | 18:21 |
| rinigus | but sometimes it is just easier to do in RPM | 18:21 |
| rinigus | poetaster: ^ | 18:21 |
| rinigus | maybe one more aspect - RPM should deal with distribution-specific aspects. | 18:22 |
| poetaster | rinigus: having looked, for instance, at smurfy's packaging for fahrplan to cover a lot of distros (or you maps app, for that matter), I've been trying to get my head around the multi platform approach. | 18:28 |
| poetaster | rinigus: but it's also a question of priorities. the PRO approach yields resulst in the SDK, the rpm/spec approach independant of the SDK???? | 18:29 |
| rinigus | poetaster: lets skip multi-platform for now - it mainly requires rewriting QML into platform-independent and dependent parts. | 18:30 |
| poetaster | rinigus: yo. | 18:30 |
| rinigus | poetaster: PRO should be independent of SDK as well. I would put most to PRO | 18:30 |
| poetaster | wait, should go torture piggz on the other channel. | 18:30 |
| rinigus | enjoy! | 18:31 |
| poetaster | nah, he's already avoiding me :) | 18:31 |
| poetaster | rinigus: the problem is that somethings expressed in the pro files effect the build but are not apparent in the spec. | 18:32 |
| poetaster | rinigus: I think that's a no go in the long term. | 18:32 |
| rinigus | poetaster: don't think I follow. PRO takes care from sources to `make install`. all what is installed is packaged by SPEC. | 18:33 |
| poetaster | example: python.path = "/usr/share/harbour-simplecrop/lib" | 18:33 |
| poetaster | INSTALLS += python | 18:33 |
| poetaster | rinigus: ok. let me think about that a while. PRO to make, spec to install. sort of BuildRequires? | 18:34 |
| rinigus | poetaster: no, not buildrequires but %files section | 18:36 |
| rinigus | maybe you should select the solution you feel best about right now (PRO vs SPEC) and then it will be changed when you feel it is right. let's not overthink it too much | 18:37 |
| poetaster | rinigus: that's what I'm trying to figure out. at the moment I have two branches because I have both PRO and SPEC differences because of libs available in SFOS. | 18:38 |
| poetaster | rinigus: I'm taking about https://github.com/poetaster/harbour-simplecrop. | 18:38 |
| rinigus | poetaster: let me see | 18:38 |
| poetaster | rinigus: in 3.4 I have to supply the libs, but I've inherited the code and just cleaned it up enough to get into harbout. | 18:39 |
| x2s | Can someone tell me what version of Android apps are supported on the X? I forgot somehow... | 18:39 |
| poetaster | rinigus: in 4.1, there is a 'usable' library (PIL) available from jolla, but I can't Require it. | 18:39 |
| rinigus | poetaster: love to look into difference with 315 files changed :) | 18:40 |
| poetaster | rinigus: the german's have a saying 'suffering on a higher plane' | 18:40 |
| poetaster | rinigus: I'm working on a go project with about 150+ services. | 18:41 |
| rinigus | poetaster: I guess nobody will notice if you make one service extra... | 18:42 |
| poetaster | rinigus: it's actually nice. I like the fine grained approach. I also know you're right about keeping the libs out. | 18:43 |
| poetaster | rinigus: but we always have a compromise with including libs in sfos context. | 18:43 |
| rinigus | poetaster: in that simplecrop, I'd crop the libs out and build them separately. but it has been suggested all the way. if you do that, I will help you later to get them back into RPM | 18:44 |
| rinigus | looks like branch 4.1 has done that :) | 18:45 |
| poetaster | yup :) | 18:45 |
| rinigus | where is new PIL packaged? | 18:45 |
| rinigus | ... as a part of SFOS? | 18:45 |
| poetaster | yup. | 18:45 |
| poetaster | ideal :) | 18:45 |
| rinigus | poetaster: do you have github repo URL for PIL as done by jolla? | 18:46 |
| poetaster | but to get into harbour (I know, I know) I have to include it some perverse way. or convince them to include it. | 18:46 |
| rinigus | one problem in a time | 18:46 |
| poetaster | https://github.com/sailfishos/python3-imaging/blob/master/rpm/python3-imaging.spec | 18:47 |
| poetaster | actually, the jolla folk are working for me. I just can't use Requires depends. | 18:47 |
| rinigus | yes, you can't. but you can use buildrequires and then just `cp` all bunch to your /usr/shared/harbour-simplecrop/lib folder | 18:48 |
| poetaster | Yeah, I know I can just cp but I've never figured out which absurd macros get me from what part of the build to install. | 18:49 |
| poetaster | you pointed me to an example. sec. | 18:49 |
| rinigus | poetaster: let's take a simpler one - osm scout server. there are just libs in it, see https://github.com/rinigus/osmscout-server/blob/master/rpm/harbour-osmscout-server.spec#L100 | 18:50 |
| rinigus | so, you do that after you had your `make install` in SPEC | 18:50 |
| rinigus | and as you include full /usr/share/appname subfolder, it will get into files as well (see https://github.com/rinigus/osmscout-server/blob/master/rpm/harbour-osmscout-server.spec#L150) | 18:51 |
| rinigus | poetaster: ^ | 18:51 |
| poetaster | yo, but buildrequires python3-imaging won't put something in %{_libdir} to cp, now, will it? | 18:52 |
| poetaster | osmscout server scares the shit out of me ! | 18:53 |
| rinigus | poetaster: it will and that's a beauty of it | 18:53 |
| poetaster | BuildRequires: pkgconfig(mapnik) provides the files that are copied with .... | 18:53 |
| poetaster | cp %{_libdir}/libmapnik.so.3.0 %{buildroot}%{_datadir}/%{name}/lib | 18:53 |
| rinigus | exactly! | 18:54 |
| poetaster | ah. well, that's a fucking completely broken system if ever I've seen one :) | 18:54 |
| poetaster | sorry. I'm a scheme / erlang guy. I usually only touch c for embedded :) | 18:54 |
| rinigus | poetaster: broken is that we cannot have requirements. | 18:54 |
| rinigus | hence the "fix" | 18:55 |
| poetaster | true. true. true. | 18:55 |
| poetaster | I think I'm going to start threatening Jolla with money. | 18:55 |
| poetaster | Ok, I thinkg I'm slowly grokking how this could go in 3 directions at once. or rather, chum->openrepos, chum->harbour. | 18:57 |
| poetaster | there's still the problem of features allowed here/there. but that's a spec thing in the long term. | 18:57 |
| rinigus | great. back to coding ... | 18:58 |
| poetaster | rinigus: not so fast. python3-imaging in buildrequires doesn't get me to a simple copy paste. | 18:59 |
| poetaster | ah, but just go back to coding. | 18:59 |
| rinigus | poetaster: try to run `rpm -ql python3-imaging` on device with it. this is something you will need to copy and make sure python loads it from there | 19:02 |
| poetaster | rinigus: thanks! | 19:04 |
| rinigus | poetaster: welcome! | 19:05 |
| piggz | rinigus: how will your new encryption stuff handle native devices? | 20:32 |
| Flohack | Hello guys, we observe on UT that switching to 2G network speed will drop any data connection (will reestablish however when set to at least 3G again). Does that sound familiar? | 20:58 |
| *** amccarthy_ is now known as amccarthy | 22:26 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!