[04:11] <Hobbsee> persia: intrepid stuff even builds nwo, too.
[04:11] <Hobbsee> persia: although i guess that wasn't what you were targetting?
[04:16] <persia> Hobbsee: Nope :p
[04:49] <jamesh> https://edge.launchpad.net/shower-days <- there are all kinds of weird projects on launchpad
[04:55]  * jml blinks
[04:55] <jml> I have a core assumption that could drastically simplify that program.
[04:56] <RAOF> def needShowerToday (date) : return True
[04:56] <RAOF> ?
[04:57] <jamesh> RAOF: that doesn't look PEP-8 compliant
[04:57] <jml> yep!
[04:57] <wgrant> jamesh: Do you get emailed on new projects, or did you just happen to look at the recent projects list at the wrong time?
[04:57] <wgrant> Damn, no code yet :(
[04:57] <wgrant> I was going to package that most useful app.
[04:57] <jamesh> wgrant: I was looking at code.launchpad.net, and it was the most recently registered branch
[06:24] <LeeJunFan> over the last few days I haven't been able to successfuly use debmirror: dists/hardy-security/main/binary-i386/Packages failed md5sum check, removing
[06:41] <wgrant> LeeJunFan: From which mirror?
[06:42] <LeeJunFan> wgrant: us.archive.ubuntu.com
[06:43] <wgrant> Hmm, that's the main mirror.
[06:43] <wgrant> You're probably not meant to be using -security from them
[06:45] <wgrant> Although that probably still shouldn't be happening.
[06:48] <StevenK> Hi, I've discovered one of the packages in the ubuntu-mobile PPA is not in the Packages file. Is there anything I can do to correct it?
[06:48] <wgrant> StevenK: Which is it?
[06:49] <StevenK> moblin-image-creator
[06:49] <StevenK> What's worrying me is it may be more than one
[06:50] <wgrant> Huh.
[06:50] <wgrant> The source is there, but the binaries aren't. SPecial.
[06:52] <LeeJunFan> wgrant: that's the one I've always used, I get that error on some other dists as well, intrepid (anything), hardy-security...
[06:52] <wgrant> LeeJunFan: How long has it been?
[06:52] <LeeJunFan> 3 days I think.
[06:53] <StevenK> wgrant: The binaries are listed on the PPA page
[06:53] <wgrant> StevenK: So I see.
[06:53] <wgrant> And there's nothing obviously wrong with them, other than the fact that they're arch-indep.
[06:53] <StevenK> Which isn't a problem. :-)
[06:54] <wgrant> If Soyuz eats binaries, it eats arch-indep ones.
[06:54] <wgrant> It's happened at least twice before.
[06:54] <StevenK> Ah. Fun.
[06:54] <wgrant> Though for reasons that are impossible here.
[06:54] <StevenK> That was due to promotion ...
[06:54] <wgrant> Yes.
[06:55]  * wgrant uploads to his PPA to see if it's reproducable.
[06:56] <LeeJunFan> wgrant: looks like tuesday was the last good debmirror I got.
[07:00] <wgrant> LeeJunFan: I think it's something on your end, like a proxy. I can mirror hardy-security/i386 fine from archive.ubuntu.com
[07:02] <wgrant> StevenK: Interesting, copying moblin-image-creator into my PPA worked fine.
[07:03] <wgrant> It would be nice if we could see the binary publishing status, but we can't for PPA packages :(
[07:04] <LeeJunFan> ok, I'll switch to another link and try.
[07:06] <wgrant> And somebody DoSed the i386 PPA buildds, so my fresh test upload won't build for another little while.
[07:07] <LeeJunFan> wgrant: looks like it was entries in .temp in the local mirror dir.
[07:07] <LeeJunFan> thanks for verifying it for me.
[07:08] <wgrant> LeeJunFan: Aha. No problem.
[07:11] <\sh> wgrant, DoSed i386 PPA?
[07:11] <\sh> moins btw
[07:12] <wgrant> \sh: The queue is immense.
[07:12] <wgrant> ALthough they must be langpacks, as mine is already building.
[07:12] <wgrant> Morning.
[07:12] <\sh> ah
[07:12] <StevenK> The queue has been pitti'd again?
[07:13] <StevenK> Yup. 378 langpacks
[07:13] <geser> 2 of the 3 i386-PPA-buildds are building language packs right now
[07:14] <wgrant> Within a couple of hours their priority will likely have exceeded that of any other build.
[07:14] <wgrant> So it'll be properly DoSed.
[07:16] <\sh> they should add another one for those langpacks
[07:16] <StevenK> There is an open bug that langpacks should have the lowest priority
[07:16] <wgrant> Or perhaps just forbid them from at least one buildd.
[07:16] <wgrant> StevenK: Right, but over time it goes up.
[07:19] <Hobbsee> what do you guys need boosted?
[07:19] <wgrant> Nothing at the moment.
[07:21] <wgrant> Yay for intermittent unreproducible Soyuz bugs.
[07:35] <wgrant> al-maisan: Are you around and able to look into a PPA oddity?
[07:36] <al-maisan> wgrant: what is the PPA oddity about?
[07:36] <wgrant> al-maisan: StevenK has noted that the moblin-image-creator binary is missing from Packages in the ubuntu-mobile PPA, though it's in the pool.
[07:37] <wgrant> Copying it to another PPA gets the binary published fine there.
[07:37] <al-maisan> wgrant: OK, so the package is not listed on the GUI page?
[07:37] <wgrant> al-maisan: It's there, but not in Packages.gz.
[07:38] <wgrant> It should be in http://ppa.launchpad.net/ubuntu-mobile/ubuntu/dists/hardy/main/binary-i386/Packages.
[07:38] <StevenK> Or binary-lpia
[07:38] <wgrant> Or binary-amd64.
[07:39]  * al-maisan looks
[07:41] <wgrant> It's in my copy: http://ppa.launchpad.net/wgrant/ubuntu/dists/hardy/main/binary-i386/Packages
[07:42] <al-maisan> OK
[07:45] <al-maisan> the image-creator was only built for i386?
[07:45] <al-maisan> https://edge.launchpad.net/~ubuntu-mobile/+archive?field.name_filter=creator&field.status_filter=published
[07:46] <wgrant> al-maisan: It's arch-indep.
[07:46] <al-maisan> Ah, OK.
[07:47] <wgrant> (that's bug #40096)
[07:47] <al-maisan> OK.
[07:53] <al-maisan> wgrant: I am afraid this will have to wait until cprov signs in .. sorry
[07:54] <wgrant> StevenK: ^^
[07:54] <StevenK> Okay
[09:29] <cprov> wgrant: hi, what's the prob ?
[09:29] <wgrant> 16:36:49 < wgrant> al-maisan: StevenK has noted that the moblin-image-creator binary is missing from Packages in the ubuntu-mobile PPA, though it's in the pool.
[09:29] <wgrant> 16:37:06 < wgrant> Copying it to another PPA gets the binary published fine there.
[09:29] <wgrant> cprov: ^^
[09:31] <cprov> wgrant: okay, let me check, one sec
[09:33] <cprov> StevenK: was it correct at any point ?
[09:36] <StevenK> cprov: Most likely. It was conspicious in it's absence.
[09:36] <StevenK> (As it were)
[09:36] <wgrant> It only had two days to be there, didn't it?
[09:38] <StevenK> I'm not certain if it has been there. The version previous was in there
[09:38] <cprov> yes, looking at the logs it was correctly published on 2008-06-04 04:00:32 (BST)
[09:41] <wgrant> cprov: Ah, so it is no longer published, but death row hasn't been processed?
[09:42] <wgrant> Is binary publishing status for PPAs deliberately hidden to simplify things?
[09:42] <cprov> wgrant: yes it is
[09:43] <cprov> wgrant: but its not the case, its binary is also published.
[09:43] <wgrant> Ah, even more special.
[09:43] <wgrant> So NMAFA is being dodgy?
[09:53] <cprov> wgrant: uhm, I see a bug
[09:53] <cprov> wgrant: https://edge.launchpad.net/~alexander-l-lopatin/+archive?field.name_filter=creator&field.status_filter=any
[09:55] <wgrant> It's dominating cross-archive?
[09:55] <cprov> wgrant: he copied you source & binaries and superseded it in his PPA, since it's a arch-indep the dominator took all occurrence of the same binarypackagerelease
[09:55] <wgrant> Yep.
[09:55] <cprov> wgrant: yes, it's very broken.
[09:55] <wgrant> So another arch-indep incorrect domination bug? I was right!
[09:56] <wgrant> I jokingly said it would have been eaten because it was arch-indep earlier, as that's where the other binary-eating bugs have been.
[09:56] <cprov> wgrant: yes, you are right
[09:56] <wgrant> Why is arch-indep domination so different?
[09:56] <cprov> wgrant: could you please file a bug I will start working
[09:56] <wgrant> And can I get primary things dominated by uploaded the same thing to my PPA? Sounds good.
[09:57] <wgrant> *by uploading
[09:57] <cprov> wgrant: becuase it has to dominate all binarypackagerelease (across distroarchseries) atomically
[09:58] <wgrant> cprov: Ah, right, so there's a separate BPR for each DAS. I didn't realise that.
[09:58] <cprov> wgrant: no, it only affects archives where the same BPR is published
[09:58] <cprov> wgrant: no, there is not, it's the same BPR published in different DASs
[09:59] <wgrant> cprov: I currently have the same version of soundconverter in my PPA/{hardy,intrepid} as in primary/intrepid. If I upload a new soundconverter to my PPA, will primary/intrepid's soundconverter binary vanish?
[09:59] <wgrant> cprov: Ah, so multiple BPPs, right.
[09:59] <wgrant> That makes more sense.
[10:00] <cprov> wgrant: the intrepid probably will
[10:00] <wgrant> cprov: Right, so it's fairly bad.
[10:00] <cprov> wgrant: yes, quite bad, needs a fix ASAP.
[10:00]  * wgrant files the bug.
[10:00] <wgrant> cprov: Thanks for looking into this.
[10:05] <cprov> StevenK: I've requested the re-publication of your binaries (ubuntu-mobile) they will show up in the indexes in 15 minutes.
[10:05] <cprov> StevenK: sorry for this inconvenience :(
[10:06] <StevenK> cprov: It's okay, thanks!
[10:14] <wgrant> cprov: Is that two arch-indep domination bugs in as many days, or is bug #237353 not arch-indep-specific?
[10:18] <cprov> wgrant: this one is not exactly the same issue
[10:19] <cprov> wgrant: it was cause by doubly copying the same arch-indep binary to the same target.
[10:19] <cprov> wgrant: it's another bug in the same code, though.
[10:20] <wgrant> Ah.
[10:20] <wgrant> Do we know if any primary binaries are missing because of this?
[10:23] <cprov> wgrant: I can check, but it's unlikely, since no binaries were copied from PPAs.
[10:24] <cprov> wgrant: we already rebuild, so they are different BPRs.
[10:24] <cprov> s/already/always/, sorry
[10:24] <wgrant> Ahh, true, forgot that.
[10:26] <wgrant> It's not like SourcePackageNames where they're always shared, of course. I'm stupid.
[10:28] <cprov> wgrant: but we can calculate all ppa binaries superseded by builds happening in other archive, and filter out the intentional copies ...
[10:28] <cprov> wgrant: not exactly easy :(
[10:44] <cprov> wgrant: did you open the bug ?  the code is fixed and tested ;)
[10:45] <al-maisan__> wow!
[10:45] <cprov> wgrant: yes, you did, https://bugs.edge.launchpad.net/soyuz/+bug/237845
[10:45] <wgrant> cprov: Oops, forgot they weren't automatically reported in here any more. Sorry.
[10:52] <wgrant> al-maisan__: Soyuz rebuild handling is coming? This is very good news.
[10:52] <al-maisan__> yep.
[10:53] <wgrant> My archive rebuild setup isn't exactly robust, and requires a fair bit of handholding, so it will be good to retire it.
[10:53] <geser> wgrant: archive rebuilds done by soyuz?
[10:54] <al-maisan__> it's a coming feature
[10:54] <wgrant> geser: It looks like they're finally happening, yep...
[10:54] <geser> also for universe?
[10:55] <wgrant> There's surely enough buildd idle time (except on hppa).
[10:55] <al-maisan__> I understand it will be a generally available feature provided you have the proper credentials
[10:55] <al-maisan__> to make use of it
[10:57] <cprov> al-maisan: ehe, you working in the marketing department ? that was a beautiful phrase :)
[10:58] <wgrant> Can we search through PPA package contents yet?
[10:58] <al-maisan> cprov: thanks .. ;-)
[10:58] <cprov> wgrant: yes, ubuntu/+ppas
[10:58] <wgrant> Or did you use superpowers to work out where the dominator was?
[10:58] <cprov> wgrant: sorry ? 
[10:58] <wgrant> Ah, so I see. Rather nice.
[10:59] <wgrant> cprov: I didn't think /ubuntu/+ppas searched through package names, so was wondering if you'd used some tool only accessible by Soyuz devs to work out where the guilty moblin-image-creator was.
[11:01] <cprov> wgrant: right, you can do some investigation using the results of ubuntu/+ppas search, it will show you all PPAs where moblin-image-creator was published
[11:02] <cprov> wgrant: the caches are updated daily, so there might be a lag.
[11:02] <wgrant> Right.
[11:02] <cprov> wgrant: it doesn't allow version-wise searches, yet. 
[13:32] <mpt> Goooooooooooooooooooood afternoon Launchpadders!
[13:34] <Hobbsee> *evening* mpt!
[13:37] <mpt> Hobbsee, always the contrarian :-)
[13:38] <Hobbsee> mpt: of course.
[13:39] <Hobbsee> mpt: besides, i can't be eating dinner in the afternoon.
[13:40] <Hobbsee> and obviously, it's to train you for the next down-under UDS.
[13:43] <intellectronica> mpt: still on a self-inflicted jet-lag?
[13:45] <mpt> intellectronica, yeah, but improving
[15:25] <seiflotfy> hi guys i want to upload soem code as a new branch for mayanna ( my project )
[15:40] <brandon_rhodes> Is it normal to create a project and not be able to "bzr push" to it for an hour or two?
[15:42] <intellectronica> brandon_rhodes: what's the problem?
[15:42] <intellectronica> what happens when you try to push
[15:43] <brandon_rhodes> I created a "ReleaseThis" project and get an error "Project 'ReleaseThis' does not exist." when I try to: bzr push bzr+ssh://brandon-rhodes@bazaar.launchpad.net/~brandon-rhodes/ReleaseThis/trunk
[15:43] <brandon_rhodes> The full error:
[15:43] <brandon_rhodes> bzr: ERROR: Generic bzr smart protocol error: Permission denied: "Project 'ReleaseThis' does not exist."
[15:45] <brandon_rhodes> Sorry if you just said something useful; xchat grabbed my focus atop its "close" button right as I was clicking :-/
[15:45] <intellectronica> brandon_rhodes: just a guess, but what happens if you try releasethis instead of ReleasThis (in the branch url)?
[15:47]  * brandon_rhodes adjusts his FVWM setup so that it will ignore the focus-grabbing messages from xchat
[15:49] <brandon_rhodes> So, this "bzr push", with the lower-case, is hanging indefinitely instead of returning immediately with the error
[15:49] <brandon_rhodes> Which I can't decide is an improvement or not
[15:52] <intellectronica> heh
[15:53] <intellectronica> no idea why it should hang. try again?
[15:53] <brandon_rhodes> Ah!  After four minutes, it says "Created new branch"
[15:53] <brandon_rhodes> So the lower case thing was my problem
[15:54] <brandon_rhodes> It should issue a warning if it sees a capital letter
[15:54] <brandon_rhodes> :-)
[15:54] <intellectronica> why should it? the client doesn't know about that
[15:55] <intellectronica> it's launchpad that doesn't allow mixed-case project names
[15:55] <brandon_rhodes> Ah, it's not a launchpad-specific mapper between person/project/branch URLs and actual repositories?
[15:55] <brandon_rhodes> I figured there was launchpad magic that understood the three-level stuff, and thus returned me an error saying there was no project with the name of the middle URL component
[15:56] <intellectronica> oh, actually, looking at the error, you're probably right. it looks like a server error
[15:56] <intellectronica> feel like filing a bug?
[15:57] <brandon_rhodes> oh, duh, I forgot that launchpad has a launchpad page :-)
[15:57] <brandon_rhodes> I'll go do that
[15:57] <intellectronica> brandon_rhodes: https://edge.launchpad.net/launchpad-bazaar/+filebug
[15:57] <beuno> well, linuz *is* case-sensitive
[15:57] <beuno> so it's not really a launchpad-specific issue
[15:58] <brandon_rhodes> linuz?
[15:58] <intellectronica> beuno: i don't understand
[15:58] <beuno> er, "linux"
[15:58] <wgrant> Linux isn't case sensitive.
[15:58] <wgrant> Some of the filesystems are.
[15:58] <wgrant> But that's not the problem here.
[15:59] <beuno> wgrant, is there any case insensitive linux filesystems?
[15:59] <brandon_rhodes> Linux is case insensitive?!
[16:00] <wgrant> Case sensitivity could refer to any of a huge number of attributes. You can't just say 'OS Y is case (in)sensitive'
[16:00] <beuno> :)
[16:57] <geser> cprov: is it still the best way to find out why a build failed to upload to ask you to look it up? or is there a public place to look it up?
[17:02] <kiko> geser, the build log is usually the best place to look :)
[17:02] <geser> kiko: also for failed to upload?
[17:03] <geser> kiko: the package build successfully but isn't then accepted to the archive
[17:03] <kiko> that's different, but the log often contains a clue
[17:03] <kiko> I think we publish upload failures somewher e public as well -- cprov?
[17:04] <geser> kiko: I know they got mailed to the uploader, but this doesn't help me, when I didn't upload the package
[17:05] <kiko> geser, yeah, I asked for this to be publically posted but am not sure where
[17:05] <kiko> let's wait for cprov to come back
[17:13] <cprov> geser: the upload log is part of the build-failure-notification
[17:15] <cprov> geser: which package are you talking about ? It's usually very easy to find out.
[17:16] <geser> libqt4-ruby and indi (both intrepid)
[17:16] <cprov> geser: ah, ubuntu primary archive.
[17:16] <geser> yes
[17:16] <cprov> geser: I receive those
[17:18] <cprov> libqt4-ruby, old version
[17:18] <cprov> indi, the same.
[17:19] <cprov> geser: do you want me to forward the messages to you ?
[17:21] <geser> cprov: please do
[17:24] <cprov> geser: email ?
[17:25] <geser> cprov: geser@ubuntu.com
[17:26] <cprov> geser: done
[17:28] <geser> cprov: thanks
[17:28] <geser> it's really nice if a binary package is build from two source packages :(
[17:29] <cprov> https://edge.launchpad.net/ubuntu/+source/kdebindings-kde4/4:4.0.3-0ubuntu4 & https://edge.launchpad.net/ubuntu/+source/libqt4-ruby/1.4.10-3
[17:29] <cprov> geser: messy
[17:33] <kiko> cprov, can we post those failures somewhere public?
[17:35] <cprov> kiko: talk to elmo/infinity, https://lists.ubuntu.com/mailman/listinfo/launchpad-buildd-admins
[17:36] <cprov> kiko: we could probably afford 2 weeks history or so.
[17:36] <kiko> cprov, so the ML exists but no posts have been made to it?
[17:36] <kiko> https://lists.ubuntu.com/archives/launchpad-buildd-admins/
[17:36] <cprov> kiko: archiving is disabled
[17:37] <kiko> ah, ok.
[17:37] <kiko> is that all that goes to that list?
[17:38] <cprov> kiko: yes, all build-failure-notifications.
[17:48] <geser> cprov: so I simply need to subscribe to that ML to get those notifications?
[17:48] <cprov> geser: dunno, if it's open for subscription.
[19:06] <pwnguin> i can't seem to find a bug about it -- does LP work with gforge that's not SF?
[19:07] <pwnguin> bugwatch I mean. it seems to have decided a gforge.blah url is SourceForge
[19:20] <kiko> pwnguin, really? can you show me a bug where that happened?
[19:23] <pwnguin> well crap
[19:23] <pwnguin> i removed it
[19:24] <pwnguin> bug #81594
[19:24] <pwnguin> maybe i did something wrong ages ago, I cant recall
[19:26] <pwnguin> kiko: at any rate, it wont let me add http://gforge.lug.fi.uba.ar/tracker/index.php?func=detail&aid=965&group_id=11&atid=129
[19:27] <kiko> pwnguin, what happens when you do?
[19:28] <kiko> can you try it on a bug on staging.launchpad.net and show me?
[19:28] <pwnguin> just any bug?
[19:30] <pwnguin> heh
[19:30] <pwnguin> it wont let me on staging
[19:30] <pwnguin> You are not the bug assignee nor the maintainer of Oregano, and therefore cannot edit this bug's status. 
[19:30] <kiko> pwnguin, what happens?
[19:31] <kiko> pwnguin, okay, try iton a bug which you /can/ edit :)
[19:32] <pwnguin> oh, apparently im not logged in
[19:33] <pwnguin> alrighty
[19:33] <pwnguin> bug #81584 on staging
[19:33] <pwnguin> err
[19:34] <pwnguin> bug #81594 on staging
[19:34] <pwnguin> https://bugs.staging.launchpad.net/oregano/+bug/81594/+editstatus
[19:34] <pwnguin> There is 1 error in the data you entered. Please fix it and try again. 
[19:36] <pwnguin> kiko: not sure what the error is, mind you. but there's only two pieces of data entered...
[19:42] <kiko> pwnguin, this is very weird!
[19:43] <pwnguin> indeed
[19:43] <pwnguin> im blaming someones regex
[20:26] <kiko> pwnguin, it's a bit odd.. 
[20:26] <kiko> gmb, are you gone yet?
[20:29] <gmb> kiko: I'm still around, for a short while. What's up?
[20:30]  * gmb reads scrollback
[20:32] <kiko> gmb, we're not accepting a gforge-type URL
[20:32] <kiko> http://gforge.lug.fi.uba.ar/tracker/index.php?func=detail&atid=129
[20:32] <gmb> kiko: pwnguin's right: it's quite likely a bad regex in the bug watch parsing code. I'll look into it.
[20:33] <pwnguin> "Many people, when faced with a problem, think 'I know, I'll use regular expressions'. Now they face two problems" :)
[20:35] <kiko> pwnguin, in this case.. it's kinda hard to avoid without offering you more questions :)
[20:35] <gmb> pwnguin: Actually, looking at the code, the problem here is that sourceforge and gforge bug URLs can look identical. So we have to decide based on hostname as to which tracker it is (there being only one SourceForge). For some reason, that's not working here. I'll see if I can reproduce it locally.
[20:35] <kiko> gmb, maybe if pwnguin registers the bugtracker first
[20:36] <gmb> kiko: Ah. Good idea.
[20:36] <pwnguin> well, if they all look and work the same
[20:36] <pwnguin> i cant see the problem :)
[20:36] <gmb> pwnguin: Right :)
[20:37] <kiko> pwnguin, can you register the bugtracker at /bugs/bugtrackers?
[20:37] <gmb> pwnguin: Can you try registering the tracker https://edge.launchpad.net/bugs/bugtrackers/+newbugtracker?
[20:37] <gmb> Hah.
[20:37] <gmb> There's an echo.
[20:37] <pwnguin> gmb wins
[20:43] <gmb> That's really weird. It should *just work*.
[20:43] <pwnguin> heh
[20:43] <gmb> At least according to the code...
[20:43] <pwnguin> kiko's link doesnt work
[20:43] <gmb> pwnguin, kiko: I just have to step out of a bit but I'll look into this when I get back.
[20:44] <gmb> pwnguin: If registering a bugtracker and then creating a bug watch solves your problem, I'd be obliged if you could file a bug about it at http://bugs.launchpad.net/malone/+filebug.
[20:45]  * gmb -> exeunt
[20:47] <pwnguin> well good news. i think i registered the bugtracker
[20:48] <pwnguin> and it still doesnt work
[21:38] <kiko> pwnguin, so it's still a bug. :-)
[21:39] <kiko> pwnguin, well, hang on
[21:39] <kiko> pwnguin, can you try again adding the bugwatch? I've updated the URL for the tracker.
[21:50] <kiko> pwnguin, yeah, doesn't work! file a bug :)
[21:50] <MvG> I'm waiting for the svn mirror for the vpnc project, registered two days ago, still in Testing status. There is a branch from jelmer. Does that mean he is the one doing the testing and responsible for setting up the official mirror once he's satisfied?
[21:51] <kiko> MvG, hang on.
[21:55] <kiko> MvG, no, in this case, it appears jelmer was maintaining a trunk branch of it 
[21:55] <kiko> but it seems out of date, right?
[21:55] <kiko> yeah
[21:56] <MvG> Seems to be no longer there.
[21:56] <kiko> I just renamed it to trunk-old
[21:57] <kiko> MvG, https://code.edge.launchpad.net/~vcs-imports/vpnc/trunk
[21:57] <kiko> it'll be importing soon
[21:57] <kiko> it's not so many revisions, so it should be finished in an hour or so
[21:57] <MvG> kiko: Thanks!
[21:58] <MvG> Is that the testing version, or already the official one?
[21:58] <kiko> that will be the official import
[21:58] <kiko> once it's running
[22:06] <bdmurray> kiko: hey there
[22:07] <kiko> bdmurray!
[22:07] <kiko> you rockin' and rolling?
[22:07] <bdmurray> A bit.  My e-mail thread on launchpad-users has strayed away from what I was really curious about.
[22:09] <bdmurray> Should bugs with duplicates not be eligible for expiration.
[22:18] <Triskelios> what kind of interfaces does launchpad offer to for packaging processes? most package consolidations currently seem to just frontends to information from outside sources
[22:18] <pwnguin> kiko: is there a specific project i need to file a bug against? launchpad itself or?
[22:19] <Triskelios> *seem to be
[22:19] <kiko> pwnguin, malone/+filebug
[22:20] <kiko> Triskelios, what do you mean, exactly? are you asking about PPAs in particular?
[22:20] <kiko> bdmurray, it hasn't strayed -- Bjorn and I said that no, they shouldn't.
[22:20] <kiko> oh
[22:20] <kiko> bdmurray, bugs /with/ duplicates
[22:20] <kiko> sorry, I think we both missed that :)
[22:20] <kiko> bdmurray, can you reply again pointing out our myopia? :)
[22:21] <bdmurray> that's what I get for making it the last line. ;)
[22:21] <bdmurray> kiko: will do
[22:21] <Triskelios> kiko: no, just generic packaging processes for an entire community
[22:22] <kiko> Triskelios, okay, I really don't know what you mean. 
[22:23] <kiko> can you give me a concrete use case?
[22:29] <Triskelios> kiko: given a a medium-size package repository with dozens of maintainers, I want to move all of the processes (managing maintainers, adding packages, tracking bugs/upstream, autobuilds and publishing releases with our own mechanisms) into launchpad
[22:31] <kiko> Triskelios, tell me more about this package repository. what sort of packages, which upstreams, etc?
[22:35] <pwnguin> Triskelios: group PPAs sound close to fitting the bill, but I dont think you can file bugs against them yet
[22:35] <Triskelios> kiko: this a repository of spec files (derived from the rpmbuild spec format) which will target two different distributions (with two different binary packaging mechanisms) on multiple architectures. the repository packages close to an entire distro so upstream is hundreds of different free-software sources
[22:35] <Triskelios> pwnguin: this is not a simple apt repository
[22:35] <pwnguin> i dislike the word simple
[22:36] <kiko> heh
[22:36] <kiko> Triskelios, so.. I think that yes, launchpad can support that. let me elaborate.
[22:36] <kiko> Triskelios, first, I think you want to keep these spec files in revision control, right? 
[22:36] <kiko> Triskelios, you can use one or more branches, associated to one or more projects
[22:37] <pwnguin> does LP offer non deb build services?
[22:39] <Triskelios> pwnguin: I just mean this is supposed to be used by an entire packaging community, not an individual, and I'm not asking about a service for a specific software mechanism. we're okay with using our own autobuilders
[22:40] <pwnguin> i guess i dont understand -- are you a new distro or not?
[22:40] <Triskelios> kiko: we currently have a crappy scm for the files, I'm looking at Bazaar's integration with the various SCMs
[22:42] <Triskelios> pwnguin: basically our project started as a file dump, but we're trying to organise things so we can actually publish binaries for a distro
[22:42] <kiko> Triskelios, this sounds really cool
[22:42] <pwnguin> oh, i see. you want to use LP to host the SPEC files in RCS
[22:43] <kiko> Triskelios, so I think launchpad fits your bill pretty well. you can have nested teams, individual upstream projects, team-committing branches, do releases, announcements, etc.
[22:46] <pwnguin> kiko: so... while filing the bug I tried again to get the error message.  works now =(
[22:47] <pwnguin> kiko: except the URL is busted
[22:47] <pwnguin> but thats a known bug
[22:47] <kiko> pwnguin, really now! show me?
[22:48] <pwnguin> https://bugs.edge.launchpad.net/oregano/+bug/81594
[22:48] <pwnguin> assigned to oregano-bugs #965
[22:48] <pwnguin> ^ not that
[22:48] <Triskelios> kiko: cool. I'm trying to dig through the documentation (which seems mostly focused on single projects) right now
[22:49] <kiko> Triskelios, I'm not entirely sure how you'd model your project -- as a project group with individual projects under it, or something mroe complex.
[22:49] <pwnguin> kiko: if you hit the upstream bug link in on the page, it cries page not found -- apparently this is one of those "gforge is not SF" things
[22:51] <Triskelios> kiko: I'm looking at debian and ubuntu as models really, although a lot of their maintainer stuff happens externally
[22:51] <kiko> pwnguin, yeah, gforge is kinda weird. we need to sort out the links to that properly
[22:52] <kiko> Triskelios, well.. we don't have bzr for distro packages yet, which is one issue.
[22:53] <pwnguin> fixed soon /crosses fingers
[22:55] <kiko> pwnguin, is there a bug filed for that?
[22:55] <pwnguin> packages in bzr
[22:55] <pwnguin> ?
[22:55] <pwnguin> https://bugs.edge.launchpad.net/malone/+bug/226596
[22:55] <johan> mwhudson_: around?
[22:56] <kiko> pwnguin, oh. right. it's a big post-july feature.
[22:56] <johan> I'm seeing  an error in the bzr import when importing kiwi: http://launchpadlibrarian.net/15092985/kiwi-trunk-log.txt
[22:56] <pwnguin> and https://bugs.edge.launchpad.net/malone/+bug/193742
[22:56] <Triskelios> kiko: that is a potential blocker
[22:57] <kiko> Triskelios, well, you could just work off team branches or product branches for now.
[22:58] <Triskelios> kiko: would that be confusing to users who want to file bugs?
[22:59] <kiko> Triskelios, it depends, I guess. If you have thousands of packages that users will file bugs against, then a bit
[22:59] <kiko> Triskelios, what do you use today?
[23:00] <Triskelios> kiko: it's currently a single project on sourceforge. the interface sucks
[23:01] <kiko> Triskelios, so, I think we could do this. you could request a distro on answers.l.n (see /topic), and have your bugs imported from SF.net. you could define a few teams, and then register a product which held your branches, for now. there's no problem connecting any branch to a bug, so that would work fine.
[23:05] <Triskelios> kiko: that sounds okay. I want to make sure this will scale properly once we start delivering binaries
[23:06] <kiko> Triskelios, well, we currently only build .debs. that's one thing that you need to consider.
[23:10] <Triskelios> kiko: are there places where LP extracts package metadata, or makes other file format assumptions, that we should be aware of?
[23:11] <kiko> Triskelios, nope.
[23:11] <kiko> Triskelios, only when you upload packages to soyuz or a PPA that is.
[23:11] <kiko> but you don't need to use that.
[23:11] <Triskelios> I didn't expect to have autobuilds certainly, although I'd like to have integration with our autobuild system
[23:12] <kiko> Triskelios, I can imagine you integrating via bzr branching, which should be a great way to do it.
[23:33] <Triskelios> kiko: thanks for the help, I'll discuss this with other project members
[23:38] <kiko> Triskelios, if you need any further help, just ask. kiko@canonical.com
[23:39] <Triskelios> will do, thanks!
[23:39] <kiko> cheers
[23:48] <MvG> lirc apparently had its last CVS sync fail in 2007-03-01 and no new attempt since. I just got a successful checkout, so maybe someone might trigger automatic mirroring again.