Re: [SRU] Set the default IO scheduler to CFQ in Kubuntu Trusty

2014-10-08 Thread Martin Pitt
Steve Langasek [2014-10-08 13:10 -0700]: > It has been pointed out that Ubuntu also has an indexer, zeitgeist, which > apparently doesn't suffer from the same problem. To clarify: For the most part, zeitgeist only stores access events, i. e. metadata like "accessed this video at this time". There

Re: [SRU] Set the default IO scheduler to CFQ in Kubuntu Trusty

2014-10-08 Thread Steve Langasek
On Wed, Oct 08, 2014 at 10:20:23AM -0700, Steve Langasek wrote: > On Wed, Oct 08, 2014 at 05:42:48PM +0100, Colin Ian King wrote: > > > Also, what exactly do you mean when you say baloo doesn't "implement > > > ionice > > > support"? The 'ionice' tool is part of the base system (util-linux). It

Re: [SRU] Set the default IO scheduler to CFQ in Kubuntu Trusty

2014-10-08 Thread Marc Deslauriers
On 14-10-08 01:25 PM, Steve Riley wrote: > On 2014-10-08 09:36:03 Steve Langasek wrote: >> >> I don't think it's at all appropriate for a desktop environment to install a >> udev rule which changes the kernel scheduler. That's a severe layering >> violation, and it means that anyone who installs

Re: [SRU] Set the default IO scheduler to CFQ in Kubuntu Trusty

2014-10-08 Thread Colin Ian King
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/10/14 17:36, Steve Langasek wrote: > Hi Jonathan, > > On Wed, Oct 08, 2014 at 03:56:42PM +0100, Jonathan Riddell wrote: >> Me and Rohan would like a second opinion on bug 1378789 >> [SRU] Set the default IO scheduler to CFQ in Kubuntu Trusty

Re: [SRU] Set the default IO scheduler to CFQ in Kubuntu Trusty

2014-10-08 Thread Steve Riley
On 2014-10-08 09:36:03 Steve Langasek wrote: > > I don't think it's at all appropriate for a desktop environment to install a > udev rule which changes the kernel scheduler. That's a severe layering > violation, and it means that anyone who installs kubuntu-desktop on an > existing system will si

Re: [SRU] Set the default IO scheduler to CFQ in Kubuntu Trusty

2014-10-08 Thread Steve Langasek
Hi Colin, On Wed, Oct 08, 2014 at 05:42:48PM +0100, Colin Ian King wrote: > > Also, what exactly do you mean when you say baloo doesn't "implement ionice > > support"? The 'ionice' tool is part of the base system (util-linux). It > > would be a simple matter of packaging to always run baloo unde

Re: [SRU] Set the default IO scheduler to CFQ in Kubuntu Trusty

2014-10-08 Thread Steve Langasek
Hi Jonathan, On Wed, Oct 08, 2014 at 03:56:42PM +0100, Jonathan Riddell wrote: > Me and Rohan would like a second opinion on bug 1378789 > [SRU] Set the default IO scheduler to CFQ in Kubuntu Trusty > https://launchpad.net/bugs/1378789 > The kernel team have changed the scheduler away from upst

Re: Juju SRU and QA plans

2014-10-08 Thread Adam Conrad
On Wed, Oct 08, 2014 at 12:49:05PM +0100, Robie Basak wrote: > On Wed, Oct 08, 2014 at 07:34:12AM -0400, Scott Kitterman wrote: > > If they aren't going to reuse the version number, why not go ahead and > > release? Seems much simpler workflow wise and if there's a problem, > > they're > > bump

[SRU] Set the default IO scheduler to CFQ in Kubuntu Trusty

2014-10-08 Thread Jonathan Riddell
Me and Rohan would like a second opinion on bug 1378789 [SRU] Set the default IO scheduler to CFQ in Kubuntu Trusty https://launchpad.net/bugs/1378789 The kernel team have changed the scheduler away from upstream Linux defaults to deadlock which causes our desktop indexing programme Baloo to run

Re: Juju SRU and QA plans

2014-10-08 Thread Tim
On 08/10/14 22:34, Scott Kitterman wrote: > On Wednesday, October 08, 2014 11:32:27 Robie Basak wrote: >> On Tue, Oct 07, 2014 at 07:30:49PM -0600, Adam Conrad wrote: >>> If upstream doesn't intend to reuse version numbers... >> Right. I've discussed this with upstream and they have committed to n

Re: Juju SRU and QA plans

2014-10-08 Thread Scott Kitterman
On Wednesday, October 08, 2014 17:38:01 Martin Pitt wrote: > Robie Basak [2014-10-08 11:19 +0100]: > > We don't have automatic dep8 test runs in trusty-proposed yet (which is > > bug 1321691), but this is something that is desirable. When we do have > > it, we're going to have a ton more QA going o

Re: Juju SRU and QA plans

2014-10-08 Thread Martin Pitt
Robie Basak [2014-10-08 11:19 +0100]: > We don't have automatic dep8 test runs in trusty-proposed yet (which is > bug 1321691), but this is something that is desirable. When we do have > it, we're going to have a ton more QA going on in trusty-proposed which > upstream can't realistically run. Not

Re: Juju SRU and QA plans

2014-10-08 Thread Robie Basak
On Wed, Oct 08, 2014 at 07:34:12AM -0400, Scott Kitterman wrote: > If they aren't going to reuse the version number, why not go ahead and > release? Seems much simpler workflow wise and if there's a problem, they're > bumping to a new version anyway. Nothing says they have to advertise the new

Re: Juju SRU and QA plans

2014-10-08 Thread Scott Kitterman
On Wednesday, October 08, 2014 11:32:27 Robie Basak wrote: > On Tue, Oct 07, 2014 at 07:30:49PM -0600, Adam Conrad wrote: > > If upstream doesn't intend to reuse version numbers... > > Right. I've discussed this with upstream and they have committed to not > re-using version numbers that they have

New component-mismatches for source universe -> main

2014-10-08 Thread process-component-mismatches-diff
The following universe packages have new reverse dependencies in main or got seeded. They need to get a MainInclusionReport and be promoted, or the reverse dependencies in main need to be dropped: o click-bin-path: click-bin-path [Reverse-Depends: Ubuntu.Utopic system-image seed] o cli

Re: Juju SRU and QA plans

2014-10-08 Thread Robie Basak
Replying to both Steve and Adam here, since I think they touch upon the same point. On Tue, Oct 07, 2014 at 05:14:57PM -0700, Steve Langasek wrote: > Given that Juju is covered by a provisional micro release exception[1], I > don't understand the ordering concern. MREs are granted on the conditio

Re: Juju SRU and QA plans

2014-10-08 Thread Robie Basak
On Wed, Oct 08, 2014 at 06:49:05AM +0200, Martin Pitt wrote: > Steve Langasek [2014-10-07 17:14 -0700]: > > Given that Juju is covered by a provisional micro release exception[1], I > > don't understand the ordering concern. MREs are granted on the condition > > that the upstream release process i