Monday, 2026-05-11

piggz[m]ViGe: are you sure its a flip? that route appears to be on 'Null Island'14:13
piggz[m]https://en.wikipedia.org/wiki/Null_Island14:13
ViGehmm14:53
ViGeI suppose you are right then14:53
ViGeIt's strange that when I look at the route in amazfish, the displayed coordinates are correct, but the route is drawn on Null Island14:55
piggz[m]when it reads points, the protcol works by sending start + offsets, rather than coordinates, so, the iniital start point must be wrong15:01
piggz[m]ill need to know if it does this every time ... and device type, bip?15:02
ViGeit's bip15:03
ViGeI'll try later today if it does it every time, I'm in a meeting right now so I can't test15:03
nephrosI wonder if it would make sense to "freeze Chum in time" for all repos <5.1 , and make a fresh one for anything starting with that.17:59
nephrosMaintaining packages to be compatible throughout SFOS history just became a lot more difficult.17:59
nephrosOr maybe not "freeze" but have "chum:legacy" and the current one.18:02
Ketonephros: I was thinking how to solve that problem, but couldn't come up with a simple solution yet18:15
Ketothe problem being that some packages can't be built from the same source/version for all SFOS versions, if I understood right18:16
KetoI think the core of the problem is they are built in one project for all SFOS versions18:19
Ketowe could possibly change it so that there is a chum "source" project that does not actually build anything, and then there would be chum:X.Y projects that link to the "source" project, and build against just the specific SFOS version18:25
Ketothen packages needing different sources can be overwriten in the chum:X.Y projects, and others just use the sources from the "source" project18:27
Ketobut it would still require quite a lot of maintenance work18:29
nephrosKeto: And wouldn't that create many different (package/download) repos?19:31
nephrosSo more management on the user or Chum GUI side?19:32
nephrosThe way it it now I predict either many pkgs will get two versions, or old SFOS repos will just be disabled or stay 'failed/unresolvable'19:34
nephrosI mean great majority of users will be always on latest (or one version behind), but it's nive being able to support old versions.19:42
nephros*nice19:43
nephros(my daily is still on 4.4 :) )19:44
attahbut whyyy?19:49
nephrosattah: 4.4? Meh initial reason was the Android Ichon change which I don't like still.19:50
nephroslater I didn't dare because the phone is full of hacks.19:50
attahA week or two later i no longer noticed the icons19:50
attahAh. I haven't patched anything in like forever.19:51
Ketonephros: no, there would be just one repo per sailfish version, like it is now19:52
nephrosNow I'll just wait for the J2 and retire the X10iii daily.19:52
nephrosKeto: I see. Hm could work. I'm just thinking up until 5.0 the current chum way worked more or less fine.19:53
nephrosBut with the (nice) major base changes in 5.1 that will become unfeasible.19:54
nephrosSo my idea would be just a new chum:5.1, and leave the current one as is.19:55
nephros(or call it :legacy)19:55
piggz[m]its sooo boring enabling qt5 and kf5 for chum19:55
KetoI'll try to make example project setup with some packages tomorrow to demonstrate how it could work19:56
nephrospiggz[m]: I'd help but I'm a bit burned out from the weekend.19:56
piggz[m]its fine, ill be taking next week off19:56
nephrosI hate python packaging. That PEP moving away from setup.py is a dumpster fire.19:57
nephrosI wonder if 'new' chum could be a branch. so anything that can't go into old chum goes into the branch and then break the link (osc detachbranch).20:02

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