[05:22] <sarnold> ouch 1572400
[05:23] <Unit193> Not specifically new, glib/gvfs (or something) related, iirc.
[05:27] <Unit193> Just use mv/cp/rm! :3
[05:28] <sarnold> much easier to remember those than something complicated like 'thunar'. 'lunar'? nope 'thor'? nope 'thunder'? nope 'lothar'? nope...
[05:28] <sarnold> besides, six whole chars, you've already got all of mvcprm in that :)
[05:33] <alkisg> `do-release-upgrade -d` from 14.04 is prompting me [continue, details etc] in Greek, and it crashes on non utf-8 input, and it doesn't continue by pressing "y" for yes in English etc
[05:33] <alkisg> Is it safe to just ctrl+c it and re-run it in english?
[05:34] <sarnold> I'd expect so
[05:34] <sarnold> but then I'd expect it to work in greek, too.
[05:35] <alkisg> Python needs some setlocale('utf-8') or so, and apparently isn't not executed at that point...
[05:35] <alkisg> Thanks, Ctrl+C'ing...
[05:35] <sarnold> since it's python I'm not surprised it crashed on non-utf8 input :/ but between you and me it shouldn't do -that- either
[05:35] <alkisg> python3 is unicode by default afaik, I thought 16.04 used python 3 by default
[05:36] <sarnold> do-release-upgrade comes from your current release, not the newest release though :)
[05:36] <alkisg> Ah, true
[05:36] <sarnold> 14.04 LTS's is python3 though
[05:39] <mgedmin> do you have a link to the ubuntu-release-upgrader bug about this?
[05:39] <alkisg> No, I didn't file a bug about it
[05:40] <mgedmin> if nobody ever did, that might explain why the bug's been unfixed for so long ;)
[05:41] <alkisg> I'm still waiting for input on the last 100 bugs I've filed :)
[05:41] <mgedmin> that does then to discourage bug filing
[05:41] <sarnold> unfiled bugs gather no .. moss. I dunno. it's late.
[05:41] <alkisg> It's a minor detail compared to other bugs that affect us... e.g. we can't even type Greek by default!
[05:41]  * mgedmin is a user who once got an ubuntu-release-upgrader bug fixed
[05:42] <cpaelzer> good morning
[05:42] <sarnold> hey cpaelzer
[05:42] <alkisg> Good morning
[05:42] <sarnold> alkisg: man how can you do math if you can't type greek by default? :)
[05:43] <alkisg> :)
[05:44] <alkisg> Ouch, now `do-release-upgade -d` thinks I'm already in Xenial and does nothing :D
[05:44] <slangasek> alkisg: python3 strings are unicode natively; this does not remove the need to do encoding handling when converting from a bytestream (such as stdin) to a string.  please do file a bug about this crash
[05:45] <alkisg> slangasek: the main problem is that I cannot continue even when I type the English letter there, I'll need to dig in more to file a proper bug report
[05:45] <slangasek> can't type Greek by default> λοοκσ γοοδ το με
[05:45] <slangasek> alkisg: ok
[05:45] <alkisg> It's like this: Continue [y/N] Λεπτομέρειες [λ] ==> I can't type "y"
[05:45] <sarnold> that's already better than something like 80% of the bug reports :)
[05:46] <alkisg> With "λ" (Details), it crashed with utf8 exception, then it restarted, then "λ" worked, but "y" still doesn't work
[05:46] <slangasek> but you said it crashed, so backtrace please ;)
[05:46] <sarnold> slangasek: haha, and here for a second I thought you actually knew greek. sigh :)
[05:46] <alkisg> OK, moment then...
[05:47] <alkisg> apport-bug /var/crash/_usr_bin_do-release-upgrade.0.crash, right? It popup up the initial window about reporting the issue, and then nothing
[05:48] <alkisg> Maybe now apport crashes because it can't collect my release info, since it already started the upgrade :D
[05:48] <sarnold> ubuntu-bug do-release-upgrade ought to work too
[05:50] <alkisg> It says no such package installed. Then apport-bug ubuntu-release-upgrader-core does work, but it doesn't seem to pick up the trace.
[05:50] <sarnold> is it still on screen? copy-and-paste is fine
[05:51] <alkisg> OK let me put the .crash part to pastebin...
[05:51] <mgedmin> it's ubuntu-bug $(which do-release-upgrade)
[05:51] <sarnold> mgedmin: gah :) thanks
[05:51] <mgedmin> it wants a package name or a full path to the program
[05:52] <alkisg> paste.ubuntu.com/15941779
[05:53] <alkisg> mgedmin: that works but doesn't seem to pick up the crash either
[05:54] <sarnold> can you stuff the traceback into the bugreport? that way it won't get lost if the pastebin database goes away for some reason
[05:57] <mgedmin> strange: λ is 0xCE 0xBB in UTF-8, but the traceback complains about "byte 0xcf in position 0: invalid continuation byte"
[05:57] <alkisg> While filing the bug, I saw LP: #1241148
[05:57] <alkisg> I'm guessing it's the same bug report, slangasek do you still want me to file it?
[05:59] <sarnold> interesting, 0xcf appears to be omicron, Ο
[06:03] <alkisg> http://www.fileformat.info/info/charset/UTF-8/list.htm
[06:04] <alkisg> 0xcf is the start byte for a lot of greek characters, but not "λ"...
[06:04] <cpaelzer> I thought I remembered something very old I once had and found links like this about the "invalid continuation byte" that sounded familiar (to at least my old case) http://stackoverflow.com/questions/5552555/unicodedecodeerror-invalid-continuation-byte
[06:04] <sarnold> alkisg: of course I forgot to mention.. 0xcf in iso-8859-7 is O ..
[06:04] <cpaelzer> I don't have all the caht backlog, but would it make any sense to assume it not even is UTF-8 ?
[06:04] <cpaelzer> bus iso-...
[06:05] <cpaelzer> ah I see by sarnold you are already on iso-...
[06:05] <alkisg> sarnold:  I don't think iso-8859 is related here, we're not using it, we're only using utf-8
[06:05] <sarnold> alkisg: you said it crashed on non-utf8 input, so I jumped to the assumption that you're using the previous decade's encodings :)
[06:06] <sarnold> alkisg: be sure to mention that in the bug report :)
[06:06] <sarnold> time to bail :) have fun
[06:06] <alkisg> sarnold: yeah sorry my bad, it was the error that made me say that
[06:07] <alkisg> sarnold: do you think I should file a bug report even though another already exists for russian?
[06:07] <alkisg> slangasek: ^ ?
[06:08] <sarnold> alkisg: yeah, never hurts
[06:08] <alkisg> OK, ty
[06:08] <sarnold> alkisg: they're cheap enough to merge if they're really the same underlying bug, and if they aren't, having two means yours is less likely to be ignored
[06:09]  * alkisg just doesn't like bugs.launchpad.net/alkisg growing all the time if some of them are to remain unresolved... :)
[06:14] <alkisg> OK, I filed LP: #1572416, now on to actually do the upgrade even manually...
[06:20] <alkisg> I reverted my sources.list and  tried again do-release-upgrade in Greek, this time it didn't crash, but it doesn't accept y/N either, so I can't continue
[06:21] <alkisg> Isn't N (capital) there meant to be the default, to be selected with plain enter?
[06:21] <pitti> Good morning
[06:21] <alkisg> Hello pitti
[06:22] <mgedmin> could be a translation file bug
[06:22] <alkisg> [enter] should still work....
[06:23] <mgedmin> but the default is N, which is "no, don't continue, abort the upgrade"
[06:23] <alkisg> Yet it doesn't accept that
[06:23] <alkisg> It just prompts again
[06:23] <mgedmin> are you saying Enter doesn't do anything?  that's weird
[06:24] <alkisg> Well, time to run it with LANG=en_US.UTF-8 :)
[06:28] <alkisg> Yey, I got it to continue in Greek by pressing the Greek letter for "y", i.e. "ν" :)
[07:57] <nhaines> dholbach, seb128: could one of you help me out with a merge proposal?  :)  https://code.launchpad.net/~nhaines/example-content/xenial-fcs/+merge/292345
[07:57] <seb128> oh, and 4
[07:59] <dholbach> wow... that's quite late :-(
[07:59] <dholbach> seb128, are we still spinning new images?
[07:59] <seb128> as said on -release I can do sponsoring
[07:59] <seb128> but unsure the release team is wanting it that late
[08:00]  * dholbach nods
[08:00] <seb128> dholbach, we might, but even if we are I'm unsure they want to include such changes
[08:00] <dholbach> I see
[08:00] <seb128> as said I'm not in the release team
[08:00] <seb128> so the wrong person to ask
[08:00] <seb128> I'm happy to help with upload though
[08:00] <nhaines> Hmm, it's too late to be split between two channels.  :)  I know it's way too late, but there were all sorts of content licensing issues with the video submissions (that I subverted by just creating original content).  It turns out installing Ubuntu 24 times takes a very, very long time.
[08:01] <nhaines> In any case, I'm asking because it's a pretty low-risk change.  If there were any binary code at all I wouldn't bother for something like this.
[08:01] <seb128> nhaines, is there a bug explaining the issue?
[08:01] <nhaines> seb128: no, but I can certainly file one.
[08:01] <dholbach> seb128, it's the winners from the free culture showcase
[08:01] <seb128> dholbach, can you just upload it?
[08:01] <seb128> then we can see if -release wants to get it in
[08:01] <dholbach> so from a release team POV just new content
[08:02] <dholbach> sure
[08:02] <seb128> or if that goes as a SRU
[08:02] <seb128> for .1
[08:02] <seb128> nhaines, ^
[08:02] <seb128> nhaines, dholbach, thanks
[08:02] <nhaines> seb128: thank you!
[08:02] <dholbach> nhaines, next time if there are issues like this, please bring it up on the ubuntu-community-team mailing list or elsewhere so people can help
[08:02] <zyga> good morning
[08:03] <nhaines> dholbach: the release snuck up on me... the 21st is also my birthday and work's been crazy too.
[08:04] <nhaines> seb128: good morning!  I hope you're having a great midweek.  :)
[08:04] <dholbach> nhaines, yeah... that's why I thought somebody could have helped earlier
[08:04] <seb128> nhaines, lol, hey :-) yeah, a bit crazy, but that's normal in release weeks!
[08:06] <nhaines> It's looking pretty good!  I've been wanting to reinstall xenial fresh on my main box a couple days early but... been too busy unfortunately.  :)  Probably this weekend though!
[08:07] <nhaines> dholbach: with the video submission, something had to be done from scratch and I wasn't certain if I wanted to even attempt it.  It was too much work for me to feel comfortable asking someone else to do.
[08:07] <nhaines> Which isn't much of an excuse, but it's an honest one.  :)  I hope you're having a nice midweek, too!
[08:07] <dholbach> right... I understand,... I'm not blaming you or anything
[08:08] <nhaines> dholbach: it's okay, I'll do that myself.  :)
[08:08] <seb128> dholbach, nhaines, did the package increase in disk size?
[08:08] <seb128> just checking
[08:08] <dholbach> seb128, I'll let you know in a sec
[08:08] <dholbach> -rw-r--r-- 1 daniel daniel 5223256 Okt  4  2013 example-content_48_all.deb
[08:08] <dholbach> -rw-r--r-- 1 daniel daniel 8995738 Apr 20 10:08 pbuilder/xenial_result/example-content_49_all.deb
[08:09] <dholbach> seb128, ^
[08:09] <seb128> ok, another 4.7M
[08:10] <seb128> I don't think it's going to make a big difference on a > 1G iso, though it's still a step in the wrong direction
[08:10] <dholbach> maybe something can be done on the video?
[08:10] <nhaines> I spent 2 hours trying to get the video to look good and not be 30 MB (I think it's 11.7 MB).  I'm not thrilled but the 4 MB one was not acceptable.
[08:10] <seb128> yeah, it feels late to start trying to change the video format or start recompressing though
[08:11] <seb128> dholbach, nhaines, just get it in like that, it's not 30M which is good ;-)
[08:11] <dholbach> ok, uploading it now
[08:11] <seb128> it's not the only part where we let things drift a bit
[08:12] <nhaines> I'd like to see work done about that... but then again I miss the 700 MB images and of course I don't have any way to help with any of that, so...
[08:12] <nhaines> I made sure the community wallpapers were all nice resolution but still 1.5 MB each.  A nice change from last time.  :)
[08:13] <nhaines> dholbach: speaking of, I did all the packaging work for ubuntu-wallpapers-xenial too!  I was proud of that.  It's the first time I've caused a new package to be created in Ubuntu.  :)
[08:13] <dholbach> https://launchpad.net/ubuntu/xenial/+queue?queue_state=1&queue_text=
[08:13] <dholbach> :-)
[08:13] <nhaines> dholbach, seb128: thank you very much.  I'll be thinking about a much better process for xenial+1.
[08:13] <seb128> nhaines, thanks for working on those, really appreciated!
[08:14] <dholbach> but yeah... next time: don't do it all alone :)
[08:14] <dholbach> and keep up the good work - as seb128 said: it's much appreciated
[08:16] <nhaines> Thank you both.  :)
[08:16] <nhaines> I did all the work for the wallpapers because I felt guilty asking others to do that in a hurry when I waited so long.  That just didn't scale to the video (which took me like 3 days).  ;)
[08:17] <dholbach> wow
[08:17] <doko> seb128, Laney: what are AppStream compatible icons?
[08:18] <Laney> https://wiki.debian.org/AppStream/Guidelines
[08:18] <nhaines> It was fun though...  I didn't remember how bold and artistic the default wallpapers got just before the new branding in Ubuntu 10.04 LTS.  I think it'll be a fitting video for 16.04.  :)
[08:21] <nhaines> seb128, dholbach: okay, this'll be the first update to example-content in like 2.5 years!  \o/  So thanks for your help, sorry for the excessive energy earlier, and now I'm going to get some sleep...
[08:22] <nhaines> Because if it gets accepted then I have a blog post to write about it and the wallpapers for Thursday or Friday.  XD
[08:22] <seb128> nhaines, no worry, have a good night and thanks again for the work!
[08:24] <seb128> wgrant, cjwatson, not something for before the release, but would somebody consider looking at bug #1260760 in exchange of some beer rounds? ;-)
[08:24] <seb128> it's a pretty annoying bug
[08:24] <seb128> every time somebody edits a gtk but it gets reassigned to "ubuntu"
[08:24] <seb128> I guess it has to do with the "+" in the name
[08:25] <cjwatson> seb128: I'll see what I can do
[08:26] <seb128> cjwatson, thanks
[08:29] <alkisg> Meh, do-release-upgrade from 14.04 was a complete disaster, it errored out in the middle of the update
[08:29] <cjwatson> https://launchpad.net/bugs/1260760
[08:29] <cjwatson> oops
[08:29] <cjwatson> Content-Disposition: form-data; name="ubuntu_gtk+3.0.target.distribution"
[08:30] <cjwatson> Content-Disposition: form-data; name="ubuntu_gtk-3.0.target.package-dWJ1bnR1X2d0ayszLjAudGFyZ2V0LnBhY2thZ2U"
[08:30] <cjwatson> that looks suspicious
[08:30] <seb128> alkisg, do you have details on the error?
[08:31] <alkisg> seb128: I got an apport prompt, let me see if it's the correct one or the previous one...
[08:31] <alkisg> (the previous was an issue with greek that I reported a couple of hours ago)
[08:31] <seb128> alkisg, did you use that prompt to submit the bug?
[08:33] <alkisg> (patience, it needs some time to process it... :))
[08:33] <alkisg> (92% cpu apport-gtk...)
[08:33] <alkisg> Nope, apport-gtk closed without explanation
[08:34] <alkisg> In /var/crash I see the old crash and a new one for smbd only
[08:34] <alkisg> So it was probably the previous crash that I already reported
[08:35]  * alkisg has seen apport show up many times about the same bug...
[08:35] <alkisg> *same crash
[08:40] <xnox> pitti, i thought slangasek fixed that up for me yesterday.
[08:41] <pitti> xnox: qemu/ yes, s'all good
[08:45] <cjwatson> seb128: damnit, you would give me the ridiculously twisty bugs
[08:45] <seb128> cjwatson, lol, sorry about that ;-)
[09:57] <alkisg> So the problem was probably due to bamfdaemon, unsatisfiable dependencies for configuring, and removing it temporarily allowed the upgrade to proceed
[10:28] <Mirv> xnox: please tell me if I need to stop having you as the "go to s390x guy", but I filed bug #1572496 about a s390x SEGV I'm getting with Qt 5.6
[10:30] <xnox> Mirv, i am s390x guy.
[10:30] <Mirv> now I'd also need a "go to powerpc guy"..
[10:31] <xnox> Mirv, powerpc or ppc64el?
[10:32] <xnox> Mirv, it would be nice if qt build would like automatically execute things under gdb and generate a traceback.
[10:32] <Mirv> xnox: powerpc only https://launchpadlibrarian.net/254349222/buildlog_ubuntu-xenial-powerpc.gsettings-qt_0.1+16.04.20160329-0ubuntu2~xenialoverlay1~2_BUILDING.txt.gz
[10:37] <Mirv> filed powerpc bugs bug #1572497 and bug #1572499
[11:54] <latenite> Hi folks, what is 'resolvconf' doing? What do I need it for? Why is a plain static interface in /etc/network/interfaces running 'resolvconf' to manipulate(overwrite) /etc/resolv.conf ?
[12:00] <ivoks> latenite: ifupdown is just one of the sources for DNS
[12:00] <ivoks> latenite: if dhclient, ppp daemon, ifupdown would write to resolv.conf, each on its own, they would owerwrite each other
[12:00] <ivoks> and then... who is correct?
[12:01] <ivoks> so they have resolvconf, which takes care of that
[12:01] <ivoks> cool for desktops, but maybe not that cool for servers
[12:01] <latenite> ivoks, I just wonder when I don't use and dhcp, ppp etc. but only a static configuration. Why is a 'resolvconf' even used for that interface then?
[12:02] <ivoks> then you don't need it, you can remove it and write everything statically
[12:02] <latenite> ivoks, why is it default for the server?
[12:02] <ivoks> it's default in ubuntu
[12:03] <ivoks> (most of the serves i deployed in last 2 years were actually on dhcp :)
[12:03] <latenite> ivoks, why is it default for ubuntu?
[12:04] <latenite> so you say the trend goes to dhcp in servers and that's why servers have resolvconf?!
[12:04] <ivoks> i wanted to give you a technical reson why it's default and needed. i understand it doesn't cover all use cases, and therefore you can uninstall it
[12:05] <ivoks> and these kind of questions belong to ubuntu-server or ubuntu; this is a development channel
[12:05] <latenite> ivoks, What is the difference between uninstalling it and setting up resolv.conf and setting up /etc/resolvconv/*conf ?
[12:05] <latenite> ivoks, oh ok, I understand
[13:30] <Odd_Bloke> I just sent an email to ubuntu-devel@; could someone reject it?
[13:30] <Odd_Bloke> I noticed something I wanted to clarify as I hit send. ¬.¬
[13:31] <Odd_Bloke> I've sent another one through, with the clarification added.
[13:32] <Odd_Bloke> So if someone could reject the earlier one and accept the new one, I would appreciate it.
[13:33] <Odd_Bloke> Oh, I'm able to self-reject; so we should be back to just one message in the queue.
[13:35] <Odd_Bloke> cjwatson: If/when you have a minute, ^.  (You're listed as the owner of the list, so I don't know who else to ping :)
[13:36] <Laney> Odd_Bloke: I accepted it for you
[13:37] <Odd_Bloke> Laney: Thanks. <3
[13:37] <Laney> not at all!
[13:56] <LocutusOfBorg> how can I see who is seeding a particular package?
[13:57] <LocutusOfBorg> seeded-in-ubuntu?
[13:58] <Laney> yes
[13:58] <LocutusOfBorg> xserver-xorg-legacy (from xorg-server) is seeded in:
[13:58] <LocutusOfBorg>   mythbuntu: daily-live
[13:58] <LocutusOfBorg>   ubuntu-gnome: daily-live
[13:58] <LocutusOfBorg> ok I need to check with mythbuntu
[13:58] <LocutusOfBorg> ubuntu-gnome is already aware
[14:13] <mterry> ogra_, you're killing me with these MIRs  :)
[14:13] <mterry> ogra_, what's the expectation there?  I doubt they'll all get approved before 16.04 ships
[14:13] <ogra_> mterry, really sorry that they come so late ... (i was planning that earlier but tons of image issues the last week)
[14:14] <ogra_> the initramfs tools and the core-libs/-config packages are surely no brainers
[14:14] <mterry> ogra_, are we looking at forced promotion and dealing with MIR issues in 16.10 cycle?
[14:14] <ogra_> well, snappy images will obnly release in july ...
[14:14] <ogra_> so there will still be plenty SRUs
[14:15] <mterry> ogra_, but flipping between universe and main can't be done in 16.04 repos, right?
[14:15] <mterry> ogra_, libnss-extrausers and watchdog probably need a quick security look, which is never quick
[14:15] <ogra_> right, not post release afaik
[14:16] <ogra_> i dont knwo if we actually need watchdog (was seeded on a 15.04 customer request)... extrausers is definitely essential though
[14:23] <superm1> LocutusOfBorg: what'st he context on looking for seeding in mythbuntu?
[14:26] <LocutusOfBorg> xserver-xorg-legacy can be removed
[14:26] <LocutusOfBorg> x don't need to be root
[14:27] <LocutusOfBorg> just replace with virtualbox-guest-dkms
[14:27] <LocutusOfBorg> superm1, ^^
[14:28] <superm1> LocutusOfBorg: IIRC we're not seeding it explicitly somewhere
[14:28] <superm1> some meta update needed maybe?
[14:28] <LocutusOfBorg> yes I guess so
[14:29] <superm1> LocutusOfBorg: according to http://people.canonical.com/~ubuntu-archive/germinate-output/mythbuntu.xenial/all it's coming from nvidia-304
[14:30] <superm1> which is an nvidia driver option installable from ubuntu-drivers
[14:30] <LocutusOfBorg> ok
[14:30] <LocutusOfBorg> thanks
[16:29] <Son_Goku> nacc: official libvirt-php 0.5.2 release: https://www.redhat.com/archives/libvir-list/2016-April/msg01337.html
[17:07] <ogra_> apw, bug 1572650
[17:07] <ogra_> apw, see the request for a team bug subscription ... i assume that should be the kernel team
[17:07] <ogra_> ?
[17:07] <apw> ogra_, yes, please
[17:07] <ogra_> apw, heh, i cant ... needs to be th e team admin
[17:08] <ogra_> (dunno who that is)
[17:08] <apw> ogra_, prolly me, where do i change subs ?
[17:08] <ogra_> i guess ogasawara =
[17:08] <ogra_> apw, https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan on the right ... "subscribe to bug mail" that gets you a popup where you can then select a team instead of yourself
[17:09] <ogra_> (in a totally intuitive pulldown with only 2987538475 entries ... )
[17:09] <apw> ogra_, ok done
[17:09] <apw> i hope
[17:09] <ogra_> thx
[17:16] <slangasek> apw, ogra_: see my followup on that bug about the right bug subcriber for the MIR process
[17:17] <ogra_> slangasek, ah ...
[17:17] <apw> slangasek, ahh ok thanks
[17:17] <ogra_> slangasek, if you make me an admin for snappy-dev i can add that team to the other packages ... (mvo doesnt react, i guess he is afk for dinner or something)
[17:18] <slangasek> list of recognized teams:http://bazaar.launchpad.net/~ubuntu-archive/ubuntu-archive-tools/trunk/view/head:/package-subscribers#L117
[17:18] <slangasek> ogra_: ah, I may have privs to do that but don't think I should be adjusting admins on the team without another admin's approval
[17:18] <ogra_> hrm, i guess we need to add some snappy team to that
[17:18] <slangasek> ogra_: I can however take care of the actual bug subscriptions now
[17:19] <ogra_> ok
[17:19] <ogra_> slangasek, yeahm thats fine too ... i'm not eager to be an admin :)
[17:19] <slangasek> ogra_: snappy-dev should own all of initramfs-tools-ubuntu-core, libnss-extrausers, watchdog, ubuntu-core-config?
[17:20] <ogra_> slangasek, yep, looks right
[17:20] <ogra_> and the ubuntu-core.meta indeed
[17:20] <slangasek> are you sure? ;)  because some of those look like things it should actually be on Foundations to maintain
[17:20] <ogra_> oh, feel free :)
[17:21] <slangasek> watchdog, libnss-extrausers
[17:21] <ogra_> yeah
[17:21] <slangasek> subscriptions done
[17:21] <ogra_> thanks !
[18:20] <kyrofa> cdimage.ubuntu.com still says "Warning: This image is oversized (which is a bug)." That's not actually a bug nowadays, is it?
[18:21] <ogra_> depends on the size
[18:21] <ogra_> iirc we bumped the size to 1G at soome point
[18:21] <sarnold> I don't think "fit on a cd" has been a goal for a  very long time..
[18:21] <kyrofa> sarnold, exactly
[18:23] <Unit193> sarnold: Considering even Lubuntu is having issues with that? :)
[18:23] <ogra_> no, but fit on 1G usb keys (or sumething along these lines was the argument when it was bumped)
[18:24] <ogra_> there was a discussion on the ubuntu-devel ML ... a few years ago :)
[18:24] <ogra_> probably time to re-visit it
[18:24] <kyrofa> ogra_, ah, then that bug message should perhaps be revamped as it specifically mentions not fitting on a CD being the reason that it's a bug
[18:24] <slangasek> kyrofa: LP #1289259, and it is a bug that our images and our declared image size limits don't match
[18:25] <kyrofa> slangasek, ah, very good thank you
[19:47] <jtaylor> doko: what was the reason for this change: https://launchpad.net/ubuntu/+source/pyzmq/15.2.0-0ubuntu3
[19:51] <doko> jtaylor, syntax errors, and it's py3 only
[19:52] <doko> jtaylor, what was the reason to remove the test_asyncio.py module? ;)
[19:52] <jtaylor> hm its not supposed to be py3 only
[19:53] <jtaylor> but indeed it is
[20:01] <doko> jtaylor, 2.7 doesn't have asyncio
[20:01] <jtaylor> doko: but cython has
[21:08] <doko> jtaylor, well, then cython is wrong if it accepts this for 2.x, isn't it?
[22:45] <nacc> Pharaoh_Atem: thanks
[22:48] <Pharaoh_Atem> nacc: actually don't update to it, because I tried to make an update for the Fedora package, and the build system is doing weird things
[22:49] <Pharaoh_Atem> the code has remained substantially the same, but something is wrong with the build system, so I'd leave it be for now
[22:49] <Pharaoh_Atem> https://www.redhat.com/archives/libvir-list/2016-April/msg01348.html