[00:43] <bjf> manjo, i've looked at uck, what about it?
[08:32]  * apw yawns
[08:34] <cooloney> apw: morning
[08:34] <apw> morning
[09:34] <jk-> brb, rewiring house
[09:36] <RAOF> And you'll be right back? :)
[09:42] <jk-> back
[09:51] <kraut> moin
[11:05] <apw> ikepanhc, hey you about ?
[11:05] <ikepanhc> apw: yes
[11:05] <ikepanhc> apw: anything?
[11:05] <apw> ikepanhc, is the current version of the karmic netbook branch well current
[11:06] <apw> ikepanhc, in order to apply debian commonisation to it i need to 1) modify it and 2) rebase it to the current proposed kernel
[11:06] <apw> ikepanhc, so i want to be sure you've not got a modified version
[11:07] <ikepanhc> apw: I do not aware who is using the branch, can you give me a hint?
[11:07] <apw> ikepanhc, the karmic netbook branch is the karmic equivalent of hardy netbook-lpia ... i thought you sort of looked after those for OEM
[11:08] <ikepanhc> apw: as I know, we have oem projects using jaunty and hardy netbook branch
[11:08] <apw> ikepanhc, ok so its likely as anything a dead branch
[11:08] <apw> ikepanhc, and if you don't have any interest in it i can just 'do it' ...
[11:08] <apw> thanks
[11:09] <ikepanhc> apw: can wait for US guys awake? so that I can ask them
[11:10] <apw> ikepanhc, i can, though if you arn't maintaining it for them, and i am not, then i suspect they arn't using it
[11:10] <apw> origin/master        Ubuntu-2.6.31-22.61
[11:10] <apw> origin/netbook       Ubuntu-2.6.31-14.47
[11:10] <ikepanhc> apw: yeah, that's what I am going to ask, if anyone need a rebase on karmic netbook-lpia branch
[11:10] <apw> oh dear, its 8 ABI bumps behind ... perhaps it really is _dead_
[11:11] <apw> ikepanhc, ok thanks man if you could ask, don't stay up till midnight to find out, i can wait till tomorrow no bother
[11:12] <ikepanhc> apw: thanks, I need to finish hardy netbook branch rebase today, otherwise too much action item queue for me
[11:13] <apw> good luck with that :)
[11:14] <ikepanhc> apw: almost, just find out I forget to update debian/control
[11:14] <apw> ikepanhc, we removed those generated files from the git repository on the other branches
[11:15] <apw> that way they are missing rather than wrong if you don't clean before building, and the source package build fails then
[11:15] <ikepanhc> apw: lrm/lum is removed, but not lbm :(
[11:16] <apw> urgle, rip them out so you don't hit it again
[11:16] <ikepanhc> apw: good idea
[11:17] <ikepanhc> apw: btw, can take some time from you reviewing the removing LGUEST_GUEST config patch? Steve gave me a green light on removing it
[11:18] <apw> ikepanhc, will have a look yep
[11:18] <ikepanhc> apw: thanks
[11:21] <apw> ikepanhc, done
[11:22] <ikepanhc> apw: thanks a lot..
[12:11]  * apw wanders out to get some parts
[13:20] <apw> amazing ... success
[13:51] <nessita> tgardner: good morning! I performed the Lucid server install, yesterday, and then installed the backport of the maverick kernel. Got oops-free dmesg outputs showing the e1000e issue
[13:51] <ubot2> https://lp-oops.canonical.com/oops.py/?oopsid=free
[13:52] <nessita> tgardner: both dmesg output (lucid kernel, backported kernel) are attached to the bug report (#591707)
[13:53] <nessita> ubot2: link please?
[13:53] <ubot2> Factoid 'link please?' not found
[13:53] <nessita> bummer
[13:54] <nessita> tgardner: I guess I don't need to tell that I still have no eth0 :-)
[13:56] <tgardner> nessita, ack.
[14:04] <tgardner> nessita, ok, one last test. Lets try a vanilla upstream kernel (http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc2-maverick/linux-image-2.6.35-020635rc2-generic_2.6.35-020635rc2_amd64.deb) to make sure there isn't an Ubuntu patch causing problems.
[14:05] <nessita> tgardner: bien sur, monsier. Would that installs in lucid?
[14:05] <tgardner> nessita, yes, it should work fine in your server flavour installation
[14:06] <nessita> ok, I'll try as soon as I finish some code reviews
[14:06] <tgardner> nessita, np, thanks for your time
[14:38]  * abogani2 waves
[14:39] <abogani2> apw: ping
[14:49] <abogani2> apw: Only for information I'm keeping up-to-date lowlatency git tree on Zinc and I'm also doing build test on my PPA: https://launchpad.net/~abogani/+archive/fix-436043/+packages
[15:03] <nessita> tgardner: test done, no eth0 with the vanilla kernel, dmesg ouput attached to https://bugs.launchpad.net/ubuntu/maverick/+source/linux/+bug/591707
[15:03] <ubot2> Launchpad bug 591707 in linux (Ubuntu Maverick) (and 1 other project) "After upgrade lucid -> maverick eth0 interface is gone (affects: 1) (dups: 1) (heat: 16)" [High,In progress]
[15:10] <tgardner> nessita, ok, I've sent an email to the e1000e Intel developers list
[15:12] <nessita> tgardner: yey!
[15:12] <nessita> tgardner: keep me posted, please. The connection through the USB dongle sucks :-/
[15:14] <tgardner> nessita, if you really need Maverick user space, its quite likely the Lucid kernel would work just fine. its worth a try.
[15:14] <nessita> tgardner: video is messed up in my maverick installation using lucid kernel
[15:15] <tgardner> nessita, I guess thats life on the bleeding edge :)
[15:15]  * nessita loves adrenaline
[15:29] <ogasawara> apw: that check-alias build failure is odd.  I expected the ports to fail in the latest upload, but they built just fine.
[15:30] <tgardner> ogasawara, are the tools versions changing?
[15:30] <ogasawara> tgardner: hrm, I'd have to check
[15:30] <apw> ogasawara, yeah its 'dependant' on the state of the tree whether it triggers
[15:30] <apw> i've taken the liberty of direct pushing a fix for it to your tree
[15:31] <ogasawara> apw: cool
[15:31] <apw> that allowed me to test it on the mainline builds, which trigger it every time
[15:39] <apw> ogasawara, which in better news the 35-rc2 build has built correctly for the first time
[16:42] <phunge0> achiang: https://bugzilla.kernel.org/show_bug.cgi?id=16090
[16:42] <phunge0> achiang: https://bugzilla.kernel.org/show_bug.cgi?id=16161
[16:42] <ubot2> bugzilla.kernel.org bug 16090 in PCI "sysfs: cannot create duplicate filename" [Normal,New]
[16:42] <ubot2> bugzilla.kernel.org bug 16161 in Video(Other) "[2.6.35-rc1 regression] sysfs: cannot create duplicate filename ... XVR-600 related?" [Normal,New]
[16:43] <achiang> phunge0: ugh, thanks for reminding me. i've been busy lately. :(
[16:44] <phunge0> np, understood
[16:46] <achiang> phunge0: the issue, which i haven't figured out a nice way to fix yet, is that pci_sysfs_init() calls pci_create_sysfs_dev_files(), which then calls pci_create_slot_links()
[16:47] <achiang> phunge0: preventing pci_create_slot_links() from being called during init would fix it, but i wonder why some of the other things like pci_create_capabilities_sysfs() seem to be fine
[16:47] <achiang> phunge0: if you want to explore this area, i'd be happy to give you pointers. :)
[16:49] <phunge0> achiang: i can take a quick look
[16:49] <phunge0> achiang: but given that 2.6.35 is -rc2 people are starting to notice
[16:50] <achiang> nod
[16:50] <tgardner> nessita, inbound email re: e1000e
[16:52] <nessita> tgardner: ok... I'll check. I hate flashing the BIOS :-(
[16:52] <tgardner> nessita, yeah, its always a bit risky.
[16:52] <achiang> phunge0: i just asked jesse to revert it. i'll try and find some time in the next merge window to get it working properly, i guess
[16:53] <achiang> phunge0: especially since i have a reproducer
[16:53] <achiang> phunge0: thanks for your help
[16:53] <phunge0> achiang: np, makes sense to me
[16:53] <nessita> tgardner: other than updating the BIOS, there is nothing else I can try?
[16:53] <tgardner> nessita, so far thats the only suggestion that I have from Intel
[16:54] <achiang> phunge0: if you want to keep an eye out for the revert and help manage the bugzillas though, that would be awesome...
[16:54] <nessita> tgardner: ok, thank you, I'll keep you posted
[16:54] <tgardner> nessita, if the BIOS upgrade doesn't fix it, then I'll have to instrument the driver and give you a custom kernel 
[16:55] <nessita> right...
[16:55] <phunge0> achiang: sure, i keep an eye on lkml... though i'm not comfortable doing the revert request myself :)
[16:55] <achiang> phunge0: oh, i just pinged jesse on irc, so that part's taken care of.
[16:56] <achiang> phunge0: when it hits linus's tree, if you could close out the bz's that would be lovely
[16:56] <achiang> or at least remind me and i can go do it
[17:39] <jjohansen> apw: is there a per flavour way of overriding the config enforcer
[17:56] <apw> jjohansen, not currently it would be possible to add pretty easily i suspect ... wahts your usecase ?
[17:57] <jjohansen> well one of the configs I need if I can get this stupid thing to work is CONFIG_SYSFS_DEPRECATED_V2
[17:58] <jjohansen> which currently is enforced off
[18:01] <apw> so for a branch you you can just edit the file and remove it
[18:01] <apw> if its coming back to master, we'll need to add support for flavours in the file
[18:02] <apw> jjohansen, i lied, seems i do have a flavour pred
[18:03] <apw> so you should be able to say
[18:04] <apw> (flavour ec2; value CONFIG_SYSFS_DEPRECATED_V2 y) | value CONFIG_SYSFS_DEPRECATED_V2 n
[18:04] <apw> or similar
[18:05] <jjohansen> okay, thanks
[18:22] <vosl> hi
[18:33]  * bjf is having email problems and has no x on laptop after this a.m. update... been trying to get to a setup where I can get something done all a.m.
[18:34] <jjohansen> ouch
[18:34]  * jjohansen has been avoiding updates since robbies email
[18:35] <bjf> but my btrfs is *FABULOUS* :-)
[18:36] <sconklin> robbie's email to which list?
[18:37] <vosl> hello
[18:40] <bjf> sconklin, i'd tell you which list but I can't get to my email
[18:40] <vosl> guys i just wanted some help on your kernel version numbering system
[18:40] <vosl> how does it usually wwork
[18:40] <vosl> i read the wiki but couldnt make sense of it
[18:41] <bjf> vosl, what is your question?
[18:41] <vosl> i assume for debian and ubuntu its the same kinda versioning
[18:41] <vosl> liunx kernel version number
[18:41] <vosl> how is the numbering done?
[18:43] <bjf> vosl, via 'uname -r' = 2.6.32-22-generic
[18:43] <bjf> vosl, we have made 22 abi bumps on a 2.6.32 kernel
[18:43] <vosl> are you talking in general or this is specific to ubuntu kernels?
[18:44] <bjf> vosl, this is a ubuntu lucid install
[18:45] <vosl> ok how does the numbering work?
[18:45] <vosl> 2.6.32-22
[18:46] <bjf> vosl, it is telling you that it is based on the 2.6.32 kernel from upstream (linus' tree)
[18:47] <vosl> ah
[18:47] <vosl> so this is the same case with vanilla too?
[18:47] <vosl> the versioning doesnt differ per distro does it?
[18:48] <dupondje> http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2208 / https://patchwork.kernel.org/patch/103568/
[18:48] <ubot2> bugzilla.intellinuxwireless.org bug 2208 in others "Driver hang while running auto test cases" [Critical,Verified: fixed]
[18:48] <dupondje> is this something we can get into maverick kernel bit earlier ?
[18:48] <bjf> vosl, i don't know how other distros report versioning but it's probably similar
[18:48] <vosl> ah
[18:48] <vosl> what does the -22 stand for?
[18:49] <bjf> vosl, as I said previously, there have been 22 abi bumps
[18:49] <vosl> ooh ok
[18:51] <vosl> bjf[afk]: which is better
[18:51] <vosl> .30 or a .30.1?
[18:51] <vosl> depends on which type of patches are allowed for each versions
[18:51] <vosl> right?
[18:51] <vosl> new features, regressions or bugfixes only
[18:59] <cking> manjo, you around?
[18:59] <manjo> cking, yes
[18:59] <cking> ok to mumble for 5 mins?
[19:00] <manjo> sure 
[19:00] <dupondje> When will maverick kernel be rebased on the upstream kernel ?
[19:01] <dupondje> the bug seems fixed in it today http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=63a07cb64ccc3ceae619d3298545d602ab5ecd38;hp=b95a56809343fb727c818ad1b9da14a17fa92ef6
[19:01] <ogasawara> dupondje: it's already been rebased to 2.6.35-rc2.
[19:02] <dupondje> will it get rebased to rc3 ?
[19:02] <dupondje> cause that bug is killing me :)
[19:02] <ogasawara> dupondje: yes, when it's released upstream we'll rebase again
[19:02] <ogasawara> dupondje: wash, rinse, repeat for the entire 2.6.35 cycle
[19:02] <dupondje> :)
[19:03] <dupondje> is there a chance to get the patch in kernel faster, or you say, wait for rebase ? :)
[19:03] <ogasawara> dupondje: seems we should just wait for the rebase as it'll be in -rc3
[19:04] <ogasawara> dupondje: and rc3 is just around the corner
[19:04] <dupondje> lets hope so. its crashing daily atm :( anyway its good to see its in the main git now, so it will be picked up for sure now
[19:05] <ogasawara> dupondje:  as an interim solution you could use the latest mainline daily build
[19:05] <ogasawara> dupondje: well you may need to wait till tomorrow for the build to include the patch that landed today
[19:05] <dupondje> i'll grab it tomorrow
[19:50] <tgardner> kees, what does dumpable mean wrt to ptrace?
[19:51] <kees> tgardner: it means core-dumpable.  as in, "has this process transitioned uid?"
[19:51] <kees> tgardner: you can't ptrace a process that started setuid, e.g.
[19:52] <kees> tgardner: but this flag can be set by a process itself using prctl.
[19:52] <kees> tgardner: this is what well-behaved processes that handle sensitive memory do (e.g. ssh-agent)
[19:52] <tgardner> kees, I was just reviewing your email that includes the 10-ptrace.conf verbage. It occurred to me that dumpable didn't mean anything to me.
[19:52] <kees> tgardner: see "man prctl" and search for PR_SET_DUMPABLE
[19:53] <kees> tgardner: I was trying to be as accurate as possible while hopefully not being too opaque.  :P
[20:21] <jjohansen> ->Lunch
[20:22] <MTecknology> jjohansen: enjoy
[20:22] <Laibsch> manjo: please be more careful when closing bugs
[20:22] <MaximLevitsky> what is the policy on EXPEREMENTAL in the ubuntu kernel?
[20:22] <manjo> Laibsch, which one ?
[20:23] <Laibsch> you should have received mail about it
[20:23] <Laibsch> please be careful with any bug you close
[20:23] <manjo> Laibsch, checking 
[20:23] <MaximLevitsky> I have 2 drivers in 2.6.35
[20:23] <Laibsch> you seem to be new at this
[20:23] <ripps> What's the likelyhood of an updated wacom driver getting into the kernel? I'm constantly rebuilding the module because the default one doesn't work with my wacom bamboo ctl-460
[20:23] <MaximLevitsky> one of which I labeled experemental
[20:24] <MaximLevitsky> now I say it is more or less well tested
[20:24] <manjo> Laibsch, bug# ?
[20:24] <dupondje> Is there a way I can build my own daily ? really need the patch that got in today :)
[20:24] <MaximLevitsky> it still contains a disclaimer about how it can eat your cat & dog though :-)
[20:25] <MaximLevitsky> I had no reports of this though :-)
[20:25] <ogasawara> mjg59: hi, we've been carrying an Ubuntu kernel SAUCE patch that was originally authored by yourself years ago.  I wanted to get your feedback on it and am curious if you prefer I use your redhat.com email address or a different one?
[20:25] <MTecknology> Transaction rate:        7.31 trans/sec
[20:25] <MTecknology> OUCH
[20:25] <MTecknology> sorry... wrong channel
[20:25] <mjg59> ogasawara: Which one is it?
[20:25] <MaximLevitsky> mjg59: hi
[20:26] <manjo> Laibsch, if you can't tell me what bug number it is I can't help 
[20:26] <Laibsch> manjo: bug 527361
[20:26] <ubot2> Launchpad bug 527361 in linux (Ubuntu) (and 1 other project) "hotplug interferes with ethernet card (affects: 1) (heat: 8)" [High,Triaged] https://launchpad.net/bugs/527361
[20:26] <Laibsch> manjo: is it too much to ask that you check your mail?
[20:26] <ogasawara> mjg59: the patch is "UBUNTU: SAUCE: hostap: send events on data interface as well as master interface" from back in 2007
[20:26] <Laibsch> geez
[20:26] <manjo> Laibsch, sorry did not see your mail yet not in my inbox yet
[20:26] <Laibsch> manjo: just don't close bugs if you don't understand what it means, OK?
[20:27] <MaximLevitsky> How can I ask ubuntu to enable it in marvic kernel?
[20:27] <mjg59> ogasawara: That was because network manager was only listening for association events on the data interface, and hsotap was only sending them on the master interface
[20:27] <mjg59> ogasawara: I have no idea whether that's still an issue
[20:27] <ogasawara> mjg59: I'm inclined to drop it and see who screams
[20:28] <manjo> Laibsch, I don't think that bug is SRU'able 
[20:28] <mjg59> ogasawara: Yeah, I'd go for it
[20:28] <Laibsch> manjo: please learn about LP before making any further embarassing comments
[20:28] <ogasawara> mjg59: perfect, thanks
[20:29] <dupondje> ogasawara: can I build my own daily ? Its crashing to much :(
[20:29] <MaximLevitsky> anybody ?
[20:29] <ogasawara> dupondje: sure, go for it
[20:30] <dupondje> ogasawara: is there some easy script or so for it ? or just pull from the git or ? :)
[20:31] <ogasawara> dupondje: I don't have a link for building the upstream kernel off the top of my head, but should be easily found via google
[20:31] <dupondje> the script you guys use for the dailies isn't availible ? :)
[20:31] <MaximLevitsky> mjg59: btw I am bisecting another ACPI bug
[20:31] <ogasawara> apw: ^^?
[20:32] <mjg59> MaximLevitsky: Excellent
[20:32] <MaximLevitsky> mjg59: I see that on boot the EC GPE is disabled
[20:32] <MaximLevitsky> mjg59: so no notify from battery, ac, ....
[20:33] <MaximLevitsky> mjg59: suspend/resume 'fixes' this. I use the acpi-test branch now. Going to reboot
[20:40] <manjo> tgardner, on the phone 
[20:40] <tgardner> manjo, ack
[20:45] <MaximLevitsky> Is it possible to enable a driver that depends on EXPREMENTAL in ubuntu kernel?
[20:46] <MaximLevitsky> my driver is CONFIG_SM_FTL (sm_ftl.ko)
[20:46] <tgardner> MaximLevitsky, its possible. which driver(s) are you considering?
[20:46] <MaximLevitsky> tgardner: ^^^
[20:46] <tgardner> lemme look
[20:46] <MaximLevitsky> this is FTL (flash translation layer)
[20:47] <MaximLevitsky> I admit that I overdue the Kconfig option for it 
[20:47] <tgardner> MaximLevitsky,  likely to have little impact on the general PC class of installs. Are you building for an embedded device?
[20:47] <MaximLevitsky> All reports I recieve untill now were positive (minus typical user errors)
[20:47] <MaximLevitsky> tgardner: this is for xD card reader
[20:48] <tgardner> ah, that thing.
[20:48] <MaximLevitsky> Ricoh R852 xD card reader
[20:49] <tgardner> MaximLevitsky, so, do you think it works better then what you've stated in the Kconfig description? 
[20:49] <MaximLevitsky> tgardner: I think yes
[20:50] <MaximLevitsky> tgardner: I didn't update it from first merge. In general especially modern xD cards (type M) should be prefectly safe because they use emulated interface
[20:51] <MaximLevitsky> In addition to that I need new udev rule
[20:51] <MaximLevitsky> to load the FTL
[20:52] <MaximLevitsky> and to tell devicekit to treat the device normally
[20:52] <tgardner> MaximLevitsky, I was just gonna ask what loads the driver
[20:53] <MaximLevitsky> converting whole mtd system to proper bus interface it too big job for me.
[20:54] <tgardner> MaximLevitsky, are you getting any traction with the udev developers? I'm not sure I can help you get a new udev rule.
[20:54] <MaximLevitsky> tgardner: I didn't yet posted anything to udev list
[20:54] <MaximLevitsky> tgardner: however I also need some modifications to devicekit rules
[20:54] <MaximLevitsky> the 'udisk' I forgot
[20:55] <tgardner> MaximLevitsky, send a patch to the kernel team list enabling the config option. I'm not opposed to it. You're on your own for components outside the kernel.
[20:55] <MaximLevitsky> because it treats all devices as system unless they are in white list
[20:56] <MaximLevitsky> tgardner: beeing lazy, whats the address :-)
[20:56] <tgardner> kernel-team@lists.ubuntu.com
[20:56] <MaximLevitsky> tgardner: thanks!
[21:03] <MaximLevitsky> tgardner: last question, the debian.master/config is the place I am looking for to change the config option ?
[21:05] <matumba> hello, i guess i should report bugs with ubuntu's mainline kernel to upstream rather than to launchpad?
[21:05] <MaximLevitsky> matumba: its is always better to report to upstream
[21:08] <matumba> MaximLevitsky, well then... thx ;-)
[21:08] <ripps> What's the likelyhood of an updated wacom driver getting into the kernel? I'm constantly rebuilding the module because the default one doesn't work with my wacom bamboo ctl-460
[21:09] <tgardner> MaximLevitsky, yeah, change it to CONFIG_SM_FTL=m in debian.master/config/config.common.ubuntu, then run 'fakeroot debian/rules updateconfigs'
[21:10] <manjo> tgardner, I am looking at SHAID bc9d24a3aeb1532fc3e234907a8b6d671f7ed68f
[21:10] <MaximLevitsky> tgardner: thanks!
[21:10] <manjo> which is the 2nd one mentioned 
[21:17] <tgardner> manjo, so I'm not sure where you came up with bc9d24a3aeb1532fc3e234907a8b6d671f7ed68f. Its not mentioned in either the BS or LP reports, is it? Though it does seem reasonable for a stable update.
[21:17] <tgardner> BS->BZ
[21:19] <manjo> tgardner, right I looked at the git logs for 2.6 upstream and I see eeepc-laptop: check wireless hotplug events with SHAID bc9d24a3aeb1532fc3e234907a8b6d671f7ed68f by Alan Jenkins <alan-jenkins@tuffmail.co.uk> Date:   Mon Feb 22 16:03:58 2010 +0000
[21:19] <manjo> tgardner, the bz report mentions this patch from a private tree 
[21:19] <manjo> the last comment in BZ
[21:19] <tgardner> ah
[21:20] <manjo> that is what I have been talking all along 
[21:20] <manjo> talking about
[21:20] <tgardner> manjo, ok, then see if you can get that one included for 2.6.32 stable
[21:34] <tgardner> manjo, you're gonna have to do a backport of that commit since it doesn't apply cleanly.
[21:34] <manjo> ah crap
[21:34] <manjo> tgardner, will do thanks
[21:42] <MaximLevitsky1> I have another probably newbie question
[21:42] <MaximLevitsky1> I downloaded the marvic kernel from git://kernel.ubuntu.com/ubuntu/ubuntu-maverick.git
[21:42] <MaximLevitsky1> I do 'fakeroot debian/rules updateconfigs
[21:42] <MaximLevitsky1> dh_testdir: cannot read debian/control: No such file or directory
[21:43] <tgardner> MaximLevitsky1, fakeroot debian/rules clean  updateconfigs
[21:43] <MaximLevitsky1> I can copy the file there, but I think I need to start some init script
[21:43] <tgardner> MaximLevitsky1, do the clean first
[21:43] <MaximLevitsky1> tgardner: works now
[21:44] <MaximLevitsky1> tgardner: maybe add that to wiki?
[21:44] <MaximLevitsky1> didn't find that at https://wiki.ubuntu.com/Kernel/Dev
[21:44] <tgardner> MaximLevitsky1, I think its there somewhere. we're in the process of rewriting a lot of that info
[21:44] <MaximLevitsky1> tgardner: ok, thanks
[21:47] <MaximLevitsky1> tgardner: should I now build the package or the 'updateconfigs' is enough?
[21:47] <MaximLevitsky1> I hate waiting 2 hours for that :-(
[21:47] <tgardner> the updateconfigs should be sufficient.
[21:48] <MaximLevitsky1> tgardner: thanks again
[23:04] <MTecknology> The only ban in here is a bot - does that still need to exist?
[23:08] <manjo> emerald not responding