[03:18] <bkerensa> How would I upload a patch for possible sponsor?
[03:19] <nigelb> You can either attach a debdiff to a bug and subscribe ubuntu-sponsors
[03:19] <nigelb> Or you can submit a merge proposal
[03:20] <bkerensa> nigelb: Ahh well I prepared a packge for multiarch at the join Jam/DSP and just wanna get credit for my first submission
[03:20] <bkerensa> nigelb: which might be easier?
[03:20] <nigelb> heh, that varies from sponsor to sponsor.
[03:20] <nigelb> I personally find debdiff easier
[03:20] <nigelb> But I might be old school :P
[03:22]  * micahg also prefers debdiff, but that only works if there isn't an official non-UDD Ubuntu VCS branch
[03:23]  * micahg is piloting tomorrow, so can take a look then
[03:24] <bkerensa> micahg: Well I do not know how to do either ;) so any guidance :P this isnt a bug but just a package moved to multiarch
[03:25] <micahg> bkerensa: I have to run right now, but someone else should be able to help you here, otherwise, I'll be happy to when I get back (1-4 hrs)
[03:29] <jtokarchuk> so how does MOTU work? I have read the literature, but can I basically just pick a package that's not in ubuntu and make it so? Is there a todo list?
[03:37] <stlsaint> JontheEchidna: https://wiki.ubuntu.com/MOTU/GettingStarted
[03:44] <jtokarchuk> I'm going to assume that was directed at me, I read that, so essentially, just work through bugs and produce meaningful packages?
[04:30] <micahg> jtokarchuk: that's the general idea, MOTU fixes random stuff in the archive
[04:30] <micahg> bkerensa: did you manage to find help yet?
[04:31] <jtokarchuk> micahg, Thank you. I submitted an app for mentorship, but am awaiting a reply
[04:31] <bkerensa> micahg: Yeah apparently I should wait till patch is uploaded upstream then sync down and I will get credit since I'm in changelog?
[04:32] <micahg> bkerensa: well, you won't get credit in LP per se, but it can count towards development activity
[04:34] <micahg> bkerensa: regardless of whether or not a patch is uploaded to Ubuntu, we try to upstream appropriate patches to Debian
[04:35] <EvilResistance> micahg:  so they get synced in to the next version of Ubuntu?
[04:35] <EvilResistance> (from debian)
[04:35] <micahg> bkerensa: the question of whether or not to upload to Ubuntu directly vs Debian is time frame and immediate impact of having the fix in Ubuntu generally
[04:35] <micahg> EvilResistance: we're still in Debian Import mode
[04:35] <EvilResistance> micahg:  true, but i meant when in a non-import mode
[04:35] <EvilResistance> i.e shortly after the release of oa version of ubuntu
[04:36] <EvilResistance> s/oa/a/
[04:36] <micahg> EvilResistance: eh, depends on what and when
[04:36] <bkerensa> micahg: What if someone does the same work and I miss out?
[04:36] <bkerensa> :D
[04:36] <bkerensa> micahg: I just dont know how to submit the patch since it is not a bug but instead moved a package to multiarch
[04:37] <micahg> bkerensa: you can still use a wishlist bug to track that sort of thing
[04:37] <micahg> bkerensa: which package is it?
[04:37] <bkerensa> audiofile0
[04:38] <EvilResistance> you mean libaudiofile0 ?
[04:38] <EvilResistance> (there's nothing that directly matches audiofile0 in natty, oneiric, or precise)
[04:38] <micahg> EvilResistance: hopefully he means the audiofile source :)
[04:39] <EvilResistance> indeed
[04:40] <EvilResistance> wouldnt that show up in the source repos though?  *tends to have them enabled by default*
[04:41] <micahg> bkerensa: IMHO, that should probably go through Debian as it has a lot of reverse dependencies that might break with the multiarched package, you can file a bug in LP for Ubuntu and link it to the Debian bug so people are aware of your work
[04:42] <micahg> eh, I guess <30 isn't that many...but still having 10 days to migrate from unstable to testing gives time to catch these things
[04:43] <micahg> slangasek: ^^ any opinion on whether or not multiarched audiofile should go through Debian first?
[04:44] <bkerensa> micahg: heh well slangasek will be adding to debian since he helped me multiarch it ;)
[04:45] <micahg> bkerensa: well, whatever he says, I'd listen to in this case :)
[04:45] <bkerensa> peh :P
[04:45] <micahg> actually, I'd listen to what he says in general :)
[04:45] <bkerensa> :D
[05:12] <slangasek> bkerensa, micahg: we certainly want multiarch patches to be pushed to Debian, but we don't want Ubuntu to wait for them to land in Debian first
[05:12] <slangasek> because there's no guarantee that will happen in time for precise
[05:13] <micahg> slangasek: what do we do about rdeps, rebuild blind?
[05:15] <slangasek> micahg: what about rdeps?  multiarch doesn't require them to be rebuilt unless there are .la file references
[05:16] <micahg> slangasek: ah, ok, I know sometimes depending on how paths are hard-coded in apps at build time, a rebuild might be necessary, but I guess the answer is wait and see if anything breaks and fix it :)
[05:19] <micahg> i.e. pkg-config paths converted to some version of hard-coded paths at run-time
[05:19] <slangasek> oh, well, that is generally only relevant when plugins are involved
[05:19] <slangasek> which is why today's Local Jam avoided libraries with plugins :)
[05:22] <micahg> sounds good
[05:23] <micahg> bkerensa: so, if you get can get a debdiff into a bug and that bug in the sponsorship queue, I'll have a look tomorrow when I'm piloting, unless slangasek was planning on sponsoring :)
[05:25] <micahg> bkerensa: https://wiki.ubuntu.com/PackagingGuide/Complete#Traditional_Process if you didn't use bzr to get the source package
[05:26] <micahg> bkerensa: https://wiki.ubuntu.com/PackagingGuide/Complete#Use_Ubuntu_Merge_Proposals if you did use bzr
[05:47] <bkerensa> micahg: How do I turn the .patch into debdiff?
[05:49] <bkerensa> slangasek: ok well.... I need to figure out how to get a debdiff from the patch file I have?
[05:50] <slangasek> bkerensa: it's already a debdiff
[05:50] <slangasek> a debdiff is just a patch expressing the difference between two source packages :)
[05:50] <bkerensa> slangasek: Oh ok and I just need to file a bug requesting it be added or?
[05:50] <bkerensa> :D
[05:50] <slangasek> bkerensa: yep
[05:50] <bkerensa> slangasek: Nothing special? if so I will file it now with Debian and Ubuntu
[05:51] <slangasek> bkerensa: nope, nothing really special :)  I did send you an email with some info about how to file the bug in Debian, but if you already know how to do that, you can ignore that mail
[05:53] <jtokarchuk> x.x Why does it seem that everything is fixed in harvest
[06:00] <bkerensa> slangasek: Ok just fired away to Debian
[06:00] <bkerensa> :D
[06:01] <bkerensa> slangasek: Is the format of opening a bug pretty much the same?
[06:01] <bkerensa> on Ubuntu
[06:01] <slangasek> bkerensa: no, for Ubuntu it's best to use the 'ubuntu-bug' command
[06:01] <bkerensa> heh
[06:02] <bkerensa> ;)
[06:02] <bkerensa> slangasek: Then I just attach the same patch and request it be supported?
[06:02] <slangasek> yes - https://wiki.ubuntu.com/PackagingGuide/Complete#Traditional_Process
[06:04] <broder> slangasek: out of curiosity, has pkg-create-dbgsym been modified to set multi-arch same?
[06:04] <slangasek> I don't know
[06:07] <broder> oh hey, apparently it does. go pitti
[06:10] <bkerensa> slangasek: https://bugs.launchpad.net/ubuntu/+source/audiofile/+bug/900153
[06:11] <bkerensa> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651029
[07:06] <micahg> bkerensa: thanks for your work :), I should be able to get to this tomorrow when I pilot unless pitti beats me to it
[07:09] <bkerensa> micahg: thx
[07:54] <dholbach> good morning
[08:14] <highvolt1ge> jgood morning
[08:14] <highvolt1ge> *good
[08:26] <Laney> ello
[17:21] <l3on> fabrice_sp, ping
[17:37] <l3on> cjwatson, can I look at merging ttf-cjk-compact ?
[17:40] <cjwatson> l3on: please leave that to me
[17:40] <l3on> cjwatson, ok :)
[17:41] <l3on> some merge to suggest? :)
[17:42] <micahg> l3on: there are some labeled free to take on merges.ubuntu.com
[17:43] <l3on> micahg, ok :)
[18:00] <micahg> l3on: would you happen to be interested in preparing security updates?  there's lots of those that need to be done for universe packages
[18:00] <l3on> micahg, ok... could you provide more info? :D
[18:00] <jtaylor> is there a list for security updates that need done?
[18:01] <micahg> jtaylor: http://people.canonical.com/~ubuntu-security/cve/universe.html
[18:02] <micahg> we also highlight 5 packages per week in our weekly security meeting in #ubuntu-meeting starting about now :)
[18:04] <micahg> here we keep a list of highlighted packages which gets refreshed weekly: https://wiki.ubuntu.com/SecurityTeam/HighlightedPackages
[18:05] <micahg> if you're interested in helping with these, feel free to join #ubuntu-hardened to learn more :)
[18:07] <l3on> thanks , I'll do :)
[19:57] <fabrice_sp> l3on, pong
[19:58] <fabrice_sp> !ping > l3on
[20:19] <jtaylor> is there some documentation on all the motu formalities and procedures? I still suck at navigating the wiki efficently ._.
[20:21] <geser> I don't know of any, just ask and someone will point you to the matching wiki page :)
[20:21] <tumbleweed> there are no formalities, really
[20:21] <tumbleweed> https://wiki.ubuntu.com/UbuntuDevelopers and https://wiki.ubuntu.com/Membership list the benefits
[20:22]  * micahg thought there was a work item that came out of UDS for new developer tasks
[20:22] <tumbleweed> DMB session?
[20:22] <micahg> maybe
[20:22] <tumbleweed> we seem to have a massive lack of notes for it...
[20:22] <micahg> ah :)
[20:24] <zooko> Dammit, I just registered https://launchpad.net/python-fs and I somehow failed to change the desired URL to https://launchpad.net/pyfilesystem .
[20:24] <zooko> I don't see how to change it now.
[20:24] <jtaylor> yey lwn subscription :) only I'm already ~4 weekly editions behind in reading :/
[20:24] <zooko> Shall I send some sort fo support request to launchpad?
[20:25] <cjwatson> zooko: I believe so, yes; https://answers.launchpad.net/launchpad
[20:25] <zooko> Hrm, and why can't I report a bug here now? https://bugs.launchpad.net/python-fs
[20:25] <zooko> cjwatson: thanks.
[20:26] <cjwatson> Bug tracking has to be turned on explicitly for new projects.  Should be in https://launchpad.net/python-fs/+configure-bugtracker
[20:26] <cjwatson> linked from the front page under "Configuration options"
[20:26] <cjwatson> the project page, I mean
[20:31] <tumbleweed> cjwatson: we were chatting a while ago about a tool that'll tell you if something is safe to upload during a freeze
[20:31] <zooko> cjwatson: thanks.
[20:31] <tumbleweed> i'm currently grabbing daily build .list and .manifests to build an index of included packages
[20:31] <zooko> cjwatson: https://launchpad.net/python-fs/+configure-bugtracker says "Sorry, you don't have permission to access this page. "
[20:31] <tumbleweed> micahg, and stgraber suggested grabbing the contents of the supported seed too
[20:32] <zooko> cjwatson: but I already requested that launchpad folks do it in my launchpad support question.
[20:32] <tumbleweed> is there any convenient way to do that?
[20:32] <micahg> tumbleweed: it's in a bzr branch
[20:32] <tumbleweed> micahg: aah
[20:33] <stgraber> micahg: or rather, in multiple bzr branches
[20:34] <micahg> stgraber: right, just saw there's the desktop supported and then other supported in platform (and possibly others in the other seed branches)
[20:34] <stgraber> tumbleweed: http://people.canonical.com/~ubuntu-archive/seeds/*/supported
[20:34] <stgraber> tumbleweed: http://people.canonical.com/~ubuntu-archive/seeds/*.precise/supported rather
[20:34] <tumbleweed> stgraber: will they always have the same names?
[20:34] <tumbleweed> otherwise I've got to parse HTML file listing
[20:34] <cjwatson> um, that only gives you the top-level packages
[20:34] <cjwatson> please don't reinvent germinate
[20:35] <tumbleweed> heh
[20:35] <cjwatson> it's complicated enough as it is
[20:35] <stgraber> yeah, the initial suggestion was to look at germinate's output :) not sure what tumbleweed needs that's not part of germinate's output
[20:35] <cjwatson> http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.precise/structure and then work from the files it lists
[20:35] <cjwatson> it's kind of complex though
[20:35] <tumbleweed> ah, missed that file
[20:36] <cjwatson> and that's only for i386; there will be some differences across architectures
[20:36] <cjwatson> and s/ubuntu/somethingelse/ etc.
[20:36] <cjwatson> also why is the supported seed relevant?  supported doesn't end up on any images
[20:37] <micahg> cjwatson: the only time it seems relevant is after final freeze
[20:37] <el2ro> Hi, could someone help a bit explaining in rough level.. what would be needed to build (backport) some packages in lauchpad?
[20:38] <cjwatson> we could symlink the LP publisher's germinate output to somewhere public, maybe
[20:38] <cjwatson> that might not be an entirely crazy thing to do
[20:39] <el2ro> I have started to play with backportpackage tool.. And tried to backport latest PHP to lucid, but it fails with dependency issues. Those should not be so hard to fix, but is there some page explaining what backportpackage tool is doing... e.g. how to that stuff manually and fix the package to make it work
[20:40] <tumbleweed> cjwatson: I assume that'd give the output from other architectures?
[20:41]  * tumbleweed has a go at parsing this
[20:42] <micahg> el2ro: backportpackage just changes the version so that's it's lower than the current one to support upgrades, it also changes the target in the changelog to whatever you're targeting (it has nice help output to show you the rest of its features), it won't "fix" a backport for you though, for that you need to make source changes
[20:46] <el2ro> micahg: ok, but I am still missing the big picture :) Howto do those things manually and fix things. What tools needed to fetch package from launchpad... changes most likely I can handle... how to push changes package to own PPA.
[20:47] <el2ro> I guess it is not so hards, but learning curve is so hard or well hidden, that it is so templating just building stuff on my web hosts and I don't want to do that :)
[20:54] <micahg> el2ro: well, if you're using backportpackage, you already have the source, you'll want to look in the source folder at debian/control, these instructions might be helpful as well: https://wiki.ubuntu.com/PackagingGuide/Complete#Updating_an_Ubuntu_Package
[20:57] <micahg> el2ro: actually, this one might be better except you don't need steps 8 or 9 (https://wiki.ubuntu.com/PackagingGuide/Complete#Traditional_Process)
[20:58] <el2ro> micahg: thx, I will take a look if they will take me any further
[21:04] <cjwatson> tumbleweed: the LP publisher's output would, yes
[21:06] <tumbleweed> any way to get a lits of the flavors? (pity it isn't rsyncable, like cdimage.u.c is)
[21:07] <cjwatson> LP source, cronscripts/publishing/cron.germinate, I'm afraid
[21:07] <tumbleweed> meh, I'll just use hardcoded lists that get stale
[21:07] <micahg> tumbleweed: wget --mirror?
[21:08] <tumbleweed> micahg: yeah, that's the other way...
[22:07] <jtaylor> ubuntu no change rebuilds will auto-sync?
[22:14] <micahg> jtaylor: yes (i.e. -XbuildY)
[22:24] <tumbleweed> micahg: is that output better?
[22:25] <micahg> tumbleweed: what output?
[22:25] <tumbleweed> micahg: committed a new version of the ubuntu-safe-to-upload tool (it's new name)
[22:25] <micahg> tumbleweed: ah, will check
[22:28] <micahg> tumbleweed: looks nice
[22:29] <micahg> tumbleweed: although the name doesn't match the tool per se
[22:29] <tumbleweed> is-seeded ?
[22:30]  * micahg forgot what the hangups around the word seeded were
[22:30] <tumbleweed> people misuse the term a lot
[22:30] <tumbleweed> this, of course, started out looking at image contents, not seeds
[22:31] <tumbleweed> but now does look at seeds (although not all seeds, only supported)
[22:31] <micahg> is-seeded seems appropriate since this is what it's checking
[22:50] <broder> tumbleweed: can i possibly get you to sponsor http://mentors.debian.net/package/rfs/freeimage for me?
[22:50] <broder> hmm...actually, hold that thought. i just realized that i want to try and tweak one of my patches for the purposes of future maintenance
[22:51] <tumbleweed> hrm, it's git tree is out of date
[22:52] <el2ro> Some help pls... trying to upload a package to ppa with dput to be build for lucid (from Oneiric). How to make it build that stuff only to lucid?
[22:53] <tumbleweed> el2ro: put lucid as the distribution in the changelog
[22:54] <el2ro> tumbleweed: thanks, I will try to digg in
[22:57] <broder> tumbleweed: oh, huh. i didn't notice it had a git tree. my inclination is to just drop the debian/control tags
[22:57] <tumbleweed> it's only *just* out of date, so easy enough to sync it up again
[22:57] <broder> oh, i see. ok
[22:58] <tumbleweed> oh, sorry, it is up to date
[22:58] <tumbleweed> just not tagged
[22:58] <broder> ugh. yeah, but reconstructing the history in git will be annoying
[22:58] <broder> i guess i can do it the trivial way
[22:58] <tumbleweed> yeah, screw pretty history
[22:59] <tumbleweed> it's orphaned, after all
[23:00] <broder> the package is kind of a mess - it ships with embedded copies of a half dozen libraries
[23:00] <broder> and its makefile lists the source files for *all* of them on a single line
[23:01] <Resistance> broder:  wouldnt dget be preferred for getting the source packages for <packagenamehere> rather than using backportpackage to try and get the source?
[23:01] <broder> the last debian upload dropped in a new version of libtiff, which was the only one the uploader couldn't tease apart from the rest of the package
[23:01] <broder> which made the merge, uh, well, unpleasant
[23:01] <broder> Resistance: sorry, i'm not sure what you're referring to?
[23:02] <Resistance> broder:  random question, basically.  Which is preferred for getting the source package of any given package, in order for modification in order to prep for backporting?
[23:02] <broder> tumbleweed: i think i can tweak the patch process so that the insane makefile is generated automatically at build time, instead of being in debian/patches/ and requiring a painful manual merge
[23:02] <Resistance> broder:  assuming that the modification is needed before actually submitting to a PPA or testing the actual backport
[23:02] <broder> Resistance: i'm not really sure i see how that's a backport specific question
[23:02] <Resistance> broder:  its not sec
[23:03] <broder> but in general, i like pull-lp-source for getting random source packages
[23:03] <tumbleweed> broder: sounds reasonable
[23:04] <Resistance> broder:  do yo uknow if the oneiric php5 exists in the backports for natty?
[23:04] <broder> Resistance: "rmadison php5" can tell you that fairly quickly
[23:04] <broder> it doesn't look like php5 has been backported to any active release
[23:05] <broder> i would expect doing so to be a pretty hard sell
[23:05] <Resistance> mmm
[23:05] <Resistance> yeah, i was considering backporting it within a PPA (not in the -backports repo), but if it was already backported i'd just add the backports repo here ;P
[23:10] <Resistance> hey broder, possible bug in backportpackage
[23:10] <Resistance> broder:  theoretically this would work: backportpackage -s oneiric -p natty php5
[23:10] <Resistance> it errors
[23:11] <broder> uh, backportpackage doesn't take a -p argument
[23:11] <Resistance> s/-p/-d/
[23:11] <Resistance> accidential mistype
[23:11] <broder> can you pastebin the error?
[23:11] <Resistance> [kahless /var/teward/php/sourcepackage/oneiric]% backportpackage -s oneiric -d natty php5                                                  [ teward on pts/1 ]
[23:11] <Resistance> Usage: backportpackage [options] <source package name or .dsc URL/file>
[23:11] <Resistance> fooey
[23:12] <Resistance> anyways, its just not taking the source package name
[23:12] <Resistance> sec i'll pastebin the entire thing
[23:12] <broder> Resistance: you didn't specify an operation to do with the package once it was backported
[23:12] <Resistance> ah
[23:12] <broder> you either need to specify -w or -u
[23:12] <Resistance> -u is upload...
[23:13] <Resistance> what's -w
[23:13] <broder> so the build product has somewhere to go - either on your filesystem or LP
[23:13] <broder> it specifies a "temporary" directory to stuff the build products
[23:13] <broder> it should specify that in the error message:
[23:13] <broder> "backportpackage: error: Please specify either a working dir or an upload target!"
[23:13] <Resistance> yep seems to be working now
[23:14] <Resistance> i assume pbuilder is a prereq for using -w ?
[23:14] <broder> no
[23:14] <Resistance> ah
[23:14] <Resistance> nevermind there we go
[23:22] <Resistance> broder:  if i locally backport the oneiric php5 to natty, what's the probability i explode PHP?
[23:22] <Resistance> (upon installation in the natty system)
[23:23] <broder> no idea
[23:23] <Resistance> i guess asking in the php channel would be a better idea, or poking around the Ubuntu developer network?
[23:24] <broder> or at least finding somebody who knows how the php stack is put together (#ubuntu-server, maybe?)
[23:24] <Resistance> mmm
[23:25] <Resistance> i'll stop there
[23:25] <zooko> Folks, where is the official Ubuntu web page describing the Release Schedule?
[23:25] <zooko> And in particular, when is Feature Freeze for 12.04?
[23:25] <zooko> I'm wondering if we'll have a new Tahoe-LAFS release out in time for that.
[23:26] <broder> zooko: https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule
[23:26] <broder> FF is 2/16
[23:26] <zooko> thx
[23:26] <broder> note that feature freeze exceptions for packages in universe without a lot (any?) reverse-deps are pretty easy to get
[23:30] <zooko> When's the deadline for FF exceptions?
[23:30] <tumbleweed> they get harder to get, closer to release
[23:31] <broder> the hard, unbreakable cut-off is https://wiki.ubuntu.com/UnseededUniverseFinalFreeze
[23:31]  * zooko nods.
[23:31] <zooko> Okay, thanks.
[23:31] <broder> but it's sort of a gradual transition from "whatever you want goes in" to "nothing goes in"
[23:33] <broder> tumbleweed: ok, i'm happy with http://mentors.debian.net/debian/pool/main/f/freeimage/freeimage_3.15.1-1.dsc now
[23:33] <broder> it has some excellent dh-autoreconf abuse
[23:34] <tumbleweed> ah, I sponsored the current version in Ubuntu. That's why I remember it
[23:35] <broder> does that mean i can blame you for re-enabling the embedded libraries? :)
[23:35] <tumbleweed> broder: there wasn't much choice
[23:35]  * broder shrugs
[23:35] <broder> i think it's more long-term maintainable with my tweaks, hopefully
[23:36] <tumbleweed> unless I'm thinkig of something else...
[23:36] <Resistance> broder:  is there any way i can grab the Debian sid source for a package using either backportpackage or dget?
[23:37] <Resistance> or should I be askign that in the debian channel on their home net
[23:37] <broder> Resistance: backportpackage can take debian releases for -s
[23:37] <broder> alternatively, pull-debian-source
[23:37] <tumbleweed> broder: are you ignoring the git tree?
[23:38] <Resistance> broder:  so theoretically i can put sid in for -s and (attempt) to backport to <ubuntudistro> ?
[23:38] <broder> Resistance: yes
[23:38] <Resistance> (granted that'd be stupid to direct backport without testing ;P)
[23:38] <broder> tumbleweed: oh, bah. let me see if i can fake the requisite commits
[23:38] <tumbleweed> broder: ok, I'm off to bed, anyway, but I'll have a look in the morning
[23:39] <broder> tumbleweed: cool. i'm assuming i can't push to git.debian.org, so i'll throw the tree on github or something
[23:39] <tumbleweed> do you have an alioth account yet?
[23:39] <broder> i think so
[23:39] <broder> does that grant git.debian.org access?
[23:40] <tumbleweed> yes and no
[23:40] <broder> (incidentally, i don't actually blame you for turning the embedded libraries back on - it took me a solid 3 or 4 hours to get everything teased apart correctly)
[23:40] <tumbleweed> git.debian.org is part of alioth
[23:41] <tumbleweed> this package is in collab-maint, so all collab-maint members can commit to it
[23:41] <Resistance> broder:  out of curiosity, is it possible to use both -w and -u simultaneously, thereby throwing the backported source into a directory, and uploading it to a PPA?
[23:41] <broder> Resistance: yes
[23:42] <broder> you just have to pass one of the options, otherwise backportpackage would do all of its work into a tmp dir and then chuck all of it
[23:42] <tumbleweed> broder: however, you can push a private branch, http://wiki.debian.org/Alioth/Git#Using_personal_Git_repositories
[23:42] <broder> tumbleweed: ok. i'll get that sorted out, then
[23:43] <tumbleweed> bonus points for adding the missing tags :)
[23:43] <broder> k
[23:45] <broder> snapshot.debian.org ftw
[23:45] <RoAkSoAx>  /win 4
[23:45] <broder> ooh, even better, git-import-dscs can do it for me
[23:45] <tumbleweed> broder: the commits look there, just not tagged
[23:45] <broder> ah, so they are