[05:30] <Mr_Pan> nhaines, hi
[05:31] <Mr_Pan> I just voted for the council
[20:21] <nhaines> @Mr_Pan Thanks for submitting your vote!  I'm excited we're having another election on time.  :)
[20:22] <nicoz> ;)


[02:14] <bluesabre> Unit193: thanks. Could be something to consider if we wanted to link to package installs from the docs or something
[02:17] <bluesabre> Unit193: so, I'm working on making xubuntu-artwork work with elementary-xfce... I have http://paste.ubuntu.com/p/ms9FC2DSFs/ and https://code.launchpad.net/~xubuntu-art/xubuntu-artwork/+git/xubuntu-artwork/+ref/elementary-xfce-transition ... but still running into some issues when installing (https://paste.ubuntu.com/p/r6YnGcDyWk/). Do you have any idea what I might be missing at this point?
[02:18] <bluesabre> been poking at it for a while now, so it might be just something dumb that I'm missing from looking at the same thing for a while
[02:35] <Unit193> bluesabre: What happens if you leave the xubuntu-artwork depends as they are?
[02:36] <Unit193> Ah.  You depend on elementary-xfce-icon-theme (>= 0.12-2), so it wants to install that, but then elementary-xfce-icon-theme breaks/replaces xubuntu-icon-theme so it wants that to be updated.
[02:36] <Unit193> If I am reading this right.
[02:50] <Unit193> bluesabre: Perhaps you just want to 1ubuntu1 elementary?  Also please poke ochosi before uploading, last I remember he didn't like my new creation! :(  (Nah, just wanted pngs over svgs.)
[02:50] <Unit193> I, of course, would think it'd be great if we used this, but either way I think it's good to be in Debian (so I can use it there. >_>)
[03:43] <bluesabre> Unit193: yeah, trying to figure out how to safely transition the package... remove the contents of xubuntu-icon-theme, install elementary-xfce-icon-theme, then patch the theme with update-alternatives
[03:44] <bluesabre> Not opposed to ubuntu-fying it
[03:44] <bluesabre> and then reducing the delta afterwards
[03:44] <bluesabre> but the transition seems weird
[03:44] <Unit193> That is, s/conflicts/breaks+replaces/ part.
[03:47] <bluesabre> oh right
[03:48] <Unit193> Did you read the rest of it?  Drop the versioned dep in x-i-t and re-try?
[03:48] <Unit193> I kind of recently did this very thing, actually.
[03:49] <bluesabre> Alrighty, will try that
[03:49] <Unit193> Package a:
[03:49] <Unit193> +Breaks: elementary-shimmer-icon-theme (<< 0.13)
[03:49] <Unit193> +Replaces: elementary-shimmer-icon-theme (<< 0.13)
[03:49] <Unit193> Package B: Depends: ${misc:Depends}, elementary-xfce-icon-theme
[03:51] <Unit193> (Package C retained the elementary-shimmer-icon-theme dep/rec for the time being.)
[03:55] <bluesabre> https://paste.ubuntu.com/p/3VQHgMJHkf/
[04:14]  * Unit193 tries
[04:15]  * bluesabre sleeps
[04:15] <bluesabre> long dayyyyyy
[04:15] <bluesabre> nighty Unit193
[04:17] <Unit193> bluesabre: http://paste.openstack.org/show/726793/ ?
[04:18] <bluesabre> huh
[04:18] <bluesabre> suppose I'll try that in a vm then
[04:19] <bluesabre> dev env is always a mess
[04:20] <Unit193> http://paste.openstack.org/show/beT0sNzQtAc4e9CkT6P5
[04:20] <Unit193> http://paste.openstack.org/show/c6eUYvI2HXLDl72bwwTY
[13:09] -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: xfwm4 4.12.5 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-xfwm4-4-12-5-released-tp51453.html (by Olivier Fourdan)
[13:24] -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: xfwm4 4.13.1 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-xfwm4-4-13-1-released-tp51456.html (by Olivier Fourdan)
[16:55] <Unit193> Wow.
[17:22] <knome> (:
[19:31] <knome> so i stitched together an admin menu for all release-related stuff...
[19:31] <knome> visible in staging if you are interested
[19:31] <knome> showing the right parent menu isn't working yet, but that's coming too
[19:32] <knome> just reusing the somewhat crappy admin pages (or just not the most appropriate really) for now
[19:32] <knome> they work though, without any code...
[19:45] <knome> ...and correct menu is now highlighted, woohoo
[19:46] <knome> ..in most cases at least
[19:48] <knome> and should now be in all cases


[00:19] <elopio> ok, this won't work for 24 hours on jenkins :(
[00:19] <elopio> tomorrow, I think it will pass.
[00:54] <daker> balloons: https://twitter.com/UbuntuTesting/status/487760664325156864
[00:56] <balloons> daker, thanks.. weird
[01:21] <balloons> elopio, I'll take your word for it
[13:27] <gerlowskija> elopio: ping
[14:07] <nik90_> mzanetti: ping
[14:12] <mzanetti> nik90_: hey
[14:13] <nik90_> mzanetti: hey would it be possible to have a hangout for about 20-30 minutes to pick your brain on a qml c++ plugin?
[14:13] <nik90_> mzanetti: doesn't have to be today
[14:13] <nik90_> mzanetti: anytime you are free would be nice
[14:13] <mzanetti> nik90_: sure
[14:14] <nik90_> mzanetti: when would you like to have it?
[14:14] <mzanetti> hmm, maybe a bit later today...
[14:15] <mzanetti> nik90_: a bit busy atm, can I ping you later about it?
[14:15] <nik90_> mzanetti: alrite, ping me when you are free later
[14:15] <mzanetti> ok
[14:15] <nik90_> yeah
[16:07] <bzoltan> nik90_:  thank you for helping out the folks with the menu probelm :) I was out of network reach.
[16:27] <nik90_> bzoltan: no worries :)
[16:51] <bzoltan> nik90_:  so it seems that the new 3.1.1 release did not mess up anything :)
[16:51] <nik90_> bzoltan: yup :)
[16:52] <bzoltan> nik90_: it is a huge luck that we got the qtc 3.1.1 backported to qt52 ... when it was released with the 5.3 I wonder how long our luck will last. At some point QtC will not be backportable to the LTS
[16:53] <nik90_> bzoltan: I can imagine..I have been coding in a 14.10 VM for the past few weeks. I suppose we must update the instructions on developer.ubuntu.com to use a 14.10 VM or release instead of 14.04
[16:54] <nik90_> bzoltan: Or even better, provide a downloadable VM that people can use just for development purposes with all the necessary tools ready
[16:56] <nik90_> bzoltan: In the future when Unity 8 becomes default, would it be possible to provide QtC+Qt 5.x in a click package that people can install without having to upgrade their OS? That would make it super convenient to stick with one OS version and keep updating the SDK.
[16:57] <bzoltan> nik90_: Yes, in the confined click world this issue will be different.
[16:58] <bzoltan> nik90_:  SDK in VM is a trivial solution but to be honest I find it rather unprofessional as a primary method of distribution.
[16:59] <nik90_> bzoltan: I agree, but requesting developers to download a development release of Ubuntu which cannot be found so easily is helpful either.
[16:59] <nik90_> isn't helpful either*
[16:59] <bzoltan> nik90_: I think either the co-installation of minor Qt releases should be resolved, or we need to install the Qt to the user space.
[17:00] <bzoltan> nik90_:  LTS is LTS, so we will never suggest developers to upgrade from LTS to use the SDK
[17:00] <nik90_> bzoltan: at the moment, for an external 3rd party app dev, it is confusing to install 14.04 and then realise that he won't get the new headers and other cool sdk features
[17:19] <bzoltan> nik90_: why would not he get? It is all in the emulator and in the chroot... When a developer installs the Android SDK on OSX is it expected to see all the android APIs on the OSX?
[17:20] <bzoltan> nik90_: I know it will take time to educate some folks that the development environment and the target environment are two different place
[17:20] <nik90_> bzoltan: true that would work
[17:22] <bzoltan> nik90_:  the problem right now is that we should support not only the phone app development but the desktop app/scope development. Right now we have good target emulator of the phone, but not for the desktop. But it is being worked out :)
[17:23] <nik90_> bzoltan: yeah I am waiting for rsalvetti to add support for updating the emulator images on the fly. Currently we have to recreate the emulator to get the latest image
[17:24] <nik90_> bzoltan: although I guess this shouldn't be too much of an issue for people targetting the stable images in the future
[17:29] <bzoltan> nik90_:  yes, it should not be much. The emulator update would be fun.