<Wizzup> freemangordon: I went into osso-addressbook and added a sip entry for my a contact, this crashed the addr book and when I now click on the contact again osso-addressbook also crashes
<Wizzup> freemangordon: https://pastebin.com/raw/ukf4xBNB
lolcat has joined #maemo-leste
lolcat is now known as lolcatw
<lolcatw> hello again
<dsc_> hi
<lolcatw> any reason why apt cant install scrot
<lolcatw> i did update && upgrade
<lolcatw> on the latest repos as well
<lolcatw> hmm
<gnarface> what is the error? apt usually tells you exactly why it can't install something...
<lolcatw> it just says unable to find scrot
<lolcatw> as if the package didnt exist
<gnarface> maybe it's named something else, try "apt-cache search scrot"
<gnarface> hmm, though... in devuan it looks like it's called scrot...
<gnarface> sorry, i'm not running maemo-leste yet, but it didn't look like anyone else is answering you
<gnarface> assuming it's supposed to have all the same packages as devuan, i'd suspect maybe an error in your sources.list
<gnarface> oh, maybe you need to "apt-get dist-upgrade" first to complete a release upgrade? that's another possibility... there's not many
<lolcatw> dist-upgrade never worked for me
<lolcatw> just noticed apt update gave some errors about some mirrors being unreachable
<lolcatw> will investigate
<gnarface> ah, yea that's probably the issue
<gnarface> fix that and run "apt-get update" again until you don't get errors
<gnarface> then the apt-get install actions should work right
<lolcatw> yeah all is good now
<lolcatw> i got some good screenshots out of it
xmn has quit [Read error: Connection reset by peer]
xmn has joined #maemo-leste
<dsc_> TIL scrot works
lolcatw has quit [Quit: had to jack off]
joerg has quit [Ping timeout: 252 seconds]
joerg has joined #maemo-leste
<freemangordon> Wizzup: what is the address you've added
<freemangordon> ?
<freemangordon> Wizzup: fixed, please upgrade
ceene has joined #maemo-leste
danielinux has joined #maemo-leste
danielinux has quit [Changing host]
ceene has quit [Read error: Connection reset by peer]
_CN_ has joined #maemo-leste
<Wizzup> freemangordon: ty, will test
<Wizzup> freemangordon: yes, works, ty
<freemangordon> :)
pere has quit [Ping timeout: 255 seconds]
arno11 has joined #maemo-leste
<arno11> this version of the plugin is buildable
<arno11> but a missing patch is needed
<arno11> to avoid hacking the .so file
<arno11> i tried this morning to use fb messenger with my wife through conversations and it works well
<arno11> with notifications
<freemangordon> wtym buildable?
<Wizzup> I think we do need to rework how some of the notifications work but it's a good start
<Wizzup> freemangordon: as in it's not in debian
<Wizzup> I guess
<Wizzup> so it needs packaging
<Wizzup> this is just the tp fb connection manager
<freemangordon> ah, ok
<Wizzup> I also packaged the slack purple plugin btw, iirc
* freemangordon wonders why it not in debian
<freemangordon> what strange source format :)
<arno11> yeah we have almost no plugin in debian
<freemangordon> like, is everything a patch?
<arno11> yes kind of
<freemangordon> ah, this is on top of libpurple-facebook?
<arno11> weird stuff
pere has joined #maemo-leste
<Wizzup> oh
<freemangordon> hmm, I am not sure we want that
<Wizzup> Purple Facebook implements the Facebook Messenger protocol into pidgin, finch, and libpurple. While the primary implementation is for purple3, this plugin is back-ported for purple2.
<Wizzup> do we need that?
<freemangordon> no :)
<freemangordon> we'd rather check why upstream does not work and fix it
<freemangordon> arno11: did you try upstream libpurple-facebook?
<Wizzup> what is upstream?
<freemangordon> trying to find
<Wizzup> I think this might be upstream
<arno11> can't find it and with no hack, impossible to get it work anyway iirc
<freemangordon> yes, this is the upstream
<freemangordon> "The purple-facebook plugin is a replacement for the builtin Facebook XMPP plugin."
<freemangordon> so it seems to patch libpurple
<freemangordon> instead of creating a new plugin
<arno11> yes ofc but that's not enough probably
<freemangordon> arno11: just thinking out loud
<freemangordon> and yes, probably not enough
akossh has joined #maemo-leste
<arno11> yep
<freemangordon> Wizzup: hmm, seems purple3 is not yet release
<freemangordon> *released
<freemangordon> arno11: so, you buld that like, patching with it libpurple?
<arno11> yes
<freemangordon> I see
<freemangordon> Wizzup: looking at the patches, does not seem bad
<arno11> the important patch is the last one (20th)
<arno11> just fyi
<freemangordon> ok
<freemangordon> Wizzup: so, besides that it brings deprecated/removed code back (IIUC) it does not look bad
<freemangordon> though, I wonder why was that never sent for upstreaming in libpurple
<arno11> good question
<freemangordon> umm....
<freemangordon> I don;t get that
<freemangordon> see Facebook
<freemangordon> ok, so this is the 'official' plugin
<arno11> and ?
<arno11> kind of lol
<Wizzup> freemangordon: so we need to pull in the old repo and then put this all in debian/patches ? or ?
<freemangordon> still don;t understand :)
<freemangordon> that's what I am trying to find
<Wizzup> why.jpg :)
<freemangordon> hmm?
<freemangordon> ok, it pulls revision 9ff9acf9fa14 an dapplies patches on top
<freemangordon> which is what we are not going to do :)
<freemangordon> or, can we?
<freemangordon> hmm, ok
<freemangordon> it builds SUBDIRS = pidgin/libpurple/protocols/facebook
<freemangordon> so ok, looks fine to me
<freemangordon> Wizzup: it already seems to have packaging
<freemangordon> we have to add gbp.conf only
<Wizzup> ok, let's put it in upstream-forks then?
<Wizzup> or do we want it in extras? (or both I guess)
<freemangordon> I think this belongs to extras
<Wizzup> ok
<freemangordon> extras
<Wizzup> freemangordon: do you have a fb account so you can test it, btw?
<freemangordon> ok, I'll create accounts plugin that will depend on that
<freemangordon> yes, I have
<arno11> or you can use a fake one, like me... :P
<Wizzup> arno11: not sure you managed to do it, I tried it once a few years ago under a fake name and they wanted my passport, and blocked me quickly afterwards
<arno11> ah really bad lol
<freemangordon> ok, have to run, ttyl
<arno11> anyway this plugin 'story' is really cool, i'll have a look later and see if i can get working other plugins
<freemangordon> I wonder why tp does not have mqtt plugin
<freemangordon> and isn't it a good idea to write one
<Wizzup> if given unfinite time :)
<freemangordon> :)
<freemangordon> ok
<freemangordon> bye
<Wizzup> let's first prove that we can actually make something that works ok using tp :P
<freemangordon> bbl
<Wizzup> we still have many challenges ahead like fetching xmpp history (xep 0313) and OMEMO keys
<bencoh> does any project still use tp btw? sailfishos maybe?
<Wizzup> yes
LjL has quit [Read error: Connection reset by peer]
LjL has joined #maemo-leste
parazyd has quit [Ping timeout: 256 seconds]
parazyd has joined #maemo-leste
uvos__ has joined #maemo-leste
<uvos__> tp being very big and essentally unmaintained for a long time worries me (and is the reason for me writeing sphone the way i did)
<Wizzup> it's relatively well documented, albeit complex, but has superior design to say just libpurple
<Wizzup> I'm confident we can work these things out
<Wizzup> like, having the chat protocol handlers in the same process is just a nightmare
<Wizzup> or requiring specific code/abi
<Wizzup> TP really got this right
<Wizzup> uvos__: btw regarding new stable, I think from my pov when we get conversations/tp working reliably (perhaps with sip/xmpp voice calls) we can start the move to the new stable, from my pov
<Wizzup> there is still gconf in current stable
<Wizzup> just python2 is lacking
<uvos__> ok, honestly python2... good ridance
<uvos__> (i know this means not gtk2 bindings)
<uvos__> i wonder who is still holding gconf in stable
<uvos__> considering they marked it depicated manny years ago now
<Wizzup> yes, with the python2 drop we lose some bindings and as a result a few extras apps
<Wizzup> I think I posted a list last week
<Wizzup> it's nothing too major but just sad because it means we'll have lost our python bindings
<Wizzup> we could of course make new ones with the better tooling that exists now
<Wizzup> but in general python/gtk2 is a dead end, so then we need gtk3 first really :)
<Wizzup> so in practice we have to live with losing a few python apps
<Wizzup> 20:22 < Wizzup> these packages will not work anymore: binaryclock-plugin, quicknote, sojourner, syncevolution-frontend, modrana
<Wizzup> 20:23 < Wizzup> python2-gconf python-conic python-hildon python-hildondesktop python-location python-mafw python-osso
<Wizzup> sojourner is sad because I still use it every fosdem :P
<sicelo> there's confclerk
<Wizzup> ?
<Wizzup> ah a different app?
<sicelo> yes
<sicelo> was originally made for maemo devices ;-)
<uvos__> i mean ok but most of those are not really usefull
<uvos__> binaryclock-plugin is just a meme and syncevolution-frontend dosent work at all anyhow
<Wizzup> yes binaryclock-plugin was a way to test the python bindings for status area
<uvos__> quicknote is easly replaceable, and sojurner appreantly has an alternative
<Wizzup> syncevo frontend works if the backend work
<Wizzup> s
<uvos__> nah the ui is really broken
<uvos__> even when the backends worked
<bencoh> modrana will really make some people sad I think
<uvos__> yeah modrana is usefull
<Wizzup> it has a qt5 backen
<Wizzup> d
<bencoh> oh
<Wizzup> just the maemo specific one is gtk2
<Wizzup> I think
<bencoh> hmm
<Wizzup> this was just me searching debian/control
fab_ has joined #maemo-leste
<uvos__> porting to everything to gtk3 would be a lot of work (even if some bits exist allready)
<uvos__> i also worry this could mean the end of n900 support
<freemangordon> why is that?
<freemangordon> qt5 (for example) works well on it
<uvos__> gtk3 (and especcaly gtk4) needs more ram, n900 is pretty at the eadge allready
<uvos__> yeah but if everthing where qt5, i dont think it would do so well
<freemangordon> well, we have maemo-launcher for that :)
<uvos__> that cant possibly help
<freemangordon> sure it can
<uvos__> it dose not even save any ram really for gtk2
<freemangordon> all thge static data etc is shared amongst the processes
<freemangordon> ok, lets not go into that
<uvos__> its like 100kb per process, and it uses some memory itself and needs like 6 apps to even break even
<uvos__> this wont save you from qt/gtk3+
<freemangordon> we shall write qt booster anyway
<Wizzup> I think we'll just see when we get there
<freemangordon> :nod:
<Wizzup> whether or not we can support n900 in a few years from now :)
<freemangordon> at some point we'll drop support, but I doubt gtk3 will be the reason
<arno11> the end of 2g and 3g in Europe in 2025 is far more problematic imo, for n900 and d4
<Wizzup> we'll see if that actually happens (everywhere)
fab_ has quit [Quit: fab_]
<arno11> gb, france, spain, belgium, netherlands, germany, most WE countries anyway
<freemangordon> I doubt it will
<freemangordon> but yeah, will see
<arno11> yeah in fact
<Wizzup> tmobile keeps 3g on indefinitely in the netherlands fyi
<Wizzup> also many smart meters and such need 2g or 3g
<Wizzup> at least indefinitely for now
<arno11> indeed
<Wizzup> in any case let's not worry about the inevitable :)
<uvos__> in germany 3g is gohne (as it is in most places by now)
<uvos__> but 2g is staying until 2030
<Wizzup> yeah, but it's going strong in austria still, kind of funny :D
<uvos__> montain germans are allways more conservative
<arno11> lol
<freemangordon> :D
<bencoh> I'm quite happy to know that they'll keep 2g over 3g tbh
<arno11> that's kind of common sense
<Wizzup> uvos__: :D
<bencoh> arno11: some places talked about killing 2g before 3g
<Wizzup> the netherlands is it seems
<Wizzup> 3g is supposedly covered by tmobile and 2g by kpn, but kpn is talking about shutting off 2g in 2025
<bencoh> :/
<Wizzup> well there's a reason I left the country :P
<arno11> bencoh: burocratic stuff probably...
parazyd has quit [Ping timeout: 260 seconds]
<arno11> Wizzup: following 2g is now a road trip :D
parazyd has joined #maemo-leste
<Wizzup> Not sure if I get it
<arno11> anyway
<arno11> btw the end of a working solution for whatsapp was a major concern for lot of maemo users iirc, seems possible again (to get it working)
<uvos__> they pretty agressively block 3rd party clients
<uvos__> so i dont think its really possible in a practical sense
<arno11> yes i know but seems to work through pidgin
<uvos__> for now
<arno11> ofc
<arno11> working for 2 years already
<arno11> the name is purple-gowhatsapp for who is interested
<arno11> it uses go language mostly
<arno11> i'd like to try it but don't wan't to give my phone number to meta...
uvos__ has quit [Ping timeout: 276 seconds]
fab_ has joined #maemo-leste
_CN_ has quit [Ping timeout: 245 seconds]
arno11 has left #maemo-leste [#maemo-leste]
fab_ has quit [Ping timeout: 276 seconds]
<Wizzup> arno11: doesn't that require you to also have an android phone?
Pali has joined #maemo-leste
arno11 has joined #maemo-leste
<arno11> Wizzup: you mean for auth ?
sch has quit [Ping timeout: 260 seconds]
sch has joined #maemo-leste
<Wizzup> arno11: well in general, can you use it without having android/ios?
<arno11> yes apparently
<Wizzup> that's cool, we should use that.
<Wizzup> reading the set-up we will run into some problems :p https://github.com/hoehermann/purple-gowhatsapp
<Wizzup> > Using your phone's camera, scan the code within 20 seconds – just like you would do with WhatsApp Web.
<arno11> yes indeed
<Wizzup> uhm
<arno11> tricky
<Wizzup> doesn't that mean ios/android phone?
<arno11> just for authentification apparently
<Wizzup> well yes
<Wizzup> but you'll have to own one
<arno11> probably
<Wizzup> 'buy an android phone to use whatsapp on maemo leste' doesn't sound quite the same :(
<arno11> indeed
<Wizzup> but yeah, since whatsapp added whatsapp web and multi-device support, there are some ways to use it
<Wizzup> I used to have a vm running anbox just for wa
<Wizzup> but they still banned me iirc
<Wizzup> many years ago
<arno11> ah ok
<Wizzup> this might be better
<Wizzup> oh no, they didn't ban me
<Wizzup> buy I bought a one-off sim card for it and lost the number
<Wizzup> so I was locked out after many years
<Wizzup> :)
<arno11> :)
<freemangordon> arno11: hmm, how did you manage to build that FP plugin?
<freemangordon> doing ./update.sh does nothing
<freemangordon> with no error message whatsoever
<arno11> ah yes let me check
<freemangordon> please, someone that is good at scripting:
<freemangordon> HASHG=$(_TMP_=$(type hg 2>&1); echo $?)
<freemangordon> wtf?
<arno11> i've been able to build v0.9.6
<arno11> master doesn't work
<freemangordon> does not work as in?
<arno11> not able to make
<arno11> even not able to configure
<freemangordon> ok
<arno11> but works from v0.9.6
<arno11> but you need to add the 20-something patch to it
<freemangordon> did you install mercurial
<freemangordon> ?
<arno11> nope
<freemangordon> well...
<freemangordon> it needs hg to pull pidgin
<arno11> ah i remember
<arno11> i used the tarball
<freemangordon> aha
<arno11> this way no mercurial needed
<freemangordon> so I would prefer master
<Wizzup> we can depend on hg in our ci
<freemangordon> mhm
<freemangordon> but I want first to see what exactly it pulls
<Wizzup> python
<Wizzup> :)
<freemangordon> like, what goes into the source package
<Wizzup> ah
<freemangordon> because I can simply add source files by hand in our repo
<freemangordon> or, maybe it is smart enough
<freemangordon> hmm, it seems it is
<freemangordon> still, debian packaging is semi-broken
<Wizzup> as usual, things are a bit broken :)
<freemangordon> mhm
<freemangordon> it does not execute autogen.sh
<freemangordon> so pidgin files will not be pulled
<freemangordon> I have to fix that it seems
<Wizzup> wait, doesn't debian do that automatically?
<Wizzup> are their rules overwriting the default stuff?
<freemangordon> no
<Wizzup> it does afaik
<freemangordon> autogen.sh is just a random file :)
<Wizzup> well it will run autoreconf or so
<Wizzup> ah
<freemangordon> autoreconf yes
<Wizzup> lol
<freemangordon> we have some packages that call autogen from their rules
<freemangordon> I have to find one to borrow the code
<freemangordon> ok, builds fine
<arno11> cool
<freemangordon> ugh, that created 200MiB source tarrball
<arno11> ???
<freemangordon> for some reason it includes .git .pidgin .travis etc
<arno11> ah ok
<arno11> otherwise it is only 500k lol
<Wizzup> arno11: I think there is some eu law coming in 2024 where these gatekeeper companies need to offer apis to their chat iirc
<Wizzup> In 2022, the EU said that interoperability for messaging platforms was a key requirement for messaging services from gatekeepers. In other words, people who use Signal, Telegram or Snapchat will be able to send messages to WhatsApp and Messenger users without having to create a WhatsApp or Messenger account.
<Wizzup> yeah should be live march 2024
<arno11> really interesting
<Wizzup> let's hope they just pick xmpp for interop...
<Wizzup> probably won't but hey.
<arno11> who knows
uvos__ has joined #maemo-leste
* uvos__ plays the 9th symphony
<Wizzup> lol
<Wizzup> there are also a lot of things I disagree with (like the central digital identity and storage of all eu citizen data), but yeah this might be good
<arno11> all citizen data @the same 'place' makes me worried about who will manage that...
<Wizzup> in general it's just a bad idea to centralise any of this
<Wizzup> but then again the netherlands did the same thing with all healthcare data
<Wizzup> (another reason to leave :P)
<arno11> :)
<uvos__> consumer protection from large private interest has been mostly good recently
<uvos__> but yeah protection from state intrest, less good
uvos__ has quit [Ping timeout: 260 seconds]
pere has quit [Ping timeout: 260 seconds]
<freemangordon> Wizzup: do you know how to tel gbp buildpackage to not include some directory in the source tarball?
fab_ has joined #maemo-leste
<freemangordon> *tell
<Wizzup> freemangordon: not really, maybe just remove them?
pere has joined #maemo-leste
fab_ has quit [Ping timeout: 252 seconds]
<freemangordon> Wizzup: could you add https://github.com/maemo-leste-extras/purple-facebook to ci
<freemangordon> and perhaps build it for extras-testing if possible
<freemangordon> I don;t dare after the last time it took me 10 attempts to build OMP :)
arno11 has left #maemo-leste [#maemo-leste]
<Wizzup> freemangordon: will do
<Wizzup> freemangordon: I don't know if extras-testing is the right thing, but I did this:
<Wizzup> ./run-job.py -d chimaera-testing -r extras -j jib
<Wizzup> oh wrong pkg
<Wizzup> :D
<Wizzup> freemangordon: it built