[00:52] <doko> slangasek, pitti: eperl wants to demote.  which package should have a Built-Using: eperl? or should it be just seeded?
[00:54] <ianorlin> flocculant, infinity I had something similar in booting a kvm virtual machine multiple times as well
[00:54] <ianorlin> with lubuntu
[03:28] <slangasek> doko: I'm not sure that we want either for eperl, it seems to me it should just be demoted.  I'm not sure why pitti thought that one should come back into main
[05:26] <zequence>  Any kind soul who could squeeze these in for us, at this late hour?
[05:26] <zequence> Bug 1568981
[05:26] <ubot5`> bug 1568981 in ubiquity (Ubuntu) "new Ubuntu Studio wallpaper for ubiquity installer [UI FREEZE EXCEPTION]" [Undecided,New] https://launchpad.net/bugs/1568981
[05:26] <zequence> Bug 1569005
[05:26] <ubot5`> bug 1569005 in ubiquity-slideshow-ubuntu (Ubuntu) "New ubiquity slideshow for Ubuntu Studio [UI Freeze Exception]" [Undecided,New] https://launchpad.net/bugs/1569005
[07:44] <slangasek> ^^ this pulls a fix from Debian that was uploaded shortly after 2.02.133-1 was merged (I maybe should've called this 2.02.133-2ubuntu1) that resolves a problem with lvm snapshotting being slow and dmeventd failing to monitor
[07:45] <slangasek> (so if you use schroot with lvm snapshots, this is why they're slow to setup/teardown, and why you get noise on stderr... which also breaks adt-virt-schroot)
[09:44] <Laney> infinity: It's regenerated at build time anyway - it's an AC_CONFIG_FILE
[09:44] <Laney> Just shouldn't be put into the release tarballs
[09:51] <infinity> Laney: Do the paths actually come out sane at build time? :P
[09:55] <Laney> Yeah
[09:55] <Laney> check the file on your system
[09:57] <Laney> https://git.gnome.org/browse/gnome-software/commit/?h=wip/iainl/ubuntu-xenial&id=1f5bc7571c4647ce3d47640f49f428ef0a89b66f anyways
[10:45] <bzoltan> folks, is here anybody who could pubish a landing silo what stuck after a late QA approval? I could use the time to integrate this release to the IDE.
[10:45] <bzoltan> https://requests.ci-train.ubuntu.com/#/ticket/1266
[11:07] <clivejo> does anyone here understand whats changed with mysql?
[11:08] <clivejo> I have a Kubuntu system with apps that require MySQL to work.  Ever since the update to MySQL a few days ago they have all stopped working
[13:11] <doko> https://bugs.launchpad.net/ubuntu/+source/gccgo-6/+bug/1571182 ^^^
[13:11] <ubot5`> Launchpad bug 1571182 in gccgo-6 (Ubuntu) "FFe: update gccgo-6 to the GCC 6.1 release candidate 1" [Undecided,New]
[13:13] <apw> clivejo, i would recommend asking on #ubuntu-server based on the previous uploaders for that ...
[13:14] <clivejo> apw: hi, do you know was there a FFE for MySQL?
[13:16] <apw> clivejo, what version worked, and which not?
[13:16] <clivejo> the one previous to the version releases in the last week or so worked fine
[13:17] <apw> (there are more than one base release in xenial)
[13:17] <clivejo> its only since an update a few days ago
[13:18] <clivejo> on the 14th my system upgraded to mysql 5.7 libmysqlclient20
[13:19] <clivejo> but the problem upgrade was on the 7th I believe when I went from 5.6 to 5.7
[13:20] <apw> clivejo, so it depends what version you had before, but that might well have been ubuntu3 which had an FFE LP: #1528583
[13:20] <ubot5`> Launchpad bug 1528583 in mysql-5.7 (Ubuntu) "[FFe] Please update to MySQL 5.7 series" [Wishlist,In progress] https://launchpad.net/bugs/1528583
[13:21] <clivejo> ubuntu3 was when I started seeing problems
[13:21] <clivejo> that was installed on the 7th
[13:22] <clivejo> which was then upgraded to ubuntu6 on the 14th
[13:22] <clivejo> but from the 14th my problems have got worse
[13:25] <apw> that all was uploaded by rbasak so i'd ask on #ubuntu-server ...
[13:39] <Skuggen> clivejo: What's the issue?
[13:41] <clivejo> I dont actually know!
[13:41] <Skuggen> What happens, then? :)
[13:42] <clivejo> apps that use it wont work
[13:42] <Skuggen> Which apps, specifically?
[13:43] <clivejo> GREPME MySQLe query failed! (2000) mysql_embedded: Shutdown complete
[13:43] <clivejo> amarok and kontact that I know of
[13:45] <Skuggen> amarok was very recently fixed to build with MySQL 5.7, at least
[13:46] <Skuggen> Which MySQL 5.7 package version are you using now?
[13:46] <clivejo> ubuntu6 I believe
[13:46] <Skuggen> And amarok?
[13:48] <clivejo> 2:2.8.0-0ubuntu8
[13:49] <clivejo> rebuilt - -- Robie Basak <robie.basak@ubuntu.com>  Wed, 13 Apr 2016 11:32:21 +0000
[13:50] <Skuggen> Both newest, then. I'd have to look closer at amarok and see how it uses MySQL
[13:51] <clivejo> the component that uses mysql in kontact is called akonadi
[13:51] <clivejo> http://packages.ubuntu.com/xenial/akonadi-backend-mysql
[13:51] <clivejo> again rebuilt -- Robie Basak <robie.basak@ubuntu.com>  Tue, 12 Apr 2016 14:33:29 +0000
[13:52] <Skuggen> Akonadi was updated for 5.7 in 4:15.12.1-0ubuntu4, yes
[13:52] <clivejo> akonadi is a complicated beast
[13:52] <clivejo> but its the heart of the Kubuntu PIM
[13:52] <clivejo> my whole groupware is dead in the water
[13:53] <Skuggen> The main differences from the 5.6 packages to 5.7 is that 5.7 is more strict by default and that it's stricter on letting you have a root account without a password
[13:53] <Skuggen> Is there anything in /var/log/mysql/error.log?
[13:55] <Skuggen> Would probably need to look closer at how akonadi is using MySQL
[13:55] <clivejo> nothing I think is relevant
[13:55] <clivejo> I think these apps startup their own instances
[13:57] <Skuggen> Ah, I saw a similar bug report for amarok that was because of config problems
[13:57] <Skuggen> Can you run mysqld --verbose --help 2>&1 > /dev/null  and see if it says anything?
[13:58] <clivejo> few warnings, few notes and an error - [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
[13:58] <clivejo> and mysqld: Can't change dir to '/var/lib/mysql/' (Errcode: 13 - Permission denied)
[13:59] <Skuggen> Ah, the permission denied is just because you didn't sudo, but that's fine.
[13:59] <Skuggen> mysql_upgrade should have been run when 5.7 was installed/upgraded, though.
[13:59] <Skuggen> But if it hasn't then the server won't work properly, so try running sudo mysql_upgrade -uroot -p
[14:00] <clivejo> Error: Failed while fetching Server version! Could be due to unauthorized access.
[14:00] <clivejo> FATAL ERROR: Upgrade failed
[14:02] <Skuggen> What does mysql_upgrade --version say?
[14:03] <clivejo> same message
[14:05] <Skuggen> Not really sure what would cause that error. my_print_defaults mysqld | grep port?
[14:05] <Skuggen> And mysql --version and mysqld --version
[14:11] <clivejo> sorry, I been purging mysql packages
[14:12] <clivejo> when I install mysql-server Im getting errors
[14:12] <clivejo> mysql_upgrade: [ERROR] 1146: Table 'mysql.innodb_table_stats' doesn't exist
[14:12] <clivejo> Setting up mysql-server-5.7 (5.7.11-0ubuntu6) ...
[14:15] <clivejo> http://paste.ubuntu.com/15873389/
[14:17] <Skuggen> I think I've seen that before in a bug report. Hang on
[14:18]  * clivejo hangs
[14:22] <Skuggen> There was a bug in mysql_upgrade if the server was started without innodb, but it was fixed before the 5.7 GA
[14:23] <Skuggen> https://bugs.mysql.com/bug.php?id=70152
[14:24] <clivejo> so its my data dir?
[14:26] <Skuggen> Yeah. You can test if everything works as it should by backing it up to somewhere else and trying to reinstall
[14:26] <clivejo> nothing in the main dir
[14:26] <clivejo> Ill just rm it
[14:27] <Skuggen> There's nothing, or just nothing you need to keep? Maybe akonadi stores it somewhere else
[14:27] <clivejo> so basically the 5.7 failed?
[14:27] <clivejo> akonadi starts an instance and stores it in my home directory
[14:28] <clivejo> ok installed that time :)
[14:28] <clivejo> I need to reboot
[14:30] <Skuggen> Ah, of course. The mysql installation probably doesn't handle data in non-standard locations too well
[14:30] <Skuggen> So if /var/lib/mysql was there, but empty, it would assume the database exists and not create it, then run mysql_upgrade.
[14:30] <Skuggen> That at least is a bug we can probably fix
[14:32] <clivejo> nope, apps still not working
[14:32] <Skuggen> Does mysql_upgrade still give the same error as before?
[14:33] <clivejo> no, mysql-server installed without error
[14:33] <Skuggen> If you run it manually as well?
[14:33] <Skuggen> When it's run as part of the 5.7 install it will  upgrade the database in /var/lib/mysql
[14:34] <clivejo> well --version is now giving an output - mysql_upgrade  Ver 2.0 Distrib 5.7.11, for Linux (x86_64)
[14:34] <Skuggen> My guess is the apps aren't working because the database is stored somewhere else, and hasn't been upgraded
[14:34] <Skuggen> Maybe akonadi specifies a config to use instead of changing the normal ones
[14:34] <clivejo> yes, the flat files are stored in my home directory
[14:35] <clivejo> --datadir=~/.local/share/akonadi/db_data/
[14:35] <Skuggen> Can you do mysqld --verbose --help | grep datadir?
[14:36] <clivejo> /var/lib/mysql/
[14:36] <Skuggen> Check your process list for mysqld and see if it specifies anything in particular on the command line?
[14:37] <clivejo> akonadi starts its own instance though
[14:37] <clivejo> in my home directory
[14:37] <clivejo> there is an error log here
[14:37] <clivejo> stderr: "mysqld: [ERROR] Could not open required defaults file: /home/~/.local/share/akonadi/mysql.conf\nmysqld: [ERROR] Fatal error in defaults handling. Program aborted!\n"
[14:38] <Skuggen> Is that file there?
[14:39] <clivejo> mysql.conf is
[14:39] <clivejo> what does \nmysqld mean?
[14:40] <Skuggen> Looking for a mysqld section in the file, I guess
[14:41] <clivejo> \n means newline?
[14:41] <Skuggen> What's in the mysql.conf file?
[14:41] <clivejo> LOL settings
[14:43] <clivejo> http://paste.ubuntu.com/15873829/
[14:43] <Skuggen> Looks like it's actually looking for the full string including \nmysqld, though
[14:44] <Skuggen> Oh wait, maybe not. Hang on, let me try just using that
[14:48] <flexiondotorg> infinity, slangasek cyphermox Ubiquity is not behaving as it should in the April 16th daily image.
[14:48] <flexiondotorg> It is boot directly to desktop.
[14:49] <Skuggen> clivejo: Config file seems to work ok to me. So does indeed look like it's trying to use the full string, for some reason
[14:51] <Skuggen> clivejo: See if you can find out where the path to that config file is set in akonadi?
[14:54] <clivejo> from what I understand it starts up agents when I log in
[14:55] <clivejo> these agents connect to my mail resources and grab my new email which are cached in akonadi
[14:55] <clivejo> its basically black magic to me
[14:56] <clivejo> I just dont understand how an upgrade of this kind can be made so close to release date
[14:56] <clivejo> it worked fine in 5.6
[14:57] <clivejo> The only thing I have done is to upgrade my system
[15:04] <apw> clivejo, rememeber whatever is in the release has to be supported for 5 years, so the latest upstream version is desirable
[15:04] <Skuggen> clivejo: So it works if you remove 5.7 and install 5.6?
[15:07] <flexiondotorg> infinity, slangasek cyphermox This is still an issue too - https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1552539
[15:07] <ubot5`> Launchpad bug 1552539 in ubiquity (Ubuntu) "Ubiquity Erase Disk and Install Fails to create Swap Space" [Critical,Triaged]
[15:08] <clivejo> Skuggen: I dont know, Robie changed the dependancies in the latest package - Depend on mysql-{server,client}-core-5.7, not 5.6, for the switch to
[15:08] <clivejo>     MySQL 5.7.
[15:09] <rbasak> o/
[15:09] <clivejo> I guess I could force install 5.6 and see if it works :/
[15:09] <rbasak> Skuggen: I wonder if it's because of the binaries missing from -core?
[15:09] <rbasak> clivejo: do you have the mysql-server-5.7 package installed also? Or just mysql-server-core-5.7?
[15:10] <Skuggen> rbasak: But the error message he's getting seems to just be about not finding the config file. Unless that's a distraction
[15:10] <Skuggen> If so, then it might just be that you need to upgrade the database to 5.7
[15:11] <rbasak> Skuggen: ah, then that sounds more likely. I was just thinking of reasons akonadi might have problems with no regard to the specific symptoms.
[15:12] <ogra_> note that akonadi got a new upstream version this morning ...
[15:12] <ogra_> (EU morning :) )
[15:12] <Skuggen> 5.6 core package didn't have those plugin binaries either
[15:12] <clivejo> ogra_: it did and it didnt
[15:12] <ogra_> ?
[15:12] <ogra_> https://launchpad.net/ubuntu/+source/akonadi/4:15.12.3-0ubuntu1
[15:13] <ogra_> regard the diff
[15:13] <rbasak> Does akonadi need to be running mysql_upgrade in its postinst?
[15:13] <ogra_> -         mysql-client-core-5.7 | virtual-mysql-client-core,
[15:13] <ogra_> -         mysql-server-core-5.7 | virtual-mysql-server-core,
[15:13] <ogra_> +         mysql-client-core-5.6 | virtual-mysql-client-core,
[15:13] <ogra_> +         mysql-server-core-5.6 | virtual-mysql-server-core,
[15:13] <clivejo> its a package thats been ready to go for a long time but we (Kubuntu) are bit short staffed at the moment
[15:13] <ogra_> (not sure that was desired)
[15:14] <ogra_> there is aalso a patch to the mysql-global.conf defaults
[15:14] <clivejo> its been working all along on 5.6
[15:15] <clivejo> its only since this forced upgrade to 5.7 that its fallen on its face
[15:15] <rbasak> There isn't that much different in 5.7 AIUI. I'm sure we can figure this out.
[15:16] <ogra_> the mysql-global.conf change looks like it is needed for 5.7
[15:16] <clivejo> rbasak: are you robie in the changelog?
[15:16] <rbasak> clivejo: yes.
[15:16] <clivejo> ah o/
[15:16] <ogra_> http://launchpadlibrarian.net/253864624/akonadi_4%3A15.12.1-0ubuntu4_4%3A15.12.3-0ubuntu1.diff.gz looks very much like rbasak and sgclark clashed there
[15:17] <ogra_> (see the top most changelog entry)
[15:17] <Skuggen> mysql_upgrade --socket=/tmp/akonadi_usersomething I think
[15:17] <ogra_> which might explain the breakage
[15:17] <Skuggen> ogra_: I don't actually think that will break, since virtual-mysql-client/server-core will be there
[15:18] <Skuggen> clivejo: Assuming it isn't actually failing to find the config file (which wouldn't be different between 5.6 and 5.7), then upgrading the database should fix it, but that's a one-way street, so should probably back it up first
[15:18] <ogra_> Skuggen, rbasak added the 5.7 dep ... people that had his package have upgraded to 5.7 ... then sgclark added a fix for the mysql default config but downgraded the dep ... so the fix wont land since 5.6 is gone
[15:19] <Skuggen> Ah
[15:19] <ogra_> at least thats how i read that diff above
[15:19] <rbasak> Both 5.6 and 5.7 provide virtual-mysql-server though
[15:19] <ogra_> sure
[15:19] <ogra_> but there are 5.7 specific config changes in the second upload
[15:19] <clivejo> Skuggen: I dont know what to do, its just strange close to release and at least two apps in Kubuntu are dead :(
[15:20] <clivejo> scary
[15:20] <ogra_> clivejo, it will be fixed one way or the other ... and it is definitely better to have a bug for the first few days around the release than having to maintain an unsupported mysql version for 5 years :)
[15:21] <ogra_> that is what you get for not waiting to the .1 release ;)
[15:21] <ogra_> (the privilege of reporting bugs :) )
[15:21] <clivejo> I dont get why we been bumped though
[15:22] <clivejo> surely the decision to move from 5.6 to 5.7 is with us?
[15:22] <ogra_> again, because 5.6 wont be supported for 5 years by upstream
[15:22] <clivejo> ie Debian/Kubuntu KDE teams
[15:22] <Skuggen> clivejo: Can you first take a backup of the .local/share/akonadi/db_data directory?
[15:22] <rbasak> We share the archive.
[15:22] <rbasak> MySQL isn't exclusive to KDE.
[15:23] <clivejo> *holds hands up*  Im new to all this, so please go easy on me!
[15:24] <Skuggen> Then run mysql_upgrade -uroot -p --socket=/tmp/akonadi-youruser-something/mysql.socket
[15:24] <rbasak> clivejo: np, just explaining. I appreciate your patience.
[15:24] <clivejo> we sync with Debian - http://anonscm.debian.org/cgit/pkg-kde/applications/akonadi.git/
[15:24] <Skuggen> Not sure about the -uroot -p, since I'm not sure what credentials akonadi sets up :)
[15:24] <Skuggen> And the youruser-something is randomly generated
[15:25] <rbasak> clivejo: if I thought it would be a major deal, I would have checked with your team first. I could yet turn out to be wrong, but I suspect it'll be a one line (or similar) fix.
[15:25] <rbasak> Skuggen: thank you for being on top of this. Shall I leave you to drive? I'm around, let me know if I can help.
[15:26] <Skuggen> Sure
[15:26] <clivejo> I dont really have the time to look into it properly
[15:26] <ogra_> someone really needs to clearify with sgclark if the rollback of the dependency was wanted though .. the new upstream definitely also modifies the SQL tables
[15:26] <rbasak> I'm also preparing the update to 5.7.12 though the release team hasn't acked that yet.
[15:27] <clivejo> I would like to know if this is a problem for new installs, or is it just upgrades
[15:27] <ogra_> (according with claiming a config change for 5.7 while the dep was downgraded to 5.6)
[15:27] <rbasak> ogra_: given that the upload chopped off my changelog message, I think it's safe to assume that the reversion was inadvertent.
[15:27] <ogra_> right
[15:27]  * ogra_ would just re-upload with the dependency fixed again ... 
[15:28] <clivejo> I cant actually see that package of sgclark's yet
[15:29] <ogra_> https://launchpad.net/ubuntu/+source/akonadi ... was released to universe 5h ago
[15:29] <clivejo> I know
[15:29] <rbasak> Oh
[15:30] <clivejo> but it hasnt made it to my system yet
[15:30] <Skuggen> clivejo: The config file you pasted has the change
[15:31] <rbasak> p/sb end
[15:31] <rbasak> clivejo: what version of akonadi do you have installed?
[15:32] <clivejo> nothing at the minute
[15:32] <rbasak> What version did you have installed?
[15:33] <clivejo> I purged mysql and akonadi
[15:33] <rbasak> /var/log/apt/history.log should be able to tell you
[15:33] <clivejo> I had the rbasak modified
[15:34] <Skuggen> But you put the contents of your mysql.conf file at http://paste.ubuntu.com/15873829/
[15:34] <clivejo> previous to that I had the one sgclark uploaded from a staging/testing PPA
[15:34] <Skuggen> Ah
[15:34] <Skuggen> # Deprecated in MySQL >= 5.6.3, removed in 5.7 (works in MariaDB)
[15:34] <rbasak> Yeah
[15:34] <rbasak> That's what I'm thinking
[15:35] <clivejo> ok so now it wants to install 5.6
[15:35] <ogra_> Skuggen, that was what i was referring to 30min ago ;)
[15:35] <rbasak> clivejo: I suggest you force it onto 5.7.
[15:35] <Skuggen> clivejo: If you install 5.7 first, then akonadi
[15:35] <rbasak> clivejo: ask apt-get for mysql-server-core-5.7 specifically, along with akonadi
[15:35] <ogra_> Skuggen, it also has a dbupdate.xml file that it likely processes to convert the tables
[15:35] <clivejo> I want to get to a point where its working
[15:36] <clivejo> and see what breaks it
[15:36] <clivejo> this only started about a wek ago
[15:36] <Skuggen> As it is now I don't think upgrading akonadi from 5.6 to 5.7 will work, because you need to run mysql_upgrade
[15:37] <Skuggen> But would be very nice to test if it works with a fresh install with 5.7
[15:37] <ogra_> doesnt it do that from a postinst ?
[15:37] <Skuggen> ogra_: Akonadi stores the database somewhere else
[15:37] <Skuggen> And uses its own config file
[15:37] <Skuggen> So the mysql-5.7 postinst will upgrade whatever database is in /var/lib/mysql, but that won't help akonadi
[15:38] <ogra_> no, i mean the dbupdate.xml file and the mysql-global.conf change from akinadi itself
[15:38] <clivejo> amarok is having problems too
[15:38] <clivejo> brb
[15:38] <ogra_> i would expect some postinst to process them
[15:38] <PaulW2U> flexiondotorg: I'm also seeing that the install option boots to a desktop. Xubuntu too although a little more graceful than MATE :)
[15:40] <clivejo> ok its working now
[15:41] <Skuggen> clivejo: Can you also try a completely fresh install with 5.7?
[15:41] <clivejo> mysql  Ver 14.14 Distrib 5.6.28, for debian-linux-gnu (x86_64) using  EditLine wrapper
[15:42] <clivejo> so purge all mysql packages?
[15:42] <Skuggen> And akonadi
[15:43] <clivejo> but akonadi will want to use 5.6
[15:43] <Skuggen> Purge mysql and akonadi, then install mysql 5.7, then akonadi
[15:43] <Skuggen> Akonadi wants 5.6 or virtual, and they both provide virtual
[15:44] <clivejo> I have to go soon
[15:44] <clivejo> It'll have to wait until later
[15:45] <Skuggen> amarok uses removed config values
[18:42] <clivejo> ok purged mysql, installed 5.7 and then installed akonadi
[18:43] <clivejo> it seems to be working
[18:44] <clivejo> Skuggen: ping if you are still here
[18:47] <Skuggen> clivejo: I'm actually surprised, because looking at the source it seems akonadi uses outdated mysql_install_db options :D
[18:48] <clivejo> it seems to have picked up my old database
[18:48] <Skuggen> Also, amarok has an option in the config file it generates that just needs renaming, and it seemed to work
[18:48] <clivejo> everything is there
[18:48] <Skuggen> Ah, right. Yeah, this would only affect new databases.
[18:48] <clivejo> Skuggen: are you on the release team?
[18:48] <Skuggen> I work for MySQL :)
[18:48] <clivejo> ah
[18:48] <clivejo> an expert :)
[18:49] <Skuggen> Only worked here for about a year, but I'm working with rbasak on the Ubuntu packaging
[18:49] <clivejo> is rbasakabout?
[18:50] <clivejo> rbasak: ping
[18:51] <Skuggen> clivejo: For amarok, I think there's a .local/share/amarok/my.cnf or something like that, with a myisam-recover=FORCE, that should be myisam-recover-options=FORCE
[18:52] <clivejo> Skuggen: would you might coming to #kubuntu-devel?
[18:53] <Skuggen> On freenode?
[18:54] <clivejo> yes
[20:07] <infinity> sgclark: Your changelog format is broken (missing a newline between entries)
[20:08] <infinity> sgclark: Also, the "debsign broken" thing can be solved by asking specifically for the right key.  "debsign -k 'Lappy2.0'" or specify the key like so:
[20:08] <infinity> (base)adconrad@nosferatu:~$ cat .devscripts
[20:08] <infinity> DEBSIGN_KEYID=B1CDE58F
[20:09] <clivejo> infinity: are you on the release team?
[20:09] <infinity> clivejo: Last I checked.
[20:09] <clivejo> :)
[20:10] <clivejo> we have a Package Manager in Kubuntu called Muon which is currently broken to install
[20:11] <infinity> sgclark: You also got Robie's entries in the wrong spot (which might account for the newline issue)
[20:11] <clivejo> kinda need some help with it
[20:11] <infinity> clivejo: Gimme a sec.  One thing at a time.
[20:12] <sgclark> infinity: ok thanks, will fix, sorry.
[20:12] <infinity> sgclark: If I fix it up, can you just commit the diff to pkg-kde (I don't think I have access).
[20:13] <sgclark> infinity: suree I can do that. We are moving back to launchpad next release.
[20:18] <infinity> sgclark: wget http://lucifer.0c3.net/~adconrad/akonadi.patch && patch -p1 < akonadi.patch && rm akonadi.patch && git commit -a -m 'Fix changelog' && git tag ubuntu/4%15.12.3-0ubuntu4 && git push -a
[20:18] <infinity> sgclark: Uploading that now.
[20:19] <infinity> sgclark: (And yes, the diff looks awful, but it looks sane against -0ubuntu1 :P)
[20:19] <sgclark> infinity: you are awesome, thank you so much.
[20:20] <infinity> sgclark: This is how it comes out as a diff against -0ubuntu1, much prettier: http://launchpadlibrarian.net/254141356/akonadi_4%3A15.12.3-0ubuntu1_4%3A15.12.3-0ubuntu4.diff.gz
[20:22] <sgclark> infinity: :)
[20:23] <clivejo> how did it get from ubuntu1 to ubuntu4 ?
[20:23] <infinity> clivejo: Magic.
[20:23] <clivejo> fairies then
[20:23] <infinity> clivejo: (I would have called it ubuntu2, but sgclark had already tagged 2 and 3 in git, and deleting tags is generally bad)
[20:24] <clivejo> ah, not I see
[20:24] <clivejo> now
[20:37] <infinity> sgclark: You didn't apply my patch. :P
[20:37] <infinity> sgclark: The changelog in git is still broken, just with an extra entry now.
[20:37] <infinity> Well, three extra entries.
[20:41] <infinity> Aww, dang, I don't have write access.  Didn't think I would.
[20:44] <sgclark> hmm but I did. let me look, I am in too many places.
[20:44] <infinity> Not the patch I linked from lucifer.
[21:09] <infinity> clivejo: Okay.  muon.  You have half an hour before I run off to an airport.  What's up.
[21:10] <infinity> clivejo: Laney ACKed your FFe two days ago.
[22:51] <doko> slangasek, pitti: eperl demoted
[23:05] <cyphermox> flexiondotorg: both known issues I want to fix on Monday
[23:05] <cyphermox> btw, I found this very funny bug: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1571262
[23:05] <ubot5`> Launchpad bug 1571262 in gnome-bluetooth (Ubuntu) "my computer's name is not "Bastien's computer"" [Undecided,New]
[23:06] <flexiondotorg> cyphermox, Yeah. I was sent the bugs by Xubuntu. I've +1 them.
[23:06] <cyphermox> cool
[23:06] <flexiondotorg> cyphermox, Hah!
[23:06] <cyphermox> I'm not sticking around to hack at the bugs tonight though, I have a school project to work on
[23:07] <flexiondotorg> Sure.
[23:07] <flexiondotorg> Time for sleeping here.
[23:07] <flexiondotorg> Night.
[23:07] <cyphermox> nght
[23:29] <infinity> doko: Ahh, I was testing a numpy merge in my PPA, you beat me to the archive upload. :)
[23:34] <infinity> clivejo: This muon upload is a bit concerning to me.
[23:34] <clivejo> infinity: how so?
[23:34] <infinity> clivejo: You drop a bunch of packages (I'm guessing everything is in muon now?), but I see no Breaks/Replaces/Conflicts/etc.
[23:34] <infinity> clivejo: How is this meant to upgrade for people who have muon-notifier, muon-common, etc installed?
[23:35] <clivejo> they have moved to a brand new package plasma-discover
[23:36] <infinity> clivejo: And libmuon?  And muon-common?
[23:37] <infinity> That's all in plasma-discover too?
[23:37] <clivejo> muon-common is now plasma-discover-common I believe
[23:37] <clivejo> packaged here - http://packages.ubuntu.com/xenial/plasma-discover
[23:38] <infinity> Kay, seeing the libmuon->libdiscover, *-common and *-discover relationships.
[23:38] <infinity> notifier and updates don't seem to be mentioned anywhere.
[23:38] <clivejo> libmuon doesnt exist any more
[23:38] <infinity> Ahh plasma-discover-updater is updater.
[23:38] <clivejo> plasma-discover-updater
[23:39] <clivejo> all part of plasma now
[23:39] <infinity> It's both.
[23:39] <infinity> Kay.
[23:39] <clivejo> basically it was all moved bar the Package Manager
[23:39] <infinity> The one thing I'd ask is that all those relationships that are currently Breaks/Replaces turn into Conflicts/Replaces, which apt takes as a hint to completely remove the old one for the new one.
[23:39] <clivejo> we werent going to package it, but a lot of users have said they still use it
[23:40] <infinity> Each of the dropped packages has a B/R in a plasma equiv.
[23:40] <clivejo> infinity: as you probably can tell Im very new to this
[23:40] <infinity> libmuon -> libdiscovercommon, plasma-discover-updater -> muon-notifier/muon-updater, plasma-discover -> muon-discover
[23:40] <infinity> I tihnk I missed one.
[23:41] <clivejo> the kubuntu team are under pressure and I took this on to try and learn
[23:41] <infinity> Oh, and plasma-discover-common -> muon-common
[23:42] <clivejo> trying to install muon currently in Xenial leads to an apt failure on libmuon
[23:42] <infinity> I guess I can upload to fix that all up.
[23:42] <infinity> I don't board for 8 minutes. :P
[23:43] <clivejo> have you a laptop?
[23:43] <infinity> Yeah. :)
[23:45] <infinity> Oh.
[23:45] <infinity> There are transitional packages in plasma-discover.  I didn't get far enough down the control file.
[23:47] <infinity> Accepted.  Please test upgrades from wily with all the muon stuff installed.
[23:47] <clivejo> thanks
[23:48] <clivejo> any feedback?
[23:48] <clivejo> does/dont's ?
[23:48] <infinity> Other than whining about upgrade paths, not really.  So, do test that it all actually works.
[23:48] <infinity> A full review is a bit hard, given the massive diff. :P
[23:48] <clivejo> I know it works in Xenial
[23:49] <infinity> Aaaand, boarding time.
[23:49] <clivejo> been using it myself for about 3 weeks
[23:49] <clivejo> have a good flight!
[23:49] <infinity> Back in 10 hours from the other side of the world.
[23:49] <clivejo> and thankyou!
[23:49] <clivejo> LOL im going to bed!