[03:20] <mwhudson> ENODOKO
=== salem_ is now known as _salem
[04:38] <pitti> Good morning
[04:49] <tsimonq2> o/ pitti
[05:01] <pitti> hey tsimonq2, how are you?
[05:05] <tsimonq2> great pitti, you?
[05:06] <pitti> quite fine, thanks
=== pete-woods[fail] is now known as pete-woods
[10:37] <LocutusOfBorg> anybody willing to bootstrap fpc on powerpc?
[10:37] <LocutusOfBorg> the issue that prevented installation seems fixed, but I have no knowledge/access to machines to test it
[10:37] <LocutusOfBorg> infinity, ^^ :)
[10:37] <LocutusOfBorg> BTW the fixed version is already in yakkety-proposed (in some seconds)
=== hikiko is now known as hikiko|ln
[10:57] <Mirv> Does "Error in `/usr/bin/python': double free or corruption (out): 0x00003fff9c373c70" ring a bell? Seen on i386 and ppc64el autopkgtests (yade) after a successfull test run..
=== marcusto_ is now known as marcustomlinson
[11:17] <flexiondotorg> Now we are in feature freeze for yakkety is syncing with Debian now stopped?
[11:26] <ginggs_> flexiondotorg: yes, we are in debian-import-freeze as well, use 'requestsync'
[11:26] <flexiondotorg> ginggs_, Yeah, I was just read the docs :-)
[11:27] <cjwatson> Mirv: probably a bug in some extension or other
[11:28] <mdeslaur> @pilot in
=== udevbot changed the topic of #ubuntu-devel to: Xenial (16.04.1) Released! | Archive: feature freeze | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-xenial | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: mdeslaur
=== hikiko|ln is now known as hikiko
[11:34] <vooze> TheMuso: Hi, I wanted to hear if you wanted to test pulseaudio (bluetooth) with me? I haven't heard from you on https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324 - You can also email me: joakimkoed@gmail.com if you want :)
[11:34] <ubottu> Launchpad bug 1574324 in pulseaudio (Ubuntu) "pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)" [High,In progress]
[11:36] <smoser> pitti, i see your name https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809740 when digging on my related issue https://bugs.launchpad.net/cloud-images/+bug/1615751
[11:36] <ubottu> Debian bug 809740 in src:initramfs-tools "initramfs-tools: Completely ignores rootdelay" [Important,Fixed]
[11:36] <ubottu> Launchpad bug 1615751 in initramfs-tools (Ubuntu Yakkety) "ROOTDELAY= causes unnecessary delay in boot" [High,Confirmed]
[11:37] <smoser> it seems now that ROOTDELAY=300 means "please do 'sleep 300' in initramfs". Where before, it meant to do 'wait-for-udev 300', which waited up to 300 seconds until the necessary device appeared.
[11:38] <smoser> azure images have this rootdelay=300 cooked into them as it sometimes takes quite a while for azure disks to appear.  it used to mean that this worked well, now it means we sleep 300.
[12:11] <flexiondotorg> Laney, now that I have PPU for a package set can I action my own sync requests for those packages?
[12:11] <Laney> yes
[12:11] <flexiondotorg> Excellent.
[12:12] <flexiondotorg> Laney, So requestsync without -s will do the business?
[12:14] <pitti> smoser: ah, I remember -- indeed, this rootdelay= thing is FUBAR; TBH I don't see how to salvage it to anything remotely useful
[12:15] <pitti> smoser: IIRC, the problem was to define what "the necessary device" actually is
[12:15] <pitti> i. e. not just waiting for the root device, which we've done with udev's wait-for-root since 2006 or so
[12:16] <pitti> so if someone actually wants to use it, it's just a plain sleep(given_number) in the initramfs ATM, as there is no other definition of what it should do
[12:19] <ginggs_> flexiondotorg: you should be able to use 'syncpackage' for packages you can upload
[12:19] <flexiondotorg> ginggs_, Thanks. I'll read the man page now.
[12:20] <pitti> smoser: anyway, if you want to kill that sleep from initramfs-tools again, you have my full blessing :)
[12:34] <flexiondotorg> ginggs_, Thanks for the pointer. That was easy :-)
[12:35] <ginggs_> flexiondotorg: yw
=== _salem is now known as salem_
[12:52] <Odd_Bloke> Is there a convention for where documentation about a package's packaging should live within the package?
[12:55] <mgedmin> debian/README.source, I think
[12:57] <Odd_Bloke> Ah, yeah, that looks like it.
[12:57] <Odd_Bloke> mgedmin: Thanks. :)
[13:34] <smoser> pitti, right..
[13:34] <LocutusOfBorg> pitti, can you please run htslib testsuite of version 1.3.1-2ubuntu1 against python-pysam/proposed? thanks
[13:34] <smoser> i dont understand why we dont use 'wait-for-root'
[13:34] <smoser> and why debian doesnt use 'wait-for-root'
[13:35] <smoser> do you know that answer to that ?
[13:36] <cyphermox> juliank: hey; have you seen bug 1611010? I think there's an issue in apt in the pmstatus output, related to the changes to setting the locale
[13:36] <ubottu> bug 1611010 in apt (Ubuntu) "yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: ''" [Critical,Confirmed] https://launchpad.net/bugs/1611010
[13:37] <juliank> cyphermox: Alright, I'll forward this to DonKult, he's tackling these locale bugs
[13:37] <juliank> cyphermox: Or well, maybe the APT was too old. Need to check
[13:38] <cyphermox> thanks
[13:42] <juliank> I really hate locales
[13:42] <juliank> The fault is probably the strprintf(status, "pmstatus:dpkg-exec:%.4f:%s\n",
[13:43] <juliank> that's awkward
[13:43]  * juliank wants locale free sprintf()
[13:44] <juliank> Anyway, should be easy to fix
[13:50] <coreycb> arges, bdmurray: hello, we could use a review of the openstack SRUs for bug 1614131 if you have a moment this week
[13:50] <ubottu> bug 1614131 in nova (Ubuntu Xenial) "[SRU] OpenStack Mitaka point releases" [Undecided,New] https://launchpad.net/bugs/1614131
[13:55] <pitti> smoser: we *do* use wait-for-root
[13:55] <smoser> well, sort of
[13:55] <smoser> we use a '10' now
[13:55] <smoser> we used to use ROOTDELAY
[13:55] <pitti> smoser: Debian> presumably because it's linux specific and thus it wouldn't work under BSD; although ISTR that i-t has a shell polling loop for it which should roughly behave the same
[13:55] <smoser> http://paste.ubuntu.com/23081737/ <-- thats what i think to get it back to properly
[13:56] <smoser> pitti, right. it has a shell polling loop
[13:56] <smoser> and then (or before, i think actually) it does sleep $ROOTDELAY
[13:56] <smoser> why? no clue.
[13:56] <pitti> LocutusOfBorg: I think you mean the other way around; done
[13:57] <pitti> LocutusOfBorg: but note that http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#python-pysam is depwait on i386, so that won't help on at least i386
=== JanC is now known as Guest58470
=== JanC_ is now known as JanC
[14:16] <arges> coreycb: i can get to it tomorrow if tha'ts alwa6ys
[14:16] <arges> alright
[14:21] <LocutusOfBorg> pitti, not sure why archive admins didn't remove it yet
[14:24] <pitti> LocutusOfBorg: why remove?
[14:24] <LocutusOfBorg> python-pysam NBS/i386?
[14:25] <pitti> LocutusOfBorg: why would it be removed? its depwait needs to be resolved
[14:27] <coreycb> arges, that'd be great, thanks
[14:28] <LocutusOfBorg> pitti, remove all the reverse-deps on i386 too? Debian seems to have done that AFAICS
[14:28] <pitti> LocutusOfBorg: hm, that's not quite obvious; mind filing a bug for it? (sorry, meeting now)
[14:29] <LocutusOfBorg> yep thanks
=== dgadomski_ is now known as dgadomski
[15:36] <mdeslaur> @pilot out
=== udevbot changed the topic of #ubuntu-devel to: Xenial (16.04.1) Released! | Archive: feature freeze | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-xenial | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
=== Laney changed the topic of #ubuntu-devel to: Xenial (16.04.1) Released! | Archive: feature freeze, beta 1 freeze | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-xenial | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
[16:46] <infinity> LocutusOfBorg: Oh, nice.
[16:47] <infinity> LocutusOfBorg: I'll rebootstrap in a bit.
[16:49]  * tsimonq2 silently grumbles about the lack of capitalization in the topic
[16:50] <LocutusOfBorg> infinity, I hope it is *really* fixed
[16:51] <LocutusOfBorg> you might want to wait for elbrus to bootstrap it in Debian
[16:51] <LocutusOfBorg> as you wish
[16:51] <LocutusOfBorg> I don't want to have you loose time
[16:51] <infinity> LocutusOfBorg: It'll be trivial to do.  Also, lose, not loose. :P
[16:51] <LocutusOfBorg> true ;)
[16:51] <infinity> (pet peeve)
[16:51] <LocutusOfBorg> what is "trivial" for you, is impossible for me
[16:52] <LocutusOfBorg> and I would like to learn/have access to machines
[16:52] <LocutusOfBorg> debian porterboxes don't allow to install stuff as root
[16:54] <infinity> Installing as root wouldn't be strictly necessary for this.
[16:54] <LocutusOfBorg> mmm how? fpc needs fpc
[16:54] <LocutusOfBorg> or you want to cross compile it?
[16:54] <infinity> Sure, but you start with a chroot that has a glibc that doesn't break fpc.
[16:54] <LocutusOfBorg> and how do you test the built binaries on a real powerpc machine?
[16:54] <infinity> Then build the new one.
[16:54] <LocutusOfBorg> ok but debian has pre-built chroots
[16:55] <infinity> Yeah, use jessie.
[16:55] <LocutusOfBorg> mmm ok
[16:55] <LocutusOfBorg> and then upgrade the chroot to stretch?
[16:56] <LocutusOfBorg> or save the built binaries, unpack them and run ./fpcmk whatever fails
[16:56] <LocutusOfBorg> I did that when debugging it
[16:59] <LocutusOfBorg> thanks for trying it then
[17:00] <LocutusOfBorg> I trust more your checks rather than mine ;)
[17:06]  * LocutusOfBorg leaves
[17:12] <bdmurray> pitti, barry, mvo: Do you know enough about aptdaemon to figure out what's going wrong here? https://errors.ubuntu.com/problem/fc13839a8f16399991b1e1907d410c7f161d7fc9
[17:14] <barry> bdmurray: i don't but i did notice a warning about xenial hwe eol on a server of mine
[17:15] <bdmurray> barry: I added that stuff to Trusty and update-manager is crashing with the above a lot.
[17:16] <barry> bdmurray: offhand, no idea, sorry
[17:16] <bdmurray> barry: okay, thanks
[17:18] <lamont> it would appear that the yakkety virt-viewer has decided that it should, by damn, take focus every time there's a change in the screen.  Any clues on how to correct this utterly antisocial and stupid behavior on its part, other than "close the window"?
[17:19] <infinity> My PowerStation just decided it doesn't have a root filesystem.  That's not ideal.
[17:20] <lamont> infinity: you win on the suckitude scale
[17:21] <mvo> bdmurray: it smeels like a package dependencies problem, maybe something with libgl1-mesa-glx-lts-xenial: on trusty, e.g. if universe is missing or somesuch
[17:23] <bdmurray> mvo: universe missing - that sounds like a good lead.  Is there any way to get more information out of aptdaemon?
[17:23] <mvo> bdmurray: hm, in a trusty chroot I get a similar error "# apt install xserver-xorg-lts-xenial"
[17:24] <mvo> bdmurray: that is even with universe
[17:24] <mvo> bdmurray: so maybe something broken in the backport?
[17:25] <bdmurray> mvo: hmm, I did lots of HWE upgrade testing w/o a problem.
[17:26] <mvo> bdmurray: no idea, I just did a pbuilder-dist xenial login and sudo apt update; sudo apt install xserver-xorg-lts-xenial
=== sarnold_ is now known as sarnold
[17:32] <infinity> xnox: -updates should be fixed on mirrors in a couple of hours.
[17:44] <xnox> infinity, \o/
[17:44] <xnox> you are full of win =)
[17:44] <infinity> I'm full of something.
[18:10] <coreycb> arges, when you do the openstack review for me, can you reject the older uploads of nova/keystone/cinder from the review queue?  I just re-uploaded with the correct bug #.
[18:10] <arges> coreycb: ok
[18:10] <coreycb> arges, thanks
[18:16] <arges> coreycb: ok all set
[19:04] <infinity> xnox:
[19:04] <infinity> sower@z13-001:~$ apt-cache show s390-tools | grep ^Support
[19:04] <infinity> Supported: 5y
[19:04] <infinity> Supported: 9m
[19:04] <infinity> xnox: So, updates fixed, I'll worry about release later.
=== elbrus_ is now known as elbrus
[21:15] <infinity> juliank: What did you do to python-apt?
[21:15] <infinity> juliank: http://paste.ubuntu.com/23083200/
[21:15] <infinity> Or is that internal to apt-listchanges?  Hrm.
[21:16] <juliank> We never had a read_changelog
[21:16] <infinity> Yeah, maybe I should blame doko's last apt-listchanges upload. :P
[21:16] <Unit193> I hit that too, but not in Debian. >_>
[21:18] <infinity> http://paste.ubuntu.com/23083202/ definitely looks to be the culprit.
[21:20] <infinity> Might have been renamed to _read_changelog
[21:20] <infinity> Because reasons.
[21:20]  * infinity tests.
[21:21] <LocutusOfBorg> sigh pitti , seems cython autopkgtestsuite has the same issues
[21:21] <LocutusOfBorg> autopkgtest for python-pysam/0.7.7-1ubuntu1: amd64: Test in progress, i386: Test in progress, ppc64el: Regression ♻
[21:21] <LocutusOfBorg> maybe we can just ignore them?
[21:22] <infinity> juliank: Right, I blamed the wrong person, sorry. ;)
[21:26] <LocutusOfBorg> infinity, how did the fpc bootstrap go?
[21:27] <infinity> LocutusOfBorg: Not started yet.
[21:28] <LocutusOfBorg> oh... ok :) I sent a mail to Paul, in case he has something to share
[21:28] <LocutusOfBorg> I'll try now
[21:36] <infinity> Unit193: Fixes uploaded.
[21:36] <Unit193> infinity: Thanks very much, sir!
[21:36] <infinity> Unit193: We may be in the short list of people who use apt-listchanges. :P
[21:37] <Unit193> This is very true, I don't even have it prompt me after displaying, like you have.
[21:38] <infinity> Unit193: I rarely need to say no, but when I do, it's quite valuable.
[21:38] <infinity> Unit193: But such is the life of a core-dev in a devel series, I guess.  Sometimes, I see a changelog and go "wait, they did WHAT?!" and investigate (and maybe fix) before upgrading.
[21:39] <Unit193> infinity: Yeah I'm just a lowly flavor Dev, so can't fix things first.  Best I can do is hold it a bit. :P
=== salem_ is now known as _salem
=== bschaefer_ is now known as bschaefer
=== bschaefer_ is now known as bschaefer