[02:16] <seyeongkim> I found that the problem with "-Wl,-Bsymbolic-functions" option in autofs pkg. the other pkgs have no problem with this? https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1470687
[06:46] <dholbach> good morning
[08:05] <Saviq> seb128, any idea where to file a bug about Compose not working?
[08:05] <Saviq> actually /me tries in a guest account
[08:08] <Saviq> crap, works in a guest account, wonder what breaks it in mine
[08:09] <seb128> Saviq, not really, did you try to force set manually using setxkbmap?
[08:09] <seb128> hum, so likely user config issue...
[08:09] <Saviq> seb128, yeah, xev reports Multi_key correctly
[08:09] <Saviq> but chars get typed in as usual regarless
[08:09] <Saviq> +d
[08:10]  * Saviq was thinking about busting $HOME, maybe it's time...
[08:14] <Saviq> would be good to find the problem in any case...
[09:01] <jamespage> wgrant, cjwatson: I've had a few packages in 14.04 main highlighted to me with "Supported: 9m" - is that a bug of some description?
[09:06] <cjwatson> jamespage: That appears to be deliberate in the code for things that are merely in some ordinary kind of supported seed (or an extra binary that's just built from the same source as something seeded) rather than in something that's a child of {server-ship, supported-server, ship, supported-desktop, supported-desktop-extra}
[09:07] <jamespage> cjwatson, ok - let me dig further
[09:16] <jamespage> cjwatson, interestingly the first on the list is cliff-tablib - its a used for testing python-neutronclient so is a BD only
[09:16] <cjwatson> Right, supportedness is pretty irrelevant there.
[09:16] <cjwatson> We can't really fix this after the fact anyway :)
[09:24] <jamespage> cjwatson, yeah - I gave the message back that this was not a problem
[09:24] <jamespage> cjwatson, I've never seen anyone pick through those fields before :-)
[10:44] <doko> jamespage, could you have a look at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777814 ?
[10:45] <jamespage> doko, yes
[10:45] <doko> ta
[11:56] <seb128> wgrant, dpm, pitti: what's the status of langpacks in wily? are translations open? can we get exports?
[12:40] <dpm> hi seb128, I've not done anything with wily translations myself, let me ping the LP folks to see if the imports are set up before opening translations
[12:44] <seb128> dpm, yeah, that's why I included wgrant in the ping ;-)
[12:44] <seb128> but I guess cjwatson might know as well
[12:47] <pitti> seb128: nothing yet on https://translations.launchpad.net/ubuntu/wily/+language-packs :(
[12:47] <dpm> seb128, ah, yes, didn't notice. I asked Colin on #launchpad in the meantime
[12:49]  * seb128 joins launchpad
[13:26] <rbasak> I think I've finally pinned down an elusive bug.
[13:26] <rbasak> logger(1) closes stdin if no log daemon is running, although only when not running systemd (presumably that listens to /dev/log or whatever)
[13:27] <rbasak> mysql-server-5.6.postinst pipes various bootstrap commands to logger.
[13:27] <rbasak> The bootstrap commands do not work when their stdout is closed, leading to future failure.
[13:28] <rbasak> Is this a bug in logger, which should instead silently throw away stdin instead of closing it and exiting 0 or something, or a bug in the mysql bootstrap commands which should succeed even if they get stdout closed on them?
[13:29] <rbasak> POSIX doesn't seem to have anything to say about this.
[13:29] <rbasak> Though it doesn't define the stdin use at all, so the fact that we're using logger's stdin at all is an extension to POSIX.
[13:48] <jamespage> doko, hey - can we run that against the ceph in experimental?
[13:49] <jamespage> that being gcc-5
[13:49] <doko> jamespage, not automagically
[13:50] <jamespage> doko, I'll look to fix in 0.94.2
[14:30] <wgrant> dpm, pitti, seb128: wily translations aren't copied yet. I can arrange that tomorrow.
[14:30] <dpm> awesome, thanks wgrant
[14:30] <seb128> wgrant, that would be nice, thanks
[14:58] <pitti> bdmurray: http://d-jenkins.ubuntu-ci:8080/job/wily-adt-python3.5/?
[15:00] <bdmurray> pitti: hmm?
[15:00] <pitti> bdmurray: sorry, that was meant for barry
[15:00] <pitti> bdmurray: I guess I saw you come into mumble and my brain somehow failed
[15:01] <barry> pitti: dang, my vpn isn't up atm
[15:04] <pitti> barry: same on public jenkins :)
[15:08] <unixpro1970> can anyone recommend a free source code call flow viewer for c/c++ code for linux? Something like this https://scitools.com/
[15:58] <pitti> slangasek, infinity: I'd appreciate a review on https://code.launchpad.net/~pitti/britney/britney2-ubuntu-amqp/+merge/263679
[16:05] <pitti> barry: \o/ http://autopkgtest.ubuntu.com/packages/p/python3.4/wily/i386/
[16:06] <pitti> barry: (2.7 and 3.5 had some tmpfail due to cloud limits, I'll work on those)
[16:09] <barry> pitti: \o/
[16:16]  * pitti waves good night
[16:22] <Laney> stgraber: any chance you can look into why the tracker isn't cancelling the re-build status for failed desktop-next builds? (also cancelling them from the tracker doesn't stick either)
[16:37] <ogra_> Laney, i dont think it ever did
[16:37] <stgraber> Laney: did you try canceling from nusakan?
[16:38] <Laney> stgraber: I did, it works
[16:38] <stgraber> Laney: you can only cancel from the tracker in the first few minutes, once nusakan acknowledges the build, it can't be canceled anymore
[16:40] <Odd_Bloke> Does anyone know the status of getting a more recent pip in to Debian/wily?
[16:40] <Odd_Bloke> (barry?)
[16:42] <Laney> stgraber: right, so that part isn't a bug then but I suppose that not noticing the build failed and clearing the state is
[16:47] <bdmurray> rbasak: If you run apt-get update, then does apt-cache policy show different information in the Version table?
[16:48] <stgraber> Laney: yeah, on failure the cdimage code on nusakan is supposed to set the state as failed
[20:06] <odell> So what's the best way to get into developing for Ubuntu?
[20:40] <tjaalton> should the installer know how to resize nvme partitions?
[20:40] <tjaalton> I got a machine with windows preinstalled and would like to keep it, but the only option on the installer seems to be to wipe it out
[20:47] <tjaalton> oh well, shrunk the ntfs volume from win10
[21:26] <rbasak> bdmurray: no, but apt-get update largely fails because of the read-only filesystem and some 404 errors.
[21:26] <rbasak> bdmurray: I want to keep this phone on stable and image-based updates and I don't really understand the implications of remounting read-write.
[21:27] <bdmurray> rbasak: sorry, I sorted it out.
[21:39] <rbasak> bdmurray: np. Thank you for looking!
[23:00] <odell> exit