[10:57] <BluesKaj> Hi folks
[11:53] <crydotsnake-M> hello
 hi
[12:05] <crydotsnake-M> Hello Rik! :)
[12:13] <crydotsnake-M> How many testers we have?.
 4 or 5 regular ones I think
 who are not developers or other team  I mean
[12:23] <crydotsnake-M> Okay.
[12:24] <crydotsnake-M> And what i have to do, to be a Tester?. Just contribute?.
[12:24] <RikMills> yep
[12:24] <crydotsnake-M> Okay :)
[12:25] <crydotsnake-M> It is a great feeling, to make software better and better
[13:54] <mparillo> There is a team, https://launchpad.net/~kubuntu-testers but I am not sure what that does.
[13:55] <crydotsnake-M> I'm already in that Launchpad Group.
[13:56] <mparillo> Excellent. Does anybody here have authority to add you to the testers factoid?
[14:05] <RikMills> ubottu: !testers is ,reply> Help is needed in #kubuntu-devel. Please ping RikMills, soee, BluesKaj, lordievader, mamarley, mparillo, wxl, DarinMiller, tsimonq2 for more information.
[14:06] <RikMills> ubottu: !testers is ,reply> Help is needed in #kubuntu-devel. Please ping RikMills, soee, BluesKaj, lordievader, mamarley, mparillo, wxl, DarinMiller, tsimonq2 for more information.
[14:06] <RikMills> ubottu: !testers is <reply> Help is needed in #kubuntu-devel. Please ping RikMills, soee, BluesKaj, lordievader, mamarley, mparillo, wxl, DarinMiller, tsimonq2 for more information.
[14:07] <crydotsnake-M> Cool!
[14:07] <RikMills> ubottu: !testers-#kubuntu-devel  is <reply> Help is needed in #kubuntu-devel. Please ping RikMills, soee, BluesKaj, lordievader, mamarley, mparillo, wxl, DarinMiller, tsimonq2 for more information.
[14:07] <crydotsnake-M> I dont know mparillo 
[14:08] <crydotsnake-M>  * testers factoid ? @_freenode_mparillo:kde.org
[14:08] <RikMills> mparillo: nope, I don't
[14:08] <crydotsnake-M> Ah you mean to the !testers command?
[14:09] <crydotsnake-M>  * Ah you mean to the !testers command :D
[14:09] <crydotsnake-M> RikMills: Do you think it is importand to have Programming Experience as a tester?
 no
[14:17] <BluesKaj> RikMills, ping
[14:18] <RikMills> ?
[14:18] <crydotsnake-M> Okay.
[14:18] <crydotsnake-M> I want to learn Python
[14:18] <BluesKaj> hehe ok, RikMills what's up?
[14:18] <crydotsnake-M> Maybe i should read my book about learning Python.
[14:19] <RikMills> BluesKaj: factiod can't be edited, that is all
[14:22] <BluesKaj> ok
[14:23] <crydotsnake-M> Anyway, i'm in the Kubuntu Testers launchpad group, that is a good start i think :)
[14:48] <santa_> good afternoon everyone
[14:48] <crydotsnake-M> Hello! :)
[14:54] <santa_> RikMills: I will have a look @ the akonadi issue whenever I have time
[14:55] <santa_> this probably needs discussion with upstream, it doesn't seem a good idea to change the underlying database just because we can
[14:56] <santa_> for now, could you please summarize the problem, it fails to start or what?
 yes, can't start
 mysql-5.7 will be removed, so we can't stay with that
 mysql-8 can't make a new database, or use an existing one
 mariadb can
[15:10] <RikMills> santa_: ^
 rik , how can i reset akonadi
 managed to get mariadb running ... but using 10.4 from mariadb repo
 i doesn't know why 10.3.x in archieve failed to start
