[05:00] <pitti> Good morning
[05:03] <Unit193> Howdy.
[05:45] <pragomer> how can I customise boot of ubuntu-iso such as setting "try ubuntu" to default? I read some tutorials but they are about isolinux.cfg and this file is no longer used in 14.04 or not?
[06:29] <dholbach> good morning
[07:03] <jasabella> hi there? :)
[07:46] <LocutusOfBorg1> hi folks, any news about the development of w release?
[07:47] <Unit193> Stiiiiiiiiiiill holding on.
[08:00] <hyperair> uh oh
[08:00] <hyperair> i just dputted a bunch of packages by mistake into ubuntu
[08:00] <hyperair> instead of a ppa
[08:00]  * hyperair groans
[08:00] <hyperair> oh it's all rejected
[08:00] <hyperair> yay!
[08:02] <pitti> hyperair: they get rejected or land in UNAPPROVED where we can easily reject them manually :)
[08:02] <pitti> hyperair: and nothing new in https://launchpad.net/ubuntu/vivid/+queue?queue_state=1
[08:02] <hyperair> yeah they were all targeted at existing utopic and below
[08:52] <Mirv> hyperair: that's why I've "default_host_main = notspecified" in my .dput.cf that I only comment out when I know I want to upload to ubuntu :)
[08:52] <hyperair> Mirv: yeah well, mine too
[08:53] <hyperair> this was a brain fart
[08:53] <hyperair> i explicitly told dput to dput to ubuntu
[08:53] <Mirv> heh
[08:53] <hyperair> nothing can save you from that ;-)
[08:53] <Unit193> dput-ng either of you, btw?
[08:53]  * hyperair hasn't tried
[08:53]  * hyperair is an old-school person
[08:53] <hyperair> no bzr for me either
[08:54] <Mirv> haven't tried either
[08:54] <Unit193> hyperair: Why not?  Fastest way to get confused!
[08:54] <hyperair> Unit193: yeah that
[08:54] <hyperair> Unit193: also git-bzr fails spectacularly on too many things, and i can't stand bzr's interface
[08:55] <Unit193> hyperair: I, err, used rsync --exclude .bzr/ mypackagedir/ ubuntu-bzr-package/  once. >_>
[08:56] <hyperair> lol
[09:34] <dholbach> willcooke, mhall119: is https://blueprints.launchpad.net/ubuntu/+spec/convergence-1505-snappy-desktop and https://blueprints.launchpad.net/ubuntu/+spec/convergence-1505-snappy-on-phone-and-desktop the same?
[09:35] <willcooke> dholbach, yeah rather looks like it
[09:36] <willcooke> don't mind which one stays, but would like to transition the subscribers from one to the other
[09:36] <dholbach> I'm just wondering if one session is not going to be too little time
[09:36] <willcooke> hrm
[09:36] <dholbach> ok... I'll leave that in your hands :)
[09:37] <willcooke> dholbach, please delete your one and I will make sure those folk are sub'd to the other one
[09:37] <dholbach> ok
[09:40] <willcooke> I dont really want a 2 hour session where we end up bike shedding the topic to death
[09:41] <willcooke> we've already got some good thought behind it from the sprint, so I want to stay focused on those topics and get feedback
[09:41] <willcooke> rather than a free for all
[09:41] <willcooke> if we uncover some interesting topics then I will schedule another session about that topic
[09:42] <dholbach> sure
[09:53] <Laney> mardy: so you want me to upload or are you doing the silo thing?
[10:31] <pragomer> how can I set the isolinux boot menu of ubuntu so that it is always been shown (the default is that I have to press a key) ?
[10:33] <highvoltage> pragomer: best to ask in an isolinux related channel or forum
[10:34] <pragomer> ok thanks
[10:35] <highvoltage> pragomer: they might send you back to ubuntu since (afaik) it's an ubuntu patch, so you might have to end up (gasp) reading the docs, http://www.syslinux.org/wiki/index.php
[10:36] <pragomer> mm. yes.. I read a lot.. but this specific thing ubuntu makes.. I cannot find this "tweak"
[10:36] <pragomer> that "always show" menu thing..
[10:38] <highvoltage> pragomer: you'll probably have to use gfxboot to create a new gfxboot binary
[10:39] <highvoltage> (gfxboot-themes package might help you find what you need to change in the gfxboot source)
[10:39] <pragomer> I thought I take the isolinux-folder from official cd... edit some files.. and put it back in remaster-process.. did I think too simple?
[10:40] <cjwatson> It's not well-documented, but you need to remove hidden-timeout from gfxboot.cfg
[10:41] <cjwatson> IIRC that's embedded in /isolinux/bootlogo
[10:42] <pragomer> well thats my gfxboot.cfg:   http://pastebin.com/5QcdTTtQ
[10:42] <cjwatson> So you'd need to unpack and repack that, although you don't need to use gfxboot as such for that; see http://bazaar.launchpad.net/~ubuntu-cdimage/debian-cd/ubuntu/view/head:/tools/boot/vivid/boot-amd64, down near the end
[10:42] <pragomer> I tried hidden=0 before.. what did not work...
[10:42] <cjwatson> For trusty and earlier you can just edit gfxboot.cfg directly, but for >= utopic you need to repack bootlogo
[10:44] <pragomer> ups... how could I do this (I am not a programer just a bash-script-kiddie :-) )    no, seriously... how to unpack/repack.. have you further advice? would be great
[10:44] <highvoltage> pragomer: for that you'd have to go read the docs, I'm afraid it's far out of the scope for #ubuntu-devel
[10:45] <pragomer> ok, but thanks in any case
[10:45] <cjwatson> I linked to the code
[10:47] <cjwatson> line 632 onwards in boot-amd64 linked above, you basically just need to fiddle with the filenames and ensure you have an updated gfxboot.cfg in place before you do the repack step near the end
[10:47] <cjwatson> highvoltage: what docs
[10:47] <pitti> cjwatson, wgrant: do we want to go ahead with the pkg-create-dbgsym SRU today, or is this blocked on something still, from your POV?
[10:48] <cjwatson> I was annoyed about the upstream syslinux change myself, but it wasn't feasible to undo unfortunately, hence the comment I left in that code noting that it's not ideal because of making customisation harder
[10:48] <cjwatson> pitti: I see no reason not to go ahead with it
[10:48] <cjwatson> pitti: All your test packages pass now, right?
[10:48] <pitti> cjwatson: yes
[10:50] <highvoltage> cjwatson: s/docs/gfxboot-docs + code link/g
[10:51] <pitti> cjwatson: I do not want to self-accept, and neither of us three is in ~ubuntu-sru; do you happen to have any of https://launchpad.net/~ubuntu-sru/+members at the sprint?
[10:51] <cjwatson> highvoltage: sorry but none of the docs nor source packages you've referred to are actually relevant.  The reason I ask this question is that I'm fairly sure this is undocumented
[10:51] <cjwatson> highvoltage: AFAIK the code links I gave are the most useful "documentation" that exists of this
[10:52] <cjwatson> well also the code in the gfxboot-theme-ubuntu source package, grep for hidden-timeout
[10:52] <cjwatson> but I don't think it's right to tell people to go read the nonexistent docs
[10:52] <cjwatson> (and yes, it's totally my fault that the docs don't exist, but ...)
[10:53] <cjwatson> and given that situation, I think it's entirely reasonable for people to ask in #ubuntu-devel
[10:53] <highvoltage> cjwatson: ah, my bad then. I recently made some changes to a few ubuntu boot screens and found the isolinux and gfxboot docs really helpful, so I thought it might be the case for pragomer as well
[10:53] <cjwatson> pitti: I'm not at the sprint
[10:53] <cjwatson> highvoltage: the hidden-timeout thing is a bit of a special hack
[11:00] <pragomer> cjwatson: as I am not a "developer" but just somebody that tries a remastering as "hobby"... what files do I have to change now? Or cant you tell it?
[11:02] <cjwatson> pragomer: You'd have to perform the procedure at the end of boot-amd64 above by hand to unpack and repack /isolinux/bootlogo using cpio
[11:02] <cjwatson> I'm afraid it will require some experimentation and reading that code, but shouldn't require writing new code
[11:02] <pragomer> cpio.. I dont know that.. but will have a look at it. Thanks
[11:03] <Unit193> cpio is fuuuuuuuunn.
[11:04] <pragomer> is it just for unpacking?no.. because unpacking the file "ini" thats inside the "bootlogo" file is also possible with gui archiver..
[11:05] <pragomer> but what do I have to do with the file "init"... is it "compiled", "hardcoded" ?
[11:05] <cjwatson> Don't touch it.
[11:05] <cjwatson> It's compiled from the gfxboot-theme-ubuntu source.
[11:05] <cjwatson> You don't need to change it for this.
[11:06] <cjwatson> As for bootlogo itself, I have no idea whether a GUI archiver will be able to repack the file in a way that syslinux/gfxboot will be able to read back.  You're on your own if you try that.
[11:07] <cjwatson> To change hidden-timeout, you only need to modify gfxboot.cfg in the bootlogo archive, not any other files.
[11:07] <pragomer> but there is only this one file "init" inside the archive "bootloader"... so if I should not touch the "init"-file... what do I do else to "edit" the default-behavior?
[11:08] <cjwatson> That's not true for at least the vivid desktop image.
[11:08] <cjwatson> What release are you using?
[11:08] <pragomer> oh.. there IS NO gfxboot.cfg in this archive... gfxboot.cf is located outside.. in /isolinux folder
[11:08] <pragomer> I am using Xubuntu 14.04
[11:08] <cjwatson> So why did you waste our time not saying that earlier?
[11:08] <cjwatson> 11:42 <cjwatson> For trusty and earlier you can just edit gfxboot.cfg directly, but for >= utopic you need to repack bootlogo
[11:08] <cjwatson> 14.04 = trusty
[11:09] <cjwatson> So all this stuff about unpacking/repacking doesn't match your case
[11:09] <pragomer> ups.. I am so sorry.. I did not realize that earlier..
[11:09] <cjwatson> When you asked about repacking following that, I assumed that you must be using at least 14.10 ...
[11:09] <pragomer> so what would I have to change here: http://pastebin.com/5QcdTTtQ
[11:09] <cjwatson> So, have you tried simply removing the hidden-timeout file from /isolinux/gfxboot.cfg and remastering the image?
[11:10] <cjwatson> Er, the hidden-timeout line
[11:10] <Unit193> cjwatson: Sorry for the dumb question, but do you know why they went with the cpio change?
[11:10] <cjwatson> I'd expect that to be enough
[11:10] <pragomer> ah, no I just set it from "2" to "0"... wait.. I am just trying to remove it and start my remastering script.. 3minutes :-) Thank you very much cjwatson
[11:11] <cjwatson> I'm surprised setting it to 0 didn't work too, but do try removing it.  Also I'd strongly suggest checking the resulting image to make sure that the file there is actually what you expect it to be.
[11:11] <cjwatson> Unit193: http://www.zytor.com/pipermail/syslinux/2014-June/022264.html and thread may help for context
[11:12] <pragomer> cjwatson: Yes, I checked it - pausing the script at that place - and "0" was repeated to the target...
[11:13] <cjwatson> It was basically the removal of the COMBOOT API which gfxboot was relying on to read files off the ISO9660 fs in its bytecode
[11:14] <Unit193> Will read the full thread later.  Thanks.
[11:14] <pragomer> I did not work :-(   I double checked... the removed hidden-line was repeatet on the targets iso... but no effect
[11:15] <cjwatson> pragomer: What does the boot screen look like?  Do you get the keyboard + accessibility icon at the bottom until you press a key?
[11:16] <pragomer> Yes.. exactly like that... so like nothing did change..
[11:18] <pragomer> perhaps I make another mistake.. I also tried to remove some of the languages in the list, what I thought would be in the file "langlist"... either that wasnt sucessfull although this textfile only contained 2 languages... it like everthing is ignored..
[11:23] <cjwatson> pragomer: I think you have something else wrong, because I just tried my own advice on a Xubuntu 14.04 image I had lying around and it works fine for me.
[11:24] <cjwatson> pragomer: That is, I just removed hidden-timeout from gfxboot.cfg, nothing else, and that's enough for the gfxboot menu to be shown by default.
[11:24] <Unit193> cjwatson: Speaking of which, for newer releases does /etc/casper/casper.conf (or whichever) still function as expected?
[11:24] <cjwatson> Unit193: I'm not sure, sorry.
[11:24] <Unit193> cjwatson: Alright, thanks.  Though, you may want to bump the timeout for selection.
[11:25] <cjwatson> Unit193: s/you/somebody who is still working on the installer/ :-)
[11:25] <cjwatson> Unless you mean in advice to pragomer
[11:25] <Unit193> you being generic, when changing gfxboot.  50 => 300
[11:26] <cjwatson> Ah right.  Yes, indeed.  I was going to mention that earlier but got sidetracked by realising that the cpio stuff was a red herring here.
[11:26] <cjwatson> That's in isolinux.cfg and prompt.cfg.
[11:30] <pragomer> so this is my prompt.cfg
[11:30] <pragomer> http://pastebin.com/rUnNCr0v
[11:30] <pragomer> and my isolinux: http://pastebin.com/MjE5kA3e
[11:30] <pragomer> what would I have to edit?
[11:31] <cjwatson> "timeout 50" => "timeout 300"
[11:32] <cjwatson> (But this is not going to help the problem that your fundamental remastering process apparently isn't working for some reason.  You need to figure that out first.)
[11:39] <pragomer> so.. to finish it... the right file would be gfxboot.cfg, right?
[11:40] <pragomer> prompt and isolinux ?
[11:41] <cjwatson> Yes
[11:42] <pragomer> ok, thank you so much.
[11:47] <wgrant> cjwatson, pitti: I'll try to catch Stéphane or Steve about it.
[11:49] <cjwatson> pragomer: Hopefully somebody can help you with your remastering if you're still stuck with changes not having any effect.  (It's often worth trying something really obvious there like changing menu item text just so that you aren't confused about whether some configuration file change might or might not affect anything.)  I'm afraid I have a bit too much to do right now though ...
[11:55] <pragomer> thank you in any case cjwatson.. yes I tried to change something obvious.. changed menu text.. that wasnt realized either..
[11:56] <cjwatson> Are you booting the result in an emulator such as kvm, to avoid silly mistakes like booting the wrong physical USB stick (not that I've ever done that, oh no)?
[11:56] <Unit193> cjwatson: Last one in my sleep deprived state, how's git lookin'?
[11:57] <cjwatson> Unit193: Merge proposals almost work, just polishing up the preview diff stuff.  We're very nearly ready to deploy to production
[11:57] <cjwatson> There'll be lots of gaps of course
[11:58] <Unit193> Awesome, glad to hear it!  I like what I've been playing with.  And yeah, but the basics will be there, which is great.
[11:58] <cjwatson> You've been playing with qastaging?
[11:59] <Unit193> Yep, though honestly expected things to get wiped off there.
[11:59] <cjwatson> Yeah, they will eventually.
[12:00] <cjwatson> At the very least the next full qastaging database refresh will have the effect of forgetting all the backend repository paths.
[12:24] <pragomer> cjwatson: could it be possible that no changes are made because "my files" in isolinux have different rights? (on cd e.g. they are not writable but I had to chmod them to write to...)
[12:28] <cjwatson> pragomer: I wouldn't expect that to matter
[12:39] <arges> @pilot in
[12:41] <pragomer> cjwatson: ok, thank you again very much
[12:57] <pragomer> cjwatson: can you imagine a reason for this: I "rm -rf" the /isolinux folder but I find it again on the iso after build process? do you think you could have a short look at my script?
[12:58] <pragomer> cjwatson: the script is here:   http://pastebin.com/EcMVKSQF
[13:02] <cjwatson> pragomer: ${WORK}/new corresponds to the live filesystem, not to the top-level ISO9660 filesystem.  As far as I can see you should be referring to ${WORK}/isolinux rather than ${WORK}/new/isolinux throughout.
[13:02] <cjwatson> That probably explains all your problems.
[13:02] <arges> tseliot: hi. Can you verify bug 1443016 for the fglrx updates? Thanks
[13:04] <tseliot> arges: hi, actually yesterday I uploaded a new revision that fixes another regression. So maybe I should really verify that revision when it's approved
[13:05] <arges> tseliot: ok add that comment in the bugs where necessary, i'll review that in the queue today hopefully
[13:06] <tseliot> arges: ok, I'll be waiting for the new packages to land and then I'll add the feedback
[13:07] <arges> cool thanks
[13:07] <Unit193> mdeslaur: Awesome, thanks!  Also, got an email, mine got sponsored into Debian too. (re: icecast)
[13:07] <mdeslaur> Unit193: nice! :)
[13:07] <pragomer> cjwatson: Mm... I thought  ${WORK}/new/ would be the "root" folder of the iso/cd...  did not know that it would be possible to be more "root" :-)   ahm you know what I mean? I will try to copy the contenct of my isolinux to where you said.. just a moment
[13:09] <cjwatson> pragomer: There are two filesystems on the image.  One of them is what's visible if you just mount the image directly; the other is nested within that and is what becomes effectively the root filesystem when you boot the image in live CD style.  The isolinux stuff lives in the outer of those two.
[13:10] <pragomer> cjwatson: Ah ok... it's basic knowledge.. but I did not know that.. thank you .. I will try it..
[13:14] <pragomer> cjwatson: ok.. now I see... the files are NOT copied to the iso...  damned... but it does not work either when copying /daten/ubunturemaster/files/isolinux to $WORK/isolinux      How can I add isolinux to the right filesystem on cd?
[13:15] <cjwatson> pragomer: Ah, sorry, looks like I meant ${WORK}/ubuntu-livecd/isolinux
[13:16] <pragomer> ah ok, I'll try :-)
[13:20] <pragomer> cjwatson: Hey cjwatson: you are so much my hero :-) :-) now everything I edited works just fine! this was my fault.. copied it to the wrong filesystem..  Thank you so so much
[13:23] <cjwatson> pragomer: Ah, brilliant, glad to have solved that mystery
[13:23] <pragomer> *thumbsup*  Thanks again and have a nice day cjwatson
[13:24] <cjwatson> Enjoy
[13:26] <pragomer> thanks and bye. just found you at launchpad (so I know now how to look my here :-) )
[13:55] <mardy> Laney: hi! I didn't see activity on my MPs, so I guess you can dput them when you have the chance
[14:17] <Laney> mardy: fine, stand by to push them directly to trunk then please
[14:17] <Laney> will be doing it later this afternoon
[14:33] <mardy> Laney: ok
[14:33] <wgrant> pitti: The new pkg-create-dbgsym looks published everywhere in -proposed. Can I commandeer the ddeb-test PPA to test it?
[14:43] <doko> wgrant, pitti: please disable running the gcc tests when verifying this pkg-create-dbgsym fix
[14:48] <doko> bdmurray, barry: see my last email on the pip/requests issue. bdmurray, do you run pip on the distro, or in a virtual env?
[14:49] <pitti> doko: I did that in the test PPA already
[14:49] <doko> ahh, good
[14:49] <pitti> wgrant: please go nuts
[14:49] <pitti> wgrant: please reupload the gcc packages in the PPA, they have the tests disabled (build time of 1 h vs. 12 or so)
[14:51] <wgrant> pitti: Will do.
[14:52] <barry> doko, bdmurray a bit busy with other things atm, but i'll look again later today
[14:54] <wgrant> pitti: Copied into https://launchpad.net/~wgrant/+archive/ubuntu/p-c-d-test/+packages for clarity.
[14:54] <wgrant> All the buildds are mine.
[14:55] <infinity> wgrant: GIVE THEM BACK.
[14:55] <wgrant> :(
[14:55] <wgrant> mine
[14:56] <infinity> Greedy.
[14:56] <wgrant> I try.
[14:57] <josepht> you guys share or you're going to go to time-out. :)
[14:57] <infinity> 1 → 75 of 10 results
[14:57] <infinity> Well job, LP.  Well job.
[14:59] <wgrant> infinity: Better than timing out.
[15:00] <roaksoax> infinity: howdy! any updates on the MAAS SRU?
[15:00] <roaksoax> infinity: 1.7 SRU?
[15:01] <bdmurray> doko: on the distro
[15:03] <bdmurray> pitti: Even if a PPA is added to /etc/apport/native-origins.d/ apport doesn't have support for getting packages or ddebs from a PPA correct?
[15:03] <infinity> roaksoax: You know what they say: No news is good news.
[15:12] <pitti> bdmurray: right
[15:32] <infinity> wgrant: I'm cancelling all the powerpc/gcc builds in that p-c-d-test PPA to save some cycles and to save my own santy when they kill off VMs.  I assume you don't actually need all the arches for your test.
[15:33] <infinity> wgrant: Killing arm64 might not be a bad plan either.
[15:34] <infinity> Oh, I guess the VMs wouldn't have died, if the testsuites were disabled.
[15:34] <infinity> But still, cycles.
[15:36] <ricotz> infinity, https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+build/7344672 ;)
[15:41] <infinity> ricotz: It's trying as hard as it can.  Poor artigas.
[16:44] <Laney> mardy: bah, I'm going to run out of time again, got overtaken with other things
[16:44] <Laney> can someone else help? like maybe kenvandine? :)
[16:44] <kenvandine> mardy, what do you need?
[16:44]  * Laney thinks that you are accountish
[16:44] <kenvandine> oh
[16:45] <Laney> but maybe not :P
[16:45] <kenvandine> mardy, you know where to find me :)
[16:45] <Laney> kenvandine: sponsor SRUs for this https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1448969
[16:45] <Laney> NO
[16:45] <Laney> this: https://bugs.launchpad.net/account-plugins/+bug/1432613
[16:47] <kenvandine> Laney, mardy: doesn't look quick :)  i'm under pressure right now for a critical hotfix destined for rtm
[16:47] <kenvandine> so probably not today
[16:56] <whatsw> Hi, I haven't been able to find anything online about Ubuntu 15.10... what's it called?
[17:01] <teward> whatsw: FYI: asking in every channel is bad form
[17:01] <teward> just ask one place, wait for answers
[17:02] <whatsw> i didn t ask in every channel, only 3
[17:02] <whatsw> but oj
[17:02] <whatsw> ok
[17:02] <teward> !crosspost
[17:02] <teward> ^ that
[17:03] <teward> ('every channel' was a generalization - the practice of asking in only one location is still valid)
[18:52] <buildit> can i install ubuntu on my android device?
[18:54] <zequence> buildit: Try #ubuntu-touch
[18:55] <zequence> Also, https://developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/
[19:23] <buildit> i have a failed upgraded device
[19:23] <buildit> an upgrade gone bad
[19:24] <buildit> if i could install something that woulde make it work...
[20:28] <shadeslayer> doko: Debian python ping
[20:28] <shadeslayer> Installing python seems to be broken on sid :(
[20:28] <shadeslayer> ( wasn't sure where else to ping you )
[20:29] <shadeslayer> doko: http://paste.ubuntu.com/10944751/
[20:34] <infinity> shadeslayer: That's fixed in -4, except for the fun part where python build-depends on python, so it might take some untangling to get all the arches fixed.
[20:47] <shadeslayer> infinity: aw :(
[20:48] <shadeslayer> infinity: uh, I dont see it on https://tracker.debian.org/pkg/python-defaults
[20:50] <shadeslayer> it's blocking alot of my CI things :(
[20:54] <infinity> shadeslayer: You want python2.7, not python-defaults
[20:55] <infinity> shadeslayer: Or incoming: http://incoming.debian.org/debian-buildd/pool/main/p/python2.7/
[20:55] <shadeslayer> aha
[20:55] <shadeslayer> infinity: thanks
[23:17] <thms> Hi everyone.
[23:17] <thms> So I have a project for my company
[23:17] <thms> I basically want to "re-brand" ubuntu
[23:17] <thms> Means I'll use plymouth to change the splash/bootscren
[23:18] <thms> And from there I want to make a .iso that will use it. and also include some software that is not (for exemple flash, vlc, so on..)