Bugfix release did not go as well as I was led to believe it would.

2016-04-14 Thread Scarlett Clark
libc6 was updated and broke some stuff leading to dependencies not being met. libksysguard I know was affected, but I found upstream patch https://phabricator.kde.org/D1010 and I uploaded ubuntu2 with said patch, as of 8PM it is still (waiting for approval) Anyway, in the future, never ever

New taglib v1.10

2016-04-14 Thread Valorie Zimmerman
Hello folks, does anyone have opinions about or have tested the newest taglib release? The Kubuntu team is being asked to package it, which is not likely to happen this close to our LTS release, but we could put it in backports, if it is a good idea

Re: [Bug 1546373] Re: [FFe] Please update to bugfix release 1.10

2016-04-14 Thread Aaron Honeycutt
I agree with Scarlett 100% since the release was in Nov (before the freeze I believe) we should have been told. It's much to late to include it since we are a week till release (USA wise). -- You received this bug notification because you are a member of Kubuntu Packagers, which is subscribed to

[Bug 1570551] [NEW] Merge plasma-discover 5.6.2-1 (universe) from Debian unstable (main)

2016-04-14 Thread Matthias Klumpp
Public bug reported: Please merge plasma-discover 5.6.2-1 (universe) from Debian unstable (main) The full Debian package can be synced to Ubuntu, but a Breaks/Replaces against the libdiscovercommon package (which does not exist in Debian) should be added. Reason for merging this so late in the

[Bug 1546373] Re: [FFe] Please update to bugfix release 1.10

2016-04-14 Thread Scarlett Clark
If the Kubuntu team is indeed responsible for packaging this, we should have been notified prior to this turning into a Ffe, don't you think? I myself am too busy, perhaps someone else will. This is unlikely so close to release. Scarlett -- You received this bug notification because you are a

Re: Review Request 127546: Can undo/redo "Unmark all".

2016-04-14 Thread Carlo Vanini
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/127546/ --- (Updated April 14, 2016, 5:21 p.m.) Status -- This change has been

CI Version number change

2016-04-14 Thread Jonathan Riddell
I noticed that our version numbers mean we can't reliable upgrade the foundation 1.0+git20160201+15.10 can't be upgraded to 1.0+git20160101+16.04 because the build for the newer foundation happens to be a bit older. So I changed it to 1.0+p15.10+git20160201 which can be upgraded to