System_Error has quit [Remote host closed the connection]
Juest has quit [Ping timeout: 260 seconds]
System_Error has joined #maemo-leste
Juest has joined #maemo-leste
Juest has quit [Ping timeout: 268 seconds]
Juest has joined #maemo-leste
joerg has quit [Ping timeout: 264 seconds]
joerg has joined #maemo-leste
fab_ has joined #maemo-leste
Juest has quit [Remote host closed the connection]
Juest has joined #maemo-leste
xmn has quit [Ping timeout: 252 seconds]
ceene has joined #maemo-leste
fab_ has quit [Quit: fab_]
Danct12 has quit [Quit: ZNC 1.9.0 - https://znc.in]
Danct12 has joined #maemo-leste
asriel has joined #maemo-leste
pere has quit [Ping timeout: 245 seconds]
arno11 has joined #maemo-leste
pere has joined #maemo-leste
<arno11> Wizzup: (for _Gary issue) his el-v1.db seems ok because he said he can bring up sms in conversation.
<arno11> and sphone sms crash is normal in devel.
<sicelo> 'normal' :-P
<arno11> :P
<Wizzup> hm, ok
<arno11> _Gary: virtual keyboard doesn't work with Qt5 currently, but you can install Onboard keyboard as a workaround
<sicelo> arno11: i don't think i've seen sms crashes in sphone btw. or you mean with tp?
<arno11> yes i mean with tp
<arno11> otherwise everything is fine
<Wizzup> I think the whole sms part is disabled
<Wizzup> that's why it won't load
<Wizzup> but we can't then also have the icons go away based on leste-config
<Wizzup> I think that's the issue atm
<arno11> yes i think so
<arno11> that's a bit confusing
<Wizzup> yeah, it is
<Wizzup> this is mostly on me, I enabled the tp stuff in conversations/sphone and then went a bit MIA :D
<Wizzup> as far as dev work goes, but I'm going to pick \it up again
<Wizzup> if we can get it to work well then we can just not install the icons in a later version
<Wizzup> or make separate sphone pkgs for the icons
<arno11> yes indeed
<arno11> anyway your tp stuff works already really well on my device
<Wizzup> yes it does, but I didn't think about the migration path
<Wizzup> I think the 'best' way to solve the sms not working problem is to fix the sphone entries, maybe from within conversations, at least for now
<Wizzup> or maybe some postinstall script
<arno11> ah ok
uvos__ has joined #maemo-leste
<Wizzup> (we just need to set a sensiblew group_uid)
<uvos__> sphone isent acctually crashing right?
<Wizzup> no
<uvos__> ok it should just have no effect ans the main sphone process should print a warning into its log that a function with no available implementation was used
<uvos__> anyhow ill try and add an api for backends to be able to tell sphone what vcard field to use this week
<arno11> ah cool
<uvos__> (this is why the name lookup dosent work)
<uvos__> with tp
<uvos__> Wizzup: if you can tell me how exactly group_id should be set i can also just fix it in sphone
<uvos__> this would be best since it would also stop sphone from makeing entries conversations dosent like going forward
<Wizzup> yes we need both
narodnik has quit [Quit: WeeChat 4.2.1]
arno11 has left #maemo-leste [#maemo-leste]
<Wizzup> I'll give you the format in a bit
uvos__ has quit [Ping timeout: 272 seconds]
uvos__ has joined #maemo-leste
vectis has quit [Ping timeout: 256 seconds]
vectis has joined #maemo-leste
f_ has joined #maemo-leste
f_ has quit [Remote host closed the connection]
f_ has joined #maemo-leste
f_ has quit [Ping timeout: 260 seconds]
narodnik has joined #maemo-leste
_Gary has quit [Read error: Connection reset by peer]
_Gary has joined #maemo-leste
System_Error has quit [Ping timeout: 260 seconds]
System_Error has joined #maemo-leste
Gary_ has joined #maemo-leste
_Gary has quit [Ping timeout: 268 seconds]
mdz has joined #maemo-leste
narodnik has quit [Ping timeout: 255 seconds]
narodnik has joined #maemo-leste
enyc has joined #maemo-leste
xmn has joined #maemo-leste
pere has quit [Ping timeout: 260 seconds]
uvos__ has quit [Ping timeout: 240 seconds]
uvos__ has joined #maemo-leste
<Wizzup> uvos__: I wonder if we can use syncevolution to sync without using the maemo backends
<Wizzup> did you try this?
<Wizzup> I guess I mean to just sync against whatever syncevolution backends exist
<Wizzup> I'm mostly wondering since the maemo ones are still broken since chimaera, and otherwise I'll have to figure out how they broke
diejuse has joined #maemo-leste
<uvos__> Wizzup: i have no idea what the maemo backends do or what the point of them is in the first place, so i cant say
<Wizzup> so how did you use it in the past?
<Wizzup> (syncevolution)
<uvos__> i used syncevolution cli to setup the contacts with backend=evolution-contacts and backend=evolution-calendar
<uvos__> i then never used the calendar besides checking that it worked in principal as qcalendars ui is too broken
<uvos__> and then i used gome-contacts and sphone with the contacts database
<Wizzup> ok
<uvos__> and for sync i use syncevolution --sync refresh-from-remote
<uvos__> in cron
<uvos__> so what do the maemo backends do?
<Wizzup> so for contacts I think we already have evolution in our notes
<Wizzup> maemo-tasks, maemo-notes and maemo-events are what is referenced here: https://leste.maemo.org/Sync
<Wizzup> but I guess we could try backend=evolution-calendar instead of the maemo-events
<uvos__> ok yeah
<uvos__> hmm looks like this broke on some point
<uvos__> at least my qualendr is empty
<uvos__> on the plus side its seams to be less broken now
<uvos__> at least the weak has 7 days so thats nice
<uvos__> also the new event dialog looks correct now
<uvos__> neat
<uvos__> when did this happen?
f_ has joined #maemo-leste
<sicelo> i think there's always been 7 days in qalendar. problem was, and still is, the week numbers are one less than they should be
mdz has quit [Ping timeout: 252 seconds]
<Wizzup> uvos__: so it's broken for you too?
<Wizzup> uvos__: I think the new syncevolution just stopped working, but I thought it was maemo specific
<Wizzup> maybe I should do a new build first
<uvos__> Wizzup: it seams like the calendar broke somewhere yes
<Wizzup> doesn't look like anything changed in 2.0.0 since I made the package last year
<uvos__> not sure if its just qalendar
<Wizzup> well qalendar works for me
<Wizzup> can you run your sync script and see if it works ok
<uvos__> ill try to install evolution later and see if its just my setup
<Wizzup> well so we're on syncevolution 2.0.0 now
<Wizzup> we weren't on 2.0.0 before
<Wizzup> (trying again now)
<Wizzup> hm, /usr/libexec/evolution-addressbook-factory is using 100% cpu for 3 minutes now
<Wizzup> now it 'Aborted'
<Wizzup> right, this is what I remember seeing:
<Wizzup> Fatal: fieldlist '' not defined for fieldmap at line 3500 col 6
<Wizzup> Fatal error 20010, no valid configuration could be read from XML file
<Wizzup> [ERROR] internal error, invalid XML configuration (with datastores):
SystemError has joined #maemo-leste
System_Error has quit [Remote host closed the connection]
<Wizzup> I'll see if I can figure this out
narodnik has quit [Quit: WeeChat 4.2.2]
narodnik has joined #maemo-leste
narodnik has quit [Client Quit]
narodnik has joined #maemo-leste
<Wizzup> doesn't look like it changed...
pere has joined #maemo-leste
<Wizzup> It might be worth it for someone to see if this happens on debian bookworm
<Wizzup> they presumably have the same version
diejuse has quit [Quit: Client closed]
<Wizzup> it looks like this commit "XML configuration: always add mapping, using correct fieldlist name" might cause these issues
<Wizzup> that is 81cf7592b93a281944affd2a2c4a83bc4f68e1e0
<Wizzup> no, hm, that was there already...
f_ has quit [Remote host closed the connection]
f_ has joined #maemo-leste
<Wizzup> interesting, so it goes wrong with the maemo-events backend, but with backend=evolution-calendar it works
<Wizzup> I just sent an email to the syncevo list
<Wizzup> cc buZz <-- you never did, right?
<Wizzup> well, that's some progress at least
<Wizzup> also emailed the main author as it's not showing on their lists archive
uvos__ has quit [Quit: Konversation terminated!]
uvos__ has joined #maemo-leste
uvos__ has quit [Ping timeout: 264 seconds]
uvos__ has joined #maemo-leste
pere has quit [Ping timeout: 268 seconds]
ceene has quit [Ping timeout: 268 seconds]
pere has joined #maemo-leste
<Wizzup> hm...
<Wizzup> uvos__: how do I print all the syncevo dbs again
<Wizzup> not syncevo, but evolution
<Wizzup> because i'm not seeing the maemo targets in syncevolution --print-databases
<Wizzup> I wonder if that was the case on beowulf
mdz has joined #maemo-leste
<Wizzup> yeah ok so the maemo ones don't show up
<Wizzup> interesting
<Wizzup> maybe a bug in calendar-backend
<Wizzup> interesting
f_ has quit [Ping timeout: 260 seconds]
pere has quit [Ping timeout: 246 seconds]
<Wizzup> OK... it looks like I somehow didn't enable maemocal for the 2.0.0 build!!
<Wizzup> *cough*
* Wizzup looks around nervously
Livio has joined #maemo-leste
<Wizzup> yup, that was it, now to get it to compile when enabled :)
ac_laptop has joined #maemo-leste
ac_laptop has quit [Ping timeout: 268 seconds]
pere has joined #maemo-leste
ac_laptop has joined #maemo-leste
SystemError has quit [Remote host closed the connection]
SystemError has joined #maemo-leste
ac_laptop has quit [Read error: Connection reset by peer]
ac_laptop has joined #maemo-leste
<Wizzup> uvos__: syncevo should work again
ac_laptop has quit [Quit: WeeChat 3.8]
<buZz> Wizzup: i never did, indeed
<buZz> awesome @ findings :)
<Wizzup> it seems rather slow (the sync), but I'll let them run for a bit
<Wizzup> yeah ok, it works well now it looks like
<Wizzup> yay
parazyd has quit [Ping timeout: 245 seconds]
<uvos__> Wizzup: neat
<Wizzup> yeah I'm using it now
<Wizzup> the contact sync with my nextcloud is slow, but I don't know if that's syncevo or nextcloud :D
Livio has quit [Ping timeout: 264 seconds]
mdz has quit [Ping timeout: 264 seconds]