[03:49] <JackYu> jibel, hi, Ubuntu Kylin is ready for release. Will is the URL of Ubuntu release note? Do we need to prepare one for Ubuntu Kylin?
[04:21] <infinity> JackYu: I'm not sure individual announcements are really necessary for the point release, but if you want want to, you can.
[05:05] <JackYu> infinity, I think so:)
[05:06] <JackYu> infinity, so, I choose to share the Ubuntu one:).
[08:29] <jibel> jamespage, hey, could you update the tracker with the results for the tests for 14.04.1 server images?
[08:31] <jamespage> jibel: I thought that was automated?
[08:38] <jamespage> jibel, I can certainly help with the iscsi testing as I normally do - beisner will be around later to co-ordinate the rest
[09:27] <infinity> jibel: I'll do server on the powerpcs and core on ppc and arm64 tonight.  How are we looking otherwise?
[09:31] <infinity> tgm4883: You good to go to mark mythbuntu ready?
[09:31] <infinity> elfy: Ditto for xubuntu?
[09:37] <jibel> infinity, images are fine, upgrades are not so good. bug 1348067 , bug 1347964 (ubuntu-desktop fails to upgrade) and the failure with procps from saucy to trusty found yesterday
[09:40] <infinity> jibel: check.  Those are archive issues rather than image issues (not to downplay them, they need investigation, but shouldn't hold up the ISOs)
[09:40] <jibel> jamespage, tests are automated I'm just not sure if anyone look at the results
[09:41] <infinity> jibel: We saw a variation on your saucy->trusty issue a day or two before release and reverted something that made apt happy, but clearly not happy enough.  The real bug needs hunting and fixing. :/
[09:41] <apw> infinity, oh is it _that_ one
[09:41] <apw> back to haunt us
[09:42] <jibel> infinity, sure these upgrade issues don't affect the images themselves
[09:45] <highvoltage> Is there a wiki page that lists what have changed in the 14.04.1 point release?
[09:56] <infinity> apw: Yeah, looks like it's the same bug.
[10:25] <jamespage> jibel, looking at https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/ the server iso tests have not run for a bit now
[10:26] <jibel> jamespage, pfff, I'll talk to CI.
[10:26]  * jibel clears the results on the tracker
[10:39] <highvoltage> jibel: hey there
[10:42] <jibel> highvoltage, hi
[10:43] <highvoltage> jibel: I see you tested edubuntu 14.04.1 and passed ltsp, what hardware was that on?
[10:43] <jibel> highvoltage, in VMs
[10:43] <highvoltage> jibel: kvm?
[10:44] <jibel> highvoltage, no virtualbox, 1rst has 2 NICs (1 for external network and 1 for internal network) and 2nd VM has 1 NIC connected to the internal network
[10:44] <highvoltage> jibel: ok, thanks. I had some trouble with it under kvm, but my host was under load so I'll try again
[10:46] <jibel> highvoltage, you must install vbox extensions to pxe boot the client
[10:47] <highvoltage> jibel: my kvm thin client boots, but ldm doesn't start, but I'll troubleshoot further in a bit...
[10:56] <highvoltage> weird, it works fine when I set my virtual display card to anything that's not 'cirrus'.
[10:59] <xnox> i have no clue why cirrus is still the default, when it's that bad, and nobody has hardware like that any more.
[11:02] <highvoltage> xnox: yeah, strangely enough my host vm was also set to cirrus and that started X up just fine oO
[11:23] <pfsmorigo> infinity: is there a way to get an "older" daily?
[11:23] <pfsmorigo> like 1 month old
[11:25] <cjwatson> Dailies are purged after a while; we don't have space to keep them for very long.
[11:34] <pfsmorigo> cjwatson: I'm doing tests with the daily and the system seems to freeze during the first reboot after the installation
[11:35] <pfsmorigo> cjwatson: talking about ppc64el here
[11:35] <pfsmorigo> cjwatson: I want to test with some older versions after 14.04
[11:35] <cjwatson> It'll probably have to be investigated directly rather than by bisection, sorry.
[11:36] <cjwatson> We don't have the old dailies any more.
[11:37] <infinity> pfsmorigo: Is this on P7 or P8?  Real hardware or VM?
[11:37] <infinity> pfsmorigo: I was just about to test on a P7 VM.
[11:37] <pfsmorigo> cjwatson: qemu
[11:37] <pfsmorigo> infinity: ^
[11:37] <pfsmorigo> infinity: do you have a powerkvm to test?
[11:39] <infinity> pfsmorigo: I do, yes.
[11:40] <pfsmorigo> infinity: nice, so you just have to create a disk and install using the default options. the problem happens after the installation is over.
[11:42] <infinity> pfsmorigo: And if I fail to reproduce it?
[11:42] <infinity> pfsmorigo: Note that the kernel on the CD and the kernel you're rebooting into are identical, so it's curious if it's freezing on reboot. :/
[11:42] <pfsmorigo> infinity, cjwatson: https://gist.github.com/pfsmorigo/1a9f21bc7d0b6a48d818
[11:43] <pfsmorigo> infinity, cjwatson: it freezes after that
[11:43] <infinity> pfsmorigo: That's not frozen, that's a lack of console.
[11:44] <pfsmorigo> infinity: hmm. how do I "fix" it?
[11:45] <infinity> I'm not sure how you broke it.
[11:45] <infinity> OF stdout device is: /vdevice/vty@30001000
[11:45] <infinity> On every other SLOF install I've done, that's /vdevice/vty@30000000
[11:45] <pfsmorigo> infinity: good point
[11:45] <elfy> infinity: I somehow knew that I'd see a ping when I got in for lunch :p marked ours ready :)
[11:46] <infinity> elfy: Ta.
[11:46] <elfy> infinity: you going to need release notes?
[11:46] <infinity> elfy: Hand't planned on extensive flavour notes, unless anyone really wants to do some of their own.
[11:47] <infinity> Hadn't, even.
[11:47] <elfy> awesome - suits me perfectly tbh :)
[11:47] <infinity> pfsmorigo: So, I guarantee I won't be able to reproduce your issue on my VMs, where my SLOF defaults to a different console device.
[11:47] <pfsmorigo> infinity: the bug reporter use virsh and his xml has serial set to 30001000
[11:47] <infinity> pfsmorigo: The question then is, is this a new version of SLOF, or some weird way you're invoking qemu?
[11:48] <pfsmorigo> infinity: will try using 30000000
[11:48] <infinity> pfsmorigo: Oh, he's explicitly using a non-standard port? :(
[11:48] <infinity> *sigh*
[11:48] <pfsmorigo> infinity: cool, isn't? :P
[11:48] <infinity> So, we could very much improve the way we detect this, to be fair.
[11:48] <infinity> But, if you just let qemu/slof do their default thing, it works fine.
[11:49] <pfsmorigo> infinity: agree
[11:49] <infinity> pfsmorigo: A bug report that says "when I pick a non-standard serial setup, it all goes to poop" and some explanation of how to reproduce would be nice.
[11:49] <infinity> pfsmorigo: Reported against "finish-install".
[11:50] <pfsmorigo> infinity: he just attached the xml that he used to test the distro. don't know why he uses a non-standard port
[11:52] <infinity> pfsmorigo: Because your testers like to confuse me. :)
[11:53] <infinity> pfsmorigo: It's definitely still a bug that we fail to detect that situation, just not a critical one, since I can't see how "normal" users would do that by accident.
[11:53] <pfsmorigo> infinity: glad we solve it before it turns into a obscure kernel bug :P
[11:55] <pfsmorigo> infinity: the serial/console in his xml is like this: https://gist.github.com/pfsmorigo/32ada7e5439ef80d8e5e
[11:56] <infinity> Have I ever mentioned how much I hate virsh/libvirt?
[11:57] <infinity> If you just call qemu raw, you get a sane console on 0x30000000 which is, in fact, what you get when you boot a "real" openfirmware system via PowerVM or SLOF on bare metal too.
[12:28] <pfsmorigo> infinity: I used qemu directly and had the same "freeze"
[12:31] <infinity> pfsmorigo: Testing independently here to see what I get.
[12:32] <infinity> pfsmorigo: Out of curiosity, where does SLOF report your console being?  And how did you call qemu?
[12:38] <infinity> pfsmorigo: An install and reboot went fine here.
[12:39] <pfsmorigo> infinity: qemu-system-ppc64 -enable-kvm -M pseries -smp 4,cores=2,threads=4 -m 4G -nographic -device spapr-vscsi -device spapr-vlan,netdev=net0,mac=4C:45:42:45:06:41 -netdev bridge,br=br0,id=net0 -nodefaults -monitor stdio -serial pty -drive file=disk.img
[12:39] <pfsmorigo> infinity: then: screen /dev/pts/xx
[12:40] <infinity> pfsmorigo: SLOF **********************************************************************
[12:40] <infinity> QEMU Starting
[12:40] <infinity>  Build Date = Oct 15 2013 03:55:10
[12:40] <infinity>  FW Version = mockbuild@(private build)
[12:40] <infinity>  Press "s" to enter Open Firmware.
[12:40] <infinity> Populating /vdevice methods
[12:40] <infinity> Populating /vdevice/vty@71000000
[12:40] <infinity> Populating /vdevice/nvram@71000001
[12:40] <infinity> Populating /vdevice/l-lan@71000002
[12:40] <infinity> Populating /vdevice/v-scsi@71000003
[12:40] <infinity>        SCSI: Looking for devices
[12:40] <infinity>           8000000000000000 DISK     : "QEMU     QEMU HARDDISK    1.6."
[12:40] <infinity>           8200000000000000 CD-ROM   : "QEMU     QEMU CD-ROM      1.6."
[12:40] <infinity> Populating /vdevice/v-scsi@71000004
[12:40] <infinity>        SCSI: Looking for devices
[12:40] <infinity> Populating /pci@800000020000000
[12:40] <infinity>  Adapters on 0800000020000000
[12:40] <infinity>                      None
[12:40] <infinity> Scanning USB
[12:40] <infinity> Using default console: /vdevice/vty@71000000
[12:40] <infinity>   Welcome to Open Firmware
[12:40] <infinity>   Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
[12:40] <infinity>   This program and the accompanying materials are made available
[12:41] <infinity>   under the terms of the BSD License available at
[12:41] <infinity>   http://www.opensource.org/licenses/bsd-license.php
[12:41] <infinity> Trying to load:  from: disk ...   Successfully loaded
[12:41] <infinity> * finddevice /memory grub workaround *
[12:41] <infinity> error: no suitable video mode found.
[12:41] <infinity> error: failure writing sector 0x1044888 to `ieee1275/disk'.
[12:41] <infinity> * finddevice /memory grub workaround *
[12:41] <infinity> * finddevice /memory grub workaround *
[12:41] <infinity> Press any key to continue...
[12:41] <infinity> OF stdout device is: /vdevice/vty@71000000
[12:41] <infinity> Preparing to boot Linux version 3.13.0-32-generic (buildd@denneed04) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #57-Ubuntu SMP Tue Jul 15 03:50:31 UTC 2014 (Ubuntu 3.13.0-32.57-generic 3.13.11.4)
[12:41] <infinity> Detected machine type: 0000000000000101
[12:41] <infinity> Max number of cores passed to firmware: 2048 (NR_CPUS = 2048)
[12:41] <infinity> Calling ibm,client-architecture-support... done
[12:41] <infinity> command line: BOOT_IMAGE=/boot/vmlinux-3.13.0-32-generic root=UUID=d3530761-1c4f-4858-a284-79190eb52841 ro splash quiet vt.handoff=7
[12:41] <infinity> memory layout at init:
[12:41] <infinity>   memory_limit : 0000000000000000 (16 MB aligned)
[12:41] <infinity>   alloc_bottom : 0000000004e10000
[12:41] <infinity>   alloc_top    : 0000000030000000
[12:41] <infinity>   alloc_top_hi : 0000000300000000
[12:41] <infinity>   rmo_top      : 0000000030000000
[12:41] <infinity>   ram_top      : 0000000300000000
[12:41] <infinity> instantiating rtas at 0x000000002fff0000... done
[12:41] <infinity> prom_hold_cpus: skipped
[12:42] <infinity> copying OF device tree...
[12:42] <infinity> Building dt strings...
[12:42] <infinity> Building dt structure...
[12:42] <infinity> Device tree strings 0x0000000004e20000 -> 0x0000000004e20727
[12:42] <infinity> Device tree struct  0x0000000004e30000 -> 0x0000000004e40000
[12:42] <infinity> Calling quiesce...
[12:42] <infinity> returning from prom_init
[12:42] <infinity>  -> smp_release_cpus()
[12:42] <lool> this is going to take some time
[12:42] <infinity> spinning_secondaries = 7
[12:42] <infinity>  <- smp_release_cpus()
[12:42] <infinity>  <- setup_system()
[12:42] <infinity> CF000012
[12:42] <infinity> CF000015ch
[12:42] <infinity> Linux ppc64
[12:42] <infinity> #57-Ubuntu SMP T * Starting Mount filesystems on boot                    [ OK ]
[12:42] <infinity>  * Starting Populate /dev filesystem                                     [ OK ]
[12:42] <infinity>  * Starting Populate and link to /run filesystem                         [ OK ]
[12:42] <infinity>  * Stopping Populate /dev filesystem                                     [ OK ]
[12:42] <infinity>  * Stopping Populate and link to /run filesystem                         [ OK ]
[12:42] <infinity>  * Stopping Track if upstart is running in a container                   [ OK ]
[12:42] <infinity>  * Starting Signal sysvinit that the rootfs is mounted                   [ OK ]
[12:42] <infinity>  * Starting Initialize or finalize resolvconf                            [ OK ]
[12:43] <infinity>  * Starting Signal sysvinit that virtual filesystems are mounted         [ OK ]
[12:43] <infinity>  * Starting Signal sysvinit that virtual filesystems are mounted         [ OK ]
[12:43] <infinity>  * Starting Bridge udev events into upstart                              [ OK ]
[12:43] <infinity>  * Starting Signal sysvinit that remote filesystems are mounted          [ OK ]
[12:43] <infinity>  * Starting Clean /tmp directory                                         [ OK ]
[12:43] <infinity>  * Starting device node and kernel event manager                         [ OK ]
[12:43] <infinity>  * Stopping Clean /tmp directory                                         [ OK ]
[12:43] <infinity>  * Starting load modules from /etc/modules                               [ OK ]
[12:43] <infinity>  * Starting cold plug devices                                            [ OK ]
[12:43] <infinity>  * Starting log initial device creation                                  [ OK ]
[12:43] <infinity>  * Starting Signal sysvinit that local filesystems are mounted           [ OK ]
[12:43] <infinity>  * Stopping Mount filesystems on boot                                    [ OK ]
[12:43] <infinity> GAH.
[12:43] <infinity> WRONG MOUSE BUTTON.
[12:43] <infinity> pfsmorigo: http://paste.ubuntu.com/7847407/
[12:43] <infinity> pfsmorigo: So, I'm assuming '-serial pty' does something funky.  But this isn't new either, it would have been broken this same way since release (indeed, since we started the port).
[12:43] <infinity> lool: Sorry.  Middle click fail. :/
[12:43] <infinity> lool: Not sure how I didn't get kicked.
[12:43] <pfsmorigo> infinity: https://gist.github.com/pfsmorigo/245ae92f1ff682f473db
[12:44] <pfsmorigo> infinity: this is what I get in the screen
[12:44] <xnox> lool: serial console over IRC is the best with rate limiting =)
[12:44] <infinity> pfsmorigo: Oh, kay, so you're getting a device we should be setting up correctly (the same one I just pasted).
[12:45] <infinity> pfsmorigo: Err, did you *install* with that setup, or are you rebooting an already broken install?
[12:45] <pfsmorigo> infinity: second option
[12:45] <infinity> pfsmorigo: Kay, right.  So, broken.
[12:45] <infinity> pfsmorigo: The installer detects if it should set up a console on hvc[01] based on magic openfirmware nodes existing at install time.
[12:46] <infinity> pfsmorigo: So, if you run an install under that setup there, it'll work fine.
[12:46] <pfsmorigo> infinity: ok, let me do some tests here
[12:46] <infinity> pfsmorigo: As you can see from my paste, which matches yours, but has a getty with a login prompt. :)
[12:46] <lool> xnox: yeah it felt like 100 bauds or something
[12:46] <ogra_> ls
[12:47] <ogra_> pwd
[12:47] <lool> ogra_: Password:
[12:47] <pfsmorigo> lol
[12:47] <ogra_> 123456
[12:47] <ogra_> oops !
[12:47] <infinity> ogra_: That's the same combination I have on my luggage!
[12:47] <ogra_> lol
[12:47] <lool> haha
[12:53] <davmor2> ogra_: I expect something more inventive from you like 123456!
[12:53] <ogra_> 123456äöü
[12:53] <ogra_> ;)
[12:55] <davmor2> ogra_: or hunter2
[12:56] <pfsmorigo> infinity: I found some tickets about this problem. https://bugs.launchpad.net/ubuntu/+bug/1347967
[12:56] <pfsmorigo> infinity: "From what I know, there is no difference/limitation between these two values to Libvirt, it just address assigned to the device. Althrough 30000000 is defined for VIO_ADDR_SERIAL specificly, both works fine as serial address."
[12:58] <infinity> pfsmorigo: Kay, so a Kimchi bug (and yes, also an Ubuntu bug)
[12:59] <infinity> pfsmorigo: For the record, the default in SLOF appears to be 71000000 (which we handle fine), and we also handle 30000000, but not 30001000.
[12:59] <pfsmorigo> infinity: ok, got it
[12:59] <infinity> pfsmorigo: Going forward, I plan to try to rewrite this to detect things a bit more sanely but, for now, it might be nice if Kimchi wasn't doing silly non-standard things.
[13:00] <infinity> pfsmorigo: If there's already an install base of systems that will be trying 30001000 though, we can certainly fix the hardcoding in the installer to also look there for now.
[13:00] <infinity> pfsmorigo: Not for the point release, but for a later update.
[13:02] <pfsmorigo> infinity: ok
[13:10] <tgm4883> infinity: yes Mythbuntu is good to go
[13:10] <infinity> tgm4883: \o/
[13:12]  * infinity spins source ISOs.
[13:34] <highvoltage> is there an estimated time for the release if everything goes well?
[13:36] <infinity> highvoltage: Not going to make estimates, but "today, in my timezone".
[13:36] <infinity> highvoltage: Which gives you, uhm, 16.5 hours of wiggle room. :P
[13:41] <highvoltage> infinity: *shrug*, good enough :)
[13:46] <jibel> infinity, ubuntu looks good, server tests are done, I'm updating the tracker. The most critical bugs found are upgrade crashes mentioned earlier, someone from foundations will have to look at them.
[13:48] <infinity> jibel: Agreed, we'll have to make some time to take a closer look ASAP.
[13:48] <infinity> jibel: And possibly hold off on flipping the meta-release upgrade switch until we know WTF is going on.
[13:49] <infinity> jibel: Though, have you seen the issue with precise->trusty, or just saucy->trusty?
[13:50] <jibel> infinity, +1 holding off flipping the switch
[13:50] <jibel> infinity, I reproduced 1347964
[13:50] <jibel> bug 1347964
[13:50] <jibel> twice
[13:50] <jibel> and it leaves the system in a completely broken state, if you reboot you cannot even login
[13:56] <infinity> jibel: Oh, that's an entirely different bug, and probably a pure packaging issue.  But yes, that should also be fixed. :/
[13:59] <mdeslaur> infinity: can the eglibc package be removed in utopic?
[14:07] <infinity> mdeslaur: Need to fix all the cross-buildy stuff, but that's the plan, yes.
[14:07] <mdeslaur> infinity: ah, ok, thanks
[14:22] <mdeslaur> infinity: if you still care about the lucid sparc eglibc FTBFS, now would be the time to get me that patch you had
[14:27] <infinity> mdeslaur: Oh, is it security time?  Whee.  No need to do utopic, BTW, I'll merge with Debian (assuming it's the CVE covered in unstable a week or so ago).
[14:27] <mdeslaur> infinity: yeah, that's the one
[14:28] <infinity> mdeslaur: I don't actually remember what the sparc issue was.  I'm not sure I remember even having the conversation. :)
[14:31] <infinity> mdeslaur: Oh, it was a breakage in the most recent security update.  Yeah, I think we pulled a patch or two for that in Debian.  Can I look tomorrow, or are you doing it Right Now?
[14:31] <mdeslaur> infinity: https://launchpad.net/~ubuntu-security/+archive/ubuntu/ppa/+build/5068250
[14:31] <mdeslaur> infinity: yeah, you can look tomorrow
[14:33] <infinity>   * patches/any/cvs-CVE-2013-4237-alignment.diff: Fix alignment of the
[14:33] <infinity>     directory block in dirstream.h, fixing readdir regression on sparc.
[14:33] <infinity> mdeslaur: Looks like it would be that one.
[14:33] <mdeslaur> infinity: thanks, I'll take a look when I work on lucid
[14:33] <infinity> mdeslaur: Possibly might also want to look at:
[14:33] <infinity>   * patches/any/cvs-CVE-2013-4332-memalign-2.diff: patch from upstream to
[14:33] <infinity>     address some remaining issues from CVE-2013-4332.
[14:37] <infinity> mdeslaur: If you have troubles hunting those down (cause they're likely merged upstream by now, and thus not patches in utopic), I can help you tomorrow.
[14:37] <mdeslaur> infinity: thanks, I'll let you know
[15:07] <mvo_> could someone reject my upload for update-manager to precise-proposed please?
[15:17] <infinity> mvo_: Sure.
[15:21] <mvo_> tthanks infinity
[15:47] <mvo_> and if someone could review the update-manger in precise-proposed that would be great - its for the hwe-support so would be good to get it in
[15:58] <jibel> infinity, I published the testing report, is there a changes summary or a script to generate it like https://wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/ChangeSummary/12.04.4 ?
[16:02] <cjwatson> jibel: I'm going to make a start on that in a bit
[16:03] <infinity> jibel: I think we can promise it'll be at the obviously guessable URL, and it can just 404 for now.
[16:04] <jibel> cjwatson, okay
[17:46] <xdatap1> Hi everybody
[17:47] <xdatap1> I'm from the Italian LoCo Team. We realese a localized version of Ubuntu. Is the 14.04.1 already out? Can we release our image?
[18:50] <zul> can an archive admin promote python-hacking please (#1331490)
[20:50] <Riddell> infinity: are we nearly there yet?
[21:38] <Riddell> zul: done