[04:37] <dupingping> hi, developers, please look here, https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1514288
[07:54] <dholbach> good morning
[09:23] <Odd_Bloke> infinity: I now have access to 1SS, so I'm ready for you to give me somewhere to play with powerpc cloud images. :)
[09:39] <dupingping> https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1514288
[09:48] <LocutusOfBorg1> mdeslaur, how do you feel about a sync of tar?
[09:48] <LocutusOfBorg1> after dinstall of course
[11:09] <alex__> hello what is the right irc channel to ask about building unity?
[11:13] <brendand> alex__, here is fine
[11:13] <brendand> alex__, but ask your question in as much detail as possible rather than asking to ask
[11:14] <brendand> alex__, like 'i get this <pastebin> failure when building unity from lp:unity on <distro>'
[11:15] <alex__> ok thanks. I have to build some parts of unity because we in gnustep are working to integrate gnustep apps as better as we can. So with this command "make panel"  the panel got compilet but at launch time I got
[11:16] <alex__> ERROR 2015-11-09 12:15:44 nux.gltexture.resource.manager GLTextureResourceManager.cpp:54 Invalid target, impossible to generate a new texture. Impossible to generate a pixbuf: Failed to open file '/home/alex/test_unity/share/unity/icons/dash_noise.png': File o directory not found and similar errors
[11:17] <alex__> also, how to install compiled stuff in a customized directory? following the HACKING file seems to not work
[11:21] <alex__> -- Up-to-date: /home/alex/test_unity/share/locale/de/LC_MESSAGES/unity.mo
[11:21] <alex__> -- Installing: /usr/share/glib-2.0/schemas/com.canonical.Unity.gschema.xml
[11:21] <alex__> CMake Error at cmake_install.cmake:168 (file):
[11:21] <alex__>   file INSTALL cannot copy file
[11:21] <alex__>   "/home/alex/Scaricati/unity-7.3.3/com.canonical.Unity.gschema.xml" to
[11:21] <alex__>   "/usr/share/glib-2.0/schemas/com.canonical.Unity.gschema.xml".
[11:23] <alex__> The distro is Uubntu 15.10 and I'm using the released source code of unity 7.3.3, the tarball on launchpad
[11:23] <brendand> alex__, you did 'mkdir build; cd build; CMAKE -DCMAKE_INSTALL_PREFIX=~/staging ../'?
[11:23] <alex__> yes, but insread of staging I used test_unity
[11:23] <brendand> bleurgh, and cmake should be lowercase
[11:24] <alex__> and yes I used a lowercase cmake command
[11:24] <brendand> alex__, what gave you the error? make or cmake?
[11:24] <brendand> alex__, did you do apt-get build-dep unity?
[11:25] <alex__> yes to build-dep, I don't have error while buidling panel, but running it. The build has success
[11:26] <alex__> brendand, this is the command I run cmake -DCMAKE_INSTALL_PREFIX=~/test_unity ../
[11:27] <alex__> then, make -j8 has success
[11:27] <alex__> make -j8 panel sorry
[11:29] <alex__> brendand, just rebuilt
[11:29] <alex__> Linking CXX static library libunity-shared-standalone.a
[11:29] <alex__> [100%] Built target unity-shared-standalone
[11:29] <alex__> Linking CXX static library libpanel-lib.a
[11:29] <alex__> [100%] Built target panel-lib
[11:29] <alex__> Linking CXX static library libunity-shared-bamf.a
[11:29] <alex__> [100%] Built target unity-shared-bamf
[11:29] <alex__> Scanning dependencies of target panel
[11:29] <alex__> [100%] Building CXX object panel/CMakeFiles/panel.dir/StandalonePanel.cpp.o
[11:29] <alex__> Linking CXX executable panel
[11:29] <alex__> [100%] Built target panel
[11:29] <alex__> no errors, but if I try to run it... I got the previous errors
[11:35] <brendand> alex__, i would doubt that building part of it will work
[11:36] <brendand> alex__, you would have to build it all, then make panel would work to rebuild just the panel bits if that's all you changed
[11:54] <alex__> brendand, ah ok, so it works in this way, understoo. I go to rebuild all
[11:54] <sladen> directhex: ta
[11:55] <directhex> hm?
[12:04] <alex__> brendand, ok Ibuilt every think and succesfully. Now I want to install everything in my customized directory
[12:05] <brendand> alex_ - make install should work?
[12:10] <mdeslaur> LocutusOfBorg1: how do I feel about a sync that would revert the ftbfs fix? Is that what you're asking me?
[12:10] <nikow> .win 21
[12:10] <nikow> woops, sorry
[12:13] <Slex1> seems I lost the xchat window. I should not use anymore xchat. I was alex__
[12:14] <alex__> brendand, I hope
[12:15] <alex__> brendand, it fails here:
[12:15] <alex__> CMake Error at cmake_install.cmake:168 (file):
[12:15] <alex__>   file INSTALL cannot copy file
[12:15] <alex__>   "/home/alex/Scaricati/unity-7.3.3/com.canonical.Unity.gschema.xml" to
[12:15] <alex__>   "/usr/share/glib-2.0/schemas/com.canonical.Unity.gschema.xml".
[12:16] <alex__> I think the reason is that it wants root permission. Why it don't install that .xm file in my custom dir?
[12:16] <alex__> xml*
[12:18] <directhex> sladen: don't thank me yet, i have Plans(tm) for OpenBVE. evil plans
[12:23] <Slex1> time to go, woth both account Slex and alex__ see you soon and thanks dor the help
[12:28] <mdeslaur> LocutusOfBorg1: oh! I see the -2.1 version now. Sure, sync it.
[13:03] <LocutusOfBorg1> exactly mdeslaur :)
[13:04] <mdeslaur> LocutusOfBorg1: I need to wait until I've had more coffee before responding to people in the morning :P
[13:05] <LocutusOfBorg1> me too :)
[13:34] <utlemming> pitti: did the behavior of "nofail" in /etc/fstab change with 15.10?
[13:35] <utlemming> pitti: I'm seeing an issue where "nofail" file systems that fail to mount on boot is resulting in a system going into emergency mode instead of continuing to boot. On 15.04 the option results in the system continuing to boot.
[14:36] <mbiebl> utlemming: can you pastebin the output of systemctl status foo.mount and systemctl show foo.mount
[14:53] <utlemming> mbiebl: sure
[14:54] <utlemming> mbiebl: http://paste.ubuntu.com/13209036/
[14:55] <mbiebl> utlemming: hm, that's not what I asked for
[14:55] <mbiebl> can you run systemctl status and show for the failed mnt.mount unit?
[14:56] <utlemming> mbiebl: oh, sorry...let me see if I can get to a system. This a remote headless system in the cloud.
[15:00] <mbiebl> utlemming: oh, and sharing your /etc/fstab would help as well
[15:02] <utlemming> mbiebl: http://paste.ubuntu.com/13209069/
[15:03] <mbiebl> utlemming: ah
[15:03] <mbiebl> nobootwait != nofail
[15:03] <mbiebl> I think that Ubuntu specific fallback has been removed
[15:05] <utlemming> mbiebl: oh, really? you wouldn't happen to have the bug/commit where that change happened?
[15:06] <mbiebl> https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu&id=8fbf6c7e671c663190eae8a63b158e686c3d41fa
[15:08] <mbiebl> utlemming: so either the migration code is buggy or you added the fstab entry using nobootwait *after* the upgrade
[15:09] <utlemming> mbiebl: the nobootwait was added by cloud-init at first boot. Then the system snapshoted and launched as a new instance.
[15:10] <utlemming> mbiebl: no upgrade, wily native
[15:10] <utlemming> mbiebl: it works just fine with 15.04
[15:17] <nemo> So, I ran into a very confusing launchpad issue when trying to figure out the vmware-view smartcard authentication using vmware-view-open-client 4.5 package
[15:17] <nemo> https://bugs.launchpad.net/ubuntu/+source/vmware-view-client/+bug/1268770
[15:17] <nemo> it was filed almost 2 years ago, and suggested a rather convoluted fix
[15:17] <mbiebl> utlemming: please file a bug against cloud-init!
[15:18] <utlemming> mbiebl: ack...should it be using nofail then?
[15:18] <nemo> both (a) and (b) seem to boil down to "custom build of OpenSC"
[15:18] <mbiebl> utlemming: yeah
[15:18] <utlemming> mbiebl: thanks, will do
[15:18] <nemo> anyway. looks like vmware view open client is broken in ubuntu packaging - at least for smartcard auth, which is an increasingly common use-case (and non-optional here)
[15:19] <nemo> gonna try that custom opensc build, but was hoping maybe there was some magic PPA or something ☺
[17:32] <pgquiles> does ubuntu/canonical provide any facility to store specialized ubuntu flavors?
[17:33] <pgquiles> translated into something meaningful: I've created an ISO of Wily with better support for Bay Trail-based computers and I cannot host 1.2 GB on my server without my ISP killing me
[17:34] <pgquiles> (new drivers, kernel 4.3 with a few patches, etc)
[17:35] <jpds> Is there a reason you can't use the hardware enablement stack?
[17:35] <jpds> pgquiles: https://wiki.ubuntu.com/Kernel/LTSEnablementStack
[17:39] <pgquiles> jpds: multiple reasons: current ubuntu images won't boot on bay trail, so it's a bad start. Also my kernel includes a couple of patches of my own to get the nvram from uefi on broadcom network/bluetooth devices and to fix the clocksource. For the rest, the new drivers are packaged in my PPA.
[17:40] <pgquiles> none of that is available from the LTS Enablement Stack, which is great otherwise
[18:11] <cyphermox> pgquiles: I think if booting on bay trail is the only requirement (for example, there aren't different packages you need for this and that aside from bay trail support), then you should ask on ubuntu-devel for an image that has the right kernel and bootloader bits. I'm not sure yet how we'd do to support that though
[18:11] <cyphermox> what changes are you making to the stock image?
[19:05] <pgquiles> cyphermox: speaking off the top of my head 32-bit efi loader, kernel 4.3 on wily with a couple of patches for better clock resolution and downloading the nvram in brcmfmac (instead of providing it as a device-specific .txt file), qf9700 driver, rtl8723bs drivers (wifi and bluetooth) and probably something else
[19:05] <cyphermox> right, so bootloader and kernel
[19:06] <pgquiles> the 32-bit efi is lp #1341944 and  lp #1025555
[19:08] <pgquiles> the drivers are dkms-enabled packages, actually. Problem is if you don't have a network connection (which is what these drivers provide), you cannot install them from a PPA :-|
[19:21] <pgquiles> cyphermox: oh, also new linux-firmware snapshot from kernel.org and new broadcom-sta proprietary driver (wl.ko)
[19:22] <cyphermox> pgquiles: I can't really comment on kernel specifics, since I'm not really involved in doing kernel work
[19:29] <pgquiles> cyphermox: I see. My question was more about hosting the ISO somewhere "decent" instead of using mega or alike.
[19:29] <cyphermox> sure, but to do that we need to have the right things in the archive already.
[19:34] <pgquiles> cyphermox: what do you mean? I'm not talking about an official ISO :-?
[19:49] <smoser> pitti, are you around ?
[19:49] <smoser> wonder if anyone else can help. i'm looking at open-iscsi and initramfs.
[19:51] <smoser> in ubuntu, we have for quite some time had https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/728088
[19:51] <smoser> basically something that stops the network device upon which the iscsi root is attached from getting bounced.
[19:51] <smoser> but debian doesn't seem to have anything like that.
[19:51] <smoser> and i'm wondering how that is possible
[19:53] <josepht> smoser: afaik there's an issue with open-iscsi and systemd
[19:53] <smoser> in ubuntu ? or in debian
[19:53] <smoser> also, it looks (this is my first look at it) that there might be a systemd-initramfs path in debian
[19:55] <josepht> smoser: I was looking at bug 1465196, but haven't made much progress yet
[19:55] <smoser> that must be dracut (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787553)
[20:04] <smoser> is debian moving away from initramfs-tools and towards dracut ?
[21:04] <smoser> hm... wondering outloud.
[21:04] <smoser> should /etc/udev/rules.d/70-persistent-net.rules be in the initramfs ? if ip= is used, and network devicews are kept up (iscsi root) it would seem maybe it should