[01:09] <mIKEjONE1> hey guys
[01:09] <mIKEjONE1> is there a way to build the kernel without having to build the whole thing from scratch everytime I make a change?
[01:09] <mIKEjONE1> I'm using fakeroot with debian/rules
[01:10] <mIKEjONE1> I'd like to have something that's able to only compile things that changed (i.e. the way Linux's Makefile works)
[01:32] <mIKEjONE1> it's getting kind of ridiculous, so any help would be greatly appreciated
[08:11] <apw> mIKEjONE1, yes after build if you want to change a few files and rebuild you can remove debian/stamp/stamp-build-<flavour> and then re-run fakeroot debian/rules binary-generic
[13:49] <rtg> henrix, kamal: I just sent a patch to the k-team list in reference to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397976/comments/4 - that commit looks good for stable.
[13:52] <henrix> rtg: yep, looks like it could be applied to 3.13 kernel (all others seem to have it already)
[13:52] <rtg> henrix, clean cherry-pick
[13:53] <henrix> rtg: cool, thanks.  kamal, i guess you can pick it ;-)
[13:54] <rtg> henrix, it might be a bit early for California slackers :)
[13:54] <henrix> heh, indeed
[13:54] <apw> henrix, so did we have that in P and fail to apply it to T somehow ?
[13:56] <henrix> apw: no, i we don't have it P but i believe it is not applicable to such an old kernel...
[13:56]  * henrix goes check
[13:56] <apw> henrix, ahh ok, it was the regression word that confused me
[13:58] <henrix> apw: right, so the issue was introduced by commit eafbe67f8476 ("n_tty: Refactor input_available_p() by call site"), which was cherry-picked into trusty.  so it *may* not even be applicable to stable 3.13, depending on whether or not it contains this commit
[13:59] <henrix> kamal: ^
[15:03] <jsalisbury> **
[15:03] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[15:03] <jsalisbury> **
[16:22] <kamal> rtg, apw, henrix: fyi, 3.13-stable does not contain eafbe67 "n_tty: Refactor input_available_p() by call site", so I'll take no action on that topic, barring further discussion.
[16:27] <henrix> kamal: ack
[16:55] <jsalisbury> ##
[16:55] <jsalisbury> ## Kernel team meeting in 5 minutes
[16:55] <jsalisbury> ##
[16:56] <bkero> Can I ask that someone install libssl-dev to the kernel build hosts so that we can actually generate kernel packages? http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-rc1-unstable/
[16:57] <bkero> Is that off-topic for the meeting?
[20:24] <hallyn> what is all this:
[20:24] <hallyn> root     22390     2  0 15:23 ?        00:00:00 [kworker/u16:88]
[20:26] <bkero> a kernel worker process
[20:28] <hallyn> why so many of them?
[20:28] <hallyn> (this is appears to be new)
[20:29] <hallyn> oh, actually they've died down
[20:29] <hallyn> perhaps a side-effect of resume.  interesting
[20:29] <bkero> It's a kernel thing
[20:29] <bkero> check out the kernel docs
[20:36] <rharper> is there any place to get previously published but superceeded kernels?  I've got an issue on the latest vivid kernel but works fine on the vivid released kernel;  would like to bisect but without building all of those kernels
[20:37] <sforshee> hallyn: entirely possible it was a result of resume, if that generated a lot of workqueue items. I think the kernel scales the number of worker threads.
[20:39] <sforshee> rharper: aren't they all still in the archive?
[20:40] <rharper> did a apt-cache policy linux-image-generic and only showed the latest; so I probably need some apt-fu to find it
[20:43] <sforshee> linux-image-generic is a meta package. Every new kernel version is its own package so that multiple kernels can be installed at the same time.
[20:44] <rharper> ah, ok
[20:44] <rharper> cool; I think I can get them now
[20:44] <rharper> sforshee: thanks
[20:44] <sforshee> np


[00:01] <Fudge> howdy
[16:57] <Daekdroom> !daily
[17:03] <Daekdroom> Hm. I don't think I should upgrade earlier in the development this time because I have so much stuff from the Software Centre.
[17:04] <penguin42> I do wonder how the numbers are working this time for non-kubuntu/edubuntu people where there isn't actually an alpha
[23:06] <Fudge> or even how pollished it will be without the extra community support


[01:40] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2856 Publishing packages
[01:57] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2856 Proposed pocket
[03:37] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2856 Release pocket
[11:23] -queuebot:#ubuntu-ci-eng- tsimonq2 mitya57, https://bileto.ubuntu.com/#/ticket/2819 Dependency wait (artful/pyqt5). Diff missing (artful/akonadi, artful/ciborium, artful/fcitx-qt5, artful/frameworkintegration, artful/hime, artful/kdeclarative, artful/kguiaddons, artful/kwayland, artful/libqtxdg, artful/lxqt-session, artful/maliit-framework, artful/openorienteering-mapper, artful/qlipper, artful/qtcharts-opensource-src, artful/qtconnectivity-opensource-src, artful/qtcre
[12:54] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2858 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[13:02] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2858 Generating diffs
[13:02] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2858 Pending binary packages
[13:18] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2858 Successfully built
[15:05] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2844 Diff missing (artful/openvswitch). Pending binary packages (artful/dpdk)
[15:25] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2844 Diff missing (artful/dpdk). Failed to build (artful/openvswitch)
[18:17] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2857 Needs rebuild due to burned version number


