[07:35] <vip> hmm, I cannot run mysql server after upgade
[07:37] <vip> oh, mysqld had been removed
[07:42] <soee> :]
[07:45] <vip> the error was, that mysql is masked.. the first results on google, was to delete all databases ;-)
[07:46] <vip> I'm guessing who would try to run mysqld_safe first to see errors
[07:52] <valorie> vip: have you filed a bug?
[07:52] <valorie> `ubuntu-bug mysqld`
[07:55] <vip> I don't have such command, with premeditation ;-)
[07:55] <valorie> in the commandline, vip
[07:55] <vip> I don't belive in reporting bugs since my kmail stoped searching for mail
[07:55] <valorie> !
[07:55] <vip> oh rly
[07:55] <valorie> this is a packaging bug
[07:56] <valorie> if you don't report it, how can we fix it?
[07:59] <valorie> I don't see the logical connection between an unfixed bug, and not reporting others
[08:00] <vip> it was with a pinch of salt
[08:03] <vip> but, what ubuntu-bug is a tool revealing too much confidental data
[08:03] <vip> moreover, there's no info about uninstalling when upgrade
[08:04] <vip> valorie: is there another way to report it? launchpad url?
[08:09] <valorie> ubuntu-bug does *not* give confidential info -- it is designed not to
[08:10] <vip> valorie: really? I see database names, e.g.
[08:10] <valorie> otherwise, you can search for bugs on launchpad and just comment on them
[08:10] <valorie> and perhaps it has already been reported
[08:11] <valorie> actually, I just began an upgrade on my travel laptop to test what you said
[08:12] <valorie> and I saw that apt full-upgrade said that mysqld18 or so was going to be removed
[08:12] <valorie> !info mysqld
[08:13] <valorie> $ apt-cache search mysqld
[08:13] <valorie> libmysqld-dev - MySQL embedded database development files
[08:13] <valorie> python-mysqldb - Python interface to MySQL
[08:13] <valorie> python-mysqldb-dbg - Python interface to MySQL (debug extension)
[08:13] <valorie> python-pymysql - Pure-Python MySQL driver - Python 2.x
[08:13] <valorie> python3-mysqldb - Python interface to MySQL
[08:13] <valorie> python3-mysqldb-dbg - Python interface to MySQL (debug extension)
[08:13] <valorie> bibus - bibliographic database
[08:13] <valorie> libmysqld-pic - PIC version of MySQL embedded server development files
[08:13] <valorie> mydumper - High-performance MySQL backup tool
[08:14] <valorie> mysql-utilities - collection of scripts for managing MySQL servers
[08:14] <valorie> python3-pymysql - Pure-Python MySQL Driver - Python 3.x
[08:14] <valorie> ruby-yaml-db - library to export/import of database into/from yaml files
[08:14] <valorie> I wonder if it has somehow escaped being added to the archive
[08:14] <vip> mysql-server
[08:15] <soee> so you dont have this package ?
[08:16] <valorie> not on this computer, according to apt-cache policy
[08:16] <valorie> !info mysql-server
[08:17] <valorie> but server and mysqld are not the same
[08:19] <vip> https://gist.github.com/vip9/fe98acacf7a9bafa1358a263c4e2fddd
[08:20] <vip> there were no mysqld package, afair
[08:20] <valorie> looks like mysql is being upgraded from 5.6 to 5.7
[08:21] <vip> looks like, but it did not
[08:23] <valorie> since the upgrade,  what does apt-cache policy show you?
[08:24] <vip> valorie: https://gist.github.com/vip9/767b40c8c3755d9de3bd2bdba7c3d1f3
[08:26] <valorie> sorry, there is a lot of characters there, but very little information!
[08:26] <vip> that's the optput of that command
[08:26] <valorie> apt-cache policy mysql-server would be more useful
[08:26] <soee> for me his package was kept back i think
[08:26] <vip> https://gist.github.com/cb7fe50426a4255d95bfef68a3973700
[08:27] <soee> i run apt-get install --reinstall mysql-server
[08:27] <soee> and the installed version is 5.7.11-0ubuntu5
[08:28] <valorie> and that won't run?
[08:34] <mikkle> Which version of Plasma and Applications will ship in 16.04?
[08:39] <valorie> oh good lord
[08:39] <valorie> I'll be charitable and figure that mikkle read the topic
[10:51] <BluesKaj> Heyas all
[11:05] <yofel> clivejo: FYI: from #kde-neon: any objections to that version number change?   4:5.6.2+git20160413.0151+15.10-0 -> 4:5.6.2+p16.04+git20160413.0151-0
[11:05] <yofel> sgclark: ^
[11:05]  * yofel replied no
[12:10] <BluesKaj> sddm still not loading the login page in xenial and journalctl -ex doesn't show any errors
[13:15] <soee_> wee http://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-PRIME-Sync-V5
[14:11] <sgclark> yofel: I have no context to that question. But I trust your judgement.
[14:12] <yofel> reordering release version and git date to allow reliable release upgrades without a date ordering mess
[14:13] <sgclark> ah ok, sure seems like a good move to me
[14:38] <mamarley> yofel: Why are they asking you guys about it?  I thought it was a separate project.
[14:39] <yofel> mamarley: same CI code
[14:40] <mamarley> yofel: So https://launchpad.net/~kubuntu-ci/+archive/ubuntu/stable is sort of like Neon's Stable repository?
[14:41] <yofel> probably, it's building from the upstream bugfix branch
[14:42] <mamarley> Ah, OK.  Thanks!
[15:21] <pursuivant> muon (master) v5.4.3-181-g4cdb139 * Carlo Vanini: src/muonapt/QAptActions.cpp
[15:21] <pursuivant> Can undo/redo "Unmark all".
[15:21] <pursuivant> Testing Done:
[15:21] <pursuivant> 1. mark packages
[15:21] <pursuivant> 2. mark other packages
[15:21] <pursuivant> http://commits.kde.org/muon/4cdb1397d3d19e901add3f0701a0bc9ad1223973
[16:13] <mhall119> ahoneybun: clivejo: see Laney's comment on https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1562406
[17:43] <mhall119> are there any core-devs working on Kubuntu who would be interested in joining the release team?
[17:46] <sgclark> yeah, myself and probably yofel?
[17:48] <sgclark> oh wait. core-dev haha. mhall119 we have no core0devs sorry I misread
[18:21] <mhall119> sgclark: any devs interested in becoming core-devs? :)
[18:22] <clivejo> interest yes
[18:23] <clivejo> but the time and commitment that could be a problem
[18:24] <clivejo> mhall119: are there any mentors?
[18:24] <mhall119> clivejo: I'm not sure, we can probably find some 
[18:25] <clivejo> Id certainly like to learn, but I have a long way to go
[18:25] <mhall119> ok
[18:26] <mhall119> clivejo: in the mean time, is anyone in contact with Riddell or ScottK to see if they can upload it?
[18:27] <clivejo> sorry, upload what?
[18:27] <mhall119> the muon packages from that FFE bug
[18:27] <mhall119> https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1562406
[18:27] <sick_rimmit> Yep I am interested too
[18:27] <clivejo> ah, emmm last I heard KDE are to bump the release number
[18:28] <sick_rimmit> Yes Carlo is working on Bumping a release tag for Muon
[18:28] <clivejo> so we are waiting for that to happen and for Rick and Co to be added as maintainers
[18:28] <clivejo> we thought that getting a proper release would help the FFE request
[18:28] <clivejo> rather than a git snapshot
[18:28] <mhall119> clivejo: ok, Laney gave a +1 to uploading it into xenial if you can get that done soon
[18:29] <clivejo> was Laney on holiday?
[18:29] <sgclark> mhall119: yeah I definately want to be a core dev but I honestly don't even know where to start.
[18:29] <sick_rimmit> We're having our packaging party tomorrow night, so with a good wind and a bit of help we could get that ready
[18:29] <sgclark> and also affected by the time issue
[18:29] <sick_rimmit> I will checkin with Carlo and see how that tag is looking
[18:30] <clivejo> sick_rimmit: would Carlo come here?
[18:31] <sick_rimmit> Dunno, let me invite him here, and to Party - Will email him
[18:31] <mhall119> clivejo: no, he's 200% on snappy work for 16.04 though
[18:32] <clivejo> He helped me the last time with kde-connect and was very halpful, but I couldnt contact him this time :(
[18:32] <mhall119> yeah, he's been under very tight deadlines with a lot of work, I wasn't expecting to hear from him at all on that FFE
[18:33] <clivejo> nice guy :)
[18:34] <sgclark> LOL someone created an FFe without packaging, and now expect us to package it? I refuse on principal. https://bugs.launchpad.net/ubuntu/+source/taglib/+bug/1546373
[18:34] <sgclark> but someone else bored? feel free.
[18:38]  * sgclark returns to her KDE hat.
[18:38] <clivejo> looks like that lib might cause problems in amarok?
[18:42] <sgclark> no clue what it is for, also they want to package a beta version... seems like it will be trouble, I don't have time for it. I also do not understand why we are responsible? 
[18:44] <clivejo> I think he just used that as a example of the lastest upstream activity
[18:44] <sick_rimmit> Email Carlo, and invited him to party
[18:44] <clivejo> to make a point that its still being worked on upstream
[18:45] <clivejo> the original FFE is for TagLib 1.10 Release - November 11, 2015
[18:46] <sick_rimmit> OK be back later, go to go
[18:46] <sgclark> the point is... it has not even been packaged, why did they make it a FFe
[18:48] <clivejo> eakk, no activity on the packaging in 2 years - http://anonscm.debian.org/cgit/users/modax/taglib.git
[18:49] <sgclark> right, so it will not likely be easy. And they pull this how long beforee release? and assign us? wtf?
[18:49] <sgclark> oh well I have to go. bbl
[19:26] <snele> when plasma 5.5.5 and other updates from staging ppas will be available in repo?
[19:26] <snele> release is very close...
[19:28] <soee> i think even old wizards have no idea :)
[19:29] <snele> yofel: sgclark: clivejo: are you these wizards? :)
[19:33] <clivejo> not me!
[19:33] <clivejo> Im no wizard
[19:42] <mhall119> sgclark: do you know who subscribed the kubuntu packagers to that?
[19:46] <mhall119> it looks like Debian is still on 1.9.x too
[19:57] <clivejo> hummm 1.10 wont build
[20:00] <sgclark> mhall119: no idea
[20:01] <sgclark> yofel: what if anything is blocking us from uploading these point releases? would make a big difference
[20:01]  * sgclark is also not a wizard
[20:02] <yofel> taglib is used by amarok, so that's how that happened probably
[20:03] <yofel> not sure, packageset issues possibly, but that might only be one or two packages and can be fixed later on. Do talk to the release folks when's a good time for the upload though
[20:03] <yofel> but I don't think anything is blocking it, aside from nobody doing it yet
[20:04] <sgclark> hmm. not sure even how to accomplish it
[20:04] <sgclark> or when I myself will have time haha
[20:05]  * sgclark envisions this nightmare of having to tag and upload each package
[20:05] <yofel> ubuntu-archive-upload does that
[20:05] <sgclark> oh excellent
[20:05] <sgclark> who exacty am I suppose to ask?
[20:07] <yofel> in -release? infinity maybe, but just pop in saying whether anyone would feel offended by you uploading plasma and apps before pinging anyone
[20:07] <sgclark> ok
[20:07] <sgclark> I will work on this tonight
[20:07] <yofel> thanks
[20:08] <clivejo> sgclark: when is your tonight?
[20:09] <sgclark> Not for 5ish hours
[20:09] <clivejo> ah Ill be in bed, any chance of pasting the comands you used to a shared pad or something?
[20:11] <sgclark> err ok I guess I need to figure how to do this within the hour.
[20:12]  * sgclark looks for a README
[20:32] <sgclark> getting errors on signing the tag, hopefully that is not bad...
[20:34] <soee> :)
[20:38] <yofel> sgclark: AFAIK, that means it's not tagging anything, as it tries to make signed tags
[20:38] <yofel> (can't try it right now)
[20:38] <sgclark> well that is not good, how do I fix this?
[20:38] <yofel> you gpg-agent should take care of that... not set up?
[20:38] <yofel> *your
[20:38] <sgclark> it is set up ...
[20:39] <yofel> maybe it's trying to use the wrong key
[20:39] <clivejo> my gpg-agent has suddenly stopped working :(
[20:39] <sgclark> mmm yes it is trying to use an old... email
[20:40] <yofel> I think it tries whatever email is set in ~/.gitconfig
[20:40] <sgclark> ok
[20:41] <sgclark> blah that is it
[20:41] <sgclark> so now what? I can't re run the script can I?
[20:42] <sgclark> hmm new email failed too
[20:42] <yofel> yes you can, it doesn't push
[20:43] <sgclark> ksysguard is broken  clivejo
[20:44] <clivejo> sgclark: it is?
[20:44] <clivejo> Ive 5.5.5 on my install, works for me?
[20:44] <sgclark> trying to parse <<<<
[20:45] <sgclark> oh in copyright file, merge marker
[20:45] <sgclark> wouldnt break the whole thing, but stilll needs to be fixed
[20:45] <sgclark> no clue how to fix this key igning thing
[20:46] <clivejo> ah yes, line 165 - http://anonscm.debian.org/cgit/pkg-kde/plasma/ksysguard.git/tree/debian/copyright?h=kubuntu_xenial_archive
[20:46] <clivejo> also line 312
[20:46] <clivejo> was that me?
[20:47] <clivejo> looks like it was introduced in this commit - http://anonscm.debian.org/cgit/pkg-kde/plasma/ksysguard.git/commit/?h=kubuntu_xenial_archive&id=6d28b20cf16298cc0e714c98ae41f933f90cfb57
[20:51] <sgclark> plasma-discover differs
 mm anyone get "POWER CALIBRATION AREA ERROR" when burning DVD's?
[21:02] <sgclark> have not burned one in awhile, but no. 
[21:14] <clivejo> aaron what are you using to burn?
[21:15] <clivejo> anyone having trouble with Kontact/Akonadi?
[21:15] <clivejo> Im getting what look to be MySQL errors
[21:21] <yofel> someone did send something to the ML about an invalid config key
[21:28] <clivejo> :(
[21:28] <clivejo> Im getting lots of errors
[21:28] <clivejo> The amarok database reported the following errors:
[21:28] <clivejo> GREPME MySQLe query failed! (2000) mysql_embedded: Shutdown complete
[21:28] <clivejo>  on init
[21:28] <clivejo> akonadi is going crazy too about MySQL
[21:30] <clivejo> is this MySQL7 related?
[21:35] <valorie> update last night removed one version of mysql and installed another
[21:35] <valorie> read up to see my conversation with someone last night with problems
[21:36] <valorie> 'vip' was his name
[21:36] <sgclark> well plasma is uploaded, I can't seem to sort out my git key tagging issue to push to git..
[21:37]  * sgclark starts applications
[21:41] <soee> :)
[21:46] <valorie> someone reported mysql errors upon upgrade in #amarok, too
[21:47] <valorie> I'm going to ask in #amarok-devel about the updated taglib
[21:47]  * sgclark is still not packaging it
[21:53] <genii> mamarley: Do the drivers at https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa have Vulcan ?
[21:58] <mamarley> genii: I believe so.  Or, you can try the Vulkan PPA which has 364.16.
[21:58] <genii> mamarley: Cool, thanks
[22:34] <valorie> sgclark: I think we are all agreed that a new taglib will not be on 16.04 -- but if we can find a packager, and IF kde multimedia wants the new taglib, we could backport it after release
[22:35] <valorie> i'll write to the lists to ask. If they don't want it, there is no push to do more work
[22:36] <ahoneybun> I think the point was why did they file a FFE at this point for a simple lib
[22:44] <sgclark> I don't care how simple or complicated. Why did they file a Ffe for something that was unpackaged, and then assign it to us... and this close to release is even more unforgivable.
[22:45] <sgclark> I get that they want someone to package it, this was NOT how to get that.
[22:49] <valorie> ahoneybun: unsure if the taglib devels are in the loop at all
[22:50] <valorie> from what I recall from my time working in Amarok; not so much
[22:51] <valorie> they probably noticed that Ubuntu wasn't shipping their latest and were just "fixitfixitfixit"
[22:51] <sgclark> FTBFS libksysguard...
[22:55]  * sgclark wishes she kept her KDE hat on
[22:59] <sgclark> oh well hopefully rebuilds will sort it out.
[23:49] <sgclark> not good: https://lists.debian.org/debian-qt-kde/2016/03/msg00193.html libksysguard...
[23:50] <sgclark> marble might fail too
[23:57] <doko> who is responsible for this kubuntu upload mess?
[23:59] <sgclark> what mess?