=== praneshp_ is now known as praneshp
=== shardy_afk is now known as shardy
=== evilissimo|afk is now known as evilissimo
=== harlowja is now known as harlowja_away
=== zz_gondoi is now known as gondoi
=== evilissimo is now known as evilissimo|afk
=== xmltok_ is now known as xmltok
=== harlowja_away is now known as harlowja
=== gondoi is now known as zz_gondoi
=== zz_gondoi is now known as gondoi
=== gondoi is now known as zz_gondoi
[17:43] <mgagne> anyone knows where I could find a backport of cloud-init 0.7.x for Precise?
[17:55] <smoser> mgagne, i've not done one. 
[17:55] <smoser> i dont think there are too many issues if you just build trunk
[17:55] <smoser> ./tools/builddeb -us -uc
[17:56] <mgagne> smoser: I'm looking at PPA and looking for a tutorial on how to backport stuff from trusty to precise so I can do it myself
[18:00] <smoser> mgagne, yeah. thats the right path. i'  not sure off the top of my head what would be problems.
[18:01] <smoser> i've done that as recently as 0.7.0
[18:01] <smoser> https://launchpad.net/~maas-maintainers/+archive/ubuntu/maas-ephemeral-images
[18:01] <mgagne> smoser: well, my main challenge is: how do I do this? apt-get source cloud-init on trusty, update changelog to target precise, dput to ppa and hope for the best?
[18:12] <smoser> mgagne, yeah. mostly. you can build it in a sbuild chroot to test locally
[18:13] <smoser> before going to ppa
[18:13] <smoser> (i'd recommend that for quicker turn around)
[18:13] <smoser> but one way or anotehr test it buildling locally before pushing ot a ppa
=== zz_gondoi is now known as gondoi
[20:26] <mgagne> smoser: lets say I have a bunch of dependencies missing that would need to be backported too. How can I programmatically get the list of missing dependencies so I can automate the process?
[20:27] <smoser> you shoudln't have too many dependencies
[20:27] <smoser> for cloud-init ?
[20:29] <mgagne> smoser: yep, it now requires python-json-patch, python-json-pointer and openstack-pkg-tools
[20:31] <smoser> hm..
[20:31] <smoser> let me see.
[20:34] <mgagne> smoser: it's the first time I create a ppa and backport a package so I'm not familiar with backporting challenges. sorry if I ask a lot of questions =)
[20:37] <smoser> thats ok. 
[20:38] <mgagne> smoser: I see backportpackage command exists. Will it take care of dependencies?
[20:38] <smoser> i dont know. i doubt.
[20:38] <smoser> where did youthink you needed openstack-pkg-tools ?
[20:39] <smoser> and python-json-pointer?
[20:40] <mgagne> smoser: this guy thinks he needs it: http://packages.ubuntu.com/source/trusty/python-json-patch
[20:40] <smoser> yeah, you do need that.
[20:40] <mgagne> smoser: python-json-patch needs python-json-pointer
[20:40] <smoser> ah. 
[20:40] <smoser> hm..
[20:40] <mgagne> smoser: so you see the rabbit hole I'm going into
[20:43] <smoser> well, you can probaly fairly easily drop the jsonpatch 
[20:43] <smoser> and its not a big deal.
[20:43] <smoser> something i had hoped to develop more
[20:44] <mgagne> smoser: ok, I'll try to drop it. I was hoping to not have to modify debian/control and have to version it somewhere =)
[20:45] <smoser> hm..
[20:45] <smoser> you'll also have to modify code to do that. i think. not much, it should be contained in 
[20:45] <smoser> cloudinit/handlers/cloud_config.py
[20:47] <mgagne> smoser: I just don't understand why python-json-patch needs a run-time dependency on openstack-pkg-tools though
[20:47] <smoser> not runtime
[20:47] <smoser> build time.
[20:47] <smoser> http://paste.ubuntu.com/7810965/
[20:48] <mgagne> smoser: true, my mistake
[20:48] <mgagne> smoser: will try your patch, thanks
[20:49] <smoser> make test will probably fail too
[20:49] <mgagne> smoser: I guess I can take care of it too
[20:50] <smoser> yeah, or just disable that if it even runs it in the build
[20:50] <smoser> i dont remember 
[20:51] <mgagne> smoser: should be trivial to add your patch and disable associated tests, will start with that for now
=== gondoi is now known as zz_gondoi
=== samkottler is now known as Guest92729