[03:47] <CarlFK> fdisk ins't in busybox?  (seems so)  so what can I use to see what disks have been found?
[13:03] <cjwatson> parted
[18:30] <CarlFK> thanks


[03:42] <tiwake> Ardonel: it was fun... wasent there for very long so enh, but the little bit I did see was pretty nice


[07:11] <wmp> hello, in ubuntu 14.04 i havent tun module, why? I using 3.13.0-29-generic with xen
[08:26] <apw> wmp, built-in perhaps ?
[08:30] <wmp> apw: possible, so how i should use it in xen pv?
[08:31] <apw> define use it, if it is built-in it is already usable
[16:48] <dupondje> still on-time to have some upstream kernel patch merged in 14.10 ?
[16:49] <apw> dupondje, there is a little, get them out to kernel-team@ asap
[16:50] <hallyn> apw: uh, interesting.  in utopic, pivot_root appears to DTRT.  But in trusty, when I do chroot followed by pivot_root, I get http://paste.ubuntu.com/8486998/
[16:50] <hallyn> I'm about to try in a clean utopic vm - my utopic laptop didn't do that though
[16:50] <hallyn> (chrootbreak is the classic chdir(..)-based chroot escape)
[16:52] <hallyn> oh wait
[16:52] <hallyn> i didn't unshare that time, lemme retry
[16:54] <dupondje> apw: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1374607
[16:54] <dupondje> and mailed to the list
[16:56] <apw> dupondje, great thanks
[17:01] <hallyn> nope, it definately works right in utopic and is broken in trusty
[17:03] <hallyn> http://paste.ubuntu.com/8487102/    -> it working in utopic
[17:07]  * hallyn whips up a script for all to enjoy
[17:08] <apw> hallyn, yeah can you file that for me, and drop the number here, and we'll look at it
[17:13] <hallyn> apw: will do
[17:26] <dupondje> apw: guess it can be added? its a quite important regression :(
[17:27] <apw> dupondje, likely assuming there are no regressions
[17:30] <dupondje> well now its completely screwed :) with the patch it works again, so :D
[17:30] <dupondje> and its an upstream patch, so :)
[17:46] <apw> i don't doubt it fixes your box, does it break any others is more of a worry
[17:46] <apw> anyhow, if you submitted it to kernel-team@ then it'll get reviewed
[18:26] <dupondje> I need to subscribe to the mailinglist before I can send mails to it ?
[18:26] <dupondje> cant see my mail on https://lists.ubuntu.com/archives/kernel-team/2014-October/thread.html
[18:27] <apw> dupondje, i can approve that
[18:27] <dupondje> ahh k, well I can subscribe, doesn't matter
[18:27] <Alive> Guys my kernel paniced after I uninstalled package crda.
[18:27] <dupondje> just send my mail an hour or so ago, and wanted to know why it didn't show yet :)
[18:28] <dupondje> you approve or i'll subscribe?
[18:28] <Alive> I filed a bug report.
[18:28] <Alive> Package crda has a priority of optional noted in its control file. One would thus not expect a kernel panic after uninstalling it.
[18:28] <Alive> Not sure when if ever anyone is going to get back to me on the report.
[18:29] <Alive> Can any of you reproduce this kernel panic on some play system ?
[18:29] <Alive> just uninstal crda and reboot.
[18:29] <Alive> :)
[18:30] <Alive> Not on your most important development machine like in my case...
[18:31] <Alive> :/
[18:31] <Alive> :(
[18:31] <Alive> This is the kernel that panicked: Linux ubuntu 3.13.0-36-generic
[18:32] <Alive> Release:	14.04
[18:32] <Alive> Codename:	trusty
[18:35] <Alive> Also manually trying to revert to an older kernel by renaming the vmlinuz links in the root directory does not work. The system will not even boot up into any recovery mode.
[18:53] <Alive> Thats me out.


[08:50] <hogar> sudo apt-get install ctorrent
[10:38] <raleeha> hi
[10:51] <guiverc> g'day raleeha, if you have a Lubuntu support question, just ask it (people answer when they can), if you want to talk, #lubuntu-offtopic
[20:04] <Mazigh> hello there


 I'm using Qps to monitor RAM usage. It seems a bit confusing (for a non-expert like me anyway). The RAM seemed to increase with each operation of the software (QGIS) but after reaching almost 50 GB it does not increase anymore. Also, I am doubtful that the software is actually using ~50GB constantly (I would guess it has some kind of garbage collection).. so my guess is Qps is actually showing the "consumed" RAM and that is why it only
[01:27] <arraybolt3> Rodrigo: Try looking at htop and see what it says. I find it a *lot* less confusing than Qps most of the time.
 I will. Thanks! (re @lubuntu_bot: (irc) <arraybolt3> Rodrigo: Try looking at htop and see what it says. I find it a *lot* less confusing than Qps most of the time.)
 yep, definitely it makes much more sense (re @lubuntu_bot: (irc) <arraybolt3> Rodrigo: Try looking at htop and see what it says. I find it a *lot* less confusing than Qps most of the time.)