[00:00] <teward> jgrimm: powersj: https://wiki.ubuntu.com/ServerTeam/NGINX, for your perusal, complete with a lot of anchors for fast-linking to things
[00:00] <teward> nacc: you suggested adding this to the Triage page, it'll go under ServerTeam/NGINX with a link to the anchor, that should work right?
[00:03] <powersj> teward: dang!
[00:03] <nacc> teward: yeah, i think so
[00:04] <trippeh> (just a random remark regarding the wiki page), nginx aio seems to work better these days. it was very unstable before.
[00:06] <teward> trippeh: it's still not enabled, and until it's proven otherwise to work without issue in all the modules shipped, I'm not enabling it
[00:07] <teward> you're right, it works 'better', but with third-party modules it fubars debugging still, according to my contact in Debian.
[00:07] <teward> powersj: yes, I write a lot sometimes.  WIth 30 minutes of bull-crap going on in my course right now, I kinda focused on the wiki page :P
[00:07] <trippeh> oh. no idea about third-party modules.
[00:07] <teward> problems?
[00:08] <teward> trippeh: indeed.  nginx-core is the only one that it'd not effect, nginx-light, nginx-extras, nginx-full, libnginx-* for modules not from NGINX upstream code tarballs/repositories are all going to be Universe and have third-party modules
[00:08] <teward> (once i do the merge)
[00:11] <teward> powersj: nacc: feel free to use this tazer on me if you think I overdid it.
[00:11] <teward> *hands powersj and nacc each a taser*
[00:11] <rbasak> teward: I'm not sure of the background, but that wiki page looks really useful. Thanks!
[00:11] <teward> those four special-cases are evil and have special handling.
[00:11] <teward> rbasak: multiple triage difference procedures
[00:11] <teward> for certain cases
[00:12] <teward> I called out powersj earlier for one case
[00:12] <teward> i updated the DebuggingServer comments.  Then I decided to document all this in a page.
[00:12] <teward> And then some.
[00:12] <teward> (I have no life lol)
[00:14] <rbasak> teward: I think you're setting a great example here. We should have one of these pages for every package :-)
[00:14]  * rbasak disappears to bed
[01:22] <axisys> trying to boot a system for the first time and forgot to build the lun with raid controller.. so trying to install ubuntu 14.04 server iso, it got stuck at no root file system and realized I did not build a lun yet.. so on next boot I could not catch the part where I will build the run and it went through and stuck at .. "Welcome to GRUB! error: no such device: HPEZCD240." any suggestion how I got
[01:23] <axisys> that error? need to call the site tomorrow, to reboot and try to build the lun through raid controller..
[01:24] <axisys> "..could not catch the raid configuration part and it went.."
[06:04] <stanford_ai> when I sudo su otheruser, then run cheese, I get (cheese:9920): Gdk-ERROR **: error: XDG_RUNTIME_DIR not set in the environment.
[06:05] <lynorian> stanford_ai, firstoff if you know that users password you do not have to use sudo
[06:05] <stanford_ai> lynorian, how do I do it?
[06:06] <lynorian> su otherusername
[06:06] <stanford_ai> oh I got it
[06:06] <stanford_ai> thanks! and about the video?
[06:06] <lynorian> then need to use xhosts
[06:06] <stanford_ai> how?
[06:06] <lynorian> I think that is the command I should check the man page
[06:06] <stanford_ai> xhost. but what am i supposed to do with it?
[06:07] <lynorian> xhost +otheruser
[06:07] <lynorian> allows otheruser to run X applications when you are logged into X
[06:07] <lynorian> although this seems more like a #ubuntu question
[06:07] <stanford_ai> i did that. still: ** (cheese:11599): WARNING **: Could not open X display
[06:08] <lynorian> ah you need to be in X11 to run cheese
[06:08] <lynorian> your server has a webcam?
[06:09] <lynorian> cheese is an x11 desktop application
[06:09] <sarnold> just ssh -X in and skip all that horrible X stuff
[06:09] <stanford_ai> it's not a server. it's my laptop
[06:09] <stanford_ai> I don't wanna use my own user to let others ssh in and work on it
[06:09] <stanford_ai> but i need to run stuff in this laptop
[06:10] <stanford_ai> they ssh in to another user
[06:10] <stanford_ai> and I su otheruser to work with them
[06:10] <stanford_ai> it all needs to be in the home directory
[06:10] <stanford_ai> but I can't run cheese from that user apparently. any ideas?
[06:14] <JanC> why would you need cheese on a server anyway?
[06:15] <stanford_ai> it's not a server. it's my laptop.
[06:30] <cpaelzer> stanford_ai: I'd agree with sarnold, ssh -X in which will set up the env for X forwarding as you need it
[06:38] <stanford_ai> cpaelzer, awesome. that works. what's the difference between -Y and -X ?
[06:39] <sarnold> I think in debian and ubuntu they're patched to be identical
[06:49] <nikeshm> how can we change iscsi initiator name in ubuntu 16.04
[06:49] <nikeshm> i changed /etc/iscsi/initiatorname.iscsi and restart the service but then i am not able to see the target LUN
[07:00] <nikeshm> ?
[07:01] <sarnold> did you log in to the target again?
[07:12] <nikeshm> sarnold: its worked with ubuntu 14.04
[07:13] <nikeshm> yes i logged in again
[07:13] <nikeshm> and log in was successful
[07:13] <nikeshm> but only lun 0 is visible
[07:13] <nikeshm> not other luns
[07:17] <nikeshm> sarnold: i restarted open-iscsi after changing /etc/iscsi/initiatorname.iscsi
[07:19] <sarnold> nikeshm: are there any errors in dmesg? logs? journalctl output?
[09:18] <jamespage> coreycb, zul: we might have to include libseccomp in the UCA for ocata - ppc64el build failure in proposed for qemu lookslike it needs >= 2.3.0
[09:19] <jamespage> cpaelzer, ^^ does that sound right?
[09:26] <jamespage> zul, hmm
[09:26] <jamespage>  sbuild-build-depends-nova-lxd-dummy : Depends: python-sphinx (>= 1.5.1) but 1.3.6-2ubuntu1 is to be installed
[09:37] <cpaelzer> jamespage: seccomp got enabled for ppc this cycle yes - I don't know about the minimum version
[09:38] <jamespage> zul, coreycb: hey can we get a bump of networking-odl in for ocata please
[09:38] <cpaelzer> jamespage: should be libseccomp-dev (>> 2.1.0)
[09:39] <cpaelzer> that is the min the control file specifies
[09:39] <jamespage> cpaelzer, configure fails with "Install libseccomp devel >= 2.3.0" on ppc64el
[09:40] <jamespage> xenial has an older version
[09:40]  * jamespage ponders if seccomp is used inthe context of openstack anyway
[09:40] <cpaelzer> I found it
[09:40] <cpaelzer> yes on ppc 2.3
[09:41] <cpaelzer> "Support for ppc/ppc64 is official in libseccomp 2.3.0" that is from upstream
[09:42] <cpaelzer> that is actually a miss in the control file - the minimum version needs to be raised, thanks
[09:45] <nikeshm> sarnold: checking
[09:46] <nikeshm> is there any guidelines for how to change the initiator name without reboot in ubuntu 16.04
[09:46] <nikeshm> i am using open-iscsi
[09:54] <nikeshm> sarnold : no error in logs
[10:24] <nikeshm> any one faced the issue
[11:04] <zul> jamespage: ack on odl
[11:48] <nikeshm> sarnold: sudo iscsid restart is solving the issue
[13:57] <frickler> cpaelzer: seems like your strongswan upload is still hanging in the queue and the earlier ppa isn't available anymore, do you still have a working build somewhere or do I have to build it myself?
[13:58] <frickler> cpaelzer: regarding https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1587886 that is ;)
[14:00] <cpaelzer> frickler: my ppa is cleared as I expected the SRU to hit proposed rather soon
[14:00] <cpaelzer> frickler: the test I'd ask you to make needs it in proposed, you can't verify it before it is there
[14:02] <frickler> cpaelzer: yeah, but I'd need the package to fix some of my servers now. so I guess I'll have to build it myself, then ;)
[14:02] <cpaelzer> frickler: if you need an interim ppa for whatever reason I can quickly create one for you if that helps you
[14:02] <frickler> cpaelzer: that would be nice, yes, please
[14:03] <cpaelzer> frickler: x86 is ok, or do you need more arches?
[14:04] <frickler> cpaelzer: amd64 rather
[14:04] <cpaelzer> frickler: sure, that is what I meant
[14:04] <cpaelzer> frickler: sorry
[14:04] <cpaelzer> frickler: ok, I uploaded to https://launchpad.net/~paelzer/+archive/ubuntu/bug-1587886-strongswan-apparmor-disconnect
[14:05] <cpaelzer> frickler: and versioned it in  a way that it is superseded by the SRU once it is out
[14:05] <cpaelzer> building shortly
[14:05] <frickler> cpaelzer: great, thanks
[14:09] <jamespage> cpaelzer, just need to figure out whether to disable seccomp for the backport to the Ocata UCA, or backport seccomp as well
[14:10]  * jamespage ponders
[14:14] <cpaelzer> jamespage: just disable seccomp support for power that would be
[14:15] <cpaelzer> jamespage: the powerless arches work with the older seccomp
[14:15] <boichev> is this the right location to ask for openstack installed from cloud-archive:icehouse that I want to upgrade to Mitaka ?
[14:15] <cpaelzer> jamespage: arm would need 2.2 but that is not enabled for seccomp in qemu
[14:15] <jamespage> boichev, its as good as any :-)
[14:16] <boichev> :) So I am looking at the openstack support model on ubuntu and I am planning on how to upgrade an Icehouse release on 14.04 to something newer ....
[14:17] <boichev> I guess to go to Mitaka I need to stop all services on all nodes then upgrade to 16.04 and replace the cloud-archive repo and upgrade the openstack part....
[14:17] <boichev> But I can't find any documentation
[15:14] <EmilienM> coreycb, jamespage: quick info, you updated ocata packages, our CI works fine, zero issue until now.
[15:22] <jgrimm> rbasak,  did you perhaps want to chair irc today, to try out thoughts on how to lean on meetbot more for note taking?
[15:26] <rbasak> jgrimm: sure
[15:26] <jgrimm> rbasak, excellent thanks.  rharper you are off the hook for today ^^ ;)
[15:35] <jamespage> EmilienM, great news - thanks for the feedback!
[15:35] <EmilienM> cool, good work folks
[15:35] <jamespage> EmilienM, I have one non-x86 build failure to deal with and we'll promote to -updates
[15:35] <jamespage> boichev, sorry missed you response
[15:36] <EmilienM> jamespage: ack
[15:36] <EmilienM> mwhahaha: ^ fyi we might want to switch stable/ocata to it when it's updated
[15:36] <jamespage> boichev, the short answer is that you need to step through all of the Ubuntu cloud archive pockets for trusty - so that's juno, kilo, liberty, mitaka
[15:37] <jamespage> ensuring that you do the db migrations for each service on each step
[15:37] <jamespage> then you could do the upgrade from 14.04 -> 16.04 inplace but it will be disruptive
[15:38] <jamespage> you might want to consider a rolling upgrade approach, bringing up 16.04 based mitaka longside 14.04 mitaka, and then migrating services and instances
[15:40] <elliotd133> http://pastebin.com/iMiBe2U2
[15:40] <elliotd133> I set up bonding like that, but bonding doesn't appear to be active on reboot/ifup/down
[15:41] <elliotd133> ubuntu 14.04.5
[16:14] <mwhahaha> jamespage: we're seeing failures when we go to install mitaka keystone, http://logs.openstack.org/90/433290/4/check/gate-puppet-keystone-puppet-beaker-rspec-ubuntu-trusty/8620825/console.html#_2017-02-13_23_26_25_786080 thoughts?
[16:16] <frickler> elliotd133: instead of "slaves none" I'd rather use "bond-slaves p11p1 p11p2", not sure about the "bond-primary" lines, too
[16:19] <cpaelzer> nacc: thanks for accepting all tasks, I could clean those that were version specific - looks correct now
[16:19] <jamespage> mwhahaha, nothing springs to mind - keystone has not had an update since Tue, 27 Sep 2016 08:23:13 -0400
[16:20] <nacc> cpaelzer: yep
[16:20] <jamespage> mwhahaha, hmm
[16:20] <jamespage> /usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py
[16:20] <mwhahaha> jamespage: ok i'll keep digging, it seems to be a dep issue since it's failing when keystone-manage runs on the install
[16:20] <jamespage> ^^ might be something pip installed conflicting with the bits in the archive
[16:20] <jamespage> mwhahaha, ^^
[16:20] <mwhahaha> we don't pip install
[16:21] <mwhahaha> we're purely packaging
[16:21] <jamespage> mwhahaha, the puppet modules don't
[16:21] <jamespage> but something has installed into /usr/local on that gate machine
[16:22] <frickler> can we get an update of Horizon in Newton to 10.0.2, please? http://docs.openstack.org/releasenotes/horizon/newton.html#id1
[16:22] <mwhahaha> jamespage: hmm ok i'll take it up with infra then, thanks for the pointer
[16:22] <jamespage> mwhahaha, my best guess - I just checked a mitaka deployment I did earlier today and I don't see the same problem
[16:23] <jamespage> frickler, I think zul is working on some newton updates
[16:29] <frickler> jamespage: that would be great, thx.
[16:43] <axisys> booting a system using ubuntu iso and cannot install since raid controller is not configured yet to provision a disk.
[16:44] <axisys> any way to do that from busybox?
[16:44] <axisys> I exited to shell from the install
[16:44] <axisys> and at shell now
[16:49] <joelio> axisys: when you say raid controller, do you mean a hardware one as opposed to using mdadm?
[16:49] <joelio> if it's hardware, generally you'd configure that at POST (say a Dell PERC.. although you can do some via ipmi etc)
[16:50] <joelio> if it's software then it's a different tact and one you can defintely do with the 'server' install (alternate as it used to be known)
[17:01] <axisys> joelio: hardware
[17:02] <axisys> need to find out if I can configure a raid controller through serial port
[17:02] <axisys> this is HP DL360 gen9
[17:03] <axisys> ipmi has no IP yet.. plus doubt if we have license to take advantage of raid config through ipmi
[17:03] <axisys> ah.. did I mention no cable connected to the ipmi/iLO rj45 port.. so only connected now through serial port and it already has an IP ..
[17:03] <axisys> but disk is provisioned yet
[17:31] <elliotd133> frickler: Thanks, I tried bond-slaves originally under the bond0 interface and it did the same thing
[17:32] <elliotd133> frickler: The reason I have bond-primary lines is due to the documentation for bonding regarding upstart systems: https://www.kernel.org/doc/Documentation/networking/bonding.txt
[17:34] <patdk-wk> is there some way to force apt-get to install a package that conflicts with another package?
[17:34] <patdk-wk> want to test them both, alternately
[17:34] <nacc> patdk-wk: conflicts in what way?
[17:34] <nacc> patdk-wk: or which package(s)?
[17:34] <patdk-wk> nut vs apcupsd
[17:35] <patdk-wk> they don't really conflict, just the packages are marked that way so people don't do something stupid
[17:35] <nacc> hrm, nut on yakkety has no conflicts
[17:35] <patdk-wk> on xeries
[17:36] <nacc> apcupsd conflicts with ups-monitor afaict
[17:36] <nacc> ah nut-client and apcupsd?
[17:37] <patdk-wk> nut-server and apcupsd
[17:37] <nacc> i think only because ntu-server depends on nut-client
[17:37] <nacc> *nut-server
[17:37] <tarpman> patdk-wk: apt-get download and dpkg -i --force-conflicts?
[17:38] <nacc> yeah, that'd be my suggestion as well
[17:38] <nacc> i don't believe you can get apt to do it for you, easily
[17:39] <patdk-wk> ya, ups-monitor causes install to fail :(
[18:44] <BrianBlaze420> alright so I have managed to clone my system and get it working on a new box as I am going to be upgrading this ubuntu 8 LTS server. My issue is that even though I can see the ethernet card in lspci yet I don't see it in ifconfig
[18:44] <BrianBlaze420> I am curious how to get the ethernet card to work. when I google it's all about newer ubuntu systems
[18:44] <alkisg> Ubuntu 8.04? Wow... :D
[18:45] <BrianBlaze420> :)
[18:45] <BrianBlaze420> this is why I need to move forward lol
[18:45] <tarpman> BrianBlaze420: just 'ifconfig' may not show all interfaces if they aren't active; try 'ifconfig -a'
[18:45] <BrianBlaze420> i do -a and it only sees my lo
[18:45] <alkisg> Well, if the kernel is from 2008, and the card from 2015, it's possible that it's not supported. What is the lspci output for the card?
[18:46] <BrianBlaze420> the card works when I install 8 from scratch
[18:46] <BrianBlaze420> this is a clone
[18:46] <tarpman> check dmesg
[18:48] <alkisg> What's the output of this? lspci -nn -k | grep -A 2 Ethernet
[18:50] <sarnold> nikeshm: thanks for reporting back; I don't know iscsi well (obviously), so it's always nice to learn more :)
[18:50] <BrianBlaze420> 00:19.0 Ethernet controller : Intel Corporation 82567LF-3 Gigabit Network Connection [8086:10df] (rev 02)
[18:52] <BrianBlaze420> like I said I can get this to work if I install ubuntu 8 from nothing but this clone still has the old settings it seems
[18:52] <BrianBlaze420> and I am not sure how to reset
[18:58] <BrianBlaze420> damn it's hard trying to find info on an extinct version of ubuntu, how fun to come to a job where the previous guy didn't update lol
[18:59] <patdk-wk> heh
[18:59] <patdk-wk> that isn't too bad
[18:59] <alkisg> BrianBlaze420: you don't see "Kernel driver in use" there? If not, that's the issue
[18:59] <patdk-wk> it was fun started a job, and finding it was using an distro that hasn't existed for 3years, and they where using v1 of that distro from 13years ago
[19:00] <alkisg> BrianBlaze420: also, what kernel does the new 8 install have, and what kernel does the old one have
[19:00] <BrianBlaze420> 2.6.24-24-server
[19:01] <BrianBlaze420> where would I see kernel driver in use?
[19:01] <alkisg> $ lspci -nn -k | grep -A 2 Ethernet 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06) 	Subsystem: Gigabyte Technology Co., Ltd Motherboard [1458:e000] 	Kernel driver in use: r8169
[19:01] <BrianBlaze420> -k is not a valid option
[19:01] <alkisg> Check the output of `lsmod` for the intel driver then; or maybe lshw or something...
[19:02] <alkisg> Does it show up in `ip l`?
[19:02] <alkisg> And, check what the "new 8 install" kernel is
[19:05] <BrianBlaze420> lshw says network unclaimed
[19:05] <alkisg> Right, so you need a newer kernel
[19:05] <alkisg> The one that the "new 8 install" has
[19:05] <alkisg> BrianBlaze420: also note that you can boot from a recent live cd which will have the driver etc, then chroot to the old installation, and update it
[19:05] <BrianBlaze420> goctha
[19:06] <patdk-wk> do you know how to update the old install from the archive repos?
[19:06] <alkisg> Or you can even boot the disk via kvm, from either a live cd or from another installation; the kvm device should be avilable
[19:07] <BrianBlaze420> this all makes sense
[19:07] <alkisg> patdk-wk, http://askubuntu.com/questions/91815/how-to-install-software-or-upgrade-from-an-old-unsupported-release
[19:08] <BrianBlaze420> and no i have never installed from an old repo
[19:08] <alkisg> So you'll need to go from 8 to 10 to 12 to 14 to 16... maybe a reinstall would be faster? :D
[19:08] <BrianBlaze420> time to learn :)
[19:08] <alkisg> (and fix whatever issues arise in each update...
[19:09] <patdk-wk> I would just archive the server, and reinstall
[19:09] <patdk-wk> if it's that old, it's going be painful fixing configs all along the way
[19:09] <alkisg> With Ubuntu 8.04, you probably also have ext3 instead of ext4...
[19:09] <OerHeks> .. and old grub1
[19:10] <BrianBlaze420> yes I am not really worried about the whole update process at the moment it shall be a task in itself I want to be able to move this install to different hardware to test
[19:35] <BrianBlaze420> so far so good
[19:35] <BrianBlaze420> I appreciate the help a lot
[19:36] <BrianBlaze420> so if I do lshw and see unclaimed
[19:36] <BrianBlaze420> it means the kernel can see it but no drivers?
[19:50] <BrianBlaze420> oh I am so happy to move forward <3
[19:51] <nacc> BrianBlaze420: or the correct driver has not been loaded, iirc
[19:51] <nacc> BrianBlaze420: it technically just means what it sounds like, nothing has yet 'claimed' to operate that device
[19:51] <BrianBlaze420> gotcha
[19:52] <nacc> where claimed is really a binding operation (again, iirc) in the kernel saying that a given driver is appropriate for a given device (it doesn't technically mean the device is operational)
[19:59] <BrianBlaze420> which is what I saw :)
[20:00] <BrianBlaze420> oh ok I understand
[21:20] <rbasak> nacc: see https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1658289/comments/4
[21:21] <rbasak> nacc: if I'm right, then do you want to just drop that changelog entry and upload 7.0.15 in SRUs anyway, or do you want to cherry-pick the fix for that too?
[21:22] <nacc> rbasak: let me double-verify, i think we'll want to include that fix
[21:23] <rbasak> nacc: in that case do you want to prepare uploads to supersede what is currently in the X/Y queues?
[21:23] <rbasak> nacc: (also an upload for Z I guess)
[21:23] <nacc> rbasak: ack, doing that now
[21:23] <nacc> rbasak: and/or will do that now
[21:23] <rbasak> OK. Thanks!
[21:23] <nacc> rbasak: thanks for catching that, and sorry for my error!
[21:24] <rbasak> No problem!
[21:25] <nacc> rbasak: do you think we'd be better off moving to 7.0.16?
[21:25] <nacc> ah nm, still in beta
[21:58] <nacc> rbasak: uploaded
[21:59] <nacc> mdeslaur: fyi, sorry for the delay
[21:59] <mdeslaur> nacc: np! :)
[22:00] <BrianBlaze420> I am doing the do-release-upgrade and get this error : http://pastebin.com/iSsffQjQ
[22:00] <BrianBlaze420> was hoping someone could point me in a direction :)
[22:01] <powersj> jgrimm: FYI LP: #1664731
[22:02]  * jgrimm looks
[22:36] <rbasak> nacc: still around?
[22:36] <rbasak> nacc: no need to burn 7.0.15-0ubuntu0.16.{04,10}.1, as the old upload was never published.
[22:37] <rbasak> nacc: but also, if you want to do that, you should use -v7.0.13-0ubuntu0.16.04.1. Otherwise the changes file doesn't include the bugs against 7.0.15-0ubuntu0.16.04.1.
[22:37] <rbasak> So we'll end up not tracking the SRU bug.
[22:43] <nacc> rbasak: ah duh, so would you rather i just fix that up and reupload as 0ubuntu0.16.{04.10}.1 ? can you reject whatever is in the queue now?
[22:43] <nacc> rbasak: and ack on the changes
[22:43] <rbasak> nacc: yeah probably easiest. I'll reject now.
[22:43] <nacc> rbasak: thanks
[22:46] <nacc> rbasak: and will you want to reject .2 as well, then?
[22:46] <nacc> rbasak: nm, just email delay
[23:21] <teward> rbasak: so FYI
[23:21] <teward> I may have a merge-candidate package ready sooner than predicted
[23:21] <teward> depends if the upload to https://launchpad.net/~teward/+archive/ubuntu/nginx-merge-zesty I just made blows up in my face or not
[23:22] <teward> fak i forgot to add the other archs.  oopsies.
[23:22] <teward> those first three chars are an accident oops :)
[23:22] <rbasak> teward: \o/ thank you!
[23:22] <rbasak> teward: anything we can do to help before you can upload?
[23:22] <teward> install test, upgrade test?
[23:22] <teward> I'll put on the ML when that's ready
[23:23] <teward> i need to make sure it builds on all archs i can turn on in the PPA
[23:24] <teward> rbasak: the only difference in the version string between testing and actual is I have +test# added to the end of the string for test builds, because of the way the version strings detect, it'll explode with ~test#, but i also want it to be identified as build tests if, say, I broke it or something
[23:24] <teward> FOO I did forget something in the changelog
[23:24] <teward> that's something I'll add before pushing though
[23:26] <teward> oops I think i failed again
[23:33] <teward> fff i think i accidentally pushed to the repos
[23:53] <teward> rbasak: whoohoo, builds didn't blow up in my face this time xD
[23:56] <teward> rbasak: do we have a server release notes page yet or is that closer to release?
[23:56] <teward> because we'll need to make a small note about the potential performance impact on 32bit by having both PIE and PIC enabled
[23:56] <teward> and we need both, or it won't build
[23:58] <rbasak> teward: usually we do it closer to release, but it's fine to start writing it now if you wish. If the page doesn't exist, feel free to create it, basing it from Yakkety's notes.
[23:58] <teward> nah i'll wait
[23:58] <teward> just remind me :)