[01:23] <darkxst> bdmurray, I can take a look now, or are you already on it?
[01:40] <bdmurray> darkxst: I've uploaded a fix now.
[02:06] <darkxst> bdmurray, ok thanks
[10:00] <alexlist> https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1571166
[10:05] <infinity> alexlist: That's not the version in 16.04, so a curious report already. :P
[10:05] <infinity> alexlist: Can you attach the apt term log from the upgrade?
[10:55] <alexlist> infinity: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1571174
[11:01] <infinity> alexlist: Can you try upgrading ufw first, on a hunch?
[11:02] <infinity> alexlist: I might need to do some fiddling to force upgrade order there.
[11:03] <alexlist> infinity: you mean manually installing the xenial ufw on a wily box? Sure, can try...
[11:13] <xpheres> hello, I'm trying to create a scope from ubuntu sdk, however there are no virtual device to do it and I can not add an armdevice to qt
[11:13] <xpheres> anyone knows why this happens?
[13:24] <ogra_> hmm, vlc upnp support seems broken in xenial
[13:39] <r1nuz> Question, i'm trying to read eglibc code. If I get it using apt-get source eglibc it will be automatically patched to the way it's used in ubuntu, correct?
[13:40] <r1nuz> Also, if I wanted to find what build configuration is used in the actual distributed version, where could I find that?
[14:41] <alexlist> infinity: http://pastebin.ubuntu.com/15873401/ -> started ubuntu 15.10 in privileged docker container, installed squid-deb-proxy and ufw, installed ubuntu-release-upgrader-core, installed xenial ufw, ran release upgrade without issues. Will amend bug report.
[14:42]  * ogra_ files bug 1571199 
[14:54] <xpheres>   p, li { white-space: pre-wrap; }  Starting /usr/bin/ubuntu-html5-app-launcher... Setting import path to:   [0416/165255:FATAL:setuid_sandbox_client.cc(126)] Check failed: IsFileSystemAccessDenied().
[14:54] <xpheres> why?
[16:08] <tumbleweed> r1nuz: yes. The build configuration is what you see in the package
[16:09] <r1nuz> tumbleweed: thanks, so when i run make without ./configure first it should build the way it's distributed?
[16:09] <r1nuz> because when i try, i get:
[16:09] <r1nuz> $ make
[16:09] <r1nuz> Makeconfig:42: *** missing separator.  Stop.
[16:09] <tumbleweed> r1nuz: when you run dpkg-buildpackage -B
[16:09] <tumbleweed> (on the same ubuntu release)
[16:11] <r1nuz> tumbleweed: awesome, thanks :)
[16:11] <r1nuz> will that also create the proper Makefile btw?
[16:11] <r1nuz> guess i should read the dpkg manpage
[16:12] <r1nuz> (what i secretly really want is the appropriate Makefile config so that i can use unifdef to make the libc sources more readable but consistent with my distro)
[16:14] <tumbleweed> I have no experience in the eglibc package, but I'd expect it to be a little complex and weird
[16:14] <cjwatson> r1nuz: debian/rules is the entry point for the packaged build system.  And what tumbleweed says
[16:14] <r1nuz> tumbleweed cjwatson thanks
[16:14] <r1nuz> looks like dpkg-buildflags might be what i want
[16:14] <cjwatson> no
[16:14] <cjwatson> what I said is what you want
[16:14] <cjwatson> dpkg-buildflags is a small piece
[16:15] <cjwatson> that's generic distribution-wide flags basically, not package-specific changes, of which I'm sure glibc has many
[16:15] <cjwatson> if you want to understand an Ubuntu (or Debian) source package, start with debian/rules
[16:15] <r1nuz> oh debian/rules file, i see
[16:15] <r1nuz> thanks
[16:16] <r1nuz> appreciate it
[16:16] <cjwatson> you'll have to chase up a lot of references from there
[16:16] <r1nuz> ah well, i enjoy a good rabbithole :)
[16:16] <cjwatson> but normally at least the set of configure flags and such is in there
[16:16] <cjwatson> (I think in glibc's case it may actually be in an included makefile under debian/rules ...)
[16:16] <tumbleweed> the best might be to build it and read the build log (or just read the log for the most recent ubuntu build)
[16:17] <r1nuz> where could i find that latter log? for the most recent build?
[16:18] <tumbleweed> https://launchpad.net/ubuntu/+source/eglibc
[16:18] <r1nuz> thanks
[16:18] <tumbleweed> follow the links through to a version, and then an architecture
[16:19] <cjwatson> and note that Ubuntu switched back to glibc after 14.04, so if you're based on anything newer than that then you want https://launchpad.net/ubuntu/+source/glibc instead
[16:21] <r1nuz> ah good to know, still on 14.04 for this machine
[17:50] <ShalokShalom_> hi there :)
[17:51] <ShalokShalom_> is it true, that snappy is something like the Google Play Store?
[17:51] <ShalokShalom_> no mirrors anymore?
[17:51] <ShalokShalom_> no forks?
[17:53] <teward> ShalokShalom: https://developer.ubuntu.com/en/snappy/#tour <-- start here?
[17:54] <teward> !crosspost | ShalokShalom
[17:54] <ShalokShalom> i post in each related room
[17:54] <ShalokShalom> some people are just in one room and i aim to reach them as well
[17:54] <teward> it's better to pick one room, ask, and if nobody answers in 15 minutes, try another one.
[17:55] <teward> rather than just post in every room at once
[17:57] <ShalokShalom> teward: why do you link me a post, which doesnt answer my questions?
[17:57] <ShalokShalom> this page shows only the pros
[21:55] <Umeaboy> Hi!
[21:57] <Umeaboy> I keep forgetting the answer, the installer terminal output can be translated WHERE?
[21:57] <Umeaboy> The terminal like window that appears when you click the arrow when the installation starts.
[21:58] <Umeaboy> I hope someone knows what I mean.
[21:58] <Umeaboy> I want to translate it more.
[21:58] <Umeaboy> I searched for bash, but that seems to be fully translated now.
[21:59] <Umeaboy> Should I check with ubiquity?
[22:19] <infinity> Umeaboy: That output is intentionally not translated so that bug reports are readable by the developers.
[22:23] <Umeaboy> OK.
[22:23] <Umeaboy> infinity: What about when you install updates in the terminal window then?
[23:14] <cyphermox> Umeaboy: it can't be translated anywhere special, that's just the output from whatever gets run as part of the install, mostly debug information for the developers as infinity pointed out
[23:14] <cyphermox> you'll see some pieces *are* translated, those are the ones that would be translated on the installed system, from commands an user would run and care about
[23:14] <cyphermox> ie. "Installing $package" or "Preparing to unpack $package"
[23:15] <cyphermox> we translate the "high level" messages that show just above the terminal window so users still know what is happening
[23:17] <Umeaboy> OK.
[23:31] <Umeaboy> cyphermox: What parts of Ubuntu are need to be more translated? I wish launchpad only would show me the stuff that needs to be translated and hide thoose that are finished.
[23:32] <Umeaboy> It currently can't.
[23:32] <Umeaboy> At least I haven't found a way to do so.
[23:33] <cyphermox> I don't know off hand. You would have to look at https://translations.launchpad.net/ubuntu/ which will display the languages your launchpad page says you know, and then click on a langauge, that will show all the different bits and pieces
[23:33] <cyphermox> from there you dig in in the fourth column which is "untranslated", sometimes there are numbers there
[23:33] <cyphermox> for example, if you scroll to the bottom of https://translations.launchpad.net/ubuntu/xenial/+lang/es
[23:34] <cyphermox> there are four untranslated strings for gnome-software and also four for nm-applet
[23:36] <cyphermox> we're past the translation deadlines though, so your work may only go in later
[23:58] <Umeaboy> cyphermox: OK so Xenial is about to be released now?
[23:59] <dax> thursday