[00:42] <psusi> xnox, doko, since you guys have touched it recently, I thought I would ask you... libboost seems to have a file, /usr/bin/quickbook... it moved from liboost-tools-dev to libboost-dev between liboost 1.53 and 1.54, which makes libboost1.54-dev have an undeclared conflicts with libboost1.53-tools-dev... why did this file move between binary packages?
[00:45] <nvrpunk> quick question, is tahr fairly usable?
[01:02] <xnox> psusi: due to multiarch.
[01:02] <xnox> psusi: in trusty, we have boost 54 (default) and 55 (available in universe) and they should be all fine.
[01:02] <xnox> psusi: ditto conflicts / replaces. Where are you spotting 1.53 / 1.54 conflict?
[01:02] <xnox> psusi: also boost-dev packages are not co-installable per se....
[01:04] <sarnold> if boost-dev packages aren't co-installable, why offer both 54 and 55?
[01:04] <psusi> xnox, yea...  I see they are set to conflict with each other but due to the change of package, 1.54 needs a Conflicts: libboost1.53-tools-dev... I saw someone asking about it on askubuntu, and there are a few upgrade failure bugs in launchpad
[01:04] <psusi> sarnold, in case you need the old one to build something.. it's there... you just have to remove the new one
[01:07] <jrwren> i've no idea why you would need an older version though. AFAIK boost is great at backward source compat
[01:24] <ScottK> It is better than it used to be.
[01:50] <nvrpunk> so my gnome-terminal's transparency is not working, what should I check?
[01:56] <semiosis> nvrpunk: use kde
[01:56]  * semiosis ducks
[01:56] <Unit193> Use #ubuntu ?
[01:57] <semiosis> nvrpunk: but seriously, as much as i love kde, this is probably teh wrong channel for that kind of question.
[01:57] <semiosis> as Unit193 points out :)
[01:57] <sarnold> it might be alright if it is busted in trusty...
[01:57] <semiosis> truth
[01:59] <Unit193> *Generally*, trusty would be in #ubuntu+1 though.
[01:59] <sarnold> heh never seen that one before..
[02:00] <nvrpunk> im using Ubuntu Gnome Trusty Tahr
[02:01] <nvrpunk> so how is this the wrong channel?
[02:01] <xnox> sarnold: why offer both -> because that's easier then black-listing from debian.
[02:01] <xnox> sarnold: and actualy libboost runtime library packages are co-installable.
[02:02] <sarnold> xnox: that's a good answer :) hehe
[02:02] <sarnold> I haven't looked enough at boost but I'm surprised there's much 'runtime library'
[02:04] <xnox> sarnold: a good chunk of boost are templates, but a whole-load of it are shared libraries that one links against.
[02:13] <TheMuso> @pilot in
[02:25] <TheMuso> Unit193: Where can I find a tarball for https://code.launchpad.net/~unit193/xfce4-panel/snapshot/+merge/206173?
[02:27] <Unit193> TheMuso: Right, sorry about that.  https://launchpad.net/~unit193/+archive/staging/+sourcepub/3912036/+listing-archive-extra
[02:27] <TheMuso> Unit193: Thanks, please put a pointer to the tarball if its a snapshot in the merge proposal in future.
[02:28] <Unit193> Sure, not used to bzr merges so wasn't really sure what to do there.
[02:28] <TheMuso> Understandable.
[02:28] <Unit193> (FWIW, xfce4-indicator-plugin is there too.)
[02:29] <TheMuso> Unit193: Yeah, I saw it, I'm doing them together.
[02:30] <Unit193> TheMuso: Just to be clear, that's preferred over dsc files?
[02:31] <TheMuso> Unit193: Yeah, thanks.
[02:57] <Devastator> can I ping a maintainer or is it considered disrespect?
[02:58] <Devastator> I would like to discuss an idea on IRC before going any further, so I thought discussing here would be better than e-mails etc as it is all informal for now
[03:17] <RAOF> Devastator: Pinging is generally fine.
[03:19] <Devastator> RAOF do you know which approach Stéphane Graber likes?
[03:20] <RAOF> If he's here I'm sure he'd be fine with a ping. stgraber?
[03:21] <Devastator> his idle says almost 4:30 hours, so probably not :)
[03:23] <Unit193> Devastator: Already been a couple pings, may as well ask now (in a highlight, and he may well see it.
[03:24] <Devastator> Unit193 alright, thanks, I'm assuming pasting links which may be from debian is ok also?!
[03:24] <sarnold> yes
[03:24] <Devastator> thanks!
[03:31] <Devastator> stgraber hi, I've seen that you are ubuntu's ifupdown maintainer and I want to add something that can be perhaps useful. Currently ifupdown exports IF_ environment variables to be used in if-pre-up.d, if-up.d, if-down.d and if-post-down.d, but it doesn't distinguish each parameter per interface, example: everytime one interface goes up it exports IF_ADDRESS, IF_NETMASK and others, what
[03:31] <Devastator> I'm proposing is adding interface logical name to it, like IF_eth0_ADDRESS, IF_eth1_ADDRESS, IF_eth0_NETMASK, IF_eth1_NETMASK and so on as this could be useful for using in shellscripts for advanced configurations. I must say I'm not currently using ubuntu but I'm willing to try it if you think this can be added
[03:32] <sarnold> Devastator: you were cut off at "others, what" in your first message
[03:33] <Devastator> thanks
[03:33] <Devastator> stgraber what I'm proposing is adding interface logical name to it, like IF_eth0_ADDRESS, IF_eth1_ADDRESS, IF_eth0_NETMASK, IF_eth1_NETMASK and so on as this could be useful for using in shellscripts for advanced configurations. I must say I'm not currently using ubuntu but I'm willing to try it if you think this can be added
[03:35] <Devastator> stgraber I give you a pastebin of what ifupdown exports currently: http://codepad.org/pksia5AW and here is the wishlist bug I posted in debian's BTS which contains the piece of code I tried to edit and failed miserably: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737749
[03:36] <psusi> Devastator, that would make it _less_ usable... if you want to know what iface you are being run for that is what the IFACE variable is for
[03:38] <Devastator> psusi yes, but how to check if IF_ADDRESS=1.2.3.4 is from IFACE=eth0 for example?
[03:38] <Unit193> TheMuso: Thanks muchly!
[03:41] <TheMuso> Unit193: You're welcome, please keep in mind the pointers I made both on IRC, and in the comments for the indicator plugin.
[03:41] <Unit193> Indeed.
[03:42] <Devastator> also, if you guys don't mind me asking, are there plans to replace ifupdown altogether?
[03:48] <Devastator> psusi also, could you please explain why you think it would make less usable?
[03:59] <psusi> Devastator, with an if statement of course
[03:59] <psusi> Devastator, it would make it less usable because you couldn't write a script without knowing the name of the iface
[04:00] <Devastator> psusi I'm not trying to replace IFACE with IF_<iface name>_ADDRESS etc, I want to keep IFACE
[04:01] <Devastator> psusi did you take a look at the pastebin also?
[04:01] <Devastator> psusi also, I'm not saying you are wrong, just trying to understand
[04:03] <Devastator> if you possible, give me an example of the if
[04:07] <psusi> Devastator, if [ $IFACE = eth0]
[04:09] <Devastator> psusi does it matter if $IFACE is exported after $IF_ADDRESS?
[04:09] <psusi> no
[04:10] <Devastator> will do some tests
[04:15] <psusi> Devastator, generally speaking, the script shouldn't *care* what interface it is being used with
[04:17] <Devastator> psusi I'm trying to come up with a multiwan failover solution without having to hardcode things, the if works, now I have to make some kind of array to store $IFACE from each interface, then get each $IF_ADDRESS, but I think it will work
[04:20] <psusi> Devastator, I think you're going about it all the wrong way.. I'm pretty sure those scripts aren't called when an interface fails... only when you manually ifdown
[04:24] <Devastator> psusi I don't think I follow you, are you saying it's not a good idea to use if-up.d scripts?
[04:40] <Devastator> psusi I really have to get some rest, can we continue this talk at perhaps.. 11:00 UTC?! my TZ is UTC-2 by the way
[04:46] <psusi> Devastator, yes, that is not a use case for if-up.d scripts
[06:04] <TheMuso> @pilot out
[06:43] <pitti> Good morning
[06:45] <pitti> mlankhorst: they auto-ran; yay, they all succeed now! https://jenkins.qa.ubuntu.com/view/Upgrade/?
[06:45] <pitti> mlankhorst: that is, ubuntu-precise-trusty-*-lts-*
[07:14] <dholbach> good morning
[07:16] <YokoZar> pitti: Not to poo-poo you for fixing wine1.4, but I'd rather you just delete it
[07:16] <pitti> YokoZar: ah, I wanted to ask you yesterday, but you weren't online
[07:16] <YokoZar> https://bugs.launchpad.net/ubuntu/+source/wine1.4/+bug/1218645
[07:17] <pitti> YokoZar: I actually already uploaded it yesterday, but the upload somehow wasn't accepted
[07:17] <pitti> YokoZar: right, Debian has 1.6, I wondered whether we want to upgrade
[07:17] <YokoZar> We have 1.6 too
[07:17] <YokoZar> now
[07:17] <YokoZar> I wanted to upgrade 2 releases ago
[07:17] <pitti> YokoZar: I just got the FTBFS when I did the libgphoto transition, and then felt obliged to spend the two hours to fixing the build and finishing the transition
[07:18] <YokoZar> It never got into saucy due to being uploaded like 2 minutes after feature freeze
[07:18] <pitti> hm, I cant' see wine 1.6 in trusty
[07:18] <YokoZar> wait, what
[07:19] <pitti> not in https://launchpad.net/ubuntu/trusty/+queue?queue_state=0 either
[07:19] <pitti> wine1.6 | 1:1.6.1-0ubuntu4 | trusty-proposed/universe | source, amd64, i386
[07:19] <pitti> ooh
[07:19] <pitti> they just didn't propagate yet
[07:19] <pitti> wine1.6/amd64 unsatisfiable Depends: wine1.6-i386 (= 1:1.6.1-0ubuntu4)
[07:20] <pitti> yeah, that looks wrong
[07:20] <YokoZar> oh right
[07:21] <pitti> I thought in the times of multi-arch we wouldn't need those -i386/-amd64 packages at all any more
[07:21] <YokoZar> didn't we have to do something manual for wine1.4
[07:21] <pitti> you can just apt-get install wine and would get wine:i386
[07:21] <YokoZar> The issue is that wine on amd64 needs BOTH the i386 and amd64 guys
[07:21] <YokoZar> and there's no way to do arch-specific depends
[07:22] <YokoZar> so instead you have to make a package that's only satisfiable as a foreign depends
[07:22] <pitti> ah, so wine: is arch: all, depends: wine-bin
[07:22] <pitti> and wine-bin is M-A: foreign?
[07:22] <YokoZar> Yeah
[07:25] <YokoZar> To be more specific, wine is a metapackage depending on wine1.6, which in turn depends on wine1.6-i386 or (both wine1.6-i386 and wine1.6-amd64)
[07:26] <YokoZar> and wine1.6 isn't arch-all but is defined for specific arches (cause the dependencies change based on the arch)
[07:28] <YokoZar> I seem to remember there being some sort of "ignore wine's unsatisfiable cross-arch depends" thing in the proposed migration for wine1.4.  Or maybe it was just manually approved each time.
[07:28] <pitti> YokoZar: ah, indeed skype is similar; skype is amd64, depending on skype-bin which is i386 only and M-A: foreign
[07:29] <pitti> IIRC slangasek set that up, so I take that as "official reference to do it right" :)
[07:29] <YokoZar> Yup.  I'm somewhat proud of it being so coherent (and Wine using just about every edge case of apt there is)
[07:31] <pitti> YokoZar: oh, and now the wine1.4 builds got rejected because they are older than the transitional ones in -proposed
[07:32] <pitti> so I guess that was in vain
[07:32] <YokoZar> hah, so I suppose you would have discovered wine1.6 that way :p
[07:33] <pitti> so, TBH I don't know why britney complains about it
[07:33] <pitti> infinity: do you have an idea about "wine1.6/amd64 unsatisfiable Depends: wine1.6-i386 (= 1:1.6.1-0ubuntu4)" in britney?
[07:34] <pitti> wine1.6-i386 is already M-A: foreign
[07:34] <infinity> pitti: Yeah, we need a fauxpkg setup for it.  britney doesn't do cross-arch deps.
[07:34] <infinity> pitti: I'll sort it in the morning when I'm more awake.  Or ask cjwatson, he knows what's up.
[07:34]  * pitti tries to make an halfway intelligent face about "fauxpkg"
[07:35] <infinity> pitti: See fauxpkg/FauxPackages in britney1 source.
[07:36] <infinity> YokoZar: Bug me about it in the morning if no one's fixed it before.  I'm sleeping in about 3 minutes.
[07:37] <pitti> infinity: I just got a bug report against langpack-locales; do we actually build locales from eglibc now? eglibc has it in it's Binary: list, but our locales still comes from langpack-locales
[07:37] <pitti> infinity: (feel free to answer after you wake up again, not urgent at all)
[07:40] <YokoZar> pitti: infinity: thank you both
[08:07] <OdyX> tkamppeter_: yay, thanks.
[09:35] <mlankhorst> pitti: not yet, xrandr needs a tes ttoo
[09:35] <mlankhorst> test that ls /usr/bin/xrandr* == /usr/bin/xrandr
[09:37] <mlankhorst> I forgot about that diversion
[09:39] <pitti> mlankhorst: would you mind describing that in https://bugs.launchpad.net/auto-upgrade-testing/+filebug ?
[09:39] <pitti> (hunting down two other failures ATM, brain stack is full)
[10:09] <mlankhorst> pitti: upload https://mblankhorst.nl/etc/xorg-lts-transitional_5.tar.gz and then https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/1280155 should be fixed for the packages in ubuntu
[10:11] <pitti> mlankhorst: uploaded, thanks!
[10:19] <zyga> hey, daily update left my system with this:
[10:19] <zyga> apt-get: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory
[10:20] <zyga> I didn't reboot but I cannot launch most things
[10:20] <zyga> doko: ^^
[10:20] <zyga> help please :-)
[10:21] <zyga> ara: what a day ;)
[10:21] <ara> zyga, what happened?
[10:22] <pitti> urhg, indeed
[10:22] <doko> zyga, I see
[10:22] <zyga> ara: libgcc_s.so.1: cannot open shared object file
[10:22] <pitti> this just caused a gazillion autopkgtset failures, too
[10:22] <zyga> ara: don't upgrade for a moment
[10:22] <doko> arghh, and it did migrate already ...
[10:22] <pitti> jibel: hm, given that this broke pretty much every autopkgtest, any idea why this wasn't held back?
[10:22] <zyga> ara: (earlier I had lots of kernel fc*ups, wired networking didn't work and other funny things)
[10:22] <seb128> an we delete the binaries before they get downloaded?
[10:23] <seb128> can*
[10:23] <pitti> oh, I guess they only started failing after the promotion of whatever caused that
[10:23] <doko> zyga, quick fix: install the old libgcc1
[10:23] <doko> if you have it in the cache
[10:24] <seb128> doko, can you get #is to block the download of the buggy binaries?
[10:24] <zyga> I only have libgcc1_1%3a4.9-20140213-0ubuntu1_amd64.deb
[10:24] <pitti> hmm, gcc-4.8 was uploaded two days ago already
[10:24] <doko> trying ...
[10:24]  * zyga checks if apt-cacher-ng has it
[10:25] <pitti> zyga: you can get older ones from https://launchpad.net/ubuntu/+source/gcc-4.8/<version>
[10:25] <Laney> why did that only just happen?
[10:25] <pitti> is that really libgcc1?
[10:26] <pitti> it must have been something which just propagated an hour or so ago
[10:26] <zyga> pitti: I may have it in apt-cacher-ng
[10:26] <Laney> yeah
[10:26] <doko> pitti: now built from gccgo-4.9
[10:26] <pitti> ah
[10:26] <doko> but empty package. messed up the testing
[10:26] <pitti> and gccgo-4.9 doesn't trigger any autopkgtests, so it wasn't caught by those until after it promoted
[10:27] <pitti> ok, that at least explains the mysteries
[10:27] <pitti> doko: i. e. is it meant to build from gccgo-4.9, or was that an oversight? In the latter case, we'd need a version downgrade, i. e. update gcc-4.8 to 4.9+really4.8.. or so?
[10:28] <doko> pitti, it is meant to
[10:28] <pitti> doko: ok, that at least simplifies the versioning problem
[10:28] <doko> but the quick fix is to download the previous version and just dpkg -i it
[10:29] <pitti> wget http://archive.ubuntu.com/ubuntu/pool/main/g/gcc-4.8/libgcc1_4.8.2-15ubuntu3_amd64.deb
[10:29] <pitti> sudo dpkg -i libgcc1_4.8.2-15ubuntu3_amd64.deb
[10:29] <pitti> zyga:  ^
[10:29] <zyga> ok, thank god I had apt-cacher-ng with the older copy :)
[10:29] <zyga> already fixed, I also installed the i386 version for parity
[10:30] <Laney> hmmmmmmm
[10:30] <pitti> the teutonic mirror is behind by half a day or so, seems that rescued me
[10:30] <Laney> I ended up with /var/lib/spamassassin being root:root rather than debian-spamd:debian-spamd
[10:30] <cjwatson> And of course this means all trusty builds are failing too
[10:30] <Laney> which broke my upgrade due to the new sa-compile thingy
[10:31] <Laney> does anybody else have it with these permissions?
[10:31] <cjwatson> /usr/bin/apt-cache exit status 32512
[10:32] <pitti> i. e. including the upcoming gccgo4.9 fix, yay
[10:32] <cjwatson> We can probably work around that with the bootstrap archive somehow
[10:32] <pitti> cjwatson: could we temporarily disable the dist-upgrade of the build chroots for that?
[10:33] <pitti> I take it the chroots are usually a few days or even weeks old
[10:33] <seb128> can we get the binaries blocked from download on the server?
[10:33] <seb128> save users and the chroots :p
[10:33] <seb128> oh, cjwatson just pinged #is a bit more, thanks
[10:34] <cjwatson> pitti: it's easier to prod it in the bootstrap archive; fiddling with the build chroots will require infinity to wake up
[10:34] <pitti> ack
[10:35] <tvoss> doko, around?
[10:35] <pitti> tvoss: not now, please : )
[10:35] <pitti> tvoss: trusty is on fire, nobody disturb doko for a while
[10:35] <tvoss> pitti, ack
[10:35] <zyga> was I the first person affected that came here/
[10:36] <cjwatson> I don't understand why autopkgtest didn't save us from this
[10:36] <cjwatson> I: [Fri Feb 14 09:42:55 2014] - Requested autopkgtest for apt_0.9.15.2ubuntu1 (NEW gccgo-4.9 1:4.9-20140213-0ubuntu1)
[10:36] <cjwatson> [lots of more things along the same lines]
[10:36] <cjwatson> final: gccgo-4.9,ubuntu-keyboard
[10:36] <pitti> cjwatson: yeah, we got a bazillion failures
[10:36] <zyga> cjwatson: this is like backup, the first time we know the backup failed, the second time we check if backups can also restore
[10:36] <cjwatson> zyga: please can I not have the smart commentary just now? :)
[10:36] <zyga> cjwatson: sorry
[10:36]  * zyga goes away
[10:37] <pitti> cjwatson: gccgo4.9 doesn't have direct rdepends that have autopkgtests apparently, but it should have caught the libgcc1 binary for sure
[10:37] <cjwatson> jibel: could you have a look at why adt-britney apparently said everything was just fine when we'd just triggered a load of autopkgtests for gccgo-4.9 and they hadn't come back yet?
[10:37] <cjwatson> pitti: the above log entry shows that it definitely felt it necessary to trigger them
[10:37] <pitti> cjwatson: ok
[10:38] <pitti> yeah, I noticed that several times, britney waving through uploads before tests finished
[10:38] <jibel> cjwatson, looking
[10:41] <cjwatson> I'm going to disable the publisher while I figure this out; don't tell anyone but I think I might be able to manage to wind this back as an emergency measure
[10:46] <cjwatson> 10:45 <cjwatson> doko: so, I'm going to remove gccgo-4.9 from trusty, copy gcc-4.8 back over it (which should be permitted, and should restore libgcc1), rerun the publisher, then hopefully we can build the new gccgo-4.9
[10:46] <cjwatson> oops, echan, but never mind
[10:51] <cjwatson> Downloads should be disabled where possible
[12:22] <cjwatson> pitti: I think you can retry those autopkgtest failures now
[12:30] <pitti> cjwatson: thanks; our internal mirror (tachash) still gives the bad deb, I asked in #ci a while ago about purging it
[12:30] <cjwatson> it should be sufficient to just sync it now
[12:30] <cjwatson> current indices have libgcc 4.8.mumble instead
[12:30] <pitti> I'll just try
[12:33] <pitti> yay, works now
[12:33]  * pitti gives our machines something to chew on then
[12:34] <pitti> doko, cjwatson: many thanks for your swift handling of this!
[12:34] <cjwatson> I'm going to do an automated search for affected failed builds
[12:34] <cjwatson> (once I write it)
[12:38] <jibel> pitti, autopkgtest in the lab use ftpmaster and should have the right deb
[12:40] <cjwatson> OK, walking through all recent builder history now searching for "/usr/bin/apt-cache exit status", will take a while
[12:41] <cjwatson> of course chances of getting answers quickly out of wildcherry right now ...
[12:41] <cjwatson> wgrant: I guess the POST rule applies with the API too?  so my first retry() -> everything after on wildcherry
[12:41] <wgrant> cjwatson: All API requests go straight to the master
[12:42] <cjwatson> ah ok
[12:42] <wgrant> But the API is mostly performing OK at the moment.
[12:43] <zbenjamin> cjwatson: i was reading in the ML and the link you gave me. But where can i find details on where i put the different binaries for the different archs? like the armhf binaries, the x86 binaries and so on
[12:47] <cjwatson> zbenjamin: that's not up to click
[12:48] <cjwatson> zbenjamin: it's for the SDK and tools such as upstart-app-launch to define how packages are laid out internally
[12:48] <cjwatson> zbenjamin: tedg might be able to advise on current standards
[12:48] <zbenjamin> cjwatson: thx i'll ask him
[12:50] <jibel> cjwatson, what I found so far, gccgo triggered an autopkgtest for 54 packages, status has been set to running for these packages and collected by britney but gccgo has not been removed from upgrade_me, it passed the upgrade test and has been copied. What is unclear yet is why gccgo has not been removed while tests of dependant packages were running.
[12:58] <cjwatson> jibel: hopefully that much will clear out soonish, a fixed gccgo-4.9 is building
[12:58] <cjwatson> oh, but you mean for why it didn't block initially
[12:59] <jibel> cjwatson, yes, for why it didn't block initially, I'm in britney.py
[13:03] <pitti> jibel: beer o'clock!
[13:03] <pitti> http://d-jenkins.ubuntu-ci:8080/view/Upgrade/
[13:03] <pitti> ugh, at least the wrestling this week was useful :)
[13:05] <jibel> pitti, 38 profiles, all green \o/ time to add more tests
[13:05] <seb128> pitti, hum, are you sure you want to hand beer to jibel while he's working on britney.py? ;-)
[13:06] <pitti> seb128: I'll buy him one next week
[13:06] <pitti> I pestered him all week with questions about how stuff works
[13:06] <seb128> oh, you guys have a team gathering coming
[13:06] <seb128> enjoy it!
[13:06] <pitti> yeah, Oakland, will fly out tomorrow
[13:06] <pitti> seb128: merci !
[13:07] <pitti> jibel: more tests> for sure, but nice to have a stable base line now
[13:09] <Laney> more Oakland, lucky pitti ;-)
[13:16] <cjwatson> jibel: hopefully you're about to get it again; accepted the fixed gccgo-4.9
[13:17] <cjwatson> though armhf is still building so maybe it'll block anyway
[13:37] <cjwatson> All libgcc-affected failed builds retried, I believe
[14:25] <spineau> doko: hello, to build checkbox-gui for ubuntu we're a bit blocked by two dependencies waiting to be promoted to the main archive: bug 1277408 and bug 1278822, could you please help us?
[14:26] <doko> spineau, not yet seen in http://people.canonical.com/~ubuntu-archive/component-mismatches.svg
[14:27] <spineau> doko: I think it's because we're still in -proposed
[14:27] <spineau> roadmr: ^
[14:27] <doko> http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
[14:30] <roadmr> spineau, doko: I see, I fixed the stuff that was keeping checkbox in proposed (dep-wait) so it should make it out, will it appear in component-mismatches once this happens?
[14:30] <doko> roadmr, yes, it should
[14:31] <roadmr> spineau, doko: OK then, upload coming up in a second
[14:31] <spineau> roadmr: doko: perfect, thanks
[15:03] <shadeslayer> ev: ping
[15:34] <shadeslayer> pitti: can Kubuntu also utilize https://jenkins.qa.ubuntu.com/view/Upgrade/ ?
[15:39] <pitti> shadeslayer: yes, I don't see why not
[15:41] <shadeslayer> yay :)
[15:41] <shadeslayer> pitti: I'll have a look at how to write a test case and send MR's
[15:42] <pitti> shadeslayer: it's primarily about defining a new scenario
[15:43] <pitti> shadeslayer: i. e. something like s/ubuntu-desktop/kubuntu-desktop/ and enabling universe
[15:43] <shadeslayer> I see
[15:43] <jpds> stgraber: Have you seen this? https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1280050
[15:43] <pitti> shadeslayer: the scenarios in lp:auto-upgrade-testing are outdated, we are actually using a branch from jibel, hang on
[15:43] <shadeslayer> pitti: I think there are 2 upgrade paths we want to check : regular 13.10 to 14.04 and 13.10 + LTS Stack + Kubuntu backports to 14.04
[15:45] <stgraber> jpds: nope, I haven't. Though to be faire, I'm not maintaining samba, I only patched the few bits I needed to get my use case covered (AD domain controller) :)
[15:45] <jpds> Ah, right.
[15:45] <stgraber> jpds: I believe the server team are the ones actually maintaining our delta, anything else should probably go straight to Debian
[15:46] <rbasak> infinity: do you think it appropriate/could you sync cyrus-sasl2, please? Looks like a host of bugs have been fixed recently there. It's not in testing yet though.
[15:46] <rbasak> (and it's a new upstream release, too, which looks minor, but the changelog suggests that it isn't)
[15:47] <jibel> shadeslayer, I think I've already a profile for Kubuntu 13.10->14.04.
[15:47] <jibel> shadeslayer, What is 13.10 + LTS stack?
[15:47] <pitti> shadeslayer: this one: https://code.launchpad.net/~jibel/+junk/auto-upgrade-testing_profiles
[15:48] <pitti> shadeslayer: I think the 12.04+LTS stack scenarios are already well-handled; is there anything Kubuntu specific in them?
[15:48] <shadeslayer> jibel: whoops, I meant 12.04 + HWE
[15:48] <pitti> oh yes, http://bazaar.launchpad.net/~jibel/+junk/auto-upgrade-testing_profiles/files/head:/kubuntu/
[15:48] <Devastatr> stgraber good afternoon (or probably evening), did you happen to see the message I leave here?
[15:48] <shadeslayer> pitti: well, we backport KDE releases to our PPA, and alot of users add that ppa
[15:48] <shadeslayer> so I think it's useful to have that tested
[15:51] <pitti> ah, yes
[15:52] <jibel> shadeslayer, ah okay as pitti said LTS+HWE is already covered, we could do 12.04 + Kubuntu backport
[15:52] <shadeslayer> sure, fine with me
[15:53] <zbenjamin> tedg: ping
[15:54] <tedg> zbenjamin, Howdy
[15:54] <zbenjamin> hey
[15:54] <zbenjamin> tedg: i got pointed to you by jdstrand i think, because i was asking about how a fat click package should look like internally and how it will work with the desktop files EXEC property
[15:55] <zbenjamin> i'm working on the qtcreator ubuntu plugin and we would like to integrate fat packaging :)
[15:55] <tedg> zbenjamin, Yup, so what we're doing is adding an arch dependent directory to the path.  So that way you can put an executable name in the Exec line and it'll find the arch dependent one.
[15:56] <zbenjamin> tedg: ok but do i need a own desktop file per architecture in the package then?
[15:57] <tedg> zbenjamin, Nope, so the desktop file can have "Exec=foo-bar" and the package would have a $(dir)/lib/$(arch)/bin/foo-bar for each arch.
[15:57] <stgraber> Devastatr: I did. I'm not necessarily against extending the script environment though I'm not going to diverge from Debian either, so if Andrew (the Debian maintainer) does those changes, I'll include them in Ubuntu but I don't want Ubuntu to suddenly become incompatible with Debian for those scripts.
[15:57] <zbenjamin> tedg: ok and the path will be set correctly so it will be found
[15:58] <tedg> zbenjamin, Yup, for some examples there are the exec-test* file in the tests directory here: http://bazaar.launchpad.net/~indicator-applet-developers/upstart-app-launch/trunk.14.04/files/head:/tests/
[15:59] <zbenjamin> tedg: and for things like : Exec=qmlscene $@ -I ./lib/arm-linux-gnueabihf/qt5/qml   share/qml/cmake1/cmake1.qml
[16:00] <Devastatr> stgraber I understand that and I agree, when you have some time, can you ping me? I want to discuss if I wanted to design something to replace ifupdown, together with you and Andrew, where to start
[16:00] <tedg> zbenjamin, We're also setting the QML2_IMPORT_PATH to be $(dir)/lib/$(arch)
[16:02] <zbenjamin> tedg: do you have any docs on which directories have to be where?
[16:02] <tedg> zbenjamin, Uhm, not really.  Not really sure where that belongs.
[16:03] <zbenjamin> tedg: ok so lets recap, i put a arch into the manifest , lets say armhf, then click wants to have executables in APP_DIR/bin/armhf  and libs in APP_DIR/lib/armhf
[16:04] <zbenjamin> or is it arm-linux-gnueabihf
[16:04] <tedg> zbenjamin, It's the triplet, and not /bin, but /lib/$arch/bin
[16:05] <zbenjamin> tedg: or maybe you could point me to the code that sets up the env
[16:08] <tedg> zbenjamin, Sure, I'm not sure that's as helpful as the tests are though.  http://bazaar.launchpad.net/~indicator-applet-developers/upstart-app-launch/trunk.14.04/view/head:/exec-line-exec.c#L62
[16:10] <zbenjamin> tedg: thanks , if i have more questions i'll come back to you :)
[16:14] <tedg> zbenjamin, No problem, good to see this getting into the plugin!
[16:16] <zbenjamin> tedg: yeah, we have a _lot_ of things to get in there ;)
[16:18] <tedg> zbenjamin, BTW, are you guys also adding support for custom URLs (or is that on the TODO list)?
[16:18] <zbenjamin> custom urls? that i don't know about, bzoltan is my mentor so he should know more
[16:22] <hallyn> bdmurray: hi, so regarding bug 1228977.  I was waiting for sdague to post a test case so I could do the SRU justification
[16:23] <hallyn> bdmurray: however, the candidate package I pushed is broader, taking the whole upstream "-stable" series for that libvirt version.  I wasn't sure if that should be handled specially
[16:24] <hallyn> (it took some time to reconsile the upstream patchset with the individually-applied CVE patches in our tree)
[16:24] <hallyn> normally, I would say that if the bug submitter can't be bothered to give a test reproduction s cript, let's just drop the patch and close the bug, but
[16:25] <hallyn> since this is a whole -stable patchset I'd prefer to test for new regressions and call it good
[16:32] <bdmurray> hallyn: I hadn't actually looked at the diff yesterday, just the bug.
[16:38] <hallyn> bdmurray: if my reasoning about the -stable patchset is legitimate i can put that in teh bug comment.  otherwise, i'll ping the bug submitter oen more time for a test case, and we can drop teh set and close the bug next week if we dont' get it
[16:39] <bdmurray> using the -stable patchset seems more like a micro release to me than a standard SRU
[16:46] <hallyn> bdmurray: if saucy was going to be around longer i'd pursue that.  unfortunately there is an upstream libvirt -stable tree for saucy, but not (other than the one i maintain :) for precise
[17:03] <ev> shadeslayer: pong
[17:04] <shadeslayer> ev: Kubuntu has started reporting crashes to errors.ubuntu.com but our backtraces usually end in KCrash ( the KDE Crash handling framework ) , would daisy interpret the crashes as crashes in KCrash or will it be able to parse the stack correctly? ( see ref : https://trello.com/c/u9KpFFxF )
[17:08] <ev> shadeslayer: what do you mean by "our backtraces usually end in KCrash"?
[17:09] <ev> oh
[17:09] <shadeslayer> ev: KDE Software :)
[17:09] <ev> shadeslayer: that's pretty easy to test. Just kill -SEGV a KDE process and see what's in the executablepath and package fields
[17:09] <ev> in the resulting crash report
[17:10] <shadeslayer> ev: but my question is whether daisy will interpret all crashes as crashes in KCrash?
[17:10] <ev> shadeslayer: right, and I'm saying the way to find out is by looking at the resulting crash report after killing a process with sigsegv
[17:12] <shadeslayer> ev: and what am I looking for?
[17:12] <ev> shadeslayer: the Package field and the ExecutablePath field
[17:14] <shadeslayer> ev: grep doesn't say anything
[17:14] <shadeslayer> Bunch of jumbled text
[17:14] <ev> shadeslayer: can you pastebin the resulting .crash file?
[17:14] <shadeslayer> sure
[17:15] <shadeslayer> ev: http://paste.ubuntu.com/6932266/
[17:16] <shadeslayer> ev: really really large file :P
[17:17] <ev> shadeslayer: looks right to me: ExecutablePath: /usr/bin/kate
[17:17] <Laney> shadeslayer: you do have Package and ExecutablePath in there
[17:17] <ev> you wont get Package until you actually run apport-kde over it
[17:17] <ev> err so you do :)
[17:17] <shadeslayer> ev: Laney yeah it's weird, grep didn't return anything
[17:19]  * Laney suspects PEBCAK :P
[17:19] <shadeslayer> http://paste.ubuntu.com/6932302/
[17:20] <shadeslayer> ev: anyway, so it'll be fine even though backtrace has KCrash in it?
[17:22] <ev> shadeslayer: ja
[17:22] <shadeslayer> cool :)
[19:58] <u-foka> Hy, I've tryed to install trusty using the latest daily-live image dd-d over an usb key but it refuses to boot :(
[20:10] <u-foka> is anyone here?
[20:11] <sarnold> a few hundred :) normally IRC works best if you've got something concrete.. an error message or something similar
[20:12] <u-foka> sorry I have only the fact that my bios immediatelly returns to the device selection mennu when I select the pendriver and hit enter :/
[20:12] <u-foka> I've tried to dd the iso on the dirst (active) partition and also on the entire device without success
[20:13] <u-foka> also I can't found the unity alpha2 iso image, there are the images for every other flavor but not for ubuntu-desktop
[20:14] <dobey> main ubuntu doesn't do actual alpha releases any more
[20:14] <dobey> the daily image should be what you use
[20:15] <u-foka> so I should try it with an older daily image?
[20:15] <dobey> maybe, i don't know
[20:15] <dobey> "refuses to boot" doesn't really say anything about what's wrong
[20:15] <dobey> you do have to dd to the main device, not a partition
[20:16] <dobey> "dd if=foo.iso of=/dev/sdg bs=4096" for example
[20:16] <u-foka> tried that way also, but got only a blank screen
[20:16] <u-foka> my bios has uefi support and it can't be disabled
[20:17] <dobey> i can't really help beyond that info though. sorry
[20:17] <u-foka> okay, thanks anyway
[20:18] <dobey> fwiw though, #ubuntu is the help channel, so you might have better luck asking in there
[20:18] <u-foka> I'll try with the 11th image maybe it will work
[20:19] <dobey> kenvandine, mardy: are there docs about what mechanisms/options can be used with the generic_oauth plug-in, when creating a provider file?
[20:19] <u-foka> well I thought this is the right channel for asking about an alpha release :) then I'l try asking there also if it won't boot with the other image
[20:24] <kenvandine> dobey, not that i've seen
[20:24] <geoff-> Hi, where can I find a kernel that will work with this: cdimage.ubuntu.com/ubuntu-core/daily/current/trusty-core-arm64.tar.gz?
[20:24] <dobey> kenvandine: do you know if PLAINTEXT is a valid mechanism?
[20:25] <geoff-> I looked around in ports.ubuntu.com, but could'nt find anything for arm64
[20:29] <dobey> ah, i guess it is
[20:32] <kenvandine> dobey, sorry, don't know
[20:34] <dobey> ok
[20:37] <Noskcaj> Is there anything i can do to speed up bug 1272123
[20:42] <u-foka> well, definitely something's wrong with the uefi boot ot the daily images.. it boots into a black screen when selecting the pendrive from the boot menu, but it boots properly when selecting the pendrive as the first boot device from the bios setup
[20:43] <u-foka> anyway it's installing now
[20:48] <dobey>  kenvandine do you know if there is some way to debug the HTTPS requests there?
[20:48] <dobey> u-foka: that sounds very much like it could be a problem with the BIOS itself
[20:49] <u-foka> yeah it was my first impression also but somehow the 13.10 insaller boots without any problems in uefi mode
[20:57] <kenvandine> dobey, i don't, but maybe cwayne might
[20:57] <kenvandine> he's done quite a bit of hacking on that stuff lately
[20:58] <dobey> oh
[20:58] <dobey> and not in here, whee
[21:24] <Unit193> mvo_: Well howdy.  Just a small poke again. :)
[22:22] <chiluk> what tool outputs this kind of information ip-21638 [020] .... 37415.094434: lg_local_unlock <-mntput_no_expire
[22:22] <chiluk> ip-21638 [020] .... 37415.094436: lg_global_lock <-do_umount
[22:22] <chiluk> ip-21638 [020] .N.. 37431.042253: lg_global_unlock <-do_umount
[22:22] <chiluk> ip-21638 [020] .N.. 37431.042265: lg_global_lock <-release_mounts
[22:30] <roadmr> chiluk: seems to come straight from the kernel: http://lxr.free-electrons.com/ident?i=lg_global_lock
[22:31] <chiluk> roadmr some tool is tracing the kernel..
[22:31] <roadmr> ohh weird then
[22:31] <chiluk> roadmr, I'm curious what the tool is that is producing the output.
[22:31] <chiluk> maybe I'll move to ubuntu-kernel
[22:31] <stgraber> chiluk: looks fairly close to ftrace
[22:32] <TJ-> chiluk: local-global spinlocks
[22:38] <chiluk> thanks stgraber
[23:19] <Logan_> Noskcaj: hi
[23:20] <Logan_> ok