[00:06] <maxb> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/237724
[00:06] <maxb> Seems relevant
[00:06] <elmo> !
[00:15] <spitfire_> fuck
[00:15] <spitfire_> maxb: is there a way to upload pre-compiled package to ppa?
[00:16] <elmo> spitfire_: no
[00:16] <elmo> maxb: thanks for the pointer; I've reopened the bug
[02:00] <thomasdelbeke> Hi
[02:00] <thomasdelbeke> was this the channel
[02:01] <thomasdelbeke> or was it ubuntu bugs
[02:15] <MTecknology> I created a project, created a series, but I can't find where to start adding code
[02:16] <nhandler> MTecknology: You probably want to host the code in a bzr branch
[02:16] <MTecknology> ya
[02:16] <MTecknology> oh...
[02:16] <MTecknology> i see now :)
[02:17] <MTecknology> no
[02:17] <MTecknology> Do I also need to create a team for it?
[02:18] <cody-somerville> no
[02:18] <nhandler> Unless you are the only person who will be pushing to the branch, you might want to make a team
[02:19] <MTecknology> there will be about 5 or 6
[02:20] <nhandler> MTecknology: Then you should probably create a team where these 5 or 6 people are members. Then, make the team the owner of the bzr branch
[02:20] <MTecknology> ok, ty
[02:20] <nhandler> You're welcome
[02:20] <MTecknology> wow - LP is starting to get complicated
[02:21] <MTecknology> easy if you know what you're doing - but there's getting to be a LOT to this thing
[02:21] <MTecknology> either that or I was just blind to all of it before
[02:22] <MTecknology> what do I put in for a Project
[02:22] <nhandler> For what? The bzr branch?
[02:22] <MTecknology> Owner is the team, Name is 1.0, and Project is main?
[02:22] <MTecknology> ya
[02:22] <nhandler> Project is your project on LP
[02:23] <MTecknology> The resulting location of the branch will be: ~scribed/scribed/1.0
[02:23] <MTecknology> I want the project name repeating twice?
[02:23] <MTecknology> oh - because it's team...
[02:23] <rockstar> MTecknology, are you registering a hosted branch on Launchpad?
[02:24] <MTecknology> ya
[02:24] <rockstar> MTecknology, don't register hosted branches.  Just push it.
[02:24] <MTecknology> oh
[02:24] <rockstar> So in the branch, just do `bzr push lp:~scribed/scribed/1.0`
[02:25] <MTecknology> what if I did it already?
[02:25] <rockstar> MTecknology, I have a personal vendetta against registering hosted branches.  It's confusing.
[02:25] <MTecknology> ok
[02:25] <rockstar> MTecknology, then you'll have to `bzr push --overwrite lp:~scribed/scribed/1.0`
[02:25] <MTecknology> How's this look? https://code.edge.launchpad.net/~scribed/scribed/1.0
[02:25] <MTecknology> I've always done --use-existing-dir
[02:25] <nhandler> rockstar: I've always registered and then pushed (unless creating a lot of branches). What is the downside to doing this?
[02:26] <rockstar> nhandler, the downside is that you have an extra step.
[02:28] <MTecknology> does the way I have it look good?
[02:30] <nhandler> rockstar: True, but for one branch, I don't find it too inconvenient. If I am doing bulk branch creation, I do skip the registration step
[02:31] <MTecknology> Now that I've done it once, I like it
[02:31] <rockstar> nhandler, but it's an unneccessary step.
[02:31] <nhandler> rockstar: But it does make it easier for people who aren't as familiar with bzr.
[02:31] <rockstar> nhandler, registration of hosted branches will one day go away, and there will be an explanation for getting a hosted branch up.
[02:32] <rockstar> nhandler, if you register first, then you have to specify --overwrite.  If you have to specify all these flags, you might as well use git.
[02:32] <nhandler> rockstar: Why not just have the registration page simply spit out the bzr push command to use? I think that is a a nice compromise
[02:33] <rockstar> nhandler, that's basically what it'll do.  "Want to create a hosted branch?  bzr push lp:blah/blah/blah"
[02:33] <nhandler> :)
[04:23] <thomasdelbeke> Hi there
[04:23] <thomasdelbeke> anyone home?
[04:24] <thomasdelbeke> OK, looks like the channel is dead
[04:24] <thomasdelbeke> not to mourn
[04:24] <thomasdelbeke> tomorrow is another day
[04:36] <lfaraone> Hi, I seem to be getting a failed build error because of PPA 404s, any idea why/how I can fix this? http://launchpadlibrarian.net/21587499/buildlog_ubuntu-intrepid-i386.abiword_2.6.4-5ubuntu2~ppa1_CHROOTWAIT.txt.gz
[04:47] <loic-m> Is there any way to force an upload to my ppa when uploading a modified package, but with same version as an already uploaded package?
[05:05] <rockstar> loic-m, no.
[05:19] <loic-m> Is there a solution (short of artificially bumping the version)? I've uploaded it as 0ubuntu1 and would like to upload a revised package as 0ubuntu1~ppa1
[08:09] <cemc> hi. are there some logs to the PPAs, to see if anybody's using ones PPA ?
[08:09] <cemc> one's*
[08:11] <persia> cemc, Not that are made available to PPA owners.
[08:11] <cemc> i see. thanks
[08:27] <stdin> cemc: https://launchpad.net/+builds
[08:27] <stdin> oh, wait
[08:27] <stdin> no
[08:27] <stdin> misread
[08:28] <cemc> yea, i ment if there are some logs or stats or something
[08:31] <stdin> I thinks there a bug report about that somewhere
[08:32] <persia> There are a couple bug reports, about the general class of "please expose statistics" for PPAs, for distros, for branches, for +downloads, etc.
[08:32] <stdin> https://bugs.edge.launchpad.net/soyuz/+bug/139855
[08:33] <persia> From what I've previously heard, this is something being discussed generally, rather than with reference to specific bugs (although it will probably go back to bugs if/when it gets implemented).
[08:34] <stdin> the report hints at the fact that it'd be difficult to gather that information, which I can imagine
[08:36] <persia> Well, it's hard to be accurate.  It's not hard to generate a lower bound of downloads.
[08:37] <persia> Well, except for the disconnect between ppa.launchpad.net and the other bits :)
[10:07] <thekorn> hi, is staging.launchpad.net down for everyone else, or just for me?
[10:07] <kiko-afk> thekorn, isn't it daily restore time?
[10:08] <thekorn> kiko-afk, I don't know, but maybe,
[10:08] <thekorn> will try again later today
[10:08] <kiko-afk> I think it is. we're trying to reduce that window -- I had a crazy idea with COW snapshots etc
[10:10] <thekorn> at least a message or something whould be really cool
[10:11] <kiko-afk> I'm looking into this..
[12:34] <ia> hello. i've uploaded package in ppa, it has been accepted, and it has been compiled successfully; but there is some errors in debian/ files, so i've deleted package from PPA, after sometime package has been deleted completly from ppa server, but now, when i try to upload fixed version, i get message via email about rejection, because package "is already accepted in ubuntu/jaunty and you cannot upload the same version within the same distribution. You have to m
[12:34] <ia> odify the source version and re-upload.". But there is no should be some additional source modifications or version name changes. so, could you tell me, please, how can i upload package?
[12:38] <persia> ia, You need to use a higher version number for each upload.
[12:39] <persia> e.g. if you start with something like 1.2.3-0ppa1, you'd then upload something like 1.2.3-0ppa2 with your packaging fixes.
[12:42] <ia> persia: so, there is no any way to upload the same version twice, even the first one has been deleted completely, right?
[12:43] <persia> Nope.
[12:43] <persia> Well, there is, but it's *very* complicated, and you have to bribe the admins: better to increase the version.
[12:46] <ia> persia: :-) ok, thanks
[14:47] <dereine> hi, is it allowed to host configs on launchpad?
[14:49] <savvas> configs such as?
[14:50] <dereine> .bashrc .foorc
[14:51] <dereine> to share them with other people
[14:52] <persia> dereine, Just create a bzr branch at lp:~dereine/+junk/configfiles with them.  As long as you license them with a license LP accepts, it ought be fine.
[14:53] <dereine> persia: wow thx
[14:53] <dereine> i expected its only allowed to host real projects thx!
[14:54] <persia> The special +junk project is specifically designed for bits and bobs that don't belong in a real project.
[14:54] <persia> Since it exposes a private namespace for you to name branches however you want, you can put anything you want there.
[15:16] <lfaraone> Hi, can https://edge.launchpad.net/~sugar please be deleted? (requested by owner)
[15:24] <maxb> lfaraone: for reasons of authentication, delete requests are (obviously) not acceptable over irc!
[15:24] <maxb> You need to file the request at https://answers.launchpad.net/launchpad
[15:26] <lfaraone> maxb: OK.
[15:28] <lfaraone> maxb: also, https://edge.launchpad.net/~sugarteam is listed as using a LP mailing list but it is currently unused, we are usign ubuntu-sugarteam instead. how hard would it be to migrate?
[15:28] <lfaraone> maxb: filed: https://answers.edge.launchpad.net/launchpad/+question/58573
[15:29] <maxb> I'm not a Canonical person, I'm just repeating the advice I'm seen them repeatedly give here :-)
[15:29] <maxb> * I've
[15:30] <lfaraone> maxb: Understood.
[16:00] <asabil> hi all
[16:01] <asabil> is this supposed to work: bzr branch lp:ubuntu/jaunty/vala ?
[16:07] <beuno> asabil, not yet
[16:07] <asabil> oki
[16:35] <mok0> How can I delete a blueprint?
[16:37] <persia> mok0, You can't.
[16:38] <mok0> I can't retarget it either, that doesn't work
[16:39] <mok0> I accidentally created a blueprint under "launchpad" namespace and it wont allow me to retarget it for "ubuntu", it claims the bp already exists under "launchpad".
[16:39] <mok0> My reply is: I KNOW that, that's why i am trying to move it!!
[16:39] <mok0> Grrr
[16:44] <persia> Oh, I believe they can be retargeted with a question.
[17:07] <mok0> persia: with a question?
[17:08] <persia> https://answers.launchpad.net/launchpad/
[17:09] <persia> To put it another way, I suspect someone can tweak the right bits to retarget a spec.  Deleting causes other issues.
[17:12] <mok0> I see.
[17:12] <mok0> Thanks
[17:37] <dereine> i pushed now this branch, https://code.launchpad.net/~dereine/+junk/configfiles but there is no possiblity to see the files or anything else
[17:38] <persia> dereine, I can see http://bazaar.launchpad.net/%7Edereine/%2Bjunk/configfiles/annotate/head%3A/.vimrc
[17:38] <persia> Try clicking "Source Code" from the branch overview page.
[17:42] <dereine> ah it needs some time
[17:42] <dereine> thx
[18:33] <jkakar> Do any of the code hosting guys know if the failures for this import are fixable?  https://code.edge.launchpad.net/~vcs-imports/libtorrent/trunk
[18:34]  * rockstar looks
[18:35] <rockstar> jkakar, looks like a cert problem.
[18:35] <jkakar> rockstar: Yeah.  I was wondering if it was something you already knew about, or just random crapiness.
[18:36] <rockstar> jkakar, we've seen a bunch of SSL certs change recently.  Not sure what's going on.
[18:36] <rockstar> This is probably the 4th or 5th time I've seen it in the last two weeks.
[18:36] <jkakar> rockstar: Ah, interesting.  While I've got your attention, another of my vcs-imports has been failing forever: https://code.edge.launchpad.net/~vcs-imports/gdb/trunk
[18:36] <rockstar> jkakar, it can probably be fixed, but will require a LOSA or mwhudson.
[18:37] <jkakar> rockstar: Cool, thanks.
[18:38] <rockstar> jkakar, the gdb one I have no idea about.  I'm willing to admit that vcs-imports need to be really worked on, because they fall over so often.
[18:38] <jkakar> rockstar: Yeah, well I bet it's a super tricky problem space. :)
[18:39] <rockstar> jkakar, I'm actually planning on doing some hacking on cscvs today, so I'll try and find the cause of that one.
[18:39] <jkakar> rockstar: The gdb one I suspect is CVS evilness.  It's an old repo and you know that the kind of person that hacks on GDB is also the kind of person that will manually "fix" their revisioned data. :)
[18:39] <jkakar> rockstar: Awesome, thanks!
[18:39] <rockstar> Yes, CVS is evil, but cscvs usually does alright with CVS stuff.  :/
[18:39] <jkakar> Aye.
[19:23] <dereine> how can i pull my current working branch to a version on a remote branch?
[19:24] <dereine> sry wrong channel
[19:31] <shilbert> Hi all, how can one contact launchpad admins ?
[19:45] <Ursinha> shilbert, what do you need?
[19:45] <persia> shilbert, Get lucky asking here, or file a question as answers.launchpad.net/launchpad
[19:51] <shilbert> Usrsinha: There is something wrong with my key in launpad and I need to have it removed so I can reupload it.
[19:54] <dnyy> I got a rejection email while uploading to PPA that isn't listed in the common errors secton.  It says "
[19:54] <dnyy> Unable to find distroseries: unstable. Further error processing not possible because of a critical previous error.
[19:54] <dnyy> Sorry about the cutoff, irssi does that sometimes when I copy/paste. ;o
[20:07] <persia> dnyy, There's no series "unstable" in Ubuntu against which you can build.  Try selecting "hardy", "intrepid" or "jaunty".
[20:09] <dnyy> ah, my bad, thanks.
[21:28] <Laney> Is anyone working on the current timeouts? OOPS-1120EB734 for example.
[22:37] <mib_q3893gop> hi
[22:37] <mib_q3893gop> Does anyone know what the Ubuntu installer package is called?
[22:39] <charlie-tca> mib_q3893gop: there are two, one on the alternate cd and one on the liveCD
[22:39] <mib_q3893gop> What's the one called on the LiveCD?
[22:42] <mib_q3893gop> charlie-tca:What's the one called on the LiveCD?
[22:42] <charlie-tca> ubiquity
[22:45] <mib_q3893gop> Yes! That's the one
[22:45] <mib_q3893gop> Thanks
[22:48] <charlie-tca> no problem.