=== bjf is now known as bjf[afk]
[00:09] <jjohansen> daishadar: most things will still work
[00:10] <jjohansen> daishadar: the ubuntu specific patches provide features, drivers, and fixes that are not upstream yet, and in some cases will never be upstream but are useful in their current state for our users
[00:11] <jjohansen> eg. aufs is used to provide union mounts for the livecds and schroots
[00:12] <jjohansen> ndiswrapper lets users fall back to windows wireless drivers
=== sconklin is now known as sconklin-gone
[00:13] <daishadar> i see... so they may be things i notice but they should be relatively minor, depending on what features i'm using
[00:13] <jjohansen> AppArmor provides the default MAC, but if you boot without things will work you just won't have the extra restrictions on some applications
[00:14] <daishadar> the other problem is that i will lose binary drivers (e.g. nvidia), right?  but i should be able to download those from the manufacturer's website...
[00:15] <jjohansen> right you loose prepackaged binary drivers, but with some digging you can find the source stubs and blobs and compile them
[00:15] <jjohansen> where you get them just depends
[00:15] <jjohansen> usually from the manufactures website or out of ubuntu DKMS packages
[00:18] <daishadar> ok, great, so it sounds like it's reasonable.  i'm thinking about buying a thinkpad t410s laptop but apparently there are major issues if you aren't running 2.6.34
[00:21] <ogasawara> jjohansen: \o/, just saw your email
[00:24] <jjohansen> 5
[00:24] <jjohansen> hehe, lets try that again
[00:24] <jjohansen> 5
[00:24] <jjohansen>   \o
[00:25] <ogasawara> will definitely have to highlight that in the release meeting tomorrow
[00:26] <jjohansen> ogasawara: I'll get you a request pull out as soon as I rebase and verify
[00:26] <ogasawara> jjohansen: cool, thanks
[00:36] <jjohansen> ogasawara: I have a couple kernel related work items that won't make tomorrows freeze but may make feature freeze deadline, should I just push those items out now?
[00:37] <ogasawara> jjohansen: yah, go ahead and push them out to be safe
[00:37] <jjohansen> okay
[00:45] <bjf[afk]> jjohansen, that's fantastic, good job
[00:45] <jjohansen> thanks :)
=== jeff_ is now known as Guest27050
[01:56]  * bjf[afk] wants to scream about the build scripts
[02:31] <xsaiddx> hello guys 
[02:31] <xsaiddx> i got this on start up
[02:31] <xsaiddx> http://pastebin.com/kgSrGqe5
[02:31] <xsaiddx> anyone ca help me pls
[02:33] <jjohansen> xsaiddx: ubuntu kernel? or other?
[02:33] <jjohansen> was this a clean install or an upgrade?
[02:33] <xsaiddx> jjohansen, sorry
[02:34] <xsaiddx> i didnt get you
[02:35] <jjohansen> basically there is not enough information to figure out what is happening
[02:35] <xsaiddx> no i removed plymouth and it takes off mostly all of the packges
[02:35] <jjohansen> ugh, uhmm yeah that is a problem
[02:36] <xsaiddx> so i had to install an image kernel  and follwin that tip in the end of it it says 
[02:36] <xsaiddx> unlink sbin/init so i got this message i showed you
[02:36] <xsaiddx> and b4 i had acces only to my console
[02:36] <xsaiddx> but like this xsaiddx@none
[02:37] <jjohansen> hrmm, what do you still have access too?
[02:37] <jjohansen> for ex. can you reinstall plymouth
[02:37] <xsaiddx> no
[02:38] <xsaiddx> now only acces to see that nice message and thats it
[02:38] <xsaiddx> : D
[02:38] <xsaiddx> i can go live via a cd and do link sbin/init ?
[02:38] <jjohansen> hrmm can you boot a livecd, or usbstick?
[02:38] <xsaiddx> wud it work
[02:38] <xsaiddx> yeh
[02:38] <jk-> xsaiddx: you could try booting with init=/bin/sh
[02:39] <xsaiddx> uhm how cus i cant type anythin
[02:39] <xsaiddx> or you mean from the live cd
[02:39] <jk-> xsaiddx: at the grub prompt
[02:39] <xsaiddx> theres no grub now
[02:39] <jjohansen> hold down the left shift key at boot
[02:39] <jk-> shift to get the grub menu
[02:39] <jjohansen> has to be left shift
[02:39] <jk-> select the right boot option, press 'e' to edit it
[02:40] <jk-> https://wiki.ubuntu.com/DebuggingKernelBoot
[02:40] <jk-> instead of step 3, add 'init=/bin/bash'
[02:40] <jk-> (probably remove 'splash' and 'quiet' too actually)
[02:42] <jk-> which 'tip' were you following that told you to remove init?
[02:43] <xsaiddx> jk ill link you
[02:43] <xsaiddx> http://forum.phillw.net/viewtopic.php?f=4&t=35, this
[02:43]  * jk- looks
[02:43] <xsaiddx> jk btw where ishud type that init
[02:44] <jk-> xsaiddx: what is on your screen at the moment?
[02:45] <xsaiddx> jk??
[02:45] <xsaiddx> sory didnt get you 
[02:45] <jk-> what do you have on your screen now?
[02:45] <jk-> are you in grub?
[02:45] <xsaiddx> no im on xp 
[02:46] <xsaiddx> now
[02:46] <xsaiddx> when i start lubuntu theres no grub
[02:46] <jk-> xsaiddx: instructions are here: https://wiki.ubuntu.com/DebuggingKernelBoot
[02:46] <xsaiddx> jsut that message i shpwed you
[02:47] <jk-> jjohansen: hm, wiki says 'escape' for some reason
[02:47] <jjohansen> ????, its always been left shift for me
[02:47] <jk-> jjohansen: i blame manjo :)
[02:47] <xsaiddx> jk well hit esc then what
[02:48] <jjohansen> yeah its got to be manjo
[02:48] <jk-> xsaiddx: then read the next step
[02:48] <jk-> xsaiddx: if escape doesn't work, try left-shift instead.
[02:48] <xsaiddx> yeh but still didnt get it sorry
[02:49] <xsaiddx> can you tell me what to do 
[02:49] <jk-> xsaiddx: do you have important stuff on that machine? maybe a reinstall is besst
[02:49] <xsaiddx> yeh 
[02:50] <xsaiddx> and i  dont like the idea to reinstall all
[02:50] <jk-> 1) reboot the computer
[02:51] <xsaiddx> yeh ten
[02:51] <xsaiddx> then
[02:51] <jk-> 2) after the BIOS screen goes away, press left shift
[02:51] <jk-> and hold it down
[02:51] <jk-> you should get the grub screen
[02:51] <xsaiddx> then
[02:52] <jk-> is this a separate computer? can you do this as we talk?
[02:52] <xsaiddx> no i have dual boot
[02:53] <jk-> so you're going to remember this stuff?
[02:53] <xsaiddx> you can tell me im takin notes tho
[02:54] <xsaiddx> hello jk
[02:56] <xsaiddx> jk-, hello
[02:56] <jk-> xsaiddx: just a sec
[02:56] <xsaiddx> ok
[02:57] <xsaiddx> sure
[02:57] <jk-> xsaiddx: print this out: https://wiki.ubuntu.com/DebuggingKernelBoot
[02:57] <jk-> xsaiddx: before you press 'b', add "init=/bin/bash"
[02:58] <xsaiddx> dude my english sux and i didnt get that doc so thats why iwas askin your help clearly
[02:58] <jk-> I've just re-written the doc for you
[02:59] <xsaiddx> where i can add that init.... ?
[02:59] <jk-> xsaiddx: however, you will need to do a few more things after you've done that boot, and I can't tell you what you need to do there
[02:59] <xsaiddx> why i have to tell wht im goin to get so you can kno is it
[02:59] <xsaiddx> i can go and see now and come bk n tell you
[03:00] <jk-> sorry, i don't understand either of those lines. could you rephrase?
[03:00] <xsaiddx> jk-, well im goin to try okies brb please and tnx for ur help
[03:01] <xsaiddx> i said
[03:01] <xsaiddx> you cant tell me wht to do after that 
[03:01] <jk-> i would suggest these commands, but I can't be sure:
[03:01] <xsaiddx> cus you need to see wht im goin to have as an error so you can kno the issue
[03:02] <xsaiddx> so i said ican go and come back to tell you
[03:02] <xsaiddx> okies ?
[03:02] <xsaiddx> well im goin now
[03:02] <xsaiddx> but i jst wnana kno when gettin grub when ishall add tat init=...
[03:02] <jk-> apt-get install --reinstall linux-image-generic-$(uname -r)
[03:02] <jk-> xsaiddx: it says where to add it in that document
[03:03] <jk-> sorry, make that:
[03:03] <jk-> apt-get install --reinstall linux-image-$(uname -r)
[03:04] <jk-> i have updated the document with more details. please refresh the page to see the latest version
[03:04] <xsaiddx> ok
[03:05] <jk-> also, apt-get install --reinstall upstart
[03:06] <xsaiddx> ok ill get back to you tnx
[03:06] <xsaiddx> wish me luck 
[05:13] <cooloney> ericm: how can i build the upstream kernel for omap without defconfig file?
[05:31] <jk-> cooloney: the defconfigs should still be there, no?
[05:35] <cooloney> jk-: no omap4_panda_defconfig
[05:35] <jk-> ah
[05:35] <jk-> menuconfig? :)
[05:35] <cooloney> and i tried to build the omap kernel from Tony's linux-omap tree
[05:35] <cooloney> it failed
[05:35] <cooloney> weird
[05:36] <cooloney> jk-: yeah, i chose TI OMAP system, it will select omap2/3/4 and build for Panda board as well
[05:46] <cooloney> jk-: my bad. i just turned on ARCH_OMAP. forget to turn off OMAP2 and OMAP3
[05:46] <cooloney> now it is building 
[05:58] <jk-> ericm, cooloney: pull request sent, for the debug macro changes
[06:08] <ripps> It looks like l-b-m and linux-meta were merged together, and now linux-meta is held up in NEW. How long before it gets into the repos?
[07:02] <ericm> cooloney, I don't think omap4_panda_defconfig is gonna squeeze into mainline recently
[07:23] <cooloney> ericm: i know, it was enabled in omap_4430sdp_defconfig
[07:24] <cooloney> ericm: i can build the kernel, but doesn't boot on my board. serial port driver is not set to the right one
[07:32] <ericm> cooloney, that always happen, maybe you should change the command line in u-boot
[07:43] <cooloney> ericm: still checking the right config, will let you know the result.
[07:43] <cooloney> ericm: btw, i am trying tony's linux-omap tree instead of linus mainline
[07:43] <ericm> cool
[08:58] <trapmax> anyone experiencing "INFO: task x blocked for more than 120 seconds." messages. In our system it gets triggered when using lvcreate. Started after updating to 2.6.32-24-server -kernel. Workaround?
[08:59] <RAOF> trapmax: That'll happen when something bogs down so much that forward progress doesn't get made fast enough.  I've managed to get almost all my tasks to spit that message when doing a bunch of I/O in btrfs.
[09:00] <trapmax> RAOF: this did not happen before updating to newest kernel
[09:00] <RAOF> I'd guess that what's happening is lvcreate is blocking I/O, and is chomping on long enough to trigger that messsage for your other tasks to trigger the message.
[09:00] <smb> Usually there would be a backtrace about it. To offer more info
[09:01] <trapmax> http://pastebin.com/KUzVGZSQ
[09:01] <smb> Most of the -24 update was ext4 which would not have an impact on lvcreate though
[09:01] <smb> Oh, actually it is ext4 related...
[09:01] <trapmax> we have ext4 environment though
[09:02] <smb> I was just wondering because lvcreate itself does no filesystem
[09:03] <smb> It could be related to the general writeback regression that we are currently seeing with 2.6.32 kernels. Maybe the ext4 update in some cases just makes it happen more often
[09:04] <trapmax> this makes our lvm-snapshot -backup virtually impossible
[09:04] <smb> trapmax, I got some test kernels to try if you want to.
[09:05] <trapmax> production server. not really confident with that option
[09:09] <smb> trapmax, Hm, hard to offer a workaround that way. The ext4 updates are verified to fix some data integrity issues and seem to cause long(er) IO times in your case
[09:09] <smb> the bug in question would be bug 585092
[09:09] <ubot2> Launchpad bug 585092 in linux (Ubuntu) "giant IO delays (affects: 1) (heat: 20)" [Medium,Triaged] https://launchpad.net/bugs/585092
[09:10] <smb> As this relates to some syncs done synchronously, I wonder whether issuing manual sync's from the command line change anything
[09:11] <trapmax> we have manual sync runnin with 5s sleep
[09:12] <smb> Hm, ok
[09:15] <smb> trapmax, All the backtraces in your log somehow go through writeback. I am currently trying to get some feedback on the backport of the writeback patches which are in the test kernels. But this will take a bit.
[09:16] <smb> Until then the only thing to play with seems to be the interval of the manual sync. The previous kernels somehow worked but from the tests that were done for the ext4 patches I would not really recommend going back to those old kernel.
=== lag is now known as lag-day-off
[09:19] <trapmax> smb: ack
[09:43] <jjohansen> rebooting
[09:43]  * smb blinks
[10:00] <jjohansen> urghh, don't update!!!
[10:01] <smb> jjohansen, Maverick kernel? Or something else?
[10:01] <jjohansen> many things
[10:01] <jjohansen> seems kernel is broken for networking
[10:01]  * smb thinks jjohansen should be sleeping instead of updating anyway ;-=
[10:01] <jjohansen> theme is broken
[10:02] <jjohansen> gnome panel seems to be broken
[10:02] <smb> Seems everything is ready to alpha3
[10:02] <smb> Have we been doing something in the networking area?
[10:02] <jjohansen> I have a high load almost 50% each cpu, but nothing is showing up via, top, htop etc
[10:03] <jjohansen> the load isn't the kernel as I had to reboot into an older kernel, and it still remains
[10:03] <smb> jjohansen, would perf give more hints?
[10:03] <jjohansen> smb maybe
[10:04] <RAOF> You might need to re-run apt; they're discussing the gtk update which is probably what has caused your “everything broken”
[10:05] <jjohansen> theme is comletely broken too, I had to revert to human :)
[10:06]  * smb likes human. :)
[10:06] <jjohansen> RAOF: already have no dice
[10:06] <RAOF> That, plus a reboot, fixed it for me.  Although I didn't have a high load.
[10:07] <jjohansen> I'm sure it will get sorted out, soon just putting out the warning that now is not a good time to update
[10:08] <jjohansen> smb: do we have a wiki on perf yet
[10:08] <smb> I guess an indication that its not kernel or is would be good to know for Leann on the release meeting
[10:09] <smb> jjohansen, I am not sure. Maybe not
[10:09] <smb> I usually try "perf top" first, that would give an overview on calls
[10:10] <smb> jjohansen, Other than that maybe in some presentation slides from chase
[10:11] <smb> II think the other was a "sudo perf record" paired with a "perf report"
[10:12] <jjohansen> smb: right, but that records a command, I was looking for a way to just get a sampling of all commands and kernel fns
[10:12] <jjohansen> after all what I am seeing is not showing up
[10:13] <smb> Would "sudo perf record -a -f -c 5000" be what you are looking for
[10:14] <smb> The 5000 might be a tad long
[10:14] <jjohansen> maybe
[10:14] <smb> I was stabbing in the dark with the count
[10:15] <smb> Seems already quite long with 50
[10:16] <jjohansen> something is really hammering my system load average 3.28 2.10 1.18
[10:16] <smb> Strangely you would expect it to show up in top if it gets accounted in the load
[10:17] <jjohansen> cpus are varying between 30- 100%, but htop isn't showing
[10:17] <jjohansen> that is it shows the cpu load and the processes are like 7%, 9% etc just small little figures
[10:18] <smb> I thought that one patch from Chase about accounting small runtimes went upstream as well
[10:20] <jjohansen> hrmm, so did I
[10:20] <smb> jjohansen, btw, -c# is not really needed. And i have no clue what it relates to
[10:20] <jjohansen> I think its something to do with panel icons, as they have been slowly showing up, 1 by 1
[10:21] <jjohansen> I now have a wifi icon, and a screen orientation icon, which I didn't before
[10:21] <smb> I see no such thing here. Oh, you mean your load
[10:21] <jjohansen> yeah
[10:22] <smb> So you could try "sudo perf record -f -a", let it run a bit then ctrl-c
[10:22] <smb> Then do "sudo perf report"
[10:23] <jjohansen> yeah, I'll give that a try, as soon as I get perf installed on this machine, the install is crawling
[10:25] <smb> jjohansen, Maybe start it and get some rest? :) I see your continent mostly in the dark...
[10:26] <jjohansen> hehe, no I am going to finish getting a pv-ops kernel together and fix my AA request-pull
[10:28] <smb> jjohansen, *sigh* There is always the next thing to do. ;-)
[10:29] <jjohansen> hehe, yeah but I want this to make kernel freeze for alpha-3 so ...
[10:29] <jjohansen> rebooting
=== ericm|ubuntu is now known as ericm-away
=== yofel_ is now known as yofel
=== cndougla is now known as cnd
=== TeTeT_ is now known as TeTeT
[13:28] <smoser> hi. i'm guessing this is known, but just want to make sure if its not already resolved that someone is looking at it:
[13:28] <smoser> The following packages have unmet dependencies:
[13:28] <smoser>   linux-virtual: Depends: linux-image-virtual (= 2.6.35.11.12) but it is not going to be
[13:28] <smoser> installed
[13:28] <smoser> , stderr: E: Broken packages
[13:30] <smb> smoser, Hm, it feels like ringing a bell. Though I am not sure whether this was back in a previous release. Could you send this hint to the kernel-team mailing list as a more permanent reminder?
[13:30] <smoser> this is last night maverick
[13:30] <smoser> the uec build fails due to that.
[13:30] <smoser> i'll send mail.
[13:32] <smb> Ok, thanks. The kernel looked like a recent Maverick. It just sounded familiar but usually I am not so much looking at the bleeding edge. :)
[13:36] <smoser> it seems to me that its fixed now.
[13:38] <smb> Hm, maybe that was just a delay in the archive...
[13:39] <smb> I would not think that someone had a chance to change anything, yet. Though there are some early birds...
=== bjf[afk] is now known as bjf
[14:43] <smb> tgardner, Re: bug to look at: ok. I have also seen some reports of problems with lvm snapshot since the ext4 patches went into updates. I have not yet looked at the other bug but it seems some changes in ext4 might trigger the bad writeback behaviour or even hangs there. Just fyi
[14:46] <tgardner> smb, ack. you should verify the kernel version they are running to see if there is a strong correlation
[14:48] <diwic> bjf, ping
[14:57] <bjf> diwic, go
[14:58] <diwic> bjf, just wondering what time takashi releases his daily and if your c-o-d's are synced to that
[14:59] <diwic> bjf, but it matters less as launchpad is three days behind. :-(
[14:59] <bjf> diwic, don't know and no
[14:59] <bjf> diwic, let me check
[15:18] <bjf> diwic, i just pushed a source package, i'll look at my cron job to see what's up with that
[15:38] <jjohansen> ogasawara: you about?
[15:39] <ogasawara> jjohansen: yep
[15:40] <ogasawara> jjohansen: saw both your apparmor and pv-ops pull requests, will review and apply momentarily
[15:40] <jjohansen> I am updating specs, and pushing out the pv-on-HVM part of pvops out to next week
[15:40] <ogasawara> jjohansen: ack, sounds good
[15:41] <jjohansen> ogasawara: so the pv-ops one doesn't include pv-on-HVM drivers which is what I am pushing out.
[15:41] <jjohansen> I am putting in an explanation of them
[15:42] <ogasawara> jjohansen: perfect, thanks
[15:48] <jjohansen> ogasawara: check your mail
[15:49] <ogasawara> jjohansen: ack
[15:53] <ogasawara> jjohansen: have you slept yet?
[15:53] <jjohansen> no
[15:53] <ogasawara> jjohansen: go take a nap
[15:54] <jjohansen> soon
[17:08] <jjohansen> -> nap
[17:09] <manjo> nap ? 
[17:10] <manjo> jjohansen, you ?
[17:11] <jjohansen> manjo: no its my evil twin
[17:12] <manjo> jjohansen, hmmm that sound more possible :) 
[17:12]  * manjo have never seen jjohansen sleep
[17:15] <tgardner> ogasawara, I've a couple of issues with jj's pv-ops pull request. I'll fix 'em up and send you an alternate pull request
[17:16] <ogasawara> tgardner: cool thanks, I haven't had a chance to review yet anyways
[17:16] <ev> Would anyone be willing to add the fix for bug 599569 to the next 10.04 update?  It works perfectly on the two 10.04 systems I've tested it with.
[17:16] <ubot2> Launchpad bug 599569 in linux (Ubuntu) "No kernel support for Sierra Wireless 250U 3G/4G USB Dongle (affects: 4) (heat: 24)" [Undecided,Triaged] https://launchpad.net/bugs/599569
[17:17] <tgardner> ev, I think the stable team accepts bribes
[17:17] <ogasawara> looks like stable was CC'd on the upstream patch
[17:18] <ogasawara> so should be coming down the queue already?
[17:18] <ev> name your price and I'll smuggle it it across the border when I go to Debconf tomorrow
[17:18] <smb> If thats true it will come sooner or later
[17:18] <smb> I would need to check the queue
[17:18] <smb> ...
[17:18] <ev> oh, cool
[17:21] <smb> ev, There is a USB: Add PID for Sierra 250U to drivers/usb/serial/sierra.c queued for the next (2.6.32.17) release from upstream stable
[17:21] <ev> hooray
[17:22] <tgardner> ev, don't hold your breath. it could still take weeks.
[17:22] <ev> well, I've solved the problem for myself (well, my dad really)
[17:23] <ev> I'd just like to make sure it gets solved for others
[17:23] <ev> which seems to be happing, glacial pace or otherwise
[17:23] <ev> :)
=== sconklin-gone is now known as sconklin
[17:52] <cwillu_at_work> iotop reports CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN and IO %
[17:53] <cwillu_at_work> it's one thing to not know I'm missing out, it's quite another when a program tells me I'm missing out :)
[17:55] <jpds> cwillu_at_work: bug #493156.
[17:55] <ubot2> Launchpad bug 493156 in linux (Ubuntu) (and 1 other project) "Please enable CONFIG_TASK_DELAY_ACCT (affects: 55) (dups: 3) (heat: 232)" [Medium,Fix released] https://launchpad.net/bugs/493156
[17:56] <tgardner> cwillu_at_work, use maverick, or the LTS backport kernel on Lucid
[17:56] <cwillu_at_work> okay, thanks
[17:56]  * cwillu_at_work reads the relevant threads
[18:16] <cwillu_at_work> also, is there any way to make swap act... sane? by which I mean:  at the end of my day, everything is running smoothly:  gedit, inkscape, firefox, they all run without hiccups.  However, at the start of my day, I have to wait 5-15 seconds at fairly random intervals as those applications hang, presumably swapping back in on demand
[18:19] <cwillu_at_work> case in point:  inkscape just spent the last thirty seconds paging in at around 1mb/s;  however there was no disk write traffic at the same time:  to me, this implies that memory is available, but the allocation policy is buggered
[18:26] <tgardner> ogasawara, I reset jj
[18:26] <tgardner> I resent jj's pull request
[18:27] <ogasawara> tgardner: ack.  my tree is somehow corrupted at the moment so am getting it fixed back up first
[18:27] <bjf> anyone else notice the daily live isos have not changed for 3 days?
[18:28] <tgardner> oh, bummer. bad disk, or fat fingers?
[18:28] <ogasawara> tgardner: I have a feeling it might be the disk :(
[18:29] <tgardner> ogasawara, back to the trusty, but ancient, laptop
[18:36] <sconklin> I'm bailing for the rest of the day, I feel terrible. See you Monday!
=== sconklin is now known as sconklin-gone
[18:53]  * tgardner lunches
[19:40]  * ogasawara runs errands, back in an hour
[21:10]  * bjf taking a headache break
=== bjf is now known as bjf[afk]
[21:48] <jjohansen> ogasawara: hrmm, what happend that my patches needed to be reset?
[21:49] <ogasawara> jjohansen: looked like just minor commit log changes that tim made a small tweak with updateconfigs
[21:50] <jjohansen> hrrm, I'll poke at what he did, I did do a rebase that did a 3 way merge, perhaps that did something?
[22:00] <jjohansen> ogasawara: is there anything you would like help on, or should I dive back into pv-on-HVM drivers?
[22:00] <ogasawara> jjohansen: nope, looking good on my side.  just waiting for test builds on ports to finish before I push all the bits
[22:01] <jjohansen> okay
[22:10] <manjo> jjohansen, you did not sleep enough 
[22:11] <jjohansen> manjo: ? really I thought almost 5 hours was pretty good
[22:11] <jjohansen> well 4.5h maybe
[22:12] <manjo> jjohansen, good for 4.5 days atleast! 
[22:12] <manjo> :)
[22:12] <jjohansen> :)
[22:21] <manjo> adios amigos .. have a good weekend
[23:26] <cwillu_at_work> What's the trick to run make-kpkg in a freshly clone'd git repo?
[23:26] <cwillu_at_work> It's complaining about a missing files list file, which I can't imagine I have to actually build by hand