[01:44] <rnetocombr> Somebody has news about bug: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1532226 ? It is fixed for tomorrow ? Devs need help testing ?
[05:25] <cpaelzer> good morning
[05:25] <alkisg> Good morning
[05:36] <Unit193> alkisg: So what'd you end up doing for firefox addons?
[05:36] <alkisg> Unit193: I packaged the .xpi myself, for adblock plus
[05:37] <alkisg> So now it's signed and works fine, but it's against the debian's desires about compiling everything from source, so it's not a solution that can be applied there
[05:37] <Unit193> So signed xpi "binary" blob?
[05:37] <Unit193> Ah, yep.
[05:39] <alkisg> At what time is Xenial going to be released today?
[05:39] <alkisg> (Mate, specifically...)
[05:44] <nhaines> alkisg: there is no set time of release.
[05:45] <alkisg> Thanks :)
[05:47] <cpaelzer> Hi, it might just be that this is my first release that I experience internally, but is there something smarter to get around "ubuntu-distro-info: Distribution data outdated" until it is updated than
[05:47] <cpaelzer> echo "16.10,Yummy Yggdrasil,yummy,2016-04-21,2016-10-18,2017-07-18" >> /usr/share/distro-info/ubuntu.csv
[05:48] <cpaelzer> since this is a public channel, I juts made something up with Y's in it - no real codenames
[05:49] <cpaelzer> well even then it surely won't find a yumma
[05:49] <cpaelzer> yummy, so that will only make ubuntu-distro-info happy, but not work at any later stages
[05:51] <cpaelzer> the following somewhat works for me - for now "16.10,Y not here Yet,xenial,2016-04-21,2016-10-18,2017-07-18"
[05:51] <cpaelzer> please let me know if there are better ways
[06:50] <pitti> Good morning
[07:01] <ottohak> \join #xubuntu
[07:54] <darkxst> where does the grub config come from?
[07:54] <darkxst> bug 1572874
[08:39] <alkisg> darkxst: it comes from /etc/default/grub, GRUB_CMDLINE_LINUX_DEFAULT
[08:43] <darkxst> alkisg, right, what I mean is what sets the config, that is not just some static file installed by grub
[08:44] <alkisg> darkxst: grub postinst uses /usr/share/grub/default/grub as a template to set that file
[09:23] <darkxst> alkisg, oh I see, trusty never specified "splash"
[09:23] <darkxst> and I guess it doesnt get merged in on upgrade
[09:24] <pitti> indeed, the default changed in xenial during the merge
[09:24] <pitti> didrocks: ^ (right?)
[09:24] <pitti> so this sounds worth a plymouth SRU that adds the flag on upgrade
[09:24] <yeehi> At what time today will the 16.04 final release be made available?
[09:24] <pitti> darkxst: mind filing a bug?
[09:25] <pitti> yeehi: 10 minutes later for everyone who asks :)
[09:25] <darkxst> pitti, already did
[09:25] <yeehi> haha! Thank you pitti!
[09:25] <pitti> darkxst: ah, sorry, can't read 5 lines of scrollback
[09:26] <pitti> darkxst: bug updated
[09:30] <darkxst> pitti, what about GRUB_CMDLINE_LINUX? none of those exist on a clean xenial install
[09:30] <darkxst> GRUB_CMDLINE_LINUX="find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US"
[09:31] <pitti> that looks like a grub line from a live system or so, not from an install
[09:31] <darkxst> it was a 14.04.4 install
[09:32] <alkisg> He might have pressed f6 while installing, and inserted a --- somewhere in the cmdline, so then ubiquity copied them to the installed system
[09:32] <darkxst> alkisg, no, I didnt touch f6
[09:33] <alkisg> darkxst: maybe you installed via usb, made by some tool that inserted that --- ?
[09:34] <darkxst> it was an ISO Attached to vmware, and pretty certain that was just installed through the usual greeter
[09:35] <pitti> darkxst: hm, that looks like a very strange command line then; preseed? auto?
[09:35] <alkisg> I think vmware has some wizard for installing OSes, maybe that was the source of that strange cmdline?
[09:35] <pitti> ah, that could be
[09:36] <didrocks> pitti: yeah, the default changed for this
[09:46] <darkxst> in that case maybe vmware is also messing with the _DEFAULT value
[10:36] <hikiko> hello
[10:37] <rbasak> o/
[10:37] <hikiko> is this the right channel to ask some questions on the SRU process? :)
[10:37] <hikiko> hi rbasak :D
[10:37] <rbasak> I think it's the most appropriate place given your question, yes :)
[10:38] <hikiko> well, I'm trying (for the 1st time) to SRU a change in compiz
[10:38] <rbasak> Could you please ask your question again to give others context? Then others can help you too.
[10:38] <hikiko> I found these instructions:
[10:38] <hikiko> https://wiki.ubuntu.com/StableReleaseUpdates
[10:38] <hikiko> and I'm trying to follow the steps
[10:39] <hikiko> basically I want to SRU the change on trusty
[10:40] <hikiko> so I've downloaded the orig.tar.gz from here: https://launchpad.net/ubuntu/+source/compiz/1:0.9.11.3+14.04.20150313-0ubuntu1
[10:40] <hikiko> and I applied the change with quilt following these instructions:
[10:40] <hikiko> http://packaging.ubuntu.com/html/patches-to-packages.html
[10:41] <rbasak> A source package actually consists (usually) of three files. You want them all, and then you can use tooling that's designed to work with them.
[10:41] <hikiko> I didn't edit/change anything else except of the code
[10:41] <rbasak> I suggest you use "pull-lp-source compiz trusty" to download the source package files for compiz that's current on trusty. The tool will also unpack the source tree for you.
[10:41] <hikiko> so I have to apply the changes to every one?
[10:42] <rbasak> The tooling takes care of all of this for you. Really your change will only go in the debian tarball and regenerate your dsc for you. The orig file is never supposed to change for a given upstream version.
[10:43] <rbasak> Then add the quilt patch to the source tree that pull-lp-source unpacks for you.
[10:43] <rbasak> Use the "dch" tool to add the changelog entry, or edit debian/changelog directly if you wish.
[10:45] <hikiko> alright :) thank you rbasak, I'm going to start the process from the beginning, I'll ping you again if I have any problems...:D (thanks!)
[10:45] <rbasak> No problem. Thank you for spending your time helping to make Ubuntu better!
[10:52] <mwhudson> today i appeared to discover that quilt chokes completely on files with spaces in their name, does that sound right?
[11:16] <mapreri> are we without name for the next release also this time?  so just about everything will be again blocked for days until mark announces the name?
[11:16] <mapreri> or maybe i'm just worrying for nothing.
[11:18] <nhaines> mapreri: don't be silly... it's xenial+1!
[11:19] <mapreri> heh
[11:28] <rbasak> Come up with a comedy name and use that instead.
[11:29] <rbasak> "Yakkety Yak"
[11:30] <Odd_Bloke> Yoloing Youngster
[11:31] <mapreri> we should be able to upload stuff to the 'devel' suite :)
[11:31] <nhaines> Sure, and 'grumpy' was going to be a perpetual 'devel' channel.  :)
[11:32] <mapreri> #ubuntu-grumpy
[11:32] <rbasak> Grumpty Gruffalo
[11:32] <rbasak> Grumpy
[11:38] <cjwatson> All this would be a lot easier (though still not trivial!) if the publisher were diskless, but that'll take a while.
[11:38] <cjwatson> At least some of the problems are because casual distroseries name changes have quite a lot of implications for what gets slapped on disk.
[11:39] <wgrant> It would still be difficult.
[11:39] <wgrant> The social solution is much easier than the technical one :)
[11:39] <cjwatson> Certainly.
[11:39] <wgrant> I sadly can't harrass Mark in person this year.
[12:03] <loganaden> hoi
[12:04] <loganaden> we have a patch for nagios-plugins for 15.10, that removes support for sslv3 when openssl is compiled with no-ssl3: https://code.launchpad.net/~pirabarlen-cheenaramen/ubuntu/wily/nagios-plugins/crypto-fix/+merge/292494
[12:04] <loganaden> backported from upstream
[12:04] <loganaden> https://tools.ietf.org/html/rfc7568 <- SSLv3 is no longer considered secure
[12:04] <loganaden> feedback welcomed
[14:25] <Bluefoxicy> trying to overwrite '/usr/lib/jvm/java-9-openjdk-amd64/include/linux/jawt_md.h', which is also in package openjdk-9-jdk-headless:amd64 9~b114-0ubuntu1
[16:24] <stgraber> \o/
[16:24] <infinity> @pilot out
[18:47] <kyrofa> jdstrand, bug #1573188 relating to the discussion yesterday
[19:00] <Pharaoh_Atem> congratulations on releasing Ubuntu 16.04 LTS :)
[19:02] <jdstrand> kyrofa: thanks, commented in bug
[19:18] <Pharaoh_Atem> can anyone help me with this? https://paste.fedoraproject.org/358315/66065146/
[19:20] <sladen> Pharaoh_Atem: can we have some context?  Is this trying to install 'ifupdown' on Fedora using 'alien' or some such?
[19:21] <Pharaoh_Atem> I'm trying to add to the Open Build Service the ability to build native Ubuntu 16.04 packages
[19:22] <Pharaoh_Atem> here's the full log: http://paste.fedoraproject.org/358318/61266534/
[19:22] <sladen> Pharaoh_Atem: okay.  Things like 'ifupdown' are low-level networking, that are unlikely to build/run/do anything useful except on Debian-based systems
[19:22] <Pharaoh_Atem> interestingly, it works fine in 15.10 and older
[19:22] <Pharaoh_Atem> as well as Debian 7 and 8
[19:23] <sladen> Pharaoh_Atem: those are useful datapoints to know
[19:25] <Pharaoh_Atem> I'm not sure what changed to cause this to break
[19:25] <sladen> Pharaoh_Atem: are you able to get into the machine?  And/or get a shell within the machine
[19:25] <sladen> Pharaoh_Atem: then we can try running things manually
[19:25] <Pharaoh_Atem> let me see if I can
[19:26] <sladen> Pharaoh_Atem: and bisecting between a working and non-working ifupdown package
[19:43] <sladen> Pharaoh_Atem: any luck
[19:44] <sladen> Pharaoh_Atem: http://packages.ubuntu.com/search?keywords=ifupdown   shows the various published versions
[19:46] <sladen> Pharaoh_Atem: from there it's possible to find the .deb  eg. http://mirrors.kernel.org/ubuntu/pool/main/i/ifupdown/ifupdown_0.8.10ubuntu1_amd64.deb
[19:46] <sladen> Pharaoh_Atem: /etc/init.d/networking then contains '#  Required-Start:    mountkernfs $local_fs urandom'
[19:48] <sladen> Pharaoh_Atem: trying to work out what 'urandom' is required for  (guessing something like IPv6 randomisation
[19:49] <sladen> Pharaoh_Atem: and I'm more puzzled for 'mourtkernfs'
[19:51] <sladen> Pharaoh_Atem: http://changelogs.ubuntu.com/changelogs/pool/main/i/ifupdown/ifupdown_0.8.10ubuntu1/changelog  points at "* Allow "hwaddress random" to generate a random MAC address." from pitti
[19:51] <sladen> Pharaoh_Atem: (originally added by guus in Debian; merged + uploaded into Ubuntu by pitti)
[20:00] <Pharaoh_Atem> sladen: brb
[20:18] <Pharaoh_Atem> sladen: back
[20:18] <Pharaoh_Atem> I'm unable to get into the image :/
[20:18] <Pharaoh_Atem> I think I'm going to have to force it to use a chroot instead to see if I can manipulate the environment
[20:19] <sladen> Pharaoh_Atem: if this is kvm, can you connect to the terminal/serial port?
[20:19] <Pharaoh_Atem> when the build fails, OBS shuts down the VM :(
[20:19] <Pharaoh_Atem> and I tried to run the command to start it, and that didn't work
[20:19] <sladen> Pharaoh_Atem: perhaps OBS has (or needs) a --preserve option
[20:20] <Pharaoh_Atem> the image is here
[20:20] <sladen> Pharaoh_Atem: or --no-detach etc
[20:20] <Pharaoh_Atem> I just don't know how to start it
[20:21] <sladen> Pharaoh_Atem: qmeu <image>
[20:49] <Pharaoh_Atem> sladen: so I was able to rebuild the error in a chroot
[21:19] <dasjoe> kirkland: I stumbled over another tool you wrote, ssh-import-id. Nice!
[21:20] <kirkland> dasjoe: ;-)
[21:20] <kirkland> dasjoe: here's a non-comprehensive list: http://blog.dustinkirkland.com/p/open-source-contributions.html
[21:23] <dasjoe> kirkland: right, I've used some of those before. Happy release day! Also, I'm a bit stuck right now, I'm trying to replace https://gist.github.com/dasjoe/d12a8061bee56a966359d046a61161c6#file-xenial-on-zfs-sh-L202-L204 with "sudo -u dasjoe ssh-import-id dasjoe" which fails due to $HOME still being /root
[21:25] <dasjoe> Fixed, "sudo -Hu"
[21:32] <kirkland> dasjoe: yep.
[21:59] <sladen> Pharaoh_Atem: excellent.  Try commenting out the two 'dependencies' and then run it and see whether it complete
[21:59] <Pharaoh_Atem> sladen: so how do I do that?
[22:02] <sladen> Pharaoh_Atem: 20:44 < sladen> Pharaoh_Atem: /etc/init.d/networking then contains '#  Required-Start:    mountkernfs $local_fs urandom'
[22:02] <Pharaoh_Atem> should I delete that, then?
[22:03] <Pharaoh_Atem> alright, now I deleted them
[22:03] <sladen> Pharaoh_Atem: rather than deleteing it completely, perhaps remove the two words 'mountkernfs' and 'urandom' that it was complianing could not be started
[22:04] <Pharaoh_Atem> sladen: it set up now
[22:04] <Pharaoh_Atem> so deleting mountkernfs and urandom fixed it
[22:04] <sladen> Pharaoh_Atem: right, so these appear not be hard depencies
[22:05] <Pharaoh_Atem> sadly, there's no chance of this getting fixed in xenial :(
[22:05] <Pharaoh_Atem> I tried to bring this up when I first encountered it last month, but no one was able to figure it out
[22:05] <Pharaoh_Atem> or rather, had time to
[22:08] <slangasek> the xenial SRU queue is open for bugfixes
[22:14] <mwhudson> ah yeah, i should stuff something into that!
[22:15] <doko> where is y?
[22:16] <sladen> Pharaoh_Atem: please could you review  https://bugs.launchpad.net/ubuntu/+bug/1573275  and subscribe yourself
[22:17] <Pharaoh_Atem> sladen: confirmed
[22:17] <Pharaoh_Atem> I'm actually "ngompa13" on LP
[22:19] <sladen> Pharaoh_Atem: I have subscribed 'Neal Gompa', but it perhaps makes it easier to follow-up on the bug report and get back in contact if it's clear what your various/preferred aliases are and the best way to make contact
[22:25] <Pharaoh_Atem> sladen: done
[22:25] <Pharaoh_Atem> I love LP's inability to let me edit comments </sarcasm>