/srv/irclogs.ubuntu.com/2016/08/05/#ubuntu-devel.txt

=== salem_ is now known as _salem
=== juliank_ is now known as juliank
=== _salem is now known as salem_
=== salem_ is now known as _salem
xnoxsarnold, thanks my vps with irc bouncer had a hickup04:38
yellabs-r2hello , good morning07:09
yellabs-r2this is just a quick flyby , i guess its known that zenity is broken on ubuntu 16.04 ?07:09
yellabs-r2it spits out an error message : Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.07:10
sarnoldplease file bugs, what's obvious to users may not be obvious to us07:10
yellabs-r2i think its an debian issue ( or zenity )07:10
yellabs-r2there are lots of file bugs ,  and i know your time is precious07:11
yellabs-r2you can test and see it yourself07:12
yellabs-r2open terminal and type zenity --info ( if you have a ubuntu desktop )07:12
RAOFyellabs-r2: That's not actually an error; what is the problem you're seeing?07:12
sarnoldthat's the thing, i, personally, have no idea what zenity -is- :) if you a file a bug, someone who knows what it is might see the bug :)07:13
yellabs-r2Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.07:13
yellabs-r2try zenity --info from terminal ( on ubuntu desktop 16.04 or up )07:13
yellabs-r2sarnold , i understand ;)07:14
RAOFyellabs-r2: Again, that's not actually an error :)07:14
Unit193sarnold: IIRC, makes shiny GUI dialog boxes pretty easily.07:14
RAOFyellabs-r2: That's a warning, which is entirely harmless.07:14
sarnoldUnit193: oh, like whiptail but .. with gtk dialogs :)07:15
yellabs-r2its not nice to see , when running a script , can we avoid such warning ?07:15
RAOFyellabs-r2: You could patch zenity to not use a GtkDialog.07:18
yellabs-r2okey i will do that, thanks for your time07:18
yellabs-r2keep up the good work !07:18
tvossxnox, o/07:37
jtaylorhm does clang++ work for anyone in xenial?08:22
jtaylorit seems to search for stuff in the wrong folders08:22
juliankdoko: Could APT or qapt (?) be having a tiny ABI break on ppc64el and s390x? I synced apt 1.3~pre4 yesterday, and now the libqapt tests fail with abi-compliance-checker exiting with 6. Ideas?08:34
juliankI do see some symbol changes in APT;  but with all the templates involved, that's not out of the ordinary08:37
dokojuliank, see https://lists.debian.org/debian-release/2016/08/msg00038.html, you probably hit https://gcc.gnu.org/ml/gcc-patches/2016-04/msg00314.html when using template member functions.08:41
ubottugcc.gnu.org bug 2016 in rtl-optimization "-O _AND_ -funroll_all_loops causes segfaults on PPC" [Normal,Resolved: fixed]08:41
dokoif yes, then please do an abi bump08:41
juliankdoko: AFAICT from dpkg-gensymbols, there are no missing cxx11 symbols. The only cxx11 mentioned in the negative string is part of __cxx11::basic_string08:44
dokojuliank, it's not about missing symbols, it's about a missing __cxx11 in some symbols08:45
Laneyjuliank: do you know about https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/i386/a/apport/20160805_024013@/log.gz ?08:54
juliankdoko: Yes, I'm looking at it08:55
juliankehm, Laney08:55
Laney<308:55
Laneyor ♥ if you prefer08:55
juliankLaney: It might be related to Dir::State::Status not being absolute /var/lib/dpkg/status anymore, but being automatically detected dependening on Dir::State08:56
* juliank wonders how much ~pre4 will break08:56
juliankLaney: But on the other hand, the python-apt rootdir option already sets that itself...08:58
juliankSo I'm a bit confused08:58
juliankLaney: Do you have a way to run the apport autopkgtest locally (I have not set up autopkgtest yet, and am basically doing blind test suite fixing ...) - It might be as simple as https://paste.ubuntu.com/22292870/09:05
* juliank would have run the test directly, but they require root09:06
juliankHmm, it seems I can easily build that test environ09:07
tsdgeosguys, i'm getting "GPG error: http://security.ubuntu.com/ubuntu yakkety-security InRelease: At least one invalid signature was encountered."09:09
tsdgeosis that known or something?09:09
tsdgeosor am i being hijacked in my dns/http traffic?09:09
Laneyjuliank: I usually use "adt-buildvm-ubuntu-cloud -r yakkety" to make a qemuable image you can pass to adt09:12
Laneyprobably pitti would tell me that's the 2014 way of doing it, but he's not here ...09:13
juliankLaney: I tried that and it severely hangs my machine :/09:17
juliankLet's try again without chrome running...09:17
juliankLaney: It seems autopkgtest qemu uses up a lot of space in /tmp, thus leading to memory pressure, as that's a tmpfs09:20
Laneydoes it respect TMPDIR?09:21
LocutusOfBorgjtaylor, for some particular projects it is not working09:21
LocutusOfBorgyou are right09:21
LocutusOfBorgbut in general, it works09:21
LocutusOfBorgand BTW you didn't say version and project09:21
LaneyI actually used to do that the other way around, set TMPDIR to a tmpfs somewhere else as for me /tmp is not one but I've got enough ram09:22
LaneyI never checked it didn't leak stuff into /tmp though09:22
juliankLaney: It creates some overlay in tmp, I hope I fixed that now09:24
Laneyyou can also use schroot, but not sure if that's good enough for apport09:24
juliankLaney: I'm setting up an lxc in parallel09:29
Laneymardy: hey... any idea what this "Web Authentication for Google" webview I started getting this morning is about? :)09:39
Laneyunity7 yakkety09:39
jtaylorLocutusOfBorg: I mean a simple file containing only main and including cstdio09:47
jtaylorLocutusOfBorg: or finding libstdc++09:47
jtaylorthough I'm on an upgraded system so the folders might be a bit messier than they should09:47
LocutusOfBorgbug clang version?09:55
LocutusOfBorgs/bug/but09:55
LocutusOfBorghttps://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.5/+bug/137206209:56
ubottuLaunchpad bug 1372062 in llvm-toolchain-3.5 (Ubuntu) "Some LLVM 3.5 headers are in wrong paths and different from llvm-3.5 installed from sources." [Undecided,Confirmed]09:56
Laneyjuliank: I've got a VM where it fails if you want access09:58
jtaylorLocutusOfBorg: 3.810:00
LocutusOfBorgoh :(10:02
LocutusOfBorgfrom updates?10:02
jtayloryes10:03
juliankLaney: autopkgtest works now, setup is a bit annoying, though ...10:05
=== hikiko is now known as hikiko|ln
LaneyI only did the vm thing, that's easy enough10:06
mardyLaney: could be that both the access token and refresh token have expired10:07
mardyLaney: if you log in, please pay attention to which app is requesting access in the google webview10:08
Laneymardy: I mean that it's just a dialog asking for my credentials, but it doesn't tell me why it wants them10:10
Laneyyou think I should log in?10:10
mardyLaney: no, wait10:10
mardyLaney: can you reproduce it at will?10:10
Laneywell, it happened the two times I've logged in today10:10
LaneyI think I set some environment variables for signon-ui debugging before10:11
mardyLaney: can you paste the syslog somewhere?10:11
Laneymardy: is 'grep signon' okay?10:12
Laneymardy: https://paste.debian.net/78702710:14
mardyLaney: should be ok, yes10:16
mardyLaney: unfortunately the signond log doesn't tell me much about who the requestor is... do you know of a way to set an environment variable which will be visible to processes auto-started by dbus?10:24
Laneymardy: sure, I can stuff something into systemd10:27
juliankLaney: I uninstalled libpam-tmpdir and can now run autopkgtests in schroot - much faster than qemu :D10:28
mardyLaney: this would help: SSOUI_LOGGING_LEVEL=210:28
Laneymardy: https://paste.ubuntu.com/22298856/ is that more useful?10:36
mardyLaney: and you have the same dialog visible?10:41
Laneyyep10:43
mardyLaney: and xkill tells you that's signon-ui? can you also check the pid please?10:45
Laneymardy: what process needs that env var10:45
Laney?10:45
Laneysignond didn't get killed when I logged out so it doesn't have it10:45
mardyLaney: signon-ui10:45
Laneyit's definitely signon-ui10:46
Laneyand the window's process has the environment variable set10:46
mardyLaney: pid 7936?10:46
Laney1722010:46
mardyuh10:46
Laneynot mentioned in syslog at all10:46
Laneybut that's the pid of signon-ui10:46
mardyLaney: do you also have another signon-ui as pid 7936?10:47
Laneythat's the dbus-daemon10:47
mardyah right10:47
Laneyaha10:47
Laneythat makes sense10:48
juliankLaney: Fixed in -0ubuntu510:49
juliankNow there's only the weird abi-compliance-checker issue in qapt to be fixed10:50
juliankUnfortunately, there is no output at all10:50
juliankwhich makes it hard to debug what exactly it is complaining about...10:51
dokojuliank, maybe wait for xnox, there are similar issues, e,g, in gnupgpp autopkg tests10:51
xnoxwell acc is easy enough to run by hand.10:52
juliankdoko: Mmh, OK. AFAICS, it errors out when dumping the ABI, not when comparing it...10:52
xnoxi guess it should be more verbose.10:52
juliankThat is, "abi-compliance-checker -q -l libqapt-dev -v1 3.0.2-0ubuntu3 -dump debian/libqapt-dev.acc -dump-path debian/libqapt-dev/usr/lib/s390x-linux-gnu/dh-acc/libqapt-dev_3.0.2-0ubuntu3.abi.tar.gz returned exit code 6"10:52
Laneyjuliank: why the host's status file?10:54
mardyLaney: it's very weird, the only request signon-ui gets (grep for queryDialog in the log) is for a web-based authentication, and that's handled opening an oxide webview, not a username/password dialog10:54
juliankLaney: Well, the chroot has no status file, and that was the previous default for Dir::State::Status, so it's the obvious fix to return it to old APT defaults where it worked ...10:54
juliankLaney: I don't know enough about apport to know why it uses the host status file there, but I guess it does not matter anyway.10:55
juliankLaney: Once pitti reappears he can rebuild it however he wants :D10:56
xnoxtvoss, where are you hitting the issue? as far as i can tell we don't ship gmock in ubuntu archive....10:56
xnoxand gtest package in ubuntu doessn't gmock10:57
tvossxnox, sorry, it's google-mock and an upgrade this morning brought in a fixed google-mock to y10:57
tvossxnox, sorry for looking into it, let me mark the bug as invalid10:57
tvossthe one against gtest that is10:57
xnoxah10:57
xnoxwell, it needs changing from gtest to google-mock10:57
xnoxi'll fix that up10:58
xnoxeverything changed names upstream now10:58
juliankxnox: The problem with running acc manually is that it only fails on ppc64el and s390x10:59
juliankxnox: ...10:59
xnoxlol =)10:59
* xnox shall fix that10:59
xnoxtvoss, can't fix gtest cause that fails with g++-6, even upstream.11:00
* xnox should suggest to smr to package googletest as a new source package with new googletest and googlemock combined11:00
=== hikiko|ln is now known as hikiko
xnoxtvoss, Laney fixed everything already?! =) so i should ignore this11:01
xnoxtvoss, now i understand what you mean.11:02
=== vrruiz_ is now known as rvr
Laneyxnox: wat11:08
Laneymardy: it is a webview11:08
Laneysorry, I must have forgotten to say that11:08
Laneyxnox: the maintainer of google-mock emailed me asking if I wanted to become the maintainer after I NMUed it11:09
Laney"erm, thanks but no thanks"11:09
mardyLaney: ah, ok, then it's called from pid 834611:09
Laneymardy: e-d-s11:10
mardyLaney: and if you log in, google should tell you the name of the app authenticating11:10
xnoxLaney, well google-mock and gtest got merged into googletest upstream, and gtest is maintainer by smr.11:10
xnoxI'd happy to take the lot into pkg-boost team =)11:10
Laneyxnox: lalala11:10
Laneyyou go do that11:10
xnoxand give Fredrik access rights11:10
* Laney doesn't want to maintain more weird things11:10
* juliank is also in the process of porting APT from the archaic 1998 build system to cmake ...11:11
Laneymardy: so the problem is that e-d-s requesting authentication doesn't tell me that until after I authenticate11:11
Laneyso I don't know why I'm giving my password11:11
mardyLaney: but did it appear out of nowhere? usually these requests get queued and an OSD notification is sent11:11
Laneythe webview appears when I log in11:11
Laneythere might be an OSD too, but those are transient11:12
LaneyI didn't notice11:12
Laneyand I definitely did see the notifications before, but never this dialog11:12
Laneyso something changed11:12
mardyLaney: anyway it's wrong, this screen should not appear; you should see a notification, then once you open system-settings -> online-accounts, it would tell you that the google account needs authentication11:13
mardyLaney: so please file a bug11:13
Laneyokay11:13
mardyLaney: maybe the OSD cannot be sent (maybe the D-Bus service is not up yet?)11:13
Laneywho wins the bug?11:13
mardyLaney: signon-ui11:13
Laneysignon-ui for now11:14
Laneythanks for the help!11:14
mardyLaney: the fact that it appears at login also hints that it might be because the OSD is not up yet11:14
Laneynotify-osd is D-Bus activated11:14
mardymmmm11:15
Laneycould be that the API call fails or something11:15
Laneyis the dialog a fallback in that casE?11:16
mardyLaney: can you just dismiss that dialog, and see if reappears some minutes later?11:16
Laneymardy: in fact it comes back straight away11:16
Laney!!!11:16
mardyLaney: it makes you feel loved, doesn't it?11:17
mardy;-)11:17
mardyLaney: yes, it's a fallback: http://bazaar.launchpad.net/~online-accounts/signon-ui/trunk/view/head:/src/request.cpp#L13311:18
mardyLaney: in our case windowId() == 0, so skip those two ifs11:18
Laneyfun11:18
Laneybut I don't see "Error dispatching to indicator" in the log11:19
mardyLaney: maybe findAccount() fails, line 24411:20
Laneymmm11:21
mardyLaney: can you please paste the output of "account-console list" and then "account-console show <id of the google account>"?11:21
mardyLaney: if you have more than one google account, please show all11:22
mardythe value of parameters[SSOUI_KEY_IDENTITY] is 102, according to your logs11:22
Laneymardy: ok, I can see which one is 10211:24
LaneyI should blanke out the ClientSecret right?11:24
Laneyblank*11:24
Laneymardy: bug #1610206 has it all11:27
ubottubug 1610206 in signon-ui (Ubuntu) ""Web authentication for Google" WebView appears on login" [Undecided,New] https://launchpad.net/bugs/161020611:27
mardyLaney: thanks, looking...11:28
mardyLaney: weird, the account seems all right...11:32
mardyLaney: given that you can reproduce it easily, could you please keep a dbus-monitor running?11:34
mardyLaney: if you have the dialog open right now, please just cancel it and let it reappear11:34
Laneymardy: oh god it didn't come back11:38
mardyLaney: might be that e-d-s retries just once11:38
LaneyI closed it like 5 times before11:39
Laneymaybe they had stacked up11:39
Laneyi'll leave it running and see if it appears11:39
Laneygoing to be a big dbus log11:39
mardyok11:39
dokotvoss, is https://launchpad.net/ubuntu/+source/qtgrilo/0.0.20130610-0ubuntu4 still needed, or is this cruft?11:40
xnoxjuliank, doko, Mirv: http://paste.ubuntu.com/22303251/11:42
juliankeww11:43
juliankthat looks nasty11:43
xnoxhm, why is gcc used, instead of g++11:44
tvossdoko, I don't know, Mirv ^11:44
xnoxgcc or g++ don't make a difference11:46
xnoxjuliank, Mirv - drop, reproducible with just "include <atomic>"11:49
Mirvdoko: tvoss: I believe qtgrilo is cruft, at least it's not on images. CC: sil210011:52
Mirvand qtgrilo is not surely the only package that should be removed. I have for example bug #1606531 which includes reminders-app, no longer published to archives.11:54
ubottubug 1606531 in reminders-app (Ubuntu) "RM: transitional QML module packages" [Undecided,New] https://launchpad.net/bugs/160653111:54
Mirvnot familiar with xnox's problem11:54
dokoMirv,  sil2100: https://bugs.launchpad.net/ubuntu/+source/qtgrilo/+bug/161021911:55
ubottuLaunchpad bug 1610219 in qtgrilo (Ubuntu) "demote qtgrilo, not compatible with grilo-0.3" [Undecided,New]11:56
dokoMirv, hmm, I don't see any of these packages in nbs ...11:57
xnoxdoko, https://bugs.launchpad.net/ubuntu/+source/gcc-6/+bug/161022011:59
ubottuLaunchpad bug 1610220 in gcc-6 (Ubuntu) "atomic header cannot be compiled into translation unit with -fkeep-inline-functions" [Undecided,New]11:59
xnoxregression in gcc-6 since gcc 5.411:59
Mirvdoko: they are in yakkety-proposed at the moment, the sources like qtquickcontrols-opensource-src and qtdeclarative-opensource-src12:09
=== JanC is now known as Guest20161
=== JanC_ is now known as JanC
sil2100grilo grilo, hmm, yeah, need to look into that but I guess it's not a thing anymore12:21
Laneyzap it12:21
jbichahttp://reqorts.qa.ubuntu.com/reports/sponsoring/ is up-to-date but the subpages like motu.html are 2 weeks old12:43
=== _salem is now known as salem_
seb128doko, thanks for sponsoring those totem/rhythmbox updates, do you plan to merge in the vcs as well?14:41
seb128slangasek, just a fyi I fixed the samba build on yakkety (and I'm going to backport a bugfix for a gvfs/cpu use issue)15:18
=== mnepton is now known as mneptok
slangasekseb128: ok, IIRC I did that merge to un-break the gnutls delta, so do what you need to :)15:36
seb128slangasek, the issue was a buggy ldb merge, once that fixed samba builds15:38
seb128anyway sorted out15:39
seb128I was just letting you know in case you still had it on some todolist15:39
slangasekseb128: nope, I summarily deleted all of the lp emails telling me about the build failures caused by people hitting the retry button ;-)15:40
seb128hehe15:40
=== davidcalle is now known as davidcalle|afk
naccbdmurray: as to the phasing of my virt-manager update; afaict, two of the errors are not new in my version (https://errors.ubuntu.com/problem/d742c4e2a061c34261f126539298c430d849d96d and https://errors.ubuntu.com/problem/28048ddac92361b73296c899966474adfef41982). One is new (https://errors.ubuntu.com/problem/00ae98e11d3c5f53ee5e58adb9811d3132176af4), but I'm not sure how my change could lead to that,16:28
naccas functionally it only changes virtinst.16:28
bdmurraynacc: okay, looking16:34
naccbdmurray: thanks, I'm reviewing the new one in more depth, but it seems unrelated to me.16:35
cyphermoxjuliank: is there a code branch in LP for the ubuntu diff for apt? or do you just upload directly?16:40
juliankcyphermox: There is no apt diff anymore (again), that was just some temporary direct uploads to try to get the autopkgtests working again.16:41
juliankcyphermox: I initially only planned one upload, but things got a bit out of control ...16:42
* juliank hought: oh hey, I pull the tarball and just apply my diffs, and upload; and everything will start working16:42
naccbdmurray: ah and the new report was a fresh install; so may be a false positive?16:43
juliankcyphermox: why do you ask?16:43
bdmurraynacc: Okay, I've overridden the increased rate so it should continue phasing.16:44
naccbdmurray: thank you very much16:45
cyphermoxjuliank: I'd like to get code review for a change to the apport magic for failed package installs16:45
cyphermoxjuliank: somehow it doesn't feel like it applies to Debian so much16:46
bdmurraycyphermox: which magic?16:46
juliankcyphermox: I see. Well, we still keep it all in one place16:46
juliankcyphermox: Feel free to open a pull request for https://github.com/Debian/apt, https://github.com/julian-klode/apt ; or send a patch16:47
cyphermoxbdmurray: making sure we can get the proper /var/log/apt/term.log when package installs fail in the uniquity environment16:47
bdmurraycyphermox: is that part of apt?16:48
juliankI can merge pull requests *really* fast16:48
cyphermoxyeah, the code that writes the apport report is directly in apt16:48
* bdmurray rereads package install fails in ubiquity16:49
juliankcyphermox: I plan for a new APT release next week (final 1.3 pre-release)16:49
juliankThat will get a ton of crazy installation ordering changes...16:50
juliankHuge potential to reduce issues and improve speed16:50
juliankand socks5 proxy support16:51
juliankand tor support16:51
juliank(not that I did any of those)16:51
cyphermoxbdmurray: basically, we noticed that some shim-signed failures to install in the live image would include the live session's /var/log/apt/term.log rather than the one in /target... at least that's how things look to me, given that there are important bits missing16:52
cyphermoxjuliank: essentially: http://paste.ubuntu.com/22330893/16:52
cyphermoxit's very crude :)16:53
juliankYes. very.16:53
cyphermox:)16:53
juliankcyphermox: But looks OK. Put it in a git commit and push it somewhere/open a pull request/send in an email16:55
cyphermoxack16:55
cyphermoxI'm going to do a bit more testing on it and send you a pull request16:55
naccslangasek: i've gotten some feedback that dep3changelog using 'Closes LP: #' is not correct (that it's intended for Debian bugs only). Given you wrote dep3changelog, do you have a strong opinion?17:07
slangaseknacc: feedback from whom?17:10
naccslangasek: rbasak mostly :)17:10
slangasekand "intended for Debian bugs only" - what part?17:10
naccslangasek: i think rbasak means that 'Closes' generally is for Debian bugs only? So 'Closes LP: #...' is confusing? Rather than just using 'LP: #...' or '(LP: #...)'17:11
slangasekok17:12
slangasekso the only part I think is confusing is that we currently write 'Closes: LP: ####'17:13
slangasekthe extra colon looks weird17:13
slangasekbut 'Closes LP: ####' has always been in use, even if not by everyone17:13
naccslangasek: and actually dep3changelog for only a lpbug doesn't insert the extra colon17:13
slangasekah? then I think it all works as intended ;)17:14
nacchttps://code.launchpad.net/~nacc/ubuntu/+source/qemu/+git/qemu/+merge/300114, the diff comments, is specifically what I mean17:14
nacche's mentioned it a few times elsewhere as well17:14
naccjust trying to be correct and consistent17:14
rbasakHmm. I've never seen "Closes: LP:" nor "Closes LP:" used before. But if slangasek says it's normal, then I suppose that's OK :)17:28
naccrbasak: sorry, i should probably have directed that to you -- I was just reviewing what dep3changelog did internally and realized slangasek owned it17:28
rbasakI favour tight consistency though. Easier to ramp up newcomers then.17:28
rbasaknacc: np. I didn't realise that was coming from a tool.17:28
naccrbasak: agreed. I just think using a tool is the most consistent (to me)17:29
naccrbasak: because now, I don't handwrite my changelog entries from my patches, i just run `dep3changelog` on the patches17:29
rbasakAgreed - if it needs fixing, the tool should be fixed. Otherwise using its default output should always be OK. I just didn't know about the tool, and had never seen that style used anywhere else.17:29
rbasakI would prefer a single style to be agreed upon as the standard to teach newcomers, and then have every tool use it.17:30
nacc100% agreed17:31
jbichait's more common to omit the Closes for LP bugs17:35
juliankWhat's goingon in -fstack-protector-strong?17:49
juliankhttps://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/160874417:49
ubottuLaunchpad bug 1608744 in ndiswrapper (Ubuntu) "ndiswrapper-dkms 1.59-2: ndiswrapper kernel module failed to build" [Undecided,New]17:50
juliankstupid copy paste pasted wrong thing ...17:50
juliankCannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler17:50
juliankgcc: error: unrecognized command line option ‘-fstack-protector-strong’17:50
juliankAh, I see. Somehow the system compiles the module for the kernel with gcc 4.817:51
juliankbut that's trusty, so it makes sense17:51
Unit193In the firefox changelog: remove ebian/patches/webapprt-support-for-langpacks.patch  I was amused. :)19:50
naccrbasak: i wonder if at least part of the solution to LP: #1597414 is to just trust the publishing history unconditionally. If it says the version goes backward, let it, but warn?21:28
ubottuLaunchpad bug 1597414 in usd-importer "isc-dhcp cannot be imported" [Undecided,New] https://launchpad.net/bugs/159741421:28
naccor maybe we could add a flag?21:28

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