[15:22] <enyc> superm1, tgm4883: ping =)
[15:23] <superm1> yep i'm around what's up?
[15:24] <enyc> superm1: ""if needbe i create a bug...   Please remind me  of the exact approach for bugs in this context..  I don't want to accidentally post bug against mythtv ubuntu version rather than mythbuntu PPA etc
[15:25] <enyc> superm1: i was trying ot ask tgm4883
[15:25] <superm1> what's the bug about ?
[15:25] <enyc> superm1: packaging related, not code
[15:25] <superm1> i'd just make a git pull request
[15:25] <superm1> and send it to me and dekarl
[15:25] <enyc> superm1: i.e. fix the bug that breaks ipv6 connection to database, fix the bug ...... etc...
[15:25] <superm1> on github
[15:25] <superm1> one of us would get it
[15:25] <enyc> superm1: what which how where why when humm   not really familiar with doing
[15:26] <enyc> superm1: i've discovered the whys and wherefores of all sorts of complexity wrt 'svn' at placement...
[15:26] <superm1> svn?
[15:27] <superm1> basic steps:
[15:27] <enyc> superm1: subversion ;p
[15:27] <superm1> 1) open a github account if you don't have
[15:27] <superm1> 2) fork https://github.com/mythtv/packaging
[15:27] <superm1> 3) checkout that branch from your fork
[15:27] <superm1> 4) make changes, git add the files you changed, git commit them
[15:27] <superm1> 5) git push to your branch at github
[15:28] <superm1> 6) use the U/I at github to file a pull request
[15:28] <enyc> I like command lines =) but hey... =)
[15:28] <superm1> hopefully we get notifications at github, but i'm not sure - so just send me the URL here in case
[15:28] <superm1> you'll get attribution for all the changes then
[15:28] <enyc> ok, there are various, different, changes that fix various, different, problems...  should all these be sumbitted as one or  what?
[15:29] <superm1> separate for each fix
[15:29] <superm1> do it against the master branch first
[15:29] <enyc> as separate _branch_ ?   separate _git add_+_git commit_ ??
[15:29] <superm1> if they're applicable to other branches those should be against the approrpiate branches too
[15:29] <superm1> git add $FILE
[15:29] <enyc> I'm not familiar with the various branches you refer to
[15:29] <superm1> # git commit
[15:29] <enyc> I (thought) this was 'one stream' we just fix our mythtv 0.27 packaging....
[15:29] <superm1> so when you check out that packaging branch - that's the "master" packaging, eg 0.28 or trunk
[15:30] <enyc> oh i see
[15:30] <superm1> we fix stuff there, and then backport to older branches
[15:30] <superm1> after you fix it in master, you can locally do a "git checkout fixes/0.27"
[15:30] <superm1> and then you are working on the fixes/0.27 branch
[15:30] <superm1> do the same set of fixes, or even cherry pick the sha-1 if that makes it easier
[15:30] <enyc> so you want me to checkout the 0.28 packaging, make changes there, git add git commit  in that context
[15:30] <superm1> Yes
[15:31] <superm1> once you're all said and done, i think you run:
[15:31] <superm1> # git push -a
[15:31] <enyc> hangon:  you will backport  or i should attempt to commit the same to both 0.28 and 0.27 ??
[15:31] <superm1> or something similar and it will push all your branches up
[15:31] <superm1> either way
[15:31] <enyc> understood
[15:35] <enyc> I need to do a little more testing at weekend, wheezy-i386 box and various things =)...
[15:36] <enyc> Need to figure out the update-rc.d or whatever postinst to make init script work
[15:36] <enyc> also need to figure out the  root:adm  vs syslog:adm  logfiles difference
[15:36] <enyc> otherwise, it largely seems that our packaging
[15:37] <enyc> can build/run on wheezy and trusty
[15:37] <enyc> AIUI you don't yet have a systemd init script, which would be a useful addition
[17:18] <superm1> yeah i've made a lot of changes over the previous year to make it usefulish on debian
[17:18] <superm1> but there probably will need to be a couple of places that you check if it's debian or ubuntu and set permissions or certain scripts etc
[17:18] <superm1> in terms of making init script work, dh_installinit is supposed to do that
[22:13] <enyc> superm1: hrrm... what mechanism do you use to check debian or ubuntu ??
[22:13] <superm1> enyc: lsb_release
[22:13] <superm1> or cat /etc/lsb-release
[22:14] <enyc> superm1: kk
[22:15] <enyc> superm1: any ideas on this weirdness... only applies to 0.27[well, not 0.25, not tried 0.28] on arm[el,hf,rpi]  on wheezy   [trusty-armhf works]   :  http://www.mythtvtalk.com/linker-issue-16751/
[22:17] <superm1> mmm not really sure on that
[22:17] <enyc> fwiw I'm going to try running the  marilatt/deb-multimedia  build on my arm chroots and see what happens =)
[22:18] <enyc> there may be some little fix in their debian diffs/patches / rules to compile =)
[22:58] <enyc> ooooh they fail in a different way ;p
[22:58] <enyc> Cannot open POTFILES.in.temp for writing at /usr/share/intltool-debian/intltool-update line 615.