 hi quadrispro, glad you are here
[00:11] <quadrispro> ScottL, thanks, nice to see you here around :)
[02:27] <persia> ScottL: Next step once the exception is approved is to get your stuff into the branch and get it uploaded.  Just ping us here.
[02:27] <persia> (as I don't think most sponsors can commit to the right bzr tree, etc.)
[03:22] <ScottL> persia, will a debdiff need to be created?  is that the mechanism?
[03:22] <ScottL> because I can start the debdiff now then
[03:22] <ScottL> just to be ready
[03:22] <persia> debdiff isn't necessary, but can help.
[03:23] <persia> The way we tend to do work on that package is to pull the branch, edit, and push a new one.
[03:24] <persia> https://code.launchpad.net/~ubuntustudio-dev lists all our branches, but you probably want to start from  lp:~ubuntustudio-dev/ubuntustudio-look/UbuntuStudio
[03:27] <persia> ScottL: So if you want to use bzr, and just shove the changes in there, that actually makes it *easier* for this package.
[03:27] <persia> IF you don't especially, and just want to send a debdiff, that can also work.
[04:26] <ScottL> persia, I'll start reading up on bzr (something I wanted to do at some point) and make this my direction
[04:26] <persia> ScottL: OK.
[04:27] <persia> Most of it is `bzr branch $URI`, make changes, `bzr diff` to check changes, `bzr debcommit` to commit the changes based on the updated contents of debian/changelog, `bzr push $other-URI` to push them somewhere for review/merge
[04:28] <persia> There's *lots* more to bzr, but that set ought be enough to get you productive.
[04:29] <ScottL> tre cool, thanks
[04:30] <persia> I generally recommend using `apt-get --download-only source $PACKAGE`in the directory first, to avoid a set of common mistakes.
[23:53] <ScottL> reminder about the monthly non-mandatory developers meeting scheduled in about 20 hours - https://wiki.ubuntu.com/UbuntuStudio/Meetings/2010Mar14
[23:53] <ScottL> don't forget about daylight saving time if it applies to you