User1: where are packaging scripts usually stored in relation to the source code repository?  like if I wanted to package http://code.google.com/p/jujuutils/ would I check out it out, add debian/*, create a repo on lp and push it all there?
User1: or just push debian/* and have a reference to the rev of http://code.google.com/p/jujuutils
User2: Hi all, I can't find anywhere docs on the process for getting a security update uploaded to the archive... pointers?
User2: Oh wait, I think I found it a few links further down the track :)
User3: User2 file a bug, attach a patch, get it sponsored by the security-team
User2: Ok, thanks
User3: User1 check it out.  Add your the  debian/  directory.    debuild -S   and upload
User3: User1 (you could of course keep the combined result in git aswell and merge from new upstream versions
User1: User3 I know I could.. I am wondering if there is a convention.
User3: User1 many conventions :-)  The only thing in-common is the  debuild -S  and  dput ppa:...  step :)
User1: i guess dput does store the source. and changelog has enough commit history/comments.  hmm.
User3: User1 well, one causes the output of a "source package" and the other uploads that to LP
User3: User1 those steps can be done manually with lots of low-level commands (eg. FTP), but it's a massive hassle
User1: User3 yeah, I was more thinking of them like compile and post a binary.
User3: User1 the system does the building for you
User4: anyone fancy doing a bunch of no-change rebuilds? ;)
User4: good for your karma...
 * ScottK bets Laney has a fence that needs whitewashing too.
User4: there /is/ a pile of washing up in the kitchen :-)
 * Laney writes a script instead
User5: so go do it
User5: its great for your karma
User4: what?
User5: what or why?
User6: http://www.pbs.org/marktwain/learnmore/writings_tom.html <-- for those unfamiliar with the whitewashing a fence story (caution: archaic language)
 * X3lectric slaps ScottK around a bit with a large trout
ubuntu-motu
Ubuntu IRC