=== salem_ is now known as _salem
=== timrc-afk is now known as timrc
slangasekpitti: did you still need an owncloud-client ignore?00:28
slangasekpitti: seems so - hint added now00:38
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying
=== echevemaster_afk is now known as echevemaster
lolcatHas it ever been considered to make aptitude use bitorrent?02:24
=== freeflying is now known as freeflying_away
tarpmanlolcat: https://wiki.debian.org/DebTorrent02:31
lolcattarpman: So it isn't feasible?02:44
lolcatI would love for it to use bittorrent on the local network in addittion to a web seed. SO if bandwidth is thight it gets it from local computers02:45
RAOFlolcat: In the meantime, running an apt-proxy is pretty simple.03:00
RAOFlolcat: See squid-deb-proxy-client + squid-deb-proxy/apt-cacher-ng etc.03:00
lolcatHard to install on freeBSD03:01
RAOFWhy would you install it on freeBSD?03:01
RAOF(And I'd be amazed if squid was hard to install on FreeBSD!)03:01
lolcatBecause I have three computers with ubuntu03:02
lolcatThey are not on at the same time always03:02
lolcatHow would I set it up so they know which has the package?03:02
lifelesslolcat: pkg_add squid; done - no ?03:02
RAOFThere's apt-zeroconf for that, if you don't have a machine that'd be mostly-on.03:03
lifelesslolcat: squid-deb-proxy uses zeroconf03:03
RAOFWelcome, squid-highlighting friends!03:03
lolcatI guess Ill just upgrade to 100mbps and forget about it03:04
RAOFOh, apt-zeroconf is dead-dead. That's a bit of a shame; the other caching solutions don't quite cover the distributed-cache usecase.03:05
=== baba is now known as fire_
RAOFlifeless: There's no trivial configuration to turns squid into a distributed cache solution, right? (ie: multiple squid caches on the network, dispatch to appropriate cache if cache has file, otherwise download locally and cache)03:07
RAOF(I've probably asked that before)03:10
lifelessRAOF: cache_peer and list all the peers03:11
lifelessRAOF: IIRC digests (bloom filter API) are on by default, so you'll get that behaviour03:11
lifelessshould be easy enough to wire a config generator into zeroconf and do that03:11
RAOFHm, yeah. Interesting.03:11
lifelessof course, trust is an issue, as you're basically saying 'hey, use me for transit!'03:12
RAOFWell, there's apt's signing mechanism on top.03:12
lifelessfor the special case of safe-over-http content, sure03:12
RAOFSo you shouldn't be able to silently break stuff.03:13
lifelessjust saying :)03:13
lifelessyou could silently withhold security updates03:13
RAOFDon't we https:// them yet?03:13
RAOFNo, we don't. Sadface (:03:13
lifelessand also they don't exist for the open release03:14
RAOFWe could always turn off proxying for Packages.gz03:14
RAOFActually, I suspect the default config works for that; setting all 0s for refresh_pattern on Packages should do that?03:17
lifelessthat affects heuristics03:18
lifelessexplicit timing data from servers takes precedence03:18
lifelessunless you actually explicitly override which IIRC requires a compile time option to enable RFC violations03:18
lifelessI'm not really worried about someone withholding updates03:19
RAOFThere's presumably a squid key to disable caching and always got to the server?03:19
lifelessit was just an observation03:19
RAOFWell, if I were to, say, update the default squid-deb-proxy configuration to handle this I'd want to make sure it's approximately as secure :)03:21
lifelessits not secure now03:21
lifelessin this sense03:21
lifelessbecause I can plug an unprivileged machine in and advertise03:21
lifelessso - no new hole03:21
lifelessthe difference is that you want to share the cache03:22
=== mwhudson is now known as zz_mwhudson
=== freeflying_away is now known as freeflying
pittiGood morning05:55
pittislangasek: yes, doko_ asked for it; thanks05:55
Noskcajpitti, The g-s-t merge should be ready for you to look at05:57
pittiNoskcaj: yes, thanks muchly! I have it in a tab to review this morning05:58
Noskcaj:) Then i can nag you about the other 50 packages i have that need sponsoring05:58
darkxsthey pitti06:00
=== zz_frobware is now known as frobware
pittihey darkxst, how are you?06:06
darkxstyeh good, finally it has cooled down here!06:07
Unit193mvo: Howdy.  Did you happen to see my comment before you left last night?06:08
darkxstpitti, would you be able to add an endorsment to my PPU/MOTU application? (Planning on attending the next meeting 27th)06:08
pittidarkxst: sure, will do06:09
=== frobware is now known as zz_frobware
pittiNoskcaj: hm, did you update debian/control manually? curious how the "XSBC-Original-Maintainer: Maintainer:  [...]" oddity came in here (will fix that during merge)06:14
NoskcajProbably. I think bzr had a conflict there that i must have done wrong. oops06:15
pittiNoskcaj: FYI, debclean will update debian/control from control.in06:15
NoskcajThis is why i hate packaging one thing over many days06:15
pitti(no worries)06:16
mvoUnit193: i didn't, sorry - could you please paste it to me again?06:20
Unit193I ended up commenting before you responded.  I saw several marked as dupes of that bug so just figured there was proper, then noticed I couldn't re-open.  Is there a chance you can do that?06:21
mvoUnit193: I think I can, could you please give me the bugnumber again?06:33
Unit193mvo: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/106054306:34
ubottuUbuntu bug 1060543 in software-properties (Ubuntu) "Additional Drivers is not discoverable in Quantal" [Critical,Fix released]06:34
NoskcajCould someone help me with refreshing a patch to argyll?06:41
Noskcajty for the syncs pitti06:41
pittiNoskcaj: yw06:41
NoskcajI need help re-adding a patch to https://code.launchpad.net/~noskcaj/ubuntu/trusty/argyll/merge06:43
Noskcajxnox, I think you made the  original06:43
Unit193mvo: Danke!06:53
mvoUnit193: your welcome .)06:54
mvoUnit193: I will try to look at your diff today, if nothing has happend by lunchtime please gently nudge me again (have to do some other stuff first)06:54
Unit193mvo: Heh, it's 01:55, I'm watching Castle then going to bed. :P  But sure, next time.06:55
mvoUnit193: wehh, these timezones .) yeah, lets talk tomorrow, have a good night06:56
=== zz_frobware is now known as frobware
dholbachgood morning07:30
=== oSoMoN_ is now known as oSoMoN
=== frobware is now known as zz_frobware
=== zz_frobware is now known as frobware
xnoxNoskcaj: be careful, in debian I think they dropped the db usage completely, which I don't think is correct.09:21
Noskcajxnox, ok. Is there any chance you could try and finish the merge, since it's beyond my understanding09:22
xnoxyeah, i will.09:23
=== doko_ is now known as doko
apwpitti, autopkgtests ... the one we did for linux ... this is a compile test basically which is great when gcc changes, but makes no sense to fire when the package in question is linux itself as we just did that.  is this something we can codify in the test?09:51
pittiapw: not really in linux itself, as that autopkgtest has no idea when/why it gets called09:52
apwpitti, so i don't get offered the name of the trigger'er or anything09:52
pittiapw: we could perhaps change eglibc's autopkgtest to try and build linux, not itself09:52
pittiapw: no, britney/jenkins are way higher up in the stack than autopkgtest, I'm afraid09:53
apwpitti, i thought that way lay madness or something, as every package had to list all possible packages09:53
pittiapw: i. e. instead of trying to build itself, packages could try and build the others in the "toolchain" set except themselves09:53
pittiand it doesn't parallelize that way09:53
pittiwhich is why we did it this way around and live with the overhead09:53
brendandponder - launchpadlib in python309:53
apwso it sounds like something fundamental to the /control level to say "but not for me"09:54
brendandrebuilt on requests09:54
pittiapw: we have enough build slaves, after all; the unnerving thing are the failures09:54
* apw has yet to see a kernel make it through testing i think09:54
pittiapw: we recently found a too small copy timeout for linux (on one node, copying the sources takes more than 5 mins, yay slow disks); so it ought to get better now09:54
pittiand fail less often09:54
pittiapw: how do you mean?09:54
pittiapw: they succeed often, but also used to timeout often09:55
apwpitti, all the ones i have followed through have failed on one arch out of the two i think09:55
apwbut that would be only on upload, not ones triggered say but eglibc or whatever09:55
pittiah, tar freaking out again with "File removed before we read it09:56
apwpitti, so you pointed me at a jenkins page which is like shoving hot needles in my brain, but making the foolish assumption that red == bad and green == good down the left there, my head says <half worked09:56
pittiapw: exactly09:56
apwok so by my cound 60% are failing09:57
jibelapw, timeout increased to 2000s. It may still fail depending on IO contention on the servers.09:57
=== Laney changed the topic of #ubuntu-devel to: Trusty Tahr Alpha 1 released! | Archive: alpha 2 freeze | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> saucy | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
pittiapw: ah, that's still the timeout apparently09:57
pittifrom copyupdown09:57
pittijibel: thanks09:57
pittijibel, apw: retried09:58
jibelpitti, yes, now set to 2000s we could as well drop it completely09:58
apwpitti, what is this copy, is it someting i need and can i ask for it not to be so copied in my test stanza09:59
pittiapw: no, unfortuantely not10:00
pittiapw: that's autopkgtest copying the source package/source tree into its temp dir in the runner10:00
pittiapw: and aldebaran's disk is just awfully slow10:00
pittiapw: most tests are run on tmpfs (this machine has 64 GB RAM or so), but it's not enough to build linux; so linux and libreoffice run on a disk overlay instead of RAM10:01
directhexpitti, exclusively on disk? or ram overflowing to disk?10:02
jibelpitti, this machine is quite good but if at the same time it runs smoke tests they eat all resources available10:03
pittidirecthex: exclusively on disk; can qemu-img do this kind of hybrid mode?10:03
directhexpitti, i think we hammered it into working for a project at work. trying to remember the details. it involved using nbd to create a ram block device (not using tmpfs) but i don't remember which service was used to overflow to an LV10:05
directhexmaybe bcache10:05
pittiapw: hey, perhaps you have an idea about that: since recently (few days, could be with the new -4 kernel), preparing our autopkgtest VMs fail due to ENOSPC10:11
pittiapw: the issue is that df says that /dev/vda1 (which is root) is 100% full, it's 5.9 GB10:11
directhexam asking the engineer who did it if he documented it anywhere10:11
pittiapw: but du -hcx / only reports some 800 MB being used10:11
pittiapw: I already checked /proc/*/fd/ and lsof for deleted files, there are none at all; and tune2fs says the journal is only 32 MB10:12
pittiapw: do you happen to know anything else which could eat up disk space which doesn't appear in df or in deleted files?10:12
lifelesspitti: out of inodes?10:13
pittilifeless: nope, checked that already10:13
pittiBlock count:              157260810:13
pittiFree blocks:              134068610:13
pittiFree inodes:              33210110:13
Laneyjodh: just got the reboot again10:13
pitti# du -hsx /10:14
lifelesspitti: so clearly has free blocks10:14
lifelesspitti: what about quotas?10:14
pitti/dev/vda1       5.9G  5.9G     0 100% /10:14
pittilifeless: they aren't set up10:14
lifelessoh, I see, df thinks its full10:14
pittibut even if they were, they shouldn't affect root and df?10:14
lifelessthe free blocks is what 80%10:14
pittilifeless: yes, and everything else fails on ENOSPC too10:14
pittilifeless: right10:14
pittiI'm running out of ideas what could be wrong10:15
lifelessI smell a bug :)10:15
pittineither cloud-init nor cloud-utils changed recently, nor the ext tools10:15
pittiI suspected hidden or deleted files, but I don't find any10:15
lifelesspitti: they would use up free blocks10:15
lifelesspitti: so it can't be that10:16
pittitrue that10:16
TJ-pitti: sparse allocation maybe?10:16
Laneyjodh: what logs do you want?10:16
LaneyI was doing an apt update in the host and inside an lxc container simultaneously10:16
jibelpitti, lifeless and after a reboot used space on /dev/vda1 is 15%10:16
pittiTJ-: perhaps; I'm not entirely sure how the cloud images' root fs are put together10:16
pittiqemu-img resize $DISKPATH +${DISKSIZE}10:17
pittijibel: ^ is that it?10:17
jibelpitti, yes10:17
pittilast qemu update was on Jan 3, the next upload is still stuck in -proposed, so not that either10:18
jibelthen cloud-init resizes it to the maximum size available10:18
jibelit = rootfs10:18
Laneyjodh: the last thing in my apt log is Setting up libselinux1:amd64 (2.2.2-1) ...10:20
Laneylibselinux1's postinst does telinit u10:20
jodhLaney: I think you'll find that you have an invalid conf file that is triggering the crash. alsa-utils is the most recent package that had invalid jobs, but that has now been fixed.10:22
Laneywould it be logged?10:22
Laneyanyway, that should certainly not cause the machine to reboot10:23
jodhLaney: yes, if you're running in debug mode (--debug).10:24
jodhLaney: of course :) I've now fixed the bug but am awaiting an upstart developer to review the fix: lp:~jamesodhunt/upstart/bug-1269731. Maybe xnox or cjwatson could take a look?10:24
TJ-pitti: doesn't make sense though; df uses the block allocation maps, so if it reports 100% the host is using sparse allocation and has run out of space10:25
cjwatsonjodh: looking shortly10:27
jodhcjwatson: thanks!10:27
lifelesspitti: jibel: is it possible that online resize is being used, and is broken ?10:27
jibelpitti, I reprovisioned a VM with a disk size of 12G and df is still reporting it is full on first boot. /dev/vda1        12G   12G     0 100% /10:27
lifelessanything in dmsg10:27
pittiTJ-: I just wanted to check this, and I made an interesting observation10:27
pitti$ sudo du -hsxc /tmp10:28
pittitmpfs                  7,8G    5,7G  2,1G   74% /tmp10:28
pittithat's on my workstation (not in qemu)10:28
pitti$ sudo du -hsxc /run10:28
pittitmpfs                  1,6G    1,2M  1,6G    1% /run10:29
pittierr, no, run-adt-test is using /run/shm, right?10:29
pittianyway, I have 4K files in /tmp/, but df says 5.7 GB are used in /tmp10:29
cjwatsonjodh: r=me, sorry for the delay10:29
pittiso it might very well be that qemu has no space because on my host /dev/shm/ is full10:29
pittialthough it isn't, /run/shm/ has 7.3 GB free10:30
pittijust /tmp/ is really wrong10:30
Laneyjodh: oh cool, thanks10:30
pittijibel: ^ does prepare-testbed use /tmp? that might explain why it's full during prepare-testbed, but works after a reboot when it uses /run/shm10:30
pittijibel: well, I'll try booting with 3.13.0-3 and compare10:31
Laneystgraber: got any ideas how we can make the ssh-agent script less racy?10:31
jodhcjwatson: thanks!10:32
jibelpitti, it uses what you set as BASEDIR in ~/.adtrc and defaults to /tmp10:32
TJ-pitti: Isn't it pressure on RAM? tmpfs is backed by swap space10:33
pittiTJ-: well, I still don't know why it would run out of RAM; but the lost 5.7 GB in my /tmp/ are certainly curious10:34
pitti(/tmp is on tmpfs)10:34
smbpitti, jibel Note that the 3.13.0-3 kernel very likely has an accounting bug for tmpfs10:35
pittismb: I didn't have the cloud-init problem on -3; it just started maybe two days ago10:35
smb3.13.0-4 (currently in proposed is believed to fix this)10:35
=== _salem is now known as salem_
pitticould coincide with -410:36
pittismb: you mean -3 → -4 and -4 → -5 ?10:36
pittismb: I'm currently downloading -5 from -proposed and will test that10:36
smbpitti, Err yeah I probably do10:36
smbpitti, Versions changing so quickly, sorry.10:37
cjwatsonwhat's up with the linux autopkgtest?10:37
pittithat at least would also explain why we don't get that problem in the DC where we have precise or saucy as a host OS10:37
pitticjwatson: it keeps timing out on copying the sources into its tmp dir; jibel just bumped the timeout again10:38
cjwatsonah, /me reads scrollback.  so is somebody retrying the test?10:38
cjwatsonwe need to get this in for the alpha10:39
pitticjwatson: already did10:39
cjwatsonok, good10:39
cjwatsonsorting d-i now10:39
pittijibel: ok, so with -5 on the host I still get the bug in the VM; we might need to get -5 into the cloud image10:41
pittiat least df now looks sensible in my hosts' /tmp/10:41
pittismb: ^10:41
darkxstcjohnston, hey, I am applying for upload rights on ubuntu GNOME packageset but there isnt one!10:42
cjwatsonpitti: good, hopefully it'll fix d-i too10:42
darkxstcjwatson, ^^10:42
cjwatsondarkxst: I'm no longer on the TB so I don't operate packagesets any more10:42
cjwatsondarkxst: though you probably actually want to ask the DMB10:42
darkxstcjwatson, Laney told me to ask you10:43
cjwatsondarkxst: Laney is wrong :)10:43
LaneyCan we drive those scripts?10:43
smbpitti, Probably needs to move to updates. But then I should read more scrollback on what exactly your tmpfs problem is after changing the latest kernel10:43
cjwatsonI *think* it needs the TB, but you can try10:43
cjwatsonlp:~cjwatson/+junk/packageset - there's a component you need to run on lillypilly10:43
pittismb: right, let's wait until this is in trusty and we have a cloud-image with -510:44
Laney== All uploaders for package set 'ubuntugnome' in 'trusty' (owned by 'Ubuntu Technical Board') ==10:44
cjwatson(or I suppose just anywhere with a full mirror)10:44
LaneyDMB cannot manage that10:44
pittismb: it's all very confusing ATM, and tests on various host and guest configurations give contradicting results10:44
smbpitti, With the tmpfs bug, anything that actually makes use of it has a chance to fail. So it could be something ending up in tmpfs on the host but also and probably more often when using anything inside the guest10:45
darkxstLaney, cjwatson, so I am applying for a non-existent packageset ? atlest MOTU will be useful ;)10:45
Laneystgraber is in the intersection10:45
apwif it is the percpu fix we are talking about you would need that everywhere, as /dev is one10:46
Laneyhe might be interested in learning how to run this process10:46
cjwatsonLaney: I was planning to hand it over at the core sprint next week10:46
pittiapw: originally it was the "/dev/vda1 is 100% full although it isn't" issue in qemu, then I noticed the "df gives bogus tmpfs usage" on my host; they might or might not be releated10:47
pittiapw: so I guess we'll let -5 propoagate and get a cloud image with it, then I'll try again; let's hope it's all good then10:47
Laneycjwatson: nod10:47
cjwatsonLaney: when people can throw tomatoes at me for it in person10:47
cjwatson(it's really dreadful code)10:47
apwpitti, indeed, but i would test with everything updated rather than hurt your mind with the infinite possibilities10:47
pittiapw: right; apparently -5 on the host and -4 in the qemu guest doesn't fix it yet10:48
smbpitti, Quite expectedly10:48
pittiapw: conversely, with a raring kernel on the host and -4 as a qemu guest it seems to work10:48
pittiapw: but curiously this is on a qemu-img backed on ext4, not tmpfs10:48
pittioh well *shrug* kernel mystics .. /me goes and investigates the equally mysterious bug 122068110:49
ubottubug 1220681 in espeak (Ubuntu) "package espeak-data 1.46.02-2ubuntu1 failed to install/upgrade: unable to move aside `./usr/lib/i386-linux-gnu/espeak-data/voices/en' to install new version: Invalid cross-device link" [Undecided,Confirmed] https://launchpad.net/bugs/122068110:49
apwthe issue is in per cpu counters, its not tmpfs related just that is very sensitive to it10:49
apwgiven the bug, i am amazed the kernel boots with it at all under any circumstances10:50
pittiapw: ah, so it could break just about anything10:50
cjwatsonapw: I guess it effectively means it never clears any references to anything10:50
cjwatsonprobably uses a shitload of memory10:50
apwand pretty much everything, i had all sorts of random things going on on -4, -5 seems better to me10:50
pittithat now also explains why my apt-get was so glacially slow yesterday10:50
apwleaking like hell at least i recon10:50
=== timrc is now known as timrc-afk
pittiapw: hm, something isn't quite  right -- why does the autopkgtest build it *twice*?11:14
pittiapw: nevermind, I mislooked; all good (i386 succeeded)11:17
=== timrc-afk is now known as timrc
pittistgraber: is it possible to set a different default container dir (than /var/lib/lxc) in /etc/lxc/default.conf or ~/.lxc<something>? man lxc.conf doesn't mention it, nor does it mention what the actual config files are11:31
pittistgraber: so that I don't need to use -P all the time11:32
pittiapw, cjwatson: linux autopkgtest succeeded now, BTW11:41
pitti"Not touching package due to block request by freeze "11:42
pittibut excuses still says "autopkgtest for linux 3.13.0-5.20: FAIL"; I hope it's just out of date11:42
apwpitti, i don't think it ever notices when you rerun a test does it ?11:45
pittiapw: actually I think jibel fixed that a while ago11:45
apwit just need ignoring the test i think there11:45
pittiapw: if it didn't update after the next run, I'll fix the history file11:46
pittiapw: ah, it just did11:46
pittiapw: all good now, it's just the release team blocker that holds it back now11:46
pitti(a2 freeze)11:46
apwand possibly d-i11:47
apwoh no that is there too ... ok11:47
cjwatsonI uploaded d-i11:47
pittinot blocked by itself, it' sjust waiting on linux11:47
=== MacSlow is now known as MacSlow|lunch
=== tkamppeter_ is now known as tkamppeter
xnoxjibel: (i think we discussed this ~1.5 weeks ago) have you tried running tests under utah with this change applied to the base image: sudo sh -c "echo exec su - -c adbd > $OUT/mnt/etc/init/android-tools-adbd.override"12:24
xnoxsudo sh -c "echo exec su - -c adbd > /etc/init/android-tools-adbd.override"12:25
xnoxthat actually?12:25
jibelxnox, it was not with me, sorry.12:32
xnoxok. i'll search my logs then...12:36
=== PeterS_ is now known as PeterSchwaller
shadeslayeris there a reason why I would not have com.upstart.Ubuntu?13:13
shadeslayerover dbus that is13:14
Laneyshadeslayer: firstly it's com.ubuntu.Upstart13:15
Laneyassuming you just typoed, then I don't know :-)13:16
shadeslayerqdbus com.ubuntu.Upstart gives me Service 'com.ubuntu.Upstart' does not exist.13:16
shadeslayerLaney: I don't suppose there's a way to actually start that interface by hand?13:18
shadeslayerLaney: also, i'm on Kubuntu if that makes a difference13:19
=== Sweetsha1k is now known as Sweetshark
Laneyshadeslayer: sorry, I don't know - I was under the impression that it should always be there13:21
Laneymaybe #upstart can help you13:21
shadeslayeraha, I'll ask13:21
=== MacSlow|lunch is now known as MacSlow
=== arun_ is now known as arunpyasi
smosercjwatson,  i'm thinking about  memtest86+ as part of ubuntu standard.  how would you recommend re-ordering things so that I can get that out of cloud images?13:52
cjwatsonsmoser: will follow up to the dormant mail thread, this IRC channel is too narrow13:58
smoserok thank you.13:58
pitticjwatson: FYI, ubiquity autopkgtest failed on i386 FTBFS of webkit-gtk (causing uninstallability)14:00
dokopitti: I usually use severity serious for broken autopkg tests by design. it's nice if people add them, but things like this should never happen in the first place14:06
dokopitti, please overwrite this test. blocks a package removal14:06
dokopitti, libocsync-plugin-owncloud, waits for owncloud-client to go to trusty14:07
pittidoko: err, yes, I know -- that looks like a replay?14:07
pittidoko: slangasek added the override, it's in trusty14:07
dokopitti, oh, is it overwritten?14:07
xnoxdoko: any ~ubuntu-release can commit adt overrides in britney hints.14:08
pitti libocsync-plugin-owncloud | 0.90.4-1        | trusty/universe | amd64, arm64, armhf, i386, powerpc, ppc64el14:08
dokostill see14:08
doko   python-ownclouduniverseamd64 i386 arm64 armhf powerpc ppc64el14:08
pittidoko: ^ is that the version you are looking for? (nothign in -proposed)14:08
cjwatsonpitti: is that something we (ubiquity developers) need to do anything about?  I'd expect it to be retried once webkitgtk is fixed14:09
pittiI don't see any "croc" in component-mismatches, NBS, or britney14:09
pitticjwatson: no, it was just a FYI (as you probably got the mail)14:09
pittiah no, xnox got it14:10
cjwatsonthat explains my confusion :)14:10
pitticjwatson: sorry, in my mind "ubiquity" is still "Colin"14:10
pittiso for once an autopkgtest failure today was not due to the test machinery *sigh*14:11
xnoxpitti: i'm not on top of my post-vacation unread mail threads yet, especially those from robots =)14:11
pittixnox: no worries, and welcome back :)14:11
xnoxpitti: re:autopilot. last time i was talking with thomi & barry, we were thinking to add a "python2" flag to all existing clicks (cause their tests run from $PWD), and for deb tests simply try module import with python3 to see if it should be run with python3.14:19
xnoxpitti: once all tests are converted to python3. A python2 flag can be dropped from clicks (one by one) and for deb tests try python3 import will no longer be needed.14:20
pittixnox: right; I just don't quite like the metapackage pulling in both the py2 and py3 stacks, as that's quite some overhead for the phone14:20
xnoxpitti: thus we should arrive at not having any "X-Run-Me-Python3" in the long term, once all is converted. Without an explicit flag day.14:20
pittiso we need to do that transition for trusty now14:20
xnoxpitti: which should be all done and dusted next week, at the core sprint when barry will be there + the rest of CI etc peoples =)14:21
xnoxpitti: barry did submit a few merge proposals, but not all of them are merged yet.14:21
pittixnox: right, I added it to the agenda of our QA sprint as well (mid-Feb)14:22
pittixnox: I have patches for dialer-app and messaging-app here, but when I did them they were blocked on splitting out emulators for python3 for some packages14:23
pittiwhich in turn was blocked by some discussion how to package/name them14:23
xnoxpitti: i think the next piece that is missing, is for phablet-test-run / utah-runners to do the "try python3" tests. And there is a rejected merge proposal that I saw in my emails.14:23
pittidoko: in our precise → trusty upgrade tests, several packages failed due to a missing python:any; what particularly provides that :any magic, new dpkg?14:24
xnoxpitti: once we have ability to run tests under python3 in jenkins it should be all easy and quick to transition things one by one.14:24
dokopitti, yes14:24
pittidoko: or new python metapackages? it seems python:any deps now get autogenerated, but there is no Pre-Depends: or somethign like that on dpkg/python-defaults/etc.14:24
dokoit's dpkg14:24
pittixnox: still needs things like bug 1253627 fixed first14:25
ubottubug 1253627 in ubuntu-ui-toolkit (Ubuntu) "Needs to provide emulators for Python3" [Undecided,New] https://launchpad.net/bugs/125362714:25
pittidoko: ah, so perhaps dh_python[23] need to generate pre-depends for that?14:25
pittidoko: well, this is rather complex, I'll create a bug report and a small reproducer first14:26
dokopitti, won't help, I don't that any python-* module has misc:pre-depends14:26
pittiyeah, we'd need to either add them, or don't use misc:pre-depends14:26
pittibbiab, will investigate this in detail later14:27
pittidoko: thanks, will try with old and new dpkg then14:27
stgraberpitti: lxc.lxcpath = in /etc/lxc/lxc.conf or ~/.config/lxc/lxc.conf14:41
stgraberpitti: those are currently undocumented because lxc.conf refers to the container's configuration, not the system config... I have a todo item for this week to create lxc.system.conf and lxc.container.conf manpages and have the lxc.conf one just explain what the two files are for and what their respective manpage is14:42
mdeslaurchiluk: unfortunately, I once again superseded your mysql packages in -proposed. Sorry.14:51
pittistgraber: works perfectly, merci !15:02
=== barry` is now known as barry_
=== barry_ is now known as barry
mdeslaurbarry: quick question: would this be the right way to run 'python setup.py configure' in a rules file? http://paste.ubuntu.com/6792046/15:03
mdeslauror is there something better?15:04
mdeslaur(with dh_python2)15:04
xnoxmdeslaur: there is "pybuild" which will run stock: configure, build, test, install for all python2 / 3 versions et.al.15:04
barrymdeslaur: interesting.  configure isn't a standard command, so i'm guessing the setup.py has added this.  in that case, dh_python2 probably won't help15:04
xnoxmdeslaur: dh_python2, is a pure packaging helper that does correct extension renaming at the end.15:05
xnoxmdeslaur: and you are playing with highly non-standard libvirt build machinery, so i'm not sure there is anything better for you than what you wrote.15:05
xnox(dh_python2 doesn't build/configure/install anything)15:05
xnox * mostly true.15:06
mdeslaurxnox, barry: ok, thanks, so I'll stick with what I used15:06
=== salem_ is now known as _salem
=== rcj` is now known as rcj
araany member of the sru team could have a look to these two verified bugs, please?16:46
ubottuUbuntu bug 404658 in OEM Priority Project precise "notification summary doesn't change for synchronous messages" [Critical,In progress]16:46
ubottuUbuntu bug 1253591 in OEM Priority Project "Display switch and Radio enable/disable hotkey icons" [High,In progress]16:46
caribouinfinity: did you notice the email I sent a while ago about the merging of makedumpfile ,16:50
caribouinfinity: if it's ok with you, I'll merge it & do my best to get the debian side I package in sync16:51
pittijibel: FYI, I filed bug 1271237 to track investigations16:58
ubottubug 1271237 in python-defaults (Ubuntu) "precise → trusty upgrade; several packages fail due to python:any dependency" [Undecided,New] https://launchpad.net/bugs/127123716:58
cjwatsonpitti: followed up with what might be a useful link17:00
pitticjwatson: right, it very much sounds like that17:00
pittipython:any isn't satisfied yet, but apt doesn't upgrade python to satisfy it17:01
pitticjwatson: many thanks for the link17:01
cjwatsonseb128: could you check that the newer grub in trusty-proposed fixes your timeout problem?17:02
pitticjwatson: I'll backport that and test an upgrade with that; the next question is of course whether apt gets upgraded before that17:02
cjwatsonpitti: similarly, could you check that grub in trusty-proposed still works with SB for you?  another commenter spotted a bug that would affect from-scratch installs on SB17:02
cjwatsonpitti: right, but that's more tractable, u-m could force that17:02
cjwatson(if it doesn't already)17:02
cjwatsonI guess I mean u-r-u17:02
pitticjwatson: yes, I'm happy to update grub again, but it'd be an upgrade, not from scratch17:03
cjwatsonright, just want to check that I didn't break anything else in the process17:03
pitticjwatson: unless I can emulate a new installation by purging and reinstalling grub? (I can do that)17:03
seb128cjwatson, sure17:03
cjwatsonno, you'd have to do manual stuff to your EFI System Partition - an upgrade is fine for this purpose17:03
cjwatsonyou could maybe run "sudo grub-install -v" after the upgrade to check that it copies shim to the right place17:04
pitticjwatson: ah, that's -4 now -- that should also get rid of the menu again, right?17:04
cjwatsoni.e. /boot/efi/EFI/ubuntu/shimx64.efi not /boot/efi/EFI/ubuntu/grubx64.efi17:04
cjwatsonpitti: yep17:04
pittiargh, laggy german mirror17:11
pitti *** 2.02~beta2-2 017:11
pitti        500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages17:11
pitticjwatson: downloaded debs from LP, installed; no failure; with -v: http://paste.ubuntu.com/6792642/17:15
pittigrub-install: Info: copying `/usr/lib/shim/shim.efi.signed' -> `/boot/efi/EFI/ubuntu/shimx64.efi'.17:15
pittigrub-install: Info: copying `/usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed' -> `/boot/efi/EFI/ubuntu/grubx64.efi'.17:15
alkisgHi, I'm seeing 100% usage of overlayfs (squashfs nbd + tmpfs) file systems, while it should be 0%, it happened in some of the latest trusty kernels, and I'm guessing it should also affect the live CDs (other than LTSP), is it a known issue or should I try to pinpoint it more precisely?17:16
cjwatsonpitti: great, thanks17:19
cjwatsonalkisg: 3.13.0-5 will fix it17:19
pitticjwatson: I'll reboot once my container upgrades are done17:19
alkisgThank you cjwatson17:19
pitticjwatson: booted fine, menu gone \o/17:22
cjwatsonit's not totally without reported glitches but I think it's close enough that I'm inclined to push it to trusty after alpha-217:23
cjwatsonso far17:23
jibelpitti, postgresql upgrade fails from P>T, I'll file a bug. http://d-jenkins.ubuntu-ci:8080/view/Upgrade/job/upgrade-ubuntu-precise-trusty-server-tasks-amd64/5/17:24
pittijibel: thanks17:24
Laneyare those tests on public jenkins?17:25
pittithere certainly ought to be; it's a bit hard to link to logs ATM17:26
=== Ursinha is now known as Ursinha-afk
jibelLaney, they should be, I'll check the configuration.17:26
pittiupdate-alternatives: error: alternative pg_basebackup.1.gz can't be slave of psql.1.gz: it is a slave of postmaster.1.gz17:27
LaneyI usually try s/<private host>/jenkins.qa.u.c/ but it failed in this case17:27
Laneythanks jibel17:27
pittijibel: ^ ah, that, rings a bell17:27
jibelpitti, and a false positive http://d-jenkins.ubuntu-ci:8080/view/Upgrade/job/upgrade-ubuntu-precise-trusty-server-lts-saucy-amd64/617:27
pittijibel: I thought that was fixed already, but apparently it needs some further nudging17:27
jibel^ fails during the removal phase17:27
pittijibel: I don't see a psql bug there?17:27
pittijibel: oh nice, that's precise with an LTS enablement stack; I guess these fall over pretty hard still17:28
jibelpitti, last bug is not postgresql, it is in xserver-common-lts-saucy and u-r-u17:28
pittijibel: right, I discussed that with mlankhorst the other day; we need these -lts-* metapackags as transitionals in trusty, which move back to the standard stack17:29
jibelbecause upgrade aborted but the release-upgrader terminates without error17:29
mlankhorstpitti: oh right I need to create some17:30
pittigood night everyone!17:30
cffI'm trying to dual boot CM Android 4.2.2 on a Galaxy Nexus with Ubuntu but after I downloaded the Ubuntu image with the Android app and click reboot to Ubuntu I'm rebooted to recovery mode. What can I do to see what's wrong?17:31
cff(is this the right channel to ask this question?)17:31
cffah, didn't realize there is an #ubuntu-touch channel17:32
=== rbasak_ is now known as rbasak
=== Ursinha-afk is now known as Ursinha
chilukmdeslaur can you have a look at 112187417:54
chilukmdeslaur it looks like your recent security update for mysql-5.5 updated the package17:54
chilukmdeslaur, and maintained the fix for 1121874, but removed it's changelog entry..17:54
chilukmdeslaur... I really think you should add the changelog entry back *(not sure if that's really doable.)17:55
chilukI'm verifying s, and t right now.17:55
mdeslaurchiluk: what release are you talking about?17:55
=== _salem is now known as salem_
mdeslaurtrusty has the fix, and includes the changelog17:56
chilukI just looked at p and q... and they have the fix... but not the changelog entry.17:57
mdeslaurchiluk: not sure what you're looking at, but my packages definitely don't contain the fix17:57
chilukthe fix is in debian/mysql*.init17:58
chilukmdeslaur also why did you just blindly remove the fix like that17:59
mdeslaurchiluk: huh? https://launchpadlibrarian.net/159968670/lp1121874.saucy.debdiff17:59
mdeslaurchiluk: no fix in .init there17:59
chilukmdeslaur.. one sec... I think I missed the series arg to pull-lp-sourcfe17:59
mdeslaurchiluk: your package was in -proposed, I can't include a fix that hasen't been qa verified17:59
chilukmdeslaur, I guess I'm just pissed because this is the third time that I'm having to rebase debdiffs because of security team.18:00
chilukand the sru team taking too long to upload/sru approve this fix.18:01
chilukthis is insane.18:01
mdeslaurchiluk: yeah, the -proposed process sucks18:01
infinity(The SRU team doesn't do uploads)18:01
mdeslaurchiluk: I'll rebase and upload them today18:01
mdeslaurchiluk: and I'll get someone from SRU team to push them to -proposed right away18:01
chiluki was going to verify them today.18:02
chilukso I guess I'll get that done as soon as this gets figured out..18:02
mdeslaurchiluk: again, sorry about that...bad timing18:02
chilukmdeslaur, it's always bad timing... this bug has been fixed since October, and it's wasted too much of a lot of peoples time.18:03
mdeslaurI definitely agree18:03
mdeslaurchiluk: mind if I keep your name in the changelog, and just change the version and date?18:06
chilukthat's fine.18:06
chilukmdeslaur.. I just checked precise.. and the fix is definitely in the precise version just not in the changelog18:06
infinitycaribou: I don't see much point in merging makedumpfile in Ubuntu at all.  Looking at the changes, those are all things you should want in Debian, so I'd merge in the other direction, if I were you, and then just sync-with-force back to Ubuntu.18:07
mdeslaurchiluk: I don't see it18:07
rbasakchiluk: if it's any consolation, I have also found it hard to get any SRUs into mysql in the past. I think I went round three times once.18:08
chilukmdeslaur the fix is mostly thesse lines   # check for diskspace shortage18:08
chiluk  datadir=`mysqld_get_param datadir`18:08
chiluk  if LC_ALL=C BLOCKSIZE= df --portability $datadir/. | tail -n 1 | awk '{ exit ($4>4096) }'; then18:08
chiluk    log_failure_msg "$0: ERROR: The partition with $datadir is too full!"18:08
chiluk    echo                "ERROR: The partition with $datadir is too full!" | $ERR_LOGGER18:08
chiluk    exit 118:08
chiluk  fi18:08
mdeslaurchiluk: yeah, I don't see that in the precise package18:09
chilukone of us is doing something wrong *(probably me)18:09
chilukmdeslaur .. I run pull-lp-source mysql-5.5 precise, and look at debian/mysql-server-5.5.mysql.init18:13
chilukand the fix is definitely sitting there.18:13
chilukmdeslaur is there a chance the fix got pushed back into debian, as is now coming full circle?18:14
mdeslaurchiluk: you're looking at the .init file, you need to look at the .upstart file18:16
mdeslaurchiluk: that's where the bug is18:16
chiluksee it's been so long ..18:16
mdeslaurhehe :)18:16
chilukmdeslaur..see I knew i was doing something wrong..18:17
=== j_f-f_ is now known as j_f-f
chilukmdeslaur... the debdiffs should still mostly just apply ... aside from the changelog entries.. do you need anything from me to get that uploaded?  or are you just going to take care of it.18:18
mdeslaurchiluk: I'm almost done uploading, and then I'll ping someone from SRU to get it pushed to -proposed right away18:20
chilukcool thanks.18:20
mdeslaurchiluk: np18:20
chilukwell at least it looks like the debian people have been paying attention and pulled my fix into the init script.18:20
chilukand I use the term "fix" loosely ... I just want to see this thing gone.18:21
mdeslaurbdmurray: I just uploaded updated mysql packages to -proposed for bug 1121874, do you think you could push them today, please?18:30
ubottubug 1121874 in mysql-5.5 (Ubuntu Saucy) "MySQL launch fails silently if < 4MB of disk space is available" [Medium,Fix committed] https://launchpad.net/bugs/112187418:30
bdmurraymdeslaur: sure18:31
mdeslaurbdmurray: thanks!18:32
xnoxtkamppeter: recently I was able to use llvmpipe / gallium 3d on an openstack instance. But with current trusty I can't.18:36
xnoxI get:18:36
xnox$ LIBGL_DEBUG=verbose xvfb-run glxinfo18:36
xnoxname of display: :9918:36
xnoxlibGL: OpenDriver: trying /usr/lib/i386-linux-gnu/dri/tls/swrast_dri.so18:36
xnoxlibGL: OpenDriver: trying /usr/lib/i386-linux-gnu/dri/swrast_dri.so18:36
xnoxlibGL: driver does not expose __driDriverGetExtensions_swrast(): /usr/lib/i386-linux-gnu/dri/swrast_dri.so: undefined symbol: __driDriverGetExtensions_swrast18:36
xnoxlibGL: Can't open configuration file /home/ubuntu/.drirc: No such file or directory.18:36
xnoxlibGL: Can't open configuration file /home/ubuntu/.drirc: No such file or directory.18:36
xnoxlibGL error: failed to load driver: swrast18:36
xnoxError: couldn't find RGB GLX visual or fbconfig18:36
xnoxError: couldn't find RGB GLX visual or fbconfig18:36
xnoxtkamppeter: is that known?18:37
seb128xnox, hum, why do you ping our printer maintainer about graphic stack issues? are you sure you don't want mlankhorst or tjaalton?18:38
xnoxseb128: good catch!18:38
xnoxtkamppeter: sorry about that.18:38
xnoxmlankhorst: tjaalton: any idea about above ^^^18:39
seb128xnox, btw I get the same output on my desktop (but followed by the glxinfo one)18:40
xnoxand there haven't been any changes to mesa recently...18:40
xnoxseb128: does it tell you "Vendor" ?18:41
seb128xnox, no18:41
xnoxseb128: in my case, i don't GPU acceleration, so the swrast better load....18:41
seb128xnox, that undef symbol looks wrong in any case18:42
xnoxseb128: well on my desktop i get:18:42
xnoxOpenGL vendor string: Intel Open Source Technology Center18:42
xnoxOpenGL renderer string: Mesa DRI Intel(R) Ivybridge Desktop x86/MMX/SSE218:42
xnox(among the rest of the stuff glxinfo prints)18:42
seb128$ ldd -r /usr/lib/i386-linux-gnu/dri/swrast_dri.so18:42
xnoxseb128: and on headless systems I used to get "Gallium 3D vendor" now I get nothing.18:42
seb128undefined symbol: _glapi_tls_Dispatch(/usr/lib/i386-linux-gnu/dri/swrast_dri.so)18:42
seb128xnox, seems like the software rendering backend is having issues18:43
xnoxseb128: here is full, working pastebin from my computer http://paste.ubuntu.com/6793108/18:44
seb128xnox, right, that has hardware support18:44
seb128though "LIBGL_ALWAYS_SOFTWARE=1 glxinfo" works on my desktop18:46
xnoxseb128: mlankhorst: tjaalton: actually nevermind me it does work after all.18:48
keesdoko: why was debian bug 27363 re-opened? I added --with autoreconf and a dep on dh-autoreconf. what is missing?18:49
ubottuError: Debian bug 27363 could not be found18:49
keessorry, debian bug 72736318:50
ubottuDebian bug 727363 in src:duo-unix "duo-unix: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4" [Normal,Open] http://bugs.debian.org/72736318:50
cjwatsonthat looks like a mistake - it builds just fine on ppc64el18:52
keesokay, cool18:53
cjwatsonI think doko was mass-operating on all those bugs and hadn't noticed that that one had already been fixed in the more comprehensive way18:53
keesyeah, that's what I suspected, but I wanted to double-check. thanks!18:54
=== lifeless1 is now known as lifeless
=== zz_mwhudson is now known as mwhudson
NoskcajCould someone help me fix an FTBFS in xchat-gnome? just get https://code.launchpad.net/~noskcaj/ubuntu/trusty/xchat-gnome/merge and build it20:00
Noskcajdoko, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727373 can be closed, ppc64el builds fine20:01
ubottuDebian bug 727373 in src:enblend-enfuse "enblend-enfuse: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4" [Normal,Open]20:01
Noskcajand i'm doing the merge now20:01
AmpelbeinNoskcaj: What failure do you get?20:06
Ampelbein(with xchat-gnome)20:06
NoskcajAmpelbein, just let me re-branch it. It's been a few days since i worked on it20:07
hallyninfinity: mdeslaur is asking about qemu in trusty's ftbfs on powerpc.  have you had any luck there?  or should we just dump the aarch64 patchset?20:12
infinityhallyn: I was sick all weekend and yesterday, haven't had a chance to look at all.20:14
hallyninfinity: ok;  i'm out today;  maybe i can use a qemu-ppc to try the build tomorrow :)20:15
hallynmdeslaur: so if you need the debdiff reverted to have it build please do so;  i'll then push when we figure out what went wrong20:16
infinityhallyn: I shouldn't think you'd need a PPC machine to build on.  I imagine if you build that ppc64-softmmu target on *any* arch, it will fail the same.20:16
infinityTHough maybe not.  Hrm.20:17
infinityNo, okay, that gets built on x86 and works.  That makes this so much more confusing.20:18
hallyninfinity: all right well maybe it'll be obvious to me once i take a closer look tomorrow.  thanks, get better!  /me out20:19
NoskcajAmpelbein, http://paste.ubuntu.com/6793607/20:22
AmpelbeinNoskcaj: gnome-doc-utils.make is missing, are you running autogen.sh ? That should call gnome-doc-prepare and create it.20:27
AmpelbeinNoskcaj: Just checked out the branch (unrelated: What switch can I use to tell bzr that I only want to checkout the files at current state, not the entire history?).20:29
AmpelbeinNoskcaj: I'd do it like in debian, with DEB_CONFIGURE_SCRIPT := ./autogen.sh20:30
NoskcajI'll test that now20:31
tarpmanAmpelbein: are you looking for 'bzr checkout --lightweight'?20:32
NoskcajAmpelbein, The error still appears20:35
Ampelbeintarpman: Well, basically the equivalent of git clone --depth=!20:35
=== salem_ is now known as _salem
AmpelbeinNoskcaj: mc20:38
Ampelbeinclumsy fingers.20:39
AmpelbeinNoskcaj: http://paste.debian.net/77688/ makes it build.20:45
AmpelbeinYou probably still had autoreconf.mk in your rules file.20:45
NoskcajCan i drop the autoreconf build dep then?20:47
AmpelbeinNo, it still gets run.20:47
Noskcajok. thanks. I'll just test build it myself then propose the merge20:48
=== freeflying is now known as freeflying_away
Logan_how can I add extra usertags with submittodebian? (cc doko)21:38
dokoLogan_, I didn't check, sorry. never used that21:47
Logan_hmm, alright21:47
Logan_I might have to tag retroactively for every bug :/21:47
dokoLogan_, see my email, you can do this with a single email to control@bugs.debian.org22:05
Logan_okay, I'll do that22:05
=== rickspencer3_ is now known as rickspencer3
NoskcajCan someone please sync xfce4-weather-plugin from debian stable to precise? it would fix bug 124462922:24
ubottubug 1244629 in xfce4-weather-plugin (Ubuntu Precise) "SRU xfce4-weather-plugin, currently showing 'No Data'" [Undecided,In progress] https://launchpad.net/bugs/124462922:24
Noskcajwhich is making it unusable22:24
Logan_Un momento.22:24
Logan_Oh, precise?22:24
Logan_You didn't subscribe ~ubuntu-sru.22:25
Logan_Er. Hold up. There was already an SRU upload?22:25
Noskcajno, and no22:26
Noskcaji've just subscribed SRU22:26
Logan_It hasn't been approved yet.22:26
Noskcajand it shouldn't be approved. It's broken22:26
infinityBroken how?22:27
Noskcajwhich is why i was waiting for -5 to ask22:27
ubottuUbuntu bug 1244629 in xfce4-weather-plugin (Ubuntu Precise) "SRU xfce4-weather-plugin, currently showing 'No Data'" [Undecided,In progress]22:27
infinityNoskcaj: We're not going to sync a new upstream from Debian to precise.22:28
NoskcajNot a new upstream. two new debian stable uploads22:28
Noskcajalthough i can change that to one ubuntu upload if you'd prefer22:28
infinityErm.  0.7.4-3 in precise, versus.  Oh, I see, you mean from wheezy.22:29
infinityI misread.22:30
infinityWe, we *could* sync that, though it wouldn't have the LP bug reference in it, which makes it a bit harder to track.22:31
infinityIf someone's willing to verify the SRU as soon as it's built, I wouldn't be against just syncing it.  I just wouldn't want it to get lost/forgotten in proposed forever.22:31
infinityNoskcaj: Would you be okay with doing a verification pretty much immediately?22:31
Noskcajwe've got a fair few affected users. We'll find people22:32
Logan_shouldn't we get rid of the current one in the queue first?22:32
NoskcajI think some of the other xubuntu devs have a precise machine22:32
NoskcajLogan_, yes22:32
infinityLogan_: This would supersede that, so meh.22:32
infinityBut I can reject it right now.22:32
infinityLP hasn't picked up the new wheezy upload yet, so couldn't sync it even if I wanted to.22:35
Noskcajok, let me know when it does and i'll find some people to test22:36
=== timrc is now known as timrc-afk

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!