zygaxnox: ping00:12
zygaxnox: I think I solved update-alternatives pretty much once and for all https://github.com/zyga/command-not-found/commit/2ee281a9750c1240c33af99b9ea4f3b84d6b44f100:13
zygaxnox: I have a large database, I'll find a new home for it soon00:13
zygaxnox: using that db, we can build 100% reliable c-n-f and rebulild it against new packages without much difficulty00:15
zygaxnox: http://screencloud.net/v/7uOD00:31
saiarcot895Before merging a branch into Ubuntu universe, do I need to sign an agreement with Canoical?02:08
RAOFsaiarcot895: No, but the question probably betrays a misunderstanding off how uploading to Ubuntu works.02:09
RAOFLet's see if we can sort that out...02:10
RAOFsaiarcot895: Canonical requires a CLA for non-trivial patches to Canonical projects - these being things like Upstart, Unity, LightDM, etc.02:11
RAOFsaiarcot895: Ubuntu is not a Canonical project :)02:11
saiarcot895I saw that link in a Ubuntu doc and worried if I was missing something02:12
ionHuh, LightDM is a Canonical project? Didn’t know that.02:12
RAOFion: Yeah, it got adopted around... Precise?02:12
RAOFMore generally, Ubuntu is quite a different thing to Upstart, LightDM, etc; Ubuntu is largely an aggregation of other projects, so it doesn't really make sense to ask for a contributor agreement.02:12
ion/usr/share/doc/lightdm/copyright doesn’t seem to mention Canonical.02:13
maslenCan someone succinctly explain the relationship between existing open-source projects that are integrated into Ubuntu and Ubuntu itself?04:34
=== jono is now known as Guest52708
dholbachgood morning06:35
pittiGood morning07:06
=== amitk is now known as amitk-afk
zygagood morning07:33
cousteauI'm getting this error on update-manager due to a LibreOffice PPA:  libreoffice-core: Depends: libgcc1 (>= 1:4.1.1) but 1:4.6.3-1ubuntu5 is installed07:56
cousteauquestion:  isn't 1:4.6.3-1ubuntu5 >= 1:4.1.1 ?07:56
dholbachSweetshark, ^ maybe you know what's going on there?07:57
cousteauoh, Sweetshark is here...  good07:58
cousteau(looks away though)07:58
cousteaualthough my question is more related to why (1:4.6.3-1ubuntu5 >= 1:4.1.1) is false07:59
ogra_is that a release upgrade ?08:00
cousteaua precise -> quantal?  no08:00
ogra_i.e. from one release to the next08:00
ogra_ah. k08:00
cousteaujust regular automatic updates08:00
cousteau(from a PPA)08:00
ogra_i know we once had a function that kept PPAs at lower prio in such cases ... shouldnt happen in regular updates (and i dont think its still there anyway)08:01
=== tkamppeter_ is now known as tkamppeter
gesercousteau: does it happen too when you try to upgrade with apt-get?08:05
* zyga updated his update-alternatives scan to 25% of the archive https://github.com/zyga/ubuntu-update-alternatives-data/blob/master/update-alternatives-db.ini08:05
cousteauapt-get -s install -f didn't say anything weird...  let me try apt-get upgrade08:06
cousteau(it's apt-get upgrade, right?)08:06
cousteauapt-get -s upgrade -> You might want to run 'apt-get -f install' to correct these.  The following packages have unmet dependencies:  libreoffice-core : Depends:  libreoffice-common (> 1:4.0.2~rc1) but 1:4.0.1~rc2-0ubuntu1~precise1~ppa1 is installed08:07
cousteaunow it's complaining about a totally different pkg...  why did it mention libgcc1 before?08:08
mitya57because libreoffice-core is unpacked but has unmet dependency08:09
cousteauok, why isn't libreoffice-common getting updated to 1:4.0.2?08:10
gesertry if "apt-get install libreoffice-core libreoffice-common" gives a better hint (might have to repeat it with additional packages till you see the final error)08:11
mitya57what does "apt-get install libreoffice-common" say for you?08:11
cousteauhmm, it's update-manager the one that doesn't let me install libreoffice-common...  let me see08:11
geserwhich PPA is that?08:12
cousteauapt-get -s install libreoffice-common  ->  [...] The following packages will be upgraded:  libreoffice-common   1 upgraded, 0 newly installed, 0 to remove and 14 not upgraded.  12 not fully installed or removed.   Inst libreoffice-common [1:4.0.1~rc2-0ubuntu1~precise1~ppa1] (1:4.0.2~rc1-0ubuntu1~precise2 LibreOffice PPA:12.04/precise [all])  [...]08:14
mitya57I see there are 14 not upgraded packages, can you run "apt-get dist-upgrade" and see what happens?08:17
Sweetsharkdholbach, cousteau: Hmm, I dont understand the issue either.09:06
Sweetsharkdholbach: Im not aware of other reports wrt -core -> libgcc deps .... strange.09:07
geserit would be nice to know if cousteau could resolve this09:08
Sweetsharkgeser: yes, as seen on https://plus.google.com/u/0/101094190333184858950/posts/byfaUDmpYCn there is clearly demand for that update to be in raring.09:14
Sweetsharkdholbach: ahh, thats in the precise ppa!09:15
dholbachI have no idea - I just thought I'd bring the two of you in touch :)09:15
cousteaugeser, not yet09:17
cousteaumaybe just installing libreoffice-common fixes the issue09:18
cousteau(and then marking it as auto installed...  how is that done in apt-get?)09:18
geserwith "apt-mark"09:19
ogra_did you try dist-upgrade ?09:19
cousteauyup, apt-mark09:19
ogra_it should tell you about adding/removing09:19
cousteauI don't want to try anything that fixes the system until I find out the problem...  how would I be contributing if I just fix my system?09:19
cousteau(or am I the only one affected by this problem?)09:19
ogra_dist-upgrade will have a y/n question09:20
ogra_it never does anything automatically if it actually adds or removes09:20
Sweetsharkdholbach, cousteau: precise is still at 4.0.2~rc1, which needed a dist-upgrade -- the 4.0.2~rc2 release in raring should have that fixed, backports for quantal/precise with hopefully show up soon ...09:20
cousteauapt-get -s dist-upgrade   ->  The following packages have unmet dependencies:   libreoffice-core : Depends: libreoffice-common (> 1:4.0.2~rc1) but 1:4.0.1~rc2-0ubuntu1~precise1~ppa1 is installed   libreoffice-emailmerge : Depends: libreoffice-common (>= 1:4.0.2~rc1) but 1:4.0.1~rc2-0ubuntu1~precise1~ppa1 is installed   You might want to run 'apt-get -f install' to correct these.09:21
ogra_theer you go09:22
Sweetsharkcousteau: yep, should be fixed09:22
cousteau(on an unrelated note, I'm actually getting "You might want to run 'apt-get -f install' to correct these" BEFORE the list of packages to be fixed)09:22
geserdid you try to install a deb with dpkg? I'm wondering why apt suggests to run "apt-get -f install"09:22
Sweetsharkcousteau: should be fixed http://anonscm.debian.org/gitweb/?p=pkg-openoffice/libreoffice.git;a=commit;h=cbb64e23f4023b16d449d33ac94c75f0c7933fce09:24
cousteauThe problem seems to be that, for some reason, libreoffice-core 1:4.0.2 has been installed but libreoffice-common hasn't (still at 1:4.0.1).  This has broken apt-get, which will refuse to install libreoffice-common 4.0.2 because there are unmet dependencies in the system.09:28
cousteauSilly apt-get doesn't realize that the solution is precisely to install this package it refuses to install.  I guess I'll have to -f09:29
geserhow did you manage to install this version and not the other packages from libreoffice as they get all build from the same source package09:30
cousteauok, running `sudo apt-get install -f`; I guess that'll fix the problem.  (running it with -s said it would install/upgrade libreoffice-common)09:30
cousteaugeser, no idea.  Aliens?09:30
cousteauI remember that yesterday I had a problem with upgrades, but I think it was just the broken dependency thing09:31
cousteauI hope this didn't have to do with a pre/post install config09:32
gesercousteau: which arch are you using? i386 or amd64? and which PPA is that?09:33
cousteauok, apt-get install -f seems to have fixed the problem09:33
cousteauamd64,  http://ppa.launchpad.net/libreoffice/ppa/ubuntu precise main09:33
cousteau(using xubuntu, if that's relevant, but I guess it isn't)09:35
Sweetsharkricotz: ping? could you update the precise/quantal backports?09:36
Sweetsharkah, not here.09:36
gesercousteau: when did you last run "apt-get update"? you might have updated the Packages files in the time window where amd64 was finished building but not i386 (incl libreoffice-common)09:37
geserthis would explain why you could update some libreoffice packages but not all09:37
cousteaugeser, how can I know that?  is there an apt-get update history or something?09:40
geserin that case try updating the package lists and see if your problem is gone (amd64 and i386 are both build now)09:41
cousteauI opened the update manager at approx 19:45+0200 (i.e. 17:45 Z)09:42
cousteaugeser, I tried that and it didn't.  I fixed it by running `sudo apt-get install -f`09:43
gesergood that it's fixed now, but I don't understand what went wrong in the first place09:44
cousteaume neither09:44
=== sraue_ is now known as sraue
=== doko_ is now known as doko
cousteaugeser, probably what you said.  -core 4.0.2 was updated before -common 4.0.2 was available, and installing -core 4.0.2 broke apt-get, so when -common was available it couldn't be installed09:49
cousteauor maybe -core 4.0.2 and -common 4.0.2 were made available at the same time but -core was installed before -common and that immediately broke -core09:49
cousteaulibreoffice-core depends libreoffice-common (> 1:4.0.2~rc1), but libreoffice-common doesn't depend on libreoffice-core.  So none of this mess would have happened if the update for -core had been held until -common were available.09:51
=== security is now known as megha
geserapt usually takes care of that marks such packages on hold during an upgrade till the dependencies are available09:52
Sweetsharkcousteau: i would assume you hit https://bugs.freedesktop.org/show_bug.cgi?id=62972 and did not notice09:59
ubottuFreedesktop bug 62972 in Libreoffice "Cannot upgrade from Ubuntu 12.04.2" [Major,Resolved: notourbug]09:59
geserah, that might explain the "apt-get -f install" call to let dpkg finish the configure of some packages10:02
cousteauI haven't tried to open LibreOffice; I wouldn't know10:12
cousteauso, ubuntu bug or LO bug?10:13
cousteauactually, why do I care?  it's already fixed10:13
cousteau...well, there's always the curiosity thing10:13
geserif you got hit by this bug then it's a packaging bug in the LO package (don't know if you count this as ubuntu bug or LO bug)10:17
Sweetsharkcousteau: it was a ubuntu bug (well, actually a debian bug that we merged in ;) ) -- the contents of the mailmerge package got move to -core and making sure that the old -mailmerge and the new -core package are not installed at the same time was fumbled.10:17
dbarthxnox: ping? is there a problem with the package upload for thin client? can i do something to help?10:17
cousteauso it was a bug in the ubuntu build system?10:17
cousteaui.e. not in the ubuntu installer, but in the thing that builds packages and distributes them to ubuntu users10:18
xnoxdbarth: no problems. the archive is frozen and it's pending review & accept.10:19
dbarthah ok10:19
Sweetsharkcousteau: not in the build system, in the package description -- the debian/control file to be exact: http://www.debian.org/doc/debian-policy/ch-controlfields.html10:19
xnoxdbarth: we just have to wait =)10:19
cousteauso DEBIAN/control was incorrectly generated, or incorrectly read by apt-get?10:20
gesercorrectly generated but with the wrong data (error of the package maintainer)10:21
Sweetsharkcousteau: incorrectly generated10:21
cousteauso a server-side problem10:28
cousteaui.e. "an ubuntu bug" where "ubuntu" is the package build system, not the ubuntu installer10:30
=== amitk-afk is now known as amitk
zygaxnox: hi10:55
zygaxnox: I've sent an email to ubuntu-devel last night10:55
=== MacSlow is now known as MacSlow|lunch
dokopitti, would it be ok to discard/hold the language pack uploads? the test rebuild should finish first, and afaiu, these will be re-uploaded next week anyway?12:08
seb128doko, it would be useful for translators to have those so they can verify what translations are incomplete or buggy12:09
seb128so they can fix things for the update next week12:09
=== MacSlow|lunch is now known as MacSlow
pittidoko: no problem from my side, Monday will be the next cronjob anyway12:20
pittidoko: but I thought infinity already mass-rejected them12:20
tvosspitti, ping12:26
pittihello tvoss12:26
tvosshey pitti :) I'm looking into fanotify right now. Does it work in 13.04/12.10?12:27
pittitvoss: I haven't used it in ages, but I don't see why it shouldn't work12:27
tvosspitti, cool :) I was just curious and wanted to check it out, if file moving/renaming is delivered to userspace in its current version or not12:28
=== _salem is now known as salem_
rbasakdistutils.sysconfig.get_python_lib(True, True) gives me /usr/lib/python2.7 in raring. But libpython2.7.a is in /usr/lib/python2.7/config-x86_64-linux-gnu. What's the general way of getting this latter path? I know python-config --ldflags will give me the right thing, but this particular acinclude.m4 isn't using it and I think it would be a more trivial patch if I could extract just the right path where libpython2.7.a can be found.12:46
smbdoko, https://launchpad.net/ubuntu/+source/xen/4.2.1-0ubuntu2/+build/4469971 <-- Internal compiler error. I am currently trying a local sbuild so I could pull things off...12:48
dokosmb, please wait until -23ubuntu2 is available12:50
smbdoko, Ah ok.12:51
pittidoko: mass-rejecting the langpacks, FYI12:51
dokopitti, thanks!12:52
pittidoko: however, with the projected 8 days of ETA there will be new cronned uploads12:52
dokoI know ...12:52
pittiif only we had some way of temporarily spawning more servers in the internet out there to help with mass rebuilds...12:53
pittiwe could call this "sky"12:53
dokopitti, I assume policykit-desktop-privileges is targeted for raring?12:56
pittiBigWhale pointed out that inconsistency12:56
pittiit doesn't change the default install behaviour, though12:57
smbdoko, Hm, maybe dumb question -23ubuntu2 or *what*?12:57
dokosmb, https://launchpad.net/ubuntu/+source/gcc-4.7/4.7.2-23ubuntu212:58
smbAh ok. I was confused by the dependency gcc package version13:01
smbDaviey, ^ I try to remember we probably need to kick the build again later... maybe next week... :)13:04
Davieysmb: super13:07
dokosmb, will be finished in 1h13:11
smbdoko, okok, maybe this week still. ;)13:12
jdstrandseb128: fyi, http://people.canonical.com/~jamie/archive-grep/seb128-com.ubuntu.SystemService.log13:13
seb128jdstrand, hey, happy friday!13:13
seb128jdstrand, thanks13:13
jdstrandseb128: hi! you too and you're welcome :)13:13
=== ckpringle_ is now known as ckpringle
seb128pitti, ^13:13
ogra_oh, do we rename the system service to be seb128.system.service ?13:14
ogra_cool !13:14
seb128ogra_, with french strings included by default ;-)13:14
seb128pitti, so it seems it's only update-notifier to fix13:14
=== Pricey is now known as PriceChild
=== PriceChild is now known as Pricey
xnoxogra_: système.de.service.seb12813:20
ogra_oh, indeed, i forgot ... french now13:21
rbasakdistutils.sysconfig.get_python_lib(True, True) gives me /usr/lib/python2.7 in raring. But libpython2.7.a is in /usr/lib/python2.7/config-x86_64-linux-gnu. What's the general way of getting this latter path? I know python-config --ldflags will give me the right thing, but this particular acinclude.m4 isn't using it and I think it would be a more trivial patch if I could extract just the right path where libpython2.7.a can be found.13:46
pittiseb128: alors qui semble très facile13:46
pittiseb128: (excusez-moi, j'ai été à une réunion13:47
seb128pitti, il n'y a pas de problème13:47
=== ckpringle_ is now known as ckpringle
pittiseb128: AFAICS it only calls is_package_system_locked13:48
kapatHello, just upgraded to raring beta and X won't start. Ideas? where (and how) should I submit bug reports?13:49
pittiwhich is basically a set of lock file existence tests13:49
seb128pitti, should be easy to replace13:49
pittiso we should completely drop that and just test for those locks13:49
pittiand then, python daemons -= 113:49
seb128the proxy thing is still annoying13:49
seb128I need to talk to cyphermox to see if there is a plan to get that done in nm13:50
cyphermoxupstream wants to integrate it, I had a WI but since it's not priority... and there has been some interest from someone to do the work on the ML13:51
xnoxkapat: raring suport at > #ubuntu+114:08
=== padv is now known as dsflms
dokosmb: xen fails now correctly ;-p with:14:24
dokointr.c: In function 'vmx_intr_assist':14:24
dokointr.c:305:17: error: request for member 'arch' in something not a structure or union14:24
dokointr.c:306:17: error: request for member 'arch' in something not a structure or union14:24
dokointr.c:307:17: error: request for member 'arch' in something not a structure or union14:24
dokointr.c:308:17: error: request for member 'arch' in something not a structure or union14:24
dokomake[8]: *** [intr.o] Error 114:24
smbdoko, Hm, ok. Apparently something only working on 64bit... But at least a more helpful failure14:25
barrydoko: any feedback on my email from last night?14:28
dokobarry, on the bug report14:28
barrydoko: thanks14:28
=== salem_ is now known as _salem
=== _salem is now known as salem_
dokobarry, the python builds are still configued with --enable-fpectl. I don't think that makes any difference14:53
barrydoko: ack.  i'm inclined to just apply the hack and be done with it14:59
=== ckpringle_ is now known as ckpringle
zygaxnox: ping16:25
xnoxzyga: hola.16:26
zygaxnox: I got some progress since yesterday16:27
zygaxnox: first, I solved the problem with flaky update-alternatives data, it's now almost perfect and the small percentage of mistakes are tagged and can be corrected (so far I have < 200 cases but after fixing one the system learns and can cascade the solution to similar packages)16:28
zygaxnox: I've also mirrored half of the archive and rewrote/improved the scanning tools16:28
zygaxnox: by Monday I should have a new, pratically perfect database for precise, quantal and raring16:28
zygaxnox: then we can issue an update to the source package with the new database16:29
zygaxnox: does that sound okay?16:29
pittiawe: hey Tony, how are you?16:29
zygaxnox: I've tweeted about the progress, there is a new project that holds the database and I've sent an email to ubuntu-devel16:30
zygaxnox: (sadly no response so far)16:30
pittiawe: I'm currently writing network tests, and stumbled over a CRDA problem that you might know about16:30
xnoxzyga: yes. I can upload the updates to raring/quantal/precise.16:31
zygaxnox: great16:31
zygaxnox: the data is text and I can also produce some diffs so that we can do some level of validation16:31
awepitti, hey16:31
awetests are good16:31
aweas for crda, be ready for a world of confusion... ;)-16:32
awewhat's troubling you right now?16:32
awemaybe do a quick mumble?16:32
pittiawe: so, b/g test cases work fine; for A I chose channel 36, as it shoudl be available in most parts of the world16:32
=== deryck is now known as deryck[lunch]
pittiawe: if I run my tests locally, they always work; but if I run them in a fresh KVM instance, they fail with "channel [0] (36) is disabled for use in AP mode, flags: 0x57"16:33
pittiawe: so my question is: do you know how we set the domain for devices? I know of /lib/udev/rules.d/40-crda.rules which is supposed to set it through that helper16:33
awewhy are you running in a container?16:33
pittiawe: but /etc/default/crda has nothing set on my workstation either, so I suppose it uses something else to determine the domain?16:34
awepitti, we actually don't set the domain for devices16:34
pittiawe: we want this as autopkgtest, don't we?16:34
awethe drivers handle it16:34
pittiawe: so I'm trying to understand why it works on my workstation but not in kvm16:34
pittiawe: I actually got it to work in kvm if I add a country_code=EU to hostapd's config16:34
awepitti, I'm not that familiar with the autopkgtest framework....  but I do know that networking inside containers/vms is not trivial16:34
pittibut apparently that only works teh second time, so there's something async going on16:34
aweespecially when you need to work with wifi drivers16:34
pittiawe: no worries, I got those parts covered16:35
awepitti, ubuntu doesn't set a default regdomain16:35
pittiawe: I now have A/B/G networks, open and wpa2, and IPv4/6 coverage16:35
awepitti, are you running against real drivers, or using the passthru code?16:35
awe( ie. driver passthru )16:35
pittiawe: just mac80211_hwsim16:35
pittiso real driver, but no real hw16:36
awewell, some might take issue with "real" driver16:36
pittiawe: but with the same hwsim driver it works on my workstation16:36
aweie. real being non-sim16:36
pittiawe: ok, I guess I'll have to dissect that a little further then16:37
pittiawe: I just thought you might have some idea how that can happen16:37
awecan we do a quick mumble?16:37
=== francisco is now known as Guest49443
=== tvoss is now known as tvoss|dinner
pittiawe: ok, apparently hwsim doesn't support setting crda; "sudo COUNTRY=DE crda" works on my workstation, but fails in kwm; I guess that depends on the loaded drivers17:06
dokopitti, seb128, didrocks: could somebody of you look at the rhythmbox ftbfs? https://launchpad.net/ubuntu/+archive/test-rebuild-20130329/+build/4443117 all archs17:08
seb128doko, it's on my list, sorry I didn't go to it today, I might still manage to do that before calling it a day, otherwise will do on monday17:12
pittiawe: ah, so "sudo iw reg get" and "sudo iw reg set EU" are the magic commands; http://wireless.kernel.org/en/users/Documentation/iw#Updating_your_regulatory_domain and http://wireless.kernel.org/en/developers/Regulatory are quite helpful17:26
pittiawe: that works very well now17:27
pittiawe: I'll also change the tests to look at "iw" instead of "iwconfig" to verify connection, etc. :)17:27
pittiso, good night everyone, enjoy your weekend17:27
aweyes, although they're only magic, when the driver supports the incantation!  ;D17:27
=== salem_ is now known as _salem
pittiawe: why? that's set by cfg80211, not by the hw driver17:27
pittiawe: or you mean it won't work for drivers which don't use the cfg80211 framework?17:28
aweyes, but cfg80211 has to talk to the driver at some point17:28
aweit's just the messenger17:28
awe( re: drivers that don't use cfg80211 )17:28
pittiawe: I think what happens here is that hostapd asks the wireless stack (i. e. the equivalent of iw reg get) about the country17:28
pittiawe: I guess the hwsim kmod doesn't care, as it doesn't actually emit anything17:29
aweyea, definitely... wpa_suppl has similar code17:29
pittianyway, seems I have all pieces together now \o/17:29
aweglad I could help17:29
=== _salem is now known as salem_
=== mitya57 is now known as mitya57_
=== security is now known as megha
=== achernya_ is now known as achernya
=== deryck[lunch] is now known as deryck
=== salem_ is now known as _salem
dokojtaylor, is there a FFe for scilab?18:04
jtaylordoko: its essentially translation update18:04
jtaylorthe diff is only large as its a normal dist tarball instead of git archive18:04
jtaylorif you drop translations and the missing makefiles the diff is almost zero18:04
jtaylorraring currently has git20130321, only ~two weeks old18:06
jtaylor(and I got an ffe for that when it when in before you ask)18:07
CheezeMonkeyJust to let you guys know, ubuntu finally installed after i unplugged two of my three harddrives, probably had something to do with the many partitions i have18:14
CheezeMonkeythanks for your help, especially xnox for the link18:14
=== _salem is now known as salem_
jtaylorCheezeMonkey: you have the installer hanging on the second screen issue?18:26
CheezeMonkeyjtaylor: yep18:27
jtaylorCheezeMonkey: which link? have that issue too :(18:27
jtaylordid you unplug internal disks?18:28
jtaylorI tried unplugging my external ones with no success18:28
CheezeMonkeyjtaylor: https://launchpad.net/bugs/108070118:28
ubottuLaunchpad bug 1080701 in ubiquity (Ubuntu Raring) "After 'Preparing to install Ubuntu' screen, raring installation hangs" [High,Confirmed]18:28
CheezeMonkeyFor me, i have three internal harddrives. Two of them are used, with quite a few (probably excessive) partitioning.18:29
jtaylorI have many many partitions too18:29
jtaylorseems to be the common factor in this bug18:29
CheezeMonkeyI took those out, and left the third smaller one inside, which had only two partitions (one being a swap partition for linux).18:30
CheezeMonkeythen i tried the installer again, and it worked like a charm :)18:30
=== Ursinha_ is now known as Ursinha
=== hallyn_ is now known as hallyn
=== superm1_ is now known as superm1
=== salem_ is now known as _salem
=== bschaefer_ is now known as bschaefer
jtaylorhm there is something weird on the arm builders22:30
jtaylorscilab failed with a "stray \38" in a source file, the file is fine22:30
jtaylorI just retried it and it worked22:30
jtaylorhow can that happen?22:30
Laneykeep watching the buildd's history and see if it builds subsequent stuff correctly22:32

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