[15:11] <RikMills> it starts here :/
[15:11] <santa_> ok, RikMills and 5.7 is going to be removed ... when?
 @RikMills, :(
[15:12] <RikMills> santa_: before eoan release. some of its packages are already taken over by 8 I think
[15:12] <santa_> and you know that because...
[15:13] <RikMills> I asked in release
[15:14] <santa_> ok, and they told you, do you remember the date and hour or do you have the backlog?
[15:14] <ejat> https://paste.ubuntu.com/p/g5Qn3m6dbp/
[15:15] <RikMills> [20:42] <RikMills> I assume mysql-5.7 is going to be removed completely soon?
[15:15] <RikMills> [20:43] <vorlon> I can't speak to the timeline on that
[15:15] <RikMills> [20:43] <vorlon> I expect it would be removed before release
[15:16] <santa_> so maybe we can ask them to keep it
[15:16] <santa_> maybe
[15:16] <RikMills> ejat: well, if you don't mind nuking it, then rm -fr .config/akonadi/ .local/share/akonadi/
[15:17] <RikMills> santa_: well, we can't build against it any more, as the -dev packages are taken over by v8
[15:17] <santa_> ok
[15:17] <RikMills> but I want to be prepared, as I suspect they will want it to go
[15:18] <ejat> doesnt have .local inside .config/akonadi 
[15:18] <RikMills> ejat: its not inside there
[15:18] <RikMills> ejat: rm -fr ~/.config/akonadi/ ~/.local/share/akonadi/
[15:19] <RikMills> if you prefer
[15:19] <RikMills> while akonadit is stopped
[15:19] <RikMills> *akonadi
[15:19] <blaze> wait
[15:19] <ejat> owh .. u mean thats 2 folder .. 
[15:19] <ejat> ok my bad 
[15:20] <RikMills> blaze: yes?
[15:20] <blaze> removing ib* files inside akonadi folder should be enough
[15:21] <santa_> RikMills: ok, so last but not least how I can reproduce the problem? Just starting akonadi in eoan? or something else?
[15:21] <RikMills> santa_: akonadictl start
[15:21] <ejat> https://paste.ubuntu.com/p/9PKH5nF4Qy/
 (Photo, 371x354) https://irc-attachments.kde.org/tC2klDZE/file_17372.jpg I mean these two
[15:22] <RikMills> santa_: once you have installed mysql-client-core-8.0 and mysql-server-core-8.0
[15:23] <santa_> RikMills: so without them it works?
[15:24] <RikMills> santa_: it obviously works with 5.7, and it also works if you switch to mariadb equivalents
[15:24] <RikMills> just not with mysql 8 ones
[15:25] <RikMills> not even if you completely disable apparmor
[15:25] <santa_> ok, so I have now a good overview, thank you very much
 @ejat, 👆🏻
 @myfenris, I can't recreate that, so not sure how to solve it
[15:28] <ejat> i need to adduser at the db ? 
[15:29] <RikMills> I didn't need to here
[15:30] <blaze> you don't need a standalone setup, just the *-core libraries
[15:31] <blaze> same as mysql before
[15:31] <RikMills> indeed
[15:31] <ejat> yeah .. 
[15:33] <ejat> https://paste.ubuntu.com/p/ZZFsNmc47p/
[15:33] <ejat> :(
[15:35] <RikMills> santa_: FYI, akonadi 19.08 also does not work with mysql-8
[15:36] <RikMills> in case you wondered
[15:36] <santa_> ok fine
[15:38] <ejat> https://www.linuxquestions.org/questions/slackware-14/akonadi-and-mariadb-10-2-8-a-4175612895/page3.html
[15:39] <ejat> wondering why fresh installed working fine 
[15:39] <ejat> @RikMills your VM not using KCI ? 
[15:40] <RikMills> nope
[15:40] <RikMills> using freah eoan install
[15:41] <RikMills> *fresh
[15:43] <ejat> okie 
[15:48] <ejat> https://paste.ubuntu.com/p/PmmQwt2W7h/
[15:48] <ejat> bug 1797643
[15:49] <ejat> related to apparmor 
[15:50] <RikMills> yes, that was fixed
[15:51] <RikMills> I hav no apparmor denials with mariadb
[15:54] <RikMills> well, not that stop akonadi starting, or that match what you pasted, anyway
[15:57] <blaze> I've managed to start akonadi against mariadb just now with existing database
[16:00] <RikMills> blaze: yeah, that is why I was pondering a switch
[16:03] <ejat> from the bugs seem not fully fixed :( 
[16:05] <blaze> libqt5sql5-mysql depends on libmysqlclient21 (>= 8.0.11), that's questionable since I only have mariadb now
 https://paste.ubuntu.com/p/SjWddCWmMR/
 🤔
 hmmmm
 @RikMills given the mysqld-akonadi complain mode
 works!
 i should not nuke the akonadi at the 1st place .. but nevermind ..
 i seldomly used kmail nowdays ..
 either mailspring @ thunderbird
 thunderbird FTW
 @RikMills, 💪🏻
[16:40] <blaze> is there a need for an upgrade script, nuking the old mysql files?
 doesn't seem so with mariadb
[16:42] <blaze> good
[16:43] <RikMills> that would need to be tested with a disco to eoan upgrade as well though
[16:43] <RikMills> where akonadi version changes
 finally my nightmare (can't start mariadb + akonadi) disappear ..
 😅
[18:39] <santa_> RikMills: while I prepare myself to dig into the akonadi issue ... do you have a few minutes to talk about a few easier things?
[18:49] <RikMills> santa_: ok
[18:54] <santa_> RikMills: ok, first of all kservice. I have seen you made a patch to fix the autotest issue, the change apparently wasn't pushed to git
[18:54] <santa_> also, may I try to convince you to use the upstream patch instead?
[18:55] <santa_> https://build.kde.org/job/Frameworks/job/kservice/job/kf5-qt5%20SUSEQt5.12/
[18:55] <santa_> I think build #43 fixed the issue in question
[18:56] <santa_> https://build.kde.org/job/Frameworks/job/kservice/job/kf5-qt5%20SUSEQt5.12/43/
[18:56] <RikMills> 404 on that link
[18:56] <santa_> wat
[18:56] <santa_> it works here
[18:56] <RikMills> did 2nd time here
[18:57] <santa_> ok
[18:57] <santa_> the second one is the build #43
[18:58] <santa_> if you click on changes -> cgit that would bring you this:
[18:58] <santa_> https://cgit.kde.org/kservice.git/commit/?id=f5b0223325c72d4d29d6f7e9e1355455355d3981
[18:58] <santa_> which is, I believe, the upstream patch to solve the problem
[18:58] <RikMills> I looks at that. it is already in 5.61
[18:58] <RikMills> *looked
[18:59] <santa_> also just FTR with or without it, it doesn't seem to fail in my test build servers
[19:00] <santa_> * without it
[19:00] <santa_> I haven't tested with it
[19:00] <RikMills> it didn't fail either when I tres in lxd autopkgtest. but it failed on ubuntu infra
[19:00] <RikMills> *tried in
[19:00] <santa_> yeah, I guessed that must be one of these complicated corner cases
[19:01] <RikMills> yeah
[19:01]  * RikMills pushed changes
[19:02] <santa_> thanks, whenever you have time please consider the upstream patch. move to the next issue [y/n]?
[19:03] <RikMills> santa_: I can't consider the upstream patch, as it was included in the 5.61 tar
[19:03] <RikMills> which is why I gave up at that point
[19:04] <santa_> oh, sorry, ok I misunderstood
[19:04] <RikMills> I though it looked an obvious fix, and I missed the date
[19:04] <RikMills> then was quite suprised to fix it already in the tar
[19:05] <RikMills> *to find it
[19:05] <santa_> so the only actual issue was pushing the thing to git which you already solved
[19:05] <santa_> so, move to the next issue [y/n]?
[19:05] <RikMills> y
[19:06] <santa_> ok, kirigami-gallery
[19:07] <santa_> this doesn't exist in our git repos so it was triggering a bug in git-clone-all which is fixed in the master branch
[19:07] <santa_> in addition to that ... maybe we should package it?
[19:08] <RikMills> it has been started in debian by sgclark 
[19:08] <santa_> yes, I know it's an example program, but still it would nice have
[19:08] <santa_> yeah, I was about to say that, apparently we already have some packaging available
[19:08] <RikMills> if debian don't get to an upload then we can do it I guess
[19:09] <santa_> I mean it's part of apps and seems better to upload it than adding it to the skip list
[19:09] <RikMills> I'll see if scarlett has any ETA
[19:09] <santa_> regarding example/demo programs it's nice to have them
[19:10] <RikMills> yep
[19:10] <santa_> for instance some time ago I did a talk @ university about Qt and it was nice to have the qt example/demo programs packaged
[19:10] <santa_> "look how awesome Qt is"
[19:11] <santa_> and well I already said all I wanted to say about kirigami-gallery, so move to the next one [y/n]?
[19:11] <RikMills> apparently in ftpmasters new queue
[19:12] <RikMills> given how they ignore low priority stuffm maybe we should get on it
[19:13] <santa_> when it comes to debian's mighty NEW queue, you can safely assume that things there might take from weeks to months to be processed
[19:14] <santa_> needless to say I used to work for debian, so I know how "wonderful" is that
[19:15] <santa_> anyway, move to the next topic [y/n]?
[19:15] <RikMills> lets take a look at the packaging in the next week or so. see what we think
[19:15] <RikMills> y
[19:16] <santa_> ok
[19:16] <santa_> last time I tried an initial build of apps 19.08 they were a few things broken
[19:16] <santa_> i.e. the source package doesn't build
[19:17] <santa_> is everything pushed to git?
[19:17] <santa_> if yes, may I fix things?
[19:17] <RikMills> there where some respins IIRC
[19:17] <santa_> ok
[19:18] <santa_> also regarding the branch naming 'kubuntu_fseries_staging'...
[19:18] <santa_> maybe it would be better to use 'kubuntu_eoan_backports'?
[19:18] <RikMills> might be
[19:19] <santa_> so this way we won't have a branch which would have to be 'renamed' in a couple of months
[19:19] <santa_> not a big tragedy, but it seems to me the 'kubuntu_eoan_backports' naming would be the path of least resistance
[19:19] <RikMills> I think the only build fail I had in the end was cantor, and that was only because new julia FTBFS in proposed on some arches
[19:22] <RikMills> let me ponder
[19:23] <santa_> I had some packages failing with "do-all gbp-tritemio" because some patches were already applied upstream
[19:23] <santa_> specifically those which I added for 19.04.3 to fix build failures
[19:23] <santa_> and I think I also had a couple of extra failures or so
[19:24] <santa_> I will give you an updated list once I get my git clones ready again
[19:24] <santa_> (I'm cloning everything in the other server)
[19:26] <RikMills> ok, going through and doing a fresh ppa rebuild is probably in order. as well as that
[22:06] <santa_> The command failed to execute in the following directories:
[22:06] <santa_> akonadi-import-wizard/ (exit status = 1)
[22:06] <santa_> cantor/ (exit status = 1)
[22:06] <santa_> kate/ (exit status = 1)
[22:06] <santa_> kmail/ (exit status = 1)
[22:06] <santa_> kpat/ (exit status = 1)
[22:07] <santa_> minuet/ (exit status = 1)
[22:07] <santa_> palapeli/ (exit status = 1)
[22:07] <santa_> s
[22:07] <santa_> RikMills: ↑ I think all of them are the missing headers patches we had to add for 19.04, are you sure you pushed all you changes to git?
[22:07] <santa_> s/you/your/