[00:04] <wonko> C++ it is. 8-)
[00:32] <OvenWerks> Huh, completely different than python 2 (and easier) create a new configparser then new_config.read_dict(config)
[00:32] <OvenWerks> and new_config is now the old config
[00:41] <wonko> oh, slick!
[00:43] <OvenWerks> Never did find an example... or what the parameters were supposed to be... try this that and the other till it works
[00:58] <wonko> That's programming in python!
[01:00] <wonko> Don't even get me started on the vmware module for python.
[03:04] <OvenWerks> wonko: git is not so fun
[03:05] <OvenWerks> I squashed as much of your commits as I could... then added my stuff on top and some how it shows yours on top of what I did
[03:05] <OvenWerks> I try again
[03:26] <OvenWerks> wonko: ok done
[03:27] <OvenWerks> umm, when working remotely and you remove the remote branch... remove the local branch too. pull to your local master then recreate your local branch and start working. Rebase was interesting
[03:27] <OvenWerks> Anyway it looks ok I think...
[03:30] <wonko> I'd say go for it then. I've been running the stuff out of my changes installed to the system. I'll upgrade to what you push to master.
[03:31] <OvenWerks> you probably want to do a git reset --hard to dcbbd7f761a9efb38d21adc444ae50d046cf6d5a
[03:31] <OvenWerks> then pull
[03:32] <OvenWerks> that should get rid of anything that is out of order etc.
[03:33] <OvenWerks> if you need to go back farther... pick ec3dd8efae2f64563dffe3c27abe8d873adb88c4 which is last release
[03:40] <Eickmeyer> You guys broke something.
[03:40] <OvenWerks> cool
[03:42] <OvenWerks> Eickmeyer: where do we try to do something with notes.txt?
[03:42] <Eickmeyer> I'm looking into it.
[03:43] <Eickmeyer> Ok, it's part of the dh_installdocs script. Did you remove that file?
[03:44] <OvenWerks> yes, the info is now a part of the source where it belongs
[03:45] <Eickmeyer> Hmmm....
[03:45] <Eickmeyer> Lemme try a local build.
[03:45] <OvenWerks> I can't find that script
[03:50] <Eickmeyer> Ok, so... dh_installdocs is part of debhelper. It expects a notes.txt in the root directory, so I would put it back as it puts it into  usr/share/docs automatically.
[03:50] <Eickmeyer> All deb packages are expected to have a notes.txt as a release notes type thing.
[03:50] <Eickmeyer> OvenWerks: ^
[03:51] <OvenWerks> Eickmeyer: well I should put something more appropriate in the file then :)
[03:51] <Eickmeyer> Yeah, that's what I would do.
[03:52] <Eickmeyer> As soon as I created a dummy notes.txt it built just fine.
[03:53] <OvenWerks> That file being there was a fluke, I used it to put some notes in about the format of a list/structure... I no longer need it so I removed it :P
[03:53] <Eickmeyer> Gotcha.
[04:03] <OvenWerks> Trying again.
[04:04] <Eickmeyer> Ok.
[04:09] <OvenWerks> didn't fail.
[04:11] <Eickmeyer> Sweet. That's all it needed.
[15:08] <Eickmeyer> OvenWerks: I was a bit wrong, that file isn't actually needed (though, I do like it). It's called by debian/docs
[15:09] <Eickmeyer> (based my info on an outdated version of debhelper)
[19:03] <OvenWerks> Eickmeyer: well if it doesn't publish for lack of it, it is not hard to put in. It is OTOH one more thing to maintain...
[19:04] <Eickmeyer> OvenWerks: Ok, completely up to you. Either way, the file to edit is debian/docs.
[19:05] <OvenWerks> I would guess it is easier reading than changelog
[19:05] <OvenWerks> and it is done now so why remove it?
[19:07] <OvenWerks> at some point after the next cycles changes are in, we need to redo the man page, internal help and README
[20:42] <Eickmeyer> OvenWerks: Yeah, good idea.