[03:02] <wgrant> DarkPlayer: I think I have a fix.
[03:02] <wgrant> Am investigating.
[03:04] <DarkPlayer> wgrant: nice, but i already created a git mirror supporting the git protocol which hopefully solves my problem
[09:51] <punter> My "punjab" package in my launchpad repository is not searchable at all from launchpad.net searchbar: https://launchpad.net/~karjala/+archive/jabber and https://launchpad.net/+search?field.text=punjab
[09:52] <punter> Is there something I can do to make it appear in the search results?
[18:40] <smoser> http://package-import.ubuntu.com/status/cloud-init.html#2013-08-01%2022:12:33.994912
[18:40] <smoser> anyone have ideas on that
[18:40] <smoser> xnox kicked a clean import for me
[18:40] <smoser> and it failed that way
[18:42] <dobey> smoser: stable release branches are set read-only
[18:42] <maxb>  It feels like lp has revoked some permissions the importer needs
[18:43] <dobey> smoser: if you want to fix a broken branch by importing to it, then it needs an RT or question on launchpad, i guess
[18:43] <maxb> it did not used to
[18:44] <maxb> I wish people wouldn't pull permissions the importer uses out from under it
[18:45] <dobey> dunno. my understanding was that release branches are set to read-only when a stable release of ubuntu is made.
[20:19] <smoser> dobey, maxb the error mentioned above is from re-import (throw away history and start import anew)
[20:19] <smoser> its possible that just hadn't occurred before. that the importer had never tried to import history a release that had been closed.
[20:25] <dobey> smoser: ah, that could be it. importing to maverick at this point would definitely be odd by any means
[20:25] <smoser> any ideas as to how to get it done anyway ?
[20:26] <smoser> "re-import from archive history" seems like a reasonable path to work.
[20:26] <smoser> ie, i'd like cloud-init to have some source :)
[20:27] <dobey> smoser: i'd ask a "question" against answers.launchpad.net/launchpad, or file an RT for it.
[20:27] <dobey> smoser: you're trying to import it to maverick, or to saucy?
[20:27] <smoser> the history was screwed up and imports would fail
[20:28] <smoser> due to some combination of importer bugs or lUser error (probably smoser's fault)
[20:28] <dobey> probably importer bugs
[20:28] <dobey> it seems to create broken conditions quite often :)
[20:29] <smoser> so i wanted importer to work
[20:29] <smoser> and we tossed the history with the intent of letting the importer figure it all out
[20:29] <smoser> the issue that started it was that i had decided to ifght the importer at some point over revision controlling .pc files (which i still think is sill, but am willing to not fight a bot over)
[20:29] <smoser> s/sill/silly/
[20:31] <dobey> yeah. i certainly don't have enough permissions to help fix it though. i think a losa will have to help. i think the questions system or an RT are the best way to do that, these days
[20:32] <dobey> (or ping one who is on duty at the moment, in the event it's a trivial thing to fix)
[20:48] <maxb> It probably needs a code change to give back the importer the permissions it is written to expect to have
[20:48] <smoser> dobey, https://answers.launchpad.net/launchpad/+question/234047
[20:49] <smoser> maxb, ^
[20:49] <smoser> xnox, also. ^
[20:50] <smoser> i figured that launchpad question was more reasonable as it might then be found by someone less "connected" (to canoncial) than myself.
[20:52] <maxb> There's a bunch of branches for cloud-init all ready on jubany, it's just erroring when it tries to upload them
[20:52] <maxb> It looks like it's trying to register a new official branch to represent the history in maverick-proposed
[20:54] <smoser> that would make sense.
[20:54] <smoser> thats what i want.
[21:02] <DarkPlayer> Hello, is the tag {git-commit} in bzr builder scripts for git imports supported ?
[21:05] <maxb> smoser: I don't know when this got broken, but I think we're going to end up needing a code change
[21:06] <smoser> maxb, thanks, and any help is greatly appreciated.
[21:06] <maxb> the only way I can see to not do that would be for ~techboard to create a new team, add themselves and ~package-import to it, and make it the owner of the Ubuntu distribution object in Launchpad
[21:06] <maxb> Which probably would grant ~package-import rights that it really shouldn't have
[21:16] <DarkPlayer> okay after changing the builder script version to 0.4 (to support the git tag) I encounter bug 915505 and the builder crashes. As the revision numbers are not linear in the git import and even decrease sometimes, I will stick to the time as the only reliable way to prevent duplicate source uploads.